Develop Bugs

Help on bootloop Moto G5

Hi guys I got bootloop in my moto g5. First I got "failed to mount /data", now the phone boots in unlocked warning screen then says "erasing" then reboots and start over again.
Before the procedure my actions was:
- I got OTA update
- inserted a microSD
- unlocked bootloader
- boot on TWRP 3.1.0
- backup to microSD
-install TWRP
as shown by bootloader screen, my model is "cedric XT1672 32GB P5", M8937_8000.122.02.45R CEDRIC_BRAZILDSDS_CUST.
What I don't understand is why TWRP don't restore, as a made a backup before the procedure.
I appreciate if somebody could help me out!

I had the same problem. Wiping /data corrupted my partition table or system partition.
You need to flash the system and / or the partition table via fastboot from the extracted stock rom (see the other thread arround here, make sure you use the right link (cedric, not the potter one)
-> boot to fastboot
fastboot flash system system.sparsechunk.0
fastboot flash system system.sparsechunk.1
...
It should boot normally afterwards, but probably twrp is gone / twrp has no access to your /data again. See the twrp thread, i'm facing the same issue. But at least the phone works again - without root
Greetings,
Chris

-> boot to fastboot
fastboot flash system system.sparsechunk.0
fastboot flash system system.sparsechunk.1
Click to expand...
Click to collapse
Did not work for me!

I hope you flashed all the system files?
Otherwise try to flash the full stock rom via fastboot. There are tons of guides explaining

Help NPP25.137-33 It doesn't work filefactory
.sirhc said:
I hope you flashed all the system files?
Otherwise try to flash the full stock rom via fastboot. There are tons of guides explaining
Click to expand...
Click to collapse
Help with stock NPP25.137-33 someone who has it in google driver to download

Got it back I, like you said! The first time I think I got any of those system file corrupted!!
I just dont know until when it gonna be good cos I am going to root this s.. now!
thks

linsspinho said:
Got it back I, like you said! The first time I think I got any of those system file corrupted!!
I just dont know until when it gonna be good cos I am going to root this s.. now!
thks
Click to expand...
Click to collapse
// already found how to root. won't do it right now as there are no success stories

TWRP 3.2.3-1 for Pixel 2 XL

Note: Do not use if you have multiple users (including a guest user)
Lots more information here: https://plus.google.com/u/1/+DeesTroy/posts/i33ygUi7tiu
I strongly recommend that kernel developers start building the touch drivers into the kernel instead of depending on modules to ensure a fully functional TWRP since recovery is now part of the boot partition.
Be careful about what you install on your device as far as kernels and ROMs go. I think there is a high potential for losing the ability to decrypt because of the OS and patch level tags that are included in the boot image and the anti-rollback features that Google has implemented.
MTP does not work in TWRP on the Pixel 2 and will not work until we have time to update the TWRP MTP implementation. You may still use adb to push and pull files.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, you will need to reflash root.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
Pixel 2:
https://twrp.me/google/googlepixel2.html
https://dl.twrp.me/walleye/
Pixel 2 XL:
https://twrp.me/google/googlepixel2xl.html
https://dl.twrp.me/taimen/

Reserved!

Awesome to see the progress here, thank you for working on it and dealing with all the impatient requests. Will definitely be keeping an eye on this thread ?

Hurray for progress!

fastboot boot /path/to/twrp.img reboots into TWRP, but it never goes past the teamwin splash screen. I am able to reboot the phone normally after that, so no biggie.
I don't have time now to mess with figuring out how to get you logs, but I'll do that later this evening. Just wanted to give you a quick "what happened when I tried it."
And THANK YOU for working on this for us so quickly!
Edit: The logs are posted here:
https://forum.xda-developers.com/pixel-2-xl/development/twrp-alpha-pixel-2-xl-t3698148/post74363478

This makes me smile. Thanks Troy and TeamWin!

Thanks Dees_Troy and Team for getting this started!

Things are looking up, thanks guys!

Awesome to see action with this phone! Thanks!!

You da man

sharkie405 said:
fastboot boot /path/to/twrp.img reboots into TWRP, but it never goes past the teamwin splash screen. I am able to reboot the phone normally after that, so no biggie.
I don't have time now to mess with figuring out how to get you logs, but I'll do that later this evening. Just wanted to give you a quick "what happened when I tried it."
And THANK YOU for working on this for us so quickly!
Click to expand...
Click to collapse
Here are those logs.

Nice! Great to see the progress

Thanks for the progress guys. Has anyone tried flashing root from TWRP yet? I wonder if this process would work, if we used this modded TWRP... https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324

sharkie405 said:
Here are those logs.
Click to expand...
Click to collapse
Did you try unlocking critical?

cwalker0906 said:
Did you try unlocking critical?
Click to expand...
Click to collapse
Yes, I've already unlocked critical.
Sent from my Pixel 2 XL using XDA Labs

Great to see...this is the start!

I unlocked the bootloader without critical and was able to bootloader into twrp. No just figuring out a way to get root.

bggold said:
I unlocked the bootloader without critical and was able to bootloader into twrp. No just figuring out a way to get root.
Click to expand...
Click to collapse
From here we should be able to push ADB shell comands to edit build.prop right?

I just fastboot booted your .img. All functioning as expected except for the issues that you indicated.
Rebooted back to system without any issues.
Thank You Great Job!

chazall1 said:
I just fastboot booted your .img. All functioning as expected except for the issues that you indicated.
Rebooted back to system without any issues.
Thank You Great Job!
Click to expand...
Click to collapse
Have you unlocked critical?
Sent from my Pixel 2 XL using XDA Labs

[FIRMWARE][GUIDE] MetroPCS/T-Mobile XT1765 Moto E4 Firmware Flashing Guide

•••••• Qualcomm Moto E (4th Gen) Perry ••••••
Factory Firmware & Flashing/Restoration Guide
MetroPCS / T-Mobile Moto E4 (XT1765)
OVERVIEW:
This guide provides factory firmware for both the MetroPCS and T-Mobile branded variants of the Moto E4 Perry (xt1765). While these two packages appear to be similar and multi-compatible, I do not own the xt1765 and cannot confirm this. So, to be safe, use only the firmware package for your branded carrier. This guide can be used to repair a device which is buggy, unstable, or stuck in a boot loop. Likewise, device owners wishing to restore their device to an unmodified, stock factory state will also find this guide beneficial. Installing this firmware will remove any custom mods from your device, such as root binaries, BusyBox binaries, Xposed framework, etc. Also, force encryption and verified boot (dm-verity/avb) will be enabled. If you have TWRP custom recovery installed, it will be replaced by the stock recovery image.
DISCLAIMER:
You are using this guide and flashing firmware to your device solely at your own risk. While these firmwares have been tested and confirmed to work on their respective variants, by proceeding further, you are absolving me of any liability or responsibility in the event you brick your device or otherwise render it inoperable. Follow the simple instructions carefully and things should go smoothly.
SPECIFICATIONS:
••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
•MetroPCS Moto E4 (xt1765) Perry
•Android Version: 7.1.1 Nougat
•Build No. NCQS26.69-64-3
•System Version: 26.261.9.perry_metropcs.en.US
•Radio Version: M8917TMO_18.08.04.18R
•Security Patch Level: March 1, 2018
•Kernel Version: Linux 3.18.31-perf
•Build Date: March 16, 2018
•Firmware Package Size: 1.36 GB
•Download Link: https://drive.google.com/file/d/17sJS8VpxSAHupqiqJQQb4wa1jHIP61uT/view?usp=drivesdk
•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
•T-Mobile Moto E4 (xt1765) Perry
•Android Version: 7.1.1 Nougat
•Build No. NCQS26.69-64-6
•System Version: 26.271.7.perry_tmo.tmo.en.US
•Radio Version: M8917TMO_18.08.04.18.01R
•Security Patch Level: May 1, 2018
•Kernel Version: Linux 3.18.31-perf
•Build Date: May 2, 2018
•Firmware Package Size: 1.33 GB
•Download Link: https://drive.google.com/file/d/1C21fgdBVn6hhPtAo5yult-PdB6DSr4HS/view?usp=drivesdk
•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
REQUIREMENTS:
This guide assumes that you have the latest version of the Minimal ADB & Fastboot utilities installed on your PC or laptop. If you do not, you can download the latest version, v1.4.3, from this MediaFire link: http://www.mediafire.com/file/ccnnv843a20tqbn/minimal_adb_fastboot_v1.4.3.zip It is also a good idea to have at least a rudimentary understanding of fastboot command line execution. There are some excellent guides here on XDA which outline the subjects of fastboot mode & fastboot commands.
In addition, to ensure that up-to-date USB device drivers are installed on your PC, download & install the latest Motorola Device Manager. You can get the latest version directly from this Motorola support link: https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222
NOTE:
Because these are factory firmware packages, in theory, xt1765 owners should be able to flash these packages, using the below instructions, to devices with a locked bootloader. Please note, however, that these firmwares were leaked by the manufacturer and may or may not be digitally signed by the OEM. In sum, I cannot confirm whether these firmwares will flash to a locked bootloader device. I can only confirm that the firmware will install normally on a device with an unlocked bootloader. As confirmation becomes available from other members in this regard, I will add the info to this thread.
On a second note, flashing this factory firmware does not re-lock an already unlocked bootloader. Also, contrary to popular misbelief, re-locking your bootloader IS NOT required in order for your device to be able to install OTA update packages. To enable your device to install OTA updates, you need only install the firmware package for your variant using the below instructions.
WARNING: The below instructions include a command for wiping your /userdata partition (fastboot erase userdata) which will effectively wipe all of your saved files, photos, videos, app data and other media. This is recommended for a clean install of the firmware, and to ensure optimal results. However, if you are stuck in a boot loop, for example, and have important files saved to internal storage that you want to try and salvage, simply skip over the "fastboot erase userdata" command and give it a try.
INSTRUCTIONS:
• 1. Download the firmware package for your branded carrier on your PC or laptop. Extract the contents of the package to your ADB/Fastboot directory;
• 2. Boot your device into fastboot mode and connect your device to your PC with the OEM or a quality equivalent micro USB to USB sync cable;
• 3. Open a command window in the path of your ADB/Fastboot directory and execute:
fastboot devices
If your device and PC are properly connected, the command window will return an alphanumeric value synonymous of your device serial number;
• 4. Once a proper connection has been established, execute the following commands, preferably in this order:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot oem fb_mode_clear
Done. Now execute:
fastboot reboot
Upon reboot, your device should be restored to unmodified stock condition, and your device will be capable of installing pending or future OTA update packages.

Thanks for posting this! Looks very comprehensive and nOObproof.... I'm going to try this out in the next few days and I will report back if I had any trouble following the instructions and let your know if I feel anything needs to be clarified. I don't foresee having any problems with this though. I appreciate you and your hard work to put this together

AesopRock127 said:
Thanks for posting this! Looks very comprehensive and nOObproof.... I'm going to try this out in the next few days and I will report back if I had any trouble following the instructions and let your know if I feel anything needs to be clarified. I don't foresee having any problems with this though. I appreciate you and your hard work to put this together
Click to expand...
Click to collapse
No problem. I've been reading a lot of posts of members needing more up-to-date xt1765 stock firmware, so I hope it helps some members. These are the same instructions and structural format that I use on all of my Moto/Lenovo firmware threads. The order of the command lines are set out exactly the same as those used in certified Motorola/Lenovo service centers. If you follow the instructions to the letter, there is no doubt that you'll have your device fully restored to stock factory condition.

When I have the time to do so, I'll use these firmwares with my Android Kitchen to cook up TWRP flashable stock ROMs for the MetroPCS & T-Mobile xt1765 models.

MotoJunkie01 said:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
My question is if i want to keep twrp as my recovery is it as simple as not running the command fastboot flash recovery recovery.img?

AesopRock127 said:
My question is if i want to keep twrp as my recovery is it as simple as not running the command fastboot flash recovery recovery.img?
Click to expand...
Click to collapse
Yes. It is that simple. Just be advised that an OTA will not install normally unless stock recovery is in place. The OTA installation script runs checksums for stock recovery.
The best policy is to flash the firmware in full, install any pending OTAs while running unmodified stock, then reinstall TWRP once you're up to date on the latest firmware build.

MotoJunkie01 said:
Yes. It is that simple. Just be advised that an OTA will not install normally unless stock recovery is in place. The OTA installation script runs checksums for stock recovery.
The best policy is to flash the firmware in full, install any pending OTAs while running unmodified stock, then reinstall TWRP once you're up to date on the latest firmware build.
Click to expand...
Click to collapse
Shiiiiiit I didn't think about that I have an update I'm going to try to do it if it doesn't work guess I'll redo the full process all over again..... By the way I pmd you
EDIT: 69-64-6 updated no problem And immediately offered me 69-64-9 so maybe these updates aren't large enough to worry about twrp instead of stock recovery? Only time will tell I guess
Sent from my Motorola XT1765 using XDA Labs

AesopRock127 said:
Shiiiiiit I didn't think about that I have an update I'm going to try to do it if it doesn't work guess I'll redo the full process all over again..... By the way I pmd you
EDIT: 69-64-6 updated no problem And immediately offered me 69-64-9 so maybe these updates aren't large enough to worry about twrp instead of stock recovery? Only time will tell I guess
Click to expand...
Click to collapse
To simplify things, just keep installing OTAs until you are on the current build. Then, reinstall TWRP. You shouldn't have to redo the whole thing as long as you haven't mounted system as r/w in TWRP. And as long as you haven't flashed Magisk or SuperSU for root. Just reboot into fastboot and flash the stock recovery and OTAs should be fine.

so i know im a pain in the ass but i followed this guide with no issues and updated fully before installing twrp and root and then couldnt install xposed and ran into a bootloop so decided to go nuclear and start over. My only issue now is after fully following this guide again my OTA updates are failing in stock recovery and when i reboot i get tons of tmobile and moto app FC issues and it says im fully updated even though i started on 69-64-3 and it failed in stock recovery it still says im on 69-64-6 and ive been on 69-64-9 before so not only do i know im not fully updatedd but these FC are driving me nuts. Trying again but does anyone have any clues what could be causing my issues? im having a lot of problems with noverity flashing right and getting the newest twrp to flash instead of only temp boot as well and i feel these issues are all cnnected somehow. I might go back to RR if possible because i was able to get my phone the way i wanted on there for the most part im not sure why stock is giving me such issues? Unfrotunately i cant provide any logs or anything because i am retrying this guide again and see how it goes and didnt think until after the fact to post this

AesopRock127 said:
so i know im a pain in the ass but i followed this guide with no issues and updated fully before installing twrp and root and then couldnt install xposed and ran into a bootloop so decided to go nuclear and start over. My only issue now is after fully following this guide again my OTA updates are failing in stock recovery and when i reboot i get tons of tmobile and moto app FC issues and it says im fully updated even though i started on 69-64-3 and it failed in stock recovery it still says im on 69-64-6 and ive been on 69-64-9 before so not only do i know im not fully updatedd but these FC are driving me nuts. Trying again but does anyone have any clues what could be causing my issues? im having a lot of problems with noverity flashing right and getting the newest twrp to flash instead of only temp boot as well and i feel these issues are all cnnected somehow. I might go back to RR if possible because i was able to get my phone the way i wanted on there for the most part im not sure why stock is giving me such issues? Unfrotunately i cant provide any logs or anything because i am retrying this guide again and see how it goes and didnt think until after the fact to post this
Click to expand...
Click to collapse
Follow the instructions exactly, but avoid gpt.bin and bootloader.img. Those will fail as they are supposed to, so no need in trying them. Otherwise you should be fully stock on reboot and your device should install OTAs normally.
If that particular problem persists, file corruption within the firmware package could be the culprit. Try downloading the firmware again (delete the other from your PC) and start over from scratch.

MotoJunkie01 said:
Follow the instructions exactly, but avoid gpt.bin and bootloader.img. Those will fail as they are supposed to, so no need in trying them. Otherwise you should be fully stock on reboot and your device should install OTAs normally.
If that particular problem persists, file corruption within the firmware package could be the culprit. Try downloading the firmware again (delete the other from your PC) and start over from scratch.
Click to expand...
Click to collapse
Ok thanks. I will try redownloading if it persists but is there any log or anything that would help out in identifying the problem if it still persists after a redownloading of the firmware? It's annoying that stock recovery says error! With no code to help identify the issue

AesopRock127 said:
Ok thanks. I will try redownloading if it persists but is there any log or anything that would help out in identifying the problem if it still persists after a redownloading of the firmware? It's annoying that stock recovery says error! With no code to help identify the issue
Click to expand...
Click to collapse
When stock recovery says ERROR during installation of an OTA, the problem is with the checksums. In other words, the OTA installer is telling stock recovery that you are not running an unmodified stock setup. You can get an error like that from just mounting /system or /oem as r/w. The installer checks your /boot, /recovery, /system and /oem partitions to make sure they are untouched, unmodified stock.

Also, @AesopRock127, there is a quicker and simpler method to install stock firmware to a Moto/Lenovo device called RSD Lite. You can Google for the basic instructions.
Here's a link to RSD Lite v6.2.4: https://drive.google.com/file/d/1MwZPdifKVpR4ZTsE3SSNAFBNr6KU29wY/view?usp=drivesdk

MotoJunkie01 said:
Also, @AesopRock127, there is a quicker and simpler method to install stock firmware to a Moto/Lenovo device called RSD Lite. You can Google for the basic instructions.
Here's a link to RSD Lite v6.2.4: https://drive.google.com/file/d/1MwZPdifKVpR4ZTsE3SSNAFBNr6KU29wY/view?usp=drivesdk
Click to expand...
Click to collapse
Okay so I redid this and the updates are sticking like you said I must have changed something and made it non-stock.... So I do not need the RSD Lite as of yet but I did download it. Looking into it it seems that I may use it to root my device when I get to that point? For now I'm just setting everything up the way I like it and fully intalling stock updates before I get into TWRP and rooting. The goal is a up to date stock, rooted, debloated, and running Xposed and gravitybox. Last time everything went smoothly until I hit xposed. I think it's due to my crappy understanding of selinux permissions, encryption and dm verity.... The best thing about struggling to install stuff like this is it gives you an opportunity to learn. In the past I've been able to follow guides and everything worked as stated so I had no need to get technical and delve into some of the things I've needed to on my xt1765. Thank God for XDA and helpful people like @MotoJunkie01 or I would have hit this phone with a Sledge hammer or chop it in half with a chop saw like I did with the Samsung j3 ?

AesopRock127 said:
Okay so I redid this and the updates are sticking like you said I must have changed something and made it non-stock.... So I do not need the RSD Lite as of yet but I did download it. Looking into it it seems that I may use it to root my device when I get to that point? For now I'm just setting everything up the way I like it and fully intalling stock updates before I get into TWRP and rooting. The goal is a up to date stock, rooted, debloated, and running Xposed and gravitybox. Last time everything went smoothly until I hit xposed. I think it's due to my crappy understanding of selinux permissions, encryption and dm verity.... The best thing about struggling to install stuff like this is it gives you an opportunity to learn. In the past I've been able to follow guides and everything worked as stated so I had no need to get technical and delve into some of the things I've needed to on my xt1765. Thank God for XDA and helpful people like @MotoJunkie01 or I would have hit this phone with a Sledge hammer or chop it in half with a chop saw like I did with the Samsung j3 ?
Click to expand...
Click to collapse
That's good news. I intend on making a TWRP flashable stock ROM for the xt1765 in the very near future. Once you are on the latest stock build, if you could make a TWRP backup of your system image and boot image and upload them, I could use the images to cook up an up-to-date stock ROM for the xt1765.

MotoJunkie01 said:
That's good news. I intend on making a TWRP flashable stock ROM for the xt1765 in the very near future. Once you are on the latest stock build, if you could make a TWRP backup of your system image and boot image and upload them, I could use the images to cook up an up-to-date stock ROM for the xt1765.
Click to expand...
Click to collapse
Absolutely. will do this ASAP. Seems best if I do nothing except boot into TWRP and make the backup? Or can I flash it and it will still work? Basically is the stock recovery needed or can I flash TWRP before I make the backup
so system and boot only or system, system image, and boot? making one now with both systems and one with just normal system since im not sure which you need and dont want to give you to much **** to sift through. also does data need to be decrypted for this to be helpful to you? sorry dont know much about it but am willing to help lol

AesopRock127 said:
Absolutely. will do this ASAP. Seems best if I do nothing except boot into TWRP and make the backup? Or can I flash it and it will still work? Basically is the stock recovery needed or can I flash TWRP before I make the backup
so system and boot only or system, system image, and boot? making one now with both systems and one with just normal system since im not sure which you need and dont want to give you to much **** to sift through. also does data need to be decrypted for this to be helpful to you? sorry dont know much about it but am willing to help lol
Click to expand...
Click to collapse
System image and boot backup with TWRP. Encryption of data isn't relevant to the backups. Whether you boot into TWRP or flash TWRP ....either will work

@MotoJunkie01 Nanodroid backup of encrypted fully uptodate stock system and boot.img only https://ufile.io/b0x6q
uploading the one with the system image too

MotoJunkie01 said:
Follow the instructions exactly, but avoid gpt.bin and bootloader.img. Those will fail as they are supposed to, so no need in trying them. Otherwise you should be fully stock on reboot and your device should install OTAs normally.
If that particular problem persists, file corruption within the firmware package could be the culprit. Try downloading the firmware again (delete the other from your PC) and start over from scratch.
Click to expand...
Click to collapse
Also verify checksums (MD5, SHA-1, etc) when offered. Fastest way to validate large file integrity. As a matter of practice I never flash critical partitions sans checksum validation.

Davey126 said:
Also verify checksums (MD5, SHA-1, etc) when offered. Fastest way to validate large file integrity. As a matter of practice I never flash critical partitions sans checksum validation.
Click to expand...
Click to collapse
Excellent point. A corrupt flash to a critical partition can equal lights out -- the proverbial hard brick.

Reboot to recovery: "the system has been destroyed"

Hi
I followed this guide to root my son's phone
(the bootloader was already unlocked or so I tought - see below)
Now when I tried to reboot to twrp to root the phone, following these instructions in the guide:
“How To Root Mi A2 / A2 Lite Using Magisk
…
Now, boot your Xiaomi device into the TWRP Recovery Mode by pressing and holding the Volume Up and Power buttons simultaneously for a couple of seconds until the device starts booting.
…”
Click to expand...
Click to collapse
it does not boot to TWRP but instead displays a red error triangle with the message“The system has been destroyed”; I get exactly the same message after using the adb command
Code:
adb reboot recovery
as an alternative reboot-to-recovery method.
Reboot to system is perfectly fine!
Help anyone? Could it be the bootloader was not properly unlocked... I dit it when I received the phone and wa spretty sure it was unlocked then
Thanks

BenG7 said:
Hi
I followed this guide to root my son's phone
(the bootloader was already unlocked or so I tought - see below)
Now when I tried to reboot to twrp to root the phone, following these instructions in the guide:
it does not boot to TWRP but instead displays a red error triangle with the message“The system has been destroyed”; I get exactly the same message after using the adb command
as an alternative reboot-to-recovery method.
Reboot to system is perfectly fine!
Help anyone? Could it be the bootloader was not properly unlocked... I dit it when I received the phone and wa spretty sure it was unlocked then
Thanks
Click to expand...
Click to collapse
It's not a bootloader issue ,it is problem with the recovery.Use twrp 3.3.3-1-offain or 3.3.3-1dees_troy.

nikoman1987 said:
It's not a bootloader issue ,it is problem with the recovery.Use twrp 3.3.3-1-offain or 3.3.3-1dees_troy.
Click to expand...
Click to collapse
@nikoman1987: Thanks, so I suppose i should go thru the guide again, from the start, right? what is the difference between the offain and dees_troy twrps please?

BenG7 said:
@nikoman1987: Thanks, so I suppose i should go thru the guide again, from the start, right? what is the difference between the offain and dees_troy twrps please?
Click to expand...
Click to collapse
different developers ,i don't have any problems with the offain version.Some of the roms have priblems with dess-troy

nikoman1987 said:
It's not a bootloader issue ,it is problem with the recovery.Use twrp 3.3.3-1-offain or 3.3.3-1dees_troy.
Click to expand...
Click to collapse
exactly the same deal with:
twrp-daisy-3.3.0-0-offain
twrp-3.3.0-dees_troy-daisy
--> red error triangle with the message“The system has been destroyed”...

You need 3.3.1, not 3.3.0
dl.twrp.me/daisy
---------- Post added at 11:37 PM ---------- Previous post was at 11:35 PM ----------
You don't need to redo everything unless you failed to backup your boot image...

a1291762 said:
You need 3.3.1, not 3.3.0
dl.twrp.me/daisy
---------- Post added at 11:37 PM ---------- Previous post was at 11:35 PM ----------
You don't need to redo everything unless you failed to backup your boot image...
Click to expand...
Click to collapse
Hi again @a1291762
I already downloaded and flashed the official daisy twrp but that didn't do it, 3.3.0 it was.
On the official twrp.me website there is only Dees_troy version (true I didn't try 3.3.1 - will do so tonight) - no offain version.
Just wondering, I think I saw some command in some posts to allow flashing on the Mi A2 lite - would that be required here (although not stated in the guide I referenced)?
[EDIT] found this:
I am seeing the ‘System has been destroyed’ message after installing TWRP on Mi A2 Lite (daisy)?
Then download the ‘aboot.img’ from V9.6.4.0 (Download Link), boot your Mi A2 to Fastboot Mode and flash it using the following command:
Code:
fastboot flash aboot_a aboot_9.6.4.img
fastboot flash aboot_b aboot_9.6.4.img
According to the explanation given by XDA Senior Member mac12m99, the newer bootloader (aboot.img) version checks for stock recovery, even when the bootloader is unlocked. To overcome this, you can flash an older bootloader version (Especifically from V9.6.4.0) to fix this issue.
Click to expand...
Click to collapse

BenG7 said:
Hi again @a1291762
I already downloaded and flashed the official daisy twrp but that didn't do it, 3.3.0 it was.
On the official twrp.me website there is only Dees_troy version (true I didn't try 3.3.1 - will do so tonight) - no offain version.
Just wondering, I think I saw some command in some posts to allow flashing on the Mi A2 lite - would that be required here (although not stated in the guide I referenced)?
Click to expand...
Click to collapse
10.0.9.0 broke all the old twrps. Only 3.3.1 works now.
The official TWRP maintainer for daisy is dees troy.
Offain does the lineage ROM for daisy. I don't know how people get links to his TWRP. Search?
That guide looks ancient. TWRP and Magisk install guides can be found in this forum... I wrote a combined one (since having both complicates OTA) but if you're doing a custom ROM... It will depend.
Many custom ROMs want an encryption Disabler fix because they can't handle the encryption (which is on even if you don't have a password).
I've seen lots of surprise by people at the processes required for this phone. It was certainly different to what I've done before, but my last phone was pre-magisk and pre-A/B partitioning so I figured that's just how things are on newer phones.

a1291762 said:
10.0.9.0 broke all the old twrps. Only 3.3.1 works now.
The official TWRP maintainer for daisy is dees troy.
Offain does the lineage ROM for daisy. I don't know how people get links to his TWRP. Search?
That guide looks ancient. TWRP and Magisk install guides can be found in this forum... I wrote a combined one (since having both complicates OTA) but if you're doing a custom ROM... It will depend.
Many custom ROMs want an encryption Disabler fix because they can't handle the encryption (which is on even if you don't have a password).
I've seen lots of surprise by people at the processes required for this phone. It was certainly different to what I've done before, but my last phone was pre-magisk and pre-A/B partitioning so I figured that's just how things are on newer phones.
Click to expand...
Click to collapse
My build is 10.0.13.0

BenG7 said:
My build is 10.0.13.0
Click to expand...
Click to collapse
Then use 3.3.3-1 dees_troy or :
https://drive.google.com/file/d/1-Enw0Kn2CAYyfN1Krv8t3CVNLyn0p0JX/view?usp=drivesdk
Here is the link for twrp 3.3.3-1 offain version ,but it is in .img format.Dont install it via fastboot or TWRP .You can boot it via this command:
fasboot boot twrp-daisy-3.3.1-0-offain.img ,install everything you want,and you'll be ok ,if you don't need permanent twrp recovery!
If you want permanent installation - I am using Android All in One tool from another XDA thread and that's what i do:
Reboot in Fastboot mode,then connect the device to PC open the all-in-one tool on your windows computer ,then click on the "Recovery Flasher and Device Rooter" button(after you see that the device is recognised in the program) ,you need to choose which version- set it to MANUAL. From there navigate to the recovery files(dees_troy and offain) in the first row navigate to the recovery image (offain) ,on the second row navigate to the recovery zip (dees_troy).Then hit the Flash button. The phone will boot in 3.3.3-1 offain twrp ,and automatically will install the dees_troy version and when everything is installed,the phone will reboot after the flash again in recovery.All the time i have 100% success with this all in one tool. When you are ready with the installation of twrp ,flash magisk and reboot to system.
Here is the thread for the tool:
https://forum.xda-developers.com/mi...ol-one-driversunlocktwrpfactory-t3866191/amp/
I guarantee it works every time with 100% chance for success

nikoman1987 said:
Then use 3.3.3-1 dees_troy or :
https://drive.google.com/file/d/1-Enw0Kn2CAYyfN1Krv8t3CVNLyn0p0JX/view?usp=drivesdk
Here is the link for twrp 3.3.3-1 offain version ,but it is in .img format.Dont install it via fastboot or TWRP .You can boot it via this command:
fasboot boot twrp-daisy-3.3.1-0-offain.img ,install everything you want,and you'll be ok ,if you don't need permanent twrp recovery!
...
Here is the thread for the tool:
https://forum.xda-developers.com/mi...ol-one-driversunlocktwrpfactory-t3866191/amp/
I guarantee it works every time with 100% chance for success
Click to expand...
Click to collapse
Thanks @a1291762 & @nikoman1987 but the tool won't do it for me at home
I do not think I need permanent TWRP (although I know how nice it is to know you can always fall back to twrp - I will have to use a PC instead); my intention is to flash https://forum.xda-developers.com/mi-a2-lite/development/lineageos-16-0-xiaomi-mi-a2-lite-t3919060LineageOS with temporary twrp 3.3.3-1 offain version

BenG7 said:
Thanks @a1291762 & @nikoman1987 but the tool won't do it for me at home
I do not think I need permanent TWRP (although I know how nice it is to know you can always fall back to twrp - I will have to use a PC instead); my intention is to flash LineageOS with temporary twrp 3.3.3-1 offain version
Click to expand...
Click to collapse
Your choice , but I always prefer to have permanent twrp with custom ROMs . You know what's best for you.

a1291762 said:
10.0.9.0 broke all the old twrps. Only 3.3.1 works now.
The official TWRP maintainer for daisy is dees troy.
Offain does the lineage ROM for daisy. I don't know how people get links to his TWRP. Search?
That guide looks ancient. TWRP and Magisk install guides can be found in this forum... I wrote a combined one (since having both complicates OTA) but if you're doing a custom ROM... It will depend.
Many custom ROMs want an encryption Disabler fix because they can't handle the encryption (which is on even if you don't have a password).
I've seen lots of surprise by people at the processes required for this phone. It was certainly different to what I've done before, but my last phone was pre-magisk and pre-A/B partitioning so I figured that's just how things are on newer phones.
Click to expand...
Click to collapse
@a1291762
I got this message after formatting the data and wiping system, trying to install LO:
Code:
"Device unable to boot. Error - mdtp image is corrupted"
I am now stuck on fastboot!
From the post https://forum.xda-developers.com/nov...7#post80993947
I understand I have to flash BOOT/RECOVERY/SYSTEM imgs to restore your device;
the commands are
Boot:
Code:
fastboot flash boot boot.img
Recovery:
Code:
fastboot flash recovery recovery.img
System:
Code:
fastboot flash system system.img
but the question is where can I get the
boot.img
recovery.img
system.img
for the xiaomi Mi A2 Lite (daisy); bearing in mind the phone is on a 2 partition system?
Thanks a lot in advance

BenG7 said:
@a1291762
I got this message after formatting the data and wiping system, trying to install LO:
Code:
"Device unable to boot. Error - mdtp image is corrupted"
I am now stuck on fastboot!
From the post https://forum.xda-developers.com/nov...7#post80993947
I understand I have to flash BOOT/RECOVERY/SYSTEM imgs to restore your device;
Click to expand...
Click to collapse
There is no recovery image because this is an A/B partitioned phone.
The mdtp issue seems to be a real issue for some people.
https://forum.xda-developers.com/mi-a2-lite/help/device-unable-to-boot-error-mdtp-image-t3926962
The advice I gave there is all I can give here. Try to fastboot/MiFlash a stock ROM.
If you don't have a stock image, they're listed here:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Note that the newest image is 10.0.13.0 (14, 15, 16 did not get full releases, just OTAs).
These threads suggest it's possible to flash a stock ROM to fix a corrupt mdtp partition...
https://forum.xda-developers.com/mi-a2-lite/help/fastboot-loop-t3996081
https://forum.xda-developers.com/mi-a2-lite/help/mi-a2-lite-stuck-fastboot-recovery-help-t3938175

a1291762 said:
There is no recovery image because this is an A/B partitioned phone.
The mdtp issue seems to be a real issue for some people.
https://forum.xda-developers.com/mi-a2-lite/help/device-unable-to-boot-error-mdtp-image-t3926962
The advice I gave there is all I can give here. Try to fastboot/MiFlash a stock ROM.
If you don't have a stock image, they're listed here:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Note that the newest image is 10.0.13.0 (14, 15, 16 did not get full releases, just OTAs).
These threads suggest it's possible to flash a stock ROM to fix a corrupt mdtp partition...
https://forum.xda-developers.com/mi-a2-lite/help/fastboot-loop-t3996081
https://forum.xda-developers.com/mi-a2-lite/help/mi-a2-lite-stuck-fastboot-recovery-help-t3938175
Click to expand...
Click to collapse
Thanks @a1291762.
I
Code:
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
as instructed by @SubwayChamp in the link you posted
but the phone boots straight back to fastboot after
Code:
fastboot reboot
so I believe I need to flash a stock rom
I'm on Debian; I am wondering wether I can use
Can XiaoMiTool V2 unbrick my device?
to unbrick my phone or just
fastboot flash the daisy_global_images_V10.0.13.0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04.tgz rom?
Please confirm the commands are:
Code:
fastboot -w
fastboot update </path/to/your/Rom.zip>
and it will work with a .tgz format or do I need to extract it and then zip it?
Thanks for your help

BenG7 said:
Thanks @a1291762.
I
Code:
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
as instructed by @SubwayChamp in the link you posted
but the phone boots straight back to fastboot after
Code:
fastboot reboot
so I believe I need to flash a stock rom
I'm on Debian; I am wondering wether I can use
Can XiaoMiTool V2 unbrick my device?
to unbrick my phone or just
fastboot flash the daisy_global_images_V10.0.13.0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04.tgz rom?
Please confirm the commands are:
Code:
fastboot -w
fastboot update </path/to/your/Rom.zip>
and it will work with a .tgz format or do I need to extract it and then zip it?
Thanks for your help
Click to expand...
Click to collapse
Mdtp flashes returned your device to an state where partitions are readable again otherwise you won´t enter not even to recovery.
You don´t have to try to flash recovery (nor stock or custom), only reboot to a custom recovery like TWRP, the process to do it is well explained there, I also faced an mdtp issue and I didn´t need to flash the whole rom, just booted to TWRP and from there I did what I wanted, but if you yet want to do it.......
First of all I´m not familiar with Debian coming to modding smartphones, just I use it within other distros for other purposes.
The tool that you linked is not useful for us, this tool works mainly to fool recovery to accept modded scripts as original/signed and our device although it has a recovery image doesn´t have a dedicated partition and it simply is not available for the normal user, it´s mean that this tool uses MiRecovery present on all the devices running Miui out of the box but not for the others running Android One.
If you can access to a Windows machine this is the tool that I frequently use: https://xiaomifirmware.com/downloads/miflashpro/ but if you only can access to a PC with Debian probably this tool works for you https://forum.xda-developers.com/android/software/tool-miflash-linux-t3708847

BenG7 said:
daisy_global_images_V10.0.13.0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04.tgz rom?
Please confirm the commands are:
Click to expand...
Click to collapse
You can't throw a .tgz or .zip at fastboot?!
If you're going to flash a stock ROM, extract it and run a flash_XXX script. It will use your fastboot to flash every partition. Variants preserve data or relock bootloader.

if fastboot fails (data transfer failure (too many links))
-> use a different USB port which is not a charging port.
-> try a different USB cable

Delete me

Guide to root motorola g stylus

QUICK STEPS TO ROOT MOTOROLA MOTO G STYLUS USING MAGISK
Just Remember*I just want to warn you that, Rooting will void the warranty of your smartphone
Rooting will block the OTA updates
1.First of all, please download and extract the ROM on your computer.
https://r.tapatalk.com/shareLink/to...1&share_fid=3793&share_type=t&link_source=app
2:*Now, connect your moto g stylus with a micro USB cable, and copy only the boot.img file from the extracted folder to your Motorola moto g stylus device storage/memory.
3:*Now you need to Launch Magisk Manager.
4:*After that, you will see a popup window that will ask you to install Magisk.
5:*Finally please select INSTALL and choose to install it again.
6:*Now Please press on “Patch Boot Image File
7:*Navigate to internal storage and select your phone’s boot image that you transferred earlier.
8:*Wait for a couple of seconds. Magisk will start patching the boot image.
9:*Once the boot image has been patched, copy the “patched_boot.img” from the internal storage and replace it in the same extracted ROM folder on your PC.
10:*Now you can follow the second step to flash the patched boot image file.
Next, you need to enter the following commands step by step:
First of all, you need to Flash the “patched_boot.img” to install Magisk and root your Motorola moto g stylus: fastboot flash boot patched_boot.img
You can also use the devices with A/B partition system, with the following commands:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
After that, you need to replace [patched_boot.img] with the same boot image file that you have already downloaded with the .img.
Now you will see the flashing process have has started. Now, run fastboot and reboot
HOW TO VERIFY IF YOUR MOTOROLA MOTO G STYLUS HAS A SYSTEMLESS ROOT?
Download and install the Magisk Manager app APK, and launch it.
If you want to verify that you have a systemless root, check the top of the screen and if you see all options with Green Tick which means you have successfully rooted and bypassed SafetyNet.
Sent from my moto g stylus using Tapatalk

surprised to see no comments on this topic. I am thinking of getting this phone but only if there is a root method for it.

It definitely works for the metro by TMobile version.

himesh82 said:
surprised to see no comments on this topic. I am thinking of getting this phone but only if there is a root method for it.
Click to expand...
Click to collapse
I got root by using magisk to patch the boot image. I purchased the phone directly from Motorola's website. If you get a version where the bootloader can be unlocked (some carrier versions apparently cannot be unlocked) you can root without much trouble.

dafunk60 said:
I got root by using magisk to patch the boot image. I purchased the phone directly from Motorola's website. If you get a version where the bootloader can be unlocked (some carrier versions apparently cannot be unlocked) you can root without much trouble.
Click to expand...
Click to collapse
I am based in Uk and will order from their website.
How easy it is to use as It has been afew years i tried rooting and will need a super easy guide.

himesh82 said:
I am based in Uk and will order from their website.
How easy it is to use as It has been afew years i tried rooting and will need a super easy guide.
Click to expand...
Click to collapse
I found it to be super easy using magisk, provided you have a PC to flash the patched boot.img to the phone via fastboot. I use the Lenovo Rescue & Smart Assist software on the PC to download the ROM from Motorola. You need to ensure the ROM you're downloading is the same version running on your phone. Using a boot.img from a different version will cause issues.
1. Copy the boot.img to the phone.
2. On the phone, patch the boot.img you just copied over with Magisk Manager.
3. Copy the patched magisk_patched.img back to your PC.
4. Connect to the phone via adb. (There's an adb.exe in the Lenovo Rescue & Smart Assist install directory "C:\Program Files (x86)\Rescue and Smart Assistant".)
5 . Reboot the phone to the bootloader with the following command on the PC:
Code:
adb reboot bootloader
6. Flash the patched boot image with the following command on the PC:
Code:
fastboot flash boot magisk_patched.img
7. Reboot the phone with the following command on the PC:
Code:
fastboot reboot
Once rebooted you can use Magisk Manager to hide root, check the SafetyNet status, etc.

Thank you for your help on this. I rooted my moto x4 long time ago and the process has definately changed.
Still confused regarding your points
1 - where can i find the boot.img
2 - how do you patch using magisk
Also do you not need to unlock boot loader and bypass the verification and why do you need to hide root after?
Thank you
dafunk60 said:
I found it to be super easy using magisk, provided you have a PC to flash the patched boot.img to the phone via fastboot. I use the Lenovo Rescue & Smart Assist software on the PC to download the ROM from Motorola. You need to ensure the ROM you're downloading is the same version running on your phone. Using a boot.img from a different version will cause issues.
1. Copy the boot.img to the phone.
2. On the phone, patch the boot.img you just copied over with Magisk Manager.
3. Copy the patched magisk_patched.img back to your PC.
4. Connect to the phone via adb. (There's an adb.exe in the Lenovo Rescue & Smart Assist install directory "C:\Program Files (x86)\Rescue and Smart Assistant".)
5 . Reboot the phone to the bootloader with the following command on the PC:
Code:
adb reboot bootloader
6. Flash the patched boot image with the following command on the PC:
Code:
fastboot flash boot magisk_patched.img
7. Reboot the phone with the following command on the PC:
Code:
fastboot reboot
Once rebooted you can use Magisk Manager to hide root, check the SafetyNet status, etc.
Click to expand...
Click to collapse

himesh82 said:
Thank you for your help on this. I rooted my moto x4 long time ago and the process has definately changed......
Thank you
Click to expand...
Click to collapse
You're welcome.
himesh82 said:
1 - where can i find the boot.img
Click to expand...
Click to collapse
In the Lenovo software you can choose a download location. The default appears to be "C:\ProgramData\LMSA\Download". In that directory you'll see a "RomFiles" folder which contains folders for the different ROM versions it has downloaded. SOFIAP_RETAIL_QPR30.80_58_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml or SOFIAP_RETAIL_QPRS30.80_58_3_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml for example. You can find the boot.img file within those folders.
The QPRD30.80_58_3 boot.img file is located in "C:\ProgramData\LMSA\Download\RomFiles\SOFIAP_RETAIL_QPRS30.80_58_3_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml"
Some people share links to the ROM files but I prefer to get mine from Motorola.
himesh82 said:
2 - how do you patch using magisk
Click to expand...
Click to collapse
Google's your friend on this topic, https://www.xda-developers.com/how-to-use-magisk/
himesh82 said:
Also do you not need to unlock boot loader and bypass the verification and why do you need to hide root after?
Click to expand...
Click to collapse
You do need to unlock the bootloader, unless you have the private key Motorola uses to sign images . Just follow the instructions on the Motorola website. Unlocking the bootloader & rooting are two separate things. You need to unlock the bootloader to allow the hardware to boot unsigned images, such as a patched boot image. Root provides applications root access to the Android OS.
You typically want to hide root as some apps won't function if they detect root, mostly banking & video streaming services I believe. It's not a requirement however.

Thank you again. I will take a good look at the guide and then decide if it is something that I can attempt

Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help

Wait DOES THIS WIPE ALL THE DATA?? I CANT get a clear answer. Supposedly the "official" unlocking through Motorola does but this is the Magisk method and I'm hoping it doesn't wipe the user data or apps.
Also how do you root AFTER you unlock the bootloader?
---------- Post added at 06:43 PM ---------- Previous post was at 06:37 PM ----------
JimmyJurner said:
It definitely works for the metro by TMobile version.
Click to expand...
Click to collapse
Does rooting wipe all the user data and apps?

nokia4life2017 said:
Wait DOES THIS WIPE ALL THE DATA?? I CANT get a clear answer. Supposedly the "official" unlocking through Motorola does but this is the Magisk method and I'm hoping it doesn't wipe the user data or apps.
Also how do you root AFTER you unlock the bootloader?
---------- Post added at 06:43 PM ---------- Previous post was at 06:37 PM ----------
Does rooting wipe all the user data and apps?
Click to expand...
Click to collapse
I honestly don't know. When I did the steps from op I unlocked the bootloader then rooted. I never booted into system. I can't check now because I'm running havoc os gsi and the op method doesn't work on gsis. I tried and it didn't boot but when I flashed the stock boot.img all my setup was still the same. Hope that helps some.

Growking99 said:
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Click to expand...
Click to collapse
Do you have a carrier model? You might be flashing the wrong boot.img although I'm not sure if theres anything different between then

No I bought the unlocked model from best buy cuz I know carrier models usually aren't rootable. Can some one post a link to the right boot.img
Here is my build number QPRS30.80-58-3 and my device info is in the pic TIA for any help

nokia4life2017 said:
Wait DOES THIS WIPE ALL THE DATA?? I CANT get a clear answer. Supposedly the "official" unlocking through Motorola does but this is the Magisk method and I'm hoping it doesn't wipe the user data or apps.
Also how do you root AFTER you unlock the bootloader?
Does rooting wipe all the user data and apps?
Click to expand...
Click to collapse
There are instructions on rooting in these forums, even in this thread.
Unlocking the bootloader forces user data to be wiped (aka factory reset).
Rooting with Magisk does not wipe user data.
Unlocking the bootloader and rooting are two separate things. Unlocking the bootloader allows unsigned images, such as a modified boot.img, to be run on the device. Rooting provides applications root level access to the Android OS.
---------- Post added at 02:19 AM ---------- Previous post was at 02:10 AM ----------
Growking99 said:
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Click to expand...
Click to collapse
It sounds like the boot image you're flashing does not match the version of the ROM on the phone. From your subsequent post, it looks like you're running QPRS30.80-58-3. Where did you get the boot.img file that you patched? You can use the Lenovo Rescue software to download the ROM files right from Motorola. These will contain the entire ROM, including the original boot image. Details are in the posts preceding yours. Flash the original boot.img & see if the phone boots. If it does, patch that image with Magisk & flash to obtain root.

Growking99 said:
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Click to expand...
Click to collapse
Try fastboot flash boot boot.img. When i did the stot a and b method i lost touchscreen etc
I bought a second stylus and the root method is different. So I fastboot flash the image (not to slots) and it worked but when the screen goes off the touch screen isn't responding.

I got it to work by using the assistant mentioned above. And using the fastboot flash magisk_patched.img or fastboot flash boot magisk_patched.img I can't remember which one at the moment but it automatically flashed both A and B slots with no problems. Also is TWRP available for the G Stylus?

Growking99 said:
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Click to expand...
Click to collapse
i just had the same thing happen to me. But i went to the assistant software and tried to rescue my device and it failed. Did you get it to work and how exactly did you get it working?
Edit: I just got it rescued and Im back up and running. Now I just need to figure out how not to repeat whatever mistake I just made and to get my device rooted. Did you ever figure out what you did wrong?

JimmyJurner said:
It definitely works for the metro by TMobile version.
Click to expand...
Click to collapse
Without unlocking the Bootloader?
*edit*
Cancel that, Just Unlocked my MetroPCS Moto G Stylus's Bootloader
*edit* *edit*
FYI : There is a new build for the RETAIL Channel from 7/21 : mirrors.lolinet.com/firmware/moto/sofiap/official/RETAIL/

Growking99 said:
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Click to expand...
Click to collapse
I am having the same issue while in fastboot, the device reboots bootloader every 20-30 seconds. I had to wait till the screen went off before hitting enter to get OEM Get_unlock_code.