[Q] Locked Out of Phone by PIN! + VPN Setting Errors - Galaxy S 5 Q&A, Help & Troubleshooting

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

Related

SM-G360V 5.1.1 (Core Prime - Verizon US) Setup Wizard Crash Loop

After rooting with the KingRoot apk apps would start crashing randomly (no message, just every running app would exit and throw me to my home screen), so I decided to factory reset. I grabbed Titanium Backup, grabbed the app backups I needed, then did the reset. Phone booted up, but now the setup wizard just crashes every run through and restarts itself, leaving my phone useless.
It may be important to know that after KingRoot, my boot screen had an unlocked lock with the text "custom" under it- I figure this means my bootloader is unlocked, but I could be wrong.
I've enabled USB Debugging through the recovery screen.
Setup Wizard (Without SIM):
Connect to Wifi network -> Next -> Crash
Skip connect to wifi -> Skip anyway -> Crash
Setup Wizard (With SIM):
Properly IDs my number and connects to 4G -> Next -> Sometimes crash
Skip Verizon Cloud -> Not Now -> Crash
Setup Verizon Cloud -> Finished Setting up -> Crash
Installing TWRP via h00ps://twrp.me/devices/samsunggalaxycoreprimequalcomm.html
Option 1 (TWRP) nogo, no previous TWRP installed
Option 2 (Odin) nogo, tried both through the website on Linux/FF and through Windows (VirtualBox). The website asks me for the PIT, then when it tries to retrieve it from the device it fails. The app on Windows doesn't ask me for it, but when trying to install it it pops up "secure check fail: recovery" on the phone's screen (the app does nothing).
Option 3 (dd) nogo, can't get an adb root shell
Rerooting through the KingRoot desktop app:
It looks like it succeeds (it's all in Chinese).
adb root gives "adbd cannot run as root in production builds"
adb shell su gives "[-] Connection to ui timed out"
Trying to remove or disable the Setup Wizard app:
ps | grep setup returns the following package names:
com.android.setupwizard (pm disable -> Unknown package)
com.google.android.setupwizard (pm disable -> Permission Denial: attempt to change component state from pid=11940, uid=2000, package uid=10014)
com.google.android.partnersetup (pm disable -> Permission Denial: attempt to change component state from pid=11958, uid=2000, package uid=10030)
com.sec.android.app.setupwizard (pm disable -> Permission Denial: attempt to change component state from pid=12180, uid=2000, package uid=1000)
kill <package> -> Operation not permitted)
pm uninstall <package> -> "Failure [DELETE_FAILED_INTERNAL_ERROR]"
pm path com.android.setupwizard -> nothing
pm path com.google.android.setupwizard -> /system/priv-app/SetupWizard/SetupWizard.apk
pm path com.google.android.partnersetup -> /system/priv-app/GooglePartnerSetup/GooglePartnerSetup.apk
pm path com.sec.android.app.setupwizard -> /system/app/SamsungSetupWizard/SamsungSetupWizard.apk
I had also sideloaded gapps-lp-20150314 (for 5.1.X) in hopes that it would fix it up.
Anything else I should try? Any stock images so I can do a complete, fresh, reinstall? I know someone here was working on getting stock everything uploaded- will that be my best bet?
Thanks!
EDIT: Additional information
Download mode returns the following strings:
ODIN MODE
PRODUCT NAME: SM-G360V
CURRENT BINARY: Samsung Offical
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T2, H1, R1, A3, P1
SECURE DOWNLOAD: ENABLE
When trying to flash TWRP with ODIN add line
SECURE CHECK FAIL: recovery
I think the twrp was not for your phone. All the cores have Qualcomm snapdragon processors and I do believe most of them are LTE. I know for a fact tmobiles is an lte. The problem is Verizon paid for the kernel so they could control our access. That's why we're the last one to get anything done. Basically, by flashing the recovery, you may have soft bricked your phone since it compiles with a different kernel. Yes, Verizon has a different kernel. If you check opensource.samsung.com, you'll notice our phone is not listed. Thats thanks to Verizon. I'm pretty sure that's illegal too but I'm not a lawyer. Until we get a stock rom or someone has an idea, I do believe your phone is KIA.
Ugh, thanks verizon. However, the soft brick immediately happened after the factory reset, not the install of twrp (it kicks out of that pretty quick). I know you're working on a stock rom in another thread, anything you need to speed up the process? I'm honestly about to just get a Nexus 5 from Amazon Prime, they're pretty cheap and it's getting rough not having mobile data.
With the new OTA having just rolled out, I'm going to pull it. You'll be able to use it to recover
https://mega.nz/#!0Q1nFQ7a!pHublKgmjElaZmePKUWxTB5rlgLytu921bFIJJbII_E
Link to the new OTA.
Flash using either recovery, if you still have access or fastboot.
And TWRP is official. I found the actual name from verizon, and it matches. Careful with the OTA, I'm now soft bricked.
jaywillsoul said:
Link to the new OTA.
Flash using either recovery, if you still have access or fastboot.
And TWRP is official. I found the actual name from verizon, and it matches. Careful with the OTA, I'm now soft bricked.
Click to expand...
Click to collapse
Awesome, you're a lifesaver. I'll do this once I get back from work- can't say I really want to deal with VirtualBox USB passthrough today or that sketchy looking java/web one.
I've still got access to everything (download, recovery, adb, no fastboot though). So the linked version of TWRP (coreprimelte or whatever) is specifically for this phone? Any reason I wasn't able to successfully flash it?
Last thing- and thanks so much- what does that zip actually contain, and if it is just the OTA files, then will I still avoid the soft brick you ran into?
Unfortunately, the OTA update changed nothing. Dunno if it was supposed to (I didn't see Setup Wizard files in there) but I'll trade a soft brick for a soft brick. There was some red debug info on screen when applying, but the phone quickly rebooted afterwards. If you need me to, I could probably adb in and check the version numbers to see if it applied and/or rerun the update and capture that debug info.
Maybe all I need is a stock copy of the Setup Wizards- I should be able to sideload them over the existing versions, right?
Maybe. I'll dig through the system and see if I can find the original.
It might be a part of gapps
That's what I was thinking too, and I've tried reapplying gapps-lp-20150314.zip. I think the Setup Wizard it's crashing on isn't the stock android one, but one of the samsung/verizon ones I listed in the first post.
Found it. Once my son goes down for his nap, I'll upload it for you.
https://mega.nz/#F!BE1TVbTL!d2G2P9S1jVyV-mr8UsfAGw
That's the entire folder in /system/app
It was worth a shot, but sideloading that apk failed. The stock you are working on should be the ultimate fix though.
I uploaded the official md5 from Samsung kies 3. It's in a new thread.
AWaterFountain said:
It was worth a shot, but sideloading that apk failed. The stock you are working on should be the ultimate fix though.
Click to expand...
Click to collapse
Did the ROM work for you?
Yep, I guess I only confirmed that with jay in PM. The stock ROM he uploaded worked fantastically, just threw it in Odin and I was good to go.
AWaterFountain said:
Yep, I guess I only confirmed that with jay in PM. The stock ROM he uploaded worked fantastically, just threw it in Odin and I was good to go.
Click to expand...
Click to collapse
Good to hear! What version of odin did you use and what settings in odin do you select to get the ROM to flash?
All stock, latest version. All I had to do was throw phone into DL, put the stock rom into ap/pda, and let odin do its thing.
Thanks!
jaywillsoul said:
I uploaded the official md5 from Samsung kies 3. It's in a new thread.
Click to expand...
Click to collapse
were do i find te tread you posyed it on?

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.

(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

Sm-T580 FRP lock and custom binary blocked by frp. Cant flash twrp recovery.

So im trying to install twrp recovery but when i try to flash it thru odin, i get a Custom Binary (RECOVERY) blocked by FRP lock. I cant factory reset because it also disabled by FRP. I cant verify the tablet because i dont know the account information as the tablet was bought through craigslist. I have tried flashing a stock firmware version and that installed fine, but i still couldnt get past the verify screen. So thats when i decided to try and flash twrp but came into the binary error. I have been trying for the past two days to find a way around the verify identity and the frp lock. I cant enable oem unlock. I have tried rootjunky method but OTG flash wont pull up the file manager when plugged into the tablet. I cant use adb because i cant enable the developer settings because you guessed it i cant get past verify identity screen. Any help would be greatly appreciated.
Sounds like you need to find the Combination Firmware.
softasspoptart said:
So im trying to install twrp recovery but when i try to flash it thru odin, i get a Custom Binary (RECOVERY) blocked by FRP lock. I cant factory reset because it also disabled by FRP. I cant verify the tablet because i dont know the account information as the tablet was bought through craigslist. I have tried flashing a stock firmware version and that installed fine, but i still couldnt get past the verify screen. So thats when i decided to try and flash twrp but came into the binary error. I have been trying for the past two days to find a way around the verify identity and the frp lock. I cant enable oem unlock. I have tried rootjunky method but OTG flash wont pull up the file manager when plugged into the tablet. I cant use adb because i cant enable the developer settings because you guessed it i cant get past verify identity screen. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Read the post by Beut in this thread and then watch the video.
4929york said:
Read the post by Beut in this thread and then watch the video.
Click to expand...
Click to collapse
I already tried that method but didn't work. It's on android 7.0. I tried downgrading to sm-t580.. XAR firmware 6.1 and it worked but when it boots it goes straight to a black screen asking for a password. I tried the frp call method as well but it doesnt have wifi calling.
softasspoptart said:
I already tried that method but didn't work. It's on android 7.0. I tried downgrading to sm-t580.. XAR firmware 6.1 and it worked but when it boots it goes straight to a black screen asking for a password. I tried the frp call method as well but it doesnt have wifi calling.
Click to expand...
Click to collapse
It only works with certain versions of 6. The one ending is PL4 is the one you want. The trick is in adding the fake wifi network instead of connecting to your home network. Pay close attention to the beginning of the video.
lewmur said:
It only works with certain versions of 6. The one ending is PL4 is the one you want. The trick is in adding the fake wifi network instead of connecting to your home network. Pay close attention to the beginning of the video.
Click to expand...
Click to collapse
Okay thank you. I will try that again when I get home. And this works on version 7.0? The device is currently on 7.0 but when I tried the pl4 md5 it flashes it but when I boot up the device it just goes to a black screen and asks for a password. It doesn't start at the setup wizard
softasspoptart said:
Okay thank you. I will try that again when I get home. And this works on version 7.0? The device is currently on 7.0 but when I tried the pl4 md5 it flashes it but when I boot up the device it just goes to a black screen and asks for a password. It doesn't start at the setup wizard
Click to expand...
Click to collapse
You have to use Odin to install PL4. You can't flash it via TWRP. Also, make sure you wipe everything first.
lewmur said:
You have to use Odin to install PL4. You can't flash it via TWRP.
Click to expand...
Click to collapse
I know. I can't install twrp like I said. I've been using Odin to flash everything. But when I flashed the pl4 file and tablet goes to reboot. It doesn't load the setup wizard. Doesn't show the welcome screen and pick a language. It goes straight to a black screen and asks for a password. Doesn't ask for an email or anything.
softasspoptart said:
I know. I can't install twrp like I said. I've been using Odin to flash everything. But when I flashed the pl4 file and tablet goes to reboot. It doesn't load the setup wizard. Doesn't show the welcome screen and pick a language. It goes straight to a black screen and asks for a password. Doesn't ask for an email or anything.
Click to expand...
Click to collapse
Never heard of that. Can you boot from there into recovery and wipe again?
lewmur said:
Never heard of that. Can you boot from there into recovery and wipe again?
Click to expand...
Click to collapse
Yea but when I try to factory wipe it says mdm doesn't allow factory reset and reboots and takes me back to that same black screen. I can only wipe cache partition. I will post a picture of the screen when I get home.
softasspoptart said:
Yea but when I try to factory wipe it says mdm doesn't allow factory reset and reboots and takes me back to that same black screen. I can only wipe cache partition. I will post a picture of the screen when I get home.
Click to expand...
Click to collapse
I found this site. It is apparently an "MDM lock" and not FRP.
lewmur said:
I found this site. It is apparently an "MDM lock" and not FRP.
Click to expand...
Click to collapse
Tried this as well. I did it about 20 times before giving up. I might try it again and do it about 30 to 50 times. If I was just able to get to settings I'd be straight but I can't get to the settings so that's why I'm trying to reset it as a completely new device. Do you know if I could flash the 7 inch tab A firmware onto the smt580? Or flash the smt585 firmware onto the t580 and flash the BL AP and CSC?
softasspoptart said:
Tried this as well. I did it about 20 times before giving up. I might try it again and do it about 30 to 50 times. If I was just able to get to settings I'd be straight but I can't get to the settings so that's why I'm trying to reset it as a completely new device. Do you know if I could flash the 7 inch tab A firmware onto the smt580? Or flash the smt585 firmware onto the t580 and flash the BL AP and CSC?
Click to expand...
Click to collapse
From what I've read, Airwatch MDM lock can't be removed by flashing ANYTHING. It is third party anti-theft protection that has nothing to do with what ROM is installed. I know I ran into their stuff a few years ago with a used laptop I bought and only Airwatch was able to solve the problem after contacting their customer and verifying the laptop wasn't stolen.
4929york said:
From what I've read, Airwatch MDM lock can't be removed by flashing ANYTHING. It is third party anti-theft protection that has nothing to do with what ROM is installed. I know I ran into their stuff a few years ago with a used laptop I bought and only Airwatch was able to solve the problem after contacting their customer and verifying the laptop wasn't stolen.
Click to expand...
Click to collapse
Okay thanks. I'll get in contact with airwatch.
lewmur said:
I found this site. It is apparently an "MDM lock" and not FRP.
Click to expand...
Click to collapse
I did end up finding this. Seems the device is completely locked with no way to get around. When i flashed the device i may have deleted the admin privilages so there is no way of gettting around it as of now. I might end up paying someone to fix it or get around it or i wasted 180$ on a locked device. The guy i bought it from either blocked my number or deactivated his number as i cant get in contact with him. Pretty pissed. Thanks for all the help tho
I had the black screen password happen to me when I downgraded my SM-P580 from Android 7 to 6. Try clearing the cache. If that doesn't work, try reflashing, then turn it off and reboot to recovery and clear the cache.
BBowermaster said:
I had the black screen password happen to me when I downgraded my SM-P580 from Android 7 to 6. Try clearing the cache. If that doesn't work, try reflashing, then turn it off and reboot to recovery and clear the cache.
Click to expand...
Click to collapse
Okay I'll try that. Didn't try that yet. Will keep updated
lewmur said:
I found this site. It is apparently an "MDM lock" and not FRP.
Click to expand...
Click to collapse
Do you think if i changed the CSC to a different region on the tablet, and put a unlocked bootloader on it, would it might get rid of the frp lock? Do you happen to have a smt580? If so do you think there is anyother way of getting around this? say if i flashed like your firmware on to my tablet? Im desperate to get this thing unlocked as i would be out 180$ :crying:. Thanks for all your help so far. I really appreciate it man. Thanks to everyone who has helped so far.
Or what if i downgrade it to 6.1 and then downgrade it again to a even farther back version? Do you think this might work and gett me around the black screen? If so then i would be able to bypass the google verify account. Ima go ahead and try it unless its a risk of bricking the tablet completely.
I also read somewhere that if i flash the cp part on odin that it will erase all data. Think that might be worth a shot? But what do i need to insert in the cp slott? I know BL goes to BL and AP to AP and CSC home goes in CSC. So what goes in the cp slot?
EDIT: So instead of putting csc home in the csc slot i put the other csc file in its place. I checked the re partition box. When i did this i got a new message on the tablet in the top left of tthe download mode that says FRP is enabled, ignore PIT download. Any idea what this means?

Galaxy Tab A 10.1 2016 (blocked by Chinese firmware) - SM-T580

Hello everyone, I flashed the stock firmware (T580ZCU6CTA) to my SM-T580 , trying to "fix it"; all the memory was occupied by the system files. The flash went well, still when the tab rebooted the screen went crazy for a while, anyways after booting up the tab works way better than before, but its block, meaning that it wont let me install some apps, I also tried to flash many different stock firmware but I always get a message that the boot-loader is block (in Chinese language). I was able to flash the U6 combination files, but it did not fix it. Please I need some help.
greynao said:
Hello everyone, I flashed the stock firmware (T580ZCU6CTA) to my SM-T580 , trying to "fix it"; all the memory was occupied by the system files. The flash went well, still when the tab rebooted the screen went crazy for a while, anyways after booting up the tab works way better than before, but its block, meaning that it wont let me install some apps, I also tried to flash many different stock firmware but I always get a message that the boot-loader is block (in Chinese language). I was able to flash the U6 combination files, but it did not fix it. Please I need some help.
Click to expand...
Click to collapse
Did you enable OEM unlock on the Chinese firmware or the U6 combination firmware?
Edit: I forgot that the Chinese firmware had Crom Service...
JJcoder said:
Did you enable OEM unlock on the Chinese firmware or the U6 combination firmware?
Click to expand...
Click to collapse
Hi JJcoder. I actually did enable OEM unlock on the Chinese firmware and had no luck. While in the U6 combination firmware; for some reason the "OEM unlock" option is not available even after enabling the developer mode menu.
Hello! The problem is that in the Chinese version they install a thing called crom protection.
To deactivate it you have to install an apk on the tablet called "crom service" and do the steps that come on this website https://www.teamandroid.com/2018/06/27/unlock-bootloader-chinese-samsung -devices-crom-service /
It has worked for me, if you realize it, before using and entering bootloader mode you get "CROM SERVICE: ON"
then once done the steps you will get "CROM SERVICE: OFF"
when that comes out install twrp and from there install the rom you want. If you have problems reinstall the Chinese version with odin and do the same again. Sorry for my bad English!
Gnzlo said:
Hello! The problem is that in the Chinese version they install a thing called crom protection.
To deactivate it you have to install an apk on the tablet called "crom service" and do the steps that come on this website https://www.teamandroid.com/2018/06/27/unlock-bootloader-chinese-samsung -devices-crom-service /
It has worked for me, if you realize it, before using and entering bootloader mode you get "CROM SERVICE: ON"
then once done the steps you will get "CROM SERVICE: OFF"
when that comes out install twrp and from there install the rom you want. If you have problems reinstall the Chinese version with odin and do the same again. Sorry for my bad English!
Click to expand...
Click to collapse
Thank you so much for your help; everything went well. I had a little problem trying to get the tablet into recovery mode after installing the TWRP, but I found a solution (when the TWRP flash is complete and the tablet starts to reboot, press and hold volume up and home to get it to boot into recovery, this has to be done quickly in order to catch the beginning of the tablet rebooting or the stock recovery will overwrite on the TWRP). I had to mentioned just in case someone else runs by this problem.
Please reply with your pay pal so I can buy you a beer for your help. Thank you.
greynao said:
Thank you so much for your help; everything went well. I had a little problem trying to get the tablet into recovery mode after installing the TWRP, but I found a solution (when the TWRP flash is complete and the tablet starts to reboot, press and hold volume up and home to get it to boot into recovery, this has to be done quickly in order to catch the beginning of the tablet rebooting or the stock recovery will overwrite on the TWRP). I had to mentioned just in case someone else runs by this problem.
Please reply with your pay pal so I can buy you a beer for your help. Thank you.
Click to expand...
Click to collapse
hahaha don't worry!! I had the same problem and spent several hours researching because I couldn't install twrp or another rom, so you don't need a beer, I just need to know that it was useful and someone else didn't have to go through the same as me XD

Categories

Resources