Hi,
A friend of mine bought a Samsung J700T1 in a second-hand shop, which happens to be locked by FRP.
I tried various things to unlock FRP, and now I'm in a situation where I have a blue screen error when I start the phone: "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software".
I've tried with Smart Switch, but it's asking for a code which I don't have.
I'm able to boot the device in Download mode, but that's all. When I plug the phone to my PC, a Samsung modem is detected, but is not recognized by ADB.
What would be the next steps? Is it possible to flash a rom or will I be blocked by FRP anyway?
Thanks in advance
I reflashed the system, boot, recovery using Odin (in a rush) on a j700t. Now it has the custom binary FRP error and wont boot. I cant get it to go past the download warning screen either. Vol+ or Vol- dont do anything.
I usually use Linux. Now I cant get it to show up with dmesg or lsusb, so no adb or heimdall. Does anyone know how to get back into this phone?
Thanks
Related
Hi,
I have an issue with a Nexus S i9023 of a friend
I installed the latest stock ICS CF_YAKJU_IMM76D some months ago and everything was fine.
I broke the glass of the screen and it was substitued: after a couple of months, the phone entered in a bootloop.
I tried to access recovery but was impossible, I could get to Fastboot and Download mode but choosing recovery from the first started bootlop again.
I flashed a latest CWM in fastboot via adb but no joy.
On top of that, handset behaviour is strange because only 1 on 20 times it is recognized by the PC as a Samsung device, in all other cases it is a "unknown device".
I remove all drivers from Windows and reinstalled the naked version, but again only sometimes I get it... I found out I need to have connected another handset (my HTC currently...) to have it recognized!
Now I can enter in download mode using the USB jig and I can see it from Odin, but if I use the
CF_YAKJU_IMM76D_full.tar
I get "verify image ipbl (fail)" on the handset.
If I use
CF_YAKJU_IMM76D_nowipe_nobootloaders_norecovery.tar
I get an "invalid volume size"
Do I have an hardware issue here? Some partition/internal memory with failure?
What else can I try to flash via Odin?
Obviously now after the fail I can't even get fastboot...
I also tried Unbrickable resurrector under Linux but it doesn't recognize the handset when I connect it.
Any suggestion? :crying:
SergioBigred said:
Any suggestion? :crying:
Click to expand...
Click to collapse
Ok, update. Using this thread I was able to flash via Odin 1.82 the 2.3.4
However I am still in a bootloop and I can't get fastboot but not recovery... and in fastboot I can't via USB the handset because it says "usb device not recognized"
I'm not sure if my phone is soft bricked or hard bricked. My phone was having some kind of firmware issues so like an idiot and not backing anything up, I tried to flash a stock firmware on my phone with odin and it failed. My phone is not rooted or anything it is complete stock and now when I try to boot up the phone I'm not sure if it goes into recovery automatically or what but when I turn it on it goes to this screen saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". If this is not recovery mode then I can only go in download mode I have tried going into recovery mode. I've tried odin several times, using different usb cables and different usb ports on my computer and still nothing, I have used Samsung Kies and Kies 3 they both fail and then tell me that I need to do emergency recovery from another computer with a code but it is just blank when it comes up it does not give me any codes. I've even went to Tools > Emergency firmware recovery and still shows no codes or anything it is still blank.
Suggestions?
I fixed it, for anyone who may have the similar problem this will help you: https://forum.xda-developers.com/galaxy-s4/general/guide-sm-s975l-twrp-4-4-2-custom-roms-t3009757
For me, all I needed to do was flash twrp recovery and my phone started working again so I decided not to mess with anything else
Hello,
I am currently in a situation where USB debugging was not enabled, CROM service status is set to "Locked". This is causing an issue on my International Galaxy S6 Edge (g9250) -- It is stuck in a boot loop and the android OS that was previously installed was wiped on accident through the stock android recovery mode.
I am unable to flash TWRP recovery to the phone, I am unable to use Odin to flash a stock ROM image to the phone, or perform any data transfer between my Windows machine to the phone. Now I am sure this is because I never enabled developer mode and turned on USB debugging, and also because this CROM service is set to lock. When I attempt to sideload using ADB I get error:closed. When using the Skipsoft Unified Android Toolkit any task performed stops at: "Waiting for USB debugging".
Is there any solution for this? I've looked all over the internet and haven't been able to solve my issue -- I'm stuck at a perpetual boot loop because there is no Android OS on the device's partition, and also am unable to flash the stock ROM using ODIN or sideload using ADB.
Is there is a way to turn on USB debugging when stuck in a bootloop? Or a way to disable CROM service on the phone to be able to flash or transfer files?
As of right now the device is completely useless and I have been researching for the past 5 days
Any help is very appreciated, please let know if there is more information needed.
mellobc said:
Hello,
I am currently in a situation where USB debugging was not enabled, CROM service status is set to "Locked". This is causing an issue on my International Galaxy S6 Edge (g9250) -- It is stuck in a boot loop and the android OS that was previously installed was wiped on accident through the stock android recovery mode.
I am unable to flash TWRP recovery to the phone, I am unable to use Odin to flash a stock ROM image to the phone, or perform any data transfer between my Windows machine to the phone. Now I am sure this is because I never enabled developer mode and turned on USB debugging, and also because this CROM service is set to lock. When I attempt to sideload using ADB I get error:closed. When using the Skipsoft Unified Android Toolkit any task performed stops at: "Waiting for USB debugging".
Is there any solution for this? I've looked all over the internet and haven't been able to solve my issue -- I'm stuck at a perpetual boot loop because there is no Android OS on the device's partition, and also am unable to flash the stock ROM using ODIN or sideload using ADB.
Is there is a way to turn on USB debugging when stuck in a bootloop? Or a way to disable CROM service on the phone to be able to flash or transfer files?
As of right now the device is completely useless and I have been researching for the past 5 days
Any help is very appreciated, please let know if there is more information needed.
Click to expand...
Click to collapse
Greetings and welcome to assist. Can you get into download mode ? If you can does smartswitch emergency firmware recovery work
Regards
Sawdoctor
Hello all,
So I finally got the dreaded FRP lock error when trying to reboot my phone.
Things I've tried to do:
1. Install Smart Switch and enter my model number + S/N and I get an error "This model number cannot be initialized"
2. Install Samsung Kiss update the drivers etc
3. Download stock firmware and try flash through Odin "Device wont recognize on PC or Odin" (But with another phone it will, so USB is fine)
4. Went into the recovery menu, wiped device/cleared cache etc
So the problem is the device is not recognizing on my on Windows 10 + Windows 7 - If I can get the device to recognize i will be able to flash stock firmware and my issue will be resolved.
If anyone has a bypass, or has resolved their issue please let me know - because I have tried everything.
Hi, I own a samsung galaxy s7, running Superman-ROM and using TWRP recovery. Recently I was mucking around with some friends and decided it would be a good idea to install a ****ty game as firmware (through Lucky Patcher). After asking me to reboot I did and it is now soft-bricked. It says "custom binary blocked by FRP lock". The problem is that both OEM unlock & USB debugging were off, so I cannot connect to my PC. The only thing I can access is Download mode, but I am not able to enter recovery mode to wipe it. I have tried reinstalling both TWRP & Samsung's default ROM through Samsung Odin (I do have USB drivers) and they both fail. Is this fixeable or would I have to give it to a professional?
Thanks in advance, Lucien
This once happened to me and I had to end up wiping everything on my phone with Odin.