I have this Z2 Force, but it has this problem, since it does not pass this screen, I connect it to my computer and it does not detect it, it has a solution or someone that can help me solve this problem.
martin13x said:
I have this Z2 Force, but it has this problem, since it does not pass this screen, I connect it to my computer and it does not detect it, it has a solution or someone that can help me solve this problem.
Click to expand...
Click to collapse
The same thing happens to me, I can not restore it in any way, I have a "Moto Z2 Force - XT1789-01" new since I got updated android stopped working and I see that.
Well so I'm seeing your firmware is retail, it's easier than my problem, I'll help you, do the following:
1 - Download the motorola drivers and install it: motorola-global-es-latam.custhelp.com/app/answers/prod_detail/a_id/81815
2 - Try to enter the "Recovery Mode" from the "Fastboot", then press the "Volume -" key next to the "Power" key for 2 seconds and then execute the "Wipe" option you can choose to delete your information together to the system or separately, I recommend doing everything full if you really do not need the information stored within your device, to restore the official and original rom as it was previously.
Note: In the event that you can not enter "Recovery Mode", do the following:
1 - Download the Android SDK - Platform Tools r27.0.1: keybase.pub/farwayer/arch/mobile/android-sdk-platform-tools-r27.0.1-1-x86_64.pkg.tar.xz
2 - Download the Firmware for your Retail Version: firmware.center/firmware/Motorola/Moto%20Z2%20Force/Stock/NASH_RETAIL_8.0.0_OPX27.109-34_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
3 - Unzip the Rom in a folder on the desktop that is called "Firmware" and inside that same folder unzip the file "Fastboot.exe, AdbWinApi.dll and AdbWinUsbApi.dll" from the tool "Platform Tools r27.0.1" all the files remain together.
4 - Then copy the path to your directory where you created the "Firmware" folder, for example: C: \ Users \ "TuUser" \ Desktop \ Firmware and paste it into the console.
commands (CMD) always without executing in administrator mode, with the word "cd" above, it should look like this: cd C: \ Users \ "YourUser" \ Desktop \ Firmware
Note: It must be with the cell phone on and connected by USB cable to the computer in the "Fastboot Mode".
5 - You execute the following chain of commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot bluetooth flash BTFM.bin
fastboot flash dsp adspo.bin
fastboot flash logo logo.bin
fastboot flash boot boot.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Note: If it fails you from the command "fastboot flash boot boot.img" and gives an error like the following:
Executing ". \ Windows \ fastboot.exe -s ZY224GBN8V flash boot boot.img"
target reported max download size of 536870912 bytes
sending 'boot_a' (23353 KB) ...
OKAY [0.501s]
writing 'boot_a' ...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished Total time: 0.677s
All devices are flashed
It is because you will have to Unlock the "Bootloader" and that is done as follows:
Note: When you unlock the "Bootloader" you lose the guarantee, so from that moment it is your responsibility to continue or stop here.
1 - Enter the Motorola page to request the deactivation code: accounts.motorola.com/ssoauth/login?TARGET=https://motorola-global-portal.custhelp.com/cc/cas/sso/redirect/standalone % 2Fbootloader% 2Funlock-your-device-b
2 - In the command console (CMD) without entering the administrator mode, copy the same path where you have the files in the folder "Firmware" and the adhere as explained in the previous point so you can execute the following command:
fastboot oem get_unlock_data
3 - Copy the rows of numbers and paste in the motor tool "Data Scrub Tool" so that you combine all the lines in one and you can copy the final code correctly in the box "Can my device be unlocked?" Once done, press the button you confirm the pop-up window and then click on the "I Agree" box and below it appears a button to request the code via email with which you entered the Motorola website.
4 - In CMD, enter the following command:
fastboot oem unlock "Your unlock code that was sent to the mail box"
5 - Download the tool "TWRP - Nash v3.2.1.0 R3": mirrors.lolinet.com/firmware/twrp/nash/
6 - Unzip the iso in the "Firmware" directory and rename it as "Recovery", then install it with the command:
fastboot flash recovery recovery.img
fastboot reboot
7 - Enter the "Fastboot Mode" again and select the option "Recovery Mode" once in search for the option "Wipe" to erase everything that has the device in case you can not find it, type the following commands in CMD:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot erase carrier
fastboot erase ddr
8 - Then you restart the device and enter "Mode Fastboot" again and execute the following chain of commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot bluetooth flash BTFM.bin
fastboot flash dsp adspo.bin
fastboot flash logo logo.bin
fastboot flash boot boot.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
9 - With this I should install and operate correctly.
Note: You can download the tool "SuperSU v2.82" and install using the "Recovery Mode" to be able to have Super User permissions on your device or access "Root" and thereby eliminate the gaps that are predetermined in the firmware as many others privileges.
I hope you have helped, many luck, greetings.
Thank you very much friend I will try to do that tutorial that you say if I can recover my cell phone.
VFArts said:
Well so I'm seeing your firmware is retail, it's easier than my problem, I'll help you, do the following:
1 - Download the motorola drivers and install it: motorola-global-es-latam.custhelp.com/app/answers/prod_detail/a_id/81815
2 - Try to enter the "Recovery Mode" from the "Fastboot", then press the "Volume -" key next to the "Power" key for 2 seconds and then execute the "Wipe" option you can choose to delete your information together to the system or separately, I recommend doing everything full if you really do not need the information stored within your device, to restore the official and original rom as it was previously.
Note: In the event that you can not enter "Recovery Mode", do the following:
1 - Download the Android SDK - Platform Tools r27.0.1: keybase.pub/farwayer/arch/mobile/android-sdk-platform-tools-r27.0.1-1-x86_64.pkg.tar.xz
2 - Download the Firmware for your Retail Version: firmware.center/firmware/Motorola/Moto%20Z2%20Force/Stock/NASH_RETAIL_8.0.0_OPX27.109-34_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
3 - Unzip the Rom in a folder on the desktop that is called "Firmware" and inside that same folder unzip the file "Fastboot.exe, AdbWinApi.dll and AdbWinUsbApi.dll" from the tool "Platform Tools r27.0.1" all the files remain together.
4 - Then copy the path to your directory where you created the "Firmware" folder, for example: C: \ Users \ "TuUser" \ Desktop \ Firmware and paste it into the console.
commands (CMD) always without executing in administrator mode, with the word "cd" above, it should look like this: cd C: \ Users \ "YourUser" \ Desktop \ Firmware
Note: It must be with the cell phone on and connected by USB cable to the computer in the "Fastboot Mode".
5 - You execute the following chain of commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot bluetooth flash BTFM.bin
fastboot flash dsp adspo.bin
fastboot flash logo logo.bin
fastboot flash boot boot.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Note: If it fails you from the command "fastboot flash boot boot.img" and gives an error like the following:
Executing ". \ Windows \ fastboot.exe -s ZY224GBN8V flash boot boot.img"
target reported max download size of 536870912 bytes
sending 'boot_a' (23353 KB) ...
OKAY [0.501s]
writing 'boot_a' ...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished Total time: 0.677s
All devices are flashed
It is because you will have to Unlock the "Bootloader" and that is done as follows:
Note: When you unlock the "Bootloader" you lose the guarantee, so from that moment it is your responsibility to continue or stop here.
1 - Enter the Motorola page to request the deactivation code: accounts.motorola.com/ssoauth/login?TARGET=https://motorola-global-portal.custhelp.com/cc/cas/sso/redirect/standalone % 2Fbootloader% 2Funlock-your-device-b
2 - In the command console (CMD) without entering the administrator mode, copy the same path where you have the files in the folder "Firmware" and the adhere as explained in the previous point so you can execute the following command:
fastboot oem get_unlock_data
3 - Copy the rows of numbers and paste in the motor tool "Data Scrub Tool" so that you combine all the lines in one and you can copy the final code correctly in the box "Can my device be unlocked?" Once done, press the button you confirm the pop-up window and then click on the "I Agree" box and below it appears a button to request the code via email with which you entered the Motorola website.
4 - In CMD, enter the following command:
fastboot oem unlock "Your unlock code that was sent to the mail box"
5 - Download the tool "TWRP - Nash v3.2.1.0 R3": mirrors.lolinet.com/firmware/twrp/nash/
6 - Unzip the iso in the "Firmware" directory and rename it as "Recovery", then install it with the command:
fastboot flash recovery recovery.img
fastboot reboot
7 - Enter the "Fastboot Mode" again and select the option "Recovery Mode" once in search for the option "Wipe" to erase everything that has the device in case you can not find it, type the following commands in CMD:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot erase carrier
fastboot erase ddr
8 - Then you restart the device and enter "Mode Fastboot" again and execute the following chain of commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot bluetooth flash BTFM.bin
fastboot flash dsp adspo.bin
fastboot flash logo logo.bin
fastboot flash boot boot.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
9 - With this I should install and operate correctly.
Note: You can download the tool "SuperSU v2.82" and install using the "Recovery Mode" to be able to have Super User permissions on your device or access "Root" and thereby eliminate the gaps that are predetermined in the firmware as many others privileges.
I hope you have helped, many luck, greetings.
Click to expand...
Click to collapse
VFArts said:
Note: You can download the tool "SuperSU v2.82" and install using the "Recovery Mode" to be able to have Super User permissions on your device or access "Root" and thereby eliminate the gaps that are predetermined in the firmware as many others privileges.
I hope you have helped, many luck, greetings.
Click to expand...
Click to collapse
SuperSU is no longer being developed. Magisk is the suggested and more reliable root for our phone.
Sent from my Moto Z (2) using XDA Labs
VFArts said:
Well so I'm seeing your firmware is retail, it's easier than my problem, I'll help you, do the following:
I also have the problem of 1789-03. I can not unlock because I need to enable it OEM unlocking' in Android Settings > Developer
"(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options"
But I can not boot into the system !!!!
Please HELPP!!!!
Click to expand...
Click to collapse
Related
Dear All,
After upgrading to Nougat 7.0 April patch with the following commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash system system.img_sparsechunk.3
fastboot.exe flash system system.img_sparsechunk.4
fastboot.exe flash system system.img_sparsechunk.5
fastboot.exe flash system system.img_sparsechunk.6
fastboot.exe flash system system.img_sparsechunk.7
fastboot.exe flash system system.img_sparsechunk.8
fastboot.exe flash system system.img_sparsechunk.9
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
My phone works normally but if i shut down and power on ,the phone boots on fastboot and I have to press on start to boot on OS . Additionally the id status has changed to bad key (previous on n/a status).
I get the update notification to 7.1.1 but because it cannot boot to recovery mode (which is part of the update procedure ) directly and it boots on fastboot mode, the update fails.
Any suggestion?
Looks like you set fastboot mode when you flashed, and just forgot to clear it.
Try rebooting to bootloader
Connect your device to your computer
In the ADB terminal, type 'fastboot oem fb_mode_clear' without the quotes and execute the command.
Reboot and see if that clears the block.
echo92 said:
Looks like you set fastboot mode when you flashed, and just forgot to clear it.
Try rebooting to bootloader
Connect your device to your computer
In the ADB terminal, type 'fastboot oem fb_mode_clear' without the quotes and execute the command.
Reboot and see if that clears the block.
Click to expand...
Click to collapse
you re MY MAN . thx a lot!
I lost my biometric sensor after leaving the test soak and go to a custom rom, how can I recover before leaving the final oreo stock?
eduh9 said:
I lost my biometric sensor after leaving the test soak and go to a custom rom, how can I recover before leaving the final oreo stock?
Click to expand...
Click to collapse
Hi, this happened to me, back to the stock rom (Android 7.0) of the device and do the whole procedure. And your sensor will work
Be careful to do not downgrade your bootloader though.
This tutorial helped me to recover biometrics in my phone (XT1676, reteu, 3/16, DualSIM).
I am not responsible for any damage! If you proceed to follow this, you're doing it at your own risk.
1. Make sure, your adb and fastboot is working.
I recommend using this one https://forum.xda-developers.com/showthread.php?t=2588979 . For me, it's fully working on Win8.1 x64. If you install it (press "Y" for all of 3 questions), but after connecting phone you see "Fastboot cedric S" with yellow exclamation mark in device manager, there's problem with driver: right click on it --> "Update driver software" --> "Browse my computer for driver software" --> "Let me pick from a list of device drivers on my computer" --> "Android devices" --> "Android Bootloader Interface" --> "Next" --> "OK" --> "Close"
(Open cmd and use "cd" command to get to directory, where's adb installed (in this case "cd C:\adb"). Then, press Enter and type "Fastboot devices". If fastboot is properly installed with corresponding drivers, you will see your device listed.)
2. Download this firmware https://drive.google.com/file/d/1hlNzlFhLCEj6xigfKrYcvnwH9jy3f5j3/view and extract it to the same directory as adb is installed.
3. Boot your phone into fastboot mode by pressing and holding power and vol- buttons for few seconds.
4. NOW, THE MOST IMPORTANT PART! Check your bootloader version.
4a. If your bootloader version is B8.25, use these commands to flash:
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
4b. If your bootloader is B8.24 and lower, use these commands:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
5. Your phone should reboot and sucessfully boot into OS in few minutes with fingerprint working.
DON'T EVEN TRY TO TAKE OTA UPDATES.
6. (optional) However, if you want to update your phone, update it manually with correct files from this site https://forum.xda-developers.com/g5/how-to/cedric-ota-archive-t3795275
Moto g5, has a biometric sensor?
666km666 said:
Moto g5, has a biometric sensor?
Click to expand...
Click to collapse
Of course, it has (fingerprint sensor at the front, under the display).
johnnywilly16 said:
Hi, this happened to me, back to the stock rom (Android 7.0) of the device and do the whole procedure. And your sensor will work
Click to expand...
Click to collapse
Sorry I'm just confirming that I need to go to stock 7.0 first? Will the debloated stock 7.0 be good enough?
eduh9 said:
I lost my biometric sensor after leaving the test soak and go to a custom rom, how can I recover before leaving the final oreo stock?
Click to expand...
Click to collapse
For anyone who finds this there is a flastable Nougat zip for Cedric which fixes finger print scanner, it is in the same thread as the soak 8.1 zip. I hope this saves others trouble as it did me. Find direct answers in telegram:
@cedricNOOBchat
WARNING: DO NOT FLASH THE GPT.BIN OR THE BOOTLOADER.IMG/MOTOBOOT.IMG ON A NEWER FIRMWARE WHEN DOWNGRADING, BECAUSE IT CAN HARD BRICK YOUR DEVICE E.G. DO NOT FLASH THE GPT.BIN OR THE BOOTLOADER.IMG/MOTOBOOT.IMG MADE FOR 7.0 ON 8.1.0 EVEN IF THE FILES IN THE FOLDER BUT ITS FINE IF YOU FLASH THE SAME FILES MADE FOR ANDROID 8.1.0 AVOID FLASHING THESE FILES AT ALL TIMES
I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DEVICE, DO THIS AT YOUR OWN RISK
so a little backstory,
i unlocked my bootloader because i wanted to downgrade back to android 7.0, and then my imei broke on me, so i attempted to upgrade back to android 8.1.0 but then everytime i rebooted my phone i see;
"your device is unlocked and cant be trusted
ID: bad key
your device will reboot in 5 seconds"
then would just loop into the bootloader
and when flashing the logo back it will just say "bad key" when editing logo.bin (changing the logo_unlocked to logo_boot)
with this guide i will tell you how to revert your device back to OOB state (OOB means out of box for all those idiots out there )
THIS WAS TESTED ON MY XT1675 IT WILL BE DIFFERENT FOR EACH DEVICE
1) grab your stock firmware, for me its "XT1675_CEDRIC_RETGB_SS_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml"
2) install minimal ADB and fastboot
3) then once you installed the adb and fastboot drivers we are really just focusing on the fastboot.exe, i will be linking the platform-tools at the bottom of this post
4) extract the firmware to a place and make sure there are no spaces (e.g. C:/Users/Example/Desktop/moto g5 downgrade otherwise cmd will assume its another path to another folder)
5) the most important file is oem.img because this is the signed file by motorola that we will need to relock the bootloader but it should come in the firmware folder, if not PM me and will try my best to find the matching oem.img
6) once you get all your files type these commands to reload the firmware onto the device
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
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 erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
what you will find now is it will at least boot into the setup screen
we are not done yet!
7) now if you reboot into the bootloader screen the options will be seriously messed up (they will overlap if you press up and down on the volume keys, i think this tells motorola that you tampered with your device)
8) now still on the bootloader screen connect up your device with cmd still open, then type these commands
fastboot oem lock
fastboot oem lock (you have to type it twice)
fastboot flash oem oem.img (you need this to relock the bootloader)
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.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 boot boot.img
fastboot oem lock
now it will say (lock complete! flash signed images after reboot if needed)
type in
fastboot reboot
now when you reboot your device you will get a black screen then it will show the motorola logo, to fix this go into the bootloader mode and reflash your original bootlogo
you got your device up and running like it did OOB!
LINKS:
Minimal adb and fastboot: https://forum.xda-developers.com/showthread.php?t=2317790
platform tools: https://developer.android.com/studio/releases/platform-tools
if your getting "image signed with key bad key when flashing the boot.img and the recovery.img, i found this really helpful tutorial, just do not flash the files on the G5, this is made for the G5 plus but the bootloader commands works for the G5 as well as the G5 plus
Link: https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
also if you get "still requires signed system.img and/or boot.img flash all the system sparsechunk files
I can't re-lock bootloader, getting "(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer" when I run "fastboot oem lock" second time. Please, help!
gkornaks said:
I can't re-lock bootloader, getting "(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer" when I run "fastboot oem lock" second time. Please, help!
Click to expand...
Click to collapse
You need to enable oem unlock in developer settings
mattwhite7102 said:
You need to enable oem unlock in developer settings
Click to expand...
Click to collapse
I am having the same error of "Allow OEM unlock" in the android setting, and the option in the developer setting of android is grayed out. I can't switch it.
Hi Everyone,
Those of you who have unlocked the OEM with a key, realize the 'bad key' error that shows up afterwards.
If you are trying to restore your phone back to factory image, the default images can be downloaded here:
Link to Factory Images
lexiyuri has a post on restoring the G7 to stock images as described here.
However, for me the bad key error didn't go away and finally ended up with additional steps in between to lock the oem. The commands below in that sequence worked for me. I don't see the 'bad key' error any more. If you're also struggling with the 'bad key' display on your g7 play, and would like to restore to stock properly, here's the code.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot oem lock begin
fastboot oem lock begin
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot oem lock
fastboot flash logo logo.bin
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase DDR
fastboot erase cache
fastboot erase carrier
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Hope this helps,
First of all this is a guide to lock your bootloader. You shouldn't provide a link to retail builds for this. Always use the current builds matching to your specific software channel.
Before you run any lock command you must check if your system is running. Finish the installation wizard and do a reboot. After that you should run the oem lock command. The very last step is to deactivate the OEM unlock option.
Moto Z2 Play was running Andorid 9.0 29.133.30 I was trying to downgrade to Android 8 by using fastboot but it kept on failing, to make sure it didn't mess with anything else I flashed the Android 9 ROM on via fastboot and all the fastboot commands were successful but now it ONLY booting into fastboot saying "Error: Failed to pass validation. backup to fastboot"
Any help?
Here's the commands used.
Spoiler: Code
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
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 system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
Right after I posted this thread I found my solution... The script I yoinked from the Android 8 ROM was missing one sparsechunk, got it working again now.
Will never do that again.
TechnoRush said:
Right after I posted this thread I found my solution... The script I yoinked from the Android 8 ROM was missing one sparsechunk, got it working again now.
Will never do that again.
Click to expand...
Click to collapse
I recommend creating your own .bat file from the flash_file.xml
Use a batch file for easier flashing
Online FlashFile Converter