[Q] Stuck in Download mode - Verizon Samsung Galaxy S 4

Hello,
I have a Verizon Galaxy S4. Today I rooted it. It all went fine, but I wanted to install a custom recovery. I followed a tutorial online, which lead me to downloading the Goo manager, and installing TWRP via that. I rebooted, and it went straight into download mode. It would not leave download mode, it continuously loops back to that. I connected it up to Odin, and downloaded the stock firmware to flash. The progress bar came up, loaded for a few minutes. Then, I got a big FAIL message. (Using 3.04). Now, its still in DL mode, but it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Tried flashing the stock firmware again, but keeps failing. Tried different USB ports, but keeps failing. Any suggestions?

Try flashing another recovery via odin
Sent from my GT-I9300 using xda premium

Jamiew1977 said:
Try flashing another recovery via odin
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
On it.

It happened to me with my s3, installed twrp with goo and I had no recovery. Flashed a different recovery with Odin and all was sweet, Hope you fix it.
Sent from my GT-I9300 using xda premium

Jamiew1977 said:
It happened to me with my s3, installed twrp with goo and I had no recovery. Flashed a different recovery with Odin and all was sweet, Hope you fix it.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Can't find a tar file flashable via Odin. All I can find is the Loki method, which I cannot do because I'm stuck in DL mode. Waiting on a download of a different stock firmware.

Dont think there is any recoveries flashable via odin. Were you on me7 by chance?
Sent from my SCH-I545 using Tapatalk 2

hexitnow said:
Dont think there is any recoveries flashable via odin. Were you on me7 by chance?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Nope.

Turn your phone all the way off and then use the button combo for odin, decline and it should boot. DoubleCheck your firmware version because what youre describing is what happens when you flash a recovery on me7, which you cant.
Sent from my SCH-I545 using Tapatalk 2

hexitnow said:
Turn your phone all the way off and then use the button combo for odin, decline and it should boot. DoubleCheck your firmware version because what youre describing is what happens when you flash a recovery on me7, which you cant.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Didn't work. Went right back into DL mode after I declined.

When you were flashing the firmware via odin did it error when it was going to flash aboot?
Sent from my SCH-I545 using Tapatalk 2

hexitnow said:
When you were flashing the firmware via odin did it error when it was going to flash aboot?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Yes. It says FAIL! (Auth) right after aboot.mbn

Do you have a link to the root method you used?
Sent from my SCH-I545 using Tapatalk 2

hexitnow said:
Do you have a link to the root method you used?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Yep here it is: http://forum.xda-developers.com/showthread.php?t=2380325
PS: Thank you so much for sticking with me so far

Not a problem. Yep youre on the me7 firmware like I thought. Im guessing your trying to flash the mdk firmware thru odin? Me7 wont let you flash anything prior is why youre getting the errors. Youll have to download the me7 odin file (in dev section) and flash again. Once you get your phone booted again you cant flash a custom recovery or else itll do the same again. Theres a few people working on unlocking/bypassing the bootloader so hopefully it wont be much longer until me7 has custom recovery.
Sent from my SCH-I545 using Tapatalk 2

hexitnow said:
Not a problem. Yep youre on the me7 firmware like I thought. Im guessing your trying to flash the mdk firmware thru odin? Me7 wont let you flash anything prior is why youre getting the errors. Youll have to download the me7 odin file (in dev section) and flash again. Once you get your phone booted again you cant flash a custom recovery or else itll do the same again. Theres a few people working on unlocking/bypassing the bootloader so hopefully it wont be much longer until me7 has custom recovery.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
You are a savior my man. Thank you.

Not a problem
Sent from my SCH-I545 using Tapatalk 2

Related

[Q]Boot Loop + No Access to Recovery

I recently flashed the latest Hyperdrive ROM onto my Samsung Galaxy S4 Device. Everything was perfectly fine until I started getting weird unmounting errors from my SD card. I thought nothing of it as my camera still had access to files on the SD card. But tonight after eating dinner I came up to find my phone on the Samsung Custom screen with the lock icon as if it were booting up. I learned that this was a boot loop. So I instantly tried to do a factory reset and the problem arose when I couldn't access recovery. It would show the text in the top left corner then it would disappear and reboot and get stuck in the same loop. When I plug in the charger it gets stuck on this battery icon but it is frozen.
After hours of searching I downloaded the original verizon rom from stockroms.net. After having trouble with it saying PIT not found I realized that it was the USB port. It successfully flashed the original firmware. It then went back into the boot loop. The video I was watching to do this said this could happen so I tried once again to go into recovery. This time I knew the recovery was even back to default (I was using goo manager) as the text at the top left changed. But it once again rebooted and got stuck in the boot loop not letting me into recovery.
If anyone has anything I can do to fix this, I am all ears. Sorry if this has been answered previously but I have found nothing. Trust me. I have searched.
EDIT: I was able to get into ODIN nothing else. I flashed with ODIN.
Were you flashing the stock rom through recovery? If you werent grab the odin flashable images from the dev section and flash that. Should get you running again.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
Were you flashing the stock rom through recovery? If you werent grab the odin flashable images from the dev section and flash that. Should get you running again.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
I flashed with Odin if that is what you mean. I can't get into recovery but I used Odin to flash the original firmware.
nickcode122 said:
I flashed with Odin if that is what you mean. I can't get into recovery but I used Odin to flash the original firmware.
Click to expand...
Click to collapse
After you said u grabbed the stock firmware from stockroms you didnt specify your flashing method I wasnt sure how you were doin it. Your download might be corrupted so I would delete it, redownload it, then verify the md5 is correct, and then try again. Your flashing under pda and not phone right?
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
After you said u grabbed the stock firmware from stockroms you didnt specify your flashing method I wasnt sure how you were doin it. Your download might be corrupted so I would delete it, redownload it, then verify the md5 is correct, and then try again.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
How do I verify the md5 is correct? Also, I'm wondering if the problem lies with it being a nowipe version of the rom. Is there anyway to find a rom that WILL wipe? I can't find any around the forum nor on google.
Google md5 checker or md5 verifier. I checked the link but sadly there wasnt an md5 posted for the file. I would still download a verifier tho they come in handy. There is wipe versions in the dev section. I decided to be nice and I grabbed the link for you. Also your flashing under pda and not phone right?
http://forum.xda-developers.com/showthread.php?t=2289325
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
Google md5 checker or md5 verifier. I checked the link but sadly there wasnt an md5 posted for the file. I would still download a verifier tho they come in handy. There is wipe versions in the dev section. I decided to be nice and I grabbed the link for you. Also your flashing under pda and not phone right?
http://forum.xda-developers.com/showthread.php?t=2289325
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I will try and download this. And yes, I'm using the PDA section.
nickcode122 said:
Thanks, I will try and download this. And yes, I'm using the PDA section.
Click to expand...
Click to collapse
Ok just checkin. Hope it works out for ya :thumbup:
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
Ok just checkin. Hope it works out for ya :thumbup:
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
This rom worked! Thank you so much! Any idea what happened so I can prevent it from happening again?
I would assume it was probably just a bad download. Glad to hear you got 'er up and running.
Sent from my SCH-I545 using Tapatalk 2

Hopefully soft bricked s4

So my friend rooted his s4 he cant remember how then got the tarp app from the play store to install tarp not goomanager and then when he booted to recovery its said could not boot normally and went into download mode. We tried goomanager but now no matter what you try to boot it says the same thing. I tried flashing the stock firmware on it but it failed in Odin. Any ideas?
Sent from my SPH-L300 using xda app-developers app
You never mentioned what firmware your friend is on. But I'm guessing it's me7. Flash the me7 firmware in Odin. Then don't try to put a recovery on the phone. You can't or you'll end up where you are now. Then have your friend read a lot before he tried custom roms.
well that's what I as trying to do was flash the stock I don't know what he was on. It failed right after aboot.mbn
Sent from my SPH-L300 using xda app-developers app
I tried to flash MDC
Maybe try the other one? Do you have a link for that?
Sent from my SPH-L300 using xda app-developers app
And don't I need to put a recovery on the phone TO put on a custom ROM? How do you put them on I thought you just flashed the zip/tar
Sent from my SPH-L300 using xda app-developers app
I'll try me7
Sent from my SPH-L300 using xda app-developers app
blu422 said:
And don't I need to put a recovery on the phone TO put on a custom ROM? How do you put them on I thought you just flashed the zip/tar
Sent from my SPH-L300 using xda app-developers app
Click to expand...
Click to collapse
It failed on aboot because he has an me7 phone and your trying to flash the mdk firmware which yoh cant do. Grab the me7 image from the dev section and flash that. You cant install a custom recovery on me7. Youre only options for romming are rooting then installing safestrap. So you and your friend got a bit of reading to do.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
hexitnow said:
It failed on aboot because he has an me7 phone and your trying to flash the mdk firmware which yoh cant do. Grab the me7 image from the dev section and flash that. You cant install a custom recovery on me7. Youre only options for romming are rooting then installing safestrap. So you and your friend got a bit of reading to do.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
Click to expand...
Click to collapse
Thanks for the help me7 worked I'll look into safestrap
Sent from my SPH-L300 using xda app-developers app

Go back to Stock but Odin Fails. . How to do it?

Long story short.. I used odin to flash the new mi5 tar and then took the mj4 update. Everything was good but I flashed a mod from old software and got stuck on the splash screen. Now whenever I use Odin it fails except for flashing twrp it works. I pretty much want to start from scratch but not sure how to get to Stock without Odin. Any help would be great! Thanks..
Sent from my SM-N900P using XDA Premium 4 mobile app
bigmase23 said:
Long story short.. I used odin to flash the new mi5 tar and then took the mj4 update. Everything was good but I flashed a mod from old software and got stuck on the splash screen. Now whenever I use Odin it fails except for flashing twrp it works. I pretty much want to start from scratch but not sure how to get to Stock without Odin. Any help would be great! Thanks..
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Gave you some options on the other thread. Also could try kies.
Sent from my SM-N900P using Tapatalk
Kies won't let me do anything...
bigmase23 said:
Long story short.. I used odin to flash the new mi5 tar and then took the mj4 update. Everything was good but I flashed a mod from old software and got stuck on the splash screen. Now whenever I use Odin it fails except for flashing twrp it works. I pretty much want to start from scratch but not sure how to get to Stock without Odin. Any help would be great! Thanks..
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which mod?
Sent from my SM-N900P using Tapatalk
LMMT said:
Which mod?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Freeza's 4 in 1 reboot..
i ran into the same problem and haven't been able to get anything to work...the phone won't even go into recovery and i have a firmware upgrade encountered an issue when i turn the phone on...
edit: flashed the cf auto root and twrp in odin then flashed jellybomb...back up and running

[Q] recovery not booting

I am now on 4.4.2 NC5 and was able to root using CFroot.
However, any recovery I try to install has about the same result: the screen right before recovery bootloops. I must take out the battery, boot into odin and cancel. Then it boots normally.
I even went so far as to use GooManager to install twrp. Same deal.
This also happened on 4.3 MJ4.
I have tried odin 1.86 anf 3.07. I have a feeling it is on the phone, I mean, I can do a hard reset into recovery. Android recovery is there with a android on his back with a red exclamation.
At this point, I am unable to flash anything
rosystreasures said:
I am now on 4.4.2 NC5 and was able to root using CFroot.
However, any recovery I try to install has about the same result: the screen right before recovery bootloops. I must take out the battery, boot into odin and cancel. Then it boots normally.
I even went so far as to use GooManager to install twrp. Same deal.
This also happened on 4.3 MJ4.
I have tried odin 1.86 anf 3.07. I have a feeling it is on the phone, I mean, I can do a hard reset into recovery. Android recovery is there with a android on his back with a red exclamation.
At this point, I am unable to flash anything
Click to expand...
Click to collapse
Thought I would try to odin the nc5 bootloader. It gave me the kernel upload error message. I am now reinstalling nc5 oneclick restore.
rosystreasures said:
I am now on 4.4.2 NC5 and was able to root using CFroot.
However, any recovery I try to install has about the same result: the screen right before recovery bootloops. I must take out the battery, boot into odin and cancel. Then it boots normally.
I even went so far as to use GooManager to install twrp. Same deal.
This also happened on 4.3 MJ4.
I have tried odin 1.86 anf 3.07. I have a feeling it is on the phone, I mean, I can do a hard reset into recovery. Android recovery is there with a android on his back with a red exclamation.
At this point, I am unable to flash anything
Click to expand...
Click to collapse
Try using twrp version 2.7.0.1 and Odin 3.09...never had any problems with those. When you used cfroot, you did get the screen with the red pirate android saying it rooted?
Sent from my SM-N900P using Tapatalk
tonyevo52 said:
Try using twrp version 2.7.0.1 and Odin 3.09...never had any problems with those. When you used cfroot, you did get the screen with the red pirate android saying it rooted?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Yes, I saw the red pirate android
I will find odin 3.09 and try that.
I am confused about installing twrp in odin. Do I want the .img file or the .img.tar file?
I always use the tar file and works. Your phone is fine though, just need to get the root and recovery to stick. When all else fails though..rj's one clicks are life savers and at least get you back to stock.
Sent from my SM-N900P using Tapatalk
tonyevo52 said:
Try using twrp version 2.7.0.1 and Odin 3.09...never had any problems with those. When you used cfroot, you did get the screen with the red pirate android saying it rooted?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
FInally got 3.09 installed. I believe I use AP??
rosystreasures said:
FInally got 3.09 installed. I believe I use AP??
Click to expand...
Click to collapse
Yea, use the ap box.
Sent from my SM-N900P using Tapatalk
tonyevo52 said:
Yea, use the ap box.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
OMG!! It worked!!! I got twrp!!!
ty!!!
rosystreasures said:
OMG!! It worked!!! I got twrp!!!
ty!!!
Click to expand...
Click to collapse
Glad it worked, make sure to flash SU...and then you'll be golden!
Sent from my SM-N900P using Tapatalk
tonyevo52 said:
Glad it worked, make sure to flash SU...and then you'll be golden!
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
got that too!! I Am sssooo excited!!!
rosystreasures said:
got that too!! I Am sssooo excited!!!
Click to expand...
Click to collapse
Now that you have all that done...make a backup in twrp..I always make one right after I root and install recovery so if I ever have to go back to the start, I use that instead of having to use the one click method. If you haven't used twrp, I always make a backup of the boot, data, and system and save to the card.
Sent from my SM-N900P using Tapatalk
tonyevo52 said:
Now that you have all that done...make a backup in twrp..I always make one right after I root and install recovery so if I ever have to go back to the start, I use that instead of having to use the one click method. If you haven't used twrp, I always make a backup of the boot, data, and system and save to the card.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I am doing it right now. oops, just finished.

I am reaching out for help. ODIN not flashing, and bricked.

Hello fellow members.
I have an S4 SCH-I545
I feel as if I'm out of options, I have read many forums for the past 3 days and cannot find a method that works. I am currently soft bricked and cannot get ODIN to successfully flash anything. When I pull the battery and try to boot it immediately takes me to ODIN Mode, and I can't seem to get into anything but that. Just recently it has given me a new image that says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I don't exactly know what it is referring to but I have Kies and there is only an emergency recover area and that does nothing.
Am I out of options? Any help is extremely appreciated.
If I left anything out let me know.
jeffysonp said:
Hello fellow members.
I have an S4 SCH-I545
I feel as if I'm out of options, I have read many forums for the past 3 days and cannot find a method that works. I am currently soft bricked and cannot get ODIN to successfully flash anything. When I pull the battery and try to boot it immediately takes me to ODIN Mode, and I can't seem to get into anything but that. Just recently it has given me a new image that says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I don't exactly know what it is referring to but I have Kies and there is only an emergency recover area and that does nothing.
Am I out of options? Any help is extremely appreciated.
If I left anything out let me know.
Click to expand...
Click to collapse
What build were you on prior to this?? Jellybean...Kit Kat ?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
What build were you on prior to this?? Jellybean...Kit Kat ?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
aircooledbusses said:
Alright, I know this is not the help/question/noob thread, but I'm I'm a pickle. Redirect me if you must. Verizon s4 that was on nc5 baseband-i don't know the bootloader, but it was 4.4.2 if that helps. Rooted with towel root and twrp through too manager. Yeah, I know that's where the problem came from. So now the phone is (hopefully) in a soft brick state stuck in down load or Odin mode. Odin recognizes the phone. I don't care to keep DAT or retain root, I just was it to function. Is the nc5 full wipe with the pit my correct next step? Thank you in advance, razz me if you must, I deserve it
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Looks like me and snoopy are in the same boat, or at least our phone is in the same soft brick state. Is there any hope?
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Looks like me and snoopy are in the same boat, or at least our phone is in the same soft brick state. Is there any hope?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Absolutely there is hope. We just need to know what exact build your phones were on prior to this soft brick. Then we'd know what Odin files to give you.
Then if there were still errors you could post them here for more help.
What were you guys doing exactly that brought you to this point?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Absolutely there is hope. We just need to know what exact build your phones were on prior to this soft brick. Then we'd know what Odin files to give you.
Then if there were still errors you could post them here for more help.
What were you guys doing exactly that brought you to this point?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I had baseband nc5. It was android version 4.4.2. Phone worked and I rooted it with towel root, the phone was rebooted and checked root with rootchecker. Then I flashed twrp 2.7.1 for jfltevzw with gooo manager and after that my problems began. Phone would not come out of Odin mode. I did try to Odin the nc5 emergency no wipe and it failed changing the Odin screen to the one that snoopy described.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
I had baseband nc5. It was android version 4.4.2. Phone worked and I rooted it with towel root, the phone was rebooted and checked root with rootchecker. Then I flashed twrp 2.7.1 for jfltevzw with gooo manager and after that my problems began. Phone would not come out of Odin mode. I did try to Odin the nc5 emergency no wipe and it failed changing the Odin screen to the one that snoopy described.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright sorry to make you write that again.. I just now saw you included your quote from an earlier post.
Are you able to hop onto your PC and copy and paste what the Odin error is into this thread?
Trying to flash a custom recovery on anything other than MDK will certainly lead to a soft brick most of the time. However you should be able to recover your phone back.
Using the full wipe NC5 Odin file should do it.. However if that's not working for you only those errors being posted here will allow the right people to help you along.
May seem silly but have you tried simply trying another USB cable? I've seen people on here have Odin flashes fail just due to the cable.
Grab the Odin errors though if you can
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Alright sorry to make you write that again.. I just now saw you included your quote from an earlier post.
Are you able to hop onto your PC and copy and paste what the Odin error is into this thread?
Trying to flash a custom recovery on anything other than MDK will certainly lead to a soft brick most of the time. However you should be able to recover your phone back.
Using the full wipe NC5 Odin file should do it.. However if that's not working for you only those errors being posted here will allow the right people to help you along.
May seem silly but have you tried simply trying another USB cable? I've seen people on here have Odin flashes fail just due to the cable.
Grab the Odin errors though if you can
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thank you, I'm traveling for the next few days, but will get set up with a different Samsung stock cable at my PC and report back. Knowing there is hope is a relief.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Thank you, I'm traveling for the next few days, but will get set up with a different Samsung stock cable at my PC and report back. Knowing there is hope is a relief.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There's definitely hope. If Odin can't bring you back I bet Heimdall could. It's a little more involved but obviously worth it.
Sent from my SCH-I545 using Tapatalk
Awesome! I've never used hemidal yet, but have recently been doing much better with adb commands, so I'm totally willing to learn. I'll post back here in a few days
Sent from my Nexus 7 using XDA Premium 4 mobile app
I was trying to flash Hyperdrive and ended up having to update to NC5, I can't remember what my phone was out of the box, I will be able to tell you in a few hours when I get my box. I just got the phone last week, so probably 4.3.
aircooledbusses said:
I had baseband nc5. It was android version 4.4.2. Phone worked and I rooted it with towel root, the phone was rebooted and checked root with rootchecker. Then I flashed twrp 2.7.1 for jfltevzw with gooo manager and after that my problems began. Phone would not come out of Odin mode. I did try to Odin the nc5 emergency no wipe and it failed changing the Odin screen to the one that snoopy described.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Your firmware is mdk?....because if you not mdk you CANT use goo manger or twrp or cwm. ...you can only use safestrap....If you were mdk...and you went to nc5 you can never go back.
sent by safestrap powered echo v26
decaturbob said:
Your firmware is mdk?....because if you not mdk you CANT use goo manger or twrp or cwm. ...you can only use safestrap....If you were mdk...and you went to nc5 you can never go back.
sent by safestrap powered echo v26
Click to expand...
Click to collapse
Uh yeah I think that was my mistake. The attempt to flash twrp while on nc5 borked the phone.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Uh yeah I think that was my mistake. The attempt to flash twrp while on nc5 borked the phone.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yep..definitely the mistake
this thread and links would have helped you before you jumped off the cliff
http://forum.xda-developers.com/showthread.php?t=2606501
also odin is very touchy with using usb cables, usb ports and computers
Looks like you are trying to Odin to an image that was lower firmware than what your phone was on. You might want to try flashing the full wipe nc5 image that has been posted. I can't link to it now as I'm on my phone but if you Google Odin full wipe Verizon nc5 it should bring you to the proper xda thread to get the file.
Sent from my SCH-I545 using XDA Premium 4 mobile app
decaturbob said:
yep..definitely the mistake
this thread and links would have helped you before you jumped off the cliff
http://forum.xda-developers.com/showthread.php?t=2606501
Yep, from the thread you suggest.......... "The number one reason people brick their Verizon Galaxy S4 phones is due to attempts to flash recovery using Goo Manager, dd, and other tools without understanding when those will or won't work. The Verizon S4 is very locked down, and will reject such attempts in most cases."
Sent from my GT-I9070 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
NC5 is in this thread
http://forum.xda-developers.com/showthread.php?t=2735172
Sent from my SCH-I545 using Tapatalk
Slowbalt said:
Looks like you are trying to Odin to an image that was lower firmware than what your phone was on. You might want to try flashing the full wipe nc5 image that has been posted. I can't link to it now as I'm on my phone but if you Google Odin full wipe Verizon nc5 it should bring you to the proper xda thread to get the file.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So I followed what you said and ended up using this guide. http://forum.xda-developers.com/showthread.php?t=2735172
I did the full wipe version, and it was successful, however I still cannot boot. It will give me the samsung icon with the unlocked padlock, and then just go black, I still can boot into ODIN mode but not into recovery. Any idea what's going on?
jeffysonp said:
So I followed what you said and ended up using this guide. http://forum.xda-developers.com/showthread.php?t=2735172
I did the full wipe version, and it was successful, however I still cannot boot. It will give me the samsung icon with the unlocked padlock, and then just go black, I still can boot into ODIN mode but not into recovery. Any idea what's going on?
Click to expand...
Click to collapse
Try booting into stock recovery and do a Factory Data Reset and wipe cache then reboot.
Sent from my SCH-I545 using Tapatalk
Also once you're back to stock run Tri Angle Away to get rid of that annoying CUSTOM screen at boot lol can't stand that thing and on my phone it can make getting into CWM a pain as well.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Try booting into stock recovery and do a Factory Data Reset and wipe cache then reboot.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I can't seem to get into stock recovery either. I tried re-flashing and I still get the same results, when I try to boot into recovery I get the Samsung logo with the unlocked padlock, and then it just shuts down. :/

Categories

Resources