Database Users

[Q] Odin Error

i used the exe og legija to recover my i9505 so i can boot in download mode but
when i install an official firmware with pit thru odin after the flash is pass success the i9505 is dead again ...
any idea?? In the phone when start flashing is appear 3 lines in red saying:
START [240,1440]
BAR [240,1440]
END [240,1440]
any help plz thx

You are in the wrong forum. This one is for the S4 Active and its European counterpart. Sounds like you have a regular S4 as we cannot yet flash ROMs on our S4 Active phones.

No , you're in the wrong forum dude
Sent from my GT-I9505 using XDA Premium HD app

Miami_Son said:
You are in the wrong forum. This one is for the S4 Active and its European counterpart. Sounds like you have a regular S4 as we cannot yet flash ROMs on our S4 Active phones.
Click to expand...
Click to collapse
I'm pretty sure this is the regular S4 section
Sent from my Googley Sammy Jellybean

tatperson said:
I'm pretty sure this is the regular S4 section
Sent from my Googley Sammy Jellybean
Click to expand...
Click to collapse
It is, now that a mod moved the thread.

yes is an european s4 i9505
yes i am from spain this s4 i9505 is european version, from vodafone, in odin when i start download mode it says wrie protection enable and when flashing it sen the messages i say above. i use the pit and the stock fw, in odin it says it pass and all succesfull but when i try to power the phone it dont boot, and goes in qualcom mode. also when i enter in download mode at star says phone coud not do normal bot in red, like that:
could not do normal boot
odin mode
product name : i9505
Current binary sumsung oficial
System status: Custom
CSB-OEM_CONFIG _FILES_SYS: 0x30
write protection : enable

We need to know exactly what you've done to the phone in the order you've done it - firmware which was originally on the phone, any OTA updates, exactly what you flashed/in what order, what happened to the phone that made you need to Odin flash it.
Little details will be important so far as getting your phone up & running as soon as possible goes, I.E the less details you give the longer it's going to take for that to happen

MistahBungle said:
We need to know exactly what you've done to the phone in the order you've done it - firmware which was originally on the phone, any OTA updates, exactly what you flashed/in what order, what happened to the phone that made you need to Odin flash it.
Little details will be important so far as getting your phone up & running as soon as possible goes, I.E the less details you give the longer it's going to take for that to happen
Click to expand...
Click to collapse
hi, is a friend phone, he flashes with odin to install 4.3 custom(i don't know what custom he use) it fails and he brick the phone, can't no enter in recovery and can't enter in download mode, also the phone no power on, when he let me the phone for repair. Know i can enter in download mode.
First of all i try to flash a new rom custom but it says no pit partition. Then i download from sammobile a stock rom of vodafone and the pit file for the S4 i9505, i flash it with pit and the stock official rom of the terminal (re-partition mark,f.reset time mark, and autoreebot mark). Odin end and say pass. but when i try to power on the phone go again into a brick (phone, can't no enter in recovery and can't enter in download mode, also the phone no power on). i use odin 3.07 , 3.09 and 1.85 i got this versions and i try some configurations like unmark re-partition,and unmark autoreboot with the same problem. (He turn un qualcome mode). i also try to install a new recovery and the same syntoms. also when i flash any thing the phone goes to the same status all ok but no power on, no recovery and no download mode.

any ideas???

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!

Hard Bricked Galaxy S4

Hey,
I've been trying to install Exposed Framework on my Galaxy S4 and managed to brick it, hard. Can't run recovery mode, download mode, it doesn't connect to my computer and when I try to start it up all it says is Start Up Failed, Device didn't start up successfully. Use Verizon Software Repair Assistant to repair it, but I don't have that nor can I find it anywhere online. I'm by no means technologically illiterate. Is there any way that someone could help?

Nevermind I ended up fixing it, ran a program through Odin that for whatever reason worked and phone is fixed.

Facing same problem here. I cannot get the recovery mode. Not rooted the S4 yet. What did you install through Odin to get through this? Thanks.

Silentspeech said:
Facing same problem here. I cannot get the recovery mode. Not rooted the S4 yet. What did you install through Odin to get through this? Thanks.
Click to expand...
Click to collapse
no, you go download mode and open odin as admin after you flash the stock firmware from sammobile.

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

I think my s7 edge SM-G935F its now just a brick...

I wanted to update my s7 edge to oreo via odin. So, i think i just flash it bad (instead of put one archive in bl i put other in ap, idk things like that). so i saw it told me An error has occurred while updating the device
software. Use the emergency recovery function in Smart Switch. I tried flashing again the firmware in odin but it just stuck in initialization. I just tried in diferent version of odin nor switch mode.
I tried with diferent usb cable nor other usb port
When i try to recover it with switch mode it just tell that it cant because it isn´t compatible (I even put the s/n)
Could someone tell a alternative tool to odin?
Help please, i think im losing my s7
Btw, sorry for my bad english.

Don't worry it will be fixed restart using volume down-home-power buttons all together go back in odin mode and try to flash only AP

Yo ur English is fine.
What version is your phone?
What version firmware are you using? Where did you get it ?
What version of Odin?
There are only 2 ways.
Odin or OTA by your provider.
Lol i don't think the change to Oreo is worth this trouble. But since you're going down this rabbit hole, we can at least try to get you working phone in Oreo.

Eggleston11 said:
Yo ur English is fine.
What version is your phone?
What version firmware are you using? Where did you get it ?
What version of Odin?
There are only 2 ways.
Odin or OTA by your provider.
Lol i don't think the change to Oreo is worth this trouble. But since you're going down this rabbit hole, we can at least try to get you working phone in Oreo.
Click to expand...
Click to collapse
SM-G935F
I was at 7.1 version before i changed(it was already rooted). During i was flashing my phone, i was tryng to change to oreo´(8.0 Panama)
From sam firm(a program who download from sammobile)
The last one. Also i try with preview version.
I use odin and it just stuck in initialization

miguelpty2702 said:
SM-G935F
I was at 7.1 version before i changed(it was already rooted). During i was flashing my phone, i was tryng to change to oreo´(8.0 Panama)
From sam firm(a program who download from sammobile)
The last one. Also i try with preview version.
I use odin and it just stuck in initialization
Click to expand...
Click to collapse
Don't know about samfirm. Sam mobile download is pretty safe and good. Download again in case of corrupt download if you want to reuse your firmware. Ensure that your firmware is for G935F. Boot to download mode. Unzip the zip file and get md5. Put md5 firmware on Odin (latest version) in AP section. Plug phone to computer. Make sure it says "added". Then start process.
Below link will help.
https://www.kingoapp.com/root-tutorials/how-to-flash-samsung-stock-rom-via-odin.htm
Should work flawlessly. Let me know if this doesn't help. Sorry if it's too simple of an explanation. Would rather have you understand than not.

Eggleston11 said:
Don't know about samfirm. Sam mobile download is pretty safe and good. Download again in case of corrupt download if you want to reuse your firmware. Ensure that your firmware is for G935F. Boot to download mode. Unzip the zip file and get md5. Put md5 firmware on Odin (latest version) in AP section. Plug phone to computer. Make sure it says "added". Then start process.
Below link will help.
https://www.kingoapp.com/root-tutorials/how-to-flash-samsung-stock-rom-via-odin.htm
Should work flawlessly. Let me know if this doesn't help. Sorry if it's too simple of an explanation. Would rather have you understand than not.
Click to expand...
Click to collapse
The bad was just the corrupted archive from samfirm, i think
Oh, thanks man, it worked!
I thought i had losed man
really thankssss

Pls help me
Hello, everyone. I have a SM-G935F Galaxy s7 Edge. usb gate was broken and i started to change the software with odin. it was installed in half and I pushed the usb cable by mistake and the installation stopped. then a error appears on the screen: an error occurrd while updating the device software. i read a lot in the forums and i watched a lot of videos how to fix it but everywhere they describe and show that the phone needs to be restarted with the combination of buttons. my problem is that when i connect my phone to pc it says error: device is not recognized. I checked how to fix this error too, although I managed to fix the device manager in windows , the smart switch still does not detect the phone and the phone cannot restart with a combination of buttons. this phone is very expensive and i want to fix it at any cost. the phone is already with a new usb port, all you have to do is help me put the software on it. please help me very much.
---------- Post added at 12:08 AM ---------- Previous post was at 12:00 AM ----------
device currently stay off because not battery power. When I connect to charging cable phone is starting on blue screen with same error and not possible to off or restart the phone with buttons. Very strange

Try This : if not working you can check the guide how to here but you need to select the right one from here