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] brick after flashing kitkat

Hi,
here following what I did on my Note 3 (SM-N9005 model ) and some information that may help to find a solution:
ROM installed on the phone (original stock no rooted): N9005XXUDMJ7_N9005PHNDMJ4_N9005XXUDMJ7 (Nederlands)
ROM I tried to install: N9005XXUENA6_N9005VFGENA4_N9005XXUENA2 (Vodafone Italy)
Tool used: ODIN 3.0.9
I flashed as usual by using ODIN the new Rom but quite at the end of the process I got a "Write failure" error.
I noticed that "write protection is set to enable and I don't know if it's the root cause of the brick.
I tried to restore the previous version but I got "Sw version error with fuse/bin error indication" and after that I tried againto install kitkat rom and process stop again with the following error:
ID:0/019> system.img.ext4
<ID:0/019> modem.bin
<ID:0/019> cache.img.ext4
<ID:0/019> hidden.img.ext4
<ID:0/019> FAIL! (Size)
<ID:0/019>
<ID:0/019> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm not able to start in recovery mode, I got always the screen ending with UDC start and the yellow triangle inviting me to recovery with kies (of course Kies doesn't work!)
I read several similar topics but I'm not an expert and the result has been a big headache :crying: !
Please help me ! Does anyone may post a procedure that I can apply to get my Note back ?
I really appreciate it
Thank You in advance
Em

epl2005 said:
Hi,
here following what I did on my Note 3 (SM-N9005 model ) and some information that may help to find a solution:
ROM installed on the phone (original stock no rooted): N9005XXUDMJ7_N9005PHNDMJ4_N9005XXUDMJ7 (Nederlands)
ROM I tried to install: N9005XXUENA6_N9005VFGENA4_N9005XXUENA2 (Vodafone Italy)
Tool used: ODIN 3.0.9
I flashed as usual by using ODIN the new Rom but quite at the end of the process I got a "Write failure" error.
I noticed that "write protection is set to enable and I don't know if it's the root cause of the brick.
I tried to restore the previous version but I got "Sw version error with fuse/bin error indication" and after that I tried againto install kitkat rom and process stop again with the following error:
ID:0/019> system.img.ext4
<ID:0/019> modem.bin
<ID:0/019> cache.img.ext4
<ID:0/019> hidden.img.ext4
<ID:0/019> FAIL! (Size)
<ID:0/019>
<ID:0/019> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm not able to start in recovery mode, I got always the sceen ending with UDC start and the yellow triangle inviting me to recovery with kies (of course Kies doesn't work!)
I read several similar topics but I'm not an expert and the result has been a big headache :crying: !
Please help me ! Someone my post a procedure that I can apply to get my Note back ?
I really appreciate it
Thank You in advance
Em
Click to expand...
Click to collapse
First thing to realize. If you can get into Donwload mode, then your chances of full recovery from this issue are extremely high, so no worries.
Second, the write protection enabled feature is specifically for the bootloader itself to prevent the user from flashing a bootloader for another device and REALLY hard bricking it.
If I were in your shoes, I'd try another Stock ROM download. There are times where the ROMs get corrupted and don't flash correctly. I'd also reinstall the Kies drivers for windows, etc. just to make sure that they are working.

For some reason, not sure why, but people cannot flash Carrier firmware, you are better off trying the stock XEO Poland 4.4.2 then trying to switch across to Vodafone's FW
HERE is the XEO stock 4.4.2, try this and see.
EDIT: Write enabled etc has nothing to do with it afaik, if you are stuck on the screen inviting you to recovery with kies, it'll still let you flash the stock ROM -- Now this is all on the premise you don't have a HK Note version, I assume you do not.

donalgodon said:
First thing to realize. If you can get into Donwload mode, then your chances of full recovery from this issue are extremely high, so no worries.
Second, the write protection enabled feature is specifically for the bootloader itself to prevent the user from flashing a bootloader for another device and REALLY hard bricking it.
If I were in your shoes, I'd try another Stock ROM download. There are times where the ROMs get corrupted and don't flash correctly. I'd also reinstall the Kies drivers for windows, etc. just to make sure that they are working.
Click to expand...
Click to collapse
Thank for your hint.
Unfortunately PHN kitkat is not yet available so I'm downloading now XEO rom, I'll let you know

donalgodon said:
First thing to realize. If you can get into Donwload mode, then your chances of full recovery from this issue are extremely high, so no worries.
Second, the write protection enabled feature is specifically for the bootloader itself to prevent the user from flashing a bootloader for another device and REALLY hard bricking it.
If I were in your shoes, I'd try another Stock ROM download. There are times where the ROMs get corrupted and don't flash correctly. I'd also reinstall the Kies drivers for windows, etc. just to make sure that they are working.
Click to expand...
Click to collapse
radicalisto said:
For some reason, not sure why, but people cannot flash Carrier firmware, you are better off trying the stock XEO Poland 4.4.2 then trying to switch across to Vodafone's FW
EDIT: Write enabled etc has nothing to do with it afaik, if you are stuck on the screen inviting you to recovery with kies, it'll still let you flash the stock ROM -- Now this is all on the premise you don't have a HK Note version, I assume you do not.
Click to expand...
Click to collapse
XEO firmware has been successfully loaded :victory: !
Thank you very much to both of you for the suggestion !
In my shoes, what would you do now? Try again Vodafone rom or wait for Italian no brand 4.4 ?

epl2005 said:
XEO firmware has been successfully loaded :victory: !
Thank you very much to both of you for the suggestion !
In my shoes, what would you do now? Try again Vodafone rom or wait for Italian no brand 4.4 ?
Click to expand...
Click to collapse
As you are able to recover you can try BUT you might have another failure. As stated above carrier roms seem to fail for some reason.
If it does then you should be able to flash Poland 4.4.2 again to recover.
Are you willing to try again with the potential of bricking?

Definitely I don't try to update to carrier rom till the reason of failure will be discovered. As I own vodafone branded S-view cover and it doesn't work with xeo rom only doubt I still have is if in that rom vodafone removed S-view issue at least for their cover
I don't think so but maybe someone was able to flash it can clarify that Anyone ?
By the way is there anybody that was able to load successfully vodafone rom ? Please give me a feedback ?
Inviato dal mio SM-N9005 utilizzando Tapatalk

Need Big Help with 900F

Recently I have received Galaxy S5 from my friend. It's model name as SM-G900F under battery. Have Single sim port and one imei. But when I switch on starting with "Samsung Galaxy S5 Duos" logo and started normally. After that when check the product details on "About Device", Product Name as SM-G900FD. But there's no two sim slots. and also showing two imei's when dial *#06#. Seems to be someone has done something. So now I want to take it back to original situation. Is it possible? Needs to convert G900F. Please if some one can help me. :crying:

eranda84 said:
Recently I have received Galaxy S5 from my friend. It's model name as SM-G900F under battery. Have Single sim port and one imei. But when I switch on starting with "Samsung Galaxy S5 Duos" logo and started normally. After that when check the product details on "About Device", Product Name as SM-G900FD. But there's no two sim slots. and also showing two imei's when dial *#06#. Seems to be someone has done something. So now I want to take it back to original situation. Is it possible? Needs to convert G900F. Please if some one can help me. :crying:
Click to expand...
Click to collapse
u can make it over Kies with Firmware Update and Initialization u need the model nr and the seriel nr there .. That i would do but if u not want kies u can also flash a stock G900f rom with odin .. b4 conect make phone off and remove battery for 10 sec .. then insert and go to download mode and flash the rom with odin

4Smoky said:
u can make it over Kies with Firmware Update and Initialization u need the model nr and the seriel nr there .. That i would do but if u not want kies u can also flash a stock G900f rom with odin .. b4 conect make phone off and remove battery for 10 sec .. then insert and go to download mode and flash the rom with odin
Click to expand...
Click to collapse
Thank you for valuable reply. I didn't try yet first step. But I tried second. This is I got error message.
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<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> aboot.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)
Please Please help me
I tried here flash Android 6. But my mobile currently run Android 5. So do I wanna flash Similar rom?

eranda84 said:
Thank you for valuable reply. I didn't try yet first step. But I tried second. This is I got error message.
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<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> aboot.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)
Please Please help me
I tried here flash Android 6. But my mobile currently run Android 5. So do I wanna flash Similar rom?
Click to expand...
Click to collapse
lol some think is not normal
what is written in download mode !!!
ty to flash 900f with another stock rom ( if no work ty with to change pit to successful )

popmpopm said:
lol some think is not normal
what is written in download mode !!!
ty to flash 900f with another stock rom ( if no work ty with to change pit to successful )
Click to expand...
Click to collapse
if you don't mind can you get me steps? Which region pt file? (KLTE_EURO_OPEN?)

No help?

Boot into download mode (Volume Down & Home & Power)
See which model it says there, that is the model you can trust

*Detection* said:
Boot into download mode (Volume Down & Home & Power)
See which model it says there, that is the model you can trust
Click to expand...
Click to collapse
It's G900FD. But this is only have single sim slot. And behind the battery compartment it says 900F.
So seems to be this is modified.:crying::crying:

if anyone can help me i'll help him / her to buy a beer

Use Kies 3
eranda84 said:
if anyone can help me i'll help him / her to buy a beer
Click to expand...
Click to collapse
Im also a G900F owner and I've been in a similiar situation. Download and install Samsung Kies 3(if you hadn't yet), just as the first reply said. On your S5, enter the Download/Odine mode by pressing VolDown+Home+Power Button and connect to PC with your USB. Open Kies 3, go Tools>Firmware upgrade and initialization. In the pop-up windows enter your model name, in your case I suppose its SM-G900F. You'll be asked for the serial number of your phone which is underneath the battery. Its written something like S/N: .... If correct, Kies will start downloading the correct firmware. The process is pretty much automatical, so just wait
After it is done, remove the USB, and the phone will (hopefully) reboot into latest stock version.

eranda84 said:
It's G900FD. But this is only have single sim slot. And behind the battery compartment it says 900F.
So seems to be this is modified.:crying::crying:
Click to expand...
Click to collapse
Forget stickers and firmware model numbers, they can all be modified to look like a different model, usually G900F
If your phone says G900FD in download mode, then your phone is G900FD, or at least the board is

*Detection* said:
Forget stickers and firmware model numbers, they can all be modified to look like a different model, usually G900F
If your phone says G900FD in download mode, then your phone is G900FD, or at least the board is
Click to expand...
Click to collapse
@*Detection* if it was hardware wise an FD it'd have 2 physical sim card slots, the OP says there is only one. In this case, download mode is wrong.....there's something else going on here. And before the OP does *anything* else I'd advise him to back up his IMEI/EFS folder, I've a feeling it's gonna be *critically important* that he does this......
http://i.imgur.com/rVnFwJM.jpg

heisenberg281 said:
Im also a G900F owner and I've been in a similiar situation. Download and install Samsung Kies 3(if you hadn't yet), just as the first reply said. On your S5, enter the Download/Odine mode by pressing VolDown+Home+Power Button and connect to PC with your USB. Open Kies 3, go Tools>Firmware upgrade and initialization. In the pop-up windows enter your model name, in your case I suppose its SM-G900F. You'll be asked for the serial number of your phone which is underneath the battery. Its written something like S/N: .... If correct, Kies will start downloading the correct firmware. The process is pretty much automatical, so just wait
After it is done, remove the USB, and the phone will (hopefully) reboot into latest stock version.
Click to expand...
Click to collapse
Hey man, this is pretty cool until it's started installed to mobile, but it's not continue. Because below error message appeared on mobile with red letters.
"secure check fail : pit" what should I do now? Please need assistance. :good:

keithross39 said:
@*Detection* if it was hardware wise an FD it'd have 2 physical sim card slots, the OP says there is only one. In this case, download mode is wrong.....there's something else going on here. And before the OP does *anything* else I'd advise him to back up his IMEI/EFS folder, I've a feeling it's gonna be *critically important* that he does this......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
@ *keithross39* hey sir, please help me on this.... :crying::crying::crying:

There are only three things we can be sure of right now.
1) It's not the FD variant simply because of the lack of a second sim slot.
2) It's not the H variant because the H variant wouldn't run the FD firmware.
3) Your device is ONE of the Qualcom quad core single sim variants.
Now....Here's the tricky part. You say your device has 2 imei numbers.....If you start flashing firmwares that are written to work with a single sim card, one of those IMEI numbers is probably going to get deleted.....If it's the wrong one, you're well and truly stuffed. So you need to find a way to back them up.
Most IMEI/EFS backup utilities require root access.
For now, you're going to have to treat your phone as if it actually *IS* the FD variant and find a root method that works on that variant.
Then once you have root, you can make that all important IMEI/EFS backup.
Once you have that, *then and only then* will it be time to think about how to return the OS to a single sim configuration.
Edit.....
This thread.....
http://forum.xda-developers.com/showthread.php?t=2829293
Gives info about rooting. But beware, if you haven't already done so, rooting will trip KNOX which will torpedo any idea of warranty repair.....
Edit 2....
This should help with the IMEI/EFS backup.....
http://forum.xda-developers.com/galaxy-s3/development/efs-samsung-tool-universal-support-t2602325
(It works on my 900F)
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
There are only three things we can be sure of right now.
1) It's not the FD variant simply because of the lack of a second sim slot.
2) It's not the H variant because the H variant wouldn't run the FD firmware.
3) Your device is ONE of the Qualcom quad core single sim variants.
Now....Here's the tricky part. You say your device has 2 imei numbers.....If you start flashing firmwares that are written to work with a single sim card, one of those IMEI numbers is probably going to get deleted.....If it's the wrong one, you're well and truly stuffed. So you need to find a way to back them up.
Most IMEI/EFS backup utilities require root access.
For now, you're going to have to treat your phone as if it actually *IS* the FD variant and find a root method that works on that variant.
Then once you have root, you can make that all important IMEI/EFS backup.
Once you have that, *then and only then* will it be time to think about how to return the OS to a single sim configuration.
Edit.....
This thread.....
http://forum.xda-developers.com/showthread.php?t=2829293
Gives info about rooting. But beware, if you haven't already done so, rooting will trip KNOX which will torpedo any idea of warranty repair.....
Edit 2....
This should help with the IMEI/EFS backup.....
http://forum.xda-developers.com/galaxy-s3/development/efs-samsung-tool-universal-support-t2602325
(It works on my 900F)
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
1) Yes. That's pretty sure me too.
2) Not a H variant
3) Yes.
As I mentioned first post there's two IMEI numbers. But none of those not similar to sticker under battery compartment. (Not match with any of those)
I have rooted mobile using "CF-Auto-Root-klte-klteduosxx-smg900fd". And it's successfully rooted.
And I did IMEI/EFS backup using "Samsung Tool". Now what should I do as a next step?

First thing to do is copy that backup 'off device'......If you have a removable micro sd card, copy it to that.....If not copy it to your pc or even cloud storage.....it's no good having a backup stored in device if the in device storage is formatted in my next suggestion......which is to flash not only a firmware, but a pit file too. I'd suggest using sammobile or samsung updates for the 900F firmware (the F variant firmware is as good a place to start as any) and the resources of XDA to locate the correct pit file. You can check here for pit files.....
S5 pit files (3rd post)
http://forum.xda-developers.com/showthread.php?t=2737448
But as it is now 3.52 AM where I am, I'm going to bed.....My kids will be up in about 4 hours so I need to get *some* sleep.....lol
Final edit for tonight......
As an alternative, you could forget about a firmware entirely, and go the custom rom route......just a thought.....
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
First thing to do is copy that backup 'off device'......If you have a removable micro sd card, copy it to that.....If not copy it to your pc or even cloud storage.....it's no good having a backup stored in device if the in device storage is formatted in my next suggestion......which is to flash not only a firmware, but a pit file too. I'd suggest using sammobile or samsung updates for the 900F firmware (the F variant firmware is as good a place to start as any) and the resources of XDA to locate the correct pit file. You can check here for pit files.....
S5 pit files (3rd post)
http://forum.xda-developers.com/showthread.php?t=2737448
But as it is now 3.52 AM where I am, I'm going to bed.....My kids will be up in about 4 hours so I need to get *some* sleep.....lol
Final edit for tonight......
As an alternative, you could forget about a firmware entirely, and go the custom rom route......just a thought.....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Ok thank you sir and Hats off. :good:
Have a Good Night

I have tried everything but again failed in Re-partition. Now only one left. That's run a custom rom. Will see CM13 and back to stock rom.
But anyone can help me on pit file failed, please help me.

keithross39 said:
@*Detection* if it was hardware wise an FD it'd have 2 physical sim card slots, the OP says there is only one. In this case, download mode is wrong.....there's something else going on here. And before the OP does *anything* else I'd advise him to back up his IMEI/EFS folder, I've a feeling it's gonna be *critically important* that he does this......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Never to date have we seen or heard of download mode being wrong, and CF AR for the G900FD just worked for OP
And if it turns out to be wrong, we both have a LOT of threads to edit when we have told other members to always trust download mode
To my knowledge, there is no way to reprogram the chip on the board to change the model number in download mode, maybe the phone is a fake
@ OP - can you post a photo of the back of the phone, with the back cover removed, so we can see the physical location of the SIM slot?
Edit out the IMEI etc if it shows on a sticker

Cant Unroot S4 I9505

Hi guys, looking for a little help / advice.
I have a UK Galaxy S4 (I9505) which is rooted and running CM12.01 ROM.
I am trying to Unroot and restore a stock rom via Odin, but it always fails.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1101)..
<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> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried different versions of the firmware, different versions of Odin. Changed USB cables and ports, but always the same error. Any advice greatly appreciated.
Thanks

Are you flashing the newest firmware available?

GDReaper said:
Are you flashing the newest firmware available?
Click to expand...
Click to collapse
I think so....
the file is: I9505XXUHOD7_I9505EVRHOD1_I9505XXUHOD7_HOME.tar.md5

flashing original rom for samobile.

johnfree98 said:
flashing original rom for samobile.
Click to expand...
Click to collapse
that is originlal ROM from sammobile as far as I know.

the version bootloader and modem to be the same that gives you the cm

johnfree98 said:
the version bootloader and modem to be the same that gives you the cm
Click to expand...
Click to collapse
not quite sure what u mean, could you explain please...

mrmcox said:
not quite sure what u mean, could you explain please...
Click to expand...
Click to collapse
I think he wants to say that you should try and flash a ROM with the same baseband you currently have.
You could also try another windows. Windows 7 always worked for me, but Windows 10 gave me some problems.

GDReaper said:
I think he wants to say that you should try and flash a ROM with the same baseband you currently have.
You could also try another windows. Windows 7 always worked for me, but Windows 10 gave me some problems.
Click to expand...
Click to collapse
So the baseband from the custom ROM that is installed is L720TVPUCOH1. Which official stock ROM should I try ?
Thanks in advance...

mrmcox said:
So the baseband from the custom ROM that is installed is L720TVPUCOH1. Which official stock ROM should I try ?
Thanks in advance...
Click to expand...
Click to collapse
The one with the same baseband. It's worth a try.

GDReaper said:
The one with the same baseband. It's worth a try.
Click to expand...
Click to collapse
Ok, I've found a Stock ROM with the same baseband, but its a US Sprint based ROM, and I have a UK based phone....Will this be ok ?

No. Odin does version checking to confirm that the firmware actually is for the device it is being flashed upon and will fail on a mismatch.
It sounds to me however that you might possibly have a Frankenphone, since you should not be able to install a Sprint bootloader on an international device. Would you please enter Download Mode and read off the model number posted on the screen? This is just to confirm that you really do have an I9505, and not another device masquerading as one.

Strephon Alkhalikoi said:
No. Odin does version checking to confirm that the firmware actually is for the device it is being flashed upon and will fail on a mismatch.
It sounds to me however that you might possibly have a Frankenphone, since you should not be able to install a Sprint bootloader on an international device. Would you please enter Download Mode and read off the model number posted on the screen? This is just to confirm that you really do have an I9505, and not another device masquerading as one.
Click to expand...
Click to collapse
Thanks for the reply..... I had already attempted to install the stock ROM I mentioned above, and It actually worked...
I just went into the Download mode, and checked the product number which now says SPH-L720T.. I also checked this in the "about device" section on the phone, which now gives the same info..... But I'm almost certain it said I9505 last time..
Is this going to be a problem, or should the phone just carry on as normal now ?
Thanks again

mrmcox said:
Thanks for the reply..... I had already attempted to install the stock ROM I mentioned above, and It actually worked...
I just went into the Download mode, and checked the product number which now says SPH-L720T.. I also checked this in the "about device" section on the phone, which now gives the same info..... But I'm almost certain it said I9505 last time..
Is this going to be a problem, or should the phone just carry on as normal now ?
Thanks again
Click to expand...
Click to collapse
The "about device" info can be changed very easily. You could make it show that your device is a S7 and is running iOS.
Download mode info is hard-coded.
So your device always was, and will be, a SPH-L720T

And since it's a Sprint phone, there is one major thing to keep in mind. In the UK and on the European continent, that phone will not get LTE service. The radio in the phone expects to see American channels and won't pick up the European ones. This is like my S4, but only in reverse. In my case, my S4 expects European channels as it's an I9505 and doesn't see American channels.
The only exception to the above is if the original owner managed to rewrite the Qualcomm chip to enable European bands.

GDReaper said:
Download mode info is hard-coded.
So your device always was, and will be, a SPH-L720T
Click to expand...
Click to collapse
This is what I don't understand....As I said, I am almost certain, that this used to say GT I9505, and was definitely an LTE version. I have used this phone on 4G networks. The phone was purchased in the UK direct from EE as a network upgrade. Could something I have done have messed this up ? and anyway to restore it ?

mrmcox said:
This is what I don't understand....As I said, I am almost certain, that this used to say GT I9505, and was definitely an LTE version. I have used this phone on 4G networks. The phone was purchased in the UK direct from EE as a network upgrade. Could something I have done have messed this up ? and anyway to restore it ?
Click to expand...
Click to collapse
It used to say GT-I9505 in download mode?

GDReaper said:
It used to say GT-I9505 in download mode?
Click to expand...
Click to collapse
I'm almost certain it did...not 100% sure, but 80-90% positive it did.... is that possible ? or am I just probably mistaken ?

mrmcox said:
I'm almost certain it did...not 100% sure, but 80-90% positive it did.... is that possible ? or am I just probably mistaken ?
Click to expand...
Click to collapse
I highly doubt it did.
I don't think the info displayed in download mode can be modified. Even if it can, I doubt it is an easy process to do. And flashing different ROMs is 100% not going to change it.
Download mode is similar to the bios of a PC, as I believe it's installed on the phone's motherboard itself, just like a PC's bios.

GDReaper said:
I highly doubt it did.
I don't think the info displayed in download mode can be modified. Even if it can, I doubt it is an easy process to do. And flashing different ROMs is 100% not going to change it.
Download mode is similar to the bios of a PC, as I believe it's installed on the phone's motherboard itself, just like a PC's bios.
Click to expand...
Click to collapse
Is there any way to try and convert it to I9505 baseband, as now it wont receive any data signal in uk, which it always did before. if so how can I do this, and what files should I be looking for ?
thanks