Database Info

[Q] Yes, another but documented Boot Loop - Sensation 4G

I examined most if not all Boot Loop related items in XDA-Developers, as well as other sources. Although there are lots of suggestions, I cannot find one that relates to my specific situation. The last thing I want to do is make it worse. So, here's my story. I'll keep it brief, but concise.
I've had my Sensation 4G for a little over two years. Soon after purchase, I rooted it via the Revolutionary mechanism. Unfortunately (I think), I also opted for the Clockwork Mod. Unfortunately, I have not been able to do OTA updates, and find I'm still running 2.3.4.
I recently desired to purchase the HTC One for T-Mobile, and did so. I wanted to pass on my Sensation 4G to my sister. Therefore I needed to unroot it. I did weeks of reading about all the ways to do this. Early last week I attempted doing so by following the directions found here (http://kgs1992.com/ruu-guide/). I used the PG58IMG file found here (http://forum.xda-developers.com/showthread.php?t=1459767#2). The file selected was Firmware 3.33 Universal: (http://d-h.st/SuC). I followed the directions precisely. All appeared to run properly, and appeared to end with successful messages. At the end of the instructions it states "If you experience a boot loop, repeat 4.4.2 again." I did that several times. I still have the boot loop.
I started the process with this...
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.17.1111
RADIO-10.14.9035.01_M
eMCC-boot
Jun 2 2011.22:31:39
HBOOT
(VOL UP) to previous item
(VOL DOWN to next item
(POWER) to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Following afore-mentioned process it says...
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24a. 3504.31-M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
That brings me to my big question. What do I do now? I had hoped to retain my contacts and applications. I'd like to first attempt ways to fix it and still salvage what's on the phone, but ultimately I just need the phone to work. I should also mention that I've downloaded the following two files. My next attempt was going to execute the top one, but I don't know the status of the phone after doing so. Can anyone help me? Are there other things I should try first?
RUU_PYRAMID_ICS_TMOUS_3.32.531.14_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_256085_signed.exe
RUU_Pyramid_TMOUS_1.50.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223976_signed.exe

Micalee said:
I examined most if not all Boot Loop related items in XDA-Developers, as well as other sources. Although there are lots of suggestions, I cannot find one that relates to my specific situation. The last thing I want to do is make it worse. So, here's my story. I'll keep it brief, but concise.
I've had my Sensation 4G for a little over two years. Soon after purchase, I rooted it via the Revolutionary mechanism. Unfortunately (I think), I also opted for the Clockwork Mod. Unfortunately, I have not been able to do OTA updates, and find I'm still running 2.3.4.
I recently desired to purchase the HTC One for T-Mobile, and did so. I wanted to pass on my Sensation 4G to my sister. Therefore I needed to unroot it. I did weeks of reading about all the ways to do this. Early last week I attempted doing so by following the directions found here (http://kgs1992.com/ruu-guide/). I used the PG58IMG file found here (http://forum.xda-developers.com/showthread.php?t=1459767#2). The file selected was Firmware 3.33 Universal: (http://d-h.st/SuC). I followed the directions precisely. All appeared to run properly, and appeared to end with successful messages. At the end of the instructions it states "If you experience a boot loop, repeat 4.4.2 again." I did that several times. I still have the boot loop.
I started the process with this...
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.17.1111
RADIO-10.14.9035.01_M
eMCC-boot
Jun 2 2011.22:31:39
HBOOT
(VOL UP) to previous item
(VOL DOWN to next item
(POWER) to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Following afore-mentioned process it says...
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24a. 3504.31-M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
That brings me to my big question. What do I do now? I had hoped to retain my contacts and applications. I'd like to first attempt ways to fix it and still salvage what's on the phone, but ultimately I just need the phone to work. I should also mention that I've downloaded the following two files. My next attempt was going to execute the top one, but I don't know the status of the phone after doing so. Can anyone help me? Are there other things I should try first?
RUU_PYRAMID_ICS_TMOUS_3.32.531.14_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_256085_signed.exe
RUU_Pyramid_TMOUS_1.50.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223976_signed.exe
Click to expand...
Click to collapse
You will probably have to wipe the data partition, and therefore delete your contacts and apps (but if your contacts are saved on your google account they will be restored).
:
Do you have access to the recovery? from there you can flash a ROM and do a fresh install. I got that problem when I upgraded to the newer firmware, and I just flashed the ROM, and then everything worked fine.

astar26 said:
You will probably have to wipe the data partition, and therefore delete your contacts and apps (but if your contacts are saved on your google account they will be restored).
:
Do you have access to the recovery? from there you can flash a ROM and do a fresh install. I got that problem when I upgraded to the newer firmware, and I just flashed the ROM, and then everything worked fine.
Click to expand...
Click to collapse
I'm not sure I know what the data partition is. I can get to all my apps via play.google.com. I took full Titanium Backups, so maybe that'll be an option. Those backups were copied to my laptop.
As to Recovery, I can access it, but cannot put anything on the sd card as I do not have access to it. Apparently I can only do things via ADB.
I was just reading "A must read for those noobs who want to enjoy ICS". Perhaps there is a solution. There are apparently conflicts with Hboot versions and ICS or something. I just found that, so I'm still looking into that. I don't know how to deal with only Hboot.

Micalee said:
I'm not sure I know what the data partition is. I can get to all my apps via play.google.com. I took full Titanium Backups, so maybe that'll be an option. Those backups were copied to my laptop.
As to Recovery, I can access it, but cannot put anything on the sd card as I do not have access to it. Apparently I can only do things via ADB.
I was just reading "A must read for those noobs who want to enjoy ICS". Perhaps there is a solution. There are apparently conflicts with Hboot versions and ICS or something. I just found that, so I'm still looking into that. I don't know how to deal with only Hboot.
Click to expand...
Click to collapse
You can connect your MicroSD card via another phone to the PC, and also use the "adb push" command to push the ROM files to the root of the microSD card. Also, some recoveries allow mounting the SD card to the PC like doing it when the phone is booted, as an external drive, check for it in the recovery.
To move the ROM files to the SD card:
put the files in the folder where ADB is located
On command line type: "adb push rom.zip /sdcard/rom.zip"
Where rom.zip is the name of the rom file you are going to flash. this should work, here is a full guide to help you pushing the file via ADB: http://forum.xda-developers.com/showthread.php?t=1667929
Good luck

astar26 said:
You can connect your MicroSD card via another phone to the PC, and also use the "adb push" command to push the ROM files to the root of the microSD card. Also, some recoveries allow mounting the SD card to the PC like doing it when the phone is booted, as an external drive, check for it in the recovery.
To move the ROM files to the SD card:
put the files in the folder where ADB is located
On command line type: "adb push rom.zip /sdcard/rom.zip"
Where rom.zip is the name of the rom file you are going to flash. this should work, here is a full guide to help you pushing the file via ADB: http://forum.xda-developers.com/showthread.php?t=1667929
Good luck
Click to expand...
Click to collapse
That certainly sounds doable. I went to the link you provided. I'm not sure how pushing the rom.zip to the sdcard and doing the recovery via the phone's recovery is different than via the adb command as done earlier. The adb command process seemed to work correctly, except for the resulting boot loop. Apparently I still need to determine which rom.zip will leave me with a function phone. The only other difference in what I read at the link you provided was to do the various ["Factory Reset", "Wipe Cache Partition", and "Wipe Dalvik Cache]" commands, which I have not done. I need to determine whether those commands are necessary in my case. Thank you for your contribution.

What's happens here is that you have placed ice cream sandwich firmware with a gingerbread Rom. Gingerbread doesn't support it and as such won't boot. If you want to regain access to everything again the reflash 1.17 firmware from the thread. Then your Rom should boot up. Then jump to recovery and make a full nandroid back up. Then re-flash the ics 3.33 universal firmware and then run one of the ics ruu's you downloaded. That will make the phone have a fresh install of ics and stock HTC sense unrooted
don't try to s-on again as their is no real point to it. It's not going back for warrenty so what's the concern eh?
Good luck pal
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2

Micalee said:
That certainly sounds doable. I went to the link you provided. I'm not sure how pushing the rom.zip to the sdcard and doing the recovery via the phone's recovery is different than via the adb command as done earlier. The adb command process seemed to work correctly, except for the resulting boot loop. Apparently I still need to determine which rom.zip will leave me with a function phone. The only other difference in what I read at the link you provided was to do the various ["Factory Reset", "Wipe Cache Partition", and "Wipe Dalvik Cache]" commands, which I have not done. I need to determine whether those commands are necessary in my case. Thank you for your contribution.
Click to expand...
Click to collapse
If you want you should backup via recovery, but wiping the phone after is necessary. if you managed to push the ROM to the SD-card, you can normally flash. but use a ICS (or newer) ROM, that supports the firmware.
In contrast to what heavy_metal_man said, you can do a nandroid backup as it is, as the files are still there. but you don't have much to do with it.
Edit - If you need any help doing it step by step - I'm here to help, just say where you are stuck on the guide (or just explain)

heavy_metal_man said:
What's happens here is that you have placed ice cream sandwich firmware with a gingerbread Rom. Gingerbread doesn't support it and as such won't boot. If you want to regain access to everything again the reflash 1.17 firmware from the thread. Then your Rom should boot up. Then jump to recovery and make a full nandroid back up. Then re-flash the ics 3.33 universal firmware and then run one of the ics ruu's you downloaded. That will make the phone have a fresh install of ics and stock HTC sense unrooted
don't try to s-on again as their is no real point to it. It's not going back for warrenty so what's the concern eh?
Good luck pal
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Click to expand...
Click to collapse
Thanks heavy_metal_man for that information. In the mean time, while waiting for another suggestion, I decided to try a different rom. That was due to the comments I'd seen about conflicts between Hboot and ICS. So, just for the heck of it I went through whole routine, using ROM V3.12. After doing so (twice), the phone booted! Amazingly, other than thinking it's 1970, it appears to be identical to what it was before I ever did anything. It's still running V2.3.4 of Android, and Sense V3.0. I don't recall which version of Sense was there before. After it booted, I shut it down again and put it in Recovery mode. There have been a number of changes there. Now it says...
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29.2
OpenADSP-v01.6.0.2226.00.1227
eMMC-boot
Dec 26 2011.12:14:25
Does any of this information affect or change your suggestion in any way? I'd still like to get ICS on this thing so the latest is available for when I give it to my sister. I wonder what will happen if I attempt OTA? By the way, it still has Revolutionary CWM V4.0.1.4 on it.

Micalee said:
Thanks heavy_metal_man for that information. In the mean time, while waiting for another suggestion, I decided to try a different rom. That was due to the comments I'd seen about conflicts between Hboot and ICS. So, just for the heck of it I went through whole routine, using ROM V3.12. After doing so (twice), the phone booted! Amazingly, other than thinking it's 1970, it appears to be identical to what it was before I ever did anything. It's still running V2.3.4 of Android, and Sense V3.0. I don't recall which version of Sense was there before. After it booted, I shut it down again and put it in Recovery mode. There have been a number of changes there. Now it says...
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29.2
OpenADSP-v01.6.0.2226.00.1227
eMMC-boot
Dec 26 2011.12:14:25
Does any of this information affect or change your suggestion in any way? I'd still like to get ICS on this thing so the latest is available for when I give it to my sister. I wonder what will happen if I attempt OTA? By the way, it still has Revolutionary CWM V4.0.1.4 on it.
Click to expand...
Click to collapse
you just used a ruu.exe from pc and restored everything to stock condition
but how you were able to keep custom recovery(cwm V4.0.1.4)
when you flashed the 3.33 firmware you could just install a custom ics rom
because with 3.33 firmware the gb rom you had it would never booted
about OTA i assume nothing will happen as long as you have cwm recovery installed
you must have the stock recovery

Well, since you flashed a new rom you can disregard my first suggestion and go straight for running the ics ruu you have. Ota updates will not work if you dont have the stock recovery. But the ruu will give you it so ota will work, but the updates will be for the cid of the rom you flashed. So flash a WWE rom to make sure you get any updates, but at this point their will be few if any.
Aside from that you will be all sorted pal
Sent from my Nexus 7 using Tapatalk 4

Thanks again heavy_metal_man. It wasn't that I ignored your suggestion, I tried the second (V3.12) Rom before I had seen it. As for your last entry, I was following it until you hit me with the WWE reference. As for the V3.12 Rom I used, there was a direct MIB match, and the CID used was cid******, so a direct match was not necessary as far as I can determine. I could have edited the txt file and inserted my actual CID however. Also, was your comment about "the ics ruu I have", in reference to the two RUU_PYRAMID_ICS_TMOUS...etc. files I mentioned that I had already downloaded? Running one of those will be a new experience. I'll run the latest. If that works, I'll be a happy camper. I've learned a lot, but I have a long way to go.

Micalee said:
Thanks again heavy_metal_man. It wasn't that I ignored your suggestion, I tried the second (V3.12) Rom before I had seen it. As for your last entry, I was following it until you hit me with the WWE reference. As for the V3.12 Rom I used, there was a direct MIB match, and the CID used was cid******, so a direct match was not necessary as far as I can determine. I could have edited the txt file and inserted my actual CID however. Also, was your comment about "the ics ruu I have", in reference to the two RUU_PYRAMID_ICS_TMOUS...etc. files I mentioned that I had already downloaded? Running one of those will be a new experience. I'll run the latest. If that works, I'll be a happy camper. I've learned a lot, but I have a long way to go.
Click to expand...
Click to collapse
ah sorry, getting ahead of myself with terminology here WWE stand for world wide English. most unbranded phones run on world wide English roms, and if people are downgrading/upgrading they tend to want unbranded as they will get official htc updates faster
as far as cid`s are concerned they dont really matter as you are s-off and the phone will accept any ruu (rom update utility) you give it. one note of caution though is you have select a t-mobileus ruu and they are ment to be for the tmobile sensation 4g. if you dont have the tmobus 4g it may give you some issues with the radio, meaning you may lose phone signal. ( im not 100% sure but caution is advised )
if you dont have a sensation 4g then download and run this one here. im pretty confident that its a stock ice cream sandwich unbranded rom
Running the RUU is simple enough, just boot the phone into your stock 2.3.4 rom and turn on usb debugging from settings for good measure. Then connect the phone to the pc via the usb cable and then run the RUU. it will connnect to the phone and confirm the phone is the correct model i believe, then it will confirm this is what you want to do. select yes and let it work its magic. its pretty straight forward they phone may reboot several times, this is normal. just dont disconnect the battery or the usb cable and you will be fine. should be done in ten minutes tops
good luck pal

I made it through the RUU process, but not without some difficulty. When I ran the RUU_PYRAMID_ICS_TMOUS_3.32.531.14 version, it died with an Error 155. Fortunately it left everything intact. Then I ran the older RUU_Pyramid_TMOUS_1.50.531.1 non-ICS version. It got the same error. I think these errors must somehow be due to the peculiar results from flashing the PG58IMG file earlier. Once again, it left everything intact. I tried the RUU ICS 3.32 version one more time, except this time I put the phone in flashboot mode first. Curiously, the RUU screen that came up thought it was updating a later version than what was actually on the phone, but IT RAN... all the way through to a successful finish. I was stunned. Now the phone reports...
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24a. 3504.31-M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
The entire process left my SD card intact as well. Amazing. It still says S-OFF as you expected. I may or may not attempt turning S-On again.
One comment I'd like to make about xda-developers. There is an amazing amount of information here. The biggest problem I've encountered is trying to figure out if I'm looking at, or have found, the latest information. Some times I'll find something that looks pertinent, only to find that I'm on page 2 of a 114 page thread, and the information I'm looking at is completely obsolete. It's tough for a noob to decipher it all. Anyway, thanks again for everyone's assistance. I think this is a proper place to terminate this particular thread. Now I'll start looking for the latest information on rooting my new HTC ONE. At least I have a fall back phone in my newly restored Sensation 4G. I'm not sure I'm in love the ONE yet, so perhaps I'll take it back. I'm within my 14 day return window.

I'm glad your sorted pal the threads can be a bit out of date, maintenance of information is not really regulated but as always if people are unsure just ask, quoting the info you have and what you think is the case
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2

Micalee said:
I made it through the RUU process, but not without some difficulty. When I ran the RUU_PYRAMID_ICS_TMOUS_3.32.531.14 version, it died with an Error 155. Fortunately it left everything intact. Then I ran the older RUU_Pyramid_TMOUS_1.50.531.1 non-ICS version. It got the same error. I think these errors must somehow be due to the peculiar results from flashing the PG58IMG file earlier. Once again, it left everything intact. I tried the RUU ICS 3.32 version one more time, except this time I put the phone in flashboot mode first. Curiously, the RUU screen that came up thought it was updating a later version than what was actually on the phone, but IT RAN... all the way through to a successful finish. I was stunned. Now the phone reports...
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24a. 3504.31-M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
The entire process left my SD card intact as well. Amazing. It still says S-OFF as you expected. I may or may not attempt turning S-On again.
One comment I'd like to make about xda-developers. There is an amazing amount of information here. The biggest problem I've encountered is trying to figure out if I'm looking at, or have found, the latest information. Some times I'll find something that looks pertinent, only to find that I'm on page 2 of a 114 page thread, and the information I'm looking at is completely obsolete. It's tough for a noob to decipher it all. Anyway, thanks again for everyone's assistance. I think this is a proper place to terminate this particular thread. Now I'll start looking for the latest information on rooting my new HTC ONE. At least I have a fall back phone in my newly restored Sensation 4G. I'm not sure I'm in love the ONE yet, so perhaps I'll take it back. I'm within my 14 day return window.
Click to expand...
Click to collapse
actually are you sure that you flashed the ruu.exe correctly?
you still have the patched hboot and on top of the screen it still says firmware 3.33 which is the patched one
don't attempt to S-ON.probably you will brick the device
after ruu installation your bootloader should say relocked or locked on top of the screen
edit:if i remember well error 155 means a connection issue

rzr86 said:
actually are you sure that you flashed the ruu.exe correctly?
you still have the patched hboot and on top of the screen it still says firmware 3.33 which is the patched one
don't attempt to S-ON.probably you will brick the device
after ruu installation your bootloader should say relocked or locked on top of the screen
edit:if i remember well error 155 means a connection issue
Click to expand...
Click to collapse
Flashed? All I did was run the program. It did whatever it did. I think the 3.33 was somehow left over from flashing a PG58IMG I'd gotten from here>http://forum.xda-developers.com/showthread.php?t=1459767#2. That failed as explained earlier in this thread. I figured that running the RUU would overwrite that failure, and I'm surprised it didn't. All I care is that I'm now getting OTA updates correctly. Yeah, I won't be trying to S-ON. I've thought about rerunning the RUU (3.32) again, but for now I'm going to just leave well enough alone.
I forgot to mention. This information was in the documentation for the RUU
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
One last note. I returned the HTC ONE, and have reactivated the Sensation 4g which this thread is about. The HTC ONE hardware is wonderful, but I didn't like all the HTC ONE software "features" you can't turn off. Maybe I'll jump ship and go with the Samsung Galaxy S4. In the mean time, this Sensation 4G is okay.

Micalee said:
Flashed? All I did was run the program. It did whatever it did. I think the 3.33 was somehow left over from flashing a PG58IMG I'd gotten from here>http://forum.xda-developers.com/showthread.php?t=1459767#2. That failed as explained earlier in this thread. I figured that running the RUU would overwrite that failure, and I'm surprised it didn't. All I care is that I'm now getting OTA updates correctly. Yeah, I won't be trying to S-ON. I've thought about rerunning the RUU (3.32) again, but for now I'm going to just leave well enough alone.
I forgot to mention. This information was in the documentation for the RUU
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
One last note. I returned the HTC ONE, and have reactivated the Sensation 4g which this thread is about. The HTC ONE hardware is wonderful, but I didn't like all the HTC ONE software "features" you can't turn off. Maybe I'll jump ship and go with the Samsung Galaxy S4. In the mean time, this Sensation 4G is okay.
Click to expand...
Click to collapse
exactly the firmware 3.33 and the 1.27.1100 hboot version are from 3.33 universal firmware zip(from the thread you mentioned)
but as long as you are on S-OFF you can use any ruu.exe if you are also supercid

When the PG58IMG flash failed, I assumed at that time that it failed completely, and that no part of it actually worked. I'm too much of a noob to understand the pieces, or elements of the phone's software vs. firmware. I know the difference of course, but not as they relate to this phone, and certainly not as they relate to all the various flashes or other 'fixes' or other such mechanisms I see here on xda-developers.
If I get the nerve to attempt it, is there a way to get everything to a fully legitimate 'stock' situation? That is, just in case I upgrade to another phone again and want to sell this Sensation 4G? For example, I wonder what would be the result of a factory reset at this point? I realize it'll wipe everything out of course, but I wouldn't care.

Micalee said:
When the PG58IMG flash failed, I assumed at that time that it failed completely, and that no part of it actually worked. I'm too much of a noob to understand the pieces, or elements of the phone's software vs. firmware. I know the difference of course, but not as they relate to this phone, and certainly not as they relate to all the various flashes or other 'fixes' or other such mechanisms I see here on xda-developers.
If I get the nerve to attempt it, is there a way to get everything to a fully legitimate 'stock' situation? That is, just in case I upgrade to another phone again and want to sell this Sensation 4G? For example, I wonder what would be the result of a factory reset at this point? I realize it'll wipe everything out of course, but I wouldn't care.
Click to expand...
Click to collapse
A factory reset only deletes the data partition and cache, not any other partition. There are ROMs that are based on stock (and even stock). By fully legitimate 'stock' situation I believe you mean S-On and every thing stock. There are guies for that in the general and development forums.

[Q] Manual update, need help

Hello,
I am trying to update my phone without losing all of my data and of coarse, root as well. Below is what I am working with:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19AS.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
Recovery TWRP v2.6.3.0
Android Version 4.0.4
Sense 4.0
software # 2.20.502.7.710RD
API Level 4.23
HTC extension 403_1_GA_20
Kernel 3.0.8-01558-g7f75e5b
baseband 0.19as
build 2.20.502.7
That's probably way more than you needed to know, but I like to be through. (c;
anyhow, I want to update everything to the latest version... firmware, hboot (if applicable), OS, radio, etc. without losing my data, recovery or root.
I have downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe from HTC
and OTA_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616bcty3drvawwo01k.zip from my phone.
I tried upgrading using adb sideload (renaming zip from carrier to update.zip) and it failed
I tried upgrading using install feature of TWRP using update.zip and it failed
I then thought I will just extract the .img files and flash using adb, but quickly discovered I don't know what .img file is which. If some one has a better way of accomplishing my goal i am all ears, however if someone can assist in identifying which .img files i should flash and how to best approach it I would be very appreciative.
the files extracted are attached (didn't want to flood the post)

It's better to provide too much information than not enough, which is what most people do lol.
I think you're a bit misguided on the whole process so I'll break it down for you. You've downloaded the right RUU but you don't need the OTA. You're also approaching it with the wrong methodology, you're not meant to extract the RUU and flash any image files manually. All you need to do is connect your phone to your PC in fastboot mode and run the RUU exe program in Windows then follow the prompts. You must get s-off first though, very important, do not skip this step!
You will lose your custom recovery and root, there's no way around that. But getting them back is as easy as flashing the custom recovery again and installing root or a rooted ROM. The RUU shouldn't wipe anything from your sd card but it's a good idea to make a backup just in case. You'll lose text messages, call logs, things like that but you can back those up using backup apps before the process.
So head over to the Rumrunner site and get s-off first and you'll be good to go.
Sent from my Evita

timmaaa said:
It's better to provide too much information than not enough, which is what most people do lol.
I think you're a bit misguided on the whole process so I'll break it down for you. You've downloaded the right RUU but you don't need the OTA. You're also approaching it with the wrong methodology, you're not meant to extract the RUU and flash any image files manually. All you need to do is connect your phone to your PC in fastboot mode and run the RUU exe program in Windows then follow the prompts. You must get s-off first though, very important, do not skip this step!
You will lose your custom recovery and root, there's no way around that. But getting them back is as easy as flashing the custom recovery again and installing root or a rooted ROM. The RUU shouldn't wipe anything from your sd card but it's a good idea to make a backup just in case. You'll lose text messages, call logs, things like that but you can back those up using backup apps before the process.
So head over to the Rumrunner site and get s-off first and you'll be good to go.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the response!
I figured I didn't need both the ruu and the ota, but I didn't know if one had newer componets than the other. Also, I didn't know that s-off had been accomplished, last I checked it was still unavailable.
The reason I was thinking of flashing the images manually was because it was so simple for the nexus 7 upgrade, and prevented data loss. The ruu says data loss will happen on it, so I was skeptical to run it as is. So now I am off to check out that link and get this party started! Thanks again!

Spy_64 said:
Hello,
I am trying to update my phone without losing all of my data and of coarse, root as well. Below is what I am working with:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19AS.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
Recovery TWRP v2.6.3.0
Android Version 4.0.4
Sense 4.0
software # 2.20.502.7.710RD
API Level 4.23
HTC extension 403_1_GA_20
Kernel 3.0.8-01558-g7f75e5b
baseband 0.19as
build 2.20.502.7
That's probably way more than you needed to know, but I like to be through. (c;
anyhow, I want to update everything to the latest version... firmware, hboot (if applicable), OS, radio, etc. without losing my data, recovery or root.
I have downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe from HTC
and OTA_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616bcty3drvawwo01k.zip from my phone.
I tried upgrading using adb sideload (renaming zip from carrier to update.zip) and it failed
I tried upgrading using install feature of TWRP using update.zip and it failed
I then thought I will just extract the .img files and flash using adb, but quickly discovered I don't know what .img file is which. If some one has a better way of accomplishing my goal i am all ears, however if someone can assist in identifying which .img files i should flash and how to best approach it I would be very appreciative.
the files extracted are attached (didn't want to flood the post)
Click to expand...
Click to collapse
If you get stuck or need more info, I threw together a guide with info from the forums that may help:
http://forum.xda-developers.com/showthread.php?t=2593037

By the way, tell me about your footer "HTC Evita Gummy 4.4.2 | Torched KK Kernel S-off | 2.14 | Modified TWRP 2.6.3"..... Cooked rom? How do you like it? How does it compare to stock?

Madcat8686 said:
If you get stuck or need more info, I threw together a guide with info from the forums that may help:
http://forum.xda-developers.com/showthread.php?t=2593037
Click to expand...
Click to collapse
Thanks!

Spy_64 said:
By the way, tell me about your footer "HTC Evita Gummy 4.4.2 | Torched KK Kernel S-off | 2.14 | Modified TWRP 2.6.3"..... Cooked rom? How do you like it? How does it compare to stock?
Click to expand...
Click to collapse
It's a really good Rom. Extremely stable with excellent battery life. It's my current "go to" Nandroid back up I use during the day now. I flash new Roms almost daily when I don't need the phone for work. It's based off AOSP and that's what I like most about it. It has tweaks but not too many. For someone making a jump to 4.4+ Roms, I would highly recommend this one as a starter. We are very fortunate to have many like this and I'm getting around too try all of them (we are very lucky to have some talented individuals working Roms in our Forum.)
As for stock, I have to be honest, I can hardly remember what stock is like. I tried most of the stock Roms a few months ago and I have Nandroid backups of them. I remember a few were very stable but as I said, I'm a sucker for pure AOSP.
AHHH shoot, I suppose I just fielded a question meant for Timmaa, my bad!

Madcat8686 said:
It's a really good Rom. Extremely stable with excellent battery life. It's my current "go to" Nandroid back up I use during the day now. I flash new Roms almost daily when I don't need the phone for work. It's based off AOSP and that's what I like most about it. It has tweaks but not too many. For someone making a jump to 4.4+ Roms, I would highly recommend this one as a starter. We are very fortunate to have many like this and I'm getting around too try all of them (we are very lucky to have some talented individuals working Roms in our Forum.)
As for stock, I have to be honest, I can hardly remember what stock is like. I tried most of the stock Roms a few months ago and I have Nandroid backups of them. I remember a few were very stable but as I said, I'm a sucker for pure AOSP.
AHHH shoot, I suppose I just fielded a question meant for Timmaa, my bad!
Click to expand...
Click to collapse
Thanks for the insight. (c; Know of any place i can see screenshots or more info? better battery life is very important to me. I have been steering clear of aftermarket rom's because it always seems that there is always one thing or another that doesn't work... and it always seems to be either or a combination of, tethering, GPS, MMS, or wifi, all are rather important to me. (c;

Spy_64 said:
Thanks for the insight. (c; Know of any place i can see screenshots or more info? better battery life is very important to me. I have been steering clear of aftermarket rom's because it always seems that there is always one thing or another that doesn't work... and it always seems to be either or a combination of, tethering, GPS, MMS, or wifi, all are rather important to me. (c;
Click to expand...
Click to collapse
The Roms are in the development and original development threads. I don't want to steer you down the wrong path and tell you that one Rom is better than another because that's not the XDA way. It implies that one dev's work is better or inferior in some way (plus it's against the rules.)
I can recommend Gummy Rom as a starter if you are ready to try out a custom Rom. I like it and I consider it a daily driver but a couple of the others are just as good. You just have to flash and find out. Many of the 4.4+ Roms on our Forum are stable and work really well.

well I have tried two different PC's running different OS's, and two different USB cables and I cannot get past
....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (11/120)
Waiting
Test 2: Booting device
Waiting for ADB (49/120)
Device detected.....................
[TTTT********************************************** **********]
Press ENTER to exit
Click to expand...
Click to collapse
when running rumrunner. I cannot seem to find anything out there that fixes it either )c;
Any thoughts?

Sometimes Rumrunner says it's failed but it has actually worked, does it still at s-on in your bootloader?
Sent from my Evita

timmaaa said:
Sometimes Rumrunner says it's failed but it has actually worked, does it still at s-on in your bootloader?
Sent from my Evita
Click to expand...
Click to collapse
Yah bootloader still says s-on. )c;

It's possible that it's the ROM/kernel that's the problem. You might consider flashing the latest MagioRom, I've had confirmed reports of success with that ROM.
Sent from my Evita

timmaaa said:
It's possible that it's the ROM/kernel that's the problem. You might consider flashing the latest MagioRom, I've had confirmed reports of success with that ROM.
Sent from my Evita
Click to expand...
Click to collapse
Wont I lose all my data doing so?

What do you mean by data? If you mean your images, music and such on your sd card, no you won't lose it. You never lose that when changing ROMs, I've flash multiple ROMs every week for the last few years and I've never once lost that data in all this hundreds of flashes.
You will lose your text messages, call logs, apps, stuff like that, but you can use several apps to back those up before you flash and then restore it afterwards. Do you use Titanium Backup? If not I suggest you look into it, it allows you to backup pretty much everything.
Sent from my Evita

timmaaa said:
What do you mean by data? If you mean your images, music and such on your sd card, no you won't lose it. You never lose that when changing ROMs, I've flash multiple ROMs every week for the last few years and I've never once lost that data in all this hundreds of flashes.
You will lose your text messages, call logs, apps, stuff like that, but you can use several apps to back those up before you flash and then restore it afterwards. Do you use Titanium Backup? If not I suggest you look into it, it allows you to backup pretty much everything.
Sent from my Evita
Click to expand...
Click to collapse
Mainly just, well data and apps...stored on sd or internal storage. That's great news though!

No problems. The rule of thumb is this: if it's worth worrying about it's worth backing up, just in case.
Sent from my Evita

I was going to backup using twrp to USB and an OTG cable but apparently that is not implemented in this kernel... so now its onwards to titanium backup... i haven't tried it for a few years now.

another question.... the romrunner page has modified hboots for htc one....does that include onex? could I use it once i get this all sorted out?

No. You don't want to use a modified hboot. Also, in TWRP recovery you can use the mount usb storage feature so your internal storage shows up on your PC and you can backup that way.
Sent from my Evita

Unable to do OTA from 1.09

I have a AT&T One X rooted
HBOOT-1.09.0000
RADIO-0.17.32.09.12
I am attempting to do the OTA's or RUU to bring it up to current because I realized since I had not touched it since first purchased and rooted so none of the OTA's went through. I never gave myself time allowed to figure out how to send them.
Well now I'm trying and I have gotten myself in to a hot mess.
I first tried using the FUU Upgrades provided by Flashalot but it said "wrong update" and I could not find a reason. I backed up a couple and tried 2.14. Well eventually it just stayed at the fastboot "HTC" screen for nearly an hour and appeared locked up. So I pulled it and rebooted. It would not let me get past the boot up screen until I cleared cache's and went back to my stock rom (cmod 10).
Now it will not mount "SD Card" when connected USB and in TWRP. I am also unable to download any files to it via browser or launched phone because it says no SD Card installed.
I attempted to send any of the OTA's via fastboot and it hangs (giving it hours...overnight even). I did writecid 11111111 before sending some with same results.
Any suggestions?
Thanks

stampy101 said:
I have a AT&T One X rooted
HBOOT-1.09.0000
RADIO-0.17.32.09.12
I am attempting to do the OTA's or RUU to bring it up to current because I realized since I had not touched it since first purchased and rooted so none of the OTA's went through. I never gave myself time allowed to figure out how to send them.
Well now I'm trying and I have gotten myself in to a hot mess.
I first tried using the FUU Upgrades provided by Flashalot but it said "wrong update" and I could not find a reason. I backed up a couple and tried 2.14. Well eventually it just stayed at the fastboot "HTC" screen for nearly an hour and appeared locked up. So I pulled it and rebooted. It would not let me get past the boot up screen until I cleared cache's and went back to my stock rom (cmod 10).
Now it will not mount "SD Card" when connected USB and in TWRP. I am also unable to download any files to it via browser or launched phone because it says no SD Card installed.
I attempted to send any of the OTA's via fastboot and it hangs (giving it hours...overnight even). I did writecid 11111111 before sending some with same results.
Any suggestions?
Thanks
Click to expand...
Click to collapse
First question is do you have s-off?
Second question is did you perform a factory reset from the bootloader at some point? I ask this because it looks like your sd card is corrupt, and that's what happens when you perform a factory reset from the bootloader on a modified Evita. Either way I believe you need to wipe your sd card with TWRP before it'll become usable again. If it still isn't usable after a wipe, try mounting it to your PC again so you can format it with Windows.
My last question is what is your end goal? Are you wanting to run a stock ROM and that's why you're wanting to install OTA updates? The rule of thumb for modified phones is to never install OTA updates on them. If you're just looking to update to the latest/latest needed firmware, you can just flash a firmware package or run an RUU. You must have s-off to do this though.
Another thing I should mention is that you don't use fastboot to install OTA updates. It seems like you're not exactly sure about what you're doing, which can be a very dangerous thing when messing with a modified device. I think you need to do a bit more research before continuing ahead. Tell me exactly what your end goal is though and I'll provide as much information as I can.
Sent from my Evita

FUBAR?
timmaaa said:
First question is do you have s-off?
Second question is did you perform a factory reset from the bootloader at some point? I ask this because it looks like your sd card is corrupt, and that's what happens when you perform a factory reset from the bootloader on a modified Evita. Either way I believe you need to wipe your sd card with TWRP before it'll become usable again. If it still isn't usable after a wipe, try mounting it to your PC again so you can format it with Windows.
My last question is what is your end goal? Are you wanting to run a stock ROM and that's why you're wanting to install OTA updates? The rule of thumb for modified phones is to never install OTA updates on them. If you're just looking to update to the latest/latest needed firmware, you can just flash a firmware package or run an RUU. You must have s-off to do this though.
Another thing I should mention is that you don't use fastboot to install OTA updates. It seems like you're not exactly sure about what you're doing, which can be a very dangerous thing when messing with a modified device. I think you need to do a bit more research before continuing ahead. Tell me exactly what your end goal is though and I'll provide as much information as I can.
Sent from my Evita
Click to expand...
Click to collapse
OK So it sounds like I've probably corrupted my memory from what you are saying. Any going back?
1. S-Off. I'm going with no. It was 2 years ago when I rooted it and installed CM10. I do not recall doing this but just flashing CM.
1a. Attempting to do it now just shows error 99 unknown error...
2. Yes. I do believe that I had hit the factory reset. Attempting to do the wipe in TWRP shows "success" but it also shows it could not mount E:\
2a. Still will not let me turn on USB storage. It just spins for a while and ends up giving up when the display is changed.
3. End goal...I could care less about root. I've always used modded ROM's and prefer them. I only did "OTA" when the RUU would not take. I became a bull in a china shop and started banging with a hammer...Was dumb but I think I had already corrupted the memory by hitting factory reset. (I'll be honest I never meant to hit that).
I've rooted and installed many a custom ROM's, but I prefer the simple methods of following one of the many awesome easy setups on here. I'm not completely useless...
I would like to get it back to the SD card working and be able to update the firmware and a moderately functioning ROM.
Thank you for any help. I really do appreciate it.

stampy101 said:
OK So it sounds like I've probably corrupted my memory from what you are saying. Any going back?
1. S-Off. I'm going with no. It was 2 years ago when I rooted it and installed CM10. I do not recall doing this but just flashing CM.
1a. Attempting to do it now just shows error 99 unknown error...
2. Yes. I do believe that I had hit the factory reset. Attempting to do the wipe in TWRP shows "success" but it also shows it could not mount E:\
2a. Still will not let me turn on USB storage. It just spins for a while and ends up giving up when the display is changed.
3. End goal...I could care less about root. I've always used modded ROM's and prefer them. I only did "OTA" when the RUU would not take. I became a bull in a china shop and started banging with a hammer...Was dumb but I think I had already corrupted the memory by hitting factory reset. (I'll be honest I never meant to hit that).
I've rooted and installed many a custom ROM's, but I prefer the simple methods of following one of the many awesome easy setups on here. I'm not completely useless...
I would like to get it back to the SD card working and be able to update the firmware and a moderately functioning ROM.
Thank you for any help. I really do appreciate it.
Click to expand...
Click to collapse
There's no point in attempting s-off at the moment because s-off requires that a working OS is installed. You can tell whether you're s-off by looking at your bootloader, it'll say s-on or s-off in the first line under the unlocked and tampered banners.
Your problem with your sd might be that the version of TWRP you have installed is too old, only the newer versions are able to fix a corrupt sd card. 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 try wiping and mounting the sd card again. Once we have that sorted out we can move onto getting your firmware updated.
Sent from my Evita

OK! Looks like we are getting somewhere! It is now mounted.

Now you can copy files across to flash. You'll need to get s-off now so you can update your firmware. You'll need a bootable OS installed to do that, I'd suggest installing Kickdroid and then you can attempt getting s-off via the Rumrunner method.
Sent from my Evita

You are awesome! Thank you so very much for your help. Up and running.

How far have you gotten?
Sent from my Evita

S-Off and firmware updated and running with different ROM's. I'm golden man. Unless you can think of something I should consider?

As long as you're on the 2.15 firmware or higher, you are indeed golden. I was just curious.
Sent from my Evita

Hey there, I just noticed you made a donation to me with this thread as the reference. I just wanted to thank you, that's very generous of you. Donations aren't expected in return for my assistance but are greatly appreciated. Anyway, thanks again and have a great day.

Is this soft brick?

Hi, I was having issues so i ran a RUU by suggestion and reset my device. afterwards I unlocked, flashed twrp 2.6.3 (2.7+ doesn't work, just boot loop) and then i upgraded to hboot 2.14 so i could install the roms i wanted. since upgrading to 2.14 i was getting new errors so i tried to wipe the device and restart and now I did that all the files are missing.
I cannot mount anything or boot, so i can't install via recovery or sideload at all, because it can't mount to anything. I can't restore or do anything else because it can't mount the cache, data etc.
I tried running the RUU again but now i am getting error 117 and it can't detect the phone, and since it has no OS installed it doesn't go far enough to register with the RUU application, or so i believe.. the phone does work fine, can access fastboot and recovery, i just can't mount or install anything else.
I am currently
Unlocked
S-OFF
HBOOT 2.14 (TextRemoval)
TWRP 2.6.3.0 (Anything higher doesn't work, will just show htc logo(20s), then go to black screen(15s or so) and bootloop
CID:111111111111
Some suggestions would be great. I've run out of ideas and spent the whole day trying different things to fix it.

When you say "so I tried to wipe the device" what exactly do you mean? Did you perform a factory reset from the bootloader? If so, you've corrupted your sd card and that's why you can't mount it. Use TWRP to wipe the sd card and then mount it to Windows and format it. You may need to flash TWRP 2.6 specifically to accomplish this. Once that's done you should be able to copy a ROM across.
You mentioned upgrading to hboot 2.14, and I see you flashed the modified one with the removed red text. That isn't the correct way to do it, you're supposed to run the 3.18 RUU so you get the full firmware. Having just the hboot upgraded is pretty pointless. Plus, those modified hboots have caused problems for a few people so I'd suggest just dealing with the red text for five seconds on boot. Basically what you need to do is run the 3.18 RUU to bring your hboot and firmware back onto line.
Which RUU did you run in the first place? And specifically which ROM build did you try to flash? This information will also help to diagnose why you were boot looping to begin with.
It's probably worth reading the Evita FAQ thread and the How-To Guide For Beginners thread, both links are in my signature, and both threads contain some essential information.
Sent from my Evita

On twrp 2.7,aren't we supposed to delete the .twrp .twrp in twrp folder by using a file explorer? I remember reading that in pandasas twrp o.p
Sent from my Desire HD using Tapatalk

I didn't need to do that, but yes, if you experience problems that's the first thing to do. Reading the OP is essential, and reading the last few pages of a thread is strongly recommended.
Sent from my Evita

timmaaa said:
When you say "so I tried to wipe the device" what exactly do you mean? Did you perform a factory reset from the bootloader? If so, you've corrupted your sd card and that's why you can't mount it. Use TWRP to wipe the sd card and then mount it to Windows and format it. You may need to flash TWRP 2.6 specifically to accomplish this. Once that's done you should be able to copy a ROM across.
You mentioned upgrading to hboot 2.14, and I see you flashed the modified one with the removed red text. That isn't the correct way to do it, you're supposed to run the 3.18 RUU so you get the full firmware. Having just the hboot upgraded is pretty pointless. Plus, those modified hboots have caused problems for a few people so I'd suggest just dealing with the red text for five seconds on boot. Basically what you need to do is run the 3.18 RUU to bring your hboot and firmware back onto line.
Which RUU did you run in the first place? And specifically which ROM build did you try to flash? This information will also help to diagnose why you were boot looping to begin with.
It's probably worth reading the Evita FAQ thread and the How-To Guide For Beginners thread, both links are in my signature, and both threads contain some essential information.
Sent from my Evita
Click to expand...
Click to collapse
Firstly, thanks for your help timmaaa.
The RUU i used was:
RUU_Evita_UL_Telstra_WWE_1.89.841.9_Radio_0.18c.32 .09.01_10.93a.32.20L_release_266699_signed.exe
I simply went to the RUU list and picked the most recent one of my carrier.
I installed it and it worked and booted, however the touch screen did not work. This confused me more because the reason I did a RUU was because the 3 softkeys were no longer working prior, and I was trying to fix it.
I was then having issues flashing roms because of the hboot, so I upgraded the hboot to 2.14 to solve this, using the method and 2.14 Textremoval file in the thread here: http://forum.xda-developers.com/showthread.php?t=2156686
After installing the hboot fine, I then went back to install candykat (to be honest all i want is a working phone, any rom works for me) and then was met with the error that it could not mount E:cache. Now i was also having issues where the bottom buttons in the Recovery menu would not respond (not the softkeys under the screen) and so i tried fixing permissions to this. Either way I got it working again - but was just other strange thing.
I just formatted the phone after mounting it in twrp 2.6.3.0 so now its ready to continue. Not sure what RUU or rom or what to go with next.

You have s-off so you don't need to worry about sticking to RUU's from your carrier, you can run any Evita RUU you like. My advice is to run the 3.18 RUU from at&t, that one will give you the firmware you require for aosp ROMs. Stay away from those modified hboots, just deal with having a red text. Make sure you flash the appropriate recovery for whatever ROM you want to flash, keeping in mind that most (maybe all?) current aosp ROMs require either the unofficial TWRP 2.7.0.8 by @pandasa123, found in our Android Development Section, or the official TWRP 2.7.1.0 from here.
Sent from my Evita

timmaaa said:
You have s-off so you don't need to worry about sticking to RUU's from your carrier, you can run any Evita RUU you like. My advice is to run the 3.18 RUU from at&t, that one will give you the firmware you require for aosp ROMs. Stay away from those modified hboots, just deal with having a red text. Make sure you flash the appropriate recovery for whatever ROM you want to flash, keeping in mind that most (maybe all?) current aosp ROMs require either the unofficial TWRP 2.7.0.8 by @pandasa123, found in our Android Development Section, or the official TWRP 2.7.1.0 from here.
Sent from my Evita
Click to expand...
Click to collapse
How can i flash the RUU without being able to boot?
When installing a RUU it says to turn the phone on and connect it via usb.
I get an error that there is no usb connection. I have tried just having the phone on and sit at the htc screen, going into bootloader, going into fastboot, recovery, mount in recovery. None of these methods connect with the RUU application. Is this normal? I can't remember how i did the RUU the first time around - but I did have access to the OS so i probably ran the RUU with the phone on and idle at homescreen the first time around.

xlmama said:
How can i flash the RUU without being able to boot?
When installing a RUU it says to turn the phone on and connect it via usb.
I get an error that there is no usb connection. I have tried just having the phone on and sit at the htc screen, going into bootloader, going into fastboot, recovery, mount in recovery. None of these methods connect with the RUU application. Is this normal? I can't remember how i did the RUU the first time around - but I did have access to the OS so i probably ran the RUU with the phone on and idle at homescreen the first time around.
Click to expand...
Click to collapse
You don't need the phone to be able to boot to run an RUU. Just boot the phone into the bootloader and start the RUU. The "not having a usb connection" problem can be caused by countless things; incorrect usb port (must be 2.0), incorrect usb cable (original HTC cable is recommended), drivers aren't setup properly. Those are the main offenders.
Sent from my Evita

timmaaa said:
You don't need the phone to be able to boot to run an RUU. Just boot the phone into the bootloader and start the RUU. The "not having a usb connection" problem can be caused by countless things; incorrect usb port (must be 2.0), incorrect usb cable (original HTC cable is recommended), drivers aren't setup properly. Those are the main offenders.
Sent from my Evita
Click to expand...
Click to collapse
I was able to get the RUU working and the 3.18 at&t is now installed and working. However I'm now back to my old issue of the 3 capacitive buttons at the bottom not working.
Is there anything software related to fix this or is it likely a hardware failure? When i tap any of the 3 keys, at best it will activate a touch at the lowest portion of the screen on that particular y axis. Example: I press the home key; instead of going back to the homescreen it does nothing, and at most sends a touch command just above at the bottom of the actual touch screen area.
Also, if you think it is a hardware issue, would it be the digitizer? I see they are $30 or so on ebay and figured i could fix up the phone. Everything else works fine except the damn cap. keys
http://www.ebay.com.au/itm/Genuine-...gitizer-front-panel-replacement-/261100897324

During any of your adventures with flashing on this phone, did the cap buttons begin working again at all? My thought is definitely that it's a hardware issue. The digitizer would be the culprit, but, do not attempt to separate the digitizer from the LCD, it will result in one or both of the items being destroyed. You'll need to buy the LCD + digitizer as a set.
Sent from my Evita

timmaaa said:
During any of your adventures with flashing on this phone, did the cap buttons begin working again at all? My thought is definitely that it's a hardware issue. The digitizer would be the culprit, but, do not attempt to separate the digitizer from the LCD, it will result in one or both of the items being destroyed. You'll need to buy the LCD + digitizer as a set.
Sent from my Evita
Click to expand...
Click to collapse
At most the cap. buttons will light up / flash when the phone does a particular action, but no actual response or input of the cap. buttons registers. I'm going to order the digitizer from the link above and hope for the best. It doesn't clearly say it, but I'm assuming it does come with the digi + screen in one.

I think you're wasting your money, that looks like it's only the digitizer. You can't separate them without destroying at least one.
Sent from my Evita

timmaaa said:
I think you're wasting your money, that looks like it's only the digitizer. You can't separate them without destroying at least one.
Sent from my Evita
Click to expand...
Click to collapse
Hmm, thats a bummer.
On another note. I just picked up the phone and unlocked it and it started vibrating like crazy, opened up the message (sms) app and started inputing random keys on the onscreen keyboard. Definitly something malfunctional with the screen. Bottom cap keys not working and random bouts of the screen randomly inputing.

The vibe crazy thing sounds like what happened to me on an inspire. Flashed wrong firmware
Sent from my HTC One X using Tapatalk

[Q] Ask a Stupid (Firmware) Question

Okay....so I need to twiddle around with my trusty old HOX in order to solve the constant rebooting issues. (I also want to jump ship off of the memory-heavy Viper Venom that's on it to just straight CM or something similarly light weight)
To do that I've got to update the firmware.
And to do that... first I have to identify what bloody firmware I have so that I use the correct updating method and don't brick my one and only device.
I'm not a total noob... I've been working on a beginner/moderate level with Android for 3 years now... I can get around ADB (typos not withstanding) reasonably well, push commands, get to hboot, know fastboot and such... but I am just not finding the specific answers I need right this moment to get this work done. So if Someone can point me in the proper direction, I would be muchly appreciative.
Right Now my bootloader screen says the following
Tampered
Unlocked
Evita PVT Ship S-ON RLHboot 1.09.0000
Radio 0.20os.32.09.10_2
OpenDSP-v31.1.0.45.0815
eMMC-boot
Click to expand...
Click to collapse
So, who can tell me which firmware version contains Hboot1.09? Once I know that, I can start the process of SuperCID and S-OFF to make these updates. Barring that, anyone who can point me to a one-click unlock tool would be great too... the ones I find on the first few pages of the forum all recommend firmware newer than what I know is installed on here according to the above into, and I am leery to use them for risk of bricking my one and only phone.

Your current firmware is actually irrelevant, you need not worry about that at all. All you need to do is get s-off, which should be a sinch. Because you don't have SuperCID (I'm assuming from your last paragraph) you really only have one option, which is the Rumrunner method. It should work with Viper installed, if not it has a good success rate with the Kickdroid ROM.
Rumrunner S-off
Sent from my Evita

So I did have SuperCID... a readCID command demonstrated that.
and thanks to your assuaging my fears, timmaaaa, I was able to flash to 2.15 without a problem.
the problem now... is even after pushing TWRP every way I know how, I can't get into recovery, even with fastboot erase cache. ugh I feel like yanking my hair out.
but at least the phone hasn't randomly slowed down or rebooted since flashing the new firmware. (and the pesky double-reboot that made flashing it such a core in the first place is fixed too)
::edit:: gonna spend the next hour redownloading the venom ro so I can push the boot.img file, maybe that will fix things.

Did you check the md5 of the recovery download?
Sent from my Evita

timmaaa said:
Did you check the md5 of the recovery download?
Sent from my Evita
Click to expand...
Click to collapse
Yes I did. I also tried to install it via a few onboard solutions like goo.im. no go. it says it's been installed, fastboot insists the phone is unlocked and s-off; but it boots to the flash screen, tries to load recovery, fails, and reboots to the rom.
I am going to assume that the unlock is fubar somehow and start from scratch by installing 2.20 and using the HTC unlock, and go from there.
now if only damned downloads didn't take 5 hours on my slow rural connections... thank you isp conglomeracy.