Database Develop

[Q] super softbrick

****************EDIT*******************
DISREGARD, I fixed it kind of....
**************************************
So... I believe my samsung cappy is "super" soft bricked. like to the point where there is nothing actually on the phone.
Holding power button + vol up and down for like.. 40 seconds results in
RST_STAT = 0x1
PMIC_IRQ1 = 0x2c
PMIC_IRQ2 = 0x0
PMIC_IRQ3 = 0x0
PMIC_IRQ4 = 0x0
PMIC_STATUS1 = 0xc0
PMIC_STATUS2 = 0x2c
*
Click to expand...
Click to collapse
My computer sees the phone in this state as "SAMSUNG USB Composite Device" and "SAMSUNG Mobile Modem #3"
Odin sees the phone but doesn't go past "File Analysis" stage.
What do?

First, this is a question, please post in the Q/A section.
Second, there are tons of threads with various combinations / orders of button presses. I can tell you based on you description that you are using the wrong one for Odin. Please use the search function in the forum to find the thread(s) you are looking for.
Also I have to nitpick here. The term bricked means it's literally a brick. Unable to fix, it might as well function as a paperweight now.
I can SORTA stand when people say soft bricked, because you can actually fix it. But "Super soft bricked" is a bit over the top to me.
There is a good chance you are NOT in fact bricked at all.

not an idiot
1) apologies for putting this in the wrong area.
2) i know how to use Odin, and what button combo to use.
3) I realize "bricked" means unusable / beyond repair
a) the phone appears to not have a working copy of Android on it at all.​
4) Impatience sucks. Time to go fool around with the SDK....

Samsung Galaxy Note 5, i need help ASAP.

This all started when i accidentally deleted a text message that i needed, i did a search on google how to recover a text message. I downloaded some software that was recommended on a reputable site, i scanned the file with Kaspersky etc and it was fine.
The software was pretty straight forward to use, you basically needed to go into developer mode to enable debugging which was easy enough and the software did the rest, it said on the site that rooting wasn't needed.
Anyway, it didn't recover the text message. After i disconnected my Note 5 from the PC i had this Security notification warning coming up which says "Unauthorised actions have been detected, restart your device", i've done that several times and nothing happens. I've tried going into the phone updates but it won't even allow me to connect to the update servers as i get a message which says
"The operating system on your device has been modified in an unathorised way. Try downloading software updates using Smart Switch on your PC or visit a customer service centre".
I've tried doing updates via Smart Switch but i can't even check if i'm upto date or not, i tried a hard reset via the home button, volume up switch and the power button but that hasn't done anything. The phone seems to function normally but it has this constant security notification being displayed.
I've tried going into the download mode to check the knox counter but a big yellow triangle comes up first with an exclamation mark inside it with a white android man underneath and it says under that "No Command , it pauses for a while then the boot and reset option list eventually appears, it's got yellow writing above the list saying Android Recovery but nowhere does it say the knox counter.
Before the above this is a UAE Note5 that is standard and hasn't been rooted, it's a stock phone.
Any ideas as to what i can try or do next ?

Do you have a link to this software you used?

One was called FonePaw, that didn't work so the one that i tried after seem to give me all these issues, that one was called Dr.Fone Toolkit for Android, version 8.3.3.64
It wouldn't let me post a link saying something about me being a new member.

This is the strange thing, ive been into the download screen a few times via the home/volume up and power button. Where normally you get a nice neat list with the actions you can do, their was a lot of yellow text at the top left, the actual list was underneath all that yellow text, it didn't have the Knox line where it usually is. I then downloaded PhoneInfo *Samsung* and that gave me a lot of info, it said the Knox was 0x0

Download mode screen says:
Odin Mode
Download Speed: FAST
Product Name: SM-N920C
CA_ TYPE: CA_2
Current Binary: Samsung Official
System Status: Custom
FRP Lock: ON
Secure Download: ENABLED
Knox Warranty Void: 0 (0x0000)
RP SWREV: B:3 K:0 S:1

Thanks Darren, i've updated the info from the download screen above.

One quick question, i've never flashed a phone before, i've flashed graphics cards etc. Do you need to remove the SIM card ?

Thanks Darren, do you have a link to the latest genuine version of Odin, sorry to be a pain mate, it's just i aint done it before and want to make sure i have the right version lol

TheJoshuaTree said:
One quick question, i've never flashed a phone before, i've flashed graphics cards etc. Do you need to remove the SIM card ?
Click to expand...
Click to collapse
No, you do not need to remove the SIM Card.
Here is a link to Odin 3.12.3 in my OneDrive account...
https://1drv.ms/u/s!AojwsjavMvQdoFsfD1CA-MEZbvr6
Works perfectly and is a stock version of Odin with no modifications.
Sent from my Samsung SM-G955U using XDA Labs

Thanks for all the help.
I flashed the phone in Odin with a stock ROM, the same UAE one that was previously on the phone. Touch Wood everything seems to be working fine with no error messages.

All sorted.....

help guys my note 9 knox applied !

why my device shows remote configuration of your device and applying know After update !:crying:

Ok take a breath. What did you do and what makes you think Knox tripped?

Warranty void 0x1 FFRP lock info and options!

I've ran into this problem twice now either using .img to .tar tool that isn't set up properly with an incompatable version of stock rom or a corrupt dump of a stock rom or even using a proper stock rom. Or if you just so happen to accidently turn off O..E.M unlock... and your phone died or you restarted it.... Download mode spits out some red code usually or fails or even can complete but not in any case I've ever seen and boot sucessfully.... usually if you try to many times with odin you'll end up with a blue screen that comes up stating something went wrong during update process and to use Samsung's smart switch program on a pc. Only problem is at this point you've already tripped Knox and your warranty is now void so downloading smart switch and typing in your serial and one I will only give you another error stating that your phone is not comparable with smart switch due to Knox being tripped at 0x1......
At that point there are a couple options claim insurance if you have it, $200 or if you don't have insurance. Samsung will give you a spill about how your 1yr warranty is over and even if it isn't when they get your phone they will see your Knox status of 0x1 and tell you sorry your warranty is void due to end user tampering. So they offer a reflash for a cool $80 without warranty and that will reset your phone back to O.E.M specs with a Knox of 0x0 fix it for a mere $80. Smartswitch won't reflash firmware do to Knox being tripped. Sorry. You are more than welcome to try....*
COLOR="red"]NEVER, I REPEAT, NEVER TURN OFF O.E.M. UNLOCK UNDER ANY CIRCUMSTANCES IF YOU HAVE ROOTED YOUR PHONE, OR PUT A CUSTOM KERNEL OR FLASH A CUSTOM RECOVERY OR YOUR FAIL TO BOOT.[/COLOR]If you turned off O.E.M unlocking. Basically O.E.M unlocking is telling your phone it's okay that Knox is tripped. O.E.M unlock allows the skipping verified samsung signature checks on the first rom based bootloade rduring the boot sequence alowing it to bypass into the secondary bootloader and kernel.*
O.E.M. stands for "Original Equipment Manafacturer" i.e. being Samsung in this case so when you have not done anything to your phone when it comes brand new out of the package. Developer mode is hidden and unacessable for a reason.... O.E.M unlock means that in download mode you can flash unofficial code, i.e. C.W.M., TWRP, Other unsigned code from various developers. With no hassle due to Samsung being so kind to us developers and allowing us the option to manually unlock our bootloaders.*
Usually what happens specifically is Samsung has a secure bootloader which uses digital certificates to ensure that the software loaded before the operating system is trusted to boot the linux kernel shell we all know and love as android OS when you load a custom bootloader such as anything not signed by Samsung it fails to pass the signature checks and that's exactly what turning off O.E.M unlock did.*
But with us all being blessed with the option to manually unlock our Bootloaders through O.E.M unlock now so many options are open to us so as but not limited to.: Roms, MODS, Hacks, Busybox, Root, Xposed, Various Root Applications, Magisk, Kingoroot, GeoHots stuff, HashCodes stuff, even have the oppourtunity to create and test various of our own creations.*
Once upon a time Bootloaders were locked, meaning, No Roms, No kernels, etc, etc... Very, Very difficult to even root phone's. The reason I go into all of that is Because with great power comes great responsibility. Always back up your eds partition, and always always if you root and like to run custom rom Roms and all the development for this scene that only continues to grow and evolve Make sure you do one thing if nothing else and that is to read, read, read and know your phone inside and out. I am a developer and I work with software as much as I do hardware. I can afford to make mistakes as these aren't my daily drivers. I suggest if you like to unlock the full potential of your devices then please heed my warning about reading and knowing all the dos and dont's for what your devices is capable of and what will turn it into a very expensive paper weight. I'm not being a **** I'm trying to help. Because you have now tripped your Knox counter meaning it is permanently stuck in the state of your phone now having a void warranty and there is no going back.*
Once you turn O.E.M mode off you lock your bootloader and if you've already tripped Knox you can't flash a stock bootloader or Rom because your phone's hardware is preventing anything unauthorized from making it past the kernel checks..... clear some things up for You? I don't care the people say they have work around forCOLOR="red"]"custom binary frp lock"[/COLOR]because I have yet to see a phone recover. P.S. word to the wise that is one error you never, and I mean never want to see on your boot screen...
I came back from it once with a zeroed out serial number and a null one I. Once and that's a whole nother ball of wax. Claim warranty, play stupid if still covered if not Sammy will know so just shell out the $80 send it to them. They will reflash it and that's the end of that.

Really weird situation with SM-N960F

Hi
I just bought a 2nd handed phone from my friend and all of the samsung apps said my phone has been rooted.
I'm quite sure my phone is not rooted and Knox still stay at 0x0
I have gone to samsung warranty service and know that this phone has broken the contract with some kind of 3rd party certified reseller, for that reason it will cause my phone to void the warranty and the phone will keep in rooted state.
Is anyone have any idea about this?
Thanks

romi1996 said:
Hi
I just bought a 2nd handed phone from my friend and all of the samsung apps said my phone has been rooted.
I'm quite sure my phone is not rooted and Knox still stay at 0x0
I have gone to samsung warranty service and know that this phone has broken the contract with some kind of 3rd party certified reseller, for that reason it will cause my phone to void the warranty and the phone will keep in rooted state.
Is anyone have any idea about this?
Thanks
Click to expand...
Click to collapse
probably was rooted. go to dl mode and check "warranty:

romi1996 said:
Hi
I just bought a 2nd handed phone from my friend and all of the samsung apps said my phone has been rooted.
I'm quite sure my phone is not rooted and Knox still stay at 0x0
I have gone to samsung warranty service and know that this phone has broken the contract with some kind of 3rd party certified reseller, for that reason it will cause my phone to void the warranty and the phone will keep in rooted state.
Is anyone have any idea about this?
Thanks
Click to expand...
Click to collapse
Are you using an app to check if Knox is 0x0 ? Apps are telling me Knox is not tripped, when it is! Best way to check is go into download mode, check via there!

bober10113 said:
probably was rooted. go to dl mode and check "warranty:
Click to expand...
Click to collapse
N1NJATH3ORY said:
Are you using an app to check if Knox is 0x0 ? Apps are telling me Knox is not tripped, when it is! Best way to check is go into download mode, check via there!
Click to expand...
Click to collapse
I have reached Download Mode as you guys have asked and noticed some lines like this, take a look
Current BINARY : Samsung Official
KG STATE: CHECKING
FRP LOCK: OFF
OEM LOCK: OFF
WARRANTY VOID: 0 (0x0000)

romi1996 said:
I have reached Download Mode as you guys have asked and noticed some lines like this, take a look
Current BINARY : Samsung Official
KG STATE: CHECKING
FRP LOCK: OFF
OEM LOCK: OFF
WARRANTY VOID: 0 (0x0000)
Click to expand...
Click to collapse
looks good then.
maybe you should just reset phone. go to recovery mode and wipe cache a data maybe?
im at a loss

bober10113 said:
looks good then.
maybe you should just reset phone. go to recovery mode and wipe cache a data maybe?
im at a loss
Click to expand...
Click to collapse
I did try soft restore in phone setting except recovery one but no luck, maybe recovery mode and wipe everything should do the trick I think.
I heard they have mentioned something like F.nox (Similar to locked carrier phone contract) that caused all of this.
More confusing, this phone somehow broke out the contract with "F.nox" and work like global except Knox involved Samsung apps.

romi1996 said:
I did try soft restore in phone setting except recovery one but no luck, maybe recovery mode and wipe everything should do the trick I think.
I heard they have mentioned something like F.nox (Similar to locked carrier phone contract) that caused all of this.
More confusing, this phone somehow broke out the contract with "F.nox" and work like global except Knox involved Samsung apps.
Click to expand...
Click to collapse
oh if it was a rental?
maybe but again try a reset in recovery if you can't then yeah maybe its the mdm that the rental company activated that is causing this
edit:
maybe it jsut needs a good old fashion reflash of stock firmware via odin

bober10113 said:
oh if it was a rental?
maybe but again try a reset in recovery if you can't then yeah maybe its the mdm that the rental company activated that is causing this
edit:
maybe it jsut needs a good old fashion reflash of stock firmware via odin
Click to expand...
Click to collapse
I have quite some baddddddddd memories with odin but maybe yeah I should think about that solution too.
EDIT : Last time I flashed my note 2 with it. It blown my imei and baseband away

romi1996 said:
I have quite some baddddddddd memories with odin but maybe yeah I should think about that solution too.
EDIT : Last time I flashed my note 2 with it. It blown my imei and baseband away
Click to expand...
Click to collapse
sounds like modem issue.
but regardless, ive not herd of such issues lately.
anyways ill let you decide.
a good way to get non corrupt firmware is to use samfirm tool 0.3.6 just enter phone model: SM-N960F
and your region code.
when using odin 3.13.1
fill all slots but for csc use regular csc.md5 not the one with home.

bober10113 said:
sounds like modem issue.
but regardless, ive not herd of such issues lately.
anyways ill let you decide.
a good way to get non corrupt firmware is to use samfirm tool 0.3.6 just enter phone model: SM-N960F
and your region code.
when using odin 3.13.1
fill all slots but for csc use regular csc.md5 not the one with home.
Click to expand...
Click to collapse
Thanks, I'll try it out later, currently, I'm trying to test if the recovery mode work or not. I hope it work.

Possible that the device had a bad IMEI/ESN and was a new CERT file was created to allow network access.