My brother asked me to root his phone, but later on he said he didn't want to format. I had already flash dm-verity disabler, so I'm now trying to re-enable it or something to boot back to stock ROM again, even if it means no root. Any thoughts? (Samsung Galaxy S7 GM-930F oreo)
Hyoretsu said:
My brother asked me to root his phone, but later on he said he didn't want to format. I had already flash dm-verity disabler, so I'm now trying to re-enable it or something to boot back to stock ROM again, even if it means no root. Any thoughts? (Samsung Galaxy S7 GM-930F oreo)
Click to expand...
Click to collapse
You can encrypt your device though settings menu ( in security menu ). I have not used this method so can't say what happens to root. If twrp is installed you will have to reformat data again to flash anything.
Or
Flash stock firmware through Odin. This will generally remove root ( and twrp if installed ).
Always do a backup before doing anything.
Related
Hello, I currently have a G920T that had been working alright for quite some time. The problem is that yesterday while using it normally, it suddenly froze. Thought it was the app, but saw it was the phone itself. Thus, I decide to turn it on again. When I do that, the phone does not continue after the logo and has the LED light white, while blinking on an off. When I manage to enter the Android Recovery menu it gives me the error shown in the title. The phone's rooted and was unlocked, so I could use it with AT&T.
I attempted doing a full reset, upgraded it to Nougat, and I am still stuck. Any help's appreciated in advanced.
Would like to say, when I installed the official Nougat Upgrade for my phone, upon starting, it began installing some things and then preceded to start Deleting. Afterwards, it just froze again. Did I do something wrong?
To get past this issue you have to Root with SuperSU, this will patch the Kernel to disable DM-Verity and will allow you to boot normally.
If you don't want to get rooted then reflash stock firmware via odin. never do OTA updates as i have always say the come "Dirty"
EDIT: Sorry didn't read you were rooted, just re-root again with SuperSU (To get your Kernel patched again) for DM-Verity
Starnel said:
To get past this issue you have to Root with SuperSU, this will patch the Kernel to disable DM-Verity and will allow you to boot normally.
If you don't want to get rooted then reflash stock firmware via odin. never do OTA updates as i have always say the come "Dirty"
EDIT: Sorry didn't read you were rooted, just re-root again with SuperSU (To get your Kernel patched again) for DM-Verity
Click to expand...
Click to collapse
So I use (what I previously used) cf-autoroot again? I ask this, since it seems their website have the recovery for marshmallow version and not for nougat (if I am not able to downgrade to 6).
Junito72 said:
So I use (what I previously used) cf-autoroot again? I ask this, since it seems their website have the recovery for marshmallow version and not for nougat (if I am not able to downgrade to 6).
Click to expand...
Click to collapse
Root with TWRP and superSU zip, i don't recommend CF-AutoRoot
Before flashing the Zip do the following on a Terminal in TWRP
Mount o- bind /dev/urandom /dev/random
Junito72 said:
So I use (what I previously used) cf-autoroot again? I ask this, since it seems their website have the recovery for marshmallow version and not for nougat (if I am not able to downgrade to 6).
Click to expand...
Click to collapse
You can use CF-AutoRoot for 6.0.1 and 7.0.
forumber2 said:
You can use CF-AutoRoot for 6.0.1 and 7.0.
Click to expand...
Click to collapse
When I use CF-Autoroot and attempt to boot it into recovery I get the following message, "recovery is not seandroid enforcing".
So I'd take I try installing a custom ROM first before attempting to start it in recovery?
Junito72 said:
When I use CF-Autoroot and attempt to boot it into recovery I get the following message, "recovery is not seandroid enforcing".
So I'd take I try installing a custom ROM first before attempting to start it in recovery?
Click to expand...
Click to collapse
Oh, that means CF-AutoRoot has not updated to work on 6.0 & 7.0 bootloader for G920T (It is updated and working on 6.0.1 & 7.0 for G920F)
Flash the stock ROM again. After that, flash TWRP and than flash latest SuperSU zip via TWRP.
forumber2 said:
Oh, that means CF-AutoRoot has not updated to work on 6.0 & 7.0 bootloader for G920T (It is updated and working on 6.0.1 & 7.0 for G920F)
Flash the stock ROM again. After that, flash TWRP and than flash latest SuperSU zip via TWRP.
Click to expand...
Click to collapse
I tried doing that, but wouldn't get past the main ROM's screen. I tried a custom ROM then (I think nemesis or such) and lasted longer, but again froze and loops with the white LED light on.
Any suggestions?
I got the "custom binary boot blocked by frp lock" issue so I gotta reflash the stock firmware, which I should have since I did a full TWRP backup so if I convert my twrp backup in to a flashable zip will i be able to flash it through ODIN? (obviously i cant do it through TWRP Recov since I can only access download mode)
I can get the stock firmware from sammobile.com but its going to take like 4h+ to download and I dont have time for that
izou1838 said:
I got the "custom binary boot blocked by frp lock" issue so I gotta reflash the stock firmware, which I should have since I did a full TWRP backup so if I convert my twrp backup in to a flashable zip will i be able to flash it through ODIN? (obviously i cant do it through TWRP Recov since I can only access download mode)
I can get the stock firmware from sammobile.com but its going to take like 4h+ to download and I dont have time for that
Click to expand...
Click to collapse
Had the same issue. Rookie mistake. I accidentally left the developer option OEM unlock disabled and viola! Had to do a reset. Also, if you had any fingerprints while using the Rom you used, You might come into issues when resetting using Odin. You might have to format your internal memory using TWRP. Im not saying its something slcertain. I just had to. The only firmware I had available was a 6.0.1 MM stock Rom and I came into issues when unlocking the phone. Remember, this was a full reinstall in Odin and the screen was locked. When I unlocked the screen it would just reboot. So, lesson learned. Make sure if you go and root your phone again never ever, ever, ever disable that option in developer.
But try it. You can follow the steps from the root guide for nougat in the threads and go up until the step where you install TWRP. Boot into TWRP and see if you can restore the backup. Chances are it might work without having to do the extra steps like reinstalling the stock firmware. If that doesn't work and you run into issues in TWRP you might need to reinstall everything from scratch again.
Thanks! Already figured it out ?
please explain
izou1838 said:
Thanks! Already figured it out
Click to expand...
Click to collapse
my note 5 is at custom binary blocked by frp lock. i think I also turned off the option of oem unlock in developers option by mistake.
I have twrp back up on pc only. please help me how to unbrick the phone now.
Unfortunately the TWRP back is no help ):
However if you have the stock full system image you can just flash that through ODIN and then re-root? easy fix.
Look for the image here in XDA I've seen it
Sir i have note 5 with csc n920pvps3bpk1 shows in phone aftar dialing *#1234# but on the box of this cell phone is printed as n920fvps3bpk1 and n9200 will u plz tell me which csc is correct and i want to upgrade it to 7.0 and its knox waranty has voided.
izou1838 said:
I got the "custom binary boot blocked by frp lock" issue so I gotta reflash the stock firmware, which I should have since I did a full TWRP backup so if I convert my twrp backup in to a flashable zip will i be able to flash it through ODIN? (obviously i cant do it through TWRP Recov since I can only access download mode)
I can get the stock firmware from sammobile.com but its going to take like 4h+ to download and I dont have time for that
Click to expand...
Click to collapse
Hi, I have the same problem with an SM-520F, did you manage to solve it?
Hi,
I would like to root my samsung galaxy s7 sm-g930f with android 7.0 and firmware phn.
I tried to root my phone with CF-Auto-Root-herolte- and odin but I made something wrong (probably not using the most recent file version or odin version) and my phone was blocked.
Then I flashed a new stock version to resolve the problem.
Now I would like to know if this method is correct (without installing twrp) and if is it possible root the phone without erasing all my data.
thank you
gnogno1985 said:
Hi,
I would like to root my samsung galaxy s7 sm-g930f with android 7.0 and firmware phn.
I tried to root my phone with CF-Auto-Root-herolte- and odin but I made something wrong (probably not using the most recent file version or odin version) and my phone was blocked.
Then I flashed a new stock version to resolve the problem.
Now I would like to know if this method is correct (without installing twrp) and if is it possible root the phone without erasing all my data.
thank you
Click to expand...
Click to collapse
If you want to root I would recommend you to use Magisk but a fsctory reset is mandatory if you want to do this as you will have to flash TWRP to install it and since the encryption changes when you install a custom recovery you will need to use the format data option under the Wipe menu in TWRP and that will factory reset your phone. So make a backup first.
If you decide to do this. Use the format data option then reboot to recovery and after that flash magisk zip. After that reboot to system and wait.
Sent from my SM-G930F using Tapatalk
Hello XDA !
This is my first post..sorry for my bad english.
I bought a S7 (SM-G930F) Android 8.0 and i rooted it then i noticed that was just systemless root.. and it's totally useless for me because i want to uninstall system apps and change build.prop..
so I flashed the stock rom and reflashed TWRP, then I executed a command to force SuperSU to install in system
(echo SYSTEMLESS=false>>/data/.SuperSU)
and I installed SuperSU.zip..but it stucks on bootloop.. I tried many different SuperSU.zip versions even a modified version for system mode root, but nothing works..
by the way I installed no-verity-opt-encrypt-6.1.zip before installing SuperSU.zip !
ysnelazzab said:
Hello XDA !
This is my first post..sorry for my bad english.
I bought a S7 (SM-G930F) Android 8.0 and i rooted it then i noticed that was just systemless root.. and it's totally useless for me because i want to uninstall system apps and change build.prop..
so I flashed the stock rom and reflashed TWRP, then I executed a command to force SuperSU to install in system
(echo SYSTEMLESS=false>>/data/.SuperSU)
and I installed SuperSU.zip..but it stucks on bootloop.. I tried many different SuperSU.zip versions even a modified version for system mode root, but nothing works..
by the way I installed no-verity-opt-encrypt-6.1.zip before installing SuperSU.zip !
Click to expand...
Click to collapse
i havent rooted an S7 in a while, but dont you just flash twrp in Odin with the reboot box unchecked and once the flash completes, reboot into twrp which will present you a slider that says something along the lines of "slide to allower SU access" or something like that. Once youve done that, then you flash magisk in TWRP, boot, install busybox, and you should then be asked if you want to grant SU access to busybox, if it does that, youre all set
youdoofus said:
i havent rooted an S7 in a while, but dont you just flash twrp in Odin with the reboot box unchecked and once the flash completes, reboot into twrp which will present you a slider that says something along the lines of "slide to allower SU access" or something like that. Once youve done that, then you flash magisk in TWRP, boot, install busybox, and you should then be asked if you want to grant SU access to busybox, if it does that, youre all set
Click to expand...
Click to collapse
Thank you so much for your response !
I did everything in the correct way, i flashed twrp with reboot option disabled.. and i formated data then reboot to recovery and I installed no verity and after that i installed SuperSU and it's done successfully but it ended up with a bootloop..
also I tried to install a system mode supersu.zip and it freezes TWRP and stuck on "installing"
I think literally I can't do the system root.. so i did systemless root.
ysnelazzab said:
Thank you so much for your response !
I did everything in the correct way, i flashed twrp with reboot option disabled.. and i formated data then reboot to recovery and I installed no verity and after that i installed SuperSU and it's done successfully but it ended up with a bootloop..
also I tried to install a system mode supersu.zip and it freezes TWRP and stuck on "installing"
I think literally I can't do the system root.. so i did systemless root.
Click to expand...
Click to collapse
the F models should allow for system root, not sure tho as i didnt spend much time with my S7 and S7 Edge. Still have em tho. If i remember, i could dink with them tonight
youdoofus said:
the F models should allow for system root, not sure tho as i didnt spend much time with my S7 and S7 Edge. Still have em tho. If i remember, i could dink with them tonight
Click to expand...
Click to collapse
mine is G930F oreo 8.0 i tried everything to do system root but failed.. one thing I didn't do is a custom rom. i prefer a rooted stock rom.
ysnelazzab said:
mine is G930F oreo 8.0 i tried everything to do system root but failed.. one thing I didn't do is a custom rom. i prefer a rooted stock rom.
Click to expand...
Click to collapse
well, you cant do a custom ROM without a custom recovery. bootloader is unlocked i assume
youdoofus said:
well, you cant do a custom ROM without a custom recovery. bootloader is unlocked i assume
Click to expand...
Click to collapse
as I said i have TWRP which is a custom recovery. and i don't want custom ROM i just want my stock ROM system rooted not systemless.
ysnelazzab said:
as I said i have TWRP which is a custom recovery. and i don't want custom ROM i just want my stock ROM system rooted not systemless.
Click to expand...
Click to collapse
im well aware that TWRP is a custom recovery, i remember when it first launched and people were converting from CWM to TWRP. Anyways, if youve successfully installed twrp, try factory resetting the device and then booting. You should only need to flash magisk in TWRP and busy box in the OS once booted
Hi there, I'm having no luck finding a solution to my problem anywhere.
I'm using a Galaxy S7 running Oreo (I know, old school), and like many phones, it came with a bunch of apps that can't be uninstalled unless you have root access. So, I installed TWRP, and then Magisk v23, and then I installed a root uninstaller in order to remove the apps in question.
However, I use Revolut and an app for the bank I'm with, and so while my device is rooted, I am locked out of both.
What I want is to have the disable-only apps gone, and my device unrooted and back to normal so I can use Revolut and said banking app.
I believe uninstalling Magisk should unroot the device, but without Magisk installed, I can't boot into the system because of TWRP and the whole dm-verity thing. So, I want to replace TWRP with the stock recovery, which, if I'm correct, should achieve the desired outcome.
I downloaded the exact firmware for my phone from sammobile, and the recovery file can be extracted from it easily, but I don't really know how to go about flashing said file, or even if I can. Odin isn't working for me.
I tried flashing the whole "AP" file via Odin (the latest version), but that restored the device back to it's factory state, disable-only apps and all.
So can anyone help me with this? Or is what I want to do here even possible? I'd really appreciate some input / advice. Thanks!
P.S. maybe you can tell, but I'm kind of a noob, so apologies if I'm overlooking something obvious.
Android's recovery where it doesn't matter whether it's Stock or Custom can't be used to unroot Android if it got rooted by TWRP and/or Magisk this because phone's boot.img got tampered by those: you'ld have to completely re-flash phone's Stock ROM to get rid off of all modifications you applied so far.
Okay then, thanks for explaining.
Just to be clear, what you're saying is that it isn't possible to unroot a device and then restore just its stock recovery (to replace TWRP). You cannot undo modifications made to boot.img and therefore must re-flash the stock firmware?
What I do with unwanted system apps on other android phones is to remove the .apk from /system by booting into recovery and using the shell/adb with u**x commands (actually move them somewhere they can't be seen by the O/S with mv command).
Also when faced with dm-verity, Magisk just modified the boot.img
and changes fstab to take out verify from system mount & patches init and removed /verity_key.
I was able to uninstall Magisk (only phone mod was unlocked boot loader allowing custom boot over usb).