flash bootloader fails - Nexus 7 Q&A, Help & Troubleshooting

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.

Related

[Q] Rooted, TWRP fastboot flash failed, adb sideload failed, bricked?

So a week ago I flashed 4.4KK with fastboot no problem, restored TWRP, root and went on my merry way. Last night I decided to flash 4.4.2 and it all went pete tong. I went into fastboot and flashed 4.4 boot.img to restore stock kernel (I was on franco) and rebooted the phone to see if I could now update OTA. On reboot I got nothing but black screen but no worries and went back into fastboot to do a flash-all.sh. It went ok up to flash bootloader and I get the error
'writing bootloader...
FAILED (remote: invalid bootloader image)
archive does not contain boot.sig
recovery.sig
system.sig
Checking product: FAILED'
I then tried opening the zip and flashing each component seperately and can flash system, recovery, boot and userdata no problem.
It also will sideload to 100% fine but then just says failed. The problem seems to be with the bootloader-grouper-4.23.img?
No matter what I try it will have a black screen if I try to boot, though I can flash TWRP and go into that and if I reboot from there it says no OS loaded?
Can someone get me out of this mess, I really need my phone working before tomorrow!
Did you ever figure this out? Having the same issue...
carpel21 said:
So a week ago I flashed 4.4KK with fastboot no problem, restored TWRP, root and went on my merry way. Last night I decided to flash 4.4.2 and it all went pete tong. I went into fastboot and flashed 4.4 boot.img to restore stock kernel (I was on franco) and rebooted the phone to see if I could now update OTA. On reboot I got nothing but black screen but no worries and went back into fastboot to do a flash-all.sh. It went ok up to flash bootloader and I get the error
'writing bootloader...
FAILED (remote: invalid bootloader image)
archive does not contain boot.sig
recovery.sig
system.sig
Checking product: FAILED'
I then tried opening the zip and flashing each component seperately and can flash system, recovery, boot and userdata no problem.
It also will sideload to 100% fine but then just says failed. The problem seems to be with the bootloader-grouper-4.23.img?
No matter what I try it will have a black screen if I try to boot, though I can flash TWRP and go into that and if I reboot from there it says no OS loaded?
Can someone get me out of this mess, I really need my phone working before tomorrow!
Click to expand...
Click to collapse
You need to flash factory images for OCCAM which is for the nexus 4. You had downloaded wrong factory images, grouper, which are for the tablet Nexus 7 Jelly Bean version.
carpel21 said:
So a week ago I flashed 4.4KK with fastboot no problem, restored TWRP, root and went on my merry way. Last night I decided to flash 4.4.2 and it all went pete tong. I went into fastboot and flashed 4.4 boot.img to restore stock kernel (I was on franco) and rebooted the phone to see if I could now update OTA. On reboot I got nothing but black screen but no worries and went back into fastboot to do a flash-all.sh. It went ok up to flash bootloader and I get the error
'writing bootloader...
FAILED (remote: invalid bootloader image)
archive does not contain boot.sig
recovery.sig
system.sig
Checking product: FAILED'
I then tried opening the zip and flashing each component seperately and can flash system, recovery, boot and userdata no problem.
It also will sideload to 100% fine but then just says failed. The problem seems to be with the bootloader-grouper-4.23.img?
No matter what I try it will have a black screen if I try to boot, though I can flash TWRP and go into that and if I reboot from there it says no OS loaded?
Can someone get me out of this mess, I really need my phone working before tomorrow!
Click to expand...
Click to collapse
You can't update to the newest android if you are rooted...you need to restore back to stock android before updating..
Sent from my Nexus 4 using XDA Premium 4 mobile app
I suggest returning the phone to stock and starting over.
http://forum.xda-developers.com/showthread.php?t=2010312
taodan said:
You need to flash factory images for OCCAM which is for the nexus 4. You had downloaded wrong factory images, grouper, which are for the tablet Nexus 7 Jelly Bean version.
Click to expand...
Click to collapse
Please listen to this. If you continue in the wrong direction, you are only going to make things worse.
korockinout13 said:
Please listen to this. If you continue in the wrong direction, you are only going to make things worse.
Click to expand...
Click to collapse
Which information is wrong direction?

Bricked Nexus 4, send help. Flashed wrong version of twrp.

I used the WonderHowTo site incorrectly to flash a nexus 5 version of twrp unto my nexus 4.
My device at this point booted to a blank screen. It could still boot the boot loader at this point.
To "fix" this I found the correct version of twrp for my device and proceeded to flash that unto my device.
This has appeared to work since I can access twrp on my device but it is only thing I can access on the phone. When I attempt to boot to system through twrp I am sent back into twrp.
I have attempted to use the wugfresh root tool kit to unroot and return to stock using both soft bricked and phone is still working normally options with no success.
It can still boot to the boot loader currently.
I have logs from the toolkit if these can shed more light on my issue.
Is there anyway I can return my device to stock? Thanks for any response
Flash factory image
https://developers.google.com/android/nexus/images#occam
attempted
attempted to flash stock and got the following error message
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
Seems like you flashed TWRP to /boot. Easy fix is to download your ROM zip. Extract the boot.img and "fastboot flash boot boot.img". Then flash TWRP with "fastboot flash recovery twrp.img"
The locations and filenames of the files may vary. But hopefully you get the idea.
codebam said:
Seems like you flashed TWRP to /boot. Easy fix is to download your ROM zip. Extract the boot.img and "fastboot flash boot boot.img". Then flash TWRP with "fastboot flash recovery twrp.img"
The locations and filenames of the files may vary. But hopefully you get the idea.
Click to expand...
Click to collapse
I flashed a boot image for mako_KTU84P and flashed recovery again with twrp but I'm still system booting into twrp.
My bootloader version is MAKOZ30f if that is any help
I probably flashed the incorrect boot image. Could you point me in the direction of reliable ROM zip's if that is the case.
MrTalk said:
I flashed a boot image for mako_KTU84P and flashed recovery again with twrp but I'm still system booting into twrp.
My bootloader version is MAKOZ30f if that is any help
I probably flashed the incorrect boot image. Could you point me in the direction of reliable ROM zip's if that is the case.
Click to expand...
Click to collapse
Okay adb push a cyanogenmod zip from here and flash it in recovery. It should automatically install a working boot image. You should also flash the latest bootloader in the factory image with "fastboot flash bootloader bootloader.img" if you're using an outdated bootloader.
used the advice
I pushed the zip file using cmd and it appears to have been successful since I was given the summary of data transferred and how long it took once the process was finished.
I can't find the zip file in twrp to attempt to flash it.. Is there any reason the file name would change inside the device once it has been pushed?
Is there a way to flash the zip in question without pushing it unto the device?

Help! "Your device is corrupt. It can't be trusted and may not work properly." (Red)

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

Anyway to unlock oem from bootloader or TWRP?

I was trying to flash the stock image and i guess i messed up somewhere because after i did that i locked the bootloder and not it is not booting past the google screen. i want to reflash all images but i cant cause the bootloader is locked. so is there anyway to unlock the oem in bootloader or recovery mode TWRP? i can access terminal in TWRP so any command that can help me?
TheTickReborn said:
I was trying to flash the stock image and i guess i messed up somewhere because after i did that i locked the bootloder and not it is not booting past the google screen. i want to reflash all images but i cant cause the bootloader is locked. so is there anyway to unlock the oem in bootloader or recovery mode TWRP? i can access terminal in TWRP so any command that can help me?
Click to expand...
Click to collapse
Maybe try and sideloading the it's through twrp. I can't remember if an unlocked bootloader is needed though. Also, you could maybe try flashing a custom ROM to see if you can boot into it.

Help! ([BOOTLOADER] image not signed or damaged)

I unintentionally skip the "format data" link and the all step, so the code unlock the bootloader but I cant flash the recovery it says "[BOOTLOADER] image not signed or damaged", the phone works but I cant flash anything, any ideas?
What device do you have, what (stock) firmware do you have on the device and what firmware are you trying to flash?
Hello is a stock Moto G5 Plus with 7.0 android and I am trying to flash the Vanche's Modified TWRP or the 3.1.2 version but I keep getting the same message "[BOOTLOADER] image not signed or damaged", is like if the BL relock itself.
I think that's a standard warning from the bootloader - TWRP is not signed software, which fastboot expects. However, as your bootloader is unlocked, it'll allow the flashing of TWRP, just with the warning message alerting you to the fact you're not flashing Motorola firmware via fastboot.
1)Do you see [OKAY] appear when you flash the TWRP?
2)After flashing TWRP, do you boot to recovery to fix TWRP? Easiest way is after flashing, on your device (if still in the device bootloader), use the volume keys to select 'Recovery' and press Power to confirm.
The instructions here suggest you need to boot to recovery after flashing to fix TWRP as the recovery, else the stock recovery may overwrite TWRP. https://forum.xda-developers.com/g5-plus/how-to/how-to-root-moto-g5-plus-t3579659 or https://forum.xda-developers.com/g5-plus/how-to/how-to-how-to-supersu-moto-g5-plus-t3587684
ok thanks, I will try that, so skipping the "format data" thing has nothing to do with it?
I'm not sure - though you'd have to unlock your bootloader so your data would be wiped anyway as part of the unlock, and that you'll have to decrypt your data. Perhaps someone with more experience in flashing on G5 plus devices can comment.

Categories

Resources