Database Develop

HARD BRICKED Note 5

completely lost and its been a week of em trying to get this phone to accept sp,ething form odin and still noluck ive been glued to this computer and learned alot but nothing that has been able to fix my issue, any help would be appreciated please and thankyou

jpres1991 said:
completely lost and its been a week of em trying to get this phone to accept sp,ething form odin and still noluck ive been glued to this computer and learned alot but nothing that has been able to fix my issue, any help would be appreciated please and thankyou
Click to expand...
Click to collapse
Can you please elaborate. .what exactly the issue...what you did?

manishvy said:
Can you please elaborate. .what exactly the issue...what you did?
Click to expand...
Click to collapse
i have had my device rooted since the week i got it in october successfully, no issues. when i got the phone it was on the oi6 firmware, rooted it and put MOAR rom on it, no issues. then on the 23rd the day before i was going to go out of town i changed my primary google account password on my device, and for some reason i couldnt tell you why other than it didnt seem that it would be of any significance that OEM UNLOCK option was enabled so i turned it off not thinking anything of it, and right after i reboot the phone i found myself in a bootloop. only going to samsung galaxy note 5 powered by android with little red writing at top that says custom binary blocked by FRP lock. so i did some research and it became obvious what my issue was that the oem unlock should never had been touched. from what i figure, but that didnt validate why i was never given the chance to actually verify my account being that the device hasnt booted back into the os or any screen other than the splash screen i mentioned and download mode. thats the only two things i can access my download screen reads this
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-N920P
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: ON
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x0500)
AP SWREV: B:2 K:0 S:0
i have tried flashing stock oi6, ive tried PIT file for oi6 ive gotten errors starting from couldnt open com port ehich seems to vary from the different versions of odin more or less, ive gotten complete write fail error, ive gotten COULDNT GET PIT FOR MAPPING as well as THERE IS NO PIT, and so i tried flashing one andit failed or just wouldnt go through, i mean ive just about ran the well dry as far as what ive read to do. Odin recognozes the device, i just cant get it to flash anything. as for all i know the device is wiped. my assumption.

http://forum.xda-developers.com/showthread.php?t=3191927
FRP LOCK ON Can't ODIN firmware... Lord help me.
---------- Post added at 08:31 PM ---------- Previous post was at 08:31 PM ----------
Seems this guy got his working

Try use Samsung KIES (or Samsung Smart Switch) on Windows PC to flash/restore your firmware. I've never had to this way though.
And BTW. This is not a "hard brick", so your thread title is misleading. It's "soft"...

jpres1991 said:
i have had my device rooted since the week i got it in october successfully, no issues. when i got the phone it was on the oi6 firmware, rooted it and put MOAR rom on it, no issues. then on the 23rd the day before i was going to go out of town i changed my primary google account password on my device, and for some reason i couldnt tell you why other than it didnt seem that it would be of any significance that OEM UNLOCK option was enabled so i turned it off not thinking anything of it, and right after i reboot the phone i found myself in a bootloop. only going to samsung galaxy note 5 powered by android with little red writing at top that says custom binary blocked by FRP lock. so i did some research and it became obvious what my issue was that the oem unlock should never had been touched. from what i figure, but that didnt validate why i was never given the chance to actually verify my account being that the device hasnt booted back into the os or any screen other than the splash screen i mentioned and download mode. thats the only two things i can access my download screen reads this
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-N920P
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: ON
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x0500)
AP SWREV: B:2 K:0 S:0
i have tried flashing stock oi6, ive tried PIT file for oi6 ive gotten errors starting from couldnt open com port ehich seems to vary from the different versions of odin more or less, ive gotten complete write fail error, ive gotten COULDNT GET PIT FOR MAPPING as well as THERE IS NO PIT, and so i tried flashing one andit failed or just wouldnt go through, i mean ive just about ran the well dry as far as what ive read to do. Odin recognozes the device, i just cant get it to flash anything. as for all i know the device is wiped. my assumption.
Click to expand...
Click to collapse
just flash latest stock firmware through odin and your phone will be completely wiped and back to normal.

54NJ41 said:
just flash latest stock firmware through odin and your phone will be completely wiped and back to normal.
Click to expand...
Click to collapse
You can't if OEM UNLOCK is not enabled. ...

UpInTheAir said:
You can't if OEM UNLOCK is not enabled. ...
Click to expand...
Click to collapse
how do you reckon i flash it using kies or smart switch ? i dont have my serial number and the device isnt recognized in kies or smart switch

jpres1991 said:
how do you reckon i flash it using kies or smart switch ? i dont have my serial number and the device isnt recognized in kies or smart switch
Click to expand...
Click to collapse
It's on the box your bought it with. ...

UpInTheAir said:
You can't if OEM UNLOCK is not enabled. ...
Click to expand...
Click to collapse
for me it worked and use latest Odin

UpInTheAir said:
You can't if OEM UNLOCK is not enabled. ...
Click to expand...
Click to collapse
UpInTheAir said:
It's on the box your bought it with. ...
Click to expand...
Click to collapse
im 100 % sure ive tried all the numbers on the box

jpres1991 said:
im 100 % sure ive tried all the numbers on the box
Click to expand...
Click to collapse
I'm sorry, this is where my help ends.
Awfully suspicious if you can't find your serial number.
They all come on the sticker that seals the two halves of the box. This is standard from Samsung.
And you're in the wrong forum. .

UpInTheAir said:
I'm sorry, this is where my help ends.
Awfully suspicious if you can't find your serial number.
They all come on the sticker that seals the two halves of the box. This is standard from Samsung.
And you're in the wrong forum. .
Click to expand...
Click to collapse
WELL THANKYOU for your detective like skills considering i know my imei and meid by heart would you like photographs of my box
fact of the matter is is smart switch DOES NOT recognize the numbers give it a try detective
model number is SM-N920P
MEID_DEC: 256691545905342464
MEID_HEX: 99000583518500
ESN_HEX: 80ED70AD
ESN_DEC: 12815560877
SPC: 970920

jpres1991 said:
i have had my device rooted since the week i got it in october successfully, no issues. when i got the phone it was on the oi6 firmware, rooted it and put MOAR rom on it, no issues. then on the 23rd the day before i was going to go out of town i changed my primary google account password on my device, and for some reason i couldnt tell you why other than it didnt seem that it would be of any significance that OEM UNLOCK option was enabled so i turned it off not thinking anything of it, and right after i reboot the phone i found myself in a bootloop. only going to samsung galaxy note 5 powered by android with little red writing at top that says custom binary blocked by FRP lock. so i did some research and it became obvious what my issue was that the oem unlock should never had been touched. from what i figure, but that didnt validate why i was never given the chance to actually verify my account being that the device hasnt booted back into the os or any screen other than the splash screen i mentioned and download mode. thats the only two things i can access my download screen reads this
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-N920P
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: ON
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x0500)
AP SWREV: B:2 K:0 S:0
i have tried flashing stock oi6, ive tried PIT file for oi6 ive gotten errors starting from couldnt open com port ehich seems to vary from the different versions of odin more or less, ive gotten complete write fail error, ive gotten COULDNT GET PIT FOR MAPPING as well as THERE IS NO PIT, and so i tried flashing one andit failed or just wouldnt go through, i mean ive just about ran the well dry as far as what ive read to do. Odin recognozes the device, i just cant get it to flash anything. as for all i know the device is wiped. my assumption.
Click to expand...
Click to collapse
mate, its really nothing to worry about, it isnt hard bricked,
i had the exam same issue, that oem lock can be a real pain in the arse,
all you need to do is download the firmware, and i mean not just the same android version, but the same, as in oc1 ok1, what ever version you were rocking,
in my case it was the latest firmware available on sammobile,
and flash it via odin,
after that you must wipe cache, data, and factory reset to be a able to use your phone,
once booted,
you can login with you google account, enable oem unlock from dev mode, and install custom recovery and do what you do from there.
cheers

UpInTheAir said:
I'm sorry, this is where my help ends.
Awfully suspicious if you can't find your serial number.
They all come on the sticker that seals the two halves of the box. This is standard from Samsung.
And you're in the wrong forum. .
Click to expand...
Click to collapse
urmother93 said:
mate, its really nothing to worry about, it isnt hard bricked,
i had the exam same issue, that oem lock can be a real pain in the arse,
all you need to do is download the firmware, and i mean not just the same android version, but the same, as in oc1 ok1, what ever version you were rocking,
in my case it was the latest firmware available on sammobile,
and flash it via odin,
after that you must wipe cache, data, and factory reset to be a able to use your phone,
once booted,
you can login with you google account, enable oem unlock from dev mode, and install custom recovery and do what you do from there.
cheers
Click to expand...
Click to collapse
SO dont do the ok3 if thats not what i was on prior to this happening?
my phone isnt recgonized in odin now for some reason. it has been up until now

I can solve your problem with Fap Lock On

hoangps said:
I can solve your problem with Fap Lock On
Click to expand...
Click to collapse
ALL EARS

So long as you are using genuine Samsung firmware or smart switch you do not need OEM unlocked.
If Odin is not recognizing your phone something has gone wrong with either your drivers or your phone is in a bad state.
Power down your phone, if you have to because it is restarting, catch it so you get back into download mode.
Then follow these steps exactly as they are laid out.
Open Smart Switch, click MORE, click Emergency software recovery and initialization, click device initialization, type in your model number using caps and dashes such as SM-N9200 or whatever your device is, then input your serial number again using caps for all the letters in your SN, finally connect your phone to your PC and continue with the prompts from Smart Switch.
The problem is since you have a carrier version, smart switch may not work. There was a guy who said it would not work for an AT&T phone.
Good luck.
Edit: I checked in smart switch using the sprint model number and it took it so you should be good to go.

CodeNameRedNeck said:
So long as you are using genuine Samsung firmware or smart switch you do not need OEM unlocked.
If Odin is not recognizing your phone something has gone wrong with either your drivers or your phone is in a bad state.
Power down your phone, if you have to because it is restarting, catch it so you get back into download mode.
Then follow these steps exactly as they are laid out.
Open Smart Switch, click MORE, click Emergency software recovery and initialization, click device initialization, type in your model number using caps and dashes such as SM-N9200 or whatever your device is, then input your serial number again using caps for all the letters in your SN, finally connect your phone to your PC and continue with the prompts from Smart Switch.
The problem is since you have a carrier version, smart switch may not work. There was a guy who said it would not work for an AT&T phone.
Good luck.
Edit: I checked in smart switch using the sprint model number and it took it so you should be good to go.
Click to expand...
Click to collapse
yes i can get it in download mode ive installed the drivers from samsung website for the note 5, and installed them. is there other drivers i should install fgor it to recognize it? i also am successful in getting smart switch to recognize the SM-N920P for my phone model but i am unclear on how to obtain the serial number that smart switch wants. ive tried the dec hex the imei esn hex and the spc none of which it accepts. i have the box and it doesnt say serial number anywhere so im lost when i get to that point

jpres1991 said:
i am unclear on how to obtain the serial number that smart switch wants. ive tried the dec hex the imei esn hex and the spc none of which it accepts. i have the box and it doesnt say serial number anywhere so im lost when i get to that point
Click to expand...
Click to collapse
That is a problem then because you need that number. It should be labeled SN and should be a mix of letters and numbers. Perhaps sprint keeps those records on file.
Good luck.

Custom Binary blocked by oem lock?

Simply: I have a 960-f note 9 (Exynos). It was rooted and had twrp. I was very stupid and disabled oem unlock. Now I am stuck on a screen that says Custom Binary blocked by OEM Unlock. Can't access download nor recovery mode.

TimaTheTam said:
Simply: I have a 960-f note 9 (Exynos). It was rooted and had twrp. I was very stupid and disabled oem unlock. Now I am stuck on a screen that says Custom Binary blocked by OEM Unlock. Can't access download nor recovery mode.
Click to expand...
Click to collapse
Z3X-team.com Box Help!

Baroccoes said:
Z3X-team.com Box Help!
Click to expand...
Click to collapse
you have to wait 168 hours with the phone being on and connected to cell or wifi before itll allow you to re-unlock it

Youdoofus said:
you have to wait 168 hours with the phone being on and connected to cell or wifi before itll allow you to re-unlock it
Click to expand...
Click to collapse
yeah... i wish... that also didn´t worked out for me... i guessyou can´t fool binarie 4 with that trick...

RSGI said:
yeah... i wish... that also didn´t worked out for me... i guessyou can´t fool binarie 4 with that trick...
Click to expand...
Click to collapse
i wouldnt necessarily say that. In all the goofy 168 hour malarky ive seen since i first heard of it, i have heard of instances where if you relock it then you might be forced to resort to starting from scratch with a fresh firmware flash via Odin

Youdoofus said:
i wouldnt necessarily say that. In all the goofy 168 hour malarky ive seen since i first heard of it, i have heard of instances where if you relock it then you might be forced to resort to starting from scratch with a fresh firmware flash via Odin
Click to expand...
Click to collapse
LOL... you wrote MALARKY...
I´ve been there and done that...
Unless i´m skipping some step (that i can´t see)...
I kept the phone connected for over 200 hours (just wanted to be sure) with OEM Unlock present but disabled (not greyed out), and still KG State Prenormal...
Have you or anyone else tried that trick with binary 4 installed? Did it work? If the answer for both questions is YES, please make a detailed step by step guide so i wont be able to f*ck it up... again....
Please notice that i have not excluded the chance that i been messing up all this time, unlikely but possible... just need to know where...

RSGI said:
LOL... you wrote MALARKY...
I´ve been there and done that...
Unless i´m skipping some step (that i can´t see)...
I kept the phone connected for over 200 hours (just wanted to be sure) with OEM Unlock present but disabled (not greyed out), and still KG State Prenormal...
Have you or anyone else tried that trick with binary 4 installed? Did it work? If the answer for both questions is YES, please make a detailed step by step guide so i wont be able to f*ck it up... again....
Please notice that i have not excluded the chance that i been messing up all this time, unlikely but possible... just need to know where...
Click to expand...
Click to collapse
yeah, i know well, if the state is prenormal, then youre still stuck (obviously). Have i personally seen any binary 4 phones work with the 168 hour trick? No, but it was worth a try. Not sure why they even bothered with the 168 hour thing in the first place, its not like thieves are worried about the cops running down a small time criminal like a random phone thief in the slightest, so leaving it on connected to a network wont dissuade anyone. sorry man, im at my depths here.

N950F bootloader issue

For mentioned model i do not get any type of Bootloader interface detected as hardware in device menager. Which also means i can not access it from adb in order to unlock bootloader. I have found some talk about switching into Unlock mode from Odin mode but can not find a way to do it. This also happens while i did USB debbiging and OEM unlock set on. I have latest Pie on it if that makes any difference.
I hope anyone has some advice on how to solve this and that you in advance

scudteshka said:
For mentioned model i do not get any type of Bootloader interface detected as hardware in device menager. Which also means i can not access it from adb in order to unlock bootloader. I have found some talk about switching into Unlock mode from Odin mode but can not find a way to do it. This also happens while i did USB debbiging and OEM unlock set on. I have latest Pie on it if that makes any difference.
I hope anyone has some advice on how to solve this and that you in advance
Click to expand...
Click to collapse
Go into developer options and toggle OEM unlock on. That's all that is required on Samsung's.

SnowFuhrer said:
Go into developer options and toggle OEM unlock on. That's all that is required on Samsung's.
Click to expand...
Click to collapse
Oh ok but still it wont let me flash twrp even thru odin. This seems far to complicated comming from xiaomi.

scudteshka said:
Oh ok but still it wont let me flash twrp even thru odin. This seems far to complicated comming from xiaomi.
Click to expand...
Click to collapse
That's probably because of some recent locks Samsung has made. It used to be easier with Samsung . But anyway, look here for more details. https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535

SnowFuhrer said:
That's probably because of some recent locks Samsung has made. It used to be easier with Samsung . But anyway, look here for more details. https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Click to expand...
Click to collapse
Dude you are a major help and thank you very much ?

Question S21 Ultra SM-G998B

Dear Friend,
I am having issue with S21 Ultra which i purchase just 2 months ago.
I decide to make my device root able , then i have notice that there is no OEM Lock option (Missing) in developer mode.
After searching XDA forum and Google all the setups mention there i have tried to visible OEM Unlocker option but OEM lock option never visible. Even flash stock rom again and again and wait for 168H but still its not visible.
When i go in download mode and try to flash TWRP or any custom rom it show below mention msg.
"Cause
No sign info: (Recovery)
Custom Binary (Recovery) due to remaining installment balance"
Can any one guide me what is the issue, i had purchase this product with Full payment then why it is behaving so strange.

google is best friend please add him to your friend list
reboot to download mode(connected phone to pc, reboot and hold vol+ and vol-) and read first screen options:
EDIT: sorry if you cant see these option list, there could be something different in your case.

Very srtange situation. I have exact same model.

vlubosh said:
google is best friend please add him to your friend list
reboot to download mode(connected phone to pc, reboot and hold vol+ and vol-) and read first screen options:
View attachment 5580147
EDIT: sorry if you cant see these option list, there could be something different in your case.
Click to expand...
Click to collapse
Thanks brother for your prompt response , i tried this but issue remain same

Samaly01 said:
Thanks brother for your prompt response , i tried this but issue remain same
Click to expand...
Click to collapse
Can you boot the phone? Try fastboot oem device-info to check what state od BL is.

vlubosh said:
Can you boot the phone? Try fastboot oem device-info to check what state od BL is.
Click to expand...
Click to collapse
Phone is booting ...no issue in that ....Fastboot not working in s21 Ultra g998b....

Samaly01 said:
Phone is booting ...no issue in that ....Fastboot not working in s21 Ultra g998b....
Click to expand...
Click to collapse
Allow usb debugging in dev.settings

vlubosh said:
Allow usb debugging in dev.settings
Click to expand...
Click to collapse
USB debuggin already allowed ....ADB command work but not fastboot

Samaly01 said:
USB debuggin already allowed ....ADB command work but not fastboot
Click to expand...
Click to collapse
I think you need to have a SIM card in there and to have internet access to see the OEM unlock toggle. Do both of these things apply to you?

Macusercom said:
I think you need to have a SIM card in there and to have internet access to see the OEM unlock toggle. Do both of these things apply to you?
Click to expand...
Click to collapse
SIM Card is installed both WIFI and Data is working but issue remain same.

Samaly01 said:
SIM Card is installed both WIFI and Data is working but issue remain same.
Click to expand...
Click to collapse
Try disabling the automatic date and time and set the date to a day at least one week from now

I have observe a very strange thing, when ever I reboot the device and visit develope option Oem Locker appear then again revisit to developer option it disappear again. Only rebooting device option bring oem option just for few minutes.

so then, when you see unlock option reboot right to DL mode and look if you see device unlock

vlubosh said:
so then, when you see unlock option reboot right to DL mode and look if you see device unlock
Click to expand...
Click to collapse
Still same issue
"Cause
No sign info: (Recovery)
Custom Binary (Recovery) due to remaining installment balance"

Someone suggested to use Samsung combination file, after searching on google there are only 3 Combination files available U1, U2, U3.
Latest file available is COMBINATION_FAC_FAR0_G998BXXU3AUD3
( I think this not usable on Android 12 version (U4)
Please suggest what option i have left to resolve above mention issue.

Could you try to flash latest Stock rom(Via odin) and try again?

Latest Firmware (SM-G998B_BTU_G998BXXU4CVC4) Flash via Odin...Result same

Found this, maybe your case
Custom binary blocked due to remaining installment balance galaxy
Hi, I recieved my S21 Ultra yesterday and sucessfully rooted it using the guide/youtube tutorial. Today, I restarted the device and upon restarting it would go into a bootloop with a small message on top saying: 'Custom binary blocked due to...
forum.xda-developers.com

vlubosh said:
Found this, maybe your case
Custom binary blocked due to remaining installment balance galaxy
Hi, I recieved my S21 Ultra yesterday and sucessfully rooted it using the guide/youtube tutorial. Today, I restarted the device and upon restarting it would go into a bootloop with a small message on top saying: 'Custom binary blocked due to...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks Brother, but issue is same mine.... no solution

checke my stats in DL mode:
KG state checking
FRP lock off
OEM lock OFF(u)
Warranty void 1
HDM status none
I think you problem is in KG state.
Maybe try to change date as in this tutorial:

Pixel 5 - Removal from Beta 13 - Corrupt Error

So.... I removed my Pixel 5 form the beta 13 program, selected update on the devices and had it download Android 12 a few weeks back. On reboot I get the "device is corrupt" error with visit the g.co/ABH link. If I hit the power button that error loops, and trying a hard / factory reset does nothing.
I tried several of the steps but since I cannot get into Dev mode to unlock the bootloader I'm kind of stuck.
The most I have been able to do is with the rescue tool, but that throws a "software on device is newer then this tool" error and wont go forward.
Any suggestions? Should I just send in to a repair shop? Or move on?

I heard from a friend yesterday that this happens with USB C to USB C. Try an A or B port and sideload the OTA

xunholyx said:
I heard from a friend yesterday that this happens with USB C to USB C. Try an A or B port and sideload the OTA
Click to expand...
Click to collapse
Tried both types of cables, no luck...

grmacd said:
Tried both types of cables, no luck...
Click to expand...
Click to collapse
As recommended by @xunholyx try sideloading the OTA, if you're able to get into recovery.
If you didn't have OEM unlocking enabled in Developer Options, you might be SOL.

V0latyle said:
As recommended by @xunholyx try sideloading the OTA, if you're able to get into recovery.
If you didn't have OEM unlocking enabled in Developer Options, you might be SOL.
Click to expand...
Click to collapse
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet

grmacd said:
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet
Click to expand...
Click to collapse
Unfortunate and I feel for you.
It's generally advisable to always unlock the bootloader when running any kind of beta software, just because of this eventuality - if something goes wrong, you need to have a way to recover the device.

grmacd said:
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet
Click to expand...
Click to collapse
You should be able to boot to recovery from the bootloader

I can boot to recovery, but the software wont sideload since the boot locker is locked.
My one hope is the fact Rescue mode on the web is throwing "software on the device older then this tool" so I am hoping once that gets a newer version I will be ok. So into the drawer it goes...

But you don't need an unlocked bootloader to sideload an OTA....

xunholyx said:
But you don't need an unlocked bootloader to sideload an OTA....
Click to expand...
Click to collapse
Ok... perhaps I will give it another try tomorrow.

grmacd said:
Ok... perhaps I will give it another try tomorrow.
Click to expand...
Click to collapse
Try flashing it a second time when you get the error. A friend is mine had trouble with it and a locked bootloader as well. I don't remember how he fixed it, but I think that that was it. I'll get in touch with him later. I'm at work right now

xunholyx said:
Try flashing it a second time when you get the error. A friend is mine had trouble with it and a locked bootloader as well. I don't remember how he fixed it, but I think that that was it. I'll get in touch with him later. I'm at work right now
Click to expand...
Click to collapse
So this AM I downloaded the newest ZIP file and followed the step on the site - after about 10 minutes presto the phone is back up and running with Android 13! Thanks for your help!