• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Where is the fix for GB?!

I'm curious, you were on GB right? Did you use the Monster.zip file by TBH to get to CM7, or did you sbf to 2.3.340 and then use the Monster.zip file, or did you sbf and go the cvpcs method???

EDIT:
Did you flash the monster zip twice as the directions say to do (assuming you used the Monster.zip file)?


I used the Linux CD boot to SBF method to get back to Froyo .340. Then just rooted, used DX2 bootstrapper to boot into CWR, then used the last nightly build, basically CVPCS method.

Originally got to .12 using P3Droids, SBF then 2 part .596 to get GB.

But so far CM is working great, thanks for the suggestion even though I'm not on the baseband I was shooting for. At least I can test now wether the connection problem is related to Gblur.
 
I used the Linux CD boot to SBF method to get back to Froyo .340. Then just rooted, used DX2 bootstrapper to boot into CWR, then used the last nightly build, basically CVPCS method.

Originally got to .12 using P3Droids, SBF then 2 part .596 to get GB.

But so far CM is working great, thanks for the suggestion even though I'm not on the baseband I was shooting for. At least I can test now wether the connection problem is related to Gblur.

You should be on .07 then because sbf'ing 2.3.340 should have brought you back to .07......I wonder if you missed a step somewhere along the line.

If you still want to get .07, then flash TBH's Monster.zip; you will have to flash it twice because you will get a radio error on the first attempt, but when you reboot the phone and go back into CWR, you will flash it again and it should install the .07 radio.
 
You should be on .07 then because sbf'ing 2.3.340 should have brought you back to .07......I wonder if you missed a step somewhere along the line.

If you still want to get .07, then flash TBH's Monster.zip; you will have to flash it twice because you will get a radio error on the first attempt, but when you reboot the phone and go back into CWR, you will flash it again and it should install the .07 radio.

Thanks, that's what I thought to. I checked just after I SBF'd and it was at .12, not sure how that could happen. Not sure how I missed a step, seeing as the bootable CD did all the work. I'm going to sit on CM7 with .12 for now and see what happens.

Thanks again.
 
Overall Gingerbread is the most stable, least buggy update for the Droid X to date. The Froyo update was plagued with tons of massive bugs, all of the recognized (ie none of the one-time-fluke-sucks-to-be-you bugs) are very minor. The only bug I have experienced on Gingerbread is that it frequently won't stay off when I turn it off. After a minute or two of sitting untouched it will spontaneously start itself, however, I would classify this a far better the Froyo random rebooting issues.

Please stop complaining about GB, it is a very solid update, and if you have big issues with it, DON'T JUST LIVE WITH IT, take it in to Verizon for a replacement, because that is not par-for-the-course on this update.

GB is the most unstable most buggy smartphone release I've ever had. I'm having dozens of issues. Some major. Some minor. None of which I had with Froyo. The biggest one is that I keep losing 3g and outgoing phone capability. A reboot restores the data network and the ability to make calls. This is is a catastrophically serious bug that can prevent you from dialing 911. A Verizon rep told me this evening is is a known problem and that it is one of the reasons they *HALTED* the GB update to the rest of the x's. Fortunately my wife's phone does not have the update when you do the firmware check on her phone, it says it's up to date.

I don't know where you got your information, but GB is not stable and bug free by a long shot!
 
Actually you are the one complaining. We are just reporting our experiences and trying to get a fix, what baseband are you on?

How do I downgrade to .07? I'm on Cm7?


.12p... And my comments were not directed at anyone in particular, it is just frustrating to hear some people (not everyone) proclaiming that the Gingerbread update is crap, yet they don't seem to remember/know that the first Froyo update was far worse...
 
GB is the most unstable most buggy smartphone release I've ever had. I'm having dozens of issues. Some major. Some minor. None of which I had with Froyo. The biggest one is that I keep losing 3g and outgoing phone capability. A reboot restores the data network and the ability to make calls. This is is a catastrophically serious bug that can prevent you from dialing 911. A Verizon rep told me this evening is is a known problem and that it is one of the reasons they *HALTED* the GB update to the rest of the x's. Fortunately my wife's phone does not have the update when you do the firmware check on her phone, it says it's up to date.

I don't know where you got your information, but GB is not stable and bug free by a long shot!


I am sorry if my mostly rhetorical rant offended anyone however, from what I have seen/read/heard Gingerbread does not have many bugs, most to all of which are minor. And you a certainly entitled to make up you own mind, but for me Verizon support does not make for a very reputable source. I have heard more BS from them then anywhere else.

For example, this conversation occurred about two weeks before the GB update was released:

Me: So is there an estimated time to the Android 2.3 update?
Verizon: Google is responsible for writing the updates for each phone, as such the update will be released for the DROID X when they make the update.
Me: ... Okay thanks.

I won't bother to point out everything that is wrong with that statement...
 
I am sorry if my mostly rhetorical rant offended anyone however, from what I have seen/read/heard Gingerbread does not have many bugs, most to all of which are minor. And you a certainly entitled to make up you own mind, but for me Verizon support does not make for a very reputable source. I have heard more BS from them then anywhere else.

For example, this conversation occurred about two weeks before the GB update was released:

Me: So is there an estimated time to the Android 2.3 update?
Verizon: Google is responsible for writing the updates for each phone, as such the update will be released for the DROID X when they make the update.
Me: ... Okay thanks.

I won't bother to point out everything that is wrong with that statement...

It's not that I'm offended. You're opinion is not supported by the posts in this forum. There are way more issues, serious, and frequent, posted about GB than there were about Froyo.

Lots of people are experiencing the 3g dropout and inability to make phone calls until a reboot. This is not an opinion. The GB update *IS* halted and is not being rolled out to the any more X's. This is not an opinion. It is fact.

Whether it was halted by VZ or Motorola, I don't know, but I'll speculate that they had to because it can render Xs incapable of dialing 911.
 
It's not that I'm offended. You're opinion is not supported by the posts in this forum. There are way more issues, serious, and frequent, posted about GB than there were about Froyo.

Lots of people are experiencing the 3g dropout and inability to make phone calls until a reboot. This is not an opinion. The GB update *IS* halted and is not being rolled out to the any more X's. This is not an opinion. It is fact.

Whether it was halted by VZ or Motorola, I don't know, but I'll speculate that they had to because it can render Xs incapable of dialing 911.

It seems that GB works well for a few, has some bugs for others and causes major issues for still more. I don't know if this is because of the variability in individual phones, user install errors or which time zone you're located in, but it makes me concerned to try the upgrade, even the rooted 2-part install (still thinking about it but...).

I hope Verizon can figure this out and issue a patch to help those with the connection issues...losing signal/not being able to dial [911] is BAD.
 
.12p... And my comments were not directed at anyone in particular, it is just frustrating to hear some people (not everyone) proclaiming that the Gingerbread update is crap, yet they don't seem to remember/know that the first Froyo update was far worse...

Not to drag this debate out any longer than it needs to be, but I think it's important to point out that there are users here that did not have to experience the froyo update. I for example bought my X with froyo already on it and it worked fine. And even if Froyo was "so much worse" as you say. That really doesn't make this GB update good. It just makes it suck LESS. For no reason known to me is it acceptable to have a fully functioning phone take a licensed and tested update OTA and suddently a fundamental feature of the phone stops working. (for me it's Mp3 playback but I've seen many other complains including the above mentioned loss of cell signal :eek:)

I understand not everything is going to work perfectly, but how many problems is an acceptable amount? I update my Linux and Windows computer nearly 4-5 times a month and I don't suddenly lose the ability to watch youtube...
 
Not to drag this debate out any longer than it needs to be, but I think it's important to point out that there are users here that did not have to experience the froyo update. I for example bought my X with froyo already on it and it worked fine. And even if Froyo was "so much worse" as you say. That really doesn't make this GB update good. It just makes it suck LESS. For no reason known to me is it acceptable to have a fully functioning phone take a licensed and tested update OTA and suddently a fundamental feature of the phone stops working. (for me it's Mp3 playback but I've seen many other complains including the above mentioned loss of cell signal :eek:)

I understand not everything is going to work perfectly, but how many problems is an acceptable amount? I update my Linux and Windows computer nearly 4-5 times a month and I don't suddenly lose the ability to watch youtube...


Point taken.
 
I came across this thread while doing a google search for 12p baseband issues. I too am experiencing loss of wifi (while 2 foot from the router) and loss of 3g signal. I find it to be irritating at the least. Nothing like hearing your phone go "droid" 20 times in a row for text messages, emails and, oh yeah...voicemails. what a missed call? NOPE..just got 3g back and I missed a call. What if it was my 12 yr old son calling me with an emergency? Hopefully that mid-August fix is a good projected date for a fix. I think this issue could be a serious problem if you lose connection at the wrong time.


Oh, and "Searching for GPS" can be irritating when in an unknown area trying to get somewhere.Been getting that a lot too.

Fingers crossed. Overall, I love Android and Motorola does a pretty damn good job with their products. Let's face it, no matter how many bench tests they do, there will be issues they did not encounter until it is pushed OTA. If things were developed perfectly the first time, there would be no such thing as updates, patches, fixes. Such is life.
 
Back
Top Bottom