[Q] OTA after different RUU Flash - Desire Q&A, Help & Troubleshooting

Hi Guys,
Does anyone know if flashing a newer RUU with a goldcard will still enable the phone to receive OTA updates? i.e. if an update is available from HTC, one will be able to know download it AND install it even though the RUU flash wasn't originally for your phone?
Thanks

Yes you will be able to get it BUT you'll need the gold card for it to install correctly

Related

[Q] help!! update to 2.2

now I use this RUU :RUU_Bravo_Virgin_Mobile_1.23.351.1_Radio_32.36.00. 28U_4.06.00.02_2_release_128941_signed.exe
I downloaded it from our forum.
But I can not get the 2.2 update notice. and can not change the rom to anothers official rom also.
my Desire's shipment place is Spain.
IS THERE SOMEBODY CAN HELP ME? THANKS A LOT!!!
I was heard there are many many heros in this forum。
But........nobody help me
I think u need a RUU_BRAVO_HTC_WWE ROM not an Virgin Mobile because the update only for not branded roms at this time
Yep Virgin haven't rolled out yet.
but my question is how can i REINSTALL the other offical roms? how can i remove this rom?
z174621 said:
but my question is how can i REINSTALL the other offical roms? how can i remove this rom?
Click to expand...
Click to collapse
Create a goldcard and insert it in the phone and run the generic WWE RUU
WHEN i install this rom:
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed
a error come out when it do the signing.
It is said: the bootloader XXXXXX wrong.....
Any body help?
pls help! the attachement was the Pic When I do the flashing rom.
Do i need the GOLD CARD when I flash the
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.
My phone was shiped to Spain.
if you get this error, than yes you need a goldcard.
To make one is not that difficult, try to search for a goldcardtool.
Hey...
I got this error too but I had a goldcard in my phone!
just flashed the official 2.2 rooted!
Does anyone have an idea if there is a RUU that works with bootloader 0.80 without downgrading it to 0.75?
Thx
I have successfully debranded my 3 branded Desire with software version 1.22.771.1. Steps:
1. Make a goldcard.
2. With unrevoked3 root your phone.
3. Patch the /misc partition with update.zip (found on modaco forums, www .shadowchild. nl/fixmisc/update.zip).
4. Install RUU with goldcard in phone (you won't get error 140). I had to restart my phone with adb reboot bootloader.
5. Flash OTA update.zip from sdcard.
This worked for me.
Works with vodafone bloatware
Many, many thanks!! Like so many others, I downloaded vf's wonderful update(?). The partition patch worked like a dream - no more bootloader errors when trying to flash. I now have a working version of 1.21.405.2.

[Q] Can't flash OTA Update?

Hey guys
So I've been reading forums and websites for a long time now and haven'f been able to fix this.
I have a T-Mobile branded Desire with a Golden Card. I flashed a RUU from shipped-roms.com, then rooted (unrevoked3) it. After a while I removed the rooting with unrevoked3 and flashed a new fresh RUU.
Now the problem is: even thou my Desire does download OTA updates, when booting into update it aborts the procedure with status 7, because my ro.cid still is T-Mobilized.
What did I do wrong?
How can I make it update normally as a generic (unbranded) Desire?
You can't run the OTA on a debranded handset, seems Google changed something in the update ZIP. You'll have to flash the RUU to get it. I assume you're trying to get 2.29.405.5?
2.29.405.5
Click to expand...
Click to collapse
Exactly.
You'll have to flash the RUU to get it.
Click to expand...
Click to collapse
This one?
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
How can I change the ro.cid prop or where is it located?
That's the one, but why do you need to change that file?
EDIT: You can't change the CID of your phone. Seems Google have changed the OTA updates so you might have to flash the RUU every time a new one is out. We won't know until a new update is released
Thank you for your quick reply.
So if I'm getting this right there is no way to actually really permanently debrand an HTC Desire?
How about rooting and disabling signature verification, would that enable me to install the OTA?
shadow player said:
How about rooting and disabling signature verification, would that enable me to install the OTA?
Click to expand...
Click to collapse
No. Never, I repeat: NEVER ota-update a custom Rom! You can either flash a close-to-stock custom rom (and then NOT install ota-update!!), maybe flash one based on the newest htc-rom, so you are not tempted to install the ota update, or install the ruu of the branded stock rom you bought your phone with and wait for the update to appear.
Tillus said:
No. Never, I repeat: NEVER ota-update a custom Rom! You can either flash a close-to-stock custom rom (and then NOT install ota-update!!), maybe flash one based on the newest htc-rom, so you are not tempted to install the ota update, or install the ruu of the branded stock rom you bought your phone with and wait for the update to appear.
Click to expand...
Click to collapse
I'm using a stock RUU firmware...
But you're DEbranded which won't allow you to get the OTA. The ONLY way you can get it is to flash the RUU
EddyOS said:
But you're DEbranded which won't allow you to get the OTA. The ONLY way you can get it is to flash the RUU
Click to expand...
Click to collapse
Thank you for making that clear. I'm really a n00b on this topic. Thanks for all your help. I'm trying to understand,
So an UNbranded (from factory) and a DEbranded (by me) phone still have differences?
On what kind of phone (branded, unbranded or debranded) would the OTA just work normally?
unbranded would get updates from HTC, branded from the operator, debranded either OTA (if they work in future) or RUUs
Hi, i've found this post and I'd like to know if there's a way to change everything in a operator branded desire to appear an unbranded one and get OTA from HTC?
Gold card should do it but other than that no

[Q] 1.29 update failed

I have a bootloader unlocked HTC one X running on 1.28. I got the 1.29 update notification today, but it kept failing when I try to install it. I am on Clockworkmod. It says cannot mount SD card. And I renamed it and deleted the assert cid thing, it failed without a reason.
And I tried to flash back to stock recovery, it still did not work. Do I really need to lock the bootloader to get this work? That's so troublesome.
Anyone can help me? Thank you very much in advance.
hy3301 said:
I have a bootloader unlocked HTC one X running on 1.28. I got the 1.29 update notification today, but it kept failing when I try to install it. I am on Clockworkmod. It says cannot mount SD card. And I renamed it and deleted the assert cid thing, it failed without a reason.
And I tried to flash back to stock recovery, it still did not work. Do I really need to lock the bootloader to get this work? That's so troublesome.
Anyone can help me? Thank you very much in advance.
Click to expand...
Click to collapse
You need to flash stock recovery. bootloader doesnt matter. Are you in europe?
hy3301 said:
I have a bootloader unlocked HTC one X running on 1.28. I got the 1.29 update notification today, but it kept failing when I try to install it. I am on Clockworkmod. It says cannot mount SD card. And I renamed it and deleted the assert cid thing, it failed without a reason.
And I tried to flash back to stock recovery, it still did not work. Do I really need to lock the bootloader to get this work? That's so troublesome.
Anyone can help me? Thank you very much in advance.
Click to expand...
Click to collapse
as far as i did my last OTA am on a branded phone. I restored my backup stock rom installed stock recovery and downloaded the OTA and installed fine. No need to relock bootloader or anything else. have you tried rebooting your phone and trying again? or have you flashed the proper stock recovery mate
Doesn't work for me either,puted the stock restore,i even relocked my bootloader and still nothing,it doesn't seem to work,i will try to update trough recovery mode,hope that will work.
Sent from my HTC One X using XDA
Same here, any solutions
I don't think that i will try to update to 1.29 anymore,i read on a site that 1.30 will be lauched very soon,so i will try to update to 1.30 when it will came up.I don't know what else to do,i mean,i've tryed everything and still no luck with this update.
I have exactly same issue as you,but what I think if its be realise of 1.30 for us be same problem if we don't find any solution now.
I'm in Japan. I've tried that, nothing worked.
Mine is unbranded. I've tried all of them. I've had enough of it.
It won't work. Don't waste your time.
No solutions seemed to work so far. My choice is to ignore it.
Yes, me too. No more 1.29.
Same here, was 1.28 and unlocked the bootloader and rooted. Tried CWM method but doesn't work and hope someone will have solution to this.
I have same problems i surf a lot today,and I find that my problem is that 1.29 Update CID is different from my phone CID. U can get u CID by cidgetter from store. And if u try to flash update by cwm it shows what Phone CID's supporting update witch u have. Just try to check this guys,thats what i find and my opinion it should work.
I think my solution to find update witch supports HTC__001 CID
So basicaly you are saying to download the update and then reboot the phone,enter in recovery mode (cwm) and then try to flash the 1.29 update that we've downloaded?i allready tryed that and it doesn't work,gives me an error and stops.if it's a CID problem can't we just put our HOX CID into the update?i think that i've seen somewhere on xda a metod to do that but i don't remember in which topic.
Sent from my HTC One X using XDA
if it possible to change CID in update,so yeas its solution witch we need. But I don't know how to do it.
I think we will skip the 1.29 update and wait for the next one.I'v just read on the forum that version 1.32 was released (nothing confirmed yet,just some pc screenshots),maybe that version will work.I will check periodicaly for the 1.32 update and see if it works.
I found a thread talking about deleting the lines about CID in a update-script file or something similar. I've tried that, but still ended up with error. I am going to give up.
Did any of you flashed something on 1.28?I am thinking that after i updated to 1.28 i flashed the 3 dot removal.Maybe this is the cause that the update fails?
I haven't flashed anything,just rooted flashed cwm and superU. No updates gonna work for us till we get S-OFF its just one solution. Follow guys in S-OFF Discussion they progressed a lot on it. If they crack our S-ON to S-OFF we can do with our phones whatever we want to do. And install whatever we want to install including updates. Now just wait...

OTA Update fails to install on HTC one M9. Help!

I recently bought an Unlocked HTC one M9 from eBay. It was on Android 5.0.2 (1.32.617.6) and I received an update notification for 1.32.617.30. When I clicked to install it, it fails saying error in cache with error 7. I think since it's a used phone the device software has been tampered before therefore the OTA update fails. I don't know the device history.This is what I found in bootloader mode.
Software status: Official
S-OFF
Bootloader:Locked
It is super CID (11111111)
And it has stock recovery.
I have tried flashing 1.32.617.6 stock ROM from stock recovery after I found it on XDA. It also failed saying signature verification failed. I searched this forum and found that someone had the same issue and they had to flash 1.32.617.6 using a SD card formatted to FAT32. I don't have a SD card so I couldn't try it.
I also tried HTC's latest RUU. EXE for Unlocked/Developer edition but it doesn't run well. It starts and shuts down after it asks me to agree to terms and conditions. I have latest HTC sync manager and it recognizes my phone. I will be trying this again on some other computer.
I really want to update my device to the latest version of OS. Please help me! I don't know what else to try.
You cannot flash an ruu because the device is modified. The easiest option is to flash an unsigned update. Unlock your bootloader and enable usb debugging first though.
Beamed in by telepathy.
I don't understand in what way the device is modified because it says bootloader Locked not relocked and everyrhing is stock. I thought it might have been restored to stock after rooting or what not. If that is the case shouldn't I be able to install OTA update?
Anyways I wanted to know if there is some way where I don't need to unlock bootloader or root it. I want to stay on stock OS.
Update: used RUU.EXE on Windows 7 computer and it worked. For some reason Windows 8/10 is not good with running external exe files.

downgrade nougat --> marshmallow with ruu - is it safe?

Can I downgrade a Verizon HTC 10 that has nougat to marshmallow by flashing the marshmallow RUU? I bricked my previous phone trying to downgrade with MM RUU (verified md5) because it blew through some error message about hboot (90?) that I couldn't stop, and it was bricked. Is there a way to prevent that from happening again? Do I need to flash a different firmware first?
Thanks!
ffuser1 said:
Can I downgrade a Verizon HTC 10 that has nougat to marshmallow by flashing the marshmallow RUU? I bricked my previous phone trying to downgrade with MM RUU (verified md5) because it blew through some error message about hboot (90?) that I couldn't stop, and it was bricked. Is there a way to prevent that from happening again? Do I need to flash a different firmware first?
Thanks!
Click to expand...
Click to collapse
Are you S-Off? If so, you can downgrade from N to MM
Downgrading from Oreo (which Verizon hasn't got yet) will cause a radio/baseband brick though
ffuser1 said:
Can I downgrade a Verizon HTC 10 that has nougat to marshmallow by flashing the marshmallow RUU? I bricked my previous phone trying to downgrade with MM RUU (verified md5) because it blew through some error message about hboot (90?) that I couldn't stop, and it was bricked. Is there a way to prevent that from happening again? Do I need to flash a different firmware first?
Thanks!
Click to expand...
Click to collapse
the reason you bricked is because you probably did what i did with my previous 10 and you have to downgrade using the full ruu. not just the firmware. also you have to use a specific htc fastboot driver to prevent blowing past that error. Googles fastboot driver does. its all in one of the ruu threads
You can not downgrade without s-off
sorry, maybe I wasn't specific enough.
The previous phone was s-off unlocked phone, supercid, had installed Verizon RUU. I was downgrading via booting into download mode and installing the RUU from my external sd card. I don't remember if I installed a different firmware before this.
Now I have an S-off Verizon HTC 10 on Verizon network, want to downgrade due to issues with keeping everything systemless to avoid breaking Verizon advanced calling features (my understanding is that if I modify anything in /system, like using an auto start manager or freezing bloatware or new kernel, these will break).
Should I be able to downgrade RUU from the external sd card through download mode without hboot issues? Or is there a way to check if there'll be an hboot issue? Doing it from adb on a computer would hopefully give me the option to rescue it if I get that error again, so it seems like the safest method. Or would flashing MM firmware first, then MM RUU, be the safest? I'm trying not to brick a second device. Thanks!
ffuser1 said:
sorry, maybe I wasn't specific enough.
The previous phone was s-off unlocked phone, supercid, had installed Verizon RUU. I was downgrading via booting into download mode and installing the RUU from my external sd card. I don't remember if I installed a different firmware before this.
Now I have an S-off Verizon HTC 10 on Verizon network, want to downgrade due to issues with keeping everything systemless to avoid breaking Verizon advanced calling features (my understanding is that if I modify anything in /system, like using an auto start manager or freezing bloatware or new kernel, these will break).
Should I be able to downgrade RUU from the external sd card through download mode without hboot issues? Or is there a way to check if there'll be an hboot issue? Doing it from adb on a computer would hopefully give me the option to rescue it if I get that error again, so it seems like the safest method. Or would flashing MM firmware first, then MM RUU, be the safest? I'm trying not to brick a second device. Thanks!
Click to expand...
Click to collapse
Yes, just put the Verizon ruu you want on your sd card and run as usual. No issues.

Categories

Resources