I tried to install android 6.0 XT1521 without unlocking the bootloader, and as it was an official rom motorola believed that would be possible. However it did not work and since I have not unlocked the bootloader, I can not go back to the retail XT1523 stock ROM
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 XT1523 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 XT1521 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 6.0 gets rolled to XT1523 phones, and that a stock ROM for it gets leaked?
Thanks a lot for your kindly help!
Disclaimer: I am not responsible for anything that happens as a result of flashing these files.
Latest Build Nougat: 7.1.1_NPSS26.118-19-18
Latest Build Oreo: 8.0.0_OPSS27.76-12-25-15
Note: Motorola doesn't allow downgrading so once u flash O via OTA/Fastboot it isn't recommended to go back to N or any older build than the latest .
Downloads:
Stock N: ALBUS_RETAIL_7.1.1_NPSS26.118-19-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Stock O: ALBUS_RETAIL_8.0.0_OPSS27.76-12-25-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
You must already have ADB and fastboot setup, check here if you haven't already as using adb/fastboot isn't within the scope of this thread.
How to Install ADB on Windows, macOS, and Linux
1. Download the file and extract the zip archive
2. Extract all the files to your fastboot folder. (Not needed if you have adb and fastboot added to the path, if you want to know how to do this, check this guide: How to Use ADB or Fastboot From Any Directory on your Windows/Linux PC)
3. Restart the device in fastboot/bootloader mode and connect to your PC.
4. Make sure the system detects the device in fastboot mode, to verify this your command window/terminal shows a serial number when you type:
Code:
fastboot devices
5. Use the following commands now or you can use the flash scripts provided as attachments to this post:
NOTE: SKIP the oem lock begin and the oem lock commands if you dont want to lock your bootloader
Linux users will need to change the extension to .sh and add sudo before each command or directly run it as a root user .
To simply flash, run the "OEM Flash" file; to lock the bootloader, run "OEM Lock" file.
Manual method:
Code:
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem lock
fastboot reboot
Credits:
JuniorPassos
TeamReviver
Motorola Mobility LLC
Sourceforge
XDA-Developers
So wait... you can fastboot unlock the Verizon model???
Help please.
Hello,
Could you provide complete stock firmware for the Moto Z2 play (Indian unit), while flashing the TWRP 3.1.10 , it is stuck on boot logo, I again go back to your verizon recovery image flash but now it is looping on the boot phase . Please help me , If you find any useful link please provide me. my region is India.
If I do complete flash of your Verizon's model Z2 on my Indian Z2 unit , whether it will work for me ??? If you have any idea for the Z2 play (General Global unit) , please share us, we will be very thankful to you. Main thing is this it is the new phone so very difficult to find and remedy so far. Thanks
niteshpant said:
Hello,
Could you provide complete stock firmware for the Moto Z2 play (Indian unit), while flashing the TWRP 3.1.10 , it is stuck on boot logo, I again go back to your verizon recovery image flash but now it is looping on the boot phase . Please help me , If you find any useful link please provide me. my region is India.
If I do complete flash of your Verizon's model Z2 on my Indian Z2 unit , whether it will work for me ??? If you have any idea for the Z2 play (General Global unit) , please share us, we will be very thankful to you. Main thing is this it is the new phone so very difficult to find and remedy so far. Thanks
Click to expand...
Click to collapse
Verizon operates in US and you flashed that for Indian version.Why?There is no official ROM out yet.
Most importantly you did not backup the ROM.
My advice would be try clearing the cache,factory reset.
Moto by Lenovo doesn't provide regular updates.
It is better to wait until Lineage OS pays a visit.
Cheers
wait how did you unlock the verizon version？
Update
New firmware BUILD NPSS26.118-19-4 for RETAIL models is added to the downloads.
https://www.androidfilehost.com/?fid=889964283620756684
Hi, do you know if is possible to flash the retail firmware to single sim version? (Vodafone, unlocked)
Hello,
I've accidentally did the oem lock...
What can I do to reverse this?
Do I have to send the smartphone back to Motorola?
Says boot image not signed, it does flash the firmware however it does not have fastboot flash system system.img_sparsechunk.7 in the zip folder so it doesn't actually flash it. However it does boot up and work like normal.
any word on this working on the canadian version?
it reads as XT1710-01 in fastboot
in the OS my current build number reads as NPSS26.118-19-11 ... i assume thats just a slightly newer version
and so, installing this would return the phone to pure stock - allow OTA and all that fun stuff?
unerds said:
any word on this working on the canadian version?
it reads as XT1710-01 in fastboot
in the OS my current build number reads as NPSS26.118-19-11 ... i assume thats just a slightly newer version
and so, installing this would return the phone to pure stock - allow OTA and all that fun stuff?
Click to expand...
Click to collapse
FYI, XT 1701-01 is the US unlocked for any carrier version.
Does this work for the xt1710-09 reteu version?
Can't flash this on xt1710-09 reteu. Says boot.img is not signed. I SO DESPERATELY want to relock my bootloader.. but it doesn't seem to work Any ideas?
I can confirm XT1710-01 works for Freedom Mobile in Canada.
I was rooted and the Motorola got into a Recovery bootloop after a security update. Makes me miss the peace of mind of Cyanogen. Hopefully LinageOS will come here soon.
cal800 said:
I can confirm XT1710-01 works for Freedom Mobile in Canada.
I was rooted and the Motorola got into a Recovery bootloop after a security update. Makes me miss the peace of mind of Cyanogen. Hopefully LinageOS will come here soon.
Click to expand...
Click to collapse
I use Titanium Backup to freeze the Motorola Update App. No more update notifications.
Help! First time trying to flash a ROM and it doesn't go well So far
I got my hand on a chinese Model of the phone. It says XT1710-11. From the first day I was fed up with their safecenter telling me everything on my phone was a virus. Then I realised I could not remove it because it was part of the "Firmware". Things got really bad when I could not use Pinterest or Twitter on the phone. I still dont know why.
So I remembered there was this thing called root that might be helpful. I started experimenting on it and I was finally able to root and installed magisk. But I still didnt know what to do so I decided it will be better to just flash a new ROM and found this trhread....
As I am writing this my phone doesnt have a OS, Back up was wiped at a point I even had to reflash TWRP and remount Data to be able to do anything with it.
I have an old iphone5 lying around that I will go back to in the mean time. But guys please help a poor lost soul. Is there a solution to my trouble?
tywinlannister7 said:
Retail Variant
BUILD: NPSS26.118-19-4
https://www.androidfilehost.com/?fid=889964283620756684
Click to expand...
Click to collapse
Add new Retail version.
https://androidfilehost.com/?fid=889964283620776139
NPSS26.118-19-1-2
Patch - December 1, 2017
Junior Passos said:
Add new Retail version.
https://androidfilehost.com/?fid=889964283620776139
NPSS26.118-19-1-2
Patch - December 1, 2017
Click to expand...
Click to collapse
Hello its compatibilty in Reteu 1710-09 ? Very thanks
Regards
Enviado desde mi Moto Z2 Play mediante Tapatalk
iron maiden said:
Hello its compatibilty in Reteu 1710-09 ? Very thanks
Regards
Enviado desde mi Moto Z2 Play mediante Tapatalk
Click to expand...
Click to collapse
Probably. I believe so, because it's a Retail version.
Junior Passos said:
Probably. I believe so, because it's a Retail version.
Click to expand...
Click to collapse
hello the ota that you climbed December gives me error in my reteu with November patch then I do not know if it is compatible with the firmware that you uploaded thanks
regards
hello folks,
I was on Android 7.0 on my Moto G 4.
I unlocked the bootloader, installed TWRP and flashed Android 7.1.2 and then 8.0 a week later.
Had backed up the stock Android 7.0 and the 7.1.2 also before i went to 8.0.
Today i restored the system back to the Stock version backup (7.0) and rebooted it.
Everything went fine. Then there was the notification of the Android security update. I proceeded with the install and it started rebooting.
In the reboot it stuck with the error message for bootlocker being unlocked and came back to TWRP. Even after going to reboot it only came back to TWRP. I then tried logged into the bootloader and tried to relock the bootloader using the commands (i was using mfastboot)
mfastboot oem lock
mfastboot flashing lock
mfastboot oem relock
it showed me an error for the 'relock' that it was an invalid command. Later i found that the unlock key also needs to be supplied (not sure). Then i tried the commands again after installing fastboot, and from the stock firmware folder.
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
it showed me an error on this l9ast command saying invalid boot mode.
Any advise on how to start the relock process cleanly? my worry is if the system is bricked !
I was missing the stock moto so i need to go back there, all the flashing didn't seem too worthwhile.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Solution is in mentions by echo92 in the post by tywinlannister7 below
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
anoopgkris said:
hello folks,
I was on Android 7.0 on my Moto G 4.
I unlocked the bootloader, installed TWRP and flashed Android 7.1.2 and then 8.0 a week later.
Had backed up the stock Android 7.0 and the 7.1.2 also before i went to 8.0.
Today i restored the system back to the Stock version backup (7.0) and rebooted it.
Everything went fine. Then there was the notification of the Android security update. I proceeded with the install and it started rebooting.
In the reboot it stuck with the error message for bootlocker being unlocked and came back to TWRP. Even after going to reboot it only came back to TWRP. I then tried logged into the bootloader and tried to relock the bootloader using the commands (i was using mfastboot)
mfastboot oem lock
mfastboot flashing lock
mfastboot oem relock
it showed me an error for the 'relock' that it was an invalid command. Later i found that the unlock key also needs to be supplied (not sure). Then i tried the commands again after installing fastboot, and from the stock firmware folder.
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
it showed me an error on this last command saying invalid boot mode.
Any advise on how to start the relock process cleanly? my worry is if the system is bricked !
I was missing the stock moto so i need to go back there, all the flashing didn't seem too worthwhile.
Click to expand...
Click to collapse
I'm not sure about this. As far as I know you can only relock the bootloader after a full (fastboot) wipe and install of the latest stockrom.
In the (far) past I managed to relock the bootloader of my Moto G 2014. Only after trial and error and only after a full flash. A week or so later I unlocked again....
I never relocked my Moto G4 Plus, nor my Moto G5 Plus. Simply because I don't see the need. The times that Motorola provides us with regular stock updates are, apparantly, over....
Thanks, Harro.
I thought that my TWRP would restore it back to stock. I read some half information about relocking and went ahead with the commands.
I also don't know if the USB debug settings are on.
It's shows a preflash verification error on the partition gpt.bin command. Think it's because maybe the stock version i downloaded is a downgrade. Can't find the exact stock for my LATAM dds_cust one. Another G4(Plus) version that was successful for others didn't work too.
Tried to skip and load boot partition but it said invalid boot state.
Need to keep trying different things. At least the bootloader and TWRP recovery are accessible for now.
Regards.
anoopgkris said:
Thanks, Harro.
I thought that my TWRP would restore it back to stock. I read some half information about relocking and went ahead with the commands.
I also don't know if the USB debug settings are on.
It's shows a preflash verification error on the partition gpt.bin command. Think it's because maybe the stock version i downloaded is a downgrade. Can't find the exact stock for my LATAM dds_cust one. Another G4(Plus) version that was successful for others didn't work too.
Tried to skip and load boot partition but it said invalid boot state.
Need to keep trying different things. At least the bootloader and TWRP recovery are accessible for now.
Regards.
Click to expand...
Click to collapse
Hi Anoop!
Yes, you'll have find the latest stockrom for your region. Also, a locked bootloader and TWRP is, in my humble opinion, a impossible combination. You'll have to fastboot install the whole rom, including (stock)recovery and the bootloader. And indeed: it's impossible to downgrade the bootloader: trying that will possibly result in a hardbrick...
Thank you, thank you for jumping in to always help.
Really sad that Moto also goes the way of not providing updates that too on a not so old phone. ROMs and the beautiful world of XDA is there, hopefully.
Hey Guys,
I´m using a Motorola One xt1941-4. I tried to flash my phone since extensive googling suggested that this would be the only remedy for the issue of my phone only charging in fastboot mode.
I tried to do this with a locked bootloader since the $ fastboot oem get_unlock_data return failed: Unlock data unavailable. I flashed with what was the newest update from the lolinet servers via the sequence of commands given in the servicefile. During that i was unable to flash the boot.img though, which is, I imagine due to the locked bootloader. i still went through with the flashing.
Obviously it didn´t work though since my phone is now alwys going directly into fastboot showing this:
AP Fastboot Flash Mode (Secure)
SSM: boot image roll back: 11,12
failed to validate boot image
I thought this might be because i have to flash the exact firmware update i had installed preflash. I´m not sure which one that was though. I tried to flash all the available firmware on lolinet for my xt1941-4 to get the correct one- unsuccessfully. Help?
PirxRaumpilot said:
Hey Guys,
I´m using a Motorola One xt1941-4. I tried to flash my phone since extensive googling suggested that this would be the only remedy for the issue of my phone only charging in fastboot mode.
I tried to do this with a locked bootloader since the $ fastboot oem get_unlock_data return failed: Unlock data unavailable. I flashed with what was the newest update from the lolinet servers via the sequence of commands given in the servicefile. During that i was unable to flash the boot.img though, which is, I imagine due to the locked bootloader. i still went through with the flashing.
Obviously it didn´t work though since my phone is now alwys going directly into fastboot showing this:
AP Fastboot Flash Mode (Secure)
SSM: boot image roll back: 11,12
failed to validate boot image
I thought this might be because i have to flash the exact firmware update i had installed preflash. I´m not sure which one that was though. I tried to flash all the available firmware on lolinet for my xt1941-4 to get the correct one- unsuccessfully. Help?
Click to expand...
Click to collapse
Try fastboot getvar all command.
It should at least give you info about which update channel you're on and probably fingerprint as well. This would hopefully help in finding the right firmware for your device.
I have two N200.
I successfully rooted both of them. Some how the second phone got updated to android 12 and lost the root. Ever since this is a headache. Phone is already unlocked boot loader and shows "Device state - unlocked" in fastboot mode.
I wanted to try booting from the patched boot.img i had earlier (From version 11 i assume) just to see if it works but the command fails:
fastboot boot boot.img
Sending 'boot.img' (98304 KB)
Booting Failed (remote: 'unknown command')
fastboot: error: Command failed
Also maybe this is due to being on android 12? If so how can i downgrade? I downloaded the zip file from:
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
Thank you.
First, I don't think you can use your previous boot. Scanman has a thread on this forum with all pre-rooted boot files, you just need to match according to the FW you're on. Second, after A12 they don't allow fastboot boot anymore, the file has to be flashed instead with fastboot flash.
Again, make sure you use the correct boot otherwise it won't work and you may cause yourself a bigger headache.