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
Related
Tried to update to CM 11 / 4.4 KitKat and got "unrecoverable bootloader error"
So I messed up big time. Trying to update to the new unofficial 4.4 OmniRom and had to update TWRP from 2.5.0.0 to the latest 2.6.3.1 in order to flash the new 4.4 ROM but it kept giving me an 'set_metadata_recursive'. So I used the version provided and then used Flashify app on Google play (mistake) to flash it (it said that it installed successfully). Then when I reseted to recovery it got corrupted. So I thought I installed at the wrong place and installed as a zip, recovery and IMG. (Bigger mistake). Now it won't load at all on any OS and boot loader and recovery are corrupted.
Can some one help me? Please o)v_v)o
ANDROiD_eKa said:
So I messed up big time. Trying to update to the new unofficial 4.4 OmniRom and had to update TWRP from 2.5.0.0 to the latest 2.6.3.1 in order to flash the new 4.4 ROM but it kept giving me an 'set_metadata_recursive'. So I used the version provided and then used Flashify app on Google play (mistake) to flash it (it said that it installed successfully). Then when I reseted to recovery it got corrupted. So I thought I installed at the wrong place and installed as a zip, recovery and IMG. (Bigger mistake). Now it won't load at all on any OS and boot loader and recovery are corrupted.
Can some one help me? Please o)v_v)o
Click to expand...
Click to collapse
You can read this to see if it helps..good luck..:fingers-crossed:
http://forum.xda-developers.com/showthread.php?t=2528313
ANDROiD_eKa said:
So I messed up big time. Trying to update to the new unofficial 4.4 OmniRom and had to update TWRP from 2.5.0.0 to the latest 2.6.3.1 in order to flash the new 4.4 ROM but it kept giving me an 'set_metadata_recursive'. So I used the version provided and then used Flashify app on Google play (mistake) to flash it (it said that it installed successfully). Then when I reseted to recovery it got corrupted. So I thought I installed at the wrong place and installed as a zip, recovery and IMG. (Bigger mistake). Now it won't load at all on any OS and boot loader and recovery are corrupted.
Can some one help me? Please o)v_v)o
Click to expand...
Click to collapse
Sorry, but after reading your post 4 times I still have no idea what you actually did.....
If you still have access in ADB (since you can't access the bootloader??) the link LMK gave you may save your bacon.
If you don't have any kind of access: ADB or fastboot and you do not have nvFlash blobs - sorry, you bricked.
Can I access fastboot when I get the menu at RCK / Android / Wipe? Because if I click con any of these its says that bootloader is corrupted.
What's the Command to fix TWRP using a computer / or other Android device?
ANDROiD_eKa said:
Can I access fastboot when I get the menu at RCK / Android / Wipe?
Click to expand...
Click to collapse
Does it say something about fastboot in the upper left corner?
ANDROiD_eKa said:
What's the Command to fix TWRP using a computer / or other Android device?
Click to expand...
Click to collapse
fastboot flash recovery twrp.img
(or whatever name your TWRP blob has)
_that said:
Does it say something about fastboot in the upper left corner?
fastboot flash recovery twrp.img
(or whatever name your TWRP blob has)
Click to expand...
Click to collapse
Thanks _that for the advice...:good: You are the expert in this area... I am done with my job to bring you in here for helps..haha...
_that said:
Does it say something about fastboot in the upper left corner?
fastboot flash recovery twrp.img
(or whatever name your TWRP blob has)
Click to expand...
Click to collapse
Yes it says
Code:
Starting Fastboot USB download protocol
Ok flashed TWRP via fastboot but device freezes?
Code:
C:\Documents and Settings\HP_Administrator.CEREBRO>fastboot -i 0x0B05 flash reco
very twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 2.563s]
writing 'recovery'...
OKAY [ 2.453s]
finished. total time: 5.016s
It still won't let me boot to TWRP saying an "unrecoverable bootloader error" occured. Is there something I can do?
ANDROiD_eKa said:
Ok flashed TWRP via fastboot but device freezes?
Code:
C:\Documents and Settings\HP_Administrator.CEREBRO>fastboot -i 0x0B05 flash reco
very twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 2.563s]
writing 'recovery'...
OKAY [ 2.453s]
finished. total time: 5.016s
It still won't let me boot to TWRP saying an "unrecoverable bootloader error" occured. Is there something I can do?
Click to expand...
Click to collapse
You can use the link on my previous reply and read post #3 by _that to clear your misc.. You need to use "dd=" command erase your mmcblk0p3 partition. Please be carefull when you use it and make sure you erase the right partition. Anything after "of=" is you write to....
Please ask more question with _that before execute that command...Good luck..:fingers-crossed:
LetMeKnow said:
You can use the link on my previous reply and read post #3 by _that to clear your misc.. You need to use "dd=" command erase your mmcblk0p3 partition. Please be carefull when you use it and make sure you erase the right partition. Anything after "of=" is you write to....
Please ask more question with _that before execute that command...Good luck..:fingers-crossed:
Click to expand...
Click to collapse
I think this may be different. Clearing the misc partition solved the problem of force booting into recovery.
Here he can't get into recovery... Not looking good.....
berndblb said:
I think this may be different. Clearing the misc partition solved the problem of force booting into recovery.
Here he can't get into recovery... Not looking good.....
Click to expand...
Click to collapse
The fastboot write is successfull but the recovery is not updating.... You and _that may have the answer..
LetMeKnow said:
The fastboot write is successfull but the recovery is not updating.... You and _that may have the answer..
Click to expand...
Click to collapse
Pff - just yesterday I used fastboot to push TWRP 2.6.3.1 and it said successful. TWRP still shows version 2.6.1. - so what do I know???
berndblb said:
Pff - just yesterday I used fastboot to push TWRP 2.6.3.1 and it said successful. TWRP still shows version 2.6.1. - so what do I know???
Click to expand...
Click to collapse
I think that his/her bootloader is still partly function because the fastboot is running.. I don't want to give any advice unless I know for sure that it works. If someone have a better knowledge on the bootloader and recovery, it can be up and running again, I hope...
LetMeKnow said:
I think that his/her bootloader is still partly function because the fastboot is running.. I don't want to give any advice unless I know for sure that it works. If someone have a better knowledge on the bootloader and recovery, it can be up and running again, I hope...
Click to expand...
Click to collapse
As long as there is fastboot, there is hope
http://lmgtfy.com/?q=fastboot+boot+image
berndblb said:
As long as there is fastboot, there is hope
http://lmgtfy.com/?q=fastboot+boot+image
Click to expand...
Click to collapse
Hey guys thank you for your help. I had learned that I encountered a softbrick. I got my tabby fix reading ]Unrecoverable bootloader error(0x00000000) Which led me to Softbrick - possible solution for you
Followed these steps...
buster99 said:
My solution
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer, as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
Click to expand...
Click to collapse
Although I admit I had to these steps several times as it initially wouldn't somehow it wiped out that error. After I had fix that bootloader error I used fastboot and installed TWRP 2.6.3.1 and now life can continue.
I also followed steps right on getting CM11 to work by using CWM Touch this time to install and it looks jelly. ?! Love these 4.4 KitKat emoticons, thanks again for your help and interest in me ?
ANDROiD_eKa said:
Hey guys thank you for your help. I had learned that I encountered a softbrick. I got my tabby fix reading ]Unrecoverable bootloader error(0x00000000) Which led me to Softbrick - possible solution for you
Followed these steps...
Although I admit I had to these steps several times as it initially wouldn't somehow it wiped out that error. After I had fix that bootloader error I used fastboot and installed TWRP 2.6.3.1 and now life can continue.
I also followed steps right on getting CM11 to work by using CWM Touch this time to install and it looks jelly. ?! Love these 4.4 KitKat emoticons, thanks again for your help and interest in me ?
Click to expand...
Click to collapse
Buster99 deserves a medal or something for this post. Dozens of people have recovered from a brick using his method!
Glad you got it going!
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.
I recently had to do the RUU recovery method found here: http://forum.xda-developers.com/showthread.php?t=2727831
Which fixed the problem i was having. Now i'm having another problem.
I flash and i get the following from my CMD:
fastboot flash recovery cm-13.0-20151210-NIGHTLY-m8-recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (18436 KB)...
OKAY [ 1.669s]
writing 'recovery'...
OKAY [ 0.982s]
finished. total time: 2.653s
Click to expand...
Click to collapse
But, when i boot into recovery, it gets stuck on "Entering Recovery", and my ADB says "unauthorized"
InuyashaITB said:
I recently had to do the RUU recovery method found here: http://forum.xda-developers.com/showthread.php?t=2727831
Which fixed the problem i was having. Now i'm having another problem.
I flash and i get the following from my CMD:
fastboot flash recovery cm-13.0-20151210-NIGHTLY-m8-recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (18436 KB)...
OKAY [ 1.669s]
writing 'recovery'...
OKAY [ 0.982s]
finished. total time: 2.653s
But, when i boot into recovery, it gets stuck on "Entering Recovery", and my ADB says "unauthorized"
Click to expand...
Click to collapse
I haven't run CM in ages but I don't recall it coming with a recovery. Maybe try using the latest TWRP recovery and flash it in fastboot.
As for the adb "unauthorized" I'm not sure but I didn't think adb works in bootloader. I think it's all fastboot until the Rom boots. Again, definitely not sure about that and I'm away from my pc to go test it out.
cntryby429 said:
I haven't run CM in ages but I don't recall it coming with a recovery. Maybe try using the latest TWRP recovery and flash it in fastboot.
As for the adb "unauthorized" I'm not sure but I didn't think adb works in bootloader. I think it's all fastboot until the Rom boots. Again, definitely not sure about that and I'm away from my pc to go test it out.
Click to expand...
Click to collapse
I was able to get it to work. Turns out, when i went back to early RUU, it also replaced my HBOOT to an earlier version. I updated to 3.19 and it fixed the problem.
NOW i have another problem where my WIFI has stopped working, (altough 4G works now)... So i will try to replace kernel & radios to see if that works.
InuyashaITB said:
I was able to get it to work. Turns out, when i went back to early RUU, it also replaced my HBOOT to an earlier version. I updated to 3.19 and it fixed the problem.
NOW i have another problem where my WIFI has stopped working, (altough 4G works now)... So i will try to replace kernel & radios to see if that works.
Click to expand...
Click to collapse
when you updated to the new hboot, did you flash the last firmware?
this will get you up-to-date with everything.
as for WiFi it could be completely ROM related.
I'm having similar issues. I have had CWM recovery in stalled and have my M8 unlocked, rooted, and S-Off with the Google Play Edition Marshmallow ROM. I made an attempt to flash the latest TWRP using both Flashify as well as Fastboot, but it just sits in "starting recovery" screen even after multiple reboots. I can re flash CWM and it works fine, but I'd really like to get TWRP up and running. Any thoughts on my next step?
I've cleared the cache in Fastboot with no luck. Also, my WiFi won't activate either when booted into Marshmallow. Not sure they are related though.
eliot1171 said:
I'm having similar issues. I have had CWM recovery in stalled and have my M8 unlocked, rooted, and S-Off with the Google Play Edition Marshmallow ROM. I made an attempt to flash the latest TWRP using both Flashify as well as Fastboot, but it just sits in "starting recovery" screen even after multiple reboots. I can re flash CWM and it works fine, but I'd really like to get TWRP up and running. Any thoughts on my next step?
I've cleared the cache in Fastboot with no luck. Also, my WiFi won't activate either when booted into Marshmallow. Not sure they are related though.
Click to expand...
Click to collapse
Yeah, After all the problems, I finally gave up and reverted back to latest stable CM12.1, WIFI is working, 4G working... I'm o.k with that
I bit the bullet as well and installed the 5.0.1 with latest firmware RUU. From there, TWRP installed with no issues.
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
I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.
toyspeed said:
I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.
Click to expand...
Click to collapse
What's the message that appears in ADB when you flash it?
toyspeed said:
I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.
Click to expand...
Click to collapse
Did u unlocked the bootloader?
Sent from my Redmi Note 7 Pro using XDA Labs
Naveenthemi said:
What's the message that appears in ADB when you flash it?
Click to expand...
Click to collapse
Just usual message such as:
PS C:\platform-tools> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.112s]
writing 'recovery'...
OKAY [ 0.355s]
finished. total time: 2.474s
I tried with Black Project also, same story. I don't understand this, I just want to root but I can't!
toyspeed said:
Just usual message such as:
PS C:\platform-tools> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.112s]
writing 'recovery'...
OKAY [ 0.355s]
finished. total time: 2.474s
I tried with Black Project also, same story. I don't understand this, I just want to root but I can't!
Click to expand...
Click to collapse
Ok someone else who's facing the same problem fixed this by formatting the data partition.
But idk why don't you try reinstalling MIUI(Flashboot it through MiFlash) and then try again?
Naveenthemi said:
Ok someone else who's facing the same problem fixed this by formatting the data partition.
But idk why don't you try reinstalling MIUI(Flashboot it through MiFlash) and then try again?
Click to expand...
Click to collapse
Ok, thanks for advice I'll try formatting data partition. That's exactly what I've been doing, flashing MIUI through MiFlash everything perfect. Then I run into problems after I try flashing recovery so I can root, very weird but I will keep trying.
toyspeed said:
Ok, thanks for advice I'll try formatting data partition. That's exactly what I've been doing, flashing MIUI through MiFlash everything perfect. Then I run into problems after I try flashing recovery so I can root, very weird but I will keep trying.
Click to expand...
Click to collapse
Did it work?
Naveenthemi said:
Did it work?
Click to expand...
Click to collapse
I actually decided to flash Superior OS instead, loving it so far!