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?

anyone who has rooted from the bay area want a shot at mine

Like my title says. Id like to meet you somewhere local in south bay preferable to have you root my inc. I would like the madness to end knowing its my drivers and or sd cards and help me get back to normal life... i got it..... did the pull the card and pray method one time at the white to black screen transition .

why rushing to root ur dinc. i rooted and seem like nothing special. currently, i only can use LED flash, setcpu, titanium backup, superusers, wireless tether, adfree, and shootme. removed city id. thats all.

lol thats all huh? thats quite a bit considering lol

+ 1 San Diego area....PLEASE HELP!!!...LOL

here are the steps i used and sdcard
Nokia 1GB class2
i installed htc sync/driver i found inside of the HTC Incredible internal storage.
complete guide: http://androidforums.com/all-things-root-incredible/98180-prs-complete-rooting-guide.html
Unplug the USB
Press and hold the optical Trackball and press power
Once in the menu press power again
Wait 20 seconds for it to do its bit
Plug USB in and wait another 10 seconds for your computer to detect the phone
press menu down to highlight "recovery"
set up the cmd for adb shell loop
Press power on the phone + hit enter on cmd at the same time.
the screen should change from "error: device not found" to "exec '/system/bin/sh' failed: No such file or directory (2) -"
ps: it worked for me.

zeke1988 said:
why rushing to root ur dinc. i rooted and seem like nothing special. currently, i only can use LED flash, setcpu, titanium backup, superusers, wireless tether, adfree, and shootme. removed city id. thats all.
Click to expand...
Click to collapse
Ha! You can install adfree but you can't run it effectively. Adfree needs to write hosts file to /ect folder which still protected (see here)

kbnguy said:
Ha! You can install adfree but you can't run it effectively. Adfree needs to write hosts file to /ect folder which still protected (see here)
Click to expand...
Click to collapse
You can write the hosts in recovery after a re-root. That's the only way right now.

E30kid said:
You can write the hosts in recovery after a re-root. That's the only way right now.
Click to expand...
Click to collapse
Re-rooted, at command prompt: adb remount
"Operation not permitted". Nope, not happened here...

HOW TO: Enable Wireless N on The Aria

EDIT:alot of people are unable to do this method because of errors writing to the system. it seems to restore the original bcm4329.ko upon reboot, so this patch has been cooked into the Roms. And wireless N is confirmed to work.
Just flash one of the below roms
Go Here For attn1's Liberated Beta 4 Rom with The Wireless N Patch Cooked in. http://forum.xda-developers.com/showthread.php?t=708434
heres his Beta 3 with wireless N cooked in - http://www.mediafire.com/?wenzltywoom
So i realized that the htc nexus one, htc desire, and htc evo all have the Bcm4329 wireless chip. And they all have wireless N enabled with hacks. Well I know from porting roms for the Aria that the aria also has a BCM4329 wireless chip. So i said to myself, why havent i enabled wireless N on my Aria.
well none of the methods worked except the manual method which isnt too difficult if you have some adb knowledge.just follow the exact steps and youll have no problem.
Prerequisites
-Must Be Rooted
-Must have clockwork recovery installed
-Must have the android sdk installed
ENABLING WIRELESS N
step 1- Download a hex editor
step 2-in a command prompt navigate to the /android-sdk/tools folder and type the following
adb pull /system/lib/modules/bcm4329.ko ./bcm4329.ko.old
adb pull /system/lib/modules/bcm4329.ko ./bcm4329.ko
(this makes a backup of the original in case you want to go back to wireless G)
Step 3- in the hex editor open up the file you pulled(bcm4329.ko). Now the same as the htc Evo 4g, Htc added 2 strings that say "nmode" without the quotes. Use the search function to find the 2 strings. now you need to replace nmode with any different string. i used "-----" without the quotes for both.
when you're done save the file.
Step 5-now reboot into clockwork recovery and go the partitions menu. go down to mount /system and press the power button.
Step 6-now type this in the command shell.
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
reboot your phone when its done and you now have wireless N enabled.

since the Aria has the same chip as the nexus,, then why wifitether does not work..?

Will try this on my Aria when I get home. Thank you in advance! Now, back to the wifi tethering debacle
Sent from my SAMSUNG-SGH-I897 using XDA App

We Aren't Sure why wireless tethering isn't working yet. But we're pretty sure its gotta be something disabled at the kernel level. It will only be a matter of time before we figure it out.

Is it confirmed that Wireless N is enabled after doing said method?
*edit*
Just tried it, and it's not picking up my Wireless N network, nor does my Wireless router show it connected to a Wireless N. Only Wireless G.
I also did a adb pull of the file I pushed back just to confirm the changes were made, and they are, but for some reason it's not working.

there are some others who are having problems getting this to work as well.
im gonna test it on a rom real quick.
try this-> forgetting the network then reconnecting and re entering the password. not sure if that will fix it but that is what i did when i first connected so maybe that had something to do with it.

I'll give that a try in a few min, and report back.
*edit*
Tried that, the scanning doesn't even pick up the Wireless N network, it only see's the 'G' network. (I have a dual band G & N router)

Well after reading the EVO thread regarding this method, it shows that people who did it are connected at over 54mbps, which is the max for G speeds.
I'm currently connected at 69mbps, so maybe I am on my N?

try to change your wireless N router to N-only and see if it connects and remains connected.

Seems I have no luck, router is in N only mode, but the wifi on the Aria is just 'scanning'.
It's a great idea, just wish it would work.

i dont know why anyone else is unable to get it working, but im patching a rom with this and gonna have someone test it and then ill know. there just seems to be problems with the writing files to the system.

I was starting to think it was a permissions issue, but I'm at a loss as to this one. It might need to be done from a update.zip file in ClockworkMod.

yeah, maybe.
Since there were problems writing files to /system i tried pre-patching a rom and it works. So we're going to just patch the liberated Rom and upload it. check the liberated Rom thread in a little while if you cant get this to work.

Flash to Metro PCS instructions

I haven't seen a post or tutorial about this yet so I figured I'd post one for those who might be interested.....BTW,
I AM NOT A PROGRAMMER AND I TAKE NO CREDIT FOR ANY OF THE INFO IN THIS POST, NOR WILL I POST ANY CREDIT.....I pieced so much of it together from so many different posts, that I just don't even remember the OP's. Sorry I'm no genius, just a jackass who stands on the backs of geniuses.
Disclaimer: This is just how I got everything to work on Metro PCS, it may or may not work in the same way for you. I don't warrant or claim that anything discussed here will not brick your phone, bankrupt your business, or impregnate your cat.
Things you will need:
1. Samsung Fascinate (Already Rooted)- Please don't ask; as there are so many already posted and accepted rooting methods for this phone. Seek and Ye shall find my son
2. QPST 2.7 (I used Build 355)- Again, please don't ask as this is considered warez and a taboo discussion on most forums.
3. CDMA Workshop (I used 2.7)- Uh....Ditto my previous remark...DON'T ASK!
4. Metro PCS Files and Support .apk's
a. u2nl
b. autostart.sh
c. autostart.apk
d. anycut.apk - I can't post these files or links to them, but I would appreciate anyone who would like to post or host them for me...just PM and I'll send you the zip if you need it.
5. Android SDK (I will assume that you have this if you have rooted your device) -Please no lectures about assumptions.
6. Samsung Drivers - I can assume you have this as well if you rooted your device. Again, anyone care to post or host...just PM me.
The Task at Hand:
1. Insert and Permission Files:- Let the fun begin
a. Copy all the Metro PCS and Support files listed above to your Android SDK tools folder...in my case this was c:\android\tools
b. Connect your phone with USB debugging turned on (Settings > Applications > Development > USB Debugging)
c. Now open a Command Prompt and change to your Android SDK tools folder.
d. From the c:\android\tools> prompt run the following commands:
adb remount
adb push u2nl /system/bin/u2nl
adb push autostart.sh /data/opt/autostart.sh
adb shell
chmod 755 /system/bin/u2nl
chmod 755 /data/opt/autostart.sh
exit
adb install autostart.apk
adb install anycut.apk
adb reboot
This will work if you have system-wide root....if you receive a "permission denied" error after the first command you have local root and will need to run the following comands:
THIS IS ONLY IF THE LAST SET OF COMMANDS DID NOT WORK....from the command prompt c:\android\tools>
adb push u2nl /sdcard/u2nl
adb push autostart.sh /sdcard/autostart.sh
adb shell
su (prepare to allow the permissions on your phone at this time....LOOK AT YOUR PHONE NOW!!!)
mount -t rfs -o remount,rw /dev/block/stl9 /system
mkdir /data/opt
busybox cp /sdcard/u2nl /system/bin/u2nl
busybox cp /sdcard/autostart.sh /data/opt/autostart.sh
chmod 755 /system/bin/u2nl
chmod 755 /data/opt/autostart.sh
mount -t rfs -o remount,ro /dev/block/stl9 /system
exit
exit
(back at the command prompt)
adb install autostart.apk
adb install anycut.apk
adb reboot
2. Provisioning Your Phone:
a. Connect your phone and put it in "diagnostic mode" (Settings > Wireless & networks > Dial up networking)
b. This should present you with a new port in QPST....take note of the port.
c. Now go to whiterabbit's site and enter your login string, then click on generate. (remember to generate the file appropriate for your version of CDMA Workshop) -P.S while you're there at whiterabbit- type your ESN into the lower box and generate your Metro PCS MSL...you will need it later.
d. Now open CDMA Workshop and choose the port you took note of earlier...click connect. Open the security tab and enter the SPC in the box (000000 <SPC) and click SPC then send....then in the bottom left corner click on the custom password box and replace "FFFFFFFFFFFFFFFF" with "2010031619780721" and send....now click on the memory tab and then click on the "write" button under NV items...navigate to where you saved the file you generated at whiterabbit's website and write...now exit CDMAW and click yes at the exit message....your phone will reset.
e. Unplug your phone and plug it back in when it has finished rebooting...it will still be in diagnostic mode...so go ahead and open QPST Configuration...click on start clients and service programming...this brings up a new window...click ok...then click on "read from Phone" in the next new window...enter your MDN and MIN under the CDMA tab them go to the M.I.P. tab....make sure to change from MOB only to MOB w/Simple back....then delete all entries in the top window except the first one...then highlight and edit that entry...make sure the top 2 entries under the new window are correct...then change all the IP's to 0.0.0.0...click OK and now go to the PPPConfig tab click on UM and enter your MSL from whiterabbit's site...do the same to AN....thats it click write to phone and let the phone reboot.
3. Now the Easy Part:
a. Once the phone reboots..you have to turn off "dial up networking" to get your 1x and arrows.....now you have full data
b. Now MMS.....open anycut on the phone...tap the new shortcut button....choose new activity then scroll down to MMS Provisioning and tap it. Your new short cut will be on your home screen...tap it and enter the MMS server for metropcs... exit and your done.
It is 3:04 am and that's as good as it gets for me..I wrote this from memory and I am sure it's not the best tutorial or the most svelt, and I may have left some things out or maybe I was a little vague....do not berate, just feel free to rewrite, edit, append, addendum, or be as helpful as you can in your replies. Leave your egos at the door and treat this like you would a wiki. Any suggestions are greatly appreciated. Any constructive criticism is welcomed. Have fun.

thanks for the guide! just a quick addition. I think you need to press ##8778# to get into the diag menu so that qpst 2.7 recognizes your phone on your port.
update: got the messaging to work and the data arrows. but the internet just won't push through. also, when I opened Any Cut and went to new activity, "MMS Provisioning" wasn't a option. Is there a specific version i should be looking for ?

Where do I get the metro pcs files? I've looked high and low for them but can't seem to find them.

you can get the u2nl and autostart.sh from white rabbit's website where it saids "precompiled arm binary"
the other two you can just turn wifi on and dl it from the market. hope that helps! if not, just PM me and i'll send em to you.

I've got step 1 completed but I'm having trouble with step 2...
Phone doesn't show up in QPST.
When it says to go to whiterabbit and enter the login string, I'm not sure what to enter. I don't have a MPCS phone number yet if that's what it's looking for...

did you dial ##8778# to get get into the diag menu and set them both to modem? that and putting the phone in dial up networking mode should get qpst to recognize your phone.
for whiterabbit, you need to enter your MPCS [email protected], so i suppose you do need one lol

breakinyoankelz said:
did you dial ##8778# to get get into the diag menu and set them both to modem? that and putting the phone in dial up networking mode should get qpst to recognize your phone.
for whiterabbit, you need to enter your MPCS [email protected], so i suppose you do need one lol
Click to expand...
Click to collapse
##8778# doesn't work for me, it just doesn't do anything. I've tried a bunch of other codes but just not working to get into that diag mode.
Ok, the problem was that I had to go to my device manager and tell it to make the phone a different COM port - 3. Then restart QPST and tell it to monitor port 3. That works...

Stumped again...
Ok, we only got this phone to test out the metro pcs service. So we don't have a metropcs account as yet.
When we called the local store, they said they wouldn't add the ESN for us for ANY smartphone.
How did you guys do it? Buy a regular phone first and get it activated, then flash the Fascinate and somehow add the ESN to their database?

Very Nice Guide.
can you please PM me (Metro PCS Files and Support .apk's)

pkley said:
Stumped again...
Ok, we only got this phone to test out the metro pcs service. So we don't have a metropcs account as yet.
When we called the local store, they said they wouldn't add the ESN for us for ANY smartphone.
How did you guys do it? Buy a regular phone first and get it activated, then flash the Fascinate and somehow add the ESN to their database?
Click to expand...
Click to collapse
I used on of these sponsored independent agents on howardforums to add your ESN to the database. I would link you to it right now, but I'm not able to as a new member of this forum. Just search "ESN added to metroPCS" on howardforums or PM me

arvinghost said:
Very Nice Guide.
can you please PM me (Metro PCS Files and Support .apk's)
Click to expand...
Click to collapse
Just PM'd you the u2nl and autostart.sh files. btw, are you the same arvinghost as from howardforums? Did you ever get data to push through because I'm stuck as the 1x arrows showing, but no data too

flash to metro pcs
Damn man I guess nobody check their messages anymore, but anys ways I got everthing done still no internet, so whats the deal
WHO BESIDES THE OP HAS ACTUALLY HAD ANY SUCCESS?

yeah i am also trying to flash a cdma hero and i dont know how to use sdk, not too familiar, but im up for it. any video tutorials any1? this sucks dude, i really wanna learn how to do this i have a phone and i cant even use it.

Did you use a custom ROM or just the standard ROM?

I've tried a few different variations of this method and it doesn't work. At least not with the standard ROM. Also the PPP username and password kept resetting itself back to verizon after reboot so I'm guessing we're gonna need a modified NV-Items file to fix that; the one from whiterabbit doesn't work on this phone.

**87284 on Verizon Galaxy S
##8778# on Sprint Galaxy S (Epic)

I had success flashing to metro with everything working. for the ppp settings to stick make sure you use qspt 2.7 build 215 and the m.ip settings with build 355.

euklid said:
I had success flashing to metro with everything working. for the ppp settings to stick make sure you use qspt 2.7 build 215 and the m.ip settings with build 355.
Click to expand...
Click to collapse
how did u get mms on it?? because i cant get it on my fascinate everything works except mms

I uploaded apn file for metropcs with apn restore app.
Sent from my SCH-I500 using Tapatalk

euklid said:
I uploaded apn file for metropcs with apn restore app.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
You have that xml file? Or a link to it? I'd like to try with new ports, I didn't even have to install AUTOSTART for web to work...wonder if mms works with just the apn.xml....

[HOW TO] Root/update/ your Australian Xoom

WANT TO ROOT YOUR AUSSIE NEXT G XOOM?
Firstly, I know this is in the wrong section of the forum, but I dont have enough XDA posts to put anything in the developement section. DEAL WITH IT
DISCLAIMER - I am not a developer or active XDA forum poster, I am a forum reader and user. The reason for this post is a lack of information regarding AUSTRALIAN Xoom rooting and updating on XDA (correct me if im wrong). This information is gathered from multiple different sources and I DONT TAKE ANY CREDIT FOR THEIR HARD WORK, nor do I take any responsibility for their instructions. Everything here is their work, however please follow the links for a more up to date process. Therefore take this information with a grain of salt, I have, however, seen it work on 4 Xoom's so far with 100% success. These instructions assume you can use adb, fastboot, and clockworkmod and assume you know that all warranty is voided by doing any of this.
Now, for the nice bit...
Do you have an Australian Xoom with 3G and wondering what to do about Verizon, US, EURO, UK, 3G, 4G, WIFI only, etc?? you want a forum that says OZ dont you? you want to ROOT YOUR XOOM!
Firstly from what I can tell our model is very similar if not identical to the UK model in that they provide 3G (Telstra Next G for us) connection. The US models dont have sim cards and access the network differently, so some of their processes and information will not apply to us, neither will all the UK information. So to save you some time, here is a collaboration of my findings after hours of web searching and flashing, re-flashing, etc.
Step 1 - Root it
[GUIDE] XOOM 3G Euro Root Instructions + Files.
http://forum.xda-developers.com/showthread.php?t=1049901
This link and all associated files work perfectly to root your OZ-Spec Xoom
Step 2 - ClockworkMod Recovery
[Recovery] ClockworkMod 3.0.2.8 Modded for Internal media [UPDATED 5/13]
http://forum.xda-developers.com/showthread.php?t=1074979
Again, this works perfectly, and gives you SD access and a really easy way to flash your OZ-Spec Xoom
Step 3 - Honeycomb 3.1 Update
Step 3
Firstly need to backup some important telstra related files
adb remount
adb pull /system/build.prop build.backup
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
adb pull /data/data/com.android.providers.settings/databases/settings.db-wal settings.db-wal
adb pull /data/data/com.android.providers.settings/databases/settings.db-shm settings.db-shm
adb pull /data/data/com.android.providers.telephony/databases/telephony.db telephony.db
adb pull /data/data/com.android.providers.telephony/databases/telephony.db-journal telephony.db-journal
[UPDATE][HC3.1] Wifi and 3G! Completely Flashable! No Fastboot Needed!
http://forum.xda-developers.com/showthread.php?t=1074609
Follow the link to update your device. After updating, extract the attached zip to your adb.exe folder and run command prompt.
adb remount
adb pull /system/build.prop build.backup ##cant be too safe##
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
adb push settings.db-wal /data/data/com.android.providers.settings/databases/settings.db-wal
adb push settings.db-shm /data/data/com.android.providers.settings/databases/settings.db-shm
adb push telephony.db /data/data/com.android.providers.telephony/databases/telephony.db
adb push telephony.db-journal /data/data/com.android.providers.telephony/databases/telephony.db-journal
adb push build.modified /system/build.prop
This will get you 3.1 and still working on the Telstra network and thinking its australian again.
Step 4 - Tiamat Kernel
[KERNEL][AOSP][HC3.1] Tiamat Riptide Special Edition 1.4.2 [Update: 5/21]
http://forum.xda-developers.com/showthread.php?t=978013
This is where those kickass quadrant scores come from. Follow instructions per usual for OZ-Spec. Dont forget to flash the new bootloader first.
tada!... a rooted Aussie Xoom running HC3.1 AND Tiamat kernel AND ClockworkMod AND 3G
Thankyou to the originators of the instructions found here.

Followed these same steps yesterday and can vouch that they work great.
Cheers
(Also long time reader, first time poster)

Hi Guys, up to stage 3.1 and not sure what files/info I need to extract?
Cheers

I think that step was supposed to point to http://forum.xda-developers.com/showthread.php?t=1089695 (which is actually the most important page to read)

adamtuba said:
I think that step was supposed to point to http://forum.xda-developers.com/showthread.php?t=1089695 (which is actually the most important page to read)
Click to expand...
Click to collapse
Thanks - had found the info via google search and all working now.

Telstra 3g files
Thanksh for this post it is of grea help. It has allow me to bring my xoom bck from "brick land". The only bit I cant follow is how to get the telstra 3g specific files you mention. n Step 3.1 I cant find anything about extractingfiles

3g files
Does anyone have these Telstra specific files?

which bootloader did you use for the Tiamat kernel?
cheers
Sent from my Xoom using XDA App

Help need ..... I am wondering if anyone out there are able to send me the files to enable 3g on Telstra as described in this post.
My situation is a follows. I have an Australian Telstra xoom and tried one of the 1 click root programs. After much pain and research I now realise 2 things. 1/ this completely stuffed by device, it now hangs at the logo on boot. 2/ even if it did work it is for US networks only. I have worked my way through the posts and have managed to recover the device by fastbooting with the euro boot.img described in this post. Problem is no 3g. This post provides a description of how to extract the Telstra 3g files for the device before it gets trashed. I did not do this. So I am assuming I now need to source these files from someone who has a working Telstra xoom.
Can anyone out these assist......

These are the files I pushed to my Xoom to get it working. Hopefully it helps.
Cheers

thank you very much I will let you know how I go ...

Yahoooooooooo... these files worked a treat, I am now back on 3g. One of the files settings.db-wal has a size of 0 bytes is that right or should it have something in it.
The only problem I have now is wifii is not working... when I look at wifi in settings it says "error" ... any ideas

Glad that helped.
That file was 0 bytes on mine as well. Don't know why the wireless has failed but someone may be able to help otherwise you may need to push the wireless driver/config file back to the tablet. I think the wireless driver was in one of the links at the start of this thread.
Cheers

can anybody link me to these files "telephony.db" (adb push telephony.db /data/data/com.android.providers.telephony/databases/telephony.db)
and "telephony.db-journal" (adb push telephony.db-journal /data/data/com.android.providers.telephony/databases/telephony.db-journal)
i assume this is why mine is not working (stuck at the HC animation loop)

Thank you to all that help me !! My xoom is back to working now have 3g and wifi working fine and I now have a root applied. For anyone that wants a bit of a smoother path (I am sure I will not be the last noob to do this) the attached ZIP has all the required files to root your device or fix it if you have stuffed it up (ie applied a US 1 click root like I did). The telstra 3g files are included.
Follow the intructions I did in the link below and the the final set of commands to push the telstra comms files back. Hope this reduces the pain for someone else !!
http://forum.xda-developers.com/showthread.php?t=1049901
After completing instructions in the link do the following
adb remount
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
adb push settings.db-wal /data/data/com.android.providers.settings/databases/settings.db-wal (no bites sent)
adb push settings.db-shm /data/data/com.android.providers.settings/databases/settings.db-shm
adb push build.prop /system/build.prop

mdevlin said:
Thank you to all that help me !! My xoom is back to working now have 3g and wifi working fine and I now have a root applied. For anyone that wants a bit of a smoother path (I am sure I will not be the last noob to do this) the attached ZIP has all the required files to root your device or fix it if you have stuffed it up (ie applied a US 1 click root like I did). The telstra 3g files are included.
Follow the intructions I did in the link below and the the final set of commands to push the telstra comms files back. Hope this reduces the pain for someone else !!
http://forum.xda-developers.com/showthread.php?t=1049901
After completing instructions in the link do the following
adb remount
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
adb push settings.db-wal /data/data/com.android.providers.settings/databases/settings.db-wal (no bites sent)
adb push settings.db-shm /data/data/com.android.providers.settings/databases/settings.db-shm
adb push build.prop /system/build.prop
Click to expand...
Click to collapse
Glad you got it sorted

hmmmm....
Not sure what's going on here. It was all working fine (well, mostly), just the odd 3g dropout after coming off wifi. I tried flashing the telephony files from the euro update thread hoping to fix that, and then no 3g at all. I then thought, what if I pushed the build.prop from watt4's post (I was using just the frankenrom one from euro post). Then , bam. Bootloop. I successfully got into recovery and flashed 3.1 again and it will work, but every time I flash the build.prop from here I get a bootloop.
any ideas anyone?

I've done all of the steps, and everything was working as expected, but after I restarted, it was showing the honeycomb loads screen for ages and ages (stuck?)
Any ideas? It gets past the M Dual Core screen, but then just loops the boot animation.

I've done all of the steps and I can boot into Honeycomb 3.1, but 3G isn't working. It gets stuck at "Searching for service..." while trying to activate.
I'm using the default build.prop, but I tried the frankenrom and my own (using the steps in the post), and nothing works.
Thoughts?
Edit: Fixed it. I reloaded the settings and telephony dbs after pushing the boot.prop and its now found Telstra and successfully using 3G!

abbaskip said:
I've done all of the steps, and everything was working as expected, but after I restarted, it was showing the honeycomb loads screen for ages and ages (stuck?)
Any ideas? It gets past the M Dual Core screen, but then just loops the boot animation.
Click to expand...
Click to collapse
Ok, So I fixed this it seems. It was that bat Build prop causing the boot loop.
However, now it's happening again. I made the mistake of trying a different framework file (which was meant to force the browser into desktop all the time). And it gave me bootloop. So I reflashed 3.1 etc, and tried again. It loaded (without Telstra service again), so again I repushed the frankenrom build prop (which had worked previously) and the connectivity settings. But again bootloop...I can't get my tab to be alive and have telstra connectivity
EDIT: Thought after reflashing I may have been missing the Wipe data/factory reset step, but did the whole process again, and still no luck!
It's so strange! I can get into the OS without Telstra connection, but once I push those settings it boot loops?! Is there anything else I can try?