Hi, some months ago, I rooted my phone, and it was a success. But yesterday, it shutted down because it ran out of battery so I connected it to the PC (only to charge it) and then to the normal power supply (I'm Italian, I don't know what it is in English ;D). Then I rebooted it, but it got stuck on the phone s/n screen, and in the top left corner there was the green text saying "Custom binary blocked by frp lock). After some rebootings I decided to flash the stock rom from Odin, but it failed: the screen showed another time the green text from the FRP Lock (still in the downloading mode) and the loading bar was frozen. Odin showed just the log and "success 0 / failed 1" at the end. Soooo..... now I'm getting "Firmware upgrade encountered an issue".... + I realized just now that my s/n is SM-J320FN and I tried flashed a SM-J320F rom....
- I tried to enter CWM
- Kies shows that it is "Connecting..." but nothing happens
- Hard reset shows me the firmware upgrade error
I can still enter Download Mode if I pull out the battery, and it says:
ODIN MODE
SECURE DOWNLOAD: ENABLE
CURRENT BIN: Custom
SYSTEM STATUS: Custom
FRP LOCK: ON
it's a Samsung Galaxy J3 6 (SM-J320FN)
Thta's my first post, and I didn't find the correct place to post this thread on
Related
My Galaxy Note 10.1 is stuck in recovery mode and I'm not sure what to do next. Here's what happened:
After connecting to wifi, a software update was downloaded and a message asked me to install it. I accepted, because otherwise it said it would remind me in 3 hours.
I left it plugged in and went out. When I came back, there was a screen warning me of the dangers of installing a "custom OS" (?) The options were to press the volume-up to install it, or volume-down to reboot. Neither option did anything. Hard rebooting went to the same screen.
Later, I tried to charge it, but got this repeating sequence: the symbol showing a charging (but empty batter) for a couple of seconds, then a picture of the android robot with blue polyhedron thing (like here), then blank screen. A few seconds later it repeats.
Finally I try rebooting into recovery mode:
Android system recovery (3e) ... reboot system now apply update from external storage wipe data/factory reset ... MANUAL MODE -- Appling Multi-CSC... (sic) Applied the CSC-code : INU Successfully applied the multi-CSC.
Now, I don't really care whether I get the update or not, or whether I lose some data - I just really want a working phone again. I'm travelling atm, so it's a bit inconvenient. But mostly I'm asking for help to avoid making the problem worse.
So: what should I do?
It's a (unlocked) Samsung Galaxy Note 10.1 with ICS.
Download the full firmware for your region. Then charge it fully
Install Kies so that you get the USB drivers.
Download Odin
Unzip the firmware that you downloaded
start Odin and select the PDA,browse to the firmware and select it.
Enter download mode on the note with Power & Vol up
Make sure kies is not running
Now connect it and check that Odin finds the Note.
Press start to flash the firmware.
Don't go out while it flashes!!
Sent from my GT-N8000 using XDA Premium HD app
Hi,
Not sure why this happened, but while charging my tablet (galaxy note 10.1 GT-N8013 2013 edition) the tablet flashed and rebooted itself without user interaction. Upon reboot it froze on the samsung splash screen, so i pressed and held in the power button until the device restarted. When it did restart it no longer showed the splash screen, just squiggly lines thru the screen and it sits there unresponsive. I can boot the device into download (odin) mode, it shows that there is no custom binary download, shows the current binary is samsung official, but it says system status is custom, which is odd because i have never attempted to flash a custom rom nor have i tried to root this device.
i proceeded to install odin on my laptop and downloaded the factory binary from sammobile. I loaded everything up (as per the directions) but it fails, says there is no PIT partition. Im not sure where to go from here, i contacted samsung, but they are useless, says they cant help because the device is out of warranty. Any help would be greatly appreciated , thanx in advance.
So the phone worked fine when I bought it 2 days ago other than red text on top of the screen that said "binary is not seandroid enforcing". I looked into it and figured it meant the phone was rooted and custom. I picked up a nano sim today and the phone would not reboot. it started getting stuck saying "binary is not seandroid enforcing" and "custom binary blocked FRP locked". So i tried to flash back to stock rom with ODIN3 3.10.7. On the download mode screen it notes a custom binary and custom system as well as knox warranty void. So i try to flash N920TTMB1BOH6 first in the AP in ODIN3 and fails. Then i try to flash N920TTMB2COKC and it starts gets through some stuff and then fails; but it keeps my phone with a progress bar as if it is still installing but ODIN3 has failed out. So I exit ODIN3 and unplug the phone and now it will not turn off or start up into the boot loop. its stays on an error screen "an error has occurred while updating the device software use the emergency recovery function in smart switch". Smart switch did nothing. i put in the model and SN and it started to go to work and failed out after downloading info and gave me not emergency recover code. the only thing it can get into now is download/recover mode and when it is there is notes that the binary is now Samsung Official while the system is still custom. How do i get past this? I have attached a few screen shots of my issues.
Any help would be sooo awesome or I'm out way more cash than I'd like to be. :crying:
Josh
Message me ...I will help actually check your msgs I'll send u one
Sent from my SM-N920T using XDA-Developers mobile app
did you get it working yet
joshd00 said:
So the phone worked fine when I bought it 2 days ago other than red text on top of the screen that said "binary is not seandroid enforcing". I looked into it and figured it meant the phone was rooted and custom. I picked up a nano sim today and the phone would not reboot. it started getting stuck saying "binary is not seandroid enforcing" and "custom binary blocked FRP locked". So i tried to flash back to stock rom with ODIN3 3.10.7. On the download mode screen it notes a custom binary and custom system as well as knox warranty void. So i try to flash N920TTMB1BOH6 first in the AP in ODIN3 and fails. Then i try to flash N920TTMB2COKC and it starts gets through some stuff and then fails; but it keeps my phone with a progress bar as if it is still installing but ODIN3 has failed out. So I exit ODIN3 and unplug the phone and now it will not turn off or start up into the boot loop. its stays on an error screen "an error has occurred while updating the device software use the emergency recovery function in smart switch". Smart switch did nothing. i put in the model and SN and it started to go to work and failed out after downloading info and gave me not emergency recover code. the only thing it can get into now is download/recover mode and when it is there is notes that the binary is now Samsung Official while the system is still custom. How do i get past this? I have attached a few screen shots of my issues.
Any help would be sooo awesome or I'm out way more cash than I'd like to be. :crying:
Josh
Click to expand...
Click to collapse
did you get your phone working yet, i might be able to help you,,, i wont be avaibable till after the shabbat is over friday sundown to saturday sundown
I got it fixed. I just had to try it on a different computer. Ridiculous.
Sent from my SM-N920T using XDA-Developers mobile app
Hello, I have a Samsung Galaxy S6 It was working fine until recently when i try to root using cf autoroot i got bootloop. Anyway, I tried flashing the rom on in to a 6.0.1 and i also get that DM-Verity Need to check drk error... But mines a bit different.. I flashed the most recent 6.0.1 onto the phone from SamFirmware just fine... When the phone restarted it starts the blue "update" screen with a loading bar. It gets to about 24% then jumps to about 32% and briefly says "erasing" and restarts once more... It then proceeds to say something along the lines of "Supported api: 3" in white and "E:failed setting up dirty target" in red.. at the recovery type screen. I can then restart the phone to VERY BRIEFLY see the blue "updating" screen and then i get the final error i see which is the DM-verity verification failed... need to chekc DRK first.... So i have NO IDEA What to do next.. i tried also to restore my phone with samsung smart switch but no luck
I bricked/bootlooped my phone.
I've been using Superman ROM v2.4.1 for a while, but recently my Snapchat stopped working and I couldn't pass the SafetyNet, so I tried to fix it.
I turned off my developer options, and downloaded this App: https://forum.xda-developers.com/sho....php?t=2524485
My phone warned me this App might be harmful but I ignored it, and then changed the setting to permissive and then enfordcing a couple times. Then I rebooted my device, now it is stuck in a loop. It doesnt go beyond the 'Samsung Galaxy S7" logo and just turns off after that.
I cannot boot into recovery either, only download mode.
When i try to boot up or into recovery, it says on the top of the screen in red text "Custom Binary blocked by FRP Lock".
Can anyone help me? I have a flight in the morning so I really need this fixed. Is this caused by the App I used to change the SELinux Mode? Or is it because Developer options and hence OEM Unlocking is turned off in the settings?
What can I do to fix this?
Cheers
Dear Sir just Flash with stock firmware be sure u are using latest one to revive phone back to life.
thanks
FRP locked and cannot load stock FW
I'm having the same issue as theDroidfanatic, but i cannot flash the stock FW.
I have a Samsung S7 edge, running Superman, i believe marshmallow (i don't recall the exact version).
I accidentally enabled the OEM lock in the phones settings.
On trying to boot normally, I see the superman startup screen, and the FRP message across the top of the screen in red. "Custom Binary blocked by FRP Lock"
I can only boot into download mode.
Odin (3.12.7 and 3.12.3) can detect the phone being plugged in (so i think this system has the correct drivers, and my cables/ports are good).
I downloaded the latest FW from sammobile.com for the MTA region (its a Canadian MTS phone).
I load all of the files into Oden and everything appears fine. When i try to start the transfer it hangs at SetupConnection. Ah hour later, its still hanging there.
I've tried 2 PCs, and about a dozen USB cables; same result every time.
Its been a while since i played with rom stuff, am i missing something somewhere?
## EDIT
## Above represents 8+ hours of frustration;
## below, 20 minutes on a hunch and some dumb luck;
## proving that sometimes it is better to be lucky than good.
For anyone else having similar issues:
After installing Kies (on Windows 10; which required a Microsoft Virtual C++ pack for Kies to install), Kies installed a different USB driver.
Odin did not show any difference regarding seeing the phone. After the new driver was installed, Odin is now able to flash stock FW.
Did you manage to repair your phone. My note 9 don’t show up on my laptop usb not recognised
I had similar issue when i was trying to install firmware while developer mod was was disabled (in my Note 5). FRP lock was ON, then it got bricked. I gave my phone to a local phone repair shop, they have some technology to bypass FRP lock by using FRP bypass box.