Hi, everybody, I am having problems with my nvidia shield tablet, it seems that after I had updated to android 6.0 I lost my custom recovery, and the original recovery is not there. Therefore I cannot update to 6.0.1, i cannot root, and my computer does not recognize the tablet when i go into the bootloader. Please help!
Are you able to turn off the tablet and use the volume keys to get into bootloader/fastboot mode? You can fastboot flash recovery from there.
Sent from my Nexus 6 using XDA-Developers mobile app
Are you able to turn off the tablet and use the volume keys to get into bootloader/fastboot mode? You can fastboot flash recovery from there.
Sorry it took so long to reply, yes, I can get into the boot loader. I can even fastboot, but my computer can't seem to communicate to my tablet once its in Fastboot/bootloader so every time I try to do as you said. My computer can't send the commands because it doesn't recognize the tablet.
Update drivers
I also lost twrp and root after the full OTA update. I tried to fastboot flash recovery back, but when I reboot into recovery it says "no command". How can I fix this? Its seems as if the recovery partition is gone? Thanks for any help.
That is stock recovery
lafester said:
That is stock recovery
Click to expand...
Click to collapse
How can I get TWRP to flash then? I am getting this:
Code:
sudo ./fastboot flash recovery recovery.img
[sudo] password:
target reported max download size of 100663296 bytes
sending 'recovery' (7228 KB)...
OKAY [ 0.353s]
writing 'recovery'...
OKAY [ 0.334s]
finished. total time: 0.687s
It finishes too fast to actually do anything. I have tried both 3.0.0 and 3.0.2 twrp for MM. I would appreciate any suggestions on how to fix this. Thanks.
You renamed twrp to recovery? If so you did flash it. Do you reboot directly into recovery?
Sent from my SHIELD Tablet using Tapatalk
Yes I renamed it to recovery.img and rebooted. When I reboot to recovery, it still just says no command.
Are you unlocked?
Yes boot loader shows unlocked
Latest twrp?
Related
Before I updated to 4.4.3 I was able to boot into TWRP by using the fastboot commands:
fastboot boot twrp.img
It would automatically reboot the phone into TWRP where I could flash SuperSU yet retain stock recovery.
Now when I attempt to do the very same thing on 4.4.3 I get:
downloading 'boot.img'...
OKAY [ 1.320s]
booting...
OKAY [ 0.402s]
finished. total time: 1.722s
The phone reboots but instead of rebooting into TWRP it just reboots the entire system.
I'm using stock everything, S-off and Unlocked.
Any help is appreciated.
maaavy said:
Before I updated to 4.4.3 I was able to boot into TWRP by using the fastboot commands:
fastboot boot twrp.img
It would automatically reboot the phone into TWRP where I could flash SuperSU yet retain stock recovery.
Now when I attempt to do the very same thing on 4.4.3 I get:
downloading 'boot.img'...
OKAY [ 1.320s]
booting...
OKAY [ 0.402s]
finished. total time: 1.722s
The phone reboots but instead of rebooting into TWRP it just reboots the entire system.
I'm using stock everything.
Any help is appreciated.
Click to expand...
Click to collapse
Why not just flash that recovery and then boot to it from the menu? Or you use flashify from within the Rom and change recoveries on the fly?
dottat said:
Why not just flash that recovery and then boot to it from the menu? Or you use flashify from within the Rom and change recoveries on the fly?
Click to expand...
Click to collapse
Worked like a charm. Thanks!
maaavy said:
Before I updated to 4.4.3 I was able to boot into TWRP by using the fastboot commands:
fastboot boot twrp.img
It would automatically reboot the phone into TWRP where I could flash SuperSU yet retain stock recovery.
Now when I attempt to do the very same thing on 4.4.3 I get:
downloading 'boot.img'...
OKAY [ 1.320s]
booting...
OKAY [ 0.402s]
finished. total time: 1.722s
The phone reboots but instead of rebooting into TWRP it just reboots the entire system.
I'm using stock everything, S-off and Unlocked.
Any help is appreciated.
Click to expand...
Click to collapse
I know you got this resolved, but for future reference, your command should be: fastboot flash recovery nameofrecovery.img
You flashed the recovery as if it were a boot.img, which it's not.
santod040 said:
I know you got this resolved, but for future reference, your command should be: fastboot flash recovery nameofrecovery.img
You flashed the recovery as if it were a boot.img, which it's not.
Click to expand...
Click to collapse
Brain fart on my part. Such an obvious mistake. Thanks!
santod040 said:
I know you got this resolved, but for future reference, your command should be: fastboot flash recovery nameofrecovery.img
You flashed the recovery as if it were a boot.img, which it's not.
Click to expand...
Click to collapse
I wanted to follow up on this. I've used his idea in the past on another htc device. I'd "fastboot boot <recovery>.img" and I could flash whole ROMs without touching the existing recovery. As soon as you reboot the old recovery is still there. His command wasn't an incorrect syntax for flashing a boot.img it was temporarily booting into a recovery. Is there any reason this wouldn't work nowadays?
cntryby429 said:
I wanted to follow up on this. I've used his idea in the past on another htc device. I'd "fastboot boot <recovery>.img" and I could flash whole ROMs without touching the existing recovery. As soon as you reboot the old recovery is still there. His command wasn't an incorrect syntax for flashing a boot.img it was temporarily booting into a recovery. Is there any reason this wouldn't work nowadays?
Click to expand...
Click to collapse
Yeah I know that was possible in the past, to flash a rom using a recovery one time, without overwriting the current one.
As I've never seen any real need or purpose to doing that, I've never done it that way.
I do know that the other command is what should be used to actually overwrite and flash a new recovery for further use.
So I can't really answer as to whether that method still works or not.
Didn't sound like it did for him though.
Hi Guys,
Hoping you can help me with this.
I was originally running Slimkat 4.4.4 and had the latest TWRP installed.
I downloaded the file for LPX13D and extracted all of the files right down to the Flash-all.bat and the images for bootloader, radio, and the system.
I ran the Flash-all.bat, and it installed everything successfully. The device booted, and voila, I am on 5.0 now.
The problem now, is that when I reboot into recovery, I am instead met with the little android guy laying on his back, with a red triange/exclamation point in his chest.
No problem, I say to myself. I'll just flash TWRP manually.
So I go to the bootloader, and try the command fastboot flash recovery recovery.img (renamed to make it faster to type.)
It goes through the motions, and says it was successful.
But when I go to recovery, it's the same red triange guy still.
I tried pressing volume up, power+volume up, etc. No dice. After about 30 seconds, it reboots on it's own back to system.
When I connect it to the Nexus Root Toolkit, and click on Flash recovery, and then choose TWRP latest, I get a window that pops up that tells me :
______
File Dependency Download
Status: Stock Kernel: Not Present - Need to download (this is in red)
Then a button that says "Download + Update All File Dependencies"
So what's my best option here? Should I let the NRT update the dependencies?
Try to flash cwm and tell me what happens
Isus <3 said:
Try to flash cwm and tell me what happens
Click to expand...
Click to collapse
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.
deleted
Stupendousman2012 said:
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.
Click to expand...
Click to collapse
Twrp is not optimized yet well like cwm is for andorid l
Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Lethargy said:
I flashed the new developer preview for 5 minutes or so then went to revert. Recovery wouldn't boot not matter what I flashed, until I flashed a KK userdata.img. So it seems like the new developer preview changes the internal storage/data partition more then the old one.
Click to expand...
Click to collapse
Don't try getting around it. Nothing to do with anything else.
Isus <3 said:
Twrp is not optimized yet well like cwm is for andorid l
Click to expand...
Click to collapse
What? CWM is outdated.
Lethargy said:
Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Don't try getting around it. Nothing to do with anything else.
What? CWM is outdated.
Click to expand...
Click to collapse
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
I also flashed the boot.img and the supersu update to get root working, and it seems to be going well now.
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.
Stupendousman2012 said:
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
Click to expand...
Click to collapse
Flash userdata.img and your TWRP will work properly.
Stupendousman2012 said:
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
Click to expand...
Click to collapse
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
Stupendousman2012 said:
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.
Click to expand...
Click to collapse
It says that because CWM is outdated.
Lethargy said:
Flash userdata.img and your TWRP will work properly.
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
It says that because CWM is outdated.
Click to expand...
Click to collapse
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?
Stupendousman2012 said:
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?
Click to expand...
Click to collapse
Yeah. Don't need to boot into recovery and wipe data since flashing a .img with fastboot while in bootloader erases it first then flashes. Just make sure you backup your stuff, including internal storage, off to a PC first if you have anything important.
Until L is officially released, we're using the below thread
http://forum.xda-developers.com/show....php?t=2796217
Android "L" Developer Preview Help, Troubleshooting, Q&A
Sent from my Nexus 5 using Tapatalk
Hi I wonder if anyone can help me. My tf700 is running Zombi-Pop 5.1.1-OMNI-DEODEX RC2 . I may have wrecked my recovery and boot-loader. My Infinity is unlocked and rooted and had TWRP 2..7.00 or roughly that. In preparation for installing KatKiss 6.0.1 . I updated TWRP to [RECOVERY] KANG TWRP TF700T [email protected] JAN 4 from within TWRP and it completed ok. When I went to reboot into recovery I got a unable to boot error boot-image is unreadable X000000 or something like that, But I am able to boot the system which seems to be working OK. Does anyone know if the is anyway for me to re-flash a working recovery or am I stuck without a recovery? If anyone can help me with this I would much appreciate it.
Cheers Al-Man
ps. I have read loads of posts but I am still unsure as to what is the best course of action. I don't want to make it totally useless.
Your bootloader is fine or you would not be able to boot Android.
Kang TWRP 2.8.x is fine for any current rom so that is not the problem either.
Did you let the tablet reboot after the recovery flash? Sounds to me as if that was when things went south.
So fastboot flash the recovery, then reboot to system once before you try to boot into recovery.
If you don't know how to fastboot flash it's high time you learned it.
http://forum.xda-developers.com/showthread.php?t=2688891
You could also use flashify or dd commands if you have root.
Sent from my KYOCERA-C6745 using Tapatalk
Tried Fastbbot still no joy
berndblb said:
Your bootloader is fine or you would not be able to boot Android.
Kang TWRP 2.8.x is fine for any current rom so that is not the problem either.
Did you let the tablet reboot after the recovery flash? Sounds to me as if that was when things went south.
So fastboot flash the recovery, then reboot to system once before you try to boot into recovery.
If you don't know how to fastboot flash it's high time you learned it.
http://forum.xda-developers.com/showthread.php?t=2688891
Click to expand...
Click to collapse
Thanks for your quick reply bernbib. I have tried to fastboot and load a new recovery image. I am able to see the device using the fastboot devices command. When I flash a new TWRP image it shows the following
twrp.img
sending 'recovery' (7038 KB)...
OKAY [ 2.801s]
writing 'recovery'...
OKAY [ 2.541s]
finished. total time: 5.343s
I then try fastboot reboot and all I get is
rebooting......
on the boot loader screen it reads just under the boot version
Starting Fastboot USB download protocol this is constantly showing every time I boot to the boot loader.
and then I reboot from the tablet and its back to square one .
Any Help with this problem would be most appreciated I can still boot to system but I am not able to access recovery.
Many Thanks. Alex
Can you reboot recovery from adb or shell?
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
Can you reboot recovery from adb or shell?
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Hi RealWelder Thanks for your quick reply No I'm afraid not.
Cheers. Alex
screenshot of boot screen
I just thought I would post a screen shot to see if anyone has any suggestions
View attachment 3863929
Any help with this would be much appreciated. :crying:
cheers Alex
Al-Man said:
I just thought I would post a screen shot to see if anyone has any suggestions
View attachment 3863929
Any help with this would be much appreciated. :crying:
cheers Alex
Click to expand...
Click to collapse
I have seen many cases of "unrecoverable bootloader error" but never that you could still boot into system with that error. So I have no idea what is going on for you, but the only method I know of to successfully recover from a unrecoverable bootloader error is to flash the Asus system blob in fastboot after fastboot erasing each major partition. We call it a buster99 and you'll find it here:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Before you do that why don't you try to 'fastboot boot recovery twrp.img' instead of flashing it. You should still be able to use TWRP as usual, flash a rom with it etc. It just does not get installed on the tablet....
See if you can use the recovery that way...
berndblb said:
I have seen many cases of "unrecoverable bootloader error" but never that you could still boot into system with that error. So I have no idea what is going on for you, but the only method I know of to successfully recover from a unrecoverable bootloader error is to flash the Asus system blob in fastboot after fastboot erasing each major partition. We call it a buster99 and you'll find it here:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Before you do that why don't you try to 'fastboot boot recovery twrp.img' instead of flashing it. You should still be able to use TWRP as usual, flash a rom with it etc. It just does not get installed on the tablet....
See if you can use the recovery that way...
Click to expand...
Click to collapse
Thanks. berndblb I tried to fastboot twrp from my PC (Ubuntu 14.04) but no joy got the following :crying:
[email protected]:~/Android$ fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
[email protected]:~/Android$ fastboot boot twrp.img
creating boot image...
creating boot image - 7211008 bytes
downloading 'boot.img'...
OKAY [ 2.727s]
booting...
FAILED (remote: ()
finished. total time: 2.751s
[email protected]:~/Android$ sudo fastboot boot twrp.img
[sudo] password for alex:
creating boot image...
creating boot image - 7211008 bytes
downloading 'boot.img'...
OKAY [ 2.729s]
booting...
FAILED (remote: ()
finished. total time: 2.747s
Any other suggestions, I don't like the sound of Buster 99 also tablet is the wife's.
Cheers. Alex
Buster99 has been a tablet saver for many users.
But if you don't want to do the whole thing try to fastboot erase recovery, cache and misc, then flash TWRP again and see if you can boot it.
Sent from my Nexus 5X using Tapatalk
berndblb said:
Buster99 has been a tablet saver for many users.
But if you don't want to do the whole thing try to fastboot erase recovery, cache and misc, then flash TWRP again and see if you can boot it.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks berndblb After erasing everthing 3 times I was finally able to flash a new TWRP image. Many Thanks again for all your help. Alex
Going through some of the threads here got me as far as being able to use fastboot on my bricked Shield.
I would like to ask if anyone can give me some pointers what to try next.
The previous owner tried to flash Lineage OS onto the Tablet using CWM but this failed and he probably wiped some needed partition.
I tried to flash new partitions and this works but I can not start the Shield and it won't boot into CWM. The strange thing is that I tried flashing TWRP and even though that started it did not boot through. And after a simple Shield reboot the CWM logo popped upmagain.....:confused
I was convinced I could fix this but I am beginning to think that this Tablet is a goner...
Any thoughts would ne appreciated.
What happens if you download an original recovery image from Nvidia for your model, and flashboot flash all 5 (recovery, boot, system, userdata, blob)? Do you get any fastboot errors? If the partition structure is corrupted, you'll see some sort of error message.
If the blob is messed up sometimes TWRP won't start. I suggest getting a factory image and trying again, then giving it a long time to boot. Once mine took 20 minutes at the Nvidia screen.
I did try flashing the original image from Nvidia including the other 4 images. One of the first things I tried. I woyld like to get it back to factory default. This went without issues an no errors. I might not have given it enough tine to but but still CWM seems to be on.
Will give it another try and post a screenshot.
Sent from my SM-G935F using Tapatalk
Here is a dump of the flash log. After flashing I reboot and the CWM logo pops up after a few minutes and gets stuck.
D:\Downloads\Shield Fix\Drivers\ADB FastBoot\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 100663296 bytes
sending 'recovery' (9758 KB)...
OKAY [ 0.384s]
writing 'recovery'...
OKAY [ 0.320s]
finished. total time: 0.709s
D:\Downloads\Shield Fix\Drivers\ADB FastBoot\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.394s]
booting...
OKAY [ 0.017s]
finished. total time: 0.417s
Think it is done for, after flashing TWRP numerous times it let me get to the start screen for TWRP it then hangs. When you reboot the Shield and want to go to the recovery again you get the dead android.
PS. I can sometimes get into TWRP but it fails on everything I do. Would there be a terminal solution for this? Like re-creating partitions?
Unlock your bootloader?
Sent from my ZTE A2017U using Tapatalk
It is already unlocked I am afraid.
Sent from my SM-G935F using Tapatalk
sn0r said:
It is already unlocked I am afraid.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Try to flash the attached file. Remember to unzip it first! Flash with:
"fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb"
Flashed the battery file and did another flash of NVIDIA's recovery image and even-tough it says everything is flashed correctly when I reboot I get the CWM logo and nothing more. When I do get into TWRP and try to flash a ROM I get messages errors like attached.
sn0r said:
Flashed the battery file and did another flash of NVIDIA's recovery image and even-tough it says everything is flashed correctly when I reboot I get the CWM logo and nothing more. When I do get into TWRP and try to flash a ROM I get messages errors like attached.
Click to expand...
Click to collapse
Then my guess would be some problems with the internal storage which may not be repairable.
Using fastboot try the following
Fastboot erase cache
Fastboot format cache
Fastboot format userdata
Make sure your tablet is in bootloader mode first though.
Sent from my pa_osprey using Tapatalk
First time trying to root, in order to install magisk and to get the full functionality of Edge sense +.
I was following this guide:
www-DOT-theandroidsoul-DOT-com/htc-u11-root-twrp-recovery-and-bootloader-unlock/
1. I have successfully unlocked bootloader
2. I have installed twrp
After some research, i think i made a mistake here, by installing twrp-3.1.1-0-ocn instead of the 3.2.1.2-ocn.
When booting to recovery mode, TWRP shows up, it asks for a password or to swipe the screen, but the screen is not responsive.
So i tried to flash the newest version of TWRP on top of the old one and i get this error :
PS C:\Users\ilan\Desktop\unlock-bl> fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (39676 KB)...
OKAY [ 1.137s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 1.145s
PS C:\Users\ilan\Desktop\unlock-bl>
How should i proceed?
I thought about going to stock recovery and then try to flash the new version of TWRP, but i didnt do a recovery. I have found that there is a way to recover to stock using something called RRU.
Help will b amazingly appreciated, tnx in advance
U may have already resolved..had same issue. Need to reboot directly to recovery and not via DL menu...then do Install Twrp Image file. Boot phone then if u can reboot directly to recovery go that route. If not try via Cmd Prompt...adb reboot recovery. Either way Twrp screen should be respnsive so u can flash Twrp img.
jelive said:
U may have already resolved..had same issue. Need to reboot directly to recovery and not via DL menu...then do Install Twrp Image file. Boot phone then if u can reboot directly to recovery go that route. If not try via Cmd Prompt...adb reboot recovery. Either way Twrp screen should be respnsive so u can flash Twrp img.
Click to expand...
Click to collapse
This is partially true. If anyone expierience touch screen not working in TWRP after following this tutorial: "theandroidsoul.com htc-u11-root-twrp-recovery-and-bootloader-unlock" - problem is, that old version of TWRP is linked there. You HAVE to download version 3.2 not 3.1 ->eu.dl.twrp.me/ocn/twrp-3.2.1-2-ocn.img.html
when touch screen is not working, use "adb reboot" and then "fastboot flash recovery twrp3.2.img"
it works for me