Related
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
I've downloaded an HTC Europe 1.15 RRU that I used before and worked.
Now, however, it wont flash. I just get to the "waiting for bootloader" and then a "connection error". I tried rebooting into bootloader but then the RRU just counts upto 100 and then tells me there is a connection error.
The difference between now and last time is that I've updated my bootloader to Alpha-Rev bootloader and Clockwork Mod Recovery is installed. The phone is rooted and S-OFF as well.
I'm trying to restore the phone to factory condition in preparation for a return to HTC for repair.
I guess I need to resintall some bootloader and recovery mod?? or is that in the RUU?
Any ideas/advice?
Android version 2.2
Baseband 32.47.00.32U_5.10.05.23
Kernel 2.6.32.15-gf5a401c
Build 2.29.405.2 CL263770 release-keys
Software: DJ Droid v1.8 (but also tried latest MoDaco, Pinky, CM6 and LeeDroid)
Browser: WebKit 3.1
HBOOT 0.93.0001
BRAVO PVT3 SHIP S-OFF
MICROP-051d
TOUCH PANEL-SYNW0101
Clockwork Recovery v2.5.0.7
Why do you want to put the FIRST ever RUU back onto your device? Just download the latest RUU (2.29.405.2) by clicking on my signature. This is assuming your phone in unbranded from the start, if not you'll need to get the RUU for your operator
Er, because I said ...
"I'm trying to restore the phone to factory condition in preparation for a return to HTC for repair"
Factory condition means ANY ROM that was meant for the unit - you don't need to go back to the first!!! So long as you're on an x.xx.405.x ROM you'll be fine!!! LMAO!!!
If you just flash the 2.29.405.2 RUU then you're back to stock so the factory will accept it
bloody hell.
saved me a ****ty weekend there pal.
nice1
cheers
will do this tonight and report back.
My HBOOT is 0.93.001 (flashed using alpha-rev clockword mod install utility). Some older RUUs refuse to load (waiting for bootloader and a reboot to bootloader whilst the RRU is still running - doesnt fix the problem). Appears to be waiting for a special signature from the bootloader. Is your link (RRU) likely to work do youo know ??
If you're currently S-OFF, which I assume you are, then get this file instead:
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.zip
It's the same RUU but in ZIP form. Once downloaded remove everything from the name except PB99IMG (so the file is effectively called PB99IMG.zip) and copy it to the root of your SD card. Then boot into HBOOT and it will read the ZIP and ask you to continue. Say yes and once done reboot and you'll be back to stock. Then just remove the ZIP from the SD card and away you go!
Word of advice: I was S-OFF and using the N1Table and the first time I ran this it failed on the System partition and got stuck on the white HTC screen. I left it an hour, ran the PB99IMG again and it completed so if you are on anything other than the stock table I'd go back to that first using the file from AlphaRev before running the ZIP
Either way you should be fine
Yeah S-OFF.
I'm okay with the PB99 - used that when creating gold card and downgrading.
The N1Table stuf is new to me. I'll google that now.
Thanks for the tip and link.
Cheers pal.
**EDIT:
Okay, so N1table is the partition table for sram/nvram chips.
I have not knowingly modified these, but in any event will grab
the stock HTC table just in case. I can only assume the hangup
is generated because the partition table is hardcoded in the RRU
rather than being read in by the RRU - or something like that.
Anyway, thanks once again pal.
[Q] The phone was purchased on the UK Orange network although no branding on the phone (orange square logo and orange applications). The phone was locked to the Orange network and the settings SLIGHTLY different than the unbranded phone my bro has. Will I need to get hold of the Orange RRU before sending to HTC for repair (as in will the IMEI number be registered to Orange or something)?
If it had the Orange ROM on it then you will need that before sending it back...now, an Orange RUU has never surfaced BUT I might know someone getting one today so if I hear anything I'll post back on here.
If you needed a gold card to flash the stock RUU then you will need the Orange RUU
With regards to S-OFF, unless you downloaded and flashed a new table you will still be on the stock Desire one
I used alpha-rev' s-off utility (cant recall the link and didnt save it) but unsure whether the table has been modified. I'll just download the HTC one. Simples.
DAMM. I thought I may need the Orange RUU. Yes, the stock RRU wouldnt install I recall; required a gold card and a bootloader downgrade as I remember. ****!
I've been searching for Orange RUU for months to no avail.
As I said, hold out a day or so as I think someone might be getting it from Orange
Leave it with me...
Acknowledged
My gracious thanks in advance.
Good luck!
Eddy if you get a stock Orange RUU you will be god . Hope you get it.
Sent from my HTC Desire using XDA App
It won't be me but apparently someone is getting an Orange techie to debrand his phone and he's getting the RUU in case he needs to go back to stock...as soon as I hear something I'll update
ste1164 said:
Eddy if you get a stock Orange RUU you will be god . Hope you get it.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
+1 for Eddy being God
EddyOS said:
It won't be me but apparently someone is getting an Orange techie to debrand his phone and he's getting the RUU in case he needs to go back to stock...as soon as I hear something I'll update
Click to expand...
Click to collapse
Hang on; dya mean its possible to create an RUU or backup of a branded Orange phone - as indeed I had before I rooted et.al. ? Oh no, could I have created one - surely not ?
EddyOS said:
If you're currently S-OFF, which I assume you are, then get this file instead:
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.zip
It's the same RUU but in ZIP form. Once downloaded remove everything from the name except PB99IMG (so the file is effectively called PB99IMG.zip) and copy it to the root of your SD card. Then boot into HBOOT and it will read the ZIP and ask you to continue. Say yes and once done reboot and you'll be back to stock. Then just remove the ZIP from the SD card and away you go!
Word of advice: I was S-OFF and using the N1Table and the first time I ran this it failed on the System partition and got stuck on the white HTC screen. I left it an hour, ran the PB99IMG again and it completed so if you are on anything other than the stock table I'd go back to that first using the file from AlphaRev before running the ZIP
Either way you should be fine
Click to expand...
Click to collapse
Nice1 Eddy. The ZIP did the trick. The RRU method didnt work but I expected that as it was looking for an original HBOOT signature.
So, back to HTC stock. Not sure whether they would accept it for repair though given that it was sold as a branded Orange handset. Can they check?
Well, I will give this a go. The reason for the repair is that I've installed god knows how many custom ROMs and:
1. wifi doesnt always work.
2. Data connection errors.
3. Random reboots.
4. 90% reboot when navigating in the car.
5. Failure to answer some incoming calls.
6. Sometimes outgoing calls carry no voice modulation (they cant hear me)
different problems depending on ROMs.
So, lets see how the stock does before I decide to send back/or not.
Thanks again Eddy.
No, the bloke at Orange is going to give the guy getting it debranded the Orange RUU so he can go back to stock if he needs to...
HTC can tell, and my still fix it and put the Orange ROM back on it, but they may also turn around and refuse to fix it due to having a different ROM to the original
You can get to stock Orange with a very complicated method. After debranding you would root the phone. Then apply the backup on my thread. You then remove the superuser.apk with adb. You then flash the two updates orange released this unroots your phone back to stock.
Sent from my HTC Desire using XDA App
Nice1 Ste, however, mine is SLCD not Amoled. The nandroid is from an Amoled handset. Wont work with mine. Nice idea tho.
Anyone have a nandroid from an Orange set??
I'm getting this on my debranded/rooted desire whenever I try to flash back to stock. I used to be able to do it but recently it's started saying this, any idea why?
Thanks
What ROM are you flashing?
I'm trying to flash back to the latest RUU 2.29.405.5.
CID error means you'll need a gold card
I think I used a goldcard to debrand ages ago but I can't remember how to do it, is it easy?
http://android.modaco.com/content/software/308798/pc-application-goldcardtool/
Give that a bash, you may need to register to get the attachment. Your gold card will be needed for ALL updates back to stock so make your day to day card the gold card and leave it in the phone
Sorted thanks mate! Is it worth making a nandroid backup if things go wrong again?
Yes but it will only go back to the rooted ROM. Keep the RUU safe and you can go back to stock if you need to (would've been best to have the actual original RUU for your phone for warranty purposes but meh)
My phone was o2 branded i'm sure there's an RUU about somewhere!
Here, to be exact:
http://shipped-roms.com/download.ph...00.32U_5.09.05.30_2_release_144166_signed.exe
Right, I have a slight issue.... my wifes phone is playing up at the moment ... the dreaded reboot issue when ever you do more than make a call, so I need to send the phone back to HTC.
The problem ...
I don't have my gold card anymore ... it was on my desk and the cat must have eaten it! I have tried unrooting without and it stops with an incorrect bootloader message (or something along those lines)
I have managed to boot back into Android after clearing all data (via the bootloader), am I ok in creating a goldcard even though I am on a custom ROM and not stock?
Did try Googling but got mixed messages .... not all relating to the Desire either.
Anyone tried unrooting an O2 Desire yet? If so what RUU did you use?
Thanks in advance
Doesn't matter what ROM you are on, you can even create a goldcard without your phone if necessary.
Be careful which RUU you choose, as some of the older ones can cause an SLCD brick (depending on which screen you have).
I'm not sure about the situation with O2, but I debranded my Orange phone with the latest stock RUU as there have been no Orange RUU leaks.
Thank you,
Hopefully that will work, it is going back to HTC not O2, so will probably go for the latest stock RUU (and hopefully the goldcard will work!!)
The bootloader is dated Aug 10 from memory so fairly new and still falls under HTC warranty.
Will post a few more details about the bootloader version later.
Thanks again.
matt.xx said:
Doesn't matter what ROM you are on, you can even create a goldcard without your phone if necessary.
Be careful which RUU you choose, as some of the older ones can cause an SLCD brick (depending on which screen you have).
I'm not sure about the situation with O2, but I debranded my Orange phone with the latest stock RUU as there have been no Orange RUU leaks.
Click to expand...
Click to collapse
Hello guys,
I purchased a second hand HTC One M8 which has been converted to GPE, unlocked bootloader and S-OFF. The phone is currently locked to the Vodafone network, so I assume it was previously a Vodafone branded device.
Now I need to get this phone unlocked because Im with another netowork, so I purchased an unlock code online which failed (they have always worked in the past). I got a refund from the seller and was told to try a different seller. Purchased a new one but it turned out to be the same code. I told the seller my story and was told I need to make sure I am on the latest official stock ROM. Maybe the previous owner entered an incorrect code too many times and disabled this whole thing altogether? I dont know.
Im not sure how a stock ROM would make a difference, but the phone is useless to me being locked to Vodafone so I guess its worth a try. Now heres where I need your help because Im a Nexus user so Im not too familiar with all these CIDS, MIDS, etc.
I have changed my CID to superCID, do I now just flash the Vodafone RUU? Or do I need to take further steps? I dont really need to change the MID aswell do I? I will not be staying on stock, I will most likely be returing to GPE or some AOSP ROM and I'd like to keep the bootloader unlocked and S-OFF.
Also are there any other methods to get this SIM unlocked? I have read the thread about using a generated dat file, but read that no longer works.
Thanks.
Follow the 'back to sense' thread in general first, then set CID to the Vodafone one, I assume UK), then flash the RUU
Hi,
Thanks. Is this the thread you are referring to?
I thought I could flash any RUU with superCID which is why I changed to that, but no problem I'll just change it over to Vodafone to be safe, it is VODAP001 for the UK version I believe.
You can use the unbranded EU RUU if you prefer, it's up to you
And yes, that thread
No what I meant was I thought I should be able to flash the Vodafone RUU using superCID without having to change to the Vodafone one...but nevermind I changed it over anyway.
But Im having some problems with this actually. I downloaded what I thought to be the Vodafone ROM from the HTC dev site, the file name is m8ul-3.4.0-g3c7a5c1.zip, I follwed the steps laid out in the going back to sense thread but I get an error message '24 parsing android-info fail', tried a few times as mentioned in the thread but same thing happens.
I then located a Vodafone RUU exe in this thread. That failed to even run as confirmed by another member, something to do with InstallScript.
So then I tried flashing the previous zip file with the htc_fastboot that you provided in the same thread, same error as before.
Any suggestions? Or do you know if there is a working Vodafone RUU available anywhere?
The file on HTC Dev is the kernel source, which is why that hadn't worked.
As for the RUU, it looks like it could be corrupt.
You first have to flash that ZIP in the back to sense thread to get the partitions corrected and then you can flash an RUU. I'd just use the EU one as (for a start) it works and it means you don't have all the carrier rubbish
Oh ok, I didnt realise I had to flash that before flashing an RUU, I just thought flashing any RUU would sort out the partitions.
I'll go ahead and flash the zip file and the EU RUU as I am unable to find a Vodafone one. But Im really not too bothered about the carrier crap anyway because as I say the only reason for going back to stock is to try and SIM unlock the device, and if doing that will really make a difference then it would most likely do it on the stock Vodafone ROM, but I dont know I could be wrong.
I'll let you know how I get on.
You can SIM unlock it regardless of ROM. Some people say flashing the RUU will sort everything out but, in my experience, I've had to flash the first ZIP and then the RUU to get it all working properly
Thats what I thought but it didnt work. The unlock code provider then told me to make sure I am on official stock ROM which is why Im trying to get the Vodafone ROM loaded on this phone. As Ive said I dont know how much of a difference it will make if any, but it is worth a try I suppose.
Anyway Ive had some problems flashing the EU RUU, I followed the guide and flashed the firmware zip which went all fine. Then I flashed the EU RUU provided in your guide, but it kept giving me errors towards the end - 51 partition update fail. Downloaded another RUU which gave me the same error, tried an RUU exe which also failed. Tried flashing a different firmware but I cant remember if it failed at that stage or at the RUU stage. Then I thought maybe the firmware is an old version from Kit Kat. I felt as if I didnt know what I was doing and should give up!
I then came across this thread and that person was doing it through TWRP backups which I thought I should maybe try. But I dont know Ive been at this for hours and currently without a ROM or recovery! I think Im gonna flash back to GPE until I know what to do.