Related
After flashing codis rom from mikrom after aroma installer was done, it jumped to recovery and asked me to fix su after i press yes it just started rebooting on and off trying to reboot back to recovery but it wont stay in recover, it goes back off and on and it keeps doing the same thing and i cant get it to stop. I can manually go into bootloader then fastboot and power down from there but when i try to go back to recovery through bootloader so i can try fixing it just doesnt want to stay in cwm recovery. Hoping anybody can help or guide me in the right direction to fix it, maybe using adb or something, thanx
Sent from my SCH-I535 using Tapatalk 2
Before flashing ROM did, did you flash boot.IMG in fast boot?
Sent from my HTC6435LVW using xda app-developers app
Robert235 said:
Before flashing ROM did, did you flash boot.IMG in fast boot?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yes, i use the app flash image GUI...but after it starting with the issues i went to bootloader/fastboot n i flashed it again
Sent from my SCH-I535 using Tapatalk 2
I think ive have tried every possible way to flash used every usb port and still cannot get my phone to flash on odin. Does anyone have any suggestions.
what ive done so far:
Used Odin3Excutionv1.81 (flashes SCH-I45 MDK Stock Restore)
Failed
Used Odin3Excution v1.81( flashes SCH-I545 MDK Kernel)
Successful
Used Odin 3.07v
Flashed Modem
Flashed Recovery
Flashed Kernel
These had to be run through odin a couple times before it would flash or pass.
Then after I tried to flash Stock Restore and that fails.
Im all out of options have, and have put many hours into getting nowwhere please if someone has any suggestions I would love to think that this isnt a 700 dollar paper i have sitting here.
When booting up I get a message that says," Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.(Tried that also)
Which version of the firmware were you on prior?
SCH-I545 using Tapatalk 2
hexitnow said:
Which version of the firmware were you on prior?
SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
I had not taken the OTA. because I didnt want to lose root
Bump.
Sent from my DROID BIONIC using xda app-developers app
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
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. :/
Hey guys I'm looking for TWRP tar file or any other way to flash a recovery kernel without going through the playstore. I tried using TWRP from playstore and every time I boot into recovery it takes me to download mode. I can't seem to find the download file for twrp. The link on website shows no downloadable file.
Can anyone help me out with a link or post that allows me to download this? Thanks!
Sent from my SCH-I545 using XDA Free mobile app
Or do I need to use safestrap? I haven't tried that one yet.
I'm on VRUFNG6
Sent from my SCH-I545 using XDA Free mobile app
http://forum.xda-developers.com/showthread.php?t=2905848
Sent from my GT-I9505G using Xparent Skyblue Tapatalk 2
pwned3 said:
http://forum.xda-developers.com/showthread.php?t=2905848
Sent from my GT-I9505G using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Thanks for the link.
But I did this already, actually from the same page.
Thats how i rooted the device.
I need access to a custom recovery but I cant find the correct files to flash.
I tried TWRP and Goomanager from playstore, also Safestrap but none of these work.
I get boot looped into Download Mode.
deviouskind said:
Hey guys I'm looking for TWRP tar file or any other way to flash a recovery kernel without going through the playstore. I tried using TWRP from playstore and every time I boot into recovery it takes me to download mode. I can't seem to find the download file for twrp. The link on website shows no downloadable file.
Can anyone help me out with a link or post that allows me to download this? Thanks!
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
If you can't boot the phone and are stuck in download mode, you have soft bricked your phone. This happened because goomanager and TWRP are only compatible with the mdk bootloader. I'm not sure if there is an NG6 Odin tar available yet, but I'm pretty sure that's your only hope.
Safe strap is your only option at the moment. Which version did you try?
Sent from my GT-I9505G using Xparent Skyblue Tapatalk 2
Version is Safestrap-JFLTEVZW-3.71
When installed it says ...
State: Not installed
And the reboot to recovery is greyed out.
Any other suggestions or thoughts?
I just got this phone so I guess the new versions are different and more secure than the old s4's
Sent from my SCH-I545 using XDA Free mobile app
deviouskind said:
Version is Safestrap-JFLTEVZW-3.71
When installed it says ...
State: Not installed
And the reboot to recovery is greyed out.
Any other suggestions or thoughts?
I just got this phone so I guess the new versions are different and more secure than the old s4's
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
You need busybox from the play store also. After you download the app go into it and "install busy box". Get selinux mode changer also and set it to "permissive".
I have supersu, busy box and selinux installed. Earlier I didn't have selinux installed but when I did and set to permissive it didn't work still.
Sent from my SCH-I545 using XDA Free mobile app
deviouskind said:
I have supersu, busy box and selinux installed. Earlier I didn't have selinux installed but when I did and set to permissive it didn't work still.
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
I only just noticed you said you were on NG6. Getting Safestrap to work with the update seems to be one of the issues right now. This thread http://forum.xda-developers.com/showthread.php?t=2905885 has some info that you may find useful and is probably where you should be asking your questions as the guy who made the OP is working on solving your very problem.
I've been looking around for a resolution to this myself but have yet to find one. I'm experiencing all of the same issues on newly rooted with NG6 Hopefully something gets figured out soon because my recovery menu also seems to be inaccessible after flashing with custom recovery using Rom Manager and TWRP Manager...also on a new phone, successfully rooted, with supersu, busybox pro and selinex installed. I'm glad my phone still works for the time being tho, and I'm sure I newbed at some point in the process lol. Fingers x'ed for a quick fix!
Thanks for that man. Let me know if you hear anything on this or if you figured it out. I will play around too.
Sent from my SCH-I545 using XDA Free mobile app
Thank you for the reply and link. Appreciate it.
Sent from my SCH-I545 using XDA Free mobile app
I just ended up going back to NC5 using this guide for FULL WIPE http://forum.xda-developers.com/showthread.php?t=2735172...couldn't handle the reboots. Phone runs like a champ now+I got safestrap working properly.
If you wanted to keep the update, I know what you were doing wrong. Sorry for being late BTW. I saw that you couldn't get SafeStrap 3.71 to install. The latest working version for nc5 and ng6 is safestrap 3.75.