Database Info

[Q] Sensation XE Bootloop

Hi,
I'm having a bootloop on my sensation xe. I never used a custom rom or anything, and last week i got the following error while updating an app:
"Couldn’t install on USB storage or SD card" I rebooted my phone, and then i got stuck in a bootloop (booting till the htc logo, then rebooting).
I tried to flash a stock RUU from fastboot following this guide http://forum.xda-developers.com/showthread.php?t=1672425 . The command line showed no errors while flashing, but this didn't help.
Also flashing 4ext and cwm recoveries didn't work, the commandline showed no errors, but on the screen of my phone the little progress bar on the upper right side never got filled, and the recovery just goes straight to the htc logo, and then rebooting again..
Version:
Relocked
Pyramid pvt ship s-on rl
hboot-1.29.0000
eMMc-boot
cid: HTC__E11
mid: PG5813001
Is there anything else i can try, or should i send it out to be repaired?
Thanks in advance!

First_FLT said:
Hi,
I'm having a bootloop on my sensation xe. I never used a custom rom or anything, and last week i got the following error while updating an app:
"Couldn’t install on USB storage or SD card" I rebooted my phone, and then i got stuck in a bootloop (booting till the htc logo, then rebooting).
I tried to flash a stock RUU from fastboot following this guide http://forum.xda-developers.com/showthread.php?t=1672425 . The command line showed no errors while flashing, but this didn't help.
Also flashing 4ext and cwm recoveries didn't work, the commandline showed no errors, but on the screen of my phone the little progress bar on the upper right side never got filled, and the recovery just goes straight to the htc logo, and then rebooting again..
Version:
Relocked
Pyramid pvt ship s-on rl
hboot-1.29.0000
eMMc-boot
cid: HTC__E11
mid: PG5813001
Is there anything else i can try, or should i send it out to be repaired?
Thanks in advance!
Click to expand...
Click to collapse
unlock again your bootloader with the unlock token.bin code
then see this thread to install roms with S-ON
http://forum.xda-developers.com/showthread.php?t=1631861

rzr86 said:
unlock again your bootloader with the unlock token.bin code
then see this thread to install roms with S-ON
http://forum.xda-developers.com/showthread.php?t=1631861
Click to expand...
Click to collapse
Thanks for your reply.
But like I said, flashing 4EXT recovery is not working. It seems to flash ok (no errors), but when i try to access the recovery it just skips to the boot loop again.

First_FLT said:
Thanks for your reply.
But like I said, flashing 4EXT recovery is not working. It seems to flash ok (no errors), but when i try to access the recovery it just skips to the boot loop again.
Click to expand...
Click to collapse
did you try to install the recovery with unlocked bootloader?
because with relocked it won't work
edit:try to install 4ext using step 2 from the guide i linked to you if you haven't done it already

rzr86 said:
unlock again your bootloader with the unlock token.bin code
then see this thread to install roms with S-ON
http://forum.xda-developers.com/showthread.php?t=1631861
Click to expand...
Click to collapse
rzr86 said:
did you try to install the recovery with unlocked bootloader?
because with relocked it won't work
edit:try to install 4ext using step 2 from the guide i linked to you if you haven't done it already
Click to expand...
Click to collapse
Yes, i tried with unlocked bootloader and just like that step from the guide. After that i tried to flash again a stock ruu so that's why the bootloader was relocked again.

what firmware do you have?
which ruu did you use?

rzr86 said:
what firmware do you have?
which ruu did you use?
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: 11.24A.3504.31_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.153
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813001
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3778mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I tried :
rmk-pyramid-stock_ics_3.32.401.3-v1
OTA_PYRAMID_LE_ICS_35_S_HTC_Europe_3.32.401.105-1.73.401.4
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_281004_signed

the last one it was suppose to work
that is what you need.nevermind
re-run ruu again and see this time if it will work
also did you do a factory reset?

rzr86 said:
the last one it was suppose to work
that is what you need.nevermind
re-run ruu again and see this time if it will work
also did you do a factory reset?
Click to expand...
Click to collapse
Running the ruu again now. I did try a factory reset, but again it jumps straight to the htc logo and then loops again
Edit: Same thing, rom update successfull, but keeps boot looping.. I did notice that the update seem to jump from 65% to 100% very fast, could that mean something?

You have latest hboot (1.29), AFAIK it cannot be completely unlocked.
Also, it is 'Relocked' ? Use htc dev token to unlock it again, than flash 4ext, and use it with 'smartflash' turned on.
Sent from my HTC Sensation Z710e using xda premium

Like i said, i cant seem to flash 4 ext. It gives no errors on flashing, but i cant enter the recovery

First_FLT said:
Like i said, i cant seem to flash 4 ext. It gives no errors on flashing, but i cant enter the recovery
Click to expand...
Click to collapse
give a try with another recovery like cwm
i am out of ideas...

rzr86 said:
give a try with another recovery like cwm
i am out of ideas...
Click to expand...
Click to collapse
I tried cwm allready, same as 4ext. I guess this means off to the repair guy :crying:

see if you can boot to recovery
fastboot boot recovery.img
if booted to recovery ..try to flash a custom rom and see

ganeshp said:
see if you can boot to recovery
fastboot boot recovery.img
if booted to recovery ..try to flash a custom rom and see
Click to expand...
Click to collapse
Same thing:
downloading 'boot.img'...
OKAY [ 1.498s]
booting...
OKAY [ 0.000s]
finished. total time: 1.498s
But phone jumps to htc logo and then keeps looping

First_FLT said:
Same thing:
downloading 'boot.img'...
OKAY [ 1.498s]
booting...
OKAY [ 0.000s]
finished. total time: 1.498s
But phone jumps to htc logo and then keeps looping
Click to expand...
Click to collapse
Ruu also didn't worked right? Then mostly a hardware issue.. If you are soff you could try gingerbread rom.. But that's not the case
Sent from my HTC Sensation using xda premium

[Q] [Help] [Solved] One X Stuck at Fastboot, Out of Ideas, Failed RUU

Hello, after looking into my problem all night (it is 4 a.m. now) I still cannot get my One X out of its issue.
Background to this story:
Bought this phone from a friend who had TWRP2 as the recovery, unlocked, s-on, supercid. I wanted to upgrade to a newer ROM, specifically Carbon on Jellybean 4.2.2, and I needed to update hboot to accept the newer ROM. Follow the procedures of multiple threads and they all lead me down the same path of re-locking your bootloader and let the install do the rest. However, the installer has failed multiple times (error codes 140 and 158) and I am now stuck and have no idea where to go next.
The current status of the One X is not to great. It now has a relocked bootloader, HBOOT version of 2.14.0000, A broken recovery, what seems to be a mismatched baseband, Stuck at FASTBOOT USB, no ADB, will not boot into a ROM, RUU will not complete its job (fails at sending ROM), and I am all out energy and grammar.
*Trying to re-unlock the bootloader via HTCdev will NOT unlock it.
I am stuck, (yea I am a noob). If you need anymore info, just ask.

I'm not entirely sure, but I think you should try and flash the stock recovery and then RUU. I couldn't find the stock recovery in RedPoint's compilation roll-up thread, but I found it on a youtube video when I searched "att one x stock recovery". After you get the stock recovery installed I believe you should be able to then RUU.

Flashing the stock recovery only really applies when you're trying to take an OTA, it isn't required for an RUU.
Sent from my Evita

whoooops just kidding then. might worth a shot to give it a try though? I was just tossing out ideas.

brotherross said:
I'm not entirely sure, but I think you should try and flash the stock recovery and then RUU. I couldn't find the stock recovery in RedPoint's compilation roll-up thread, but I found it on a youtube video when I searched "att one x stock recovery". After you get the stock recovery installed I believe you should be able to then RUU.
Click to expand...
Click to collapse
I am not exactly sure how to do that.

I honestly don't think that's going to help you anyway.
Sent from my Evita

timmaaa said:
I honestly don't think that's going to help you anyway.
Sent from my Evita
Click to expand...
Click to collapse
Alright, gonna need to fix it later. (Recovery still broken, I assume because of the failed RUU)

Which RUU are you trying to run?
Is this the AT&T version of the One X?
Be aware that running any Jellybean RUU (3.18, 3.17) with S-on and SuperCID will brick the phone. So if you were trying to run a JB RUU, it might actually be a good thing it didn't install.
If you were trying to run an older RUU (2.20, etc.) then it will fail since the hboot version is older (hboot 2.14 goes with 3.1x).
Do you still have a TWRP nandroid available (if not, whey the heck not?!?!). Have you tried to flash TWRP again using fastboot? If that works you can try to get your nandroid restored. With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot.
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
brotherross said:
After you get the stock recovery installed I believe you should be able to then RUU.
Click to expand...
Click to collapse
As already pointed out by timmaaa, this is incorrect. RUU installs stock recovery on its own, and stock recovery is therefore not needed for an RUU (only an OTA).

redpoint73 said:
Which RUU are you trying to run?
Is this the AT&T version of the One X?
Be aware that running any Jellybean RUU (3.18, 3.17) with S-on and SuperCID will brick the phone. So if you were trying to run a JB RUU, it might actually be a good thing it didn't install.
If you were trying to run an older RUU (2.20, etc.) then it will fail since the hboot version is older (hboot 2.14 goes with 3.1x).
Do you still have a TWRP nandroid available (if not, whey the heck not?!?!). Have you tried to flash TWRP again using fastboot? If that works you can try to get your nandroid restored. With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot.
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
As already pointed out by timmaaa, this is incorrect. RUU installs stock recovery on its own, and stock recovery is therefore not needed for an RUU (only an OTA).
Click to expand...
Click to collapse
Yes, this is the AT&T version.
I was trying to do an RUU with RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25.
Anytype of backup was made on the phone with TWRP, if TWRP still exists on the phone, it should be there.
I have not tried flashing TWRP back. I can try that next, can you point me in the right direction? Which version of TWRP do you recommend? (I am a noob)
"With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot." I am not aware of this, (again, noob) do I just extract the boot.img from the zip and use 'fastboot flash boot boot.img' ?

It looks like the problem is that you're trying to run an RUU that is older than your current firmware version. So, you would need to use a later RUU. But, like Redpoint said, if you are s-on and SuperCID this will brick your device. Maybe what you should try first is flashing TWRP recovery again and seeing if you can restore a backup or even just flash another ROM.
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and see if you can restore a backup. You are s-on so you will need to flash the boot.img from the ROM that's backed up after restoring it. If you didn't backup the boot partition you might be out of luck.
If this is the case, download a ROM (and gapps if it's an aosp ROM), extract the boot.img from the ROM zip and place it in your fastboot folder on your PC, copy the ROM zip (and gapps if applicable) to your phone, flash ROM zip (and gapps if applicable) in TWRP, reboot to bootloader, connect to pc, give this command:
Code:
fastboot flash boot boot.img
Reboot your phone and hopefully it will boot.
Sent from my Evita

timmaaa said:
It looks like the problem is that you're trying to run an RUU that is older than your current firmware version. So, you would need to use a later RUU. But, like Redpoint said, if you are s-on and SuperCID this will brick your device. Maybe what you should try first is flashing TWRP recovery again and seeing if you can restore a backup or even just flash another ROM.
Download TWRP 2.6 from . Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and see if you can restore a backup. You are s-on so you will need to flash the boot.img from the ROM that's backed up after restoring it. If you didn't backup the boot partition you might be out of luck.
If this is the case, download a ROM (and gapps if it's an aosp ROM), extract the boot.img from the ROM zip and place it in your fastboot folder on your PC, copy the ROM zip (and gapps if applicable) to your phone, flash ROM zip (and gapps if applicable) in TWRP, reboot to bootloader, connect to pc, give this command:
Code:
fastboot flash boot boot.img
Reboot your phone and hopefully it will boot.
Sent from my Evita
Click to expand...
Click to collapse
I may need to reiterate, that my bootloader is still locked.

MDAWG25 said:
Yes, this is the AT&T version.
I was trying to do an RUU with RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25.
Click to expand...
Click to collapse
This is why you are getting errors 140 and 158. As timmaaa mentioned, you can't run an older RUU than the hboot that is already on your phone. The RUU you stated is very old, the 1.73 firmware with 1.09 hboot that came out at the phone's release. You are on hboot 2.14, so once the RUU sees that your hboot version is greater than that of the RUU (1.09), it fails.
Thye 3.18 RUU (which comes with hboot 2.14) would be what you want. BUT as already mentioned, you should not run this with S-on and SuperCID, as there is a bug with the Jellybean RUUs where this combo will brick the phone (not fixable without JTAG or new motherboard).
Follow timmaaa's steps in the previous post.
---------- Post added at 10:40 AM ---------- Previous post was at 10:37 AM ----------
MDAWG25 said:
I may need to reiterate, that my bootloader is still locked.
Click to expand...
Click to collapse
You might be in a catch-22 here then. As you know, you can't install custom recovery with a relocked bootloader (and S-on). You can keep trying to unlock it, but I'm not sure if that can be done if the phone can't boot.

MDAWG25 said:
I may need to reiterate, that my bootloader is still locked.
Click to expand...
Click to collapse
Sorry, I missed that. As Redpoint said above, you might be in a catch 22 situation here unfortunately.
Sent from my Evita

Yeah, normally RUU would be the answer. But the RUU bricking bug mentioned is stopping you from going that route.
Keep trying to unlock the bootloader. If you were able to relock in the current condition, maybe you can unlock. Unlocking is quirky and will fail, then will succeed after multiple attempts. So just the fact it hasn't worked yet, doesn't necessarily mean it won't.

redpoint73 said:
Yeah, normally RUU would be the answer. But the RUU bricking bug mentioned is stopping you from going that route.
Keep trying to unlock the bootloader. If you were able to relock in the current condition, maybe you can unlock. Unlocking is quirky and will fail, then will succeed after multiple attempts. So just the fact it hasn't worked yet, doesn't necessarily mean it won't.
Click to expand...
Click to collapse
I am currently not home to interface with the device physically (RDP). I should be returning around 4PM EST.
The superCID was written by the previous owner. Writing a generic CID (like HTC_001) is not an option with s-on, is it?
*Are there any RUUs that won't brick when flashing?

<Sorry for the double post but this post is different then my last>
Interesting thing, I can still write the recovery image even though fastboot claims it is 'relocked'. Here is the command line output.
sending 'recovery' (8028 KB)...
OKAY [ 0.993s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
The signature checking failed, but it still accepted the image. Not sure if this means anything.

You could try hex editing your CID back to its original CID, but it must be the original CID to match the CID that the RUU is looking for, not just any CID. In order for this to work your would need to have adb fully working though. Please note the method I linked to above is to gain SuperCID, but the principle is the same, you just want to change 11111111 back to CWS__001 for an at&t phone.
The only RUUs that won't brick are the lower ones, which you can't run because you're s-on.
Sent from my Evita
---------- Post added at 01:26 AM ---------- Previous post was at 01:25 AM ----------
MDAWG25 said:
Interesting thing, I can still write the recovery image even though fastboot claims it is 'relocked'. Here is the command line output.
sending 'recovery' (8028 KB)...
OKAY [ 0.993s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
The signature checking failed, but it still accepted the image. Not sure if this means anything.
Click to expand...
Click to collapse
Can you actually enter recovery? The failed message tells me that it hasn't worked.
Sent from my Evita

timmaaa said:
You could try hex editing your CID back to its original CID, but it must be the original CID to match the CID that the RUU is looking for, not just any CID. In order for this to work your would need to have adb fully working though. Please note the method I linked to above is to gain SuperCID, but the principle is the same, you just want to change 11111111 back to CWS__001 for an at&t phone.
The only RUUs that won't brick are the lower ones, which you can't run because you're s-on.
Sent from my Evita
---------- Post added at 01:26 AM ---------- Previous post was at 01:25 AM ----------
Can you actually enter recovery? The failed message tells me that it hasn't worked.
Sent from my Evita
Click to expand...
Click to collapse
Fastboot claims it wrote the recovery image, it just failed the signature check, unless it reverted, should it still be there?
I am not home to try it. I am RDPing to my computer at home, which the phone is connected to. I should be home at 4PM EST (4 hours from now).
Here is a 'getvar all'
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.17.32.09.12
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT246*********** (omitted for privacy)
(bootloader) imei: 359****************** (omitted for privacy)
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4177mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
See anything out of the usual?
Being able to unlock the bootloader will solve all my issues, I should be able to try again when I get home.

It looks to me like it failed while writing, but I may be wrong. The info you just posted looks to be ok. I'd continue to try unlocking the bootloader.
Sent from my Evita

timmaaa said:
It looks to me like it failed while writing, but I may be wrong. The info you just posted looks to be ok. I'd continue to try unlocking the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
I won't post again until 4pm est, as I do not have full access to the device.
Thank you for your help, I really do appreciate it.

[q] not booting

My HTC One SV (LTE europe version ) stuck while booting, it displays white logo screen only,
now i unlocked bootloader and tried to flash rom, but failed,
How i can flash a custom rom or original oerating systedm in my phone,
please help me.

anpayy said:
My HTC One SV (LTE europe version ) stuck while booting, it displays white logo screen only,
now i unlocked bootloader and tried to flash rom, but failed,
How i can flash a custom rom or original oerating systedm in my phone,
please help me.
Click to expand...
Click to collapse
Can you get into the bootloader? If you can, you can flash TWRP recovery via fastboot and flash a custom Rom with the recovery.

Yes
thearif said:
Can you get into the bootloader? If you can, you can flash TWRP recovery via fastboot and flash a custom Rom with the recovery.
Click to expand...
Click to collapse
i can get into bootloder, but where can i get TWRP recovery and custom rom file ?

anpayy said:
i can get into bootloder, but where can i get TWRP recovery and custom rom file ?
Click to expand...
Click to collapse
Go to http://forum.xda-developers.com/showthread.php?t=2292432 . Read through and find the recovery there. It is pretty well explained there. I am on my mobile so I am not sure of the link will take you to the first page. It is on the first page. Make sure you get the correct recovery for your phone model.

Original rom
Where i can get original ROM for HTC ONE SV LTE k2ul_4.2.2_3.11.401.1 ???

anpayy said:
Where i can get original ROM for HTC ONE SV LTE k2ul_4.2.2_3.11.401.1 ???
Click to expand...
Click to collapse
That I do not know, but if my memory serves me right, there was a thread either in android development or general sections with the latest OTAs. You might wanna search for that...

anpayy said:
Where i can get original ROM for HTC ONE SV LTE k2ul_4.2.2_3.11.401.1 ???
Click to expand...
Click to collapse
You've already got the link to my index thread, but it seems you are to lazy to have a look at it. You even only need to watch for the software number and you will easily find what you are searching for.

Os intallation failed
i tried to install OTA update through TWRP recovery , but it failed

You can't flash this in recovery. Use TWRP recovery and flash the rom (not the Ota). Links are in my index thread.

Installed rom
Sucessfully instaled Viper SV rom,
but still phone did not booting,

Did you also flash boot.img of the rom in fastboot?

no
I missed to boot boot.img,
Now phone is working perfectly...........
Thanks all........specially old.splatterhand & thearif

Nice

anpayy said:
I missed to boot boot.img,
Now phone is working perfectly...........
Thanks all........specially old.splatterhand & thearif
Click to expand...
Click to collapse
Good to hear that...

Hi all,
I'm new in this forum so I post there.
My problems starts after try to updete htc one sv k2_ul. After update I get red triangle and then my phone freezed on white screen with logo.
Try to do factory reset from bootloader, but nothing happen. After few days looking information I unlock bootloader and try flash new boot, but after that I get Tampered. I found if I must s-off, but how I can get it? My pc found phone only on fastboot mode. Any ideas?

miegas said:
Hi all,
I'm new in this forum so I post there.
My problems starts after try to updete htc one sv k2_ul. After update I get red triangle and then my phone freezed on white screen with logo.
Try to do factory reset from bootloader, but nothing happen. After few days looking information I unlock bootloader and try flash new boot, but after that I get Tampered. I found if I must s-off, but how I can get it? My pc found phone only on fastboot mode. Any ideas?
Click to expand...
Click to collapse
You can't get S-off, without working OS.
You don't have an OS anymore on your phone?
Are you running a custom recovery like TWRP?
Run this fastboot cmd and copy the output here (remove your imei & serial number):
Code:
fastboot getvar all

old.splatterhand said:
You can't get S-off, without working OS.
You don't have an OS anymore on your phone?
Are you running a custom recovery like TWRP?
Run this fastboot cmd and copy the output here (remove your imei & serial number):
Code:
fastboot getvar all
Click to expand...
Click to collapse
My os just stop working.
I don't try TWRP, today will look more about that.
(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.401.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4143mV
(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.075s
edit
I flashed TWRP and I make restore, but phone won't start anyway. Maybe need to flash new os?

Flash the stock rom in TWRP, and don't forget to flash boot.img of the rom in fastboot.
Links are in my index thread.
Make a backup in recovery (just in case) and a wipe (advanced -> everything except int & ext sdcard) before.

old.splatterhand said:
Flash the stock rom in TWRP, and don't forget to flash boot.img of the rom in fastboot.
Links are in my index thread.
Make a backup in recovery (just in case) and a wipe (advanced -> everything except int & ext sdcard) before.
Click to expand...
Click to collapse
Something I make wrong. I flashed TWRP, then installed ViperSV, phone restarted and booted TWRP. Then I found boot.img in yours index thead.
Then in fastboot flashed new boot, but phone still booting in TWRP. What I make wrong?

You need to flash the boot.img thats inside the ViperSV.zip, not any from my index thread.

I have no ROM. How install one?

Hi there!
I unlock the bootleader and root my device (HTC One S) to install another ROM.
I have done a full clean, so I have nothing. I installed the clockworkmod recovery.
What Can I do to install the factory rom and let my device like factory, but with the bootloader unlocked?
PD: Sorry with my english.

jajasuperman said:
Hi there!
I unlock the bootleader and root my device (HTC One S) to install another ROM.
I have done a full clean, so I have nothing. I installed the clockworkmod recovery.
What Can I do to install the factory rom and let my device like factory, but with the bootloader unlocked?
PD: Sorry with my english.
Click to expand...
Click to collapse
You can relock your bootloader, flash a RUU (stock firmware package), unlock the bootloader again. Or you can just flash a sense based custom rom. BUT if I was you, I would go for a Kitkat (Android 4.4.4) or Lollipop (5.0.2) custom rom, as it really improves your One S

LS.xD said:
You can relock your bootloader, flash a RUU (stock firmware package), unlock the bootloader again. Or you can just flash a sense based custom rom. BUT if I was you, I would go for a Kitkat (Android 4.4.4) or Lollipop (5.0.2) custom rom, as it really improves your One S
Click to expand...
Click to collapse
Thanks for answering.
I prefer the second jejeje
Which rom would you recommend me? It doenst matter if it is kitkat or lollipop. I wanna use the mobile
I dont know if it is a S3 or S4 :S

jajasuperman said:
Thanks for answering.
I prefer the second jejeje
Which rom would you recommend me? It doenst matter if it is kitkat or lollipop. I wanna use the mobile
I dont know if it is a S3 or S4 :S
Click to expand...
Click to collapse
Thats quite bad Are you familiar with using fastboot commands? Its important if its S3 or S4.

LS.xD said:
Thats quite bad Are you familiar with using fastboot commands? Its important if its S3 or S4.
Click to expand...
Click to collapse
Yes, I have installed some recoveryes using it
What should I do?

jajasuperman said:
Yes, I have installed some recoveryes using it
What should I do?
Click to expand...
Click to collapse
Connect phone in "fastboot" mode to your computer.
Open command line and type:
fastboot getvar all
Post the output here but remove your "IMEI"

LS.xD said:
Connect phone in "fastboot" mode to your computer.
Open command line and type:
fastboot getvar all
Post the output here but remove your "IMEI"
Click to expand...
Click to collapse
Here u have:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH24WW408505
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4174mV
(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

HTC One S - S4 - Europe
1. step: flash actual recovery
Fastboot flash recovery openrecovery-twrp-2.8.5.0-ville.img
Once done choose your rom from HERE

LS.xD said:
HTC One S - S4 - Europe
1. step: flash actual recovery
Fastboot flash recovery openrecovery-twrp-2.8.5.0-ville.img
Once done choose your rom from HERE
Click to expand...
Click to collapse
Installed.
I´ll choose this: http://forum.xda-developers.com/htc-one-s/development/rom-resurrection-remix-lollipop-t2986405
What is the second step?

jajasuperman said:
Installed.
I´ll choose this: http://forum.xda-developers.com/htc-one-s/development/rom-resurrection-remix-lollipop-t2986405
What is the second step?
Click to expand...
Click to collapse
Download ROM - GApps - SuperSU
copy all to your sdcard. (you can connect your phone via twrp recovery: "Mount" --> "Enable MTP"
then press "Install" and select the downloaded zips.
Order: 1. Rom 2. GApps 3. SuperSU (4. Kernel)
You can optionally use a "custom kernel" e.g. Frosted Kernel which can be controlled with Trickster Mod

LS.xD said:
Download ROM - GApps - SuperSU
copy all to your sdcard. (you can connect your phone via twrp recovery: "Mount" --> "Enable MTP"
then press "Install" and select the downloaded zips.
Order: 1. Rom 2. GApps 3. SuperSU
Click to expand...
Click to collapse
I tried only flashing the Rom, and when I reboot, I see a black screen and the device do nothing :S
The Roms says something habout 2.15 and 2.16. Do I nothing something else?

jajasuperman said:
I tried only flashing the Rom, and when I reboot, I see a black screen and the device do nothing :S
The Roms says something habout 2.15 and 2.16. Do I nothing something else?
Click to expand...
Click to collapse
Yup i forgot that your phone is S-ON. S-ON means you need to flash the kernel manually via fastboot each time you install a rom. Flash 1. 2. 3. and then connect your phone in fastboot mode to the computer.
Extract "boot.img" from the rom.zip and flash it via fastboot:
Fastboot flash boot boot.img

LS.xD said:
Yup i forgot that your phone is S-ON. S-ON means you need to flash the kernel manually via fastboot each time you install a rom. Flash 1. 2. 3. and then connect your phone in fastboot mode to the computer.
Extract "boot.img" from the rom.zip and flash it via fastboot:
Fastboot flash boot boot.img
Click to expand...
Click to collapse
You are the best!
Thank thank thank you very very much DD
Wow

jajasuperman said:
You are the best!
Thank thank thank you very very much DD
Wow
Click to expand...
Click to collapse
You're happy - me too

Bootloop - unable to get to recovery - maybe no OS?

Folks, 7 rooted devices over last 7 years, and I have usually been able to find a solution without having to start a new thread... however, this time... I better get an expert opinion.
Essentially, here are the facts... I was flashing a rom yesterday on my wife's m8, and the wifi would not work. I thought about it, and then figured it likely was that I had not updated to latest TWRP prior to flashing. So I restored an old backup, I think the one I made right after rooting, which was 1.5 yrs ago, maybe more. That flashed fine, except after many tries via many methods, I could not get TWRP updated, and in fiddling around, I clicked update software, which downloaded the Verizon kitkat update, and started installing it... that was a mistake, finger too fast notwithstanding... I did not need to do it at all, since I was going to flash something new anyway right after updating recovery. Anyway phone appeared to be stuck, I powered it off (Vol up + Power) and went into bootloader (Vol down while it powered up) to go back into recovery and start over. However, the phone went into a boot loop and has since given me much grief over the past few hours.
Output from getvar all is below. It appears to be missing the OS - which kind of makes sense, if I interrupted it midway through something. The phone neither boots, and refuses to enter recovery - even after flashing recovery using fastboot as well as the Hasoon All in One tool. I also cleared cache. I suspect the recovery is loading, but is hidden behind the boot loop screen (is that possible? not sure, just a guess) because the phone has haptic feedback where the TWRP buttons would be - FWIW.
What should my next steps be? Please advise...
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0321
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: dottat was here
(bootloader) imei: ###
(bootloader) imei2: Not Support
(bootloader) meid: ###
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: fd3e0448
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.021s

First off you should edit you're post to remove the imei and meid. I don't know how but they say people can do bad things with them so they shouldn't be posted publicly.

cntryby429 said:
First off you should edit you're post to remove the imei and meid. I don't know how but they say people can do bad things with them so they shouldn't be posted publicly.
Click to expand...
Click to collapse
Thanks for the heads up, I have taken those out.
I tried fastboot flash zip rom.zip, that failed with error 'remote: not allowed'

montropistic said:
Thanks for the heads up, I have taken those out.
I tried fastboot flash zip rom.zip, that failed with error 'remote: not allowed'
Click to expand...
Click to collapse
I edited out your serial number. As to the not allow error you must do the following first before attempting to flash.
Fastboot oem rebootRUU
Sent from my Nexus 6 using Tapatalk

dottat said:
I edited out your serial number. As to the not allow error you must do the following first before attempting to flash.
Fastboot oem rebootRUU
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thanks dottat, yes, I got to the need of being in RUU just prior to your pointing it out, and on doing that, it failed with remote: 24 parsing android-info fail
Trying again with a different ROM now... let us see.
Edit - and it failed with the different ROM zip with the same error, 24: parsing android-info fail.

montropistic said:
Thanks dottat, yes, I got to the need of being in RUU just prior to your pointing it out, and on doing that, it failed with remote: 24 parsing android-info fail
Trying again with a different ROM now... let us see.
Edit - and it failed with the different ROM zip with the same error, 24: parsing android-info fail.
Click to expand...
Click to collapse
could be a bad download of the RUU

andybones said:
could be a bad download of the RUU
Click to expand...
Click to collapse
hmmm... shall i 'Flash factory RUU zip' (in all in one toolkit, or fastboot). Note that I have not done this yet. I will have to go look for the said factory RUU, should be findable. Can I do that while being unlocked/S off, or do I need to adjust any of those first?

montropistic said:
hmmm... shall i 'Flash factory RUU zip' (in all in one toolkit, or fastboot). Note that I have not done this yet. I will have to go look for the said factory RUU, should be findable. Can I do that while being unlocked/S off, or do I need to adjust any of those first?
Click to expand...
Click to collapse
I personally stay away from toolkits, and use fastboot
you can always RUU, with S-OFF you can downgrade if need be. I would fastboot flash the latest RUU. Or you can put on SD-Card and do that method.
http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103

andybones said:
I personally stay away from toolkits, and use fastboot
you can always RUU, with S-OFF you can downgrade if need be. I would fastboot flash the latest RUU. Or you can put on SD-Card and do that method.
http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Click to expand...
Click to collapse
Yep, grabbing the file from dottats post now, and will flash that. I assume I will do it using option 1 (rename and put it on the root of SD card)... or should I fastboot flash that instead, as you suggested?

montropistic said:
Yep, grabbing the file from dottats post now, and will flash that. I assume I will do it using option 1 (rename and put it on the root of SD card)... or should I fastboot flash that instead, as you suggested?
Click to expand...
Click to collapse
Either way works the same - which one your more comfortable with.

andybones said:
Either way works the same - which one your more comfortable with.
Click to expand...
Click to collapse
OK - so update from my side.
1. Grabbed dottat's RUU file(as pointed out above), checked md5, renamed it, and put it on the root of SD card.
2. Rebooted into bootloader - it saw file, went about updating as per spec - orgasmic.
3. While going through list of updates 2nd cycle, USERDATA - Fail-PU, PG2FS - SPCOSTUM - Fail PU and at the bottom - partition update fail, update fail - press power to reboot - crap.
4. Pressed power - HTC ONE - Vzw Logo - Android is updating - back to orgasmic.
Phone is back to life. Yay!
Going back to bootloader, Phone is still unlocked and S-off. Has the default recovery. I will flash TWRP next.
2 questions - what were the fails, and should i be worried about them?
the issue that got me going down this path still remains. maybe that is a separate topic, but the phone seems to have lost the ability to sense touch in the notification area. I cant pull down notifications, from the portrait mode notifications area. i can pull down in landscape mode, or if i use swipe down in middle of screen in adw.
anyway - will probe into that after TWRP and ROM.
Thanks for all the advice!
Update:
5. Flashed TWRP via fastboot, worked
6. Went into recovery, installed CleanRom v 4.0, worked.
All seems fine. Except that notification pull down issue...

montropistic said:
OK - so update from my side.
1. Grabbed dottat's RUU file(as pointed out above), checked md5, renamed it, and put it on the root of SD card.
2. Rebooted into bootloader - it saw file, went about updating as per spec - orgasmic.
3. While going through list of updates 2nd cycle, USERDATA - Fail-PU, PG2FS - SPCOSTUM - Fail PU and at the bottom - partition update fail, update fail - press power to reboot - crap.
4. Pressed power - HTC ONE - Vzw Logo - Android is updating - back to orgasmic.
Phone is back to life. Yay!
Going back to bootloader, Phone is still unlocked and S-off. Has the default recovery. I will flash TWRP next.
2 questions - what were the fails, and should i be worried about them?
the issue that got me going down this path still remains. maybe that is a separate topic, but the phone seems to have lost the ability to sense touch in the notification area. I cant pull down notifications, from the portrait mode notifications area. i can pull down in landscape mode, or if i use swipe down in middle of screen in adw.
anyway - will probe into that after TWRP and ROM.
Thanks for all the advice!
Update:
5. Flashed TWRP via fastboot, worked
6. Went into recovery, installed CleanRom v 4.0, worked.
All seems fine. Except that notification pull down issue...
Click to expand...
Click to collapse
Run the ruu again. It's not typical to have partition update messages. Bypass is OK but not pu (partition update). Regardless of how it's running right now re-run it.
Sent from my Nexus 6 using Tapatalk

dottat said:
Run the ruu again. It's not typical to have partition update messages. Bypass is OK but not pu (partition update). Regardless of how it's running right now re-run it.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
OK - Yeah - it is running very nice right now, Clean Rom loaded fine, and all systems seem ok. However, per your advice, I will run the RUU again. FWIW, I had grabbed the version with the patch.

dottat said:
Run the ruu again. It's not typical to have partition update messages. Bypass is OK but not pu (partition update). Regardless of how it's running right now re-run it.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
OK, so I finally got around to this. I ran the RUU again, and got a fail on Userdata, and finally the same message at the end, partition update failed - power to reboot.
I let the phone boot, and then ran the RUU again, by straightaway going back into bootloader. This time, no fails, everything went through as per spec.
Thanks for insisting on re RUU. Seems like something was off, and iterating over it cured it finally. You rock, dottat.