Need Help With Soft Brick - Verizon Samsung Galaxy S 4

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.

Related

[Q] Wifi Not Turning On

I recently installed Omega ROM and to my luck the wifi stopped working. I tried the steps they recommended and did exactly what they told me except I used the regular Odin program instead of the mobile. I tried flashing the modems on both the pda and phone section in odin and this is what happened:
<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> NON-HLOS.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone help with this? Im so tired of not having wifi..
Flash back to stock and start over doing the directions to the T.
Short answer - just reflash kernel, if it does not help - reflash your ROM and then kernel again. And if this does not help - you can always back to stock with full wipe (backup your data before).

[Q] Soft Bricked SCH-I545

I guess there is a first time for everything.
I can not boot into recovery and I get the message 'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I do not have Kies installed and nothing samsung is running.
I have tried multiple cables, usb ports, and downloads of SCH-I545_MDK_562219_Stock_Restore.tar.md5
*Edit* I just had a thought, is this happening because I am trying to go back to the stock rom I.E. before any Verizon firmware updates?
The phone says in red Start [224, 1440]
SW REV. CHECK FAIL : fused : 3, binary : 1
Here is the Odin Log
<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> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Any help would be appreciated. Thank you
Guess my phone was ME7 not MDK, hence why it wouldn't flash. I've got it flashed with an ME7 rom now and I think all is well. Thanks again.

[Help Requested] Restore Stock Firmware and Unroot

I downloaded the stock firmware from this thread: http://forum.xda-developers.com/showthread.php?t=2357200
I checked the md5 and it matched up perfectly, so no corrupt download.
I am in Download Mode on my Galaxy S4 SCH-i545 and I have Odin3 v3.07. I placed the extracted .zip file (which is a .tar.md5 file) into the PDA slot in Odin, placed a checkmark in it and clicked start.
I get the following message:
Code:
<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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<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 am currently stuck on the yellow exclamation screen on my device and desperately need help as I want to return the device. I have searched the forums and on google but what I have found hasn't helped me.
Thanks for any help!
I really need help and am sorry for replying to myself; however, I have tried everything I have found and nothing has worked. I can only get into download mode and to the yellow exclamation. Odin is failing and nothing shows up in Kies Emergency Recovery.
Don't worry, we can figure this out. Read through the entire thread you posted, the last post in that thread states that the guy was stuck on the yellow exclamation as well, but was relieved for some reason or another. You may find your answer there, and if not, private message that person to ask how they got around it.
What build do you have? MDK or ME7? The link you have is for ME7. If you need MDK, here are two different stock versions.
Why are you flashing this is the big question? Is the screen broken or something?

I accidentally clean wiped everything on my Samsung Galaxy J3 Emerge (Boost Mobile)

I accidentally clean wiped everything on my Samsung Galaxy J3 Emerge (Boost Mobile) (SM-J327P) with twrp. I decided to flash the stock rom and whenever I try an official stock rom I get FAIL! (Auth). Odin says:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<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> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone says
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 2
[1]eMMC write fail: ABOOT
I have tried multiple official stock roms. Thanks for any help. If someone has the latest official boost mobile stock rom please put it in the reply because I am not completely sure I'm using the latest versions.

Samsung Galaxy Note 4 bricked

Hello,
yesterday i decided to install a new custom rom. Had Note 7 ROM running for a half year.
At first i updated TWRP, after that my touchpad is not working correctly.(also in TWRP) I have to click 1 inch above the buttons to hit them...
So after a few tries to get a new ROM running(tried a few), finally one worked, but the problem with the touchscreen was still there. After that, i decided to install the stock firmware. Downloaded it from SAMMobile, but even that i can't install in Odin.
I already tried to wipe the complete phone with twrp and tried it with Pit file, but i get still the same error in Odin.
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<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> 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> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone help?

Categories

Resources