Database Info

Official T-mobile RUU help

Hello, i'm new guy on this forum. I'm going back from s-off to s-on and official stock t-mobile ruu and i'm using tutorial form this forum. But then i try install RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed i'm getting this ERROR[170]: USB CONNECTION ERROR. But my phone is properly connected, i tried europe ruu(no usb erros), but then i got cid error.
Hboot 0.98.0000
cid t-mob005

Ok, turn in bootloader and now no usb error, but now i'm getting bootloader error 140. Any suggestions?
I'm using this ruu RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed
My phone info
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.401.4
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: good
(bootloader) battery-voltage: 4200mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0

It seems that you used an European unbranded RUU. To fix you have to create a goldcard, use the 1.47.401.4 RUU again to have a booting system, then change the main version and after that flash the TMOB RUU again
Sent from my HTC Desire S

thanks, but now i got another problem, my phone turn only in bootloader(but i cant see it using adb devices). But i can choose fastboot and then i see my device using fastboot devices. So i'cant get card cid maybe there is another way to get goldcard?

cezzka said:
thanks, but now i got another problem, my phone turn only in bootloader(but i cant see it using adb devices). But i can choose fastboot and then i see my device using fastboot devices. So i'cant get card cid maybe there is another way to get goldcard?
Click to expand...
Click to collapse
Use this to get the CID
Then this to make the GoldCard

Big thanks to amidabuddha. Finally i flashed 1.47.401.4 RUU(phone is booting fine), so how i can change main version to install TMOB RUU?

cezzka said:
Big thanks to amidabuddha. Finally i flashed 1.47.401.4 RUU(phone is booting fine), so how i can change main version to install TMOB RUU?
Click to expand...
Click to collapse
Follow this guide.
When you are done I suggest to fill the offset 00000000 to 00000170 of your sdcard with zeroes (as it was before) because various users reported that running a device with a goldcard inside can cause issues.

amidabuddha said:
Follow this guide.
When you are done I suggest to fill the offset 00000000 to 00000170 of your sdcard with zeroes (as it was before) because various users reported that running a device with a goldcard inside can cause issues.
Click to expand...
Click to collapse
Thanks again ! you and this forum really helped me. Now i got what i wanted

Thanks
amidabuddha said:
Use this to get the CID
Then this to make the GoldCard
Click to expand...
Click to collapse
I've signed up JUST to say thanks for this post. Bacon saved.

Help!?
Im a bit confussed, im desperately trying to get back to stock ics but can work out how, i have what seems to be a rare cid: TMOB005, my phone is S-ON, can i use this method?
Thanks!

im having this exact problem same phone same ruu flashed
amidabuddha said:
It seems that you used an European unbranded RUU. To fix you have to create a goldcard, use the 1.47.401.4 RUU again to have a booting system, then change the main version and after that flash the TMOB RUU again
Sent from my HTC Desire S
Click to expand...
Click to collapse
im having this exact problem same phone same ruu flashed can you please tell me what is the 1.47.401.4ruu please give me a link where to download it also i tried to make a gold card think i did but i dont know how to use it as on my bootloader it dont say update from zip on sd card anymore also its got s-on. please help

[Q] HTC One S bricked (noob level)

Hello guys,
yesterday my brother bricked his HTC One S (he is very peachy in breacking new phones ) and I was not able to restore the stock rom.
I tried some restore methods:
- If I try to enter in recovery mode on the screen appears the phone with red triangle
- If I try to run ruu exe in fastboot it doesn't work (error 155 or error 130 after various try)
- If I try to install stock zip from fastboot (after the restoring of genuine boot.img and recovery.img) the terminal said:"FAILED <remote: not allowed>"
I have no idea how to fix the issue so I hope you can help me
I noted a strange think: if I try to get all global variables, some of them are unknown, here my getvar all:
version: 0.5
version-bootloader: 1.14.0002
version-baseband: 1.08es.50.02.16
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: MB231W404549
imei: xxx (I hide it)
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: ORANG309
battery-status: good
battery-voltage: 4057mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 1a7fdca3
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
What could I do? Thanks all!

PierDesk said:
Hello guys,
yesterday my brother bricked his HTC One S (he is very peachy in breacking new phones ) and I was not able to restore the stock rom.
I tried some restore methods:
- If I try to enter in recovery mode on the screen appears the phone with red triangle
- If I try to run ruu exe in fastboot it doesn't work (error 155 or error 130 after various try)
- If I try to install stock zip from fastboot (after the restoring of genuine boot.img and recovery.img) the terminal said:"FAILED <remote: not allowed>"
I have no idea how to fix the issue so I hope you can help me
I noted a strange think: if I try to get all global variables, some of them are unknown, here my getvar all:
What could I do? Thanks all!
Click to expand...
Click to collapse
you should flash TWRP recovery to install a custom rom than you can try different sense roms which are very close to stock

Could you say what the RUU says for error 155 or 130? Also, to enter the menu for recovery hold down power, and while holding it down, press volume up.
Edit: You are using the wrong RUU. What CID are you and what phone do you have, Ville C2?
Also you might want to hide your Serial #

[Q] upgrade from rooted stock ICS to stock JB: ERROR 132

I need help to upgrade my HTC One S (C4) (Ville U) rooted from stock ICS (rom version 2.31.401.5) to the new JB.
There are several things I don't understand, so, please, help me.
Some info:
Code:
HTC Ville U no brand (got from H3G Italy)
Tampered
Unlocked
Vle pvt ship s-on
Hboot 1.14.0002
Radio 1.06es.50.02.31
Cid HTC_405 (italy, no brand)
Mainsku 401
Rom: Ville_u_isc_40_s version 2.31.401.5
version: 0.5
[email protected] bootloader : 1.14.0002
[email protected] baseband : 1.06es.50.02.3
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: ***************
imei: ***************
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: HTC__405
battery-status: good
battery-voltage: 3950mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
[email protected] bootloader : 1a7fdca3
hbootpreupdate: 11
gencheckpt: 0
I have reverted to stock recovery (but in bootloader I see always "tampered"). Then I relocked. Then I tryed to flash the ruu RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
But after a while I get ERROR 132 (signature error).
I tryed to start the ruu after manually entering in fastboot mode, but I get the same error.
The phone was factory reset, but apps like SuperSu are always present as they were flashed in system.
What should I do now?

You just need stock recovery to flash OTA
Search for how to reinstall stock recovery
From HTC One S

Just flashed stock recovery and relocked bootloader.
I started the RUU named RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe from Windows 7 32 bit (antivirus and any protection disabled) but after the initial screen, the software closes.
So I restarted the RUU from fastboot, the ruu start the update but stops again with this error:
ERROR [132] SIGNATURE ERROR (don't know if in english is "SIGNATURE", I got the message in Italian, that is "ERRORE FIRMA".
How to proceed?

Did you disable 'fastboot' in settings of your phone?
Else I don't see a reason why it shouldn't work. You could change CID to HTC__001, also HTC_405 should be good for an EU branded RUU.
Btw, the tampered flag can only be removed when your phone is s-off.

The phone is always in usb debug mode. I neve tried the ruu with debug mode off. Now I will try to reinstall the same ruu of ICS that I have on the phone. Just to make a try
EDIT:
well, the ruu of ICS was succesfully installed. Then I run ruu of JB but I got another time the error 132.
Now I'm trying the OTA. Is it a risk?
EDIT2:
Done: I made the OTA and all works perfectly. Now I have JB.

Unbrand and update 3UK S4 on 1.06 hboot

Hello, I could use a little help, as I cannot flash recovery on branded 3-Mobile UK phone (S4 processor).
I have unlocked the bootloader via htcdev.
More phone info via fastboot getvar all :
Code:
version: 0.5
version-bootloader: 1.06.0000
version-baseband: 0.15.31501S.19_2
version-cpld: None
version-microp: None
version-main: 1.53.771.4
serialno: HT242W411761
imei: ***
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: H3G__001
battery-status: good
battery-voltage: 4018mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 802fa374
hbootpreupdate: 11
gencheckpt: 0
CID is H3G__001 and HBOOT is 1.06.0000
I have tried flashing both CWM and TWRP from fastboot, but though it seems everything goes well, when I reboot to recovery, it gives me the generic HTC recovery screen (the one with the little bar on the top right of the screen) and reboots after a while to the branded ROM. I think it reflashes the branded recovery automatically, because the bar is proceeding and then reboots the phone.
I cannot root or change CID without custom recovery.
Do I need to flash a boot.img (and which one)?
Thank you in advance!
*UPDATE*
OK, I managed to install an older version of TWRP (2.6.3.0).
What must I do to update hboot and install newer ROMS?

Candlemass said:
Hello, I could use a little help, as I cannot flash recovery on branded 3-Mobile UK phone (S4 processor).
I have unlocked the bootloader via htcdev.
More phone info via fastboot getvar all :
Code:
version: 0.5
version-bootloader: 1.06.0000
version-baseband: 0.15.31501S.19_2
version-cpld: None
version-microp: None
version-main: 1.53.771.4
serialno: HT242W411761
imei: ***
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: H3G__001
battery-status: good
battery-voltage: 4018mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 802fa374
hbootpreupdate: 11
gencheckpt: 0
CID is H3G__001 and HBOOT is 1.06.0000
I have tried flashing both CWM and TWRP from fastboot, but though it seems everything goes well, when I reboot to recovery, it gives me the generic HTC recovery screen (the one with the little bar on the top right of the screen) and reboots after a while to the branded ROM. I think it reflashes the branded recovery automatically, because the bar is proceeding and then reboots the phone.
I cannot root or change CID without custom recovery.
Do I need to flash a boot.img (and which one)?
Thank you in advance!
*UPDATE*
OK, I managed to install an older version of TWRP (2.6.3.0).
What must I do to update hboot and install newer ROMS?
Click to expand...
Click to collapse
your phone's security is on. I would recommend do the following:
1) S-off ur phone
2) change CID to supercid
3) Run any new RUU
4) Re-flash TWRP
5) Enjoy

bilal_liberty said:
your phone's security is on. I would recommend do the following:
1) S-off ur phone
2) change CID to supercid
3) Run any new RUU
4) Re-flash TWRP
5) Enjoy
Click to expand...
Click to collapse
Thank you for your answer and congrats on your ROM (it is the one I'm running right now ).
I managed to solve the issues yesterday, but the information was so scattered around, it took me half a day (along with the sloooow downloads).
For anyone interested, the procedure was like this :
1) Unlock bootloader via htcdev.com and identifier token
2) Flash TWRP 2.6.3.0
3) Root
4) SuperCID
5) S-OFF
6) Change CID to HTC__001
7) Update HBOOT to 2.15 via firmware flash
8) Run newest RUU
9) Flash newest radio
10) Re-flash TWRP
11) Flash Custom ROM
Step 8 can be skipped, but I wanted to see if it ran the stock ROM ok.
In more detail, with links and files :
Initially the phone was branded on 3UK with CID H3G__001, HBOOT 1.06 and MID PJ4010000.
Code:
version: 0.5
version-bootloader: 1.06.0000
version-baseband: 0.15.31501S.19_2
version-cpld: None
version-microp: None
version-main: 1.53.771.4
serialno: HT242W411761
imei: ***
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: H3G__001
battery-status: good
battery-voltage: 4018mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 802fa374
hbootpreupdate: 11
gencheckpt: 0
The safest way to update my HBOOT to 2.15 or 2.16 was via a latest official RUU from here http://www.androidruu.com/?developer=Ville . But the latest RUU matching my CID was a bit old (RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed) and I didn't know which HBOOT it contained, so I decided to update using the latest European RUU (RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4). In order to do this, I would have to chance CID to something corresponding (i.e. HTC__001 or HTC__N34 for my region - ELL).
(1)
I began with the thread [Tutorial]Root, Unlock, Recovery and flashing a Custom ROM, but got stuck on the recovery flashing, that's when I started this thread. I flashed the latest TWRP (2.7.0.0) and latest CWM (6.0.4.8) but they didn't work.
The recovery boot acted as described in the OP (gave me the generic HTC recovery screen) and tried multiple times. Then I remembered reading something like that the newest recoveries work differently to support newest hboot, so I tried the previous version (TWRP 2.6.3.0 from http://techerrata.com/browse/twrp2/ville ) and it worked.
(2-3)
TWRP also offered to root the ROM by installing supersu automatically, so I didn't have to flash it myself. After the reboot to system, I installed supersu from market, updated su binary and the root access was complete. The rooting was necessary so that we can change the CID to SuperCID.
(4)
SuperCID can be set following this guide [UNLOCK] AT&T Bootloader Unlock Through HTC-Dev. I changed H3G__001 to 11111111 with HxD (needs care not to change more that those 8 bytes and check that the size remains the same - mine was 1024B).
(5)
Next stop is S-OFF via Facepalm with the help of this thread [S-Off] Facepalm S-Off for HTC Devices One S, One XL, Droid DNA. It worked right away, following exactly the procedure as described.
(6)
I changed CID to HTC__001 , not leaving SuperCID on, because there were reports of bricks when flashing OTA updates. Just wanted to be on the safe side.
Easy from fastboot with S-OFF :
Code:
fastboot oem writecid HTC__001
(7-8)
The next step was to flash the latest RUU (RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4), in order to update my HBOOT to 2.15. But this came to a halt, as the RUU didn't proceed, giving me error 159. More info and solution on this matter can be found in the thread RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1. 11.50.05.28_10.27.50.08L_release.
In short, the problem is that the ROM.zip inside the RUU is encrypted and we either had to decrypt it using ruuveal via linux, or to use the already decrypted by hasoon2000 zip ( http://forum.xda-developers.com/showpost.php?p=40925380&postcount=79 ).
As I also mentioned in that said thread ( http://forum.xda-developers.com/showpost.php?p=52852710&postcount=123 ), if you update the HBOOT manually, by flashing corresponding firmware, the RUU flashing proceeds without any issues.
So, I followed the thread [GUIDE][TOOL]FUU/FirmwareHTC One S and flashed the Official Unbranded 2.15 Firmware (Sense) zip via fastboot. The result was an updated HBOOT to 2.15 and the ability to flash the official RUU. With S-OFF there is no need to relock the bootloader.
(9-10-11)
After that, I simply reflashed TWRP and the custom ROM Liberty-S4-V7a. I skipped the manual radio flash, because Liberty ROM had the option to flash it from AROMA installer automatically. For other ROMs, it is a simple flash via fastboot.
Simple, hah

[Q] Newbie stuck , would love some help guys

Hello Lads
Sorry to trouble you but ive read and read and tried and tried various options but no luck. I was up till two this morning and have been on this all day when I was supposed to be out with the wife. Shes not a happy bunny.
Got an HTC ONE S here on Vodafone, I can get into Bootloader and custom recovery twrp-2.7.1.0a-ville.img
but I cant load any image nothing, The phone wont boot and keeps restarting in a boot loop. I've tried various options and nothing.
I have reflashed stock recovery and tried to put a vodafone ruu on but I keep getting an error
htc android phone update rom utility 1.04 2011
error 140 bootloader version error
Click to expand...
Click to collapse
All I want to do is put a stock vodafone rom back on this phone but teh three ive tried give the same error
I thin I have to flash stock recovery
Then relock Bootloader through fastboot
Then run RUU while phone is in fastboot USB
Is this correct and can anyone point me to the correct RUU
details are
TAMPERED
UNLOCKED
VLE PVT SHIP ON RL
HBOOT -2 .15.0000
RADIO -1.15.50.05.29
OPENDSP - V31.1.0.45.0815
EMMC -BOOT
DEC 14 2012. 17:10:57-1
Click to expand...
Click to collapse
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.15.50.05.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT23SW403509
(bootloader) imei: 359901041141397
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3944mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.067s
C:\fastboot>
Click to expand...
Click to collapse
Thanks for taking the time to read this , hope someone can put me out of my misery.

mitch127 said:
Hello Lads
Sorry to trouble you but ive read and read and tried and tried various options but no luck. I was up till two this morning and have been on this all day when I was supposed to be out with the wife. Shes not a happy bunny.
Got an HTC ONE S here on Vodafone, I can get into Bootloader and custom recovery twrp-2.7.1.0a-ville.img
but I cant load any image nothing, The phone wont boot and keeps restarting in a boot loop. I've tried various options and nothing.
I have reflashed stock recovery and tried to put a vodafone ruu on but I keep getting an error
All I want to do is put a stock vodafone rom back on this phone but teh three ive tried give the same error
I thin I have to flash stock recovery
Then relock Bootloader through fastboot
Then run RUU while phone is in fastboot USB
Is this correct and can anyone point me to the correct RUU
details are
Thanks for taking the time to read this , hope someone can put me out of my misery.
Click to expand...
Click to collapse
Try getting the ICS RUU instead of straight up JB then from there update to JB. Worth a try, hope this helps!
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app

YoungDev said:
Try getting the ICS RUU instead of straight up JB then from there update to JB. Worth a try, hope this helps!
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for replying to my question Pal.
I've managed to figure out how to unlock, root, get SuperCid, relock, get another unlock token and then eventually get S_ OFF,, which wouldn't work until I relocked then unlocked again with a new bin file.
Once I had done all this I re flashed a new twrp recovery, then flashed a new rom from recovery, then gapps.. Still cant the find a vodafone stock rom I was on but as I now have S Off I guess that doesnt matter and I can flash the european latest rom if i want to.
Thank you for taking the time to help me Mate, I am Grateful.
Im still on 1.15 radio and I think I will try to flash that next with the 1.20 or higher version to see if it helps with my phone signal which is not very good