Unlock pattern changed by itself (how to bypass)

Unlock pattern changed by itself (how to bypass) - YotaPhone

Hello
This forum helps me a lot with my all smartphones (Thank You So Much), but now i have a big problem i cannot solve.
Yotaphone YD206 -> YD201 android MM with hybrid modem
Few days ago i configured Android Pay on MM and protected it by lock pattern. Yesterday i tried to unlock my Yota - wrong pattern. All tips won't help. I have locked bootloader and stock MM recovery. ADB not authorized (lock screen). I don't want to wipe all data. I saw somebody upload modded boot.img that allow to run adb comands but for Kit Kat only. Do You have modded boot for MM or signed recovery that can mount data or system partition and allow adb? Please help if U can.

Related

Unable to Unlock OEM

1-I Installed TWRP
2- I installed custom ROM CM 13
3-I need to update my custom ROM so i entered fastboot i found that OEM is disabled so i have to reboot to enable OEM unlocking
4-something happens so that i can't reboot to normal OS as power button doesn't make any response, i can only start fastboot using power and volume up, power and volume down doesn't make any response.
so the question is i need a way to install any thing that make my phone boot to OS regardless any thing (Formating ,.....)
Noting that:-
1-I can't use any (flash,erase,format,...) as OEM is locked.
2-I can't unlock OEM as it is disabled.
3-flashboot continue result device shutdown.
4-I am in a country that doesn't any support to oneplus devices.
Thanks in advance

How can you have a locked bootloader if you've already flashed a custom ROM? I'm not sure I understand what's going on - if you're able to boot into Android, there should be an option in the Developer Options menu to allow OEM unlocking. Again, I'm not sure if I understand what's going on but if you're able to access the bootloader (fastboot) you can flash the stock ROM found here: http://downloads.oneplus.net/2016-02-26/op2/OnePlus_2_OxygenOS_2.2.1/
I hope this helps!

Five cents he upgrade to OOS3 or MM H2OS with newer bootloader and failed to upgrade TWRP to compatible one with the bootloader, just like other thread 99% similar to this one, that I already answered to.

pitrus- said:
Five cents he upgrade to OOS3 or MM H2OS with newer bootloader and failed to upgrade TWRP to compatible one with the bootloader, just like other thread 99% similar to this one, that I already answered to.
Click to expand...
Click to collapse
Could you please provide link for any or post the solution.

Phone is bugged badly.

A while back i unlocked my bootloader and installed TWRP 2.8 (via fastboot) but that was way back ago. Later i tried installing the OTA update via the phone directly which didn't work so i didn't bother as it didn't affect much. But today i was about to install a new rom but i couldn't boot into recovery(booting into recovery via advanced power options, it just didn't work anyway) I thought i might as well reflash recovery using the fastboot method again but when i used fastboot oem unlock command ( I know i used it before i thought i had to do it again im so sorry) it just flashed the one plus logo, vibrated and redid the same thing again and again with no chance of booting.....after using command fastboot continue it booted ! ( God thank you !) but the phone only boots via fastboot continue command I need to get it back to normal !
Also I checked fastboot device info, it said device unlocked and device verified =false ?!
So my BOOTLOADER is locked on its own ? plus recovery isnt available ? AND it doesn't even boot the normal way?
Im really worried now ! please assist me ?
Link used for tutorial : https://forums.oneplus.net/threads/...-custom-recovery-root-efs-backup-more.345478/

Use the usual Qualcomm factory restore to revert everything back to working Lollipop software. From there you can try anything except OxygenOS 3.0 Beta or latest HydrogenOS without having to change to compatible recovery for those bootloaders.
Next time, at least try to use the search function, your case is nothing new and has already been answered many times over since the release of OOS3 beta and HydrogenOS Marshmallow ROM.

(Un)lock bootloader using Boot Unlocker

Good news everyone!
I've added the capability to unlock and lock the bootloader of the Yota Phone 2 to @segv11 's Boot Unlocker. There is already a pull request on GitHub for my code.
This means that everyone can now safely use custom recoveries without having to worry about warranty issues or losing data because of the mandatory factory reset.
Technical information
On the Yota Phone 2, the bootloader uses position `0x004FFE10` of the "aboot" partition, stored as `00` / `01` to indicate lock status, whereby `01` stands for "unlocked".
Download
For those eager to try it, until the pull request is merged, you can download the app from my GitHub repository. Please note that it is signed with my own developer key, so you will have to manually uninstall the official Google Play version from your device before installing it.

wow great just what i wanted :good::laugh:

Did you come to try it yet? I'd love to hear whether it works for other users.

For me (running android 6 beta) the app is not compatible with my device. (NOT WORKING ON DEVICE WAS THE VERSION FROM GOOGLE PLAY STORE)
I am using a yotaphone 2.
L.E.
could anyone confirm this app can relock the bootloader if root access is available? I have not yet rooted it yet.
I am asking this because we will need a locked bootloader to install google pay.

Did you try to install my version over the official Play Store version? This doesn't work, as the APK is signed with a different key. You have to uninstall the official version first.
Regarding a relock confirmation: I didn't try tools like SafetyNet, but when you relock the bootloader using Boot Unlocker, the bootloader command fastboot oem unlock again offers to unlock the device.
Unfortunately, I can't investigate much further currently, as I have installed Magisk, which needs a permanently unlocked device.

I testet the github version. The attempt to relock the bootloader on a unlocked Yotaphone2 on Android 6.0 ends in a boot loop

In my experience, the boot loop occurs when the boot partition is modified (e.g. after installing Magisk). If you flash the original boot partition (and potentially also recovery), the phone should be able to start just fine.

Different way?
Great job! Is any solution to unlock bootloader via fastboot mode like flashing modified aboot partition image? On my YD201 MM after turn off Extreme Power Saving Mode my lock pattern had been changed itself and i don't want to wipe data by fastboot oem unlock.

Red Magic 5G Bootloader Unlock Guide: OR get ROOT & TWRP without unlocking the BL!!!

Red Magic 5G Bootloader Unlock Guide: OR get ROOT & TWRP without unlocking the BL!!!
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
WARNING: ANY BOOTLOADER UNLOCK METHOD INVOLVES THE RISK OF BRICKING YOUR DEVICE PERMANENTLY. WHILE THERE IS USUALLY A WAY TO RECOVER, DO NOT ATTEMPT THIS PROCEDURE IF YOU DO NOT KNOW WHAT YOU ARE DOING. BAD THINGS CAN HAPPEN. YOU HAVE BEEN WARNED!!! YOU MAY BE LEFT WITH A USELESS BRICK!!! READ ALL FURTHER WARNINGS EXPERIMENTAL METHOD IN ORIGINAL DOWNLOAD FILE WORKS, I'M USING IT
If you want a NOOB guide look at this post: https://forum.xda-developers.com/nu...beginner-tutorial-unlock-bootloader-t4131585/
Also note a user has managed to fix the FP sensor post BL unlock, see this post here: https://forum.xda-developers.com/nu.../guide-calibration-finger-print-loss-t4132961
Still, I suggest root bypass it's better.
MegaNZ Link for Root without unlocking the Bootloader, and without breaking the FP, also includes instructions for installing BlackMagic5G (explanation below), adding HD VOLTE, how to restore from a brick, and some other cool tricks: https://mega.nz/file/igphSCTD#OybJo9t1zwvJ0bdbAcN2BCqxWXAfHdhk3JFB4_5xkVc
I suggest you flash my BlackMagic5G and don't unlock your bootloader at all - just root. It's CN 2.52 ROM based. You'll get VOLTE, , GApps installed, Rooted with Magisk, TWRP, debloated, YouTube Vanced, AdAway, SmartPack Kernel Manager, etc. - looks like the Global / NA variant of the ROM. Almost perfect except still uses Messages and Phone from Nubia. Plus you will enable Face Unlock not available in the Global or NA versions of the ROM, and FP will still work! Click on the Google Search bar widget and the mic icon takes you to the Google Assistant, the left icon is Google Feed, type in the middle bar for a Google Search. Has 1Weather Free weather widget that looks great, and Google Calendar widget for your whole month of activities. Translate, Lens, Chrome, all the Google Apps are there. And the Chinese Nubia apps are nearly all GONE!
MegaNZ Link for BlackMagic5G Beta - IT'S ONLY THE DATA PARTITION + ROOTED KERNEL + NA SPLASH SCREEN, you NEED to 1) install the Red Magic 2.52 ROM below FIRST 2) Root using the first link posted above 3) Flash restore this from TWRP: https://mega.nz/file/r9hF2BwS#RrAXiFWSBNX8dLqfrH8nNHo_uigPC8uYXonwhALhGbo
MegaNZ Link for the Red Magic 5G CN 2.52 ROM: https://mega.nz/file/aoxBFAqY#EDt2OZBGTME4ZGKnERKpK_t-aJT_rWgD0aqBFkilRcY
*** NOW THE BOOTLOADER UNLOCK INSTRUCTIONS ***
Go to Settings / About phone / Build Number (NX659_J_ENCommon_V3.08 on North American Variant), click 7 times, Now you are a developer message appears, go back a menu to Settings / Other system settings / Developer options.
Enable:
OEM unlocking "Allow the bootloader to be unlocked"
USB debugging "Debug mode when USB is connected"
Install Minimal ADB and Fastboot (Windows 10 in this example): https://www.androidfilehost.com/?fid=746010030569952951
Default install path is:
C:\Program Files (x86)\Minimal ADB and Fastboot\
Go to the Search button on the bottom on Windows 10, type cmd, Command Prompt will appear in the menu. Right click it and Run as Administrator. All commands to be typed will be run in this Command Prompt window (referred to as terminal) unless otherwise stated to run on the phone.
Now Terminal window appears (it says Administrator: Command Prompt in the heading):
Text displayed is:
Microsoft Windows
(c) 2020 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>
Typed in terminal:
cd "c:\Program Files (x86)\Minimal ADB and Fastboot"
I now connected the phone to a USB port on the PC.
On the phone, a Window appeared:
"Allow USB debugging?"
The computer's RSA key fingerprint is:
[36 digit code] Example:
C8:A17:E2:01:F6:A1
:368:10:E8:33:20:FB:
93:7D
Always allow from this computer (it's my computer so I clicked it since I trust the computer)
CANCEL / ALLOW (I clicked ALLOW)
Typed in terminal:
adb reboot bootloader
The phone reboots. Once the phone screen boots, in the center it says: Now you are in fastboot mode.
From the terminal I typed:
fastboot oem nubia_unlock NUBIA_NX659J
The terminal now displayed:
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) START set state to 1 ok!!!
In the terminal I typed:
fastboot flashing unlock *** DO NOT TYPE THIS IF YOU WANT TO KEEP A WORKING FP!!! READ TOP OF POST!!! AVOID THIS WITH THE EXPERIMENTAL METHOD OF ROOT WITH NO BL UNLOCK ***
Now a screen appeared on the phone with a big <!> red icon in the left corner. The rest in white text is a warning message. "By unlocking the bootloader, you will be able to install custom operating system on this phone. A custom OS is not subject to the same level of testing as the original OS, and can cause your phone and installed applications to stop working properly-
Software integrity cannot be guaranteed with a custom OS, so any data stored on the phone while the bootloader is unlocked may be at risk.
To prevent unauthorized access to your personal data, unlocking the bootloader will also delete all personal data on your phone.
Press the Volume keys to select whether to unlock the bootloader, then the Power Button to continue."
I selected UNLOCK BOOTLOADER and my device was completely erased. The factory OS loaded then. This process takes some time to complete.
Now the device rebooted with a warning message, and a big <!> yellow icon in the left corner.
"The boot loader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device.
Visit this link on another device:
g.co/ABH"
Now the device reloads the firmware apparently and wipes all user data. Upon setting up the phone, the fingerprint display registration comes up and asked to place my finger on the back of the phone. There is no fingerprint sensor on the back of the Redmagic 5G! It is under the screen! So this step must be skipped. The ROM setup is corrupt or incomplete, a beta possibly. I setup the phone then went into Settings / Security to try to add a fingerprint. The button to add fingerprint then appears. Once I click the button, I get this error:
Loss of fingerprint calibration data
Loss of fingerprint calibration data was detected.
Currently unable to complete fingerprint entry,
please contact Nuia after-sales service via
4007006600
See the XDA post for recalibrating the FP: https://forum.xda-developers.com/nu.../guide-calibration-finger-print-loss-t4132961
ROOT FOR ALL DEVICES:
(These files are included in the tools download zip, Magisk 20.4 and MagiskManager-v7.5.1.apk, but this is the official source as updates post): Go to XDA and Download Magisk Manager and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power, release the power button once the screen shows it loading, hold the volume up down until you see TWRP pop up). Flash Magisk from TWRP Install / Zip / sdcard / Magisk.zip reboot and you'll have root.
BL unlock first method was tested on North American variant and it works. But it breaks your FP sensor and gives you an annoying boot prompt.
If at any time you want to remove the OEM Bootloader unlock, you plug into the PC, go to the terminal for Minimal ADB and Fastboot, type:
adb reboot fastboot
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing lock (screen will prompt to relock BL, choose to Relock)
The phone should reboot and install the original software. BUT...
If it says you are corrupted well, you have more issues.
You'll have to reflash the stock recovery.img, reboot to stock recovery, wipe data, wipe cache, and flash the CN update.zip rom to a flash drive FORMATTED TO FAT32 (annoying as hell) But you NEED a USB-C to OTG Adapter to attach a Flash Drive / SDCARD this way). If you don't have one, you better reflash TWRP using the prior instructions and flash the update.zip from there. Install, select the update.zip, flash. Wipe Data, Cache, ART/Dalvik. Reboot.
Now it should WIPE the entire phone and be back to normal Android 10 setup non rooted, no unlocked bootloader. Always beware of data loss doing root functions!!! Always be prepared to setup your phone entirely over again. Google Backup is very good to turn on before you do any of this stuff if you have already installed apps.
*** WARNING - THIS BYPASS METHOD COULD GO AWAY AT ANYTIME. IT SHOULD EVENTUALLY BE FIXED BY NUBIA ***

mslezak said:
{Mod edit}
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
Settings / About phone / Build # click 7 times, now your a dev message appears, good back a menu, go to Additional Settings / Developer Options
Enable:
ADB debugging, + OEM unlock
Connect phone to PC, approve device on phone RSA key for USB debugging
From Minimal ADB and Fastboot:
adb reboot bootlader
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing unlock
(approve on phone with volume keys to unlock and hit the power button, now you'll get an annoyng mesage on boot as insecure unlocked BL) *ALL YOUR DATA WILL BE WIPED*
Next:
fastboot flash recovery recovery-TWRP-3.4.1B-0324-NUBIA_REDMAGIC_5G-CN-wzsx150.img
fastboot reboot recovery
Enter TWRP, set to not be removed by updates if prompted.
Boot up the device, setup as a new device. You're on stock ROM / kernel now unlocked.
Once you get up and running you'll want APK Mirror app to install stuff on the China Variant it's in the Nubia Playstore. Gboard download as well and set as default it's a lot easier than the Chinese keyboard that swaps between Chinese and English. Set size extra tall for this huge phone (I prefer anyhow). Chrome go download it from APK Mirror app as well. Then go to XDA and Download Magisk Manager and download it and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power). Flash Magisk from TWRP reboot and you'll have root.
Note on my testing the fingerprint did not work after unlocking the bootloader. It says to contact Nubia support at some odd number. Hopefully they fix this.
Click to expand...
Click to collapse
You were able to actually install TWRP? Not just boot it? I thought A10 devices cant have twrp permanently installed?

That is a very good question my friend. I had to reflash it several times while rooting so it appears you are correct.
Now a window when I FIRST installed popped up and said make Recovery read only so a system update. can't overwrite it, to this I didn't even pay attention. So assuming that question does lock down recovery, it should stick.

mslezak said:
That is a very good question my friend. I had to reflash it several times while rooting so it appears you are correct.
Now a window when I FIRST installed popped up and said make Recovery read only so a system update. can't overwrite it, to this I didn't even pay attention. So assuming that question does lock down recovery, it should stick.
Click to expand...
Click to collapse
So its not permanent? Thats what I thought.

Well it could be permanent...
VZTech said:
So its not permanent? Thats what I thought.
Click to expand...
Click to collapse
What I was trying to say is that I've never had a phone where I had to select "prevent recovery from being overwritten" so I just clicked off the message. Had I selected "keep TWRP from being overwritten" then possibly it sticks. It's just a matter of making the recovery partition READ ONLY.

mslezak said:
What I was trying to say is that I've never had a phone where I had to select "prevent recovery from being overwritten" so I just clicked off the message. Had I selected "keep TWRP from being overwritten" then possibly it sticks. It's just a matter of making the recovery partition READ ONLY.
Click to expand...
Click to collapse
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe

Can anyone send me backup of the super partition?
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)

Future updates...
VZTech said:
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe
Click to expand...
Click to collapse
Yes what I've been told by prior Redmagic Users 3 and 3S is the ROM is released, as long as your boot.img is not patched with Magisk, it can be installed through the menus in Settings / About Phone / Update or someplace like that. You just download the ROM to the appropriate folder on the phone.
So far I have 1 link to a China ROM update here: https://ui.nubia.cn/rom/detail/65
Now on how to install the ROM, I use the Chrome browser set to autotranslate webpages. Most of the Chinese will be translated from here: https://bbs.nubia.com//thread-1136030-1-1.html
Basically it's going to wipe your device clean, and you can use a Nubia backup tool which will save all your items to a folder. Which then you should copy to your PC before installing the new ROM. Then it gives you instructions to get that data back onto your updated device.

apersomany said:
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)
Click to expand...
Click to collapse
Your probably screwed. I had this issue on a rm3s. You will need an unbrick tool. It was released for the rm3s about 4 mos after release. NUBIA should have true fastboot images available for download, but they dont.

VZTech said:
Your probably screwed. I had this issue on a rm3s. You will need an unbrick tool. It was released for the rm3s about 4 mos after release. NUBIA should have true fastboot images available for download, but they dont.
Click to expand...
Click to collapse
That's because of the super (dynamic) partition, see from the latest (and only) ROM:
Excerpt of the ROM installation script where it delineates the dynamic vs non dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm, The other files (boot.img, dtbo.img, splash.img, etc. and other various files) should be flashable with fastboot.
# Update dynamic partition metadata
assert(update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")));
unmap_partition("product");
block_image_update(map_partition("product"), package_extract_file("product.transfer.list"), "product.new.dat.br", "product.patch.dat");
unmap_partition("vendor");
block_image_update(map_partition("vendor"), package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat");
unmap_partition("system");
block_image_update(map_partition("system"), package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
unmap_partition("odm");
block_image_update(map_partition("odm"), package_extract_file("odm.transfer.list"), "odm.new.dat.br", "odm.patch.dat");
# --- End patching dynamic partitions ---

apersomany said:
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)
Click to expand...
Click to collapse
You should be able to flash the latest ROM via EDL mode if you've ever used EDL mode before, it usually requires shorting pins together in the device, although some recoveries will let you just boot into EDL mode if the phone still boots. It will be detected. Although on this device with the dynamic partition, I don't know how you would flash these in EDL mode... dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm that do not look like fastboot flashable parts. Possibly the unbrick tool for Redmagic 3/3S could be modified to do this for you.

mslezak said:
That's because of the super (dynamic) partition, see from the latest (and only) ROM:
Excerpt of the ROM installation script where it delineates the dynamic vs non dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm, The other files (boot.img, dtbo.img, splash.img, etc. and other various files) should be flashable with fastboot.
# Update dynamic partition metadata
assert(update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")));
unmap_partition("product");
block_image_update(map_partition("product"), package_extract_file("product.transfer.list"), "product.new.dat.br", "product.patch.dat");
unmap_partition("vendor");
block_image_update(map_partition("vendor"), package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat");
unmap_partition("system");
block_image_update(map_partition("system"), package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
unmap_partition("odm");
block_image_update(map_partition("odm"), package_extract_file("odm.transfer.list"), "odm.new.dat.br", "odm.patch.dat");
# --- End patching dynamic partitions ---
Click to expand...
Click to collapse
Yes those .img files can easily be fastboot flashed. Unfortunately it wont solve his problem. He needs the nubia unbrick tool, which is tough to get. I dont understand why Nubia makes things difficult. They should provide proper Fastboot files.

I already tried edl (not to flash, but to recover my backup of the super partition) but it seems like it needed a firehose binary. I still can use bootloader, fastbootd, recovery. It's just that the recovery fails at assert dynamic partition update thing with a error 7 (probably because my super partition turned into a normal partiton). I tried to flash a super empty image made with lpmake and try flashing the ota but that didn't work. I think if someone gives me a backup of the super partition I could flash that and that could work. I also had an idea of flashing a super partition of another devices factory image to make my super partition a dynamic partition, but I couldn't find any online.

apersomany said:
I already tried edl (not to flash, but to recover my backup of the super partition) but it seems like it needed a firehose binary. I still can use bootloader, fastbootd, recovery. It's just that the recovery fails at assert dynamic partition update thing with a error 7 (probably because my super partition turned into a normal partiton). I tried to flash a super empty image made with lpmake and try flashing the ota but that didn't work. I think if someone gives me a backup of the super partition I could flash that and that could work. I also had an idea of flashing a super partition of another devices factory image to make my super partition a dynamic partition, but I couldn't find any online.
Click to expand...
Click to collapse
I get a Global Device on Monday. I'll try to use Qualcomm tools to make a brick restore image of Global. If I get one made I'll post all the tools to restore the device on Mega.nz. Because of the super partition it has to be done this way. Not via TWRP as you know. I'm working on Dev tools for this device as fast as possible.

mslezak said:
I get a Global Device on Monday. I'll try to use Qualcomm tools to make a brick restore image of Global. If I get one made I'll post all the tools to restore the device on Mega.nz. Because of the super partition it has to be done this way. Not via TWRP as you know. I'm working on Dev tools for this device as fast as possible.
Click to expand...
Click to collapse
Thank you so much!

Okay I can't add anything special but daaamn this community is amazing. So much help I love you all

To relock BL repeat the instructions with 1 different command
Just replace
fastboot flashing unlock
with
fastboot flashing lock
Again you approve to lock on the phone prompt with the volume keys and your phone will be wiped and all will be back to normal, you'll be locked. And back to phone setup.
I'd edit the original post but the moderators took away my rights!!! Because I posted a Telegram link WHY - how do you expect development to get better???
BTW anyone with a NEW phone arriving that can record the FP failures and all errors please contact me so I can send to Nubia. They are waiting for me to reproduce the error but I already setup my new phone... Thinking I wouldn't be the ONLY ONE to contact [email protected] ... Guys you want developer support on this phone or not. Contribute please.
mslezak said:
{Mod edit}
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
Settings / About phone / Build # click 7 times, now your a dev message appears, good back a menu, go to Additional Settings / Developer Options
Enable:
ADB debugging, + OEM unlock
Connect phone to PC, approve device on phone RSA key for USB debugging
From Minimal ADB and Fastboot:
adb reboot bootlader
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing unlock
(approve on phone with volume keys to unlock and hit the power button, now you'll get an annoyng mesage on boot as insecure unlocked BL) *ALL YOUR DATA WILL BE WIPED*
Next:
fastboot flash recovery recovery-TWRP-3.4.1B-0324-NUBIA_REDMAGIC_5G-CN-wzsx150.img
fastboot reboot recovery
Enter TWRP, set to not be removed by updates if prompted.
Boot up the device, setup as a new device. You're on stock ROM / kernel now unlocked.
Once you get up and running you'll want APK Mirror app to install stuff on the China Variant it's in the Nubia Playstore. Gboard download as well and set as default it's a lot easier than the Chinese keyboard that swaps between Chinese and English. Set size extra tall for this huge phone (I prefer anyhow). Chrome go download it from APK Mirror app as well. Then go to XDA and Download Magisk Manager and download it and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power). Flash Magisk from TWRP reboot and you'll have root.
Note on my testing the fingerprint did not work after unlocking the bootloader. It says to contact Nubia support at some odd number. Hopefully they fix this.
Click to expand...
Click to collapse

Just in case if somebody need a Chinese version of official ROM v2.46 for RedMagic 5G.
Code:
https://mega.nz/file/vc0DiabR#npahTop-JXZ9Mwv-lA7G6DxTG2qqOOAf6AwW8NdEEKw

mslezak said:
Just replace
fastboot flashing unlock
with
fastboot flashing lock
Again you approve to lock on the phone prompt with the volume keys and your phone will be wiped and all will be back to normal, you'll be locked. And back to phone setup.
I'd edit the original post but the moderators took away my rights!!! Because I posted a Telegram link WHY - how do you expect development to get better???
BTW anyone with a NEW phone arriving that can record the FP failures and all errors please contact me so I can send to Nubia. They are waiting for me to reproduce the error but I already setup my new phone... Thinking I wouldn't be the ONLY ONE to contact [email protected] ... Guys you want developer support on this phone or not. Contribute please.
Click to expand...
Click to collapse
we found out that using the cn rom it all works without even unlocking the bootloader, even while oem unlock was disabled in dev options but there is some kind of vbmeta img required. a full guide is incoming.

VZTech said:
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe
Click to expand...
Click to collapse
You can flash their NX659J-update.zip files directly from TWRP that's how we restored our bricked devices already. So OTA updates no, but you can download them anyway and flash from TWRP directly. Yes we have to figure out a concrete restore method which isn't 100% working yet. I.e. all your data is lost this way apparently AT THIS MOMENT... MORE TO COME.

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

Database Users

welcome