Has anyone managed to root their device by patching their boot image and not installing a custom recovery (TWRP)?
I am referring to the method described on the Magisk website:
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
mmedei9 said:
Has anyone managed to root their device by patching their boot image and not installing a custom recovery (TWRP)?
I am referring to the method described on the Magisk website:
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Click to expand...
Click to collapse
I think this would work with the xiaomi.eu rom. And I say it because when I install Magisk through TWRP, it works without the need to close AVB2.0 etc etc. Just install Magisk, reboot and you're good to go.
You need TWRP in order to flash the Xiaomi.eu rom though. Except if you flash all the partitions of the rom one by one through fastboot. And then flash the rooted boot.img.
Side note: I have not managed to root ANY rom (Chinese/global) on the Chinese device while keeping encryption. It always leads to bootloop, except if you disable forceencrypt, which of course leads to loss of encryption.
polfrank said:
Side note: I have not managed to root ANY rom (Chinese/global) on the Chinese device while keeping encryption. It always leads to bootloop, except if you disable forceencrypt, which of course leads to loss of encryption.
Click to expand...
Click to collapse
Do you suspect that the reason rooting via patching boot doesn't work is the encryption then? I'd be willing to disable encryption to obtain root with stock recovery
mmedei9 said:
Do you suspect that the reason rooting via patching boot doesn't work is the encryption then? I'd be willing to disable encryption to obtain root with stock recovery
Click to expand...
Click to collapse
Not exactly. I suspect that it is the reason for bootloop when trying to install Magisk on the Chinese device. Because Magisk does not work on the Chinese device, even if you flash and close avb2.0, you get bootloop.
In global device + global rom, you can disable avb2.0 through TWRP after flashing Magisk, and then reboot normally to get a perfectly rooted phone while keeping encryption.
But if you flash the rooted boot.img through fastboot, how are you going to close avb2.0?
polfrank said:
Not exactly. I suspect that it is the reason for bootloop when trying to install Magisk on the Chinese device. Because Magisk does not work on the Chinese device, even if you flash and close avb2.0, you get bootloop.
In global device + global rom, you can disable avb2.0 through TWRP after flashing Magisk, and then reboot normally to get a perfectly rooted phone while keeping encryption.
But if you flash the rooted boot.img through fastboot, how are you going to close avb2.0?
Click to expand...
Click to collapse
Of the handful of tutorials on the forums, which would you recommend for flashing TWRP and rooting the device?
Would it require me flashing the global rom in the place of my global (EEA) rom?
polfrank said:
I think this would work with the xiaomi.eu rom. And I say it because when I install Magisk through TWRP, it works without the need to close AVB2.0 etc etc. Just install Magisk, reboot and you're good to go.
You need TWRP in order to flash the Xiaomi.eu rom though. Except if you flash all the partitions of the rom one by one through fastboot. And then flash the rooted boot.img.
Side note: I have not managed to root ANY rom (Chinese/global) on the Chinese device while keeping encryption. It always leads to bootloop, except if you disable forceencrypt, which of course leads to loss of encryption.
Click to expand...
Click to collapse
Attention because there will be no more updates for the redmi note 8 pro concerning the rom xiaomi.eu! (announcement on their site ...)
I flashed patched boot image without disabling avb and now I'm stuck in bootloop.
Is it necessary to disable avb before flashing patched image through fastboot?
Related
So I've done a lot of reading and there are multiple threads with steps that aren't exactly clear or contradict each other or are outdated. I just want clarification on what I believe are the steps to flash a custom rom (7.1.2 since I can wait for 8) on a brand new Pixel XL.
Setup phone to the point of enabling adb debugging and oem unlock
Fastboot unlock
Fastboot boot twrp RC1 img
Flash twrp RC2 zip in twrp
Reboot to installed twrp
Wipe system, data, caches
Flash ROM
Flash twrp again
Reboot to twrp
Flash gapps and root method (magisk working for 7.1.2 or should I be using supersu? Also which versions?)
Flash twrp again??
Boot to ROM then setup and use like normal
Should this give me custom ROM, root and twrp that I can boot directly to without a pc again? As long as I do twrp flashing after a ROM each time it'll stick? Also, I keep seeing things for setting a pin before initial twrp boot but without spending 4 days reading I can't find the reason for it. Should I be flashing vendor, bootloader and radio for the latest Nougat release BEFORE unlocking or can I do it through fastboot prior to unlocking?
Coming from Nexus 6P and that was my first run in with the bootloader, radio and vendors so I want to avoid issues for myself. Phone should be here tomorrow and want to get down to business right away lol.
Any and all information is greatly appreciated. If all of this is answered in a centralized area please point me to it and tell me I'm stupid for missing it.
Sent from my SM-N910P using Tapatalk
Found this over in PN thread. Is it accurate? Seems similar to my process.
https://forum.xda-developers.com/showthread.php?p=73846565
wgrant said:
Fastboot boot twrp RC1 img
Flash twrp RC2 zip in twrp
Reboot to installed twrp
Wipe system, data, caches
Flash ROM
Flash twrp again
Reboot to twrp
Flash gapps and root method (magisk working for 7.1.2 or should I be using supersu? Also which versions?)
Flash twrp again??
Boot to ROM then setup and use like normal
https://forum.xda-developers.com/showthread.php?p=73846565
Click to expand...
Click to collapse
Assuming the bootloader is already unlocked and disregarding the unlocking instruction, these instructions are dead on accurate. I personally dont use magisk, but maybe another user will chime in. For 7.1.2 id use supersu 2.82.
You dont have to flash twrp again after flashing gapps and supersu, but its a good practice to have.
noidea24 said:
Assuming the bootloader is already unlocked and disregarding the unlocking instruction, these instructions are dead on accurate. I personally dont use magisk, but maybe another user will chime in. For 7.1.2 id use supersu 2.82.
You dont have to flash twrp again after flashing gapps and supersu, but its a good practice to have.
Click to expand...
Click to collapse
Thank you very much. I'm about to unlock and go nuts on my phone. New phones are so fun to fiddle with!
if you want to use magisk you'll need to flash a custom kernel before you flash magisk. Also you'll need a modified magisk zip. Search around the thread you'll find one, the latest version I found was magisk v13.3.
Edit: Just found out magisk is officially support for pixel on version 14.1 Check out the magisk beta thread.
Hi everyone.
I had a issue and i really want help
I had unlock the OEM,and after installing the twrp and format data (to remove the forced encrypt), i had flash the Disable_Dm-Verity_ForceEncrypt zip file.
Okay, after that i have restarted the device and configure as my away to use, after that, booted on recovery again and flashed the magisk.
But i wanna encrypt my device, and when i go to configs->security and encrypt area, says that my device its not encrypted. Okay, i followed the steps and when i gonna try to encrypt the device, the process start and... some seconds after, the phone just restart and nothing has done.
The onlys changes that i have made on system is: root and flashed a splash.img(without that stupid warning of unlocked bootloader)
I really want to encrypt my device, so, if i get stolen, the thief wont get my user data.
Can anyone help me?
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
marstonpear said:
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
Click to expand...
Click to collapse
Thanks sir, i will try!
marstonpear said:
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
Click to expand...
Click to collapse
Sir, i really need twrp now, its there any way i can enable encrypt after rooting the device? (to sure that, if gets stolen, the data need to be wipped out or the password must be given on twrp)
Same issue, i tried to encrypt on security menu,reboot and nothing was done.
@edit
Better, without TWRP, i can flash other zips via magisk/stock recovery?
mrkeitsuke said:
Sir, i really need twrp now, its there any way i can enable encrypt after rooting the device? (to sure that, if gets stolen, the data need to be wipped out or the password must be given on twrp)
Same issue, i tried to encrypt on security menu,reboot and nothing was done.
@edit
Better, without TWRP, i can flash other zips via magisk/stock recovery?
Click to expand...
Click to collapse
I'm not sure what you're trying to do here, do you want to have TWRP + stock encryption?
If so you can just boot TWRP and flash the TWRP installer package (.zip) inside TWRP to do that. And you don't need to change anything, currently I have TWRP installed and encryption enabled on my Stock ROM.
But if you're trying to get TWRP's own encryption, sadly that doesn't work.
You can also use TWRP without flashing/installing it, just go to the directory TWRP is stored in, open a command line, connect your phone and boot it with this command :
Code:
fastboot boot twrp.img
then flash whatever you'd like.
DO NOT lock your bootloader after you flash something on TWRP, this will most probably brick the device.
marstonpear said:
I'm not sure what you're trying to do here, do you want to have TWRP + stock encryption?
If so you can just boot TWRP and flash the TWRP installer package (.zip) inside TWRP to do that. And you don't need to change anything, currently I have TWRP installed and encryption enabled on my Stock ROM.
But if you're trying to get TWRP's own encryption, sadly that doesn't work.
You can also use TWRP without flashing/installing it, just go to the directory TWRP is stored in, open a command line, connect your phone and boot it with this command :
Code:
fastboot boot twrp.img
then flash whatever you'd like.
DO NOT lock your bootloader after you flash something on TWRP, this will most probably brick the device.
Click to expand...
Click to collapse
I want to stick with the stock rom rooted, with the twrp installed and the user data encrypted
So i can flash things through TWRP even i have encrypt enabled?
@edit
dont worry about bootloader, i will keep unlocked
It's perfectly fine to have TWRP and/or Magisk and encryption using stock ROM.
Flash stock ROM (erase user data)
Install TWRP
install Magisk
Don't flash the encryption Disabler. As its name implies, it disables the automatic encryption of the userdata partition.
a1291762 said:
It's perfectly fine to have TWRP and/or Magisk and encryption using stock ROM.
Flash stock ROM (erase user data)
Install TWRP
install Magisk
Don't flash the encryption Disabler. As its name implies, it disables the automatic encryption of the userdata partition.
Click to expand...
Click to collapse
:highfive: i had done this and... i think its working!!! :crying::crying::crying:
(crying for emotion, almost thirty factory resets to get an good result :crying::crying::crying
Anyway, if anything bad occurs, i will update here, thanks a1291762 and marstonpear
I unlocked and rooted my 8T as described in this thread
https://forum.xda-developers.com/re...de-unlocking-bootloader-twrp-rooting-t4031831
I made decryption including format Data and installing Universal DM-Verity and ForceEncrypt disabler, also installed stock EEA V11.0.3.0.PCXEUXM (MIUI10) and Magisk
All working fine except phone password lock, and as I read now, locks don't work on decrypted phone. So I decide to encrypt my phone back. But it does not work, when I pressed "encrypt phone" button in privacy settings it just reboot and nothing happened.
I tried OrangeFox recovery, made all steps as described here
https://forum.xda-developers.com/redmi-note-8/how-to/guide-flashing-miui-ota-rom-recovery-t4041591
but still the same trouble.. So, how to encrypt phone with stock rom, root and recovery?
rusm said:
I unlocked and rooted my 8T as described in this thread
https://forum.xda-developers.com/re...de-unlocking-bootloader-twrp-rooting-t4031831
I made decryption including format Data and installing Universal DM-Verity and ForceEncrypt disabler, also installed stock EEA V11.0.3.0.PCXEUXM (MIUI10) and Magisk
All working fine except phone password lock, and as I read now, locks don't work on decrypted phone. So I decide to encrypt my phone back. But it does not work, when I pressed "encrypt phone" button in privacy settings it just reboot and nothing happened.
I tried OrangeFox recovery, made all steps as described here
https://forum.xda-developers.com/redmi-note-8/how-to/guide-flashing-miui-ota-rom-recovery-t4041591
but still the same trouble.. So, how to encrypt phone with stock rom, root and recovery?
Click to expand...
Click to collapse
All kind of phone password,pattern,pin,fingerprint,face locks etc do work on decrypted phone in stock rom without any issue..tested myself.... although if you want to encrypt phone again then flash fastboot rom via mi flash
the_weird_aquarian said:
All kind of phone password,pattern,pin,fingerprint,face locks etc do work on decrypted phone in stock rom without any issue..tested myself.... although if you want to encrypt phone again then flash fastboot rom via mi flash
Click to expand...
Click to collapse
Yes, I want encrypted phone.
How it possible with Magisk and recovery?
I need flash fresh EEA 11.0.3.0 from Miflash, than install recovery and Magisk. And what else?
If I install Dm-Verity path, than I need format data and decrypt phone.
If I skip Dm-Verity installation, than I will have a bootloop.
rusm said:
Yes, I want encrypted phone.
How it possible with Magisk and recovery?
I need flash fresh EEA 11.0.3.0 from Miflash, than install recovery and Magisk. And what else?
If I install Dm-Verity path, than I need format data and decrypt phone.
If I skip Dm-Verity installation, than I will have a bootloop.
Click to expand...
Click to collapse
flash the fastboot rom from mi flash and boot it till android setup....you don't necessarily have to set up your phone right now(you can setup your phone no issue though)...then flash orangefox recovery....then in orangefox settings->miui ota settings-> tick everything except Disable Forced Encryption...then flash stock recovery rom through orangefox once....after that flash magisk.... don't flash dm verity....now reboot.
Do not format data in any step..
the_weird_aquarian said:
flash the fastboot rom from mi flash and boot it till android setup....you don't necessarily have to set up your phone right now(you can setup your phone no issue though)...then flash orangefox recovery....then in orangefox settings->miui ota settings-> tick everything except Disable Forced Encryption...then flash stock recovery rom through orangefox once....after that flash magisk.... don't flash dm verity....now reboot.
Do not format data in any step..
Click to expand...
Click to collapse
Thank you! It working.
Seems that OrangeFox do his job well. Now I have encrypted phone with root, and recovery handling my password and decrypt data if need.
Strange, that menu items "Disable DM-Verity" and "Disable forced encryption" gray in my Orangefox any time from initial installation, but everything looks OK in system...
rusm said:
Thank you! It working.
Seems that OrangeFox do his job well. Now I have encrypted phone with root, and recovery handling my password and decrypt data if need.
Strange, that menu items "Disable DM-Verity" and "Disable forced encryption" gray in my Orangefox any time from initial installation, but everything looks OK in system...
Click to expand...
Click to collapse
:good:
I have OnePlus7T Indian version. I was on 11.0.9.1 and rooted with Magisk Canary version. There was an Update to Magisk which I accidentally installed with OTA option instead of full. Now my phone is not booting. It goes into original recovery mode or fastboot only. How can I recover from this? I tried to flash the magisk patched image file and it shows as flashed but when I reboot I again reach original recovery / fastboot menu only. Please help!!
Problem solved but don't know how. I was trying many things and when I used Tool All in One to flash TWRP the phone rebooted into the system. Not even sure if TWRP is installed or not but everything is working now and phone is rooted. Not sure how it got resolved. Magisk is updated to latest version.
jesrani said:
Problem solved but don't know how. I was trying many things and when I used Tool All in One to flash TWRP the phone rebooted into the system. Not even sure if TWRP is installed or not but everything is working now and phone is rooted. Not sure how it got resolved. Magisk is updated to latest version.
Click to expand...
Click to collapse
Most likely changed slot accidentally when it crashed and then corrected on multiple interventions
HueyT said:
Most likely changed slot accidentally when it crashed and then corrected on multiple interventions
Click to expand...
Click to collapse
Hi. I am again having same problem. I updated Magisk Manager and Magisk and some other apps and phone was not booting. After many tries it again booted but all the modules in Magisk were off. So I switched them on and rebooted the phone and now it is just not booting. I tried to use Tool All In One to flash a TWRP but now there is no recovery. The phone is either not booting (stuck on Circle dot rotating) or just going into fastboot, does not go into recovery. I was on OOS11. I tried flashing original recovery through the tool but it fails. Any way out of this mess??
jesrani said:
Hi. I am again having same problem. I updated Magisk Manager and Magisk and some other apps and phone was not booting. After many tries it again booted but all the modules in Magisk were off. So I switched them on and rebooted the phone and now it is just not booting. I tried to use Tool All In One to flash a TWRP but now there is no recovery. The phone is either not booting (stuck on Circle dot rotating) or just going into fastboot, does not go into recovery. I was on OOS11. I tried flashing original recovery through the tool but it fails. Any way out of this mess??
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
This will wipe your data. Otherwise, you can try manually fastboot flash each individual files of oos11 rom:
⭐[ROM][STOCK] 11.0.9.1-GLOBAL-OnePlus7TOxygen_14.O.35_GLO_0350_2206171459-FASTBOOT
Created my own FASTBOOT Rom can anybody test this out, to see if it works please? Used to "Restore the Firmware" on your phone or when bricked you cannot downgrade or upgrade with FASTBOOT Roms, you must be on the same (Firmware Update Global...
forum.xda-developers.com
HueyT said:
This will wipe your data. Otherwise, you can try manually fastboot flash each individual files of oos11 rom:
Click to expand...
Click to collapse
Thanks. I managed to boot the phone but having root problems. After spending a number of hours doing various trials and checking Xda threads I managed to get it to boot again but root was lost.
I again read more articles and learnt that I have to flash recovery to both partitions so I used Tool All in one, changed active slots and flashed the magisk patched image from this thread i think on both slots. But i am not sure. I managed to get root but the Magisk manager was not getting installed.
I tried few other things and finally i am now not able to root again. Phone is booting after I flash a recovery but I am not sure if it will boot if restarted or go into loop.
Can anyone explain the proper procedure and sequence to follow for rooting and which files to use.
I am on OOS11.09.1
jesrani said:
Thanks. I managed to boot the phone but having root problems. After spending a number of hours doing various trials and checking Xda threads I managed to get it to boot again but root was lost.
I again read more articles and learnt that I have to flash recovery to both partitions so I used Tool All in one, changed active slots and flashed the magisk patched image from this thread i think on both slots. But i am not sure. I managed to get root but the Magisk manager was not getting installed.
I tried few other things and finally i am now not able to root again. Phone is booting after I flash a recovery but I am not sure if it will boot if restarted or go into loop.
Can anyone explain the proper procedure and sequence to follow for rooting and which files to use.
I am on OOS11.09.1
Click to expand...
Click to collapse
[OP7T][Stock/Magisk v23.0] OxygenOS 11.0.9.1.HD65AA boot.img
OnePlus 7T OxygenOS 11.0.9.1.HD65AA Global boot.img Stock: https://mega.nz/file/CV9B2I5A#kIjb0ST0XvAn1yJTMi56hdz1asi-d_LH0uaOCcfrA2g Magisk v23.0 Patched: https://mega.nz/file/eFcygLwb#U0m48VlQekyhrKAEC3Oc56yfxdbjGmGhiwgndU-Grwc Note: DISABLE...
forum.xda-developers.com
HueyT said:
[OP7T][Stock/Magisk v23.0] OxygenOS 11.0.9.1.HD65AA boot.img
OnePlus 7T OxygenOS 11.0.9.1.HD65AA Global boot.img Stock: https://mega.nz/file/CV9B2I5A#kIjb0ST0XvAn1yJTMi56hdz1asi-d_LH0uaOCcfrA2g Magisk v23.0 Patched: https://mega.nz/file/eFcygLwb#U0m48VlQekyhrKAEC3Oc56yfxdbjGmGhiwgndU-Grwc Note: DISABLE...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi. I already used these boot images but I was still having a problem. I had flashed the stock image to both partitions and then the Magisk patched image also but either I was not rooted or Magisk App not working. Finally got things to work by installing TWRP to partition a I believe. I changed active partition to a and then flashed the twrp recovery. Again changed active to b and booted and had root. I had to install Magisk Canary 25210 version only as other versions did not install. After checking on net it seems this version is faulty. So I installed Magisk Delta, then installed Magisk using Direct Install option, rebooted, checked regular Magisk Manager and showed the same Magisk version. Removed all modules from old Magisk Manager and unstalled the app. Setup Magisk Delta modules, hide, SuList as well as apps like LSPosed, HMA etc and now everything is working again.
I still am not very sure where the recovery is installed, on partition a or b? And if a difference recovery is installed on each partition what happens? I am pretty sure I had not installed TWRP on partition b. I am also assuming that once I set a partition as active and flash a recovery in fastboot that recovery is flashed to that partition, is this correct? Things are working but I don't know if the phone will go to recovery mode from system, I have not tried that. So I am not very clear yet but still got things to work.
jesrani said:
Hi. I already used these boot images but I was still having a problem. I had flashed the stock image to both partitions and then the Magisk patched image also but either I was not rooted or Magisk App not working. Finally got things to work by installing TWRP to partition a I believe. I changed active partition to a and then flashed the twrp recovery. Again changed active to b and booted and had root. I had to install Magisk Canary 25210 version only as other versions did not install. After checking on net it seems this version is faulty. So I installed Magisk Delta, then installed Magisk using Direct Install option, rebooted, checked regular Magisk Manager and showed the same Magisk version. Removed all modules from old Magisk Manager and unstalled the app. Setup Magisk Delta modules, hide, SuList as well as apps like LSPosed, HMA etc and now everything is working again.
I still am not very sure where the recovery is installed, on partition a or b? And if a difference recovery is installed on each partition what happens? I am pretty sure I had not installed TWRP on partition b. I am also assuming that once I set a partition as active and flash a recovery in fastboot that recovery is flashed to that partition, is this correct? Things are working but I don't know if the phone will go to recovery mode from system, I have not tried that. So I am not very clear yet but still got things to work
Click to expand...
Click to collapse
Only data partition is shared. All else have both A and B parts
So I wanted to switch from OOS 11 to 13.
I was unl;ocked, rooted with magisk installed.
Updated to c47 and flashed magisk. all good.
Then flashed TWRP and tried flashing the full OOS c64 I downloaded.
The flashing failed and now I have no OS since I wiped before flashing as recommended.
At the past with previous devices I just flashed TWRP, flashed the ROM, reflashed TWRP and was done with it.
How can I recover my phone now? All of the data is backed up (contacts, apps, photos) so it's not a big deal if I lose all my data.
Currently I'm at TWRP
PLEASE HELP ME
Also when trying to activate sideload, TWRP is stuck on 'starting ADB sideload feature' and nothing happens, adb devices command doesn't recognize the phone and I have a red warning 'unable to decrypt FBE device'
Just use MSM TOOL and never unlock bootloader.
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
Not sure but I think the problem was installing twrp, as far as I know it does not support installation, just start without installing like, (Fastboot boot twrp.img)
Why didn't you follow all the updates without inventing fashion?
Just download the complete package of the update and does the manual update, does not restart the phone, go in magisk, click install and mark the third option, which is to install after full Ota.
N1ldo said:
Not sure but I think the problem was installing twrp, as far as I know it does not support installation, just start without installing like, (Fastboot boot twrp.img)
Why didn't you follow all the updates without inventing fashion?
Just download the complete package of the update and does the manual update, does not restart the phone, go in magisk, click install and mark the third option, which is to install after full Ota.
Click to expand...
Click to collapse
I don't think TWRP even support flashing OOS.
@N1ldo cause I wanted Android 13 and the OTA failed to update from C47 to C61.
Also I thought that my past experience with flashing the Oneplus 6 will still be relevant, which obviously isn't apparently...
Gonna try to follow the MSM guide.
But for the future, assuming I will succeed in restoring via MSM, what should I do in order to gain root?
1. MSM
2. re-unlock the bootloaded
3. Flash magisk via fastboot
That's it? did I get this right?
Alonzzo2 said:
@N1ldo cause I wanted Android 13 and the OTA failed to update from C47 to C61.
Also I thought that my past experience with flashing the Oneplus 6 will still be relevant, which obviously isn't apparently...
Gonna try to follow the MSM guide.
But for the future, assuming I will succeed in restoring via MSM, what should I do in order to gain root?
1. MSM
2. re-unlock the bootloaded
3. Flash magisk via fastboot
That's it? did I get this right?
Click to expand...
Click to collapse
nope, you boot twrp-3.7.0-12.1 via fastboot (fastboot boot twrp.img) and there you can install magisk. if normal installation doesn't work, try using sideload. if you plan on flashing the twrp installer zip, do it before flashing magisk as it patches your current boot image.
Guest902379028 said:
I don't think TWRP even support flashing OOS.
Click to expand...
Click to collapse
worked fine for me
DirtryElectroOP3 said:
nope, you boot twrp-3.7.0-12.1 via fastboot (fastboot boot twrp.img) and there you can install magisk. if normal installation doesn't work, try using sideload. if you plan on flashing the twrp installer zip, do it before flashing magisk as it patches your current boot image.
Click to expand...
Click to collapse
great. and I can do it regardless of the oos I'm running right? I wouldn't ask that question under normal circumstances but after today, better safe than sorry
Alonzzo2 said:
great. and I can do it regardless of the oos I'm running right? I wouldn't ask that question under normal circumstances but after today, better safe than sorry
Click to expand...
Click to collapse
should work as I described. if you want to be 101% safe, just boot the twrp, but if I remember correctly, the installer should work on oos 13. if you want, you can extract the payload.bin of your current oos so you have the stock boot.img and vendor_boot.img in case anything goes wrong. you can find the exact description here.
Thanks, And one last question, if I'll unlock the bootloader now that I've installed all of the updates up to android 13, it will erase all the data but not the updates, right?
Alonzzo2 said:
Thanks, And one last question, if I'll unlock the bootloader now that I've installed all of the updates up to android 13, it will erase all the data but not the updates, right?
Click to expand...
Click to collapse
Never mind, it works, after the updates I unlocked the bootloader, patched the boot image, booted from it and installed magisk. I now have root.
Thanks all for helping me out!