ok I think I messed up bad, my son updated tmobile s6 edge to 5.1.1, don't know what he did but when phone boots up on top of screen in red writing it says recovery is not seandroid enforcing what can I do to fix it?? or are we screwed
found out what he did, he updated to 5.1.1 , the tried to root without checking the oem bootloader unlock in dev options so when used oden to install the leaked 5.1.1 and all is good but we don't have root for it
Related
Hello all. I've been trying to flash Helios rom for my s7 edge but I keep failing. First of all, my device is exynos so it should be good to root. However, when I check TWRP page it says ''This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.''
I've tried flashing TWRP but failed into a bootloop, flashed a stock rom to recover. The rom needs TWRP to be installed and I just can't get it working. Maybe I'm using a wrong version of TWRP, or doing something wrong? Any help is appreciated, thank you.
Edit - I faced ''recovery is not seandroid enforcing'' on my last try. Been trying different rooting files to find anything works. Couldn't find anything yet.
I was install French firmware 6.0.1 and flash via Odin. After flashing it PASS in Odian and starting instalation but after 5 sec i got message that i havent drk please chec DRK. I found on youtube how to fix that so i doing that and phone operating normally but is still root, can not get update Official and when power phone have a meesage the kernel is no seandroid Enforce .. In phone in info about softwer write version of kernel 3.10.61 Space X MM RC1+
I want to have as it was from the factory all the original to be. I do not want root phone.
I do not understand if I flash official 6.0.1 that i steel have rooted phone.
How to fix that to have all as it is from factiry and to have official softwer?
Hi there, I hope you guys can help me. Here is the information I have, and thank you so much in advance for your help. Really hope someone will be able to help my stupid self. Haha.
SM-G925F
1.Your bootloader status if applicable - UNLOCKED
2. Rom name with complete baseband/date/version - NEMESIS NOUGAT STABLE S7E PORT V3.1 -
3. Kernel name - Linux 3.10.x
4. Any Mods you are using - None
5.If you are using Custom Rom, your flashing style i.e dirty/clean or you wiped anything else in specific - Flashed Nemesis after flashing another rom that used superSU, then attempted to restore superSU while still using the same rom. I believe this caused a bootloop and I factory wiped the phone to attempt to resolve the bootloop, which has been unsuccessful.
6. If you used any guide, link to the guide - N/A
7. Root status - ROOTED
8. Your exact problem - When attempting to power up the device, stuck in the flashing samsung logo screen. I am able to access both TWRP recovery screen and download screen, however TWRP does not recognise .tar.md5 files, so it seems I am unable to flash a recovery.
9. Any method you tried that failed - Factory wiping the device
10.Any other detail you think would be necessary - I believe am unable to use ODIN as I am using a Macbook, however I am attempting to use it via Parellel. I can still transfer zips to the sd card using the TWRP recovery. The download screen reads:
ODIN MODE
PRODUCT NAME: SM-G925
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
SECURE DOWNLOAD: ENABLED
KNOX WARRANTY VOID: 1 (0x030c)
RP SWREV: B:5 K:2 S:2
alexsamsungsht said:
Hi there, I hope you guys can help me. Here is the information I have, and thank you so much in advance for your help. Really hope someone will be able to help my stupid self. Haha.
SM-G925F
1.Your bootloader status if applicable - UNLOCKED
2. Rom name with complete baseband/date/version - NEMESIS NOUGAT STABLE S7E PORT V3.1 -
3. Kernel name - Linux 3.10.x
4. Any Mods you are using - None
5.If you are using Custom Rom, your flashing style i.e dirty/clean or you wiped anything else in specific - Flashed Nemesis after flashing another rom that used superSU, then attempted to restore superSU while still using the same rom. I believe this caused a bootloop and I factory wiped the phone to attempt to resolve the bootloop, which has been unsuccessful.
6. If you used any guide, link to the guide - N/A
7. Root status - ROOTED
8. Your exact problem - When attempting to power up the device, stuck in the flashing samsung logo screen. I am able to access both TWRP recovery screen and download screen, however TWRP does not recognise .tar.md5 files, so it seems I am unable to flash a recovery.
9. Any method you tried that failed - Factory wiping the device
10.Any other detail you think would be necessary - I believe am unable to use ODIN as I am using a Macbook, however I am attempting to use it via Parellel. I can still transfer zips to the sd card using the TWRP recovery. The download screen reads:
ODIN MODE
PRODUCT NAME: SM-G925
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
SECURE DOWNLOAD: ENABLED
KNOX WARRANTY VOID: 1 (0x030c)
RP SWREV: B:5 K:2 S:2
Click to expand...
Click to collapse
First thing... if it's just stuck on the glowing Samsung logo then it's not a bootloop. It can take a while to boot so leave it about 20 minutes.
TWRP won't recognise tar.md5 files as it doesn't flash them. It flashes .zips. Odin is the one to flash tar.md5.
TWRP is the recovery, so you can't flash a recovery through a recovery (twrp)
What I would try from here... power on the phone and leave it on the Samsung logo for a while and it should boot. If it doesn't then just reflash nemesis ROM through twrp and start again.
This is how you can install the latest twrp and install magisk to get root
I have a Samsung Galaxy S6 Edge SM-G925W8 and it don't have OEM Unlocking In Dev Options so kinda hard for me to do this
KyleAustin said:
I have a Samsung Galaxy S6 Edge SM-G925W8 and it don't have OEM Unlocking In Dev Options so kinda hard for me to do this
Click to expand...
Click to collapse
Not sure how it applies to your particular version. Yet I had no oem unlock on my G925I in developer mode, either.
I went ahead anyway and installed twrp via odin and no problems were encountered.
It will either work or it won't. The risk is yours.
Nah it don't work for me soons I installs TWRP with Odin it just soft bricks my phone and I have a message pop up something about dm-verity blocked it
KyleAustin said:
Nah it don't work for me soons I installs TWRP with Odin it just soft bricks my phone and I have a message pop up something about dm-verity blocked it
Click to expand...
Click to collapse
Did odin reboot your phone after installing twrp? Or did you follow the manual reboot instructions?
My S7 Edge (G935F) was rooted, but with a stock Nougat that kept negging me with Knox, so I got to change that Nougat to this Oreo ZTO-G935FXXS3ERLA_G935FZTO3ERKA-20181212.zip one. Everything was great until yesterday when I had the great idea of turning off OEM Unlocking. I didn't know what I was doing. Then I got the Custom Binary Blocked by FRP Lock. So I just reflashed a full ROM (instead of just the AP) and now I have no Recovery and every attempt to flash TWRP (last 5 versions or any other recovery.img) with Odin 3.13 has failed. It loads "recovery.img" then fails. I'm stuck with the "No Command" eternal loop.
I've scoured the Internet and found no solution yet. Please, help me save my only phone. At this point I just want it to function as a phone again.
ZoOMBeE said:
My S7 Edge (G935F) was rooted, but with a stock Nougat that kept negging me with Knox, so I got to change that Nougat to this Oreo ZTO-G935FXXS3ERLA_G935FZTO3ERKA-20181212.zip one. Everything was great until yesterday when I had the great idea of turning off OEM Unlocking. I didn't know what I was doing. Then I got the Custom Binary Blocked by FRP Lock. So I just reflashed a full ROM (instead of just the AP) and now I have no Recovery and every attempt to flash TWRP (last 5 versions or any other recovery.img) with Odin 3.13 has failed. It loads "recovery.img" then fails. I'm stuck with the "No Command" eternal loop.
I've scoured the Internet and found no solution yet. Please, help me save my only phone. At this point I just want it to function as a phone again.
Click to expand...
Click to collapse
Reinstall the Odin, Reinstall Samsung Drivers and try reflashing your ROM