yashsingh1/xdaforums huggingface dataset:
[HD2 Android Q&A, Help & Troubleshooting and Genera] webuser71:
I have the ROM IMILKA-DHD-RAM image. SD is partitioned with FAT32 and ext3. ROM works fine. As SD / MAGLDR (Boot AD SD) I have different ROM' , DHD and Miui and work properly.

THERE IS ONLY Gingerbread7 (AmericanAndroid,poybbc, MCCM, ...) will not start. It just stays on the HTC logo are (freezes). rootfs.img and startup are OK . I have 5 different MAGLDR GB Rome tried but can not start. The another Rom like DHD, INC., Z and Miui work fine. I've reformatted SD, 2 SD tried but without success. Can someone please help me. :mad:
[Captivate Q&A, Help & Troubleshooting] bluemoon1221:
So i am currently using gr-12 Rom. And i don't use setcpu or voltage control.

However i have been noticing that my phone stays at 800 mhz the entire time...

According to cpu spy. Its 98% 800 mhz... This has been resulting in a very decreased battery life.(about 10hours on standby).

Any solutions?

Sent from my Galaxy S captivate
[Captivate Q&A, Help & Troubleshooting] neubauej:
Using what kernel?
[Captivate Q&A, Help & Troubleshooting] TRusselo:
boot into cwm and clear voltage settings.

or USE voltage control and make sure 1000 is enabled.. or wtf is going on and change it manually.

ps and ya what kernel.
[Captivate Q&A, Help & Troubleshooting] bluemoon1221:
I'm just using the kernel that you flash when you flash gr12... I didn't flash any other one..

Sent from my Galaxy S captivate
[Captivate Q&A, Help & Troubleshooting] bluemoon1221:
And any guide on how to use voltage control? I have no idea what to do

UPDATE: I just got voltage control off the market. And it said my kernel is not compatible with it...

Sent from my Galaxy S captivate
[Captivate Q&A, Help & Troubleshooting] majinzen:
Don't know if this is an issue with GB roms, but change your wifi sleep policy to never and see if that helps. I know on froyo there was a bug that caused the phone to stay awake when the wifi sleep policy was set to turn of when the screen was off.
[Captivate Q&A, Help & Troubleshooting] mrhaley30705:
I think GR12 used xcals kernel, and it does not support oc/uv. Thats why voltage control won't work.
[Captivate Q&A, Help & Troubleshooting] mrhaley30705:
Check for an app gone wild.
[Captivate Q&A, Help & Troubleshooting] bluemoon1221:
Mine was already set to 'Never'...

So that's not the problem..

Sent from my Galaxy S captivate
[Captivate Q&A, Help & Troubleshooting] bluemoon1221:
What do you mean?

Sent from my Galaxy S captivate
[Captivate Q&A, Help & Troubleshooting] bluemoon1221:
Well can I flash another kernel?

Or any other solution than voltage control?

Sent from my Galaxy S captivate
[Captivate Q&A, Help & Troubleshooting] mrhaley30705:
I would start watching app. You may have one thats running rampant.

You can flash Talon. Its oc/uv capable.
[Captivate Q&A, Help & Troubleshooting] bluemoon1221:
Well how do you flash another kernal? Just put my phone to download mode and put the kernal on 'pda' section and flash?

Sent from my Galaxy S captivate
[Captivate Q&A, Help & Troubleshooting] mrhaley30705:
Yes. Should take about 15 second.
[G Tablet General] goodintentions:
Like most people, I never fully drained my battery and reset my battery stat. So, up until couple days ago, it never went above 94%. But for some reason, I was at my bro's house and plugged it in at night. In the morning, turned it on and holy cow it was 100%. Just recharged it over night again and holy cow it's 100% again.

Any idea why it suddenly started to charge to 100%? I didn't do anything to it. Running Calk+Clem combo OC at 1.2.
[G Tablet General] rgrossi:
Mine has gone to 100% a few times but not consistently. Sometimes it tops out around 96% but once in a while it makes it to 100%. I've never seen it happen twice in a row, and I've never drained the battery to 0%. Running Froyo VeganTab btw
[G Tablet General] fidju:
Mine has NEVER gone above 94%. Doesn't matter what ROM I use. If you figure out what did it please let me know!!
[G Tablet General] baoli:
Mine doesn't go to 100% with the wall charger but it does with the car charger...
[G Tablet General] doctorisin:
Mine will go to 100% every time... but when it's at 100% the led on the tablet is still red. The number then starts to go down to 96 or 94% and THEN the led turns green. Pretty funny stuff.
[Xoom General] zehkaiser:
I'm running the leaked 3.1 for WiFi. I've had it on there since Friday evening without any issues. Yesterday I installed the OC kernel and didn't have any problems. Played games on it, emailed, and texted for around 5 hours. Plugged it in and went to bed. Got up this morning and tossed it in my backpack. Got to work an hour later and noticed it was rebooting constantly. I wiped data/cache and it's still rebooting. Should I start with restoring the 3.1 stock kernel? And does anyone have the .img file?
[Xoom General] cwizardtx:
Personally I would restore it back to factory stock, using the images supplied by Motorola. Afterwards, let the real 3.1 download and update via OTA and then see if you can get normal usage out of it.

Spontaneously rebooting and constantly rebooting can only be determined to be a side effect of overclocking. If the device was meant to run at 1.5ghz I think Motorola would have just released it that way.

After a week of "normal use", go back to tinkering if you feel like it's safe and worth possibly bricking your unit.
[Xoom General] jiwengang:
Looks like a problem from oc.

Normally the reason why manufacturer did not put the cpu as 1.5G out of box is because for different cpu chips, their capability varies. So if you are manufactuere, you want to set your clock at a level when the instable % of cpu is very small

When it goes to 1.5G by users, the instablity may / may not occur to some users. Unfortunately, it looks like this is the case here.

That being said, it is not saying that your cpu is the one that not capable of running 1.5G. It has something to do with voltage too. The voltage at 1.5G is purely tested using kernel developer's lab and that result definitely will vary.

If I remember it right, oc kernel developers will need to tune down voltage at each cpu level to see the minimum stable voltage to cpu to switch at this frequency, so that your battery won't be killed running 1.5G at very high voltage.
[Xoom General] zehkaiser:
I'll revert to stock 3.0.1. I just load the 4 images using fastboot, correct?

Also, I initially removed the OC, but still had the kernel installed. I thought that was the problem, but restoring stock speeds didn't solve the problem.
[Thunderbolt General] ajd88:
I just called Verizon and told them after updating I have been getting random reboots. The tech said its happening to certain phones and is sending a replacement, no questions asked. Im sure my phones not defective I agree with those that say its a radio issue. I even mentioned that to the tech and he said he doesn't think so. Kinda sucks I got to restore to stock, and reroot and what not. I'll be sure to let everyone know if the replacement has the same issues.

Update: Just so you know I've gotten two replacements, and it didn't help my situation. So no point in getting one unless you got a little cosmetic issue with your phone. Htc is working on a fix for these pesky reboots. It's in testing stages right now supposedly.

Sent from my Thunderbolt
[Thunderbolt General] sublimaze:
It may be a pain to return to stock & root the new phone, but at least verizon is swapping your phone for free. It wouldn't surprise me if they didn't try to blame it on the owner & charge for the exchange
[Thunderbolt General] ajd88:
Yeah the tech was real cool about it. Free overnight fed ex and everything.
[Thunderbolt General] TheStick13:
Do you have to send your current phone back to them, then, or what?
[Thunderbolt General] GutterIsATool:
Interesting that they're doing this. I thought this was happening on all TBs, not just individual ones. Maybe I should call. Anybody else had this experience with the techs? Or did ajd88 just happen to catch a tech that had already put in his 2 weeks notice and didn't care.
[Thunderbolt General] phatal:
I called this morning. Having a new one next-day shipped to me. My phone has become unusable.
[Thunderbolt General] FoxRacR17:
My phone has rebooted maybe 3 times total since I installed the leaked radio when it first was leaked, you guys think I should try and get a replacement just to be on the safe side?
[Thunderbolt General] ericatomars23:
While my phone isn't randonly rebooting it does loose 4G all the time, rarely goes into 3G and 1x seems to be the norm. I live in Chicago so I know it has a solid 4G signal. Wonder if it's worth the trouble of swapping out. But knowing my luck they will give me a refurbished phone...
[Thunderbolt General] cavillis:
in my experience, verizon has always been really good at replacing phones. I had a droid since launch day before upgrading to my TB, and it had been replaced 2 times.

The first time the camera stopped focusing, the second time it just stopped turning on.

I walked in to a VZW store on a Wednesday, and I had fedex at my door delivering new phone on thursday afternoon. badass!
[Thunderbolt General] dalrym05:
You know he funny thigh here is. It probably is happening on all thunderbolts or some people just arent ppaying attention and not realizing that this is happening. It even happens on my wife's fascinate. So ineradicable of sending back my non defective phone that random rebooted once in a while for a "refurbished" phone. Ill keep my new out of box one. Not one someone else has allready had. Just because of a software issue.
[Thunderbolt General] ProTekk:
Well it seems like I get the short end of the stick with VZW on a daily basis. I called and explained it all to the rep and explained how this is a known issue and that there are plently of reputable community sites (like XDA) confirming this and there is rarely a common thread between two devices. Apparently, the rep I spoke to, said that this isn't a known issue.

Got told to factory reset and if it comes down to an exchange, I'd be getting a "certified like-new device" a.k.a. crappy refurb. Again, IF it comes down to that. Awesome. Now they want me to wait it out and see if it keeps acting up. Fun.
[Thunderbolt General] ajd88:
I asked the tech if i was gonna get a refurb, he said no. He better not be lying.

Of course theres a gb leak right after, probably with a new radio that fixes it lol.
[Thunderbolt General] ERIFNOMI:
You'll most likely get a "Certified Like-New" It's a refurb. But, a refurb with a working power button is better than what I have now so I'm going to give this a go.
[Thunderbolt General] Busphan:
I just got the same response. Tech support said not a known issue. They want me to see if I can make it happen again. I guess random reboot isn't telling. I know they have to go through their troubleshooting process and I'm not upset about that, but i can see where this is going. I won't get another reboot today which will tell them I don't have a problem. Alright, I'm off the soapbox.
[Thunderbolt General] ajd88:
Yeah my power button is F'ed too. Whatever if they send me a phone thats in worse shape then the one i got ill just send it back rather than my old one.
[Thunderbolt General] ajd88:
The guy i spoke to asked if I did a factory restore, I lied told him yes. So there was no troubleshooting. I told him its all over google, he put me on hold came back and said he looked on google and confirmed with me he sees that some people are having problems. After that he told me he was confident a new device would solve my problems and thats it. I guess i might have just got lucky.
[Thunderbolt General] ece4free:
It is possible that physical defects in the phones are contributing to the issue. Something like a bad run of filter components could cause the radio to operate ever so slightly out of spec, but still within QA tolerances. Then, if they then tweaked the radio parameters a bunch in the update, it could have pushed the performance requirements of the RF hardware closer to the device tolerances - suddenly revealing a whole bunch of bad components they did not see previously.
[Thunderbolt General] papi92:
I got my new phone today and no reboots and my screen is a lot nicer and brighter. I'm happy
[Thunderbolt General] HarlyFan:
Can someone explain the nature of the reboots that they are experiencing? I had a reboot on Friday but it was much more then just a reboot, after the phone was finishing powering back up I had no ability to call out as if there was no service. I tried numerous battery pulls and even had Verizon do a reset on there end, nothing helped yet I was still able to receive and send data. Finally after about an hour my service was back. Then the same thing happened again yesterday, I went through the same processes with no success yet. I have tried all the different radio choices and nothing is working, does anyone have any suggestions?

Thanks!!!

Also I am rooted and using the stock rom
[Thunderbolt General] micompcs:
Couple different things I'd like to point out. Most vzw employees at the sales level will replace your phone if they actually see it reboot on its own. Some, though, chalk it up to being just a part of the device. I, myself, am a vzw employee and would most definitely exchange your device if its rebooting. However, rooting your phone voids the manufacturers warranty, so you better have insurance. Also, certified like news are not refurbished phones. They are phones that are brought back within the 14-day return policy because the customer either didn't like it or didn't understand how to use it. They're cleared out, tested, and repackaged as CLNRs. Certified pre-owned are, in fact, refurbished. Just thought I'd clear that up.

Sent from my HTC RootedBolt running CM-7.0.
[Thunderbolt General] ajd88:
Well looks like the tech I talked to had some kinda idea what was going on. We have a new radio leak that for me has fixed reboots completely. It seems that a ota update will hit soon. :)
[Thunderbolt General] patches152:
the build from which the leaked radio came from will most likely fail due to the fact that none of the testers can dowload it OTA to actually test it. results are due like next week sometime, and nobody i talk to has been able to install it. but i'm glad the updated radio file fixes the issue. unless they figure out why it won't load OTA, it won't pass.
[Thunderbolt General] ajd88:
We are getting some kind of ota that's hitting the 15th. So sais Jcase. I figured that the 15th would be the day seeing as they are discontinuing free hotspot. Honestly I'm good with the leaked radio and some bamf sense 3.0 previews. I'm just glad the reboots are done.
[Thunderbolt General] patches152:
hotspot ending and software update are unrelated. also, the testing cycle isn't even done until around the 15th, so they wouldn't have a release date for something that hasn't passed testing yet. IF this build passes, then it'll be a week or two after that when we get the OTA. i'll see if i can get a change log for the build, it's got like 20 something fixes in it, which is a lot for a MR update.
[Thunderbolt General] Dspradau:
I had a lot of reboots before I rooted and now I'm reboot free. :)
[Thunderbolt General] hammer4203:
Someone tell me if ur in a 3g area and know they r testing 4g. My phone went nuts a week ago and so did the wife's. I believe it's in the 3g, 4g hand off. They have been installing equipment in my area.
[Thunderbolt General] jbcarboni:
me too

I just switched from Sprint to VZW on Thursday and bought thunderbolts for the wife and I. We are in an area that is getting 4G next week... She started complaining that her phone was randomly rebooting and I thought it was just her phone. While talking to her my phone rebooted...

Sent from my ViewSonic Gtablet running BOS 3.1
[Thunderbolt General] ILMF:
Ditto. Still stock, though. I don't think its root per se, but the process.
[Thunderbolt General] jakaro:
i just had four!!!! ****ing reboots in 30 minutes!!! GOD DAMMIT!!!

hmm, time for MR2 and gingerbread maybe?
[Thunderbolt General] DeathAdder666:
I live in Sacramento and work in Marin (North of SF) and both were 3G areas until recently. I know they are testing.g because I saw the announcement that both were going 4G on the 16th. Sac is pretty solid 4G right now and the past week or so. Marin is up and down still.

I also saw 4G working out towards Davis (about 20 miles West of Sac) so I think we are solid here now.
[Thunderbolt General] jbcarboni:
At Noon today 4G arrived. My phone has now been rock solid with no reboots in 23 hours.
[Thunderbolt General] Docarut:
To the Gurus more knowledgeable than I,

I just ordered supposedly new TB factory sealed from Verizon. Who knows if refurb, insurance replacement or actually new. Question is if the update that seems to cause reboots is offered can I just refuse to download and wait for the OTA that supposedly is to fix the reboots?

Thanks,

Doc
[Thunderbolt General] Jwilder517:
My TB has been rebooting since I got it on its release date. It started with just a couple of times a day (that I noticed), but it got a little insane after the OTA -- it seems like the more I use it, the more it reboots. 2-3 times an hour was about the norm ... and it took about 5-10% battery with every reboot.

I talked with Verizon tech support several times, but they (every time) said there were no issues with the phone, but I should wait for the update (? how could an update fix a phone with no issues, I kept asking?). They were no help.

I walked into a Verizon store yesterday, talked with a rep about an unrelated problem (screen seems to be separating on right side - it has a slight click and is not always responsive to touch) and I complained again about the rebooting. The rep tells me that there were a number of TBs that had overheating and rebooting issues (before the OTA) and that the problems associated with the OTA just made it worse. He set me up for a replacement right away.

Hadn't really thought about it before he said that, but my TB gets pretty warm pretty quick, for pretty normal use. I'm not sure how accurate it is, but Battery Indicator Pro gives the battery temp -- to turn the phone on from sleep, battery is usually about 24-25C ... after a couple of minutes use (FB, Internet, Email, etc), it is usually in the high 30s.

Either way - I wasn't sure if this guy knew what he was talking about or if it just fit with what I was already seeing ... but I get a new (to me) phone out of the deal and will hopefully not have to deal with a lot of the bugs this phone has had so far.
[Thunderbolt General] k2trill:
I qualify. My phone hasn't done anything odd tho.
[Thunderbolt General] Pender1:
Same here, 4G activated on Monday(3 days earlier than it was supposed to) and it's pretty awesome.

My TB rebooted about 3-4 times a day after the update. They gave me a new one with no argument, but it did the same thing and had a busted speaker, so I sent it back and got a 2nd replacement. So far I've had the newest one 3 days and no restarts.:cool:
[Thunderbolt General] zx12dak:
I am on my 3rd Bold. All of them reboot. It rebooted 8 times yesterday and its a week old. Just 4 times today. Tired of this BS. And yes Verizon KNOWS there is a problem with them.
[Thunderbolt General] :
Can anyone confirm what software version they have on the replacement phone?
[Thunderbolt General] thegeebo:
My Thunderbolt suffered random reboots after I installed the new RUU. I unrooted it and cleared all my data, and swapped it for another one. Now I am running Das BAMF with new radio, LeanKernel 2.5, custom undervolt, and everything is super awesome with great battery life.

Trade in your random reboot TB!
[Thunderbolt General] ajd88:
Well restoring to unrooted stock will re enable warranty correct?
[Thunderbolt General] sublimaze:
Yep
[Thunderbolt General] micompcs:
Technically no, just don't mention the aforementioned root and we can't tell. So, theoretically yes, it will. :)

Sent from my HTC RootedBolt running CM-7.0.
[Thunderbolt General] micompcs:
2.2.1. They're all flashed before repackage.

Sent from my HTC RootedBolt running CM-7.0.
[Thunderbolt General] ERIFNOMI:
Thanks for clearing that up. I knew they had two names that were very similar. Either way, you get a somewhat used phone. Still, if it's better than mine I'm in. I called and they said it wasn't a known problem. I said I did a little reading and saw others were having this problem. I was told by the first person I talked to that doing a factory reset would get rid of the software update :/ Luckily I got transferred to someone who knew what they were doing. I was told to do a factory reset, see what happened, and if it happened again I would get a replacement.
[Thunderbolt General] micompcs:
No problem. Sometimes you do have to dive a little deeper to get someone who is a little more savvy when it comes to known issues. We have a resource that gives us a list of known issues, but the problem is that list is not always up to date. Over the phone its a little more difficult, as well, to determine if the issue really is an issue. Hope everything turns out well for you.

Sent from my HTC RootedBolt running CM-7.0.
[Thunderbolt General] davidbudd1:
I called then about this for my wife's phone and they are sending her a replacement. she will have it by wed so hopefully this will resolve the issues.
[Thunderbolt General] Hyper4mance2k:
Mine reboots almost daily. Stock, with no OTA update.
[Thunderbolt General] champaned_out:
can someone confirm Verizon is NOT sending out refurbished phones?
[Thunderbolt General] micompcs:
I just did.

Sent from my HTC RootedBolt running CM-7.0.
[Thunderbolt General] JBAeroEngineer:
are you having to go in and prove a reboot, or is this becoming such a widespread issue that they're taking it on faith?
[Thunderbolt General] ajd88:
They took faith in my issue. I did everything over the phone. I told him how random the reboots were. Three one day none for the rest of the week. Actually I wouldn't call it rebooting the device would just shut off. Anyways seems as though it dependant on who you talk to. I'm sure its becoming a know issue on verizons end because of more people calling them up. I've been running gb leak and haven't had a single issue with this radio shutting my phone off yet. So maybe it'll just take an update to fix these issues. BTW other people are still getting reboots on gb radio.
[Thunderbolt General] kwiggington:
Well whoever runs the quality control needs fired i went through 7 droid x's before i got sick of it and sold the last like new one before i even activated
[Thunderbolt General] ludionis:
Verizon Replacements...

Here's the scoop on how it <i>should</i> work:

1: If you are within 14 days of purchase, you can swap out your phone for a new one. As long as you don't make a model change, no charge/no harm/no foul, but probably won't fix the issue.

2: If you are outside your 14 days, and the rep doesn't check the Known Issues List (basically, doesn't know how to do their job), they will replace with a CLNR (Certified Like New Replacement). This again probably won't fix the issue.

The reason this is a pointless step, is the software is to blame. Changing hardware won't affect the problem. This has been reported to HTC, they have received devices affected with the issue for testing, and ideally, a future MR will repair the problem. If the rep does their job, they should check the known product issue list, verify it is a known issue, and deny a replacement based upon the fact that it <i>won't help anyway</i>. Just an FYI to policy....
[Thunderbolt General] snicklet:
Why not? +10 char
[Thunderbolt General] ludionis:
Better check your sources, there is no guarantee that CLNRs are all returns, or that CPOs are all refurbed. Either one could be either, device history is not provided, and we are instructed to tell customers if asked that it could be a reburb, or a return, or in rare cases a new unit, the history is not given.