I'm a veteran at rooting android phones, but this is the first phone where TouchWiz roms won't boot after installing SuperSu. How do I root my stock rom(my phone has twrp installed), or install a custom TouchWiz rom(that automatically installs SuperSu) without bootlooping?
Sent from my SM-G900T using Tapatalk
Flashing SuperSU from TWRP should work, is that where it is bootlooping?
Make sure to say NO if TWRP asks if you want it to root the phone for you after flashing SuperSU or that will cause problems, you only need flash SuperSU, and then refuse the next request if asked
There is also CF Auto Root, this is for flashing with ODIN
G900T CF AR
http://download.chainfire.eu/407/CF-Root1/CF-Auto-Root-kltetmo-kltetmo-smg900t.zip
hope i am not violating any forum rules here, as i know how strict they can be. I am not a noob in this area, ive rooted and flashed all my phones since my droid x on. I miss my s-off HTC so bad. I did 5 minutes of research and thought all Galaxy S7s were bootloader/recovery unlockable...only to find out the american versions arent after im stuck with s Sprint SM-G930P. I was able to root and install xposed with the engineer boot.img and odin. Since TWRP or recovery isnt an option I have tried for months to systemless root this thing to hide root and pass safetynet. Ive tried flashfire to flash SU systemless 2.78SR5 and root switch and am on android 6.0.1 PE1 firmware following guides here: https://forum.xda-developers.com/sprint-galaxy-s7/how-to/sm-g930p-root-t3410604 but after factory reseting and trying Rootswitch (will hide exposed but not root with flashfire installing it since bootloader lock doesnt allow TWRP) I piddled with magisk but I am not on the Equinox unlockable s7 and am just at a loss here. Any one out there know of a way to hide root with this version of S7? Im out of ideas and any help here is appreciated. When i flashfire Supersu i get the locked out modified boot img error, but selecting AP and flashing the engineer boot img will get me back up rooted but root switch is a no go. I can use buildprop/rootzwitch to set selinux permissive sstatus but still fail. I refuse to let samsung not let me root my phone properly. I ser xposed modules like snorlax being updated so there seems to be a way to use xposed modules in PoGo while hiding root/xpised but every guide i see leads to TWRP instructions. Can i adb/terminal install magisk/rootswitch? and stiil use modules? (Cart before the horse question seeing as right now i cant bypass safetynet.) HELP!!
Have you made any more progress with this by chance?
Hi,
is there a way to root the G935F with CF Autoroot after updating to nougat?
I did try the existing CF Autoroot file from the website - but that ended up in boot loop. I wiped data and system and the system bootet, but I didn't have wifi.
So I flashed again and rooted successfully with TWRP + SuperSU, but I think I lost encryption on the way. Before I had Android 6 with stock Rom + CF Autoroot, which kept encryption, I'd like that for Android 7 as well, is that possible, or not yet?
thanks
Catscrash said:
Hi,
is there a way to root the G935F with CF Autoroot after updating to nougat?
I rooted successfully with TWRP + SuperSU, but I think I lost encryption on the way. Before I had Android 6 with stock Rom + CF Autoroot, which kept encryption, I'd like that for Android 7 as well, is that possible, or not yet?
thanks
Click to expand...
Click to collapse
I can 100% confirm it is not yet possible. The current cf-autoroot only works with Marshmallow, and using it on a Nougat device will soft-brick your phone (I learned this the hard way).
The only other working method I'm aware of is flashing SuperSU through TWRP, at least until the cf-autoroot devs release a new version that works on Nougat.
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'm about to provision my One Plus 5 for use I will be running it with TWRP a unencrypted data partition (makes restores easier) and root via Magisk day one.
I'm curious if I'm running it in this configuration when an OTA comes down the pipe will it do any of the following?
re apply fastboot oem lock?
flash the recovery to stock recovery?
remove magisk?
re-enable dm-verity?
Curious if the process after an OTA apply is to re-flash TWRP potentially re-apply magisk? Does applying ota mess with your data partition if you already decrypted it?
Also was thinking about leaving the data partition decrypted so I can push things to it via ADB or manipulate it when it's in a non-functional state can anyone here comment on if that's still possible while encrypted? And if so what dis-advantages of leaving it encrypted I hear one is you have to remove the lock screen password before you create a backup since the keys are not backed up and you might be locked out after a restore.
With some more research I've answered my own question I'll put them here in case anyone wants to refer to them in the future.
TWRP users will lose TWRP after a flash of the OTA.
Root will be lost regardless if you flash using TWRP or stock.
Data is not touched during flash so it should stay as is.
DM-verity requirement is unknown.
For rooted users it's better to do a full flash with TWRP OTA through TWRP will cause a problem.
Actually, you won't get the small incremental OTA, you will download the complete 1.5 - 2gb rom... This happens when you have root whether you have got TWRP or stock recovery.
Root will always be lost, yes but if you flash with TWRP you can flash magisk oe SuperSU immediately afterwards to gain root again. Not having TWRP you will need to either boot TWRP or install it to install root again.
DM-Verity, I have never had any problems with this after flashing and then rooting...
I dirty flash the 4.5.10 and i had to reflash the ROM + no_verity_op5.zip. My first and only issue was a sort of bootlop to the recovery.
So wait. If I flash the OTA, then flash Magisk, I will have root and lose TWRP, right?
Then could I use some app like Flashify or the TWRP app to install the recovery?
I don't own a PC right now and want to know if it's possible.