my friend has a j200f.
first, the phone stuck on samsung logo and said "custom binary blocked by frp lock"
i tried to hard reset bu cannot do it.then i used odin and flashed stock rom.
now the phone stuck on download mode. can you help me please?
btw i tried to flash twrp and says "custom binary blocked by frp lock" again
you just have to flash the official firmware because the bootloader is locked you cant do anything about it because you happened to trip or modified the firmware in that state the phone wont boot unless you flash the official firmware
and make sure to flash the correct variant and latest firmware
Adding to @blood1995 said, After installing custom rom make sure you check OEM Unlock in Developer options(AFTER INSTALLING ROM).
itutu008 said:
my friend has a j200f.
first, the phone stuck on samsung logo and said "custom binary blocked by frp lock"
i tried to hard reset bu cannot do it.then i used odin and flashed stock rom.
now the phone stuck on download mode. can you help me please?
btw i tried to flash twrp and says "custom binary blocked by frp lock"
Click to expand...
Click to collapse
See, the FRP lock isn't required to be open. You can close it if you want by using this guide. Oh also remember, the phone battery should be more that 50%. Now here's the steps:
Step 1: This combo "Volume down-Power(not home)" and hold the combo at the same time for 7 seconds, the Odin screen will disappear.
Step 2: Open the phone by using that combo "Volume down-Power" (Hold it for 7 seconds and) it should boot into Android 5.1(or the os you were currently using before the rom installation thing)
Step 3: Get back into Odin mode by pressing "Volume Down-Home-Power" at the same time, and install your rom. The FRP lock should be closed
Related
Hello,
Here is what led to my issue:
I rooted my phone using this method: http://forum.xda-developers.com/showthread.php?p=38886073#post38886073
Downloaded clockwork rom manager.
Here comes the thing I don't remember. At least i know that the last thing i did was to click on 'backup current rom'
After this the phone reset itself and this message came up:
Secure booting error!
Cause: boot certification verify
Then i tried to reset using the power button, which led me to the 'battery full' screen - afterwards i was able to reboot. As stupid as I am I just tried the same thing again. And ever since i am stuck at the 'Secure booting error!' screen.
I am unable to enter download mode. I get to the 'Hard factory reset' screen, but if i accept doing so, it says 'Secure booting error!' again.
I also remember clicking on 'restart into recovery mode' at some point, but this is not the last thing i did.
I am really desperate. Please, help me!
Well i had the same issue today... It happened after i did two changes. One of them was to to try to relock from freegee and flash twrp again from freegee. In my case i was able to go in download mode and flash original kk rom with lg flash tool.
Unfortunatly, trying to boot in downloadmode, i still get the same error :/
Jubi-Wan said:
Unfortunatly, trying to boot in downloadmode, i still get the same error :/
Click to expand...
Click to collapse
How are you trying to boot into download mode? And what factory reset screen? It seems as though you did not unlock the bootloader using freegee, if you make any changes and relock the boot loader you will get that error. But it seems that it has not been unlocked. If you hold power and volume up what happens? Same thing when power and volume down, one of them is recovery (possibly factory reset you are seeing) and the other is download mode. I don't remember right now but you should read the whole softbrick thread and see if you are missing something. You may need to use LGPNST to go back to stock, you can also use that program to flash a new recovery so read carefully and follow all steps.
When this happened to me I was able to flash an unlocked bootloader and it allowed me to use my phone again as it was before doing something stupid (for me it was an attempt to re lock the bootloader).
well, i managed to get into download mode. Obviously i used the wrong method to get into download mode...
I used this method and everything worked fine, so far. : http://forum.xda-developers.com/showthread.php?t=2249500
My phone doesn't boot now. Fast Boot doesnt work aswell.
All that happens is a white battery showing on the screen and when i try to fastboot all that happens is that the LED is blinking or glowing red after some while.
Jubi-Wan said:
well, i managed to get into download mode. Obviously i used the wrong method to get into download mode...
I used this method and everything worked fine, so far. : http://forum.xda-developers.com/showthread.php?t=2249500
My phone doesn't boot now. Fast Boot doesnt work aswell.
All that happens is a white battery showing on the screen and when i try to fastboot all that happens is that the LED is blinking or glowing red after some while.
Click to expand...
Click to collapse
What do you mean when you try to fastboot? Fastboot is basically the bootloader and allows you to select recovery or download mode. What you should have done after following that thread is go to recovery and wipe everything and flash a new ROM.
If you are saying that the bootloader is not coming up and allowing you into recovery then I believe something was missed.
After trying out some varioants of this it worked: http://forum.xda-developers.com/showthread.php?p=40274560&highlight=red+led#post40274560
I wiped the phone, but since I had to leave over the weekend i just turned it off and went away.
Now that I am back, nothing works now :/ The Phone doesnt react to anything, not even donwload-mode.
Is the battery too low maybe? It's on the wall now for a few hours, but it still doesn't react. It's not warm either.
edit:
when i charge the phone, i will get a 'watchdog bark' after some time allowing me to get into recovery. accesing downloadmode from there doesn't do anything. strangely, the recovery isnt trwp although it should be because teenybin comes with it. it's 'bbs.gaodi.net' which doesn't have a sideload feature. what do i do now?
edit2:
after 10000 tries i got into download mode. i don't want to **** up now so i won't do anything until i know exactly what to do.
any advice?
edit3:
got it working by flashing another teenybin which included trwp - then i installed miui via sideload. i don't have signal though, but i will open another thread for this since this is another issue.
i rebooted a my phone after installing and setting up a new rom. for the first time in a million flashes with this thing, frp lock was on and now i cant get into recovery or anything but download mode. i just odined the cof8 firmware, and the phone just bootloops on s6 edge screen. it no longer shows custom binary locked, or whatever it said in red letters at the top of the sceen. but when i go back into download mode, it still says frp lock is on. according to odin, the firmware flash was successful. I cant get back into the phone.
any help, please!!
I went to the t-mobile store and they fixed it with a reset. She didn't have to plug it in at all. She pressed and held a few buttons down till the android robot popped up and it reset the phone back to doh6 firmware I believe it is. Only bummer was it wiped my internal storage
You have to boot into recovery and do a factory reset after flashing with odin. (Sounds like what they did at the store)
DJxL3G1T said:
You have to boot into recovery and do a factory reset after flashing with odin. (Sounds like what they did at the store)
Click to expand...
Click to collapse
Yeah I didn't think about booting into the factory recovery.
Sent from my SM-A710F using Tapatalk
srimay said:
Yeah I didn't think about booting into the factory recovery.
Sent from my SM-A710F using Tapatalk
Click to expand...
Click to collapse
You can fix your problem by using Smart Switch Emergency Recovery. Get your Serial Number from the Download mode.
I can remove FRP Lock on almost all samsung devices.
Text me 7609156486 and ill remove the lock for you
Hello everyone,
My phone (S4 mini GT-I9195) decided all of a sudden to stop working. I couldn't boot it, charge it, nothing but a black screen. After some research on the world wide web, I came to the conclusion that it might be "bricked", as the cool kids call it. I came upon a guide on this website that seemed promising: https://forum.xda-developers.com/showthread.php?t=2600869
I followed the instructions, found a debrick.img corresponding to my GT-I9195, put it on a sd card and managed to boot the phone.
Next was entering Download mode and flash with a stock firmware via Odin (v3.09). I used a 4.4.2 firmware I found on Sammobile (I9195XXUCNK4_I9195QXZCOA1_XEF) corresponding to my region and phone.
Everything went fine with Odin, I waited until it said "PASS!" and rebooted the phone.
The next step was to enter Recovery mode, and that's where I have a problem. I use the combination "Volume up + Home + Power" to enter it, it vibrates once, shows me the Samsung logo (+ model) with "Recovery booting...." written in blue on the top left corner, I release all the buttons, and after a few seconds, it goes to a black screen, it vibrates twice and reboot on the Samsung logo, but without the "Recovery booting..." message on top left corner. After that, it enters a bootloop that only ends when I remove the battery.
So, I can never enter the recovery mode (I tried multiple times, with different methods, such as releasing only the power button, but to no avail) and cannot complete the debrick guide. I tried different stock firmwares but always with the same result.
Did I do something wrong? What can I do differently to enter recovery mode? Should I prepare the funeral for my phone?
Thank you in advance for your answers.
You should try flashing cwm with odin, then formating your system partition, if you can externally put a rom on your memory card then do so, after that install that rom on your phone, if that doesn't work then try flashing your stock firmware after you had done everything...Of course I don't know if any of this will work because I haven't run into a issue like this before, though one time my recovery was blocked and flashing cwm on it fixed it, instead of flashing stock firmware I went for cyanogenmod (now lineage os) so it might work for you, who knows.
Well, first of all, thank you for your leads.
Secondly, as you suggested, I tried flashing with Odin, with CMW (6.0.4.6 and 6.0.5.1). It went smoothly in Download mode, I get the green PASS!, but just as before, when it reboots in Recovery mode, it doesn't go beyond the blue "Recovery booting...." step, instead, the dreaded bootloop begins.
I also tried flashing with TWRP (3.0.2.0), but unfortunately no change...
And without any custom recovery, I cannot try the lineage os.
I'm begining to feel the end ^^
paupiette said:
Well, first of all, thank you for your leads.
Secondly, as you suggested, I tried flashing with Odin, with CMW (6.0.4.6 and 6.0.5.1). It went smoothly in Download mode, I get the green PASS!, but just as before, when it reboots in Recovery mode, it doesn't go beyond the blue "Recovery booting...." step, instead, the dreaded bootloop begins.
I also tried flashing with TWRP (3.0.2.0), but unfortunately no change...
And without any custom recovery, I cannot try the lineage os.
I'm begining to feel the end ^^
Click to expand...
Click to collapse
I have TWRP on my mini. When I first flashed TWRP (3.0.2.1) via Odin, I had to manually boot into recovery by holding VolUp+Home+Power as soon as I see PASS!, BEFORE the phone automatically reboots.
I have to try this a couple times to get TWRP to stick. From what I read, if you let the phone boot automatically after flashing from Odin, it will automatically overwrite the new flash with stock Samsung recover (which is bad in your case.) So you have to interrupt this by a manual reboot before the phone does its thing. If you are successful, you should boot directly into TWRP on the manual reboot. From then on TWRP will overwrite the stock recovery and you will be good to go.
I find the timing of this manual reboot a bit tricky on the phone. Do it too soon, and the TWRP was not flashed, a second too late, and the phone boots to stock. I had to try that a few times to get it right. Basically, be ready with the buttons and press it the instant you see PASS! So maybe you can try flashing TWRP again before giving up.
I have encountered the same problems today. After waking up, my phone (S4 Mini) told me an update (17 MB) was available. Happy about still getting updates, I started the process and the telephone rebooted. When returning ten minutes later it was all dark and wouldn't respond to any button combination. After working through a lot of threads and forums, trying to fix the problem, I managed to get a debrick image for the phone as well as the right firmware from Sammobile (which is astonishingly the same one that paupiette uses, though I'm from Germany, but the phone seems to have a French regional code).
At first I wasn't able to get to the Download Mode, instead my phone always told me this while denying my attempts to flash it:
BOOTE RECOVERY MODE
CHECK BOOT PARTITIONS..
COPY FROM T-FLASH..
BOOT RECOVERY..
WRITE 139008 sectors..
FLASH WRITE FAILURE
ddi: mmc_read failed
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER RPSWREV: 2
WRITE PROTECTION: Enable
Nothing seemed to work and some other topics on different forums blamed the internal flash chip (eMMC) to be the cause for all the trouble. I gave up on my phone, loosening the skrews on the back to get a look on the board. Before ripping apart the last bits, I tried to start the Download Mode one more time, so I put in the battery and hold the three buttons. Et voilĂ - the phone came up with that white booting screen. It was looping this process over and over as paupiette had allready described. I managed to start the Download Mode and flash with Odin3 (v3.12). A green "PASS!" told be, it worked until it began to enter the loop of rebooting again unable to enter the Recovery Menu.
So close but yet so far away from what I want.
Any new ideas or suggestions?
I'm trying to install TWRP on my Galaxy tab 3 10.1 (Model GT-P5210) using ODIN v3.13.1 which is currently running stock everything. Before trying to install I enabled USB debugging. I did not unlock the bootloader before attempting to install TWRP using ODIN. I do not know how to tell if I have an unlocked bootloader or how to unlock it.
I am installing the version listed here: https://forum.xda-developers.com/ga...covery-twrp-3-x-samsung-galaxy-tab-3-t3340938
I am using the version labelled FLASH WITH ODIN: Galaxy Tab 3 10.1 Wifi: GT-P5210
The file I downloaded is called "twrp-3.0.2-0-santos10wifi.tar.md5"
The first time I tried I left "Auto Reboot" option selected in ODIN. Odin said "PASS!" and booted into Android. When it finished loading I powered off the device and booted to recovery, but it booted to stock recovery, not TWRP.
I read that some people have this problem and that it is fixed by deselecting "Auto Reboot" in Odin. I did that, but after ODIN said "PASS!", I tried to restart the device but was unable to. I tried every possible button combination for 30+ seconds, including combinations that are supposed to simulate disconnecting the battery, but the device did not respond to anything at all. After growing desperate, I flashed TWRP in ODIN again, but selected "Auto Reboot" as this seems to be the only way to get the device to respond after flashing with ODIN. Booting into recovery after this led to stock recovery again. Again I tried flashing with "Auto Reboot" deselected. I again could not restart the phone. After trying to flash again using "Auto Reboot" the flash process got stuck. At this point I could not do anything to get the phone to restart. Eventually I figured out how to get the back cover off and I had to manually disconnect the battery. After reconnecting the battery the device booted into Android just fine and now I am letting it charge.
How can I get TWRP to flash correctly?
I got it to work by selecting the "Auto Reboot" option in Odin, but booting into recovery manually and quickly after the package was installed, but before it had time to boot into android.
I think were having the same issue...
IT WORKED TO ME, TOO! Thanks!
After install the TWRP file via Odin (I installed the file CF-Auto-Root-santos10wifi-santos10wifixx-gtp5210.zip in chainfire.eu domain), the Android restart and THIS is the moment to open the recovery mode: press the power and volume down, and when appear de logo in the screen, release the power button and maintain de volume down.
the_angel_moroni said:
I got it to work by selecting the "Auto Reboot" option in Odin, but booting into recovery manually and quickly after the package was installed, but before it had time to boot into android.
Click to expand...
Click to collapse
Hi,
Recently my devices start to boot loop suddenly so, i decide to flash the custom rom back.after flashing the custom rom,the device still boot loop then i try to get into TWRP Recovery mode but it would not appear, then i proceed to flash the TWRP Image recovery (suspecting the recovery already missing during the flashing rom ) via FASTBOOT once the process done, i had disconnect the cable and suddenly the device screen wouldnt turn on even though i pressed the power button for a long time.
Please help.
Thanks.
asen[email protected] said:
Hi,
Recently my devices start to boot loop suddenly so, i decide to flash the custom rom back.after flashing the custom rom,the device still boot loop then i try to get into TWRP Recovery mode but it would not appear, then i proceed to flash the TWRP Image recovery (suspecting the recovery already missing during the flashing rom ) via FASTBOOT once the process done, i had disconnect the cable and suddenly the device screen wouldnt turn on even though i pressed the power button for a long time.
Please help.
Thanks.
Click to expand...
Click to collapse
Connect phone with PC and check if you Notification light turn on or not.
If it's still on, your phone got hard bricked (maybe because you mess with custom roms and TWRP). Next time follow Flash guide in each custom roms.
You can use unbrick hardbrick method (free) or get service (paid). I recommend try free method first but when use SP Flash tool, remember ONLY use "Download Only" (Some stupid local shop can use Format and you can lose IMEI too, so careful).
You can find that method easily on: Youtube, XDA, Github, Telegram,...
If you have any error, you can reply here or join Telegram group to get help.
hi i already using SP Flash tool but i stuck at this level..