Hi,
I have a Sprint 4G LTE rooted with VIPER rom installed. Last night my phone freaked out, so I did the 10 second "battery pull" and it started up again. I plugged it into the charger and I fell asleep without much worry.
I woke up to find my phone stuck at the LTE splash screen of the VIPER rom. I've done the 10 second "battery pull" several times, and it doesn't just shut the phone off, it forces a reboot. Each time it only makes it as far as the LTE splash screen.
My experience with phones and computers is telling me that the OS might have gotten corrupt some how since it is stuck at the splash screen.
I do have access to the bootloader, so I have some paths I can go down, factory reset/recovery, but both those I'd like to avoid so that I do not lost the contents of my storage.
I have had VIPER rom installed for a good half year, so this issue isn't due to a new rom being flashed.
Does anyone have any suggestions?
Thanks,
-billypilgrim
When data gets corrupted, all you can do is wipe and start over. I had to do that once when running Viper as well.
Just a thought in trying to be helpful....
I used that ROM for a while myself and never really had any issues but have had a similar situation.
I pulled my sd card out and backed it all up. Replaced SD card.
Then went into recovery and reflashed the ROM.
Worked solid after that and no explanation as to why it was corrupt/hanging in a loop.
Hope this helps..
billypilgrim said:
Hi,
I have a Sprint 4G LTE rooted with VIPER rom installed. Last night my phone freaked out, so I did the 10 second "battery pull" and it started up again. I plugged it into the charger and I fell asleep without much worry.
I woke up to find my phone stuck at the LTE splash screen of the VIPER rom. I've done the 10 second "battery pull" several times, and it doesn't just shut the phone off, it forces a reboot. Each time it only makes it as far as the LTE splash screen.
My experience with phones and computers is telling me that the OS might have gotten corrupt some how since it is stuck at the splash screen.
I do have access to the bootloader, so I have some paths I can go down, factory reset/recovery, but both those I'd like to avoid so that I do not lost the contents of my storage.
I have had VIPER rom installed for a good half year, so this issue isn't due to a new rom being flashed.
Does anyone have any suggestions?
Thanks,
-billypilgrim
Click to expand...
Click to collapse
I have that happen several times. Nothing obvious that causes it. Cap'n is right need to wipe and re-flash. Here's the small trick since it just keeps rebooting on you, after you hold power for ten seconds and the screen blacks out. Make sure the capacitive buttons go out as well, that split second they go dark let go of the power button and press vol down and power to get it back into bootloader. Then you can get back in recovery to flash.
Related
So I just got done configuring chompSMS. Disabled notifications on the built in SMS app. Did a battery pull and got this screen and haven't been able to get out of it. Held down home & power and got a user memory wipe screen. Figure I'd give that a shot. Still stuck on the FASTBOOT screen and now have to redo the whole thing if I manage to get out of this screen.
Anyone else see this? Not much out there about Sprint's Hero, but there's a bit about Orange's Hero, rooting, flashing rom's and all that fun stuff. Nothing about getting it back to normal though.
and to add....after letting it sit connected to usb for a bit, the screen finally went dark but now won't turn back on. Really odd.
hmm im kinda new to android, but if your stuck in fastboot cant you use the devkit to push a new recovery image like RA 1.2.3 and flash ?
i might be wrong tough
I'm brand spanking new to Android. Haven't dealt with sdk's andn loading rom's in ages and don't have the time to figure it out. Thought there might be some hard reset button combo that I was missing or something. Just heading to the Sprint store now with box in hand to have them switch it out or activate my Treo Pro again. Kinda need the phone for work and don't have a home phone so downtime is not a good thing.
darkenergy said:
hmm im kinda new to android, but if your stuck in fastboot cant you use the devkit to push a new recovery image like RA 1.2.3 and flash ?
i might be wrong tough
Click to expand...
Click to collapse
he won't be able to push that to do ADB tricks, nor do fastboot flashing with img files
Goldcard doesn't help as well
I hv got a G1 in same situation after pulling out the battery.
Stucked at first splash screen on next boot.
I assume that is a rom / system problem so I tried to boot into recovery but still freeze on 1st splash screen.
I tried to figure out the problem and I'd try to connect by usb and tried adb logcat but only waiting device return. And yep the screen goes black ( but still on ) likely in this situation.
And yea SPL enter was successful but can't connect to fastboot so no recovery can flash.
I notify the phone (seemingly) won't be able to charge as the notification do not turn on, or it does charge but problem with notification light (?), probably it is more likely a hardware problem due to removing the battery. Recently I take the G1 to a shop to figure out is that a hardware failure.
I'm all for troubleshooting and playing around with ROMs, but there's times when I just need to be up and running and have opted not to screw around with something I depend on for work. There's other toys to "play" with.
So after a way too long stay at the Sprint store I have a new Hero that's up and running just fine.
Wanted to say it was something I installed, but everything seemed to be approved by the masses as working well. Maybe it was something with the battery pull. I'm surprised no one has made a soft reset widget. Seems kinda basic coming from 13yrs of PalmOS and a bit of winMob.
dbpaddler said:
So I just got done configuring chompSMS. Disabled notifications on the built in SMS app. Did a battery pull and got this screen and haven't been able to get out of it. Held down home & power and got a user memory wipe screen. Figure I'd give that a shot. Still stuck on the FASTBOOT screen and now have to redo the whole thing if I manage to get out of this screen.
Anyone else see this? Not much out there about Sprint's Hero, but there's a bit about Orange's Hero, rooting, flashing rom's and all that fun stuff. Nothing about getting it back to normal though.
and to add....after letting it sit connected to usb for a bit, the screen finally went dark but now won't turn back on. Really odd.
Click to expand...
Click to collapse
download htc sync and install it.
http://www.htc.com/us/supportdownloadlist.aspx?p_id=300&act=sd&cat=all
download sprint RUU and run it, it will wipe your phone, but it will work agian
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
thanks for that. Will keep that handy for next time or if I ever play around with it. I think I'm going to the Moment though when it hits next month. Better screen, processor and keyboard will be doing it for me.
fixing any android stuck in fastboot
If your stuck in fast boot this is what you do.
1. Remove the micro sd card and somehow connect it to your computer.
2. Download a rom that is made for your phone and put it in a easily accessible folder on the micro sd.
3. Reinsert the sd card in the phone and reboot, once in fast boot go to hboot.
4. After going into hboot select recovery.
5. After this is done you must go to "install zip from sd card" and choose the rom that you have downloaded, select install and wait until the installation is complete, if unsuccessful redownload and try the whole process again, if unsuccessful the second time try downloading another rom.
If you have any questions please personal message me so i can help you.
Download: cyanogenmod.com
Btw i had a HTC hero and had this problem many times and this had worked every time.
I have a similar situation
when i power on the phone it goes straight to fastboot mode.
I Checked volume keys and are not stuck.
If I connect phone via usb and run:
fastboot reboot
the phone will load normally the android OS and will work just fine until you power it off again.
\
I dismantled the phone just to be sure there is no hardware issues, I tried to power on the phone without the home button connected to the board and the phone will load the android OS without any issue.
I dismantled the button itself, it has some sort of touch IC inside and a normal key button downside.
I could not notice any dust or water tracks in the button, so
at this point and dont know where to go...
I dont have another button just to be sure if it is the button itself or a board issue.
dbpaddler said:
So I just got done configuring chompSMS. Disabled notifications on the built in SMS app. Did a battery pull and got this screen and haven't been able to get out of it. Held down home & power and got a user memory wipe screen. Figure I'd give that a shot. Still stuck on the FASTBOOT screen and now have to redo the whole thing if I manage to get out of this screen.
Anyone else see this? Not much out there about Sprint's Hero, but there's a bit about Orange's Hero, rooting, flashing rom's and all that fun stuff. Nothing about getting it back to normal though.
and to add....after letting it sit connected to usb for a bit, the screen finally went dark but now won't turn back on. Really odd.
Click to expand...
Click to collapse
yurais said:
I have a similar situation
when i power on the phone it goes straight to fastboot mode.
I Checked volume keys and are not stuck.
If I connect phone via usb and run:
fastboot reboot
the phone will load normally the android OS and will work just fine until you power it off again.
\
I dismantled the phone just to be sure there is no hardware issues, I tried to power on the phone without the home button connected to the board and the phone will load the android OS without any issue.
I dismantled the button itself, it has some sort of touch IC inside and a normal key button downside.
I could not notice any dust or water tracks in the button, so
at this point and dont know where to go...
I dont have another button just to be sure if it is the button itself or a board issue.
Click to expand...
Click to collapse
People still use the Hero? There are so many better phones you can buy for dirt cheap. Heck, I got the Evo LTE for $80 on Craigslist. Even the Evo Shift, Design and 3D can be had cheap. I'd dump the Hero without blinking.
Thanks in advance for your help. So far my experience with the Thunderbolt has been pretty bad - this is the worst Android experience I have had yet, coming from OG DROID and then DInc w/ CM7. Besides the bad battery life I have had several reboots, several FCs on pretty vanilla apps, problems with Exchange Sync and now this:
I have done nothing to the phone other than install a couple of apps - no rooting, etc.
I left the phone plugged in last night and this morning picked it up (still plugged in) and went to play a game of Angry Birds. App would not run, immediate force close. Ok, move on to check my Gmail - check email and delete a message, Gmail FC. Ok, let me reboot. I reboot the phone (while plugged in) and the phone goes into bootloader. I try again (not knowing at the time that this is a known issue with this phone) and keep ending up in bootloader/recovery. Unplug the power cord, pull the battery and now the phone boots to the Thunderbolt scene and sound, hangs on that, then resets immediately (no black screen) to the white HTC screen and then the Thunderbolt scene again - over and over.
I rebooted back into recovery and tried to do a factory reset - the phone flashes to the androids on the skateboards and goes right back to recovery in about 5 seconds. Pull battery and boot up - goes back into the boot loop at the Thunderbolt scene.
Not really sure what to do now - any ideas?
boingboingbilly said:
Thanks in advance for your help. So far my experience with the Thunderbolt has been pretty bad - this is the worst Android experience I have had yet, coming from OG DROID and then DInc w/ CM7. Besides the bad battery life I have had several reboots, several FCs on pretty vanilla apps, problems with Exchange Sync and now this:
I have done nothing to the phone other than install a couple of apps - no rooting, etc.
I left the phone plugged in last night and this morning picked it up (still plugged in) and went to play a game of Angry Birds. App would not run, immediate force close. Ok, move on to check my Gmail - check email and delete a message, Gmail FC. Ok, let me reboot. I reboot the phone (while plugged in) and the phone goes into bootloader. I try again (not knowing at the time that this is a known issue with this phone) and keep ending up in bootloader/recovery. Unplug the power cord, pull the battery and now the phone boots to the Thunderbolt scene and sound, hangs on that, then resets immediately (no black screen) to the white HTC screen and then the Thunderbolt scene again - over and over.
I rebooted back into recovery and tried to do a factory reset - the phone flashes to the androids on the skateboards and goes right back to recovery in about 5 seconds. Pull battery and boot up - goes back into the boot loop at the Thunderbolt scene.
Not really sure what to do now - any ideas?
Click to expand...
Click to collapse
Sorry I don't have an answer for you but how did you reboot into recovery if you haven't rooted? I'm confused.
I would say you got a bad phone and should go ahead and take it back to where you bought it and get another one.
Sorry, probably calling it the wrong thing. Boots into HBOOT, where fastboot, recovery, and Factory Reset are available options.
return it!
I was wondering the same thing. Didn't know you can boot into recovery without root access.
jacobk said:
return it!
Click to expand...
Click to collapse
Yep I would be returning it... As fast as possible.
So far my experience is the opposite, battery life isnt great sure. But the phone is blazing fast and worth the money, ill just keep a charger with me. Ive haf every smartphone made and if you use them as much as i do, the battery wont last a full day on anything. Ive give up on that. Take that beast back and get a new one.
Sent from my ADR6400L using XDA App
Wasnt getting much feedback other than "return it" so I called up VZB and they are overnighting a new one.
My coworker had some problems with his too - he got frustrated and returned it and doesn't want another one. His would reboot randomly while in apps - Google search shows several people having that issue and he was getting terrible battery life compared to his iPhone and OG Droid.
Seems this phone is pretty rough around the edges considering all the delays with its release. Gonna give it another go with the replacement, but definitely not as smooth as my DInc or my iPhone 4. This thing makes my iPhone look damn near perfect in terms of stability and battery life. Don't get me wrong, I am a huge Android fan with many Android phones under my belt, 2 rooted Nook colors one with Froyo and the other with CM7, and a Xoom - just been disappointed with what I am experiencing first hand and what I am reading. Only reason I asked for a replacement instead of a return is hopefully CM7 will come along soon and make this device shine.
you can enter hboot, recovery and all by holding power and volume down when turning ur phone on. then select recovery and it will boot u into recovery.
RafficaX said:
you can enter hboot, recovery and all by holding power and volume down when turning ur phone on. then select recovery and it will boot u into recovery.
Click to expand...
Click to collapse
In my case booting to recovery from HBOOT got the red exclamation point. Phone was hosed I guess.
RafficaX said:
you can enter hboot, recovery and all by holding power and volume down when turning ur phone on. then select recovery and it will boot u into recovery.
Click to expand...
Click to collapse
but you can only install signed/ verified VZW files in the official recovery... usually have to be named update.zip for the recovery to find them... just to clarify...
sorry to hear about your first tbolt experience... I had a Dinc for 6 months before I reccomended it to my friends... I rooted and ran every rom imaginable with 0 problems... they leave it stock and its just been one thing after another... yesterday my friend showed me her messed up camera, i told her i didn't touch it so I wont fix it take it back... good luck and hope our next one is a good one
Weird experience today..used my phone at lunch, no issues. Went to to use it this afternoon and it would not wake up. I held the power button down for about 10-15 seconds, then it vibrated like it was rebooting. That's when it started to vibrate every 10-15 seconds, similar to a boot loop, but the display is dark. I'm unable to get it to boot into hboot, or recovery. When plugged in, the charging indicator does not illuminate. I think it's bricked. I'm running s-off, and MeanBean. This is the first time I've ever experienced an issue like this with any of my android phones.
I hope that once the battery dies, I can charge it and hope that it boots into hboot, or recovery.
Any suggestions?
Damn. Seeing a lot of posts like this lately. Making me nervous
Sorry, wish I knew what to tell you.
Sent from my EVO using xda premium
Greubin said:
Weird experience today..used my phone at lunch, no issues. Went to to use it this afternoon and it would not wake up. I held the power button down for about 10-15 seconds, then it vibrated like it was rebooting. That's when it started to vibrate every 10-15 seconds, similar to a boot loop, but the display is dark. I'm unable to get it to boot into hboot, or recovery. When plugged in, the charging indicator does not illuminate. I think it's bricked. I'm running s-off, and MeanBean. This is the first time I've ever experienced an issue like this with any of my android phones.
I hope that once the battery dies, I can charge it and hope that it boots into hboot, or recovery.
Any suggestions?
Click to expand...
Click to collapse
This has happened to me. It is in what I believe diag mode or something. I kept holding the power and volume to get in recovery, which it did go to, and I wiped all caches, and re flashed the rom, and all was good! Hope that helps.
I dropped my phone off at a Sprint Service Center today...they tried everything to restore it, or get it to boot for that matter. It's dead, replacement phone on the way.
I had the same thing happen to my phone and came across this thread while looking for a solution. I also ended up having to get it replaced. Fortunately I did a full back-up three days prior to it crapping out so I didn't loose much.
Last night my phone started bootlooping very frequently. I was running the CM10 built with Samsung source that was posted in this section for a while with absolutely no problems, when suddenly the phone shut off and started doing short, quick vibrations repeatedly. Like the vibration that the phone makes when it first turns on and shows the Samsung logo. I pulled the battery but it continued once I put the battery back in. Eventually I got it to boot but soon after it booted it started again. I am now running Blackjelly v1, and though less frequent, the problem still persists...does anyone have any idea what could be causing this?
zefir738 said:
Last night my phone started bootlooping very frequently. I was running the CM10 built with Samsung source that was posted in this section for a while with absolutely no problems, when suddenly the phone shut off and started doing short, quick vibrations repeatedly. Like the vibration that the phone makes when it first turns on and shows the Samsung logo. I pulled the battery but it continued once I put the battery back in. Eventually I got it to boot but soon after it booted it started again. I am now running Blackjelly v1, and though less frequent, the problem still persists...does anyone have any idea what could be causing this?
Click to expand...
Click to collapse
Mine did the same thing... It was crazy...Nothing I did fixed it... Flashed away at any 4.2.2 Rom and It was consistent bootloop... Decided to take phone apart and clean power button (read somewhere power button gets stuck) Same issue bootloop... I odined back to stock...bam it worked...now the capacitive buttons don't work... So after booting stock I flashed TWRP recovery and attempted to flash 4.2.2 rom to no prevail, I am only capable of flashing BlackJelly v1 any other rom sends me into (App is upgrading screen after boot after apps say Starting Apps bootloop) nonstop bootloop...
I honestly wonder if my phone is the only phone that will not accecpt 4.2.2 roms...
kaljr1980 said:
Mine did the same thing... It was crazy...Nothing I did fixed it... Flashed away at any 4.2.2 Rom and It was consistent bootloop... Decided to take phone apart and clean power button (read somewhere power button gets stuck) Same issue bootloop... I odined back to stock...bam it worked...now the capacitive buttons don't work... So after booting stock I flashed TWRP recovery and attempted to flash 4.2.2 rom to no prevail, I am only capable of flashing BlackJelly v1 any other rom sends me into (App is upgrading screen after boot after apps say Starting Apps bootloop) nonstop bootloop...
I honestly wonder if my phone is the only phone that will not accecpt 4.2.2 roms...
Click to expand...
Click to collapse
It's now bootlooping like crazy. It'll turn on for like 5 minutes and then go right back to bootlooping. My USB port is kinda screwy so it's hard to odin anything. I'm at a loss for what to do.
zefir738 said:
It's now bootlooping like crazy. It'll turn on for like 5 minutes and then go right back to bootlooping. My USB port is kinda screwy so it's hard to odin anything. I'm at a loss for what to do.
Click to expand...
Click to collapse
I had boot looping problems several times now. For me, it's always been sticky power button. One time, I forgot it had that problem at work and looped for 30 minutes. I just take out the battery for about an hour, then get the power button unstuck. My button gets stuck at the bottom of the button, so I can normally mess with the top part to fix it.
So the issue has escalated even further now. It is a sticky power button, i believe, but now when the phone tries to turn on it shows both samsung logos and then shuts right back off and refuses to turn on again unless i do a battery pull...I'm not even sure if it's turning off, actually. It turns on immediately after inserting a battery into the device. But right now I have a fancy brick.
Definitly a power button issue
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Similar Issue
My phone started doing a crazy bootloop just out of the blue last night. I have never had a problem. I took the battery out to put my memory card back in. I'd been using it for my digital camera. This is not out of the ordinary. I do it all the time. But after I replaced the card, battery and cover it started this continuous boot loop. Sometimes it will go to the main screen and allow me to perform some functions, but then it goes right back to the bootloop. I am running the Padawan JB rom. I did the complete wipe, factory reset and re-flash. But it still did the bootloop. The only time it does NOT exhibit this issue is when the phone is on the charger. Then and only then it works perfectly. Is it the battery? Why will it bootloop without the charger and work fine when on the charger?
It is probably your battery
cayjominara said:
My phone started doing a crazy bootloop just out of the blue last night. I have never had a problem. I took the battery out to put my memory card back in. I'd been using it for my digital camera. This is not out of the ordinary. I do it all the time. But after I replaced the card, battery and cover it started this continuous boot loop. Sometimes it will go to the main screen and allow me to perform some functions, but then it goes right back to the bootloop. I am running the Padawan JB rom. I did the complete wipe, factory reset and re-flash. But it still did the bootloop. The only time it does NOT exhibit this issue is when the phone is on the charger. Then and only then it works perfectly. Is it the battery? Why will it bootloop without the charger and work fine when on the charger?
Click to expand...
Click to collapse
The Note won't run without a proper battery installed. I had the problem where I swapped out my dead battery for a fully charged one (I do this everyday) and all of a sudden it kept bootlooping.I spent a few hours, when I got home, flashing it back to stock etc to no avail. I could get into download mode, and download to my hearts content but when I tried to boot the phone, it looped. Samsung, samsung, samsung....
I swapped back my, now charged, spare and BAM it booted into stock android no problem. I think my first (stock samsung battery actually) is finished. Or at least has some serious issues, and the phone refuses to boot with it in but my spare (Anker battery) works fine.
I hope this works for you's, it did for me
---------- Post added at 03:27 AM ---------- Previous post was at 03:25 AM ----------
Also, if I had just charged my phone using my working battery, I would have saved myself some serious grief, and hours wasted. Here's to hoping you don't too!
There's no need for n extensive backstory because rooting, flashing, etc I am pretty familiar with, having first rooted the old HTC Thunderbolt.
Now here's what happened:
I have quite a few roms for the S4 but the BoneStock 1.1.4 rom by Andybones always kept bringing me back. I pretty much settled for that one as my dail driver and kept it so for at least 2 months.
Recently in the past week i started getting notifications on my internal sys memory almost out. So i check and realize that my Google Play Music is almost at 6 gb, so I decide to wipe my entire phone just to give it a fresh new flash. Flash goes well, fresh install. I hardly have the time to let my phone die, so I usually just charge it regardless (I have a 5200 mAh extended battery) but this time I decided to let it die. Once it did, i put it to charge immediately and thats when i noticed something was wrong. It was stuck at the battery logo, the animated one that charges while your phone isn't on yet? Well the circle that spins and sort of 'detects' how much battery is left is stuck there. Even if i disconnect my charger it stays there.
So i did what's natural and battery pulled. Did that, reconnected my phone, still the same thing. Now i tried multiple times to get it to turn on and what not but it won't. It gets stuck at the samsung boot logo, no idea why.
So i've decided to call it a night (3 am here, work in the afternoon) and hopefully this thread gets seen by someone who knows how to deal wth this.
TL;DR Clean re-flash of the same daily driver (BoneStock 1.1.4) and let my phone die because I realize I never let it die. Once it does, it get stuck at both the Samsung boot logo, or the animated battery charge circle. I tried accessing recovery, and while I see the little blue message top left hand corner, it just seems to shut itself off, and boot back up only to be stuck again. I have no idea what happeend, I never mess with system functions or any thing of that sort.
The only real solution I see if restoring to stock firmware through Odin? Hopefully that will work, but anyone else experience this before? or something similar and can shed some light on this weird situation?
Thanks in advance!
EDIT: I apologize for the bad grammar, I've been trying to figure this out for the past 2 hours, and it's very late right now.
FriendlyNeighborhoodEnt said:
There's no need for n extensive backstory because rooting, flashing, etc I am pretty familiar with, having first rooted the old HTC Thunderbolt.
Now here's what happened:
I have quite a few roms for the S4 but the BoneStock 1.1.4 rom by Andybones always kept bringing me back. I pretty much settled for that one as my dail driver and kept it so for at least 2 months.
Recently in the past week i started getting notifications on my internal sys memory almost out. So i check and realize that my Google Play Music is almost at 6 gb, so I decide to wipe my entire phone just to give it a fresh new flash. Flash goes well, fresh install. I hardly have the time to let my phone die, so I usually just charge it regardless (I have a 5200 mAh extended battery) but this time I decided to let it die. Once it did, i put it to charge immediately and thats when i noticed something was wrong. It was stuck at the battery logo, the animated one that charges while your phone isn't on yet? Well the circle that spins and sort of 'detects' how much battery is left is stuck there. Even if i disconnect my charger it stays there.
So i did what's natural and battery pulled. Did that, reconnected my phone, still the same thing. Now i tried multiple times to get it to turn on and what not but it won't. It gets stuck at the samsung boot logo, no idea why.
So i've decided to call it a night (3 am here, work in the afternoon) and hopefully this thread gets seen by someone who knows how to deal wth this.
TL;DR Clean re-flash of the same daily driver (BoneStock 1.1.4) and let my phone die because I realize I never let it die. Once it does, it get stuck at both the Samsung boot logo, or the animated battery charge circle. I tried accessing recovery, and while I see the little blue message top left hand corner, it just seems to shut itself off, and boot back up only to be stuck again. I have no idea what happeend, I never mess with system functions or any thing of that sort.
The only real solution I see if restoring to stock firmware through Odin? Hopefully that will work, but anyone else experience this before? or something similar and can shed some light on this weird situation?
Thanks in advance!
EDIT: I apologize for the bad grammar, I've been trying to figure this out for the past 2 hours, and it's very late right now.
Click to expand...
Click to collapse
I would tend to agree odin the full wipe stock image back and start over
FriendlyNeighborhoodEnt said:
There's no need for n extensive backstory because rooting, flashing, etc I am pretty familiar with, having first rooted the old HTC Thunderbolt.
Now here's what happened:
I have quite a few roms for the S4 but the BoneStock 1.1.4 rom by Andybones always kept bringing me back. I pretty much settled for that one as my dail driver and kept it so for at least 2 months.
Recently in the past week i started getting notifications on my internal sys memory almost out. So i check and realize that my Google Play Music is almost at 6 gb, so I decide to wipe my entire phone just to give it a fresh new flash. Flash goes well, fresh install. I hardly have the time to let my phone die, so I usually just charge it regardless (I have a 5200 mAh extended battery) but this time I decided to let it die. Once it did, i put it to charge immediately and thats when i noticed something was wrong. It was stuck at the battery logo, the animated one that charges while your phone isn't on yet? Well the circle that spins and sort of 'detects' how much battery is left is stuck there. Even if i disconnect my charger it stays there.
So i did what's natural and battery pulled. Did that, reconnected my phone, still the same thing. Now i tried multiple times to get it to turn on and what not but it won't. It gets stuck at the samsung boot logo, no idea why.
So i've decided to call it a night (3 am here, work in the afternoon) and hopefully this thread gets seen by someone who knows how to deal wth this.
TL;DR Clean re-flash of the same daily driver (BoneStock 1.1.4) and let my phone die because I realize I never let it die. Once it does, it get stuck at both the Samsung boot logo, or the animated battery charge circle. I tried accessing recovery, and while I see the little blue message top left hand corner, it just seems to shut itself off, and boot back up only to be stuck again. I have no idea what happeend, I never mess with system functions or any thing of that sort.
The only real solution I see if restoring to stock firmware through Odin? Hopefully that will work, but anyone else experience this before? or something similar and can shed some light on this weird situation?
Thanks in advance!
EDIT: I apologize for the bad grammar, I've been trying to figure this out for the past 2 hours, and it's very late right now.
Click to expand...
Click to collapse
When you see the blue text for recovery do you continue to hold the buttons down until you see the recovery screen? If you take your fingers off it will do what your describing. If you can get into recovery reflash your ROM.
Sent from my Nexus 7 using XDA Premium 4 mobile app