s7 edge G935F with FRP lock & DRK error - Samsung Galaxy S7 Edge Questions and Answers

s7 edge G935F with FRP lock & DRK error - Samsung Galaxy S7 Edge Questions and Answers

hi, I flashed the latest stock ROM of s7 edge from sammobile ( G935FXXS8ETC1 ) then I had dm-verity error / the developer options off / FRP on and I can't do anything I cant flash TWRP I can't flash any unofficial files ...... help, please !!!!!

leonardo8877 said:
hi, I flashed the latest stock ROM of s7 edge from sammobile ( G935FXXS8ETC1 ) then I had dm-verity error / the developer options off / FRP on and I can't do anything I cant flash TWRP I can't flash any unofficial files ...... help, please !!!!!
Click to expand...
Click to collapse
Xda's search bar is your best friend mate, be sure to use it before posting
Sent from my hero2lte using XDA Labs

1. Download a U8 firmware for your device which is SM-G935F. You can download it in sammobile.com , updato.com or samfw.com
2. After the download is completed, you need to extract the downloaded rom (I recommend using apps like 7zip or Winrar)
7-zip: https://www.7-zip.org/download.html
3. After you extract the file, you will be greeted with files saying
AP_XXXXXXXXXXX
BL_XXXXXXXXXXX
CP_XXXXXXXXXXX
CSC_XXXXXXXXXX
Home_CSC_XXXXXXXXX
4. Extract the AP_XXXXXXXXX with 7-zip or Winrar
5. In my case, 3 files and 1 folder were extracted which were
system.img.lz4
boot.img.lz4
recovery.img.lz4
meta-data (This is a folder)
Note: In your case, there might be different amount of files with different extensions
6. Copy "boot.img.lz4" to another folder (lets call the folder Hello for now) and rename the boot.img.lz4 to "recovery.img.lz4"
7. Make a backup of the original "recovery.img.lz4" and "boot.img.lz4" and "meta-data" and delete those files/folders
8. Copy the "recovery.img.lz4" file from Hello to your folder which contains system.img.lz4
9. Now, your folder should only contain system.img.lz4 and recovery.img.lz4 (renamed boot.img.lz4)
10. Download the Auto Tar folder
https://www.mediafire.com/file/ah20h...s.com.rar/file
11. Extract the autotar file using 7-zip or winrar
12. Copy all the content inside the autotar file and paste it to your folder containing system.img.lz4 & recovery.img.lz4 (renamed boot.img.lz4)
13. Open the Autotar application
14. Select system.lz4.img and recovery.img.lz4
15. Press on make .md5 & type the name on the box beside select files
Note: There should not be any special characters in the name, I recommend not using any spaces, numbers, capital letters or special characters like [email protected]#
16. Then, wait until it says done, usually took us around 15 Minutes
17. Open Odin, if you dont have odin download it
https://odindownload.com/download/#.Xq6i9pnBXDc
18. In Ap tab, choose the newly created .md5 file and do the same for CSC, CP & BL
19. Connect your phone to the PC in download mode
20 Then, flash
Note: If the verification fails, rename the newly created .tar.md5 file and remove .md5 from its name, then we will be left with .tar file
21. Set up your phone and before switching off/ restarting or doing anything "Special" enable OEM unlock, or charge your phone if it has less battery, which was the issue in my case
22. Restart your phone and you will be greeted with No Command screen. The first time I saw that again, I got freaked out but dont worry the solution is pretty simple due to the fact we dont have FRP lock anymore
23. Go to download mode and flash UNMODIFIED CP, CSC, AP & BL
24. You will get the no command screen again, no worries though, go to TWRPP websiet and download TWRP for your device
https://twrp.me/
25. Enter download mode and flash the recovery through the AP tab
26. Download this
https://zackptg5.com/downloads/Disab...03.04.2020.zip
27. You will be rebooted to the TWRP screen. And by the way, ALLOW SYSTEM MODIFICATIONS
28. Connect your phone to the PC and transfer the previously downloaded Dm verity file and copy it to your phone
29. Go to Install in your TWRP screen and locate the file and install it
30. Clear Dalvik Cache and reboot
Edit: Alternatively, In the last steps, you can flash turbo luke's twrp instead of official twrp, then select format option in twrp wipe, then flash no-verity-force-encrypt
Then flash magisk from here : https://github.com/topjohnwu/Magisk/releases/tag/v20.4
In all of doing this, don't swipe for system modifications in twrp, it is basically useless and obsolete now, as magisk does everything without modifying system.
Ofcourse, this only applies to stock rooted rom and stock based debloated custom roms (which have non-modified system)
Edit 2: This a copy pasta
Credit: @turbolukex5 @shah22
Sources:
https://forum.xda-developers.com/s7-edge/help/bricked-s7-edge-t4039153
https://forum.xda-developers.com/s7-edge/help/rip-s7-edge-g935fd-one-help-t4082203
https://forum.xda-developers.com/s7-edge/development/recovery-upstreamed-twrp-android-8-1-t3921785

but frp is on how can i flash twrp @Rapidfayaround

leonardo8877 said:
but frp is on how can i flash twrp @Rapidfayaround
Click to expand...
Click to collapse
Bruh....Did you read that properly. First flash the modified AP, then you will boot then enable OEM Unlock which will disable FRP Lock, then you can flash TWRP. Or just tell me the CSC for your country, I will do all this and send you the modified AP.

Have the same problem with G935FXXS8ETC1
Rapidfayaround said:
Bruh....Did you read that properly. First flash the modified AP, then you will boot then enable OEM Unlock which will disable FRP Lock, then you can flash TWRP. Or just tell me the CSC for your country, I will do all this and send you the modified AP.
Click to expand...
Click to collapse
Hallo, i have the same problem after i disabled develeper options after root(G935FXXS8ETC1)
My country code is DBT, can you send me please the modded AP File. Thanks.

Autotar application dont works for me
I have done all steps but autotar does not work for me. There is no output. Only 1kb in MD5.
That can not work.

Fixed your problem ?
leonardo8877 said:
hi, I flashed the latest stock ROM of s7 edge from sammobile ( G935FXXS8ETC1 ) then I had dm-verity error / the developer options off / FRP on and I can't do anything I cant flash TWRP I can't flash any unofficial files ...... help, please !!!!!
Click to expand...
Click to collapse
I tried to convert the img,lz4 file with auto tar . No chance. Next time i will try to flash a combination rom.
Perhaps this will solve my oem unlock problem. i can not aktivate it, thats the main problem. I waited 7 Days, but oem unlock ist still not possible.:crying:
I have the same problem. FRP ON, no twrp or custom rom. OEM can not be unlocked to flash twrp.
DId you have success in any way?
LG

@chris1abc download 7zip from this link: https://www.7-zip.org/download.html after installing it on your pc select two files system and recovery ( renamed boot ) file then select 7zip like the photo below then select open archive then choose the file type and make it tar.
images link: https://drive.google.com/open?id=1rxbY-Ytxsb1yzcQ4io5yZE6gJHoTRQP_

leonardo8877 said:
@chris1abc download 7zip from this link: https://www.7-zip.org/download.html after installing it on your pc select two files system and recovery ( renamed boot ) file then select 7zip like the photo below then select open archive then choose the file type and make it tar.
images link: https://drive.google.com/open?id=1rxbY-Ytxsb1yzcQ4io5yZE6gJHoTRQP_
Click to expand...
Click to collapse
Thanks, i managed to convert the files. Still on stock rom. I had no sucess, flashed the files in different ways.
BL CP HOMESCS; only ap etc. etc.... I spendend many hours but sometimes the phone did not boot,when it booted I was not able to unlock oem in developer options.
I will wait new 7 days, perhaps i have luck. Grrrrrr....... **** Samsung I WANT MY TWRP BACK. With Samsung S5 i had not this trouble.
Cause of this i will not buy any Samsung products neither Tv or anything else. SAMSUNG WANTS TO FORBID THE PEOPLE TO ROOT AND FLASH THEIR PHONES.
Hey, I am over 18.
s7,s8, S9,s10, S20 the people get often problems to root their phones. Will see what happens after 7 days.

chris1abc said:
Thanks, i managed to convert the files. Still on stock rom. I had no sucess, flashed the files in different ways.
BL CP HOMESCS; only ap etc. etc.... I spendend many hours but sometimes the phone did not boot,when it booted I was not able to unlock oem in developer options.
I will wait new 7 days, perhaps i have luck. Grrrrrr....... **** Samsung I WANT MY TWRP BACK. With Samsung S5 i had not this trouble.
Cause of this i will not buy any Samsung products neither Tv or anything else. SAMSUNG WANTS TO FORBID THE PEOPLE TO ROOT AND FLASH THEIR PHONES.
Hey, I am over 18.
s7,s8, S9,s10, S20 the people get often problems to root their phones. Will see what happens after 7 days.
Click to expand...
Click to collapse
Still not getting what your problem is mate .. you can boot but not enable oem unlock in developer option ?? This isn't possible ..
Sent from my hero2lte using XDA Labs

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
shah22 said:
Still not getting what your problem is mate .. you can boot but not enable oem unlock in developer option ?? This isn't possible ..
Sent from my hero2lte using XDA Labs
Click to expand...
Click to collapse
yes, that is my problem. I was able to install the modified AP and flashed it how you described it. In developer option i can toggle the button,
cause it went back. This problem stays with the modified AP ROM and also on unmodified stock rom.
There is no green light . It just goes back. MY Status is FRP LOCK on while staying on stock rom or AP modified rom. I have no google frp lock only by Samsung.
Odin picture is only for example what i did (removed you see), i must use my s7 edge to take the picture.
AP FILE was flashed with 3 Files:
recovery.img + (renamed boot.img)+ system.img. + boot.img. converted in one AP FILE
with BL CP SCSHOME in Odin. The phone booted now in system, but in dev.options the oem button can be actived but it struggles back. That´s the fact.

chris1abc said:
yes, that is my problem. I was able to install the modified AP and flashed it how you described it. In developer option i can toggle the button,
cause it went back. This problem stays with the modified AP ROM and also on unmodified stock rom.
There is no green light . It just goes back. MY Status is FRP LOCK on while staying on stock rom. I have no google frp lock only by Samsung.
Click to expand...
Click to collapse
You mean when you enable the toggle, it automatically gets off ??
This is weird indeed, first time seeing this..
Did you bought your phone second hand ? It maybe that its hardware is semi modified ..
Sent from my Legendary Hero2LTE using Tapatalk

shah22 said:
You mean when you enable the toggle, it automatically gets off ??
This is weird indeed, first time seeing this..
Did you bought your phone second hand ? It maybe that its hardware is semi modified ..
Sent from my Legendary Hero2LTE using Tapatalk
Click to expand...
Click to collapse
Yes, i bought it second hand , but the people did not modiefie the phone. It had stock rom an KNOX 0+0.
The oem toggle did not go back before I installed TWRP and moro Kernel. Do you know if its possible that oem unlock will not go back automically after waiting for 7 days ?

chris1abc said:
Yes, i bought it second hand , but the people did not modiefie the phone. It had stock rom an KNOX 0+0.
The oem toggle did not go back before I installed TWRP and moro Kernel. Do you know if its possible that oem unlock will not go back automically after waiting for 7 days ?
Click to expand...
Click to collapse
Can't be sure, RMM lock is not implemented on S7 series per my knowledge, but yeah you can try waiting..
Also confirm that your oem unlock toggle automatically turns off when enabled ??
Sent from my Legendary Hero2LTE using Tapatalk

shah22 said:
Can't be sure, RMM lock is not implemented on S7 series per my knowledge, but yeah you can try waiting..
Also confirm that your oem unlock toggle automatically turns off when enabled ??
Sent from my Legendary Hero2LTE using Tapatalk
Click to expand...
Click to collapse
Yes the unlock toggle automatically turns off when enabled . I succsefully flashed AP Rom and also Stock Rom. In both cases the phone boots normally, but there is the problem
with the toggle. Its a pity for the work and lot of tries.

Its the first time im coming across this issue .. don't know then, i tested this solution on many people and it always worked .. you sure your phone isn't a hardware semi-modified snapdragon variant to show itself as a exynos one ? That could make sense why the toggle can't be enabled but still its really weird ..
Sent from my hero2lte using XDA Labs

i have never heared about a semi modified snapdragon. On cpuz or ohter apps it shows me exynos . The last try is too flash the ap file with the meta folder, that i did not tried. Perhaps i mayed a fault while flashing or converting, i dont know. But the phone starts with the modified ap file, but how i said, i was not able to turn oem on.
Next time i will start another try with flashing meta folder in ap file. Perhaps i have luck.
No chance, i installed ap with meta folder. Phone booting in system , oem unlock not possible.

shah22 said:
Its the first time im coming across this issue .. don't know then, i tested this solution on many people and it always worked .. you sure your phone isn't a hardware semi-modified snapdragon variant to show itself as a exynos one ? That could make sense why the toggle can't be enabled but still its really weird ..
Sent from my hero2lte using XDA Labs
Click to expand...
Click to collapse
i have checked with phone info and samsung imei the phone is 100% original.

Oem unlock not possible, still on stock rom 8.
chris1abc said:
i have checked with phone info and samsung imei the phone is 100% original.
Click to expand...
Click to collapse
SM- G935F EXYNOS 8890
After trying a last flash with nand erase and repartion with stock rom binary 8 , the problem still is not solved.
Download mode shows FRP on. Status official.
FRP Lock for hardware is still alive. I normally can sign in to my google account with my device.
The phone boots normally but in dev. options, the oem button automatically goes back. I am not able to solve the problem.
Stock rom works,but no way to flash TWRP cause custom binary blocked by FRP. Its possible to flash different stock roms with binary 8, all is working except s- health.
(notice: phone is rooted, but root has gone). I have no chance to flash a rom below binary 8.
History: I installed TWRP with moro Kernel on Stock rom. All works, after accidentally i disabled the dev. options i got the dead android and i was not able to go back in TWRP
recovery. Twrp had disappeared.
When i start the revovery the "dead android no command" appears and after 1 minute the stock recovery appears.
I read ( Google research) , there was a user who had the same problem with a s7 g930f. He could flash stock roms but no other and he also could not unlock oem in any
rom.
I would be happy to hear from somebody who had a solution. I think there is a new security patch by samsung. Meanwhile i stay on latest stock rom and hope sometime i can unlock oem in dev. options. I have tried all incl. flash with Nand Erase in Odin ( you should not do this, i heard), but nothing worked for me.

Related

Fix bootloop in redmi note 3 (no recovery ,no edl mode)

After trying to flash the latest 7.1.1 cm 14 ropms many people ended up in bootloop where your phone switch on ,shows mi logo and rebbot again. Many where not able to enter recovey mode also.. Now i come up with a perfect soluton for you all on how to fix these issues in your phone..Lets Get started..
If anything goes wrong iam not responsible.Do it At your Own Risk.
Requirements
------------------
1. Enter edl .rar (attached below)
2.Miui Stock Rom (FastBoot). Download it from(only use this version) here
3.Phone Must have Charge of 50% or more.
4.Unlock Boot loader.zip (Attched Below)
6.MIPhone Tools and install it .Get it from here
6.Extract all the file
7. PDA Net.(Optional,but installing will be useful). Get it from here
Once you have all of the file we can move on
Steps
------
1. Put Your Phone into fastboot mode by pressing Vol Down and power button at same time.
2.Connect your Phone With Your PC
3.Run EDL Mode.exe from the zip Enter edl.. Now your phone must be in edl mode. You can see a light blinking at the top of your phone.
4. From the Unlock Boot Loader folder copy "emmc_appsboot.mbn" to the rom folder ie)
kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global--> images--> paste it there (replace/overwrite if existing)
5. Once the above step is done, Open MIFlash tool as administrator. Browse the folder
kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global and select it..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6.From the drop Down Menu Select Advanced.
7.Set Fastboot Script As Flash_ALL.Bat.
8.Set Flash Programmer As prog_emmc_firehose_8976_ddr.mbn from images folder.
9. Set RAW Xml File as rawprogram*.xml from images folder
10. Set Patch XML File as patch*.xml from images folder.
11. Video Help HERE.... Watch from 2.40 (Ignore the other portion,We dont need that Part)
Special [email protected] for the video.. I didn't made that video..
12. Once The Above step is done. Click REFRESH OPTION,and you will see Phone detected By The Name COMXX.(XX will be a number)
13.Click Flash and Wait for some time and allow the phone to reboot.
14.Once all the step is done your phone will be good to use..:fingers-crossed: :fingers-crossed:
UNLOCKING BOOT LOADER AND INSTALLING TWRP AGAIN
-------------------------------------------------------------------------
1.Once Your Phone Reboots successfully enable USB Debugginf From Developer Option.
2.Connect Your phone to your PC and Open CMD as administrator.
3.Type in "adb devices".
4. Cmd will show a random number and Device (Everyone will be knowing this,but for info only iam writing it here)
5.Type "adb reboot bootloader". Now your phone will boot into fastboot mode.
6.Type "fastboot oem device-info" to get device status.
7.Type "fastboot oem unlock-go" to unlock bootloader.
8.Again type "fastboot oem device-info" to check to find if device is unlocked.(Do not reboot YET)
9. Now Downlaod TWRP from HERE
10. Now Got to the folder containig TWRP . By holding the Shift Key Of key Board ,right click the mouse and select OPEN COMMAND WINDOW HERE.
11. Type "fastboot flash recovery recovery_filename.img"
12.Type "fastboot reboot".
You Phone will be good to go. If anything goes wrong or you have any doubt Comment Below do not pm me..i will not reply..
If this thread helpef you thumbs up and do comment and shre this post

So i do not need to unlock the boot loader before using MiTool to flash phone via EDL

ahh988 said:
So i do not need to unlock the boot loader before using MiTool to flash phone via EDL
Click to expand...
Click to collapse
Nope if phone is bricked enter fastboot mode and run enter edl.exe to enter edl,flash ROM using mi flash tool

adithyan25 said:
Nope if phone is bricked enter fastboot mode and run enter edl.exe to enter edl,flash ROM using mi flash tool
Click to expand...
Click to collapse
I did that but phone is still stuck . I'm getting infinite boot animation ?

ahh988 said:
I did that but phone is still stuck . I'm getting infinite boot animation ?
Click to expand...
Click to collapse
Boot animation or simply mi logo and then vibrating and again rebooting???
If mi flash tool shows successfully done without any errors then
Try this
Roeboot to fast boot and type
fastboot oem unlock-go
I guess it will be fixed

adithyan25 said:
Boot animation or simply mi logo and then vibrating and again rebooting???
If mi flash tool shows successfully done without any errors then
Try this
Roeboot to fast boot and type
fastboot oem unlock-go
I guess it will be fixed
Click to expand...
Click to collapse
I am stuck at boot animation with the three white dots spinning for ever ? will try to do as you said

I tried fastboot oem unlock-go but i get response: token verification failed and device still stuck on bootanimation

well, i think this caused by relocking bootloader after we flash a new firmware. if that happens, just go in fastboot mode by hold power button + volume down, then unlock it again using mi unlock. reboot it..your twrp is back.
no need to enter edl mode & install twrp again, btw thanks..this is helpful

nitephoenix said:
well, i think this caused by relocking bootloader after we flash a new firmware. if that happens, just go in fastboot mode by hold power button + volume down, then unlock it again using mi unlock. reboot it..your twrp is back.
no need to enter edl mode & install twrp again, btw thanks..this is helpful
Click to expand...
Click to collapse
always my pleasure
For some mi unlock stucks at 50%.. I was one of them...every time I try fails...so I found this was the only way for those who can't access it using mi unlock

tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted

nitephoenix said:
tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted
Click to expand...
Click to collapse
Yeah...I know that...but it does not support volte. .only abhisheks fw sprt volte

nitephoenix said:
tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted
Click to expand...
Click to collapse
@nitephoenix
Can we then flash update marshmallow global firmware this way? (Just delete emmc apsbot.mbn file inside the firmware). Thanks

Pleroma said:
@nitephoenix
Can we then flash update marshmallow global firmware this way? (Just delete emmc apsbot.mbn file inside the firmware). Thanks
Click to expand...
Click to collapse
don't flash official miui from twrp (you better do it in edl mode), but yes you can flash custom miui like miui eu, miuipro, multirom, epic miui etc from twrp. and..after u delete the emmc file inside the firmware which is included on every miui rom, your bootloader will be safe

nitephoenix said:
don't flash official miui from twrp (you better do it in edl mode), but yes you can flash custom miui like miui eu, miuipro, multirom, epic miui etc from twrp. and..after u delete the emmc file inside the firmware which is included on every miui rom, your bootloader will be safe
Click to expand...
Click to collapse
I used to flash it via twrp ..(by deleting bootllader file) followed by flashing lazyflasher...I didn't faced any prblm yet

Mine behaves different
I tried restoring the backup it started to back up and completed sucessfully but when i reboot there comes Mi logo and again it boots to TWRP Recovery .... Same case with any ROM ... Kindly tell me what to do.
ZCX recovery i have.

sarabeshsab said:
I tried restoring the backup it started to back up and completed sucessfully but when i reboot there comes Mi logo and again it boots to TWRP Recovery .... Same case with any ROM ... Kindly tell me what to do.
ZCX recovery i have.
Click to expand...
Click to collapse
Probably the problem with bootloader file

not a whole lot of talk anywhere else so i'll try here. i just got my kenzo few days ago, jumped the gun and started trying to get twrp on it. i'm assuming the bootloader was locked. As of right now it wont boot up, its in edl mode maybe... red led flashes and i can upgrade driver to 9008. sometimes its recognized by miflash and when it is and i try to flash stock fastboot it gives me an error. i know thats a lot to take in but i'm trying to cover all my bases. the phone came from overseas so sending it back isnt really an option. any help is appreciated.

Jjleininger said:
not a whole lot of talk anywhere else so i'll try here. i just got my kenzo few days ago, jumped the gun and started trying to get twrp on it. i'm assuming the bootloader was locked. As of right now it wont boot up, its in edl mode maybe... red led flashes and i can upgrade driver to 9008. sometimes its recognized by miflash and when it is and i try to flash stock fastboot it gives me an error. i know thats a lot to take in but i'm trying to cover all my bases. the phone came from overseas so sending it back isnt really an option. any help is appreciated.
Click to expand...
Click to collapse
Download eiter China based ROM or ROM from post.
Mi flash tool have many prolems.
Some tips:-
Make sure driver enforcement is disabled in PC.
All drivers including PDA net is installed.
Copy paste the unlocked bootloade file inside images folder and replace original one. Even after tryig this method it fails try my other method unbrick viafasrboot

uhm, this does not work for some reason...
i did everything as you said but in the end it just says cathasrophic error and something

After flashing i get Mi logo, vibration and reboot, please help

[Tutorials] How To Root Lenovo K8 Note & Install TWRP(UnOfficial) + Stock Rom

Warning
Before Proceeding backup your data
TRY at OWN risk I'm NOT Responsibe if you BRICK YOUR DEVICE
Update- This method is tested & working with latest ota update NMB26.54-74
[/CENTER][/B][/SIZE][/COLOR]
IF ANYTHING GOES WRONG Download & Flash Stock ROM
Stock ROM link
SPFlashTool link
Updated Stock ROM 54-74 GDrive - here
New Oreo 27.43-20 Link
Old version Stock ROM Google Drive Link Stock Rom
nvram backup file by @peacelover94 - here
Solution For
>Tool img DL fail
Just check/tick these option in spflashtool settings & Flash stock rom again
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Video Guide For Stock Rom Flashing - Youtube
How to Flash Stock Rom via Fastboot Method -
1. Open CMD by Shift + Right Click in Folder where your stock firmware .img files are.
2. Reboot to Fastboot Mode by using cmd command
adb fastboot rebootOr
Switch off then Press & Hold Vol Up + Power button for while once menu appeared Select fastboot by using Vol Up key & confirm by pressing Vol Down Key
3. In fastboot type following command in CMD Window
For checking devices is connected in fastboot enter
fastboot devicesIf Connected then proceed following commands
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img flashing system takes 10+ mins
fastboot flash data userdata.img
fastboot reboot
Download & Install ADB from here
First Unlock your bootloader
1. First of all, enable the Developer Option
To Enable the Developer Option, Go to your Settings -> About -> Software Information -> More -> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled"
2. Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
3. Now connect your phone to Computer using USB Cable.
4. When you connect your Phone to Computer, please wait until all the drivers get installed.
5. Open a command prompt window by pressing Shift Key + Right Mouse Click.
6. Now type the command below to reboot your phone to bootloader
adb reboot bootloader7. If you see a pop up to allow USB Debugging on your phone, Click OK.
8. proceed to unlock the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
fastboot oem unlockSay Yes to unlock bootloader and then it will some time format your data
9. Reboot Your Device , You will see Orange Status bla bla bla Don't panic Its normal thing now setup your device but do not restore backup yet
Flashing TWRP and ROOT
Updated Black Screen Fix TWRP - Download
Old Download TWRP
Download latest Magisk zip from here
Or
SuperSu zip from here
Flahed & Tested SuperSU v2.82 works fine but SafetyNet Fails
Sock Recovery if needed Link
1. Connect your device to PC
2. Open CMD by Shift+Right click open cmd where your TWRP_3.1.1.0.img is downloaded.
3. Reboot to Bootloader by
adb reboot bootloader4. Now enter following command in fastboot
fastboot flash recovery TWRP_3.1.1.0.img5. DO NOT USE fastboot reboot
Use "vol up + down + power button" to manually switch off you k8 note, otherwise twrp will restore to stock if you use fastboot reboot command.
6. After Switch Off Press & hold vol up + power button then select recovery by vol up & press vol down key to enter in recovery.
7. Now Wait for 30 Sec/ till phone vibrates, Then press power button + vol up simultaneously until you see twrp lock screen.
8. Just Cancel if It asks for Enter password to decrypt and Allow modification by swipe.
9. If you see internal storage 0mb Then GoTo Wipe and FORMAT DATA once & reboot to recovery
10. GoTo install browse and select Magisk.zip or SuperSU.zip & flash.(optional if needed install Busybox for Android NDK by osm0sis magisk module for busybox)
11. Reboot Enjoy.
Known bug in TWRP-
Battery always shows 50% in TWRP
Video Guide https://youtu.be/HrbppEWlOhs
Join Lenovo K8 Note Development Group on Telegram for direct Conversation Link
WhatsApp Group Link
Enable Wireless Display/MiraCast Magisk Module - Video
Thanks to:
@andy_zhang - for stock rom post link
and me @ysalunke007 for TWRP
NEXT CUSTOM ROM

Big Thanks for the Tutorial. If anything happens wrong while rooting like boot loop or something worse, is there stock rom or firmware to flash or push through adb ?

Yes
peacelover94 said:
Big Thanks for the Tutorial. If anything happens wrong while rooting like boot loop or something worse, is there stock rom or firmware to flash or push through adb ?
Click to expand...
Click to collapse
yes, there is stock ROM
link also provided in this post end.
btw here's direct link Stock ROM
FlashTool link

ysalunke007 said:
yes, there is stock ROM
link also provided in this post end.
btw here's direct link Stock ROM
FlashTool link
Click to expand...
Click to collapse
Thank you very much. The flash tool link does not seems to work. Hope its SP flash tool you are talking about.

flash via adb fastboot methoad i have succesfully flash adb method
peacelover94 said:
Big Thanks for the Tutorial. If anything happens wrong while rooting like boot loop or something worse, is there stock rom or firmware to flash or push through adb ?
Click to expand...
Click to collapse

Nice Job
Finally rooting tutorial for Lenovo K8 Note has become available.

Does SuperSu work fine?

Anas Rahman said:
Does SuperSu work fine?
Click to expand...
Click to collapse
Not tested by me but some user says in original rom post that he flashed superSU from old twrp also works fine.

peacelover94 said:
Thank you very much. The flash tool link does not seems to work. Hope its SP flash tool you are talking about.
Click to expand...
Click to collapse
Yes it's SP flash tool but you can use adb fastboot also

ysalunke007 said:
Not tested by me but some user says in original rom post that he flashed superSU from old twrp also works fine.
Click to expand...
Click to collapse
I'll confirm it tomorrow

ysalunke007 said:
Yes it's SP flash tool but you can use adb fastboot also
Click to expand...
Click to collapse
Please tell me how to flash firmware.Im new to this device firmware flashing

lenrussel said:
Please tell me how to flash firmware.Im new to this device firmware flashing
Click to expand...
Click to collapse
It's easy bro check this guide
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Fastboot Guide
http://www.stupdroid.com/2016/08/flash-stock-rom-via-fastboot-on-android.html?m=1

Does the rom link given here unzips perfectly?
Because i saw in another thread of Lenovo K8note titled firmware, users unable to unzip due to error in system img. Also downloading from baidu needs a user id. If its possible could you or anyone else reading this upload it in some other online storage drive. Im little bit worried about getting a worse situation while rooting. Even if it goes wrong i can use the stock firmware to make it back.

peacelover94 said:
Does the rom link given here unzips perfectly?
Because i saw in another thread of Lenovo K8note titled firmware, users unable to unzip due to error in system img. Also downloading from baidu needs a user id. If its possible could you or anyone else reading this upload it in some other online storage drive. Im little bit worried about getting a worse situation while rooting. Even if it goes wrong i can use the stock firmware to make it back.
Click to expand...
Click to collapse
There is mega download link available too
https://forum.xda-developers.com/an...8note-original-firmware-t3679499/post73946000

lenrussel said:
There is mega download link available too
https://forum.xda-developers.com/an...8note-original-firmware-t3679499/post73946000
Click to expand...
Click to collapse
Thanks for the reply. Anyhow got a work around for downloading from baidu using chrome extension, without account. Just wanted to confirm whether the firmware zip is working fine. If some one used it and been successful, please do tell me.

ysalunke007 said:
It's easy bro check this guide
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Fastboot Guide
http://www.stupdroid.com/2016/08/flash-stock-rom-via-fastboot-on-android.html?m=1
Click to expand...
Click to collapse
Do i have to unlock bootloader again after flashing the firmware in order to root the device?

lenrussel said:
Do i have to unlock bootloader again after flashing the firmware in order to root the device?
Click to expand...
Click to collapse
Yes, I think so. Anyhow there is no need to unlock oem again if you are flashing the rom via TWRP. Anyhow let someone confirm about it.

peacelover94 said:
Yes, I think so. Anyhow there is no need to unlock oem again if you are flashing the rom via TWRP. Anyhow let someone confirm about it.
Click to expand...
Click to collapse
There is a error while extracting zip file of the firmware .just checked, I downloaded it from mega.i want to confirm if its the same for baidu also

lenrussel said:
Do i have to unlock bootloader again after flashing the firmware in order to root the device?
Click to expand...
Click to collapse
No need to unlock bootloader again if you use fastboot method to flash stock firmware , & for spflashtool I'm not sure but I think it remains unlocked

lenrussel said:
There is a error while extracting zip file of the firmware .just checked, I downloaded it from mega.i want to confirm if its the same for baidu also
Click to expand...
Click to collapse
No error while extracting firmware downloaded from baidu

[HOW-TO][EXYNOS/SNAPDRAGON] Root S20 series and upgrade firmware

Applicable Models:
All Exynos models including but not limited to:
SM-G980F or SM-G980F/DS (S20)
SM-G981B or SM-G981B/DS (S20)
SM-G985F or SM-G985F/DS (S20+)
SM-G986B or SM-G986B/DS (S20+)
SM-G988B or SM-G988B/DS (S20 Ultra)
All BL-unlockable Snapdragon models including but not limited to:
SM-G9810 (S20, Hong Kong, Taiwan, China mainland)
SM-G9860 (S20+, Hong Kong, Taiwan, China mainland)
SM-G9880 (S20 Ultra, Hong Kong, Taiwan, China mainland)
SM-G981N (S20, Korea)
SM-G986N (S20+, Korea)
SM-G988N (S20 Ultra, Korea)
Japanese model (SC-*) also use Snapdragon but I can't not confirm that its bootloader is unlockable.
It is known that bootloader can NOT be unlocked on U.S. models (U/U1) .
Frequently used key combinations of S20 series:
FORCE REBOOT: Hold "Volume Down" and "Bixby/Power" button.
DOWNLOAD MODE: With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. Release the buttons after you see the "Warning" screen and then press "Volume Up"
RECOVERY MODE: With the phone off, hold "Volume Up" and "Bixby/Power" button.
Some facts:
1. S20 series uses dynamic partition which means there is only one "super" partition (instead of "system", "vendor", "product").
3. S20 series uses A-only partition which means there is only one set of system partition.
3. S20 series uses 2 stage init (2SI).
4. KNOX will be tripped after you flash a custom image. As a result, Samsung Pay and Secure Folder will become permanently (even after restore to stock firmware) unusable and your warranty may be voided. However, many jurisdictions including the European Union has law mandating manufacturer to provide hardware warranty even if user modifies the software.
5. Samsung devices are almost impossible to hard brick (render the device unusable without a hardware-level repair) as critical sections including the bootloader are well-protected. However, if you do things incorrectly, you may soft brick your phone, but that can usually be resolved by resetting to factory settings (wipe data and cache) or restoring to stock firmware (check out Stage 4).
Tools needed:
On your computer:
1. Odin 3.14.4 or newer
2. Samsung Android USB driver
3. SamFirm or other tools/websites to download official firmwares
4. Android Verified Boot Metadata Image with verification disabled (vbmeta_disabled.tar)
On your device:
1. Magisk Manager
Stage 1: Know your model and carrier code (CSC)
1. Open "Settings"
2. Go to "About phone" -> "Software information"
3. Pay attention to "Service provider SW ver."
4. Starting with "SM-", for example "SM-G9810", that's the model of your phone.
5. Immediately after that, there are two 3-letter code, for example "OZL_CHC". The second 3-letter code "CHC" is your CSC.
6. Remember your model and CSC.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Stage 2: Unlock the bootloader
WARNING: ALL data on your device, including apps, settings and files in internal storage, will be lost. You do not need to repeat this if you didn't re-lock your bootloader.
1. Open "Settings"
2. Turn on "Developer mode" by going to "About phone" -> "Software information" and pressing "Build number" for several times.
3. Go to main menu of "Settings" and at the bottom you will find "Developer options"
4. Go to "Developer options". You will find a toggle "OEM unlocking". Turn it on.
5. Skip to step 8 if your device reboots to "Unlock bootloader?" screen. Make sure the toggle is on and then turn off your phone.
6. With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. (don't use charging only cables)
7. Release the buttons after you see the "Warning" screen. Then, hold the "Volume Up" button.
8. You will see "Unlock bootloader?" screen. Proceed and unlock your bootloader by pressing "Volume Up" button.
9. Your device will be reset to factory settings. Proceed with the Setup Wizard. Only connect to network via Wi-Fi or cellular and skip everything else. (to save time as data will be cleared again later.)
10. Repeat step 1-4 to validate that "OEM Unlocking" is on. If it is not, turn it on.
11. Repeat step 6.
12. Release the buttons after you see the "Warning" screen. This time, press (not hold) the "Volume Up" button.
13. You will see "Downloading" screen. On the top left, there are some important info.
14. Pay attention to "OEM LOCK" and "REACTIVATION LOCK". If both of them are "OFF", you have unlocked the bootloader.
Stage 3: Disable Android Verified Boot
1. Reboot to DOWNLOAD mode. If you are already in the download mode, skip to step 2.
2. Download Odin 3.14.4 or newer and make sure Samsung USB drivers are installed.
3. Open Odin and put the vbmeta_disabled.tar into USERDATA slot and click "Start"
4. Your device will reboot but it will not boot into system as vbmeta signature has changed.
5. Your device will reboot into RECOVERY mode automatically and prompt "You have to reset your device to factory settings". Use "Volume Up" or "Volume Down" button to move and "Power/Bixby" button to select. Confirm and reset the device to factory settings.
6. This is the last time the data on the device has to be cleared. Afterwards, if you don't re-lock bootloader or re-enable the Android Verified Boot, you will not lose your data. Be aware, a stock firmware package contains a Android Verified Boot Metadata Image (vbmeta.img) with verifications enabled. You will need to flash the vbmeta_disable image (put into USERDATA slot) along with the stock firmware (use BL, AP, CP, CSC slots) to make sure AVB is not re-enabled and the data is preserved.
View attachment 4990053
With bootloader unlocked and AVB disabled, it is now possible to boot modified images on the device.
If a recovery is available and you don't want to go through the process of downloading official firmware, go to #2.
You can also download a KERNEL TAR archive of your version here:
Exynos: https://github.com/jesec/proprietary_vendor_samsung_xyzs/releases
Snapdragon: https://github.com/jesec/proprietary_vendor_samsung_xyzq/releases
and then skip to Step 6.
Stage 4: Obtain the official firmware and upgrade
1. Open SamFirm
2. Type in your model and your region (CSC) and click "Check Update"
3. "Download" and you will get a zip file.
View attachment 4990061
4. Extract it and you will get 5 files (AP, BL, CP, CSC and HOME_CSC). All files are in tar format and can be opened by 7-Zip, WinRAR or other software.
5. Check the version code, for example (G9810ZCU1ATD1). The last 4 letters (ATD1) indicates the version of the firmware. If the version is the same as your current firmware, skip to Stage 5.
Your data will be preserved if you do it right but it is good to have a backup.
6. Open Odin on your computer and reboot your device to DOWNLOAD mode.
7. Put AP, BL, CP files in their Odin slots. It takes time to verify the firmware so be patient.
8. Put HOME_CSC file in CSC slot. Be careful here. Unlike AP, BL, CP slots, you should NOT use CSC file for CSC slot. Instead, you should use HOME_CSC file. CSC file contains partition table (PIT) which will erase all your data.
9. Put vbmeta_disabled file in USERDATA slot so AVB remains disabled and your data preserved.
10. Click "Start" and wait for it to finish. Allow the device to boot into system to complete the upgrade process. Do NOT interrupt/disconnect phones/hold button. It needs to complete the process without interruption or strange BUGs may appear.
View attachment 4990063
Stage 5: Extract boot (kernel) image from firmware
If you are having trouble creating tar file, you can skip to Stage 6. (NOT RECOMMENDED as AP is basically full system image. It is huge (takes long time to flash/process) and Magisk may misbehave.)
1. Extract boot.img.lz4 from the AP file.
2. Use 7-Zip to create a tar archive which contains boot.img.lz4 only. (or "tar cvf boot.tar boot.img.lz4")
View attachment 4990065View attachment 4990067View attachment 4990069View attachment 4990071
Stage 6: Patch the boot (Kernel) image via Magisk
1. Transfer the tar archive (or the AP file if you skipped stage 5) to your phone.
2. Open Magisk Manager.
3. Click top-right "Install" button
4. Make sure "Recovery Mode" is off in Options.
5. Click "Next" and select "Select and Patch a File" in Method.
6. Select the file you transferred to your phone in step 1.
7. Click "Next" and "LET'S GO".
8. Transfer the patched file (in Download/magisk_patched.tar) to your computer
9. Reboot the device to DOWNLOAD mode.
10. Open Odin, put patched file to AP slot and then click "Start".
11. After reboot, Magisk is installed and you will have the root access.
HOW TO upgrade the firmware
Repeat stage 4-6.
XDA:DevDB Information
Root S20 series and upgrade firmware, Tool/Utility for the Samsung Galaxy S20
Contributors
jesec
Version Information
Status: Stable
Created 2020-04-08
Last Updated 2020-04-08

Other Methods:
You still need to unlock bootloader and disable AVB. (check Stage 2-3)
Recovery Magisk installation:
1. Open Odin on your computer.
2. Reboot your device to DOWNLOAD mode.
3. Put the recovery TAR flashable into AP slot.
4. Click start.
5. Use Volume Up + Power to reboot into recovery mode.
6. Install Magisk via recovery.
My recovery usually includes Magisk in "Select from root" -> ".builtin" folder. Or you can sideload the ZIP flashable of your choice via adb or https://flash.jesec.io/.
Flash pre-patched boot (Kernel) image:
Basically others have done stage 4-6 for you. Be aware that it is always safer to DIY.
You are welcomed to share your patched image to the community by replying to this thread.
Naming convention: model + firmware version (last four letters of build number) + magisk version .tar
1. Make sure that the model and firmware version of the pre-patched image is the exact SAME as yours.
2. Open Odin on your computer.
3. Reboot your device to DOWNLOAD mode.
4. Put pre-patched image into AP slot.
5. "Start"
SM-G9810_ATD1_ef9d077c.tar:
https://drive.google.com/open?id=1SxKXWHqR0aM_g457Yp7pk524_6aqp1k5

Some Interesting Things:
Change your CSC (carrier code):
You have to root your device. There might be some secret codes to trigger the menu without root, though.
Note that you can only change it to carrier configurations already included in your firmware.
WARNING: Your device will be reset to factory settings.
In a local terminal, type:
su
am start -n com.samsung.android.cidmanager/.preconfig.PreconfigActivity

Cheers jesse seems like years since we were on s9 forums nice friendly guide you made here

What is the purpose of disabling android verify boot?

ngoralph said:
What is the purpose of disabling android verify boot?
Click to expand...
Click to collapse
Android Verified Boot prevents images which are not signed by Samsung to boot on the device. Obviously we don’t have Samsung’s private key and we need to modify images to obtain root access. So it has to be disabled.
ngoralph said:
Am rooted without doing this step will it cause any problems?
Click to expand...
Click to collapse
You must have done it somewhere in the process. Magisk will patch vbmeta.img for you if you give it a tar archive.

jesec said:
Android Verified Boot prevents images which are not signed by Samsung to boot on the device. Obviously we don’t have Samsung’s private key and we need to modify images to obtain root access. So it has to be disabled.
Click to expand...
Click to collapse
Am rooted without doing this step will it cause any problems?

Stage 6: Patch the boot (Kernel) image via Magisk
can't Patch the boot (Kernel) image via Magisk
! Unable to repack boot image!
! Installation failed
---update
use 7-zip to creat tar

bigback said:
Stage 6: Patch the boot (Kernel) image via Magisk
can't Patch the boot (Kernel) image via Magisk
! Unable to repack boot image!
! Installation failed
---update
use 7-zip to creat tar
Click to expand...
Click to collapse
you can extrsct boot and re tar it all in mixplorer then just upload to pc and flash in odin

jesec said:
Android Verified Boot prevents images which are not signed by Samsung to boot on the device. Obviously we don’t have Samsung’s private key and we need to modify images to obtain root access. So it has to be disabled.
Click to expand...
Click to collapse
I'm rooted for weeks now without this... can you explain more in detail what this is for? Why is it advised from you to do this step? maybe in form of examples? like I said rooted without doing this and had no issues so far.

chieco said:
I'm rooted for weeks now without this... can you explain more in detail what this is for? Why is it advised from you to do this step? maybe in form of examples? like I said rooted without doing this and had no issues so far.
Click to expand...
Click to collapse
Backread he already answered it on my inquiry

ngoralph said:
Backread he already answered it on my inquiry
Click to expand...
Click to collapse
I qouted his answer to your question asking for more details.

Magisk Root on Snapdragon based SM-G9860 S20+?
First of all, thanks for putting this guide together - very useful. I did want to share my experience following these instructions.
Everything went well until Stage 6 where I installed the Magisk patched AP file. The AP file was successfully patched with the latest canary Magisk and it also installed properly in Odin (did the full AP file and not the boot image since that encountered errors while trying to repack for some reason).
The problem is that when I reboot, No Magisk installed and No root...
I tried a factory reset just to confirm but same outcome. I did use the same AP file that was used to flash the phone as well.
Anyone successfully root and install Magisk on the Snapdragon based SM-G9860 S20+ (with latest Hong Kong firmware)? I suspect it has something to do with the Magisk not being able to handle the unlocked snapdragon based phones yet (it was like that for the Galaxy 10+ last year - took an extra month to come up with a Magisk branch that was able to handle the phone). I'm also following this thread for Snapdragons based S20 but it doesn't seem to have too many details yet
Cheers
A.A.

chieco said:
I qouted his answer to your question asking for more details.
Click to expand...
Click to collapse
jesec said:
You must have done it somewhere in the process. Magisk will patch vbmeta.img for you if you give it a tar archive.
Click to expand...
Click to collapse
AloxeCorton said:
First of all, thanks for putting this guide together - very useful. I did want to share my experience following these instructions.
Everything went well until Stage 6 where I installed the Magisk patched AP file. The AP file was successfully patched with the latest canary Magisk and it also installed properly in Odin (did the full AP file and not the boot image since that encountered errors while trying to repack for some reason).
The problem is that when I reboot, No Magisk installed and No root...
I tried a factory reset just to confirm but same outcome. I did use the same AP file that was used to flash the phone as well.
Anyone successfully root and install Magisk on the Snapdragon based SM-G9860 S20+ (with latest Hong Kong firmware)? I suspect it has something to do with the Magisk not being able to handle the unlocked snapdragon based phones yet (it was like that for the Galaxy 10+ last year - took an extra month to come up with a Magisk branch that was able to handle the phone). I'm also following this thread for Snapdragons based S20 but it doesn't seem to have too many details yet
Cheers
A.A.
Click to expand...
Click to collapse
My Snapdragon S20 has been rooted with Magisk. I think probably it has problem patching the full AP file. In that case, I recommend you to research how to pack a tar file. I don't recommend you to patch the full AP as it is huge.
Also be aware that all patched file is located in /sdcard/Download and named magisk_patched.*. It is NOT in-place patch. You might accidentally use the unpatched file.

So I tried to apply this tutorial to update my phone SM-G981F
And it can't boot. it finish in failsave recovery :
"Can't load ndroid system. your data may be corrupted..... please perform a factory reset...."
I really would like to avoid it... I flashed vbmeta_disabled.tar but no GO...
I was already rooted with Magisk patch on ATCH rom...
Edit : wiped...

Orphee said:
So I tried to apply this tutorial to update my phone SM-G981F
And it can't boot. it finish in failsave recovery :
"Can't load ndroid system. your data may be corrupted..... please perform a factory reset...."
I really would like to avoid it... I flashed vbmeta_disabled.tar but no GO...
I was already rooted with Magisk patch on ATCH rom...
Edit : wiped...
Click to expand...
Click to collapse
As it finishes flashing firmware hold volume buttons as it reboots. Then flash patched boot.img and reboot. Worked for me going from ATCH to ATCT today.

jesec said:
My Snapdragon S20 has been rooted with Magisk. I think probably it has problem patching the full AP file. In that case, I recommend you to research how to pack a tar file. I don't recommend you to patch the full AP as it is huge.
Also be aware that all patched file is located in /sdcard/Download and named magisk_patched.*. It is NOT in-place patch. You might accidentally use the unpatched file.
Click to expand...
Click to collapse
Thanks for the help. I did try patching the TARed (using 7zip) boot.img.lz4 file but for some reason it just refuses to "repack" from within Magisk (see screen capture attached)- I'm not sure if anyone experienced this or if I'm overlooking something.
Also tried to reformat everything with the Chinese firmware instead of HK (it was a little more recent) but I got the same results. Oddly the full AP file seems to patch fine in Magisk but never produces the expected results (no Magisk installed, no root).
A.A.

AloxeCorton said:
Thanks for the help. I did try patching the TARed (using 7zip) boot.img.lz4 file but for some reason it just refuses to "repack" from within Magisk (see screen capture attached)- I'm not sure if anyone experienced this or if I'm overlooking something.
Also tried to reformat everything with the Chinese firmware instead of HK (it was a little more recent) but I got the same results. Oddly the full AP file seems to patch fine in Magisk but never produces the expected results (no Magisk installed, no root).
A.A.
Click to expand...
Click to collapse
I had the same issue... I used a tool (lz4_win64_v1_9_2) to uncompress lz4 format... I kept it just as boot.img and packed in boot.tar file and it worked.
Just for info, 7-zip built wrong tar file (don't ask me why...)... I had to use cygwin for it (or a linux if you have)

Orphee said:
So I tried to apply this tutorial to update my phone SM-G981F
And it can't boot. it finish in failsave recovery :
"Can't load ndroid system. your data may be corrupted..... please perform a factory reset...."
I really would like to avoid it... I flashed vbmeta_disabled.tar but no GO...
I was already rooted with Magisk patch on ATCH rom...
Edit : wiped...
Click to expand...
Click to collapse
That's expected.
From Android 10, encryption keys are tied to AVB key (stored in vbmeta). By disabling AVB, you changed the AVB key from Samsung's to none. Though, if I remember correctly, some old versions have security loophole that allows you to boot a patched kernel even if AVB key is intact (recovery is still protected however). That's actually a serious breach of this additional integrity assurance. (your sensitive data is still safe nonetheless as there is a customer key tied to your password/pattern/etc)
Read more: https://source.android.com/security/keystore/version-binding
AloxeCorton said:
Thanks for the help. I did try patching the TARed (using 7zip) boot.img.lz4 file but for some reason it just refuses to "repack" from within Magisk (see screen capture attached)- I'm not sure if anyone experienced this or if I'm overlooking something.
Also tried to reformat everything with the Chinese firmware instead of HK (it was a little more recent) but I got the same results. Oddly the full AP file seems to patch fine in Magisk but never produces the expected results (no Magisk installed, no root).
A.A.
Click to expand...
Click to collapse
That should not happen. Here is a screenshot if things are done right:
Make sure you pack the TAR right (see OP for a screenshot of boot.img.lz4.tar) and the file you transfer to your device is the TAR file (boot.img.lz4.tar if you don't change the file name).
Plus, maybe check if Magisk version is right. Make sure you use the Canary builds.

AloxeCorton said:
Thanks for the help. I did try patching the TARed (using 7zip) boot.img.lz4 file but for some reason it just refuses to "repack" from within Magisk (see screen capture attached)- I'm not sure if anyone experienced this or if I'm overlooking something.
Also tried to reformat everything with the Chinese firmware instead of HK (it was a little more recent) but I got the same results. Oddly the full AP file seems to patch fine in Magisk but never produces the expected results (no Magisk installed, no root).
A.A.
Click to expand...
Click to collapse
do it on fone thats what i did mixplorer will tar it for you then move to pc and flash

RIP S7 EDGE G935FD Can any one help me?

ON U7 Binary with FRP LOCK ON (thats my mistake i turnoff oem unlock after updating to new bootloader on twrp and restarted it)
DM VERIFICATION FAILED
NEED U7 BINARY (COMBINATION FIRMWARE)
or CAN ANYONE TELL ME HOW TO TURN OFF FRP LOCK so that i can flash twrp
or any other method to erase full device so that only mode will be left to flash firmware

The safest way is to boot into download mode and flash in stock rom in odin. Make sure you have the correct stock rom.
Set up the phone as usual, after login to your Google account, you can skip the rest of the phone setup.
Then go settings - accounts - Google and remove your Google account.
Then you can continue to do what you wanted to do. Google frp is switched off.
Sent from my SM-G985F using Tapatalk

vash_h said:
The safest way is to boot into download mode and flash in stock rom in odin. Make sure you have the correct stock rom.
Set up the phone as usual, after login to your Google account, you can skip the rest of the phone setup.
Then go settings - accounts - Google and remove your Google account.
Then you can continue to do what you wanted to do. Google frp is switched off.
Sent from my SM-G985F using Tapatalk
Click to expand...
Click to collapse
I tried flashing the right firmware but it always says frp lock on
and dm verification failed error 255 blob verification failed
i remember my google id and password but the main issue is phone is not booting up normally it always shows NO COMMAND and then restart itself
also not able to open recovery
IF ANYONE KNOWS HOW TO FLASH ONLY SYSTEM.IMG from previous firmware i can return to U6 and will flash U6 Factory Binary to turnoff oem unlock

Tapas27s said:
I tried flashing the right firmware but it always says frp lock on
and dm verification failed error 255 blob verification failed
i remember my google id and password but the main issue is phone is not booting up normally it always shows NO COMMAND and then restart itself
also not able to open recovery
IF ANYONE KNOWS HOW TO FLASH ONLY SYSTEM.IMG from previous firmware i can return to U6 and will flash U6 Factory Binary to turnoff oem unlock
Click to expand...
Click to collapse
Bro.. Using odin. That's using pc. You screwed up big time and I don't know why you wanted to change the bootloader.
Sent from my SM-G985F using Tapatalk

I flashed firmware using odin..
I want to change bootloader because U7 binary is not on internet U6 is.. thats why

vash_h said:
Bro.. Using odin. That's using pc. You screwed up big time and I don't know why you wanted to change the bootloader.
Sent from my SM-G985F using Tapatalk
Click to expand...
Click to collapse
After updating to latest bootloader i turn off oem unlocking and that cost me this.. dead phone

I purchased a phone off a guy on facebook for like $60 knowing that it was locked, but not realizing what FRP was exactly and how hard it would be to bypass. I thought I was locked out of my phone as well. Tried everything...odin, Samsung Pro Tool, various random little programs floating around, and all the youtube videos showing FRP bypass glitches. Spent maybe 20 hours trying to figure it out..but FRP always came back. Then, by total accident, I got it to work. Try this: on first boot after flashing the firmware you'll come to a point that says "Installing Applications" or something along those lines. It should occur after the samsung logo but before you get to the "Welcome!" screen. When you see that, turn your phones screen off, wait a second, and then turn it back on. If you are lucky, it will bring you to the normal lock screen and if it does, you'll be able to pull the drop down settings menu from which you can click on the button to bring up the full settings, from which you need to then login to wifi then go back and add a google account. From what I gather, there seems to be a point during the setup process that exists after boot and before FRP actually activates where Android is up and running in terms of it's basic functions before the setup process gets far enough to be able to check the FRP status/engage it. So again:
1. Flash Firmware
2. Boot phone
3. When screen says "Installing Applications" (black screen with a white progress bar) turn your screen off via power putton.
4. Turn screen back on.
5. If you are greeted by the standard android lock screen, try to access the drop down setting toggle switches.
6. If 5 works, click the settings icon to enter into the full settings menu.
7. Go to connections-Wifi and login into your wifi network
8. Back button to main settings menu, then to accounts, add Google account.
9. If you are able to add your google account, that should be it. You'd be able to enter into android and FRP would be disabled. Might need to restart phone.
The above worked for me on a Binary A 8.0 setup. Again, zero luck trying anything..pro software, combination firmwares, etc...that is the only thing that worked. Good luck.

freakwithracket said:
i purchased a phone off a guy on facebook for like $60 knowing that it was locked, but not realizing what frp was exactly and how hard it would be to bypass. I thought i was locked out of my phone as well. Tried everything...odin, samsung pro tool, various random little programs floating around, and all the youtube videos showing frp bypass glitches. Spent maybe 20 hours trying to figure it out..but frp always came back. Then, by total accident, i got it to work. Try this: On first boot after flashing the firmware you'll come to a point that says "installing applications" or something along those lines. It should occur after the samsung logo but before you get to the "welcome!" screen. When you see that, turn your phones screen off, wait a second, and then turn it back on. If you are lucky, it will bring you to the normal lock screen and if it does, you'll be able to pull the drop down settings menu from which you can click on the button to bring up the full settings, from which you need to then login to wifi then go back and add a google account. From what i gather, there seems to be a point during the setup process that exists after boot and before frp actually activates where android is up and running in terms of it's basic functions before the setup process gets far enough to be able to check the frp status/engage it. So again:
1. Flash firmware
2. Boot phone
3. When screen says "installing applications" (black screen with a white progress bar) turn your screen off via power putton.
4. Turn screen back on.
5. If you are greeted by the standard android lock screen, try to access the drop down setting toggle switches.
6. If 5 works, click the settings icon to enter into the full settings menu.
7. Go to connections-wifi and login into your wifi network
8. Back button to main settings menu, then to accounts, add google account.
9. If you are able to add your google account, that should be it. You'd be able to enter into android and frp would be disabled. Might need to restart phone.
The above worked for me on a binary a 8.0 setup. Again, zero luck trying anything..pro software, combination firmwares, etc...that is the only thing that worked. Good luck.
Click to expand...
Click to collapse
phone is not booting up .. In your case phone boots up
in my case phonde dont boot up after flashing firmware it says no command and then shows dm verity error
if my frp was off i would flash twrp and set up my phone..
My case frp on
dm verity error error 255 cannot flash target
i had to fix one of these.... Frp or dm verity..
When my phone was on i made a mistake by turning off oem unlocking then restarting it
that cause me this dead phone..

Tapas27s said:
phone is not booting up .. In your case phone boots up
in my case phonde dont boot up after flashing firmware it says no command and then shows dm verity error
if my frp was off i would flash twrp and set up my phone..
My case frp on
dm verity error error 255 cannot flash target
i had to fix one of these.... Frp or dm verity..
When my phone was on i made a mistake by turning off oem unlocking then restarting it
that cause me this dead phone..
Click to expand...
Click to collapse
Did you try booting the phone in safe mode?

freakwithracket said:
Did you try booting the phone in safe mode?
Click to expand...
Click to collapse
How to boot phone into safe mode when your phone doesn't boot at all
My phone boots up and stuck on NO COMMAND BLUE SCREEN AND THEN SHOW THis

Tapas27s said:
How to boot phone into safe mode when your phone doesn't boot at all
My phone boots up and stuck on NO COMMAND BLUE SCREEN AND THEN SHOW THis
Click to expand...
Click to collapse
I don't know why even at this point of time when there are forums like xda and every basic thing pinned on internet why do people try to intentionally do new/f*** things
In other words, try to fix something which isn't broken..
No, you don't "accidentally" turn oem unlock off.. you need to scroll the screen halfway and then 'tap' right buttons on right screen to enter developer options and then scroll to oem unlock option and tap on it "intentionally" to see what happens
Not trying to be rude or to pick on you.. but it is hillarious how much people in s7 edge forums are 'accidentally' turing oem unlock off.. my inbox is full of such messages ..
I think xda has some issue displaying words correctly.. otherwise this simple basic sentence is posted everywhere on the xda forums :
"YOU NEED TO ENABLE OEM UNLOCK BEFORE DOING ANY UMOFFICIAL MODIFICATION TO YOUR PHONE"
Do you know oem unlock means to unlock bootloader to flash anything other then official OEM ? Failing which will cause phone to reject unofficial modifications and become a brick..
Also let me tell you this luxury of unlocking bootloader is so easily available on samsung phones ..
Do you know how difficult it is now to unlock bootloader of huawei devices ? They stopped providing unlock codes and its a premium charged service now to unlock huawei bootloaders..
And still.. when samsung has made it so easy .. one tap bootloader unlocking and still people mess it to see "what happens".. is ironic really
Ok , the point of all this was not to flame on you or anyone.. but to LET OTHERS KNOW THAT THIS IS NOT A GREAT IDEA TO TURN OEM UNLOCK OFF AFTER YOU MODIFIED YOUR PHONE IN ANY WAY..
Now, to get on your problem.. this cannot be solved by any combination rom ..
The reason your phone cannot boot is because your device's drk (device root key) is corrupted/modified/missing.. which causes dm (device mapping) verity error, it occurs in two types :
1. 1st type is when you enable system modifications in twrp plus dm verity is enabled in the kernel and you "accidentally" turn oem unlock off..
dm verity kicks in this scenario and prevents phone from booting..
BUT your EFS/NV data partition containing DRK is NOT corrupted/modified/missing in this type of error.
This happens when you root your phone with NON-SYSTEMLESS method and oem unlock being turned off..
In this case, just a stock samsung firmware reflash would solve this. Like it happened with @ freakwithracket , he only had frp problem due to oem unlock turned off, and he was able to solve it.
Now the 2nd type which you and many others suffered here too.. this one is akin to a hard brick and trust me when i say hard brick it means it is very very difficult (if not impossible) for average users (including me too) which are noobs to mess in android/linux guts..
I say it is nearly impossible for average users to fix it when even master ChainFire have had difficulty in such..
Refer to his vital post here : https://forum.xda-developers.com/showpost.php?p=72204306&postcount=978
And i am just a noob, i just did some research to get knowledge.. thats what everyone should do before posting..
2. This type 2 dm verity mostly kicks in for unfortunate users when:
They enabled system modifications in twrp, and rooted phone using NON-SYSTEMLESS method.
They decided to jump in the death valley (literally lol) by turning OEM UNLOCK OFF.. why though ? :emo_y.tho:
3rd and main reason : FOR SOME REASON THEIR DEVICE'S NV DATA/EFS PARTITION (WHICH CONTAIN DRK) IS CORRUPTED/ENCRYPTED/MODIFIED IN SUCH WAY THAT WHILE ROOTED AND OEM UNLOCK ENABLED IT CAUSES NO PROBLEM IN BOOTING CUSTOM ROMS (BECAUSE OEM UNLOCK IS ON AND CUSTOM ROMS HAVE DM VERITY DISABLED IN KERNELS) BUT YOU CAN ONLY BOOT CUSTOM ROMS WHICH HAVE DM VERITY CHECK DISABLED.. YOU CANNOT BOOT STOCK UNMODIFIED ROM.. (FOR BOOTING STOCK ROM YOU NEED TO INSTALL TWRP AND FLASH NO VERITY ZIPS IN IT)
BUT WHEN OEM UNLOCK IS TURNED OFF, IT CAUSES DM VERITY ERROR PROBABLY DUE TO CORRUPTED/ENCRYPTED/MODIFIED EFS/NV DATA (CONTAINING DRK) WHEN BOOTING STOCK UNMODIFIED ROM AND YOU CANNOT BOOT WITH ANY MODIFIED BINARIES LIKE TWRP OR CUSTOM ROMS OR NO VERITY ZIPS DUE TO OEM UNLOCK BEING OFF WHICH CAUSES CUSTOM BINARY BLOCKED BY FRP AND STOCK BINARY BLOCKED DUE TO DRK PROBLEM (SO YOU GET KIND OF HARD BRICK)
BUT WHICH CANNOT BE SOLVED BY REFLASHING STOCK.. OR ANY COMBINATION ROM..
Now how it can be solved ..
1. Surely can be solved by opening android's/linux guts along with opening your phone's guts and maybe using some hardware tools/boxes too (which frankly only developers can do)..
2. Surely a hardware box can solve this.. (for repairers)
3. Not 100% sure (may work) , editing your stock firmware to "REMOVE" recovery partition and flashing it .. SO THERE IS NO RECOVERY PRESENT BUT PHONE CAN BOOT AND YOU CAN GO IN SETTINGS TO ENABLE OEM UNLOCK..
AND YES, RECOVERY CHECKS DM VERITY AND BLOCKS BOOTING.. (BUT AS MASTER CHAINFIRE SAID THIS MAY NOT WORK BUT PLEASE TRY ! )
I will refer you two posts.. 1st post for following 2nd (box) method above, 2nd post for the 3rd method above..
1. Using box (this may work) https://forum.xda-developers.com/s7-edge/how-to/fix-imei-downgrading-g935f-fd-t3947911
This guy here was able to fix something like this too using a box : https://forum.xda-developers.com/s7-edge/help/s7-edge-t4073957/post82232707
2. Using no-recovery method
https://forum.xda-developers.com/s7...-g935f-custom-binary-dm-t4073925/post82134961 - just apply the method on official downloaded stock firmware you had in your phone before it got this problem OR another firmware with a MATCHING bootloader number..
Good luck !
Edit : Was your imei okay and network working?
Pro/experimental tip .. always backup your efs partition (first thing you do after installing twrp), if you have efs backup before all this (which you expect to NOT be corrupted).
Only do this *IF YOU GOT A BACKUP OF EFS (FIRST TIME AFTER INSTALLING TWRP)*..
1. Extract that backup and copy prov_data folder (not a flashable zip) to phone internal memory..
2. Open root explorer , navigate to efs partition (delete all files there EXCEPT FACTORY APP.. DELETE THE PROV_DATA FOLDER THERE TOO) or go in twrp recovery and do this.
3. The moment you delete these files you will not reboot again in phone..
use these commands in adb shell while in twrp
1. su
2. cd /efs
3. mv /data/media/0/prov_data /efs/
4. chmod -R 755 /efs/prov_data
5. chown -R root:root /efs/prov_data
(Note: S7 Edge on android 8's path may differ, just replace with correct one)
Don't reboot phone..
After this, device's original drk is restored, but need to be activated, go in download mode from twrp.. flash correct combination rom, go into combination recovery from download mode (without booting into combination rom) do factory data wipe and clear cache and reboot now into combination rom.. your original drk should be okay now.
Warning
*DON'T DO THIS IF YOU DON'T HAVE UNTOUCHED/UN-CORRUPTED (NOT CORRUPTED) EFS BACKUP !*
*YOU NEED TO MAKE YOUR PHONE BOOTING AGAIN TO DO THIS ! AND BEFORE DOING ALL THIS YOU NEED TO REFLASH YOUR CORRECT STOCK FIRMWARE IN ODIN THEN GO IN RECOVERY AND FACTORY DATA WIPE AND CLEAR CACHE, THEN ROOT YOUR PHONE TO GET SU PERMISSIONS THEN BOOT INTO PHONE TO DO ABOVE*
*DON'T DO THIS IF YOU ARE NOT SURE ABOUT ADB COMMANDS*
Successfully doing this can restore drk so if you "accidentally" turn off oem unlock again you won't have a hard brick again.. (Nah, just kidding lol..)
IF YOU DON'T HAVE ORIGINAL EFS BACKUP.. NEVER DO THIS EXPERIMENTAL PROCESS..
Original post reference : https://forum.xda-developers.com/showpost.php?p=67840769&postcount=1
All credits to their respective contributors.
Edit 2 : how to check if your drk is corrupted/modified/missing??
(Always try this after backing up all stuff and making SURE THAT OEM UNLOCK IS ON!!)
Simply flash stock unmodified rom (BUT ALWAYS KEEP OEM UNLOCK ON AT ANY COST), then go in recovery from download mode directly without booting phone, do a factory data wipe and clear cache then reboot phone.. if you can boot into stock unmodified rom without any verification errors.. then your drk is intact (immediately make a backup of your phone's efs partition using any method/tool but systemless root is preferred)
If it gives verification errors, then your drk has problem as described above .. you cannot boot unmodified stock rom and oem unlock being enabled is essential for your phone to be alive.. Flash twrp and then no verity zip to eliminate the dm verity error in stock unmodified rom..
OR flash any custom rom to your liking (most have dm verity disabled in them)
Sorry for the huge word wall, but i thought it is essential information to share
Sent from my S7 Edge using XDA Labs

shah22 said:
I don't know why even at this point of time when there are forums like xda and every basic thing pinned on internet why do people try to intentionally do new/f*** things
In other words, try to fix something which isn't broken..
No, you don't "accidentally" turn oem unlock off.. you need to scroll the screen halfway and then 'tap' right buttons on right screen to enter developer options and then scroll to oem unlock option and tap on it "intentionally" to see what happens
Not trying to be rude or to pick on you.. but it is hillarious how much people in s7 edge forums are 'accidentally' turing oem unlock off.. my inbox is full of such messages ..
I think xda has some issue displaying words correctly.. otherwise this simple basic sentence is posted everywhere on the xda forums :
"YOU NEED TO ENABLE OEM UNLOCK BEFORE DOING ANY UMOFFICIAL MODIFICATION TO YOUR PHONE"
Do you know oem unlock means to unlock bootloader to flash anything other then official OEM ? Failing which will cause phone to reject unofficial modifications and become a brick..
Also let me tell you this luxury of unlocking bootloader is so easily available on samsung phones ..
Do you know how difficult it is now to unlock bootloader of huawei devices ? They stopped providing unlock codes and its a premium charged service now to unlock huawei bootloaders..
And still.. when samsung has made it so easy .. one tap bootloader unlocking and still people mess it to see "what happens".. is ironic really
Ok , the point of all this was not to flame on you or anyone.. but to LET OTHERS KNOW THAT THIS IS NOT A GREAT IDEA TO TURN OEM UNLOCK OFF AFTER YOU MODIFIED YOUR PHONE IN ANY WAY..
Now, to get on your problem.. this cannot be solved by any combination rom ..
The reason your phone cannot boot is because your device's drk (device root key) is corrupted/modified/missing.. which causes dm (device mapping) verity error, it occurs in two types :
1. 1st type is when you enable system modifications in twrp plus dm verity is enabled in the kernel and you "accidentally" turn oem unlock off..
dm verity kicks in this scenario and prevents phone from booting..
BUT your EFS/NV data partition containing DRK is NOT corrupted/modified/missing in this type of error.
This happens when you root your phone with NON-SYSTEMLESS method and oem unlock being turned off..
In this case, just a stock samsung firmware reflash would solve this. Like it happened with @ freakwithracket , he only had frp problem due to oem unlock turned off, and he was able to solve it.
Now the 2nd type which you and many others suffered here too.. this one is akin to a hard brick and trust me when i say hard brick it means it is very very difficult (if not impossible) for average users (including me too) which are noobs to mess in android/linux guts..
I say it is nearly impossible for average users to fix it when even master ChainFire have had difficulty in such..
Refer to his vital post here : https://forum.xda-developers.com/showpost.php?p=72204306&postcount=978
And i am just a noob, i just did some research to get knowledge.. thats what everyone should do before posting..
2. This type 2 dm verity mostly kicks in for unfortunate users when:
They enabled system modifications in twrp, and rooted phone using NON SYSTEM LESS method.
They decided to jump in the death valley (literally lol) by turning OEM UNLOCK OFF.. why though ? :emo_y.tho:
3rd and main reason : FOR SOME REASON THEIR DEVICE'S NV DATA/EFS PARTITION (WHICH CONTAIN DRK) IS CORRUPTED/ENCRYPTED/MODIFIED IN SUCH WAY THAT WHILE ROOTED AND OEM UNLOCK ENABLED IT CAUSES NO PROBLEM IN BOOTING CUSTOM ROMS (BECAUSE OEM UNLOCK IS ON AND CUSTOM ROMS HAVE DM VERITY DISABLED IN KERNELS) BUT YOU CAN ONLY BOOT CUSTOM ROMS WHICH HAVE DM VERITY CHECK DISABLED.. YOU CANNOT BOOT STOCK UNMODIFIED ROM.. (FOR BOOTING STOCK ROM YOU NEED TO INSTALL TWRP AND FLASH NO VERITY ZIPS IN IT)
BUT WHEN OEM UNLOCK IS TURNED OFF, IT CAUSES DM VERITY ERROR PROBABLY DUE TO CORRUPTED/ENCRYPTED/MODIFIED EFS/NV DATA (CONTAINING DRK) WHEN BOOTING STOCK UNMODIFIED ROM AND YOU CANNOT BOOT WITH ANY MODIFIED BINARIES LIKE TWRP OR CUSTOM ROMS OR NO VERITY ZIPS DUE TO OEM UNLOCK BEING OFF WHICH CAUSES CUSTOM BINARY BLOCKED BY FRP AND STOCK BINARY BLOCED DUE TO DRK PROBLEM (SO YOU GET KIND OF HARD BRICK)
BUT WHICH CANNOT BE SOLVED BY REFLASHING STOCK.. OR ANY COMBINATION ROM..
Now how it can be solved ..
1. Surely can be solved by opening android's/linux guts along with opening your phone's guts and maybe using some hardware tools/boxes too (which frankly only developers can do)..
2. Surely a hardware box can solve this.. (for repairers)
3. Not 100% sure (may work) , editing your stock firmware to "REMOVE" recovery partition and flashing it .. SO THERE IS NO RECOVERY PRESENT BUT PHONE CAN BOOT AND YOU CAN GO IN SETTINGS TO ENABLE OEM UNLOCK..
AND YES, RECOVERY CHECKS DM VERITY AND BLOCKS BOOTING.. (BUT AS MASTER CHAINFIRE SAID THIS MAY NOT WORK BUT PLEASE TRY ! )
I will refer you two posts.. 1st post for following 2nd (box) method above, 2nd post for the 3rd method above..
1. Using box (this may work) https://forum.xda-developers.com/s7-edge/how-to/fix-imei-downgrading-g935f-fd-t3947911
This guy here was able to fix something like this too using a box : https://forum.xda-developers.com/s7-edge/help/s7-edge-t4073957/post82232707
2. Using no-recovery method
https://forum.xda-developers.com/s7...-g935f-custom-binary-dm-t4073925/post82134961 - just apply the method on official downloaded stock firmware you had in your phone before it got this problem OR another firmware with a MATCHING bootloader number..
Good luck !
Edit : Was your imei okay and network working?
Pro/experimental tip .. always backup your efs partition (first thing you do after installing twrp), if you have efs backup before all this (which you expect to NOT be corrupted).
Only do this *IF YOU GOT A BACKUP OF EFS (FIRST TIME AFTER INSTALLING TWRP)*..
1. Extract that backup and copy prov_data folder (not a flashable zip) to phone internal memory..
2. Open root explorer , navigate to efs partition (delete all files there EXCEPT FACTORY APP.. DELETE THE PROV_DATA FOLDER THERE TOO) or go in twrp recovery and do this.
3. The moment you delete these files you will not reboot again in phone..
use these commands in adb shell while in twrp
1. su
2. cd /efs
3. mv /data/media/0/prov_data /efs/
4. chmod -R 755 /efs/prov_data
5. chown -R root:root /efs/prov_data
(Note: S7 Edge on android 8's path may differ, just replace with correct one)
Don't reboot phone..
After this, device's original drk is restored, but need to be activated, go in download mode from twrp.. flash correct combination rom, go into combination recovery from download mode (without booting into combination rom) do factory data wipe and clear cache and reboot now into combination rom.. your original drk should be okay now.
Warning
*DON'T DO THIS IF YOU DON'T HAVE UNTOUCHED/UN-CORRUPTED (NOT CORRUPTED) EFS BACKUP !*
*YOU NEED TO MAKE YOUR PHONE BOOTING AGAIN TO DO THIS ! AND BEFORE DOING ALL THIS YOU NEED TO REFLASH YOUR CORRECT STOCK FIRMWARE IN ODIN THEN GO IN RECOVERY AND FACTORY DATA WIPE AND CLEAR CACHE, THEN ROOT YOUR PHONE TO GET SU PERMISSIONS THEN BOOT INTO PHONE TO DO ABOVE*
*DON'T DO THIS IF YOU ARE NOT SURE ABOUT ADB COMMANDS*
Successfully doing this can restore drk so if you "accidentally" turn off oem unlock again you won't have a hard brick again.. (Nah, just kidding lol..)
IF YOU DON'T HAVE ORIGINAL EFS BACKUP.. NEVER DO THIS EXPERIMENTAL PROCESS..
Original post reference : https://forum.xda-developers.com/showpost.php?p=67840769&postcount=1
All credits to their respective contributors.
Edit 2 : how to check if your drk is corrupted/modified/missing??
(Always try this after backing up all stuff and making SURE THAT OEM UNLOCK IS ON!!)
Simply flash stock unmodified rom (BUT ALWAYS KEEP OEM UNLOCK ON AT ANY COST), then go in recovery from download mode directly without booting phone, do a factory data wipe and clear cache then reboot phone.. if you can boot into stock unmodified rom without any verification errors.. then your drk is intact (immediately make a backup of your phone's efs partition using any method/tool but systemless root is preferred)
If it gives verification errors, then your drk has problem as described above .. you cannot boot unmodified stock rom and oem unlock being enabled is essential for your phone to be alive.. Flash twrp and then no verity zip to eliminate the dm verity error in stock unmodified rom..
OR flash any custom rom to your liking (most have dm verity disabled in them)
Sorry for the huge word wall, but i thought it is essential information to share
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
1 ST METHOD TRIED with modified AP ( name boot.img as recovery.img and system.img )
Result in direct booting and samsung logo then it gets off suddenly and shows No command with blue screen view 1st pic
2nd method tried modified ap with bl cp csc result in stuck with samsunt logo for about 15 mintues watch 2 nd pic
3rd Tried modified ap with bl cp csc and with pit file..
Also result in stuck with samsung logo
4TH I TRY FLASHING 2nd modified ap ( rename boot.img as recovery,original boot.img and system.img)
Then i put my phone into boot process
Showed samsung logo and then it shows button lights..i was waiting for the screen to say insatlling applications like the galaxy app and smart switch but instead of that.. it showed nothing and reboots into blue screen with no command and shows this image

Tapas27s said:
1 ST METHOD TRIED with modified AP ( name boot.img as recovery.img and system.img )
Result in direct booting and samsung logo then it gets off suddenly and shows No command with blue screen view 1st pic
2nd method tried modified ap with bl cp csc result in stuck with samsunt logo for about 15 mintues watch 2 nd pic
3rd Tried modified ap with bl cp csc and with pit file..
Also result in stuck with samsung logo
Click to expand...
Click to collapse
You wont stuck on samsung logo for long.. eventually it will boot in and you could enable oem unlock..
WAIT ATLEAST FOR 30 MINUTES ON SAMSUNG LOGO, MAYBE IT WILL LET YOU IN..
If it didn't worked your phone wouldn't have booted.
Try as said in post..
system.img + [renamed] recovery.img (which is boot.img) see if it works
If not then try : system.img + [renamed] recovery.img + boot.img (which means system.img + boot.img + boot.img) see if this works
If not then try : system.img + [renamed] recovery.img + boot.img + userdata.img .. see if it works ?
If not try : system.img + [renamed] recovery.img + userdata.img .. see if this works.
Try flashing only AP in odin , if don't works .. use BL+CP+CSC too
First try with normal csc , then try with Home_Csc too
Don't use pit file..no use..
Try with combinations i said above.
If couldn't fix, pm me, we try to fix on tv. Good luck
Edit : I SEE DM VERITY IS NOT KICKING IN.. YOU JUST NEED TO GET IN PHONE TO ENABLE OEM UNLOCK..
You just need to try different combinations to get inside..
Maybe use userdata.img too ??
I think you need to try with : system.img + [renamed] recovery.img + boot.img + userdata.img ..
Sent from my S7 Edge using XDA Labs

Thanks thanks thanks thanks!!!!
shah22 said:
You wont stuck on samsung logo for long.. eventually it will boot in and you could enable oem unlock..
WAIT ATLEAST FOR 30 MINUTES ON SAMSUNG LOGO, MAYBE IT WILL LET YOU IN..
If it didn't worked your phone wouldn't have booted.
Try as said in post..
system.img + [renamed] recovery.img (which is boot.img) see if it works
If not then try : system.img + [renamed] recovery.img + boot.img (which means system.img + boot.img + boot.img) see if this works
If not then try : system.img + [renamed] recovery.img + boot.img + userdata.img .. see if it works ?
If not try : system.img + [renamed] recovery.img + userdata.img .. see if this works.
Try flashing only AP in odin , if don't works .. use BL+CP+CSC too
First try with normal csc , then try with Home_Csc too
Don't use pit file..no use..
Try with combinations i said above.
If couldn't fix, pm me, we try to fix on tv. Good luck
Edit : I SEE DM VERITY IS NOT KICKING IN.. YOU JUST NEED TO GET IN PHONE TO ENABLE OEM UNLOCK..
You just need to try different combinations to get inside..
Maybe use userdata.img too ??
I think you need to try with : system.img + [renamed] recovery.img + boot.img + userdata.img ..
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
THANKS THANKS THANKS!!!!
it successfully booted
i signed in and turn on the oem unlock option with usb debugging now i am just reflashing the firmware and then twrp then dmverity opt zip then magisk then i will charge and use my phone
thanks alot!!! @shah22

Tapas27s said:
THANKS THANKS THANKS!!!!
it successfully booted
i signed in and turn on the oem unlock option with usb debugging now i am just reflashing the firmware and then twrp then dmverity opt zip then magisk then i will charge and use my phone
thanks alot!!! @shah22
Click to expand...
Click to collapse
Glad it worked..
JUST DON'T TURN OFF OEM UNLOCK AGAIN "ACCIDENTALLY"
So you used system.img + [renamed] recovery.img + boot.img + userdata.img ??
Post your exact steps here so others may benefit
Sent from my S7 Edge using XDA Labs

shah22 said:
Glad it worked..
JUST DON'T TURN OFF OEM UNLOCK AGAIN "ACCIDENTALLY"
So you used system.img + [renamed] recovery.img + boot.img + userdata.img ??
Post your exact steps here so others may benefit
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
STEPS
1 EXTRACT FILES FROM AP TAKE 2 FILES BOOT.IMG AND SYSTEM.IMG
MAKE A COPY OF BOOT.IMG TO ANOTHER FOLDER AND RENAME IT AS RECOVERY.IMG
2 YOU HAVE NOW 3 FILES BOOT.IMG, RENAMED RECOVERY.IMG AND SYSTEM.IMG
3 DOWNLOAD AUTO TAR 2.0 AND MAKE TAR MD5 FILE
4 SO YOU HAVE MODIFIED AP FLASH IT ALONG WITH CP BL AND HOME CSC AND WAIT TO BOOT THE PHONE ( CHARGE YOUR PHONE ATLEAST 10%)
THEN THERE YOU GO WELCOME SCREEN SIGN IN AND AFTER TURN OFF THE OEM UNLOCK OPTION BY GOING INTO DEVELOPER OPTIONS BY CLICKING ON THE BUILD NUMBER SEVERAL TIMES AND ALSO TURN ON THE USB DEBUGGING
THEN YOU HAVE TO REFLASH THE FIRMWARE
THEN AFTER FLASH TWRP THEN DM VERITY ZIP AND THEN MAGISK TO ROOT AND THEN BOOT INTO SYSTEM AND ENJOY
THANKS FOR HELPING me @shah22

Ah nice, so you need to flash HOME_CSC to make it work.. thats what i wanted to confirm ..
Enjoy
Edit : in your No. 4 step : we turn "ON" OEM UNLOCK in the developer option but you wrote "turn off" ? ..
Sent from my S7 Edge using XDA Labs

shah22 said:
Ah nice, so you need to flash HOME_CSC to make it work.. thats what i wanted to confirm ..
Enjoy
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
If you need to flash clean try ODD CSC and if you want to save data flash HOME CSC

shah22 said:
ah nice, so you need to flash home_csc to make it work.. Thats what i wanted to confirm ..
Enjoy
edit : In your no. 4 step : We turn "on" oem unlock in the developer option but you wrote "turn off" ? ..
Sent from my s7 edge using xda labs
Click to expand...
Click to collapse
hey sim card not working..
I am using jio sometimes it is showing networks with volte and sometime it is showing nothing..and thanks for editing my point

[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy Note 20 & Note 20 Ultra Exynos

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Official TWRP 3.6.1-* For Galaxy Note 20 & Note 20 UltraOnly for exynos variants - N980F / N981B / N985F / N986B (Europe - Global, Single/Dual-SIM)
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Kernel Features:
N986BXXU3FVC5 kernel source (OneUI 4.1 / March 2022 sourcecode)
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
Recovery Features:
Android 11 tree
built in full 64 mode
toybox/busybox support
compatible with Android 12.0 and above
Downloads:
Galaxy Note 20 (c1s / N980F / N981B)
Galaxy Note 20 Ultra (c2s / N985F / N986B)
AVB disabled vbmeta
* official TWRP builds are not up yet, you can find latest test builds in post #2, below
Instructions:
Odin (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .tar file according to your device
Download AVB disabled vbmeta .tar
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Heimdall (Linux)
Install heimdall & additional required packages:
Code:
sudo apt-get update
sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .img file according to your device
Download AVB disabled vbmeta .img
Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
Code:
sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
and press enter - once you press enter grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
TWRP
Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery
dd (Requires root)
Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13100000.ufs/by-name/recovery
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Sources:
Device trees - c1s / c2s
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9830/tree/android-11.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu

Compatibility and changelog:
06.05.2022 - Initial TWRP 3.6.1 release
Compatibility: Android 12 (OneUI 4.0 & 4.1)
Security patch: N/A
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
Further reading:
Full guide of how to unlock/root your device
Background on Android Verified Boot
Rollback protection

FAQ
Q: Can i use this recovery with other firmware then mentioned in compatibility?
A: Only with same Android version or Rollback protection might kick in and you won't be able to pass the lockscreen.
Q: Where do i get vbmeta.img?
A: From here, download the one you need according to install instructions.
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed multidisabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.

Updated first post with official pages from twrp.me, but since the builds are not up yet, i posted latest test builds in post #2.
Regards

well done sir

Hello! I have a rooted sm-n980f exynos European version. I rooted my phone using magisk patched AP file through odin. I am trying to flash twrp 3.6.1 above and vbmeta.tar using odin but it fails. What shall I do? Thank you!

edsoedso said:
Hello! I have a rooted sm-n980f exynos European version. I rooted my phone using magisk patched AP file through odin. I am trying to flash twrp 3.6.1 above and vbmeta.tar using odin but it fails. What shall I do? Thank you!
Click to expand...
Click to collapse
Can you attach a screenshot of Odin and eventually tell me if you see anything in particular changing on phone screen? It should throw an error or something below the usual download mode lines. A pic of phone screen would be nice but i'd assume it's your only phone..
Regards

corsicanu said:
Can you attach a screenshot of Odin and eventually tell me if you see anything in particular changing on phone screen? It should throw an error or something below the usual download mode lines. A pic of phone screen would be nice but i'd assume it's your only phone..
Regards
Click to expand...
Click to collapse
Nothing changes in the screen phone. Attached is odin screen. Thank you!

edsoedso said:
Nothing changes in the screen phone. Attached is odin screen. Thank you!
Click to expand...
Click to collapse
Can you please check Kg state line from download mode? What's written there?

corsicanu said:
Can you please check Kg state line from download mode? What's written there?
Click to expand...
Click to collapse
I installed twrp but it seems that it does not read the internal storage.

corsicanu said:
Can you please check Kg state line from download mode? What's written there?
Click to expand...
Click to collapse
And how to flash the multidisabler? it seems that everything is encrypted and is impossible to locate it in twrp?

I found it!
1. enter into TWRP (after flashing twrp.tar and Vbmeta.tar via odin), format data and reboot again in TWRP
2. Being in TWRP, transfer from PC to your phone multidisabler.zip and magisk zip.
3. flash them both
4. reboot system
That is all!

i have note 20 5G N918B , i make every thing but my mobile keep restarting in to TWRP recovery , not going to system

Hello! What can be done to remove encryption from TWRP? I have flashed disabler but it still continues to encrypt. I tried formatting data from twrp, changing file system to EXT4 and back to EXT2 but with no result so far. any help?

m7mdo_93 said:
i have note 20 5G N918B , i make every thing but my mobile keep restarting in to TWRP recovery , not going to system
Click to expand...
Click to collapse
edsoedso said:
Hello! What can be done to remove encryption from TWRP? I have flashed disabler but it still continues to encrypt. I tried formatting data from twrp, changing file system to EXT4 and back to EXT2 but with no result so far. any help?
Click to expand...
Click to collapse
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards

corsicanu said:
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards
Click to expand...
Click to collapse
yeah , after flashing multidisabler second time my mobile able to working .. thanks for your help

corsicanu said:
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards
Click to expand...
Click to collapse
Thank You very much. It worked!

A big thank you, it works fine.

hey.
i did everything from this guide, and i got root access+twrp installed.
the problem that i am facing, is that i canot install anything from twrp, due to insufficient space.
the system size that twrp is reading is only 8384kb, so every installation of gapps is failed.
i tried to wipe ,format data, and changing the file system, but nothing helped.
please give me an idea how to solve it.
thanks.

Good day
Does this work for Android 13 One UI 5.1?

Database Users

welcome