Database Develop

[Q] Im brick my AHD AT&T on JB flashing MB886_niimx-user-4.1.2-9.8.2Q-50_MB886

I made the mistake of flash this file MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-AHD MX.xml.zip in my AHD AT&T on JB 4.1.1, now when I try to flash, I get this error:
RSDLite: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL.
ATRIX HD: security downgraded version
gpt_main version update failed
preflash validation failed for GPT.
any ideas to fix this?
PD. Excuse my english

How is there a Mexican firmware for this phone??? I haven't seen this phone available in Mexico...

3z3-8917 said:
I made the mistake of flash this file MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-AHD MX.xml.zip in my AHD AT&T on JB 4.1.1, now when I try to flash, I get this error:
RSDLite: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL.
ATRIX HD: security downgraded version
gpt_main version update failed
preflash validation failed for GPT.
any ideas to fix this?
PD. Excuse my english
Click to expand...
Click to collapse
+1

joel_sinbad said:
How is there a Mexican firmware for this phone??? I haven't seen this phone available in Mexico...
Click to expand...
Click to collapse
Yes the mexican firmware is avaliable for dowload in sbf.droid-developers, but it's but it's no compatible with AHD AT&T.
I lost the signal constantly in my AHD AT&T 4.1.1 stock JB, for that reason I flashing mexican firmware for fix this, but I brick my phone, not is posible reflashing MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip, I get this error en RDS: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL

3z3-8917 said:
Yes the mexican firmware is avaliable for dowload in sbf.droid-developers, but it's but it's no compatible with AHD AT&T.
I lost the signal constantly in my AHD AT&T 4.1.1 stock JB, for that reason I flashing mexican firmware for fix this, but I brick my phone, not is posible reflashing MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip, I get this error en RDS: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL
Click to expand...
Click to collapse
I learned YEARS ago never to flash an sfb\fastboot\odin\whatever if its not made specifically for your device+OS+carrier until the super smarts have determined if the signatures\values are compatible (or wait until a post like this shows up ). Motorola's notorious for setting up sbf's in a way that will brick you, prevent you from ever going back to stock, and\or downgrading. Knowing that, I made a rom from MR instead of flashing the fastboot.
ATRIX HD: security downgraded version -- that line worries me the most, especially if that's what it says if you're trying to flash AT&T now -- It could mean that MR has a higher CG value than AT&T. You'll never be able to install the AT&T fastboot again if that ends up being the case -- you've blown an efuse.
I'm gonna need some more details: Did the MR flash fully finish the first time used? If it fully finished and didn't boot or loops, do a factory reset in the stock reocovery. You could also try to unlock the bootloader (worth a shot at any rate) -- seems like you still have fastboot access so its at least worth trying -- it would be great if MR is the secret fastboot that unlocks us (I mean, the rom itself has no entitlement checking whatsoever, maybe its bootloader doesn't either...)
.
Can you still access SS or does it boot directly into fastboot\stock recovery? . If fastboot only, try flashing just the boot.img from the fastboot (probably won't work if an efuse has been blown). If you still have SS then we can put the boot.img in a zip and flash that -- its how we safely tested Defy sbf's without blowing an efuse.
After trying all of the above and if none of them work you should attempt flashing the Bell JB fasboot as a last ditch effort.

loading into fastboot only with error "flash failure"

marshok said:
loading into fastboot only with error "flash failure"
Click to expand...
Click to collapse
I'm not really sure what to tell you. You could try flashing just AT&T boot.img and devtree....Maybe make a hybrid fastboot, replace what fails during the AT&T flash with files from the MR fastboot (and modify the xml accordingly). Since it seems you're using the MR fastboot menu it, trying the unlock command is worth a shot.
All my other suggestions involve trying to connect directly to the nand and manually dd in the mbr and such -- I've never even tried connecting to my phone like that, so you'll have to search for those methods on your own, sorry. You'll also be diving in to full on brick territory too. You're just semi bricked, so you can still get lucky if you don't change that.
There is still hope (maybe) -- Apparently 4.2 is in testing and a fastboot should pop up for it before or after it's released. If its like every other major sbf\fastboot release I've seen it should have higher signatures\cg values and could possibly be a fix for you. That's all an assumption, but its based on credible rumor (a Mattlgroff post) and Motorola's past actions. The point is -- You still have access to fastboot, don't do anything to screw that up because your needed fix might not be available yet.
Or you could send in your phone for warranty; check Motorola's website to see if your still covered under factory warranty -- I am and my phone is a 99 cent refurbished model -- I still have 11 months left You get 12-24 months coverage when you register (length depends on New or Refurb). I was truthful on my Purchase Date, but I suppose you could lie and say you just recently bought it and it quit working when you started to upgrade it.

Did the MR flash fully finish the first time used?
Click to expand...
Click to collapse
no the flashing not completed, I got the error just flash boot.img
You could also try to unlock the bootloader (worth a shot at any rate) -- seems like you still have fastboot access so its at least worth trying -- it would be great if MR is the secret fastboot that unlocks us (I mean, the rom itself has no entitlement checking whatsoever, maybe its bootloader doesn't either...)
Click to expand...
Click to collapse
how I can do this? when my AHD is briked
Can you still access SS or does it boot directly into fastboot\stock recovery? . If fastboot only, try flashing just the boot.img from the fastboot (probably won't work if an efuse has been blown). If you still have SS then we can put the boot.img in a zip and flash that -- its how we safely tested Defy sbf's without blowing an efuse.
Click to expand...
Click to collapse
if boot directly into fastboot and I have acces stock recovery
After trying all of the above and if none of them work you should attempt flashing the Bell JB fasboot as a last ditch effort.
Click to expand...
Click to collapse
I try flash Bell JB fasboot and I get the same error
thanks for your help skeevy420
PD. Excuse my english

del

3z3-8917
How do you help skeevy420?
you have restored your phone after flashing on MB886_niimx-user-4.1.2-9.8.2Q-50_MB886?

In the same boat
Hey guys I'm in the same boat. I rooted my Atrix HD and was happy until I installed busy box 9.2, which managed to overwrite /system/bin and I don't know what else I could no longer mount/remount, change w/r in root, use the ls or many other commands and wifi, mobile data, bluetooth, or OS factory reset all gone.
I should have made a copy of my system before doing anything else but I went ahead and used the boot menu recovery, which didn't do anything to help the problem.
I then flashed the MR rom with RSD Light in an attempt to recovery my phone, it was 4.1.2 and seemed like a good (hindsight horrible) idea at the time.
Now I can fastboot flash recovery images from att JB but it does no good because the boot partition fails. The RSD Light MR boot flash failed but somehow the security version stuck, and the Bell 4.1.2, Att 4.1.1, and 7.7.1Q-144, roms boot.img all return Partition (boot) Security Version Downgraded. If anyone knows a way around this please let me know.
It seems kind of tragic that Dan's bootloader unlocking came out, pretty much the day after I got stuck in this locked bootloader loop

You have to use a special xml, unzip your stock-rom replace the old xml with this one: for ICS and this one for JB.
Then try to flash it again with https://www.box.com/s/cmoz84iachug77tghdlo version of rsd lite. Make sure you have these latest drivers.

3z3-8917 said:
Yes the mexican firmware is avaliable for dowload in sbf.droid-developers, but it's but it's no compatible with AHD AT&T.
I lost the signal constantly in my AHD AT&T 4.1.1 stock JB, for that reason I flashing mexican firmware for fix this, but I brick my phone, not is posible reflashing MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip, I get this error en RDS: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL
Click to expand...
Click to collapse
it can fix?????? i did the same flash at my atrix hd

rorrito said:
it can fix?????? i did the same flash at my atrix hd
Click to expand...
Click to collapse
for the moment it's not possible, wait bootloader unlock tool for AHD briked....

Codex01 said:
You have to use a special xml, unzip your stock-rom replace the old xml with this one: for ICS and this one for
JB
Then try to flash it again with this version of rsd lite. Make sure you have these latest drivers.
Click to expand...
Click to collapse
Ok downloaded the JB you linked and upgraded from RSD Light 6.1.4 to 6.1.5, I edited the XML to remove getvar, and ran RSD Light but it still fails on step 1.
"Failed Flashing Process 1/23 "gpt_main0.bin -> Phone returned FAIL."
On the Phone "preflash validation failed for gpt_main0.bin"
The only stock rom that made it past step 1 has been the MR that bricked my phone, so I replaced the system.img, boot.img, and recovery.img of the MR with the JB 4.1.1 you linked but it still fails at step 15, flashing boot.img. Preflash validation falure

BRICK AHD
Exactly same situation here, Flashing Mexican Firmware.
Now i got Partition (Boot) Security Version Downgraded
Hope it can be fixed:crying:

fix fail on part 1 rsd
use the stickyboot fix from general got it from skeevydude it works, try using mythtools after!
ickysjazz said:
Exactly same situation here, Flashing Mexican Firmware.
Now i got Partition (Boot) Security Version Downgraded
Hope it can be fixed:crying:
Click to expand...
Click to collapse

Shame on me :S
Well, I just bricked an ATT AHD in the same manner, trying to flash the Mexican JB version (I bought 3 of this phones to sell here in Mexico and wanted them to look as the phones they sell here by replacing the broken digitizers with ones with no ATT logo and flashing local firmware) ...But yeah, I made a big mistake, I wasn't aware I had to unlock BL before flashing other carrier SBF's... :S At least I've learned from this and didn't made the same mistake with the other 2 AHD's I have (And I'm planning to go back to stock and deodex em' because Mex fw isnt working pretty well on this AHD's...)
Trying to repair this thing by reflashing ATT JB stock fw... RSD & Myth seem not to work;
-In RSD I can't even get past step 1/23 (flash partition "gtp_main0.bin" failed"); when trying to flash Mexican rom I got to step 15/23 till I got the error.
-In Myth It looks like some files get flashed (It even gets me to the "Load Recovery" option, I obviously choose Stock as I don't want to f'up the phone even more ) and then "finishes" but when rebooting, shows "Dual Core tech" bootscreen and sends me back to Fastboot (Reason: Sticky bit factory_fastboot), tried stickyboot solution on cmd and then reflash on myth, same result.
Also I get the messages "downgraded security version" and "Invalid PIV Image: System" in AHD Fastboot. I don't know what else to do now, I still haven't tried Bell rom as I think I'll mess things up even more so I've stayed away from it At this point I guess I'm pretty much f***ed...

@ickysjazz
@vananucho
You're using the wrong fastboot...I can tell that by the error code...use snapdragon fastboots...those are the only ones for us to use. Any other fastboot will result in errors.
So Download those
DL Mex Retail
Extract it
Open terminal to that extracted directory
Do the sticky_bit fix.
Do these commands in this order
Code:
fastboot flash partition gpt_main0.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash sbl3 sbl3.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot flash cdrom cdrom
fastboot erase cache
fastboot erase userdata
And that's how you manually flash a fastboot. I've never used MythTools or RSD. That is how I do it, always have done it, always will do it -- with the same fastboot linked above with same commands posted. Those are for Mex Retail, but should work on any JB fastboot...ICS fastboots need a few minor tweaks.
Do the fastboot commands as root on Linux or as a Windows Admin (set the admin privileges for the app in the right click properties menu)

Replaced the fastboot with the one provided by Skeevydude and still get the same error but I guess it's due to the fact that I'm running out of battery (Started showing low bat advice after 3rd failed attempt, using regular cable), I'll try this again as soon as I make a flashing cable, I'll keep updated!

Any change to relock bootloader?

Is there any chance to relock the bootloader? I don't mind about warranty i just want to make it as much similar to stock as possible!

alexhdkn said:
Is there any chance to relock the bootloader? I don't mind about warranty i just want to make it as much similar to stock as possible!
Click to expand...
Click to collapse
There Are three status for the 2013 X boot loader...
Locked Status Code 0
Unlocked Status Code 3
Locked Status Code 2 (aka RELocked).
If the status is Unlocked or Relocked, you'll get the unlocked bootloader warning at boot up.
We do not have a way to toggle back to LOCKED Status Code: 0.
So you could take it back to RELocked, but it won't really matter much. Moto has the steps on their web page https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and there was a thread here on XDA too http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786
Also keep in mind that if you used Sunshine to unlock, if you do RELocked you will not be able to unlock again. Where as if you unlocked by having the unique code for your phone, you'll be able to rel-unlock using your code.

Why would you want to relock the bootloader just to get back to close as stock as possible?

I recently reset my phone back to the stock ROM after jacking up a kernel (did everything on manual flash with the exception of relocking it). Just follow the steps and you'll get it.
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
TechSavvy2 said:
NOTE, YES, THIS IS A LONG DRAWN OUT VERSION OF WHAT IS ACTUALLY VERY VERY QUICK PROCESS. This is for reference only. I know there are a few people out there just like me who probably had a few small hickups getting back to stock with the firmware. This is to help "spoon-feed" the instructions to you.
Two Methods-
Method 1 - RSD Lite
Method 2 - Manual Flash
If you cannot get RSD Lite to recognize your device, try Method 2, it works like a charm!
Downloads:
I assume you already have adb drivers if you're even here.....otherwise get them from the latest sdk here: http://developer.android.com/sdk/index.html
Moto Drivers (Motorola Device Manager): https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
RSD Lite (I used version 6.1.5): https://dl.dropboxusercontent.com/u/42057363/RSDLite_v6.1.x.zip - Extract and use 6.1.5
Stock Firmware: http://sbf.droid-developers.org/ thanks to Skrilax_CZ and Firmware Team
Moto Fastboot exe: https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing - NOTE - YOU MUST UNZIP AND USE THIS WHERE MANUAL FLASH SAYS "mfastboot"
My Setup: Windows 8 machine <--obvious driver issues as usual
My Device: VZW Moto X
METHOD 1 - RSD LITE
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit
METHOD 2 - MANUAL FLASHING
Much easier AND don't have to deal with getting RSD Lite to work....
Note - this was done on VZW variant, and based on XML file of that particular firmware. Get these instructions from your firmware package XML file.
Note 2 - VERY IMPORTANT!!! - You MUST use mfastboot (Moto fastboot) for the system.img flash as its too large for standard Android fastboot to handle, your flash WILL fail if you use standard fastboot. Hence why it says "mfastboot" this is not a typo.
Code:
fastboot oem fb_mode_set
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
mfastboot 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 config carrier vzw
fastboot oem fb_mode_clear
Click to expand...
Click to collapse

KidJoe said:
There Are three status for the 2013 X boot loader...
Locked Status Code 0
Unlocked Status Code 3
Locked Status Code 2 (aka RELocked).
If the status is Unlocked or Relocked, you'll get the unlocked bootloader warning at boot up.
We do not have a way to toggle back to LOCKED Status Code: 0.
So you could take it back to RELocked, but it won't really matter much. Moto has the steps on their web page https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and there was a thread here on XDA too http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786
Also keep in mind that if you used Sunshine to unlock, if you do RELocked you will not be able to unlock again. Where as if you unlocked by having the unique code for your phone, you'll be able to rel-unlock using your code.
Click to expand...
Click to collapse
I unlocked it with the Motorola code, can i relock it? I've tried fastboot oem lock command and it gives me error.

nhizzat said:
Why would you want to relock the bootloader just to get back to close as stock as possible?
Click to expand...
Click to collapse
So i can get Lollipop official!

TheBoiledDogs said:
I recently reset my phone back to the stock ROM after jacking up a kernel (did everything on manual flash with the exception of relocking it). Just follow the steps and you'll get it.
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Click to expand...
Click to collapse
Already done this but it won't relock the bootloader.

alexhdkn said:
I unlocked it with the Motorola code, can i relock it? I've tried fastboot oem lock command and it gives me error.
Click to expand...
Click to collapse
As I said, if you got your Bootloader Unlock code from Moto (or the former China web site or China Middleman), you CAN relock, then unlock it later.
Did you use mFastboot, and follow the FULL sequence of starting with mfastboot oem lock begin followed by flashing the Stock MOTOROLA rom, and finishing wth the mfastboot oem lock command?
note: some have said the fastboot oem lock command needs to also include the Unique code. ex mfastboot oem lock uniquecode
alexhdkn said:
So i can get Lollipop official!
Click to expand...
Click to collapse
Being bootloader Unlocked will NOT impact being notified about, or getting the OTA.
But actually installing the OTA will have some conditions... see -> http://mark.cdmaforums.com/MotoX-OTA.html
So WHEN Lollipop for the 2013 X is finally made available, undo any hacks or changes that move you too far from the stock rom, then take the OTA.
And for the record, I have never attempted to re-lock my bootloader. I've been unlocked since late Nov 2013. and I have received the OTA's just fine.

edit:canceled

KidJoe said:
As I said, if you got your Bootloader Unlock code from Moto (or the former China web site or China Middleman), you CAN relock, then unlock it later.
Did you use mFastboot, and follow the FULL sequence of starting with mfastboot oem lock begin followed by flashing the Stock MOTOROLA rom, and finishing wth the mfastboot oem lock command?
note: some have said the fastboot oem lock command needs to also include the Unique code. ex mfastboot oem lock uniquecode
Being bootloader Unlocked will NOT impact being notified about, or getting the OTA.
But actually installing the OTA will have some conditions... see -> http://mark.cdmaforums.com/MotoX-OTA.html
So WHEN Lollipop for the 2013 X is finally made available, undo any hacks or changes that move you too far from the stock rom, then take the OTA.
And for the record, I have never attempted to re-lock my bootloader. I've been unlocked since late Nov 2013. and I have received the OTA's just fine.
Click to expand...
Click to collapse
Thanks for the answer I will try at home the mfastboot oem lock (i have always wrote fastboot oem lock without the m).

alexhdkn said:
Thanks for the answer I will try at home the mfastboot oem lock (i have always wrote fastboot oem lock without the m).
Click to expand...
Click to collapse
Again, its MORE than just mfastboot/fastboot oem lock. There is an entire process. And it requires to flash the ENTIRE STOCK OEM SBF to your phone, and this process WILL also erase user data. If you only used FASTBOOT, then you probably didn't follow the process, as it requires flashing all IMG files and other parts included in the SBF, and flashing system.img requires mFastboot.
And relocking the bootloader is NOT needed if all you are trying to do is get the OTA when it becomes available.

KidJoe said:
Again, its MORE than just mfastboot/fastboot oem lock. There is an entire process. And it requires to flash the ENTIRE STOCK OEM SBF to your phone, and this process WILL also erase user data. If you only used FASTBOOT, then you probably didn't follow the process, as it requires flashing all IMG files and other parts included in the SBF, and flashing system.img requires mFastboot.
And relocking the bootloader is NOT needed if all you are trying to do is get the OTA when it becomes available.
Click to expand...
Click to collapse
I know it's an entire process and I did it last night to go back to stock 4.4.4. But I just feel safer (thieves) with the bootloader locked.

Thieves? How will having a locked bootloader protect you from thieves?

Using Lenovo Moto Smart Assistant to restore stock rom (and lock bootloader after)

If you have some difficulties finding fastboot rom for some G5S+ variant, I suggest using Lenovo Moto Smart Assistant (LMSA). You can download it from here and install on your PC.
How to download latest specific stock fastboot rom for your G5S+
You must:
Using stock rom (locked or unlocked bootloader).
Install Lenovo Moto Smart Assistant on your PC.
Restore stock firmware, recovery, and boot image (if you changed it before).
Steps:
Reboot your phone to bootloader.
Open "Lenovo Moto Smart Assistant".
Connect your phone to PC using the USB cable.
Choose "Flash" menu on LMSA.
Choose "Moto Phone".
Choose "Moto G Plus (5th Gen S)".
Choose your phone models.
Wait for a minute while LMSA checking your phone, and then choose "Rescue". It will download the latest 1.5+ GB stock fastboot rom based on your phone model. You can find it on "C:\ProgramData\LMSA\Download\RomFiles".
Click "Rescue" to flash latest rom and accept some confirmations. Your phone will be rebooted after flashing process completed.
Now your phone is back to stock rom. Of course, if you have unlocked it before, those steps wouldn't lock your bootloader. If you want to lock it, I suggest you do it immediately after flashing process completed.
Here to lock your phone after successful stock rom restoration.
You must:
Have ADB fastboot driver installed.
Get extracted fastboot rom from "C:\ProgramData\LMSA\Download\RomFiles".
Steps
Reboot to bootloader.
Open "Command Prompt" on your PC, and go to the location of extracted fastboot rom.
Connect your phone to PC using the USB cable.
Check first that your phone is connected using "fastboot devices" command.
Do all below commands in sequence:
Code:
Code:
fastboot oem lock
fastboot oem lock
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 system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash boot boot.img
fastboot oem lock
Your phone will be restarted. There will be no unlocked bootloader message anymore. And you'll have your phone locked. Ta-da .
Note:
Check "system.img_sparsechunk.x" files (where "x" is sequential numbers) in extracted fastboot rom folder. Newer rom may have more files than the older one. You must flash ALL those "system.img_sparsechunk.x" files in sequence.
If you have issues, please share here. Thanks are appreciated.

I did all above steps but my G5 plus is still saying it has an unlocked bootloader with a ID: Invalid key error.
My phone simply avoids the bootloader to be relocked... it's just pure garbage...

What is the reason for relocking the bootloader? You don't get the warranty back...

should i setup my devices and come back to bootloader or without setup please clear this
thanks in advance

Will Moto Smart Assistant also work for the G7 (Play)?
Motorola support sais no (and that there is no way at all to restore the images after unlocking the bootloader)... will try to find out myself later today.
And another question, do people have experience with updating Motos via Moto Smart Assistant? Reason is that latest models (G7) do not allow for OTA updates with bootloader unlocked. Am wondering if it will still be possible via the Smart Assistant - provided that works at all

Does it require only stock rom?
Can i flash the stock rom using lenovo smart assistant when the phone is with custom rom?

Tried it all, but no good news.
Did it all, but my phone is stuck in boot screen. Can enter bootloader and recovery but can't do anything else. Tried everything I could find online (adb flash from twrp, fastboot flash [stock rooms, custom rooms]). Just keep getting kernel errors. If someone could please give me a light I would aprecciate a lot. This started after I installed lineage and tried to restore it back to stock via fastboot flashing (Potter retail 8.1), since fingerprint sensor stoped working on lineage. Mine is XT1802

Install Pixel Experience ROM
voliveira92 said:
Did it all, but my phone is stuck in boot screen. Can enter bootloader and recovery but can't do anything else. Tried everything I could find online (adb flash from twrp, fastboot flash [stock rooms, custom rooms]). Just keep getting kernel errors. If someone could please give me a light I would aprecciate a lot. This started after I installed lineage and tried to restore it back to stock via fastboot flashing (Potter retail 8.1), since fingerprint sensor stoped working on lineage. Mine is XT1802
Click to expand...
Click to collapse
I am on Pixel Experience ROM and this ROM is purely copy of Android Pie of Pixel Devices and most stable rom
Prepare an sd card and copy pixel Experience ROM winrar file then put it in your phone and flash going into the recovery mode
This will work out for your device and will start up again

Abhimlv12345 said:
I am on Pixel Experience ROM and this ROM is purely copy of Android Pie of Pixel Devices and most stable rom
Prepare an sd card and copy pixel Experience ROM winrar file then put it in your phone and flash going into the recovery mode
This will work out for your device and will start up again
Click to expand...
Click to collapse
hello i was looking around to fix my revvl xt-1952-t ( motola g 7)
its stuck in boot loop flashing bad key ( always had bad key since unlocking the phone. )
i have done a couple roms on samsung devices and never on any thing else .
fast boot is some what new to me. i love it vr oden installs . so i went to reinstall
stock rom on a extra phone
and didnt not get it to load i have whipped and reinstalled 4 tines checked the models var etc seems like it is all correct . is there any ideas or tricks i could be missing

I think i did it without flashing the sparsechunk

Moto G6 Bricked NEED HELP!!!

ibb.co/qMypk9M)
ibb.co/SPB646j)
ibb.co/Y823s3r)
ibb.co/QmnK1cB)
[Copy link and past without the )]
I relocked my oem and cant unlock it again. Says feature disabled
Tried potting and restocking but its not flashing because of oem being locked.
Any Ideas?? This is my first rooted phone and I’m new. I had magisk installed earlier but had to reinstall due to android system apps like media storage crashing.
Thanks

pyschodelicbros said:
ibb.co/qMypk9M)
ibb.co/SPB646j)
ibb.co/Y823s3r)
[Copy link and past without the )]
I relocked my oem and cant unlock it again. Says feature disabled
Tried potting and restocking but its not flashing because of oem being locked.
Any Ideas?? This is my first rooted phone and I’m new. I had magisk installed earlier but had to reinstall due to android system apps like media storage crashing.
Thanks
Click to expand...
Click to collapse
You should download the stock firmware from here and following this guide to restore to stock firmware. Even if the rest of the commands don't work, the first two should reset the bootloader and partition tables and make it bootable or maybe unlockable again. You can also maybe try to boot TWRP but I don't know if that'll work because the boorloader is acting odd

pyschodelicbros said:
ibb.co/qMypk9M)
ibb.co/SPB646j)
ibb.co/Y823s3r)
[Copy link and past without the )]
I relocked my oem and cant unlock it again. Says feature disabled
Tried potting and restocking but its not flashing because of oem being locked.
Any Ideas?? This is my first rooted phone and I’m new. I had magisk installed earlier but had to reinstall due to android system apps like media storage crashing.
Thanks
Click to expand...
Click to collapse
You should be able to flash official firmware even if the bootloader is locked. Do you still have the original unlock key you received from Motorola to unlock the bootloader? You'll have to use that to re-unlock your bootloader.
Code:
fastboot oem unlock UNIQUE_KEY
Replace UNIQUE_KEY with the unlock key you received.
EDIT: It just occurred to me that "OEM unlocking" is probably toggled off since you re-locked the bootloader. That's why it says "feature disabled".
You could also try to restore stock firmware using Lenovo Moto Smart Assistant. It has a Rescue option that does that.
https://support.lenovo.com/us/en/downloads/ds101291

AgentICS said:
You should download the stock firmware from here and following this guide to restore to stock firmware. Even if the rest of the commands don't work, the first two should reset the bootloader and partition tables and make it bootable or maybe unlockable again. You can also maybe try to boot TWRP but I don't know if that'll work because the boorloader is acting odd
Click to expand...
Click to collapse
I heard that once u relock bootloader, your unlock feature gets disabled for a few days. Anyone know if that is true?

pyschodelicbros said:
I heard that once u relock bootloader, your unlock feature gets disabled for a few days. Anyone know if that is true?
Click to expand...
Click to collapse
I'm pretty sure it's because the bootloader can't contact the OS correctly and therefore can't validate the request

AgentICS said:
I'm pretty sure it's because the bootloader can't contact the OS correctly and therefore can't validate the request
Click to expand...
Click to collapse
mfastboot oem lock
mfastboot oem lock
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash boot boot.img
mfastboot oem lock
I did this to lock the bootloader, not knowing my OS wasnt installed properly so theres no OS and my bootloader is locked.
"fastboot oem unlock"
says bootloader feature disabled
Picture of my bootloader log
[Copy link and past without the )]
ibb.co/QmnK1cB)

Ragarianok said:
You should be able to flash official firmware even if the bootloader is locked. Do you still have the original unlock key you received from Motorola to unlock the bootloader? You'll have to use that to re-unlock your bootloader.
Code:
fastboot oem unlock UNIQUE_KEY
Replace UNIQUE_KEY with the unlock key you received.
EDIT: It just occurred to me that "OEM unlocking" is probably toggled off since you re-locked the bootloader. That's why it says "feature disabled".
You could also try to restore stock firmware using Lenovo Moto Smart Assistant. It has a Rescue option that does that.
https://support.lenovo.com/us/en/downloads/ds101291
Click to expand...
Click to collapse
Lenovo Moto Smart assistant says device isnt recognize, it might be USB debugging due to not being able to get into the OS.
I tried getting the unique key using "fastboot oem get_unlock_data" but i get this in my CMD
[Copy link and past without the )]
ibb.co/QHD0ZcS)
I do have my orginal unique key saved in a file from when i first unlocked my bootloader and when I tried to flash it I get bootloader feature disabled.
[Copy link and past without the )]
ibb.co/0MPsZrp)
I heard that the oem unlock gets disabled for 7 days after relocking wondering if that is true???

[RECOVERY] Need stock recovery for XT2113-2

I unlocked the bootloader a few months ago, flashed TWRP and installed Magisk and rooted. Discovered I can't use my work profile while rooted and Google Pay won't work with an unlocked bootloader. So I unrooted and removed Magisk, and locked the bootloader again. Then I got this notification for an OTA update to Android 11, but it fails at step 3 of 6, I assume it's because of TWRP.
I asked Motorola to send me the image(s) necessary for the recovery_a and recovery_b partitions but they refuse to help, despite the fact that as the owner of the device, I also own a license to use every piece of software that comes with it. Can anyone here provide me with the stock recovery image(s)? My phone gives me a notification every 10-20 minutes that this Android 11 update is available and it's incredibly frustrating that I can't get rid of it and Motorola won't give me what I need to fix it.
Thx in advance to anyone willing to help.

Look at https://mirrors.lolinet.com/firmware/moto/kiev/official/
Use the file that matches what you have on your phone.

Thank you for the link. However, my build number [QZKS30.Q4-40-95-9] isn't listed. Should I try QZKS30.Q4-40-95-6?

Kor1134 said:
Thank you for the link. However, my build number [QZKS30.Q4-40-95-9] isn't listed. Should I try QZKS30.Q4-40-95-6?
Click to expand...
Click to collapse
build number is not model number. As long as your device is "kiev" you can download any one of the firmware packages.

Or just download the 11 to start with

Fandroid Tech said:
build number is not model number. As long as your device is "kiev" you can download any one of the firmware packages.
Click to expand...
Click to collapse
I understand, thank you for clarifying, but all I need is the recovery image. I just didn't want to flash a recovery image with a different build number in the unlikely event there's a difference between my build and whichever build I download. I'd prefer not to flash the whole system if I can avoid it, but whatever, I guess I'll just throw Android 11 in it.
Thx.

So, can someone let me know exactly how to flash the oem images to this phone? I booted into the bootloader and ran the following commands:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
fastboot flash dtbo dtbo.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Now it just boot loops when powering on and entering charging mode.
EDIT: nevermind, I missed super.img_sparsechunk.9, all good now.

XT2113-2

Kor1134 said:
I unlocked the bootloader a few months ago, flashed TWRP and installed Magisk and rooted. Discovered I can't use my work profile while rooted and Google Pay won't work with an unlocked bootloader. So I unrooted and removed Magisk, and locked the bootloader again. Then I got this notification for an OTA update to Android 11, but it fails at step 3 of 6, I assume it's because of TWRP.
I asked Motorola to send me the image(s) necessary for the recovery_a and recovery_b partitions but they refuse to help, despite the fact that as the owner of the device, I also own a license to use every piece of software that comes with it. Can anyone here provide me with the stock recovery image(s)? My phone gives me a notification every 10-20 minutes that this Android 11 update is available and it's incredibly frustrating that I can't get rid of it and Motorola won't give me what I need to fix it.
Thx in advance to anyone willing to help
Click to expand...
Click to collapse
1st. rsdlite, 2nd. fastbootd, 3rd. make back-up(s), 4th. checkout L-os, its a PLETHORA of relevant info ex. dual partition issues and resolutions. AND i do believe
i know this is a bit l8, HOWEVER, in the event it is not too l8 OR you find yourself requiring assistance hmu. ive spent last couple months DARING my kiev to transform into this elusive paperweight...to no avail. along the way ive learn_ed a couple-o-tings, this and the photon q are amazing marvels of techno{imo}
ciao

if anyone has kiev ?s, i MIGHT be albe to help. i am no self professed aficionado or anything but ive been learning about moto's for a few years.
ciao