Database Users

Need help on unfamiliar error screen. Image provided.

Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
UPDATE <21_03_2015><16_54_09_524>____________________________________________________________
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit

I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.

3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app

Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?

intervall said:
I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.
Click to expand...
Click to collapse
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
st3chn0 said:
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
3XTR3M1ST said:
Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?
Click to expand...
Click to collapse
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.

1. If its possible for him to return to the seller then yes but he can't to samsung. Due to knox being tripped. If he does its just basically a 50/50 chance
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
3. Using odin to flash any official firmware. Is not bad advice.
Sent from my SM-N9005 using XDA Free mobile app

celderic said:
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.
Click to expand...
Click to collapse
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/

Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone

st3chn0 said:
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
Click to expand...
Click to collapse
This is a softbrick, if the hardware is fine then you should be able to fix it in 10mins by flashing a stock rom, but as the seller has sold it in this state then i assume it is softbricked for a reason so you can't test the device for example.
cryostasis25 said:
Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone
Click to expand...
Click to collapse
But his knox is already tripped.. he bought a phone with knox 0x1 that's why i suggested returning it.
3XTR3M1ST said:
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/
Click to expand...
Click to collapse
If the seller is not responding, then it points to them tampering with the device before selling it. Where did you buy it from, i would ring your bank as soon as possible.
Download the latest n9005 rom from sammobile and flash it through odin if you want to try and fix it, shouldn't really matter what csc as your knox is already tripped anyway so you can't recieve OTA updates or warranty from samsung anymore, mine is a BTU device but i have used many XEO roms.
If the phone isn't connecting to the computer properly like you say, then it's probably best to leave it. As this could result in the connection failing when it is flashing the bootloader or something. But if it works fine, then there should be no problems.
Here is something you could try, start up odin (i use v3.09), close all processes relating to kies, boot the device into download mode, that screen you provided pictures of. Plug the phone in and wait a few minutes to check the connection is stable, move the cable around to make sure the socket and cable are okay. You will see it come up on the top left in odin after windows has installed the drivers.
If this all works fine then flashing a stock rom should fix the device if the hardware is okay.

Just a quick question. From what site did you buy the phone and how did you pay for the phone?
Sent from my SM-N9005 using XDA Free mobile app

Where is a reliable source to download the official firmwares? I cant find it on the samsung site.
Tried http://www.samsungupdate.com/how-to/download-firmware but the file sizes are different on either filehost mirrors and it seems shady.

www.sammobile.com/firmwares/

I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit

3XTR3M1ST said:
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Click to expand...
Click to collapse
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.

sirobelec said:
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.
Click to expand...
Click to collapse
Thanks for the suggestion. I'll give it a try after a little more research.
I have no idea what the phone was before, or what the seller did to it since he's just not responding anymore.

So I tried flashing the new bootloader as suggested, it seem to have worked to some extent, but then I screw it up again by pulling out the cable before seeing "PASS!". What now?
http://forum.xda-developers.com/showpost.php?p=59616074&postcount=16 said:
iketil said:
Hi the file size should be 58 041 KB
From what I can see from you ODIN log, ODIN has "done its thing"
If you did not uncheck the auto reboot tab, the phone should now be rebooting.
And bootloader and Modem should be updated when its booted up.
Are you still stuck at the "Samsung GALAXY Note3 SM-9005" screen ?
Click to expand...
Click to collapse
I'm still stuck on the "Samsung GALAXY Note3 SM-9005" screen. However I do think that the "hlte_lollipop_bootloader_modem.tar.md5" has "done its thing". I was previously unable to get to the recovery, but I was able to get to this <3e>recovery after flashing.
Also managed to see some logs of "i'm not sure what it is" before the phone went blank. I presume its due to battery going flat.
Later, I tried putting TWRP on it. Starting with "twrp-2.8.3.0-hlte-4.3.img.tar". But being a novice odin user I mistakenly unpluged the phone when odin is showing "RESET!". Then I tried going into recovery using VOLUP+HOME+POWER, and got this screen instead. I'm not sure if removing the phone before "PASS!" in odin could have caused this? Subsequently I tried flashing "twrp-2.7.0.3-hlte-4.3.img.tar" and
"twrp-2.7.2.0-hlte-4.3.img.tar", which resulted in the same error screen about SEANDROID.
I also noticed it increased my KNOX counter?
This is before and after.
Next I tried flashing ""hlte_lollipop_bootloader_modem.tar.md5" again hoping it would fix it. It didnt work. Silly me, this flash does not have a recovery image in it does it?
Anyway, now I dont have a working recover and is still stuck on the "Samsung GALAXY Note3 SM-9005". Thankfully odin mode still work. What should I do next? Please see this thread below for a little background to my problem. Thank you.
http://forum.xda-developers.com/galaxy-note-3/general/help-unfamiliar-error-screen-image-t3059227
Click to expand...
Click to collapse

HORRY SHET!!
I think my phone is asian! I just flashed the latest taiwan firmware released (N9005ZSUGOC3_N9005OZSGOC3_BRI) after flashing the new bootloader and everything works now!
I'm not sure what actually made it work since this is the first taiwan firmware I tried (its all XEO and BOB previously), but big thanks to everyone who helped!

(Help) Note 4 bricked, unable to mount data

Hi guys, i have some big problems with my n910f, tried to upload a pic to facebook and my phone crashed.
It simply does nothing, not booting, not charging, download and stock recovery are working.
I tried everything possible>
*flashed 3 different stock firmwares with odin
*tried a pit file repartion in odin
*wiped cache, did a few factory resets from stock revovery
*bought a new battery
*tried to root and flash a custom recovery but doesnt work
It is simply as bricked as it could be, the only information about this i have is stock recovery telling me unable to mount /data
So it seems my filesystem got corrupted as hell
The question is, how do i repair it?
Like i said pit file and bootloader flash did nothing, odin lets me flash everything without an error but it doesnt help.
I assume i could somehow repair it with adb fastboot but how?
Any help is welcome!

atilla88 said:
Hi guys,
Any help is welcome!
Click to expand...
Click to collapse
It may or may not help but I would sure try Kies. You NSFW get done errors like Kies telling you is not compatible bit but I would try the firmware initialization.

CodeNameRedNeck said:
It may or may not help but I would sure try Kies. You NSFW get done errors like Kies telling you is not compatible bit but I would try the firmware initialization.
Click to expand...
Click to collapse
Well i forgot to mention that i tried kies aswell, everyhting went good but didnt help, still nothing.
It confuses me a bit that it doesnt even charge, could a broken filesystem lead to this?

atilla88 said:
Well i forgot to mention
Click to expand...
Click to collapse
I am not sure what parts of the system need to be working for the battery to be able to charge. Good luck.

CodeNameRedNeck said:
I am not sure what parts of the system need to be working for the battery to be able to charge. Good luck.
Click to expand...
Click to collapse
did try root=> costum recovery for your variant => installing costum roms for your variant (all can be done with odin +sd card and some fils on it) but warranty is lost it may worth the try
did you try the 5 flashing fils(pit pda bl csc phone) to initial stocks with odin

ZOHUHRZED said:
did try root=> costum recovery for your variant => installing costum roms for your variant (all can be done with odin +sd card and some fils on it) but warranty is lost it may worth the try
did you try the 5 flashing fils(pit pda bl csc phone) to initial stocks with odin
Click to expand...
Click to collapse
i have the same problem, do you know where can we find the complete 5 files (pit pda bl csc phone) for flashing with odin?
its the only thing i haven't already tried.

I manage to fix the issue with storage partition, i used a pit file and the one file firmware in csc button, that made the hole data partition rewriten again so the phone is able to boot properly.
Hope you gays this may help.
Happy new year!!

heratis said:
I manage to fix the issue with storage partition, i used a pit file and the one file firmware in csc button, that made the hole data partition rewriten again so the phone is able to boot properly.
Hope you gays this may help.
Happy new year!!
Click to expand...
Click to collapse
What makes you assume we're all gay?

Sorry pal, i better watch my grammar, i ment guys.

SM-N910F HARD brick! Desperate and running out of ideas..?!

Hi guys!
I would just like to start by apologizing for making another thread about a bricked note4, however I have read about so much I don't know which advice to go with anymore. I'm also a complete novice when it comes to this.
So long story short, my note 4 started playing up and lagging, eventually not turning back on at all. After endless attempts using odin and flashing what I seemed to have thought was the right firmware, it whittled down to about 1 in 5 attempts of trying to enter download mode (using the buttons) on the phone actually working. Now its completely bricked...no power, no download mode, nothing!
Just like to reiterate, I'm a complete novice,sorry if I'm not making sense, my knowledge doesn't go further than articles and google!
I have tried using kies to recover my phone and it cant recognize it...
I have read about using adb to get my phone into download mode, but I couldn't understand the explanation given well enough to use it...
I bought a 16gb micro sd card and have tried writing an unbrick image to it but I get no response off my phone, also tried another file, possibly sdc? cdc? cant quite remember, but that failed too.
I don't even know if the files I'm using are correct, I got them from a forum on here.
I'm at a loss!
The only hope I have left is if someone is able tell me if any steps I have tried are correct, and possibly provide me with the correct unbrick image?
Also, when I plug my phone into my computer via usb, there is a noise that sounds but nothing else happens, don't know if these means anything. As far as I'm aware I also have correct drivers installed.
Sorry about the long explanation!
Any help is greatly appreciated!
Thanks in advance.
Lucy.

Only logical result from your explanation is you have a hardware problem.
I dont think you are gonna be able to solve it with software...
Time for service visit i guess..

Turkawa said:
Only logical result from your explanation is you have a hardware problem.
I dont think you are gonna be able to solve it with software...
Time for service visit i guess..
Click to expand...
Click to collapse
Thanks for the reply!
I hope that's not the case forgot to mention,when I plug my phone into a computer and go into device manager, it shows qhsusb_bulk...if this means anything to you?

Lucyhenn123 said:
Thanks for the reply!
I hope that's not the case forgot to mention,when I plug my phone into a computer and go into device manager, it shows qhsusb_bulk...if this means anything to you?
Click to expand...
Click to collapse
Nope.. I have no idea.. Sorry

Try the sd recovery method .
First you can try to flash the pit partion .
You can find that on xda .
Just search for note 4 pit files.
Download the n910f pit file with correct csc.
TRY flashing via download mode.
Try flashing .
Use this guide for using sd card to get into download mode if you cant access download mode
There is a method for http://cloud.tapatalk.com/s/57e756f41dc6e/read me for brick fix.txt
Reporting via N910G

Bricked my phone trying to learn

Well the title says it all. Made a similar post in that wrong area I believe. That's probably why I didn't get a response.
Anyway, I had 6.0 but had downgraded to 5.0 and my build is SM-G870AUCUBF03. I tried to apply a stock kernel, G870A_NE4_Stock_Kernel.tar.md5, more specifically and it appears to be soft-bricked.
It shows the Samsung splash then after awhile going into recovery mode. I can still access Download mode as well. I tried hard-resetting, wiping data/factory settings. Any help would be very much appreciated. Thanks for taking the time to read this.

You could try the restore firmware function in Kies. It will be the easiest way to get back a working phone

I'm trying that right now, but it is saying that the connected device is not supported.

Can't find 5.0 stock firmware or anything really that leads me to believe that I can recover this phone. I can't believe this.

bfletxh said:
Can't find 5.0 stock firmware or anything really that leads me to believe that I can recover this phone. I can't believe this.
Click to expand...
Click to collapse
Read here.
https://www.sammobile.com/forum/showthread.php?t=30248
First Google search.
https://www.sammobile.com/firmwares/galaxy-s5-active/SM-G870A/
I'd suggest staying away from KIES and using Odin instead. In fact if you use Odin, and you have KIES installed on the same PC, disable it first. When all else fails, Odin is your friend. Just read up on the steps for using Odin if you're unfamiliar with it. And make sure you have the right firmware.
Sent from my Samsung SM-G900I using XDA Labs

Note 3 Factory Data Reset Daily -

Ok - haven't seen this problem anywhere - all I see are posts and articles regarding how to get it off the Samsung screen during boot... Which is a Factory Data Reset... I have to FDR my phone daily.. not running anything custom (accept this was originally a Rent-A-Center phone - and I know they have a special system built in to kill the phone if its not paid for etc... Was paid off well over a year ago)
How do I fix this?? Do I have to root and install a custom ROM?? Do I have to do something else? Having to FDR every day, and sometimes twice is becoming rather annoying.

Flash your models stock rom through Odin .

JJEgan said:
Flash your models stock rom through Odin .
Click to expand...
Click to collapse
Do I have to use KIES for that, or is there a better way to do it? I have not flashed anything before... I know it is a little different than installing an OS on a computer.

AncientNerd said:
Do I have to use KIES for that, or is there a better way to do it? I have not flashed anything before... I know it is a little different than installing an OS on a computer.
Click to expand...
Click to collapse
Nope, you just download Odin (PC software) and download stock firmware (search in Sammobile or Updato) and look for a tutorial on how to flash software through Odin and you're all set

ShaDisNX255 said:
Nope, you just download Odin (PC software) and download stock firmware (search in Sammobile or Updato) and look for a tutorial on how to flash software through Odin and you're all set
Click to expand...
Click to collapse
Awesome - Thanks!

ShaDisNX255 said:
Nope, you just download Odin (PC software) and download stock firmware (search in Sammobile or Updato) and look for a tutorial on how to flash software through Odin and you're all set
Click to expand...
Click to collapse
Ok - Update..
I have searched both Updato and Sammobile - nothing but European and otherwise non-USA Firmware - I also cannot get Odin - or frankly Kies to work either... Kies does not find the device, and Odin acts like it is there, but nothing I put in it is working..
CWM Recovery? Nada... Doesnt do anything through Odin - just stares at me -
ADB and FB? They briefly flash on my PC screen and vanish - no options to do anything... I have updated the Samsung USB drivers 4 times... So I am not sure what to do next..
Thanks for the help so far!

AncientNerd said:
Ok - Update..
I have searched both Updato and Sammobile - nothing but European and otherwise non-USA Firmware - I also cannot get Odin - or frankly Kies to work either... Kies does not find the device, and Odin acts like it is there, but nothing I put in it is working..
CWM Recovery? Nada... Doesnt do anything through Odin - just stares at me -
ADB and FB? They briefly flash on my PC screen and vanish - no options to do anything... I have updated the Samsung USB drivers 4 times... So I am not sure what to do next..
Thanks for the help so far!
Click to expand...
Click to collapse
What's your phone's model? It doesn't have to be carrier-specific to be able to flash it.
Also, try TWRP instead of CWM recovery, devs seem to prefer TWRP overall.

SM-N900T is the model number.. I'll give TWRP a shot next. Maybe I'll have better luck with it.
Could the RAC software be putting a wall up that I can't get through? I bricked a phone I was getting through them once because I tried to update Android through Kies (on an S5) and discovered they don't use stock ROM's with their phones.

AncientNerd said:
SM-N900T is the model number.. I'll give TWRP a shot next. Maybe I'll have better luck with it.
Could the RAC software be putting a wall up that I can't get through? I bricked a phone I was getting through them once because I tried to update Android through Kies (on an S5) and discovered they don't use stock ROM's with their phones.
Click to expand...
Click to collapse
I've got a N900T and I've found software in both Sammobile and Updato, I don't know why you're not finding anything (N900T is supposed to be T-Mobile's variant)
Anyway, I would try out the following tutorial: Link
I found it very useful when I wanted to completely flash my phone clean and root.
I am not sure about what roadblocks you could have of this phone being a RAC phone, but if you still want to give it a try I'd suggest you try out the tutorial I showed you