A friend of mine (really) has an S4 that goes to a black screen after the Verizon splash screen, nothing else happens other than the LED pulses blue.
When I go into recovery mode, the little green dude says 'Initializing System Update' for a fraction of a second, the he falls over dead with a red exclamation triangle over his open chest and it quickly says 'No command', 'Error' and finally 'No command' again.
I don't want to try a factory reset, as all of his photos are in phone memory rather than on an SD card. He's already gotten a new phone from Verizon, but is trying not to lose his photos.
Kies won't see the phone either, so I'm at a loss of what to try. It will go into ODIN mode, don't know if that provides me any options. The phone is unmodded, stock factory image.
You can try to Odin a no wipe image to salvage the photos but it sounds like only the full wipe will take.
Do you know what he was trying to do that soft bricked the phone?
Sent from my HTC6525LVW using XDA Premium 4 mobile app
joshm.1219 said:
You can try to Odin a no wipe image to salvage the photos but it sounds like only the full wipe will take.
Do you know what he was trying to do that soft bricked the phone?
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Josh,
Looks like a no-go. Downloaded Odin 3.07, along with a no-wipe image tar file (VRUAMDK). Open Odin, loaded tar file to PDA, it successfully checked the file as valid. Turned on phone in Odin mode, pressed volume up to go to Downloading screen on phone. Plugged in USB cable to phone, no COM ID shows up in Odin. Samsung USB driver 1.5.33.0 is installed, as part of my Kies install, so that's not it. Guess I'm screwed....
mikemcm1956 said:
Josh,
Looks like a no-go. Downloaded Odin 3.07, along with a no-wipe image tar file (VRUAMDK). Open Odin, loaded tar file to PDA, it successfully checked the file as valid. Turned on phone in Odin mode, pressed volume up to go to Downloading screen on phone. Plugged in USB cable to phone, no COM ID shows up in Odin. Samsung USB driver 1.5.33.0 is installed, as part of my Kies install, so that's not it. Guess I'm screwed....
Click to expand...
Click to collapse
Most likely you're not screwed. What I've done in the past is uninstall Kies and the Samsung drivers from your commuter. Then reboot. Then go to K1mu's Saferoot thread and grab the drivers he has in the op.
Try that and maybe if you have to try another USB cable and different Port on your computer. You should be able to get Odin to see your phone.
Sent from my SCH-I545 using Tapatalk
mikemcm1956 said:
Josh,
Looks like a no-go. Downloaded Odin 3.07, along with a no-wipe image tar file (VRUAMDK). Open Odin, loaded tar file to PDA, it successfully checked the file as valid. Turned on phone in Odin mode, pressed volume up to go to Downloading screen on phone. Plugged in USB cable to phone, no COM ID shows up in Odin. Samsung USB driver 1.5.33.0 is installed, as part of my Kies install, so that's not it. Guess I'm screwed....
Click to expand...
Click to collapse
Try what Mistertac said. He basically covered everything you can do to get Odin to try and recognize the phone. Try another computer as well. You could also try Heimdall, similar program to Odin. Also, if you can get the phone connected, make sure you figure out what build he was on, probably wasn't MDK.
Yea it most likely wasn't MDK but you never know. Worse that can happen is it just won't work and if that's the case just grab the MK2 tar. Sometimes these new computers are just a pain with the drivers from what I've seen and dealt with. I miss Windows 2000/XP Pro lol
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Yea it most likely wasn't MDK but you never know. Worse that can happen is it just won't work and if that's the case just grab the MK2 tar. Sometimes these new computers are just a pain with the drivers from what I've seen and dealt with. I miss Windows 2000/XP Pro lol
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Josh & Mistertac,
Thanks for the help, it's been a while since I had to do this on my own phones. The first issue with connecting has been solved, dumbass me was using a Samsung dock USB cable that was charge only with no data lines. Swapped out the cable and Odin sees it fine. Tried to run the MDK tar file and got a big fat FAIL. Now the phone immediately goes to Odin on powerup and displays the 'encountered an issue' screen. I've found two more no-wipe images here, VRUAME7 and VRUDMI1, but don't see the MK2 tar in this thread: http://forum.xda-developers.com/showthread.php?t=2301259
So I'm downloading the ME7 and MI1 files now to give them a shot.
mikemcm1956 said:
Josh & Mistertac,
Thanks for the help, it's been a while since I had to do this on my own phones. The first issue with connecting has been solved, dumbass me was using a Samsung dock USB cable that was charge only with no data lines. Swapped out the cable and Odin sees it fine. Tried to run the MDK tar file and got a big fat FAIL. Now the phone immediately goes to Odin on powerup and displays the 'encountered an issue' screen. I've found two more no-wipe images here, VRUAME7 and VRUDMI1, but don't see the MK2 tar in this thread: http://forum.xda-developers.com/showthread.php?t=2301259
So I'm downloading the ME7 and MI1 files now to give them a shot.
Click to expand...
Click to collapse
Check here too
http://forum.xda-developers.com/showthread.php?t=2578209
You should be good with that thread.
Good luck man
Edit
I'd say cut to the chase and just use the mk2 file
Sent from my SCH-I545 using Tapatalk
mikemcm1956 said:
Josh & Mistertac,
Thanks for the help, it's been a while since I had to do this on my own phones. The first issue with connecting has been solved, dumbass me was using a Samsung dock USB cable that was charge only with no data lines. Swapped out the cable and Odin sees it fine. Tried to run the MDK tar file and got a big fat FAIL. Now the phone immediately goes to Odin on powerup and displays the 'encountered an issue' screen. I've found two more no-wipe images here, VRUAME7 and VRUDMI1, but don't see the MK2 tar in this thread: http://forum.xda-developers.com/showthread.php?t=2301259
So I'm downloading the ME7 and MI1 files now to give them a shot.
Click to expand...
Click to collapse
Just found the no-wipe MK2, will try that first.
mikemcm1956 said:
Just found the no-wipe MK2, will try that first.
Click to expand...
Click to collapse
MK2 no-wipe restore went perfectly, was able to recover all photos and other data. Moved everything off to the SD card and will do a full factory reset before it gets sent back to Verizon. Thanks to both of you for the help. I haven't rooted my last two phones, may have to fall back into this game again....
Related
Alright guys as my title states I pulled a "noob move" and it looks like I've soft bricked my phone (It won't boot past the verizon splash screen). I've done a little research and I'm pretty familiar with Odin and how it works. Seems to be the same concept as jungle flasher and I've modded a few 360's in my time. I've tried, to no avail, to flash my phone back with the stock image numerous times and I figured it was time to consult the experts. What I've done so far: Downloaded the factory stock restore TAR from Rwilco12's site and put that in the PDA file browser of Odin. My phone shows up in Odin when connected in download mode with a light blue com:4 box. I read sometimes this is supposed to be yellow? Other versions of Odin it is yellow. This instance was attempted in 3.07. 1.85 it shows up as yellow. Regardless of either version, they both fail after the "aboot" step. I've tried two computers and have failed miserably all morning. Any help or advice would be much appreciated.
-Be easy on me, it's my first time.
-HerdOn
HerdOn said:
Alright guys as my title states I pulled a "noob move" and it looks like I've soft bricked my phone (It won't boot past the verizon splash screen). I've done a little research and I'm pretty familiar with Odin and how it works. Seems to be the same concept as jungle flasher and I've modded a few 360's in my time. I've tried, to no avail, to flash my phone back with the stock image numerous times and I figured it was time to consult the experts. What I've done so far: Downloaded the factory stock restore TAR from Rwilco12's site and put that in the PDA file browser of Odin. My phone shows up in Odin when connected in download mode with a light blue com:4 box. I read sometimes this is supposed to be yellow? Other versions of Odin it is yellow. This instance was attempted in 3.07. 1.85 it shows up as yellow. Regardless of either version, they both fail after the "aboot" step. I've tried two computers and have failed miserably all morning. Any help or advice would be much appreciated.
-Be easy on me, it's my first time.
-HerdOn
Click to expand...
Click to collapse
Have you tried a different USB cable and/or running odin as an administrator?
BladeRunner said:
Have you tried a different USB cable and/or running odin as an administrator?
Click to expand...
Click to collapse
Yes, I've used the factory samsung and another cable while running as an administrator. Thanks for the thought though!
HerdOn said:
Yes, I've used the factory samsung and another cable while running as an administrator. Thanks for the thought though!
Click to expand...
Click to collapse
which Verizon release are you on VRUAMDK or VRUAME7?
BladeRunner said:
which Verizon release are you on VRUAMDK or ?
Click to expand...
Click to collapse
VRUAME7 is the most recent with the latest OTA update correct? If so that's the one I was on. Now I did root it successfully initially, it got stuck this way after installing SuperSU... I guess I should have said that initially. My apologies.
HerdOn said:
VRUAME7 is the most recent with the latest OTA update correct? If so that's the one I was on. Now I did root it successfully initially, it got stuck this way after installing SuperSU... I guess I should have said that initially. My apologies.
Click to expand...
Click to collapse
ME7 is the current OTA, yes. Are you using the correct .TAR file from here? http://www.androidfilehost.com/?fid=23032113221600748? Also did you try doing a data wipe/factory reset in stock android recovery?
BladeRunner said:
ME7 is the current OTA, yes. Are you using the correct .TAR file from here? Also did you try doing a data wipe/factory reset in stock android recovery?
Click to expand...
Click to collapse
The link you sent was broken, I'm using the rwilco12 factory image. It wont let me post a link because I don't have enough posts.
I have tried doing the data wipe/factory reset but it kept saying error. and now it says Firmware upgrade encountered an issue please select recovery mode in kies and try again. That's when going to the volume up "recovery" mode. Volume down, "download" mode still works fine.
http://www.androidfilehost.com/?fid=23032113221600748
The link BladeRunner posted had an extra question mark. Try that one.
Sent from my SCH-I545 using xda app-developers app
HerdOn said:
The link you sent was broken, I'm using the rwilco12 factory image. It wont let me post a link because I don't have enough posts.
I have tried doing the data wipe/factory reset but it kept saying error. and now it says Firmware upgrade encountered an issue please select recovery mode in kies and try again. That's when going to the volume up "recovery" mode. Volume down, "download" mode still works fine.
Click to expand...
Click to collapse
sorry, here is the link to the Odin files thread: http://forum.xda-developers.com/showthread.php?t=2301259 Download the VRAUME7 factory image. I'm not sure but I think you may have the MDK image from RWILCO and there's no going back to that once you've updated to ME7.
---------- Post added at 02:26 PM ---------- Previous post was at 02:25 PM ----------
Checkm8 said:
http://www.androidfilehost.com/?fid=23032113221600748
The link BladeRunner posted had an extra question mark. Try that one.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Thanks! Don't know where that extra "?" came from
Alright I'm downloading that version now. Its capping my connection so it should be done in 25 mins and we'll try again! Thanks for your help so far bladerunner. Seems like we're getting somewhere...
Bladerunner, you were right my friend! The image is finally going to the phone. After nearly pulling all of my hair out, we're making extreme progress!
Ten minutes later my phone is back to factory flawless condition. Thanks Bladerunner for all your help! It's very much appreciated..
HerdOn said:
Ten minutes later my phone is back to factory flawless condition. Thanks Bladerunner for all your help! It's very much appreciated..
Click to expand...
Click to collapse
Excellent! No problem
I did the OTA update from M1I to MJ7 and read somewhere that the M1I root method would work. It made my phone unbootable. Obviously the M1I file I have won't work now. I need the MJ7 odin file now or else my phone is a paperweight until then.
Someone else did this 2, you can't use this method because it FLASHES A ROOTED Ml1 Rom....... Odin file still has not been posted yet
Sent From My Hyperdriven S4
ebsk8er06 said:
Someone else did this 2, you can't use this method because it FLASHES A ROOTED Ml1 Rom....... Odin file still has not been posted yet
Sent From My Hyperdriven S4
Click to expand...
Click to collapse
Yeah I thought I read that it would still work. I'll just have to wait for the Odin file
I am in the same boat, my phone is unbootable and I am waiting for the MJ7 odin file or my replacement phone
villainous said:
I am in the same boat, my phone is unbootable and I am waiting for the MJ7 odin file or my replacement phone
Click to expand...
Click to collapse
thankfully i have an iphone i can use for now. surprisingly i went to boot up my phone just now and it went through almost the whole boot process. it's stuck on the verizon splash. last night it would just go straight into odin.
I am not so lucky as to have a backup phone
I should look for a cheap 4g phone to keep in a drawer for such occasions. Hopefully an MJ7 file is made available soon so I can recovery my files before my new phone arrives.
villainous said:
I am not so lucky as to have a backup phone
I should look for a cheap 4g phone to keep in a drawer for such occasions. Hopefully an MJ7 file is made available soon so I can recovery my files before my new phone arrives.
Click to expand...
Click to collapse
I'm sure it will. In a few days. I'm surprised the verizon repair tool doesn't have MJ7.... maybe that'll take a while too.
antisomnic said:
thankfully i have an iphone i can use for now. surprisingly i went to boot up my phone just now and it went through almost the whole boot process. it's stuck on the verizon splash. last night it would just go straight into odin.
Click to expand...
Click to collapse
You might be able to get it into recovery and manually use the update.zip.
It is reported that at least a few people have been able to get out of the state you are in my using a manual update.
tech_head said:
You might be able to get it into recovery and manually use the update.zip.
It is reported that at least a few people have been able to get out of the state you are in my using a manual update.
Click to expand...
Click to collapse
yeah i actually did that and have been using my s4 for a few days
open1your1eyes0 posted [ODIN][TAR] Complete Device Wipe/Repartition and Emergency Recovery for VRUEMJ7 Build in the dev forum.
This is an ODIN factory image similar to the one posted here but this is an emergency recovery image that will help you recover and restore your device from nearly ANY possible soft-brick by entirely wiping, refreshing, and repartitioning your device to out-of-box OEM firmware.
WARNING: Please use this with caution as this will wipe your ENTIRE device with no chance of restoring back old data afterwords!
How to Use
Download file from: http://www.androidfilehost.com/?fid=23203820527944861
Unzip file to your computer (desktop or some location)
Use ODIN v3.09 to flash in AP section once your device is connected
Click to expand...
Click to collapse
And joderme has a VRUEMJ7 no wipe ODIN image available in dev too.
--OctOS Powered VZW GS4 Dev Edition
antisomnic said:
yeah i actually did that and have been using my s4 for a few days
Click to expand...
Click to collapse
So I rooted and updated to MJ7 all went well. Then tried to install twrp not realizing it wont work. Now I'm stuck into download mode and yellow triangle. Is there not a way to odin back to stock since I have this update. Need help.
mickrg123 said:
So I rooted and updated to MJ7 all went well. Then tried to install twrp not realizing it wont work. Now I'm stuck into download mode and yellow triangle. Is there not a way to odin back to stock since I have this update. Need help.
Click to expand...
Click to collapse
Untested, but you can unzip the attached and flash it in ODIN - it's the stock MJ7 recovery. With a bit of luck that'll get you repaired.
If not, flash the no-wipe MJ7 ROM from the Android Development forum, but that'll probably cause you to lose root.
Bait-Fish said:
open1your1eyes0 posted [ODIN][TAR] Complete Device Wipe/Repartition and Emergency Recovery for VRUEMJ7 Build in the dev forum.
And joderme has a VRUEMJ7 no wipe ODIN image available in dev too.
--OctOS Powered VZW GS4 Dev Edition
Click to expand...
Click to collapse
wrong post
Awesome
You know... I don't post much if at all on xda. Mostly im an intel junkie but I have to say after bricking my 24 hour old MJ7 s4 and fully recovering it using this post you guys are ****ing AWESOME!
FYI The exact steps I took were as follows using windows 8.1 pro x64
downloaded Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
downloaded Odin3 v3.07
downloaded ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
Install Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0 drivers
Ran odin as administrator, left defaults checked and chose PDA ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
(Windows hangs when trying to first browse the file, WAIT)
plugged phone in and got instant com green and hit start. Waited 20 mins and it all went through successfully.
USERS NOTE:
The first computer I tried just absolutely would not flash this phone. Drivers where correct etc it just seemed like it dropped connection. Tried 3 separate usb ports one even off a powered hub and all failed on the system flash. Changed computers and followed the same setup and went first try. If it fails try and try again. Changing different ports, computers, and or drivers helps if you get failure messages.
Thanks to all of you!
SmOoThEm said:
You know... I don't post much if at all on xda. Mostly im an intel junkie but I have to say after bricking my 24 hour old MJ7 s4 and fully recovering it using this post you guys are ****ing AWESOME!
FYI The exact steps I took were as follows using windows 8.1 pro x64
downloaded Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
downloaded Odin3 v3.07
downloaded ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
Install Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0 drivers
Ran odin as administrator, left defaults checked and chose PDA ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
(Windows hangs when trying to first browse the file, WAIT)
plugged phone in and got instant com green and hit start. Waited 20 mins and it all went through successfully.
USERS NOTE:
The first computer I tried just absolutely would not flash this phone. Drivers where correct etc it just seemed like it dropped connection. Tried 3 separate usb ports one even off a powered hub and all failed on the system flash. Changed computers and followed the same setup and went first try. If it fails try and try again. Changing different ports, computers, and or drivers helps if you get failure messages.
Thanks to all of you!
Click to expand...
Click to collapse
Where can I grab ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low _ship_MULTI_CERT.tar.md5 ??
emtownsend said:
Where can I grab ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low _ship_MULTI_CERT.tar.md5 ??
Click to expand...
Click to collapse
http://www.androidfilehost.com/?fid=23203820527944861
Bait-Fish said:
open1your1eyes0 posted [ODIN][TAR] Complete Device Wipe/Repartition and Emergency Recovery for VRUEMJ7 Build in the dev forum.
And joderme has a VRUEMJ7 no wipe ODIN image available in dev too.
--OctOS Powered VZW GS4 Dev Edition
Click to expand...
Click to collapse
antisomnic said:
Yeah I thought I read that it would still work. I'll just have to wait for the Odin file
Click to expand...
Click to collapse
antisomnic said:
I did the OTA update from M1I to MJ7 and read somewhere that the M1I root method would work. It made my phone unbootable. Obviously the M1I file I have won't work now. I need the MJ7 odin file now or else my phone is a paperweight until then.
Click to expand...
Click to collapse
Just an FYI. Whenever you take an OTA from the Carrier it's written so you cannot revert back to an earlier build or a soft and possible hard brick can occur. This has been discussed numerous times in various forums. You were lucky this time.
I'll first list specs of my phone so it gives you some information you might need to help me solve my problem.
Verizon Galaxy S4
Android 4.3 MK2
Download mode works properly. Phone will not turn on unless it is plugged in via micro USB. Recovery mode boot loops.
(Recovery mode) I hold volume up and power after I plug in the micro usb to turn the phone on, and it shows the samsung logo, and the blue text pops up in the corner and says "Recovery Booting". After about 2 seconds of it showing that, it'll just black screen and repeat this boot loop of the samsung logo popping up and the blue text as if I have the recovery keys held down.
What led up to all of this is, my phone crashed and it turned off and tried to reboot, and crashed during the reboot. That's where I ran into the problem with the phone not turning on unless it was plugged in(battery is fully charged). At that time, if I plugged it in and didn't touch any keys, it would vibrate, and then a battery icon with a gray circle loading thing would pop up in a frozen picture. Then after about 8 seconds, it'd black screen and boot loop that. I couldn't get into Recovery at that time, but download worked fine. So then I googled a little and I flashed something onto my phone using Odin and Download mode. The file is supposed to make the default boot sequence go to recovery mode. This worked, but since Recovery mode is broken, it doesn't work entirely. After this, I didn't do anything for a day, and then I read some posts and tried flashing both a Wipe and No-wipe stock firmware MK2. Both of which did not work, since still, the phone was defaulting its boot to the broken recovery mode.
So as far as I know, the only way to do anything to the phone is through Odin and Download mode since nothing else works. I'm really hoping I'll be able to fix this, because I'd rather not pay $100 for a new phone :/
Basically what I'm asking for is what I should do next.. My only last thought is(If its possible) to wipe the phone using Odin, then putting the stock firmware back onto it. (The wipe of course getting rid of that stupid file that makes it go into recovery mode.
Baurblades43 said:
I'll first list specs of my phone so it gives you some information you might need to help me solve my problem.
Verizon Galaxy S4
Android 4.3 MK2
Download mode works properly. Phone will not turn on unless it is plugged in via micro USB. Recovery mode boot loops.
(Recovery mode) I hold volume up and power after I plug in the micro usb to turn the phone on, and it shows the samsung logo, and the blue text pops up in the corner and says "Recovery Booting". After about 2 seconds of it showing that, it'll just black screen and repeat this boot loop of the samsung logo popping up and the blue text as if I have the recovery keys held down.
What led up to all of this is, my phone crashed and it turned off and tried to reboot, and crashed during the reboot. That's where I ran into the problem with the phone not turning on unless it was plugged in(battery is fully charged). At that time, if I plugged it in and didn't touch any keys, it would vibrate, and then a battery icon with a gray circle loading thing would pop up in a frozen picture. Then after about 8 seconds, it'd black screen and boot loop that. I couldn't get into Recovery at that time, but download worked fine. So then I googled a little and I flashed something onto my phone using Odin and Download mode. The file is supposed to make the default boot sequence go to recovery mode. This worked, but since Recovery mode is broken, it doesn't work entirely. After this, I didn't do anything for a day, and then I read some posts and tried flashing both a Wipe and No-wipe stock firmware MK2. Both of which did not work, since still, the phone was defaulting its boot to the broken recovery mode.
So as far as I know, the only way to do anything to the phone is through Odin and Download mode since nothing else works. I'm really hoping I'll be able to fix this, because I'd rather not pay $100 for a new phone :/
Basically what I'm asking for is what I should do next.. My only last thought is(If its possible) to wipe the phone using Odin, then putting the stock firmware back onto it. (The wipe of course getting rid of that stupid file that makes it go into recovery mode.
Click to expand...
Click to collapse
are you an unrooted stock ROM??
I'm sure someone smarter then me will know exactly what is going on here but things I'd try in the mean time is another Odin file possibly. I believe Surge has said that if MK2 file doesn't work to try the MJ7 full wipe/Re-Partition one. At this point what you got to lose?
Sent from my SCH-I545 using Tapatalk
decaturbob said:
are you an unrooted stock ROM??
Click to expand...
Click to collapse
I am rooted with safestrap installed. Using the Hyperdrive ROM
Mistertac said:
I'm sure someone smarter then me will know exactly what is going on here but things I'd try in the mean time is another Odin file possibly. I believe Surge has said that if MK2 file doesn't work to try the MJ7 full wipe/Re-Partition one. At this point what you got to lose?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I believe I've already done this? I'm not sure. I'll have to check once I get home later in the day.
Baurblades43 said:
I believe I've already done this? I'm not sure. I'll have to check once I get home later in the day.
Click to expand...
Click to collapse
I would strongly suggest the Full Wipe method back to MK2. As long as you can boot into Download mode this is probably the best way to get a clean OS working again. From there you know the drill, Saferoot, SS, etc.
http://forum.xda-developers.com/showthread.php?t=2578209
Use sp flash tool and install another recovery. That will surely work. Just download sp flash tool and drivers for your device and install these files in your pc. After that download recovery.img and scatter file.txt for your device. First load the scattered file.txt using sp flash tool, now uncheck all the tick box except the recovery. Now click on recovery and select the recovery.img which you have downloaded. Now take out your phone's battery and connect it via usb cable. Make sure you have installed your phone's drivers. Click on download button on sp flash tool. If not works then remove the usb cable and reconnect again. You will see a green circle saying its done. Click on ok. And try to get into recovery again.
Sent from unnamed ROM using xda premium app
naveen6252 said:
Use sp flash tool and install another recovery. That will surely work. Just download sp flash tool and drivers for your device and install these files in your pc. After that download recovery.img and scatter file.txt for your device. First load the scattered file.txt using sp flash tool, now uncheck all the tick box except the recovery. Now click on recovery and select the recovery.img which you have downloaded. Now take out your phone's battery and connect it via usb cable. Make sure you have installed your phone's drivers. Click on download button on sp flash tool. If not works then remove the usb cable and reconnect again. You will see a green circle saying its done. Click on ok. And try to get into recovery again.
Sent from unnamed ROM using xda premium app
Click to expand...
Click to collapse
If he's using Safestrap, it most likely means he can't flash a recovery image. He could brick his phone.
Was just going to say that. I don't know much about that flash tool myself... Is it an alternative to Odin? From the little I read... You can flash an entire rom or just something in particular to repair a phone. Either way I don't think the OP should try that method. Stick with Odin.
Sent from my SCH-I545 using Tapatalk
riker147 said:
If he's using Safestrap, it most likely means he can't flash a recovery image. He could brick his phone.
Click to expand...
Click to collapse
+1, the only safe option is to flash a clean factory image via Odin. Otherwise say hello to your new doorstop if you mess with Recovery on MK2 locked bootloader
Flash new image >> 15-25 minutes
Root >> 2-3 minutes
SS >> 3-5 minutes
HD RLS15 (for example) >> 15 minutes
In about an hour or so phone is back up and running. No brainer..........
cbmggm said:
+1, the only safe option is to flash a clean factory image via Odin. Otherwise say hello to your new doorstop if you mess with Recovery on MK2 locked bootloader
Flash new image >> 15-25 minutes
Root >> 2-3 minutes
SS >> 3-5 minutes
HD RLS15 (for example) >> 15 minutes
In about an hour or so phone is back up and running. No brainer..........
Click to expand...
Click to collapse
The thing is.. I've tried flashing new images before, and all its doing is overwriting my old one, but the stupid factory thing I flashed makes the default path the broken recovery so I don't think this will work.
Baurblades43 said:
The thing is.. I've tried flashing new images before, and all its doing is overwriting my old one, but the stupid factory thing I flashed makes the default path the broken recovery so I don't think this will work.
Click to expand...
Click to collapse
Are you sure you flashed the full wipe tar file? I've successfully used this method numerous times.
http://www.androidfilehost.com/?fid=23269279319198294
Make sure you download to PC first then copy to your external SD card on your phone.
Sent from my SCH-I545 using xda app-developers app
cbmggm said:
Are you sure you flashed the full wipe tar file? I've successfully used this method numerous times.
http://www.androidfilehost.com/?fid=23269279319198294
Make sure you download to PC first then copy to your external SD card on your phone.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Umm.. Why would I want to put that on my external SD card? Wouldn't I want to just use it through ODIN?
Oops sorry I meant to leave the tar file on the PC.
Sent from my SCH-I545 using xda app-developers app
cbmggm said:
Oops sorry I meant to leave the tar file on the PC.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Haha alright. I'll go ahead and download this file and give it a go. Wish me luck.
cbmggm said:
Oops sorry I meant to leave the tar file on the PC.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Also, can you give me a quick guide on how to flash this through Odin? I just wanna make sure I'm not doing anything wrong.
Baurblades43 said:
Also, can you give me a quick guide on how to flash this through Odin? I just wanna make sure I'm not doing anything wrong.
Click to expand...
Click to collapse
Directions are in the thread: http://forum.xda-developers.com/showthread.php?t=2578209
Oishikatta said:
Directions are in the thread: http://forum.xda-developers.com/showthread.php?t=2578209
Click to expand...
Click to collapse
I followed the directions for everything as they were given and I got the same result I've gotten after flashing anything. Everything works fine, then the big blue "RESET" icon appears on Odin, then the phone reboots, I get samsung logo, and then the blue "recovery booting" text shows up.. and then the screen blacks out, and boot loops that same thing.
Baurblades43 said:
I followed the directions for everything as they were given and I got the same result I've gotten after flashing anything. Everything works fine, then the big blue "RESET" icon appears on Odin, then the phone reboots, I get samsung logo, and then the blue "recovery booting" text shows up.. and then the screen blacks out, and boot loops that same thing.
Click to expand...
Click to collapse
Make sure you're using the Full Wipe image (SCH-I545_VZW_1_20131212083410_mwx72ql56g_fac.zip), and have extracted it to a .tar.md5
Also download the JFLTE_USA_VZW_16G.pit (assuming you have the 16GB version of the S4).
Put the .tar.md5 in the AP section and the PIT file in the PIT section.
Leave the other checkboxes in Odin at their defaults.
Take a screenshot at this point, click Start, and then take another screenshot when it completes or gives an error.
Oishikatta said:
Make sure you're using the Full Wipe image (SCH-I545_VZW_1_20131212083410_mwx72ql56g_fac.zip), and have extracted it to a .tar.md5
Also download the JFLTE_USA_VZW_16G.pit (assuming you have the 16GB version of the S4).
Put the .tar.md5 in the AP section and the PIT file in the PIT section.
Leave the other checkboxes in Odin at their defaults.
Take a screenshot at this point, click Start, and then take another screenshot when it completes or gives an error.
Click to expand...
Click to collapse
Alright. I did a lot between your post and now. All of the information for everything I did is underneath each picture thats posted. So read them carefully.
http://imgur.com/3c4YZoz,CjiLmlY,Gfjx7Tc,TO1xSMV#0
EDIT: I looked up the battery icon problem and I found some interesting news. After all of the struggling with the darn phone, this is a common problem with this phone on 4.3. Its an overheating issue to the PBA(Motherboard I think). Thanks everyone for the help, I'm just gonna send it in and get a new phone.
My S4 was on MK2 rooted, but since the TowelRoot came out, I wanted to upgrade. So I unfroze all the system apps, used the Unroot option in SuperSU and rebooted....
BUT I FORGOT TO DISABLE/UNINSTALL XPOSED FRAMEWORK. FACEPALM!!!!
I've tried wiping cache/data, downloading the update.zip in stock recovery (now trying download mode install just to try something else) but I can't get the phone to be recognized by Odin (3.09) or the Verizon update/recovery tool. The only time I was able to get ADB to recognize was in recovery when using the appy update with ADB mode, but each time I try it finds the extra stuff where Xposed left it. Is there any hope of rescuing this phone???
Please help if you can?
Thanks
Well strike another dumb moment for me... booted into download mode, and now Odin 3.07sees the phone (still not 3.09) and so does Verizon restore, so hopefully one of those does the trick, Sheesh I feel dumb. lol
aaand back to sqare one. verizon repair gets to 83 percent, but then the phone disconnects the USB and won't continue. Next, tried Odin, and that fails to write to the phone as well... I'm stuck!
ToastyZ71 said:
aaand back to sqare one. verizon repair gets to 83 percent, but then the phone disconnects the USB and won't continue. Next, tried Odin, and that fails to write to the phone as well... I'm stuck!
Click to expand...
Click to collapse
Try re installing the USB drivers. I've had good luck with the one found in the SafeRoot thread myself.
Also what file are you using in Odin?
I'd say at this point just go for the full wipe nc5
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Try re installing the USB drivers. I've had good luck with the one found in the SafeRoot thread myself.
Also what file are you using in Odin?
I'd say at this point just go for the full wipe nc5
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Well it took a couple of things, but it's alive again. The first USB cable crapped out on me in the middle of the process, so swapped cables, and odin/verizon sua could see the phone. I was using Surge's link to full wipe MK2 and associated PIT file. I got the PIT file to load, but the image file kept falling with auth failures. Somewhere in there, whether Odin repartitioned the phone or what, the phone finally got to the "Firmware update has encountered a problem" screen, prompting to restore with Kies. I couldn't get Kies to not lock up, so I tried Verizon SUA again, and well whaddya know, NC5 installed. Grabbed TowelRoot straight away, and all good now, minus the fact that my Titanium BU apparently went to the emulated sd card... Ugh. But hey, at least I don't have a brick!
ToastyZ71 said:
Well it took a couple of things, but it's alive again. The first USB cable crapped out on me in the middle of the process, so swapped cables, and odin/verizon sua could see the phone. I was using Surge's link to full wipe MK2 and associated PIT file. I got the PIT file to load, but the image file kept falling with auth failures. Somewhere in there, whether Odin repartitioned the phone or what, the phone finally got to the "Firmware update has encountered a problem" screen, prompting to restore with Kies. I couldn't get Kies to not lock up, so I tried Verizon SUA again, and well whaddya know, NC5 installed. Grabbed TowelRoot straight away, and all good now, minus the fact that my Titanium BU apparently went to the emulated sd card... Ugh. But hey, at least I don't have a brick!
Click to expand...
Click to collapse
to get titanium backup to work with your external sdcard, use this: https://play.google.com/store/apps/details?id=nextapp.sdfix
Sent from my SCH-I545 using Tapatalk
joshuabg said:
to get titanium backup to work with your external sdcard, use this: https://play.google.com/store/apps/details?id=nextapp.sdfix
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Cool. It won't bring back my deleted backups, but good for future use
Hello all, I think I may have hard bricked my s4 but I can still get in to stock recovery and odin mode (download mode?) so Im sure. I've gotten out of soft brink many times but this one is winning and it's my daily driver. I'm fairly sure I partitioned ROM Slot-1 in Safestrap to small for the intnended ROM. Upon trying to reboot or power up I get black samsung custom screen and I have to pull batt to procede with only two choices: stock recovery and a file from my sd card or odin mode with proper zip file and procedure. Kies doesnt recognize and I've tried going back to NC5 through odin but that fails. I've reflashed the vrunk1 kernel and it doesnt fail but blk custom screen interupts and freezes the process.
Any help is appreciated. I FEEL that the phone is recoverable but hope is dwindling. Thanks to all.
Verizon Galaxy S4 sch-i545vrufunk1
Odin tar
Page of android development post for nc5 Odin tar works very well by surge1223
amory128 said:
Page of android development post for nc5 Odin tar works very well by surge1223
Click to expand...
Click to collapse
Thank you for the response! Im just short of freakin out here! I've tried that prodedure at least 5 times and odin fails everytime. How might I be doing it wrong? I've tried both wipe and no wipe and both fail over and over.
Thanks!!
Pull battery and put it backt, hold power+vol down+home to get into download mode and Odin back to whatever suggested above.
meazz1 said:
Pull battery and put it backt, hold power+vol down+home to get into download mode and Odin back to whatever suggested above.
Click to expand...
Click to collapse
Thank you for the suggestion...sadly thats part of what I've tried about 19 times now. : (
Try a different cable or different port. Make sure you're using the right file.
Sent from my NCC-1701 using Tapatalk.
riker147 said:
Try a different cable or different port. Make sure you're using the right file.
Sent from my NCC-1701 using Tapatalk.
Click to expand...
Click to collapse
YOU SIR ARE THE FRIGGIN MAN!!! I CANT BELIEVE THAT WORKED!!!
I was using a USB extention cable. after 86in that it went smooth as glass. THANK YOU SOO FRIGGIN MUCH...TO ALL CONTRIBUTERS who helped me get my precious back.