Database Users

Jiayu S3 PIN Locked by Kinguser app

First of all, I may be posting this in the wrong section. But I desperately need your help on this.
I got a Jiayu S3, and couldn't not try to flash a custom rom on it, so I tried with "Pure AOSP V1 TF".
All went well, untill i found this app which was included with the rom, "Kinguser" (should be Superuser, i believe), which game me the option to toggle root.
At first and only time I opened this Kinguser app, option root was active. I did deactivate it, and reactivated immediately after.
As soon as i reactivated root, the privacy pin screen showed up.
I didn't set any PIN on my phone, so at first i thought it could be something like 1111 or 0000. Tried 5 times and it made me wait 30 seconds. Then tried another 3-4 times.
Here began the real mess: "forgot pin" (or psw) didn't show up, but at the time i didn't even know about that recovery option.
I didn't know what to do, so I just thought that a factory reset would certainly solve the problem, how couldn't it? Well, wiped everything, but PIN lock screen didn't go away.
So, wiping everything, I also deleted my gmail account from the phone, and I lost the possibility to lock phone and give it a new password (Android Device Manager). Too bad at the time I didn't know about this recovery option as well...
Now I'm out of ideas. I think I've tried every method I could find with a search of "Smartphone PIN locked". Tried with resets, plugins, deleting files with adb..
How do I unlock my phone?
little update: after a factory reset, for 2-3 seconds, it shows the default initial screen, but it doesn't last more that and i just can't do anything.
Now i managed to bring back the stock rom, but with that i lost the twrp recovery, and i can't find a way to make pc recognize the phone to reflash it.
It seems it's going worse instead of better...

I had just bought this Jiayu S3 and planned to bring it on holidays on wednesday, but i'm starting to think i won't be able to fix it before then

Did you have any resolution to this problem. I am currently sitting in the exact same boat. Did the factory reset, pass code screen still there, I didn't set a pass code. Basically hands tied, can't update firmware, guessing i'll have to get a new phone, but hoping maybe you found a miracle cure! ha! - Thanks for any guidance. - Arden (Seattle, WA)

Just flash another rom (stock/original) and start over.

How have you done that?
Can you help please?
I tried factory reset (volume plus+ power button), hard reset (volume- plus power button), update, and nothing works; I also went to two different specialized stores and they failed to find a way to reinstall the original Android version or a recent one.
Comparing the files with the factory version installed in the phone, the phone report identified three changes:
- a new file: /system/priv-app/7mK0T6e8Z5.apk
- the lost of a file: /system/app/com.android.fallen.apk
- and a modified file: /system/bin/debuggerd

AzulFogo said:
How have you done that?
Can you help please?
Click to expand...
Click to collapse
To flash firmware you can use SP Flash Tool on a windows or linux computer (not sure about macosx). You have to decide which firmware you want (which one do you have now?). The 'official' firmwares can be found on needrom. SP Flash Tool can be found there as well. There are 2 popular LP firmwares built by Jiayu resellers in Europe (Xtreme from Spain and Jiayu.de from Germany). Guides on how to flash are often present at the place where you find the firmware.

Dior DNA said:
To flash firmware you can use SP Flash Tool on a windows or linux computer (not sure about macosx). You have to decide which firmware you want (which one do you have now?). The 'official' firmwares can be found on needrom. SP Flash Tool can be found there as well. There are 2 popular LP firmwares built by Jiayu resellers in Europe (Xtreme from Spain and Jiayu.de from Germany). Guides on how to flash are often present at the place where you find the firmware.
Click to expand...
Click to collapse
Thank you!
I found "Xtreme from Spain":
needrom.com/download/rom-xtreme-rom-tf/
I found the "SP Flash Tool":
needrom.com/download/sp-flash-tool-v5-1424-00/
but it is for Linux... can you send me the link of the windows version?
And I could not found the "Jiayu.de from Germany": can you send the link?
Also, can you recommend some good manual for dummies?
Thanks again for your patient and help!

latest sp flash tools is 5.1532
search needrom with "5.1532" will leed you to the download page
no link allowed here, so ...
for beta 10 from jiyau.de, search google with "jiyau.de Lollipop 5.1.1 - Beta 10 (14.10.2015)".
it will leeds you to the rom.
Good hunting
tuto sp flash tool
https://youtu.be/ztI8sc8MUNo

AzulFogo said:
Thank you!
I found "Xtreme from Spain":
needrom.com/download/rom-xtreme-rom-tf/
I found the "SP Flash Tool":
needrom.com/download/sp-flash-tool-v5-1424-00/
but it is for Linux... can you send me the link of the windows version?
And I could not found the "Jiayu.de from Germany": can you send the link?
Also, can you recommend some good manual for dummies?
Thanks again for your patient and help!
Click to expand...
Click to collapse
see jaunedoeuf's answers
I would like to add: if you come from KK and go to LP, you must use firmware upgrade to update/adjust internal SD partition layout. Good Luck! if you succeed, and are happy with firmware, consider voting @ http://forum.xda-developers.com/android/general/firmware-jiayu-s3-t3212184 (almost 100 votes)

First, thank you for your great help!
With your suggestions, I managed to install Lolipop in my Jiayu S3S (upgraded from Kit Kat) - Xtreme ROM TF (JiayuS3-5.1Extreme1.1SP.zip).
However the problem remain... the phone still is asking for a PIN (that I never had put there, in first place)...
What should I do now?

you could try factory reset and are you sure its the phone asking for pin and not the sim card

G928F bought with frp,no imei after frp reset. Help

hi, short sad story:
Bought s6 edge+ 64gb ,after reset frp(with box), no imei, after what tried to flash many times with odin with no luck.
long story:
s6 edge plus 64gb G928F from nordic region. phone have been fully working, until my friend forgot pass.
So i bought it,do factory reset, when try many ways to to bypass FRP with no luck(earlier friends email unavaible). bring to my other friend and he disable it with box (dont know yet what type of box). and when no imei, unknow baseband and etc. spend 2 days of reading and trying to flash many roms with no luck.
Maybe someone can help me? or explain something? please help guys. over 5 years reading xda and always solved problems but not this time sadly.
edit: box was z3x, and have been done "Reset FRP in flash mode"
one more question, the box makes itself any backup on computer of efs or imei?

Please help guys, any suggestions? still searchin with no luck. How you think can i make it without box?

guys, whats the reason what i couldn get any help from you? maybe silly queston? or too young member? im member sinc 2010. if any one knows the solution i can donate via paypal. i need to repair it, to known the issue for next time. im reading to little? sorry but i tried everything what i had found, anything helps. maybe i need box for solution?

Kestasp said:
guys, whats the reason what i couldn get any help from you? maybe silly queston? or too young member? im member sinc 2010. if any one knows the solution i can donate via paypal. i need to repair it, to known the issue for next time. im reading to little? sorry but i tried everything what i had found, anything helps. maybe i need box for solution?
Click to expand...
Click to collapse
Please One of main forum rule is dont bump threads. I know youre in a rush because u wanna know whats going on on your phone but keep this in mind.
My suggestion. Get Samsung Kies, hook up your Phone in Downloading mode and do a total restore. If this will not help you can also try samsung firmware downloader and flash everything custom to stock via Odin. Try first method if this will not help, pm me. If the hole thing will not work i think your EFS partition is bad or corrupted maybe.

I had a similar problem, the only way I managed to fix it was by using Samsung smart switch. Here's how:
I am not responsible if this ends up destroying you phone
1- download Samsung smart switch to your pc http://www.samsung.com/us/smart-switch/assets/downloads/Smart_Switch-PC_setup.exe
2- Put your phone into download mode ( Turn off your phone, press the volume down + home + power button together and then press the volume up)
3- connect your phone to your pc via USB cable
4- open Samsung smart switch
5- on the top right there is a option button click on it
6- now click on emergency recovery
7- now click on device initialization tab
8- now enter your model name. For example: SM-G928C
9- now enter your serial number. You can find this in your box.
10- after that agree to everything and it will start downloading your original rom. This will take a while.
After that hopefully you phone will boot up.

allready tried everything you writte. didnt help. but thank you guys for helping

thanks for help grsjohn, i havent fix efs yet. because i dont have so much time. just reading a little a day about it. i havent any efs backup or something.
can you tell me little more about efs? can i flash efs or recovery it without box? if its hardware, how you fix baseband? i tried only apps what need rooted device to solve this problem(with no luck). nothing else yet
thanks guys for help to solve the problem
grsjohn said:
Hello, I had many phones from clients with your issue, it's a hardware issue, baseband got damaged, if you flash different firmware versions and fix efs an result is still baseband unknown for sure is hardware issue. Probably guy from who you bought that phone knew about this problem, baseband cannot get damaged after frp reset, I do this kind of operations often and never had problems
Click to expand...
Click to collapse

grsjohn, so i realised what it canot be fixed by software metods. so now im going to hardware, is it possible to fix the imei baseband module? or i need to buy all logic board? how u solving the problem like this? buying new logic board is expensive, and also my model is 64 gb thank you for help
grsjohn said:
Hello, I had many phones from clients with your issue, it's a hardware issue, baseband got damaged, if you flash different firmware versions and fix efs an result is still baseband unknown for sure is hardware issue. Probably guy from who you bought that phone knew about this problem, baseband cannot get damaged after frp reset, I do this kind of operations often and never had problems
Click to expand...
Click to collapse

(Soft?)-Bricked My S7 with a Flashfire Update, Need Help to Fix It?

So I've been rooting me phone for a while and have managed to never f*** up, till now, and I sincerely hope you guys can help me.
After rooting my S7 a while back, I just recently noticed SuperUser telling me that I didn't have root anymore, so I decided to follow these instructions to re-root my phone:
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I successfully followed all the steps to get root, but when I opened Flashfire it told me I could install a new update while maintaining root, so since my android is at 6.0.1, I did that and it bricked my phone.
On boot it says "Startup Failed - Use the Verizon Software Repair Assistant . . . " and on top it also says "Custom binary blocked by SECURE BOOT." I have tried going into recovery mode and deleting the system cache, but that doesn't do it. So is there any way to get the phone to properly boot while not deleting my data? I was rooting my phone precisely so I could use Titanium Backup again, so I don't have any backups stored anywhere. I have heard that flashing a recovery image with Odin can work, but would that delete my files? Someone please lend me your expertise.
My phone is a Verizon S7.

Fixed
I am surprised that no one responded to me, but what's important is that, miraculously, I managed to un-brick the phone myself without losing any data! What I did was, as my last hope (since Odin wasn't able to flash the stock image, a la the traditional soft-brick fix), decide to follow the on-screen instructions my phone was giving me and to download and run something called the "Verizon Software Repair Assistant," which can be found in the top google results after searching for the quoted name (xda doesn't let me post the link).
After putting my phone into download mode, I plugged it in, ran the software and let it work overnight. Checking on it in the morning, I found my phone, not only completely functional and working, but updated to Android 7.0 (it was 6.0.1 previously before the failed Flashfire OTA update) and still holding all of my data intact.
So, the interesting thing that I learned is that flashing to stock via Odin to fix a soft-bricked phone should not be the default resolution for potentially most people, as the carrier's default (in my case, Verizon's) repair utility managed to completely fix my phone without any side effects or data loss.
Is there anyone who could chime in on why the Repair Utility did not wipe my phone's memory, even though it warned it would?
**Note**
Verizon links to the Windows version of the repair assistant on their site, but to get the Mac version (which I used), the only way you can get it is by changing the end of the url they mention within the thread from "Win" to "Mac."

Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here

*Detection* said:
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
Click to expand...
Click to collapse
I guess I am not acquainted with this forum enough then, thanks!

Most likely the cause of the fault would be updating via FlashFire and keeping root. When the update was flashed, it most likely flashed the stock kernel and patched it for root, which is not a compatible root for our devices. Flashing the root kernel with Odin probably would have made the phone boot normally.

(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

I think i screwed myself (Galaxy S8 Root)

Hey i couldnt find anything else so i hope this isnt a duplicate,
im somewhat of a noob when it comes to rooting but i know a little bit
Today i rooted my Galaxy s8 , everything whet smooth and without a problem,
but then for some reason i deactivated the OEM unlock and rebooted my phone.
Obviously that locked me out of my phone, after trying to flash my phone with the stock firmware that i downloded through samfirm
i got the error sw rev check fail bootloader device 5 binary 4 and i couldnt get that to work.
My next step was to try the Samsung smart switch emergency recovery, which failed.
I got the error that my device was not supported.
After that my S8 also stared showing me a blueish screen with the message : "An error has occurred while updating the device software....",
i can still access downlod mode tho
At this point i really dont know what to do and i should really be in bed because its 2 in the morning .
I really hope someone can help me out here, thanks in advance and a good night for now.

Hirnvitamin said:
Hey i couldnt find anything else so i hope this isnt a duplicate,
im somewhat of a noob when it comes to rooting but i know a little bit
Today i rooted my Galaxy s8 , everything whet smooth and without a problem,
but then for some reason i deactivated the OEM unlock and rebooted my phone.
Obviously that locked me out of my phone, after trying to flash my phone with the stock firmware that i downloded through samfirm
i got the error sw rev check fail bootloader device 5 binary 4 and i couldnt get that to work.
My next step was to try the Samsung smart switch emergency recovery, which failed.
I got the error that my device was not supported.
After that my S8 also stared showing me a blueish screen with the message : "An error has occurred while updating the device software....",
i can still access downlod mode tho
At this point i really dont know what to do and i should really be in bed because its 2 in the morning .
I really hope someone can help me out here, thanks in advance and a good night for now.
Click to expand...
Click to collapse
Device 5 binary 4 means you are flashing lower version of firmware than what is on your phone. Samsung will let you downgrade ( bootloader ) versions numbers.
You will need to flash a bootloader 5 or higher to fix.
Note: Don't relock oem in developer option.

spawnlives said:
Device 5 binary 4 means you are flashing lower version of firmware than what is on your phone. Samsung will let you downgrade ( bootloader ) versions numbers.
You will need to flash a bootloader 5 or higher to fix.
Note: Don't relock oem in developer option.
Click to expand...
Click to collapse
Thanks for your reply!
That's what I found out too but I couldn't find a "higher" bootloader, I would have thought that if I download it through SamFirm it should have the proper BL
Do you have any recommendations on where to download the proper bootloader?
Yea that was a big f**k up haha
I just tried to get Poke Go to run but it wouldn't let me login because it detected that the Device was rooted I guess and after changing my device fingerprint and adding PokeGo to MagiskHide and still not being able to login I followed some FAQ blindly Wich recommended to turn off OEM unlock, and other things to hide the hardware site or the root, thinking about it again it should have been super obvious that this is a stupid idea, but you are always smarter afterwards right? Haha

spawnlives said:
Device 5 binary 4 means you are flashing lower version of firmware than what is on your phone. Samsung will let you downgrade ( bootloader ) versions numbers.
You will need to flash a bootloader 5 or higher to fix.
Note: Don't relock oem in developer option.
Click to expand...
Click to collapse
Wow I feel stupid, I'm flashing the stock through Odin right now as I type this, I've downloaded 2 firmwares first one was a random one from online second one was the SamFirm , after realizing the first didnt work I must have deleted the samfirm variant by accident, I redownloaded it and now it's working , but thanks for replying!