Database Info

XCover 3 (SM-G388F) root on 5.1.1

So, I received this phone as an award in a competition, and when I wanted to root it... nope. No root for this phone. Only for 4.4.4, but I hate ****Kat and I don't want it. So, I updated to 5.1.1 and I was looking for root.. didn't find anything. And those "universal" roots such as KingRoot, Kingo Root, TowelRoot didn't work. I also tried installing TWRP, but after installing it and rebooting into it, the phone got stuck on "recovery is not seandroid enforcing". After booting the phone and than entering the recovery, the "recovery is not seandroid enforcing" appeared again, but instead of getting stuck, the stock recovery booted. So I flashed the stock rom with stock recovery just to remove that annoying error via odin.
Any ideas how to root this f*****g knox device?
Thanks

Please..

i have the same probleme. Nothing work for root.

Hi together, i am mucho interested, too.
Also slightly skilled linux user, so if anyone has a clue where to start rooting this thing i can give it a try.

Mhh I also need a way to root this device because I need a full Image of my /data Partition.
My first idea was to flash the Kitkat bootloader and TWRP. However it will not but a L /system.
So we need a custom L system image which has the already installed SuperSU.
I really like to try it but however my task is to restore photos and not to hardbrick this phone.
Can anybody try a custom /sytem image which is Prerooted? Heimdall should be able to flash it.

_Beni_ said:
Mhh I also need a way to root this device because I need a full Image of my /data Partition.
My first idea was to flash the Kitkat bootloader and TWRP. However it will not but a L /system.
So we need a custom L system image which has the already installed SuperSU.
I really like to try it but however my task is to restore photos and not to hardbrick this phone.
Can anybody try a custom /sytem image which is Prerooted? Heimdall should be able to flash it.
Click to expand...
Click to collapse
If you have a clue where to find such images i can try. Without root this phone is useless to me, so i wouldn't mind bricking it

Tried to flash SBOOT, SBOOT2, Loke_Primary, Loke_Recovery ... it is now hard broken
Yeah maybe i forgot it has no Qualcomm processor where you even can flash a image even you dd if=/dev/zero of=/dev/mmc.
Now giving my old OnePlus Two to her.
You need to register at SAMMobile there you can the latest 5.1.1 for xcover3, you need to extract the image with 7zip then unpack the system.img with sparsed, then mount it via loop-back device. Now umount it, repack the image with sparse and flash the result into SYSTEM with heimdall.
Good luck, I ****ed it up

Oh sh*t, sorry to hear dude! Okay, this evening i can give it a try. Am i guessing right that i want to put the SuperSU binary into the /system/app? Or what's the best way to root this?

todomade said:
Oh sh*t, sorry to hear dude! Okay, this evening i can give it a try. Am i guessing right that i want to put the SuperSU binary into the /system/app? Or what's the best way to root this?
Click to expand...
Click to collapse
Yeah, however I'm not sure how su exactly works.
I know took a look at UPDATE-SuperSU.zip.
This lines are interesting:
if ($SAMSUNG); then
# Prevent "KERNEL IS NOT SEANDROID ENFORCING"
SAMSUNG_CHECK=$(cat /sutmp/boot.img | grep SEANDROIDENFORCE)
if [ $? -ne 0 ]; then
echo -n "SEANDROIDENFORCE" >> /sutmp/boot.img
fi
fi
dd if=/sutmp/boot.img of=$BOOTIMAGE bs=4096
Click to expand...
Click to collapse
It seems its just appends SEANDROIDENFORCE at the end of the boot.img and then flashes it.
Maybe it is the same for the recovery.
You could just try to "echo -n "SEANDROIDENFORCE" >> twrp-3.0.2-*.img"
and then flash this image via heimdall.

Okay, looks like i should dig some deeper into that matter. I guess i can try your suggestion within the next week. I'll post an update if i make any progress.

_Beni_ said:
Yeah, however I'm not sure how su exactly works.
I know took a look at UPDATE-SuperSU.zip.
This lines are interesting:
[...]
It seems its just appends SEANDROIDENFORCE at the end of the boot.img and then flashes it.
Maybe it is the same for the recovery.
You could just try to "echo -n "SEANDROIDENFORCE" >> twrp-3.0.2-*.img"
and then flash this image via heimdall.
Click to expand...
Click to collapse
Okay i tried it, sadly no success.
Still getting "Recovery is not Seandroid Enforcing" and default recovery
Will now try to pack a boot.img myself and flash it.
Other approaches or tips are highly appreciated!

Is the "Recovery is not seandroid enforcing" showing up on the most recent build of twrp, 3.0.2.0. For the lollipop build of the device?? I want some confirmation before deciding to flash twrp and then supersu into my phone running lollipop?
Newest twrp link: https://dl.twrp.me/xcover3ltexx/

Matt07211 said:
Is the "Recovery is not seandroid enforcing" showing up on the most recent build of twrp, 3.0.2.0. For the lollipop build of the device??
Click to expand...
Click to collapse
Affirmative.

VolterPL said:
Affirmative.
Click to expand...
Click to collapse
So do you mean that the "recovery is not seandroid enforcing" shows up with the newest twrp build (3.0.2-0) for our device while running lollipop? Are you able to use the twrp recovery and phone as normal even though that message flashes on boot.
I geuss a fix could be compiling the kernel with the flag disabled on the flag that stops you from switching between enforcing and permissive modes. As done on this guide, http://graemehill.ca/compiling-permissive-android-kernel/ . This would allow the recovery to set itself to be running in permissive mode, when it runs "setenforce 0" as seen
https://github.com/TeamWin/android_device_samsung_xcover3ltexx/blob/android-4.4/init.rc
The source code for the Samsung phone, http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=g388f
I am willing to build/compile the kernel, but due to this phone being my main phone, I am not in a position to test it out, would anyone here be willing to try?
The modified kernel will also allow you to run the OS in permissive mode if done through the terminal.

Matt07211 said:
So do you mean that the "recovery is not seandroid enforcing" shows up with the newest twrp build (3.0.2-0) for our device while running lollipop? Are you able to use the twrp recovery and phone as normal even though that message flashes on boot.
Click to expand...
Click to collapse
Yes, I can confirm it's true. The phone works fine. When I try to go to the recovery mode, it shows said message and boots to the stock recovery.

VolterPL said:
Yes, I can confirm it's true. The phone works fine. When I try to go to the recovery mode, it shows said message and boots to the stock recovery.
Click to expand...
Click to collapse
I got a few questions to ask
How are you flashing the twrp image? Is it via odin and are you using the newest twrp build (3.0.2-0)
I am willing to work, read up and compile anything necessary to get the recovery working on the device, but due to it being my only phone I cant afford to mess around with it much, so are you willing to try out stuff for me e.g. flashing a custom kernel with the ability to toggle selinux modes?
I believe a fix for the "recovery is not seandroid enforcing" can be fixed if I recompile the kernel with a flag set to false (It a custom flag from samsung that disallows the changing of selinux modes, "EXTRA_CFLAGS += -DCONFIG_ALWAYS_ENFORCE=false") allowing for the twrp recovery to change "setenforce 1" to a "0" allowing the recovery to run in permissive mode. http://graemehill.ca/compiling-permissive-android-kernel/ , https://su.chainfire.eu/#selinux , https://source.android.com/security/selinux/
If you are willing to help test for me I would really appreciate it And once I get the recovery working I am gonna root my phone by flashing the SuperSu.zip.

Matt07211 said:
How are you flashing the twrp image? Is it via odin and are you using the newest twrp build (3.0.2-0)
Click to expand...
Click to collapse
Yes, I am using the newest Odin and the newest TWRP, downloaded from TWRP site.
I would like to help you if, and only if, there's absolutely no chance of bricking my phone as I've bought it recently for quite a lot (at least for me). I don't care about warranty, as well as triggering KNOX.

VolterPL said:
I would like to help you if, and only if, there's absolutely no chance of bricking my phone as I've bought it recently for quite a lot (at least for me). I don't care about warranty, as well as triggering KNOX.
Click to expand...
Click to collapse
I can't say that their is not a chance for a brick, but all I am changing is one single flag from "true" to "flase". Their is always a chance at bricking your phone when working with root, tons, custom recovery and kernels as you are messing with the system, but as long as you have either a backup (nandroid) or now how to fix it (flashing stock firmware), their is very little chance of screwing up, and if screwed up you will in almost all cases be able to fix the problem
But yea if the device stuffs up some how e.g. unable to boot you would able to boot your phone into "download mode" and flash stock firmware, although losing you data e.g. apps,. Your phone would be back in a functional state.
Once I am able to get the recovery working properly (booting and running (in permissive mode)) I will root my phone, make a nandroid backup and then I am willing to start adding custom goveners to the kernel and would be willing to share/get help devloping the kernel in the future.
I might be able to provide the kernel later this week (internet limitations are the reason for a long wait) and will post instructions on how to flash the kernel, and how to flash stock firmware (for either you stuffed up and need to fix the phone, or for testing properly with everything at stock and then working the way up, kernel and then twrp)
So if you are willing, i would appreciate the help if given

Matt07211 said:
I can't say that their is not a chance for a brick, but all I am changing is one single flag from "true" to "flase". Their is always a chance at bricking your phone when working with root, tons, custom recovery and kernels as you are messing with the system, but as long as you have either a backup (nandroid) or now how to fix it (flashing stock firmware), their is very little chance of screwing up, and if screwed up you will in almost all cases be able to fix the problem
But yea if the device stuffs up some how e.g. unable to boot you would able to boot your phone into "download mode" and flash stock firmware, although losing you data e.g. apps,. Your phone would be back in a functional state.
Once I am able to get the recovery working properly (booting and running (in permissive mode)) I will root my phone, make a nandroid backup and then I am willing to start adding custom goveners to the kernel and would be willing to share/get help devloping the kernel in the future.
I might be able to provide the kernel later this week (internet limitations are the reason for a long wait) and will post instructions on how to flash the kernel, and how to flash stock firmware (for either you stuffed up and need to fix the phone, or for testing properly with everything at stock and then working the way up, kernel and then twrp)
So if you are willing, i would appreciate the help if given
Click to expand...
Click to collapse
@ Matt07211 If you need a tester. here i am. But what i need is, a step by step for flashing with heimdall on linux mint 18 in easy english. mx phone is sm-g388f with 5.1.1

@VolterPL @yy1
So but this is gonna be an onslaught of questions and information, I would appreciate if you are able to work through this (READ EVERYTHING AT LEAST ONCE) and test/answer my questions.
Some info: When I was searching for info for how to use heimdall for yy1 because I never used it before, I happened to stumble upon a bit of info that I found interesting, and which may solve one of our problems.
In one of the comment sections a user mentioned that their recovery gets replaced each time with stock, a user replied mentioning that their is a script that runs at boot that replaces the recovery if its been tampered with e.g. TWRP, with a stock recovery. So with a bit of digging (ES File Explorer FTW!!) I happened to find the script mentioned in "/system/bin/install-recovery.sh" and the fix is to rename the file, therefore being unable to run at boot and therfore not replacing the custom recovery.
So I believe one (maybe all) of our problems with the recovery being unable to boot can be fixed as follows, would appreciate help/testing here.
Sidenote: I still plan to build a custom kernel, as I would like the ability to run in permissive mode if needed (also including running recovery in permissive mode as well) and adding custom governors as time progress.
Now time for the fix/instructions:
NOTE: I am not responsible for any damage to the phone, system, tripping KNOX, warranty or your insanity
1. Download Odin, I am using version v3.12.3 (sorry yy1, won't have a guide for Haimdell yet as on phone typing this out) and make sure to have ADB, Fastboot and Samsung drivers installed and backup any important files
2. Download newest SuperSu (yep we are gonna try rooting the phone) from this link: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page1
and then put it on the root of the phones internal memory
3. Download the newest TWRP image for our device, which should be 3.0.2-0, link: https://dl.twrp.me/xcover3ltexx/ which should be in the .img.tar format
4. Would probably be best to enable USB Debugging and make sure you have everything backed up and have all files downloaded and Samsung drivers working before preceding any further. If you don't then you should fix that.
5. Launch Odin and boot device into download mode (Power, Volume Down and Home buttons at the same time, for a few seconds.), ensure that the phone is connected to the computer USB port
6. Check Odin and make sure the "added" message is displayed; also, the ID:COM field should now be turned yellow or blue â?? if not, reinstall USB drivers and retry the steps from above.
7. Click on the AP button and then load the TWRP recovery file from desktop. Then, make sure Re Partition and Auto Reboot fields are not checked. Make sure especially that the auto reboot is un-ticked, or this wont work properly as the install-recovery.sh would be able to work before we could get into the recovery at least once.
8. Click "Start" and once finished the â??passâ? message will be displayed; also the ID:COM field will be turned green â?? then you should unplug the USB cord and reboot your device into recovery mode (Reboot straight into recovery or you are gonna have to flash it all over again, due to the install-recovery.sh script)
9. Once in recovery, do a nandroid backup and then flash the SuperSu.zip and reboot
10. Verify that you have root and then download and install a file manager that allows you to modify the /system area, I suggest ES File Explorer and then navigate to "/system/bin/install-recovery.sh" and rename the "install-recovery.sh" to "install-recovery.sh.bak". On a side note, according to the TWRP page, if you boot into TWRP at least once it will patch the stock ROM to prevent this happening. So if TWRP has acctually done this then you probably wont need to modify this file, but try rebooting into recovery at least once after booting to the android OS to see if TWRP is their before modifying the file. If TWRP is their then you can skip the last step.
11. Now due to the "install-recovery.sh" script running at the most recent boot, we will have to re-flash the TWRP recovery once more as the current recovery has been reverted back to stock due to the script. So repeat the steps to flash TWRP one more time and verify that the recovery is persistent across reboots etc.
Outcomes:
- Should have a persistent recovery due to the disabling of "install-recovery.sh" script
- Should have Root on the phone
Stuff wanted to be completed in the future:
- IF this has actually worked, I would like feedback once completed the above steps stating if recovery is persistent across boots and can verify root access. If this worked I will write up a separate thread for rooting this phone and see if we can then get a section on XDA for this phone
- Recompiling the kernel to allow the changing of selinux modes between "enforcing" and "permissive", and as time progresses adding more CPU governors. I will be working to develop this myself so any help would be appreciated.
NOTES/Questions:
- Appreciate your input if this is successful
- If it still flashes the "recovery is not seandroid enforcing" and if the recovery still works in spite of that fact
- If you achieved root, please mention this
- Thank you for taking the time to read and test this if you do
- @yy1 I will write a tutorial for using Heimdall depending on this success of rooting and twrp this phone
Sorry for the wall of text and good luck

G920T DRK Error + FRP Lock after Smart Switch Upgrade Attempt to MM

Got the device from a vendor who said updating through smart switch would not have any issues with a rooted device from 5.1 to MM. Tried flashing stock after smart switch attempt through Odin, no go with DRK error. Attempted to fix DRK error, FRP lock prevents it.
At a loss.

skyalchemist0 said:
Got the device from a vendor who said updating through smart switch would not have any issues with a rooted device from 5.1 to MM. Tried flashing stock after smart switch attempt through Odin, no go with DRK error. Attempted to fix DRK error, FRP lock prevents it.
At a loss.
Click to expand...
Click to collapse
Hi, I have the same problem with a S6 G920T. Were you able to solve the problem?

I got that same problem, did y'all ever figure it out

skyalchemist0 said:
Got the device from a vendor who said updating through smart switch would not have any issues with a rooted device from 5.1 to MM. Tried flashing stock after smart switch attempt through Odin, no go with DRK error. Attempted to fix DRK error, FRP lock prevents it.
At a loss.
Click to expand...
Click to collapse
1st you need to remove frp so flash (combination file) and remove frp
now drk repair drk(device root key)
after removing frp you must flash stock rom and you will see drk is still there so
flash (cf auto root) according to your android version and flash it
you will see error is gone and your phone is in normal
i'm 100% sure it's work for you
please hit thanksif worked
---------- Post added at 09:41 PM ---------- Previous post was at 09:41 PM ----------
skyalchemist0 said:
Got the device from a vendor who said updating through smart switch would not have any issues with a rooted device from 5.1 to MM. Tried flashing stock after smart switch attempt through Odin, no go with DRK error. Attempted to fix DRK error, FRP lock prevents it.
At a loss.
Click to expand...
Click to collapse
1st you need to remove frp so flash (combination file) and remove frp
now drk repair drk(device root key)
after removing frp you must flash stock rom and you will see drk is still there so
flash (cf auto root) according to your android version and flash it
you will see error is gone and your phone is in normal
i'm 100% sure it's work for you
please hit thanks if worked

S7 in recovery boot-loop

Hi,
I just "slightly" bricked my S7 (SM-G930F), and I hope someone can help me. My first S7 (which had Superman-Rom installed) had a burnt-out USB port, so I got a brand new replacement. I made a TWRP backup from the old one and installed that on the new one, but I think I made 1 (or even 2) critical mistakes here: I installed TWRP with ODIN on the phone directly out of the box without starting it once, so I never activated the OEM unlock. Furthermore I restored the backup including the EFS partition. The first start-up went fine, just I couldn't unlock the screen (password not valid). After restarting the phone I got the message "Custom binary locked by FRP lock". Using Smart Switch's device initialization, I could get the phone into download mode again and flashed the stock rom (G930FXXU1DQEI with VD2 carrier) via ODIN. But that got me nowhere, after showing "Installing system update" I just got a screen with "No command". Then the phone rebooted again and went directly to the recovery, showing "Successfully verify for dmverity hash tree". Any attempt to restart the phone just shows the Samsung boot logo two times and then I'm back in recovery, where it then shows "No Support SINGLE-SKU, Supported API: 3, dm-verity error, failed code: 0x02". Trying to install TWRP again just triggers FRP lock. I tried both Smart Switch and ODIN several times in different orders, but nothing works.
Here the timeline again:
1. TWRP-Backup old phone (Superman-Rom)
2. First start new phone directly to download mode, installing TWRP (no OEM unlock)
3. TWRP-Restore new phone, EFS included
4. Rom starts, lock screen password not valid
5. Restart
6. FRP lock
7. Smart Switch
8. Stock rom via ODIN
9. "No command"
10. Starting to recovery, dm-verity ok
11. Restart
12. Starting to recovery, dm-verity error
13. Restart
14. GOTO 12
15. ???
Another interesting thing is that at the first start into recovery after flashing the VD2 stock rom, I also get the message "# MANUAL MODE#, Appling Multi-CSC, Applied the CSC-code : DBT, Successfully applied multi-CSC". As I downloaded the VD2 rom, why is it setting the csc to DBT?
Anyone who can help me break the loop?

Yanai1701 said:
Hi,
I just "slightly" bricked my S7 (SM-G930F), and I hope someone can help me. My first S7 (which had Superman-Rom installed) had a burnt-out USB port, so I got a brand new replacement. I made a TWRP backup from the old one and installed that on the new one, but I think I made 1 (or even 2) critical mistakes here: I installed TWRP with ODIN on the phone directly out of the box without starting it once, so I never activated the OEM unlock. Furthermore I restored the backup including the EFS partition. The first start-up went fine, just I couldn't unlock the screen (password not valid). After restarting the phone I got the message "Custom binary locked by FRP lock". Using Smart Switch's device initialization, I could get the phone into download mode again and flashed the stock rom (G930FXXU1DQEI with VD2 carrier) via ODIN. But that got me nowhere, after showing "Installing system update" I just got a screen with "No command". Then the phone rebooted again and went directly to the recovery, showing "Successfully verify for dmverity hash tree". Any attempt to restart the phone just shows the Samsung boot logo two times and then I'm back in recovery, where it then shows "No Support SINGLE-SKU, Supported API: 3, dm-verity error, failed code: 0x02". Trying to install TWRP again just triggers FRP lock. I tried both Smart Switch and ODIN several times in different orders, but nothing works.
Here the timeline again:
1. TWRP-Backup old phone (Superman-Rom)
2. First start new phone directly to download mode, installing TWRP (no OEM unlock)
3. TWRP-Restore new phone, EFS included
4. Rom starts, lock screen password not valid
5. Restart
6. FRP lock
7. Smart Switch
8. Stock rom via ODIN
9. "No command"
10. Starting to recovery, dm-verity ok
11. Restart
12. Starting to recovery, dm-verity error
13. Restart
14. GOTO 12
15. ???
Another interesting thing is that at the first start into recovery after flashing the VD2 stock rom, I also get the message "# MANUAL MODE#, Appling Multi-CSC, Applied the CSC-code : DBT, Successfully applied multi-CSC". As I downloaded the VD2 rom, why is it setting the csc to DBT?
Anyone who can help me break the loop?
Click to expand...
Click to collapse
Hi
Main issue I see is:
Install EFS partition from one phone to the other.....lets hope you did not mess the IMEI , EFS are device specific.
OEM unlock maybe an issue but Odin flashing should solve it ( most of the times)
You said you flashed with ODin , what file you used CSC or home_csc? if you used CSC did you selected re partition?

MAX 404 said:
Install EFS partition from one phone to the other.....lets hope you did not mess the IMEI , EFS are device specific.
Click to expand...
Click to collapse
Is there a way to restore the original EFS partition? ODIN has the option to clear the EFS, but I could not find any information on what this does, only "stay away from it!!!!!".
MAX 404 said:
You said you flashed with ODin , what file you used CSC or home_csc? if you used CSC did you selected re partition?
Click to expand...
Click to collapse
I tried both, but mainly CSC to also do a factory reset, and I also tried to repartition. Only thing I still haven't tried is "Nand Erase All", because "stay away from it!!!!!"

Yanai1701 said:
Is there a way to restore the original EFS partition? ODIN has the option to clear the EFS, but I could not find any information on what this does, only "stay away from it!!!!!".
I tried both, but mainly CSC to also do a factory reset, and I also tried to repartition. Only thing I still haven't tried is "Nand Erase All", because "stay away from it!!!!!"
Click to expand...
Click to collapse
There are ways to restore the EFS , the question is do you have a copy of the original EFS??
Do not use option in Odin you do not know about.... re partition is known did you use it?
check this info regarding that

Yes, I already tried to repartition. And no, I don't have a backup of the original EFS, I accidentally restored it because I overlooked that is was checked in TWRP (or just checked everything that was there without really looking?).
Regarding Odin it's just sad that nobody seems to know what some of the options really do, maybe some combination could help me.

Yanai1701 said:
Yes, I already tried to repartition. And no, I don't have a backup of the original EFS, I accidentally restored it because I overlooked that is was checked in TWRP (or just checked everything that was there without really looking?).
Regarding Odin it's just sad that nobody seems to know what some of the options really do, maybe some combination could help me.
Click to expand...
Click to collapse
long shot but you could try this.
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
or may have to take it to a service shop ( a good one) they have special boxes with special options to fix this kind of problems

Thanks for your help Max, but it seems I have to pick your last option and search for a service shop. I downloaded the latest available combination firmware, but after installing it the phone gets stuck on the boot screen with displaying "ASV TBL VER = 10; ASV TBL VER2 = 0; NAD: PASSED; NAD ACAT: FAILED; RPMB PROVISIONED" on the top. Reverting to the normal firmware brings me back to the recovery loop. The problem is also that there seems to be no combination firmware for Nougat, all the files are for Marshmallow. Not sure if this is the reason that the phone gets stuck, but I think it likely.

Stuck on Boot screen after flashing TWRP

Hello,
I just flashed the latest ROM for the S8+ (AQL5) and that went well.
Afterwards I tried to flash TWRP, but now the phone is stuck on the Samsung screen.
I then followed the guide I found here to use the BL file of AQF7 in Odin and spam the Start button so I managed to get into TWRP.
Question is, what do I do next? I restart the system it's the same problem all over again.
No one explains anywhere what to do in TWRP to save the phone.
Can I remove TWRP or somehow save the phone (without wiping my data)
Please help

Can you get to download mode? Then go to ODIN and redo your flashing of the OS and then TWRP. After the flash of TWRP, immediately boot into TWRP, and do Verity if you want that, and your root, if not already done. Clear Dalvik/cache and reboot to system.
It is not uncommon for folks, following TWRP flash, to get stuck in boot loop, unfortunately. Can take a little time, but you will get through it and finally to System.

But I thought all new firmware versions are incompatible with TWRP and cause this error.
I might try to install TWRP again if I flash the latest compatible version (I think it's the F7 one).
Does "Verify" in TWRP make that annoying "Your phone is not verified" message go away? The only option is to Reset phone when that thing comes up and I don't want to do that.
I managed to get out of that by reflashing the AQL5 version and just not installing TWPR.
Kind of scared to retry because everything goes wrong when I try to follow the guides on here or youtube

nkomp18 said:
But I thought all new firmware versions are incompatible with TWRP and cause this error.
I might try to install TWRP again if I flash the latest compatible version (I think it's the F7 one).
Does "Verify" in TWRP make that annoying "Your phone is not verified" message go away? The only option is to Reset phone when that thing comes up and I don't want to do that.
I managed to get out of that by reflashing the AQL5 version and just not installing TWPR.
Kind of scared to retry because everything goes wrong when I try to follow the guides on here or youtube
Click to expand...
Click to collapse
Would you please provide the info from my first post? and Exynos of Snapdragon?

JeffDC said:
Would you please provide the info from my first post? and Exynos of Snapdragon?
Click to expand...
Click to collapse
I have Exynos - model SM-G955F
Yes I can go to download mode but I won't do the things you ask because they're guaranteed to soft-brick the phone again and I have it working now

i have the same problem, followed this guide https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-root-galaxy-s8-crgh-rom-t3846009 managed to get to TWRP no problems, once i reset the device though im stuck at the samung galaxy s8+ boot screen and can't get it off
any suggestions ? i did try to search but this old thread was the only relevant one i could find

stuck on boot screen after flashing twrp for magisk manager
i flashed magisk manager in twrp youtube.com/watch?v=r3R9kiBIx34 by this and now not booting to android . before i had this i reflashed miui 11 using official software and coulnt be sucess this time also please help me any one . my mobile is redmi 6 pro.:crying::crying::crying::crying:

Oem locked, frp block, and drk help

Hey guys. I'm in a hell of a bind and could use some help.
My Galaxy Note 5 (N920T, rooted) was running fine on this ROM: https://forum.xda-developers.com/tm...m-qc6-lite-rom-bloated-knoxed-odexed-t3598686 ; however, I had disabled OEM unlock at one point to try and fix a random app I was playing with. The battery died not long after, causing the phone to reboot. On power, it failed to boot due to custom binary block from FRP, so I decided to try and run the usual troubleshooting of flashing a stock ROM via Odin. Stock images will flash (tried 5.1.1, 6.1, and 7); however, when they try to install I get the error for no DRK. Sometimes I'll also get a dm-verity error as well... So I then tried to flash TWRP or any recovery via Odin to let me fix this issue; however, any custom recoveries I try to flash are being blocked by FRP.
So, I'm in a loop. I can't use my initial ROM because FRP, however I also can't install a stock ROM because of missing DRK, AND I can't fix the DRK or verity errors because I can't install a recovery capable of doing so because of FRP.
IMEI is intact when I look into Download mode, but I can't seem to get anything to work. I've tried the FRP Tool and crack, but that gives me FRP blocks as well (USERDATA).
Am I boned?

B U M P
Anyone?

same situation, going to try flashing it to stock. Can we just flash a stock bootloader or do we need to start over?
Got it working by flashing stock rom with odin so maybe not exact same situation as you. Hard to find a filehosting site with good download speeds and spent all day trying to get latest stock note 5 firmware. Well good for now.. All started because of a wrong flip of a switch *bangs head on desk*

You need to do a few things. First you need to wipe everything in TWRP including format data, so love your files to some other storage. In Odin go to options and turn off auto reboot. Turn on f reset time, phone bootloader update and Nand Erase All. You need to know that this doesn't always work, if you can't unlock it this way try disabling encryption after flashing stock and TWRP and flash Magisk. Let me know how it goes.

Metabolic12 said:
You need to do a few things. First you need to wipe everything in TWRP including format data, so love your files to some other storage. In Odin go to options and turn off auto reboot. Turn on f reset time, phone bootloader update and Nand Erase All. You need to know that this doesn't always work, if you can't unlock it this way try disabling encryption after flashing stock and TWRP and flash Magisk. Let me know how it goes.
Click to expand...
Click to collapse
Got as far as getting the firmware flashed via Odin, but when I first boot I get "Device does not have DRK" error. I cannot install TWRP or any custom recovery through Odin due to FRP lock.

x24veggie said:
Got as far as getting the firmware flashed via Odin, but when I first boot I get "Device does not have DRK" error. I cannot install TWRP or any custom recovery through Odin due to FRP lock.
Click to expand...
Click to collapse
if all you are getting is frp lock just flash back to stock like I did and start over rooting etc.

craig198 said:
if all you are getting is frp lock just flash back to stock like I did and start over rooting etc.
Click to expand...
Click to collapse
That's not all. Basically, it goes,
Flash back to stock
Reboot
Can't finish ROM install because DRK is unavailable
Can't install anything in locked, stock android recovery
TWRP, autoroot, etc. is blocked from Odin by FRP

craig198 said:
same situation, going to try flashing it to stock. Can we just flash a stock bootloader or do we need to start over?
Got it working by flashing stock rom with odin so maybe not exact same situation as you. Hard to find a filehosting site with good download speeds and spent all day trying to get latest stock note 5 firmware. Well good for now.. All started because of a wrong flip of a switch *bangs head on desk*
Click to expand...
Click to collapse
No. It started because you didn't back up your phone properly with twrp before going flash crazy
---------- Post added at 08:52 AM ---------- Previous post was at 08:47 AM ----------
x24veggie said:
That's not all. Basically, it goes,
Flash back to stock
Reboot
Can't finish ROM install because DRK is unavailable
Can't install anything in locked, stock android recovery
TWRP, autoroot, etc. is blocked from Odin by FRP
Click to expand...
Click to collapse
https://www.google.ca/amp/s/forum.x...to-solve-dm-verity-verification-t3293306/amp/ have you tried this? If we can figure this out please don't ever play with oem or have a stock recovery ? that's your security blanket