(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
I have the following installed:
[url]https://forum.xda-developers.com/oneplus-one/development/8-0-0r3-lineageos-15-0-t3670670[/URL]
Android: LineageOS 15.1 (8.1.0_r4) with latest magisk installed (15.3) with unofficial opengapps 8.1 mini package
When I try to downgrade to either Lineage 14.1 official or carbonrom 5.1 I am getting a boot loop at the oneplus logo. Restoring from backup to 8.1 resolves the issue.
1. factory reset
2. wipe system
3. Install Lineage 14.1 or carbonrom 5.1
4. Install recent opengapps mini package for 7.1.2
4. Reboot
The phone boot loops at the oneplus logo and I end up restoring from backup.
I have looked online and was struggling to find anything relevant. Some people report a new battery solved the issue but since It works when I restore from the backup It doesn't seem to be that. I do have a new battery on hand that I am eventually going to install though so I can do that.
Apologies if I am missing something obvious.
-Snowrider- said:
I have the following installed:
https://forum.xda-developers.com/oneplus-one/development/8-0-0r3-lineageos-15-0-t3670670
Android: LineageOS 15.1 (8.1.0_r4) with latest magisk installed (15.3) with unofficial opengapps 8.1 mini package
When I try to downgrade to either Lineage 14.1 official or carbonrom 5.1 I am getting a boot loop at the oneplus logo. Restoring from backup to 8.1 resolves the issue.
1. factory reset
2. wipe system
3. Install Lineage 14.1 or carbonrom 5.1
4. Install recent opengapps mini package for 7.1.2
4. Reboot
The phone boot loops at the oneplus logo and I end up restoring from backup.
I have looked online and was struggling to find anything relevant. Some people report a new battery solved the issue but since It works when I restore from the backup It doesn't seem to be that. I do have a new battery on hand that I am eventually going to install though so I can do that.
Apologies if I am missing something obvious.
Click to expand...
Click to collapse
Try the following :
-uninstall magisk using uninstaller(available in magisk forum)
-clear system,data,cache,dalvik
-install only the rom with out gapps
if it boots properly then you can install the gapps later or else if u find flashing gapps is causing the bootloop then use an older version and double check the compatibility.
if still not just try out another nougat rom
Thanks for the suggestion.
I tried your steps with the latest stable slimrom 7.1.2, lineage 14.1 and carbonrom 5.1 and I am still seeing the same issue. I was able to clean install the lineage 15.1 beta I linked to though in addition to restoring my backup as I have done before. I might try to clean install a different 8.1 (AOSP for example) and see if that one works. This will help narrow down if the issue is caused by 8.1 in general or specifically something that the lineage 15.1 beta has done.
I had a similar problem when I flashed Sultan's LOS14.1. I fixed it by flashing down to stock using wugfresh's bacon root toolkit. Keep in mind though that this will wipe EVERYTHING on your phone. Hope it doesn't come to that. Best of luck!
CedArctic said:
I had a similar problem when I flashed Sultan's LOS14.1. I fixed it by flashing down to stock using wugfresh's bacon root toolkit. Keep in mind though that this will wipe EVERYTHING on your phone. Hope it doesn't come to that. Best of luck!
Click to expand...
Click to collapse
This is what I ended up doing and it did the trick. Thank you for the suggestion.
Hello!
I have FRD-L09 with latest officially available firmware(FRD-L09C432B360) EMUI 5.1
I have successfully unlocked the bootloader and installed TWRP 3.1.1-1-FRD.
I have tried installing custom ROMs, Lineage and the one newer from it. Bootloop.
Magisk. Bootloop.
SuperSU. Bootloop.
On Lineage ROM, i got bootloop despite formatting data before and wiping cache/dalvik after flashing.
On Magisk, i have tried latest stable(v16) and test build(v16.6), both resulting bootloop despite if i wipe cache/dalvik or not. Magisk uninstaller works though, so i don't need to restore the whole ROM again.
Exactly same thing with SuperSU.
And by bootloop, i mean that the Honor intro plays only like 2 seconds and the phone restarts.
Any wild guesses what could be wrong? Apparently the TWRP flashes them right, because Magisk uninstaller works.
I found out o some random thread that the Magisk needs a newer firmware. Coincidentally the newest update 402 came out, so i tried to install Magisk, and it works.
At the same time the TWRP app got installed also.
I haven't found anywhere that all those apps are firmware-dependent.
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.
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