yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] atsoft:
PPC2003 on XDA1

Thanks to those that published all the relevent details to upgrade to ppc2003. It all works a treat thanks. 1 small thing though, the O2 Autoconfig program won't run on the device now and i cant find what the settings should be.

Can anyone tell me what the APN, Userid, password should be for GPRS. Also the DNS server ip addresses ?

I think the APN is MOBILE.O2.CO.UK....

Regards

Andy T
[Upgrading, Modifying and Unlocking] ajkett:
o2 settings for my gprs are as follows:

apn: mobile.o2.co.uk

user: WEB

pass: PASSWORD

(the capital letters are very important)

Mine connects fine with the new 2003 rom, BUT like other people, it connects fine but does not get internet access. If i load interent explorer, it just times out on every page. I read on this thread that welcome.exe might help fix it. I ran that from my windows folder, yet it still doesnt work. Another post on this thread suggested mucking around with your dial up's until it worked.... im still pissing around with my settings but no luck as yet. Im sure its a small thing...because it connects fine.... ive tried manually putting in DNS servers i know into the DNS tab for the connection, but still no luck (i thought it might be that the GPRS connection was fine and your on the net, but you are unable to resolve domain names for I.E.). I'll try connecting to some http:// IP's to test that theory.

I'm about to test receiving SMS msg's.

Cheers for all the info people... keep it coming...

Tony.
[Upgrading, Modifying and Unlocking] ajkett:
ignore my rantings about internet explorer not working for me... i re-read the thread and saw maltloaf's post.

Unticking the proxy server does it.... doh.
[Upgrading, Modifying and Unlocking] atsoft:
All Working OK Now

Thanks guys.

Eventually found a doc on the O2 website that tells how to manually set up, so got there in the End.

For everyone else:-

APN: mobile.o2.co.uk

Primary DNS: 193.113.200.200

Secondary DNS: 193.113.200.201

username: username

Password: password

UNcheck: Use Proxy //Thanks to another member for this

Works great. Means i can use eVC4 which is heaps faster than eVC4.

Regards

Andy T
[Upgrading, Modifying and Unlocking] :
Hi All,

I use the Australian version of O2 XDA.

thanks for all your info and I am now on WM2003!!! :)

Now, everything seems to work okay and the ringing is not annoying me... :wink:

But, one thing I really want to get rid of is the "AT&T" section on the Today's screen....

Does anyone know how to get rid of it??? :twisted:

thanks... :)
[Upgrading, Modifying and Unlocking] samohile:
Upgraded to ATT wm2003

Managed to upgrade my Qtek 1010 to wm2003 by att. Tried to run programA but it extracted the files and then just wouldn't do anything!

I could not run any unzip program to extract the nk.nbf but found it in \Program Files\SX56 Upgrade Utility\english and used SD Card method to flash. I could retain the original RSU, and it's good since I am not sure if that upgrade will work with asian version.

It works much better than any other release of wm2003, however, the multiple reset bug still exists. Good thing is that it comes with upgraded pocket msn messenger.

By and large, it's not a bad deal!
[Upgrading, Modifying and Unlocking] Biso007:
Hello fellows ...

I flashed my xda with A30.09 few hours ago (many thanks to Stefan for his great kitchen !!) ... here is my comments on the last few hours:

1. the sound clipping is not that bad if u use a loud wav file. it doesn't annoy me since my favorite ringing mode is 'increasing' ... ;)

2. i didn't feel this much improved speed over T4.01.00 ... both look the same for me ... will do more tests tho.

3. in general it's stable ... no hangs so far.

4. it doesn't have any extras :( ... T4.01.00 has 2 very nice viewrs for PDF docs and PPT presentations ... may someone tell me where i can get them for free.

5. its network dialog has a nice feature to connect/stop GPRS ... very good point.

6. not sure yet of the notify.db bug status ... will give it more trials.

7. this is general note for all cooked ROMs : don't include EZWAP coz it's not v2.5 with MMS option, and don't include imov coz it won't work as part of the ROM (seems the developer didn't consider having this s/w in ROM so it seems the setup wizrard is trying to update a read only file!!

8. it is a general observation and may someone explain: i thought by including s/w in ROM this will save space in RAM ... this is not true!! ... check the \windows directory and you will find the exe files there ... you can even delete them!! ... it's not the case for 'true' ROM modules like MSN messenger ... the only benefit is saving the installation time after hard reset :)

i will keep the A30.09 for a while then may decide to go back to T4.01.00
[Upgrading, Modifying and Unlocking] samohile:
I agree with all the observations.

The notify bug still exists!

PDF viewer and ppt presentations can be downloaded free from www.freewareppc.com

The sound clipping does annoy if you prefer to keep volume low.

The greatest benefit of cooking a rom is its "theft protection" feature.

And it does not crash like the other wm2003 versions before.
[Upgrading, Modifying and Unlocking] Biso007:
There is no PDF or PPT viewers there ... the only free viewer for PDF I found is of 4.5 MB in size!! ... but it may worth the space since it's from Adobe
[Upgrading, Modifying and Unlocking] TomBrown:
SX56 flashed, but crashed. Now XDA doesn't work.

Hi everyone,

I wonder if someone could help me with my XDA which I just tried to flash with the SX56 I downloaded, but now the XDA won't work :?

I originally used the XDATools OSImageTool to copy the NK.nbf file from the SX56 download to the 128MB SD card which seemed to work okay, then follow the bootloader instruction to write the new version. However didn’t get prompted to do any upgrade, it just sat at the bootloader screen with GSM OK.

So I decided to follow another set of instructions (see quote below). This all seemed to work okay up to 65% flashed, then I got an error message on my computer screen saying it could not continue. From there it was all down hill :-(

I click on the [OK] / [Close] button - I forget, which closed the program. Then tried to load the NK.nbf again, but it wouldn't. The XDA just stayed on the "Upgrading..." screen.

I've tried since to reconnect the device, but active sync does not recognise the device. Functions under the bootloader still work, but doesn't seem to help me.

I am so unhappy about this, after seeing so many others sing praise with their great results.

So, is there anybody out there kind enough who can help me recover my XDA?... if of course it can be recovered? :cry:

Thanks,

Tom.
[Upgrading, Modifying and Unlocking] Biso007:
What's your bootloader version ?

Did you try the hard reset ?
[Upgrading, Modifying and Unlocking] TomBrown:
Apologies for not including additional details.

Wallaby Bootloader V5.14

Details displayed at bootup when the XDA was working:

G32S54

R4.21.00

3.17.03

Thanks,

Tom.
[Upgrading, Modifying and Unlocking] Biso007:
Plz take a look at this topic http://xdaforums.com/viewtopic.php?t=2079

I believe you may need to have Wallaby 5.15 to use the SD method.

May someone more experienced than me to confirm you it's the right solution.

Good luck ... :)
[Upgrading, Modifying and Unlocking] TomBrown:
SX56 flashed, but crashed. Now XDA doesn't work.

I've tried all the suggestions in http://xdaforums.com/viewtopic.php?t=2079 but I can't get a connection to my XDA via the ActiveSync on my computer, therefore can't get any of the tools to work.

Is there any way of fixing this problem without the ActiveSync component?... or have I missed another option somewhere.

Getting into the Bootloader (V5.14) seems to work fine, but now when I reset the XDA normally, or press in the smaller button (bottom right) with the scored out battery logo and then restart, it just comes up with a white screen with black noise on the screen. I think this originally was the "updating" screen but now gone funny. Just I'm not laughing.

Any further help would be very much appreciated.

Thanks,

Tom.
[Upgrading, Modifying and Unlocking] dtidmore:
Nightmare

Just an update on the SX-56 fiasco. LOTS of us had problems with the Siemens/AT&T upgrade that left the phone stack uninstalled and with NO way to reflash the radio stack successfully. I sent my unit to the PPC Tech guys who have been waiting for a MS MVP to help them with the problem. Seems that there is a program contained in the radio stack that MUST be there before you can reflash the stack. NO radio stack, no way to reflash. I contacted AT&T and they blamed Siemens and told me that I would have to contact Siemens and have them fix it. I contacted Siemens who acknowledged the problem and gave me a no-cost RMA (other than my initial shipping) to have the unit reflashed by Siemens. They told me to expect a 3-5 day turnaround. I had the PPC guys ship it to Siemens, who got the unit on Feb 19 (FedEx tracking). As it is now almost 2 weeks later, I called Siemens today. They have been unindated with returned SX-56s needing reflash. They are blaming AT&T for telling everyone to upgrade, but AT&T wanted everyone to upgrade as the new radio stack contained specific enhancement to improve GSM performance. NOW it gets ugly, Siemens is telling me the turn around time is now expected to be at least 30 days and when it is reflashed, Siemens will NOT flash it to WM2003 and the new radio stack. That has to be done by the customer and it may fail again. I called AT&T and they are clueless (in more ways than one). They offered to put my acct on hold while the SX-56 was being fixed, but that would extend my contract for the amount of time it was on hold. NO WAY. They offered me a new phone (extend contract or buy outright) NO WAY. She finally agreed to do some more investigating and see if given the # of affected customers (yes they are aware of the problem), maybe AT&T would agree to suspend the acct and NOT extend the contract.

Everyone seems to have overlooked that this is more than just a phone issue. Those of us with the SX-56 used them as our PDAs. This is big impact. I am seriously considering paying the cancellation fee and moving to either Cingular or T-Mobile. AND this is the last Siemens branded phone that I will purchase.

This whole upgrade was obviously NOT sufficiently tested.

David
[Upgrading, Modifying and Unlocking] Smokinvegas:
all is well with siemens and the sx56 being returned

:D

Those of you concerned about your sx56 being returned no need to worry. I sent my sx56 in on the 2-12-04. I expected it would take 4 to 6 weeks before I would see my sx56 again. Needless to say I received it on 3-04-04. It was restored to the original configuration wm2002. I immediately ran the upgrade and this time around it worked flawlessly. I had another sx56 that was a refurb. I did a sd backup and then installed the backup on the newly upgraded windows mobile 2003. It worked flawlessly. I am excited to finally have a working sx56 instead of a brick.
[Upgrading, Modifying and Unlocking] cgigate:
For all upgrade failure- crash, radio stack broken, bootload

For all upgrade failure- crash, radio stack broken, bootloader damaged.

If your phone is out of warranty, or any reason no way to get Siemens service.

I can help all people to fix the problem at a fee.

cgigate@unifiedcomm.com
[Upgrading, Modifying and Unlocking] jonathanmiami:
I try to install the upgrade but from Siemens but It make me lose my GSM Bands,

I returned the phone to the seller and now I got a new one with XDA on it but with Pocket PC 2002.

Anybody that can help me out?
[Upgrading, Modifying and Unlocking] ranmasaotomes:
Has anyone worked out what the prob is with the volume yet?

I tried the T-Mobile rom on my XDA but it is prone to crashing. I have found that the ATT rom works better except for that annoyance with the sound starting really low and going up gradually.

The worst hing is that it even does it on my MP3's
[Upgrading, Modifying and Unlocking] ranmasaotomes:
Does this mean that no one has found a cure for the sound problem.

I really want to go back to this rom as it is the best that there has been.

IMO anyway.

I would live to go back to this rom. when someone can help with the volume problem.
[Upgrading, Modifying and Unlocking] lanzx:
XDA - ATT RELEASES FINAL WM2003

Hi a newbie here!,

I'm refering to this page

http://xdaforums.com/viewtopic.php?t=5623&start=0&postdays=0&postorder=asc&highlight=

I have intention to upgrade my O2 XDA I (Asia) with this release of WM2003.

It is possible ? or it only works on Siemens SX56

FYI here is my device information

ROM version 3.20.06 ENG

ROM date 07/30/03

Radio version 4.21.01

Protocol version 32S54

Hope for a helpful reply.

Thanks guys
[Upgrading, Modifying and Unlocking] Biso007:
Yes it can be used with any HTC Wallaby device ... including the SX-56

Just make sure to flash

ONLY

the ROM and don't touch the RSU
[Upgrading, Modifying and Unlocking] lanzx:
Try SD Method But The ROM Not Flashed

Hi,

I use XDATool to copy the NK.nbf to SD card and follow steps given in this topic, but the bootloader seems not read the new ROM, and the process takes less then 5 second as mentioned in this topic.

So after on/off the battery switch...my XDA boot as pocket pc 2002...not windows mobile 2003...

Which step did I missed ?...(is there something i should do to instruct the bootloader look for ROM update in SD)

FYI my XDA bootloader is 6.22

Any help is most grateful...

(Sorry for my bad english)
[Upgrading, Modifying and Unlocking] funkay:
SX56 Windows Mobile 2003 no longer available

Hello,

I'm going to buy an SX56 on ebay. Seimens is no longer releasing Windows Mobile 2003 for it. I was wondering if you still had the executable. Does anyone have it or know what the exact name of it is so I can try to google it? Please email/pm me. I have a gmail account or FTP it can be sent to.

http://communications.siemens.com/c...tion:-5_pageType:downloads_imagePos:0,00.html

"We are sorry. This Free Microsoft Pocket PC 2003 Update is no longer available from Siemens."

I guess it was just too much hassle or something.

Thanks

Joe
[LG Optimus L9 P760, P765, P768, P769] Albertook:
Can someone tell 2 me a good unlocker website?lg l9 p769 can be unlocked?
[LG Optimus L9 P760, P765, P768, P769] rbraswell8:
Okay, first, quit posting the same freakin thing in multiple areas, its both noobish and makes you look like you have absolutely no reason to be on this site. Second, wait 90 days and email t-mobile for the unlock code and they'll do it for free, even going so far as to give you instructions on how to do it. Lastly, welcome to our little corner of the internet.
[LG Optimus L9 P760, P765, P768, P769] atljatl:
Also, unlocking outside of the above mentioned process through your carrier was recently deemed illegal under U.S.law. xda doesn't condone illegal activities, so use Google for any further questions.
[Nexus 7 Q&A, Help & Troubleshooting] deter:
Hi all,

My play store will not open after updating my PA Rom from 4.2.1 to 4.2.2. I did a full wipe and factory reset before updating, but when I flashed the new rom and google apps the play store just simply shows a white screen and closes after a second - no error message or anything.

I've tryed clearing the data for Google Play Services, the Play store app itself, and disabling it and rebooting multiple times and still nothing. I've also tried reflashing the google apps package and redownloading it, and still nothing. Lastly, I uninstalled the play store app via TB and reflashed the google apps package and that did not work, either.

Running Paranoid Android 3.15 Android version 4.2.2 Grouper. Do you guys think it's an issue with the rom, maybe? I couldn't find anything in the development thread leading me to think no, so I'm guessing it's just my device.

I searched around for a bit and found something about the vender.apk - but not much help on that. Thanks in and advance - any other help would be appreciated.
[Nexus 7 Q&A, Help & Troubleshooting] Billchen0014:
just reinstall everything including the rom and do a factory reset.
[Nexus 7 Q&A, Help & Troubleshooting] squabbi:
Maybe you could try flashing Google Apps for 4.2.2 :fingers-crossed:
[HTC One X] Anim@niax:
Good morning:cool::cool::cool::cool: or afternoon, or night, depend on your timeline. It's 7:44 AM here.

So people, the Infobar A02 had been released by KDDI au for more than a month. I'm very, very, very exciting to get it. The problem here is: I wonder if any Japanese here try to unlock it? So far all I can find is a way to temproot it:

htcsoku.info/htcsokudev/2013device/root-a-locus/ (Sorry:laugh: Still not enough post to actually post a link)

This one is basically a modified version of HTC One X, so someone on 2chan suggest that we should follow the same procedure of unlocking the AT-T HTC One X to unlock this one, after rooting.

Anyone here try anything? Very appreciate any helpings :D
[HTC One X] DeeZZ_NuuZZ:
This here isn't the att HTC one X forum its the international HTC one X forum with tegra 3 therefore no one here tried because we can't use that

Gesendet von meinem HTC One X mit Tapatalk 2
[HTC One X] Anim@niax:
Oh? Right. Thank you, sorry for asking the wrong room. I'll move this to the right place.
[Android Q&A, Help & Troubleshooting] ultimate_reconx:
I rooted my phone a while back with a one click root process that rooted it to a rooted version of the stock rom. Recently I recieved notification that Jelly Bean is now available for my phone and that I need to connect to my computer via usb to update. But, my computer keeps getting a "device not recognized" error. I tried to install Kies for the drivers with no luck, uninstalled the drivers from Kies and installed the others straight from the Samsung website with no luck. I have tried 2 different computers and three different usb cables, including 2 oem usb cables. I have windows 7 which may be the problem. Are there any work arounds like going to stock from my sd card? My phone is no longer rooted, but for some reason still has Superuser which i can uninstall still. I brought my phone to Sprint which the guy was really cool and informed me that its not the usb port on the phone and that odin is recognizing it, but odin on my computers doesn't even see it.
[Android Q&A, Help & Troubleshooting] PikachuCLS:
Did you have the Android drivers installed previously? I'm assuming that you're trying to install the drivers for the first time on that your computer and that you have USB Debugging enabled. I'll also be assuming you disabled driver verification, which can be a problem in some computers.

First you need to boot your phone normally, and plug it into the computer. Press Win+R to open the "Run" dialog and run "devmgmt.msc," which is the Device Manager. Look up the "Unknown Device" that is your phone and double click it. Click on the Event tab and check the Hardware ID in the drop-down box. It should look something like this (sorry mine is Android Composite ADB Interface because I've installed it already, but that's what it should look like in the end):

Now you have to make a new section in the driver inf. It should be in the google adt bundle and in the extras\google directory. The file name is android_winusb.inf. In the picture below my tablet is the iDeaUSA CT702. You need to add one of these sections in both the x86 and x64 section if you have a 64 bit computer. If not, just put it in the x86 section. The %USB stuff needs to match that in the Device Manager Hardware ID.

Now you should have a device called Android Composite ADB Interface or anything like that is fine.
[Android Q&A, Help & Troubleshooting] ultimate_reconx:
It says there are no drivers and that there is no hardware id. All there is are device instance id. Im not quite sure where the driver.inf is located. This has been a pain for the past week. Hopefully we can figure this out. Lol.
[Android Q&A, Help & Troubleshooting] ultimate_reconx:
I think there may have been something wrong with the rom. If i could just reinstall stock i think it would work. Just need to get the USB to read to the computer.
[Android Q&A, Help & Troubleshooting] PikachuCLS:
If you don't know where the driver is, then download a new one. I've uploaded the official Google USB driver to mediafire here: Mediafire - usb_driver.zip

You need to modify this driver, then when asked to select the inf file for driver installation choose the android_winusb.inf inside. After installation your phone should be recognized. Please tell me if there's any uncertainties you have.
[Android Q&A, Help & Troubleshooting] Cha1n5aW:
Have you tried connecting the device with usb dev mode disabled? I know its strange but I've a few devices that use different drivers if the usb dev mode is enabled. I've also devices where I need to enable usb mass storage setting every time (settings menu or slide down notification). Also it never hurts to try a new cable, usb wires do tend to wear out and are very cheaply manufactured so they break inside with the slightest tug of the wire. I know most of this stuff is uber basic but I've made things much worse on countless occasions by overlooking simple stuff like this.
[Android Q&A, Help & Troubleshooting] PikachuCLS:
Good point. If you don't have developer mode usb debugging enabled, then there will be no "unknown device" as shown above in the device manager. Be more detailed about "no luck" please.
[Android General] zedawg:
Thanks for this! It helped a lot
[Android General] Ricky Divjakovski:
nice to know! :)
[Android General] mark manning:
Stuck, good job :)
[Android General] Gabilheri:
Thank you very much! :)
[Android General] liqueurlee:
Thanks for your sharing these.
[Android General] Ricky Divjakovski:
It was not shared, I made the package and guide myself, hope this has helped!
[Android General] liqueurlee:
Thanks again and it is very useful to me. :)
[Android General] TheStrokerace:
Ummm, what is the purpose of this guide and what phone is it for?

It looks like its for an HTC. If it is, you should put that in the beginning so everyone knows. You should also explain why you are doing this and what it does to the phone. From what I can tell, it does nothing at all and not even worth being a sticky
[Android General] thanhtaivtt:
Thanks you very much!

Thanks you very much!
[Android General] Ricky Divjakovski:
This is for all android phones, if you knew what Adb and fastboot are you would be quite happy that I have posted this guid.

Also if it wasn't worth a sticky it wouldn't be here as it has to be approved.
[Android General] Ricky Divjakovski:
Android debug bridge, and this is a developers website and lucky enough people like me enjoy helping others.

Anyways I don't want my thread ruined, you don't like my topic so don't comment
[Android General] justmpm:
Sorry for the interuption. This thread needed little cleaning. It was going a little bit of course.

ADB and fastboot are incredibly useful tools and a lot of problems can be solved using these tools. The OP has made an installer and a "quick launcher" that makes using ADB and fastboot a lot easier for people who are unfamiliar with using the command line and he provides an introduction into entering commands. This thread can be a valuable resource for people who need help getting started with ADB and Fastboot - let's not derail it by arguing!

Thanks!
[Android General] thrt:
Thanks you very much!
[Android General] Swav3y:
thanks for the guide:o
[Android General] bstyle bears:
Thamk you!!!!!!!!!!!!!!!!!
[Android General] Miaxus:
Thanks a lot man ;)
[Android General] 9anas:
Thank you very much!

Thank you very much!
[Android General] mikevillarroel:
Is there a command or something to copy everything on the internal storage os a device that only boots to bootloader?
[Android General] Scapoose:
So as I've read through the comments it seems everyones got every other phone or what not,

any chance you know if there is a touch fastboot img or something ? for Moto x 1st Generation. If so i haven't any clue where to look for it.
[Android General] dawgdoc:
I haven't heard of a touch fastboot.img.

I have seen a generic tethered recovery for devices with locked intel bootloaders. But, it's not touch.