Database Users

[Q] Having issues booting up my N9005 after a failed 5.0 Official Lollipop Update

Hello, I have tried updating my N9005 to the latest firmware 5.0 provided on Sammobile. After attempting to flash it via ODIN, the following error occurs:
<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> 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>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Retried this step several times, but i have received the same error.
Following a few instructions found on the XDA forums, I tried using PIT file in order to re-partition.
The phone now reboots but will not go past the first boot screen "Samsung Galaxy Note3 N9005".
I tried pulling out the battery and performing a factory reset (along with wiping caches), but the situation is still the same after rebooting the device.
Also I have noticed that upon accessing "recovery mode", a error stating " Failed to mount /system (Invalid argument)" error is displayed.
I'm pretty new at upgrading phones and I've bought this phone recently and was unaware of the consequences of flashing ROMS via Odin.
The initial fw. on the device was 4.4.2 Official Samsung. Is there any way that I can make the phone reboot normally with fw. 4.4.2? Or any other firmware for that matter?
Thanks in advance.

AndreiRonaldo said:
Thanks in advance.
Click to expand...
Click to collapse
Reflash the firmware again now via ODIN without the .pit file.

Joku1981 said:
Reflash the firmware again now via ODIN without the .pit file.
Click to expand...
Click to collapse
I've tried that several times without success. But the issue was fixed. Apparently the PIT file I was using did not match the ROM i was flashing. I just had to find a matching pair of both ROM and PIT and now I've successfully booted my device. Hope that this thread might help others in need for answers to similar questions.

Alright, this is taking alot more than i had expected, after finally managing to boot my device, I've noticed that flashed rom behaves awfully, my phone is stuttering, and i have no sound. Also, my IMEI is displayed as "Unknown" in the "Status'" section of the device's Settings. Any suggestion on how to fix this issue?

flash the stock the rom you have before

Stuck in bootloop from trying to downgrade from 5.0 to 4.2

As the title says, I tried to downgrade from lollipop 5.0 to 4.2 because I've had several issues and I also wanted to get root. I think part of my mistake was I wiped data/factory reset before I flashed AP. Any help would be much appreciated, as I have been at this for the past five hours. I added some info below that might help below. Thanks
- I cannot boot into recovery and get the message (Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again)
- CP is the only thing that will flash and CSC also fails
- model number is g900a AT&T
- I have used Odin 3.10.7 and 3.09, but no luck
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> persist.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Did you try to repair him via kies?Maybe would help.
Sent from my D6503 using Tapatalk

Hey I have also experienced the same thing before, I was panicking that time, so I fixed it by flashing the old zip file, if that does not work try following the instructions your phone gave eg. Go to kies

VoltexYT said:
Hey I have also experienced the same thing before, I was panicking that time, so I fixed it by flashing the old zip file, if that does not work try following the instructions your phone gave eg. Go to kies
Click to expand...
Click to collapse
Kies and kies3 are both not recognizing my device. I heard it could be because of usb debugging, but I can't boot into my phone to check.

Allek84 said:
Did you try to repair him via kies?Maybe would help.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Both kies and kies3 are not recognizing my device.

Galaxy S4 9505 odin problem.

Hello i have a problem with flashing anything with odin on my Samsung Galaxy S4 9505.
Whenever i try flashing ROM or recovery or whatever, it says 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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also when i try to boot my phone normally or go to the recovery it says this:
"Firmware upgrade encountered an issue.Please select recovery mode in Kies & try again."
I've downloaded Kies and tried to recover it but it says:
'GT-I9505' does not support initializing.
What i've tried so far:
flashing pit file with and without the rom.Tried multiple odin versions.Tried multiple rom versions.Tried flashing recovery CWM and TWRP.
Also the error i got "Firmware upgrade encountered an issue.Please select recovery mode in Kies & try again." was after i tried flashing official rom 4.4.2 downloaded form Sammobile(first i installed TWRP recovery wiped system data dalvic cache and booted in download mode ). I was previously using latest Android 5.0.1 official.
Is there any hope of unbricking my device?

Have you tried reinstalling your ADB driver?
Honestly, kies sucks. You don't need kies to have ADB driver installed. There is a package that install samsung drivers seperately.

Once you upgraded to a lollipop bootloader you can't just simply go back to a kitkat one. Samsung doesn't allow that.
Try using the back USB ports on your PC. Trust me, it can do wonders.
You could also try Heimdall.

well i think i've advanced abit now i get this:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<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> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> persdata.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
tried to reinstall the ADB driver and using the back ports.
Also is there any way to flash Official Samsung ROM true a custom recovery?Cuz i just managet to install TWRP recovery on it.

hollydamn i just tried flashing true odin Android 5.0.1 and it worked.But the wifi isn't working it just not letting me turn it on.

Why don't people understand when I say YOU CANNOT DOWNGRADE ?

i didn't downgrade it now i've installed 5.0.1.

simeon112 said:
i didn't downgrade it now i've installed 5.0.1.
Click to expand...
Click to collapse
Yes, but you tried to, even after I explicitly said you can't.
Your WiFi issues might be related to modem/kernel.
You could try flashing a different firmware.

I tied a differed one the wifi works now.Only when i turn on the mobile data and try to go to a random site it says Forbidden.I think i need to wait my carrier to send me the setting for the net...
Anyway THANK YOU very much!! <3

I have an i337m (North American version of s4) and you can downgrade from stock 5.01 to stock 4.4.2. I did this on 3 phones in order to use regionlockaway to sim unlock all three phones. Everything worked, including data and wifi.
I'd like to try a downgrade with a i9505 for curiosity sake but that particular model is not sold by carriers in Canada.

Needing some serious help G900F

Hello all,
So ill make this short and sweet, I have an S5 the G900F and it wont boot, it just turns on, shows the Galaxy S5 logo, then appears to start the next Samsung logo but crashes instantly and restarts (does this on a loop)
I have attempted to use odin and flash using the latest firmware I believe to be correct for the phone, to which it fails at the end on "complete write operation failed". I then proceeded to try the recovery.tar file from the same rom and it worked (took about 10 seconds total) but im still getting the same loop.
Tried Kies and all that jazz, literally doesn't even see the phone so cant do jack, recovery mode doesn't boot, all I can get is download mode (home+vol down+power)
I would be ever so grateful if someone knows the answer to this as its driving me insane.
p.s. im by no way good with android so if im missing something blatantly obvious shout it out.
Where am I going wrong?
<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> 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> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks in Advance

Which firmware are you using? Do you have a branded or unbranded phone? What happens if you try installing unlocked BTU firmware? This was a problem of mine when I had a branded phone and then I got the motherboard changed due to a display crack and then I couldn't install my branded firmware and only unlocked firmware like BTU. If I wanted to install my locked (DRE) firmware, it failed at the same point on odin like on yours (hidden write) . Idk if installing unbranded firmware helps, but atleast try it out

Bricked SM-J510FN Help

Hello everyone,
I bricked my phone…. It is a SM-J510FN and when I start it right now, it shows "An error has occured while updating the decive Software. etc." Smart Switch is not recognizing the decive anymore, I cannot enter TRWP and I tried to Flash the stock Rom with Odin but it fails with the following error :
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 2878 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> hyp.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I would highly appreciate any help since I am running out of ideas what to do....
Thanks in Advance!

ottavio22 said:
Hello everyone,
I bricked my phone…. It is a SM-J510FN and when I start it right now, it shows "An error has occured while updating the decive Software. etc." Smart Switch is not recognizing the decive anymore, I cannot enter TRWP and I tried to Flash the stock Rom with Odin but it fails with the following error :
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 2878 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> hyp.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I would highly appreciate any help since I am running out of ideas what to do....
Thanks in Advance!
Click to expand...
Click to collapse
Did you try flashing TWRP again? Bc you flash stock one! If you could enter twrp, flash some of ROMs for your device.

RootingPro-18 said:
Did you try flashing TWRP again? Bc you flash stock one! If you could enter twrp, flash some of ROMs for your device.
Click to expand...
Click to collapse
Thank you for your answer. I did try that but was unable to to boot into TWRP. I finally managed to Flash the stock ROM via Odin. The mistake I pointed out above was fixed by changing from a 3.0 USB to a 2.0 USB port. Weirdly Odin seems to create Errors when using 2.0 in some rare Occasion. For everyone encoutering the same I encourage you to check if you are using a 2.0 USB.
Thank you for the answer anyway. Thread can be closed.

ottavio22 said:
Thank you for your answer. I did try that but was unable to to boot into TWRP. I finally managed to Flash the stock ROM via Odin. The mistake I pointed out above was fixed by changing from a 3.0 USB to a 2.0 USB port. Weirdly Odin seems to create Errors when using 2.0 in some rare Occasion. For everyone encoutering the same I encourage you to check if you are using a 2.0 USB.
Thank you for the answer anyway. Thread can be closed.
Click to expand...
Click to collapse
i had no issues with 3.0