I tried to flash Google Factory Images from the Google website.
7Zip complained of a CRC mis-match. Wugfresh's NRT kit complained of the same thing. MD5 and SHA-1 checksums are the same as what Google has on its download page. And of course I can't run the flash-all.bat script because I get the "Signature verification failed" message. I would like to have the option to return the device to Stock status. What can I do?
Any help would be appreciated!
Thanks,
joslide
UPDATE: Problem Solved
I had been researching Google on this problem for days. One possible solution was to issue a "fastboot oem unlock" before executing the flash-all.bat script. Well, my bootloader was clearly unlocked (icon on the startup screen). Evidently that's not enough. I locked the bootloader via fastboot and then unlocked it again. That did the trick.
Related
When i had my nexus 7 i updated to 4.2.1 and then did a factory reset. Upon booting my nexus was back on android 4.1.2(i thought this shouldnt have happened?)
Now the OTA update wont install - i get the dead android with an exclamation mark.
I have downloaded the nexus 7 toolkit to try and unlock the bootloader and flash stock 4.2.1 but i get an error when trying to unlock - FAILED (command write failled (unknown error))
anyone able offer some help please?
ive tried fastboot oem unlock using nexus toolkit and direct through the command line with same results
is this guide any good?
http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html
Otherwise you have this GUIDE
Phone:I9100P
Kernel:Dorimanx
ROM:4.2.1 Vanilla RootBox
Tablet:Nexus 7
Kernel:M-Kernel
ROM:4.2.1 AOKP PUB
MOD:JusTunBean
welly_59 said:
When i had my nexus 7 i updated to 4.2.1 and then did a factory reset. Upon booting my nexus was back on android 4.1.2(i thought this shouldnt have happened?)
Now the OTA update wont install - i get the dead android with an exclamation mark.
I have downloaded the nexus 7 toolkit to try and unlock the bootloader and flash stock 4.2.1 but i get an error when trying to unlock - FAILED (command write failled (unknown error))
anyone able offer some help please?
Click to expand...
Click to collapse
It is possible (albeit very slightly) that the file didn't flash correctly, but did corrupt the bootloader just enough to stop it being unlocked/booting into recovery.
If you can't issue the 'fastboot oem unlock' command then it could be for 2 reasons:
1. It is already unlocked (try typing 'fastboot oem lock' and see if it re-locks')
2. The bootloader is slightly corrupt.
Hopefully it is the first one
liamwli said:
It is possible (albeit very slightly) that the file didn't flash correctly, but did corrupt the bootloader just enough to stop it being unlocked/booting into recovery.
If you can't issue the 'fastboot oem unlock' command then it could be for 2 reasons:
1. It is already unlocked (try typing 'fastboot oem lock' and see if it re-locks')
2. The bootloader is slightly corrupt.
Hopefully it is the first one
Click to expand...
Click to collapse
i managed to get it working after erasing everything as in the guide above. I had to keep unplugging the device and trying again though and after a few attempts it worked
when encountering this error i simply cycled through the options (using volume) and said boot into bootloader, familiar windows device dis/connect and then tried the fastboot flash boot boot.img cmd again, worked a treat, currently flashing the system part.
hope this helps!
Not sure why but i wiped my device with adb so i could install the new JWR66Y image but when i try to flash the booterloader it keeps giving me a error FailedState. I could remove boot, system etc in adb so the device is pluged in but when i try to fastboot flash bootloader it fails. My device is Unlocked also so i aint got a clue whats going on i have the correct 4.3 image file etc, anyone know how to fix this? Cheers.
Edit: I notice when trying to flash the bootloader in the top corner of the bootloader it says Signature Mismatch.
Ok i have sorted it now, wasent just me with the problem its the bootloader image signature so downloaded the bootloader from the JWR66V image.
Hi everyone !
I searched for a case like mine on the forum, but didn't find a solution to my problem, so you're my last hopes !
I have a Nexus 7 (2012) WIFI for a while now and I wanted to return to stock, on Lollipop (I was on Paranoid Android ROM, 4.4.4).
So, l used the Nexus Root Toolkit and ran the "return to stock + unroot" feature.
I downloaded the last google image for my device (5.0.2) and let the thing began.
It erases all partitions like it has to do, but when it needs to write bootloader, it fails and says: "FAILED (command write failed (Unknown error))".
I tried severals time, but always same problem. So I tried to flash stock 4.4.4, but can't write bootloader too: "FAILED (No suck device)" or "FAILED (too many links)" errors appear, something like those.
So, in last hopes, I tried to do this manually and followed this thread: http://forum.xda-developers.com/showthread.php?t=1907796
I erased correctly all partitions, but when I need to flash bootloader with "fastboot flash bootloader bootloader-tilapia-4.23.img" command, I get "FAILED (command write failed (Unknown error))" too...
I can't flash recovery, get the same error as the bootloader one...
If someone had the same problem or if someone can help me to restore my Nexus 7, it would be very kind !
Thanks to everyone who'll read this
Also have the same problem generated by the very same software!!
Anyone have any further info please?
MiMilz said:
Hi everyone !
I searched for a case like mine on the forum, but didn't find a solution to my problem, so you're my last hopes !
I have a Nexus 7 (2012) WIFI for a while now and I wanted to return to stock, on Lollipop (I was on Paranoid Android ROM, 4.4.4).
So, l used the Nexus Root Toolkit and ran the "return to stock + unroot" feature.
I downloaded the last google image for my device (5.0.2) and let the thing began.
It erases all partitions like it has to do, but when it needs to write bootloader, it fails and says: "FAILED (command write failed (Unknown error))".
I tried severals time, but always same problem. So I tried to flash stock 4.4.4, but can't write bootloader too: "FAILED (No suck device)" or "FAILED (too many links)" errors appear, something like those.
So, in last hopes, I tried to do this manually and followed this thread: http://forum.xda-developers.com/showthread.php?t=1907796
I erased correctly all partitions, but when I need to flash bootloader with "fastboot flash bootloader bootloader-tilapia-4.23.img" command, I get "FAILED (command write failed (Unknown error))" too...
I can't flash recovery, get the same error as the bootloader one...
If someone had the same problem or if someone can help me to restore my Nexus 7, it would be very kind !
Thanks to everyone who'll read this
Click to expand...
Click to collapse
PaulG2000 said:
Also have the same problem generated by the very same software!!
Anyone have any further info please?
Click to expand...
Click to collapse
It's pretty well known that for some reason, the bootloader images included on many of the factory images for grouper are not valid, and Google has never corrected this. You'll need to grab a valid bootloader from a different factory image, and flash it manually.
Check this thread out, it's all been covered in great detail there: http://forum.xda-developers.com/showthread.php?t=2573015
Edit: Also, if you're already on a valid bootloader version 4.23, then there's no need to flash the bootloader again.
I accepted the 5.1 OTA, it seemed to download fine, rebooted to install it, and it failed at around 20% or so with this log:
Code:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/app/ConfigUpdater/ConfigUpdater.apk" has unexpected contents.
E:Error in cache/update.zip
(Status 7)
Installation aborted.
Since then, that's all I get when I boot it up. I don't have ADB Debugging enabled, so I figured the easiest way to fix it was to flash back to stock, but I can't get it the bootloader to unlock. I can get to the bootloader, and fastboot recognizes it with the correct serial number, but fastboot oem unlock keeps failing with this:
Code:
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 2.640s
I've tried all the USB ports on my computer and several different cables, but the result is the same. I've been banging my head against the wall for a couple weeks now on this, tried a couple different tools, but it all keeps failing at the same spot because the bootloader just won't unlock. Is there any hope of fixing this, or am I in the market for a new tablet?
Can you try opening ADB/Command Prompt with administrative rights and retrying the unlock of the bootloader?
Fobos531 said:
Can you try opening ADB/Command Prompt with administrative rights and retrying the unlock of the bootloader?
Click to expand...
Click to collapse
All right, gave that a shot, but still getting the same results.
I had my N7 go belly up too while doing the update. What got things back to normal was to use the "flash-all.bat" file that comes with all the updates (it's in the zip file from Google. Caution!!! ****Each flash-all.bat is unique to each Android version****. Make sure you use the proper .bat file. ). First I had to go back to 4.4.4 (for some unknown reason). After that, I did the same (ran the "flash-all.bat" file that came with 5.1) and bingo, everything went fine.
I was about to toss my N7 in the garbage, but after getting this suggestion from XDA member "Fobos531", gave it it go and it worked.
Look over here:
http://forum.xda-developers.com/nexus-7/help/thank-google-bricking-nexus-7-t3082379
Also make sure to take a look at this thread, I thought it might be relevant: http://forums.androidcentral.com/go...s-bootloader-failed-remote-invalid-state.html
phillip - Unfortunately (or maybe fortunately), since I can't get the bootloader unlocked, I haven't been able to get far enough to screw it up by flashing the wrong thing. Using the flash-all.bat starts by failing to unlock the same way, then not flashing anything at all because the bootloader is still locked.
Phobos - My tablet shows 4.23 installed. Since the last successful system update was the LRX22G OTA, is it then likely I have the invalid version? And if so, any clue how I would go about fixing that with the bootloader still locked?
Maybe bootloaders can be flashed while being locked? Try flashing this one using fastboot(the link is from this site:http://www.wugfresh.com/google-changes-nakasi-and-nakasig-factory-packs/) : https://www.androidfilehost.com/?fid=95916177934550135 Make sure the md5 checksum is valid: it has to be df53028033c9eccf4fe5ba7bc198ce24). Afterwards flash it using "fastboot flash bootloader name-of-bootloader-file.img (i think this is the right command).
Note: Everything you do, you do on your own risk.
Good luck!
EDIT: In the WugFresh page it says that your bootloader must already be unlocked, but I just don't have any idea on how to fix the adb error you are getting.
Help! "Your device is corrupt. It can't be trusted and may not work properly." (Red)
Hello,
just recently i rooted my Nexus 6p device and unlocked the bootloader, i noticed however, after rooting the device i received an error on boot up stating "Your device software can't be checked for corruption. Please lock the bootloader." (Orange), but after researching on the internet many people said that was normal due to the boot loader being unlocked...
however my concern for today is i have flashed back to the factory images of marshmallow, and am now experiencing an error on boot up that Your device is corrupt. It can't be trusted and may not work properly." i followed the exact step-by-step guide on how to unroot and lock the boot loader on the link below however am still experiencing the issue, please help it will be ever so much appreciated.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(the error that i am receiving after flashing stock image)
https://lh3.googleusercontent.com/iGv9RPFbDSLec-4-cvsQNOh46pt5RhEvPy7EKKZXmbtjJ16P7d5EXOJHCIsR=w300
I've had that as well with mine before. The way I fixed mine was a somewhat tedious process but it did work for me. Start by downloading one of the angler images from Google, then with 7zip, decompress the .tgz which gives you a .tar. Once more will get you a folder named xxxxxx-angler. (I think it was that way but not 100% sure since I'm not at my laptop at the moment). With your phone (unlocked) in bootloader/fastboot mode, run flash-all.bat. this gets you back to a fully stock system but still has the corruption flag tripped. Run stock recovery and do a factory reset and the corruption warning should be gone and back to the "normal" screen saying please lock the bootloader.
bb1981 said:
I've had that as well with mine before. The way I fixed mine was a somewhat tedious process but it did work for me. Start by downloading one of the angler images from Google, then with 7zip, decompress the .tgz which gives you a .tar. Once more will get you a folder named xxxxxx-angler. (I think it was that way but not 100% sure since I'm not at my laptop at the moment). With your phone (unlocked) in bootloader/fastboot mode, run flash-all.bat. this gets you back to a fully stock system but still has the corruption flag tripped. Run stock recovery and do a factory reset and the corruption warning should be gone and back to the "normal" screen saying please lock the bootloader.
Click to expand...
Click to collapse
thank you but i have already done all that, the problem is that i have flashed the angler image from google and did a factory reset,however, i am selling the phone soon and the warning message is still there even though the boot loader is locked and am not rooted
Moddy98 said:
thank you but i have already done all that, the problem is that i have flashed the angler image from google and did a factory reset,however, i am selling the phone soon and the warning message is still there even though the boot loader is locked and am not rooted
Click to expand...
Click to collapse
Try doing this process manually, if you're selling it. I would infer the data doesn't matter on the device.
Depending on which OS you are on. Focus your command prompt with fast boot installed to your directory containing the stock files (unzip the image zip)
Now do the following process manually. Step by step
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash vendor vendor.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot flash cache cache.img
Now, if you still get the red warning. Repeat the process and add :
fastboot format userdata
DO NOT FLASH THE USERDATA IMAGE
If this does not work, I have other suggestions.
same prob in orange..plz help bro
TnT_ said:
Try doing this process manually, if you're selling it. I would infer the data doesn't matter on the device.
Depending on which OS you are on. Focus your command prompt with fast boot installed to your directory containing the stock files (unzip the image zip)
Now do the following process manually. Step by step
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash vendor vendor.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot flash cache cache.img
Now, if you still get the red warning. Repeat the process and add :
fastboot format userdata
DO NOT FLASH THE USERDATA IMAGE
If this does not work, I have other suggestions.
Click to expand...
Click to collapse
I flashed my nexus 5x with marshmallow from nougat...but at the end i didn't lock the oem bootloader...so now i am repeatedly getting an error message "your device software can't be checked for corruption.Please lock the bootloader nexus"(orange color)..i had downgraded my nexus to marshmallow because i was having a bootloader stuck up loop problem...
And to do any of the steps I have to switch on the usb debugging mode right ??? But the problem is this message is constantly coming and i am unable to do anything for the past 2 days
vigy321 said:
I flashed my nexus 5x with marshmallow from nougat...but at the end i didn't lock the oem bootloader...so now i am repeatedly getting an error message "your device software can't be checked for corruption.Please lock the bootloader nexus"(orange color)..i had downgraded my nexus to marshmallow because i was having a bootloader stuck up loop problem...
And to do any of the steps I have to switch on the usb debugging mode right ??? But the problem is this message is constantly coming and i am unable to do anything for the past 2 days
Click to expand...
Click to collapse
To flash back to stock, you have to boot into bootloader and using fastboot to flash factory image.
But hey, you're in the Nexus 6P forum, try following this guide in the Nexus 5X forum:
https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I just went through this. Just unlock your bootloader with the Nexus toolkit and it'll go away that's all i did
Sent from my Nexus 6P using Tapatalk
---------- Post added at 06:45 PM ---------- Previous post was at 06:42 PM ----------
Moddy98 said:
Hello,
just recently i rooted my Nexus 6p device and unlocked the bootloader, i noticed however, after rooting the device i received an error on boot up stating "Your device software can't be checked for corruption. Please lock the bootloader." (Orange), but after researching on the internet many people said that was normal due to the boot loader being unlocked...
however my concern for today is i have flashed back to the factory images of marshmallow, and am now experiencing an error on boot up that Your device is corrupt. It can't be trusted and may not work properly." i followed the exact step-by-step guide on how to unroot and lock the boot loader on the link below however am still experiencing the issue, please help it will be ever so much appreciated.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(the error that i am receiving after flashing stock image)
https://lh3.googleusercontent.com/iGv9RPFbDSLec-4-cvsQNOh46pt5RhEvPy7EKKZXmbtjJ16P7d5EXOJHCIsR=w300
Click to expand...
Click to collapse
It happened to me just last week. Just unlock your bootloader with the Nexus toolkit and it'll go away. That's all i did and it went away i got it the same way you did and that's all I did
Sent from my Nexus 6P using Tapatalk