Hi folks,
just posting this writeup thinking maybe it might be of help to some people.
Started with a clean S6 Edge straight from Samsung repair for broken screen. Factory wipe, KNOX reset. It had the PD2 update. Tried using Skipsoft's Toolkit and ponied up a donation to get the Pro version with the S6 Edge 6.0.1 update, but it didn't work: it got stuck at the "SEANDROID NOT ENFORCING" screen after flashing TWRP 3.0.2. I know there are issues with 3.0.2, but it's what's optioned in Toolkit now.
Flashing TWRP 2.8.7.0 results in normal boot, but I could not enter recovery mode for some reason. 3.0.0-0 didn't work, either.
What I ended up doing is forcing phone into download mode (Power+Volume Down+Home), ODINing TWRP 3.0.2-1. This resulted in a bootloop (somewhat expected). But I could get into recovery easily. From recovery, I flashed Renegade's PD2-Aroma V3.0 Full ROM via ADB sideload. After a very long first boot, everything works 100%! Root, SuperSU, etc., all taken care of. Hotspot works.
Notes and tips:
- While I didn't use Skipsoft's Toolkit in the end, it's still worth supporting. Might work smoothly using 3.0.2-1 instead of 3.0.2.0, but I'm comfortable with adb/fastboot/etc. so just ended up using that. If you don't already have Android SDK and tools/platform-tools, Skipsoft conveniently includes those commands in its directory under C:\Unified_Android_Toolkit (they're named adb-toolkit and fastboot-toolkit. You can copy and rename them as "adb" and "fastboot" for convenience).
- Make sure you get the right TWRP 3.0.2-1 device version. You want to use twrp-3.0.2-1-zeroltespr.tar.md5 for Sprint S6 Edge. Remove the .md5 part and set it to use the .tar extension (stupid Windows asks you to confirm file extension type change).
- In TWRP you can either push your custom ROM or sideload it. To push a file, move the custom ROM into the same directory you've got adb/fastboot for convenience. Open a terminal window in that directory, and either "adb push customromfilenamehere.zip /sdcard/" or in TWRP, click Advanced/ADB Sideload, and enter "adb sideload customromfilenamehere.zip".
- If you're sideloading it, it's gonna take a while, and will start flashing even while the transfer percentage is creeping up. Example: at around 9%, it started AROMA, around 14%, it went through some of the installation options. It was done flashing everything and ready for reboot even though the terminal window said only 76% was transferred. That's ok. Click "finish" in AROMA on phone, reboot. Unplug phone. Wait a long time for first boot (this took around 20 minutes for me). ENJOY.
Remember: all is not lost as long as you can get into download mode! Power-Volume Down-Home until you get to screen prompting to get to download mode. Volume up to select that mode. You can ODIN from here.
Additionally: if you find yourself for whatever reason stuck at the initial S6 Edge boot screen with "SEANDROID NOT ENFORCING," you might be in some kinda of boot limbo. I was able to issue some adb commands here, even with recovery was borked and the phone didn't boot all the way. Doing an "adb reboot-bootloader" would let me do a complete boot to ROM while I was trying to get the different TWRP versions working (until 3.0.2-1).
Hope this helps someone.
tl;dr: For PD2/6.0.1 Sprint S6 Edge, manual flash TWRP 3.0.2-1. Push custom ROM through Recovery. Reboot, wait a long time. Success!
Just to Clarify (and mostly for myself), I think this is the simplest and most foolproof way to get yourself fully update and on a custom rom with root.
1. ODIN Stock PD2 Image. Reboot, make sure dev options + USB debugging is enabled.
2. ODIN latest TWRP 3.0.2.1 - HERE.
3. Obtain root by going into TWRP immediately after you install it and flashing the root kernel Ram did for this device - HERE
4. Then after wiping cache, dalvik and data in TWRP, flash Renegade ROM 3.0 PD2.
Using CFauto root method is known to cause issues. This is the type of approach I took and it was flawless. The initial boot of the Renegade ROM can seriously take like 20min though, I thought I was looping for a second.
If anyone disagrees with this method or sees where it can be done better, please advise. This seems to prevent the instance of any loops or issues. The Renegade ROM has a rooted kernel so flashing the root kernel is likely a redundant step. You could omit Step 3 if you are flashing a custom ROM, probably, but it seems to prevent any hangups. But if you plan to stay stock, you still have to flash a rooted kernel after TWRP.
Alpine- said:
Just to Clarify (and mostly for myself), I think this is the simplest and most foolproof way to get yourself fully update and on a custom rom with root.
1. ODIN Stock PD2 Image. Reboot, make sure dev options + USB debugging is enabled.
2. ODIN Ram's TWRP 3.0.2 - HERE I'm assuming the other guy's 3.0.2 works fine too, I am not sure why you hung and had to revert to a 2.x TWRP build.
3. Obtain root by going into TWRP immediately after you install it and flashing the root kernel Ram did for this device - HERE
4. Then after wiping cache, dalvik and data in TWRP, flash Renegade ROM 3.0 PD2.
Using CFauto root method is known to cause issues. This is the type of approach I took and it was flawless. The initial boot of the Renegade ROM can seriously take like 20min though, I thought I was looping for a second.
If anyone disagrees with this method or sees where it can be done better, please advise. This seems to prevent the instance of any loops or issues. The Renegade ROM has a rooted kernel so flashing the root kernel is likely a redundant step. You could omit Step 3 if you are flashing a custom ROM, probably, but it seems to prevent any hangups. But if you plan to stay stock, you still have to flash a rooted kernel after TWRP.
Click to expand...
Click to collapse
I noticed chainfire now has a CF-autoroot for the 925P 6.01 and people were having success using the one for the 925F. Any verification on this? Haven't seen anyone on this forum say anything about it. I just bought a new S6 edge for sprint. I always am about year behind on phones because of the high cost of the latest and greatest. I picked the edge because my wife has had one a year and it gets a lot better reception than my N5. But, I gots to have root and don't wanna screw up a new phone. I know the first thing I need to do is check which software it's running. Should I do this before I activate it or can i stop any system upgrades before they install?
baknblack said:
I noticed chainfire now has a CF-autoroot for the 925P 6.01 and people were having success using the one for the 925F. Any verification on this? Haven't seen anyone on this forum say anything about it. I just bought a new S6 edge for sprint. I always am about year behind on phones because of the high cost of the latest and greatest. I picked the edge because my wife has had one a year and it gets a lot better reception than my N5. But, I gots to have root and don't wanna screw up a new phone. I know the first thing I need to do is check which software it's running. Should I do this before I activate it or can i stop any system upgrades before they install?
Click to expand...
Click to collapse
I have not attempted to use CF-autoroot just because of reported issues and the general recommendation being to use the standard method. It may work fine now that its been updated, but I have not personally tested it.
Alpine- said:
I have not attempted to use CF-autoroot just because of reported issues and the general recommendation being to use the standard method. It may work fine now that its been updated, but I have not personally tested it.
Click to expand...
Click to collapse
I just bought my phone new off ebay it updated to PF4 just as soon as I activated it. I couldn't stop it. Anyway I used the CF autoroot on it and it worked perfectly. I tried to do it manually a couple times first and never could get TWRP to flash. It would say it was successful but, stock recovery stayed. Anyways, I got er done and running Renegade wich btw is an awesome ROM. This is my first samsung device and had I done a bit more research I'd of known the majority of development is on the regular S6. I just picked the edge because my wife has one and it worked so much better in the boonies than my N5 did.
baknblack said:
I just bought my phone new off ebay it updated to PF4 just as soon as I activated it. I couldn't stop it. Anyway I used the CF autoroot on it and it worked perfectly. I tried to do it manually a couple times first and never could get TWRP to flash. It would say it was successful but, stock recovery stayed. Anyways, I got er done and running Renegade wich btw is an awesome ROM. This is my first samsung device and had I done a bit more research I'd of known the majority of development is on the regular S6. I just picked the edge because my wife has one and it worked so much better in the boonies than my N5 did.
Click to expand...
Click to collapse
Edge is better imo, certainly looks better. All you need is Renegade rom anyway. May be a few more roms in active dev for s6 but nothing better per se. Renegade rom dev is alive and well.
Would these root methods trip knox?
chen69chuck said:
Would these root methods trip knox?
Click to expand...
Click to collapse
Yes
Thanks.
Working for g920v 6.0.1?
freaking thank you been struggling with twrp on and off for two days trying to bring this phone back from the dead! YOU the man
Hey all,
I'm trying to root my phone and I keep running into issues.
I followed this thread https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
and when it comes to the flashing recovery section, I keep ending up in Qualcom crash dump.
I took the advice on another thread and tried using Blu-spark 9.8.6.
Whilst that booted into temp recovery, everything was encrypted and illegible, so I couldn't do anything.
I am on Pie, stock ROM.
How can I get this phone rooted? I was hoping to install xXx.
What info do you need to help me?
Thanks in advance.
EDIT: To be a little clearer, when it boots in temp recovery, it asks me for a password to decrypt the data. I've tried all passwords I know, non work. Hence why it is encrypted.
Even if I work out how to get past the encryption stage, how do I know I won't run into other issues?
Is there a guaranteed root and recovery method for Pie?
EDIT EDIT: Worked it out. I had to turn off security settings. No ****.
Hopefully I don't tun into any more issues. About to flash Magisk.
Ok, phone booted up fine and seems to be rooted with magisk.
One last question.
xXx says that I must have TWRP to flash. I do have TWRP, but it is Blu spark version.
Does that matter?
EDIT: Flashing ROM now. Hopefully all is well.
Thanks anyone who was going to reply to my initial question. Everything seems to be working.
I’ll make this short.
I was successfully rooted. But I couldn’t update to 9.5.6.
I updated but it keeps failing. I switch to slot A and I was on 9.5.6 but WiFi didn’t work and apps would crash randomly, and it was laggy. I would go back to slot b and WiFi worked and everything was great but I’m on 9.5.3. And I would try to update again and it would fail and sometimes I would have to have in fastboot and reflash twrp to reboot to restore. I restored the device multiple times, removed root but it still happens. I used to always use android but I was on iOS for years and I’m used to jailbreaking and Apple IOS. Please help me. How can I restore and start from scratch? Or how can I fix this? It’s very annoying. I have my info backed up so I don’t care what I have to do. I love this phone but I had the Verizon iPhone bug when people call me and I answer it fails on there end. Or else I would deal with 9.5.3. All help is greatly appreciated.
You need to read the threads better, it's already been explained that wifi can end up being disabled because the rooted boot.img is older than your current rom version. Flashing one of the kernels available usually fixes this. You can also extract the boot image from the rom you downloaded and patch that boot.img file using Magisk, then when you apply that everything should work correctly.
From reading your post it would appear you're on T-Mobile (US) so you would need to download the 9.5.6 package and then extract the boot.img, then patch that using Magisk and push it to the phone using fastboot, once you reboot everything should be rooted and working.
I have the ZTE 2050 which has the MT6771 chipset. It seems to well developed in Russia for some reason. The rest of the world hasn't really done much with it. After several battles with root and recovery, I finally got them both to stick. I downgraded the phone from Android 10 to the earlier Android 9 and have TWRP 3.4.0. Still have issues though. As soon as TWRP starts, it ask me for a password. I have tried using no dm verity force encrypt.zip, and I have a patched boot.img from Magisk. When I flash the no dm zip, the phone stays stuck on the boot screen. And the one time it it finally passed that screen, the phone told me the phone could not be decrypted. Another issue is that when I open my root file explorer and try to alter, copy, or do anything within that file system, the phone freezes and needs to be rebooted. I can use Magisk modules to do certain things, but not all that I am trying to do is made into modules. Even simple things like adding to my build.prop. Also, after debloating, when I try to open and read any file, no matter what file manager I use it tells me that my web viewer is no longer installed even though it is. Can anyone tell me what I may possibly be doing wrong in all of these situations? Thanks in advance.
I'm using a Galaxy watch 4 Classic for a month now and it has been working perfectly fine. But the only issue I'm facing is unable to quickly reconnect after my phone restarts. I have to repeat the long first-time connection procedure (which has got quite frustrating TBH). I even have to do this when I turn on Flight Mode on my phone. I know it is not how it is supposed to act normally but I believe there must be some solution to this.
It seems to be something wrong with my Samsung Wearables app. It does not seem to remember any device after a restart.
Also to mention, my phone is rooted if that is causing this.
It is indeed your root that's causing this problem
Install the Bluetooth Library patcher via Magisk or TWRP (whichever you prefer) from here:
https://github.com/3arthur6/BluetoothLibraryPatcher/releases/tag/v2.4.1
And this problem should go away. Reboot and re-pair your device. Should remember them afterwards.
I tried to install the Bluetooth patch file but, the root manager I have installed "EFTSU Manager", does not open any of the Bluetooth patch files I downloaded. I installed Magsik but it does not seem to work on this device. Also my device boots normally. No TWRP from where I can install packages.
Please guide me on how I should make this work... If any additional details are required, ask ill provide them.
If not Top Secret...
Why not tell Model Name of your Phone...
Samsung not Samsung?
For instance I fixed this ugly issue on my Samsung SM-A202F rooted with Magisk...
Best Regards
Here my "Diary"...
Firmware and Combination Firmware and FOTA Delta and CSC change and...
Looks like it could be harder since Tizen... A Stock Firmware for netOdin/Odin not available yet... B Combination Firmware not available yet C FOTA Delta File for study I have...
forum.xda-developers.com
IMHO only fixed after FukKkKtory Reset Watch again.
Best Regards
Skipping f%$ing useless Intro by tap tap few times on Screen.
This is since Tizen totally stupid feature because in earlier Tizen firmware Intro asked for skip...
Seems Samsung loves to torture user by stupid tasks.
Best Regards
adfree said:
If not Top Secret...
Why not tell Model Name of your Phone...
Samsung not Samsung?
For instance I fixed this ugly issue on my Samsung SM-A202F rooted with Magisk...
Best Regards
Click to expand...
Click to collapse
My Device is Samsung Galaxy S9 SM-G960F. I guess it is not rooted with magisk because magisk app wont work on this device.
ShaDisNX255 said:
It is indeed your root that's causing this problem
Install the Bluetooth Library patcher via Magisk or TWRP (whichever you prefer)
Click to expand...
Click to collapse
As you told, i tried to install the patch file using Magisk for which i installed Magisk. But it did not seem to work. Have a look at the screenshots from the app and log.
What should i do now.