Database Users

Note 4 SM-N910F Samsung Reactivation Lock Activated - locked accidentally by Samsung?

Hi guys,
I got my Note 4 SM-N910F and installed latest update ROM from sammobile.com, respectively I've upgraded it from 4.4.4 to 5.1.1.
After reboot, I got the following message when restarted:
"This device is locked because of an abnormal factory reset. Sign in to the Samsung account that you have already signed in to on this device to confirm that it belongs to you."
Shortly: Samsung Reactivation Lock Activated
I've tried my Samsung account, on the web it logs in successfully, on my phone it doesn't let me login.
What should I do?
(phone is never locked, bought from Cosmote Romania, now Telekom Romania)
Thanks.

Samsung Reactivation Lock Activated - [ SOLVED ]
Hi guys,
I've succesfully deactivated the Samsung Reactivation Lock on my Samsung Note 4 SM-N910F - Android Lollipop 5.1.1. !!!
I'll tell you in detail how I did it. After 5 hours of data mining and documenting myself, I've gathered all the necessary data to do it.
Statement: On Samsung Note 4 with Lollipop 5.1.1, the Samsung Reactivation Lock cannot be deactivated!
In order to do that you need to downgrade it to KitKat 4.4.4. (thanks to brayhanrd for coming up with this downgrade-first idea in this post: http://forum.xda-developers.com/galaxy-s5/help/reactivation-lock-root-custom-rom-t3097964#post60511431
It can be done following these simple steps:
1) Downgrade the Samsung Note 4 software version from Lollipop 5.1.1 to KitKat 4.4.4 - using the stock 4.4.4 version specifically designed for your phone which can be downloaded from www.sammobile.com.
(Obs: if it was purchased from Verizon then THAT's the version you need to get it. I'm telling you this to avoid a lot of downgrade failures because of mismatch files and Odin writing errors, believe me, I read a lot about it today! )
- Downgrading from Lollipop to KitKat instructions and all the necesarry files to do it (e.g. Odin) can be found here: http://www.androidexplained.com/galaxy-note-4-how-to-downgrade-to-android-4-4-4-kitkat/ (thanks to Doug for documenting this )
If downgrade was successful, it should look like this: http://screencast.com/t/S9ONzxqPvaG
2) A work around to be able to turn off (deactivate) the Samsung Reactivation Lock can be found on this YouTube video: https://www.youtube.com/watch?v=U23TdbqJehA
- Long story short, the video emphasize what you need to do to get into the phone's Samsung Account, trick the already locked account and re-register yourself with a new (yet existing) Samsung account, which later on, will be seen by Samsung as the phone's default account, thus allowing yourself to register with it. What this guy's doing, basically is using the Text to Speech Samsung update to get logged in to the Samsung Galaxy Apps with this new Samsung account he created (or already had). From there, he gets back to the first phone setup steps and use this Samsung account which will be recognized by Samsung Reactivation Lock as being the default account (because he already signed-in with it into the Samsung Galaxy Apps) and voila, passed the protection.
3) Turn off the Samsung Reactivation Lock: After you tricked the Samsung Lock screen and passed over it reaching the classic, well known home screen, go to -> Settings -> Security -> and find the "Reactivation Lock" option and UNCHECK it! It will ask again for your Samsung account password, insert it and - ONLY THEN - you will have turned off the Samsung Reactivation Lock.
4) Upgrade back to Lollipop 5.1.1: same instructions here, first, upgrade only with stock image made specifically for your Note 4 version, to ba taken from www.sammobile.com or any other respectable place.
If upgrade was successful, it should look like this: http://screencast.com/t/U0BgITnrMmzi
Voila! you have a fully functional Note 4 phone again!
I hope this post will help you spare those 5 hours I used for reseaching these things!
ChiefRA

Not possible to downgrade 5.1.1 to 4.4.4
Funny you say you downgraded from 5.1.1 to 4.4.4 because everywhere I've read the consensus is the new bootloader makes this impossible.
Re: http://forum.xda-developers.com/note-4-sprint/help/downgrading-5-1-1-t3206848/post62923032
"If you upgraded your boot loader past OB7 (OE1, OF5 or OG5) You can no longer downgrade."
I tried your intructions anyway with the proper stock rom for my SM-N910P with 5.1.1 (OG5) and no dice. Odin failed right away.
Thanks anyway!
ChiefRA said:
Hi guys,
I've succesfully deactivated the Samsung Reactivation Lock on my Samsung Note 4 SM-N910F - Android Lollipop 5.1.1. !!!
I'll tell you in detail how I did it. After 5 hours of data mining and documenting myself, I've gathered all the necessary data to do it.
Statement: On Samsung Note 4 with Lollipop 5.1.1, the Samsung Reactivation Lock cannot be deactivated!
In order to do that you need to downgrade it to KitKat 4.4.4. (thanks to brayhanrd for coming up with this downgrade-first idea in this post: http://forum.xda-developers.com/galaxy-s5/help/reactivation-lock-root-custom-rom-t3097964#post60511431
It can be done following these simple steps:
1) Downgrade the Samsung Note 4 software version from Lollipop 5.1.1 to KitKat 4.4.4 - using the stock 4.4.4 version specifically designed for your phone which can be downloaded from www.sammobile.com.
(Obs: if it was purchased from Verizon then THAT's the version you need to get it. I'm telling you this to avoid a lot of downgrade failures because of mismatch files and Odin writing errors, believe me, I read a lot about it today! )
- Downgrading from Lollipop to KitKat instructions and all the necesarry files to do it (e.g. Odin) can be found here: http://www.androidexplained.com/galaxy-note-4-how-to-downgrade-to-android-4-4-4-kitkat/ (thanks to Doug for documenting this )
If downgrade was successful, it should look like this: http://screencast.com/t/S9ONzxqPvaG
2) A work around to be able to turn off (deactivate) the Samsung Reactivation Lock can be found on this YouTube video: https://www.youtube.com/watch?v=U23TdbqJehA
- Long story short, the video emphasize what you need to do to get into the phone's Samsung Account, trick the already locked account and re-register yourself with a new (yet existing) Samsung account, which later on, will be seen by Samsung as the phone's default account, thus allowing yourself to register with it. What this guy's doing, basically is using the Text to Speech Samsung update to get logged in to the Samsung Galaxy Apps with this new Samsung account he created (or already had). From there, he gets back to the first phone setup steps and use this Samsung account which will be recognized by Samsung Reactivation Lock as being the default account (because he already signed-in with it into the Samsung Galaxy Apps) and voila, passed the protection.
3) Turn off the Samsung Reactivation Lock: After you tricked the Samsung Lock screen and passed over it reaching the classic, well known home screen, go to -> Settings -> Security -> and find the "Reactivation Lock" option and UNCHECK it! It will ask again for your Samsung account password, insert it and - ONLY THEN - you will have turned off the Samsung Reactivation Lock.
4) Upgrade back to Lollipop 5.1.1: same instructions here, first, upgrade only with stock image made specifically for your Note 4 version, to ba taken from www.sammobile.com or any other respectable place.
If upgrade was successful, it should look like this: http://screencast.com/t/U0BgITnrMmzi
Voila! you have a fully functional Note 4 phone again!
I hope this post will help you spare those 5 hours I used for reseaching these things!
ChiefRA
Click to expand...
Click to collapse

eltrkbrd said:
Funny you say you downgraded from 5.1.1 to 4.4.4 because everywhere I've read the consensus is the new bootloader makes this impossible.
Re: http://forum.xda-developers.com/note-4-sprint/help/downgrading-5-1-1-t3206848/post62923032
"If you upgraded your boot loader past OB7 (OE1, OF5 or OG5) You can no longer downgrade."
I tried your intructions anyway with the proper stock rom for my SM-N910P with 5.1.1 (OG5) and no dice. Odin failed right away.
Thanks anyway!
Click to expand...
Click to collapse
Let me help you further because IT IS POSSIBLE. I've done it! Are you sure you read my thread correctly where I've stated that:
...using the stock 4.4.4 version specifically designed for your phone
Click to expand...
Click to collapse
You need to download a stock version of 4.4.4. specifically made for your phone version, model and mobile operator.

maybe for the sm-n910f but not the sm-n910p
I greatly appreciated your response, I spent almost the entire day yesterday working on this with no success.
Just so you know, I did in fact download the stock rom made specifically for my sm-910p, here:
http://androidromupdate.com/sprint-galaxy-note-4-sm-n910p-stock-firmware/
I'm on N910PVPU4COG5 now which is Lolipop 5.1.1 now.
I tried downgrading to N910PVPU1ANK2 Kitkat 4.4.4 and no go.
That is definitely the stock firmware for my device.
I did a factory reset & wiped cache first, then tried flashing with odin and after a successful md5 check it failed.
Not sure but maybe because you had the international version the bootloader is different?
But again, I'm sure it didn't work at that seems to be the consensus everywhere else too. that once you go above OB7 there's no going back on the N910P.
ChiefRA said:
Let me help you further because IT IS POSSIBLE. I've done it! Are you sure you read my thread correctly where I've stated that:
You need to download a stock version of 4.4.4. specifically made for your phone version, model and mobile operator.
Click to expand...
Click to collapse

I would suggest to not give up just yet.
Verify the following:
a) From the page you gave me http://androidromupdate.com/sprint-galaxy-note-4-sm-n910p-stock-firmware/ - I know it sais there It cannot be done, just ignore that - did you installed the Drivers on your computer before you plugged in your phone?
b) Did you tried both 4.4.4. versions available?
c) Did you tried multiple times to flash it? As it opten happens to crash 1,2,3 time until you get it done right. (in between the flashes, try reconnecting the phone to the computer and restarting it).

Try Try Try Again...
Thanks for your advice. I would like to downgrade and so haven't given up just yet; you gave me hope (even a shot in the dark)!
ChiefRA said:
I would suggest to not give up just yet.
Verify the following:
a) From the page you gave me http://androidromupdate.com/sprint-galaxy-note-4-sm-n910p-stock-firmware/ - I know it sais there It cannot be done, just ignore that - did you installed the Drivers on your computer before you plugged in your phone?
A: Yes, I have installed the drivers on my computer and successfully flashed with odin before and my com port is detected, everything is working on that end. However, I read today someone said they could only use odin 3.10 to flash without it failing so I will try that too.
b) Did you tried both 4.4.4. versions available?
A: No, I'm going to try the older version of KitKat 4.4.4 next, N910PVPU1ANIE
c) Did you tried multiple times to flash it? As it opten happens to crash 1,2,3 time until you get it done right. (in between the flashes, try reconnecting the phone to the computer and restarting it).
A: OK, I will try this and report back.
Click to expand...
Click to collapse
FYI regarding being unable to downgrade from 5.1.1 to 4.4.4:
http://forum.xda-developers.com/not...ding-5-1-1-t3206848/post62923032#post62923032
http://forum.xda-developers.com/showpost.php?p=61959946&postcount=157
http://forum.xda-developers.com/showpost.php?p=61803843&postcount=151
I'm not giving up just yet!

hi guys!! im having the same issue with my note 4 n910u.. just flashed to 5.1.1 and blocked bootloader.. i dont know what to do..!! the phone was with my samsung account and the device appers to be OFF when i check samsungs web.
someone?? any solution??

hi guys, same problem here, n910c 5.1.1 can't downgrade, any solve?

Samsung Reactivation Bypass Alternative
Hi all,
This is my first posting and reply to a thread. Hope all is doing well.
After many many many attempts to either bypass or deactivate Knox's reactivation lock.. I was finally successful. I"m sure you can imagine how i was jumping up and down..
Any who, here's how i did it:
What you need:
1- An OTG Cable
2- A USB flash drive
3- Samsung Google bypass
First thing I did was factory reset my Verizon Note 4 from the recovery mode.
If you have another android phone available, that would be useful. Take the OTG cable plus it into the extra android phone and plug in your USB flash drive. It will either pop up or ask you to reformat the drive. You want to make sure that the USB flash drive is compatible with android devices. If you don't have an extra phone, reformat your USB flash drive using CMD (format Fat32.)
After that's completed, plug your flash drive into your laptop/desktop and drag the file you downloaded (Samsung google bypass) to your flash drive.
IF YOU CAN'T BEAT THEM, JOIN THEM!
Power on your android phone, after it turns on, plug your OTG cable into your phone and attach your USB flash drive. Wait a few seconds so your phone can recognize the new hardware. A folder from the flash drive should pop. Now run the Samsung Google Bypass file. This will take you to the settings on the phone. Connect to your WiFi.
Click on the Security tab and check "Unknown Sources" and then click ok.
In the same tab> Click on where is says "Go to website". That will open a browser. If for any reason you don't have that option in that tab, in the settings options, click on "Accounts" and add your gmail account to the phone. Go back to the settings options and click on your Google account. We need to get this to the browser.
After clicking on your account, scroll down to where is says "Smart Lock for passwords", go ahead an open that up.
You will see "Google Account" - Click on it. That should take you to a browser.
(If for any reason with those option don't take you to a browser, search the settings section to find a way. THERE IS ALWAYS A WAY)
Now we are almost done!
Download Aptoide> It will ask you all the prompts to install> after its done, click on open.
Download Knox> it will ask you to upgrade> go ahead and upgrade it> after thats done, open up the knox app and create a new account. This will now save to your phone.
You can unplug the OTG cable and restart your phone. But before doing so, make sure that account is was successfully created.
You will go back to set up wizard. Go ahead and set up your phone. You should not have any problems now.
Hope this works for you as it did for me.
Thanks for reading
---------- Post added at 03:48 PM ---------- Previous post was at 03:41 PM ----------
Forgot to mention, when you download the Samsung Google bypass, make sure its a APK and if its in a rar file, unzip it.
QueenElizabethMaseda said:
Hi all,
This is my first posting and reply to a thread. Hope all is doing well.
After many many many attempts to either bypass or deactivate Knox's reactivation lock.. I was finally successful. I"m sure you can imagine how i was jumping up and down..
Any who, here's how i did it:
What you need:
1- An OTG Cable
2- A USB flash drive
3- Samsung Google bypass
First thing I did was factory reset my Verizon Note 4 from the recovery mode.
If you have another android phone available, that would be useful. Take the OTG cable plus it into the extra android phone and plug in your USB flash drive. It will either pop up or ask you to reformat the drive. You want to make sure that the USB flash drive is compatible with android devices. If you don't have an extra phone, reformat your USB flash drive using CMD (format Fat32.)
After that's completed, plug your flash drive into your laptop/desktop and drag the file you downloaded (Samsung google bypass) to your flash drive.
IF YOU CAN'T BEAT THEM, JOIN THEM!
Power on your android phone, after it turns on, plug your OTG cable into your phone and attach your USB flash drive. Wait a few seconds so your phone can recognize the new hardware. A folder from the flash drive should pop. Now run the Samsung Google Bypass file. This will take you to the settings on the phone. Connect to your WiFi.
Click on the Security tab and check "Unknown Sources" and then click ok.
In the same tab> Click on where is says "Go to website". That will open a browser. If for any reason you don't have that option in that tab, in the settings options, click on "Accounts" and add your gmail account to the phone. Go back to the settings options and click on your Google account. We need to get this to the browser.
After clicking on your account, scroll down to where is says "Smart Lock for passwords", go ahead an open that up.
You will see "Google Account" - Click on it. That should take you to a browser.
(If for any reason with those option don't take you to a browser, search the settings section to find a way. THERE IS ALWAYS A WAY)
Now we are almost done!
Download Aptoide> It will ask you all the prompts to install> after its done, click on open.
Download Knox> it will ask you to upgrade> go ahead and upgrade it> after thats done, open up the knox app and create a new account. This will now save to your phone.
You can unplug the OTG cable and restart your phone. But before doing so, make sure that account is was successfully created.
You will go back to set up wizard. Go ahead and set up your phone. You should not have any problems now.
Hope this works for you as it did for me.
Thanks for reading
Click to expand...
Click to collapse

queenelizabethmaseda said:
hi all,
this is my first posting and reply to a thread. Hope all is doing well.
After many many many attempts to either bypass or deactivate knox's reactivation lock.. I was finally successful. I"m sure you can imagine how i was jumping up and down..
Any who, here's how i did it:
What you need:
1- an otg cable
2- a usb flash drive
3- samsung google bypass
first thing i did was factory reset my verizon note 4 from the recovery mode.
If you have another android phone available, that would be useful. Take the otg cable plus it into the extra android phone and plug in your usb flash drive. It will either pop up or ask you to reformat the drive. You want to make sure that the usb flash drive is compatible with android devices. If you don't have an extra phone, reformat your usb flash drive using cmd (format fat32.)
after that's completed, plug your flash drive into your laptop/desktop and drag the file you downloaded (samsung google bypass) to your flash drive.
If you can't beat them, join them!
power on your android phone, after it turns on, plug your otg cable into your phone and attach your usb flash drive. Wait a few seconds so your phone can recognize the new hardware. A folder from the flash drive should pop. Now run the samsung google bypass file. This will take you to the settings on the phone. Connect to your wifi.
Click on the security tab and check "unknown sources" and then click ok.
In the same tab> click on where is says "go to website". That will open a browser. If for any reason you don't have that option in that tab, in the settings options, click on "accounts" and add your gmail account to the phone. Go back to the settings options and click on your google account. We need to get this to the browser.
After clicking on your account, scroll down to where is says "smart lock for passwords", go ahead an open that up.
You will see "google account" - click on it. That should take you to a browser.
(if for any reason with those option don't take you to a browser, search the settings section to find a way. There is always a way)
now we are almost done!
Download aptoide> it will ask you all the prompts to install> after its done, click on open.
Download knox> it will ask you to upgrade> go ahead and upgrade it> after thats done, open up the knox app and create a new account. This will now save to your phone.
You can unplug the otg cable and restart your phone. But before doing so, make sure that account is was successfully created.
You will go back to set up wizard. Go ahead and set up your phone. You should not have any problems now.
Hope this works for you as it did for me.
Thanks for reading
---------- post added at 03:48 pm ---------- previous post was at 03:41 pm ----------
forgot to mention, when you download the samsung google bypass, make sure its a apk and if its in a rar file, unzip it.
Click to expand...
Click to collapse
no job in 5.1.1 ok, not open browser or other to otg in or sidesync or other, 5.1.1 and 6.0 its no possible downgrade and not possible unlock account samsung

sm-n910p blocked
Hi guys,
I got my Note 4 SM-N910p and installed latest update ROM from sammobile.com, respectively I've upgraded it from 5.1.1. to 6.0.1.
After reboot, I got the following message when restarted:
"This device is locked because of an abnormal factory reset. Sign in to the Samsung account that you have already signed in to on this device to confirm that it belongs to you."
Shortly: Samsung Reactivation Lock Activated
I've tried my Samsung account, on the web it logs in successfully, on my phone it doesn't let me login.
What should I do?

Note 4 (N910C)
MY phone n910c is running to 6.0.1 Android Version.But i want to costomized Rom to install it.No Recovery is installed because it binary blocked by Reactivation Lock.How is it possible to Turn it off. I tried best but no problem solved.
Help me out to turn off reactivation lock.

Yo, so glad I found this thread. 4.4.4 saved my note 4

Galaxy S6 G920X / G925X Master Thread - Guides / Firmwares / Gear VR / more

So its been a long time coming, and I've finally compiled the files and time to make the long promised thread on flashing or modifying demo units. Most information herein will also apply to the G925X, granted that you have the corresponding firmwares.
If you find this compilation of information and/or files particularly useful, please consider buying me a beverage with the donate button, thanks!
Please do not direct link to my files. Send people to this thread instead. This prevents confused users and helps everyone involved.
Table of contents
Background info on the G920X
What can and can't be flashed
Returning to stock
Disabling retail mode
Creating a working Gear VR device while on a Demo Unit rom
Flashing to other variant roms
Special features like the fingerprint scanner
Available firmware files
Background info on the G920X / G925X
The G920X and G925X are live demo unit versions of the Samsung Galaxy S6 and S6 edge distributed internationally. They are almost full featured devices minus modem components and anything directly related to it. Although the bootloader allows for flashing of G920F / G925F files, several guides below offer a way to accomplish a nearly complete experience on the stock rom, which does not attempt to use the non-existent cell phone components but suffers a couple of minor drawbacks.
To keep it simple, the following features work, with caveats as noted -
Fast Charging - Stock G920X / G925X kernel may turn off charging around 70%. Will experiment with directly flashing other kernels on top and update this.
Gear VR - Works once following instructions below. Some power savings are evident and the phone does not seem to get as hot as the G920T/F/I and G925T/F/I, which is an awesome bonus. On stock G920X / G925X, there is an additional disclaimer screen when first putting the device on. There may also be a timeout where the currently open app closes if the device is not worn for a period of time. Need to do more experiments. Please test and report your own findings. You can always flash a G920F / G925F rom and compare.
Fingerprint scanner - Works after flashing 5.1.1 bootloader and rom and running software update, then flashing to G920F / G925F. Should also be able to root the stock rom and replace the settings apk with one from the G920F / G925F to get it working (possibly fingerprint packages as well).
32GB memory - Unfortunately this one is a bit painful. Samsung has started signing their PIT partition map files blocking us from flashing one with a reasonable hidden partition size (stock is 4gb). Until this is cracked there is no way to reintegrate this space into user data. In the meantime, if you have root you can edit the default mounting options for the hidden partition (change to rw) and create a symlink or similar to it in your userdata partition as a partial workaround.
What can and can't be flashed
All G920X / G925X and G920F /G925F roms should work, but you must remove bootloader files (cm.bin, sboot.bin, param.bin, modem.bin) to use G920F / G925F roms correctly.
If your G920X / G925X is currently on 5.0.2, you may have issues flashing or using certain features like fingerprint on 5.1.1 roms due to the old bootloader. It's recommended to update to the newer one using the files below, running the one available system update, and then proceeding with custom recovery and G920F / G925F flashing.
Returning to stock
Simple enough, for G920X, download the files below and use odin 3.10.6 or newer to load up all three. If you were on 5.0.2 or don't know, go into the odin options tab and check off bootloader update before starting. There is currently one update available that will download and install after you finish setting up the rom.
S6 Edge, G925X, see post here and use the files linked to revert to stock and obtain a newer bootloader - http://forum.xda-developers.com/showpost.php?p=63762911&postcount=104
Disabling retail mode
There are two main apps and main passwords to deal with here, the admin password, 5444, and the master password, M729Q16K8546. After your system has been flashed and updated, enter the application called "RetailMode" and enter the admin password. Untick Play time scheduling (this setting may not stick) and then Service Enable. You must now enter the master password. Now exit the app and open "Samsung Retail Mode" and enter Customize Experience Contents, entering the admin password. Disable Retail contents protection (wait a bit for it and tap a few times to keep the device awake until it says that setup is finished), and, for safety, set the auto reset timer to the maximum timeout (3 hours?). Restart the app and enter Configuration Settings. Enter the admin password and disable the Factory Reset protection. Enter the master password once more and choose NOT to reset the device. Now tap "Delete hidden folders" and confirm. At this point you've finished with both retail mode apps.
You're now free to delete the folder in the main user storage called "Retail" or "RetailMedia". This is a big folder so you'll be happy to see it gone. If for any reason it wont delete, turn the retail contents protection from above back on, and after the reboot enable and disable service mode again. Now turn off retail protection (keeping the device awake) and delete the folder. If all else fails, delete if via your PC while the wizard is turning protection off.
Optionally, download Package Disabler Pro and disable the two retailmode applications used above. This will remove the notification tray icon as well as ensure that the services are not turned back on.
If at any point you factory reset the device, you will likely need to repeat this process.
Creating a working Gear VR device while on a Demo Unit rom
Currently recommend using a G920F / G925F rom instead if Gear VR is your primary use case.
You'll need to start by returning to a baseline stock setup with the files at the bottom of the post as directed above. Once you've booted into it and set up (samsung account sign in NOT necessary), check for system updates and let it update to the latest build. Disable retail mode as per above and delete its stray files. Download the Oculus Base package here - https://drive.google.com/file/d/0B4LLzOQW_EV4TzFRWmhqbEFNZkk/view?usp=sharing and extract all included APKs onto your phone. Install ALL of them, then open the Oculus app and sign in / sign up, then give the app a moment to recognize that you have all requisite APKs already installed. That's it! You're ready to slide the device into your Gear VR, accept the "extra" disclaimer page until a full disable method is found, and start the tutorial/download more apps. If you disable bloatware using package disabler, be aware that disabling some things will cause the Oculus app to fail to install its own apps.
Flashing to other variant roms
G920F roms and possibly others will flash and run just fine. The only preparation required is the removal of the modem, bootloader, PIT, and related partitions. This is mainly because Odin will fail, and not specifically due to incompatibility (though some pieces are in fact incompatible). G920FXXU3QOKN is provided below in the downloads with the extra files already removed and ready to flash, otherwise, continue on for instructions on modifying any other rom package. For any 5.1.1 rom such as those listed below, use the Return To Stock instructions first if you aren't sure that you're already on a 5.1.1 compatible bootloader.
To proceed, take an existing rom archive and remove the .md5 from the filename. Copy it to an available *unix machine and run the following commands -
tar --delete --file=[Filename here] hidden.img
tar --delete --file=[Filename here] cm.bin
tar --delete --file=[Filename here] sboot.bin
tar --delete --file=[Filename here] modem.bin
If a PIT file is included, delete it in the same way.
Now load the file up in odin and flash it over. Note that if you flash any non-stock kernel or recovery, it may work for up to one reboot, after which it will bootloop. Always be sure to test across several reboots before confirming that a specific rom or kernel works.
Special features like the fingerprint scanner
Confirmed working when flashing to G920FXXU3QOJQ, further tests to follow.
Available firmware files
G920XXXU1BOH2 - Install and use system update to get latest version, then disable retail mode as listed above
If your current/old rom was 5.0.2, download the bootloader (BL) first and flash it in odin as bootloader update (use the checkbox in options).
PIT file included in CSC.
AP - https://mega.nz/#!34EG2BCZ!m1WywuvOP3awZ2S9Sh5WIxmhzP-pOSs0wG7DYA-ehyI
BL - https://mega.nz/#!bxt3XBIK!-iH4gXYjQFVa3GDWFpv-W1Jg_Jxy0wR9kLigTGKX368
CSC - https://mega.nz/#!K91RgQjZ!wPtNc1RNTLTfcQRRa2OYNQuy40p3haMAC9R4ccggxKg
Special -
CSC without hidden.img - https://mega.nz/#!Cs9lASQa!4vKuuFabqRb3QeQA3PPZHq92IDg8iRr9fPmnbYqUtx0
G920F Rom with modem/bl/hidden already removed and verified working - G920FXXU3QOKN - https://drive.google.com/file/d/0B4LLzOQW_EV4ck5CeEF3MWpWUkk/view?usp=sharing (dead link, you'll have to make your own, sorry)
G920XZCU1BOI2 Files, only to be used if you specifically need them -
AP - https://mega.nz/#!Cx03WTTQ!-LyhT6baji6zdorVVMHE8S9cNJkFataORuWRNHqGFRs
BL - https://mega.nz/#!C8NShYya!dWxyz1VuX-4Jjws60f2M732FUlniKlA_dmkQk5HhDps
CSC - https://mega.nz/#!a1U1zZYQ!4qezYWoj16PylxU3_2kLFaafK_pJvSREI5r7bZ0zHOU

Reserved

seargent007 said:
Reserved
Click to expand...
Click to collapse
Great work
I normally just flash twrp and install one of the many roms from xda and if they loop, i just flash one of the many custom kernels out there.
Aldo if you want use VR you have to use original Kernel, very pixelated with custom kernel
keep up the info would love to be able to use full internal storage instead of 20gb

Great Start!
Thinking of picking up a demo unit - looking forward to reading more.

this is so amazing, thank you for your post
This is so amazing, thank you for your post.
Bought ldu via fraud trade.
But still pretty happy - it was cheap and i bought it as a gear vr device in development purposes.
What i did to make it work with release vr SM-R322:
1) Made a root via odin anddownload.chainfire.eu\733\CF-Root1\CF-Auto-Root-zeroflte-zerofltexx-smg920f.zip?retrieve_file=1
2) Removed demo soft with this -droidviews.com\list-of-galaxy-s6-and-s6-edge-bloat-apps-how-to-remove-them-without-root\
3) Followed the instructions from section Creating a working Gear VR device while on a Demo Unit rom
I think root is not really necessary, cheers

Hi @Seargant007 i am interested in G920XZCU1BOI2 if you can help me

am intersted in G920XZCU1BOI2 can u pls help me

tareqak13 said:
Hi @Seargant007 i am interested in G920XZCU1BOI2 if you can help me
Click to expand...
Click to collapse
ixgeneral said:
am intersted in G920XZCU1BOI2 can u pls help me
Click to expand...
Click to collapse
Hey folks, what are you looking to do with that specific version?

Thanks for this, extremely helpful. I had a go with the stock G920X rom for use with a Gear VR (consumer edition), but the extra warning it shows was causing a few issues. Namely, that no matter what you do, after the disclaimer you *always* boot into Oculus Home. Meaning that you can't start an app from the Oculus store in regular phone mode, or an app from Sideload VR. It also meant I couldn't link my Twitch account to Oculus Video- perhaps I was doing something wrong but changing to G920F rom fixed my issue.

de.monkeyz said:
Thanks for this, extremely helpful. I had a go with the stock G920X rom for use with a Gear VR (consumer edition), but the extra warning it shows was causing a few issues. Namely, that no matter what you do, after the disclaimer you *always* boot into Oculus Home. Meaning that you can't start an app from the Oculus store in regular phone mode, or an app from Sideload VR. It also meant I couldn't link my Twitch account to Oculus Video- perhaps I was doing something wrong but changing to G920F rom fixed my issue.
Click to expand...
Click to collapse
Thanks, unforunately the easiest route is in fact to go to G920F roms, but it would be nice to get a fully functional stock rom (I hate the perpetually crossed out radio signal and such). I don't know how much longer I'll have access to a demo unit for, but if I can I'll make the Gear disclaimer screen a priority to hunt down.

de.monkeyz said:
Thanks for this, extremely helpful. I had a go with the stock G920X rom for use with a Gear VR (consumer edition), but the extra warning it shows was causing a few issues. Namely, that no matter what you do, after the disclaimer you *always* boot into Oculus Home. Meaning that you can't start an app from the Oculus store in regular phone mode, or an app from Sideload VR. It also meant I couldn't link my Twitch account to Oculus Video- perhaps I was doing something wrong but changing to G920F rom fixed my issue.
Click to expand...
Click to collapse
I have the same problem you had. Cannot test apps made with Unity because of the stupid warning. Thanks to SEARGENT (good fckin job ) I managed to get rid of retail mode, but when I flashed some g920f stock I bricked my s6. Now I reverted to the stock suggested by seargent.
I dont know why I bricked the phone, maybe I used a 5.0.2 variant.
Can you tell me what stock firmare worked for you , and how did you flash it ?
---------- Post added at 12:40 AM ---------- Previous post was at 12:32 AM ----------
seargent007 said:
Thanks, unforunately the easiest route is in fact to go to G920F roms, but it would be nice to get a fully functional stock rom (I hate the perpetually crossed out radio signal and such). I don't know how much longer I'll have access to a demo unit for, but if I can I'll make the Gear disclaimer screen a priority to hunt down.
Click to expand...
Click to collapse
Pfff, for me going to g920f seems imposible. What I am doing wrong ?
Maybe this : since I only use Windows I deleted the four bin files from one g920f stock image by decompressing the .tar.md5 file, deleting four files and compressing again to .tar (without md5). Odin accepted the .tar file, flashing was succesful, but it seems that it was a wrong version for me.

mirceanu said:
I have the same problem you had. Cannot test apps made with Unity because of the stupid warning. Thanks to SEARGENT (good fckin job ) I managed to get rid of retail mode, but when I flashed some g920f stock I bricked my s6. Now I reverted to the stock suggested by seargent.
I dont know why I bricked the phone, maybe I used a 5.0.2 variant.
Can you tell me what stock firmare worked for you , and how did you flash it ?
---------- Post added at 12:40 AM ---------- Previous post was at 12:32 AM ----------
Pfff, for me going to g920f seems imposible. What I am doing wrong ?
Maybe this : since I only use Windows I deleted the four bin files from one g920f stock image by decompressing the .tar.md5 file, deleting four files and compressing again to .tar (without md5). Odin accepted the .tar file, flashing was succesful, but it seems that it was a wrong version for me.
Click to expand...
Click to collapse
Did you follow steps for doing the bootloader update, and then follow up by having the rom update to the latest build? If you have, I can tell you that G920FXXU3QOJQ and G920FXXU3QOKN work perfectly fine for me. I'll upload the latter of the two with the modem/BL ripped out and PM you a link, so you can test it and let me know if you still have issues. Generally speaking you don't want to mess with tarring/untarring, but I don't know for sure that it's the cause of your issue.

seargent007 said:
Did you follow steps for doing the bootloader update, and then follow up by having the rom update to the latest build? If you have, I can tell you that G920FXXU3QOJQ and G920FXXU3QOKN work perfectly fine for me. I'll upload the latter of the two with the modem/BL ripped out and PM you a link, so you can test it and let me know if you still have issues. Generally speaking you don't want to mess with tarring/untarring, but I don't know for sure that it's the cause of your issue.
Click to expand...
Click to collapse
Seargent I sent you an PM with what I did.
Now I reflashed a G920FXXU3QOJQ version and it works well.
The next step I want to do is to root the unit to get rid of the bloatware that eats my memory and processot time. Any suggestion ?

The easiest way to turn off the bloat is by using package disabler pro, just be aware that disabling some of it will interfere with some system functions.

Any BL to use Marsh 6.0

datto666 said:
Any BL to use Marsh 6.0
Click to expand...
Click to collapse
Is this works room with sm-g920x already and how it is run

datto666 said:
Any BL to use Marsh 6.0
Click to expand...
Click to collapse
Your best (and probably only) bet is to flash back to stock and wait for an update to 6.0, then rip apart a 6.0 G920F package as detailed and flash it.

Hi , there is a ripped 6.0MM going around but cant boot with loli Bootloader , atm TWRP cant boot 6.0MM either.
So cant flash the LDU with Original BL and no TWRP that will boot 6.0MM
sit and wait i suppose

datto666 said:
Hi , there is a ripped 6.0MM going around but cant boot with loli Bootloader , atm TWRP cant boot 6.0MM either.
So cant flash the LDU with Original BL and no TWRP that will boot 6.0MM
sit and wait i suppose
Click to expand...
Click to collapse
That's my point, you need to sit on the stock rom and wait for an LDU update to be pushed that brings you to 6.0 before trying anything. If I can't get my hands on the odin files for 6.0, the procedure will still be the same even after the update is pushed; Revert to stock, update so your BL is updated, then go to another rom.

seargent007 said:
So its been a long time coming, and I've finally compiled the files and time to make the long promised thread on flashing or modifying demo units. Most information herein will also apply to the G925X, granted that you have the corresponding firmwares.
If you find this compilation of information and/or files particularly useful, please consider buying me a beverage with the donate button, thanks!
Please do not direct link to my files. Send people to this thread instead. This prevents confused users and helps everyone involved.
Table of contents
Background info on the G920X
What can and can't be flashed
Returning to stock
Disabling retail mode
Creating a working Gear VR device while on a Demo Unit rom
Flashing to other variant roms
Special features like the fingerprint scanner
Available firmware files
Background info on the G920X
The G920X is a live demo unit version of the Samsung Galaxy S6 distributed internationally. It is an almost full featured device minus modem components and anything directly related to it. Although the bootloader allows for flashing of G920F files, several guides below offer a way to accomplish a nearly complete experience on the stock rom, which does not attempt to use the non-existent cell phone components but suffers a couple of minor drawbacks.
To keep it simple, the following features work, with caveats as noted -
Fast Charging - Stock G920X kernel may turn off charging around 70%. Will experiment with directly flashing other kernels on top and update this.
Gear VR - Works once following instructions below. Some power savings are evident and the phone does not seem to get as hot as the G920T/F/I, which is an awesome bonus. On stock G920X, there is an additional disclaimer screen when first putting the device on. There may also be a timeout where the currently open app closes if the device is not worn for a period of time. Need to do more experiments. Please test and report your own findings. You can always flash a G920F rom and compare.
Fingerprint scanner - Works after flashing 5.1.1 bootloader and rom and running software update, then flashing to G920F. Should also be able to root the stock rom and replace the settings apk with one from the G920F to get it working (possibly fingerprint packages as well).
32GB memory - Unfortunately this one is a bit painful. Samsung has started signing their PIT partition map files blocking us from flashing one with a reasonable hidden partition size (stock is 4gb). Until this is cracked there is no way to reintegrate this space into user data. In the meantime, if you have root you can edit the default mounting options for the hidden partition (change to rw) and create a symlink or similar to it in your userdata partition as a partial workaround.
What can and can't be flashed
All G920X and G920F roms should work, but you must remove bootloader files (cm.bin, sboot.bin, param.bin, modem.bin) to use G920F roms correctly.
If your G920X is currently on 5.0.2, you may have issues flashing or using certain features like fingerprint on 5.1.1 roms due to the old bootloader. It's recommended to update to the newer one using the files below, running the one available system update, and then proceeding with custom recovery and G920F flashing.
Returning to stock
Simple enough, download the files below and use odin 3.10.6 or newer to load up all three. If you were on 5.0.2 or don't know, go into the odin options tab and check off bootloader update before starting. There is currently one update available that will download and install after you finish setting up the rom.
Disabling retail mode
There are two main apps and main passwords to deal with here, the admin password, 5444, and the master password, M729Q16K8546. After your system has been flashed and updated, enter the application called "RetailMode" and enter the admin password. Untick Play time scheduling (this setting may not stick) and then Service Enable. You must now enter the master password. Now exit the app and open "Samsung Retail Mode" and enter Customize Experience Contents, entering the admin password. Disable Retail contents protection (wait a bit for it and tap a few times to keep the device awake until it says that setup is finished), and, for safety, set the auto reset timer to the maximum timeout (3 hours?). Restart the app and enter Configuration Settings. Enter the admin password and disable the Factory Reset protection. Enter the master password once more and choose NOT to reset the device. Now tap "Delete hidden folders" and confirm. At this point you've finished with both retail mode apps.
You're now free to delete the folder in the main user storage called "Retail" or "RetailMedia". This is a big folder so you'll be happy to see it gone. If for any reason it wont delete, turn the retail contents protection from above back on, and after the reboot enable and disable service mode again. Now turn off retail protection (keeping the device awake) and delete the folder. If all else fails, delete if via your PC while the wizard is turning protection off.
Optionally, download Package Disabler Pro and disable the two retailmode applications used above. This will remove the notification tray icon as well as ensure that the services are not turned back on.
If at any point you factory reset the device, you will likely need to repeat this process.
Creating a working Gear VR device while on a Demo Unit rom
Currently recommend using a G920F rom instead if Gear VR is your primary use case
You'll need to start by returning to a baseline stock setup with the files at the bottom of the post as directed above. Once you've booted into it and set up (samsung account sign in NOT necessary), check for system updates and let it update to the latest build. Disable retail mode as per above and delete its stray files. Download the Oculus Base package here - https://drive.google.com/open?id=0B4LLzOQW_EV4WFZ6ZS1vUHBiT2c and extract all included APKs onto your phone. Install ALL of them, then open the Oculus app and sign in / sign up, then give the app a moment to recognize that you have all requisite APKs already installed. That's it! You're ready to slide the device into your Gear VR, accept the "extra" disclaimer page until a full disable method is found, and start the tutorial/download more apps. If you disable bloatware using package disabler, be aware that disabling some things will cause the Oculus app to fail to install its own apps.
Flashing to other variant roms
G920F roms and possibly others will flash and run just fine. The only preparation required is the removal of the modem, bootloader, PIT, and related partitions. This is mainly because Odin will fail, and not specifically due to incompatibility (though some pieces are in fact incompatible). G920FXXU3QOKN is provided below in the downloads with the extra files already removed and ready to flash, otherwise, continue on for instructions on modifying any other rom package. For any 5.1.1 rom such as those listed below, use the Return To Stock instructions first if you aren't sure that you're already on a 5.1.1 compatible bootloader.
To proceed, take an existing rom archive and remove the .md5 from the filename. Copy it to an available *unix machine and run the following commands -
tar --delete --file=[Filename here] hidden.img
tar --delete --file=[Filename here] cm.bin
tar --delete --file=[Filename here] sboot.bin
tar --delete --file=[Filename here] modem.bin
If a PIT file is included, delete it in the same way.
Now load the file up in odin and flash it over. Note that if you flash any non-stock kernel or recovery, it may work for up to one reboot, after which it will bootloop. Always be sure to test across several reboots before confirming that a specific rom or kernel works.
Special features like the fingerprint scanner
Confirmed working when flashing to G920FXXU3QOJQ, further tests to follow.
Available firmware files
G920XXXU1BOH2 - Install and use system update to get latest version, then disable retail mode as listed above
If your current/old rom was 5.0.2, download the bootloader (BL) first and flash it in odin as bootloader update (use the checkbox in options).
PIT file included in CSC.
AP - https://drive.google.com/open?id=0B4LLzOQW_EV4cE1XX290Mk1ycG8
BL - https://drive.google.com/open?id=0B4LLzOQW_EV4Z1dtVlJCSVZfVE0
CSC - https://drive.google.com/open?id=0B4LLzOQW_EV4VTNydlZxMEsyaWc
Special -
CSC without hidden.img - https://drive.google.com/open?id=0B4LLzOQW_EV4OENyS1p2dFd1WEU
G920F Rom with modem/bl/hidden already removed and verified working - G920FXXU3QOKN - https://drive.google.com/file/d/0B4LLzOQW_EV4ck5CeEF3MWpWUkk/view?usp=sharing
G920XZCU1BOI2 also available if someone has a specific need for it.
Click to expand...
Click to collapse
Special -
CSC without hidden.img - https://drive.google.com/open?id=0B4...ENyS1p2dFd1WEU
G920F Rom with modem/bl/hidden already removed and verified working - G920FXXU3QOKN - https://drive.google.com/file/d/0B4L...ew?usp=sharing
Click to expand...
Click to collapse
Are you saying that these surrender the 4Gb or so that the hidden.img is holding hostage?

S7 Edge - Custom Binary block by FRP Lock

Hi Guys,
I'm sure some of you may have heard about this error before.
Well, here's my sad sad story.
After trying to root my s7 edge,
Everything seems fine.
One day when i re-format my phone, and after which downloaded a few apps, there wasn't any issue at all
However when i restarted my phone, i saw the error msg : Custom Binary block by FRP Lock
And after which it can't boot up anymore.
Anyone of you guys able to help me ?
It'll be much appreciated!

Flash the stock firmware with ODIN
Envoyé de mon SM-G935F en utilisant Tapatalk

Thanks for the reply,
Sorry but I'm new. How do i do that?

pr0cupid said:
Thanks for the reply,
Sorry but I'm new. How do i do that?
Click to expand...
Click to collapse
What model? Country
Sent from my Blackberry Bold

Model : SM-G935FD
Country : Singapore

frp lock s7 edge
pr0cupid said:
Hi Guys,
I'm sure some of you may have heard about this error before.
Well, here's my sad sad story.
After trying to root my s7 edge,
Everything seems fine.
One day when i re-format my phone, and after which downloaded a few apps, there wasn't any issue at all
However when i restarted my phone, i saw the error msg : Custom Binary block by FRP Lock
And after which it can't boot up anymore.
Anyone of you guys able to help me ?
It'll be much appreciated!
Click to expand...
Click to collapse
i have same issue here, did you find any solutions ?

AFAIK when you factory reset your phone etc. if rooted you must remember to go back into Developer Options and re enable OEM Unlocking. This depends on the method you used to root, if you flashed dm-verity then you "May not" have this issue but cannot say for sure.
If it is already too late for you then I think you need to flash stock via Odin, plenty of threads out there on where to find the firmware (SamMobile) and how to do it. Even a quick google of the error gave me plenty of results...
One thing I have read is that you may have to keep trying to get your phone into download mode as the timing is much stricter with this error message.

I've the same problem with my g935x blocked on FRP when ii treid to root if any one can help .plz

https://drive.google.com/file/d/0B4sLrKlVs0CPQTBaamduLXdNYW8/view?usp=sharing
wHEN THE PHONE INICIALIZES PUT THIS FILE IN A OTG pendrivve install and do the reset by the menu of the phone.

djluisbento said:
https://drive.google.com/file/d/0B4sLrKlVs0CPQTBaamduLXdNYW8/view?usp=sharing
wHEN THE PHONE INICIALIZES PUT THIS FILE IN A OTG pendrivve install and do the reset by the menu of the phone.
Click to expand...
Click to collapse
@djluisbento This method seems to be interesting. But would you please clarify more about it. How to install the apk file on official recovery? Or it's enough to have the pendrive connected? And if yes, when this step should take place, after flashing the official ROM or when?
I'm stuck in a boot loop into recovery mode with dm-verity error, and unfortunately I have the FRP locked, so I can't install TWRP to flash the no-dm-verity.zip file to skip it.
Appreciate your suggestions.

I have the same issure. stock firmware wont install either. im just stuck on the FRP screen, cant even get into recovery

Same issue here, please help
Everything was fine with rooting and installing TWRP. after that did a restart/ attempt to goto twrp recovery, from then the s7 edge is stuck at "Custom Binary Blocked By FRP" and doesnt boot. please help!!

Have you do a Wipe then Format Data.
Then flash the no-verity-opt-encrypt zip in TWRP
Only if you want internal storage or data to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you only want a bootable system partition or writable data in TWRP:
Download the latest dm-verity and force encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
Click to expand...
Click to collapse
just quoting from the original thread by jcadduono.

Had that problem with a brand new phone, just wanted to get into download mode to see if the phone was tampered with and boom, flash screen with the red warning, flashed stock KSA (phone original CSC) , worked and phone was formatted, another surprise was faced, google did not accept my gmail account, had to shut down phone for 72 hours as read in my google search for people encountering same issue, once the 72 hours passed I was able to sign in and using my phone again.

maxkento said:
Have you do a Wipe then Format Data.
Then flash the no-verity-opt-encrypt zip in TWRP
just quoting from the original thread by jcadduono.
Click to expand...
Click to collapse
taiseer999 said:
Had that problem with a brand new phone, just wanted to get into download mode to see if the phone was tampered with and boom, flash screen with the red warning, flashed stock KSA (phone original CSC) , worked and phone was formatted, another surprise was faced, google did not accept my gmail account, had to shut down phone for 72 hours as read in my google search for people encountering same issue, once the 72 hours passed I was able to sign in and using my phone again.
Click to expand...
Click to collapse
Yes, flashed both Zips in recovery. I used my regular google account during the initial set up. If i wait for 72 hours, will the phone just boot back online just fine? Still, how do i make sure it wont goto the FRP lock again while trying to reboot or reboot to TWRP?

Solved,
Flashed with stock firmware, logged in with same google account, rooted with TWRP, installed Zubi's sound mod. Made sure to keep the 'OEM Unlock' stay turned on.

anoopgopalpt said:
Flashed with stock firmware, logged in with same google account, rooted with TWRP, installed Zubi's sound mod. Made sure to keep the 'OEM Unlock' stay turned on.
Click to expand...
Click to collapse
Helo
But U did this after 72 hours?

There are several methods depending on firmware version installed on your phone. Basically you have to enter in your phone, launch chrome, install an app which gives you the possibility to log into your google account from chrome and not set-up program.
I used successfully the Bluetooth method. Search for with google. You need a bluetooth headset and follow the steps described on youtube.
BTW. My phone was brand new and I flashed different official samsung firmware ( csc). I had to change google password in between and that resulted in FRP lock....
The wait time is 24 hours as is stated in google docs from site
Sent from my SM-G935F using XDA-Developers mobile app

Hello I have a related problem, opened a new thread, but my thread was closed, because my problem is related to this one, but more complicated. I have the same problem with FRP lock as described here, I can turn on the download mode but it wont be recognized by my computer. I tried different usb cables, drivers, even computers, it wont help. I cant flash it with odin, smartswitch, kies, no matter what I try. If I go to recovery mode it says `dm-verity verification failed...`and if I choose `apply update from ADB or SD card` it says `update from external storage disabled`. I dont know what to do anymore Its a new phone

FRP Block - no Dev Tools enabled
Hey guys,
you're my last resort, I've tried everything I happened to come across, to no avail.
First off, I did something incredibly stupid, don't even ask me why, as I have no idea what the heck drove me to do this in the first place.
Anyways, I was using the stock ROM on my S7 Edge, not tweaked or tinkered with besides the usual CF-Auto_Root. It never caused any trouble whatsoever. But for no reason at all this morning I decided to disable USB debuggin and OEM unlock. A short while later I rebooted my phone, which ended up in "Custom binary blocked by FRP Lock".
I gave a factory reset a try, but that obviously didn't change a thing. So I went to sammobile.com and downloaded the latest official stock ROM for my device and tried flashing it with Odin. Unfortnately Odin always fails with "Complete(Write) operation failed.", which I assume is because I messed with the settings in dev mode.
Next stop: ADB. I've never used that thing before, but I thought I should possibly be able to get it done following a simple guide. Unfortunately ADB won't even list my device when typing "adb devices". It's just an empty list.
So please guys, give me some tipps on how I can bring my phone back to life.

Phone will not booting anymore, please help

Hey guys since today I can not startup my phone. The screen stays black and in red
text I got the message "custom binairy blocked by FRP lock"
Can anybody help me please.

FRP lock stands for Factory Reset Protection, it's there to stop a phone being stolen and sold on. You must have made changes (root etc) without first setting the OEM Unlock to on in Developer Options.
You now need to flash the stock rom with ODIN and, on boot, log in using the Google account that was in use when the changes were made and the lock happened. Without that Google account you won't be able to use the phone. As soon as you do that, go into the Dev Options and select OEM Unlock to stop it happening again.

Thanks for your answer, is there any url where I can download the stockrom for the G935F and any tutorial how to flash with Odin?

http://forum.xda-developers.com/s7-edge/how-to/official-stock-firmware-update-odin-t3335065

Now I donloaded Odin 3.11 and the latest firmware file.
I did also extract the firmware file, now 5 files are comming up.
I understand to put one in AP, one into CP, one into BL and one into CSC.
But where do I have to put the file starting with HOME?

List the contents of the zip/rar.

It, is done now. Phone is booting again and I had to verify with my google account.
Thanks for your fast and kindly helping.

No probs, glad you sorted it.

(Soft-)Bricked S7 Edge/G935F with FRP lock & DRK error, but no root/OEM unlock/ADB

(Soft-)Bricked S7 Edge/G935F with FRP lock & DRK error, but no root/OEM unlock/ADB
Hello guys,
I bought a, what I thought to be, soft bricked S7 Edge (G935F) from the bay. It was listed as having sw issues, so I thought I could easily fix the issue myself. Stupid me, this one really isn't easy to fix. I've tried a lot of different hints that I found meandering around the web, but none of them have proofed working so far. I would appreciate some help because I don't seem to be making any progress.
When I got the phone, it would boot directly into Android Recovery with a dm-verity error on the bottom.
Below is what I have tried already:
1 . First I did the obvious, factory reset and wipe partition. No change.
2. Downloaded the latest firmware with updato (SM-G935F Region DBT) and flashed with Odin. It then booted into a screen with a hazard sign and a DRK error (Device does not have DRK, please install DRK first. press any button). Then returned to Android Recovery with variations of the DRK and dm-verity error messages
3. I flashed the same firmware again. This time the phone booted up to a Samsung error that said to use SmartSwitch's Emergency recovery. I tried but it asks for a recovery code and I don't have one.
4. I used an older version of SmartSwitch which gave me the initialization option where you need to input the device model and SN - SmartSwitch decided not to cooperate and noted that the S7 edge does not support initialization
5. I tried to flash CF-autoroot but it gave an error in Odin and failed because it is "Blocked by FRP Lock". I can't boot normally into android. Any workaround?
6. I used a dm-verity workaround file (G935FXXU1DQC4_FIX_DRK_dm-verity.tar) to actually get the phone booted up- but then it asks for the account information to do away with the FRP lock. And the former owner does not want to give me his login information. In addition, none of the workarounds (bluetooth, modem terminal prompts, etc.) did work.
7. Flashed oldest Android version I could find for the G935F - 5.1.1 - this gave me a prompt right after reboot that looks like the password request for encrypting memory. default_password and variations did not work. I am still stuck with...
No Support SINGLE-SKU
Supported API: 3
dm-verity error...
failed code : 0x02
...in the recovery
8. I flashed the combination file and was able to boot into Factory Binary and used the IMEI recovery option which is supposed to fix also the DRK issue. No luck.
So, this is where I am right now. If anyone out there still has sparks of hope, I would be delighted to hear about them.
Thanks much in advance!

Conversion software and ADB Shell
Small update - I booted into factory mode again using the conversion firmware. This way, I could connect to the device via ADB and use ADB shell. There is a guide (here: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516) which guides through IMEI recovery using the conversion software and factory mode - that is supposed to also help with DRK issues. Did not work for me.
Another great guide (here: https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965) used ADB shell to push and repair the DRK with some additional files. Since the device is not rooted, I did not get very far, either.
So, no progress whatsoever.
In summary, I can get the device booted up into factory mode using the conversion firmware, or, by using the dm-verity tweaked firmware, I can end up in the Google Account locked part of the initial start-up settings.
Any ideas?

Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At least that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.

JeffDC said:
Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At east that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the reply. How would this process look like? I have flashed the phone with all sorts of variations of Android L, M and N - plus the combination fw and the one with the dm-verity/DRK workaround which at least got the phone booted up. But then I am stuck at the google auth request.
I cannot flash anything custom since the FRP lock is on.
Hence, if there is any other way to re-do the phone as you are saying, I would live to hear about it.

https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965

JeffDC said:
https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the links.
Link #1: I can flash the file #1 and get the device visible for ADB by using the combination FW before starting the steps. Unfortunately, step #2 does not work due to lack of permissions. I guess because of missing root.
Links #2 and #3: These are the guides I was already referencing in my post #2 - they both do not work due to, I guess, missing root.

Smart Switch initialization
Update: I got smart switch to do the update and initialization for the device. Workaround was to use a different real serial number than the one of the actual device (I can only assume that it has got to do with country presets).
Cool stuff, all went smooth - but, still the same result. The device ends up in recovery showing the dm-verity error (failed code : 0x02) with FRP lock on and no root.

https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.

I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.

zzThrain said:
I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.
Click to expand...
Click to collapse
Thanks for the recommendation. Done that (MM downgrade and full wipe) - same result, still DRK error only booting to recovery.

JeffDC said:
https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.
Click to expand...
Click to collapse
Hi JEffDC, thanks for the follow-up hints. Very interesting read and approach. As commented in the other thread, I think the package download link in the opening post is dead. I am also curious to see 2 more complexities in action:
1. Will this work on a G935F variant (Exynos vs Snapdragon)?
2. The only way for me to get to the Google Account prompt is by using the modded dm-verity version mentioned in my first post - but I am not sure I can get ADB access enabled simultaneously

Good luck.

Deleted

Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.

JeffDC said:
Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.
Click to expand...
Click to collapse
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...

sathiere said:
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...
Click to expand...
Click to collapse
Yes, I am hoping for a response to my post there, near the end, clarifying. I think I get the method, and it's really pretty straight forward, really.

sathiere, I think basically what it does is provide two connections to the phone at the same time, one via Odin, and the other via direct ADB.
Step one is to flash a Universal boot loader, which is unlocked or can be unlocked via ADB. Now with the locked boot loader out of the way, on to getting rid of FRP.
Step two is run the. bat file which deletes the Persistence file, which is the Google encrypted setup file/FRP file. BOOM, FRP gone.
Then either stay on the Universal bootloader, or go back and flash the OEM.
Brilliant!

I have the same problem with a sm930f binary 2 boot loader. Stock Rom doesn't start and frp lock. How you fix it ? Thank you

Try this method
https://forum.xda-developers.com/general/general/solved-bypass-frp-lock-drk-error-t3779082