Return to stock odin FAIL - Galaxy S 5 Q&A, Help & Troubleshooting

Im trying to return to stock and Odin fails at the very end of the flash each time. I was running blisspop before trying to flash, and i did a factory reset as well before trying to flash.
this is what the log says in odin
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<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> 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)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

You put the phone in recovery mode or download mode during flashing?
skrcer1 said:
Im trying to return to stock and Odin fails at the very end of the flash each time. I was running blisspop before trying to flash, and i did a factory reset as well before trying to flash.
this is what the log says in odin
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<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> 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)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

Download mode

androidtweaker1 said:
You put the phone in recovery mode or download mode during flashing?
Click to expand...
Click to collapse
Download mode

Are all the usb drivers installed?
skrcer1 said:
Download mode
Click to expand...
Click to collapse

androidtweaker1 said:
Are all the usb drivers installed?
Click to expand...
Click to collapse
Yes I have successfully flashed on this PC before

androidtweaker1 said:
You put the phone in recovery mode or download mode during flashing?
Click to expand...
Click to collapse
lol what question man stop kiding
ext 4 fail mean not same pit with your phone ty another stock rom or trick pit option with your pit ( if you want only this rom )

popmpopm said:
lol what question man stop kiding
ext 4 fail mean not same pit with your phone ty another stock rom or trick pit option with your pit ( if you want only this rom )
Click to expand...
Click to collapse
I tried using a different pit and it didn't seem to help.

I asked because some people use recovery mode while flashing.
Thanks for the additional info though :good:
popmpopm said:
lol what question man stop kiding
ext 4 fail mean not same pit with your phone ty another stock rom or trick pit option with your pit ( if you want only this rom )
Click to expand...
Click to collapse

popmpopm said:
lol what question man stop kiding
ext 4 fail mean not same pit with your phone ty another stock rom or trick pit option with your pit ( if you want only this rom )
Click to expand...
Click to collapse
how do I find the correct pit file for my rom? Im pretty sure i have the correct one but just in case??

androidtweaker1 said:
I asked because some people use recovery mode while flashing.
Thanks for the additional info though :good:
Click to expand...
Click to collapse
custom roms work and this stock rom actually did boot up even though it said failed in odin, although it was buggy in some places. Any ideas how to go back completely to stock?

What version of odin you using.
Asking because I was unable to flash stock whenever I used 3.10
3.07 worked for me
skrcer1 said:
custom roms work and this stock rom actually did boot up even though it said failed in odin, although it was buggy in some places. Any ideas how to go back completely to stock?
Click to expand...
Click to collapse

im using 3.10, ill try 3.07 and report back.

androidtweaker1 said:
I asked because some people use recovery mode while flashing.
Thanks for the additional info though :good:
Click to expand...
Click to collapse
androidtweaker1 said:
What version of odin you using.
Asking because I was unable to flash stock whenever I used 3.10
3.07 worked for me
Click to expand...
Click to collapse
Still a fail...
<ID:0/003> Added!!
<ID:0/003> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BOC7_G900FOJK1BOC2_G900FXXU1BOC7_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> 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> 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)
Same as before, I put in the pit file, put in the firmware, factory wiped my phone, put into download mode, plugged it in then started the flash.
I remember I had the same issue before but the XEO (polish firmware) flashed properly, I just tried it again and it works. Why wont my other stock firmware work? It should be the same european pit as the XEO firmware. Maybe a different bootloader or something? Or maybe it is a different pit? I want to install the ILO firmware, what pit does it need?

If you have custom recovery try flashing a stock rom through that method. If using Odin method, try taking the battery out of your phone first, put it back in and then boot phone directly into download mode, then try flashing. From the log you posted it looks as though you have a bad stock rom file. Try downloading another one or use different version of Odin like 3.07. Here is the link to all the CSC codes that may help: http://forum.xda-developers.com/showthread.php?t=800257 If you cant find any help with that link try this one: http://www.galaxys5update.com/galaxy-s5-sm-g900f-europe-android-4-4-2-g900fxxu1ance-firmware-stock-rom-list/ Hope this helps you out some.

skrcer1 said:
Still a fail...
<ID:0/003> Added!!
<ID:0/003> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BOC7_G900FOJK1BOC2_G900FXXU1BOC7_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> 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> 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)
Same as before, I put in the pit file, put in the firmware, factory wiped my phone, put into download mode, plugged it in then started the flash.
I remember I had the same issue before but the XEO (polish firmware) flashed properly, I just tried it again and it works. Why wont my other stock firmware work? It should be the same european pit as the XEO firmware. Maybe a different bootloader or something? Or maybe it is a different pit? I want to install the ILO firmware, what pit does it need?
Click to expand...
Click to collapse
try to flash this last stock rom mega:///#!1AgXRSJC!qLhH124dDQE7marSruk89mAbVROJxGFF3bvXloyHYFc
for xeo you have last boj1

hi,
this happened to me and i followed the instructions from here : https://www.reddit.com/r/GalaxyS6/comments/35zshn/howto_fix_a_failed_odin_flash_softbrick_hiddenimg/
and this fixed it so i could go back to complete stock

odin 3.09 and usb 2.0 cable try
Usb 2.0 port used for flash frm lap

So I looked inside the md5 file and there is no such file hidden.img.ext4 maybe that is what the problem is? Can someone really show the line to normal stock ROM that can be flashed without all those trouble.

guys just tried flashing again with 6.0.1 netherlands and the same thing is happening, i think the problem was the XEO csc from the xeo 5.0 firmware but how do i fix it?!?!?!?!

Related

4.3 Bootloader

Hey everyone. I flashed the MI8 leak of TW 4.3, and it was decent, but I flashed the Google Edition by Jamal2367 and WiFi doesn't work, so I'm assuming it's because of this new bootloader. Is there anyway to either go back to the 4.2.2 bootloader (I assume it's highly unlikely) or to get WiFi and everything working?
Thanks
EDIT: Went to attempt to flash MH8 again (4.2.2) and even with the aboot file in it, Odin seems to be flashing it without a problem?
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUDMH8_I9505OXXDMHA_I9505XXUDMH8_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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> persdata.img.ext4
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
So could that mean it succesfully downgraded?
nellisere said:
Hey everyone. I flashed the MI8 leak of TW 4.3, and it was decent, but I flashed the Google Edition by Jamal2367 and WiFi doesn't work, so I'm assuming it's because of this new bootloader. Is there anyway to either go back to the 4.2.2 bootloader (I assume it's highly unlikely) or to get WiFi and everything working?
Thanks
Click to expand...
Click to collapse
Try flash NON-HLOS Bin for older firmware
LastStandingDroid said:
Try flash NON-HLOS Bin for older firmware
Click to expand...
Click to collapse
Didn't try that before downgrading but looks like it did downgrade the bootloader! No more eMMC boost thing in the bootloader. Already had Knox warranty void 0x1 so couldn't see if it triggered it. Now going to try Google Edition ROM again.
EDIT: Yes, after downgrading from MI8 (4.3 inc bootloader) to MH8 worked, and now WiFi works on 4.2.2 roms!

[Q] Failed updating to 4.4.2 DBT version

Hello,
Have a N9005 with 4.3 BTU version on it. Today I have tried to upgrade via Odin to KitKat 4.4.2 German version DBT and at the end of upgrading IT FAILED.(on the phone screen appears "Invalid ext4 image" in red. Tried to start the phone, UDC start appears in red and a screen putting me to connect and recovery with Kies, obviously no result. In Odin it says:
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.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>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
What can I do? Have I ruined my phone? :crying::crying::crying:
Tried to write the BTU 4.3 version but doesn't work also.
Please help!
Did you check MD5 to make sure you don't have a corrupt download?
acolosha said:
Hello,
Have a N9005 with 4.3 BTU version on it. Today I have tried to upgrade via Odin to KitKat 4.4.2 German version DBT and at the end of upgrading IT FAILED.(on the phone screen appears "Invalid ext4 image" in red. Tried to start the phone, UDC start appears in red and a screen putting me to connect and recovery with Kies, obviously no result. In Odin it says:
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.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>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
What can I do? Have I ruined my phone? :crying::crying::crying:
Tried to write the BTU 4.3 version but doesn't work also.
Please help!
Click to expand...
Click to collapse
Try to flash latest Dutch PHN 4.4 or Polish XEO 4.4.
A lot of guys have problem flashing the DBT NB4.
You can probably not go back to 4.3 when you now have flashed the 4.4 DBT although it failed. There is no way back to 4.3.
Try to flash the above mentioned 4.4.
Sent from my SM-N9005 using Tapatalk
kriskras said:
Did you check MD5 to make sure you don't have a corrupt download?
Click to expand...
Click to collapse
How do I check that? I thought Odin checks it...
acolosha said:
How do I check that? I thought Odin checks it...
Click to expand...
Click to collapse
It's not MD5 issue. It's an issue with the DBT NB4 pit file. It has wrong size.
People are bypassing the problem by modding the pitfile.
Search/browse for threads about it.. I got no link right now
Sent from my SM-N9005 using Tapatalk
mikkelrev69 said:
Try to flash latest Dutch PHN 4.4 or Polish XEO 4.4.
A lot of guys have problem flashing the DBT NB4.
You can probably not go back to 4.3 when you now have flashed the 4.4 DBT although it failed. There is no way back to 4.3.
Try to flash the above mentioned 4.4.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Now I'm downloading the XEO NB3 4.4. Which Odin do you recommend?
acolosha said:
Now I'm downloading the XEO NB3 4.4. Which Odin do you recommend?
Click to expand...
Click to collapse
Odin3 1.85 is my choise. Also included in cf-autoroot download zip file..
Sent from my SM-N9005 using Tapatalk
mikkelrev69 said:
Odin3 1.85 is my choise. Also included in cf-autoroot download zip file..
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Thanks A LOT!!! Worked with XEO NB3 version. Thanks again!
Seems to have an issue with the S-View application but I've heard it's a known one, hope they'll fix it.
acolosha said:
Hello,
Have a N9005 with 4.3 BTU version on it. Today I have tried to upgrade via Odin to KitKat 4.4.2 German version DBT and at the end of upgrading IT FAILED.(on the phone screen appears "Invalid ext4 image" in red. Tried to start the phone, UDC start appears in red and a screen putting me to connect and recovery with Kies, obviously no result. In Odin it says:
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.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>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
What can I do? Have I ruined my phone? :crying::crying::crying:
Tried to write the BTU 4.3 version but doesn't work also.
Please help!
Click to expand...
Click to collapse
Same problem here. I have NB3 Polish (CSC TPH after make root). Any solution?
EDIT: Flashing with Pit file

[Q] Problems Upgrading to 4.4.2

Hi all
Long time lurking and now hoping to pass some knowledge i have learned onto other but at the minute i have a problem myself.
I have a Note 3 running Baseband N9005XXUENB1 Build number KOT49H.N9005ZHUENB5 which given the keyboard settings i believe it is the Hng Kong firmware.
I want to use a stable UK firmware like the Vodafone one N9005XXUENB4_N9005VFGENA4_N9005XXUENB1_HOME.tar.md5 however everytime i try to flash using odin 3.09 it fails.
I am using an original USB cable and tried different USB ports.
Any ideas what is going wrong?
Can anyone suggest a version which will work?
daveherron said:
Hi all
Long time lurking and now hoping to pass some knowledge i have learned onto other but at the minute i have a problem myself.
I have a Note 3 running Baseband N9005XXUENB1 Build number KOT49H.N9005ZHUENB5 which given the keyboard settings i believe it is the Hng Kong firmware.
I want to use a stable UK firmware like the Vodafone one N9005XXUENB4_N9005VFGENA4_N9005XXUENB1_HOME.tar.md5 however everytime i try to flash using odin 3.09 it fails.
I am using an original USB cable and tried different USB ports.
Any ideas what is going wrong?
Can anyone suggest a version which will work?
Click to expand...
Click to collapse
Can we get an exact copy of the error you get on Odin please?
As the 16GB Hong Kong Note 3s have a different partition layout, you might have gotten that an error.
Sent from my fingers to your face using my Samsung Galaxy Note 3!
nicholaschum said:
Can we get an exact copy of the error you get on Odin please?
As the 16GB Hong Kong Note 3s have a different partition layout, you might have gotten that an error.
Sent from my fingers to your face using my Samsung Galaxy Note 3!
Click to expand...
Click to collapse
This is what i got from Odin
<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> cache.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005VFGENA4_N9005XXUENB1_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)
Try a non-carrier rom, people seem to have trouble with these...
ultramag69 said:
Try a non-carrier rom, people seem to have trouble with these...
Click to expand...
Click to collapse
I cannot locate a non carrier rom
daveherron said:
I cannot locate a non carrier rom
Click to expand...
Click to collapse
:sly:
Sent from my N9005
Dejan Sathanas said:
:sly:
Sent from my N9005
Click to expand...
Click to collapse
Sorry don't understand you response?:sly:
You're trying to flash a vodafone rom... This is a carrier rom...
Look for the UK rom that has a csc with BTU as this is the open rom...

Lollipop update issue.

Hi guys.
I have an italian unbranded phone n9005.
Today i've tried flashing a german and a UK n9005 lollipop rom from sammobile with odin.
In both cases odin failed the last step while flashing hidden.img and gave me error "fail (size)"
Now i can still access to download mode but i have no clue of what to do.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBOA5_N9005VFGGBOA2_N9005XXUGBOA1_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> SingleDownload.
<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)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for your time
Try This
is your note3 rooted or stock ?
I have a stock Note3 LTE and downloaded the XEO (polish) from sammobile firmwares and it worked perfectly because it is an unlocked rom. You can download it from here http://samsung-updates.com/device/?id=SM-N9005&details=Galaxy_Note_3__Snapdragon Roms that are network branded can quite often fail in the way yours did.
To get out of your current position you have 2 choices...You can download the above and simply follow normal Odin procedure or you can flash your old rom again.
Uxepro said:
Hi guys.
I have an italian unbranded phone n9005.
Today i've tried flashing a german and a UK n9005 lollipop rom from sammobile with odin.
In both cases odin failed the last step while flashing hidden.img and gave me error "fail (size)"
Now i can still access to download mode but i have no clue of what to do.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBOA5_N9005VFGGBOA2_N9005XXUGBOA1_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> SingleDownload.
<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)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for your time
Click to expand...
Click to collapse
Solved. Just flash an unbrand FW on an unbrand phone
billd2439 said:
is your note3 rooted or stock ?
I have a stock Note3 LTE and downloaded the XEO (polish) from sammobile firmwares and it worked perfectly because it is an unlocked rom. You can download it from here http://samsung-updates.com/device/?id=SM-N9005&details=Galaxy_Note_3__Snapdragon Roms that are network branded can quite often fail in the way yours did.
To get out of your current position you have 2 choices...You can download the above and simply follow normal Odin procedure or you can flash your old rom again.
Click to expand...
Click to collapse
Will this work on my rooted n90005.
And can you send me a link to step by step rooting guide?
Sent from my SM-N9005 using Tapatalk
Couldn't be certain but I believe if you install an official rom on a rooted phone the root is lost. That would meet it should install no problem and restore the phone to stock.

[Note 3 n9005] root problem

Hello,
First I was on 4.4.2, then I've switch to 5.0. ( without root priv )
Today I've downgrade from 5.0 to 4.4.2, and my "note 3" bricked!
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGNH1_N9005TMNGNL2_N9005XXUGNH1_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> SingleDownload.
<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)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then I've download .pit file from here, and my "note 3" got re-partition.
Now I want root my android, but I got this error ( using this tut here )
Code:
NAND Write Start!!
<ID:0/004> FAIL!
I need your help, I want clean (rom, pit, 4.4.2 system) with root for my "note 3- n9005"
Thanks.
your first mistake: updated to loli(s..t)pop.
second: not saved rom creddentials
solution: kies 3 or odin
dancapitan said:
your first mistake: updated to loli(s..t)pop.
second: not saved rom creddentials
solution: kies 3 or odin
Click to expand...
Click to collapse
when my note bricked, I try restore from kies, but I can't
now I need clean .pit and 4.4.2 software with root
a7m3d said:
when my note bricked, I try restore from kies, but I can't
now I need clean .pit and 4.4.2 software with root
Click to expand...
Click to collapse
1. That .pit file is good but you have to flash the correct firmware for it: HERE. Follow the steps of that thread too for flash the firmware correctly.
2. Take out the battery of your device when the process of flashing finish (wait 10 sec.). Put it in again.
3. Boot your device in Stock Recovery and select: Wipe data/Factory reset.
4. Select "Reboot System Now" option then.
5. Root it then with that method you posted b4.
Joku1981 said:
1. That .pit file is good but you have to flash the correct firmware for it: HERE. Follow the steps of that thread too for flash the firmware correctly.
2. Take out the battery of your device when the process of flashing finish (wait 10 sec.). Put it in again.
3. Boot your device in Stock Recovery and select: Wipe data/Factory reset.
4. Select "Reboot System Now" option then.
5. Root it then with that method you posted b4.
Click to expand...
Click to collapse
1- I've download PIT from here, and download firmware from here, and flash the firmware.
Code:
<ID:0/004> 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/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> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.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> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
2- when flash finish, I've take out my battery from device. ( I didn't put "auto-reboot" in Odin3)
3- I've Wipe data/Factory reset with Stock Recovery.
4- I've Reboot System.
5- I try to root it with http://androidxda.com/root-samsung-galaxy-note-3-sm-n9005
but the problem:
Code:
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
a7m3d said:
1- I've download PIT from ...
Click to expand...
Click to collapse
1. Try flashing this custom recovery first: HERE.
2. Flash this FILE via TWRP. Reboot then.
Joku1981 said:
Try flashing this custom recovery first: ONE.
Click to expand...
Click to collapse
I've going to setting, and enable developer mode then I've root my phone again and it's rooted!
but my phone still reboot and reboot (dosen't stop??)
edit; I've done ‘wipe cache partition.’ and it's work now
Please close the topic

Categories

Resources