Database Info

[Q] Fastboot with no USB Control Init/End messages? [i9020T]

Hey, I'm having trouble getting my phone recognised in Fastboot mode. I can get to the bootloader, but Windows 7 64 bit doesn't recognise it. And -- I think this is important -- I don't see the USB Control Init/USB Control Init End messages which usually appear when it's connected. Added to that, the Vol Up/Down keys don't work in Fastboot, but they do work in recovery and when ICS is running.
I've tried most, if not all, of the guides on Fastboot with Windows 7 64 bit. Yes, I've tried using the PdaNet drivers and all that. It used to work before, even without the PdaNet drivers.
All the symptoms are:
- Vol Up/Vol Down don't work in the bootloader. They do work in stock recovery and when the OS, ICS, is running.
- No USB Init messages appear at the bottom of the bootloader screen when the phone is connected to the PC (Win7 x64).
- Not recognised even PDANet drivers. adb devices lists the device, fastboot devices doesn't list the device, and fastboot flash recovery recovery.img says <Waiting for Device>
- i9020T with ICS 4.0.3 (Stock)
Any help would be great, thanks guys/gals.
Related:
My phone fell from a desk about waist height and now the Power Button doesn't work. Trying to get Fastboot working so I can install a ROM with Volume Wake since I'm running stock.

I'm having this EXACT same problem. Someone please help!

I'm also have this issue. Any help would be great

Tom Foolery said:
I'm also have this issue. Any help would be great
Click to expand...
Click to collapse
Same issue here.
Has someone solved?

Sorry guys/gals, I didn't manage to get it resolved. I ended up getting a Galaxy Nexus.

Another Bricked TF300

Hi, good people. I have bought a TF300T bricked last week, the old user has stock OS, tried to root and failed.
Now im fighting with that. When i turn on the tablet, it stuck at 'The Device is Unlocked' with Asus n' Nvidia Logo, after a minutes it reset and keeps in a constant loop.
I tried to recovery [vol down etc etc] and no effect, i tried with a few of tutorial and nothing.
I connected the tablet via APX [VOL UP + power]. PC recognized it but i stucked in this. Tried to fastboot and stays in 'waiting device'
Someone with ideas? Thanks frr all and sorry for the inconvenience.

AdvanceArg said:
Hi, good people. I have bought a TF300T bricked last week, the old user has stock OS, tried to root and failed.
Now im fighting with that. When i turn on the tablet, it stuck at 'The Device is Unlocked' with Asus n' Nvidia Logo, after a minutes it reset and keeps in a constant loop.
I tried to recovery [vol down etc etc] and no effect, i tried with a few of tutorial and nothing.
I connected the tablet via APX [VOL UP + power]. PC recognized it but i stucked in this. Tried to fastboot and stays in 'waiting device'
Someone with ideas? Thanks frr all and sorry for the inconvenience.
Click to expand...
Click to collapse
PC operating system?
Drivers for fastboot and adb loaded?
Look at my signature about universal naked drivers.
Also about getting into your bootloader menu.
APX will be useless to restore.

tobdaryl said:
PC operating system?
Drivers for fastboot and adb loaded?
Look at my signature about universal naked drivers.
Also about getting into your bootloader menu.
APX will be useless to restore.
Click to expand...
Click to collapse
W7 x64
Used exactly those naked drivers.
Cant access to bootloader.

AdvanceArg said:
W7 x64
Used exactly those naked drivers.
Cant access to bootloader.
Click to expand...
Click to collapse
Did you actually use the link to attempt the bootloader access?
Did the drivers properly install?
Do you have an sdcard for this tablet?

tobdaryl said:
Did you actually use the link to attempt the bootloader access?
Did the drivers properly install?
Do you have an sdcard for this tablet?
Click to expand...
Click to collapse
i installed ADB Interface Drivers, but i cant Android Bootloader Interface Driver because 'vol down + up + power' doesnt work.

AdvanceArg said:
i installed ADB Interface Drivers, but i cant Android Bootloader Interface Driver because 'vol down + up + power' doesnt work.
Click to expand...
Click to collapse
I'll assume that means all ten methods to get into the bootloader failed.
If the adb drivers installed we may have a chance.
You didn't say about the sdcard.
At the moment are you still stuck in apx or bootlooping.
Sorry but I need a place to begin.

tobdaryl said:
I'll assume that means all ten methods to get into the bootloader failed.
If the adb drivers installed we may have a chance.
You didn't say about the sdcard.
At the moment are you still stuck in apx or bootlooping.
Sorry but I need a place to begin.
Click to expand...
Click to collapse
i have a sd, it doesn't have info [isn't from tf300, it doesnt came with]. When i introduce it into eeepad i can't access the storage from windows.
I can only interact with the tablet when i turn it on with VOLUP + POWER then is when windows ask me for drivers, now i have installed ADB drivers.
sorry for all dude. And thanks.

AdvanceArg said:
i have a sd, it doesn't have info [isn't from tf300, it doesnt came with]. When i introduce it into eeepad i can't access the storage from windows.
I can only interact with the tablet when i turn it on with VOLUP + POWER then is when windows ask me for drivers, now i have installed ADB drivers.
sorry for all dude. And thanks.
Click to expand...
Click to collapse
No problem we just need to get a starting place and have as much in our favor as possible.
I don't believe adb works in apx mode but we'll give it a shot.
No sdcards come with the tablet.
Go into apx mode (volume + power).
Go to your adb folder with cmd and type
adb devices - press return or enter
If it is working we should get your serial number in return.
Now get out of apx mode.
type
adb devices - do not press return yet
watch your unit and when the screen goes black and before it lights(rebooting) now press return
Tell me what is returned each way.

tobdaryl said:
Go into apx mode (volume + power).
Go to your adb folder with cmd and type
adb devices - press return or enter
If it is working we should get your serial number in return.
Now get out of apx mode.
type
adb devices - do not press return yet
watch your unit and when the screen goes black and before it lights(rebooting) now press return
Tell me what is returned each way.
Click to expand...
Click to collapse
No serial. only ''List of devices attached''
Tried with Asus Trasnformer Prime APX Interface [naked drivers] and ADB drivers.

AdvanceArg said:
No serial. only ''List of devices attached''
Tried with Asus Trasnformer Prime APX Interface [naked drivers] and ADB drivers.
Click to expand...
Click to collapse
[FONT=TimesNewRomanPSMT, serif]Download 10.4.2.9 JB from this thread post #3[/FONT]
[FONT=TimesNewRomanPSMT, serif]unzip once and you should still have a zip if you get a blob then do not unzip.[/FONT]
[FONT=TimesNewRomanPSMT, serif]rename to EP201_768_SDUPDATE.zip and copy to sdcard and place sdcard into your tablet.[/FONT]
[FONT=TimesNewRomanPSMT, serif]Power tablet and hope![/FONT]

nothing. Renamed US_epad-user-10.4.2.9 to EP201_768_SDUPDATE.zip, throwed it into sd and turned tablet on. Stuck on ASUS logo.

AdvanceArg said:
nothing. Renamed US_epaduser_10_4_2_9_UpdateLauncher.zip to EP201_768_SDUPDATE.zip, throwed it into sd and turned tablet on. Stuck on ASUS logo.
Click to expand...
Click to collapse
I have some bad news for you.
Without adb or fastboot access I don't know of anything else to be done.
If you could have gotten into the bootloader menu we would have had a chance.
Maybe someone else will read this thread and have more ideas.
I'm sorry.
Good Luck!

same problem here. i have a tf300t and can only access apx interface.
I got into this mess, after by "accident" choosed the "wipe data" option present on the bootleader.
!! adb, fast boot do not work!! "power key + down button" dont do anything!
i'm getting a bit resteless because no matter were i search on the web i can not find anything suitable on how to resolve this issue...
there are some youtube videos that show a solution for tf100. it seems the same problem.
http://www.youtube.com/watch?v=CwvfNIHCYlQ
there is also a tool for tf100, called easy flasher. to bad it does not work for tf300t
http://forum.xda-developers.com/showthread.php?t=1688012
i think it is a question of seaching and waiting. someone will help and get or point to a solution. because if we google for tf300t bricked that are lots and lots of links stating this issue...
what a mess...

AdvanceArg said:
Hi, good people. I have bought a TF300T bricked last week, the old user has stock OS, tried to root and failed.
Now im fighting with that. When i turn on the tablet, it stuck at 'The Device is Unlocked' with Asus n' Nvidia Logo, after a minutes it reset and keeps in a constant loop.
I tried to recovery [vol down etc etc] and no effect, i tried with a few of tutorial and nothing.
I connected the tablet via APX [VOL UP + power]. PC recognized it but i stucked in this. Tried to fastboot and stays in 'waiting device'
Someone with ideas? Thanks frr all and sorry for the inconvenience.
Click to expand...
Click to collapse
Do you see anything after resetting by holding volume down and the power button? If you can get the tablet into fastboot mode you may able to revive it. If you can, ask the previous owner which version stock Android he was running before he tried to root it (it matters!).

This method worked for me!
Link to my thread ---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps guys. Good luck!

[Q] Softbricked after 4.3.3

Hey guys, semi-noob here. Here is the situation:
1) encrypted device yesterday (Nexus 5 w/ stock android 4.4.2 and CWM Recovery)
2) 4.4.3 came out, downloaded and installed (yee! new dialer)
3) restarted after install (so excited! :fingers-crossed
4) enter the bootloop
5) try to do fastboot -> recovery mode
6) nope. recovery mode = bootloop
What do, XDA? I searched the forums, and nothing seems to address this. The N5 isn't even showing up on the devices list for my comp (W7 w/ ADB installed and ran before). I can't talk to it through my computer.

haloux said:
Hey guys, semi-noob here. Here is the situation:
1) encrypted device yesterday (Nexus 5 w/ stock android 4.4.2 and CWM Recovery)
2) 4.4.3 came out, downloaded and installed (yee! new dialer)
3) restarted after install (so excited! :fingers-crossed
4) enter the bootloop
5) try to do fastboot -> recovery mode
6) nope. recovery mode = bootloop
What do, XDA? I searched the forums, and nothing seems to address this. The N5 isn't even showing up on the devices list for my comp (W7 w/ ADB installed and ran before). I can't talk to it through my computer.
Click to expand...
Click to collapse
Hi.
Boot into bootloader
open cmd
Type fastboot devices
See if your device gets detected or not.
If yes..you can flash stock factory IMG.
If not make sure u have installed the drivers and adb set up is there.
Sent from my Nexus 5 using XDA Free mobile app

Vivek_Neel said:
Hi.
Boot into bootloader
open cmd
Type fastboot devices
See if your device gets detected or not.
If yes..you can flash stock factory IMG.
If not make sure u have installed the drivers and adb set up is there.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
Thanks for the quick response.
Win7 doesn't even detect the N5. Device manager doesn't even show that it exists (as android device or anything else). I've unplugged and replugged, no sound, multiple different ports.

Whatever you do don't use a toolkit try and fix it.If something else happens trying to diagnosis it would be very hard.Manual installation and fixing is the Best. Plus you learn how to get out of jams.

habitformer said:
Whatever you do don't use a toolkit try and fix it.If something else happens trying to diagnosis it would be very hard.Manual installation and fixing is the Best. Plus you learn how to get out of jams.
Click to expand...
Click to collapse
Will do (or won't do?). Thank you for the advice. Any tips on how to get my system to recognize the device?

So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
Verified that ADB and all SDK software was up to date
Restarted computer to verify USB controller status
Refreshed device manager list before and after plugging in N5.
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.

haloux said:
So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
Verified that ADB and all SDK software was up to date
Restarted computer to verify USB controller status
Refreshed device manager list before and after plugging in N5.
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.
Click to expand...
Click to collapse
I swear I went through this 2 days ago @scarmon25 will tell,we had a late night hangouts session.
I used a one of my many nexus cables and it finally linked up.Not to sound like a jerk but you've got USB debugging on right?
I reread your OP.If.you can get into recovery just restore a back up!!! Than all should be good.

haloux said:
So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.
Click to expand...
Click to collapse
One thing you haven't stated. Do you have the fastboot drivers installed? They're different from adb. Since you're not seeing the device after "fastboot devices", I would check and make sure.

habitformer said:
I swear I went through this 2 days ago @scarmon25 will tell,we had a late night hangouts session.
I used a one of my many nexus cables and it finally linked up.Not to sound like a jerk but you've got USB debugging on right?
I reread your OP.If.you can get into recovery just restore a back up!!! Than all should be good.
Click to expand...
Click to collapse
Yea, USB debugging was on. The recovery mode just yields the dead android.
adrman said:
One thing you haven't stated. Do you have the fastboot drivers installed? They're different from adb. Since you're not seeing the device after "fastboot devices", I would check and make sure.
Click to expand...
Click to collapse
How would I verify that? I assumed that fastboot drivers were installed bc I used them in the past.
Code:
fastboot devices
(yields)
No devices found.

I would do a search here for "windows fastboot drivers". I can't be of much help to you as I haven't used windows for several years now. Also, if you have a working Android device, see if it shows up when connected in bootloader mode as a test.
Sent from my Nexus 5 using Tapatalk

Small breakthrough:
Used a diff cable like someone suggested and my device appeared. Updated device driver and fastboot driver. ADB devices still yields no device attached though.

haloux said:
Small breakthrough:
Used a diff cable like someone suggested and my device appeared. Updated device driver and fastboot driver. ADB devices still yields no device attached though.
Click to expand...
Click to collapse
if you are in fastboot mode (or bootloader) you should use the fastboot command and not the adb.
type: fastboot devices
any signs of life?
Tapatalk-kal küldve az én Nexus 5-el

bitdomo said:
if you are in fastboot mode (or bootloader) you should use the fastboot command and not the adb.
type: fastboot devices
any signs of life?
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Wow. It worked! The device showed up! Thank you guys.

haloux said:
Wow. It worked! The device showed up! Thank you guys.
Click to expand...
Click to collapse
Not sound like a turd but I mentioned using a nexus USB cable in post #7 after mentioning my issue.

Shield K1 Tablet isn't recognized by fastboot

Good afternoon everyone
I got my K1 for Christmas and I've been trying to root it for a few days but I can't get that far because I can't get the bootloader unlocked.
I've been following the guide based off of Nvidia's website
I've activated USB Debugging mode as seen here . Now once I've authorized the PC using the tablet. Once I run cmd in administrator mode I run
Code:
adb devices
I am able to get the serial and it says it's authorized. However if I go into Fastboot. if I check for devices it just goes back to the prompt, and if I try to run the unlock command it just gets stuck on <waiting for devices> (I've attached a screenshot here.)
At first I thought this was an issue with the OS/Drivers because I am on Win10 x64, and the shield drivers gave some error about driver incompatibility. So I loaded up a VM with win7 x32. However I am running into the exact same issue once I get to fastboot; the tablet just doesn't want to cooperate. I've booted into fastboot manually Where the options are:
Code:
[nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - locked
Continue
Fastboot Protocol
Recovery Mode
Restart
Poweroff
Nothing is recognized from there either. I've also tried multiple cables, since the Shield doesn't come with any. Anyways I've searched the older threads here for help but none of them have given me any luck. If there's something I can try I would definitely be open to hearing it and trying, I just don't know what the issue could be.
Thanks for your time everyone.

You have boot into the bootloader before being able to use fastboot. Just reboot your device and hold vol- during startup. The tablet will show some console messages, offering some options. If you see that screen, you can use fastboot.

bob3rt said:
Good afternoon everyone
I got my K1 for Christmas and I've been trying to root it for a few days but I can't get that far because I can't get the bootloader unlocked.
I've been following the guide based off of Nvidia's website
I've activated USB Debugging mode as seen here . Now once I've authorized the PC using the tablet. Once I run cmd in administrator mode I run
Code:
adb devices
I am able to get the serial and it says it's authorized. However if I go into Fastboot. if I check for devices it just goes back to the prompt, and if I try to run the unlock command it just gets stuck on <waiting for devices> (I've attached a screenshot here.)
At first I thought this was an issue with the OS/Drivers because I am on Win10 x64, and the shield drivers gave some error about driver incompatibility. So I loaded up a VM with win7 x32. However I am running into the exact same issue once I get to fastboot; the tablet just doesn't want to cooperate. I've booted into fastboot manually Where the options are:
Code:
[nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - locked
Continue
Fastboot Protocol
Recovery Mode
Restart
Poweroff
Nothing is recognized from there either. I've also tried multiple cables, since the Shield doesn't come with any. Anyways I've searched the older threads here for help but none of them have given me any luck. If there's something I can try I would definitely be open to hearing it and trying, I just don't know what the issue could be.
Thanks for your time everyone.
Click to expand...
Click to collapse
Adb works in normal mode.
Fastboot works in Bootloader mode.
Reboot to BL and type "fastboot devices", if no device go to K1 and select "fastboot protocol". Select on/yes.

dzidexx said:
Adb works in normal mode.
Fastboot works in Bootloader mode.
Reboot to BL and type "fastboot devices", if no device go to K1 and select "fastboot protocol". Select on/yes.
Click to expand...
Click to collapse
Hey there, sorry for my late reply, I've been swamped with work. I've tried your advice with no luck so far.
I can reboot to the bootloader, but when I select "fastboot protocol" I don't get to choose Select on/yes. it just refreshes the screen with the same options that I listed above. If you'd like when I get home I can provide a screenshot of my tablet so you can see the options, but I'm not getting anything like you described. Am I missing something?
Thank you for your time so far helping me.

Connect k1 to pc, type in cmd:
adb devices
adb reboot bootloader
fastboot devices
/Enable fastboot protocol on k1, type again/
fastboot devices
Give here screenshot from pc - all command/answers in cmd. @bob3rt

I had the same issue and lasted untill I tried different usb cable
Shield K1 connectivity is very sensible to cable quality
try others

dzidexx said:
Connect k1 to pc, type in cmd:
adb devices
adb reboot bootloader
fastboot devices
/Enable fastboot protocol on k1, type again/
fastboot devices
Give here screenshot from pc - all command/answers in cmd. @bob3rt
Click to expand...
Click to collapse
Hey Sorry again for a late response! However the good news is that I got it working!
What I ended up doing was hooking up the tablet to my Raspberry Pi with MATE and running adb/fastboot there. I originally ran into the same issue, but since I was able to sudo fastboot everything was recognized and seemed to work fine. I appreciate all of your help, and I apologize once again for the late replies!

For those that don't have a Raspberry Pi to follow the OP solution (like me), it's likely that your drivers aren't up to date on your PC.
Go here... https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
And follow the initial instructions in the introduction paragraph and get yourself NVIDIA CodeWorks for Android. Once downloaded and installed you'll then see the shield in your fastboot devices list.
:good:

0mad said:
For those that don't have a Raspberry Pi to follow the OP solution (like me), it's likely that your drivers aren't up to date on your PC.
Go here... https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
And follow the initial instructions in the introduction paragraph and get yourself NVIDIA CodeWorks for Android. Once downloaded and installed you'll then see the shield in your fastboot devices list.
:good:
Click to expand...
Click to collapse
Worked like a charm! Thanks.

Stuck on TWRP splash, windows cant see device.

if this has been asked before, i'm sorry, i have searched all over and no one seems to have my problem.
tablet boots to twrp splash, vol down and power does not work. i cant get it into any other modes because windows 10 does not see that it is connected.
i found a guide to inturupt twrp, but windows cant see my device.
tried dual booting windows 7, still cant see device
tried linux distro, adb still says no device found.
even with drivers installed in guessing that while in twrp splash it doesn't show up that there is a device connected.
is there anything i can do? or is it curtains for the ol' transformer?
thanks in advance.

Try booting to the fastboot screen before you boot into TWRP and see if the Windows 7 system can see the tablet, also what program are you using on the PC to access/flash the tablet? - NP

power and vol up don't do anything sadly, it still goes to the twrp splash screen.
I was using ADB on 10, 7 , and on the linux distro.

Try d/ling this Minimal ADB and Fastboot: https://forum.xda-developers.com/showthread.php?t=2317790 on a Windows 7 system and see if that will pick it up. - NP

still says no devices found. I think i really messed it up this time

kingkoopa85 said:
still says no devices found. I think i really messed it up this time
Click to expand...
Click to collapse
With it hooked up try sending it the reboot command and see if it responds. - NP
fastboot reboot

or fastboot reboot-bootloader

no luck, it says waiting for devices and it just sits there. i miss this tablet.
i think the problem is still that when stuck in twrp the computer doesnt recognize that its there, so I cant get the drivers installed to be able to run any commands.