I rooted and S-offed my G/F's Desire to unbranded the UK vodafone version so that she was on stock, and thus would get updates like normal, i did this by flashing a RUU 1.47 - thus removing root but leaving S-off.
Her dippy brother thought he knew what he was doing and flashed the new 2.10 RUU so that she'd have sense 3.0.
It Apparently all went well, but then just hangs on the white HTC screen.
Can anyone Offer any help on how to fix this?
Edit: Fixed it, just flashed the 1.47 RUU again - sorted
hey try this
Mate there is a software for flashing HTC phone via PC. I think you don't have cwm NCIS u flashed Ruu. So from the link get that software and install HTC drivers in PC. install that software and flash as cwm.forum.xda-developers.com/showthread.php?t=794638
Related
Guys,
I have found a definite issue regarding trying to debrand and flash the 2.3.4 OTA update to my Bell debranded sensation...Here are my steps and results...
1. Performed Revolutionary on shipping Bell Canada Sensation
2. Changed CID to 11111111 via fastboot.
3. Flashed generic UK 1.35.401.1 software via RUU file.
4. Downloaded 2.3.4 OTA update.
5. Try to install the OTA update.zip from recovery, it errors out with Status 7 error. No matter what CID I use, I always get this error status 7.
6. Change CID to HTC__E11 to try and get the OTA update automatically, Downloads and then gives me a "variant system software" error when it goes to install. I've never heard of or seen this error before.
7. Run Revolutionary again and then flash the update.zip. It appears to successfully flash, but when the phone reboots, all I get is a black screen. the phone makes noises and appears to be functioning somewhat, but screen is black.
8. I am now thinking, great, I just bricked my phone...
9. Reboot into hboot. It still shows Bootloader of 1.17.0011, which is strange because the OTA is supposed to update it to 1.18.0000.
10. I then change the CID to 11111111 and reflash with the 1.35.401.1 RUU and thank god the phone is back to working condition.
It appears that there is either a hardware difference or something really low level that is being changed with this new update and it might not work properly with the different radio from the Bell Canada version with the 850/1900 radio, but I don't understand why flashing to the 1.35.401.1 RUU works fine. If anyone else can shed any light on this or give me any hints, I would appreciate. I thought my experiences might help the devs out there further understand the new OTA and the Sensation software/hardware. My end goal is to have the most up to date stock unbranded software installed on my Sensation. I am using with AT&T if anyone is wondering.
Y2J
y2jdmbfan said:
Guys,
I have found a definite issue regarding trying to debrand and flash the 2.3.4 OTA update to my Bell debranded sensation...Here are my steps and results...
1. Performed Revolutionary on shipping Bell Canada Sensation
2. Changed CID to 11111111 via fastboot.
3. Flashed generic UK 1.35.401.1 software via RUU file.
4. Downloaded 2.3.4 OTA update.
5. Try to install the OTA update.zip from recovery, it errors out with Status 7 error. No matter what CID I use, I always get this error status 7.
6. Change CID to HTC__E11 to try and get the OTA update automatically, Downloads and then gives me a "variant system software" error when it goes to install. I've never heard of or seen this error before.
7. Run Revolutionary again and then flash the update.zip. It appears to successfully flash, but when the phone reboots, all I get is a black screen. the phone makes noises and appears to be functioning somewhat, but screen is black.
8. I am now thinking, great, I just bricked my phone...
9. Reboot into hboot. It still shows Bootloader of 1.17.0011, which is strange because the OTA is supposed to update it to 1.18.0000.
10. I then change the CID to 11111111 and reflash with the 1.35.401.1 RUU and thank god the phone is back to working condition.
It appears that there is either a hardware difference or something really low level that is being changed with this new update and it might not work properly with the different radio from the Bell Canada version with the 850/1900 radio, but I don't understand why flashing to the 1.35.401.1 RUU works fine. If anyone else can shed any light on this or give me any hints, I would appreciate. I thought my experiences might help the devs out there further understand the new OTA and the Sensation software/hardware. My end goal is to have the most up to date stock unbranded software installed on my Sensation. I am using with AT&T if anyone is wondering.
Y2J
Click to expand...
Click to collapse
I would venture to guess you're not aware that you should probably not (at least not now), do an official FOTA/OTA on an unauthorized S-OFF Sensation.
The official HTC 2.3.4 OTA that came out a few days ago, LOCKS your device. It puts it back into an S-ON state.
Unless something has changed, if you have S-OFF via Revolutionary....stay far away from official HTC updates.
Something has changed...revolutionary now supports the new "locked" bootloader!
Hoggles said:
I would venture to guess you're not aware that you should probably not (at least not now), do an official FOTA/OTA on an unauthorized S-OFF Sensation.
The official HTC 2.3.4 OTA that came out a few days ago, LOCKS your device. It puts it back into an S-ON state.
Unless something has changed, if you have S-OFF via Revolutionary....stay far away from official HTC updates.
Click to expand...
Click to collapse
I'm well aware that the the official HTC 2.3.4 OTA locks the device. As long as I have a debranded Sensation running the latest and greatest firmware/software, that is all I am looking for. And now that Revolutionary works on the new HBOOT there shouldn't be much trouble getting back to the original shipping software. I still am curious as to what is causing this "Error Status 7" error code.
So how can I update my sensation with s-off?
A bug in me from being updated.
That would really interest me too! don't want to be S-ON again to make this update. Another question (maybe off topic): how can i update to new S-OFF version 04pre4? I'm now on 03pre7.
Hi
I have the exact same problem as yours, what can we do to update it?
Same on Swisscom-branded phone
I tried the OTA on my swisscom phone, it reboots and I get an exclamation mark with a blue droid. Waited 10 minutes just in case, but no change.
Removed battery and rebooted. Phone still ok, but not updated obviously.
I'm not sure it will remove S-OFF, but I don't care, HTC provides an official procedure for that and we have what we need.
But I need this update to work on my rooted, S-OFF stock sensation. Will try again anyway...
EDIT: I tried going into recovery and manually flashing the OTAxx.zip file, but it gave me an assert_failed: check_cid!? Though I never changed the phone CID! So why propose me an update on my phone if it's the wrong one??? Not sure I want to change the CID of my phone now.
I bought my used Desire S and it was rooted with revolutionary so i could not get OTA from 2.3.3 beyond. I read some threads but nobody was telling me which RUU i needed as my phone was unbranded and i was not sure about its origin. I managed to bring back the official stock Rom and original radios, hboot and downloaded and installed 2.3.5 successfully.
Nobody could help but finally i managed to take the risk and it paid off thankfully.
It is the easiest and fastest way to unroot, remove superuser, revolutionary and to restore hboot back to normal and S-On again, to get official updates including ICS.
Download the attachment "usmanxhmed.rar", it has Android Flasher and FlashENGHBOOT.
Attach your phone to PC with USB cable, make sure you have HTC fastboot drivers installed.
Open Android Flasher and select bootloader and browse to the file FlashENGHBOOT which you downloaded in file "usmanxhmed.rar", boot phone into fastboot and click flash.
It will remove REVOLUTIONARY **** from the phone.
Now download your specific RUU from this link http://www.filefactory.com/f/c64d333a2755a421/ i was unsure which is my RUU for the phone as i bought it second hand, my phone was unbranded, i matched the software version and radio version in my software information of the phone and downloaded the specific RUU.
After flashing the RUU my Desire S became factory fresh and back to S - ON and updated my phone with Android 2.3.5 and Sense 3 and hopefully/ may be i will get ICS in future as well
Good guide cheif :thumbup:
Sent from my HTC Desire S using XDA
Thanks ttocs99
Quick question, this might not be the best spot for it but it is somewhat related.
My desire s is branded/locked to vodafone portugal, so i have no specific RUU in that list. What will happen if i use Europe one? Or UK's Vodafone?
Best Regards,
Daniel
dan_alexandre said:
Quick question, this might not be the best spot for it but it is somewhat related.
My desire s is branded/locked to vodafone portugal, so i have no specific RUU in that list. What will happen if i use Europe one? Or UK's Vodafone?
Best Regards,
Daniel
Click to expand...
Click to collapse
Vodafone UK !
I have a Desire S from Vodafone Germany and it works perfect with the Vodafone UK RUU.
Stefan
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
I have a desire s, s-on, hboot 2.00.0002, radio 3822.10.08.04_M. It was bought in UK.
I currently have the Vanilla ICE v2.0 rom installed, however there are some features that are really annoying me, and I would like to try the official HTC ics update.
I have been to htcdev and downloaded the ICS RUU (after selecting WWE as the region).
However, when I run it it bombs out, with error 155, and suggests I download the correct version.
From what I can see on here, I've been told that the WWE version should be correct version for UK, is this correct?
I did try downloading Endymion 3.5, and installing that onto my phone, however when I boot my phone, it keeps saying that the phone, messaging and pretty much everything has crashed! I tried running the RUU with that installed, and it got as far as trying to send the rom over, however it failed. Unfortunately, I cannot remember the exact error. It *may* have either been 155 or 175.
I have since read this thread -> http://forum.xda-developers.com/showthread.php?t=1655832 about re-locking the bootloader, however I have not yet managed to restore my phone to stock.
I am currently downloading a rom from here -> http://forum.xda-developers.com/showthread.php?p=31345345&highlight=link#post31345345 in the hopes it will work.
Does anyone know if you HAVE to have either a stock rom, or an older rom, in order to run the ruu?
I tried re-locking the bootloader, and running the
RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed
file I downloaded, however it got as far as updating the signature, and failed saying I need to get the right version.
Can someone PLEASE help.
How can I downgrade my phone to stock gingerbread, and why is the WWE ruu not working on my o2 (uk) branded phone?
check this out: http://forum.xda-developers.com/showthread.php?t=1318919&highlight=skanob
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.