Develop Bugs

I can't update to 1.21.405.2

Hi,
My device is 1.15 and rooted. When I click "system software update" I'm always seeing checkingin, nothing more.
I want to update my device to 1.21.405.2 but I can't.
What is your suggestions?

Unroot it.

Code:
How to Unroot your HTC Desire to stock
If you Have A 0.75 Bootloader:
Generic RUU Download / Mirror #1
T-Mobile UK RUU Download
o2 UK RUU Download
3 UK RUU Download
If You Have A 0.80 Bootloader: Download
Other RUUs Avalible Here
You will need:
1. HTC Sync (For Drivers)
2. The Download Above
3. A Windows PC
4. A Goldcard (Not required for generic HTC Desires)
The Guide:
1. Make sure your goldcard is in your phone (If Required-if your phone is branded)
2. Turn your Desire on
3. Connect it to a Windows PC
4. Run the HTC RUU
5. Let it run
6. & YOUR DONE!
Okey, I understood. But which file I must the download for 0.75 or 0.80. My boot version is 0.75.

Apparently the 1st version for 0.75 bootloader, you didnt tell if your Desire is unbranded or not, so if it is, the 1st link.

thed0g said:
Apparently the 1st version for 0.75 bootloader, you didnt tell if your Desire is unbranded or not, so if it is, the 1st link.
Click to expand...
Click to collapse
I don't know what is unbranded. I bought this phone from Germany. Before I rooted I was see T-Mobile logo. After root I see HTC logo. My friend ordered for me and I think he will pay 24 month to T-Mobile Germany. Is that mean branded?
In this case which version is good for me?. I rooted this device one week ago and I tried make 1.21 OTA update but I couldn't. Phone was say: "There is no any update". I dont want to see this meassage again after unroot.
Thanks for reply.

Im not sure, maybe someone else can confim that, but it seems that yours is T-mobile branded. Im not aware though, what and if there is a difference in UK vs German version (if in the UK version the german language is missing for instance).

I don't know what t-mobile is doing, but vodafone users only got a 1.19 update OTA! So no 1.21 in germany I think. Is it not possible to unbrand the phone and install one of these RUU updates from htc? Check this in dev forum

I downloaded this:
If you Have A 0.75 Bootloader:
Generic RUU Download
Click to expand...
Click to collapse
I will do unroot, after that I will try to take OTA 1.21 update, if can't I will try manuelly do RUU 1.21 update. I hope I don'tl corrupt the phone.

Just to be in the safe side, it's best practise to perform a Nandroid backup in Recovery Mode beforehand, which you can later restore if anything does go wrong with the flash.
Sent from my HTC Desire using XDA App

MasDroid said:
Just to be in the safe side, it's best practise to perform a Nandroid backup in Recovery Mode beforehand, which you can later restore if anything does go wrong with the flash.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Ok, nondroid is okey. I did unroot, and I saw a popup about system update
Now, I'm downloading BL 0.80 files to make again unroot but I confuse, should I do again goldcard process? I did already one time before..

Yes, you will need to use the same Gold Card to flash RUU files with a different CID to your own device.
Sent from my HTC Desire using XDA App

So, I have a rooted Desire with stock 1.15 fw. If I want to upgrade to stock 1.21 fw I must unroot, then install the upgrade and re-root, isn't it? But if I'll follow this sequence will I lost every application that is on the phone now? Maybe it's better waiting for Froyo or installing a modded fw?

Well i downloaded offical updated and did the updated manualy because i also did not get updated via phone

Something goes wrong.
1. I have unrooted and did OTA 1.21 update.
2. I checked bootloader version. It's 0.80
3. I have unrooted again with 0.80 and 1.21 version.
4. After that I checked sw version it was 1.15 again
5. Again I did 1.21 updated and after reebot I checked again 1.15
I can download and install OTA 1.21 update many times, but still same. What is wrong?

HTC Wildfire original condition

Hello!
I have a question.
Currently I have the phone Rooted and a custom Rom is installed. Now you have my phone for repair. I would like the phone back in the original condition (ie without root privileges and ClockworkMod menu) to bring.
I had then the original image, which I did for the root time, have re-played.
But unfortunately I get the menu ClockworkMod not go away.
The menu is still available.
Next try:
After I had been playing the original image, and I had started the cell phone was offered by T-Mobile is an update.
But unfortunately this update is not installed.
It aborts with an error message.
Now I have read that I should just flash the original RUU, Complete new. So I went to shipped rom on the side and I have the appropriate RUU for my phone charged. (RUU with the Tmobile UK).
But this I do not get installed.
The flash process is interrupted after a few minutes with the error 140 (wrong bootloader version).
Now my question:
How do I bekome out there, I have on my phone without the original T-Mobile software ClockworkMod, or do I uninstall ClockworkMod?)
Did any of you an idea?
Thank you!
Greeting Hollux
P.S.: Sorry for my bad English.....

Everything you need to know about putting your wildfire to original condition is in this post:
http://forum.xda-developers.com/showthread.php?t=1160251
Enjoy

dragdusan said:
Everything you need to know about putting your wildfire to original condition is in this post:
http://forum.xda-developers.com/showthread.php?t=1160251
Enjoy
Click to expand...
Click to collapse
Hello!
Thank you for the link, but my Handy is not S-off!
I'm at HBoot 0.80 and I have the Problem, that I can not flash the original RUU for my Wildfire....
I become an Error 140 Code (Bootloader error)...
Greets Hollux

what is your language?
is your phone branded?
you have breaked your recovery?
Maybe you have installed the bootloader driver from Unrevocked
Is yes,download and install htc syn from its official site and after the installation,unistall ONLY htc sync,not the drivers
my phone is unbranded and i used this
http://shipped-roms.com/download.ph...5.55.24H_3.35.20.10_release_160191_signed.exe
it will update your HBOOT to 1.01.00001 so you need s-off to flash recovery and custom rom

kylon said:
what is your language?
is your phone branded?
you have breaked your recovery?
Maybe you have installed the bootloader driver from Unrevocked
Is yes,download and install htc syn from its official site and after the installation,unistall ONLY htc sync,not the drivers
my phone is unbranded and i used this
http://shipped-roms.com/download.ph...5.55.24H_3.35.20.10_release_160191_signed.exe
it will update your HBOOT to 1.01.00001 so you need s-off to flash recovery and custom rom
Click to expand...
Click to collapse
Hello!
I have my phone with Rooted Unrevoked3.
Then a Custom Rom installed. (DK ROM).
Original is the phone branded by T-Mobile Germany. It was originally Froyo still on the phone.
HTC Sync I have installed and then uninstalled so I only have the drivers on my computer.
For flash process:
I've taken on shipped-rom RUU following:
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35.15.19_release_130442_signed
If I'm in HBOOT USB plug mode, the mobile is an Android Phone - Android detected bootloader interface.
However, so after the start of the RUU, the phone is not detected!
If I'm in the fast boot mode, the USB phone as a USB device is Android - My HTC detected.
Even after you start the RUU detected the phone and I can start the flash process.
However, it comes out after a minute the error 140 (bootloader error).
If I install the image, which I then made ​​by the original ROMs, will start after the one offered on Air update.
This, however, can not even install.
The flash process will start, but after a short time I see a picture in the phone with an Android males and a triangle. Then I am back in ClockworkMod menu ....
As I've written, I only want to install my phone with the original RUU from T-Mobile Germany and the menu should disappear ClockworkMod ...
Did any of you an idea?
What happens if I flash a non T-Mobile RUU ....?
I can try to flash another RUU and then later, my T-Mobile?
Please Answer, thank you
Greeting Hollux

You will have to downgrade MISC Partition, to allow "Downgrading" your ROM. (DK Custom ROM is based on 2.22.405.1, and you are trying to flash 1.10.114).
The Guide for AlphaRev X to Downgrade HBoot from 1.01.0002 to 1.01.0001 follows this same procedure, but, its for the WWE 2.22.405.1 ROM only.
But, you can follow this procedure, since you are on HBoot 0.80x
http://forum.xda-developers.com/showthread.php?t=905003
Obviously, the command version numbers will change in your case, and, you will need the TMO Rom.zip from that RUU.
NB - Disclaimer - It should work, but, it's a sensitive process, and I am not responsible for bricks.

[WARNING] OTA Update 2.13.401.3

Note: This works for some people, but I suggest you don't update, because majority of the people are having problems.
theq86 has reported his phone bricked.
Conclusions:
1- S-ON & Bootloader Locked
Your HBOOT will stay to the version 1.08.0000.
You will not be able to unlock the bootloader until HTCDev updates its RUU.
2- S-ON & Bootloader Unlocked (HBOOT 1.08.0009)
Your HBOOT will be downgraded to 1.08.0000 and your bootloader will be locked again. You will lose root and CWM.
You will not be able to unlock the bootloader until HTCDev updates its RUU.
3- S-OFF
Your HBOOT will stay (or be updated/downgraded) to 1.08.0000.
You don't have to worry about the bootloader cause it is unlocked forever.
For those who performed the update and are S-ON and want to unlock their bootloader, three solutions :
1- S-OFF your phone with an XTC-Clip
2- Wait for a software S-OFF (they are getting closer and closer)
3- Wait that HTCDev updates its RUU. We should write to them to be sure they are aware of this problem.
Want to get rid of the notifications telling you to update?
1. Download update (to the phone).
2. When the phone asks to install update, plug your phone to the computer in Disk Drive mode.
3. Run Winrar and browse to sdcard/download and enter OTA_Marvel_S_HTC_Europe_2.13.401.3-2.13.401.2_release_237041qqcw21hxt5vkhdz6.zip.
4. Inside you will find file firmware.zip. Unpack it anywhere.
5. Run Winrar and enter unpacked firmware.zip.
6. Click INFO button and go to SFX label.
7. Click "Remove the already existing module from the archive" and OK.
8. Delete all files except "android-info.txt". Save file (firmware.zip).
9. Replace firmware.zip in original OTA update.
10. Run update in your phone.
11. You will see yellow exclamation mark in triangle which means failure.
12. Remove the baterry for one second.
13. Turn on. Phone will show smtng like "update file is corrupt. download again?" - click NO. Turn off automatic check for updates in settings.
--------------------------------------------------------------------
Credits:
theq86 - Bricked his phone in the process! Click thanks for him!
popopo0 - Solution to get rid of the notification icon.
pihug12 - OP of the source post.
Source: [OTA Update] 2.13.401.2 => 2.13.401.3

Why is this update bad?
Why is this update bad? (background info)
HTC included it's newest radio and hboot with the update. Actually nothing to worry about, but there's a problem regarding software version numbers.
For example (HTC EU example):
My WFS shipped EU 2.3.3 (sw no. 1.33.401.2)
Then came the FOTA to EU 2.3.5 (sw no. 2.13.401.2)
And some days past a new FOTA (sw no. 2.13.401.3)
the software numbers are the problem here. HTCDEV provides the RUU updater for unlockable hboot only for 2.13.401.2.
As we know, HTC will not allow us to downgrade even a signed ruu. Thus, we will get a main version is older error.
This leads to the conclusions above.
------------------------------------
Will there be a way to re-unlock the phone?
HTC wrote:
Unfortunately once the device has updated to the most recent software it cannot be reverted to the previous update allowing the device to be unlocked. I can escalate this issue as a feature request to see if a further Hboot update can be released in the future for users who may have missed the opportunity to unlock their devices.
I hope that this information meets with your requirements. Should you have any further questions please do not hesitate to contact me again.
Click to expand...
Click to collapse

You will not be able to unlock the bootloader until HTCDev updates its RUU.
Click to expand...
Click to collapse
1) downgrade 2.13.401.3 to 2.13.401.2
http://forum.xda-developers.com/showthread.php?t=1301388
http://www.filefactory.com/file/c0a...5.3035H_7.53.39.03M_release_225747_signed.exe
2) Only Step-0 (ruu-downloads - Install hboot 1.08.0099)
http://htcdev.com/bootloader
3) I rebooted to bootloader mode and my hboot is 1.08.0099 unlocked
Works fine for me ...

I've S-OFF'd my phone with xtc clip. Should I update my phone?
Also, my Hboot is 0.90.0000
What are the benefits of
Hboot 1.08.0009 as compared to 0.90.000?!
Thanks
Sent from my HTC Wildfire S A510e using xda premium

Royal King said:
I've S-OFF'd my phone with xtc clip. Should I update my phone?
Also, my Hboot is 0.90.0000
What are the benefits of
Hboot 1.08.0009 as compared to 0.90.000?!
Thanks
Sent from my HTC Wildfire S A510e using xda premium
Click to expand...
Click to collapse
I'm qurious about this as well. I'm S-OFF, but haven't installed any custom ROM yet, only Link2SD. So I should be able to install the update without problems, right?

Andreas75k said:
I'm qurious about this as well. I'm S-OFF, but haven't installed any custom ROM yet, only Link2SD. So I should be able to install the update without problems, right?
Click to expand...
Click to collapse
right, see conclusion 1 above.

After struggling to unlock BL my wfs s-on, I prefer not to update. I don't want to take risk.

theq86 said:
Why is this update bad? (background info)
HTC included it's newest radio and hboot with the update. Actually nothing to worry about, but there's a problem regarding software version numbers.
For example (HTC EU example):
My WFS shipped EU 2.3.3 (sw no. 1.33.401.2)
Then came the FOTA to EU 2.3.5 (sw no. 2.13.401.2)
And some days past a new FOTA (sw no. 2.13.401.3)
the software numbers are the problem here. HTCDEV provides the RUU updater for unlockable hboot only for 2.13.401.2.
As we know, HTC will not allow us to downgrade even a signed ruu. Thus, we will get a main version is older error.
This leads to the conclusions above.
------------------------------------
Will there be a way to re-unlock the phone?
I'm not promising anything. I told HTCDEV about the problems in general. Maybe I can get them to provide a RUU for 2.13.401.3 so that everyone who updated this can unlock again. I'm currently negotiating with HTC and waiting for an answer.
Click to expand...
Click to collapse
The easiest way is to edit the software number to a lower one. The How-To is in the forum here:
http://forum.xda-developers.com/showthread.php?t=1301388
Only do the steps before the ruu extract

ONeill123 said:
The easiest way is to edit the software number to a lower one. The How-To is in the forum here:
http://forum.xda-developers.com/showthread.php?t=1301388
Only do the steps before the ruu extract
Click to expand...
Click to collapse
Pitty it is not useful for me. can not even boot into android or access adb
--------------------------------------
UPDATED POST #2 IMPORTANT

Hi there!
I need a little help.. My problem is that I can't remove CWM 5.0.2.8 from my Marvel.
It is S-OFF with XTC Clip.
USB Debugging is ON.
Fast Boot is ON.
I have stock ROM 2.3.5
I chose Charge Only.
I use Marvel Auto-Installers. It detect my Marvel.. I press uninstall recovery (HTC original). Then my phone restarts. After booting I shut down and restart with vlume down pressed to check what recovery I have and... surprise: still CWM 5.0.2.8!
Any little help will be appreciated.

Then please download the auto-installers new.
Go to the folder installed the auto-installers and you will find a orig.img and a fastboot.exe
Restart your phone into the fastboot mode and open terminal. Navigate to the fastboot.exe and execute this command:
fastboot flash recovery orig.img

Thanks a lot!
sending 'recovery' <3100KB>... OKAY
writing 'recovery' ... FAILED (remote: not allowed)
Any ideas?

helbet said:
Thanks a lot!
sending 'recovery' <3100KB>... OKAY
writing 'recovery' ... FAILED (remote: not allowed)
Any ideas?
Click to expand...
Click to collapse
strange behavior for an s-off device ...

theq86 said:
strange behavior for an s-off device ...
Click to expand...
Click to collapse
Anyway .. thanks a lot! I give up with this update..

No, this command must work for unlocked bootloader too.
Have you relocked bootloader? Or check if u really unlocked!!!

I don't know how my bootloader is.. My phone is S-Off by XTC Clip and I have a stock ROM 2.3.5 installed in CWM Recovery from a zip file..

Ähm, i think the StockHBOOT does not support the flash recovery command, if i'm right
Or what HBOOTversion you have?

ONeill123 said:
Ähm, i think the StockHBOOT does not support the flash recovery command, if i'm right
Or what HBOOTversion you have?
Click to expand...
Click to collapse
of course it does support. as you see in helbets post. just fastboot rejects flashing. which should not happen if he is s-off

Can anyone confirm whether this updated ROM can be rooted using the usual methods (GingerBreak/ZergRush) ?
Thanks.
Sent from my Desire Z running CM7.

I can confirm , done it. Head to http://forum.xda-developers.com/showthread.php?t=1445867 there is solution.

some quastion about this phone

hi all
after reading too much about this phone im really confused about some of things that i need to ask them from you guys
1-can s-off be blocked by htc?
2-what is hboot? is it down gradable ?
3-what are the most awful things about this phone ?
thank all of you guys

1) HTC could only block S-OFF by releasing a firmware update that patches the exploit used to gain S-OFF. Anyone who is not S-OFF already and updates, would not be able to use whatever method existed previously to S-OFF.
2) Hboot is technically just one file out of the firmware file package that makes up the bootloader screen and reports the firmware version number or hboot version number. This can get confusing because technically one could just flash or update an hboot, without updating the rest of the device firmware so, while the hboot version will show to be one version, the rest of the firmware files to match that hboot version may not actually be those pertaining to the hboot version projected. Hence, it is usually within best practice to update your hboot along with the rest of the firmware files that have been updated with that hboot version. It is common practice on XDA to refer to the entire group of firmware files from an hboot version as simply the hboot.
Typically updating one's hboot is done by flashing an HTC signed RUU or OTA. But can also be done by flashing the firmware.zip file contained within them respectively. It is important to note, if just flashing the firmware.zip files, they must be done sequentially or altered properly to contain all sequential updates otherwise one will brick and probably require JTAG.
3) After unlocking and modding my phone to my liking, I have not one complaint. This phone is everything I wanted in a phone when setting out to upgrade.
Sent from my HTC One_M8 using xda app-developers app

i have 3 more quastions
1-what happens if i receive the phone after s-off is blocked. can devs make s-off again? can i downgrade and s-off my phone? (im going to buy a unlocked version)
2-can i s-off my phone again after flashing ruu and s-on?
3-will i lose s-off if htc fixes the bug and i update my phone?

pedyvirus said:
i have 3 more quastions
1-what happens if i receive the phone after s-off is blocked. can devs make s-off again? can i downgrade and s-off my phone? (im going to buy a unlocked version)
2-can i s-off my phone again after flashing ruu and s-on?
3-will i lose s-off if htc fixes the bug and i update my phone?
Click to expand...
Click to collapse
1) There is a good chance your phone will not come with any updated firmware if you order it in the near future. That being said, I am not a fortune teller..I have no idea if future updates will be able to achieve S-OFF should they be released.
2) Once you achieve S-OFF, it remains so until you manually force S-ON. If you force S-ON after updating to a firmware that cannot be exploited, you will not be able to get S-OFF until an exploit is found if one is found, however there is never any real good reason to S-ON unless you're trying to trick HTC into honoring the warranty you knew you were forgoing upon unlocking your bootloader.
3) see answer to 2.
*****EDIT*****
I felt I should add that money and or money and knowledge can get your phone S-OFF in just about any state assuming your hardware is working fine. A riff box and some knowhow or a JTAGG service if you don't have the knowhow can always put your phone in an S-OFF state.
Sent from my HTC One_M8 using xda app-developers app

[Q] Debrand M9 and get lastest FW

Hi there all,
Have previously done some modding on older HTCs, but have not really done it in a while.
By chance and opportunity, I got my hands on an M9. Love it, but it is Telstra (AU) branded. I know that to get the lastest FW (OEM or otherwise), its best to get off carrier branded FW.
In order to do this (aim to get to intl or Asia unbranded generic FW), I should:
1. S-Off (via HTC Dev).
2. Install custom recovery
3. do a back up (Just in case)
4. Load the generic RUU of my choosing
5. (optional) install the stock recovery that matches the RUU (for OTA updates)
Is this right? Do I need to mess with CID?
Any info to help me refresh myself would be great.

Apparently HTC dev does not assist with S-OFF.. maybe www.theroot.ninja though ..

jauhien said:
Apparently HTC dev does not assist with S-OFF.. maybe www.theroot.ninja though ..
Click to expand...
Click to collapse
oh good old sunshine.

Anyone have anything else to add? any tips to make it easier on the m9?

Just that installing a RUU will install stock recovery anyway.

The root ninja guys are in the US and get their M9s in a few weeks, you won't be able to achieve the above until s-off is available, you will need to supercid the device to enable you to flash a none telestra RUU.
A custom ROM may well be an option once they start popping up ?

Thanks Punk/Lee, good insight.
Yeah, I've used Viper ROM ages ago with my M7 i think, and that went well, so may go down custom as well. Cant wait to start mucking around with my M9.

Bootloader unlock reportedly works if you select "other" on HTC dev., also, the process must be done from Recovery Download mode, i. e. Hboot-->Downloadoad mode. At least that's the method I have seen reported successful.
My name is Harold and I'm a flashaholic.....

thanks Harold. I will try it when I get some time this week

Excuse the noobness.
As per above, if I can unlock the bootloader using the "Other" selection on HTC Dev, plus this toolkit is available : http://forum.xda-developers.com/one-m9/development/tool-windroid-universal-android-toolkit-t3066989
Then, flash one of the following RUUs - http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
Effectively, that means I can unbrand (use one of the stock RUUs), and it would receive the relevant updates from those regions, yes?

sephstyler said:
Excuse the noobness.
As per above, if I can unlock the bootloader using the "Other" selection on HTC Dev, plus this toolkit is available : http://forum.xda-developers.com/one-m9/development/tool-windroid-universal-android-toolkit-t3066989
Then, flash one of the following RUUs - http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
Effectively, that means I can unbrand (use one of the stock RUUs), and it would receive the relevant updates from those regions, yes?
Click to expand...
Click to collapse
If that RUU, what you want to flash, has different CID/MID - flashing will fail..
And on the other hand for editing your CID/MID in order to match those in RUU can't be accomplished without S-OFF - which you should not confuse with "unlocking bootloader"..

hey, I managed to debrand my M9. I followed these steps:
1. unlock bootloader
2. flash recovery and root
3. S-Off with sunshine
4. Change my CID to HTC__001
5. Put the 0PJAIMG.zip on an SD card and rebooted into bootloader mode and it de-branded the phone