Just installed Nougat stock ROM for my S7 Edge with ODIN, and trying to root.
I installed TWRP latest version 3.01 and immediately after installed supersu 2.79 SR3 from TWRP.
At first I could not boot the phone because it kept saying I used the wrong PIN code for boot. I reflashed stock rom and was able to boot again (same PIN) - disabled PIN on boot, and reflashed TWRP and supersu, but it keeps hanging at the Samsung Logo.
Flashing stock rom solves it, but I still want to root it..
What am I doing wrong?
currently there is no reliable root for nouget roms. It is being worked on.
Cosmic Blue said:
currently there is no reliable root for nouget roms. It is being worked on.
Click to expand...
Click to collapse
Thanks for replying.
In this case - even if the goal is to root - it seems the problem is with TWRP.. Even if I do not root, but just install TWRP, the neverending bootlogo shows up..
Nougat OS has been changed that all the old rooting and twrp need to be updated.
It will be a while till developers can modify the os to allow changes.
Have posted the same question in the TWRP S7 thread that I did not see before posting this one - sorry
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 am hoping I can bounce my plan of attack for updating my Pixel 2 XL that is already rooted (using Magisk Manager + Magisk) and currently running Magisk Manager 5.6.4 + Magisk v16.0 and Android 8.1 (build OPM1.171019.021) to the latest and greatest version of Android (looks like its currently v9.0 w/ build# PQ1A.181105.017.A1)
First off, I didn't use TWRP when originally rooting android v8.1 on my Pixel 2 XL previously, I didn't think I needed it and had no plan to ever install a custom ROM. I am still in this boat and would prefer not to install or use TWRP if possible. I went the route letting the magisk manager app on my phone update the (at that time) newest factory image of android then flashing that image back onto my phone via fastboot and everything went great.
Anyway - If anyone would look over my approach here and let me know if this should work or not I would appreciate it!
My plan for updating to android 9.0 and keeping root:
1. Download the last android factory image from google (currently PQ1A.181105.017.A1)
2. Backup everything on my phone I care about (pictures, etc)
3. Use fastboot to flash the latest factory image to my phone (I understand this will reset everything on my phone and I'll lose root for the time being)
4. Download magisk manager apk from ******************
5. Make sure my phone is setup to allow installation of apps from unknown sources, then install magisk manager on my phone
6. Use Magisk Manager to install magisk and use the option to "patch boot image file" to patch the boot.img file from the latest factory android image (currently PQ1A.181105.017.A1)
7. Use flashboot to flash the patched version of the latest factory android image (currently PQ1A.181105.017.A1) to my phone, then finally check that root is working by using Magisk Manager. Then restore my backed up files to my phone (e.g pictures)
Thanks in advance for the advice!
I'm rooted with magisk, i took the ota, knowing full well it wasn't going to complete while I'm rooted. Haha me... It took. Didn't lose a thing except root. 10 minutes later, I'm rooted on pie. No issues for me.
As for twrp, you don't flash it, you boot it. It runs until you reboot. I turn off security on the phone before I re- boot into the bootloader. Twrp did or still does have an issue with patterns. Otherwise it works great for my needs.
After a painful rooting process, I finally achieved root with Magisk 19.1 and unlocked bootloader. I decided to load Super V20 ROM this morning but it has never finished the boot process. It's sticking on the Verizon boot animation. As far as the stock phone, I had version VS99510B and Android 7.0, running TWRP 3.2.1-0. When I went through the options in the Aroma loader for Super ROM, I don't think I chose anything crazy. I selected Magisk & MK2000 kernel (though, that didn't have any effect on the static screen; I was told it would).
After the first load attempt, I went back into TWRP, triple-wiped everything and reflashed again. Same effect. It just won't move past the Verizon boot animation. What could be the issue? Is there anything I can fix here or do I need to reload all the stock software? If that is the case, do I need to go back to 10B or would a newer version work better? I do intend to load a custom ROM at some point but I just want to get this phone functioning again.
Right now, I do have access to recovery (TWRP 3.2.1-0) so all is not lost. Got any help?
Thanks all.
LG V20 VS995, attempting Super V20 4.1 (8.2.18), Magisk 19.1, TWRP 3.2.1-0
Galaxy S8 Exynos [SM-G950FD] Android Oreo 8.0.0
Hello. it's my first time posting here. So I've had a successful attempt at flashing TWRP and Magisk into my phone. Today I accidentally plugged in my charger while it was in the process of rebooting, so it entered my device into kind of a bootloop. I solved this by going into Download Mode and pressing 'Cancel', which prompted my device to successfully reboot and work again.
The problem is that I've somehow lost my root. None of my apps can get root access, CPU-Z says no root available, and Magisk Manager said "Magisk is not installed". Idk how I got to this because yesterday all was working, I assume it's because I got a bootloop or went into Download Mode.
I tried to install the official Magisk ZIP file from the Manager, go into recovery mode, and flash it via TWRP. Unfortunately this didn't work. This is the only solution I can come up with besides reflashing Stock and having to flash Magisk again and wipe all my current data. If anyone has any suggestions please comment down below as I'm kinda stuck rn. They would be greatly appreaciated!