Hello folks,
I have a Pixel sailfish and I am on Nougat 7.1.2. I would like to just root it via Magisk. Bootloader is unlocked and i tried the latest version of TWRP 3.2.1.2 and latest Magisk 16.0, Magisk Manager is 5.7. Heres the problem, if I tried to flash TWRP and then reboot into recovery (to check if TWRP sticks) I could not access my files because they are all encrypted. I did removed all pass codes, fingerprint etc. Is there a specific version of TWRP, Magisk that I need to install on Nougat 7.1.2? My process is as follow (assume fresh Nougat is onboard):
1. Boot into bootloader
2. Fastboot twrp zip
3. In twrp, flash twrp .zip
4. Reboot into recovery to see if twrp sticks
5. If 4 passes, then flash Magisk zip (version 16)
6. Reboot into system
7. Install Magisk manager apk file
8. Open Magisk manager.
Please let me know,
Thank you very much
I would like to point out that my main goals are: run stock 7.1.2 and root. That's it, no fancy kernels or anything. 8.1 and 8.0 stock are killing my battery so i would like to do some tests on 7.1.2.
You can try set a pin, twrp in nougat worked perfectly.
So when you go in twrp with a pin set, it will 100% ask you the pin for decrypt.
Also, not sure if you made a writing mistake, but you have to fastboot the img, not the zip of twrp
Thanks for this but i still have the same problem. Setting pin in Nougat, then reboot into bootloader, fastboot the .img file works. When in TWRP, it asks for my pin, i enter and manage to decrypt my data. Then I proceed to flash install tpwrp.zip. Process ends well but then when I reboot the phone, then reboot into TWRP (already installed). TWRP is there which means that the installation process is ok. However, this time, it does not ask for my PIN, there is only a slide bar to "Swipe to allow modifications". I did so and my file manager only has a bunch of files with weird letters. I assume these are encrypted. Obviously, I cannot flash install Magisk.zip here. So I tried the following:
1. Fastboot the twrp.img to get into TWRP
2. Do not install TWRP but go to file manager and flash the Magisk.zip
3. The process ended well. I rebooted
4. Phone booted fine. I then installed Magisk Manager v5.7 (latest from XDA) via apk.
5. Installation ended ok.
6. I opened up Magisk Manager and got stuck at the Boot Logo.
I hope these are detailed, please let me know if you can help me.
Thank you very much
TENN3R said:
You can try set a pin, twrp in nougat worked perfectly.
So when you go in twrp with a pin set, it will 100% ask you the pin for decrypt.
Also, not sure if you made a writing mistake, but you have to fastboot the img, not the zip of twrp
Click to expand...
Click to collapse
maxwell0312 said:
... there is only a slide bar to "Swipe to allow modifications". I did so and my file manager only has a bunch of files with weird letters. I assume these are encrypted...
Click to expand...
Click to collapse
Looks like some kinda problem with this twrp version.
Have you tried an older one, just to be sure? From what I remember, latest version made for nougat was 3.1.1 (?) but I'm not sure.
Maybe just try a 3.2.0, for example. Just boot it to avoid problems, don't flash the zip since you are not sure.
Otherwise, you can always try the manual boot.img patch method for magisk, so you don't have to use a recovery (official magisk thread -> installation instructions -> Via magisk manager)
These are only my ideas, not sure if they're gonna work or not.
TENN3R said:
Looks like some kinda problem with this twrp version.
Have you tried an older one, just to be sure? From what I remember, latest version made for nougat was 3.1.1 (?) but I'm not sure.
Maybe just try a 3.2.0, for example. Just boot it to avoid problems, don't flash the zip since you are not sure.
Otherwise, you can always try the manual boot.img patch method for magisk, so you don't have to use a recovery (official magisk thread -> installation instructions -> Via magisk manager)
These are only my ideas, not sure if they're gonna work or not.
Click to expand...
Click to collapse
Thank you very much for your help, I managed to fix and make TWRP stick, so no problem there. Problem now is Magisk doesnt work. Is there a problem with my order:
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
If anyone has any ideas, please let me know.
Thank you
maxwell0312 said:
...
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
...
Click to expand...
Click to collapse
I think for this you better ask in magisk forums. Stable version of magisk also installs the manager apk, I noticed that beta versions don't.
You can find better support in official magisk thread :good:
Hey
maxwell0312 said:
Thank you very much for your help, I managed to fix and make TWRP stick, so no problem there. Problem now is Magisk doesnt work. Is there a problem with my order:
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
If anyone has any ideas, please let me know.
Thank you
Click to expand...
Click to collapse
What version of TWRP did you use..More like what did you do..I am having the same problem.
I used TWRP 3.1.2.0 and 3.2.1.0. All failed. I figured that after flashing TWRP.zip via TWRP Recovery (which you get to after you do fastboot boot twrp.img from PC) , you would need to pick the correct Slot to reboot. Once you boot into the correct slot, then flashing Magisk.zip would work, I think. I kept messing around with reboot into A and B and got tired of it. Now I switched to Resurrection OS for sailfish, got all I want: theming and rootless support. I actually tried to go back to stock 7.1.2 myself to test if batteries improved. It turned out that it didnt really matter much. Also, if you are into Substratum theming like I do, its better to use an OMS rom
Fixed (update)
hardhead808 said:
What version of TWRP did you use..More like what did you do..I am having the same problem.
Click to expand...
Click to collapse
I flashed TWRP 3.1.1-1 then of course went in a recovery bootloop...Just flash SU..... PROFIT
maxwell0312 said:
I used TWRP 3.1.2.0 and 3.2.1.0. All failed. I figured that after flashing TWRP.zip via TWRP Recovery (which you get to after you do fastboot boot twrp.img from PC) , you would need to pick the correct Slot to reboot. Once you boot into the correct slot, then flashing Magisk.zip would work, I think. I kept messing around with reboot into A and B and got tired of it. Now I switched to Resurrection OS for sailfish, got all I want: theming and rootless support. I actually tried to go back to stock 7.1.2 myself to test if batteries improved. It turned out that it didnt really matter much. Also, if you are into Substratum theming like I do, its better to use an OMS rom
Click to expand...
Click to collapse
I found that when I use the uninstall magisk then flash magisk zip, if you watch closely, magisk will install some files to slot b also. Most of the time it will automatically download magisk manager. As far as battery life, my pixel XL was never better on 8.1. I installed the app is 9 preview 2 and my battery life is even better. You should move forward not back.
Good luck
fiverings said:
I found that when I use the uninstall magisk then flash magisk zip, if you watch closely, magisk will install some files to slot b also. Most of the time it will automatically download magisk manager. As far as battery life, my pixel XL was never better on 8.1. I installed the app is 9 preview 2 and my battery life is even better. You should move forward not back.
Good luck
Click to expand...
Click to collapse
What is your SOT when go back with root? Also, what are the versions of TWRP and magisk that you use?
maxwell0312 said:
What is your SOT when go back with root? Also, what are the versions of TWRP and magisk that you use?
Click to expand...
Click to collapse
TWRP version is 3.2.1-2
Magisk is 16.0 version
Magisk is 16.4 installed version
Magisk Manager is 5.7.0
I read somewhere that I should be on 16.2 or 16.3 I read that after I installed 16.4 it didn't work at first, but about 4 or more hours later it started working. I'm certified and pass all tests. After installing Magisk, I always clear cache & data from play store app, then clear just cache from play store services.
Sot, I usually can get around 8 with 15-20% left
Good Luck
fiverings said:
TWRP version is 3.2.1-2
Magisk is 16.0 version
Magisk is 16.4 installed version
Magisk Manager is 5.7.0
I read somewhere that I should be on 16.2 or 16.3 I read that after I installed 16.4 it didn't work at first, but about 4 or more hours later it started working. I'm certified and pass all tests. After installing Magisk, I always clear cache & data from play store app, then clear just cache from play store services.
Sot, I usually can get around 8 with 15-20% left
Good Luck
Click to expand...
Click to collapse
Thanks. I am on the smaller OG Pixel with 2770 mAh battery. I got 6h15 mins of SOT with 5% left. Not sure if this is normal
Was this problem ever resolved? I've been having problems that seem similar. I'm trying to use TWRP with Magisk and the stock google 9.0 for my Pixel, but I keep getting stuck. Wonder if someone has complete set of steps with specific versions of each of the necessary components.
bad post
Related
I had a request to make a Magisk friendly mod to remove the navbar. I don't have this phone and so this has not been tested by me. Thanks to @Fede Luzzi for the necessary files and testing. His steps for a successful install is as follows:
Version 8.1 beta 1, disable lockscreen security for twrp to work.
Flash twrp via fastboot via :
Fastboot flash boot xxxx.img
Boot into recovery
Flash boot IMG for versión 8.1 beta.
Flash magisk 15.3
Flash Tulsadiver zip
Boot
Navbar Gone Magisk zip
https://www.androidfilehost.com/?fid=890129502657583766
@Fede Luzzi,
I have an Magisk aroma mod module maker for you or someone to try. Flash in TWRP. Install the first selection that is a base (it is already selected). Select any mods you want in the Aroma. Hit next. Magisk module maker is already selected for you. Hit next again. A magisk.zip is created on your sdcard in a folder called Magisk. When back in TWRP go find that zip and flash it.
Have a backup though I included a return to stock mod.
There are center clock mods which obviously do you no good with that sensor in the middle of your screen but I left them there anyway.
https://www.androidfilehost.com/?fid=673956719939820683
Tulsadiver said:
@Fede Luzzi,
I have an Magisk aroma mod module maker for you or someone to try. Flash in TWRP. Install the first selection that is a base (it is already selected). Select any mods you want in the Aroma. Hit next. Magisk module maker is already selected for you. Hit next again. A magisk.zip is created on your sdcard in a folder called Magisk. When back in TWRP go find that zip and flash it.
Have a backup though I included a return to stock mod.
There are center clock mods which obviously do you no good with that sensor in the middle of your screen but I left them there anyway.
https://www.androidfilehost.com/?fid=673956719939820683
Click to expand...
Click to collapse
Thanks man!I'll try it during the week and let you know!
Fede Luzzi said:
Thanks man!I'll try it during the week and let you know!
Click to expand...
Click to collapse
Hey, I didn't need any if the mods but anyway I tested it, and it didn't work, it breaks magisk I needed to reinstall it.
Fede Luzzi said:
Hey, I didn't need any if the mods but anyway I tested it, and it didn't work, it breaks magisk I needed to reinstall it.
Click to expand...
Click to collapse
That's too bad. Works great on the pixels and Nexus phones.
Tulsadiver said:
I had a request to make a Magisk friendly mod to remove the navbar. I don't have this phone and so this has not been tested by me. Thanks to @Fede Luzzi for the necessary files and testing. His steps for a successful install is as follows:
Version 8.1 beta 1, disable lockscreen security for twrp to work.
Flash twrp via fastboot via :
Fastboot flash boot xxxx.img
Boot into recovery
Flash boot IMG for versión 8.1 beta.
Flash magisk 15.3
Flash Tulsadiver zip
Boot
Navbar Gone Magisk zip
https://www.androidfilehost.com/?fid=890129502657583766
Click to expand...
Click to collapse
Hi !
I had an issue with my phone and i made a full wipe, when i was trying to install your mod (i love it ) i found out that with the last magisk 16, your installer is not able to detect magisk so it wont install. I had to install magisk 15.3, install your mod, then update to magisk 16.
I want to inform you because probably this is happening with all your magisk mods.
THanks for the great work!!
Fede Luzzi said:
Hi !
I had an issue with my phone and i made a full wipe, when i was trying to install your mod (i love it ) i found out that with the last magisk 16, your installer is not able to detect magisk so it wont install. I had to install magisk 15.3, install your mod, then update to magisk 16.
I want to inform you because probably this is happening with all your magisk mods.
THanks for the great work!!
Click to expand...
Click to collapse
Nope, still working on all my phones ?
..
Hello, I'm still a noob trying to learn, so far with help of this forum I've learned to unlock and root my first android phone, now I'm trying to learn how to properly keep my device updated!
Can someone please give a little rundown to what are the correct steps to update OTA on a rooted twrp device?
I've been browsing the forums a lot but I seem to find a lot of different approaches, or too vague instructions.
It would be greatly appreciated if someone could help me out, step by step, and explain the steps with the commands I need to put in, if there are any.
Thank you
download the ota from here
place it on your phone
go to update on you phone then hit the cog and hit local update
let it up date
reboot to boot loader
fastboot twrp img again
then flash the installer
reboot recovery
then it will boot back in to recovery again
flash root
job done
Hello,
To save you having to fastboot boot TWRP, do the following:
Save the following files to your SDCard:
OTA.zip
Magisk.zip
TWRP.zip
Boot into TWRP
Flash OTA.zip first, then TWRP.zip straight after, then Magisk.zip straight after that, reboot.
@Swatto86 By twrp do you mean TWRP recovery or TWRP installer? I assume that you mean the installer
audinak2 said:
@Swatto86 By twrp do you mean TWRP recovery or TWRP installer? I assume that you mean the installer
Click to expand...
Click to collapse
Sorry yes, put the installer zip on the sdcard
Thank you everyone for the quick replies,
What exactly is it to 'flash' the installer? Is it something I can do from the TWRP screen, just tap on it? Or will I have to put in command prompts?
audinak2 said:
@Swatto86 By twrp do you mean TWRP recovery or TWRP installer? I assume that you mean the installer
Click to expand...
Click to collapse
I have followed this guide https://www.youtube.com/watch?v=Es80k627kTc to unlock/twrp/root, I have a TWRP recovery as far as I know, I'm not sure about 'installer'.
Thanks!
i just download and install the OTA through system updates. Then boot to Trwp recovery and flash magisk . Profit
DampDeceiver said:
Thank you everyone for the quick replies,
What exactly is it to 'flash' the installer? Is it something I can do from the TWRP screen, just tap on it? Or will I have to put in command prompts?
I have followed this guide
to unlock/twrp/root, I have a TWRP recovery as far as I know, I'm not sure about 'installer'.
Thanks!
Click to expand...
Click to collapse
You can flash the installer zip for TWRP through TWRP itself.
Doesn't installing OTA through system settings wipe TWRP? That's why I perform all my updates from TWRP directly.
DampDeceiver said:
Thank you everyone for the quick replies,
What exactly is it to 'flash' the installer? Is it something I can do from the TWRP screen, just tap on it? Or will I have to put in command prompts?
I have followed this guide https://www.youtube.com/watch?v=Es80k627kTc to unlock/twrp/root, I have a TWRP recovery as far as I know, I'm not sure about 'installer'.
Thanks!
Click to expand...
Click to collapse
You have to do twrp/root again after updates. Unlock sticks, but twrp and root don't.
there must be something strange with me then , OTA update doesnt wipe my twrp , i just flash magisk after OTA
Ajaykumar21066 said:
there must be something strange with me then , OTA update doesnt wipe my twrp , i just flash magisk after OTA
Click to expand...
Click to collapse
It prob doesn't overwrite until u reboot so twrp may not have been overwritten on that partition yet, so would make sense, I need to try it out sometime
When you install OTA via system settings and reboot, the slot switches to the inactive one (where the OTA installed to) and boots. This means the previous slot (prior to reboot) still has TWRP installed.
You are probably going direct to recovery after the OTA install without doing a full reboot first.
Swatto is correct. The risk when using twrp is that you must reboot to recovery immediately after flashing the twrp installer zip, or you will boot to the old slot and things will be broken. Rebooting to recovery gets you onto the active, updated slot.
When you reboot to recovery and flash an OTA, you are flashing it to the other slot. The current slot is untouched, while the new active one is completely stock. The twrp installer zip flashes twrp to both slots.
This is the procedure to follow if you want to update via twrp. Personally, I prefer taking the OTA and reinstalling via fastboot just to make sure everything is clean.
lollyjay said:
I have personally tested the following with TWRP already installed and twrp-installer-enchilada-3.2.1-0.zip on your phone:
Download full (not incremental) OOS ROM to your phone and check MD5
Reboot to your installed TWRP
Install the OOS ROM
Do not reboot instead stay in TWRP
Install twrp-installer-enchilada-3.2.1-0.zip
Reboot Recovery
Wipe cache
Reboot System
Click to expand...
Click to collapse
Alright everyone, thanks for all the replies. I have to say even with all your help things were still really confusing for me. I went ahead and ditched TWRP (since I don't really need it anyway), updated OTA through the system, reinstalled magisk before reboot on 2nd slot (the OTA option), and rebooted. And so far all seems fine, I'm on the latest OOS version and I'm still rooted, everything seems to work. Can I do this again in the future and completely overwrite my TWRP installation on my A slot?
I kinda went with TWRP as it's supposed to be more safe for noobs but it ended up making things a lot more difficult to manage.
Thank you
DampDeceiver said:
Alright everyone, thanks for all the replies. I have to say even with all your help things were still really confusing for me. I went ahead and ditched TWRP (since I don't really need it anyway), updated OTA through the system, reinstalled magisk before reboot on 2nd slot (the OTA option), and rebooted. And so far all seems fine, I'm on the latest OOS version and I'm still rooted, everything seems to work. Can I do this again in the future and completely overwrite my TWRP installation on my A slot?
I kinda went with TWRP as it's supposed to be more safe for noobs but it ended up making things a lot more difficult to manage.
Click to expand...
Click to collapse
I have not tried that method as I want twrp, but that is the recommended approach.
I know things have changed with twrp, but it's not that hard once you get used to it. You just have to remember that your phone will switch active slots every time it gets an update or you flash an ota (for example, to go back to stock), so twrp, etc, have to be installed on the other slot before you boot to it. Once you get comfortable with that idea, the rest of it is pretty easy.
Well, I am glad to read this post. Its always interesting how things can be slightly different in every phone manufacturer's setup.
After my lady Huawei device (Honor 6x), I did not want to have to deal with their style of... Control over their devices.
And things seem much easier here, while also being a little confusing right now. I don't fully get the slot a/b stuff yet but it sounds like it's a system to ensure stability on the phone in cases where the newest update could install incorrectly the alternative slot has a backup to ensure the device will function.
Sorta sounds like the dual bios setup on some motherboards. It's good!
Right, so to summarise to ensure I got it right:
1) Downloaded large (1gb+) ota zip from one of these threads, official twrp recovery installing zip, new version of magisk recovery installing zip
2) in recovery install all 3 of those zips in that listed order
3) reboot to recovery again to ensure twrp is still installed
4) profit
Which twrp thread should I take the zip from? There are a few different threads. I shouldn't care about the fastboot version when I already have twrp installed, right?
Either way, it can be much easier than what I had to do on Huawei phones. (currently the easiest phone I used for customisation like this was Nexus 4, but gladly OP6 is getting pretty close to that same level).
Sent from my OnePlus 6 using XDA Labs
You're best off downloading from the official twrp site. If you already have it installed, no need to use the fastboot boot method. You should to reboot to recovery in between flashing twrp and magisk to be sure magisk gets installed on the active slot.
Swatto86 said:
When you install OTA via system settings and reboot, the slot switches to the inactive one (where the OTA installed to) and boots. This means the previous slot (prior to reboot) still has TWRP installed.
You are probably going direct to recovery after the OTA install without doing a full reboot first.
Click to expand...
Click to collapse
Question, more of a scenario really. So if I'm on slot A and have TWRP and Magisk installed, would it be alright to just do a local update and reboot, giving me a perfectly clean install in slot B? Does it work that way? Thanks!
I'm actually using a 6t, but worst case scenario I just use the MSM Download tool, still I wanna get the hang of these confusing A/B devices.
Latest TWRP doesn't support Android Pie 9.0 for OnePlus 6, or at least for me it didn't.
So, I've made a Magisk patched boot image for Android P that we can flash it in fastboot bootloader.
Note: This is not Oxygen OS ROM, this is just a patched boot img for Oxygen OS to make root work. You need to unlock the bootloader before proceeding with anything.
Note 2: Please disable Magisk modules in the Magisk Manager before flashing the patched boot, because some modules might not support the latest OOS and your device will bootloop. If the modules has been updated by the devs to support the latest OOS you can install the modules after that.
Note 3: Sorry guys, I haven't tested the Android Q Developer Previews. Even though Magisk is supported on Q, please flash it at your own risk.
For older versions download from here: Google Drive
Folder updated with Stock boot images as well.
OOS 10 Open Beta 5 Patched Boot
OOS 10 Open Beta 5 Stock Boot
OOS 10.3.1 Patched Boot
OOS 10.3.1 Stock Boot
Flashing instructions:
Code:
fastboot boot (patched_boot_filename_here).img
or
fastboot flash boot (patched_boot_filename_here).img
Thanks @vlaf
reboot to system (if you make another reboot the root won't stick, so continue with the following steps)
Open Magisk (in settings select beta channel) and click install and install Magisk again with Direct Install (recommended)
reboot again and the root will stick even after the reboot.
The thread I followed for the instructions is here. Thanks for @b1czu
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440
Even easier way to root without TWRP:
1. Install OTA update (Don't reboot).
2. Open Magisk Manager, install Magisk and choose "Install to Inactive Slot (After OTA)" (Now reboot).
3. Now you are rooted without TWRP and without any boot img hassles as well.
wow dude that's useful. I don't need TWRP that bad but I need root to use Titanium backups.
Thanks man！
Not work here. Bootloop, only see Bootanimation not more.
SpectraFun said:
Not work here. Bootloop, only see Bootanimation not more.
Click to expand...
Click to collapse
I've tried it again and it worked for me
Are you using Android P Developer Preview 3?
ManikandanGuru said:
I've tried it again and it worked for me
Are you using Android P Developer Preview 3?
Click to expand...
Click to collapse
If you are I can give you the stock boot image for reverting it.
ManikandanGuru said:
I've tried it again and it worked for me
Are you using Android P Developer Preview 3?
Click to expand...
Click to collapse
Yes lol.
It works for me. That's a great help. Thank you.
SpectraFun said:
Yes lol.
Click to expand...
Click to collapse
I've updated the Google drive folder with the stock boot image for DP3.
Download and flash it to revert the bootloop.
I'm not really sure why it didn't work for you. Sorry about that.
Raymond.William said:
wow dude that's useful. I don't need TWRP that bad but I need root to use Titanium backups.
Thanks man！
Click to expand...
Click to collapse
Yeah TiBu is the main reason for me as well.
Worked great for me, thanks! Only issue is I can't get Pokemon Go to work anymore, I'll play around with it.
geoff5093 said:
Worked great for me, thanks! Only issue is I can't get Pokemon Go to work anymore, I'll play around with it.
Click to expand...
Click to collapse
Did you try hiding Pokemon Go in Magisk hide? Because the latest update addressed the Pokemon Go issue as far as I know.
Yeah I did, but I rebooted an additional time and everything works now!
ManikandanGuru said:
Did you try hiding Pokemon Go in Magisk hide? Because the latest update addressed the Pokemon Go issue as far as I know.
Click to expand...
Click to collapse
Sent from my ONEPLUS A6003 using Tapatalk
Easy way to install twrp is to fastboot boot twrp. From there, you must turn on adb sideload and push twrp to phone because it will not decrypt storage. After install, reboot to recover and it will ask for password to decrypt. Then just flash magisk to have root with working twrp. Also, you have to use twrp 3.2.2 or it will crash.
geoff5093 said:
Yeah I did, but I rebooted an additional time and everything works now!
Click to expand...
Click to collapse
That's great.
What about safety net?
G0dofWar said:
What about safety net?
Click to expand...
Click to collapse
The first one, ctsProfile, fails. But the second one basicintegrity passes. I believe the only app I use that checks safetynet is PokemonGo and that works for me.
SpectraFun said:
Not work here. Bootloop, only see Bootanimation not more.
Click to expand...
Click to collapse
Did you unlock your bootloader? Don't think you can boot rooted/unsigned images without unlocking first
toastyp said:
Did you unlock your bootloader? Don't think you can boot rooted/unsigned images without unlocking first
Click to expand...
Click to collapse
Lol sure is unlock.
MrSteelX said:
Easy way to install twrp is to fastboot boot twrp. From there, you must turn on adb sideload and push twrp to phone because it will not decrypt storage. After install, reboot to recover and it will ask for password to decrypt. Then just flash magisk to have root with working twrp. Also, you have to use twrp 3.2.2 or it will crash.
Click to expand...
Click to collapse
Yes. This worked. A simple workaround to get twrp working with encrypted Android P
Download link updated with Beta 1 patched image.
Just updated my phone to Open beta 2, dirty flashed it and it booted up. works perfectly fine. but after i tried to flash magisk 17.1 , it won't boot. stuck at the boot animation.
im using blu spark twrp to flash the magisk.
btw i had magisk installed on 5.1.11 and it works fine too.
any suggestions ? thxx.
UPDATE (09/12) : Issues fixed by installing the uninstaller first then install the magisk 17.1 zip. thx to exelinguy.
Try to do the whole flash procedure again.
Boot into recovery
Flash beta2
Flash twrp
Reboot to twrp
Flash magisk
Boot to system
That way it will be installed on both partitions, could/should do the trick.
Azhar_Fahry said:
Just updated my phone to Open beta 2, dirty flashed it and it booted up. works perfectly fine. but after i tried to flash magisk 17.1 , it won't boot. stuck at the boot animation.
im using blu spark twrp to flash the magisk.
btw i had magisk installed on 5.1.11 and it works fine too.
any suggestions ? thxx.
Click to expand...
Click to collapse
Flash the Magisk uninstaller first to remove any old files, and then flash 17.1 zip again.
Azhar_Fahry said:
Just updated my phone to Open beta 2, dirty flashed it and it booted up. works perfectly fine. but after i tried to flash magisk 17.1 , it won't boot. stuck at the boot animation.
im using blu spark twrp to flash the magisk.
btw i had magisk installed on 5.1.11 and it works fine too.
any suggestions ? thxx.
Click to expand...
Click to collapse
Will upgrading reset the phone or will just upgrade with the same data?
sanu26661 said:
Will upgrading reset the phone or will just upgrade with the same data?
Click to expand...
Click to collapse
it depends on the situation. If you're on the Open beta updating to a newer build, the data will still be there, but if you're on the open beta downgrading a build or downgrading to oreo, your data will be lost.
whizeguy said:
Try to do the whole flash procedure again.
Boot into recovery
Flash beta2
Flash twrp
Reboot to twrp
Flash magisk
Boot to system
That way it will be installed on both partitions, could/should do the trick.
Click to expand...
Click to collapse
I already tried, still nothing
try to change slot A / B
dum143 said:
try to change slot A / B
Click to expand...
Click to collapse
When you install rom, install twrp and reboot to twrp it changes slot. If he has done it 2 times both slots are tested.
exelinguy said:
Flash the Magisk uninstaller first to remove any old files, and then flash 17.1 zip again.
Click to expand...
Click to collapse
I tried to wipe the system and flash the rom, thought that will remove all the Magisk files that already installed before. but then I flash magisk again, it still nothing. just bootloop
Azhar_Fahry said:
I tried to wipe the system and flash the rom, thought that will remove all the Magisk files that already installed before. but then I flash magisk again, it still nothing. just bootloop
Click to expand...
Click to collapse
Nonetheless, just try flashing the magisk uninstaller from here and reflashing magisk 17.1 zip
Refer to section Hotfix v17.1 in topjohnwu's update post
exelinguy said:
Nonetheless, just try flashing the magisk uninstaller from here and reflashing magisk 17.1 zip
Refer to section Hotfix v17.1 in topjohnwu's update post
Click to expand...
Click to collapse
Issues fixed by installing the uninstaller first then install the magisk 17.1 zip. thx for helping me bro. appreciate it.
I'm having the same issue but now twrp won't even show my files although I haven't wiped it. Its only showing like 9gb of storage.
whymista said:
I'm having the same issue but now twrp won't even show my files although I haven't wiped it. Its only showing like 9gb of storage.
Click to expand...
Click to collapse
have u tried to flash the open beta rom zip? I got that problem too, it's shows random folder and it contains nothing. but after I flashed the open beta rom and re flash the twrp from fastboot, it's fixed.
I'm at my wit's end here. I know I'm probably missing some critical step, but I haven't been able to install any OTAs since installing TWRP and Magisk. Fortunately, I was able to update to the latest TWRP before trying (the one that has working decryption) and backup Boot, the two Systems, and Data. I cannot stress enough how important this is!.
The OTA installer detects the device is rooted (or unlocked, if magisk isn't installed) and downloads the OTA. It then asks to install (which is does while booted to system, presumably to the side (A or B) that isn't updated), and asks to reboot. After reboot, the system fails to boot, then goes to the original OnePlus recovery (with the Chinese characters).
I seem to remember reading somewhere that I needed to shut the phone down instead of rebooting, but that doesn't seem to help. I want to know the correct procedure for updating, but I also want to better understand what is actually going on. I'm guessing the boot image on the other side gets overwritten by the OTA, which then flips you to that side, but I don't understand why it doesn't boot. Non-patched boot.img, I suppose?
These steps worked for me:
1 install ota
2 flash TWRP_A_B_Retention_Script-Magisk.zip via magisk
3 install magisk on inactive slot
4 reboot
RocketGeeezer said:
These steps worked for me:
1 install ota
2 flash TWRP_A_B_Retention_Script-Magisk.zip via magisk
3 install magisk on inactive slot
4 reboot
Click to expand...
Click to collapse
Awesome. I had not even heard of the retention script, but it sounds like exactly what I'm missing.
As for step 3, how do you install Magisk on the inactive slot?
Flapjack said:
Awesome. I had not even heard of the retention script, but it sounds like exactly what I'm missing.
As for step 3, how do you install Magisk on the inactive slot?
Click to expand...
Click to collapse
Open magisk, click the first install option and download that zip. Then a box with four options should appear. Click the last option to install on another slot.
whatthekj said:
Open magisk, click the first install option and download that zip. Then a box with four options should appear. Click the last option to install on another slot.
Click to expand...
Click to collapse
Thanks! Trying now!
Flapjack said:
Thanks! Trying now!
Click to expand...
Click to collapse
No problem. Let me know if you have any issues.
Well, it's different (booting to TWRP instead of stock recovery), but it still didn't work. It booted through the "warning...unlocked bootloader" screen twice, then went to TWRP, though without encryption. I was able to switch the boot slot and get into system again (just as it was before the flash), but I don't know what I did wrong.
The only thing different I did was use the tools under EX Kernel Manager to flash the TWRP retention script, as I couldn't find where Magisk could do that.
**EDIT**
Now when I try to do the OTA, I get a "System update installation failed".
I cleared the cache and tried it again, this time doing the retention zip from inside Magisk > Modules > Add (+ sign) option, which is what I'm assuming you did.
It did the exact same thing. After step four, I rebooted, and it went straight into recovery (without the option to decrypt).
I think you have to root your phone again If you have the chinese twrp you can do it via twrp. Otherwise put tj magisk installer on a USB stick
RocketGeeezer said:
I think you have to root your phone again If you have the chinese twrp you can do it via twrp. Otherwise put tj magisk installer on a USB stick
Click to expand...
Click to collapse
I can install/uninstall Magisk all day long, now that I've put TWRP 3.3.1-30 on. Even after a failed update, where it fails to ask to decrypt, I can still sideload via USB and install it (even though I can't see the internal storage).
Flapjack said:
I can install/uninstall Magisk all day long, now that I've put TWRP 3.3.1-30 on. Even after a failed update, where it fails to ask to decrypt, I can still sideload via USB and install it (even though I can't see the internal storage).
Click to expand...
Click to collapse
Can you lflash the ota image again? And after that twrp and after that magisk again. After that reboot to system again. This worked on my pixel. Not shure if this works on the 7 pro...
Maybe do some research first. There is also a unbrick thread
RocketGeeezer said:
Can you lflash the ota image again? And after that twrp and after that magisk again. After that reboot to system again. This worked on my pixel. Not shure if this works on the 7 pro...
Click to expand...
Click to collapse
I've tried that... several times. I wish it worked.
Maybe do some research first. There is also a unbrick thread
Click to expand...
Click to collapse
I've been doing a lot of research. There are some pretty in-depth threads on reddit how the A/B treble system works. Nothing I didn't already know. It's certainly different than pre-treble, but not rocket science... something is wrong with the phone. I would just like to know what I did wrong in the first place so I don't do it again.
Fortunately, I still have a bootable system with root on my B partition, so I was able to run TB and backup everything, along with all my pictures and such. I'll be restoring it to stock and just going from there. Looks like I don't have any other choice.
Flapjack said:
I've tried that... several times. I wish it worked.
I've been doing a lot of research. There are some pretty in-depth threads on reddit how the A/B treble system works. Nothing I didn't already know. It's certainly different than pre-treble, but not rocket science... something is wrong with the phone. I would just like to know what I did wrong in the first place so I don't do it again.
Fortunately, I still have a bootable system with root on my B partition, so I was able to run TB and backup everything, along with all my pictures and such. I'll be restoring it to stock and just going from there. Looks like I don't have any other choice.
Click to expand...
Click to collapse
Okay I updated just like we do with our pixels when we flash a custom ROM. TW RP flash your ota.zip,TWRP zip, reboot to recovery that will switch slots , because your update just flashed to the other slot, then flash magisk then reboot. That's how I did this last update. Oh and it's got to be the full ota from what I read anyways.