Related
EDIT 8/2/19: I do not own this device anymore. So i cannot and dont know if anything changed about the procedures unlocking rooting etc. BUT if you are getting any trouble i might can help you. Comment your thoughts below
Hey guy, i saw a lot of guys here wondering how to root and flash twrp recovery on thier devices . Today i am gonna show you how to do that.
First of all make sure 3 things :
1. backup your images, contacts, music tracks etc on a external SD CARD, or on your computer.
2. You MUST have the BOOTLOADER unlocked. To do that, read this guide http://en.miui.com/thread-202290-1-1.html
3.Charge your device to 80%+
HOW TO FLASH TWRP AND ROOT MI MAX
1. Go to Settings-About phone-Find the MIUI VERSION, and tap on it for 5-10 times.
2. Go back to settings, sellect adittional settings. click on Developer options, and select enable
3. Find the option USB Debugging and enable it.
4. Download the TWRP recovery from the link
5. rename the file to 'recovery.img'
6. Move the image to the same file where the ADB was installed ( it should be on Computer-> C: -> Adb )
7. Open the adb folder
8. Press and hold the shift key and right click in the folder
9. click on the option "Open command window here"
10. Boot your device on fastboot mode by turning it off, pressing Power and the Volume Down buttons together, and then connect it with your computer
11. First type this command "fastboot devices" to check if your device is into fastboot mode
12. Enter the command "fastboot flash recovery recovery.img"
13. Enter the command "fastboot boot recovery.img"
14. Your phone is now in TWRP recovery mode ( if it is not, the write on ADB: reboot recovery )
15. select Install Zip and click on 'SuperSu.zip'
16. corfirm the flash
17. reboot your device
18. DONT PANIC IF YOU DEVICE WONT TURN ON. Sometimes need to wait 10-20 secs.
DOWNLOADS
1. ADB- (https://forum.xda-developers.com/showthread.php?t=2588979)
2. XIAOMI MI MAX HYDROGEN DRIVERS (http://xiaomiadvices.com/download-xiaomi-usb-drivers/)
3. TWRP RECOVERY IMAGE https://dl.twrp.me/hydrogen/ LATEST VERSION IS twrp-3.2.3-0
4. BetaSuperSu 2.74 http://www13.zippyshare.com/v/OFQGvIyA/file.html
RESERVED
The thread must be removed to XIAOMI MI MAX GUIDES, NEWS, & DISCUSSION
Hallo Friend!
I am about to test your guide. I think it is most decent among other guides on the net...
Could you please just tell me if it's gonna work on:
Android 6.0.1 MMB29M
MIUI 8.2.1.0 (MBCMIDL) Stable
kernel 3.10.84-perf-gfe86e7b
bootloader UNLOCKED
Is superSU by default included in the TWRP you gave? No need to download it additionally from somewhere?
What about warning about "dm-verity" on official TWRP website?
This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
Click to expand...
Click to collapse
Should this be any concern that the phone will not boot up again? Should this be disabled first?
Is it better to use the TWRP version you provided (3.0.3.0? not listed on official TWRP website? why?) or the lastest 3.1.0.0?
noob456 said:
Hallo Friend!
I am about to test your guide. I think it is most decent among other guides on the net...
Could you please just tell me if it's gonna work on:
Android 6.0.1 MMB29M
MIUI 8.2.1.0 (MBCMIDL) Stable
kernel 3.10.84-perf-gfe86e7b
bootloader UNLOCKED
Is superSU by default included in the TWRP you gave? No need to download it additionally from somewhere?
What about warning about "dm-verity" on official TWRP website?
Should this be any concern that the phone will not boot up again? Should this be disabled first?
Is it better to use the TWRP version you provided (3.0.3.0? not listed on official TWRP website? why?) or the lastest 3.1.0.0?
Click to expand...
Click to collapse
hello, please write again your problem. I can understand what do you mean.
StonebridgeGr said:
hello, please write again your problem. I can understand what do you mean.
Click to expand...
Click to collapse
Ok just two questions then, because I'm not sure what you can't understand. Please explain.
1) What Android, MIUI and kernel did you root?
2) Do you have SuperSu.zip in TWRP 3.0.3 by default? You didn't say anything in your guide about downloading it and from where + what version.
noob456 said:
Hallo Friend!
I am about to test your guide. I think it is most decent among other guides on the net...
Could you please just tell me if it's gonna work on:
Android 6.0.1 MMB29M
MIUI 8.2.1.0 (MBCMIDL) Stable
kernel 3.10.84-perf-gfe86e7b
bootloader UNLOCKED
Is superSU by default included in the TWRP you gave? No need to download it additionally from somewhere?
What about warning about "dm-verity" on official TWRP website?
Should this be any concern that the phone will not boot up again? Should this be disabled first?
Is it better to use the TWRP version you provided (3.0.3.0? not listed on official TWRP website? why?) or the lastest 3.1.0.0?
Click to expand...
Click to collapse
This twrp. Img it's for all the versions but only for mi max. Not the prime . This twrp doesn't contain superSU. If I remember correctly. But if on the TWRP contain the super su. Don't say yes. Just flash it like I saying on the guide. Maybe they upload a newest version. You can use the new. I think I put the official website . I will check it.
Ok thanks for the answer. Please check from where I download SuperSu - which version would be best.
Please tell me your Android, kernel and MIUI version that you rooted.
noob456 said:
Ok thanks for the answer. Please check from where I download SuperSu - which version would be best.
Please tell me your Android, kernel and MIUI version that you rooted.
Click to expand...
Click to collapse
LOL I forgot to add the superSU link...
That's what I told you. Then please do.
noob456 said:
That's what I told you. Then please do.
Click to expand...
Click to collapse
ok on the first post you can find all the links. if i miss something please tell me here !
Is this beta version of SuperSU reliable? Did you use it? Not better to use a stable version?
noob456 said:
Is this beta version of SuperSU reliable? Did you use it? Not better to use a stable version?
Click to expand...
Click to collapse
It's compatible with mi max. You will not have any problem. Don't worry
noob456 said:
Is this beta version of SuperSU reliable? Did you use it? Not better to use a stable version?
Click to expand...
Click to collapse
Waiting to tell me if everything went fine with the installation and the flashing
Hey, tried following Your guide to install a new rom last night. Great guide for noobs like me, but it may be worth renaming the thread to something like "How to flash whatever makes You happy on to Your Mi Max". These instructions seem to work fine regardless of what's being flashed. Great job, mate!
So I finally tried it and it was successful for me as well! But I used the latest version of TWRP (3.1.0) and SuperSu (2.79-20161205). Please add a point in your tutorial to upload SuperSU.zip to the phone first, because out of emotion, I forgot... So I flashed TWRP, booted it and then... ups... no SuperSu So I wanted to reboot the phone to upload SuperSU but since only SuperSU patches dm-verity (the thing I was afraid of the most - I told you before), my phone got into boot-loop and didn't want to start. So I just uploaded SuperSU to a memory card, entered Fastboot Mode again with key-combination, plugged the cable, typed "fastboot reboot-bootloader" command and was again in TWRP to flash SuperSu from my memory card.... ufff.
So I would reedit it a bit:
0. Copy SuperSU.zip to the phone/memory card!
1. Go to Settings-About phone-Find the MIUI VERSION, and tap on it for 5-10 times.
2. Go back to settings, sellect adittional settings. click on Developer options, and select enable
3. Find the option USB Debugging and enable it.
4. Download the TWRP recovery from the link
5. rename the file to 'recovery.img'
6. Move the image to the same file where the ADB was installed ( it should be on Computer-> C: -> Adb )
7. Open the adb folder
8. Press and hold the shift key and right click in the folder
9. click on the option "Open command window here"
10. Boot your device on fastboot mode by turning it off, pressing Power and the Volume Down buttons together, and then connect it with your computer
11. First type this command "fastboot devices" to check if your device is into fastboot mode
12. Enter the command "fastboot flash recovery recovery.img"
13. Enter the command "fastboot boot recovery.img" - the phone will get disconnected from your PC automatically
14. Your phone is now in TWRP recovery mode (it takes about 30-60 seconds before FastBoot screen switches into TWRP - wait patiently)
15. select Install Zip and click on 'SuperSu.zip'
16. corfirm the flash
17. reboot your device
18. DONT PANIC IF YOU DEVICE WONT TURN ON. Sometimes need to wait 10-20 secs.
Hey, I just got connected with WiFi and new MIUI 8.2.3.0 MBCMIDL wants to be installed, although the phone is rooted with bootloader unlocked. Is it safe to apply the update? Is it goona remove root so that I have to go over the process again?
So I tried the update. First time it said it failed, second time it downloaded the whole ROM after which it rebooted device and TWRP started doing "something" - I don't know what. After that the phone didn't want to boot, and what's even better didn't want to run recovery (TWRP), instead it went into fastboot. What I had to do was to use MiPhoneDrivers from this topic: https://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594 (including MiFlash 2015, because 2016 version didn't want to work properly on my PC) and follow the instruction from official MIUI website to flash from scratch the new ROM MIUI 8.2.3.0 which I did. After that my phone was alive again. I installed TWRP and rooted the phone again. Now I've got MIUI 8.2.30 rooted. :] End of the story so far. My settings left untouched - icons, wallpaper etc. So that would be the way to update MIUI if they prepare a new one.
Is there anyway to root the phone without connecting it to pc?
noob456 said:
So I tried the update. First time it said it failed, second time it downloaded the whole ROM after which it rebooted device and TWRP started doing "something" - I don't know what. After that the phone didn't want to boot, and what's even better didn't want to run recovery (TWRP), instead it went into fastboot. What I had to do was to use MiPhoneDrivers from this topic: https://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594 (including MiFlash 2015, because 2016 version didn't want to work properly on my PC) and follow the instruction from official MIUI website to flash from scratch the new ROM MIUI 8.2.3.0 which I did. After that my phone was alive again. I installed TWRP and rooted the phone again. Now I've got MIUI 8.2.30 rooted. :] End of the story so far. My settings left untouched - icons, wallpaper etc. So that would be the way to update MIUI if they prepare a new one.
Click to expand...
Click to collapse
Thanks for saving me the trouble.
Can someone help with a better method of applying updates?
Will downloading the zip (1.4GB approx) and flashing via TWRP help?
What are the steps to be able to update to Android 10?
Can't seem to find it anywhere. Coming from pie. Thank you.
It was said that Edxposed does not work on android 10. Will eye on this as I need Edxposed badly, currently on Pie.
bush911 said:
It was said that Edxposed does not work on android 10. Will eye on this as I need Edxposed badly, currently on Pie.
Click to expand...
Click to collapse
Edxposed I can remove it. But I know that magisk does work. And that's what I need. Maybe disabling it and updating it will work ?
You can update you Pixel downloading the ota and the factory image from Google repository. Sideload the ota, reboot your phone and wait for the "update optimization" (there is a notification), then you have to patch the boot image (get it from factory) with Magisk Manager. Finally, flash the patched boot image.
In details:
1. Download the full OTA image and the Factory image from Google
2. Keep Magisk and root, copy boot.img from Factory in the Pixel
3. Boot into factory recovery (go in bootloader, choose recovery, keep power and press volume up button).
4. Choose Apply update from ADB
5. From windows: adb sideload fullOTAimage.zip
6. The update will take awhile
7. Reboot and let the update finish in android
8. Load magisk and patch the boot.img, copy patch_boot.img to computer
9. Boot into the bootloader
10. Flash the patched boot image with: fastboot flash boot patch_boot.img
BUT in the Google repository there are 2 version of ota/factory images (.019 e .020). I don't know the difference.
Edit: you need the Magisk Manager canary version, see this post: https://forum.xda-developers.com/pixel-3/how-to/guide-patching-boot-img-magisk-canary-t3964359
Simone_ASR said:
BUT in the Google repository there are 2 version of ota/factory images (.019 e .020). I don't know the difference.
Click to expand...
Click to collapse
According to what I've read .019 is for those who were already on the betas and .020 is for those upgrading from Pie.
Simone_ASR said:
You can update you Pixel downloading the ota and the factory image from Google repository. Sideload the ota, reboot your phone and wait for the "update optimization" (there is a notification), then you have to patch the boot image (get it from factory) with Magisk Manager. Finally, flash the patched boot image.
In details:
1. Download the full OTA image and the Factory image from Google
2. Keep Magisk and root, copy boot.img from Factory in the Pixel
3. Boot into factory recovery (go in bootloader, choose recovery, keep power and press volume up button).
4. Choose Apply update from ADB
5. From windows: adb sideload fullOTAimage.zip
6. The update will take awhile
7. Reboot and let the update finish in android
8. Load magisk and patch the boot.img, copy patch_boot.img to computer
9. Boot into the bootloader
10. Flash the patched boot image with: fastboot flash boot patch_boot.img
BUT in the Google repository there are 2 version of ota/factory images (.019 e .020). I don't know the difference.
Edit: you need the Magisk Manager canary version, see this post: https://forum.xda-developers.com/pixel-3/how-to/guide-patching-boot-img-magisk-canary-t3964359
Click to expand...
Click to collapse
Awesome man, thank you !
i updated from pie and patched the boot.image so now i have root. i was trying to edit the build.prop for hotspot tethering, the old net.tethering.noprovisioning=true but it wont allow me to edit and save the changes to the build.prop, root explorer is not getting read write permissions or something, root explorer does have super user [permission though. can anyone shed some light on this please
This seems kind of dangerous. It would be great to hear some more people's experience.
Has anyone confirmed whether or not Xposed works on Android 10? Riru Core says that it's compatible with Android 10. As long as Riru core works then Xposed should work. But I would like some confirmation so that I can update.
Ariel_PR said:
Has anyone confirmed whether or not Xposed works on Android 10? Riru Core says that it's compatible with Android 10. As long as Riru core works then Xposed should work. But I would like some confirmation so that I can update.
Click to expand...
Click to collapse
I haven't yet. I've been busy with work. As soon as I get a moment I'll do the update and confirm if everything is working right.
GunToYoMouth123 said:
I haven't yet. I've been busy with work. As soon as I get a moment I'll do the update and confirm if everything is working right.
Click to expand...
Click to collapse
Awesome, let us know!
Ariel_PR said:
Awesome, let us know!
Click to expand...
Click to collapse
I finally updated through OTA while on magisk and disabled it to enable it again with a patch. But with steps. I'll upload it soon for people coming from Android 9 (rooted in magisk) and OTA updating to Q and rooting back with magisk. Xposed will come in next.
GunToYoMouth123 said:
I finally updated through OTA while on magisk and disabled it to enable it again with a patch. But with steps. I'll upload it soon for people coming from Android 9 (rooted in magisk) and OTA updating to Q and rooting back with magisk. Xposed will come in next.
Click to expand...
Click to collapse
I'm exactly the same situation as you, currently on Android 9 rooted with Magisk, and receiving 10 OTA notification, but I don't know how to move foward. Looking for your guide, thanks dude!
GunToYoMouth123 said:
I finally updated through OTA while on magisk and disabled it to enable it again with a patch. But with steps. I'll upload it soon for people coming from Android 9 (rooted in magisk) and OTA updating to Q and rooting back with magisk. Xposed will come in next.
Click to expand...
Click to collapse
Thanks for the update!
ngelee said:
I'm exactly the same situation as you, currently on Android 9 rooted with Magisk, and receiving 10 OTA notification, but I don't know how to move foward. Looking for your guide, thanks dude!
Click to expand...
Click to collapse
Sorry it's taking long. I'm gonna post it here now in a few.
Okay, I work at a fulltime job so please bear with me and sorry for my late responses. And acknowledge that I am not responsible for anything that happens to your device. This step-by-step guide was done on an unlocked Google Pixel 3 XL unlocked bought from the Google Play store. I haven't tested it out on other versions of Pixel 3's or any other phone that isn't the Pixel 3 models since I do not own them, so keep that in mind. My situation was to find out how to update my ALREADY ROOTED/MAGISK version of Android 9 PIE through OTA. Upon checking or looking around I couldn't find any tutorials that are easy for me so with all the info I gathered I decided to wing it and compile steps from a lot of sites,risk it all and used my knowledge to put together this guide. In hopes, this helps everyone else! anyways here we go...
First, PLEASE make sure if you have Edxposed or any other modules or anything that is similiar, uninstall it or remove it. (Applications or mods from magisk are fine, I did this while I had a few mods from magisk, like viperfx, youtube vanice etc..)
1. Disable Automatic system updates in developer options, so it won't install OTAs without your acknowledgment.
2. When an OTA is available, first go to Magisk Manager → Uninstall → Restore Images. Do not reboot or you will have Magisk uninstalled. This will restore your boot back to 100% untouched stock images in order to pass pre-OTA block verifications.
3. After restoring the stock boot image, apply the OTA update as you normally would (Settings → System → System Update).
Wait for the installation to be fully done then press the "Restart now"
Wait for the phone to reboot and let it sit for a few minutes. 10-15 minutes give or take.
Don't panic, let it do its thing.
Once you see the "G" with the loading under it, you should be fine.
let it boot up.
4. Now download the factory zip
download 10.0.0 (QP1A.190711.020, Sep 2019)
5. Once downloaded, open the zip using any zip/rar program. (I HIGHLY recommend WinRar) within THAT zip folder extract the image-crosshatch-qp1a.190711.020.zip somewhere on your desktop.
6. Now then open THAT zip file and from it, extract the boot.img file onto your desktop and move it into your Pixel 3 XL's download folder. (I did it this way, so I recommend it)
7. Now uninstall your old magisk manager and install the latest Magisk Manager (app-release.apk)from HERE
8. Open Magisk Manager and Press Install ==> Press Install again ==> Select Patch a File ==> Select the boot.img file you extracted from the latest factory image that you placed in your Pixel 3 XL.
9. Magisk Manager will patch the boot.img and store the patched boot.img in the download folder as "magisk_patched.img"
10. Copy the magisk_patched.img file to your computer's Platform-tools folder(The one you use to adb push files in etc.) or the folder that has fastboot.exe(your ADB folder should have the fastboot.exe in it normally lol ) in it.
11. Connect the phone to the Computer with USB type- c cord.
12. Open your platform-tools folder if you haven't, and on the search bar type in "cmd" and tap enter on your keyboard.
(the cmd promt should open already in your location)
13. Now boot your Pixel 3 XL into fastboot mode by typing the commad: adb reboot bootloader
14. Once your phone is on fastboot mode then type: fastboot flash boot magisk_patched.img
15. Once it's done then type the command : fastboot reboot
16. Google logo should show,but don't panic give it a few.
Open Magisk and check if its rooted on the manager
And congrats ! you have a Magisk root on Android Q ! :highfive:
Please let me know if it worked for you and let me know if you need any help! :fingers-crossed:
ngelee said:
I'm exactly the same situation as you, currently on Android 9 rooted with Magisk, and receiving 10 OTA notification, but I don't know how to move foward. Looking for your guide, thanks dude!
Click to expand...
Click to collapse
Just posted it above ! please let me know if it works!
does Dolby work on pixel 3 xl? can anyone confirm?
I installed the OTA update the other day, but did anyone figure out if Edxposed Is working on Android 10?
This also works on Pixel 2 XL going from Android 9.0 July image with xposed 19.3.
Here's a simpler guide:
1. Go to Magisk Manager → Uninstall → Restore Images
2. Apply the OTA update and reboot
3. Download factory ZIP for 10.0 (In this case for taimen: Pixel 2 XL Android 10.0 Image)
4. From ZIP extract "taimen-qp1a.190711.020/image-taimen-qp1a.190711.020.zip/boot.img" and put it somewhere in the phone
5. Update Magisk with this version: Link
6. Open Magisk Manager and press: Install -> Install -> Patch a File and then select boot.img extracted before
7. Copy magisk_patched.img that Magisk has made to PC
8. Reboot phone to bootloader: adb reboot bootloader
9. Flash patched boot image: fastboot flash boot magisk_patched.img
10. Reboot phone: fastboot reboot
TL;DR:
Disable Magisk, update 10.0 OTA, upgrade Magisk, patch factory boot image with Magisk and flash boot image.
btw: I recommend Easy 7zip: http://www.e7z.org/ for handling the ZIP in a ZIP
Rom miui 11 stable for realme Q
Sorry English my bad
Fingerprints work
Faceunlock
Bt audio
Wifi,call and more
Bug : No miui camera but may be flash ANX camera support 48mp
Note : Gcam need add configs
Kernel and vendor mod for Q but i thing 5pro will work
How to install:
- wipe all
- flash rom zip
- flash sdcard fix
- flash gapps 9.0 or magisk (if you want)
- if then reboot devices auto boot twrp . you need format data
We are the ones who were used the earliest. So be grateful to the team mokee especially development china CHEN
Link rom and patch : <Mod edit>
Is like the stock Color Os from RealmeQ right?, Only with Asian Languages and English, With MiUi apps and NO Play store or Google apps (Unless flash OGAPPS Of course).
I really need the Spanish Language so is a no go for me, but still, it works pretty good for anyone who wnat to try.
I think would be a good idea to clarify what languages it has.
To clarify, you do all this from TWRP? So this requires that phone is rooted and TWRP installed?
@motherface
The ROM zip packages should be flashed trought TWRP, but its not neccesary to have rooted the phone.
So to clarify, you need to unlock your bootloader, flash TWRP zip trought Fastboot-Bootloader and then reboot to recovery (TWRP).
Tmv_Josue said:
@motherface
The ROM zip packages should be flashed trought TWRP, but its not neccesary to have rooted the phone.
So to clarify, you need to unlock your bootloader, flash TWRP zip trought Fastboot-Bootloader and then reboot to recovery (TWRP).
Click to expand...
Click to collapse
I very much would like to do this - just came from a xiaomi redmi phone, but don't know exactly how to do this. Can you link a tutorial. Gracias
Setup of miui 11 succeeded.If I try to change the default launcher to another one(ex nova launcher), An error message (As launcher apps from third parties may result in problems like data leak, abnormal battery drain and lagging, etc., only those verified by MIUI can be set as your default launcher) appears to change the default launcher. Do you happen to know the solution?
@motherface.
Unlock Bootloader
Go to:
https://forum.xda-developers.com/realme-5-pro/help/realme-5-pro-bootloader-unlock-tutorial-t3985011
1. Install: DeepTesting_SDM710_9.0_Realme.apk
2. Start the in-depth test
3. Download ADB for Windows:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
4. Go to: Settings > Additional settings > Developer options > USB Debugging (Activate it)
5. In PC open CMD and put these commands:
adb reboot bootloader
fastboot flashing unlock
fastboot reboot
TWRP Install:
Go to:
https://forum.xda-developers.com/re...ild-twrp-realme-q-support-flash-ozip-t3986131
adb reboot bootloader
fastboot flash recovery TWRP.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
Tmv_Josue said:
@motherface.
Unlock Bootloader
Go to:
https://forum.xda-developers.com/realme-5-pro/help/realme-5-pro-bootloader-unlock-tutorial-t3985011
1. Install: DeepTesting_SDM710_9.0_Realme.apk
2. Start the in-depth test
3. Download ADB for Windows:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
4. Go to: Settings > Additional settings > Developer options > USB Debugging (Activate it)
5. In PC open CMD and put these commands:
adb reboot bootloader
fastboot flashing unlock
fastboot reboot (System)
TWRP Install:
Go to:
https://forum.xda-developers.com/re...ild-twrp-realme-q-support-flash-ozip-t3986131
adb reboot bootloader
fastboot flash recovery TWRP.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery (Reboot to RECOVERY -TWRP)
Click to expand...
Click to collapse
Got it to work! Thank you very, very much. I am really loving this/needing this. ColorOS is trash.
I initially had issues with the deeptesting app. I think it was because I didn't launch into bootloader through that app itself, and used a different adb command prompt location. Got this work work this time though.
Thanks heaps
I flashed the gapp but it didn't work
hoangnam1103 said:
I flashed the gapp but it didn't work
Click to expand...
Click to collapse
Then download google app installer apk nd try
prashant.palange said:
Then download google app installer apk nd try
Click to expand...
Click to collapse
I installed gapp and downloaded apps from gapp. however I have problems with syncing contacts. It seems the problem is from google sync contact
Hello there
Any possibility to use this ROM with the Realme 5 pro global variant?
@sbsmbm.
Have you tried installing it through the TWRP that works with the R5pro?:
Maybe it works:
https://forum.xda-developers.com/re...ecovery-unofficial-twrp-realme-5-pro-t3985203
THREAD CLOSED!
@29y6145 Please consult the inbox of your private messages.
I see "11.0.0 (RQ1A.201205.003, Dec 2020" is available for Crosshatch and Blueline.
I'm still on Android 9 with Magisk installed by patching the boot image.
Is the following process still valid and supported for applying an OTA update to Android 11, and then re-installing Magisk?
1) Magisk Manager → Uninstall → Restore Images
2) Apply the OTA update :
__a) Boot into factory recovery
__b) Choose Apply update from ADB
__c) From windows: adb sideload crosshatch-ota-rq1a.201205.003-4d6e609b.zip
__d) Reboot phone and let the update finish in Android
3) Separately download the corresponding Factory image: crosshatch-rq1a.201205.003-factory-d5cb2a93.zip. Extract the boot.img, move it into the Pixel 3 XL's download folder
4) Uninstall old Magisk manager and install the latest Magisk Manager (Direct Install Magisk Manager v8.0.4 from here, per Magisk installation instructions)
5 ) Open Magisk Manager and Press Install ==> Press Install again ==> Select Patch a File ==> Select the boot.img file in "Download". It will be patched.
6) Copy the magisk_patched.img file to your computer's Platform-tools folder
7) Boot Pixel 3 XL into fastboot mode by typing the commad: adb reboot bootloader
8) Once phone is on fastboot mode then type: fastboot flash boot magisk_patched.img
9) Once it's done then type the command : fastboot reboot
10) Open Magisk Manager and check if its rooted
This is based on the process from about a year ago. so please reply if anything has changed.
timg11 said:
I see "11.0.0 (RQ1A.201205.003, Dec 2020" is available for Crosshatch and Blueline.
I'm still on Android 9 with Magisk installed by patching the boot image.
Is the following process still valid and supported for applying an OTA update to Android 11, and then re-installing Magisk?
1) Magisk Manager → Uninstall → Restore Images
2) Apply the OTA update :
__a) Boot into factory recovery
__b) Choose Apply update from ADB
__c) From windows: adb sideload crosshatch-ota-rq1a.201205.003-4d6e609b.zip
__d) Reboot phone and let the update finish in Android
3) Separately download the corresponding Factory image: crosshatch-rq1a.201205.003-factory-d5cb2a93.zip. Extract the boot.img, move it into the Pixel 3 XL's download folder
4) Uninstall old Magisk manager and install the latest Magisk Manager (Direct Install Magisk Manager v8.0.4 from here, per Magisk installation instructions)
5 ) Open Magisk Manager and Press Install ==> Press Install again ==> Select Patch a File ==> Select the boot.img file in "Download". It will be patched.
6) Copy the magisk_patched.img file to your computer's Platform-tools folder
7) Boot Pixel 3 XL into fastboot mode by typing the commad: adb reboot bootloader
8) Once phone is on fastboot mode then type: fastboot flash boot magisk_patched.img
9) Once it's done then type the command : fastboot reboot
10) Open Magisk Manager and check if its rooted
This is based on the process from about a year ago. so please reply if anything has changed.
Click to expand...
Click to collapse
You might be able to skip all the step 2's and just check for update after unrooting and take the ota normally. That has worked for me for quite awhile.
Other than that, your steps are spot on and work with 11.
TonikJDK said:
You might be able to skip all the step 2's and just check for update after unrooting and take the ota normally. That has worked for me for quite awhile.
Other than that, your steps are spot on and work with 11.
Click to expand...
Click to collapse
Thanks for the reply. So to take the OTA (which I do get periodic prompts for), I'd just use the "uninstall" function at the bottom of Magisk Manager, then take the update?
Can you confirm that you moved from Pie (9) to Android 11 in one step?
I just posted in a Magisk thread asking about the boot method change between Android 10 and Android 11. I'm unclear of the implications. Hopefully Google has tested all the from/to contingencies in their OTA process?
timg11 said:
Thanks for the reply. So to take the OTA (which I do get periodic prompts for), I'd just use the "uninstall" function at the bottom of Magisk Manager, then take the update?
Can you confirm that you moved from Pie (9) to Android 11 in one step?
I just posted in a Magisk thread asking about the boot method change between Android 10 and Android 11. I'm unclear of the implications. Hopefully Google has tested all the from/to contingencies in their OTA process?
Click to expand...
Click to collapse
Best practice would be to do an actual update and reboot bootloader to flash your patched boot.img. If you are jumping android releases problems might arise that no one can account for and generally you should do a full wipe when switching releases. Google has by no means accounted for any contingencies in the ota process, read the disclaimer they give upon an ota (any data lost in the process is never their fault, so backup you stuff). Patching the boot image through the manager is the preferred method, anything else is very difficult to troubleshoot.
timg11 said:
Thanks for the reply. So to take the OTA (which I do get periodic prompts for), I'd just use the "uninstall" function at the bottom of Magisk Manager, then take the update?
Can you confirm that you moved from Pie (9) to Android 11 in one step?
I just posted in a Magisk thread asking about the boot method change between Android 10 and Android 11. I'm unclear of the implications. Hopefully Google has tested all the from/to contingencies in their OTA process?
Click to expand...
Click to collapse
By boot method do you mean unroot, do not boot, update do not boot, then root the inactive slot?
Do not do that, on 11 it can go bad in fact if you have 11 it will not even be available in Magisk. He took it out for now due to problems.
What I was suggesting bead unroot, boot, take the OTA, boot. Then patch the boot img and flash it.
Hi,
for those who want to install and root the open beta based on android 13, here's how.
Prerequisite
- SDK Platform-Tools for Windows
- OnePlus_USB_Drivers_Setup
- TWRP image file for OnePlus 9 pro
- usb tpye-C otg cable and FAT32 memory card
or usb type-C/usb type-A dual socket memory card
- Android Bootloader Interface driver
Download links for OnePlus 9 Pro full packages:
OnePlus 9 Pro (IN)
OnePlus 9 Pro (NA)
- Be sure that your device is in the latest OxygenOS 12 version C.63 and completely unrooted.
You will need this apk to perform the update: OPLocalUpdate_For_Android12.apk
Be careful this operation will erase all your data. Back them up before updating
- Once the update is done, unlock the bootloader and enable usb debugging.
1- Download the latest TWRP: twrp-3.6.2_11-0-lemonadep.img and put it in the fastboot folder of your pc ( with this twrp you will not be able to access your phone's internal memory but that's not a problem, that's why we need a usb key ).
2- Start your phone in fastboot mode then connect it to your pc.
3- open a command prompt on your pc from the fastboot folder and run ( don't flash, only boot) : fastboot boot twrp-3.6.2_11-0-lemonadep.img
4- once in twrp, connect a usb key to your phone, select Mount / Select Storage / USB storage.
5- go back to Advanced and to Terminal.
6- in the TWRP terminal run : dd if=/dev/block/bootdevice/by-name/boot of=/usbstorage/boot.img
7- disconnect the usb key and plug it into your pc to check that the extraction was successful and that the boot file is indeed present on the usb key.
8- restart your phone.
9- copy and paste the extracted boot.img into the phone's internal memory.
You now have the boot.img file to patch, you just need to install magisk to patch the file.
So as not to end up in bootloop, remember to always test the file with the command : fastboot boot magisk_patched.img
If the phone restarts and you are rooted, reboot to fastboot and run : fastboot flash boot magisk_patched.img
Stock and patched files : LE2121 boot img files / LE2125 boot img files
thanks! this method worked for me.
Shouldn't this same process (incl. TWRP) work on the oneplus 9?
4Xrayk said:
Shouldn't this same process (incl. TWRP) work on the oneplus 9?
Click to expand...
Click to collapse
Normally yes, you just have to use TWRP recovery of your model.
What if I am already in c.63 rooted? Plus where in the steps did you install Android 13?
samdaman91 said:
What if I am already in c.63 rooted? Plus where in the steps did you install Android 13?
Click to expand...
Click to collapse
Updating from c63 to f08 didn't work for me, I had to unroot completely for it to work.
to install the full ota update you must first install this apk OPLocalUpdate_For_Android12.apk.
copy the android13 zip file to your phone (\sdcard)
open OPLocalUpdate_For_Android12 and go to top right corner
select the zip file
Look at Steve0007 thread . Thanks for his work
buu'buu said:
Updating from c63 to f08 didn't work for me, I had to unroot completely.
View attachment 5719027
View attachment 5719023
to install the full ota update you must first install this apk OPLocalUpdate_For_Android12.apk.
copy the android13 zip file to your phone (\sdcard)
open OPLocalUpdate_For_Android12 and go to top right corner
select the zip file
Look at Steve0007 thread . Thanks for his work
Click to expand...
Click to collapse
ok so after unrooting your phone under android 12, you just updated it to android 13 beta? when are you supposed to be back majisk?
I extracted the boot file with TWRP, patched the file and did rooting
what region is your c63 rom?
buu'buu said:
I extracted the boot file with TWRP, patched the file and did rooting
Click to expand...
Click to collapse
how is that possible? TWRP does not work in android 12
I did it , the extracted files are at the bottom of the first post.
it's the file decryption that doesn't work.
With payload dumper I did not succeed.
hey guys I have done a similar thing.
I patched the boot.img from payload.bin using payload dumper.
This is the patched file.
magisk_patched.img
drive.google.com
Copy the file to pc.
Phone to fastboot mode.
Connect via usb.
Enter Powershell using Left Shift + Right CLick
Enter command: fastboot boot <patched file>
It will reboot your phone. If not, enter command: fastboot reboot.
Once rebooted.
Install Magisk App and direct install after this.
Enjoy.
*THIS IS FOR ALL WHO HAVE LOST ROOT ACCESS AFTER UPDATING. BUT CAN ALSO BE FOLLOWED AFTER UNLOCKING THE BOOTLOADER THE 1ST TIME. THIS IS FOR INDIAN VERSIONS ONLY.*
This is for Indian Version only.
how to make system R/0? i need to delete/uninstall system apps and install vanced youtube
this.guy.lol said:
how to make system R/0? i need to delete/uninstall system apps and install vanced youtube
Click to expand...
Click to collapse
GitHub - 0x192/universal-android-debloater: Cross-platform GUI written in Rust using ADB to debloat non-rooted android devices. Improve your privacy, the security and battery life of your device.
Cross-platform GUI written in Rust using ADB to debloat non-rooted android devices. Improve your privacy, the security and battery life of your device. - GitHub - 0x192/universal-android-debloater:...
github.com
Use this to remove stock YouTube app. Then use Vanced Manager to install Vanced.
Here are the files for the EU version (LE2123_11_F.08).
I booted to the patched img and installed Magisk from the manager, worked perfectly.
stock boot.img
patched boot.img
mrironsights said:
GitHub - 0x192/universal-android-debloater: Cross-platform GUI written in Rust using ADB to debloat non-rooted android devices. Improve your privacy, the security and battery life of your device.
Cross-platform GUI written in Rust using ADB to debloat non-rooted android devices. Improve your privacy, the security and battery life of your device. - GitHub - 0x192/universal-android-debloater:...
github.com
Use this to remove stock YouTube app. Then use Vanced Manager to install Vanced.
Click to expand...
Click to collapse
is it 100 percent confirmed working? hate to go through the hassle of installing only for it to not work
this.guy.lol said:
is it 100 percent confirmed working? hate to go through the hassle of installing only for it to not work
Click to expand...
Click to collapse
Works. 100%
mrironsights said:
Works. 100%
Click to expand...
Click to collapse
obviously it dnt.....link me the file that does....
Worked for me. Whats the issue?