Related
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.
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.
I was wondering if the S6 on Vodafone in the UK came with a locked bootloader, and if so how difficult was it to unlock? I have an S7 Edge on pre-order, and presume that would come locked too if the S6 did. I can't live without root. Cheers.
No one has an S6 Edge on Vodafone?
Beefheart said:
I was wondering if the S6 on Vodafone in the UK came with a locked bootloader, and if so how difficult was it to unlock? I have an S7 Edge on pre-order, and presume that would come locked too if the S6 did. I can't live without root. Cheers.
Click to expand...
Click to collapse
Seems so, as I have had the same problem by installing MM 6.0.1 firmware with the UK csc code VOD (appearing as BTU on phone). The bootloader wouldn't let me flash TWRP through ODIN (sorry, could flash, but not boot into TWRP, stuck on bootloader).
So i took the provided MM 6.0.1. bootloader from Carotix CarHDRom, flashed it together with at the same place provided TWRP for
MM (the old 2.8.7.0/2.8.7.1 or even new TWRP 3.0 provided on the homepage of TWRP.me , won't work on MM) throught ODIN.
Within TWRP flashed hybridmax's S5E-AELKernel_MM...kernel 1.5 and superSU beta 2.67 (previosly stored/copied to the mobile device) and rebooted - rooted and all working fine.
Take a look at : http://forum.xda-developers.com/galaxy-s6-edge/development/rom-carhdrom-1-t3111519
coco722 said:
Seems so, as I have had the same problem by installing MM 6.0.1 firmware with the UK csc code VOD (appearing as BTU on phone). The bootloader wouldn't let me flash TWRP through ODIN (sorry, could flash, but not boot into TWRP, stuck on bootloader).
So i took the provided MM 6.0.1. bootloader from Carotix CarHDRom, flashed it together with at the same place provided TWRP for
MM (the old 2.8.7.0/2.8.7.1 or even new TWRP 3.0 provided on the homepage of TWRP.me , won't work on MM) throught ODIN.
Within TWRP flashed hybridmax's S5E-AELKernel_MM...kernel 1.5 and superSU beta 2.67 (previosly stored/copied to the mobile device) and rebooted - rooted and all working fine.
Take a look at : http://forum.xda-developers.com/galaxy-s6-edge/development/rom-carhdrom-1-t3111519
Click to expand...
Click to collapse
Did you have the OEM Unlock toggle in dev options?
Beefheart said:
Did you have the OEM Unlock toggle in dev options?
Click to expand...
Click to collapse
Do not know if or not.
Just flashed first the original VOD 6.0.1 fw and then tried to have a working TWRP recovery, but could't boot into TWRP recover, the original bootloader did not let me... this for, bootloader and twrp from carotix (and eventually his provided kernel and/or rom) , and everything goes fine.
coco722 said:
Do not know if or not.
Just flashed first the original VOD 6.0.1 fw and then tried to have a working TWRP recovery, but could't boot into TWRP recover, the original bootloader did not let me... this for, bootloader and twrp from carotix (and eventually his provided kernel and/or rom) , and everything goes fine.
Click to expand...
Click to collapse
My understanding of a locked bootloader is that you can't flash anything that isn't official, including a replacement bootloader, which you indicate you did successfully. Otherwise Verizon Samsung customers would simply flash a new bootloader over their locked one. Ever TWRP wouldn't have flashed, it would have kicked out an error in Odin as you made the attempt because the bootloader wouldn't have allowed it. It sounds like your attempt at flashing it finished successfully, but just wouldn't boot into it. I'm wondering if this was caused by something other than the bootloader being locked.
Beefheart said:
My understanding of a locked bootloader is that you can't flash anything that isn't official, including a replacement bootloader, which you indicate you did successfully. Otherwise Verizon Samsung customers would simply flash a new bootloader over their locked one. Ever TWRP wouldn't have flashed, it would have kicked out an error in Odin as you made the attempt because the bootloader wouldn't have allowed it. It sounds like your attempt at flashing it finished successfully, but just wouldn't boot into it. I'm wondering if this was caused by something other than the bootloader being locked.
Click to expand...
Click to collapse
All possible. However, sometimes we'll just have to give it a try, by using the information and software available. I do have to mention, that my mobile is/was provider-free (not locked to a specific provider). But even a locked mobile can be handeld to get
in free and unlocked. In such case, this should be done first and after that the upgrade to rooted MM and ROM, etc.
No worries, cheers for the reply. I'll wait until I receive it then simply return it and cancel the contract if it's locked.
Hi, i had the same problem. I flashed TWRP, but i could not boot to TWRP. I found that I also have locked bootloader. No OEM Unlock toggle in dev options.
Login on this site
https://findmymobile.samsung.com/login.do
and try Disable Reactivation lock if you can.
vrzy007 said:
Hi, i had the same problem. I flashed TWRP, but i could not boot to TWRP. I found that I also have locked bootloader. No OEM Unlock toggle in dev options.
Login on this site
https://findmymobile.samsung.com/login.do
and try Disable Reactivation lock if you can.
Click to expand...
Click to collapse
I've not received my phone yet, but this doesn't look good. Were you able to disable the reactivation lock on your S6? Or, alternatively, like coco722, were you able to simply overwrite the bootloader? I'm not concerned with Knox or Vodafone's warranty, as long as I'm able to overcome the locked bootloader and root.
hey everyone. trying to OEM unlock the TWRP bootloader. When I type "fastboot OEM unlock" it will reboot into TWRP bootloader, and nothing unlocks. I know this because when I type "fastboot oem device-info" it says "unlocked FALSE".
I have OEM unlock and USB debugging enabled.
This is a phone with previously successfully installed CM13, and now I'm trying to revert to stock/unrooted. I can't seem to flash the recovery at all here because I can't get the damn thing to unlock.
Any ideas?
Did you lock the bootloader ? If your flashing Roms and custom recoverys imagine its already unlocked. Bootloader won't lock itself. If you want full stock just flash any OS2 firmware with twrp. You can worry about stock recovery after. I would just leave the bootloader unlocked won't hurt anything.
I had the same issue not long ago. Finally, i used the mega unbrick guide, but warning, all the data is lost
Ps: Sorry for bad english
hey, thanks for the response. I have been following the following tutorial (and others similar for installing CM13):
(great, website won't let me post it here... it's the unlockr oneplus x guide)
so yes, I originally flashed the stock recovery and replaced it with the one from the tutorial. There were a few hiccups during setup, which may have affected why I can't easily update nightly now, so now I'm trying to revert to the unrooted stock state so I can try from scratch, hopefully fixing the issues I'm seeing now. The problem is that I can't flash the recovery using the stock recovery... I can't even update the damn recovery because it's locked. Is this what is meant by a 'soft brick' ?
I Got a new XT1926-7 EVERT from Amazon today.
Did OTA to PPWS29.116-11-13 (Nov.1, 2019 update) , everything stock, no warnings, Google Pay worked fine.
Then unlocked BL and then > Settings > System Update > see "System integrity is compromised..... no longer eligible for software updates"
Then I have re-locked BL with 'fastboot oem lock'.
Still, Settings > System Update > see "System integrity is compromised.....no longer eligible for software updates"
Google Pay is not working
On reboot, warning message: "Your device has loaded a different OS".
BTW, On BL screen, "flashing_locked"
in Developer options, OEM unlocking is set to left (locked)
I have a second identical phone which I flashed to stock EVERT_RETAIL_9.0_PPWS29.116-11-11 and re-locked BL, same result.
So, it looks like there is no way to return to clean stock after BL has been unlocked.
Once you have unlocked the BL you won't get back to the "locked" state, only to "relocked". To solve your problem regarding the updates you have to install Magisk.
WoKoschekk said:
Once you have unlocked the BL you won't get back to the "locked" state, only to "relocked". .
Click to expand...
Click to collapse
and the "relocked" state appears to be not eligible for future OTA updates
You can receive OTA updates in any case, but your FW must be complete stock to install it. It doesn't matter if your BL is unlocked or not.
The info under settings > System updates does not have any effect on it.
Hey there,
I wanna bring up this topic. I used a moto g6 plus for about a half year now with just bootloader unlocked and magisk rooted.
When there was an update I got it installed via Download on Lolinet and flash command no erase found here on xda.
So now I wanna resell the phone again. Of course I will tell the potential buyers about the unlocked bootloader but I wanted to bring it to stock and OTA able again.
So I thougt reflashing the stock downloaded from lolitnet and relocking the bootloader would do the job. Well no.
If the Reteu Version (which is my phone) from Lolinet is not 100% stock, where can I find something to flash on it for doing the job and letting disappear the "Your device has loaded a different OS" prompt?
Thank you out there.
Dennis
Hobbygamer27 said:
Hey there,
I wanna bring up this topic. I used a moto g6 plus for about a half year now with just bootloader unlocked and magisk rooted.
When there was an update I got it installed via Download on Lolinet and flash command no erase found here on xda.
So now I wanna resell the phone again. Of course I will tell the potential buyers about the unlocked bootloader but I wanted to bring it to stock and OTA able again.
So I thougt reflashing the stock downloaded from lolitnet and relocking the bootloader would do the job. Well no.
If the Reteu Version (which is my phone) from Lolinet is not 100% stock, where can I find something to flash on it for doing the job and letting disappear the "Your device has loaded a different OS" prompt?
Thank you out there.
Dennis
Click to expand...
Click to collapse
Lenovo Smart Assistant.
Peace.