Database Info

RUU - Error 140.

I tried to run a RUU.exe on my HTC One S. Sadly I get a error 140 everytime I try. I read somewhere it could be something with I try to flash an older RUU version, than my current version. What can I do about it?
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0002
(bootloader) version-baseband: 1.06es.50.02.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.31.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4164mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 1a7fdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
EDIT: THIS PICTURE I POSTET, SAYS UNLOCKED. BUT I DID RELOCKED WHEN I TRYID TO FLASH.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Your hboot is 1.14 thats highest currently hence cannot RUU an older version, RUU 2.31 is released by football in development section, try it to return stock!

mughalgxt said:
Your hboot is 1.14 thats highest currently hence cannot RUU an older version, RUU 2.31 is released by football in development section, try it to return stock!
Click to expand...
Click to collapse
I will try to take a look on it. Tyvm.
EDIT: Wow, he just uploaded it, 1 hour ago?

mughalgxt said:
Your hboot is 1.14 thats highest currently hence cannot RUU an older version, RUU 2.31 is released by football in development section, try it to return stock!
Click to expand...
Click to collapse
Alright. RUU did work. But I'm very confused about what ClockMod I should install, can anyone be nice and guide me?
I also read there is a different between HTC One S models, S1, S2, and S3. How to find out which one I have?

DownClock said:
Alright. RUU did work. But I'm very confused about what ClockMod I should install, can anyone be nice and guide me?
I also read there is a different between HTC One S models, S1, S2, and S3. How to find out which one I have?
Click to expand...
Click to collapse
Lol there is only the S4 and S3. Check your box the phone came in and see if it says 1.5GHz or 1.7GHz. 1.5 is the S4
Sent from my HTC One S running ViperOneS!

invasion2 said:
Lol there is only the S4 and S3. Check your box the phone came in and see if it says 1.5GHz or 1.7GHz. 1.5 is the S4
Sent from my HTC One S running ViperOneS!
Click to expand...
Click to collapse
Ah kewl, I just skipped most of the text. It's 1.5GHz, so it's S4.
EDIT: It worked! Perfectly!
Thanks for helping me put guys!

DownClock said:
Ah kewl, I just skipped most of the text. It's 1.5GHz, so it's S4.
EDIT: It worked! Perfectly!
Thanks for helping me put guys!
Click to expand...
Click to collapse
Hey DownClock,
yesterday I tried to install the 2.31 RUU but it did not work for me. I am on codefireX nightlies (CM10 derivate). To install the RUU I flashed stock recovery and relocked the bootloader. But the the phone stuck on boot animation and I had to revert everything (re-unlock, flash custom recovery (TWRP) and restored a backup).
What ROM were you on when you installed the RUU and did you relock the bootloader and flash stock recovery? Is that all necessary?
TIA
Burkhard

herzbert said:
Hey DownClock,
yesterday I tried to install the 2.31 RUU but it did not work for me. I am on codefireX nightlies (CM10 derivate). To install the RUU I flashed stock recovery and relocked the bootloader. But the the phone stuck on boot animation and I had to revert everything (re-unlock, flash custom recovery (TWRP) and restored a backup).
What ROM were you on when you installed the RUU and did you relock the bootloader and flash stock recovery? Is that all necessary?
TIA
Burkhard
Click to expand...
Click to collapse
Yes you need to relock your device. My (or my friends ROM) was Stock, but that should not affect anything. What I did was:
Step 1: Relock.
Step 2: Run the RUU.
Sendt fra min HTC One X med Tapatalk2

How do I relock? Also, I have an S4, but I'm not sure what version my hboot is. I never flashed a new radio, jsut rooted and am running CM10. Which RUU do I download and where do I download it from? Thanks!

Legaleye3000 said:
How do I relock? Also, I have an S4, but I'm not sure what version my hboot is. I never flashed a new radio, jsut rooted and am running CM10. Which RUU do I download and where do I download it from? Thanks!
Click to expand...
Click to collapse
This is not my primary phone, but my friends. But I will try my best
Your HBOOT version should not being affected if you install the newest RUU.
You can download a RUU here. Remember to choose the right country!
And as you noticed the accecs will cost you a bit.
Here is also a guide you should follow.

It's better to flash RUU by fastboot usb.

hawkattack said:
It's better to flash RUU by fastboot usb.
Click to expand...
Click to collapse
Eh.. How else can you flash?
Sendt fra min HTC One X med Tapatalk2

DownClock said:
Here is also a guide you should follow.
Click to expand...
Click to collapse
That guide helped me. Relock bootloader, reboot into fastboot and start the RUU exe file.
Tanks.

herzbert said:
That guide helped me. Relock bootloader, reboot into fastboot and start the RUU exe file.
Tanks.
Click to expand...
Click to collapse
Glad I could help
Sendt fra min HTC One X med Tapatalk2

Please help!! Stuck in fastboot after flashing a rom

I tried flashing CM10 onto my AT&T HOX and now I'm stuck in the fastboot menu (picture below)
Let me know what information I could supply that could help
C:\Users\temp\Downloads\OneXUnroot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.16.32.09.01_3
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.73.502.1
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4127mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.080s

Shows "relocked" what did you do there? Can you get into recovery.
Sent from my One X using xda premium

lost45 said:
I tried flashing CM10 onto my AT&T HOX and now I'm stuck in the fastboot menu (picture below)
Click to expand...
Click to collapse
Relocked + custom recovery = no boot

subarudroid said:
Shows "relocked" what did you do there? Can you get into recovery.
Sent from my One X using xda premium
Click to expand...
Click to collapse
I was trying to follow some instructions from another website to flash it back to stock and I did a oem relock
And no I can't get into recovery, just the bootloader menu and the fastboot menu.

lost45 said:
I was trying to follow some instructions from another website to flash it back to stock and I did a oem relock
And no I can't get into recovery, just the bootloader menu and the fastboot menu.
Click to expand...
Click to collapse
You have to unlock again.

iElvis said:
You have to unlock again.
Click to expand...
Click to collapse
Could you point me in the right direction on how to do this from fastboot?
Edit: Just realized it has to be in fastboot to unlock the bootloader.
I'll post results after I do this.

lost45 said:
Could you point me in the right direction on how to do this from fastboot?
Click to expand...
Click to collapse
How did you do it the first time? You just flash the same unlock token you used before.

After I reunlock it should I flash the stock recovery?
Then what would my next step be?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

lost45 said:
After I reunlock it should I flash the stock recovery?
Then what would my next step be?
Click to expand...
Click to collapse
What are you trying to do? Flash CM?

iElvis said:
What are you trying to do? Flash CM?
Click to expand...
Click to collapse
At this point I'd like to flash anything that can work. If I can do CM10 that would be great.
Newest Update:
I have TWRP successfully running. How can I copy the .zip onto the sdcard now?

lost45 said:
At this point I'd like to flash anything that can work. If I can do CM10 that would be great.
Click to expand...
Click to collapse
Once you reunlock, you may or may not still have root. Open superuser or SuperSU (whatever you have installed), go into settings, and turn it off and back on again. Then check a root app to see if you're still rooted. If all you did was relock, you should still be rooted.
If that's the case, reboot to recovery and flash away. You have the old hboot so you don't need to worry about flashing boot.imgs.

ok, if you can get back to square 1 (any rom installed, any recovery installed) and get into bootloader and recovery you will be fine. remember when flashing a rom to the One X, you must do "fastboot flash boot boot.img" from terminal before you proceed and flash from twrp (or whatever recovery you use). otherwise it will flash but not boot.
so i recommend:
1. going into your recovery and clearing EVERYTHING (cache, dalvik, data) and then get back into fastboot mode.
2. running the "fastboot flash boot boot.img" from terminal on your PC
3. exiting bootloader and getting into recovery
4. flash the rom/gapps/root zips
if this doesnt work, then let me know. i'll try my best to help you out
EDIT: sorry, just saw that you had the old hboot.... never mind about all those steps :/ i honestly dont know what you should do next, since you dont need to flash the boot.img...

tyessen said:
ok, if you can get back to square 1 (any rom installed, any recovery installed) and get into bootloader and recovery you will be fine. remember when flashing a rom to the One X, you must do "fastboot flash boot boot.img" from terminal before you proceed and flash from twrp (or whatever recovery you use). otherwise it will flash but not boot.
so i recommend:
1. going into your recovery and clearing EVERYTHING (cache, dalvik, data) and then get back into fastboot mode.
2. running the "fastboot flash boot boot.img" from terminal on your PC
3. exiting bootloader and getting into recovery
4. flash the rom/gapps/root zips
if this doesnt work, then let me know. i'll try my best to help you out
EDIT: sorry, just saw that you had the old hboot.... never mind about all those steps :/ i honestly dont know what you should do next, since you dont need to flash the boot.img...
Click to expand...
Click to collapse
I have TWRP working now so I'm going to try to find a good ROM and flash it through recovery.
I'll let you know how it goes
UPDATE: Flashing CM10 with a nightly failed, it would just sit at the start up screen. I flashed the stable CM10 from here: http://get.cm/?device=evita&type=stable which worked!
Now I just need to flash gapps

lost45 said:
I have TWRP working now so I'm going to try to find a good ROM and flash it through recovery.
I'll let you know how it goes
Click to expand...
Click to collapse
ok, hope it works if you get it to work and it runs fine, make a backup in twrp so you always have a safety-blanket if something goes wrong someday

CM10 should boot fine just make sure you wiped everything and flash boot.img in fastboot

CM10 went on smoothly and its all set. Thanks for the help!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

You might want to edit your first post to take out your imei, serial # etc...
Sent from my HTC One XL using xda premium

iElvis said:
Once you reunlock, you may or may not still have root. Open superuser or SuperSU (whatever you have installed), go into settings, and turn it off and back on again. Then check a root app to see if you're still rooted. If all you did was relock, you should still be rooted.
If that's the case, reboot to recovery and flash away. You have the old hboot so you don't need to worry about flashing boot.imgs.
Click to expand...
Click to collapse
I know this is an old thread, but I have the same issue, but when I flash anything it just bootloops still. And my dalvik cache wipe always fails when I try to do that. I dunno why that is.

Read 4 posts up.. Flash boot.IMG first. And wipe everything
Sent from my One X using xda premium

Any stable roms on xda......

Admin, please remove/delete this tread, I am starting a new one to fully address my issue...... Sorry about the inconvenience.

Running magio sense 5... Stable as they get. Sounds like you have other issues if you can't get viperxl to boot. What recovery version do you use?
Sent from my HTC One XL using XDA Premium 4 mobile app

31ken31 said:
Running magio sense 5... Stable as they get. Sounds like you have other issues if you can't get viperxl to boot. What recovery version do you use?
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
twrp 2.6.3.0. The viper rom is always good at android 4.1. When I upgrade my hboot to 2.15, viper rom for sense 5 still work, it's just not stable. After I upgraded to RUU 3.18 today, viper rom doesn't even boot.

Have you wiped everything before flashing?
Sent from my HTC One XL using XDA Premium 4 mobile app

31ken31 said:
Have you wiped everything before flashing?
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I did...... wipe data, cache, system, dev cache

For hahas I just flashed viper on 2.15 hboot and it's working fine
Sent from my HTC One XL using XDA Premium 4 mobile app

31ken31 said:
For hahas I just flashed viper on 2.15 hboot and it's working fine
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Are you RUU 3.18?

Yes I ruu to 3.18 a while back, to play with the new cm roms. Now I'm using the 4.2.2 hboot (2.15 and the 3.18 radio)
Sent from my HTC One XL using XDA Premium 4 mobile app

31ken31 said:
Yes I ruu to 3.18 a while back, to play with the new cm roms. Now I'm using the 4.2.2 hboot (2.15 and the 3.18 radio)
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sigh, I'll see what I can do

I'd start over with ruu. And double manual wipe everything before install, after flash wipe cache n dalvik. And factory reset in twrp before first boot.
And verify md5 on rom your flashing, it would suck if your glitches are from a slightly corrupt download.
Sent from my HTC One XL using XDA Premium 4 mobile app

31ken31 said:
I'd start over with ruu. And double manual wipe everything before install, after flash wipe cache n dalvik. And factory reset in twrp before first boot.
And verify md5 on rom your flashing, it would suck if your glitches are from a slightly corrupt download.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just RUU to 3.18 and flashing hboot 2.15 right now...I will check md5 on the rom. Thanks for all the advise.

snake3276120 said:
I just RUU to 3.18 and flashing hboot 2.15 right now...I will check md5 on the rom. Thanks for all the advise.
Click to expand...
Click to collapse
after I flash hboot 2.15, the ruu becomes 5.08.111.2 ......

I think you're getting your terminology mixed up, do you mean the build number becomes 5.08.111.2?
Sent from my Evita

timmaaa said:
I think you're getting your terminology mixed up, do you mean the build number becomes 5.08.111.2?
Sent from my Evita
Click to expand...
Click to collapse
After I ran the RUU 3.18 upgrade in this tread: http://forum.xda-developers.com/showthread.php?t=2382933
I boot into bootloader, and ran fastboot getvar all, the result is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT246W304864
(bootloader) imei: 359691041684351
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4122mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
I'm assuming "(bootloader) version-main: 3.18.502.6" is the RUU version. I also flashed an hboot 2.14, it became 3.17.xxxxxxx. That'w why I am assuming this is the RUU number.
Ok, regardless of the build number or ruu...... I think there is something wrong with my bootloader. It doesn't matter which hboot I flash (hboot 2.14 with version-main 3.17/3.18, or hboot 2.15 with version-main 5.08), and I tried several twrp (2.4.4.0 and 2.6.3.0). The time it took to flash viper xl is really short while viper xl has 700MB. It is even shorter than the time I flash CM, which is around 180 MB.
I guess I'll start with the current AT&T stock rom (which still lose respond after I left the phone open for a while, and I have to press the power button for 10 secs to reset my phone)on hboot 2.14 and ruu 3.18. Root it, try to s-off again. Not sure if this will solve the problem.
Something interesting when I'm booting my phone, when the phone displays only the green HTC in the middle of the display, there is some text below it... saying something like "This is an internal build, do not distribute outside of HTC, failure may cause to law action". However, the AT&T stock rom I'm running right now does not have this.

snake3276120 said:
After I ran the RUU 3.18 upgrade in this tread: http://forum.xda-developers.com/showthread.php?t=2382933
I boot into bootloader, and ran fastboot getvar all, the result is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT246W304864
(bootloader) imei: 359691041684351
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4122mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
I'm assuming "(bootloader) version-main: 3.18.502.6" is the RUU version. I also flashed an hboot 2.14, it became 3.17.xxxxxxx. That'w why I am assuming this is the RUU number.
Ok, regardless of the build number or ruu...... I think there is something wrong with my bootloader. It doesn't matter which hboot I flash (hboot 2.14 with version-main 3.17/3.18, or hboot 2.15 with version-main 5.08), and I tried several twrp (2.4.4.0 and 2.6.3.0). The time it took to flash viper xl is really short while viper xl has 700MB. It is even shorter than the time I flash CM, which is around 180 MB.
I guess I'll start with the current AT&T stock rom (which still lose respond after I left the phone open for a while, and I have to press the power button for 10 secs to reset my phone)on hboot 2.14 and ruu 3.18. Root it, try to s-off again. Not sure if this will solve the problem.
Something interesting when I'm booting my phone, when the phone displays only the green HTC in the middle of the display, there is some text below it... saying something like "This is an internal build, do not distribute outside of HTC, failure may cause to law action". However, the AT&T stock rom I'm running right now does not have this.
Click to expand...
Click to collapse
It's a bit hard to follow what you're saying there but here goes. It's not the RUU number it's the build number. An RUU is the program that updates your phone, the reason you see them referred to as the 3.18 RUU is because they're known by the build number that they update your phone to.
Did you check the md5 of the downloaded file as someone else suggested? It might be corrupt. Also, maybe you should try TWRP 2.6, versions 2.4.x and 2.5.x are well known as being very buggy, and I've seen people have issues with version 2.6.3 too. 2.6 is rock solid though.
The red text you see when the phone boots up is completely normal for a modified phone so you needn't worry about that. The reason the stock ROM doesn't have it is because the RUU has returned your phone to being completely stock, therefore not modified, therefore no red text.
Sent from my Evita

timmaaa said:
It's a bit hard to follow what you're saying there but here goes. It's not the RUU number it's the build number. An RUU is the program that updates your phone, the reason you see them referred to as the 3.18 RUU is because they're known by the build number that they update your phone to.
Did you check the md5 of the downloaded file as someone else suggested? It might be corrupt. Also, maybe you should try TWRP 2.6, versions 2.4.x and 2.5.x are well known as being very buggy, and I've seen people have issues with version 2.6.3 too. 2.6 is rock solid though.
The red text you see when the phone boots up is completely normal for a modified phone so you needn't worry about that. The reason the stock ROM doesn't have it is because the RUU has returned your phone to being completely stock, therefore not modified, therefore no red text.
Sent from my Evita
Click to expand...
Click to collapse
Sorry for my broken English, and thanks for the reply...... I will start another tread to fully address my problem.

There's no need to start another thread, you're already getting help in here. The threads don't just get deleted, creating a new one just means you're duplicating the post which is unnecessary.
Sent from my Evita

timmaaa said:
There's no need to start another thread, you're already getting help in here. The threads don't just get deleted, creating a new one just means you're duplicating the post which is unnecessary.
Sent from my Evita
Click to expand...
Click to collapse
Sigh,I have already started a new one... Please take a look at http://forum.xda-developers.com/showthread.php?p=46229767#post46229767

So to summarize and to be clear: It turns out the OP is having some issues possibly due to updating hboot, and not problems with the stability of the ROMs themselves.
I know the OP deleted the content in the top post and started another thread (which is in itself not the right way to go about things). But it was in pretty bad style to title this thread the way it is, and imply that the ROMs are unstable, when you don't even know what the root cause of the problems is. If you have flashed several ROMs, and having the same issue on all, its most probable the problem is not with the ROMs, but with something you did (or didn't do), or else a hardware issue.

[Q] K2_UL breaked during official update, what can I do?

Hi everyone
I decided to update my HTC one sv using wifi, but after reboot, the cell phone stay on htc logo.
I can go to bootloader but not recovery, it seams official recovery is damaged.
S-on
Locked
HBOOT 2.00
Radio 1.15.40a.00. 04
Can anyone help? Should I use RUU file? What if there was not suitable RUU out there?

You can find everything you need to fix your phone here:
http://forum.xda-developers.com/showthread.php?t=2292432
HTC K2_PLC_CL

Thanks alot for your reply but I don't know where to start. For example which ruu is suitable for my device?
Or can I unlock the bootloader at this situation to install custom rom in case of unavailability of suitable ruu rom?
Sent from my HTC One using Tapatalk

If your phone is locked and S-On (and never was unlocked S-off), you should think about returning for warranty.

The warranty period is already expired. Another solution?
Sent from my HTC One using Tapatalk

More information about your phone model, please!

I dont think he can use an RUU. Last I checked, the available RUU's for you guys is based on ICS. Because he is S-On he can't use it since it would require downgrading. Would need to be S-Off to do that.
If there is a JB RUU for you guys then he is good to go, but I haven't seen one yet.
Sent from my C525c using Tapatalk

old.splatterhand said:
More information about your phone model, please!
Click to expand...
Click to collapse
What information exactly?
Sent from my HTC One using Tapatalk

Modding.MyMind said:
I dont think he can use an RUU. Last I checked, the available RUU's for you guys is based on ICS. Because he is S-On he can't use it since it would require downgrading. Would need to be S-Off to do that.
If there is a JB RUU for you guys then he is good to go, but I haven't seen one yet.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Can I S-OFF only through hboot and without working android os?
Sent from my HTC One using Tapatalk

salehi.com said:
Can I S-OFF only through hboot and without working android os?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
No!
Connect your phone with fastboot and type into the cmd:
Code:
fastboot getvar all
Put the output here (except your IMEI & Serial number)

old.splatterhand said:
No!
Connect your phone with fastboot and type into the cmd:
Code:
fastboot getvar all
Put the output here (except your IMEI & Serial number)
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 1.15.40a.00.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.708.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ************
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8015000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 3842mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.078s

- unlock your bootloader at htcdev.com
- flash k2ul recovery with fastboot
- wipe everything in recovery (except internal & external sd)
- flash a stock rom from recovery (either 4.1.2 or 4.2.2)
- get S-Off: if 4.1.2 rom, then use moonshin.io or if 4.2.2 rom use rumrunner.us
- after you are S-off you get a firmware.zip from me, wich updates your phone/radio related to your modelid, so you can run the latest 4.2.2 software without bugs
You can find everything you need in my index thread, which is linked in my signature.
Good luck!

old.splatterhand said:
- unlock your bootloader at htcdev.com
- flash k2ul recovery with fastboot
- wipe everything in recovery (except internal & external sd)
- flash a stock rom from recovery (either 4.1.2 or 4.2.2)
- get S-Off: if 4.1.2 rom, then use moonshin.io or if 4.2.2 rom use rumrunner.us
- after you are S-off you get a firmware.zip from me, wich updates your phone/radio related to your modelid, so you can run the latest 4.2.2 software without bugs
You can find everything you need in my index thread, which is linked in my signature.
Good luck!
Click to expand...
Click to collapse
Thanks alot for your step by step guide.
Step one have been done!
In step two, there are a lot of recovery there but none of them are compatible with my device(version-main: 2.14.708.5)
http://forum.xda-developers.com/showthread.php?t=2317379
can you please give a link of recovery for above version?
And after that in step 3, should i use the following link?
http://forum.xda-developers.com/showthread.php?t=2512742

TWRP Recovery 2.7.0.1

- unlock your bootloader at htcdev.com Done.
- flash k2ul recovery with fastboot Done.
- wipe everything in recovery (except internal & external sd) Done.
- flash a stock rom from recovery (either 4.1.2 or 4.2.2) Done. k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip
- get S-Off: if 4.1.2 rom, then use moonshin.io or if 4.2.2 rom use rumrunner.us Unsuccessful(rumrunner)! Here's the log:
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (37/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit

salehi.com said:
- unlock your bootloader at htcdev.com Done.
- flash k2ul recovery with fastboot Done.
- wipe everything in recovery (except internal & external sd) Done.
- flash a stock rom from recovery (either 4.1.2 or 4.2.2) Done. k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip
- get S-Off: if 4.1.2 rom, then use moonshin.io or if 4.2.2 rom use rumrunner.us Unsuccessful(rumrunner)! Here's the log:
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (37/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
Click to expand...
Click to collapse
Did you use rumrunner universal?
Sent from my C525c using Tapatalk

Modding.MyMind said:
Did you use rumrunner universal?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Yes.

salehi.com said:
Yes.
Click to expand...
Click to collapse
Make sure you do not have a lockscreen password of any kind turned on. Must be off.
Sent from my C525c using Tapatalk

Modding.MyMind said:
Make sure you do not have a lockscreen password of any kind turned on. Must be off.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
The screen lock is already None
Settings-Security-Screen lock-none

Do you have root? If not (because rom is stock), flash SuperSu.zip, linked in my index thread and don't forget to allow root permission to adb shell!

Soft brick HTC One S on Hboot 1.09 - S-On

I'm stuck on hboot 1.09 with S-on and a custom recovery. My questions are
1. Are there any roms that i can flash ?
2. Can i S-off using fasboot since adb isn't accessible atm
3. Any other way to get this phone running ?
4. I dont have any backup, wiped everything and don't even have the previous rom that was flashed on the phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Enter recovery and mount USB .
Copy a ROM that is working on ur hboot.
Unmount usb, do a full wipe and than flash the copied ROM .
Don't forget to flash the boot IMG( after flashing the ROM) via fasboot.
Restart system .
Sent from my One S using Tapatalk

matu89 said:
Enter recovery and mount USB .
Copy a ROM that is working on ur hboot.
Unmount usb, do a full wipe and than flash the copied ROM .
Don't forget to flash the boot IMG( after flashing the ROM) via fasboot.
Restart system .
Sent from my One S using Tapatalk
Click to expand...
Click to collapse
I've tried a few roms from xda, none working. Flashed boot.img and all ?
Sent from my Nexus 7 using Tapatalk

What's the error says?
Sent from my One S using Tapatalk

matu89 said:
What's the error says?
Sent from my One S using Tapatalk
Click to expand...
Click to collapse
No error, just doesn't boot. Gets stuck on the htc logo
Sent from my Nexus 7 using Tapatalk

Try to update twrp and see
Sent from my One S using Tapatalk

matu89 said:
Try to update twrp and see
Sent from my One S using Tapatalk
Click to expand...
Click to collapse
Already am on 2.5.0 Twrp :|

U must doing something wrong , flash again the previous ROM (the last one that worked for u) , return to fastboot and issue the command : flash boot xxx.IMG
Sent from my One S using Tapatalk

Yo, had the sam issue while trying to flash to CyanogenMod 12.1.
Forgot to flash boot.img using fastboot and it ended up in infinite looping, and i was unable to even get tot he fastboot menu.
It helped to disconnect the battery for 10 seconds.
Took me a while to get to it, as Torx 5 is needed for disassembly.
I'm sorry i can't post links as i am a newbie, but the YT video ID is the following: KkG2mPkfGZI

matu89 said:
U must doing something wrong , flash again the previous ROM (the last one that worked for u) , return to fastboot and issue the command : flash boot xxx.IMG
Sent from my One S using Tapatalk
Click to expand...
Click to collapse
I dont have the previous rom on the phone either. A relative was using this phone and wanted to sell it off. Wiped it without actually knowing and now am in this situation. Tried flashing viper 2.2.0 from http://forum.xda-developers.com/showthread.php?t=2105863 but it stops before ending. I guess i need to update my hboot to be able to flash any rom at the moment ?

You could still try with a RUU...

DaMachk said:
You could still try with a RUU...
Click to expand...
Click to collapse
I haven't found the RUU for my mobile. I'd prefer to go full stock or anything. I'm willing to try anything at the moment :| my "fastboot getvar all" result is following
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.16.31501S.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: HT249W403058
(bootloader) imei: 359902040657367
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4196mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

How 'bout ths site?
http://forum.xda-developers.com/showthread.php?t=2094414

DaMachk said:
How 'bout ths site?
http://forum.xda-developers.com/showthread.php?t=2094414
Click to expand...
Click to collapse
Quick question. Is T-MOB010 = TMOUS ?

shani248 said:
Quick question. Is T-MOB010 = TMOUS ?
Click to expand...
Click to collapse
Sorry, but i'm not sure...
But if you are in the US and the mobile is T-MOBILE branded, then go with the TMOUS...
If the mobile was bought in Europe and is T-MOBILE branded, then i suggest you go with the TMOB_DE.
EDIT: so apparenlty, regarding this topic: http://forum.xda-developers.com/showthread.php?t=1228787
the T-MOBILE010 is TMOUS.

DaMachk said:
Sorry, but i'm not sure...
But if you are in the US and the mobile is T-MOBILE branded, then go with the TMOUS...
If the mobile was bought in Europe and is T-MOBILE branded, then i suggest you go with the TMOB_DE.
EDIT: so apparenlty, regarding this topic: http://forum.xda-developers.com/showthread.php?t=1228787
the T-MOBILE010 is TMOUS.
Click to expand...
Click to collapse
Thank you for this so much ! Downloading the RUU as we speak. Will update after it finishes !

Finally flashed the RUU after some windows 8.1 problems but the phone is working now. Thank you so much guys ! You've been great help !

Great to hear.
Hope it serves you well. Mine will be 3 yeas old in a few weeks.