Related
I did not find a subforum dedicated to P9 lite mini version so I will post this guide here , as I know that many users that have this phone wish to have it rooted but don't know how.
I apologise to mods in advance if this is wrong place to post this.
Before I start, I will tell you that I am not a programmer and that I just followed a guide to the letter that @txmt5 told me about. So all credits go to him.
Lets start:
0. Make sure that your phone has USB DEBUGGING enabled.
1. a) You will need unlocked bootloader. There is simple official solution to get unlock code by huawei. Just go to their website , UNLOCK tab and follow instructions.
b) Once you get unlock code just use this simple tool by @Mandrigan. BE WARNED : use only unlock bootloader option as other options may brick your phone.
There is also an option to use cmd but I found this one easier to follow and it worked anyway.
Once you unlock your bootloader your phone will give you a warning about it before every boot. This is normal for every device just that some keep silent about it
2. Just install magisk app by @topjohnwu from here. As you do not have costum recovery (as far as I know it is still not developed for our device) you will not be able to root it as usual but it will require additional steps.
3. Get an original unpatched version for your frimware from here. It is really important that you find a right one. It will use the same code that is written in your "update info" in settings so it is easy to find.
4. From the update.zip file you hopefully downloaded in step before you will need to extract BOOT.img file.
To do this use huawei update extractor app by @worstenbrood. I personally use version 0.9.9.5 and extracted only BOOT.img .
It may look like it hangs on full green bar once you extract it. If it hangs for more than 5 minutes it is safe to cancel it and take the BOOT.img file it created. This happened to me and it worked anyways.
5. Put the BOOT.img file from previous step on your device and use magisk on it. It will create patched_boot.img that you will transfer back to your PC
6. Download adb fastboot tools (put patched_boot.img from previous step inside that folder) and HiSuite (just for huawei drivers)
7. Connect your phone to your PC and go to fastboot tools folder (from previous step) and shift+right click anywhere in that folder and take open CMD window here option.
The commands are as follows :
Code:
adb reboot bootloader
after it reboots input
Code:
adb fastboot flash boot patched_boot.img
Your device should be rooted now
You will have root permission but you will not be able to use any other fancy magisk repo app as you do not have TWRP or other custom recovery. And there is really high chance that you will have to repeat this whole thing after every update (it is just my guess) .
I really hope that this guide will help someone
P.S. I wish to thank all people that I tagged and let them know that it was not my wish to spam them but to give them proper credit.
batman1950 said:
5. Put the BOOT.img file from previous step on your device and use magisk on it. It will create patched_boot.img that you will transfer back to your PC
Click to expand...
Click to collapse
Hi, I'm grateful for your contribution to this community. Users who come through here will appreciate.
Can you talk to me about step 5?
breathislava said:
Hi, I'm grateful for your contribution to this community. Users who come through here will appreciate.
Can you talk to me about step 5?
Click to expand...
Click to collapse
I am really glad that you find my guide helpful.
When you go to magisk->install you will need to patch boot file.
Since wedo not have custom recovery you need to provide a path (impossible)
to BOOT.img file so magisk can patch it.
So you just put boot.img you downloaded to phome or sd card and provide path to it
batman1950 said:
I am really glad that you find my guide helpful.
When you go to magisk->install you will need to patch boot file.
Since wedo not have custom recovery you need to provide a path (impossible)
to BOOT.img file so magisk can patch it.
So you just put boot.img you downloaded to phome or sd card and provide path to it
Click to expand...
Click to collapse
I don't understand!
I don't find any "Install" option. Since TWRP is not available for this device, how to proceed?
Can you give me more details?
Until now, I flashed a "ready to be flashed" pre-rooted kernel and I owned SuperUser rights.
Now I want to patch a self-made one. How can I do?
breathislava said:
I don't understand!
I don't find any "Install" option. Since TWRP is not available for this device, how to proceed?
Can you give me more details?
Until now, I flashed a "ready to be flashed" pre-rooted kernel and I owned SuperUser rights.
Now I want to patch a self-made one. How can I do?
Click to expand...
Click to collapse
on newest magisk ver. press install (huge bottun next to magisk icon)-->install--> patch boot image
batman1950 said:
on newest magisk ver. press install (huge bottun next to magisk icon)-->install--> patch boot image
Click to expand...
Click to collapse
I don't find it!
Can you post a screenshot?
breathislava said:
I don't find it!
Can you post a screenshot?
Click to expand...
Click to collapse
for some reason I can't post screenshots -.- I will do it as soon as I get to my laptop
batman1950 said:
for some reason I can't post screenshots -.- I will do it as soon as I get to my laptop
Click to expand...
Click to collapse
Ok, in the meantime, can you explain the whole step 5?
breathislava said:
Ok, in the meantime, can you explain the whole step 5?
Click to expand...
Click to collapse
You just need to put BOOT.img file from step 4. anywhere on your device and use magisk on it.
really don't know how to tell it differently
batman1950 said:
You just need to put BOOT.img file from step 4. anywhere on your device and use magisk on it.
really don't know how to tell it differently
Click to expand...
Click to collapse
What a dumb I am! I forgot to say you that the phone is offline. To understand better my issue, you can read here.
I never thought internet connection was necessary. For now, I have neither a data plan nor a wi-fi internet connection. Is there a way to solve?
Thanks for your patience
breathislava said:
What a dumb I am! I forgot to say you that the phone is offline. To understand better my issue, you can read here.
I never thought internet connection was necessary. For now, I have neither a data plan nor a wi-fi internet connection. Is there a way to solve?
Thanks for your patience
Click to expand...
Click to collapse
I really don't know :/
batman1950 said:
I really don't know :/
Click to expand...
Click to collapse
OK! Thanks!
TWRP available soon
breathislava said:
I don't understand!
I don't find any "Install" option. Since TWRP is not available for this device, how to proceed?
Can you give me more details?
Until now, I flashed a "ready to be flashed" pre-rooted kernel and I owned SuperUser rights.
Now I want to patch a self-made one. How can I do?
Click to expand...
Click to collapse
I'm currently working on a TWRP port for this device. I have only a single problem with data partition.
ioanvlad67 said:
I'm currently working on a TWRP port for this device. I have only a single problem with data partition.
Click to expand...
Click to collapse
Is there any progress )
It doesn't flash it
Vaios1231 said:
It doesn't flash it
Click to expand...
Click to collapse
what step you have a problem with? And are all other steps completed ?
batman1950 said:
what step you have a problem with? And are all other steps completed ?
Click to expand...
Click to collapse
I got it now. All you have to do is not type adb fastboot and just type fastboot flash...
Also another problem that I'm having with rooting another p9 lite mini is that I can't get the bootloader unlock code from huawei anymore. Any solutions? Huawei seems to not want to give you the code anymore.
Vaios1231 said:
I got it now. All you have to do is not type adb fastboot and just type fastboot flash...
Also another problem that I'm having with rooting another p9 lite mini is that I can't get the bootloader unlock code from huawei anymore. Any solutions? Huawei seems to not want to give you the code anymore.
Click to expand...
Click to collapse
I had to type adb as I was on CMD...you were on powershell?
I think they MUST give it to you as it is your phone after all
batman1950 said:
I had to type adb as I was on CMD...you were on powershell?
I think they MUST give it to you as it is your phone after all
Click to expand...
Click to collapse
I was on cmd. Also i have e-mailed Huawei support to give it to me. Do you get the unlock code option on their site? I swear 4 days ago i got it and now it is gone... If you would like, you could add me on discord or such to tell you more details.
Vaios1231 said:
I was on cmd. Also i have e-mailed Huawei support to give it to me. Do you get the unlock code option on their site? I swear 4 days ago i got it and now it is gone... If you would like, you could add me on discord or such to tell you more details.
Click to expand...
Click to collapse
It must be on their site. I will check tonight when I get home
I read through quite a few post here to get everything sorted out and in order to save every one some time here is a summary of all the info I have gathered so far, and my way to thank the forum for offering me so many helpful tips. I'll try to keep this thread updated as information comes in.
All credit goes to their respective owners, I am only aggregating all the information here.
Current status on BL Unlock:
China version: OEM unlock not greyed out, direct BL unlock possible
EU/NA version (L09/L29/L0C): OEM unlock greyed out in developer options, BL unlock possible via FunkyHuawei method by upgrading to .170.
UPDATE 2019/01/02: Some users reported they have already received the .171 update from carrier (https://forum.xda-developers.com/showpost.php?p=78571337&postcount=6), if that is the case you can skip the FH Method part and go directly to unlock BL.
Note: Currently .170 is not GooglePay certified, so Google Pay won't work on this, if you must have Google pay please wait for your carrier to update to some version that support OEM unlock (tap build number 7x to get Developer Options in Settings -> System -> About Phone and then go to Settings -> System -> Developer Options and see if Enable OEM Unlock option is enabled).
Also current recovery install requires you to boot into recovery (Power and volume up with phone disconnected from USB) every single time if you want root, which is not perfect.
The only time you'd be required to wipe your phone is right after your BL is unlocked with fastboot OEM unlock, please make sure you have a backup before doing that step.
Where to get unlock code?
In order to get BL unlocked, you need both allow OEM unlock option NOT greyed out (i.e., you can enable it) AND a BL unlock code. BL unlock code can only be purchased either from FunkyHuawei (55 USD one time for BL unlock code only or if you buy an unlimited pass 132USD for unlimited flashing + BL unlock code (note that it is locked to your phone and can not be transferred)), or MinistryOfSolutions (30 Euro, https://ministryofsolutions.com/huawei-bootloader-unlock-service-all-new-models-new-firmwares, BL unlock code only).
FunkyHuawei Method (for non-China version)
1. Create an account in https://funkyhuawei.club/membersarea, buy 1 credit (if you just want to download .170 firmware, each credit cost 18USD).
2. Go to Select Firmware tab, use LYA-Global if you don't see the exact model. Then select .171 version.
3. Follow instructions here: https://pastebin.com/raw/Db5ZSyqu, you must download the specific HiSuite version (9.0.2.301）and the specific installer executable. Run the executable FHHiSuiteInstaller.exe as administrator (right-click and choose Run As Administrator) <- must run as admin since it will need to modify your host file. Make sure the script runs without error.
3.1 (Additional step for L0C): Edit the c:\users\YOURHOMEFOLDER\appdata\local\hisuite\userdata\updatedogdev\hisuiteconfig.xml file and change LYA-L29 to LYA-L0C everywhere it occurs and save the file. (Thanks to FunkyHuawei Support for pointing this one out).
4. Put the phone into fastboot mode (adb reboot-bootloader or with the phone off connect the usb cable while holding volume down, or boot the phone holding volume down with USB cable connected to PC).
5. Go to HiSuite on your PC and click on System Recovery (furthest to the right towards the bottom of the main screen), and let it do the magic. You will see some cmd windows pop up however it should get to the download progress with a percentage pretty fast, if you don't see that pop up then please check to make sure you have at least one credit in the FH Select Firmware tab and you have installed the specific versions of HiSuite and ran the installer as admin in Step 3.
6. Once everything is completed please verify to see if your firmware version is .171.
Unlock Bootloader
Again, get the BL code and go to Settings -> System -> Developer Options and make sure Enable OEM Unlock option is enabled. Also check to make sure you have everything backed up. Also enable USB Debugging in the same screen as well.
Rest is pretty standard:
Code:
adb devices (will bring up the authorization window on your phone, click on Always Trust)
adb reboot-bootloader
fastboot devices (make sure the device is in fastboot mode)
fastboot oem unlock *UNLOCK CODE*
at this point there will be a format operation performed on the phone, if it didn't complete successfully don't worry, your phone is wiped. During the boot you should see a black window with yellow text of warnings to tell you your phone is unlocked and not secured.
Go through all the steps to initialize the phone, turn on Developer options again, and enable USB Debugging again.
Root
1. Download and install Magisk Manager from this XDA post: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2. Switch channel, go to Magisk Manager -> Settings -> Update Channel , set it to Custom, and the URL is https://bit.ly/2N8UVlq (at the moment, per https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337). Go back to main screen and down swipe to refresh, it should say Latest Version > v18.0.
3. You will need to find the stock RECOVERY_RAMDIS.img file, I used HW Firmware Finder (https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146) to help me with the task, however I couldn't find the L0C update file and ended up using L09 update file instead, which appear to work. I also couldn't find the update.zip for .171 so I ended up using the latest full update version that was available to me (http://update.hicloud.com:8180/TDS/...69/g1750/v181585/f1/full/update_full_base.zip).
4. Unzip the file, drag out UPDATE.APP file in the zip package, and opened it with Huawei Firmware Extractor (I used 0.9.9.5 in this thread: https://forum.xda-developers.com/showthread.php?t=2433454). Extract and open the UPDATE.APP in update file. If you get a checksum error make sure to uncheck both of the verify checksum in Settings -> Extract.
5. Now you should see a RECOVERY_RAMDIS.img file, right click and extract it.
6. Send the RECOVERY_RAMDIS.img file back to your phone (anywhere is fine), go back to Magisk Manager -> Install -> Patch boot, get the patched_boot.img file from the phone back to the PC.
UPDATE 2019/01/02: @pvillasuso was kind enough to post the ramdisk image (both original and Magisk modified) for Mate 20 Pro LYA-L09 (Firmware version .171):https://forum.xda-developers.com/showpost.php?p=78575496&postcount=13, obviously use it at your own risk.
7. Go to fastboot mode again:
Code:
adb devices
adb reboot-bootloader
fastboot devices
fastboot flash recovery_ramdisk "PATH_TO_patched_boot.img"
fastboot reboot
Now your phone should be back to normal with no root yet, turn off your phone and turn it back on by booting into recovery (Power and volume up with phone disconnected from USB)
Boot up and if you go to Magisk now you should be able to see Magisk installed with Installed Version same as Latest Version.
Congrats you are now rooted!
In future you will need to boot into recovery each time to maintain root (which requires you to turn phone off and power + vol up), if you prefer not to do so @ThatsJustLogic suggested you can use the app https://forum.xda-developers.com/showpost.php?p=78569733&postcount=2 to add a one-click reboot from your dropdown menu.
Credits:
@ThatsJustLogic - Figured out the installation steps to patch ramdisk: https://forum.xda-developers.com/showpost.php?p=78554707&postcount=125
@duraaraa - Guy behind FunkyHuawei for figuring out the .171 upgrade and make everything works smoothly https://forum.xda-developers.com/mate-20-pro/how-to/unlock-rebrand-unbrick-update-t3855065
@mutahharbashir - Guy behind MinistryOfSolutions for the unlock BL code.
And creators of Magisk, HWFirmwareFinder, HWUpdateExtractor.
zhuanyi said:
Now your phone should be back to normal with no root yet, turn off your phone and turn it back on by booting into recovery (Power and volume up with phone disconnected from USB)
Click to expand...
Click to collapse
To stop you needing to do this on every boot this app: https://play.google.com/store/apps/details?id=com.superthomaslab.rootessentials allows you to add a "Reboot Recovery" button to your notification tray so its just a one tap reboot instead of holding volume up when you want to reboot after applying a change or something its something small but it saves some hassle.
Awwsome, thank you so much. Now I can finally use Google pay on global firmware 9.0.0.171. It's working perfectly
This is amazing development
Hi, can someone post his oeminfo?
On firmware versions; I have an Australian L29 running an ota update v 168. Oem unlock is available, and Google pay works.
Thank you for the guide.
Can we re-brand from Chinese to international now?
thunderpossuem said:
On firmware versions; I have an Australian L29 running an ota update v 168. Oem unlock is available, and Google pay works.
Click to expand...
Click to collapse
How come? Can you post a screenshot with developer options on yhe screen?? Oh, you have. Can this mean that we will be able to unlock bootloader for free when v168 update arrives to other countries??
Sent from my LYA-L29 using XDA Labs
The 171 official firmware also allows OEM Unlock..
Maybe wait until you get the new update , save a few bucks
deepsrd said:
The 171 official firmware also allows OEM Unlock..
Maybe wait until you get the new update , save a few bucks
Click to expand...
Click to collapse
That's just what i thought
Sent from my LYA-L29 using XDA Labs
Thanks for the guide , Im rooted now !
One question , I have the patched_boot.img file , is it the same for everyone ?
I can share it and it will save some extra steps
Let me know
pvillasuso said:
Thanks for the guide , Im rooted now !
One question , I have the patched_boot.img file , is it the same for everyone ?
I can share it and it will save some extra steps
Let me know
Click to expand...
Click to collapse
The patched file will work for anyone who has the mate 20 pro and the same FW version as you. Theres no extra steps it just removes the finding the FW, extracting and patching the image yourself They will still need magisk and the canary channel.
If you are going to share I would specify Firmware version and attach a non patched one incase people have issues and want to revert.
My phone model : Mate 20 Pro LYA-L09 (Firmware version 9.0.0.211)
patched_boot.img > https://www.mediafire.com/file/fp3jk281d47bh6k/patched_boot.img/file
Apply on your own risk , worked for me !
Hi, glad to hear that even L0C model has to the chance to root. Just wondering after flash the global .171 version which should solve the OEM greyed-out problem, the next step is to purchase a BL unlock code? And is there a chance that after BL and FRP unlocked. My model (LYA-L0C) can be rebrand to another one?
deepsrd said:
The 171 official firmware also allows OEM Unlock..
Maybe wait until you get the new update , save a few bucks
Click to expand...
Click to collapse
Indeed it is 18 USD saved, also hopefully it is more compatible with your phone.
Can you give an example of your path to "PATH_TO_patched_boot.img"
I must be getting syntax incorrect for the file in internal storage download folder, and I have tried everything with and without / leaving out folders.
is this ota proof?
Some rooting questions....
Hi.
I will try to be brief and on topic. Feel free to remove post if not according to Xda forum rules.
Long story short. I am an heavy iOS user from the apple jailbreak scene. I am no developer (only user) and now I have taken the big step from IOS to Android.
Huawei mate 20 pro broke my curiosity. I have always "jailbroken" my iPhone since 2007 and now I am considering root of my HM20PRO.
I have some questions before I try this and brick my phone.
I have Norwegian model, LYA-L29 with 9.0.0.153 (c432) software. (BL unlock greyed out here as well)
How is the partitions setup on this device?
Easy explanation of RAM disk, main disk or whatever?
Do I always have the option to revert to stock setup no matter what? With simple erase/wipe/recover?
Is hisuite the recovery software to use if I want to go back?
Is it possible to unlock the boot loader and go back to 9.0.0.153??
Is the software builds so the highest number software has the latest fixes? (108,122,153,168,171 +++)
Do i loose the safety net like google pay, and other apps that can see that my phone is rooted?
Is there an app to run to trick the apps into believing that the phone is not rooted? (like on iOS)
Hope that someone can take the time to help me with my questions.
The boot via ramdisk/fastboot or what you call it to get rooted is only nesecary on each boot up right? You stay rooted until the next shutdown?
(Semi.tethered on iOS)
sorry for the noob questions, but I am new with this so thanks...
Regards,
Kenneth - Trondheim, Norway
PS:I have to say the switch from iOS to android and Huawei mate 20 pro have been great so far (except new replacement phone on the first day with green screen on BOE screen.) Now all is good.
Main reasons to root android?
I like to have different custom gestures through out the software. And also tweaked apps and notification tweaks, icons.
fromiOS2Android said:
Hi.
How is the partitions setup on this device?
Easy explanation of RAM disk, main disk or whatever?
Do I always have the option to revert to stock setup no matter what? With simple erase/wipe/recover?
Is hisuite the recovery software to use if I want to go back?
Is it possible to unlock the boot loader and go back to 9.0.0.153??
Is the software builds so the highest number software has the latest fixes? (108,122,153,168,171 +++)
Do i loose the safety net like google pay, and other apps that can see that my phone is rooted?
Is there an app to run to trick the apps into believing that the phone is not rooted? (like on iOS)
The boot via ramdisk/fastboot or what you call it to get rooted is only nesecary on each boot up right? You stay rooted until the next shutdown?
(Semi.tethered on iOS)
Main reasons to root android? I like to have different custom gestures through out the software. And also tweaked apps and notification tweaks, icons.
Click to expand...
Click to collapse
Hi, first of all, welcome to Android
My advice is to NOT root until you got an answer to all your questions
I'll let some pros answer the technical questions on the partitions) but here's what I can tell you:
- Main reason to root for me is adblockers and (not a must though) custom roms.
- There is a function within magisk to hide root from apps.
- On the fixes, yes, 171 is the one that allows root and that's also the latest one with all the fixes.
- Once you root you stay rooted, you don't have to repeat the whole process at every boot.
- From what I read in several threads, right now you can't revert to older firmwares. Also, the 171 seems to be market specific, what I will do is to wait until the update gets rolled out in my market by Huawei, I read that the unlock bootloader option is then available officially.
- I would also like to know about google pay (does it brake with root?) and are there other functions that break (camera functions,etc) like it does on other phones (sony for instance)
charliebigpot said:
- I would also like to know about google pay (does it brake with root?) and are there other functions that break (camera functions,etc) like it does on other phones (sony for instance)
Click to expand...
Click to collapse
Using Magisk Hide on Google Pay will prevent it from detecting root, however if SafetyNet fails then it probably still won't work.
There are a few Magisk modules that can (apparently) force SafetyNet to pass, however I haven't ever used any of them.
Everybody trying to flash/boot and everthing that couild work.
But how many have get the eu-version or global?
Have it work for nobudy?
Or that is am that doesnt get what some happen.
Are that money some waiting på Andriod 13, it should couils change language to every app.
I waiting on that, i dont come longer then unlock boatlooder.
Or are that somebody that have any simple instructures ?
I only understand from your message, that you are asking if there is anyone who is using global/eu ROM, correct? So I do use it.
Yes, that was that i was asking,i have tried many different ways but i dont get it.
Did you fink it was easy?
zelma83 said:
Yes, that was that i was asking,i have tried many different ways but i dont get it.
Did you fink it was easy?
Click to expand...
Click to collapse
I have OP10P which is global unlocked at all so I didn't need to switch from chinese coloros to global/europe OOS.
Ok, that was nice
I have eu op10pro unlocked and rooted.
I've got a guide on how to root, plus the stock and patched boot images, I'll release them on each new update.
All will be EU
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com
Great,
But im in mac.
I download the files but i dont know to open then on mac.
And my phone is NE2210_11_A.13. Couild it work with yours settings and files?
Which firmware are to mine?
Thanks that you wrote to me.
zelma83 said:
Great,
But im in mac.
I download the files but i dont know to open then on mac.
And my phone is NE2210_11_A.13. Couild it work with yours settings and files?
Which firmware are to mine?
Thanks that you wrote to me.
Click to expand...
Click to collapse
You'd need windows..
So if you're on a Mac like I am for work then you could use boot camp and have a dual boot or just get parallels, have an OS within an OS, it's £70 a year but it works extremely well..
mxmda said:
I have eu op10pro unlocked and rooted.
Click to expand...
Click to collapse
I've also
Me too
Ok how have you done, like his setttings?
It says that i have one update in oxygen updater, but then it go to recovery,wipe data, reboot. I have tried all.
But couild i use magisk boot file that is to NE2210_11_A.13. like my phone is?
zelma83 said:
Ok how have you done, like his setttings?
It says that i have one update in oxygen updater, but then it go to recovery,wipe data, reboot. I have tried all.
But couild i use magisk boot file that is to NE2210_11_A.13. like my phone is?
Click to expand...
Click to collapse
Your phones saying you have an update?
If you're rooted then you do not want to update the conventional way..
This is in my guide on rooting mate. Just follow it.
In short to update you do this.
1. Install oxygen updater
2. Change update method to full in the app.
3. If an update is available then download the whole thing, it'll be big.
4. Once downloaded, back out and navigate to the normal phones system update and click the 3 dots, then select local upgrade.
5. Take the update and let it install.
DO NOT REBOOT WHEN PROMPTED!!!
6. Back out and open Magisk.
7. Click the top install button and then install after OTA.
8. Reboot and you're updated and rooted.
I'm on NE2210_11_A.13 too, local install doesn't work (it doesn't recognize the Oyxgen ROM)
Ultimatum99 said:
I'm on NE2210_11_A.13 too, local install doesn't work (it doesn't recognize the Oyxgen ROM)
Click to expand...
Click to collapse
Turn on airplane mode,turn off wifi, then reboot, does it show it then?
read this the other day, someone was able to get it to show by doing something like this.
Or could be a Magisk module causing it, if you disable them then reboot, that may make it work.
dladz said:
Turn on airplane mode,turn off wifi, then reboot, does it show it then?
read this the other day, someone was able to get it to show by doing something like this.
Or could be a Magisk module causing it, if you disable them then reboot, that may make it work.
Click to expand...
Click to collapse
It doesn't show if there is an update pending to install. Solution is to reset the phone and not connect it to the internet or to delete the installation hidden files.
Unfortunately the problem is not finding the option, but that when you pick the .zip for Local Install it says it's invalid. I've downloaded the ROM .zip file directly from Oxygen Updater and from external links to no avail.
Ultimatum99 said:
It doesn't show if there is an update pending to install. Solution is to reset the phone and not connect it to the internet or to delete the installation hidden files.
Unfortunately the problem is not finding the option, but that when you pick the .zip for Local Install it says it's invalid. I've downloaded the ROM .zip file directly from Oxygen Updater and from external links to no avail.
Click to expand...
Click to collapse
Ahh I see so can I clarify, at the moment you're on the Chinese OOS?
And you're attempting to install another regions firmware?
dladz said:
Ahh I see so can I clarify, at the moment you're on the Chinese OOS?
And you're attempting to install another regions firmware?
Click to expand...
Click to collapse
Correct, NE2210_11_A.13 is the Chinese version. I'm attempting to simply install an OxygenOS official ROM but it's not allowing to. I have an OP8 Plus and it worked very easily, simply pick the original ROM, local upgrade (now the option is called "Local install" instead) and then clean cache and good to go. This is not working now for whatever reason. I tried both in A.12 CN to A.12 EU and A.13 CN to A.12 EU.
dladz said:
Your phones saying you have an update?
If you're rooted then you do not want to update the conventional way..
This is in my guide on rooting mate. Just follow it.
In short to update you do this.
1. Install oxygen updater
2. Change update method to full in the app.
3. If an update is available then download the whole thing, it'll be big.
4. Once downloaded, back out and navigate to the normal phones system update and click the 3 dots, then select local upgrade.
5. Take the update and let it install.
DO NOT REBOOT WHEN PROMPTED!!!
6. Back out and open Magisk.
7. Click the top install button and then install after OTA.
8. Reboot and you're updated and rooted.
Click to expand...
Click to collapse
It didnt work.
But look here you can se update is availble but not install.
It is in full mode.
I think that i most find something else.
Disclaimer: By attempting this I accept no responsibility for any consequences or repercussions or perceived consequences or repercussions of using this guide or any of the files in it. I'm simply a n00b trying to make things easier for the next guy because this was quite a process and my phone was "bricked" for several days before i found the solution so this is more a "how i did it, maybe it will work for you" guide then most of these guides by guys with a lot more experience than me. If you run into something crazy I didn't run into, ill likely not be able to help you.
With that being said after 3-4 days of struggling, this is what was working TODAY, 6-3-2022
Now that the disclaimer is out of the way, here's a further warning... THIS WILL ONLY WORK FOR THE NORD N100 Metropcs Variant (BE2015) BE82CF. You WILL have issues if you try this on another N100! Furthermore, this will leave you stuck on OOS 10.5.8 (android 10) rooted with no way (that I could find) to update further. If that's not ok with you, well then this guide isn't for you.
PLEASE READ THE WHOLE GUIDE BEFORE BEGINNING TO AVOID MAKING MISTAKES OR MISSING STEPS/NOTES!
So normally we would unlock the bootloader and then install magisk and take our boot.img from the firmware we are on and patch it and flash the patched boot img and then we would be done.... HOWEVER there's not a lot of newer firmware floating around for this phones variant.... so first, a step backwards before we continue.
0) Before you start make sure you have everything you want to keep backed up one way or another because this will wipe your phone several times over and you will lose everything that you don't backup!
1) Flashing OOS 10.5.8 using MSMDownloadtool.exe so that our boot.img will match our current version
So the newest firmware I could find that I could VERIFY belonged to this exact variant was 10.5.8 (android 10). However i was on the newest firmware which was android 11. The boot.img wouldn't match so this could likely brick my device
So first i used the firmware i found to go back to an older firmware that i got from here [OPN100][OOS METRO BE82CF] Unbrick tool to restore your device to OxygenOS
and in case a newer version is posted in the future here's the direct link from this post OOS 10.5.8
I used the included MSMDownloadTool but had trouble connecting until i used my motherboard USB port AND uninstalled the qualcomm driver that was already installed and installed the one i got from this post: Qualcomm HS-USB QDLoader 9008 Drivers: Download & Install
After i finally connected it took me just about 4 minutes to flash the new firmware. Once again you have a fresh clean install. Setup everything really quickly in OFFLINE mode. This is for 2 reasons, one is speed but the other is to stop the auto update of the system firmware! Before enabling internet. enable developer mode and uncheck Automatic System Updates
NOTE: For some people it will make more sense to do this next part first so they aren't stuck on an old firmware for a week while waiting for an unlock token, but regardless if you do these steps first or not they still need to be done here as well since flashing firmware with MSMDownloadTool relocks the bootloader if it was unlocked already.
This is already going to be long so for sake of shortening it im putting these steps here instead
2) Switch the OEM UNLOCK toggle in dev options
We have to flip the OEM Unlocking option in developer options. But it's greyed out! I myself did this the time consuming way but theres two methods, ONLY CHOOSE ONE
2.1a) Its greyed out because you're carried locked. You can get this ungreyed by waiting 6 months and using the stock carrier unlock app named "unlock." You can do this quite easily using this app and following the prompts.
2.1b) There's a way to skip the carrier unlock, after all we dont want to switch carriers just unlock the bootloader. This was found the best way: by accident. Someone made a one plus debloat script and the people that were running it found out that the"unlock bootloader" came unlocked afterwards. It's a neat little script, i ended up running it myself. I found somewhere in my searches the exact command in the script that did it but i can't remember exactly and can't find the post that identified the one command.
I BELIEVE it's one of these three:
com.qualcomm.qti.remoteSimlockAuth
com.qualcomm.qti.uim
com.qualcomm.qti.uimGbaApp
The most obvious one seems to be the remoteSimlockAuth. TBH i only added that because it seemed so obvious. I believe it's actually one of the other two, but i'm just not sure. You could try removing those three only and see if it works. Worse come to worst, run the whole script from this post: One Plus Pure Debloat
NOTE: If you are going to run the whole debloat script make sure to install a keyboard FIRST or you will be stuck without one! Or remove com.google.android.inputmethod.latin from the list.
2.2) No matter which way you completed it (using step 2.1a or 2.1b), the OEM Unlocking toggle in developer option will be usable now. Enable it. While you're in developer options, make sure usb debugging is on because you will need it for the next part. Make sure to plug your phone in and when the rsa key fingerprint pops up, choose "always allow from this computer"
3) Unlocking the bootloader
This part is pretty standard with no serious deviations. I followed this guide from step number 3 on: How to unlock bootloader for OnePlus smart Phone
When you get to step 5 they don't mention it but it takes about a week to get the unlock token.
The only real thing i changed for all of this pretty straightforward guide was when they say the command is fastboot flash cust-unlock <unlock_token.bin> ... Well the bin is called unlock_code.bin so i ended up using fastboot flash cust-unlock unlock_code.bin instead.
Once you finish and your phone restarts, set up the phone quickly in offline mode just to get through it again. Before enabling internet. enable developer mode and uncheck Automatic System Updates. While you're in developer options, make sure usb debugging is on because you will need it further on. Make sure to plug your phone in and when the rsa key fingerprint pops up, choose "always allow from this computer"
4) Decrypt the .OPS firmware file from step 1 to get the boot.img
The next part seemed very complicated but really wasn't. We need to decrypt the .OPS firmware file to get the boot img out of it. I used Oppo Decrypt
There were some changes I needed to make in this section which ended up working, i don't know if the issue was a newer python version or what but if following the readme from the github doesn't work as-is for you, try this instead.
4.1) install python for windows from the official website Python Official Site
4.2) Navigate to the python install directory. C:\Users\%username%\AppData\Local\Programs\Python\PythonXXX\ is the default directory, with %username% being your account username, and XXX being the current python version without the .'s For me this was C:\Users\Kaladin\AppData\Local\Programs\Python\Python310\
Now launch a command prompt from this location.
4.3) Run the command pip3 install -r requirements.txt and if it complains about anything not being updated run that command next to update everything.
4.4) Move a copy of bengal_14_O.04_201221.ops from step 1 into the python310 folder and then run the command opscrypto.py decrypt bengal_14_O.04_201221.ops and wait for it to finish. You can now close the CMD window. You will find the boot.img we need in the "extract" folder in the same directory. Put your phone in file transfer/MTP and move just the boot.img over to your phone or however you want to get this done, do it.
5) Install magisk and root by patching the boot.img and then flashing the patched boot.img
Now we just follow these steps starting at step 2.3 from this guide How to Root OnePlus Nord N100 using Magisk [No TWRP Required]
The only thing that seemed wrong here is in step 3.4 they say to run the command fastboot devices and not only is this not needed but wont work here. If you want to make sure you're connected, use adb devices here instead or reboot to fastboot first before running fastboot devices (so after step 3.5 before step 3.6 instead of step 3.4).
Then, in step 3.6 we have an A/B partition systems, so we need to use the first command only, fastboot flash boot boot.img ... ignore the second part about non A/B Partition systems. Flashing the wrong command here could probably brick your device.
Follow the rest of the guide.
One additional thing i needed to do to obtain root after rebooting was to again open Magisk Manager and click install and choose "Direct Install (recommended)" this time (instead of select file and patch it). When the process is done, reboot your phone and then once it restarts you will be able to download a root checker app off the play store and verify root.
Yay! It was a long journey, but we are done!
NOTE: Magisk has a way to install OTA updates while keeping root by half uninstalling Magisk and reverting to the stock boot.img before allowing the OTA update, then you would reinstall Magisks patched boot.img to the other partition before restarting but i wasn't able to get this to work myself. I will give you the tutorial here though just in case but for me it auto restarted as soon as the OTA update finished installing and updated me to the newest firmware which removed my root and made it so that i had to start this whole process all over again from step 1 (minus the wait time for the carrier unlock and the unlock token of course). So up to you if you want to try this out.
For now i'm just happy to be rooted on a stock rom even if it is a little old. Hope this helps someone out =)
SPECIAL THANKS FOR ALL THE PEOPLE WHO WROTE THE GUIDES, TUTORIALS, AND PROGRAMS USED THAT I LINKED TO! I WOULD HAVE BEEN LOST WITHOUT THESE AND ALSO WITHOUT GOOGLE TO FIND THEM!
any chance you could upload the patched and unpatched boot.img?
dabman710 said:
any chance you could upload the patched and unpatched boot.img?
Click to expand...
Click to collapse
Sure, but i don't know enough to know if you should use the patched one or not. I think you should use magisk and patch yourself.... But ill include it anyways Boot.img from bengalm_14_O.04_201221 it may be totally safe im just not sure. but the boot.img is unaltered.
AesopRock127 said:
Sure, but i don't know enough to know if you should use the patched one or not. I think you should use magisk and patch yourself.... But ill include it anyways Boot.img from bengalm_14_O.04_201221 it may be totally safe im just not sure. but the boot.img is unaltered.
Click to expand...
Click to collapse
i didnt try using your patched boot.img, but the unpatched one worked perfect for me after patching myself. saves everyone a few steps too by having that available. thank you
So even though i debloated all one plus things i could find and kept autoupdate automatically in dev settings turned off , my phone still pushed an update and i lost root.... Unless someone knows how to fix this, CFW may be our only hope of keeping root, at least for this variant
Hello everyone, i just tried updating to the latest ota on android 13 on a rooted 10 pro using the incremental magisk method and now my phone is bricked. wondering if there is a way to recover without losing data. Phone can boot into fastboot, anything else results in Qualcomm Crashdump mode being displayed on screen. ive connected to a computer and it registers when i type fastboot devices, from that point im pretty much stuck on next steps
I did the same mistake thinking it would work like it would on A12 and ended up sending it in to oneplus to reflash.
In my case I have a NE2215 converted to NE2213, what version are you? Full NE2215?
unsafe8989 said:
In my case I have a NE2215 converted to NE2213, what version are you? Full NE2215?
Click to expand...
Click to collapse
yes full ne2215. quite sad knowing we don't even have proper access to the tools to recover our own phones yet. luckily i kept my op8 for a situation like this.
ltw5ki said:
Hello everyone, i just tried updating to the latest ota on android 13 on a rooted 10 pro using the incremental magisk method and now my phone is bricked. wondering if there is a way to recover without losing data. Phone can boot into fastboot, anything else results in Qualcomm Crashdump mode being displayed on screen. ive connected to a computer and it registers when i type fastboot devices, from that point im pretty much stuck on next steps
Click to expand...
Click to collapse
you are sol. i already told you guys that you'll brick your phone if you use magisk method when updating os versions.
ltw5ki said:
Hello everyone, i just tried updating to the latest ota on android 13 on a rooted 10 pro using the incremental magisk method and now my phone is bricked. wondering if there is a way to recover without losing data. Phone can boot into fastboot, anything else results in Qualcomm Crashdump mode being displayed on screen. ive connected to a computer and it registers when i type fastboot devices, from that point im pretty much stuck on next steps
Click to expand...
Click to collapse
If you did unroot completely you can try to boot into EDL mode, in doing so I managed to flip the boot slot and get mine to boot when I was stuck in crashdump mode.
I updated to C.20 yesterday. The process is to unroot completely with image restore, reboot, then let the the update fully install and reboot. You will update fine but be unrooted. Then you boot a patched boot from bootloader and root directly from Magisk.
Do not forget the reboot after uninstalling Magisk before updating.
I already called op to start the repair process. I am willing to try the edl method in a last ditch effort. Is there a detailed explanation on how to get into edl and the process to flip the boot slot?
ltw5ki said:
I already called op to start the repair process. I am willing to try the edl method in a last ditch effort. Is there a detailed explanation on how to get into edl and the process to flip the boot slot?
Click to expand...
Click to collapse
I'm genuinely not sure how to flip the slot on purpose, it happened to me while I was trying the button combination for EDL mode. I believe you have hold all three buttons (Power, Vol Up&Down) until it restarts, it should vibrate but be a black screen and you can plug the USB in from there to see a port 9008 on the PC. This is very generalized but there are more details all around the forum here.
I will say I believe when it flipped, it booted and I saw the oneplus screen for a split second, the screen sort of glitched, and it immediately rebooted from black screen back to bootloader. I think the switch occurred then.
Also is that from a powered off state or is it possible to do with the phone being on?
Hmmm... I can get into bootloader okay and even launch recovery, but I can't seem to switch the partitions. I contacted support, they can replace the phone, but can't or won't tell me how to switch partitions or load it manually.
Quantumrabbit said:
Hmmm... I can get into bootloader okay and even launch recovery, but I can't seem to switch the partitions. I contacted support, they can replace the phone, but can't or won't tell me how to switch partitions or load it manually.
Click to expand...
Click to collapse
If you can get into bootloader, can you try to fastboot boot a boot image? Does that also lead to a qualcomm crashdump?
Prant said:
If you can get into bootloader, can you try to fastboot boot a boot image? Does that also lead to a qualcomm crashdump?
Click to expand...
Click to collapse
The problem is I don't know if I have any fastbootable images... I have the C19 full zip... would that work to try and fastboot it? Do I fastboot just the C19 bootloader?
I'm not used to being in the situation I'm in right now
Quantumrabbit said:
The problem is I don't know if I have any fastbootable images... I have the C19 full zip... would that work to try and fastboot it? Do I fastboot just the C19 bootloader?
I'm not used to being in the situation I'm in right now
Click to expand...
Click to collapse
Just take a step back and don't do anything rash. Absolutely do not FLASH anything in fastboot, but there are numerous guides around here. You basically want to extract the boot.img from that full upgrade zip's payload.bin file, easiest way being with FastbootEnhance, then use command 'fastboot boot "boot.img"' while you're on bootloader. I'm not sure if this will boot your phone, but it definitely can not damage it as long as you're just booting, so it's worth a shot.
Prant said:
Just take a step back and don't do anything rash. Absolutely do not FLASH anything in fastboot, but there are numerous guides around here. You basically want to extract the boot.img from that full upgrade zip's payload.bin file, easiest way being with FastbootEnhance, then use command 'fastboot boot "boot.img"' while you're on bootloader. I'm not sure if this will boot your phone, but it definitely can not damage it as long as you're just booting, so it's worth a shot.
Click to expand...
Click to collapse
Hey man I'd like to poke at your brain if you don't mind, so I did the same thing as quantumrabbit, didn't reboot after unrooting and got the same issue. My problem was my dumba** tried to follow one of the fastboot guides to try and recover my phone and boy let me tell you I bricked my phone harder then I've ever bricked a phone lol. Anyway I got into contact with OP shipped them the phone, they claim to have repaired it and it should get back to me tomorrow, overall took 2 weeks. I want to avoid doing in this future as root is a must for me, before the 10 Pro I had a 6T. Whenever I was on that device from OOS 9,10 & 11 and custom roms after the update support was over, I was always able to unroot without rebooting, flash the full OTA zip and then install magisk to the next inactive slot. It would work and I would retain root. When I got my 10 Pro, for the first 4 updates that came out for the NE2215 where only incremental. So my method was unroot with no reboot, install the incremental ota, then install root to inactive slot and it worked some how even being incremental updates and without the reboot. Well then, I then converted my NE2215 to a NE2213 using the rollback package, and then update normally until C19 released where I fully unrooted and even factory reset for the OS jump from A12 to A13. C20 came out, and this is where I tried the same stupid method, unroot with no reboot, install full OTA zip, then flash magisk to the inactive slot, this then immediately gave the Qualcomm error people are getting. My question is, is that reboot mandatory and should it always be done, since I never had a issue before hand it slipped my mind. I hope you understand what I'm trying to ask, basically I want to avoid this issue in the future especially with no MSM and OP taking their sweet time to fix my phone, should I always completely unroot and reboot for absolutely any OTA and just manually root again by booting the boot image I'm pretty sure that's a no brainer "yes" to my question but more or less I wanna know what changed from Android 12 where I was able to use the un-recommended method with 4 consecutively updates on NE2215 and about 2 of them on NE2213 after converting. I'd like your insight on why it should be done the correct way and what issues arise etc as you seem knowledgeable. Also the possibilities on how to recover, I saw your solution where you recommend booting a boot image to see if that would work, didn't even cross my mind but I think that would've been the correct approach instead of jumping straight into fastboot flashing like my dumb self did. Thank you!
unsafe8989 said:
Hey man I'd like to poke at your brain if you don't mind, so I did the same thing as quantumrabbit, didn't reboot after unrooting and got the same issue. My problem was my dumba** tried to follow one of the fastboot guides to try and recover my phone and boy let me tell you I bricked my phone harder then I've ever bricked a phone lol. Anyway I got into contact with OP shipped them the phone, they claim to have repaired it and it should get back to me tomorrow, overall took 2 weeks. I want to avoid doing in this future as root is a must for me, before the 10 Pro I had a 6T. Whenever I was on that device from OOS 9,10 & 11 and custom roms after the update support was over, I was always able to unroot without rebooting, flash the full OTA zip and then install magisk to the next inactive slot. It would work and I would retain root. When I got my 10 Pro, for the first 4 updates that came out for the NE2215 where only incremental. So my method was unroot with no reboot, install the incremental ota, then install root to inactive slot and it worked some how even being incremental updates and without the reboot. Well then, I then converted my NE2215 to a NE2213 using the rollback package, and then update normally until C19 released where I fully unrooted and even factory reset for the OS jump from A12 to A13. C20 came out, and this is where I tried the same stupid method, unroot with no reboot, install full OTA zip, then flash magisk to the inactive slot, this then immediately gave the Qualcomm error people are getting. My question is, is that reboot mandatory and should it always be done, since I never had a issue before hand it slipped my mind. I hope you understand what I'm trying to ask, basically I want to avoid this issue in the future especially with no MSM and OP taking their sweet time to fix my phone, should I always completely unroot and reboot for absolutely any OTA and just manually root again by booting the boot image I'm pretty sure that's a no brainer "yes" to my question but more or less I wanna know what changed from Android 12 where I was able to use the un-recommended method with 4 consecutively updates on NE2215 and about 2 of them on NE2213 after converting. I'd like your insight on why it should be done the correct way and what issues arise etc as you seem knowledgeable. Also the possibilities on how to recover, I saw your solution where you recommend booting a boot image to see if that would work, didn't even cross my mind but I think that would've been the correct approach instead of jumping straight into fastboot flashing like my dumb self did. Thank you!
Click to expand...
Click to collapse
your jumping around probably screwed up some partition size. I did not restart for the c20 ota and have no issues.
unsafe8989 said:
Hey man I'd like to poke at your brain if you don't mind, so I did the same thing as quantumrabbit, didn't reboot after unrooting and got the same issue. My problem was my dumba** tried to follow one of the fastboot guides to try and recover my phone and boy let me tell you I bricked my phone harder then I've ever bricked a phone lol. Anyway I got into contact with OP shipped them the phone, they claim to have repaired it and it should get back to me tomorrow, overall took 2 weeks. I want to avoid doing in this future as root is a must for me, before the 10 Pro I had a 6T. Whenever I was on that device from OOS 9,10 & 11 and custom roms after the update support was over, I was always able to unroot without rebooting, flash the full OTA zip and then install magisk to the next inactive slot. It would work and I would retain root. When I got my 10 Pro, for the first 4 updates that came out for the NE2215 where only incremental. So my method was unroot with no reboot, install the incremental ota, then install root to inactive slot and it worked some how even being incremental updates and without the reboot. Well then, I then converted my NE2215 to a NE2213 using the rollback package, and then update normally until C19 released where I fully unrooted and even factory reset for the OS jump from A12 to A13. C20 came out, and this is where I tried the same stupid method, unroot with no reboot, install full OTA zip, then flash magisk to the inactive slot, this then immediately gave the Qualcomm error people are getting. My question is, is that reboot mandatory and should it always be done, since I never had a issue before hand it slipped my mind. I hope you understand what I'm trying to ask, basically I want to avoid this issue in the future especially with no MSM and OP taking their sweet time to fix my phone, should I always completely unroot and reboot for absolutely any OTA and just manually root again by booting the boot image I'm pretty sure that's a no brainer "yes" to my question but more or less I wanna know what changed from Android 12 where I was able to use the un-recommended method with 4 consecutively updates on NE2215 and about 2 of them on NE2213 after converting. I'd like your insight on why it should be done the correct way and what issues arise etc as you seem knowledgeable. Also the possibilities on how to recover, I saw your solution where you recommend booting a boot image to see if that would work, didn't even cross my mind but I think that would've been the correct approach instead of jumping straight into fastboot flashing like my dumb self did. Thank you!
Click to expand...
Click to collapse
Yeah, flashing on this device is a big no go until we get proper recovery tools. 9 times out of 10 you'll make things worse.
While you have people like @g96818 that don't use the full reboot, PC method; when I tried to use that method for C.19, I was the one stuck in qualcomm crash dump last month. When I posted I was informed that with this device, especially since Android 13, doing the incremental systemflash then trying to install magisk to inactive *CAN* leave some weird errors in the system update process.
Either way, for me personally, after that big a scare. I will always update using the full uninstall Magisk with restore images, reboot, flash system update, let it do its thing, then root again using a magisk patched boot image, which is super simple to do. You can use cross region boots, as in 2213 on 2215, done that the past two times. Just remember to never flash, only boot.
Appreciate your guys input, I'll make sure to be extra cautious! Phone comes in today, fingers crossed I successfully update to C20 and root! Lol.
Prant said:
Yeah, flashing on this device is a big no go until we get proper recovery tools. 9 times out of 10 you'll make things worse.
While you have people like @g96818 that don't use the full reboot, PC method; when I tried to use that method for C.19, I was the one stuck in qualcomm crash dump last month. When I posted I was informed that with this device, especially since Android 13, doing the incremental systemflash then trying to install magisk to inactive *CAN* leave some weird errors in the system update process.
Either way, for me personally, after that big a scare. I will always update using the full uninstall Magisk with restore images, reboot, flash system update, let it do its thing, then root again using a magisk patched boot image, which is super simple to do. You can use cross region boots, as in 2213 on 2215, done that the past two times. Just remember to never flash, only boot.
Click to expand...
Click to collapse
One last question, do you remove all your modules first reboot then unroot and reboot?
Prant said:
Yeah, flashing on this device is a big no go until we get proper recovery tools. 9 times out of 10 you'll make things worse.
While you have people like @g96818 that don't use the full reboot, PC method; when I tried to use that method for C.19, I was the one stuck in qualcomm crash dump last month. When I posted I was informed that with this device, especially since Android 13, doing the incremental systemflash then trying to install magisk to inactive *CAN* leave some weird errors in the system update process.
Either way, for me personally, after that big a scare. I will always update using the full uninstall Magisk with restore images, reboot, flash system update, let it do its thing, then root again using a magisk patched boot image, which is super simple to do. You can use cross region boots, as in 2213 on 2215, done that the past two times. Just remember to never flash, only boot.
Click to expand...
Click to collapse
Technically that's on you. I gave a warning that you will brick if you don't fully unroot for c19.
Quantumrabbit said:
The problem is I don't know if I have any fastbootable images... I have the C19 full zip... would that work to try and fastboot it? Do I fastboot just the C19 bootloader?
I'm not used to being in the situation I'm in right now
Click to expand...
Click to collapse
I posted the c20 boots and how to flip the boot so go try it out.