Hi, this is my first time making a post, ok here's the thing, a couple of days ago my phone run out of battery, when i come back to charge the phone, this just get stuck in the Motorola logo and don´t turn on, i never make nothing like root or flashing roms, the phone os was all stock Android 5.1; so i look in the internet for possible cause and i find that it was a bootloop, i try to get in to the fastboot flash mode to make a reset with the factory option but just get directly to the motorola logo and dont do nothing, so a try with the recovery option and gets in to the android system recovery <3e> and try the wipe data/factory reset but doesn´t work. I try even via computer using the minimal adb and fastboot to erase the cache and the userdata with the commands and doesn't work, still appearing the motorola logo. so i found that i have to install the original rom again but first ill have to unlock the bootloader for my device, so i did it, i unlock the bootloader and now appear <Device is UNLOCKED. Status Code: 3> and now appear the poster WARNING BOOTLOADER UNLOCKED instead of the motorola logo; then i search for the stock rom for my device and i find this one XT1040_PEREGRINE_RETBR_5.1_LPB23.13-8_cid12_CFC.xml.zip (i know that my device is peregrine because i remember saw it before in the settings but not remeber the hole name), so i make the installation with adb tools like the post say and make this commands:
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 system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
when its over i press fastboot reboot, but then appears again the WARNING BOOTLOADER UNLOCKED poster, i try to make it again, bus still appearing, i try more than 10 times, but still appearing.
sorry if the post is too large but i try to explain everything so you guys can help me because im desesperate with this, thanks.
HanSolo97 said:
Hi, this is my first time making a post, ok here's the thing, a couple of days ago my phone run out of battery, when i come back to charge the phone, this just get stuck in the Motorola logo and don´t turn on, i never make nothing like root or flashing roms, the phone os was all stock Android 5.1; so i look in the internet for possible cause and i find that it was a bootloop, i try to get in to the fastboot flash mode to make a reset with the factory option but just get directly to the motorola logo and dont do nothing, so a try with the recovery option and gets in to the android system recovery <3e> and try the wipe data/factory reset but doesn´t work. I try even via computer using the minimal adb and fastboot to erase the cache and the userdata with the commands and doesn't work, still appearing the motorola logo. so i found that i have to install the original rom again but first ill have to unlock the bootloader for my device, so i did it, i unlock the bootloader and now appear <Device is UNLOCKED. Status Code: 3> and now appear the poster WARNING BOOTLOADER UNLOCKED instead of the motorola logo; then i search for the stock rom for my device and i find this one XT1040_PEREGRINE_RETBR_5.1_LPB23.13-8_cid12_CFC.xml.zip (i know that my device is peregrine because i remember saw it before in the settings but not remeber the hole name), so i make the installation with adb tools like the post say and make this commands:
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 system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
when its over i press fastboot reboot, but then appears again the WARNING BOOTLOADER UNLOCKED poster, i try to make it again, bus still appearing, i try more than 10 times, but still appearing.
sorry if the post is too large but i try to explain everything so you guys can help me because im desesperate with this, thanks.
Click to expand...
Click to collapse
If your goal is to re-lock the bootloader: try the command: fastboot oem lock
However, I don't see that solving your problem and may compromise your ability to restore to stock. Instead check this link and follow the install directions EXACTLY:
http://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
eg. for Canada choose: XT1040 (Note: for Rogers/Fido - confirmed)
Retail Canada 5.1 ROM (Untouched) (531mb) [Download]
i.e., you want the untouched version for your specific region.
Good luck. S
Hello everyone, i have big problem with my new motorola x force, i bought it with dead software. And i tried install new, (I'm doing it isnt first time). I get key for unlock from motorola service but is imposible. I get an error. This device can not be unlocked.
I guess first owner, forgot turn on develop mode.
Any idea? I'm tried flashing it with instructions from other thread https://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515.
I download soft from motorola, I'm tried first ver. android and new one. Everything without result.
Rasah97 said:
Hello everyone, i have big problem with my new motorola x force, i bought it with dead software. And i tried install new, (I'm doing it isnt first time). I get key for unlock from motorola service but is imposible. I get an error. This device can not be unlocked.
I guess first owner, forgot turn on develop mode.
Any idea? I'm tried flashing it with instructions from other thread https://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515.
I download soft from motorola, I'm tried first ver. android and new one. Everything without result.
Click to expand...
Click to collapse
You do not need to unlock the bootloader to flash original moto firmware
Just put it in bootloader mode and on your pc where you have fastboot and all the firmware files open a command/terminal prompt and type the following
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img (not all devices have this)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk0 (flash all sparsechunks in number order - for example)
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
TheFixItMan said:
You do not need to unlock the bootloader to flash original moto firmware
Just put it in bootloader mode and on your pc where you have fastboot and all the firmware files open a command/terminal prompt and type the following
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img (not all devices have this)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk0 (flash all sparsechunks in number order - for example)
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
Sure, but When i done it phone starting with Motorola logo and restarting, I didn't have this file img with nr 1/4 I mean this fastboot flash system system.img_sparsechunk4
I download soft from Motorola, I don't remember version but it like 5.1? Middle one from list and in another one first vet same
Rasah97 said:
Sure, but When i done it phone starting with Motorola logo and restarting, I didn't have this file img with nr 1/4 I mean this fastboot flash system system.img_sparsechunk4
I download soft from Motorola, I don't remember version but it like 5.1? Middle one from list and in another one first vet same
Click to expand...
Click to collapse
Some phones may not have sparsechunks 0 & 4 - as long as you flash all the ones in the firmware in number order
I don't have your phone so I couldn't tell you what firmware to use
I have Motorola g5 so I can just tell you the process
And looking on that firmware thread it says you need to use mfastboot for system images - so see that thread for details
Long as everything is flashed successfully in the order I have written above including erasing user data
Sooo.... Could you tell me which comand i have to use ?
Related to no sim card issue?
I'm wondering if this is related to a problem I am having with mine phone. I flashed the official firmware (6.0) on my moto x force and everything works but the simcard. It says it's not loaded so I have no phone or cell data. My sim card works in other moto phones so its not that.
All,
I successfully updated my Moto G Stylus (2021) [RETUS / XT2115-1] with the following fastboot commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.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 dtbo dtbo.img
fastboot flash recovery recovery.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 flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot flash super super.img_sparsechunk.16
fastboot erase carrier
fastboot erase userdata [optional]
fastboot erase metadata
fastboot erase ddr
fastboot flash boot <name of magisk patched boot file.img> [optional]
fastboot oem fb_mode_clear
fastboot reboot
I downloaded the latest firmware from the Moto Rescue and Smart Assistant PC application.
Enjoy!
Caution: The flash commands can vary from one Software Channel to another, and the number sparsechunk(s) can change with the android versions.
You should always use the flashfile.xml or service.xml to get the flash commands.
Several ways to do that.
Online FlashFile Converter
Write a Batch File
XML to Bat Converter Tool for Windows
More here
[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:
.....
You should always use the flashfile.xml or service.xml to get the flash commands.
.....
Click to expand...
Click to collapse
I like using Notepad++ to view a flashfile.xml from the extracted firmware. Right-click and open with, it formats it very nicely.
peajul said:
I successfully updated my Moto G Stylus (2021) [RETUS / XT2115-1] with the following fastboot commands: ...
Click to expand...
Click to collapse
Just curious, this was an actual "update"? OTA? Or did you just refresh a current install? Do you have a version number? I'm gonna plug-in to the MRSA app as soon as I can get my hands on my lady's phone, but I'm asking so I can be prepared for what I might find.
peajul said:
All,
I successfully updated my Moto G Stylus (2021) [RETUS / XT2115-1] with the following fastboot commands.....
Click to expand...
Click to collapse
Your list and order does match perfectly (except for the added Magisk-patched bootloader) with the flashfile.xml in my downloaded copy of XT2115-1_MINSK_RETUS_10_QPC30.Q4-31-26-1.
. . . I'm needing to reflash my lady's Stylus 2021, is why I went so far as to check in detail. Apparently I screwed up in manually copying the blocked numbers database from an older version of Android to her new XT2115-1. Something in Android 10 just doesn't like what I did (same thing I've done between Nougat and Pie with no problems at all). And then I further mangled the situation trying to fix it.
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.