BG: Running Eclipse 1.4 with PBJ kernel. Yesterday I used my phone til it ran out of battery. Out for a few hours and end up at my parents for dinner. Brought the USB cord so i plug it into my Mom's laptop to let it charge over night. I take it off the charger this morning and turn it on...
First thing that happens is it wants me to set up a google account "touch the android" as if I had wiped data. I hit skip, see that one account is still connected, and all my apps are in the drawer. Most of them F/C when I try to run them. So I decide to restore from CWM. Went back to Tweakstock (Guess I never got around to backing up on eclipse) and then went back to CWM and flashed Eclipse again. Now, some android.acore keeps f/cing, as well as all gapps, google framework junk, the eclipse keyboard if i switch from swype, my contacts, etc. Titanium backup doesn't find root. Superuser seems to be working. So I try flashing eclipse again to no avail.
I noticed after this morning that Verizon data widget wanted to be updated. Looked into that a bit and it seems it MAY be to blame, God knows how...
Anyone experience this before? What should my next steps be. I'm thinking back to stock through odin w/ PIT file and work from there?
Tazer2death said:
BG: Running Eclipse 1.4 with PBJ kernel. Yesterday I used my phone til it ran out of battery. Out for a few hours and end up at my parents for dinner. Brought the USB cord so i plug it into my Mom's laptop to let it charge over night. I take it off the charger this morning and turn it on...
First thing that happens is it wants me to set up a google account "touch the android" as if I had wiped data. I hit skip, see that one account is still connected, and all my apps are in the drawer. Most of them F/C when I try to run them. So I decide to restore from CWM. Went back to Tweakstock (Guess I never got around to backing up on eclipse) and then went back to CWM and flashed Eclipse again. Now, some android.acore keeps f/cing, as well as all gapps, google framework junk, the eclipse keyboard if i switch from swype, my contacts, etc. Titanium backup doesn't find root. Superuser seems to be working. So I try flashing eclipse again to no avail.
I noticed after this morning that Verizon data widget wanted to be updated. Looked into that a bit and it seems it MAY be to blame, God knows how...
Anyone experience this before? What should my next steps be. I'm thinking back to stock through odin w/ PIT file and work from there?
Click to expand...
Click to collapse
Sounds like something corrupted in /system area, that's why you back to factory setup screen. To prevent long term issue, I would do the clean slate back to stock with PIT file. Make sure you follow instruction carefully with PIT file.
I couldn't figure anything else out so I went ahead back to stock, and as it's been a while, rooted following a pretty awesome guide at chargeforums.
Still on stock rom but everything seems to be running smooth. From here I will cwm back to eclipse and see how it goes over the next few days. I really have no idea what happened but the last person to touch my phone before it died was my gf so I've had some fun picking on her for breaking my phone. Literally nothing was working earlier so she thought she really messed it up bad.
Tazer2death said:
I couldn't figure anything else out so I went ahead back to stock, and as it's been a while, rooted following a pretty awesome guide at chargeforums.
Still on stock rom but everything seems to be running smooth. From here I will cwm back to eclipse and see how it goes over the next few days. I really have no idea what happened but the last person to touch my phone before it died was my gf so I've had some fun picking on her for breaking my phone. Literally nothing was working earlier so she thought she really messed it up bad.
Click to expand...
Click to collapse
After you fixed your phone, she probably think you're a smart guy and give you more...."love".
Related
I'm new to these forums so I'm not really sure if this is a known problem but I'll give you guys a little background of what lead to my issue.
So I rooted my Droid X last night using SuperOneClick and worked fine. Downloaded a bunch of root apps including ROM Manager and Bootstrap. I backed up my phone using bootstrap perfectly fine and everything was working good until this afternoon when I did another backup after getting rid of a few old unused apps. During the back up process, my phone crashes and goes into the reboot screen. It stayed on the M logo for a good half hour. I finally pulled the battery and loaded into recovery mode. I attempted to restore my backup from the previous night multiple times but it kept freezing in the middle of the process. After several battery pulls (I know not a very good idea but i didn't know what else to do) my X finally turned on normally but it was like a brand new phone. I don't know much about the backup process but from what I've read, my phone is supposed to be just like how it was, now restored.
I've linked my google account so I can get everything back, my photos/videos are still there and from the apps that I've tried to use, they're like the way they were (haven't tried any games yet because theyre still downloading).
However I'm tempted to try another attempt at loading my back up now that I'm home but is it a good idea? Or is linking google accounts the way bootstrap backs up apps? My phone is currently still downloading all my old apps that i got off the marketplace so I might just wait until thats finished, then maybe think about.
BTW: For some reason my phone can't connect to 3G either. Earlier today it was fine and I was even surprised that I got 3G at work which I never get. But half way through the day it just went back to normal phone connection. I thought it was because of my work but now that I'm back at my house I still don't have 3G connection. Is this an issue with my phone or do you think it's just my connection?
Thanks so much for the help
Hello, everyone.
Ok I'll explain the situation, then explain how it might of happened.
My phone will not turn on. It is stuck at the white at&t screen.
How It Happened:
I went out camping with family. We decided to go boating, No I didn't dunk the phone in lake water. I was listening to music on the boat, I noticed that an error message kept coming up. It said something along the lines of "com.android.phone has stopped unexpectedly, please try again." I would get this message every other second. So I booted the phone into clockwork recovery, hoping to recover an old back up of my system. It didn't work, I got some other error message saying it couldn't recover. Being desperate, I was like, "I'll just flash a different ROM!" I tried flashing cognition. It said it installed correctly. I was stoked! I rebooted my phone. I noticed it still showed the cyanogenmod 7 boot animation, so of course it didn't flash the other ROM. I decided to reboot my phone again. This time instead of turning all the way on, it stopped at the cyanogenmod animation, then restarted. It looks as if, right before it would restart it looked like a "loading screen" in clockwork recovery. It rebooted continually for the next 10 minutes until I took the battery out. I then tried to recover the phone again. Then I rebooted my phone, but then it froze at the at&t white screen. I left it like that for around 20 minutes. As we were coming back to the dock, I decided that I had enough messing with it and turned it off.
Any ideas. Did I do what they call "Bricking" and if so, what can I do to fix it?
And if not what do you think I did?
Thanks for help. I am getting a new phone in 2 days.
Btw, I am running through AT&T, and I own a sumsung captivate.
Well, the phone does sound like it has a pretty solid issue, I would have assumed that the flashing would have fixed it. There are probably other things you can try to get it running, but honestly after everything you've done, I would just Odin the phone. There are plenty of posts in the dev forums about running Odin. You download it on PC, plug the phone into download mode, click the button in Odin and after a bit, bam you are back to stock 2.1 like it's right outta the box. Then the obvious, root/rom. Unless you are desperate to get data off the phone I would just use Odin.
Someone may have a better answer, but weird stuff like that, I don't bother with trial and error. Just make sure if you do go with the Odin route, follow instructions, or you definitely WILL brick the phone. If you need the link because you actually can't find it on the forums (sigh) then I can send it tomorrow, it's bookmarked on another PC. Hope this helps
DanBroChill said:
Well, the phone does sound like it has a pretty solid issue, I would have assumed that the flashing would have fixed it. There are probably other things you can try to get it running, but honestly after everything you've done, I would just Odin the phone. There are plenty of posts in the dev forums about running Odin. You download it on PC, plug the phone into download mode, click the button in Odin and after a bit, bam you are back to stock 2.1 like it's right outta the box. Then the obvious, root/rom. Unless you are desperate to get data off the phone I would just use Odin.
Someone may have a better answer, but weird stuff like that, I don't bother with trial and error. Just make sure if you do go with the Odin route, follow instructions, or you definitely WILL brick the phone. If you need the link because you actually can't find it on the forums (sigh) then I can send it tomorrow, it's bookmarked on another PC. Hope this helps
Click to expand...
Click to collapse
No, I got Odin3. Thanks, I got it back to stock. I got my new Cappy today. I'm sending my old one to AT&T and all that. Thanks anyways.
My phone will not switch on. The battery is fully charged, i checked it with a reliable voltmeter and it read 3.7 volts. I put a different working battery from a different working sensation and still nothing. The led does not come on when i connect it to the charger and i am losing patience.
The back story is, yesterday i flashed SENSEay onto my phone and all was good. I used titanium to restore the apps, no data, I made a backup and left the phone alone for a while. I decided later on that i was going to play a game of samurai vengeance, but to do so i had to install chainfire3d. I did this and tried to install the beta part of chainfire, unfortunately this caused a bootloop. I pulled the battery and went into recovery to restore, restore went fine and my phone was back to working. Before i went to bed i put my phone on charge and when i woke this morning the bugger would not switch on. Because it has happened during the night i have no idea what occurred to kill it, all i do know is that no-one else has played with it. What the hell has happened to my phone?
All help will be gratefully accepted.
Your in the same boat as me buddy
I started going through the same issue yesterday, finally gave up and called HTC. Your phone (like mine) should still be under factory warranty with HTc so they are willing to fix it for free. I am gonna send mine in but am hesitant because idk if they will be able to tell if its rooted or not.
I have no idea if they will be able to tell if its rooted. What have you tried to get your phone to power on? Most threads with similar problems seem to be battery related, but thats not the case with my phone.
big_smurf said:
I have no idea if they will be able to tell if its rooted. What have you tried to get your phone to power on? Most threads with similar problems seem to be battery related, but thats not the case with my phone.
Click to expand...
Click to collapse
This happened to me too, I tried all my batteries just to make it power up but it won't so o just called tmobile and they sent me a new one. Hope they will not charge me because the phone I sent back for.replacement.is rooted and flashed with arhd.
Sent from my HTC Sensation 4G using xda premium
i it wont turn on your good cuz it wont turn on for them they just force phone to d/l mode and reinstall if it will take it them resell as refreb
I have got myself a new phone and the old one is history. Thanks to everyone that helped but this thread is more dead than the old phone. Might as well close it!
Hello everyone, I did do a search for my issue but found no solutions so I'm hoping someone out there can help me.
Phone: Samsung Infuse 4G on AT&T running Cyanogenmod 7
I just very recently started messing around with custom ROMs so bear with me. I may use some wrong terminology out of sheer noobness. Feel free to correct me.
A few days ago I put my phone to stock Froyo using GTG's ultimate un-brick. I did this because I wanted a fresh start. I didn't care If I lost my apps, I wanted to start over anyways.
I then rooted using SuperOneClick, and installed CWM using ROM Manager.
I then flashed Cyanogenmod 7 to my phone.
Everything was going great. Pretty much everything worked on the ROM and I was having a great time playing around with it and getting everything set up how I liked it....
until this morning.
I woke up, checked facebook using H+, so I know it was connected to the internet this morning, and then the next time I picked my phone up, it wouldn't connect to the internet! I didn't change any settings or anything between when it was working and when it stopped working. I did have Juice defender installed and if you have ever used that, it has a little shield icon in the status bar that tells you what it is disabling to conserve battery. It had a red circle next to it, indicating that it was disabling my internet. The drop-down also said something like "Data Disabled - (Data/User)"
So I tried disabling Juice defender. No luck. I completely uninstalled Juice defender and rebooted. Still no luck. The only change I had made to my phone recently was installing some crappy N64 emulator, so i uninstalled and rebooted, still no luck. I rebooted into recovery and cleared my cache. Still nothing.
So I'm kinda stuck. My internet suddenly decided not to work and I've tried everything I can think of trying short of going back to the stock ROM and doing it all over again.
So does anyone have any advice to offer?
P.S. - My phone signal works fine. I can send texts and make calls, I just cant get on the internet. No, I'm not in flight mode! :good:
Let me know if you need any other info to diagnose this issue. I've provided everything I can think of but I'm sure I'm missing something.
Also a completely unrelated issue: When I'm using my phone and plug it into a wall charger it becomes unbearably laggy. frame rate is in the single digits, buttons don't respond, etc. Any idea on that either?
Try getting rid of rom manager. I heard its borked. Go back to stock and flash the froyo community kernel through froyo. You can find it on the super everything thread. (That thread is stickied I believe)
That will give you cwm and from there you are good to go.
As far as the charging thing, my phone and my wife's phone does the same thing since the charger that came with my phone broke. Try a different charger.
Sent from my SGH-I997 using xda app-developers app
I can't figure out what I'm doing wrong. The last time, how I loaded it was I installed the factory rom. Then I rooted it. (I paid one click root to do it the right way.) I then found a debloated rom and reimaged it without the bloat. After that, it was debloated but unrooted. So, I rooted it the same way one click root rooted it. (I recorded the screen as they did it the first time.)
Everything was working great. The phone worked wonderful for weeks. All the sudden this morning, my google play started crashing over and over. I wasn't sure why, so I rebooted the phone. It was stuck on the AT&T logo for 15+ minutes and the phone was heating up and appearing to be dead. So, I then forced rebooted it a few times with no luck. So, then I rebooted it into recovery and factory reset it.
The one thing I'm confused about that part is I did recover it this morning using the factory recovery. It seems like that would've put the directv app back on and exactly as if it was factory. But it didn't.
But none the less, it's back working. It's still running the debloated rom but unrooted. Not sure if I feel like re-rooting it. But, does anyone have any theories why a phone would be working just fine for weeks on end, then randomly one morning google play starts crashing non-stop. reboot the phone and it's dead? I swear I didn't do anything else. I'm really trying to refrain from messing with it. I just wanted it debloated so the battery life could be better. (The battery life is pathetic.) Today the battery life wasn't too bad. But, I'll pretty much guarantee that within the next few weeks, something will go haywire out of the blue.
dorlow said:
I can't figure out what I'm doing wrong. The last time, how I loaded it was I installed the factory rom. Then I rooted it. (I paid one click root to do it the right way.) I then found a debloated rom and reimaged it without the bloat. After that, it was debloated but unrooted. So, I rooted it the same way one click root rooted it. (I recorded the screen as they did it the first time.)
Everything was working great. The phone worked wonderful for weeks. All the sudden this morning, my google play started crashing over and over. I wasn't sure why, so I rebooted the phone. It was stuck on the AT&T logo for 15+ minutes and the phone was heating up and appearing to be dead. So, I then forced rebooted it a few times with no luck. So, then I rebooted it into recovery and factory reset it.
The one thing I'm confused about that part is I did recover it this morning using the factory recovery. It seems like that would've put the directv app back on and exactly as if it was factory. But it didn't.
But none the less, it's back working. It's still running the debloated rom but unrooted. Not sure if I feel like re-rooting it. But, does anyone have any theories why a phone would be working just fine for weeks on end, then randomly one morning google play starts crashing non-stop. reboot the phone and it's dead? I swear I didn't do anything else. I'm really trying to refrain from messing with it. I just wanted it debloated so the battery life could be better. (The battery life is pathetic.) Today the battery life wasn't too bad. But, I'll pretty much guarantee that within the next few weeks, something will go haywire out of the blue.
Click to expand...
Click to collapse
It is the fault of the rom you installed. Since it is de-bloated, then the developer of that rom might have accidentally removed an important app or service which is the cause of all of your problems. It can be fixed it by installing the stock rom via odin, rooting the phone and installing a different rom.
You paid to root your phone?
This particular crash was the first time it happened on this pre-debloated rom. The previous ones have all been on the stock rom.
ok, last night my phone required an att update. It attempted to update and rebooted. Stuck in a boot loop. Couldn't get out of it. Would just sit at the AT&T logo indefinitely. This was with the stock ROM rooted. So, I had to reload stock room unrooted again. Does anyone else have this problem with the rooted stock rom? Basically it runs for a few weeks. Then AT&T attempts to update and crashes the OS.
You can't OTA update a rooted phone
So what does everyone do about this? My phone pops up the update now or later message 3-4 times a day. I can't block the Ota update. If I ignore it, it prompts constantly.
dorlow said:
So what does everyone do about this? My phone pops up the update now or later message 3-4 times a day. I can't block the Ota update. If I ignore it, it prompts constantly.
Click to expand...
Click to collapse
Freeze the updater service / process / app, clear the cache to remove the downloaded update
Can u explain further how to freeze the updater service?
Ok, I looked up how to freeze the updater service and did that. I re-unrooted the phone, rooted it, then froze the updater service. My phone never updated. This morning an app was crashing. Rebooted it and same thing. Stuck on the at&t logo and won't boot. I'm having to re-default it again. The phone never updated from AT&T. But something crashed it last night. No clue. Problem is when this happens, the phone never boots back up so I can't look at it to find out why it happened.