Tried installing Serendipity ROM and it keeps getting stuck at the following:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> param.lfs
<ID:0/004> zImage
<ID:0/004> boot.bin
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
Also tried going back to stock and I get stuck at modem.bin.
Can't seem to get to any recovery mode now either.
What to do???
You need Ultimate Unbrick. Get it here. Remember, you'll need to get into Download Mode, NOT RECOVERY, for Odin to work so you can restore.
Read, grasshoppa, read.
I tried Ultimate unbrick and im still getting the same results as OP above.
Related
Hi, reflashed my GS2 with the stock O2 ICS firmware as the non O2 one was giving me issues, as I was rooted, did a factory reset + clear cache, and all worked fine.
My friend saw me do this and asked if I could put his to the O2 ICS release as he was also on the stock ICS release, as we wanted to get it early ( we both are on O2 contracts)
Tried reflashing without a full factory reset, as he didn't want to loose data, and it failed. Now the phone says firmware issue but will still boot into download mode.
I've tried reflashing again and I can't get the phone back working, ODIN fails when flashing saying this
Code:
<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.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Not sure what to try, i've read some posts of people who claim to have got back to a working state, but none listed steps
Help!
Thanks
Chris
So here's what happened. I tried to install CWM 6.0.1.2 using EZ Recovery and it rebooted into ODIN with the words, could not do normal boot, in red. When I reboot it, it would just go back to the ODIN screen, so I tried to use the root 66 method. At first, it would get to system.img.ext4, but the green bar would barely move and be stuck there for 30 minutes. I would try again by taking out the USB cord, rebooting phone (maybe bad idea?). I did it again and it would be stuck there. I tried different USB ports on my laptop. Some will get to system.img and be stuck or get to recovery.img and say fail. Is my phone hard bricked or is there something else I can do? Thanks!
I also tried it on a different computer and it gets stuck on boot.img instead. Any help would be greatly appreciated!
It seems like using the older version of Odin gave me more consistent results. I now always get to system.img before it fails. The green bar gets 1/3 of the way then says failed.
<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> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Is there anyway to get it to be successful?
I've soft bricked my Galaxy Note I717 3 times in the last week while trying to update to the Jellybean firmware. Samsung Kies does not work. It says that there was a communication error during the upgrade process, whatever that means. I took it to the ATT store and they revived it within a few minutes with no data loss. This happened twice. I just tried to manually flash the update using odin, but I get this message:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> amss.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> mdm.bin
<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)
Now I'm stuck in download mode. I tried to flash the Jellybean ROM again, but it stops right there. I'm currently runnin the stock ICS firmware. Any suggestions?
Beastmutt said:
I've soft bricked my Galaxy Note I717 3 times in the last week while trying to update to the Jellybean firmware. Samsung Kies does not work. It says that there was a communication error during the upgrade process, whatever that means. I took it to the ATT store and they revived it within a few minutes with no data loss. This happened twice. I just tried to manually flash the update using odin, but I get this message:
Initialzation..
Get PIT for mapping..
Firmware update start..
amss.bin
NAND Write Start!!
boot.img
cache.img.ext4
mdm.bin
recovery.img
system.img.ext4
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Now I'm stuck in download mode. I tried to flash the Jellybean ROM again, but it stops right there. I'm currently runnin the stock ICS firmware. Any suggestions?
Click to expand...
Click to collapse
So what are you flashing exactly and what slot are you placing it in?
Sent from my CLEAN Note ll
Hello,
I recently borrowed my roommate's Verizon S4 because my phone broke. I rooted it because I have a different provider.
However, in my root addicted mind-set, I decided to get a custom ROM installed and so I tried to download recovery. This phone was running 5.0.1.
Upon downloading a recovery, the phone soft-bricked. It shows the Samsung logo with a wrench, and makes an error message when attempting to boot.
I tried using Odin to flash the stock firmware, but I kept getting the following error:
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've searched long and far and have yet to find a solution. I know that the reason for this issue is most likely due to the 5.0.1. build, but I was hoping that maybe something had developed in the last few months.
Any and all help is appreciated.
Also, I am not able to boot into recovery, but I am able to boot into download mode - I also reinstalled the Samsung drivers, and am using Odin 10.6. I tried using the ME7 firmware, but that didn't lead to much either.
I recently found a Verizon Software Assistant file and my phone won't be recognized on the application. Not sure what next steps are. I posted on reddit too, and no luck there either.
shivpaulchadha said:
Hello,
I recently borrowed my roommate's Verizon S4 because my phone broke. I rooted it because I have a different provider.
However, in my root addicted mind-set, I decided to get a custom ROM installed and so I tried to download recovery. This phone was running 5.0.1.
Upon downloading a recovery, the phone soft-bricked. It shows the Samsung logo with a wrench, and makes an error message when attempting to boot.
I tried using Odin to flash the stock firmware, but I kept getting the following error:
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've searched long and far and have yet to find a solution. I know that the reason for this issue is most likely due to the 5.0.1. build, but I was hoping that maybe something had developed in the last few months.
Any and all help is appreciated.
Also, I am not able to boot into recovery, but I am able to boot into download mode - I also reinstalled the Samsung drivers, and am using Odin 10.6. I tried using the ME7 firmware, but that didn't lead to much either.
I recently found a Verizon Software Assistant file and my phone won't be recognized on the application. Not sure what next steps are. I posted on reddit too, and no luck there either.
Click to expand...
Click to collapse
Hi shivpaulchadha
Thanks you for using XDA Assist.
I see you already posted in the correct forum before here. Could you please "bump" your thread up for it could be noticed by others users? I'm sure our experts in there will be able to tackle the issue.
Nice regards and good luck.
.
Hi all,
This may be a newb question but I've searched high and low and can't find an answer to this anywhere...
A friend gave me their parents tablet to try and fix. It's a Galaxy Tab 2 10.1 (GT-P5100). It won't boot, though will display charging animation so it's not a screen issue. Booted into download mode, installed Odin 3.07, downloaded firmware (P5100XXDMK3_P5100OPSDMK1_P5100XXDMK1_HOME.tar.md5 ) and flashed. Odin reports everything successful but the tablet boots and displays "Firmware update encountered an issue. Please select recovery mode in Kies & try again.". Have flashed a second time with a different carrier version of the same firmware - same result. The fact that its still writing gives me hope but I'm out of my depth as to what to do next. Any help would be greatly appreciated!
Log from previous flash:
<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> Sbl.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> system.img
<ID:0/004> boot.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> recovery.img
<ID:0/004> modem.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
I've also noticed the progress bar during the flash process on the tablet starts moving, but only gets a few cm long and then stops.
Anything I'm able to do at this point?
Try installing TWRP via Odin. Boot into TWRP if the install is successful and wipe everything. Then install whatever rom you were trying to install on the first place.