Hi,
I need some help. So basically what happened was I was rooted using the latest Supersu but was running 7.1.2 April patch on my Pixel. I stopped there since I read the May patch and supersu had issues. Now with the release of magisk for pixel I decided I wanted to update and change from supersu to magisk and here is what I did:
Went into TWRP and flashed unSU and then tried to flash magisk 14.2 but kept getting error 1 when trying to flash magisk. SuperSU was gone off my phone. I read that the issue with flashing magisk is I needed to flash the stock boot.img over the supersu patched one before I could flash magisk.
I wasn't sure how to get the stock boot.img so the next idea I had was to re-flash supersu, so I did that but the application didn't show up, so I remembered last time I did that that I had to delete the fstab.sailfish file. I did that then re-flashed supersu and it still wasn't there, so I downloaded the app from the playstore.
I went into the app and chose the full unroot option and said yes when asking if it wanted to restore the original boot.img.
After that I went back into TWRP and flashed magisk and it worked. I thought everything was good, when it booted all my root apps asked for permission.
Now the problems started , I kept getting the pop up that "android.process.media has stopped" working and also that gmail, calendar, photos, and the play movies app keep crashing.
I read that magisk can do OTA now without issues so I thought I would do the Android 7.1.2 to Anrdoid 8.0 jump using the OTA. I tried following this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips.
I thought updating would solve my issues but it didn't upon reboot with 8.0 I am still having all those apps continuously crash. I noticed magisk isn't installed anymore even though i followed those steps regarding the OTA update and magisk.
I also noted that when I plug my phone to my computer and chose transfer files nothing happens, the phone doesn't come up under my computer so I can't transfer anything.
what are my options now without losing any of my data? I did make a TWRP backup before I started all this, should I restore that? Will I lose my photos if I do that?
Please help!
Edit: Tried going into TWRP and I got the "No Command" picture. I was able to boot back into normal boot and into the phone.
Edit: Since updating to Oreo the "android.process.media has stopped" doesn't seem to appear anymore not sure if still an issue but Gmail, Photos, Calendar, and Play Movies keep crashing.
For anyone else that runs across this issue, wipe data for com.android.providers.media
Related
(Not sure if it is better to make a new thread or ask in the SuperSU thread...)
Hey all. I had previously been running the 7.1 OTA build with SuperSU installed. It seemed fine and I had done OTA updates with it installed with little issue. This was pre-2.78 SR3 builds of SuperSU, so I was using the boot-to-root. One day, I inexplicably noticed that root was gone. App too. I was very confused because to the best of my knowledge no OTA updates or security updates happened since I last rooted.
With that, I decided to sideload update to NMF26Q, which apparently was released about 12 hours earlier, and install TWRP since it was needed for newer SuperSU. TWRP installed fine and worked, but SuperSU did not seem to work. In fact, every time I attempted to flash SuperSU 2.78 SR5, I noticed it would remove the SuperSU app if it was installed via the Play Store. Finally, I noticed that it was installing in System mode.
I attempted to override this by running `echo "SYSTEMLESS=true" >> /data/.supersu`, but nothing I did worked. It did the same exact thing. Looking through the shell script, I'm entirely unsure how it is possible that my override did not work. I also reflashed the stock boot image to both slots and then reinstalled TWRP. This had no effect on installing SuperSU.
I try to do due diligence before turning to the internet for help, but I don't have any clue what's going on here. Maybe it is best if i reflash the entire stock ROM, but I'd love to avoid that if possible, as everything else seems to work great, and I have no idea why this in particular would be an issue.
Use alpha 2 of twrp and ask will be well
Yep, that worked great. Cheers.
http://forum.xda-developers.com/showpost.php?p=69626115&postcount=2
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
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
So, when I updated from OOS 9 to 10 I forgot to remove magisk and it's modules and completely forgot about it.
When I finished the update I noticed all the emojis where gone and from other posts here I found that it was because of a problem with the reserve partition that could be solved flashing a magisk module. Well, to my surprise, when I tried flashing magisk again on OOS 10 I always got stuck on a bootloop, I tried everything, removing the old modules that where still installed, using different twrp versions, using bluspark kernel, flashing a patched img through adb... But I always got a bootlop after installing magisk.
Since I couldn't get magisk on and was getting frustrated I decided to wait for the next OTA to see if it might fix it, but now that I tried installing it, I get stuck at 89% installation and don't know what to do. It's probably because of the reserve partition where the emoji should be, but since I can't use magisk idk how to fix it.
Is there another way to fix the reserve partition? Maybe a patch through twrp? Will a clean install of some sort help me or will it also get stuck at installation and brick my device?
Any help is welcome!
EDIT: Since noone replied I tried to fix it myself by trying to flash magisk a couple of times again (which gave me bootlops as expected), so I ended up flashing an OOS 5.1 downgrade build (which factory resets your phone so back up your stuff) and updating all the way to 10.3.1 through OTA updates. This fixed both my emoji and stuck update problem, so If you have similar problems and have not had any luck with other solutions I suggest you to downgrade like I did. If you back everything up on the cloud you should be back up and running in under an hour.
How did you flash the downgrade rom since your system updater is stuck?
Go twrp recovery, look for .Ota, flash the downloaded update zip and reboot.(Must be patient for step 2 to complete)
If can't find .Ota, go to File manager app, click storage below, click 3 dot on top right coner, settings, turn Show hidden file switch on
Ok having trouble updating and issue with rebooting
Have XX No limits and phone rooted
So backed up via Twrp and then installed ota update and then Twrp installer. Reebooted to recovery and then flashed Magisk
Re booted and kept getting error
Com. Android.Systems S........Keeps stopping
So rebooted to recovery again and flashed Magisk again and it worked and started ok
Then flashed no limits via magisk and same issue phone would not start
Then rebooted back into Twrp to reninstall back up and got a boot loop
So what is causing this and how can I fix it?
Thanks
funkyirishman said:
Ok having trouble updating and issue with rebooting
Have XX No limits and phone rooted
So backed up via Twrp and then installed ota update and then Twrp installer. Reebooted to recovery and then flashed Magisk
Re booted and kept getting error
Com. Android.Systems S........Keeps stopping
So rebooted to recovery again and flashed Magisk again and it worked and started ok
Then flashed no limits via magisk and same issue phone would not start
Then rebooted back into Twrp to reninstall back up and got a boot loop
So what is causing this and how can I fix it?
Thanks
Click to expand...
Click to collapse
The problem with bootloop can be caused by No Limits xXx ROM. It's exactly like Renovate Ice ROM. After updating Oxygen OS, I need to uninstall/disable Renovate Ice ROM and to wait that RIce to be updated to can use it again.
You can root with Magisk, reboot TWRP, open "Advanced">"File Manager">"data" (folder) >"adb"(folder)>"modules"(folder)>No limits (or something like that... Folder, again) and choose "delete">swipe right and reboot.
If it works, you can wait that NoLimitsxXx ROM to be updated.
P.S. sorry for my English and tell me if it worked
Dragoș2200 said:
The problem with bootloop can be caused by No Limits xXx ROM. It's exactly like Renovate Ice ROM. After updating Oxygen OS, I need to uninstall/disable Renovate Ice ROM and to wait that RIce to be updated to can use it again.
You can root with Magisk, reboot TWRP, open "Advanced">"File Manager">"data" (folder) >"adb"(folder)>"modules"(folder)>No limits (or something like that... Folder, again) and choose "delete">swipe right and reboot.
If it works, you can wait that NoLimitsxXx ROM to be updated.
P.S. sorry for my English and tell me if it worked
Click to expand...
Click to collapse
So everything is working just have not installed no limits
So take it remove all installed modules Reboot and reinstall no limits then install renovate ice?
funkyirishman said:
So everything is working just have not installed no limits
So take it remove all installed modules Reboot and reinstall no limits then install renovate ice?
Click to expand...
Click to collapse
No, I meant that some modules (Magisk ROMs usually) aren't compatible with every new Oxygen OS update, so you need to wait that respectively module to be updated.
I don't use No Limits xXx ROM, but I guess that Renovate Ice is exactly like this.
For example, you have two ways when you receive an update.
1. You can wait that your Magisk ROM to be compatible with the new Oxygen OS and then to install both.
2. You can install new Oxygen OS and wait that your Magisk ROM to be updated.
In case number two, I prefer to download it from settings (or Oxygen Updater app... it's the same size knowing that a unlocked bootloader needs a full update to not born conflicts). Ok, I download new update. I install it from settings. I DON'T REBOOT. Firstly, I go to disable all my Magisk modules, to install Magisk (After OTA to inactive slot). Then I reboot. I go to Magisk, install TWRP and Magisk (directly) and activate all my modules, but not Renovate Ice (or, in your case, No Limits xXx). I reboot and after that I need to wait the next update for Renovate Ice/No Limits xXx to come and to install it.