Related
Hi,
Okay, I hope this method can help you, so you don’t have to go through the tedious process I went through to fix this fpr lock problem, I personally tried a lot of methods described in forums and finally was able to fix this problem, so I hope this works for you too and you don’t have to spend a lot of time looking for a solution to this problem.
I used this method on my galaxy a5 2016, but I think it will work on other Samsung phones as well if you download the right stock rom for it.
Warning: if you are a newbie, please read through this entire post once before attempting to try it out. It’ll only take a few minutes but at least you’ll know what you’re doing.
since i'm a new user i'm not allowed to post outside links so i'll put spaces between my links to be able to post them.
So I had the same problem as a lot of other guys, I had rooted my Galaxy A5 Sm-a510-fd through CF-Auto-Root, Everything was working fine, But Since I didn't know about OEM Unlocking & FRP Lock (Factory Reset Protection), I Logged Into my google account in my phone, and after restarting my phone after installing an app, my phone showed a red small text at the top left corner of my screen saying "custom binary blocked by fpr lock", now keep in mind I had enabled usb debugging and oem unlocking before but since I logged into my google account, apparently google had disabled the oem unlocking, hence this message.
Now I tried a few methods like a method where someone had said to go into download mode (Hold Volume down + Home + Power) and then pressing the volume down (cancel) instead of volume up (continue) and after the restart the phone for some reason wouldn't show this message again (weird), some had tried this in that forum with success but it didn’t work for me, so first try this see if it works for you, then I tried to flash a new stock rom but I got the same frp lock message in download mode as well, then I tried a few other method which didn’t work and I don’t even remember them (I’m a newbee, and I was confused by all the articles I had read and all the method I had tried so I don’t remember a lot of them, and a few of them may have worked but needed to remove the battery but in galaxy a5 battery isn’t removable), but the method which finally worked for me was this (It was posted in gsmhosting . com by zishhaider user):
1. Download (A510FXXU1AOL1 02.12.2015) from samsung-updates . com/device/?id=SM-A510F or from sammobile . com/firmwares website.
2. Remove .md5 at the end of stock rom you downloaded, extract the .tar file with 7zip to a folder, delete cm.bin and sboot.bin from this folder, open 7zip file manager from you installed program list in windows, navigate to the folder, choose all remaining files, click add, choose tar as archive format and and click ok to compress the files again into a tar format (a better method to re-pack these files into a tar ball is by using a software called unified android toolkit described at the end of this post).
3. Download and install the latest kies from Samsung (it will automatically install the latest usb drivers for your phone) and I recommend restarting your computer after installing kies.
4. Now go to download mode (Volume down + Home + Power >> Volume Up) , Download odin 3.10.7 or newer if available at the time of reading this post, right click on odin and run as administrator, now connect your phone to your computer with the usb cable preferably coming with your own phone, now if you have installed the drivers (from kies software) and if the cable is working and usb debugging is enabled, odin should detect your phone and show <ID:0/003> added in the message section (the number 3 isn't important, it depends on which usb port you use), now check the options tab to make sure only Auto Reboot and F. Reset Time are checked (by default these 2 are always checked, make sure Re-partition is unchecked). I recommend waiting a minute or two to make sure your phone and odin have recognized each other fully and usb drivers are fully installed.
5. Click on AP and browse to the location where you compressed the rom files and choose it, now to begin flashing this stock rom, just hit start.
6. When ODIN is done, you should see a box that will say reset or passed (depending on which version you have, you may see either or both.). At this point it is ok to remove your device.
ODIN has completed the flash, and by now, the device should be going through the reboot screen, if it works for you as it did for me you won't get the frp lock message again.
Any problems, try these few things: Update Drivers, and restart your PC; Different cables; Different USB ports.
Just a tip: If you are in download mode and you want to restart or turn off your phone for any reason and you have an unremovable battery like me, in download mode hold Volume down + Power for 10 to 20 seconds to restart your phone, now if you want to turn it off completely, after the restart hold Volume up + Home + Power to go to recovery and from there choose turn off.
-------------------------
After this process your phone should boot and the red little text saying “custom binary is locked by frp lock” should disappear. But since you flashed your phone after you removed cm.bin and sboot.bin your phone will be slow and you will aslo, still have to bypass the frp lock from google inside your phone, to do that I will give you a link to youtube from rootjunkey which explains it best how to bypass this frp lock inside the phone, or if you have the user and password of the google account you had previously logged in with to you phone, you can enter those and when asking to backup your previous apps choose "treat this phone as a new device" because you don’t want to install the apps just yet and you’ll have to flash your phone one more time with the complete stock (including cm.bin and sboot.bin). after entering your phone either by logging into your google account or bypassing the google acounot login screen, go to settings >> about >> software info and hit build number several times to enable developers options, then go to developers option and enable usb debugging and the damned oem unlock, and from now on before restarting or turning your phone off check to see the goddamned oem unlock box is on.
www . youtube . com/watch?v=JzywoFS_r9U
www . youtube . com/watch?v=DJ8_qbj1DPQ
Now after I did all these things I tried to flash the whole stock rom I had downloaded but I got the message “sw .rev binary check failed device 2 binary 1” and I think the reason I got this was beacase I had flashed many other recovery and roms before and I had screwed up my bootloader version and my phone didn’t recognize this rom as the right one for my phone, I downloaded a few more roms from my own country (Iran) and each time it either gave me this message or failed because it was stuck in flashing either hidden.img or sboot.bin or … . so what I did was a method I learned from someone in a forum (I don’t remember which forum), I’ll post a picture of that method and explain a little bit about the steps or modifications I made. And before using this method, download unified android toolkit, just google and download it, you’ll need it for this method.
link to the image:
s7.picofile . com/file/8250224492/Galaxy_S6_NAND_Write_Start_Fail_Fix.jpg
this software creates a folder in the root of your operating system drive (c Drive in my case) named Unified_Android_ToolKit, inside it you will find an input and an output folder, put the files you want to re-pack into tar files in the input folder, follow the instructions (99, 8, 1, 3) and your resulting files will be saved in output folder.
So the modifications I made to that method was:
The order I followed in flashing was as follows:
- AP: Boot/Recovery/System : these are the main system and recovery files and have the biggest size.
- CRC: Cashe/Hidden : This is some country code used for the region to flash the ROM against, XE is Europe, AU is Australia, and so on, this part can throw you off, its more then for tracking what region this is based of, in terms of localization and language support. And more importantly, for Kies to recognize the region and to determine if there's firmware update available. It is quite possible to have a CSC that can be limited to one country.
- CP: Modem
- BL: cm/sboot : Your bootloader
This is the order I followed and as you can see I chose all buttons and their corresponding files instead of choosing all of them with AP. Each one of these buttons re-writes the corresponding file into it’s previous partition in your phone.
Also I flashed boot.img first, restarted, flashed recovery.img, restarted, and so on, except for the cm.bin and sboot.bin which I repacked with unified android toolkit into one tar ball instead of 2 tar file, and flashed them together, to do this all you have to do is put these 2 together into the input folder and select 99, then 8, then 2, then yes.
finally I decided to try using Samsung smart switch (which I had tried but didn’t work before) to try to flash a stock rom once again to make sure everything is back to normal, but it still didn’t work and froze just like before, so I decided to use kies and it worked, even though smart switch is newer I believe kies is still better, so I recommend you use kies to update your firmware one more time using this Samsung tool, especially if the previous method still didn't fully work or if your baseband version or IMEI is unknown. To do that after enabling usb debugging, open kies, connect your phone to your computer, unlock your phone screen if it is locked and wait for kies to recognize your phone, if it said kies does not support your device or try smart switch just ignore it, it’s okay even if it doesn’t recognize your phone, just go to tools and choose firmware upgrade and initialization, now enter your model number (Upper-case), then serial number, both are on the box of your phone, sn is also behind your battery or at the back of your phone if your battery is unremovable, follow the instructions, at one point you’ll have to disconnect the cable, turn off your phone, go into download mode and conncet the cable again and then hit update to update the downloaded firmware. This time if everything goes right your phone may work even better and faster than before just like it did for me.
one last thing: I had screwd up my phone so badly that my baseband and IMEI was unknown and I couldn’t make any calls, and what’s worse I hadn’t backed up my efs folder, so I tried a few methods to solve this and finally decided to use kies, kies hadn’t worked before but this time it worked and restored everything to normal.
Now this time after i fixed my phone, I have backed up my efs folder, and my stock rom from clockworkmod recovery, and I have also set up a Microsoft/Samsung drive, google drive and dropbox account and installed some software to backup every contact, message, and app I have to the cloud in case sth like this happens again, I learned my lesson, I hope you do the same.
Developers, please correct any mistakes I may have made explaining this method, I am a newbie and these are what I learned in just 2 days of reading many forums and applying them to solve my own problem, so I may be wrong in some of these, so before people try this method out correct all the mistakes I may have made so people don’t brick their phones. Thank you
I hope this was helpful, thanks for reading, sign out.
quick question, when i try to flash the modified .tar rom a message appears saying: "custom binary(boot) blocked by frp lock"
but without i cant activate developer options and OEM unlock. i cant use my phone atm
edit: phone is a510f
After removing the 2 files from tar, I was able to flash OK.
But after flashing, my phone is stuck in bootloop - it shows Samsung Galaxy A5 and restarts, continuosly.
---------- Post added at 09:09 AM ---------- Previous post was at 09:08 AM ----------
After removing the 2 files from tar, I was able to flash OK.
But after flashing, my phone is stuck in bootloop - it shows Samsung Galaxy A5 and restarts, continuosly.
Thanks, this helped my friend he is a n00b
This does not work with 6.0.1
Just for anybody who has that version, dont waste your time downloading 5.1.1, it wont work if you already in 6.0.1
Why should oem unlocking automatically turned off
This actually applies to all Samsung phones...
But, use the right firmware and flash it using Odin.
Side note:
To activate Developer options, tap Build number 7 times on About phone settings. Then, open Developer options and activate OEM Unlock.
You should ready to go flashing everything. Happy flashing!
AlokAk said:
Why should oem unlocking automatically turned off
Click to expand...
Click to collapse
OEM Unlock is turned off by default for Factory Reset Protection (FRP) feature to work properly.
Sent from my ASUS_Z00AD using XDA Labs
Is there any way by which i turned on OEM UNLOCKING permanentaly..
I have also rooted my A5 2016 by cff auto root.it rooted But after restarting it shows custom binary blocked by Frp lock. I have submitted this phone to samsung care. They fix it.
Now my phone is okk .
But no root access. Now I am not dare to root it by cff auto root
Is there any other way to Root my Galaxy A5 2016 Marshmallow (6.0.1) that after rooting it works without any problemm, if anyone could help me please.
Thanks in Advance
Which country's firmware i download for my galaxy A5 2016 ( SM-A510FD ) INDIA region.
On Sammobile website there is no firmware for india region.
Please tellll
AlokAk said:
Which country's firmware i download for my galaxy A5 2016 ( SM-A510FD ) INDIA region.
On Sammobile website there is no firmware for india region.
Please tellll
Click to expand...
Click to collapse
You could try to find it on Updato.
Sent from my ASUS_Z00AD using XDA Labs
No firmware for India region infact it only shows four region in filter region section
samsung a5 2016 SM-A510FD firmware fail any [Q-call 9041634416 i help you better
orion7i7 said:
Hi,
Okay, I hope this method can help you.
Click to expand...
Click to collapse
tx You saved my phone life
It works also with other software not only old one
não da certo comigo
no meu galaxy a5 deu essa mensagem mas coloco no modo download mas ele não aparece no ODIN pois não reconhece o cel pelo pc e agora ???
Fwatech said:
no meu galaxy a5 deu essa mensagem mas coloco no modo download mas ele não aparece no ODIN pois não reconhece o cel pelo pc e agora ???
Click to expand...
Click to collapse
The same thing happened with my phone.
After this message "Custom recovery blocked by FRP lock", the boot does not go ahead and in the download mode is not recognized by the pc.
I can not solve this :crying:
danjercm said:
and in the download mode is not recognized by the pc.
Click to expand...
Click to collapse
1) Have you installed USB drivers?
2) Have you tried other cables?
3) Have you tried different OSes, Odin versions, etc...?
Sent from my Redmi 3 using XDA Labs
krasCGQ said:
1) Have you installed USB drivers?
2) Have you tried other cables?
3) Have you tried different OSes, Odin versions, etc...?
Sent from my Redmi 3 using XDA Labs
Click to expand...
Click to collapse
Hi
thanks for answering
1) Yes, I installed the most up-to-date version of the samsung driver (SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.63.0)
2) Yes, I tried 5 different original cables
3) I tried with 6 different versions of Odin, on windows 7, 8.1 and 10.
so I researched google, the only alternative is to do a procedure called JTAG, but still had hope of being able to solve without having to open the device
If anyone has a suggestion, I'll appreciate it.
Thanks
Many thanks
Me and my A5 want to thank you a lot. You saved his life I don't have to use my Wiko View :silly: anymore
Not simple is write combination firmware to the phone, then enable usb debugging and then just write firmware that not erase user data and cache and use free sw or adb command(this work not depend on software in the phone) to unlock the phone.
Simple software is here and the manual.
http://www.hardreset.info/FRP-Unlocker/
Thank you so much dude! I've searched the internet for 2 days and then this post came by so I decided to read and do it because I had nothing to lose and hell yeah it worked! THANKS!
Previously, I've talked about how I bricked my G920T by using an apk to try to root my phone.
Then I tried to do a factory reset with the stock recovery but it wouldn't even go into the stock recovery. So I flashed TWRP and wiped the whole phone including the system partition.
Then I tried to flash a stock 6.0.1 firmware to the phone but doing so did not improve the situation as my phone still won't boot. Even worse, when I power my phone, all I see is the blue LED indicator, no Samsung logo, nothing.
Then I tried to flash a custom ROM like XtreStoLite but that didn't fix anything either.
When I use TWRP or the stock recovery, the error "failed to mount /efs (invalid argument)" comes up on the log. I tried using the ADB method to fix it but my phone would not get recognized by ADB probably because USB debugging isn't on by default.
I cannot shut down the phone without having it charged to a power source then holding down PWR+DOWN VOLUME+HOME until the screen shuts off.
When I enter download mode, I don't see the warning screen, I enter the download mode directly.
It will warm you when you enter download. Or use TWRP and reboot into Download.Once in download flash the ROM using Odin. Get the latest one from SamFirm.
P.S. Next time root using CF Auto Root
yasteellutch said:
It will warm you when you enter download. Or use TWRP and reboot into Download.Once in download flash the ROM using Odin. Get the latest one from SamFirm.
P.S. Next time root using CF Auto Root
Click to expand...
Click to collapse
It doesn't warn me when I enter download mode, that's one of the problems.
I tried flashing the official ROM using ODIN, it still won't boot because of the efs error.
1) Download the latest SmartSwitch
2) Click on more -> Emergency software recovery and initialization
3) Go into Device initialization, enter your model name, search for it and proceed as advised by the assistant
That should fix everything, otherwise:
1) Download the latest official firmware for your model, the 4-File (or 3-File) Version
2) Use latest ODIN, check repartition in options
3) Select all the files and flash it
If EFS or DRK is corrupted, flashing roms, custom or not won`t help, it can be fixed via repair box maybe (Octoplus/Z3X)
Try to flash CF auto root for your model, if it still won`t boot, then find someone with a box to try to help you remotely or not.
But Smart Switch emergency initialization with phone sn would be the first thing I would try.
Orginator said:
1) Download the latest SmartSwitch
2) Click on more -> Emergency software recovery and initialization
3) Go into Device initialization, enter your model name, search for it and proceed as advised by the assistant
That should fix everything, otherwise:
1) Download the latest official firmware for your model, the 4-File (or 3-File) Version
2) Use latest ODIN, check repartition in options
3) Select all the files and flash it
Click to expand...
Click to collapse
Which mode should I be in when using SmartSwitch? No devices are shown when I have it plugged in during the bootup, and is so too in download mode but shows a not supported message.
brenner650 said:
If EFS or DRK is corrupted, flashing roms, custom or not won`t help, it can be fixed via repair box maybe (Octoplus/Z3X)
Try to flash CF auto root for your model, if it still won`t boot, then find someone with a box to try to help you remotely or not.
But Smart Switch emergency initialization with phone sn would be the first thing I would try.
Click to expand...
Click to collapse
How can someone with a box help me remotely?
zheyizhu said:
Which mode should I be in when using SmartSwitch? No devices are shown when I have it plugged in during the bootup, and is so too in download mode but shows a not supported message.
Click to expand...
Click to collapse
Download mode offcourse. Nevermind the not supported message.
Follow instructions from link below, I made it for such occasions:
http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
zheyizhu said:
How can someone with a box help me remotely?
Click to expand...
Click to collapse
Well if you know someone who have a box, it doesn`t have to be remotely.
If not, it is possible to fix it remotely, with help of usb hub (FlexiHub or similar), tunneling (TeamViewer or similar) and box software (you connect phone to your computer, the other guy connects box to his computer, both of you are connected through a gateway to a wonderfull thing called internet, and everybody is happy ) .
Same as on site, just with few more things in between the phone, and the box.
brenner650 said:
Download mode offcourse. Nevermind the not supported message.
Follow instructions from link below, I made it for such occasions:
http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
Well if you know someone who have a box, it doesn`t have to be remotely.
If not, it is possible to fix it remotely, with help of usb hub (FlexiHub or similar), tunneling (TeamViewer or similar) and box software (you connect phone to your computer, the other guy connects box to his computer, both of you are connected through a gateway to a wonderfull thing called internet, and everybody is happy ) .
Same as on site, just with few more things in between the phone, and the box.
Click to expand...
Click to collapse
The S/N sticker on the back of the phone is long gone, is there any other way I can find it besides from going into settings because I can't do that?
EDIT: I am able to borrow a friend's serial and got the firmware installed.
The Samsung boot logo is back now, however, the device still won't boot. The efs error is still there but the download mode warning sign came back.
EDIT #2: Okay, I flashed TWRP now and ADB is working once again. Can I utilize this to fix the efs error?
I rooted my my few weeks ago with snapdragon root, and yesterday I realized that some apps kept crashing, so I rebooted my phone, but it stucks at Tmobile logo. So I opened up smart switch on my pc, tries to restore my phone, but it said that : SM-G930T does not support initializing. It's confusing since I restore using smart switch before, but I downloaded stock firmware from xda forum, and flashed with odin. And it shows sw rev check fail device 4, binary 3. And it boots in to recovery mode everytime I forced to restart. btw, it says dm-verity verification failed. What can I do to fix this? Thanks for any suggesions.
i had the same problem with my s7 SM-G930T
JokerCat233 said:
I rooted my my few weeks ago with snapdragon root, and yesterday I realized that some apps kept crashing, so I rebooted my phone, but it stucks at Tmobile logo. So I opened up smart switch on my pc, tries to restore my phone, but it said that : SM-G930T does not support initializing. It's confusing since I restore using smart switch before, but I downloaded stock firmware from xda forum, and flashed with odin. And it shows sw rev check fail device 4, binary 3. And it boots in to recovery mode everytime I forced to restart. btw, it says dm-verity verification failed. What can I do to fix this? Thanks for any suggesions.
Click to expand...
Click to collapse
I had the exact same problem with my phone which is the same model as yours, and after almost 2 days of surfing in the internet like crazy and trying all the diferent programs I found the solution.
1. first go to this video youtube,com/watch?v=RSZiVxJyFb4 (I cant post links so I will substitute the dot in "DOT COM" by a comma)
2.Download the firmware and Samsung drivers in the link in the video which is pangu.in/samsung_firmware.html skip thru the pages until you find your model(this link will download the drivers and a notepad with the link to the actual firmware download page which is sammobile,com/firmwares/
3. type the model number in the search bar (SM-G930T) and select the first one in the list and download it(note: you will need to create an account in this page in order to download the firmware but its only put your email and choose a password so it shouldn't be a problem. extract the firmware after downloaded.
4.Download the version of odin that is linked in the video link: pangu.in/odin_tool.html . Scroll down a lil bit and download the one that says "ODIN 3.11 (GALAXY S7)"HAS TO BE THIS ONE other versions wont work. extract it.
5.After you have downloaded everything(make sure you installed the drivers if you haven't done before) proceed to run ODIN with your phone unplugged from your pc and turned off
6.Load the AP file from the extracted firmware file into the AP tab you will see in ODIN(do all this with your phone UNPLUGED from the PC.
7.Now put your phone(which should be off and disconnected from the PC) into download mode[hold vol down+home+pwr button
then you will be aske to press button up to continue, do so(you probably know how to do this but I said in case other people don't)
8.connect your phone onto your pc and you should see your device show up in odin, now click start and you should be good to go
I hope it works for you since I know how frustrating it is to have such and expensive phone bricked.
juanernestous said:
I had the exact same problem with my phone which is the same model as yours, and after almost 2 days of surfing in the internet like crazy and trying all the diferent programs I found the solution.
1. first go to this video youtube,com/watch?v=RSZiVxJyFb4 (I cant post links so I will substitute the dot in "DOT COM" by a comma)
2.Download the firmware and Samsung drivers in the link in the video which is pangu.in/samsung_firmware.html skip thru the pages until you find your model(this link will download the drivers and a notepad with the link to the actual firmware download page which is sammobile,com/firmwares/
3. type the model number in the search bar (SM-G930T) and select the first one in the list and download it(note: you will need to create an account in this page in order to download the firmware but its only put your email and choose a password so it shouldn't be a problem. extract the firmware after downloaded.
4.Download the version of odin that is linked in the video link: pangu.in/odin_tool.html . Scroll down a lil bit and download the one that says "ODIN 3.11 (GALAXY S7)"HAS TO BE THIS ONE other versions wont work. extract it.
5.After you have downloaded everything(make sure you installed the drivers if you haven't done before) proceed to run ODIN with your phone unplugged from your pc and turned off
6.Load the AP file from the extracted firmware file into the AP tab you will see in ODIN(do all this with your phone UNPLUGED from the PC.
7.Now put your phone(which should be off and disconnected from the PC) into download mode[hold vol down+home+pwr button
then you will be aske to press button up to continue, do so(you probably know how to do this but I said in case other people don't)
8.connect your phone onto your pc and you should see your device show up in odin, now click start and you should be good to go
I hope it works for you since I know how frustrating it is to have such and expensive phone bricked.
Click to expand...
Click to collapse
Thanks alot！ I fixed it somehow, I reflash the root ap file, and it works
I never EVER post in these chats/forums, but you, whoever you are, you are a life saver. Thank you, THANK you, THANK YOU so much. it worked like a charm on my t-mobile SM-G930T
Hello,
I wonder if someone would help me FRP unlock my phone. It is a T-mobile sm-J700t 2015. I have searched the forum but don't see a clear answer.
I have tried (from Youtube) the USB cable method, the camera method and flashing the 10/2016 stock firmware through ODIN. In Odin I get an error: "Complete(Write) operation failed". I cannot turn on USB debugging of course because I cannot get into the device. Haven't tried updating with Kies yet because I'm nervous they'll patch any additional back doors I could try.
I am somewhat experienced at flashing and such and I think there must be a way to completely wipe the device and flash new firmware but I don't see instructions for that.
Thanks in advance!
Odin v3.10.7 & v3.12.3
Recovery: Haven't changed
USB installed from Samsung Kies (made sure Kies isn't running)
Firmware: J700TUVU2APJ3_J700TTMB2APJ3_TMB.tar.md5
Where I got firmware: https://qc3.androidfilehost.com/dl/...224401143/J700TUVU2APJ3_J700TTMB2APJ3_TMB.zip
Anyone? Still locked out of my phone. :crying:
Reboot normaly > go to settings > developer setting > oem unlock check yes
#gggirlgeek
Reboot normaly > go to settings > developer setting > oem unlock > check yes
I can't get into the phone at all. It is FRP (Google) locked because I did a factory reset from recovery. I can only manipulate it from PC or stock recovery. I have ADB, Odin and Samsung Kies on my PC if that helps.
What is the reason I am getting the ODIN error: "Complete(Write) operation failed"? Is it due to the FRP lock?
If not, would flashing the same stock firmware even help? (I have read that it's not possible to flash older firmware versions.)
Is the boot partition where the FRP status is stored? Is it possible to flash a new boot image to reset it?
I assume flashing a custom recovery would be useless? I doubt it could be done without USB debugging/ADB being enabled anyway.
One of the reason for that odin error is flashing an old build of stock ROM, your guess is right
Even if you are able to flash a stock FW via ODIN you'll still not be able to boot to your OS.
You have to login using the same google id that was previously logged in
OR you have to bypass the Google Account Login Screen.
There are varous method on youtube (i know you saw them) to bypass that screen (Side Sync method worked for me at the 10th attempt) inorder to install a 3rd party app either to
1. enable the developer option or enable OEM unlock ( to flash custom ROM or custom recovery)
OR
2. to overwrite the previous google account saved with your new account details. (THIS ONE HELPED ME)
WITH FRP LOCK ON, ODIN SHOULD NOT GIVE YOU ERROR ONLY IF YOU ARE FLASHING STOCK ROM. BUT STILL YOU WILL BE LOCKED WITH GOOGLE ACCOUNT LOGIN SCREEN BECAUSE OF FRP LOCK ON AND STOCK ROM
FRP info. is saved in Sboot. Flashing a new sboot works only for devices those were never upgraded to Android 6. For J7 2015 that was upgraded to android 6, flashing Sboot bricks the phone as said by a cell phone repair agent
Regards,
Sid
@saddam.khan999 : Thank you so much for replying. This is helpful. :highfive:
What did you do to get the sidesync to work? Mine wouldn't even connect to Sidesync on my PC.
Tried different USB ports, and even different PC's to get it to pop up on the phone. Tried old usb drivers too. Sidesync never senses it, and My Computer only show MTP folder that won't accept any file pasted to it.
You did this with Android 6.0.1 October 2016 update? They fix more holes every time.
Also, can you give me the link to the unlock tutorial you used with Sidesync? Just want to compare my method.
Hi,
gggirlgeek said:
This is helpful. :highfive:
Click to expand...
Click to collapse
How grateful I am to read the above line! Thanks :good:
gggirlgeek said:
You did this with Android 6.0.1 October 2016 update?
Click to expand...
Click to collapse
Yes on Android 6.0.1 but i dont remember the build date.
gggirlgeek said:
Also, can you give me the link to the unlock tutorial you used with Sidesync?
Click to expand...
Click to collapse
I tired two different tutorials of SideSync to crack it. Once I reach home in the next 10 hours from now. I'll search on youtube and give u the links. Right now I cannot remember it.
gggirlgeek said:
What did you do to get the sidesync to work? Mine wouldn't even connect to Sidesync on my PC.
Click to expand...
Click to collapse
I followed below step to fix popup issue
1. Uninstall all samsung apps like, Kies, SmartSwitch, SideSync everything.
2. Uninstall Samsung USB drivers
3. Install SmartSwicth (to get best drivers)
4. Now install SideSync (latest)
5. Open SideSync and check for OTA updates in your PC (update it if available)
I give up. I'm going to pay somebody. He can use one of those low-level programs to unlock it remotely. It only costs $15. Well worth it. Wish me luck!
gggirlgeek said:
I give up. I'm going to pay somebody. He can use one of those low-level programs to unlock it remotely. It only costs $15. Well worth it. Wish me luck!
Click to expand...
Click to collapse
@gsmDabbler this guy says he/she can solve FRP issue for 5$ on skype. I dont know if he's fake or real. Best of luck
1. At welcome screen push next.
2. Connect to wifi and push next.
3. Accept terms and conditions and push next
4. Attempt to sign in to your google account.
5. On loopback to sign in page, push back intel you see the welcome screen again.
6. Push emergency dialer.
7. Dial 112
8. Put in on speaker and when the disbatcher askes what is your emergency, quickly swipe where the speaker option is to your left and click on email.
9. Ask the disbatcher for the number for non-emergency. (EXTREAMLY IMPORTANT TO NOT SKIP THIS STEP)
10. Sign into your email.
11. Compose a new message.
12. On another device download drive.google.com/file/d/0B3quVdCaxqLfaG9VY2xjd3hhWmM/view?usp=drivesdk[/url]
13. Move this file to a microsd card, and put it into the j7.
14. Push attach
15. Locate your sdcard and select es file explorer.
16. Once attached to the email, click on the box inside the email that says es file explorer. If redirected to security setting check the box that says "Unknown Sources".
17. If then redirected to install screen for es file explorer, install app and skip the next step.
18. Push back intel your on the screen with your new composed email with attachment, and once again click on es file explorer, and then install...
19. After install, restart your phone.
20. On welcome screen, plug your j7 into a power source.
21. Toggle your power button off, and then back on.
22. Click on the far right last bubble.
23. On home screen of es file explorer, take the sdcard out of the j7 and put back into the extra device you downloaded es file explorer to, and download these 2 files.
drive.google.com/file/d/0B3quVdCaxqLfNVFvMHlOWnNnY2M/view?usp=drivesdk[/url]
&
drive.google.com/file/d/0B3quVdCaxqLfc0gyRTBTNGNXOTA/view?usp=drivesdk[/url]
24. Copy these files to your microsd card from earlier, and put back into your j7.
------------> continued to next post of mine!
gggirlgeek said:
Hello,
I wonder if someone would help me FRP unlock my phone. It is a T-mobile sm-J700t 2015. I have searched the forum but don't see a clear answer.
I have tried (from Youtube) the USB cable method, the camera method and flashing the 10/2016 stock firmware through ODIN. In Odin I get an error: "Complete(Write) operation failed". I cannot turn on USB debugging of course because I cannot get into the device. Haven't tried updating with Kies yet because I'm nervous they'll patch any additional back doors I could try.
I am somewhat experienced at flashing and such and I think there must be a way to completely wipe the device and flash new firmware but I don't see instructions for that.
Thanks in advance!
Odin v3.10.7 & v3.12.3
Recovery: Haven't changed
USB installed from Samsung Kies (made sure Kies isn't running)
Firmware: qc3.androidfilehost.com/dl/T2pLZbjUe0enTeLqQNLjsA/1482428974/385035244224401143/J700TUVU2APJ3_J700TTMB2APJ3_TMB.zip"]J700TUVU2APJ3_J700TTMB2APJ3_TMB[/URL].tar.md5
Where I got firmware: qc3.androidfilehost.com/dl/T2pLZbjUe0enTeLqQNLjsA/1482428974/385035244224401143/J700TUVU2APJ3_J700TTMB2APJ3_TMB.zip[/URL]
Click to expand...
Click to collapse
gggirlgeek said:
Hello,
I wonder if someone would help me FRP unlock my phone. It is a T-mobile sm-J700t 2015. I have searched the forum but don't see a clear answer.
I have tried (from Youtube) the USB cable method, the camera method and flashing the 10/2016 stock firmware through ODIN. In Odin I get an error: "Complete(Write) operation failed". I cannot turn on USB debugging of course because I cannot get into the device. Haven't tried updating with Kies yet because I'm nervous they'll patch any additional back doors I could try.
I am somewhat experienced at flashing and such and I think there must be a way to completely wipe the device and flash new firmware but I don't see instructions for that.
Thanks in advance!
Odin v3.10.7 & v3.12.3
Recovery: Haven't changed
USB installed from Samsung Kies (made sure Kies isn't running)
Firmware: J700TUVU2APJ3_J700TTMB2APJ3_TMB.tar.md5
Where I got firmware: https://qc3.androidfilehost.com/dl/...224401143/J700TUVU2APJ3_J700TTMB2APJ3_TMB.zip
Click to expand...
Click to collapse
Its simple. Just flash the latest firmware through odin and you'll be booted on stock.
Don't forget to turn on OEM unlock next time
?guys...no.. just Go to settings tap build 7 times go to developer options, turn on oem unlock, turn on usb debugging.ta dah.
mohitmallick17 said:
Its simple. Just flash the latest firmware through odin and you'll be booted on stock.
Don't forget to turn on OEM unlock next time
Click to expand...
Click to collapse
^^^^^^ Does flashing the latest firmware really work
?????????????????????????????????????????????
victhesunshine said:
^^^^^^ Does flashing the latest firmware really work
?????????????????????????????????????????????
Click to expand...
Click to collapse
Just take out your battery and reboot, turn oem unlock on and do whatever.its simple.
gggirlgeek said:
Hello,
I wonder if someone would help me FRP unlock my phone. It is a T-mobile sm-J700t 2015. I have searched the forum but don't see a clear answer.
I have tried (from Youtube) the USB cable method, the camera method and flashing the 10/2016 stock firmware through ODIN. In Odin I get an error: "Complete(Write) operation failed". I cannot turn on USB debugging of course because I cannot get into the device. Haven't tried updating with Kies yet because I'm nervous they'll patch any additional back doors I could try.
I am somewhat experienced at flashing and such and I think there must be a way to completely wipe the device and flash new firmware but I don't see instructions for that.
Thanks in advance!
Odin v3.10.7 & v3.12.3
Recovery: Haven't changed
USB installed from Samsung Kies (made sure Kies isn't running)
Firmware: J700TUVU2APJ3_J700TTMB2APJ3_TMB.tar.md5
Where I got firmware: https://qc3.androidfilehost.com/dl/...224401143/J700TUVU2APJ3_J700TTMB2APJ3_TMB.zip
Click to expand...
Click to collapse
Saw a same issue please check & follow this steps if it helps you some way.
Download the latest samfirm tool available on xda.
Open the samfirm tool. Enter model and region. Tick Auto and binary nature.
Click on Check update. It will show the latest firmware available on samsung server.
Then click on download. It will download four file full firmware. Then flash it through odin.
You need a strong internet connection to download the file.
fullofhell said:
Just take out your battery and reboot, turn oem unlock on and do whatever.its simple.
Click to expand...
Click to collapse
Not so simple.
During FRP Lock you are restricted to the google sign in page, locked out of everything else. Cannot even pull down the status bar. So no way to get to settings.
This can be done via ADB , but only if you had USB Debugging enabled prior.
I just obtained a used J7000T1 and FRP lock is activated , Even on the bootloader it displays "FRP Locked" . USB Debugging was never enabled .
If I find a way , I'll post. Any one have luck yet?
Once " FRP Locked " is off the bootloader, I'm sure we can just load a recovery / rom via Odin .... But that's where I am a stuck of course.
hightech316 said:
Not so simple.
During FRP Lock you are restricted to the google sign in page, locked out of everything else. Cannot even pull down the status bar. So no way to get to settings.
This can be done via ADB , but only if you had USB Debugging enabled prior.
I just obtained a used J7000T1 and FRP lock is activated , Even on the bootloader it displays "FRP Locked" . USB Debugging was never enabled .
If I find a way , I'll post. Any one have luck yet?
Once " FRP Locked " is off the bootloader, I'm sure we can just load a recovery / rom via Odin .... But that's where I am a stuck of course.
Click to expand...
Click to collapse
I had this happen last Feb when I got the phone and was trying to install twrp, and it says frp lock when I tried flashing the recovery tar via odin. I literally took out the battery rebooted back into the OS and turned on oem unlock and USB Debugging and it was fine then when I flashed twrp. I have never heard of this other issue u speak of. The phone has an unlocked bootloader to begin with. If u are stuck in a Google sign in page, I would download the Samsung z3 tool and make sure u have drivers installed and unlock the frp that way.it does have an option for frp lock
fullofhell said:
I had this happen last Feb when I got the phone and was trying to install twrp, and it says frp lock when I tried flashing the recovery tar via odin. I literally took out the battery rebooted back into the OS and turned on oem unlock and USB Debugging and it was fine then when I flashed twrp. I have never heard of this other issue u speak of. The phone has an unlocked bootloader to begin with. If u are stuck in a Google sign in page, I would download the Samsung z3 tool and make sure u have drivers installed and unlock the frp that way.it does have an option for frp lock
Click to expand...
Click to collapse
Thanks.
Drivers are installed.
Just cannot move from the google sign in.
There is a guide that shows how to use a USB drive with a shortcut apk on it , hooked up via OTG and is able to open settings. Although that did not work for me as well...
Maybe N version is different than MM ?
Almost the same problem here.....but in my j700f, I can't boot to recovery at all...can't flash stock firmware also due frp locked
[originally posted here on reddit, but due to the low activity around this device i'm posting it here too]
Hi All,
I have some experience installing TWRP via Odin and LineageOS via TWRP on 2 Galaxy S3s. Recently i have tried installing them on my S2 plus so i can have a backup phone. I know there are newer phones, i just want this for the challenge and to give it to a special someone...
basically i aim to install Lineage 14.1 and preferably (but not necessarily) with TWRP too.
Any suggestions on how to proceed ?
some info:
Samsung model:GT-i9105p
Android version: 4.1.2
Computer OS: Windows 10. the same ports and cables that i always use. in fact i just used them again for my s3.
with Heimdall the problem is:
when running zadiag.exe, i follow these instructions but list all devices does not give me any of these device names even after i uninstall all samsung USB drivers and Kies.
Run zadiag.exefrom the Drivers folder of the Heimdall suite.
Choose Options » List all devices from the menu.
Select Samsung USB Composite Device or MSM8x60 or Gadget Serial or Device Name from the drop down menu. (If nothing relevant appears, try uninstalling any Samsung related Windows software, like Samsung Windows drivers and/or Kies)
Click to expand...
Click to collapse
.
with Odin The problem is:
i fail after flashing TWRP successfully. each time the boot after the successful installation gives me the Samsung splash screen for quite some time and then the normal stock android comes up.
I successfully flashed twrp-2.8.7.0-s2vep.img.tar and twrp-2.8.7.0-s2ve.img.tar (not sure what the difference is) many times.
i tried both with both Odin 3.12.3 and Odin 3.09 that i found on XDA threads that are specific to S2 Plus, and every combination was successful as far as Odin reports.
I tried manually pressing the combination to enter recovery mode when the phone restarts after the flash, and also to flash without an auto-restart and then do the above, with and without the removal of the battery
overall 10 successful flashing with all of them going to the stock eventually.
I also followed all instructions on https://www.xda-developers.com/how-to-install-twrp/ but running
adb reboot bootloader
only results in a normal boot of the stock android