Develop Bugs

[Q] Desire keeps crashing, Rollback to stock condition.

Hi,
I have tried several ROMs on my desire but none of them is working perfectly.
The only rom that somehow makes it possible to work is dj-droid
Leedroid and Chinese rom kept on crashing
The phone keeps crashing if I use it to much. (run a demanding app like waze or o game)
It even crashed when I use the internet for too long.
All of this made me come to a conclusion that there is something wrong with the hardware (feel free to correct me if I’m wrong)
Now I want to get my phone to his stock condition.
I know that I need to download something called a RUU file.
I found this thread, but I can’t figure which ROM should I D\L.
I suppose it should be something marked as WWE and the numbers are the radio version.
From what I can see my radio version is 32.44.00.32U_5.09.05.30_2 (found in setting-> about phone -> Software information Baseband version) is it really the radio or I’m looking at the wrong place?
Can I use any RUU file is there a specific RUU should I D\L because in the thread I found the highs radio version is 32.30.00. If I need a specific ROM can some please point to the right direction.
Also I’ll be happy is some will explain to me what are the steps to install the RUU file, or is it same thing as installing a custom ROM ?
Please feel free to throw any other suggestions that might help to set my desire to it’s proper condition.
Thank in advance
Mark
P.S
I had froyo 2.2 and my HBOOT is 0.93.001

In order to return to stock, just connect the phone to the pc and run the RUU (it's just an exe file). The latest OFFICIAL European rom is here:
http://forum.xda-developers.com/showthread.php?t=828519
That will upgrade HBOOT and Radio, you really need that. In case you'll need to get root access, just download unrevoked (google it), but remember to uninstall HTC Sync in case you have it installed before running it.
After rooting, just reflash the rom of your choice and keep the new radio, just don't change it, it's superb.
Hint: before flashing any rom on top of each other, remember to wipe cache, dalvik cache, and user data, so you won't get any crash.
To restore data I suggest MyBackup Pro, gives less issues than Titanium Backup.

You need a gold card to flash anything other than the one that originally came with the phone. Radio is irrelevent

EddyOS said:
You need a gold card to flash anything other than the one that originally came with the phone. Radio is irrelevent
Click to expand...
Click to collapse
Radio is responsible of many crashes: an old radio not compatible with the camera app gives FCs.
Why would he need a goldcard if he already rooted?? To go back to stock just enter in the bootloader, select fastboot, connect via usb, start the RUU and you're done.

Thanks,
I'll try the attched RUU and update with the result.
BTW
is the there posibility i'll brik my phone during this procedure ?
Oh and i anderstand that i need a goldcard only if my phone is/was branded.

Ok, I managed to restore the phone but after the installation it entered to a boot loop.
I let the phone rest for 2 or 3 minutes and it started up perfectly.
I suspect that if I'll stress my it's get too hot and crushes.
Any suggestion how can I confirm this theory ?

How did you get it out that boot loop? Resting? Did you take out the battery or smth?

Yes,
I had to to that several time before the phone started to work.

DomFel said:
Radio is responsible of many crashes: an old radio not compatible with the camera app gives FCs.
Why would he need a goldcard if he already rooted?? To go back to stock just enter in the bootloader, select fastboot, connect via usb, start the RUU and you're done.
Click to expand...
Click to collapse
If the OP has a branded phone and wants to flash a stock unbranded RUU you need a gold card. Radio is irrelevent in the flashing of an RUU as you get the correct radio for the ROM included in it

I am just asking because I am trying to flash the Rooted , A2SD+ version of this ROM and after flash it just keeps looping (when the little green android logo appears and the phone vibrates) and does that on and on and on. Maybe I have to wait more.

Which ROM have you come from? IF it wasn't a Sense-based ROM you'll have to do a full wipe before booting

EddyOS said:
Which ROM have you come from? IF it wasn't a Sense-based ROM you'll have to do a full wipe before booting
Click to expand...
Click to collapse
I came from exactly this one (latest OTA). It was rooted and as clockwork recovery did not work , I flashed Amonra. I did a full wipe, I formatted the SD card and then partitioned it, I did everything from scrap. I am almost certain I am missing astep or smth. Phone shows S-ON, maybe amonra doesnt get read of Security...?? I am not very good at this stuff, but any other ROM I flash works, except for the latest OTA (rooted and with A2SD- there is a post here on the forum containing it).
OR you mean a full wipe AFTER flashing, and before the first boot??

Chapter 2 – Return of the Desire
Hi again
First of all I want to thank you all for your assistance I had no problem to activate the warranty.
It seems that the constant reboot issue was a know issue of the A8181 series so my original phone was sent to HTC.
Finely I got the phone back and according to what I've been told it's a new device.
When I tried to use the phone I noticed that the APN settings were not transformed from the SIM card to the phone
(did not had that problem before I shipped the phone).
I tried to ran the RUU I used before and It seemed like I'm also going to gain an upgrade from 2.10.405.2 to 2.29.405.2 .
With a heart full of joy I'm pressing the next button and when the status bar reaches the "updating signature" I get the " Error [131] customer ID" error.
Noting I do seems to help fixing the problem.
I managed to root the phone, I flashed the LeeDroid rom, but i still can't run the RUU.
Any suggestions how do I fix the problem ?
I don't think my phone is branded as I bought an online store and from my provider.
Thanks in advance

You need a goldcard.
Sent from my HTC Desire using Tapatalk

Ok, I tried with the GoldCard, still the same error.
I'm trying to install.
RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.
Also i see notification on that tells me that it is safe to remove my SD card.

Can you access your sdcard on your phone?
Sent from my HTC Desire using Tapatalk

nope,
can't access it at all

I think that's your problem then.
Have tried removing it, cleaning the contacts etc?
Sent from my HTC Desire using Tapatalk

I think i messed the card in the proccess of making it a GC
The phone keeps telling me that it's sage to remove it
I dont have this problem when i insert my ap2sd card

try reformatting / remaking your goldcard.
HTH

[Q] Two questions

I'm on T-Mobile UK and getting the DHD soon. I've done quite a bit of reading on rooting and I will definitely do it for the added benefits to my phone. I have two questions surrounding the subject...
1. The VISIONary page says to have a 'safety net' ready before attempting to permaroot. Can someone tell me, or point me in the right direction (Links would be nice) to preparing a copy of the stock ROM to reinstall if something goes wrong? If there are any guides please share =)
2. If I needed to send it for repairs would the only thing I really need to do is to use VISIONary to Unroot the phone? What about any apps that required rooting? Would they have to be un-installed first? I assume that in such a scenario once I got the phone back just re-root it again.

Hi and welcome to XDA.
nikmesh said:
1. The VISIONary page says to have a 'safety net' ready before attempting to permaroot. Can someone tell me, or point me in the right direction (Links would be nice) to preparing a copy of the stock ROM to reinstall if something goes wrong? If there are any guides please share =)
Click to expand...
Click to collapse
One such "safety net" is to ensure you have all the correct drivers installed on your host computer, just install HTC Sync 3 and it will take care of that. Also download the correct RUU (Rom Update Utility) for your particular region & carrier. You can use this to revert your DHD to the state it was when you took it out of the box.
Here you can find the --> Desire HD Files. HTC Sync will come on the SD Card of your new phone.
nikmesh said:
2. If I needed to send it for repairs would the only thing I really need to do is to use VISIONary to Unroot the phone? What about any apps that required rooting? Would they have to be un-installed first? I assume that in such a scenario once I got the phone back just re-root it again.
Click to expand...
Click to collapse
Using the above RUU's your DHD will be factory restored. Everything you did will be reverted back. All the apps you installed will be removed. There would be technically no way HTC would know you rooted your DHD.

andyharney said:
One such "safety net" is to ensure you have all the correct drivers installed on your host computer, just install HTC Sync 3 and it will take care of that. Also download the correct RUU (Rom Update Utility) for your particular region & carrier. You can use this to revert your DHD to the state it was when you took it out of the box.
Here you can find the --> Desire HD Files. HTC Sync will come on the SD Card of your new phone.
Click to expand...
Click to collapse
Thanks for the answer.
How do I know what RUU to use? From my glance I would assume mine would be the: TMO DE 1.39.111. Also know how I can confirm if it's the same version as mine or older? thanks.

If your getting it from T-Mobile UK then you will need a TMO-UK RUU, sadly there isn't one available yet. The TMO DE is for T-Mobile Germany.
You could use a generic HTC RUU, just find the latest version. If you are planning to root, S-OFF, etc... then avoid this --> RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_ 26.04.02.17_M2_release. As this will lock down your DHD.

Thanks again. Though I'm not sure if I shouldn't just wait for a TMO-UK RUU to make an appearance before I root my phone.....Would a generic HTC RUU work for my current firmware? Also wouldn't a generic RUU be a problem if I tried to send it back for repairs?
Oh also I heard mention of a gold card a couple of times here and there. Would this be needed for using an RUU?

No problem at all,
Yes a generic HTC RUU would work. I got my DHD from Orange UK, as it was from the first batch I received it unlocked & unbranded, just a generic HTC DHD. Although carriers will supply you with a branded & locked handset 99% of the time, people still get generic HTC handsets.
If it went in for repairs, T-Mobile will just replace the software for their own anyway.
A goldcard is a modified SD Card that will allow you to flash unsigned ROM's to a locked (S-ON) handset.

Help needed ... unable to find RUU to restore using Orange GSM Desire

Hi all
I am afraid I need help, seems all I ask for ... I have never fully got my head round all of this android tinkering.
I have been running quite happily on a custom ROM but the time has come for me to try and get back to stock since I am trying to unlock the phone for use on another network. The code Orange have given me doesn't seem to work when using a different network SIM, but I got the code to enable me to use a custom Radio and rom ahead of Orange's release of Froyo.
So ... I have tried a couple of the WWE and Europe RUUs from the stock ROM thread
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed
RUU_Bravo_HTC_Europe_1.15.405.1_Radio_32.30.00.28U_4.05.00.11_release_121684
RUU-MoDaCo-Bravo-1.15.405.4-release
both fail to complete saying "ERROR[131]: CUSTOMER ID ERROR" I guess that means Orange variant. I have googled but I can't see anywhere that I can get hold of the Orange original eclair or the new Froyo ROMs. Any help on getting this sorted would be much appreciated as I presume others have hit issues when using Orange Desires
I also seem to have lost the ability to get into recovery mode ... and thus update my current ROM to anything else
Any ideas on what my best steps may be now?
Cheers
Sam

You need to create a goldcard in order to flash a branded handset to an unbranded ROM. Same story if you try to use another carriers branded ROM (not sure why you would, but hey.)
http://forum.xda-developers.com/showthread.php?t=954723&highlight=goldcard
Always make sure that you have the Goldcard in your phone when performing OTA updates.
Another important point is that you need the HTC software / drivers installed on your computer and also make sure you phone has USB Debugging enabled when creating your goldcard.

Quick RUU Question, need to bring my phone back to TMO

I'm done with these issues that my phone is having. It keeps locking up no matter what ROM I use or how little apps I have installed. Something has got to be wrong with my phone and it's time to bring it back to TMO for repair/replacement.
I found this link on HTC to download the RUU: http://www.htc.com/us/support/rom-downloads.html#tmobile
My question is, would this be enough to bring my phone back to stock so that they don't know I've rooted it?
Edit: Also, I just remembered about my bootloader being s-off/unlocked. Would this make a difference or would the RUU set everything back like it should?
Edit again: I found this thread: http://forum.xda-developers.com/showthread.php?t=2735235
So, would I be able to follow his instructions but change the CID to t-mob010 instead of the ones he has listed?

Nobody? I could really use some input on this, I don't want to brick my phone. I have to do this today, I can't take the lockups anymore.

There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.

jshamlet said:
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
Click to expand...
Click to collapse
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.

ned4spd8874 said:
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
Click to expand...
Click to collapse
You are S-off, which means you do NOT have to lock the bootloader first. Most instructions for running an RUU assume you are S-on, however, which does require your bootloader to be locked. It's one of the checks that is disabled by S-off.
Also, S-off is getting harder to obtain, so unless there is a pressing reason to go S-on, it's safer to remain S-off. Warranty support could be that pressing reason.

Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?

ned4spd8874 said:
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
Click to expand...
Click to collapse
If you think your phone has bad hardware, then yeah, at this point you need to go ahead and S-on with the assumption that you will get a refurb - especially now that the M9 has been out a while. Who knows what you will get, though. You might even luck out and get a "new old stock" device with 4.4.2. Or, the refurb place could RUU it up to the latest. It's purely the luck of the draw.

Well this sucks. Can't get adb to recognize my phone in recovery. I can when it's booted into the system, but not recovery or the bootloader....
What a pain this is becoming!!!!!!!!!!!! I'm even trying to get into shell when the phone is booted up and sure I can do that, but I can't su! The binary isn't installed. So, what now I have to f'ing install a different ROM, s-on it and then ruu again????

So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!

ned4spd8874 said:
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
Click to expand...
Click to collapse
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.

jshamlet said:
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
Click to expand...
Click to collapse
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?

ned4spd8874 said:
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
Click to expand...
Click to collapse
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.

jshamlet said:
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
Click to expand...
Click to collapse
Things are looking up! Found a ROM called something like Alex V that was stock enough to get SunShine to work. Also, I was using the original version so once I got it to run, it was giving network errors. Once I installed the latest version, that's when I got was able to go S-OFF. So, now I'm S-OFF, the bootloader is saying Official and locked so now I'm going to RUU and throw it in TMO's face!

Mobile data doesn't work because of RUU?

Hi guys,
So I get my second HTC One M9.
I bought my two phones from Germany and I'm from Portugal.
My first one was an European version and I was able to change Recovery and ROM with S-ON.
My second one was a little different, it comes with CID "O2___102" (branding O2 from Germany) and because I have a higher RUU version, now HTC blocks download mode to prevent custom developments... so I'm not able to install a new Recovery and consequently a new ROM.
So I need to do S-OFF, my main concern is...
1) Everything works, but Mobile Data is not working (I select this option but no icon appears in notification bar and no Internet at all)... Is this related to this RUU ("O2___102") or what can I do to make it work?
2) Will I get Mobile Data working with other RUU (I want European RUU)?
Thank you in advance!

You only have to enable OEM Unlock in Developer Options. HTC doesn't block anything. Only a new securitys feature has been added which demands that extra step during the unlock. Thant means you don't need S-OFF (unless you want to get rid of the branded firmware).
Are you sure that you set up your APN correctly? I don't think that the O2 firmware is the reason for your lack of mobile internet.
Oh and just to clarify some terms: You're talking about firmware and firmware versions. A RUU is an *.exe or a*.zip file which restores the stock rom and reflashes the corresponding firmware.

Hi @Flippy498,
I have enable that option as well.
I think HTC unables to downgrade firmware since version 2.10 and I need it to install the recovery I want. Otherwise it stay stuck in "download mode" with 100% installed but unable to reboot (If I reboot manually no Recovery is installed).
I didn't try to correct the APN because every phones always recognize and do that automatically for me... I need to try that.
EDIT: Fixed!! Tried VPN now working and I was able to install new Recovery, now I'm installing a new ROM. Thanks!

Blutrünstig said:
I think HTC unables to downgrade firmware since version 2.10 and I need it to install the recovery I want. Otherwise it stay stuck in "download mode" with 100% installed but unable to reboot (If I reboot manually no Recovery is installed).
Click to expand...
Click to collapse
I don't understand what you're trying to do. Downgrades have never been possible with S-ON*. You simply need to unlock the bootloader via HTCdev and afterwards you need to flash TWRP 2.8.7.1-CBTB-B1. Since I had to flash TWRP on version 2.10.206.2 for being able to create a TWRP backup for my collection I know that it is possible.
* Well, except for the downrade from 1.32.<EnterYourSKUhere>.15 to the firmware version the phone was originally sold with (for the WWE SKU it was 1.32.401.8).
Edit: Looks like you edited your last post while I was typing this one. I'm glad that you reached your goal but I still don't understand what you tried to do...