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.
Related
http://forum.xda-developers.com/archive/index.php/t-644769.html << I got my idea from there.
If you update the
Code:
/data/data/com.android.providers.settings/databases/settings.db
file so that "install_non_market_apps" = 1 instead of 0, you will be able to install non-market apps off of your sdcard or wherever.
This works for me at least, but you'll have to root first.
I ended up editing the file with the SQLite Manager firefox add-on.
But, since that took me a really long time, I'll just upload the edited settings.db for you. (don't forget to make the extention .db instead of .db.txt)
Now, as far as I know, this won't mess anything up... BUT, I'd feel a lot better if someone who knows more about Android would provide some feedback before anyone else tries this. [It works for me, but I'm not sure if any other user-specific settings are kept in that file that I don't know about!]
But, at least for me, I no longer need to use adb to install apks that aren't from the Android Market.
I hope this is useful to someone...
EDIT::
You will lose your settings if you use the attached settings.db.txt file. Your best bet is to pull the file off your phone, edit it with something that understands sqlite3's database format, and then push it back. It's just better that way.
Further EDIT:: As someone pointed out later in this thread, this file unbeknownst to me when I shared it, actually has a unique ID by which phones can be identified on the android market, etc. While this isn't a huge deal, it can lead to some rather strange behavior... my phone for example has started attempting to download apps from the android market all by itself.
So--- if you want to side-load apps, change the variable in the database like I explained above.
Sorry, completely new to android but where would you put this file so it would allow side-loading?
You'd have to replace
Code:
/data/data/com.android.providers.settings/databases/settings.db
with it. You'll have to have your phone rooted first though. Then you'll have to transfer the file to your phone with adb, and you'll then copy it over the existing settings.db file.
Honestly, it might not even be worth the trouble now that attn1 is just doing the whole ROMs.
But make sure you take off the .txt.
This works. Thanks.
For some reason, i'm getting a permissons error regardless that i successfuly rooted my phone...o_o
justince said:
For some reason, i'm getting a permissons error regardless that i successfuly rooted my phone...o_o
Click to expand...
Click to collapse
did you boot the phone and do adb remount with debugging enabled?
USB debugging? Yeah.
What i did was i used the other method to sideload root explorer, took the settings.db.txt, deleted the .txt part and replaced it via root explorer, and now i can sideload whenever...however, when i try to delete any of the att bloatware, its read only o_o fawking att
Can anyone confirm any other way to remove bloatware without flashing the rom?
justince said:
USB debugging? Yeah.
What i did was i used the other method to sideload root explorer, took the settings.db.txt, deleted the .txt part and replaced it via root explorer, and now i can sideload whenever...however, when i try to delete any of the att bloatware, its read only o_o fawking att
Can anyone confirm any other way to remove bloatware without flashing the rom?
Click to expand...
Click to collapse
That's why made the ROM without all that -er- stuff.
attn1 said:
That's why made the ROM without all that -er- stuff.
Click to expand...
Click to collapse
Attn's Rom is ****ing great. many thanks btw
a little help please
a bit confused..
how do i type in this code "/data/data/com.android.providers.settings/databases/settings.db"?
adb /data/data/com.android.providers.settings/databases/settings.db
or something else because that doesnt work.
fluffyarmada said:
I'm not sure if any other user-specific settings are kept in that file that I don't know about!
Click to expand...
Click to collapse
The only issue I see (as an Android newcomer, but with a development background) is that the settings.db contains an android_id that is supposed to be unique (it gets generated when you boot the phone the first time after a reset). So anyone installing your settings.db is going to have the same ID.
I'm sure it won't be an issue for most people but I wonder if there'd be a collision in any apps that are designed to communicate between Android devices? For this reason I'll be tweaking my own settings.db once the phone arrives later today.
Big thanks for posting this though!
Thanks for that, I honestly had no idea. I'm very new to Android. And this was a kludge.
fluffyarmada said:
http://forum.xda-developers.com/archive/index.php/t-644769.html << I got my idea from there.
If you update the
Code:
/data/data/com.android.providers.settings/databases/settings.db
file so that "install_non_market_apps" = 1 instead of 0, you will be able to install non-market apps off of your sdcard or wherever.
This works for me at least, but you'll have to root first.
I ended up editing the file with the SQLite Manager firefox add-on.
But, since that took me a really long time, I'll just upload the edited settings.db for you. (don't forget to make the extention .db instead of .db.txt)
Now, as far as I know, this won't mess anything up... BUT, I'd feel a lot better if someone who knows more about Android would provide some feedback before anyone else tries this. [It works for me, but I'm not sure if any other user-specific settings are kept in that file that I don't know about!]
But, at least for me, I no longer need to use adb to install apks that aren't from the Android Market.
I hope this is useful to someone...
EDIT::
You will lose your settings if you use the attached settings.db.txt file. Your best bet is to pull the file off your phone, edit it with something that understands sqlite3's database format, and then push it back. It's just better that way.
Further EDIT:: As someone pointed out later in this thread, this file unbeknownst to me when I shared it, actually has a unique ID by which phones can be identified on the android market, etc. While this isn't a huge deal, it can lead to some rather strange behavior... my phone for example has started attempting to download apps from the android market all by itself.
So--- if you want to side-load apps, change the variable in the database like I explained above.
Click to expand...
Click to collapse
NOTE: You MUST have root access in order for this to work
sqlite3 is included in the Android SDK tools, so this would be the best way:
COMMON
Enable USB debugging (settings > applications > development > USB Debugging)
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
Linux/OS X
echo "update secure set value = 1 where name = 'install_non_market_apps';"|./sqlite3 settings.db
WINDOWS
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
COMMON
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
Reboot phone and sideloading works. (thanks fluffyarmada)
I wonder if this might be why google voice fails to install properly for some...
Sent from my HTC Liberty using XDA App
Cobus said:
I wonder if this might be why google voice fails to install properly for some...
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
It is possible. The Google apps all use the android_id, afaik.
Although, I do remember I was never able to get the settings menu to setup the voicemail forwarding... I always had to use the weird GSM code. (The weird number with a bunch of * and # that you have to type in if you follow google's directions.)
judicious said:
a bit confused..
how do i type in this code "/data/data/com.android.providers.settings/databases/settings.db"?
adb /data/data/com.android.providers.settings/databases/settings.db
or something else because that doesnt work.
Click to expand...
Click to collapse
After you've rooted your phone, download the new settings.db into the same folder as where your adb program is. Then type:
adb push /data/data/com.android.providers.settings/databases/settings.db
in that folder while your phone is connect via usb.
I'm not sure if you have to restart your phone into recovery or not. Can someone check on this?
tiga2001 said:
After you've rooted your phone, download the new settings.db into the same folder as where your adb program is. Then type:
adb push /data/data/com.android.providers.settings/databases/settings.db
in that folder while your phone is connect via usb.
I'm not sure if you have to restart your phone into recovery or not. Can someone check on this?
Click to expand...
Click to collapse
Well, it's
Code:
$ adb push /path/to/file/on/computer/settings.db /path/to/file/on/phone/settings.db
So, if your settings.db is in your tools folder, then you can do
Code:
$ adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
what happen to the file download? i cant find it..
judicious said:
what happen to the file download? i cant find it..
Click to expand...
Click to collapse
Please follow the instructions posted by attn1 on reply number 13 to this thread.
I removed the settings.db, because it actually has a bunch of extra settings I didn't know about like a handset specific android_id variable... that caused me a bit of trouble...
But, follow the instructions on reply #13 on this thread, and you'll be able to fix it yourself.
Sorry for the inconvenience.
so if we already used the file, is there anyway to revert it back to default and then change the settings via the method outlined above? or.. if we failed to make a copy of our original settings.db file.. basically am i SOL?
EDIT: nevermind, just rebooted into Clockwork and wiped the phone.
****** WARNING do a nandroid backup before doing this in case anything goes wrong, NOTE!! if your already signed into the market this requires doing a Factory data reset before changes will be affected, so backup your data and apps before you do this... ******
note!! this process is much easier doing on a clean rom install, you just push the eri.xml file, and make the changes to the build.prop file and reboot your phone so the settings will stick.
How to change the sprint tab in the Market back to downloads in CM6.
create an eri.xml file by copying and pasting this into a text file
Code:
<EriFile VersionNumber="1357" NumberOfEriEntries="1" EriFileType="1">
<CallPromptId Id="0" CallPromptText="CallPromptId0"/>
<CallPromptId Id="1" CallPromptText="CallPromptId1"/>
<CallPromptId Id="2" CallPromptText="CallPromptId2"/>
<EriInfo RoamingIndicator="128" IconIndex="1" IconMode="0" EriText="Appalachian" CallPromptId="0" AlertId="0"/>
</EriFile>
replace Appalachian with your carrier id, save the file as eri.xml, and place it in the android-sdk/tools directory.
connect your phone to your pc, open a cmd prompt, cd into the android-sdk/tools dir.
run
Code:
adb pull /system/build.prop
open the build.prop file located in the android-sdk/tools directory with notepad++ or wordpad
scroll down to the line
Code:
ro.product.brand=sprint
replace "sprint" with your carrier id
next scroll down to
Code:
ro.com.google.clientidbase=android-sprint-us
replace "sprint" with your carrier id save the file.
open the cmd prompt cd into the android-sdk/tools directory
and push the build.prop file to your phone with
Code:
adb remount
enter
Code:
adb push build.prop /system
enter
restart your phone with
Code:
adb reboot
reset your phone to factory defaults by going to menu/Settings/Privacy/Factory data reset, after your phone resets, and boots back up, now push the eri.xml file we made earlier by conecting you phone to your pc, opening a cmd prompt, cd into the android-sdk/tools directory
and run
Code:
adb remount
enter
Code:
adb push eri.xml /data
enter
reboot your phone again last time i promise with
Code:
adb reboot
enter.
when your phone boots back up your correct carrier id will be displayed and when you sign back into the market it will be back to normal.
+1, very nice.
what about these entries
ro.cdma.home.operator.numeric=310120
ro.cdma.home.operator.alpha=Sprint
ngholson said:
what about these entries
ro.cdma.home.operator.numeric=310120
ro.cdma.home.operator.alpha=Sprint
Click to expand...
Click to collapse
i just left those entries alone, not positive but I'm guessing they are generic, because they are also present in all stock non-sprint 2.1 rom builds that I've seen.
codejunkie78 said:
i just left those entries alone, not positive but I'm guessing they are generic, because they are also present in all stock non-sprint 2.1 rom builds that I've seen.
Click to expand...
Click to collapse
wow really?? that seems odd certainly there has to be other carrier identifiers for those carriers
o well. thanks for the info!
im going to try and comment them out to see if makes any difference
ok so i changed:
ro.cdma.home.operator.alpha to my carrier id. had no effect as best i can tell.
i did not change the ro.cdma.home.operator.numeric entry.
edit:
on a side note the other changes you suggested also seem to have had no effect. my market still shows a sprint tab. also now it seems that clearing the app data doesn't fix it anymore either..... this is really starting to irritate me.
Thanks works perfectly. Even though I never had to change Appalachian..lol. Nice work.
Hello. I'm on Alltel with an HTC Hero using the CM 6.1 RC1.
This worked fine for removing the general branding but it did nothing for the Marketplace Sprint tab itself.
jfigura said:
Hello. I'm on Alltel with an HTC Hero using the CM 6.1 RC1. This worked fine for removing the general branding but it did nothing for the Marketplace Sprint tab itself.
Click to expand...
Click to collapse
I've found that, for the Tabs fix to stick, I have to go back and repeat the process after flashing a new ROM and signing into the Market.
I've used this for a long time. Always works great! A build or 2 back, my downloads tab in market changed back to sprint. I still have my regional carrier showing on my lock screen and notifications pull down. Is there a way to get the my downloads back without having to do the hard reset? Thanks.
dirtroad said:
I've used this for a long time. Always works great! A build or 2 back, my downloads tab in market changed back to sprint. I still have my regional carrier showing on my lock screen and notifications pull down. Is there a way to get the my downloads back without having to do the hard reset? Thanks.
Click to expand...
Click to collapse
I'm curious as to why you dug so deep and bumped a thread that hasn't been posted in since Nov of 2010...
dastin1015 said:
I'm curious as to why you dug so deep and bumped a thread that hasn't been posted in since Nov of 2010...
Click to expand...
Click to collapse
And, who even still uses 6.0 anymore?
nandroids are for
sissies
dastin1015 said:
I'm curious as to why you dug so deep and bumped a thread that hasn't been posted in since Nov of 2010...
Click to expand...
Click to collapse
Probably so he didn't get flamed for not searching.
Sprint shows up as a market tab for me now too after editing build prop. I am a Sprint user so it's not that annoying, but I would like to have the MyApps tab back.
I never said I used 6 anymore. I've flipped between AOSP and the CM nightlys for awhile. Right now I'm on #125. Like I said, I've used this process for awhile. I keep it bookmarked. I like having MY carrier show and my downloads tab in the market. Sometimes I would have to pull this page up and do as it says. Anyway, all I was trying to find out is if anyone had another way to get my downloads tab back without having to do the hard reset again. If I have to do a clean install then I will.
And yes I've searched.
Seems the AT&T ROMs have some tether protection (entitlement check) built into them that does not exist on the Rogers ROMs. So if you are a Rogers user and have flashed an AT&T based ROM then you will need to make a change to your telephony database to be able to get tethering working.
This problem probably is not unique to Rogers and probably applies to anyone who is using an AT&T based ROM on a network other than AT&T. To apply this to a different carrier you will just need to change the APN, numeric, mcc and mnc values in step 5 to match your carrier values.
Update: Turge made a flashable zip to perform this update.
Just install the zip in recovery.
Flashable ZIP (thanks Turge):
http://forum.xda-developers.com/attachment.php?attachmentid=1145125&d=1340286308
------------------------------------------------------------------
Old Instructions:
1. Use a rooted filemanager (e.g. ES File Explorer) to backup the Telephony Database (/data/data/com.android.providers.telephony/databases/telephony.db) to a safe place (e.g. /sdcard/).
2. Download SQLite Installer for Root from the Market and open the app and install SQLite3
3. Open an adb shell
4. Type the following command in to open the telephony database:
su -c sqlite3 /data/data/com.android.providers.telephony/databases/telephony.db
5. This should have opened sqlite3. If it did then type the following command in to update the database:
INSERT INTO carriers (name, numeric, mcc, mnc, apn, authtype, type, insert_by, state, protocol, roaming_protocol, carrier_enabled, bearer) VALUES ("Entitlement","302720","302","720","ltemobile.apn","-1","entitle","internal","hidden","IP","IP","1","0");
6. To confirm that this has been applied you can type the following:
select * from carriers;
This should list all the carriers you have in your telephony.db and the one you just added should be at the bottom.
7. Type the following to quit sqlite3
.exit
8. Type the following to reboot your phone
reboot
When your phone reboots it will work with standard ICS/Sense tethering!
I tried to write an ADB script to do this but ran into problems with the INSERT command so I just wrote some instructions instead.
Someone more skilled at scripting could probably build an ADB script pretty easily I am sure.
cmaxwe said:
I tried to write an ADB script to do this but ran into problems with the INSERT command so I just wrote some instructions instead.
Someone more skilled at scripting could probably build an ADB script pretty easily I am sure.
Click to expand...
Click to collapse
I was bored, so I made you a recovery flashable zip to perform your changes
If you want to find out if it worked, just type "cat /tmp/recovery.log" via adb shell after flashing the zip. The output should look like this:
Opening update package...
Installing update...
Enabling Rogers Tethering on AT&T ROM
by cmaxwe and Turge
about to run program [/sbin/busybox] with 3 args
about to run program [/sbin/busybox] with 3 args
minzip: Extracted file "/tmp/enable.sh"
minzip: Extracted file "/tmp/sqlite3"
about to run program [/sbin/busybox] with 3 args
1307|Entitlement|302720|302|720|ltemobile.apn ||||||||||-1|entitle|internal|||hidden|||||IP|IP|1|0
script result was [Done]
Done
Click to expand...
Click to collapse
I just created a hack that will unlock the tethering on AT&T based ROMs without modding this setting, so I'll post it in a couple when I get the chance
Calkulin said:
I just created a hack that will unlock the tethering on AT&T based ROMs without modding this setting, so I'll post it in a couple when I get the chance
Click to expand...
Click to collapse
This way is much better, it is universal.
designgears said:
This way is much better, it is universal.
Click to expand...
Click to collapse
Yeah the other method is carrier agnostic/universal but it needs to be updated for each new AT&T RUU.
Using the method in this thread you could create a flash file for each carrier and that flash file should be usable on any new AT&T RUU.
The method in this thread seems safer too because you are just modifying a few rows in a database instead of replacing functionality/executable code (which I think is what the other mod does).
In fact ROM creators could insert Entitlement rows for all the common carriers in the Telephony.db and we wouldn't need to worry about any of these mods.
I just flashed it and tried to run a wifi-hotspot and it doesn't seem to work.
I do get a different message now saying that if I want this to work, I should call someone from att or dial 611.
Anyone else try this?
daitienshi said:
I just flashed it and tried to run a wifi-hotspot and it doesn't seem to work.
I do get a different message now saying that if I want this to work, I should call someone from att or dial 611.
Anyone else try this?
Click to expand...
Click to collapse
i tried it and got the same result as you....
zakhir_n said:
i tried it and got the same result as you....
Click to expand...
Click to collapse
Same here, no luck. Rooted stock 1.85 AT&T, connected on "4G" (HSPA+).
(ADB method)
shchenok said:
Same here, no luck. Rooted stock 1.85 AT&T, connected on "4G" (HSPA+).
(ADB method)
Click to expand...
Click to collapse
That is odd...hmm.
With the ADB method did step 6 (select * from carriers) show the new line that you added?
Also are you in Canada on the Rogers network? This is only for Rogers.
Edit: If you are both on HSPA+ and not LTE then maybe that has something to do with it. The APN that I used was for LTE. You could try replacing ltemobile.apn in the instructions above with rogers-core-appl1.apn.
I would do revert to the backup of your telephony.db first before I tried this though as I am not sure what happens if you have more than one Entitlement APN for a carrier. It probably just uses the first one in the list which would mean adding rogers-core-appl1.apn would have no impact.
cmaxwe said:
That is odd...hmm.
With the ADB method did step 6 (select * from carriers) show the new line that you added?
Also are you in Canada on the Rogers network? This is only for Rogers.
Click to expand...
Click to collapse
Yes, it did.
No, I'm on AT&T, my mistake!
Hi, I would like to remove a Wi-Fi network from my list. It's listed as "not in range"
A long press then "forget" sequence returns "cannot forget".
After resetting the phone, the entry is unaffected.
How do I remove the entry (Z736563757265).
thanks nb
spice123 said:
Hi, I would like to remove a Wi-Fi network from my list. It's listed as "not in range"
A long press then "forget" sequence returns "cannot forget".
After resetting the phone, the entry is unaffected.
How do I remove the entry (Z736563757265).
thanks nb
Click to expand...
Click to collapse
Hey, I encountered the same issue (I have this exact SSID saved that cannot be forgotten, "failed to forget network" - where did this SSID come from????) and spent some time figuring out how to remove it. Well, I actually fixed it with the 'attwifi' network but I assume the following steps would apply for you too. I have an LG G2 running stock android 4.2, rooted. Note that you will need a rooted phone in order to do this. Here are the steps I took:
1.) Get a text editor capable of running as root (I used 920 text editor, there is a permissions issue with it though that I detail later).
2.) Open /data/misc/wifi/wpa_supplicant.conf using your text editor. Make a backup of this file while you're at it.
3.) Find the 'attwifi' entry and rename it (I renamed it to 'attwifi2'.) You could also probably remove the entry but I didn't try that.
4.) Turn off and turn on Wifi
* Note, I couldn't turn on wifi at first once I changed wpa_supplicant's conf file. It turned out to be a permission issue - my text editor did not save the file with the correct permissions. I had to run 'chmod 777 /data/misc/wifi/wpa_supplicant.conf' in a terminal window to give permissions back (it probably just needs chmod 666).
5.) Find 'attwifi2' in your saved wifi list and 'forget network'. It should now be forgetten. There is no more attwifi or attwifi2.
If this doesn't work for you, then you are probably using a different version of android where the conf file is in a different path. Try grepping for attwifi via a terminal window. Another thing you can try is to run 'dmesg' in a terminal window to see the system log - this could give you a clue as to what is going wrong. Best of luck!
Wifi issue on note2
I have a wifi issue, wifi I is not turning on after flashed the hd revolution on my note 2 pls help me
klaus ita said:
I have a wifi issue, wifi I is not turning on after flashed the hd revolution on my note 2 pls help me
Click to expand...
Click to collapse
I think your best bet is to ask your question in this thread: http://forum.xda-developers.com/showthread.php?t=2055736
Thanks!
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