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.
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.
