Database Users

[Q] [i9505] HELP! - Soft bricked device

Hi guys and girls,
I'm new to this forum and new-ish to flashing roms and rooting my phone (SGS4 i9505 jfltexx i9505xxUBMGA), so I apologize If I've posted this in the wrong thread for starters.
I've been jumping between Samsung's stock ROM and Cyanogenmod 10.1/10.2 ROMs.
I can't remember exactly what I did wrong for my phone to be soft bricked, but I can list a few possibles and my device information to see if anyone can spot the problem;
CF-AUTO-ROOT jflte-jfltexx-gti9505
CM-10.2 Nighty Jfltexx
GAPPS
openrecovery-twrp-2.6.3.1
recovery-clockwork 6.0.4.4
PhilZ Touch 5.18.9-i9505
Now when I try boot my device I get told to boot recovery mode in samsung kies .. Which I've tried but it doesn't bring up any device in the list. I've tried it whilst my phone is in download mode, recovery mode and where it displays I've got a firmware issue.
I've tried flashing new recovery files and also I tried flashing "XSS-I9505XXUBMGA-20130924140120.home.tar" via Odin.. All seems to fail
I'm running out of ideas and options and I'm not the wisest guy so if any of you criticize me for my poor knowledge It'll be pointless as I wouldn't be here writing this in the first place If I didn't know that already.
I've never had a problem flashing custom ROMs and recoverys before, this is the first time. I've not selected no stupid options in Odin such as Re-Partition. I stick to the Auto Reboot and occasionally the F. Reset Time. Every guide I look at tells me different.
Below is a list of my devices original stock details:
kernal version
3.4.0-1081224
[email protected] #1
build number
JDQ39.I9505XXUBMGA
Click to expand...
Click to collapse
Any help, files, guides on how to solve this problem given to me would be VERY appreciated.
Also, I'm not sure if this is a kernal problem. But my battery has recently appeared to be draining rather quickly and It'll display "low battery" warnings at about 30% instead of the usual 14%. And It'll also shut down thinking its out of battery at about 16%, then I turn it back on and it says like 30%. Sometimes once its fully died, I place it on charge and after a matter of minutes it says its at 50%... I guess fully draining and leaving my battery on charge for 24 hours may fix that problem?
Please help!
EDIT: I think USB debugging is disabled, but I cannot get into my phone settings to enable it now?
My download mode screen says "Write protection: Enabled".

Just download stock firmware from sammobile and flash with Odin.
Sent from my GT-I9505 using XDA Premium HD app

Obagleyfreer said:
Just download stock firmware from sammobile and flash with Odin.
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
I've looked on sammobile but there isn't a i9505xxubmga?

Ipasah said:
I've looked on sammobile but there isn't a i9505xxubmga?
Click to expand...
Click to collapse
here you go
http://www.sammobile.com/firmwares/1/?model=GT-I9505&pcode=BTU#firmware

Really do appreciate it - I'll get downloading that now and I'll let you know how it goes.
As for the debugging mode? Is there a way to enable USB debugging from recovery or download mode?
Also, can I only get xxumbga for my device? xxuemj7 and xxudmh8 are also being show in that link you sent me. Would they not work?

Ipasah said:
Really do appreciate it - I'll get downloading that now and I'll let you know how it goes.
As for the debugging mode? Is there a way to enable USB debugging from recovery or download mode?
Also, can I only get xxumbga for my device? xxuemj7 and xxudmh8 are also being show in that link you sent me. Would they not work?
Click to expand...
Click to collapse
no need to enable usb debugging to flash with odin.
mj7 and mh8 had a secured bootloader with knox (for more info read here), once flashed, you can not downgrade

samersh72 said:
no need to enable usb debugging to flash with odin.
mj7 and mh8 had a secured bootloader with knox (for more info read here), once flashed, you can not downgrade
Click to expand...
Click to collapse
Seems like my bootloader isn't knoxd yet, which i guess makes easier for me to resolve my softbrick problem.
Damn hotfile downloading at 200kb/s. Hopefully I'll have my phone fixed before tomorrow, kinda waiting on a phone call for a job interview lol.

I'm flashing the stock version to my phone now, and it appears to be stuck at the BOOT part.
It is a 2.4GB file though so I'll leave it doing it overnight I guess.
What I got so far:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMGA_I9505OXXBMH1_I9505XXUBMGA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
Click to expand...
Click to collapse
EDIT - Anyone got any idea how long this takes roughly? It's been stuck on BOOT for about an hour now.
My device displays this in the download mode whilst trying to flash this stock firmware.
ODIN MODE
Product name: GT-i9505
Current binary: Samsung official
System status: Custom
CSB-CONFIG-LSB:0x30
Write protection: Enabled
START [224,1440]
Click to expand...
Click to collapse
UPDATE: Tried flashing the stock firmware with two different versions of ODIN, in different USB slots, and they both failed with the same reason as before. Writing had failed. I'm running out of ideas and really hope I haven't permanently bricked my phone...
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

Bump - Need my phone fixing today really, considering anything as long as it works again.

Now it appears like I've got the knox warranty due to trying to fix my phone over Kies .... which failed -.-
Odin mode
Product name: GT-I9505
Current binary: Samsung official
System status: customer
Knox kernel lock: 0x0
Knox warranty void: 0x0
CSB-CONFIG-LSB:0x30
write protection: enabled
eMMC BURST MODE: enabled.
Click to expand...
Click to collapse
HELP ME

same ensingsb
I'm gonna try install this version from Samsung Kies off the Sammobile.com website now:
Model: GT-I9505
Country: United Kingdom
Version: Android 4.3
Changelist: 1765174
Build date: Tue, 15 Oct 2013 07:21:56 +0000
Product Code: BTU
PDA: I9505XXUEMJ7
CSC: I9505BTUEMJ8
MODEM: I9505XXUEMJ7
Click to expand...
Click to collapse
Appears to be my only remaining method of fixing my phone....

Even tried PIT file and re-partitioning now and STILL fail..
I know I shouldn't try things unless I'm 100% sure, but that's the best help I'm getting right now.
The internet has no answers for my problem, and it appears neither does the community of this forum.
One £400 house brick, ****ing brilliant stuff.

Ipasah said:
Even tried PIT file and re-partitioning now and STILL fail..
I know I shouldn't try things unless I'm 100% sure, but that's the best help I'm getting right now.
The internet has no answers for my problem, and it appears neither does the community of this forum.
One £400 house brick, ****ing brilliant stuff.
Click to expand...
Click to collapse
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
if not, flash a pre-rooted firmware http://forum.xda-developers.com/showthread.php?t=2250824

samersh72 said:
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
if not, flash a pre-rooted firmware http://forum.xda-developers.com/showthread.php?t=2250824
Click to expand...
Click to collapse
Tried all of those steps many times over.
Is there a point in trying to root my rom when my phone doesn't even get to the bootloader?
Soon as i turn it on i get told theres a firmware issue encountered. I can still get to download mode, but not recovery mode.
EDIT: I dont even know what ROM is on it right now, everything is a mystery to me now, I'm relying purely on the XDA communities help now. As far as I'm aware, I've got a brick.

Sorry I'm giving up trying to find an answer myself now.
If anyone out there actually knows how to fix it, please enlighten me as I haven't the foggiest.
I'll try include as much details as I can ..
Recovery mode doesn't work
Download mode does work
Soon as i turn the device on I get the "Encountered firmware issue" problem
I've tried using many different versions of Odin
I've tried using different USB ports
I've tried using a different USB cable
I've tried using a different PC
I've tried flashing all sorts of recoveries such as TWRP, CWM, PhilZ.
I've tried flashing all sorts of custom and STOCK ROMs
I've tried re-partitioning using a PIT file
Click to expand...
Click to collapse
I've tried EVERYTHING I can possibly think of..
The problem appears to be that my phone WONT let ANYTHING write to it.
Thus making it impossible to flash ANYTHING therefore leaving me stuck with a waste of metal and plastic.
I have the Samsung Galaxy S4 LTE i9505 Jfltexx .. Not sure what ROM is on it, not sure what Kernal, not sure what firmware .. I haven't a clue
Just help me dear god please.

Ipasah said:
Tried all of those steps many times over.
Is there a point in trying to root my rom when my phone doesn't even get to the bootloader?
Soon as i turn it on i get told theres a firmware issue encountered. I can still get to download mode, but not recovery mode.
EDIT: I dont even know what ROM is on it right now, everything is a mystery to me now, I'm relying purely on the XDA communities help now. As far as I'm aware, I've got a brick.
Click to expand...
Click to collapse
try to flash a pre-rooted firmware from the link i gave

samersh72 said:
try to flash a pre-rooted firmware from the link i gave
Click to expand...
Click to collapse
Not gonna lie, i'm not even sure which one I should be downloading from the link you provided.
I dont even know If my device is still under xxubmga or not anymore.

Now I get:
Odin Mode
Product name GT-i9505
current binary samsung official
system status custom
knox kernel lock 0x0
knox warranty void 0x0
csb-config-lsb 0x30
write protection enabled
emmc burst mode enabled
Click to expand...
Click to collapse
and now when odin fails it says
start [224,1440]
sw rev. check fail : fused : 3, binary : 1
Click to expand...
Click to collapse

Ipasah said:
Now I get:
and now when odin fails it says
Click to expand...
Click to collapse
hmmmm.... emmc burst!!!!

samersh72 said:
hmmmm.... emmc burst!!!!
Click to expand...
Click to collapse
If it helps, I couldn't care less about the warranty?
I'd just like my phone to work again, I don't care on what ROM whether it be custom or stock.

[Q] My Note 3 is stuck after trying Odin

thinks should be super easy but sadly things got F-ed up for no reason.
Hoping that someone can help me out.
I'm on a SM-N9005 model
Reactivation lock off
Knock kernel lock 0x0
I also see on the Odin mode screen that it says
"Write protection: Enable" (not sure if that's important).
On the Box the phone says sm-n9005zwexs
I downloaded the drivers from http://stockroms.net/file/Drivers/Samsung/SAMSUNG_USB_Driver_for_Mobile_Phones.exe (which is what all sites I've checked recommended).
I've tried different USB ports.
I'm using the USB 3 charger that came with the Note 3
Now I followed the instructions by downloading Odin, going into "odin mode" on the device (down volume, power and home and seeing the giant green android), the phone is detected and I select the CF-Auto Root file after clicking on PDA (in Odin 3) and sadly I end up getting a fail (specifically when it gets to 40% of the progress bar on the note 3). Since I have an N9005 I used this CF Auto Root file http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
I've tried both versions Odin3 1.85 and Odin 3 3.09 and they both give me a giant red FAIL.
Now when I tried to reboot my phone, I get "firmware upgrade encountered an issue"
When I try and launch KIES 3, it says that the mobile phone is not supported -_-
I really don't know what to do. At this point, screw rooting, I just want it to work -_-

I know that people don't need much of an incentive on these forums, but happy to even go as far as paying a reward to fix this
Only had the phone for a day...

I read about others that have bricked their new N3 trying to root it, and, losing their warranty in the process, (it's the first thing they check).
Seems as if most of the educated folks on this site are waiting for a safe procedure, (and I'm gonna follow their lead).
Good luck my friend, I hope you didn't ruin a $700 device :crying:

K, I had a similar problem. I accidently left KIES running in the background. Kies and ODIN don't play nice together. If you left Kies running it can cause havoc while trying to flash and seems to cause ODIN to fail no matter what version.
Thought I'd bricked my phone for a little while too...

amnesia said:
thinks should be super easy but sadly things got F-ed up for no reason.
Hoping that someone can help me out.
I'm on a SM-N9005 model
Reactivation lock off
Knock kernel lock 0x0
I also see on the Odin mode screen that it says
"Write protection: Enable" (not sure if that's important).
On the Box the phone says sm-n9005zwexs
I downloaded the drivers from http://stockroms.net/file/Drivers/Samsung/SAMSUNG_USB_Driver_for_Mobile_Phones.exe (which is what all sites I've checked recommended).
I've tried different USB ports.
I'm using the USB 3 charger that came with the Note 3
Now I followed the instructions by downloading Odin, going into "odin mode" on the device (down volume, power and home and seeing the giant green android), the phone is detected and I select the CF-Auto Root file after clicking on PDA (in Odin 3) and sadly I end up getting a fail (specifically when it gets to 40% of the progress bar on the note 3). Since I have an N9005 I used this CF Auto Root file http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
I've tried both versions Odin3 1.85 and Odin 3 3.09 and they both give me a giant red FAIL.
Now when I tried to reboot my phone, I get "firmware upgrade encountered an issue"
When I try and launch KIES 3, it says that the mobile phone is not supported -_-
I really don't know what to do. At this point, screw rooting, I just want it to work -_-
Click to expand...
Click to collapse
It's much more helpful when trying to troubleshoot the failure if you actually paste the full log from Odin. The "write protection enabled" thing is not part of the problem. That's bootloader protection and you want it on, because it protects you from flashing the wrong device bootloader and bricking your device.
If you can still get into download mode, you have nothing to worry about. In general, it's good to redownload the ROM again, make sure that it passes the md5 check, reboot, and reflash.

You don't have a brick. So you are lucky. Boot into download mode and flash N9005 ROM, preferably same one or later version.
Here - http://samsung-updates.com/device/?id=SM-N9005
Get for your region or any other one. Cheers!
And yh! UNINSTALL KIES! Leaving the drivers

Hi there,
This is what I get in Odin
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

thanks for that, I've gone ahead and downloaded the KSA version since I bought mine in Qatar and there was no Qatar ROM.
Just to be clear, what's the best way to flash it to my phone?

In my case I didn't have KIES running. I've also uninstalled it to be sure.
Kies seems to be useless since it doesn't event detect the note 3 as a supported device.

One more post. Tried three different cables now (Nokia, HTC One, and the Note 3 cable).
Tried all the different ports on my iMac (I'm on VMWARE Windows 8)
Tried downloading a stock ROM, tried Flashing with N9005 KSA version.
Got the same exact error, Complete(Write) operation failed

Are you trying to Root ur phone or Flash Stock ROM?

Same problem.
I have the self same problem.
I was trying to root the Note 3 (LTE) and got the FAIL error in red on ODIN 3.09.
Do I continue to try to root, or do I need to reinstall the stock ROM?
Any assistance appreciated for this idiot newbie.

Sothai said:
I have the self same problem.
I was trying to root the Note 3 (LTE) and got the FAIL error in red on ODIN 3.09.
Do I continue to try to root, or do I need to reinstall the stock ROM?
Any assistance appreciated for this idiot newbie.
Click to expand...
Click to collapse
Are you running 4.4 or 4.3?
Which root method are you using?

Thanks for the fast reply! I am running 4.4.2 and was attempting the ibitimes listed for method, but I am not yet allowed to post links. (Root Galaxy Note 3 LTE on Android 4.4.2 N9005XXUENB4 Stock Firmware [GUIDE])
The method said to get ODIN 3.09 and the CF Root package, which I did. Does this help, or can I provide any further info?

Sothai said:
Thanks for the fast reply! I am running 4.4.2 and was attempting the ibitimes listed for method, but I am not yet allowed to post links. (Root Galaxy Note 3 LTE on Android 4.4.2 N9005XXUENB4 Stock Firmware [GUIDE])
The method said to get ODIN 3.09 and the CF Root package, which I did. Does this help, or can I provide any further info?
Click to expand...
Click to collapse
Download and extract this file and flash through included odin.

amnesia said:
One more post. Tried three different cables now (Nokia, HTC One, and the Note 3 cable).
Tried all the different ports on my iMac (I'm on VMWARE Windows 8)
Tried downloading a stock ROM, tried Flashing with N9005 KSA version.
Got the same exact error, Complete(Write) operation failed
Click to expand...
Click to collapse
KSA has Jellybean 4.3 up to now that means u r trying to flash 4.3, before root process on which version u were, jelly bean or kitkat, I am not sure but your phone is seems to be for Singapore.

OK, many thanks. Downloading now.
It seems to be quite a large file, as my system says 44 minutes remaining - does that sound correct? May I ask what the file contains to be so large? Thanks!

Sothai said:
OK, many thanks. Downloading now.
It seems to be quite a large file, as my system says 44 minutes remaining - does that sound correct? May I ask what the file contains to be so large? Thanks!
Click to expand...
Click to collapse
It's about 20 meg in size. It contains odin and the cf auto root tar file.

OK, it's downloading, so delete the copies of ODIN and CF Root that I already have and use the ones in that bundle, yes?
I must admit that I am panicking here. The phone won't boot as it is, so I hope this will unbrick it as well as root it...

Sothai said:
OK, it's downloading, so delete the copies of ODIN and CF Root that I already have and use the ones in that bundle, yes?
I must admit that I am panicking here. The phone won't boot as it is, so I hope this will unbrick it as well as root it...
Click to expand...
Click to collapse
Yes use the one in the bundle.
Can you boot your phone in download mode though?

[Q] [i9505]: Won't boot into any OS / Recovery; only Download Mode

Hello,
My Galaxy S4 (i9505) won't boot into Recovery or Android. It only boots into Download Mode.
Before this failure when everything worked fine i updated xposed to it's latest version, then i had to reboot the system. It rebooted normally then when unlocking the screen Android 4.4.2 (GoldenEye ROM) froze. I pulled the battery out and retried it.
Next try: Same thing. The third time it even didn't want to show the lock screen, only up to the bootanimation, then my phone rebooted itself.
Xposed shouldn't be the problem here?​
I tried flashing a new rom, had troubles going into recovery so i flashed a new/other one with Odin (from PhilZ touch to TWRP) and then reinstalled my OS whis is GoldenEye and Ktoon kernel from extsd.
I didn't wipe data which i could see in recovery because i thought i don't want to loose anything, so i rebooted.
Then the next big problem, it doesn't boot android, stuck at Samsung Galaxy S4 GT-I9505 splash screen. Recovery won't come up, stuck at booting recovery. Flashed the newest PhilZ touch with Odin: nothing, same result.
I downloaded a stock ROM (I9505XXUGNF1_I9505YBTGNF2_I9505XXUGNF1_HOME.tar) from SamMobile and flashed it several times with my Notebook and PC, both running Windows 8.1
Samsung Drivers are installed.
I used Odin with and without PIT file, turned Auto Reboot off and flashed over again, tried a PreRooted Knox Free ROM (I9505XXUFNC9) but nothing works :/
Found a full wipe rom, so i flashed this. Yep my data are gone, but my phone is still dead...
Also removed my SIM and SD before booting to ensure that this is not the problem.
And Odin shows no error:
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Does something like eMMC Sudden Death exist on Galaxy S4 like it was on the Galaxy S3 and Note II?? :/, i hope not​
So does anybody know a solution how to fix my phone and get it running again? Don't want to loose my baby

raph6280 said:
Hello,
And Odin shows no error:
Click to expand...
Click to collapse
Is same "no error" shown in ROM flash? You presented screen info from recovery flash only.
I think that you messed with bootloader, so "resurrection" ROM would be needed...

Sounds to me like a hardware failure.
Xposed has nothing to do with being unable to enter the recovery.
Try flashing Philz again, make sure to uncheck auto-reboot. If it really won't boot and also flashing stock roms won't work, then you just had bad luck. Nothing you did that caused it. It's failed hardware then.

spamtrash said:
Is same "no error" shown in ROM flash? You presented screen info from recovery flash only.
I think that you messed with bootloader, so "resurrection" ROM would be needed...
Click to expand...
Click to collapse
Yes flashing with Odin works fine without any error but the device won't boot even with a clean stock rom in PDA
Is there any "resurrection" ROM or something similar?
Try flashing Philz again, make sure to uncheck auto-reboot. If it really won't boot and also flashing stock roms won't work, then you just had bad luck. Nothing you did that caused it. It's failed hardware then.
Click to expand...
Click to collapse
Flashed it without auto-reboot and still half dead :/
When it's a hardware failure how is it handled by Samsung with the knox warranty void flag because custom ROM and so on?

raph6280 said:
Is there any "resurrection" ROM or something similar?
Click to expand...
Click to collapse
It was for 4.3, here.
However with all KNOX mess, I am unsure if anything exists/leaked to us for 4.4.2.
Hmmm... you can try flashing the stock ROM with PIT file and repartition...

spamtrash said:
It was for 4.3, here.
However with all KNOX mess, I am unsure if anything exists/leaked to us for 4.4.2.
Hmmm... you can try flashing the stock ROM with PIT file and repartition...
Click to expand...
Click to collapse
Thanks, already tried this and over this i flashed the newest 4.4.2 ROM, i tried soo much but this beast won't come alive...
I will try it again with a pit, used one yesterday but that didn't work, eventually i'll find another to try that, i hope this makes a difference but my hopes are already gone :/

raph6280 said:
... but my hopes are already gone :/
Click to expand...
Click to collapse
Well, if your phone is:
a) dead (no warranty void in download mode)
b) covered by warranty
you could claim repair via Service Centre

spamtrash said:
Well, if your phone is:
a) dead (no warranty void in download mode)
b) covered by warranty
you could claim repair via Service Centre
Click to expand...
Click to collapse
I can boot into Download Mode, so sadly warranty void is shown
Bought my S4 over Amazon, hope they can do something.

raph6280 said:
I can boot into Download Mode, so sadly warranty void is shown
Bought my S4 over Amazon, hope they can do something.
Click to expand...
Click to collapse
Well, you shall learn the lesson... I have no idea how it looks in your country... in mine, I have the phone insurance bundled with Platinum bank account, and it is a very nice policy, covers "whatever happens". I have to pay a fee of 50 pounds per claim, and then I have repair/replacement.

I think it's not to bad, they repaired the small hardware issue which I caused on my old HTC for free and "updated" the software which I also had unlocked and rooted
Hope with that Samsung it is the same, eventually they see that this could be a hardware failure

raph6280 said:
Yes flashing with Odin works fine without any error but the device won't boot even with a clean stock rom in PDA
Is there any "resurrection" ROM or something similar?
Flashed it without auto-reboot and still half dead :/
When it's a hardware failure how is it handled by Samsung with the knox warranty void flag because custom ROM and so on?
Click to expand...
Click to collapse
If Linz is located in Austria, then the shop where you bought it from has to repair it. No rooting, custom rom can free them from their obligation. That is regulated by EU-law.

Soft Bricked S4!

So I tried rooting my phone and did so succesfully, I then went on and tried to install a custom ROM, so I backed up my current ROM using the CWM Recovery and went to install the ROM being sure to factory reset first, something went wrong and so I used the backup file I made before.
The backup file seemed to be corrupted and now I'm left with my phone that just goes into the recovery mode when I turn it on.
Help? It's an i9506

In short
In short, could someone just link me to a ROM of any sort suitable for the i9506

have a look on samsung - updates dot com
take a "old" firmware before 06-2014

Do you know of any other ROM's? That one will take almost 8 hours to download because of their stupid attempt in making money and slowing downloads.

ungmon said:
Do you know of any other ROM's? That one will take almost 8 hours to download because of their stupid attempt in making money and slowing downloads.
Click to expand...
Click to collapse
Flash official rom. Download it from
Www.sammobile.com/firmwares
It wont take much time. But yeah..1-1.5gigs download takes time buddy..
Do press thanks if my posts are helpful
Sent from my Stock Deodexed i9500 :')

I had the same thing happen, and I did all of that including the whole flash counter reset thing, but now I'm stuck. I have a fully functioning phone, besides one thing: it's not activated. Now that wouldn't be a problem if I could actually activate it, but every time I try to activate it (*228), I get the Verizon wireless activation instead of US Cellular. I am in way over my head and have no idea what to do to try and fix this. I just want it back to stock at this point. Thanks in advance.

Thanks for all the help guys!, Ill let you know on how I go.
Was also wondering if anyone here had found any customs ROM's for the i9506 that would be sweet!

I'm still trying to fix this, the first ROM I downloaded took 18 hours and left me with this
<ID:0/004> FAIL! (Ext4) <ID:0/004> <ID:0/004> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1)
So I tried another ROM from SamMobile, same deal.
I found another ROM which was sucesful despite the fact that every 2 seconds a 'Unfortunately Samsung Keyboard has stopped working' error would appear.
I am so lost right now and on the verge of giving up and selling this phone can someone please help me or atleast provide me a ROM I could flash (i9506) please.

ungmon said:
I'm still trying to fix this, the first ROM I downloaded took 18 hours and left me with this
<ID:0/004> FAIL! (Ext4) <ID:0/004> <ID:0/004> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1)
So I tried another ROM from SamMobile, same deal.
I found another ROM which was sucesful despite the fact that every 2 seconds a 'Unfortunately Samsung Keyboard has stopped working' error would appear.
I am so lost right now and on the verge of giving up and selling this phone can someone please help me or atleast provide me a ROM I could flash (i9506) please.
Click to expand...
Click to collapse
try another usb port worked for me

galaxys4s5 said:
try another usb port worked for me
Click to expand...
Click to collapse
Tried, didn't work.

ungmon said:
Tried, didn't work.
Click to expand...
Click to collapse
maybe u got a problem with usb drivers?
restart pc
try odin 3.07
its odin fail not ur phone
did u put it in download mode

I'm using Odin 3.09, phone was in download mode

You managed to flash 1 stock rom right? Then flash that rom and perform a factory reset.

I do but it doesn't solve the "Unfortunately, Samsung Keyboard has stopped working" issue.

You should also know that I do have backup files but they show up with MD5 mismatch errors, I've tried various things to fix them but no cigar.
As you guys can see I'm reaaaaaaaly lost here.

I've successfully loaded Cyanogen mod onto my phone, questions, the cyanogen mod is 4.4.4 does that mean that I can't go back to 4.3 for a stock ROM?

This has got to be the most useless forum I've ever visited. Bye I'll figure this one out on my own.

ungmon said:
This has got to be the most useless forum I've ever visited. Bye I'll figure this one out on my own.
Click to expand...
Click to collapse
Bye :fingers-crossed:

[Q] Help Please Experts

:crying::crying::crying: I can`t flash my S4 SGH-M919V with odin, i try to flash any firmware lollipop 5.0.1 of GT-I9505 that is the same thing and others firmwares of 4.4.4 of the same model but always send me FAIL abort the operation.
I don`t know why when I put my s4 in odin mode show this information in small letters:
ODIN MODE
PRODUCT NAME: SGH-M919V
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enabled
MMC BURTS MODE: Enabled
One question the last lines maybe is the problem write protection enabled or not? if is yes the problem how i can fix it for flash any firmware on my s4 thanks for your time (if this post is in the wrong section please change thanks again) i hope solutions XDA-Developers

http://forum.xda-developers.com/galaxy-s4-tmobile is where you need to go for issues with your device, as that forum has far more people familiar with your S4. This is the international S4 forum.
Now, regarding Odin, you should be using a recent version of Odin (current is 3.10), the original cable connected directly to the computer, not using a hub, and not have Kies running. You may also need Samsung's drivers if you haven't installed Kies or downloaded them from Samsung, so if you haven't already downloaded them, do so. That said, attempting to flash an I9505 ROM to your device is automatically going to fail. Odin verifies the model number and other parameters in the S4 before it allows a flash to proceed. Naturally, the model numbers don't match and thus flashing the ROM will not work.
Write protection and MMC bursts modes are supposed to be enabled, so you can eliminate that as a concern.

Thanks for your anwer bro but so to try install a firmware of the same model of mine and the same error

Post your Odin log, so we can see where it fails.

This is mi phone information: i have install Albe95 rom
AP:I9505XXUHOA7
CP:M919VVLUFNH3
CSC:I9505OXAHOA7
This is the Error with any versión of odin and any firmware stock forma this model or :
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I9505XXUHOB7_I9505YXYHOB5_I9505XXUHOB7_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin v.3 engine (ID:17)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
sbl1.mbn
NAND Write Start!!
FAIL! (Auth)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Any solution? Thank s
I read some post and say it that write protection is enable never can't flash any firm help

Seriously? After telling you that you cannot install an I9505 ROM on your device and explaining why you can't, you're still trying?
YOU CANNOT INSTALL AN I9505 ROM ON A T-MOBILE S4! All attempts to do so will automatically fail. The only stock ROMs that will work on your device are T-Mobile ROMs.
What part of the above do you not understand? Tell me now so I can dumb things down.

i m understand all above OK
this log show with any firmware for the phone or t-mobile firmware men i triying to install stock firmwares for my mobile ok and don`t work of any way but thanks for your time and help :good::good::good: i waiting for more solutions or i read the link than you put above

@LE_17: I apologize for snapping. However I thought I had made it reasonably clear that you could not install an I9505 ROM on your device. Apparently this wasn't the case. In any event, your ROM is here.

that s ok bro no problem
thank s for your time but the link of the firmware that you post i have in my PC downloaded and when i flash it send the same error i dont know why :crying::crying::crying:

You may want to try a different computer completely. Odin is sometimes weird like that. It could also be that the ROM you're currently using may require some steps to get the correct version of Android back on the device, especially if going down from Android 5.x to Android 4.4.4.

Strephon Alkhalikoi said:
You may want to try a different computer completely. Odin is sometimes weird like that. It could also be that the ROM you're currently using may require some steps to get the correct version of Android back on the device, especially if going down from Android 5.x to Android 4.4.4.
Click to expand...
Click to collapse
You gave him a version for the T-mobile variant. He has a different variant. He has the SGH-M919V. It's really confusing al those different models.
Try to flash the latest version from here.
http://www.sammobile.com/firmwares/database/SGH-M919V/#firmware
if it fails, try different usb port and different usb cable.

Try using the latest version of Odin (v3.10.6) and see if you can flash the correct firmware for your rom.
http://forum.xda-developers.com/showthread.php?t=2711451
Try using a different USB port if its failing again and make sure your USB drivers are up to date

Ok man i try it thanks for your time and answer post the result

Lennyz1988 said:
You gave him a version for the T-mobile variant. He has a different variant. He has the SGH-M919V. It's really confusing al those different models.
Click to expand...
Click to collapse
Well color me silly. I did miss that, and I'm sure the OP did too as he mentioned already having that ROM.

LE_17 said:
Ok man i try it thanks for your time and answer post the result
Click to expand...
Click to collapse
If you're trying to flash the official Lollipop update for the S4, use the Canadian version. I tried using the Rogers version (as Videotron uses Rogers' network) from SamMobile and it worked perfectly well. I was even able to change my CSC to Rogers and get the update through Kies.
Disclaimer: If you choose to try this, it is at your own risks. I cannot be held responsible if your phone gets damaged in any way nor can I guarantee the results.

No need for this anymore! The SGHM919V has gotten the Lollipop update this morning.