I've recently flash a T555 wihtout success using Odin. Done many a time on other Tabs and phones in the past without issue. This time however it fails with an invalid EXT4 error and no the device wont complete a boot. I've read the most common issue is down to the pit file. Can anyone help with a Pit for this model please?
Post the error log.
ashyx said:
Post the error log.
Click to expand...
Click to collapse
Sorry i hope you mean the Odin error log
<ID:0/020> 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/020> Odin engine v(ID:3.1101)..
<ID:0/020> File analysis..
<ID:0/020> SetupConnection..
<ID:0/020> Initialzation..
<ID:0/020> Get PIT for mapping..
<ID:0/020> Firmware update start..
<ID:0/020> SingleDownload.
<ID:0/020> aboot.mbn
<ID:0/020> NAND Write Start!!
<ID:0/020> sbl1.mbn
<ID:0/020> rpm.mbn
<ID:0/020> tz.mbn
<ID:0/020> hyp.mbn
<ID:0/020> NON-HLOS.bin
<ID:0/020> sec.dat
<ID:0/020> boot.img
<ID:0/020> recovery.img
<ID:0/020> system.img.ext4
<ID:0/020> modem.bin
<ID:0/020> cache.img.ext4
<ID:0/020> hidden.img.ext4
<ID:0/020> FAIL! (Ext4)
<ID:0/020>
<ID:0/020> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
section_32 said:
Sorry i hope you mean the Odin error log
<ID:0/020> 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/020> Odin engine v(ID:3.1101)..
<ID:0/020> File analysis..
<ID:0/020> SetupConnection..
<ID:0/020> Initialzation..
<ID:0/020> Get PIT for mapping..
<ID:0/020> Firmware update start..
<ID:0/020> SingleDownload.
<ID:0/020> aboot.mbn
<ID:0/020> NAND Write Start!!
<ID:0/020> sbl1.mbn
<ID:0/020> rpm.mbn
<ID:0/020> tz.mbn
<ID:0/020> hyp.mbn
<ID:0/020> NON-HLOS.bin
<ID:0/020> sec.dat
<ID:0/020> boot.img
<ID:0/020> recovery.img
<ID:0/020> system.img.ext4
<ID:0/020> modem.bin
<ID:0/020> cache.img.ext4
<ID:0/020> hidden.img.ext4
<ID:0/020> FAIL! (Ext4)
<ID:0/020>
<ID:0/020> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The error has nothing to do with the PIT file.
It fails at hidden.img.ext4 because you are flashing a firmware not intended for your region.
You should flash firmware that matches your CSC.
Irrespective of that the firmware would actually flash if you remove the hidden.img.ext4 from the firmware package.
The other alternative is to uncheck auto-reboot in Odin then simply reboot to download mode and flash something like twrp or cf_autoroot after it fails.
This will clear the firmware error notice.
ashyx said:
The error has nothing to do with the PIT file.
It fails at hidden.img.ext4 because you are flashing a firmware not intended for your region.
You should flash firmware that matches your CSC.
Irrespective of that the firmware would actually flash if you remove the hidden.img.ext4 from the firmware package.
The other alternative is to uncheck auto-reboot in Odin then simply reboot to download mode and flash something like twrp or cf_autoroot after it fails.
This will clear the firmware error notice.
Click to expand...
Click to collapse
thanks, the hidden.img.ext4 isn't the original message i received, i believe it was system.ext4 before. The firmware is for the UK vodafone version which is what mine are so that's strange. as these are work devices i'm trying to restrain from twrp or cf_autoroot lol but will be my last result if all else fails.
section_32 said:
thanks, the hidden.img.ext4 isn't the original message i received, i believe it was system.ext4 before. The firmware is for the UK vodafone version which is what mine are so that's strange. as these are work devices i'm trying to restrain from twrp or cf_autoroot lol but will be my last result if all else fails.
Click to expand...
Click to collapse
Can you point me to the firmware you are using?
It shouldn't fail if it's correct.
Could you also download Samsung phone info from play and check what the original CSC is?
ashyx said:
Can you point me to the firmware you are using?
It shouldn't fail if it's correct.
Could you also download Samsung phone info from play and check what the original CSC is?
Click to expand...
Click to collapse
Galaxy Tab A 9.7 (LTE) SM-T555 VOD T555XXU1AOJ1 5.0.2 found here
i've also tried the matching version for 6.0.1
I'm trying to get hold of another of these from a colleague to check the CSC
section_32 said:
Galaxy Tab A 9.7 (LTE) SM-T555 VOD T555XXU1AOJ1 5.0.2 found here
i've also tried the matching version for 6.0.1
I'm trying to get hold of another of these from a colleague to check the CSC
Click to expand...
Click to collapse
Are you certain these are carrier versions of the T555 and not just international versions of the T555?
Samsung phone info will give the details required.
ashyx said:
Are you certain these are carrier versions of the T555 and not just international versions of the T555?
Samsung phone info will give the details required.
Click to expand...
Click to collapse
you might be right, do you know which LTE version i should download if that's the case or do i not worry about whether they say LTE?
section_32 said:
you might be right, do you know which LTE version i should download if that's the case or do i not worry about whether they say LTE?
Click to expand...
Click to collapse
Why not just post the device info from Samsung phone info then there's no guessing?
ashyx said:
Why not just post the device info from Samsung phone info then there's no guessing?
Click to expand...
Click to collapse
thanks for all your help. managed to flash a rom in the end and everythings fine now.
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:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUFNF4_N9005OLBFNG1_N9005XXUFNF2_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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please help
j0ndav3 said:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUFNF4_N9005OLBFNG1_N9005XXUFNF2_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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please help
Click to expand...
Click to collapse
Download and install a custom rom here (AOSP or Stock and etc). Assuming you have a custom recovery.
Graffiti Exploit said:
Download and install a custom rom here (AOSP or Stock and etc). Assuming you have a custom recovery.
Click to expand...
Click to collapse
I cannot boot in recovery mode. What can I try?
I don't know what to do.. (
j0ndav3 said:
I cannot boot in recovery mode. What can I try?
I don't know what to do.. (
Click to expand...
Click to collapse
From what version did you come from exactly? You can't flash an older one from your current one.
Install a custom recovery through Odin. Download one here at the forums.
Graffiti Exploit said:
From what version did you come from exactly? You can't flash an older one from your current one.
Install a custom recovery through Odin. Download one here at the forums.
Click to expand...
Click to collapse
from 4.4.2 but i tried to install a same 4.4.2 version with download booster and kids mode that's why i tried to manual update my note 3 n9005
sorry im a noob.. thanks..
j0ndav3 said:
I cannot boot in recovery mode. What can I try?
I don't know what to do.. (
Click to expand...
Click to collapse
Do you can boot in Download mode?
porcelana said:
Do you can boot in Download mode?
Click to expand...
Click to collapse
Yes i can boot in Donwload mode..
Is it possible to update my 4.4.2 to 4.4.2 with download booster? because to my previous version, there's no download booster that's why I tried to install that firmware..
j0ndav3 said:
Yes i can boot in Donwload mode..
Is it possible to update my 4.4.2 to 4.4.2 with download booster? because to my previous version, there's no download booster that's why I tried to install that firmware..
Click to expand...
Click to collapse
Is your new image from a same region as your old one ?
If you had a let's say UK Version of firmware, you cannot flash with a Hong Kong one. That's when problems start.
Don't worry, this is not a big deal. We just need more info.
having same problem here.. currently stuck with SweetRom 4.4.2 v20 with video camera not working!
Colide said:
Is your new image from a same region as your old one ?
If you had a let's say UK Version of firmware, you cannot flash with a Hong Kong one. That's when problems start.
Don't worry, this is not a big deal. We just need more info.
Click to expand...
Click to collapse
I had a Hongkong version then I tried to install the Philippine version I think that's the problem. Thanks I hope I can fix this
)))))))))
Colide said:
Is your new image from a same region as your old one ?
If you had a let's say UK Version of firmware, you cannot flash with a Hong Kong one. That's when problems start.
Don't worry, this is not a big deal. We just need more info.
Click to expand...
Click to collapse
Thanks Colide! I already fixed my phone! Thanks for your tips! I really appreciate it! many thanks!
Hi,
I;ve posted this issue before but no one answered my previous thread ( T_T )
the issue still hasn't changed.
Trying to flash a Australian ROM on to my N9005.
getting this error in odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENE3_N9005VAUENF1_N9005XXUENE3_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> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing EU ROM's are fine as I'm currently using the UK 4.4.2 ROM N9005XXUGNG1
Please HELP; as it seems I cant use 4G with this ROM
you cant flash older fw, NG1 is new dont downgrade to older
Both 4.4.2
Thanks for reply!
Yes I'm aware that you can't downgrade.
Both ROM'S are 4.4.2 it just always fail at the same point no matter what.
The only thing that is different is one ROM is branded and one isn't
The one I'm trying to flash is Vodafone.
soulzsium said:
Thanks for reply!
Yes I'm aware that you can't downgrade.
Both ROM'S are 4.4.2 it just always fail at the same point no matter what.
The only thing that is different is one ROM is branded and one isn't
The one I'm trying to flash is Vodafone.
Click to expand...
Click to collapse
Your current version is GNG1 while the rom being flashed is ENE3 (older).
Try to flash the newer one.
vndnguyen said:
Your current version is GNG1 while the rom being flashed is ENE3 (older).
Try to flash the newer one.
Click to expand...
Click to collapse
N9005XXUGNG1 this was released in August
N9005XXUENE3 this was released in July
so I can't flash to a release that was a month old?
I thought that as long as the boot loader was the same version I could flash freely?
soulzsium said:
N9005XXUGNG1 this was released in August
N9005XXUENE3 this was released in July
so I can't flash to a release that was a month old?
I thought that as long as the boot loader was the same version I could flash freely?
Click to expand...
Click to collapse
Not sure if they have the same bootloader version?
You can only check for the bootloader version after install it.
vndnguyen said:
Not sure if they have the same bootloader version?
You can only check for the bootloader version after install it.
Click to expand...
Click to collapse
They are both KitKat 4.4.2 so I'm assuming yes
soulzsium said:
They are both KitKat 4.4.2 so I'm assuming yes
Click to expand...
Click to collapse
I'm not too sure, sorry. You have to check for the bootloader version.
Or you can also flash the modem (baseband) separately.
soulzsium said:
Hi,
I;ve posted this issue before but no one answered my previous thread ( T_T )
the issue still hasn't changed.
Trying to flash a Australian ROM on to my N9005.
getting this error in odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENE3_N9005VAUENF1_N9005XXUENE3_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> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing EU ROM's are fine as I'm currently using the UK 4.4.2 ROM N9005XXUGNG1
Please HELP; as it seems I cant use 4G with this ROM
Click to expand...
Click to collapse
The problem is your original pit file. As you can see problem is related to hidden partition that is to small for the image from your room that you want to flash(is the place where of in is stopping and give you error). To solve this you need to flash a pit file compatible with the room that you want to flash. What exactly do you want to achieve flashing this room anyway? ..
---------- Post added at 06:56 PM ---------- Previous post was at 06:39 PM ----------
If just LTD is your problem then check this:
<br />
Use ES File explorer or your favorite root explorer and go to data/property and find the persist.radio.lteon.xml file. Open it in Text Editor and if the value that is written is false, change it to true. Save and exit and reboot. Got the options back. Done.<br/>
Hi everyone !
I'm Matt, a Belgian student so don't be afraid of my english !
So I've a SM-G900F since September. Three weeks after bought it, I changed the ROM ! I put a port of CM11. After that, every rom ROM that i've flashed (exept Cyanogen ) was bugged. When i say bugged, i talk about the data connection. Once very slow, once not functionately,... Firstly, i thonk that that was a problem on the APN but i check that and that's not. After that, I asked me over the MODEM so i said, Ok , I'm going to put the original firmware from SamMobile ( The belgian firmware ) with Odin. Yesterday I did it BUT , at the end, they were an error Message ! That was something like that :
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA7_N9005DTMENA2_N9005XXUENA2_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> modem.bin
<ID:0/006> cache.img.ext4
<ID:0/006> hidden.img.ext4
<ID:0/006> FAIL! (Size)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
So i search that on XDA and i found that i had to put the firmware of my country (http://forum.xda-developers.com/showthread.php?t=2641965) but that's my coutry's firmware ! So after this failed message, i put CWM recovery on PDA section and my phone booted ! But since that, I can't use any data connection exept on cyanogen. And today, i looked at the G900F of a friend and that was the same baseband ... ANG2 for Belgium ....
Thx for reading and i hope that i'll find a member that he can resolve my problem ! See u
Try to flash this, I found this firmware with information you provided.
Model: SM-G900F
Country: Belgium
(you are responsible for your actions)
http://www.sammobile.com/firmwares/download/33819/G900FXXU1ANG9_G900FPRO1ANG3_PRO.zip/
Sent from my SM-G906S using XDA Premium 4 mobile app
Probably s problem with your modem / baseband, flash a new one.
dladz said:
Probably s problem with your modem / baseband, flash a new one.
Click to expand...
Click to collapse
And do you know a site where i can find some modem ? Or extract a part of a ROM ?
Matt-2905 said:
And do you know a site where i can find some modem ? Or extract a part of a ROM ?
Click to expand...
Click to collapse
Not off hand no, I would have to search and i'm sure we'd yield the same results so i'll leave that to you, if you're rooted and have a custom recovery, have no problem using odin, then i'd flash Neat Rom's rom, there's a tutorial in there which links to a bootloader and modem, ang3 I believe or AMG3, can't remember exactly, but that one works for me so try that.
If i've been understand, you think that i have to flash AMG3 Modem part ? Did u ever heart something like that ?
I've done everything to restore to stock firmware. I used odin-v3.10.6 and Kies 3. They both stop at 4%. My firmware is T530NUUEU1BOE5_T530NUXAR1BOE5_XAR.zip. But I can flash TWRP-2.8.7 via Odin just fine. But I am running out of ideas.
T530NUUEU1BOE5_T530NUXAR1BOE5_HOME.tar.md5 (2,225,735,835 bytes)
MD5: 5358d7e9247803a164d9a8cbc713bc55
T530NUUEU1BOE5_T530NUXAR1BOE5_XAR.zip (1,351,979,593 bytes)
MD5: 5c910ca3b4599971669cddf445fef8dc
This is why I'm requesting a PIT file or another solution.
Thanks
Sakui
sakui23 said:
I've done everything to restore to stock firmware. I used odin-v3.10.6 and Kies 3. They both stop at 4%. My firmware is T530NUUEU1BOE5_T530NUXAR1BOE5_XAR.zip. But I can flash TWRP-2.8.7 via Odin just fine. But I am running out of ideas.
T530NUUEU1BOE5_T530NUXAR1BOE5_HOME.tar.md5 (2,225,735,835 bytes)
MD5: 5358d7e9247803a164d9a8cbc713bc55
T530NUUEU1BOE5_T530NUXAR1BOE5_XAR.zip (1,351,979,593 bytes)
MD5: 5c910ca3b4599971669cddf445fef8dc
This is why I'm requesting a PIT file or another solution.
Thanks
Sakui
Click to expand...
Click to collapse
Try taking off the .md5 extension, or try the Canadian Firmware file, or try KitKat instead.
Also try doing a factory reset in recovery before flashing the firmware file
thisisapoorusernamechoice said:
Try taking off the .md5 extension, or try the Canadian Firmware file, or try KitKat instead.
Also try doing a factory reset in recovery before flashing the firmware file
Click to expand...
Click to collapse
Some reason TWRP-v2.8.7 can't mount /system when I do a wipe. Is there a way to do it manually and wipe it myself?
Thanks
Sakui
sakui23 said:
Some reason TWRP-v2.8.7 can't mount /system when I do a wipe. Is there a way to do it manually and wipe it myself?
Thanks
Sakui
Click to expand...
Click to collapse
If you want you always can to use service firmware for your device from here http://forum.xda-developers.com/showpost.php?p=61896173&postcount=1 .
This firmware include pit-file .
thisisapoorusernamechoice said:
Try taking off the .md5 extension, or try the Canadian Firmware file, or try KitKat instead.
Also try doing a factory reset in recovery before flashing the firmware file
Click to expand...
Click to collapse
I tried everything you said and I got no where. TWRP complained that the file system was read only.
repey6 said:
If you want you always can to use service firmware for your device from here http://forum.xda-developers.com/showpost.php?p=61896173&postcount=1 .
This firmware include pit-file .
Click to expand...
Click to collapse
I'm trying it right now. I'm just confused why Odin stops at system.img.ext4. Is the partition corrupt because its read only? But I installed a custom ROM (BlissPOP) and it worked fine.
sakui23 said:
I tried everything you said and I got no where. TWRP complained that the file system was read only.
Click to expand...
Click to collapse
In TWRP 2870 you need uncheck checkbox on Mount button
repey6 said:
If you want you always can to use service firmware for your device from here http://forum.xda-developers.com/showpost.php?p=61896173&postcount=1 .
This firmware include pit-file .
Click to expand...
Click to collapse
Service firmware [SM-T530NUUEU1BOE5_XAR_SERVICE_LP.zip] didn't work. It stopped at 4% again. But I have 5.0.1 and not 4.4. TWRP won't let me check "system" under mount.
It stopped at 4% again
Click to expand...
Click to collapse
What is 4% ? Where ? I dont understand this .
repey6 said:
What is 4% ? Where ? I dont understand this .
Click to expand...
Click to collapse
That's where Kies 3 stopped at. It stops in system.img.ext4 [Odin-v3.10.6] at the beginning of it. But it does process it but very little of it.
sakui23 said:
That's where Kies 3 stopped at. It stops in system.img.ext4 [Odin-v3.10.6] at the beginning of it. But it does process it but very little of it.
Click to expand...
Click to collapse
Why Kies . Close it . Use only Odin with him guide . Go to dounload mode . Connect to PC . In Odin download unpack service firmware (BL , AP , CSC ) to their button . And start . Please copy Odin log to me .
Odin v1.85
<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> BL_T530NUUEU1BOE5_CL4910899_QB4956020_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> AP_T530NUUEU1BOE5_CL4910899_QB4956020_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_XAR_T530NUXAR1BOE5_CL4910899_QB4956020_REV00_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The newer version don't spit out an error. Just sits there.
Stop Kies and delete from processes . Stop antivirus .
sakui23 said:
Odin v1.85
<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> BL_T530NUUEU1BOE5_CL4910899_QB4956020_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> AP_T530NUUEU1BOE5_CL4910899_QB4956020_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_XAR_T530NUXAR1BOE5_CL4910899_QB4956020_REV00_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The newer version don't spit out an error. Just sits there.
Click to expand...
Click to collapse
Correct, kies is awful don't use it. Also use Odin v3.10 or 3.09, not 1.85
Boy, do I feel very stupid...
It was the cords. I had 2 extension USB cords attached to the cord for the Tab 4 and used a different USB port.
Now, the service and the regular firmware works now.
Thanks for everything.
Sakui