Database Info

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!

Device not being detected in recovery mode?

I'm trying to install the 4.4.1 update but my device isn't being detected in recovery mode and thus adb sideload is not working. Would really appreciate some help. I've tried almost every solution that I've googled and nothing seems to be working.

I had a similar issue. Found the naked drivers and they seemed to work after uninstalling the other drivers and rebooting my PC.
Sent from my Nexus 5 using xda app-developers app

jkimbro said:
I had a similar issue. Found the naked drivers and they seemed to work after uninstalling the other drivers and rebooting my PC.
Click to expand...
Click to collapse
Any chance you could post those drivers? Mine works fine, but it would certainly help others if you could post them, or at least post a link to where you found them.

You just need the Google drivers from their website:
http://developer.android.com/sdk/win-usb.html

I had to force the installation of the drivers for the "AOSP on Hammerhead" device in the device manager.
I couldn't even get the device to show until I pressed VolUp in recovery and selected the ADB option in the recovery.
I used USB ADB Composite Interface or something like that by pointing the device manager's Update Driver dialog to the USB drivers from the SDK that EddyOS pointed at.
Windows 7 x64

Yep, had issues with my work PC (Win 7 Pro x64) - had to manually point Device Manager to the android_winusb.inf so it would find the drivers. Bit of a ballache but all working after that!

greenkabbage said:
I couldn't even get the device to show until I pressed VolUp in recovery and selected the ADB option in the recovery.
Click to expand...
Click to collapse
ADB isn't enabled on stock recovery, and sideload is not the same thing. From Google's POV, ADB access on recovery would be a heavy security risk, since you can still access recovery even with your bootloader locked. That's why they created sideloading.
a hammerhead wrote this.

beekay201 said:
ADB isn't enabled on stock recovery, and sideload is not the same thing. From Google's POV, ADB access on recovery would be a heavy security risk, since you can still access recovery even with your bootloader locked. That's why they created sideloading.
Click to expand...
Click to collapse
ADB Server may not be enabled, but ADB obviously is, otherwise you wouldn't be able to connect in order to Sideload, which you can certainly do with stock recovery (even with a locked bootloader). Also, if ADB wasn't available on the device, it wouldn't show up with the "ADB Devices" command.
Now, maybe you mean it's not available once you boot into recovery until you select "apply update from ADB." That may be true (not sure), but that's not what I got from your statement.

jt3 said:
Any chance you could post those drivers? Mine works fine, but it would certainly help others if you could post them, or at least post a link to where you found them.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2513339

jt3 said:
ADB Server may not be enabled, but ADB obviously is, otherwise you wouldn't be able to connect in order to Sideload, which you can certainly do with stock recovery (even with a locked bootloader). Also, if ADB wasn't available on the device, it wouldn't show up with the "ADB Devices" command.
Now, maybe you mean it's not available once you boot into recovery until you select "apply update from ADB." That may be true (not sure), but that's not what I got from your statement.
Click to expand...
Click to collapse
Try it. Select "apply update from ADB", and then try to get a ADB prompt like you would normally, you know, ls /sdcard/, something.

[Q] Can't get ADB to recognize my device

When I plug my device into my computer, run an ADB command window and type "adb devices", my phone isn't recognized. I'm running 5.0 right now, but I switched back to a sense based ROM and it still isn't recognized. I looked online and it said to check if the correct drivers are installed, but when I plug my phone in nothing happens and I'm not sure where to check to see if they're installed or not. I'm trying to figure this out so I can flash the newer 4.4.4 or 5.0 firmware, but I can't if my device isn't recognized. Thanks so much, I really appreciate it!

tannerrblake said:
When I plug my device into my computer, run an ADB command window and type "adb devices", my phone isn't recognized. I'm running 5.0 right now, but I switched back to a sense based ROM and it still isn't recognized. I looked online and it said to check if the correct drivers are installed, but when I plug my phone in nothing happens and I'm not sure where to check to see if they're installed or not. I'm trying to figure this out so I can flash the newer 4.4.4 or 5.0 firmware, but I can't if my device isn't recognized. Thanks so much, I really appreciate it!
Click to expand...
Click to collapse
I assume that you are using Windows?
Click on Start\All Programs\HTC and you should see HTC Driver in there.
Have you tried a different USB cable?

jsaxon2 said:
I assume that you are using Windows?
Click on Start\All Programs\HTC and you should see HTC Driver in there.
Have you tried a different USB cable?
Click to expand...
Click to collapse
I haven't tried a new cable, I don't have any others with me unfortunately. I see the HTC driver folder, it looks to me like the drivers are installed, but I'm still not sure. I'm running Windows 8.1
Also, how can I check which firmware I'm currently running?

tannerrblake said:
I haven't tried a new cable, I don't have any others with me unfortunately. I see the HTC driver folder, it looks to me like the drivers are installed, but I'm still not sure. I'm running Windows 8.1
Also, how can I check which firmware I'm currently running?
Click to expand...
Click to collapse
You need to go into the bootloader to see your firmware version.
Hold Power + Vol Up and as soon as the screen goes off, slide your finger down to Vol Down while still holding Power.

jsaxon2 said:
You need to go into the bootloader to see your firmware version.
Hold Power + Vol Up and as soon as the screen goes off, slide your finger down to Vol Down while still holding Power.
Click to expand...
Click to collapse
I did that, but I still don't know how to comprehend all the stuff on that screen. Which one of the lines in the firmware version? I still can't get ADB to recognize my device, I'm starting to get frustrated haha. I've tried multiple ROM backups that I have, I uninstalled HTC Sync Manager and installed it again, I can't get anything to work. Anyone have any more suggestions?

its the drivers
From time to time my computer doesn't like to bring up the drivers when I plug mine in. The driver is definitely the issue though. Make sure the drivers are installed, then plug your phone in and restart your machine. It might find your phone at boot. It's worked for me a few times.

tannerrblake said:
I did that, but I still don't know how to comprehend all the stuff on that screen. Which one of the lines in the firmware version? I still can't get ADB to recognize my device, I'm starting to get frustrated haha. I've tried multiple ROM backups that I have, I uninstalled HTC Sync Manager and installed it again, I can't get anything to work. Anyone have any more suggestions?
Click to expand...
Click to collapse
Do you have USB debug enabled on your phone?

damn straight its the drivers
Uninstall all the drivers you have to do with your phone right now. Then follow this tutorial.
/watch?v=afrvSGiMAtk
It's on YouTube but I can't post links
I was at the same exact spot yesterday but I followed this guy's instructions now I'm s off rooted and unlocked
Good Luck

TF700 - unrecoverable botloader error

Hello
I need help with my TF700.
I had this tablet for some time. It was unlocked with TWRP and ZOMBI-POP.
Last week I wanted to upgrade it for KIT-Kass 7.1
I wanted to update my TWRP for kang wersion ( 2.8.7.4) through TWRP and during the process it rebooted.
Then I've got a bootloop on normal starting. I can't get into recovery mode through power + vol up - tablet has no respond for that
I can only go to fastboot through power + vol down but when I connect it to windows with adb drivers or to linux(FWUL) it sees no device and no respond for any command.
Do You have any idea what to do ?
Thank You in advance

Sorry to say this but, if you can't send it commands then you are most likely hard bricked. What OS are you running on the computer with fastboot on it? - NP

Nektopoli said:
Sorry to say this but, if you can't send it commands then you are most likely hard bricked. What OS are you running on the computer with fastboot on it? - NP
Click to expand...
Click to collapse
This sounds not so good. I use windows 10 but as I said also I used FWUL to try.

marmacapp said:
This sounds not so good. I use windows 10 but as I said also I used FWUL to try.
Click to expand...
Click to collapse
Do you have access to a Windows 7 computer/laptop. There's an issue with Windows 10 and the fastboot drivers not working together, and causing a problem like yours. - NP

marmacapp said:
This sounds not so good. I use windows 10 but as I said also I used FWUL to try.
Click to expand...
Click to collapse
Found this in another thread, windows 10 fix. - NP
"I used Windows 10 and had to disable driver signature enforcement. Once I did this the PC recognized the tab without issue. "
To disable;
http://www.thewindowsclub.com/disable-driver-signature-enforcement-windows

Thank You for the info, but I have laptop with Windows7 and still the same.
But if I have text on screen like this Starting fastboot USB download protocol can the device still be hard-bricked ?
Maybe I am missing some drivers ?

I would d/l Minimal ADB and Fastboot from here;
https://forum.xda-developers.com/showthread.php?t=2317790
and Universal_Naked_Driver_0.72 here; - NP
https://forum.xda-developers.com/showthread.php?t=2263822

For now the problem is I can not install the "naked driver" because devices manager can not see TF700 when it is connected, so I can't update the driver

Have you tried sending the [fastboot reboot] command to see if the tablet will reboot. When I bricked my TF201t my laptop didn't see it but it still took the commands allowing me to wipe the recovery partition and install the correct TWRP. - NP

Dear Guys
I know that this topic is quite old, but I am still fighting with this problem.
I tryied different drivers, 3 different computers ( two with windows 10 one with windows 7) and I can;t connect to fastboot.
The tablet is in this mode, but when I will use adb and type any command like fastboot reboot - it displays "waiting for device"
Do You have any idea what else can I try ?
Best regards

Hi,
me too! I was using it at lunch - no problem. Got home and turned it on and unrecoverable bootloader error.

Mi unlock tool issue

Hi,
I have faced a problem trying to unlock my bootloader.
On the Mi unlock tool I have pressed the button "unlock". after one week the time required passed, but opening the app on the PC and connecting the phone in fastboot mode anything happens! You can see attached a capture of my PC screen with the phone connected in fastboot mode.
How I can fix it?
Thanks

Is this Windows? Does the OS see the device? (Check "My Computer".) Are the correct drivers installed?
If not, click the cog wheel and install driver, then reboot.

pnin said:
Is this Windows? Does the OS see the device? (Check "My Computer".) Are the correct drivers installed?
If not, click the cog wheel and install driver, then reboot.
Click to expand...
Click to collapse
Yes, it is Windows. not in fastboot mode the computer see my phone. in fastboot mode no.on the unlock tool the refresh and unlock buttons seem to be frozen.
How I can install the driver? on the cogwheel I can see only this (picture attached)...
It is really strange, why one week ago everything was ok? same computer, same phone of course!

In my experience, it's normal to not have any button feedback when the device is in fastboot mode -- only long-press power button to shutdown.
Sorry, can't help you on the rest, never faced this myself.
This is what comes up on the cog in the version I have (just pressed check to install the "drive", before rebooting the phone into fastboot)...

It is really frustrating this.
Any piece of advice?

Hi. I know it might sound silly but have you tried a different USB port on your PC? Preferably a USB 2.0 port.

finally done!
mybe the cable not working I don't know why!
Thanks