guys i am getting (patching system unconditionally--stuck for more than 20mins) while flashing official cm13 nightly.i tried 2 nighlty builds but same result. but flashing other roms are working fine..i installed lastest twrp and gapps..any solution??
On global stable 7.2.3
What i have done till now-
Unlocked bootloader unofficially on 7.1.8, twrp flashed, edited ota 7.2.3 and flashed, rooted.
Everthing good for days till now.
To flash 7.2.5 what i did-
Restored unrooted 7.2.3 (twrp backup) with un patched boot.img.
Edited updater script of ota 7.2.5, replaced emmc
Flashed ota.
The problem-
Twrp skips the patching system image part (didn't touched this part while editing updater script) and patches boot.img fine.
Then bootloop. Tired safe twrp too.
What else i have done?
Flashed 7.1.8 again by mi tools and flashed edited 7.2.3 ota and then 7.2.5 ota. Twrp skips 7.2.5 system patching part.
Now after flashing 7.1.8 again by mi flash tool, twrp is skipping both otas 723 and 725 system patching part.
I am not getting it why.
Anyone face same issue? Or can anyone with unoffical unlock share there updater script for ota 7.2.5?
assuming you have 7.2.3 MIUI global stable installed, follow this steps:-
1) try this updater-script View attachment updater-script.zip in the OTA
2) boot to TWRP, and flash original boot.img of 7.2.3
3) flash the OTA of 7.2.5
4) flash universal boot.img patcher
tell me if it works
Sudeep Duhoon said:
On global stable 7.2.3
What i have done till now-
Unlocked bootloader unofficially on 7.1.8, twrp flashed, edited ota 7.2.3 and flashed, rooted.
Everthing good for days till now.
To flash 7.2.5 what i did-
Restored unrooted 7.2.3 (twrp backup) with un patched boot.img.
Edited updater script of ota 7.2.5, replaced emmc
Flashed ota.
The problem-
Twrp skips the patching system image part (didn't touched this part while editing updater script) and patches boot.img fine.
Then bootloop. Tired safe twrp too.
What else i have done?
Flashed 7.1.8 again by mi tools and flashed edited 7.2.3 ota and then 7.2.5 ota. Twrp skips 7.2.5 system patching part.
Now after flashing 7.1.8 again by mi flash tool, twrp is skipping both otas 723 and 725 system patching part.
I am not getting it why.
Anyone face same issue? Or can anyone with unoffical unlock share there updater script for ota 7.2.5?
Click to expand...
Click to collapse
Here's what I had done :
1. Replaced boot.img in OTA zip with patched boot.img
2. Edited updater script to remove device verification (for status 7 errors)
and to remove package_extract_file lines for emmc_appsboot.mbn (there are 2 lines).
3. Removed emmc_appsboot.mbn from firmware_update folder.
4. Flashed the zip in TWRP 3.0.2-2.
5. Waited for boot and success!
I have attached my patched boot.img and updater-script. Replace the ones in the 7.2.5 OTA zip.
The issue was twrp mounting system as read/write. The Ota then skips system patching or bootloops after patching.
Fix: mount system as read only in twrp. Flash the Ota. Make a system+boot backup. Mount twrp read/write. Flash su and patched boot.img.
Apply next ota:restore stock system+boot backup. Mount system ready only. Flash Ota. Make new system+Ota backup. Mount system read/write. Flash su and patched boot.img. If success, delete old backup.
Ps. admin/moderator please close the thread.
Thank you.
Sent from my MI PAD using XDA-Developers mobile app
Using h830 device running stock as primary and encountering an error when flashing patched zip for tmobile. It says that my device is h1 and that it can not complete the flashing. It fails in twrp altogether. I tried patching with the h850 variant selected and it fails in tarp but passes in the app. After reboot from application flashing I get stuck in a twrp loop and have to flash the stock image over again to restore my device. Any thoughts?
Hello, Please can someone assist me with rooting of my android phone as the phone is not rooted due to below error during installation of SuperSU 2.82 SR5. I just flashed a new stock firmware (MT6735) on this device.
boot image patcher
finding boot image
boot image /dev/block/mmcblk0p7
extracting ramdisk
failure, aborting
Hi I recently updated my Mi A3 to May Android 10 update i.e. v11.0.15 . Before this it was rooted with TWRP and Magisk as now both of these softwares are gone due to update. Now i want to flash TWRP first but unable to install it as I changed the active slot to A (current B) as per old method but nothing happened and phone stucked at Fastboot screen. This thing really concerns me as if I flash twrp.img at slot B, does it boot properly? Other way around to root Mi A3 using Magisk manager by patching boot.img of V11.0.15. Where can i get this and is it a reliable method without flashing custom recovery like TWRP? Can i flash any other good custom recovery?
vjrx88 said:
Hi I recently updated my Mi A3 to May Android 10 update i.e. v11.0.15 . Before this it was rooted with TWRP and Magisk as now both of these softwares are gone due to update. Now i want to flash TWRP first but unable to install it as I changed the active slot to A (current B) as per old method but nothing happened and phone stucked at Fastboot screen. This thing really concerns me as if I flash twrp.img at slot B, does it boot properly? Other way around to root Mi A3 using Magisk manager by patching boot.img of V11.0.15. Where can i get this and is it a reliable method without flashing custom recovery like TWRP? Can i flash any other good custom recovery?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
vjrx88 said:
Hi I recently updated my Mi A3 to May Android 10 update i.e. v11.0.15 . Before this it was rooted with TWRP and Magisk as now both of these softwares are gone due to update. Now i want to flash TWRP first but unable to install it as I changed the active slot to A (current B) as per old method but nothing happened and phone stucked at Fastboot screen. This thing really concerns me as if I flash twrp.img at slot B, does it boot properly? Other way around to root Mi A3 using Magisk manager by patching boot.img of V11.0.15. Where can i get this and is it a reliable method without flashing custom recovery like TWRP? Can i flash any other good custom recovery?
Click to expand...
Click to collapse
Use Sharp by the old process! Dont have to use twrp made for Android 9
Is a problem with a new security patch, i have one only and functional..
vjrx88 said:
Hi I recently updated my Mi A3 to May Android 10 update i.e. v11.0.15 . Before this it was rooted with TWRP and Magisk as now both of these softwares are gone due to update. Now i want to flash TWRP first but unable to install it as I changed the active slot to A (current B) as per old method but nothing happened and phone stucked at Fastboot screen. This thing really concerns me as if I flash twrp.img at slot B, does it boot properly? Other way around to root Mi A3 using Magisk manager by patching boot.img of V11.0.15. Where can i get this and is it a reliable method without flashing custom recovery like TWRP? Can i flash any other good custom recovery?
Click to expand...
Click to collapse
Return at the v10.xxx rom stock, and can i flash twrp or orange fox recovery, but not all the version can i flash new's rom android 10 i have the same problem about 1 month & this is my solution :crying:
vjrx88 said:
Hi I recently updated my Mi A3 to May Android 10 update i.e. v11.0.15 . Before this it was rooted with TWRP and Magisk as now both of these softwares are gone due to update. Now i want to flash TWRP first but unable to install it as I changed the active slot to A (current B) as per old method but nothing happened and phone stucked at Fastboot screen. This thing really concerns me as if I flash twrp.img at slot B, does it boot properly? Other way around to root Mi A3 using Magisk manager by patching boot.img of V11.0.15. Where can i get this and is it a reliable method without flashing custom recovery like TWRP? Can i flash any other good custom recovery?
Click to expand...
Click to collapse
Starting July im also facing the same issue. I restarted my phone but received a message that phone has been updated. Now TRWP and root is gone. I can't flast TWRP again on slot boot_a, also cannot flast twrp on boot_b. Stuck on Flashboot.
I was lucky to have the Stock boot img, i then flashed the Stock boot img on both slots a & b. But cannot flast TWRP anymore using ABD/fastboot
Solution: I flashed the new TWRP 3.4 for Android 10 from this link and now the problem is fixed!! https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
SidRose01 said:
Starting July im also facing the same issue. I restarted my phone but received a message that phone has been updated. Now TRWP and root is gone. I can't flast TWRP again on slot boot_a, also cannot flast twrp on boot_b. Stuck on Flashboot.
I was lucky to have the Stock boot img, i then flashed the Stock boot img on both slots a & b. But cannot flast TWRP anymore using ABD/fastboot
Solution: I flashed the new TWRP 3.4 for Android 10 from this link and now the problem is fixed!! https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
Click to expand...
Click to collapse
in that post they said
"Note: enable "use rm -rf instead of formatting" in TWRP settings, before you wipe data, else userdata partition will be damaged"
what does it mean???
ovi2901 said:
in that post they said
"Note: enable "use rm -rf instead of formatting" in TWRP settings, before you wipe data, else userdata partition will be damaged"
what does it mean???
Click to expand...
Click to collapse
I only used the files from that link. I did not read it anything. But Thanks, you pointed this out.
This means that the next time I wipe data in TWRP, then I should first enable "use rm -rf instead of formatting" in TWRP settings
I have never tried 'wipe data' on this phone. But I'll remember this the next time I 'wipe data'. Thanks, you just saved me.