Database Info

How to downgrade baseband

Hello Friends,
I am Using Honor H60-L04. I have Updated My Mobile to EMUI 3.0 B370. Unknowingly My Baseband Got Updated. And i am Unable to Install EMUI 2.3. I have tired to Flash MODEM files but i am facing ERROR can any Help Me
FAILED (remote: Command not allowed)

pudup said:
Download a 2.3 ROM and split it into its .IMG files and then flash all the necessary parts with fastboot/bootloader.
Do it at your own risk, I don't know if it could soft brick your phone or not.
Click to expand...
Click to collapse
I Tried to flash Using Fastboot. But Still I am it is showing the Below ERROR
FAILED (remote: Command not allowed)

You cannot downgrade the bootloader.

pudup said:
is your boot loader locked?
Click to expand...
Click to collapse
my bootloader is unlocked.

only a revert package could help
read this

ratelutz said:
only a revert package could help
read this
Click to expand...
Click to collapse
Where Can i Download the REVERT PACKAGE?

read the post i linked. There is no revert pack available right now

[GUIDE] [XT1572] Flashing Stock Firmware

As the Nougat is rolling out for XT1572 devices, here's the guide for Flashing Stock Firmware using Fastboot for receiving Nougat OTA.
(Inspired by @acejavelin guide)
Prerequisites:
1) USB Drivers (Not needed for Windows 10)
2) Fastboot installed and working.
3) Stock Factory Images for Moto X Style (XT1572): https://firmware.center/firmware/Motorola/Moto X Style/Stock/XT1572/
Procedure:
1) Open a terminal or command prompt (Shift + Right click) window into the directory that contains the firmware files you extracted above.
2) Reboot the phone in Fastboot Mode (Reboot to Bootloader) and connect the USB Cable.
3) To verify if everything is perfect type in:
Code:
fastboot devices
If it shows your device serial number then you can be sure that it's properly connected.
4) Read the 'Notes' below.
6) Before proceeding, flash this commands to clean up the previous system's mess. This will get rid of the '(bootloader) Preflash validation failed' error when flashing gpt.bin (partition table).
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
5) Here's the actual commands to Flash the Stock Image. Please Enter them One-by-one, Don't create any .bat files or copy and paste the entire section.
Code:
[STRIKE]fastboot getvar max-sparse-size[/STRIKE]
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash 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 modem NON-HLOS.bin
fastboot flash modem NON-HLOS.bin (Flash twice, if Prevalidation Error)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Make sure you read whatever is happening on the prompt, do not miss any errors. (Scroll up the prompt and re-check everything before booting)
Notes:
1) This won't Lock your bootloader but you will be able to get OTA's.
2) For receiving Nougat on RETASIA Dual Sim, download: XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip
There will be a 44mb update already queued when you boot the device. It will update the device to December 2016 Security Patch.
Reboot and you will be able to get Nougat OTA (911mb), if eligible.
3) If you didn't get the OTA Update, Flash this Nougat OTA after updating to December 2016 security patch: https://forum.xda-developers.com/moto-x-style/general/ota-nph25-200-15-retasiads-t3636765 (Credits: @Sagar_1401)
4) Different firmwares may contain a different number of system.img_sparsechunk.X files, you must flash the number you have in your firmware image in order. From what I have seen, most 5.1.1 firmwares have nine, 6.0 has eight, and 6.0.1 has eleven sparsechunks.
5) You must use a factory firmware image that is the same version as what you have installed or newer to successfully relock the bootloader, you cannot just grab the old (shipped) version from Moto's site. If you attempt to use a firmware image that is older than what you have installed currently, you will receive a Preflash Validation Error indicating such when you attempt to flash the partition table (gpt.bin).

There is no need to do fastboot getvar max-sparse-size, that is just for RSD Lite to check your maximum system chunk size, when doing it manually it does nothing.
Not really sure why this guide is needed, there are already a few out there that are basically identical.

Nice guide @antariksh thanks for this.
i will be flashing from my current version 6.0.1_MPH24.107-58 (seemingly higher version) tomorrow.
will update once i attempt this.

Quick tip if you can't get SafetyNet passed with Magisk V13.1 or V13.2
For Stock Nougat as we don't have boot.img
1) Backup boot with TWRP
2) Restore boot with TWRP
3) Flash Magisk zip
4) Reboot and Install Magisk Manager v5+
This won't get your SafetyNet passed.
5) Open Magisk Manager and once again press 'Download and Install'
This will automatically download and install the latest Magisk and after a reboot your SafetyNet will be passed.

antariksh said:
5) You must use a factory firmware image that is the same version as what you have installed or newer to successfully relock the bootloader, you cannot just grab the old (shipped) version from Moto's site. If you attempt to use a firmware image that is older than what you have installed currently, you will receive a Preflash Validation Error indicating such when you attempt to flash the partition table (gpt.bin).
Click to expand...
Click to collapse
I got 6.0.1 ROM, how do i downgrade to 6.0? I try to flash to 6.0, it's shown message like above

hi guys,
My XT1572, previous rom version 6.0.1_MPH24.107-58-5 and I reflashed to 6.0 MPHS 24.49-18-8 successfully but I can not update December patch security 2016. I attempted to flash Nougat on RETASIA Dual Sim in Recovery but error FingerPrinter. Do I need any tricky ? Thank

trannamcloud said:
I got 6.0.1 ROM, how do i downgrade to 6.0? I try to flash to 6.0, it's shown message like above
Click to expand...
Click to collapse
titanworm said:
hi guys,
My XT1572, previous rom version 6.0.1_MPH24.107-58-5 and I reflashed to 6.0 MPHS 24.49-18-8 successfully but I can not update December patch security 2016. I attempted to flash Nougat on RETASIA Dual Sim in Recovery but error FingerPrinter. Do I need any tricky ? Thank
Click to expand...
Click to collapse
You can't go from 6.0.1 to 6.0 completely... Your bootloader and partition table cannot be downgraded and are actually different than on 6.0, they work (meaning 6.0 will boot} but it isn't a match. You cannot take an OTA to 18-16 or any other version because of the mismatch.
The only way to upgrade is go back to 6.0.1 then take the OTA to Nougat.

acejavelin said:
You can't go from 6.0.1 to 6.0 completely... Your bootloader and partition table cannot be downgraded and are actually different than on 6.0, they work (meaning 6.0 will boot} but it isn't a match. You cannot take an OTA to 18-16 or any other version because of the mismatch.
The only way to upgrade is go back to 6.0.1 then take the OTA to Nougat.
Click to expand...
Click to collapse
Thanks a lot!
I go back to 6.0.1 Retapac, with security pack 1-Mar-2016, an now waiting for official Nougat OTA update

So I was on 6.0.1 as well and used the 18-8 firmware to downgrade to 6.0. had the same preflash validation error, i flashed gpt the second time after the error occurred and completed the flash like normal. Everything just worked perfectly fine after that. Got the security update to December and nought!
Edit : I did all of this keeping my bootloader unlocked.
Sent from my HTC 10 using Tapatalk
---------- Post added at 08:05 AM ---------- Previous post was at 08:01 AM ----------
You need to go to 6.0 and not 6.0.1.. The firmware to download is XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip
trannamcloud said:
Thanks a lot!
I go back to 6.0.1 Retapac, with security pack 1-Mar-2016, an now waiting for official Nougat OTA update
Click to expand...
Click to collapse
Sent from my HTC 10 using Tapatalk

pradeepvizz said:
So I was on 6.0.1 as well and used the 18-8 firmware to downgrade to 6.0. had the same preflash validation error, i flashed gpt the second time after the error occurred and completed the flash like normal. Everything just worked perfectly fine after that. Got the security update to December and nought!
Edit : I did all of this keeping my bootloader unlocked.
Sent from my HTC 10 using Tapatalk
---------- Post added at 08:05 AM ---------- Previous post was at 08:01 AM ----------
You need to go to 6.0 and not 6.0.1.. The firmware to download is XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
So have you upgrade to Nougat yet?
I unlocked bootloader already, so could i bypass preflash validatation error as your guide? My phone said "downgrade failured " in bootloader screen logs

titanworm said:
hi guys,
My XT1572, previous rom version 6.0.1_MPH24.107-58-5 and I reflashed to 6.0 MPHS 24.49-18-8 successfully but I can not update December patch security 2016. I attempted to flash Nougat on RETASIA Dual Sim in Recovery but error FingerPrinter. Do I need any tricky ? Thank
Click to expand...
Click to collapse
Last week I flashed the MPH24.107-58-5 (6.0.1) thinking that this was the latest version. But then I TWRP restored back to my Custom ROM as there was no Nougat OTA.
On this Saturday I was able to flash the MPHS 24.49-18-8 without any issues.
Try flashing the gpt.bin twice and don't try to lock your bootloader.

trannamcloud said:
So have you upgrade to Nougat yet?
I unlocked bootloader already, so could i bypass preflash validatation error as your guide? My phone said "downgrade failured " in bootloader screen logs
Click to expand...
Click to collapse
i didn't see what the bootloader screen logs said, but when you get the error, you have to reflash the same thing again.
fastboot flash modem NON-HLOS.bin (Flash twice, if Prevalidation Error)
Click to expand...
Click to collapse
I have upgraded to Nougat successfully with no problems.

pradeepvizz said:
i didn't see what the bootloader screen logs said, but when you get the error, you have to reflash the same thing again.
I have upgraded to Nougat successfully with no problems.
Click to expand...
Click to collapse
Att image for your ref, i got preflash error when trying to flash gpt.bin. And i found problem as Mr @acejavenlin said below, saidly i have to go back 6.0.1 again
acejavelin said:
You can't go from 6.0.1 to 6.0 completely... Your bootloader and partition table cannot be downgraded and are actually different than on 6.0, they work (meaning 6.0 will boot} but it isn't a match. You cannot take an OTA to 18-16 or any other version because of the mismatch.
The only way to upgrade is go back to 6.0.1 then take the OTA to Nougat.
Click to expand...
Click to collapse

yep, I had to return to XT1572_CLARK_RETASIA_DS_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml although I reflashed XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml completely on my devices and I was not able to upgrade to December patch. Now, my Android security patch level is September 1,2016. Did we have December 2016 patch for this MPHS24.107-58-5 and Asia DS? @acejavelin

titanworm said:
yep, I had to return to XT1572_CLARK_RETASIA_DS_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml although I reflashed XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml completely on my devices and I was not able to upgrade to December patch. Now, my Android security patch level is September 1,2016. Did we have December 2016 patch for this MPHS24.107-58-5 and Asia DS? @acejavelin
Click to expand...
Click to collapse
trannamcloud said:
Att image for your ref, i got preflash error when trying to flash gpt.bin. And i found problem as Mr @acejavenlin said below, saidly i have to go back 6.0.1 again
Click to expand...
Click to collapse
Same me, the only way is back to 6.0.1 now

titanworm said:
yep, I had to return to XT1572_CLARK_RETASIA_DS_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml although I reflashed XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml completely on my devices and I was not able to upgrade to December patch. Now, my Android security patch level is September 1,2016. Did we have December 2016 patch for this MPHS24.107-58-5 and Asia DS? @acejavelin
Click to expand...
Click to collapse
trannamcloud said:
Att image for your ref, i got preflash error when trying to flash gpt.bin. And i found problem as Mr @acejavenlin said below, saidly i have to go back 6.0.1 again
Click to expand...
Click to collapse
i am not expert in Moto flashing, don't honestly have the patience to wait for the OTA from 6.0.1 to 7.
Was the build MPHS24.107-58 official for ASIA DS in the first place? i see posts on the lenovo forums asking 6.0.1 for Asian version which makes me think there was no official release. i wouldn't expect a OTA update if there was no official release of the 107-58 build in Asia. mine is a Asain version, what version is yours?

hi, guys
What is your Bootloader version, mine is BL: A0.4C for 6.0 Retasia DS. I see 6.0.1 Retasia DS has BL: A0.4A. Which versions is higher? With BL: A0.4C for 6.0 Retasia DS, I cannot flash to 6.0.1 with GPT.bin and Boot.img.

I'm currently on xt 1572 retasia ds MPHS24.49-18-16 but with bootloader unlocked and twrp installed. Can someone guide me to the December 2016 file so that I can restore to stock or the nougat file so that I can directly update my phone through fastboot method. Thanks in advance.

duttandy said:
I'm currently on xt 1572 retasia ds MPHS24.49-18-16 but with bootloader unlocked and twrp installed. Can someone guide me to the December 2016 file so that I can restore to stock or the nougat file so that I can directly update my phone through fastboot method. Thanks in advance.
Click to expand...
Click to collapse
We don't have either... The best you can do is hope someone can do a TWRP backup of recovery you can restore, it needs to be the same variant and version.

pradeepvizz said:
i am not expert in Moto flashing, don't honestly have the patience to wait for the OTA from 6.0.1 to 7.
Was the build MPHS24.107-58 official for ASIA DS in the first place? i see posts on the lenovo forums asking 6.0.1 for Asian version which makes me think there was no official release. i wouldn't expect a OTA update if there was no official release of the 107-58 build in Asia. mine is a Asain version, what version is yours?
Click to expand...
Click to collapse
Confuse now. As you said, 6.0.1 build 107-58 is not official release, so maybe not receive OTA Nougat?
My version is Asian - retapac, 6.0.1 - build 107-58 with security patch 1-Mar-2016. It's unable to downgrade to any stock 6.0, as preflash error.

Problem installing update.zip

After a bad manipulation on TWRP, I would have liked to install a rom stock in zip file, problem see photo :
http://www.stechguide.com/honor-6x-b365-nougat-update/
I followed the procedure indicated on the link with the TWRP method

DELLINSPIRON1958 said:
After a bad manipulation on TWRP, I would have liked to install a rom stock in zip file, problem see photo :
http://www.stechguide.com/honor-6x-b365-nougat-update/
I followed the procedure indicated on the link with the TWRP method
Click to expand...
Click to collapse
Were you on MM or nougat before this? And accordingly use the correct twrp. The ine you used may be not be the correct one.once the correct twrp installed, you may flash without error 7.
Whats the phone model btw?

Hi, I am on nougat and I use TWRP.3.1.0-2 berlin the only one I managed to make it work
you have a other version for BLNL21C432B365

DELLINSPIRON1958 said:
Hi, I am on nougat and I use TWRP.3.1.0-2 berlin the only one I managed to make it work
you have a other version for BLNL21C432B365
Click to expand...
Click to collapse
You are using incorrect version of trwp. Check in rom section there is one for emui 5 decryption support or in my signature for root method you will direct link there.

DELLINSPIRON1958 said:
Hi, I am on nougat and I use TWRP.3.1.0-2 berlin the only one I managed to make it work
you have a other version for BLNL21C432B365
Click to expand...
Click to collapse
You'll find latest working TWRP here in OP https://forum.xda-developers.com/honor-6x/development/twrp-t3583413

Hello, I have "Enable OEM unlock" which is grayed out how to unlock to be able to install TWRP

DELLINSPIRON1958 said:
Hello, I have "Enable OEM unlock" which is grayed out how to unlock to be able to install TWRP
Click to expand...
Click to collapse
Mine is grayed out too. Dont worry its just mean frp will be unlocked. Go ahead with flashing

Thanks for the information, or I could find a link with the ADB directory,
PS C:\Users\jeanl\Desktop\Telephone\Adb-fastboot-win> fastboot flash recovery twrp-3.1.1-0-berlin.img
target reported max download size of 471859200 bytes
sending 'recovery' (24466 KB)...
OKAY [ 0.636s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.644s
PS C:\Users\jeanl\Desktop\Telephone\Adb-fastboot-win>

DELLINSPIRON1958 said:
FAILED (remote: Command not allowed)
finished. total time: 0.644s
Click to expand...
Click to collapse
Bootloader is unlocked? When you go on fastboot, what is the status of the 2 voices, FRP and phone?

RedSkull23 said:
Bootloader is unlocked? When you go on fastboot, what is the status of the 2 voices, FRP and phone?
Click to expand...
Click to collapse
Voir Photo

impossible to bootload back to SAV

DELLINSPIRON1958 said:
impossible to bootload back to SAV
Click to expand...
Click to collapse
Only dload will work on this

I cant update my Honor 8 (B360) Please help me!

Hi guys , i have big problem...
My Device : Honor 8 FRD-L09 with B360 , Bootloader Unlocked - FRP Unlock - No Root.
My Situation :
- I do not get updates
-I cant locked Bootloader
C:\adb>fastboot oem relock ##########
...
FAILED (remote: root type is risk)
finished. total time: 0.005s
- I cant flash B380 with TWRP or Normal Update (dload etc etc)
- I cant flash B394 with TWRP
I need locked Bootloader and update at last version because the battery does not last long and if i no fix with update I'm sending it to assistance :crying::crying::crying::crying::crying::crying:
NB: Sorry for my bad english

GosuSfaccim said:
Hi guys , i have big problem...
My Device : Honor 8 FRD-L09 with B360 , Bootloader Unlocked - FRP Unlock - No Root.
My Situation :
- I do not get updates
-I cant locked Bootloader
C:\adb>fastboot oem relock ##########
...
FAILED (remote: root type is risk)
finished. total time: 0.005s
- I cant flash B380 with TWRP or Normal Update (dload etc etc)
- I cant flash B394 with TWRP
I need locked Bootloader and update at last version because the battery does not last long and if i no fix with update I'm sending it to assistance :crying::crying::crying::crying::crying::crying:
NB: Sorry for my bad english
Click to expand...
Click to collapse
Try to reinstall everything using a rollback (that will lock, not relock, the bootloader) and you'll be able to flash updates again

GosuSfaccim said:
Hi guys , i have big problem...
My Device : Honor 8 FRD-L09 with B360 , Bootloader Unlocked - FRP Unlock - No Root.
My Situation :
- I do not get updates
-I cant locked Bootloader
C:\adb>fastboot oem relock ##########
...
FAILED (remote: root type is risk)
finished. total time: 0.005s
- I cant flash B380 with TWRP or Normal Update (dload etc etc)
- I cant flash B394 with TWRP
I need locked Bootloader and update at last version because the battery does not last long and if i no fix with update I'm sending it to assistance :crying::crying::crying::crying::crying::crying:
NB: Sorry for my bad english
Click to expand...
Click to collapse
What's your cust version?

itisiryan said:
What's your cust version?
Click to expand...
Click to collapse
Try searching on the forum

grilla99 said:
Try searching on the forum
Click to expand...
Click to collapse
Wat? Why would I seatch for that in the forum?

itisiryan said:
Wat? Why would I seatch for that in the forum?
Click to expand...
Click to collapse
Oh Sorry i logged in with my other account ?

grilla99 said:
Oh Sorry i logged in with my other account ?
Click to expand...
Click to collapse
You have two accounts here?

itisiryan said:
You have two accounts here?
Click to expand...
Click to collapse
One for Honor 8 with the xda app, and another for my Honor 7, i was typing this answear in a Honor 7 question. And i did not realized i was in the Honor 8 forum

grilla99 said:
One for Honor 8 with the xda app, and another for my Honor 7, i was typing this answear in a Honor 7 question. And i did not realized i was in the Honor 8 forum
Click to expand...
Click to collapse
Oh. Got it. :laugh:

ScardracS said:
Try to reinstall everything using a rollback (that will lock, not relock, the bootloader) and you'll be able to flash updates again
Click to expand...
Click to collapse
I try reflash all and i cant lock bootloader ...

GosuSfaccim said:
I try reflash all and i cant lock bootloader ...
Click to expand...
Click to collapse
That's strange... What's method have you tried?

Moto G 5G XT-2213-3

Has anyone installed a custom rom successfully on a Moto G 5G model XT-2213-3?
The kiev build for Lineage 18.1 lists these variants as compatible:
Supported models
XT2113-2
XT2113-3
XT2113-5

This is the device's specs on GSM arena.
Moto G 5G (2022)

So apparently in moving from the 2020 kiev version to this phone, they replaced the qualcomm processor with a mediatek. Bad news for the custom rom future of it. It did easily bootloader unlock, so now I'm trying to see if root is a possibility.

Old_Mil said:
So apparently in moving from the 2020 kiev version to this phone, they replaced the qualcomm processor with a mediatek. Bad news for the custom rom future of it. It did easily bootloader unlock, so now I'm trying to see if root is a possibility.
Click to expand...
Click to collapse
Hello. Have you found any solution to root this device? I have the same model (2213-3 Austin), and unlocked the phone but could not root the device. No solution on the internet works for me.

enaykey said:
Hello. Have you found any solution to root this device? I have the same model (2213-3 Austin), and unlocked the phone but could not root the device. No solution on the internet works for me.
Click to expand...
Click to collapse
I was successfully able to root using this guide.
[Guide][Root] Magisk without TWRP on Android P
Via Magisk Manager: This method does not need root, and also does not require a custom recovery. However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode...
forum.xda-developers.com
I've uploaded the patched boot.img for firmware G_S1SAS32.47_77_2 so you can save some time and skip step 1 and go straight to flashing the patched boot.img hope this helps.

I gave up on this handset as with it's Mediatek innards there won't be any future Custom ROM options.

traceroute87 said:
I was successfully able to root using this guide.
[Guide][Root] Magisk without TWRP on Android P
Via Magisk Manager: This method does not need root, and also does not require a custom recovery. However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode...
forum.xda-developers.com
I've uploaded the patched boot.img so you can save some time and skip step 1 and go straight to flashing the patched boot.img hope this helps.
Click to expand...
Click to collapse
Oh thank you! I tried to do the same thing but i got an error each time. I'll try your boot.img

traceroute87 said:
I was successfully able to root using this guide.
[Guide][Root] Magisk without TWRP on Android P
Via Magisk Manager: This method does not need root, and also does not require a custom recovery. However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode...
forum.xda-developers.com
I've uploaded the patched boot.img so you can save some time and skip step 1 and go straight to flashing the patched boot.img hope this helps.
Click to expand...
Click to collapse
I still get this error on fastboot:
sending 'boot' (40960 KB)...
OKAY [ 1.187s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 1.202s

enaykey said:
I still get this error on fastboot:
sending 'boot' (40960 KB)...
OKAY [ 1.187s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 1.202s
Click to expand...
Click to collapse
hmm.
try: fastboot flash boot_a boot.img
or: fastboot flash boot_b boot.img

traceroute87 said:
hmm.
try: fastboot flash boot_a boot.img
or: fastboot flash boot_b boot.img
Click to expand...
Click to collapse
Oh, it worked! Thank you so much. You saved my phone.

traceroute87 said:
I was successfully able to root using this guide.
[Guide][Root] Magisk without TWRP on Android P
Via Magisk Manager: This method does not need root, and also does not require a custom recovery. However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode...
forum.xda-developers.com
I've uploaded the patched boot.img so you can save some time and skip step 1 and go straight to flashing the patched boot.img hope this helps.
Click to expand...
Click to collapse
This is awesome.
Would you happen to have a stock firmware for austin RETUS? I can't find one on lolinet.

slipchicken said:
This is awesome.
Would you happen to have a stock firmware for austin RETUS? I can't find one on lolinet.
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmwar...RSU_QCOM_regulatory-DEFAULT_cid50_CFC.xml.zip
This is stock for XT2213-3

Old_Mil said:
I gave up on this handset as with it's Mediatek innards there won't be any future Custom ROM options.
Click to expand...
Click to collapse
I have a WIP lineage/aosp device tree up on github, still have a few small things to sort out on the device tree and probably another week or two away from a workable vendor tree. Motorola has released the source for the kernel along with the out of tree modules, currently trying to get them to release an aosp build readme since this is my first mediatek device and there isn't much info on porting roms to said soc, but there is always gsi's

damnthefall said:
https://mirrors.lolinet.com/firmwar...RSU_QCOM_regulatory-DEFAULT_cid50_CFC.xml.zip
This is stock for XT2213-3
Click to expand...
Click to collapse
Is this one valid for those that bought directly from Moto? It's stating subsidy for T-Mobile and not seeing a standard official release on lolinet . . .

zinjashike said:
Is this one valid for those that bought directly from Moto? It's stating subsidy for T-Mobile and not seeing a standard official release on lolinet . . .
Click to expand...
Click to collapse
This is just for the T-Mobile variant. The one bought directly from Moto has different specs IIRC

Okay, I thankfully remembered that one can get stock roms from Moto using the Rescue Smart Assistant so did that.
Now I'm just stuck waiting till Motorola tells me phone I can use the OEM Bootloader Unlock . . . so much for a fast upgrade >_<

zinjashike said:
Okay, I thankfully remembered that one can get stock roms from Moto using the Rescue Smart Assistant so did that.
Now I'm just stuck waiting till Motorola tells me phone I can use the OEM Bootloader Unlock . . . so much for a fast upgrade >_<
Click to expand...
Click to collapse
Mine only took like 24 hours before the option could be enabled. I just want to go back to a qcom soc because not having any bsp for this phone is killing me

damnthefall said:
Mine only took like 24 hours before the option could be enabled. I just want to go back to a qcom soc because not having any bsp for this phone is killing me
Click to expand...
Click to collapse
I'm not familiar, what is BSP?
Just want to make sure I'm not biting myself in the ass here keeping it. The only things I really need unlocked BL/root for is CF.Lumen, some tasker stuff, proper full backups, and call recording for work/business >_>

zinjashike said:
I'm not familiar, what is BSP?
Just want to make sure I'm not biting myself in the ass here keeping it. The only things I really need unlocked BL/root for is CF.Lumen, some tasker stuff, proper full backups, and call recording for work/business >_>
Click to expand...
Click to collapse
BSP=Board Support Package(makes custom ROM development much easier) you should be just fine doing the standard magisk root, it's what I did and I haven't had any issues with except that now whenever I reboot my phone it boots into Meta mode instead of back to system. So when I reboot I have to make sure to hold vol down to get the bootloader and then boot normally from there. I'm guessing it has something to do with verified boot because if I reflash the factory boot image it reboots normally, I tried flashing vbmeta with disable verity and verification, but after doing that the sim card reader stopped working lol

Anyone found a root for the moto g stylus 5G xt2131-1? Just purchased it factory unlocked.