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
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.
If your phone was bricked in any way, but still shows something on the screen when powered on or plugged in, try this.
1. Take out battery, put it back in. (to turn the phone fully off)
2. Don't turn it the phone on!
3. Plug the phone into your PC, do not hit the power button!
4. See if the phone shows anything on the screen
IF the phone screen does show the battery charger or something else on the screen after being plugged in without you hitting the power button, so far so good.
5. Now while it's on like this, hold the volume up and volume down buttons.
6. Hold the power button as well as the volume buttons until the screen goes black.
7. As soon as the screen goes black, let go of the power button! But DON'T let go of the volume buttons!
When done properly, this will always get you into Download mode. After that you should be able to use Odin to revert to stock, tar and instructions here:
http://forum.xda-developers.com/showthread.php?t=734475
This fixed my 'odd' bricks. Over and over again.
I'd say it's impossible to truly brick this phone.
I have been researching this most of the day, due to some testing I was doing, and the one thing I have come to realize is that this phone recovers well from "brick" it's not a true brick it's just scary. One of the posts I read, here on xda, said that unless the blue progress bar started advancing while using Odin, you can unplug, pull battery fairly safely.
davbran said:
I have been researching this most of the day, due to some testing I was doing, and the one thing I have come to realize is that this phone recovers well from "brick" it's not a true brick it's just scary. One of the posts I read, here on xda, said that unless the blue progress bar started advancing while using Odin, you can unplug, pull battery fairly safely.
Click to expand...
Click to collapse
Haha well that's exactly what happened to me. I flashed wrong with Odin and it failed halfway through, and I had no choice but to reboot the phone.
And when I did I got a truly odd screen. All I could see was a picture of a phone connected to an exclamation point connected to a laptop. That's it. Lol.
And I fixed it by doing this.
omg, i love you This totally fixed my problem XD
Everyone kept saying go to download mode, but no one ever said to "7. As soon as the screen goes black, let go of the power button! But DON'T let go of the volume buttons!"
super life saver... thanks alot
I actually did find someone else say to do that but it was out of luck as it was deeply buried. Don't remember where it was here lol
Its nice to have people who help us newbies
andershizzle said:
Haha well that's exactly what happened to me. I flashed wrong with Odin and it failed halfway through, and I had no choice but to reboot the phone.
And when I did I got a truly odd screen. All I could see was a picture of a phone connected to an exclamation point connected to a laptop. That's it. Lol.
And I fixed it by doing this.
Click to expand...
Click to collapse
Yea, last night I was messing around with the latest lag fix, but it ending up causing a lot of FC's, so I had to revert to stock a few times. I tried to make it work using ext2 and ext3, but it still wasn't stable enough. I didn't enjoy the noticeable speed increase, but it wasn't worth it since launcher pro was one of the programs that was FCing.
Anyways, so after I gave up for the 3rd time, I flashed stock using ODIN and it got stuck. I left it there for awhile with no progress and the phone's screen actually just went completely black. I pulled the battery and got the weird cell phone pointing to computer icon. I almost crapped my pants at that point. Very scary moment since I had not seen that screen before.
A quick google search for "bricked Vibrant" led me to this thread and voila! My Vibrant is alive and well again.
Thanks a bunch.
PS: After reflashing stock that many times, I still find it strange that after a fresh flash, I still get a noticeable speed boost by wiping the phone through the privacy setting. Not sure if it's a placebo effect, but I swear it makes a noticeable difference every time.
Maverick777 said:
Yea, last night I was messing around with the latest lag fix, but it ending up causing a lot of FC's, so I had to revert to stock a few times. I tried to make it work using ext2 and ext3, but it still wasn't stable enough. I didn't enjoy the noticeable speed increase, but it wasn't worth it since launcher pro was one of the programs that was FCing.
Anyways, so after I gave up for the 3rd time, I flashed stock using ODIN and it got stuck. I left it there for awhile with no progress and the phone's screen actually just went completely black. I pulled the battery and got the weird cell phone pointing to computer icon. I almost crapped my pants at that point. Very scary moment since I had not seen that screen before.
A quick google search for "bricked Vibrant" led me to this thread and voila! My Vibrant is alive and well again.
Thanks a bunch.
PS: After reflashing stock that many times, I still find it strange that after a fresh flash, I still get a noticeable speed boost by wiping the phone through the privacy setting. Not sure if it's a placebo effect, but I swear it makes a noticeable difference every time.
Click to expand...
Click to collapse
Glad I could help!
And that's intersting. I'll make sure to wipe the privacy settings. I actually haven't ever wiped them yet.
No go for me.
I used the stupid partition tool in rom manager. partitioned the internal memory not the sd card.
Saw a few others did this, and this worked for them, either right away or after flashing eugene's froyo rom then reverting back, but that rom just hangs on cache.fsd or something like that.
Trying to repartition through odin, with no download files selected right now. It does not appear to be doing anything, just set pit file, then do not turn off target in odin.
Will leave it for a bit, maybe try to flash this again, i think the issue might be deeper for me though. need kernel and everything else.
I did that but my phone locked up and now all I get is a picture of a yellow cation sign next to a little phone and pc pic.. anything I can do at this point or??
tried going into recovery and download mode but it wont let me past that screen.
Thank you so much for this, I received a replacement set 2 days ago and was playing around the the phone and I bricked it, it thought it was frozen so I pulled the batter and it bricked.
I followed your instructions and it works like a charm. What I did find though is that i can't seem you use odin on a mac even with a virtual machine. I had to use an actual PC.
tweezit said:
I did that but my phone locked up and now all I get is a picture of a yellow cation sign next to a little phone and pc pic.. anything I can do at this point or??
tried going into recovery and download mode but it wont let me past that screen.
Click to expand...
Click to collapse
This is exactly the screen I had. Follow my instructions exactly and you'll get into download mode (at least i did)
This should be made a sticky.
thank you thank you thank you
Sticky this thread.
Sent from my SGH-T959 using XDA App
Great find for all.
has anyone found a way to unbrick a flashed EU rom then the person flashed to US rom? and then the power wont come on? But the unit does get hot when plugged in?
Im trying to see if i need to jtag this thing. or if anyone had success?
Thanks
ok so my vibrant gave me the cell phone and computer screen i got it back in download mode. started odin to get it back to stock but no matter how long i let odin go nothing happens i got the files that i need for odin out of a thread on these forums and i have followed the directions to the letter and still nothing. any help some one can give would be great. thank you for your time.
How do I know if my phone is being picked up by Odin or being flashed?
did the same thing the clockwork partition wiped my internal memory
F**k!
woop guess im going to tmobile in the a.m. and playin the whole
idk what happened it wont turn on
thank god for the 14 day return policy!
I ran into "brick mode" myself 2 nights ago and could not get my phone into download mode. Any possible combo of volume key up/down and power had no effect. Just that phone exclamation point pc icon slowly blinking in the center of the screen. I did finally get it into download mode but it wasn't using any of the previously mentioned methods, so I'll add one more to the growing list to try. This one worked for me after almost 4 hours of experimenting.
BTW....my phone would never display the battery charging image when powered off and plugged in. Just this same annoying image.
Pull the battery. Put it back in. Hold the just the volume down button. Do not hold the power button. Plug in either a wall charger or USB cable. The cable will power up the phone and voila. I was in the download screen.
I also highly recommend the stock ROM from the thread
"[ROM] OFFICIAL T-Mo Vibrant JFD ODIN/Nandroid Backup Images 7/29/10 (Tested/Working)" In Vibrant > Vibrant Android Development
I tried another ROM found out on the internet and ended up with a shell that crashed and restarted every 60 seconds.
For those running into Odin stuck on a message about verifying the file system, I had no luck when the phone used COM3. I suggest moving your USB cable into different ports on your PC. Each new port will "install" a new instance of the phone using different COM ports. COM5 and COM6 both worked as I was reflashing the day away yesterday.
Today i decided to try out the nocturnal rom, but before that i had to make a backup. at the the time the phone was what i would a call luke warm so i paid no mind to it. so a few minutes later i look back at the phone and notice that the screen turned off annd the phone was now averagely hot
so i let it cool down for a bit (i thought that the phone must have shut itself off in order to make sure the internals wouldn't be damaged), then when i try to turn it on the lg logo does show up but never gets to the base roms nexus boot animation, now i'm thinking that TWRP must have drained my battery because when i usually make a backup my battery can go from 94% to 50% in a span of 7 minutes (only during backup). So i leave it to charge for 30 minutes 1 hour and then 5 hours but each time i check it still won't turn on correctly.
Now i have had this happen to me before, when i had the atrix 4g this happened and i had to buy a battery only charger to even get it to work again
but as we all know that won't work for the optimus g because you cannot take out the battery.
so i have to ask, what should i do? is there any way to fix this?
Side note: can't get into recovery (seems to shut off before it loads up, its like an infinite loop of dying and turning on again) the power button still glows while its connected giving the appearance of charging but it still never boots up all the way ( the most i can get it to is the part of recovery before going into TWRP. you know holding vol+ and seeing fastboot mode)
There is thread here someone made of disassembly. You can do a battery pull pretty easily. Never know might help.
Have you tried download mode at all BTW?
Sounds more like something was deleted then a batter problem to me. If download mode works you could try lgnpst back to stock.
The information in THIS thread might be able to help.
I can't vouch for it because I haven't experienced these problems, but the OP there seemed to get his problem fixed.
GL.
Although, looking things over, sounds like you have a different issue.
So you can get to the bootloader?
from the bootloader have you tried hitting the volume down key twice then hitting power?
That should reboot you into recovery, where you can restore something or flash stock.
Edit. Quote from FreeGee post.
To enter bootloader, hold volume UP and power.
Upon entering the bootloader, you will notice that there is no 'menu' to enter fastboot or recovery. Unfortunately, since the stars didn't align properly, we were unable to tell the new bootloader where to load the images that contain the menu from.
In light of that, you'll have to navigate the menu blind. Use the volume keys to change selection, and the power key to select.
The choices are (in order of pressing volume down):
Start - boot the phone normally [already selected]
Restart Bootloader - reboot into the bootloader
Recovery Mode - enter recovery (CWM)
Power Off - powers the phone off
So, to get to Recovery, you would press volume down twice then power.
Click to expand...
Click to collapse
bleached45 said:
The information in THIS thread might be able to help.
I can't vouch for it because I haven't experienced these problems, but the OP there seemed to get his problem fixed.
GL.
Although, looking things over, sounds like you have a different issue.
So you can get to the bootloader?
from the bootloader have you tried hitting the volume down key twice then hitting power?
That should reboot you into recovery, where you can restore something or flash stock.
Edit. Quote from FreeGee post.
Click to expand...
Click to collapse
when i try to get into TWRP it doesnt start up, same as when it trys to turn on, it seems to die before it boots fully or so to say the screen
goes from a backlit black to just black and then it doesn't come on again. (looking at thread and nothing has worked yet i'm now trying last advice in thread since my phone won't even turn on unless its connected to the charger)
also i have no idea what download mode is but since nothing seems to be working i will assume that does not work either
Edit: actually maybe i can lgnpst. all i have to do is be able to get into the bootloader right? going to try in the afternoon.
Kurodo said:
when i try to get into TWRP it doesnt start up, same as when it trys to turn on, it seems to die before it boots fully or so to say the screen
goes from a backlit black to just black and then it doesn't come on again. (looking at thread and nothing has worked yet i'm now trying last advice in thread since my phone won't even turn on unless its connected to the charger)
also i have no idea what download mode is but since nothing seems to be working i will assume that does not work either
Edit: actually maybe i can lgnpst. all i have to do is be able to get into the bootloader right? going to try in the afternoon.
Click to expand...
Click to collapse
Sorry none of that is working.
To enter download mode:
Connect phone to computer, power off, and then power on, holding down the power button and both volume buttons
Click to expand...
Click to collapse
In the FAQ section of THIS thread, it explains how to use LGNPST.
This is god's way of telling you not to mess with flashing roms on your phone. Hopefully you will learn your lesson and keep your dirty hands off your phone, it just wants to be left alone!!!!!!!
sent from my Nexus 4 using xda premium
jamesc760 said:
This is god's way of telling you not to mess with flashing roms on your phone. Hopefully you will learn your lesson and keep your dirty hands off your phone, it just wants to be left alone!!!!!!!
sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I can't tell if you're being serious or not
to that nay sayer
jamesc760 said:
This is god's way of telling you not to mess with flashing roms on your phone. Hopefully you will learn your lesson and keep your dirty hands off your phone, it just wants to be left alone!!!!!!!
sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
There is beauty in god given stock but there is TRUE beauty in the purgatory that is flashing roms and making it all your own!!!!!!:laugh:
last resorts
well the lgnpst did work but the battery still won't charge, so if i can't get a replacement i'll try this http://forum.xda-developers.com/showthread.php?t=2039707 and see if i can charge it.
now a different question...
does anyone know if i can exchange the phone at an att store if i bought it from amazon or would i have to go through amazon?
and exactly how does that work?
Kurodo said:
well the lgnpst did work but the battery still won't charge, so if i can't get a replacement i'll try this http://forum.xda-developers.com/showthread.php?t=2039707 and see if i can charge it.
now a different question...
does anyone know if i can exchange the phone at an att store if i bought it from amazon or would i have to go through amazon?
and exactly how does that work?
Click to expand...
Click to collapse
Amazon is actually VERY easy to deal with, and a HELL of a lot easier than AT&T. They'll ship you out a replacement, you send the old one back once you receive the new one. Done. You MAY have to send the old one first, but if you let them put a hold on a credit card, I believe they'll definitely ship first.
You may be able to fix this by holding down both the volume down and power buttons for at least 45 seconds after you plug in the phone.
so
STEP 1: PLUG IN PHONE
STEP 2: PRESS AND HOLD THE VOLUME DOWN AND POWER KEYS TOGETHER FOR AT LEAST 45 SECONDS
STEP 3: LEAVE PLUGGED IN FOR TEN MINUTES
STEP 4; BOOT INTO RECOVERY MODE, WIPE BATTERY STATS, WIPE CACHE, AND WIPE DALVIK, THEN REBOOT TO SYSTEM FROM WITHIN RECOVERY.
LAST PART IS TO PREVENT IT FROM HAPPENING AGAIN.
I've gone the three of these for various reasons and some times lgnpst pretends to work and you need to do it again. And some times you need to wipe data boot back into download and do it again. This phone is retarded.
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
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.