I have a XT1527 Moto E, and I wanted to flash the 5.1 rom I found (can't link it, but it's the one called surnia retus in motofirmware.centerit), it is stock firmware and my bootloader is locked so I tried flashing by extracting and flashing the contents one per one. It gave me an error saying preflashing validation error. My phone now won't go further past the fastboot, with the logs saying "version downgraded for boot / failed to validate boot image". To me, it sounds like the phone knows that it's not the official firmware for my specific phone or something.
I'm thinking about unlocking the bootloader and then reflashing the rom, maybe even flashing TWRP, formatting everything and then flashing the rom. I don't know if any of this is possible, and I'm nervous about the phone. What should I do?
Puertasamuel said:
I have a XT1527 Moto E, and I wanted to flash the 5.1 rom I found (can't link it, but it's the one called surnia retus in motofirmware.centerit), it is stock firmware and my bootloader is locked so I tried flashing by extracting and flashing the contents one per one. It gave me an error saying preflashing validation error. My phone now won't go further past the fastboot, with the logs saying "version downgraded for boot / failed to validate boot image". To me, it sounds like the phone knows that it's not the official firmware for my specific phone or something.
I'm thinking about unlocking the bootloader and then reflashing the rom, maybe even flashing TWRP, formatting everything and then flashing the rom. I don't know if any of this is possible, and I'm nervous about the phone. What should I do?
Click to expand...
Click to collapse
You most likely will not be able to unlock the bootloader now, as it relies on a setting in the system itself (which will not boot for you.) You are in a tight spot right now, and you have my sympathies! First off, is your phone carrier branded? Secondly, did you get the error message right away, or did you successfully flash some of the firmware before hitting the error?
brotherswing said:
You most likely will not be able to unlock the bootloader now, as it relies on a setting in the system itself (which will not boot for you.) You are in a tight spot right now, and you have my sympathies! First off, is your phone carrier branded? Secondly, did you get the error message right away, or did you successfully flash some of the firmware before hitting the error?
Click to expand...
Click to collapse
I live in Colombia, and every carrier here unlocks their phones, so mine is unlocked and probably uses a generic firmware. The error appeared after I tried flashing one per one, I guess it wrote something, but then the verification failed or something. I had flashed the first file, I think. Please help me, man, I don't know what to do.
Puertasamuel said:
I have a XT1527 Moto E, and I wanted to flash the 5.1 rom I found (can't link it, but it's the one called surnia retus in motofirmware.centerit), it is stock firmware and my bootloader is locked so I tried flashing by extracting and flashing the contents one per one. It gave me an error saying preflashing validation error. My phone now won't go further past the fastboot, with the logs saying "version downgraded for boot / failed to validate boot image". To me, it sounds like the phone knows that it's not the official firmware for my specific phone or something.
I'm thinking about unlocking the bootloader and then reflashing the rom, maybe even flashing TWRP, formatting everything and then flashing the rom. I don't know if any of this is possible, and I'm nervous about the phone. What should I do?
Click to expand...
Click to collapse
I have the same problem in my xt1527 chile
It appears trying to flash the 5.1 to a phone that is bootloader locked and is running the wrong rom for it is an insta-brick. I have yet to see a fix for it. I tried it on a cricket version and it ended up successfully flashing the bootloader and a few other things, but not otheres. That then prevented me from going back to stock because it would require downgrading the bootloader. I sold it online (full disclosure of course) and am buying another one.
Related
I'm getting the "Failed to boot 2, then RSD Starting." I've read that I may not have the correct files, or possibly I'm doing something wrong. Can someone dumb down the correction to my issue? I want to get into recovery, so that I can back up and then install CM7. I think I have the latest versions of everything.
Any help is appreciated. Sorry if this is a repost
Have you unlocked your bootloader ?
I had this *exact* same problem. It occurred as I tried to flash ROM Manager's recovery (from ROM Manager) *before* I unlocked the bootloader. IE, I tried to flash the recovery partition before I was unlocked. I could never recover. I tried the AUTOMATIC... unlock batch program - many options, just about everything.
I ended up using Motorola's official MSU to recover to stock. Then I ran the AUTOMATIC... unlock batch program first. Once unlocked, it was pretty simple after that.
Problems with CWM recovery
jmaddr said:
I had this *exact* same problem. It occurred as I tried to flash ROM Manager's recovery (from ROM Manager) *before* I unlocked the bootloader. IE, I tried to flash the recovery partition before I was unlocked. I could never recover. I tried the AUTOMATIC... unlock batch program - many options, just about everything.
I ended up using Motorola's official MSU to recover to stock. Then I ran the AUTOMATIC... unlock batch program first. Once unlocked, it was pretty simple after that.
Click to expand...
Click to collapse
Hello, i've the same problem. I need to ask before do what you do because i'm a noob. i'm rooted and i flashed CWR
1-Doing the MSU stock recover will hard brick my phone?
2-i've been reading the "What's in this Software Update?" and is says it's for 2.3 GB. It will works for me? i'm 2.2.2 froyo.
I was searching but can't find answers.
Sorry about my english
Thanks
Hello all, I know this is an old phone so not many people care for it anymore, but I was trying to get mine back to stock so I can use it while the phone I am using now is out for repairs. I am having issues getting it back to stock though and these issues resulted in my phone becoming stuck in bootloader. I have relocked my phone and tried both flashing a PG86IMG.ZIP from bootloader and from fastboot, both of them fail. Is there maybe a step I am missing? Or possibly have I completely bricked my phone? Could it be that I need a more updated RUU? (they have been kinda hard to find, it seems that a lot of the mirrors have been taken down.)
Thank you in advance for your help.
Is there a fail message? Do you remember what version rom you had?
Can't remember what version rom I had. It has been a while since I have done anything with it.
You locked with custom rom, recovery, or kernel. Looks like stock was v2.95 or v2.89 problem is they never released a full PG86img.zip for 2.95
I've an update which might fix it or possible 2.89 zip might work. Will upload them when I can. But if you can unlock, then it might be possible to edit misc partition to allow you to install an older rom
I have bricked my phone. It's stucked in a boot loop.
I had an up-to-date, non-rooted, locked XT1524. Since 3G and 4G didn't work on my country, first I tried flashing the modem and baseband from a retail XT1527 stock ROM. The flashing went OK, but 3G and 4G still didn't work (as happened to pablo_cba in this thread).
Then I turned my common sense off and tried flashing the whole XT1527 ROM. I though that since they were stock ROMs I didn't have any need to root the phone (or install TWRP). And since I was flashing the same version I had, I didn't need to unlock the bootloader either. Wrong! The ROM I flashed was version 5.1 (23.29-15), and my current ROM at the moment was 5.0 (22.50-X). Since I haven't unlocked the bootloader, I can't go back to the retail XT1524 stock ROM published here.
I was able to flash gpt.bin and bootloader.img, but things went south on boot.img. Now the bootloader is stuck with the following error:
Code:
version downgraded for boot
failed to validate boot image
Trying to flash boot.img (or system) fails with error:
Code:
hab check failed for boot
Failed to verify hab image boot
Trying to go back to XT1524 ROM fails with:
Code:
version downgraded for aboot
Trying to unlock the bootloader fails with:
Code:
Enable OEM Unlock
Which is obvious because I haven't enabled it on the phone, but it sucks because I can't boot and enable it.
So, here goes my questions:
- What does the "hab check failed" means? Is there any way to bypass it and finish flashing the XT1527 ROM?
- Is there any way to unlock the bootloader without enabling it first on developer settings?
- Is there anything I can do other than waiting that 5.1 gets rolled to XT1524 phones, and that a stock ROM for it gets leaked?
Thanks a lot for your kindly help!
Ah, I know exactly what happened. The good news is that your device is not bricked. The bad news is that you will need to wait a few weeks for the XT1524 5.1 stock images to be released.
The CID is a one byte Motorola specific value that indicates which region your device is for. Boot and system images are signed by Motorola tools that sign for a specific CID. The bootloaders for Motorola phones are signed with qualcomm tools that do not care about CIDs. As a result, you can flash a bootloader meant for a device with a different CID, but you can't flash a boot or system image for a different CID (while bootloader locked).
Since the bootloader is not CID specific, you were able to flash the new bootloader. The new bootloader blows fuses to increment the security version and prevent rollback. It will not allow you to flash an older boot and system image, since they may contain vulnerabilities. Now, the bootloader won't allow you to flash anything except a new 5.1 ROM signed for your CID.
I'd recommend just waiting a few weeks for the signed official 5.1 images for XT1524 to be released.
If you can't wait and are willing to take your phone apart and void the warranty and solder onto stuff, you can circumvent the Factory Reset Protection feature to unlock your bootloader. I don't recommend doing this, but it can be done. You will need to solder onto test points for the flash (that will be located underneath shielding cans). Writing 0x01 to the last byte of the frp partition will enable bootloader unlocking. Once again, I don't recommend doing this, I'm just stating what is possible.
EDIT: It might be worth a try seeing if Motorola will do something under warranty. The challenge will be to explain your problem in a manner that will not make them consider it to have been damaged by you. I don't know what they will think of your issue.
The exact thing happened to me. I think that the 5.1 firmware will arrive soon to your device. I took to my carrier, and they gave a new one in 2 weeks. I think that Motorola won't help you, as you requested the bootloader code.
Hi all! I tried to flash 5.1 retus on a 5.0.2 retla variant (as the tutorial said it would work on all variants, and both are for XT1527) without unlocking the bootloader.
Sadly it won't boot (boots directly to bootloader) and can't go back to stock.
It says: 'version downgraded for boot' 'failed to validate boot image'
This is a problem because everything I find about it says that I should either unlock the bootloader or find a newer retla ROM to flash over. Sad part is that this version is not coming any soon.
I tried to unlock bootloader afterwards but since I've never checked the option inside Dev Options this is like a no-go.
Any ideas?
I received an OTA update on my AT&T M9 and proceeded to unlock the bootloader and flash a custom recovery, and forgot to make a backup of my system before flashing a new rom. Now I can't get any rom to load properly, and can't run the RUU program from HTC on any of my computers. Does anyone have a way of retrieving an official AT&T firmware zip or any solution? I'm at my wit's end, and HTC was no help at all. The phone is S-On, to make matters worse. And any rom I flash that manages to get to the welcome screen hangs at "Connecting to Wi-fi" forever.
Managed to fix it, had to S-Off to reset my firmware version, but to anyone who screwed up like I did, this is the AT&T Marshmallow update to the HTC One. Fixed my problem, and allowed me to restart from the beginning. To anyone that reads this, $25 is a small price to pay for an S-Off.
https://www.htc.com/us/support/htc-one-m9-att/news/