When I switch on my device. I always boot to recovery. If I select reboot it also reboot to recovery.if I goto twrp and choose reboot to system it also reboot to recovery again if I need to boot to system I have to boot into bootloader and choose normal power up... What to doo
The problem comes after I flashed twrp via fast boot on StockRom
Also in cm11 plz help
I'm currently on Cm11 stable build
XT1022
Adarsh1998 said:
When I switch on my device. I always boot to recovery. If I select reboot it also reboot to recovery.if I goto twrp and choose reboot to system it also reboot to recovery again if I need to boot to system I have to boot into bootloader and choose normal power up... What to doo
The problem comes after I flashed twrp via fast boot on StockRom
Also in cm11 plz help
I'm currently on Cm11 stable build
XT1022
Click to expand...
Click to collapse
You unlock your bootloader?
if no, apply the steps in http://forum.xda-developers.com/showthread.php?t=2753110
If not work, go back to stock 4.4.4, not 4.4.2 and repeat the process to unlock bootloader and flash twrp and cm11 again.
noRetail said:
You unlock your bootloader?
if no, apply the steps in http://forum.xda-developers.com/showthread.php?t=2753110
If not work, go back to stock 4.4.4, not 4.4.2 and repeat the process to unlock bootloader and flash twrp and cm11 again.
Click to expand...
Click to collapse
I unlocked bootloader
Without unlocking bootloader there is no way to root without root there is nonway to flash cm11... LoL
Adarsh1998 said:
I unlocked bootloader
Without unlocking bootloader there is no way to root without root there is nonway to flash cm11... LoL
Click to expand...
Click to collapse
OK, with bootloder unlock try restore stock recovery in http://forum.xda-developers.com/moto-e/general/stock-recovery-recovery-img-t3031437
If not work try restore entirely rom stock 4.4.4 (I prefer this action)
After this apply the twrp and cm11, or, if you like lollipop?
Steps followed by me to get lillipop working 100% in xt1021 brazillian retail.
Get the zip file in https://mega.co.nz/#!wVsQmajI!tmEkvt...jtAS2GwF5fncws (Get stock 4.4.4 for your country)
Extract the files
In Fastboot mode apply the commands bellow in root user (I use Linux Mint 64)
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Apply your Google Account
Get the zip file in https://mega.co.nz/#!IJ9SVCaT!watj3-...GnKkg8od_kthLw (Get SOAK OTA for your country)
Put this zip file in root internal memory
In Fone go to Settings, About Phone, System Updates
After detect and apply update your Moto E have Lollipop 5.0.2
if you have a bootloader unlocked warning in boot phone after update to lillipop
Get the zip file in https://mega.co.nz/#!MFVkCQ7J!W7SmL3...rWDXoHW5hz6l44
unzip the file
In Fastboot mode apply the commands bellow in root user (I use Linux Mint 64)
commands :
fastboot flash logo logo.bin
fastboot reboot
noRetail said:
OK, with bootloder unlock try restore stock recovery in http://forum.xda-developers.com/moto-e/general/stock-recovery-recovery-img-t3031437
If not work try restore entirely rom stock 4.4.4 (I prefer this action)
After this apply the twrp and cm11, or, if you like lollipop?
Steps followed by me to get lillipop working 100% in xt1021 brazillian retail.
Get the zip file in https://mega.co.nz/#!wVsQmajI!tmEkvt...jtAS2GwF5fncws (Get stock 4.4.4 for your country)
Extract the files
In Fastboot mode apply the commands bellow in root user (I use Linux Mint 64)
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Apply your Google Account
Get the zip file in https://mega.co.nz/#!IJ9SVCaT!watj3-...GnKkg8od_kthLw (Get SOAK OTA for your country)
Put this zip file in root internal memory
In Fone go to Settings, About Phone, System Updates
After detect and apply update your Moto E have Lollipop 5.0.2
if you have a bootloader unlocked warning in boot phone after update to lillipop
Get the zip file in https://mega.co.nz/#!MFVkCQ7J!W7SmL3...rWDXoHW5hz6l44
unzip the file
In Fastboot mode apply the commands bellow in root user (I use Linux Mint 64)
commands :
fastboot flash logo logo.bin
fastboot reboot
Click to expand...
Click to collapse
I think u miss understood my question.
Im able to boot into all rom. Cm11, stock. 4.4.2, stock 4.4.4. Stock 5.0.1 but the problem is that when i press reboot the phone goes to the recovery. in recovery i hv to goto reboot bootloader option in bootloader i hv to choose normal powerup option
Adarsh1998 said:
I think u miss understood my question.
Im able to boot into all rom. Cm11, stock. 4.4.2, stock 4.4.4. Stock 5.0.1 but the problem is that when i press reboot the phone goes to the recovery. in recovery i hv to goto reboot bootloader option in bootloader i hv to choose normal powerup option
Click to expand...
Click to collapse
Yes, i don't have unserstand, sorry my mistake, you try factory reset?
noRetail said:
Yes, i don't have unserstand, sorry my mistake, you try factory reset?
Click to expand...
Click to collapse
All i tried no use
Adarsh1998 said:
All i tried no use
Click to expand...
Click to collapse
this is bad, I try to go back to stock 4.4.4 to clean the phone and if everything is ok would install the cm11 again, I see no other solution, sorry not help much.
Adarsh1998 said:
When I switch on my device. I always boot to recovery. If I select reboot it also reboot to recovery.if I goto twrp and choose reboot to system it also reboot to recovery again if I need to boot to system I have to boot into bootloader and choose normal power up... What to doo
The problem comes after I flashed twrp via fast boot on StockRom
Also in cm11 plz help
I'm currently on Cm11 stable build
XT1022
Click to expand...
Click to collapse
Try wipe partition system, this may work
GabrielRW said:
Try wipe partition system, this may work
Click to expand...
Click to collapse
How in twrp?
flash kernel again
Adarsh1998 said:
When I switch on my device. I always boot to recovery. If I select reboot it also reboot to recovery.if I goto twrp and choose reboot to system it also reboot to recovery again if I need to boot to system I have to boot into bootloader and choose normal power up... What to doo
The problem comes after I flashed twrp via fast boot on StockRom
Also in cm11 plz help
I'm currently on Cm11 stable build
XT1022
Click to expand...
Click to collapse
i did the same thing before.
flash kernel with proper command
you have flashed recovery with kernel command maybe
Adarsh1998 said:
How in twrp?
Click to expand...
Click to collapse
Yes, go to advanced wipe, make a full wipe except sdcard and flash again the ROM. Sorry for my bad english
kushal.purkar said:
i did the same thing before.
flash kernel with proper command
you have flashed recovery with kernel command maybe
Click to expand...
Click to collapse
How to pl, help
Where is link?
this may help
Adarsh1998 said:
How to pl, help
Where is link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-e/development/downgrade-5-0-x-to-4-4-4-stock-firmware-t3031073
Related
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Fastboot flash the images. Then reroot.
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
TenderloinShadow said:
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56921581&postcount=33
That post left out flashing recovery. The download should have 6 files. I flashed recovery at the end (but I don't think it matters how you flash the files, I could be wrong though).
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
di11igaf said:
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
Click to expand...
Click to collapse
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
ericplatham said:
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
Click to expand...
Click to collapse
You're right, now that I think about it, I believe I had to do that as well last time I flashed a factory image.
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
GatorsUF said:
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
Click to expand...
Click to collapse
maybe I'll write up a guide, but download the factory image, extract it. In there is a zip file, extract it too. Then Google 15 second adb install xda. That'll set up fastboot on your pc. Then boot into the bootloader and in a command window opened in the folder where the bootloader image is located run the commands:
fastboot flash bootloader bootloader.img. Note, use the full name of the bootloader.img
fastboot reboot-bootloader
fastboot -w
Open the folder where the boot, system, cache, system, and vendor images are located. Open a command window in that folder and run the commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Then you're done
Click to expand...
Click to collapse
He will still have to reroot and flash custom recovery... but you got 95% of the process :laugh:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
rank78 said:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
Click to expand...
Click to collapse
Since its a small update you could probably get by just flashing the system and boot images. But I haven't tried it
Sent from my Nexus 5 using XDA Free mobile app
I'd flash everything as described to be safe, I just prefer simply flashing a zip and moving on.
Will updating thru adb wipe my device?
GatorsUF said:
Will updating thru adb wipe my device?
Click to expand...
Click to collapse
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I have actually flashed a few times thru fastboot in the past so I'm not totally lost on the idea. I've always used tibu in the past, will Google restore my data too?
TenderloinShadow said:
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Click to expand...
Click to collapse
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
fhem said:
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
Click to expand...
Click to collapse
Why erase recovery twice?
Just dont flash stock recovery
fhem said:
STEP #1
fastboot flash bootloader {bootloader.img}
Click to expand...
Click to collapse
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Double_U said:
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Click to expand...
Click to collapse
Hi, Double_U...
Are you sure you've typed the EXACT command..?
Code:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
Reboot the bootloader, enter fastboot, and try again.
Rgrds,
Ged.
I tried to flash a downgrade image to my moto e 2nd gen. Now Im stuck in bootloader and a warning message for unlocked bootloder. Ive tried to flash logo.bin, and other images aswell with no luck. It keeps asking me to install a valid signed images, I don't know where to find these images. Please help!
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
squid2 said:
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
Click to expand...
Click to collapse
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
pemhak said:
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
Click to expand...
Click to collapse
Hmm, so you went from a newer 5.0.2 build to an old 5.0.2 build? What were you downgrading to?
Go to this folder: https://mega.nz/#F!rMIhDLgR!oq5Cz_XbgZLEEysmqoYtcA
Navigate to Surnia ->5.0.2
Look for the file XT1524_RETEUALL_MOTOE2... (it's near the middle of the list)
Download and try flashing everything it in using fastboot.
squid2 said:
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
Click to expand...
Click to collapse
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
I got my device back!! I did succeed to flash it with this rom "surnia_stock_5.0.2.zip" with TWRP. I did not have the patience to wait at the Motorola logo when booting, I have to wait 2-3 min and 2-3 min for services to start. for the device to boot. But now it doesn't register any sim card when at desktop?!?
squid2 said:
Hmm, so you went from a newer 5.0.2 build to an old 5.0.2 build? What were you downgrading to?
Go to this folder:
Navigate to Surnia ->5.0.2
Look for the file XT1524_RETEUALL_MOTOE2... (it's near the middle of the list)
Download and try flashing everything it in using fastboot.
Click to expand...
Click to collapse
I was downgrading to kitkat 4.4.4 due to poor battery in lollipop 5.0.2. I'm downloading a xt1524reteuall rom right now but ir is going slowly.
pemhak said:
I was downgrading to kitkat 4.4.4 due to poor battery in lollipop 5.0.2. I'm downloading a xt1524reteuall rom right now but ir is going slowly.
Click to expand...
Click to collapse
Oh, you must have flashed something really wrong then. There are no 4.4.4 ROMs for this device. You would have flashed something totally incompatible and highly risky if you flashed 4.4.4 from somewhere. That may have wrecked your modem software too. Download and flash the proper XT1524-specific software with the correct modem. If you are unhappy with the performance of the stock ROM, you can flash scritch007's CM12.1.
squid2 said:
Oh, you must have flashed something really wrong then. There are no 4.4.4 ROMs for this device. You would have flashed something totally incompatible and highly risky if you flashed 4.4.4 from somewhere. That may have wrecked your modem software too. Download and flash the proper XT1524-specific software with the correct modem. If you are unhappy with the performance of the stock ROM, you can flash scritch007's CM12.1.
Click to expand...
Click to collapse
Ok, thanks. I will wait for download to complete and flash that image.
pemhak said:
Ok, thanks. I will wait for download to complete and flash that image.
Click to expand...
Click to collapse
Hi! Did you solve your problem? I'm kind of stuck on same problem and with no working solution yet.
EDIT: I tried the @squid2 with no success. Maybe I will send the phone to waranty....
Noeljunior said:
Hi! Did you solve your problem? I'm kind of stuck on same problem and with no working solution yet.
EDIT: I tried the @squid2 with no success. Maybe I will send the phone to waranty....
Click to expand...
Click to collapse
I did solve the problem with these steps.
1. Find and download the files for your region.
2. Unzip files to a folder with fastboot and adb.
3. Create stock.bat with these commands and run stock.bat within the same folder as above files.
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
fastboot reboot
(4. I needed to reunlock my Moto E 2nd Gen at Motorolas site, because i did relock it.)
5. Get into bootloader menu and flash this TWRP image (i can email it to you) within the same folder and flash it with fastboot.
6. Restart phone. Wait 2-3 minutes so it boots into android.
7. Hope I made it clear enough to follow the instructions, if you got questions please reply and I try to answer them. Sorry for my poor english.
pemhak said:
I did solve the problem with these steps.
1. Find and download the files for your region.
2. Unzip files to a folder with fastboot and adb.
3. Create stock.bat with these commands and run stock.bat within the same folder as above files.
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
fastboot reboot
(4. I needed to reunlock my Moto E 2nd Gen at Motorolas site, because i did relock it.)
5. Get into bootloader menu and flash this TWRP image (i can email it to you) within the same folder and flash it with fastboot.
6. Restart phone. Wait 2-3 minutes so it boots into android.
7. Hope I made it clear enough to follow the instructions, if you got questions please reply and I try to answer them. Sorry for my poor english.
Click to expand...
Click to collapse
And I'm back with my Moto E! Thank you! I wasn't doing some of those commands and with all those commands it works! Thank you!
Your bootloader must be unlocked.
You can't lock the bootloader, to do this you will need a signed firmware from Motorola (and no one found yet). Instead you can use Magisk to hide the unlocked bootloader, bypass SafetyNet and be able to use Google Pay, for example.
You will not get OTA updates from Motorola even if you somehow lock the bootloader because your phone is registered forever to the "retcn" software update channel, instead of "retail" or "retbr".
Recommended: set your Platform Tools (adb and fastboot) system wide using this guide
https://forum.xda-developers.com/android/software/guide-how-to-set-fastboot-adb-to-wide-t3591240
Tested for updating from Oreo stock without wipe.
Steps for clean flashing or update
- Place the suitable script attached on the extracted ROM folder and flash (these scripts are only for XT1710-08 variant to prevent lost modem signal)
- After all the commands succeeded, wait for a full reboot (because of encryption)
- Flash TWRP
- Flash Magisk normally through TWRP
- Be happy
Firmware (you can use this on other XT1710 variants)
Version: PPS29.133-30 (Android 9.0 Pie)
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Other versions:
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
TWRP
https://forum.xda-developers.com/z2-play/development/-t3715660
Magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Motorola drivers https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,153
Google SDK Platform Tools https://developer.android.com/studio/releases/platform-tools
Commands for flashing and wipe
PS: the difference from the official `flashfile.xml` commands is that it doesn't contains `fastboot erase modemst1` and `fastboot erase modemst2`
Code:
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 flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Commands for flashing without wipe (update)
PS: the only difference from the previous one is that it doesn't contains `fastboot erase userdata`
Code:
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 flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Thanks to
@eqbirvin
@Junior Passos
@HTCDevil
Hello. If I use your script is unzipped the rom with update to August 2018 is the same? They are currently on custom rom Firehound! I would like to go back to the Motorola Blur retail. Do I have to give all the commands from fastboot?
cuciu70 said:
Hello. If I use your script is unzipped the rom with update to August 2018 is the same? They are currently on custom rom Firehound! I would like to go back to the Motorola Blur retail. Do I have to give all the commands from fastboot?
Click to expand...
Click to collapse
Yes! To go back to Motorola stock ROM you must follow this tutorial to make a clean flash, using the flash-wipe script.
my post was wrong, Moderators please delete my post.
Did'nt know i can't delete my own post.
felipecassiors said:
Yes! To go back to Motorola stock ROM you must follow this tutorial to make a clean flash, using the flash-wipe script.
Click to expand...
Click to collapse
the password does not work.
I tried to open the file with 7zip and zip extractor pro. I enter the password!
wrong password.
cuciu70 said:
the password does not work.
I tried to open the file with 7zip and zip extractor pro. I enter the password!
wrong password.
Click to expand...
Click to collapse
Firmware:
https://drive.google.com/open?id=1rcgUvLG5c7l9jH8AzuTg3WPJnORQ6VlY
The password is
Code:
MotorolaFirmwaresLB
I use WinRAR, but 7-Zip should work. Try again please, here is working.
Would it be easy to update the system with the latest patch? I have magisk installed with system from April patch. If so what how would be the procedure?
Followed all the steps and got it working. Thanks so much, the original software on this version of the phone is terrible!
One thing, like a few others, my fingerprint sensor isn't working. Is it as simple as a wipe after install?
pjcons said:
Followed all the steps and got it working. Thanks so much, the original software on this version of the phone is terrible!
One thing, like a few others, my fingerprint sensor isn't working. Is it as simple as a wipe after install?
Click to expand...
Click to collapse
Take a look at this post friend:
https://forum.xda-developers.com/z2...reo-retail-via-fastboot-t3786153/post76486376
Try to flash again but evading this 4 commands.
felipecassiors said:
Take a look at this post friend:
https://forum.xda-developers.com/z2...reo-retail-via-fastboot-t3786153/post76486376
Try to flash again but evading this 4 commands.
Click to expand...
Click to collapse
Yes I took those out when flashed and still no fp sensor. Thanks for sending on though. I read everything b4 flash but still no fp sensor.
But I didn't wipe 1st so might flash again and wipe 1st?
Everything else working 100% :good:
pjcons said:
Yes I took those out when flashed and still no fp sensor. Thanks for sending on though. I read everything b4 flash but still no fp sensor.
But I didn't wipe 1st so might flash again and wipe 1st?
Everything else working 100% :good:
Click to expand...
Click to collapse
If you can, please try wiping in first. If still doesn't work, the procedure to solve this is:
- Flash the original ROM (that ugly ZUI one) to get it working again
- Flash the ROM on this thread, wiping, evading that 4 commands
I can help you to find the ZUI ROM if you need.
felipecassiors said:
If you can, please try wiping in first. If still doesn't work, the procedure to solve this is:
- Flash the original ROM (that ugly ZUI one) to get it working again
- Flash the ROM on this thread, wiping, evading that 4 commands
I can help you to find the ZUI ROM if you need.
Click to expand...
Click to collapse
Cheers mate. If u can send me a link to the very ugly Zui rom just in case would be great.
pjcons said:
Cheers mate. If u can send me a link to the very ugly Zui rom just in case would be great.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=1322778262903986742
Just make sure your device is XT1710-08
Tested on a XT1710-06 full wipe and it works great, because i wanted to do and update and i goot bootloop.
Just in case someone find this, im from México, I flashed this fastboot rom and installed Magisk to get root, used the Canary build to make it work with my fav games that are Fate go and Pokemon go (spoof) and it works like a charm, thanks.
felipecassiors said:
https://androidfilehost.com/?fid=1322778262903986742
Just make sure your device is XT1710-08
Click to expand...
Click to collapse
Yep, it's an XT1710-08 for sure! Thanks again...
pjcons said:
Yep, it's an XT1710-08 for sure! Thanks again...
Click to expand...
Click to collapse
Friend, use the tutorial of this thread, but instead of that script, use this attached to flash the ZUI stock ROM.
8bitcode said:
Tested on a XT1710-06 full wipe and it works great, because i wanted to do and update and i goot bootloop.
Just in case someone find this, im from México, I flashed this fastboot rom and installed Magisk to get root, used the Canary build to make it work with my fav games that are Fate go and Pokemon go (spoof) and it works like a charm, thanks.
Click to expand...
Click to collapse
Friend, for models other than XT1710-08 (outside China), you can use this script attached. It is more recommended.
Thank you for the feedback!
felipecassiors said:
Friend, for models other than XT1710-08 (outside China), you can use this script attached. It is more recommended.
Thank you for the feedback!
Click to expand...
Click to collapse
Hey I got back to ZUI - the Chinese ROM came up. Fingerprint working. So rebooted into BL and flashed the firmware as per OP. Again, no FP sensor.
I'm gonna try again and wipe after install ZUI, BEFORE flash and wipe Oreo.
[2nd try no better??]
It flashes ok but FP sensor just won't work. Everything else working. When you say "Flash the ROM on this thread, wiping, evading that 4 commands" I use the flash and wipe script and remove the 4 commands (the erase modem seem to have been removed already from the script). Any ideas, I'm so close! Have flashed back and forth a few times tonight. It's fun though! Cheers!
pjcons said:
Hey I got back to ZUI - the Chinese ROM came up. Fingerprint working. So rebooted into BL and flashed the firmware as per OP. Again, no FP sensor.
I'm gonna try again and wipe after install ZUI, BEFORE flash and wipe Oreo.
[2nd try no better??]
It flashes ok but FP sensor just won't work. Everything else working. When you say "Flash the ROM on this thread, wiping, evading that 4 commands" I use the flash and wipe script and remove the 4 commands (the erase modem seem to have been removed already from the script). Any ideas, I'm so close! Have flashed back and forth a few times tonight. It's fun though! Cheers!
Click to expand...
Click to collapse
Mine XT1710-08 fingerprint sensor works without removing the 4 commands, I just remove the 2 erase modem (already removed in the flash scripts). Anyway, try to install the ROM of this thread (https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153) and see if it work for you. Please post here if you have news about it.
Rooting
I did all the steps and completely reinstalled android 8.0 on my moto z2 play, I then got twrp and tried flashing magisk 17.1, I got stuck in a bootloop but managed to flash the whole thing again, which solved the problem. To make sure this doesn't happen again, could you please state the steps for rooting. I cant remember if it was because I did not input the code into the terminal. When I input the code am I supposed to get a response or message, because it just stays bank?
Thank you
Hi, Android 9.0 for Albus is available here >> Direct Download <<
Just install with ADB Fastboot
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase carrier
fastboot erase DDR
fastboot reboot
Ps: Clean Install is recommend
(Retail version)
Enjoy!!!
I'AM NOT RESPONSIBLE IF YOUR CELLPHONE TURNS IN A BRICK AFTER THIS PROCESS
I think you have to do a twrp backup and then restore it.it's strange but works
Inviato dal mio GT-N5120 utilizzando Tapatalk
can we use this update for the Indian version of Z2play, software channel: RETIN. Bootloader: locked. if yes, then is there any problem with the mobile network?
JulioCeesarC said:
Hi, Android 9.0 for Albus is available here >> Direct Download <<
Just install with ADB Fastboot
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase carrier
fastboot erase DDR
fastboot reboot
Ps: Clean Install is recommend
(Retail version)
Enjoy!!!
I'AM NOT RESPONSIBLE IF YOUR CELLPHONE TURNS IN A BRICK AFTER THIS PROCESS
Click to expand...
Click to collapse
I blindly flashed the above mentioned pie rom on my moto z2 play xt1710-02 it flashed gpt and bootloader and failed the rest of the commands returned with errors
Now stuck at fastboot mode warning of startup failed @JulioCeesarC
Please help me get out of here
Bootloader is locked and i was at latest oreo update probably ods27.12-42-14
I also tried to flash above oreo image but it returns with error saying security downgrade
junejo46726 said:
I blindly flashed the above mentioned pie rom on my moto z2 play xt1710-02 it flashed gpt and bootloader and failed the rest of the commands returned with errors
Now stuck at fastboot mode warning of startup failed @JulioCeesarC
Please help me get out of here
Bootloader is locked and i was at latest oreo update probably ods27.12-42-14
I also tried to flash above oreo image but it returns with error saying security downgrade
Click to expand...
Click to collapse
try to install 8.0 again and after that unlock bootloader and try to install 9.0 again with bootloader unlocked
ghost.deathrider said:
can we use this update for the Indian version of Z2play, software channel: RETIN. Bootloader: locked. if yes, then is there any problem with the mobile network?
Click to expand...
Click to collapse
I recomend bootloader unlocked for this process
junejo46726 said:
Hi, Android 9.0 for Albus is available here >> Direct Download <<
Just install with ADB Fastboot
I blindly flashed the above mentioned pie rom on my moto z2 play xt1710-02 it flashed gpt and bootloader and failed the rest of the commands returned with errors
Now stuck at fastboot mode warning of startup failed @JulioCeesarC
Please help me get out of here
Bootloader is locked and i was at latest oreo update probably ods27.12-42-14
I also tried to flash above oreo image but it returns with error saying security downgrade
Click to expand...
Click to collapse
Before you unlock:
Try fastboot "Boot" TWRP, if you can, it might be possible to use one of the TWRP backups to fix your phone. There is another thread with TWRP backups of stock.
If successful boot, restore system partition last and separately.
XT1710-09 bootloader unlocked, installed 9.0 without any issue! Everything ok with twrp-3.2.3-0-albus recovery, but got bootloop trying to root with Magisk 20.0. Any tip?
kain83 said:
XT1710-09 bootloader unlocked, installed 9.0 without any issue! Everything ok with twrp-3.2.3-0-albus recovery, but got bootloop trying to root with Magisk 20.0. Any tip?
Click to expand...
Click to collapse
did you try cleaning your cache? I used 19.3.
kewlzter said:
did you try cleaning your cache? I used 19.3.
Click to expand...
Click to collapse
I didn't indeed. I'm gonna give it a try, thanks
EDIT: it works!! So installed 19.3 version and wiped cache/dalvik, then reboot. So far so good, many thanks!!
keeps saying waiting for device
hindraftv said:
keeps saying waiting for device
Click to expand...
Click to collapse
Phone is either not connected, or in the wrong mode.
Make sure the phone is in Boot Loader. Unplug and replug USB.
ghost.deathrider said:
can we use this update for the Indian version of Z2play, software channel: RETIN. Bootloader: locked. if yes, then is there any problem with the mobile network?
Click to expand...
Click to collapse
Yes, i tried both the US version and the Brazil version and the Brazil version works. I'm on Vodafone India and everything works perfectly fine on android pie.
However, after several trials and errors, I realized there are two commands that you shouldn't run when flashing pie on the Indian variant. They are:
1) flashboot erase userdata
2) flashboot erase carrier
Special Thanks to @Junior Passos
reallydan said:
Yes, i tried both the US version and the Brazil version and the Brazil version works. I'm on Vodafone India and everything works perfectly fine on android pie.
However, after several trials and errors, I realized there are two commands that you shouldn't run when flashing pie on the Indian variant. They are:
1) flashboot erase userdata
2) flashboot erase carrier
Special Thanks to @Junior Passos
Click to expand...
Click to collapse
Clean flash or dirty flash?
rayudu123 said:
Clean flash or dirty flash?
Click to expand...
Click to collapse
Clean flash
reallydan said:
Clean flash
Click to expand...
Click to collapse
Is it possible to flash indian pie version after release of pie in india??? Or do we face any problem in flashing??
Everything works except dark theme. Any fix?
kewlzter said:
Phone is either not connected, or in the wrong mode.
Make sure the phone is in Boot Loader. Unplug and replug USB.
Click to expand...
Click to collapse
It is connected.. I have Moto Z2 Play - Build Number OPSS27.76.12-42-13 (Baseband M8953P_50.59.07.96 ALBUS_NA_CUST_
are you able to provide step by step guide, if you don't mind
hindraftv said:
It is connected.. I have Moto Z2 Play - Build Number OPSS27.76.12-42-13 (Baseband M8953P_50.59.07.96 ALBUS_NA_CUST_
are you able to provide step by step guide, if you don't mind
Click to expand...
Click to collapse
Why sure...
Step 1: you get yourself a usb cable.
Step 2: you plug one end into your computer.
Step 3: plug the other end into your phone..
glad to help
kewlzter said:
Before you unlock:
Try fastboot "Boot" TWRP, if you can, it might be possible to use one of the TWRP backups to fix your phone. There is another thread with TWRP backups of stock.
If successful boot, restore system partition last and separately.
Click to expand...
Click to collapse
I also tried but fastboot saying can not load twrp @JulioCeesarC
I would like to share my experienced how to unbricked my phone that stock on fastboot mode.why my phone is brick? The reason why my phone brick just because i restore the wrong system with the other vendor from china to miuimix and after restore it, it stock on fastboot mode unable to recover backup or to load in recovery mode. It didn't also turn off. l try to use miflash tool but it didn't work because of authorization not match to my phone, i tried other fastboot rom but it didnt work.. Try to boot twrp using fastboot boot but it didn't show any. I came up with the idea to flash. Img using cmd into the system that i restore, begin with the boot.img nothing will happen. Until i flash the vbmeta.img, then it begin to show boot img and eventually access twrp. I wiped everything and flash again a brandnew rom miui12 and it works well now.. Hope it will help to others to have an idea to unbrick there phone. ☺☺☺
flamedrops said:
I would like to share my experienced how to unbricked my phone that stock on fastboot mode.why my phone is brick? The reason why my phone brick just because i restore the wrong system with the other vendor from china to miuimix and after restore it, it stock on fastboot mode unable to recover backup or to load in recovery mode. It didn't also turn off. l try to use miflash tool but it didn't work because of authorization not match to my phone, i tried other fastboot rom but it didnt work.. Try to boot twrp using fastboot boot but it didn't show any. I came up with the idea to flash. Img using cmd into the system that i restore, begin with the boot.img nothing will happen. Until i flash the vbmeta.img, then it begin to show boot img and eventually access twrp. I wiped everything and flash again a brandnew rom miui12 and it works well now.. Hope it will help to others to have an idea to unbrick there phone.
Click to expand...
Click to collapse
Could you explain? My phone is stuck at fastboot and my pc doesn't detect the phone.
if u could access your phone via fastboot / adb then it wasn't a hardbrick , just a softbrick
TahmidZee said:
Could you explain? My phone is stuck at fastboot and my pc doesn't detect the phone.
Click to expand...
Click to collapse
You should check first the driver of your computer. Make sure you have the driver of your phone to your computer. After that you can check your device via adb by using commnd on cmd "adb devices".
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
w595shubham said:
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
VERY VERY THANX A LOT MAN...THX THX THX:highfive:
flamedrops said:
I would like to share my experienced how to unbricked my phone that stock on fastboot mode.why my phone is brick? The reason why my phone brick just because i restore the wrong system with the other vendor from china to miuimix and after restore it, it stock on fastboot mode unable to recover backup or to load in recovery mode. It didn't also turn off. l try to use miflash tool but it didn't work because of authorization not match to my phone, i tried other fastboot rom but it didnt work.. Try to boot twrp using fastboot boot but it didn't show any. I came up with the idea to flash. Img using cmd into the system that i restore, begin with the boot.img nothing will happen. Until i flash the vbmeta.img, then it begin to show boot img and eventually access twrp. I wiped everything and flash again a brandnew rom miui12 and it works well now.. Hope it will help to others to have an idea to unbrick there phone.
Click to expand...
Click to collapse
Can u please explain it. I am stuck with the same problem. I got success in flashing fastboot rom via miflash tool but it's still stuck in fastboot.
Thanks God Bless You.
---------- Post added at 05:01 PM ---------- Previous post was at 04:36 PM ----------
Deaddo6 said:
VERY VERY THANX A LOT MAN...THX THX THX:highfive:
Click to expand...
Click to collapse
This Helped You guys are angel
w595shubham said:
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
I have the same problem. I tried also this one, but nothing.
Everything goes ok in CMD, but when I type:
fastboot boot twrp.img
I get:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
I still can't go in Recovery, neither turn off the phone. How solve this?!
dix93 said:
I have the same problem. I tried also this one, but nothing.
Everything goes ok in CMD, but when I type:
flash boot twrp.img
I get:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
I still can't go in Recovery, neither turn off the phone. How solve this?!
Click to expand...
Click to collapse
flash boot twrp.img?
What do you wanna do?
If you want to boot into TWRP it should be
Code:
fastboot boot recovery "name-of- recovery.img"
If you want to flash TWRP it should be
Code:
fastboot flash recovery "name-of-recovery.img"
Your command
fastboot flash boot twrp.img should flash the recovery image over the boot image?
If you want to boot into twrp you should use the command above.
As far as I know not every device/firmware is able to boot into TWRP. It seems other users were able to do so with a mi 9t so my advice would be:
- Try another usb port / cable.
- Check twice if you renamed the twrp image correctly
- Try another twrp version (older one or unofficial)
w595shubham said:
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
Wolfcity said:
flash boot twrp.img?
What do you wanna do?
If you want to boot into TWRP it should be
Code:
fastboot boot recovery "name-of- recovery.img"
If you want to flash TWRP it should be
Code:
fastboot flash recovery "name-of-recovery.img"
Your command
fastboot flash boot twrp.img should flash the recovery image over the boot image?
If you want to boot into twrp you should use the command above.
As far as I know not every device/firmware is able to boot into TWRP. It seems other users were able to do so with a mi 9t so my advice would be:
- Try another usb port / cable.
- Check twice if you renamed the twrp image correctly
- Try another twrp version (older one or unofficial)
Click to expand...
Click to collapse
Thank you. Actually I was confused in the transcript here, I meant fast boot instead of flash.
But I figured out to use XiaomiFlash Tool to install a ROM via fastboot, and then reinstall a recovery.
The popup camera is not working good with the XIAOMI official rom (It tries to close the cam even if it is already closed). Now I'm trying to install Havoc OS to try to solve those problem, but it demands me the miui v11.0.4 or new (error in twrp), even if I have the miui v12.... trying to figure out why
for the guys whome are stuck on fastboot, you may try "XiaoMiTool V2". this bought my Mi9T from fastboot to life.
make sure all the drivers are installed as well. what's better is install usb drivers, reboot computer, enable usb debugging, connect the phone to computer, select transfer data, wait till the computer completely setup your phone, turn off phone and connect to computer, wait till computer detects and setup, put the phone on fastboot mode and connect, check whether computer shows android device... once everything are confirmed then proceed with flasing.. :good::good:
w595shubham said:
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
This command - fastboot flash vbmeta worked.
(using a version from Redispade for Grus - mi9se)
Unbricked my bootloop (recovery) after upgrading from miui 12 (android 10) to 12.5 android 11.
thanks!