Hello!
I recently got a S4 mini and decided to root so I could have an extended memory using link2sd! Everything was perfect but later the KITKAT update started to roll out, so i decided to go back to stock so I could update my phone... I downloaded a stock Rom from Sammobile and used odin to flash it... It keeps saying that EXT4 failed! So now its stuck in download mode! When I try to root just to see if it fixes anything it makes the Samsung boot sound and then the screen goes black.. I try reflashing the 4.4.2 Rom but it keeps failing!
Here is what ODIN3 3.0.7 says:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9195XXUCNEA_I9195VFRCNE4_I9195XXUCNEA_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> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Please tell me a fix because its stuck in firmware upgrade fail screen!
Also Kies wont detect it and i have installed USB drivers for my phone!
Also please don't say that I shouldn't have rooted and stuff because it is too late for that.
BTW I am going to thank (like) anyone who fixes this!
Yiannis1 said:
Hello!
I recently got a S4 mini and decided to root so I could have an extended memory using link2sd! Everything was perfect but later the KITKAT update started to roll out, so i decided to go back to stock so I could update my phone... I downloaded a stock Rom from Sammobile and used odin to flash it... It keeps saying that EXT4 failed! So now its stuck in download mode! When I try to root just to see if it fixes anything it makes the Samsung boot sound and then the screen goes black.. I try reflashing the 4.4.2 Rom but it keeps failing!
Here is what ODIN3 3.0.7 says:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9195XXUCNEA_I9195VFRCNE4_I9195XXUCNEA_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> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Please tell me a fix because its stuck in firmware upgrade fail screen!
Also Kies wont detect it and i have installed USB drivers for my phone!
Also please don't say that I shouldn't have rooted and stuff because it is too late for that.
BTW I am going to thank (like) anyone who fixes this!
Click to expand...
Click to collapse
Try a different ROM. I had the same problem with the NEA one but the NE6 loads OK.
Related
HELP
So, I should have read more thoroughly. I guess the Casual OneClick will not work with version 4.1.2 and soft bricked the phone.
So my fault.
I launched Odin to revert back to 4.1.1 but now Odin keeps failing and I can not recover.
I'm kind of a noob and don't know what else to do.
Odin Log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> param.bin
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT, my phone is back! sorry for the posts...I was in a bit of a panic
The solution was here: http://forum.xda-developers.com/showthread.php?p=41008476&nocache=1
Hey guys, Im having some issues with my samsung note 4 SM-N910G 5.1.1 lollipop. Yesterday I tried to flash the stock rom which I downloaded from sammobile, but it didn't work as it took forever. Now the problems Im encountering is that the phone can't enter recovery mode by pressing vol up+home+power. Instead, it shows a similar downloading screen as when vol+down, but the top message shows "unable to boot" or something. Now Im trying to flash the stock firmware, but it takes forever and doesn't seem to move, as follows:
Ok, it just failed flashing:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910GDTU1COJ5_N910GOLB1COJ1_N910GDTU1COJ4_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>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When I boot it up normally by pressing power button, it goes into a bootloop.
Hope to receive some help here.
Thanks.
Fixed it. Thanks for the prompt replies.
helo..
my tablet gt-p5110
cannot enter recovery (pwr+vol+) and download mode (pwr+vol-), but just stuck in "firmware upgrade encountered an issue, please recovery mode in kies & try again",but the device still connect and sync to odin.
I was using a pit file but when started there is an info from Odin that ''pit partition does not exist''.
when flashing use odin 3.07 with stock rom from samsung-updates.com / or cwm/twrp/chillpilz recovery for my device the flasher complete and pass..but after auto rebooting just got black screen,and if press power got back to firmware upgrade encontered an issue.
here the odin log :
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3100XXCME2_P3100OLBCME2_P3100DXDLL1_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> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> recovery.img
<ID:0/004> MLO
<ID:0/004> param.lfs
<ID:0/004> Sbl.bin
<ID:0/004> modem.bin
<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!!
tired use another odin version just get flashing FAIL and other gt-p3100 still stuck firmware issue
anyone can give me another solusion ?
i aready read all thread in forum xda about flashing/brick/recovery...but still no luck
when i try to flash my SM N915V and then i get this:
<ID:0/004> Added!!
<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/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> FAIL! (Ext4)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
At the Phone said like this:
IMG too big
How i can fix it?
Someone please help me
Are you flashing a custom rom or one from another region? Looks like your system img dies not match the data in your PIT file.
Flashing a stock rom should make it okay
Sent from my SM-N915G using Tapatalk
Hey,
I was successfully running LineageOS on my GT-N8010.
However, it froze at one point and I force turned it off, and ever since I just get the 'Firmware upgrade encountered an issue' screen. However, I am still able to get into download mode.
I'm now wanting to get it back to stock so I can re-try LineageOS on it. I have the stock image but if I try to install through ODIN I just get an error(posted below) and also on the tablet I get SW Rev. Invalid magic string.
Any idea how I could try sort it out?
In the details section of the download screen it shows;
ODIN MODE
Product name: GT-N8010
Current Binary: Samsung official
System status: Custom
Log:
Code:
<ID:0/004> Added!!
<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/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> tz.img
<ID:0/004> NAND Write Start!!
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Odin requires TAR files not image .
Flash stock rom via Odin .
Sboot.bin fail means you are flashing firmware with an older bootloader than is currently on the device .
JJEgan said:
Odin requires TAR files not image .
Flash stock rom via Odin .
Sboot.bin fail means you are flashing firmware with an older bootloader than is currently on the device .
Click to expand...
Click to collapse
Edit:
Looks like I didn't have the latest version, tried a newer one but it now gets stucks and after about 5mins of trying it stops at system.img;
Logs:
<ID:0/004> 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/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 1746 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Stuck on system.img means odin not recognized your system partition..
And or change USB port change usb cable .
Make sure that you have the least official firmware for your device and if it still fails,
it looks like a eMMC failure.
This problem is very common on the N80XX devices.
I already had to replace hundreds of eMMC's on them.