Related
OTA currently being deployed, but there are no signs of the FXZ or SBF files. Motorola has not released them and no one has tried the MDM update trick (method explained by similar threads) for the XT1053 model.
If any user acquires it, please upload it and post link here. Thank you.
Let's hope for the best!
Looks like the recovery images for xt1053 have been posted to the moto customer portal:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
This is great news!!! Trying to get access to it now...
UPDATE: I was able to flash successfully from a windows box.
----------------------------------
I seem to be having some issues with flashing system.img, hopefully I'm just doing something wrong. Using the copy of fastboot within the Darwin folder of the download and I'm on OSX 10.10.3 if that matters.
------------------------------------------------------------------------------
./fastboot flash system ../system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
Sparse-Flash is enabled!
sending sparse 'system' (785466 KB)...
OKAY [ 49.379s]
writing 'system'...
OKAY [ 36.278s]
sending sparse 'system' (587908 KB)...
OKAY [ 37.032s]
writing 'system'...
(bootloader) Invalid sparse image data
OKAY [ 0.192s]
finished. total time: 122.882s
------------------------------------------------------------------------------
Hm, this is great news. I honestly wasn't expecting the SBF to be posted this soon.
Now, how does one go about turning it into an xml.zip?
JimJ2Mz said:
Hm, this is great news. I honestly wasn't expecting the SBF to be posted this soon.
Now, how does one go about turning it into an xml.zip?
Click to expand...
Click to collapse
just use fastboot.. Moto probably included the bat file for it anyway (like they did with 4.4.4)... or you can probably grab the XML out of the 4.4.2 SBF and pretty much use it with the 5.1 files.
EDIT: No, at least on the XT1053 5.1 rom on their site, Moto did not include either a BAT file for fastboot, nor did they include the XML for RSDlite...
To make your own FLASH.BAT... open notepad... copy/paste the following lines into it.. save as.. "all files" and name it flash.bat... (copied directly from the flash.bat included in the XT1053 4.4.4 rom on Moto's site.)
Code:
SET fastboot=mfastboot.exe
%fastboot% getvar max-download-size
%fastboot% oem fb_mode_set
%fastboot% flash partition gpt.bin
%fastboot% flash motoboot motoboot.img
%fastboot% reboot-bootloader
%fastboot% flash logo logo.bin
%fastboot% flash boot boot.img
%fastboot% flash recovery recovery.img
%fastboot% flash system system.img
%fastboot% flash modem NON-HLOS.bin
%fastboot% erase modemst1
%fastboot% erase modemst2
%fastboot% flash fsg fsg.mbn
%fastboot% erase cache
%fastboot% erase userdata
%fastboot% erase customize
%fastboot% erase clogo
%fastboot% oem fb_mode_clear
pause
NOTE: this does ASSUME that you are using the fastboot included in the rom you downloaded which is moto's fastboot. Using stock fastboot from the Android SDK/Platformtools will fail flashing system.img due to its size.
Thanks for the find! Can I flash the developer edition ROM onto my 16gb GSM unlocked XT1053?
bub181 said:
Thanks for the find! Can I flash the developer edition ROM onto my 16gb GSM unlocked XT1053?
Click to expand...
Click to collapse
The GSM Developer Edition XT1053, and the XT1053's sold on MotoMaker as GSM Unlocked (ships with T-Mobile SIM) and GSM Unlocked (ships with Net10 SIM) all use the same ROM/SBF/FXZ files.
KidJoe said:
The GSM Developer Edition XT1053, and the XT1053's sold on MotoMaker as GSM Unlocked (ships with T-Mobile SIM) and GSM Unlocked (ships with Net10 SIM) all use the same ROM/SBF/FXZ files.
Click to expand...
Click to collapse
Ok great thanks. I'm just waiting for Motorola to give me access to the download. If someone already has it could they post here please?
bub181 said:
Ok great thanks. I'm just waiting for Motorola to give me access to the download. If someone already has it could they post here please?
Click to expand...
Click to collapse
Please someone post it here!!!
bub181 said:
Ok great thanks. I'm just waiting for Motorola to give me access to the download. If someone already has it could they post here please?
Click to expand...
Click to collapse
santiagute said:
Please someone post it here!!!
Click to expand...
Click to collapse
Only took me about 2hrs wait to get link last night when I requested.
Why does motorola take 4 hours to approve a download?
Motorola let me access to file. Downloading now. 880 MB.
ufukcoskun said:
Motorola let me access to file. Downloading now. 880 MB.
Click to expand...
Click to collapse
Shared already
Hello, i'm uploading a backup of the OTA update for XT1053 i did with TWRP after wiping data, dalvik cache and factory reset twice.
It is rooted and i removed some system apps i don't use like email and some google apps like google books, movies, etc.
Don't know if it will work flashing as a restore with TWRP as i didn't test.
Should i keep uploading or i better cancel the thing?
I'm downloading the 5.1 files now and I have a question because it's been a while since I've done any flashing with this device and remember it being a pita to work with.
If I do this part
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
Click to expand...
Click to collapse
but not this part
$ fastboot erase userdata
$ fastboot erase cache
Click to expand...
Click to collapse
it won't wipe any of my data or settings, correct?
csos95 said:
I'm downloading the 5.1 files now and I have a question because it's been a while since I've done any flashing with this device and remember it being a pita to work with.
If I do this part
but not this part
it won't wipe any of my data or settings, correct?
Click to expand...
Click to collapse
fastboot erase userdata would wipe the phone, apps, data, like a factory reset.
fastboot erase cache will wipe the phone's cache.. since you are upgrading to 5.1 which uses art and not Dalvik, its worth erasing cache.
I'm having a problem after flashing. Now when I try to boot my phone it goes straight to recovery. I tried reflashing and restoring from a backup, but neither works.
Looking at the terminal in recovery, it's showing that it can't mount /cache either
EDIT: fixed it by manually formatting /cache, restored from backup(still didn't boot), flashed stock 4.4.4, and now im on android is upgrading. So I guess not lollipop for me for now
EDIT 2: got 5.1 ota notification as soon as motorola update services update. It's 694.6MB and it's claiming 122 minutes left to download
EDIT 3: I now have 5.1 installed and working.
lavero.burgos said:
Hello, i'm uploading a backup of the OTA update for XT1053 i did with TWRP after wiping data, dalvik cache and factory reset twice.
It is rooted and i removed some system apps i don't use like email and some google apps like google books, movies, etc.
Don't know if it will work flashing as a restore with TWRP as i didn't test.
Should i keep uploading or i better cancel the thing?
Click to expand...
Click to collapse
Here's the link: https://drive.google.com/file/d/0B3XeIVyUffMKVm1rbUdCbWpwd0U/view?usp=sharing
I downloaded 5.1 file from the following link. After flashing it, my system version is "222.21.15.ghost_row.Retail.en.US vzw" and my bootloader is also "Verizon" although my device is XT1053. How can i solve it?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Hello guyz do you have or post the latest version stock rom for Moto G4 Plus XT1643 ?
Waiting eagerly for your heads up
edit :
head to this link for flashing procedure and lock/ re-lock the bootloader on moto g4 plus :
https://forum.xda-developers.com/showpost.php?p=70383231&postcount=15
http://forum.xda-developers.com/mot...d-ota-nougat-ota-moto-g4-plus-t3517059/page37
Sent from my Moto G (4) using Tapatalk
Sent from my Moto G (4) using Tapatalk
zazzy24 said:
http://forum.xda-developers.com/mot...d-ota-nougat-ota-moto-g4-plus-t3517059/page37
Sent from my Moto G (4) using Tapatalk
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
this is captured ota I'm asking for updated stock rom for flashing.. thanks for your head up (Y)
snd team said:
this is captured ota I'm asking for updated stock rom for flashing.. thanks for your head up (Y)
Click to expand...
Click to collapse
It isn't released. That's already discussed.
snd team said:
Hello guyz do you have or post the latest version stock rom for Moto G4 Plus XT1643 ?
Waiting eagerly for your heads up
Click to expand...
Click to collapse
Find it here. It's flashable ROM zip:
removed link.. mod edit: not flashable..
removed link.. mod edit: not flashable..
Anyone tried this ? is it compatible with Indian (XT1643) version?
Arivendu said:
Find it here. It's flashable ROM zip:
removed link.. mod edit: not flashable..]
Click to expand...
Click to collapse
Don't misguide users. You shouldn't post if you are not sure about something.
First, its not a zip file. Its a rar file.
Second, its not flashable. You need to flash it using fastboot.
Arivendu said:
Find it here. It's flashable ROM zip:
https://cloud.mail.ru/public/CKF3/AWVREk6s9
Click to expand...
Click to collapse
Thanks buddy you're the best
praveenbda said:
Anyone tried this ? is it compatible with Indian (XT1643) version?
Click to expand...
Click to collapse
yes sure see the topic title and also tested on XT1643
also I'm able to re-lock the bootloader
TO relock the bootloader and Flashing
First of all download the stock firmware rar file ( thanks to Arivendu for heads up) - multi platform support (windows linux etc)
https://cloud.mail.ru/public/CKF3/AWVREk6s9
Mirrors :
https://files.fm/u/hfapbktm
https://drive.google.com/open?id=0B-ReAPgYg5ISNFpaeV92V2hRaWc
https://mega.nz/#!0oV33RhI!5U51UqC4v16qTSN5ur6FAV7EOpLTXL0Pfm12n71GGwc
***** this firmware also worked for other moto g4 variants *****
extract it
open folder name : athene_oem_user_7.0_NPJ25.93-11_12_release
under the folder their is a folder name "Windows"
copy files from "windows" folder to root folder
and use below command to re-lock bootloader and flash your phone with latest version of stock 7.0 (tested on xt1643)
SHIFT + Mouse right click >>> open command window here
and enter this commands one by one
Code:
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
Or download the oem unlock and flash mobile.zip (833.6 KB) from atatchment and place the files in root dir where you extracted the firmware
and run the OEM lock.bat file for automation
if the device not reboot after firmware flash run this command at the end :
Code:
fastboot reboot
I can confirm that rar contains factory images and it's working fine on my Moto G4 Plus XT1644 64GB/4Gb RAM (RETUS). Finally, running Nougat on my device.
snd team said:
no i don't have any link and i confirm it is original moto firmware
Click to expand...
Click to collapse
Thanks, I had a browse and it looks like it's from http://lenovo-forums.ru/topic/22076-moto-g⁴-plus-npj2593-11/
Although the website says they are not an official Lenovo forum, if it's working for people, that's great. It'd be nice if we get a Nougat ROM we can flash in stock recovery without adb fastboot
Massive cleaning on the thread.. Please be warry of whatever type of file you are flashing on your devices.. A little mistake will brick your devices. I hope no one will post again a non-flashable zip.. and pls. put into considerations the knowledge of others. Not everyone knows what a RAR file or a ZIP file is... Please be cautious.. AND LASTLY .. NO FLAMING ..... NEVER ALLOWED HERE
reyscott said:
Massive cleaning on the thread.. Please be warry of whatever type of file you are flashing on your devices.. A little mistake will brick your devices. I hope no one will post again a non-flashable zip.. and pls. put into considerations the knowledge of others. Not everyone knows what a RAR file or a ZIP file is... Please be cautious.. AND LASTLY .. NO FLAMING ..... NEVER ALLOWED HERE
Click to expand...
Click to collapse
thanks for cleaning cheers
Fastboot flashing steps
snd team said:
Hello guyz do you have or post the latest version stock rom for Moto G4 Plus XT1643 ?
Waiting eagerly for your heads up
edit :
head to this link for flashing procedure and lock/ re-lock the bootloader on moto g4 plus :
https://forum.xda-developers.com/showpost.php?p=70383231&postcount=15
Click to expand...
Click to collapse
Hi guys
I have an XT1643 and I have downloaded the firmware mentioned below. It was a 7z compressed file with password as "lenovo-forums.ru"
"athene_oem_user_7.0_NPJ25.93-14_16_release.7z"
I couldn't find the commands for flashing this through bootloader. If someone may know a solution, could you please post the command or guide me?
thanks
shailuo said:
Hi guys
I have an XT1643 and I have downloaded the firmware mentioned below. It was a 7z compressed file with password as "lenovo-forums.ru"
"athene_oem_user_7.0_NPJ25.93-14_16_release.7z"
I couldn't find the commands for flashing this through bootloader. If someone may know a solution, could you please post the command or guide me?
thanks
Click to expand...
Click to collapse
The fastboot commands are the same as in the post you linked in your quote. Alternatively, you may refer to the instructions listed here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
One way to flash your stock ROM is (just expanding on the instructions mentioned previously):
1) Download the Motorola drivers and minimal adb tool from the links here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 Install the drivers and tool as directed by the installers.
2)Extract the 7z ROM with your preferred decompression tool (that can handle .7z file types). The resulting folder should be about 2 GB. Copy the files (from the extracted stock ROM) to your adb folder (may be on your C:\ drive, you may have to give permission to copy).
3)Connect your device to your computer. Enable USB debugging.
3a)Once recognised by your computer, open the adb terminal and type/execute 'adb devices' without the quotes. Your device should return back its serial number if properly detected.
4)Back up all necessary data and files to your computer. Flashing a fastboot ROM may wipe your data from your device.
5)Reboot your device to bootloader mode.
5a) Re-confirm you can still detect your device in fastboot mode by executing 'fastboot devices'. Should get your serial number again.
6)Run the commands as directed in the fastboot ROM thread in the adb terminal.
6a)These commands are for relocking your bootloader:
Code:
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem lock
fastboot reboot
6b) If you don't wish to type all this, you may wish to download and run the scripts from this thread: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Ensure you copy the scripts to the adb folder, where your ROM files and the adb terminal should be. There should be 2 scripts there, one for if you want to relock your bootloader, one if you don't wish to.
getting error whilw flashing
snd team said:
First of all download the stock firmware rar file ( thanks to Arivendu for heads up) - multi platform support (windows linux etc)
https://cloud.mail.ru/public/CKF3/AWVREk6s9
Mirrors :
https://files.fm/u/hfapbktm
https://drive.google.com/open?id=0B-ReAPgYg5ISNFpaeV92V2hRaWc
https://mega.nz/#!0oV33RhI!5U51UqC4v16qTSN5ur6FAV7EOpLTXL0Pfm12n71GGwc
***** this firmware also worked for other moto g4 variants *****
extract it
open folder name : athene_oem_user_7.0_NPJ25.93-11_12_release
under the folder their is a folder name "Windows"
copy files from "windows" folder to root folder
and use below command to re-lock bootloader and flash your phone with latest version of stock 7.0 (tested on xt1643)
SHIFT + Mouse right click >>> open command window here
and enter this commands one by one
Code:
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
Or download the oem unlock and flash mobile.zip (833.6 KB) from atatchment and place the files in root dir where you extracted the firmware
and run the OEM lock.bat file for automation
if the device not reboot after firmware flash run this command at the end :
Code:
fastboot reboot
Click to expand...
Click to collapse
log:
Fastboot device is ready
There are 1 device(s) connected: ZY2237XWMH
Trying to flash device ZY2237XWMH
Starting flashing device ZY2237XWMH...
Flashing partition table ...
Executing ".\Windows\fastboot.exe -s ZY2237XWMH flash partition gpt.bin"
target max-download-size: 512MB
sending 'partition' (32 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.048s
All devices are flashed
Press any key to continue .
Iam getting same error even while flshing without bootloader and GPT. (Iam trying downgrade from 7.1.2 to stock 7.0)
please help me with this
Udaya.kr said:
log:
Fastboot device is ready
There are 1 device(s) connected: ZY2237XWMH
Trying to flash device ZY2237XWMH
Starting flashing device ZY2237XWMH...
Flashing partition table ...
Executing ".\Windows\fastboot.exe -s ZY2237XWMH flash partition gpt.bin"
target max-download-size: 512MB
sending 'partition' (32 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.048s
All devices are flashed
Press any key to continue .
please help me with this
Click to expand...
Click to collapse
What firmware did you have previously on your device, and are you trying to relock your bootloader? The firmware linked here is quite old (November 2016 security patch), and the warning you're getting suggests you have newer firmware on your device.
If you're on the June update, do not flash this firmware.
echo92 said:
What firmware did you have previously on your device, and are you trying to relock your bootloader? The firmware linked here is quite old (November 2016 security patch), and the warning you're getting suggests you have newer firmware on your device.
If you're on the June update, do not flash this firmware.
Click to expand...
Click to collapse
Successfully flashed june firmware and re locked bootloader. thank you for your help.
Udaya.kr said:
Successfully flashed june firmware and re locked bootloader. thank you for your help.
Click to expand...
Click to collapse
Can you please share the link for june fastboot rom for XT1643?
My XT1625 has an unlocked bootloader and TWRP installed. Today I got a notification that the Sept security patch was available so I downloaded it and tried to install. I was paying attention until I noticed it booted back into TWRP and does it everytime so I guess accepting and installing that patch was a no-no. I got it to boot into Android from instructions in another post.
Can I locate the patch in TWRP and flash it from there? Btw, I did notice that the patch was only 49MB so it clearly wasn't the entire Nougat ROM.
lmacmil said:
My XT1625 has an unlocked bootloader and TWRP installed. Today I got a notification that the Sept security patch was available so I downloaded it and tried to install. I was paying attention until I noticed it booted back into TWRP and does it everytime so I guess accepting and installing that patch was a no-no. I got it to boot into Android from instructions in another post.
Can I locate the patch in TWRP and flash it from there? Btw, I did notice that the patch was only 49MB so it clearly wasn't the entire Nougat ROM.
Click to expand...
Click to collapse
You cannot flash an official OTA update. You need to be on official recovery for this. Have a look at here, same question https://forum.xda-developers.com/moto-g4-plus/help/luck-moto-g4-plus-flashable-logo-bin-t3701652
For update its advisable to use the full stock rom to be flashed with fastboot like this one https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Please use always search function as this happens every week a few times and same question is answered already enough.
Also worth having a look here https://forum.xda-developers.com/moto-g4-plus/help/help-thread-question-noob-friendly-t3526598 and also ask here.
strongst said:
You cannot flash an official OTA update. You need to be on official recovery for this. Have a look at here, same question https://forum.xda-developers.com/moto-g4-plus/help/luck-moto-g4-plus-flashable-logo-bin-t3701652
I saw that other post and edited mine to acknowledge that I saw the fix (see last sentence of 1st paragraph.)
For update its advisable to use the full stock rom to be flashed with fastboot like this one https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Thanks. I probably won't go to that much trouble.
Please use always search function as this happens every week a few times and same question is answered already enough. I generally do.
Also worth having a look here https://forum.xda-developers.com/moto-g4-plus/help/help-thread-question-noob-friendly-t3526598 and also ask here.
Click to expand...
Click to collapse
I rebooted and it went back to TWRP again. I will ask how to fix this in the help thread.
lmacmil said:
I rebooted and it went back to TWRP again. Will I have to boot to fastboot mode and select factory mode every time now or is there a fix that will boot into Android instead of TWRP?
Click to expand...
Click to collapse
Try to run these commands from fastboot..
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
____Mdd said:
Try to run these commands from fastboot..
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
I will give it a try.
lmacmil said:
I will give it a try.
Click to expand...
Click to collapse
use the following script :
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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
____Mdd said:
Try to run these commands from fastboot..
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Got error messages:
D:\Computer\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.005s]
finished. total time: 0.008s
siddhesh9146 said:
use the following script :
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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Is this going to wipe my system like a factory reset? If so, can I just restore the backup I made after I installed TWRP initially? Or just do a factory reset?
@lmacmil ignore it, use both commands then try to boot.
---------- Post added at 12:41 AM ---------- Previous post was at 12:34 AM ----------
lmacmil said:
Is this going to wipe my system like a factory reset? If so, can I just restore the backup I made after I installed TWRP initially? Or just do a factory reset?
Click to expand...
Click to collapse
Don't use it if you are thinking to just run script and not to flash... since it has "erase modemst1 & 2" it will erase modem, but will not flash fsg/modem, also "erase data" will wipe everything on phone.. this can put you in trouble..
Instead of doing this, as strongst said in his post, flash complete firmware, see the link for september's update he gave in his post.
Then move everything from your phone to PC (images / video/ etc)
Then flash firmware...
____Mdd said:
@lmacmil ignore it, use both commands then try to boot.
---------- Post added at 12:41 AM ---------- Previous post was at 12:34 AM ----------
Don't use it if you are thinking to just run script and not to flash... since it has "erase modemst1 & 2" it will erase modem, but will not flash fsg/modem, also "erase data" will wipe everything on phone.. this can put you in trouble..
Instead of doing this, as strongst said in his post, flash complete firmware, see the link for september's update he gave in his post.
Then move everything from your phone to PC (images / video/ etc)
Then flash firmware...
Click to expand...
Click to collapse
Still boots to TWRP. Maybe this is the time to move to LineageOS 14.1. I was going to wait until 15 was stable but if I'm going to lose everything, I might as well get more up to date.
This seems to have killed my cell signal too. Just noticed that last time I booted to Android.
lmacmil said:
Still boots to TWRP. Maybe this is the time to move to LineageOS 14.1. I was going to wait until 15 was stable but if I'm going to lose everything, I might as well get more up to date.
This seems to have killed my cell signal too. Just noticed that last time I booted to Android.
Click to expand...
Click to collapse
Did you flash complete stock ROM ?
Move your files to External Storage then try it.
____Mdd said:
Did you flash complete stock ROM ?
Move your files to External Storage then try it.
Click to expand...
Click to collapse
I decided since I would have to reinstall all my apps anyway that I would flash LineageOS 14.1, which I did. I did the appropriate wipes (data, system, cache, Dalvik/ART), then flashed the latest nightly and Gapps. It was successful but it's still booting into TWRP and I still have no cell service. I thought that a complete wipe and installation of new ROM would correct those issues but it did not. And since it didn't, I'm not confident that flashing the stock ROM would either but unless there's something else to try, I will do it. One concern I have is I have a plain G4 and the ROM is for the G4 Plus. My build was NPJ25.93-14.5 and I think the Plus build is NPJS... Not sure if that makes a difference.
Maybe I should restore my original Nandroid backup first and see if that fixes things.
lmacmil said:
. My build was NPJ25.93-14.5 and I think the Plus build is NPJS... Not sure if that makes a difference.
Click to expand...
Click to collapse
NPJ25.93-14.5 was for Amazon variant if i am not wrong.
I don't know but in past that two commands [fb_mode_set and fb_mode_clear] worked fine for this problem.
Try this thing, [reboot to bootloader and flash TWRP but with fb_mode_ commands]
- fastboot oem fb_mode_set
- fastboot flash recovery twrp(name).img
- fastboot oem fb_mode_clear
If this too doesn't work, then you have to find correct firmware for your phone and flash it..
EDIT: for easiness to find correct firmware, restore backup, then see "about phone" for build number, it will help to find firmware..
EDIT-2:
I found 2 firmware of version you said,
But one says Amazon and another doesn't. You have Nandroid, restore and check your phone build..
Then go for following one correctly..
AMAZON : Click here
Non-AMAZON : Click here
____Mdd said:
NPJ25.93-14.5 was for Amazon variant if i am not wrong.
I don't know but in past that two commands [fb_mode_set and fb_mode_clear] worked fine for this problem.
Try this thing, [reboot to bootloader and flash TWRP but with fb_mode_ commands]
- fastboot oem fb_mode_set
- fastboot flash recovery twrp(name).img
- fastboot oem fb_mode_clear
If this too doesn't work, then you have to find correct firmware for your phone and flash it..
EDIT: for easiness to find correct firmware, restore backup, then see "about phone" for build number, it will help to find firmware..
EDIT-2:
I found 2 firmware of version you said,
But one says Amazon and another doesn't. You have Nandroid, restore and check your phone build..
Then go for following one correctly..
AMAZON : Click here
Non-AMAZON : Click here
Click to expand...
Click to collapse
Mine was the non-Amazon version. See attachment. The software channel was "retus" and the baseband version also said "ATHENE_RETUSA_CUST" The Amazon version software channel is amz.
I was able to get the bootloader unlock code from Motorola and they don't allow the Amazon versions to be unlocked.
I'll try your suggestions. Thanks for your continued help.
____Mdd said:
NPJ25.93-14.5 was for Amazon variant if i am not wrong.
I don't know but in past that two commands [fb_mode_set and fb_mode_clear] worked fine for this problem.
Try this thing, [reboot to bootloader and flash TWRP but with fb_mode_ commands]
- fastboot oem fb_mode_set
- fastboot flash recovery twrp(name).img
- fastboot oem fb_mode_clear
Click to expand...
Click to collapse
This is what I got:
D:\Computer\Minimal ADB and Fastboot>fastboot devices
ZY223N5GLF fastboot
D:\Computer\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ -0.000s]
finished. total time: -0.000s
D:\Computer\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12530 KB)...
OKAY [ 0.402s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.190s]
finished. total time: 0.595s
D:\Computer\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.001s]
finished. total time: 0.001s
=================================
Not sure why I'm getting the bootloader error messages but I backed up just the bootloader recently so am going to restore that and see what happens.
@lmacmil that "not found" is ignorable, just check you get "OKAY" after one command ends... Since GPT and Bootloader commands got "OKAY" they are flashed successfully..... Go for complete firmware...
____Mdd said:
@lmacmil that "not found" is ignorable, just check you get "OKAY" after one command ends... Since GPT and Bootloader commands got "OKAY" they are flashed successfully..... Go for complete firmware...
Click to expand...
Click to collapse
I guess I need to bite the bullet and do this. It will install stock recovery and erase TWRP, right? If that's the case, and I don't relock the bootloader, will I be able to accept the OTA update? Or does an unlocked bootloader prevent OTA updates?
Last question: I just extract the firmware .zip file to the same folder where fastboot and adb reside? Then type the commands one by one (or copy/paste from the script shown in the thread about flashing stock firmware.)
Thanks again.
lmacmil said:
I guess I need to bite the bullet and do this. It will install stock recovery and erase TWRP, right?
Click to expand...
Click to collapse
Yes, it will install stock recovery, you will have to install TWRP again.
If that's the case, and I don't relock the bootloader, will I be able to accept the OTA update? Or does an unlocked bootloader prevent OTA updates?
Click to expand...
Click to collapse
It will be fine, You will have successful installation with unlocked bootloader too, no need to lock back..
Last question: I just extract the firmware .zip file to the same folder where fastboot and adb reside? Then type the commands one by one (or copy/paste from the script shown in the thread about flashing stock firmware.)
Thanks again.
Click to expand...
Click to collapse
You did right, that's why there is "OKAY" when command end, see your own post where you asked for "not found" error... Keep Going..
____Mdd said:
Yes, it will install stock recovery, you will have to install TWRP again.
You did right, that's why there is "OKAY" when command end, see your own post where you asked for "not found" error... Keep Going..
Click to expand...
Click to collapse
Success! Just flashed the stock Nougat ROM and as soon as it booted up, I let it download and install the Sept security patch. I am now on NPJ25.93-14.7.
Thanks again for all your help.
Lee
I reloaded my G5 Plus with POTTER_RETAIL_7.0_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip sucessfuly. However, I was not able to relock the bootloader :
C:\Moto potter>fastboot oem lock
...
(bootloader) Still require signed boot.img
It got OTA'ed to Oreo 8.1 latter on, but still bootloader unlocked. That's weird, I thought a phone with open bootloader would not receive OTA, but mine does.
I just went through the flashing process to POTTER_RETAIL_8.1.0_OPSS28.85-17-4, same damn thing.
Everything works fine, except for Netflix that can't be installed no longer and my bank software who keeps complaining.
C:\MinimalADBFastboot>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.052s]
writing 'logo'...
OKAY [ 0.099s]
finished. total time: 0.161s
C:\MinimalADBFastboot>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.397s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.285s]
finished. total time: 0.689s
C:\MinimalADBFastboot>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.491s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.364s]
finished. total time: 0.861s
I just dunno what to do to relock, any advice ?
CanadianGixxerman said:
I reloaded my G5 Plus with POTTER_RETAIL_7.0_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip sucessfuly. However, I was not able to relock the bootloader :
C:\Moto potter>fastboot oem lock
...
(bootloader) Still require signed boot.img
It got OTA'ed to Oreo 8.1 latter on, but still bootloader unlocked. That's weird, I thought a phone with open bootloader would not receive OTA, but mine does.
I just went through the flashing process to POTTER_RETAIL_8.1.0_OPSS28.85-17-4, same damn thing.
Everything works fine, except for Netflix that can't be installed no longer and my bank software who keeps complaining.
C:\MinimalADBFastboot>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.052s]
writing 'logo'...
OKAY [ 0.099s]
finished. total time: 0.161s
C:\MinimalADBFastboot>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.397s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.285s]
finished. total time: 0.689s
C:\MinimalADBFastboot>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.491s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.364s]
finished. total time: 0.861s
I just dunno what to do to relock, any advice ?
Click to expand...
Click to collapse
An unlocked bootloader has nothing to do with getting OTA updates. At least you get the unlock code from the manufacturer himself.
Only changes in /system or /vendor like rooting or other tweaks make OTA fail.
About locking the BL, a bit of research would have taken you here: https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
For Oreo the whole sets of commands are for
Locking:
-----------------
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 boot boot.img
fastboot oem lock
-------------------
Flashing:
-------------------
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 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
--------------------
Edited because of wrong number of sparechunk files for Oreo firmwares.
@Wolfcity
Unlike you supposed, I just did not throw my problem in the forum and waited for someone else to hand me a solution on a silver plate. I did do my homeworks, I did *MANY* searches, I did see the post you pointed me toward, that one and many many others that resembled it closely. But this whole endeavour did not lead me to my expected objective, which is to relock my phone. I am in the same loop I was in when I started trying : The second time I issue the «fastboot oem lock» command, I get this :
C:\Moto potter>fastboot.exe oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.003s]
finished. total time: 0.003s
And the BL does not lock.
CanadianGixxerman said:
@Wolfcity
Unlike you supposed, I just did not throw my problem in the forum and waited for someone else to hand me a solution on a silver plate. I did do my homeworks, I did *MANY* searches, I did see the post you pointed me toward, that one and many many others that resembled it closely. But this whole endeavour did not lead me to my expected objective, which is to relock my phone. I am in the same loop I was in when I started trying : The second time I issue the «fastboot oem lock» command, I get this :
C:\Moto potter>fastboot.exe oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.003s]
finished. total time: 0.003s
And the BL does not lock.
Click to expand...
Click to collapse
You can get signed images from Lenovo Moto smart assistant app, just go for rescue and let the firmware gets download, then go to the c/LMSA/ROM there you can find the firmware which has signed, use that image for locking bootloader, then you can lock your bootloader.and don't get anger on wolfcity he just try to help you as, some person don't know how to lock bootloader so they just post on XDA without reading the other thread only.
CanadianGixxerman said:
@Wolfcity
Unlike you supposed, I just did not throw my problem in the forum and waited for someone else to hand me a solution on a silver plate. I did do my homeworks, I did *MANY* searches, I did see the post you pointed me toward, that one and many many others that resembled it closely. But this whole endeavour did not lead me to my expected objective, which is to relock my phone. I am in the same loop I was in when I started trying : The second time I issue the «fastboot oem lock» command, I get this :
C:\Moto potter>fastboot.exe oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.003s]
finished. total time: 0.003s
And the BL does not lock.
Click to expand...
Click to collapse
I don't wanted to sound rude or something like that.
You didn't mention that you used all the fastboot locking commands in you first post, you just posted three lines of flashing boot, recovery and logo.
So no offense.
What sounds strange to me is that Netflix and your banking app aren't working with an unlocked bootloader. Normally these applications are looking for traces of rooting methods like magisk or SuperSU. I'm unlocked and rooted with magisk and Netflix is working for me if I put in on magisk's hide list. Maybe you have some files on your device that trigger these anti rooting mechanisms? Sometimes just a file or folder named magisk could be enough.
Wolfcity said:
I don't wanted to sound rude or something like that.
You didn't mention that you used all the fastboot locking commands in you first post, you just posted three lines of flashing boot, recovery and logo.
So no offense.
What sounds strange to me is that Netflix and your banking app aren't working with an unlocked bootloader. Normally these applications are looking for traces of rooting methods like magisk or SuperSU. I'm unlocked and rooted with magisk and Netflix is working for me if I put in on magisk's hide list. Maybe you have some files on your device that trigger these anti rooting mechanisms? Sometimes just a file or folder named magisk could be enough.
Click to expand...
Click to collapse
No hard feelings.
It turns out that with your instructions (1st part : Locking) I was sucessful at my aim, finally. It did whine again about the signed image requirement after line 2, I continued [9 sparsechunks though, not 5 ... ], then, upon hitting «enter» after the last line [fastboot oem lock], Shazam, it locked.
You may be right about some left over garbage files [or traces of] that could still be present in the file system. I have loaded many customs roms last year on this phone, magisk and SuperSu as well.
Last but not least : Thank you.
CanadianGixxerman said:
No hard feelings.
It turns out that with your instructions (1st part : Locking) I was sucessful at my aim, finally. It did whine again about the signed image requirement after line 2, I continued [9 sparsechunks though, not 5 ... ], then, upon hitting «enter» after the last line [fastboot oem lock], Shazam, it locked.
You may be right about some left over garbage files [or traces of] that could still be present in the file system. I have loaded many customs roms last year on this phone, magisk and SuperSu as well.
Last but not least : Thank you.
Click to expand...
Click to collapse
Good to hear it worked out for you at last.
Seems that these "unsigned" messages are nothing to worry about to much. Sorry for the "sparechunk thing", copied the wrong flashall.bat file, this is the one for Oreo :https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
with 8 sparechunk files.
Last but not least: You're welcome.
Yeah this same thing happened to me today morning.. most guides have till sparsechunk4.. where as oreo has uptill 8.. so u need to flash the rest i.e 5,6,7,8. And then it will lock..
Wolfcity said:
Good to hear it worked out for you at last.
Seems that these "unsigned" messages are nothing to worry about to much. Sorry for the "sparechunk thing", copied the wrong flashall.bat file, this is the one for Oreo :https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
with 8 sparechunk files.
Last but not least: You're welcome.
Click to expand...
Click to collapse
I also had same error. Followed what you said. Finally locked bootloader. I am very happy now.
Thank you.
Might be good for someone who has gone through it, to make a new write-up, with current info. The longer these phones have been out, and bootloader unlocked, the more fragmented the info gets. It gets harder to know what currently works, and what could possibly "fubar" the phone.
[email protected] said:
Might be good for someone who has gone through it, to make a new write-up, with current info. The longer these phones have been out, and bootloader unlocked, the more fragmented the info gets. It gets harder to know what currently works, and what could possibly "fubar" the phone.
Click to expand...
Click to collapse
What do you mean? An "locking BL guide" or something more complete like "flashing/locking/encrypting/rooting"? I'm willing to that but I have to know what you guys need.
Wolfcity said:
What do you mean? An "locking BL guide" or something more complete like "flashing/locking/encrypting/rooting"? I'm willing to that but I have to know what you guys need.
Click to expand...
Click to collapse
Sure,,,, all of it! I unlocked my first G5 plus a year and a half ago. I have hard bricked it 3 times, and now use it for a test phone, as it has an addison bootloader. My everyday G5 plus is unlocked and rooted, but I've kept it on stock roms and kernels, due to a little fear of how easily these can be corrupted. I am certainly not ignorant of most of the workings with these, even going so far as to use Qualcomm's factory utilities to dig deep inside. However, that being said, what worked when I first unlocked my original, isn't totally pertinent today. Nougat and Oreo factory roms, nougat, oreo, pie developer roms, 64 bit and 32 bit, all add to a confusing set list of what can be safely done without irreversible consequences. I've kept up on these forums for almost 2 years, but the fragmentation of guides makes it confusing enough for myself, much less a novice. Example of things that can go wrong to unsuspecting, is the loss of touchscreen with stock oreo. I haven't experienced it, but it is out there. I'm just saying it would be hugely beneficial for all, if we could get some current guides, stickied in place of our outdated ones. I have the test phone that I have put through the wringer, and am more than willing to use it as a guinea pig for any other processes that may add to the guides.
[email protected] said:
Sure,,,, all of it! I unlocked my first G5 plus a year and a half ago. I have hard bricked it 3 times, and now use it for a test phone, as it has an addison bootloader. My everyday G5 plus is unlocked and rooted, but I've kept it on stock roms and kernels, due to a little fear of how easily these can be corrupted. I am certainly not ignorant of most of the workings with these, even going so far as to use Qualcomm's factory utilities to dig deep inside. However, that being said, what worked when I first unlocked my original, isn't totally pertinent today. Nougat and Oreo factory roms, nougat, oreo, pie developer roms, 64 bit and 32 bit, all add to a confusing set list of what can be safely done without irreversible consequences. I've kept up on these forums for almost 2 years, but the fragmentation of guides makes it confusing enough for myself, much less a novice. Example of things that can go wrong to unsuspecting, is the loss of touchscreen with stock oreo. I haven't experienced it, but it is out there. I'm just saying it would be hugely beneficial for all, if we could get some current guides, stickied in place of our outdated ones. I have the test phone that I have put through the wringer, and am more than willing to use it as a guinea pig for any other processes that may add to the guides.
Click to expand...
Click to collapse
You're lucky you have the ability to financially purchase a second G5 Plus to use as a failsafe. When I purchased mine it was roughly around $300-400 (was brand new) so to have purchased another at the time wasn't an option, and may as well purchase a 700+ flagship with that money. To this day I've owned over 30 devices and tested well over that. Thus far only the Galaxy S2 and the Motorola G5 Plus were the only two that have surpassed a year with good stable service. I don't even purchase the phone cases cause devices are supposed to be visually appealing like cars, because tech will always be sexxy. Anyways, my point was since the Photon Q back in early 2014 to this G5 Plus, I've really liked Motorola. If you take the time the align this phone purrs. But I need to upgrade soon as.. Thinking of getting a Pixel 3 when it reaches my shores.. Anyways, it's 1:28am, goodnight.
I was able to purchase the second phone for less than $100 US, slightly used. So it was a no brainer to have a guinea pig phone.
Wolfcity said:
An unlocked bootloader has nothing to do with getting OTA updates. At least you get the unlock code from the manufacturer himself.
Only changes in /system or /vendor like rooting or other tweaks make OTA fail.
About locking the BL, a bit of research would have taken you here: https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
For Oreo the whole sets of commands are for
Locking:
-----------------
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 boot boot.img
fastboot oem lock
-------------------
Flashing:
-------------------
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 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
--------------------
Edited because of wrong number of sparechunk files for Oreo firmwares.
Click to expand...
Click to collapse
Hi!!
I need to relock my Moto G5 Plus, because my country use a Covid App to transit trough states.
And I need it to use because I´m a essential worker. This App check the locked / unlocked devices.
I Know that Netlix do the same, but it never mattered to me to that app.
Now I really need to Re Locked my phone
I have tried several methods.. and doesn´t work any of them
Mr.BUBU said:
Hi!!
I need to relock my Moto G5 Plus, because my country use a Covid App to transit trough states.
And I need it to use because I´m a essential worker. This App check the locked / unlocked devices.
I Know that Netlix do the same, but it never mattered to me to that app.
Now I really need to Re Locked my phone
I have tried several methods.. and doesn´t work any of them
Click to expand...
Click to collapse
You can orientate yourself by this guide but as the one is for Nougat you need to correct the number of the sparechunk files:
How to re-lock Bootloader of all Potter version
Hi guys, finally I succed in relock my XT1685 Bootloader on RETEU, so I will guide you to relock your bootloader. DISCLAIMER: I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm...
forum.xda-developers.com
So the first set of commands should be:
First set:
Lock.
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 boot boot.img
fastboot oem lock
Second set:
Flashing firmware.
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 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Device is now full stock with locked bootloader.
For the second set of commands you can use a flashall.bat file like this:
Dropbox - File Deleted - Simplify your life
www.dropbox.com
It may look like the first set would be enough but that's not true, you have to flash the whole firmware afterwards.
Be aware that all of your internal data (apps, settings and everything you have in internal storage) will be erased so make backups of everything. Also backup all partitions with TWRP especially persist and efs!
This tutorial may help you to find the correct firmware for your device (links available) and also guide you through the flashing process of the whole firmware;
[GUIDE] Moto G5 Plus: Flashing Stock Firmware & Rooting [2021]
Flashing signed stock firmware: You need: Latest signed stock firmware: Europe (RETEU): https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/potter/official/RETEU/ India (RETIN)...
forum.xda-developers.com
Maybe use also the tools and drivers from there.
Wolfcity said:
You can orientate yourself by this guide but as the one is for Nougat you need to correct the number of the sparechunk files:
How to re-lock Bootloader of all Potter version
Hi guys, finally I succed in relock my XT1685 Bootloader on RETEU, so I will guide you to relock your bootloader. DISCLAIMER: I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm...
forum.xda-developers.com
So the first set of commands should be:
First set:
Lock.
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 boot boot.img
fastboot oem lock
Second set:
Flashing firmware.
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 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Device is now full stock with locked bootloader.
For the second set of commands you can use a flashall.bat file like this:
Dropbox - File Deleted - Simplify your life
www.dropbox.com
It may look like the first set would be enough but that's not true, you have to flash the whole firmware afterwards.
Be aware that all of your internal data (apps, settings and everything you have in internal storage) will be erased so make backups of everything. Also backup all partitions with TWRP especially persist and efs!
This tutorial may help you to find the correct firmware for your device (links available) and also guide you through the flashing process of the whole firmware;
[GUIDE] Moto G5 Plus: Flashing Stock Firmware & Rooting [2021]
Flashing signed stock firmware: You need: Latest signed stock firmware: Europe (RETEU): https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/potter/official/RETEU/ India (RETIN)...
forum.xda-developers.com
Maybe use also the tools and drivers from there.
Click to expand...
Click to collapse
Wait so I have to run the bootloader lock first and then flash the firmware for my Motorola one p30 play as well?
smartasiankid said:
Wait so I have to run the bootloader lock first and then flash the firmware for my Motorola one p30 play as well?
Click to expand...
Click to collapse
No, the user who was asking wanted to lock his BL so I gave him the lock commands too.
I don't know anything about your device but normally the BL has to be unlocked to flash firmware on a Moto.
Wolfcity said:
No, the user who was asking wanted to lock his BL so I gave him the lock commands too.
I don't know anything about your device but normally the BL has to be unlocked to flash firmware on a Moto.
Click to expand...
Click to collapse
Oh okay. I tried relocking the bootloader on Moto one p30 play but when repeatedly entering 'fastboot oem lock' it says "still require signed boot.img" and even after I flash the boot.img when it asks to whenever I enter the fastboot oem lock command it says "still require signed boot.img"
Can you help me out please?
This guide will only work up to OOS 11.
This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with a fastboot capable of executing fastboot reboot fastbootd.
To start, download the appropriate Oxygen OS zip for your device from the OP8T repo thread. Extracting the zip file should give you a file named
payload.bin.
Use payload dumper to extract payload.bin.
You can grab payload_dumper from here (Windows and macOS), here (linux), or here (github, any OS).
For the download link from github, make sure you're running python 3.6 or higher. Run payload dumper with:
python payload_dumper.py payload.bin
The image files will be extracted to a folder named output.
Before starting the flashing process, you can check your device memory type using the DevCheck app by flar2 or with the command adb shell getprop ro.boot.ddr_type. The adb command will return 0 for LPDDR4X chips and 1 for LPDDR5 chips. This is important to flash the right xbl img files. LPDDR4X is more common for OP8T, so no worries if you miss this step.
You can start flashing from the standard bootloader or fastbootd. The first three lines below will flash the stock recovery then reboot into fastbootd.
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot
fastboot flash --slot=all recovery recovery.img
fastboot flash --slot=all boot boot.img
fastboot flash --slot=all dtbo dtbo.img
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all logo logo.img
fastboot flash --slot=all mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all multiimgoem multiimgoem.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all spunvm spunvm.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
If your phone has the LPDDR4X memory chip (returned 0 with the adb shell command above), flash the images below:
Code:
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img
LPDDR4X is the more common chip for OP8T, so if you forgot to check, you can flash this.
If your phone has the LPDDR5 chip (returned 1 with the adb shell command above), flash the images below:
Code:
fastboot flash --slot=all xbl_config xbl_config_lp5.img
fastboot flash --slot=all xbl xbl_lp5.img
This next section will clear the super partition (contains odm, system, system_ext, vendor and product). It's not absolutely necessary, so you can skip to the next step. Clearing the super partition will help avoid the following error, which can come up if you had manually flashed ROMs on both slots previously.
Code:
Resizing '<partition name>' FAILED (remote: 'Not enough space to resize partition')
Example: Resizing 'product' FAILED (remote: 'Not enough space to resize partition')
If you've ever had this error or you just want to be sure that everything is cleared, check the spoiler.
Spoiler
Before deleting, you can check the names of the logical partitions on your phone using fastboot getvar all. Scroll up to the section that looks like this:
Code:
(bootloader) is-logical:odm_a:yes
(bootloader) is-logical:product_a:yes
(bootloader) is-logical:system_a:yes
(bootloader) is-logical:system_ext_a:yes
(bootloader) is-logical:vendor_a:yes
or
(bootloader) is-logical:odm_b:yes
(bootloader) is-logical:product_b:yes
(bootloader) is-logical:system_b:yes
(bootloader) is-logical:system_ext_b:yes
(bootloader) is-logical:vendor_b:yes
As @Matt85m pointed out, you may also have:
Code:
(bootloader) is-logical:odm:yes
(bootloader) is-logical:product:yes
(bootloader) is-logical:system:yes
(bootloader) is-logical:system_ext:yes
(bootloader) is-logical:vendor:yes
It is also possible to have logical partitions with the same names ending in -cow (system_a-cow, system_b-cow, system_ext_b-cow, vendor_a-cow, product_b-cow, etc).
These are created by various ROMs during an OTA. Shout out to @mslezak for the discovery.
Delete everything with the commands below:
Code:
fastboot delete-logical-partition odm
fastboot delete-logical-partition system
fastboot delete-logical-partition system_ext
fastboot delete-logical-partition product
fastboot delete-logical-partition vendor
fastboot delete-logical-partition odm_a
fastboot delete-logical-partition odm_b
fastboot delete-logical-partition system_a
fastboot delete-logical-partition system_b
fastboot delete-logical-partition system_ext_a
fastboot delete-logical-partition system_ext_b
fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
fastboot delete-logical-partition vendor_a
fastboot delete-logical-partition vendor_b
Delete any -cow partitions with the same command:
Code:
fastboot delete-logical-partition system_a-cow
and so on.
If you get an error deleting the -cow partitions, @firegate22 suggests changing slots from the bootloader (fastboot --set-active=a or b) not from fastbootd, then return to fastbootd and try the delete command again.
All logical partitions can be deleted to free up space in the super partition.
Recreate partitions a and b with the commands below.
Code:
fastboot create-logical-partition odm_a 100000
fastboot create-logical-partition odm_b 100000
fastboot create-logical-partition system_a 100000
fastboot create-logical-partition system_b 100000
fastboot create-logical-partition system_ext_a 100000
fastboot create-logical-partition system_ext_b 100000
fastboot create-logical-partition product_a 100000
fastboot create-logical-partition product_b 100000
fastboot create-logical-partition vendor_a 100000
fastboot create-logical-partition vendor_b 100000
Flash the rest of the images.
Code:
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash vendor vendor.img
fastboot flash --slot=all vbmeta vbmeta.img
fastboot flash --slot=all vbmeta_system vbmeta_system.img
Assuming everything flashes with no errors, return to recovery, do a factory reset and reboot.
I like what you're proposing. I've been thinking along these lines also.
Would you mind explaining why you're flashing to both slots rather than just the inactive one?
If you leave the current slot untouched you have a fallback position (the whole point of having A/B partitioning).
The same question applies to the flashing/deleting of the dynamic partitions in super.
BillGoss said:
I like what you're proposing. I've been thinking along these lines also.
Would you mind explaining why you're flashing to both slots rather than just the inactive one?
If you leave the current slot untouched you have a fallback position (the whole point of having A/B partitioning).
The same question applies to the flashing/deleting of the dynamic partitions in super.
Click to expand...
Click to collapse
For this guide specifically, the idea is to return as close to stock as possible. Wiping everything and replacing with OOS would be the best way to do that.
More generally, other than boot.img and recovery.img, the images flashed on both slots in the first part are the firmware files. You can grab and flash them from pretty much any new OOS version to update the firmware without affecting the installed ROMs. The specific files for the ROM are all in the third part. If you extract the payload.bin for any custom ROM, those are usually the only image files included.
You can certainly run two different firmware versions on the two slots, but if the inactive slots are empty or contain much older firmware, you can end up with weird issues in the active slots (usually a boot loop but could be more or less serious). Keeping the versions close is just to avoid unnecessary issues.
Some custom ROMs for OP8T like Lineage recommend or insist on flashing the copy-partitions.zip package for this reason. It's also why the install instructions for older A/B phones that have TWRP generally begin with "flash the stock ROM on both slots" - only the firmware files are strictly necessary, so you can keep the fallback ROM on the other slot if you want to.
That ended up much longer than planned. Hope it answers your questions though!
I'm going through this process rn, and I figured I'd ask here. How long does it usually take to flash dsp? It's been over 20 minutes of Sending 'dsp_a' (65536 KB)
65 M looks pretty big, and that's maybe the max size? How long did it take for you?
edit: seems to be unrelated to size as the modem part went fine, and that's bigger
No go, next step : fastboot reboot fastboot enter QDLoader mode
nero075 said:
I'm going through this process rn, and I figured I'd ask here. How long does it usually take to flash dsp? It's been over 20 minutes of Sending 'dsp_a' (65536 KB)
65 M looks pretty big, and that's maybe the max size? How long did it take for you?
edit: seems to be unrelated to size as the modem part went fine, and that's bigger
Click to expand...
Click to collapse
Did you figure this out? Flashing dsp should only take a couple seconds.
coomac said:
Did you figure this out? Flashing dsp should only take a couple seconds.
Click to expand...
Click to collapse
I ended up just skipping that one, and it turned out fine ¯\_(ツ)_/¯
Full time Linux user here, glad to see this guide after few days looking for a way to go back to stock without Msmtool.
However I do have some question, is it possible to have a OTA update from Oneplus if I go back to stock using this method and re-lock my bootloader?
mrhieu059 said:
Full time Linux user here, glad to see this guide after few days looking for a way to go back to stock without Msmtool.
However I do have some question, is it possible to have a OTA update from Oneplus if I go back to stock using this method and re-lock my bootloader?
Click to expand...
Click to collapse
Shouldn't be a problem. I was able to install an OTA update after returning to stock using this method with no issues even without relocking my bootloader.
thanks for this helped me alot to restore my device, i have one question though i checked all the commands and i see there might be one command missing, when i extracted the rom i checked all the img files and saw :
xbl_lp5.img
xbl_config_lp5.img
cant help wonder if i have to input the commands as well
rdlr19 said:
thanks for this helped me alot to restore my device, i have one question though i checked all the commands and i see there might be one command missing, when i extracted the rom i checked all the img files and saw :
xbl_lp5.img
xbl_config_lp5.img
cant help wonder if i have to input the commands as well
Click to expand...
Click to collapse
Glad it helped. Those files depend on whether your device has a DDR type 0 (LPDDR4X) or DDR type 1 (LPDDR5) memory chip.
You can check your device memory type with adb shell getprop ro.boot.ddr_type. It will return 0 or 1. You can also use the DevCheck app by flar2.
I believe most OP8Ts use DDR0, which requires xbl_config.img and xbl.img. The lp5 images are for DDR1.
According to the lineage OS wiki, you'd flash the lp5 images with the same commands on DDR1:
Code:
fastboot flash --slot=all xbl_config xbl_config_lp5.img
fastboot flash --slot=all xbl xbl_lp5.img
I've tried to bring my KB2003 back to stock from LineageOS using this guide and when it comes to flashing the odm, product and vendor files I get the following errors
Code:
Sending 'odm' (34544 KB) OKAY [ 0.849s]
Writing 'odm' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Invalid sparse file format at header magic
Resizing 'product_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Resizing 'vendor_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
I've cleared the logical partitions. any ideas? Ignoring these errors and the device doesnt boot, just get a black screen
edit: if I do these product and vendor files first, system throws the error. Are the posted logical partition sizes correct?
Matt85m said:
I've tried to bring my KB2003 back to stock from LineageOS using this guide and when it comes to flashing the odm, product and vendor files I get the following errors
Code:
Sending 'odm' (34544 KB) OKAY [ 0.849s]
Writing 'odm' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Invalid sparse file format at header magic
Resizing 'product_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Resizing 'vendor_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
I've cleared the logical partitions. any ideas? Ignoring these errors and the device doesnt boot, just get a black screen
edit: if I do these product and vendor files first, system throws the error. Are the posted logical partition sizes correct?
Click to expand...
Click to collapse
You need to clear more space in the super partition. You can basically delete and recreate both slots a and b for system, system_ext, product, vendor, and probably even odm to get more space.
coomac said:
You need to clear more space in the super partition. You can basically delete and recreate both slots a and b for system, system_ext, product, vendor, and probably even odm to get more space.
Click to expand...
Click to collapse
is't that was the
Code:
fastboot delete-logical-partition
fastboot create-logical-partition
commands were about? I've followed that step as you laid out. I've now tried it by adding a line for deleting and recreating the odm partition and still no joy
Matt85m said:
is't that was the
Code:
fastboot delete-logical-partition
fastboot create-logical-partition
commands were about? I've followed that step as you laid out. I've now tried it by adding a line for deleting and recreating the odm partition and still no joy
Click to expand...
Click to collapse
Yeah, that's what they're for. Strange. Any other errors before the one for odm? Would be helpful if you can upload a screenshot of your terminal with all the commands.
Edit: One suggestion is to make sure you're in fastbootd, not fastboot. Also, the size for the new logical partitions is arbitrary - they get resized when being flashed.
coomac said:
Yeah, that's what they're for. Strange. Any other errors before the one for odm? Would be helpful if you can upload a screenshot of your terminal with all the commands.
Edit: One suggestion is to make sure you're in fastbootd, not fastboot. Also, the size for the new logical partitions is arbitrary - they get resized when being flashed.
Click to expand...
Click to collapse
it definitely is in fastbootd, I ran into that issue initially as the android-tools package shipped with Fedora was out of date, I dumped the newer tools from google into my /usr/bin.
Here is a dump of my last step by step attempt text file
OK, couple things you can try.
- Switch to slot a and try flashing again.
- If that doesn't work, flash the copy-partitions zip from the lineage wiki then try again.
Btw you can check the size of the super partition using fastboot getvar partition-size:super (you'll have to convert the hex value to decimal). It should be around 7.5 gb. Use fastboot getvar all to get the sizes of all the logical partitions. The total should be between ~3.3 and 4 gb after flashing or about 500 mb after you delete/recreate them.
Matt85m said:
it definitely is in fastbootd, I ran into that issue initially as the android-tools package shipped with Fedora was out of date, I dumped the newer tools from google into my /usr/bin.
Here is a dump of my last step by step attempt text file
Click to expand...
Click to collapse
Responded above.
coomac said:
Responded above.
Click to expand...
Click to collapse
worked it out looking at the entire list of partitions - I had 3 lots of each rom partion for example system_a, system_b and system, for all vendor product etc. purging the ones without the _a/b allowed the process to complete.
Might be a quirk of lineageOS installation process - you might want to make a note of it on the OP incase someone else runs into it
Matt85m said:
worked it out looking at the entire list of partitions - I had 3 lots of each rom partion for example system_a, system_b and system, for all vendor product etc. purging the ones without the _a/b allowed the process to complete.
Might be a quirk of lineageOS installation process - you might want to make a note of it on the OP incase someone else runs into it
Click to expand...
Click to collapse
Good to know. I'll update the OP.