samsung galaxy s4 i9505
here is detail of download mod
currnt binary: samsung official
system status: custom
knox kernel lock: 0x0
know warrenty void: 0x1
csb-config-lsb: 0x3
what i try
flashing all these official rom with pass story
I9505XXUENAA, I9505XXUFNA5, I9505XXUFNB9, I9505XXUFNC9 and so on
after writing firmware doing wipe
flash with pit files tooo
flash with cutom roms
still no luck
set still in stuck with samsung
one more thing when it stuck at samsung screen have become some line like u press lcd tightly
experts tell me what i miss?
latest firmware succes story
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNC9_I9505OXEFNC1_I9505XXUFNC9_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/133> Added!!
<ID:0/133> Odin v.3 engine (ID:133)..
<ID:0/133> File analysis..
<ID:0/133> SetupConnection..
<ID:0/133> Initialzation..
<ID:0/133> Get PIT for mapping..
<ID:0/133> Firmware update start..
<ID:0/133> SingleDownload.
<ID:0/133> aboot.mbn
<ID:0/133> NAND Write Start!!
<ID:0/133> sbl1.mbn
<ID:0/133> sbl2.mbn
<ID:0/133> sbl3.mbn
<ID:0/133> rpm.mbn
<ID:0/133> tz.mbn
<ID:0/133> boot.img
<ID:0/133> recovery.img
<ID:0/133> system.img.ext4
<ID:0/133> modem.bin
<ID:0/133> NON-HLOS.bin
<ID:0/133> cache.img.ext4
<ID:0/133> hidden.img.ext4
<ID:0/133> RQT_CLOSE !!
<ID:0/133> RES OK !!
<ID:0/133> Removed!!
<ID:0/133> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Odin version
shahab uddin said:
samsung galaxy s4 i9505
here is detail of download mod
currnt binary: samsung official
system status: custom
knox kernel lock: 0x0
know warrenty void: 0x1
csb-config-lsb: 0x3
what i try
flashing all these official rom with pass story
I9505XXUENAA, I9505XXUFNA5, I9505XXUFNB9, I9505XXUFNC9 and so on
after writing firmware doing wipe
flash with pit files tooo
flash with cutom roms
still no luck
set still in stuck with samsung
one more thing when it stuck at samsung screen have become some line like u press lcd tightly
experts tell me what i miss?
latest firmware succes story
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNC9_I9505OXEFNC1_I9505XXUFNC9_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/133> Added!!
<ID:0/133> Odin v.3 engine (ID:133)..
<ID:0/133> File analysis..
<ID:0/133> SetupConnection..
<ID:0/133> Initialzation..
<ID:0/133> Get PIT for mapping..
<ID:0/133> Firmware update start..
<ID:0/133> SingleDownload.
<ID:0/133> aboot.mbn
<ID:0/133> NAND Write Start!!
<ID:0/133> sbl1.mbn
<ID:0/133> sbl2.mbn
<ID:0/133> sbl3.mbn
<ID:0/133> rpm.mbn
<ID:0/133> tz.mbn
<ID:0/133> boot.img
<ID:0/133> recovery.img
<ID:0/133> system.img.ext4
<ID:0/133> modem.bin
<ID:0/133> NON-HLOS.bin
<ID:0/133> cache.img.ext4
<ID:0/133> hidden.img.ext4
<ID:0/133> RQT_CLOSE !!
<ID:0/133> RES OK !!
<ID:0/133> Removed!!
<ID:0/133> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Change Odin 3.09 luck
Pika71 said:
Change Odin 3.09 luck
Click to expand...
Click to collapse
this logs from odin 3.09
Make sure you use the usb port on the back of your pc.
And it is unclear what your problem is.
Can you flash some roms Odin? Or can't you flash any roms with Odin?
ok...
Change 3.07 or 3.04
Related
Odin failed while updating to KitKat. I don't understand it as I have flashed roms before. Can anybody help on the message or what to do to restore it? It seems to be failing on a size issue but the MD5 checks are correct.
<ID:0/046> Removed!!
<ID:0/046> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA7_N9005DTMENA2_N9005XXUENA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/046> Odin v.3 engine (ID:46)..
<ID:0/046> File analysis..
<ID:0/046> SetupConnection..
<ID:0/046> Initialzation..
<ID:0/046> Get PIT for mapping..
<ID:0/046> Firmware update start..
<ID:0/046> SingleDownload.
<ID:0/046> aboot.mbn
<ID:0/046> NAND Write Start!!
<ID:0/046> sbl1.mbn
<ID:0/046> rpm.mbn
<ID:0/046> tz.mbn
<ID:0/046> sdi.mbn
<ID:0/046> NON-HLOS.bin
<ID:0/046> boot.img
<ID:0/046> recovery.img
<ID:0/046> system.img.ext4
<ID:0/046> modem.bin
<ID:0/046> cache.img.ext4
<ID:0/046> hidden.img.ext4
<ID:0/046> FAIL! (Size)
<ID:0/046>
<ID:0/046> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ALD2355 said:
Odin failed while updating to KitKat. I don't understand it as I have flashed roms before. Can anybody help on the message or what to do to restore it? It seems to be failing on a size issue but the MD5 checks are correct.
<ID:0/046> Removed!!
<ID:0/046> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA7_N9005DTMENA2_N9005XXUENA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/046> Odin v.3 engine (ID:46)..
<ID:0/046> File analysis..
<ID:0/046> SetupConnection..
<ID:0/046> Initialzation..
<ID:0/046> Get PIT for mapping..
<ID:0/046> Firmware update start..
<ID:0/046> SingleDownload.
<ID:0/046> aboot.mbn
<ID:0/046> NAND Write Start!!
<ID:0/046> sbl1.mbn
<ID:0/046> rpm.mbn
<ID:0/046> tz.mbn
<ID:0/046> sdi.mbn
<ID:0/046> NON-HLOS.bin
<ID:0/046> boot.img
<ID:0/046> recovery.img
<ID:0/046> system.img.ext4
<ID:0/046> modem.bin
<ID:0/046> cache.img.ext4
<ID:0/046> hidden.img.ext4
<ID:0/046> FAIL! (Size)
<ID:0/046>
<ID:0/046> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Looks to me like you need a PIT file. What variant are you running?
We are using Odin 3.09 and the tar file as above.
I don't think you need a pit file , have you re tried the odin flash ?
I used the polish NB3 version (multi csc)
It works on my BTU N9005
Sent from my SM-N9005 using xda app-developers app
---------- Post added at 10:34 PM ---------- Previous post was at 10:26 PM ----------
http://forum.xda-developers.com/showthread.php?p=50201265
Try the Poland multi csc
Sent from my SM-N9005 using xda app-developers app
There is no PIT file in the download from Sammobile. There is only one file for the PDA/PIT.
I have downloaded and tried a second copy and get the same as it gets to the end of the first section
<ID:0/046> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/046> Odin v.3 engine (ID:46)..
<ID:0/046> File analysis..
<ID:0/046> SetupConnection..
<ID:0/046> Initialzation..
<ID:0/046> Get PIT for mapping..
<ID:0/046> Firmware update start..
<ID:0/046> SingleDownload.
<ID:0/046> sbl1.mbn
<ID:0/046> NAND Write Start!!
<ID:0/046> aboot.mbn
<ID:0/046> rpm.mbn
<ID:0/046> tz.mbn
<ID:0/046> sdi.mbn
<ID:0/046> NON-HLOS.bin
<ID:0/046> boot.img
<ID:0/046> recovery.img
<ID:0/046> system.img.ext4
<ID:0/046> modem.bin
<ID:0/046> cache.img.ext4
<ID:0/046> hidden.img.ext4
<ID:0/046> FAIL! (Size)
<ID:0/046>
<ID:0/046> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ALD2355 said:
There is no PIT file in the download from Sammobile. There is only one file for the PDA/PIT.
Thanks for your help on this - this worked with the PIT file in place
Click to expand...
Click to collapse
ALD2355 said:
Odin failed while updating to KitKat. I don't understand it as I have flashed roms before. Can anybody help on the message or what to do to restore it? It seems to be failing on a size issue but the MD5 checks are correct.
<ID:0/046> Removed!!
<ID:0/046> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA7_N9005DTMENA2_N9005XXUENA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/046> Odin v.3 engine (ID:46)..
<ID:0/046> File analysis..
<ID:0/046> SetupConnection..
<ID:0/046> Initialzation..
<ID:0/046> Get PIT for mapping..
<ID:0/046> Firmware update start..
<ID:0/046> SingleDownload.
<ID:0/046> aboot.mbn
<ID:0/046> NAND Write Start!!
<ID:0/046> sbl1.mbn
<ID:0/046> rpm.mbn
<ID:0/046> tz.mbn
<ID:0/046> sdi.mbn
<ID:0/046> NON-HLOS.bin
<ID:0/046> boot.img
<ID:0/046> recovery.img
<ID:0/046> system.img.ext4
<ID:0/046> modem.bin
<ID:0/046> cache.img.ext4
<ID:0/046> hidden.img.ext4
<ID:0/046> FAIL! (Size)
<ID:0/046>
<ID:0/046> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
hv a look a this http://forum.xda-developers.com/showthread.php?t=2643572
Are trying to flash a carrier rom, it seems there's a problem when trying to flash these...
The reason I ask is carrier roms generally have the "hidden" partition and it almost always screws up there...
ultramag69 said:
Are trying to flash a carrier rom, it seems there's a problem when trying to flash these...
The reason I ask is carrier roms generally have the "hidden" partition and it almost always screws up there...
Click to expand...
Click to collapse
Thanks for the help in getting me out of the mess. I used these links:
Pit: http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Files: http://forum.xda-developers.com/showthread.php?p=50201265
ALD2355 said:
There is no PIT file in the download from Sammobile. There is only one file for the PDA/PIT.
I have downloaded and tried a second copy and get the same as it gets to the end of the first section
<ID:0/046> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/046> Odin v.3 engine (ID:46)..
<ID:0/046> File analysis..
<ID:0/046> SetupConnection..
<ID:0/046> Initialzation..
<ID:0/046> Get PIT for mapping..
<ID:0/046> Firmware update start..
<ID:0/046> SingleDownload.
<ID:0/046> sbl1.mbn
<ID:0/046> NAND Write Start!!
<ID:0/046> aboot.mbn
<ID:0/046> rpm.mbn
<ID:0/046> tz.mbn
<ID:0/046> sdi.mbn
<ID:0/046> NON-HLOS.bin
<ID:0/046> boot.img
<ID:0/046> recovery.img
<ID:0/046> system.img.ext4
<ID:0/046> modem.bin
<ID:0/046> cache.img.ext4
<ID:0/046> hidden.img.ext4
<ID:0/046> FAIL! (Size)
<ID:0/046>
<ID:0/046> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
DBT NB4 is faulty. Pit file error.
XEF NB4 works just fine. At least on unbranded phones
Sent from my SM-N9005 using Tapatalk
mikkelrev69 said:
DBT NB4 is faulty. Pit file error.
XEF NB4 works just fine. At least on unbranded phones
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. It works with th PIT file. There is no note on the download site so that's why I posted the links above as other people will experience the same problem as me.
ALD2355 said:
Thanks for the help in getting me out of the mess. I used these links:
Pit: http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Files: http://forum.xda-developers.com/showthread.php?p=50201265
Click to expand...
Click to collapse
No problem, happy you're back up and running... :good:
Hi guys i bricked my galaxy note 3 - n9005 and nothing help i ve been trying flash it with odin ,in recovery mode by zip roms - by zip rooms it got stuck on samsung galaxy note 3 title and nothing happen , i want to get my phone back to the stock 4.4.2 rom pls help me nothing works in odin , i ve been trying with those pit files and nothing works :
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Do you know what firmware you had before flashing this one?
Did you try another firmware?
Also, is reactivation lock off?
Does the firmware u flash need a pit?
to be honest with you guys im quite amateur in phone things i just wanted get my phone back to stock rom , before i had this rom N9005_JACKYAWAY_NB7.1 even now when i m trying to instal this one from sd card it gets stuck on the screen " SMASUNG GALASY NOTE 3 ". i m not sure this rom requires pit file or not i have been trying flash rom without this pit file and with this pit file - effect is the same :
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
Also, is reactivation lock off?
Click to expand...
Click to collapse
what does it mean ?
odin window :
ODIN MODE
PRODUCT NAME: SM-N9005
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK (KK): OFF
KNOX KERNEL LOCK: OXO
KNOX WARRANTY VOID: 0X1
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
WRITE PROTECTIONl: ENABLE
UDC START
jacek88zs said:
to be honest with you guys im quite amateur in phone things i just wanted get my phone back to stock rom , before i had this rom N9005_JACKYAWAY_NB7.1 even now when i m trying to instal this one from sd card it gets stuck on the screen " SMASUNG GALASY NOTE 3 ". i m not sure this rom requires pit file or not i have been trying flash rom without this pit file and with this pit file - effect is the same :
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
what does it mean ?
odin window :
ODIN MODE
PRODUCT NAME: SM-N9005
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK (KK): OFF
KNOX KERNEL LOCK: OXO
KNOX WARRANTY VOID: 0X1
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
WRITE PROTECTIONl: ENABLE
UDC START
Click to expand...
Click to collapse
ok.
try this. Go to : http://forum.xda-developers.com/showthread.php?t=2643109
download the latest czech NC2. This one no need pit file.
Just put it under PDA/AP, no need to tick repartition. Then after your phone connected, click start.
Your reactivation lock is OFF already, so no need to worry about this.
Ok thank you, i will try do as you said mate and i will let you know about results as soon as its possible ! hopefuly it will works because i started be worried about i spent lot of money and lost the phone hehe
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N9005XXUENA6_340325_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
STILL same problem with this czech rom ;///
Weird. Tat error is because the partition which need pit file.
Pardon me, if u don't mind, go to that thread again and download the firmware latest which need pit, download together with the pit, and flash again with repartition being ticked.
Sent from N7105, DN3 with AGNi kernel.
When Odin throws up that error, what does the download mode say?
It always appears when the odin is trying to flash the "system"
jacek88zs said:
It always appears when the odin is trying to flash the "system"
Click to expand...
Click to collapse
I meant, what error appears on the phone screen?
jacek88zs said:
Hi guys i bricked my galaxy note 3 - n9005 and nothing help i ve been trying flash it with odin ,in recovery mode by zip roms - by zip rooms it got stuck on samsung galaxy note 3 title and nothing happen , i want to get my phone back to the stock 4.4.2 rom pls help me nothing works in odin , i ve been trying with those pit files and nothing works :
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Your phone is failing on flashing the hidden partition which usually contains the CSC info etc etc
Try downloading this rom or simply to go http://forum.xda-developers.com/showthread.php?t=2643572 or http://forum.xda-developers.com/showthread.php?t=2643109
And which one should i download now and try to flash ? before i have been trying to flash czech ... but still wasgot stuck on " system "
system.img.ext
FAIL! (Ext4)
Guys which one is with pit file and which one propably should get over this bug ?
jacek88zs said:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N9005XXUENA6_340325_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
STILL same problem with this czech rom ;///
Click to expand...
Click to collapse
Also this isnt the stock C2 Rom if you check above it Says AP_N9005XXUENA6_340325_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid. try downloading a stock C2 rom from Sammobile or a mirror but make sure that you reset your phone through recovery once u successfly flash the rom.
i just pastet wrong text from expired window of odin sorry ,the correct was with like screen shows without this " AP_N9005XXUENA6_340325_REV03_user_low_ship_MULTI_C ERT.tar.md5 is valid. " i ve been trying to instal this czech one
jacek88zs said:
i just pastet wrong text from expired window of odin sorry ,the correct was with like screen shows without this " AP_N9005XXUENA6_340325_REV03_user_low_ship_MULTI_C ERT.tar.md5 is valid. " i ve been trying to instal this czech one
Click to expand...
Click to collapse
Try Odin 3.09 . Sometimes older version is the issue.
guys i have been tryin with different versions of odin ...same problem on every of them . Can someone tell me step by step what to do just apart of what to do in odin ,i know this ,which rom ,and what css files or whatever ? pls tell me in details how to do this , i propably have some korean version of phone ;/ its 16 gb note 3
jacek88zs said:
guys i have been tryin with different versions of odin ...same problem on every of them . Can someone tell me step by step what to do just apart of what to do in odin ,i know this ,which rom ,and what css files or whatever ? pls tell me in details how to do this , i propably have some korean version of phone ;/ its 16 gb note 3
Click to expand...
Click to collapse
What model does it show ??? remove the battery and look .
Sm-n9005 rf8f10pd75j
@jacek88zs : If urs is 16gb, I think u need a pit file. Urs is hongkong version I guess.
Take a look at this thread :
http://forum.xda-developers.com/showthread.php?t=2631628
Sent from N7105, DN3 with AGNi kernel.
samsung galaxy s4 i9505
here is detail of download mod
currnt binary: samsung official
system status: custom
knox kernel lock: 0x0
know warrenty void: 0x1
csb-config-lsb: 0x3
what i tru
flashing all these official rom with pass story
I9505XXUENAA, I9505XXUFNA5, I9505XXUFNB9, I9505XXUFNC9 and so on
after writing firmware doing wipe
flash with pit files tooo
flash with cutom roms
still no luck
set still in stuck with samsung
one more thing when it stuck at samsung screen have become some line like u press lcd tightly
experts tell me what i miss?
shahab uddin said:
samsung galaxy s4 i9505
here is detail of download mod
currnt binary: samsung official
system status: custom
knox kernel lock: 0x0
know warrenty void: 0x1
csb-config-lsb: 0x3
what i tru
flashing all these official rom with pass story
I9505XXUENAA, I9505XXUFNA5, I9505XXUFNB9, I9505XXUFNC9 and so on
after writing firmware doing wipe
flash with pit files tooo
flash with cutom roms
still no luck
set still in stuck with samsung
one more thing when it stuck at samsung screen have become some line like u press lcd tightly
experts tell me what i miss?
Click to expand...
Click to collapse
latest firmware succes story
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNC9_I9505OXEFNC1_I9505XXUFNC9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/133> Added!!
<ID:0/133> Odin v.3 engine (ID:133)..
<ID:0/133> File analysis..
<ID:0/133> SetupConnection..
<ID:0/133> Initialzation..
<ID:0/133> Get PIT for mapping..
<ID:0/133> Firmware update start..
<ID:0/133> SingleDownload.
<ID:0/133> aboot.mbn
<ID:0/133> NAND Write Start!!
<ID:0/133> sbl1.mbn
<ID:0/133> sbl2.mbn
<ID:0/133> sbl3.mbn
<ID:0/133> rpm.mbn
<ID:0/133> tz.mbn
<ID:0/133> boot.img
<ID:0/133> recovery.img
<ID:0/133> system.img.ext4
<ID:0/133> modem.bin
<ID:0/133> NON-HLOS.bin
<ID:0/133> cache.img.ext4
<ID:0/133> hidden.img.ext4
<ID:0/133> RQT_CLOSE !!
<ID:0/133> RES OK !!
<ID:0/133> Removed!!
<ID:0/133> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
no any other solution?
Try flashing the rom for your country and phone, the latest build with odin, latest modem, try and find the right pit file and flash all with odin, then after it passes and restarts, at samsung logo, go into recovery mode( vol up, home button and power button), wipe cache, and wipe data factory reset( from recovery also). Good luck. There is no such thing as stuck i9505 there is allways a solution
Evening all ,
Hopefully someone here can help , Im somewhat of a newbie to this but was currently running Xnote Rom on 4.3 , I tried to upgrade to N9005XXUGNG1 following steps read on a well known website.
I received a "invalid ext4 image" error from odin and now stuck in a soft brick state where i can only access download mode. I am currently trying to get out of this back to a stock phone. I live in the UK and am on EE 4G.
Thanks in advance
UPDATE: Tried flashing N9005XXUDMK2_N9005OXXDMK3_N9005XXUDMJ7_HOME.tar.md5 with the following results:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXXDMK3_N9005XXUDMJ7_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
hmm..
try this..
take battery out and put it back in after 30 seconds.. then boot to download mode..
use odin to flash the latest gng1 rom..make sure to tick update bootloader in odin
take another stock ROM, you partition sizes dont seem to match to the rom u want to flash. i suggest to use the latest BTU Android 4.4.2 rom ( sammobile.com/firmware )
Killberty said:
take another stock ROM, you partition sizes dont seem to match to the rom u want to flash. i suggest to use the latest BTU Android 4.4.2 rom ( sammobile.com/firmware )
Click to expand...
Click to collapse
Could you tell me which one , as the latest i can see is the GNG1 and i am not getting on well with that at present
xinfinityoO said:
hmm..
try this..
take battery out and put it back in after 30 seconds.. then boot to download mode..
use odin to flash the latest gng1 rom..make sure to tick update bootloader in odin
Click to expand...
Click to collapse
Same problem..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGNG1_N9005H3GGNG1_N9005XXUGNG1_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Just to let you whats on my download screen too :
the little android man
ODIN MODE
PRODUCT NAME - SM-N9005
CURRENT BINARY: SAMSUNG OFFICAL
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK(KK): OFF
KNOX KERNAL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2 T2 R2 A3 P1
WRITE PROTECTION: ENABLE
UDC START
ODIN : INVALID EXT4 IMAGE
Hope this helps ... And thanks for trying to help :cyclops:
Sometimes I get the android man and others I get a phone with a warning symbol and a pc saying " Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again".
Killberty said:
take another stock ROM, you partition sizes dont seem to match to the rom u want to flash. i suggest to use the latest BTU Android 4.4.2 rom ( sammobile.com/firmware )
Click to expand...
Click to collapse
It worked , Thank you !!! :good:
Its my first post so i would like to say hello to You all.
I have bricked my phone. I cant enter recovery mode and i dont have software installed. I have honkong version 16gb sm-n9005. When im trying to flash offical rom N9005XXUGBOJ6 (polish XEO) by Odin I have error:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBOJ6_N9005XEOGBOJ1_N9005XXUGBOJ1_HOME.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> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> boot.img
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> modem.bin
<ID:0/007> NON-HLOS.bin
<ID:0/007> recovery.img
<ID:0/007> rpm.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> sdi.mbn
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Ext4)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In my phone its writthen
ODIN MODE
PRODUCT NAME SM-N9005
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Reactivation Lock: OFF
Knox Warranty Void: 0x1 (3)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREW S2, T2, A2, A3, P3
SECURE DOWNLOAD ENABLE
UDC START
Volume Size is too big 4620288 < 4718592
ODIN : Invalid ext4 image
I have tried to find any pit file, but any pit file doesnt work. Dont know what to do next.
It would be great if you could help me.
Volume Size is too big 4620288 < 4718592
ODIN : Invalid ext4 image
AFAIK, HongKong phone can't be flashed with other region's fw due to some differences in hardware....
You must flash HK fw....
You are right, its working now. Do you know what custom rom can I install on Hong Kong version? I was trying to install Darklord note 5 port, but its bootlooping on samsung logo. So i stayed on CM 12.1.