Database Info

[Q] Time to speak up

Getting tried of watching my phone reboot. If going back to stock would resolve the issue I would do it. I called big red today and the pinhead I spoke to acted like it was the first time anyone had called about the TB rebooting on it's own. I'm looking at going to a different phone. I really think at this point it is a software issue that they need to correct. Just like with most businesses things are not addressed until they become a problem. So my thought is we should set a date when every one calls in to report their rebooting phones. We do this every week until we get a resolution. Anyone with me?

Wait... You are rooted and getting reboots? Are you on gb? Did you root or install your rom properly? What kernel?
Stock I had no issues. Non-Gb I've had mostly no issues... Some kernels less reliable than others, of course. But to be honest it sounds more like a user issue than a tb issue
Sent from my ADR6400L using XDA App
Sent from my ADR6400L using XDA App

Are you near a Verizon store? Verizon is usually very easy to convince that you need your phone replaced. (Although I think they will only replace it with the same model. But I'm not sure.) My Thunderbolt never reboots on its own but I know it is a problem that many Thunderbolts are experiencing, so maybe yours (and many others) is/are defective. I'm 99% sure if you go into a Verizon store and tell them that it randomly reboots all the time, they'll replace it for you.

I reverted back to stock and haven't had a single reboot or loss of data on three days. Just sayin'.
Sent from my ADR6400L using XDA App

I have read posts where people who are not rooted are getting reboots after they took the update. Have never had an issue with my phone until I took the update. Am going back to stock for a week or so to see if that clears things up.

Funny how VZW is changing their stance on it, almost as if it never has happened. About a month ago I went into a store and they told me that Im not the only one experiencing problems and that there will be a fix within 2 months.
I called VZW tech support and they told me that no one else is having reboots.. . . . I dont get it.

Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)

Can you specify what you mean when you say "both"? I have been getting reboots too - approximately 1 per day - but is there a process to flash each radio independently?
Sent from my ADR6400L using XDA App

sethschmautz said:
Can you specify what you mean when you say "both"? I have been getting reboots too - approximately 1 per day - but is there a process to flash each radio independently?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
No, but each flash has two radios
Sent from my ThunderBolt using XDA Premium App

Silvus said:
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Click to expand...
Click to collapse
Any issues with tethering or gps using the old radios?
Sent from my ADR6400L using XDA App

Silvus said:
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Click to expand...
Click to collapse
I still had reboots with both at .6, currently trying cdma.7/LTE.6.
Sent from my ADR6400L using Tapatalk

It is a hardware issue,that's where the few pricked phone came from,my original bolt had the reboot loop on stock but no one seems to want to hear that,it is a series of phones having the trouble and they are or have replaced most of them,as far as most of the other reboot go that is self made misery by not following directions or not reading to find the fix, this bolt I have now has no reboot issues and it has a mat finish to it,the other one and a few I have seen that had issues had a smooth glossy finish.
Sent from my ADR6400L using XDA Premium App

satseaker said:
It is a hardware issue,that's where the few pricked phone came from,my original bolt had the reboot loop on stock but no one seems to want to hear that,it is a series of phones having the trouble and they are or have replaced most of them,as far as most of the other reboot go that is self made misery by not following directions or not reading to find the fix, this bolt I have now has no reboot issues and it has a mat finish to it,the other one and a few I have seen that had issues had a smooth glossy finish.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I would love to think its a hardware issue, but my phone was solid from day one. Then I took the update and get these random reboot.
Sent from my ADR6400L using XDA App

It is not a hardware issue. It is a problem with the update and how certain phones installed it. Verizon is in the process of making a new update and has been working on it with HTC for a little while now & expect to have it going out this month. For some reason the software does not talk to the towers properly with some models & the hardware does not get the proper info which causes the reboots. Exactly how to tell which phones are affected, I don't know. My friend is trying to find out for me.
I can say that I ran my phone with rooted stock & moved up to the rooted update when it was available which I am still on and I have not had any issues at all besides the low recorded video audio which the update seems to have fixed for me.
My phone is:
Rooted stock & radios w/update
Adrynelynes 4.47 Kernal

I am telling you what HTC said they admit that a certain series is defective hence the snappy replacement. Just cause one Rom works and another doesn't isn't always the Roms fault,ever had a CPU that would run one OS and not another or RAM that worked fine on xp but not win 7 once the defective hard hits its limit it will fail. I have seen hardware work fine overclocked and the exact same hardware crash with half the settings,or a motherboard run suse fine but put Windows on it and it dies a week later. I didn't say they all were defective just one series of them and when they did the update a lot of the phones started to fail and some didn't,so does that tell you hardware or software,if one can run fine and the other fails its either a bad flash or bad hardware. Take your pick
Sent from my ADR6400L using XDA Premium App

I didn't do the update over the air on my other bolt, I downloaded it from HTC and it killed the phone,but the same download is on this phone and it works just fine,not one reboot, and its still stock and not rooted. The other one was dated Dec
10 and this one is dated Feb 11, I would just about guess they tweaked the update to weed out the bad phones faster,makes sense to me.
Sent from my ADR6400L using XDA Premium App

satseaker said:
I am telling you what HTC said they admit that a certain series is defective hence the snappy replacement. Just cause one Rom works and another doesn't isn't always the Roms fault,ever had a CPU that would run one OS and not another or RAM that worked fine on xp but not win 7 once the defective hard hits its limit it will fail. I have seen hardware work fine overclocked and the exact same hardware crash with half the settings,or a motherboard run suse fine but put Windows on it and it dies a week later. I didn't say they all were defective just one series of them and when they did the update a lot of the phones started to fail and some didn't,so does that tell you hardware or software,if one can run fine and the other fails its either a bad flash or bad hardware. Take your pick
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I wasn't aware of HTC stating there was some defective hardware. Never saw any references to it. If thats the case then glad they acknowledged it.

It's definitely not a hardware issue. Its a radio/ signal issue. Verizon does know about it, and is working on getting a new update out there. I know this, for a fact.
Sent from my ADR6400L using XDA App

jett2314 said:
I have read posts where people who are not rooted are getting reboots after they took the update. Have never had an issue with my phone until I took the update. Am going back to stock for a week or so to see if that clears things up.
Click to expand...
Click to collapse
My TBolt is not rooted and before the update I had no problems at all but after the update the random reboots started. Battery life is acceptable but could be allot better.
Called Verizon yesterday and they acknowledge the problem and actually said HTC is aware of the problem and are working on it but have no expected date as to when it will be fixed. I believe it is definitely is a software issue and will be fixed when the official Gingerbread is released. Just my 2 cents.

Major Atrix 2 Problems!

So I've been an atrix 2 user for a few months now and its a great phone...Its rooted and I just updated it with the latest ota update and kept the root and all of that good stuff. But one problem that I have been having with my phone for the past month or so is that my phone will heat up like CRAZY! Then restart and then it wont let me use it. The power button doesnt let me turn the phone on...nothing. The only way I can wake my screen is by putting the power chord in and that just lights it up it doesnt let me use the phone. It shows that everything is functioning in the background I still receive messages and my apps update ect. but I cant use me phone. It goes through this cycle for about an hour then completely kills my my battery after it runs its course. I have no idea whats wrong with my phone. Can anyone help or have any suggestions? Anything would be appreciated!

Sounds to me that you need a new phone. Is it through att? You may need to do a warranty exchange.
Sent from my SAMSUNG-SGH-I997 using xda premium

Yes it is from AT&T I had to do the same thing with my original Atrix, but I traded up for the atrix 2

That doesn't sound good... the OG Atrix had a couple problems with that but I've never experienced it on the A2. You should try for a warranty exchange... look at the noob thread and flash the fxz, apply the OTA update and then take it to AT&T.

Yeah I think thats what I'm going to end up doing...this especially happens when I'm listening to music on my phone it loves to freak out on me. I'm just starting to have my doubts about Motorola because my original Atrix gave me problems and I so desperately hoped that it would be fixed in this version. Is it just bad luck I got 2 phones from motorola that both freak out on me? or is it me?

I'd say bad luck.
I've had 4 A2's and, while none of them were perfect, none of them had overheating problems.
Sent from my MB865 using Tapatalk

drummerkid_167 said:
Yeah I think thats what I'm going to end up doing...this especially happens when I'm listening to music on my phone it loves to freak out on me. I'm just starting to have my doubts about Motorola because my original Atrix gave me problems and I so desperately hoped that it would be fixed in this version. Is it just bad luck I got 2 phones from motorola that both freak out on me? or is it me?
Click to expand...
Click to collapse
My A2 is my first Motorola. I have an htc and two samsung phones and my A2 is by far more stable than any of my previous phones. I would say you have just gotten two bad phones. Do what you want to but i would stick with Motorola. Just giving my two cents.
Sent from my SAMSUNG-SGH-I997 using xda premium

Try cpu master pro and change governor to ondemand.
It works on my a2.
The major problem for me now is sometimes signal dissapear.
Sent from my MB865 using Tapatalk

kojitabe said:
Try cpu master pro and change governor to ondemand.
It works on my a2.
The major problem for me now is sometimes signal dissapear.
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
Interesting if the problem is the governor...
Also for a free way to change the governor use ROM Toolbox (free) and go to CPU Sliders.
Sent from my MB865 using Tapatalk

I really appreciate all the feedback from everyone, what I did so far is that I flashed the stock FXZ file back to my phone then updated and seems to be working like a charm buy I still think its too soon to say how its really doing. Instead of second guessing myself I think Im going to get a fresh A2 today hopefully and I won't have any problems like this again! Thanks to all the help from everyone!
Sent from my MB865 using XDA App

drummerkid_167 said:
I really appreciate all the feedback from everyone, what I did so far is that I flashed the stock FXZ file back to my phone then updated and seems to be working like a charm buy I still think its too soon to say how its really doing. Instead of second guessing myself I think Im going to get a fresh A2 today hopefully and I won't have any problems like this again! Thanks to all the help from everyone!
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
I would also take a good a good look at the apps you use, some apps leave themselves running and take some good resources, and can cause your phone to overheat because of this. take a look at the resources in use from settings --> applications, go to the running apps tab, do this when the phone is hot and see what apps are taking a good bit of resources. Just a thought, as I have had this issue before, not on the exact phone I am on now, since I found the offending app and did not reinstall it the last time I got a replacement of this phone.

I wish I could check it when my phone gets hot, but when it gets to that point my phone boots me out. Not letting me touch it at all :/
Sent from my MB865 using XDA App

Apparently the systempanel app (paid version in the market) can identify which apps were running when your phone rebooted, won't tell you whats causing it but may get you close. I dunno how to use th app very well though but I heard good things.
Sent from my Motorola Atrix 2 with AT&T 4G

I've started having this problem today as well. Two days ago I noticed a very quick drop in battery level to almost nothing after going below 50%. Same thing yesterday and today. Today was the first day that I noticed the severe overheating.
I'm using the SCv5.1 ROM. I've been using it for about a month without trouble, but any chance that's the cause? I'd love to not need to return the phone to ATT.

The only time I experienced these symptoms was after restoring an AtrixBlaze ROM.
Flashed back to stock w/root, then OTA. Restored a backup of RebelROM. No problems since. Was very concerned for a day that it had some how damaged the phone.
I've been through Iphone, Palm Pre and HTC, this phone beats them all except for WebOS which was the software on the Pre. That was an amazing OS with a lot of potential.
Sent from my MB865 using Tapatalk

Using Jimbridgman's advice above, I looked at some of my apps. I had been using Green Power Premium (paid) and it just updated a few days ago. I disabled it and have not had an issue since, but I have yet to go through an entire power cycle.

I bought my Atrix 2 in India yesterday. Everything works like charm except the earpiece. The voice I get from the other party is so shrill that I need to keep my phone away from my ear to understand what they are saying . There are 4 settings in all to change the voice quality of the earpiece but it seems they are of no use. On the last setting, I can even hear my own voice from the earpiece. Also, when I tap my phone around the 3.5mm jack area, I hear a sound that makes me feel that something is loose inside. Is it a known issue or a bug or its just me who’s facing this? What’s the way out? Thanks in advance.

Ics 4.04 hopefully to us too

http://www.xda-developers.com/android/galaxy-nexus-gets-ics-4-0-4-update/

We'll most likely get it once the sources are updated to 4.0.4. It looks like a lot of things have changed in this build too. Maybe performance will increase on our phones?

Source has been pushed.
Sent from my Amazon Kindle Fire using Tapatalk 2 Beta-4

dw9906 said:
Source has been pushed.
Sent from my Amazon Kindle Fire using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
ok guys its here Whitehawkx AOKP 29 is android 4.0.4 maybe its just me but it seems a lot smoother

I just like the fact that multitouch was updated in it for the keyboard issues I was having... Typing drunk on CM9 was messing with everything I needed lol.

Anyone know when the OTA will be out
Been trying different ROMs but then my phone started random rebooting even when I put it back to completely stock and re-locked it. So, I sent it in for replacement. Now my replacement phone at the top of the screen used to say "T-mobile" but now just reads "LG" on the glass. I guess the later phones were no longer branded T-mobile.
One thing I noticed though is when I put in a ROM that worked flawlessly on my old phone it would cause the replacement to have random reboots, force close, and just plain lock up where I would be required to remove/replace the battery to get it to work again. Any ideas or suggestions??? I have only been able to run the stock GB rom successfully.
Any ideas on what the phones issue may be?? Or maybe when the OTA for a stock ICS will be available?
Thanks,
NotinStock

notinstock said:
Been trying different ROMs but then my phone started random rebooting even when I put it back to completely stock and re-locked it. So, I sent it in for replacement. Now my replacement phone at the top of the screen used to say "T-mobile" but now just reads "LG" on the glass. I guess the later phones were no longer branded T-mobile.
One thing I noticed though is when I put in a ROM that worked flawlessly on my old phone it would cause the replacement to have random reboots, force close, and just plain lock up where I would be required to remove/replace the battery to get it to work again. Any ideas or suggestions??? I have only been able to run the stock GB rom successfully.
Any ideas on what the phones issue may be?? Or maybe when the OTA for a stock ICS will be available?
Thanks,
NotinStock
Click to expand...
Click to collapse
1. why are you posting in this thread?
2. some roms/kernels are undervolted, if your phone cant handle it youll get random reboots.
3. nobody knows when ICS will get here, NOBODY. if anyone says they know when it will get here, they are lying. there are no exceptions, EVER!

Loving all the improvements that come with this update. I just installed AOKP build 31 and have had zero issues thus far. Just one thing missing...can't hangout in G+ and we know whose fault that is. Nvidia

Issues with 2.2 update

Let me start off by saying this is my first Android phone that I've used that I actually haven't cared to root (and I started with a Nexus One).
I updated to 2.2 that ATT pushed out last week and while some things have proved, some things seem much worse.
1. Poorer battery life (drains much faster. Had 34% deplete in 3 hours and hardly used my phone)
2. Runs hot! For no apparent reason, my phone will get quite warm under the camera and the phone is simply just in my pocket getting e-mail or push notifications. Nothing crazy and no reason to get so hot (I can feel the heat through my jeans).
3. Multitasking is better but still sucks.
Anyone else having similar issues after updating?
Sent from my HTC One X using xda app-developers app

upyouratrix said:
Let me start off by saying this is my first Android phone that I've used that I actually haven't cared to root (and I started with a Nexus One).
I updated to 2.2 that ATT pushed out last week and while some things have proved, some things seem much worse.
1. Poorer battery life (drains much faster. Had 34% deplete in 3 hours and hardly used my phone)
2. Runs hot! For no apparent reason, my phone will get quite warm under the camera and the phone is simply just in my pocket getting e-mail or push notifications. Nothing crazy and no reason to get so hot (I can feel the heat through my jeans).
3. Multitasking is better but still sucks.
Anyone else having similar issues after updating?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Exact opposite on my device. Take it back to ATT, have them replace it (and tell them you don't want one with the 2.2 update) and then root, unlock, and ROM it.

I'm sorry, mate, but I think your device might have some issues. This update actually made my phone much better.
Sent from my HTC One X using Xparent SkyBlue Tapatalk 2

ILoveYouAll said:
I'm sorry, mate, but I think your device might have some issues. This update actually made my phone much better.
Sent from my HTC One X using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
Ditto, I feel mine is better also, no heating problems either...
Sent from my HTC One X using xda app-developers app

Has anyone noticed that WiFi is always searching even if the option is turned off in settings?
Sent from my HTC One X using xda app-developers app

kyndacrazy said:
Has anyone noticed that WiFi is always searching even if the option is turned off in settings?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Nope. My 2.2 update has really made this phone stellar. Though, I'm taking it back so I can root/unlock/rom. Since Cleanrom is based off the official release, I'll be going that rout.
Multitasking actually works, signal/clarity is quite a bit better, and my battery life is at least twice as good as it was before the update.
Methinks you need a factory reset.

upyouratrix said:
Let me start off by saying this is my first Android phone that I've used that I actually haven't cared to root (and I started with a Nexus One).
I updated to 2.2 that ATT pushed out last week and while some things have proved, some things seem much worse.
1. Poorer battery life (drains much faster. Had 34% deplete in 3 hours and hardly used my phone)
2. Runs hot! For no apparent reason, my phone will get quite warm under the camera and the phone is simply just in my pocket getting e-mail or push notifications. Nothing crazy and no reason to get so hot (I can feel the heat through my jeans).
3. Multitasking is better but still sucks.
Anyone else having similar issues after updating?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yep, I was having the same exact issues along with it never shutting up about wi-fi being available even though I told it not to tell me. Ended up resetting the phone to factory and it runs like a champ now.

I am constantly getting the wifi networks are available notification after the update, which I never got before. Quite a nuisance.

+1 to the Factory Reset. Many times this will clear up the problems that start happening right after an update.

It's easier and faster to go into the battery stats and see which app is misbehaving than it is to post on the forum here.

upyouratrix said:
Let me start off by saying this is my first Android phone that I've used that I actually haven't cared to root (and I started with a Nexus One).
I updated to 2.2 that ATT pushed out last week and while some things have proved, some things seem much worse.
1. Poorer battery life (drains much faster. Had 34% deplete in 3 hours and hardly used my phone)
2. Runs hot! For no apparent reason, my phone will get quite warm under the camera and the phone is simply just in my pocket getting e-mail or push notifications. Nothing crazy and no reason to get so hot (I can feel the heat through my jeans).
3. Multitasking is better but still sucks.
Anyone else having similar issues after updating?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I'm having the same issue. Before the update I could go all day and have 35-50% battery left depending on usage. I updated to 2.20 before going on vacation. I don't have LTE at home but where I went on vacation was LTE areas. Battery drain was 10%+ an hour. I assumed it was LTE using more power. But everything I read said that LTE wasn't that bad. Only way I could stop the drain was to put in airplane mode. I got home Friday and drain is just as bad at home.
Anyway, I'm glad I found this thread.
I don't mind doing a factory reset if it solves the problem. Question is, does it solve the issue?
Thanks.

I will have to agree with some of you and say that the update was a big improvement on a great phone! I also think that when doing an OTA update the results are going to be hit or miss. The OTA worked great for me but I installed it on top of a new, clean and unmolested copy of 1.85. I'm willing to bet that just about everyone with new issues after doing the OTA will see an improvement after doing a factory reset. Having said that I personally would not waste time doing a factory reset, I would suggest flashing the ruu. If you're going to wipe your phone might as well get the best possible outcome for your time.

Reboot issue with JB 4.1.2 vzw newest update on Razr HD

Hey so after a few days of the new update running OK I started having random reboots! I noticed on a few other sites people complaining about the same issue of reboots multiple times of the day! Just wanted to let everyone know a possible solution to the issue! I have went through multiple FDR's and did come to the conclusion that the random reboots for my phone were associated with a new update to the chrome browser and were easily fixed by uninstalling new update and telling it not to automatically update so hope this helps anyone who may be having the same issues!!!
Well so much for that after trying everything its back to rebooting again? I love my phone but seriously considering putting it against a wall!!!

xgshortbus25 said:
Hey so after a few days of the new update running OK I started having random reboots! I noticed on a few other sites people complaining about the same issue of reboots multiple times of the day! Just wanted to let everyone know a possible solution to the issue! I have went through multiple FDR's and did come to the conclusion that the random reboots for my phone were associated with a new update to the chrome browser and were easily fixed by uninstalling new update and telling it not to automatically update so hope this helps anyone who may be having the same issues!!!
Well so much for that after trying everything its back to rebooting again? I love my phone but seriously considering putting it against a wall!!!
Click to expand...
Click to collapse
Never had that issue with the new update. Try doing a factory reset or try the new fast boot files to start fresh. Not sure why chrome would be an issue.try the chrome beta version but I suspect chrome had nothing to do with the reboot just a bad initial update.
Sent from my DROID RAZR HD using Tapatalk 2

Fixed!! I hope!!!
Finally broke down done a fast boot to the new files all is working seems OK anyway know in a day or 2!!!

xgshortbus25 said:
Finally broke down done a fast boot to the new files all is working seems OK anyway know in a day or 2!!!
Click to expand...
Click to collapse
My Wife's phone is doing the Random Reboot thing since the 4.1.2 update as well. I did a Factory Reset on it and it still does the same thing.
I suspect an application is doing it? Because I put the phone in Safe Mode and it never rebooted while in Safe Mode.
But I have No Idea of how to tell which app is doing it, other than to uninstall a random app after every reboot to find out which one it is.
But I would like to try this fast boot option? I know how to get the phone into fastboot, but which files are you redoing? What exactly are your doing ?

Have the same problem. I have done:
SBF 4.1.2
FDR
WIPE
Even tried running a parallel rom with safestrap (bakatang)
The chrome thing did not work
Keeps freezing. Seems the problem is way worse when having the phone play some music.
I am just about unlocking the thing and SBFing back to 4.1.1 but not really interested into unlocking the bootloader. That would be the last choice for me.
If someone knows of some way to fix this, please help, this used to be a great phone...

No problem here with the sfr rom... used for over 1 month now and no problem and my system is always fast...
Sent from my XT925 using xda premium

I've been running some tests for about a week now since I got my RAZR and the results are interesting... I've had lockups and reboots multiple times a day, most often while doing something involving sound i.e. listening to music or playing a game or video. I've tried stock and custom 4.1.2 ROMs and custom 4.2.2 ROMs and it persists so I'm inclined to say its either bad audio software or faulty audio chips. This is everything I've done:
1. turning off sounds (keeping phone on vibrate/silent) pretty much eliminates the random lockups/reboots I got from receiving multiple texts or calls at once. I noticed if I bombarded the phone and made it ring a lot it gave the same results as listening to music but if its just a text or email or call here and there during regular use it the phone works fine.
2. Listening to music, either streamed or local from phone/SD storage and through headphones or speaker, would cause skips and audio cutting out. After a few minutes of this the phone will lock up completely and reboot itself. Strangely enough it happened only rarely or not at all while streaming music via bluetooth to a stereo.
3. I don't think its anything kernel related or if it is its not causing visible errors or wake locks. My battery seems to be just fine through all this.
4. I have tried multiple music/video players, put my SD card with music in another phone and the music plays fine, stock ROMs with nothing disabled/removed still has the issue, custom ROMs debloated and modified also have the issue. I think I've just about covered every base I can as an end user to track down what's causing it but I'm open to suggestions.
I have a replacement scheduled so I will see if that fixes it, I have seen this problem reported quite a few times all over the interwebz but there are also a lot of people not having the issue either so idk. If there are any Devs or anyone skilled in android-fu that can read logcats I will be more than willing to get those for you. Sorry for the essay everyone lol
tl;dr Like others I have freezes and reboots from what seems to me to be an audio software/hardware problem, either built in or from the 4.1.2 update
Sent from my DROID RAZR HD using Tapatalk 2

I am almost sure is kernel related bc I did not have problems in the 4.1.1 sw.
If someone that has an unlocked bootloader could install 4.1.1 from an sbf and tell if the problems are gone, would be great!
here is the sbfs: http://sbf.droid-developers.org/vanquish/list.php
here is the bl unlocker: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
u have to be rooted here: http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit-412/?pid=244281#entry244281
I am not doing that bc I do not use custom roms so dont want to unlock BL. If someone has, this could help much. It is different from using safestrap, because safestrap uses the same kernel, from what I read.

barbaroja said:
I am almost sure is kernel related bc I did not have problems in the 4.1.1 sw.
If someone that has an unlocked bootloader could install 4.1.1 from an sbf and tell if the problems are gone, would be great!
here is the sbfs: http://sbf.droid-developers.org/vanquish/list.php
here is the bl unlocker: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
u have to be rooted here: http://www.droidrzr.com/index.php/t...roid-root-exploit-412/?pid=244281#entry244281
I am not doing that bc I do not use custom roms so dont want to unlock BL. If someone has, this could help much. It is different from using safestrap, because safestrap uses the same kernel, from what I read.
Click to expand...
Click to collapse
I have seen reports that the problem persists even on 4.1.1 but I am unlocked and rooted on stock 4.1.2 so if I get time I can give it a try
Sent from my DROID RAZR HD using Tapatalk 2

anoninja118 said:
I have seen reports that the problem persists even on 4.1.1 but I am unlocked and rooted on stock 4.1.2 so if I get time I can give it a try
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
When I was at 4.1.1 phone was near perfect.
If you are unlocked, please do check. I am debating whether to unlock or not just bc of this. Today it has resetted at least a good 20 times or so.
Thanks for helping!!! Waiting for your results!!!!

barbaroja said:
When I was at 4.1.1 phone was near perfect.
If you are unlocked, please do check. I am debating whether to unlock or not just bc of this. Today it has resetted at least a good 20 times or so.
Thanks for helping!!! Waiting for your results!!!!
Click to expand...
Click to collapse
one solution that has worked for me is silencing the phone or putting it on vibrate and I haven't had a freeze or reboot in almost 2 days... the problem seems to me to be related to audio/sound and not listening to music or watching videos along with silencing ringtones has put a stop to it which kind of confirms my suspicions... I will try and flash back when I can but it'll need a day or 2 of field testing to confirm if its a solution
Sent from my DROID RAZR HD using Tapatalk 2

I can confirm that audio stuff just does worse to the phone. However, I have not had your luck when silencing. Keeps rebooting no matter what. Please let us know when you do.

barbaroja said:
I can confirm that audio stuff just does worse to the phone. However, I have not had your luck when silencing. Keeps rebooting no matter what. Please let us know when you do.
Click to expand...
Click to collapse
looks like a negative on the SBF, tried to restore 4.1.1 and it failed halfway through the flash, now won't turn on... working on reviving it... I really need to replace this thing as its been nothing but a PITA since I got it
old school post from my Thunderbolt via Tapatalk

wow that sucks. I recall reading somewhere that you could actually downgrade your software version if you have an unlocked bootloader.what is the error you are getting? Tried using RAZR utility 1.1? Won't it turn on at all? Maybe a discharged battery? Hope we can solve it

barbaroja said:
wow that sucks. I recall reading somewhere that you could actually downgrade your software version if you have an unlocked bootloader.what is the error you are getting? Tried using RAZR utility 1.1? Won't it turn on at all? Maybe a discharged battery? Hope we can solve it
Click to expand...
Click to collapse
got it revived with Mattlgroff's new 1.2 utility, was able to force it to fastboot mode... the problem seemed to be some kind of partition error, I tried redownloading the sbf files thinking it was a bad file and got the same error so idk what it is since I'm on stock unrooted 4.1.2. My bootloader is already irreversibly unlocked so that won't be a problem lol but I am a n00b to RSD Lite and Moto devices so I'll tinker with it more when I get some free time
edit: I did have a Maxx HD way back at launch for a month or so running stock 4.1.1 and it ran perfectly, so my idea is its kernel/codec/software related. Hopefully a custom ROM (or hell even stock) with Hashcodes Qcom kernel will fix the issue we're having
Sent from my DROID RAZR HD using Tapatalk 2

I talked with vzw service, the assistant said that 2% of the phones were having this issue, wich for this kind of technology is a pretty big number of phones. Suuggested to send it to Motorola but since its rooted its almost sure not to be replaced by them. What is strange is that not everyone is having this issue. I would be almost sure Motorola is going to release a fix for this, but would not count days. Getting kind of frustrated with this phone I used to like so much. Thinking of going the htc route bc this is getting unbearable.

Any news in this? Anyone tried a new ROM that could solve this? Or even a fix?
... or just everyone had another phone lying aroud...

barbaroja said:
Any news in this? Anyone tried a new ROM that could solve this? Or even a fix?
... or just everyone had another phone lying aroud...
Click to expand...
Click to collapse
My wife & I both have this phone and still are constantly being rebooted. This is even after the software update. I have been wiped, factory reset, and everything possible, but I've not called for a replacement yet. Normally I havea worse luck with those.
Wife used to love this phone, now she hates it and hates we changed from AT&T to Verizon since we have no backup Verizon phones. At least we could take the sim out and go to the iPhone that's floating around the house when the phone went to pot before. Makes me really hate suggesting that we go back to Moto phones since that's all that I've used on Verizon.
Wonder if big red will get the new HTC One....

Tried flashing the MR-4 sbf, but did not solve the issue.
Sent from my GT-I9100 using Tapatalk 2

barbaroja said:
Tried flashing the MR-4 sbf, but did not solve the issue.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
If an sbf didn't solve it then it's a hardware problem.you guys are definitely in the minority with this reboot issue.go get a warranty replacement.this phone and moto in general are solid phones.
sent from my xt926 RAZR maxx hd