hello guys
i have a Samsung galaxy S6 g920F running on 6.0.1 with baseband G920FXXU3DPB6.
I have previously rooted my phone using CF-autoroot. Suddenly today when i tried to use superSU, it said "There is no SU binary installed, and superSU cannot install it. This is a problem!. If you have upgraded to Android 5.0, you need to manually re-root".
As i said above that i have rooted after i updated to 6.0.1 and was working till yesterday. i don't know what happen today that it started giving me this error.
I even downloaded latest cf-autoroot from its site and flash it through odin, but still no luck.
Can anyone please help me.
Thanks.
Flash a custom recovery and a kernel and then This
Had the same issue and doing this solved it. hope it helps
Here is how I get the root access back.
1. Copy to phone SuperSU 2.72
2. Flash with Odin arter97 kernel 13.1 (it has TWRP also)
3. Reboot in TWRP and flash SuperSU.
4. Reboot the phone
turulojko said:
Here is how I get the root access back.
1. Copy to phone SuperSU 2.72
2. Flash with Odin arter97 kernel 13.1 (it has TWRP also)
3. Reboot in TWRP and flash SuperSU.
4. Reboot the phone
Click to expand...
Click to collapse
can't we use on stock kernel only as it was before instead of flashing a custom kernel..?
Related
Just flashed the factory Rom and got everything set up. I flashed TWRP then tried to flash the latest SuperSu to get root and it installed it but when I went to open it it would say that I don't have any binaries installed and I can't uninstall SuperSU either. I tried to install CWM Recovery and refresh it through there but I still have the same issues... :/ What am I doing wrong or how can I get my phone rooted properly? Thanks for any help!
Nocturnal86 said:
Just flashed the factory Rom and got everything set up. I flashed TWRP then tried to flash the latest SuperSu to get root and it installed it but when I went to open it it would say that I don't have any binaries installed and I can't uninstall SuperSU either. I tried to install CWM Recovery and refresh it through there but I still have the same issues... :/ What am I doing wrong or how can I get my phone rooted properly? Thanks for any help!
Click to expand...
Click to collapse
You need to flash a kernel that is permissive and then flash SuperSU there are a few in the forums if you search you shall find them
Instead of a permissive kernel, simply use Chainfire's AutoRoot, which will flash a more secure kernel and SuperSU automatically. You don't even need TWRP for this. http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Go to http://autoroot.chainfire.eu/ to get AutoRoot for other devices.
aalaap said:
Instead of a permissive kernel, simply use Chainfire's AutoRoot, which will flash a more secure kernel and SuperSU automatically. You don't even need TWRP for this. http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Go to http://autoroot.chainfire.eu/ to get AutoRoot for other devices.
Click to expand...
Click to collapse
So I flash this in ADB? Is the secure kernel the same as stock? and if I were to flash a customer kernel like FK would I lose root? Sorry for all the questions just trying to clarify some stuff so I'm not completely ignorant to what I'm doing lol
There's a batch file that does it. You run it in the bootloader, not ADB.
FK has a Lollipop compatible kernel, but try and root stock first. Then flash FK's Lollipop version (it's different) and run CF AutoRoot again. Just to be sure things are working. Personally, I'm going to use stock for a while, understand the performance and then try FK or EX or whatever, so I'll be able to tell the difference.
Have now done the following .
1. Cell unroot per SuperSU ( If only a short note, then the app closed )
2. boot into TWRP manually and flashed Magisk - v6
3. next phh 's systemless superuser ) with Super SU magisk version already tried )
4. Mobile launched new
5. After that, it will not boot - When loading only the LED that flashes red and I have to flash a new firmware ...
Anyone know what I'm doing wrong ?
Have a Sony Xperia Z3 D6603
gerooted and SuperSU ( 2.78 )
TWRP 3.0.2-0
Rom : PureX v5 ( Android 6.0.1 - 23.5.A.1.291 )
Locked Blootloader
would be great if he had a solution for me ...
smellz said:
Have now done the following .
1. Cell unroot per SuperSU ( If only a short note, then the app closed )
2. boot into TWRP manually and flashed Magisk - v6
3. next phh 's systemless superuser ) with Super SU magisk version already tried )
4. Mobile launched new
5. After that, it will not boot - When loading only the LED that flashes red and I have to flash a new firmware ...
Anyone know what I'm doing wrong ?
Have a Sony Xperia Z3 D6603
gerooted and SuperSU ( 2.78 )
TWRP 3.0.2-0
Rom : PureX v5 ( Android 6.0.1 - 23.5.A.1.291 )
Locked Blootloader
would be great if he had a solution for me ...
Click to expand...
Click to collapse
I had the same, but maybe the SU can't uninstall. I'm on existenz Rom...
Don't you need an unlocked bootloader?
Sent from my D6633 using Tapatalk
at magisk was nothing about it because that an unlocked bootloader is required.
Yes unlocked Bootloader is required. My Bootloader is unlocked. But can't delete the superuser.apk. That's bad
Exactly the same happened to me. I tried SLiMM 3.1 and PureX V5. After installing Magisk in TWRP device is like dead - only led flashes. If I used Elite kernel, system boots, but the system gets random restarts. Now flashing eXistenZ.
Maybe cause you need to be on stock rom and stock kernel
I use the stock kernel with custom Rom based on the latest official version
Got same issue when using stock kernel on my Xperia Z2, switched to Advanced stock kernel Marshmallow 6.0.1 'cause it has Systemless root support and SElinux permissive and now everything works.
I have try it again, with unroot and install Magisk. Now it works with the advanced stock kernel. But I have some reboots when root is enabled.
Hi All,
I have the same problem, I can see S1 /SOMC Flash Device in Device Manager.
Could someone please post step by step instructions to restore a to Marshmellow?
Will I have to download an Image and a Flashtool?
I have D6603 with TWRP, I am not able to boot to recovery.
Z3- said:
Hi All,
I have the same problem, I can see S1 /SOMC Flash Device in Device Manager.
Could someone please post step by step instructions to restore a to Marshmellow?
Will I have to download an Image and a Flashtool?
I have D6603 with TWRP, I am not able to boot to recovery.
Click to expand...
Click to collapse
Resolved using Emma. I installed the S1 SOMC Flash Device Drivers and I was able to download lollypop.
I will attempt now to reinstall recovery, new rom, and Magisk
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.
Hello, I currently have a G920T that had been working alright for quite some time. The problem is that yesterday while using it normally, it suddenly froze. Thought it was the app, but saw it was the phone itself. Thus, I decide to turn it on again. When I do that, the phone does not continue after the logo and has the LED light white, while blinking on an off. When I manage to enter the Android Recovery menu it gives me the error shown in the title. The phone's rooted and was unlocked, so I could use it with AT&T.
I attempted doing a full reset, upgraded it to Nougat, and I am still stuck. Any help's appreciated in advanced.
Would like to say, when I installed the official Nougat Upgrade for my phone, upon starting, it began installing some things and then preceded to start Deleting. Afterwards, it just froze again. Did I do something wrong?
To get past this issue you have to Root with SuperSU, this will patch the Kernel to disable DM-Verity and will allow you to boot normally.
If you don't want to get rooted then reflash stock firmware via odin. never do OTA updates as i have always say the come "Dirty"
EDIT: Sorry didn't read you were rooted, just re-root again with SuperSU (To get your Kernel patched again) for DM-Verity
Starnel said:
To get past this issue you have to Root with SuperSU, this will patch the Kernel to disable DM-Verity and will allow you to boot normally.
If you don't want to get rooted then reflash stock firmware via odin. never do OTA updates as i have always say the come "Dirty"
EDIT: Sorry didn't read you were rooted, just re-root again with SuperSU (To get your Kernel patched again) for DM-Verity
Click to expand...
Click to collapse
So I use (what I previously used) cf-autoroot again? I ask this, since it seems their website have the recovery for marshmallow version and not for nougat (if I am not able to downgrade to 6).
Junito72 said:
So I use (what I previously used) cf-autoroot again? I ask this, since it seems their website have the recovery for marshmallow version and not for nougat (if I am not able to downgrade to 6).
Click to expand...
Click to collapse
Root with TWRP and superSU zip, i don't recommend CF-AutoRoot
Before flashing the Zip do the following on a Terminal in TWRP
Mount o- bind /dev/urandom /dev/random
Junito72 said:
So I use (what I previously used) cf-autoroot again? I ask this, since it seems their website have the recovery for marshmallow version and not for nougat (if I am not able to downgrade to 6).
Click to expand...
Click to collapse
You can use CF-AutoRoot for 6.0.1 and 7.0.
forumber2 said:
You can use CF-AutoRoot for 6.0.1 and 7.0.
Click to expand...
Click to collapse
When I use CF-Autoroot and attempt to boot it into recovery I get the following message, "recovery is not seandroid enforcing".
So I'd take I try installing a custom ROM first before attempting to start it in recovery?
Junito72 said:
When I use CF-Autoroot and attempt to boot it into recovery I get the following message, "recovery is not seandroid enforcing".
So I'd take I try installing a custom ROM first before attempting to start it in recovery?
Click to expand...
Click to collapse
Oh, that means CF-AutoRoot has not updated to work on 6.0 & 7.0 bootloader for G920T (It is updated and working on 6.0.1 & 7.0 for G920F)
Flash the stock ROM again. After that, flash TWRP and than flash latest SuperSU zip via TWRP.
forumber2 said:
Oh, that means CF-AutoRoot has not updated to work on 6.0 & 7.0 bootloader for G920T (It is updated and working on 6.0.1 & 7.0 for G920F)
Flash the stock ROM again. After that, flash TWRP and than flash latest SuperSU zip via TWRP.
Click to expand...
Click to collapse
I tried doing that, but wouldn't get past the main ROM's screen. I tried a custom ROM then (I think nemesis or such) and lasted longer, but again froze and loops with the white LED light on.
Any suggestions?
Hey! So let me get straight to the point . . . I used Odin flashed the TWRP recovery, installed SuperSU zip, installed NexusOS-9 ROM, then installed OpenGApps. However, my SuperSU app did not show up and Root Checker says I did not successfully root my phone. I have a Samsung S6 SM-G920T. Did I "root" my phone yet? and how come it shows up as not rooted? Please help. The Custom ROM and Gapps all work but it just says not rooted. Thanks in advance!