Unable to do OTA from 1.09 - AT&T, Rogers HTC One X, Telstra One XL

Unable to do OTA from 1.09 - AT&T, Rogers HTC One X, Telstra One XL

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.

Related

Inspire 4G Reverting on boot

I have a really strange issue and I've done everything I can think of to fix it to no avail. I'm hoping someone here can give me a few pointers.
I'm working on a Inspire 4G for someone. The issue is that the phone reverts to a specific state no matter what I do. For example, if I wipe the phone, the phone boots back up to Froyo with all of his stuff on it. If I try loading an RUU or IMG file (Froyo or Gingerbread), it will "take" but boot to Froyo with all of his stuff on it. It's almost like it wipes itself and loads this image out of nowhere...
Another weird thing, which may or may not be related, is that I see a weird download in his notification tray. Apparently, the file named "WinBej2Setup.exe" was downloaded twice. I did some research on that and everything I see points to some kind of malware for a Windows PC.
Any and all help is appreciated.

Forgive me if this sounds stupid, but you do have S-off correct? I'm not sure about the weird file, have you tried to access it? Also what other roms have you tried to flash? Also what method did you use to root?
Sent from my Inspire 4G using xda premium

I don't have S-OFF. Here's all the bootloader info:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0019
MICROP-0438
RADIO-26.06.04.06_m
Emmc-boot
Dec 27 2010, 14:47:30
As for the file, I'm not sure where it's located. I can only see the notifications that they have finished downloading.
As for the history on the phone, I really can't say much since it's not my personal phone. The person I'm doing this for said he tried to root it using the ACE Hack kit and "some ADB commands" and failed. That's all the information I was given.
At this point, I can load anything to the phone but it will just revert to Froyo in the exact state that it's currently in.
For example, I just tried installing Gingerbread via the official RUU file. It goes through the entire process without a hiccup. Then it reboots and takes forever to load; but when it does, it's back on Froyo with all the owners files...

Personally I would root it, make sure s off, and make sure to format the memory card the corrrect way also.
Then I would install a custom rom.
And the file you speak of is also a game called bejewled. My girl loves that game.
Sent to you by ......
This p-o-s I'm addicted to, and my woman is jealous of.

Reformat the sd card then do an official upgrade thru HTC. Go to the website and download the Gingerbread RUU and HTC Sync. If this doesn't work, complete the root process as suggested.Tell your friend you can't install exe files on Android. They need to be apk files or zip files if installed thru recovery.
Sent from my Inspire 4G using Tapatalk

I appreciate the advice guys, but I think you guys are overlooking what I'm trying to say... I've already tried running the official upgrades from HTC. The RUU says it's completed fine, but on reboot, I'm back on Froyo with all the same stuff on it.
I've even gone as far as extracting the IMG file out of the RUU and loading it through the bootloader. If I do this, it does the same thing-- says everything loaded fine but reverts on boot back to Froyo in the same state it was in prior.
I can temp root the phone using psneuter but that's about it. I have no idea how I'm going to achieve S-OFF if everything I do is wiped on reboot...
What I'm wondering is if there is a way to lock the entire phone down in a state where nothing can be changed; and if so, is there a way to disable this feature.

Are you sure you do not have a file on the root of the card named PD98IMG.zip? You may be installing this every time the phone boots.
How can you install a non RUU ROM when you have s-on?
Something does not make sense here. Also the exe file you talked about has no use on android as android can do nothing with it. Where do you actually see it?
Go back to square 1. What ROM is on the phone now? Do you have clockwork installed?

I'm not sure how to many different times/ways I can explain the same thing. The phone is on stock AT&T Froyo 2.2.1 (1.80.502.3). Currently, there is no custom recovery and it's not rooted.
The issue is that the phone always reverts (almost like it's doing a nandroid restore in the background) during boot to Froyo 2.2.1 (1.80.502.3) with all his stuff on it.
I've installed Gingerbread 2.3.3 (2.47.502.7) via the official AT&T RUU file
I've extracted the PD98IMG.zip from the Gingerbread 2.3.3 (2.47.502.7) RUU and loaded it via bootloader
I've installed Froyo 2.2.1 (1.80.502.3) via the official AT&T RUU file.
I've extracted the PD98IMG.zip from the Froyo 2.2.1 (1.80.502.3) RUU and loaded it via bootloader
I've done a factory reset from within the phone
I've deleted user data & cache with the stock recovery
After performing each and everyone of these steps, the phone hangs on the white HTC screen while booting and eventually boots up to Froyo 2.2.1 (1.80.502.3) along with all the guys stuff on it.
How can you install a non RUU ROM when you have s-on?
Click to expand...
Click to collapse
I don't believe I've ever said that the phone has a non-RUU ROM...
Also the exe file you talked about has no use on android as android can do nothing with it
Click to expand...
Click to collapse
I agree completely; however, the issue I'm running into very unusual. With that being said, I'm trying to point out anything unusual that I notice with the phone. This file most likely has absolutely nothing to do with the problem I'm encountering, but I mentioned it just in case.
Are you sure you do not have a file on the root of the card named PD98IMG.zip? You may be installing this every time the phone boots.
Click to expand...
Click to collapse
I wish this was the case; however, this wouldn't explain why all his stuff is still on the phone... The only time there is a PD98IMG.zip on the sdcard is when I put it there. Even so, I would have to boot the phone into bootloader mode and go through the prompts to get it take. More so, even if I did do this, it would just revert upon rebooting (hints the problem).
I appreciate the help but I think the problem is a little deeper than what has be presented.

That clears it up for me. You obviously know what you are doing. You mentioned "wipe" a few times which confused me. Didn't think there was a way to actually wipe it without a recovery installed. Sounds like one helluva confusing issue there. Goodluck.

Its always going to revert back to the previous state because its still s-on.
You need to get s-off before anything will change.
Sent from my Inspire 4G using xda premium

Its always going to revert back to the previous state because its still s-on.
You need to get s-off before anything will change.
Click to expand...
Click to collapse
This I know is not true-- You can load signed code with S-ON. If what you said was true there would be no way to load an official RUU or OTA...
I appreciate the help, but telling me to get S-OFF (which I've clearly stated that I'm unable to do) is not getting me anywhere.

Is the original ROM branded? Have you tried installing a PD98IMG.zip from a gold card? Just a thought.

[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] Need some help badly, I just messed up my phone

OK i will admit I am over my head on this one. Frustration kicked in and I think I just lost all the data on my phone (pics and videos and everything which is the worst part). Here's the story.
I was originally on Team Venom 4.2 and was having random reboots.
I tried fixing by updating the Radio to ATT 3.18: http://d-h.st/DcT in this thread: http://forum.xda-developers.com/showthread.php?t=1694012 I flashed WITh the RIL (under the line that says do not flash these with newer roms) yeah I know.
flashed 3.18 again without RIL (above the 'do not flash' line
flashed att 2.0 radio
so now my radio still isnt working, tries to prepare sim card and will not work.
now I am trying to flash a new ROM to rewrite everything. tried to install android revolution HD. http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
flashed the android revolution boot.img file and attempted to flash the android revolution rom and would not flash, rebooted twrp after 30%
messed around in twrp a bit and hit factory reset. thought that would do a reboot of the android install. looks like i just formatted my sd card AND deleted android operating system. i cannot reboot into system 'no android os installed' and under twrp file manager i have NOTHING LEFT in my sd card. except the twrp folder. the phone has not been rebooted since.
DID I JUST LOSE EVERYTHING?
i am seriously interested in getting the pictures and data off the sd partition somehow. that is my main concern, i will deal with reinstalling android afterward.
any help will be rewarded, thank you in advance.

beppomarx said:
OK i will admit I am over my head on this one. Frustration kicked in and I think I just lost all the data on my phone (pics and videos and everything which is the worst part). Here's the story.
I was originally on Team Venom 4.2 and was having random reboots.
I tried fixing by updating the Radio to ATT 3.18: http://d-h.st/DcT in this thread: http://forum.xda-developers.com/showthread.php?t=1694012 I flashed WITh the RIL (under the line that says do not flash these with newer roms) yeah I know.
flashed 3.18 again without RIL (above the 'do not flash' line
flashed att 2.0 radio
so now my radio still isnt working, tries to prepare sim card and will not work.
now I am trying to flash a new ROM to rewrite everything. tried to install android revolution HD. http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
flashed the android revolution boot.img file and attempted to flash the android revolution rom and would not flash, rebooted twrp after 30%
messed around in twrp a bit and hit factory reset. thought that would do a reboot of the android install. looks like i just formatted my sd card AND deleted android operating system. i cannot reboot into system 'no android os installed' and under twrp file manager i have NOTHING LEFT in my sd card. except the twrp folder. the phone has not been rebooted since.
DID I JUST LOSE EVERYTHING?
i am seriously interested in getting the pictures and data off the sd partition somehow. that is my main concern, i will deal with reinstalling android afterward.
any help will be rewarded, thank you in advance.
Click to expand...
Click to collapse
Ok, first, you're all over the place. Why did you install a radio+RIL when it explicitly tells you not to? It's actions like this that get people like you into a lot of trouble and destroys phones.
Secondly, there is no Android Revolution HD for this device. I believe you have the HTC One XL / at&t One X (Evita) judging from your post, but like I said there's no ARHD ROM for the Evita, only for the HTC One X (Endeavoru). This leads me to believe that you're jumping between the two device forums, very bad idea, none of the stuff from the Endeavoru forum is compatible with our phone.
You're lucky the ROM install stopped otherwise you would have bricked your phone. Long story short, you have no OS because the ROM install didn't complete, you have a corrupt boot partition because you flashed the ARHD boot.img which isn't compatible. In future do not stray outside our device forum for any reason at all. Here's our forum main page, bookmark it:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Next. Performing a factory reset in TWRP recovery does not wipe user data (images/music etc). I'm not sure what you've done but the factory reset in recovery wasn't it. A factory reset performed in the bootloader does however corrupt the sd card, so never do a factory reset from the bootloader.
You might have a chance at saving some of your data using a data recovery tool in Windows. You'll need to mount usb storage in TWRP for Windows to access the sd. Do not under any circumstances do any writing to the sd card before you attempt to save your data.
In conclusion, you've made numerous mistakes with your device. You need to slow down a bit and educate yourself a bit better, a lack of knowledge when it comes to modifying devices is a very dangerous thing.
Please post the first five lines of your bootloader.
Sent from my Evita.

i could have sworn i got the android revolution rom from the att one x forum but i suppose not....
ok guys thanks so much so far i will pick up again after work today.
bootloader says:
TAMPERED
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT-1.09.000
RADIO-0.19as.32.09.11_2
OpenDSP-v34.1.0.45.1219
eMMC-boot
Apr 2 2012,21:08:24
I'm 99.9% i was s-off before this all...

There isn't and never has been an Android Revolution ROM in this forum. It's kinda easy to make the mistake, the forums are named similarly.
I'm 99.9% sure you weren't s-off before all this. A phone can't change the security status without you doing it manually. It just can't happen. Did you actually go through either the Facepalm or Rumrunner s-off processes?
Well, you definitely have the Evita (HTC One XL / at&t One X) so make sure you stay within the forum I linked to earlier.
Good luck with attempting to recover your data, I hope you get at least some of it back.
Sent from my Evita.

Ok so as far as mounting my sd card in twrp, there's something up with my screen touch input I think... I am not able to click that particular box in the 'mount' menu. It seems like that part of the screen was not clickable when installing roms and such but once I get into android everything works perfectly.
Is there a way to rotate the screen in twrp?
Also by looking at my bootloader info once I get my sd card mounted and recovered best as I can, what is my best plan of action? Re-lock and flash a stock att ruu and begin from scratch or what? Or just try and load a correct radio and rom? I'm not a complete newbie I know I made a foolish mistake but I have done this quite a few times playing on the inspire, cha-cha, my kids nabi 2 tablets and on this att one x. This is the first time I have gotten really stuck in probably 35 flashes. Just this time I might be over my head...

To be honest I've never tried rotating the screen while in recovery, so I'm not sure about that. Exactly which recovery type (CWM/TWRP) and version number are you using?
I think your best plan of action would be to run an RUU, this will bring everything back to the way it should be. You're lucky in the sense that you're still on quite an early firmware version, so you should have a couple of RUU options. One thing to be careful of though, absolutely do not run a jb RUU if you have SuperCID, it will brick your device. SuperCID + s-on + jb RUU = brick. We should check your CID just in case, connect your phone in fastboot mode and issue this command:
Code:
fastboot oem readcid
Sent from my Evita.

beppomarx said:
i could have sworn i got the android revolution rom from the att one x forum but i suppose not....
Click to expand...
Click to collapse
There is absolutely no ARHD ROM for EVITA. You've made a grave error, and as timmaaa mentioned, you are lucky your phone isn't a paperweight now.
EVDEAVORU is partitioned completely differently from EVITA, so all bets are pretty much off on whether your data is still intact or not. The ROM itself may have overwritten your data. Also, if you happened to do a factory reset in hboot instead of TWRP (as you mentioned) this will corrupt the SD card on modded EVITAs (known issue, and somewhat common error).
Your best bet is to get the phone back up and running using timmaaa instructions. Then see if the files are still on the SD. If the data files aren't easily visible, you can also try data recovery programs to see if they can be salvaged (sometimes corrupted files get dumped to a temp folder, or otherwise recoverable).
But I wouldn't hold my breath on recovering the files. This is what always puzzles me (why folks never back their data, then freak out when its gone of damaged). If your data is important to you, its important enough to back up. And there are so many easy methods to do so (with built-in cloud backup apps and whatnot) yet so many folks neglect to do that. And all you are left with is regret when things do south. Its pretty much a no-brainer to backup anything important to you when modding the phone. I'm puzzling why so many folks never do it.

So since I have the 1.09.000 hboot i am going to download and install this:
1.85.502.3
File Timestamp: 25/05/12
Publically Seen: 06/06/12
Android: 4.0.3
Kernel: 3.0.8-01155-gca24d1e
hboot: 1.09.0000
radio: 0.17.32.09.12_10.86.32.08
adsp: 28.1.0.32.0504
wcnss: 1031120A
tp_syn3202: 3.0_PR1100755
tz: 001.031.511
sbl1: 001.031.503
sbl2: 001.031.501
sbl3: 001.031.502
OTA: OTA_Evita_UL_Cingular_US_1.85.502.3_R2_NEW_NFCPHON ESTORAGE-1.73.502.1_release_263287jkmeqj8u75z409z9.zip
RUU: RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17. 32.09.12_10.86.32.08L_release_262092_signed.exe (Download)
Source: evita-ics-crc-3.0.8-271616b.zip
is this my best bet? I am going to try and check my CID status right now just need to download the android SDK and get that going...
**EDIT**
my CID is 11111111. is that superCID?
**EDIT**
looking for a way to remove superCID. If i just go S-off am i OK to run a RUU or should I keep looking to change my CID back?
**EDIT**
just downloaded WinDrid HTC One XL Toolkit and seems to be up and running fine. my plan so far is to S-off and run the RUU I posted above but I will wait for someone to chime in before I do anything else.. I feel like I am on the edge here and don't want to brick it... I can't find any way so far to return my CID but from what I read if I am S-off it should keep me safe.

S-off won't work unless you're able to boot into a ROM. I'd forget about using a toolkit for now, it completely bypasses some much needed learning, and doesn't always work anyway. I believe all you need to do is relock your bootloader and then run the RUU.
Sent from my Evita.

Ok I will look into how to re-lock that after work today. Can anyone else confirm this? Not that I don't trust you but wording it like 'I believe this will work' makes me ask again...

I'm 99.99% sure it's only the jb and above RUU that you need to worry about while s-on and SuperCID.
Sent from my Evita.

timmaaa said:
I'm 99.99% sure it's only the jb and above RUU that you need to worry about while s-on and SuperCID.
Click to expand...
Click to collapse
ICS RUUs are free of the S-on and SuperCID bug. Plenty of folks have flashed that RUU (such as 2.20) with SuperCID with no issue.

so I am going to relock the bootloader, it's as simple as 'fastboot oem lock'? that's it? before doing so should i bother s-off first? here's my plan of action:
s-off
relock bootloader
run 2.20.502.7 ruu
unlock bootloader again
install twrp
load custom rom
that should work correct?

If you s-off first, I believe you do not need to relock the bootloader to run the RUU. Just s-off, then run the RUU.

As I've previously mentioned, you won't be able to get s-off unless your phone will boot a ROM. The above process looks right.
Sent from my Evita.

got back to stock just fine, now to work my way back to modded. You guys are the best thank you a million.

Please hit the thanks button on any post that you've found helpful on XDA.
Sent from my Evita.

Remember also to either s-off or change cid back to normal, it will assist in the future if you get in a jam like this.
Although s-off and flashing a rom for a different phone(like you did) may have ended up much worse as some of the checks that likely saved you will be disabled.
At very least do not OTA/RUU update to Jellybean while you are s-on and supercid!

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

Sunshine s-off, but can't get Superuser SU Binaries installed.....

I just got S-Off with Sun Shine, but can't seem to get SuperuserSU working (I was going to install TWRP from TWRP Manager after getting SuperuserSU.) Anyone know what I need to do? I looked for a thread that explained the process, but have not found anything. Many thanks!

Flash twrp from fastboot. Flash SuperSU from twrp.
Sent from my XT1254 using Tapatalk

I am trying to flash TWRP with Minimal ADB and Fastboot from here..... http://androidmtk.com/download-minimal-adb-and-fastboot-tool
I keep getting this for messages when I type the command flash twrp.img "cannot load 'twrp.img'
I know that the device is connected since it goes into fastboot when I type "adb reboot bootloader".
Any ideas?

Solved......I am a complete fool. I renamed the recovery image "twrp.img" so the actual file was "twrp.img.img". How embarrassing.....LOL! Time to just go and hit the bar and have a beer! I must have cabin fever after this winter and my mind is not functioning properly. ARGH!

therreid said:
Solved......I am a complete fool. I renamed the recovery image "twrp.img" so the actual file was "twrp.img.img". How embarrassing.....LOL! Time to just go and hit the bar and have a beer! I must have cabin fever after this winter and my mind is not functioning properly. ARGH!
Click to expand...
Click to collapse
It happens a lot[emoji14]
Sent from my XT1254 using Tapatalk

I posted this in the general questions thread, but I wanted to post here as well...
beaups said:
It happens a lot[emoji14]
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
I apologize in advance as I'm sure this has been asked toomany times to count, but I have searched and searched thread after thread to see if I can find a solution for about 23 hrs straight, I'm pretty much out of time & panicking now that I messed up beyond fixing. Any advice, help, or a point in the right direction to the right post would be very much appreciated!!!
So, the problem is, I'm not 100% sure but I think I have "soft bricked" my phone... I gained s-off through Sunshine about a week ago, I have been reading & researching how to root my phone for updating to a custom ROM running 6.0 MM for months now trying to prevent any issues & be as well educated as possible...
Last night I finally gained root access using Kingroot, then switching over superSU BUT of course, I had the problem with the binaries. I installed TWRP app to perform the recovery flash to ext SD because I do have a PC, but it's a work computer so I don't have administrator rights to install any programs/apps on the PC such as ADB, Flashify, etc.
Before I decided to restart my phone I had SuperSU running the # sign in the notifications center (re: the binaries), I also had the TWRP manager I chose my device model, but I did not install any files (at least I don't think I did). I was most concerned on my current backup & flashing that to my extSD. Which is what I thought I had done, or maybe I didn't do anything at all? BTW- I have removed the SD card & inserted into my PC to see what files were on it, and nothing!! Nothing at all to do with SuperSU nor TWRP (I have since installed the latest update SuperSU zip file on that card). All I know is I cannot get my phone on past the Verizon screen, I can perform a hard boot & get back into hboot /fastboot, I have all options on the menu, and have tried every one of them minus the 'factory data reset', 'apply from phone storage' or 'ramdump'. I would have typed in the information that the screen says in HBOOT but my phone literally just died from the screen being on so long :-/ I will add that info if needed once I can boot it back up without use of the charging cable.
Any help on what to do would be so greatly appreciated as apparently I'm freaking out & I'm thinking I'm way in over my head not knowing what exactly happened to cause this!!! Please Help:crying:

M-FayeHTC said:
I apologize in advance as I'm sure this has been asked toomany times to count, but I have searched and searched thread after thread to see if I can find a solution for about 23 hrs straight, I'm pretty much out of time & panicking now that I messed up beyond fixing. Any advice, help, or a point in the right direction to the right post would be very much appreciated!!!
So, the problem is, I'm not 100% sure but I think I have "soft bricked" my phone... I gained s-off through Sunshine about a week ago, I have been reading & researching how to root my phone for updating to a custom ROM running 6.0 MM for months now trying to prevent any issues & be as well educated as possible...
Last night I finally gained root access using Kingroot, then switching over superSU BUT of course, I had the problem with the binaries. I installed TWRP app to perform the recovery flash to ext SD because I do have a PC, but it's a work computer so I don't have administrator rights to install any programs/apps on the PC such as ADB, Flashify, etc.
Before I decided to restart my phone I had SuperSU running the # sign in the notifications center (re: the binaries), I also had the TWRP manager I chose my device model, but I did not install any files (at least I don't think I did). I was most concerned on my current backup & flashing that to my extSD. Which is what I thought I had done, or maybe I didn't do anything at all? BTW- I have removed the SD card & inserted into my PC to see what files were on it, and nothing!! Nothing at all to do with SuperSU nor TWRP (I have since installed the latest update SuperSU zip file on that card). All I know is I cannot get my phone on past the Verizon screen, I can perform a hard boot & get back into hboot /fastboot, I have all options on the menu, and have tried every one of them minus the 'factory data reset', 'apply from phone storage' or 'ramdump'. I would have typed in the information that the screen says in HBOOT but my phone literally just died from the screen being on so long :-/ I will add that info if needed once I can boot it back up without use of the charging cable.
Any help on what to do would be so greatly appreciated as apparently I'm freaking out & I'm thinking I'm way in over my head not knowing what exactly happened to cause this!!! Please Help:crying:
Click to expand...
Click to collapse
You are fine. Start fixing it by flashing the latest s-on ruu I have posted. This will NOT affect your s-off or unlocked boot loader status. Then when done flash twrp via fastboot. (Never use that stinking app). Then flash supersu zip in twrp to root your stock rom. If you have fast internet I can always you using team viewer (free app)

I'm still having trouble...
dottat said:
You are fine. Start fixing it by flashing the latest s-on ruu I have posted. This will NOT affect your s-off or unlocked boot loader status. Then when done flash twrp via fastboot. (Never use that stinking app). Then flash supersu zip in twrp to root your stock rom. If you have fast internet I can always you using team viewer (free app)
Click to expand...
Click to collapse
First,I appreciate you getting back tome so soon. I downloaded the latest RUU onto my SD card, then reloaded it into my phone in bootloader, nothing happened
Right now, I still cannot get past the red Verizon screen, my phone won't turn on fully... The options I have are my "Administrator PW protected work PC" that I cannot run fastboot on, or my Nextbook tablet. Would Team View work on either of these since my phone is out of the question?
Rightnow this is what my HBOOT screen is saying....
**UNLOCKED**
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT- 3.19.0.0000
RADIO- 1.12.20.1211
OpenDSP- v47.2.2-00564-M8975-FO.1024
OS-4.17.605.9
eMMC-boot 2048MB
Aug 11 2015, 22:31:04.0
Thanks in Advance!!!

M-FayeHTC said:
First,I appreciate you getting back tome so soon. I downloaded the latest RUU onto my SD card, then reloaded it into my phone in bootloader, nothing happened
Right now, I still cannot get past the red Verizon screen, my phone won't turn on fully... The options I have are my "Administrator PW protected work PC" that I cannot run fastboot on, or my Nextbook tablet. Would Team View work on either of these since my phone is out of the question?
Rightnow this is what my HBOOT screen is saying....
**UNLOCKED**
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT- 3.19.0.0000
RADIO- 1.12.20.1211
OpenDSP- v47.2.2-00564-M8975-FO.1024
OS-4.17.605.9
eMMC-boot 2048MB
Aug 11 2015, 22:31:04.0
Thanks in Advance!!!
Click to expand...
Click to collapse
If nothing ran you have the file either named wrong or have an extra .zip on the end of the name. Make sure you view file extensions to be sure. It's case sensitive and 0P6BIMG.zip
Leading character is a zero.

First part COMPLETE!
dottat said:
If nothing ran you have the file either named wrong or have an extra .zip on the end of the name. Make sure you view file extensions to be sure. It's case sensitive and 0P6BIMG.zip
Leading character is a zero.
Click to expand...
Click to collapse
Okay, I have hope. Thank You SO MUCH!!! Phone is on (upgrading currently), but IT'S ON:highfive: I think I accidentally used the s-off file instead of the s-on, and I did add the .zip onto that file (since it wasn't showing it w/ it, DUHHH). I will follow the rest of your instruction's very carefully later on, this will take a while, on app 80 out of 279 (bloatware, ugh!!) Hopefully, it goes more smoothly & I won't have to bother you again :fingers-crossed:
Thanks Again!
P.S. Will be contributing ASAP once I get this mess cleaned up. I really do appreciate all of your hard work & the magic that you make happen!!

M-FayeHTC said:
Okay, I have hope. Thank You SO MUCH!!! Phone is on (upgrading currently), but IT'S ON:highfive: I think I accidentally used the s-off file instead of the s-on, and I did add the .zip onto that file (since it wasn't showing it w/ it, DUHHH). I will follow the rest of your instruction's very carefully later on, this will take a while, on app 80 out of 279 (bloatware, ugh!!) Hopefully, it goes more smoothly & I won't have to bother you again :fingers-crossed:
Thanks Again!
P.S. Will be contributing ASAP once I get this mess cleaned up. I really do appreciate all of your hard work & the magic that you make happen!!
Click to expand...
Click to collapse
Well if you used the s-off one that's fine too. You will be rooted already. Just need to flash the latest twrp image and you will be fine.

Database Info

welcome