Related
Okay. So I pushed Axura final onto my phones internal sd card and booted into recovery mode. The damned Axura copy ( it downloaded properly via google chrome, no errors) had some issue with it and DID NOT install properly. I tried again and again to make it work, did not load flash from voodoo eclair 2.1 to axura which is 2.2.
Now I want to use ODIN and come back.
I get into download mode BEAUTIFULLY using youtubes """Samsung Vibrant download mode; Corntez" .
and then load Odin, load pit file, and the tar/jar file. detected as COM 6 Odin says "added" . then run it. RUNS perfectly. firmware update start; cache.rfs;modem.bin;factoryfs.rfs; and all, and the blue bar finished completely.
Then restarts, "VIBRANT" says "data wiping failed " , everything else succeeds...lots of small writing....restart' VIBRANT" ; then Samsung Galaxy S shiny logo.
Now.....the plot thickens and my vibrant does not move forward. Black, black screen.
If I touch the bottom touch keys---viz, home etc...they light up fine. But the screen. the beautiful screen, remains as dark as Lord Voldemorts heart.
What to do??
I forgot to mention that I moved from a forward port on my thinkpad to an aft port )); and the COM4 in ODIN changed to COM 6 , promptly.
Odin is causing some issues. seems like. Any suggestions and links for newer, better versions of the T mobile stock firmware.????
Need I mention that I had voodoo before I tried to put Axura on? I did.
Thanks for all the help, in anticipation,
cheers
houston123 said:
Need I mention that I had voodoo before I tried to put Axura on? I did.
Thanks for all the help, in anticipation,
cheers
Click to expand...
Click to collapse
Houston we have a problem. Voodoo MUST be disabled BEFORE you flash. There are plenty of info on the board on how to do this. Then ODIN to stock then FLASH. Not all ROM's need a lag fix, some just run smooth!
my phone is doing the same thing but all i did was hit the voodoo button that was available in the oclf app and it went dumb the women counted down and said complete after a while and then it stuck on the vibrant samsung screen. i flash with stock rom and now its doing what this guys phone is doing please help us
Hey, yes, I read somewhere, that voodoo needs to be disabled. I did not do that, I had issues doing that.
houston123 said:
Hey, yes, I read somewhere, that voodoo needs to be disabled. I did not do that, I had issues doing that.
Click to expand...
Click to collapse
For the dear love of [deity]/self-sufficiency, go read how to solve your problem
(You need to flash Eugene's "froyo that does not brick." Then flash whichever firmware you want.)
Can someone post a link to Eugenes Froyo that does not brick please. Eugene himself has removed all support. Also, I found a zip file for Eugene somewher and NOT a tar or whateva file type ODIN uses to restore firmware.
houston123 said:
Can someone post a link to Eugenes Froyo that does not brick please. Eugene himself has removed all support. Also, I found a zip file for Eugene somewher and NOT a tar or whateva file type ODIN uses to restore firmware.
Click to expand...
Click to collapse
http://eb-productions.proboards.com/index.cgi?board=samsungsgs
I have tried but doesn't work for me. Unfortunatly I too did not disable voodoo before flashing and now I am stuck and can not get into download screen. I guess I will have to take my stuff to a cell phone repair since I have ran out of options.
got eugenes software. Now I am going to try out this:
""""
ok so here is what you have to do:
1. download odin, froyo that doesn't brick, and 2.1 true stock
2. go to download mode, flash the pit and tar file from the froyo that doesn't brick (DON'T RE-PARTITION!)
3. it will boot into recovery and error out, DONT PANIC, that is what is supposed to happen
4. remove battery (from phone) and usb from phone and computer
5. put battery back in, access odin and download mode
6. flash the pit and tar file from the true 2.1 stock (RE-PARTITION THIS TIME!)
7. if done successfully, your phone software will like when you just took it out of the box!"""
If all this does not work out, I have the 6 $ a month insurance from T Mobile---how do I use that? They might just say **** off, you screwed with the ROM and bricked the phone! Should I told them that someone flicked at Swing dance class.....instead of " I bricked it" sorry!!!!
Your opinions on this???
houston123 said:
If all this does not work out, I have the 6 $ a month insurance from T Mobile---how do I use that? They might just say **** off, you screwed with the ROM and bricked the phone! Should I told them that someone flicked at Swing dance class.....instead of " I bricked it" sorry!!!!
Your opinions on this???
Click to expand...
Click to collapse
My opinion on this is not to worry unless it doesn't work. But since you know how to use Odin and your phone can get into download mode okay, it should work.
With the insurance there is a hefty copay. But you should be fine.
I partitioned my SD card using ROM Manager, turned the phone off and got a black screen with lit keys. So, I read around and was told to use ODIN to reflash the stock TMO build, so I did. Now, Im getting the TMO logo and Galaxy S screen, but I get a black screen still.
I cannot get into download mode. I vol - and power and I get the Vibrant logo, then it goes back off. Even when plugged it, I get the batt charging animation, then back to the Vibrant screen.
I tried to push the update.zip to the SD card through ADB, but I get a permission denied message, meaning the root was killed.
So, is this phone pretty much screwed? I cant think of any other way to get it going outside of moving the update.zip to the sd card by a 3rd party measure i.e card reader/another phone
dude that's not even close to a brick as the phone is still responsive somehow..
do this:
1. pull out battery wait 5-10secs
2. connect USB to computer and phone
3. hold down the vol +/- buttons
4. plug in battery
5. you should be in download mode now
6. do what you gotta do with ODIN
good luck
Dont use that method to get to DL mode . Do it this way . First turn off your phone , then plug the usb cable into your computer ONLY . Next hold both volume buttons and plug the micro usb into your phone . Also use odin v1.3 and flash the rom of your preference .
Edit : xtone beat me to the punch
trill12 said:
I partitioned my SD card using ROM Manager, turned the phone off and got a black screen with lit keys. So, I read around and was told to use ODIN to reflash the stock TMO build, so I did. Now, Im getting the TMO logo and Galaxy S screen, but I get a black screen still.
I cannot get into download mode. I vol - and power and I get the Vibrant logo, then it goes back off. Even when plugged it, I get the batt charging animation, then back to the Vibrant screen.
I tried to push the update.zip to the SD card through ADB, but I get a permission denied message, meaning the root was killed.
So, is this phone pretty much screwed? I cant think of any other way to get it going outside of moving the update.zip to the sd card by a 3rd party measure i.e card reader/another phone
Click to expand...
Click to collapse
Yes using ROM Manager to repartition your phone will create the "soft-brick" you are experiencing. But as one person has already noted, this can pretty much be recovered using ODIN.
Definitely follow the advice given in Posts 2 and 3 of this thread to get into Download mode. If you're not getting the desired results using ODIN, what settings are you using? For example, what are the names of the .pit and .tar files you are using? Did you check or leave unchecked the "re-partition" option?
Sorry for the noobery. Im usually good at this.
Well, I was able to get into download mode and get ODIN to run, but im getting a MBD checksum error when I boot into recovery.
And I cannot install CWM through the market because my Application Storage is at 0.00B for some reason.
trill12 said:
Sorry for the noobery. Im usually good at this.
Well, I was able to get into download mode and get ODIN to run, but im getting a MBD checksum error when I boot into recovery.
And I cannot install CWM through the market because my Application Storage is at 0.00B for some reason.
Click to expand...
Click to collapse
What ROM did you flash. You might want to perform a factory reset and then flash the stock JFD ROM and see if that fixes your problem.
Good luck.
Oh this is a nightmare.... exactly what happened to me.
I'll be honest, I tried and tried and tried all sorts of stuff and somehow I got it back reading again.
I would ODIN to Eugenes Froyo that doesn't brick and see where that gets you. Thread is in developers section and I am pretty sure that's what got me back working but follow ALL the instructions. With no application room I couldn't push, unistall, install ect...
blizzard1017 said:
Oh this is a nightmare.... exactly what happened to me.
I'll be honest, I tried and tried and tried all sorts of stuff and somehow I got it back reading again.
I would ODIN to Eugenes Froyo that doesn't brick and see where that gets you. Thread is in developers section and I am pretty sure that's what got me back working but follow ALL the instructions. With no application room I couldn't push, unistall, install ect...
Click to expand...
Click to collapse
That's only needed if he flashed a rom with the wrong kernel or if he flashed a rom without disabling voodoo .
Sent from my SGH-T959 using XDA App
Just get to DL mode as xtone and I stated in post 2 & 3 . Then flashed to JFD with odin v1.3 and click the repartition box in odin and you'll be fine .
Sent from my SGH-T959 using XDA App
I had this problem for the last two days, but I found a way to fix it thanks to a user (whom I don't know the name of)
I did this to go back to stock firmware (JFD), make sure you have that downloaded.
Look for Eugene's Galaxy S Froyo PDA, for the i9000, not the Vibrant. Flash it through Odin with the 512 pit file. It's not going to boot up but take you to recovery mode instead, and it's going to remap your Volume buttons, but you can still get into DL mode (up is now down, and vice versa but whatever)
Now Odin back to stock, using the same 512 pit and there you go! Should boot up with no problem. Now you can redo everything, but remember to never partition through ROM Manager ever again!
Sent from my SGH-T959 using XDA App
Is there a link you could provide him?
AgentFour20 said:
That's only needed if he flashed a rom with the wrong kernel or if he flashed a rom without disabling voodoo .
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
His exact symptoms happened to me when the noob in me decided to repartition in Rom Manager awhile back. I am just suggesting he uses this tool as an option. It's definitely a good tool to use regardless of how he got where he got.
something like this happened to a buddy of mine, i'm trying to fix it, but the guy was completely stock so it makes no sense... I've tried everything, and i cant seem to find eugenes files...
Mr.Duck said:
something like this happened to a buddy of mine, i'm trying to fix it, but the guy was completely stock so it makes no sense... I've tried everything, and i cant seem to find eugenes files...
Click to expand...
Click to collapse
Eugenes rom are on his new site www.eb-production.proboards.com
Sent from my SGH-T959 using XDA App
OK, I got it fixed. Heres how.
I was finally able to get into ODIN and flash Eugenes Froyo.
So, from there, I was getting an MD5 checksum error when Id try to get into recovery, and I couldnt install the ROM Manager from the Market
Well, upon inspection of a the Nero V3 build I had downloaded, there was a ROMManager.apk there. So I pushed it onto my phone, reflashed to CWR (had to do it about 3 times) and reinstalled Nero V3.
After installing the build, I was able to re-enable voodoo and its theres no more MD5 craziness when I access the Recovery
trill12 said:
OK, I got it fixed. Heres how.
I was finally able to get into ODIN and flash Eugenes Froyo.
So, from there, I was getting an MD5 checksum error when Id try to get into recovery, and I couldnt install the ROM Manager from the Market
Well, upon inspection of a the Nero V3 build I had downloaded, there was a ROMManager.apk there. So I pushed it onto my phone, reflashed to CWR (had to do it about 3 times) and reinstalled Nero V3.
After installing the build, I was able to re-enable voodoo and its theres no more MD5 craziness when I access the Recovery
Click to expand...
Click to collapse
So voodoo was the culprit . lmao
I dont remember you ever mentioning that . Any way glad you figured it out and have your phone back .
AgentFour20 said:
So voodoo was the culprit . lmao
I dont remember you ever mentioning that . Any way glad you figured it out and have your phone back .
Click to expand...
Click to collapse
Apparently. Completely forgot I attempted to enable it. I was freaked all the way out trying to repair the damn thing.
My phone was working fine after installing the DOW14 kernel yesterday. This morning it was even working fine. Even my alarm went off this morning on the phone and I set it an hour ahead (for more sleep) and it didn't go off. I looked at my phone and the screen would not come on. The "buttons" at the bottom lit up, but nothing I had to hold the power button down to get it to reboot.
It got past the "Vibrant" text and shows the green robot for TeamWhiskey, but just sits there. Tried taking the battery out and still it will boot to the same place. Can anyone help?
I did not overclock, I never ran SetCPU.
If you can get it to download mode, try flashing another kernel through odin since you cant see anything. Just the kernel not a rom. Supercurio has some voodoo kernels for odin in the dev section. Just look for your base and odin the corresponding kernel. Goes in PDA. Dunno if there are any "stock" odin kernels or not.
jmcghee1973 said:
If you can get it to download mode, try flashing another kernel through odin since you cant see anything. Just the kernel not a rom. Supercurio has some voodoo kernels for odin in the dev section. Just look for your base and odin the corresponding kernel. Goes in PDA. Dunno if there are any "stock" odin kernels or not.
Click to expand...
Click to collapse
Hold vol up + down + power right? I can't seem to get into recovery/download mode. I am downloading Bay_wolf's AIO Vibrant Toolbox 2.5 right now.
raulcota said:
Hold vol up + down + power right? I can't seem to get into recovery/download mode. I am downloading Bay_wolf's AIO Vibrant Toolbox 2.5 right now.
Click to expand...
Click to collapse
Watch this video to get to download mode http://www.youtube.com/watch?v=D0aoabVtPJ8&feature=youtube_gdata_player
Sent from my SGH-T959 using XDA App
I had a similar issue and crazy enough, it worked. Then I just odined back to stock then rooted and flashing all over again
Sent from my SGH-T959 using XDA App
I can get it to reboot using adb reboot recovery, but it never actually boots into recovery still sticks at the teamwhiskey robot chick screen, lame
raulcota said:
I can get it to reboot using adb reboot recovery, but it never actually boots into recovery still sticks at the teamwhiskey robot chick screen, lame
Click to expand...
Click to collapse
not recovery...download mode w/the digging robot on the screen.. I'm not familiar with adb does it adb reboot download or anything of that nature?
Try this, it worked for me. Pop your battery, put it back in, hold vol up down and power. Wait for vibrant to pop up the second time and release. Should put you in recovery. Factory data reset, reflash you rom, wipe dalvik and fix permissions, then reboot. I had the same issue with the Bionix 1.2.1 update and the glasstopia theme w/ dragon 4. They didnt play well together. Hope this helps.
you may want to build a jig or buy one online in the future just in case you cannot get into the download mode.
http://cgi.ebay.com/ws/eBayISAPI.dl...25272&ssPageName=STRK:MESELX:IT#ht_595wt_1139
OK, I can get into download mode and I have been trying this method with no success:
http://forum.xda-developers.com/showpost.php?p=8698655&postcount=150
Odin flashes the phone and it just comes back and reboots again. Man this sucks
I am wondering if there is a full flash file somewhere I found one Fascinate, but I am afraid to flash my Vibrant with it.
http://forum.xda-developers.com/showthread.php?t=867648 that is the fascinate one
Several people are having this problem including me... I worked on it all day yesterday. No matter what you odin, even eugenes no brick fix then JFD, nothing will work. I hate to tell you but your phone is toast.
Sent from my MB200 using Tapatalk
I agree man.
I've looked at every single thread with this same exact issue.
No avail. The file system, the ones that are reserved and locked for the bootloader and ROM are corrupted, is my guess.
I can load all the roms on there, but something isn't loading correctly, or is beyond corrupted, not allowing me to boot the phone at all.
My phone is toast too.
Damn, im not happy.
Nobody has a fix for this though. Nobody.
Anyway, sorry to hear about your phone. Mine is also bricked completely.
Keep in mind, this is from somebody who has bricked every possible way (apparently not this way), and ODIN at least once a week. I've also used Eugene's i9000 OC kernels, old DOW OC kernels, and TTBAL's OC kernel with NO PROBLEMS AT ALL!!! 1.4gHz stable.
Now this.
WTF Mate.
drewdude007 said:
Several people are having this problem including me... I worked on it all day yesterday. No matter what you odin, even eugenes no brick fix then JFD, nothing will work. I hate to tell you but your phone is toast.
Sent from my MB200 using Tapatalk
Click to expand...
Click to collapse
I see that in the DoW 14 thread now. I am not giving up yet, but that is discouraging.
Unbrick me!!!
ive bricked my phone before and ive used odin to get my phone running again but this time its diffrent it wont go into download mode it just keeps blinking at the VIBRANT samsung screen and when i connect it to my computer the battery loop turns on and if i let go of the buttons that take me to download mode it just goes back to flashing vibrant IM SCARED someone plz help!
posted by team whiskey
"Optional Kernels:
Optional kernels will be uploaded and posted when I get home.
They will include a Modded DOW and Modded Dragon to allow for mounting Internal SD. Do Not flash the current DOW/Dragon kernels or you will loose mounting functionality."
my girls phone is shot and i took the dow off mine real quick
no more oc for me thanks sold my bricked phone on ebay for 150$
maybe that will help for people to recover the loss a bit?
good luck i tried for days.
Still Broken...
Anyone ever get this fixed? I still have a broken phone
power off phone
pull out battery
GRAB THIS STUFF : http://forum.xda-developers.com/showthread.php?t=1047087
turn on odin
attach phone to pc with usb cable
now while holding down both volume buttons put battery back in.
now you should be in download mode and go back to stock with odin from here!
make sure u put the proper .pit and .pda file in there proper places on odin and ur set to go.
Enjoy and also make sure u have the proper samsung drivers
what rom are you running? did you check to see if it was even compatible with the kernel your flashing? I mean.... are you on gingerbread roms or froyo?
I sold my friend my Samsung Vibrant and I've never had any problems flashing it, he tried flashing the cyanogenmod rom (tried being the operative word...) and I'm not sure what he did to but when I try to turn it on its has the I9000 boot screen and it goes to the vibrant splash screen and turns off, if it's plugged it gets to the vibrant screen and then has the cycle icon for the battery then it shows the battery and it infinitely loops like this when its plugged in (when I had it, it would be completely dead and I could plug it in and turn it on at the same time and it would boot fine and didn't die). I tried flashing JI6 via ODIN, which seemed to flash correctly (gets to zImage and says removed and then pass), but nothings changed (still I9000 boot screen and still crashes on splash screen with battery loop). Any idea what I can do to fix this?
I think your friend flashed the I900 Version of the Rom. Try odin-ing to stock.
EDIT: You already odin-ed JI6. Try odining to stock JFD with both pit and tar files. That should restore everything (bootloader, kernel, baseband, etc...)
its shows i9000 on boot with the GB bootloaders
http://forum.xda-developers.com/showthread.php?t=849028 have a read through there
if you do have the GB bootloaders its vol up and power for download mode
odin to stock will fix it
Downloaded and tried all three of these things and still nothing different. When I turn it on the boot and splash screen come up but then the device just turns off. Tried JI6 and JFD, and the boot screen keeps showing up as the I9000 (GB), when it should be the stock TMOUS bootscreen, so it seems like the bootloader isn't being flashed correctly, although it says pass and has no errors. I'm thinking that the phone is bricked, is there anything I'm not thinking of that would help?
ddaydude said:
Downloaded and tried all three of these things and still nothing different. When I turn it on the boot and splash screen come up but then the device just turns off. Tried JI6 and JFD, and the boot screen keeps showing up as the I9000 (GB), when it should be the stock TMOUS bootscreen, so it seems like the bootloader isn't being flashed correctly, although it says pass and has no errors. I'm thinking that the phone is bricked, is there anything I'm not thinking of that would help?
Click to expand...
Click to collapse
go there:
http://forum.xda-developers.com/showthread.php?t=1230059
skip the parted part you dont need it and phone would be back to good function asap.
ddaydude said:
Downloaded and tried all three of these things and still nothing different. When I turn it on the boot and splash screen come up but then the device just turns off. Tried JI6 and JFD, and the boot screen keeps showing up as the I9000 (GB), when it should be the stock TMOUS bootscreen, so it seems like the bootloader isn't being flashed correctly, although it says pass and has no errors. I'm thinking that the phone is bricked, is there anything I'm not thinking of that would help?
Click to expand...
Click to collapse
the jfd.tar doesnt have the bootloaders i dont think so you'll still be on GB bootloaders on 2.1, they're backwards compatible anyway so it doesnt matter
demetris_I said:
go there:
http://forum.xda-developers.com/showthread.php?t=1230059
skip the parted part you dont need it and phone would be back to good function asap.
Click to expand...
Click to collapse
I've tried to get into recovery mode for this but I can only get into download mode (tried VOLUP+HOME+POWER (and without home) boots to download mode, tried VOLDOWN+HOME+POWER (and without home) and it does nothing, I've tried to use adb on the download screen but it doesn't find the device). Is there another method that I'm missing?
I remember telling you you dont need parted part -> dont need to enter cwm just download mode.
1.download mode
2.http://www.4shared.com/file/dJiyRz3v...Froyo_PDA.html
unzip it and get odin ready.
Go to download mode, place pda only in phone area pit not needed, flash
Let it boot into recovery, remove battery and re-enter download mode.
Flash JFD with pit file and re-partitions checked.
Done and done.
demetris_I said:
I remember telling you you dont need parted part -> dont need to enter cwm just download mode.
1.download mode
2.http://www.4shared.com/file/dJiyRz3v...Froyo_PDA.html
unzip it and get odin ready.
Go to download mode, place pda only in phone area pit not needed, flash
Let it boot into recovery, remove battery and re-enter download mode.
Flash JFD with pit file and re-partitions checked.
Done and done.
Click to expand...
Click to collapse
Sorry about that, my bad. But I tried just tried that, and when I flashed the Froyo file it booted to recovery (like it sounds like it should have, still with GB bootloader and reversed controls on recovery and not able select since vibrant doesn't have an ok button) and then flashed JFD with the pit and repartition selected and it goes back to turning off after the vibrant screen. I tried redownloading both froyo and JFD thinking one might be corrupt and I still get the same result as before. I've checked the instructions 10+ times and I've used odin for the life of this phone more times than I have counted, and I can't figure out why it doesn't seem to be taking it, it doesn't fail in odin so it doesn't make sense.
After doing what i recommended your phone would be in fully functioning order.
Your problem lies on the bootloader so i would recommend to flash froyo bootloader from here:
http://forum.xda-developers.com/showthread.php?t=1117990
but before md5 check the downloaded file and follow exactly the guide there.
If this dont fix it then i think your phone is a pita.
I kinda agree that its probably just the Bootloaders that is the culprit for the I9000 splash. As mentioned flashing the original FROYO should fix it. At least it did for me. I had to do both these links in the GB bootloader thread for it to take though. 1st one 1st - then either of the 2nd links 2nd.
adyscorpius said:
jfd odin file - for use after installing gingerbread bootloaders
http://www.multiupload.com/hryjkflkfq "thanks to laylovj"
md5: 977e2136996e7138945447a8245d6776
if you have gingerbread bootloaders installed and you end up odining to stock (jfd), you will notice it changes the bootsplash to i9000. You can either reflash a gb bootloader again, or simply use the odin package above to do so.
vibrant stock (froyo) bootloader download link
- dropbox download link
- mediafire download link
md5 sum - 754ecbd8e76d4f81bec49240031f3262
Click to expand...
Click to collapse
Now as far as ODIN. The yellow triangle and android dude digging should be there throughout the entire ODIN flash. If I understand you correctly and the phone goes black during the ODIN flashthats no good. If its doing it after the ODIN flash, then maybe you still have the "reboot after flash" button ticked. Either way the phone needs to stay in download mode during the entire ODIN flash.
*EDIT*
- If all else fails JTAG! but that should be the last option. There is a fix!
- BUY A USBJIG you can get them from either TeamWhiskey or EDT on their sites. If everyone had one we would never see another
"NO DOWNLOAD MODE!!! HELP" thread again. And at the same time you'd be supporting developers which is a good thing.
Good luck!
You should try the "froyo that does not brick" in the early days of froyo eugene released a froyo package that came with bootloaders. Google ftdnb, it may also be in either bricked or eb's threads
Beware of angry gingerbread man
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.