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?
Related
My rooted T-mobile Note did not like the OTA update it received today (hung at the samsung logo). I reflashed the rooted UVLG3 firmware image, following the instructions at http://androidlegend.com/how-to-root-t-mobile-galaxy-note-sgh-t879/. This worked, and I'm ignoring the OTA update for now.
I don't need root anymore, i didn't really use it anyways, I would like to get back to stock.
How do i get back to the stock/factory image? From http://forum.xda-developers.com/showthread.php?t=1837907, I see items B (T879-STOCK RECOVERY IMAGE) and D (T879-STOCK BOOT IMAGE). In ODIN, do I need to load one or both of these in one the sections (Bootloader, PDA, Phone, CSC, or UMS) and would i then hit the "Start" button?
Thanks for any help.
Just go to Samfirmware.com and download the tar file for the T879. Put it in the PDA section and start.
Sent from my SAMSUNG-SGH-I717 using xda premium
Thanks Charlie, that worked! In case any other newbie like me wants to know what to do, this is what i did:
Downloaded/installed Samsung Kies
Downloaded Odin 3.07 from www __ android __ gs
From samfirmware __ com, i searched for T879 and downloaded the file for "SGH-T879 USA (T-Mobile) 2013 January Android 4.0.4 T879UVMA1 T879TMBMA1". The ZIP file "T879UVMA1_T879TMBMA1_TMB.zip" has a large file called "HOME_T879UVMA1_CL892179_REV02_user_mid_ship.tar.md5", which I renamed to .tar
Powered off the phone, removed battery, connected USB cable to computer and phone, inserted battery, press power/vol-up/vol-down then hit vol-up to get into download mode
Started ODIN3 v3.07 (the box read 0:[COM4], message window read "<ID:0/004> Added!!")
Pressed PDA button, loaded the TAR file
Pressed START
Took about 4 minutes, then the green status bar finished, box above says RESET!, phone resets.
Message window:
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> amss.bin
<ID:0/004> cache.img.ext4
<ID:0/004> mdm.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
The phone automatically reset and started the boot sequence, took a few minutes to load updates, and everything was groovy again. When i connect the phone to Samsung Kies on my computer, it now reads "This is the latest firmware" (used to read something like "we don't what firmware is loaded").
How can i rooting the phone if i want to keep stock rom?
Do i have to do same as regular root?
Thank you.
Sent from my SGH-T879 using xda premium
I got it
Sent from my SAMSUNG-SGH-T879 using xda premium
bigape-revamped said:
Thanks Charlie, that worked! In case any other newbie like me wants to know what to do, this is what i did:
Downloaded/installed Samsung Kies
Downloaded Odin 3.07 from www __ android __ gs
From samfirmware __ com, i searched for T879 and downloaded the file for "SGH-T879 USA (T-Mobile) 2013 January Android 4.0.4 T879UVMA1 T879TMBMA1". The ZIP file "T879UVMA1_T879TMBMA1_TMB.zip" has a large file called "HOME_T879UVMA1_CL892179_REV02_user_mid_ship.tar.md5", which I renamed to .tar
Powered off the phone, removed battery, connected USB cable to computer and phone, inserted battery, press power/vol-up/vol-down then hit vol-up to get into download mode
Started ODIN3 v3.07 (the box read 0:[COM4], message window read "<ID:0/004> Added!!")
Pressed PDA button, loaded the TAR file
Pressed START
Took about 4 minutes, then the green status bar finished, box above says RESET!, phone resets.
Message window:
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> amss.bin
<ID:0/004> cache.img.ext4
<ID:0/004> mdm.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
The phone automatically reset and started the boot sequence, took a few minutes to load updates, and everything was groovy again. When i connect the phone to Samsung Kies on my computer, it now reads "This is the latest firmware" (used to read something like "we don't what firmware is loaded").
Click to expand...
Click to collapse
I did the same but the phone still hangs at the Samsung logo after I get the TMo Galaxy Note logo.
I had CyanogenMod on it with TWRP and tried to do a restore (bad idea) that's when it bricked.
I got a USB jig to get me to download mode so Odin would see it. All was installed just great but still the logo..
Just remember to flash the flash counter zip if u need to send it over to repairs with Samsung cus if they know ur phone is rooted they won't fix it cus rooting a device voids ur warranty... I flashcounter.zip everything I flash a rom... I usually flash that file last...
Sent from my SGH-T879 using xda premium
thanks all I just learn something from this:good:
Problem solved
JessSayin said:
I did the same but the phone still hangs at the Samsung logo after I get the TMo Galaxy Note logo.
I had CyanogenMod on it with TWRP and tried to do a restore (bad idea) that's when it bricked.
I got a USB jig to get me to download mode so Odin would see it. All was installed just great but still the logo..
Click to expand...
Click to collapse
Got it going. Had to jump on a Windows XP 32 bit PC to get the USB drivers to see the phone. Thanks for the help.
Running great on stock.
I have the update on my status bar but I'm wondering what did the update do for u? Can u post a screen shot of ur about phone info? Thnx
Sent from my SGH-T879 using xda premium
I'm curious, can I flash the stock everything of t879 on my at&t note? I have the i717 switched fully to t-mobile with twrp. I want the ota to upgrade from 4.04
Sent from my SGH-T879 using Tapatalk 2
JessSayin said:
I did the same but the phone still hangs at the Samsung logo after I get the TMo Galaxy Note logo.
I had CyanogenMod on it with TWRP and tried to do a restore (bad idea) that's when it bricked.
I got a USB jig to get me to download mode so Odin would see it. All was installed just great but still the logo..
Click to expand...
Click to collapse
I had to flash TWRP temporarily and wipe the phones emmc and flash the stock ROM again above instruction and worked. I guess before doing anything you should wipe/factory reset your phone first before flashing the stock ROM, this I can't test but just based on logical explanation.
My solution for being stuck on the Samsung logo
I know the last post was done a year earlier, but I thought I'd share this information I learned yesterday. After numerous flashing attempts My Note was stuck on the samsung logo.
I had soft bricked my Note by not clearing out the data on my phone. The previous post here gave me a clue and not being really good at this, I wasn't able to install and get TWRP to play nice with my non-working stock rom image. But I was still able to get the the Samsung Recovery and Download modes.
The working solution (borrowed from a post by andersbot on another thread) was:
1. Go to Recovery mode. Do a "clear cache" and next a "wipe data". Then reboot.
2. Go to Download mode and then connect to a XP PC and start up Odin. Be sure to use the latest Samsung USB drivers.
3. Flash with Odin using ther stock firmware downloaded from sammobile.com. Only tick the boxes for f.reset time and autoreboot (Odin default). Click PDA and load the downloaded file renamed with .tar at the end instead of .tar.md 5.
I dont know if this was the easiest way to clear the data on my SGH-T879, but it worked, and my Note started up correctly with the stock rom.
A few days ago I tried upgrading to 4.4.2 via safestrap and ran into some problems. Long story short I was stuck in Download mode but eventually got out of it and flashed 4.3 ML2. I rooted 4.3 before my problem and followed the instructions and everything worked. Flashed the two different tar files (pwndkernel and orignalkernel) so my wifi was working fine.
Now after I had the problem I can't get wifi working no matter what I try, and I can't flash anything besides the tar kernels but they aren't doing anything to fix my problem. Everytime I try to flash 4.3 so I can start from scratch it fails.
I have tried renaming and deleting wpa_supplicant.conf and that had no effect.
I have also tried doing a factory reset and I still have the same problem.
Any suggestions would help! I've been reading for the last 2 days trying to find something but no one seems to have the same issue.
Dan
dan123dbl said:
A few days ago I tried upgrading to 4.4.2 via safestrap and ran into some problems. Long story short I was stuck in Download mode but eventually got out of it and flashed 4.3 ML2. I rooted 4.3 before my problem and followed the instructions and everything worked. Flashed the two different tar files (pwndkernel and orignalkernel) so my wifi was working fine.
Now after I had the problem I can't get wifi working no matter what I try, and I can't flash anything besides the tar kernels but they aren't doing anything to fix my problem. Everytime I try to flash 4.3 so I can start from scratch it fails.
I have tried renaming and deleting wpa_supplicant.conf and that had no effect.
I have also tried doing a factory reset and I still have the same problem.
Any suggestions would help! I've been reading for the last 2 days trying to find something but no one seems to have the same issue.
Dan
Click to expand...
Click to collapse
Did you try flashing the MF1 modem.bin?
Devo7v said:
Did you try flashing the MF1 modem.bin?
Click to expand...
Click to collapse
I tried downloading it but was unable to (link was bad I think)
Would that work even though im mf2?
I also just tried flashing 4.3 again on a different computer with the right drivers installed and it failed.. I'm kind of lost as to why this is happening.
Just tried flashing modem.bin mf1 and got this
<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> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Everything I try and flash fails besides originalkernel.tar.md5
dan123dbl said:
Just tried flashing modem.bin mf1 and got this
Added!!
Odin v.3 engine (ID:3)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
modem.bin
NAND Write Start!!
Transmission Complete..
Now Writing.. Please wait about 2 minutes
Receive Response from boot-loader
FAIL! (Auth)
All threads completed. (succeed 0 / failed 1)
Everything I try and flash fails besides originalkernel.tar.md5
Click to expand...
Click to collapse
Odin is super picky. Make sure you are using the original cable that came with your phone. Try different usb ports, try to uninstall and reinstall the drivers, try different computers. Odin will work, the conditions just need to be right. There are also 2 versions of the MF1 floating around, one works and one doesn't.
Unfortunately the only thing I can tell you it's too keep trying, it will eventually work.
EDIT: Here's the correct modem file. http://forum.xda-developers.com/showthread.php?p=52001518
Devo7v said:
Odin is super picky. Make sure you are using the original cable that came with your phone. Try different usb ports, try to uninstall and reinstall the drivers, try different computers. Odin will work, the conditions just need to be right. There are also 2 versions of the MF1 floating around, one works and one doesn't.
Unfortunately the only thing I can tell you it's too keep trying, it will eventually work.
EDIT: Here's the correct modem file. http://forum.xda-developers.com/showthread.php?p=52001518
Click to expand...
Click to collapse
I was able to flash the mf1 modem you linked succesfully. Still no wifi though! Would it be worth trying to get a hold of an at&t sim card to update to 4.4.2 through the network? (I'm on rogers)
dan123dbl said:
I was able to flash the mf1 modem you linked succesfully. Still no wifi though! Would it be worth trying to get a hold of an at&t sim card to update to 4.4.2 through the network? (I'm on rogers)
Click to expand...
Click to collapse
There is no network update anymore, AT&T pulled it because it was messing up people's phones.
I don't know what to tell you, maybe try completely wiping the phone and flash the ML2 package again? It could be a hardware issue and in that case you'd have to send it in for warranty.
I wiped the phone and I was still unable to flash the ml2 package. I'm able to flash the modem.bin. I just can't flash any full packages for some reason. I have tried 3 different usb cables, including the one that the phone came with. I've tried 2 computers, and 3 different versions of odin.
I find it odd that I can flash modem.bin or originalkernel.tar but I can't do a complete package...
I bet it's something simple but I just can't figure it out.
I'm not sure how it would be a hardware issue since it happened right after I messed up going to 4.4.2. The wifi button just won't toggle, every time you go to turn it on it quickly goes back to off.
EDIT:
Right after I typed that I thought of something to try and it fixed it.....
In the whole odin package for 4.3 I decided to single out just the CP file and try to flash that since that's the modem file for the package.
After i flashed that it worked perfectly :silly::silly::silly:
Still have no idea why I couldn't flash the entire package but I will leave it alone for a while before I try and get to 4.4.2 again.
Thanks for all your suggestions!
You're a genius!
Thanks, it works!
dan123dbl said:
i wiped the phone and i was still unable to flash the ml2 package. I'm able to flash the modem.bin. I just can't flash any full packages for some reason. I have tried 3 different usb cables, including the one that the phone came with. I've tried 2 computers, and 3 different versions of odin.
I find it odd that i can flash modem.bin or originalkernel.tar but i can't do a complete package...
I bet it's something simple but i just can't figure it out.
I'm not sure how it would be a hardware issue since it happened right after i messed up going to 4.4.2. The wifi button just won't toggle, every time you go to turn it on it quickly goes back to off.
Edit:
Right after i typed that i thought of something to try and it fixed it.....
In the whole odin package for 4.3 i decided to single out just the cp file and try to flash that since that's the modem file for the package.
After i flashed that it worked perfectly :silly::silly::silly:
Still have no idea why i couldn't flash the entire package but i will leave it alone for a while before i try and get to 4.4.2 again.
Thanks for all your suggestions!
Click to expand...
Click to collapse
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?
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 -.-