Related
Hello,
This is a dead easy fix to get tethering working completely with android-wifi-tether (http://code.google.com/p/android-wifi-tether/):
UPDATE
New development version has support for this rolled in, instructions are no longer necessary:
http://code.google.com/p/android-wi...name=wireless_tether_2_0_2-pre14.apk&can=2&q=
Steps:
1. Open adb shell (start cmd.exe, run "adb shell")
2. Issue the following commands:
- "mkdir /sdcard/android.tether"
- "cat /etc/firmware/fw_bcm4329_ap.bin > /sdcard/android.tether/fw_bcm4329.bin"
3. Download and install the android-wifi-tether application, start tethering.
Your log from android-wifi-tether should look like the attached image.
Happy configuration free tethering!
NOTE: This works because of the two separate firmwares that HTC has included in /etc/firmware. One is specific for AP-mode and must be more open to this kind of stuff. The original bug stemmed from the usual firmware dropping ARP requests pretty consistently, possibly as a powersaving measure.
The second firmware is loaded using the firmware_path option when loading the bcm4329.ko kernel module.
anyone else confirm this working please.
I confirm this working...
You will need to have root to run the app of course but 2 or 3 people have confirmed it on bug 362 already on the google project.
Not working for me
AWESOME!!!
actually i ever use wifi tether but this is pretty cool because it actually worked. i know on the heroC we had issues with wifi tether all of a sudden not wrking after 2.1. nice to see that its been fixed. good work spreading the word
ya. it will get SU permissions,
i can find the connection.
i connect to it. but no data transmitting.
would be cool if someone can confirm 4g is able to be tethered.
fdot said:
ya. it will get SU permissions,
i can find the connection.
i connect to it. but no data transmitting.
Click to expand...
Click to collapse
same here. any ideas?
toastcfh said:
would be cool if someone can confirm 4g is able to be tethered.
Click to expand...
Click to collapse
Not confirming but based on what I read harry_m stated the wifi tether app uses the current connection, so in theory if you switch between 3g and 4g the app will switch accordingly.
i can confirm
I originally flashed with toast's rom. Used the recovery .bat to install Flipz's stock root rom.
I then flashed toast's radio rom.
wifi tether did NOT work.
I then performed the above instructions, and viola, it works fine. (i am posting via wifi tether)
I want to thank everyone who is hard at work on these projects, you guys are awesome.
fdot said:
ya. it will get SU permissions,
i can find the connection.
i connect to it. but no data transmitting.
Click to expand...
Click to collapse
Check that the log screen looks exactly like mine does. Did you get any errors when you issued the adb commands?
Look on your sdcard for the android.tether folder and see if fw_bcm4329.bin file exists there.
toastcfh said:
would be cool if someone can confirm 4g is able to be tethered.
Click to expand...
Click to collapse
dcmtnbkr said:
same here. any ideas?
Click to expand...
Click to collapse
It should work according to one of the comments given about the issue. http://code.google.com/p/android-wifi-tether/issues/detail?id=362#c36
Because I am weary of rooting my phone not being able to return it to stock, I am gonna try it with the unrevoked root first.
goodfellaslxa said:
I originally flashed with toast's rom. Used the recovery .bat to install Flipz's stock root rom.
I then flashed toast's radio rom.
wifi tether did NOT work.
I then performed the above instructions, and viola, it works fine. (i am posting via wifi tether)
I want to thank everyone who is hard at work on these projects, you guys are awesome.
Click to expand...
Click to collapse
i followed this same exactly.
andrew500 said:
Check that the log screen looks exactly like mine does. Did you get any errors when you issued the adb commands?
Look on your sdcard for the android.tether folder and see if fw_bcm4329.bin file exists there.
Click to expand...
Click to collapse
no errors in adb.
and the .bin file is sitting in the directory.
and the log looks like yours.
running toasts ROM
can't get this to work
followed instructions, and when i click on the tether button it instantly says: unable to start tethering, please try again!
log screen is completely blank
any ideas?
fdot said:
i followed this same exactly.
no errors in adb.
and the .bin file is sitting in the directory.
Click to expand...
Click to collapse
I meant the screen in android-wifi-tether, does it look like the screen cap I included? It should have a debug line about the loaded firmware on the first item.
- Didn't see the edit you made with that screen:
Have you done the OTA update? Could be the SD card bug possibly. The log screen shows it didn't load the external firmware.
"Unable to start teterhing try again"
I skimmed this thread, I am using toast's rom.
I have just applied the Unrevoked root. I cannot access the sdcard via adb shell. Any ideas?
When i send command
"cat /etc/firmware/fw_bcm4329_ap.bin > /sdcard/android.tether/fw_bcm4329.bin"
it gives me error msg
"cannot creat /sdcard/android.tether/fw_bcm4329.bin: directory nonexistent"
i followed this same exactly.
no errors in adb.
and the .bin file is sitting in the directory.
Click to expand...
Click to collapse
I meant the screen in android-wifi-tether, does it look like the screen cap I included? It should have a debug line about the loaded firmware on the first item.
- Didn't see the edit you made with that screen:
Have you done the OTA update? Could be the SD card bug possibly. The log screen shows it didn't load the external firmware.
Click to expand...
Click to collapse
I have not done the ota.
-------------------------------------
Sent via the XDA Tapatalk App
My buddy got this phone I want to hook it up as he's not great with tech stuff i rooted with z4root and just need to know how to access recovery cause i didn't see a reinstall packages option in standard recovery ? Any help would be awesome thanks guys
I just rooted with Z4root... then I installed Titanium Backup and then ROM Manager, giving both apps root access (which I verified with the SuperUser app). In ROM Manager I did "Flash ClockworkMod Recovery" and chose the Fascinate option and was told that it downloaded the latest ClockworkMod Recovery. What's my next step?... Choose "Reboot into Recovery" within ROM Manager or do it another way. (My goal is to install Voodoo5 using the stock ROM for now. I have the Voodoo5 file on the SD card.)
EDIT: Whoops. I just realized that I had downloaded the two files to get CWM working but hadn't followed the unzipping, etc. instructions. I'd better go back and read that CWM thread again...
First get CWM working
Then check out this ROM
Or this ROM
and if you really wanna get fancy check out this kernel
Just in case you screw up
If you need more help on each specific topic, just ask in the appropriate areas and there is usually someone around that can answer questions.
Thanks for the quick links... really appreciate it.
BTW - Titanium Backup asks for USB Debugging to be enabled... do you have to do this? It creates issues for me when connecting the phone as mass storage to my PC.
ALSO - I'm assuming I should take an initial backup with Ti before I get too far into this, right? Not having done a backup before... is Ti the best to use? (Do I just choose batch and pick an option(s)? Does choosing "Backup user apps + system data" backup game save data?) EDIT: Just did this and it ran fine but it switched my Live wallpaper back to stock?!? WTF?
monthlymixcd said:
Thanks for the quick links... really appreciate it.
BTW - Titanium Backup asks for USB Debugging to be enabled... do you have to do this? It creates issues for me when connecting the phone as mass storage to my PC.
ALSO - I'm assuming I should take an initial backup with Ti before I get too far into this, right? Not having done a backup before... is Ti the best to use? (Do I just choose batch and pick an option(s)? Does choosing "Backup user apps + system data" backup game save data?)
Click to expand...
Click to collapse
Quick links are awesome! They save time, for sure.
Check the box to ask each time for mass storage and kies. Then you can have debugging enabled, and yes you have to have it enabled or TB won't do it's thing properly. You can switch it back and forth also. That's what I do.
I use TB to do my app and system data backups. Just run a batch backup on user apps and system data, like you said. That's the best option to start with. This isn't the same as a nandroid backup, but it's a good second choice for if you need to wipe data and restore apps quickly like a ROM install that requires you to wipe data/factory reset.
phidelt82 said:
Check the box to ask each time for mass storage and kies. Then you can have debugging enabled, and yes you have to have it enabled or TB won't do it's thing properly. You can switch it back and forth also. That's what I do.
Click to expand...
Click to collapse
Perfect. Thanks! Only thing is... USB dubugging doesn't stay ticked, it's ticked and Ti says it's not, or the connection still triggers a missing driver error message with Vista on the PC. Oh well.
phidelt82 said:
This isn't the same as a nandroid backup, but it's a good second choice for if you need to wipe data and restore apps quickly like a ROM install that requires you to wipe data/factory reset.
Click to expand...
Click to collapse
Easiest way to do a Nandroid backup? BTW - Ti backup ate up 5GB of my sd card?!? Yikes!
Also, regarding this thread:
phidelt82 said:
First get CWM working
Click to expand...
Click to collapse
I get "adb: not found"?
monthlymixcd said:
Perfect. Thanks!
Easiest way to do a Nandroid backup?
Also, regarding this thread:
I get "adb: not found"?
Click to expand...
Click to collapse
Nandroid backup will be there once you get CWM working.
You can do everything from the phone, just read down through the pages to find the people that have done it. They have left instructions using terminal emulator and root explorer. You will find that in a lot of instances many problems will have different ways of dealing with them. You probably don't have the Android SDK which is how you get ADB working on your computer. This isn't critical, it just makes it so that you will have to either install it or use the other means available. (ie terminal emulator and root explorer)
Still getting errors after trying several of the things in the thread... Q:I never did get a robot voice when I ran Z4root and never saw a place to choose permanent... should I run Z4root again? I mean, I was able to install Ti, etc. so I must have root, right? But I think my issues stem from not being able to get redbend_ua into the /system/xbin folder. Astro can't paste it there, Root Explorer can't paste it there, but in the terminal it appears like chmod worked... thoughts?
monthlymixcd said:
Still getting errors after trying several of the things in the thread... Q:I never did get a robot voice when I ran Z4root and never saw a place to choose permanent... should I run Z4root again? I mean, I was able to install Ti, etc. so I must have root, right? But I think my issues stem from not being able to get redbend_ua into the /system/xbin folder. Astro can't paste it there, Root Explorer can't paste it there, but in the terminal it appears like chmod worked... thoughts?
Click to expand...
Click to collapse
Root explorer needs to be mounted RW. There is a button at the top that will say RO or RW.
Sent from my SCH-I500 using XDA App
phidelt82 said:
Root explorer needs to be mounted RW. There is a button at the top that will say RO or RW.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
"Mounted as r/w"
I tried this. Used root explorer to finally get redbend_ua into system/xbin but when I try to run the commands in the post it cannot find redbend_ua. I also cannot cd into xbin within the emulator to ls ... says xbin not found. Explorer can see it there... what gives? do you have to restore redbend_ua inside the xbin directory or will it work to restore it elsewhere?
EDIT: cd to /system/xbin worked and an ls shows the redbend_ua there but the chmod 777 redbend_ua fails to "Unable to chmod redbend_ua: No such file or directory
EDIT to the EDIT: Hang on... think I may have found where I went wrong. What's the terminal command for delete?
monthlymixcd said:
"Mounted as r/w"
I tried this. Used root explorer to finally get redbend_ua into system/xbin but when I try to run the commands in the post it cannot find redbend_ua. I also cannot cd into xbin within the emulator to ls ... says xbin not found. Explorer can see it there... what gives? do you have to restore redbend_ua inside the xbin directory or will it work to restore it elsewhere?
Click to expand...
Click to collapse
Are you doing /system/xbin? The first / is important. You don't need to cd to xbin, though.
Sent from my SCH-I500 using XDA App
Isn't there anyway to flash a rom using odin ? If not are the codes the same for terminal emulator as they are for adb to get cwm working? I'm from the vibrant section of this site running nero v4 right now I have a good understanding of odin for the most part but this not having an easy recovery is bs lol
willsnews said:
Isn't there anyway to flash a rom using odin ? If not are the codes the same for terminal emulator as they are for adb to get cwm working? I'm from the vibrant section of this site running nero v4 right now I have a good understanding of odin for the most part but this not having an easy recovery is bs lol
Click to expand...
Click to collapse
I've never flashed a ROM using Odin, but that doesn't mean that it can't be done. The process should be the same using terminal emulator or adb, just more of a pain. I agree it would be nice to have full CWM Recovery support (or any full recovery support) but I don't have the money to spend on a phone to send to Koush right now to get that done. As soon as I do, this will be done and then I'll have a tester phone for firmware builds. It really isn't that difficult to get it working, though. I've done it probably 30-40 times now and even the first time the only flub was in a typo for the second to last character (thought it was a 1 and not an L)
So you type this stuff in all in one line or what?
willsnews said:
So you type this stuff in all in one line or what?
Click to expand...
Click to collapse
Depending on which parts you are talking about, yes. Each new line is a line of code. If it moves to a new line, hit enter.
phidelt82 said:
Are you doing /system/xbin? The first / is important. You don't need to cd to xbin, though.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Yes. Something's definitely up 'cause when I try to use Astro to copy redbend_ua to /system/xbin the paste option is grayed out for that directory.
monthlymixcd said:
Yes. Something's definitely up 'cause when I try to use Astro to copy redbend_ua to /system/xbin the paste option is grayed out for that directory.
Click to expand...
Click to collapse
I can't remember if Astro has R/W options for the root directory. That may be the problem.
phidelt82 said:
Depending on which parts you are talking about, yes. Each new line is a line of code. If it moves to a new line, hit enter.
Click to expand...
Click to collapse
I just ned to get a custom recovery how did you type it in to terminal emulator? Like extacy how?i just dont want to mess up my buddies phone I want yo hook him up not **** him up lol
monthlymixcd said:
Yes. Something's definitely up 'cause when I try to use Astro to copy redbend_ua to /system/xbin the paste option is grayed out for that directory.
Click to expand...
Click to collapse
You guys are confusing the hell outta me I don't know who's answering me and who's answering you I know this pertains to this thread but im right in the middle of this process and its not even my phone
I apologize for the derail... I got mine working. I had a typo. I'm off to voodoo.
I'm trying to perm root my mytouch 4g using Visionary
I have android 2.2.1 and have successfully temp rooted using Visionary
I download the root folder from HERE
I put them in the root of the SD card and open up Terminal Emulator and type in
su
cd /sdcard/root
sh root.sh
when I type the first line (su) I get the # and am told that Terminal Emulator has been granted superuser permissions.
when I type in the second line (cd /sdcard/root) I get this message
cd: can't cd to /sdcard/root
What could be causing this?
Thanks
Jonathan
The "cd" command is a "change directory" command, and there is no directory called "root" on your SD card, because either you haven't unzipped what you downloaded, or you unzipped it in the wrong place.
Unzipping what you downloaded creates a directory (or a "folder", if you're a Windows user) called "root" that has several files in it -- a kernel module and a script, if I remember correctly. The script loads the kernel module and makes a call to it in order to set S Off.
thank you much, I think I figured out the problem. I'll try again later and see what happens. I'll post back with the results later. Thanks again!
Jonathan
NOTE: Ok, I can now run through the
su
cd /sdcard/root
sh root.sh
commands but when it's done and I check for s-off I don't have it (I still have s-on)
I've tried this twice to no avail. any advise?
i am having the same problem. i've tried this method about 15 times, mostly with visionary r14, but also a couple times with r11. i have also tried the gfree method a couple times as well via the semi-automated method. no s=off!
i have a new MT4G direct from phone upgrade order. i've read of others who have rooted the MT4G before multiple times, but can't do it now with a new phone. i'm wondering if it's something HTC has changed with the newest releases.....
kenrippy said:
i am having the same problem. i've tried this method about 15 times, mostly with visionary r14, but also a couple times with r11. i have also tried the gfree method a couple times as well via the semi-automated method. no s=off!
i have a new MT4G direct from phone upgrade order. i've read of others who have rooted the MT4G before multiple times, but can't do it now with a new phone. i'm wondering if it's something HTC has changed with the newest releases.....
Click to expand...
Click to collapse
HTC was going to install a measure that would prevent "rage methods" from working on their phones. How ever, none of the tech blogs are reporting that this has been rolled out. So i doubt that is the case.
make sure the its set up as sdcard/root. If you've just extracted the folder and copied the extraction to the sdcard it's not set properly.
neidlinger said:
HTC was going to install a measure that would prevent "rage methods" from working on their phones. How ever, none of the tech blogs are reporting that this has been rolled out. So i doubt that is the case.
make sure the its set up as sdcard/root. If you've just extracted the folder and copied the extraction to the sdcard it's not set properly.
Click to expand...
Click to collapse
yes, i understand the root folder in the root of the sdcard, and not 2 root folders. (sdcard/root/root)
like i mentioned, i read posts from a couple people on here with the same problems with new mt4g's after having done it multiple times before with success.
kenrippy said:
yes, i understand the root folder in the root of the sdcard, and not 2 root folders. (sdcard/root/root)
like i mentioned, i read posts from a couple people on here with the same problems with new mt4g's after having done it multiple times before with success.
Click to expand...
Click to collapse
then set up the ADB (see my sig) and do it the long way.
neidlinger said:
then set up the ADB (see my sig) and do it the long way.
Click to expand...
Click to collapse
after doing that, would i start on #4 in this guide?
http://forum.xda-developers.com/showthread.php?t=858996
kenrippy said:
after doing that, would i start on #4 in this guide?
http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
nope you would start @ number 1.
you need to download those files and check the MD5SUM of every download load. the files need to be PERFECT for it to work correctly.
and i cannot stress enough. take your time and read directions. Read through the list a few times and make sure you have a good understanding of what you are doing. Doing that wrong can make your phone an expensive paper weight.
instead of pushing stuff to the "SDK tools folder" you store it to the ADB folder TrueBlue had you create in his walkthrough. And make sure to change your target folder to "c:\adb".
and remember you are choosing to do this. so if you screw it up. it's on your shoulders not mine.
neidlinger said:
nope you would start @ number 1.
you need to download those files and check the MD5SUM of every download load. the files need to be PERFECT for it to work correctly.
and i cannot stress enough. take your time and read directions. Read through the list a few times and make sure you have a good understanding of what you are doing. Doing that wrong can make your phone an expensive paper weight.
instead of pushing stuff to the "SDK tools folder" you store it to the ADB folder TrueBlue had you create in his walkthrough. And make sure to change your target folder to "c:\adb".
and remember you are choosing to do this. so if you screw it up. it's on your shoulders not mine.
Click to expand...
Click to collapse
thanks for all the help/info. i'll hold off for a while to see what else unfolds in the coming weeks in regards to alternate root methods. i don't want to brick this thing, just to get it rooted.
kenrippy said:
thanks for all the help/info. i'll hold off for a while to see what else unfolds in the coming weeks in regards to alternate root methods. i don't want to brick this thing, just to get it rooted.
Click to expand...
Click to collapse
The way this phone is made it's going to be pretty difficult to write a "one click s=off" program.
If you are wanting the benefits of being rooted you can always use VISIONary.apk when you need the root features like AD-HOC tethering or Screen Shots.
neidlinger said:
The way this phone is made it's going to be pretty difficult to write a "one click s=off" program.
If you are wanting the benefits of being rooted you can always use VISIONary.apk when you need the root features like AD-HOC tethering or Screen Shots.
Click to expand...
Click to collapse
what i'd really like to do is remove some bloatware and demo games. (not just hide them) any way to do that aside from perm root?
kenrippy said:
what i'd really like to do is remove some bloatware and demo games. (not just hide them) any way to do that aside from perm root?
Click to expand...
Click to collapse
not really. As soon as you reboot they'll pop right back up.
ok thanks.
Two things.
1. I've decided to put off perm rooting until I can understand adb and use it properly. No need to rush, I've got time.
2. Is it true that given time, effort, and ingenuity there really isn't such a thing as a bricked phone? It can always be recovered, it's just a question of how far you have to go to do it?
I've read around a lot and though I've heard many people talk of bricking their phone, it seems like many say that if you can use things like adb commands you can pretty well fix any issue, it's just difficult.
Like I was saying in point 1, I'm newer to all this and I'm learning so thanks for answering!
Jonathan
lanternslight456 said:
2. Is it true that given time, effort, and ingenuity there really isn't such a thing as a bricked phone? It can always be recovered, it's just a question of how far you have to go to do it?
Click to expand...
Click to collapse
At minimum, I believe the phone requires a functioning bootloader in order to be able to connect via USB to fastboot.
Any update on this? I also just got a mytouch 4g yesterday and am trying to root it. Is it possible right now?
Root the mt4g
Friend, I used the adb method here on xda, after I got the forked childs msg, and restart terminal w/e, make sue to pull out battery. Restart, the LAST THING I DID WAS USE VISIONARY r14, to attempt permroot, took me a week before I figured out to try this, the guide said phone would be rooted after terminal commands went through. So, to recap if u entered everything correctly, (my avg protection was telling me my phone was rooted for a week after I pushed gfree using the adb method but had no s-off, tried visionary permroot, BINGO!) THANKS TO ALL THE HARD WORK/GUIDES ON XDA, using ICE GLACIER ROM, titanium backup, rom manager, root explorer, my internet security (ad free web) set cpu, cache cleaner ng, drocap, couldn't get barnacle to work, the tethering on board works fine. Quadrant standard for benchmarking.
My wifes mt4g arrived today, and I had it perm rooted, with s-off in about 20 minutes, following this guide from the wiki:
http://forum.xda-developers.com/showthread.php?t=858996
Sent from my Nexus One using XDA App
danger-rat said:
My wifes mt4g arrived today, and I had it perm rooted, with s-off in about 20 minutes, following this guide from the wiki:
http://forum.xda-developers.com/showthread.php?t=858996
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
dude this method is great especially if your a noob or cant use adb for whatever reason just use visionary for temp root and then using root explorer move the gfree file to data>local then open terminal emulator and follow the instructions that gives you s-off and allows you to use visionary to permaroot when you reboot and then rommanager it now supports 3.xx so you can flash gingerroms just be careful and have fun
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!
Hello everyone. I have the S4 model and just recently flashed CM11 and now my phone randomly goes into 3G and stays there and then goes back to 4G for enough time to load something and then go to 3G again for sometime and then shut off completely and that keeps repeating. I have tried everything I saw in the #*#*4636*#*# menu and it hasn't helped. Any assistance would be great.
NinjaAngel777 said:
Hello everyone. I have the S4 model and just recently flashed CM11 and now my phone randomly goes into 3G and stays there and then goes back to 4G for enough time to load something and then go to 3G again for sometime and then shut off completely and that keeps repeating. I have tried everything I saw in the #*#*4636*#*# menu and it hasn't helped. Any assistance would be great.
Click to expand...
Click to collapse
There were some build.prop changes that seem to help some T-Mobile users. Have you tried them?
ro.ril.hsdpa.category=24
ro.ril.hsupa.category=6
ro.ril.hsxpa=4
ro.ril.radio-svn=19
ro.ril.fast.dormancy.rule=0
For fast dormacy I've seen 1,2 as well, this depends if it's supported by T-Mobile
Rapier said:
There were some build.prop changes that seem to help some T-Mobile users. Have you tried them?
ro.ril.hsdpa.category=24
ro.ril.hsupa.category=6
ro.ril.hsxpa=4
ro.ril.radio-svn=19
ro.ril.fast.dormancy.rule=0
For fast dormacy I've seen 1,2 as well, this depends if it's supported by T-Mobile
Click to expand...
Click to collapse
I am using ROM Toolbox pro and the only build.prop options I can find that you have listed is the ro.ril.fast.dormacy.rule which is set to 1
NinjaAngel777 said:
I am using ROM Toolbox pro and the only build.prop options I can find that you have listed is the ro.ril.fast.dormacy.rule which is set to 1
Click to expand...
Click to collapse
Yes, the others should be manually added to the file. You just have to use a root file explorer (like ES File Explorer, Root Explorer, CM File Manager) and edit the build.prop that is found in /system. Make sure you have /system mounted as R/W or you won't be able to save the file after editing. Reboot after making the changes
fast dormacy should be set to 0 if carrier doesn't support it, or to 1 or 2 (2 don't know exactly what it does but several people said it's better) if it's supported
Rapier said:
Yes, the others should be manually added to the file. You just have to use a root file explorer (like ES File Explorer, Root Explorer, CM File Manager) and edit the build.prop that is found in /system. Make sure you have /system mounted as R/W or you won't be able to save the file after editing. Reboot after making the changes
fast dormacy should be set to 0 if carrier doesn't support it, or to 1 or 2 (2 don't know exactly what it does but several people said it's better) if it's supported
Click to expand...
Click to collapse
That worked perfectly. Thank you for your help
NinjaAngel777 said:
That worked perfectly. Thank you for your help
Click to expand...
Click to collapse
You got back the 4G, no longer stuck on 3G?
Rapier said:
You got back the 4G, no longer stuck on 3G?
Click to expand...
Click to collapse
It occasionally flips to 3G, but immediately snaps back to 4G so everything worked great.