I'm hoping I can provide information that may be helpful to developers about the Thunderbird's random rebooting problems.
For my phone it seems related to the ROM I'm running, so maybe this will help ID the problem?
ROMS w/o reboots:
Got the phone, got the OTA update, no reboots. None.
Rooted the phone, configured and ran PG05IMG_MR1_upgrade.zip, no reboots.
After bad experienced, unrooted, back to stock, no reboots.
OTA update again, no reboots.
Re-rooted, again ran the updated rooted ROM, no reboots.
Several listed below caused problems so I'm on Synergy with no reboots.
ROMs with reboots:
Liquid 1.5, reboots 2-3 times/hour
Liquid 1.4, reboots several times/day
Liquid 1.6, reboots several times/day
PUR3A05PTH3ORY v 1.2.2 reboots several times/day
Gingervitis 1.2, no reboots, powers off and won't come back on until I do a battery pull!
I'm really hoping this will help someone take a stab at fixing the problem! Changelogs for Liquid should help, why is 1.5 worse than 1.4 or 1.6? What's included or missing in the ROMs that fail as compared to the roms that work?
Every phone is different, just because a certain version of a rom isn't working well for you, doesn't mean that is the case with everyone. Each phone is different in you have to find what works best for you.
For example, I used Gingeritis based off of the GB leak and was getting a lot of reboots, but I tried BAMF and wasn't getting any. Meanwhile others get reboots on BAMF and don't on Gingeritis. Android is some trial and error before everything works just how you want it, IMO.
I was getting a lot of reboots almost non-stop from PUR3A05PTH3ORY. and I get 1 once in a while with CM7.
I know some TB's even rebooted a lot with the stock rom unrooted. My first one was like that.
I've flashed the mr2 radio and have used it for all roms and I've had no reboots
Bolted Down....
g00s3y said:
Every phone is different, just because a certain version of a rom isn't working well for you, doesn't mean that is the case with everyone. Each phone is different in you have to find what works best for you.
Click to expand...
Click to collapse
Partially true but there are common factors such as many having reboot problems with Liquid 1.5, etc.
hi, i have a 3d evo with s-on & h-boot 1.50 and i used gui to flash silver needle & went to recovery to flash viper rom and the phone keeps rebooting and i have read other posts and tired to flash other kernals & roms and nothings working. even tired to use my friends phone and tired to use his back-up but didn't work. any new ideas?? thanks in advance
My Evo 3D has been doing this consistently with the new kernel from the OTA update (I use MeanROM though), but I have seen others on Stock report the same.
It was doing it annoyingly constantly every couple hours when I would just not actively use it.
Now though it has settled down a bit and I'm wondering if it's not a bug but a feature? Because almost like clockwork every night it will reboot on it's own late at night. if I'm using the phone..it won't do it..but it seems to wait for a period of long idle time or something.
I have only had this issue on Kernel 2.6.35.13. Check and see if that is your kernel version as it's the newest one that is blazing smooth and fast (stock) and why I have chosen not to flash another kernel over it yet.
dzap said:
My Evo 3D has been doing this consistently with the new kernel from the OTA update (I use MeanROM though), but I have seen others on Stock report the same.
It was doing it annoyingly constantly every couple hours when I would just not actively use it.
Now though it has settled down a bit and I'm wondering if it's not a bug but a feature? Because almost like clockwork every night it will reboot on it's own late at night. if I'm using the phone..it won't do it..but it seems to wait for a period of long idle time or something.
I have only had this issue on Kernel 2.6.35.13. Check and see if that is your kernel version as it's the newest one that is blazing smooth and fast (stock) and why I have chosen not to flash another kernel over it yet.
Click to expand...
Click to collapse
i can't tell what kernel on here, its i flashed silver needle and then the rom and it nevered booted up.
I had the same problem using ROMs from XDA. Found that I used RUU to back to stock and it stopped. Haven't had a single reboot since I went back to stock where I would get reboots constantly, to the point the phone was useless.
Since I have S-Off, used the root patch to get root access, but only can be done with S-off...
djcro said:
hi, i have a 3d evo with s-on & h-boot 1.50 and i used gui to flash silver needle & went to recovery to flash viper rom and the phone keeps rebooting and i have read other posts and tired to flash other kernals & roms and nothings working. even tired to use my friends phone and tired to use his back-up but didn't work. any new ideas?? thanks in advance
Click to expand...
Click to collapse
nobody has asked this yet... so I will...
are you on the latest version of viper? silver needle is a 2.3.3 kernel... viper is 2.3.4.
that is your issue if that is the case. flash a kernel that is meant for that build.
sent from Evo
cobraboy85 said:
nobody has asked this yet... so I will...
are you on the latest version of viper? silver needle is a 2.3.3 kernel... viper is 2.3.4.
that is your issue if that is the case. flash a kernel that is meant for that build.
sent from Evo
Click to expand...
Click to collapse
yeah, most likely your issue is flashing a kernel NOT COMPATIBLE with the new base....
oh and your only compatible kernel at this time is stock
i tried to do the ruu step and none of the verisons workked, anybody have anymore ideas?? this is were i downloaded the ruu's from for sprint http://www.filefactory.com/f/4ef0ef536face67a/
I LOVE this rom and it makes the Thunderbolt more current and removes all the bloatware (Which, IMHO, includes Sense. Don't have a problem with Sense per se, but I do on phones that it makes sluggish, like this one).
What I am wondering is if there is a way to update Google Now on this rom (which is part of the extras of which I am grateful). Apparently Google just released an update to Google Now and Im wondering if there is a way to get that update onto a phone with this ROM.
Thanks!
I think you would have to see if a new version has been custom made for ics. Just Google Mikey Google now ics and you'll find out.
Sent from my ThunderBolt using xda premium
I am still getting bootloops with the latest release from twisted. I notice a new software when up and I did a dirty flash and nothing. and I tried a clean install and i still keep getting bootloops. I am using 4ext. for your information. any help would be appreciated. I went back down to 12/13 built from twisted before the bootloops started happening.
dgutierrez04 said:
I am still getting bootloops with the latest release from twisted. I notice a new software when up and I did a dirty flash and nothing. and I tried a clean install and i still keep getting bootloops. I am using 4ext. for your information. any help would be appreciated. I went back down to 12/13 built from twisted before the bootloops started happening.
Click to expand...
Click to collapse
Is there a way for me to get the 12/13 build to try? I only have from 12/16 up or so and it stays stuck in bootloop.
Never mind, I found all of the builds :-/
(My) Bootloop Solution
dgutierrez04 said:
I am still getting bootloops with the latest release from twisted. I notice a new software when up and I did a dirty flash and nothing. and I tried a clean install and i still keep getting bootloops. I am using 4ext. for your information. any help would be appreciated. I went back down to 12/13 built from twisted before the bootloops started happening.
Click to expand...
Click to collapse
I was able to solve my bootlooping issues by restoring the boot partition after flashing the rom. It works with dirty and clean installs. I've used this method successfully with all builds after 12/6. Let me know if you need any additional information
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I had the same issue today between 2 and 3, but it wasn't letting me send texts even though I could receive them. Maybe a network hiccup?
I am on stock radios, didn't know new ones came out. It is working for me now.
in the same boat
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
sjhanson Today, 12:20 AM #1035
Junior Member
Thanks Meter 1
Posts: 11
Join Date: Jan 2011
I am running 3.0.3 now. I was running Viper until the big man published 3.0.3, then i switched back. But even on Viper I was getting the same COM.PHONE.ANDROID has stopped error.
Cheers!
http://forum.xda-developers.com/showthread.php?t=2126386&page=2
borkborkbork! said:
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
Click to expand...
Click to collapse
Link to any of the other threads?
http://forum.xda-developers.com/showthread.php?t=2157855
xDexter said:
Link to any of the other threads?
Click to expand...
Click to collapse
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
You went back to S-ON or just a different kernel?
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
I also tried going back to stock ruu , nothing worked for me
borkborkbork! said:
I also tried going back to stock ruu , nothing worked for me
Click to expand...
Click to collapse
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
xDexter said:
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
Click to expand...
Click to collapse
com.android.phone .. but I still get my txt messages, go figure. I think my partitions may be in rare shape from rom's, kernals, and all the other numerous changes. Never been the same after I got error 7 on schatka 3.0.2, I switched back and forth from viper/hatka and twrp/cwmr
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
xDexter said:
You went back to S-ON or just a different kernel?
Click to expand...
Click to collapse
Forgot about this post, sorry. Did not go back to s-on, just flashed stock kernel from here: http://d-h.st/Ma1, boot.img via fastboot and then the modules zip contained within in recovery, and everything was good.
This didnt work for me . Any other suggestions?
cappiez said:
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Basically I hd the same situation happen to myself, no calls or data but wifi was good. Mine started to fail slowly , firs \t it was showing a 1X connection but dl were about 3G speeds. Next I lost signals in areas I never had signal issues with. Then total loss. New sim card and spent hours on the support line and a replacement unit.
Got a PM request for assistance, and thought I don't have a lot of tips to offer other than what I provided before, I'm going to post a more detailed overview (as I remember it, it's been awhile...) in case it's helpful for any other who may come across it later. The bottom line for me was that once things broke, it didn't work again until I flashed stock kernel via fastboot +modules in recovery and did a clean install of Hatka 3.03 w/ Sense launcher. That said, because of my flashing compulsion and failure to fully test things once installed, I can't pinpoint the exact step at which things broke.
Initially, I: Bought phone and factory reset, did not take Verizon OTA. Fiddled around, hated Sense, unlocked, flashed recovery, flashed Viper 1.1.0 (?, whatever the base was), booted and setup, fiddled around, hated Sense, wiped data, flashed 3 subsequent Viper updates (1.1.1,2,3 maybe?), booted and setup, fiddled around, hated Sense. Wiped and reinstalled de-Sensed Viper a few times in an attempt to get rid of Sense as much as possible.
Then things get murky. I did s-off, and at some point flashed (recovery) a kernel, Cubed I think. Wifi or something was borked (as I understand is the case with Cubed/Viper), and I flashed stock kernel back via recovery (no modules, I didn't catch that part at the time) and restored my backup for good measure, leaving me on fully functional Viper 1.1.3. Everything worked for a few days, but I continued to hate Sense, and began searching for something more sensible. At some point I flashed Hatka 3.03 w/ de-Sensed options, went to 320 DPI, and thought everything was fine for about 18 hours until I realized my phone was warm, and figured out it was rebooting every time I received (or placed) an incoming call (boss was pissed and kept trying to call me, already gives me a hard time about being an Android fanboy so I'm never going to hear the end of that). After a few hours of fiddling and various recovery attempts including restores and full wipe/clean installs of Viper, I finally managed to get things up and running with A. flashing stock kernel via fastboot + modules in recovery and a full wipe/clean install of Hatka 3.03 w/ Sense + Xperia launchers and eventually a 380 DPI.
One of or some combination of the s-off/custom kernel/failure to reinstall stock kernel modules/de-Sensed/low DPI/pin lock/Widget Locker/Viper combo I had going fouled something up, which I know is not entirely helpful. If I found myself in this situation again, I would flash stock boot.img via fastboot + modules in recovery, and probably flash a stock ROM to rule out anything else, then wipe and flash things from there until I got where I wanted or it broke.
For the record, I'm now back on my Galaxy Nexus until stable-ish CM 10.1 is within sight or I get tired of waiting and sell the thing, I just can't tolerate Sense.
same issue
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
jimmydee62 said:
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
Click to expand...
Click to collapse
Have you tried fixing permissions? In some other post I read phone process force closing was just a matter of wrong permissions.
In other hand I think if you format system, data and cache the phone storage would just keep hboot and recovery; at that point you could only run RUU to stock or adb sideload from recovery if your CWM version has the feature.
Sent from my HTC6435LVW using xda app-developers app
still problem
Yes have fixed permissions. Also have formatted everything I could in CWM still have problem. Is there a way to format with ADB commands?
Hi.
I'm on my 2nd S3 now. First one suffered from the "sudden death syndrome".
My 2nd S3 has been perfectly fine bar the odd lock up. It's rooted and flashed with Supernexus by Faryab on v4.2.2
It has been freezing a lot lately, maybe 3 or 4 times a day but over the past few hours, it's now locked up approximately 20-30 times and I have to keep the power button pressed to reboot it. I've uninstalled any apps I have installed over the past few days. Booted into recovery and cleared cache and davlik cache (it's now saying Android is Upgrading upon every reboot). I can't even get time to backup my apps using Titanium Backup without it crashing.
What is going on anybody? Any help is much appreciated.
Try having a read of the freezing thread over in general.
boomboomer said:
Try having a read of the freezing thread over in general.
Click to expand...
Click to collapse
Thanks. It appears my full microSD card was causing the problem. Cleared a few movies off it last night and it's not crashed since. Fingers crossed!
5aq1b said:
Thanks. It appears my full microSD card was causing the problem. Cleared a few movies off it last night and it's not crashed since. Fingers crossed!
Click to expand...
Click to collapse
I guess i spoke too soon. More crashes again today
Did you do a full wipe including system format before installing the ROM? . It may be a data problem. Don't forget that 4.2.2 is also a beta firmware mate and not official like 4.1.2 so these things can happen. Also there are no custom kernels to flash to try and see if it's kernel based either.
cooza said:
Did you do a full wipe including system format before installing the ROM? . It may be a data problem. Don't forget that 4.2.2 is also a beta firmware mate and not official like 4.1.2 so these things can happen. Also there are no custom kernels to flash to try and see if it's kernel based either.
Click to expand...
Click to collapse
Hey, yeah I did a full wipe including system format before I installed the new ROM. I've had this ROM for probably 3 months now and haven't had any problems with it up until the last few weeks. Infact 4.1.2 was killing my battery in a matter of hours. 4.2.2 ROM made me love my phone again as it fixed my battery woes!
This is so frustrating...
4.2.2 being a beta version can do this but re-installing can sometimes cure it though. Changing the kernel in 4.1.2 can give you better battery if you play around with a few and if course is more stable being an official release too. You can also try a different 4.2.2 ROM. They aren't all the same.
Thanks for the reply. Im not too comfortable/confident in changing kernels due to my lack of knowledge on them!
I do however like Faryabs ROMS as I like the original Android flavoured ROMS.
Will try a reinstall!
Same Problem
5aq1b said:
Thanks for the reply. Im not too comfortable/confident in changing kernels due to my lack of knowledge on them!
I do however like Faryabs ROMS as I like the original Android flavoured ROMS.
Will try a reinstall!
Click to expand...
Click to collapse
I have the exact same issue, I was running Faryaabs rom version M1, Android 4.2.2. And a couple of days ago, I noticed it started freezing, and I have to reboot with power button. Now I installed the leaked Touchwiz 4.2.2. but the freezing remains and it has started to be worse. As you mention, 20-30 times a day. I have noticed though, when I shutt of internet, both wifi and 3/4G I get less crashes. Have you noticed the same?
If you find a solution, please inform me to.
Cheers,
Niko
Niko_v said:
I have the exact same issue, I was running Faryaabs rom version M1, Android 4.2.2. And a couple of days ago, I noticed it started freezing, and I have to reboot with power button. Now I installed the leaked Touchwiz 4.2.2. but the freezing remains and it has started to be worse. As you mention, 20-30 times a day. I have noticed though, when I shutt of internet, both wifi and 3/4G I get less crashes. Have you noticed the same?
If you find a solution, please inform me to.
Cheers,
Niko
Click to expand...
Click to collapse
I think you may have found it
Wifi for example is controled by the kernel but there is no source codes released by Samsung so thats why there are no custom 4.2.2 kernels available for the S3 or you could flash one and most likely sort the problem out.
Its a shame cos there are for other phones on this version.
Hi dude
I went to the freezing thread here and found that the DFG method solved it all. So for anyone willing to try this please head over to that thread or just download the dummy file generator apps (2 in app store) although one is only necessary.
Gl and ty for the reaponse
Xda 4life
Sent from my GT-I9300 using xda app-developers app