Hi all!
I've been having a big problem and I can't solve it on my own since I can't understand what am I doing wrong...
I tried to install a custom os on my HTC one S but something went wrong (I can't remember exactly what) and my HTC One S was just rebooting in TWRP recovery without loading the system.
I assume there is no system anymore and I don't know what to do..
Some friends of mine told me that I should return to stock ROM throughout RUU Ville and I've tried to follow some tutorials about that failing miserably...
I've been going crazy for the last month trying to figure out which RUU I should download since my model is VODAP102 and it seems that this CID is pretty much uncommon.
I don't know what to do and I'm at the point of no return and giving up, please help me
Wrong section, head over to the HTC One S thread for help.
Anyone?
Sorry for having to say that but the Information you provide are pretty much useless. According to your post I assume you don't know what S-OFF is and therefore your phone is probably S-ON (stated in Bootloader Mode, btw), right? Therefore you need a RUU that matches your firmware or belongs to a higher firmware version.
Set up an ADB/Fastboot environment (if you haven't already): Download this archive, create the directory "C:\Android" and unzip the archive into that folder. Right-click into the folder while the Shift button is pressed and choose "Open command line here" (the naming might be a bit different - I only translated it from German into English). Use the command "fastboot getvar all" and look at the line with "version-main" (Edit: never post the fastboot getvar all output somewhere on the internet unless you removed your IMEI and your serial number). That's your currently installed firmware. Besides you need to look at the line with "product" to find out whether you own the Snapdragon S4 model (Ville aka vle) or the Snapdragon S3 model (VilleC2). Search on this site (for the Ville) or this Site (for the VilleC2) for a RUU with the same or a higher version number. Be aware that the 3 numbers behind the second dot always have to stay the same. E.g. a phone with S-ON and firmware 2.31.401.5 can also use a RUU for 3.16.401.8 but not for 2.21.401.10.
If your version-main is deleted (happens if you flash a faulty TWRP version - I forgot which one it was because it's a pretty old version) then you should try to use the latest RUU that belongs to your SKU (those are the 3 numbers behind the second dot). The CID VODAP102 either belongs to SKU 161 or 166. (I know that HTC changed that somewhere in the past but I forgot when that was. On the M9 VODAP102 belongs to 161 but I'm not sure whether this applies to the Ville, too).
If there is no RUU available you could use your only hope is Llabtoofer's RUU Service.
Related
Hi,
Apologies that this will very much be a noob post but help would be very much appreciated. I bought a HTC sensation XE which was imported from Taiwan. I wanted to use an RUU that is from Europe (the most recent one I found, 1.73.401.4), so that I wouldn't have all the branded apps. To do this, I first followed the htcdev unlocking guide, and then tried to change the CID to superCID, which it did not allow. Instead, I changed the CID to HTC__001 which I thought would work for Europe RUU. I then tried running the RUU exe file, but it eventually came up with a 155 error and did not install. From what I can gather, this is because I actually needed S-OFF to change the regions of the device.
I read that it was best to undo the htcdev lock (or perhaps even to not have done it in the first place). So, I ran "fastboot oem lock". This seems to have worked, because the bootloader now reads 'RELOCKED'. However, when I load the phone and click on bootloader it flashes a load of green lines like this:
sd checking...
loading...[PG58DIAG.zip]
No image!
Loading...[PG58DIAG.nbh]
No image or wrong image!
...
Otherwise it seems to be loading the original ROM without any issues. I cannot find any files on the SD card that include PGD58DIAG in their name. I have now changed the CID to HTC__622, but I'm not sure if this was the original one (is there any way to find out now?).
Does anybody have suggestions on how I proceed from here? Just to recap:
- Taiwanese import HTC sensation XE
- Used HTCdev to unlock, but have now relocked
- Have changed the CID to HTC__001 and now to HTC_622; may not be original.
The questions I have are:
1) Are the green lines of text that I am getting about PG58DIAG important?
2) If I want to debrand the phone and ideally move to European unbranded RUU, what should I do now? Should I try S-OFF and then changing to superCID as in the guide by Alexp999 here (http://forum.xda-developers.com/showthread.php?t=1193033) - i.e. is it safe to do this, despite the green lines of text and having re-locked the htcdev?
Thank you so much for any assistance. I've really tried looking everywhere on here and can't seem to find a guide or thread that takes into account all my issues!
Oliver
**********
Software number 1.77.709.104
Baseband version 10.58.9035.00U_10.15.9035.02_2
Build number 1.77.709.104 CL239628 release-keys
Hboot: 1.18
1. That green "loading img" message you keep getting almost always normally occurs when you enter boot loader....it checks for RUU file in sdcard root folder. This is normal.
2. Root...super cid...the fastboot flash ruu
Just as FYI. Wasn't sure if you knew this so forgive me if you did.
RUU flashed in fast boot must my named "PG58IMG.zip"
RUU must be in root folder of sdcard
Sent from my HTC Pyramid using XDA
Choose the correct firmware from here
super sid not needed
Read and follow the instructions carefully
Thanks for the advice and the reassurance! From the sounds of things I shouldn't go ahead until I have the original RUU downloaded in case things go wrong. Can't seem to find it for 1.77.709.104 anywhere, so perhaps I'll wait to change ROMs until it gets posted somewhere!
hey guys,
I have a one s with the following info
cid = t-mob102
android version = 4.03
htc sense = 4.0
software number = 1.84.531.2 710RD (MoDaCo.one ir3)
i wanted to go back to stock rom, so ive downloaded a RUU, but it wasnt the right one.(says ERROR [130]: MODEL ID ERROR)
i wonder if anyone knows which ruu i should use to get back to my phones stock?
its kinnda urgent.
thanks in advance
m2afs said:
hey guys,
I have a one s with the following info
cid = t-mob102
android version = 4.03
htc sense = 4.0
software number = 1.84.531.2 710RD (MoDaCo.one ir3)
i wanted to go back to stock rom, so ive downloaded a RUU, but it wasnt the right one.(says ERROR [130]: MODEL ID ERROR)
i wonder if anyone knows which ruu i should use to get back to my phones stock?
its kinnda urgent.
thanks in advance
Click to expand...
Click to collapse
Goto http://www.4shared.com/folder/jKN2qjTl/HTC_Ville_RUU_Collection.html
I think there are a few T Mobile RUUs there. On the second page there is
RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501
which likely should work.
On the first page there is also an upgraded RUU for T Mobile
RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04
If your OK with an upgrade go for that one. Just remember it may upgrade your bootloader and radio. If you wanted to flash older radios after that, you would have to go through a more complicated bootloader downgrade.
Those should work.
AKToronto
actually the ruu i have downloaded that says its the wrong model is exactly the following
RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed
as Ive looked inside its ROM this ruu is for t-mob010 not for t-mob102. and i guess thats why it fails.
what now?
Ive realized my phone loses signal from time to time and after a research i found out that upgrading to that specific version will solve the problem, but right now i cant really get into it coz i don't know the exact RUU to use.
the process i tried to do this is
1.i tried the normal way
-boot into fastboot
-relock the bootloader
-reboot to fastboot again
-run the ruu
-got error 130
2.i tried without locking the bootloader
the same process
-got error 155
i dont know if im missing something here, im new to android and all the flashing stuffs, any help would be appreciated.
So, I've found out that T-MOB102 refers to T-Mobile Austria, and I should be looking for one with this signature x.xx.112.x.
Still I haven't found any with the signature for ONE S.
Any Suggestions?
still nothing on the TMA T-MOB102 T-Mobile Austria RUU.
I've tested every RUU in Here: filefactory.com/f/cf061f69b5bf7878/
None of them were mine, how is it possible that there's no RUU made for my phone type.
Should I Change my CID? Is It possible?
m2afs said:
still nothing on the TMA T-MOB102 T-Mobile Austria RUU.
I've tested every RUU in Here: filefactory.com/f/cf061f69b5bf7878/
None of them were mine, how is it possible that there's no RUU made for my phone type.
Should I Change my CID? Is It possible?
Click to expand...
Click to collapse
So I think you have two options. One is CID, or two is to keep trying to find that RUU.
1. There is a link to Super CID instructions in the dev forum at http://forum.xda-developers.com/show....php?t=1671643
-Do read a bit of the thread. You can still only flash a RUU that has a bootloader version equal or higher than what is on your phone.
2. If there is a RUU that you think exists that Football has not posted in his thread, than I suggest PM ing him. Thats how I was able to get the three Bell Mobility RUUs onto FileFactory. He was pretty helpful when I PMed him myself.
Cheers,
AKToronto
How Can I PM Football?
m2afs said:
How Can I PM Football?
Click to expand...
Click to collapse
Click on his name in any of his posts. Then click send message. I use PM to stand for private message.
AKToronto
I know there are several threads like this one but I prefer not to write another RUU request while you're answering to another user
So, I got a HTC One S S3 yesterday... I began to unlock it because I wanted to change its CID. I found that in the S3 version the CID can't be changed (still) when I had already installed the TWRP Recovery.
Now I'd like to go back to stock, but there is not a RUU compatible with my device: It has VODAP102 as CID, but the RUU for Vodafone AT here doesn't work. I found the kernel source for the same software version I have in htcdev.com, my question is: is it possible to build a RUU or at least a boot.img from it?
The sources can be found in htcdev /devcenter/downloads (sorry but being new I can't post direct links!), HTC One S as Device, Vodafone as Carrier and UK -
1.11.161.133 as software version. Actually I am in Italy, but the software and kernel version are exactly the same.
Thank you in advance.
Bump to first page and a little addendum:
I've read again all the possibilities I have with this phone, and if I have understood accurately then I'm forced to go back to stock, roms like the ThickDroid seem to require a non-branded CID, but that's the point... it is the CID that's compelling me to maintain this original Vodafone software, otherwise I would have already installed the HTC "basic" rom.
Am I missing something?
Thank you again!
Have you tried looking on HTCRUU.COM?
Check your radio id on the bootloader screen then flash the appropriate ROM
mikejasonsmith said:
Have you tried looking on HTCRUU.COM?
Check your radio id on the bootloader screen then flash the appropriate ROM
Click to expand...
Click to collapse
Yes I checked, but they have just unbranded RUUs, here in the forum there's one RUU for Vodafone but the region isn't the same as mine.
I've read that it is possible to flash an OTA update deleting the string that checks the CID - I'll have to take a look about that (moreover, it seems very difficult to find .zip OTA updates for this phone...).
Nevertheless I'd like to find this RUU update too - it is an important option too. So... bump to first page.
I am having some troubles with finding the proper RUU for my phone.
I have a dutch vodafone branded phone which I rooted and flashed with CWM. I am still on 1.53 and i want to upgrade to 1.78 because of the home-screen button bug. I hope the OTA update fixes it.
In order to update my phone, I need to revert to stock and therefore I need the original shipped RUU .
Can i use the "RUU_Ville_U_Vodafone_UK_1.78.161.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258386_signed" ? I know this is UK version but there seems to be no NL version and my phones also downloads OTA_VIlle_U_Vodafone_UK_1.78 itself. So I figured i could also use the UK RUU. Is this correct?
Thank you in advance.
Anybody who knows the answer?
petersm said:
I am having some troubles with finding the proper RUU for my phone.
I have a dutch vodafone branded phone which I rooted and flashed with CWM. I am still on 1.53 and i want to upgrade to 1.78 because of the home-screen button bug. I hope the OTA update fixes it.
In order to update my phone, I need to revert to stock and therefore I need the original shipped RUU .
Can i use the "RUU_Ville_U_Vodafone_UK_1.78.161.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258386_signed" ? I know this is UK version but there seems to be no NL version and my phones also downloads OTA_VIlle_U_Vodafone_UK_1.78 itself. So I figured i could also use the UK RUU. Is this correct?
Thank you in advance.
Click to expand...
Click to collapse
Well you should probably Run the RUU.exe without connecting the phone. When it runs, it places a "firmware.zip" in a temporary folder (please search for the exact location of the temporary folder as I don't exactly remember it). Open the firmware.zip file to view its contents. It should have a "android-info.txt". Open it and you'll see the supported CID. If it matches with your phone CID, you're good to go.
To get your phone CID, use CID GETTER from store. It shows CID in red at the top of the app.
Sent from my HTC One S using Tapatalk 4 Beta
khan.orak said:
Well you should probably Run the RUU.exe without connecting the phone. When it runs, it places a "firmware.zip" in a temporary folder (please search for the exact location of the temporary folder as I don't exactly remember it). Open the firmware.zip file to view its contents. It should have a "android-info.txt". Open it and you'll see the supported CID. If it matches with your phone CID, you're good to go.
To get your phone CID, use CID GETTER from store. It shows CID in red at the top of the app.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you. I read about that but I couldn't find the firmware.zip. I took a guess and it turned out that the RUU is correct. So for other dutch users on this forum: I can confirm that 1.78 UK Vodafone RUU works on dutch vodafone branded phones.
Hello everyone! Sorry for my bad English
I've got a HTC One S (HTC__017) with unlocked bootloader, S-ON, HBOOT 1.06.0000 and Radio 1.11.50.05.28 and recently, i'm a little motivated to give a try for a Custom ROM (Obviously, there's more work to do with the S-ON) but i want to prevent a big accident in the process and i need the correct RUU File for my phone, I've been looking on my own the file but I couldn't find it
Now, someone knows which RUU file can I use? I'm novice with HTC Phones and this is new for me
Thanks in advance
Auraburst said:
Hello everyone! Sorry for my bad English
I've got a HTC One S (HTC__017) with unlocked bootloader, S-ON, HBOOT 1.06.0000 and Radio 1.11.50.05.28 and recently, i'm a little motivated to give a try for a Custom ROM (Obviously, there's more work to do with the S-ON) but i want to prevent a big accident in the process and i need the correct RUU File for my phone, I've been looking on my own the file but I couldn't find it
Now, someone knows which RUU file can I use? I'm novice with HTC Phones and this is new for me
Thanks in advance
Click to expand...
Click to collapse
It's easier to find the correct one if you know your firmware version/build number. If you're still using stock rom you can find it in settings>about>software information>more. If you already deleted the stock system on your phone you need to use
Code:
fastboot getvar all
in fastboot mode (look at the line beginning with "version-main"). Since you already unlocked your phone I assume you know how to use fastboot with the windows cmd.
RUUs can be found here for example. Just use the search function of your browser and be sure that you download a RUU and not an OTA. Since there are two versions of the One S you need to be careful not to use VilleC2 (Snapdragon S3 with 1.7 gHZ) files on a Ville (Snapdragon S4 with 1.5 gHz) and vice versa (this rule applies on roms, kernels, etc., too). If I remember correctly your hboot is Ville specific but if you want to be sure you can find the answer in the getvar all output (look at the line beginning with "product").
Thank you so much man, i understand a little more but i have another problem: i can't find a proper version of the RUU File (My build number is 3.14.422.11) and there's only one similar (3.14.422.9) and matches with my radio version (1.11.50.05.28) but i'm not sure if it works with my One S (It's a Snapdragon S4 and in the "product" line says "vle" btw)
Auraburst said:
Thank you so much man, i understand a little more but i have another problem: i can't find a proper version of the RUU File (My build number is 3.14.422.11) and there's only one similar (3.14.422.9) and matches with my radio version (1.11.50.05.28) but i'm not sure if it works with my One S (It's a Snapdragon S4 and in the "product" line says "vle" btw)
Click to expand...
Click to collapse
The problem is that the only file with the 422 SKU is an OTA and not a RUU. If your phone was S-OFF you wouldn't need to use corresponding RUUs because you were able to flash any you want. It's a vicious circle in your case since you wanted the correct RUU before you start flashing. On the other side if you carefully follow the instructions of the S-OFF guides there shouldn't be any risk of bricking. Simply don't try to use any short cuts if any step doesn't not work the way the instructions tell you. Since I'm not living in the states I'm not completely sure but Cincinnati Bell is part of Bell Mobile, right? If that's correct I would change the CID to SuperCID (depending on the S-OFF method you use you may need to get the SCID anyway) and try to run one of the "BM" RUUs on AndroidRUU. Since all of them are older than you actual firmware your phone will be downgraded then but you can update it by using the OTA function in settings>about.
Btw.: With that output you can be sure it's the Ville and not the VilleC2.
Okay, so, in simple words, what can I do with SuperCID (S-OFF) is:
-Restore my phone with any RUU regardless of my version of Radio, and without any risk
-Safe downgrade to upgrade my version of HBOOT (Because I want to try a custom ROM and most require HBOOT 2.15)
If not so, tell me in what I am wrong, btw, there's any custom ROM that you can recommend? I want to try Cyanogenmod 12.1 or MaximusHD, both look great but I'm a little undecided and would listen to someone more experienced with this phone
Auraburst said:
Okay, so, in simple words, what can I do with SuperCID (S-OFF) is:
-Restore my phone with any RUU regardless of my version of Radio, and without any risk
-Safe downgrade to upgrade my version of HBOOT (Because I want to try a custom ROM and most require HBOOT 2.15)
If not so, tell me in what I am wrong, btw, there's any custom ROM that you can recommend? I want to try Cyanogenmod 12.1 or MaximusHD, both look great but I'm a little undecided and would listen to someone more experienced with this phone
Click to expand...
Click to collapse
Actually your radio doesn't matter at all in regard of RUUs. Flashing a RUU is never risky as long as it's a signed/official one and you do not turn off the phone during the flashing process or disconnect it from your pc. If you are not S-OFF and your CID and/or firmware version doesn't match (SCID always matches) official RUUs will simply abort the flashing process.
After you achieved S-OFF and got the SCID you simply need to relock your bootloader, boot into fastboot mode, connect the phone to your pc and run the RUU.exe. (As far as I remember relocking was needed for being able to install OTAs afterwards but I'm not completely sure. I just remember that I always did when I downgraded. Maybe someone else can confirm this.)
I personally do not like Cyanogenmod on this phone. Since there never was a GPE of the One S (the first HTC GPE that ever existed was the HTC One M7 GPE which is actually younger than this phone) there are no AOSP drivers for this phone and you can notice this problem for example in a worse camera quality on roms that are not based on sense (there are other problems but that's the most prominent one I can remember).
MaxximusHD is based on the leaked but never officially published android 4.2.2 firmware of the One S. If you want to use it without memory problems (the leaked firmware changes the way the phone interacts with it's memory) you need to flash the hboot 2.16. Instructions can be found in the Maxximus thread for example. I personally prefer hboot 2.16 because of its reorganized memory but the radio 1.20 that gets flashed with that firmware has some problems with the incall voice quality.
To sum it up, every custom rom has its pros and cons and every user has his/her own preferences so it's hard to tell others which rom to use. The best way is to look which ones fullfil your needs and to test them out by yourself.
Edit: Downgrading isn't needed if you just want to start flashing. I just wanted to point out what happens if you run a RUU that is older than your actual firmware.
Edit2: Nevertheless here is a chronological list of the roms I liked and used longer than a week on this phone: Viper 2.2 (hboot 2.15), MaxximusHD (hboot 2.16), Viper 3.2.1 (hboot 2.16).