Database Info

[HELP] Nexus S can't boot recovery

Hi all,
Been given a Nexus S i9023 by my brother who has been "tampering" with it and now it seems a bit messed up.
When booting up - it gets stuck on the "Google" screen with a padlock on it... I can get into fastboot and I can flash recovery but when I attempt to load any recovery - I get that same Google screen with the padlock! I've downloaded a stock rom and even flashed system etc via fastboot but that still gets me nowhere past the damn padlock!!
I've tried to "fastboot boot recovery.img" and I still get the Google screen with the padlock but it says "Fastboot status - OK" on the bottom left.
I've searched and searched but everyone just seems to give tips on how to flash recovery. I know how to flash recovery; it just seem to be going into it though! Could the internal memory be screwed?
Thanks for any advice!

Sounds strange for sure. You try from within the OS? Enable USB debugging and adb reboot recovery.
Doubt it will work but its worth a shot

albundy2010 said:
Sounds strange for sure. You try from within the OS? Enable USB debugging and adb reboot recovery.
Doubt it will work but its worth a shot
Click to expand...
Click to collapse
The phone stops at Google with the padlock on boot! Can't even get into the OS. Going to try to unbrick it and Odin but left my ubuntu laptop at my parents and can't be bothered to go get it... couldn't get it to work booting off cd rom. Kept giving me the "SBL Injection Failure Failed to find device" error booting ubuntu on a CD!

You may have a storage issue.
I seen you tried to flash system and boot recovery with fastboot ( which should have booted) but did you try to flash them all and wipe. The command is fastboot -w update file name.
I think Odin is a windows only tool anyways by the way.

albundy2010 said:
You may have a storage issue.
I seen you tried to flash system and boot recovery with fastboot ( which should have booted) but did you try to flash them all and wipe. The command is fastboot -w update file name.
I think Odin is a windows only tool anyways by the way.
Click to expand...
Click to collapse
No idea why I said Odin - I meant the unbrickable recovery thing.
I tried Odin with a Jig last night; got it into download mode and flashed with odin. Got the same result.
fastboot -w also gives the same issue...
If I have a storage issue - is there any way I can tell?

Basically you can tell by the issues you're having. Doing all the proper stuff to flash images etc and still having a booting/working device.
As far as a actual diagnostic tool I don't know of one. But it sure sounds like a hw issue to me.

I have the following problem: since a few weeks I'm unable to enter recovery.
This is what I do:
- shut down my phone
- press the power button while holding the volume up
- than I get a screen where I can choose from 4 options using the volume controls and selecting an option with the power button
- I select 'Recovery' and press the power button
- I get the usual black screen with Google logo and padlock
- but instead of getting into my recovery, I get a black screen with a Droid lying down, the 'chest' opened and some kind of small warning triangle above it..somebody who knows what I have to do??
Thanks in advance

Pironi90 said:
I have the following problem: since a few weeks I'm unable to enter recovery.
This is what I do:
- shut down my phone
- press the power button while holding the volume up
- than I get a screen where I can choose from 4 options using the volume controls and selecting an option with the power button
- I select 'Recovery' and press the power button
- I get the usual black screen with Google logo and padlock
- but instead of getting into my recovery, I get a black screen with a Droid lying down, the 'chest' opened and some kind of small warning triangle above it..somebody who knows what I have to do??
Thanks in advance
Click to expand...
Click to collapse
Reflash your recovery using fastboot.

polobunny said:
Reflash your recovery using fastboot.
Click to expand...
Click to collapse
And where can I find how to do this? I'm a total newbie for this kind of stuff and I found some hits on google (e.g. http://forum.xda-developers.com/showthread.php?t=1757146) but I'm actually a bit scared to damage my phone or something by doind something wrong or applying some method that's actually made for another device or so.. :s

Pironi90 said:
And where can I find how to do this? I'm a total newbie for this kind of stuff and I found some hits on google (e.g. http://forum.xda-developers.com/showthread.php?t=1757146) but I'm actually a bit scared to damage my phone or something by doind something wrong or applying some method that's actually made for another device or so.. :s
Click to expand...
Click to collapse
Flash custom recovery.img part
http://wiki.cyanogenmod.org/wiki/fastboot#Flash_Custom_Recovery.img
You need ADB (and ADB drivers installed, strongly recommend PDANet Android Drivers) and fastboot executable.
Custom recovery I suggest you use Clockworkmod Recovery.
I imagine your phone is already unlocked?

polobunny said:
I imagine your phone is already unlocked?
Click to expand...
Click to collapse
I think so yes, I could access recovery before if that's what you mean by unlocked

Pironi90 said:
I think so yes, I could access recovery before if that's what you mean by unlocked
Click to expand...
Click to collapse
When u boot on the Google screen on the bottom centre does it have a padlock? If so then it is unlocked.

You are entering recovery. Stock recovery
If you want a custom one either flash with fastboot or if you're rooted with a app. Goo manager. Rom manager etc.
Keep it mind that if you're on a stock ROM the custom recovery gets overwritten back to stock when the phone boots up the os
Q

UselessSniper001 said:
When u boot on the Google screen on the bottom centre does it have a padlock? If so then it is unlocked.
Click to expand...
Click to collapse
Then my phone is unlocked yes

polobunny said:
You need ADB (and ADB drivers installed, strongly recommend PDANet Android Drivers) and fastboot executable.
Custom recovery I suggest you use Clockworkmod Recovery.
I imagine your phone is already unlocked?
Click to expand...
Click to collapse
In installed the drivers and I installed the fastboot executable, but what do I have to do next? If I run the fastboot.exe, it just quickly shows a CMD-window and then disappears.
Edit:
I just discovered that, when I'm at the bootloader (I think it's called that way, the screen where you can select recovery), and I choose to reboot, I get the same 'error' as when I try to enter recovery.
Edit:
Alright, I was able to flash a new recovery, using cmd, but now when I try to enter my recovery, the phone gets stuck at a black screen with Google logo and padlock...

I have same problem as wolverine_2k who made the post. My nexus, can't start, I tried reboot and recovery but didn't work. After reboot or recovery I see Google logo, than Nexus screen and that is it. It didn't move to home screen and it stay with lighting screen all the time till I remove the battery. I can't power off it and don't know what to do. I can't transfer data with my PC (it don't recognize the device - only notice that "unknown device" is connected). Please any ideas?
P.S.: My English is not good, if someone answer do it simple please
Thanks!

[Q] HELP! I think i bricked my TF700 while installing Jelly bean.

Hi All,
i have unlocked bootloader, Rooted ICS
now i installed the latest JB update via the SD card method (renaming it to E201_768_SDUPDATE).
did the power+vol down method. intstalled it and reboot.
now all i get is this message coming up.
"The Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image"
and it gets stuck there at the ASUS screen.
i have tried to install the APX driver from universal driver 0.7 TF700, and all i get is unknown device in win7 device manager.
hence i cant get into NVflash or Fastboot.
is there anything else that i can do to unbrick this tablet.
are there any other drivers that i need to install in win7 x64 or it to recognize that it is an asus tablet.??

Looks like the JB update didn't write everything properly - you still have the old bootloader. You should really have created backups for nvflash before trying to upgrade to JB.
But it's still not too late. Can you switch yout device to fastboot mode? If yes, then it's just a matter of getting your PC configuration right.
Then the next thing I would do: re-flash some custom recovery via fastboot, make sure it works and you have adb root access, check if /sdcard is ok, then install the AndroidRoot bootloader to create your blobs for nvflash, reboot into recovery, pull the blobs to your PC via adb, and only then try to upgrade to JB again.

_that said:
Looks like the JB update didn't write everything properly - you still have the old bootloader. You should really have created backups for nvflash before trying to upgrade to JB.
But it's still not too late. Can you switch yout device to fastboot mode? If yes, then it's just a matter of getting your PC configuration right.
Then the next thing I would do: re-flash some custom recovery via fastboot, make sure it works and you have adb root access, check if /sdcard is ok, then install the AndroidRoot bootloader to create your blobs for nvflash, reboot into recovery, pull the blobs to your PC via adb, and only then try to upgrade to JB again.
Click to expand...
Click to collapse
Hi, no unfortunately i cant access fastboot, i have tried using the TWRP method of and all i get it a message saying waiting for device. when i try to push the TWRP.blob file.
i think my problem is that the usb device drivers are not working hence win7 x64 cant recognize the tablet when it is turned off (APX mode i believe)

dazzyd said:
Hi, no unfortunately i cant access fastboot, i have tried using the TWRP method of and all i get it a message saying waiting for device. when i try to push the TWRP.blob file.
Click to expand...
Click to collapse
Let's check it step by step:
- On the device, can you still activate the fastboot mode (USB icon)?
- On your PC, you should see a USB device with vendor ID 0b05 and product ID 4daf. Should be visible somewhere in Device Manager under Windows, maybe someone else can give you details (under Linux everything is much simpler with lsusb).
- On the PC, "fastboot devices" should give you more than no output at all (some question marks, AFAIR).

_that said:
Let's check it step by step:
- On the device, can you still activate the fastboot mode (USB icon)?
- On your PC, you should see a USB device with vendor ID 0b05 and product ID 4daf. Should be visible somewhere in Device Manager under Windows, maybe someone else can give you details (under Linux everything is much simpler with lsusb).
- On the PC, "fastboot devices" should give you more than no output at all (some question marks, AFAIR).
Click to expand...
Click to collapse
Hi again, no i cant see the usb icon,
i am only getting this Asus screen
the Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image"
and it gets stuck there at the ASUS screen.

dazzyd said:
and it gets stuck there at the ASUS screen.
Click to expand...
Click to collapse
And if you hold down Volume-down while powering on, it's the same? In that case, 3 icons should appear before it tries to start the recovery kernel.

_that said:
And if you hold down Volume-down while powering on, it's the same? In that case, 3 icons should appear before it tries to start the recovery kernel.
Click to expand...
Click to collapse
yes i have tried holding down the volume-down while power on and still nothing. no icons appear.

dazzyd said:
yes i have tried holding down the volume-down while power on and still nothing. no icons appear.
Click to expand...
Click to collapse
Sorry, then I am out of ideas.

dazzyd said:
Hi All,
i have unlocked bootloader, Rooted ICS
now i installed the latest JB update via the SD card method (renaming it to E201_768_SDUPDATE).
did the power+vol down method. intstalled it and reboot.
now all i get is this message coming up.
"The Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image"
and it gets stuck there at the ASUS screen.
i have tried to install the APX driver from universal driver 0.7 TF700, and all i get is unknown device in win7 device manager.
hence i cant get into NVflash or Fastboot.
is there anything else that i can do to unbrick this tablet.
are there any other drivers that i need to install in win7 x64 or it to recognize that it is an asus tablet.??
Click to expand...
Click to collapse
You're done. You need to send out for repair. Sorry, but I haven't see any one here able to recover the device with the above message.

buhohitr said:
You're done. You need to send out for repair. Sorry, but I haven't see any one here able to recover the device with the above message.
Click to expand...
Click to collapse
hmm bummer.. no other way to force install a device driver to detect the tablet on my win7 pc.? all i need is a glimmer of hope that i can still talk to the tablet at the lowest level interface. ie APX mode.

dazzyd said:
hmm bummer.. no other way to force install a device driver to detect the tablet on my win7 pc.? all i need is a glimmer of hope that i can still talk to the tablet at the lowest level interface. ie APX mode.
Click to expand...
Click to collapse
The driver on your PC is not the problem. For using nvflash in APX mode you'd need the Secure Boot Key, which is unique for each device and which Asus does not give us, or the blob for the wheelie tool that can be created with the AndroidBoot hacked bootloader, which is also unique for each device. But for creating this blob, you need working fastboot access.

[Q] ROM manager clockworkmod update bricked tf700

Hello there!
I have a TF700T pad, I installed free rom manager application, from within that application I chose to install clockworkmod recovery, the application loaded the clockworkmod recovery from the internet (there was an indicator on top of the application screen).
After finished, I rebooted into recovery, but it doesn't reboot to recovery, it loads android normally, then I tried to boot to recovery manually by pressing and holding the the power button along with the volume down button it loads nothing and stays there for ever!! I did this several times then it it changed and now it doesn't even load the android normally.
And when I boot into APX mode, the adb can't find it!
In short, I can't access recovery nor system!
When I try to boot to recovery
(power + volume down) It freezs and the following shows on the screen:
"The device is unlocked.
Android cardhu-user bootloader <2.10 e> release by "CN_epad-9.4.5.30-20120907" A03
Checking for android ota recovery
Booting recovery kernel image"
- I downloaded the firmware from ASUS and renamed it to "EP201_768_SDUPDATE" and copied to the root of a formated FAT32 micro SD card and tried to boot, but still freezing on above mentioned screen.
- The PC recognizes it (drivers are correct, i downloaded them and installed them) but the adb can not find the pad and tells me to install tap's specific drivers!
- I tried to flash the recovery image image.img through adb, but same problem, it stays there for ever showing the message "waiting for device".
Please, help me with a solution for that situation!
Thank you.

shreef said:
Hello there!
I have a TF700T pad, I installed free rom manager application, from within that application I chose to install clockworkmod recovery, the application loaded the clockworkmod recovery from the internet (there was an indicator on top of the application screen).
After finished, I rebooted into recovery, but it doesn't reboot to recovery, it loads android normally, then I tried to boot to recovery manually by pressing and holding the the power button along with the volume down button it loads nothing and stays there for ever!! I did this several times then it it changed and now it doesn't even load the android normally.
And when I boot into APX mode, the adb can't find it!
In short, I can't access recovery nor system!
When I try to boot to recovery
(power + volume down) It freezs and the following shows on the screen:
"The device is unlocked.
Android cardhu-user bootloader <2.10 e> release by "CN_epad-9.4.5.30-20120907" A03
Checking for android ota recovery
Booting recovery kernel image"
- I downloaded the firmware from ASUS and renamed it to "EP201_768_SDUPDATE" and copied to the root of a formated FAT32 micro SD card and tried to boot, but still freezing on above mentioned screen.
- The PC recognizes it (drivers are correct, i downloaded them and installed them) but the adb can not find the pad and tells me to install tap's specific drivers!
- I tried to flash the recovery image image.img through adb, but same problem, it stays there for ever showing the message "waiting for device".
Please, help me with a solution for that situation!
Thank you.
Click to expand...
Click to collapse
Do you have nvflash backup? if not, I believe you're done. You need to send out for repair.

Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!

shreef said:
Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!
Click to expand...
Click to collapse
I'm assuming you've unlocked the bootloader. Can you get the device into fastboot and push a new recovery through that?

shreef said:
Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!
Click to expand...
Click to collapse
ArmyAg08 said:
I'm assuming you've unlocked the bootloader. Can you get the device into fastboot and push a new recovery through that?
Click to expand...
Click to collapse
That would be the only remaining option, but ROM Manager is known to do this. If a user cannot even read on a forum before doing stuff, I'm not sure this is going to work out very well.
OK. I'll go back to my hermit cave now.

No, I can only boot in APX mode!
Isn't there any way we can make the adb reconize and access the PAD?
I can bring the recovery image and put in the root of the SD card, but what should I name it so the boot can reconize it and update? (the device says "checking for android ota recovery" !!

shreef said:
No, I can only boot in APX mode!
Isn't there any way we can make the adb reconize and access the PAD?
I can bring the recovery image and put in the root of the SD card, but what should I name it so the boot can reconize it and update? (the device says "checking for android ota recovery" !!
Click to expand...
Click to collapse
APX is NOT adb -- you need to issue commands using fastboot. Did you use the manufacturer's switch? "adb devices" won't return anything, even on a perfectly healthy 700. Take a look here:
http://forum.xda-developers.com/showthread.php?t=1926286
and don't forget to use that switch: -i 0x0B05, as in
fastboot -i 0x0B05 <command>
For example, fastboot -i 0x0B05 devices or fastboot -i 0x0B05 reboot
EDIT: APX = FASTBOOT, for clarity.

MartyHulskemper said:
That would be the only remaining option, but ROM Manager is known to do this. If a user cannot even read on a forum before doing stuff, I'm not sure this is going to work out very well.
OK. I'll go back to my hermit cave now.
Click to expand...
Click to collapse
I only asked because I thought ROM manager was known to brick this tablet if you tried to install a recovery with it. I may be mistaken though.
Sent from my ASUS Transformer Pad TF700T

MartyHulskemper said:
APX is NOT adb -- you need to issue commands using fastboot.
Click to expand...
Click to collapse
APX is also NOT fastboot - in APX mode you can *only* use nvflash, but for that you'd need to have created the blob before bricking.

I am sorry, I didn't really understand what you are trying to say!!
What does "manfacturer's switch" mean?
Also, what does APX = FASTBOOT ?

shreef said:
I am sorry, I didn't really understand what you are trying to say!!
What does "manfacturer's switch" mean?
Also, what does APX = FASTBOOT ?
Click to expand...
Click to collapse
shreef, the short answer is that only ASUS can help you now. I believe that is your only solution.
I'm so sorry.

OK, I have sent it to ASUS!
Thank you guys for your care and help.
Regards

ArmyAg08 said:
I only asked because I thought ROM manager was known to brick this tablet if you tried to install a recovery with it. I may be mistaken though.
Sent from my ASUS Transformer Pad TF700T
Click to expand...
Click to collapse
You're right. I wasn't mad/annoyed at your post. I just wanted to point out it has been known for a while now that ROM Manager does funky things on the 700. I'd just stay away from it -- iIn the sense that if one aspect of a program is broken by a device's particulars, changes are relatively high that some other aspect(s) is/are broken as well and you might get to know which one(s) that is/are by first-hand experience.
_that said:
APX is also NOT fastboot - in APX mode you can *only* use nvflash, but for that you'd need to have created the blob before bricking.
Click to expand...
Click to collapse
You're right. I was cutting the curve. I'm sorry for the confusion.
okantomi said:
shreef, the short answer is that only ASUS can help you now. I believe that is your only solution.
I'm so sorry.
Click to expand...
Click to collapse
That is quite the accurate summary.
@OP: hope ASUS treats your device nicely and you can get back in our midst with a 700 working well for you, soon.

Bricked my tf300t?

To sum everything up:
1. My rom didn't work so I decided to find a new one :good:
2. I read and understand that it's much easier using fastboot
3. I was flashing the official rom when the antivirus requested a reboot
4. I forgot the flashing, and just clicked on reboot :silly: :crying:
The screen remains black when I try to boot it up :crying:
The only sign of life is when I'm charging the light is lighting and "APX" is showing in the device manager on pc with a yellow triangle, I haven't understand what "APX" stand for yet so please explain
(My bootloader was unlocked and I flashed twrp 2.5.5 just before I did this)
Do you have any tips for me? Or is the device bricked and have to be sent for service?
Please help me :fingers-crossed:
Edit: This is wrong section I know, can anyone move it to the Q&A please?

Moved.

mathiash98 said:
To sum everything up:
1. My rom didn't work so I decided to find a new one :good:
2. I read and understand that it's much easier using fastboot
3. I was flashing the official rom when the antivirus requested a reboot
4. I forgot the flashing, and just clicked on reboot :silly: :crying:
The screen remains black when I try to boot it up :crying:
The only sign of life is when I'm charging the light is lighting and "APX" is showing in the device manager on pc with a yellow triangle, I haven't understand what "APX" stand for yet so please explain
(My bootloader was unlocked and I flashed twrp 2.5.5 just before I did this)
Do you have any tips for me? Or is the device bricked and have to be sent for service?
Please help me :fingers-crossed:
Edit: This is wrong section I know, can anyone move it to the Q&A please?
Click to expand...
Click to collapse
Apx is a method provided by the cpu manufacture for recovery. Due to the way asus has handled locking the unit apx is only available if nvflash is installed while on ICS (4.0).
Reset may be a good option for you. Power on unit. Hold volume down and insert a small paperclip to into into the reset hole. This may get you into the bootloader.
Reset: A small hole about 25mm or 1inch below the sdcard slot.
Note: If this fails you could do the same but hold volume up and hope.
Beyond this running the battery down has worked for some or remove the back cover and disconnect the battery. Leave it disconnected for thirty minutes, then reconnect.
Also see my signature for other methods to get into the bootloader. Don't bother with apx as it is useless for us.
We are looking for any change in the unit. With a change may come use of adb, fastboot, or recovery.
Try do each thing in turn and repeat this sequence twice more.

Thanks for the explanation and fir the tips! I'm going to try this

mathiash98 said:
Thanks for the explanation and fir the tips! I'm going to try this
Click to expand...
Click to collapse
Good Luck!

tobdaryl said:
Good Luck!
Click to expand...
Click to collapse
It doesn't seem that any of the following work, but I haven't tried the battery pull thing, because I see that it's a sticker over the cover that says that the warrenty is void if removed. If I send it for service will the guys know that I have unlocked it, and then void the warranty?

mathiash98 said:
It doesn't seem that any of the following work, but I haven't tried the battery pull thing, because I see that it's a sticker over the cover that says that the warrenty is void if removed. If I send it for service will the guys know that I have unlocked it, and then void the warranty?
Click to expand...
Click to collapse
I understand. If still in warranty I wouldn't remove it either.
I'm sorry that is all I have for your situation.

Lads, let me join your conversation. I've almost same problem, probably different root cause, but same summary:
1. Originally I downloaded JB 4.2 from support.asus.com source
2. Tablet got reflashed & worked as normal, but I lost roots which I had earlier, therefore I decided to get root privs again.
3. So, I went into TWRP web-site & downloaded openrecovery-twrp-2.5.0.0-tf300tg-JB.blob blob file & via ADB was able to flash TWRP 2.5 onto my TF300T, but...
4. ...somehow TWRP doesn't let me to mount neither system, not SD-card, nothing. And currently
5. I think I'm bricked (& my TF300T too). When I press power button - tablet switches on & gets straight into TWRP, where I've only option to power it down or reboot TWRP tells me "are you sure? No OS installed".
6. When I try to switch tablet into bootload (with volume -) writing "The Device is Unlocked" shortly blinks slightly brighter, kind of trying to get into bootloader, but gets into TWRP anyway.
Any help, please! I know how Donate button works!
P.S. Because I very new writer (but really old reader) of XDA - I can't incert outside links...

goldenval said:
Lads, let me join your conversation. I've almost same problem, probably different root cause, but same summary:
1. Originally I downloaded JB 4.2 from support.asus.com source
2. Tablet got reflashed & worked as normal, but I lost roots which I had earlier, therefore I decided to get root privs again.
3. So, I went into TWRP web-site & downloaded openrecovery-twrp-2.5.0.0-tf300tg-JB.blob blob file & via ADB was able to flash TWRP 2.5 onto my TF300T, but...
4. ...somehow TWRP doesn't let me to mount neither system, not SD-card, nothing. And currently
5. I think I'm bricked (& my TF300T too). When I press power button - tablet switches on & gets straight into TWRP, where I've only option to power it down or reboot TWRP tells me "are you sure? No OS installed".
6. When I try to switch tablet into bootload (with volume -) writing "The Device is Unlocked" shortly blinks slightly brighter, kind of trying to get into bootloader, but gets into TWRP anyway.
Any help, please! I know how Donate button works!
P.S. Because I very new writer (but really old reader) of XDA - I can't incert outside links...
Click to expand...
Click to collapse
Which tablet do you have? You show TF300T but using TF300TG twrp.
The bootloader changed again with 4.2 firmware and requires twrp especially for that version. I have been told the openrecovery-twrp-2.5.0.0-tf300t-4.2.blob does not work properly so you should have used openrecovery-twrp-2.4.4.0-tf300t-4.2.blob if you have a tf300t.
We need to break the cycle of going into twrp and only twrp.
Let's try to use twrp for that purpose. While in twrp select reboot while holding volume down.
If that fails to make a change while in twrp type adb reboot bootloader.
If that makes no change type fastboot -i 0x0B05 reboot-bootloader.
If there is still no change try the reset while holding volume down.
Reset: A small hole about 25mm or 1inch below the sdcard slot. Use a small paperclip to insert into the hole and press gently while holding volume down.

Dear Friend! :good: That what makes difference between you - old member & me - amatuer. Yes, I loaded ...TG version of TWRP onto my ..T tablet. Bad words aren't allowed in XDA forum, otherwise I'd call myself with proper name. Anyway,
I tried to reboot from TWRP, held volume - & had no success. It loaded into TWRP again.
Then tried to reboot with command adb reboot bootloader, as you mentioned - my Windows7 PC doesn't see tablet, showing Transformer with yellow ! sign. And I tried fastboot -i 0x0B05 reboot-bootloader command, ADB is saying <waiting for device> forever & nothing happens. so I stopped here so far, waiting for your advise...
We need to break the cycle of going into twrp and only twrp.
Let's try to use twrp for that purpose. While in twrp select reboot while holding volume down.
If that fails to make a change while in twrp type adb reboot bootloader.
If that makes no change type fastboot -i 0x0B05 reboot-bootloader.
If there is still no change try the reset while holding volume down.
Reset: A small hole about 25mm or 1inch below the sdcard slot. Use a small paperclip to insert into the hole and press gently while holding volume down.

No bad words needed. We all make mistakes. I them pointed out for future reference in case you were not aware.
First you need to get your drivers loaded for windows.
[GUIDE] How to install Universal Naked Drivers
Use that guide to get your drivers properly installed and retry the adb and fastboot commands.
goldenval said:
Dear Friend! :good: That what makes difference between you - old member & me - amatuer. Yes, I loaded ...TG version of TWRP onto my ..T tablet. Bad words aren't allowed in XDA forum, otherwise I'd call myself with proper name. Anyway,
I tried to reboot from TWRP, held volume - & had no success. It loaded into TWRP again.
Then tried to reboot with command adb reboot bootloader, as you mentioned - my Windows7 PC doesn't see tablet, showing Transformer with yellow ! sign. And I tried fastboot -i 0x0B05 reboot-bootloader command, ADB is saying <waiting for device> forever & nothing happens. so I stopped here so far, waiting for your advise...
We need to break the cycle of going into twrp and only twrp.
Let's try to use twrp for that purpose. While in twrp select reboot while holding volume down.
If that fails to make a change while in twrp type adb reboot bootloader.
If that makes no change type fastboot -i 0x0B05 reboot-bootloader.
If there is still no change try the reset while holding volume down.
Reset: A small hole about 25mm or 1inch below the sdcard slot. Use a small paperclip to insert into the hole and press gently while holding volume down.
Click to expand...
Click to collapse

Ok...
So, I bricked my tf300t. I ordered a new motherboard off ebay and replaced the bricked one. It works, but it was not factory reset and still has the owners info, etc. It is password protected. I don't know the pw. When I try to boot into the recovery console, I get a dead android. Going into the menu, I have an option to wipe or boot android. How do I get around this?

n3tm0nk said:
So, I bricked my tf300t. I ordered a new motherboard off ebay and replaced the bricked one. It works, but it was not factory reset and still has the owners info, etc. It is password protected. I don't know the pw. When I try to boot into the recovery console, I get a dead android. Going into the menu, I have an option to wipe or boot android. How do I get around this?
Click to expand...
Click to collapse
My suggestion is use stock recovery to replace the encrypted os (probably JB 4.2) with JB 4.1 (10.4.2.20). You can download here [INDEX]25 Apr 2013 - TF300T/TG WITH ALL ASUS ORIGINAL TOOLS-Firmwares-Kernels-Guides-. Look in firmware TF300T. Use the proper sku (ww, us, etc) for your country. Please give philos64 a thanks while there he spent much time creating that post, supporting the downloads, and updating.
Unzip the downloaded file once - rename to EP201_768_SDUPDATE.zip. Place the file on your internal sdcard if possible if not place on your micro sdcard. Boot into the recovery console and make the hungry android happy. This will probably take ten plus minutes.

Dear tobdaryl! Thanks very much for your advice, I had to dissapear for couple of days, so couldn't answer. I followed your link & had no success. When I power on TF300T & connect it to PC, it's being read as Transformer (see my 1st picture), unlike in the guide they are working with Asus Eee pad device (my 2nd picture), so when I'm trying to install drivers from un-zipped folder it says "...couldn't install drivers for your Transformer".
Looking for more help... (
tobdaryl said:
No bad words needed. We all make mistakes. I them pointed out for future reference in case you were not aware.
First you need to get your drivers loaded for windows.
[GUIDE] How to install Universal Naked Drivers
Use that guide to get your drivers properly installed and retry the adb and fastboot commands.
Click to expand...
Click to collapse

goldenval said:
Dear tobdaryl! Thanks very much for your advice, I had to dissapear for couple of days, so couldn't answer. I followed your link & had no success. When I power on TF300T & connect it to PC, it's being read as Transformer (see my 1st picture), unlike in the guide they are working with Asus Eee pad device (my 2nd picture), so when I'm trying to install drivers from un-zipped folder it says "...couldn't install drivers for your Transformer".
Looking for more help... (
Click to expand...
Click to collapse
Right click on the Transformer with the yellow symbol and point to your Universal Naked Drivers inf file. If one inf files fails to install then try the other.

tobdaryl said:
Right click on the Transformer with the yellow symbol and point to your Universal Naked Drivers inf file. If one inf files fails to install then try the other.
Click to expand...
Click to collapse
Tobdaryl, I couldn't find "Donate Me" button in your profile, so give me your paypal account for a little present please! :good: It worked!!! I installed correct driver from given guide, rebooted into bootloader, using ADB comand & got 3 icons: RCK, Android & Wipe Data. I tried Wipe Data, it said "can't mount something", don't remember now what. I rebooted again & clicked on Android & loaded into normal screen. Because of Asus became completely flat I put it on charge now. And after that I will have to come back to original task - to root my TF300T. While it's charging I downloaded Goo manager & tried to install TWRP, it said "No recoveries were found for your device", but in same time file for my device (that's where I made mistake, downloading TF300TG version) does exist, so what's story here? I guess this is may be because my TF300T isn't rooted yet?
Adding later. after digging this & other forums I found that in order to get root & have to have CWM/TWRP on my device & I can't get them until my TF300T is rooted. Am I confused & talking rubbish?
Adding 2 hours later. I rooted the device using XDA guide. Still trouble to reboot device. It always reboots into TWRP, then I have to connect it to PC & reboot with ADB commands. This isn't right...

goldenval said:
Tobdaryl, I couldn't find "Donate Me" button in your profile, so give me your paypal account for a little present please! :good: It worked!!! I installed correct driver from given guide, rebooted into bootloader, using ADB comand & got 3 icons: RCK, Android & Wipe Data. I tried Wipe Data, it said "can't mount something", don't remember now what. I rebooted again & clicked on Android & loaded into normal screen. Because of Asus became completely flat I put it on charge now. And after that I will have to come back to original task - to root my TF300T. While it's charging I downloaded Goo manager & tried to install TWRP, it said "No recoveries were found for your device", but in same time file for my device (that's where I made mistake, downloading TF300TG version) does exist, so what's story here? I guess this is may be because my TF300T isn't rooted yet?
Adding later. after digging this & other forums I found that in order to get root & have to have CWM/TWRP on my device & I can't get them until my TF300T is rooted. Am I confused & talking rubbish?
Adding 2 hours later. I rooted the device using XDA guide. Still trouble to reboot device. It always reboots into TWRP, then I have to connect it to PC & reboot with ADB commands. This isn't right...
Click to expand...
Click to collapse
Go manager does not have the proper twrp for our tablet.
Rooting is no longer required to flash twrp. Motochopper will root with just adb.
I suggest we try to get everything working properly with stock before changing or adding anything.
Go to to this link and download the stock Asus firmware 10.4.2.20. Choose the proper sku for your location (ww, us or whatever). Don't forget to thank philos64 while there. Unzip once and place on your tablet, flash with twrp, if that fails unzip again and place the blob file in the directory with adb and fastboot and flash with fastboot. Verify everything works properly before making any other changes.
Thank you for the donation offer.
I don't have a method to receive donations. A simple click on thanks will be good.

My problem is that because I installed wrong TWRP by mistake - it can't mount anything & I can't install anything from SD or internal memory. So, should I delete existing TWRP somehow &/or replace it by CWM recovery?
tobdaryl said:
Unzip once and place on your tablet, flash with twrp, if that fails unzip again and place the blob file in the directory with adb and fastboot and flash with fastboot
Click to expand...
Click to collapse

goldenval said:
My problem is that because I installed wrong TWRP by mistake - it can't mount anything & I can't install anything from SD or internal memory. So, should I delete existing TWRP somehow &/or replace it by CWM recovery?
Click to expand...
Click to collapse
No don't delete twrp or install cwm. We should have access to adb and or fastboot. We should be able to use either to get sorted.
Go to to this link and download the stock Asus firmware 10.4.2.20. Choose the proper sku for your location (ww, us or whatever). Don't forget to thank philos64 while there. Unzip twice and place the blob file in the directory with adb and fastboot and flash with adb. Verify everything works properly before making any other changes.
adb push blob /sdcard/blob
adb shell
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
exit
adb reboot

May I ask you then? My ROM number is: JOP40D.WW_epad-10.6.1.15.3-20130416 & as I can see from numbers you are offerring me to downgrade (from 4.2 to 4.1). Will this not kill the device? And why can't we re-install existing ROM through ADB? I'm not arguing, just trying to understand.
tobdaryl said:
No don't delete twrp or install cwm. We should have access to adb and or fastboot. We should be able to use either to get sorted.
Go to to this link and download the stock Asus firmware 10.4.2.20. Choose the proper sku for your location (ww, us or whatever). Don't forget to thank philos64 while there. Unzip twice and place the blob file in the directory with adb and fastboot and flash with adb. Verify everything works properly before making any other changes.
adb push blob /sdcard/blob
adb shell
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
exit
adb reboot
Click to expand...
Click to collapse

I somehow broke TWRP

I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.

mattlokk said:
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
Click to expand...
Click to collapse
Did you set:
Allow oem unlock in dev opt.
Fastboot protocol into BL?
Twrp app & manager need root to work.

Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link

thanks for the help, i'll try and work through this soon.

fpozar said:
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
Click to expand...
Click to collapse
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.

mattlokk said:
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
Click to expand...
Click to collapse
Okay so I'm guessing you have stock ROM.
To flash TWRP you have to enter fastboot mode (vol down + power I believe) and flash the twrp image with fastboot flash recovery twrp.img (rename the shield tablet twrp to just twrp.img and place it into your easy adb and fastboot folder)
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck

fpozar said:
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
Click to expand...
Click to collapse
Agreed. This is probably what is happening (as described on the TWRP webpage here:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Alternately, immediately rooting (flash SuperSU or Magisk) right after flashing TWRP, will prevent TWRP from being replaced with stock recovery.
Although the inconsistent fastboot connection, and how much trouble you had flashing TWRP initially, is a bit worrisome. Try using a different cable (maybe the one you are using is not connecting well?) try another USB port on the computer, and don't use a USB hub (connect direct to the PC).

Well, like they say: persistence is key. I kept pushing and trying new things until eventually.... I bricked the device. No, not really, it's working great now on LineageOS.
Thanks again to everyone who helped me out :good:. I'm still not sure exactly what caused TWRP to stop working on my device, however following this guide helped me fix it: https://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
The "flash-all.bat" restored everything to stock (including the recovery mode) and after that I was able to flash the latest TWRP and install Lineage.