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.
Related
Hey all,
I'm still a newbie, so I wasn't able to follow-up directly in the Das Bamf 1.5 Remix thread.
First off, awesome ROM and thanks for all your hard work. I love the recent apps replacement and battery enhancement.
However, I'm noticing that my phone has randomly shutdown a few times today. Does anyone have any insight on that?
Thanks
Are you overclocking? What kernel are you using?
Nope and I was running Adrynalyne's 4.4.2 experimental kernel (stock speeds), but I just downgraded to 4.3a.
In hindsight, maybe it was just a symptom of using the experimental kernel, however I didn't see the random shutdowns while using Bamf Remix 1.4.
Thanks for the quick response.
I had one as well... it happened only once so far. I'm running 4.4.2 kernel with the remix as well.
MoshingPanda said:
Nope and I was running Adrynalyne's 4.4.2 experimental kernel (stock speeds), but I just downgraded to 4.3a.
In hindsight, maybe it was just a symptom of using the experimental kernel, however I didn't see the random shutdowns while using Bamf Remix 1.4.
Thanks for the quick response.
Click to expand...
Click to collapse
Try running "fix permissions" in RM?
Sent from my ADR6400L using XDA App
I've have had no reboot, wiped all on install, oc at 1200+ on smartASS gov.....
Sent by my ThumperBolt
Thanks for the comments I'm going to give a full wipe a try
If your going to use something other than 4.4.2 I strongly recommend 4.3c. Very stable OC kernel.
4Geezy ON DopeDiculous's ROOTED TBeezy!
Hi,
I just installed BAMF Remix 2 days ago, and I did a full wipe and am not running any different Kernel's other than what came with it. And I and getting random reboots and shutdowns.
Thoughts???
I ended up unrooting my phone to exchange it with Verizon for another reason. However after getting my new phone, I rooted it, flashed the radio RUU and then Das Bamf and haven't gotten any reboots since. A clean wipe seems to fix it.
ive never had a random reboot on this rom until this morning. been pretty stellar so far
Yeah, I had the Radio he recommended and wiped everything, followed all the instructions, and this has been the worst ROM to date for me. Im not one to enjoy Sense in the first place. I used it for about 48 hours, it was pretty sluggish, and titanium backup took about 3 hours, when it takes about 20 minutes on other Roms. I got the random shutdowns, where it would just turned off without notice. I fixed the Permissions and it just wouldnt turn around. So im back to boLTEd .35 and part time CM7 - alpha
So I am thinking about isntalling the gingervitis 1.0 rom, I am currently on 1.12.605.6 radio and stock os w/root, I was wondering what radio i need to be on for this rom( he does have a link for a radio but dont know if it is ok to upgrade from the verison i am on) and after i do flash this radio and rom, and say i dont like the rom, if i restore back to stock os w/root am i able to keep the radio i upgraded to or am i going to have to downgrade to a different one, sorry about posting this in general i tried in the actual thread and got no answers.
You should be fine upgrading as long as you follow his steps.
As far as going back, I don't think that radio works on froyo roms. That's why when you flash the radio first and boot your phone back up, you don't have service. I could be wrong, but that's what I've gathered from everything.
I have GB right now and the only problem I've had so far is my text messages are out of order. Other than that, everything works great. I do know a lot of people are having trouble placing phone calls, and having random reboots though. It seems pretty hit or miss, but the developers are working hard trying to get everything as stable as possible.
Seems like every day since the leak a new version comes out with more bug fixes and different sense 3.0 additions. If you don't like the downfalls you see today, wait until tomorrow and see if they've fixed it yet.
I've been very impressed with the amount of bugs have been fixed so far and how fast they've fixed them.
I was having Force Close issue on beta 6 but beta 5 rocked
k i think i am going to do it, do you know if its easy enough to just flash the old radio back on it or am i going to run into problems if i decide to restore back, also when he comes out with updates i should just be able to flash the newest beta on top the other or should i do a wipe and then install again.
I'm having serious charging problems with this rom and the test 4 kernel. Talking like, 3% charged in 45 minutes off the wall.
I'm using the beta 6 Rom with the kernel that came with it and no problems so far not even reboots, have tried the newest kernel by imoysen?
Sent from my ADR6400L using Tapatalk
Well here is the issue, I bought the HTC Thunderbolt awhile ago. I then rooted my phone but left the original ROM on it since the custom roms were not stable. I noticed verizon was pushing me some update and I just ignored them. I woke up today to see my phone rebooted with the screen on an exsclamation point. And then my Thunderbolt keeps rebooting itself now. I tried going into ROM Manager to download a Custom ROM but the phone just reboots before I can do it. I just installed Liquid Gingersense v1.6 rom with the MR2 OTA Radio which said it installed just fine after installing the Liquid Gingersense rom. I went through setting up the google account fine and after it booted to the main screen now my phone boots all over again, get stuck at htc screen for a bit then loads the phone fine then boots again. I am really not sure what the heck is going on. I am new to the MR2 OTA Radio since I cam from the Droid 1. So I hope it was not the install order I did it. I Have turned off the phone booted it with still same rebooting over and over issue. If anyone has idea's please let me know. Much appreciated. Thanks
I'm in the same boat. I have wiped the SD card and done a factory reset on the phone. It is no longer rooted, as I can't install and run apps requiring root permission. The update fails every time it tries to install, I also get the exclamation point android screen when the update tries to install. I'll take the update, I don't care. I just want a reliable phone again.
I'm seeing this issue come up a lot. Some of you folks seem pretty upset by it, and reasonably so. Search through the threads and you'll find you solution.
For those who are STILL running that antique and wildly obsolete ROM that the jcase rooting process leaves you with, I'd like to set a few facts before you. First of all, that ROM wasn't provided as a long-term daily driver. It's OLD and it's not very efficient with the battery. Second, simply because it's stock doesn't mean it's inherently stable. It's probably less stable than the custom ROMs out there. Third, the only ROMs really struggling with stability were the 2.01 RUU gingerbread builds. That build is obsolete, but not nearly as obsolete as the ROM that the rooting process leaves you with. The stability issues with the second OTA had nothing to do with the ROM, but rather, the radio that came with the RUU. In short, it's foolhardy to believe that custom ROMs are somehow inherently dangerous or unstable.
I'd like to suggest to whoever might be running the rooted ancient ROM the rooting process leaves you with to abandon it at your earliest convenience. Flash an MR2 radio, and if you like stock, use the stock rooted debloated ROM based on the 1.70 RUU. If you decide not to do this, and your phone auto-accepts the update, you'll probably lose everything on the phone trying to get it working again. Save yourself that hassle. Flashing ROMs isn't hard and people do it everyday.
Ok, so I need some help. I had to trade my evo in due to a problem with the front facing camera so, naturally, I have hboot 1.5. Though it is frustrating, I don't have a really big problem with taking an extra step to flash ROMS. Unfortunately, I have not been able to sucessfully flash for a while. I was on Nocturnal Xplod (1/2/12) and it was relatively stable, with only a few reboots every week. However, lately, it has gotten unstable and so I started looking for an alternative.
Every single time I flash a different ROM I get about an hour of stability, then it reboots every 5-10 minutes until the battery runs out.
I have tried the flashimg gui method, I have tried using adb to go through fastboot and flash recovery . . . I have tried with and without TiBa. I am not sure what to do. Am I missing something? I am not a flashaholic, but I do like to have the ability to take advantage of stable roms.
I am using TWRP 1.03 on my phone, so I will try CWM since I just read that people are having trouble with bad flashes with TWRP. If anyone else has any other recommendations, I would be very happy to hear them.
Drachen808 said:
Ok, so I need some help. I had to trade my evo in due to a problem with the front facing camera so, naturally, I have hboot 1.5. Though it is frustrating, I don't have a really big problem with taking an extra step to flash ROMS. Unfortunately, I have not been able to sucessfully flash for a while. I was on Nocturnal Xplod (1/2/12) and it was relatively stable, with only a few reboots every week. However, lately, it has gotten unstable and so I started looking for an alternative.
Every single time I flash a different ROM I get about an hour of stability, then it reboots every 5-10 minutes until the battery runs out.
I have tried the flashimg gui method, I have tried using adb to go through fastboot and flash recovery . . . I have tried with and without TiBa. I am not sure what to do. Am I missing something? I am not a flashaholic, but I do like to have the ability to take advantage of stable roms.
Click to expand...
Click to collapse
Drachen808 said:
I am using TWRP 1.03 on my phone, so I will try CWM since I just read that people are having trouble with bad flashes with TWRP. If anyone else has any other recommendations, I would be very happy to hear them.
Click to expand...
Click to collapse
A bad flash can occur but generally they aren't prevelant. The best place to look for feedback on ROMs is in that specific ROM thread. If that specific ROM isn't setup well, or has bugs, these will cause random reboots.
If you're really interested in helping out the devs, the best first step in technically troubleshooting a random reboot is to grab the /proc/last_kmsg file. This is a log of the kernel as of last boot and will indicate whether or not the kernel was involved in the random reboot. If the issue is in the kernel, will narrow down the focus. If the issue is not in the kernel, will eliminate that possibility.
Another common cause of random reboots can be poorly coded 3rd party apps. Unfortunately, depending on the number of 3rd apps installed, this process can take a while to troubleshoot as the best method is to remove all and start installing in batches waiting to see if any random reboots occur.
Hope these few suggestions and some technical information help!
Thank you Joeykrim. I will look into that, but I am fearing more and more that it may be my phone. I have tried probably every sense 3.0 rom (need wimax and camera so no 3.5) and several different kernels, and it keeps happening.
Okay, I was running infection 2.5 for about 2-3 months. I tried to upgrade to 2.8.1 infection last week, but kept getting random wifi/date drops constantly. I tried Tron for a few day, but that kept hanging up. I tried Xenion??, but that also had the wifi/date drops. Now I have tried Vanilla. It was running fine all day yesterday and today, but now it stuck in bootloop.
What gives. Any advice? Should I reflash an RUU and update?
I am S-off; H-boot 2.28 and radios 2.23....
I never had this many issues with different ROM before. FYI, I have tried different kernals, different governors, etc... It also seems my phone is running hot with battery temps over 110* constantly.
Please help.
(Edit: Before someone asks, I have wiped, and wiped, and wiped even more, total clean install of apps, etc...).
Nappyloxs said:
Okay, I was running infection 2.5 for about 2-3 months. I tried to upgrade to 2.8.1 infection last week, but kept getting random wifi/date drops constantly. I tried Tron for a few day, but that kept hanging up. I tried Xenion??, but that also had the wifi/date drops. Now I have tried Vanilla. It was running fine all day yesterday and today, but now it stuck in bootloop.
What gives. Any advice? Should I reflash an RUU and update?
I am S-off; H-boot 2.28 and radios 2.23....
I never had this many issues with different ROM before. FYI, I have tried different kernals, different governors, etc... It also seems my phone is running hot with battery temps over 110* constantly.
Please help.
(Edit: Before someone asks, I have wiped, and wiped, and wiped even more, total clean install of apps, etc...).
Click to expand...
Click to collapse
Did your issues start after flashing the latest firmware?
kc6wke said:
Did your issues start after flashing the latest firmware?
Click to expand...
Click to collapse
No, my wifi/data was going in and out before, so I update to the latest firmware.
Nappyloxs said:
No, my wifi/data was going in and out before, so I update to the latest firmware.
Click to expand...
Click to collapse
I was having similar issue on New firmware with older roms
That's why I decided to make my own from the latest ota.
I havent had an issue since.
kc6wke said:
I was having similar issue on New firmware with older roms
That's why I decided to make my own from the latest ota.
I havent had an issue since.
Click to expand...
Click to collapse
I wish I knew how to. One day I may learn. I just switched to a Sense rom (Nils 4.0), just because I could not get out of bootloop earlier. I am going to let that run until it a) either acts up or b) until I have time to toss on a new rom, RUU, etc...
Go for a cm9 ROM maybe. There super stable, I used them before cm 10.1
I use the unofficial cm 10.1 rom now
Sent from my ADR6425LVW using xda app-developers app