Im running stock ROM 7.1.1 with Latest ElementalX Kernel and latest Magisk + MagiskSU. Also Running latest TWRP 3.1
I haven't updated yet. so I have the march patch, and this recent patch im behind on my 5x. I thought maybe i could just accept the OTA and just reflash magisk and the elementalX kernel afterwards. Oh, and likely would have to do TWRP as well. But accepting the update clicking to restart and install just rebooted me into TWRP. Flashfire doesn't work yet either been waiting a month on that. I get that failure during "uncrypting" error.
I'm slightly new back on the modding scene, until recently have been out of it for years. I did recently make a mistake with an audio mode and had to download the full image and use fastboot to throw that back on my device. Anyway with 7.1.2 out i really do want to update so i need to do it manually, and hopefully without losing my data. (or having to restore it from a backup if possible anyway)
I'd read somewhere that you can download the full images and extract the updated images you need and flash them to your device then your respective addons root kernel ect.. There seems to be lots of way to go about it, but little clear on how to do this so that's what brings me here to this post. What's the best way to manually update (add security patches) if im running Magisk and magiskSU.
Thanks in Advance.
https://elementalx.org/how-to-install-android-monthly-security-updates/
After you flash the /system /boot /vendor (I would also do bootloader and radio), reboot into TWRP and install kernel & Magisk.
Hello,
I have recently purchased my OP5T transitioning from 3 years of iOS and this is one of the best choice I've made when using phones.
I have managed to root my phone on OS 4.7.6 with SuperSU and install TWRP recovery. However, with the new Oreo update out, I want to upgrade my OS and still have root. Reading many tutorials on the OP forums and comments in the XDA forums, I was very confused mainly regarding the TWRP and it's compatibility on Oreo as well as when to flash it (before or after flashing oreo ota??)
I already have the Oreo 5.0.1 file installed on my PC.
Sorry for another pointless thread, but I'm at a loss here.
Thanks.
There are different flavors of TWRP for the 1+5t and some versions of them were unable to decrypt and mount /data partition so that's maybe the issues you read about.
However, I can personally confirm that I was able to install the beta versions of Oreo and the final version of Oreo without any issues.
Here's what I did:
1. Download full .zip
2. Download Blu_Spark TWRP
3. Download Magisk 15.3
4. Make sure you have both ROM and Magisk on a easy to find place on your phone.
5. Boot to fastboot and fastboot flash the recovery you just downloaded.
6. Boot to recovery, wipe dalvik and cache and then install the ROM.
7. Once the installation is done, boot to system and wait till the system to finish updating. Once there you can go to settings > phone status and it should read (android version = 8.0.0 and OxygenOS version = 5.0.2).
8. Reboot to fastboot, and fastboot flash the custom recovery again.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
Did I hear SuperSU is broken in the Official Oreo OTA? I haven't made the jump to Magisk and would rather stick with SuperSU for root.
crakerjac said:
Did I hear SuperSU is broken in the Official Oreo OTA? I haven't made the jump to Magisk and would rather stick with SuperSU for root.
Click to expand...
Click to collapse
Magsik is way better. 95% of people use it. It helps pass safety net which is requires for apps like pokemon go, bank apps, snapchat etc. So if u want to use those apps while rooted. Stick with magisk.
Yeah all the issues with twrp after at the beginning of this phones life. If u stick with oos and don't try custom roms u will have 0 issues.
I used SuperSu for 3-4 years and was too stubborn to try Magisk for quite a while....always saw guys talking about it this module and that module and didnt understand the hype. Then about 4 months ago I gave it a shot and in an instance totally understood the hype. I my opinion it is superior to SuperSu in everyway.
HueleSnaiL said:
There are different flavors of TWRP for the 1+5t and some versions of them were unable to decrypt and mount /data partition so that's maybe the issues you read about.
However, I can personally confirm that I was able to install the beta versions of Oreo and the final version of Oreo without any issues.
Here's what I did:
1. Download full .zip
2. Download Blu_Spark TWRP
3. Download Magisk 15.3
4. Make sure you have both ROM and Magisk on a easy to find place on your phone.
5. Boot to fastboot and fastboot flash the recovery you just downloaded.
6. Boot to recovery, wipe dalvik and cache and then install the ROM.
7. Once the installation is done, boot to system and wait till the system to finish updating. Once there you can go to settings > phone status and it should read (android version = 8.0.0 and OxygenOS version = 5.0.2).
8. Reboot to fastboot, and fastboot flash the custom recovery again.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
Click to expand...
Click to collapse
Following your steps above, will the latest official twrp work?
Dazed No More said:
I used SuperSu for 3-4 years and was too stubborn to try Magisk for quite a while....always saw guys talking about it this module and that module and didnt understand the hype. Then about 4 months ago I gave it a shot and in an instance totally understood the hype. I my opinion it is superior to SuperSu in everyway.
Click to expand...
Click to collapse
lmao same with me, i was so stubborn to try Magisk and always used SU, then i figured it out and I love magisk and would not go back to SU at this time.
I guess I just don't understand Magisk then... I just want to flash a zip and have access to root and Xposed.
I think most confusion from magisk come from modules
I thought magisk was a framework like closed by the way people were talking about it
Finally made the jump
Magisk is root on its own like supersu
But you have the added choice to install systemless modules
And you can add xposed the same way as supersu, its the same procedure
I've got my Max 3 unlocked today, decided to install Magisk but was prompted for password to decrypt, I've tried various passwords that I have but it doesn't work. So I wiped my data and and factory reset the phone from TWRP, thinking I could just download and flash the official ROM from the website.
After downloading the Official Global Stable ROM from Xiaomi, I've tried flashing it with various methods: by transferring the file through MTP within TWRP, through SD card and also sideload it with adb. But my phone remains stuck at the Xiaomi loading screen animation.
I have a Global version of the Max 3 and has the latest update (Pie) prior to unlocking. Did some reading, so I'm not sure if ARB is the cause or there's some steps that I've missed since I'm pretty new at this (usually unlock to install Magisk for Adaway and that's about it.)
Is there anyway that I can fix this or my Max 3 is doomed?
what version of recovery do you use?
Bartos81 said:
what version of recovery do you use?
Click to expand...
Click to collapse
TWRP 3.2.3-4 for nitrogen by nijel8
iDeft said:
I've got my Max 3 unlocked today, decided to install Magisk but was prompted for password to decrypt, I've tried various passwords that I have but it doesn't work. So I wiped my data and and factory reset the phone from TWRP, thinking I could just download and flash the official ROM from the website.
After downloading the Official Global Stable ROM from Xiaomi, I've tried flashing it with various methods: by transferring the file through MTP within TWRP, through SD card and also sideload it with adb. But my phone remains stuck at the Xiaomi loading screen animation.
I have a Global version of the Max 3 and has the latest update (Pie) prior to unlocking. Did some reading, so I'm not sure if ARB is the cause or there's some steps that I've missed since I'm pretty new at this (usually unlock to install Magisk for Adaway and that's about it.)
Is there anyway that I can fix this or my Max 3 is doomed?
Click to expand...
Click to collapse
Reinstalls the same version of rom via fastboot by Mi flash. Here is the link to rom via fastboot (https://forum.xda-developers.com/mi-max-3/how-to/rom-official-recovery-fastboot-roms-mi-t3827503). Mi flash you can search google or look here (https://forum.xda-developers.com/mi-max-3/how-to/b-guide-to-fake-rom-unlocked-bootloader-t3846891) . In the latter there are instructions on how to do the whole process. But remember that you have to use the same version of the rom that came in the device not to give brick by ARB. Never skip a step and carefully read the entire process before doing it (I made a mistake myself for lack of attention or skip steps when doing these procedures).
Hello,
i have version 11.0.2.0 Global on the device with twrp, magisk and edXposed.
Now I have seen that there is already a global version 11.0.6.0.
In my case, how can I update to a new version without losing the data and settings?
And one more question in general. Version 11.0.6.0 is not shown to me via OTA. Here it says, latest stable version 11.0.2.0. Is it not rolled out via OTA?
And if there was a newer version available via OTA, could I install the update despite TWRP?
hmarder said:
Hello,
i have version 11.0.2.0 Global on the device with twrp, magisk and edXposed.
Now I have seen that there is already a global version 11.0.6.0.
In my case, how can I update to a new version without losing the data and settings?
And one more question in general. Version 11.0.6.0 is not shown to me via OTA. Here it says, latest stable version 11.0.2.0. Is it not rolled out via OTA?
And if there was a newer version available via OTA, could I install the update despite TWRP?
Click to expand...
Click to collapse
I (without root) flashed the OTA on 11.0.2.0 global PGGMIXM to 11.0.6.0, but, to flash with root... Maybe (I dont know if it will brick) but you can try flash a recovery version of 11.0.6.0
hmarder said:
Hello,
i have version 11.0.2.0 Global on the device with twrp, magisk and edXposed.
Now I have seen that there is already a global version 11.0.6.0.
In my case, how can I update to a new version without losing the data and settings?
And one more question in general. Version 11.0.6.0 is not shown to me via OTA. Here it says, latest stable version 11.0.2.0. Is it not rolled out via OTA?
And if there was a newer version available via OTA, could I install the update despite TWRP?
Click to expand...
Click to collapse
I had exactly the same setup as you - here's what I did: 1 - Downloaded full rom from official Mi website (MIUI Global 11.0.6.0(PGGMIXM) 2 - Moved rom to root storage 3 - Flashed rom with TWRP, and voila! Updated to latest stable rom. Just remember to flash TWRP recovery again through Fastboot, because you will have stock recovery after update. I am using LTWRP- 3.3.1 -0924 and rooted and installed Magisk, without issues
hmarder said:
Hello,
i have version 11.0.2.0 Global on the device with twrp, magisk and edXposed.
Now I have seen that there is already a global version 11.0.6.0.
In my case, how can I update to a new version without losing the data and settings?
And one more question in general. Version 11.0.6.0 is not shown to me via OTA. Here it says, latest stable version 11.0.2.0. Is it not rolled out via OTA?
And if there was a newer version available via OTA, could I install the update despite TWRP?
Click to expand...
Click to collapse
One thing you forgot to mention is what region is your phone (not your Rom). If Chinese you may have to be extra cautious and steps above might not work for you.
Good luck!
KonahZave said:
I (without root) flashed the OTA on 11.0.2.0 global PGGMIXM to 11.0.6.0, but, to flash with root... Maybe (I dont know if it will brick) but you can try flash a recovery version of 11.0.6.0
Click to expand...
Click to collapse
Interesting. I'm still on rooted miui 10 4.5.0 PGGEUXM rooted magisk and twrp recovery-红米Note8Pro-3.3.1-9.0.img
I didn't update yet as bricking started to happen and I can't miss my phone as a daily driver.
Normally I would flash the full ROM, flash magisk, wipe cache and reboot.
So flashing full ROM doesn't break root?
Can't we flash recovery by twrp after flashing ROM instead by flashing by fastboot?
Isnt secure flash twrp after the ROM.
donkyshot said:
So flashing full ROM doesn't break root?
Can't we flash recovery by twrp after flashing ROM instead by flashing by fastboot?
Click to expand...
Click to collapse
Flashing a full rom will break root, and install stock recovery...
It is too risky to flash another recovery with twrp (possible brick)
so where to put official update on sd card?
download recovery rom?
unoturbo1 said:
I had exactly the same setup as you - here's what I did: 1 - Downloaded full rom from official Mi website (MIUI Global 11.0.6.0(PGGMIXM) 2 - Moved rom to root storage 3 - Flashed rom with TWRP, and voila! Updated to latest stable rom. Just remember to flash TWRP recovery again through Fastboot, because you will have stock recovery after update. I am using LTWRP- 3.3.1 -0924 and rooted and installed Magisk, without issues
Click to expand...
Click to collapse
I just brought rmn8p with miui 11.0.6.0 ,so it is ok to use LRTWRP-3.3.1 -0924. I came across a new version -1104, I'll try it after unlock the bootloader. After that flash preloader then trwp.
Use LR.TWRP, it got an option to make the TWRP persist on every OTA.
Also LR.TWRP = less headache on Xiaomi devices.
Here's the latest build: https://mega.nz/folder/cMAT3Q4b#7CbPV7sbEuSEdP7cehXJ-w
tze_vitamin said:
so where to put official update on sd card?
download recovery rom?
Click to expand...
Click to collapse
??
Put on external sd card dude
unoturbo1 said:
I had exactly the same setup as you - here's what I did: 1 - Downloaded full rom from official Mi website (MIUI Global 11.0.6.0(PGGMIXM) 2 - Moved rom to root storage 3 - Flashed rom with TWRP, and voila! Updated to latest stable rom. Just remember to flash TWRP recovery again through Fastboot, because you will have stock recovery after update. I am using LTWRP- 3.3.1 -0924 and rooted and installed Magisk, without issues
Click to expand...
Click to collapse
For chinese, this will brick the phone. See this instead.
Guys I Just see This video and in it shows the update process, with ltwrp, when the recovery capture the process and update even without losing data, its This True?, somebody has tried?
Link.
This will brick every phone. I brick my EU ROM, with this method of update rooted phone.
What is correct solution to update rooted phone?
Redmi Note 8 Pro, 11.0.2 QGGEUXM, TWRP 3.3.1 1210, Magisk 20.3 -> 12.0.1 QGGEUXM
System say there exists update, i choose download, select reboot, but after reboot i end up in TWRP but nothing happened. After exit i boot to old 11.0.2 system with message that update fail.
Edit 1: after 2. download/update/reboot TWRP start installing image ...
Edit 2: after automatic update system say 12.0.1, just loosing root (all apps stay)
Edit 3: installed TWRP again, Magisk (there was little problem because Magisk Manager say "not installed", but after some googlig i fix that. So i update system without reinstalling apps or loosing data.
Clear solution is probably download full rom from official Mi website and flash selected rom with TWRP (flash TWRP recovery again, repeat root process, to get root back). See next post.
RedMu said:
So what is correct solution to update rooted phone?
Redmi Note 8 Pro, 11.0.2 QGGEUXM, TWRP 1210, Magicks 20.3 -> 12.0.1 QGGEUXM
Now system say there exists update, i choose download, select reboot, but after reboot i end up in TWRP. After exit i boot to old 11.0.2 system with message that update fail.
So solution is probably downloaded full rom from official Mi website and flash selected rom with TWRP (flash TWRP recovery again, repeat root process, to get root back).
So what is correct way for update in this case?
Click to expand...
Click to collapse
This is how I upgraded, try at your own risk.
Download full recovery zip of MIUI 12 and latest magisk
Create twrp Backup just in case
In LR TWRP 10 mount & format system, cache, dalvik, vendor.
Flash full rom (not ota!)
Press home to return to the main screen Choose Advanced-File Manager item >system_root / system / folder at the bottom if there is a recovery_fromboot.p file delete it.
Go back to Advanced and select Close AVB2.0 and confirm with a swipe to the right.
flash Magisk
boot to system
First boot takes a while, relax and grab a drink
Remember to backup and close AVB!
Thank you so much for sharing these steps. I have questions for a couple of steps below:
donkyshot said:
This is how I upgraded, try at your own risk.
Download full recovery zip of MIUI 12 and latest magisk
Create twrp Backup just in case
In LR TWRP 10 mount & format system, cache, dalvik, vendor.
Click to expand...
Click to collapse
What is TWRP 10? Do I format first and then mount? I usually wipe system, cache, dalvik and then "install" the full rom (your next step), but i never try "mount" here. What does mount do here? what is wiping vender and mounting vender?
donkyshot said:
[*]Flash full rom (not ota!)
[*]Press home to return to the main screen Choose Advanced-File Manager item >system_root / system / folder at the bottom if there is a recovery_fromboot.p file delete it.
[*]Go back to Advanced and select Close AVB2.0 and confirm with a swipe to the right.
Click to expand...
Click to collapse
There are two check box here. one is "close the boot verification of avb2.0" the other is "close the DMVerity of avb2.0". Do O check one of both?
Thank you!
po1 said:
Thank you so much for sharing these steps. I have questions for a couple of steps below:
What is TWRP 10? Do I format first and then mount? I usually wipe system, cache, dalvik and then "install" the full rom (your next step), but i never try "mount" here. What does mount do here? what is wiping vender and mounting vender?
There are two check box here. one is "close the boot verification of avb2.0" the other is "close the DMVerity of avb2.0". Do O check one of both?
Thank you!
Click to expand...
Click to collapse
Recovery LR TWRP for Android 10
https://androidfilehost.com/?fid=8889791610682889486
First mount system, cache, dalvik, vendor
Than format system, cache, dalvik, vendor
Without mounting folders they won't be mounted
►go back to your main screen: ADVANCED- close AVB 2.0 then swipe to confirm, just tick only 1st box, ignore the second box
I'm trying update from 12.0.1 to 12.0.5 with TWRP recovery.
"Package expects build fingerprintof redmi/begonian this device has begonia" This error is coming.
I Removed the fist line which checks this from updater script. still this error is coming.
The Questions I have .
1) Is is possible to do OTA update without loosing apps/data?
2) Can i Use the image from this link Here ?
3) If i can't do the above should i flash the full rom from Here ?? Is it possible to do this without loosing apps/data?
4) Is there any other recovery that supports flashing the OTA rom?
1) OTA won't erase your data
2) You should install the correct OTA distribution for your phone. If you have begonia then flash begonia. So does for begoniain. Unless you are flashing fastboot ROM, it will count as switching region and are totally fine with UBL. How do I know which device am I? Refer to about section in settings
3) Dirty flash for MIUI in mi flash with same region distribution is fine. Even downgrade from A10 to A9 is completely fine (but some apps may show weird behaviour, for this case, factory reset is recommended). I've done it many times (stable global to stable global).
4) It sure can but I wouldn't recommend. It will lead to bootloop. I will recommend to flash stock recovery and do the update via miflash pro with full recovery rom. I also recommend to completely remove magisk prior update. Carrying over your magisk+magisk hide+magisk settings+it's module is fine, but I recently discovered incompatibilities that leads bootloop when switching off magisk hide that carried over from previous update on 12.0.7.0 global. You can re-install everything after update