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.
Related
Title says it all. Will putting one of the froyo based ROMS on my phone get rid of the dreaded silent bug? I am currently running 2.1 with aloysius v12 and I get it pretty often.
I don't believe that there is anyway to be able to tell that just from which rom you run as everyone's phone is different. With that in mind though, the good thing about being rooted is that you can do a Nandroid backup, then flash another rom and see if it works out for you. If it doesn't, then you've only lost a bit of time with playing around with the new system. If you don't like it, then restoring your phone only takes a couple more minutes, then you'll know for certain. Good luck!
try a rom without sense. on the regular v3 leak i was getting the silent bug constantly, but after rooting and installing xtrrom(highly recommended) i have yet to get it
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
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.
Just got s-off on my DNA but installing a custom Rom makes the phone randomly freeze and reboot. Tried CM11, carbon, and a few others. The time before restarting varies wildly from 10 seconds after boot to 20-30 minutes. It seems more frequent when the screen is on or when plugged into my PC but I could just be imagining things or could be coincidence.
I have flashed and rommed many phones over the years and this one really has me stumped.
I cleared the cache and dalvik and formatted the system partition before installing the Rom and gapps. I have tried multiple roms and multiple versions of gapps as well with no luck. I have superCID of 11111111 from the original unlock process if that makes any difference. I have currently RUUd back to 3.06 for now and it seems perfectly stable on the stock Rom. Any help would be appreciated!
renegadeone8 said:
Just got s-off on my DNA but installing a custom Rom makes the phone randomly freeze and reboot. Tried CM11, carbon, and a few others. The time before restarting varies wildly from 10 seconds after boot to 20-30 minutes. It seems more frequent when the screen is on or when plugged into my PC but I could just be imagining things or could be coincidence.
I have flashed and rommed many phones over the years and this one really has me stumped.
I cleared the cache and dalvik and formatted the system partition before installing the Rom and gapps. I have tried multiple roms and multiple versions of gapps as well with no luck. I have superCID of 11111111 from the original unlock process if that makes any difference. I have currently RUUd back to 3.06 for now and it seems perfectly stable on the stock Rom. Any help would be appreciated!
Click to expand...
Click to collapse
check my thread in the same section, mine started doing this two nights ago. I don't know why it started, my phone was fine prior to this. I did nothing to it, had been running Venom for a while, and two nights ago it started rebooting randomly and wildly. I have switched ROMs twice since then and it has not stopped. Like you said, it tends to be when the screen is on or gets plugged up. But unfortunately mine is doing it a lot on answering phone calls. I don't know if we are having same issure or what.
Possibly
lemonoid said:
check my thread in the same section, mine started doing this two nights ago. I don't know why it started, my phone was fine prior to this. I did nothing to it, had been running Venom for a while, and two nights ago it started rebooting randomly and wildly. I have switched ROMs twice since then and it has not stopped. Like you said, it tends to be when the screen is on or gets plugged up. But unfortunately mine is doing it a lot on answering phone calls. I don't know if we are having same issure or what.
Click to expand...
Click to collapse
I don't know if we are having the same issue it may be that we are though. I am on stock 3.06 not one reboot since I went to work this morning. Get home, install the newest twrp (it is removed in the RUU process), install cm11 snapshot m5, and the appropriate gapps. I got through setup to the point of adding my gmail and it froze and rebooted. I tried cwm recovery too but it made zero difference
TBH my screen is shattered really bad and I was going to replace it but I don't want to if I have to run stock roms forever. I was running one of the original Venom roms before s-off was possible, but then I broke the screen and switched back to my droid bionic but now I can afford the new LCD so I want to get this one running
renegadeone8 said:
I don't know if we are having the same issue it may be that we are though. I am on stock 3.06 not one reboot since I went to work this morning. Get home, install the newest twrp (it is removed in the RUU process), install cm11 snapshot m5, and the appropriate gapps. I got through setup to the point of adding my gmail and it froze and rebooted. I tried cwm recovery too but it made zero difference
TBH my screen is shattered really bad and I was going to replace it but I don't want to if I have to run stock roms forever. I was running one of the original Venom roms before s-off was possible, but then I broke the screen and switched back to my droid bionic but now I can afford the new LCD so I want to get this one running
Click to expand...
Click to collapse
Did you use the proper recovery stated in the thread to flash the rom, have you installed any new apps recently? Does it happen when you run the phone in safemode? Have you tried Performing an RUU and the unlocking and installing a custom rom again?
Did all that
Jaggar345 said:
Did you use the proper recovery stated in the thread to flash the rom, have you installed any new apps recently? Does it happen when you run the phone in safemode? Have you tried Performing an RUU and the unlocking and installing a custom rom again?
Click to expand...
Click to collapse
I have done all of that stuff multiple times
I haven't installed any apps at all on it. This phone is basically brand new, I got it right when they launched. I shattered the screen like 3 days after I got it, and tucked it in a drawer. It has been sitting there ever since.
I have another piece to add to the puzzle. While it has the stock ROM installed it seems to get service and work just fine, but when I install the custom ROMS it has absolutely zero cell connectivity (though WiFi works fine.)
Going into the settings reveals that on the custom roms it shows the IMEI and MEID as Unknown, and the ICCID is listed as Unknown as well. If I try to change the network mode (to LTE/CDMA or any one of the many available options) it says com.phone has crashed.
After the RUU process I have my proper MEID and ICCID showing in the settings panel, and service returns.
Can't flash radio?
After discovering the issues with the service while on custom ROMS I wondered if the radio had something wrong with it.
I tried to manually reflash the radio via fastboot (fastboot flash radio radio.img).
I tried this both in standard fastboot as well as in the rebootRUU mode, but both times I get an error that says remote not allowed. Could my bootloader somehow still be locked? The flag in bootloader mode says "Unlocked" but I unlocked manually after obtaining s-off rather than doing it officially via HTCdev. just trying to explore all options
My phone did that at one point. I had to re-lock and RUU back to 100% stock. I then unlocked my phone with Rumrunner S-Off tool. Flashed a Sense 6 ROM and has been working fine since.
Fixed!
So this problem is fixed!! I am not 100% sure what did the trick, so I will post my solution here in case anybody else experiences a similar issue. I won't go into too much detail with these instructions as all the tools are here: http://forum.xda-developers.com/showthread.php?t=2612740
I first downgraded to the 1.15 hboot and radio. I had to rebootRUU and flash them there as it can't be done directly in fastboot as far as I know.
Do them one at a time (flash the hboot, then reboot-bootloader, then rebootRUU then flash the radio, then reboot bootloader again.)
After doing this I tried to run the RUU exe but it came up with an error that it could not update my phone, so I did the manual Alt 3.06 RUU.
This seemed to work great, restarted the phone and saw the stock rom. I then changed from superCID 11111111 back to the stock CID, relocked my bootloader went back to s-on status. At this point I ran the RUU.exe again just to make sure everything was as stock as could be.
Got that all finished, ran RumRunner again, installed CM11 and no reboot for nearly 24 hours. Pretty sure all is well!
renegadeone8 said:
I don't know if we are having the same issue it may be that we are though. I am on stock 3.06 not one reboot since I went to work this morning. Get home, install the newest twrp (it is removed in the RUU process), install cm11 snapshot m5, and the appropriate gapps. I got through setup to the point of adding my gmail and it froze and rebooted. I tried cwm recovery too but it made zero difference
TBH my screen is shattered really bad and I was going to replace it but I don't want to if I have to run stock roms forever. I was running one of the original Venom roms before s-off was possible, but then I broke the screen and switched back to my droid bionic but now I can afford the new LCD so I want to get this one running
Click to expand...
Click to collapse
thats kinda crazy... i was on bionic before my dna. my screen on DNA is shattered like crazy. thought about going back to bionic temporarily, instead i'm gonna replace my screen and RUU and see if it fixes my problem
lemonoid said:
thats kinda crazy... i was on bionic before my dna. my screen on DNA is shattered like crazy. thought about going back to bionic temporarily, instead i'm gonna replace my screen and RUU and see if it fixes my problem
Click to expand...
Click to collapse
Good news and bad news. The good news is for you!!! I think I figured out what the problem was. It seems to be an issue either with using an older radio, or an older hboot on a newer ROM. I don't know why exactly, but the RUU process was not properly updating my radios. This may be because I ran an RUU while unlocked at one point (every guide I see is very adamant about relocking before the RUU process.)
The bad news is that I ordered a new LCD for my DNA, and I ruined my phone trying to do the repairs. It is by FAR the worst phone I have ever had to work on. I have replaced LCD's in Galaxy devices, Iphones/ipod touches, laptops, TV's, and one in a smartwatch and have never hurt a thing. Got my DNA back together and it flat out wont turn on I don't know what the problem is, but something is fried. Hope you have better luck than me!
So my girlfriend's EVO 4G LTE is a bit of.. well, I'm gonna say bastard. I'm not new when it comes to rooting devices but I've never had to deal with one that fought me so much.
I've been through this adventure many times with it, and it gets more complicated each time. Here is what's happened with it so far.
It was stock, and it was terrible. It lagged so much, despite factory resets, that apps like google maps were completely unusable. It got no battery life AT ALL, and was generally freeze-happy and miserable.
So then I s-off'd it and after learning all its quirks, installed recovery and CM 11.2 (I think? It's been a year)
This worked great! For.. a few days. The phone worked, we went on vacation to a roaming area where Sprint had no coverage. We come back, and only the data works, texts and calls do not, and the phone acts like it's not activated. Yay. All attempts to get it activated are met with failure, much to the confusion of the poor sprint person on the line. The phone just will not take, at all. (damn lack of real sim cards..) We tried recovering back to a backup from twrp of the stock firmware but that won't work either? It wouldn't register with sprint even on the backed up version of stock sense. The phone seemed dead at this point. Bricked radio?
So we give up. We bring it to the sprint store, and they do some magic to it, and its back to stock, slow and terrible, but functional. We don't touch it until about three weeks ago.
But, my girlfriend is tired, again, of the terribleness, and asks me to try again. Okay, sure.
I install TWRP again, so far so good. The phone is still S-OFF from last time, which is nice. I go to install CM11.2 from the files used from last time (the MD5 does check out correct) But, the phone complains about not having a new enough bootloader. ???? (So I assume sprint downgraded the bootloader in the process of fixing it. somehow)
I forget the exact numbers, but we can't install CM11.2, only 10. or 10.whatever. the newest 10. Okay, fine. I gather a new set of cyanogen files, gapps, whatever, and flash all of that, so far so good.
This time it works, and stays working! Yay! So I thought.
As it turns out, its on a very old version of android (so old that it goes into a special usb file host mode when usb is plugged in) and more importantly, the camera is TERRIBLE. I've read that the evo 4g lte uses a special ImageSense chip to boost camera performance, and that cyanogen 10 does not support it. I can tell, because the camera is absolutely terrible. The battery life also is terrible, presumably because it lacks optimizations. It had way better battery life on CM11.2 when it worked. Other then that, its working just fine, but the camera is just unacceptable.
So, I want to know what to do from here. I see a few paths.
plan A:
update HBOOT to a newer version to allow the install of CM11.2
(how do I do that? I heard you have to use an RUU, but which RUU? I read that there is some touchscreen driver that is an issue depending on what version you run)
(Once I install the ruu is it business as usual, install twrp and then flash cyanogen like normal? Will it do the crazy not activation thing again? was that a fluke??)
plan B:
update HBOOT, but to a much newer one that allows the install of CM12 or whatever the newer ones are. Presumably updating past the touch screen driver issue and not allowing us to go back to an old version.
(once again, what do I need to do that? Is this advisable? I quite prefer the idea of running a newer version. So if this is the better idea, I will do it.)
I thank you greatly for your help. I'm not used to it being this complicated. I've read a lot of things about this phone and it seems very conflicting at times. I just want to get straightened out.
yeah, it's probably running like crap because the firmware is so out of date.
use this RUU http://forum.xda-developers.com/showthread.php?t=2653730
then re-flash twrp and another ROM if you want (i've been running cm12.1 for MONTHS) but she might be able to survive just like that. only fear would be staying vulnerable to security threats, but you've been living in that house this whole time anyway.
for a good while i was running this stock 4.3 with root and some xposed modules installed to get the cm functionality that i missed. but seriously, run the RUU, let it activate, then go under settings and update profile and PRL, fire up maps/navigation with GPS on so that it gets a good lock and its cache populated, then you should be good from there.
Thank you!
Can I use the same utility that I used to flash twrp (that one-click thing that seems to support a half million phones) or do I need something special? This sounds very easy to do. Almost too easy, given that the story of this phone's life is that the easiest thing I've ever done to it was take it completely apart to replace its battery.
never used the one-click stuff. flashing recovery via fastboot is simple enough.
get the adb tools, here's some easy instructions for that http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
get the latest twrp from here https://dl.twrp.me/jewel/
then follow these directions to flash twrp https://wiki.cyanogenmod.org/w/Install_CM_for_jewel#Installing_a_custom_recovery_using_fastboot
if not installing cm or any other rooted rom (you want to root stock) get supersu from here http://forum.xda-developers.com/showthread.php?t=1538053 and use the twrp installable zip
If you've gone through the trouble to S-Off, then fastboot flash the latest TWRP (3.0.2.0, I believe), which supports the new partition layout (extra 4gig of internal SD space).
From there, flash the official 651.4 developers version, go through the device setup which updates your PRL, then shut it down and reboot to TWRP and flash the latest CM12.1 and a proper gapps package (I use "stock", which is a bit much for some, but I like having everything available to me).
The one thing I do that most don't is to disable zRam and enable swap with my own script I wrote specifically for the external SD I formatted as vFat/ext4/swap.
After doing all this, I do not have the issues you seem to have, and the PRL seems to stay from the last install of stock Sense 5. Even with all the apps I have installed, it's still fairly snappy. Facebook/Messenger, and other memory hogging apps run smooth with no discernable lag, unless there's network issues.
YMMV, but look into using an app like "Ampre" to measure battery life and gauge if the battery is going bad or not.
Outside of that, there's not much left to do with these older devices that hasn't been done already.