Related
Hey! I need all your help, please. Yesterday, I saw that Motorola reveled a tool to unlock the bootloader of our tablet (I know, late). I read all the information about the process, and I could do this on my mz607 wifi. I downloaded all that I need, drivers and android sdk. After that, I rebooted the xoom on bootloader using adb command but....I can't do anything on this!!
I looked for some information about this, and I found in all forums that I can unlock bootloader with "fastboot oem unlock" command. It's false, I cant do nothing!! I rebooted my tablet and now, always run on bootloader and not boot system.
This is my bootloader info:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6B (sha-h13f845, 2011-11-17 16:40:56)
eMMC Info: Size 16G
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
I found a germany forum with the same problem (I think) but I don't understand how they solved this.This the link
After this, I looked for other solutions and I found a tool of Motorola, RSDLite. I downloaded the correct file for my model, and when it flashing (7 step for the tool) not flash the boot.img! It's flash correctly other file packages (recovery.img, fastboot, etc) but it can't flash boot.img
Now, when I do "vol up+vol down+power" and select "Normal Boot", It doesn't do anything, the system would be missing!
I think it's can be a soft brick....or no, I dont know. I'm very worried about this and I would appreciate all your help.
Thanks. I'm waiting your answer.
Anybody can help me????
Ok, Anybody wants to help me!
Bye.
Re: [Q] HELP! Possible Brick on Xoom MZ607 WIFI
Joshbone said:
This is my bootloader info:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6B (sha-h13f845, 2011-11-17 16:40:56)
eMMC Info: Size 16G
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Click to expand...
Click to collapse
You may have tried to flash something before you said you did.
Basically your tablet wouldn't boot do to a failed flash, it said so right on the boot loader.
"AP Fastboot Flash Mode (S) (Flash Failure)"
Either way. You will have to find the fast boot files for your specific device! DO NOT THINK THEY ARE CLOSE ENOUGH it must be your device mz607!
Once you find them simple follow any tutorial on how to fast boot.
If you have trouble finding something just Google my name and you find a few helpful posts and topics.
And on the topic of unlocks. These will never and have not been unlocked. Furthermore a update (from Motorola) would have to update the bootloader for their new(ish) unlock tool.
runandhide05 said:
You may have tried to flash something before you said you did.
Basically your tablet wouldn't boot do to a failed flash, it said so right on the boot loader.
"AP Fastboot Flash Mode (S) (Flash Failure)"
Either way. You will have to find the fast boot files for your specific device! DO NOT THINK THEY ARE CLOSE ENOUGH it must be your device mz607!
Once you find them simple follow any tutorial on how to fast boot.
If you have trouble finding something just Google my name and you find a few helpful posts and topics.
And on the topic of unlocks. These will never and have not been unlocked. Furthermore a update (from Motorola) would have to update the bootloader for their new(ish) unlock tool.
Click to expand...
Click to collapse
So I have to find the same files for my MZ607? boot, recovery and system?
runandhide05 said:
You will have to find the fast boot files for your specific device! DO NOT THINK THEY ARE CLOSE ENOUGH it must be your device mz607!
Click to expand...
Click to collapse
Joshbone said:
So I have to find the same files for my MZ607? boot, recovery and system?
Click to expand...
Click to collapse
Re: [Q] HELP! Possible Brick on Xoom MZ607 WIFI
Mjamocha said:
Click to expand...
Click to collapse
What??
Re: [Q] HELP! Possible Brick on Xoom MZ607 WIFI
Anybody more??
Joshbone said:
Anybody more??
Click to expand...
Click to collapse
Runandhide told you everything you need to know. You need to find the right regioned fastboot file for your mz607 and flash it. And that ypur bootloader is not unlockable. Any tutorial you were reading to unlock it would have to have been for the original xoom, not xoom2.
HELP! Possible Brick on Xoom MZ607 WIFI
Hello, I have the same problem,
I Bricked my MZ607 by flashing a bad "motoboot.img".
That and only that can be flashed!
Have you found a solution? I would also like to unlock the bootloader.
Thanks. I'm waiting your answer.
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6C (sha-c79f1fc, 2011-12-19 11:36:21)
eMMC Info: Size 16G
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Invalid CG OTV (DG: system): Invalid SP Data
Invalid CG HAB (DG: system, status: 0x0056)
Invalid CG OTV (DG: system)
As I am not I Xoom 2 owner I can't help much.
However, Googling around found a few links that may be useful.
Possible stock files?
http://sbf.droid-developers.org/xoom2/list.php
Factory reset using hardware keys:
https://motorola-global-en-uk.custhelp.com/app/answers/detail/a_id/74653
And there's always:
http://www.xoomforums.com/forum/motorola-xoom-2-forum/
Hopefully this at least helps.
Good luck.
f5bud said:
Hello, I have the same problem,
I Bricked my MZ607 by flashing a bad "motoboot.img".
That and only that can be flashed!
Have you found a solution? I would also like to unlock the bootloader.
Thanks. I'm waiting your answer.
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6C (sha-c79f1fc, 2011-12-19 11:36:21)
eMMC Info: Size 16G
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Invalid CG OTV (DG: system): Invalid SP Data
Invalid CG HAB (DG: system, status: 0x0056)
Invalid CG OTV (DG: system)
Click to expand...
Click to collapse
Hi, my Xoom is the MZ607 WIFI model, and I fix whit this:
https://drive.google.com/folderview?id=0B5JuUC6auPR-bWJ2cFFUVVNmNFE&usp=sharing
Download the 3 files. First, install the Moto drivers, after that, execute the RSDLite and flash the zip.
Hope I've helped you
Like the genius I am I've bricked mine too. It's a UK MZ607 that's been updated to JB from the US MZ609. I managed to delete the stock browser whilst trying to install a CyanogenMOD browser (long story) so figured I'd just repeat the steps that I used to flash the US MZ609 firmware. What I'd forgotten is that the first stage is to flash the US MZ609 ICS ROM then do an update to JB meaning I was effectively trying to downgrade. Everything flashes successfully except the boot partition which gives an error that it doesn't exist. Any ideas out there? I tried what I believe to be the original Fastboot file but no luck
Joshbone said:
Hi, my Xoom is the MZ607 WIFI model, and I fix whit this:
https://drive.google.com/folderview?id=0B5JuUC6auPR-bWJ2cFFUVVNmNFE&usp=sharing
Download the 3 files. First, install the Moto drivers, after that, execute the RSDLite and flash the zip.
Hope I've helped you
Click to expand...
Click to collapse
Also tried this and it fails when flashing the boot partition. I just ordered a factory cable to see if it can bring it back to life...
Is this zip still available?
alecbond said:
As I am not I Xoom 2 owner I can't help much.
However, Googling around found a few links that may be useful.
Possible stock files?
http://sbf.droid-developers.org/xoom2/list.php
Factory reset using hardware keys:
https://motorola-global-en-uk.custhelp.com/app/answers/detail/a_id/74653
And there's always:
http://www.xoomforums.com/forum/motorola-xoom-2-forum/
Hopefully this at least helps.
Good luck.
Click to expand...
Click to collapse
anybody who still has the mz607 files for a restore? The possible stock files link doesn't work any more...
http://sbf.droid-developers.org/xoom2/list.php
I have been rooting for about a year now, albeit largely with Samsung devices via Odin and CWM Recovery. I now have a Verizon Motorola RAZR HD (xt925) and have been unsuccessful with unlocking the bootloader. I decided to use Safestrap with it, and tried to load Eclipse-v5.0-build2-xt926, reportedly compatible with my XT925... now i am stuck with this screen:
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-02-14 09:13:08)
eMMC Info: Size 16GB
Deviced is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I have been looking to XDA for my answers over the last year. Help would be appreciated. Twenty-five dollars worth of appreciation.
(Yes, I have resorted to bribes....)
Easy fix,
download what ever version of the system software you had on it previously.
Flash it in fast boot mode.
?????
Profit.
Edit: also Verizon RAZRs are xt926 not xt925
Darbness said:
Easy fix,
download what ever version of the system software you had on it previously.
Flash it in fast boot mode.
?????
Profit.
Edit: also Verizon RAZRs are xt926 not xt925
Click to expand...
Click to collapse
Phone identified itself as 925... either way, i am unsure where i can find stock software for it and seem to be unable to flash anything from fastboot, because as it turns out, i am code-retarded. definitely profit when this is solved. I can "cd" through dos and get to where fastboot commands are entered and I have even tried to "fastboot recovery recovery.img" but for the life of me, i must be typing the string incorrectly somehow. But I am excellent at following clear-cut directions. i will try to find a stock image...for motorola, it is a .sbf file, right? If i seem stupid, i apologize, i'm not. just not up on all the nomenclature native to adb and fastboot (or linux). Thanks for helping me though.....i need it.
Ok,
First thing I want you to do is look on the back of the phone, It will have the model on the lower half of it.
Second thing is to find the official software.
For XT96:
http://sbf.droid-developers.org/vanquish/list.php
For xt925
http://sbf.droid-developers.org/vanquish_u/list.php
Flash the ROM file using RSD Lite.
If it dosnt work:
Make sure you have the moto drivers installed.
open up the .xml file in the rom and remove the "getvar" lines.
Still trying
Failed at 16/27 flash system system.img
What version did you try?
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-4_VQW_CFC.xml
having a hard time finding other .xml files to use... any non-stock .xml available? really want to get into an AOKP/CM/PAC/Liquidsmooth/Carbon/Paranoid.....whatever is 4.2.2
No, only official roms are packaged like that.
You need to have RSDlite at least Version 6 or higher. Also, edit the xml file as stated here.
If your phone is up & running again you can consider going to another rom either with safestrap or by unlocking your BL, installing a recovery and flashing any ROM you like. As stated above you can only flash Stock FW using RSDLite. All other roms can only be applied with either safestrap or CWM Recovery (or similiar).
HELP-ME
FRIENDS, AFTER I TRY TO INSTALL A ROOM 4.2.2 MY PHONE NO OUT OF AP fastboot.
JA TRIED TO PUT ALL ROOMS OF MOTOROLA BUT NOT RESOLVED.
SCREEN IS BLACK AND PHONE DOES NOT NOTHING COULD HELP ME?: (
Hi everyone,
I end up here after loads of searchs and manipulations unsuccessful...
Well here is my problem :
Edit : The problem much advanced, but is still not resolved, see 5th post for more information of current status
Final Edit : Problem solved, see the 5th post.
I have a Motorola Razr HD XT925 which is Unlocked.
I tryed flashing a custom rom on it, and failed hard.
Before failing that hard, I had some backups which were working perfectly, those, don't work anymore ...
So here is what I can access :
Fastboot (works perfectly, I can access it from my PC also without any issues)
Recovery (works "perfectly", the only thing is I cant restore any backups and I can't flash any ROM well yet, tryed Factory Reset also, does not work)
Normal boot just remains on "Warning bootloader unlocked"
By the way, by doing all that my backups have gone from my phone, so I only have em on my computer which is a bit hard when you want to try a restore (on a backup that was working perfectly before).
Another thing I noticed, when trying to Factory reset for example, It says "Unable to mount '/data'" which is a bit hard if you want to write data ^^
If anyone has an idea, feel free to make a comment, any idea is accepted since I can't use my phone at all...
Feel free to ask any question if you need more information or if you did not understand something.
Here some more infos I got while using DroidHD Utility Deluxe :
The command "fastboot flash aboot file.mbn" leads to a "error: cannot load 'folder/file.mbn'"
I managed to get a functional Driod Razr XT925 OS working by using the tool I mentioned before : DriodHD Utility Deluxe
Everything works well except those :
I can't read any backups made with TWRP before that (I mean the backups which were functionnal but that I couldnt manage to get back on).
I can't make my SIM work anymore, it says, unknown sim, and no network available when I'm trying to use my phone with GSM functions.
Managed to get my backups work again. The folder was under another name, which is why TWPR couldnt find it.
One last problem, my /efs partition has left me You already see the problem ? No IMEI around !
So I managed to find my IMEI number again and trying to use that http://forum.xda-developers.com/showthread.php?t=1960918 to write it back on my phone.
But...cause there's a but, I cant seem to use my USB drivers when I boot up in "BP Tools".
So impossible to access the phone, and impossible to write that "recovered" IMEI...
Anyone has a solution roaming around ?
Well at least I can feel like not being a total dumb ^^ Managed to install manually the driver for QC Diag Port, by selecting "Motorola" > "Motorola QC Diag Port" manually.
So, the BP tools mode can now be accessed from my computer, but here is another problem, I can communicate with the phone and even write my IMEI, but not on the phone Sounds like the entry 555 (which was totally absent) is in read-only mode :/
Here is the error given by RF NV Manager :
NvManager::writeToPhone(comPort, nvItems, throwException) -Unable to write 'NV_UE_IMEI_I' to the phone. (Parameter is write-protected and thus read only)
A clue ? Anyone ? Before I find it alone again, I think I'll soon be bald considering how I tear my hair since some hours...
Edit :
Ok so I tryed the QPST thing on a 32bits XP computer. Same problem.
I also tryed flashing my ROM into the stock one with RSD Lite, which is called like that :
9.8.2Q-8-XT925_VQU-22_USERSIGNED_S7_UCAVANQU02NA02F.0R_LSAVNQJBRTFR_P007_A004_CFC
Found it here : http://forum.xda-developers.com/showthread.php?t=2032284
Under that name :
Branding: Retail France/Retail Central Europe
Version: 9.8.2Q-8-XT925_VQU-22 FULL
Android Version: 4.1.2
Bootloader Version: N/A
Requires RSD Lite 6.0
Click to expand...
Click to collapse
And got an error (even after removing the getvar command) which is :
Failed flashing process. 2/22 flash partition "partition_signed"->Phone returned FAIL
Click to expand...
Click to collapse
Here is what the fastboot screen says :
Fastboot reason: Flash Failure
usb connected
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
Click to expand...
Click to collapse
Final Edit (#Request lock) :
Ok so I finally got out of trouble.
Flashed to the stock rom with that rom : 9.8.2Q-8-XT925_VQU-22_USERSIGNED_S7_UCAVANQU02NA02F.0R_LSAVNQJBRTFR_P 007_A004_CFC
Found it here : http://forum.xda-developers.com/show....php?t=2032284
And applyed that homemade script (which gets rid of the cache memory problem before system flash) :
Code:
@echo off
fastboot flash sbl1 sbl1_signed
fastboot flash sbl2 sbl2_signed
fastboot flash sbl3 sbl3_signed
fastboot flash rpm rpm_signed
fastboot flash tz tz_signed
fastboot flash aboot aboot_signed
fastboot reboot-bootloader
echo. When the screen bcomes back on, press any key to continue!
pause
fastboot flash partition partition_signed
fastboot flash sbl1 sbl1_signed
fastboot flash sbl2 sbl2_signed
fastboot flash sbl3 sbl3_signed
fastboot flash rpm rpm_signed
fastboot flash tz tz_signed
fastboot flash aboot aboot_signed
fastboot flash boot boot_signed
fastboot erase cache
fastboot flash system system_signed
fastboot flash recovery recovery_signed
fastboot flash modem modem_signed
fastboot flash devtree devtree_signed
fastboot flash logo logo
fastboot flash cdrom cdrom_signed
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg_signed
fastboot erase cache
fastboot erase tombstones
echo. Press a key to reboot the phone
pause
fastboot reboot
Then when I came back on my phone, my IMEI was back itself like a big one
4 days of SMS came back at that time, I'm saved
Hybris95 said:
Hi everyone,
I end up here after loads of searchs and manipulations unsuccessful...
Well here is my problem :
Edit : The problem much advanced, but is still not resolved, see 5th post for more information of current status
Final Edit : Problem solved, see the 5th post.
I have a Motorola Razr HD XT925 which is Unlocked.
I tryed flashing a custom rom on it, and failed hard.
Before failing that hard, I had some backups which were working perfectly, those, don't work anymore ...
So here is what I can access :
Fastboot (works perfectly, I can access it from my PC also without any issues)
Recovery (works "perfectly", the only thing is I cant restore any backups and I can't flash any ROM well yet, tryed Factory Reset also, does not work)
Normal boot just remains on "Warning bootloader unlocked"
By the way, by doing all that my backups have gone from my phone, so I only have em on my computer which is a bit hard when you want to try a restore (on a backup that was working perfectly before).
Another thing I noticed, when trying to Factory reset for example, It says "Unable to mount '/data'" which is a bit hard if you want to write data ^^
If anyone has an idea, feel free to make a comment, any idea is accepted since I can't use my phone at all...
Feel free to ask any question if you need more information or if you did not understand something.
Click to expand...
Click to collapse
i have a same problem, could you tell me step by to solve it.. thanks before
---------- Post added at 01:35 PM ---------- Previous post was at 01:02 PM ----------
arinata1983 said:
i have a same problem, could you tell me step by to solve it.. thanks before
Click to expand...
Click to collapse
i realy need your help
arinata1983 said:
i have a same problem, could you tell me step by to solve it.. thanks before
---------- Post added at 01:35 PM ---------- Previous post was at 01:02 PM ----------
i realy need your help
Click to expand...
Click to collapse
My post clearly says the steps I made to get rid of my problem.
If you don't understand a step or want more information on a step, tell me which one at least.
Hybris95 said:
My post clearly says the steps I made to get rid of my problem.
If you don't understand a step or want more information on a step, tell me which one at least.
Click to expand...
Click to collapse
i dont understand where and how should i start for the homemade script...
where can i find the firmware?
arinata1983 said:
i dont understand where and how should i start for the homemade script...
where can i find the firmware?
Click to expand...
Click to collapse
You should be able to find your stock rom here (for JellyBean 4.1.2) :
http://forum.xda-developers.com/showthread.php?t=2032284
And here (for Ice Cream Sandwich 4.0.4) :
http://forum.xda-developers.com/showthread.php?t=1943879
Extract your stock rom into a folder then copy these files into this folder :
"fastboot.exe", "AdbWinApi.dll" and "AdbWinUsbApi.dll"
And about the script, write it into a file called "flash_fastboot_hybris.bat" using your favorite text editor (notepad or notepad++ for example).
Then copy this file into the stock rom folder.
Then boot up your smartphone into fastboot mode, plug it to your computer and execute "flash_fastboot_hybris.bat".
Follow the script insctructions, and your smartphone should be back to its stock recovery.
Tell me if you need some files or more information.
Hybris95 said:
You should be able to find your stock rom here (for JellyBean 4.1.2) :
http://forum.xda-developers.com/showthread.php?t=2032284
And here (for Ice Cream Sandwich 4.0.4) :
http://forum.xda-developers.com/showthread.php?t=1943879
Extract your stock rom into a folder then copy these files into this folder :
"fastboot.exe", "AdbWinApi.dll" and "AdbWinUsbApi.dll"
And about the script, write it into a file called "flash_fastboot_hybris.bat" using your favorite text editor (notepad or notepad++ for example).
Then copy this file into the stock rom folder.
Then boot up your smartphone into fastboot mode, plug it to your computer and execute "flash_fastboot_hybris.bat".
Follow the script insctructions, and your smartphone should be back to its stock recovery.
Tell me if you need some files or more information.
Click to expand...
Click to collapse
flashing succes, but it stuck on red circle motorola boot animation. i think i can't find a correct firmware...
and than, i try to flash stock firmware using droidHD utility 2.0 lite, i flashed it without modem (fastboot restore 4.1.2 stock (dont flash modem) )
and now my xt925 running on verizon's droid razrhd firmware without imei,everything running great,but the network stuck in edge.
what should i do now??
arinata1983 said:
flashing succes, but it stuck on red circle motorola boot animation. i think i can't find a correct firmware...
and than, i try to flash stock firmware using droidHD utility 2.0 lite, i flashed it without modem (fastboot restore 4.1.2 stock (dont flash modem) )
and now my xt925 running on verizon's droid razrhd firmware without imei,everything running great,but the network stuck in edge.
what should i do now??
Click to expand...
Click to collapse
For my own story, when I had successfully flash with droidHD utility, I flashed back using my own script and it worked.
If it doesn't then your problem is probably different from mine (your IMEI is probably corrupted), you could try using QPST and modify entry #550 with your own IMEI.
fixed
Hybris95 said:
For my own story, when I had successfully flash with droidHD utility, I flashed back using my own script and it worked.
If it doesn't then your problem is probably different from mine (your IMEI is probably corrupted), you could try using QPST and modify entry #550 with your own IMEI.
Click to expand...
Click to collapse
hey brother.. the problem was solved today
i tried to QPST, but it said that the system is write protected, and then i've find this post http://forum.xda-developers.com/showthread.php?p=46476292#post46476292
there are three steps, on the first step i really frustrated, flashing via rsd not work at all even i edit the script as told.
but i remember your " homemade script" it work perfectly....
i get my imei back just by flashing an ICS france firmware..
THANKS brother..
arinata1983 said:
hey brother.. the problem was solved today
i tried to QPST, but it said that the system is write protected, and then i've find this post http://forum.xda-developers.com/showthread.php?p=46476292#post46476292
there are three steps, on the first step i really frustrated, flashing via rsd not work at all even i edit the script as told.
but i remember your " homemade script" it work perfectly....
i get my imei back just by flashing an ICS france firmware..
THANKS brother..
Click to expand...
Click to collapse
You're welcome, I had been stuck like you which is why I made that homemade script
*** This process can relock your bootloader if you chose, but it does NOT restore your warranty in any way, so don't ask ***
Be aware you do NOT have to lock the bootloader, have Status Code of 0, or have it show "Official" status to successfully accept and apply an OTA update, it will happily apply with an unlocked bootloader and unofficial software status, as long as you have a 100% pure stock ROM installed the update script doesn't care what the bootloader reports.
Preflash validation error? See notes at the bottom of this post.
Prerequisites:
1) Fastboot installed and working. I used Linux Mint 18, but the OS is not relevant. There are are various threads discussing how to get this working, I am not covering it.
2) You need a factory firmware image that is the same version or newer than what you have installed (see below for more info), for me with a Moto X Pure Edition (XT1575) and wanting the latest MPH24.49-18-4 firmware, I used the image from this thread and extracted it into it's own directory. In Windows it is best to place this in the same folder as fastboot (probably the platform-tools folder)
XT1572 Factory Images: http://dl.prazaar.de/?dir=Android/XT1572/Factory courtesy of @Prazaar
XT1575 Factory Images: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833 - UPDATE: Direct link to XT1575 for 24.49-18-8 (Sept 1, 2016 security update) uploaded on 1/27/2017 courtesy of Motorola Firmware Team. The December 2016 security update image is NOT available as of yet!
Alternate firmware source for Pure and Style: https://firmware.center/firmware/Motorola/
XT1575 OTA ZIP file to go from 18-8 to 18-16 ONLY is available in this post for sideloading thanks to @annoyingduck
NOUGAT FIRMWARE (XT1575 ONLY): https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
OPTIONAL: 2a) Because when doing this procedure when you are done the logo when booting will still say your bootloader is unlocked, we can fix this by downloading the logo from this thread and extracting the bin file to the same folder as above.
Now, open a terminal or command window into the directory that contains the firmware files you extracted above, on Linux or Mac this could be anywhere, in my example I will use /home/acejavelin/Downloads/MXPE/18-4 as the directory, in Windows this will likely be the same as where your fastboot binary or platform-tools directory is, and follow these commands entering them ONE AT A TIME, do not just copy and paste the entire section. If you are using Linux, I recommend executing "sudo su" prior to beginning to prevent permission errors (this is shown in my sample attachment).
Code:
fastboot oem lock begin (see notes below if not wanting to lock)
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 flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
fastboot reboot
Note that in place of "fastboot flash logo logo.bin" you can substitute "fastboot flash logo XT1575-logo-new-9-14-15.bin" and it will work and validate at the end, and you will NOT get the bootloader unlocked screen any longer... I tested this and verified it to work.
This will return your bootloader status to LOCKED, although STATUS will still show 2, and your software status to OFFICIAL... It will pass SafetyNet for Android Pay, Pokemon GO, and banking/financial apps.
Remember that you will get checked for FRP even with this procedure, so either remove your Google account prior to this or know your credentials. This procedure will not bypass Factory Reset Protection in any way.
If you are interested in returning to stock WITHOUT locking the bootloader, then follow the above commands, but the following commands in place of the "lock" commands in the list above:
fastboot oem fb_mode_set instead of fastboot oem lock begin
fastboot oem fb_mode_clear instead of fastboot oem lock
The procedure for other XT157x device like the Style would be identical, except substitute your appropriate factory image. Note that different firmwares may contain a different number of system.img_sparsechunk.X files, you must flash the number you have in your firmware image in order. From what I have seen, most 5.1.1 firmwares have ten (0-9), 6.0 has nine (0-8), 6.0.1 has twelve (0-11), and 7.0 has ten (0-9) sparsechunks, but always verify with the XML flash file contained within the firmware archive to verify if you are in question.
If you lock with this process, you can unlock the bootloader again and even use the same unlock token... subsequent unlocking will wipe data as well. Doing this procedure will set OEM Locking option in Developer options to disabled, although it is perfectly safe to leave it like this, I suggest turning it on immediately since your warranty is gone and if something does go wrong you have the ability to unlock again to fix it.
NOTE: You must use a factory firmware image that is the same version as what you have installed or newer to successfully relock the bootloader, you cannot just grab the old (shipped) version from Moto's site. If you attempt to use a firmware image that is older than what you have installed currently, you will receive a Preflash Validation Error indicating such when you attempt to flash the partition table (gpt.bin). At this point you can either continue the flash and NOT lock the bootloader at the end, or stop until you can find the most current image. Moto used to be quite willing to hand these out when they were requested, so if you have a very new firmware installed you may not find one that you can use to relock with on the Internet. Part of the requirements to lock the bootloader is you must successfully flash the partition table (gpt.bin) in order to complete the lock process, if you can't then the bootloader lock process cannot be finished.
Also, some users have noted that after completing this process the software status does NOT go back to "Official", if it does not, upon accepting the OTA it should go back to official after the OTA is successful. The Status Code will always show 2 (relocked) or 3 (unlocked), and it can never go back to 0 (locked).
A proper flash log is attached to this guide.
Just a blurb on Marshmallow software versions... To determine what you need look at version/build numbers, here is the Security update dates and release dates (actual, not tests) of all known public OTA releases of Marshmallow for the Moto X Pure (Style varies somewhat). The initial release was MPH24.49-18 (sometimes MPH24.49-18_18, we don't know why, but it is the SAME versions), and all others after that are MPHS24.49-XX-XX as shown below.
18 or 18_18 - The initial (shipped) Marshmallow release for Moto X Pure, November 2015 (release via OTA in late-December 2015, incorrectly dated on Moto's official website as 01-SEP-16 in the "official" recovery images section, it is NOT the newest or recommended image to use)
18-3 - February 2016 (released for OTA in mid-March 2016)
18-4 - May 2016 (released for OTA in late-June 2016)
18-8 - September 2016 (released for OTA in early-November 2016)
18-16 - December 2016 (release for OTA in mid-February 2017) *** Not available as a factory image***
Nougat:
NPH25.200-22 - September 2017 (released for OTA September~November 2017) Factory image available as of 11/12/2017
NPH25.200-23 - Little is know about this version, it appears to be slowing rolling out to Verizon users only as of mid-November 2017 (no firmware available as of yet)
To see what version your bootloader is now, go into fastboot and perform a "fastboot getvar ro.build.fingerprint" and look at the output, it should be pretty clear.
NOTE: I no longer own this device, but will help where I can and will keep this thread open to assist users where ever possible, but I no longer have a device to test/verify things with.
acejavelin said:
*** This will relock your bootloader, but it does NOT restore your warranty in any way, so don't ask ***
So with Nougat coming, several people have asked how to return to stock to get the update... well, I just did this so here is a quick guide.
Prerequisites:
1) Fastboot installed and working. I used Linux Mint 18, but the OS is not relevant. There are are various threads discussing how to get this working, I am not covering it.
2) You need a factory firmware image, for me with a Moto X Pure Edition (XT1575) and wanting the latest MPH24.49-18-4 firmware, I used the image from this thread and extracted it into it's own directory. In Windows it is best to place this in the same folder as fastboot (probably the platform-tools folder)
OPTIONAL: 2a) Because when doing this procedure when you are done the logo when booting will still say your bootloader is unlocked, we can fix this by downloading the logo from this thread and extracting the bin file to the same folder as above.
Now, open a terminal or command window into the directory that contains the firmware files you extracted above, on Linux or Mac this could be anywhere, in my example I will use /home/acejavelin/Downloads/MXPE/18-4 as the directory, in Windows this will likely be the same as where your fastboot binary or platform-tools directory is, and follow these commands entering them ONE AT A TIME, do not just copy and paste the entire section. If you are using Linux, I recommend executing "sudo su" prior to beginning to prevent permission errors (this is shown in my sample attachment).
Code:
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot reboot bootloader
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
Note that in place of "fastboot flash logo logo.bin" you can substitute "fastboot flash logo XT1575-logo-new-9-14-15.bin" and it will work and validate at the end, and you will NOT get the bootloader unlocked screen any longer... I tested this and verified it to work.
This will return your bootloader status to LOCKED, although STATUS will still show 2, and your software status to OFFICIAL... It will pass SafetyNet for Android Pay and Pokemon GO as well.
Remember that you will get checked for FRP even with this procedure, so either remove your Google account prior to this or know your credentials. This procedure will not bypass Factory Reset Protection in any way.
The procedure for other XT157x device like the Style would be identical, except substitute your appropriate factory image.
A proper flash log is attached to this guide.
Click to expand...
Click to collapse
So, flash command for partition gpt.bin does work? I've never been able to lock bootloader due to failure to execute this command. But, I've always thought of downgrading, rather than flashing the same stock build!
donrojo said:
So, flash command for partition gpt.bin does work? I've never been able to lock bootloader due to failure to execute this command. But, I've always thought of downgrading, rather than flashing the same stock build!
Click to expand...
Click to collapse
Yes, of course it does... You can clearly see in the log I attached from my flashing the device.
The key is you cannot downgrade to a lower gpt.bin, you can only flash the same or newer version of firmware. After having several Moto devices, I can attest that downgrading successfully while locking is almost impossible. I will update my guide to make it clearer.
And please do not quote the entire first post and embed your comments in it, on mobile I had a very difficult time trying to determine what you were asking. EDIT: Sorry, your previous post looked very different in the XDA app, looks fine on computer... weird.
What is the purpose of relocking your bootloader? The unlocked bootloader has never interfered with me taking an OTA.
Thank you for this guide.
I have a question.
I'm currently on a relatively recent nightly of CM13, which I believe is based on 6.0.1.
I don't think the XT1575 ever got 6.0.1, only 6.0.
Is there a way around this issue other than waiting for 7.0 to hit officially?
quakeaz said:
What is the purpose of relocking your bootloader? The unlocked bootloader has never interfered with me taking an OTA.
Click to expand...
Click to collapse
You are correct, and this as nothing to do with accepting OTA (that is just how this discussion came up), but the lock/unlock state of the bootloader has two distinct issues I can think of although there maybe more I am forgetting.
1. Security - If your bootloader is unlocked, anyone who gets access to your device can just fire up fastboot and boot TWRP and access any information on your device, even if it is encrypted since TWRP can read the encryption password.
2. SafetyNet API - Do to recent changes by Google, SafetyNet API checks to fail just because the bootloader is unlocked, even if everything else is perfectly stock... SafetyNet is a mandatory part of Play Services that auto-updates itself regardless of your settings, and it is used to see if your device has been modified (rooted) or tampered with in anyway, and applications can use SafetyNet to check the status of your device... Sounds harmless enough, but for example this means that even an unlocked bootloader will make it so you can't use Android Pay or many other financial apps or even play Pokemon Go. Until recently, SafetyNet could be fooled with apps like RootCloak or Suhide, but Google has updated it to detect these things and look far beyond simple rooting. UPDATE: This only seems to be enforced on devices that shipped with Nougat or newer, and does seem to effect any device upgraded to Nougat so far. Lollipop and Marshmallow devices are not effected.
acejavelin said:
Sounds harmless enough, but for example this means that even an unlocked bootloader will make it so you can't use Android Pay or many other financial apps or even play Pokemon Go. Until recently, SafetyNet could be fooled with apps like RootCloak or Suhide, but Google has updated it to detect these things and look far beyond simple rooting.
Click to expand...
Click to collapse
Interesting, I've used Android Pay with my bootloader unlocked on the MXPE (otherwise stock, no root).
If you decide to unlock the bootloader again, I assume the original code supplied by Motorola is required? I've never relocked/unlocked.
Also, just an observation, I assume once we do get the Nougat (or any other) OTA, the unlocked bootloader warning screen will return, since the unlocked flag has already been tripped and the OTA will write a new logo.bin.
---------- Post added at 08:25 AM ---------- Previous post was at 08:20 AM ----------
Mejilan said:
Thank you for this guide.
I have a question.
I'm currently on a relatively recent nightly of CM13, which I believe is based on 6.0.1.
I don't think the XT1575 ever got 6.0.1, only 6.0.
Is there a way around this issue other than waiting for 7.0 to hit officially?
Click to expand...
Click to collapse
You're fine to downgrade to the latest stock firmware you were running.
quakeaz said:
Interesting, I've used Android Pay with my bootloader unlocked on the MXPE (otherwise stock, no root).
If you decide to unlock the bootloader again, I assume the original code supplied by Motorola is required? I've never relocked/unlocked.
Click to expand...
Click to collapse
Have you used Android Pay since October 16-18, such as to add a payment method/card? Because that is when Google made the changes to the SafetyNet API, and has committed to aggressively maintaining it to detect and report all "tamper" situations.
Yes, the original code works... Tested it myself, locked, unlocked, and locked again, works perfectly, and if you wish you can request the code again from Motorola if you lost the email or something, but it will still be the same code.
quakeaz said:
You're fine to downgrade to the latest stock firmware you were running.
Click to expand...
Click to collapse
Ah hah! Good to know.
Thank you.
acejavelin said:
Have you used Android Pay since October 16-18, such as to add a payment method/card? Because that is when Google made the changes to the SafetyNet API, and has committed to aggressively maintaining it to detect and report all "tamper" situations.
Yes, the original code works... Tested it myself, locked, unlocked, and locked again, works perfectly, and if you wish you can request the code again from Motorola if you lost the email or something.
Click to expand...
Click to collapse
Thanks for confirming about the unlock/relock/unlock.
I just added a CC to check if it'd work. No issues here. Maybe it's only certain devices? Google Play Services 9.8.77.
Mejilan said:
Thank you for this guide.
I have a question.
I'm currently on a relatively recent nightly of CM13, which I believe is based on 6.0.1.
I don't think the XT1575 ever got 6.0.1, only 6.0.
Is there a way around this issue other than waiting for 7.0 to hit officially?
Click to expand...
Click to collapse
The issue isn't the aftermarket firmware or it's version, it could be Android 29 Gamma for all we care... You need to use an official Moto firmware that is at least the same version or newer than your bootloader and partition table (gpt.bin), if you are not a stock firmware you will need to do some investigating via the baseband version what actual version you have (unless you can remember the last official firmware version).
Safest bet is just use the current release, if you can't find it online you can always request it from Moto service but this may take several days (weeks in some areas I have heard). Be aware that the firmware posted on Moto's official is NOT the most current and is likely a downgrade if you have ever accepted an OTA since the device was released.
quakeaz said:
Thanks for confirming about the unlock/relock/unlock.
I just added a CC to check if it'd work. No issues here. Maybe it's only certain devices? Google Play Services 9.8.77.
Click to expand...
Click to collapse
All I know is it didn't work for me on BrokenOS anymore, neither did Pokemon Go (not that big deal though), so I figured go all in...
There are multiple articles on this online, here are just a few...
http://www.xda-developers.com/android-safetynet-now-reportedly-tripped-by-unlocked-bootloaders/
http://www.androidpolice.com/2016/1...unlocked-android-phones-android-pay-affected/
http://www.androidcentral.com/andro...u-unlock-your-bootloader-and-thats-good-thing
acejavelin said:
The issue isn't the aftermarket firmware or it's version, it could be Android 29 Gamma for all we care... You need to use an official Moto firmware that is at least the same version or newer than your bootloader and partition table (gpt.bin), if you are not a stock firmware you will need to do some investigating via the baseband version what actual version you have (unless you can remember the last official firmware version).
Safest bet is just use the current release, if you can't find it online you can always request it from Moto service but this may take several days (weeks in some areas I have heard). Be aware that the firmware posted on Moto's official is NOT the most current and is likely a downgrade if you have ever accepted an OTA since the device was released.
Click to expand...
Click to collapse
Understood, thank you.
I haven't been on stock since the first half of the year.
I honestly don't remember if my last stock build was 5.1.1 or 6.0, but regardless, I should be good to go if I just download the newest stock and attempt your tutorial.
Again, many thanks.
Does the relocking procedure wipe userdata like unlocking does? I am considering relocking as most of the Android Pay issues with unlocked bootloader seem to be with N. I'm already running stock so I was thinking I could just begin lock process, reflash same stock images, complete lock, skipping the erase userdata command.
quakeaz said:
Does the relocking procedure wipe userdata like unlocking does? I am considering relocking as most of the Android Pay issues with unlocked bootloader seem to be with N. I'm already running stock so I was thinking I could just begin lock process, reflash same stock images, complete lock, skipping the erase userdata command.
Click to expand...
Click to collapse
Probably, my assumption is you can't complete the process without erasing cache and userdata, as 'fastboot oem lock' will likely fail, but to be honest I did not test it. Basically to get it complete you must follow all steps of the flashing XML file in the firmware file.
acejavelin said:
Probably, my assumption is you can't complete the process without erasing cache and userdata, as 'fastboot oem lock' will likely fail, but to be honest I did not test it. Basically to get it complete you must follow all steps of the flashing XML file in the firmware file.
Click to expand...
Click to collapse
Interesting. I may give it a shot, if I do I'll report back here. The erase userdata and cache commands are optional according to Motorola.com factory image download page instructions. I've done normal stock reflash without them.
quakeaz said:
Interesting. I may give it a shot, if I do I'll report back here. The erase userdata and cache commands are optional according to Motorola.com factory image download page instructions. I've done normal stock reflash without them.
Click to expand...
Click to collapse
Good luck... Let me know how it goes, but I think that only works for developer models, on "normal" models you have to do oem lock begin before oem lock though, not the same process.
delete wrong thread
Can't seem to boot up
Hi, so I flashed using this guide, I'm using the XT1572 model in the UK and used the appropriate firmware etc, my issue is that after everything had finished and I rebooted, it was stuck booting for an hour, I know this phone can sometimes take a while to boot after a factory reset but I haven't experienced it this badly before, also, I flashed the moto splash screen image but the boot animation is still the one from AICP :/ any help would be appreciated guys
JIMMMEHHHH said:
Hi, so I flashed using this guide, I'm using the XT1572 model in the UK and used the appropriate firmware etc, my issue is that after everything had finished and I rebooted, it was stuck booting for an hour, I know this phone can sometimes take a while to boot after a factory reset but I haven't experienced it this badly before, also, I flashed the moto splash screen image but the boot animation is still the one from AICP :/ any help would be appreciated guys
Click to expand...
Click to collapse
Your flash didn't take... Do you have a log of flash attempt from the terminal?
Also, sometimes the firmware has different numbers of system sparse chunks, it's not always 8, and sometimes it only has "system.img" as a single file, you have to flash what it shows in the XML file contained within the firmware archive.
Hi guys, I need help, because I can't relock my bootloader. I have Honor 8 L09C432
I was on Carbon ROM and I had TWRP installed, and I wanted to go back to stock ROM, so I followed a procedure that I found in a comment on some thread.
( This is a screenshot of a comment that I followed, if that means anything to you ) https://forum.xda-developers.com/attachment.php?attachmentid=4385584&stc=1&d=1515621906
I successfully returned to EMUI 5.0 and I'm currently on B360, and I wanted to update to B381. I got an OTA, I downloaded it, but installation failed, and that's, I guess, because the bootloader is unlocked.
I tried to lock the bootloader with some adb commands:
-adb devices ( my device would appear )
-adb reboot bootloader
-fastboot oem lock * Bootloader code *
and then I would get a message that says " FAILED (remote: Command not allowed) "
( Here's also a screenshot of that too ) https://dl.xda-developers.com/4/3/8/5/5/8/5/Capture2.PNG?key=L_OuO3DslYw7HJaIJW-mGw&ts=1515622403
I enabled USB Debugging and OEM unlock options in Developer options, but it still doesn't work...
If someone's knows why this is happening, or how can I update the phone without even locking, I would really appreciate that, thank you in advance, and If I didn't mention something that may be important, please tell me, so I can help you to help me
Use fastboot oem relock instead of lock.
Note that relocking isn't the same as locking, for that you'd have to flash something like MM via dload which automatically locks the bootloader. Some other official packages might work, too
Edit: Also you need to be in fastboot mode to actually use the fasboot commands. (power+vol. down)
I'm not sure if an unlocked bootloader should actually break the OTA but it's been a while.
You can just download the flashable (for TWRP) versions from FF ( the full ota mf-pv) and use those otherwise
Sent from my OnePlus5 using XDA Labs
I tried Fastboot oem relock too, but that also didn't work, and I was in fastboot mode when I typed in the commands. I don't have TWRP since I installed stock ROM ( EMUI ). I guess you are suggesting that I should downgrade to MM, so then the bootloader will be locked? Still, thank you for your time and help!
You don't need to lock the bootloader in order to take an update. However, you must have the stock boot and recovery .img loaded for it to work. Here is a link for instructions on how to do this. Keep in mind that my instructions only talk about extracting the boot.img, but in your case it is probably best to extract both the boot and recovery.img just like the video shows. Use the B360 firmware to extract the files from. This will ensure all of your partitions are stock and that will hopefully allow you to take the update OTA.
sic0048 said:
You don't need to lock the bootloader in order to take an update. However, you must have the stock boot and recovery .img loaded for it to work. Here is a link for instructions on how to do this. Keep in mind that my instructions only talk about extracting the boot.img, but in your case it is probably best to extract both the boot and recovery.img just like the video shows. Use the B360 firmware to extract the files from. This will ensure all of your partitions are stock and that will hopefully allow you to take the update OTA.
Click to expand...
Click to collapse
I'll try this method, thank you very much for your help and time :angel: