Okay, I had my S5 rooted on 4.4.4 NHA, and I tried to flash the NI2 ROM onto the phone. Now whenever I try to flash the stock ROM onto the phone, ODIN starts the process but fails after a bit.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
This is getting highly infuriating, and I would love someone to be able to help me out. I've tried searching for solutions but none of the are working. I am in download mode, the ROM is the correct one for my phone downloaded from SamMobile, I've tried using different USB ports, removing the SIM, using different USB cables, and the NCG stock ROM. Any help would be highly appreciated.
..
Thank you for the response! I did eventually manage to get it to flash, after many, many tries. I think maybe 20? At any rate, the methods I saw in other threads did work, I just had to keep trying. Thanks again!
Related
Hello, after hours of searching on google i cannot seem to find a solution to my problem. I am running 4.4.2 NC1. I have rooted it with towel root and tried flashing twrp with rom installer. It claimed success but now i cannot boot into recovery. I have tried flashing twrp with odin but it gives me this error:
"<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
I have tried restarting my computer, phone and using a different chord. Im at the end of my rope here and need some help. Thanks in advance.
You can't flash twrp. The only recovery you can use is safestrap. Start by reading this
http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 5 using XDA Free mobile app
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
Hey everyone,
So I've finally had my first soft brick :crying: Hopefully I am missing some easy solution. So here's the background. This morning I was running MF3 with root. Using this guide http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642 I was able to upgrade to NB1 using Odin. Then I upgraded to NJ4 using stock recovery added root using towelroot v3. Then the trouble began.
I noticed my WiFi wouldn't switch on so I performed a stock recovery wipe data then factory reset. This didn't fix the problem. I then tried to use Odin to go back to NB1 because my WiFi was working back then. It failed halfway through (message on Odin) so I left it sitting for about 30 min. The phone never changed anything so I removed the battery and tried Odin again. It failed again. I decided to try to boot into stock recovery and was unable to do so. I have the screen with a phone (dot)(dot) yellow triangle (dot)(dot) computer saying Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Tried Odin again and I actually got about 75% through the process but it failed again. Now it makes the same amount of progress every time and continues to fail.
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1005)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
My overall goal is to upgrade to OC3 with root access but right now it seems like I just need to unbrick my phone. Any ideas?
Update: Even though there are a bunch of warnings against it I went ahead and used Odin to redo my PIT file. Now I can boot into recovery. About to wipe data/factory reset.
Update 2: After the factory reset I tried to flash NB1 again using Odin. Still failing near the beginning, but with all my resetting I was finally able to get into the phone itself (WiFi still won't turn on). Also when starting up I no longer have the Samsung Custom with the lock (I'm assuming this means my root is gone for now). Now to figure out a way to fix the WiFi....
Update 3: My baseband version is NJ4 and the build version is NB1. I'm pretty sure this is why the WiFi is not working. I am now following this guide http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814 to get to OC3. Hopefully this will fix the WiFi issue...
ava12ice said:
Hey everyone,
So I've finally had my first soft brick :crying: Hopefully I am missing some easy solution. So here's the background. This morning I was running MK3 with root. Using this guide http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642 I was able to upgrade to NB1 using Odin. Then I upgraded to NJ4 using stock recovery added root using towelroot v3. Then the trouble began.
I noticed my WiFi wouldn't switch on so I performed a stock recovery wipe data then factory reset. This didn't fix the problem. I then tried to use Odin to go back to NB1 because my WiFi was working back then. It failed halfway through (message on Odin) so I left it sitting for about 30 min. The phone never changed anything so I removed the battery and tried Odin again. It failed again. I decided to try to boot into stock recovery and was unable to do so. I have the screen with a phone (dot)(dot) yellow triangle (dot)(dot) computer saying Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Tried Odin again and I actually got about 75% through the process but it failed again. Now it makes the same amount of progress every time and continues to fail.
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1005)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
My overall goal is to upgrade to OC3 with root access but right now it seems like I just need to unbrick my phone. Any ideas?
Click to expand...
Click to collapse
Mk3 is a sprint s3 modem, make sure you're in the right forum. As far as what else to try, I'm not sure.
Sorry not MK3, I meant MF3 (original post edited as well)
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
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