Database Users

[Q] Need help unbricking my phone.

I have searched and used as much google fu as I know how, so if I've missed the obvious I'm sorry.
Phone: Att Galaxy S4 SGH-I337
Running: I think stock 4.2.2 that was rooted.
Problem: currently will only get to the att logo then moves no further. Odin always fails to get me back to stock.
Cause of problem: Mostly likely me. I was attempting to unroot my phone using ODIN following a tutorial on galaxys4root.com.
Things I have tried: 6 different USB cords, 4 PCs 1 mac, Odin 3.07 and Odin 1.85, Several different sources for stock roms.
Notes: When I try to use the power button volume button method of booting to recovery it just goes to the odin download screen. This has been happening for a day or so that I've noticed.
Output from odin: <OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)​
Output from phone: Odin Mode
Produc Name: SGH-I337
Current Binary: Samsung Offical
System Status: Custom
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
START [224, 1440]
SW REV. CHECK FAIL : fused : 2, Binary : 1​
the output is pretty much the same regardless of odin computer or cable.
Any help would be greatly appreciated.
Thanks

#1. did you have usb debugging enabled before booting into download mode?
#2. do you know what firmware version was on the device when you got it (MDB, MDL, MF3)?
#3. booting into recovery is volume up + home + power. when your device vibrates, release just the power button. not sure if this is what you've been doing or if this will even benefit you right now.

Can you get into recovery? Were you stock beforehand or did you have a custom rom? If you can get into recovery do a factory reset. I'm guessing you got the mf3 update and that's why odin is not working.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

xBeerdroiDx
1. It was enabled the last time I was able to boot up.
2. Sadly no.
3. Tried a million on a thousand times. Every way which way i could think. The blue text pops up for a fraction of a second then it dumps off into odin mode.
jd1639
Can't get to recovery. Stock rooted. wasn't even aware i got the update. noobed it up.

Idk what else you can do. Try to see if kies will do an emergency restore. After that I'm out of ideas.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Try an older version of odin like 1.85 get into download mode then try to flash a custom recovery?
Sent from my SAMSUNG-SGH-I337 using xda premium

Are you releasing all the buttons as soon as you see the blue text come up--like immediately
@BD could OP have lost recovery and maybe dd the twrp recovery image. assuming adb recognizes phone

rugmankc said:
Are you releasing all the buttons as soon as you see the blue text come up--like immediately
@BD could OP have lost recovery and maybe dd the twrp recovery image. assuming adb recognizes phone
Click to expand...
Click to collapse
Immediately, promise, the text flash up for less than time that it would take to read it. just long enough for you to see something blue. I haven't been able to get it into recovery mode. Up until recently it wasn't a problem.

do you have adb access to phone to see if phone is recognized thru windows command terminal

Rabidbot, you got some serious fire power here helping you. I hope you're successful. Good luck to you.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

rugmankc said:
do you have adb access to phone to see if phone is recognized thru windows command terminal
Click to expand...
Click to collapse
Working on trying to figure that out now.
UPDATE It isn't coming up in the list of attached devices.

ok, i don't know if phone can be recognized in your situation. It has to have had usb debugging enabled.

rugmankc said:
Are you releasing all the buttons as soon as you see the blue text come up--like immediately
@BD could OP have lost recovery and maybe dd the twrp recovery image. assuming adb recognizes phone
Click to expand...
Click to collapse
I would be curious to know if adb in fact does recognize the phone. If so, the OP might be more successful flashing stock recovery and seeing if a factory reset clears it up. Sound like that partition is borked?

xBeerdroiDx said:
I would be curious to know if adb in fact does recognize the phone. If so, the OP might be more successful flashing stock recovery and seeing if a factory reset clears it up. Sound like that partition is borked?
Click to expand...
Click to collapse
Agreed--

xBeerdroiDx said:
I would be curious to know if adb in fact does recognize the phone. If so, the OP might be more successful flashing stock recovery and seeing if a factory reset clears it up. Sound like that partition is borked?
Click to expand...
Click to collapse
Doesn't seem to be recognized.

rabidbot said:
SW REV. CHECK FAIL : fused : 2, Binary : 1
Click to expand...
Click to collapse
I believe you were on MF3 when it died.
Fused:2 means the qfuse was blown by the mf3 update
Binary:1 means the software you're attempting to flash matches a qfuse level 1 (mdl and lower)
I think it's either a samsung warranty replacement or wait for mf3 on kies.
Sent from my SAMSUNG-SGH-I337 using xda premium

Hi,
I would say google these terms to get a better idea of what you need to do to fix your phone:
START [224, 1440]
SW REV. CHECK FAIL : fused : 2, Binary : 1
I am pretty sure it sounds like you somehow flashed the new MF3 update and now it is not possible to Odin an AMDL image onto phone now due to blown Qfuse in the MF3 update. Here is example of what the above terms mean:
http://forum.xda-developers.com/showpost.php?p=43484436&postcount=370
Possible fix? (Not quite the same situation as you are in, but if you try to use Kies to restore your phone, I bet you will be in this same position maybe?)
http://forum.xda-developers.com/showthread.php?t=2360859
Sorry I couldn't provide a definite, quick fix, but I hope this helps point you in the right direction at least!

rabidbot said:
Working on trying to figure that out now.
UPDATE It isn't coming up in the list of attached devices.
Click to expand...
Click to collapse
ok based on other's comments, you may not have a quick solution. i missed the part about "fuse" -- sorry
did you have adb working before as in are your drivers installed. if no drivers, dl kies to get drivers. then uninstall it and try again
sounds like you are familiar with running adb commands?

Klown80 said:
Hi,
I would say google these terms to get a better idea of what you need to do to fix your phone:
START [224, 1440]
SW REV. CHECK FAIL : fused : 2, Binary : 1
I am pretty sure it sounds like you somehow flashed the new MF3 update and now it is not possible to Odin an AMDL image onto phone now due to blown Qfuse in the MF3 update. Here is example of what the above terms mean:
http://forum.xda-developers.com/showpost.php?p=43484436&postcount=370
Possible fix? (Not quite the same situation as you are in, but if you try to use Kies to restore your phone, I bet you will be in this same position maybe?)
http://forum.xda-developers.com/showthread.php?t=2360859
Sorry I couldn't provide a definite, quick fix, but I hope this helps point you in the right direction at least!
Click to expand...
Click to collapse
This is the output from odin. It was successful but my phone still doesn't boot past the att logo.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MF3_BTL_FIX.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> rpm.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> tz.mbn
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!​

rugmankc said:
ok based on other's comments, you may not have a quick solution. i missed the part about "fuse" -- sorry
did you have adb working before as in are your drivers installed. if no drivers, dl kies to get drivers. then uninstall it and try again
sounds like you are familiar with running adb commands?
Click to expand...
Click to collapse
I got the Drives are installed and have worked before. still nothing in the device list.

The end of my S4? (Brick/dead) - Help..

Hi guys, long time lurker here anyway i've always flashed my S4 with odin and not a single problem always flashed STOCK firmwares
but today i recently discovered a new firmware on the list for the GT-I9500 Exynos Octa (version) - this firmware to be in fact I9500ZNUCMI1
but now its bombed... it hanged and hanged at booting for 20 min then it shut it self off turned it back on 'the firmware encounter a problem' message popped up... i cannot go into recovery mode AT ALL (just download mode) so i thought i will flash my previous stock firmware known as I9500XXUBMG9 but now i cant even do that..... odin just gives me a god damn fail - FOR THE LOVE OF ANDROID HELP ME
- Kies is not running in the background
- USB connections are fine
- Cables are fine
So do i have to fear this is the end ? lol i cannot believe this happened to me on a STOCK firmware.... (lucky for me... all my stuff is backed up on sd)
Any help would be greatly appreciated

lethcore said:
Hi guys, long time lurker here anyway i've always flashed my S4 with odin and not a single problem always flashed STOCK firmwares
but today i recently discovered a new firmware on the list for the GT-I9500 Exynos Octa (version) - this firmware to be in fact I9500ZNUCMI1
but now its bombed... it hanged and hanged at booting for 20 min then it shut it self off turned it back on 'the firmware encounter a problem' message popped up... i cannot go into recovery mode AT ALL (just download mode) so i thought i will flash my previous stock firmware known as I9500XXUBMG9 but now i cant even do that..... odin just gives me a god damn fail - FOR THE LOVE OF ANDROID HELP ME
- Kies is not running in the background
- USB connections are fine
- Cables are fine
So do i have to fear this is the end ? lol i cannot believe this happened to me on a STOCK firmware.... (lucky for me... all my stuff is backed up on sd)
Any help would be greatly appreciated
Click to expand...
Click to collapse
If you can get into Download mode, all hope is not lost. Uninstall and resinstall drivers, Odin, etc. reboot.
Odin back to stock, immediately boot into stock recovery, wipe data, reboot.
Done.

donalgodon said:
If you can get into Download mode, all hope is not lost. Uninstall and resinstall drivers, Odin, etc. reboot.
Odin back to stock, immediately boot into stock recovery, wipe data, reboot.
Done.
Click to expand...
Click to collapse
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH

lethcore said:
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH
Click to expand...
Click to collapse
The good news is that Download mode is still working. AS long as that's the case, you can get it back. Just keep trying. Switch PCs, switch cables, switch ports, re download a different stock ROM, etc. do whatever it takes to try every variable you can think of.
Eventually, you'll find what's causing it and the ROM will flash successfully. When that happens, get immediately into recovery and wipe data.
(Remove the battery after it flashes, but it back in and hold vol-up+home+power.)
After the data wipe....
Reboot.
Like I said, Download mode means you can find a way to flash, but working with Odin to resolve these issues can sometimes be a PITA. I've had the same thing myself before. Just don't give up. Try to stay calm, and work your way through it. You'll get it eventually.
Edit: Just noticed that you flashed a CHINA firmware. (Why? ) You may be facing this issue because (I think) they use a different pit. There's a thread devoted to resurrecting the device with pit. Maybe check it out.

lethcore said:
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH
Click to expand...
Click to collapse
dont flash China or Hong kong firmwares.
please post odin progression

samersh72 said:
dont flash China or Hong kong firmwares.
please post odin progression
Click to expand...
Click to collapse
Nothing to post just says 'completed' but its failed.... i'll remember this next time stay away from china/hong kong firmwares...
im still tyring now and will let you guys/girls know how it pans out! wish me luck!

lethcore said:
Nothing to post just says 'completed' but its failed.... i'll remember this next time stay away from china/hong kong firmwares...
im still tyring now and will let you guys/girls know how it pans out! wish me luck!
Click to expand...
Click to collapse
INFO HERE
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUBMG9_I9500OJVBMG9_I9500XXUBMG9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> persdata.img
<ID:0/005> system.img
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)

lethcore said:
INFO HERE
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUBMG9_I9500OJVBMG9_I9500XXUBMG9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> persdata.img
<ID:0/005> system.img
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
recovery is flashed, try to boot into it and make the wipe then re-flash stock, re-wipe.
if not, flash a custom recovery, format system, cache, re-flash stock, re-wipe

@donalgodon
Why ? well i got the I9500 in hong kong (im actually based in china now) (not Chinese though) thought i'll see some nice changes? but seems i fK'ed the phone.... pit? i haven't a clue man pit number? think i've KILLED HER... lol (i never knew the dangers of Chinese firmware) - wont be going down that route again.

@samersh72
Are you sure? i cannot get into 'recover' mode... the phone just hands at 'Firmware upgrade encounted an issue please select kies & try again
i canm only enter download mode.... when i try to enter recover mode it just flashes at the firmware message.

lethcore said:
@samersh72
Are you sure? i cannot get into 'recover' mode... the phone just hands at 'Firmware upgrade encounted an issue please select kies & try again
i canm only enter download mode.... when i try to enter recover mode it just flashes at the firmware message.
Click to expand...
Click to collapse
flash custom recovery,
if not see my signature for flashing right pit with the firmware

samersh72 said:
flash custom recovery,
if not see my signature for flashing right pit with the firmware
Click to expand...
Click to collapse
Well i just grabbed a I9500 pit file and have my stock firmware just add these 2 to odin and click start? that simple or ??

lethcore said:
Well i just grabbed a I9500 pit file and have my stock firmware just add these 2 to odin and click start? that simple or ??
Click to expand...
Click to collapse
yes, make sure that you are using the right pit, put it in "pit" window in odin, and the firmware in "pda", make sure "re-partition" is ticked, start.

samersh72 said:
yes, make sure that you are using the right pit, put it in "pit" window in odin, and the firmware in "pda", make sure "re-partition" is ticked, start.
Click to expand...
Click to collapse
Well you be happy to know
installed the previous firmware and that pit file for I9500 from your sig and everything seems well... booted correctly nothing lost all seems good to early to tell but will keep you informed !
THANK YOU!!!

Note 3 is "not supported" by Kies 3

EDIT: At this point, I'm just trying to flash official firmware via ODIN but every attempt is ending with ODIN: Invalid ext4 image on various firmwares and via various USB ports
Hi everyone,
I recently picked up a Galaxy Note 3 which I soon realized was a parallel import and so I decided to flash firmware from my country with Odin. It failed (I soon realized I had forgotten to enable USB debugging) and my phone currently displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I have tried reinstalling Kies, different USB ports (USB 2.0 & 3.0) after turning off USB 3.0 charging too, reseating the battery etc but each time, Kies tells me "The connected device is not supported by Kies 3. Check which devices are supported and try again." except Kies 3 is what the Note 3 uses...
Reinstalling the driver as well doesn't appear to do anything either. The Note 3 shows up in device manager as SAMSUNG Mobile USB Modem so it's detected but I can't exactly say if that is correct?
Anyway, any help is appreciated! I'll see when Samsung's contact centre is open next being Christmas and all and since I was only flashing official firmware, my Knox counter is still at 0x0 so my warranty is still in place should the need to use it arise.

If you flash with odin then why do you need kies for? Just put it in download mode and flash it again.
Sent from Note 3 SM-N9005

ione2380 said:
If you flash with odin then why do you need kies for? Just put it in download mode and flash it again.
Sent from Note 3 SM-N9005
Click to expand...
Click to collapse
Flashing with ODIN has been stopping on "Invalid ext4 image" every time but I'm downloading another ROM to try out at the moment. Hopefully that should work. I was trying to avoid ODIN since I wasn't sure if repeatedly try to flash a ROM (even official firmware) and having it fail would make things worse.

Having the same problem
Sentryism said:
Flashing with ODIN has been stopping on "Invalid ext4 image" every time but I'm downloading another ROM to try out at the moment. Hopefully that should work. I was trying to avoid ODIN since I wasn't sure if repeatedly try to flash a ROM (even official firmware) and having it fail would make things worse.
Click to expand...
Click to collapse
What's the solution? Do you already could find the problem?

bgantenbein said:
What's the solution? Do you already could find the problem?
Click to expand...
Click to collapse
Well, I don't have one yet. I'm still going through various firmwares but the second one I've tried threw up the same error. Basically, I'm just waiting for firmwares to download at the moment. I'll report back if I manage to fix it. I would assume it's due to not having debugging mode enabled but I can't exactly enable it in my current situation.
Here is the ODIN log if it is of any use:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMJ7_N9005OXADMJ4_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> sbl1.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> aboot.mbn
<ID:0/009> rpm.mbn
<ID:0/009> tz.mbn
<ID:0/009> sdi.mbn
<ID:0/009> NON-HLOS.bin
<ID:0/009> boot.img
<ID:0/009> recovery.img
<ID:0/009> system.img.ext4
<ID:0/009> FAIL! (Ext4)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.

Sentryism said:
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Click to expand...
Click to collapse
It seems that you might have a severe case of bad blocks on the eMMC (internal flash) - that in itself should be enough reason for a warranty replacement.
If you can not do a warranty replacement you should look (inside Odin) into erasing all NAND and repartitioning (there are some posts around with similar info, read a few of those until you understand what you are doing before starting to do anything on that direction).

Hello!
I made the switch from iOS to Android a couple of days ago and as well own a Note 3 device. After a couple of days of reading around the forums I decided to flash the MK2 Uk rom since in my country we're only up to MJ7 and I've been experiencing very weird battery drains. I am aware that the update won't likely fix them and I'll have to wait for the next one in January but I hope to at least make things better. Unfortunately today I downloaded Kies3 and I'm getting the same error when I click on the firmware check or upgrade menu (or whatever it is called). I haven't tried Odin yet because the firmware was taking too long to download and I had tl go out for work. Still I very doubt it will work since the official program isn't even working.
tl;dr; Please post in the topic when you find a solution as I am experiencing the same problem as well. Especially if I have to do a warranty replace since I have a wiggly button and I was wondering whether to do that in the first place.

Possible not a genuine Note 3?

This is absurd, I said I am new to Android, this doesn't mean I have grown in a pot. My device came with all the appropriate stickers, branding and everything and is purchased through a local carrier. Unfortunately I got one from Vietnam with the wiggly home button but it is a legit device. Anyways I even tried contacting my local support but they were most unhelpful, only forwarded me to an Authorized Service Provider (what an awful chat app, they disconnected me and I even lost the details). I think I will soon try flashing a custom firmware through CWM or something..

Sentryism said:
...
I recently picked up a Galaxy Note 3 which I soon realized was a parallel import and so I decided to flash firmware from my country with Odin. It failed (I soon realized I had forgotten to enable USB debugging) and my phone currently displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
...
Click to expand...
Click to collapse
I believe KIES 3 in Emergency Firmware Recovery mode does NOT YET support the updated bootloaders - so if your device has a bootloader >= MJ3 it will not be seen in KIES 3. I am still using Kies v3.1 but I have seen a v3.2 available, however I do not know if the problem is solved.

Sentryism said:
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Click to expand...
Click to collapse
Hi
Just had exactly the same problem as yours, and odin continuously failed just after 'hidden img'. Tried several roms to no avail. Phone was already rooted before the issue, and knox flag was already 0x1. I decided to flash cwm recovery (via odin) from here:
http://forum.xda-developers.com/showthread.php?t=2454079
The note 3 (SM-N9005) booted all the way surprisingly but with some issues (back button not working/Samsung keyboard stopping). I can now flash rom zip.
Tip: As your Knox flag is 0x0, try flashing stock recovery via odin.

Flashed Rom zip. Note 3 back to health.

shayind4 said:
Flashed Rom zip. Note 3 back to health.
Click to expand...
Click to collapse
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2

shayind4 said:
Flashed Rom zip. Note 3 back to health.
Click to expand...
Click to collapse
R2D2_NZ said:
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
Click to expand...
Click to collapse
\given the fact it was a Zip file he flashed, it would a CWM flashable ROM that worked

R2D2_NZ said:
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
Click to expand...
Click to collapse
Hi
I flashed Djembey's deodexed pre-rooted jb 4.3 SM-N9005 XXUDMJ7 superslim rom (cwm) from here (second post):
http://forum.xda-developers.com/showthread.php?t=2461929
I used CWM recovery. After flashing the superslim rom, I was able to flash stock rom via odin.
Shayind4
---------- Post added at 02:09 PM ---------- Previous post was at 02:07 PM ----------
androidlover287 said:
\given the fact it was a Zip file he flashed, it would a CWM flashable ROM that worked
Click to expand...
Click to collapse
You are right.

If you tried to flash a firmware from another country than the original one, it might be that the partition size is not correct. You probably need to flash a pit file that is matching the partition size of the new firmware. Try to search for one that is matching to one of the firmware you downloaded and flash it with the new firmware ( tick repartition in Odin - this will erase your data !!!).
This is just a proposal and I do not know it it will work, but I got that hint from a thread in a German forum about changing from EU version to DBT firmware.

Im having a similar issue, except my note3 is the exynos (sm-n900), kies3 says my phone is not supported and odin fails at flashing my phone, it shows this
<ID:0/026> Added!!
<ID:0/026> Removed!!
<ID:0/027> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900ZSUCML1_N900OZSCML1_N900ZSUCMJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/027> Odin v.3 engine (ID:27)..
<ID:0/027> File analysis..
<ID:0/027> SetupConnection..
<ID:0/027> Initialzation..
<ID:0/027> Get PIT for mapping..
<ID:0/027> Firmware update start..
<ID:0/027> modem.bin
<ID:0/027> NAND Write Start!!
<ID:0/027> sboot.bin
<ID:0/027> boot.img
<ID:0/027> cache.img
<ID:0/027>
<ID:0/027> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have no idea on what else to do, any help please?

I've got the system.img.ext4 issue as well. Knox is still 0x0 and I was only trying to flash (Odin) a ROM from Sammobile - MI7, same level as the original but XSA instead of TGY. Bloody annoying.
Anyone got the Aussie Samsung support number?

I resolved my issue by DL'ing and flashing the TGY ROM - got an MI7 version so I should be still OK for RDLV. Apparently flashing with the ROM from another country is a problem - Odin passed teh XSA one without an issue, so I don't think it was a corrupt DL. I did see a reference in my searching to perhaps the partitions are different sizes in different CSC's or something.
So, now to enjoy my Note for a few days before rooting...

S4 I9500 Bricked while installing rom...

Hi, I had my S4 with stock rom 4.3 with adam kernel and philz touch recovery, tried to install via odin the stock rom 4.4.2 TTT but because of a CPU problem the usb connection was interrupted while installing. Now I'm stuck at download mode.
Here's details.
Download mode:
ODIN MODE
PRODUCT NAME: GT-I9500
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
RP SWREV: A3
After attempting install rom via odin:
appears the same in download mode plus this line:
SW REV. CHECK FAIL. DEVICE:-3, BINARY:2
Odin log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500UBUEMK1_I9500UUBEMK1_I9500UBUEMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've already tried the same with the PIT file but still doesn't work, anybody got a clue?

Anybody? I need my phone back :S

chemell said:
Anybody? I need my phone back :S
Click to expand...
Click to collapse
Odin was interrupted at the bootloader update (sboot.bin). You need the "factory ROM" to flash it, however I am not aware if anything for 4.2.2 would be available for now.

spamtrash said:
Odin was interrupted at the bootloader update (sboot.bin). You need the "factory ROM" to flash it, however I am not aware if anything for 4.2.2 would be available for now.
Click to expand...
Click to collapse
But can I use another rom? I don't care if isn't a 4.2.2 rom because I need the phone again doesn't matter with which rom or android version.

If u can boot to recovery flash a custom rom then flash stock via odin

aayushkhajuria2842 said:
If u can boot to recovery flash a custom rom then flash stock via odin
Click to expand...
Click to collapse
I can't, I only got download mode...

Try the right key combination .....its nt possible that you can have download mode but nt recovery
Press and hold Volume Up, Home and Power

aayushkhajuria2842 said:
Try the right key combination .....its nt possible that you can have download mode but nt recovery
Press and hold Volume Up, Home and Power
Click to expand...
Click to collapse
Well it doesn't work, when I turn on the phone a black screen with a cellphone, a warning sign and a monitor appears and a text says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
With this screen I can only go into download mode but when I try recovery mode it just puts the screen black and back to the same text and pictures.
Another thing that worries me it's that I can't turn the phone off with the button, only if I pull the battery out.

This can be recovered I had same prblm some months ago bt I just flashed stock firmware nd it was fixed u may try flashing stock rom again

aayushkhajuria2842 said:
This can be recovered I had same prblm some months ago bt I just flashed stock firmware nd it was fixed u may try flashing stock rom again
Click to expand...
Click to collapse
I've already tried with the rom "I9500UBUEMK1_I9500UUBEMK1_I9500UBUEMK1_HOME.tar.md5" (I believe it's stock rom) and get the odin error that appears in my first post...

Try some other firmware of you own region ......... 4.3 or 4.4 whichever u have for your region .......I think then u will nt get same error

chemell said:
Hi, I had my S4 with stock rom 4.3 with adam kernel and philz touch recovery, tried to install via odin the stock rom 4.4.2 TTT but because of a CPU problem the usb connection was interrupted while installing. Now I'm stuck at download mode.
Here's details.
Download mode:
ODIN MODE
PRODUCT NAME: GT-I9500
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
RP SWREV: A3
After attempting install rom via odin:
appears the same in download mode plus this line:
SW REV. CHECK FAIL. DEVICE:-3, BINARY:2
Odin log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500UBUEMK1_I9500UUBEMK1_I9500UBUEMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've already tried the same with the PIT file but still doesn't work, anybody got a clue?
Click to expand...
Click to collapse
Hi, try to flash through kies emergency firmware recovery.

navdeepavi said:
Hi, try to flash through kies emergency firmware recovery.
Click to expand...
Click to collapse
Hi, I tried, but in Kies I can't get trough the "Connecting..." status so when I choose "Emergency firmware recovery" the list of devices appears empty.

I think u should try flashing some other stock firmware I hav had the prblm before

aayushkhajuria2842 said:
I think u should try flashing some other stock firmware I hav had the prblm before
Click to expand...
Click to collapse
Hi, I'm downloading another firmware now. But I don't think it will work, i've tried with a pack I found (firmware+pit+booloader+cp+csc) and didn't work. Also I tried just flashing only de BP file and keep getting the same error:
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
I don't know what to do but I'm downloading an ARO stock firmware (4.3) and I'll try...

It should work I did the same thing but cant say anything

aayushkhajuria2842 said:
I think u should try flashing some other stock firmware I hav had the prblm before
Click to expand...
Click to collapse
Obviously not. simple flash of ROM is not sorting out the corrupted bootloader problem.
---------- Post added at 07:52 AM ---------- Previous post was at 07:45 AM ----------
chemell said:
Hi, I'm downloading another firmware now. But I don't think it will work, i've tried with a pack I found (firmware+pit+booloader+cp+csc) and didn't work. Also I tried just flashing only de BP file and keep getting the same error:
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
I don't know what to do but I'm downloading an ARO stock firmware (4.3) and I'll try...
Click to expand...
Click to collapse
considering your situation, I doubt if it will work. you have to pick from two scenarios:
a) your download mode shows warranty void, knox void, custom: then you have to go to step 2 below.
b) your download mode shows all statuses samsung or official or 0x0 - then go to 1
1. Call samsung service center, they shall sort it out under the warranty.
2. More complicated, if you do not want to pay for repairs.
DELETED, procedure was for I9505 ONLY
you have to follow the procedure form this link instead.
Good luck.

spamtrash said:
Obviously not. simple flash of ROM is not sorting out the corrupted bootloader problem.
---------- Post added at 07:52 AM ---------- Previous post was at 07:45 AM ----------
considering your situation, I doubt if it will work. you have to pick from two scenarios:
a) your download mode shows warranty void, knox void, custom: then you have to go to step 2 below.
b) your download mode shows all statuses samsung or official or 0x0 - then go to 1
1. Call samsung service center, they shall sort it out under the warranty.
2. More complicated, if you do not want to pay for repairs.
You will need the PC with not faulty CPU, first.
Then, you have to use the PIT from here
Of course, you will need the Qualcomm drivers as well, from here or this one
Then, you have to follow the relatively simple procedure described here
That shall fix the corrupted bootloader, and I hope that you will not see the described there errors which would point to the hardware problem.
Good luck.
Click to expand...
Click to collapse
Warning!
He said he is in trouble with a I9500 device, so the Qualcomm drivers will not help....much.

Just an observation, you said you have no recovery right? So have you tried just flashing the tar of PhilZ recovery using Odin to get it back?
At least then you'll have a recovery again and can move forward with a custom ROM install
Sent from my GT-I9505 using XDA Premium HD app

lolo9393 said:
Warning!
He said he is in trouble with a I9500 device, so the Qualcomm drivers will not help....much.
Click to expand...
Click to collapse
right. the correct one provided.

[Q] Soft brick at&t note 3?

Hi
I have AT&T Note 3 , sim unlock from carrier, successful kingo root 0x0 Knox (startup splash screen says Custom Unlock)
So, I was hopped up on percocets because of my recent surgery and i decided i was in conscious enough mind to tackle getting AWS unlock. I wasn't.
I was reading about chainfire regionaway app, so i went to the app store and downloaded the first chainfire app that popped up - 3D. so now i am stuck in the note 3 splash screen. yes i know i should have read it more carefully, etc. but i just wasn't all there at the time. Please help me save this $500 brick!
I've been reading these methods:
http://www.droidviews.com/how-to-unbrick-att-galaxy-note-3-sm-n900a/
i can get the phone recognized in ODIN, but the secure check fail: cache occurs
http://forum.xda-developers.com/showthread.php?t=2567133
i can't download any of these files...
http://forum.xda-developers.com/showthread.php?t=2507403
tried this but didn't work.
i'm really not making any headway... any help would be much appreciated.
side note:
can i send this in for warranty? Since AT&T just release the kitkat update can i claim that i tried to update and it failed?
current binary: samsung official
system status: custom (not official)
Knox lock 0x0
Knox warranty void 0x0
EDIT: After doing the ODIN fail - it is stuck in ODIN mode and says "firmware upgrade encountered an issue. Please select recory mode in Kies & try again."
Can not enter download mode. But still connects in ODIN
thanks!

Yes you can return. Best bet as Knox counter is still 0.
If you try other methods and they don't work, you may tripe Knox.
Even you connect to your pc is the phone on download mode?

kenny1991 said:
Yes you can return. Best bet as Knox counter is still 0.
If you try other methods and they don't work, you may tripe Knox.
Even you connect to your pc is the phone on download mode?
Click to expand...
Click to collapse
when i connect to PC it recognizes in ODIN but KIES does not recognize it.
It won't go into reboot mode (vol up + power + home)
it only boots into ODIN mood

firstsx said:
when i connect to PC it recognizes in ODIN but KIES does not recognize it.
It won't go into reboot mode (vol up + power + home)
it only boots into ODIN mood
Click to expand...
Click to collapse
Lol?
What are you trying to do here? Flashing anything?
Is it 4.3 or 4.4 os?
Never run kies side by side Odin add the last one hates the first. Kies is useless.
Kill it and restart your pc. Don't run kies services when using Odin.
I think you should download your firmware from sammobile.com and flash it.
Take battery out and then try download mode again. After killing kies you should be able to use Odin to flash.
---------- Post added at 10:35 PM ---------- Previous post was at 10:32 PM ----------
I don't know. But flashing kitkat may tripe Knox i don't know atnt models. If you don't want to flash then return it.

kenny1991 said:
Lol?
What are you trying to do here? Flashing anything?
Is it 4.3 or 4.4 os?
Never run kies side by side Odin add the last one hates the first. Kies is useless.
Kill it and restart your pc. Don't run kies services when using Odin.
I think you should download your firmware from sammobile.com and flash it.
Take battery out and then try download mode again. After killing kies you should be able to use Odin to flash.
Click to expand...
Click to collapse
lol sorry!
ok if i run KIES (because the screen says connect to kies and do recovery mode) it does not recognize. I am not trying to connect ODIN and kies at the same time!
it was 4.3
i download the sammobile file - it says:
SQ Rev Check fail: [sbl1]Fused 2 > Binary 1

firstsx said:
lol sorry!
ok if i run KIES (because the screen says connect to kies and do recovery mode) it does not recognize. I am not trying to connect ODIN and kies at the same time!
it was 4.3
i download the sammobile file - it says:
SQ Rev Check fail: [sbl1]Fused 2 > Binary 1
Click to expand...
Click to collapse
Where does it say? Kies? Again kies is useless. I don't think it supports note 3.
This is your firmware. http://www.sammobile.com/firmwares/3/?download=25106
You know how to flash?

kenny1991 said:
Where does it say? Kies? Again kies is useless. I don't think it supports note 3.
This is your firmware.
You know how to flash?
Click to expand...
Click to collapse
yes i know its useless, the phone itself tells me to connect to kies. I just tried it once to see if it would rexognize but it does not!
Yes i downloaded the firmware from sammobile, put it into the AP portion of ODIN and start.
but when i run it, it fails and says this on my phone
SQ Rev Check fail: [sbl1]Fused 2 > Binary 1

firstsx said:
yes i know its useless, the phone itself tells me to connect to kies. I just tried it once to see if it would rexognize but it does not!
Yes i downloaded the firmware from sammobile, put it into the AP portion of ODIN and start.
Click to expand...
Click to collapse
hm. Still no recovery mode?
Past your Odin log so someone can see why it fails.

<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900AUCUBMI9_N900AATTBMI9_N900AUCUBMI9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Need pit file?

kenny1991 said:
Need pit file?
Click to expand...
Click to collapse
sammobile doesn't say anything about pit file?
i only used the AP file from there
i have HLTE__USA_ATT_32G_pit file even when i use that PIT file with the AP file it still gives me the same fail error...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900AUCUBMI9_N900AATTBMI9_N900AUCUBMI9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

firstsx said:
i download the sammobile file - it says:
SQ Rev Check fail: [sbl1]Fused 2 > Binary 1
Click to expand...
Click to collapse
This means you are trying to flash a version older than what is currently installed. Try the next higher revision, or find one that doesn't include a bootloader.
Sent from my leanKernel 2.3 powered stock 4.4.2 SM-N900T

toastido said:
This means you are trying to flash a version older than what is currently installed. Try the next higher revision, or find one that doesn't include a bootloader.
Sent from my leanKernel 2.3 powered stock 4.4.2 SM-N900T
Click to expand...
Click to collapse
how can there be a newer version, it was never updated to kitkat?
sammobile only lists that version and i'm quite certain it was 4.3
so if i don't flash the bootloader, what do i flash?
can i not use these files?
AP_N900AUCUBMJ5.zip
BL_N900AUCUBMJ5.zip
CP_N900AUCUBMJ5.zip
HLTE_USA_ATT_32G.pit

firstsx said:
how can there be a newer version, it was never updated to kitkat?
sammobile only lists that version and i'm quite certain it was 4.3
so if i don't flash the bootloader, what do i flash?
can i not use these files?
AP_N900AUCUBMJ5.zip
BL_N900AUCUBMJ5.zip
CP_N900AUCUBMJ5.zip
HLTE_USA_ATT_32G.pit
Click to expand...
Click to collapse
Hi mate,
if you are stuck, maybe you can try this.
http://forum.xda-developers.com/showthread.php?t=2701062
it's a way to unbrick your software.
and update to kitkat.
maybe your problem is the firmware in the sammobile were before the firmware you have install on your device via OTA update.
Yours firmware came throw out via OTA update and with some reason you can't see any latest firmware USA N900A in sammobile.
try the method in the link and reply if you have been successful.
cumps

Markudsc said:
Hi mate,
if you are stuck, maybe you can try this.
http://forum.xda-developers.com/showthread.php?t=2701062
it's a way to unbrick your software.
and update to kitkat.
maybe your problem is the firmware in the sammobile were before the firmware you have install on your device via OTA update.
Yours firmware came throw out via OTA update and with some reason you can't see any latest firmware USA N900A in sammobile.
try the method in the link and reply if you have been successful.
cumps
Click to expand...
Click to collapse
can i use this method
http://forum.xda-developers.com/showthread.php?t=2559715
it seems pretty much the same, except yours includes updating to kitkat.
if i do kitkat, can i still keep root?
will this trip knox?

Ok i did this method
http://forum.xda-developers.com/showthread.php?t=2559715
i re-downloaded all the files because the files i had just wouldn't work in ODIN or anything. so based your advice i just downloaded new files.
ODIN flash was successful
then i did the rest of the steps successfully! and i am back!