Develop Bugs

Willing to pay to unroot HTC Desire

Hey guys,
I've a desire and decided to sell it but before that, i need to unroot it. I'm willing to pay.
Anyone interested?

Are you branded and do you know what was your software version out of the box.

What do you mean by branded? I got the set from M1 though..
I can't recall the orginal version but currently it is 2.13.707.1 after rooting with unrevoked.

Okay so you are in Singapore and need an Asian RUU.
Sounds like you have rooted but have not installed a custom ROM.
Download this RUU http://www.shipped-roms.com/downloa...00.32U_5.09.05.30_2_release_143921_signed.exe
Turn off your phone;
Turn on your phone holding the back button;
You have now entered "fastboot";
Plug you phone via the usb cable to the PC and then start the RUU.

And thats all?? No gold card or whatever sort of complex steps to get it unrooted?

If that's the correct ROM you won't need a gold card, it'll just work. If you get any error messages then chances are you were on another ROM originally
A gold card is only needed to move to a ROM not originally on your handset, e.g. I have an x.xx.405.x Desire so can only flash x.xx.405.x RUUs without a gold card

You need a goldcard if you are branded (for example having splash screen when booting and preinstalled apps by your carrier) and flashing a ROM or an update that is different software version from what you bought your phone with in the first place.
You should be unrooted just by doing the above.

After successful rooting i didn't do anything to the phone so it should work right? What will happen if it doesn't work? Will the phone be bricked?

No, just follow the steps and you will be unrooted.

I got this when i try running the ruu
error 5001 "please make sure you have finished any previous setup and closed other applications

Does it matter on what OS i'm doing this from? I'm currently using windows 7

Run it as admin.
Right click on the RUU and choose "run as administrator" (or sort of that).

RUUs run fine in Windows 7, I use Windows 7 Ultimate 64-bit and have no issues.
Obviously can't have any other programs installing when running an RUU as it is an installer in itself

I tired running as admin but still the same error pops up. I read from somewhere that HTC sync needs to be installed for it to work?

You don't need htc sync when you are in fastboot mode.
It's possible that the RUU which is a self-extracting archive can't be extracted properly. Check if you have the whole file and it's not corrupted, be sure that you have enough space to extract it (you probably have it).
Run the RUU on a fresh restart of the windows.
If you got another windows machine at hand you can do it on it.

Thanks for the help guys!

also you might want to check out many tutorials HOW TO on this forum or youtube etc

[Q] Root via fastboot?

Are there ways to root using fastboot? Have usb brick but working fastboot, and guide using android emulatro doesnt work. Have latest RUU with 0.93 hboot

Have you tried running an RUU from HTC? They completely restore your phone to how it was, and your device only needs to be turned on on the bootloader screen for it to work. (power up with volume down pressed)
Note that this wil completely wipe the phone's internal memory. (though not the sd card)
You can find the RUUs here. If you have an unbranded device (meaning it wasn't customized by the carrier), this is probably the one you're looking for.
Remember: if the device powers on, it isn't bricked!

That post of RUUs is VERY old, here's the site which has them all...
http://shipped-roms.com/index.php?category=android&model=Bravo

It was rooted originally with oxygen. When brick, I used downgrade tool, pimg.img zip from sdcard in hope for it to fix itself. Installed upgrades from htc to froyo. No luck
but if possible to push ruu using fastboot I will try it. Strange thing, it will only charge if rebooting via fastboot, and its then detected as in need of qualcomm drivers.. no luck finding working drivers to that.. Haven't found similar case in any forums. ideas?

Blubba10 said:
It was rooted originally with oxygen. When brick, I used downgrade tool, pimg.img zip from sdcard in hope for it to fix itself. Installed upgrades from htc to froyo. No luck
but if possible to push ruu using fastboot I will try it. Strange thing, it will only charge if rebooting via fastboot, and its then detected as in need of qualcomm drivers.. no luck finding working drivers to that.. Haven't found similar case in any forums. ideas?
Click to expand...
Click to collapse
For drivers you should install htc sync.

I know, but it doesn't take.. Thanks for hint though

Update. When I tried to run RUU in windows I only get 170 connection error, also in fastboot mode. Found it as PB99IMG file and ran it through SDcard, but it didnt fix usb problem.. Is there a difference between those two methods when i comes to degree of restoring? Dont think so, anyway..

I'm not entirely sure, but you can try this: when the device's powered on and connected in bootloader mode, go into the Device Manager, and find your phone in the list. Right click and choose the option to install a new driver (I don't know the exact function name in English, my system's locale is Dutch). Then, go to the screen where you can select a driver. Select HTC in the vendor list and install the driver. That should fix your 170 error.
If that doesn't work, try this, and optionally the above again.

http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/ download zip from here and flash from recovery after renaming it update.zip
Blubba10 said:
Update. When I tried to run RUU in windows I only get 170 connection error, also in fastboot mode. Found it as PB99IMG file and ran it through SDcard, but it didnt fix usb problem.. Is there a difference between those two methods when i comes to degree of restoring? Dont think so, anyway..
Click to expand...
Click to collapse

Big thanks, but I´ve sent it in for repair. Hope to get in on garantee, but if not, I will just get it returned and try it out..

You need root for that though which he (and me) probably has not.

No, you don't. You can flash update.zip through the stock recovery.
Do you have access to that?
Sent from my HTC Desire using XDA App

I've never had to do a usb-brick fix, but from what I understand, you should have root to flash that particular "update.zip", because otherwise you'll end up with a sig ver error or some sort of that.
As said in the first step "1. Follow this r5 rooting guide to do Step 1 of the rooting.That will give you a basic ROM to work with, with root capability."
The reason I think you need to flash it as an "update.zip" file is because the r5 method in itself does not flash a custom recovery (from which you can flash files without regard to the name).

3722 said:
I've never had to do a usb-brick fix, but from what I understand, you should have root to flash that particular "update.zip", because otherwise you'll end up with a sig ver error or some sort of that.
As said in the first step "1. Follow this r5 rooting guide to do Step 1 of the rooting.That will give you a basic ROM to work with, with root capability."
The reason I think you need to flash it as an "update.zip" file is because the r5 method in itself does not flash a custom recovery (from which you can flash files without regard to the name).
Click to expand...
Click to collapse
Yup...And now we need 10chars.

I eneed up using rageagainstthecage method to apply usb fix.. Only way wich worked..
Sent from my HTC Desire using XDA App

[Q] reinstalling stock ROM on hboot 0.93.0001

My Desire recently had to be sent back to HTC for repair. Came back with hboot 0.93.001. When I got it back, I rooted it (using Unrevoked) and flashed LeeDroid 2.3b.
However, the phone has developed the common locking/rebooting fault and I need to send it back to HTC again, but before I can send it back I need to reflash the stock ROM (T-Mobile UK).
However, whichever method I try I can't get the stock ROM back on to the phone. If I try reflashing using HTC sync, then I get ERROR #140 or #170 (assuming the phone doesn't freeze during the process).
If I try extracting the ROM.zip and renaming it to PB99IMG and installing from the root of the micro SD then I get a message saying "CID incorrect! Update Fail!"
Does anyone have any ideas how I can get my piece of crap HTC Desire back to stock ROM?
P.S. if you haven't already guessed from the last statement or read any of my other posts about my Desire going wrong, I will NEVER EVER buy another HTC....their customer service stinks worse than a landfill site!!

The CID error indicates that you need a Gold Card, you could use the Gold Card tool in my sig below to create one quickly.
Sent from my HTC Desire using eMIUI

MasDroid said:
The CID error indicates that you need a Gold Card, you could use the Gold Card tool in my sig below to create one quickly.
Sent from my HTC Desire using eMIUI
Click to expand...
Click to collapse
OK, I've created the goldcard. Now, how do I get the rom image onto the card? When the phone boots with the gold card in, I can't select mass storage. I've also tried the card in a card reader...it wasn't recognised.
Help???

babblerx said:
OK, I've created the goldcard. Now, how do I get the rom image onto the card? When the phone boots with the gold card in, I can't select mass storage. I've also tried the card in a card reader...it wasn't recognised.
Help???
Click to expand...
Click to collapse
Are you able to mount your SD card in recovery?
Try the following, I am assuming that you are running Windows 7: Try to re-format the card as FAT32 (if present, right-click on the removable disk and select Format).
1) Check if the device is getting detected in device manager. Follow the steps to go to device manager:
- Click Start, type devmgmt.msc and press enter.
- Search for the name of the device
If the device is not getting detected in device manager, then check if it is hidden device.
- Click show hidden devices under View
- Expand all the nods under device manager
There would be many grayed out entries in device manager uninstall all the grayed out entries under all the nods and then restart the computer and plug the external device to the computer and check if it works
2) Install the latest drivers from the manufacturer website and even make sure the driver is compatible with the version of operating system installed on your computer. check if it works
Link: http://windows.microsoft.com/en-us/windows7/Update-a-driver-for-hardware-that-isnt-working-properly
Install the driver in Compatibility mode: http://windows.microsoft.com/en-us/windows7/Make-older-programs-run-in-this-version-of-Windows
3) Check with any other another SD card if it is getting recognized or detected or you may even check if the same SD card is getting recognized or detected on other computer

I have the same prob

still having problems...
MasDroid said:
Are you able to mount your SD card in recovery?
Try the following, I am assuming that you are running Windows 7: Try to re-format the card as FAT32 (if present, right-click on the removable disk and select Format).
1) Check if the device is getting detected in device manager. Follow the steps to go to device manager:
- Click Start, type devmgmt.msc and press enter.
- Search for the name of the device
If the device is not getting detected in device manager, then check if it is hidden device.
- Click show hidden devices under View
- Expand all the nods under device manager
There would be many grayed out entries in device manager uninstall all the grayed out entries under all the nods and then restart the computer and plug the external device to the computer and check if it works
2) Install the latest drivers from the manufacturer website and even make sure the driver is compatible with the version of operating system installed on your computer. check if it works
Link: http://windows.microsoft.com/en-us/windows7/Update-a-driver-for-hardware-that-isnt-working-properly
Install the driver in Compatibility mode: http://windows.microsoft.com/en-us/windows7/Make-older-programs-run-in-this-version-of-Windows
3) Check with any other another SD card if it is getting recognized or detected or you may even check if the same SD card is getting recognized or detected on other computer
Click to expand...
Click to collapse
OK, I managed to create another goldcard with the goldcard tool in your signature. I then extracted the rom from the T-Mobile (UK) stock ROM and renamed it to PB99IMG.ZIP and dropped it onto the goldcard.
Rebooted with the goldcard in the phone and vol - pressed, got the boot menu. The rom image was detected and started to load (side bar in top right of screen showing progress). ROM loaded 100%, then got the 'checking ROM' message. Then..."CID incorrect! Update Fail!" message again.
I've checked and double checked the goldcard creation process and am convinced I'm doing nothing wrong.
Any other ideas? I'm beginning to think hboot 0.93.0001 can't be downgraded.
P.S. I'm running Vista 32-bit

No, flashing an old RUU over a new HBOOT won't work. The issue you've got is there isn't a 2.2 T-Mobile UK RUU available so unless you've got an AMOLED screen the only thing you can do is flash the stock HTC RUU

it is an AMOLED screen
EddyOS said:
No, flashing an old RUU over a new HBOOT won't work. The issue you've got is there isn't a 2.2 T-Mobile UK RUU available so unless you've got an AMOLED screen the only thing you can do is flash the stock HTC RUU
Click to expand...
Click to collapse
Cheers Eddy. However, as far as I can tell, it is an AMOLED screen. All I want to do is get it back to T-Mobile stock ROM so I can send it back to HTC again.
Can't understand why there isn't a 2.2 T-Mobile UK RUU available yet.
It's damned infuriating!! Stuck with a phone I can't use at the minute...and getting desparate!

T-Mobile UK Stock 2.2 RUU anbody???
***BUMP***

I still need help
Anyone managed to re-install a stock ROM on an hboot 0.93.0001 device yet. If so, how did you do it?

babblerx said:
Anyone managed to re-install a stock ROM on an hboot 0.93.0001 device yet. If so, how did you do it?
Click to expand...
Click to collapse
Im in the same boat. Cant get mine back to t-mobile uk stock either
Sent from my HTC Desire using Tapatalk

EddyOS said:
No, flashing an old RUU over a new HBOOT won't work. The issue you've got is there isn't a 2.2 T-Mobile UK RUU available so unless you've got an AMOLED screen the only thing you can do is flash the stock HTC RUU
Click to expand...
Click to collapse
I know t mobile would know that the rom has changed from there own one to the htc one, but are the any differences apart from that if the htc rom was installed?
I mean would it run normally and recieve the normal updates ota, and would that affect if the htc was simlocked or anything?
Sent from my HTC Desire using Tapatalk

It'd run normally but would get HTC OTA updates not T-Mobile ones. Seems the latest OTA doesn't work on debranded phones, though

EddyOS said:
It'd run normally but would get HTC OTA updates not T-Mobile ones. Seems the latest OTA doesn't work on debranded phones, though
Click to expand...
Click to collapse
@Eddy,
Since he has AMOLED, there's a multistep procedure he can try.
1. Prepare the goldcard correctly with a Format in Fat32 (and deleting any extra partitions. Only 1 partition should exist-It should be a Fat32 Primary). If Goldcard is correct, phone should not give CID incorrect error.
2. Download the WWE 2.29 PB99IMG.zip, and put it in the goldcard and run it.
3. Run Teppic74's downgrader with goldcard. At the last step, choose to use this PB99img (Run this RUU while monitoring your Temp folder for changes. When the RUU loads and displays a window, search temp for Rom.zip. Rename it to PB99IMG.zip and put it in the root of the sdcard) instead of the Teppic one.
4. At this point the phone will have a completely working 2.1 Android OS branded to TMO.
5. Check for and update with OTA (You will get TMO OTAs at this point). Now your phone will have the latest TMO ssoftware and be as good as any other!

But they'd have to extract the PB99IMG file out of the RUU, the RUU on it's own won't do

EddyOS said:
But they'd have to extract the PB99IMG file out of the RUU, the RUU on it's own won't do
Click to expand...
Click to collapse
Yes indeed, but quite doable. The result would be a perfectly unrooted T-Mobile branded phone.
Edit: Added instructions for extracting the PB99IMG.zip from the TMO RUU

thanks for all the advice.....
...but I've given up on my Desire.
I can't use it for more than 2 minutes at most without it freezing up!! This is nowhere near long enough to do any of the above! I've even tried resting it on a bag of ice to keep it cool, but even that was no good!
I'm just gonna sell it to one of the recycle companies and put the money towards buying myself out of my contract.
Shame really because when it was working, it was a brilliant phone!!
HTC seriously need to get their house in order QC-wise. I know they have been making phones for a good few years now, but people still say "HTC, who??" and while they're QC remains as bad as it seemingly appears to be then that situation will persist!!
Think I'm gonna take a risk on the LG Optimus 2X when it comes out!! Why? because I love Android...I love bleeding edge...only now I hate HTC with a passion!!!

Droidzone are you based in the uk, as i dont know how to do what you have said. If you are and can do it for me that would be great and i would pay for your services.
Sent from my HTC Desire using Tapatalk

digo21 said:
Droidzone are you based in the uk, as i dont know how to do what you have said. If you are and can do it for me that would be great and i would pay for your services.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Same here. If anyone can get my T-Mobile (UK) Desire (rooted, hboot 0.93.0001) back to stock ROM then I'd be willing to pay (within reason). Bearing in mind you'd first have to solve the problem of it not being usable for any more then 2 minutes even from 'cold'.

No software problem should fail to be repaired by running a ruu. If if freezes or loops while running ruu, that confirms a hardware fault which necessitates a return if the device.
No I'm not in UK. I know that what I described may seem overwhelming, but believe me, if you run the procedure I mentioned, step-by-step and with the files I linked, there is no reason why you can't have your phone up and running in under 45 mins. See the unrooting guide I've written, linked in my signature, for the step-by-step method of running the pb99img from an ruu. It's easy enough. Only things you need for a smooth sailing is a working goldcard and the file extracted from the ruu correctly.
Note that I can't confirm that this method will work for Slcd , and it is quite dangerous running a 1.20 ruu on slcd. Proceed only if you're sure that yours is an amoled desire
Sent from my HTC Desire

[Q] messed up htc desire - tried to unroot phone now phones stopped working

Hi. i tried to unroot my phone and install orange stuff back on by following a guide on this forum.
http://forum.xda-developers.com/showthread.php?t=796975
When i followed the guide i kept on getting md5 error, so then i dont know what i did, i somehow installed something and now the phones stuck on htc screen, phone wont load. However i still can enter hboot menu. i have taken some pics so you can see. i will add them to Flickr.
http://www.flickr.com/photos/kaisar89/sets
the phones orange uk branded which i purchased from phones4u. Details on the box are as follows:
HTC Desire PM Handset
OHTN1132
IMEI:
S/N:
P/N
EAN
Barcode: 5 027141 592329
That is the all the information on the box.
can someone please give me a solution on how to fix this problem. Much appreciated. TY

Of I've followed that guide. That nandroid backup is the Orange version but it's still rooted. And in the guide it says to open up a file and remove one of the lines. That will fix the md5 error. Anyway to unroot properly just use an ruu.
Swyped...

Meaple said:
Of I've followed that guide. That nandroid backup is the Orange version but it's still rooted. And in the guide it says to open up a file and remove one of the lines. That will fix the md5 error. Anyway to unroot properly just use an ruu.
Swyped...
Click to expand...
Click to collapse
ty for posting. i have not got a clue on how to use ruu or find an ruu for that matter. could you point me to an orange branded ruu. would i need to connect my phone to computer to use ruu? if so i cant connect the phone because i cant access phone and turn on usb debugging etc.

just go into fastboot mode, plug phone to computer and run the RUU on pc.
it will work.

dzumagos said:
just go into fastboot mode, plug phone to computer and run the RUU on pc.
it will work.
Click to expand...
Click to collapse
hi, is there a stock orange ruu? if not the very least a stock htc ruu?
if possbile could you post link
in fastboot mode theres 4 options.
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Which one do i need to select?

You just leave it in fast boot then plug it in to the computer you should see the red fastboot writing turn to fastboot USB plug then just run the ruu and that's it
Sent from my HTC Desire using XDA App

No there isn't a stock Orange RUU - it's the one drawback of rooting an Orange-branded phone as there's no way of getting back to stock. You'll have to flash a stock unbranded RUU using a gold card

Need stock RUU for Telstra HTC M9 4.30.841.1

Hello
My stock HTC M9 is stuck in a boot loop.
S-ON
OS 4.30.841.1
I can access the stock recovery mode by 'Reboot to Recovery Mode' then pressing power + volume up when the red triangle appears.
In recovery mode I can Apply update from ADB and Apply update from SD card. Unfortunately can't get ADB to recognise the phone as connected. (probably because USB debugging was not enabled before the phone got stuck in boot loop?)
Anyway have tried to apply the following updates from SD card that I have found links to on these forums
0PJAIMG_HIMA_UHL_L50_SENSE70_Telstra_WWE_1.32.841.7_R_Radio_01.01_U11440261_56.01.50303G_3_F_release_425231_signed.zip
OTA_HIMA_UHL_N70_SENSE80_MR_Telstra_WWE_4.23.841.1_R1-3.38.841.6_release_4967203jqx6xvhwi80vam2.zip
Both come back with the same error
[E:footer is wrong ... E:signature verification failed]
Does anybody have a copy of the stock Telstra RUU for 4.30.841.1 with the correct package verification they would be willing to share?
Also open to any other suggestions to on how to recover this device.

You dont flash in recovery, you flash in download mode..
Rename the 2nd one to 0PJAIMG.ZIP and copy it to an sdcard, put sdcard in the phone and boot into download mode. You should see a prompt at the bottom of the screen to press vol+ to flash.
If you don't get the option then the firmware isn't signed and you'll need to find another one.

The signature has nothing to do with the prompt since that check is the first step of the flashing process after you accepted the prompt.
And flashing the 4.23.841.6 RUU on that phone isn't possible with S-ON. Only RUUs that have a higher version than your phone or 4.30.841.x (with x being any number) RUUs can get flashed without S-OFF in this case since all numbers in front of the SKU (841) and the SKU itself need to match for a downgrade.
Websites like ir-file or easy-firmware might have the needed RUU. Both will require you to pay for the file, though.
Sent from my HTC One M9 using XDA Labs

Thx Flippy498 that's exactly why I'm asking if anyone on this forum has a Telstra 4.30 RUU they're willing to share!
Anyone... Anyone?
I'll search the web a bit more but not willing to pay for the file as phone is 3 years old.
I noticed that HTC dev site offers the source code for the Telstra 4.30 kernel. Anybody have instructions to turn this into a RU?

LuckyLuke2017 said:
I noticed that HTC dev site offers the source code for the Telstra 4.30 kernel. Anybody have instructions to turn this into a RU?
Click to expand...
Click to collapse
That's not possible since no one except HTC has access to the needed signature. And without signature you won't be able to flash the file with S-ON.
Sent from my HTC One M9 using XDA Labs