Hi fellas, So here I am up at 5:42am (australian time) trying to fix my phone for the past 12 or so hours.
The Situation:
I can go into download mode as well as CWM recovery
- I cannot flash a stock rom via ODIN because it triggers the: INVALID EXT4 image error
- If I flash a rom via CWM, I can only boot up to the load screen
So guys, this is my last call. I'm willing to try ANYTHING.
EDIT1:
So here's the error message I receive when I try to flash a stock rom in ODIN:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMJ7_N9005XSADMJ2_N9005XXUDMJ7_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
LegendaryLvl1 said:
Hi fellas, So here I am up at 5:42am (australian time) trying to fix my phone for the past 12 or so hours.
The Situation:
I can go into download mode as well as CWM recovery
- I cannot flash a stock rom via ODIN because it triggers the: INVALID EXT4 image error
- If I flash a rom via CWM, I can only boot up to the load screen
So guys, this is my last call. I'm willing to try ANYTHING.
EDIT1:
So here's the error message I receive when I try to flash a stock rom in ODIN:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMJ7_N9005XSADMJ2_N9005XXUDMJ7_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
this sounds weird, try to re-download the firmware and flash it again
just to know, how this happend? what do you do after get this error message??
Is it a HK note?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Try following the second link in my signature. See if that works for you.
Though it will flash the kitkat bootloader to your phone. So be sure.
No sweat mate. Had something like that happen to me before.
Factory reset in CWM.
Check this thread, post #16: http://forum.xda-developers.com/showthread.php?p=49020087#post49020087
Good luck.
darkoctavius said:
this sounds weird, try to re-download the firmware and flash it again
just to know, how this happend? what do you do after get this error message??
Click to expand...
Click to collapse
I'm going through a list of multiple stock roms and flashing each one - hopefully one will work
I originally installed sweet rom and then tried to flash back to stock - most likely I accidentally flashed something through ODIN
radicalisto said:
Is it a HK note?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yup (or at least I think so) - bought off of KOGAN in Australia
FeralFire said:
Try following the second link in my signature. See if that works for you.
Though it will flash the kitkat bootloader to your phone. So be sure.
Click to expand...
Click to collapse
Thanks heaps I'll definitely try that
shayind4 said:
No sweat mate. Had something like that happen to me before.
Factory reset in CWM.
Check this thread, post #16: http://forum.xda-developers.com/showthread.php?p=49020087#post49020087
Good luck.
Click to expand...
Click to collapse
Awesome thank you!
FeralFire said:
Try following the second link in my signature. See if that works for you.
Though it will flash the kitkat bootloader to your phone. So be sure.
Click to expand...
Click to collapse
Damn feralfire!
You're method actually worked
Here I am after 21+ hours trying to fix my phone and your solution was the one that worked!
Thanks heaps!
Many thanks!
LegendaryLvl1 said:
Damn feralfire!
You're method actually worked
Here I am after 21+ hours trying to fix my phone and your solution was the one that worked!
Thanks heaps!
Many thanks!
Click to expand...
Click to collapse
Glad I could help.
LegendaryLvl1 said:
I'm going through a list of multiple stock roms and flashing each one - hopefully one will work
I originally installed sweet rom and then tried to flash back to stock - most likely I accidentally flashed something through ODIN
Yup (or at least I think so) - bought off of KOGAN in Australia
Thanks heaps I'll definitely try that
Awesome thank you!
Click to expand...
Click to collapse
Always remember Hong Kong edition phone cannot install whole world others country Note 3 stock ROM due to they aren't friend.
The only solution for you now is install CWM for KitKat and later updates to Sweet ROM v7
FeralFire said:
Glad I could help.
Click to expand...
Click to collapse
But now I'm guessing I can't install any roms until they update them for the newest baseband na2?
Related
Hey,
A while ago I've installed CM10.1 on my S4, but I was missing a lot of samsung features. So I've installed 4.2.2 again, set the binary back to the official one so I was able to update my phone again. Now that 4.3 has came out I tried to install it but then my phone bricked. The first attempt was not with odin but official via OTA.
Now i've got a soft bricked S4, tried to install the firmware several times via Odin but Odin keeps failing. If I first try to install it it wil fail at the aboot.mbn point. When I root it with Autoroot CF and then try to install the firmware it fails at system.img.ext4 as I show down here. Has anyone an idea how to fix this? Tried many options already like installing a new recovery like CWM Recovery and TWRP. (Couldn't find a stock recovery, maybe thats the solution.)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ7_I9505PHNEMJ8_I9505XXUEMJ7_HOME.tar.md 5 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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Currently have CM10.2 installed so I can use my phone, this works but not great. Wifi, Calling, Camera, Headphone and much other options won't work. I really want to install official Samsung 4.3 firmware and be able to update again with OTA.
chendoyen said:
Hey,
A while ago I've installed CM10.1 on my S4, but I was missing a lot of samsung features. So I've installed 4.2.2 again, set the binary back to the official one so I was able to update my phone again. Now that 4.3 has came out I tried to install it but then my phone bricked. The first attempt was not with odin but official via OTA.
Now i've got a soft bricked S4, tried to install the firmware several times via Odin but Odin keeps failing. If I first try to install it it wil fail at the aboot.mbn point. When I root it with Autoroot CF and then try to install the firmware it fails at system.img.ext4 as I show down here. Has anyone an idea how to fix this? Tried many options already like installing a new recovery like CWM Recovery and TWRP. (Couldn't find a stock recovery, maybe thats the solution.)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ7_I9505PHNEMJ8_I9505XXUEMJ7_HOME.tar.md 5 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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Currently have CM10.2 installed so I can use my phone, this works but not great. Wifi, Calling, Camera, Headphone and much other options won't work. I really want to install official Samsung 4.3 firmware and be able to update again with OTA.
Click to expand...
Click to collapse
I thought the only way to fix a bricked phone is to have it repaired or something. But I dont understand why you would switch back to samsung ui, but thats not my business. I believe is risky to go back to the phones normal UI after installing a rom because of the update problem. Basically I would never go back to the normal phones UI even if I wanted to after installing a rom, because I feel like there will be a problem. I dont really know a solution but maybe you can give it into someone to repair it, but I believe it costs A LOT. Sorry I don't really have a good solution for you. These are the risks with installing roms and switching back.
Are you using the official cable that came with the phone
Sent from my GT-I9505 using xda app-developers app
imlgl said:
Are you using the official cable that came with the phone
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Yes, also tried another cable.
Also tried: Another Odin version, another PC and different USB ports.
Anyone?
Nobody an idea?
You could try the following things:
Re-install samsung drivers
Make sure Kies is not running in the background
Try changing ports
Try different USB cable
bAk3ry said:
You could try the following things:
Re-install samsung drivers
Make sure Kies is not running in the background
Try changing ports
Try different USB cable
Click to expand...
Click to collapse
Tried again another PC and it worked a bit, I now have stock samsung firmware 4.3 installed but still no wifi and no sound. Is there a solution for that? Already tried to install CWM and TWRP but still doesn't work. When I try to play music it says audio file not supported (.MP3 file, before problems always worked) S Voice keeps crashing... And when I try to turn Wifi on I get a security message that says:
The device detected an application attempts to perform action that are not allowed. These actions are blocked.
You need to flash one of the WiFi 'fixes' from this thread, read it to work out which file you need to flash.
MistahBungle said:
You need to flash one of the WiFi 'fixes' from this thread, read it to work out which file you need to flash.
Click to expand...
Click to collapse
Tried that but it still won't work.
Hey guys...
I need a little help from professionnals...I wanted to try a Cyanogen rom, the 10.1.3, a stable one, on my S4. So I downloaded it, I rooted my phone with cf-autoroot with Odin, intalled CWM Recovery. Then I did all the wipes and flashed the cyanogenmod.
Guess what, it didn't work The flash worked well but next infinite bootloop on the boot animation of cyanogen...So I tryied to go back to recovery, mount USB and flash an another rom of cyanogen. And the results was worse, the flash did'nt work at all, if I remember "failed to mount /system" or something similar. And when I tried to restard the phone, nothing happened.
So I wanted to go back to the stock rom to repair this mess. => Download mode then under PDA, my tar.md5 files. Didn't work. I also tried with a PIT file, same result.
I changed my usb cable, the version of Odin, the usb port.
Here's what Odin give :
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I don't know what to do, I tried a lot of things beside all of this. Any ideas ?
THX
Try install STOCK ROM with older ODIN (click here), no the newest version
What stock rom are you trying to flash?
Thanks, but no change...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Lennyz1988 said:
What stock rom are you trying to flash?
Click to expand...
Click to collapse
This is I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_HOME, official for Europe, 4.3
BeamGG said:
This is I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_HOME, official for Europe, 4.3
Click to expand...
Click to collapse
if you have the secured bootloader (knox warranty void 0x0 in download mode) that means you can not flash old firmware such as MGA. you can flash firmwares MH?, MI? or MJ?.
I9505XXUBMGA = 4.2.2.
Thats probably why the flashing fails.
Lennyz1988 said:
I9505XXUBMGA = 4.2.2.
Thats probably why the flashing fails.
Click to expand...
Click to collapse
I'm such an idiot...I hasd chosen the wrong file...I'm trying with the MJ5 now, I'll let you know
EDIT : Indeed it goes further, but not at the end :
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
EDIT : I changed the usb port and re-installed the drivers, worked...finally, thx guys !
BeamGG said:
I'm such an idiot...I hasd chosen the wrong file...I'm trying with the MJ5 now, I'll let you know
EDIT : Indeed it goes further, but not at the end :
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
EDIT : I changed the usb port and re-installed the drivers, worked...finally, thx guys !
Click to expand...
Click to collapse
Only changing usb port and reinstalling solved it?
I have the same issue with ODIN3 3.07.
need4steer said:
Only changing usb port and reinstalling solved it?
I have the same issue with ODIN3 3.07.
Click to expand...
Click to collapse
Hey man,
Sorry for this late answer. Yes, as I said, I only changed the usb port et reinstalling drivers...did it work for you ?
BeamGG said:
Hey man,
Sorry for this late answer. Yes, as I said, I only changed the usb port et reinstalling drivers...did it work for you ?
Click to expand...
Click to collapse
Unfortunately no. Apparently the tar.md5 file I was trying to flash was the problem. The developer released a newer version of it which was flashed okay. Thanks a lot anyway!
need4steer said:
Unfortunately no. Apparently the tar.md5 file I was trying to flash was the problem. The developer released a newer version of it which was flashed okay. Thanks a lot anyway!
Click to expand...
Click to collapse
Cool, you are welcome ! :good:
Please is there any way to downgrade or root the sph-720t on android 5.0.1 OH1 Update. I swear I hate this update, and I'm urged to downgrade back to 4.4
maurs4216 said:
Please is there any way to downgrade or root the sph-720t on android 5.0.1 OH1 Update. I swear I hate this update, and I'm urged to downgrade back to 4.4
Click to expand...
Click to collapse
Copy latest SuperSU zip to SD card
Flash TWRP through Odin(uncheck reboot in Odin), disconnect USB, pull battery.
Reboot directly to TWRP
Flash SuperSU zip in TWRP
Boot phone and open SuperSU app to complete rooting process.
mattzeller said:
Copy latest SuperSU zip to SD card
Flash TWRP through Odin(uncheck reboot in Odin), disconnect USB, pull battery.
Reboot directly to TWRP
Flash SuperSU zip in TWRP
Boot phone and open SuperSU app to complete rooting process.
Click to expand...
Click to collapse
I've tried flashing twrp through doing several times with no success. Could it be because I flashed the full update (recovery, bootloader and rom)? I got the update straight from sam mobile
maurs4216 said:
I've tried flashing twrp through doing several times with no success. Could it be because I flashed the full update (recovery, bootloader and rom)? I got the update straight from sam mobile
Click to expand...
Click to collapse
No, that wouldn't stop you from flashing TWRP, what error did you get? Which version of TWRP did you try? Did you try different USB ports and/or cables?
mattzeller said:
No, that wouldn't stop you from flashing TWRP, what error did you get? Which version of TWRP did you try? Did you try different USB ports and/or cables?
Click to expand...
Click to collapse
Yes I've tried different usb ports/cables. Im on windows 8.1 and using odin v3.10. So far I've tried flashing twrp 2.8.4.0 and 2.8.0.0 both this error:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also tried cwm/philz touch and got errors:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.15.4-jfltespr.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
maurs4216 said:
Yes I've tried different usb ports/cables. Im on windows 8.1 and using odin v3.10. So far I've tried flashing twrp 2.8.4.0 and 2.8.0.0 both this error:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also tried cwm/philz touch and got errors:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.15.4-jfltespr.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I had problems flashing stock using Odin 3.10, give Odin 3.09 a try
mattzeller said:
I had problems flashing stock using Odin 3.10, give Odin 3.09 a try
Click to expand...
Click to collapse
Nah still got the same error on Odin 3.09
maurs4216 said:
Nah still got the same error on Odin 3.09
Click to expand...
Click to collapse
Hmmm, maybe the drivers? I have gone as far as formatted my computer reinstall windows and then reinstalled Samsung drivers just to make sure the computer wasn't the issue, turned out it was. Do you have another computer you could cleanly install the Samsung drivers and try flashing on that one?
King root probably works...
You can try King root and then replace King root with supersu. Check this out... https://www.youtube.com/watch?v=BVvmGs_q6n8
mattzeller said:
Hmmm, maybe the drivers? I have gone as far as formatted my computer reinstall windows and then reinstalled Samsung drivers just to make sure the computer wasn't the issue, turned out it was. Do you have another computer you could cleanly install the Samsung drivers and try flashing on that one?
Click to expand...
Click to collapse
K94U said:
You can try King root and then replace King root with supersu. Check this out...
Click to expand...
Click to collapse
Solved my issue today, and everything is working now! I used odin 1.85 with a samsung usb cable, flash twrp and supersu, thanks for you guys' help tho:good:
I've tried flashing the original Samsung roms on both Windows 7 & 8.1, on Odin 3.07, 3.09, 3.10.7 all failed in the same manner.
Flashing fails as soon as the system tries to flash cache.img.
Code:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone is the SM-N900 Exynos variant.
h3llb3nd4 said:
I've tried flashing the original Samsung roms on both Windows 7 & 8.1, on Odin 3.07, 3.09, 3.10.7 all failed in the same manner.
Flashing fails as soon as the system tries to flash cache.img.
Code:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone is the SM-N900 Exynos variant.
Click to expand...
Click to collapse
Udpate your Samsung drivers or simply install Kies 3. Try again then.
Joku1981 said:
Udpate your Samsung drivers or simply install Kies 3. Try again then.
Click to expand...
Click to collapse
I did install both Kies and Kies3, also made sure they weren't running. No avail. :/
h3llb3nd4 said:
I did install both Kies and Kies3, also made sure they weren't running. No avail. :/
Click to expand...
Click to collapse
Maybe is for that. Uninstall both. Only install now Kies 3 and try flash the firmware again.
* Are you sure that is the correct firmware for your device?
Your cache partition is most likely corrupted, just use the correct pit file for your n900 whilst flashing the rom.
Sent from my SM-N9005
Right, the issue was that I didn't flash the correct Pit file. But that's for another time.
NEW ISSUE!
In trying to solve the bad flash, during one of the flashes I checked NAND erase all. Now I just got the phone and have no EFS backups. is there any chance of fixing this? I don't have custom recoveries. Or do I have to send it in to Samsung?
The device boots fine, but I seemed to have wiped the phone's IMEI and baseband. The device can't register sims.
I was running CM13 for a while with no issues but I decided today to go back to stock because I want flip cover/s-view functionality without using garbage 3rd party apps to halfway do this.
Anyway....I tried to flash the stock ROM using Odin but it just made me stuck at a boot loop where it would play the Samsung animation about half way, freeze then restart and do this over and over again..
I installed TWRP and did a full wipe of everything, and now tried to install stock firmware using Odin again, and it writes everything to the phone in download mode then gets to the point where the device resets but then when it turns back on it just sits at the boot screen saying "recovery booting...." and locks up from there. If I even plug the phone in to charge it will freeze on the battery with the lightning bolt image and not proceed to the charging animation as it normally would and I need to pop the battery out to hard reset it out of this..
When I try to flash the stock firmware (G900W8VLU1COI4_G900W8OYA1COI4_G900W8VLU1COI4_HOME.tar) Odin says this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900W8VLU1COI4_G900W8OYA1COI4_G900W8VLU1COI4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> modem.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Please help....I don't know what I am missing. Is there a step I have missed somewhere along the way? Everything I read simply tells me to install the stock firmware using Odin to fix this, but that is actually what caused this issue in the first place and I cannot find any other info anywhere.
EDIT: I just reinstalled CM13 and it is working fine....what have I done to make it so that my phone cannot run the stock firmware anymore???
You should try to flash the KitKat image for your version. I am trying to find it right now, but that should work. I ended up having to do that when I went back to stock.