Database Info

Data problems on all roms above 2.3.3

I know i'm not the only one having this problem, its been posted about before but no answers so id like to see if someone else who didn't get to see those can see this and come up with a solution..
I use an unlocked G2X with Cincinnati Bell, currently running Weapon. I have no problem at all on any rom though that is 2.3.3, any rom over that like 2.3.4, 2.3.4 etc data has NEVER worked, not i had it but lost it when i rebooted, never . i've never been able to run CM7 or MIUI because of this, and yes before someone suggests it my APN settings are correct i've checked them 1000 times they are the same as when on 2.3.3 roms, i've hard booted after to try to get data flowing a million times, i've followed installation instructions 100 percent and still have never had data working on those roms.
even on the new CM7 where the APN issue is fixed, data still does not work. Its obviously something in roms over 2.3.3 that is creating this problem. I BEG, BEG someone please help find an answer i would love you and most likely donate. Thanks.

58 views and no ideas? anyone, please?

You obviously haven't been checking the Development Section lately. There are many threads on this issue, and it has been fixed already. (Well, for the most part)

FatalityBoyZahy said:
You obviously haven't been checking the Development Section lately. There are many threads on this issue, and it has been fixed already. (Well, for the most part)
Click to expand...
Click to collapse
obviously you didn't read my post. I have NEVER had data work above roms with 2.3.3, most people have it then lose it. I also stated that the new kernel from ttbal and the newest CM where the issues are supposedly fixed I still can't get data. Please, read my post entirely before replying, thank you.

C-4Nati said:
I know i'm not the only one having this problem, its been posted about before but no answers so id like to see if someone else who didn't get to see those can see this and come up with a solution..
I use an unlocked G2X with Cincinnati Bell, currently running Weapon. I have no problem at all on any rom though that is 2.3.3, any rom over that like 2.3.4, 2.3.4 etc data has NEVER worked, not i had it but lost it when i rebooted, never . i've never been able to run CM7 or MIUI because of this, and yes before someone suggests it my APN settings are correct i've checked them 1000 times they are the same as when on 2.3.3 roms, i've hard booted after to try to get data flowing a million times, i've followed installation instructions 100 percent and still have never had data working on those roms.
even on the new CM7 where the APN issue is fixed, data still does not work. Its obviously something in roms over 2.3.3 that is creating this problem. I BEG, BEG someone please help find an answer i would love you and most likely donate. Thanks.
Click to expand...
Click to collapse
try editing the t-mobiles apn to yours that worked for me on simple mobile on cm7 but on the apn dont delete the password n server i think thats it

Ek07 said:
try editing the t-mobiles apn to yours that worked for me on simple mobile on cm7 but on the apn dont delete the password n server i think thats it
Click to expand...
Click to collapse
Yeah I read this in the other thread unfortunately there isn't a apn at all t mobiles or not on CM when I flash it
Sent from my LG-P999 using xda premium

I've been following the development threads, because I too have been having data issues deeper than just missing APNs. It actually seems to be an issue with the entire radio side as a whole on any rom that's not based on the factory firmware. It's become much more stable, but still I can only get a GPS instant lock immediately after a hard reboot and can only receive multimedia messages immediately after a reboot as well. Another thing I've noticed, is I will get a "No internet connection" warning whenever I open the browser, despite having a data connection, and the page still loads.
Also, why do I have to set all my carrier information (my phone number, and voicemail number specifically) when the other factory firmware roms can pull this from the sim card?
I love all the features of CM7 and it's based roms, but the data stability has made it unusable for me.

Ek07 said:
try editing the t-mobiles apn to yours that worked for me on simple mobile on cm7 but on the apn dont delete the password n server i think thats it
Click to expand...
Click to collapse
You can't edit T-MO's one. You can copy and make a duplicate of that and then edit it, but that just beats the point.
And yeah I STILL have the same problem.
I'm not a t-mobile customer so I need to add my APN manually. And yes after a hard I can see my list of APNs and I'm allowed to add APNs but still no data. even after the latest stable version. And even after that with the Dragon Kernel with the supposed APN fix.
Really hope someone can shed some light here.

C-4Nati said:
obviously you didn't read my post. I have NEVER had data work above roms with 2.3.3, most people have it then lose it. I also stated that the new kernel from ttbal and the newest CM where the issues are supposedly fixed I still can't get data. Please, read my post entirely before replying, thank you.
Click to expand...
Click to collapse
I apologize for my ignorance.

FatalityBoyZahy said:
I apologize for my ignorance.
Click to expand...
Click to collapse
Its ok
Sent from my LG-P999 using xda premium

pyromaniac1 said:
You can't edit T-MO's one. You can copy and make a duplicate of that and then edit it, but that just beats the point.
And yeah I STILL have the same problem.
I'm not a t-mobile customer so I need to add my APN manually. And yes after a hard I can see my list of APNs and I'm allowed to add APNs but still no data. even after the latest stable version. And even after that with the Dragon Kernel with the supposed APN fix.
Really hope someone can shed some light here.
Click to expand...
Click to collapse
in cm7 you can edit the tmobiles apn i done it and i got data
---------- Post added at 11:36 AM ---------- Previous post was at 11:34 AM ----------
C-4Nati said:
Yeah I read this in the other thread unfortunately there isn't a apn at all t mobiles or not on CM when I flash it
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
oh ok try going into recovery menu and wipe all data then boot up again maybe then you can see the apn

Since you are rooted go into adb and try the following. Download the attached zip file and extract the "apns-conf.xml" file and put it in the same directory you run adb from. Then execute the following adb commands.
# adb shell mv /system/etc/apns-conf.xml /system/etc/apns-conf.xml.bak
# adb push apns-conf.xml /system/etc/apns-conf.xml
# adb shell chmod 644 /system/etc/apns-conf.xml
Then go into apn settings and press menu and choose to restore to default. The TMO one will still show but now your Cincinnati Bell one should show also; and it will be a default apn like TMO now (they are on equal footing now). Make sure you press the radio button to make the Cincinnati Bell one green, it it wasn't already. Hopefully your data will work after this. Plus you will now have global apn settings automatically for virtually any sim you use from a GSM carrier worldwide.
(Note: Simple Mobile users don't use this - find my special thread for Simple Mobile users).

jboxer said:
Since you are rooted go into adb and try the following. Download the attached zip file and extract the "apns-conf.xml" file and put it in the same directory you run adb from. Then execute the following adb commands.
# adb shell mv /system/etc/apns-conf.xml /system/etc/apns-conf.xml.bak
# adb push apns-conf.xml /system/etc/apns-conf.xml
# adb shell chmod 644 /system/etc/apns-conf.xml
Then go into apn settings and press menu and choose to restore to default. The TMO one will still show but now your Cincinnati Bell one should show also; and it will be a default apn like TMO now (they are on equal footing now). Make sure you press the radio button to make the Cincinnati Bell one green, it it wasn't already. Hopefully your data will work after this. Plus you will now have global apn settings automatically for virtually any sim you use from a GSM carrier worldwide.
(Note: Simple Mobile users don't use this - find my special thread for Simple Mobile users).
Click to expand...
Click to collapse
Thanks for the help, I'm not where near an xda and phone "noob" but i have never used adb I wouldn't feel comfortable trying to do that if it risks bricking my phone. Unless you have any opinion on how doing it or if its not really complicated I don't think I will try that.

C-4Nati said:
Thanks for the help, I'm not where near an xda and phone "noob" but i have never used adb I wouldn't feel comfortable trying to do that if it risks bricking my phone. Unless you have any opinion on how doing it or if its not really complicated I don't think I will try that.
Click to expand...
Click to collapse
There is no risk of bricking your phone if you stick to the commands I gave you. Just highlight and copy them and you can paste them into the command prompt window by right clicking and selecting paste.
Download the attached zip with the adb.exe and two dlls need for it to run. All you are doing is backing up the apn configuration file, replacing it with a new one and setting permissions so the phone can use the new file. Then you reset the apns to default and the phone will set the apns from that file based on the sim in the phone.
Go into settings, applications and turn on usb debugging, if it is not on already. Then connect your phone to your computer and make sure the adb drivers load (you can find the driver pack by searching this site or installing them from the LG Updater app). To make sure the phone is connected in the command prompt window type "adb devices" and hit enter. The phone should be shown as connected. If not, the drivers are not installed.
Run the command prompt from the same directory where you unzip the three adb files and put the apns-conf.xml file in the same directory. That makes it easier for you to do this. It is actually quite simple and will take only a minute or so.

Flashable zip to replace apns-conf.xml file
Here is a flashable zip that can be installed with clockworkmod recovery. It does the same thing but does not back up your existing file. If you are running a stock rom this will prevent an ota from installing. If you are running a custom rom it doesn't matter as you cannot get ota updates anyway.
Just boot into CWM recovery and flash this zip file. Reboot and reset your apns to default.

Ok sweet, should i flash it while on my current rom that works or flash CM7 then flash it?
quick edit- it won't effect my phone being unlocked and lock it will it? after those questions i'm done asking and i will give it a try good sir thanks

Bump
Sent from my LG-P999 using xda premium

C-4Nati said:
Ok sweet, should i flash it while on my current rom that works or flash CM7 then flash it?
quick edit- it won't effect my phone being unlocked and lock it will it? after those questions i'm done asking and i will give it a try good sir thanks
Click to expand...
Click to collapse
The phone remains unlocked once you unlock it. Nothing you will do will relock it.

jboxer said:
The phone remains unlocked once you unlock it. Nothing you will do will relock it.
Click to expand...
Click to collapse
I did your suggestion, flashed the zip. Still didn't work
Sent from my LG-P999 using xda premium

I have some problem and something more.
GPRS data will not work, my default APN is mss.life.com.by, and I see arrows in my status bar, but internet not worked.
So, I changed it to internet.life.com.by(got it from operator instructions) and I anymore see arrows and internet still not work.
I have an idea with broadband, I think in my country other radio frequency.
But I can find other broadband for LG G2x

Rooted AT&T 3.18 JB Stock Wifi+USB Tethering/Hotspot

I made a thread for Rooted AT&T 2.20 about enabling factory tethering. I found out that using this same .db file on 3.18 was not working for me. So I went back and re-edited the telephony.db that came with 3.18 and it seems to work again. I have uploaded the 3.18 version of telephony.db to enable factory hotspot sharing again. I have CleanROM 6 R2 installed and this seems to work well on it. Should work on stock rooted phones as well.
To Install
1. Extract telephony.db into the same folder as your adb.exe
2. Run these commands (they create a backup as well as push the edited database):
>adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/data/data/com.android.providers.telephony/databases/telephony.db of=/sdcard/telephony.db.bak
>adb push telephony.db /sdcard/telephony.db
>adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/sdcard/telephony.db of=/data/data/com.android.providers.telephony/databases/telephony.db
[email protected]:/ # reboot
After reboot everything should work fine.

this is awesome, but you got my hopes up with the "rooted 3.18" title. you may want to move that bit to the end of the title. will definitely use this if my phone is ever unlocked again :\

Ha I got all excited too. And I may be wrong, but shouldn't this be in the development section?

lightpost712 said:
I made a thread for Rooted AT&T 2.20 about enabling factory tethering. I found out that using this same .db file on 3.18 was not working for me. So I went back and re-edited the telephony.db that came with 3.18 and it seems to work again. I have uploaded the 3.18 version of telephony.db to enable factory hotspot sharing again. I have CleanROM 6 R2 installed and this seems to work well on it. Should work on stock rooted phones as well.
To Install
1. Extract telephony.db into the same folder as your adb.exe
2. Run these commands (they create a backup as well as push the edited database):
>adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/data/data/com.android.providers.telephony/databases/telephony.db of=/sdcard/telephony.db.bak
>adb push telephony.db /sdcard/telephony.db
>adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/sdcard/telephony.db of=/data/data/com.android.providers.telephony/databases/telephony.db
[email protected]:/ # reboot
After reboot everything should work fine.
Click to expand...
Click to collapse
I downloaded file, but seems zip file is empty... I am using Peazip

diekastro said:
I downloaded file, but seems zip file is empty... I am using Peazip
Click to expand...
Click to collapse
I just re-downloaded it and the file is there. Try using a different unzipping program.

lightpost712 said:
I just re-downloaded it and the file is there. Try using a different unzipping program.
Click to expand...
Click to collapse
I tried again with windows pack and winzip... Both shows empty file.
I disabled Eset Enpoint, and I downloaded it 3 times.
However, I am using stock rom and I have the SQLite Editor. What changes did you do? Do you just have to change file 12 'broadband' to 'pta'?
Thanks

diekastro said:
I tried again with windows pack and winzip... Both shows empty file.
I disabled Eset Enpoint, and I downloaded it 3 times.
However, I am using stock rom and I have the SQLite Editor. What changes did you do? Do you just have to change file 12 'broadband' to 'pta'?
Thanks
Click to expand...
Click to collapse
I don't remember which line exactly off the top of my head. I am reattaching the zip file see if that works if that fails then I will go in a compare the standard .db with the new one. It was a simple one line change just don't remember which line it was. Trial and error is how I found it.

Thank you
lightpost712 said:
I don't remember which line exactly off the top of my head. I am reattaching the zip file see if that works if that fails then I will go in a compare the standard .db with the new one. It was a simple one line change just don't remember which line it was. Trial and error is how I found it.
Click to expand...
Click to collapse
I guess you did it using SQLite editor, it works for me.
Make a backup of telephony.db
Your internet APN should be configured (Settings - Mobile data - Access Point names)
1)Open Telephony.db (flange files: data/data/com.android.providers.telephony/databases)
2)Select 'carriers'
3)Search second row, then select Edit field
4)Change ID field with a number non used in this db (ex: in my case the last row is "42" so I used "43") - Save
5)Repeat the 3 and 4 steps, but using row 12.
6)Search the last line (or line with your carrier internet APN)
7)Select the row and Edit Field.
8)Change the ID field to "2". - Save
9)Chose the second row, then Clone Record and change ID field to '12' - Save
Just need to change a lot of things
Row number 2 -> Edit field
1)Change name to ATT Phone
2)Type to "default"
2)Insert_by field to "internal".
3)State to "readonly"
Row number 12 -> Edit field
1)Change name to Entiltlement
2)Type to "entitle"
2)Insert_by field to "internal".
3)State to "hidden"
My phone: HTC One X AT&T 3.18 unlocked and root. Stock rom

Worked great for me with a rooted, s-off HTC First and ST (ATT) SIM. Thank you!

diekastro said:
I guess you did it using SQLite editor, it works for me.
Make a backup of telephony.db
Your internet APN should be configured (Settings - Mobile data - Access Point names)
1)Open Telephony.db (flange files: data/data/com.android.providers.telephony/databases)
2)Select 'carriers'
3)Search second row, then select Edit field
4)Change ID field with a number non used in this db (ex: in my case the last row is "42" so I used "43") - Save
5)Repeat the 3 and 4 steps, but using row 12.
6)Search the last line (or line with your carrier internet APN)
7)Select the row and Edit Field.
8)Change the ID field to "2". - Save
9)Chose the second row, then Clone Record and change ID field to '12' - Save
Just need to change a lot of things
Row number 2 -> Edit field
1)Change name to ATT Phone
2)Type to "default"
2)Insert_by field to "internal".
3)State to "readonly"
Row number 12 -> Edit field
1)Change name to Entiltlement
2)Type to "entitle"
2)Insert_by field to "internal".
3)State to "hidden"
My phone: HTC One X AT&T 3.18 unlocked and root. Stock rom
Click to expand...
Click to collapse
I did all this it worked, it stopped saying "there's temporary network problem that stop the enablement of your... yari yari yari"
but it is not showing tethering status icon at the notification drawer however, it is saying limited service if i connected it with my computer..
somebody gotta help me out pls
BEST REGARDS

brilliant_smart said:
I did all this it worked, it stopped saying "there's temporary network problem that stop the enablement of your... yari yari yari"
but it is not showing tethering status icon at the notification drawer however, it is saying limited service if i connected it with my computer..
somebody gotta help me out pls
BEST REGARDS
Click to expand...
Click to collapse
The AT&T ROMs are a real pain in the butt in regards to tethering and WiFi hotspot. As you are already bootloader unlocked and rooted, I would suggest just flashing any non-AT&T base ROM, and the tethering functions should work properly. Especially if you are not on AT&T, and your carrier does not limit tethering in any way (it looks like you are not located in the US?).
In my opinion, there is nothing "good" about being on the AT&T ROM. Many functions are intentionally broken or hidden, with nothing useful added. So going to a non-AT&T based ROM is "win" all around.

brilliant_smart said:
I did all this it worked, it stopped saying "there's temporary network problem that stop the enablement of your... yari yari yari"
but it is not showing tethering status icon at the notification drawer however, it is saying limited service if i connected it with my computer..
somebody gotta help me out pls
BEST REGARDS
Click to expand...
Click to collapse
Maybe Its late for answer, but did you restar your phone after edit the file?

diekastro said:
Maybe Its late for answer, but did you restar your phone after edit the file?
Click to expand...
Click to collapse
No offense to the OP, but I would suggest not wasting any more time with this method (its been 6 months after all). As I already mentioned in Post #11 above, just flash any custom or stock rooted ROM that is not AT&T base (Sense base - I don't follow AOSP ROMs enough to know how well WiFI hotspot works on those), and WiFi hotspot will work fine.

You are right
redpoint73 said:
No offense to the OP, but I would suggest not wasting any more time with this method (its been 6 months after all). As I already mentioned in Post #11 above, just flash any custom or stock rooted ROM that is not AT&T base (Sense base - I don't follow AOSP ROMs enough to know how well WiFI hotspot works on those), and WiFi hotspot will work fine.
Click to expand...
Click to collapse
yes, really I flashed with T-mobile Sense 5 ROM five months ago, and its better option.

[Q] DROID3 XT862 for pageplus and T-Mobile

Hi,
The system version is 5.7.906.XT862.Verizon.en.US
It was unlocked, rooted and installed root explorer ready to modify to work with US GSM ( Lycamobile also)
Here is where I got info to follow
http://forum.xda-developers.com/showthread.php?t=1989359
However, I have some concerns need help
1- will the instruction and the first build.prop file in the above link will work with my phone?
2- Can I use the phone with both pageplus ( being flashed with TalkForGood) and T-Mobile ( Lycamobile later)? I saw the same question without answer here http://forum.xda-developers.com/showthread.php?t=1425519
3- Can I use the phone oversea as a global phone without a need to follow the above link in Non-US GSM Networks session?
4- In case I want to go back stock image ( revert to the original one after messing it up), how?
To Skreelink, thank for your instruction but can you or anyone show me where to do the "required options" part because I simply couldn't find what you mentioned in my phone under Wireless & Network setting -> Mobile Network.
( I tried to post this under the above post but couldn't)
Thanks

macarong1 said:
Hi,
The system version is 5.7.906.XT862.Verizon.en.US
It was unlocked, rooted and installed root explorer ready to modify to work with US GSM ( Lycamobile also)
Here is where I got info to follow
http://forum.xda-developers.com/showthread.php?t=1989359
However, I have some concerns need help
1- will the instruction and the first build.prop file in the above link will work with my phone?
2- Can I use the phone with both pageplus ( being flashed with TalkForGood) and T-Mobile ( Lycamobile later)? I saw the same question without answer here http://forum.xda-developers.com/showthread.php?t=1425519
3- Can I use the phone oversea as a global phone without a need to follow the above link in Non-US GSM Networks session?
4- In case I want to go back stock image ( revert to the original one after messing it up), how?
To Skreelink, thank for your instruction but can you or anyone show me where to do the "required options" part because I simply couldn't find what you mentioned in my phone under Wireless & Network setting -> Mobile Network.
( I tried to post this under the above post but couldn't)
Thanks
Click to expand...
Click to collapse
1: The link you provided is my information and files for KEXEC ROMs, such as CM10.2 or AOKP. For the stock rom (As you listed 906), you will want to go here.
2: If you flash the XT883 radio for US GSM networks (like T-Mobile) you will not be able to flip between them via software toggle, you will have to flash the stock radio + swap build.prop back to stock and OTA on PagePlus, vice versa when you want to use the other network. (I wanted the same thing, I solved it by getting a Motorola Razr M XT907). The main reason for this is; The XT883 radio expects an RUIM card (CDMA version of SIM) and without it, puts it in emergency only mode. Verizon/PagePlus/Sprint/other US CDMA networks do not use the RUIM so no real way around this.
3: To use it as a global phone, just restore the stock radio and build.prop, it should work without issue WITHOUT MODIFICATION, as long as you have input the SIM unlock code to unlock the phone. You *can* use the XT883 radio globally, but both radios will work for global GSM.
4: To return to stock, follow this thread.

thank you
The best answer I have ever seen.
So if I buy Motorola Razr M XT907 to achieve the goal Pageplus/T-mobile, where is the best procedure I should follow?
Thank you very much.
McR

Help please
Skreelink said:
1: The link you provided is my information and files for KEXEC ROMs, such as CM10.2 or AOKP. For the stock rom (As you listed 906), you will want to go here.
Click to expand...
Click to collapse
I follow the above link to flash my Droid3 with the current stock image.
The flash was done then I rebooted the phone.
However, I was unable to replaced the build.prop file
I couldn't change its properties or owner or overwrite the file.
I see the instruction here http://forum.xda-developers.com/showthread.php?t=1406812&page=3
but I couldn't overwrite the original file with the modified one.
I rooted the phone already.
I am not sure what I did was wrong.
Please help.
Thanks,

macarong1 said:
I follow the above link to flash my Droid3 with the current stock image.
The flash was done then I rebooted the phone.
However, I was unable to replaced the build.prop file
I couldn't change its properties or owner or overwrite the file.
I see the instruction here http://forum.xda-developers.com/showthread.php?t=1406812&page=3
but I couldn't overwrite the original file with the modified one.
I rooted the phone already.
I am not sure what I did was wrong.
Please help.
Thanks,
Click to expand...
Click to collapse
You either have to use adb or a root browser. Rom Toolbox Lite has one, ES File explorer also has one. I'm sure other apps have a root browser, but I've not used others.Rom Toolbox's root browser allows you to longpress for a menu to change permissions.

Help please
Skreelink said:
You either have to use adb or a root browser. Rom Toolbox Lite has one, ES File explorer also has one. I'm sure other apps have a root browser, but I've not used others.Rom Toolbox's root browser allows you to longpress for a menu to change permissions.
Click to expand...
Click to collapse
Thank you for your fast reply.
I use totalcommander that run with superuser permission.
With a long press on the file, I go to property and set up with all permission ( 777)
After I hit OK to confirm the change, nothing happens but when I check again, it is still (rw-r--r--)
I have superuser installed.
I am stuck now.
Is there a way to browse and copy overwrite via windows or before the phone is up ( using usb cable)
Help please

macarong1 said:
Thank you for your fast reply.
I use totalcommander that run with superuser permission.
With a long press on the file, I go to property and set up with all permission ( 777)
After I hit OK to confirm the change, nothing happens but when I check again, it is still (rw-r--r--)
I have superuser installed.
I am stuck now.
Is there a way to browse and copy overwrite via windows or before the phone is up ( using usb cable)
Help please
Click to expand...
Click to collapse
If the permissions are not sticking, then the app you're using either does not have root privledges, is not performing correctly, or your root isn't correct. Try updating your superuser binary via the superuser app. Although, rw-r--r-- should be just fine, 777 would 'pose' a security threat since it would allow any app to modify it. Long as you replace it with the one required for GSM, rw-r--r-- permissions should work.
macarong1 said:
The best answer I have ever seen.
So if I buy Motorola Razr M XT907 to achieve the goal Pageplus/T-mobile, where is the best procedure I should follow?
Thank you very much.
McR
Click to expand...
Click to collapse
Sorry, didn't see this until now... getting the Razr M on pageplus is a real pain, though T-Mobile would be simple. It's a matter of getting the computer to read the diag port (you have to manually select the driver) and simply editing ONE NV-Item, then any GSM sim will work (AT&T, T-Mobile, etc).
Here is one of my posts with a quick guide about unlocking a razr m for gsm.

THANK YOU
Skreelink said:
You either have to use adb or a root browser. Rom Toolbox Lite has one, ES File explorer also has one. I'm sure other apps have a root browser, but I've not used others.Rom Toolbox's root browser allows you to longpress for a menu to change permissions.
Click to expand...
Click to collapse
I install Rom Toolbox Lite, it failed to verify root.
I check in SuperUser app and found a check mark "Temp Unroot"
I clear and run update for superuser.
Then I remove Rom ToolBox Lite and install again.
I then use Root browser from its link.
Each time it prompts permission of su.
I copy and paste sucessfully.
Reboot the phone and it work in T-Mobile NOW.
It WORKS now.
Thank you so much.
According to your answer in my first post, I can use this phone with GSM oversea without modification ?
Can you help on the link to the instruction of the phone model that can toggle between Pageplus/T-mobile.
I am much appreciated your help.

macarong1 said:
I install Rom Toolbox Lite, it failed to verify root.
I check in SuperUser app and found a check mark "Temp Unroot"
I clear and run update for superuser.
Then I remove Rom ToolBox Lite and install again.
I then use Root browser from its link.
Each time it prompts permission of su.
I copy and paste sucessfully.
Reboot the phone and it work in T-Mobile NOW.
It WORKS now.
Thank you so much.
According to your answer in my first post, I can use this phone with GSM oversea without modification ?
Can you help on the link to the instruction of the phone model that can toggle between Pageplus/T-mobile.
I am much appreciated your help.
Click to expand...
Click to collapse
The Droid 3 requires flashing the radio and build.prop to swap between CDMA/GSM
UNLESS it it is a foreign GSM network like Rogers in Canada, then the stock radio works without modification. The XT907 Razr M can do a software toggle between them (Network mode under Mobile Networks like the D3) but setting up PagePlus requires a lot of work for data, though GSM is a lot easier to get working than the D3. You can still go ahead and activate the D3 on pageplus, just after you flash between radios, you have to OTA program each time.

question for help
Skreelink said:
The Droid 3 requires flashing the radio and build.prop to swap between CDMA/GSM
UNLESS it it is a foreign GSM network like Rogers in Canada, then the stock radio works without modification. The XT907 Razr M can do a software toggle between them (Network mode under Mobile Networks like the D3) but setting up PagePlus requires a lot of work for data, though GSM is a lot easier to get working than the D3. You can still go ahead and activate the D3 on pageplus, just after you flash between radios, you have to OTA program each time.
Click to expand...
Click to collapse
Thank you.
I think I can do the same process with the image file from the original and overwrite the build.prop with original.
I did back up the build.prop but not the radio.img
Where can I find the Droid 3 radio.img of 906 version?
I want it simple as a reverting from what I did because I already removed all Verizon apps and install my apps in the current image.
A recovery task can bring back the original image.
** Oversea I meant is Vietnam
Thank again,

macarong1 said:
Thank you.
I think I can do the same process with the image file from the original and overwrite the build.prop with original.
I did back up the build.prop but not the radio.img
Where can I find the Droid 3 radio.img of 906 version?
I want it simple as a reverting from what I did because I already removed all Verizon apps and install my apps in the current image.
A recovery task can bring back the original image.
** Oversea I meant is Vietnam
Thank again,
Click to expand...
Click to collapse
I will see about uploading the stock radio when I get home.

THANK YOU
Skreelink said:
I will see about uploading the stock radio when I get home.
Click to expand...
Click to collapse
I am waiting.
Thank you sir ( my guess)

macarong1 said:
I am waiting.
Thank you sir ( my guess)
Click to expand...
Click to collapse
Sorry it took me so long, I had a long hectic day, but Here it is.
Just flash it like you did the XT883 radio and put a stock build.prop in (you should have backed up the original). Then you should be able to OTA program with *228 if it's activated on pageplus.

THANK YOU
Skreelink said:
Sorry it took me so long, I had a long hectic day, but Here it is.
Just flash it like you did the XT883 radio and put a stock build.prop in (you should have backed up the original). Then you should be able to OTA program with *228 if it's activated on pageplus.
Click to expand...
Click to collapse
I understand.
Thank you.
You are the best in my eyes

Carrier Unlocking Sprints Photon Q

Ok, b4 I get 15 people Pointing me to an irrelevant Thread Not related to this Device , Directing someone to a thread where they arent Interested in the device supported in this forum doesnt provide answers lets discuss In detail carrier unlocking this device
1. Can this be accomplished by Flashing a new Radio Firmware? if so does one exist?
2. if this can be accomplished VIA RadioComm Has anyone dabbled in the MPQ Firmware Specificly for US carriers?
3. there are No threads specifically Covering this topic pertaining to this device and Instead of redirecting everyone Lets start one

Morecrabs said:
Ok, b4 I get 15 people Pointing me to an irrelevant Thread Not related to this Device , Directing someone to a thread where they arent Interested in the device supported in this forum doesnt provide answers lets discuss In detail carrier unlocking this device
1. Can this be accomplished by Flashing a new Radio Firmware? if so does one exist?
2. if this can be accomplished VIA RadioComm Has anyone dabbled in the MPQ Firmware Specificly for US carriers?
3. there are No threads specifically Covering this topic pertaining to this device and Instead of redirecting everyone Lets start one
Click to expand...
Click to collapse
1. No
2. Yes
You need to be on stock ics firmware for the NV edit to succeed and stick.
Use Android 4.0.4 Blur_Version.77.8.14.XT897.Sprint.en.US - http://sbf.droid-developers.org/phone.php?device=3
If you're downgrading from jellybean, you have to remove the line with flash gpt_main0.bin from the xml file, otherwise the flashing via rsdlite will fail.
Code:
[STRIKE]<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="6C05E70F1DCC59AD92B0BBEC4E6100ED" />[/STRIKE]
The firmware thread is here: http://forum.xda-developers.com/showthread.php?t=2095536
Then you can follow this (RadioComm):
http://forum.xda-developers.com/showthread.php?t=2166542
or this (CDMA WS) guide:
http://forum.xda-developers.com/showthread.php?t=2386871
After it's done, you should flash the stock Android 4.1.2 via rsdlite, then install CM10.2 (or any other custom ROM) again.

soo i have reason to believe this device I bought is actually a developer Model under my developer Options it has a development device ID d7vk-gus7-rvcl-s does that mean this unit is already carrier unlocked and i can simply skip the Radio comm steps? Im having a few radio Comm issues that are making me alil squimish it keeps telling me its not loading the card driver, because of a 64/32 bit difference and it tells me that it wont be able to properly enumerate values
any radiocomm setup suggestions?

Morecrabs said:
soo i have reason to believe this device I bought is actually a developer Model under my developer Options it has a development device ID d7vk-gus7-rvcl-s does that mean this unit is already carrier unlocked and i can simply skip the Radio comm steps? Im having a few radio Comm issues that are making me alil squimish it keeps telling me its not loading the card driver, because of a 64/32 bit difference and it tells me that it wont be able to properly enumerate values
any radiocomm setup suggestions?
Click to expand...
Click to collapse
That development ID is simply for identifying your device under debugging circumstances like ADB, every device has them. Also, flashing another ROM changes this value.
Sent from Google Nexus 4 @ CM11

ok so that was a dumb decision to come to, but its not something id ever seen on any of my other android devices, Droid 1,2,4 samsung captivate glide, so i figured it was related to the developer Models
Do I need to run my copy of radio Comm on a 32 bit machine to accomplish this hacking?
my 64 bit machines seem to have driver related issues with the software

was wondering if anyone could help me setup the drivers, I keep getting errors with Radio comm and cdma workshop, and it all boils down to driver issues, with cdma workshop i cant get the QC port setup because IM missing a driver, and with radio comm, I cant get it to communicate properly with the phone once i boot into fastboot any help suggestions? ive installed the moto drivers and setup on a PC with a 32 bit version of win7 starter to allow radio comm to setup properly
In radio comm it will ID the phone as xt897 and i can get software version if its booted into OS, but it will do nothing else

Hi,
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer. I did this because the other method did not really work reliable for me (probably because I'm using a virtualized windows-installation).
This program works on the CM-11 builds. I have not tested stock, it may not contain the necessary diag_tty-support in the kernel.
download the binary: http://bork.cs.fau.de/~michael/photonq/xt897-fix-usa
copy the binary to /data/local/tmp/
make it executable (adb or terminal): chmod 755 /data/local/tmp/xt897-fix-usa
run the binary (adb or terminal):
Code:
[email protected]_c:/ $ su
[email protected]_c:/ # /data/local/tmp/xt897-fix-usa
Setting logging_mode to internal...
Creating /dev/diag_tty...
Opened diag...
Getting value of NV-item 8322...
GSM outside USA only: 1
Setting value of NV-item 8322 to 0...
Getting value of NV-item 8322...
GSM outside USA only: 0
Setting logging_mode to usb...
If you want to reinstate the lock, you can run: /data/local/tmp/xt897-fix-usa lock
You can find the source-code here: https://github.com/stargo/xt897-fix-usa
EDIT: Works fine on stock rooted JB, too, and sticks after a reboot.
EDIT2: This is now included as "unlock-us-gsm" in CM12.0 and up on XT897, XT907 and XT926. To use it run "unlock-us-gsm" in a root shell:
Code:
[email protected]_c:/ # unlock-us-gsm
Setting logging_mode to internal...
Creating /dev/diag_tty...
Opened diag...
Reading value of NV-item 8322...
GSM locked in the US: 1
Setting value of NV-item 8322 to 0...
Reading value of NV-item 8322...
GSM locked in the US: 0
Setting logging_mode to usb...
Regards,
Michael

stargo said:
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer
Click to expand...
Click to collapse
Excellent! I picked a good day to try to figure out how to do this, I was making notes of all the various steps (install ics on phone, use radiocomm on pc, install jb on phone, then cm on phone) when I got to this post and realized I won't need to do any of that, thanks much!

Terminal Emulator Question
stargo said:
Hi,
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer. I did this because the other method did not really work reliable for me (probably because I'm using a virtualized windows-installation).
This program works on the CM-11 builds. I have not tested stock, it may not contain the necessary diag_tty-support in the kernel.
download the binary: http //bork cs fau de/~michael/photonq/xt897-fix-usa
copy the binary to /data/local/tmp/
make it executable (adb or terminal): chmod 755 /data/local/tmp/xt897-fix-usa
run the binary (adb or terminal):
[CODE
[email protected]_c:/ $ su
[email protected]_c:/ # /data/local/tmp/xt897-fix-usa
Setting logging_mode to internal...
Creating /dev/diag_tty...
Opened diag...
Getting value of NV-item 8322...
GSM outside USA only: 1
Setting value of NV-item 8322 to 0...
Getting value of NV-item 8322...
GSM outside USA only: 0
Setting logging_mode to usb...
[/CODE]
If you want to reinstate the lock, you can run: /data/local/tmp/xt897-fix-usa lock
You can find the source-code here: https //github com/stargo/xt897-fix-usa
EDIT: Works fine on stock rooted JB, too, and sticks after a reboot.
Regards,
Michael
Click to expand...
Click to collapse
I'm trying out this method on my xt897 (Razr M) and Im up to the point where I need to run the binary but I'm not sure how to enter multiple lines into the terminal to run that last step, I've tried searching around and found nothing, any help would be much appreciated.

DroidRazrMv said:
I'm trying out this method on my xt897 (Razr M) and Im up to the point where I need to run the binary but I'm not sure how to enter multiple lines into the terminal to run that last step, I've tried searching around and found nothing, any help would be much appreciated.
Click to expand...
Click to collapse
Just FYI, RAZR M is xt907.
Also, I'm not sure what you mean - just run the script/binary from the shell. "su" is one line - gives you root access. The next line just runs the binary, "/data/local/tmp/xt897-fix-usa"
Good luck.

arrrghhh said:
Just FYI, RAZR M is xt907.
Also, I'm not sure what you mean - just run the script/binary from the shell. "su" is one line - gives you root access. The next line just runs the binary, "/data/local/tmp/xt897-fix-usa"
Good luck.
Click to expand...
Click to collapse
Ah whoops my mistake, thank you, yeah I definitely meant xt907, I typed that in during my lunch break so I was somewhat rushed. Anywho I meant to try it out according to kabaldan's post on http://forum.xda-developers.com/showthread.php?t=2166542&page=87.
So I'm going to test it out momentarily to see if I can run it on the xt907. Thanks again for your help, I was just somewhat confused about the terminal commands.

DroidRazrMv said:
Ah whoops my mistake, thank you, yeah I definitely meant xt907, I typed that in during my lunch break so I was somewhat rushed. Anywho I meant to try it out according to kabaldan's post on http://forum.xda-developers.com/showthread.php?t=2166542&page=87.
So I'm going to test it out momentarily to see if I can run it on the xt907. Thanks again for your help, I was just somewhat confused about the terminal commands.
Click to expand...
Click to collapse
Still confused as to where you're having issues - we are both talking about the same post. If you look, kabaldan's post redirects to the one I am referencing....

So once these steps are used to unlock the phone, which carriers can be used and how does flashing of carrier info occur?

Just want to say thanks again Michael. I just got my new Photon Q back from having sim card slot installed, ran your program and it worked perfectly on 21OCT2014 CM nightly.
I did also change a couple settings in the phone menu too, cuz I put an AT&T sim card in it, but sprint kept calling me to activate. Seems to be working well now, but not sure I understand everything, does this seem right - in regular CM11 settings menu under Mobile network settings, I set Preferred network type to "GSM/WCDMA Auto".
stargo said:
Hi,
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer. I did this because the other method did not really work reliable for me (probably because I'm using a virtualized windows-installation).
This program works on the CM-11 builds. I have not tested stock, it may not contain the necessary diag_tty-support in the kernel.
Click to expand...
Click to collapse

AT&T LG V10 H900 Force Upgrade To Android 6.0 MM GUIDE

After a lot of attempts, I found a way to force upgrade to Android 6.0 MM on AT&T LG V10 H900.
Before you start these steps:
•Make sure you have ADB installed on your computer and running. If you don’t, follow this guide to set it up. Or if you don't want the whole Android Studio, try this guide to setup Minimal ADB and Fastboot
•Make sure your phone is stock non rooted. If not here is the link to the stock tot file. And here is the link to the instructions for using tot file.
Instructions:
1. Download the Android 6.0 MM OTA zip file.
2. Unzip the file, and you get a 20N.up file
3. Copy 20N.up file to /Internal storage/SoftwareUpdate/ not external SD card (if folder doesn't exist, just create it)
4. Activate USB Debugging on phone and plug into computer
5. Open CMD window in C:\Users\YOURUSERNAME\AppData\Local\Android\sdk\platform-tools by holding shift and right clicking and selecting open command window here. (Path may be in different location based on your installation of SDK)
6. Type the following command in CMD window:
Code:
adb devices
Check and see if your device appears listed. If not, check on phone and select to trust computer if prompted. Run command again once you added computer to trusted list.
7. Run this command:
Code:
adb shell
This should appear: [email protected]:/ $
8. Run this command in ADB shell:
Code:
am start -n com.lge.lgfota.permission/com.lge.lgfota.permission.DmcEzUpdateStart
Phone Screen should show OFTA Easy Upgrade screen for a few seconds and then reboot to software update.
Note:
This does not give you root, it simply forces the update to marshmallow.
Edit: This method has now worked for everyone who tested it. If it doesn't work for you, just ask for help and either myself or one of the other fine members of the community can try and see what we can do to help.
Special Thanks To:
@kangi26
@syndicator
@LGMONO
@@autostrada048
@betasp
@shepcontracting

RESERVED
Reserved

Tested works

Thanks for this. After flashing back to stock my phone wouldn't show that I had an update no matter what I tried. This method worked perfectly.
For those who do not want to install the whole android studio to get ADB you can use this to get it.
http://forum.xda-developers.com/showthread.php?p=42407269#post42407269
That is what I used.

silentmage said:
Thanks for this. After flashing back to stock my phone wouldn't show that I had an update no matter what I tried. This method worked perfectly.
For those who do not want to install the whole android studio to get ADB you can use this to get it.
http://forum.xda-developers.com/showthread.php?p=42407269#post42407269
That is what I used.
Click to expand...
Click to collapse
Thanks @silentmage for Minimal ADB and Fastboot link! Added link to OP.

I can't decide if give up root and update. I use root mainly for adblock

So I don't currently have a SIM in my V10, it's in my Nexus 6P, but when I check for the MM update I've been told there is no update. This has happened since the MM update was released. My question is can I use this method to update to MM even if there is no SIM in the phone?
I wouldn't think that having a SIM would be require to update but maybe it uses the SIM to auth to the AT&T servers?

manny18pr said:
I can't decide if give up root and update. I use root mainly for adblock
Click to expand...
Click to collapse
You can technically adblock without root, if that's the only thing holding you back from an update.
http://forum.xda-developers.com/showthread.php?t=2726443

This worked perfectly! Thanks, TheBobMiller. Glad we figured out what I was doing wrong.

rcook55 said:
So I don't currently have a SIM in my V10, it's in my Nexus 6P, but when I check for the MM update I've been told there is no update. This has happened since the MM update was released. My question is can I use this method to update to MM even if there is no SIM in the phone?
I wouldn't think that having a SIM would be require to update but maybe it uses the SIM to auth to the AT&T servers?
Click to expand...
Click to collapse
I'm honestly not sure if this method would work for you or not. I am unaware if any of the testers or anyone who has used this method has done so without a sim card. In theory it should work since it's an AT&T version of the phone just missing the sim card. If you try, let me know the outcome please.

Worked great. Thanks!

takkuso said:
You can technically adblock without root, if that's the only thing holding you back from an update.
http://forum.xda-developers.com/showthread.php?t=2726443
Click to expand...
Click to collapse
Have you tried this?

manny18pr said:
Have you tried this?
Click to expand...
Click to collapse
Yep! Did it today. Working like a dream. Adblock was the main reason for rooting, but I really wanted marshmallow.
Best of both worlds!

takkuso said:
Yep! Did it today. Working like a dream. Adblock was the main reason for rooting, but I really wanted marshmallow.
Best of both worlds!
Click to expand...
Click to collapse
Can you post a screenshot of the apn settings you used?

manny18pr said:
Can you post a screenshot of the apn settings you used?
Click to expand...
Click to collapse
http://imgur.com/a/GO5KX

takkuso said:
http://imgur.com/a/GO5KX
Click to expand...
Click to collapse
When I set the apn settinga and hit save it said that the apn name was invalid

manny18pr said:
When I set the apn settinga and hit save it said that the apn name was invalid
Click to expand...
Click to collapse
Are you naming it the same as the original? I'm not sure, but I'd bet they can't have the same name. Other than that, I'm not sure what the issue would be. Maybe length of name, or invalid characters?

takkuso said:
Are you naming it the same as the original? I'm not sure, but I'd bet they can't have the same name. Other than that, I'm not sure what the issue would be. Maybe length of name, or invalid characters?
Click to expand...
Click to collapse
I'm trying again. I'll let you know
Edit: I managed to change the apn.
I now don't know what to manage in the adblock plus.

Deleted

TheBobMiller said:
I'm honestly not sure if this method would work for you or not. I am unaware if any of the testers or anyone who has used this method has done so without a sim card. In theory it should work since it's an AT&T version of the phone just missing the sim card. If you try, let me know the outcome please.
Click to expand...
Click to collapse
I hate to say this but it was all of 5 seconds to put the SIM back into the phone and then perform the update in the thread which worked fine. Sorry I just wanted to update the phone.