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.
Hello!
I have spent around 5-6 hours tonight fixing my phone. Before it had CM13 working just fine but my recovery didn't work (got an error when trying to enter recovery). I manged to solve that problem by doing lots of things I have already forgotten about now and to be honest I didn't really have any idea what I was doing as I am very new to this and have no knowledge about it.
Right now my CM13 works just fine. No problems booting. My recovery works just fine. I have CAF bootstack and the latest TWRP recovery that was mentioned in the guide. However, my SuperSU doesn't want to work properly. At first, I had to download the SuperSu app from Play Store. I don't know if that's how it is supposed to be. When I start the app it says "The SU binary needs to be updated. Continue?". I press Continue and it says "If you have a custom recovery like TWRP or CWM, that can be used to (try to) install the SU binary. This is recommended for HTC devices. How would you like to install the SU binary?". I have two options: "NORMAL" and "TWRP/CWM". If I press "NORMAL" it proceeds to installing and the circle is spinning and spinning... "Installing, please wait..." After about 30 seconds it says "Installation failed! Please reboot and try again". Rebooting and trying again doesn't help. If I try the TWRP/CWM option it reboots me into TWRP Recovery but nothing happens there. If I reboot system from recovery the problem remains. I googled a bit and found some thread where they said I needed to download some SuperSU zip-file and install it from recovery. I did that but that just broke it even more giving me some error saying SuperSu wasn't installed at all, or something like that. I ended up re-rooting the device and installing bootstack, CM, and GAPPS again.
I have enabled root access in the CM developer options menu, for both apps and ADB. I have downloaded Root Checker and it says i am rooted. In download mode it also says rooted.
Is there some step I have missed? Please help me. I just want CM13, Recovery, and SuperSU to all be working at the same time. Not just pick two, like I have done before.
I had the same problem on my d802. That thing you did in development settings worked for me. Is supersu so neccesary?
Hi guys, I was able to root my G900V, unlock the boot loader into Developer mode, re-write the recovery with TWRP and install AICP custom rom. It was working great, I put Titanium Backup on my phone and it warned of an old version of SU. It recommended I upgrade SuperSU, so I installed the SuperSU app. When it came up of course it detected the same thing (old version of su) and recommended update. I have never used the TWRP/CWM method so again I tried Normal mode. It asked for access and I granted it, spent some time acting like something was happening then failed. I rebooted the phone and tried again -- same thing still failed.
Since I had TWRP installed, I thought I'd give the alternative flash a try. When I chose it, it booted into recovery and flashed a zip file. When it rebooted, it tried to bring up the OS and it hangs at the AICP logo. I can still get into recovery but the OS won't fire up. I'm not sure where to go from here, I think I can start over with ODIN but I'd rather know how to repair this situation (if it's possible) since I started to get the phone set up...
EDIT: By the way, the rom was the AICP Nightly from 12/30 and TWRP of 3.0.2-2.
Solved
I downloaded chainfire's latest SuperSU zip file: https://plus.google.com/+Chainfire/posts/WrCvex7KAZR and flashed it in TWRP. Got me rollin' again.
Hello everyone, I went to root my phone today, I used a Youtube tutorial with the exact links/downloads given. Followed the steps but my device is having trouble rebooting, it is just stuck on the Samsung logo flashing and I'm not too sure what to do. Also when it boots up I get the error message in the top left of my screen saying "Recovery Is Not Seandroid Enforcing", hopefully that helps.
Thanks.
Hipp0123 said:
Hello everyone, I went to root my phone today, I used a Youtube tutorial with the exact links/downloads given. Followed the steps but my device is having trouble rebooting, it is just stuck on the Samsung logo flashing and I'm not too sure what to do. Also when it boots up I get the error message in the top left of my screen saying "Recovery Is Not Seandroid Enforcing", hopefully that helps.
Thanks.
Click to expand...
Click to collapse
Hard to help if you do not write in detail. Such as phone type, links you have used, etc etc
Hipp0123 said:
Hello everyone, I went to root my phone today, I used a Youtube tutorial with the exact links/downloads given. Followed the steps but my device is having trouble rebooting, it is just stuck on the Samsung logo flashing and I'm not too sure what to do. Also when it boots up I get the error message in the top left of my screen saying "Recovery Is Not Seandroid Enforcing", hopefully that helps.
Thanks.
Click to expand...
Click to collapse
You need to flash SuperSU manually.
1. Flash TWRP
2. Format data
3. Flash SR3-SuperSU-v2.79-SR3-20170114223742.zip
http://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
You simply brick your phone. You need to know that there is not Chainfire-AUTO-Root for Nougat, so you need first flash Stock FIRMWARE from Sammobile, then flash TWRP and flash SuperSU
Or you can flash many of 100 roms with prerooted supersu and busybox.
Hi there,
After upgrading my S7 Edge G935F to stock version xxu1dqd7 (with latest May 2017 upgrades) I had to install TWRP (twrp-3.1.1-0-hero2lte.img) again.
Unfortunately this change will NOT recognise my pattern lock now! I had to re-install the stock image (DBT-G935FXXU1DQEF-20170523093738 with ODIN) using the HOME_CSC file to hold my data.
This re-installation brought me back to the game, but without TWRP and hope for root, but the pattern pin (the same) is now working...
Update 1
Installing TWRP (twrp-3.1.1-0-hero2lte.img) over the new stock image (DBT-G935FXXU1DQEF-20170523093738 with ODIN) without having the pattern lock enabled feature during start will result in stuck on
the samsung title.
Update 2
I had to repeat the step above (stock firmware), so stay now without root.
Will check later with other stock versions
>It seems you didn't format the data partition or dm-verity was not installed. Happened to me, won't boot if >anything is altered like when installing a custom recovery.
Yes, I did it with and without dm-verity, All 3 options,
TWRP (ok, but pattern lock will not recognized)
TWRP + supersu (2.82) (stuck on the samsung logo)
TWRP + supersu (2.82) + dm-verity (stuck on the samsung logo)
Yes, I didn'T format the data partition. Didn't want to lose my data ( Never had a problem to upgrade stock roms on my old S4 and root after).
Before the stock upgrade, I run with the Jan 2017 patch level (I bought this 2 days ago) and was able to root with the above method.
Today I wanted to jump the the latest stock version but run in trouble then.
Update 3
Downgrading to Stockrom from 2017-Jan-30 Germany 7 G935FXXU1DQB3 G935FDBT1DQA8 is not an option (anymore), The system boot up but with lot of errors and it's unresponsable and not usable.
Upgade then to the April patch status (2017-Apr-17 Germany 7 G935FXXU1DQD7 G935FDBT1DQD1) brought me back to operational,
but TWRP + supersu (2.82) + dm-verity (stuck on the samsung logo).
Will try it now with the Februar patch version
Downgrade to the Feb patch status (2017-Feb-23 Germany 7 G935FXXU1DQBX G935FOXJ1DQB2) had the same resut like the Jan version - not usable.
I'll give up now and install the April version without TWRP.
I need root to restore my apps AND data with Titanium Pro.
seppdep said:
Hi there,
After upgrading my S7 Edge G935F to stock version xxu1dqd7 (with latest May 2017 upgrades) I had to install TWRP (twrp-3.1.1-0-hero2lte.img) again.
Unfortunately this change will NOT recognise my pattern lock now! I had to re-install the stock image (DBT-G935FXXU1DQEF-20170523093738 with ODIN) using the HOME_CSC file to hold my data.
This re-installation brought me back to the game, but without TWRP and hope for root, but the pattern pin (the same) is now working...
Update 1
Installing TWRP (twrp-3.1.1-0-hero2lte.img) over the new stock image (DBT-G935FXXU1DQEF-20170523093738 with ODIN) without having the pattern lock enabled feature during start will result in stuck on
the samsung title.
Update 2
I had to repeat the step above (stock firmware), so stay now without root.
Will check later with other stock versions
>It seems you didn't format the data partition or dm-verity was not installed. Happened to me, won't boot if >anything is altered like when installing a custom recovery.
Yes, I did it with and without dm-verity, All 3 options,
TWRP (ok, but pattern lock will not recognized)
TWRP + supersu (2.82) (stuck on the samsung logo)
TWRP + supersu (2.82) + dm-verity (stuck on the samsung logo)
Yes, I didn'T format the data partition. Didn't want to lose my data ( Never had a problem to upgrade stock roms on my old S4 and root after).
Before the stock upgrade, I run with the Jan 2017 patch level (I bought this 2 days ago) and was able to root with the above method.
Today I wanted to jump the the latest stock version but run in trouble then.
Update 3
Downgrading to Stockrom from 2017-Jan-30 Germany 7 G935FXXU1DQB3 G935FDBT1DQA8 is not an option (anymore), The system boot up but with lot of errors and it's unresponsable and not usable.
Upgade then to the April patch status (2017-Apr-17 Germany 7 G935FXXU1DQD7 G935FDBT1DQD1) brought me back to operational,
but TWRP + supersu (2.82) + dm-verity (stuck on the samsung logo).
Will try it now with the Februar patch version
Downgrade to the Feb patch status (2017-Feb-23 Germany 7 G935FXXU1DQBX G935FOXJ1DQB2) had the same resut like the Jan version - not usable.
I'll give up now and install the April version without TWRP.
I need root to restore my apps AND data with Titanium Pro.
Click to expand...
Click to collapse
With the TWRP + supersu root method, no matter what 7.0 stock ROM you use, you will not succeed before you disable boot pin and format data. You can restore data after rooting.
So start with the latest stock ROM that is working 100% for you, flash twrp, format data, flash supersu, and it should work. You have to format data because root and stock rom currently does not work with encryption.
Or even simpler, use the new cf autoroot, however it seems you still have to format data.
I had high hopes that the new cf autoroot nougat binary would work with encryption, but alas it seems it doesnt, at least I had the same wrong pin code at boot issue as with twrp. I havent had time to test it, nor to format data and root, so I am currently not rooted.
doclorenzo said:
With the TWRP + supersu root method, no matter what 7.0 stock ROM you use, you will not succeed before you disable boot pin and format data. You can restore data after rooting.
So start with the latest stock ROM that is working 100% for you, flash twrp, format data, flash supersu, and it should work. You have to format data because root and stock rom currently does not work with encryption.
Or even simpler, use the new cf autoroot, however it seems you still have to format data.
I had high hopes that the new cf autoroot nougat binary would work with encryption, but alas it seems it doesnt, at least I had the same wrong pin code at boot issue as with twrp. I havent had time to test it, nor to format data and root, so I am currently not rooted.
Click to expand...
Click to collapse
Thank you doclorenzo.
I had success with the latest stock version (xxu1dqd7) and your recomendation to format data in TWRP.
In short: Boot in Download mode, Install TWRP via Odin, Boot into TWRP - format data, supersu (2.82) + dm-verity
and then restore all data. Unfortunately it requires lot of time (at least 4 hrs to restore the apps + more for fine tuning)
Thank you and hope to have a better way with the next stock update and TWRP
I've messed everything up and now I'm devastated!
My S8 stucks at the very first screen (where it says: SAMSUNG GALAXY S8 - powered by android). It doesn't boot further this very specific screen. I have tried to update Magisk and Magisk Manager but only Magisk Manager seems to get updated successfully while the app suddenly says that the latest version of Magisk Manager required Magisk V19.XX hence I've tried to install it via TWRP. According to log screen, I've managed to install magisk via TWRP but after booting up, I opened Magisk Manager where it now says that Magisk isn't installed. I therefore boot into TWRP and tried to fix it since some apps of mine that required root access wasn't working anymore. So, I thought I must have lost root access. I once again boot into recovery, I uninstalled magisk and install an older version of magisk and magisk manager and also the no_verity patch. After that my Galaxy S8 won't boot up. It just stucks at the very first screen. My S8 (international version) is still on Nougat stock samsung firmware and I can enter TWRP but the phone remains freeze and stubbornly refused to boot up.
I'm quite devastated and I hope you guys can help me fix this issue!
Thank you!
Hi, well sorry if I am stating the obvious but I would format and install one of the many custom roms available...
tosmaniac said:
Hi, well sorry if I am stating the obvious but I would format and install one of the many custom roms available...
Click to expand...
Click to collapse
Are there any solutions other than flashing a custom rom? Meanwhile, I have managed to flash Android 9 via ODIN and have TWRP installed but it won't boot up and stucks at the very first booting screens.
Any help would be appreciated!
Thanks!
cocolish said:
Are there any solutions other than flashing a custom rom? Meanwhile, I have managed to flash Android 9 via ODIN and have TWRP installed but it won't boot up and stucks at the very first booting screens.
Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
Have you tried just flashing stock rom only to see if it boots up. You may have to do a clean install.
Problem sounds like you haven't decrypted phone and flashed no verity zip file.
You won't need to flash a custom rom to fix this.
As for magisk have a look through this very helpful guide for installs and troubleshooting.
https://www.didgeridoohan.com/magisk/HomePage
I've managed to solve this issue by myself. But still, thank you so much! It's the thought that counts ? And yes, I've figured out that I haven't decrypt my S8. But everything is absolutely fine now and I feel extremely relieved. It took me 1 day to fix this major issue and I've encountered lots of difficulties while trying to fix this like bootloops, system won't boot up and managed to stuck at the very first booting screen again and the phone boot past the first booting screen and stucks at the second booting screen, and also bootloader error and stuffs like where realization hit me that I can't restore my nandroid backup while still on Nougat because after restoring it won't boot up. I therefore managed to flash Android 9 and twrp. My S8 is now on Android Pie with custom recovery and rooted (via Magisk).