i tried multiple roms and every time my phone freeze to a point that i have to take the battery out. any idea what could be the problem?
When is it freezing?
Did you wipe your data, cache, and dalvik-cache before flashing?
...
tuamazing said:
i tried multiple roms and every time my phone freeze to a point that i have to take the battery out. any idea what could be the problem?
Click to expand...
Click to collapse
Are you full wiping between flashes? If so and you're still getting problems you can try to flash a stock image via Odin and if the problem persists it may be a hardware problem.
Related
After my phone got back from repair I had the "phone turning off" bug, I tried almost everything but can'T solve the problem at all. Who else suffers from the problem and who solved it so far?
What android version are you on I thought it was fixed with gb
sent from my acidhazard thrill
no, the problem started with gb, the reboot problem was on froyo
Ahh I thought that's what you meant my phone has never shut off
sent from my acidhazard thrill
Have you ever used overclocking?
Are you on a custom rom or on stock?
GentlyCriminal said:
After my phone got back from repair I had the "phone turning off" bug, I tried almost everything but can'T solve the problem at all. Who else suffers from the problem and who solved it so far?
Click to expand...
Click to collapse
I have the problem on both froto and gb, and drain battery when the problem occur, i really want to know if there is a solution
Sent from my LG-P920 using XDA
Mostly when I get into that problem, I'll backup all my application+data and wipe factory reset the phone and fresh install custom firmware. Then restore app and certain important data only such as contacts, sms etc.
cyclonmaster said:
Mostly when I get into that problem, I'll backup all my application+data and wipe factory reset the phone and fresh install custom firmware. Then restore app and certain important data only such as contacts, sms etc.
Click to expand...
Click to collapse
I have the problem no matter which rom i have used
Do you think the problem the setting related! ? i think it is hardware related
Sent from my LG-P920 using XDA
Suck, i have lost 25% of battery when i encounter this turning off problem again!! plx help, should i sent back the phone to lg !??
Sent from my LG-P920 using XDA
things really get crazy somehow ! as i was sure that the problem was hardware related, I remembered that the phone never shut down on froyo, so I downgraded to 2.2, but no matter to which version i revert back, I just don't have signal !
GentlyCriminal said:
things really get crazy somehow ! as i was sure that the problem was hardware related, I remembered that the phone never shut down on froyo, so I downgraded to 2.2, but no matter to which version i revert back, I just don't have signal !
Click to expand...
Click to collapse
How did you revert back your ROM? And how do you do an upgrade? Is it by flashing .zip from recovery of by KDZ method? If by .zip from recovery I believe you did it wrong since ding it that way is not include flashing baseband.
Wipe dalvik cache, Wipe battery stats, wipe cache partition and full wipe/factory reset from recovery. Then flashing.
Proper method to upgrade/downgrade is using KDZ method: http://forum.xda-developers.com/showthread.php?t=1287236
It will install the ROM and the baseband. After that don't restore any application yet. Check it first, is it still shutdown? Is it still no signal? Is it still have battery drain problem? If it is, then it's a hardware failure. Send it to LG Service centre.
cyclonmaster said:
How did you revert back your ROM? And how do you do an upgrade? Is it by flashing .zip from recovery of by KDZ method? If by .zip from recovery I believe you did it wrong since ding it that way is not include flashing baseband.
Wipe dalvik cache, Wipe battery stats, wipe cache partition and full wipe/factory reset from recovery. Then flashing.
Proper method to upgrade/downgrade is using KDZ method: http://forum.xda-developers.com/showthread.php?t=1287236
It will install the ROM and the baseband. After that don't restore any application yet. Check it first, is it still shutdown? Is it still no signal? Is it still have battery drain problem? If it is, then it's a hardware failure. Send it to LG Service centre.
Click to expand...
Click to collapse
Man nothing against you, I know you wanna help, so thx for that, but I'm trying to get advanced help, all these common things aren't any problem and I know almost everything about them. I am asking if anybody succeeded to get rid of the shut down problem and if anybody else had signal loss after reverting back to froyo ? And the main reason why I started the thread, is because I know that there was the reboot issue on froyo and the shut down problem on ginger and this was a serial bug
Hey guys...today i put the factory ATT ICS from sammobile on my device via Odin. Now, about every 2-5 seconds I get the com.phone.android crash message. I've looked at about 50 or so different threads and can't seem to find a resolution.
I've factory reset, I've reflashed, I've cleared cache data in phone, I've cleared cache data in contacts storage. On the verge of phone smash.
Any ideas?
Try reverting to stock via kies? it sounds like you have a bad flash maybe due to the file. In stock you shouldn't have these issues.
kishke said:
Try reverting to stock via kies? it sounds like you have a bad flash maybe due to the file. In stock you shouldn't have these issues.
Click to expand...
Click to collapse
THanks for the quick reply. Actually I just went into boot/recovery mode (not sure of correct name) and cleared cache a few times and did another full wipe and problem solved. Must have been some strange conflict...
Try fixing permissions if it happens again. That will usually fix FCs without a full wipe (although phone process FCs tend to be a little trickier to get rid of).
Not sure if you tried first time around but I always wipe things a minimum of 3X (usually 4-7 -- call me paranoid).
I'm glad you fixed the issue; I haven't seen/heard this one before.
I rooted and installed a few different ROMs (some didn't take) on my brother's phone, and they seem to work fine until the phone is turned off or the battery runs out. Then the phone freaks out when he restarts, it keeps Force Closing a bunch of different processes and he can't use and will end up having to wipe again. We've done factory wipes, formatted system, cache, dalvik cache when we install ROMs and we keep running into this problem. Any suggestions? I think his battery may need to be replaced, I heard a rumor that it may cause issues, but is there anything else to try? Thanks in advance.
They are the right ROMs for his phone?
OverDosed 4g Slide
Best Porting Team > S.W.a.R.M
chairhome said:
I rooted and installed a few different ROMs (some didn't take) on my brother's phone, and they seem to work fine until the phone is turned off or the battery runs out. Then the phone freaks out when he restarts, it keeps Force Closing a bunch of different processes and he can't use and will end up having to wipe again. We've done factory wipes, formatted system, cache, dalvik cache when we install ROMs and we keep running into this problem. Any suggestions? I think his battery may need to be replaced, I heard a rumor that it may cause issues, but is there anything else to try? Thanks in advance.
Click to expand...
Click to collapse
Under "advanced" in recovery select "set permissions". Something else MAY be going on like you said but most unexplainable force closes come from the permissions somehow getting scrambled.
Good Luck!
K7Cobb said:
They are the right ROMs for his phone?
OverDosed 4g Slide
Best Porting Team > S.W.a.R.M
Click to expand...
Click to collapse
Definitely. They are myTouch 4G Slide ROMs.
WeekendsR2Short said:
Under "advanced" in recovery select "set permissions". Something else MAY be going on like you said but most unexplainable force closes come from the permissions somehow getting scrambled.
Good Luck!
Click to expand...
Click to collapse
I think we tried that, but if it happens again, we'll try again.
Another thing you could try is to install the stock rom then try installing the rom of your choice. Sometimes phones need that type of clear.
Nas Escobar said:
Another thing you could try is to install the stock rom then try installing the rom of your choice. Sometimes phones need that type of clear.
Click to expand...
Click to collapse
I couldn't find a stock ROM that would work. Tried the RUU method and it didn't work.
I just rooted last night and everything was good... This morning all I did was freeze some of the stock Verizon apps, and the system crashed. Now when it reboots, it's stuck at the Verizon screen. I can access Bootloader/Recovery, and have tried "fastboot erase cache" but that hasn't fixed it. If I let it sit, I can hear notifications and stuff in the background (I also have MightyText installed, and can send/receive texts via that), so Android is running in the background - it's just "stuck" on this Verizon screen. I'd really rather not have to do a factory reset, since I just spent last night getting everything set back up from the root process.
Any suggestions? Please help!
Uncertain. Just a shot in the dark but which recovery do you have? Have you tried doing a "fix permissions" within it?
Drunkula said:
Uncertain. Just a shot in the dark but which recovery do you have? Have you tried doing a "fix permissions" within it?
Click to expand...
Click to collapse
TWRP. Just did that now, no changes.
You may have froze something you shouldn't have. At this point, I'd personally do a full wipe and reflash the ROM. If not on a ROM and on the stock RUU ROM. I would:
1) consider flashing a stock based ROM:
This ROM is 100% stock based off RUU -
http://forum.xda-developers.com/ver...-4-17-605-9-stock-resources-firmware-t3196906
2) run RUU again, and freeze one app at a time to narrow down what may have caused this.
3) you can try a wipe of just cache/dalvik cache
andybones said:
You may have froze something you shouldn't have. At this point, I'd personally do a full wipe and reflash the ROM. If not on a ROM and on the stock RUU ROM. I would:
1) consider flashing a stock based ROM:
This ROM is 100% stock based off RUU -
http://forum.xda-developers.com/ver...-4-17-605-9-stock-resources-firmware-t3196906
2) run RUU again, and freeze one app at a time to narrow down what may have caused this.
3) you can try a wipe of just cache/dalvik cache
Click to expand...
Click to collapse
Thanks, yeah I just wiped and flashed a ROM. I needed my phone running in the next two hours, and didn't have the time to investigate. Hopefully it doesn't happen again.
dajoip said:
Thanks, yeah I just wiped and flashed a ROM. I needed my phone running in the next two hours, and didn't have the time to investigate. Hopefully it doesn't happen again.
Click to expand...
Click to collapse
Next time when you're cleaning out Verizon bloat, don't take out anything that you're not sure of.
Leave in there: VZWAPN and vzwdummylibs if you dump any Verizon apps.
Besides being able to start the phone, it's got to be able to send and receive calls. I have learned this thru bad decisions and their results.....
I'm trying to reinstall my old phone to give to a friend.
I do a complete reset, and install a fresh ROM. The phone starts, sometimes even gets to full functionality, then restarts and is mostly stuck on bootloop. Other times it restarts during the initial set-up process.
I've tried different ROMs.
Does that mean it's a hardware issue, or can reinstalling custom recovery or even re-rooting help?
Have you tried stock roms like RedRom?
If it still bootloops, it's a battery issue.
Johnny TDN said:
Have you tried stock roms like RedRom?
If it still bootloops, it's a battery issue.
Click to expand...
Click to collapse
Well, I'll be dammed, RedRom seems to have no reboot issues! Why is that?
Lauriso said:
Well, I'll be dammed, RedRom seems to have no reboot issues! Why is that?
Click to expand...
Click to collapse
I don't know.
Have you tried when you used those different roms, a clean flash? Sometimes problems occur when you "dirty" flash (aka flash roms without factory reset).
Johnny TDN said:
I don't know.
Have you tried when you used those different roms, a clean flash? Sometimes problems occur when you "dirty" flash (aka flash roms without factory reset).
Click to expand...
Click to collapse
Hmm, I was doing factory resets always, but this time I manually selected to wipe EVERYTHING apart from external sd, as well as cache/dalvik AFTER installation, and the problem seems to be fixed! Thanks for pointing me in the right direction!