I had 6.01 Oct 2016 security image installed with SuperSU working great. I forgot which version I had when I flashed the images for the Dec 2016 security update.
Now I can't figure out which SuperSU to use. I tried the latest beta and the latest stable and my Nexus 5 would just bootloop for half an hour and nothing else. I know when you install it it should reboot a couple times, but bootlooping for 30 minutes isn't normal.
Anyone know which SuperSU version I should use?
2.78 SR5 (the latest beta) works fine for me.
Related
Hello.
I have a Pixel with stock Android that was rooted with Chainfire SuperSU 2.78SR3
Last night I've noticed that the phone isn't rooted anymore and has installed the Feb security update OTA. (I only had the Nov update installed).
I've tried rerooting using the same method (Fastboot boot) and got stuck in a bootloop.
I had to flash a clean stock rom to get it out of the bootloop.
Next I installed TWRP. That worked.
Next I tried installing a ZIP version of SuperSU 2.78SR4. The Zip installs but when I boot into Android SuperSU says that the phone isn't rooted.
Anyone had anything similar happen to them?
Borrisl said:
Hello.
I have a Pixel with stock Android that was rooted with Chainfire SuperSU 2.78SR3
Last night I've noticed that the phone isn't rooted anymore and has installed the Feb security update OTA. (I only had the Nov update installed).
I've tried rerooting using the same method (Fastboot boot) and got stuck in a bootloop.
I had to flash a clean stock rom to get it out of the bootloop.
Next I installed TWRP. That worked.
Next I tried installing a ZIP version of SuperSU 2.78SR4. The Zip installs but when I boot into Android SuperSU says that the phone isn't rooted.
Anyone had anything similar happen to them?
Click to expand...
Click to collapse
You might need to flash back to stock to fix this. If you do let us know so we can help you save your data and apps.
You used the wrong SU. You need 2.79 SR3. Note the 9 on there, you used 2.78.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Copy it to your phone and boot to TWRP. Then INSTALL it from TWRP.
So I experienced a "little" trouble after the Pie update, when trying too root my phone again.
Which one of you Oneplus 6-ers with rooted and "normal" phones also had problems after the Pie update?
And which one of you had the perfect update?
Perfect update here.
Coming from 5.1.5 straight to 9.0
Flashed bluspark.zip while still on 5.1.5, reboot to twrp, flashed Android Pie + twrp.zip + magisk 17.2, reboot twrp flash Android Pie + twrp.zip + magisk.zip again in second slot, reboot system.
Worked without any issues
From 5.11 to 9.0 with no issues. Updated to blue spark TWRP. Flashed full ota. Flashed TWRP again and Magisk 17.2. rebooted to TWRP, flashed TWRP and Magisk again and all was perfect. After first reboot I flashed EX Kernel 3.01 for pie and no Hicks and same insanely good battery life. No rogue apps (68 apps) at all.
Perfect here.
Updated dirty flash from twrp from 5.1.8 - 5.1.9 - beta 1 - beta 2 - beta 3 - stable pie - beta 4 never had an issue beside the device is corrupted message, i just ignored that one.
I tried to flash to magisk 19, 18, and 17 without success. I sideloaded and installed the newest april 19 security update OTA, I also grabbed the boot.img from there.
I tried using magisk manager to patch the image, I've tried using TWRP to install it to boot, as well as flashing with the zip... But both methods yields the same outcome, I get an infinite load (or boot loop ig?) and it won't work.
I flashed back to the original boot.img and phone works again. I also installed magisk 16.7 (by sideloading the zip) and my phone is now rooted again. Please help me, how do I use a later version of magisk (preferably the latest stable one)?
LootBoop said:
I tried to flash to magisk 19, 18, and 17 without success. I sideloaded and installed the newest april 19 security update OTA, I also grabbed the boot.img from there.
I tried using magisk manager to patch the image, I've tried using TWRP to install it to boot, as well as flashing with the zip... But both methods yields the same outcome, I get an infinite load (or boot loop ig?) and it won't work.
I flashed back to the original boot.img and phone works again. I also installed magisk 16.7 (by sideloading the zip) and my phone is now rooted again. Please help me, how do I use a later version of magisk (preferably the latest stable one)?
Click to expand...
Click to collapse
Try flashing the magisk uninstaller prior to flashing magisk.
Tulsadiver said:
Try flashing the magisk uninstaller prior to flashing magisk.
Click to expand...
Click to collapse
Thanks, that actually works.
Link contains factory boot, and patched images, bootloader and radio from stated release
August 2020 (canary): https://drive.google.com/drive/folders/1SpBngNA35CnCCF57jK8wjhRUQEeyyCHG?usp=sharing
Tulsadiver module disabler: https://forum.xda-developers.com/pixel-3-xl/themes/magisk-modules-disabler-t3966867 (i think magisk canary disables modules if you boot into safe mode https://github.com/topjohnwu/Magisk/commit/a5d7c41d209527fe7b45a2ef7d031add9b6fad24 )
Way to update without flashing: https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md
here is a guide for getting root: https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
platform tools were updated in july 2020: https://developer.android.com/studio/releases/platform-tools
and a guide for google pay with root: https://forum.xda-developers.com/ap...7-1-22-pie-t3929950/post79643248#post79643248
Hide Google pay, Google play services, Google services framework, clear Google pay data after update and apply module.
old factory and patched images:
July 2020 (canary patch): https://drive.google.com/folderview?id=16-XxwJbT5VIIT1cbDTXIffdOuqwx3XCH
Feb 2020 (beta patch): https://drive.google.com/open?id=1WZ2-tza0IB3oICGFCHuj1GJKJr0nd8a3
Jan 2020 (canary patch): https://drive.google.com/open?id=1_zNt1i2uqbGhfEiWn0O716v9noJdR4uJ
Dec 2019(canary patch): https://drive.google.com/open?id=1JHc86ZOHkyNA0uJ6r43eLqG4oe6KBfGy
nov 2019(canary patch): https://drive.google.com/open?id=14GA7qrPITZ_-jYNDAFuC0bJiaKwGmqRP
oct 2019(canary patch) : https://drive.google.com/folderview?id=16bbXgyWwi8TmJNaih_UvdtXxB8fC5W0t
note: i think you can go into recovery mode to disable modules with canary magisk if you have trouble.
updated OP with nov images
one report of nov 2019 update breaking google pay
The boot images are very helpful. Thanks!
I initially used the one patched for Magisk and was able to get root on the Nov release. Than I tried to install EdXposed Yahfa version (after installing Riru 19.5) and I got stuck in during boot at the "G logo" screen.
I was able to get back to a non-rooted system by reflashing the unpatched boot.img file. Now I need to figure out how to disable the Edxposed modules while staying on the November patch. The instructions for disabling Magisk modules seem written for a release earlier than Nov or they assume you have TWRP.
Any quick pointer on how to disable my Magisk modules on the November release?
if you can push the magisk uninstall zip to your device, then fastboot booting into twrp then flashing the magisk uninstall zip that should do the trick.
swieder711 said:
The boot images are very helpful. Thanks!
I initially used the one patched for Magisk and was able to get root on the Nov release. Than I tried to install EdXposed Yahfa version (after installing Riru 19.5) and I got stuck in during boot at the "G logo" screen.
I was able to get back to a non-rooted system by reflashing the unpatched boot.img file. Now I need to figure out how to disable the Edxposed modules while staying on the November patch. The instructions for disabling Magisk modules seem written for a release earlier than Nov or they assume you have TWRP.
Any quick pointer on how to disable my Magisk modules on the November release?
Click to expand...
Click to collapse
See this, https://forum.xda-developers.com/pixel-3/themes/magisk-modules-disabler-booting-magisk-t3967433. Twrp isn't going to work on 10.
jd1639 said:
See this, https://forum.xda-developers.com/pixel-3/themes/magisk-modules-disabler-booting-magisk-t3967433. Twrp isn't going to work on 10.
Click to expand...
Click to collapse
Thanks for the pointer. I wasn't sure if that Disabler would work with the November image.
I ended up reflashing the factory default and than reapplying the correct files. I now have GravityBox running on the Nov Image!
Up and running with OP's patched image and November "dirty" flash. Don't use G-pay so no report on that.
Edit - patched IMG after first boot shows magisk 19.5 installed, not 20.2 ¯\_(ツ)_/¯
ffchampmt said:
Up and running with OP's patched image and November "dirty" flash. Don't use G-pay so no report on that.
Edit - patched IMG after first boot shows magisk 19.5 installed, not 20.2 ¯\_(ツ)_/¯
Click to expand...
Click to collapse
OP updated to show 19.5.
Had the same issue and ran into the problem getting the modules disabled. Glad you were able to get it up and running.
Sent from my Pixel 3 XL using Tapatalk
i think doing a full uninstall of magisk (removes modules and settings) might be best until twrp or something else comes along...
Thanks for the patched image @dipstik. Gonna wait for Dec's iteration
chinesecooler said:
Thanks for the patched image @dipstik. Gonna wait for Dec's iteration
Click to expand...
Click to collapse
wait no more!
Woop woop, time for my bi-annually update
dipstik said:
wait no more!
Click to expand...
Click to collapse
Which version of Magisk did you use to patch the boot image? I tried using stable and canary to patch the stock boot image when I updated earlier, but each time it would just reboot straight to bootloader.
i patched with 20.2-72edbfc4 .
this thread might help. i havent updated yet. https://forum.xda-developers.com/pixel-3-xl/help/december-update-rootable-t4013605
dipstik said:
i patched with 20.2-72edbfc4 .
this thread might help. i havent updated yet. https://forum.xda-developers.com/pixel-3-xl/help/december-update-rootable-t4013605
Click to expand...
Click to collapse
I've been following that thread and there doesn't really seem to be a definitive solution yet. What works for one person doesn't seem to work for anyone else (including me). I'll just live without root for the first time in about 9 years until the problem is figured out...
Face_Plant said:
I've been following that thread and there doesn't really seem to be a definitive solution yet. What works for one person doesn't seem to work for anyone else (including me). I'll just live without root for the first time in about 9 years until the problem is figured out...
Click to expand...
Click to collapse
I read through this thread and the other thread you referenced, Has anyone tried topjohnwu's method: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md ? I used with the November update and had no issues. It doesn't involve flashing patched image.
Is root working for anyone else on the Dec update? I just flashed it and Magisk detects that it's installed (20.2 so I'm guessing it's Canary as the latest stable/beta is 20.1) but no root apps work at all.
comady25 said:
Is root working for anyone else on the Dec update? I just flashed it and Magisk detects that it's installed (20.2 so I'm guessing it's Canary as the latest stable/beta is 20.1) but no root apps work at all.
Click to expand...
Click to collapse
It is working for many and not for others. My wife's P3 rooted fine with canary.
jlokos said:
I read through this thread and the other thread you referenced, Has anyone tried topjohnwu's method: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md ? I used with the November update and had no issues. It doesn't involve flashing patched image.
Click to expand...
Click to collapse
I used this method and it worked with no issues. It was only the second time i used this method but with others having issues with the factory image and patched boot image i thought I'd give it a try.
Hi everyoneactually i bought samsung j5 pro from few days, so i started to search about how can i root it
but i found many ways to do that by magisk so i started to install twrp by odin 3.13.1 because my android system is 9.0 pieso i installed twrp but i got bootloop after install it directly and if i will flash it without open it i won't get bootloop and the basic recovery will back
i tried to install no-verity-opt-encrypt V 6.1 and 6.0 but that's didn't work too
i tried all the options in the internet and in this site and CF-Auto-Root-j5y17lte-j5y17ltexx-smj530f but nothing works and all the ways will take me to get bootloop againso what have i do to get rid of that bootloop and root the device by magisk?THE DEVICE INFO...ONE UI VERSION 1.1ANDROID VERSION 9
BASEBAND VERSION (J530FXXS7CTF1)
KERNEL VERSION(3.18.91-16642474)
BUILD NUMBER (PPR1.180610.011.J530FXWS7CTF1)
SE FOR ANDROID STATUS (ENFORCING.. SEPF_SM-J530F_9_0008)
KNOX VERSION (KNOX 3.4, KNOX API LEVEL 29, TIMA 3.3.0)
SECURITY SOFTWARE VERSION (ASKS V3.1.1 RELEASE 20200120, ADP V3.0 RELEASE 20191001, SMR JUN-2020 RELEASE 1)
ANDROID SECURITY PATCH LEVEL (1 JUNE 2020)
i hope you help me guys
Ammar Mamo said:
Hi everyoneactually i bought samsung j5 pro from few days, so i started to search about how can i root it
but i found many ways to do that by magisk so i started to install twrp by odin 3.13.1 because my android system is 9.0 pieso i installed twrp but i got bootloop after install it directly and if i will flash it without open it i won't get bootloop and the basic recovery will back
i tried to install no-verity-opt-encrypt V 6.1 and 6.0 but that's didn't work too
i tried all the options in the internet and in this site and CF-Auto-Root-j5y17lte-j5y17ltexx-smj530f but nothing works and all the ways will take me to get bootloop againso what have i do to get rid of that bootloop and root the device by magisk?THE DEVICE INFO...ONE UI VERSION 1.1ANDROID VERSION 9
BASEBAND VERSION (J530FXXS7CTF1)
KERNEL VERSION(3.18.91-16642474)
BUILD NUMBER (PPR1.180610.011.J530FXWS7CTF1)
SE FOR ANDROID STATUS (ENFORCING.. SEPF_SM-J530F_9_0008)
KNOX VERSION (KNOX 3.4, KNOX API LEVEL 29, TIMA 3.3.0)
SECURITY SOFTWARE VERSION (ASKS V3.1.1 RELEASE 20200120, ADP V3.0 RELEASE 20191001, SMR JUN-2020 RELEASE 1)
ANDROID SECURITY PATCH LEVEL (1 JUNE 2020)
i hope you help me guys
Click to expand...
Click to collapse
Flash an earlier version of the recovery (twrp) and sometimes it will reboot upto 3 times, so be patient .
2ISAB said:
Flash an earlier version of the recovery (twrp) and sometimes it will reboot upto 3 times, so be patient .
Click to expand...
Click to collapse
actually i tried many versions and all of them don't work i tried 3.1.1 and up
and i didn't find less than 3.1 of twrp
Ammar Mamo said:
actually i tried many versions and all of them don't work i tried 3.1.1 and up
and i didn't find less than 3.1 of twrp
Click to expand...
Click to collapse
hmmm. You did boot straight into twrp after installing it and wiped (factory reset) inside twrp and it will ask you to type in "yes" then slide across, then reboot back into twrp after a restart (holding the power up key) and all that.
then go to rebboot system..it should be working.
I would love to help, but im going back from 10 to 9 in about half hour.
cu tomorrow and the best faith and love my friend
2ISAB said:
hmmm. You did boot straight into twrp after installing it and wiped (factory reset) inside twrp and it will ask you to type in "yes" then slide across, then reboot back into twrp after a restart (holding the power up key) and all that.
then go to rebboot system..it should be working.
I would love to help, but im going back from 10 to 9 in about half hour.
cu tomorrow and the best faith and love my friend
Click to expand...
Click to collapse
ya actually i installed TWRP-3.3.1-j5y17lte-26052020 and i did same what you told me about wipe the data and i wrote (yes) and then i mounted the data from mount button then i installed magisk so that's work now and i wanna mention this that i used odin v 3.14.4
i was useing odin v 3.13.1 when i had bootloop
so thank you so much for your help
the best faith and love my friend ♥♥
You are welcome