No bootloader interface is found ! :(

ADB interface driver can be easily installed when "USB debugging" is enabled in phone because this way it allows Windows to detect a device with name string "ADB interface driver" and its specific vendor id along with product id. In my case, VID is VID_0bb4 and PID is PID_0004&MI_02 ( this PID is for ADB interface only). There is no problem in installation and detection of "ADB interface". adb reboot-bootloader is working from both Windows 7 64 bit command prompt and Ubuntu 15.04 terminal. Till now it is okay.

Now, this is what I am stuck at.
if anyone understood me with previous part please help me unlocking bootloader because unlocking bootloader requires switching into "fastboot" mode. With ADB command I am able to switch my phone into "fastboot" mode successfully. Now I disconnect USB cable from phone. Phone is still in "fastboot" mode ("=>> fastboot ..." written in lowest left corner on the screen). I connect USB cable again. No other new device is found this time. Fastboot commands that is detecting my phone successfully is with that adb interface port. Why is that ? At least I have learned from Internet that "bootloader interface" is required for Windows to unlock bootloader. Now after searching through many android_winusb.inf file from USB driver folder, I found out that the device id (VID) is same for both "adb interface" and "bootloader interface" BUT product id (PID) is different for both interfaces. Now it is VID_0bb4&PID_0FFF.

According to inf, Windows/Linux will only detect "bootloader interface" when the device which here in this case is a phone provides the VID_0bb4&PID_0FFF through the USB cable. The real problem here is my phone which is Micromax Bolt A065 (Kitkat 4.4.2, Kernal 3.4.67) is providing only one VID/PID in both ADB and fastboot mode and that is of "ADB Interface" only.

How can I get my phone to send that "bootloader interface" vid/pid to Windows/Linux in fastboot mode ?

Latest Android SDK is installed.
Tested with many adb/fastboot USB Drivers from Internet.

No bootloader interface is found ! :(

ADB interface driver can be easily installed when "USB debugging" is enabled in phone because this way it allows Windows to detect a device with name string "ADB interface driver" and its specific vendor id along with product id. In my case, VID is VID_0bb4 and PID is PID_0004&MI_02 ( this PID is for ADB interface only). There is no problem in installation and detection of "ADB interface". adb reboot-bootloader is working from both Windows 7 64 bit command prompt and Ubuntu 15.04 terminal. Till now it is okay.

Now, this is what I am stuck at.
if anyone understood me with previous part please help me unlocking bootloader because unlocking bootloader requires switching into "fastboot" mode. With ADB command I am able to switch my phone into "fastboot" mode successfully. Now I disconnect USB cable from phone. Phone is still in "fastboot" mode ("=>> fastboot ..." written in lowest left corner on the screen). I connect USB cable again. No other new device is found this time. Fastboot commands that is detecting my phone successfully is with that adb interface port. Why is that ? At least I have learned from Internet that "bootloader interface" is required for Windows to unlock bootloader. Now after searching through many android_winusb.inf file from USB driver folder, I found out that the device id (VID) is same for both "adb interface" and "bootloader interface" BUT product id (PID) is different for both interfaces. Now it is VID_0bb4&PID_0FFF.

According to inf, Windows/Linux will only detect "bootloader interface" when the device which here in this case is a phone provides the VID_0bb4&PID_0FFF through the USB cable. The real problem here is my phone which is Micromax Bolt A065 (Kitkat 4.4.2, Kernal 3.4.67) is providing only one VID/PID in both ADB and fastboot mode and that is of "ADB Interface" only.

How can I get my phone to send that "bootloader interface" vid/pid to Windows/Linux in fastboot mode ?

Latest Android SDK is installed.
Tested with many adb/fastboot USB Drivers from Internet.

user interface stopped

Phone home screen or the so-called user interface stopped .. closed the phone and then re-run and still the same problem stops the user interface .. Is there a solution?
The problem that you've got to add many of the additions XPOSED .. Knowing that xposed installation was successful
models h818p dual sim

Help! How to get back the original phone interface?

I turned off advanced calling on my S6 Edge as the service sucked but I still have the advanced calling interface when making phone calls. Does anyone know how to remove this or revert it back to the original interface? I liked the other one better as it had the extra-volume button easily accessible.

[BUG REPORT] lock screen will make interface disappear after second video

By interface I mean the lock screen icon and any custom info that has been set. For example I have time remaining, time etc in the top corners. The only workaround is to switch on-off the screen with a hardware button, and the device will leave lock mode.

Using the last pro version in a Samsung galaxy 10.1 2014 but this issue is already several month in.

Fluidity of the interface ?

Hello, can you tell me if there's a way to make the interface of the stock rom more fluid ? I found it kinda sluggish compare to my old phone.

I haven't root the phone yet, but I saw that some xposed does work... what is the problem with that phone ? I mean even just going from one menu to another seems sluggish =T (and I set the animation to 0.5x) :confused: