Is there any way to get a full image for "adb sideload", which doesn't depend on current system contents? I'm still locked, so I assume it would have to be signed from Google, but maybe this unicorn doesn't exist.
I'm in the marshmallow-brick club, desperately searching for solutions while I wait "7-10 days" for HTC escalation to get back to me. The LMY48T OTA apparently applied fine, but then MRA58K bricked me. I wasn't watching the update the whole time, just came back to see it stuck at the Google boot logo. I did a factory reset both from hboot and from recovery, still gets nowhere.
Recovery says I'm still on LMY48T. I tried to sideload MRA58K, and I get "system partition has unexpected contents". Since that check is part of the update script, I thought a mythical full-OTA wouldn't need to bother, but I'm probably grasping at straws.
I'm still OEM locked, and until now I didn't realize the full implications in "Developer options" of not enabling "OEM unlocking". How lovely. I'd be happy to blow it away with a factory image right now, but it seems there's no way...
What worked for me
I just sideload the Nexus 9 (WIFI) image from here: droid-life.com/2015/12/09/download-android-6-0-1-marshmallow-updates-for-nexus-devices
I was at 6.0.0 (MRA58N) according to the error messages I received when I tried to revert to lollipop. But, like you, the OTA update soft-briked my Nexus 9 which was working fine before on lollipop. I was just not aware that I had to OEM unlock it before the OTA update. Well...
The update process is long but it worked!
No more OEM-locked-endless-boot loop.
---------- Post added at 05:47 AM ---------- Previous post was at 05:43 AM ----------
Applying that image using adb sideload (while your device is locked) will erase all your data. I didn't find a way to not lose everything. On first boot, I was asked to provide my master password and did receive a message that my data is corrupted, then the device did a factory reset. On next reboot, was able to log on Google account, etc.
At least, my Nexus 9 will be working again!
Related
I'd like to start off by saying that I have NEVER rooted this device and have been 100% stock since day 1.
The only thing I did was enable developer options to unlock the bootloader so I could sideload OTA updates in the event they take too long to hit my device... No custom recoveries, no custom roms, no custom kernels, no exposed framework... NOTHING.. pure stock.
I started getting the 5.0.2 upgrade notification yesterday. Everytime I download and install, about 30% of the way through the installation I get the android icon showing ERROR. When I open the last recovery log it mentions not being able to open /cache/update.zip with a status 7 error. .. All I can do it reboot and return back to 5.0.1
I did some reading and it was recommended to wipe / format the CACHE partition. So I went into the stock recovery and tried this but to no avail.
I REALLY don't want to factory reset (or flash a factor image) and lose all the progress on the various games I have been playing.
Is there anything else I can try ??
you can try sideloading the update, grabbing the factory image and manually flashing the partitions (except userdata). you can try the factory image and just edit the flash-all.bat file to not wipe the device (sometimes the flash all file gave me an issue forcing me to do the partitions manually)
Thanks for the feedback... I can try this but IMO it's more of a workaround than a solution.
What I'm trying to get at is..... How in the heck would Google or HTC expect the average consumer to resolve such an issue.
Needing to have a PC, have special drivers installed, etc.., is understandable for those who want to step away from STOCK but what about the average consumer who just purchased the tablet to use as is, continues to receive a notification that an update is available, but fails every time it is applied ? Surely there is something that can be done so allow the update to take without having to factory reset or RMA the device...
y2whisper said:
you can try sideloading the update, grabbing the factory image and manually flashing the partitions (except userdata). you can try the factory image and just edit the flash-all.bat file to not wipe the device (sometimes the flash all file gave me an issue forcing me to do the partitions manually)
Click to expand...
Click to collapse
From the sounds of it there is an issue with the OTA file. But I agree you shouldn't be having to do this. I worry about the non xda'ers of the world when this stuff happens
Mine is doing the same crap. Also unmodified Nexus 9. This is nonsense.
Same issue here. Error every time I hit Restart & Install after downloading the update. Have to long press the power bottom to get it to boot back again. Tried a factory reset, didn't work. Still getting same error.
Thanks for sharing that you tried a factory reset. I am trying to avoid this for reasons mentioned in my 1st post.
I have tried numerous times now wiping cache and waiting for the upgrade to reappear but it continues to error out that the same place during the upgrade each time. Fortunately it's not bricking the device but IF this update is required as a stepping stone for subsequent updates then it will be extremely disappointing if Google doesn't address this issue.
I still cannot imagine google / htc not being able to resolve this WITHOUT having to make a user connect to a PC and manually flash imagess (or worse.. RMA the device). Hoping someone on XDA comes up with a magical sequence to allow the OTA to prcess properly.
In addition to wiping cache through recovery I have also ensured that I didn't have any apps / process or services disabled.
This is also being reported in google support forums:
https://productforums.google.com/fo...ter#!category-topic/nexus/nexus-9/MzHmJu4glkQ
I still haven't tried sideloading the OTA but at this point I don't think it would make a difference as the OTA does download properly and says it was verified.
kurtis.austin2 said:
Same issue here. Error every time I hit Restart & Install after downloading the update. Have to long press the power bottom to get it to boot back again. Tried a factory reset, didn't work. Still getting same error.
Click to expand...
Click to collapse
the.teejster said:
Thanks for sharing that you tried a factory reset. I am trying to avoid this for reasons mentioned in my 1st post.
I have tried numerous times now wiping cache and waiting for the upgrade to reappear but it continues to error out that the same place during the upgrade each time. Fortunately it's not bricking the device but IF this update is required as a stepping stone for subsequent updates then it will be extremely disappointing if Google doesn't address this issue.
I still cannot imagine google / htc not being able to resolve this WITHOUT having to make a user connect to a PC and manually flash imagess (or worse.. RMA the device). Hoping someone on XDA comes up with a magical sequence to allow the OTA to prcess properly.
In addition to wiping cache through recovery I have also ensured that I didn't have any apps / process or services disabled.
This is also being reported in google support forums:
https://productforums.google.com/fo...ter#!category-topic/nexus/nexus-9/MzHmJu4glkQ
I still haven't tried sideloading the OTA but at this point I don't think it would make a difference as the OTA does download properly and says it was verified.
Click to expand...
Click to collapse
I found this -> http://www.telekom-presse.at/apps/n...sht_update_auf_version_5-1_fehlt.id.33675.htm. There is a comment claiming to have fixed the issue by sideloading the OTA. I have yet to try it myself though.
On a side note,
Google has apparently finally released 5.1.1 for our device so it should be making it's way out soon.. HOPEFULLY we can go straight from 5.0.1 to 5.1.1 without having to worry about 5.0.2.
adstro said:
I found this -> http://www.telekom-presse.at/apps/n...sht_update_auf_version_5-1_fehlt.id.33675.htm. There is a comment claiming to have fixed the issue by sideloading the OTA. I have yet to try it myself though.
Click to expand...
Click to collapse
the.teejster said:
On a side note,
Google has apparently finally released 5.1.1 for our device so it should be making it's way out soon.. HOPEFULLY we can go straight from 5.0.1 to 5.1.1 without having to worry about 5.0.2.
Click to expand...
Click to collapse
Have you seen any evidence of this unicorn? Just curious...
Reported on the official Google+ page :
https://plus.google.com/+Nexus/posts/2hB9k5r2Z7T
But I can't find any reports of anyone actually receiving it yet. IF 5.0.2 needs to act as a stepping stone then maybe they delayed to get the 5.0.2 issue resolved 1st.. It seems to be getting more and more attention out there now.
cam30era said:
Have you seen any evidence of this unicorn? Just curious...
Click to expand...
Click to collapse
FWIW.
I went into recovery, wiped cache and tried to side load the 5.0.2 OTA update manually and got the same error. The error displayed approx. 40% into the upload process from the PC.
I'm getting frustrated I can't get 5.0.2 to install. This is ridiculous
When I get the error, Power/Vol+ switches to the recovery log - there is a warning about (from memory) a partition having been mounted R/W, and a suggestion to re-flash the device first.
All I can remember changing from stock is permitting bootloader-unlock from dev options (never got round to unlocking, so far as I remember).
Not too worried, will hang on for the next major update (or 6.x if there is a preview, maybe) - however, it seems 5.0.2 is a fix to allow 5.1.1 to download (from comments on the G+ thread)
My error is an SHA mismatch on /dev/block/platform/sdhci-tegra.3/by-name/APP. I have
47e96f7e7daa360947b456eca9dc5a8e45573b30
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
cam30era said:
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
Click to expand...
Click to collapse
How do I do this? Need adb from a computer?
kurtis.austin2 said:
How do I do this? Need adb from a computer?
Click to expand...
Click to collapse
Yes you need ADB and Fastboot. Follow this guide and don't hesitate to ask questions > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
cam30era said:
Yes you need ADB and Fastboot. Follow this guide and don't hesitate to ask questions > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Click to expand...
Click to collapse
Thank you ? very kind of you
kurtis.austin2 said:
Thank you ? very kind of you
Click to expand...
Click to collapse
Welcome
Please read the OP.
cam30era said:
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
Click to expand...
Click to collapse
Hi there,
I think I may have messed up my tablet. I recently was trying to update it through the fastboot commands but after wiping the internal storage and data, I went back to the bootloader and found out that the device was locked now. I can't fastboot flash anything since I don't have permission to do anything. I have TWRP flashed to the recovery though but when I go into there it asks for a password. I checked to see and it's because the device is locked, so I needed to unlock it. Well unfortunately there isn't an OS on the tablet to go into the settings and unlock it from. I was trying to flash Dirty Unicorns to see if I could just change it there but it fails during flash saying '/umount system failed: no volume exsists' if I try to reboot after that it just goes to the Google screen and does nothing.
So Bootloader Locked, TWRP installed, can't unlock bootloader since no OS installed.
Help!
Edit: I put this in the wrong forum. My bad.
@Verttex,
Let me see if I have understood your situation:
- bootloader is locked
- No ROM (deleted?)
-TWRP recovery installed, but you can't get into it because it requests a password?
---------- Post added at 08:07 PM ---------- Previous post was at 07:37 PM ----------
[/COLOR @Verttex
I think there is a solution for you on the Nexus 6 forum. See post #40 here >http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539/page4
Well I did the third command with the unlock.IMG that they provided, but now the screen doesn't work. It seems I can still get it to go to the bootloader since my computer detects it.
I might be able to get it to TWRP and then run the adb command again but right now, the screen is just blank.
Maybe I accidentally flashed the n6 unlock image instead of the n9 one?
Verttex said:
Well I did the third command with the unlock.IMG that they provided, but now the screen doesn't work. It seems I can still get it to go to the bootloader since my computer detects it.
I might be able to get it to TWRP and then run the adb command again but right now, the screen is just blank.
Maybe I accidentally flashed the n6 unlock image instead of the n9 one?
Click to expand...
Click to collapse
Go to that thread and post your question. They are the experts, and VERY helpful. The OP is actually looking for someone like you to try this.
Discussion moved to http://forum.xda-developers.com/nex...enable-oem-unlock-t3113539/page6#post61042231
Thread closed as per OP request.
I haven't used my Nexus in about a month and the last time I used it, I had flashed a new rom with the wrong gapps. It was a fresh factory reset and whenever it booted up, I would get error messages and I wouldn't be able to do the initial set up. At the time, this was nothing I couldn't fix, but I had to put it aside because I was busy.
Fast forward to present day, I completely forgot about it. I locked the device, flashed stock recovery and did another factory reset. Now whenever I try to turn it on I get stuck at a black screen with error messages (I can't do initial setup). I can't install a new rom because the device is locked and I can't unlock it because it's OEM locked and I can't get into the OS.
Am I screwed or can I still pull off a miracle?
Wug's Nexus Root Toolkit! There are tons of video tutorials on YouTube that should help.
Sent from my Nexus 6 using Tapatalk
Go_Radio said:
I haven't used my Nexus in about a month and the last time I used it, I had flashed a new rom with the wrong gapps. It was a fresh factory reset and whenever it booted up, I would get error messages and I wouldn't be able to do the initial set up. At the time, this was nothing I couldn't fix, but I had to put it aside because I was busy.
Fast forward to present day, I completely forgot about it. I locked the device, flashed stock recovery and did another factory reset. Now whenever I try to turn it on I get stuck at a black screen with error messages (I can't do initial setup). I can't install a new rom because the device is locked and I can't unlock it because it's OEM locked and I can't get into the OS.
Am I screwed or can I still pull off a miracle?
Click to expand...
Click to collapse
Hi, Go_Radio...
Probably screwed ... sorry, I don't mean to be glib or flippant. I've experienced something similar myself, late last year, and I had to return my Nexus 9 for a replacement, so I know what a pain in the backside this problem is.
-----
But to be clear, if I read and understand your post correctly, you're looking to run fastboot flash commands (either directly yourself, or allow a toolkit to run them for you) in order to either...
----
a) Fastboot Flash back to Google Factory Stock.
~ or ~
b) Fastboot Flash TWRP, and via TWRP, flash some Custom ROM.
----
...but cannot do either...
...because the bootloader is locked, and attempts unlock it with fastboot oem unlock fail.
And it fails because the option in SETTINGS>>DEVELOPER OPTIONS>>OEM unlocking (allow the bootloader to be unlocked) has not be enabled, or has been disabled.
This damnable nuisance problem, at the moment, can only be resolved in one of two ways... Either by returning your device for repair or replacement...
Or by the method described here...
[INFO] Nexus 6 / Nexus 9 Enable OEM Unlock [GUIDE] Unlock via TWRP/CWM
http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
...unfortunately for this to work, you do need TWRP installed, in order for the necessary files to be copied over to your Nexus 9, as the stock recovery doesn't allow for ADB connections (I know, I've tried )
And since Android won't boot, for whatever reason, you're locked out, and you can't enable the 'Allow OEM unlocking' setting in Developer Options in order to allow the bootloader to be unlocked, in order to fastboot flash TWRP. You're caught in a Catch 22 situation .
I wish I had some better options for you... .
Rgrds,
Ged.
Hi I need some help please, not really technical but loaded the Android N beta on my Nexus 9 wi-fi, as it was crashing almost hourly I opted to restore it to factory defaults, it is now stuck in a boot loop. Tried to install the current supported factory image using ADB OTA sideload but it fails at 47% saying something like "Error: image is "flounder"; device is "".. as if the device has no identity.
the fastboot can see the device but ADP struggles. the device shows LOCKED at all times. any suggestions greatly appreciated
part fixed
graminou said:
Hi I need some help please, not really technical but loaded the Android N beta on my Nexus 9 wi-fi, as it was crashing almost hourly I opted to restore it to factory defaults, it is now stuck in a boot loop. Tried to install the current supported factory image using ADB OTA sideload but it fails at 47% saying something like "Error: image is "flounder"; device is "".. as if the device has no identity.
the fastboot can see the device but ADP struggles. the device shows LOCKED at all times. any suggestions greatly appreciated
Click to expand...
Click to collapse
I have now got my device working by sideloading Android N image, not achieved my objective of unenrolling but at least I have a device that boots, will wait for a more stable version eventually
What image are you trying to sideload?
Make sure your not using the LTE version.
Try sideloading the Android N OTA again.
Have you previously enabled OEM unlock in developer options? If yes try "fastboot OEM unlock".
---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------
graminou said:
I have now got my device working by sideloading Android N image, not achieved my objective of unenrolling but at least I have a device that boots, will wait for a more stable version eventually
Click to expand...
Click to collapse
You post the above around the same time as my reply.
You now can enable OEM unlock and flash factory images.
corkiejp said:
What image are you trying to sideload?
Make sure your not using the LTE version.
Try sideloading the Android N OTA[/URL] again.
Have you previously enabled OEM unlock in developer options? If yes try "fastboot OEM unlock".
---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------
You post the above around the same time as my reply.
You now can enable OEM unlock and flash factory images.
Click to expand...
Click to collapse
Hi corkyejp and thanks, i was aiming to go back to current supported not the beta N release, I officially unenrolled received the OTA image, installed, got stuck in bootloop, tried sideloading MOB30G which i beleive was the correct wifi not LTE version (I saw that version mentioned in my crashlogs too). the device was in developer mode, I think but am not sure, however the HBOOT screens always showed LOCKED. i tried the fastboot flashing unlock (and OEM unlock options) but neither unlocked me. anyway at least I have a device that boots now, will put up with crashes if they occur. thanks again
I know there's some other threads about this already but my situation seems to be somewhat unique and the other solutions I've found haven't worked so I'm hoping someone may have other ideas.
When I boot my Pixel 6 which has unlocked bootloader and rooted with Magisk, I'm getting the RED message saying "your device is corrupt. it cant be trusted and may not work properly" and requiring me to push the power button a second time to continue booting. This is different than the YELLOW warning about unlocked bootloader, which comes after this.
This error started when I tried to install the April update the way I usually do, by downloading the factory image, and using flash-all.bat without the -w to avoid wiping. I was using a new computer though and so I downloaded the latest platform-tools (34.0.1) without realizing that version apparently has an issue. The update failed with the error about "FAILED (Sparse file is too large or invalid)" so I downgraded to platform-tools 33.0.3 and updated successfully. Except now that error is happening on boot.
Googling about the error I find that the main solution is factory reset and reinstall using the Pixel Flash Tool online and let it lock the bootloader and everything. I tried this and the error went away! But as soon as I unlocked the bootloader (NO other modification yet whatsoever, just unlocked the bootloader, the error is back.
I can't find anything about this online where it comes back from just unlocking the bootloader after a fresh stock install and everything back to factory.
Any ideas? It is still under warranty so if this seems like a hardware fault, I can probably get it replaced. Google support assured me that the factory reset would help, and when it didn't, they told me to take it to the local UBreakIFix store. I just want to see if I have any other course of action before doing that.
Thanks!
Oh, and the other solution I found which was this adb command: "
adb reboot "dm-verity enforcing" doesn't seem to help either. If I try to run the command I get this error "/system/bin/reboot: too many arguments". This is being run on Windows 11 and I am including the quotes around dm-verity enforcing so I don't see why that should be too many arguments.
ms4sman said:
I know there's some other threads about this already but my situation seems to be somewhat unique and the other solutions I've found haven't worked so I'm hoping someone may have other ideas.
When I boot my Pixel 6 which has unlocked bootloader and rooted with Magisk, I'm getting the RED message saying "your device is corrupt. it cant be trusted and may not work properly" and requiring me to push the power button a second time to continue booting. This is different than the YELLOW warning about unlocked bootloader, which comes after this.
This error started when I tried to install the April update the way I usually do, by downloading the factory image, and using flash-all.bat without the -w to avoid wiping. I was using a new computer though and so I downloaded the latest platform-tools (34.0.1) without realizing that version apparently has an issue. The update failed with the error about "FAILED (Sparse file is too large or invalid)" so I downgraded to platform-tools 33.0.3 and updated successfully. Except now that error is happening on boot.
Googling about the error I find that the main solution is factory reset and reinstall using the Pixel Flash Tool online and let it lock the bootloader and everything. I tried this and the error went away! But as soon as I unlocked the bootloader (NO other modification yet whatsoever, just unlocked the bootloader, the error is back.
I can't find anything about this online where it comes back from just unlocking the bootloader after a fresh stock install and everything back to factory.
Any ideas? It is still under warranty so if this seems like a hardware fault, I can probably get it replaced. Google support assured me that the factory reset would help, and when it didn't, they told me to take it to the local UBreakIFix store. I just want to see if I have any other course of action before doing that.
Thanks!
Click to expand...
Click to collapse
Two things you can try to get rid of the message:
1. Flash the previous month's boot image (your device likely won't boot but that's ok), then flash the boot image of your current month's build.
or
2. Flash the factory image of the previous month and then flash the current factory image.
The message is quite innocuous. You can also safely ignore it and wait until May's security patch is released, install that and the message should go away.
In a nutshell, the bootloader is looking for a new/updated OS without corruption errors so it will go back to restart mode rather than being stuck in the RED eio mode which displays that message.
Verifying Boot | Android Open Source Project
source.android.com
Boot Flow | Android Open Source Project
source.android.com
Lughnasadh said:
Two things you can try to get rid of the message:
1. Flash the previous month's boot image (your device likely won't boot but that's ok), then flash the boot image of your current month's build.
or
2. Flash the factory image of the previous month and then flash the current factory image.
The message is quite innocuous. You can also safely ignore it and wait until May's security patch is released, install that and the message should go away.
In a nutshell, the bootloader is looking for a new OS without corruption errors so it will go back to restart mode rather than being stuck in the RED eio mode which displays that message.
Verifying Boot | Android Open Source Project
source.android.com
Boot Flow | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
Thanks for the suggestions! I'll give it a try.
I'm curious though, is there a known issue with the April update or something?
Otherwise, since I completely factory reset it and installed the latest image using the Pixel Flash Tool and let it lock the bootloader and everything, wouldn't that have replaced any corrupt images? Why does JUST unlocking the bootloader trigger that warning now when it didn't used to?
Thanks!
ms4sman said:
Thanks for the suggestions! I'll give it a try.
I'm curious though, is there a known issue with the April update or something?
Otherwise, since I completely factory reset it and installed the latest image using the Pixel Flash Tool and let it lock the bootloader and everything, wouldn't that have replaced any corrupt images? Why does JUST unlocking the bootloader trigger that warning now when it didn't used to?
Thanks!
Click to expand...
Click to collapse
Not sure why just unlocking the bootloader caused that message (I haven't seen that before), but there really wasn't a need to re-lock your bootloader in the first place as far as I'm aware of.
The error was likely originally caused by using Platform Tools 34 and encountering the error you did. I've seen plenty of people update to April without a problem.
Lughnasadh said:
Not sure why just unlocking the bootloader caused that message (I haven't seen that before), but there really wasn't a need to re-lock your bootloader in the first place as far as I'm aware of.
The error was likely originally caused by using Platform Tools 34 and encountering the error you did. I've seen plenty of people update to April without a problem.
Click to expand...
Click to collapse
Yeah it's very strange indeed. I just did some more testing. Just to confirm things, I just used the Pixel Flash Tool and flashed the latest stock image for the phone onto both slots just to be safe, then locked the bootloader. At this point, the phone should be EXACTLY as it was from the factory, right?
But as soon as I unlocked the bootloader and rebooted, it goes right back to the corrupt message. I locked it again, and bang, error gone. Unlocked, error back.
JUST unlocking the bootloader shouldn't cause any issue or trigger this error right?
ms4sman said:
Yeah it's very strange indeed. I just did some more testing. Just to confirm things, I just used the Pixel Flash Tool and flashed the latest stock image for the phone onto both slots just to be safe, then locked the bootloader. At this point, the phone should be EXACTLY as it was from the factory, right?
But as soon as I unlocked the bootloader and rebooted, it goes right back to the corrupt message. I locked it again, and bang, error gone. Unlocked, error back.
JUST unlocking the bootloader shouldn't cause any issue or trigger this error right?
Click to expand...
Click to collapse
As I stated earlier, the bootloader is looking for a new/updated OS without corruption errors. So try doing one or both of the two things I suggested earlier. Sounds like you are just flashing the same factory image which isn't actually updating to a new/updated OS.
All this locking and unlocking is causing factory resets.
Why bother?
Easiest way to make the red corruption message go away is to extract the vbmeta image from the factory image zip and do this -
Code:
fastboot --disable verity flash vbmeta vbmeta.img
Voila! Red warning gone and no factory reset.
Next month continue flashing as you usually do.
No need to disable verity next time because the corruption message is gone and an updated OS will be installed.