Everything has gone completely pear-shaped, despite following every single guide to the letter. Fastboot outright refuses to flash things that were asked for, e.g. any recovery image that isn't named recovery.img, flashing anything other than the 3280KB one even after erasing the recovery partition (despite asking it to flash one of the other sized recovery images renamed to recovery.img). amms.mdn outright refused to flash. The single time I got into the 1.4.1 build it had no service, WiFi was completely broken, and after that it just spiralled into the Dell logo cycle. I can't downgrade since it won't let me flash the downgrade recovery, and whatever I do it all doesn't work. No one else has had these problems, it seems. And I have been left without a phone.
Please help.
EDIT: Found this guide, might help with the recovery image flash problem:
androidforums.com/eris-all-things-root/130639-can-someone-help-me-remove-clockwork-mod.html
Only problem is that this suggests it should be in charge-only mode. Would this still work if I can't get it into Android?
Related
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
puppinoo said:
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
Click to expand...
Click to collapse
Theres a hardware method to boot into the bootloader, this i think you can test, just to see if you can at least get into bootloader.....nothing more
Details in the official nvidia link
http://nv-tegra.nvidia.com/gitweb/?...ob_plain;f=README_SHIELD;hb=rel-22r18-partner
There's a thread here on the "questions" thread with users reporting that the timing of the hardware method can be a pain in the you know where.............might be worth looking into that thread for their experiences in booting the bootloader using the hardware method
Disclaimer:If your brave enough to risk a brick, read on
I suspect this might be the 2.1 stock/twrp issue........current twrp, or current stock dont play nice
Its a good sign that SOMETHINGS loading, rather then NOTHING booting, but dont know if theirs a solution
My analysis of the situation, of what little i know, the -w (wipe) command was expecting a stock recovery but instead got twrp, which is why your in this situation.........maybe, i stress maybe, if you could reflash stock again, you might be able to boot into android stock again and try full android again, leaving out twrp, until a twrp fix is found
Edit
Saying that, if the bootloader is, as i suspect, now using twrp to flash things, then you might be boned....... im no expert on bootloaders, stock "recoveries" and how they work, so i might be wrong on that
Reports around here say that 1.3 stock firmware is the recommended back to stock firmware, apparently, flashing any other firmware versions, bring their own issues.............
From 1.3 stock, use nvidias official OTA to upgrade from 1.3 stock, to 2.1 stock, then try 2.1 full android again...........note, i dont think you can skip firmwares i.e. you have to upgrade to 1.4, then to 2.0, then to 2.1, alot of downloading.......the OTA does'nt give you any other choice
Before doing anything that ive suggested, wait till someone with more experience to come along........i dont want to be responsible for you fully bricking your shield..........just wanna give you an idea of what i think has happened
If worse comes to worse, if you have warrenty, get a replacement
Gd luck........remember, this is an analysis of your predicament of what i THINK might of happened, and what steps, i likely might of entertained.......after looking into it more thouroughly, knowing that i could get a replacement if it went downhill.........so your mileage might vary
Edits
Crappy grammer, further musings, clarifications
Thanks.[/QUOTE]
puppinoo said:
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
Click to expand...
Click to collapse
I had something similar about... shield goes booting in recovery and trying delete some cache and keeps repeat and repeat
Hardware boot in fastboot / bootloader mode
Accessing Bootloader via Hardware
Unplug power from the Shield Android TV. *
Wait a few seconds.
Hold down the power button.
Plug in power
Count to three
Release the power button
You should see the bootloader screen.
If you hold it down too long or not long enough, it simply doesn’t work.
Restore Shield Android TV to Stock
P.s. Personally me I followed this instructions and kind of magically got it in bootloader mode. First done by instruction and then just gave up and pressed randomly and fastboot screen appear. Thanks God I had to done only once, if I would do again I wouldn't had patients
Good luck with this, hope you will get sorted
Here will be link about where I got instructions about hardware boot
http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/
Sent from my Nokia 3310 using free xda app
Thanks a lot fro your help.
I was able to put the box in fastboot mode.
Since I'm not that expert can you tell me where and which rom I have to download (I have a french 16gb version of the box).
Then I'd need to know exactly what commands to performs (even a link to a tutorial is fine).
I really appreciate your help. It seems I can (hopefully) save the box.
EDIT: The fastboot command gave me a (not enough space) when I bricked the box. Is there a risk it could happen again while flashing stock? No idea how much space I have left on the box really.
EDIT2: I found this page: https://developer.nvidia.com/shield-open-source
and I'm downloading this rom called nv-recovery-image-shield-atv-upgrade2_1.zip
and Intend to follow these instructions: http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Can anyone please confirm I'm doing right?
EDIT with joy : I followed all the steps using that rom and it seems everything worked. I reconfiguring the box now. Thanks for help.
basically the procedure I intend to follow is this part (please confirm it's ok):
To flash this recovery image to your SHIELD, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader. Get
DTB file name to use for flashing for your product(see below):
P.s. maybe Since past fastboot commands failed and I only flashed system from zulu99 I could skip the 'fastboot flash boot boot.img' command so if it fails again I still can attempt the fastboot process again?
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb <DTB file name>
puppinoo said:
Thanks a lot fro your help.
I was able to put the box in fastboot mode.
Since I'm not that expert can you tell me where and which rom I have to download (I have a french 16gb version of the box).
Then I'd need to know exactly what commands to performs (even a link to a tutorial is fine).
I really appreciate your help. It seems I can (hopefully) save the box.
EDIT: The fastboot command gave me a (not enough space) when I bricked the box. Is there a risk it could happen again while flashing stock? No idea how much space I have left on the box really.
EDIT2: I found this page: https://developer.nvidia.com/shield-open-source
and I'm downloading this rom called nv-recovery-image-shield-atv-upgrade2_1.zip
and Intend to follow these instructions: http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Can anyone please confirm I'm doing right?
Click to expand...
Click to collapse
You are on the right way with those links
P.s. You can do manual one by one entering or paste and copy those commands or (I'm doing) drag and drop file "flash-all.bat" on cmd previous opened there where you have abd/fastboot etc files and extracted RIGHT FIRMWARE (like shift and right click mouse "open command prompt here"
And after this all sit down and relax
Anyway you are on the right way.
P.s. Hope you download adb fastboot drivers somewhere from Internet !?!
Sent from my Nokia 3310 using free xda app
There's a painful brick story behind this, and I'll share those details if needed, but let me start with my current situation.
I've got a D800 (AT&T). I can boot to Android (almost stock D80030f, rooted), but I can't get to recovery. I've tried AutoRec to install TWRP, but when I reboot to recovery, it takes me to fastboot mode instead. I would try to flash recovery from fastboot, but the only fastboot command that ever returns is getvar, and it comes back empty for most variables. Anything else I've tried just hangs (erase, flash, reboot). I see the command printed on the phone's screen, but nothing happens after that. This is the same as it was while I was bricked and stuck in fastboot mode. I've tried from Linux, from Windows in a VM, and from a Windows host.
I can get to download mode, but I can't flash anything there, either. The drivers are installed and everything is set up correctly according to all the guides, but when I try to flash, I get an error that the version doesn't match (or something, I can get the exact error message if needed). I suspect this is related to the fastboot problem, because it shows version strings that are either empty or null, I don't remember which. I get the same behavior from both my Windows VM and my Windows host. Both are Windows 7 64-bit.
It would be nice to get fastboot and download mode working, but what I really care about is TWRP, of course. Is there anything I can do to get this working while booted to Android?
I've already short circuited this thing once, and that's how I got this far. I dd'ed every partition (from http://downloads.codefi.re/autoprime/LG/LG_G2/D800/Stock_Firmware/30f_partitions) except for modem and dbi, and a TWRP image for the recovery partition. So if I have to short circuit again, I'm not afraid to.
Edit:
I'm not sure if this is in any way indicative of the problem, but I just noticed that my GPS isn't working. Honestly, I'd be happy to start with a fresh TOT if I could just get it to flash.
This is just a friendly notice for Ticwatch E&S users. If you do anything that resets the watch back to default, it seems the device needs to boot to the stock recovery before it will boot back into the system. The only way to do this after flashing TWRP is to reboot to the bootloader and and run 'fastboot boot StockRecovery_TicwatchE.img' with the image file from the root thread by @EpicLPer. Normally, this wouldn't be a big deal but this could be an issue if you do this away from a PC where you can run fastboot.
This is also a big problem if you screw up and flash a broken TWRP and can't reboot into the bootloader. I was working on a recovery procedure for this but screwed the pooch on that too so I'm going to see if I can RMA the dead watch.
BackCheck said:
This is just a friendly notice for Ticwatch E&S users. If you do anything that resets the watch back to default, it seems the device needs to boot to the stock recovery before it will boot back into the system. The only way to do this after flashing TWRP is to reboot to the bootloader and and run 'fastboot boot StockRecovery_TicwatchE.img' with the image file from the root thread by @EpicLPer. Normally, this wouldn't be a big deal but this could be an issue if you do this away from a PC where you can run fastboot.
This is also a big problem if you screw up and flash a broken TWRP and can't reboot into the bootloader. I was working on a recovery procedure for this but screwed the pooch on that too so I'm going to see if I can RMA the dead watch.
Click to expand...
Click to collapse
You can flash the stock recovery and all other stuff via the Flash Tool. You don't have to RMA a dead flashed watch, you can recover 99% of all the bricks you do via that. But you'll have to ask @Luxios for that as I don't know how to correctly use it
He's also trying to make a hacked bootloader which allows you to boot into recovery and fastboot directly from the watch without ADB.
EpicLPer said:
You can flash the stock recovery and all other stuff via the Flash Tool. You don't have to RMA a dead flashed watch, you can recover 99% of all the bricks you do via that. But you'll have to ask @Luxios for that as I don't know how to correctly use it
He's also trying to make a hacked bootloader which allows you to boot into recovery and fastboot directly from the watch without ADB.
Click to expand...
Click to collapse
Flash Tool is a mighty powerful tool, alright. I couldn't find a good scatter file so in a caffeine deprived state I tried to cobble one together. I may have damaged the preloader. It does show up in device manager but it is different that the VCOM preloader device that was showing. Now it totally crashes Flash Tool too. I'm still working on it but since I have a second watch now, I might just RMA this one and start over.
Again, if anyone has a good scatter file please post it. I found one after the fact but I get errors and it's for another MT2601 device, not the Ticwatch.
The good news is I found if you power down the watch and hold the power button on boot you'll get a long vibrate. If you release the button and hit it 3 or 4 times during the vibrate you'll be in the bootloader.
Anyone have stock or even custom working system.img and boot.img?
great
thank you very much man, i was blocked in twrp recovery after a factory reset, and now i should have installed stock recovery, thanks to your post .
Well, as every good person was trying to get root access from my device and all the tutorials I was seeing told me that it would be necessary to unlock the bootloader so that I could install a superior room, android 8, and unlock the cell phone - so I followed my walk and I was trying various tutorials, I could list the links here, but it would not work.
Well, what was the game change was this:
https://eusouandroid.co/voltar-zenfone-3-para-o-android-marshmallow-6-0/
Which is basically based on running a flash recovery and a flash boot. After the procedure the cell decided to stay a reboot loop, that is, it loaded the android screen, loaded the asus screen and rebooted.
Searching in the forums I saw that it would be necessary to perform an update via recovery mode, so I downloaded the version correctly for my boot and recovery, I passed the data to the memory card and went to access my recovery mode, however, Access keys to recovery mode is the same as doing nothing.
The cell phone has decided that it will no longer open recovery mode and I do not know how to solve it.
In the middle of the way I realized one:
fastboot erase cache
fastboot erase recovery
fastboot erase boot
And without wanting a fastboot erase system.
I think my solution starts by putting the system files back into the phone and following this tutorial here:
https://forum.xda-developers.com/zenfone-3/help/unbricking-zenfone-3-ze552kl-dm-verity-t3563970
I created the files and would perform the procedure as described, however by the time I should open the recovery mode saint nothing happens while holding the keys and I do not know what options I have anymore.
Does anyone know of any way to regain access to recovery?
I already tried to flash the twrp indicated for the device in the tutorials, but the recovery still does not open.
At the moment I have an electronic block that sheer lack of knowledge has arrived in this state.
At the moment I only have access to fastboot
Thanks in advance!
EDIT: It looks like I was sabotaging myself, the model of the device is zc553kl. I still could not figure it out, but I was headed in the wrong direction.
EDIT: I was using the incorrect version of the device to flash the information, after updating the post with the version of the device I was able to find the correct information on how to recover the cell and perform the root.
Thank you very much.
Pixel 3a. Bootloader unlocked. Stock. Previously have used Magisk although I didn't have it installed or setup at the moment. I was neglectful and hadn't updated OTA or factory images since updating to Android 10. My current boot slot is b. I've tried updating via Magisk OTA or system OTA but they both fail, so I use factory images manually to keep my data partition.
Today I downloaded the sargo November 2019 image. The process I've been using across a few Pixel phones the past few years has been to manually unpack the Factory image ZIP and the update ZIP, then manually fastboot flash bootloader, reboot, radio, reboot, then boot_a and boot_b, system, system_b, vendor, and modem.
It should have been a hint to me that I got an error when I went to flash system. My console told me I need to use fastbootd. So I switched there, flashed the system partitions. Went to reboot and got "Your device is corrupt. It can't be trusted and may not work properly.", which I've never encountered before. Press Power - ignore the device-is-unlocked message, and get to the Google boot screen. And then the device appears to be frozen.
Right now I'm thinking to go back to my first Android 10 factory image and see if I can reverse whatever I did... but figured I should check here to see if I had missed something important. Low and behold this forum says to only flash one slot at a time, to switch and boot into the other slot, etc. Okay, so I messed up. Any good ideas on how to fix what I did?
UPDATE: I don't normally sideload updates, but I got into recovery mode, sideloaded the OTA for November, and I'm back in business. I'll do a few reboots to be sure I'm good but the phone did boot up, my user data is intact. The phone still starts out with a "your phone is corrupt" message, which is then followed by the "you have an unlocked bootloader" message. That second screen has some messed up characters on it.
If anyone has advice on the "right" way to maintain slots A vs. B and how to be careful, how to combine this with Magisk etc and can point me to posts in threads, that'd be helpful for the future. Thanks!
I don't understand why so many people even mess with A/B partition commands. If you follow the normal flashing instructions, you don't specify a boot partition. Entering specific boot partition commands will greatly increase the odds that you mess something up.
ohioDroid said:
Pixel 3a. Bootloader unlocked. Stock. Previously have used Magisk although I didn't have it installed or setup at the moment. I was neglectful and hadn't updated OTA or factory images since updating to Android 10. My current boot slot is b. I've tried updating via Magisk OTA or system OTA but they both fail, so I use factory images manually to keep my data partition.
Today I downloaded the sargo November 2019 image. The process I've been using across a few Pixel phones the past few years has been to manually unpack the Factory image ZIP and the update ZIP, then manually fastboot flash bootloader, reboot, radio, reboot, then boot_a and boot_b, system, system_b, vendor, and modem.
It should have been a hint to me that I got an error when I went to flash system. My console told me I need to use fastbootd. So I switched there, flashed the system partitions. Went to reboot and got "Your device is corrupt. It can't be trusted and may not work properly.", which I've never encountered before. Press Power - ignore the device-is-unlocked message, and get to the Google boot screen. And then the device appears to be frozen.
Right now I'm thinking to go back to my first Android 10 factory image and see if I can reverse whatever I did... but figured I should check here to see if I had missed something important. Low and behold this forum says to only flash one slot at a time, to switch and boot into the other slot, etc. Okay, so I messed up. Any good ideas on how to fix what I did?
UPDATE: I don't normally sideload updates, but I got into recovery mode, sideloaded the OTA for November, and I'm back in business. I'll do a few reboots to be sure I'm good but the phone did boot up, my user data is intact. The phone still starts out with a "your phone is corrupt" message, which is then followed by the "you have an unlocked bootloader" message. That second screen has some messed up characters on it.
If anyone has advice on the "right" way to maintain slots A vs. B and how to be careful, how to combine this with Magisk etc and can point me to posts in threads, that'd be helpful for the future. Thanks!
Click to expand...
Click to collapse
Just unpack the factory images and remove the -w. Then either do flash-all or open the flash-all and follow the steps inside to see what you need to flash. The portion that says update will fail if you have not followed the initial steps. Don't specify boot partitions the factory images should flash to both slots. That should take care of your corrupted message.
Sent from my Pixel 3a using Tapatalk
sic0048 said:
I don't understand why so many people even mess with A/B partition commands. If you follow the normal flashing instructions, you don't specify a boot partition. Entering specific boot partition commands will greatly increase the odds that you mess something up.
Click to expand...
Click to collapse
Probably because there are references around saying to do so. And the threads have so many posts it can be difficult to read it all and learn something is right or wrong.
3-ish years ago I had come across this post that specifically says to flash A/B both:
https://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
I've been following it on Pixel phones every since then. I never gave a second thought to the A/B partitions up until this happened. The main thing that was different now from my perspective was having to use fastbootd to flash the system, which I've never done before.
By manually flashing the bootloader and radio, and then using Recovery to install an OTA update (instead of using the Factory image) I was able to get the phone to boot properly. It still starts up by saying it is corrupt and requiring me to hit the power button to proceed, and then showing the 'phone is unlocked' message with some garbled characters, but then starts up and works fine (as far as I can tell). Maybe I can OTA the future December update and that will fix things? Or is there something I can do now?
Just want to try to provide some sound advice, next time maybe look to use the flash-all.sh script. There is absolutely zero reason not to, and going outside of that just means you're just tinkering around way more than necessary.
I think you're over complicating things. Just download latest factory image, unzip it, connect the phone to PC and double click the run me bat file. I always clean flash, but if you want to keep data, as others have said, delete the - w .
Just an update on the status...
I decided to not try to install magisk or anything during November. With the December update I ran it OTA the standard format. The "Corrupt" message is gone. I assume (haven't yet checked) that I've switched over to boot_a.
Okay so going forward if I want to install Factory Images while keeping data just use the flash_all.bat but remove the -w switch. Got it.
Now I just need to get Magisk back on there and figure out the current way to enable WiFi Tether/hotspot.