Database Users

[Q] Odin Keeps Failing

Hello. I have been searching for hours like a mad man on Google for a solution to my problem, but i'm having no luck. Excuse the nooby nature of this post please. So I rooted my Galaxy S4 and I am trying to get it back to stock by flashing the AT&T md5 onto my phone (Galaxy S4 SGH-I337) through ODIN and it fails every single time. Initially, with ODIN 3.07, it would return something like fail (auth). Then I tried with ODIN 1.85, but that version returns "Complete(Write) operation failed." In addition, I attempted Kies but it too failed (no specific error code), and now the phone wont boot. It says that the firmware upgrade encountered an issue. I am not able to access stock recovery or TWRP because it will automatically go to Download Mode with "Could not do normal boot" in the top left corner if I in any way attempt to access it. I am using the stock cable with USB Debugging enabled. I also tried two different computers, two different cables (one being stock of course), and tried every single usb port on both computers. What went wrong? I will give you my upmost respect if you can solve this. I also am absolutely willing to supply any information you may need. Just ask. (Please don't be bricked. Please don't be bricked)
-With kind regards, Branden.

Let me guess you had the att mf3 firmware and tried retoring by flashing the MDL firmware via odin? You said md5 so I assume mdl? You might at this point still be able to fix it visiting a best buy near you if it has a samsung center. Also att store can reflash mf3.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Click Here throw this thread in the MF3 pile... guys we got another noob here, take a trip to your closest best buy and hope the samsung experience will flash the mf3 update for u

You mention md5, which as febby assumed I'll assume to be mdl, and twrp. Do you have mdl firmware on your phone and did you have twrp installed. Assuming you had twrp you were probably on mdl firmware. If so, I would re-download the firmware and try again. It would help if you could explain where Odin is failing too.

jd1639 said:
You mention md5, which as febby assumed I'll assume to be mdl, and twrp. Do you have mdl firmware on your phone and did you have twrp installed. Assuming you had twrp you were probably on mdl firmware. If so, I would re-download the firmware and try again. It would help if you could explain where Odin is failing too.
Click to expand...
Click to collapse
I never actually got TWRP working. I flashed it through Goo Manger and I was never able access it (It went to download mode with "Could not do normal boot" in the corner). Does this change the type of firmware I was on? In both cases of ODIN, the newer version (3.07) fails immediately after you start the process at around NAND Write start. It returns Fail (auth). In the older version (1.8.5), it reports that the write operation failed. I attached screenshots of both cases.

If you never got twrp to work then I'm almost positive you have mf3 firmware. You're best bet is best buy and have them re-flash the firmware.

Astrophysicist789 said:
I never actually got TWRP working. I flashed it through Goo Manger and I was never able access it (It went to download mode with "Could not do normal boot" in the corner). Does this change the type of firmware I was on? In both cases of ODIN, the newer version (3.07) fails immediately after you start the process at around NAND Write start. It returns Fail (auth). In the older version (1.8.5), it reports that the write operation failed. I attached screenshots of both cases.
Click to expand...
Click to collapse
There is no way to fix your problem currently so like jd1639 said, take it to best buy to the Samsung Experience area and tell them Samsung Kies firmware update fail and it did this to your phone. Thats what I did yesterday, they flashed it and I have my phone working again.

gandes said:
There is no way to fix your problem currently so like jd1639 said, take it to best buy to the Samsung Experience area and tell them Samsung Kies firmware update fail and it did this to your phone. Thats what I did yesterday, they flashed it and I have my phone working again.
Click to expand...
Click to collapse
Okay. I thank everybody for their assistance. You are very helpful people. I will head down to best buy and see what they can do for me.

Astrophysicist789 said:
Okay. I thank everybody for their assistance. You are very helpful people. I will head down to best buy and see what they can do for me.
Click to expand...
Click to collapse
Your welcome

And just so everyone knows...md5 is part of the package name I believe... (.tar.md5) or could be referring to md5 checksum...anyways as was mentioned and you acknowledged, best buy is your best bet
Sent from my SGH-I337 using Tapatalk 4

Hey guys I used oden to flash back to stock amdl and then a att update keep trying ro come threw durring the night I noticed.it downloadwd went into recovery and was on flash update I hit no instead and rebooted now I noticed my baseband changed to amdb . update is back again and I now hit remind me later is this the update witch will lockbootloader
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

ralphie1267 said:
Hey guys I used oden to flash back to stock amdl and then a att update keep trying ro come threw durring the night I noticed.it downloadwd went into recovery and was on flash update I hit no instead and rebooted now I noticed my baseband changed to amdb . update is back again and I now hit remind me later is this the update witch will lockbootloader
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Yeah it is the dreaded one! Root your device and flash a custom ROM or use titanium backup to freeze the update apps.
Sent from my SGH-I337 using Tapatalk 2

[Q] Bricked S5 Exynos Variant....

Hi XDA!!
I am experiencing problems on my Samsung Galaxy S5 Exynos variant (SM-G900H).
It has been soft-bricked. I can clearly say so as it can boot into stock recovery and in download mode, but not in stock 4.4.2.....
It has been bricked due to following the steps mentioned in this thread : s health and xposed
Many videos on youtube ask the viewer to flash stock Samsung Firmware from sammobile.com using odin in download mode.
I have a problem even there.... all versions of odin get stuck on initializing......
Tried on all USB ports.... Kies closed..... basically done everything everybody wrote on XDA.
Any new bright ideas would be appreciated....
Thanks in advance!!:good::good:

skb_twiz said:
It has been soft-bricked. I can clearly say so as it can boot into stock recovery and in download mode,
Click to expand...
Click to collapse
You need to do more reading. A lot more.
You clearly haven't tried everything yet. Nor are you are bricked if you can boot into recovery mode. It sounds like you have messed up the system files preventing a normal boot.
Odin is the most common way of recovering. Use Odin 3.09, ensure that you have disabled anti virus, malware amd firewall software and do not have intensive programs running in the background. If necessary use a different computer.
Flash a full stock firmware, ideally the same version as the current firmware on your phone. But in any event, not an older version and matching your current CSC /carrier /baseband. And you ought to make the effort to find the correct PIT file and flash it at the same time. This insures that you don't have any lingering partition corruption. A forum search will explain all about PIT files. And someone probably has a thread with the actual files too.
It will work. In the worst case, you will just need to find a different PC.
.

fffft said:
You need to do more reading. A lot more.
You clearly haven't tried everything yet. Nor are you are bricked if you can boot into recovery mode. It sounds like you have messed up the system files preventing a normal boot.
Odin is the most common way of recovering. Use Odin 3.09, ensure that you have disabled anti virus, malware amd firewall software and do not have intensive programs running in the background. If necessary use a different computer.
Flash a full stock firmware, ideally the same version as the current firmware on your phone. But in any event, not an older version and matching your current CSC /carrier /baseband. And you ought to make the effort to find the correct PIT file and flash it at the same time. This insures that you don't have any lingering partition corruption. A forum search will explain all about PIT files. And someone probably has a thread with the actual files too.
It will work. In the worst case, you will just need to find a different PC.
.
Click to expand...
Click to collapse
You seriously think that I don't mean it when I said that I had tried everything?? All steps you mentioned have been tried before I read your reply... Anyways, going on a different PC helped... apparently Odin is quite moody.... If it decides it is not going to run on a PC, it simply will get stuck on initialization... hence the solution is to find a PC which has run Odin before... It will work on that PC definitely!!! If you can't find one, try running on all PC's in your vicinity (friend's, family etc). There will be one that can run Odin...
And by the way, I clearly said my phone is "soft-bricked"... It means that I can boot only into recovery or download... not android... so my friend, you are quite wrong in saying that my phone isn't bricked...
Sent from my SM-G900H using XDA Free mobile app

skb_twiz said:
You seriously think that I don't mean it when I said that I had tried everything?? All steps you mentioned have been tried before I read your reply... Anyways, going on a different PC helped... apparently Odin is quite moody.... If it decides it is not going to run on a PC, it simply will get stuck on initialization... hence the solution is to find a PC which has run Odin before... It will work on that PC definitely!!! If you can't find one, try running on all PC's in your vicinity (friend's, family etc). There will be one that can run Odin...
And by the way, I clearly said my phone is "soft-bricked"... It means that I can boot only into recovery or download... not android... so my friend, you are quite wrong in saying that my phone isn't bricked...
Sent from my SM-G900H using XDA Free mobile app
Click to expand...
Click to collapse
Did you try a data factory reset/clear the caches in recovery and reboot and go one from there?

gee2012 said:
Did you try a data factory reset/clear the caches in recovery and reboot and go one from there?
Click to expand...
Click to collapse
Yes... but to no avail... anyways... like I said above, flash the stock firmware in download mode again using Odin... If Odin gets stuck, try it on a different PC...
I will not recommend anyone to do data factory reset as
(1) It won't do anything that helps you
(2) If you don't reset your phone, you can still retain your apps and settings after flashing the stock firmware again!!
<i>LOL, here I am, posting solutions to my own problem!!</i>

same
skb_twiz said:
Yes... but to no avail... anyways... like I said above, flash the stock firmware in download mode again using Odin... If Odin gets stuck, try it on a different PC...
I will not recommend anyone to do data factory reset as
(1) It won't do anything that helps you
(2) If you don't reset your phone, you can still retain your apps and settings after flashing the stock firmware again!!
<i>LOL, here I am, posting solutions to my own problem!!</i>
Click to expand...
Click to collapse
I am an exynos man, and have fewer options and waiting for better prospects OR 6 months of purchase to pass before tinkering. Anyway I appreciate u posting the solutions you found for your own problem. See you have gained a THANKS point from me.

suchiqaz said:
See you have gained a THANKS point from me.
Click to expand...
Click to collapse
I have thanked you for thanking me...
For everyone else, this thread will remain open forever even though my S5 is back up and running...
This thread is now no longer limited to the Exynos variant... All are welcome...
Any problem regarding unbricking any S5 can be discussed here and I will try my best to help you...
Sent from my Reborn GALAXY S5

S5 G900I: Soft Brick or Door Step?

Hi guys,
I bought my wife a G900I, flashed it to CM12 5.0.1 and had it working no problem for a week. 2 days ago after watching a FB video the phone rebooted and has seen been stuck in the Boot Loop. Nothing, even the stock firmware seems to want to install.
Tried the following:
philz_touch_6.26.6-klte.tar.md5
openrecovery-twrp-2.8.4.0-klte
CF-Auto-Root-klte-kltedv-smg900i.tar.md5
CWM recovery
Even PIT: SM-G900I_16Gb.pit
Did full WIPE, CACHE, Re-Format via TWRP
Tried the following Stock Roms:
G900IDVU1ANK1_G900ITEL1ANJ1_G900IDVU1ANJ1_HOME.tar.md5
G900IDVU1AND2_G900ITEL1AND2_G900IDVU1AND2_HOME.tar.md5
G900IDVU1ANK1_G900ITEL1ANJ1_G900IDVU1ANJ1_HOME.tar.md5
G900IDVU1ANK1_G900IVAU1ANJ2_G900IDVU1ANJ1_HOME.tar.md5
After flashing via Odin (tried 2x original cables, 3x Windows PCs)
I get the following Errors (see attached). Sceenshot is from Odin 3.07, but I tried 1.85, 3.07 and 3.09 on 3 different computers with 2x different original cables plugged into USB 2.0 at the back of the motherboard - same results, no matter which Stock ROM I choose.
Whats interesting, is that after a few boot loops, you get a Samsung Logo and a sound, but only intermittently. One time it even managed booting into the new 4.2.2 Stock Setup Wizard, but within a second the phone just reboots and keeps boot-looping.
I'm running out of ideas and I thing I tried everything possible.
Any ideas?

1) have you tried Kies?
2) are your firewall and anti virus turned off on the PCs?
3) XP, Vista and 7 have a better track record with Odin than 8.
4) have you tried EVERY USB port with EVERY PC (it *can* make a difference)
5) are you running Odin as an administrator?
6) leave the .pit files well alone for now. If a pit flash goes wrong, you have a totally unrecoverable brick.
Sent from my rooted Kn0x0 SM-G900F S5

keithross39 said:
1) have you tried Kies?
2) are your firewall and anti virus turned off on the PCs?
3) XP, Vista and 7 have a better track record with Odin than 8.
4) have you tried EVERY USB port with EVERY PC (it *can* make a difference)
5) are you running Odin as an administrator?
6) leave the .pit files well alone for now. If a pit flash goes wrong, you have a totally unrecoverable brick.
Sent from my rooted Kn0x0 SM-G900F S5
Click to expand...
Click to collapse
Hey keithross39,
1) Yes, I have tried Kies. Updated to latest version. It stays on "Connecting" - I can only get the phone in Download mode since I cannot successfully flash stock via Odin.
I also tried Emergency Firmware recovery in Kies, but I don't have the code. Also tried "Firmware Upgrade and Initialisation" When I put in my model (All Upper Case) and serial number I get an error: 'SM-G900I' Does not support initialising
2) All firewalls are switched off (stopped via windows services), Anti-Virus disabled.
3) All 3 computers that I tried (with 3x different ORIGINAL Samsung cables) are Windows 7 machines
4) I tried ALL USB2.0 ports, front and back of the PCs
5) I run Odin as Administrator
Basically, I can successfully flash various roots and recoveries, be it TWRP, PHILZ, CF-Auto-Root. I can even succesfully wipe and install the CM12 + GAPPS. The end result is that I get a boot loop. If you leave the phone for 20 minutes, every once in a while it actually boots, almost to the GUI, but then resets and gets stuck in boot loops again.
Another interesting observation is that when I get into TWRP and try Wipe and Format, I get all kinds of Read/Write errors.. (see screenshots)
I've been running custom roms on my Galaxy S, S2 and S4 for years now, and have been though everything, never managed to brick any phones yet. This time I am still technically in 'Soft Brick', but after trying so many different Stock Roms via Odin I am starting to suspect maybe faulty hardware? I mean when I first got it, I rooted it and flashed CM12 via PHILZ Recovery. It ran beautifully for just over a week. Then I started getting boot loops. And these "add/remove storage" errors in TWRP are making me suspect hardware..

Hmm.......sounds like you're up against it there fella......The only thing I can suggest is to persevere with what you are trying........Most folks here know that if you are having problems Odin flashing, perseverance is the only thing that works. Odin may not flash on the first X number of flashes, but the time after, it will.........
I still maintain that you should stay away from .pit flashes though......They are strictly "last chance saloon" flashes........
Sent from my rooted Kn0x0 SM-G900F S5

artem1 said:
Hey keithross39,
1) Yes, I have tried Kies. Updated to latest version. It stays on "Connecting" - I can only get the phone in Download mode since I cannot successfully flash stock via Odin.
I also tried Emergency Firmware recovery in Kies, but I don't have the code. Also tried "Firmware Upgrade and Initialisation" When I put in my model (All Upper Case) and serial number I get an error: 'SM-G900I' Does not support initialising View attachment 3116279
2) All firewalls are switched off (stopped via windows services), Anti-Virus disabled.
3) All 3 computers that I tried (with 3x different ORIGINAL Samsung cables) are Windows 7 machines
4) I tried ALL USB2.0 ports, front and back of the PCs
5) I run Odin as Administrator
Basically, I can successfully flash various roots and recoveries, be it TWRP, PHILZ, CF-Auto-Root. I can even succesfully wipe and install the CM12 + GAPPS. The end result is that I get a boot loop. If you leave the phone for 20 minutes, every once in a while it actually boots, almost to the GUI, but then resets and gets stuck in boot loops again.
Another interesting observation is that when I get into TWRP and try Wipe and Format, I get all kinds of Read/Write errors.. (see screenshots)
View attachment 3116299
View attachment 3116300
I've been running custom roms on my Galaxy S, S2 and S4 for years now, and have been though everything, never managed to brick any phones yet. This time I am still technically in 'Soft Brick', but after trying so many different Stock Roms via Odin I am starting to suspect maybe faulty hardware? I mean when I first got it, I rooted it and flashed CM12 via PHILZ Recovery. It ran beautifully for just over a week. Then I started getting boot loops. And these "add/remove storage" errors in TWRP are making me suspect hardware..
Click to expand...
Click to collapse
Usually that error in odin means that there is a problem with the partition of the memory , try to flash your original firmware including PIT file for your device.

Try to find a 3 part or test firmware for your device. These firmwares fully wipe (and I think repartition) your phone rather than simply overwriting what's already there........
Sent from my rooted Kn0x0 SM-G900F S5

Where do you find 3 part or test firmware
---------- Post added at 12:31 PM ---------- Previous post was at 11:58 AM ----------
keithross39 said:
Try to find a 3 part or test firmware for your device. These firmwares fully wipe (and I think repartition) your phone rather than simply overwriting what's already there........
Sent from my rooted Kn0x0 SM-G900F S5
Click to expand...
Click to collapse
Isn't all three included in the Odin Flash-able Full Stock

Yes......but in a "finalized" form.......
As I said in my post before, the regular "end user" firmware flashes on top of or overwrites what's already on the phone.....The 3 part test firmware wipes the old before installing the new......
And as for finding it, sammobile and samsung firmwares are extremely UNLIKELY to host it......Unfortunately they're not readily available.......You're just going to have to trust your luck to Google or sites like XDA.........
Sent from my rooted Kn0x0 SM-G900F S5

keithross39 said:
Yes......but in a "finalized" form.......
As I said in my post before, the regular "end user" firmware flashes on top of or overwrites what's already on the phone.....The 3 part test firmware wipes the old before installing the new......
And as for finding it, sammobile and samsung firmwares are extremely UNLIKELY to host it......Unfortunately they're not readily available.......You're just going to have to trust your luck to Google or sites like XDA.........
Sent from my rooted Kn0x0 SM-G900F S5
Click to expand...
Click to collapse
I cant seem to find any 3 part firmware for T-Mobile anywhere

For 3 part I don't know however sometimes you need just pit file, try asking here: http://forum.xda-developers.com/showthread.php?t=2737448, there is a collection of pit for galaxy s5

Don't look for a "branded" 3 part firmware.....they're generic unbranded (but device specific)......
And *please* leave the pit flashing as a FINAL resort........
Why will a pit flash work when firmware flashes don't.......and if a pit flash fails part way through, nothing short of motherboard replacement is going to unbrick your phone........
Sent from my rooted Kn0x0 SM-G900F S5

qrono said:
For 3 part I don't know however sometimes you need just pit file, try asking here: http://forum.xda-developers.com/showthread.php?t=2737448, there is a collection of pit for galaxy s5
Click to expand...
Click to collapse
Thanks everyone for posting your suggestions. Latest developments:
- Paid for the Raipidgator Premium DL services 'cause I was getting sick of 8-9 hour long stock downloads
- Downloaded 2x more Stock Firmwares for SM-G900I from the XDA and samsung-updates (all official stock roms)
- Downloaded PIT file from the link above. Shame I could only find 1x PIT for the 900I. Anyways, my understanding of PIT is that its just an XML partition table
Tried PIT + Official ROM at the same time - same result (
My buddy recons my Internal Flash is corrupt. I think so too. Evidence is that I can install the CM12 which is 200 odd Mbs, but I can't install the official ROM via Odin and its 1.5Gb... Also I get read/write partition errors in TWRP when doing wipe+format.
What do you guys recon?

R2D2 is sick when PITTIN
R2D2 is sick when PITTIN

artem1 said:
Thanks everyone for posting your suggestions. Latest developments:
- Paid for the Raipidgator Premium DL services 'cause I was getting sick of 8-9 hour long stock downloads
- Downloaded 2x more Stock Firmwares for SM-G900I from the XDA and samsung-updates (all official stock roms)
- Downloaded PIT file from the link above. Shame I could only find 1x PIT for the 900I. Anyways, my understanding of PIT is that its just an XML partition table
Tried PIT + Official ROM at the same time - same result (
View attachment 3117831
My buddy recons my Internal Flash is corrupt. I think so too. Evidence is that I can install the CM12 which is 200 odd Mbs, but I can't install the official ROM via Odin and its 1.5Gb... Also I get read/write partition errors in TWRP when doing wipe+format.
What do you guys recon?
Click to expand...
Click to collapse
keithross39 said:
Yes......but in a "finalized" form.......
As I said in my post before, the regular "end user" firmware flashes on top of or overwrites what's already on the phone.....The 3 part test firmware wipes the old before installing the new......
And as for finding it, sammobile and samsung firmwares are extremely UNLIKELY to host it......Unfortunately they're not readily available.......You're just going to have to trust your luck to Google or sites like XDA.........
Sent from my rooted Kn0x0 SM-G900F S5
Click to expand...
Click to collapse
LATEST SET OF ODIN:
Successfully flashed G900IZTU1BOA1_G900IZZT1BOA1_G900IZTU1BOA1_HOME.tar
See Picture:
Interesting that now Odin has 2x sets of COM ports, as if some how PIT flashing did something to the boot loader? Anyways, after successful Odin (finally) I have the same problem - continuous reboots. Sometimes I see the Samung logo, music plays, but it keeps on rebooting..
Any tips how I can find the "finalized" 3 part firmware for SM-G900I? All I seem to find is the .tar 1x piece firmware files (including the one that flashed successfully above..) Would these be the 3-piece firmwares?
http://www.galaxys5update.com/austr...1anc6-original-4-4-2-firmware-restore-unroot/

keithross39 said:
Don't look for a "branded" 3 part firmware.....they're generic unbranded (but device specific)......
And *please* leave the pit flashing as a FINAL resort........
Why will a pit flash work when firmware flashes don't.......and if a pit flash fails part way through, nothing short of motherboard replacement is going to unbrick your phone........
Sent from my rooted Kn0x0 SM-G900F S5
Click to expand...
Click to collapse
I flashed pit for my phone many times and my phone still stuck at the first boot screen. It still can get to download mode and flash-able.
I am starting to think it is possible for a phone to be flash able successfully in Odin, but still be hard bricked.

Hard brick = hardware issue......usually unrecoverable
Soft brick = software issue.......*possibly* recoverable.
If your device was hard bricked, it would show NO signs of life whatsoever, no matter what you did to it......
Sent from my rooted Kn0x0 SM-G900F S5

have you tried to start in recovery and wipe data/cache?

keithross39 said:
Hard brick = hardware issue......usually unrecoverable
Soft brick = software issue.......*possibly* recoverable.
If your device was hard bricked, it would show NO signs of life whatsoever, no matter what you did to it......
Sent from my rooted Kn0x0 SM-G900F S5
Click to expand...
Click to collapse
So its possible to be permanently soft brick and unfix able despite odin being able to flash with no errors?

Ok....So here's a simplification of it........
1) ABACADAE_FA
2) ABACADAEaFA
Imagine number 1 as a firmware you are trying to flash.
Imagine number 2 as a firmware already installed on your device.
Imagine the lower case 'a' in number 2 is a bit of corrupt data that is causing your phone difficulties.
When you flash a firmware with Odin, you are OVERWRITING or directly replacing the software on your device, so the data string that goes ABACADAE and FA will be replaced.......The data called 'a' will be left untouched.....and will still be an issue after the flash.
The TEST firmware is different and does things differently. It's designed to test the firmware on a 'pristine' device, one that has ABSOLUTELY NO TRACE of a previous OS remaining that might interact with it and cause issues. To make sure this happens, the test firmware will COMPLETELY erase EVERY trace of a pre-existing OS during the flash thereby removing any trace of corrupt data (the lower case 'a' in my example).
The bottom line is, if you REALLY can't recover your phone successfully with Odin, and a test firmware for your device hasn't been 'leaked', you have 2 options.....
1) get your device JTAG-ged.
2) send it to Samsung for an out of warranty repair.......
Sent from my rooted Kn0x0 SM-G900F S5

@artem1 just had a look at your firmwares link.......at a guess, without attempting to download, I'd say that these AREN'T test firmwares.....but single file, finalised, carrier branded, official firmwares......sorry fella, just going to have to 'dig deeper'........
Just bear in mind though.........A device has to have it's 'test' firmware unofficially 'leaked' and unless that's the case for your device, you may not find it.........
Sent from my rooted Kn0x0 SM-G900F S5

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!

Galaxy S5 G900P stucks in unrepairable boot loop

Hello everyone who is reading this, I seriously need your help. I have been using resurrection remix android 8 custom ROM on my galaxy s5 g900p for a while now. 5 days ago, my phone just went off when the battery is around 23% and restart by itself. I waited for it to finish booting, few seconds after it boots up it restart again. Then it continues restarting again and again, it won't stop, it stuck in boot loop.
So I thought I have issue with the ROM so I downloaded the right stock firmware for my phone. Flash it using odin but after it finished successfully it stucks in boot loop again but this time it only shows the samsung galaxy s5 logo.
I boot to recovery and factory reset but it didn't solve the problem. I tried everything it still stuck in boot loop.
But one thing I noticed is, the stock firmware flashing didn't really cleared the root and custom kernel. When I boot up to download mode, system status still shows custom. I have search everywhere on the internet and find solution but none of them seems to work for me.
I don't know if this thread has been created somewhere else, if it is please forgive me. I am newbie here and I don't know that.
I have tried flashing twrp recovery and it worked without me rooting the phone. It worked as if I have already rooted the phone. When in recovery mode, I connected my phone to a PC and finds out it still brings my name attached to the removable storage which it should cleared after flashing with odin.
And also it won't allow me to install any custom ROM on it no matter what I do
It won't allow me to make backup in twrp recovery, any time I tap on backup, it starts backing up then it will froze and restart the phone.
The same applies when I tried installing custom ROM
Guys please I need your help, what could be the problem

BrightyH said:
Hello everyone who is reading this, I seriously need your help..........
Click to expand...
Click to collapse
I don't have this variant but, this behavior is sometimes linked to a battery going bad.
Try turning off the device and fully charge the battery.
Once charged up, see how it performs.
When it fully boots up, take note at the battery % strength. It should be between 98-100%...
I really can't state anything for sure nor guess at it with the current information.
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.

Ibuprophen said:
I don't have this variant but, this behavior is sometimes linked to a battery going bad.
Try turning off the device and fully charge the battery.
Once charged up, see how it performs.
When it fully boots up, take note at the battery % strength. It should be between 98-100%...
I really can't state anything for sure nor guess at it with the current information.
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Click to expand...
Click to collapse
I bought a new battery, charged it to 100% then turn it on but still. It only shows the samsung logo and restart, then the boot loop continues again

BrightyH said:
I bought a new battery, charged it to 100% then turn it on but still. It only shows the samsung logo and restart, then the boot loop continues again
Click to expand...
Click to collapse
When flashing the firmware in odin add the pit file & tick repartition device
Pit file (900p sprint edition)
https://drive.google.com/file/d/0BzyeAt2hy6XeTF9hMzJua0J3UlU/view
Then factory reset in recovery

BrightyH said:
I bought a new battery, charged it to 100% then turn it on but still.......
Click to expand...
Click to collapse
The devices forced shutdown can "potentially" cause a Bootloop as a result.
I believe that the issue may ultimately be the battery itself...
The battery has 4 brass colored pads on it. 2 are for the - & + power and the other 2 are for data information.
Yes, the batteries have a small circuit board within it for battery/power information provided to and from the device itself.
Batteries can go bad without real warning. It doesn't matter how old they are and, most of the time, it goes bad by no fault of yours and no fault of the Firmware.
It just looks to me like a coincidence and bad timing.
_____
TheFixItMan said:
When flashing the firmware in odin add the pit file & tick repartition device......
Click to expand...
Click to collapse
@BrightyH, you'll have to start from scratch as @TheFixItMan had just provided you with the information for doing this.
You can try starting from scratch first to see if it's resolved itself somehow but, my "opinion/suggestion" would be to first get a good/new battery, charge it to 100% then start from scratch.
This is your call...
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.

TheFixItMan said:
When flashing the firmware in odin add the pit file & tick repartition device
Pit file (900p sprint edition)
https://drive.google.com/file/d/0BzyeAt2hy6XeTF9hMzJua0J3UlU/view
Then factory reset in recovery
Click to expand...
Click to collapse
OK
I will try that and give feedback

Ibuprophen said:
The devices forced shutdown can "potentially" cause a Bootloop as a result.
I believe that the issue may ultimately be the battery itself...
The battery has 4 brass colored pads on it. 2 are for the - & + power and the other 2 are for data information.
Yes, the batteries have a small circuit board within it for battery/power information provided to and from the device itself.
Batteries can go bad without real warning. It doesn't matter how old they are and, most of the time, it goes bad by no fault of yours and no fault of the Firmware.
It just looks to me like a coincidence and bad timing.
_____
@BrightyH, you'll have to start from scratch as @TheFixItMan had just provided you with the information for doing this.
You can try starting from scratch first to see if it's resolved itself somehow but, my "opinion/suggestion" would be to first get a good/new battery, charge it to 100% then start from scratch.
This is your call...
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Click to expand...
Click to collapse
ok
thanks, I will try it and give feedback

I have tried all that was suggested and none of them work.
I bought a new battery again, this time around it was tested with another S5 to be sure it is original.
Flashed again with the pit file provided and exactly instructed but still
the boot loop refuse to stop

BrightyH said:
I have tried all that was suggested and none of them work. I bought a new battery again, this time around it was tested with another S5 to be sure it is original. Flashed again with the pit file provided and exactly instructed but still. the boot loop refuse to stop
Click to expand...
Click to collapse
I'm not sure why it is still stuck in a Bootloop...
I performed a quick forum search and located a few threads that may be helpful for you.
I know that they're a bit dated but, the information provided in them should still be valid.
https://forum.xda-developers.com/showthread.php?t=3381961
https://forum.xda-developers.com/showthread.php?t=3350319
https://forum.xda-developers.com/showthread.php?t=3366840
If needed, you can always try to obtain some member guidance within the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=2700073
As a last resort, you can also try to obtain some member guidance within one of the following General Help Threads.
https://forum.xda-developers.com/showthread.php?t=2259645
https://forum.xda-developers.com/showthread.php?t=2257421
Just keep in mind that it's really frowned upon to post for guidance within all of them at once. When posting, give it time for someone to respond first. I personally give it approximately a week or so for a response. This is just a suggestion/recommendation...
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.