About 2 weeks ago, I unlocked the bootloader to my Nexus 9. I installed TWRP and a CyanogenMod nightly. After deciding the only availible Cyanogen builds for the Nexus 9 (the nightlies) are far too unstable for general use, I tried today to flash the recovery ROM. I flashed the rom with an error:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(893,0xa04ae1d4) malloc: *** mach_vm_map(size=1816023040) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1814205204 bytes
error: update package missing system.img
I then made the ridiculous mistake of locking my bootloader again (fastboot oem lock) which ran successfully, but then got me stuck in a recovery boot loop (teamwin splash screen). After about a minute of this, the screen went black and the device is now a $399 paperweight. I cannot use any key combinations to get the screen on. It won't show up in fastboot either. I have no hopes of getting a repair from HTC for three main reasons:
1. I got the device from somebody who attended a conference at Google and received the device for free. Does it affect my warranty?
2. If there is a custom recovery, I have surely voided what warranty I would've had.
3. I live in a Central American country, where it is extremely difficult to ship items to the United States, especially items of high value.
Is my wonderful device that was so kindly given to my now an HTC branded brick?
[UPDATE] I have been able to get into fastboot, but I still get the error? I got the firmware from the official Google page, and I am 100% sure I downloaded the correct rom :/
You're most likely sol. Read this thread, http://forum.xda-developers.com/showthread.php?p=59677447
Sent from my Nexus 9 using XDA Free mobile app
With the error you get when trying to flash factory image through adb . Have you tried first to unzip the images from inside the file downloaded from google and flash individually? You've already flashed the bootloader/radio when you started installing the factory image, I wonder if you flash the image files inside the zip inside the factory tgz if you might escape? look here, http://forum.xda-developers.com/nexus-9/general/guide-nexus-9-to-stock-guide-unbrick-t2975668 if you can still fastboot this might help?
nrsmac said:
About 2 weeks ago, I unlocked the bootloader to my Nexus 9. I installed TWRP and a CyanogenMod nightly. After deciding the only availible Cyanogen builds for the Nexus 9 (the nightlies) are far too unstable for general use, I tried today to flash the recovery ROM. I flashed the rom with an error:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(893,0xa04ae1d4) malloc: *** mach_vm_map(size=1816023040) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1814205204 bytes
error: update package missing system.img
I then made the ridiculous mistake of locking my bootloader again (fastboot oem lock) which ran successfully, but then got me stuck in a recovery boot loop (teamwin splash screen). After about a minute of this, the screen went black and the device is now a $399 paperweight. I cannot use any key combinations to get the screen on. It won't show up in fastboot either. I have no hopes of getting a repair from HTC for three main reasons:
1. I got the device from somebody who attended a conference at Google and received the device for free. Does it affect my warranty?
2. If there is a custom recovery, I have surely voided what warranty I would've had.
3. I live in a Central American country, where it is extremely difficult to ship items to the United States, especially items of high value.
Is my wonderful device that was so kindly given to my now an HTC branded brick?
[UPDATE] I have been able to get into fastboot, but I still get the error? I got the firmware from the official Google page, and I am 100% sure I downloaded the correct rom :/
Click to expand...
Click to collapse
First of all why the HELL did you lock your bootloader?? Secondly, every single person who has tried to flash these factory images from google using the built in script got this same exact error, including me. All you had to do was manually "fastboot flash system system.img" and thats it. Problem solved. Unless you can manage to get the bootloader unlocked again, its bricked. Good luck
bynarie said:
First of all why the HELL did you lock your bootloader?? Secondly, every single person who has tried to flash these factory images from google using the built in script got this same exact error, including me. All you had to do was manually "fastboot flash system system.img" and thats it. Problem solved. Unless you can manage to get the bootloader unlocked again, its bricked. Good luck
Click to expand...
Click to collapse
I made the mistake of blindly following the advice on the Google page (which did tell me to lock the device). Google needs to fix that script, and get us 5.1 on our nexus devices!!!
Related
I've been searching and experimenting for a week with different solutions as time allowed and still haven't found the write post although It's probably right under my nose.
I bought a used prime that was rooted and unlocked. It was in a 1a brick when I bought it so I quickly fixed that. But I'm having a weird issue with the recovery partition. I'm thinking possible the unlock was borked or never took but I'm new to the prime and don't know my way around like I do with HTC smartphones and hboots.
When I fastboot flash a recovery.img, the command prompt shows it writing to the partition and the time for each section and says successful, and I'm on the screen with the blue bar. I let it sit a while and reboot and when it reboots it still has the old recovery. I've tried several recovery img files and they all do the same thing. If I try the flash_image method I've seen here in some threads I get an error -1in the last line of the terminal string.
I've tried erasing recovery partition and then writing to it and I get the same error. However, I can flash a zip file of a new recovery that was made for clockwork and it works. And also if I use one of the rooting tools to install recovery, that writes the recovery also.
I tried unrooting and installing an asus .15 blob and starting over with a factory reset in order to run the asus bootloader unlock apk. Once I got to unrooted .15 the tool would at least run, but when it connects to the server after I agree to the end user license agreement and terms of unlocking, it throws up and error message that says "Error: Unknown Error."
It could be something I'm doing wrong thats very simple, but I need someone to weigh in on this and let me know where I went wrong, either with fastboot flashing the recovery or with unlocking.
What has me puzzled is that fastboot erased the partition fine but wont write to it.
Sent from my Transformer Prime using xda premium
Hi Guys,
Long-time listener, first-time caller..
I have a feeling I’ve broken my HTC One X+ [enrc2b] (UK Vodafone running CM10.2) due to a bad upgrade.
I had Cyanogen 10.2 installed and have been happily using and updating it via the built in CM update tool.
I went from stable to nightly a couple months ago and have never found any major issues so continued to use nightlies.
On Sunday (12th Jan) a new CM update was made available and I went through the usual process without really looking closely at the update. The update was for CM11. (Shouldn't matter? I've flashed new boot.img's before when required).
The update downloaded so the phone rebooted and went to flash, but failed halfway through due to a corrupt download.
I’m not sure if it was the file on the CM servers or if the download simply corrupted but I’ve never seen a similar issue and didn’t interrupt the update so I’m guessing it was a bad file uploaded for the update.
This is where it gets messy.
I had removed the previous update files so there are none available in the /cmupdate/ folder other than the CM11 version. If I had kept just one I wouldn't be in this situation (lesson learnt!).
My phone DOES NOT have USB debugging turned on, therefore I am not able to use ADB to push files to the device. Is there anyway to send files to the phone without using ADB. I'm pretty familiar with fastboot but can only flash recovery/boot using fastboot (?).
I’ve tried flashing the stock recovery so I can use the RUU for Vodafone UK but the RUU flsah fails. I’ve re-locked the bootloader and have the stock recovery but I get an error when using the RUU.
The RUU is v1.14 and my phone has v1.17 (from CM) so I suspect this is the problem as the version needs to be greater than the current?
The error from the RUU is related to the bootloader (error 140). I’ve tried a couple different versions of RUU such as a Europe one with v1.17 but it throws the wrong region code error when trying to flash.
I don’t have a nandriod back up. I thought I had done when I originally unlocked and rooted the phone. Turns out that it didn’t work.
I have downloaded a couple nandriods that I think would work but because I don’t have ADB working I can’t push the files to the device anyway.
I have CWM recovery installed again now, after the failed RUU update, and a version of hboot (that’ll check when I get home). I think it’s 1.400?
So, is my phone save-able, or is it now a paperweight. Any and all help appreciated.
A lot of the posts relating to fixing similar issues assume you have ADB/USB debug available, and I don’t! I have done a lot of reading over the past couple of days but am no closer to resolving this.
In case it helps, I can grab the zips from the RUU temp folder but wouldn't know how to flash them (does it need ADB?).
Can anyone help?
max3o6 said:
Hi Guys,
Long-time listener, first-time caller..
I have a feeling I’ve broken my HTC One X+ [enrc2b] (UK Vodafone running CM10.2) due to a bad upgrade.
I had Cyanogen 10.2 installed and have been happily using and updating it via the built in CM update tool.
I went from stable to nightly a couple months ago and have never found any major issues so continued to use nightlies.
On Sunday (12th Jan) a new CM update was made available and I went through the usual process without really looking closely at the update. The update was for CM11. (Shouldn't matter? I've flashed new boot.img's before when required).
The update downloaded so the phone rebooted and went to flash, but failed halfway through due to a corrupt download.
I’m not sure if it was the file on the CM servers or if the download simply corrupted but I’ve never seen a similar issue and didn’t interrupt the update so I’m guessing it was a bad file uploaded for the update.
This is where it gets messy.
I had removed the previous update files so there are none available in the /cmupdate/ folder other than the CM11 version. If I had kept just one I wouldn't be in this situation (lesson learnt!).
My phone DOES NOT have USB debugging turned on, therefore I am not able to use ADB to push files to the device. Is there anyway to send files to the phone without using ADB. I'm pretty familiar with fastboot but can only flash recovery/boot using fastboot (?).
I’ve tried flashing the stock recovery so I can use the RUU for Vodafone UK but the RUU flsah fails. I’ve re-locked the bootloader and have the stock recovery but I get an error when using the RUU.
The RUU is v1.14 and my phone has v1.17 (from CM) so I suspect this is the problem as the version needs to be greater than the current?
The error from the RUU is related to the bootloader (error 140). I’ve tried a couple different versions of RUU such as a Europe one with v1.17 but it throws the wrong region code error when trying to flash.
I don’t have a nandriod back up. I thought I had done when I originally unlocked and rooted the phone. Turns out that it didn’t work.
I have downloaded a couple nandriods that I think would work but because I don’t have ADB working I can’t push the files to the device anyway.
I have CWM recovery installed again now, after the failed RUU update, and a version of hboot (that’ll check when I get home). I think it’s 1.400?
So, is my phone save-able, or is it now a paperweight. Any and all help appreciated.
A lot of the posts relating to fixing similar issues assume you have ADB/USB debug available, and I don’t! I have done a lot of reading over the past couple of days but am no closer to resolving this.
In case it helps, I can grab the zips from the RUU temp folder but wouldn't know how to flash them (does it need ADB?).
Can anyone help?
Click to expand...
Click to collapse
the phone when on recovery doesn't need the USB debugging to be turned on....
if u had installed the proper drivers u will be able to see ur phone as on recovery.....
[email protected] said:
the phone when on recovery doesn't need the USB debugging to be turned on....
if u had installed the proper drivers u will be able to see ur phone as on recovery.....
Click to expand...
Click to collapse
Hmm, ok thanks. Maybe I need to reinstall ADB drivers. The HTC USB drivers work ok (fastboot usb is fine) and I do have ADB installed but having meddled with it (reinstalled ADB) I should try pushing again I guess.
Thanks, will try when when home! :good:
ADB without USB debugging turn on
Now sorted!
ADB works when the phone is in recovery, not in hboot. Dur.
Thanks!
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.
I was trying to figure out how to install a larger GApps package on my tablet, and I used GNU parted to do repartition. I've resized the system partition to 3GB and still can't install the full package.
Anyway I didn't do anything disastrous except that I accidentally deleted misc partition, I made a new partition and name it as misc and thought it was all good.
I didn't realize what I've done until I tried to reboot, my tablet is now completely a brick, the screen doesn't turn on no matter what I do
What can I do now? Is there any possible solution?
Nathaniel_Wu said:
I was trying to figure out how to install a larger GApps package on my tablet, and I used GNU parted to do repartition. I've resized the system partition to 3GB and still can't install the full package.
Anyway I didn't do anything disastrous except that I accidentally deleted misc partition, I made a new partition and name it as misc and thought it was all good.
I didn't realize what I've done until I tried to reboot, my tablet is now completely a brick, the screen doesn't turn on no matter what I do
What can I do now? Is there any possible solution?
Click to expand...
Click to collapse
If you can't see/access device in fastboot nothing can be done short of board replacement (factory/fastboot cables won't work). Even if it does respond in fastboot only a few have been successful in reviving the device after a repartitioning which is BAD idea on this device. I lack the necessary experience so will not be able to guide you further. Assumes an unlocked bootloader; you're done if device is still locked.
Davey126 said:
If you can't see/access device in fastboot nothing can be done short of board replacement (factory/fastboot cables won't work). Even if it does respond in fastboot only a few have been successful in reviving the device after a repartitioning which is BAD idea on this device. I lack the necessary experience so will not be able to guide you further. Assumes an unlocked bootloader; you're done if device is still locked.
Click to expand...
Click to collapse
Fastboot device list doesn't show anything… My bootloader is unlocked, but that doesn't matter now I guess…:crying:
hello i think minse one is break or so, was serving in internet it hang over, now it only starts in fastboot mode, wantet to flash twrp there but comes error: fash write failure, what can i do?
brill_e said:
hello i think minse one is break or so, was serving in internet it hang over, now it only starts in fastboot mode, wantet to flash twrp there but comes error: fash write failure, what can i do?
Click to expand...
Click to collapse
Can't flash or boot TWRP on this device. Consult index or other threads for info on reloading FireOS via stock recovery.
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.