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

Root Rooted GB (.596) losing all connections

varaonaid

Android Enthusiast
Sep 4, 2009
621
128
VT!
Hello,

I'm running the rooted GB (.596) on my DX. Everything is pretty much OK (other than the sucky battery life) except the fact that almost everyday, I lose all connection. I have good signal (3-4 bars) but they're grayed out and whether or not I have wi-fi available, no connection is there and the 1x/3G connection is likewise gone. If I try to make a call, it immediately disconnects. I've tried turning off and on both wi-fi and 3G data but the only thing that works is a complete reboot. Does anyone else have this issue or have any ideas what to do to fix this? I find out after the reboot that I've also not been receiving email, texts or anything else that would normally be "pushed" to the phone as I receive numerous numbers of both once the blue data/phone connection is restored.

I'd be grateful for any assistance or advice. Thanks in advance.
 
Well, I'm sorta glad to hear I'm not the only one but that likely means it's some strange obscure bug with GB. Frustrating. There are features that I love with GB & miss them when I'm back on Froyo not to mention the newer versions of several programs that only run of GB.

Maybe Apex 2.0 will have ironed out the issue. I'm looking forward to trying it sometime soon when I get a chance to flash it.

If anyone has any suggestions or is having the same issue please post so we can get some idea of how widespread it is.
 
Upvote 0
same issue here. Drop out has been an issue with some devices since GB dropped in March.

The only fix i too have found so far is a reboot. One day i'm going to try sbf'ing back to stock and go up through the process cleanly and see if that helps. I just haven't had time to turn lose from my phone yet.


i was on rooted froyo/then .573 leak/then .588 leak/ then .595 leak..then jumped to .596 leak so maybe somewhere in there things got cluttered.
 
Upvote 0
same issue here. Drop out has been an issue with some devices since GB dropped in March.

The only fix i too have found so far is a reboot. One day i'm going to try sbf'ing back to stock and go up through the process cleanly and see if that helps. I just haven't had time to turn lose from my phone yet.


i was on rooted froyo/then .573 leak/then .588 leak/ then .595 leak..then jumped to .596 leak so maybe somewhere in there things got cluttered.

Good luck. I've sbf'd about three times and installed the two part rooted file to no avail. Seems like for some reason data connectivity sucks on this build.
 
Upvote 0
same issue here. Drop out has been an issue with some devices since GB dropped in March.

The only fix i too have found so far is a reboot. One day i'm going to try sbf'ing back to stock and go up through the process cleanly and see if that helps. I just haven't had time to turn lose from my phone yet.


i was on rooted froyo/then .573 leak/then .588 leak/ then .595 leak..then jumped to .596 leak so maybe somewhere in there things got cluttered.

I did a single clean install but have the problem. I wonder if it's particular devices within a line of devices (ie some DX's but not all) or if all DX's are affected or all of GB. It's darn annoying, I can tell you. It's ALWAYS when you need to make that "quick call" that it's not got any signal at all and waiting through a reboot on my phone takes awhile. Frustrating. I guess I can cross my fingers and hold my breath that the phone that they're sending me that should arrive Wed. will be better. Hopefully it won't have the current issues that this replacement does. :(

I wish we could trace down the problem...if it's GB, another program conflict, root or??? But I guess that isn't going to happen, eh?
 
Upvote 0
I wonder if it's particular devices within a line of devices (ie some DX's but not all) or if all DX's are affected or all of GB.

42/10 is my date stamp on the my dx, i have the same problem as is mentioned in the OP...
what is your guy's date stamp? found on sticker behind battery.. maybe it is like what varaonaid was thinking and it's a certain line/date ... be nice to discover so i could yell at VZW more.
 
Upvote 0
Still haven't gotten a consistent connection since this morning. I've tried:
Rebooting
Pulling the battery for 10 minutes
Clearing the cache
Clearing the dalvik cache
Turning airplane mode on and off
Using *228 option 1
Using *228 option 2
Change battery mode to "Performance"
Probably a few other things that I forget

The strange thing is that every once in a while, the blue 3G will come on...and then go away again. It's like it only connects when the phone wants to sync. I think the next step is a factory reset. :(
 
Upvote 0
I would bring it in to VZW and tell them what's going on with the phone and that you have reset it many times with no luck. It may be a fault in your radio and will have to have the phone replaced. That would be your last option and my last bit of advice I can give you.

EDIT: b3nder my date stamp is Sep 14, 2010. In case you wanted to know....lol. And I have no radio troubles with mine. In fact I get great reception 95% of the time.
 
Upvote 0
I would bring it in to VZW and tell them what's going on with the phone and that you have reset it many times with no luck. It may be a fault in your radio and will have to have the phone replaced. That would be your last option and my last bit of advice I can give you.

EDIT: b3nder my date stamp is Sep 14, 2010. In case you wanted to know....lol. And I have no radio troubles with mine. In fact I get great reception 95% of the time.
Yeah, if doing a factory reset doesn't work, that's the plan. If I'm lucky, maybe they'll give me an X2 as a replacement... :D
 
Upvote 0

Yes. That only applies to insurance claims. And you can bet they will be looking at every claim under the microscope to be sure people aren't trying to get a freebie.

The article also states "the DROIDX2 is the current replacement phone until they receive another batch" which suggests this is only a temporary move till they get more DX1's in stock.
 
Upvote 0
So, I ended up having to SBF back to 340 and then re-upgrading to GB, but it is working at the moment. I also tried applying the 1-part zip (hoping that would allow me to keep the .07P radio), but it didn't work. I got stuck at the Droid eye. I didn't have a whole lot of time to mess with it, so there may be an upgrade path that will allow you to stick with the .07P radio.
 
Upvote 0
So, I ended up having to SBF back to 340 and then re-upgrading to GB, but it is working at the moment. I also tried applying the 1-part zip (hoping that would allow me to keep the .07P radio), but it didn't work. I got stuck at the Droid eye. I didn't have a whole lot of time to mess with it, so there may be an upgrade path that will allow you to stick with the .07P radio.

If you want the .07p baseband, just completely install the 2 part update, and then use this:

https://www.dropbox.com/s/yfjl383zn5tazq4

I think someone posted this yesterday too, just can't remember which thread.
 
Upvote 0
I am having this problem as well on Apex RC2. Airplane mode usually fixes it. I think I am going to switch back to gingerblur and see if it happens as often and if it does I'll try to get a replacement device. Maybe some of our radio's just don't play well with GB, this device's radio on FroYo variants was super.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones