Hi everyone,
I have some weird root on my Meizu Pro 5 with 5.1.6.0 G. Root permissions are ON in the Settings/Fingerprint and Security/Root Permission/ . I have a list of apps with Allow permission, including SuperSU, BusyBox, Root Explorer and Terminal Emulator. When I launch any of these apps for the first time I get a prompt for permission and I choose Allow.
However, Root checker does not recognize the root and Kingroot failed to root the device. When I boot device into fastboot to unlock the bootloader to install TWRP, I see “Fastboot [locked, rooted]” message. Whenever I try to use “su” command in the Terminal it returns access denied or something similar. SuperSU app fails to update the binary, although, ES Explorer has root access to explore files.
I tried to Reset to factory settings - same issue
Tried to Factory reset + Format internal storage and test root on clean device without even restoring from a backup - same issue
Tried to flash update.zip from File Explorer and from Recovery itself - firmware corrupt and does nothing.
Not sure when and what went wrong. I updated to 5.1.6.0G via terminal commands, hence I had su access with no problems.
Do you have any ideas? Now I just want to revert to the original state of the device and repeat the rooting from scratch, but unable to do so since any firmware I tried was "corrupt" and terminal does not let to use commands.
P.S. After "Factory reset + Format internal storage" in the very first boot of the device I noticed that Root access was already ON, even though I skipped the Flyme account login step. The phone is working fine - no bootloops, not bricked. Even Xposed is installed and working fine. The only issue is with the root, which appears to be incomplete.
Something similar happened to me.
Just update Flyme and check clear data. Then root it again.
Found the problem: if you are unrooted on the bootloader (check with [power] + [vol-])
And rooted within flymeos, you experience this problem.
I've got the same issue but I'm unable to instal another version of flymeOS (got corrupted firmware).
Does someone know how to fix ?
Atarhorn said:
I've got the same issue but I'm unable to instal another version of flymeOS (got corrupted firmware).
Does someone know how to fix ?
Click to expand...
Click to collapse
I might be able to help you, do you have a locked bootloader ?
Related
Hi,
i try to encrypt and root my note 4.
After rooting the phone i try to encrypt it, but it always stuck after reboot on the samsung logo (for hours)
Without rooting it will encrypt in ~10 mins.
Ps. the note is rootet with the 4.4.4 cf-auto-root from chainfire.
anyone had a soulution for me ?
thank you so mutch ! :good:
edit:
I found a soulution for this.
1. root your phone with cf-auto root
2. install busybox
3. install a terminal app
4. open the terminal app and type:
su
pkill -KILL daemonsu
after this you should be back at the "$" prompt
now directly encrypt your phone, dont reboot or change something in the terminal app
Nexus-Nerd said:
Hi,
i try to encrypt and root my note 4.
After rooting the phone i try to encrypt it, but it always stuck after reboot on the samsung logo (for hours)
Without rooting it will encrypt in ~10 mins.
Ps. the note is rootet with the 4.4.4 cf-auto-root from chainfire.
anyone had a soulution for me ?
thank you so mutch ! :good:
edit:
I found a soulution for this.
1. root your phone with cf-auto root
2. install busybox
3. install a terminal app
4. open the terminal app and type:
su
pkill -KILL daemonsu
after this you should be back at the "$" prompt
now directly encrypt your phone, dont reboot or change something in the terminal app
Click to expand...
Click to collapse
Thank you for this! It worked for me.
Just a word for advice for anyone that tries to DECRYPT their phone after having encrypted it using this method. When I tried decrypting my phone I got a decrypt fail error telling me I had to reset the device, but because I had a custom ROM the reset wasn't working. I had to ODIN back to stock and start all over.
So, though I didn't try it again, you probably need to follow the same steps prior to decrypting. Either way, keep in mind you may be forced to reset so do backups before you attempt to decrypt.
That was on a T-Mobile Note 4 on KitKat, not Lollilop BTW.
Another method (success)
Just to share my experience, maybe it will be useful for someone.
I have Galaxy Note 4 rooted using CF-auto-root, and when trying to encrypt the device, all I got was green android logo on black screen for hours. The phone froze, so I eventually had to pull out the battery. After booting I got the message that encryption failed due to interruption, and promted to do a factory reset, which I did.
I tried the method above, but it did not work. The result was exactly the same -- green robot and nothing else.
Then I tried another method I found in another thread, and it worked!
1-Root your device and install/update SuperSu;
2-Convert SuperSu to system app (there is an option in SU config). Reboot.
-OBS: If your root method has already installed SuperSu as a system app, this step can be skipped;
3-As SuperSu is now a system app, it can be deactivated through Applications Management in settings. Deactivate it;
-OBS: does NOT use deactivate in SU own config;
4- Reboot in Safe Mode. This can be done pressing both Volume Up/Down while rebooting;
5-Start encryption the normal way and wait until it finishes. Enter your password and wait device boot normally;
6-Go to Applications Management in settings and activate SuperSu;
7-Reboot one more time and your system is encrypted with SuperSu working normally.
Oscar_6 said:
Just to share my experience, maybe it will be useful for someone.
I have Galaxy Note 4 rooted using CF-auto-root, and when trying to encrypt the device, all I got was green android logo on black screen for hours. The phone froze, so I eventually had to pull out the battery. After booting I got the message that encryption failed due to interruption, and promted to do a factory reset, which I did.
I tried the method above, but it did not work. The result was exactly the same -- green robot and nothing else.
Then I tried another method I found in another thread, and it worked!
1-Root your device and install/update SuperSu;
2-Convert SuperSu to system app (there is an option in SU config). Reboot.
-OBS: If your root method has already installed SuperSu as a system app, this step can be skipped;
3-As SuperSu is now a system app, it can be deactivated through Applications Management in settings. Deactivate it;
-OBS: does NOT use deactivate in SU own config;
4- Reboot in Safe Mode. This can be done pressing both Volume Up/Down while rebooting;
5-Start encryption the normal way and wait until it finishes. Enter your password and wait device boot normally;
6-Go to Applications Management in settings and activate SuperSu;
7-Reboot one more time and your system is encrypted with SuperSu working normally.
Click to expand...
Click to collapse
I have been trying to find a way to do this on my TMobile branded Note 4 for some time now. As I am contemplating updating to the recently released 5.0.1 for my variant, I wanted to know if you have had any problems with your device after using your method? Were there any issues with regard to decryption?
PS- Anyone else take 15 tries to get through the blasted image verification.
KingBeef said:
I have been trying to find a way to do this on my TMobile branded Note 4 for some time now. As I am contemplating updating to the recently released 5.0.1 for my variant, I wanted to know if you have had any problems with your device after using your method? Were there any issues with regard to decryption?
Click to expand...
Click to collapse
I have upgraded to Lollipop before encrypting the phone. I didn't try to decrypt it after encryption. So far, everything is working normally.
Greetings Folks!!!
I am on CM12.1 Lollipop 5.1.1 Nightly, and ROOT access was working fine on my phone so far. When I launched Thunderzap today, I noticed that the app was waiting on "Requesting ROOT Privileges" for over 2 mins, and also the SuperSU app was missing from the app drawer. Thunderzap had been recently updated, and I suspect that might have triggered the root access to be requested again, but it wasn't given root access for some reason, and I never got a prompt to grant it root access. However, my other apps like ROOT Explorer, Shell Terminal Emulator etc, which weren't updated off lately, worked fine with root access. Not sure why now, but I thought reinstalling SuperSU-v2.46 might be a good idea at that time, and I flashed that file. And ever since I have completely lost my root access. When I launch the SuperSU app now, i get an error saying:- "There is no SU binary installed, and SuperSU cannot install it"
Some help would be appreciated. Screenshots attached.
I've managed to fix the issue. I just re-flashed the CM-Update file (located in the pone's internal memory), and got some ROOT access prompt while trying to open Thunderzap again. Thereafter, I installed SuperSU from the Playstore and got my binary updated through it. :good:
acemccloud1 said:
I've managed to fix the issue. I just re-flashed the CM-Update file (located in the pone's internal memory), and got some ROOT access prompt while trying to open Thunderzap again. Thereafter, I installed SuperSU from the Playstore and got my binary updated through it. :good:
Click to expand...
Click to collapse
can you please share the method u used to flash back CM?
i am unable to re root
According to the following post, I should be able to gain root on my encrypted phone.
wgspoelstra said:
Yes, decryption is broken right now. On all versions of TWRP available, that support Oxygen OS 3.x.x, decryption is non-functional.
I have a workaround for flashing zips with an encrypted phone:
Boot into recovery, flash SuperSU over ADB Sideload, reboot phone.
You now have working root. Any zips you want to flash, place them in /system/media folder.
I use Root Explorer for this. When you boot back into recovery, mount /system and navigate to /system/media folder.
This way you can still flash all zips you want without decryption.
Click to expand...
Click to collapse
But I am having issues. Most notably, ADB does not recognize my phone unless I connect while in the OS or in stock recovery. If I connect while using any custom recovery (I've tried Hybrid and a few versions of TWRP), ADB does not list my phone when I run ADB devices. It's also very wonky trying to get stock recovery back on my phone afterwards, but that's a different issue.
While attempting to flash SuperSU when using stock recovery, the command sends the file and the phone begins the "update". It runs for about a second and then I get a "Installation Failed" message on my phone's screen. I've tried many different versions of SuperSU.
My current setup is the latest OOS (3.0.2) and stock recovery. The device is encrypted. My bootloader is unlocked, but I do not have root.
Could someone please help me out here? I have to have encryption on the phone for my work, but I really want to have root as well. Being able to customize my phone is why I went with OnePlus, but it's not proving to be any better than my Samsung Galaxy S4!!! Please help!
Hi, so I was trying to get full root not only system less root on j730gm and what i followed here to rooted mobile witj twrp first(boot.img patched), then after that full unroot (keep boot.img patched) and in twrp gave command and install super su zip again and this time logs clearly showed system method while rooting, after all that I am getting bootloop. Mobile is hang on samsung logo, tried reset with twrp and official recovery both. Can some one tell me where i did mistake or where is the problem. My only requirement is to root this mobile and make super user app as system app. Even after hard reset mobile should stay rooted. Any help would be much appreciated.
Br
Zish
zishhaider said:
Hi, so I was trying to get full root not only system less root on j730gm and what i followed here to rooted mobile witj twrp first(boot.img patched), then after that full unroot (keep boot.img patched) and in twrp gave command and install super su zip again and this time logs clearly showed system method while rooting, after all that I am getting bootloop. Mobile is hang on samsung logo, tried reset with twrp and official recovery both. Can some one tell me where i did mistake or where is the problem. My only requirement is to root this mobile and make super user app as system app. Even after hard reset mobile should stay rooted. Any help would be much appreciated.
Br
Zish
Click to expand...
Click to collapse
I don't understand your goal?
Systemless root IS full root. Your terminology is incorrect.
SuperSU doesn't really support system root on Android 7.
I also dont see the point of making SuperSU a system app. Even though its rather pointless if that is all you require for whatever strange reason then you can just move the Supersu app to the system partition.
There is a better way to stay rooted after a hard reset and it's called FRP.
First there is nothing strange in stay rooted after hard reset, trust me. My friend use this mobile. He needs root for lucky patcher. When first he came to me I rooted it via twrp and after couple of days he came back with custom binary block option and plus he doesn't remember newly created gmail id pass. For me it was hell of a job. So i decided to root it permanently. I am not an expert though but my point was to take full root instead of systemless root. Thanks for clearing that 7.0 isn't supported for full system root. I saw here a rom stock dexoded and pre rooted. Is it better option to install it rather than stock rom?
See this link, i was trying to do the same
https://android.stackexchange.com/q...om-systemless-root-to-system-traditional-root
zishhaider said:
See this link, i was trying to do the same
https://android.stackexchange.com/q...om-systemless-root-to-system-traditional-root
Click to expand...
Click to collapse
Like I already stated Factory Reset Protection (FRP) is already built in to SuperSU.
Just do the following in a terminal then re-install SuperSU:
echo "FRP=true">>/data/. supersu
.
Hello,
recently I have flashed my ze500kl with XenonOS. I would like to go back to stock rom but I have couple problems.
First of all - my bootloader is now locked. I wanted to unlock it via SuperSU, that is already installed on my phone but when I try to open SuperSU App I see this:
"SU Binary occupied"
So I found tutorial on how to fix this issue, but the problem is i can't uninstall SuperSU, I can only disable it in App options.
Then I tried to install TWRP via App from Google Store, but offcourse my phone isn't rooted so I can only download TWRP installation files but can't initiate installation via App. I downloaded TWRP on my PC, opened ADB in CMD, installed it there and rebooted my phone. TWRP isn't loading and my device stuck on ASUS welcome screen.
I tried also WINDROID but I get lots of errors, so it's not working for me either.
Please help me unlock and root my phone. I really want to go back to stock os.
Thanks!
svyatogor92 said:
Hello,
recently I have flashed my ze500kl with XenonOS. I would like to go back to stock rom but I have couple problems.
First of all - my bootloader is now locked. I wanted to unlock it via SuperSU, that is already installed on my phone but when I try to open SuperSU App I see this:
"SU Binary occupied"
So I found tutorial on how to fix this issue, but the problem is i can't uninstall SuperSU, I can only disable it in App options.
Then I tried to install TWRP via App from Google Store, but offcourse my phone isn't rooted so I can only download TWRP installation files but can't initiate installation via App. I downloaded TWRP on my PC, opened ADB in CMD, installed it there and rebooted my phone. TWRP isn't loading and my device stuck on ASUS welcome screen.
I tried also WINDROID but I get lots of errors, so it's not working for me either.
Please help me unlock and root my phone. I really want to go back to stock os.
Thanks!
Click to expand...
Click to collapse
For anyone who struggle with the same issues.
Use ADB and twrp_2.8.7.7.img. I don't know why, I don't know how but this version of TWRP works.