[Q] [S3] Help for cid HTC__622 - HTC One S

Hi to all,
here is my story/problem:
Bought Htc One S (S3) from HK, CID HTC__622.
Latest WWE for cid HTC__044 isn't working (obviously).
No way to flash OTA or RUU 'couse there is none of these for HTC__622.
No way to change CID/SuperCID 'couse this is S3 version.
No way to flash latest custom roms 'couse my hboot isn't upgraded (still with v.2.09.0001).
I've succeded (after some panic moments) only in flashing custom recovery and rooting (and for this i owe HUGE THANKS to user azzledazlle who spent a whole day helping and de-noobing me).
I'm asking...no, i'm BEGGING for an advice. Any advice*.
*(if possibile different from "Buy another device")

Related

HTC India to HTC Europe

Hi,
I'm in the UK and I bought my Sensation XE from Hong Kong and use it with a T-mobile sim.
The mobile seems to think it's Indian and I would like to change it to a UK or euro setup.
At present it has HBOOT 1.18 and has CID HTC__038 with ro.carrier HTC-India. Software number is 1.77.720.103.
I had to use locale app to change it from india to UK so that I could have a UK keyboard/dictionary and also receive UK news in the news app.
Now it's coming up to release time for ICS and I would like to make my phone so that it receives the UK version.
Is it possible to flash my phone with the most recent Euro RUU to do this? If I do will I still need to change the CID to HTC__001 and will the RUU change all the bits relating to India that show up when you run the CID Getter app?
I've tried running the RUU > "RUU_PYRAMID_LE_HTC_Europe_1.73.401.4_Radio_10.58.9035.00U_10.15.9035.02_2_release_220036_signed" and it looks as though it will change my software version to a version lower than it is currently on. From what I have read on the thread > http://forum.xda-developers.com/showthread.php?t=1193033&page=2 about "How to debrand...." I was under the impression I might need to use revolutionary to get S-OFF, change my CID to HTC__001 or HTC11111 run the RUU then put S-ON again or leave it off.
All just a little confused as to what's best to do.
Sorry for the long post with multiple questions.
I updated the Mrs Desire to Runnymede AIO without too much headache the other day so thought I'd look into sorting out my XE.
Cheers
Finally got there by myself.
Had to HTC Dev unlock bootloader. Flash recovery with 4EXT recovery. Use 4EXT recovery to flash an old ROM with HBOOT 1.17. Use Revolutionary to get S-OFF. Use RUU for most recent Euro GB ROM.
No have S-OFF, Unlocked bootloader, 1.18 HBOOT, Stock HTC european ROM. CID HTC__001.
Still no ICS update available when checking updates though

[Q] Downgrade from 3.04.401.1?

Hello all,
I'm having a serious issue ... i want to switch to stock. I had Virtuous Saga ROM before which upgraded my HBOOT to 3.04.401.1. Now i flashed older hboot (i didn't know it is wrong) which made me only have bootloader.
Old Ruu's don't work. HtcDev Unlock ditto. i guess i need to have the RUU for 3.04.401.1 or newer to have the phone working before i change version number to downgrade ...
I can't find that RUU ... any help on that?? or other advice?
Thank you,
Edit:
The thread here contains the same problem, the OP claims he fixed it and that he has the newer RUU file. Though i can't find that RUU
Anything friends? Any help please??

[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] Help with TMB101 branding

Hi guys,
I would like some help with flashing a Stock RUU onto my desire s.. I have gotten it S-On and removed revolutionary.
You can see my phoneinformation from adb below i attached it. Hboot 0.98 and a T-MB101 branding.. Build(main) 2.10.401.5 german phone
The problem is I cannot find any RUU to flash which will work for my Phone (I open them as admin)
I have tried the TMO 1.3.111.1 with the RUU error 140
I have tried the 2.10.401.5 and 8 and 9 builds for EU but they all give me error 131 (as they are not for branded phones?)
What can I do know what RUU could work how do I get the TMO to work? Are there any more RUUS I could even try to use? Should I try a Goldcard? Any Ideas? Thanks guys..
Please Help

Soft Bricked HTC One S (S3) on Hboot 2.09.0001 - S-On (VilleC2 PVT SHIP)

Hello,
First time poster so please be gentle. (I am somewhat noobish when it comes to remembering terms and whatnot)
I've gotten myself into quiet a pickle here. I ran a successful RUU on my handset (ofc with SuperCID as well as S-off, unlocked bootloader and root) and had the time of my life. I was back to stock! A day later I wanted to update you see but got the "variant system detected" problem. Considering that I was still S-off and SuperCID'd I instead decided to change my CID (yes, that wasnt very smart) instead of just going S-on and then updating (I'm also not too familiar with OTA so yeah....). I had 2 RUU's on my desktop (the current one i used was for ICS a.k.a 4.0.4 Asia WWE Telkomsel whereas the other one i was planning to use was Vodafone UK JB), Me being the idiot I was clicked on the Vodafone one, searched up the CID for Vodafone UK (VODAP001) and rewrote the CID.
I then proceeded to S-On so i could get OTA updates working finally and again being the idiot I am ran the Vodafone RUU.
This cleared all my data and wiped the OS clear off my phone.
So now im stuck with:
VilleC2 PVT Ship S-On
Hboot -2.09.0001
Radio-16.05.20.16_M2
OpenDSP-v05.6.0.2226.00.0418
eMMC-boot
as well as a CID for Vodafone UK (VODAP001)
And here I am now. (sorry about the storytelling)
I have tried 2 roms so far which are:
- mcOneS3_1_0_0_DeODEX (yes i know, my Hboot wasn't right. Tried it anyways)
- BackToBasics_V3
Neither worked and I've been searching the web for more roms as well as an RUU that can match all my details (which is very unlikely).
I've also been trying to search for [ROM][DISCONTINUED][S3][18 FEB] TrickDroid 6.0.0 and was wondering if anyone had a copy lying around that they could provide since Trickdroid for the S3 has been discontinued:crying:. If someone could provide me that, I would be extremely grateful. Also any advice is great too.
Thanks~

Categories

Resources