Hi,
I want to give my unlocked Moto G to a family member - and I'd like to relock the bootloader again, for security reasons.(I don't care about the warranty)
is there a way to do that?
RazorHail said:
Hi,
I want to give my unlocked Moto G to a family member - and I'd like to relock the bootloader again, for security reasons.(I don't care about the warranty)
is there a way to do that?
Click to expand...
Click to collapse
open FAQ
ctrl+f : "relock"
matmutant said:
open FAQ
ctrl+f : "relock"
Click to expand...
Click to collapse
thanks,
I've already tried that.
But when I enter "fastboot oem lock", I get:
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
Click to expand...
Click to collapse
when I enter the suggested "fastboot oem lock begin", I get:
(bootloader) Ready to flash signed images
Click to expand...
Click to collapse
I'm not sure what that's suppose to mean.....I already downloaded the official firmware images and flashed those immediately after I get this message........but it still says that the bootloader is unlocked.
And immediately returning back to the bootloader and typing in "fastboot oem lock" still won't work - same message as before...
am I missing something?
RazorHail said:
thanks,
I've already tried that.
But when I enter "fastboot oem lock", I get:
when I enter the suggested "fastboot oem lock begin", I get:
I'm not sure what that's suppose to mean.....I already downloaded the official firmware images and flashed those immediately after I get this message........but it still says that the bootloader is unlocked.
And immediately returning back to the bootloader and typing in "fastboot oem lock" still won't work - same message as before...
am I missing something?
Click to expand...
Click to collapse
Yup, this "unlock-relock" is WIP yet ..
i done a relock last week and this works for me.use adb command "fastboot oem lock begin" go through the routine to flash factory firmware image and use "fastboot oem lock" command to finish after you flashed factory firmware.
akaygee said:
i done a relock last week and this works for me.use adb command "fastboot oem lock begin" go through the routine to flash factory firmware image and use "fastboot oem lock" command to finish after you flashed factory firmware.
Click to expand...
Click to collapse
So, steps are these:
1: fastboot oem lock begin
2: flash stock firmware
3: fastboot oem lock
And BL will be locked again. Correct me if i'm wrong.
Problem is that for "unlocked" we need always of a code by motorola atm.
denzel09 said:
So, steps are these:
1: fastboot oem lock begin
2: flash stock firmware
3: fastboot oem lock
And BL will be locked again. Correct me if i'm wrong..
Click to expand...
Click to collapse
thats how it works on most motorola android phones i have used ,it works fine on my moto g so yes that is right.
like so
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
akaygee said:
thats how it works on most motorola android phones i have used ,it works fine on my moto g so yes that is right.
like so
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
Click to expand...
Click to collapse
for me not working
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
danger2u said:
for me not working
Click to expand...
Click to collapse
you didn't flash factory firmware in between
akaygee said:
you didn't flash factory firmware in between
Click to expand...
Click to collapse
i have some problem when i try to flash the system img
this is just a quick howto am at work....
the files you need and will use are in moto g section of this forum.
firmware's here
http://forum.xda-developers.com/showthread.php?t=2546251
relock bootloader
=============
keep in mind this will remove any and all personal files and settings
like any self respecting android user you have made backups right....!!!! GOOD
download adb and fastboot extract or place into a directory.
now download the factory firmware image of your phone extract zip/rar and place into the same directory.
download "relock bootloader.txt" rename to "relock bootloader.bat" place this in the same directory as the files and double click it ,this would save you typing in all the commands from below in by hand and does it all for you.recap....if you did download and run relock bootloader.bat you dont need to type anything form below
open a command prompt as administrator ,navigate to the directory where you placed all the files we are working with and type as follows giving time for each command to finish.
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
When we ask the motorola unlock code, this does not imply that we actually unlock the bootloader.
I mean, i can ask to motorola to unlock code but i can decide to unlock also after sometimes, who stops me.
So, i think that when we relock bootloader, also if previously we asked an unlock code, we are ok, for what i writed above. How can they to be sure that bootloader has been really unlocked in case of brick or hardware failure ?
denzel09 said:
When we ask the motorola unlock code, this does not imply that we actually unlock the bootloader.
I mean, i can ask to motorola to unlock code but i can decide to unlock also after sometimes, who stops me.
So, i think that when we relock bootloader, also if previously we asked an unlock code, we are ok, for what i writed above. How can they to be sure that bootloader has been really unlocked in case of brick or hardware failure ?
Click to expand...
Click to collapse
the boot loader has a status indicator.phone shops/retailers probably won't check it but motorola will.
akaygee said:
the boot loader has a status indicator.phone shops probably won't check it but motorola will.
Click to expand...
Click to collapse
Understood, i had read something in an other post, so to complete the "opera" we need to 'something' to reset that count/status? Like on samsung device, s2 et similia?
denzel09 said:
Understood, i had read something in an other post, so to complete the "opera" we need to 'something' to reset that count/status? Like on samsung device, s2 et similia?
Click to expand...
Click to collapse
yes that is right we would need to find out what file is responsible for storing the count or status of the boot loader as its not the boot loader its self that holds this information.even if you flash the whole system after relocking the bootloader the count is still there.
akaygee said:
yes that is right we would need to find out what file is responsible for storing the count or status of the boot loader as its not the boot loader its self that holds this information.even if you flash the whole system after relocking the bootloader the count is still there.
Click to expand...
Click to collapse
wth i just doing wrong???
the firmware is Blur_Version.14.91.11.falcon_umts.Retail.en.DE
he gives me this error and on the phone says failed to validate system image
akaygee said:
yes that is right we would need to find out what file is responsible for storing the count or status of the boot loader as its not the boot loader its self that holds this information.even if you flash the whole system after relocking the bootloader the count is still there.
Click to expand...
Click to collapse
Motorola talked about a fuse that is "burned" when unlocking, that's why they know, even after relocking
_________________________
i need to update FAQ about relocking (i never ever needed to relock a bootloader myself )
So for relocking, i would like to directly link your post @akaygee, please duplicate it in FAQ thread . then, i'll ask the current thread to be moved to Q&A.
@danger2u
interesting ,are you using a carrier branded phone.? that or the bootloader is locked
i used this method on a uk retail moto g and never run into any problems
akaygee said:
interesting ,are you using a carrier branded phone.?
i used this method on a uk retail moto g and never run into any problems.
Click to expand...
Click to collapse
no is not branded
i bought from italian retail store
now i will try to flash with uk firmware
matmutant said:
Motorola talked about a fuse that is "burned" when unlocking, that's why they know, even after relocking
_________________________
i need to update FAQ about relocking (i never ever needed to relock a bootloader myself )
So for relocking, i would like to directly link your post @akaygee, please duplicate it in FAQ thread . then, i'll ask the current thread to be moved to Q&A.
Click to expand...
Click to collapse
So it will be impossible to reset that status ?
Related
Hey,
So I've been searching for a few days now in the moto g section. I can't find any guides to restore my moto g GPE US version to stock. I found somewhat of walkthrough using the moto tool but I dont' have a windows machine to run that program. Is there another way to do this? Please let me know, also if I missed a post that shows this info please reply with the link.
Thank you!
If you don't have a Windows machine, it'd be good if we knew what you do have in order to guide you properly.
Flashing back to stock on Linux is quite easy once you've got the tools set up. I would assume MacOS X is similar provided you can get a suitable fastboot or mfastboot binary. (I recommend having them in a directeory listed in your $PATH variable with proper permissions for USB so that you don't need to sudo to use them.)
If you've got no computer, but can boot in a modified recovery, it should be possible to flash the entire stock ROM with that. You wouldn't be able to relock the bootloader though, if that's something you were aiming for.
killjoydreams said:
Hey,
So I've been searching for a few days now in the moto g section. I can't find any guides to restore my moto g GPE US version to stock. I found somewhat of walkthrough using the moto tool but I dont' have a windows machine to run that program. Is there another way to do this? Please let me know, also if I missed a post that shows this info please reply with the link.
Thank you!
Click to expand...
Click to collapse
If you are on MAC or linux I suppose you have fastboot installed! If not get it installed from here
Now To restore your phone to stock download this firmware.
After Downloading! Extract the firmware. cd to the directory of extraction.
Use the script in the attachement to restore your phone.
OR
Enter these commands manually
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
You will need the path to fastboot to be added in path variable!
OMG!!!! thank you, thank you, thank you!!!!!
Worked like a charm, I was flipping out trying to figure this out b4 I had to work, your a life saver!!! Btw is there any downside to this process, like can I re-lock the boot loader and is it still possible to get OTA updates?
OTA updates work regardless of whether your bootloader is unlocked or not.
It's root and other changes to the /system partition that'd prevent such updates from working.
killjoydreams said:
Worked like a charm, I was flipping out trying to figure this out b4 I had to work, your a life saver!!! Btw is there any downside to this process, like can I re-lock the boot loader and is it still possible to get OTA updates?
Click to expand...
Click to collapse
No no downsides
You can re-lock the bootloader
And you will get OTA updates as well, even if your bootloader is unlocked!
Just have stock recovery
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own.
This firmware can be flashed on Both locked and Unlocked Bootloaders
Moto G4 Plus [XT1640/XT1641/XT1642/XT1643/XT1644] ATHENE NPJ25.93-14 FASTBOOT + Relock Bootloader
Requirements:
1. Download the Minimal ADB and Fastboot = https://www.androidfilehost.com/?fid=745425885120698566
2. Install Minimal ADB and Fastboot = https://forum.xda-developers.com/showthread.php?t=2317790
3. Moto Drivers
For Windows: http://www.devfiles.co/download/5eExXq3a/MotorolaDeviceManager_2.5.4.exe
For Mac:http://www.devfiles.co/download/i51GYJjz/MDM_Installer_2.2.9.dmg
4. Download Fastboot ROM Zip : https://drive.google.com/file/d/0Bx6eXSiwEdFFWXZyYjB5S0xlZWs/view :good:
Firmware via FASTBOOT:
1. Download the rar file and unzip it.
2.Extract all the files to your fasboot folder.
3.Restart the Moto G4 in fastboot mode.
4. Make sure that usb debugging is on.
5.Connect the Phone in fastboot mode to the computer
Run the "OEM Flash.bat" script that is inside the folder that is created when you unzip the file.(If you want to lock your bootloader Use "OEM lock.bat")
You Can also do it Manually In adb fastboot folder shift+right click and then in the pop up click open command window here
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
NOTE:
1. If you dont want to lock your bootloader just skip the "fastboot oem lock" and "fastboot oem lock begin" Commands
2. Since this file was compressed using 7zip you need 7zip to extract it using Winrar or Winzip will give you an error you can download 7zip from http://www.7-zip.org/download.html
3.Using the "OEM Flash.bat" or "OEM lock.bat" will wipe your data and all the Customizations like Root and Xposed and get it to Factory Condition if You are Reverting back to Stock from a Custom Rom Or Upgrading Stock it is Strongly Advised to Wipe your Data to avoid bugs and crashes(system/app)
In any case if you don't want to wipe data just remove this command "fastboot erase userdata" from the bat file or skip it if your flashing manually
HIT THANKS IF I HELPED YOU !
FOR FURTHER ASSISTANCE JOIN THE TELEGRAM GROUP FOR OUR G4 FAMILY https://telegram.me/g4plus
Works on XT1622 ?
kosmasgr said:
Works on XT1622 ?
Click to expand...
Click to collapse
May work not confirmed
kosmasgr said:
Works on XT1622 ?
Click to expand...
Click to collapse
Yes it does. Just used it to re lock my uk 1622. All seems to be working perfectly. Shows the correct model in about settings
oldsoulsong said:
Yes it does. Just used it to re lock my uk 1622. All seems to be working perfectly. Shows the correct model in about settings
Click to expand...
Click to collapse
Can confirm.
Just re-locked the bootloader on my European XT1622 with this.
Don't forget to enable OEM Unlocking and USB Debugging in Developer Options!
How about xt1641
Sent from my Moto G (4) using XDA-Developers Legacy app
Can i use this for rooted ressurection remix
Sent from my Moto G4 Plus using Tapatalk
tonypooyappallil said:
Can i use this for rooted ressurection remix
Click to expand...
Click to collapse
Yes
daeshawn said:
How about xt1641
Click to expand...
Click to collapse
Yes it works on xt1641
Greekgodmerwyn said:
Yes
Click to expand...
Click to collapse
So if i use this, i will relock my bootloader, then iam eligible for warranty?
Sent from my Moto G4 Plus using Tapatalk
tonypooyappallil said:
So if i use this, i will relock my bootloader, then iam eligible for warranty?
Click to expand...
Click to collapse
No you have received an unlock key from Motorola to unlock your bootloader hence when they enter your serial no they will find out in their data base that your device was unlocked
Greekgodmerwyn said:
No you have received an unlock key from Motorola to unlock your bootloader hence when they enter you serial no they will find out in their data base that your device was unlocked :good:
Click to expand...
Click to collapse
Okay. But the device will get locked bootloader right?
Sent from my Moto G4 Plus using Tapatalk
tonypooyappallil said:
Okay. But the device will get locked bootloader right?
Click to expand...
Click to collapse
Yes use the oemlock.bat or if you are doing it manually then use the OEM lock commands this will only work if you are upgrading
Greekgodmerwyn said:
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own.
Moto G4 Plus [XT1640/XT1641/XT1642/XT1643] ATHENE NPJ25.93-14 FASTBOOT + Relock Bootloader
Requirements:
1. Download the Minimal ADB and Fastboot = https://drive.google.com/file/d/0B1M...ew?usp=sharing
2. Install Minimal ADB and Fastboot = https://forum.xda-developers.com/showthread.php?t=2317790
3. Moto Drivers
For Windows: http://www.devfiles.co/download/5eExXq3a/MotorolaDeviceManager_2.5.4.exe
For Mac:http://www.devfiles.co/download/i51GYJjz/MDM_Installer_2.2.9.dmg
4. Download Fastboot ROM Zip : https://drive.google.com/file/d/0Bx6eXSiwEdFFWXZyYjB5S0xlZWs/view :good:
Firmware via FASTBOOT:
1. Download the rar file and unzip it.
2.Extract all the files to your fasboot folder.
3.Restart the Moto G4 in fastboot mode.
4. Make sure that usb debugging is on.
5.Connect the Phone in fastboot mode to the computer
Run the "OEM Flash.bat" script that is inside the folder that is created when you unzip the file.(If you want to lock your bootloader Use "OEM lock.bat")
You Can also do it Manually In adb fastboot folder shift+right click and then in the pop up click open command window here
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
fastboot erase clogo
fastboot oem lock
fastboot reboot
NOTE:
If you dont want to lock your bootloader just skip the "fastboot oem lock" and "fastboot oem lock begin" Commands
HIT THANKS IF I HELPED YOU !
FOR FURTHER ASSISTANCE JOIN THE TELEGRAM GROUP FOR OUR G4 FAMILY https://telegram.me/g4plus
Click to expand...
Click to collapse
The image is corrupted plz upload new image in google drive
a-2-k said:
The image is corrupted plz upload new image in google drive
Click to expand...
Click to collapse
Use 7Zip to Extract it is a 7zip file if you try to extract it with winrar or WinZip you will definitely get an error and please don't quote the whole thread while replying
Greekgodmerwyn said:
Use 7Zip to Extract it is a 7zip file if you try to extract it with winrar or WinZip you will definitely get an error and please don't quote the whole thread while replying
Click to expand...
Click to collapse
sorry I don't see....7zip
xploder270 said:
Can confirm.
Just re-locked the bootloader on my European XT1622 with this.
Don't forget to enable OEM Unlocking and USB Debugging in Developer Options!
Click to expand...
Click to collapse
What about your baseband version now ? Is it still EMEA ? (I am extra cautious not to lose European LTE bands).
a-2-k said:
sorry I don't see....7zip
Click to expand...
Click to collapse
download from here:
http://www.7-zip.org/download.html
rjtgupta84 said:
download from here:
http://www.7-zip.org/download.html
Click to expand...
Click to collapse
I think he meant to say that he didn't know that it was 7zip
Greekgodmerwyn said:
I think he meant to say that he didn't know that it was 7zip
Click to expand...
Click to collapse
Yes you got it
Hi, I'm trying to flash firmware on moto g3 but when I write command "fastboot flash partition gpt.bin" it tells me "error: cannot found 'gpt.bin' ". I have got all files thats are necessary. What is wrong with my phone? Some one had this problem? Someone can help me?
I actualy did it. I used Minimal ADB and fastboot program. But now, when I'm trying to lock bootloader, it saies "Please fully flash the signed build before locking phone!". I flashed system stepbystep with https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 ( without flashing gpt.bin because it saies "Preflash validation failed" ) Any ideas?
Theheero said:
I actualy did it. I used Minimal ADB and fastboot program. But now, when I'm trying to lock bootloader, it saies "Please fully flash the signed build before locking phone!". I flashed system stepbystep with https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 ( without flashing gpt.bin because it saies "Preflash validation failed" ) Any ideas?
Click to expand...
Click to collapse
You can't relock the bootloader using a version of firmware that is older than what you have... that is what you are trying to do.
Don't preface the flash with "oem lock begin", just start with like this:
fastboot oem fb_mode_set
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash partition gpt.bin
<rest of stuff>
fastboot oem fb_mode_clear
fastboot reboot
Without a version of official firmware that is the same or newer than what you have installed, you cannot relock the bootloader... and we don't have the current releases.
acejavelin said:
You can't relock the bootloader using a version of firmware that is older than what you have... that is what you are trying to do.
Don't preface the flash with "oem lock begin", just start with like this:
fastboot oem fb_mode_set
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash partition gpt.bin
<rest of stuff>
fastboot oem fb_mode_clear
fastboot reboot
Without a version of official firmware that is the same or newer than what you have installed, you cannot relock the bootloader... and we don't have the current releases.
Click to expand...
Click to collapse
Any danger if I 'll use gpt.bin from other firmware of other version of phone which match?
Theheero said:
Any danger if I 'll use gpt.bin from other firmware of other version of phone which match?
Click to expand...
Click to collapse
Don't do it. Download the factory images for your specific device here https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639, and flash them.
i have the official firmware downloaded using Lenovo Moto Smart Assistant: OCEAN_PPOS29.114_134_7_1_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
running a batch file with the following
Code:
fastboot set_active a
fastboot reboot-bootloader
sleep 5
fastboot oem lock begin
fastboot oem lock begin
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.exe erase modemst1
fastboot.exe erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
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 system.img_sparsechunk.9
fastboot flash system_b system.img_sparsechunk.0
fastboot flash system_b system.img_sparsechunk.1
fastboot flash system_b system.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.exe erase carrier
fastboot.exe erase userdata
fastboot.exe erase ddr
fastboot oem fb_mode_clear
fastboot oem lock
pause
when i run
Code:
fastboot oem lock
the final time it tells me "Still Requires Signed Boot.Img"
flashing the boot.image results in "(bootloader) Still require signed boot.img"
any ideas where i can get a working boot.img?
MadMan29729 said:
i have the official firmware downloaded using Lenovo Moto Smart Assistant: OCEAN_PPOS29.114_134_7_1_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
running a batch file with the following
when i run the final time it tells me "Still Requires Signed Boot.Img"
flashing the boot.image results in "(bootloader) Still require signed boot.img"
any ideas where i can get a working boot.img?
Click to expand...
Click to collapse
(coming from flashing stock)
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
vinoxflame said:
(coming from flashing stock)
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
Click to expand...
Click to collapse
that worked! Thanks!
that didn't lock mine
C:\ADB>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (32768 KB)...
OKAY [ 0.993s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.763s]
finished. total time: 1.760s
C:\ADB>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.014s
your going to have to root it with magisk or the option will be greyed out and say "bootloader already unlocked".. once you have a booted rooted rom, goto developer options and check enable Allow OEM Unlock..
MadMan29729 said:
your going to have to root it with magisk or the option will be greyed out and say "bootloader already unlocked".. once you have a booted rooted rom, goto developer options and check enable Allow OEM Unlock..
Click to expand...
Click to collapse
So have to to root it first, then lock the bootloader?
endleesss said:
So have to to root it first, then lock the bootloader?
Click to expand...
Click to collapse
Yeah that doesn't sound like a good idea.
Sent from my mata using XDA Labs
---------- Post added at 05:58 AM ---------- Previous post was at 05:56 AM ----------
Make sure you have the correct software channel
Sent from my mata using XDA Labs
yes cause that's what I had to do cause motorola won't let you relock it unless you flash the factory firmware along with the lock command but you can't lock it without checking allow oem unlock
endleesss said:
So have to to root it first, then lock the bootloader?
Click to expand...
Click to collapse
its the only way to get rid of the bootloader error that says you need to enable Allow OEM Unlock.. rooting with magisk just forces the allow oem unlock to be enabled.. so you can check it..
as far as locking.. once you run the lock commands you have to flash the factory images then run the lock command again.. therefore you won't be rooted in the end!
Question for anyone who may know ..
So if we're already rooted and we would like to lock our bootloader we have to flash our factory image and type in the bootloader lock command as well?
Anyone successfully locked there bootloader?
If we have an unlocked bootloader and we lock it can we return back to unlocked bootloader immediately afterwards? Has anyone done this? Do we use same method as we initially did to unlock our bootloader? I only say that because I do not have my original code for my bootloader unlock that I used. If we go about it same way will Motorola give us the code again or do we need to still have those #s that we originally used?
I'm on a mission now. Soon as I comment this I'll search my butt off for a while and see what all I can figure out. If I get any good solid information I shall return here and share it for sure. Good day to everyone.
---------- Post added at 07:21 PM ---------- Previous post was at 07:08 PM ----------
Credit to @smokinu from motp G7 River forum. I'm pasting the comment here below.
I saw the same thing on my end at first. Found this to work repeatedly....
fastboot oem lock (enter this a few times until i says something to the effect of...."you still need to flash a signed boot.img")
fastboot flash boot boot.img (this will now flash fine without saying the image is not signed)
fastboot oem lock (if you prefer to re-lock. You'll need the unlock key again if you plan to unlock).
Above is from post #34 here: https://forum.xda-developers.com/mo...are-29-114-t3913673/post79305396#post79305396 And I'm quite sure the same method will work for Power although I have not tested this. Pretty sure it will though.
In order to relock my bootloader, I had to root my phone using the magisk method.
After I was rooted I was able to go into develope options and turn on allow oem unlocking.
Then, I was able to flash the signed bootloader from an oem firmware and relock the bootloader.
You must use the same bootloader version that is currently on your phone. You can not downgrade the bootloader.
And yes, you can unlock it at a later time.
Sent from my moto g(7) power using Tapatalk
MrCamby said:
In order to relock my bootloader, I had to root my phone using the magisk method.
After I was rooted I was able to go into develope options and turn on allow oem unlocking.
Then, I was able to flash the signed bootloader from an oem firmware and relock the bootloader.
You must use the same bootloader version that is currently on your phone. You can not downgrade the bootloader.
And yes, you can unlock it at a later time.
Click to expand...
Click to collapse
Thanks for the info! I always just assume on any device that bootloader can't be downgraded. When I first get the device anyway.. thanks!
can you help me relock bootloader of motorola one p30 play? i am having same issue even after typing
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
it still says "still require signed boot.img"
also i have a dual slot partition slot phone
Hey everyone. So recently I tried rooting my motorola g7 play. I followed this guide on youtube
and everything was going fine until one point I received something like "bad error" (or something like that) when I tried installing magisk patched boot.img file on my phone. It then asked if I would try installing again or do a factory reset. I tried again and it didn't work so thought I had no choice besides to do a factory reset. When I booted it back up, it put this code on the top left of the screen: 80012A99-86FDA48-4E357816-0E549F1B-B067FD5 and then everything was working fine until it asked to do the language selection. The problem was that the touch screen wouldn't work anymore, but the side buttons still work. So I tried restarting my phone, safe mode and using things in bootload mode (factory mode, recovery mode, etc.) and the screen still didn't work. I think the problem may be where I got the boot.img from, which is here: https://forum.xda-developers.com/t/magisk-on-g7-play-xt1952-4-installed-succesfully.3975477/ and I feel like this problem is still able to be fixed. I was considering buying an otg adapter to try connecting my mouse to the phone, but I'm not sure since it might be considered a waste of money. any help would be appreciated. Thanks in advance!
nimbussecond said:
Hey everyone. So recently I tried rooting my motorola g7 play. I followed this guide on youtube
and everything was going fine until one point I received something like "bad error" (or something like that) when I tried installing magisk patched boot.img file on my phone. It then asked if I would try installing again or do a factory reset. I tried again and it didn't work so thought I had no choice besides to do a factory reset. When I booted it back up, it put this code on the top left of the screen: 80012A99-86FDA48-4E357816-0E549F1B-B067FD5 and then everything was working fine until it asked to do the language selection. The problem was that the touch screen wouldn't work anymore, but the side buttons still work. So I tried restarting my phone, safe mode and using things in bootload mode (factory mode, recovery mode, etc.) and the screen still didn't work. I think the problem may be where I got the boot.img from, which is here: https://forum.xda-developers.com/t/magisk-on-g7-play-xt1952-4-installed-succesfully.3975477/ and I feel like this problem is still able to be fixed. I was considering buying an otg adapter to try connecting my mouse to the phone, but I'm not sure since it might be considered a waste of money. any help would be appreciated. Thanks in advance!
Click to expand...
Click to collapse
I started flashing TWRP a month or so ago on my g9 Power with the wrong version and the touchscreen did the same thing, I attached an OTG and hooked the mouse and it worked great... As for your failed flash, is your firmware xt1952-4? I suspect that boot.img is from a phone with a different touchscreen. I would find the correct firmware from lollinet and reflash a stock boot.img and you should be fine. Install Magisk as an app then modify your own boot.img and install root that way. ALSO if you can still use side buttons you should still be able to flash a new stock boot.img from inside fastboot without digitizer support...
Dauksza72 said:
Accident... Don't know how to delete it now...
Click to expand...
Click to collapse
Dauksza72 said:
I started flashing TWRP a month or so ago on my g9 Power with the wrong version and the touchscreen did the same thing, I attached an OTG and hooked the mouse and it worked great... As for your failed flash, is your firmware xt1952-4? I suspect that boot.img is from a phone with a different touchscreen. I would find the correct firmware from lollinet and reflash a stock boot.img and you should be fine. Install Magisk as an app then modify your own boot.img and install root that way. ALSO if you can still use side buttons you should still be able to flash a new stock boot.img from inside fastboot without digitizer support...
Click to expand...
Click to collapse
OK, thank you so much. In fastboot mode it says Product/Variant: channel XT1952-4 32GB PVT, so I assume that the firmware is indeed xt1952-4. Also could you clarify how to flash a new stock boot.img from inside fastboot because I'm not sure how to modify anything on my phone without allowing usb debugging (which I can't do since the phone factory resetted). If there are no other options I plan on trying the OTG adapter then.
nimbussecond said:
OK, thank you so much. In fastboot mode it says Product/Variant: channel XT1952-4 32GB PVT, so I assume that the firmware is indeed xt1952-4. Also could you clarify how to flash a new stock boot.img from inside fastboot because I'm not sure how to modify anything on my phone without allowing usb debugging (which I can't do since the phone factory resetted). If there are no other options I plan on trying the OTG adapter then.
Click to expand...
Click to collapse
I've not had issues with using fastboot after a stock flash even without going in and enabling adb thru developer mode. When you hold volume - while powering up and plug in the usb cord from the PC you should go into the bootloader and can flash the new boot image from there with fastboot commands. You may already know but open cmd prompt on pc, type cd then drag your fastboot directory folder over to cmd prompt and drop it, click anywhere in cmd prompt and hit enter. Put your system boot image inside the folder with you fastboot files and type "./fastboot flash boot boot.img" and hit enter and you should be flashing.
Dauksza72 said:
I've not had issues with using fastboot after a stock flash even without going in and enabling adb thru developer mode. When you hold volume - while powering up and plug in the usb cord from the PC you should go into the bootloader and can flash the new boot image from there with fastboot commands. You may already know but open cmd prompt on pc, type cd then drag your fastboot directory folder over to cmd prompt and drop it, click anywhere in cmd prompt and hit enter. Put your system boot image inside the folder with you fastboot files and type "./fastboot flash boot boot.img" and hit enter and you should be flashing.
Click to expand...
Click to collapse
Thanks so much, my phone seems to work fine now. I ended up finding the right boot.img file and wanted to try following the video again, but at the last step where I have to flash the magisk patched img file, command prompt gives me the error (bootloader) is-logical:boot_b: not found. Do you know what I can do to so that it can flash properly?
nimbussecond said:
Thanks so much, my phone seems to work fine now. I ended up finding the right boot.img file and wanted to try following the video again, but at the last step where I have to flash the magisk patched img file, command prompt gives me the error (bootloader) is-logical:boot_b: not found. Do you know what I can do to so that it can flash properly?
Click to expand...
Click to collapse
In fastbootD, (go to bootloader and type
./fastboot reboot fastboot)
./fastboot erase-logical-partition product_a
./fastboot erase-logical-partition product_b
then flash the Magisk_modified.img to boot_a and boot_b from fastboot.
./fastboot flash boot_a Magisk(whatever Magisk named it)
./fastboot flash boot_b Magisk(whatever Magisk named it)
./fastboot -w
./fastboot reboot
Now that you know how to recover from a soft brick don't be afraid to play around with it. Eventually you'll make a text document and have all your commands on it so all you have to do is copy the whole page and paste it in fastboot and pretty much automate the whole process... Let me know if that helps.
Realized I typed flash product_a/b instead of boot_a and boot_b... SORRY. Total oversize. Delete product , flash boot
Dauksza72 said:
In fastbootD, (go to bootloader and type
./fastboot reboot fastboot)
./fastboot erase-logical-partition product_a
./fastboot erase-logical-partition product_b
then flash the Magisk_modified.img to boot_a and boot_b from fastboot.
./fastboot flash boot_a Magisk(whatever Magisk named it)
./fastboot flash boot_b Magisk(whatever Magisk named it)
./fastboot -w
./fastboot reboot
Now that you know how to recover from a soft brick don't be afraid to play around with it. Eventually you'll make a text document and have all your commands on it so all you have to do is copy the whole page and paste it in fastboot and pretty much automate the whole process... Let me know if that helps.
Click to expand...
Click to collapse
For some reason I can't get into FastbootD, it gives the error FAILED (remote: 'Unknown command') fastboot: error: Command failed. I tried searching up stuff, removing the passcode, switching USB ports and more but I couldn't get the screen to pop up. What can I do about this?
Have you tried reflashing stock recovery? You also may be able to delete partition and flash through regular fastboot. If you still haven't got it by this evening then I'll brick my wife's g7 and figure out a work around for you.
Dauksza72 said:
Have you tried reflashing stock recovery? You also may be able to delete partition and flash through regular fastboot. If you still haven't got it by this evening then I'll brick my wife's g7 and figure out a work around for you.
Click to expand...
Click to collapse
So I tried flashing stock recovery and I seem to get a similar error to when I flash the magisk patched file and I've tried deleting partition and flash through regular fastboot, but it didn't work either (error in the image). I might be doing something wrong since I'm still very new to this, but I also tried downloading TWRP since I know that's another way to root and it lead to the same problems as well (bootloader) is-logical whatever I'm trying to do not found. I also tried LMSA (Lenovo Rescue and Smart Assistant) to see if there was something wrong with my phone, but it made no difference. I might consider an alternative rooting method, let me know what's the best option. You don't have to brick your wife's g7, but either way I appreciate it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok, do this and post a screenshot again and we'll get it pinpointed. I think your tools are out of date but it could still be a firmware issue.
Make sure you're using latest platform tools, https://developer.android.com/studio/releases/platform-tools.
./fastboot --version
./fastboot -w
./fastboot getvar current-slot
./fastboot oem device-info
Are you sure the g7 Play has a separate recovery partition? It may be part of the boot partition... Instead of flashing the modified image to a/b just try
./fastboot flash boot "modimg".img
Dauksza72 said:
Ok, do this and post a screenshot again and we'll get it pinpointed. I think your tools are out of date but it could still be a firmware issue.
Make sure you're using latest platform tools, https://developer.android.com/studio/releases/platform-tools.
./fastboot --version
./fastboot -w
./fastboot getvar current-slot
./fastboot oem device-info
Click to expand...
Click to collapse
Ok I updated it to the most recent version and also fastboot flash boot "modimg".img says boot_a not found as well. Here are the results of the commands you told me to run.
Are these the files you have?
Post a screenshot of the flashfile.xml or servicefile.xml
nimbussecond said:
Ok I updated it to the most recent version and also fastboot flash boot "modimg".img says boot_a not found as well. Here are the results of the commands you told me to run. View attachment 5295077
Click to expand...
Click to collapse
The G7 Play doesn't have fastbootd and recovery/boot are merged. You can't have twrp and magisk at the same time. Magisk must patch the boot.img as recovery. (Check all 3 boxes) When you boot up, you must hold Vol↓+power, and select recovery from the fastboot menu to have root.
Inside your firmware zip, there's a flashfile.xml, open it and flash everything as directed, and in order. It'll start with gpt.bin. That's the only tricky one, it repartitions the phone so it flashes to "partition" like so...
fastboot flash partition gpt.bin
Spaceminer said:
The G7 Play doesn't have fastbootd and recovery/boot are merged. You can't have twrp and magisk at the same time. Magisk must patch the boot.img as recovery. (Check all 3 boxes) When you boot up, you must hold Vol↓+power, and select recovery from the fastboot menu to have root.
Inside your firmware zip, there's a flashfile.xml, open it and flash everything as directed, and in order. It'll start with gpt.bin. That's the only tricky one, it repartitions the phone so it flashes to "partition" like so...
fastboot flash partition gpt.bin
Click to expand...
Click to collapse
Thanks, that's where I was headed with this.
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 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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot oem fb_mode_clear
fastboot erase userdata
fastboot erase DDR
Dauksza72 said:
Thanks, that's where I was headed with this.
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 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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot oem fb_mode_clear
fastboot erase userdata
fastboot erase DDR
Click to expand...
Click to collapse
I did a lot of dev work for this phone. I had to help.
Alright so I did what you guys told me to with the flashfile.xml, the zip I used is XT1952-4_CHANNEL_RETCA_10_QPYS30.52-22-11-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml. I tried doing recovery mode after this and after flashing the magisk boot.img, but it had the same result. I'm not sure what to do after this step. (These are the screenshots after I did the commands).
nimbussecond said:
Alright so I did what you guys told me to with the flashfile.xml, the zip I used is XT1952-4_CHANNEL_RETCA_10_QPYS30.52-22-11-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml. I tried doing recovery mode after this and after flashing the magisk boot.img, but it had the same result. I'm not sure what to do after this step. (These are the screenshots after I did the commands).View attachment 5295529View attachment 5295531View attachment 5295533
Click to expand...
Click to collapse
Install magisk manager, patch your boot.img as "recovery". Flash the patched boot.img. Use the volume buttons while in the bootloader menu to select recovery, and hit the power button. Open magisk and it should be rooted. If it needs additional setup allow it.