Database Users

[Q] OTA Relocked Bootloader, Bricked Device

Some strange experience to report.
Flashed my unlocked (had been running CM11 beforehand) RAZR M to stock using Matt's utility (all modems, kernel, system and recovery) and everything worked fine.
After booting, I decided to accept OTA update (had done this before without any problems)
Device booted into recovery, flashed the OTA, and booted straight into fastboot, telling me my device's bootloader is now locked (status code 0) and that I can no longer use Matt's utility to flash anything (my guess is something messed up the partitions)
AP Fastboot:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e94557, 2013-05-24 14:49:34)
eMC Info: Size 8GB
Device is LOCKED, Status Code 0
Battery OK
Transfer Mode:
USB Connected
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
Click to expand...
Click to collapse
Anyone got any ideas what might have caused this, and what can be done to fix it?

Leraeniesh said:
Some strange experience to report.
Flashed my unlocked (had been running CM11 beforehand) RAZR M to stock using Matt's utility (all modems, kernel, system and recovery) and everything worked fine.
After booting, I decided to accept OTA update (had done this before without any problems)
Device booted into recovery, flashed the OTA, and booted straight into fastboot, telling me my device's bootloader is now locked (status code 0) and that I can no longer use Matt's utility to flash anything (my guess is something messed up the partitions)
AP Fastboot:
Anyone got any ideas what might have caused this, and what can be done to fix it?
Click to expand...
Click to collapse
Try flashing each file through Mfastboot.
Code:
mfastboot flash partition gpt_main0.bin
mfastboot flash logo logo.bin
mfastboot flash system system.img
mfastboot flash boot boot.img
mfastboot flash fsg fsg.mbn

ATTACK said:
Try flashing each file through Mfastboot.
Code:
mfastboot flash partition gpt_main0.bin
mfastboot flash logo logo.bin
mfastboot flash system system.img.ext4
mfastboot flash boot boot.img
mfastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
When flashing anything via fastboot (or mfastboot)
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'partition' (32KB)...
OKAY [ 0.074s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.383s
Click to expand...
Click to collapse

Leraeniesh said:
When flashing anything via fastboot (or mfastboot)
Click to expand...
Click to collapse
Have you tried RSDLite? What version of firmware are you flashing? It looks like you flashed a downgraded GPT partition.

ATTACK said:
Have you tried RSDLite? What version of firmware are you flashing? It looks like you flashed a downgraded GPT partition.
Click to expand...
Click to collapse
Have also tried RSD Lite (5.6 and 6.1.5) with similar results
I just flashed the OTA that VZW sent my way.
EDIT: Was able to get it to flash using HouseofMoto's RSD XML.
All good

Leraeniesh said:
Have also tried RSD Lite (5.6 and 6.1.5) with similar results
I just flashed the OTA that VZW sent my way.
Click to expand...
Click to collapse
And you tried to restore 98.30.1? I know with the leak, it is a two part flashing process. It will reboot after part 1, then you need to reboot into recovery to start part 2. You may need to wait until there's a FXZ to fix it.

This is scary. Ive just RSD'd back to stock and am about to update my phone with all the OTA's. Perhaps ill stop for now.
EDIT: And the OTA process just failed from Stock update. FML.

Maybe try this? This is sourced from Moto's website
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/91999/p/1449,8620

If anyone else experiences something similar, you can follow jimyv's post regarding setting up RSD to flash (despite something going wonk with the partition table)

I am having this same issue, I tried the house of moto tutorial and my result is everything failed. Any other suggestion will be greatly appreciated

techfellow said:
I am having this same issue, I tried the house of moto tutorial and my result is everything failed. Any other suggestion will be greatly appreciated
Click to expand...
Click to collapse
How did "everything fail?" Just need more details.

xKroniK13x said:
How did "everything fail?" Just need more details.
Click to expand...
Click to collapse
I've been trying this for the past 2 days. I just tried it again so I can give you details, and it worked without any issues, so I'm good.
Thanks to all the previous posters, and the house of moto maker.

[GUIDE][NOOB FRIENDLY] Explaining Boot loader Locking [ERROR][FIX]

Hi , guys after been long time i jumped from my old Galaxy Ace to these MOTO G2 , the concept of rooting and flashing on the Ace was very different from these new devices , we used to have one click flash got ROOT and again with one flash we got UNROOT , tada !
But in these devices for rooting we need to first unlock the boot loader and then we are free to root it or flash or any modding , but what if have to unroot and lock the boot loader ? , though unrooting is a quite a just one click we got unrooted phone but at the time of locking Bootloader we face errors .But why to lock it again ? though every one has different thinking but these is for those who want to lock . But at the time of locking ERRORS What are they ? how to solve them ? searching over the whole Internet but didn't found a proper solution ! So these type of situation is very critical for new users who are new to these like me ( jokes apart) . So below i have explained a little bit & a fail safe process , I am not taking about tools and download links for them just a process .
Click to expand...
Click to collapse
Various ERRORS which we face like
Code:
(bootloader) sst lock failure!
OKAY [ 0.011s]
finished. total time: 0.012s
Code:
failed to validate system image
Code:
Executing ".\Windows\fastboot.exe flash boot boot.img"
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.505s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.090s
Click to expand...
Click to collapse
These type of error we face while locking boot loader , now do note these things first of check out the build number of your phone & download the same build number firmware , or if there is updated version then you can download that . Because OEM doesn't allow you to downgrade the system it will give you error like system downgrade started & then failed to validate system image so flash the same build version firmware or higher one . By doing these follow the same steps as stated here @archies20 in his thread
Click to expand...
Click to collapse
Code:
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
mfastboot.exe reboot
Click to expand...
Click to collapse
Now by following the above procedure in the between watch out in your phone the screen will be black , and you will get to see the Locked status will be written after that the last error will be like
Code:
C:\MOTOROLA\mfastboot-v2>mfastboot.exe oem lock
...
FAILED (status read failed (Too many links))
finished. total time: 20.117s
But don't get panic the boot loader will be locked still the Unlock warning logo will be there so just flash the logo.bin .
Click to expand...
Click to collapse
Note : Don't try to lock the boot loader after flashing the firmware it will give you error like
Code:
(bootloader) sst lock failure!
OKAY [ 0.011s]
finished. total time: 0.012s
so follow the above procedure only , if you checked out the whole thing then there will be 0% chances of failing .
I hope you will found these thread very helpful ,
Thankyou
Click to expand...
Click to collapse
.
EDIT : You can downgrade via Fastboot not mFastboot.

Bootloader warning
I followed the steps exactly , and the only error occurred was the one you mentioned ,
but the "bootloader unlocked warning " still remains after i flashed the logo
what is the soulution ?
thankyou,

Good job hitesh :good:

If i relock the bootloader will miss the root?

Sebastian94 said:
If i relock the bootloader will miss the root?
Click to expand...
Click to collapse
Yes.

archies20 said:
Good job hitesh :good:
Click to expand...
Click to collapse
Thanks buddy , just i cleared all doubt's and errors .

ghostcoder said:
I followed the steps exactly , and the only error occurred was the one you mentioned ,
but the "bootloader unlocked warning " still remains after i flashed the logo
what is the soulution ?
thankyou,
Click to expand...
Click to collapse
First just check the Bootloader status in bootloader menu , if it is locked then just flash the logo.bin that's it .

OK, first you are giving instructions to flash the firmware and then to send command "lock oem" (the last line).
Later in your post:
Note : Don't try to lock the boot loader after flashing the firmware it will give you error like
sst lock failed.
This is exact error everyone gets, even following your steps (lock begin -> flash firmware -> oem lock).
This guide is misleading.

linasmit said:
OK, first you are giving instructions to flash the firmware and then to send command "lock oem" (the last line).
Later in your post:
Note : Don't try to lock the boot loader after flashing the firmware it will give you error like
sst lock failed.
This is exact error everyone gets, even following your steps (lock begin -> flash firmware -> oem lock).
This guide is misleading.
Click to expand...
Click to collapse
You are not getting properly , i told that after flashing firmware and after booting it , then taking back into boot loader now in these state if you will give command then it wont work !!
That's the point i have explained in that Note .
And above what ever i have written it is 100% working not only tested by but also some other users .

Cannot relock bootloader
Hitesh2626 said:
.
Click to expand...
Click to collapse
I have Global version. then flashed US version and upgrade to lollipop. Later decided to go back to Global version for using CF-autoroot. SO I downgraded to KitKaT US first. I again then changed to global version.
The problem is, now, I cannot relock bootloader. I can chage to us and also in us version i cannot relock.
While I flash Fastboot flash boot boot.img it says downgrading; same for Fastboot flash system system.img_sparsechunk.0; downgrading error as well as invalid piv signed system image error.
Thus after mfastboot.exe oem lock command, it gives SST lock failure ! failed to validate system image in device display.
Applied flash according to :
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
Click to expand...
Click to collapse
my mobile version info is attached

Anonymous 360 said:
I have Global version. then flashed US version and upgrade to lollipop. Later decided to go back to Global version for using CF-autoroot. SO I downgraded to KitKaT US first. I again then changed to global version.
The problem is, now, I cannot relock bootloader. I can chage to us and also in us version i cannot relock.
While I flash Fastboot flash boot boot.img it says downgrading; same for Fastboot flash system system.img_sparsechunk.0; downgrading error as well as invalid piv signed system image error.
Thus after mfastboot.exe oem lock command, it gives SST lock failure ! failed to validate system image in device display.
Applied flash according to :
my mobile version info is attached
Click to expand...
Click to collapse
+1 i cant flash the stock rom with mfastboot.exe oem lock begin if i use tht command .. am facing failed to validate system image plz help me to get out of here plz:crying:

pradeepmaddy said:
+1 i cant flash the stock rom with mfastboot.exe oem lock begin if i use tht command .. am facing failed to validate system image plz help me to get out of here plz:crying:
Click to expand...
Click to collapse
You can try this, for the first time with US version, as far as i can remember, it worked for me. But now, after downgrading and changing back to the global version, it is not working.....
Fastboot oem lock begin
Fastboot flash partition gpt.bin
Fastboot flash motoboot motoboot.img
Fastboot flash logo logo.bin
Fastboot flash boot boot.img
Fastboot flash recovery recovery.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 modem NON-HLOS.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Fastboot erase cache
Fastboot erase userdata
Fastboot oem lock
Fastboot reboot
Click to expand...
Click to collapse
please, inform me, if it works

Anonymous 360 said:
You can try this, for the first time with US version, as far as i can remember, it worked for me. But now, after downgrading and changing back to the global version, it is not working.....
please, inform me, if it works
Click to expand...
Click to collapse
The user u have quoted is trying to lock the bootloader for Global version retaildsds.en03
If it works then its well & good..

Solved! Solved! Solved!
YEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE!!!!
After lots of flashing, at last ::fingers-crossed:
followed these steps:
after downgrading, go to bootloader, install twrp 2801 and flash supersu2.16 (that means, root your device ! ))
reboot and copy your lollipop update file (same variant) to the internal storage
now, again go to bootloader and flash the recovery: Fastboot flash recovery recovery.img
Now go to recovery and select your lollipop update... ta-da.... explanation:
After entering recovery node, Press the Volume Up and Volume Down buttons for around 5 seconds. Now while holding those two, press and release the Power button.
Your device will now be booted into stock recovery mode, displaying Android System Recovery <3e> text at the top of the screen.
apply adb trougt sdcard.... select file AND WAIT TO THE PROCess to finish
You dont need to lock the bootloader at all :good: :good:
Hit thanks if it helps

Anonymous 360 said:
YEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE!!!!
After lots of flashing, at last ::fingers-crossed:
followed these steps:
after downgrading, go to bootloader, install twrp 2801 and flash supersu2.16 (that means, root your device ! ))
reboot and copy your lollipop update file (same variant) to the internal storage
now, again go to bootloader and flash the recovery: Fastboot flash recovery recovery.img
Now go to recovery and select your lollipop update... ta-da.... explanation:
After entering recovery node, Press the Volume Up and Volume Down buttons for around 5 seconds. Now while holding those two, press and release the Power button.
Your device will now be booted into stock recovery mode, displaying Android System Recovery <3e> text at the top of the screen.
apply adb trougt sdcard.... select file AND WAIT TO THE PROCess to finish
You dont need to lock the bootloader at all :good: :good:
Hit thanks if it helps
Click to expand...
Click to collapse
Do you still have your device rooted after lollipop update?

Anonymous 360 said:
I have Global version. then flashed US version and upgrade to lollipop. Later decided to go back to Global version for using CF-autoroot. SO I downgraded to KitKaT US first. I again then changed to global version.
The problem is, now, I cannot relock bootloader. I can chage to us and also in us version i cannot relock.
While I flash Fastboot flash boot boot.img it says downgrading; same for Fastboot flash system system.img_sparsechunk.0; downgrading error as well as invalid piv signed system image error.
Thus after mfastboot.exe oem lock command, it gives SST lock failure ! failed to validate system image in device display.
Applied flash according to :
my mobile version info is attached
Click to expand...
Click to collapse
Anonymous 360 said:
YEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE!!!!
After lots of flashing, at last ::fingers-crossed:
followed these steps:
after downgrading, go to bootloader, install twrp 2801 and flash supersu2.16 (that means, root your device ! ))
reboot and copy your lollipop update file (same variant) to the internal storage
now, again go to bootloader and flash the recovery: Fastboot flash recovery recovery.img
Now go to recovery and select your lollipop update... ta-da.... explanation:
After entering recovery node, Press the Volume Up and Volume Down buttons for around 5 seconds. Now while holding those two, press and release the Power button.
Your device will now be booted into stock recovery mode, displaying Android System Recovery <3e> text at the top of the screen.
apply adb trougt sdcard.... select file AND WAIT TO THE PROCess to finish
You dont need to lock the bootloader at all :good: :good:
Hit thanks if it helps
Click to expand...
Click to collapse
bro am in kitkat now... i dont want to go with us variants again but i want to lock boot loader in kitkat itself please give me the solution for tht

I afraid I do not have a solution......
---------- Post added at 06:38 PM ---------- Previous post was at 06:35 PM ----------
You still have SU app, but you will not have the binary, so you have to appy CF auto root : http://forum.xda-developers.com/moto-g-2014/help/solved-cf-chainfire-autoroot-problem-t2942154

Help please
pradeepmaddy said:
+1 i cant flash the stock rom with mfastboot.exe oem lock begin if i use tht command .. am facing failed to validate system image plz help me to get out of here plz:crying:
Click to expand...
Click to collapse
I've got an XT1068 bought in UK.......and stuck with the same problem after upgrading to lollipop (xt1063 way) and downgrade.
I cant' lock the bootloader and if I install a stock firmware trying to locking it i receive a lot of FAILED messaged (in partition,motoboot,boot, system system.img_sparsechunk1-2-3....) And can't lock with "SST lock failure ! failed to validate system image" error.
What I have to do? T_T Can someone help me please? I want to bring back everything as before...clean!
If I try to install a stock rom and i don't try to lock the bootloader i receive FAILED error only in the first 2 strings
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
and this never happen. What I have to do for locking the bootloader again? :\ I try with fastboot instead of mfastboot commands too..but...same results.
Thanks.... :crying:

After reading numerous threads about relocking the bootloader, I came to the conclusion that after a downgrade it's simply impossible to relock the bootloader.
So, if you have, for instrance, an XT1068 and you have flashed the US build of Lollipop on it, the only way to make it 'stock' is to downgrade to KitKat, since there is no official Lollipop build for the XT1068 yet. This means that you will be unable to lock the bootloader. You'll have to wait for an official Lollipop build, install that manually, and then relock the bootloader.
So in short: after a downgrade (as from Lollipop to Kitkat) it's impossible to lock the bootloader!
Please correct me if I'm wrong!

smitharro said:
After reading numerous threads about relocking the bootloader, I came to the conclusion that after a downgrade it's simply impossible to relock the bootloader.
So, if you have an XT1068 and you have flashed the US build of Lollipop on it, the only way to make it 'stock' is to downgrade to KitKat, since there is no official Lollipop build for the XT1068 yet. This means that you will be unable to lock the bootloader. You'll have to wait for an official Lollipop build, install that manually, and then relock the bootloader.
Please correct me if I'm wrong!
Click to expand...
Click to collapse
According Motorola downgrading from lolipop to kitkat is not possible
Moto G (2nd Generation) - Android™ 5.0 Lollipop - Release Notes
INTRODUCTION
We are excited to announce a new software update for Moto G (2nd Generation) by Motorola. This update brings Android™ 5.0 Lollipop to your phone along with other improvements.
For more information on Motorola updates and repairs, visit us at www.motorola.com/mymotog.
NOTE: You cannot downgrade to a previous software version after installing this update.

[GUIDE] [Maxx XT1225] Install Lollipop OTA if you have Rooted - no Wipe necessary

as always I'm not responsible for any damage in your device (or lost files)
Always backup everything first - nandroid and titanium.
TL;DR for more experienced users: flash stock boot, stock recovery and stock system images (system via mfastboot since its chunks) and then install OTA zip file in the stock recovery (via sd or sideload)
If you have rooted your Moto Maxx and are trying to install the OTA for Lollipop, you are probably getting errors due to modifications on you system.
Simply removing SuperSU doesnt work, you have to restore your system to stock.
If you received the OTA notification, download it and don't install.
0- After downloading, grab the zip file from /cache/ and save it on your computer.
Filename will be something like Blur_Version.XX.XX.XX.quark_retbr.retbr.en.BR.zip
1- Download brazilian retbr full 4.4.4 firmware from here
http://forum.xda-developers.com/dro...tbrxt12254-4-4kxg21-50-9cid12subsidy-t2992444
Decompress it and you should see these files:
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
system.img_sparsechunk.4
recovery.img
boot.img
2- Download mfastboot (google it) (I used both regular fastboot and mfastboot)
3- Decompress mfastboot and put all files in the decompressed folder above
All files should be in the same folder: mfastboot.exe, boot.img, recovery.img and all system sparsechunks.
Of course they can be in different folders if you know how to use paths in command
4- Unroot
Go to SuperSU app -> configurations -> uninstall root
I recommend uninstalling xposed, busybox etc (I didnt have those, not sure if they will mess with something)
5- Put your phone in bootloader mode
adb reboot bootloader
5- Flash stock kernel, recovery using regular fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
6- flash stock system to fix install-recovery.sh bug/validation, using mfastboot:
Flashing stock boot and recovery was not enough for me. I was getting an error saying /system/etc/install-recovery.sh has unexpected contents.
To solve this, I flashed the stock system image by using mfastboot:
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
Code:
C:\mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (259107 KB)...
OKAY [ 8.130s]
writing 'system'...
OKAY [ 4.122s]
finished. total time: 12.259s
C:\mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (254153 KB)...
OKAY [ 7.958s]
writing 'system'...
OKAY [ 3.282s]
finished. total time: 11.250s
C:\mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 8.208s]
writing 'system'...
OKAY [ 3.719s]
finished. total time: 11.937s
C:\mfastboot.exe flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (262142 KB)...
OKAY [ 8.207s]
writing 'system'...
OKAY [ 3.880s]
finished. total time: 12.098s
C:\mfastboot.exe flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (144756 KB)...
OKAY [ 4.533s]
writing 'system'...
OKAY [ 2.330s]
finished. total time: 6.871s
After this your system is back to stock.
All you have to do now is enter in stock recovery, go to "install zip from adb" and sideload the zip you saved in step 0.
1.2- Reboot your phone to stock recovery
You should see a broken android laying on the floor
in this screen, press Power+VOL UP together and hold for like 2 seconds and release.
A menu should appear. If it doesnt, try again many times - it can be tricky
2.2- Select install zip from ADB or something like that
Now you should be able to see your device in your computer via adb devices command
You should see your device ID and a sideload string when you type this. If you dont, you have incorrect drivers
3.2- Sideload the OTA zip file
In your command prompt find the OTA file you saved in step 0 and then
adb sideload filename.zip, exemple:
adb sideload Blur_Version.XX.XX.X.quark_retbr.retbr.en.BR.zip
If everything goes ok, just wait and relax, if could take a while for the first boot.
Phone will hang on a blank screen with motorola Logo for a while. Dont panic.
Obviously you will lose root by doing this.

Very good i need do that, but i do full wipe for test all, you can flash from sd its works too only need copy file in sd when software release.

I have stock recovery, only I have root, with a simply factory reset I can erase root?
Can I leave boot loader unlocked? Or I need lock the boot loader?
Sent from my XT1225 using XDA Free mobile app

flowserver said:
I have stock recovery, only I have root, with a simply factory reset I can erase root?
Can I leave boot loader unlocked? Or I need lock the boot loader?
Sent from my XT1225 using XDA Free mobile app
Click to expand...
Click to collapse
you dont need to relock your bootloader
I havent tried to just factory reset, but I saw people trying just this without succcess, because seems like super su modifies some files and after uninstalling supersu they're not the same anymore, so when you try to install the OTA you will get an error since validation for file md5/sha will fail

respider said:
you dont need to relock your bootloader
I havent tried to just factory reset, but I saw people trying just this without succcess, because seems like super su modifies some files and after uninstalling supersu they're not the same anymore, so when you try to install the OTA you will get an error since validation for file md5/sha will fail
Click to expand...
Click to collapse
Does anyone have the OTA yet? Or is this just prep for the future?

Gundabolu SC said:
Does anyone have the OTA yet? Or is this just prep for the future?
Click to expand...
Click to collapse
yes, soak test is happening

someone could post the Lollipop OTA file here?..

flowserver said:
I have stock recovery, only I have root, with a simply factory reset I can erase root?
Can I leave boot loader unlocked? Or I need lock the boot loader?
Sent from my XT1225 using XDA Free mobile app
Click to expand...
Click to collapse
No factory reset dont remove root for me, only this tutorial removes

where is the OTA zip???

This tutorial is to unroot device and back to stock

Lollipop ROM
Where's lollipop zip rom?

this is a guide to install OTA zip If you received the OTA notification and if you have a rooted phone
this is not a rom, this is a guide/howto

Mexico Maxx
Great tutorial, maybe a dumb question, the BR image file works the same on the MX Maxx? Or do I need to download the mexican retail image?
Thanks!

Quetzalfp said:
Great tutorial, maybe a dumb question, the BR image file works the same on the MX Maxx? Or do I need to download the mexican retail image?
Thanks!
Click to expand...
Click to collapse
I think should works fine, but motorola said mexican already have soak too so.

maybe this will help to someone who received Lollipop and wants to share with us the OTA

matheus_sc said:
I think should works fine, but motorola said mexican already have soak too so.
Click to expand...
Click to collapse
Thanks, I know that is coming to Mexico too, but from the tutorial says that we need some files from the brazillian image to return to pure stock before the update, this files works for the mexican devices or I need to download the MX image?

Quetzalfp said:
Thanks, I know that is coming to Mexico too, but from the tutorial says that we need some files from the brazillian image to return to pure stock before the update, this files works for the mexican devices or I need to download the MX image?
Click to expand...
Click to collapse
probably you just need to replace with mexican images
I'm not sure if recovery/boot/system are all the same, but if you use everything from mexico you should be fine

I have 2 questions sorry for my ignorance.
1 is there a link to download the other zip?
2 is this update compatible with the xt1225 Puerto Rico version?
Sent from my XT1225 using XDA Free mobile app

respider said:
probably you just need to replace with mexican images
I'm not sure if recovery/boot/system are all the same, but if you use everything from mexico you should be fine
Click to expand...
Click to collapse
Thanks! I'll give it a try if I get the OTA notification and let you know

Atrix_Lover said:
I have 2 questions sorry for my ignorance.
1 is there a link to download the other zip?
2 is this update compatible with the xt1225 Puerto Rico version?
Sent from my XT1225 using XDA Free mobile app
Click to expand...
Click to collapse
Updates only works in Brazilian firmware but dont release yet

Stock ROM Nougat 7.0 For Moto G4 Plus XT1643

Hello guyz do you have or post the latest version stock rom for Moto G4 Plus XT1643 ?
Waiting eagerly for your heads up
edit :
head to this link for flashing procedure and lock/ re-lock the bootloader on moto g4 plus :
https://forum.xda-developers.com/showpost.php?p=70383231&postcount=15

http://forum.xda-developers.com/mot...d-ota-nougat-ota-moto-g4-plus-t3517059/page37
Sent from my Moto G (4) using Tapatalk
Sent from my Moto G (4) using Tapatalk

zazzy24 said:
http://forum.xda-developers.com/mot...d-ota-nougat-ota-moto-g4-plus-t3517059/page37
Sent from my Moto G (4) using Tapatalk
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
this is captured ota I'm asking for updated stock rom for flashing.. thanks for your head up (Y)

snd team said:
this is captured ota I'm asking for updated stock rom for flashing.. thanks for your head up (Y)
Click to expand...
Click to collapse
It isn't released. That's already discussed.

snd team said:
Hello guyz do you have or post the latest version stock rom for Moto G4 Plus XT1643 ?
Waiting eagerly for your heads up
Click to expand...
Click to collapse
Find it here. It's flashable ROM zip:
removed link.. mod edit: not flashable..

removed link.. mod edit: not flashable..
Anyone tried this ? is it compatible with Indian (XT1643) version?

Arivendu said:
Find it here. It's flashable ROM zip:
removed link.. mod edit: not flashable..]
Click to expand...
Click to collapse
Don't misguide users. You shouldn't post if you are not sure about something.
First, its not a zip file. Its a rar file.
Second, its not flashable. You need to flash it using fastboot.

Arivendu said:
Find it here. It's flashable ROM zip:
https://cloud.mail.ru/public/CKF3/AWVREk6s9
Click to expand...
Click to collapse
Thanks buddy you're the best
praveenbda said:
Anyone tried this ? is it compatible with Indian (XT1643) version?
Click to expand...
Click to collapse
yes sure see the topic title and also tested on XT1643

also I'm able to re-lock the bootloader

TO relock the bootloader and Flashing
First of all download the stock firmware rar file ( thanks to Arivendu for heads up) - multi platform support (windows linux etc)
https://cloud.mail.ru/public/CKF3/AWVREk6s9
Mirrors :
https://files.fm/u/hfapbktm
https://drive.google.com/open?id=0B-ReAPgYg5ISNFpaeV92V2hRaWc
https://mega.nz/#!0oV33RhI!5U51UqC4v16qTSN5ur6FAV7EOpLTXL0Pfm12n71GGwc
***** this firmware also worked for other moto g4 variants *****
extract it
open folder name : athene_oem_user_7.0_NPJ25.93-11_12_release
under the folder their is a folder name "Windows"
copy files from "windows" folder to root folder
and use below command to re-lock bootloader and flash your phone with latest version of stock 7.0 (tested on xt1643)
SHIFT + Mouse right click >>> open command window here
and enter this commands one by one
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
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
fastboot erase clogo
fastboot oem lock
Or download the oem unlock and flash mobile.zip (833.6 KB) from atatchment and place the files in root dir where you extracted the firmware
and run the OEM lock.bat file for automation
if the device not reboot after firmware flash run this command at the end :
Code:
fastboot reboot

I can confirm that rar contains factory images and it's working fine on my Moto G4 Plus XT1644 64GB/4Gb RAM (RETUS). Finally, running Nougat on my device.

snd team said:
no i don't have any link and i confirm it is original moto firmware
Click to expand...
Click to collapse
Thanks, I had a browse and it looks like it's from http://lenovo-forums.ru/topic/22076-moto-g⁴-plus-npj2593-11/
Although the website says they are not an official Lenovo forum, if it's working for people, that's great. It'd be nice if we get a Nougat ROM we can flash in stock recovery without adb fastboot

Massive cleaning on the thread.. Please be warry of whatever type of file you are flashing on your devices.. A little mistake will brick your devices. I hope no one will post again a non-flashable zip.. and pls. put into considerations the knowledge of others. Not everyone knows what a RAR file or a ZIP file is... Please be cautious.. AND LASTLY .. NO FLAMING ..... NEVER ALLOWED HERE

reyscott said:
Massive cleaning on the thread.. Please be warry of whatever type of file you are flashing on your devices.. A little mistake will brick your devices. I hope no one will post again a non-flashable zip.. and pls. put into considerations the knowledge of others. Not everyone knows what a RAR file or a ZIP file is... Please be cautious.. AND LASTLY .. NO FLAMING ..... NEVER ALLOWED HERE
Click to expand...
Click to collapse
thanks for cleaning cheers

Fastboot flashing steps
snd team said:
Hello guyz do you have or post the latest version stock rom for Moto G4 Plus XT1643 ?
Waiting eagerly for your heads up
edit :
head to this link for flashing procedure and lock/ re-lock the bootloader on moto g4 plus :
https://forum.xda-developers.com/showpost.php?p=70383231&postcount=15
Click to expand...
Click to collapse
Hi guys
I have an XT1643 and I have downloaded the firmware mentioned below. It was a 7z compressed file with password as "lenovo-forums.ru"
"athene_oem_user_7.0_NPJ25.93-14_16_release.7z"
I couldn't find the commands for flashing this through bootloader. If someone may know a solution, could you please post the command or guide me?
thanks

shailuo said:
Hi guys
I have an XT1643 and I have downloaded the firmware mentioned below. It was a 7z compressed file with password as "lenovo-forums.ru"
"athene_oem_user_7.0_NPJ25.93-14_16_release.7z"
I couldn't find the commands for flashing this through bootloader. If someone may know a solution, could you please post the command or guide me?
thanks
Click to expand...
Click to collapse
The fastboot commands are the same as in the post you linked in your quote. Alternatively, you may refer to the instructions listed here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
One way to flash your stock ROM is (just expanding on the instructions mentioned previously):
1) Download the Motorola drivers and minimal adb tool from the links here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 Install the drivers and tool as directed by the installers.
2)Extract the 7z ROM with your preferred decompression tool (that can handle .7z file types). The resulting folder should be about 2 GB. Copy the files (from the extracted stock ROM) to your adb folder (may be on your C:\ drive, you may have to give permission to copy).
3)Connect your device to your computer. Enable USB debugging.
3a)Once recognised by your computer, open the adb terminal and type/execute 'adb devices' without the quotes. Your device should return back its serial number if properly detected.
4)Back up all necessary data and files to your computer. Flashing a fastboot ROM may wipe your data from your device.
5)Reboot your device to bootloader mode.
5a) Re-confirm you can still detect your device in fastboot mode by executing 'fastboot devices'. Should get your serial number again.
6)Run the commands as directed in the fastboot ROM thread in the adb terminal.
6a)These commands are for relocking your bootloader:
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
6b) If you don't wish to type all this, you may wish to download and run the scripts from this thread: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Ensure you copy the scripts to the adb folder, where your ROM files and the adb terminal should be. There should be 2 scripts there, one for if you want to relock your bootloader, one if you don't wish to.

getting error whilw flashing
snd team said:
First of all download the stock firmware rar file ( thanks to Arivendu for heads up) - multi platform support (windows linux etc)
https://cloud.mail.ru/public/CKF3/AWVREk6s9
Mirrors :
https://files.fm/u/hfapbktm
https://drive.google.com/open?id=0B-ReAPgYg5ISNFpaeV92V2hRaWc
https://mega.nz/#!0oV33RhI!5U51UqC4v16qTSN5ur6FAV7EOpLTXL0Pfm12n71GGwc
***** this firmware also worked for other moto g4 variants *****
extract it
open folder name : athene_oem_user_7.0_NPJ25.93-11_12_release
under the folder their is a folder name "Windows"
copy files from "windows" folder to root folder
and use below command to re-lock bootloader and flash your phone with latest version of stock 7.0 (tested on xt1643)
SHIFT + Mouse right click >>> open command window here
and enter this commands one by one
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
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
fastboot erase clogo
fastboot oem lock
Or download the oem unlock and flash mobile.zip (833.6 KB) from atatchment and place the files in root dir where you extracted the firmware
and run the OEM lock.bat file for automation
if the device not reboot after firmware flash run this command at the end :
Code:
fastboot reboot
Click to expand...
Click to collapse
log:
Fastboot device is ready
There are 1 device(s) connected: ZY2237XWMH
Trying to flash device ZY2237XWMH
Starting flashing device ZY2237XWMH...
Flashing partition table ...
Executing ".\Windows\fastboot.exe -s ZY2237XWMH flash partition gpt.bin"
target max-download-size: 512MB
sending 'partition' (32 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.048s
All devices are flashed
Press any key to continue .
Iam getting same error even while flshing without bootloader and GPT. (Iam trying downgrade from 7.1.2 to stock 7.0)
please help me with this

Udaya.kr said:
log:
Fastboot device is ready
There are 1 device(s) connected: ZY2237XWMH
Trying to flash device ZY2237XWMH
Starting flashing device ZY2237XWMH...
Flashing partition table ...
Executing ".\Windows\fastboot.exe -s ZY2237XWMH flash partition gpt.bin"
target max-download-size: 512MB
sending 'partition' (32 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.048s
All devices are flashed
Press any key to continue .
please help me with this
Click to expand...
Click to collapse
What firmware did you have previously on your device, and are you trying to relock your bootloader? The firmware linked here is quite old (November 2016 security patch), and the warning you're getting suggests you have newer firmware on your device.
If you're on the June update, do not flash this firmware.

echo92 said:
What firmware did you have previously on your device, and are you trying to relock your bootloader? The firmware linked here is quite old (November 2016 security patch), and the warning you're getting suggests you have newer firmware on your device.
If you're on the June update, do not flash this firmware.
Click to expand...
Click to collapse
Successfully flashed june firmware and re locked bootloader. thank you for your help.

Udaya.kr said:
Successfully flashed june firmware and re locked bootloader. thank you for your help.
Click to expand...
Click to collapse
Can you please share the link for june fastboot rom for XT1643?

Yet Another Bootloop Thread

Hello,
So I decided to unlock and root my Pure today. Originally I was going to flash Lineage, but I later decided not to. Anyway, I was following the instructions here.
So I unlocked and installed TWRP succesfully. Then I decided to root. And that's where I screwed up.
Following these instructions, I now have a phone that won't boot past the "M" logo. Apparently my mistake was not using the current SU version.
I have been Googling for an hour now, but almost every solution I've come across has involved plugging the phone into the computer. My issue is that my computer isn't recognizing the phone when I plug it in, so my knowledge of how to fix this is limited (and my expertise in this topic was minimal to begin with...). I can get to recovery mode, and have tried a factory reset. No dice. I also put the latest official factory image from Motorola on the SD card, but when I went to install it, it wouldn't show up.
As you can tell I am quite stuck here. I haven't tried to root a phone since my Incredible back in the day. Any help would be greatly appreciated.
Thanks!

Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.

jason2678 said:
Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.
Click to expand...
Click to collapse
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?

bootloopohgod said:
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?
Click to expand...
Click to collapse
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps

Sagar_1401 said:
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps
Click to expand...
Click to collapse
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.

bootloopohgod said:
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.
Click to expand...
Click to collapse
ignore that partition error
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 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 system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
make sure
while flashing NON-HLOS.bin you might get error
dont worry
when you reach that step do type it again when you see that error and it'll successful flash the NON-HLOS.bin which is your main step for your modem
im sure this will 100% work
edit: all the files have different no of system system.img_sparsechunk
if you are flashin sept patch it should have 8 i assume but if you just type system system.img_sparsechunk.9 it'll say file not found u won't encounter any error by that