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.
Related
I recently had to replace my phone through warranty and so now I'm new to Safestrap.
So please bare with me!
So what I am trying to do is root my phone keep the stock lollipop and put Xposed on but when I flash Xposed my phone gets stuck on AT&T.
The other day I ended up trying something different and yes Xposed work but I was getting gasps and google play not wroking.
Here are my steps for when my phone gets stuck on AT&T ( These are also my notes for me that I keep and follow)
1. Odin through computer and put I337UCUFNB1_Rootable_Full_Odin.
2. Once installed and gone through set up steps, installed Towelroot, and Root Phone.
3. Install Super User. (Sometimes after it disables Knox it requires to reboot or If disabling Knox takes WAY too long get out of app press menu key and close out all apps and clear ram. Re open super su and it will disable Knox and no reboot is required)
4. Install Flash Fire.
5. Flashed - I337_OC3_Stock_DeOdexed_ROM.zip through Flash Fire (Flash Zip or OTA). Once it tries to restart for about 10-20 minutes there will be AT&T logo.
6. Once installed and gone through set up steps again, install Busy Box, Safestrap, & NC1 Flasher.
7. In Safestrap app - clicked on Install Recovery
8. NC1 app - Flashed and reboot.
9. Safestrap loads up.
10. Wipe Factory reset
11. Install ATT_OC3_modules
12. Install I337_Stock_OC3_kernel_recovery_flashable and then reboot. Again AT&T logo sits for about 10 - 20 minutes and I do a battery pull.
13. Install Flash Fire and XposedInstaller_3.0_alpha4.apk
14. Flash xposed-v74-sdk21-arm.zip through Flash Fire.
15. The phone will sit at the AT&T logo for ever. I do a battery pull and still the same thing. Will not Boot up.
I DON’T THINK THIS IS PROCESS IS RIGHT BUT XPOSED DID WORK AND GASPS AND GOOGLE PLAY STOPPED WORKING.
-Note the Colored lines is what I did differently from up above
1. Odin through computer and put I337UCUFNB1_Rootable_Full_Odin.
2. Once installed and gone through set up steps, installed Towelroot, and Root Phone.
3. Install Super User. (Sometimes after it disables Knox it requires to reboot or If disabling Knox takes WAY too long get out of app press menu key and close out all apps and clear ram. Re open super su and it will disable Knox and no reboot is required)
4. Install Flash Fire.
5. Flashed - I337_OC3_Stock_DeOdexed_ROM.zip through Flash Fire (Flash Zip or OTA). Once it tries to restart for about 10-20 minutes there will be AT&T logo.
6. Once installed and gone through set up steps again, install Busy Box, Safestrap, & NC1 Flasher.
7. In Safestrap app - clicked on Install Recovery
8. NC1 app - Flashed and reboot.
9. Safestrap loads up.
10. Wipe Factory reset
11. Install I337_OC3_Stock_DeOdexed_ROM.zip
12. Install ATT_OC3_modules
13. Install I337_Stock_OC3_kernel_recovery_flashable and then reboot. Again AT&T logo sits for about 10 - 20 minutes and I do a battery pull.
14. Install Flash Fire and XposedInstaller_3.0_alpha4.apk
15. Flash xposed-v74-sdk21-arm.zip through Flash Fire.
16. The phone will sit at the AT&T logo for ever. I do a battery pull and still the same thing. Will not Boot up.
17. Battery Pull and go into Recovery Mode.
18. Wipe Clean and then Installed I337_OC3_Stock_DeOdexed_ROM.zip
19. I believe this is the time when it was able to restart the phone. Xposed work but got GASPS and GOOGLE not working.
I have also tried to install Xposed through Safestrap but I believe it didn't work.
I know this is long but I've finally been trying to keeps notes on what and how I've been doing this.
Can someone Please help me with this process?
You need to sdk22 version of xposed for the S4.
Sent from my SGH-I337 using XDA Free mobile app
Actually you need the unofficial xposed for tw, look here. http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463
Unless the official xposed works now, I haven't checked the thread lately.
I had the same problem. After some trial and error and many bootloops later, I found the right files. I've attached the ones I use. I use GoldenEye ROM, but it should work on OC3 Deodexed ROM too.
I have rooted my L8lite using Kingroot and it was successful (I think), but now I can't get rid of Kingroot if my life depended on it.
Things I have tried so far:
- Replacing Kingroot with SuperSU using the method described here: http://forum.xda-developers.com/p8lite/general/tutorial-how-to-root-bootloader-unlock-t3314786
- Replacing Kingroot with SuperSU using SuperSU-Me application from here: https://androidmtk.com/replace-kinguser-with-supersu
- Removing Kingroot using the option of SuperSU to remove other SU apps
- Uninstalling from Kingroot options menu
- Restoring a backup previously made using adb
- Factory reset
None of this worked. Please for the love of god someone tell me how to remove that piece of malware from my phone. I am frustrated beyond measure and extreme close to completely giving up.
Is my only option flashing? Would that help with removing Kingroot?
Thank you.
Update: I upgraded to Android 6.0 from local storage using an update I downloaded from Huawei's official website (http://forum.xda-developers.com/p8lite/general/rom-emui-4-0-android-6-0-single-sim-ale-t3360097). Kingroot is no longer there and Root checker app says the phone is no longer rooted. Curiously, SuperSU and SuperSU-Me are still there, but I removed them using app manager without hassle. Am I in the clear now?
Update 2: After rebooting using "adb reboot bootloader" command it seems that bootloader is still unlocked, which is good. Now I have to find a better way to unroot.
Getting rid of kingroot
Hey bujamin,
Kingroot is a powerful app and removing it without losing root is a near impossible task.
However, I have a solution, not a programmed flashable zip or something but just a way to get rid of Kingroot using existing tools.
My solution :
1. Use kingroot to root your device.
2. Get a custom recovery after you acquired root with KingRoot, preferably TWRP (bear with KingUser).
3. Open Kingroot and in Settings you will find an option to Remove Root authorisation or Uninstall kingroot (depending on the version). This will remove Kingroot completely and unroot your phone too.
4. Since, you have a custom recovery installed now, you no longer need Kingroot to acquire root access.
5. Get the latest SuperSu flashable zip from here.
6. Access the recovery and install the SuperSu zip that you downloaded.
7. A Success message and an option to reboot system will be shown.
8. Reboot.
SuperSu has now been installed and can be found in your app drawer. Your phone is now rooted.
Read my full thread (with detailed explanation) here and leave comments for further clarifications.
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 ?
Good afternoon,
After MUCH research, I have arrived at the conclusion rooting the D6616 with T-Mobile's likely final Z3 build for 5.0.2 (Build 23.1.C.0.399 and, really anything past KK) is no longer possible without involving Kingroot.
Why does this matter? Because there may not be a feasible way to remove the most recent builds of Kingroot from the D6616 ROM. Using Kingroot's own uninstaller in the App settings fails and factory resetting using the ROM/stock recovery threw my phone into a bootloop. Other users report it successfully factory reset their ROM with kingroot installed as a system app and their device no longer rooted. I attribute the variety of outcomes to different software builds and Kingroot versions.
It seems as though the only working root method also uses ZXDualRecovery. Though I have not tried it, all procedures that show the ZXDualRecovery method of pushing recovery and superSU involved rooting the device with Kingroot first and removing it after SuperSU is installed. This appears to be the only still-working method of acquiring temporary root long enough to install recovery. The only way to remove Kingroot is to use flashtool and a new Sony TFT, which also removes root and recovery.
Has anyone successfully been able to pull off rooting a D6616 lately? I want to keep this phone but it is unfortunately useless to me without working root so I'll likely be returning it if nobody still has one that's running the last software with a locked bootloader.
I would really appreciate any help anyone can give.
I believe I have done it! I think SuperSU is ever so slightly ahead of Kingroot.
What I did:
1) Rooted via Kingroot app on Google Play. Run rootchecker after it's done its business to make sure. DO NOTHING ELSE IN THE APP. Doing so may prevent SuperSU from kicking its ass later.
2) Downloaded and upacked to desktop the file for Xperia Z3 from here:
http://nut.xperia-files.com/path/XZD...ecovery_2.8.26
Z3-lockeddualrecovery2.8.26.-RELEASE.combined.zip
3) Disabled antivirus
4) Installed USB drivers via Windows 7 plug-n-play. Unplug phone.
5) Downloaded SuperSU recovery flashable zip from here:
http://www.supersu.com/download#zip
6) Ran install.bat from extracted ZXDualRecovery zip
7) Enabled developer options in phone, enabled USB debugging, revoked USB devices, rebooted phone, plug in phone.
8) Connect Phone, wait for device to register in windows.
9) Okayed communication from PC.
10) Place in USB Install Mode on phone.
11) Choose option 2 to install to device rooted by SuperUser. Kingroot has blocked option 1 (old method)
12) Enter TWRP (Automatic) and go to Backup, check all boxes, create Nandroid by sliding the slider
13) Reboot, ensure phone boots. Put SuperSU.zip on the external flash drive. Go to your new App: NDR Utils. Choose TWRP as Primary Recovery. Choose Reboot to Primary recovery
14) Flash zip for SuperSU. DO NOTHING ELSE. Do not wipe cache, do not fix permissions. Click REBOOT.
15) Launch SuperSU App. Attempt to update Binaries. It will not, but it will detect Kingroot, and somehow can get rid of it itself using onboard capabilities. It will do so and update binaries.
16) Reboot (Automatic via SuperSU)
17) Check to make sure SuperSU binaries installed by launching the app.
18) Reboot to recovery using the steps from step 13) above.
19) Create another backup using step 12) above
20) Reboot and DONE.
To the best of my knowledge, nobody has indicated how to do this in a clear Step-By-Step for the final build of this ROM. So because I've troubled you all for small chunks of the process I figured I would.
This applies to T-Mobile's likely-final software release for the Xperia Z3 android 5.0.2 on build 23.1.C.0.399.
DISCLAIMER TO ANYONE ATTEMPTING THIS: It appears Kingroot is "onto" what it is being used for. Given the behavior of this application, there is no reason for anyone to believe it is not a malicious program, but it is a necessary evil for this purpose. Newer versions of SuperSU are capable of removing Kingroot on their own, but alternative methods may be necessary. I attempted an earlier version of SuperSU and it was incapable of removing Kingroot.
It might remove via debloater. This is the only way to remove the system apps on this phone reliably, so you WILL need it if you intend to keep the bootloader locked. I couldn't get any root-enabled appstore app to do it including ES File explorer and Titanium Backup. It looks like you need a computer to remove system apps on this phone. Fantastic. Debloater works great though so don't be afraid to use it. Use the filter to search for Apps. You can remove them, but they will not be gone until you reboot your device. Hooray no more filecommander and lookout! Debloater can be found here:
https://forum.xda-developers.com/and...bloat-t2998294
Plug in your phone. Give it root access. Easy peezy.
Then Xposed current framework and installer:
https://forum.xda-developers.com/sho....php?t=3034811
Version 3.1.1 fixed the bootloop problem, so you shouldn't need the fix zip, or at least I didn't. But if you do, you can find it here:
https://dottech.org/187028/how-to-fi...-z5-z4-z3-tip/
Flash the framework for your device in recovery (arm) and then the installer APK from the ROM using a file browser.
FINALLY Youtube Adblock and minimized playback. SCORE!
I think that's about it. That's literally the best we can currently hope for from this device. I think there is an Xposed module to heavily alter the look of the ROM here but I have not tried it. Plus it only claims to work w/ 4.4, and we have 5.0.1.
https://forum.xda-developers.com/z3/...6#post71601966
For devicewide adblocking I use DNS66 since there are no proxy settings for adblocking on this device, unless I'm missing something. I really hope I am. This means there's no native adblocking.
Xposed modules worth using you can find by searching in the Xposed store: Blurred System UI (LP), Gravity Box [LP], RootCloak, Xperia/AOSP NavBar Buttons, Xperia Super Radio, YouTube AdAway, YouTube Background Playback. And of course DNS66 (PlayStore).
I have tinkered with the rest and find them of no value.
I followed the steps but SU didn't ask to update anything. It just opens up and everything is fine?
Then all I did was unistall kingroot(purify) and it looks like it's gone, but is it?
Just leaving this here, this is how I rooted on Android 5.0.2 with the D6616
http://nut.xperia-files.com/
Read the documentation that comes with the latest XZDualRecovery and flash SuperSU or whatever you want.
stef-nix said:
Just leaving this here, this is how I rooted on Android 5.0.2 with the D6616
http://nut.xperia-files.com/
Read the documentation that comes with the latest XZDualRecovery and flash SuperSU or whatever you want.
Click to expand...
Click to collapse
Were you able to install twrp without rooting first on your PC? It doesn't work for me. I did option 3, install on unrooted device.
Are you able to systemless root?
When I run the installation it fails at step 3 on the install bat.
Hi, a bit of an old thread, but has anyone had any success rooting the D6616 without using Kingoroot or Kingroot? Both are malware which are designed to not be fully removed and be as resilient as possible, and uninstall does not actually uninstall them...
Yes, the old method still works. Use the search feature. I'd just link you, but I"m busy at the moment.
i followed these steps, and have gotten to the point where you flash supersu and reboot, but i'm stuck in a reboot loop now. wanted to use this old z3 as a dedicated audio player, and needed to root for some audio enhancements...
edit: i did have TWRP for a minute, but now when i go into recovery it's the stock recovery again, with options only to continue booting, boot to safe mode, factory recovery or power down. the first two options return to a boot loop. can/should i attempt to use flashtool, or factory recovery? i don't want to accidentally wipe something i might need in the backup.\
UPDATE 10/19: I was able to get back to ground zero using Sony's xperia companion software repair. Flashtool 9.25 and 9.26 would never successfully install flashmode drivers, nor would it display the stock .ftf file.
fierogt42 said:
Yes, the old method still works. Use the search feature. I'd just link you, but I"m busy at the moment.
Click to expand...
Click to collapse
this new method seems to fail for me on both of my old z3's. does the method you're referring to involve downgrading to 4.4.4? i've done some extensive searching of this forum (and the android development ones as well) but don't seem to be able to find any other info.
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
.