Database Info

SuperSU 2.79 SR3 will not survive reboot

Google Play Store Pixel, stock feb update (nof26v), unrooted, unlocked bootloader. There's a longer back story to this issue I've encountered, but to cut to the chase:
I can successfully flash TWRP 3.0.2 RC1 and 2.79 SR3. I can boot into system and enjoy benefits of root. However, I've noticed that whenever I try to reboot SYSTEM, it only boots into recovery. Even when I boot into bootloader and flash stock boot.img, it'll just reboot into stock recovery, but never into system. My way out of this quasi soft-brick state is to flash stock boot.img and sideload ota and I'm good to go with all my settings/data intact, I'll just be unrooted (as expected). I can verify it survives reboot in this state.
Has anyone else encountered this before? Is there something in the latest SU that won't let it reboot properly? Is there a way I can force it to reboot a certain slot to somehow avoid this issue?
The way Android handles memory now, I don't ever feel the need to reboot. But one of the things that's essential for me is to edit build.prop to enable wifi tether and miracast. Thing is, it requires a reboot for those changes to apply, but as soon as I reboot...
I've had this all working before on the dec update and SuperSU-v2.79-201612051815.zip but then something really strange happened (long backstory referenced above) and it required me to have to re-root, only now it won't survive reboot.
Any insight is greatly appreciated!

I have never encountered this issue as a result of flashing Super SU. I have come across this when I updated to the latest image by just flashing a few components.. IE: i didnt flash the whole factory image.
Flashing the latest factory image to both slots and starting over fixed the issue for me.
Flash the image (flash_all.bat) then fastboot boot twrp and switch slots, flash factory image again.
Just my two cents.

k.s.deviate said:
Flashing the latest factory image to both slots and starting over fixed the issue for me.
Flash the image (flash_all.bat) then fastboot boot twrp and switch slots, flash factory image again.
Just my two cents.
Click to expand...
Click to collapse
Thanks for your input! Should I remove -w while flashing, or when you said starting over do you mean full wipe?
Was hoping to avoid going that route... Is there any way to salvage without wipe?

Let me also share the strange event I encountered which led me to this point:
As stated, I had December update with stable 2.79 and TWRP 3.0.2. I skipped Jan update and was planning to do the same for the Feb update, but for whatever reason, I went to check updates (knowing full well it wouldn't take since I'm not on stock recovery). It gave me the standard "downloading, installing..Oops, there's a problem" prompt and I went on my merry way.
A week or so later, I decided to manually reboot and upon boot, I noticed it said "Android is starting/configuring" something along those lines. Then I tried double tap to lock (Nova gesture) and it says phone wasn't rooted. I check and sure enough, no SU icon. Checked Android version and now it says I'm on Feb update.
Attempt to install latest from chainfire on play store and no dice. Decide to flash it instead. Downloaded 2.79 SR3. Booted temporary TWRP and flashed the install and SU and then I found that phone won't boot to anything but recovery. Now anytime, I modify the boot image in any way, I'm bricked on subsequent reboots until I flash stock boot image and sideload OTA.
How do you think the Feb update installed when it shouldn't have? Did it install to one slot while my other slot was TWRP+root?

I would guess that it may have installed onto the inactive slot, but it doesn't sound like it should have if you had TWRP and Su installed. However we are all still learning new things about the pixel every day.
I would recommend clean flashing the factory image to both slots and starting over. Sounds like something became corrupt.

What version of ADB and Fastboot are you running? This reboot to bootloader happened to me when I unknowing using an older version.

Try wiping the device completely push your factory image via ADB and fastboot and installed of TWRP RC1 use alpha 2 never had a issue with alpha 2 after flashing TWRP boot into stock then go back into TWRP then flash SuperSU

jamespark said:
How do you think the Feb update installed when it shouldn't have?
Click to expand...
Click to collapse
People have reported automatic OTA updates on rooted Pixel phones. You can shut off automatic OTA updates by following the following link. People report still getting a notification for updates after the setting change, but updates no longer happen automatically. The site below also lists a way to entirely shut off OTA notifications, yet that change causes my phone to stay awake constantly and never go into deep sleep, so I only recommend the link. There's a thread or two about FlashFire, which I may eventually get around to trying.
https://www.androidexplained.com/pixel-disable-ota-updates/

Are you okay with losing data? I can post the links I used to download SuperSU and a little guide to flash to stock and reroot. Maybe you'll be able to figure what you're doing wrong or just doing what I do step by step might fix it.

mngdew said:
What version of ADB and Fastboot are you running? This reboot to bootloader happened to me when I unknowing using an older version.
Click to expand...
Click to collapse
Definitely using an older version of adb and fastboot. I'll update and retry with the latest, thanks for the suggestion!

alluringreality said:
People have reported automatic OTA updates on rooted Pixel phones. You can shut off automatic OTA updates by following the following link. People report still getting a notification for updates after the setting change, but updates no longer happen automatically. The site below also lists a way to entirely shut off OTA notifications, yet that change causes my phone to stay awake constantly and never go into deep sleep, so I only recommend the link. There's a thread or two about FlashFire, which I may eventually get around to trying.
https://www.androidexplained.com/pixel-disable-ota-updates/
Click to expand...
Click to collapse
Thanks for the heads up! I had this setting enabled and I have since disabled it.
I really appreciate the community and all your help!

SOLVED
I'm pleased to report that I now have root that survives reboot!
- From stock: flashed TWRP and SU. verified root, edited build.prop and reboot system..... boots into recovery (the usual problem)
- switched active slots and flashed SU, reboot
- SU icon in app drawer but when launched: "supersu binaries not installed"
- reboot into recovery and flashed su, reboot
- su is installed, but build.prop changes didn't stick. edited build.prop, reboot system
- boots into recovery.
- flashed su, did NOT reboot, backed out, switched slots, flash SU to the other slot, reboot
- huzzah!
is it verified that android will alternate active slots upon each subsequent reboot (i.e. A/B/A/B/...)?
it would seem I was making changes and rebooting to the other slot which was jacked up, so I had to finally apply the same changes to both slots and now everything is working!
I honestly don't know what I just did, and I guess sometimes it's better to be lucky than smart lol but, boy, this two-system partition is a piece of work...
Thanks again to everyone for all your help!!

Pixel 3 March 2019 Root

Okay. I'm late getting into the pixel 3 game because I got my pixel 2 late last year. But i've just purchased it recently and it's great. But iv'e been unable to root it & I've never had any trouble rooting any Google devices in the past, stretching back to the nexus 3. I've always been under the impression that Google encourages rooting, or at least, makes no attempt to stop it. So I'm surprised that I even feel the need to make this post. I can find plenty of people talking about rooting even up to February's security patch, but nothing for Google's current most recent security patch (March 2019). Nothing I do seems to make any difference, I've followed steps on several tutorial threads to the letter and still end up in a boot loop. I'm tempted to downgrade so I can root, but I'd like to avoid that if possible. Am I the only one having this issue? I'm not able to find a wealth of people complaining about it, which strikes me as weird. Has Google done something with this update to actively block Magisk, or what? I'm at a loss. Like I say, never have I ever encountered such a road block in rooting any device.
Anyways, hopefully someone can ease my frustrations by at least sharing in them. Thanks for any replies.

This assumes you have already unlocked the bootloader...
1. Fastboot boot TWRP.
2. If you don't want permanent TWRP, skip to step 5. Otherwise, go to step 3.
3. Flash TWRP zip.
4. Reboot to recovery.
5. Flash magisk zip.
6. Reboot to system
That's it. It's the same on every security patch.

This is exactly what I am doing. I've also tried manually patching the boot image and live booting it as well as flashing it, but none of these methods render any different result. I've done it so many times I don't need to follow instructions, I only looked at tutorials because it kept failing. I've definitely got the bootloader unlocked but every time I install Magisk I get boot looping.

You need to boot into system before flashing magisk.

watlingj said:
This is exactly what I am doing. I've also tried manually patching the boot image and live booting it as well as flashing it, but none of these methods render any different result. I've done it so many times I don't need to follow instructions, I only looked at tutorials because it kept failing. I've definitely got the bootloader unlocked but every time I install Magisk I get boot looping.
Click to expand...
Click to collapse
Maybe a shot in the dark, but, in twrp, after you flash the magisk zip, reboot to twrp, flash the magisk uninstaller, then flash magisk again. I had the same issue when I updated to 9.0 on my P2XL :good:

wangdaning said:
You need to boot into system before flashing magisk.
Click to expand...
Click to collapse
I've never had issues without booting back to system before flashing magisk.

Badger50 said:
Maybe a shot in the dark, but, in twrp, after you flash the magisk zip, reboot to twrp, flash the magisk uninstaller, then flash magisk again. I had the same issue when I updated to 9.0 on my P2XL :good:
Click to expand...
Click to collapse
Thanks for the suggestion but alas, still boot looping.

wangdaning said:
You need to boot into system before flashing magisk.
Click to expand...
Click to collapse
I've tried this, it didn't make a difference.

OK, try:
1) Flash factory image, remove -w if you want
2) Reboot system then reboot bootloader
3) Fastboot boot TWRP (if you flash install zip reboot system again, then back to recovery)
4) Flash magisk v18.1 (redownload it to eliminate bad dl as culprit)
Not sure what is causing your problems. The initial guide is the same as with the march update. I have done it several times without issue.

wangdaning said:
OK, try:
1) Flash factory image, remove -w if you want
2) Reboot system then reboot bootloader
3) Fastboot boot TWRP (if you flash install zip reboot system again, then back to recovery)
4) Flash magisk v18.1 (redownload it to eliminate bad dl as culprit)
Not sure what is causing your problems. The initial guide is the same as with the march update. I have done it several times without issue.
Click to expand...
Click to collapse
Sorry for the late reply, i actually ended up returning it to stock and swapping it for a different one, because my speaker was making a weird sound when i was calling and it was having bluetooth issues, this one rooted perfectly fine first try.'
Except, Magisk randomly can't detect it's self through it's own manager app, but all my installed modules are working.. but i can't... manage them..

Updated to 9.5.9 and now it reboots into TWRP over and over.

I followed the previously rooted guide to update to 9.5.9 and now when the phone reboots, it gets to the unlock screen and immediately tells me its shutting down and reboots back into twrp again. How do i fix this? Please help and thank you.

what method did you use (there are a million rooted guides)? did u get the correct OS OTA for you model phone? provide us more info please.

Looks like i forgot to turn off the magisk modules. I had to go into twrp and delete them all and re download the modules. silly me

I'm having a similar issue. I can't figure out what to do, but I i went and deleted all the zip files for magisk but after reinstalling magisk thru twrp, I get stuck booting to recovery everytime. I can someone help point me in the right direction?

jakemaxfield said:
I'm having a similar issue. I can't figure out what to do, but I i went and deleted all the zip files for magisk but after reinstalling magisk thru twrp, I get stuck booting to recovery everytime. I can someone help point me in the right direction?
Click to expand...
Click to collapse
I stuck at the same situation. Can you flashboot flash boot.img and then it can boot normally?

Same problem here.
Situation before flash: stock 9.5.8, Magisk, a number of Magisk modules
What I did:
* downloaded 9.5.9 with Oxygen Updater
* disabled Magisk modules
* rebooted
* installed 9.5.9 from the builtin System Update
* went to Magisk, installed it with After OTA
* rebooted to recovery
* installed TWRP and Magisk
* cleared Dalvik
* rebooted to system
The phone seems to start normally, but when it reaches the unlock screen it immediately goes to Power Off, then it reboots to TWRP (not power off). From TWRP I can decrypt data ok etc.
I tried reinstalling the boot loader, OTA image, TWRP, Magisk - same result. Rebooting to system from TWRP just goes back to Power Off then TWRP.

equlizer said:
I followed the previously rooted guide to update to 9.5.9 and now when the phone reboots, it gets to the unlock screen and immediately tells me its shutting down and reboots back into twrp again. How do i fix this? Please help and thank you.
Click to expand...
Click to collapse
If this is any help in the future, whilst I don't have twrp, I install the updates via local update in settings > system > updates and then before reboot I go to magisk manager, and install magisk to second slot and reboot. Never had a problem and I'm on 9.5.9 now. The only modules I disable, update, or remove are the magisk ROMs available here such as no limits, as they are usually version specific.

manor7777 said:
If this is any help in the future, whilst I don't have twrp, I install the updates via local update in settings > system > updates and then before reboot I go to magisk manager, and install magisk to second slot and reboot. Never had a problem and I'm on 9.5.9 now. The only modules I disable, update, or remove are the magisk ROMs available here such as no limits, as they are usually version specific.
Click to expand...
Click to collapse
That's exactly what I did. It landed me to the bootloop.

All you guys had to do is,
Install the full uddate zip in twrp,
Install the latest twrp zip,
Reboot recovery,
Install latest magisk,
Reboot system,
Hope this helps, cheers

Update: I can break out of the loop from TWRP > Advanced > Fix Recovery Bootloop. That lets me boot normally, but loses root. As soon as I reinstall Magisk I get back to the bootloop.

lcd047 said:
Update: I can break out of the loop from TWRP > Advanced > Fix Recovery Bootloop. That lets me boot normally, but loses root. As soon as I reinstall Magisk I get back to the bootloop.
Click to expand...
Click to collapse
I'm in the same boat.
My twrp doesn't offer to decrypt partition_b so I cannot manually install Magisk on the new partition.

This seems to be a common problem when updating rooted Oneplus 7 pro and I haven't found a update guide which actually works every time. Last update to 9.5.8 I had the same issue where I couldn't get into oxygen os because it turned itself off and when twrp opened I couldn't decrypt the data. I couldn't find a solution last time and I had to full wipe and start from scratch. Now I don't want the same to happen so I hope someone can post a guide how to do the update successfully.

sapalot said:
This seems to be a common problem when updating rooted Oneplus 7 pro and I haven't found a update guide which actually works every time. Last update to 9.5.8 I had the same issue where I couldn't get into oxygen os because it turned itself off and when twrp opened I couldn't decrypt the data. I couldn't find a solution last time and I had to full wipe and start from scratch. Now I don't want the same to happen so I hope someone can post a guide how to do the update successfully.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.

Sometimes you might be on the wrong active slot, you can change this by using fastboot set_active a or fastboot set_active b. TWRP seems to like changing your slot but will tell you when it does. If you're getting stuck try changing slot and booting.

schmeggy929 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.
Click to expand...
Click to collapse
It worked for me for 9.5.8, got the bootloop this time around. I guess this means I'm not the Chosen One.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
djsubterrain said:
Sometimes you might be on the wrong active slot, you can change this by using fastboot set_active a or fastboot set_active b. TWRP seems to like changing your slot but will tell you when it does. If you're getting stuck try changing slot and booting.
Click to expand...
Click to collapse
I tried that too. When I switch to the other slot I get to a menu where I can only wipe data, reboot to boot loader, or reboot to recovery. Not particularly useful.

Hey guys!
I'm having the same problem. No matter how I try to update it will reboot to stock recovery.
I was wondering if any of you have /Data converted to f2fs? Maybe it could be culprit...

mkos86 said:
Hey guys!
I'm having the same problem. No matter how I try to update it will reboot to stock recovery.
I was wondering if any of you have /Data converted to f2fs? Maybe it could be culprit...
Click to expand...
Click to collapse
What I had to do here was go to fastboot mode and flash twrp img. Then in TWRP I flash the TWRP zip file and magisk and rebooted. All good

Alright so I fixed mine. I went and just removed all the modules while I was in twrp. To do that go to Advanced, then file manager or whatever it says, find the adb folder and from there look for a folder named Modules and just delete them all. From there just reinstall magisk through twrp and it should all work.

jakemaxfield said:
Alright so I fixed mine. I went and just removed all the modules while I was in twrp. To do that go to Advanced, then file manager or whatever it says, find the adb folder and from there look for a folder named Modules and just delete them all. From there just reinstall magisk through twrp and it should all work.
Click to expand...
Click to collapse
Thank you sir, this fixed it for me, too. So the missing link was that Magisk modules have to be removed completely, not just disabled, before upgrading. Removing all directories except .core from /data/adb/modules allows the phone to boot normally, with Magisk enabled.

schmeggy929 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.
Click to expand...
Click to collapse
Thats the way i tried that time and got stuck in bootloop.

Struggling to flash TWRP / Magisk on last Android 11 update

Hello everyone! Thanks in advance for taking a look at this thread.
I recently upgraded from a Pixel 2 to a Pixel 5 and decide to root my old phone and mess around with that before doing the same with my new phone. It's been several years since I've messed around with rooting a device, so I've spent some time this week refreshing myself on how to do so.
I've already unlocked my bootloader, but the main issue that I'm running into is when I try to install TWRP or Magisk. For some reason, when I try to flash TWRP (version 3.3.0.0), I've managed to install it properly but loading into recovery mode just leaves me stuck at the TWRP splash screen, while booting directly into it doesn't allow me to backup my data (kicking out an error 255 each time). It would be nice to have TWRP to be able to back up rather than starting from scratch each time, even if I've gotten quick at flashing the stock image when I screw up later.
As for Magisk, I've tried flashing the patched boot image through TWRP and received errors (size of image is larger than target device) as well as the .zip file which just caused a bootloop. I know you can install Magisk without TWRP, so I've tried doing that as well. I've been working with both Magisk 23.0 and the Canary build with no luck; after patching the boot image and attempting to flash it using fastboot flash boot magisk_patched.img, I just repeatedly get an error showing "FAILED (remote: 'Error flashing partition')".
So far I've not really been able to find any solutions on how to fix this, so I feel a bit stuck at this point (and definitely questioning my ability to just follow directions). Any advice on how I might get around these errors?

Hello mate,
With regards to installing twrp, I think there is a workaround in the official twrp thread to get twrp installed with working decryption and working pin by rolling back to a pie build prior to encryption being broken for twrp. Personally I just fastboot it when needed to flash anything but sadly twrp back ups don't work (I'm on A11).
It sounds as if you have tried to install magisk a few ways but I found the simplest way was to install the latest magisk.apk then rename it to magisk.zip and flash it via fasbooted twrp.
It sounds as if you tried patching the image etc so may pay to reflash the stock boot.img and then do the APK/zip method to get magisk running.
Lastly, if you don't mind losing your data it may well pay to reflash a full stock.img and then try magisk again. It's solved a few dramas for me when stuff didn't seem to work first time round.

Qualcomm Crash Dump Mode - PLEASE HELP - Hard Brick ?!

Hello!
I wanted to update my oneplus 8 from 11.0.4.4 to newest version. OTA was not working idk why. I had magisk in place and I patched magisk to second partition or something like that [I dont remember how it was called] - I'm sure this is the reason of the problems. I turned off devices and wanted to boot into recovery, but suddenly it boot into Qualcomm crash dump mode with message: Attempted to kill init! exitcode: 0x00007f00 do_exit - that's all. I can't boot the system, I can;t boot into recover, I flashed patched boot, I flashed recovery - none of these works. Fastboot is present and recognized by PC.
First question can I do some backup through fastboot? To be honest I was not prepared for such problems. APKs are not even such a problem I care more about photos, documents and other data.
Can I flash some rom and restore phone back to life without wiping my personal data?
Maybe an idea would be to load TWRP recovery and then do backup, but how to boot into recovery when even after flashing recovery or booting via fastboot it enters in qualcoom crash dump mode. Something must be corrupted, but is it possible to fix some partition just in order to flash recovery to do backup of the files?
Please can you help me? I tried with some tutorials, but no success...

What did you try doing if OTA wasn't working?
You won't be able to use TWRP since you're on Android 11.

Okay I managed to get back to normal - since like I mentioned i patched the magisk into second slot, then probably this corrupted something. What has helped me is this: fastboot --set-active=b
It was not working via powershell I had to launch CMD and then it worked I switched slot to "b" and phone booted normally.
Regarding OTA I have no idea what has happened. The only things I have done is magisk with modules like xXx No Limits and YTB Vanced. To be honest nothing more. I'm at Oxygen OS 11.0.4.4.IN21AA with bootloader unlocked. What would you suggest to do in order to update to newest version?

I would disable the magisk modules first in case that is what caused problems. Then do a local upgrade using the full OTA zip. Then install magisk to the inactive partition. I think that would work, but I'm not sure if a messed up A partition might affect the installation. I don't think so, but I haven't read anything about it. After, you can try re-enabling the magisk modules.

I turned off all the modules obviously and still OTA is not working via the oneplus updater. It does not see the zip rom even though it's in the main directory. I don't know what is wrong...

Oh, that's strange. I don't know how to recover from there. If it were me, I would just backup my files and MSM, but that's a lot of work.
Did you check the obvious things for the zip file like making sure it ends in the right extension? Sometimes if you download it from OnePlus, it has a jar extension instead of zip.

L
trinidude4 said:
Oh, that's strange. I don't know how to recover from there. If it were me, I would just backup my files and MSM, but that's a lot of work.
Did you check the obvious things for the zip file like making sure it ends in the right extension? Sometimes if you download it from OnePlus, it has a jar extension instead of zip.
Click to expand...
Click to collapse
Lol yes you're right it was jar. Now the updater sees the zip file, but I'm afraid to update because I'm not sure if the phone won't brick or bootloop. What do you think?

I think it should be fine. I think the only thing that got messed up was the boot partition on the A slot and that will get overwritten with the OTA.

How about the root and magisk?

Okay I updated and it's working fine. I'm on 11.0.7.7 but now magisk is not working, how to get it back?

remialfa said:
Okay I managed to get back to normal - since like I mentioned i patched the magisk into second slot, then probably this corrupted something. What has helped me is this: fastboot --set-active=b
It was not working via powershell I had to launch CMD and then it worked I switched slot to "b" and phone booted normally.
Regarding OTA I have no idea what has happened. The only things I have done is magisk with modules like xXx No Limits and YTB Vanced. To be honest nothing more. I'm at Oxygen OS 11.0.4.4.IN21AA with bootloader unlocked. What would you suggest to do in order to update to newest version?
Click to expand...
Click to collapse
Any idea if it's possible to do something similar to rooted OP6?
I have a similar situation where I tried to update magisk and ended up with a bricked device.
I can reboot to fasboot, but I can't boot to recovery or flash anything through some pc flashing apps.