Develop Bugs

[GUIDE] How to manually upgrade firmware

First of all, this guide expects you to have some basic knowledge how to use fastboot, have working ADB/fastboot connection on your computer and understand the fact that this may brick your phone if you mess up.
I am NOT responsible for anything! This will wipe everything on your phone, so get backups if needed.
This guide is written for X720 and supplied files are ONLY for X720. Same procedure will work on X727, but you will have to get right files yourself.
All files are from stock 23S, just extracted, converted and repacked for your convenience.
Read the whole guide before doing anything. If you're unsure about anything, don't do it.
Here we go:
1. Download .zip containing files from Mega: https://mega.nz/#!5boxDYrL!_O-oD05yhiU5FbCmYuf47VH4Qar5RhV5LKwyHa39bWM
2. Extract files to path where you are able to flash them using fastboot (ie. same folder with fastboot)
3. Boot your phone to bootloader (Vol- & Power)
4. Flash everything:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format data <-- THIS WILL WIPE YOUR PHONE INCLUDING INTERNAL STORAGE
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash ddr ddr.mbn
fastboot flash cmnlib cmnlib.mbn
fastboot flash hyp hyp.mbn
fastboot flash pmic pmic.elf
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash xbl xbl.elf
fastboot flash keymaster keymaster.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash bluetooth BTFM.bin
fastboot flash devinfo devinfo.bin​5. Reboot, and let it boot up (takes some time)
6. Flash TWRP, wipe everything and install ROM (you have done this before, won't write a guide)
Credit for this guide goes to @darkobas

get error
C:\Program Files (x86)\Minimal ADB and Fastboot\x720_upgrade_23s>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi

I'm only guessing, since many have flashed this successfully, but maybe a bad download or incompatible fastboot.

Presterin said:
I'm only guessing, since many have flashed this successfully, but maybe a bad download or incompatible fastboot.
Click to expand...
Click to collapse
thx
i will try again.

Does anyone know which ones are safe to flash over the existing rom? I do not wish to wipe or break current rom.

I flashed everything except system and boot on top of Omni rom. Everything works great.

Does anyone know where I can get all of the files for my x727, I considered using the files from these OTA zips but I think some of the files are missing like the modem firmware and system.img.

On x720 some of the files were divided into scatter files, had to do some research to get them sorted.

Which fastboot is compatible with system.img? Because of me too :"target reported max download size of 536870912 bytes
Invalid sparse file format at header magi". minimal fast boot 1.42
Edit: ok..as long as the post I wrote started installation

Should/Can we install the latest fastboot? Mine is on shop altered 17s from over a year a go, which to be fair runs great; i just fancy a change.
Thanks

write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do

Any solution?
Hasancaktar said:
write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do
Click to expand...
Click to collapse
Stuck here as well

Hasancaktar said:
write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do
Click to expand...
Click to collapse
First, you provided no information. For example what phone do you have, what OS etc.
I am guessing EUI: It would be alot easier to simply flash the firmware for your device instead of flashing the exact same pieces of it one at a time. By extracting the bits from the full OS.
This is a old outdated guide that has way too many steps, and it was made a long time ago. Since the name of the guide is upgrading firmware, I assume thats what you are trying to do.
Since you are hoping to flash firmware, I will go ahead and assume that you already have your bootloader unlocked, have flashed Twrp and are rooted? You can accomplish updating your firmware with one step. > Go to Lineage 15.1 page and go to downloads section. Here you will see firmware listed, download the firmware to your device. One flash in Twrp will install all of the radio and sensor files needed.
Hint: always boot to recovery first, checking the Twrp installation boxes if present> this is a best practice to avoid bricking your phone.
If you have any issue after following the steps I mentioned ( Its possible because of the fastboot commends) You may need to clean wipe reset and start fresh
Before you begin disable any passwords and fingerprints within the system settings.
Boot to recovery > click wipe > advanced wipe > check cache ( not Dalvik, just cache) > swipe> press home key to return to main menu.
Click install >Navigate to your download folder and select firmware > swipe to install > clear cache again> reboot to recovery
If there are any check boxes to check for TWRP installation, check them >
Once back in recovery reboot to system > Finished

Great guide Thanks.
It saved me from a system wipe and a nightly not recognized by TWRP...:crying:

tsongming said:
First, you provided no information. For example what phone do you have, what OS etc.
I am guessing EUI: It would be alot easier to simply flash the firmware for your device instead of flashing the exact same pieces of it one at a time. By extracting the bits from the full OS.
This is a old outdated guide that has way too many steps, and it was made a long time ago. Since the name of the guide is upgrading firmware, I assume thats what you are trying to do.
Since you are hoping to flash firmware, I will go ahead and assume that you already have your bootloader unlocked, have flashed Twrp and are rooted? You can accomplish updating your firmware with one step. > Go to Lineage 15.1 page and go to downloads section. Here you will see firmware listed, download the firmware to your device. One flash in Twrp will install all of the radio and sensor files needed.
Hint: always boot to recovery first, checking the Twrp installation boxes if present> this is a best practice to avoid bricking your phone.
If you have any issue after following the steps I mentioned ( Its possible because of the fastboot commends) You may need to clean wipe reset and start fresh
Before you begin disable any passwords and fingerprints within the system settings.
Boot to recovery > click wipe > advanced wipe > check cache ( not Dalvik, just cache) > swipe> press home key to return to main menu.
Click install >Navigate to your download folder and select firmware > swipe to install > clear cache again> reboot to recovery
If there are any check boxes to check for TWRP installation, check them >
Once back in recovery reboot to system > Finished
Click to expand...
Click to collapse
I hate to be that person, but where the heck is the firmware dl's on the LIneage site? I did search and search. Thanks in advance.

jackpollard said:
I hate to be that person, but where the heck is the firmware dl's on the LIneage site? I did search and search. Thanks in advance.
Click to expand...
Click to collapse
https://forum.xda-developers.com/le-pro3/development/rom-lineageos-15-0-leeco-le-pro3-t3683720

amdol said:
https://forum.xda-developers.com/le-pro3/development/rom-lineageos-15-0-leeco-le-pro3-t3683720
Click to expand...
Click to collapse
Thank you! My flaw was looking on https://lineageos.org/ and not on here.

ajegile said:
get error
C:\Program Files (x86)\Minimal ADB and Fastboot\x720_upgrade_23s>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
get the same. iam not shure if i have the x722 or x720. they look same

Help getting start

Hello everyone,
I need help to start on flashing g7 play etc. In the old days I flashed phones like galaxy s3, s4, s5 and Note 4, but I'm not an expert in all of this.
Then I changed to iPhone 6s and now I want to come back to Android.
My goal:
de-googled moto g7 play
Android 9/10 -> would prefer 10
if possible -> root
My Device:
moto g7 play - XT1952-1
(bootloader unlocked)
---
Build number:
PPYs29.105-134-7
---
If have read most of the Threads for the g7 play, but at the moment I'm a little scared to brick it.
I have some questions:
1. I copied together for myself a Instruction (at the end of post). Could you tell me if this is OK like this, or do I have to do additional things before start?
2. In my copied instruction, at the point of flashing the GSI (Instruction ROM: -> Step 1)
What does "Dirty flashing your g7 play" mean? Do I have something additional to do, before following the instruction, or is dirty flashing the following instruction of the post?
3. Modded phh -> I have no information about this, could you explain, or give me link?
4. Overlay -> I have no information about this, could you explain, or give me link?
Thanks for your help
---
INSTRUCTION: (it is a quick&dirty instruction)
ROM:
lineage-17.1-20200309-UNOFFICIAL-treble_a64_bvN.img.xz
DTBO:
dtbo.img
(https://drive.google.com/file/d/1pV6-LbNoMG0J8vcyAWN0QWYGx67vxBgT/view?usp=sharing)
---
---
Instruction ROM:
step 1
Dirty flashing your g7 play -> what does that mean, what to do???
step 2
extract the gsi
step 3
put phone in fastboot mode and enter the commands
$ fastboot -w
$ fastboot flash dtbo dtbo.img
$ fastboot flash system [this is where you put your android 10 img]
$ fastboot boot twrp.img
(https://forum.xda-developers.com/g7-play/development/gsi-images-g7-play-t3980807
#1)
------------------------
TWRP:
twrp.img
---
Instruction TWRP:
step 1
Fastboot boot twrp.img
step 2
Copy twrp to your external sdcard, or use adb push twrp.img /tmp/twrp.img
step 3
Go to Advanced > install recovery ramdisk then navigate to tmp or your external sdcard and select the twrp.img you copied
step 4
Use wipe > format > type "yes" to continue then use reboot > recovery from twrp's menus
step 5
Once twrp starts up again, wipe data & system, make sure system is mounted, then flash a GSI. Flash the universal disabler afterwards.
If you get a failed to unmount error, manually mount all partitions and reflash whatever it errored on
step 6
Optional: Flash my modded phh for root. (Install the apk after.) Never use Magisk! It will fail to root, cause a bootloop, or break twrp
FIX navbar on a GSI:
$ adb root
$ adb shell
$ setprop persist.sys.phh.mainkeys 0
$ reboot
(https://forum.xda-developers.com/g7...ery-dirty-ported-twrp-g7-play-t3947205/page41
#403)
------------------------
Modded phh: -> LOS16 & 17
modded-phh-superuser.zip
phh-su.apk
(https://forum.xda-developers.com/showpost.php?p=81503713&postcount=240)
------------------------
Overlay: -> what does that mean???
treble-overlay-moto-g7play.apk.zip
(https://forum.xda-developers.com/g7...ery-dirty-ported-twrp-g7-play-t3947205/page41
#404)
------------------------

@ggg777
First make sure you install the stock OS to both slots, including the bootloader. I forgot to flash bootloader_b, and got stuck in EDL last week. You don't want that to happen and it's not easy to get out of. If you do this first, you will not have to worry about getting bricked.
Use my instructions found here for twrp. Inside the instructions you'll also find a link to my modded phh. Flashing a GSI can be done with twrp or fastboot. You also don't need the dtbo.img anymore since it's embedded inside of twrp. The trickiest part really, is just getting twrp installed. If you're using twrp to install a GSI, wipe system, data, dalvik, then flash the image to system. (You'll get a location prompt.) After installing a GSI, copy the overlay to /vendor/overlay, and set permissions on it to 0644, then reboot. Flash modded phh for root if you're using LOS 16 or 17. I think it's already included in Phh's AOSP builds.
There's also a trick to dual boot your OS. I keep one slot with stock installed, that's debloated and rooted with magisk. The other slot I use for flashing GSIs. Twrp can't restore encrypted data for stock, but you can format /data using "yes" then switch slots and use "reboot recovery" to boot up stock with magisk. To swap back to the GSI, fastboot boot twrp, format data, switch slots from the reboot menu, reboot to recovery. If twrp starts, you changed slots successfully. Then just restore data for lineage and bootup.
Oh by the way, "dirty flashing" is just flashing an OS update without wiping data first. I don't recommend it though. Sometimes bugs from older builds will get carried over. You don't need to do that to install LOS 17 or Android 10. It might've been true at one time, but it isn't now. You can just do your wipes and flash the latest build.

Thanks for your Help
How can I check if both partitions are with stock and bootloader?
Is there a trick to copy a working partition to the oter?
I would flash like it is written in this: [Guide][Channel][Stock]Moto g7 play Factory Firmware Images
(https://forum.xda-developers.com/g7-play/how-to/channel-moto-g7-factory-firmware-images-t3996303)
Would it flash both partitions (if only one is written)?
Thanks for your help

ggg777 said:
Thanks for your Help
How can I check if both partitions are with stock and bootloader?
Is there a trick to copy a working partition to the oter?
I would flash like it is written in this: [Guide][Channel][Stock]Moto g7 play Factory Firmware Images
(https://forum.xda-developers.com/g7-play/how-to/channel-moto-g7-factory-firmware-images-t3996303)
Would it flash both partitions (if only one is written)?
Thanks for your help
Click to expand...
Click to collapse
Typically if you've taken an OTA then you already have both slots filled. You can check with...
Code:
fastboot getvar all
Near the bottom you'll see some slot information. If slot b is active, then you should already be covered. I still think it's best to manually flash both slots though. If you've never updated then slot b is definitely empty. This is what I do...
Code:
fastboot flash boot_a boot.img
fastboot sending image boot_a...
Successful!
Image not signed blah blah something that isn't important...
Hit the up arrow on the keyboard then just change _a to _b
Code:
fastboot flash boot_b boot.img
Same with system, only I run through the list of sparse chunks in one shot, then hit the other slot. Use the big series of sparse chunks (0-7) on both slots. Skip the two that would normally go to system_b.
Code:
fastboot flash system_a system.image_sparsechunk.0
fastboot flash system_a system.image_sparsechunk.1
fastboot flash system_a system.image_sparsechunk.2
etc...
Then on the other side the same way.
Code:
fastboot flash system_b system.image_sparsechunk.0
fastboot flash system_b system.image_sparsechunk.1
fastboot flash system_b system.image_sparsechunk.2
etc...
When you get to oem, do not use oem_other.img, flash oem.img to both slots instead. Basically just make sure you do that with everything. E.g. dsp_b modem_b. I'm sure you get the idea by now.

Hello Spaceminer,
I have little knowledge in working with terminal in debian (I used man fastboot and tried some things like changing slots but this did not work). And then I tried some of these things and was to scared to brick it so I flashed it with RDS Lite (I hate to use Windows ) last night.
With RDS Lite flashing was no problem and I got a OTA, so slots a and b are not empty. After that I used your TWRP-Guide which you linked and it worked
BUT
Then I was trying to flash a GSI (arm32binder64ab):
lineage-17.1-20200309-UNOFFICIAL-treble_a64_bvN.img
Havoc-OS-v3.0-20191226-A64AB-Unofficial.img
system-quack-arm32_binder64-ab-vanilla.img
it completed but failed to boot:
Start Up Failed:
---
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
No bootalbe A/B slot
Failed to boot Linux, falling back to fastboot
Boot up failed
---
TWRP is always available with:
fastboot -> recovery
Could you please help me to handle this?
I would really love to use this phone de-googled with root permission cause I'm sad of spying on me by Gafa and the moto g7 play (I hate the size of the bigger ones) looks like the perfect model for me
PS: I have some screenshot's if you need

ggg777 said:
Hello Spaceminer,
I have little knowledge in working with terminal in debian (I used man fastboot and tried some things like changing slots but this did not work). And then I tried some of these things and was to scared to brick it so I flashed it with RDS Lite (I hate to use Windows ) last night.
With RDS Lite flashing was no problem and I got a OTA, so slots a and b are not empty. After that I used your TWRP-Guide which you linked and it worked
BUT
Then I was trying to flash a GSI (arm32binder64ab):
lineage-17.1-20200309-UNOFFICIAL-treble_a64_bvN.img
Havoc-OS-v3.0-20191226-A64AB-Unofficial.img
system-quack-arm32_binder64-ab-vanilla.img
it completed but failed to boot:
Start Up Failed:
---
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
No bootalbe A/B slot
Failed to boot Linux, falling back to fastboot
Boot up failed
---
TWRP is always available with:
fastboot -> recovery
Could you please help me to handle this?
I would really love to use this phone de-googled with root permission cause I'm sad of spying on me by Gafa and the moto g7 play (I hate the size of the bigger ones) looks like the perfect model for me
PS: I have some screenshot's if you need
Click to expand...
Click to collapse
Hey im in a smiliar situation with the G7 Play (XT1952-2)
I have the same goal of running this phone without google..
I would like to install LineageOS with microG (signature spoofing)
Have you been successful with this? Do you have a A-Z list of instructions for a fellow newbie?

Twrp 3.3.1-0 & root [updated] kane/troika

Our old twrp have been great compared to nothing but it isn't exactly fully working and freezes a lot on splash screen.
Thanks to @Stricted and @deadman96385 we now have a more functional twrp.
Support for A/B slots.
ADB working.
No need to flash full firmware. Just flash the vbmeta_patch.img and boot twrp.
!!BOOTLOADER MUST BE UNLOCKED!!
YOUR DATA WILL BE WIPED!!​
Code:
fastboot flash vbmeta vbmeta_patch.img
fastboot boot twrp-3.3.1-test3.img
Now that we booted to TWRP it's time to format data.
Go to wipe -> format data -> type yes.
"Permanent" install of TWRP (optional):
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot and go to advanced settings.
Use the option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings so that it won't reboot to recovery instead of system..
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
This must be done every time you update your boot.img.
-------------------------------------------------------------------------------------------------------------------------------------------------------
# ROOT:
-----------
# First time:
# Method 1: Root, forced encryption disabled. Full access to data from twrp:
Flash Magisk and Disable_Dm-Verity_ForceEncrypt.zip.
# Method 2: Root only. Device still encrypted and won't be able to decrypt / mount data in twrp.
Magisk modules through Magisk manager still works:
Flash only Magisk.
----------------------------------------------------------------------------------------------------
# Fastboot flash update without loosing root or data:
----------------------------------------------------------------------------------------
# Already rooted with encryption disabled:
Extract the firmware zip to your adb/fastboot folder.
You already have the patched vbmeta flashed so just remove the stock vbmeta.img from the folder after extraction to avoid flashing it by mistake.
Flash full firmware without wipe. (Use cmds from below. Save as .bat to make it more simple.)
Boot twrp and then install it, fix recovery bootloop.
Reboot recovery, flash Magisk and Disable_Dm-Verity_ForceEncrypt.zip.
Boot system.
Code:
echo off
echo - UPDATE AND PRESERV ROOT -
fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.img
fastboot flash ldfw_a ldfw.img
fastboot flash ldfw_b ldfw.img
fastboot flash keystorage_a keystorage.img
fastboot flash keystorage_b keystorage.img
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash modem_a modem.bin
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot flash vendor_a vendor.img
fastboot reboot bootloader
pause 10
fastboot boot twrp-3.3.1-test3.img
echo TWRP is booting..
echo - install recovery ramdisk, fix bootloop, flash magisk & dm-verity zip.
echo - alternatively flash only magisk and Disable_Dm-Verity_ForceEncrypt.zip if you want to keep stock recovery.
pause
# Already rooted with device still encrypted:
Flash firmware update, except vbmeta.
Boot twrp and flash Magisk with adb sideload.
(alternative method: boot twrp and flash magisk patched boot.img)
Download TWRP: https://images.stricted.net/test/troika/twrp-3.3.1-test3.img
Download Magisk: https://github.com/topjohnwu/Magisk/releases
Download vbmeta_patch.img & Disable_Dm-Verity_ForceEncrypt.zip attached below.
PLEASE, DON't QUOTE THE WHOLE OP.

Great guide @tys0n and thank you to @Stricted and @deadman96385 for his work !

tys0n said:
Code:
fastboot flash vbmeta vbmeta_patch.img
fastboot boot twrp-3.3.1-test3.img
Click to expand...
Click to collapse
My Vision is already unlocked and rooted by the old TWRP method. Should I just do this step so I can update to the new TWRP, and then I can follow "encryption disabled" steps to update to a new firmware?
I suppose I can't enable encryption anymore without resetting data.

daekdroom said:
My Vision is already unlocked and rooted by the old TWRP method. Should I just do this step so I can update to the new TWRP, and then I can follow "encryption disabled" steps to update to a new firmware?
I suppose I can't enable encryption anymore without resetting data.
Click to expand...
Click to collapse
You're right. You can't switch between encrypted / non encrypted without a reset.
This update method have been working for me with the old twrp as well, but this new build is much better and more stable that I see no reason not to switch to the new one.
Actually, I think it may be better to first fastboot flash the new firmware (except vbmeta) so that you have a "clean" boot.img to start with if you're planning to use the install recovery ramdisk. At least if you have the old one installed already.
That's how I switched and I've had no problems.

Worked to my, Thnx

Good afternoon,
I'm trying to "patch" the TWRP as you indicate at the beginning of the first post.
When you say:
"For permanent install, use the" flash recovery ramdisk "option in twrp advanced settings"
What file do I have to flash?
Regards

gonzo1963 said:
Good afternoon,
I'm trying to "patch" the TWRP as you indicate at the beginning of the first post.
When you say:
"For permanent install, use the" flash recovery ramdisk "option in twrp advanced settings"
What file do I have to flash?
Regards
Click to expand...
Click to collapse
Sorry, I could have been more clear about this step in the description.
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot, go to advanced settings.
There's an option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings.
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.

tys0n said:
Sorry, I could have been more clear about this step in the description.
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot, go to advanced settings.
There's an option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings.
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
Click to expand...
Click to collapse
Good evening,
One last question:
Currently I have permanently installed the TWRP.
Is it also necessary to do these last steps that you have added?
Regards
Enviado desde mi unknown mediante Tapatalk

gonzo1963 said:
Good evening,
One last question:
Currently I have permanently installed the TWRP.
Is it also necessary to do these last steps that you have added?
Regards
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
Good afternoon,
Any answer?
Regards
Enviado desde mi unknown mediante Tapatalk

Bootloop
Dude, my phone was encrypted and unrooted. I flashed vbmeta then booted into twrp. Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop, then I flashed Magisk then I flashed the Disable DM Verity. Now I'm stuck in a recovery loop. The phone turns on, then android one screen, then reboots then goes to twrp...
What did I do wrong / miss?

"Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop."
Agter this restart the phone in recovery mode and then continue as explained.
Sorry in bad english

First of all, @tys0n thank you very much for your work. I got this phone for work, but since an unrooted Android device is almost useless to me, this is very much appreciated. Just a few annotations from my side, maybe they help someone.
1. Permanent TWRP install didn't work for me. TWRP was installed sucessfully but just like the dude above me, it would not boot to system, even after appying the bootloop fix. I had to reflash to fix this, so better be careful here!
2. I didnt want to lose encryption, so i chose method 2 for rooting. This works fine, but still I had to wipe data in the first place. Otherwise it would again not boot to system, but at least this time it told me that wiping would possibly fix this. However, after wiping encryption IS active. Maybe I did something wrong here but I don't know... Chosing method 1 seems to be the more straightforward option here.
3. Despite these issues, flashing updates seems to work just fine as described described in the OP, preserving data and root. I have only tried this once, from QSA30.62-24-6 to QSA30.62-33, which is currently the most recent patchlevel for RETEU devices. I even got the "successfully updated" notification afterwards, as if it was an OTA update

Preceptor said:
Dude, my phone was encrypted and unrooted. I flashed vbmeta then booted into twrp. Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop, then I flashed Magisk then I flashed the Disable DM Verity. Now I'm stuck in a recovery loop. The phone turns on, then android one screen, then reboots then goes to twrp...
What did I do wrong / miss?
Click to expand...
Click to collapse
same here !

sennator said:
First of all, @tys0n thank you very much for your work. I got this phone for work, but since an unrooted Android device is almost useless to me, this is very much appreciated. Just a few annotations from my side, maybe they help someone.
1. Permanent TWRP install didn't work for me. TWRP was installed sucessfully but just like the dude above me, it would not boot to system, even after appying the bootloop fix. I had to reflash to fix this, so better be careful here!
2. I didnt want to lose encryption, so i chose method 2 for rooting. This works fine, but still I had to wipe data in the first place. Otherwise it would again not boot to system, but at least this time it told me that wiping would possibly fix this. However, after wiping encryption IS active. Maybe I did something wrong here but I don't know... Chosing method 1 seems to be the more straightforward option here.
3. Despite these issues, flashing updates seems to work just fine as described described in the OP, preserving data and root. I have only tried this once, from QSA30.62-24-6 to QSA30.62-33, which is currently the most recent patchlevel for RETEU devices. I even got the "successfully updated" notification afterwards, as if it was an OTA update
Click to expand...
Click to collapse
Hi. Yes, you're right. After flashing the patched vbmeta we need to format data. I've made it more clear in OP now.
Thanks for pointing it out.
kArLiN_dRaKE_MX said:
same here !
Click to expand...
Click to collapse
Format data in twrp

It doesn't work for me (XT1970-1).
I did the process according to information method 2.
the system boots normally.
however magisk is not 'GREEN' like two pieces of information.
How is it going without ROOT, how do I put ROOT?
have another process after this information?
Thank you.

It worked.
I performed the process again.
and everything went well.
Thanks to everyone involved. :good:
gambiarraweb1 said:
It doesn't work for me (XT1970-1).
I did the process according to information method 2.
the system boots normally.
however magisk is not 'GREEN' like two pieces of information.
How is it going without ROOT, how do I put ROOT?
have another process after this information?
Thank you.
Click to expand...
Click to collapse

Just a quick question, when I have TWRP and root I can't pass the SafetyNet check, right?

Hello all. When I click on Internal storage, there are folders with names like "a16sgyx462" and so on, so I am not able to install TWRP permanently. Can somebody help me with this?

simije97 said:
Hello all. When I click on Internal storage, there are folders with names like "a16sgyx462" and so on, so I am not able to install TWRP permanently. Can somebody help me with this?
Click to expand...
Click to collapse
You probably have Data encrypted. You need to execute Format Data in TWRP.

Has anyone used the official TWRP version? I've been thinking of transitioning from the older, unofficial, TWRP to that, but I haven't found any comment about it at all.

[GUIDE][UNBRICK] How unbrick your bootloop in MERLIN after flashing TWRP (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)

If you try to flash the file misc.bin your device can be in bootloop forever, please follow this guide to fix it.
It works with:
- Xiaomi Redmi Note 9
- Xiaomi Redmi 10X 4G
Method 1:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
If you can see your device in adb recovery mode, you have to erase misc partition:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p2
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will ERASE any other partition and it can brick your device forever and cause more damages.
Method 2:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
And then reboot to bootloader:
Code:
adb reboot bootloader
And then check if it is detected in fastboot mode:
Code:
fastboot devices
If you can see your device in fastboot mode, you have to erase misc partition:
Code:
fastboot erase misc
Keep attention, if you try to format misc partition, you will get this error: Formatting is not supported for file system with type 'raw data'.
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will ERASE any other partition and it can brick your device forever and cause more damages.
Good luck !
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/

VD171 said:
If you boot your device and it keeps in a black screen because outdated TWRP, please follow this guide.
It works with:
- Xiaomi Redmi 10X 4G
- Xiaomi Redmi Note 9
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected:
Code:
adb devices
If you can see your device in adb recovery mode, you have to format misc partition:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p2
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will FORMAT any other partition and it can brick your device forever and cause more damages.
Good luck !
Click to expand...
Click to collapse
OR they can just use
adb reboot bootloader
boot to fastboot and flash the stock image of the partition which is corrupted.

Communos said:
OR they can just use
adb reboot bootloader
boot to fastboot and flash the stock image of the partition which is corrupted.
Click to expand...
Click to collapse
Please, read the guide. This guide is for people who flashed misc.bin partition from the outdated TWRP.
This misc.bin partition from the outdated TWRP, will bootloop the device forever in recovery mode.
There is NO misc partition on stock image. So, you have to erase misc partition for stops with bootloop in recovery.

Thanks! If I knew this a few weeks ago it would have been helpful, But I fixed it with MiTool V2

VD171 said:
Please, read the guide. This guide is for people who flashed misc.bin partition from the outdated TWRP.
This misc.bin partition from the outdated TWRP, will bootloop the device forever in recovery mode.
There is NO misc partition on stock image. So, you have to erase or format misc partition for stops with bootloop in recovery.
Click to expand...
Click to collapse
Well, I've been in this situation twice or thrice, first I fixed by flashing full stock rom, rest of the times flashing stock recovery and stock boot fixed it for me.

Communos said:
Well, I've been in this situation twice or thrice, first I fixed by flashing full stock rom, rest of the times flashing stock recovery and stock boot fixed it for me.
Click to expand...
Click to collapse
As I've said, if you've flashed misc.bin from the outdated TWRP, just flashing stock recovery or stock boot will not fix the problem.
For fixing it, you have to erase misc partition. If it doesn't help you, please, go away and let it help who wants help.
Nice job and see you later.

VD171 said:
If you try to boot your device and it keeps in a black screen because outdated TWRP, please follow this guide.
It works with:
- Xiaomi Redmi Note 9
- Xiaomi Redmi 10X 4G
Method 1:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
If you can see your device in adb recovery mode, you have to format misc partition:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p2
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will FORMAT any other partition and it can brick your device forever and cause more damages.
Method 2:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
And then reboot to bootloader:
Code:
adb reboot bootloader
And then check if it is detected in fastboot mode:
Code:
fastboot devices
If you can see your device in fastboot mode, you have to format misc partition:
Code:
fastboot format misc
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will FORMAT any other partition and it can brick your device forever and cause more damages.
Good luck !
Click to expand...
Click to collapse
thanks sooo much

imranbinlatif said:
thanks sooo much
Click to expand...
Click to collapse
Good job, my friend.
You are welcome

VD171 said:
If you try to boot your device and it keeps in a black screen because outdated TWRP, please follow this guide.
It works with:
- Xiaomi Redmi Note 9
- Xiaomi Redmi 10X 4G
Method 1:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
If you can see your device in adb recovery mode, you have to erase misc partition:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p2
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will ERASE any other partition and it can brick your device forever and cause more damages.
Method 2:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
And then reboot to bootloader:
Code:
adb reboot bootloader
And then check if it is detected in fastboot mode:
Code:
fastboot devices
If you can see your device in fastboot mode, you have to erase misc partition:
Code:
fastboot erase misc
Keep attention, if you try to format misc partition, you will get this error: Formatting is not supported for file system with type 'raw data'.
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will ERASE any other partition and it can brick your device forever and cause more damages.
Good luck !
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/
Click to expand...
Click to collapse
Hey there, i erased the Misc partition, it's still bootlooping,
I tried to un-brick my device from the Xiaomi Mod Tool,
Yes i did try flashing a outdated TWRP image,
It got hard bricked, and i tried to fix it,
through some good luck, i managed to get into "fastboot"
And, nothing, it just got soft bricked,
I guess that's proggress?
My device: merlinnfc (Redmi Note 9/10X 4G)

TheMagnificent_Y said:
Hey there, i erased the Misc partition, it's still bootlooping,
I tried to un-brick my device from the Xiaomi Mod Tool,
Yes i did try flashing a outdated TWRP image,
It got hard bricked, and i tried to fix it,
through some good luck, i managed to get into "fastboot"
And, nothing, it just got soft bricked,
I guess that's proggress?
My device: merlinnfc (Redmi Note 9/10X 4G)
Click to expand...
Click to collapse
If you have access to fastboot and erasing misc did not work, simply flash the entire stock rom you were on through MiFlash.

TheMagnificent_Y said:
Hey there, i erased the Misc partition, it's still bootlooping,
I tried to un-brick my device from the Xiaomi Mod Tool,
Yes i did try flashing a outdated TWRP image,
It got hard bricked, and i tried to fix it,
through some good luck, i managed to get into "fastboot"
And, nothing, it just got soft bricked,
I guess that's proggress?
My device: merlinnfc (Redmi Note 9/10X 4G)
Click to expand...
Click to collapse
Erasing misc only works if you are frozen in a black screen after flashing misc partition.
Recovery partition can't break boot.
Probably your problem is vbmeta.
Vbmeta can break the boot.
Did you flash it too?

I flashed the entire ROM,
So yes,
Every single partition, except misc since it's gone now,
When i say "Every Single Partition", I mean every single one,
this includes,
Scp1/2
super
..etc.

TheMagnificent_Y said:
I flashed the entire ROM,
So yes,
Every single partition, except misc since it's gone now,
When i say "Every Single Partition", I mean every single one,
this includes,
Scp1/2
super
..etc.
Click to expand...
Click to collapse
Misc partition is not present in original stock rom.
It contains a variable data/parameter for boot.
Did you solve the bootloop after flash full rom?

No,
Here are the full details:
1. I tried flashing the recovery partition, Nothing.
2. I used an unnofficial TWRP ROM that hard bricked my device, this includes the following partitions:
Misc Opt Vbmeta Recovery
3. I managed to get into ADB recovery, i got into fastboot, then flashed the stock rom.
4. Boot loop

TheMagnificent_Y said:
No,
Here are the full details:
1. I tried flashing the recovery partition, Nothing.
2. I used an unnofficial TWRP ROM that hard bricked my device, this includes the following partitions:
Misc Opt Vbmeta Recovery
3. I managed to get into ADB recovery, i got into fastboot, then flashed the stock rom.
4. Boot loop
Click to expand...
Click to collapse
You need to avoid the misc partition.
If you've flashed it, you REALLY need to erase it.
Or, it will make your device to enter in recovery forever.
Vbmeta needs to be flashed with disababled verification.
Here you can find safe and secure vbmeta with disabled verification: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/
Or, it will detect modification on partitions and will reboot the device forever.
I think Opt doesn't change anything.
I'm not sure, but I think it only matter for devices without vbmeta partition. (I'M NOT SURE.)
Because it modifies the system, and obviously you will get in a bootloop.
If you want to modify the system, you need to debloat your system before.
Try to flash the whole system again.
Or just try to flash the whole rom again.

I've done that twice, and i deleted misc afterwards,
What about...:
fastboot flashall -w ?
Shouldn't that help flashing the system?
Also what does Vbmeta verify?
Thanks.

PS: I tried flashing the un-official and official versions, both leave a brick, and nothing really changes, i haven't tried your "Patched" version tho.

TheMagnificent_Y said:
I've done that twice, and i deleted misc afterwards,
What about...:
fastboot flashall -w ?
Shouldn't that help flashing the system?
Also what does Vbmeta verify?
Thanks.
Click to expand...
Click to collapse
I'm not sure.
Just flashing the system should solve it.
Or just flashing the whole rom using the flashing scripts inside the original stock rom.
Vbmeta checks if boot, recovery and dtbo partitions keeps untouched and unmodified.

I flashed the whole rom using the Xiaomi Mod Tool which is coded in java script,
i'll try to flash your "Patched" vbmeta image and see if that helps, if not, i'll re-flash the stock rom.

TheMagnificent_Y said:
I flashed the whole rom using the Xiaomi Mod Tool which is coded in java script,
i'll try to flash your "Patched" vbmeta image and see if that helps, if not, i'll re-flash the stock rom.
Click to expand...
Click to collapse
Flashing the whole stock rom, certainly solves everything.
And then, if you want TWRP again, try this first: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227751/
Good luck

I flashed twrp but now I'm stuck at an error "Unable to wipe Data. Unable to format to remove encryption".

i flashed twrp but now im stuck at a formatting error called "mke2fs -t ext4 -b 4096 /dev/block/sdc46 29325304 process ended with ERROR: 1 Unable to wipe Data. Unable to format to remove encryption."
I am installing PE11 Exp. ROM and right after successfully flashing my PE ROM I am stuck at this format stage. Will I be needing to flash MIUI stock rom and uninstall TWRP or what now? I'm confused. Pls help.

th1nd said:
i flashed twrp but now im stuck at a formatting error called "mke2fs -t ext4 -b 4096 /dev/block/sdc46 29325304 process ended with ERROR: 1 Unable to wipe Data. Unable to format to remove encryption."
I am installing PE11 Exp. ROM and right after successfully flashing my PE ROM I am stuck at this format stage. Will I be needing to flash MIUI stock rom and uninstall TWRP or what now? I'm confused. Pls help.
Click to expand...
Click to collapse
Just changed the formatter in format settings (rm -rf instead of formatting) and it did install PE rom but my internal storage is inaccessible now .

Same issue here, haven't changed the format settings yet. Did you fix the issue with the internal storage?

Same problem

Laminesls said:
Same problem
Click to expand...
Click to collapse
Just need for more steps. Wipe dalvik, data, cache, system, vendor > Reboot recovery. Format data> Reboot recovery. Then start do flash rom and do other steps again. This happen because of encryption. If wipe data error, go in fastboot and type "fastboot -w" in ADB PC

Kirasu2080 said:
Just need for more steps. Wipe dalvik, data, cache, system, vendor > Reboot recovery. Format data> Reboot recovery. Then start do flash rom and do other steps again. This happen because of encryption. If wipe data error, go in fastboot and type "fastboot -w" in ADB PC
Click to expand...
Click to collapse
I am stuck as well. I followed the flash guide of the LiteUp MIUI V12.5 rom for the redemi note 8 pro: https://telegra.ph/Steps-01-01 And I got the error message after formatting the data. I asked on the telegram channel and they told me to change the file system to ext4, but that didn't worked. I tried your solution of wipe, then reboot recovery, fromat data, reboot recovery... flashed the rom again and then I rebooted straight to TWRP again. Can you help me?

Anyone know how to fix this I've tried to format data typed yes and this is what I get back using OnePlus 6t android 11 twrp 3.7.0

jamiehawman said:
Anyone know how to fix this I've tried to format data typed yes and this is what I get back using OnePlus 6t android 11 twrp 3.7.0
Click to expand...
Click to collapse
If you have PC, boot in fastboot mode and type "fastboot -w"
If you dont have PC, you can do some tricks to format:
- For flash new rom, Wipe necessary things > Reboot Recovery > Format data > Reboot Recovery > Flash rom
- Or you can go Wipe > Advanced Wipe > Data and Change File System to Ext4 (Or any default file system that your phone using)

i rebooted the twrp asked for password it decrypted so now il drag and drop magisk to phone do i need to drag and drop the twrp and that rom too

ive sorted it now well a g
Kirasu2080 said:
If you have PC, boot in fastboot mode and type "fastboot -w"
If you dont have PC, you can do some tricks to format:
- For flash new rom, Wipe necessary things > Reboot Recovery > Format data > Reboot Recovery > Flash rom
- Or you can go Wipe > Advanced Wipe > Data and Change File System to Ext4 (Or any default file system that your phone using)
Click to expand...
Click to collapse
uy sorted it for me i had to install a new rom install the new twrp and wallah all good

Back up your data if you still can.
You can try two methods below. Be careful: both will wipe our your data.
Method 1: boot into fastboot
fastboot erase userdata
fastboot erase cache
fastboot erase recovery
fastboot erase system
Try flashing a recovery
fastboot flash recovery [name-of-your-recovery.img]
Method 2: boot into recovery, if you still can
In Twrp / Orangefox / other recovery, format data -> yes;
Plus, you can wipe data, cache and other partitions in recovery.

wenyendev said:
Back up your data if you still can.
You can try two methods below. Be careful: both will wipe our your data.
Method 1: boot into fastboot
fastboot erase userdata
fastboot erase cache
fastboot erase recovery
fastboot erase system
Try flashing a recovery
fastboot flash recovery [name-of-your-recovery.img]
Click to expand...
Click to collapse
Just logged in to say thanks. I flashed a PixelOS Rom without removing the password on the old ROM, and the storage is encrypted. Failed to format data, TWRP bootloop, tried different methods, did not work until I found this post.