Related
Let me give some info on my situation:
The phone has unlocked boot loader
I got a replacement phone and wanted to odin back to stock to send back my original phone.
I used Odin to flash back to stock but the phone will not boot and I cannot get into recovery.
I am able to use Odin with success every time. I have followed instruction on how to return to stock and everything goes perfectly until I try to reboot or go into recovery. I just get the Samsung splash screen and it blinks every couple of seconds.
Any ideas?
so you pulled battery, reinsert, three finger combo(vol up/home/power) until you see recovery booting and it wont boot into recovery?
droidstyle said:
so you pulled battery, reinsert, three finger combo(vol up/home/power) until you see recovery booting and it wont boot into recovery?
Click to expand...
Click to collapse
correct, I am able to get into download mode but not into recovery and I have tried everything. I am not a noob but am totally lost here.
I can use Odin without any issue.
droidstyle said:
so you pulled battery, reinsert, three finger combo(vol up/home/power) until you see recovery booting and it wont boot into recovery?
Click to expand...
Click to collapse
I have been using your instructions to go back to stock using odin from any rom. Do I need to flash the PIT with any stock odin file?
I have successful used the route66, Revision3 and Imuts files. all flash in Odin gave me the "SUCCESS" but then I cannot boot into recovery or start the phone.
Could it be because I had an unlocked bootloader? Is there a way to reinstall just a bootloader and/or recovery.
mzimand said:
I have been using your instructions to go back to stock using odin from any rom. Do I need to flash the PIT with any stock odin file?
I have successful used the route66, Revision3 and Imuts files. all flash in Odin gave me the "SUCCESS" but then I cannot boot into recovery or start the phone.
Could it be because I had an unlocked bootloader? Is there a way to reinstall just a bootloader and/or recovery.
Click to expand...
Click to collapse
If you're returning it use the OTA jb image (full wipes and locks boot loader) and the pit file.
Sent from the dark on a Note 2
kintwofan said:
If you're returning it use the OTA jb image (full wipes and locks boot loader) and the pit file.
Sent from the dark on a Note 2
Click to expand...
Click to collapse
I just tried this and got the same results. I got the "PASS" in Odin after flashing the PIT and the stock JB Image. I am still stuck at a slow blinking Samsung screen.
I am open to any ideas
wizeguydesigns had the same problem...you didnt flash the jedi rom prior did u?
droidstyle said:
wizeguydesigns had the same problem...you didnt flash the jedi rom prior did u?
Click to expand...
Click to collapse
Yes, this was my problem exactly!! I know you weren't saying this, but it wasn't the Jedi ROM that did it just to clear that up. It was a ROM that I was beta testing that hasn't been released yet. I was on Jedi ROM prior to flashing the beta test ROM which I think is what you meant.
OP, did you happen to be testing a ROM and this happened? I won't name it but at least tell me that much.
Sent from my SCH-I605 using xda premium
WizeGuyDezignz said:
Yes, this was my problem exactly!! I know you weren't saying this, but it wasn't the Jedi ROM that did it just to clear that up. It was a ROM that I was beta testing that hasn't been released yet. I was on Jedi ROM prior to flashing the beta test ROM which I think is what you meant.
OP, did you happen to be testing a ROM and this happened? I won't name it but at least tell me that much.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
ahh thanks for clearing that up.
WizeGuyDezignz said:
Yes, this was my problem exactly!! I know you weren't saying this, but it wasn't the Jedi ROM that did it just to clear that up. It was a ROM that I was beta testing that hasn't been released yet. I was on Jedi ROM prior to flashing the beta test ROM which I think is what you meant.
OP, did you happen to be testing a ROM and this happened? I won't name it but at least tell me that much.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Yes I was flashing a ROM. It was a sprint rom that i was trying to patch. It was whompasrus. Where you able to fix the issue?
Sent from my SCH-I605 using Tapatalk 2
mzimand said:
Yes I was flashing a ROM. It was a sprint rom that i was trying to patch. It was whompasrus. Where you able to fix the issue?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Yep, that was the ROM that I was testing as well. I know you won't want to hear this, but I wasn't able to fix the issue.
Sent from my SCH-I605 using xda premium
WizeGuyDezignz said:
Yep, that was the ROM that I was testing as well. I know you won't want to hear this, but I wasn't able to fix the issue.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
I had a feeling that is was bricked as I have tried everything I could to fix it. It is not that big of a deal because the screen was shattered on it last week and I paid the insurance for a replacement and was sending it back anyways.
So i was going to flash a rom I made a back up, I hit fixed permissions. and now all I have is Samsung Galaxy S4 logo and is just stuck there. I can get into twrp and have tried wiping and starting from a clean slate and restoring the back up but still get the galaxy logo? any suggestions ?
**have just tried to use odin and fails also*** How do I get back to stock please? Anyone please help
bump
Imprezive13 said:
bump
Click to expand...
Click to collapse
Have you tried flashing a stock ROM from TWRP?
-------edit----------
I just remembered. This used to happen on the Note 2 at times. If you're booting and get the Samsung splash screen, try going to TWRP and doing a Factory Reset a couple times. No idea if it will work, but with the Note that would usually clear whatever block existed and allow the ROM to boot past the splash screen. Good luck.
eakeller said:
Have you tried flashing a stock ROM from TWRP?
Click to expand...
Click to collapse
what do you mean ? first time ever having a problem with this. are you talking about the SCH-I545_MDK_562219_Stock_Restore.tar file ?
Imprezive13 said:
what do you mean ? first time ever having a problem with this. are you talking about the SCH-I545_MDK_562219_Stock_Restore.tar file ?
Click to expand...
Click to collapse
If it exists, it would basically be that ROM stuck into a .zip file which could be flashed from TWRP. I'm not sure it exists, was just browsing the Dev thread for you to see if anyone posted it. There is a version here http://forum.xda-developers.com/showthread.php?t=2292707 , but I'm not familiar with Loki enough to say whether or not you have it.
eakeller said:
If it exists, it would basically be that ROM stuck into a .zip file which could be flashed from TWRP. I'm not sure it exists, was just browsing the Dev thread for you to see if anyone posted it. There is a version here http://forum.xda-developers.com/showthread.php?t=2292707 , but I'm not familiar with Loki enough to say whether or not you have it.
Click to expand...
Click to collapse
Well for right now im trying to just get the phone back to its working condition. trying to using odin, but fails every time. and not sure what i should do.
Imprezive13 said:
Well for right now im trying to just get the phone back to its working condition. trying to using odin, but fails every time. and not sure what i should do.
Click to expand...
Click to collapse
If Odin isn't working for you, a solution might be had via TWRP since you can still get into the recovery. If you flash your ROM or try your backup, does the install complete or does it crash? Have you wiped cache, dalvik, system, and data before the flash?
-edit-
Sorry, just saw your OP where you said you wiped and tried. If I were you my next step would be trying a different ROM just to see if you can get something booting.
eakeller said:
If Odin isn't working for you, a solution might be had via TWRP since you can still get into the recovery. If you flash your ROM or try your backup, does the install complete or does it crash? Have you wiped cache, dalvik, system, and data before the flash?
Click to expand...
Click to collapse
Trying again. First wiping wiped cache, dalvik, system, and data , then restoring back up. I've tried this multiple times before hopefully it works this time. But generally when i hit reboot system afterward it just hangs at the Samsung Galaxy IV boot screen and does nothing.
Imprezive13 said:
Trying again. First wiping wiped cache, dalvik, system, and data , then restoring back up. I've tried this multiple times before hopefully it works this time. But generally when i hit reboot system afterward it just hangs at the Samsung Galaxy IV boot screen and does nothing.
Click to expand...
Click to collapse
After your backup restores, try using TWRP to do a Factory Reset a couple times before rebooting. Also wipe cache/dalvik again before the boot.
Failed again stuck at Samsung Galaxy S4 boot screen
eakeller said:
After your backup restores, try using TWRP to do a Factory Reset a couple times before rebooting. Also wipe cache/dalvik again before the boot.
Click to expand...
Click to collapse
Stuck again
Imprezive13 said:
Stuck again
Click to expand...
Click to collapse
Sorry to hear that, man. I'm out of ideas and hopefully someone with more know-how can give the solution.
Sent from my SCH-I545 using Tapatalk 2
I would try downloading a ROM to your computer then copying it to a microsd, put the card in your phone and then try to flash the fresh ROM from TWRP. (After wiping everything again.)
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
I would try downloading a ROM to your computer then copying it to a microsd, put the card in your phone and then try to flash the fresh ROM from TWRP. (After wiping everything again.)
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Ive been looking for the stock rom files no luck at the moment.
Maybe this one?
http://forum.xda-developers.com/showthread.php?t=2292707
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
Maybe this one?
http://forum.xda-developers.com/showthread.php?t=2292707
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
downloading now wish me luck
Good luck to you.
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
Good luck to you.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
got it working. on a deoxed rom. but is there a way to go completely back to stock using odin ?
http://forum.xda-developers.com/showthread.php?t=2289325
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
http://forum.xda-developers.com/showthread.php?t=2289325
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Well went to restart the phone and now its stuck on a Samsung logo with a unlocked icon thats says custom underneath it and just sits there.
I accidentally accepted the OTA update (because it f*cking pops up every 5 minutes).
The phone rebooted into recovery to apply the update, but I pulled the battery.
I am not rooted and running stock. I just want to keep the old rootable/unlockable firmware in place.
How can I stop this update from applying? Every time I restart the phone it jumps into recovery to apply this update. Is there a way to stop this or am I doomed?
I can get into odin mode, but when I try to load recovery it tries to apply the update.
I dont know if it will work but Boot to odin decline it and see if it will boot normally. If it works youll have to root and then freeze or rename sdm.apk to stop it. The ota data is located in data/fota if you want to delete it. If none of that works you can always try reflashing the mdk image.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
I dont know if it will work but Boot to odin decline it and see if it will boot normally. If it works youll have to root and then freeze or rename sdm.apk to stop it. The ota data is located in data/fota if you want to delete it. If none of that works you can always try reflashing the mdk image.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
bunklung said:
I accidentally accepted the OTA update (because it f*cking pops up every 5 minutes).
The phone rebooted into recovery to apply the update, but I pulled the battery.
I am not rooted and running stock. I just want to keep the old rootable/unlockable firmware in place.
How can I stop this update from applying? Every time I restart the phone it jumps into recovery to apply this update. Is there a way to stop this or am I doomed?
I can get into odin mode, but when I try to load recovery it tries to apply the update.
Click to expand...
Click to collapse
Wait if it was me, I would get into odin and flash the stock mdk tar image.,,,
Surge1223 said:
Wait if it was me, I would get into odin and flash the stock mdk tar image.,,,
Click to expand...
Click to collapse
if he can get the phone to boot normally flashing mdk would be unnecessary. Could end up being the only way though. Wish I could say ive been in this situation to post a definitive answer but I havent.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
if he can get the phone to boot normally flashing mdk would be unnecessary. Could end up being the only way though. Wish I could say ive been in this situation to post a definitive answer but I havent.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
He isnt rooted though, so would have to root right away. If he rebooted before the update started deleting/patching files and changining permissions then it might be ok. I just would rather have no chance of the update patching the recovery or the kernel. The odin image would format the partitions and would delete the update it shouldny brick the phone because the bootloader and firmware arent patched until literally the screen shows 95.39% of the update is complete.
set_progress(0.953849);
ui_print("Patching hidden files...");
ui_print("Patching NON-HLOS modem image...");
apply_patch("EMMC:/dev/block/platform/msm_sdcc.1/by-name
Etc..etc
And rooting is a long process? Hes going to have to root regardless if he wants to cancel it out. No reason to take an extra step to do the same thing.
Sent from my SCH-I545 using Tapatalk 2
I agree, more often than not your suggestion would be sufficient. I guess its just personal preference.
Sent from my SCH-I545 using XDA Premium 4 mobile app
bunklung said:
I accidentally accepted the OTA update (because it f*cking pops up every 5 minutes).
The phone rebooted into recovery to apply the update, but I pulled the battery.
I am not rooted and running stock. I just want to keep the old rootable/unlockable firmware in place.
How can I stop this update from applying? Every time I restart the phone it jumps into recovery to apply this update. Is there a way to stop this or am I doomed?
I can get into odin mode, but when I try to load recovery it tries to apply the update.
Click to expand...
Click to collapse
Boot and pull the battery at the same place you did before, after about 9 or 10 times the phone will tell you update failed. Then root immediately. Do not pass go do not collect $200
Sent from my BNTV250A using xda app-developers app
Surge1223 said:
I agree, more often than not your suggestion would be sufficient. I guess its just personal preference.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I hear ya there.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
I dont know if it will work but Boot to odin decline it and see if it will boot normally. If it works youll have to root and then freeze or rename sdm.apk to stop it. The ota data is located in data/fota if you want to delete it. If none of that works you can always try reflashing the mdk image.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
All,
Thanks for the responses. Booting into ODIN did not stop the recovery install OTA loop.
I used the nowipe Odin image and all is well:
http://forum.xda-developers.com/showthread.php?t=2301259
Still on MDK!
I took the extra steps and rooted the phone and renamed/deleted:
/data/fota contents
FWUpgrade.apk
FWUpgrade.odex
SDM.apk
SDM.odex
LocalFOTA.apk
I installed a custom recovery and then unrooted the phone. Thanks everyone. I hope this helps someone in a similar situation.
bunklung said:
All,
Thanks for the responses. Booting into ODIN did not stop the recovery install OTA loop.
I used the nowipe Odin image and all is well:
http://forum.xda-developers.com/showthread.php?t=2301259
Still on MDK!
I took the extra steps and rooted the phone and renamed/deleted:
/data/fota contents
FWUpgrade.apk
FWUpgrade.odex
SDM.apk
SDM.odex
LocalFOTA.apk
I installed a custom recovery and then unrooted the phone. Thanks everyone. I hope this helps someone in a similar situation.
Click to expand...
Click to collapse
Wasnt for sure if the odin decline would work but if it would have it would of saved you a lil bit of time. Glad you got her up and running.
Sent from my SCH-I545 using Tapatalk 2
bunklung said:
All,
Thanks for the responses. Booting into ODIN did not stop the recovery install OTA loop.
I used the nowipe Odin image and all is well:
http://forum.xda-developers.com/showthread.php?t=2301259
Still on MDK!
I took the extra steps and rooted the phone and renamed/deleted:
/data/fota contents
FWUpgrade.apk
FWUpgrade.odex
SDM.apk
SDM.odex
LocalFOTA.apk
I installed a custom recovery and then unrooted the phone. Thanks everyone. I hope this helps someone in a similar situation.
Click to expand...
Click to collapse
Im sorry for the several month bump, but can anyone confirm this will work for stock ME7 with the new OTA update. I just put myself into the same situation as the OP.
Party_Grunt said:
Im sorry for the several month bump, but can anyone confirm this will work for stock ME7 with the new OTA update. I just put myself into the same situation as the OP.
Click to expand...
Click to collapse
Should work. Just boot into odin mode and either flash the ME7 factory restore image or the no-wipe ME7 image. But if you really wanted to impress the ladies you could flash the sch1545 pit file. But if you don't know what the pit file does then use one of the first two suggestions.
Surge1223 said:
Should work. Just boot into odin mode and either flash the ME7 factory restore image or the no-wipe ME7 image. But if you really wanted to impress the ladies you could flash the sch1545 pit file. But if you don't know what the pit file does then use one of the first two suggestions.
Click to expand...
Click to collapse
Thanks, it did work. Unfortunately the last time this happened I was on vacation with no computer available so I was forced to take the OTA update or have no phone for two weeks. I had only rooted the week before and had not gotten around to putting in a custom recovery and bootloader, so I was SOL. Didn't even know root had been found for ME7 until last week. My timing seems to suck on this.
Now time to root and delete the upgrade files.
and tried to install open recovery script using goomanager. It put me into the download mode. I was finally able to get out of it. Do I need to do anything to clean up anything or just wait till the me7 is able to install a custom recovery?
Today I was using nav a bit and my device turned off on me several times. I don't know what's causing that to happen. Don't know if it has something to do with root or not. Hasn't happened before I rooted.
If your device is in the window it could be overheating. You could try uninstalling any updates/data and re update if that doesnt work then I would flash the me7 image through odin and re root and see if that solves the problem. Im on an me7 based rom and dont have that problem.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
You could try uninstalling any updates/data and re update
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
It was in my hand...
How do I do that? I can't use Odin because I have a Mac.
Hey Hexitnow...Didn't want to hijack the other thread but you said to reflash. Do I just do that by running the script in the terminal emulator on the phone again like I did the first time?
That im not sure about i dont think there is an odin version for mac. I could be wrong tho because ive never really looked either. There is another program called heimdall (google it and you can find it, instructions are in the readme) and you should be able to flash using that. But I would try uninstalling any updates/data before hand and see if that solves it.
Edit:
Rerun the script? Sorry im a little lost there.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
But I would try uninstalling any updates/data before hand and see if that solves it.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
How do I do that? ...and in the other thread you said I should reflash so I would have a stock recovery.
This is the method I used.... http://forum.xda-developers.com/showthread.php?t=2380325
I gotcha. You can do it through application manager. After you get me7 reflashed then yeah you just do the same process over to get root back.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
I gotcha. You can do it through application manager. After you get me7 reflashed then yeah you just do the same process over to get root back.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
I'm bit of a noob again. I had Android for several years but I've had an iphone for the last 4 or 5 years and I've forgotten everything. Could you give me a step by step on what I should do? And does reflash mean going back to unrooted?
If you go into settings, more, application manager then scroll to the app in question youll see the options. When i say reflash I mean flashing the me7 stock image. After flashing it it puts your phone back to how it was when you first pulled it out of the box.
Sent from my SCH-I545 using Tapatalk 2
Thanks for explaining!
CatsTide said:
Thanks for explaining!
Click to expand...
Click to collapse
You bet.
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. :/