Hello,
I tried flashing SuperSU 2.79 and 2.82 onto my G8141 which runs oreo but it always results in the phone getting stuck at the Sony logo right after the bootloader unlock warning.
Try Magisk 14?
It turned out that oreo didnt flash correctly and now TWRP wont even boot anymore.
Just reflash then .
BigBrainAFK said:
Hello,
I tried flashing SuperSU 2.79 and 2.82 onto my G8141 which runs oreo but it always results in the phone getting stuck at the Sony logo right after the bootloader unlock warning.
Click to expand...
Click to collapse
Does the kernel not need to be patched for SU to work?
Mackay53 said:
Does the kernel not need to be patched for SU to work?
Click to expand...
Click to collapse
It does but SuperSU does that when flashing with TWRP doesnt it?
Is there already supersu for Oreo?
It's because dm-verity and Sony RIC are active on stock kernel. If you flash root, the system won't boot.
sToRm// said:
It's because dm-verity and Sony RIC are active on stock kernel. If you flash root, the system won't boot.
Click to expand...
Click to collapse
How to deal with it
Related
I used Wugfresh's Bacon Root Toolkit to root my phone. I unlocked my bootloader and rooted my phone correctly and even got a confirmation by the toolkit saying that my phone was successfully rooted. However, my phone has been stuck on the CYANOGEN MOD READY for the last 30 minutes. How do I fix this?!
yqazi27 said:
I used Wugfresh's Bacon Root Toolkit to root my phone. I unlocked my bootloader and rooted my phone correctly and even got a confirmation by the toolkit saying that my phone was successfully rooted. However, my phone has been stuck on the CYANOGEN MOD READY for the last 30 minutes. How do I fix this?!
Click to expand...
Click to collapse
You should never use toolkits for rooting!
Now you need to flash TWRP recovery and flash any stock/custom rom as you like.
Flashing recovery wouldn't be much of a issue as your bootloader is already unlocked.
Mr.Ak said:
You should never use toolkits for rooting!
Now you need to flash TWRP recovery and flash any stock/custom rom as you like.
Flashing recovery wouldn't be much of a issue as your bootloader is already unlocked.
Click to expand...
Click to collapse
Darn
I tried using fastboot to install TWRP and I used TWRP to flash SuperSU. After rebooting, I had the same problem.
My phone is running CyanogenOS 13.1
yqazi27 said:
Darn
I tried using fastboot to install TWRP and I used TWRP to flash SuperSU. After rebooting, I had the same problem.
My phone is running CyanogenOS 13.1
Click to expand...
Click to collapse
Fek all that;
Just use kingoroot or kingroot(google it).
Make sure you've a fast connection.
And if you want to change from kinguser to supersu,use this guide..
https://forum.xda-developers.com/ca...ck-switch-kingroot-to-supersu-easily-t3426965
Mr.Ak said:
Fek all that;
Just use kingoroot or kingroot(google it).
Make sure you've a fast connection.
And if you want to change from kinguser to supersu,use this guide..
https://forum.xda-developers.com/ca...ck-switch-kingroot-to-supersu-easily-t3426965
Click to expand...
Click to collapse
I tried installing it but KINGROOT says there is no adaptation(root) available for A0001 Oneplus One
yqazi27 said:
I tried installing it but KINGROOT says there is no adaptation(root) available for A0001 Oneplus One
Click to expand...
Click to collapse
Use kingoroot latest version.
I'm sure one of it will work.
Mr.Ak said:
Use kingoroot latest version.
I'm sure one of it will work.
Click to expand...
Click to collapse
KINGOROOT didn't work either
yqazi27 said:
KINGOROOT didn't work either
Click to expand...
Click to collapse
Ok so I flashed back to CyanogenOS 11 and installed root and it worked. Then I went into TWRP and installed the CyanogenOS 13 zip. My device booted but my root access was gone. How do I update from COS 11 to COS 13 and still retain root? Also, TWRP asked to install SuperSU to root. I clicked no since my device was already rooted. Should I try again and click yes?
yqazi27 said:
Ok so I flashed back to CyanogenOS 11 and installed root and it worked. Then I went into TWRP and installed the CyanogenOS 13 zip. My device booted but my root access was gone. How do I update from COS 11 to COS 13 and still retain root? Also, TWRP asked to install SuperSU to root. I clicked no since my device was already rooted. Should I try again and click yes?
Click to expand...
Click to collapse
No,the root will not survive a clean flash.
Why don't you root cos13.1.x with twrp?
Mr.Ak said:
No,the root will not survive a clean flash.
Why don't you root cos13.1.x with twrp?
Click to expand...
Click to collapse
First of all, I did a dirty flash. Second if I SuperSU zip from TWRP while running COS13.1.2, my device gets stuck in a bootloop.
yqazi27 said:
First of all, I did a dirty flash. Second if I SuperSU zip from TWRP while running COS13.1.2, my device gets stuck in a bootloop.
Click to expand...
Click to collapse
Dirty flash of what?
I'm not talking about SuperSu.zip,Twrp has inbuilt root script,use that.
Flashing SuperSU will cause bootloop in Cm13 buddy.
Kalyan nath said:
Flashing SuperSU will cause bootloop in Cm13 buddy.
Click to expand...
Click to collapse
Are you sure you used latest SuperSU?
giaur said:
Are you sure you used latest SuperSU?
Click to expand...
Click to collapse
Yeah.
are you getting a bootloop or stuck at OnePlus bootlogo? i had a similar problem with SuperSU 2.78 and 2.79 besides i use MultiROM. after flashing a new 7.X ROM and SuperSU i got stuck at OPOs bootlogo.
by the way: never use toolkits
Sent from my One
Anyone know if I need to downgrade to MM and re-flash twrp to get Magisk working for systemless root?
I can install SuperSU but Magisk automatically reboots the phone while flashing the Zip file in twrp.
Zekisu said:
Anyone know if I need to downgrade to MM and re-flash twrp to get Magisk working for systemless root?
I can install SuperSU but Magisk automatically reboots the phone while flashing the Zip file in twrp.
Click to expand...
Click to collapse
No Magisk possible on N.
Read up on it here: https://forum.xda-developers.com/honor-8/how-to/info-loop-support-7-0-emui-magisk-t3578091
N01tra said:
No Magisk possible on N.
Read up on it here: https://forum.xda-developers.com/honor-8/how-to/info-loop-support-7-0-emui-magisk-t3578091
Click to expand...
Click to collapse
Cool ty for your reply.
Also all versions after 11.1 break the fingerprint sensor.
Magisk kernel is currently being worked on .ETA 10 days , check the post in the Dev section
+
I am not able to root my Z5 E6653 running the new .160 build
I have already rooted it when Lollipop, Marshmallow and 7.0 was installed but this time it is pretty weird!
bootloader is unlocked of course!
I flashed the patched kernel and TWRP 3.1.1
then i flashed magisk v12 and as SU binaries I chose SuperSU v82...
after booting and opening the SuperSu app it wants me to grant root access for itself, it says "greant for SuperSu" and then the app freezes and keeps crashing :/ reinstalling did not help, is v82 not compatible with 7.1.1 sony rom?
What kernel do you flashed
jpl8910 said:
What kernel do you flashed
Click to expand...
Click to collapse
the patched .160 kernel for e6653. I reflashed the 7.1.1 ftf and wiped everything except data so my system and stuf are back to normal, flashed the kernel and recovery again and this time I only flashed magisk v12 without SuperSu v82
now root is working
it seems like magisk v12 in combination with supersu v82 does not work ^^
First supersu then Magisk, otherwise is wrong.
sceryavuz said:
First supersu then Magisk, otherwise is wrong.
Click to expand...
Click to collapse
Okey thanks
freaky2xd said:
the patched .160 kernel for e6653. I reflashed the 7.1.1 ftf and wiped everything except data so my system and stuf are back to normal, flashed the kernel and recovery again and this time I only flashed magisk v12 without SuperSu v82
now root is working
it seems like magisk v12 in combination with supersu v82 does not work ^^
Click to expand...
Click to collapse
sceryavuz said:
First supersu then Magisk, otherwise is wrong.
Click to expand...
Click to collapse
Magisk has root built-in, there is no reason to flash SuperSU if you've successfully flashed Magisk. You either flash Magisk OR SuperSU, not both.
Devo7v said:
Magisk has root built-in, there is no reason to flash SuperSU if you've successfully flashed Magisk. You either flash Magisk OR SuperSU, not both.
Click to expand...
Click to collapse
Not for noob. If you want to use SuperSU with Magisk Modules, then you have to flash both with this order(SuperSU, Magisk).
Already mentioned on my thread..
Magisk is a module manager like Xposed. If you dont know..
sceryavuz said:
Not for noob. If you want to use SuperSU with Magisk Modules, then you have to flash both with this order(SuperSU, Magisk).
Already mentioned on my thread..
Magisk is a module manager like Xposed. If you dont know..
Click to expand...
Click to collapse
Exactly
At the moment I am using magisk v12 only though
root fail
freaky2xd said:
the patched .160 kernel for e6653. I reflashed the 7.1.1 ftf and wiped everything except data so my system and stuf are back to normal, flashed the kernel and recovery again and this time I only flashed magisk v12 without SuperSu v82
now root is working
it seems like magisk v12 in combination with supersu v82 does not work ^^
Click to expand...
Click to collapse
hello
i have xperia z5 running version 7.1.1 i have tried alot to root it but i couldnt please help me
thanks
So i flashed twrp on top of the stock rom and it just keeps bootlooping it not even getting to the samsung logo just the galaxy s6 splash screen
Heres a odin screenshot http://prntscr.com/h13jdx
Flash Magisk. It' s dm-verity
arkasha17 said:
Flash Magisk. It' s dm-verity
Click to expand...
Click to collapse
its need to flash magisk when you are on stock and flash twrp recovery?
what cause the dm-verity and what is that ?
paul222008 said:
its need to flash magisk when you are on stock and flash twrp recovery?
what cause the dm-verity and what is that ?
Click to expand...
Click to collapse
Just search. From twrp flash Magisk.
Inviato dal mio SM-G920F utilizzando Tapatalk
DON'T FLASH MAGISK v14.0
Like the others said, you need to flash magisk but don't flash magisk v14.0. I had huge issues with my SM-G920F with magisk v14.0 (I kept on losing root, modules didn't work correctly...) so I just went back to the last working version, which was v13.3. You can still install the same modules (by manually flashing them through apps like flashify), but you will never lose root (or at least I haven't). I lost root after 3 minutes of use on average on v14.0 and never lost it once on v13.3. However, the best way to do so it to run the uninstall script in twrp if you had magisk previously installed and then flash the older versions. The older versions can be found on the original magisk developer section right at the bottom where it says downloads.
Magisk Root now Works on Nokia 3 Device! You can flash it on Twrp recovery, and no errors comes up! (Like software update stopped working and cust manager) it requires stock boot image.
Link https://www.mediafire.com/folder/n2dmcnfjl7mz88h,4771ez9ddvccuim
In link, there is Magisk and Boot.img
RootingPro-18 said:
Magisk Root now Works on Nokia 3 Device! You can flash it on Twrp recovery, and no errors comes up! (Like software update stopped working and cust manager) it requires stock boot image.
Link https://www.mediafire.com/folder/n2dmcnfjl7mz88h,4771ez9ddvccuim
In link, there is Magisk and Boot.img
Click to expand...
Click to collapse
this is modified boot.img to work with magisk without errors, right? How to do this for SuperSU
SkaboXD said:
this is modified boot.img to work with magisk without errors, right? How to do this for SuperSU
Click to expand...
Click to collapse
No, this is clean boot img. Magisk you have to flash by yourself