Database Info

[Q] OTA updates to debranded Sensation

Just a quick question as I can't see that it has been answered anywhere else...
I have debranded a Vodafone Sensation using the excellent guides on XDA; Revolutionary and then CID change, S-Off, etc and installed the latest stock HTC RUU. So far so tricky...
Going forward, will I be able to accept and install OTA updates from HTC, or am I stuck in going down the RUU route when I want to update?
Many thanks.

If your CID is HTC__001 then, for all intents and purposes, you have an unbranded Sensation and will get updates once pushed out by HTC

Eddy
So these will be fine to install and won't error? Good news! Was a pain when they started getting locked on the Desire.
I use Mybackuppro to try and restore everything, but it's still a pain to flash RUU's all the time. Especially after my recent issues with the Radio...

Until a new OTA comes out you won't know but it should be fine

flashing ICS back to stock

Hey guys,
I have to flash my HTC Sensation back to stock, because it have a little hardware error (its sometimes suddenly shutting down ...)
My Sensation is from Germany..
On my phone is currently the Cyanogenmod 9. Yesterday I flashed the eng Hboot 1.17, because I read somewhere that i have to. Is this true?
After this I wanted to restore my backup of the original Rom, but this doesn't work. There were some errors and so on.
I think if I would send it back to HTC I have to uninstall the CWM and I have to install the old Hboot 1.18, but after a lot of reading today and yesterday I'm very confused., because I found no working way ...
greets
Tobi

http://forum.xda-developers.com/showthread.php?t=1516255
Person with pretty much same problem and some advice.

1. Flash old 1.17 FW (unless you're Super CID, in which case you may not need to)
-> ok i flashed a 1.17 FW. Everything is still working without any issue,but after I unlocked my phone i had the 1.17.111and so on FW. Now I have the 1.17.2008. Is this maybe a wrong fw?
2. Flash the RUU of your choice (normally the one your phone came with, if available)
->I don't know the RUU which my phone came with , the most was done by the program revolutionary. I have an unbranded European Sensation. Which is the right RUU?
RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe
RUU_Pyramid_HTC_Europe_1.28.401.1_Radio_10.42.9007.00P_10.11.9007.15_M_release_192608_signed.exe
RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198179_signed.exe
RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035.00U_10.14.9035.01_M_release_208857_signed.exe
RUU_Pyramid_HTC_Europe_1.45.401.3_Radio_10.56.9035.00U_10.14.9035.01_M_release_219990_signed.exe
RUU_Pyramid_HTC_Europe_1.50.401.1_R_Radio_10.58.9035.00U_10.15.9035.02_2_release_228602_signed.exe
I read that I can brinck my phone very fast with it, so it is very important
I just have to download the exe and run it, after this it will flash my phone if it is in USB Debugging ?
I hope it is so easy to downgrade the phone from 4.0.3 to 2.3.4
3. Reset Super CID to one of your choice (again, usually the one your phone came with)
Is this important? Or is it enought if I just reinsert the battery, becuase I don't know if I'm Super CID
4. S-ON using the fastboot command in the guide in the Dev forum
with adb-tools:
-fastboot oem writesecureflag 3
-fastboot reboot-bootloader
right?

RUU_Pyramid_HTC_Europe_1.50.401.1_R_Radio_10.58.90 35.00U_10.15.9035.02_2_release_228602_signed.exe
This was on my unbranded Sensation when I bought it.
For SuperCID look here (Step 4):
http://forum.xda-developers.com/showthread.php?t=1192300&page=1

warning
i updated to icecreamsandwich firmware h boot 1.23. i neede to go back to stock so i follwed directions on guide to s-on and ran ruu that came with my phone and it says error get the right bootloader ruu .however it didnt brick it but bootloader says security warning wifi and wifi hotspot both gives error. ive tried everything i know to fix it with no luck. ive heard its because i upgraded the firmware.

ok I'm now on Super cid. This was just very easy
Ok now I have to download the RUU (filefactory is very slow... )
What will happen, when I would flash the wrong EU ROM? Or is this just impossible?
Is it important to reset the cid to the cid which was set, when I got the phone? Or is it set back by flashing the RUU?
I have a lot of questions, but I don't wanna brick my lovely phone
Edit:
Ok everything is now fine. My phone is now on Andorid 2.3.4, S-On, old CID and unrootet...
I hope they will repair it, because sometimes the phone run 2 days without any issue and sometimes it just runs some hours without issue...

[Q] cant update back to 2.3.5 after downgrading hboot and whatnot

okay so I haven't quite got used to my HTC yet, am so used to my old nexus s, so that could be why I am confused.
Basically as soon as i got the phone the ota updated to 2.3.5 sense 3.0 and all was fine but then i decided to downgrade my Hboot so i'm back to the 98.000 or whatever and it works fine, i used revolutionary, re-romed a lot!! and then took rev off, so its back to S-on and Hboot locked... the only thing is that since being back on sense 2.1 i wondered if i could push the ota update back (no longer showing up) or if someone had the RUU? mines the VODAFONE version though so the normal europe one doesn't work trust me.
if anyone could help it would be much appreciated, thanks.

If your phone is vodafone branded, then the CID setting would lock you to using vodafone RUUs / OTAs, hence generic HTC / europe ones would fail.
To solve that you can either:
1. Use XTC clip to get SuperCID or
2. Create Goldcard
Both methods allow you to flash non-brand-authorised RUUs / OTAs.
Hope this helps!

i used the goldcard and ran the RUU straight after and it worked perfectly THANK YOU! .. me and my boyfriend had made a goldcard before but we never really knew what it did lol.. now i know

[REF] Dead/Bricked phone after JB OTA, QHSUSB_DLOAD

Hi All,
There are more and more reports coming in from people who ended up with a dead/bricked phone after the JellyBean Update 4.1.1 , 3.16.401.8 OTA. As you connect it to your PC you will soon find out it's in QHSUSB_DLOAD mode.
The purpose of this threat is to see how many people are affected, what people have done to attempt to recover their phone, and to find a possible solution (this chance seems rather small though).
There are alot of post about this in the JellyBean Speculation/News/Discussion threat, starting from page 157.
There are 2 threats about it in Q&A:
One S in QHSUSB_DLOAD mode
My HTC to really died
Reported attempts to recover:
QHSUSB_DLOAD Fix by team Unlimited
Unbricking HTC devices with the QHSUSB_DLOAD issue tutorial by kgs1992
Step 3 (and some others) from [TUT] Downgrade/Unbrick Ville S4
Another HTC one V recover guide where i can't find the link for.
Please report here if you have this issue. Please mention your CID, in what country you downloaded the OTA, the software version you upgrade from and the hboot version.
Also any new ideas to recover our phones our self are welcome!
My phone:
2.31 Unbranded Europe
1.14 Hboot
Downloaded in The Netherlands
1111111 Supercid

I have exactly the same problem, waiting...

As far as I know the issue is only caused by people who previously had SuperCID.
Sent from my HTC One S using Tapatalk 2

usaff22 said:
As far as I know the issue is only caused by people who previously had SuperCID.
Click to expand...
Click to collapse
I thought I saw a report of a fully stock device and one htc__001 cid as well. I can't find them at the moment, but this is also why I started this threat. But there seem to be more of these reports of supercid indeed, though there are also allot with supercid who successfully updated.

My phone is bricked too
Orginal CID was HTC_0001 (maybe), branded by 1&1 Germany
but changed to 11111111 to flash a unbranded RUU (what had worked)
I had Stock Recovery and relocked bootloader

My phone is bricked too
SuperCID 11111111 Hboot 1.14 Recovery Stock y Relocked bootloader.

My phone is bricked too
Orginal CID was HTC_203 (maybe), not branded by telecom company - France
but changed to 11111111
I had Stock Recovery and relocked bootloader and flash the 2.31 RUU

hellgod said:
My phone is bricked too
Orginal CID was HTC_203 (maybe), not branded by telecom company - France
but changed to 11111111
I had Stock Recovery and relocked bootloader and flash the 2.31 RUU
Click to expand...
Click to collapse
Dam it didnt mean to hit thank so enjoy that lol.
@Vauix, did you run a RUU before updating? if so what one?

let's discuss who and what options tried to output the list of sections? How you think why it happened?

All of them seem to be caused by SuperCID. But the updater script allows flashing for SuperCID, so I wonder why they get bricked.
Sent from my HTC One S using Tapatalk 2

I agree with you. But what it is necessary to undertake that Ubuntu saw sections?

Same here.
SuperCID and ota
Now nobody can call me

Same here.
SuperCID too

Darknites said:
Dam it didnt mean to hit thank so enjoy that lol.
@Vauix, did you run a RUU before updating? if so what one?
Click to expand...
Click to collapse
Yes I ran a RUU prior to flashing this update, i didn't chance anything to the rom yet but to search for the OTA. it was the RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
I thought about my supercid before I ran the RUU but i thought the worst thing that could happen was i could get a error that it couldn't flash it.
Its rather weird that some guys with supercid managed to flash it successfully. And i still think I saw some people with other cid's with bricked devices.

SuperCID too, previously Vodafone germany, unbranded an relocked ...

I ran the OTA update twice on my supercid'd device successfully.
In opposite to what I could read here, my bootloader was unlocked before and still after the update.
The first time I ran the update I forgot to reflash stock recovery. The phone started updating and rebooted, but no changes had happened. After restoring stock recovery and downloading the update again, I successfully updated.
As I couldn't get root I restored Venom and downgraded my new hboot from 2.15 to 1.06.
Today I started a second try successfully without a glitch.
Basically I keep an untouched nandroid backup of every new rom installation on my local harddisk. This means in case of custom roms I do a nandroid before the first boot.
As this is not possible on stock recovery I change back to custom recovery after the first boot, doing my backup then. I'm just checking the needed boxes otherwise I only proceed during the setup - the complete customization is done afterwards.
In this case I restored a backup called 2012-08-23--08-18-16_htc_stock_2.31
Stock here means: No apps, no customizations, no nothing, simply: stock and supercid.
After that was done I restored apps with Titanium.
That's how it worked (pretty simple) Maybe this will help you find some reasons for what has happened to your devices.

Same problem here...
SuperCID

All people here seem to have SuperCID, I have not.
I got my ville for about 7 months now and never had SuperCID.
I did it like everytime:
-Wiped everything ( Data / Cache / System )
-Flashed Stock Recovery
-Relocked
-Flashed 2.31 Europe RUU in Bootloader ( yes, that works but I guess noone knows )
-Downloaded 4.1.1 Update and let the Device do its magic
Now my phone is bricked.
Strange enough, a good friend of mine whos barely able to use its phone, got the same issue.
Im 100% sure he doesnt have any modifications done to his device.
Already tried the Ubricking-Tutorial but the Partitions just dont show up :-/

I did the super CID, too. No my phone is dead. Won't even charge.
I tried to do Enumerating the partitions but could only find up to 3. No 4 or 12.
Please help :crying:

SuperCID, German ONE S unbranded. Dead.
Unbrick/Downgrade instruction did not work here.

[Q] Failed attempt at re-branding K2_UL - help needed

I have been faffing about with S-OFF and the like in an attempt to de-brand my phone to stock HTC with root (the handset was an Orange UK CID). I've been at this for a couple of days now and have seemingly got myself stuck in a corner with the 2.0 hboot, which seems to be what's causing the problem for me - I was previously able to run the stock ICS RUU, but can't any longer.
Handset: HTC One SV LTE (model ID PL8010000)
*** UNLOCKED ***
K2_UL PVT SHIP S-OFF RL
CID: HTC__001 (have also been in SuperCID 11111111 numerous times)
HBOOT: 2.00.0000
RADIO: 1.15.40a.00.04
OpenDSP: v9.2.0268.1214
eMMC-boot
Mar 14 2013, 22:10:43-1
OS at the moment is Viper, because that's all I can get to install. None of the OTAs work (various errors relating to parsing android-info.txt and remote access issues in fastboot). The trouble with Viper is that the radio is apparently knackered, because I can't get a signal at all, and I was on stock JB and on ICS.
If anyone can provide me with a stock ICS 1.00.0000 HBOOT, I can try the RUU again at least. OTAs don't work from there, but it'd be a start. Any other ideas would also be greatly appreciated!
EDIT: Sorry, I forgot I'd already found a stock HBOOT and used it earlier, so have done that again now. Have now run RUU and am on stock HTC__001 version of ICS (K2_UL_ICS_40_HTC_Europe_1.17.401.5_R_Radio_0.12.40.00.14_2_10.49.40.11L_release_301902_signed). However, I still need help getting updated through the OTAs, of which I have 3 in .zip form:
OTA_K2_UL_JB_45_S_HTC_Europe_2.14.401.2-1.17.401.5_R_release_308698hqk34kifwjk0g071
OTA_K2_UL_JB_45_S_HTC_Europe_2.14.401.6-2.14.401.2_release_311966gsyc11xrfb40ox3c
OTA_K2_UL_JB422_SENSE50_MR_HTC_Europe_3.11.401.1-2.14.401.6_release_338297mseg08soslxcubit
METHOD 1:
When I try to run any of the above via fastboot oem rebootRUU, it fails and says it can't parse android-info.txt. I've checked the android-info in all three files, and the CID I have on the handset is listed in there, and the model ID is correct. I have verified with fastboot getvar cid that the CID is indeed HTC__001, so I don't understand what the problem is.
METHOD 2:
I've tried re-locking the bootloader and running again, but that still fails as above.
METHOD 3:
I've also tried just flashing the firmware.zip alone, but that spits out errors relating to the checks at two early stages in the updater script:
assert(check_cid(getprop("ro.cid") - I'm not sure why that fails given that the CID is correct for the OTAs, but it works if I just delete this check
assert(getprop("ro.product.device") == "k2ul" || - again, this is the correct device I'm trying to apply the OTA to, so I don't understand the issue
Sorry about the confusion in the initial post; any help would be greatly appreciated!

Your task should basicly be the easiest today, lol.
Get back to SuperCID, flash the RUU again (if needed, the 1.0 hboot before), and then, when phone is booted into android, let it search for updates.
Download and installing should go fine, because you are stock from the RUU and have SuperCID. Do this until no updates left and you are on 4.2.2.
You can also orientate on this guide.

old.splatterhand said:
Your task should basicly be the easiest today, lol.
Get back to SuperCID, flash the RUU again (if needed, the 1.0 hboot before), and then, when phone is booted into android, let it search for updates.
Download and installing should go fine, because you are stock from the RUU and have SuperCID. Do this until no updates left and you are on 4.2.2.
You can also orientate on this guide.
Click to expand...
Click to collapse
Man, I am so sorry. Not only did I fix this myself, I found out what I'd done to cause the ballsup. You know how I said I was getting 0 signal on the network? When changing the CID, I had accidentally overwritten the first 4 digits of the IMEI, so it wasn't recognised as valid any more. Just re-edited mmcblk0p4 to reinsert the original IMEI and it's now getting a signal. Prior to that, I managed to flash HBOOT 1.0 and run RUU then flash the OTAs manually. Have also reflashed TWRP 2.7 and backed up so I can hopefully recover faster from any more mess I make for myself...
Having said that, when I was trying to get the OTAs actually over-the-air, it kept reporting no updates available. Do you think that's just a result of the IMEI issue or do I need to be fully S-ON and locked (as in HTCL) to get OTAs? Do I also need the stock recovery?
Thanks very much for the reply, mate. I wouldn't have been able to do this stuff without your guides and replies on this forum, as well, so I'm grateful for your help.

Well, hard to say with your OTAs, because i never had a non-working CID.
But to run the official OTAs you need for sure a stock recovery!

old.splatterhand said:
Well, hard to say with your OTAs, because i never had a non-working CID.
But to run the official OTAs you need for sure a stock recovery!
Click to expand...
Click to collapse
The CID's fine, it's just the fact I overwrote it onto part of the IMEI... at one point I had manually edited HTC__001 into mmcblk0p4 then later rewritten it via the set cid command, which resulted in that line of the file being set to "HTC__001_001" because I'd keyed it in with the _001 overwriting the first 4 digits of my IMEI. Because I am an idiot, it would seem. Nonetheless, when I was requesting the updates OTA the CID was working fine. However, I only had stock recovery *some* of those times I tried to get OTAs, and I can't say whether the IMEI ballsup was there right from the start or not because I have no idea when I did that. I'll possibly reflash from the RUU again at some point and attempt an OTA on stock recovery with the correct IMEI, but for the time being I'm playing around with Viper because half the reason I started faffing about in the first place was that I thought some of the stock bloatware on the Orange firmware was possibly slowing down the handset (which it evidently was, since it remained slow post-fstrim) and Viper lets me strip the HTC crap out as well.
Anyway, sorry about the dimwittedness, and thanks very much for your help! :good: