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!
Related
So I used the Nexus Root Toolkit to flash stock and unroot it, but after using it, I got stuck at the bootloader screen. So I pushed the start button to reboot, and my nexus 7 is still rooted. Help plz?
Give it a try again? I have use this 5 times, work great for me, u have adb fastboot mode on ur desktop?
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Download the stock image and flash in fastboot .
Sent from my Nexus 7 using xda premium
So when i try to fastboot the bootloader .img manually, it says:
sending bootloader ... okay
'writing bootlader'.... failed (remote: (invalid state))
so what do i need to do to fix that?
zeiloz said:
So when i try to fastboot the bootloader .img manually, it says:
sending bootloader ... okay
'writing bootlader'.... failed (remote: (invalid state))
so what do i need to do to fix that?
Click to expand...
Click to collapse
Is your bootloader locked?
Sent from my Nexus 7 using xda premium
it said lock status: unlock
So i would presume its unlocked...
zeiloz said:
it said lock status: unlock
So i would presume its unlocked...
Click to expand...
Click to collapse
OK. I've never seen that error before. And a quick google search doesn't come up with anything either.
You could try restarting the bootloader with
Code:
fastboot reboot-bootloader
and trying again.
The only thing I can think of is you could be trying to flash the wrong bootloader (which i doubt) Just to confirm you are trying to flash bootloader-grouper-3.34.img
Also, to just unroot you don't need to reflash the bootloader. Just boot.img and system.img
El Daddy said:
OK. I've never seen that error before. And a quick google search doesn't come up with anything either.
You could try restarting the bootloader with
Code:
fastboot reboot-bootloader
and trying again.
The only thing I can think of is you could be trying to flash the wrong bootloader (which i doubt) Just to confirm you are trying to flash bootloader-grouper-3.34.img
Also, to just unroot you don't need to reflash the bootloader. Just boot.img and system.img
Click to expand...
Click to collapse
Yes, I am trying to flash bootloader.grouper-3.34.img
And Im flashing bootloader because its I'm told to do in this thread? http://forum.xda-developers.com/showthread.php?t=1781250
I will try what you told me and see if it will work
So i rebooted the bootloader, and it still gives me the same thing. Whats the command to boot.img and system .img?
zeiloz said:
So i rebooted the bootloader, and it still gives me the same thing. Whats the command to boot.img and system .img?
Click to expand...
Click to collapse
Both the boot.img and the system.img are in the image-nakasi-jro03d.zip you must extract them first.
Then run: fastboot devices (to make sure you're connected) if it returns the serial number then proceed.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot erase cache
fastboot reboot
This should maintain your data and unroot your nexus.
However, I am a bit concerned about the invalid state error. I can't find anything about it at all. I'm worried your nand might be corrupted and proceeding with this might lead to an unrecoverable state. Maybe someone else can weigh in on this... I don't want to scare you but I don't want to be responsible if something goes wrong.
hmm... I hope more people would weigh in on this? Cuz im exchanging the nexus 7 due to flickering screens, and im new to the rooting/unrooting stuff so i dont want to brick this device cuz im a n00b.
hmm... I hope someone else weigh in on this to help, cuz I'm going to exchange this nexus 7 for another 1 because of flickering issues...
Restart, carefully check
My nexus had the ghosting issue and I had to unroot my device to ship back today. Heres how I did it.
1. Download stock ROM from Google.
2. Unzip stock ROM from Google. The unzipped file will have 4 files in it. (Boot loader grouper image, flash all.sh, flash base.sh and the image.zip)
3. Unlock your device by clicking the unlock button on nexus root toolkit
4. When your device wakes turns on set it back up. No need to log into Google.
5. turn a dB back on in development
6. Click flash stock + unroot
7. click other/browse
8. For choice click I did this already.
9. Click OK
10. browse to your unzipped file location with the 4 files in it.
11. click OK
12. Done
Sent from my Desire HD using xda premium
I'm facing a similar problem.
http://forum.xda-developers.com/showthread.php?p=31128926
Did you find a way to flash the Bootloader?
I'm thinking about a hardware issue as well. Are there any Devices, with corrupted NAND's known?
Marcus
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
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.
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
Before I describe my issue I'll let you know I've been looking up articles on how to solve this for weeks now. first post to XDA, so bear with me I'm new
I have two OPT, both have a similar problem, but one is working (I dare not try to mess with it) and the other I've already tried and tried and now I'm stuck in fastboot, no recovery, no OS.
I HAD an OS on it (Paranoid Android 6.0.1), but I couldn't factory reset, and I needed to, so that I could sell the phone. when I tried to factory reset through OS settings, it would boot loop until I hard reset the phone. I had no recovery apparently (IDK how I did that) but trying to install a recovery requires the "OEM Unlocking" setting to be checked. and for some reason it won't let me check the box. My working OPT phone has the same problem, the "Allow OEM unlocking?" box pops up, I select enable, and the toggle moves itself back to the grayed out selection. so I couldn't install a custom recovery, I can't do any formatting or erasing in fastboot either without that selection for some reason either. trying to only gives me a "FAILED (remote: device is locked. cannot erase images)" or "FAILED (remote: device is locked. cannot flash images)"
AND SO, I tried this (search google for "mega unbrick guide for a hard bricked oneplus 2". I can't post links apparently as it is my first post. it will be on the oneplus website) and now I have no OS. or at least I believe I have no OS because trying boot causes a bootloop. I've tried all the methods, but I'm assuming because my bootloader is locked, It failed with the "A2001_save_brick_mini" tool.
And so, all I have right now is bootloader. didn't have a recovery I guess, and now I think I don't have an OS. and I can't do anything in fastboot because is returns with a "FAILED" hehe. dang locked bootloader. I have no idea how both of these phones have locked bootloaders anyways, because I obviously unlocked the bootloader to install a custom ROM in the first place. did the bootloader relock itself, or maybe during the process of installing the ROM, the bootloader relocked? I'm not sure as I wasn't watching for that. the phones had booted with the new OS, and so I happily went along my business and didn't find out I had a problem until I tried to factory reset one of them.
no I have no phones now with similar problems, but at different stages of the same issue.
My ONE A2005 is working, but I can't toggle the "OEM unlocking". At least it has a working custom recovery (TWRP)
and MY ONE A2003 is stuck in fastboot (fastboot recognizes it via "fastboot devices" and I can reboot and "fastboot oem device-info") with what I believe to be no recovery or OS.
ask me any questions to further explain my predicament, and PLEASE offer me any things to try. I ave two phones to test different things with. I would prefer to keep the working one working though.
Have you tried the fastboot oem unlock command?
DR_HAX34 said:
Have you tried the fastboot oem unlock command?
Click to expand...
Click to collapse
Ah yes, I forgot to write that in. That also results in a "FAILED (remote: unlock device to use this command)"
I can't unlock because of the OS, or perhaps lack of OS now; And I can't install a new OS or recovery because my bootloader is locked
use qualcomm recovery tool if you can't get any help. it'll restore your phone to 100% stock
Hi All,
Trying to flash an A1 with the following rom images and both give the error of Mismatching image and device.
tissot_images_V9.5.9.0.ODHMIFA_20180316.0000.00_8.0_f8cd1b4e8e
tissot_images_V9.5.11.0.ODHMIFA_20180504.0000.00_8.0_1a04581058
The phone is currently a brick belonging to a friend of mine, and I would like to try and get it back up and running. Fastboot can see the device, as can MiFlash, but when running the command
Code:
Fastboot oem device-info
it throws an error stating
Code:
FAILED (Command write failed (Unknown Error))
Any ideas? The device will boot into fastboot but no further, and gives a warning about being unlocked when you try to boot. I'm not sure how to check if it is a re-branded Mi5x or not, as the box is a Global version A1 box with corresponding IMEI cods to a model MDG2. The phone does have the Android One laser etch on the back however.
By bricked I mean the phone will turn on, load the warning about an unlocked bootloader and then go to the Android One "bars" screen you see before the pretty android one loading screen. Here it just stops.
The drivers i'm using come from the MiFlash install, and I've tried doing a TWRP install with fastboot but still no joy. Fastboot can see the device, and talk with it, but nothing I seem to do has got the kit back working.
Anyone able to give some help or advice?
Further info on what ive tried here
http://en.miui.com/thread-3158263-1-1.html