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.

Found a deal on a Glass Screen Protector and USB C Cable.

http://slickdeals.net/f/8055990-onep...src=SiteSearch

Found this on Slickdeals-- though i'd share, in case anyone else (like me) is sitting there patiently... waiting for my phone to come....

Found the Menu Button

Several release ago Samsung did away with a dedicated menu button. Many of the application developers enhanced their apps to have the 3 dots in the upper right hand corner to allow touch access to the menu button.. In the S6 those apps with out a menu button had a floating circle with the 3 dots. Now with the note 5 I could not find a button combination or the floating circle for apps like moon reader. Previously you would press and hold the multitasking button. NOW you need to press and hold the back button. Why do they need to change this so often and not communicate it? Oh well but there is your answer

ADB Device not found!

I tried to use this guide to update to 5.1.1.
http://forum.xda-developers.com/g-wa...-lg-g-t3114528

Now, I'm stuck on the LG Screen at boot up. I can enter recovery mode/bootloader.
I'm fine with sideloading back stock boot recovery and sys images.
The only problem is that my device won't show up in ADB.
Allow me to clarify that 30 minutes ago, my device WAS showing up in adb while I was using the guide that I mentioned earlier.

New apps found on Alcatel oneTouch website

Check these out.


http://www.alcatelonetouch.com/global-en/apps/appsList

.

Found SD crad in new HTC One M9.

I received a factory sealed HTC One M9 the other day from Vodafone. When I opened the SD card slot drawer I found a old 8GB Micro SD card in it........

On the card are the following:

Folders: Android, ghost [inside: SystemLoggers.conf & SystraceEnabler.conf] & LOST.DIR.

Zip: OPJAIMG.zip & OPJAMFG.zip [inside: android-info.txt, dzdata_16g.hdr, dzdata_32g.hdr & dzdata_64g.hdr].

Other files: @@htcmfg_sfcdata.txt, @@file_crc.mfg, OPJAMFG.CRC, htc58diag, PTPTDIAG.nbh, sec.dat & @@station.txt

Any idea what they are used for????

No update found ,

Hello guys,

my at&t htc one m8 is stuck on 4.4.2 , i was in US till 14th of may and then came back on august 1st. When ever i try to update it just says no update found check after 48 hours .

I did reset the mobile couple of times with no help, I downloaded the manual update file from the htc website and it just says mobile is not detected or is on wrong ROM. I dont know what is wrong with this one , is there any workaround ? or should i try to take it to the at&t store ?

S-ON
Not rooted
everything is stock

Class File for SupportParentable in android.support.v4.app not found

So I just upgraded an ADT project to Android Studios, I've spent the day learning about Gradle and converting all the old imported libraries to compile lines, however I seem to be stuck on one final issue. The class:

public abstract class MainActivity extends ActionBarActivity

Is resulting in 21 Errors. The first 4 are

Error: (14, 17) error: cannot access SupportParentable class file for android.support.v4.app.TaskStackBuilder$SupportPar entable not found

Error: (31, 3) error: cannot find symbol variable super

Error: (42, 3) error: cannot find symbol variable super

Error: (47, 2) error: method does not override or implement a method from a supertype

(Rest available if anyone thinks they're relevant)

I have support-v4 and appcompat-v7 compiled:

compile "com.android.support:support-v4:22.2.1"
compile "com.android.support:appcompat-v7:22.2.1"

I've synced, cleaned and ran in all combinations. I'm not sure what step I'm missing here.

Yes I do know that ActionBarActivity has been depricated in place of AppCompatActivity, however switching to AppCompatActivity results in no noticeable changes. My focus right now is to get the project running as is and I'll look into modernizing after that.

Anyone found a good keyboard case for the Pro 8.4 yet?

Been looking around and everything looks pretty flimsy.