Database Users

[Q] Locked Out of Phone by PIN! + VPN Setting Errors

First off, this started with a possible error which I will describe incase anyone else encounters this problem with the SM-G9006v by China Unicom
I added my VPN and of course set up a PIN number. I didn't actually use the VPN for a few days, but when I went back to check on it the VPN had disappeared. I attempted to add a new VPN and it appeared in the box area for about a second and then also disappeared. I think it was at this point that I saw my first "Settings has encountered an error" message. The settings window sort of flashed and reloaded. I then went to the Lock Screen area and attempted to remove the PIN number, but was unsuccessful as the other less secure options were greyed out. At this point I pressed setup Password. The password screen came up and I started to enter my information when I received another Settings Error.
So, I am currently faced with a PIN lock screen that does not respond to my original PIN. My phone did not have USB Debugging Set and Reboot Lock is enabled, so I cannot enter recovery to factory reset my phone.
Solved By: Flashing a new Recovery via Odin, Please Note: You might need to use VolUp+Home+Power Button rather than VolDown+Home+Power Button

ddxv said:
First off, this started with a possible error which I will describe incase anyone else encounters this problem with the SM-G9006v by China Unicom
I added my VPN and of course set up a PIN number. I didn't actually use the VPN for a few days, but when I went back to check on it the VPN had disappeared. I attempted to add a new VPN and it appeared in the box area for about a second and then also disappeared. I think it was at this point that I saw my first "Settings has encountered an error" message. The settings window sort of flashed and reloaded. I then went to the Lock Screen area and attempted to remove the PIN number, but was unsuccessful as the other less secure options were greyed out. At this point I pressed setup Password. The password screen came up and I started to enter my information when I received another Settings Error.
So, I am currently faced with a PIN lock screen that does not respond to my original PIN. My phone did not have USB Debugging Set and Reboot Lock is enabled, so I cannot enter recovery to factory reset my phone.
I have no idea how to solve this problem, I have tried:
Millions of pins
Flashing a new Recovery via Odin (Passes, but nothing loads)
Using Flashboot & ADB (device not found)
Click to expand...
Click to collapse
Have you tried master reset in android recovery mode.

kms108 said:
Have you tried master reset in android recovery mode.
Click to expand...
Click to collapse
Yeah, I can't figure out how to get into that recovery mode. It freezes after:
Knox Warranty Void: 0x0
Qualcomm secureboot: enable (CSB)
AP Swrev: s1, t1, a1, p1
UDC START
If anyone has any suggestions...?

I got locked out on my Note 3 from a kernel/rom issue. Only way I could fix was flash stock Via Odin.. Seems like that's the method you'll have to take also.

I was able to solve my problem by flashing CWM via Odin. I thought it hadn't worked because I was using VolDown+Home+Power.
It worked when I used: VolUp+Home+Power

ddxv said:
I was able to solve my problem by flashing CWM via Odin. I thought it hadn't worked because I was using VolDown+Home+Power.
It worked when I used: VolUp+Home+Power
Click to expand...
Click to collapse
Could you link what CWM you used? I can't get my phone to recognize by Odin... or perhaps link how you did it. I would like to drop a custom rom or at least have a recovery that can flash gapps (default recovery fails to flash them for me)

Queueyou said:
Could you link what CWM you used? I can't get my phone to recognize by Odin... or perhaps link how you did it. I would like to drop a custom rom or at least have a recovery that can flash gapps (default recovery fails to flash them for me)
Click to expand...
Click to collapse
You might want to look at this post on a chinese forum http://bbs.gfan.com/android-7340315-1-1.html
It worked for me, but tripped Knox.
One extra step, not sure if it was necessary, but I installed 豌豆荚 pinyin: wandoujia on my computer, then hooked my phone in. I'm not entirely sure, but I think it helped install the drivers, which might be the only problem.
As far as getting gapps, I'm still working on that too. I put in a few apks to my phone, but gmail and play store are still broken....

ddxv said:
As far as getting gapps, I'm still working on that too. I put in a few apks to my phone, but gmail and play store are still broken....
Click to expand...
Click to collapse
Much appreciated! I don't speak Chinese and those around me that do aren't technically inclined. I don't even need a custom ROM if i can get gapps working.
I used a site to download apk's off google play store (website version) and it worked ok. Doesn't work for paid apps, but at least i was able to get google's translate / etc installed. Google translate wouldn't let me load off-line languages though sadly.
When I attempt Odin to flash a recovery or any other file, it won't reboot the phone, then in the stock recovery, odin doesn't see the phone, been a touch of a roadblock. I'll be sure to look into those links.

Queueyou said:
Much appreciated! I don't speak Chinese and those around me that do aren't technically inclined. I don't even need a custom ROM if i can get gapps working.
I used a site to download apk's off google play store (website version) and it worked ok. Doesn't work for paid apps, but at least i was able to get google's translate / etc installed. Google translate wouldn't let me load off-line languages though sadly.
When I attempt Odin to flash a recovery or any other file, it won't reboot the phone, then in the stock recovery, odin doesn't see the phone, been a touch of a roadblock. I'll be sure to look into those links.
Click to expand...
Click to collapse
My recovery ended up being Vol++Home+Power and download mode being Vol-+Home+Power. You might wanna just check that to make sure recovery isn't hiding there.

Locked Out of Phone by PIN!
ddxv Did you manage to root your SM-G9006V following the process provided in the Chinese Forum link that you provided? I sure would like to know, before I try...
S/F, Phillip

Hungup said:
ddxv Did you manage to root your SM-G9006V following the process provided in the Chinese Forum link that you provided? I sure would like to know, before I try...
S/F, Phillip
Click to expand...
Click to collapse
Yes, it worked.
Check this new thread for info about a ROM that includes google play: http://forum.xda-developers.com/showthread.php?p=52356416

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?

Samsung FRP Bypass

Hi, I'm a total noob on this but I don't know where to start to looking for an answer.
My girlfriend went on vacation (from Chile) to the united states, her mother gave her a cell phone (her cell phone at that moment) an almost new Samsung Galaxy S7 Edge (SM-G935P) from the Sprint Network.
Before returning to Chile the cell phone was unlocked (or so they said at Spring), so here in Chile she put her local carrier SIM but the cell phone never recognized the Sim Card.
So she hard reset the cell phone. Everything went well until he had to enter the original Gmail account for the cell phone. Her mother did not remember the password so after som trial and error, they manged to reset the Google Account. But now when I try to enter de Gmail and password give me this error: Unable to sign in device due to a recent password change. try again in 24 hours, I have waited more than 24 hours and still can't activate the account.
The cell phone is still showing at her known devices in her mother's Gmail account, and the password is correct but I can't by pass the Gmail Activation, I was reading that I can downgrade to a firmware that allowed me to by pass the Samsung FRP but I don't know wich firmware I can use.
Can someone plase guide me how can I activate this cell phone.
Thank you!

edit: You were right I apologize.
If you want to get your password then whoever knows the best information will need to tell google over the phone what that information was when initially set up...birthdays, time of creation,etc-when they ask and %100 will ask. If she/you don't know it..you may never get it back... but calling their --> Customer Support <-- is your best option.

For s7 edge Android 7.0
So I found a way to bypass Google frp on Android 7.0 for the s7 edge and couple other model, it's an old way but modified. First enter into the Google account login screen where it says verify your account. All you do is simply over load it with characters. Tyler a bunch misc letters and number until you have a long good string then begine select all copy paste do this until your phone seem like it going to freeze up. I did it until it took about 2-5 mins to go through. Doing this will send you to a screen says error something went wrong. Hit enternor continue and if you notice this time when it goes back to verify your account the screen should have a black background at the top where's your notifacatioons are . Repeat 2-3-4 times overloading it and getting the error message I'm not sure exactly how many time think it suffers a on phone and Android build I just know once isn't enough to do it so do it a fewbtime it'll take awhile to get the first error but after that you should have the character line copies and ready to paste. After a couple time hit back arrow on your phone clear to where it ask to select language or start screen and emergency call if done correctly it should now give you the accessibility menu also enter into the accessibility option and modify your set up. Mess with stuff a little be careful with setting up universal switches as you can really mess yourself up. At some point in time you should be able to get your notification menu to drop down and open. When this happens hit the little setting menu button long click it and it should shortcut you to system settings. Bypassing for temporarily. Set up your setting and movie your app permissions as much as possible. Now the trick is getting my Knox downloaded open and set up on your phone. Once you do this make sure you click on both my Knox and regular device administration for know to have some control and make sure you say yes for Knox to be able to reset wipe your phone . After device administration is set and that all done go to your pc or another phone tablet whatever and log into know online and you hold re your phone connected on it white a button that says wipe this phone. Click it make sure the phone has Wi-Fi or service connected and wait for phone to wipe this should reset frp and Google verification back to being a new phone. There ya go merry Christmas

Is this fix legit?^^

Master Shredder said:
Is this fix legit?^^
Click to expand...
Click to collapse
Fцck no it ain't legit. Dude probably got baked & strung up that nonsense to laugh at folks who tried it. You could string up a petrabyte worth of miscellaneous characters so long that your phone would be permanently frozen... & you wouldn't get an error message to pop up, let alone one that would change your notification bar background color or whatever else he said
☆KØŁØЯΛĐØ☆

Master Shredder said:
Is this fix legit?^^
Click to expand...
Click to collapse
No, It's not.
I still can not remove the Samsung FRP, I've tryed all the methods I found online, but still nothing.

S7 & S7 Edge FRP [SOLVED]
Here's the real S7 & S7 Edge FRP bypass method..
Nougat 7.0+ will NOT work; You NEED to downgrade to Marshmallow. Links to Stock Firmware & FRP Removal files posted at the bottom.
- Download & extract the .zip file from my Google Drive below to your PC, then extract + run Odin
- Flash the boot.tar file that corresponds with your device (enables ADB)
- Once the device reboots to the Welcome page, run the Qualcomm.bat file (reboots to Download Mode & removes FRP Lock)
- Back in Download Mode, flash the [MM] Stock ROM (CSC_HOME keeps user data; CSC wipes user data)
You've now successfully kicked FRP's ass from the device. Congrats.
NOTICE:
- You will be able to upgrade back to Nougat 7.0 following successful FRP Removal
- I INTENTIONALLY LEFT A FEW STEPS OUT. It took me a solid week to finally crack this migraine of a phone. You WILL have to figure some parts out on your own just like I did. If you cant, why are you even here?
Stock Firmware located here: https://forum.xda-developers.com/sp...rmware-g935p-pe1-official-sprint-6-0-t3414654
FRP Removal files located here: https://drive.google.com/open?id=0B-BpyLgU2mXlbkVGUDVHWkVnM0E
☆KØŁØЯΛĐØ☆

☆KØŁØЯΛĐØ☆ said:
Here's the real S7 & S7 Edge FRP bypass method..
Nougat 7.0+ will NOT work; You NEED to downgrade to Marshmallow. Links to Stock Firmware & FRP Removal files posted at the bottom.
- Download & extract the .zip file from my Google Drive below to your PC, then extract + run Odin
- Flash the boot.tar file that corresponds with your device (enables ADB)
- Once the device reboots to the Welcome page, run the Qualcomm.bat file (reboots to Download Mode & removes FRP Lock)
- Back in Download Mode, flash the [MM] Stock ROM (CSC_HOME keeps user data; CSC wipes user data)
You've now successfully kicked FRP's ass from the device. Congrats.
NOTICE:
- You will be able to upgrade back to Nougat 7.0 following successful FRP Removal
- I INTENTIONALLY LEFT A FEW STEPS OUT. It took me a solid week to finally crack this migraine of a phone. You WILL have to figure some parts out on your own just like I did. If you cant, why are you even here?
Stock Firmware located here: https://forum.xda-developers.com/sp...rmware-g935p-pe1-official-sprint-6-0-t3414654
FRP Removal files located here: https://drive.google.com/open?id=0B-BpyLgU2mXlbkVGUDVHWkVnM0E
☆KØŁØЯΛĐØ☆
Click to expand...
Click to collapse
Hi ☆KØŁØЯΛĐØ☆, I think I ****ed up.
I follow your instructions, but after the first step (flashing boot.tar) the phone whent on a endless reboot.
Please can you help me.

☆KØŁØЯΛĐØ☆ said:
Here's the real S7 & S7 Edge FRP bypass method..
Nougat 7.0+ will NOT work; You NEED to downgrade to Marshmallow. Links to Stock Firmware & FRP Removal files posted at the bottom.
- Download & extract the .zip file from my Google Drive below to your PC, then extract + run Odin
- Flash the boot.tar file that corresponds with your device (enables ADB)
- Once the device reboots to the Welcome page, run the Qualcomm.bat file (reboots to Download Mode & removes FRP Lock)
- Back in Download Mode, flash the [MM] Stock ROM (CSC_HOME keeps user data; CSC wipes user data)
You've now successfully kicked FRP's ass from the device. Congrats.
NOTICE:
- You will be able to upgrade back to Nougat 7.0 following successful FRP Removal
- I INTENTIONALLY LEFT A FEW STEPS OUT. It took me a solid week to finally crack this migraine of a phone. You WILL have to figure some parts out on your own just like I did. If you cant, why are you even here?
Stock Firmware located here: https://forum.xda-developers.com/sp...rmware-g935p-pe1-official-sprint-6-0-t3414654
FRP Removal files located here: https://drive.google.com/open?id=0B-BpyLgU2mXlbkVGUDVHWkVnM0E
☆KØŁØЯΛĐØ☆
Click to expand...
Click to collapse
Flashing the boot image tar file causes bootloop. I believe that's also the eng boot file? For root? How do you solve bootloop? Also what marshmallow were you on before doing this?

jazzdglass said:
Flashing the boot image tar file causes bootloop. I believe that's also the eng boot file? For root? How do you solve bootloop? Also what marshmallow were you on before doing this?
Click to expand...
Click to collapse
I have not been able to fix it yet, it wasn't on MM it was Nougat.
You know another boot file I can use?

keiichitroncio said:
I have not been able to fix it yet, it wasn't on MM it was Nougat.
You know another boot file I can use?
Click to expand...
Click to collapse
There is Nougat boot files. Check xda here for Qualcomm s7 root. There's a boot file you need to flash before doing adb root.bat..this enables adb, But this also causes bootloop.

jazzdglass said:
There is Nougat boot files. Check xda here for Qualcomm s7 root. There's a boot file you need to flash before doing adb root.bat..this enables adb, But this also causes bootloop.
Click to expand...
Click to collapse
I've been reading a lot a topics here at XDA and I'm overly confused about which method or boot file to use.
I think this could be the one:
https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
What do you think? although it is for another is for G935T no G935P
Thank you

keiichitroncio said:
I've been reading a lot a topics here at XDA and I'm overly confused about which method or boot file to use.
I think this could be the one:
https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
What do you think? although it is for another is for G935T no G935P
Thank you
Click to expand...
Click to collapse
Just downgrade to marshmallow.. Try PJ2.. I used that. Flash the boot file provided, run Qualcomm.bat via adb.. Then flash again 6.0.1... If phone reboot after flash boot file, you'll have to be very fast, after phone boot to welcome screen, before it reboots, keep running the Qualcomm.bat till u see adb recognize device. It will say error. About phone storage. Just ignore. It has been unlocked

Starting to see how much of a headache this sh¡t was is? Took me a solid week to crack it.
Bravo @jazzdglass Props on figuring it out
KØŁØЯΛĐØ

☆KØŁØЯΛĐØ☆ said:
Starting to see how much of a headache this sh¡t was is? Took me a solid week to crack it.
Bravo @jazzdglass Props on figuring it out
KØŁØЯΛĐØ
Click to expand...
Click to collapse
Do you happen to have the exynos adb bypass code?

OMFG this freaking worked!!
☆KØŁØЯΛĐØ☆ said:
Here's the real S7 & S7 Edge FRP bypass method..
Nougat 7.0+ will NOT work; You NEED to downgrade to Marshmallow. Links to Stock Firmware & FRP Removal files posted at the bottom.
- Download & extract the .zip file from my Google Drive below to your PC, then extract + run Odin
- Flash the boot.tar file that corresponds with your device (enables ADB)
- Once the device reboots to the Welcome page, run the Qualcomm.bat file (reboots to Download Mode & removes FRP Lock)
- Back in Download Mode, flash the [MM] Stock ROM (CSC_HOME keeps user data; CSC wipes user data)
You've now successfully kicked FRP's ass from the device. Congrats.
NOTICE:
- You will be able to upgrade back to Nougat 7.0 following successful FRP Removal
- I INTENTIONALLY LEFT A FEW STEPS OUT. It took me a solid week to finally crack this migraine of a phone. You WILL have to figure some parts out on your own just like I did. If you cant, why are you even here?
Stock Firmware located here: https://forum.xda-developers.com/sp...rmware-g935p-pe1-official-sprint-6-0-t3414654
FRP Removal files located here: https://drive.google.com/open?id=0B-BpyLgU2mXlbkVGUDVHWkVnM0E
☆KØŁØЯΛĐØ☆
Click to expand...
Click to collapse
You sir are a genius. I tip my hat to you.... The only method out of....pretty much the entire internet...that actually works. To all other modders, if you follow the instructions carefully, this will work. Thank again man.:good::good::good:

I have a G935V that is stuck with FRP. I reset my password today and then happened to try to flash a new ROM (didnt know about FRP at the time).
Been trying this all day, but cant get the S7 & S7 Edge QUALCOMM.bat to run on the phone... a flashed back to MM and the Boot.rar pushes fine, but when the phone gets to the welcome screen its like my computer doesn't recognize the phone is connected. Any ideas?

This worked great on my VZW s7 (just had to get the right VZW firmware)...
@KjK89, you have to run the .bat file before the welcome screen. I basically kept running it over and over during boot and it took before th welcome screen.

Check my post about SAMSUNG S7 Nougat 7.0 frp remove

Thanks So much, the only thing that actually worked!
☆KØŁØЯΛĐØ☆ said:
Here's the real S7 & S7 Edge FRP bypass method..
Nougat 7.0+ will NOT work; You NEED to downgrade to Marshmallow. Links to Stock Firmware & FRP Removal files posted at the bottom.
- Download & extract the .zip file from my Google Drive below to your PC, then extract + run Odin
- Flash the boot.tar file that corresponds with your device (enables ADB)
- Once the device reboots to the Welcome page, run the Qualcomm.bat file (reboots to Download Mode & removes FRP Lock)
- Back in Download Mode, flash the [MM] Stock ROM (CSC_HOME keeps user data; CSC wipes user data)
You've now successfully kicked FRP's ass from the device. Congrats.
NOTICE:
- You will be able to upgrade back to Nougat 7.0 following successful FRP Removal
- I INTENTIONALLY LEFT A FEW STEPS OUT. It took me a solid week to finally crack this migraine of a phone. You WILL have to figure some parts out on your own just like I did. If you cant, why are you even here?
Stock Firmware located here: https://forum.xda-developers.com/sp...rmware-g935p-pe1-official-sprint-6-0-t3414654
FRP Removal files located here: https://drive.google.com/open?id=0B-BpyLgU2mXlbkVGUDVHWkVnM0E
☆KØŁØЯΛĐØ☆
Click to expand...
Click to collapse
Anybody looking for a fix for Galaxy S7 and S7 Edge Factory Reset Protection Bypass needs to follow these steps and you'll get past this pesky protection.
The only step that wasn't clear was this:
- Flash the boot.tar file that corresponds with your device (enables ADB)
On Odin you have to choose the boot.tar file corresponding to your model number. This is done by selecting the BL button and only that one then in Odin click Start. This might be clear for veterans to flashing phones with new firmwares but it wasn't clear for me, being the n00b that I am. Thanks again. This worked great!

(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

[HELP] Samsung SM-G950F system & Os recovery ?

Hello,
Here is my problem.
2 days ago, I wanted to root my phone to get rid of any Google stuff (at this point I didn't know the existence of ADB commands :crying: ).
I followed a step by step youtube tutorial (youtube.com/watch?v=ZD-5twDm6XI), which works with TWRP, magisk and Odin (factory reset is needed).
Once everything is finished, my phone is finally rooted, and I grant superuser rights to Titanium app to uninstall google, and only SOME apps uninstalled totally (maps, chrome, facebook) BUT google play services won't uninstall. So, I try with System App Removal to uninstall google play stuff, and the same happens.
I reboot my phone, and it seems that everything disappeared... Not so sure... Indeed, the play store reinstall all applications as soon as I connect to the WiFi! and I have a persistent message "google play services stopped" that prevents me from browsing for example.
At this point, I use ADB commands, to remove anything which contains "com.blahblah.google.blahblah" and the play store (com.android.vending) with -k command. And it worked totally fine !!!!! I disconnect my phone, ready to backup my data. Idkw, i wanted to uninstall system app removal. IMPOSSIBLE from the phone, which says : "samsung One UI stopped" (I was in safe boot mode). My phone doesn't answer, so I reboot it.
Once it has booted, the TWRP menu screen appears. Ok, isn't that weird ? I swipe to allow changes, then I go to system to boot "normally" my phone.
A warning says : NO OS INSTALLED !!!! I don't understand, I panic, but finally boots my phone. Black charging screen. Forever.
I started first to flash an "official" Samsung ROM from Sammobile. TWRP indicates it is an invalid .zip, adb too. Odin doesn't manage to boot from the ROM too. I take a deep breathe and cry. Then I download the /e/ ROM which works fine !! but it has become impossible to backup my data from my samsung account....
So, I came to ask you a few things. WHY did it happen ? How can I be sure that there is no trace of TWRP anymore ? However, my phone storage is 64 GB and there is only 53,5 Gb free of internal storage !? Do you think the original firmware could be "hidden" in my files (e ROM is about 800Mos compressed) ?
It is stupid, but after my mistakes, I miss google...
I will do my best to reply asap.
Thank you for your help !
PS: -I'm a newbie in informatic, don't make things too complicated
-sorry for bad English, not my mother language

Google writes and distributes android.
There are many things in android that you cannot remove and still have a viable system.
imho you will have to flash a rom but we need your phones information (found in settings/system/about phone) model, version baseband, etc. etc
Others more knowledgeable can step in and help.
also read:
https://www.androidcentral.com/factory-reset-protection-what-you-need-know

KrisM22 said:
Google writes and distributes android.
There are many things in android that you cannot remove and still have a viable system.
imho you will have to flash a rom but we need your phones information (found in settings/system/about phone) model, version baseband, etc. etc
Others more knowledgeable can step in and help.
also read:
Click to expand...
Click to collapse
Thank you for your reply ! I've read your article about FRP but I'm afraid it's not my problem...
Here are some of my phone specifications :
model : SM-G950F
version baseband : G950FXXS8DTC1
OS : /e/ version 0.9-p-dev-dreamlte (LineageOS API : Ilama 9)
Android 9
I've been digging the web for ROMs but each time I feel unsecure about it (virus, etc...) so I hope maybe you have something trustworthy

[UPDATE]
S8recovery said:
Hello,
Here is my problem.
2 days ago, I wanted to root my phone to get rid of any Google stuff (at this point I didn't know the existence of ADB commands :crying: ).
I followed a step by step youtube tutorial (youtube.com/watch?v=ZD-5twDm6XI), which works with TWRP, magisk and Odin (factory reset is needed).
Once everything is finished, my phone is finally rooted, and I grant superuser rights to Titanium app to uninstall google, and only SOME apps uninstalled totally (maps, chrome, facebook) BUT google play services won't uninstall. So, I try with System App Removal to uninstall google play stuff, and the same happens.
I reboot my phone, and it seems that everything disappeared... Not so sure... Indeed, the play store reinstall all applications as soon as I connect to the WiFi! and I have a persistent message "google play services stopped" that prevents me from browsing for example.
At this point, I use ADB commands, to remove anything which contains "com.blahblah.google.blahblah" and the play store (com.android.vending) with -k command. And it worked totally fine !!!!! I disconnect my phone, ready to backup my data. Idkw, i wanted to uninstall system app removal. IMPOSSIBLE from the phone, which says : "samsung One UI stopped" (I was in safe boot mode). My phone doesn't answer, so I reboot it.
Once it has booted, the TWRP menu screen appears. Ok, isn't that weird ? I swipe to allow changes, then I go to system to boot "normally" my phone.
A warning says : NO OS INSTALLED !!!! I don't understand, I panic, but finally boots my phone. Black charging screen. Forever.
I started first to flash an "official" Samsung ROM from Sammobile. TWRP indicates it is an invalid .zip, adb too. Odin doesn't manage to boot from the ROM too. I take a deep breathe and cry. Then I download the /e/ ROM which works fine !! but it has become impossible to backup my data from my samsung account....
So, I came to ask you a few things. WHY did it happen ? How can I be sure that there is no trace of TWRP anymore ? However, my phone storage is 64 GB and there is only 53,5 Gb free of internal storage !? Do you think the original firmware could be "hidden" in my files (e ROM is about 800Mos compressed) ?
It is stupid, but after my mistakes, I miss google...
I will do my best to reply asap.
Thank you for your help !
PS: -I'm a newbie in informatic, don't make things too complicated
-sorry for bad English, not my mother language
Click to expand...
Click to collapse
I've been browsing through my root files and folders ( / ) ...
So :
/system is occupied with 2.33 GB
/vendor with 577 MB
/mnt with 9.01 GB
/proc with ... 236.9GB but every under-folder is empty... (explanations welcome !)
/storage is empty
If anyone could check on his device (S8 Exynos with android 9.0 Pie and One UI) if the files' sizes approximately matched, it would be great !

The one I just received is G950FXXS8DTC6 / G950FOXM8DTC1 / G950FXXS8DTC1 (after it took the Apr 1 update) so probably identical - a Yateley GU46 6GG UK phone. I am running it on ATT Prepaid(US) , which gave me the Apr 1 update. I don't know its history but it hasn't been modified - knox=0.
What you would need to do is get that zip and flash it with odin, but having no experience flashing the S8 myself, or any idea where to get that zip, I can be of no help to you. (I just came off a moto x4 which I ruined by flashing a couple custom rom's to try to help others on that forum - the blessings of Pie on that device!)(plus, taking the Apr 1 update on that phone requires a factory reset/wipe.) I needed a dependable phone here and in Europe on vacation.
Keep posting and ask someone to help you re-flash it.
EDIT: I wonder what a settings/general management/factory reset would do. But don't do one until someone here much more experienced with the S8 suggests it.
EDIT: WARNING WARNING WARNING -> Before flashing, ACTIVATE PIN in "Secure startup" (You'll be asked for it AFTER flashing!)
lockscreen and security / secure startup / require pin
I also see a note to delete your google account before doing this. Don't know if necessary.
EDIT: I believe I have found the rom - see pic This is from the SamFirm exe. 0.3.7 I put VOD for the region.
Remember: don't do anything with this until someone experienced in S8 tells you to!

Hi KrisM22,
I've already flashed with Odin, and I have talked about this on different forums, seen tutos on websites,... I hope this time it will work
I have the ROM required, selected activate pin, followed step by step the recommendations, and if I figured it out I will keep you up to date !

KrisM22 said:
The one I just received is G950FXXS8DTC6 / G950FOXM8DTC1 / G950FXXS8DTC1 (after it took the Apr 1 update) so probably identical - a Yateley GU46 6GG UK phone. I am running it on ATT Prepaid(US) , which gave me the Apr 1 update. I don't know its history but it hasn't been modified - knox=0.
What you would need to do is get that zip and flash it with odin, but having no experience flashing the S8 myself, or any idea where to get that zip, I can be of no help to you. (I just came off a moto x4 which I ruined by flashing a couple custom rom's to try to help others on that forum - the blessings of Pie on that device!)(plus, taking the Apr 1 update on that phone requires a factory reset/wipe.) I needed a dependable phone here and in Europe on vacation.
Keep posting and ask someone to help you re-flash it.
EDIT: I wonder what a settings/general management/factory reset would do. But don't do one until someone here much more experienced with the S8 suggests it.
EDIT: WARNING WARNING WARNING -> Before flashing, ACTIVATE PIN in "Secure startup" (You'll be asked for it AFTER flashing!)
lockscreen and security / secure startup / require pin
I also see a note to delete your google account before doing this. Don't know if necessary.
EDIT: I believe I have found the rom - see pic This is from the SamFirm exe. 0.3.7 I put VOD for the region.
Remember: don't do anything with this until someone experienced in S8 tells you to!
Click to expand...
Click to collapse
The flashing WORKED :victory: !!! It frightens me right now to check if TWRP has disappeared... But thank you anyway !z

S8recovery said:
The flashing WORKED :victory: !!! It frightens me right now to check if TWRP has disappeared... But thank you anyway !z
Click to expand...
Click to collapse
Excellent! What ROM did you flash it with?

KrisM22 said:
Excellent! What ROM did you flash it with?
Click to expand...
Click to collapse
I flashed a ROM from https://www.imei.info/download-firmware/samsung/samsung-g950f-galaxy-s8/SM-G950F/ , then I just followed the steps and flashed with Odin. TWRP has disappeared (the classic recovery menu came back). I think I have found my issue with the "no OS installed" bug : it could be because I deleted the essential API com.google.android.packageinstaller, what may have prevented the phone from booting and launching the OS and its apps .
I should have read this excellent post before...
*I ran antivirus analysis with virustotal and Bitdefender, which both declared the extracted files were safe : I didn't notice anything different by my phone compared to the original OS too, so...