Hi All,
I have a Samsung S5 Mini (SM-G800h), I am trying to update its firmware using ODIN but I keep getting "system.img.ext4"
<ID:0/008> system.img.ext4
<ID:0/008> Fail
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried all firmwares available on SamMobile on different PCs using different USB cables and different Odin Versions with no luck. I keep getting the same message all the time. (and the USB Debugging is on)
Can anyone help in this please?????????
moamh1 said:
Hi All,
I have a Samsung S5 Mini (SM-G800F), I am trying to update its firmware using ODIN but I keep getting "NAND START Fail"
<ID:0/008> NAND Write Start!!
<ID:0/008> Fail
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried all firmwares available on SamMobile on different PCs using different USB cables and different Odin Versions with no luck. I keep getting the same message all the time. (and the USB Debugging is on)
Can anyone help in this please?????????
Click to expand...
Click to collapse
You need download firmware and ODIN from this page and do like instruction says.
sammobile.com/firmwares/3/?download=31721
If you still have a problems - try change computer, sometimes problem not in device. I was repair my S5mini couple time.
Winstrol said:
You need download firmware and ODIN from this page and do like instruction says.
sammobile.com/firmwares/3/?download=31721
If you still have a problems - try change computer, sometimes problem not in device. I was repair my S5mini couple time.
Click to expand...
Click to collapse
Thanks .. but I downloaded all the firmwares on Sammobile and tried 4 or 5 pcs, same problem all the time.
Does anyone have an idea why this is happening or what causes it?
moamh1 said:
Thanks .. but I downloaded all the firmwares on Sammobile and tried 4 or 5 pcs, same problem all the time.
Does anyone have an idea why this is happening or what causes it?
Click to expand...
Click to collapse
look is like your phone was locked before you start update.
it can be operator version or some one started option in Setting\Security\Reactivation lock - this option dont give you choice reinstalling OS
Winstrol said:
look is like your phone was locked before you start update.
it can be operator version or some one started option in Setting\Security\Reactivation lock - this option dont give you choice reinstalling OS
Click to expand...
Click to collapse
Thanks Winstrol for the prompt response. The phone does not even have a reactivation lock option int he Security menu.
Its really weird that all I get is Fail after the Nand write Start, any idea to try?
just for clear - did you try to change you computer and do it on another PC?
Winstrol said:
just for clear - did you try to change you computer and do it on another PC?
Click to expand...
Click to collapse
I have tried 3 different Pc's and also tried like 5 or 6 different usb cables, still no luck! Getting frustrated with it .. its just weird..
I need to know what can cause such a problem?!?
Having almost the same problem. SM-G800F. Trying to flash the latest stock firmware (SER-G800FXXU1ANG1-20140709112536.zip / G800FXXU1ANG1_G800FSER1ANG1_G800FXXU1ANG1_HOME.tar.md5). Odin 3.09 and 3.07 both are stopping on the same file: system.img. Tried different USB cables and two more firmwares for other regions.
Maybe it is necessary to try to re-partition with PIT file? Is it possible to find it somewhere?
Alex Sad said:
Having almost the same problem. SM-G800F. Trying to flash the latest stock firmware (SER-G800FXXU1ANG1-20140709112536.zip / G800FXXU1ANG1_G800FSER1ANG1_G800FXXU1ANG1_HOME.tar.md5). Odin 3.09 and 3.07 both are stopping on the same file: system.img. Tried different USB cables and two more firmwares for other regions.
Maybe it is necessary to try to re-partition with PIT file? Is it possible to find it somewhere?
Click to expand...
Click to collapse
I am now facing the same problem that you are facing, I now have the two versions of the S5 Mini 1: sm-g800f and 2: sm-g800h (dual sim). I have tried all available firmwares at sammobile for both phones using different pcs, cables and odin versions, I always get Fail after 5-10 seconds from the system.img.ext4 start.
Any help?
Have u stopped all Kies services in the Taskmanager before flashing?
NikePershing said:
Have u stopped all Kies services in the Taskmanager before flashing?
Click to expand...
Click to collapse
I don't even have it installed on my PC and I have stopped it on the other ones that I have used, still no luck, same error every time. It always fails just when it gets to the system.img.ext4.
Any idea ?
moamh1 said:
I don't even have it installed on my PC and I have stopped it on the other ones that I have used, still no luck, same error every time. It always fails just when it gets to the system.img.ext4.
Any idea ?
Click to expand...
Click to collapse
I have to say that I have flashed a Grand 2 on the same pc using the same USB cable and that worked fine.
moamh1 said:
I have to say that I have flashed a Grand 2 on the same pc using the same USB cable and that worked fine.
Click to expand...
Click to collapse
This is Odin's log:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G800HXXU1ANGF_G800HODD1ANGB_G800HXXU1ANGH_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> 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)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Are you trying to flash SM-G800H firmware on a SM-G800F? They are not the same device. lt won't work.
Sent from my SM-P605 using XDA Free mobile app
polyconvex said:
Are you trying to flash SM-G800H firmware on a SM-G800F? They are not the same device. lt won't work.
Sent from my SM-P605 using XDA Free mobile app
Click to expand...
Click to collapse
To be honest with you, out of desperation at the end I have tried it (no luck off course), but I have originally flashed SM-G800H with SM-G800H firmwares. These are the ones that I have tried, I got the same error with all (using different PCs, Odin versions and USB cables):
Model Country/Carrier Date Version PDA CSC
SM-G800H India 2014 July 4.4.2 G800HXXU1ANGF G800HODD1ANGB
SM-G800H Russia 2014 July 4.4.2 G800HXXU1ANGD G800HOXY1ANGD
SM-G800H UAE 2014 July 4.4.2 G800HXXU1ANGF G800HOJV1ANG5
SM-G800H Egypt 2014 July 4.4.2 G800HXXU1ANGF G800HOJV1ANG5
SM-G800H South Africa 2014 July 4.4.2 G800HXXU1ANGF G800HOJV1ANG5
SM-G800H Afghanistan 2014 July 4.4.2 G800HXXU1ANGF G800HOJV1ANG5
SM-G800H Saudi Arabia 2014 July 4.4.2 G800HXXU1ANGF G800HOJV1ANG5
SM-G800H Guatemala 2014 July 4.4.2 G800HXXU1ANGG G800HUWA1ANG1
SM-G800H Trinidad and T 2014 July 4.4.2 G800HXXU1ANGG G800HUUB1ANFE
SM-G800H Panama 2014 July 4.4.2 G800HXXU1ANGC G800HUUB1ANFE
SM-G800H Russia 2014 July 4.4.2 G800HXXU1ANGA G800HOXY1ANGA
SM-G800H Brazil 2014 July 4.4.2 G800HXXU1ANGC G800HZTO1ANG1
Does anyone have an idea what to do? still getting the same error and on the phone screen it states: Odin invalid ext4 image
Guys, pleas tell, what you did with your phones before trying to flash? Just for clear - which reasons did you have for reflashing?
Winstrol said:
Guys, pleas tell, what you did with your phones before trying to flash? Just for clear - which reasons did you have for reflashing?
Click to expand...
Click to collapse
for me it was getting a problem with it freezing the screen, a friend of mine brought it for me from abroad so I couldn't benefit from the warranty. Therefore, I thought the best option would be just to flash it with the latest firmware available. I have done this several times with other phones with no problem, no sure why i am facing this problem with this one (actaully its now the two of them), cause i tried the same with my friends phone, same result !!
Still have no idea why it is happen.. but when we try rooting SM-800F and made several versions of ROM by several different compilations we have same problems - stopped flashing at system.bin. Just one from several versions got work and was flashed normaly and got a root on my device - i putted this version in the post here
For sure - who have problem and have SM-800F try to flash this version.
Winstrol said:
Still have no idea why it is happen.. but when we try rooting SM-800F and made several versions of ROM by several different compilations we have same problems - stopped flashing at system.bin. Just one from several versions got work and was flashed normaly and got a root on my device - i putted this version in the post here
For sure - who have problem and have SM-800F try to flash this version.
Click to expand...
Click to collapse
Thanks for the update but any solution for the SM-800H?
Related
Hi Folks,
please bare with me I am a total new comer in this forum and new on Android because of my new Phone:
Samsung Galaxy Note GT-I9220 Chinese Version (but no fake it has Android 4.0.4 and was bought from amazon)
I accidentially installed the franco.Kernel .... don't aks me why.... and since then I am in big troubles :crying:
I can not get a USB Connection to my Win7x64 PC anymore (MTP driver installation fails.... anything I tried did not work)
Eventhough Odin does see my phone but after clicking START if shows me FAILED (Odin 1.85 nor 1.87 works) ... and the phone does seems to do anything (not turn black ... as decsribe in the following threat: http://forum.xda-developers.com/showthread.php?t=1660012 )
So how do I get back to a "normal" Kernel and which file can I use?
Thanks a lot for looking into this.
Le_Tifou:
cowboy:
PS:
All this issues only have come up, because I actually only tried to get full access to all GOOGLE PLAY STORE apps, but google always (90% of all apps) tells me this is incompatible with your phone ... and under [+] sometime says it can not be delivered to your country China or so...
Are you putting the phone in download mode when you connect to odin? If yes then paste the odin logs.
here the ODIN log for 1.87 but same for 1.85
nokiamodeln91 said:
Are you putting the phone in download mode when you connect to odin? If yes then paste the odin logs.
Click to expand...
Click to collapse
Thanks for having a look into this.
So Windows recognizes the following drivers if it is in Download mode
SAMSUNG Mobile USB CDC Composite Device
SAMSUNG Mobile USB Modem
And ODIN 1.87 recognizes the device under ID:COM yellow 0:[com3]
<ID:0/003> Added!!
after START PIT and Bootloader
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The Phone does not do anything. :crying:
I assume that the wrong KERNEL is causing this missbehaviour!?
what to do now? Any idea?
Thx 1000times
So how do I first get a new fitting Kernel?
Le_Tifou said:
Hi Folks,
please bare with me I am a total new comer in this forum and new on Android because of my new Phone:
Samsung Galaxy Note GT-I9220 Chinese Version (but no fake it has Android 4.0.4 and was bought from amazon)
I accidentially installed the franco.Kernel .... don't aks me why.... and since then I am in big troubles :crying:
I can not get a USB Connection to my Win7x64 PC anymore (MTP driver installation fails.... anything I tried did not work)
Eventhough Odin does see my phone but after clicking START if shows me FAILED (Odin 1.85 nor 1.87 works) ... and the phone does seems to do anything (not turn black ... as decsribe in the following threat: http://forum.xda-developers.com/showthread.php?t=1660012 )
So how do I get back to a "normal" Kernel and which file can I use?
Thanks a lot for looking into this.
Le_Tifou:
cowboy:
PS:
All this issues only have come up, because I actually only tried to get full access to all GOOGLE PLAY STORE apps, but google always (90% of all apps) tells me this is incompatible with your phone ... and under [+] sometime says it can not be delivered to your country China or so...
Click to expand...
Click to collapse
You would better restock your note.
You will need a rom with four files: .pit , .pda, modem and csc
The rom MUST be made for your phone and you may find it in samfirmware.com.
If your phone can't enter dowload mode, you'll need a USB JIG.
Hope this can help.
After reading the Odin resulst, try to flash only PDA as your error is comming from the PIT file.
Uncheck "repartition"
First get a kernel for your phone in tar.md5, and flash it by selecting it in the PDA tab. Don't use PIT for now.
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
Phone has to be in download mode to use odin
Is that the right file: 165512339/c6b85b4/I9220ZCLPL_I9220OZHLPL_CHN.zip ??
nokiamodeln91 said:
First get a kernel for your phone in tar.md5, and flash it by selecting it in the PDA tab. Don't use PIT for now.
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
Phone has to be in download mode to use odin
Click to expand...
Click to collapse
Thanks for your adive.
How do I get the right kernel files I have no glue for what I should search for....
Ok I found recently this threat which seams to point to the origínal chinese android versions:
droidevelopers dot com/f479/11859-samsung-galaxy-note-i9220-china-firmware-list.html
which points to the following
CHINA I9220 Ice Cream Sandwich 4.0.4 Firmwares
Download PDA Version Release Date CSC version Country / Carrier
Link I9220ZCLPL 4.0.4 2012 July I9220OZHLPL China
from hotfile DOT com/dl/165512339/c6b85b4/I9220ZCLPL_I9220OZHLPL_CHN.zip =606MB
Is that the right stuff? I am just downloading it.
Thx
Even if you get a whole rom, it's good. Flash with odin without the pit
Le_Tifou said:
Thanks for your adive.
How do I get the right kernel files I have no glue for what I should search for....
Ok I found recently this threat which seams to point to the origínal chinese android versions:
droidevelopers dot com/f479/11859-samsung-galaxy-note-i9220-china-firmware-list.html
which points to the following
CHINA I9220 Ice Cream Sandwich 4.0.4 Firmwares
Download PDA Version Release Date CSC version Country / Carrier
Link I9220ZCLPL 4.0.4 2012 July I9220OZHLPL China
from hotfile DOT com/dl/165512339/c6b85b4/I9220ZCLPL_I9220OZHLPL_CHN.zip =606MB
Is that the right stuff? I am just downloading it.
Thx
Click to expand...
Click to collapse
Yes, should be fine, it's made for GT-I9220. Just flash PDA.:good:
Thanks KERNEL has been changed back to original
lionelia said:
Yes, should be fine, it's made for GT-I9220. Just flash PDA.:good:
Click to expand...
Click to collapse
Thanks both of you!!!
Odin 1.87 worked so far. And immediately Windows recognized the phone as GT-I9220 again.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9220ZCLPL_I9220ZCLPI_I9220OZHLPL_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> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> factoryfs.img
<ID:0/003> zImage
<ID:0/003> hidden.img
<ID:0/003> cache.img
<ID:0/003> modem.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
I got after disconneting and taking out battery and restart -
got into mode VOL-up + power-on + center key
and made a factory reset as well as deleted cache
Modell: GT-I9220
Android version: 4.0.4
Baseband: I9220ZCLPI
KERNEL: 3.0.15 - ...
Build: IMM76D.ZCLPL
When I unpacked the ZIP file there was an additioal file ss_DL.dll what shall I do with it?
now it works thanks to you!
Great!
Nothing to do with the the dll file. Congrats for a working phone.
Rooting failure
nokiamodeln91 said:
Nothing to do with the the dll file. Congrats for a working phone.
Click to expand...
Click to collapse
Please help,
I was trying to root my Samsung galaxy note gt-i9220, I followed the video instructions from rootgalaxynote.com, I used the CWM.Zip, CWM-supers-v0.87.zip and after I installed the franco kernel-r5.zip
PROBLEM: after installing the franco kernel when I restarted the system my note comes on and shows Galaxy Note GT-I9220 and after that I have a black screen.
What can I do to get back the original state, it seems I can not handle rooting it. However it can get to the download mode when I place the volume up+power+home burton.
NB: I did not use a computer while doing this neither did I backup any thing
Hello guys,
i'm new in the forum and this is my first entry.
I got quite a complicated situation with my phone... i try to describe this as good as possible.
My brother gave his old phone, a GT-I9070P with GB (v2.3.6) on it and i wanted to upgrade it to a newer firmware. Unfortunatly I haven't had an Android phone in a long time (2 years or so).
Nevertheless i wanted to upgrade it to 4.1.2 stock and use NFC (for programming a little bit).
I asked the father of a friend of mine to upgrade it because he has much more expirience with flashing and all that stuff ..
He said that this is no problem and after a few days he gave it back to me and told me that there were some difficulties but he did it.
Now i got my phone with JB 4.1.2 but when i tried it out, it didn't recognize the SIM card.
I gave it back to him and said, that the SIM wasn't working.
We found out that he flashed a I9070 stock and that the IMEI was "deleted" but he knows a guy how can fix this.
I read in a few forums about this problems and found out that this has got something to do with the modem (baseband / IMEI).
When i got my phone back, the SIM was recognized again.
But now i got a GT-I9070P with I9070 stock firmware (-> NFC not working)
Today i tried to flash two I9070P stock roms with Odin 3.09 but it didn't work out.
(I can post the LOG from Odin if you want)
When i flashed the I9070 stock again, it worked perfectly.
Sorry for the long post but now my actual question:
Is it possible to get a full functional I9070P with working NFC back on the phone?
(To be honest: i don't have any backups or /lib/tee - folders)
Thank you very much for helping me out!
cheers,
MonkeySon
MonkeySon said:
Hello guys,
i'm new in the forum and this is my first entry.
I got quite a complicated situation with my phone... i try to describe this as good as possible.
My brother gave his old phone, a GT-I9070P with GB (v2.3.6) on it and i wanted to upgrade it to a newer firmware. Unfortunatly I haven't had an Android phone in a long time (2 years or so).
Nevertheless i wanted to upgrade it to 4.1.2 stock and use NFC (for programming a little bit).
I asked the father of a friend of mine to upgrade it because he has much more expirience with flashing and all that stuff ..
He said that this is no problem and after a few days he gave it back to me and told me that there were some difficulties but he did it.
Now i got my phone with JB 4.1.2 but when i tried it out, it didn't recognize the SIM card.
I gave it back to him and said, that the SIM wasn't working.
We found out that he flashed a I9070 stock and that the IMEI was "deleted" but he knows a guy how can fix this.
I read in a few forums about this problems and found out that this has got something to do with the modem (baseband / IMEI).
When i got my phone back, the SIM was recognized again.
But now i got a GT-I9070P with I9070 stock firmware (-> NFC not working)
Today i tried to flash two I9070P stock roms with Odin 3.09 but it didn't work out.
(I can post the LOG from Odin if you want)
When i flashed the I9070 stock again, it worked perfectly.
Sorry for the long post but now my actual question:
Is it possible to get a full functional I9070P with working NFC back on the phone?
(To be honest: i don't have any backups or /lib/tee - folders)
Thank you very much for helping me out!
cheers,
MonkeySon
Click to expand...
Click to collapse
"But now i got a GT-I9070P with I9070 stock firmware" - your phone would be hardbricked if you flashed I9070 firmware on I9070P, so I suppose that is not the case. Did you try to do factory reset after flashing stock firmware for I9070. P.S. We do not have any custom ROM with NFC support as I know.
shut_down said:
"But now i got a GT-I9070P with I9070 stock firmware" - your phone would be hardbricked if you flashed I9070 firmware on I9070P, so I suppose that is not the case. Did you try to do factory reset after flashing stock firmware for I9070. P.S. We do not have any custom ROM with NFC support as I know.
Click to expand...
Click to collapse
Thank you for the quick response.
Hm... but this is exactly whats the case right now...
The back of the phone says "I9070P" and i have the backcover with the NFC "antenna" but the the device information says "Model: GT-I9070... Basebandversion: I9070XXLQG"
Okay, i will try that
But even if this works, wouldn't there the problem with the SIM-recognition again?
I know, that's the reason why i wanted to flash the newest stock rom.
I'd try to flash 9070P lib/tee/folder (use temporary recovery or flash any cocore kernel beforehand) - to be found here: http://forum.xda-developers.com/showthread.php?t=2191628 (use version for stock ROMs)
adamuadamu said:
I'd try to flash 9070P lib/tee/folder (use temporary recovery or flash any cocore kernel beforehand) - to be found here: http://forum.xda-developers.com/showthread.php?t=2191628 (use version for stock ROMs)
Click to expand...
Click to collapse
If i get it right you suggest:
- flash CoCore incl. recovery (for I9070)
- install the I9070P tee folder zip on my 9070 stock
What should theoretically happen then - would i be able to use NFC or flash the 9070P stock rom then?
But now i got a GT-I9070P with I9070 stock firmware (-> NFC not working)
Click to expand...
Click to collapse
Maybe the guy changed the board and you have i9070 without p/nfc ....
MonkeySon said:
If i get it right you suggest:
- flash CoCore incl. recovery (for I9070)
- install the I9070P tee folder zip on my 9070 stock
What should theoretically happen then - would i be able to use NFC or flash the 9070P stock rom then?
Click to expand...
Click to collapse
Try to flash cocore for I9070P as your phone is with NFC,then flash that tee folder zip and see if its working.If it is,download stock rom for P vesion from sammobile.com .I dont remember if flashing stock from there will increase count,but you can reset it later.
@shut_down
Now i did a factory reset after flashing the 9070 stock but i got the same error as before while flashing 9070P stock
@Tarola
Well this could possibly be but i don't think that, i trust them
@Force
Okey thanks, i will try that and report later
BTW: flashing stock also increases counter.
well, lets see..
i installed CoCore-EP-8.6-CWM - everything ok
installed 9070PJBlibteefolder.zip via recovery - no problem
restart the phone - restart to download mode and try to flash P rom.
Exact same error as before, in addition to that, the phone is now unable to read my SIM again
this is my Odin log if somebody is interested:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9070PXXLPJ_I9070PNRJLP2_HOME.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> SingleDownload.
<ID:0/004> cache.img.md5
<ID:0/004> NAND Write Start!!
<ID:0/004> hidden.img.md5
<ID:0/004> kernel.bin.md5
<ID:0/004> kernel2.bin.md5
<ID:0/004> normal.bin.md5
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
MonkeySon said:
well, lets see..
i installed CoCore-EP-8.6-CWM - everything ok
installed 9070PJBlibteefolder.zip via recovery - no problem
restart the phone - restart to download mode and try to flash P rom.
Exact same error as before, in addition to that, the phone is now unable to read my SIM again
this is my Odin log if somebody is interested:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9070PXXLPJ_I9070PNRJLP2_HOME.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> SingleDownload.
<ID:0/004> cache.img.md5
<ID:0/004> NAND Write Start!!
<ID:0/004> hidden.img.md5
<ID:0/004> kernel.bin.md5
<ID:0/004> kernel2.bin.md5
<ID:0/004> normal.bin.md5
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Odin does not complete instalation. It stuck at installing normal.bin.md5
shut_down said:
Odin does not complete instalation. It stuck at installing normal.bin.md5
Click to expand...
Click to collapse
yeah... but does anyone know why it stuck?
i don't think it would be the rom.. because this was the case with every 9070P rom i tried so far.
this whole thing is a little mystrey to me to be honest
EDIT:
I got my IMEI and SIM functionality back by flashing the 9070 stock again.
Just in case someone wants to know
I think i'm gonna ask the guy who did this for me how he achieved it, that the phone thinks its another model
MonkeySon said:
yeah... but does anyone know why it stuck?
i don't think it would be the rom.. because this was the case with every 9070P rom i tried so far.
this whole thing is a little mystrey to me to be honest
EDIT:
I got my IMEI and SIM functionality back by flashing the 9070 stock again.
Just in case someone wants to know
I think i'm gonna ask the guy who did this for me how he achieved it, that the phone thinks its another model
Click to expand...
Click to collapse
Only thing that I can tell you now is that you are lucky that your phone was not hardbricked.
Hey guys .. I have tried to update the firmware on my Samsung S5 Mini using all versions available in the firmware section in SamMobile and it always fails just when it starts the system.img.ext4. I have tried all available versions on several PC's, using different versions of Odin and using different usb cables !
Does anyone have an idea why this is happening?
Please note that I have used the same PCs to update other phones such as the Grand 2, s4 mini, s3 and they all worked well !
Thanks
The following is the log of Odin:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G800HXXU1ANGF_G800HODD1ANGB_G800HXXU1ANGH_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> 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)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Hey Guys .. any help here .. still getting the same error even with the new firmwares that just came out on SamMobile.
I even got a brand new laptop, still getting the same error: the update fails at system.img.ext4
Hellpppppp please ...
Hey! Use rooted russian firmware, i have the same prob.
Sent from my SM-G800H using Tapatalk
BinMgen said:
Hey! Use rooted russian firmware, i have the same prob.
Sent from my SM-G800H using Tapatalk
Click to expand...
Click to collapse
Hi , do you have a link to that?
Thanks
moamh1 said:
Hi , do you have a link to that?
Thanks
Click to expand...
Click to collapse
https://yadi.sk/d/r-CNY64OZswrM
BinMgen said:
https://yadi.sk/d/r-CNY64OZswrM
Click to expand...
Click to collapse
Thanks for the link but still no luck .. any other idea please ?
moamh1 said:
Thanks for the link but still no luck .. any other idea please ?
Click to expand...
Click to collapse
What's the problem?
Sent from my SM-G800H using Tapatalk
BinMgen said:
What's the problem?
Sent from my SM-G800H using Tapatalk
Click to expand...
Click to collapse
Still facing the same problem:
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Ext4)
<ID:0/007>
Any idea?
Your device is true g00h?
Sent from my SM-G800H using Tapatalk
BinMgen said:
Your device is true g00h?
Sent from my SM-G800H using Tapatalk
Click to expand...
Click to collapse
It is : SM-G800H Dual Sim
moamh1 said:
It is : SM-G800H Dual Sim
Click to expand...
Click to collapse
Which version of odin r using?
Sent from my SM-G800H using Tapatalk
Hi all have the same problem with my SM G800F update fail
i use odin 3.09
BinMgen said:
Which version of odin r using?
Sent from my SM-G800H using Tapatalk
Click to expand...
Click to collapse
I tried 3.09 , 3.07 and 1.3 with no luck !! I have also tried a number of laptops and a number of cables .. all with the same error!
itryed the orgilan firmware fro sammobile and it work. try to flasch the orginal firmware
Lazarosh said:
itryed the orgilan firmware fro sammobile and it work. try to flasch the orginal firmware
Click to expand...
Click to collapse
I tried all firmwares on Sammobile, still the same problem. Does any one have a link to the pit file?
Question about model
Lazarosh said:
itryed the orgilan firmware fro sammobile and it work. try to flasch the orginal firmware
Click to expand...
Click to collapse
Hi Lazarosh a question if I may ask, is your model the Galaxy S5 Mini Dual Sim SM-G800H Duos (SM-G800H/DS) international version? and if so which firmware did you use from Sammobile and worked for you ?
How to animate bricks? SM-G800H S5 mini.
How to animate bricks? SM-G800H S5 mini.
turning on s5
my galaxy s5 mini
This comes evrytime on the screen when i turnd him o n
Firmware upgrade encounterd an issue please select recovery mody in kies & try again
can someone help my please
killingrush24 said:
my galaxy s5 mini
This comes evrytime on the screen when i turnd him o n
Firmware upgrade encounterd an issue please select recovery mody in kies & try again
can someone help my please
Click to expand...
Click to collapse
You need to initialize your phone through Kies 3, Kies 3 has a way of re-flashing your device to the latest official firmware for a certain model with a certain Samsung serial number, i.e. even if your device is bricked and Kies 3 cannot detect it, you enter it's model and Samsung serial number and Kies 3 will download and flash the firmware for you, all you need to do is open Kies 3, power up your device and connect it to your PC, you will then open Tools menu and select Firmware Upgrade and Initialization, if Kies 3 can detect your phone it will show you the version of the firmware that will be downloaded and flashed then you will proceed as instructed (very simple procedures), if not you will be asked to enter just your model (for example SM-G800H) and your Samsung Serial Number (usually starts with R can be found on the sticker under the battery) then it will show you the latest official firmware for your device and if you proceed it will download and flash it for you, but be careful (this will be noted by Kies 3 too) you should get a full backup of your phone as it may wipe out everything on the internal storage in the process if it's required (i.e. a bricked phone to the extent of wrong partitioning that lead to loss of imei), needless to say this process depends on your internet connection (it downloads prerequisite files and firmware files which are relatively large), from little experience I have, it's best that you use the conventional official method for any product rather than unconventional ways at the beginning to solve any problem related to any product, if it doesn't help then try your best with any other method that might help you (by the way I tried this with more than one model of Samsung smart phones, tablets and notes and it always ends up solving the problem, in some cases with my friends devices reviving the device again after being totally bricked), hope this helps .
Note: all devices I used this method with were original devices straight from Samsung (International Versions, Unbranded & Unlocked), so the firmware comes straight from Samsung (no modifications done by operators / carriers) so I'm not sure if it will work for other devices (Fake Cloned, Locked or Branded devices with carriers specific settings)
Update success
Yesterday I updated firmware to G800HXXU1ANK2 latest over Odin 3.10 without any problem. Everything is working fine, Wifi is faster than before. Waiting for CM 11 anyway.....
So here's my problem. I bought my Note 4 (SM-N910T3) with 5.1.1 and rooted. As soon as 6.0.1 released, I downloaded and flashed and then rooted a little later. I started having some small issues because of the root so I did some research and found a systemless root method on XDA that was a possible solution. At some point, probably from flashing MM, my Baseband and Bootloader got updated to the newest at the time. That was fine at the time but I starting missing some of the features of 5.1.1 that got removed in the update. So now I'm looking at iB4STiD's Rapture ROM which is build upon stock 5.1.1 but I've hit a pretty major wall. No matter what I try, how many times, I cannot flash anything through Odin, besides 6.0.1 that I haven't tried. iB4STiD provides the Baseband and Bootloader files to flash with his ROM which are for my specific model.
Now, I've read in a couple places that you can't downgrade your bootloader but that sounds weird to me so maybe someone can explain more if that's correct. Now for some info:
Download Mode Text:
Code:
[COLOR="Red"]ODIN MODE (HIGH SPEED)[/COLOR]
PRODUCT NAME: SM-N910T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (2)
[COLOR="Silver"]QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, R1, A2, P1[/COLOR]
[COLOR="Blue"]SECURE DOWNLOAD: ENABLE[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
Now this is what comes up when I attempt to flash:
Odin:
Code:
<ID:0/008> 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/008> Odin engine v(ID:3.1203)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Download Mode:
Code:
[COLOR="Red"]SECURE CHECK FAIL: aboot
[1]eMMC write fail: ABOOT[/COLOR]
I am at the end here and mentally exhausted so if anybody can give some guidance or advice then that would be awesome. Let me know if you need more info!
It's silly. But I remember trying to unroot my nte 4 by going back to stock, odin kept failing until I s
Used the official USB cable of the note 4. I had to borrow my step dad's USB to successfully get the thing back working.
Sent from my SM-N910T using Tapatalk
nano303 said:
It's silly. But I remember trying to unroot my nte 4 by going back to stock, odin kept failing until I s
Used the official USB cable of the note 4. I had to borrow my step dad's USB to successfully get the thing back working.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Yep I tried 4 different cables and different ports, including 2 OEM samsung cables that came from my Note 4 and an older phone. Nothing.
squiglybob13 said:
Yep I tried 4 different cables and different ports, including 2 OEM samsung cables that came from my Note 4 and an older phone. Nothing.
Click to expand...
Click to collapse
You can't downgrade T3 via ODIN once you upgrade to MM. So basically you are stuck with latest bootloader.
pvsgh said:
You can't downgrade T3 via ODIN once you upgrade to MM. So basically you are stuck with latest bootloader.
Click to expand...
Click to collapse
Yea that's what I was afraid of. My next issue though is I can't seem to flash ANYTHING via Odin. I even tried a stock rom that matched my current bootloader and it gave me the same error.
squiglybob13 said:
Yea that's what I was afraid of. My next issue though is I can't seem to flash ANYTHING via Odin. I even tried a stock rom that matched my current bootloader and it gave me the same error.
Click to expand...
Click to collapse
Use PhoneInfo application from Playstor to check your exact bootloader version and post it here. The error from your 1st post shows only when you try to downgrade.
I believe I've got the same problem (N910T, I tried to downgrade to 5.1.1 so that I can install Rapture v8.2), except in Odin it stops at system.img.ext4 then fails. I tried restoring with my backup through TWRP but now it's giving me this:
extractTarFork() process ended with ERROR=255
Basically I'm stuck with Odin and TWRP, I have the 5.1.1 firmware which doesn't work, and I'm currently downloading the 6.0.1 firmware and hopefully I'll be able to get it working again after this 2.2GB file finishes downloading with my 10mb/s internet -.-
I noticed a couple people had success flashing N920G INS Nougat firmware onto the N920I.
I'm having an issue where Odin goes dead after "Setup Connection" or "NAND Write Start". After that happens I'll only ever get to "Setup Connection" unless I force the phone off and back into Download Mode again.
I've done all the usual, different computers, ports, cables, Odin revisions, etc. I've never had this issue before. Before attempting to install Nougat I did a factory reset. I've also tried installing N920G INS Marshmallow and I had the same issues. USB Debugging and OEM Lock is off. When I got the phone it had Optus XSA (Australia) firmware on it and I flashed (with Odin) stock XSA firmware onto it fine.
Any ideas on what I could try? I have a blank N920I now so open to anything. It couldn't be a bad NAND could it? (I have no other bad NAND symptoms, phone seems fine).
try 4 files firmware nougat for N920I
can you help a bit more wiht the 4 files firmware? link? instructions?
now I am stuck in bootloader mode
I kind of fixed it by using the latest Odin (3.11.1).
Now I just get FAIL! at system.img. Does this mean I need the SM-N920G PIT for Nougat?
I soft-bricked and had to re-flash XSA MM for the SM-N920I.
nvhung SM-N920I Nougat isn't available yet. Any other ideas on how to get INS Nougat on the N920I?
It seems everyone who tries is getting stuck at system.img unless they were already on INS MM on their N920I.
Thanks!
Have you tried flashing 920g mm first?
Sent from my SM-N920I using Tapatalk
I'm having a similar issue. I've tried flashing the N920G 6.0.1 and 7.0 from stock 6.0.1 N920I, and get stuck with the following error:
<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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
6.0.1 was flashed using the 4 file method, 7.0 using 1 AP file. Tried using Odin 3.10.7, 3.11.1 and 3.12.3.
I think someone needs to post the 4 file link so everyone can move forward
Sent from my SM-N920I using Tapatalk
I tried AP for 6.0.1 MM INS (N920G) on my N920I with the same system.img fail. Where can I get the 4 file INS 6.0.1 N920G?
Ok I found the four files to convert 920i to 920g Marshmallow.
https://forum.xda-developers.com/no...-update-sm-t3334866/post66058243#post66058243
Maybe you guys need to do this step first then update to nougat???
I'll let you know how it goes in 20 minutes.
Thanks for files!
Fail on system.img. Phone error: sw rev check fail device 3 binary 2
Have to wait until official N920I Nougat.
So I've managed to get my phone model to say N920G in download mode, but it is now failing on system.img. This happens on both 6.0.1 and 7.0 INS
azzicles said:
Fail on system.img. Phone error: sw rev check fail device 3 binary 2
Have to wait until official N920I Nougat.
Click to expand...
Click to collapse
Bugger
azzicles said:
Fail on system.img. Phone error: sw rev check fail device 3 binary 2
Have to wait until official N920I Nougat.
Click to expand...
Click to collapse
Did you uncheck repartition?
You definitely need to convert with the 4 files first.....they had the exact same problem when MM was released if you read through that thread in the link I posted, everyone was failing on system.img also back then.
I would start with converting MM first.
Sent from my SM-N920I using Tapatalk
me_ashman said:
Did you uncheck repartition?
You definitely need to convert with the 4 files first.....they had the exact same problem when MM was released if you read through that thread in the link I posted, everyone was failing on system.img also back then.
I would start with converting MM first.
Sent from my SM-N920I using Tapatalk
Click to expand...
Click to collapse
I'm downloading the latest 6.0.1 INS and will convert when it's done. Will update when finished.
Here are the four files from another thread...to convert to 920g MM first.
https://mega.nz/#!hM9FBILb!UZZB4J9JzoswFPzyaDfZmmfLGzM-QTP7pjtt4Kuy_OI
Sent from my SM-N920I using Tapatalk
Tried that one, didn't work, downloading the latest 6.0.1 version and trying with that.
me_ashman said:
Did you uncheck repartition?
You definitely need to convert with the 4 files first.....they had the exact same problem when MM was released if you read through that thread in the link I posted, everyone was failing on system.img also back then.
I would start with converting MM first.
Sent from my SM-N920I using Tapatalk
Click to expand...
Click to collapse
re-partition was never checked. I don't have PIT file. I tried 4 files though. fails.
I wonder if there's something in the last couple of security updates causing this
Sent from my SM-N920I using Tapatalk
Any other ideas to try?