Related
Hi all so I am planning to install a Havoc OS on my phone with TWRP and Magisk
So my question is in the event that the install doesnt work out for me or that I dont like the rom (no rearson why I shouldnt) how do I get back to the original A10 rom?
I have downloaded the OxygenOS 10.0.6 [EU] OnePlus 7 Pro 5G.zip file from here already. Would I be able to go ahead boot into TWRP and flash this ifneeded?
TIA Bart
bartjunited said:
Hi all so I am planning to install a Havoc OS on my phone with TWRP and Magisk
So my question is in the event that the install doesnt work out for me or that I dont like the rom (no rearson why I shouldnt) how do I get back to the original A10 rom?
I have downloaded the OxygenOS 10.0.6 [EU] OnePlus 7 Pro 5G.zip file from here already. Would I be able to go ahead boot into TWRP and flash this ifneeded?
TIA Bart
Click to expand...
Click to collapse
Hi Bart,
Make sure you keep TWRP recovery after flashing custom Rom.
Then if you want to go back, flash official Rom zip on both slots after formatting data otherwise it won't boot.
Thanks for that.
Only thing I'm not sure is what you mean by flashing to both slots?
If for example you get a boot loop can you still get into TWRP?
I assume this is a yes as this is before it boots into the phones OS?
bartjunited said:
Thanks for that.
Only thing I'm not sure is what you mean by flashing to both slots?
If for example you get a boot loop can you still get into TWRP?
I assume this is a yes as this is before it boots into the phones OS?
Click to expand...
Click to collapse
When returning to stock,
format data
Flash stock zip
Flash TWRP
Reboot into recovery which is TWRP
Follow the same steps again and reboot...
If you end up in boot loop, don't stress. You can always flash TWRP recovery again via fastboot.
Since kernel releases are yet to be published " a total duck move by xiaomi ?" I wanted to keep on using the stock ROM without changing anything but miui is too cringy for me to live with it, so I need to put the ol'rooting hat once again
My question is.. did any one actually root it using magisk and can still get ota , or you would need to uninstall magisk then update then get magisk again?
Also what happens to TWRP , can it coexist with miui ?
I had a previous xiaomi phone (mido) but tbh I never even thought of using the miui and switched to RR once I unlocked the bootloader ?
You can get ota with magisk but updating will rewrite boot and recovery so you'll need to re-root.
mr-mero said:
My question is.. did any one actually root it using magisk and can still get ota , or you would need to uninstall magisk then update then get magisk again?
Also what happens to TWRP , can it coexist with miui ?
Click to expand...
Click to collapse
FYI, I'm still on stock EU v12.0.3.0 with mauronofrio TWRP and rooted with Magisk.
I got two OTAs already, the last with v12.0.4.0 -- and it even tried to apply one of them while I wasn't looking but it obviously failed, since there's no stock recovery.
pnin said:
FYI, I'm still on stock EU v12.0.3.0 with mauronofrio TWRP and rooted with Magisk.
I got two OTAs already, the last with v12.0.4.0 -- and it even tried to apply one of them while I wasn't looking but it obviously failed, since there's no stock recovery.
Click to expand...
Click to collapse
What if I reflash the stock recovery.img after rooting, that might get the ota working ?
Yes I know I would still have to flash twrp and magisk again after it
I'll test it on my old phone first , hope it can work as a reference for one last time of it's miserable life
mr-mero said:
What if I reflash the stock recovery.img after rooting, that might get the ota working ?
Click to expand...
Click to collapse
I thought the same, but then I'm not keen on moving to v12.0.4.0 right now, so I didn't budge. Let us know how it goes. :good:
.
How to install magisk on stock miui global after bootloader unlock?
@coolboy744:
In case you haven't already, you'll have to install a custom recovery first...
.
pnin said:
@coolboy744:
In case you haven't already, you'll have to install a custom recovery first...
.
Click to expand...
Click to collapse
yes i know that. using since 2015 TWRp. but i heard there is system wipe issue on poco twrp. if you installed it confirm
No issue here, just flashed it through TWRP as usual.
.
what about installing magisk from orangefox? What are the steps?
abubin said:
what about installing magisk from orangefox? What are the steps?
Click to expand...
Click to collapse
Still the same, just flash the root file and reboot it up... And also install magisk manager to have root management
Orange Fox is much more recommended for our Poco by ManoloRey for installing AOSP ROMS...
yan2xme said:
Still the same, just flash the root file and reboot it up... And also install magisk manager to have root management
Orange Fox is much more recommended for our Poco by ManoloRey for installing AOSP ROMS...
Click to expand...
Click to collapse
thanks! done it and it is working now.
All of the similar threads just end after a few replies (I think because people didn't have unlocked bootloaders) so I thought I'd try to ask again. I have a T-Mo OP8 (IN2017) on 10.5.22IN55CB. I already have the bootloader unlocked. But all of the root methods I can find need a payload.bin from the stock firmware, and I can't seem to find that. Is there another method or a source for branded firmware? I wasn't sure if I could do it by just booting the TWRP found on this board without flashing the recovery.
TIA.
SilverZero said:
All of the similar threads just end after a few replies (I think because people didn't have unlocked bootloaders) so I thought I'd try to ask again. I have a T-Mo OP8 (IN2017) on 10.5.22IN55CB. I already have the bootloader unlocked. But all of the root methods I can find need a payload.bin from the stock firmware, and I can't seem to find that. Is there another method or a source for branded firmware? I wasn't sure if I could do it by just booting the TWRP found on this board without flashing the recovery.
TIA.
Click to expand...
Click to collapse
I booted into TWRP and took a backup of the device. I then transferred the backup to my local PC and took the boot file from the backup, renaming the extension to .img. I then put this boot image on my device and downloaded magisk manager and set magisk manager to install magisk by patching a file. Once completed, I downloaded the patched file to my PC and booted to fastboot. While in fastboot, I flashed the magisk_patched boot image to both boot slots (boot_a, and boot_b). Upon rebooting, I had root. One thing, as soon as you have root, I recommend taking an image of your persist file (for fingerprint) to prevent any issues if the persist partition gets corrupted on your device. Search the forum for instructions on how to do this.
Cheers,
B.D.
You literally don't have to do anything special. Boot TWRP, flash Magisk zip in TWRP, reboot. Done.
stompysan said:
You literally don't have to do anything special. Boot TWRP, flash Magisk zip in TWRP, reboot. Done.
Click to expand...
Click to collapse
Works great. Thanks!
BostonDan said:
I booted into TWRP and took a backup of the device. I then transferred the backup to my local PC and took the boot file from the backup, renaming the extension to .img. I then put this boot image on my device and downloaded magisk manager and set magisk manager to install magisk by patching a file. Once completed, I downloaded the patched file to my PC and booted to fastboot. While in fastboot, I flashed the magisk_patched boot image to both boot slots (boot_a, and boot_b). Upon rebooting, I had root. One thing, as soon as you have root, I recommend taking an image of your persist file (for fingerprint) to prevent any issues if the persist partition gets corrupted on your device. Search the forum for instructions on how to do this.
Cheers,
B.D.
Click to expand...
Click to collapse
Post below yours worked for me but I appreciate the advice on backups and what to watch for. I haven't installed TWRP yet, just booted it and installed.
SilverZero said:
Works great. Thanks!
Click to expand...
Click to collapse
I should state one thing that I didn't in my original post. Booting TWRP and flashing that way ONLY works if you are still running Android 10. Since you have a T-Mobile variant, I knew this was a non-issue (we STILL don't have official A11). For those running Android 11, you do have to patch the boot image and flash it like stated above. Also note that this will likely change if we get TWRP on A11. Once we have that working, flashing Magisk from it should work fine.
stompysan said:
I should state one thing that I didn't in my original post. Booting TWRP and flashing that way ONLY works if you are still running Android 10. Since you have a T-Mobile variant, I knew this was a non-issue (we STILL don't have official A11). For those running Android 11, you do have to patch the boot image and flash it like stated above. Also note that this will likely change if we get TWRP on A11. Once we have that working, flashing Magisk from it should work fine.
Click to expand...
Click to collapse
Following up on this just in case you know anything new. My IN2017 just updated to A11 without any action on my part, and I lost root. Is there a TWRP or patched boot img that you know of for us on TMo now?
There is no working twrp for us on Android 11. I also haven't seen a patched boot image of 11.0.1.3.IN55CB around yet. I have that firmware extracted on my laptop so I could grab the boot image and patch it for you, but I won't be able to do that until later tomorrow. If no one else has it out or if you don't find it before I can get to it, I'll post it up.
Edit: Here's the patched boot image: Magisk Patched Boot IMG TMO 11.0.1.3
It looks like the OP8T OOS recovery doesn't really exist. About the only things it will do is wipe data or reboot to fastboot or system. No sideload.
All of the android devices that I own I have rooted as well as installed new ROMS on them and they had at least a basic recovery. Why doesn't OP8T OOS have a recovery like most any basic android OS? I really don't understand especially since OP has been very user-oriented in dealing with it's fan base. It appears the LOS recovery has these basic features. I expect other ROMS built for OP8T have a working recovery. Is there something unusual about the OP8T?
zzjea said:
It looks like the OP8T OOS recovery doesn't really exist. About the only things it will do is wipe data or reboot to fastboot or system. No sideload.
All of the android devices that I own I have rooted as well as installed new ROMS on them and they had at least a basic recovery. Why doesn't OP8T OOS have a recovery like most any basic android OS? I really don't understand especially since OP has been very user-oriented in dealing with it's fan base. It appears the LOS recovery has these basic features. I expect other ROMS built for OP8T have a working recovery. Is there something unusual about the OP8T?
Click to expand...
Click to collapse
With the move to the A/B model, you now flash updates directly in the running system. So that functionality is no longer required in recovery. Which leaves just factory reset and fastboot as the two functions you can't do while the phone is still running.
Thanks. How do you install a new ROM then?
zzjea said:
Thanks. How do you install a new ROM then?
Click to expand...
Click to collapse
You use the custom ROM's recommended installation process.
You flash images, after unpacking them, with fastbootd.
So if you wanted to go back to OOS stock ROM from a custom ROM, you have to use the MSMtool? Did Android 10 or 11 or OOS change the partition structure for the OP8T? When and why did payload. bin become the container for the img files that used to be directly in the zip file? Is this all about the introduction of the seamless update and the a and b slots?
zzjea said:
So if you wanted to go back to OOS stock ROM from a custom ROM, you have to use the MSMtool? Did Android 10 or 11 or OOS change the partition structure for the OP8T? When and why did payload. bin become the container for the img files that used to be directly in the zip file? Is this all about the introduction of the seamless update and the a and b slots?
Click to expand...
Click to collapse
Have a read of this: https://source.android.com/devices/tech/ota/ab
Note that the OnePlus 8T uses this method - it even gets the updates from Google's servers.
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Thanks,
¿GJ?
¿GotJazz? said:
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Than
Click to expand...
Click to collapse
¿GotJazz? said:
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Thanks,
¿GJ?
Click to expand...
Click to collapse
I had the same issue, I had to downgrade to 11.04, grab a new 11.05 ota from oxygen updater app, extract boot from that and go from there
hammered58 said:
I had the same issue, I had to downgrade to 11.04, grab a new 11.05 ota from oxygen updater app, extract boot from that and go from there
Click to expand...
Click to collapse
Is this the Oxygen Updater App you are referring to, or is it the incremental OTA that I would get from a "OnePlus system update" on a now unrooted and unTWRP'd phone?
Also ... Will I lose any data if I downgrade to 11.04? I've never downgraded before, so do I just install the stock 11.04 image via TWRP like I did the 11.05 image?
Lastly ... I'm assuming this will just get me root, but not including TWRP?
¿GotJazz? said:
Is this the Oxygen Updater App you are referring to, or is it the incremental OTA that I would get from a "OnePlus system update" on a now unrooted and unTWRP'd phone?
Also ... Will I lose any data if I downgrade to 11.04? I've never downgraded before, so do I just install the stock 11.04 image via TWRP like I did the 11.05 image?
Lastly ... I'm assuming this will just get me root, but not including TWRP?
Click to expand...
Click to collapse
1. Yes that is the app Iam talking about.
2. Will you lose data? I always do a format (after the down grade) so I lost data but I never tried it with out formating, it might work, you could try it and see what happens .If it acts strange then it will need a format.
3. Yes you install 11.04 via twrp
4. Yes you will get root but if you want twrp you will have to reinstall
Once you down grade install the oxygen updater, let it download the update , don't let it install it, you can then grab the update from your root directory as it doesn't hide it, then your good to go, you can extract the boot.img by using payload dumper, then take the boot.img and patch that with the magisk app . ( Just install the magisk app on your downgraded 11.04 you don't need root to run the app ) ,,Then after your thru upgrading to 11.05 and after setup just reboot to bootloader and run the magisk patched boot.img, ( fastboot flash boot boot.img) reboot and wait a minute for the magisk app to appear ,it will want to install and do a reboot . Then you can install twrp if you want.
This is how I did it and it worked, you may find a simpler way once you start doing it ,, hth
I'm reluctant to go and do a total wipe (which I have been reading will be required to downgrade).
I'm wondering if the problem I'm facing is that my OP7P needed to be rooted for Magisk 24.1 to be able to successfully patch the latest OP7P build? My OP7P isn't rooted right now although I have v24.1 installed.
I accidentally had installed the latest 11.0.5 OTA before I had a chance to attempt re-rooting.
¿GotJazz? said:
I'm reluctant to go and do a total wipe (which I have been reading will be required to downgrade).
I'm wondering if the problem I'm facing is that my OP7P needed to be rooted for Magisk 24.1 to be able to successfully patch the latest OP7P build? My OP7P isn't rooted right now although I have v24.1 installed.
I accidentally had installed the latest 11.0.5 OTA before I had a chance to attempt re-rooting.
Click to expand...
Click to collapse
Right now I have 11.05 installed and Iam rooted, tomorrow I will unroot and downgrade to 11.04 without wiping and let you know what happens iam curious myself
I'm rooted now. I did have to wipe my OP7P to get root (due solely to my own heavy-handed approach to getting root again).
I posted in another thread, and I think that the thing that might have made a difference for me wasn't that I wiped, but possibly that I removed encryption before installing the Magisk-patched boot image.
¿GotJazz? said:
I'm rooted now. I did have to wipe my OP7P to get root (due solely to my own heavy-handed approach to getting root again).
I posted in another thread, and I think that the thing that might have made a difference for me wasn't that I wiped, but possibly that I removed encryption before installing the Magisk-patched boot image.
Click to expand...
Click to collapse
I guess that's possible , I never thought of that, the only way to know is to do a fresh install only this time setup encryption then try to install magisk . But for now your rooted,, until the bug hits you or me to try another rom then we can start the whole thing over again,,