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:
Odin engine v(ID:3.1005)..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Firmware update start..
SingleDownload.
sbl1.mbn
NAND Write Start!!
sbl2.mbn
sbl3.mbn
rpm.mbn
aboot.mbn
FAIL! (Auth)
Complete(Write) operation failed.
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.
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:
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.
via xda-developers http://ift.tt/1UxAYE7
Put the internet to work for you.
No comments:
Post a Comment