yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Q&A, Help & Troubleshooting] fjelsten:
Nobody gets this - or is there no solution?
[Galaxy S I9000 Q&A, Help & Troubleshooting] GuestK0097:
The browser does that automaticly. You can set another browser as default but if you open the standard browser it opens the URL with it and not with the one set as default. The same with other browser like firefox, opera and dolpfin hd.
[Galaxy S I9000 Q&A, Help & Troubleshooting] fjelsten:
This is a pita - and I can't believe this is how it's supposed to work but thank you for your answer
[Nexus One Q&A, Help & Troubleshooting] jonahs:
So, I've been trying to figure this out and before I go too far with this I'd like to ask you people if you have tried to change the information in "android-info.txt" within a "signed-passion-img-XXXXXX" file.

What I'm looking at is trying to downgrade a software-rooted, locked bootloader, FRG83D to any lower version and I just noticed this row in "android-info.txt";

version-bootloader=0.33.2012

Right now, my bootloader-version is 0.35.0017 (upgraded from FRG83X as I understand it).

So I was thinking "hmmmm, how about changing that version number to the one I got and try that out?" but went for the better safe than sorry routine before doing anything stupid.

Will this help? Will I be able to flash this PASSIMG.zip by changing the version-bootloader value or is this a dead end?

Why am I doing this? Well, I want to find out an as fast as possible way to restore an N1 to factory/stock state, with a locked bootloader.

I appreciate any information on this; both the version-bootloader question and any insight on any fast way of restoring the phone to stock without unlocking the bootloader.
[Nexus One Q&A, Help & Troubleshooting] cmstlist:
There's already a guide to downgrading HBOOT. Do not use it if you have an SLCD Nexus One, AMOLED only.

If you're just trying to get to stock unrooted for warranty or resale reasons, no need to downgrade. You could apply the FRG33 PASSIMG, then take the OTA upgrade.
[Nexus One Q&A, Help & Troubleshooting] ajitpillai:
the downgrading of bootloader is mainly to flash older cyanogenmod roms but the latest 6.1.1 supprts the new bootloder and if u hav a SLCD nexus one ur fone will get bricked (it happend to me!) so please dont flash the PASSIMG unless u chek wad display u hav!
[Nexus One Q&A, Help & Troubleshooting] Jack_R1:
Once you make changes to PASSIMG.ZIP, it loses its signature - and you can't sign it, since you don't have Google keys. So changing it won't allow you to flash it, because it'll fail verification.
[Nexus One Q&A, Help & Troubleshooting] cmstlist:
And this is why the downgrade instructions involve flashing first a modified MISC partition - so that it fools the PASSIMG version check into letting you downgrade.
[Nexus One Q&A, Help & Troubleshooting] jonahs:
I'll definitely check this one out. I tried going for the unmodified FRG91 and older ones but they didn't flash at all. I'll fiddle a bit with the FRG33 instead.
[Nexus One Q&A, Help & Troubleshooting] jonahs:
Ah, that explains a thing or two. Guess this has to do with the signatures and packages being checksum checked against a hash or some other method.
[Nexus One Q&A, Help & Troubleshooting] jonahs:
That worked like it was never intended to do anything else than restore the phone to a stock/factory state.

Awesome! Thanks!
[Vibrant Q&A, Help & Troubleshooting] Sam v boy:
I was wondering if you guys know of a windows rom for my vibrant . Or if any developers could make on . Please hit me up.
[Vibrant Q&A, Help & Troubleshooting] cjggilbert:
Shame
[Vibrant Q&A, Help & Troubleshooting] Sam v boy:
What , I serously need it . I have the nero v3 rom , but I want windows

Sent from sam v boy
[Vibrant Q&A, Help & Troubleshooting] FRIEDjellyWALNUT:
This post should belong in the Q&A section. Anyhow, assuming you are not a troll, I have never heard of Windows being ported to any Android device. If you want both Windows mobile and Android get the HTC HD2.
[Vibrant Q&A, Help & Troubleshooting] web_ninja:
Well from my though, Windows is closed source. Microsoft will not in a million years release the source for any of their products.... which makes porting very difficult. Could always buy a windows phone... OR find out if there is a way to run a virtual machine within froyo? but highly unlikely... there is a program to remote into your windows box though.. team viewer and phone my PC... :cool:
[Vibrant Q&A, Help & Troubleshooting] Sam v boy:
Well , thanks . I will try to get the htc hd2 to dual boot it

Sent from sam v boy
[Vibrant Q&A, Help & Troubleshooting] mmelo76:
Moved of: Samsung Vibrant > Vibrant Android Development

To: Samsung Vibrant > Vibrant Q&A

Please put your questions to: Vibrant Q&A

Ok! Thread Closed
[Desire Q&A, Help & Troubleshooting] babblerx:
My Desire recently had to be sent back to HTC for repair. Came back with hboot 0.93.001. When I got it back, I rooted it (using Unrevoked) and flashed LeeDroid 2.3b.

However, the phone has developed the common locking/rebooting fault and I need to send it back to HTC again, but before I can send it back I need to reflash the stock ROM (T-Mobile UK).

However, whichever method I try I can't get the stock ROM back on to the phone. If I try reflashing using HTC sync, then I get ERROR #140 or #170 (assuming the phone doesn't freeze during the process).

If I try extracting the ROM.zip and renaming it to PB99IMG and installing from the root of the micro SD then I get a message saying "CID incorrect! Update Fail!"

Does anyone have any ideas how I can get my piece of crap HTC Desire back to stock ROM?

P.S. if you haven't already guessed from the last statement or read any of my other posts about my Desire going wrong, I will NEVER EVER buy another HTC....their customer service stinks worse than a landfill site!!
[Desire Q&A, Help & Troubleshooting] MasDroid:
The CID error indicates that you need a Gold Card, you could use the Gold Card tool in my sig below to create one quickly.

Sent from my HTC Desire using eMIUI
[Desire Q&A, Help & Troubleshooting] babblerx:
OK, I've created the goldcard. Now, how do I get the rom image onto the card? When the phone boots with the gold card in, I can't select mass storage. I've also tried the card in a card reader...it wasn't recognised.

Help???
[Desire Q&A, Help & Troubleshooting] MasDroid:
Are you able to mount your SD card in recovery?

Try the following, I am assuming that you are running Windows 7: Try to re-format the card as FAT32 (if present, right-click on the removable disk and select Format).

1) Check if the device is getting detected in device manager. Follow the steps to go to device manager:

- Click Start, type devmgmt.msc and press enter.

- Search for the name of the device

If the device is not getting detected in device manager, then check if it is hidden device.

- Click show hidden devices under View

- Expand all the nods under device manager

There would be many grayed out entries in device manager uninstall all the grayed out entries under all the nods and then restart the computer and plug the external device to the computer and check if it works

2) Install the latest drivers from the manufacturer website and even make sure the driver is compatible with the version of operating system installed on your computer. check if it works

Link: http://windows.microsoft.com/en-us/windows7/Update-a-driver-for-hardware-that-isnt-working-properly

Install the driver in Compatibility mode: http://windows.microsoft.com/en-us/windows7/Make-older-programs-run-in-this-version-of-Windows

3) Check with any other another SD card if it is getting recognized or detected or you may even check if the same SD card is getting recognized or detected on other computer
[Desire Q&A, Help & Troubleshooting] LakiAntonopoulos:
I have the same prob
[Desire Q&A, Help & Troubleshooting] babblerx:
still having problems...

OK, I managed to create another goldcard with the goldcard tool in your signature. I then extracted the rom from the T-Mobile (UK) stock ROM and renamed it to PB99IMG.ZIP and dropped it onto the goldcard.

Rebooted with the goldcard in the phone and vol - pressed, got the boot menu. The rom image was detected and started to load (side bar in top right of screen showing progress). ROM loaded 100%, then got the 'checking ROM' message. Then..."CID incorrect! Update Fail!" message again.

I've checked and double checked the goldcard creation process and am convinced I'm doing nothing wrong.

Any other ideas? I'm beginning to think hboot 0.93.0001 can't be downgraded.

P.S. I'm running Vista 32-bit
[Desire Q&A, Help & Troubleshooting] EddyOS:
No, flashing an old RUU over a new HBOOT won't work. The issue you've got is there isn't a 2.2 T-Mobile UK RUU available so unless you've got an AMOLED screen the only thing you can do is flash the stock HTC RUU
[Desire Q&A, Help & Troubleshooting] babblerx:
it is an AMOLED screen

Cheers Eddy. However, as far as I can tell, it is an AMOLED screen. All I want to do is get it back to T-Mobile stock ROM so I can send it back to HTC again.

Can't understand why there isn't a 2.2 T-Mobile UK RUU available yet.

It's damned infuriating!! Stuck with a phone I can't use at the minute...and getting desparate!
[Desire Q&A, Help & Troubleshooting] babblerx:
T-Mobile UK Stock 2.2 RUU anbody???

***BUMP***
[Desire Q&A, Help & Troubleshooting] babblerx:
I still need help

Anyone managed to re-install a stock ROM on an hboot 0.93.0001 device yet. If so, how did you do it?
[Desire Q&A, Help & Troubleshooting] digo21:
Im in the same boat. Cant get mine back to t-mobile uk stock either
[Desire Q&A, Help & Troubleshooting] digo21:
I know t mobile would know that the rom has changed from there own one to the htc one, but are the any differences apart from that if the htc rom was installed?

I mean would it run normally and recieve the normal updates ota, and would that affect if the htc was simlocked or anything?
[Desire Q&A, Help & Troubleshooting] EddyOS:
It'd run normally but would get HTC OTA updates not T-Mobile ones. Seems the latest OTA doesn't work on debranded phones, though
[Desire Q&A, Help & Troubleshooting] Droidzone:
@Eddy,

Since he has AMOLED, there's a multistep procedure he can try.

1. Prepare the goldcard correctly with a Format in Fat32 (and deleting any extra partitions. Only 1 partition should exist-It should be a Fat32 Primary). If Goldcard is correct, phone should not give CID incorrect error.

2. Download the WWE 2.29 PB99IMG.zip, and put it in the goldcard and run it.

3. Run Teppic74's downgrader with goldcard. At the last step, choose to use this PB99img (Run this RUU while monitoring your Temp folder for changes. When the RUU loads and displays a window, search temp for Rom.zip. Rename it to PB99IMG.zip and put it in the root of the sdcard) instead of the Teppic one.

4. At this point the phone will have a completely working 2.1 Android OS branded to TMO.

5. Check for and update with OTA (You will get TMO OTAs at this point). Now your phone will have the latest TMO ssoftware and be as good as any other!
[Desire Q&A, Help & Troubleshooting] EddyOS:
But they'd have to extract the PB99IMG file out of the RUU, the RUU on it's own won't do
[Desire Q&A, Help & Troubleshooting] Droidzone:
Yes indeed, but quite doable. The result would be a perfectly unrooted T-Mobile branded phone.

Edit: Added instructions for extracting the PB99IMG.zip from the TMO RUU
[Desire Q&A, Help & Troubleshooting] babblerx:
thanks for all the advice.....

...but I've given up on my Desire.

I can't use it for more than 2 minutes at most without it freezing up!! This is nowhere near long enough to do any of the above! I've even tried resting it on a bag of ice to keep it cool, but even that was no good!

I'm just gonna sell it to one of the recycle companies and put the money towards buying myself out of my contract.

Shame really because when it was working, it was a brilliant phone!!

HTC seriously need to get their house in order QC-wise. I know they have been making phones for a good few years now, but people still say "HTC, who??" and while they're QC remains as bad as it seemingly appears to be then that situation will persist!!

Think I'm gonna take a risk on the LG Optimus 2X when it comes out!! Why? because I love Android...I love bleeding edge...only now I hate HTC with a passion!!!
[Desire Q&A, Help & Troubleshooting] digo21:
Droidzone are you based in the uk, as i dont know how to do what you have said. If you are and can do it for me that would be great and i would pay for your services.
[Desire Q&A, Help & Troubleshooting] babblerx:
Same here. If anyone can get my T-Mobile (UK) Desire (rooted, hboot 0.93.0001) back to stock ROM then I'd be willing to pay (within reason). Bearing in mind you'd first have to solve the problem of it not being usable for any more then 2 minutes even from 'cold'.
[Desire Q&A, Help & Troubleshooting] Droidzone:
No software problem should fail to be repaired by running a ruu. If if freezes or loops while running ruu, that confirms a hardware fault which necessitates a return if the device.

No I'm not in UK. I know that what I described may seem overwhelming, but believe me, if you run the procedure I mentioned, step-by-step and with the files I linked, there is no reason why you can't have your phone up and running in under 45 mins. See the unrooting guide I've written, linked in my signature, for the step-by-step method of running the pb99img from an ruu. It's easy enough. Only things you need for a smooth sailing is a working goldcard and the file extracted from the ruu correctly.

Note that I can't confirm that this method will work for Slcd , and it is quite dangerous running a 1.20 ruu on slcd. Proceed only if you're sure that yours is an amoled desire

Sent from my HTC Desire
[Desire Q&A, Help & Troubleshooting] digo21:
Thanks droidzone.

Can I clarify the procedure with you so that I know I understand it.

1. Prepare the goldcard correctly with a Format in Fat32 (and deleting any extra partitions. Only 1 partition should exist-It should be a Fat32 Primary). If Goldcard is correct, phone should not give CID incorrect error.

2. Download the WWE 2.29 PB99IMG.zip, and put it in the goldcard and run it.

Im guessing that after the two steps above, I will now have the unbranded rom installed on my desire, working normally (but no updates).

Then I do the below steps

3. Run Teppic74's downgrader with goldcard. At the last step, choose to use this PB99img (Run this RUU while monitoring your Temp folder for changes. When the RUU loads and displays a window, search temp for Rom.zip. Rename it to PB99IMG.zip and put it in the root of the sdcard) instead of the Teppic one.

4. At this point the phone will have a completely working 2.1 Android OS branded to TMO.

5. Check for and update with OTA (You will get TMO OTAs at this point). Now your phone will have the latest TMO ssoftware and be as good as any other!

And I'm guessing i can get Teppic74's downgrader form here

http://xdaforums.com/showthread.php?t=768256.
[Desire Q&A, Help & Troubleshooting] Droidzone:
Right so far. The only place where you can possibly go wrong is the goldcard. Note that windows by default hides the extension for files, so double check to make sure that the file is named PB99IMG.zip and not PB99IMG.zip.zip. If in doubt, remove the extension and see if the file is de-recognized. If yes, add the extension, if not, leave the name as such. Keep the file in the root of the card and not in a folder.

Allow teppic downgrader to finish its work.then when it boots correctly, remove the pb99img from the card, before replacing it with your file.

Sent from my HTC Desire
[Desire Q&A, Help & Troubleshooting] digo21:
Oh Great Thanks Droidzone.

When you say boots correctly, do you mean boot in to android, or do you mean when it boots into the recovery/clockwork etc part.

Thanks
[Desire Q&A, Help & Troubleshooting] Droidzone:
Once you run the first step and install the first ruu, you will lose clock work mod recovery forever. :) Until you root it again. Clockwork will be replaced by the android recovery.

Sent from my HTC Desire
[Desire Q&A, Help & Troubleshooting] Droidzone:
I was talking about booting to android home screen with the htc clock widget.

Sent from my HTC Desire
[Desire Q&A, Help & Troubleshooting] babblerx:
I've got no doubt that your instructions above would work Droidzone...if only I could use my Desire for more than 2 minutes without it locking up!! It's driving me mad!!! I can't even get it to stay active long enough to get the CID using the goldcard tool!!!
[Desire Q&A, Help & Troubleshooting] Droidzone:
When you say it doesnt stay active, do you mean it reboots or hangs?

By the way, babblerx, I happened to read on another thread, that you had flashed your device back to stock rom previously and returned it. Which RUU did you flash at the time?
[Desire Q&A, Help & Troubleshooting] babblerx:
It generally hangs....sometimes it'll even hang during the boot up. It rarely reboots.

When I previously flashed back to stock ROM, I was on hboot 0.83 and the ROM was the T-Mobile (UK) stock ROM (Android 2.1) which can be found on the stock ROMs page of XDA Developers. That was when I originally sent it back to HTC for repair. The replacement phone I got back was a refurb unit with a different IMEI and hboot 0.93.0001.

When I have managed to get the phone to boot lately I have tried both of the T-Mobile (UK) ROMs available...neither work.
[Desire Q&A, Help & Troubleshooting] Droidzone:
If your phone doesn't have a hardware fault, which causes it to hang during the process of applying the ruu, then the steps I prescribed would definitely overcome your code 140,170, and cid error.

Sent from my HTC Desire
[Desire Q&A, Help & Troubleshooting] babblerx:
good news

Managed to use my phone long enough to create a goldcard and install the HTC stock ROM in your earlier post.

So far, so good...I've been using the phone for about an hour...and no lock ups or reboots!!!

It's not back to T-Mobile stock yet and I I've lost root, but since the phone is working again, I'm tempted to leave it for now. Having said that, now I know I can get it back to HTC stock, I'm not so afraid to play around with it again

I'll update again later to let you know if it's still working but up to now Droidzone, I definitely owe you a drink or several!! Cheers mate, you've been a fantastic help!!!
[Desire Q&A, Help & Troubleshooting] Droidzone:
Well unless you wish to return it to tmo, you don't have to continue the procedure any further. You can use the unbranded software you have right now. But if you wish to revert to tmo stock, please repeat the entire process in the mentioned order, and please avoid flashing any ruu other than those I've mentioned. That may prevent you from getting back to tmo.

At this point, it is possible to root it again if you wish. :) But don't do an s off unless you have to.

Sent from my HTC Desire
[Desire Q&A, Help & Troubleshooting] babblerx:
OK, I'm happy that my phone is not locking up/rebooting, so I figure it's safe to root it again. I only followed your steps to step 2. I have tried to root with UnRevoked but it keeps failing with 'Failed to flash recovery image' error. I have made sure I uninstalled HTC Sync and all associated HTC USB drivers then installed the USB drivers from the link on the UnRevoked site, but it just isn't working.

Don't suppose you have any ideas?
[Nexus S Q&A, Help & Troubleshooting] garoelms:
Hello!

I have seen the threads on blurry MMS messages in the US.....which has been more or less fixed.....anyone in the UK have any idea how we get this fixed over here?!

I have contacted O2 and they have said the phone is not officially supported by them and therefore they cannot assist (although I bought the phone on a 2 year contract with them!!!). They have advised I take the phone back to Carphone warehouse and get another model as they cannot give me a date when the Nexus S will be supported.

Anyone have a work around for this in the UK? Surely I'm not the only one in the UK with this issue?

Regards

G

UPDATE

~~~~~

Have just spoken with O2 technical data services and they have confirmed there is nothing at all they can do and the phone apparently should be used on the network and they have no plans in the near future to support the phone and they advised I get a refund.

If anyone in the UK has found a work around for this on one of the other networks please let me know as I love the phone agh!! Its available on all the UK networks from Carphone Warehouse/Bestbuy....need to know if they have a fix! :-)
[Nexus S Q&A, Help & Troubleshooting] Highland3r:
Just tried sending an MMS to myself (may not be a valid test :P) and pic looks fine.

On O2 UK (Simplicity package) using Handcent SMS. Rooted running 2.3.1 at the moment.

I've played around with the "stock" APN's which may or may not be relevant - happy to post settings if needed.
[Nexus S Q&A, Help & Troubleshooting] garoelms:
Yeah if you could post setting so I can compare that would be great!

I have tried sending a pic from the camera to myself and thats blurry also! As well as ones other people have sent me.

Dont know if its the phone settings then or something in your rooted ROM may have rectified it? Hmm...
[Nexus S Q&A, Help & Troubleshooting] debro012:
I'm not in the UK, but 2.3.1 corrected the blurry mms for me.
[Nexus S Q&A, Help & Troubleshooting] Highland3r:
MMS APN details:

Name: O2 MMS

APN: wap.o2.co.uk

Proxy: http://wap.o2.co.uk

Port:9201

Username: o2wap

Password: password

Server: http://mmsc.mms.o2.co.uk:8002

MMSC: http://mmsc.mms.o2.co.uk:8002

MMSproxy: 193.113.200.195

MMS port: 8080

MCC: 234

MNC: 10

APN type: mms

(Originally taken from http://www.3g.co.uk/3GForum/archive/index.php/t-96298.html - post dated 12-03-2010, 11:29 AM)

You'll need to reboot for the APN to take affect.

I only have two APN's listed currently (the other is for 3g/mobile web - it's listed on the same post as the MMS APN in the link above)
[Nexus S Q&A, Help & Troubleshooting] daffyno:
sorry m8, what blurry?
[Nexus S Q&A, Help & Troubleshooting] garoelms:
I have tried all the settings you have listed and still exactly the same....cant explain it! It sends fine....but any incoming MMS messages are blurred beyond belief!!! How annoying! grr
[Nexus S Q&A, Help & Troubleshooting] qwerp_:
which network are you on?

i believe there is some switch that can be turn on/off on the network.

when i first switch from iphone to N1, i have similar problem.

sending a MMS to iphone is not a issue (other than needing to manually resize the picture), but upon receiving MMS, it comes in a very small picture.

at that time, i heard other users on other network does not have this issue.

if you have friends on other network, maybe you will want to borrow their sim to give it a try.
[Nexus S Q&A, Help & Troubleshooting] slowz3r:
What a chicken **** response from them.....it is a network issue, prolly the same issue with us on Tmobile
[Nexus S Q&A, Help & Troubleshooting] Highland3r:
What app are you using to send MMS with? Have you tried something like handcent?
[Nexus S Q&A, Help & Troubleshooting] garoelms:
Hi...I have tried it stock and handcent.....same issue! :-(
[Nexus S Q&A, Help & Troubleshooting] garoelms:
I am on O2 UK. ANy idea what this "switch" is as they are clueless their end! I have tried another O2 sim in my handset....exactly the same issue :-(
[Nexus S Q&A, Help & Troubleshooting] garoelms:
When you took these APN details and put them in...did you get a green circle by them? When I entered all the details in manually.....I havent got a green circle and after reboot the net/mms wouldnt work at all! Had to "restore default" to get them back (still blurry!! haha)
[Nexus S Q&A, Help & Troubleshooting] Highland3r:
You get the green circle for the default APN (afaik this should be set to the 3G/Data APN you have setup)

I don't have a green circle (MMS APN set as default) next to the MMS APN either.

You should also ensure you have your 3G/data APN set as default (use the settings on that post if needed) and just delete the other APN's from the list.
[Nexus S Q&A, Help & Troubleshooting] Highland3r:
Have you tried an app such as picsay to reduce the size of the image see if that helps?

YGPM btw