Database Users

[Q] Help! Trouble after upgrade to 4.3

Hi guys i would really appreciate the help!!!
I am not sure if my I9500 is bricked. I flash UEMJ5 onto my S4 and flashed Adam Kernel onto it after flashing some other stuff, my phone just wont boot up! I cant enter recovery mode and it boots to "Firmware upgrade encountered an issue." when it try flashing an official firmware through Odin i get this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500UBUEMJ5_I9500UUBEMJ5_I9500UBUEMJ5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
I can only boot in to Download Mode and when i click vol + to continue i also see Warranty Bit: 1 .. im guessing it has to do with Knox
Please i need help with this .
Thanks in advance.

Did you try a differnt usb port, reinstall drivers, make sure Kies is not running in the background, different cable?

Lennyz1988 said:
Did you try a differnt usb port, reinstall drivers, make sure Kies is not running in the background, different cable?
Click to expand...
Click to collapse
Thanks for the help, the only way i was able to solve was upgrading to UEMJ8 firmware through ODIN, wasnt able to flash a downgrade or same firmware i had. Warranty is void now, show: WARRANTY BIT: 1
And i am afraid to root now.

moibajan said:
Thanks for the help, the only way i was able to solve was upgrading to UEMJ8 firmware through ODIN, wasnt able to flash a downgrade or same firmware i had. Warranty is void now, show: WARRANTY BIT: 1
And i am afraid to root now.
Click to expand...
Click to collapse
If knox is already 0x1, then just go ahead and root. Nothing you can trip anymore.

[Q] How to root after the latest update ?

Hi all,
I've just updated my Note3 SM-N9005 via kies to Build number N9005XXUDMK2 and now I can't flash root, It fails every time...
My version is N9005XXUDMJ7 and my build number is N9005XXUDMK2.
I don't know if it has something to do with it, but when I enter download node I see a gray line saying: "Write protection: Enabled".
Can anyone please tell me how can I gain root access again ?
I'm tring to flash this file: "CF-Auto-Root-hlte-hltexx-smn9005.tar.md5" with "Odin3 v3.09.exe"
which I found in this site: http://true-android.blogspot.co.il/2013/12/root-n9005xxudmk2-galaxy-note-3-sm.html

frliran said:
Hi all,
I've just updated my Note3 SM-N9005 via kies to Build number N9005XXUDMK2 and now I can't flash root, It fails every time...
My version is N9005XXUDMJ7 and my build number is N9005XXUDMK2.
I don't know if it has something to do with it, but when I enter download node I see a gray line saying: "Write protection: Enabled".
Can anyone please tell me how can I gain root access again ?
I'm tring to flash this file: "CF-Auto-Root-hlte-hltexx-smn9005.tar.md5" with "Odin3 v3.09.exe"
which I found in this site: http://true-android.blogspot.co.il/2013/12/root-n9005xxudmk2-galaxy-note-3-sm.html
Click to expand...
Click to collapse
Can you paste the Odin log after it fails?
Also you may have the new updated CF Root which has been adapted for KitKat and doesn't work with 4.3 anymore.

Here is the log from odin
radicalisto said:
Can you paste the Odin log after it fails?
Also you may have the new updated CF Root which has been adapted for KitKat and doesn't work with 4.3 anymore.
Click to expand...
Click to collapse
<ID:0/007> 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/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I even tries using the same root file I did the first time I rooted my phone...

frliran said:
<ID:0/007> 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/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I even tries using the same root file I did the first time I rooted my phone...
Click to expand...
Click to collapse
Gave the same error using the original file you used from the first time? -- It is possible it doesn't like MK2, however it should work because I used it fine when I was on it.. Try re-downloading it again and trying again (I don't have it anymore, only the KK version )

Here is the log of the first file
radicalisto said:
Gave the same error using the original file you used from the first time? -- It is possible it doesn't like MK2, however it should work because I used it fine when I was on it.. Try re-downloading it again and trying again (I don't have it anymore, only the KK version )
Click to expand...
Click to collapse
The previous log was from the new file I downloaded today.
This is the log from "Odin3 v3.07" using the first file I rooted my phone with:
<ID:0/007> 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/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE...Can you please help me to re-root my phone.
(And if you can, please send me a link to download root for the KitKat version so that I can re-root it when the update will rollout in my country.)

Just to double check -- you are flashing it via the PDA option correct? and you have unrar'd it so you can see the tar.md5 file ?

yes
radicalisto said:
Just to double check -- you are flashing it via the PDA option correct? and you have unrar'd it so you can see the tar.md5 file ?
Click to expand...
Click to collapse
Yes I am.
But in odin 3.9 there is AP and not PDA.
But I tried both in both odin versions: 3.7 and 3.9.
In odin 3.7 I am using PDA, and in odin 3.9 I am using AP.

Hmm I am stumped I'm afraid. Usually re-flashing it normally works. See if anyone else will chime in and know the answer.

)-;
radicalisto said:
Hmm I am stumped I'm afraid. Usually re-flashing it normally works. See if anyone else will chime in and know the answer.
Click to expand...
Click to collapse
Do you think doing "Wipe cache partition" can fix it ? I don't realy knkow what it means...
Can you please send me a download link for rooting after updating to KitKat ? So I could use it when the update rolls out in my country

frliran said:
Do you think doing "Wipe cache partition" can fix it ? I don't realy knkow what it means...
Can you please send me a download link for rooting after updating to KitKat ? So I could use it when the update rolls out in my country
Click to expand...
Click to collapse
When it rolls out it may be a different version of KK than is currently compatible with CR Root. Better waiting til it comes out then seeing what is available.
**[Side Note... If you want KK now you can flash the Official XEO version depending on your Model (IF Hong Kong then it won't work) - and you can root on that without issue after flashing, but you cannot go bac to 4.3 again]**

hmmm
radicalisto said:
When it rolls out it may be a different version of KK than is currently compatible with CR Root. Better waiting til it comes out then seeing what is available.
**[Side Note... If you want KK now you can flash the Official XEO version depending on your Model (IF Hong Kong then it won't work) - and you can root on that without issue after flashing, but you cannot go bac to 4.3 again]**
Click to expand...
Click to collapse
I prefer to wait till an official KK will roll out and update via kies.
Can you please tell me if I do "Wipe cache partition" will fix the root failure probloem ?
I don't realy know what this wipe does...

Solved it (-:
frliran said:
I prefer to wait till an official KK will roll out and update via kies.
Can you please tell me if I do "Wipe cache partition" will fix the root failure probloem ?
I don't realy know what this wipe does...
Click to expand...
Click to collapse
On the settings page under security..make sure you have reactivation lock uncheck...
Than try again..that's usually the problem

It's always something so simple, Not turned activation lock on myself so never had an issue with it. Glad you got sorted thouugh.

Thank you very much for your help
radicalisto said:
It's always something so simple, Not turned activation lock on myself so never had an issue with it. Glad you got sorted thouugh.
Click to expand...
Click to collapse
Yes (-:
Thanl you very much for your help and consideration

[Q] Bricked N9007?

Ok, so today I tried to root my Note 3 N9007 via Odin 3.07 and autoroot files from chainfire. BUT, it seems like it doesnt worked... I did everything what was said in the tutorial here in the forum but no luck... Now I am stuck in Odin mode:
Current binary: Custom
System status: Official
Reactivation lock: OFF
Knox kernel lock: 0x0
Knox varanty: 0x0
Qualcomm secureboot: Enable
Write protection: Enable
Now log the from odin:
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-htdlte-htdltedi-smn9007.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks........

mkotruch said:
Ok, so today I tried to root my Note 3 N9007 via Odin 3.07 and autoroot files from chainfire. BUT, it seems like it doesnt worked... I did everything what was said in the tutorial here in the forum but no luck... Now I am stuck in Odin mode:
Current binary: Custom
System status: Official
Reactivation lock: OFF
Knox kernel lock: 0x0
Knox varanty: 0x0
Qualcomm secureboot: Enable
Write protection: Enable
Now log the from odin:
Removed!!
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
CF-Auto-Root-htdlte-htdltedi-smn9007.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
recovery.img
NAND Write Start!!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Thanks........
Click to expand...
Click to collapse
You tried root made for N9007 ??? Maybe a curropt dowload .try flashing again.
Btw to get back your device to work flash your official firmware through odin.
Sent from my SM-N9005 using Tapatalk

yep, it was a direct download from chainfire... IDK, hope the reflash will work... I am going to hang myself if it wont.

There are different files for 4.3 and 4.4

but not for 9007 bcs there is just Jelly Bean, no KitKat yet...
ok update, I am stuck with writing error... tried to flash official JB but still got the same error... anyone could help?

Used Odin 1.85? And right instructions.
Wipe cache and data reset

mkotruch said:
yep, it was a direct download from chainfire... IDK, hope the reflash will work... I am going to hang myself if it wont.
Click to expand...
Click to collapse
I'm guessing you have the Australian Optus device. If so I have the same one and successfully rooted mine (SM-N9007) last night without a problem! (Been running root apps ie. Titanium Backup and xposed framework)
I jumped on 'AndroidXDA.com' and downloaded CF-Auto-Root File from their guide. If your phone is bricked then download official firmware for SM-N9007 from sammobile and install using ODIN 3.09. Hopefully you'll be able to get it working.

Thanks, I managed to reinstall the stock rom and root it - the problem was with the usb connection, my pc has got problems with usb ports from time to time. So I switched to another pc and got it working

Need a TWRP Recovery MD5/WIN.000

Hello, everyone!
I recently have run into some trouble with my (ATT) Galaxy S4 (SGH-I337). I flashed a custom rom and (idiotically) didn't make a backup. Long story short, things didn't quite work out with the new rom. I didn't like it, and I wanted to go back to the old stock firmware. So I decided I would try to do it. I tried flashing with odin, using recovery, etc. Nothing worked so far. I've been researching for about 12 hours now. I think I know what I need. I need a TWRP backup, so that I can move it to the sd, and trick twrp into thinking I backed up my system so I can restore it. Below, I will link a post to what I want. The reason I can't use the below is because it's for a different carrier. If someone would be kind enough to link me something, that would be great. Again, my phone is a ATT Galaxy S4 (SGH-I337). Please help me out!
http://forum.xda-developers.com/showthread.php?t=2506562

Before I help you I want to be absolutely sure.
Are you sure you have an i9505? Because you keep saying ATT. That's a completely different phone. That's the SGH-I337. You can't flash stuff for the i9505 on the SGH-I337.
So what model do you have? Do you have an i9505 or the SGH-I337. My guess would be that you have the SGH-I337.
ps I have no idea what the thread is what you posted. Don't use that thread because its outdated.

Lennyz1988 said:
Before I help you I want to be absolutely sure.
Are you sure you have an i9505? Because you keep saying ATT. That's a completely different phone. That's the SGH-I337. You can't flash stuff for the i9505 on the SGH-I337.
So what model do you have? Do you have an i9505 or the SGH-I337. My guess would be that you have the SGH-I337.
ps I have no idea what the thread is what you posted. Don't use that thread because its outdated.
Click to expand...
Click to collapse
Yes, then I have an SGH-I337.

Lennyz1988 said:
Before I help you I want to be absolutely sure.
Are you sure you have an i9505? Because you keep saying ATT. That's a completely different phone. That's the SGH-I337. You can't flash stuff for the i9505 on the SGH-I337.
So what model do you have? Do you have an i9505 or the SGH-I337. My guess would be that you have the SGH-I337.
ps I have no idea what the thread is what you posted. Don't use that thread because its outdated.
Click to expand...
Click to collapse
Since I did in fact flash the wrong ROM, could I just reflash a new ROM that's compatible with my phone?

dillondonnelly1 said:
Since I did in fact flash the wrong ROM, could I just reflash a new ROM that's compatible with my phone?
Click to expand...
Click to collapse
Yes. You can flash a stock rom for your device.

Lennyz1988 said:
Yes. You can flash a stock rom for your device.
Click to expand...
Click to collapse
Alright, but for some reason I get an error in Odin. It says "SECURE CHECK FAIL". Do you have any idea what might cause this?

dillondonnelly1 said:
Alright, but for some reason I get an error in Odin. It says "SECURE CHECK FAIL". Do you have any idea what might cause this?
Click to expand...
Click to collapse
You need to give way more details.
- Post the complete log here.
- What are you trying to flash?
- What is your bootloader?

Lennyz1988 said:
You need to give way more details.
- Post the complete log here.
- What are you trying to flash?
- What is your bootloader?
Click to expand...
Click to collapse
- Post the complete log here.
Odin Log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004>
<ID:0/004> Receive Response from boot-loader
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Phone Log:
Product Name: SGH-I337
CURRENT BINARY: Samsung Official
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
Write PROTECTION: Enable
eMMC BURST MODE enabled
START [224,1440]
SW REV. CHECK FAIL : fused : 5 , Binary : 1
- What are you trying to flash? I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 (Stock ROM)
-What is your bootloader? (Safestrap)
Also, the firmware came with a SS_DL.dll file. Do I do anything with this file?

Odin won't flash?
Here are the logs. I'm trying to flash the stock firmware with odin, because currently, there is no rom on my device. I have an ATT SGH-I337. Please help.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004>
<ID:0/004> Receive Response from boot-loader
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Phone Log:
Product Name: SGH-I337
CURRENT BINARY: Samsung Official
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
Write PROTECTION: Enable
eMMC BURST MODE enabled
START [224,1440]
SW REV. CHECK FAIL : fused : 5 , Binary : 1

Its probably because you are flashing an old firmware on your new bootloader. What version where you previously on? 4.4.2? Then you can't flash a 4.2.2 rom.
ps stop opening new threads for this. You already got this thread.

Lennyz1988 said:
Its probably because you are flashing an old firmware on your new bootloader. What version where you previously on? 4.4.2? Then you can't flash a 4.2.2 rom.
ps stop opening new threads for this. You already got this thread.
Click to expand...
Click to collapse
Please tell me exactly what to do. I have to get my phone fixed by tonight.

dillondonnelly1 said:
Here are the logs. I'm trying to flash the stock firmware with odin, because currently, there is no rom on my device. I have an ATT SGH-I337. Please help.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004>
<ID:0/004> Receive Response from boot-loader
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Phone Log:
Product Name: SGH-I337
CURRENT BINARY: Samsung Official
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
Write PROTECTION: Enable
eMMC BURST MODE enabled
START [224,1440]
SW REV. CHECK FAIL : fused : 5 , Binary : 1
Click to expand...
Click to collapse
Hi mate ,
check if
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
Thanks to @samersh72
what software a re you flashing ? if you try to flash an older bootloader Odin will not allowed

[Help] My Phone won't boot (Samsung Galaxy S4)

Hi guys, i been searching for long time to resolve my issue and nothing found i think you guys could help me.
The issue is
My phone was rooted - Samsung Galaxy S4 - GT-I9505
And then i unrooted, but nothing to do with this, it was all oK..
After that i tried to upgrade the firmware from sammobile something like that..
I downloaded the new firmware I9505XXUGNG8_I9505MAXGNG1_I9505XXUGNG8_HOME.tar for my phone
And in the end of the line using Odin i got FAILED red box.. And since that i can't boot my phone stuck at Odin Mode: Firmware upgrade encountered an issue. Please select recovery mode in Kies & Try again. And up with small text says: Odin Mode, PRODUCT NAME: GT-19505, CURRENT BINARY: costum, SYSTEM STATUS: costum, KNOX KERNEL LOCK: 0x0, KNOX WARRANTY VOID: 0x1, CS0-CONFIG-LS8: 0x30, WRITE PROTECTION: enable, eMMc BURST MODE: enable
i tried with Kies but i can't connect , because i think after i unrooted, i reset my phone so USB debugging is not checked. I think for that. So i'm trying to install new firmwares with Odin and is not working i always get fail message red box, i tried all versions.
Does anyone know what to do please.
i Appreciate it.
Thanks.

GoodMan14 said:
Hi guys, i been searching for long time to resolve my issue and nothing found i think you guys could help me.
The issue is
My phone was rooted - Samsung Galaxy S4 - GT-I9505
And then i unrooted, but nothing to do with this, it was all oK..
After that i tried to upgrade the firmware from sammobile something like that..
I downloaded the new firmware I9505XXUGNG8_I9505MAXGNG1_I9505XXUGNG8_HOME.tar for my phone
And in the end of the line using Odin i got FAILED red box.. And since that i can't boot my phone stuck at Odin Mode: Firmware upgrade encountered an issue. Please select recovery mode in Kies & Try again. And up with small text says: Odin Mode, PRODUCT NAME: GT-19505, CURRENT BINARY: costum, SYSTEM STATUS: costum, KNOX KERNEL LOCK: 0x0, KNOX WARRANTY VOID: 0x1, CS0-CONFIG-LS8: 0x30, WRITE PROTECTION: enable, eMMc BURST MODE: enable
i tried with Kies but i can't connect , because i think after i unrooted, i reset my phone so USB debugging is not checked. I think for that. So i'm trying to install new firmwares with Odin and is not working i always get fail message red box, i tried all versions.
Does anyone know what to do please.
i Appreciate it.
Thanks.
Click to expand...
Click to collapse
Hi mate ,
You have to flash an stock rom with odin , there is no other solution
Check this thread , i will give you in detail how to proceed
http://forum.xda-developers.com/showthread.php?t=2265477

MAX 404 said:
Hi mate ,
You have to flash an stock rom with odin , there is no other solution
Check this thread , i will give you in detail how to proceed
http://forum.xda-developers.com/showthread.php?t=2265477
Click to expand...
Click to collapse
That's what he's doing. It should be working.
It MIGHT be because you have non official firmware on it now and it's not accepting the flash back to stock. IF that's the case the solution is to uncheck auto reboot in Odin and run the install sequence twice in a row. That's worth a shot here, but I don't think it's the solution.
Do you still have a working custom recovery? If so you should still be able to flash a custom ROM. I might try flashing a custom TouchWiz rom then starting over.

Still fail !
ty for reply guys, ok i captured everything
this is image when i browse the file on AP / PDA odin freezed for few seconds...
And this is what i got:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUGNG8_I9505MBMGNG1_I9505XXUGNG8_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!

GoodMan14 said:
ty for reply guys, ok i captured everything
this is image when i browse the file on AP / PDA odin freezed for few seconds...
And this is what i got:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUGNG8_I9505MBMGNG1_I9505XXUGNG8_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Click to expand...
Click to collapse
Hi ,
This is from the post i gave you earlier
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.
Check and see if it helps , did you try what Skipjacks said?

i di all
Hi, in this morning i tried again and passed.. finally
Thanks for helping.

GoodMan14 said:
Hi, in this morning i tried again and passed.. finally
Thanks for helping.
Click to expand...
Click to collapse
Great news mate
Sent from my Nexus 7 using XDA Premium 4 mobile app

Try flash stock firmware using odin