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
Okay, so I rooted my Mi A1 with the help of Dhananjay Bhosale's video uploaded today.
Everything worked fine until I discovered that I couldn't install OTA updates. Pretty common thing for rooted devices (although somewhat disappointing). But the weird thing is, I was on the September security patch while installing this update but then when I booted into the system after everything was done and dusted, a notification showed that the system was finishing up with installing the August update and that the September update was still to be downloaded and installed. So I did that but the system failed to install it.
Then I checked XDA and Dhananjay, in his XDA account, has suggested that OTA updates could be installed by switching partitions (new thing in Android N). So I did that, redownloaded the September patch and everything installed just fine but then I realized that there were no root privileges in this particular partition. After some effort, I somehow re-entered recovery and switched back to the other partition, hoping that the update would stick. But it didn't. As soon as I rebooted back into system, there was that notification again (finishing up the August update and telling me to download the September patch).
So basically, I am back to square one.
Anyone knows how to break out of this vicious circle?
anirbannath said:
Okay, so I rooted my Mi A1 with the help of Dhananjay Bhosale's video uploaded today.
Everything worked fine until I discovered that I couldn't install OTA updates. Pretty common thing for rooted devices (although somewhat disappointing). But the weird thing is, I was on the September security patch while installing this update but then when I booted into the system after everything was done and dusted, a notification showed that the system was finishing up with installing the August update and that the September update was still to be downloaded and installed. So I did that but the system failed to install it.
Then I checked XDA and Dhananjay, in his XDA account, has suggested that OTA updates could be installed by switching partitions (new thing in Android N). So I did that, redownloaded the September patch and everything installed just fine but then I realized that there were no root privileges in this particular partition. After some effort, I somehow re-entered recovery and switched back to the other partition, hoping that the update would stick. But it didn't. As soon as I rebooted back into system, there was that notification again (finishing up the August update and telling me to download the September patch).
So basically, I am back to square one.
Anyone knows how to break out of this vicious circle?
Click to expand...
Click to collapse
Similar with me, I have Sep build in slot A and Aug build in slot B. I'm not able to install the Oct build.
sunshinebhushan said:
Similar with me, I have Sep build in slot A and Aug build in slot B. I'm not able to install the Oct build.
Click to expand...
Click to collapse
mine also any sol to fix this?
Steps to fix any root mess-up that might happened and/or corrupt system from tampering with files.
1. Follow this guide, you can start from the flashing part
2. Download the mi flash app + a1 fastboot stock rom
3. Flash using the guide, make sure you select 'save user data'! or you will lose all your data!!
4. Once the flashing is complete you will reboot into the august patch, go to updates and install all the updates as usual
5. Root/Flash recovery using your favorite method.
I played around the system partition too much and had some issues with play services, also I couldn't update to october patch, after doing the above, everything works great. just use this guide anytime you want a clean slate.
Also always backup everything on twrp, always a useful thing to do.
Good luck
I didn't have any such problem. This is what I did: I was on Sep patch on 'b' rooted with magisk --> installed Oct ota update --> rebooted --> rebooted to twrp, flashed magisk 13.4. and rebooted to system --> everything works.
BTW how did you get root; CF-auto root or Magisk?
Ex-Hunter said:
I didn't have any such problem. This is what I did: I was on Sep patch on 'b' rooted with magisk --> installed Oct ota update --> rebooted --> rebooted to twrp, flashed magisk 13.4. and rebooted to system --> everything works.
BTW how did you get root; CF-auto root or Magisk?
Click to expand...
Click to collapse
I used AIO tool with patched boot.img then flashfire for SuperSu.
For me, the oct update is not getting installed at the first place
sunshinebhushan said:
I used AIO tool with patched boot.img then flashfire for SuperSu.
For me, the oct update is not getting installed at the first place
Click to expand...
Click to collapse
The AIO tool uses CF root. Normally you FlashFire would be able to capture the OTA update and flash it but some have reported that it's not happening for our device. IMO you can do one of the two things.
You can do what @sooti suggested till step 4 and then root using Magisk and TWRP. Refer here.
Or
You can find which partition has sep update installed; reboot to it and unroot SuperSU; flash stock sep boot.img and install oct OTA update. After that follow this to get root.
BTW you don't need to flash TWRP; just boot to it and flash Magisk to get root.
Ex-Hunter said:
I didn't have any such problem. This is what I did: I was on Sep patch on 'b' rooted with magisk --> installed Oct ota update --> rebooted --> rebooted to twrp, flashed magisk 13.4. and rebooted to system --> everything works.
BTW how did you get root; CF-auto root or Magisk?
Click to expand...
Click to collapse
Hi. As I mentioned, I am not even on the September patch. I used to be but then I rooted it today (installed Magisk) and suddenly I'm back to the August patch. September patch only installs in 'a', which is not rooted. That doesn't really serve my purpose.
Ex-Hunter said:
The AIO tool uses CF root. Normally you FlashFire would be able to capture the OTA update and flash it but some have reported that it's not happening for our device. IMO you can do one of the two things.
You can do what @sooti suggested till step 4 and then root using Magisk and TWRP. Refer here.
Or
You can find which partition has sep update installed; reboot to it and unroot SuperSU; flash stock sep boot.img and install oct OTA update. After that follow this to get root.
BTW you don't need to flash TWRP; just boot to it and flash Magisk to get root.
Click to expand...
Click to collapse
Hi. There seems to be a problem with what you suggest. The video I followed does almost the same thing. I even have TWRP, along with Magisk of course. The problem is, when I boot to 'a' (the partition that successfully installs the September update), I find that it isn't rooted. Magisk is inactive. And root checker says that root isn't properly installed. So obviously, the question of unrooting is rendered moot.
I want to be able to install the OTA update in my rooted partition and make it stick. People have installed OTA updates to rooted ROMs (mostly using FlashFire), but Flash Fire is giving me an unusual error, something about being unable to install OTA even though it has detected it due to being unable to find some files in boot/recovery folder or something like that.
@anirbannath
Just to be clear, when you reboot to system which partition and which patch are you in?
Ex-Hunter said:
@anirbannath
Just to be clear, when you reboot to system which partition and which patch are you in?
Click to expand...
Click to collapse
@Ex-Hunter
I think I should update a little bit : I tried rooting both the partitions and what I saw was that I am on September patch on both of them now. However, the problem still persists albeit in a slightly different manner. Currently I am on partition 'a' because the WiFi is having some weird problems in partition 'b'. So now I have the update notification for the October security patch but after downloading, the system gets stuck on Step 1 of 2 of installing the update. I guess, side-effect of rooting. But this isn't the issue.
I found out that the real problem is the FlashFire app. Since I have downloaded the October patch and rooted both partitions, I had hoped that FlashFire would work now, but that same error persists (which is something like Update Engine binaries could not be found, so update cannot be handled - I have asked a separate question about that, if you would be so kind as to go to my profile and check it out).
I got bootloop when installing october security patch......
I have unlocked bootloader and also rooted my phone using CF-auto-root but when try to install october security update after reboot my phone got bootloop.....
So, what do i do now ?
anirbannath said:
@Ex-Hunter
I think I should update a little bit : I tried rooting both the partitions and what I saw was that I am on September patch on both of them now. However, the problem still persists albeit in a slightly different manner. Currently I am on partition 'a' because the WiFi is having some weird problems in partition 'b'. So now I have the update notification for the October security patch but after downloading, the system gets stuck on Step 1 of 2 of installing the update. I guess, side-effect of rooting. But this isn't the issue.
I found out that the real problem is the FlashFire app. Since I have downloaded the October patch and rooted both partitions, I had hoped that FlashFire would work now, but that same error persists (which is something like Update Engine binaries could not be found, so update cannot be handled - I have asked a separate question about that, if you would be so kind as to go to my profile and check it out).
Click to expand...
Click to collapse
Thanks for clarifying. It is interesting that you are on Sep patch on both the partitions. IMO the sure shot way of solving your problem would be to go back to stock and root using Magisk.
Follow the "Flashing Guide for Fastboot Update"guide. Download the Sep fastboot rom for Step 2; Select 'clean all' for Step 5 but do note that it will wipe all user data. Now you will be on stock sep rom on slot a. You'll get OTA notification for the Oct patch, go ahead and install. After rebooting you will be on stock oct rom on slot b.
After finishing, download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Go to fastboot mode and verify that you're unlocked and all drivers are installed.
While in fastboot type
Code:
fastboot getvar all
You can see which slot is active.
I suggest you NOT to flash TWRP but boot to it instead.
To do so type
Code:
fastboot boot recovery.img
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; Press vol down button and connect the USB. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP.
Reboot to system
Download the latest Magisk Manager and install. DO NOT update Magisk.
Download and install as usual when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Ex-Hunter said:
The AIO tool uses CF root. Normally you FlashFire would be able to capture the OTA update and flash it but some have reported that it's not happening for our device. IMO you can do one of the two things.
You can do what @sooti suggested till step 4 and then root using Magisk and TWRP. Refer here.
Or
You can find which partition has sep update installed; reboot to it and unroot SuperSU; flash stock sep boot.img and install oct OTA update. After that follow this to get root.
BTW you don't need to flash TWRP; just boot to it and flash Magisk to get root.
Click to expand...
Click to collapse
I followed the steps you mentioned, all went well thanks for that. But couldn't edit build.prop with this root method tried with ES explorer (previously with CF root it was successful)
sunshinebhushan said:
I followed the steps you mentioned, all went well thanks for that. But couldn't edit build.prop with this root method tried with ES explorer (previously with CF root it was successful)
Click to expand...
Click to collapse
Go to Magisk Manager>Menu>Superuser; Check if the switch is ON for ES explorer.
You can also try Amaze file manager. Its completely FOSS. Go to Amaze>menu>Settings>Root Explorer and switch ON.
Edit: BTW you're not editing build.prop directly,are you? You can't do that for systemless root.
Ex-Hunter said:
Go to Magisk Manager>Menu>Superuser; Check if the switch is ON for ES explorer.
You can also try Amaze file manager. Its completely FOSS. Go to Amaze>menu>Settings>Root Explorer and switch ON.
Edit: BTW you're not editing build.prop directly,are you? You can't do that for systemless root.
Click to expand...
Click to collapse
I am trying to edit directly, what is the other way to edit?
sunshinebhushan said:
I am trying to edit directly, what is the other way to edit?
Click to expand...
Click to collapse
You've to use resetprop tool for that. You can modify an existing module or put a script at /magisk/.core/service.d (I think.... haven't done that in a long while). You can ask magisk related queries here (unofficial magisk 13.4) or here (official)
Ex-Hunter said:
Thanks for clarifying. It is interesting that you are on Sep patch on both the partitions. IMO the sure shot way of solving your problem would be to go back to stock and root using Magisk.
Follow the "Flashing Guide for Fastboot Update"guide. Download the Sep fastboot rom for Step 2; Select 'clean all' for Step 5 but do note that it will wipe all user data. Now you will be on stock sep rom on slot a. You'll get OTA notification for the Oct patch, go ahead and install. After rebooting you will be on stock oct rom on slot b.
After finishing, download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Go to fastboot mode and verify that you're unlocked and all drivers are installed.
While in fastboot type
You can see which slot is active.
I suggest you NOT to flash TWRP but boot to it instead.
To do so type
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; Press vol down button and connect the USB. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP.
Reboot to system
Download the latest Magisk Manager and install. DO NOT update Magisk.
Download and install as usual when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Click to expand...
Click to collapse
I have updated magisk in Mi 1 and now I am not able to boot my mobile...it just restart and also not able to boot into TWRP...only it's boots into fastboot mode but PC shows waiting for device...wat to do plz help
kiran8631 said:
I have updated magisk in Mi 1 and now I am not able to boot my mobile...it just restart and also not able to boot into TWRP...only it's boots into fastboot mode but PC shows waiting for device...wat to do plz help
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=74203817&postcount=4
by flashing with flashfire rooted and installed supersu without twrp flash and now wifi stopped working rest everythig works just fine..for now i m back2stock...can any one tell me the most safe procedure wich do not break any drivers. i m on 1st october patch. thank you in advance
Hello all awesome members, i have searched google, xda and even bing for answers but none have answerd me yet.
So i have an OP5 wich is running Oxygen os 5.1.2 and now i want to update it to the latest.
Things i have tried:
Download and update through the phone updater: Fail
Recovery manager: Fail
ADB sideload: Fail.
To be clear i don't care if i loose root i just want my phone back to fully stock.
So how do i get there? what am i missing?
Can you tell us more details, what ROOT method you are use? If you are using TWRP + Magisk, it's easy to update. Just download Full Update (not OTA) mostly OnePlus 5 will detected if our device ROOTED then will download Full ROM.
Then Goes to Custom Recover, Clear Cache dan Dalvi, install Full Update ROM and flash Magisk again and done
jauhari said:
Can you tell us more details, what ROOT method you are use? If you are using TWRP + Magisk, it's easy to update. Just download Full Update (not OTA) mostly OnePlus 5 will detected if our device ROOTED then will download Full ROM.
Then Goes to Custom Recover, Clear Cache dan Dalvi, install Full Update ROM and flash Magisk again and done
Click to expand...
Click to collapse
I diskussionen use twrp and magisk bit when i Tried to update via twrp i get error 7. I want it to get normal again