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 ?

[Being resolved!] MotoG Bootup Problem - Recovery Mode failed

CURRENT UPDATE 25/6 :
unlocked the bootloader and flashed the O.S (5.0.2) without erasing userdata.
stock recovery mode works now.
booted using custom recoveries : a)TWRP 2.8.X.X b)Philz Touch (will add details later)
data recovery almost done.
NEXT STEP : time to install a CLEAN STOCK ROM
PROBLEM : Not booting up to the Android lock-screen
DEVICE INFO :
Phone Model : Moto G XT 1033 Dual SIM (India)
No Root.Bootloader is LOCKED.No customizations.
ADB Debugging disabled (default).
Moto G XT1033(Black, 16 GB)
Using : Android Lollipop (the latest update done by OTA as part of System Update)
Upgraded : 2-3 weeks after the update was released.
Info from Motorola Media Manager (when connected through USB)
{
"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"
}
What Happened :
Day before : Phone switched off at 0% battery.
Put for recharge the next day (29/5) and I tried to switch it on as it reached 35%.
Didn’t boot.Tried a few more times.
I can access :
Only the bootloader
Problem after Moto Boot Animation
http://imgur.com/l5bUHyq
VIDEO :
Main problem :
https://drive.google.com/open?id=0B3l72ArFhLc1ZThqU3ZoY29hWWM&authuser=0
Recovery mode issue:
https://drive.google.com/open?id=0B3l72ArFhLc1LWJ2VXI3SmxEQjA&authuser=0
HD Quality Videos & Images
-> https://drive.google.com/open?id=0B...k50a3VEa1RmZGkwRjJja3E5M0NpSHQzQ3c&authuser=0
Windows Device Mgr:
http://i.imgur.com/lGjFzDR.jpg
What I tried :
http://i.imgur.com/Lq9qHs1.jpg
(suggested on motorola website)Reboot - 10 seconds
(suggested on motorola website)Reboot - 120 seconds power button
Erased cache using fastboot - works.
Recovery mode : I got “bootup failed”
ADB not able to detect the device.Fastboot can.
PC able to detect USB but as a “Falcon Device”
WHAT I WANT :
I want to get a copy of all my internal SD Card data,eg : photos,Contacts,WhatsApp folder,etc.
Flashing it in any way that causes data loss would be my last option.
Besides,i don't have relevant experience and would be asking a friend who has experience with this stuff.
What I found out :
Bootloader UNLOCK will wipe all my internal memory user data.
To root the phone,I’ll have to UNLOCK the Bootloader.
ADB can be used to backup using PUSH,PULL (may or may not require Android USB Debugging enabled)
Battery drained to 0% from 75% in one night when i kept the phone in the blank but bright screen mode.
STEPS AHEAD :
Service Centre Visit (Saturday) - Problem Detection -> Won’t be giving the phone since they might damage the data in a situation where it can be recovered.
More Research about such cases and solutions?
Eg : Battery replacement,re-adjustment.
Any way to make it appear as a storage volume on PC?
Any links,suggestions,etc. can
Motorola Support Says :
Service Centre can help
ADB Reqd to recover data
Or use backup software (how can I do this when i am not able to boot :| )
Went to a Service Centre today,they said they will have to "download" software to the phone to check for problems
So my data will be lost.
So I am currently searching for more solutions.
ANY ADVICE,TIP,COMMENT or even a positive post would be really appreciated.THANKS FOR READING

Do you have a custom recovery installed? If not, try installing TWRP from here: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then use the following ADB command: adb pull /sdcard c:/Motog_backup

Thanks for reading and giving your suggestion
I've never rooted,flashed or unlocked my device,no major modifications as well.
So no custom recovery.
I tried what you suggested but it didn't work for now.
Here's what I got :
Maybe because of the LOCKED Bootloader.
ADB doesn't detect my device probably because i don't have debugging enabled.
Thanks Again @lost101
lost101 said:
Do you have a custom recovery installed? If not, try installing TWRP from here: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then use the following ADB command: adb pull /sdcard c:/Motog_backup
Click to expand...
Click to collapse

@ravibhat - Could you unlock the Bootloader? See FAQ for instructions: http://forum.xda-developers.com/showthread.php?t=2537119

@lost101 : I did consider the option using the "fastboot oem lock" option.But it was claimed that it will delete my user data which i don't want

ravibhat said:
@lost101 : I did consider the option using the "fastboot oem lock" option.But it was claimed that it will delete my user data which i don't want
Click to expand...
Click to collapse
Ah yes, I forgot about that. Good thing you caught it.
XT1032 Retail Asia 5.0.2 Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
mFastboot commands:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3​
Doing only the above commands will not erase userdata, only reinstall Android.

Hey @lost101,
I'll be using the firmware for XT1033 (Asia-Retail 5.0.2) since the one i have is the dual-sim version.
I came across additional commands in this format:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo Moto-logo.bin
fastboot flash boot boot.img
<SYSTEM IMAGE FLASH FILES go here - 4 commands like you said here since it's Lollipop>
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
Since I want to save my data i won't be using "oem unlock" and "erase userdata" commands.
So,
a) Can you tell me if there's a specific reason you didn't add them?Will they damage or reset any of my data or affect user partition?
They were also mentioned by a few folks who are trying something similar while trying to protect their data.
I thought they were part of the process.
b) mfastboot or fastboot - will using the normal "fastboot".exe cause any problems?And so you suggest mfastboot?
And thanks a lot for helping me out
lost101 said:
Ah yes, I forgot about that. Good thing you caught it.
XT1032 Retail Asia 5.0.2 Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
mFastboot commands:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3​
Doing only the above commands will not erase userdata, only reinstall Android.
Click to expand...
Click to collapse

@ravibhat - the fastboot commands I mentioned are the only ones that should be necessary. Report back what happens, and if needed I will suggest additional commands.
mFastboot is preferred because it was created by Motorola for flashing these files. Traditional fastboot may fail to successfully flash the files, and often does.

Hey @lost101!
Man,i tried the commands you mentioned first,didn't work.
Also tried it with the other commands,still no result.
Overall : i didn't get any errors except the ones where i tried to flash a custom recovery.
When i choose the "Recovery" option in the bootloader - I get "booting failed" error for both stock and custom recovery images.
Also,i couldn't directly boot using a custom recovery image file using the "boot" command.
Is it something to do with the files i used or...something else?
Any other tips?
lost101 said:
@ravibhat - the fastboot commands I mentioned are the only ones that should be necessary. Report back what happens, and if needed I will suggest additional commands.
mFastboot is preferred because it was created by Motorola for flashing these files. Traditional fastboot may fail to successfully flash the files, and often does.
Click to expand...
Click to collapse

@lost101 :
Can't boot from stock recovery,however able to flash it (why???)
Can't boot or flash custom recovery (probably because bootloader is locked which i can understand.)
@deej_roamer @deeplyyoung : thoughts and advise please

ravibhat said:
@lost101 :
Can't boot from stock recovery,however able to flash it (why???)
Can't boot or flash custom recovery (probably because bootloader is locked which i can understand.)
Click to expand...
Click to collapse
Please provide a log of what mfastboot responds with when you try to flash a system.img as instructed above. Do not say 'it did not work' - I need to see exactly what is being said by mfastboot.

Hey @lost101
Sorry for not being clear.
Here's the exact response :
Response on the screen:
The responses upto "boot up failed" in the below image were the ones i got while trying to flash recovery images.
The responses below it are the ones i got for flashing those 4 commands.
After this when I try to bootup - the same problem as mentioned in the main thread - getting stuck after Motorola Logo on a blank but active screen.
VIDEO :
Main problem :
https://drive.google.com/open?id=0B3...WWM&authuser=0
Recovery mode issue:
https://drive.google.com/open?id=0B3...QjA&authuser=0
HD Quality Videos & Images
-> https://drive.google.com/open?id=0B3...Q3c&authuser=0
Anything else you'd like to know that can help
lost101 said:
Please provide a log of what mfastboot responds with when you try to flash a system.img as instructed above. Do not say 'it did not work' - I need to see exactly what is being said by mfastboot.
Click to expand...
Click to collapse

@ravibhat - You mention in OP: ADB can be used to backup using PUSH,PULL (may or may not require Android USB Debugging enabled)
When is it working? While the Android is booting up? If so, you could pull the /sdcard/ during that time.
Regarding your previous post:
Mismatched Partition Size - is a normal error when flashing TWRP and can be ignored. It does not mean flashing has failed.
mfastboot is successfully flashing the Android ROM (system.img)​Has anything changed if you let Android boot?

@lost101 :
ADB can be used but when i searched,USB Debugging Enabled seemed to be a per-requisite in almost all cases on XDA and other forums which I can't do right now since no access to settings.
Push,Pull can be used to backup and restore - tried this on an emulator (Bluestacks on PC) which was detected by it (image below).
My driver is :
I'm not sure if it's the right one or not,no way to test it except testing with "adb devices" in command line but fastboot works so i guess it is.
Fastboot works well in the bootloader,it was able to flash all system images including the ROM.
I am not sure whether this device is hard-bricked since i haven't tried the "fastboot erase userdata command".
No change in the Android boot up process - it's the same issue as before.
It took a little more time (5-10 seconds more to arrive at the blank but lit screen as in the video mentioning the problem) after those 4 commands but that was most likely due to stocking the new firmware.
What bothers me is that i am unable to boot into recovery directly or boot into it after flashing.
It shows "boot up failed" even for the flashed recovery.
lost101 said:
@ravibhat - You mention in OP: ADB can be used to backup using PUSH,PULL (may or may not require Android USB Debugging enabled)
When is it working? While the Android is booting up? If so, you could pull the /sdcard/ during that time.
Regarding your previous post:
Mismatched Partition Size - is a normal error when flashing TWRP and can be ignored. It does not mean flashing has failed.
mfastboot is successfully flashing the Android ROM (system.img)​Has anything changed if you let Android boot?
Click to expand...
Click to collapse

There is another command: adb reboot recovery
I am no longer clear. Can you access stock recovery mode? Power on while holding Vol up?

@lost101 :
adb doesn't work as i mentioned since it doesnt detect the device,probably since ADB debugging wasn't enabled.
And i cannot access stock recovery (like previously mentioned in the OP - same issue ) - it gives "boot up failed" error on the device.
These are the commands i can use right now (since only fastboot works) :
I would really like to save the data but if that's really not possible or practical at this point,i'd go for the second best option.
Unlock the bootloader - try flashing custom/stock images or recovery - take backup or use recovery software.
Any suggestions on unlocking the bootloader?

@ravibhat - I was under the impression accessing recovery from boot was different depending on Bootloader version. With v14.18, you power on while holding 'vol up.' With older Bootloaders - it's 'vol down.'

@ravibhat
OK so i have understood what problem you got
Now since you wanna save you data here's what you need to do( if it actually works)
As the system boots up, after 2 or 3( not exact) seconds the data partition is mounted ( this is necessary to boot up OS )
Now can you confirm that adb ( not fastboot) is working while you see the blank screen with backlit active
Report

@ravibhat - If you can boot into Stock Recovery, you can enable 'ADB Sideloading.' You will then be able to ADB pull /sdcard/ to PC.

Hey @lost101,
I am able to boot into the bootloader and use fastboot commands.
But when i select "Recovery" on the bootloader as shown in the image in the above post,it says "boot up failed".
I've flashed stock recovery and it was successful but unable to boot directly using "flash boot recovery.img" or even after successful flashing (by choosing Vol down button to navigate and then Vol Up button to select while in the bootloader)
lost101 said:
@ravibhat - I was under the impression accessing recovery from boot was different depending on Bootloader version. With v14.18, you power on while holding 'vol up.' With older Bootloaders - it's 'vol down.'
Click to expand...
Click to collapse
@sjandroiddeveloper
ADB doesn't detect my device.Is USB Debugging required to be enabled to use ADB ?
I don't have USB debugging enabled (it was disabled by default).
sjandroiddeveloper said:
Now can you confirm that adb ( not fastboot) is working while you see the blank screen with backlit active
Report
Click to expand...
Click to collapse
Yes,i saw a lot of posts suggesting this but unfortunately the device doesn't get detected by ADB,also i don't understand the reason why i can boot into Stock Recovery despite being able to successfully flash it,it always says "booting failed".
lost101 said:
@ravibhat - If you can boot into Stock Recovery, you can enable 'ADB Sideloading.' You will then be able to ADB pull /sdcard/ to PC.
Click to expand...
Click to collapse

Nougat Moto Z on at&t mexico (this may be compatible with more models)

Greetings,
Just sharing this info, if you install verizon stock firmware on at&t iusacell Mexico, you will be able to update till nougat. I already tried with success, you just need unlocked bootloader and the moto z verizon stock firmware (wich is on this forum).
Wold like to upload a photo but i dont know how.
Flashing stock verizon will not relock your bootloader, and you will get the 2.2 ghz cpu and 610 mhz gpu from verizon rom.
You willl find the software at:
http://forum.xda-developers.com/moto...loads-t3449837
Choose the verizon version. You may also search:
"XT1650_GRIFFIN_VERIZON_MCL24.203-22_cid2_subsidy-DEFAULT_CFC.xml.zip"
on google for improved download speeds.
After you downloaded the firmware, flasht it over fastboot.
You may try this instructions over cmd to flash it (just like i did):
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 logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot reboot
after that:
- Let the phone make the first boot (your may signup with with your google account, because you will not loose the information over the updates)
- Go to settings and search for updates
- Keep updating till Nougat (think i updated the phone like 3 times, till it get to Nougat).
- Enjoy

will flashing verizon rom relock your bootloader ?
and which verizon rom did u flash - can u link to the message ?

reiteravi said:
will flashing verizon rom relock your bootloader ?
and which verizon rom did u flash - can u link to the message ?
Click to expand...
Click to collapse
Flashing stock verizon will not relock your bootloader, and you will get the 2.2 ghz cpu and 610 mhz gpu from verizon rom.
You willl find the software at http://forum.xda-developers.com/moto-z/development/moto-z-official-firmware-downloads-t3449837
Choose the verizon version. You may also search "XT1650_GRIFFIN_VERIZON_MCL24.203-22_cid2_subsidy-DEFAULT_CFC.xml.zip" on google for improved download speeds.
imagen jpg

And... By the way, no bugs at all.
- ALL MODS WORKING
- CALLING WORKING
- WIFI, DATA WORKING
been using it on my moto z almost 12 hours without any crash or issue at sight

Thanks man
i have this file
how did u flash it ? using twrp ?

U think works on two sim mexican moto z?

reiteravi said:
Thanks man
i have this file
how did u flash it ? using twrp ?
Click to expand...
Click to collapse
I flash it using fastboot commands, if you want it i will upload the full instructions, just hold me 2 hours, im far from my computer and i dont wanna write the flash file again xD.
estanenmi said:
U think works on two sim mexican moto z?
Click to expand...
Click to collapse
I think it will works on any moto z, but if anything goes wrong you may reflash the stock retail mexican rom again (cause you buy it directly from motorola, isnt?) .

90dfx said:
Greetings,
Just sharing this info, if you install verizon stock firmware on at&t iusacell Mexico, you will be able to update till nougat. I already tried with success, you just need unlocked bootloader and the moto z verizon stock firmware (wich is on this forum).
Wold like to upload a photo but i dont know how.
Click to expand...
Click to collapse
Have you "Verizon flashers" doublechecked if the supported LTE bands are reduced this way?
Verizon's models support a lot less bands than international models...

enetec said:
Have you "Verizon flashers" doublechecked if the supported LTE bands are reduced this way?
Verizon's models support a lot less bands than international models...
Click to expand...
Click to collapse
Yes, i know this is something really strange, but.... It works! 4g lte! No issue at all.
It's a kind of contradictorious stuff, verizon rom being compatible and useful for anothers xD
{
"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"
}

90dfx said:
Yes, i know this is something really strange, but.... It works! 4g lte! No issue at all.
It's a kind of contradictorious stuff, verizon rom being compatible and useful for anothers xD
Click to expand...
Click to collapse
Yes, but check how many of them are still supported using Network Signal Guru...

Sorry, dont know how to use that tool :/ why dont you try it and see??
By the way, day dream crash after welcome screen... But i think this is something related to the app, because thats the only crash i had on 24 hours using this rom

Worked like a charm on my Bell Moto Z up here in Canada. Now all we need to do is unencrypt the storage and get root
EDIT - Went back to stock 6.0.1 worked ok, then for some reason I cannot boot now into any type of rom or software. The only thing I can think of are these three commands did something?
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
I've never used those on any other rom or going back to stock in Fastboot ever before.

Happened to me the same a few hours back.
Cant go back to 6.0, its something related to nougat partitions.
Only way to boot is installing nougat again and thats is installling last update from verizon before nougat:
https://drive.google.com/open?id=0ByioJuadKHC6MjJDXzhJSXlBaDA
And them install the OTA to nougat over stock recovery using adb sideload from your pc.
Thats how i did and finally boot. Lets see if someone find some workaround to this issue

90dfx said:
Sorry, dont know how to use that tool :/ why dont you try it and see??
...
Click to expand...
Click to collapse
No way...!
If you want to check you have to: start Network Signal Guru, grant root, press magic wand, then select bands locking, then LTE... you will see all the LTE bands supported by phone at the moment. Then *cancel* and select Exit on three dot menu.
Simple enough?

enetec said:
No way...!
If you want to check you have to: start Network Signal Guru, grant root, press magic wand, then select bands locking, then LTE... you will see all the LTE bands supported by phone at the moment. Then *cancel* and select Exit on three dot menu.
Simple enough?
Click to expand...
Click to collapse
Well.. it sounds easy but how do i root, to grant permission
Tried with turbo kernel to disable encryption and them installing supersu(system mode) (just booting from twrp), but it doesn't boot... And it takes like age's to get it back to a bootable nougat xD

90dfx said:
Well.. it sounds easy but how do i root, to grant permission
Tried with turbo kernel to disable encryption and them installing supersu(system mode) (just booting from twrp), but it doesn't boot... And it takes like age's to get it back to a bootable nougat xD
Click to expand...
Click to collapse
Try like it worked on MM: disable encryption (fully, not only by flashing kernel or patch...), flash Magisk v.9 and then SuperSU official/stock v.2.78... (NOT forced 2 system one...)
Reboot to system after every step...

Hi guys I just wanna to say it's really dangerous to flash Verizon OTA on non Verizon device
Because on this OTA and firmware we have some images like partition (gpt), modem and other firmwares like Bluetooth..
This may affect on your device modem.
Personally i suggest you guys not to install it on your devices and I have only one request to who did this and got nought on unlocked device.
Please get system image and boot partition backup with TWRP and share it to public or me.
I promise I'll create flashable zip to not flash modem and gpt, .. for safety
And you can back to marshmallow whenever you want
Thanks a lot

I 100% agree...

estanenmi said:
U think works on two sim mexican moto z?
Click to expand...
Click to collapse
Yes. You can flash any system of any version because the hardware is the same. You will lose two SIM options because ia software related and Verizon only has one SIM version. My advice is not to flash this because maybe you won't be able to use two SIM in the future. And I think that Verizon and AT&T are only 32 GB not 64 like the unlock versions.
Sent from my XT1650 using XDA-Developers mobile app

enetec said:
Try like it worked on MM: disable encryption (fully, not only by flashing kernel or patch...), flash Magisk v.9 and then SuperSU official/stock v.2.78... (NOT forced 2 system one...)
Reboot to system after every step...
Click to expand...
Click to collapse
How did you disable encryption?... Flashing boot image and them wipe data, dalvik and cache?...
Would like to try it but dont i dont think it will work cause that was the boot image of marshmallow, and feel to much lazy to recover a brickphone xD..... So maybe at weekend xD
erfanoabdi said:
Hi guys I just wanna to say it's really dangerous to flash Verizon OTA on non Verizon device
Because on this OTA and firmware we have some images like partition (gpt), modem and other firmwares like Bluetooth..
This may affect on your device modem.
Personally i suggest you guys not to install it on your devices and I have only one request to who did this and got nought on unlocked device.
Please get system image and boot partition backup with TWRP and share it to public or me.
I promise I'll create flashable zip to not flash modem and gpt, .. for safety
And you can back to marshmallow whenever you want
Thanks a lot
Click to expand...
Click to collapse
Sure, no problem but yesterday after flashed and use twrp, my moto z didnt boot. Do you think that if i just "boot" (fastboot boot twrp.img) i will be able to boot after made the backup?

[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.