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
Hello,
I am hoping someone can direct me as to how I can unbrick my device.
I have been using JellyBomb for about a month now and decided to upgrade to the newest version. I downloaded 3.0 and put it on my external SD card via usb. I backed up what I needed to onto google drive and dropbox and did a factory reset. Upon installing the ROM, however, I received an error message saying that the ROM had failed.
I tried another old file after another factory reset (old jellybomb version) and this got stuck in the middle of flashing it. This is when the trouble started as when I rebooted my device I could not access Recovery.
I have since reflashed my recovery to Clockwork and now I can get into that menu. I have tried to download the stock ROM from sammobile and after that 10 hour download (and I am not sure if I'm doing this correctly) it does not flash the entire 1.3 gig file. It looks like it only does something to the recovery. I am putting the .TAR file into the "PDA" section of ODIN... is this not correct? I can not find a TAR.mp5 file like the tutorials say so maybe I have the wrong file type?
Any help is GREATLY appreciated!!! Thank you for your time.
Drew
To clarify: The only screens that I can get to are recovery and download mode. If I go into recovery and try to flash something it does not work but gets stuck in a freeze. In download mode my computer is seeing it when I am in ODIN but I am not sure that I have the right stock ROM file.
Does anyone have experience with this?
thecarpenter said:
To clarify: The only screens that I can get to are recovery and download mode. If I go into recovery and try to flash something it does not work but gets stuck in a freeze. In download mode my computer is seeing it when I am in ODIN but I am not sure that I have the right stock ROM file.
Does anyone have experience with this?
Click to expand...
Click to collapse
I'm on my 3rd Note 3 because of all kinds of issues with rooting....I've used CF auto, and Kingo. Had exact same issue of not being able to restore android, and soft bricking. Once was able to push MI4 from sammobile using ODIN 1.85, .tar in PDA. If it took you 10 hours to download, you probably have a bad download. I have not rooted this device because of all the problems almost everyone is having sooner or later, and STILL have to reboot, battery pull, wipe cache from stock recovery etc. Knox/selinux kernel Samsung has started using seems to be the culprit(s). Just look at all the posts for problems, lack of new development, and the fact that a Note 2 costs more with a contract than the 3....If you can successfully flash stock,I would stick with it for now. Good luck!:good:
thecarpenter said:
To clarify: The only screens that I can get to are recovery and download mode. If I go into recovery and try to flash something it does not work but gets stuck in a freeze. In download mode my computer is seeing it when I am in ODIN but I am not sure that I have the right stock ROM file.
Does anyone have experience with this?
Click to expand...
Click to collapse
I believe that this is what you want,
http://forum.xda-developers.com/showthread.php?t=2549035
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
I believe that this is what you want,
http://forum.xda-developers.com/showthread.php?t=2549035
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
NICE. Going to give this a try. Thanks!
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.
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....
I went to upgrade to the new hyperdrive since they sent me the ota. Phone has been acting weird so I was going to do a complete wipe. I took my sd card out which my son took and lost on me and OI can find anywhere. I had another card so d/l new hyperdrive onto other card. I went to wipe cache and install new rom. phone wiped data and now wouldnt install new rom. I dont remember all the build I was on on the phone but I had Hyperdrive 16 before I started this if that helps at all. I am stuck on samsung custom boot screen. I can get into odin recovery and tried recovery but keeps failing. can I get some help I need my phone i have to go to work soon. Thanks
ive tried the rootjunky video with both no wipe and full wipe neither worked. odin failed.
FlipFlop425 said:
ive tried the rootjunky video with both no wipe and full wipe neither worked. odin failed.
Click to expand...
Click to collapse
What files are you trying to flash? Did you use Safestrap to install RLS16?
Sent from my NCC-1701 using Tapatalk.
i had downloaded the new update for hyper drive. Right now my biggest probelm is I cannot get past the splash screen. I can get into download mode though so can we try to figure out how to unbrick me first. Download mode is the only thing I can seem to get into right now
FlipFlop425 said:
i had downloaded the new update for hyper drive. Right now my biggest probelm is I cannot get past the splash screen. I can get into download mode though so can we try to figure out how to unbrick me first. Download mode is the only thing I can seem to get into right now
Click to expand...
Click to collapse
That's why I need to know if you used Safestrap as your recovery. It's very likely you're trying to flash the wrong file with Odin.
If you had Safestrap your build wasn't MDK. If you didn't need Safestrap then your build was MDK.
So I'll ask again, what file are you trying to flash, with Odin, that keeps failing?
riker147 said:
That's why I need to know if you used Safestrap as your recovery. It's very likely you're trying to flash the wrong file with Odin.
If you had Safestrap your build wasn't MDK. If you didn't need Safestrap then your build was MDK.
So I'll ask again, what file are you trying to flash, with Odin, that keeps failing?
Click to expand...
Click to collapse
I used to have to use safestrap. I was trying to flash the mdk file from rootjunky's video on unbricking your phone
FlipFlop425 said:
I used to have to use safestrap. I was trying to flash the mdk file from rootjunky's video on unbricking your phone
Click to expand...
Click to collapse
NO!!! You cannot flash the MDK file, you cannot downgrade the S4! Always ends badly, go to the general section and grab the NC5 full-wipe tar and flash with ODIN.
npjohnson said:
NO!!! You cannot flash the MDK file, you cannot downgrade the S4! Always ends badly, go to the general section and grab the NC5 full-wipe tar and flash with ODIN.
Click to expand...
Click to collapse
I have tried that from SUrge1223. That did not work for me. I cannot get in to my phone to re root it. Is that the right file the one from him?
FlipFlop425 said:
I have tried that from SUrge1223. That did not work for me. I cannot get in to my phone to re root it. Is that the right file the one from him?
Click to expand...
Click to collapse
From here http://forum.xda-developers.com/showthread.php?t=2735172. I would choose the "Full Wipe" version. Make sure you have a good download. Check MD5. Make sure you follow the directions for Odin. If you verify all of that, and it still doesn't work, I'm afraid I won't be any more help. Someone with more knowledge than I have will have to step in. Good luck.
riker147 said:
From here http://forum.xda-developers.com/showthread.php?t=2735172. I would choose the "Full Wipe" version. Make sure you have a good download. Check MD5. Make sure you follow the directions for Odin. If you verify all of that, and it still doesn't work, I'm afraid I won't be any more help. Someone with more knowledge than I have will have to step in. Good luck.
Click to expand...
Click to collapse
I can vouch for the full Version. Saved my bacon.
You have to boot the phone into a special mode that will allow ODIN to funtion
Turn off the SGS4 and boot it into Download/Odin Mode: press and hold the Volume Down, Home and Power buttons simultaneously for a couple of seconds till you see a warning screen. Then press Volume Upkey to enter Download Mode.
I got it!!! Found my Samsung cable and all went well. TY for ALL the help!
FlipFlop425 said:
I got it!!! Found my Samsung cable and all went well. TY for ALL the help!
Click to expand...
Click to collapse
Yeah, it is a really good feeling when that ODIN starts to run like it means it. Nothing beats that first boot up!