Hi there
i'm really stuck at the moment and i've been reading threads after threads on this forum and i still couldn't find any solution and no luck with search as well.
my current problem is that i flashed a hero rom (i believe it's called myhero) about half a year ago when i first got it, but now i want to go back to the original Roger rom so that i can update to the new RUU. But i have no luck going back to the original rom at all. Anyone here would like to help?? i dun want to see my data plan go to waste just because of this
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT - 1.33.0009 (SAPP50000)
CPLD-12
RADIO - 3.22.20.17
PS: i tried many different ways, including unlockr's unrooting method, someone's nandroid wiped roger rom etc, but either htc sync said usb error or my fastboot screen said update failed. please help~
Should work using this method, just apply the update while the phone is in fastboot mode.
i tried that but i never knew i need to go into fastboot mode, i will give that a try, thank you very much
~dimdim~ said:
i tried that but i never knew i need to go into fastboot mode, i will give that a try, thank you very much
Click to expand...
Click to collapse
You don't usually need it. But if HTC Sync can't find the phone, you can apply the update trough fastboot. Let me hear your result.
yes same as before i get an error 170: usb error, is there any other way :S??
fastboot errors on mine also.
I have RUU which I used a few times, this time one pops me "error 155" and check the CID still gives me H3G-UK H3G__001 but as I check the version does not show any information. Already changed the cables, I have uploaded the drivers, I downloaded the new files from the RUU.
TEMPERED
RELOCKED
VLE PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-1.08es 50.02.16
PpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
If anyone can solve this riddle?
Ironic this happened to you because I was just trying to go back to ( which I have successfully have done several times before ) my stock RUU file. I am also getting the ERROR 155. Maybe our issues are the same.
I have :
- Gone back to a stock rom
- Relocked Bootloader
- tried to run RUU from within Fastboot ( and every other way I could imagine )
Still get the ERROR 155! The only difference now is that I am coming back off a Jelly Bean ROM ( every other time I was on a Sense 4.04 based ROM)
Could that be the issue? Did it update my HBOOT to one that my stock RUU won't recognize? That seems to be were the RUU fails everytime. It blinks fast but I do beleive the RUU installer says something about HBOOT before it craps out.
Any suggestions or help would be appreciated by us both I presume!
Thanks! :fingers-crossed:
Have you checked the ruu log on your c drive?
The utility usually saves one there.
That may provide some incite.
Sent from rooted awesomeness using xda premium
TheArtiszan said:
Have you checked the ruu log on your c drive?
The utility usually saves one there.
That may provide some incite.
Click to expand...
Click to collapse
Thanks for the reply! I didn't even think to look for a log file for the RUU. Sure enough it was right on the root of my hard drive! The log confirms my suspicion :
<T230213><DEBUG><OUT>INFOchecking hboot version...</OUT>
</DEBUG></T230213>
<T230213><DEBUG><OUT>FAILED (remote: 44 hboot version check fail)</OUT>
Somehow my HBOOT has been updated from the last time I have went back to stock. I don't remember doing an update last time I was STOCK and RELOCKED ( i might of though, can't remember! ). Is it possible that the Jelly Bean ROM I had installed after my last RELOCK, updated the HBOOT?
Sooooo.....I went ahead and I have extracted the HBOOT NB0 file from the ROM.ZIP that the RUU creates in a temp folder. Is there a way to push that onto my phone, then run the RUU?
Hope this helps!
So first off, to the OP Kobi71, sorry if I hijacked your thread! I was going to post about my issue and came across yours first which sounded pretty much identical! So hopefully my experience can help you!
So I got it to work! I have successfully flashed my RUU. What I found out from reading other threads and poking around was that my HBOOT was to new for the RUU file I had. There isn't an update RUU for my phone out there so I decided to give the HBOOT downgrade to 1.06 a shot.
[TUT] Downgrade/Unbrick Ville S4
http://forum.xda-developers.com/showthread.php?t=1990043&page=16
I followed the instructions and it all worked out just fine. READ through the instructions twice if you have too!
Understand them if you decide to try this because your essentially bricking your phone (at first). All being said, worked like a charm. Downgraded to HBOOT 1.06 from 1.13. The only "troubles" I had during the process, was that when I did step 9 and 12 the phone would hang on Sending Reset randomly throughout the process. Probably about ten times. So I did this each time :
absolutelygrim said:
" If it stalls at "Waiting for /dev/sdc12, hold the power button down on your phone about 10 seconds, or until your see "Qualcomm. Inc. Gobi Wireless Modem (QDL mode) disappear from your terminal window, then release it. 10 seconds or less after you do this, emmc_recovery will see your phone and proceed "
Click to expand...
Click to collapse
It also hung at the very end of the process too, so again hold the power button down if that happens to you.
After all that was done, I flashed the stock recovery from the ROM.ZIP that i got from the RUU ( don't know if I needed to do this ). Wiped everything/Factory reset. Then i relocked the bootloader. I then ran the RUU file, and it worked perfectly. Just like before. HBOOT was also "upgraded" to 1.08
Hope this helps your situation!
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.
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.