Hi All,
I have had a bit of a unlikeable experience with HTC today that I felt I needed to share with the community. My HTC Desire has been purchased off EBay as I just couldn't wait to get my hands on one. I was assured by the seller that the device had not been rooted and never questioned the information. This may have been my mistake, however I took it for granted I had an unbranded Desire and this was the reason the device took my Vodafone SIM without worries.
So, oblivious and ignorant to any potential history of the device I get the long awaited OTA prompt today. I have been waiting ever so patiently for the new features, especially the official implementation of APP2SD. I was aware of the possibilities of rooting my device for this feature, however did not want to jeopardise my investment so soon after purchase.
Well, needless to say the update has not gone smoothly. The download completes fine and the installation begins to take shape, however towards the end of the installation a reboot cycle begins and all starts to go pear shaped. The black screens complete OK, however I then get a white screen that contains a percentage indicator. At this stage there is a short delay before I am apologised to and informed that "Process system is not responding.". I have the option to "Force Close" or "Wait", I'm patient by nature so I "Wait"... Whichever option I choose always results in the same outcome anyways... This process repeats some ten times up to the 97% stage (enough to take me to the end of my tether). I finally figure out that if I take the SD Card out the phone will boot into the Home Screen. I have to replace the card for HTC Sense to boot up. At this stage things get even weirder as the same error message continues and my SIM Card is refused. The system is just about accessible but frequent random reboots occur every few minutes or so.
I feel I have tried all obvious techniques to resolve the problem, including a number of different hard resets and blanking the SD Card used in the device (inc. simultaneously), however once the update has been applied stability can not be regained.
I phoned HTC and explained my predicament. They say it was sold as a T-Mobile device and it must have been rooted to accept my Vodafone SIM card. They offered to reflash the device for £50, however could not advise if it would be the 2.1 or 2.2 firmware that would be installed. I imagine I would probably end up with a T-Mobile locked device if I took this option, and the 2.1 firmware... :-S
Thankfully I have found my own resolution using a Goldcard and this firmware image:-
PB99IMG_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.zip (Posted by 'ortonnorth')
I renamed the file to "PB99IMG.zip" and booted up holding the Volume Down key and seem to have successfully flashed back to the 2.1 firmware that was installed when I obtained my device. After getting back onto 2.1 and trying to update to 2.2 again (over wi-fi) all the same symptoms were present, back to 2.1 again and all is OK. To be honest I'm still uncertain as to whether my device is rooted, I'm gonna try checking as soon as I finish this post..
I have gathered this information along the way:-
Code:
[B][U]2.2 OTA Update[/U][/B]
Android Version : 2.2
Baseband Version : 32.36.00.28U_4.06.00.02_2
Kernel Version : 2.6.29-0cb9f166 (htc-kernel 'at' and18-2 #1)
Build Number : 2.09.405.8 CL218634 release-keys
Software Number : 2.09.405.8
[B][U]2.1 WWE ROM[/U][/B]
Firmware Version : 2.1
Baseband Version : 32.36.00.28U_4.06.00.02_2
Kernel Version : 2.6.29-0cb9f166 (htc-kernel 'at' and18-2 #1)
Build Number : 1.21.405.2 CL174215 release-keys
Software Number : 1.21.405.2
I write this in the hope that I can warn others who may be just about to make the same mistake, and hopefully provide some information about how to get back out of the situation. I personally was a bit livid that HTC wanted to charge me for a repair, despite being prompted for an update by their device. I probably wouldn't even mind paying it if I was going to get the 2.2 update, but the intentions seemed to be to flash it back to stock.
May I also take the opportunity to express gratitude to the community. Without the information on this site I would have been at HTC's mercy..
Thanks for reading!
Futurian
Kernel version for OTA Update is 2.6.32
Hi
That solution was posted in the dev forum this morning
I hope everything works ok now on your Desire. Your post is really helpful for people who might come across this problem.
Sent from my HTC Desire using XDA App
sfa said:
Kernel version for OTA Update is 2.6.32
Click to expand...
Click to collapse
I thought it was a bit suspicious that the Kernel hadn't changed, also I am believing that the Radio ROM should also update during the process..
huwwatkins said:
Hi
That solution was posted in the dev forum this morning
Click to expand...
Click to collapse
Did look around, shame I didn't notice it :-S O well, if one person is able to fix their phone from my post then the effort won't have been in vain
thpoul said:
I hope everything works ok now on your Desire. Your post is really helpful for people who might come across this problem.
Click to expand...
Click to collapse
Everything is looking perfect as of yet I have checked that my phone isn't rooted (No Ninja icon, can't "su" in a terminal). God knows what the problem is!
Update : OTA Update completed successfully using Gold Card!
1) Create a blank gold card and insert into device.
2) Download OTA Update through Wi-Fi.
3) Turn off Wi-Fi and disassociate from Access Point.
4) Install Update.
Code:
[B][U]New System Information[/U][/B]
Android Version : 2.2
Baseband Version : 32.43.00.32U_5.09.00.20
Kernel Version : 2.6.32.15-gf9c0527 (htc-kernel 'at' and18-2 #1)
Build Number : 2.09.405.8 CL218634 release-keys
Software Number : 2.09.405.8
Happy days!
Futurian said:
I renamed the file to "PB99IMG.zip" and booted up holding the Volume Down key and seem to have successfully flashed back to the 2.1 firmware that was installed when I obtained my device. After getting back onto 2.1 and trying to update to 2.2 again (over wi-fi) all the same symptoms were present, back to 2.1 again and all is OK. To be honest I'm still uncertain as to whether my device is rooted, I'm gonna try checking as soon as I finish this post..
Click to expand...
Click to collapse
I tried this, just comes up wit error message "CID incorrect" Update Fail! Do you want to reboot the device...
Any ideas?
chessmaster82 said:
I tried this, just comes up wit error message "CID incorrect" Update Fail! Do you want to reboot the device...
Any ideas?
Click to expand...
Click to collapse
Need to use a Goldcard.
CID
Just tried creating a gold card again, does this look like a valid CID to you guys?
CID: 00000000000000000049E917D100A69E
Reversing CID
CID: 00A600D117E949000000000000000000
Seems not to me... why so many zeros ? oO
chessmaster82 said:
I tried this, just comes up wit error message "CID incorrect" Update Fail! Do you want to reboot the device...
Any ideas?
Click to expand...
Click to collapse
Ive just created a new goldcard with CID shown above, loaded the file PB99IMG, Powered up whilst holding the down volume, entered Hboot, but it didnt do anything with th file this time, any ideas?
chessmaster82 said:
Just tried creating a gold card again, does this look like a valid CID to you guys?
CID: 00000000000000000049E917D100A69E
Reversing CID
CID: 00A600D117E949000000000000000000
Click to expand...
Click to collapse
bightf said:
Seems not to me... why so many zeros ? oO
Click to expand...
Click to collapse
Thats what I was thinking... I've followed the instructions properly, only im using Gold Card Tool 0.05 by Klutsh rather than the command line
Update - Just tried the CMD method, get the same CID 00000000000000000049E917D100A69E reversed is 00A600D117E949000000000000000000
chessmaster82 said:
Ive just created a new goldcard with CID shown above, loaded the file PB99IMG, Powered up whilst holding the down volume, entered Hboot, but it didnt do anything with th file this time, any ideas?
Click to expand...
Click to collapse
PB99IMG.zip ?
chessmaster82 said:
Thats what I was thinking... I've followed the instructions properly, only im using Gold Card Tool 0.05 by Klutsh rather than the command line
Update - Just tried the CMD method, get the same CID 00000000000000000049E917D100A69E reversed is 00A600D117E949000000000000000000
Click to expand...
Click to collapse
Futurian said:
PB99IMG.zip ?
Click to expand...
Click to collapse
Im running W7, so doesnt show it's a zip therefor no need to label as zip, if I go into properties it tells me its a zip file
There's an app on the Android Market called "GoldCard Helper". Does this give you the same reverse CID for your SD Card? I believe I have read that not every Make/Brand/Model of SDCard will be usable for the process, you could be one of the unfortunate ones with an unsuitable card. Can we also confirm that the card is formatted as FAT32?
The exact filename is still very relevant, Windows 7 is not going to work this out for you. I recommend showing file extensions for known file types, so that you can be sure that its exactly "PB99IMG.zip" and not anything like "PB99IMG.zip.zip"..
huwwatkins said:
Hi
That solution was posted in the dev forum this morning
Click to expand...
Click to collapse
would you send a link for the solution?
Futurian said:
Hi All,
I have had a bit of a unlikeable experience with HTC today that I felt I needed to share with the community. My HTC Desire has been purchased off EBay as I just couldn't wait to get my hands on one. I was assured by the seller that the device had not been rooted and never questioned the information. This may have been my mistake, however I took it for granted I had an unbranded Desire and this was the reason the device took my Vodafone SIM without worries.
So, oblivious and ignorant to any potential history of the device I get the long awaited OTA prompt today. I have been waiting ever so patiently for the new features, especially the official implementation of APP2SD. I was aware of the possibilities of rooting my device for this feature, however did not want to jeopardise my investment so soon after purchase.
Well, needless to say the update has not gone smoothly. The download completes fine and the installation begins to take shape, however towards the end of the installation a reboot cycle begins and all starts to go pear shaped. The black screens complete OK, however I then get a white screen that contains a percentage indicator. At this stage there is a short delay before I am apologised to and informed that "Process system is not responding.". I have the option to "Force Close" or "Wait", I'm patient by nature so I "Wait"... Whichever option I choose always results in the same outcome anyways... This process repeats some ten times up to the 97% stage (enough to take me to the end of my tether). I finally figure out that if I take the SD Card out the phone will boot into the Home Screen. I have to replace the card for HTC Sense to boot up. At this stage things get even weirder as the same error message continues and my SIM Card is refused. The system is just about accessible but frequent random reboots occur every few minutes or so.
I feel I have tried all obvious techniques to resolve the problem, including a number of different hard resets and blanking the SD Card used in the device (inc. simultaneously), however once the update has been applied stability can not be regained.
I phoned HTC and explained my predicament. They say it was sold as a T-Mobile device and it must have been rooted to accept my Vodafone SIM card. They offered to reflash the device for £50, however could not advise if it would be the 2.1 or 2.2 firmware that would be installed. I imagine I would probably end up with a T-Mobile locked device if I took this option, and the 2.1 firmware... :-S
Thankfully I have found my own resolution using a Goldcard and this firmware image:-
PB99IMG_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.zip (Posted by 'ortonnorth')
I renamed the file to "PB99IMG.zip" and booted up holding the Volume Down key and seem to have successfully flashed back to the 2.1 firmware that was installed when I obtained my device. After getting back onto 2.1 and trying to update to 2.2 again (over wi-fi) all the same symptoms were present, back to 2.1 again and all is OK. To be honest I'm still uncertain as to whether my device is rooted, I'm gonna try checking as soon as I finish this post..
I have gathered this information along the way:-
Code:
[B][U]2.2 OTA Update[/U][/B]
Android Version : 2.2
Baseband Version : 32.36.00.28U_4.06.00.02_2
Kernel Version : 2.6.29-0cb9f166 (htc-kernel 'at' and18-2 #1)
Build Number : 2.09.405.8 CL218634 release-keys
Software Number : 2.09.405.8
[B][U]2.1 WWE ROM[/U][/B]
Firmware Version : 2.1
Baseband Version : 32.36.00.28U_4.06.00.02_2
Kernel Version : 2.6.29-0cb9f166 (htc-kernel 'at' and18-2 #1)
Build Number : 1.21.405.2 CL174215 release-keys
Software Number : 1.21.405.2
I write this in the hope that I can warn others who may be just about to make the same mistake, and hopefully provide some information about how to get back out of the situation. I personally was a bit livid that HTC wanted to charge me for a repair, despite being prompted for an update by their device. I probably wouldn't even mind paying it if I was going to get the 2.2 update, but the intentions seemed to be to flash it back to stock.
May I also take the opportunity to express gratitude to the community. Without the information on this site I would have been at HTC's mercy..
Thanks for reading!
Futurian
Click to expand...
Click to collapse
My 2p here...
This isn't HTC fault and the fact they offered to help at all is a credit to them - they could've just told you to go away as you've bought a phone that's been modified and as such void its warranty. Your anger should be at the eBay seller. The fact that your phone offered an update is because all it does is check the version number with their servers - it doesn't know you on a debranded device and as such isn't their fault either.
As said on here by other you need to perform all updates in future with a gold card in the phone as the CID won't pass checks and updates will fail/install incorrectly.
Lesson learnt, I assume you managed to get the new 2.10.405.2 update OK?
Related
Hi,
I have HTC Desire that was rooted and I want to restore the ROM to factory default so I will be able to receive the FROYO OTA.
My BaseBand ver. is: 32.36.00.28U_4.06.00.02_2
Kernel ver. is: 2.6.29-82821fb5
I'll appreciate your help.
shpits said:
Hi,
I have HTC Desire that was rooted and I want to restore the ROM to factory default so I will be able to receive the FROYO OTA.
My BaseBand ver. is: 32.36.00.28U_4.06.00.02_2
Kernel ver. is: 2.6.29-82821fb5
I'll appreciate your help.
Click to expand...
Click to collapse
just flash one of the rooted ones from here
shpits said:
Hi,
I have HTC Desire that was rooted and I want to restore the ROM to factory default so I will be able to receive the FROYO OTA.
My BaseBand ver. is: 32.36.00.28U_4.06.00.02_2
Kernel ver. is: 2.6.29-82821fb5
I'll appreciate your help.
Click to expand...
Click to collapse
Put in the Goldcard and then run the official RUU (you can get one from here: http://forum.xda-developers.com/showpost.php?p=6703172&postcount=1)
It should let you install the stock 2.1. Then connect to wifi, go to settings->About Phone->System software updates and hit Check Now.
I did it that way, worked for me.
Thank you for the reply,
How can I be sure what is the ROM RUU that I need?
Hi AndroHero,
Can you please link me to the rooted versions you mentioned...
shpits said:
Thank you for the reply,
How can I be sure what is the ROM RUU that I need?
Click to expand...
Click to collapse
I used the WWE version (Link: http://shipped-roms.com/shipped/Bra...00.28U_4.06.00.02_2_release_126984_signed.exe). When i booted the 2.1 rom after going back to stock, I got options to choose the carrier so it could apply the internet and mms settings. Am on Voda UK. Didnn want to install the Voda ROM as i think voda always release the updates much later than the official releases. After setting up the 2.1, I did update and it worked.
Hi,
1. While installation i got an error message 171 (connection lost), it was waiting for the bootloader when it threw the error
2. I retried the whole process twice and the same thing happened.
Can any one assist me?
Thanks ahead.
shpits said:
Hi,
1. While installation i got an error message 171 (connection lost), it was waiting for the bootloader when it threw the error
2. I retried the whole process twice and the same thing happened.
Can any one assist me?
Thanks ahead.
Click to expand...
Click to collapse
Reboot the phone in fastboot mode, i think its press and hold the volume down button as you switch the phone on. then use volume keys to select fastboot and select it with the power button. When you leave this on there, run the RUU and it should work. WITH A GOLDCARD (IMPORTANT).
My desire is unlocked, why do I need a GOLDCARD?
I did exactly what you suggested. I moved it to fastboot but I still get the same
ERROR[171]:USB CONNECTION ERROR
This happens after the PC restart the device so it is not a 'physical Connection' issue.
I have my phone unlocked and the SIM working. From what I read, I need goldcard if I wan't to unclock my SIM...
Please advise
I successfully installed the RUU ROM, but I'm not getting the 2.2 OTA... What should I Do?
My phone is unbranded and unlocked, do I still need a gold card to restore to factory state for warranty purposes?
Sent from my HTC Desire using XDA App
If you purchased the Desire and it was on an x.xx.405.x software version then you don't need a gold card.
Don't people bother to actually absorb information as this is pretty n00b stuff...
I keep offering to help out with FAQs because this sort of information is not clearly stated. But thanks for letting me know. And I presume HTC read this forum and would know our tricks but apparently its still not a problem.
Sent from my HTC Desire using XDA App
EddyOS said:
If you purchased the Desire and it was on an x.xx.405.x software version then you don't need a gold card.
Don't people bother to actually absorb information as this is pretty n00b stuff...
Click to expand...
Click to collapse
How would anyone know what version of the software his phone had when he purchased it? I, for instance, knew nothing of the "rooting world" when I got my unbranded unlocked desire, so now, after the OTA upgrade, I don't think I can retrieve that information: am I correct?
In order to absorb information, someone has to give it to you. The process is long (for some longer maybe), but I'm sure you were a n00b once and I hope nobody treated you this way.
Luca
That is correct but if you'd read all threads/information logic would dictate that perhaps it's wise to make a note of what it comes with out the box and make sure you have a back up route in case things go pear shaped/need to be reversed. If all you've done is root the phone and not flashed a ROM then you can still check but if you're now on a custom ROM then you're kinda screwed (unless you just wanna be on an unbranded ROM then you can obviously so this).
Easy way of at least finding out if you're branded or not is to just try and flash a stock WWE RUU without a gold card - if it completes then you're unbranded
Yes, I was a n00b once (Android n00b April this year) but I didn't ask any questions - I just lurked and read other posts and learnt by others mistakes and only asked if I wasn't sure what I was doing. I've had previous mobile phones and so knew about checking version numbers so always make sure I know what I have before trying anything like rooting (or the equivalent term for other makes)
Thank you Eddie.
As a matter of fact, I haven't rooted the phone yet: still in the info gathering stage as I just purchased the phone a month ago. I come from "stupid" phones so never had this problem/opportunity before.
I know for a fact that my phone is not branded, but I don't know:
1) which is the software + radio I should download to restore my phone in case I don't like what I get with rooting;
2) which rom to install: in this specific case, the more you read, the more you get confused. I read some people installing the same rom and one saying it is slower than Luancher Pro + stock rom, others that claim that it is faster than anything they've ever tried (and, mind you, they are talking about the same rom!)
3) last but not least, all guides I found in Italian are relative to using unrevoked with windows 7, while I still run xp and it seems that xp poses some additional problems. I just created a virtual machine on my pc to start using ubuntu, but I never even seen the thing!
However, thanks for the help and sorry about being a little snappish in my previous post. I guess we all approach this problem with different attitudes: some would like it to be a real one-click easy procedure and so keep on asking until they find somebody who does it for them!
Ciao
Luca
Yeah I agree to anti-n00b remarks are getting really old. I'm sure many of us have tried searching threads and doing the right thing, so can we all just get over it? I've offered 6 times now to help create FAQs and not one of the anti-n00bs has offered to help.
Anyway, so I understand then that for those with unbranded / unlocked phones it is a simple matter to restore to factory state. Just thinking in case the USB connector broke or something, which worries me a lot because often connections are rather wobbly although I'm not sure how much that has to do with cheap cables or what.
[UPDATE] Fixed using method 2 in the link in post #4. Thanks a lot!!
Hi everyone, new to the forum and in need of some help please
I have a new Desire from T-Mobile UK. Branded and I assume locked, not rooted.
I attempted to debrand my phone by doing the following.
1. I already had Android SDK and HTC Sync.
2. I made a GoldCard following the unlockr instructions "how-to-create-a-goldcard" (not allowed to post link as am new forum user).
3. I ran an RRU from the pinned ROMS topic in this forum, which was RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.exe
The flash completed with no errors.
Afterwards, the phone appears to boot up but the screen remains completely black at all times. I have tried everything I can think of, and have seen absolutely nothing on the screen at all since flashing. Pure black not even backlight.
What I have observed is:
1. On power-up, the vibration and welcome sound.
2. The hardware buttons illuminate. They time out and go off, and they illuminate again when pressed.
3. On inserting a freshly formatted SD card and turning on, waiting ages, turning off (remove battery), removing card, then viewing in a card reader, Android has added some folders to the card (.footprints, LOST.DIR, rssreader) so obviously it is booting up to some degree.
4. On attempting to flash another ROM, the tool reports the "From image version" to be 1.21.405.2 which is the one I flashed earlier, not the phone's original version.
5. Phone no longer shows up in "adb devices" when connected, although this may be simply because USB debugging isn't enabled, or because the phone will be at its start-up introduction screens.
6. There is network activity after a while, indicated by the interference on my PC's speakers.
What I have tried to do to fix:
1. Numerous reboots removing battery, SD, SIM etc.
2. Flashed the WWE 1.21 ROM again, which succeeded, but didn't fix the problem.
3. Attempted to flash the WWE 1.15 ROM RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704.exe which failed with "ERROR [140]: BOOTLOADER VERSION ERROR. The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."
4. Attempted to flash the T-Mobile 1.5 ROM RUU_Bravo_TMO_UK_1.15.110.11_Radio_32.30.00.28U_4.05.00.11_release_122755.exe which failed with the same error.
5. Flashed the T-mobile 1.21 ROM, which succeeded, but didn't fix the problem, and has made it slightly worse in that I don't get the welcome sound at power-on any more. I still get the vibration, the lights, the network activity, and the black screen.
6. Tried with another SD card, no difference.
Before I started debranding at all, I took a photo of the software versions screen as supplied by t-mobile, which showed as follows.
Firmware version: 2.1-update1
Baseband version: 32.41.00.32U_4.08.00.09
Kernel version
2.6.29-3cb3dfbf
htc-kernel{at}and18-2 #1
Build number 1.15.110.11 CL155070 release-keys
Software number: 1.15.110.11
Browser version: WebKit 3.1
(replace {at} with the email at symbol, new forum members aren't allowed to post these)
So in summary, I probably have the WWE 1.21 ROM working on my phone, but the screen doesn't work so I can't see it, and re-flashing doesn't work so I can't try a different ROM.
I'm a noob to debranding but am a programmer and Android app developer so feel free to get a little bit technical
Any help you can give is greatly appreciated! Hopefully I won't have to explain this to the T-Mobile support people!
Thanks!
Hi. Sorry to hear you having trouble, I'm not too sure. But sounds to me like its a display issue? You may have a Desire with the new cheaper display, not a amoled.screen? Think I remember reading in the forums blank screens and issues with roms. (please check other treads)
The good news is I think its recoverable. Sorry. I can't be of mote help.
Sent from my HTC Desire using XDA App
Thanks for the reply,
I had a better search around and found showthread.php?t=747393 which describes apparently the same problem, although I haven't messed with bootloaders. It was fixed by installing the OTA update blind by pressing buttons in the right order.
It is indeed possible I have a different screen type, or perhaps a different model of AMOLED, does anyone know how to tell the difference? I do notice the screen is more reflective than my G1, which I think is associated with AMOLEDs, but that might just be down to 2 yrs of wear and tear.
Anyway, I will try it now let you know how I get on!
Thanks!
As above you have a Desire with an SLCD screen.
You will have a HBOOT of 0.83 or 0.92 - You need a rooting and/or debranding guide for those HBOOTs. The current guides only work for HBOOT 0.80 and lower.
Here is your fix for your current problem: http://forum.xda-developers.com/showthread.php?t=748498&highlight=brick+fix+SLCD
I couldn't get the pressing buttons blindly method to work, but method 2 from dickenz's link worked a treat.
It gave me WWE Android 2.1, and I immediately got the OTA update to Froyo, WOOHOO!
Can I suggest we create a section in the pinned ROM topic listing RRUs and OTAs compatible with the new screens? That'll make it more obvious to new visitors.
Thanks for your help both of you, I'll stay around the forums!
Hi,
I really hope someone is able to help me out - i cannot use my desire......
Since i bought my desire it has been unable to install the OTA updates. It always fails during the installation which has been really anoying since i really want to upgrade the system.
That caused me to start playing around, trying to upgrade using update.zip files with different versions. That unfortunately didn't work, usually with a message:
-------------------
Installing update…
assert failed: file_getprop(“/system/build.prop”, “ro.build.fingerprint”) == “htc_wwe/htc_bravo/bravo/bravo:2.1-update1/ERE27/174215:user/release-keys” || file_getprop(“/system/build.prop”, “ro.build.fingerprint”) == “htc_wwe/htc_bravo/bravo/bravo:2.2/FRF91/218634:user/release-keys”
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
-------------------
Investigating the installed system on my desire I found that my version of the build.prop was containing bravo:2.1-update1/ERE27/155070, eg. probably not compatible with any of the supported versions in the assert message above.
So... I tried installing via RUU files, but this has caused my phone to be stuck on the green HTC logo!
The RUU files i tried was:
1) RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704.exe
then (when the above didnt work):
2) RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed.exe
I can still boot in HBOOT and i can still install RUUs, but nothing seems to work...
One more thing... My phone is an unbranded phone...
Please (!!!) help... I'm completely lost at this point!
- Zyb3r
Put your phone into fastboot mode by starting with back key + power button. Then run the Froyo RUU above.
teppic74 said:
Put your phone into fastboot mode by starting with back key + power button. Then run the Froyo RUU above.
Click to expand...
Click to collapse
trying now... i chose fastboot on the Desire, then on pc clicked the exe.
It shows:
From version: 2.09.405.8
To version: 2.09.405.8
Clicking next.... waiting...
Now says Congrats...
Then restarts... green update icon appears on phone... restarts again but then shows the Green HTC logo. (
Is your phone NOT branded or DEbranded?
Try installing an RUU using a goldcard.
Was your phone unbranded from the start?
EddyOS said:
Was your phone unbranded from the start?
Click to expand...
Click to collapse
Hi,
Thanks for the quick replies...
Yes, it's never been branded. I bought it and have always been able to use any kind of simcard in the phone == unbranded i guess...
Regarding the goldcards... Isn't that only for branded/simlocked phones?
Thx!
Zyb3r said:
Regarding the goldcards... Isn't that only for branded/simlocked phones?
Click to expand...
Click to collapse
I have a debranded phone. I can update OTA only by having a goldcard inserted or else i get problems and restarts. Are you sure yours is not debranded? Also branded does not always mean locked. It just have personalized firmware.
bluesax said:
I have a debranded phone. I can update OTA only by having a goldcard inserted or else i get problems and restarts. Are you sure yours is not debranded? Also branded does not always mean locked. It just have personalized firmware.
Click to expand...
Click to collapse
Ok, I cannot be sure. At the store i guess they could have debranded it, but I've always been able to use any kind of simcard.
Hmm, how can I tell if it's branded or not?
Just cause you can use any SIM card doesn't mean it's not branded - Vodafone Desires are SIM unlocked but are still branded in terms of not having the same product code (e.g. 2.10.161.2 as opposed 2.10.405.2)
I don't think there is a way to see if it was originally branded, but usually debranded phones have problems with OTA updates. In any case just make a goldcard and retry installing the RUU. Another thing: for how long have you waited on the HTC green logo screen? Sometimes updating takes very long time.
EddyOS said:
Just cause you can use any SIM card doesn't mean it's not branded - Vodafone Desires are SIM unlocked but are still branded in terms of not having the same product code (e.g. 2.10.161.2 as opposed 2.10.405.2)
Click to expand...
Click to collapse
Ok, so what do I do?
Before flashing with RUU files I could see my versions being:
1.15.405.4
and Radio:
4.05.00
Only thing that i found kinda odd was the "bravo:2.1-update1/ERE27/155070" that I found in my build.prop. Could that be a branded version of something...?
Even if i get a goldcard i guess i still have to find the right RUU file?
bluesax said:
I don't think there is a way to see if it was originally branded, but usually debranded phones have problems with OTA updates. In any case just make a goldcard and retry installing the RUU. Another thing: for how long have you waited on the HTC green logo screen? Sometimes updating takes very long time.
Click to expand...
Click to collapse
Could be an idea... But dont i still have to use the right RUU file (that matches my "brand"?
Where's the best guide for creating Gold cards?
Zyb3r said:
Could be an idea... But dont i still have to use the right RUU file (that matches my "brand"?
Where's the best guide for creating Gold cards?
Click to expand...
Click to collapse
No, with a goldcard you just use whatever RUU you like.
Take a look here
or use Goldcard tool
bluesax said:
No, with a goldcard you just use whatever RUU you like.
Take a look here
or use Goldcard tool
Click to expand...
Click to collapse
Ok, I'll go get a MicroSD card reader and a spare MicroSD card now (YES... It's that important)..
I'll be back in a jiffy...
One more thing. I've used whatever installer that comes with the exe files, but it doesn't allow me to go back from the Froyo version I've installed. Can i just apply the same file again with the exe installer or do I need to do something else once i have the goldcard?
The one i installed: http://shipped-roms.com/shipped/Bra...3.00.32U_5.09.00.20_release_140022_signed.exe
Thanks for all your help so far!
Here there are instructions for downgrading but in any case you need a goldcard. Better try applying the same file again. Again, are you sure you waited enough on green HTC icon?
How are you checking the build.prop on a stock ROM? You can't see any of that if updating via an RUU
bluesax said:
Here there are instructions for downgrading but in any case you need a goldcard. Better try applying the same file again. Again, are you sure you waited enough on green HTC icon?
Click to expand...
Click to collapse
I waited for several minutes ... nothing happend...
EddyOS said:
How are you checking the build.prop on a stock ROM? You can't see any of that if updating via an RUU
Click to expand...
Click to collapse
I mean... Via the ASTRO file manager i checked the /system/build.prop of the already system before updating. That was an attempt to troubleshoot the reason for getting the error message "assert..." (see first post). That error message referred to the reason not being able to install the update.zip (before i started playing with RUU files) -> being that my system/build.prop contained a version not compatible with the one in the update.zip.... I hope i'm making sense
Anyways... off to buy a new microSD. Will a MicroSDHC card work ok?
ERE27 is Android 2.1 so that's right, it should update to show FRF91 once running 2.2
I'd follow this guide to get back to stock:
http://forum.xda-developers.com/showthread.php?t=768256
And then look to root after wards...if it doesn't work (CID error or something) then you'll need a goldcard and you have a 'branded' Desire
Zyb3r said:
I waited for several minutes ... nothing happend...
Click to expand...
Click to collapse
IMO several minutes are not enough... try waiting for over half an hour.
Hello
Few days ago I was prompted to install update 2.10.405.2. After the installation I can't enable wifi anymore; it simply says error. I just got my phone 2 weeks ago on an Orange contract (from mobiles.co.uk), but when I contacted HTC they said that my phone should be a branded and locked O2 Desire. HTC said that because my phone was unbranded the update messed my phone. Is that possible?
I noticed that quite a few people are affected by this, but the guy from HTC wouldn't say if they are aware of this problem or if they are working on a fix. They "escalated" the call but haven't contacted me back yet.
Is there a way to simply uninstall the update?
I read this post http://forum.xda-developers.com/showthread.php?t=779787 but I wouldn't want to downgrade to 2.1 (I just got this phone 2 weeks ago, plus this is my first Android so...) wouldn't that invalidate my warranty ?
Please advise,
Thanks
If your Desire was a previously branded handset then you need your gold card in the unit for ALL updates. This is why the handset is having issues...
I didn't know that.
Why was I given a previously branded phone in the first place, if this could cause problems like this?
Anyway, I made my main microSD card a gold card now... for future updates. Does this gold card just needs to be in the device when you update, or you need to do something else as well ?
Is there a way to simply uninstall this bloody update?
You just need the gold card in the unit...Don't suppose you happen to know the software version that was on the unit when you got it do you?
Unfortunately no. But this was the first and only update that I got, if that helps.
Same issue here, is a hard reset/reflash the only solution? I'd rather not lose my files and stuff, ofcourse.
It would be either 1.21.405.2 or 2.09.405.8 I'd imagine...
CPW own mobiles.co.uk so it should've been an unbranded device - mine was from a CPW store and was unbranded - so it may have not been a branded unit. Follow this guide and if it completes with no issues you're on an unbranded unit (it will roll you back to Android 2.1 and you can then flash the Android 2.2 RUU file directly (or try the OTA update again)*
http://forum.xda-developers.com/showthread.php?t=768256
* You will lose all data, mind, so backup what you need before doing this
Will this invalidate my warranty?
I also contacted mobiles.co.uk (as HTC suggested) to ask them why on HTC database my phone apears as a branded O2 phone, but still got no answer from them. You are saying that it should have been an unbranded Desire ?
No it won't, if it completes then you've got a generic Desire and that guide puts you back to stock 2.1...you can then update again to 2.2 and HTC won't know a thing...
I'm saying it should have been an unbranded Desire going from my experience of CPW - that's not to say EVERY Desire will be unbranded as it depends where they got the stock from
Quote from post : [HOWTO] Downgrade Froyo (2.2) to Stock 2.1 (ANY HBOOT | WIN/LINUX/MAC | ROOT)
"Further Information
If you want to flash an alternative RUU (e.g. a branded 2.1 release), just skip the downgrade section at the end by pressing vol-down on the phone when the utility has completed. Then reboot the phone and run the RUU you want. If you have an SLCD screen you should be very careful here - most RUUs don't support the screen."
Question: Do I need to skip the downgrade?
My model number is HTC Desire A8181 - is this with SLCD screen?
I have downloaded RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.00.32U_5.09.05.30_2_release_142828_signed.exe
Is this ok to flash after this process?
Sorry, I am a novice (got the phone 2 weeks ago) and did not expect to bump into problems like this so early.
Please help, I wouldn't want to brick my phone.
The guide downgrades you to the stock 1.21.405.2 ROM which is fine for SLCD screens. You can then either use that RUU or just do the OTA update again - whichever you prefer (personally, I use the RUU)
There should be no issues if you follow the guide to the letter
Other thing to try first, though, is a hard reset - it might fix it for you
Just did a hard-reset. It didn't help. Will try downgrading and let you know how it went.
I did the downgrade and now the wireless is working again )
I'm flashing that RUU now
Thanks so much EddyOS
No worries matey, just keep the gold card in the phone and you shouldn't have issue in future
I had the same problem.
No WiFi and hotspot after ota.
This because i forgot to put in my goldcard...
Easiest way to fix it is to make a goldcard, then get the .zip file from the 2.10.405.2 update and place it on the goldcard.
Rename it update.zip.
Put the goldcard in your phone.
Then enter recovery mode (reboot your phone, when turning on hold the lock button and volume down button)
Select recovery in the menu you get, then wait, after a while it shows you a few options. Choose the option to run the update.zip.
Done, everything works perfectly.
Its really easy, only making the goldcard out of an SD requires a little searching/reading.
Good luck!
Edit: forgot to say it doesnt erase any data, like apps and contacts.
Just be sure if you use your current SD card as goldcard to copy everything to your pc before making it. Then you can put it back later on.
Finaly back to the latest 2.2 Android. Updated using OTA.
Tried updating with RUU but for some reason after the RUU rebooted the phone to start the update, the phone got stuck on the HTC screen and the RUU timed out; tried it several times.
But I'm back on track now.
Will keep the goldcard in at all times. Lesson learned the hard way.
DaannRoz - unfortunately I already did the hard-reset...
Thanks everybody.
Thanks DaannRoz
I put a new 16gb into my phone a while back and put it through the gold card process so I thought it should work. It didnt and I got the Wifi error code. I put the original gold card in and went through the steps you provided and got my Wifi back. It saved me from reflashing the phone and wiping out all my apps and data.
I anyone gets a picture of a phone with a red triangle and a apostrophe in it you need to push and hold the volume key up and then press the power button to get to the rom select screen.
Thanks Daan..
Just stuffed my Desire. Will try the update via recovery @ home.
BTW is this the update you want me to do ??
http: / / fotadl.htc.com/OTA_Bravo_HTC_EU_2.10.405.2-2.09.405.8_releaseol2djq7rqarka2ka.zip[/url]
Cheers,
Sai
Thanks Daan...now my Wifi works...
@Sai> I used the link provided by you..thnx.. (Hope its an original one!!!)
saro
I got the same issue. After reapplying the update with an update.zip and the recovery mode --with gold card inside at this moment-- everything goes fine and my WiFi works again...
Hi all, would like to know if, after installing a custom ROM, if i use a RUU will the recovery image be restored to default?
Thanks in advance!
Yes it Will
Yay! thank you! so just using the RUUs i will totally reset my desire, so HTC won't be able to tell if it's been rooted before?
Don't know whether they can't tell, whether they look if they've no need to I don't know...so long as it's on a stock ROM I don't think they'd check
lambdafreak said:
Hi all, would like to know if, after installing a custom ROM, if i use a RUU will the recovery image be restored to default?
Thanks in advance!
Click to expand...
Click to collapse
What is a RUU and how can I do it, as I'm having the same problem.
I rooted to allow Titanium Backup to have root after using unrevoked but wasn’t aware that meant I also had a custom rom installed now.
I’ve been told I need to RUU as well.
RUU = ROM Upgrade Utility
It's the official way of flashing a ROM. Each phone has a software version running on it when you first get it and you should make a note of the one on yours before doing anything root-related for the very reason that if something goes wrong you can revert back to stock. Not all versions are available, e.g. there are no Orange RUUs about, but the ones that are can be found here:
http://shipped-roms.com/index.php?category=android&model=Bravo
If you didn't happen to make a note of yours then it's hard to say what it came with. If you've only rooted and NOT flashed a new ROM yet then if you go to Settings>About phone>Software information and post the software version we might be able to help
Thanks for all the information it helps fill in some blanks.
I dont think I have put a different rom on it, I only rooted using revoked- does that mean it has a different rom now?
and my settings show
Android 2.2
Baseband version 32.46.00.32U_5.10.05.17_2
Kernel version 2.6.32.15-gd96f2c0 [email protected] #1
Build number 2.12.110.2 CL232610 release-keys
Software number 2.12.110.2
on a side note the link you posted - what do the numbers correspond to, my Kernel or build
Right you're on a T-Mobile FroYo ROM but the issue is there isn't that versions RUU available...how long have you had your Desire?
Damm.
I got mine in April this year, why do you ask.
Can I not use RUU_Bravo_Froyo_TMO_AT_2.12.112.1_Radio_32.46.00.32U_5.10.05.17_2_release_143754_signed.exe?
You CAN use that but it's the Austrian one...the reason I ask is to find out the screen type, you should be on an AMOLED screen so you can flash the older 1.21.110.4 RUU if you need to - you'll need a gold card to do it, though, I believe
http://shipped-roms.com/download.ph...00.28U_4.06.00.02_2_release_127570_signed.exe
If I do flash the older 1.21.110.4 version, are there any drawbacks, or will I just be able to update through OTA updates that will then be available to me through T-mobile to get me back to normal?
Also is there a best way to do this RUU as I have seen a few guides, can you recommend any to follow.
The way I'd do it is:
1. Download that RUU
2. Have gold card in your phone and HTC Sync installed on your PC
3. Connect phone to PC and select 'HTC Sync' from the options on the phone
4. Once HTC Sync on the PC shows connected, run the RUU
5. All being correct it'll flash the ROM
6. Assuming it's worked, you should get the OTA updates again as you did before
Replying on here and androidforums is getting confusing!!!
Thanks for all the help and I hope those instructions were meant for me and not some one else
Maybe you have to downgrade your hboot to 0.75.
Sent from my HTC Desire using newest version of swype and the XDA App
digo21 said:
Thanks for all the help and I hope those instructions were meant for me and not some one else
Click to expand...
Click to collapse
Yes they're for you but there's someone on androidforums with EXACTLY the same issue - you sure you're not the same person??
Nope thats not me
I followed all the procedures. But the RUU gave me an error after a few minutes saying 'Error 140 Bootloader version error'.
What does that mean and how can I fix it.
Which RUU are you trying to use? And which HBOOT are you on now?
Im trying to use the one you recommended above RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed.exe
Bootloader version I found out by holding the back key and power button to swithc on, it says HBOOT - 0.93.0001