So the past 2 days I've had an interesting problem, with even more interesting results.
Both mornings I've tried to use my GPS and it just hangs on trying to connect to it. The GPS says it's on, and I can toggle it off and back on again but it never finds any sats.
Yesterday I reboot the phone and it takes a while to boot the phone back up (most like the first time you boot after a fresh install), and when the phone came back online the GPS worked but all my bluetooth pairings were gone.
Today I have the same GPS problem so I reboot again, and again it takes a while to boot and so far I still have my bluetooth pairings, but I've been unable to connect to the devices, all my sound settings are back to the defaults, when I hold down the power button now the only option I have is Power Off, nothing else, when my screen times out and I hit power to bring it back on it goes right back to wherever I was, I don't see the lock screen anymore. And to top it all off my home button and my search button do not work.
What a mess, this phone is getting worse by the day, I'm actually starting to regret the purchase. I guess it's time to call it in and see what they say.
Edit: Forgot to add all my SMS messages were deleted as well.
Rooted? Have you done anything to it? That's definitely not normal but I guess you know that
Ya it's rooted and has nvflashed clockworkmod recovery installed. Rooted the day I got the phone and clockworkmod recovery has been installed for about a week.
I just tried clearing the cache partition, wiping Dalvik Cache, fixing permissions, and no change. Running a full backup via Titanium Backup now before I try a factory reset to see if that fixes it.
If that doesn't do it I'll try restoring a backup image from last week.
gohawks1 said:
Ya it's rooted and has nvflashed clockworkmod recovery installed. Rooted the day I got the phone and clockworkmod recovery has been installed for about a week.
I just tried clearing the cache partition, wiping Dalvik Cache, fixing permissions, and no change. Running a full backup via Titanium Backup now before I try a factory reset to see if that fixes it.
If that doesn't do it I'll try restoring a backup image from last week.
Click to expand...
Click to collapse
I would guess it's not the phone but the CWM made the mess. You probably want to try factory reset.
My Bluetooth settings and profiles randomly appear and disappear and I'm bone stock.
Well, factory reset got all my buttons working again, and my screen locks again. Since I'm back to stock now and have to re-setup everything now I think I'll go try out the Eaglesblood ROM and see how that goes.
G2x appears to be stuck in a boot cycle. After completely draining its battery, it began to happen. Ive tried charging while its off and it still happens. Its gets to the lock screen and it tuns off again. Stock rom, rooted, nv flash. Help..
When I had this problem on the gb leak I had to unlock as soon as it showed up. I switched to bionix as soon as it was released and it hasn't happened since. Might be an app causing the problem though.
Sent from my LG-P999 using XDA Premium App
Did you make a backup after you flashed clockworkrecovery? If so than retore it and you should boot fine. If you didnt make a backup then boot into recovery and do a factory reset.
REG, I have clockwordmod and I did a backup of my stock, but I think I did not have sufficient space on my SD card, so when I did the restore it succeeded, but when I rebooted my phone it's stuck on LG logo, do I have to reboot in recovery and do a factory reset?
Things to try
1 Factory reset in cwm
2 Load CWM internal recovery via nvflash (since you seem to have a small microsd)
3 Load another rom or nandroid back to stock again of your internal mem
I don't want to screw it up, would factory reset work for me in cwm?
It'll just wipe all your apps/cache. If that doesn't load correctly, then you got something wonky in either your boot or system.
Okay, so if that doesn't work, how can I get passed the LG reboot?
Mikeglongo said:
Okay, so if that doesn't work, how can I get passed the LG reboot?
Click to expand...
Click to collapse
I already told you what to do. Look at what I wrote for options 2 and 3.
Edit: I actually told the OP what to do, but it goes for you too if you are in the same situation.
This happened to me today while I was out getting my car fixed! I was playing the new free game from amazon when it got a little hot so I let it rest, then next thing you know it was stuck doing the rebooting cycle. I was pretty pissed since I really raved earlier about how good this phone was until it struck me all the sudden.
I was at costco when this was still happening and showed it at the kiosk and asked if I could get a new another model since the G2X was making me pull my hair and basically I just have to bring the box in and they will replace it with the phone of my choice. Hoping they have sensation before the end of the month because this piece of brick is going. In the end I had to press down on the volume and power at the same time to LOSE ALL MY DATA to do a hard reset.
I don't care what people say about this phone and how great it is. I literally in the middle of costco curse the crap out of this phone!
Titanium and nandroid backup is definitely your friend.
So here is a quick rundown of what happened:
-DL Beats audio, opened it, it was supposed to restart my phone, but it froze it.
-Could not power off or reset it, had to pull battery
-Was then stuck on the 4G LTE rainbow and would not load. Tried pulling battery nothing.
-Went into recovery mode and tried loading, nothing happened and I read someone say the only way out of it was to wipe everything and start over, so I wiped Data and Cache and Dalvik Cache with Clockwork. Nothing happens.
-Finally I Odin it supposedly back to stock. Hooray I can get into my phone, weird thing is all of my apps are there, email is set up, contacts are there with pics from FB, syncmypix, etc. It even retained the fact that I had disabled the stupid ongoing Wi-Fi notification. Just the homescreens are blank again.
-I never made a CWM backup, I think I made a Titanium backup, I know I used MyBackupRoot (the one that is a life preserver). That being said I thought I wiped everything in CWM. It said it had formatted the internal and external SD.
Question is should I go ahead and try to wipe everything clean again?
Am I going to run into issues using my phone how it is?
Should I back it up and then load a recovery from this or would that be pointless?
Or do I leave it alone and consider myself lucky?
Thank you and by no means am I a developer or anything, just getting back into android after 2 years on iOS and apparently know just enough to get myself into trouble.
If everything is working fine then you sgould be good. You must haved had the restore thing checked or verizon backup crap restored your stuff. When you odin that will flash the file system img so there is no way that your data survived
Did you check the md5 on the beats audio thing before you flashed it? Cause i have ran that fine.
Sent from my CleanRom'd Galaxy SIII
Hey guys. I've been around since the OG Droid, and I've never posted because I've been able to find the information by searching usually. But now I have a problem that I haven't been able to solve, and I was hoping someone could puzzle it out.
Right now I have a Nexus 5. I got it at launch and it's been perfect, with none of the issues others have had that required RMA. I unlocked the bootloader when I got it and loaded TWRP and rooted, but left it stock beyond that. About a week or so ago, I rebooted into recovery. While I was there, out of habit, I cleared cache and Dalvik. The thing is, it took 5-10 minutes to clear, and during that time I remembered that i had ART enabled. Now, I know others have had trouble with TWRP messing them up on a wipe, but this is where it gets interesting.
I rebooted when TWRP finished wiping. The boot animation spins the balls in once, then on the second time, there is color bleed forming a line across screen on the top and bottom of the boot animation. Again it spins, and it's fine, and then it does it again. Every second spin of the boot animation.
Eventually it booted in and I used the phone. An hour later, I got some force closes, it locked up, and then it rebooted into a bootloop. With the boot animation bleeding every second spin. When I got sick of that, I started trying to fix it by flashing factory images, locking and unlocking bootloader, fastboot erasing cache, userdata and system, fastboot formatting cache, userdata and system, trying TWRP again and wiping, trying CWM and wiping, wiping in stock recovery, anything and everything. I don't know how this is lasting past flashing factory images after an erase or a format, but every time I try to boot my Nexus 5, it either gets caught in a bootloop with varying amounts of boot animation graphics glitches, or it boots into Android and then after I spend a few hours setting up again, it will randomly hit me with graphical glitches in the OS or reboot, and then I'm stuck in the exact same boot loop.
Does anyone have any ideas that I haven't tried? I've done all of these multiple times, checked MD5's and SHA's, used different downloads of factory images, applied or not applied the update to 4.4.1, and nothing seems to work. Sometimes it's right away, sometimes it takes hours or even a day, but eventually I end up with force closes and a boot loop with bleeding graphics.
Thanks in advance for any possible help. I'll sit here quietly and wait for someone to tell me to just flash the factory image.
Kal5el said:
Hey guys. I've been around since the OG Droid, and I've never posted because I've been able to find the information by searching usually. But now I have a problem that I haven't been able to solve, and I was hoping someone could puzzle it out.
Right now I have a Nexus 5. I got it at launch and it's been perfect, with none of the issues others have had that required RMA. I unlocked the bootloader when I got it and loaded TWRP and rooted, but left it stock beyond that. About a week or so ago, I rebooted into recovery. While I was there, out of habit, I cleared cache and Dalvik. The thing is, it took 5-10 minutes to clear, and during that time I remembered that i had ART enabled. Now, I know others have had trouble with TWRP messing them up on a wipe, but this is where it gets interesting.
I rebooted when TWRP finished wiping. The boot animation spins the balls in once, then on the second time, there is color bleed forming a line across screen on the top and bottom of the boot animation. Again it spins, and it's fine, and then it does it again. Every second spin of the boot animation.
Eventually it booted in and I used the phone. An hour later, I got some force closes, it locked up, and then it rebooted into a bootloop. With the boot animation bleeding every second spin. When I got sick of that, I started trying to fix it by flashing factory images, locking and unlocking bootloader, fastboot erasing cache, userdata and system, fastboot formatting cache, userdata and system, trying TWRP again and wiping, trying CWM and wiping, wiping in stock recovery, anything and everything. I don't know how this is lasting past flashing factory images after an erase or a format, but every time I try to boot my Nexus 5, it either gets caught in a bootloop with varying amounts of boot animation graphics glitches, or it boots into Android and then after I spend a few hours setting up again, it will randomly hit me with graphical glitches in the OS or reboot, and then I'm stuck in the exact same boot loop.
Does anyone have any ideas that I haven't tried? I've done all of these multiple times, checked MD5's and SHA's, used different downloads of factory images, applied or not applied the update to 4.4.1, and nothing seems to work. Sometimes it's right away, sometimes it takes hours or even a day, but eventually I end up with force closes and a boot loop with bleeding graphics.
Thanks in advance for any possible help. I'll sit here quietly and wait for someone to tell me to just flash the factory image.
Click to expand...
Click to collapse
What kind of FC's? Random apps you have on your phone or specific apps? Also, do you have any kinds of system mods or complete stock? Do the weird graphical glitches on the bootanimation happen on the boot right after you flash the factory images? Or subsequent boots after the OS graphical glitches start?
As for right now, try running a factory image without installing anything apart from apps that come stock (don't install anything from the Play Store). If you can't live without some apps, try keeping them to the top 100 downloaded apps (ie. ones that have huge userbases and most definitely do not cause system issues).
Reason I say this is because the only three reasons I can think of are 1) app you have installed doesn't play nicely with stock Kitkat 2) something borked your EFS partition 3) your GPU is screwed.
thattypicalnerd said:
What kind of FC's? Random apps you have on your phone or specific apps? Also, do you have any kinds of system mods or complete stock? Do the weird graphical glitches on the bootanimation happen on the boot right after you flash the factory images? Or subsequent boots after the OS graphical glitches start?
As for right now, try running a factory image without installing anything apart from apps that come stock (don't install anything from the Play Store). If you can't live without some apps, try keeping them to the top 100 downloaded apps (ie. ones that have huge userbases and most definitely do not cause system issues).
Click to expand...
Click to collapse
Thanks for the reply.
The force closes are Google Search, or other Google stuff. I had the build.prop edited for 400 LCD density before this all started, but I haven't changed it back on subsequent flashes. So it is completely stock, not even rooted, and sometimes not even a custom recovery. 100% stock. The glitches happen on a clean flash from factory images, immediately on first boot. They get worse on subsequent boots after OS glitches start. In terms of what they look like, they are red or blue or white. Never other colors. On boot, they form dash lines bordering the boot animation. On the OS, they form lines above the default Google folder or vertical or horizontal lines mostly.
I've tried running just factory image with nothing installed except stock. I get the same results. Either I get glitches and force closes followed by a reboot right away, or it starts within a few hours of booting. If it reboots and gets back to OS without boot looping, the glitches in OS will be worse, and it will reboot into boot loops within a few minutes.
I still have my GNex, so I can afford to keep this phone stock until I resolve this. But it is basically unusable, and I don't want to RMA since I seem to have gotten one of the good ones, you know? This has to be a software problem, possibly a partition problem caused by TWRP. I was paying close attention to Metal_Head's thread, but he resolved his problems by wiping in TWRP, and that hasn't worked for me.
Kal5el said:
Thanks for the reply.
The force closes are Google Search, or other Google stuff. I had the build.prop edited for 400 LCD density before this all started, but I haven't changed it back on subsequent flashes. So it is completely stock, not even rooted, and sometimes not even a custom recovery. 100% stock. The glitches happen on a clean flash from factory images, immediately on first boot. They get worse on subsequent boots after OS glitches start. In terms of what they look like, they are red or blue or white. Never other colors. On boot, they form dash lines bordering the boot animation. On the OS, they form lines above the default Google folder or vertical or horizontal lines mostly.
I've tried running just factory image with nothing installed except stock. I get the same results. Either I get glitches and force closes followed by a reboot right away, or it starts within a few hours of booting. If it reboots and gets back to OS without boot looping, the glitches in OS will be worse, and it will reboot into boot loops within a few minutes.
I still have my GNex, so I can afford to keep this phone stock until I resolve this. But it is basically unusable, and I don't want to RMA since I seem to have gotten one of the good ones, you know? This has to be a software problem, possibly a partition problem caused by TWRP. I was paying close attention to Metal_Head's thread, but he resolved his problems by wiping in TWRP, and that hasn't worked for me.
Click to expand...
Click to collapse
"One of the good ones"? You clearly don't have "one of the good ones".
I think this doesn't have anything to do with anything you might have done wrong, I think the phone needs to be RMA...can you relock it?
Kal5el said:
Thanks for the reply.
The force closes are Google Search, or other Google stuff. I had the build.prop edited for 400 LCD density before this all started, but I haven't changed it back on subsequent flashes. So it is completely stock, not even rooted, and sometimes not even a custom recovery. 100% stock. The glitches happen on a clean flash from factory images, immediately on first boot. They get worse on subsequent boots after OS glitches start. In terms of what they look like, they are red or blue or white. Never other colors. On boot, they form dash lines bordering the boot animation. On the OS, they form lines above the default Google folder or vertical or horizontal lines mostly.
I've tried running just factory image with nothing installed except stock. I get the same results. Either I get glitches and force closes followed by a reboot right away, or it starts within a few hours of booting. If it reboots and gets back to OS without boot looping, the glitches in OS will be worse, and it will reboot into boot loops within a few minutes.
I still have my GNex, so I can afford to keep this phone stock until I resolve this. But it is basically unusable, and I don't want to RMA since I seem to have gotten one of the good ones, you know? This has to be a software problem, possibly a partition problem caused by TWRP. I was paying close attention to Metal_Head's thread, but he resolved his problems by wiping in TWRP, and that hasn't worked for me.
Click to expand...
Click to collapse
HIGHLY doubt its a software issue at this point. Considering your phone is completely stock, the crashes are unrelated to the phone app, that takes out app interference/EFS issues. Also, considering it happens on first boot, 99.99% sure it's hardware. Relock and send it back to Google. If you really want to, try CWM and see if that does anything, but I doubt it. In my experience, CWM causes more trouble than TWRP. Computers are complex little devices, it could be a bad CPU that has a small sector of the transistors not working or something like that. Bad RAM even?
So you guys think it's a hardware issue? It's possible, I guess. But it started after TWRP messed up on wiping Dalvik, so I figured it was a partition problem. I can relock it, I'll just have to reset the tamper flag. Was really hoping this was a fixable software problem.
I think you don't have the latest TWRP, which causes some issues on cache partition, and takes ages to wipe
2.6.3.4 is the latest
I'm running 2.6.3.4 TWRP. Thanks for the suggestion though.
Okay, just posting the solution in case this happens to anyone else. Wiping in stock recovery, CWM, or TWRP didn't work. Fastboot erase, fastboot format, and fastboot oem lock/unlock didn't work. Factory images didn't work, with multiple downloads and md5 checking. What ended up somehow fixing it after trying everything I could think of was pretty simple.
In the Android OS, in settings, under backup and reset, I clicked reset. That's it. So far, graphical glitches gone. It's been almost 2 days, far longer than it's gone without a bootloop since it started these shenanigans.
No idea why recovery and fastboot and all that business didn't work. Just posting the solution for those who come after.
Funny thing is the reset in android settings uses recovery
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
I know, I can't figure it out. It rebooted into recovery exactly like I had done before, and I watched the robot's polygon spin exactly like I had done 20 times. I can't explain why it worked.
Same thing that happened to me. What I finally got done to resolve it was:
1) Completely wiped the device and I mean all partitions so there is no OS and no internal files
2) Get the refresh zip file from Google to flash the device back to stock 4.4 while in the bootloader
3) Boot up, skip the setup, place CM11 files on the phone, then turn it off, reboot to bootloader
4) Flash CWM with fastboot
5) Boot to recovery
6) Do a factory reset
7) Wipe cache
8) Install CM11 & gapps
9) Wipe cache again
10) Reboot
So far for me no more issues. I did the same steps as you when mine started acting up. Now cache wipes super fast as expected no more reboots.
Sent from my Nexus 5 using xda app-developers app
I was wrong. The reset fixed it for 2 days or so, then it started showing the same problems. Graphical glitches and rebooting. I'm RMAing it. This thread can be ignored from now on. Further discussion of this particular problem can go in ssconceptz's thread linked below.
http://forum.xda-developers.com/showthread.php?t=2547863
That sucks. Mine works great now. I'll remove the first method.
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 11:41 PM ---------- Previous post was at 11:41 PM ----------
Maybe you could try the method I show before RMA?
Sent from my Nexus 5 using xda app-developers app