Database Users

Devs Need volunteers that are using 1.5

This is a call to arms for anyone still running 1.5 on their eris. We (developers) need people to capture the update process using wireshark (or an equivalent). This is needed for a new root attempt, but sadly all of the devs have already updated to 2.1 so we can't do this.
First go here and download the RUU:
http://www.pcdphones.com/downloads/Eris%20MR1.zip
Next you need to go to verizon's website and login to your account. Click "Suspend/Resume Service" and suspend your phone. You can resume service on the phone after you are done here with no penalties or charges.
Please follow these directions, taken from the first root thread
bftb0 said:
Steps:
[Binny knows this, but if anyone else is reading, it is the same as a factory reset - you will lose all your settings and apps (but not the contents of the SD card)]
1) Unpack the 1.16.605 RUU - by running it as if you were going to actually do the RUU using the USB cable and your host PC, but stop right before you would apply the update to the phone. Pull the "rom.zip" file out of the temporary area that the RUU installer unpacks.
(Poke around under C:\Documents and Settings\<Username>\??? (I can't remember - you'll see folders with names that look like registry entries). You have to do this while the RUU installer is sitting there waiting for you - if you cancel the install, it will nuke everything it unpacked. I just made copies of the entire subtrees.
2) Cancel the RUU install.
3) Move the ROM.ZIP file to the root folder of your SD card, and rename it PB00IMG.ZIP
4) You can cancel the RUU install session on the PC, and unplug the USB cable if you want (so long as you have a well-charged battery!)
3) Power down the phone, and boot it back up holding the Call and End buttons simultaneously
4) Scroll down (or whatever it asks) to go from Fastboot mode to HBOOT mode
5) The phone will automatically discover the PB00IMG.ZIP file, and unpack it and verify it.
6) It will ask you if you want to install; when you (select and) enter Yes, the phone will reboot, and come up again - appearing as if it is repeating the same thing. This time, however, it won't stop and ask you - it will just begin the install.
7) Wait... Wait... Wait... Wait... and then wait some more. If I recall correctly, it seems to hang a little bit at the HTC splash screen after the reboot. That is normal - just WAIT and let the phone do it's thing.
That's it, except for:
8) You probably will want to dial *228 and choose option 1 to complete the programming of your phone - it will reboot after it completes.
Click to expand...
Click to collapse
After you are done, DO NOT start the OTA update that it prompts you to do.
Now we are going to install wireshark and setup the capture environment:
Download wireshark from http://www.wireshark.org/download.html for your versions of windows
Install it - make sure you also install WinPcap
At this point you should turn off any wireless encryption on your router. I know it's not necessary but it makes it easier to go through the captures.
Setup the wireless on your phone to connect to your wireless router and turn off your mobile data connection.
After you have turned off the wireless security on your router, we are going to start the wireshark capture.
Run wireshark - if you are on vista or windows 7 make sure to run it as an administrator
Click "Capture" then "Interfaces"
Click "options" next to the interface that your computer has an IP for
Make sure to check "Capture packets in promiscuous mode"
In the Capture Filter box, type "host <ip_address>" where <ip_address> is the ip address your router gave your phone
Make sure that "Automatic scrolling in live capture" is checked so you can ensure the capture is working
Click "Start"
At this point, you should browse the web with your phone. You should see lots of stuff scrolling by in the wireshark window.
If there isn't, you messed up something above and should try again.
If there is a lot of stuff scrolling by, continue:
Close the browser
In wireshark, click "Capture" then "Restart"
Reboot your phone
On your phone, go to "Settings" -> "About Phone" -> "Check for Updates" and go through with the OTA update
After the update is done and your phone is rebooted, go to wireshark and click "Capture" -> "Stop"
Then click "File" -> "Save As" and give it a name.
Upload that file to Megaupload, or Mediafire, or some other file sharing site, or any private server that I can get access to.
After you have uploaded the file please message me through the forums with a link to the file.
Thanks a ton.

e-mail me at [email protected] i got my wifes phones todo this to shes still on 1.5

NO need to have a average user do this, guinea pig yourself and roll back down to 1.5 it can and has been done by other devs.

Isn't there a "logcat" line you can run through adb to get the same thing? Like, when the update is available, you can plug your phone into your computer, connect it to terminal using adb and run a logcat to find the address of the update.zip

FireSokar said:
NO need to have a average user do this, guinea pig yourself and roll back down to 1.5 it can and has been done by other devs.
Click to expand...
Click to collapse
You CANNOT downgrade from 2.1 to 1.5.

Videofolife13 said:
Isn't there a "logcat" line you can run through adb to get the same thing? Like, when the update is available, you can plug your phone into your computer, connect it to terminal using adb and run a logcat to find the address of the update.zip
Click to expand...
Click to collapse
We don't need the location of the update file, we need all the extra network traffic that surrounds the OTA process.

Ah. My bad.

We need to know, exactly, how the update process works.
I'm currently working on downgrading 2.1. Will post back a tut if i get it working

Can't we create an AVD to run with a custom rom and use the Eris MR1 ROM to do it?

Scratch that. I don't think AVDs will get OTAs.

zifnab06 said:
Scratch that. I don't think AVDs will get OTAs.
Click to expand...
Click to collapse
Sadly I tried this a while ago when messing around with AVD Skins but wasn't able to figure it out. If anyone can figure it out please let me know how you do it! -_-"

zifnab06 said:
Scratch that. I don't think AVDs will get OTAs.
Click to expand...
Click to collapse
Wait can't you set it to wireless only mode and get the OTA through wireless? (Simulated by your network connection)

nindoja said:
This is a call to arms for anyone still running 1.5 on their eris. We (developers) need people to capture the update process using wireshark (or an equivalent). This is needed for a new root attempt, but sadly all of the devs have already updated to 2.1 so we can't do this.
...
Thanks a ton.
Click to expand...
Click to collapse
No need to go to all that trouble. I've already posted a link to the OTA update (1.16.605.1 -> 1.17.605.1) in this XDA thread a couple of days ago. Just copy n' paste into your browser's URL bar. I'll repeat it here for grins.
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
(You might get a browser security warning as that server uses the wrong (google.com) cert.)
Let me know if the above link no longer works - I suppose I could repeat the OTA thing - I am not on 2.1
The OTA process drops the downloaded zip file into /cache, and somehow during reboot, it's presence is detected. If it "only" needs to be dropped in there, or there are some other hooks that need to be present at the reboot, I am not sure. I say "only" because that implies that root privilege is needed to do that - or perhaps it is possible to use "fastboot update" after rebooting the phone with $ adb '(sync; reboot -n oem-78)' The OTA zip file is not signed the way the RUU "rom.zip" files are; it uses the same signing methods as app (.apk) files - the SDK "jarsigner" method.
You can unpack the zip file and look at what it does - there is a script at
META-INF/com/google/android/update-script
which controls the update... and there is a binary patch executable included in zip which is called upon to do file-by-file binary patching.
cheers
bftb0

Thanks for the info bftb0, but we aren't looking to snag the OTA file. We are actually trying to see what communication goes on between our phones and the verizon update servers.

FYI,
When you roll back to MR1, the phone seems to have already grabbed and downloaded the OTA update... in less time than it takes to hand-configure the phone. If you want to observe the OTA process via wireless, you need to prevent the phone from having Mobile network access, since that comes up by default after a FR or MRx rom burn.
Here's a long shot. Perform the MR1 rollback inside a cell dead zone, and conduct a MIM attack by setting up a server on the wireless net so the phone downloads a different OTA zip. You control DHCP for WiFi, so you also in principle control the DNS and routing the phone sees via WiFi. In principle, it's not possible because https should prevent Man-In-the-Middle... but if that (Google) server isn't correctly configured, maybe the phone is not really being too careful about certificate problems. (Either that or the Google server is tuning its' responses based on UA strings).
bftb0

bftb0 said:
No need to go to all that trouble. I've already posted a link to the OTA update (1.16.605.1 -> 1.17.605.1) in this XDA thread a couple of days ago. Just copy n' paste into your browser's URL bar. I'll repeat it here for grins.
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
(You might get a browser security warning as that server uses the wrong (google.com) cert.)
Let me know if the above link no longer works - I suppose I could repeat the OTA thing - I am not on 2.1
The OTA process drops the downloaded zip file into /cache, and somehow during reboot, it's presence is detected. If it "only" needs to be dropped in there, or there are some other hooks that need to be present at the reboot, I am not sure. I say "only" because that implies that root privilege is needed to do that - or perhaps it is possible to use "fastboot update" after rebooting the phone with $ adb '(sync; reboot -n oem-78)' The OTA zip file is not signed the way the RUU "rom.zip" files are; it uses the same signing methods as app (.apk) files - the SDK "jarsigner" method.
You can unpack the zip file and look at what it does - there is a script at
META-INF/com/google/android/update-script
which controls the update... and there is a binary patch executable included in zip which is called upon to do file-by-file binary patching.
cheers
bftb0
Click to expand...
Click to collapse
bftb06: could you please PM me? I am going to trade my phone this week if you understand what I am getting at.

nindoja said:
Thanks for the info bftb0, but we aren't looking to snag the OTA file. We are actually trying to see what communication goes on between our phones and the verizon update servers.
Click to expand...
Click to collapse
Sorry, my bad. I didn't read carefully enough.
I could probably attempt what you are asking for - I am quite familiar with wireshark (and even hardware sniffing of WiFi, so long as you have the right nic), but the fact that the phone seems to go and look for updates immediately after a FR or MRx update means that the "check for updates" thing may not do anything useful for you if there is already an update on the phone waiting to be installed by the time you start pressing menu buttons. (Thus the idea about "do MR1 in a cell dead zone")
Beyond that, there is a possibility that the update app does not do a wildcard host bind() when it sets up the socket when it inquires about updates with the Verizon servers - for instance, MMS service works exactly that way (it will only use the mobile network interface), and precisely so because of security considerations. Do you know whether or not any of the update conversation actually traverses WiFi if the mobile network is turned off?
bftb0

bftb0 said:
Do you know whether or not any of the update conversation actually traverses WiFi if the mobile network is turned off?
bftb0
Click to expand...
Click to collapse
You can force updates to occur over WiFi if the mobile network is turned off. Do you think this would work:
1. on 1.17 do a factory reset but do not activate the phone.
2. Initiate the downgrade process
2a. while downgrading, turn on packet capture
3. When the phone boots back up and wants you to call a number to activate, hang up
I think if you can skip the activation the phone will not have a mobile data connection, which would allow you to turn on wifi and initiate the update process.

Im still on 1.5 PM me and ill help if needed

Do you guys still need this?

[GUIDE] Galaxy Tab Network Unlock

**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.

How to: Wireless (&USB) Tethering on LG Quantum

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?

[GUIDE] How To Unlock Tethering on Nexus 5X.

I'll start off by saying I didn't come up with any of this method myself, its just different information I found scattered on different threads on XDA and Reddit. Maybe some other 5X users will find it useful contained in this thread.
Secondly, this requires an unlocked bootloader, also working adb and fastboot with correct drivers for your 5X, enable USB debugging. I won't go over that here, there are plenty of other guides on how to do that, and know that it will erase all your data. As long as you can find your device via "adb devices" and "fastboot devices" you should be fine.
Lastly, you will get the corrupt data message on phone startup. I don't see any negative effects with this, other than an annoying message. Also I'm still able to use the fingerprint scanner as well as set up Andoid Pay. I can't verify Android Pay as I don't have any stores near me that accept it.
You also won't have to flash any custom recovery or root the device, which keeps it closer to stock, which hopefully will allow Android Pay to still function, hopefully someone with a Android Pay store nearby can test this to verify.
First grab TWRP for 5X from here. Save it in the same folder as your adb/fastboot install.
Make sure your phone is connected to your computer, open command prompt and verify adb sees your phone.
Code:
adb devices
Now reboot to bootloader.
Code:
adb reboot bootloader
Now we boot from TWRP without having to flash/install it.
Code:
fastboot boot twrp-2.8.7.0-bullhead.img
When TWRP finishes booting, click Mount and check the box for /system
Now we need to pull the build.prop file.
Code:
adb pull /system/build.prop
Using a text editor add this line to the end of the build.prop file and save it.
Code:
net.tethering.noprovisioning=true
Now we push it back to the phone.
Code:
adb push build.prop /system/
Make sure the permissions are correct.
Code:
adb shell chmod 644 /system/build.prop
And lastly
Code:
adb shell settings put global tether_dun_required 0
Now we just reboot
Code:
adb reboot
and your tethering should be working!
I'm currently using this method and it is working for me. I'm on Verizon with a Grandfathered Unlimited Plan, so I can't test it for any other carriers.
Most of this information I pulled from this reddit thread, I just did my best to condense it down and simplify it, and make it aimed toward the Nexus 5X specifically.
edit* People are confirming on the Reddit thread on their Nexus 6 that Android Pay is still working after making these changes!

Thanks! This works exactly as stated, even the "corrupt data" warning on boot.
I will add that - this being my first Nexus device since a Galaxy Nexus - the "fastboot oem unlock" step needed prior to this guide has an additional step where you have to enable the "OEM Unlock" option in the Developer Options menu, within the booted system. After confirming this you can unlock the bootloader via the standard "fastboot oem unlock" command prior to starting this guide.

Thanks for this, used same method to push supersu and get it installed without needing to decrypt the phone!

Thanks. Worked great for me. I'm on AT&T, weird thing though, I never had any problem activating the hotspot on my OG Nexus 5.

AWESOME!

added to index
[INDEX] LG NEXUS 5X Resources Compilation Roll-Up

Guys can you please explain what do you mean as "unlock tethering"? Is not enabled by default?

olivercervera said:
Guys can you please explain what do you mean as "unlock tethering"? Is not enabled by default?
Click to expand...
Click to collapse
This method bypasses the subscription check for tethering, those of us with unlimited data have to pay a separate fee to use tethering with Verizon, and this fixes that. It should be the same for other carriers as well.
Sent from my XT1060 using XDA Free mobile app

I was so excited to play with my 5x when I got home (that and dealing with my 2 sick kids) and I completely forgot to unlock the bootloader before I got too carried away. Now all the time I spent downloading apps and such is lost. Our DSL connection is slow, so all that took one time. I've been rooting and romming way too long to make such a rookie mistake.
So, I get the joy of blowing the whole thing way and re-setting it up again...

XF1ber said:
Thanks for this, used same method to push supersu and get it installed without needing to decrypt the phone!
Click to expand...
Click to collapse
Could you confirm the steps?
Can you confirm you can still use supersu? I thought the kernel had to allow su.
Also, I guess you can also install the bootunlock app and see if that works?

Thank you thank you thank you!
This is huge for me.
BTW, I assume you can just push the original unmodded build.prop back for OTA updates. Anyone know if anything else is required apart from that?

Confused on why we need TWRP just to do this.

You're not flashing twrp, just booting into it. Twrp allows you to pull and push files to /system without root, which is needed to make these changes.
Sent from my Nexus 5X using XDA Free mobile app

Can someone confirm Android Pay actually works?
Sent from my Nexus 5X using Tapatalk

T-Mobile/MetroPCS users additional steps to enable tethering
If you are on T-Mobile or MetroPCS you will need to perform some additional steps for tethering to work. After you have performed the steps outlined earlier in this thread do the following:
Under Settings -> More -> Cellular Networks -> Access Point Names
Touch the name of the APN that is selected (there may only be one) then:
1) change "APN Protocol" to "IPv4"
2) change "APN roaming protocol" to IPv4
3) Edit "APN Type" and add "dun" to the comma separated list so it reads something like "default,supl,mms,dun"
4) OPEN THE MENU IN THE UPPER-RIGHT AND CHOOSE SAVE!
5) You MAY have to reboot for this to take effect

Ok needing it for that reason makes sense now.

So... I'm getting about 30% packet loss on att with my 5x.
If I take my sim out and pop it into my nexus 6(also with marshmallow), everything is fine.
Could someone with att run some extended pings from a device connected to your phones tether and note any ping drops?
I don't know if this is a sw bug, or hardware issue.

Does this work if the device is still encrypted?
My TWRP seems to have trouble accessing /system partition with encryption.
Sent from my Nexus 5X

Ascertion said:
Does this work if the device is still encrypted?
My TWRP seems to have trouble accessing /system partition with encryption.
Sent from my Nexus 5X
Click to expand...
Click to collapse
yep works fine. You have the correct twrp i presume and your phone's bootloader is unlocked?

MarkGbe said:
yep works fine. You have the correct twrp i presume and your phone's bootloader is unlocked?
Click to expand...
Click to collapse
Ah my bad. It's not reading my /sdcard partition. No matter. That's what adb is for. Please disregard my post. I'll update my progress when I get home later today and try it on my personal PC.

Trying to root a Moto g4 from Amazon

Hello, everyone. Thanks in advance for any help provided.
Recently, I purchased this phone from Amazon, and I like it a great deal, except for one thing -- the wireless hotspot does not turn on. When I try to activate it, I get the following message, after it checks subscription status:
"Account not set up for tethering
To enable, go to att.com/mywireless or dial 611"
Here is the issue though -- I have the service through Tracfone's BYOP program, and they do not support the feature, even though they do not mind you using it if it happens to work. So, they will not enable it. Further, AT&T cannot help, as the service is through Tracfone and they do not have access to their customer's account information.
I have looked around this excellent forum, and I have found that this issue can be fixed by using ADB shell to enter this command:
settings put global tether_dun_required 0
as well as adding this line to the build.prop file in the /system folder:
net.tethering.noprovisioning=true
I was excited by this, and attempted to do it through ES File Explorer using root explorer -- and then told the option doesn't work on this device. The reason, of course, was because the phone is not rooted, so I figure, if I can root my phone, then I can edit the file, reboot the phone, and enable the hotspot. So, I continued researching.
I learned in the last day or two I learned that you cannot unlock the bootloader on this phone, something to do with Amazon's agreement with Motorola as a way to keep people from removing the advertisements. So, I cannot go that route.
I downloaded KingRoot (version 4.9.6) and attempted to root with it... and it failed, multiple times.
So, I was hoping someone might have a suggestion of what step or steps to take next. Any help would be greatly appreciated.

Hotspot works
On my 32gig Amazon G4 the hotspot works without rooting and no additional software. I've got FoxFi loaded, but it has never been used on this phone, and was not running.

Rincrast said:
Hello, everyone. Thanks in advance for any help provided.
Recently, I purchased this phone from Amazon, and I like it a great deal, except for one thing -- the wireless hotspot does not turn on. When I try to activate it, I get the following message, after it checks subscription status:
"Account not set up for tethering
To enable, go to att.com/mywireless or dial 611"
Here is the issue though -- I have the service through Tracfone's BYOP program, and they do not support the feature, even though they do not mind you using it if it happens to work. So, they will not enable it. Further, AT&T cannot help, as the service is through Tracfone and they do not have access to their customer's account information.
I have looked around this excellent forum, and I have found that this issue can be fixed by using ADB shell to enter this command:
settings put global tether_dun_required 0
as well as adding this line to the build.prop file in the /system folder:
net.tethering.noprovisioning=true
I was excited by this, and attempted to do it through ES File Explorer using root explorer -- and then told the option doesn't work on this device. The reason, of course, was because the phone is not rooted, so I figure, if I can root my phone, then I can edit the file, reboot the phone, and enable the hotspot. So, I continued researching.
I learned in the last day or two I learned that you cannot unlock the bootloader on this phone, something to do with Amazon's agreement with Motorola as a way to keep people from removing the advertisements. So, I cannot go that route.
I downloaded KingRoot (version 4.9.6) and attempted to root with it... and it failed, multiple times.
So, I was hoping someone might have a suggestion of what step or steps to take next. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I would avoid Kingroot as that won't get you rooted. Tethering is iffy at best depending on your carrier. Some will suspend your service if they catch you tethering which they can easily do. Tracfone used to be pretty quick about suspending service for anyone tethering so good luck on getting it to work.

You can use adb mode if you turn on USB debugging in developer settings. Settings > about phone > tap build number a lot of times to enable it.
Then it'll be in settings. And you can use system-wide adb for Windows to make it easier to use ADB.
Or, you can try an app called EasyTether to tether.

ADB and EasyTether
AidenSurvival said:
You can use adb mode if you turn on USB debugging in developer settings. Settings > about phone > tap build number a lot of times to enable it.
Then it'll be in settings. And you can use system-wide adb for Windows to make it easier to use ADB.
Or, you can try an app called EasyTether to tether.
Click to expand...
Click to collapse
I know the ADB commands to try; I listed one of them in the OP. However, it didn't help in my situation.
EasyTether doesn't have a wireless network tether option, and I have tried other apps too -- such as Pda+ -- that will not enable the wireless tether.
What I need is a way to edit the build.prop file, but it appears that I cannot do it without rooting.
Someone mentioned there might be an issue with Tracfone not permitting it. I conferred with Tracfone, and, though they do not support the feature, they do not mind if you can get it to work.

Flashxxposed framework and iinstall x tether

hooks024 said:
Flashxxposed framework and iinstall x tether
Click to expand...
Click to collapse
That requires rooting and OP said he couldn't root.