Related
Hurrah! this has been fixed WOO!.
see here.
well done guys, you have made me a happy g2 owner again!!
Hi Everyone,
i figured we might need to clean up the
http://forum.xda-developers.com/showthread.php?t=805024
conversation.
as i see it, there are 2 issues
1. people receive an unlock code, the phone accepts it but then it cannot find any network
2. people receive an unlock code, have troubles entering the code but eventually get it in ok.
please do not post anything "setting" related - apn's, bands etc as this has been tried and shown not to work (yet)
it might be helpful if people who have issue number 1 could post some answers to some questions.
as i am not at all smart enough to work out what we need to know from these people, id appreciate it if those in the know could pm me what they think could be useful, and ill make a template for people to follow
troubleshooting template
----
----
----
----
Current Theories: (please PM me if i have anything wrong here or if i need to add details.)
-------------
Theory #1
Ghul99: the code is accepted, but the phone is still locked?
http://forum.xda-developers.com/show...&postcount=121
------------
interesting information
this seems to support theory #1
1. i unlocked phone - code entered successfully, and i was no longer prompted to enter an unlock code
2. i perm-rooted my phone - all went to plan
3. i put the vision rom on my phone (http://forum.xda-developers.com/showthread.php?t=834450) loaded ok
4. i put a sim in my phone and now i am prompted for an unlock code.
5. i tried to re-enter my code but it would not accept it (it is the same code from step 1)
Nice idea for taking the initiative to clean up the thread which was getting excessilely long!
I'm hoping we can see some progress in a few days as I'm really missing being able to get any cell reception on a MOBILE PHONE!?
Regards.
I will summerize my knowledge later but one thing upfront.
IntuativNipple posted today in IRC that he found the way to get real S-OFF which would also allow SIM-unlock without code.
So there is hope for a solution, but keep your patience.
Sent from my T-Mobile G2 using XDA App
guhl99 said:
I will summerize my knowledge later but one thing upfront.
IntuativNipple posted today in IRC that he found the way to get real S-OFF which would also allow SIM-unlock without code.
So there is hope for a solution, but keep your patience.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
That's really exciting.
Thanks for bring up the good news!
Sent from my T-Mobile G2 using XDA App
guhl99 said:
I will summerize my knowledge later but one thing upfront.
IntuativNipple posted today in IRC that he found the way to get real S-OFF which would also allow SIM-unlock without code.
So there is hope for a solution, but keep your patience.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Just to help guhl and catch up with some unnecessary posts.
Common solutions like Reboot, different sims to try, Hard reset, flash stock ROM or trigger the unlock window to reenter the code doesn't work
Summary of my knowledge so far
For case 1 which was the original problem my theory is the following.
Cause:
Because of problems with the write procedure to the emmc memory the MCCMCN to which the phone is locked did not get cleared but set to an arbitrary value in my case "C3AB".
The CID value is still the same as it used to be (and also in case of a successful unlock would stay the same) which is "T-MOB010". The CID is a 8 character string and the case where all characters are the same (i.e. "11111111") is called Super-CID.
It is of no relevance if you use or used the hardware or software keys, T-Mobile or third party sources. The only reason where it would be your fault is if you pulled the battery!
The unlock-code that we possess (regardless if official or from a different source) is not valid to unlock the phone from this value "C3AB". If one tries again (directly with the modem, using my modified libril.so or a different ROM) the lock counter will increase.
Potential ways to repair this state:
1. Give it back to T-Mobile if you can In my opinion this is a clear warranty case
2. Find someone who has the MegaSIM and the HTC-diag software.
This will definitely work but it is going to be hard to find someone because the SIM is rare and very new.
3. Wait until (or help achieving) the so called "real S-OFF" state of the phone (when also the radio has security disabled) is reached.
When this is achieved one can disable the SIM-lock without any code.
There are still some very good developers after this goal even if for different reasons.
Which information could help us:
1. The output of the following AT-Command sequence from successful and unsuccessful unlocks
Code:
ATE1
ATV1
[email protected]?
[email protected]?AA
[email protected]?40
[email protected]?80
I will try to write a HowTo later for Windows.
For linux see the following posting from the old thread (http://forum.xda-developers.com/showpost.php?p=8750299&postcount=121)
2. The next thing that would help is a logcat from the first unlock process itself.
Howto:
Start the first logcat using the USB-cable and adb before you boot the phone with the foreign SIM.
Code:
adb logcat -b radio > lc_unlock.txt
leave the logcat running and complete the unlock procedure till the phone reboots (the logcat will end automatically)
As soon as the first logcat exits start a new one using:
Code:
adb logcat -b radio > lc_after_unlock.txt
leave it running for 1 minute and then stop it using <Ctrl>-C
3. The next thing that really would help is that you do not post anything in this thread (use the old one instead) that has to do with:
- the APN
- trying another SIM (you would be very lucky if you had one that fits the arbitrary SIMlock)
- reboot, factory reset, use a stock or non stock firmware
- use the hw/sw-keyboard, wait for the right outside temperature or other esoteric procedures
Finally I would like to ask moodecow to edit his original posting and incorporate or link everything that he finds important or helpful in his posting so that it will stay an top.
That is some very exciting news, thank you for the update!
One quick question, when we achieve radio-s off it esssentially would mean everyone could unlock their phones for free?
Thanks.
Sent from my T-Mobile G2 using XDA App
I have 2 ideas, which can help:
1. For people before unlock - maybe performing S-off before unlock will help.\
2. For people after unlock: in bootloader there is "SIMLOCK" option. When you open it, it shows file not found etc. As I think, it can be used to simlock phone for operator, whose numbers are in some file. There is my solution - find what that files are in phone's source code or by any other method, then put them in right place, enter numbers of operator you want to use, open that "SIMLOCK" and lock phone to your network. I don't know if it will work, but it makes some sense.
ms93 said:
I have 2 ideas, which can help:
1. For people before unlock - maybe performing S-off before unlock will help.\
2. For people after unlock: in bootloader there is "SIMLOCK" option. When you open it, it shows file not found etc. As I think, it can be used to simlock phone for operator, whose numbers are in some file. There is my solution - find what that files are in phone's source code or by any other method, then put them in right place, enter numbers of operator you want to use, open that "SIMLOCK" and lock phone to your network. I don't know if it will work, but it makes some sense.
Click to expand...
Click to collapse
Your first idea sounds reasonable and I would support it.
Your second idea is something that is worked on, but you do not only need the correct file (which is actually called DMCID.dat) but there also has to be some "magic number" (like on a gold card) on the micro-sd card.
an important piece of info to carryover from other thread:
1- No APNs are listed
2- if you try to define one, it doesnt save
No APNs being listed is related to the rom more or less, not the issue we're having.
APN is software issue, correct me if I'm wrong so either way it shouldn't pose as an issue to us.
im saying its a symptom that seems to go along with the problem in the title of this thread, so, worth noting.
ie: i think everyone who has the post-unlock no-connection problem, cannot save APNs. all others can.
if you are a counterexample please say so. that would help.
guhl99 said:
For case 1 which was the original problem my theory is the following.
Cause:
Because of problems with the write procedure to the emmc memory the MCCMCN to which the phone is locked did not get cleared but set to an arbitrary value in my case "C3AB".
The CID value is still the same as it used to be (and also in case of a successful unlock would stay the same) which is "T-MOB010". The CID is a 8 character string and the case where all characters are the same (i.e. "11111111") is called Super-CID.
It is of no relevance if you use or used the hardware or software keys, T-Mobile or third party sources. The only reason where it would be your fault is if you pulled the battery!
The unlock-code that we possess (regardless if official or from a different source) is not valid to unlock the phone from this value "C3AB". If one tries again (directly with the modem, using my modified libril.so or a different ROM) the lock counter will increase.
Potential ways to repair this state:
1. Give it back to T-Mobile if you can In my opinion this is a clear warranty case
2. Find someone who has the MegaSIM and the HTC-diag software.
This will definitely work but it is going to be hard to find someone because the SIM is rare and very new.
3. Wait until (or help achieving) the so called "real S-OFF" state of the phone (when also the radio has security disabled) is reached.
When this is achieved one can disable the SIM-lock without any code.
There are still some very good developers after this goal even if for different reasons.
.
Click to expand...
Click to collapse
i have got HTC MEGA SIM and Almost all DIAG files but
T-mobile G2 case =After putting unlock code NO NETWORK cant be solved because when we give s58 clear command it shows SIMLOCK CORRUPTED
i can post the detailed info and pictures if you want it would be a pleasure if could help in any kind of DEVELOPMENT
BTW
if we don t put code in the same version,same country,purchased in the same lot of handsets and use MEGASIM directly without touching anything than it works perfect
kabir_del said:
i have got HTC MEGA SIM and Almost all DIAG files but
T-mobile G2 case =After putting unlock code NO NETWORK cant be solved because when we give s58 clear command it shows SIMLOCK CORRUPTED
i can post the detailed info and pictures if you want it would be a pleasure if could help in any kind of DEVELOPMENT
BTW
if we don t put code in the same version,same country,purchased in the same lot of handsets and use MEGASIM directly without touching anything than it works perfect
Click to expand...
Click to collapse
Posting any further details and/or pictures would be much appreciated!
So if megasim has failed due to corruption I think that the only way to solve our issue is to write directly to emmc partition holding locking information. And I don't now how easy and plausible this is...
I think if we get S-Off for Radio, we'll be able to write to that partition. I hope
andrewklau said:
I think if we get S-Off for Radio, we'll be able to write to that partition. I hope
Click to expand...
Click to collapse
I am a little bit worried about writing this information directly because the partition will be encrypted.
And also copying the complete partition from a working phone or one that is still unlocked will not be an option because the IMEI will also be there and we would not want to overwrite that.
So my hopes are more that there is some kind of a restore procedure from a secure area (I know that Nokia phones can do this, but HTC ?) or that we can lock the phone again with the SIMLOCK option in hboot.
Sent from my T-Mobile G2 using XDA App
well I guess time will tell, does tmobile or htc do replacements (or has anyone tried) for phones no longer on a contract or that are now unlocked?
Sent from my T-Mobile G2 using XDA App
andrewklau said:
Posting any further details and/or pictures would be much appreciated!
Click to expand...
Click to collapse
here we go Pictures first Video coming soon
First Red colour is the error we get on when we try the command
1=clear s58 data
2ND IMAGE is the one when we press the DEVICE INFO
today is sunday not much time will upload the full clear video tommorow and still i have not tried to the all options of the diag maybe it can repair it but sure i will do some more things tomm.
88
I have tried to use my HTC vision G2 as I unlocked it but after that I am unable use as I am unable to find anything which would be hlpful for me as I have the first case problem. I just want to know that would it help me that if someone would flash my HTC Vision G2. I just want to know about that as now I am in Pakistan
Sent from my T-Mobile G2 using XDA App
**UPDATE**
This method causes your serial number to change to 00000000 (which isn't a problem as such as this isn't currently used for anything) but there is a new method which involves directly hex editing the nv_data.bin file, which may be faster and does not change your serial number. You can find the details here: http://forum.xda-developers.com/showthread.php?t=843323.
**UPDATE**
First up I'll say that I'm not incredibly familiar with Galaxy S firmware changes/modding, and this mostly builds on work done in these areas, so not all these steps may be necessary but they worked for me. If someone can suggest a faster way to do this/unnecessary steps then please go ahead and reply with them!
This unlocked my Network Locked Australian Galaxy Tab and so I assume should work for others.
You should back up your /efs/ folder before you proceed as you may need this to undo if something goes wrong.
*I take no responsibility if something goes wrong!*
Requirements:
Root access
repair_nv_data.zip (from http://forum.xda-developers.com/showpost.php?p=8942669&postcount=94)
Java
Busybox
The Android SDK for ADB, Root Explorer or some similar file system explorer/editor
(If you have US firmware with no Phone software, you may need to flash European firmware as described here: http://forum.xda-developers.com/showthread.php?t=838250 ).
Firstly, on your phone dial *#7465625# and check if the Network Lock is set to [ON], if so then your phone is locked (duh), so continue.
1. Use Superoneclick (http://forum.xda-developers.com/showthread.php?t=812367) to root your phone (the other z4root method may work as well, but this isn't what I used).
2. Either use ADB or some other method to rename or delete (backup first):
/efs/nv_data.bin.md5
/efs/.nv_data.bak
/efs/.nv_data.bak.md5
(I just used Root Explorer to rename them to something else).
3. Restart your phone and then go into the /efs/ directory and see if the 'nv_data.bin.md5' file has been re-created by your phone, as long as it has been created then you can proceed.
4. Go to http://forum.xda-developers.com/showpost.php?p=8942669&postcount=94 and download the repair_nv_data.zip file (the credit for all of this mostly goes to that thread and helroz).
5. Install 'busybox' from the Market. Once you install it, you actually have to run it and properly install it (the Market app is basically an installer) - the files in the above zip have a dependency on this.
6. Extract the above zip to your PC, plug in your Tab in USB debugging mode. Run the Step 2.bat from the extracted file. You may need to allow the script super user access several times. This should copy the /efs/ and a bunch of files into a directory with a french name.
7. Run the Reparation_nv_data.jar file. (You will need Java for this step.) It will prompt you to enter two numbers, which are your pseudo-unlock codes. I entered '11111111' and '11111111' (eight 1's) both times. This rewrites the nv_data.bin file to be simunlocked with these details.
8. Run the Step 4.bat. Your superuser app (the one installed when you rooted using SuperOneClick) will need you to allow each command to have root access so keep an eye on your Tab. You may need to press y/n a few times if you encounter errors. This is uploading the edited nv_data.bin onto your Tab.
This batch file will stop several times and need you to hit a key when it pauses. My Tab rebooted halfway through this batch file - when it did this I waited for it to fully reboot back to the lock screen before pressing a key to make the script continued while the Tab was actually able to respond to its commands.
9. Towards the end of its execution it rebooted a second time. It paused during loading up and had some yellow writing on the screen saying it was updating media (I assume it was rebuilding the nv_data.bin). Leave it for a minute and it will prompt you to reboot/some other options. Just press whatever it wants (home I think) to reboot the phone - you don't want any of the other recovery options.
10. Go into your dialer and put in *#7465625# again and (hopefully) voila! Your phone should no longer be network locked. Try a SIM from a different provider to make sure.
Enjoy!
Edit: I had to go out and actually buy a prepaid SIM to confirm that all was working with a different provider. Attached are screen caps of my Tab on two different networks, as well as the network status screen, making/receiving calls etc. all works on both.
Awesome man, thanks.
This is much better than the 2 month wait we had for Galaxy S unlocking.
Hello, I'm french and i use your post to unlock my Galaxy TAB SFR ''réunion island'' and she is unlock thanks for your AMAZING post for unlock TAB
Ps: For unlock my TAB by SFR REUNION, he tell me 150 Euros.... Vive smithdc & helroz
Works well! I had little trouble running java on windows7. But changing compatibility mode to windowsxp sp3 and check run this program as an administrator solved the problem.
Thanks for easy guide!
tacoda, you mean for running the .jar file? or for installing Java itself? (I assume the former).
Sweeet thx , curious if unlocking the AT&T version has hardware only set to AT&Ts 3G frequencies, so 3g wont work on tmobile or is it capable of running 3g on tmobile with a unlocked AT&T tab?
smithdc said:
tacoda, you mean for running the .jar file? or for installing Java itself? (I assume the former).
Click to expand...
Click to collapse
Running the jar file. I didnt know how to run it.
Sent from my SGH-T959 using XDA App
Does the sim card and/or sd card should or should not be plugged in during the unlocking progress?
It shouldn't make a difference Zeron.Wong.
jay_jay_n said:
Sweeet thx , curious if unlocking the AT&T version has hardware only set to AT&Ts 3G frequencies, so 3g wont work on tmobile or is it capable of running 3g on tmobile with a unlocked AT&T tab?
Click to expand...
Click to collapse
Traditionally, AT&T and T-Mobile hardware used different radios, it was more than just firmware. That's also true on the little brother Galaxy S series, the Vibrant has a different radio than the Captivate (though the Vibrant radio DOES have 1900 band in the hardware, for some reason).
Kudos to smithdc for this awesome guide! I saved a lot of money thanks to him. Congrats again.
Bump, is there any way to sticky/pin this for people?
So your saying if I use this method and install my tmous unlimited sim I can get calls and 3g or do I need a prepaid sim
I'm not sure on how T-Mobile are blocking, but if it IS my IMEI then you would have to use a SIM from a different network.
If they are blocking your IMEI on their network, then you would have to use a SIM from a different network (as a different network, wouldn't be blocking this IMEI number). Changing it to a different SIM on the same network won't help as your IMEI is for the device itself.
I just want to clarify something..
I have a T Mobile Tab and want to use a SIM I have for ATT.
Will I have to flash my device with the EU firmware first in order to get the phone software on it..then do the rest of the unlocking steps?
Assuming thats correct..after unlocking it I then can put my ATT sim card in and it should work for calls and data (Edge only) with not having to tweak any setting at all? Or do I have to set up my wap.cingular connections for the data like on a WM phone on ATT?
And if I want to get back to original out-of-the-box firmware from T Mobile (like if I had to send it in for repair) I just have to flash stock T Mobile firmware and its back completely to original?
Thanks..and wow am I loving this TAB !!!
You'll need to set up your APN data for AT&T, yes.
Thanks for the fast reply. As for the flashing of the EU rom..is that the only/best way so far in order for me T Mobile Tab to get the radio software on it. I was thinking I saw an APK for the radio software someplace but did not know what way was better.
I just want to be 100% sure bfr I take the jump to unlocking and playing with the phone part
thanks
I got a quick couple of questions:
1. If I restore original firmware (Canadian), does it relock my phone?
2. Where can I get the Canadian firmware release? I see EURO and US, but no Canadian.
I read on one of the other threads that sim unlock method also changes your imei number. Is this really case?
clubtech said:
I read on one of the other threads that sim unlock method also changes your imei number. Is this really case?
Click to expand...
Click to collapse
Yes, it will set your IMEI to a bogus one that will get your T-Mobile internet access disabled after 1/2 hour.
My apologies if there is a thread for this somewhere else.
I have spent the last 2 days looking for one but have either been blind to it or I'm "special"
I currently own the HD2.
Purchased in February of 2011 and am with T-Mobile.
I did manage to flash my phone almost immediately after purchase to a NAND version of Android 2.2
Hspl 2.08
MAGLDR version 1.10
Baseband Version:
15.39.50.07U_2.10.50.26
Kernal Version:
2.6.32.15-g66f6ed7-dirty
[email protected] #2
Build number:
2.29.405.5 CL293415 release-keys
Software number:
2.29.405.5
Browser version:
WebKit 3.1
Now I have no idea if all those numbers are needed or not but, better safe than sorry right.
Anyways, I have had no real issues outside of data connection strength but would like to upgrade to a newer version or OS.
I was looking at this particular one.http://forum.xda-developers.com/showthread.php?t=1275119
But I have no idea how to flash over my current one.
Things such as; CWM, and the MAGDLR various toolkits that have been developed in recent months and other vocabulary of the trade has thrown me for a loop.
I am interested keeping things like calendar events, text messages, photos, audio, etc. The basics if you will.
Please, any help or direction would be most appreciated as I am totally lost.
Thanks in advance.
Verkruk
I guess you need to go back to wm6.5 rom and upgrade from there..
You can download the stock rom from htc official website..
Well, if you have a google account linked (doh), calendar events are usually synced with it. Audio and photos, are usually saved in separate folders on your sdcard, so they will remain even if you changed the ROM.
However, I don't usually save my text messages when I'm upgrading, I don't care if I lose them, and they are not backed up automatically. So you need to look for an app in the market (look for "SMS backup" or something) .
After you've backed up your stuff, follow this tut written by me :
http://forum.xda-developers.com/showpost.php?p=16528026&postcount=7
It's for everyone that thinks he's special (jk) . But you need to edit step 8 and step 10.
in step 8, you will need to go to the ROM's thread that you are to install (obviously)
in step 10, you will need to edit those numbers (150, 5) in correspondence to the ROM you are to install and to what device you own (T-mobile or European).
Good luck.
Marvlesz said:
Well, if you have a google account linked (doh), calendar events are usually synced with it. Audio and photos, are usually saved in separate folders on your sdcard, so they will remain even if you changed the ROM.
However, I don't usually save my text messages when I'm upgrading, I don't care if I lose them, and they are not backed up automatically. So you need to look for an app in the market (look for "SMS backup" or something) .
After you've backed up your stuff, follow this tut written by me :
http://forum.xda-developers.com/showpost.php?p=16528026&postcount=7
It's for everyone that thinks he's special (jk) . But you need to edit step 8 and step 10.
in step 8, you will need to go to the ROM's thread that you are to install (obviously)
in step 10, you will need to edit those numbers (150, 5) in correspondence to the ROM you are to install and to what device you own (T-mobile or European).
Good luck.
Click to expand...
Click to collapse
really good tuto... hope it helped him (or her... dunno )
I keep getting a rapitool error and am unable to continue.
It would seem that I have successfully bricked my device.
Typical really +(
Thank you though so much for your help!
And I really do mean that. Least with your help I stood a chance +)
Will keep trying and will update you if I see any changes.
It took several hours and a few breaks, but I got it up and running. Again thank you so much!
If you’re an owner of the LG Quantum/c900, you may have noticed that your carrier hasn’t enabled Internet Sharing on the device. This is a universal problem for all carriers with the exception of Telstra (Australia).
Internet sharing is a feature that Microsoft made available in Mango, to carriers but not consumers. The drivers are available to manufacturers, who can choose whether or not to include them in their Mango drivers and can also be removed by carriers before pushing them out to the public.
Now let’s go back to that bit about Telstra… It is true that this carrier selected to include the tethering drivers in their mango driver package. There was much speculation about changing registry values to get the update on a different carrier, but this would not work because of the model variations - the Telstra Quantum is labelled c900k, with the Bell variation being c900b, while AT&T and other international models are simply c900). There are actually no hardware differences between the two, so I’m unsure why they’re labelled differently.
Now, in order to get tethering on any Quantum, we need to flash the Telstra ROM. If you’re uncomfortable with flashing ROM’s, or have never done it before (it’s easy, trust me!), you may want to stop here, although I have included easy instructions for newbies. Please note that flashing a ROM will delete/erase all content on your phone. You can reinstall apps more easily by viewing your purchase history in the Zune software! Alternatively, you can read how to enable wired tethering (which doesn’t require flashing) at the bottom of this post.
**Note that this will break MMS! The only solution (at this time) is to carrier unlock your phone and run the LG Network Setup tool, available from the marketplace!**
First of all, you’ll need to download the package (which weighs in at 372 MB) after the break, which has:
A modified DLL that allows cross-model flashing.
The LG flashing/engineering tool.
The LG United Mobile driver.
The Telstra Mango ROM
Download this file (Deposit Files) and extract the contents to wherever you want.
Start your phone in “Emergency Download” mode; you can do this by holding the camera and volume down button while pressing the power button. A screen with an exclamation mark should appear, with the text “EmergencyDownload”.
On your PC, open the “LGDP2 V36 Flashing Tool” folder, followed by the “Setup” subfolder.
Launch the included executable and proceed through the installation process. When asked for the serial key, copy and paste it from “Serial Number.txt”. Finish the setup. You may get an error related to mqmailoa.dll, disregard it.
Copy the “DOWNLOAD” folder from the flashing tool folder and paste it in C:\, overwriting any file conflicts.
Install the LG Modem Driver found in “LG Modem Driver (MA 4.9.7) in your extracted directory.
Connect your phone to the computer via USB and allow the drivers to install.
Disconnect your phone now.
Navigate to C:\DOWNLOAD and launch “LGDP2_V36_UMTS.exe”
The tool will launch with a pop-up asking for Model Division, select “UMTS” and press OK.
You will be presented with another pop-up, asking for Port Selection. In “Easy Select” on the left hand side, select “All”.
Under “DLL Selection”, point the program to the DLL located in the directory you originally extracted everything to, under subfolder “DLL”
Under “Download Configuration”, point the program to the Telstra Mango ROM, which is also in the extracted directory, under ROM. Press OK. Ignore warnings about being “Unable to Find Monitor Port”.
Press “START” in the upper right hand corner. DO NOT CONNECT YOUR PHONE YET!
NOW reconnect your phone. The process will begin, allowing you to view detailed information related to the progress in whatever COM port window the phone is connected to. Be patient as the process may take some time. DO NOT DISCONNECT YOUR PHONE!
When the progress reaches 100%, you may disconnect. Now quickly run through the setup of your phone. At this point in time, you can close the LG Flashing Tool.
You’ve now officially flashed the ROM.
There are still a few steps to get tethering! Currently, you are running Mango only. The latest LG/Telstra drivers haven’t been installed yet.
Navigate to settings on your phone and verify “Date and Time” are set to the correct values, and set “Region and Language Options” to the appropriate values for where you reside and tap “Accept Changes and Restart Phone” at the top.
Reconnect your phone to your computer and launch Zune. If required, go through a quick name setup and then allow the phone to check for updates. The update “LG Update for Windows Phone” will be installed. After this, restart your device and voila! You can now enable Internet Sharing from the Settings menu! Telstra has also released the 8107 update, so you don't have to use the CAB sender method to get the keyboard fix.
If you want to remove the Telstra boot screen (or even replace it with your own), you can root unlock your device using WP7 Root Tools 0.9 (requires interop unlock first: see here (follow the LG method, obviously) http://forum.xda-developers.com/showthread.php?t=1271963, and then use this tool http://windowsphonehacker.com/articles/app_wph_tweaks-04-09-12
If you’re uncomfortable with ROM flashing, or don’t want to have to re-sync your content/apps, there is a less efficient but easier to apply method of tethering via USB. This hack is applied via the LG MFG app on the phone, but requires a reboot every time you apply it.
To do this, follow these instructions:
Install the LG Pilot Modem Driver from here! (Deposit Files).
Open the dialpad on your phone and dial “##634#”. The MFG app will install and open.
You’ll be presented with a password field. The password is “appmfg#*#”.
Open the “Engineer Menu” and then “Port Setting” followed by “USB Switching”.
Take note that the default value here is MS COMPOSITE” - if you don’t change this back later, you’ll be unable to sync your phone via USB with Zune.
Select “QC COMPOSITE” and press OK to reboot.
Connect your phone to your PC, the drivers will be automatically installed.
Open Device Manager, and find “LGE CDMA USB Modem” and open the Properties dialog. Under the advanced tab, add the additional string “AT+CGDCONT=1 “IP” “your carriers APN” (isp.cingular for AT&T, “pda.bell.ca” for Bell Canada, etc). Apply the setting.
Create a new connection, by opening start and typing “dial-up”, click “Setup a Dial-up Connection”
Select the “LGE USB Modem” as the source, and set the phone number as either *99***1# (America/International[?]) or *99# (Canada).
Turn off the Data connection on your phone prior to dialing!
Connect! There’s no username/password.
The next time you want to sync via USB, you need to change back to MS COMPOSITE in MFG.
oustanding post. thank you for all of this very useful information summarized in one place! We Quantum users seem to be very neglected unfortunately.
---------- Post added at 11:58 AM ---------- Previous post was at 11:01 AM ----------
a few questions for you...
Are there any negative consequences for at&t (US) subscriber to flashing this ROM?
I assume I will need to flash back to at&t ROM before the next update is pushed out?
Also, does the Marketplace recognize region and only offer certain apps, etc.?
Are there any performance differences?
Any other consequences?
Thank you for posting! I've been looking for wifi tethering on a C900B on Bell for awhile.
No problem
Sent from my LG-C900B using XDA Windows Phone 7 App
There should be no noticeable differences, if you use MMS, take a look at one of the other threads in the Quantum forum, it will explain how to get it working again. Also, if you chose not to rollback, you will stay on the Telstra update channel (which isn't a good one as they haven't released 7740 or 8107 yet) and will continue to receive updates from them as they are pushed. If you'd like, I can post a tutorial later for updating to 7740/8107 to fox the keyboard issue. In reality, unless your carrier is to release tethering drivers, there's no real reason to rollback unless you're experiencing other issues.
Thanks for the kind words,
Mitch.
Sent from my LG-C900B using XDA Windows Phone 7 App
What's wrong with the keyboard?
thejaredhuang said:
What's wrong with the keyboard?
Click to expand...
Click to collapse
I mean the issue with the virtual keyboard disappearing while typing, which is fixed in 8107.
Any update for 8107?
THANK YOU!!!!
I tried to do this before but I had no idea how to do it...
so the flashing failed, obviously =P
I'll try again with your guide x)
I switched from a samsung galaxy s (i9000) to this phone 6 months ago, and wireless tethering was the only feature I really missed.
Thanks! =)
Also had trouble getting into Download Mode. Used this trick from this user:
http://forum.xda-developers.com/showpost.php?p=12472295&postcount=8
Space + Power
And here is a faster mirror
For some reason... as a secondary effect to this...
The wireless status now displays an H instead of 3G...
Am I connected to my carrier's HSPA network now? ?
---------- Post added at 06:45 PM ---------- Previous post was at 06:07 PM ----------
Don't know how google docs works for sharing, but here is another link in case you need one =)
https://docs.google.com/open?id=0B1WDFOpp7DELNEw5eTBtSUFSSFdWcEc4dGZWTERGQQ
I can confirm this guide works flawlessly on at&t Quantum!! It is very simple and takes about 30 minutes to complete. If you want tethering on your non-Telstra Quantum, there is no reason not to just this and you won't regret it!
---------- Post added at 04:39 PM ---------- Previous post was at 03:49 PM ----------
Actually I have to somewhat qualify my previous statement. The installation went perfectly, however there are some after effects. For instance, my data connection no longer works and as stated previously by others, MMS no longer works. Also, I noticed, as I suspected, the marketplace is region specific and some apps are not available with the Telstra ROM. An example would be the Xbox Extras apps. The marketplace thinks I am outside the US even though I am definitely in the US on at&t network. DAMN! This is alittle annoying and it makes me wonder what other apps I am not able to get access to with this ROM. OH well, I guess there are positives and negatives, but wifi tether is worth it in my opinion.
Just be aware, there are some minor consequences. I'm sure I can get most everything working again, but may take some tinkering.
thejaredhuang said:
Any update for 8107?
Click to expand...
Click to collapse
look at the update thread in development and hacking.. Its something like oem updates and I believe 8107 is in the title as well. You can update any phone to 8107 there. Just make sure you follow all the instructions.
Sent from my LG-C900B using XDA Windows Phone 7 App
Perhaps the icon text in the registry for your hspa connection before was set set to 3G.. For whatever reason. There's nothing that should have happened by flashing this ROM. I'll look into the MMS issues, there should be an easy solution.
Sent from my LG-C900B using XDA Windows Phone 7 App
See this thread guys, it worked for me:
http://forum.xda-developers.com/showthread.php?t=1068893
Hey, I did this using a Bell LG Quantum and I ended up not being able to use my Cellular data, is there anything that I could be doing wrong that would cause this, I may do a re-Flash since I have reverted back to Bell's ROM
Anyone else having problems downloading this file.
I also tried the faster downloading mirror and it just times out.
I'm still looking for an MMS solution that will work for everyone. It appears Telstra removed some of the ADC settings in the MFG app, so I'm looking for potential workarounds in the registry.
As for the servers, they're working fine for me? If need be, I can re-uplod/email the files to you.
As far as I was able to see once you flash the Telstra firmware you'll get the update to 7.10.8107.79, so don't mind which version you flash
Lg configuration app fixed MMS and APN too.
Diomorgan said:
As far as I was able to see once you flash the Telstra firmware you'll get the update to 7.10.8107.79, so don't mind which version you flash
Lg configuration app fixed MMS and APN too.
Click to expand...
Click to collapse
Can you give me some more details on your specific configuration? What model of Quantum are you using/what is your carrier? What version of LG configuration app are you using?
Hi Devs,
I've just joined and am uncertain of the proper place for this thread. Apologies if inaccurately posted.
I have the T337A, which I have rooted on ANF4, but I cannot find a recovery. I have read and read but am not finding the solution to my little project. I would like to get a safestrap on this locked bootloader so that I can install and learn to write custom ROMs. I have tried a safestrap but it was not for this specific device and did not work. I have also installed and purchased CWM Recovery and TWRP Recovery, in my learning process. The problem with the recovery is that there is no custom recovery written for this device and the bootloader is locked, as this is the AT&T WiFi/LTE version. So it looks to me like I need to figure out the partitioning image somehow in order to make a safestrap work on this device...as step 1. Is there anything else that I can do with this locked bootloader? I would love to have some help in writing a custom recovery and ROM for this device but I am a tiny tiny noob here and not a hard core programmer. If I could get some feedback on places to start for such a daunting task, it would be great. I guess one thing that I do not understand is why I cannot make my current rooted ROM the default recovery in TWRP. It asks me to choose from the list of supported devices. I understand that it goes: NAND --> aboot.img/bootloader --> recovery/or/kernel --> OS/or/ROM? If this is close to accurate then I would have to write something to the NAND?, which I'm not sure what is yet, in order to hijack the factory bootloader and then write the partitions on the sdCard for the ROM, like the safestrap folks wrote? It looks to me like they also included a version of TWRP touch which I used on the S4 yesterday and was really cool, so I guess that would be needed as well and is also why TWRP does not work for me now...it cannot hijack the locked bootloader. How do I hijack this hard headed thing? fastboot does not work to this device. In the process of this project, I have also run into a roadblock trying to update the /system/framework/framework-res.apk, in the manner that a flash needs to be done, I think. I want to change the /res/values/bools/bools.xml switch "voice_capeable" to true. AT&T or Samsung disable this on this version of the tablet, I guess to sell tethering or something else I'm not familiar with...but the way it looks to me, everything is configured on the device and I have a phone number provisioned for data at least. Why can't I turn on this switch and use the phone portion of the device? Any time I tickle the running framework-res.apk, it kills the OS. I tried compiling an update.zip aligned and signed with test keys or something like that but when I flash it, it fails with wrong footer and invalid signature...then it wipes me back to the stone ages. I warned I was a noob..! ...but not scared to brick some shtuff in order to learn this and write some custom solutions. An after thought...is there a solution for a bootable extSdCard for Android? This might lead to some options if it is possible.
Gathering phone info...
Collecting information. Be patient! Do NOT disconnect the phone!
Model: SM-T337A
Android Version: 4.4.2
Sales Code: ATT
PDA Version: T337AUCU1ANF4
Phone Version: T337AUCU1ANF4
CSC Version: T337AATT1ANF4
Product Code: SM-T337AZWAATT
HIDSw Version: T337AUCU1ANF4/T337AATT1ANF4/T337AUCU1ANF4/T337AUCU1ANF4
Board Platform: MSM8226
Serial Number: R32FA00PMRF
Imei: 3534.............
Unique Number: C1604.......
Connections: AT,MTP,MTP
Battery Status: 4.28V (94%)
Network Type: GSM
SuperSU Pro v2.40
TWRP donate latest
CWM donate v5.5.3.7
BusyBox Stericson donate v1.23.0
Titanium Backup Pro latest
xPosed v2.7.1
Wanam xPosed v3.3.1
NinjaMorph Pro v2.8.2
ROM Toolbox Pro v6.0.6.5
RootLogger Pro v1.9
Nandroid Backup v4.4.5
Next Launcher 3D Shell v3.20
Root Firewall Pro v2.1
SetCPU v3.1.2
w/respect. PitPin
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
We had a dev working to get safestrap, but he struck out. So if you can get it, I'll test. I too have the 337a. Sucks to have a locked bootloader and no dev interest.
pre4speed said:
We had a dev working to get safestrap, but he struck out. So if you can get it, I'll test. I too have the 337a. Sucks to have a locked bootloader and no dev interest.
Click to expand...
Click to collapse
Thanks pre4speed. I am taking a look at the two tasks again tonight and decided to take the res/bool = voice_capable issue on first since this will determine how brickable this device can be for me. If I can use it as a regular modem phone then I might be a bit more careful with the bootloader project I did some more tinkering with the framework-res.apk ...specifically the /res/values/bools/bools.xml resource and tried the following:
-------
Factory wipe
Flashed sammobile.com T337AATT1ANF4 firmware
Rooted
SuperSU
Busybox
Froze AT&T update service and others involved
Titanium backup and pulled a good backup
Online Nandroid and pulled a good backup
Installed my XDA app. of course..!
-------
Framework-res.apk:
Used total commander to copy the running apk off to the sdCard and then my PC.
Decompilled in APKStudio2.0.3b-Windows (I am also using Ubuntu 14.04 if there is a better way here..also Android Studio on both OS...just learning).
Edited my value.
Recompiled with zip align/sign option.
***Now here in lies the problem, if I haven't already created one above ***
The random article I dug up said that in order to get past the wrong footer and signature issue, and stone-age wipe, when attempting this via abd sideload with an update.zip, is to now copy the edited file back into the original APK using 7zip in order to retain the original signing keys. When I open the original APK archive, it does not show the resource folders deemed "important and I should not jack with them" in the compiled APK (mainly values/* folder). The article mentioned the resource folders such as res/values/bools are compiled and hidden and that I needed to copy over the new resources.arsc file. I see this in the newly compiled APK I made but it also put the Manifest.xml and /res folder in there. Do I need to copy all of that or just the compiled resources.arsc file? I did all and it boot looped me so I'm guessing that I either did something wrong or this was not the right answer. The last part was to chmod the new APK, use total commander to mount the folder as rw, copy over the file, and reboot. All of that worked and I had to reboot many many times...loop.
That is where I am on the modem part and am going to attempt copying just the resources.arsc in a few. I will post more on the bootloader side soon, as I've been researching what goes on from the time I push the power button until the time I swipe the first screen. Lots of reading
w/respect - PitPin
Copying only the resources.arsc file from within the newly compiled apk back to the original framework-res.apk made some progress. Now I have the phone dialer app icon in my apps drawer... but it is failing complaining about contacts. On to the next round of research..!
PitPin said:
Copying only the resources.arsc file from within the newly compiled apk back to the original framework-res.apk made some progress. Now I have the phone dialer app icon in my apps drawer... but it is failing complaining about contacts. On to the next round of research..!
Click to expand...
Click to collapse
Stalled out temporarily on the tab project as laptop hard drive bought the farm. Back in action and made some progress on the tab voice_capable issue. Everything appears to be there and in working order but the SMS modules. I think this has something to do with why the contacts app is blowing up but not sure yet. GoSMS and EXDialer seem to work together without blowing up but the dialer taps the modem and then dies. Taking a break from this to start a thread on rooting the AT&T Alpha. I'm about half way through the exploit on that project. Any input on what might be my SMS problem on the tab 4 would be appreciated. Attached are a few screens.
Does anyone know how to removed the caution sign on the left corner it keep telling me unauthorized action have been detected.
I am in the same boat, I so wish this would come through because I do love this little tab.
same boat
/baker said:
I am in the same boat, I so wish this would come through because I do love this little tab.
Click to expand...
Click to collapse
so did you finally get it going or what?I have been wanting to get my Tab going as well. I've Rooted it and paid for an unlock even, which worked fantastic by the way...Thanx XDA!!! The rooting guide I got from here was right on point,no problem at all!!But anyways, I have it on metro pcs now on the unlimited $60 plan which is awesome (.REAL unlimited internet with NO THROTTLING ) for me because now at home I run pda.net, which gives me very good, fulltime, internet for my home computers as well as the ability to stream everything onto a large screen or even via windows when we want to watch with all the bells and whistles! No lag at all usually,and I don't use my hotspot because of the usb internet connect on pda.net. When I do use the wireless connect, it doesn't take any of the allotted hotspot usage up either!!All in all it's a great deal for me. I just got a new sim for it, called in the imei to metro ,which in turn gave me a phone number and data account, and presto!Been on the net ever since! Now that I've had it for over a month ,I wanna get the voice capability to work as well, being that I am paying for 2 lines now. Although I can use the old trusty hangouts dialer with the GoogleVoice easily enough. I want to be able to use my metro number mainly because these phone companies charge and charge and charge, never caring about us,or our need to have communication at our disposal at all times.Cell phones are by far not inexpensive and the internet wasn't started for us to pay aan arm and a leg to use.Anytime I come out good while dealing with a wireless company. it's a stupendous event,I'm telling you!! Heck ,I'm writing from my home computer now, going through the Tab at this very moment! Nevertheless, I'm wanting for the devs, to come through as well. With maybe even a new rom,sans the at&t stuff, of course, since I do now have a different carrier? Heck, the Tab is even great for when we travel! 24/7 unlimited internet /streaming , and the screen size is much better than the phone screen ever was!I just really wanted to thank XDA for the work they put in to help us part - timers out,Ive been rooting and unlocking and bricking and un-bricking for quite some time now,I even repair phones now actually,but the programming and the putting it all out here for guys like me to have fun and tinker with these phones would be entirely impossible without the DEV'S and their hard work for SURE...Thanx Guys!!You ROCK!