G920T : "dm-verity verification failed..." Help. - Galaxy S6 Q&A, Help & Troubleshooting

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?

Related

Moto G (2015) Update issue

Background: My phone is rooted and I have TWRP installed as my recovery.
Android 6.0 rolled out to my phone, and I really want to update it. However, everytime I try to install it, my phone boots into TWRP and does nothing. After booting into Android, my phone will boot into TWRP on its own again, and after repeating this for a while it will read something along the lines of, "There was a problem with the update" My question is this: how do I install the software update sent to my phone?
AliRockz said:
Background: My phone is rooted and I have TWRP installed as my recovery.
Android 6.0 rolled out to my phone, and I really want to update it. However, everytime I try to install it, my phone boots into TWRP and does nothing. After booting into Android, my phone will boot into TWRP on its own again, and after repeating this for a while it will read something along the lines of, "There was a problem with the update" My question is this: how do I install the software update sent to my phone?
Click to expand...
Click to collapse
You can't flash the OTA with a custom recovery or root. You'll have to flash a stock recovery to get the OTA.
Tel864 said:
You can't flash the OTA with a custom recovery or root. You'll have to flash a stock recovery to get the OTA.
Click to expand...
Click to collapse
How would I do this?
AliRockz said:
How would I do this?
Click to expand...
Click to collapse
Search, or look around in the 2015 General Forum.

Want to unlock my bootloader + installing TWRP

Hello all,
I am receiving tomorrow my new Samsung S6 and i want to know some things.
- Unlocking bootloader (how to and link?) - have searched a bit and you need ODIN. but what is the best version etc
- Installing TWRP3.0 (how-to) - where to find the latest TWRP for samsung s6
And than one of the most important question, is there a stock android that doesent have any buys and fc's????
Bootloader is not locked on S6 (except AT&T variant)
You can get latest ODIN from here;
http://dl.sammobile.com/Odin3_v3.10.7.zip
If you want to install TWRP on it;
1- Update it to Marsmallow if you haven't
2- Install this TWRP via ODIN;
http://arter97.com/browse/S6/kernel/13.1/g920fi/arter97-recovery-g920fi-13.1-twrp_3.0.2-0.tar.md5
3- Boot up to TWRP and flash this ZIP before do anything on TWRP;
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
forumber2 said:
3- Boot up to TWRP and backup your unmodified stock ROM before do anything on TWRP;
4- flash this ZIP
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
Click to expand...
Click to collapse
Wouldn't this order make more sense so he had a backup in case something goes wrong?
Also, here are the threads for TWRP and SuperSU for the S6 on XDA:
http://forum.xda-developers.com/galaxy-s6/orig-development/twrp-t3080940
http://forum.xda-developers.com/galaxy-s6/orig-development/cf-auto-root-t3056630
djbosanac said:
And than one of the most important question, is there a stock android that doesent have any buys and fc's????
Click to expand...
Click to collapse
No, and there probably won't be any for a long time, but there are lots of TouchWiz-based custom ROMs.
so basicly i dont need any customezation? because you telling me there will not be released a custom stock rom? Even a CM13 rom
thats poor services!
Uhm
djbosanac said:
so basicly i dont need any customezation? because you telling me there will not be released a custom stock rom? Even a CM13 rom
thats poor services!
Uhm
Click to expand...
Click to collapse
Correct. The only custom ROMs availability now and the foreseeable future are based on TouchWiz, not AOSP Android or CyanogenMod.
CafeKampuchia said:
Wouldn't this order make more sense so he had a backup in case something goes wrong?
Click to expand...
Click to collapse
He need dm-verity disabled boot image for working TWRP backups. That's why I suggest him to install this ZIP.
While reading topics on the internet (google)
If you THE smartphone update to 6.0 you do not need to unlock the bootloader. is this correct?
For now i will not use TWRP because there isent a proper ROM for the S6. is this because the exynoss CPU? because QSD cpu's have always the better support for CM..
djbosanac said:
While reading topics on the internet (google)
If you THE smartphone update to 6.0 you do not need to unlock the bootloader. is this correct?
For now i will not use TWRP because there isent a proper ROM for the S6. is this because the exynoss CPU? because QSD cpu's have always the better support for CM..
Click to expand...
Click to collapse
As I said before, there's no bootloader unlock because bootloader is factory-unlocked on Samsung devices.
If you want root, you should to use TWRP for install the latest SuperSU.
Yes, there's no CM ROM for Exynos 7420 right now. Maybe in future? Who knows...
is there a twrp that works because the original twrp that i download form twrp.me isent working getting a weird issue: recovery is not seandroid enforcing
djbosanac said:
is there a twrp that works because the original twrp that i download form twrp.me isent working getting a weird issue: recovery is not seandroid enforcing
Click to expand...
Click to collapse
It is not an issue, it is just a warning. I wrote what you need to do at first reply;
forumber2 said:
Bootloader is not locked on S6 (except AT&T variant)
You can get latest ODIN from here;
http://dl.sammobile.com/Odin3_v3.10.7.zip
If you want to install TWRP on it;
1- Update it to Marsmallow if you haven't
2- Install this TWRP via ODIN;
http://arter97.com/browse/S6/kernel/13.1/g920fi/arter97-recovery-g920fi-13.1-twrp_3.0.2-0.tar.md5
3- Boot up to TWRP and flash this ZIP before do anything on TWRP;
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
Click to expand...
Click to collapse
i tried to install it, used the AP method in Odin.
But when i want to go in TWRP recovery i get the stock recovery! How to solve this issue
I'm having this issue as well on the T-Mobile variant. I have tried the unchecking auto reboot option in Odin and manually going to recovery. When I successfully flash according to Odin, I can't not get past the Recovery is not Seandroid enforcing boot.
SuddenGun007 said:
I'm having this issue as well on the T-Mobile variant. I have tried the unchecking auto reboot option in Odin and manually going to recovery. When I successfully flash according to Odin, I can't not get past the Recovery is not Seandroid enforcing boot.
Click to expand...
Click to collapse
where you able to figure this out? same problem. I can flash the twrp via ODIN, but get stuck on the "recovery is not seandroid enforcing" message. It just freezes on that.
help anyone? what should I be looking at? BL, Modem? I flashed original MM .tar file already...
I have a 920t (galaxy s6 non-edge tmobile)
piotrus22 said:
where you able to figure this out? same problem. I can flash the twrp via ODIN, but get stuck on the "recovery is not seandroid enforcing" message. It just freezes on that.
help anyone? what should I be looking at? BL, Modem? I flashed original MM .tar file already...
I have a 920t (galaxy s6 non-edge tmobile)
Click to expand...
Click to collapse
I did figure this out, check this post for how I did it.

[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root

[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root
THIS GUIDE IS NOW DEPRECATED. THERE IS NO NEED ANYMORE TO GO THROUGH THE UPDATING PROCESS AS THERE IS A FULL NOUGAT FACTORY IMAGE AVAILABLE (Build NPH25.200-22). FIRMWARE AVAILABLE HERE: https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142 BE SURE TO THANK @acejavelin FOR TRACKING DOWN THE FIRMWARE PACKAGE FOR US.
Notes:
-YOU ATTEMPT THIS AT YOUR OWN RISK IF YOU FLASHED ANY FIRMWARE PREVIOUSLY NOT FOR THE XT1575 US VERSION
-This guide will have 2 parts. 1 for those that kept their systems read only/systemless, and 1 for those that did not.
-Whether you live booted TWRP or Installed TWRP, if you chose to allow system modifications your OTA will likely fail (you'll need part 2).
-Restoring a TWRP backup will not work and will cause an OTA to fail due to having to allow system write access in TWRP - You Need Part 2.
-This guide assumes you have basic ADB knowledge and already know what fastboot is and how it works.
-Thanks to @gokart2 for the OTA and @acejavelin for the return to stock guides
Part 1: Those That Tweaked Systemlessly Currently On 24.49-18-16 (Will only work if you kept TWRP read only/used systemless root):
1: Disable & Remove systemless Xposed within Magisk Manager and all other Magisk modules. Reboot and wait for Art cache to rebuild.
2: Remove any adblock hosts within your adblock app if installed, or any other root level system altering apps like Greenify (don't worry, you'll get them back).
3: Remove Magisk by booting into TWRP and flashing the current Magisk Removal zip. Reboot.
4: For systemless SuperSu you need to consult their thread as I do not use it. (I'll update this if someone knows the correct process).
5: ADB reboot bootloader and fastboot flash the stock recovery. Latest MM recovery links at the bottom of this post. (rename file to recovery.img).
6: Move the OTA Blur_Version.24.231.16.clark_retus.retus.en.US.zip to the root of your internal sd card (NOT in a folder). File links at the bottom of the post. Thanks @gokart2
7: ADB reboot recovery, when "no command" is listed, hold power + tap volume up then release to access recovery options. Choose "apply update from phone storage". Choose the file and wait for the flash. It's a large update so be patient (about 10-20min). Choose reboot manually in recovery after flash succeeds. Enjoy Nougat!
8: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly.
Part 2: Those That Have Done Everything - TWRP Write Access, Custom Roms, On Older Firmware, Etc (XT1572 Build Flashers Do This At Their Own Risk):
1: Flash the latest full factory image available (24.49-18-8) available here: https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110. Thank @acejavelin for the thread while your at it. Follow the directions in that guide, it's well detailed and accurate - however read my notes just below first:
NOTES:
-Omit the "fastboot oem lock begin" & "fastboot oem lock" commands to remain bootloader unlocked.
-Omit the "fastboot erase userdata" command if you want to dirty flash and keep all of your data. I recommend clean, you can always root & restore each apps data with Titanium after the Playstore installs everything.
-The "fastboot oem fb_mode_set" instead of "fastboot oem lock begin" & "fastboot oem fb_mode_clear" instead of "fastboot oem lock" I've found to be unnecessary if staying unlocked. Your choice.
-The "fastboot flash partition gpt.bin" & "fastboot flash bootloader bootloader.img" commands will likely fail due to version mismatches. This is ok.
-The "fastboot flash modem NON-HLOS.bin" tends to fail too. For this, just run the command again until it succeeds.
2: After flashing 24.49-18-8 take the OTA to 24.49-18-16. Reboot. OTA zip provided below if you prefer to sideload.
3: Either install the 7.0 OTA the normal way via the update center or just side load it using the directions above. I recommend side loading due to the file size being very close to 1GB.
4: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly!
For Xposed, See My Guide Here: https://forum.xda-developers.com/showpost.php?p=74014516&postcount=96
Stock MM 24.49-18-16 Recovery: https://mega.nz/#!aZpC2RzQ!Fy3GTo_XYPjB1lwuHffCUUERuvnsyvON3kS8kMJ9Cm8
Stock MM 24.49-18-16 Recovery Mirror: https://drive.google.com/file/d/0BxxRfNko9QDKNS1NdnAyZVp6dVU/view?usp=sharing
24.49-18-8 OTA to 24.49-18-16: https://mega.nz/#!yZx2FLzR!cWfKIAYe5VyuadLI55UNHJvwWU98CXUi1g0DO1pDoKg
NPH25.200-22 OTA: https://mega.nz/#!HVhWWLxK!h-8G3vO3Sye_YwypyIJyWb2_79Ow34vNiDnMl2Q8uJg
NPH25.200-22 OTA Mirror: https://drive.google.com/file/d/0B3gPYUZ4nRLwOHJKQnNYczNEMHc/view?usp=sharing
MD5 for NPH25.200-22 OTA: 74d1a4b135200661cc4efd248f99ce33
Stock 7.0 NPH25.200-22 Recovery: https://mega.nz/#!TNoHQAjI!5U2w4p_G7pHlW6Mak7LqFR_PeWUDpSLc7S3OiUs_Qf8
Alrighty. I got back to stock 6.0 with the 18-16 update. I couldn't get the OTA via the system update, so I tried doing it via ADB. That threw up a "status 7 error". I then copied the file to my internal storage and selected update via SD Card in recovery. It hung on "Patching System Files" for a while, but in the end it moved on and worked fine. Thanks for the awesome guide!
Thread updated with downloads for the 24.49-18-8 OTA to 24.49-18-16 zip.
I exctracted the 7.0 Stock recovery to replace if you decide to flash TWRP and want to go back to the stock recovery for future updates (HAHAHA yeah right!). Download link in OP. The 7.0 Recovery is different than the MM recovery. They are not interchangeable. Don't flash the 7.0 recovery on MM.
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Bwangster12 said:
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Click to expand...
Click to collapse
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
annoyingduck said:
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
Click to expand...
Click to collapse
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Here's the recovery before the 7.0 one, just incase.. Was bored. Ok, I won't lie....didn't see u posted the 7.0 recovery....lol.:good::highfive:
Bwangster12 said:
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
Click to expand...
Click to collapse
Yup. TWRP flashes and works, magisk v14 works, and so far systemless xposed api24 is working.
EsteBandido4444 said:
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Click to expand...
Click to collapse
What is everyone's fascination with relocking the bootloader? You do not need to relock your bootloader. You cannot relock the bootloader unless all your system partitions match. Use my part 2 section. Read the notes, skip the bootloader lock commands. Leave your bootloader unlocked, get up and running on nougat, then you can issue the lock commands if you really want a locked bootloader.
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
EDIT nevermind didn't read lol
Amp699435 said:
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
Click to expand...
Click to collapse
Copy the file to the root of your internal storage. Reboot into recovery. Hold power = volume up & release to access menu options. Choose apply update from storage. Select the OTA.zip package and let it install. (Directions are clearly written in OP.)
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
Click to expand...
Click to collapse
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
GrandAdmiral said:
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
Click to expand...
Click to collapse
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
annoyingduck said:
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
Click to expand...
Click to collapse
Gotcha. I know I'm going to root again, but I've never used Magisk before so I wasn't sure of that piece.
annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
I am running Dirty Unicorns right now and when i looked up what I'm on in fastboot, it showed MPSH24.49-18-16. Would I just follow part 2 and use MPSH24.49-18-8 or something? I thought I had to use at least the version I'm on or newer.
GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.[/QUOTE
Your issue is that TWRP has modified your
System, any restoring of the stock rom will fail to update. So yes, you'll need to go through part 2 and downgrade and work your way back up.
Click to expand...
Click to collapse
I downloaded the zip (it took a while).
Restored to stock like 3 different ways but still hit a road block. I went the adb sideload route but got status error 7 because my build fingerprint wasn't correct. I tried searching for the right build I need, but I'm not an expert and couldn't find the right set of files that I was sure I knew how to restore. I ended up restoring my AICP backup.
If somebody could PM me and give me a hand (messaging through Hangouts or something) that would be AWESOME!
I'm planning trying to snag an XL 2 pre-order next week, but until then the less headache the better! Plus stock Nougat looks better on a Swappa listing
Trying to sideload via recovery 24.49-18-16 but I keep getting "("unexpected contents:EMMC:/dev/block/bootdevice/by-name/boot...". I've also tried installing from the phone but the same error appears in recovery. Any ideas?

Can't Update renovate firmware

Hey guys,
Hopefully someone can help me with my problem. So i did the following:
To get rid of the 7 day Block of oem-unlocking on my s8+ i downgraded back to Nougat. From here on I flashed TWRP + rooted my device with magisk. After That i flashed the RENOVATE_ICE_G95X-7.5 rom + the Flashable_G95xF_FD_Firmware_TWRP_AQL5_r8 Firmware. I've let my Phone start up and went back to TWRP To Update the rom to RENOVATE_ICE_G95X-10.1. To this point everything Worked fine, the Phone Boots completely fine. Now to my problem: im Sitting on the actual stable rom but with the Baseband-version of Nougat which is AQL5. When i try to Flash the actual Firmware (CRC7 or CRD7) via TWRP my Phone gets stuck on the first Samsung Logo and Shows the following red Message: "Only official released binaries are allowed to be flashed". I would be glad for any help.
If you can find a standalone modem file from the ROM you mentioned you should be able to flash it in TWRP recovery. Last time I did this was on a Note 3. I think that the process should be the same with S8.
Can't seem to find one, but i found out that the same error occurs when installing other custom-roms like the King Oreo Rom which installs the newest Bootloader and Modem via Aroma installer. Only solution after that is to Flash Nougat again via Odin.

can't root S7 (SM-G930F) in system mode.

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

Categories

Resources