Database Info

Relock the Bootloader

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 ?

[Firmware] 8.1 official Moto Z3 Play [BECKHAM]

{
"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"
}
DISCLAIMER
I am not to be held responsible for any of the damage that occurs to your device during this process. You are yourself responsible for any damage done (if) to your device during this process.
REQUIREMENTS
Make sure your device is charged above 80%.
We recommend creating a backup of all your important files before beginning with this process.
HOW TO INSTALL STOCK ROM IN MOTO Z3 Play
Download Moto Z3 Play Stock Firmware from below (in download section).
Install Motorola Driver and ADB Fastboot Driver on your PC.
Now extract stock firmware in ADB Fastboot folder.
Now, turn off your device and boot into bootloader by pressing volume down button +power button simultaneously.
Now, connect your device to your PC via a USB Cable.
Open a command prompt window and type the following commands:
adb fastboot
fastboot flash partition gpt.bin ( not mandatory )
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
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 flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot erase modemst1 ( not mandatory )
fastboot erase modemst2 ( not mandatory )
fastboot reboot
Click to expand...
Click to collapse
Thanks to Motorola firmwares.
Password:
MotorolaFirmwaresLB
BECKHAM_OPW28.70-22_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
-DRIVE
-AFH

Will this work on the Amazon version?

Hello, it should work

I would be VERY careful about trying to use the image provided here.
I picked up the Z3 today hoping to be able to build TWRP recovery with this image. Using the kernel from this image resulted in a permanently bricked device. It would no longer turn on. At all.
Second Z3, using the provided image's boot.img and only booting boot.img from fastboot... hung the device.
This tells me the linked image here is very likely to be incompatible with many Z3 Play devices.
The version I've tested it with is the US retus software channel version.
As far as I've been able to tell, this image is for French devices only. DO NOT use this image if you cannot confirm it will work by testing the boot image first.
Extract boot.img from the archive and put your phone into fastboot mode. Test it by typing "fastboot boot boot.img" - If your phone hangs at the motorola logo, this firmware WILL BRICK YOUR PHONE.
The Z3 Play has NO FIRMWARE candidates on https://firmware.center - So, I repeat, the firmware linked here is likely NOT compatible with your device.

twelfth said:
I would be VERY careful about trying to use the image provided here.
I picked up the Z3 today hoping to be able to build TWRP recovery with this image. Using the kernel from this image resulted in a permanently bricked device. It would no longer turn on. At all.
Second Z3, using the provided image's boot.img and only booting boot.img from fastboot... hung the device.
This tells me the linked image here is very likely to be incompatible with many Z3 Play devices.
The version I've tested it with is the US retus software channel version.
As far as I've been able to tell, this image is for French devices only. DO NOT use this image if you cannot confirm it will work by testing the boot image first.
Extract boot.img from the archive and put your phone into fastboot mode. Test it by typing "fastboot boot boot.img" - If your phone hangs at the motorola logo, this firmware WILL BRICK YOUR PHONE.
The Z3 Play has NO FIRMWARE candidates on https://firmware.center - So, I repeat, the firmware linked here is likely NOT compatible with your device.
Click to expand...
Click to collapse
This firmware is for XT1929-4 and no mention is made in the topic....

GuzXT said:
This firmware is for XT1929-4 and no mention is made in the topic....
Click to expand...
Click to collapse
The XT1929-4 is what I have and the firmware definitely did not work for me. I tried to build TWRP for the Z3 Play as I have for other devices and it definitely wasn't going to happen with these files. Even if you 'fastboot boot boot.img', it's supposed to boot like normal using the rest of the what is stored on your phone. Instead it only hangs.

there is this https://forum.xda-developers.com/moto-z/development/tool-motorola-ota-link-generator-tool-t3537039
we just have to wait for OTA i guess
also there is this if you google beckham_opw28.70-25_subsidy-default_regulatory-default_cfc.xml.zip but they ask for money
https://firmware.gem-flash.com/index.php?a=browse&b=category&id=19944
search for 1929- on https://firmware.gem-flash.com/index.php?a=browse&b=category&id=2634

Here in free access all the same))
https://mirrors.lolinet.com/firmware/moto/beckham/official/

Has anyone been able to relock the bootloader in a way that passes safetynet. I noticed that phone boots with verity set at log only which fails CTS and I want to go back to stock until Magisk works properly.

driverdis said:
Has anyone been able to relock the bootloader in a way that passes safetynet. I noticed that phone boots with verity set at log only which fails CTS and I want to go back to stock until Magisk works properly.
Click to expand...
Click to collapse
magic works quite well if you patch the boot normally, with check marks.

Willy33 said:
magic works quite well if you patch the boot normally, with check marks.
Click to expand...
Click to collapse
Thanks, this did the trick. I was able to download use the boot.img from the lollinet mirror firmware zip. It does require both force encrypt and verity enabled before patching it or it will boot loop.

---REDACTED---

Will this work on the Moto Z3 (XT1929-17)?

wanb1i said:
Will this work on the Moto Z3 (XT1929-17)?
Click to expand...
Click to collapse
You need a firmware image for your specific device. Check the websites from this thread and see if you can find one specific to your device. Other images could brick your device.
The steps should be the same for every device as far as fastboot flashing goes. But don't use an image for another device

darkdaemon32 said:
You need a firmware image for your specific device. Check the websites from this thread and see if you can find one specific to your device. Other images could brick your device.
The steps should be the same for every device as far as fastboot flashing goes. But don't use an image for another device
Click to expand...
Click to collapse
Found the original vzw firmware on Moto's site.
Thanks!

twelfth said:
The XT1929-4 is what I have and the firmware definitely did not work for me. I tried to build TWRP for the Z3 Play as I have for other devices and it definitely wasn't going to happen with these files. Even if you 'fastboot boot boot.img', it's supposed to boot like normal using the rest of the what is stored on your phone. Instead it only hangs.
Click to expand...
Click to collapse
So I have a Verizon Moto Z3 (Brand New XT1929-17, NO XDA Thread yet) I found the firmware off the Motorola site at this link https://androidfilehost.com/?w=files&flid=279604 (last file). I unzipped it, copied the boot.img to my adb folder and executed fastboot boot boot.img and this is the result:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.622s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.633s
My goal here is to modify a boot.img so I can root with Magisk without unlocking the bootloader. (Verizon devices don't allow unlocking the bootloader)
Any help would be appreciated.

wanb1i said:
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.633s
Click to expand...
Click to collapse
Your bootloader is locked. Being a Verizon device, it's likely not unlockable.
You have to have an unlocked bootloader before you can boot and flash in fastboot.
This is why people buy unlocked devices.

Xt-1929-4 opw 20.70-31
Hi, I have the Moto Z3 Play. This is the updated Firmware that I have on my device. I felt I should share it, just in case anyone else needs its. I also added a couple of simple batch files to the folder that I thought everyone might appreciate.
FlashRoot(Service) - Will automatically flash the phone with the patch_boot.img instead of boot.img. This will flash the rooted version of the boot image that was made with Magisk Manager. (Must be in Fastboot)
Flash - Stock --Will automatically flash the regular boot.img also with all the other stock files to the phone. (Must be in Fastboot)
Credit -
Magisk Manager
Google
Hi, I have the Moto Z3 Play. This is the updated Firmware that I have on my device. I felt I should share it, just in case anyone else needs its. I also added a couple of simple batch files to the folder that I thought everyone might appreciate.
FlashRoot(Service) - Will automatically flash the phone with the patch_boot.img instead of boot.img. This will flash the rooted version of the boot image that was made with Magisk Manager. (Must be in Fastboot)
Flash - Stock --Will automatically flash the regular boot.img also with all the other stock files to the phone. (Must be in Fastboot)
Credit -
Magisk Manager
Google
Android FileHost[https ://drive.google. com/open?id=1KAMijX1W2HQx69mDhZ294tp51vtAoo0E[/URL]

Can someone provide a system dump for Moto Z3 Play..
Edit: Done

Hi, my Z3 play has a Bootloop I tried with hard reset and still not working. It's XT1929-6 dual SIM, can someone help me ? Please

[GUIDE] SIMPLE STOCK FLASH AND DOWNGRADE MOTO G6 ALI

{
"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"
}
JOIN MOTO G6 GLOBAL GROUP ON TELEGRAM
https://t.me/Moto_G6 ​
Be sure backup yout own files phone will be erased.
Downgrade can be cause lose ril and IMEI be 0
To recover Empty IMEI and signal read this thread:
(1) [GUIDE] IMEI RECOVERY STOCK & CUSTOM ROM | XDA Developers Forums (xda-developers.com)
> If you don't have download and install drivers and ADB:
Motorola Drivers: https://support.motorola.com/us/en/drivers
ADB WINDOWS https://dl.google.com/android/repository/platform-tools-latest-windows.zip
ADB MAC https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
ADB LINUX https://dl.google.com/android/repository/platform-tools-latest-linux.zip
Download the stock ROM of your own area like RETAIL RETEU RETIN RETAR, from lolinet source and extract and please, don't download from another site or it won't work.
These two ROM work in the most of cases.
RETAIL 9.0 Pie
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
RETEU 9.0 Pie
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Lolinet Official Motorola Ali Source
https://mirrors.lolinet.com/firmware/moto/ali/official/
1. Now start terminal/pront on ADB folder.
2. Extract files from stock rom.
3. Copy files inside ADB mixing.
4. In terminal copy and paste line per line.
4.5. You can copy code in a txt file and make a bat file too.
5. Just wait phone turn ON alone, first boot leave around 10 minutes
Code:
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 bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot

Do not downgrade firmware with a locked bootloader, it may make the device unusable.
These commands need to be changed from time to time.
If you want to know the correct flashing command open the servicefile.xml
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com

sd_shadow said:
Do not downgrade firmware with a locked bootloader, it may make the device unusable.
These commands need to be changed from time to time.
If you want to know the correct flashing command open the servicefile.xml
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
This is the order what work on moto G6 ali guy, we use these too much times on telegram group and works fine, and with lockedboot loader only can be loose ril, justing flashing non--los again you recover it.

brunogroa said:
This is the order what work on moto G6 ali guy, we use these too much times on telegram group and works fine, and with lockedboot loader only can be loose ril, justing flashing non--los again you recover it.
Click to expand...
Click to collapse
Ok but your original post doesn't warn about that, nor how to fix it.

sd_shadow said:
Ok but your original post doesn't warn about that, nor how to fix it.
Click to expand...
Click to collapse
sure, thx i'll put it on XD is my first time posting, and i read a lot of others to make this better, thx guy

I successfully flashed my RETLA Moto G6 but im getting a security patch update notification from 2019 which is obviosuly older than the Stock ROM I flashed. If I try to install this update the update will fail and the phone start again normally. Is there any way to solve this and let the phone "know" the latest version is installed so that I dont get this notification anymore? thanks

how do i downgrade back to android version 8 and relock the bootloader there?

smartasiankid said:
how do i downgrade back to android version 8 and relock the bootloader there?
Click to expand...
Click to collapse
You shouldn't downgrade then lock the bootloader.
You may brick it, if you manage to do it correctly, it will just try to reupdate.

sd_shadow said:
You shouldn't downgrade then lock the bootloader.
You may brick it, if you manage to do it correctly, it will just try to reupdate.
Click to expand...
Click to collapse
oh ok thanks for the warning.

Motorola g7 Play touch screen not working after root attempt

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.

Question need a little information

Moto G stylus 5G Denver build I had TWRP installed and majisk installed I wanted to install a ROM during insallaion i was having issues and needed 2 set my device down for a few minutes and take care of like regular life problems. Anyways my kid get ahold of my phone and did god-knows-what but he had enough time to wipe everything but my external USB drive. i have the full stock file i downloaded to pach wih magisk i have the twrp file as well.i had my backup on my sd card which was erased. so my question is his, where do i go from here? how do i use files in the picture recover back to I guess a stock
{
"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"
}
. Version of Android
also doing all his thru bugjager and im sure more then one guide explaining what to do but i need o be at work in 2 hours and so alink in thr right direction would be awesome

tommy2tones1990 said:
also doing all his thru bugjager and im sure more then one guide explaining what to do but i need o be at work in 2 hours and so alink in thr right direction would be awesome
Click to expand...
Click to collapse
In my opinion I would just restore back to stock. Basically, using bugjager, make sure you have the stock rom downloaded and unzipped. Now you'll want to probably copy and paste these commands but you'll reboot your Stylus 5G into fastboot mode and once its connected to the second device with bugjager on it, start going down the list of flashing the partitions back... Here are commands you can copy and paste:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear

I basically spent a hour trying random things on bugjaegar I honestly have no ideal how I didn't brick this phone seriously but then I flashed vbmeta boot and vendor boot and restarted. It took a long time to start then a msg popped up for half a second and the phone rebooted and then I went thru the whole Google startup process and when I got there I rebooted back to bootloader and flashed the magisk patched img and so far everything seems to work
.. thanks for your help.. I'll probably go ahead and wipe everything and start over using your guide. Then go get everything back to how I had it before and and make multiple backups on at least 2 different micro sds then retry the to install ROM

No worries Just saw your post and figured I'd offer some help.. I personally love the bugjaeger app. I use it all the time... it definitely helps if I'm without a computer and got my tablet lol.. and my handy dandy USB-C to USB-C cable lol...