Database Users

Help, Phone Says " Firmare Upgrade encountered an issue, Please use Software Repair

Help, Phone Says " Firmare Upgrade encountered an issue, Please use Software Repair
Hey Guys,
I have no clue what happened, Phone is stuck in ODIN Mode,
I am in odin 3.09, downloaded the pit file and the latest MJE firmware and i get to this step.
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help a lost soul...
Justin

Install pit by itself. Restart in recovery and factory wipe. Then install firmware
If I helped hit thanks!!

I did the pit file, not it stays locked at Samsung Galaxy Note 3 screen.
2swizzle said:
Install pit by itself. Restart in recovery and factory wipe. Then install firmware
If I helped hit thanks!!
Click to expand...
Click to collapse

Pit File - HLTE_USA_VZW_32G.PIT
PDA - MI9/MJ7/MJE (none work)
I am running odin as an administrator. I just can't get this thing to download to the phone... am i doing something wrong..
I put the phone in download mode.
Ive Done :
Download the MJE Stock Firmware 1.3 GB and extract it once...
Download latest ODIN 3.09...
In your device go into Download mode(Vol Down+Home Button+Power Button) and again Volume Up for Download mode...
Right click ODIN and open as administrator...
Now connect your device to PC and check the status in ODIN as Connected... (COM 5)
Make sure that only Auto Reboot and F.Reset Time are checked in ODIN...
Click on AP and select the extracted file from MJE firmware...
After checking the MD5 file...Click on START and wait I get the following error
-<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
is there something I am missing?
Thanks in advance!

Looks like you are trying to install I9 in your second post. Unless you were on i9 to start with you cannot downgrade. At the top of your post you refer to MJE. That is probably the reason.
Sent from my SM-N900V using Tapatalk

ive tried them all.. still no luck... verizon is sending me a new phone... it should load through odin, it doesn't nothing..

Well the issue was I was running ODIN in my VMWare Windows 7 Virtual Machine. I got my new phone today from verizon, for ****s i hooked it up to my old Windows XP machine and it went with out a hitch. I unplugged it was 75% so they can have it showing ODIN MODE..
Thanks for all the help...

[Q] I need help with my soft bricked verizon note 3

I bought my SM-N900V a few weeks ago and rooted it using Root de La Vega as soon as I got it home. Everything worked perfectly on the first attempt and I hadn't messed with anything since. I was probably stupid at one point and took the first OTA update because I noticed one day that I no longer had root access. I reboot my device every few days without an issue. My problem began about a week ago when I rebooted it like I regularly do and had it come to the message at the top saying "set warranty bit: kernel" followed by the Verizon screen which says "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." I rebooted into Odin mode a few times selected cancel to restart which got me back into the OS after a few attempts. A few days later I watched it restart itself into the same screen as before except that this time I haven't been able to get past it. I have the latest Samsung USB drivers installed, Odin 3.09, the MJE tar file from SamMobile, and the PIT file from these forums. No matter which cable or computer I use, I haven't been able to successfully flash the firmware, it consistently fails at boot.img. I can get into Odin/Download mode but not recovery mode. The only thing I ever did to the phone was root, nothing else. Please help me?

This thread had all you need to Odin back to mje
http://forum.xda-developers.com/showthread.php?t=2483380
sent from tapatalk....probably while pooping.

Thank you for the link but that thread was followed exactly prior to this post with no success.

This is what Odin shows every time that I try to flash any version firmware.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT.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> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Did u use the pit file as well and the tar?
Sent from my SM-N900V using Tapatalk

Yes, I used both files.

HELP

<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUGNF1_I9505OXAGNF1_I9505XXUGNF1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.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> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> modem.bin
<ID:0/004> NON-HLOS.bin
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)

Are you sure you have the right .tar image for your device?
Did you try downloading it again and trying with a fresh copy?

help
what i must do now my phone is in download mode at end stuck what now?

SchawanHD said:
what i must do now my phone is in download mode at end stuck what now?
Click to expand...
Click to collapse
A LOT more detail about what you are trying to do, what you started with, etc etc etc would be helpful.
Was the phone working before?
Are you just trying to update it?
What ROM did you have before? Stock or custom?
Give us the bigger picture here.
If your phone was working before then what you've done shouldn't have killed anything. Pull the battery and reboot and it should start up as normal.
The next thing I'd try (After the 2 things I've already suggested that you didn't check yet) is to uncheck REBOOT AUTOMATICALLY in Odin. When it fails, immediately run the update again. See what happens then.

HELP!
i have before make this Cyanogen mod 10.2 and then i decided to flash to stock rom
now i make an Fullwipe per CWM and then i took The tar of the firmware of my old stock version.
now my phone stuck at end of downloadmode (i'm too scared to pull off battery)
and odin says fail blablabla
CMOD had android 4.3.1 and i took I9505jtexx... 4.4.2

Skipjacks said:
A LOT more detail about what you are trying to do, what you started with, etc etc etc would be helpful.
Was the phone working before?
Are you just trying to update it?
What ROM did you have before? Stock or custom?
Give us the bigger picture here.
If your phone was working before then what you've done shouldn't have killed anything. Pull the battery and reboot and it should start up as normal.
The next thing I'd try (After the 2 things I've already suggested that you didn't check yet) is to uncheck REBOOT AUTOMATICALLY in Odin. When it fails, immediately run the update again. See what happens then.
Click to expand...
Click to collapse
i fullwiped the phone per CWM and try in downloading mode flashing the stock FW via ODin

Do the thing about unchecking auto reboot that i said earlier

Skipjacks said:
A LOT more detail about what you are trying to do, what you started with, etc etc etc would be helpful.
Was the phone working before?
Are you just trying to update it?
What ROM did you have before? Stock or custom?
Give us the bigger picture here.
If your phone was working before then what you've done shouldn't have killed anything. Pull the battery and reboot and it should start up as normal.
The next thing I'd try (After the 2 things I've already suggested that you didn't check yet) is to uncheck REBOOT AUTOMATICALLY in Odin. When it fails, immediately run the update again. See what happens then.
Click to expand...
Click to collapse
ok now what to do phone is in downloadmode stuck ?

Skipjacks said:
Do the thing about unchecking auto reboot that i said earlier
Click to expand...
Click to collapse
but if i pull off battery what will hapen? before flash i fullwiped phone!!!!

SchawanHD said:
but if i pull off battery what will hapen? before flash i fullwiped phone!!!!
Click to expand...
Click to collapse
As long as Odin isn't actively writing to the device, nothing will happen with a battery pull.
You shouldn't have full wiped the phone prior to this.
And please don't make multiple threads to discuss the same thing.
Just try the things I've suggested so far.

[Q] Need help with Recovery Problems.

I've been rooting and stuff since 2012. I got a S4 AT&T I337. I rooted with Geohots app. I don't know what its called, but you just tap "make it rain" and then you install SuperSu. All that worked fine, it rooted and I took off the bloatware with TBK. And after that I tried installing TWRP. I downloaded the TWRP app and chose the right phone and model I have and flashed the TWRP recovery. Then I rebooted and It booted into download mode and I got a message in red at the top saying "stuck in odin mode". I then took the battery out and booted into download mode by holding volume Down and power and then pressed down to restart the phone. The phone works fine it's just when I boot into recovery mode It boots into this download mode thing with a message in red saying 'Stuck in odin Mode'
I installed safestrap and now when I restart the phone from the Device options. Power Off, airplane mode and restart. it gives me the option to continue and boot normally or go into recovery mode. But at the top off safestrap in says safestrap Disabled I don't know what that means.
What did I do wrong? How can I fix this? And did I make a big mistake?
I have a I337 NI1 running 4.4.2 Stock. I just got this phone off ebay so I know for a fact it probaly hasn't been messed with.
I also tired uning triangle away but that didn't fix my problem. I'm thing about just getting a Stock NI1 odin .tar and doing an emerency flash.

Do you have an i337 our an i337m? I'm not clear on that. Twrp won't work on the i337
Sent from my Nexus 5 using XDA Free mobile app

I got the normal S4

You're most likely gonna have to use the Odin to stock thread in the general section. Sounds like you meant 1337 on NI1 baseband, which can't use twrp. You're right to use safestrap but it sounds like you might have mucked your phone up a bit.

I tried that but it didn't work out to well. odin almost finished but I got an error at the very very end of the flash. But I can still get into download mode. I'm thinking about flashing the MLD since the NI1 didn't work out.

How bad do you think I messed my phone up? what would you do to fix it? This is my first time working with the s4. Every other phone I had and rooted and messed with worked fine. But this s4 is something different. Do you think you can tell me the do's and don'ts on the s4. Thanks! I need to get it fixed by Friday.
Odin log file
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUFNB1_TWRootable_Full_Odin.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> 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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
It took less than 10 seconds to get this.

TylerMarshall256 said:
How bad do you think I messed my phone up? what would you do to fix it? This is my first time working with the s4. Every other phone I had and rooted and messed with worked fine. But this s4 is something different. Do you think you can tell me the do's and don'ts on the s4. Thanks! I need to get it fixed by Friday.
Odin log file
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUFNB1_TWRootable_Full_Odin.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> 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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
It took less than 10 seconds to get this.
Click to expand...
Click to collapse
Try different usb ports (use the ones in the back of the pc) and cables. Odin can be finicky. You're flashing the right file
Sent from my Nexus 9 using XDA Free mobile app

Murasakiii said:
You're most likely gonna have to use the Odin to stock thread in the general section. Sounds like you meant 1337 on NI1 baseband, which can't use twrp. You're right to use safestrap but it sounds like you might have mucked your phone up a bit.
Click to expand...
Click to collapse
jd1639 said:
Try different usb ports (use the ones in the back of the pc) and cables. Odin can be finicky. You're flashing the right file
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
That's what I figured it was. I'm on a little Acer laptop right now. I'm about to go use my cousins desktop. I hear those are better than laptops. I'll keep you updated man just stick with me.

ALRIGHT! All I did was go to my cousins house, install the USB driver! NOT KIES! And use his factory USB cable and it fixed it just FINE!!

I think I rooted too much?

I have a Note 4 SM-N910G that used to run on 5.1.1.
It kept bugging me for an update through OTA but couldn't cuz It was rooted
so I skimmed over the procedure and used TWRP and flashed my phone to CM13. Which ended up worse than before.
Sooo I flashed the stock rom for 6.1.1 using Odin aaand it was still laggy and now shuts down on its own.
Long story short, I re-rooted a couple of times. 30-ish. Aaaand now anything I flash my phone with keeps failing.
I know. I know. I'm an idiot.
It can still boot with VOL Down + Power button + Home though.
When I do the volume up procedure I get a "firmware upgrade encountered an issue".
Am I screwed or is there still hope?

Don't give up mate, Your phone is just laggy, not hard bricked. There is no 6.1.1 stock rom for note 4, we just got 6.0.1!!! I have flashed (rom, mods, recovery, etc) thousands of times in my note 4 and your issue may not have caused because of rooting or flashing. As u have already tried mm stock, Try to flash 5.1.1 unmodified stock rom with odin. Check the battery too, Once my friend's Note 2 had boot loop just because of the faulty battery, in live power(battery removed after samsung logo with charger plugged) it booted without a issue.

I'm having exactly the same issue, nothing I flash be it stock or rom is stable any more. Lags, then shuts off. Sometimes reboots on it's own, other times it needs the battery pulling. Nothing I have tried works

scorpienez said:
Don't give up mate, Your phone is just laggy, not hard bricked. There is no 6.1.1 stock rom for note 4, we just got 6.0.1!!! I have flashed (rom, mods, recovery, etc) thousands of times in my note 4 and your issue may not have caused because of rooting or flashing. As u have already tried mm stock, Try to flash 5.1.1 unmodified stock rom with odin. Check the battery too, Once my friend's Note 2 had boot loop just because of the faulty battery, in live power(battery removed after samsung logo with charger plugged) it booted without a issue.
Click to expand...
Click to collapse
So I left it without the battery on for a couple of hours and tried to flash the stock rom and it failed again. But halfway through though!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910GDTU1COL3_N910GVAU1COL3_N910GDTU1COL3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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! (Write)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

akeemcab26 said:
So I left it without the battery on for a couple of hours and tried to flash the stock rom and it failed again. But halfway through though!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910GDTU1COL3_N910GVAU1COL3_N910GDTU1COL3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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! (Write)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Use Kies to recover your phone. Choose firmware upgrade & initialisation and enter your full model number (for example SM-N910F) & serial number.

akeemcab26 said:
So I left it without the battery on for a couple of hours and tried to flash the stock rom and it failed again. But halfway through though!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910GDTU1COL3_N910GVAU1COL3_N910GDTU1COL3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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! (Write)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
See if you have checked repartition. uncheck it if it is checked(Uncheck this just before you are about to click on start) and flash again.

sanjaydev said:
See if you have checked repartition. uncheck it if it is checked(Uncheck this just before you are about to click on start) and flash again.
Click to expand...
Click to collapse
It's always unchecked though. Still the same result. Messes up at system.img.ext4

houstie said:
Use Kies to recover your phone. Choose firmware upgrade & initialisation and enter your full model number (for example SM-N910F) & serial number.
Click to expand...
Click to collapse
Kies 1? 2? or 3?
I'm using 3 btw.
Whenever I choose firmware upgrade & initialization it hangs when I search for my phone's model.

Ooookay. It said I needed a PIT File. I got one scouring the internet and did a flash.
I got 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> 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> 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! (Write)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Now I read somewhere that I need to enable something in my android to make the system.img.ext4 not fail.
But how can I enable that option if I can't even finish flashing? :|
If I boot it normally, I get firmware upgrade encountered and issue.

Rafa5e5t6yf said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
all I'm seeing are broken links :\

akeemcab26 said:
Kies 1? 2? or 3?
I'm using 3 btw.
Whenever I choose firmware upgrade & initialization it hangs when I search for my phone's model.
Click to expand...
Click to collapse
Kies 3. Make sure you use capital letters when entering your phone model.

houstie said:
Kies 3. Make sure you use capital letters when entering your phone model.
Click to expand...
Click to collapse
I enter the phone model, SM-N910G, click ok, and says do not remove usb connection.
after the preparation for the update finishes Kies 3 just turns black and nothing in it can be clicked.
My phone's firmware is now 6.0.1
The errors I get are
system.img.ext4 fail
rpm.mbn fail
firmware encountered an issue
mmc read failed to boot normal
either of the 4 show up after flashing.
tried flashing with the PIT file + the stock firmware, PIT file only, firmware only,
system.img.ext4 fails. Always does. But last night I tried it again and it went halfway through! But still failed.

Here You go,
1. Use Odin v3.10, go to PIT tab and select your device specific pit file first.
2. Click AP on the right side and select the latest firmware .tar.md5 file.
3. Go to options tab and select Auto-reboot, clear nand partition, re-partition, F.reset time & bootloader update as you need to format emmc (nand).
4. Flash the device, wait for it to complete and give it 5 mins to boot.
5. Once rebooted you may get stuck at samsung logo, dont worry, just go to stock recovery by pulling battery and holding down volup+home+power and perform a factory reset and clear cache.
6. Might take upto 5mins, but works like a charm.

akeemcab26 said:
I tried flashing with the PIT file + the stock firmware, PIT file only, firmware only,
system.img.ext4 fails. Always does. But last night I tried it again and it went halfway through! But still failed.
Click to expand...
Click to collapse
Use this PIT file I extracted from latest 6.0.1 binary stock rom.

vighneshpillai90 said:
Here You go,
1. Use Odin v3.10, go to PIT tab and select your device specific pit file first.
2. Click AP on the right side and select the latest firmware .tar.md5 file.
3. Go to options tab and select Auto-reboot, clear nand partition, re-partition, F.reset time & bootloader update as you need to format emmc (nand).
4. Flash the device, wait for it to complete and give it 5 mins to boot.
5. Once rebooted you may get stuck at samsung logo, dont worry, just go to stock recovery by pulling battery and holding down volup+home+power and perform a factory reset and clear cache.
6. Might take upto 5mins, but works like a charm.
Click to expand...
Click to collapse
Thanks for the reply!
I used the PIT file you gave me and used
N910GDTU1DPD4_N910GODD1DPB5_N910GDDU1DPB4_HOME.tar and
N910GDTU1DPD4_N910GODD1DPB5_N910GDDU1DPB4_HOME.tar
but both still gave me the system.img.ext4 fail
I checked
auto reboot,
repartition,
f. reset time,
nand erase all
and phone bootloader update on the third try
but still failed and gave me a new error written in blue or grey not sure but it was something like
odin failed to write.
edit: I can now boot to android recovery!
but at the very bottom it says
supported api: 3
dm-verity verification failed...
E: failed to mount /system (invalid argument)

Still hoping someone could help me!