Database Develop

[Q]How to activate G1 through wifi?

Upon reading the title you probably entered ready to flame me for not using the search button. The reality is though, that is just one of my many problems I'm having. I'll start from the beginning, give you the whole rundown and hopefully you can help, because if I can't figure this out soon I'm going to start smashing things, my G1 being first on the list.
A couple of days ago i was just surfing around, heard about custom ROMS, rooting, etc. so I started my journey. Thinking this would just take an afternoon, at the max, was a mistake on my part. I started here:
[ROM]TheOfficial TMO (US/EU) & HTC ADP - CRC1- Rooted [8/17/09]- v1.5.2-SecurityPatch
Looking at the prerequisites, I realized I lacked both the requirements so I followed that threads link to here:
Easiest How To for: Root, Hero, Recovery, Partition (no computer), etc. READ FIRST!!
I was able to complete up to step 7, but 8 posed a problem.
When trying to sync my google account to the phone it gave that old message we all know and love from when the G1's were just released. The one where it tells you: "There is a problem communicating with the Google servers. - This could be a temporary problem or your SIM card may not be provisioned for data services. If it continues, call Customer Care."
At first, I thought maybe it was because I had horrible service in my house, ranging anywhere from 0-2 bars. Thinking I could easily fix the problem by walking up the road to get 4 bars, that's what I did. Still having trouble communicating with the servers. It's obviously not server overload like they tried to say at launch and it can't be I don't have data services because I've been paying and using them for about 9 months now. So I set off to the internet for a fix. I came across this:
[How To] Activation over Wifi
Reading the first sentence, it told me to set up ADB. So I went here:
Setting up ADB
But, I obviously couldn't complete the steps listed because I can't set my phone to debugging mode with out it being activated. So I went back to the Wifi act. page and scrolled down to find this:
[How To] Activation over Wifi (12th Post)
Following the first step, I typed <enter>reboot<enter> and nothing happened.
This, obviously, confused me very much. Because, did I not just wipe my whole phone and install rc29?
But I disregarded it, putting it to the side as a fluke and hoping the rest would work anyway, because at this point I just wanted things to start working.
I went to step 2, but once again I can't do that because I don't have access to the phone settings.
But I just continued.
Upon trying to complete step 5, I was just pissed... This seems like a never ending road. Of course, my phone had to be wrong and show up as a USB mass storage device. So I followed the steps, but I don't understand part D in step 5 because it only gives me one choice on the list which is USB mass storage device. After this I started trying everything, uninstalling that driver, turning of PnP, just about everything I could think of.
If someone could just help me, even a little, I would be so very happy.
If you need any info at all just, pictures, build info, w/e I/'ll have it to you as soon as I see your message. If you don't understand something I said, ask right away and I'll answer. Thank you so much in advance lol
Mind you, I've tried all these guides a couple times over, I've tried different guides and I've installed rc29 3 times now. Still no luck

I'm confused....
I have a few questions before we start you on the journey to getting you rooted.
Firstly, am I understanding things correctly when I assume that you have already flashed DREAIMG.nbh (RC29) onto your phone and can't get past the setup screen?
Secondly, you say that you have data service, but then say that you didn't have enough "bars" so you headed up the street for more "bars". Are you sure you have data service because the bars on the phone have to do with cell reception and have nothing to do with data service.....
Thirdly, are you on 3G or EDGE in your area?
If you do indeed have a data plan for sure, then other than a crappy 3G or EDGE signal, there really shouldn't be a reason for the error message your getting other than google's servers might actually be experiencing difficulty. No way to know for sure.
If/when you are able to get past the login screen to root, go to this link
http://forum.xda-developers.com/showthread.php?t=548924
instead of Easiest How To for: Root, Hero, Recovery, Partition (no computer), etc. READ FIRST!!
its recently updated, and easier to follow.

I have bad service...
Yes, after flashing RC29 onto it I can't hook my google account up to my phone. I've got EDGE in my area, checking t-mobile's service map though I found that it's really bad right where I live. Until I can head out to somewhere with some good service any ideas on how to get he wifi act. to work?

KingTasty said:
Yes, after flashing RC29 onto it I can't hook my google account up to my phone. I've got EDGE in my area, checking t-mobile's service map though I found that it's really bad right where I live. Until I can head out to somewhere with some good service any ideas on how to get he wifi act. to work?
Click to expand...
Click to collapse
If you cannot get adb working properly, then you cannot use JF's method to bypass the signin screen therefore you just have to wait until you can get to a better service area.
Your two choices are: bypass the signin screen or sign in over the network. You can't sign in over the network as previously stated by you, and you cannot bypass the signin screen because you can't get adb working. There is no way to setup wifi within android if you are stuck at the signin screen

but wait?
There must be someway to activate ADB, because if there's not then isn't a guide activating through wifi pointless?

KingTasty said:
There must be someway to activate ADB, because if there's not then isn't a guide activating through wifi pointless?
Click to expand...
Click to collapse
There are plenty of guides on how to get adb working... its just so happens that you reported that you can't figure it out. If you can't figure it out and get it working, then you can't use the sign in screen work around as outlined in JF's post.
The very first step in JF's work around is
You have to connect to your phone with adb shell and get root access, and then type the following command:
Click to expand...
Click to collapse
Since you can't do that, you can't do the work around. Try reading up more on adb and see if you can get it working.

Couple questions
I've basically fixed all the problems I was having that needed to be fixed to use ADB except for one. According to every guide I need USB Debugging enabled, My questions is how did others achieve this with being activated?

OMG help me too i have the same problem !!!

KingTasty said:
I've basically fixed all the problems I was having that needed to be fixed to use ADB except for one. According to every guide I need USB Debugging enabled, My questions is how did others achieve this with being activated?
Click to expand...
Click to collapse
I know for a fact there that I saw some terminal command not too long ago to be able to activate usb debugging from the command line. I can't for the life of me remember where I saw it, but if you can be patient, I may be able to find it eventually.

florevil said:
OMG help me too i have the same problem !!!
Click to expand...
Click to collapse
Just keep checking back here and see where we get, hopefully we can figure it out.
@DirectMatrix:
The command is <enter>setprop persist.service.adb.enable 1<enter> and you enter it in your phone, but that only works with RC28 I think. Or does the RC29 have the hidden shell also? The reason I'm thinking it doesn't is because when I type <enter>reboot<enter> nothing happens. The only things I can think of is that I'm on the wrong screen when typing or the RC29 I'm using is messed up.
I'm on the very first screen when registering, where the it says touch the android to begin. btw, thanks for all the help so far

KingTasty said:
Just keep checking back here and see where we get, hopefully we can figure it out.
@DirectMatrix:
The command is <enter>setprop persist.service.adb.enable 1<enter> and you enter it in your phone, but that only works with RC28 I think. Or does the RC29 have the hidden shell also? The reason I'm thinking it doesn't is because when I type <enter>reboot<enter> nothing happens. The only things I can think of is that I'm on the wrong screen when typing or the RC29 I'm using is messed up.
I'm on the very first screen when registering, where the it says touch the android to begin. btw, thanks for all the help so far
Click to expand...
Click to collapse
RC29 has the hidden shell also which is what allows the telnetd command to be entered to start the rooting process. It sounds like when you enter the reboot command at the welcome screen you should be getting a reboot because you said you installed RC29. It also sounds like your doing the commands in the correct spot but just to recap, you should be at the "touch the android to begin" screen, once there, just slide out the keyboard, hit enter, type reboot, hit enter again and the phone should reboot.
What happens if you keep trying to follow JF's guide even though you can't get the reboot to work? Have you made any promising progress with steps after the A few tips and tricks section?

I flashed it again, and reboot works now. I don't know what was wrong before. I'll try the "setprop persist.service.adb.enable 1" again. Just to be clear, after typing that nothing happens right? and I'll go check the tips and tricks.

KingTasty said:
I flashed it again, and reboot works now. I don't know what was wrong before. I'll try the "setprop persist.service.adb.enable 1" again. Just to be clear, after typing that nothing happens right? and I'll go check the tips and tricks.
Click to expand...
Click to collapse
Glad to hear it and yes, your right, nothing that you can see will happen. Essentially what it is doing is executing the command behind the scenes same as would happen if you were to hit the check box next to usb debugging if you were able to.
The way you will see if it worked is you should be able to open up a command prompt assuming your a windows user and type:
Code:
adb devices
You should see a device listed something like HT.........
Lemme know if you have anymore problems

Still nothing.
I tried but I don't think it worked, but it may have. The problem could be my drivers so I followed this.
"Im not getting a notification of Android ADB when i plug in my USB"
Why: Your computer has detected your phone but as a protable device and as a storage device.
Fix: This took me a lot of research and time to figure out so this is what your are going to do.
First download USBDeview - Here
Unzip it
Run USBDeview.exe as Administrator
You will see all drivers being used on your computer
Highlight and Uninstall all drivers with the description have HTC Android (Should be 3 of them)
Right Click on the driver and press uninstall
Once done, Unplug your phone and plug it back in
You should now get the notification of the ADB device
Follow the steps above to install the drivers
Click to expand...
Click to collapse
I did that but every time I plug my g1 back one it makes a new one, calling it USB Mass Storage Device. I keep deleting it but it keeps coming back every time.
Here's what I got in cmd.
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Tyler>cd C:\android-sdk-windows-1.5_r3\tools
C:\android-sdk-windows-1.5_r3\tools>adb devices
List of devices attached
C:\android-sdk-windows-1.5_r3\tools>adb shell
error: device not found
C:\android-sdk-windows-1.5_r3\tools>
I'm not really sure what to do now... I guess I keep trying to see if it'll work. Meanwhile, what do you think?

King,
PM me your contact info and I'll try to troubleshoot this with you. I did it the old fashion way without any programs and I think I remember my steps so I just have to walk through it again.
You could also try this adb tutorial, thats the one I used and would use if I were to walk you through it.
http://forum.xda-developers.com/showthread.php?t=502010

Alright yeh, sounds good.
Gimme like 20 min, I'm gonna go grab something to eat quick.
Take a look here though, I uploaded what re appears every time I plug in my g1. Something must have been turned on or changed be cause now 3 new drivers appear every time instead of just one.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But still no luck in cmd, so something is still wrong...

Hi! I have the same problem too. There're a lot of tutors online but they are just copy and paste from each others. I did pass by the first time via wifi when I root my G1 but cann't the second time rooting my girlfriend's.
The USB driver that window or HTC using before works on vista and only see the device as ADB composite deivce, but not anymore, Windows now recognized the devices as ADB composite device AND mass storage. I don't know about XP. and don't know what to do about it
I think that's why I can not enable ADB on G1 by typing "setprop....enable 1"
Anybody help? Offering your Tmo SIM card for 5 mins? I am at Dallas. Txt [email protected] #469-759-9897 Really need it PLZ

I guess this is obvious but I just want to clarify: Everytime you flash the rom you need to re-activate the phone? Or is activation only a one time requirement?
I just purchased a used, tmobile g1 (from the US) and am hoping to root it and flash SuperD's wrong as soon as I get it. However, the problem is I obviously don't have a Tmobile SIM and I don't have a data connection on my local sim card.
Do I have to go through these ADB steps to activate the phone? Thanks!

"Force Roaming" App for Android HTC Hero

Does anyone know if XDA developers have any intent to create an app that would allow us to force the HTC Hero (CDMA for Sprint), and future Sprint Android phones, to roam? Service is weak in my office and I would love to force it to roam.
Thanks!

Would love to have the ability to force roam.
I would love to have the ability to force roam. Sounds like I'm in the same boat. At work i get like 1/2 bar of reception, while my roaming reception is full bars. My centro had the ability to force it to roam which really saved me but my hero doesn't. I would love if an app made this possible with maybe a toggle switch widget. Not sure if you would need root access for this or not. Could someone elighten us as to whether or not this can be done and if someone is already looking into the issue?

totally on the same boat. this is a must have.
it was done easily on my sprint touch on winmo =/

I would love this ability as well.

^^ Bump ^^

Same problem here!

Same here...while I don't know anything about rooting, I would imagine it wouldn't be that difficult for someone with some skill to allow roam only if it was a setting originally there and disabled before release..

Had this for my Pre. Definately would make my Hero much more usable. I actually believe my battery would last over a day if someone could create this.

Ok, we need to bump this thread. I just switched from my Q9c that had full signal while roaming at my
house (otherwise, no service from sprint). I got my Hero yesterday, and I can't get service PERIOD. I
am willing to pay, and so are a lot of others, for an app for the Hero to force roam. Willing to pay damn good money here.
PLEASE, someone chime in on this.

Yes I need this app I would so pay for this I only need it at my home and I'm paying for air rave bump bump bump

Someone seems to be trying http://www.mail-archive.com/[email protected]/msg16197.html
I have noticed something.......if I turn on wifi in my home rather than use the data it finds roaming network 50% less. If I leave an app running that consistently taps the data which can be expensive unless you have unlimited it seems to hold the roaming signal in place until the data connection goes dormant.

bump?Anything?

Bumpity bump. This is the only thing stopping me from getting a Hero (or another Android phone).

I am honestly shocked noone has come up with this yet. This is definately one instance where Android fails. Im bout ready to jump ship to big red.

pahick said:
I am honestly shocked noone has come up with this yet. This is definately one instance where Android fails. Im bout ready to jump ship to big red.
Click to expand...
Click to collapse
I'm surprised as well. I think I'm going to get the Pre for now, and if there is ever a fix for this, then I'll move over to an Android phone. I'd like to contribute to a solution, but unfortunately time is hard to come by (the same I'm sure for many people).

I upgraded to Android and love it but hate the no forced roaming crap so I had to trade my other phones for a TP2 but I can't activate it until I get my stupid $100 MIR back from Sprint. So I suffer....

V.A.T.Juice said:
Someone seems to be trying http://www.mail-archive.com/[email protected]/msg16197.html
I have noticed something.......if I turn on wifi in my home rather than use the data it finds roaming network 50% less. If I leave an app running that consistently taps the data which can be expensive unless you have unlimited it seems to hold the roaming signal in place until the data connection goes dormant.
Click to expand...
Click to collapse
So the link you provided above...is guy that barking up the wrong tree?

Alright folks..I think i may have stumbled upon a workaround to force roaming!!
Procedure:
1. Download and install the diagnostics drivers for the Hero
2. Download the latest version of QPST (i'm using 2.7 build 323)
3. On your phone make sure USB debugging is turned on and push ##3424# in your phone keypad
4. Plug your phone in via USB and install the diagnostics drivers when prompted
5. If you've installed the drivers correctly, you should be able to go to Device Manager in control panel and see it registered as a COM port/USB diagnostic device
6. Next open QPST Service Programming>Connection>New. You should see your phone/COM port and you obviously choose that.
7. Choose "Read from phone" in the lower left hand of the window, after which you'll be prompted for your service programming code/MSL (Google your way to find it if you don't already have it)
8. Whence you have entered that code you'll see your phone info around
9. Go to the System tab (5th tab in my setup)
10. NOW..what worked for me was this setup: Preferred Mode: Digital Only (upon further investigation, apparently "Automatic" works as well) Band Preference: A Only (as a side note B Only worked for me as well) Roam Preference: Automatic
11. Press Write to Phone
12. Reboot your phone
That should do it!! If alls done right you should see the familiar Roam triangle over your service bars! Hope it works fer ya..to change back from roaming only change everything back to Automatic.
*DISCLAIMER*: I've been messing around with my phone's service programming quite a bit so this may only work for me cuz of some erroneous change I made to the internals. Also I've only tried this in an area that I know I can get signal at, so whether it is TRULY roaming, I don't know. All I do know is that it says Roaming in my phone's Status

KERKEDAGAIN said:
Alright folks..I think i may have stumbled upon a workaround to force roaming!!
Procedure:
1. Download and install the diagnostics drivers for the Hero
2. Download the latest version of QPST (i'm using 2.7 build 323)
3. On your phone make sure USB debugging is turned on and push ##3424# in your phone keypad
4. Plug your phone in via USB and install the diagnostics drivers when prompted
5. If you've installed the drivers correctly, you should be able to go to Device Manager in control panel and see it registered as a COM port/USB diagnostic device
6. Next open QPST Service Programming>Connection>New. You should see your phone/COM port and you obviously choose that.
7. Choose "Read from phone" in the lower left hand of the window, after which you'll be prompted for your service programming code/MSL (Google your way to find it if you don't already have it)
8. Whence you have entered that code you'll see your phone info around
9. Go to the System tab (5th tab in my setup)
10. NOW..what worked for me was this setup: Preferred Mode: Digital Only (upon further investigation, apparently "Automatic" works as well) Band Preference: A Only (as a side note B Only worked for me as well) Roam Preference: Automatic
11. Press Write to Phone
12. Reboot your phone
That should do it!! If alls done right you should see the familiar Roam triangle over your service bars! Hope it works fer ya..to change back from roaming only change everything back to Automatic.
*DISCLAIMER*: I've been messing around with my phone's service programming quite a bit so this may only work for me cuz of some erroneous change I made to the internals. Also I've only tried this in an area that I know I can get signal at, so whether it is TRULY roaming, I don't know. All I do know is that it says Roaming in my phone's Status
Click to expand...
Click to collapse
Has anyone tried this yet? I don't have my cable available now to do so myself, but hopefully I can get it this weekend.

links
links please.....

Cant change sprint hero esn/meid?

I know this topic is kind of frowned on, but bear with me, I'm doing it for legitimate purposes.
I just picked up a used sprint CDMA hero for use on my Carolina West plan. I rooted the new hero, put it in diag mode so that I could manipulate it with CDMA workshop 3.5 and Qxdm. My wife has a Carolina West Hero, so I was able to pull the PRL off of it and load it to my Sprint Hero. I also copied all of her NAM and EVDO settings to my phone and set my MSL/SPC to match Carolina West's, while giving it my phone #.
At this point, the phone's pretty much provisioned for Carolina West. So, I take it to one of their retail stores and they refuse to add the ESN to their database although its common practice with other carriers like Verizon.
I already have a data package for WAP browsing on my current phone, so I thought I'd try to change the ESN/MEID on the hero just to see if I could get it to work. Not hurting or defrauding anybody.
As I stated earlier, I used my licensed copy of CDMA workshop to change all of the EVDO, NAM, MSL, etc. However, it fails every time I try to change the ESN or MEID. I also read up on QXDA. As with CDMA workshop, I can read/change Nam stuff etc. but when I go to the Memory Viewer, all of the information on the screen is greyed out and the only address I can access is 0x00400000. And, since it returns all 0's for everything, I don't think it is actually reading the phone's memory.
Without discussing any legal implications, can someone please share ideas with me as to why CDMA Workshop and QXDA can't access the phone's memory even though they are supposed to be able to?
Thanks a million guys, I've learned more here so far than every other phone forum put together.

Only thing I can think of is restarting computer / phone...
I wouldn't be posting anything about this stuff on this site, I'm sure if you googled meid and hero you'd find a site that is a bit more accepting of this stuff.

I had already thought of that. I restarted the computer and both phones several times. For a "control group" I also tried to see if I could read the memory on the other Hero. Neither will allow it (in either CDMA workshop or QXDM).
Do you think flashing to an earlier software revision would do me any good? The sprint one is at 1.56.651.2 and pri 1.70_003. The other one is running something newer and proprietary (much like what I've read about Cellsouth, Bluegrass, Appalachian, Alaska, etc.).
Actually, this is the most accepting forum I've found so far. Thats why I chose this forum to ask. This is where I found most of my research on ESN/Meid.
If you have any suggestions of somewhere else to look/ask please post...or shoot me a PM.
I also did alot of reading at Howard Forums, Mobile Files, CDMA gurus, etc. but the information on the subject was really more clear and coherent here.

This forum is just more accepting because a mod hasn't come across your post yet. There are too many sections and most of the sections do not have individual mods for that section only. So it is a bit harder to police.
Anyway... you can try searching google for "esn repair" rather then "change esn". Unfortunately we can't help you any further. I only know the basics and not the details of the programs since I never had a reason to do that. There might be 1 or 2 people on these forums who could truly help you.
However, no one can post anything more because it would mean a ban and this thread deleted. Even though you have a good reason to do so, changing your esn is illegal and almost any forum out there will strictly get rid of posts that talk about it because they don't want to be shut down.

Its not like this is one of the thousands of posts out there asking "how do I change my esn". That information is fairly readily available.
Instead, if you read my post you'll see that I'm asking for some troubleshooting help to try to determine why my device isn't functioning properly and a spitballing of ideas as to how I can get it to work (ie...possibly rolling back to a previous software revision). I just filled in the backstory, because I felt it was pertinent information (showing that I can make writes to all areas of the device with various programs) just not the ESN/MEID.
Though, some would frown on what I'm trying to accomplish, I haven't asked for any illegal information...just troubleshooting help to figure out why my device isn't behaving properly. I don't know of any forum that would delete a post and ban somebody for asking for troubleshooting help, thats why the forum is here.

Muleguy said:
Though, some would frown on what I'm trying to accomplish, I haven't asked for any illegal information...just troubleshooting help to figure out why my device isn't behaving properly. I don't know of any forum that would delete a post and ban somebody for asking for troubleshooting help, thats why the forum is here.
Click to expand...
Click to collapse
I know where you are coming from. All I was trying to say is that many forums will error on the side of caution and get rid of these threads.
I am not sure if there was a bunch of forums that got shut down that has brought the fear of god into the forum operators or what. I know forums get shut down all the time for warez(not just android) but I am not sure why they are so fearful about the ESN issue.
I think it is because a shutdown notice can be sent to the hosting site and the hosting site will blindly comply without looking into the issue. So the owner/operators of the forum have no say in the matter and can't argue their case.

Are you using a laptop? I had that problem, so used a desktop. Then after that it worked with the laptop. It is pretty simple thing to do.
-------------------------------------
Sent via the XDA Tapatalk App

Good idea aven. That is one of the things though that struck my mind late last night, although for a different reason. I was originally trying on a laptop running Win 7 Pro. Sometimes Win 7's a bastard about running programs designed for legacy communications. So, I installed the programs onto my desktop which is still on Win XP pro. Well, at least I was able to try QPST and QXDM on the desktop. My CDMA workshop license is tied to the laptop.
Anyway, I got the same errors on the desktop that I did the laptop.
And back to the idea I had about going back to a earlier software version, then attempting it...that didn't work too swimmingly either. In trying to research what earlier stock versions there were, I found that some Heroes came out with 1.29 and some with 1.56. Once a phone is at 1.56, it can never go back to 1.29. I don't know the history of this phone, if it came out with 1.29 or not, but either way its at 1.56 now. Either way, I reinstalled the stock 1.56 RUU which unrooted the phone. I haven't had time to root it again yet. But, with the stock 1.56 on, I still got the same errors when messing with the ESN/MEID.
I posted on another forum in the post that details this method asking if it can be confirmed that they are in fact changeable in 1.56. I also found some information about people using MTTY to log communications during this process. That is what I plan to do next.
Can anyone here confirm that they've seen it done on a Hero at 1.59?

Are you using the HTC usb data cord or a regular one? Could be worth looking into

Have you set up your ports in QPST Configuration? That solved my problems I think.
-------------------------------------
Sent via the XDA Tapatalk App

Are you using the HTC usb data cord or a regular one? Could be worth looking into
Click to expand...
Click to collapse
Yep...using the data cable that came new in the box with my wife's Hero.
Have you set up your ports in QPST Configuration? That solved my problems I think.
Click to expand...
Click to collapse
Yes, while using QXDM, QPST is configured properly. I can use it to write to NAM, EVDO, etc., just not ESN/MEID. If the port isn't connected in the QPST configuration, QXDM won't even behave like a phone is there.
In CDMA workshop, the program itself grabs the com port. I've forgotten before and left QPST server running while opening CDMA workshop. When that happens, QPST has the port locked so that other programs (apart from QXDM) can't access it. At that point I have to shut down QPST server before I can connect the port in CDMA workshop.
Actually, I ran into the same problem when I tried what I mentioned earlier. I tried to connect the port in MTTY to log the communications. But then, I wasn't able to use CDMA Workshop or QXDM because MTTY had the port locked.

Were you ever able to find a solution? Stuck here as well.

Lets just say programs like DFS and CDMA Workshop have come light years since this thread was started.

I need to find the new versions then. I was one of the first to do it after the 2.1 update that I could find. Now I'm wondering if I could do it to a newer HTC phone
Sent from my HERO200 using XDA App

[HW][DEV] Internal Pictures Please

I'd like to see some closeup internal photos of the HW inside the Camera.
Something along the line of the "tear apart"-style pictures of the PCB.
Why? I'm trying to establish whether or not it will be possible to make 3G phone calls in the (near?) future.

E:V:A said:
I'm trying to establish whether or not it will be possible to make 3G phone calls in the (near?) future.
Click to expand...
Click to collapse
How about rooting it and getting a Skyroam Gmate for the SIM card? That should work, I guess...

E:V:A said:
I'd like to see some closeup internal photos of the HW inside the Camera.
Something along the line of the "tear apart"-style pictures of the PCB.
Why? I'm trying to establish whether or not it will be possible to make 3G phone calls in the (near?) future.
Click to expand...
Click to collapse
I can't help you with tearing apart the camera since I have no expertise in that matter.
But I assume the phone has the ability to make calls, just disabled by software (no phone/dialer/call logs app), because the phone has IMEI number and can send/receive SMS natively.
But even if we can enable the phone function, i assume it has to be in speaker mode, or using wired headset or bluetooth headset since this device doesn't have speaker in the "right position" for us to make a phone call normally...

Here are some internal pictures from FCC for the following cameras:
Code:
[SIZE=2]FCC PCB Markings RF Hardware PCB Date
--------------------------------------------------
EKGC100 Rev.0.0 XG626 + RF 2012.07.27
EKGC110 Rev.0.3 Missing RF 2012.08.21
EKGC120 Rev.0.* MDM **** ****
--------------------------------------------------
* = unreadable
[/SIZE]
The EKGC100 with full radio capability:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The EKGC110 with no RF capability, except WiFi:
< pictures for EKGC120 missing since the FCC pic quality sucks >

^^
So there is phone module after all.. ?
Sent from Samsung GT-I9082

80000037 said:
^^
So there is phone module after all.. ?
Sent from Samsung GT-I9082
Click to expand...
Click to collapse
/\/\ this?

Didn't want to clog the ROM thread so I moved some stuff over here:
twistedumbrella said:
Nevermind, I think I have them reversed. The 100 should be the one I can mod, the 110 is wifi, and the 120 should be CDMA, which would need a software change instead of a firmware modification.
Edit: Anyway, it's going to require editing the NVRAM with a donor phone to get calling since it is a CAMERA, but I have a tutorial to get it done.
Click to expand...
Click to collapse
I'm pretty sure the Verizon GC120 board is Qualcomm although I am still iffy on the processor. Either way once I get mine and get access to it I am willing to test out some things to see if we can get true voice calling/sms on it.
I had a Bionic when it was determined because of the board you could edit the NVRAM to get it working for gsm. I wasn't too interested in that but did dig into it because I was hoping to use the same process to get an ATT Tab 8.9 I had working on Verizon (using one of MY valid Verizon IMEI's). So I'm familiar enough to be dangerous and a willing victim.

Jiggity Janx said:
...
I'm pretty sure the Verizon GC120 board is Qualcomm although I am still iffy on the processor. Either way once I get mine and get access to it I am willing to test out some things to see if we can get true voice calling/sms on it.
Click to expand...
Click to collapse
Excellent! Yes, I noticed the GC120 pictures were so bad. Impossible to read anything, but I also think they're Qualcomm, but we need to know which! (Actually, if you have the firmware I can check!)
To thread newcomers:
We started this discussion about the possibility of making 3G/4G radio phone calls in this thread: [ROM][PHONE][4way-reboot]Stock Rooted deodexed 4.1.2 XXBMC4 with mods. However that thread is a ROM thread, and is not the right place for this kind of discussion, so let's stay in this thread.
Click to expand...
Click to collapse

If you have an EK-GC120, I would appreciate if you could send me the latest firmware update. The update was an OTA, so it should probably be located in the /cache directory and called something like:
****.update_EK-GC120_GC120VRALL2_To_GC120VRAMC4_FWD-1.zip
Thanks in advance.

E:V:A said:
To thread newcomers:*We started this discussion about the possibility of making 3G/4G radio phone calls in this thread:*[ROM][PHONE][4way-reboot]Stock Rooted deodexed 4.1.2 XXBMC4 with mods. However that thread is a ROM thread, and is not the right place for this kind of discussion, so let's stay in this thread.
Click to expand...
Click to collapse
Ok man, you have my full support. If you or someone else need someone to test stuffs feel free to contact me!

Jiggity Janx said:
Didn't want to clog the ROM thread so I moved some stuff over here:
I'm pretty sure the Verizon GC120 board is Qualcomm although I am still iffy on the processor. Either way once I get mine and get access to it I am willing to test out some things to see if we can get true voice calling/sms on it.
I had a Bionic when it was determined because of the board you could edit the NVRAM to get it working for gsm. I wasn't too interested in that but did dig into it because I was hoping to use the same process to get an ATT Tab 8.9 I had working on Verizon (using one of MY valid Verizon IMEI's). So I'm familiar enough to be dangerous and a willing victim.
Click to expand...
Click to collapse
Actually GSM cannot be converted to CDMA through NVRAM edits. You can switch carriers, enable hardware, bypass hardware, but the hardware is not going to transform. Going 4G SIM to 3G phone is possible by modifying the values IF the 4G still has a 3G fallback, hence using the Thunderbolt as a donor for a 3G connection since the 4G and 3G radios are actually completely separate. I can't take my GSM Galaxy Nexus and make it CDMA, though.

I am not talking about making the gsm gc100 into cdma because the board likely does not have a cdma radio on it.
But in my example of the att tab 8.9 the board already had cdma radio (hardware) that just wasnt enabled so it absolutely could have been enabled to work.
Edit: I was just noting that as an example of my prior knowledge of qpst/nvram.

E:V:A said:
Excellent! Yes, I noticed the GC120 pictures were so bad. Impossible to read anything, but I also think they're Qualcomm, but we need to know which! (Actually, if you have the firmware I can check!)
Click to expand...
Click to collapse
I have the device(s) now so let me know what you would like me to do.

Jiggity Janx said:
I have the device(s) now so let me know what you would like me to do.
Click to expand...
Click to collapse
Unless, you're hip on opening the device (which I do not recommend unless you have some Adam Outler unboxing tools/skills), I suggest you to:
1. Look for FCC ID
2. Connect camera via USB and open Device Manager if using windows to look for some COM port that says "blah blah Samsung Modem". Then use a terminal program to try to connect to the modem and send "ATI" and post the results.
3. If (2) is not working or you're not finding the correct port, we'll have to look around using ADB shell and/or find the correct (Windows) drivers. Do list any associated VID/PID from connected USB devices.
4. This should probably be "0", but try looking in device info for the modem firmware version. Also see if you can access service menu. That should also contain a way to display current firmware etc.
5. If you have the firmware, uncompress it and send me the modem.bin file or just the whole blob, if not possible.
That is just to verify what's inside...

E:V:A said:
Unless, you're hip on opening the device (which I do not recommend unless you have some Adam Outler unboxing tools/skills), I suggest you to:
1. Look for FCC ID - will pull that tonight
2. Connect camera via USB and open Device Manager if using windows to look for some COM port that says "blah blah Samsung Modem". Then use a terminal program to try to connect to the modem and send "ATI" and post the results. - comes up as Samsung Android, will use ADB again tonight to send ATI and post results
3. If (2) is not working or you're not finding the correct port, we'll have to look around using ADB shell and/or find the correct (Windows) drivers. Do list any associated VID/PID from connected USB devices. - can adb while in recovery but still having problems connecting in odin
4. This should probably be "0", but try looking in device info for the modem firmware version. Also see if you can access service menu. That should also contain a way to display current firmware etc. - will look for modem firmware and use outler's method to get into service menu
5. If you have the firmware, uncompress it and send me the modem.bin file or just the whole blob, if not possible. - can't find the firmware. rooted already and can dd through adb. was going to attempt last night but had to merge the partitions twisted notes in another thread with the dd command I found online and just ran out of time.
That is just to verify what's inside...
Click to expand...
Click to collapse
updates in red

Jiggity Janx said:
updates in red
Click to expand...
Click to collapse
I think the "Terminal program" he means is something like "Putty", or "Tutty", right?

Delux9364 said:
I think the "Terminal program" he means is something like "Putty", or "Tutty", right?
Click to expand...
Click to collapse
That would make sense. I work with linux servers at work but use windows at home. Is there a good way to come up with the same result.
Btw worked a long day today so wont be able to pull this stuff until tomorrow.

Jiggity Janx said:
That would make sense. I work with linux servers at work but use windows at home. Is there a good way to come up with the same result.
Btw worked a long day today so wont be able to pull this stuff until tomorrow.
Click to expand...
Click to collapse
You would simply use PuTTY for linux.

Right. But windows at home. So what do I use at home on windows to get the requested info?

Putty
RealTerm

Droid Bionic on Straight Talk?

I'm trying to get Straight Talk working with this Bionic. Could someone help?

Not sure but...
I used to be a Verizon Wireless agent (Straight Talk piggy backs on their network.) If I remember right straight talk/net10/verizon's own prepaid phones are limited to 3G devices only. Policies may have changed, or I could potentially be wrong but I am going to guess that you won't be able to get it working on their network because they won't be able to issue you a compatible SIM

You have to edit the build.prop and create a local.prop (it probably doesn't exist). I recently put SlimKat 4.4.4 on my friend's Bionic, and got it working well with Straight Talk (Voice, MMS, Data, etc). Just edit build.prop with:
persist.radio.ap.phonetype=1
ro.mot.phonemode.vzw4gphone=0
ro.mot.phonemode.vzwglobalphone=1
ro.telephony.default_network=3
ro.telephony.gsm-routes-us-smsc=0
telephony.lteOnCdmaDevice=0
Create a local.prop file and add:
ro.telephony.ril.v3=signalstrength
Move this into /data/
Next, go into system/etc/ and get your apns-conf.xml file and delete all the entries you don't need, keeping only the one relevant to Straight Talk. In my friend's case:
Code:
<apns version="7">
<apn carrier="StraightTalk ATT" mcc="310" mnc="410" apn="tfdata" port="80" mmsc="http://mms-tf.net" mmsproxy="mms3.tracfone.com" mmsport="80" type="default,supl,mms,hipri" />
</apns>
For the novices, to do this last part, you'll need a file manager like ES that can utilize root permissions after enabling in settings.
After this, any 4.3 or 4.4 ROM should let you edit APN settings, etc. You may need to set your radio to GSM (auto PRL) by going into your dialer and hitting *#*#4636#*#* and going into Phone Information then down to network type or whatever. I don't have a Motorola phone in front of me If that doesn't work, I've noticed GSM/WCDMA (auto PRL) works for some.
Good luck
Edit: I forgot one crucial thing you must do. You have to use RadioComm to enable GSM/UMTS bands. You can find it with Google. The version I used is 11.12.2. You'll either have a green or purple light on the right side, signifying that your phone is connected. It should show up in the status bar too. Steps:
Ensure you have correct Motorola drivers and that device shows up in device manager (You may need to use Google USB driver, as this has worked with some Motorola phones for me)
Ensure that USB is in PC Tools mode
In Radiocomm go to MA->COMMON->MDM 6x00
Go to the FTM Common1 tab, and wait for purple or green light on side
Toward the top of NVAccess you'll see a select box. Scroll to NV item 1877 NV_RF_BC_CONFIG_I
Click on read value
Once read, replace the first 8 bytes with: 8703E80400000200 (back up original as a .txt file or something)
Write the new value to the device and reboot
There's also a flashable zip that does this, but I've not tested it. Use at your own risk:
http://forum.xda-developers.com/attachment.php?attachmentid=1048524&d=1336485537
All of the information I presented is from others, but I can't remember all the threads I got this from. I take no responsibility for any bricked phones or the like.

shadolis said:
You have to edit the build.prop and create a local.prop (it probably doesn't exist). I recently put SlimKat 4.4.4 on my friend's Bionic, and got it working well with Straight Talk (Voice, MMS, Data, etc). Just edit build.prop with:
persist.radio.ap.phonetype=1
ro.mot.phonemode.vzw4gphone=0
ro.mot.phonemode.vzwglobalphone=1
ro.telephony.default_network=3
ro.telephony.gsm-routes-us-smsc=0
telephony.lteOnCdmaDevice=0
Create a local.prop file and add:
ro.telephony.ril.v3=signalstrength
Move this into /data/
Next, go into system/etc/ and get your apns-conf.xml file and delete all the entries you don't need, keeping only the one relevant to Straight Talk. In my friend's case:
Code:
<apns version="7">
<apn carrier="StraightTalk ATT" mcc="310" mnc="410" apn="tfdata" port="80" mmsc="http://mms-tf.net" mmsproxy="mms3.tracfone.com" mmsport="80" type="default,supl,mms,hipri" />
</apns>
For the novices, to do this last part, you'll need a file manager like ES that can utilize root permissions after enabling in settings.
After this, any 4.3 or 4.4 ROM should let you edit APN settings, etc. You may need to set your radio to GSM (auto PRL) by going into your dialer and hitting *#*#4636#*#* and going into Phone Information then down to network type or whatever. I don't have a Motorola phone in front of me If that doesn't work, I've noticed GSM/WCDMA (auto PRL) works for some.
Good luck
Edit: I forgot one crucial thing you must do. You have to use RadioComm to enable GSM/UMTS bands. You can find it with Google. The version I used is 11.12.2. You'll either have a green or purple light on the right side, signifying that your phone is connected. It should show up in the status bar too. Steps:
Ensure you have correct Motorola drivers and that device shows up in device manager (You may need to use Google USB driver, as this has worked with some Motorola phones for me)
Ensure that USB is in PC Tools mode
In Radiocomm go to MA->COMMON->MDM 6x00
Go to the FTM Common1 tab, and wait for purple or green light on side
Toward the top of NVAccess you'll see a select box. Scroll to NV item 1877 NV_RF_BC_CONFIG_I
Click on read value
Once read, replace the first 8 bytes with: 8703E80400000200 (back up original as a .txt file or something)
Write the new value to the device and reboot
There's also a flashable zip that does this, but I've not tested it. Use at your own risk:
http://forum.xda-developers.com/attachment.php?attachmentid=1048524&d=1336485537
All of the information I presented is from others, but I can't remember all the threads I got this from. I take no responsibility for any bricked phones or the like.
Click to expand...
Click to collapse
I'm not sure what the deal is - I'm trying to do the same thing, but with T-Mobile US rather than Straight Talk... Should work fine, but when I make the above changes, I get com.android.phone stopped working over and over. If I follow every step above, but instead of "ro.telephony.default_network=3", I use "ro.telephony.default_network=7", it works fine, I can make calls on T-Mobile, but the signal strength is horrible. I can be where I normally have full 2G/3G signal, and the Bionic barely has one bar if anything. Most of the time it just says "No Service" unless I step outside, whereas my other T-mobile specific phones have no problems with the signal anywhere in my house.
What might I be doing wrong here? I just bought the Bionic as a backup as I've been told it works fine with GSM when you do the above tweaks, but I'm finding it's real-world operability on GSM to be less than stellar.

gully52 said:
I'm not sure what the deal is - I'm trying to do the same thing, but with T-Mobile US rather than Straight Talk... Should work fine, but when I make the above changes, I get com.android.phone stopped working over and over. If I follow every step above, but instead of "ro.telephony.default_network=3", I use "ro.telephony.default_network=7", it works fine, I can make calls on T-Mobile, but the signal strength is horrible. I can be where I normally have full 2G/3G signal, and the Bionic barely has one bar if anything. Most of the time it just says "No Service" unless I step outside, whereas my other T-mobile specific phones have no problems with the signal anywhere in my house.
What might I be doing wrong here? I just bought the Bionic as a backup as I've been told it works fine with GSM when you do the above tweaks, but I'm finding it's real-world operability on GSM to be less than stellar.
Click to expand...
Click to collapse
What rom are you using? I've used this technique on a ridiculous number of bionic roms to make them GSM so hopefully I can help, it's worth noting that I do not create a localprop. I found that most roms have the "ro.telephony.ril.v3" line in the default.prop and I can simply amend them by adding "signalstrength," (note the comma to include the end of the quotes) at the beginning of the entry. You might try wiping the rom and starting over but skip the step changing the radio with the *#*#4636#*#* part
---------- Post added at 11:15 AM ---------- Previous post was at 11:10 AM ----------
shadolis said:
For the novices, to do this last part, you'll need a file manager like ES that can utilize root permissions after enabling in settings.
After this, any 4.3 or 4.4 ROM should let you edit APN settings, etc. You may need to set your radio to GSM (auto PRL) by going into your dialer and hitting *#*#4636#*#* and going into Phone Information then down to network type or whatever. I don't have a Motorola phone in front of me If that doesn't work, I've noticed GSM/WCDMA (auto PRL) works for some.
Click to expand...
Click to collapse
The settings adjusted in the default.prop permit that you do not need to change the radio. since i started using these particular settings, I've never had to change it and additionally found it to be commonly problematic. I also found that MOST roms do not need you to add the straight talk APN. Cyanogen and Paranoid, I know for fact include them. When you boot the phone for the first time you'll need to go into the settings and select the appropriate Straight Talk APN (mine is the MVNO one).

HW-A vs. HW-C
Plasmaleto said:
What rom are you using? I've used this technique on a ridiculous number of bionic roms to make them GSM so hopefully I can help, it's worth noting that I do not create a localprop. I found that most roms have the "ro.telephony.ril.v3" line in the default.prop and I can simply amend them by adding "signalstrength," (note the comma to include the end of the quotes) at the beginning of the entry. You might try wiping the rom and starting over but skip the step changing the radio with the *#*#4636#*#* part.
Click to expand...
Click to collapse
I've tried with stock JB, as well as CM11 M11 in Slot 1. I've wiped and started over more times than I can count.
What do you mean that you add "signalstrength," at the beginning of the ro.telephony.ril.v3 entry? It's my understanding that the entry should be "ro.telephony.ril.v3=signalstrength". I don't understand what you mean by putting signalstrength at the beginning of the entry. Also, what's up with that comma?
Then again, all my difficulties could be in the fact that I have a "HW C" Bionic. Just got a "HW A" model, and will be tinkering with that soon too. It actually came with original Stock 5.5.886 Gingerbread ROM... Right now, I plan on upgrading to the 232 ICS leak (so I can go back to GB if needed), and see if I can get GSM working on it a little better.
How would you recommend I proceed with a bone stock ICS 6.7.232 ROM?
Thanks a BUNCH for your reply on this old (but fun to tinker with) phone!
Brian

gully52 said:
I've tried with stock JB, as well as CM11 M11 in Slot 1. I've wiped and started over more times than I can count.
What do you mean that you add "signalstrength," at the beginning of the ro.telephony.ril.v3 entry? It's my understanding that the entry should be "ro.telephony.ril.v3=signalstrength". I don't understand what you mean by putting signalstrength at the beginning of the entry. Also, what's up with that comma?
Then again, all my difficulties could be in the fact that I have a "HW C" Bionic. Just got a "HW A" model, and will be tinkering with that soon too. It actually came with original Stock 5.5.886 Gingerbread ROM... Right now, I plan on upgrading to the 232 ICS leak (so I can go back to GB if needed), and see if I can get GSM working on it a little better.
How would you recommend I proceed with a bone stock ICS 6.7.232 ROM?
Thanks a BUNCH for your reply on this old (but fun to tinker with) phone!
Brian
Click to expand...
Click to collapse
Ahhhh yes, i believe you found the root of the issue. The method that was used for Ginger Bread was slightly different which almost certainly why the above may not be working for you. I practically forgot about that, I upgraded mine years ago. I've grown so fond of the bionic I'm on my third you can buy them second hand for like $50 to $100. So i Just keep fixing/repairing them haha.
I'm gonna dig through some old book marks and tutorials and find out how I upgraded mine originally and I'll post them up here for you. The timing of this coming up is almost bizarre. I'm actually in the middle of working on a website that lets you point it at a rom, it downloads it, modifies it for GSM, then provides you a link to download it. I'd actually like to make it an Android app because when I download rom updates, I have to make them GSM compatible first.

Plasmaleto said:
Ahhhh yes, i believe you found the root of the issue. The method that was used for Ginger Bread was slightly different which almost certainly why the above may not be working for you.
Click to expand...
Click to collapse
As I mentioned above, I just received the phone that's still running Gingerbread on Rev. A Hardware. Haven't even tried to start messing with that phone yet.
The original phone I was having trouble with, prompting the post to this thread, was running stock Jelly Bean on Rev. C hardware.
You say you're on your 3rd Bionic because you like them so much! They are a rugged and capable phone, for sure. What carrier have you been using it with? I've been attempting plain old T-Mobile, but assume making it work for Straight Talk would make it work for T-Mobile as well, aside from APN settings.
How's your signal strength on your bionic compared to an official GSM phone, both for calls and data?

gully52 said:
As I mentioned above, I just received the phone that's still running Gingerbread on Rev. A Hardware. Haven't even tried to start messing with that phone yet.
The original phone I was having trouble with, prompting the post to this thread, was running stock Jelly Bean on Rev. C hardware.
You say you're on your 3rd Bionic because you like them so much! They are a rugged and capable phone, for sure. What carrier have you been using it with? I've been attempting plain old T-Mobile, but assume making it work for Straight Talk would make it work for T-Mobile as well, aside from APN settings.
How's your signal strength on your bionic compared to an official GSM phone, both for calls and data?
Click to expand...
Click to collapse
The #1 reason I continue using bionics is because of how cheap parts are if I need them (like when I drop them and break the screen ) and accessories. Like I have several docks that I've bought for like $7 a piece (retail was like ridiculous $40 or something but just for a dock $7 is dirt cheap). I even got the lapdock that I picked up on ebay for $50. You can't beat it. That thing is awesome. Add to it that you can get a micro HDMI to HDMI cable, hook this thing up to a TV and use it as an entertainment player sorta like a roku and it just keeps getting better. You can then use another android device and run AllCast to turn it into a chromecast wannabe. I've just found endless fun, with this particular model of android.
I personally utilize Straight Talk. No BS, $45 every month, no surprises. Love it. As far as GSM signal goes, it's like any other GSM phone!

gully52 said:
As I mentioned above, I just received the phone that's still running Gingerbread on Rev. A Hardware. Haven't even tried to start messing with that phone yet.
The original phone I was having trouble with, prompting the post to this thread, was running stock Jelly Bean on Rev. C hardware.
You say you're on your 3rd Bionic because you like them so much! They are a rugged and capable phone, for sure. What carrier have you been using it with? I've been attempting plain old T-Mobile, but assume making it work for Straight Talk would make it work for T-Mobile as well, aside from APN settings.
How's your signal strength on your bionic compared to an official GSM phone, both for calls and data?
Click to expand...
Click to collapse
So here's what I would do
1) Update to Jelly Bean (you can do this with official Motorola OTA updates or more info here http://forum.xda-developers.com/showthread.php?t=2235946)
2) Power on phone and edit the hex values with Radiocomm see: post 29/30 http://forum.xda-developers.com/showthread.php?t=1297714&page=3
- - Be PARTICULARLY picky about this part, I found this to be extraordinarily difficult time and time again. Even though I've done it at least 5 or 6 times, I felt like it never went exactly as it should. After changing the value, you might even disconnect, reconnect, and make sure the hex value has changed.
3) Root the phone (this guide seems a little indepth but it works very well once you get it down compared to other methods http://forum.xda-developers.com/showthread.php?t=2256439)
4) At this point you have a choice of either modifying stock rom or use custom ROMS. I HIGHLY recommend custom ROMS, the stock ROM is highly bloated. I have found that AOSP based ROMS like Cyanogen or Paranoid (personal recommendation), work considerably better in general in addition to being more suited for GSM usage.
Should you choose custom roms then here's what I would do next, I have found this is the easiest way to consistently use GSM:
a) You'll want to install SafeStrap or something similar (I've only got experience with SafeStrap personally and understand the developer has suspended his project from future updates but still works for me) http://forum.xda-developers.com/showthread.php?t=1391875
b) Once you have that, you can download almost any ROM, extract it to a folder, change the build.prop with the proper GSM configuration you listed, find the line for "ro.telephony.ril.v3" inside build.prop and add "signalstrength," (including punctuation) immediately after the equal sign. Don't bother with local.prop.
c) Re-zip it just like it was before, then install the ROM in a SafeStrap slot (probably want to add GApps)
d) Once it's booted, you can connect to wifi to setup the Google Acct and whatnot, then (this part varies slightly depending on the rom but AOSP roms are all pretty similar) go into the Settings: Mobile Networks: Access Point Names: Select the carrier of your choice (there's literally hundreds preloaded)
Lot of detail but a lot of specifics left out, if I can expound on anything please let me know which areas are too vague.
UPDATE: Here's the ROM I'm currently using. I literally install this thing with safe strap along with the pa gapps modular micro and just use it. No editing files, no thing. Just use it.
Paranoid Android Legacy Original - http://get.aospa.co/legacy/targa
Paranoid Android Legacy GSM Ready - http://dailen.bitnamiapp.com/roms/pa_targa-4.6-BETA5-20141022.GSM.zip
PA Gapps Modular Micro - https://www.androidfilehost.com/?w=files&flid=15801

Above and Beyond
Plasmaleto said:
Here's the ROM I'm currently using. I literally install this thing with safe strap along with the pa gapps modular micro and just use it. No editing files, no thing. Just use it.
Click to expand...
Click to collapse
Wow! This is above and beyond! Truly thankful for this guide. I'm fairly familiar with ROMs in general and putting Safestrap on the Bionic... but the fact that you hand-edited the PA ROM and provided a link... I deserve not such service!
Will attempt a flash tonight and let you know. Still plan to keep stock 232 ICS leak, since it will never get used once PA is installed! Will reply tomorrow if I get everything working!
Thanks again!
---------- Post added at 11:05 PM ---------- Previous post was at 10:28 PM ----------
Plasmaleto said:
a) You'll want to install SafeStrap or something similar (I've only got experience with SafeStrap personally and understand the developer has suspended his project from future updates but still works for me)
Click to expand...
Click to collapse
What version of Safestrap are you running? I installed 3.73, and once installed, my stock ICS 232 gets stuck on the boot animation forever. FXZ back to 905 and then update to 232 to get back into ICS...
I dunno, maybe I'm making a big deal out of wanting to keep the path back to gingerbread. I should probably just bite the bullet and go up to stock JB first as you mentioned...

gully52 said:
Wow! This is above and beyond! Truly thankful for this guide. I'm fairly familiar with ROMs in general and putting Safestrap on the Bionic... but the fact that you hand-edited the PA ROM and provided a link... I deserve not such service!
Will attempt a flash tonight and let you know. Still plan to keep stock 232 ICS leak, since it will never get used once PA is installed! Will reply tomorrow if I get everything working!
Thanks again!
---------- Post added at 11:05 PM ---------- Previous post was at 10:28 PM ----------
What version of Safestrap are you running? I installed 3.73, and once installed, my stock ICS 232 gets stuck on the boot animation forever. FXZ back to 905 and then update to 232 to get back into ICS...
I dunno, maybe I'm making a big deal out of wanting to keep the path back to gingerbread. I should probably just bite the bullet and go up to stock JB first as you mentioned...
Click to expand...
Click to collapse
For some reason I distinctly remember their being a link between the stock rom, and those installed in rom slots. I'm currently using 3.7.2. I also THINK I recall that a while back when I wanted to use SafeStrap 3.5 I only could do so if I upgrade to JB. I can't find any documentation to back these up so take it with a grain of salt. Personally, I'm one who upgrades and never looks back so maybe I'm just biased haha
(P.S. your eyes do not deceive you, my username changed from Plasmaleto to Dailen, special request made to XDA webmasters!)

I've made a tool to convert Bionic ROMS to GSM ready if anyone would like to give it a shot I'm likely to move or relocate this at some point btw
http://dailen.bitnamiapp.com/roms/convert.php
Relocated:
http://dailen.net/roms/convert.php

Dailen said:
For some reason I distinctly remember their being a link between the stock rom, and those installed in rom slots. I'm currently using 3.7.2. I also THINK I recall that a while back when I wanted to use SafeStrap 3.5 I only could do so if I upgrade to JB. I can't find any documentation to back these up so take it with a grain of salt. Personally, I'm one who upgrades and never looks back so maybe I'm just biased haha
(P.S. your eyes do not deceive you, my username changed from Plasmaleto to Dailen, special request made to XDA webmasters!)
Click to expand...
Click to collapse
Dailen (the artist formerly known as Plasmaleto),
I took the plunge and updated to stock JB, rooted, installed Safestrap 3.73, then installed your pre-GSM-configured version of Paranoid ROM. Rebooted, connected to wifi, got everything setup. Powered down, inserted my T-Mobile SIM card, and voila! Full HSPA signal! 5.01mb/sec download, 1.22mb/sec upload. Outgoing calls work! Incoming calls work! Data works! Super cool! Thanks again!

Congrats! Glad that worked for ya!

Dailen said:
I've made a tool to convert Bionic ROMS to GSM ready if anyone would like to give it a shot I'm likely to move or relocate this at some point btw
http://dailen.bitnamiapp.com/roms/convert.php
Click to expand...
Click to collapse
Just trying your tool on the CM11 M11 release. Will let you know how it works. Do you know, if I came across some older ROMs... JB 4.2/4.3, would your tool work for them as well?
Also, since you're a Bionic nut, I don't suppose you have a version of CarbonROM sitting around from before they dropped support for the Bionic? I contacted them and was surprised to learn that they have absolutely ZERO archive of old version downloads.

gully52 said:
Just trying your tool on the CM11 M11 release. Will let you know how it works. Do you know, if I came across some older ROMs... JB 4.2/4.3, would your tool work for them as well?
Also, since you're a Bionic nut, I don't suppose you have a version of CarbonROM sitting around from before they dropped support for the Bionic? I contacted them and was surprised to learn that they have absolutely ZERO archive of old version downloads.
Click to expand...
Click to collapse
Well in theory the answer is yes. The way my script works, it changes only what it finds. If you can send me a link to one of the roms you'd like to try I'd be happy to take a look at the build.prop and tell you for sure if anything is missing.
Also, I don't recall having the carbonrom sitting around anywhere but I see their github still has the source posted, I suppose I could always try compiling for you. I got a couple ubuntu systems running I could put to some good use. Might take a few days.

Give it a shot!
Going to give this a shot right now on a friends Bionic. Unfortunately have to wait a few days for the Straight Talk Sim card to arrive. I'll report back.

Think I screwed up!
Dailen said:
Congrats! Glad that worked for ya!
Click to expand...
Click to collapse
I believe I have screwed up. I tried the radiocomm program last night and everything was green for me but I didn't write to the phone. I installed the pa_targa-4.6-BETA5-20141022.GSM.zip file, and the Gapps for that ROM. When I tried to go into Radiocomm again, it comes up red when I try to read (1877). Do I still need to do that or will the phone be good to go once I pop in an AT&T sim card? Thanks, Howie

meandg5 said:
I believe I have screwed up. I tried the radiocomm program last night and everything was green for me but I didn't write to the phone. I installed the pa_targa-4.6-BETA5-20141022.GSM.zip file, and the Gapps for that ROM. When I tried to go into Radiocomm again, it comes up red when I try to read (1877). Do I still need to do that or will the phone be good to go once I pop in an AT&T sim card? Thanks, Howie
Click to expand...
Click to collapse
Radiocomm is EXTREMELY particular and I swear it only works 3 out of 5 times. I seem to recall that when I did it, it wasn't "writing" the settings properly and I had to change the USB connection type. If my current setup is any indicator, it was set to "PST USB Driver". I also recall that one time I uninstalled the bionic drivers and reinstalled them and it started working.
It's probably worth mentioning that I would connect to your phone in Radiocomm while in the stock rom if possible. There's no telling if there's some quirky specific USB driver in the rom that Radiocomm depends on. When in doubt, try a different machine. Be sure to get the Bionic USB drivers working 100% (meaning no device errors in device manager) prior to doing the radiocomm stuff.