Related
I'm pretty sure i couldn't be the only one who recently updated from 16.0 to 17.0 (Stable Channel). I first updated the magisk manager and it prompted me to flash 16.0(1600) instead of a 17.0 version. Well since i flashed the 16.0(1600) version it prompted me to download, i got into a nasty bootloop and thankfully recovered with me having the stock ROM in my storage. I'm wondering if anyone else went through the bootloop i did this morning and if people should just flash the newer zips outside of the manager
HighOnLinux said:
I'm pretty sure i couldn't be the only one who recently updated from 16.0 to 17.0 (Stable Channel). I first updated the magisk manager and it prompted me to flash 16.0(1600) instead of a 17.0 version. Well since i flashed the 16.0(1600) version it prompted me to download, i got into a nasty bootloop and thankfully recovered with me having the stock ROM in my storage. I'm wondering if anyone else went through the bootloop i did this morning and if people should just flash the newer zips outside of the manager
Click to expand...
Click to collapse
I also got a bootloop but I flashed 17.0 through twrp. I had to go through the qualcomm drivers process to unbrick it because it was hard bricked lol
Flashed uninstall magisk and than magisk 17 and all worked well.
dracoboss said:
I also got a bootloop but I flashed 17.0 through twrp. I had to go through the qualcomm drivers process to unbrick it because it was hard bricked lol
Click to expand...
Click to collapse
That's horrible to have a hard bricked device. There's a hotfix that just got released right at this moment (17.1) so i'd recommend you to download that and continue the process to try getting root access back
Got the same problems as described here. Then I downloaded the latest Magisk uninstaller and Magisk 17 from the Magisk thread. The next step was to flash the uninstaller and afterwards Magisk 17 and the device booted well.
Running 17.1 and still getting the same thing with safety net check as before
The response is invalid
HighOnLinux said:
That's horrible to have a hard bricked device. There's a hotfix that just got released right at this moment (17.1) so i'd recommend you to download that and continue the process to try getting root access back
Click to expand...
Click to collapse
Yeah that's what I did and everything is fine... For now lol. Thanks
From Magisk 17.0 to Magisk 17.1, install it automatically. SafetyNet test successful
it's better and more secure deinstall first magisk manager clearing cache and data, install magisk 17.1 from twrp and if magisk manager doesnt be installed, install the apk
Hi!
I have a OP6. Running rooted stock with BluSpark TWRP and Magisk. Some months ago I rooted it and I was running 9.0.1 or 9.0.0, not sure which one. I then updated to 9.0.2 OTA a week or so later. I can not remember the exact procedure, but everything worked fine. Today I installed 9.0.3 OTA and then used Magisk (18.0) before reboot to install it to slot A (9.0.2 was on B). Somehow, I ended up with a wiped device and stock recovery. Can anyone help me to find my potential fault in this? I don't want it wiped during the next OTA, it's a real hassle to set up everything again. I remember that I checked a guide that had tips on OTA, but I can't seem to find it.
Best.
yogra1921 said:
Hi!
I have a OP6. Running rooted stock with BluSpark TWRP and Magisk. Some months ago I rooted it and I was running 9.0.1 or 9.0.0, not sure which one. I then updated to 9.0.2 OTA a week or so later. I can not remember the exact procedure, but everything worked fine. Today I installed 9.0.3 OTA and then used Magisk (18.0) before reboot to install it to slot A (9.0.2 was on B). Somehow, I ended up with a wiped device and stock recovery. Can anyone help me to find my potential fault in this? I don't want it wiped during the next OTA, it's a real hassle to set up everything again. I remember that I checked a guide that had tips on OTA, but I can't seem to find it.
Best.
Click to expand...
Click to collapse
I had the same thing happen to me. I missed the part where I flash TWRP right after the OTA. That probably triggered the factory reset
So instead of rebooting, I should do a "fastboot boot IMAGE" and then install the bluspark twrp zip from inside that one? I guess I can boot up to TWRP and install Magisk as well after this while I'm at it?
Are you flashing from twrp?
If so,flash ROM zip
Flash twrp zip
Reboot to twrp
Flash magisk
Done.
If ur doing it from Android
Install ROM,when it asks you to reboot, DON'T
go to magisk app
Go to modules
Search for a/b twrp (you should only find one module)
Install it ,don't reboot
Go to main magisk screen
Press install,install, install to inactive slot (after OTA) after it's done you can REBOOT.
The module keeps your twrp
Flashing magisk to inactive slot will root the update you just installed
I was installing the OTA normally, without TWRP. It worked just fine last time.
You shouldn't install any OTA if you are rooted.
Only full roms.
yogra1921 said:
I was installing the OTA normally, without TWRP. It worked just fine last time.
Click to expand...
Click to collapse
Sent from my ONEPLUS A6003 using Tapatalk
I understand. But it doesn't change the fact that it worked like a charm last time. I just assumed there might be a general way.
RASTAVIPER said:
You shouldn't install any OTA if you are rooted.
Only full roms.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
On OOS it knows if you are rooted and will download full ROM,so it's fine if you install a/b twrp magisk module after (keeps twrp) and then install magisk to inactive slot .
What happened here is he probably forgot to install twrp and magisk probably got to the wrong slot, hence the wipe
Not only probably. I did not install TWRP after the OTA. And I probably got the Magisk slot right (I installed it to other slot though the manager). Thanks for your help!
So next time:
OTA
Check if all dev USB-settings are enabled (?)
Shut off
Boot to TWRP
Install TWRP
Install Magisk to new slot
Boot up
Seems right?
yogra1921 said:
Not only probably. I did not install TWRP after the OTA. And I probably got the Magisk slot right (I installed it to other slot though the manager). Thanks for your help!
So next time:
OTA
Check if all dev USB-settings are enabled (?)
Shut off
Boot to TWRP
Install TWRP
Install Magisk to new slot
Boot up
Seems right?
Click to expand...
Click to collapse
no.... you do what i wrote like 3 posts up.. DO NOT REBOOT!!
After every single rom flash, TWRP, from android or fastboot or whatever way you install any rom TWRP will be replaced, aswell as boot.img (magisk is there)
OTA
DONT REBOOOOOOTT!!!
go to magisk, search for A/B twrp module, install it
DONT REBOOT
Go to main screen of magisk
install, install, install to inactive slot.
done..
your way will wipe TWRP.
From twrp:
Flash rom zip
flash twrp
reboot to twrp
flash magisk
done
Oh yeah. I completely forgot about that the TWRP retention script exists. Perfect. This is exactly what I did last time. Thanks!
Hi everyone,
I had recently upgraded to android 10 (clean flash) and installed TWRP and Magisk and everything was fine. However, one fine day, I performed a random reboot and my phone got stuck in a bootloop. I proceeded to boot into TWRP and flashed Magisk uninstaller and the phone booted again. But now, the problem is that every time I try to flash Magisk, I end up in the same bootloop. I am unsure how to get Magisk installed again and I don't want to Clean flash and set up the device all over again.
Please help me out XDA.
Thank you!
ImperatorShade said:
Hi everyone,
I had recently upgraded to android 10 (clean flash) and installed TWRP and Magisk and everything was fine. However, one fine day, I performed a random reboot and my phone got stuck in a bootloop. I proceeded to boot into TWRP and flashed Magisk uninstaller and the phone booted again. But now, the problem is that every time I try to flash Magisk, I end up in the same bootloop. I am unsure how to get Magisk installed again and I don't want to Clean flash and set up the device all over again.
Please help me out XDA.
Thank you!
Click to expand...
Click to collapse
Hello,
Which instruction did you follow?
What version of rom, twrp and magisk did you have? (maybe with file names).
strongst said:
Hello,
Which instruction did you follow?
What version of rom, twrp and magisk did you have? (maybe with file names).
Click to expand...
Click to collapse
Thank you for the response strongst!
I am using the 10.0.1 GM57AA build right now. Updated directly from 10.0.0 by flashing rom in local updater, then without reboot, flashed twrp installer and magisk in inactiv slot, in magisk iteslf (followed your guide and the one Kollachi had put up).
Magisk version is 20.1 and TWRP version is 3.3.1-70.
Everything was working fine for about two months before one reboot started causing the bootloop. (I made no other changes to magisk before this reboot)
Thanks!
ImperatorShade said:
Thank you for the response strongst!
I am using the 10.0.1 GM57AA build right now. Updated directly from 10.0.0 by flashing rom in local updater, then without reboot, flashed twrp installer and magisk in inactiv slot, in magisk iteslf (followed your guide and the one Kollachi had put up).
Magisk version is 20.1 and TWRP version is 3.3.1-70.
Everything was working fine for about two months before one reboot started causing the bootloop. (I made no other changes to magisk before this reboot)
Thanks!
Click to expand...
Click to collapse
Maybe you did have any magisk modules left?
Have you tried an older magisk version?
strongst said:
Maybe you did have any magisk modules left?
Have you tried an older magisk version?
Click to expand...
Click to collapse
Thanks for the fast response! Yes, I tried Magisk 19.3 ver but got the same issue.
ImperatorShade said:
Thanks for the fast response! Yes, I tried Magisk 19.3 ver but got the same issue.
Click to expand...
Click to collapse
And are there any magisk modules or mods left? It can be the reason for this.
Are there any errors within the log while flashing?
You have the twrp guacamole unified from mauronofrio 3.3.1-70, right? You can try 3.3.1-73 if you want.
There were no errors when flashing. But I'm not sure whether I had disabled Magisk Modules before flashing OxygenOS 10. Anyway, what would be the best way to untwrp and clean flash?
Dears,
I have a OnePlus 6 unlocked and rooted with magisk and TRWP.
Currently I'm running stock firmware: oxygenos 10.3.
I got a message from system to update to 10.3.1.
Last time (when I have to update to 10.3) I tried to update in every way but without success and at the end I had to format everything and I lost my data.
So here is my question: which is the correct procedure to update software?
Thanks!
Look in TWRP and Root for OnePlus 6 on Oxygen OS 10 Stable/Beta thread
So you need to download latest Oxygen zip which is 042 buil if I'm not wrong...put it on your phone if you already didn't done that...then reboot to TWRP...and here starts the procedure....I HIGHLY RECCOMEND TO DO A WIPE WITHOUT FORMATTING INTERNAL STORAGE ONLY DATA...FOR AVOIDING ISSUES...but you can go without it...so here we start
Boot into twrp
Flash oxygen os zip(latest)
Flash twrp
Reboot to twrp(if it says no os installed just ignore it and swipe reboot anyway)
Flash magisk
and your done...thats it...nothing could go wrong.... I'm always doing it this way....
ilpratti said:
Dears,
I have a OnePlus 6 unlocked and rooted with magisk and TRWP.
Currently I'm running stock firmware: oxygenos 10.3.
I got a message from system to update to 10.3.1.
Last time (when I have to update to 10.3) I tried to update in every way but without success and at the end I had to format everything and I lost my data.
So here is my question: which is the correct procedure to update software?
Thanks!
Click to expand...
Click to collapse
For me, the phone downloaded the whole package instead of just the little OTA. I let it install it, bit did not let it restart it. Then I went to magisk modules and installed "twrp-keep". Then in magisk manager I had it install magisk on the other slot. Then I restarted the phone. Everything worked great.
tabletalker7 said:
For me, the phone downloaded the whole package instead of just the little OTA. I let it install it, bit did not let it restart it. Then I went to magisk modules and installed "twrp-keep". Then in magisk manager I had it install magisk on the other slot. Then I restarted the phone. Everything worked great.
Click to expand...
Click to collapse
Try this method... im also done my update like this!
my way of doing it
Here's what i did and it didn't took me long at all i'm a newbie
I unroot my phone via magisk
install os 10.3.1 then flash twrp and root my phone again.
Dears,
Thanks for the replay.
I forgot that I was without TWRP.
What I did, and it worked, is:
- uninstall magisk manager by magisk
- install full update
- reboot
- flash by fastboot boot.img patched by magisk.
Thanks again
Hey,
Yesterday i received the official global version of Ogygen OS 11 (OnePlus7Oxygen_14.E.35_OTA_0350_all_2103221233) for my Oneplus 7 which made me happy and i installed it on my current TWRP and root Ogygen OS 10. Afterwards my root and TWRP was gone. I read many threads now about that TWRP is not available currently for Android 11. So i was stuck with extracting the boot.img from the stock zip file and patching it with the latest canary Magisk (66e30a77 (22006)). The patch is successful.
After i flashed the boot.img to boot_a and boot_b via fastboot the phone restarted but there was still no root. (Magisk still showed that its not installed and superuser rights for Magisk also weren't granted->notification during start).
After trying and validating that i used the latest version of everything and also did a factory reset and tried the same handling again, i tried to use the latest beta Oxygen OS11 stock image for flashing the boot.img (same handling as before). After flashing i gained superuser rights and magisk was installed but no bluetooth and WIFI was working so there was an issue (is clear because it was not the same stock zip).
So does anyone of you might have already an solution for this?
Rgds,
Matthias
matthi383 said:
Hey,
Yesterday i received the official global version of Ogygen OS 11 (OnePlus7Oxygen_14.E.35_OTA_0350_all_2103221233) for my Oneplus 7 which made me happy and i installed it on my current TWRP and root Ogygen OS 10. Afterwards my root and TWRP was gone. I read many threads now about that TWRP is not available currently for Android 11. So i was stuck with extracting the boot.img from the stock zip file and patching it with the latest canary Magisk (66e30a77 (22006)). The patch is successful.
After i flashed the boot.img to boot_a and boot_b via fastboot the phone restarted but there was still no root. (Magisk still showed that its not installed and superuser rights for Magisk also weren't granted->notification during start).
After trying and validating that i used the latest version of everything and also did a factory reset and tried the same handling again, i tried to use the latest beta Oxygen OS11 stock image for flashing the boot.img (same handling as before). After flashing i gained superuser rights and magisk was installed but no bluetooth and WIFI was working so there was an issue (is clear because it was not the same stock zip).
So does anyone of you might have already an solution for this?
Rgds,
Matthias
Click to expand...
Click to collapse
Hello,
Did you see this thread right below yours?
Android 11 OB4
Just installed OB4, anybody got a boot.img file or magisk patched boot image file? Also any news on TWRP for Android 11? Thanks in anticipation OK I was just lazy hoping somebody Elese did the work. Ended up using my OB2 patched boot image file...
forum.xda-developers.com
Magisk canary can also cause a lot of issues. I'm using 22.0.
Hey thank you! I already saw this and tried it out before to get TWRP working as in the Oxygen OS 11 Beta but this TWRP version does not work with the official OOS11 for the Oneplus 7. It's strange that on Open Beta it works and now its not working.
Watching this thread because I'm stuck too. I either need locked bootloader or unlocked with Magisk
Does anyone already has a solution to this one?
I got the OTA today for 11.0.0.2, rooted fine with Magisk 22.1. Check out my guide:
https://forum.xda-developers.com/t/...m1900-android-11-oos-stable-11-0-0-2.4253743/
WareDat said:
I got the OTA today for 11.0.0.2, rooted fine with Magisk 22.1. Check out my guide:
https://forum.xda-developers.com/t/...m1900-android-11-oos-stable-11-0-0-2.4253743/
Click to expand...
Click to collapse
I wish someone would upload the fastboot ROM
Thank you man it worked ! i hope others are seeing also your intructions and files so they can use them and have root back again