does it work with stock rom?

Have you tried wiping several tiems before installing a rom?

I hope someone else can give you more specific pointers

Regards

Christian

My best guess would be your radio version. There are ways of rooting that will break data, and other ways that will not. I would suggest looking at your radio version, making sure it's compatible with your network, and if not, flashing back to your stock version and re-rooting the way that doesn't touch your radio. That can cause HUGE problems if not done the right way.

@cebrian I did try to flash stock at one time, but didn't help me either. Also, I've installed several ROMs and versions, and wiped, wiped, rewiped, superwiped, and nothing.

@1madfitter I'm on T-Mobile Puerto Rico, and running 5041 baseaband. I've flashed several radios since I rooted about a year ago. I'm not an Android expert, but I am fairly familiar with the rooting/flashing process.  I rooted with "The Dude's Method", then, when I installed Brett's Froyo, I rerooted with Z4.

First I thought it was just T-Mobile here, because that happened almost at the same time that we transitioned to 4G, but then I have friends with rooted Androids (although not the same phone, but all TMo) that have their Network stuff working flawlessly.

Is there some parameter on any of those config files or sqlite databases that I should check?

Thanks for the help guys!

That's an odd one. As far as where network location is in the system, I know where it is, but that can't be the issue because everytime you flash a new ROM, it changes with the ROM. I would hook up your phone to adb and run logcat, see what kind of errors you are getting while trying to get network location to work, then google the error you get. Other than that, I would have to say something screwed up in the hardware. Not really sure of anything else to help off the top of my head?

@1madfitter I think I found something. I just don't know how to fix it. Plugged in logcat, started a diagnostic tool that I found on the marked, and when it starts querying the network location, magic happens:

RIL_REQUEST_GET_NEIGHBORING_CELL_IDS = RIL_E_REQUEST_NOT_SUPPORTED

Currently, RIL_REQUEST_GET_NEIGHBORING_CELL_IDS causes the RIL to crash,
due to backward compatibility issues.
This fix is a temporary hack to make the API return REQUEST_NOT_SUPPORTED
Command Exception till the compatibility issues are fixed.

I think @madfitter is on the right track. What service are you using? What country? What radio version. You can find out by going to /settings/about. it would be the baseband I believe.

Thanks @ngiordano! It's on the previous comment:

"I'm on T-Mobile Puerto Rico, and running 5041 baseaband"

I just read here:

http://groups.google.com/group/android-framework/browse_thread/thread/a49109594c0ffacb/d988bb287e94ac7e?fwc=1&pli=1

...something about permissions problems. My phone is rooted (with Z4), so I guess my account has root/admin privileges.

Just a question: When you flash a ROM, does it delete all files prior to installing the new version, as when you do a fresh Windows or Linux install. or the process just updates certain files, leaving old content floating around. If that's the case, maybe I have a conflict of some sort.

Thanks for your help.

And that is the dump from ADB...

This is a fragment of the dump included above:

D/QCRIL_MSC (   65): "RIL"=>"Android" [ label = "RIL_REQUEST_QUERY_NETWORK_SELECTION_MODE - Automatic"];
D/QCRIL_MSC (   65): "Android"=>"RIL" [ label = "RIL_REQUEST_GET_NEIGHBORING_CELL_IDS"];
D/QCRIL_MSC (   65): "RIL"=>"Android" [ label = "RIL_REQUEST_GET_NEIGHBORING_CELL_IDS - RIL_E_REQUEST_NOT_SUPPORTED" ];
D/QCRIL_MSC (   65): "AMSS"=>"RIL" [ label = "CM_SS_EVENT_SRV_CHANGED"];
D/QCRIL_MSC (   65): "RIL"=>>"Android" [ label = "RIL_UNSOL_RESPONSE_NETWORK_STATE_CHANGED acquired on UMTS"];
D/QCRIL_MSC (   65): "Android"=>"RIL" [ label = "RIL_REQUEST_OPERATOR"];
D/QCRIL_MSC (   65): "RIL"=>>"Android" [ label = "RIL_UNSOL_SIGNAL_STRENGTH"];
D/QCRIL_MSC (   65): "RIL"=>"Android" [ label = "RIL_REQUEST_OPERATOR - T-Mobile"];
D/QCRIL_MSC (   65): "Android"=>"RIL" [ label = "RIL_REQUEST_GPRS_REGISTRATION_STATE"];
D/QCRIL_MSC (   65): "RIL"=>"Android" [ label = "RIL_REQUEST_GPRS_REGISTRATION_STATE - Registered (Home network), UMTS"];
D/QCRIL_MSC (   65): "Android"=>"RIL" [ label = "RIL_REQUEST_REGISTRATION_STATE"];
D/QCRIL_MSC (   65): "RIL"=>"Android" [ label = "RIL_REQUEST_REGISTRATION_STATE- Registered (Home network)"];
D/QCRIL_MSC (   65): "Android"=>"RIL" [ label = "RIL_REQUEST_QUERY_NETWORK_SELECTION_MODE"];
D/QCRIL_MSC (   65): "RIL"=>"AMSS" [ label = "cm_ph_cmd_get_ph_info()"];
D/QCRIL_MSC (   65): "AMSS"=>"RIL" [ label = "CM_COMMAND_CALLBACK"];
D/QCRIL_MSC (   65): "AMSS"=>"RIL" [ label = "CM_PH_EVENT_INFO"];
D/QCRIL_MSC (   65): "RIL"=>"Android" [ label = "RIL_REQUEST_QUERY_NETWORK_SELECTION_MODE - Automatic"];
D/QCRIL_MSC (   65): "Android"=>"RIL" [ label = "RIL_REQUEST_GET_NEIGHBORING_CELL_IDS"];
D/QCRIL_MSC (   65): "RIL"=>"Android" [ label = "RIL_REQUEST_GET_NEIGHBORING_CELL_IDS - RIL_E_REQUEST_NOT_SUPPORTED" ];
D/LocationMasfClient(  108): getNetworkLocation(): Returning cache location with accuracy -1.0
D/dalvikvm( 9007): GC_FOR_MALLOC freed 1660 objects / 354328 bytes in 179ms
D/dalvikvm(  184): GC_EXTERNAL_ALLOC freed 13875 objects / 646832 bytes in 235ms
D/dalvikvm( 9007): GC_FOR_MALLOC freed 5328 objects / 489264 bytes in 92ms

I just flashed a stock sbf, just to reset every setting and file to stock. Nothing... My guess is hardware failure. I even tried the "Motoblur" utility to "Locate Your Phone"... and nothing happened. My phone appeared in an empty map.

I'm calling warranty today, which I should have done long time ago. Let's see what happens. Thanks a lot for your support.

SUCK

It sucks even more that I just spent 1 hour with an online rep, and the browser froze. I printed the transcript, becuase I don't want to go again through the: Turn off the phone, remove sim card, go to settings, etc.

At least, my phone appears "stock", so I would have issues with warranty.

Hi guise!