Hello, and I apologize if this is in the wrong place, and if there is already a thread to solve my issue please direct me there (I could not find one for my specific issue). I cannot install Magisk without my OP6 becoming stuck in Fastboot mode (I can still access TWRP recovery); Should I get this Blu_Spark? People tell me it's better, especially on OnePlus 6.
So I was installing modules for Magisk, but Magisk itself is fairly new to me; I am used to SuperSU which is now outdated. I enjoy Magisk and its interface and the lot. Earlier today I attempted to install Viper4Android via Magisk and was told I needed BusyBox. I installed it from the app store, but then realized Magisk had a module for it. So I uninstalled BusyBox and installed the module. Upon reboot I found myself stuck in Fastboot. Luckily I could still access TWRP and managed to fix the Bootloop without losing data. I've since made a full backup of my things.
However, now I am facing a new issue altogether. After getting back into the phone Magisk told me that it was not installed. So I uninstalled Magisk via their flashable uninstaller and attempted to reinstall. Now I think Magisk itself is causing these issues. I don't want to wipe and do a fresh reset because the phone has a large capacity and I have a lot on it. Backup would be 180GB+ and restoration would take forever. Unless I'm missing something...
Basically I had to uninstall Magisk completely for it to go back to my phone. I just want my root. Also, is LineageOS worth it, I hear OxygenOS is superior but I enjoy the features Lineage has. Thank you.
Why is Magisk causing these issues? The only thing I can think of was my mess-up with BusyBox. If anyone could help me find an alternative to a factory reset to fix Magisk so it doesn't cause bootloop or fastboot I'd appreciate it.
Thank you for your time
FURTHER INFORMATION UPON INQUIRY
If its better to provide solution if you include exact version name of your OS or magisk or twrp or other details instead of mentioning just names!
However below Solution might work if you are in Android 10. Read and follow the steps carefully
1. So if you access TWRP, flash Magisk Uninstaller so it will remove magisk and its existing modules. Dont teboot
2. Then flash the stock boot image or Full Rom ZIP in boot partition(current boot partition). Don't reboot since now you will lose TWRP as it will replace stock recovery. Remember dont reboot
3. Flash TWRP installer zip(not twrp image) and then now reboot to recovery. So now you have a fully working TWRP in OOS 10 with Magisk stuff removed. . Don't reboot .
4. Now Flash Magisk v20.1. Reboot to system.
Edit: you can get Twrp img and zip file from here https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
tvteja said:
If its better to provide solution if you include exact version name of your OS or magisk or twrp or other details instead of mentioning just names!
However below Solution might work if you are in Android 10. Read and follow the steps carefully
1. So if you access TWRP, flash Magisk Uninstaller so it will remove magisk and its existing modules. Dont teboot
2. Then flash the stock boot image or Full Rom ZIP in boot partition(current boot partition). Don't reboot since now you will lose TWRP as it will replace stock recovery. Remember dont reboot
3. Flash TWRP installer zip(not twrp image) and then now reboot to recovery. So now you have a fully working TWRP in OOS 10 with Magisk stuff removed. . Don't reboot .
4. Now Flash Magisk v20.1. Reboot to system.
Edit: you can get Twrp img and zip file from here https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Click to expand...
Click to collapse
Thank you so much for your suggestion, and reply. Magisk and TWRP were up to date (the latest releases); Magisk v20.1, and TWRP 3.3.1.2 ("Enchilada"). My device is a OnePlus 6 running Android 9, last updated August 1st of this year, "ONEPLUS A6003_22_190911"
I will try your suggestion and respond as soon as possible. If there is anything else you need to know, ask. I am new to the concept of forums so I've been kinda flopping around like a fish out of water. :laugh:
Marmalade_Shaws said:
Hello, and I apologize if this is in the wrong place, and if there is already a thread to solve my issue please direct me there (I could not find one for my specific issue). I cannot install Magisk without my OP6 becoming stuck in Fastboot mode (I can still access TWRP recovery); Should I get this Blu_Spark? People tell me it's better, especially on OnePlus 6.
So I was installing modules for Magisk, but Magisk itself is fairly new to me; I am used to SuperSU which is now outdated. I enjoy Magisk and its interface and the lot. Earlier today I attempted to install Viper4Android via Magisk and was told I needed BusyBox. I installed it from the app store, but then realized Magisk had a module for it. So I uninstalled BusyBox and installed the module. Upon reboot I found myself stuck in Fastboot. Luckily I could still access TWRP and managed to fix the Bootloop without losing data. I've since made a full backup of my things.
However, now I am facing a new issue altogether. After getting back into the phone Magisk told me that it was not installed. So I uninstalled Magisk via their flashable uninstaller and attempted to reinstall. Now I think Magisk itself is causing these issues. I don't want to wipe and do a fresh reset because the phone has a large capacity and I have a lot on it. Backup would be 180GB+ and restoration would take forever. Unless I'm missing something...
Basically I had to uninstall Magisk completely for it to go back to my phone. I just want my root. Also, is LineageOS worth it, I hear OxygenOS is superior but I enjoy the features Lineage has. Thank you.
Why is Magisk causing these issues? The only thing I can think of was my mess-up with BusyBox. If anyone could help me find an alternative to a factory reset to fix Magisk so it doesn't cause bootloop or fastboot I'd appreciate it.
Thank you for your time
FURTHER INFORMATION UPON INQUIRY
Click to expand...
Click to collapse
tvteja said:
If its better to provide solution if you include exact version name of your OS or magisk or twrp or other details instead of mentioning just names!
However below Solution might work if you are in Android 10. Read and follow the steps carefully
1. So if you access TWRP, flash Magisk Uninstaller so it will remove magisk and its existing modules. Dont teboot
2. Then flash the stock boot image or Full Rom ZIP in boot partition(current boot partition). Don't reboot since now you will lose TWRP as it will replace stock recovery. Remember dont reboot
3. Flash TWRP installer zip(not twrp image) and then now reboot to recovery. So now you have a fully working TWRP in OOS 10 with Magisk stuff removed. . Don't reboot .
4. Now Flash Magisk v20.1. Reboot to system.
Edit: you can get Twrp img and zip file from here https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Click to expand...
Click to collapse
Hello, just wanted to update you. I am happy to report your suggestion worked. Sadly I still lost my data, but that's alright; all the important bits were already backed up. Just lost the home screen layout and some application settings. All the same, I am now successfully running my rooted device and couldn't be happier! Thanks! :laugh::good:
Marmalade_Shaws said:
Hello, and I apologize if this is in the wrong place, and if there is already a thread to solve my issue please direct me there (I could not find one for my specific issue). I cannot install Magisk without my OP6 becoming stuck in Fastboot mode (I can still access TWRP recovery); Should I get this Blu_Spark? People tell me it's better, especially on OnePlus 6.
So I was installing modules for Magisk, but Magisk itself is fairly new to me; I am used to SuperSU which is now outdated. I enjoy Magisk and its interface and the lot. Earlier today I attempted to install Viper4Android via Magisk and was told I needed BusyBox. I installed it from the app store, but then realized Magisk had a module for it. So I uninstalled BusyBox and installed the module. Upon reboot I found myself stuck in Fastboot. Luckily I could still access TWRP and managed to fix the Bootloop without losing data. I've since made a full backup of my things.
However, now I am facing a new issue altogether. After getting back into the phone Magisk told me that it was not installed. So I uninstalled Magisk via their flashable uninstaller and attempted to reinstall. Now I think Magisk itself is causing these issues. I don't want to wipe and do a fresh reset because the phone has a large capacity and I have a lot on it. Backup would be 180GB+ and restoration would take forever. Unless I'm missing something...
Basically I had to uninstall Magisk completely for it to go back to my phone. I just want my root. Also, is LineageOS worth it, I hear OxygenOS is superior but I enjoy the features Lineage has. Thank you.
Why is Magisk causing these issues? The only thing I can think of was my mess-up with BusyBox. If anyone could help me find an alternative to a factory reset to fix Magisk so it doesn't cause bootloop or fastboot I'd appreciate it.
Thank you for your time
FURTHER INFORMATION UPON INQUIRY
Click to expand...
Click to collapse
Hey, I'm in a similar situation you were in and I'm stuck in a bootloop after I flashed/installed busybox from magisk repo, I wanted viper 4android as well and while installing viper it said that I'd need busybox. Soon after I install busy box from magisk I'm in this bootloop, i have access to twrp luckily and i tried deleting this busybox and viper 4android module from twrp file manager but still I'm in a boot loop, can you guide me on how you managed to get out of this bootloop?? Thanks
Related
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!
https://developers.google.com/android/images
Still 9.0, but it's starting a new quarterly build so might have some updates. No change log yet
There is this
"All Pixel devices running Android 9 will receive an Android 9 update as part of the May OTA. This quarterly release contains many functional updates and improvements to various parts of the Android platform and supported Pixel devices."
i did clean install of the recovery image this morning. all seems fine. nothing visually different
Has anyone already rooted? With me, the carrier service crashes continuously after I installed Magisk 19.1.
Atomregen said:
Has anyone already rooted? With me, the carrier service crashes continuously after I installed Magisk 19.1.
Click to expand...
Click to collapse
I can't speak to the 3XL since I am on dotOS, but I had no issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
sliding_billy said:
I can't speak to the 3XL since I am on dotOS, but I had no issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
Click to expand...
Click to collapse
Thanks for replay,
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck.
After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
hopefully it is written understandably.
208.9mb too! Quite large for just a small incremental update too!
considering locking my BL and clean wiping...
google pay no longer works and its fustrating.
virtyx said:
considering locking my BL and clean wiping...
google pay no longer works and its fustrating.
Click to expand...
Click to collapse
Try this first.
Factory reset in TWRP (after installing factory update and rebooting).
You'll have to set up as new but won't lose internal data.
Atomregen said:
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck. After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
Click to expand...
Click to collapse
I had some issues getting the May update, TWRP 3.3.0-1, Kirisakura 2.3.0, and Magisk 19.1 to play nicely together. Lots of "rescue party" reboots at the "G" logo of booting after trying to install everything together. I basically did what you did to solve the issue too. Installed the May update (removing -w) then installed TWRP 3.3.0-1, Kirisakura 2.3.0 and Magisk 18.1 and restarted back to system to make sure it all worked (which it did). After that I upgraded to Magisk 19.1 via the Magisk app and everything seems to be fine now. My temp solution until this was just use TWRP 3.2.3-3 which I had been using up until this point. That worked too and allowed everything to play nice from the initial installation.
Aren't you supposed to boot system before flashing magisk?
Atomregen said:
Thanks for replay,
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck.
After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
hopefully it is written understandably.
Click to expand...
Click to collapse
wangdaning said:
Aren't you supposed to boot system before flashing magisk?
Click to expand...
Click to collapse
I was wondering the same thing about whether you finished booting before installing Magisk. I completely boot after every step (Image, TWRP, Magisk, Kernel - ElementalX installed with EX Kernel Manager) and don't stack installs in TWRP. Been doing that for years, and it has saved me some time long term despite the couple of extra minutes during installs. My other thought was possibly a bad 19.1 file.
---------- Post added at 02:00 AM ---------- Previous post was at 01:58 AM ----------
sstanton86 said:
208.9mb too! Quite large for just a small incremental update too!
Click to expand...
Click to collapse
Looking at new apps to backup in TB, there were about 7 new system apps that I saw and one that had been removed.
since there is an auto reboot after flashing flash-all.bat, I did a reboot after flashing the factory image.
Sent from my Pixel 3 XL using XDA Labs
Atomregen said:
since there is an auto reboot after flashing flash-all.bat, I did a reboot after flashing the factory image.
Click to expand...
Click to collapse
I always reboot to the system after the factory image/monthly update is installed and allow it to finish setup. Then I fastboot into TWRP to install TWRP recovery, my kernel, and Magisk via the "add more zips" option in TWRP. I've been doing this ever since I got the device and never ran into issues until this May update. Doing this with the May update, TWRP 3.3.0-1, Kirisakura 2.3.0 and Magisk 19.1 caused reboots like I described. However, reverting to TWRP 3.2.3-3 instead (my initial solution/fix) or Magisk 18.1 then upgrading Magisk to 19.1 (like @sliding_billy suggested) worked fine. This to me implies a compatibility issue of some type and not an issue with the method of installation.
Tulsadiver said:
Try this first.
Factory reset in TWRP (after installing factory update and rebooting).
You'll have to set up as new but won't lose internal data.
Click to expand...
Click to collapse
magisk and gpay dont work after googleplay services version 16.0.91
if i downgrade to 16091 it works - but i cant let it upgrade otherwise it breaks gpay
im not sure if its on all phones or just pixels with the titan chip that GPS is now interacting with, but if you try to upgrade to 17.x google play service with magisk - it doesnt work and detects root.
just FYI for people with issues with updates let it boot into OS before flashing TWRP / KERNEL / MAGISK otherwise you will get a bootloop.
and personally i flash TWRP/KERNEL/Magisk in that order and ive never gotten a bootloop (but have flashing kernel last a couple times)
my rationale behind flashing magisk last is because if you were on stock kernel, you would just flash magisk, you wouldnt flash magisk then stock kernel over it would you?
virtyx said:
magisk and gpay dont work after googleplay services version 16.0.91
if i downgrade to 16091 it works - but i cant let it upgrade otherwise it breaks gpay
im not sure if its on all phones or just pixels with the titan chip that GPS is now interacting with, but if you try to upgrade to 17.x google play service with magisk - it doesnt work and detects root.
just FYI for people with issues with updates let it boot into OS before flashing TWRP / KERNEL / MAGISK otherwise you will get a bootloop.
and personally i flash TWRP/KERNEL/Magisk in that order and ive never gotten a bootloop (but have flashing kernel last a couple times)
my rationale behind flashing magisk last is because if you were on stock kernel, you would just flash magisk, you wouldnt flash magisk then stock kernel over it would you?
Click to expand...
Click to collapse
This is the way Freak recommends flashing his kernel. Did Freak change something?
Freak07 said:
Flash factory image with -w removed (if you want to keep data intact)
Do a reboot
Then you can boot to twrp and flash twrp, magisk and kernel (in that order)
Afterwards all should be fine.
I personally do a reboot after flashing twrp. Then back to twrp and magisk plus kernel...
Click to expand...
Click to collapse
Homeboy76 said:
This is the way Freak recommends flashing his kernel. Did Freak change something?
Click to expand...
Click to collapse
I always flash kernel before magisk. I've never had issues.
Homeboy76 said:
This is the way Freak recommends flashing his kernel. Did Freak change something?
Click to expand...
Click to collapse
not saying either way is right or wrong
but it makes sense to flash magisk LAST.
Anyone try to sideload the OTA? I believe the file is too big to sideload?
lucky_strike33 said:
Anyone try to sideload the OTA? I believe the file is too big to sideload?
Click to expand...
Click to collapse
I sideloaded. Worked fine.
Anyone else unable to root the May update? I installed the update, TWRP, and the kernel I use and everything was fine. After installing Magisk 19.1 the phone boots straight to a "System UI has stopped" dialog box. Substratum overlays were uninstalled before updating and uninstalling Magisk fixes the issue, leading me to believe that it is the cause.
I tried installing Magisk 18.1 instead to see if it would work, but oddly it doesn't seem to install at all. When I boot the phone Magisk Manager was installed, but it claims that Magisk is not installed and no apps can get root access.
As the title says I updated to 9.5.9 and I installed magisk to ota slot and then I got a bootloop.... I fixed it by using twrp option to fix bootloop but that removed root, everything I do now sends it into a bootloop, please tell me there is a way to reroot this without wiping my data
https://forum.xda-developers.com/on...-to-uninstall-magisk-module-t3940369#poststop
Just had the same issue an hour ago. Do this then re-root your phone again. Easy. Then re-install magisk modules.
spart0n said:
As the title says I updated to 9.5.9 and I installed magisk to ota slot and then I got a bootloop.... I fixed it by using twrp option to fix bootloop but that removed root, everything I do now sends it into a bootloop, please tell me there is a way to reroot this without wiping my data
Click to expand...
Click to collapse
Had the same issue.
Same here. I just reflashed TWRP (flash boot command), flashed the TWRP installer zip, rebooted recovery and then flashed Magisk. That solved it.
By the way, theres a new TWRP out for the 7 Pro.
I got the same problem but my internal storage is encrypted (it shows 0kb). TWRP is not asking for PIN to unencrypt the partition. What can I do now?
Do we have a custom boot image for 9.5.9? I'm looking to root and want to find the best method which will continue to allow future updates (even if I need to flash manually)
dude9946 said:
Do we have a custom boot image for 9.5.9? I'm looking to root and want to find the best method which will continue to allow future updates (even if I need to flash manually)
Click to expand...
Click to collapse
Your best bet is to use the oxygen updater app, download 9.5.9 and then copy it to a PC then use boot.img extract thingy and then use magisk to patch it and then use fastboot to to root it
I have Android 10 on my OG Pixel. I have secured it with pin and fingerprint. When i booted twrp-3.3.1-0-sailfish.img it sucesfully decrypted data with PIN then i flashed latest available zip which is twrp-pixel-installer-sailfish-3.3.0-0.zip. Rebooted and phone booted normaly. Then i downloaded latest magisk zip and apk. I tried to flash magisk but pin unlock does not work in twrp 3.3.0-0 which i flashed. Then i tried to boot from twrp-3.3.1-0-sailfish.img and this version decrypts data fine. Maybe because it's newer version and there is some fix in there. Can i flash 3.3.1-0 to my device permanently?
Why there is no 3.3.1-0 flashable zip for OG Pixel? https://eu.dl.twrp.me/sailfish/
Pixel XL does have 3.3.1-0 flashable zip too which is dated the same as live boot img 3.3.1-0 image https://eu.dl.twrp.me/marlin/
Can i flash magisk from booted twrp-3.3.1-0-sailfish.img and not with twrp that i flashed? Will it work?
matusala said:
I have Android 10 on my OG Pixel. I have secured it with pin and fingerprint. When i booted twrp-3.3.1-0-sailfish.img it sucesfully decrypted data with PIN then i flashed latest available zip which is twrp-pixel-installer-sailfish-3.3.0-0.zip. Rebooted and phone booted normaly. Then i downloaded latest magisk zip and apk. I tried to flash magisk but pin unlock does not work in twrp 3.3.0-0 which i flashed. Then i tried to boot from twrp-3.3.1-0-sailfish.img and this version decrypts data fine. Maybe because it's newer version and there is some fix in there. Can i flash 3.3.1-0 to my device permanently?
Why there is no 3.3.1-0 flashable zip for OG Pixel? https://eu.dl.twrp.me/sailfish/
Pixel XL does have 3.3.1-0 flashable zip too which is dated the same as live boot img 3.3.1-0 image https://eu.dl.twrp.me/marlin/
Can i flash magisk from booted twrp-3.3.1-0-sailfish.img and not with twrp that i flashed? Will it work?
Click to expand...
Click to collapse
Twrp does not work on 10. You can root fairly easily by clean flashing 10, installing the latest magisk Canary build and then patching the boot.img through magisk. There is currently no working twrp and although you can root you cannot mount your system. We await further magisk updates to fix that.
Go to the main magisk support thread on XDA. It's all there.
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page3558
I've done it anyway and all working fine (apart from system mount). Magisk hide works, my adblockr works. It's all good.
Follow this guide for root. It works the same for the original Pixel
https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
Horgar said:
Twrp does not work on 10. You can root fairly easily by clean flashing 10, installing the latest magisk Canary build and then patching the boot.img through magisk. There is currently no working twrp and although you can root you cannot mount your system. We await further magisk updates to fix that.
Go to the main magisk support thread on XDA. It's all there.
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page3558
I've done it anyway and all working fine (apart from system mount). Magisk hide works, my adblockr works. It's all good.
Follow this guide for root. It works the same for the original Pixel
https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
Click to expand...
Click to collapse
I removed fingerprint and pin code temporarily and flashed magisk.zip and installed magisk apk. All is working great. Then i set up pin and fingerprint and once there was some problem pin did not unlock phone fingerprint did. After reboot it also fixed.
Thing is if i boot 3.3.1-0 with fastboot boot it works, it decrypts data with pin. But 3.3.0-0 says pin wrong. I tried to install twrp-3.3.1-0.img from TWRP 3.3.0-0 with new menu to flash ramdisk but it says something that not enough memory available. How can i flash new 3.3.1-0 TWRP there is no zip. What version of TWRP do you have?
matusala said:
I removed fingerprint and pin code temporarily and flashed magisk.zip and installed magisk apk. All is working great. Then i set up pin and fingerprint and once there was some problem pin did not unlock phone fingerprint did. After reboot it also fixed.
Thing is if i boot 3.3.1-0 with fastboot boot it works, it decrypts data with pin. But 3.3.0-0 says pin wrong. I tried to install twrp-3.3.1-0.img from TWRP 3.3.0-0 with new menu to flash ramdisk but it says something that not enough memory available. How can i flash new 3.3.1-0 TWRP there is no zip. What version of TWRP do you have?
Click to expand...
Click to collapse
The issue you describe is nothing to do with being on Android 10. That issue of decryption with twrp has been around for a while. Just get rid of pin etc, then you will get into twrp. But. Twrp does not work with 10. There is no point attempting to flash twrp for the time being. It does not work.
If you want a working root, you need to do the old way by patching your boot.img. That seems to be the only working root method so far on 10
Horgar said:
The issue you describe is nothing to do with being on Android 10. That issue of decryption with twrp has been around for a while. Just get rid of pin etc, then you will get into twrp. But. Twrp does not work with 10. There is no point attempting to flash twrp for the time being. It does not work.
If you want a working root, you need to do the old way by patching your boot.img. That seems to be the only working root method so far on 10
Click to expand...
Click to collapse
Why do you keep saying it does not work? I just got rid of pin + fingerprint then went into TWRP which i flashed before from live TWRP. Flashed magisk.zip it worked perfectly and then rebooted and installed magisk manager. TWRP works great with 10 if i do not have pin + fingerprint and magisk also works great.
I used twrp to flash Magisk on 10.0. I didn't flash twrp, just booted it. It flashed the normal magisk fine and I have root. What is more strange, my Pixel accepted and installed 10.0 via the OTA. I have never had a rooted phone accept an OTA before.
jackdubl said:
I used twrp to flash Magisk on 10.0. I didn't flash twrp, just booted it. It flashed the normal magisk fine and I have root. What is more strange, my Pixel accepted and installed 10.0 via the OTA. I have never had a rooted phone accept an OTA before.
Click to expand...
Click to collapse
Magisk is systemless root maybe that's why it did that.
matusala said:
Why do you keep saying it does not work? I just got rid of pin + fingerprint then went into TWRP which i flashed before from live TWRP. Flashed magisk.zip it worked perfectly and then rebooted and installed magisk manager. TWRP works great with 10 if i do not have pin + fingerprint and magisk also works great.
Click to expand...
Click to collapse
If Twrp sticks and works on 10 then that's good. But all the reports on XDA are saying Twrp will not stick and/or does not work on 10. You're the only person I've heard that has got a working Twrp on 10
Horgar said:
If Twrp sticks and works on 10 then that's good. But all the reports on XDA are saying Twrp will not stick and/or does not work on 10. You're the only person I've heard that has got a working Twrp on 10
Click to expand...
Click to collapse
Have you tried just booting twrp instead of flashing it?
jackdubl said:
Have you tried just booting twrp instead of flashing it?
Click to expand...
Click to collapse
No. Not tried. But if it worked for you that's good to know. I know for others it didn't work. Patching the boot.img only takes 10 minutes anyway.
Are you able to mount your system with magisk rooted 10?
Horgar said:
No. Not tried. But if it worked for you that's good to know. I know for others it didn't work. Patching the boot.img only takes 10 minutes anyway.
Are you able to mount your system with magisk rooted 10?
Click to expand...
Click to collapse
I seem to remember getting some strange messages while flashing Magisk, like it couldn't mount system or something. It was in red. It seemed bad but it also came after successfully flashing Magisk, so it said. Everything was working fine after I rebooted. All root apps working as normal.
Howdy y'all, this is all something I did recently after resurrecting my Google pixel. I also got Android 10 and twrp working with magisk. All was good until I tried mounting system so I can edit build.prop. I spend a ton of time trying to research why I could not mount system. Came up empty until I found this thread with someone mentioning you cannot mount system. Why is this? Is there no way that I can edit build.prop in this configuration?
jeffritz1 said:
Howdy y'all, this is all something I did recently after resurrecting my Google pixel. I also got Android 10 and twrp working with magisk. All was good until I tried mounting system so I can edit build.prop. I spend a ton of time trying to research why I could not mount system. Came up empty until I found this thread with someone mentioning you cannot mount system. Why is this? Is there no way that I can edit build.prop in this configuration?
Click to expand...
Click to collapse
If your running Magisk you could try the Magiskhide props config module, Its in the downloads section of magisk manager. Should allow you to set custom props, there is a dedicated thread for it so may be worth a look there also.
junglism93 said:
If your running Magisk you could try the Magiskhide props config module, Its in the downloads section of magisk manager. Should allow you to set custom props, there is a dedicated thread for it so may be worth a look there also.
Click to expand...
Click to collapse
Yeah, after trying everything under the sun I started going down this route but as I was going through the Magiskhide props config module menu I see "Edit Magisk Props" and "Edit custom props" but It made me believe that it creates / edits new custom props and could not see a way of editing the build.prop in /system. May need to dig further into it since I never used this module before. Thanks for mentioning the Magiskhide props config module support thread.
is rooted Magisk on Android 10 or 11 with Pixel 1 possible?
jeffritz1 said:
Yeah, after trying everything under the sun I started going down this route but as I was going through the Magiskhide props config module menu I see "Edit Magisk Props" and "Edit custom props" but It made me believe that it creates / edits new custom props and could not see a way of editing the build.prop in /system. May need to dig further into it since I never used this module before. Thanks for mentioning the Magiskhide props config module support thread.
Click to expand...
Click to collapse
Is there a link. I currently have a pixel on 8.1 and I am trying to get a rooted pixel up and running so I can tether. This will be my daily phone. I am looking for the best solution for a safe and robust system that allows tethering. thanks for any leads.
Sam
YogaSlackers said:
Is there a link. I currently have a pixel on 8.1 and I am trying to get a rooted pixel up and running so I can tether. This will be my daily phone. I am looking for the best solution for a safe and robust system that allows tethering. thanks for any leads.
Sam
Click to expand...
Click to collapse
Hey, almost a week late but hope it's still helpful. Yes I recommend the official 10 firmware with Magisk, flashed through a temporary TWRP.
I've been running this setup for months, I can use all my root apps, even Google Pay and Netflix no problem.
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