Related
Why is this phone some wonky with installing **** through recovery?
Installed magisk and don't pass the safetynet. F droid won't give me an option to install adaway.
How the heck do you root this thing.
I'm on crdroid 8.1
Are you using the latest version of Magisk? How did you install it? Do you have the Magisk Manager app installed?
You can install AdAway yourself. Get it here.
I'm on stock Pie and rooted no problem flashing magisk through twrp.
Maybe if you have a pixel it's easier to just stay up to date instead of playing the nerd who always knows better and then complaining that **** doesn't work.
Hello,
I have a global Mix 3 with globe Rom (10.2.1) installed, which is basically a debloated version of the xiaomi.eu rom.
My phone is rooted with Magisk 17.3
While trying to install ViPER4Arise and YouTube vanced I noticed that I have root access but changes made to system files do not stick after reboot. While installing something ist says it worked, but after a reboot everything is back to stock. Same with busy box.
Any ideas on this?
I tried different versions of magisk and some fixes for this problem i found on xda for other devices, but nothing worked.
JetzNicht said:
Hello,
I have a global Mix 3 with globe Rom (10.2.1) installed, which is basically a debloated version of the xiaomi.eu rom.
My phone is rooted with Magisk 17.3
While trying to install ViPER4Arise and YouTube vanced I noticed that I have root access but changes made to system files do not stick after reboot. While installing something ist says it worked, but after a reboot everything is back to stock. Same with busy box.
Any ideas on this?
I tried different versions of magisk and some fixes for this problem i found on xda for other devices, but nothing worked.
Click to expand...
Click to collapse
Use one of the custom kernels
Thanks, this solved my problem
This is for if you have Magisk 18.1 installed with manager version 7.1.1. Upgrading to manager 7.1.2 and then directly installing 19.1 caused my I3223 to go into a boot loop.
Image patching seems to have changed as well. With manager 7.1.1 we were able to directly patch the boot_X_FLASH_ALL-*.sin file. I had to extract boot.000 from the sin file before the new manager would patch it. Even so, the result is still a boot loop.
Reflashing older patched boot images did not restore root. In short, hold off on upgrading Magisk. If you have a solution please share. Thanks.
I was able to flash the older (v18.1) magisk patched boot image using fastboot. I will attach the image here if you need too. I had to split the RAR file into 3 parts due to limitation of XDA of RAR files to be 8MB.
Root is working fine, I was able to grant access to Titanium Backup. But seriously that was messed up. If that happened to my Shield TV and I lost all of my games I will be furious. Luckily, I tried that on the Shield TV before knowing it will mess up my Xperia 10 plus phone. What is more messed up is there is no way from Magisk Manager to keep using older APK or download older version of Magisk, I tried Custom URL in the settings to check the update from, but all I got was a spinning wheel while checking for updates.
Currently running Magisk Manager 7.1.2 and v18.1 , just ignoring the ZIP update.
Rule of thumb, if it aint broken, don't fix / update.
Thank you Rebel_X. I will try again tonight. I was hoping to retain userdata but that's probably what's giving me problems with the revert.
Has anyone tried 19.1 patched boot image on a fully reset phone? Do we know if that works?
Rebel_X said:
I was able to flash the older (v18.1) magisk patched boot image using fastboot. I will attach the image here if you need too. I had to split the RAR file into 3 parts due to limitation of XDA of RAR files to be 8MB.
Root is working fine, I was able to grant access to Titanium Backup. But seriously that was messed up. If that happened to my Shield TV and I lost all of my games I will be furious. Luckily, I tried that on the Shield TV before knowing it will mess up my Xperia 10 plus phone. What is more messed up is there is no way from Magisk Manager to keep using older APK or download older version of Magisk, I tried Custom URL in the settings to check the update from, but all I got was a spinning wheel while checking for updates.
Currently running Magisk Manager 7.1.2 and v18.1 , just ignoring the ZIP update.
Rule of thumb, if it aint broken, don't fix / update.
Click to expand...
Click to collapse
Hay, what model is your Xperia 10 plus?
My phone is I4293, i used your boot.img, when reboot, nothing is changed, just not rooted.
yishisanren said:
Hay, what model is your Xperia 10 plus?
My phone is I4293, i used your boot.img, when reboot, nothing is changed, just not rooted.
Click to expand...
Click to collapse
Mine is I3223. I don't know if it is compatible with your model, but if it flashed fine and the phone booted, try to install magisk manager apk v7.1.1 and see if you are rooted.
Rebel_X said:
Mine is I3223. I don't know if it is compatible with your model, but if it flashed fine and the phone booted, try to install magisk manager apk v7.1.1 and see if you are rooted.
Click to expand...
Click to collapse
It flashed fine, also my phone can be booted, but not rooted.
:crying::crying::crying:
Have you guys tried to summit a bug report on magisk's github issue page?
https://github.com/topjohnwu/Magisk/issues/1537
The bugreport about magisk bootloops on xperia devices
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.
Ive been using magisk for quite some time, rebooted my phone once to check that it worked. Went on for a while without rebooting, decide to reboot it after installing all my apps (no modules), have a couple root apps like adaway and J oneplus tools. Anybody else have this issue, any idea on how to fix it? Im running the latest OOS and the latest Magisk with the most recent Mauronofrio TWRP