Stock RUU 2.3.5 error 155 - HTC Sensation XL

I was going back to stock ruu and I keep getting error 155. I tried to recover from the error but same thing happens. I can go into recovery (recovery_for_1.28)
new touch recovery for ics 4.0.3. It can't find sdcard, so I can't do anything with recovery.
At the moment it looks like my phone is good enough as paper weight.
Any help to reincarnate it will be greatly appreciated. SOS.

The title says 2.3.5, I've googled error 155 and I'm pretty sure it's because your trying to flash a gingerbread RUU over the official ics update? Try and find a ics RUU. If you haven't done the official update to ics, then try this recovery: http://www.modaco.com/topic/348973-clockworkmod-recovery-5027-unofficial-modaco-edition/

Thank you COSAWA for your input and sorry for wasting your time.
I think error 155 was due to unlocked bootloader. I relocked the bootloader and flashed ics update ruu file for europe, which i found at rapidlibrary.com.
Mission accomplished!

Haha, forgot that, was pretty tired lol, glad you've got it sorted mate!
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium

Related

Bricked again?

So got the Incredible S in the beginning of July and was very happy with it, beat the hell out of my old HD2 who got bricked Desided not to root this one cause it was already android and i didnt want to break the warranty. But then the 2.3.3 update came and i didnt recieve text and calls was dismissed. (it is an own thread about this issue on the forums) so i desided to try a rom from XDA to see if this could help solve the issue. It did not but i rooted the phone (S-off right?) and used it with GSM only.. today i talked with HTC support and got a hold of the RUU_Vivo_HTC_WWE_1.36.405.1_Radio_Radio_20.23.30.0 802U_38.02.01.11_M_release_172670_signed.. the cusomter support guy uploaded it and i installed it with the USB cable.. the installer said everything went fine.. the phone reebots.. boots to the HTC logo screen and turns off again.. and keeps on going in the same cycle..
I can get into bootloader, but when i press "power" to choose recovery it goes straight to the white htc screen again and reebots.. what to do now? Is this one dead also?
Tried rename RUU to PG32IMG and put it on the memory card.. still no luck it says "Bootloader - Bypasses"
"TP - Bypassed"
"TP - Bypassed"
Why? And still no luck tried with two signed RUU's now.. The bootloader says
Vivo PVT SHIP S-OFF RL
HBOOT 6.13.1002
At least i want all the Revolutionary stuff gone.. Any idea? Im out of ideas right now.. Oh geez, it booted the 2.1.3 RUU.. nice.
But why would not the other room work? This is the one i have to get workin.. Any ideas?
Does the RUU got a radio in it? Please share this RUU cause I believe this is not avaible anywhere. I would give it a try then and report if I have issues.
Sent from my HTC Incredible S using xda premium
Yes I think it can be a radio conflict too, perhaps you downgraded it.
Here you go Please give a report if it work on your device
I also want to gain S-ON on my Incredible, used AlphaRevX Beta to get the S-OFF but i need it to be S-ON again, and i cant really fint the information on how to do it. These forums are amazing but very hard to navigate true, and find the information you are looking for.
Was thinking... You said you are S-OFF and then installed the 1.36 RUU. Possibly this RUU or ROM needs an older bootloader. Cause the bootloader cannot be overwritten (I assume you used Alpharev), the installation is aborted.
The newer RUU accepts the current bootloader and therefore is being installed.
I think, when you first downgrade your Hboot to the one that can be overwritten, the RUU should work and you can enjoy Froyo again!
So did it work ?
Sent from my xxx using Tapatalk .
wallytax said:
Was thinking... You said you are S-OFF and then installed the 1.36 RUU. Possibly this RUU or ROM needs an older bootloader. Cause the bootloader cannot be overwritten (I assume you used Alpharev), the installation is aborted.
The newer RUU accepts the current bootloader and therefore is being installed.
I think, when you first downgrade your Hboot to the one that can be overwritten, the RUU should work and you can enjoy Froyo again!
Click to expand...
Click to collapse
How to do this? Do i need to S-ON first? Or?

[Q] Unable to install latest Telstra RUU

Hi all,
I'm having issues trying to restore the latest Telstra RUU and I'm hoping someone will be able to give me a hand with this.
I originally unlocked the bootloader, flashed a CWM recovery, custom ICS ROM, and all was working fine.
I've decided to go back to stock Telstra release but every time I try running the RUU I get an error message saying ERROR [140]: BOOTLOADER VERSION ERROR.
From what I've read, this relates to the bootloader being newer then that included in the RUU. I'm not sure how accurate this is though so if someone could confirm, that would be great. If I do need to downgrade the bootloader, where do I get it from?
The RUU's I've tried flashing are from here: http://www.filefactory.com/f/002b74e0f4775869/
- RUU_HOLIDAY_SENSE3_5_Telstra_WWE_2.27.841.6_Radio_3.01.4720.09_34.06.701020.02_release_231121_signed.exe
- RUU_HOLIDAY_ICS_35_S_Telstra_WWE_3.25.841.4_Radio_3.02.4740.09_34.20.701040.19_release_246698_signed.exe
Neither of these work and both show the same error as indicated above.
HOLIDAY PVT SHIP S-ON RL
HBOOT-1.85.0029
eMMC-boot
Mar 15 2012, 17:16:42
If anyone can provide any assistance getting this phone back to stock Telstra release it would be greatly appreciated. I've been working on it for almost 6-8 hours now and seem to be going around in circles.
Thank you! :good:
You need to relock your boot loader to run an ruu
Sent from my HTC PH39100 using xda premium
Sorry, I forgot to mention that. The bootloader has been relocked.
What hboot do you have currently?
Sent from my HTC PH39100 using xda premium
As above, HBOOT-1.85.0029.
I've managed to flash Velocity² "Nightly Build 5" which is as close to stock as I can get for the time being. Phone is working fine.
I can't seem to find any information at all regarding updating the HBOOT though, and what small information I do come across, it doesn't make a whole lot of sense. I don't even know if 1.85.0029 is the latest. Whether I need to upgrade/downgrade it before the RUU will work which some information I've found seems to suggest.
You shouldn't have to change the hboot to be able to run the ruu. Did you unlock your bootloader again to flash the new Rom?
Sent from my HTC PH39100 using xda premium
I did unlock the bootloader again to flash the new rom, only becasue the RUU wouldn't flash. I've tried flashing the RUU with the bootloader locked and unlocked even though I know it needs to be locked. I've tried flashing the RUU while using both a GB rom and an ICS rom - just incase it makes it difference - it didn't.
I've never had this much trouble flashing an RUU before - it's ridiculous.
You cannot flash an RUU with a lower main version or lower hboot version than what is currently on your phone unless you are S-OFF.
kgs1992 said:
You cannot flash an RUU with a lower main version or lower hboot version than what is currently on your phone unless you are S-OFF.
Click to expand...
Click to collapse
What do you mean by main version?
HBOOT version is 1.85.0029. How can tell if the RUU is lower? If I need to upgrade or downgrade the hboot, where do I find the info on this?
I have read that if the hboot is lower then that of the RUU I wont be able to run it but I could never find any information about how to upgrade/downgrade hboot nor how to tell what version the RUU is.
Nucleotide said:
What do you mean by main version?
HBOOT version is 1.85.0029. How can tell if the RUU is lower? If I need to upgrade or downgrade the hboot, where do I find the info on this?
I have read that if the hboot is lower then that of the RUU I wont be able to run it but I could never find any information about how to upgrade/downgrade hboot nor how to tell what version the RUU is.
Click to expand...
Click to collapse
Main version is the software number.
The one you see in Settings > About > Software Information.
The number should be on the RUU that you downloaded, it's the first set of numbers. for example: 3.25.841.4
How did you go with this, I am in the exact same boat. I want to sell my phone but not with this rom.
I was never able to install the stock Telstra RUU. Could never figure it out. After countless hours and at one stage thinking I'd bricked it, I gave up. I ended up sticking with this ROM (http://forum.xda-developers.com/showthread.php?t=1653317) which hasn't been too bad really.
I would still really love to restore it to factory but in all honesty I don't think it will ever happen.
I managed to extract the boot.img file from the RUU and am having a crack at building the ROM myself. If all is successful I will upload it to my dropbox account and link it.
androidlurv said:
I managed to extract the boot.img file from the RUU and am having a crack at building the ROM myself. If all is successful I will upload it to my dropbox account and link it.
Click to expand...
Click to collapse
That would be awesome. Very interested to know how you get on. :good:
Nucleotide said:
That would be awesome. Very interested to know how you get on. :good:
Click to expand...
Click to collapse
I guess no one ever found out how to fix it? I'm screwed because I can't even flash a new rom as mine cant read my internal_sd
Drunkllamajr said:
I guess no one ever found out how to fix it? I'm screwed because I can't even flash a new rom as mine cant read my internal_sd
Click to expand...
Click to collapse
I was never able to fix it. Still running a custom ROM to this day. I tried for hours to restore the RUU but could never get it to work. :crying:
Nucleotide said:
I was never able to fix it. Still running a custom ROM to this day. I tried for hours to restore the RUU but could never get it to work. :crying:
Click to expand...
Click to collapse
Same here I'm now running Holics 1.3 very similar to stock with some nice addons etc
just s-off and then use that RUU
I can't find the RUU's any more. They have gone from File Factory. I've pretty much given up on trying to restore this to factory. I can't even find up to date information on how to S-OFF - and from memory it's got to be done via hardware hack of some sort? Not real keen on that idea.
That said, I'm looking at flashing CyanogenMod 10 4.1.2 ROM which I'd be more then happy with.
RUU
You might be looking for this http://forum.xda-developers.com/showthread.php?t=2094150&highlight=ruu. I was having the same problem and what I did was find the exact/the same version of the RUU and the version of my phone.

Help!!! Error[155] Unknown Error

Help, I am trying to Install custom rom and i get the Error[155] Unknown Error while trying to S-Off the Device.
Earlier i had tried to S-Off and had done it successfully, somewhere, somehow, i had managed to screwup the phone where it would not pass the the HTC screen. so i had to try and get the phone back to stock and i guess thats where the issue began. I downloaded the RUU "RUU_VIVO_ICS_35_S_hTC_Asia_WWE_4.10.707.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266513_signed" and was successful in installing, after which any RUU i run, i get the Error 155. the RUU is a Asian release and not happy with it as there is no English UK or US in it.
currently the details of my Device are as Follows
Security: S-On
HBoot: 2.02.0002
Radio: 3831.18.00.11_M
Bootloader: Unlocked
Managed to install ROM "vivo_signed_WWE_4.10.405.1_ICS_SENSE36_8" today. But i desperately want to install a ROM with Sense 4. Any help is appreciated. Thanks in advance.
Nav
(Code 155 )means that your bootloader is unlocked !
I do not understand fully , but To install A (Ruu.exe) your bootloader must be relocked
Relock bootloader
And install this Ruu
http://d-h.st/7UC
Greet serge
Sent from my Incredible S using XDA Premium App
77777777777777 said:
(Code 155 )means that your bootloader is unlocked !
Relock
And install this Ruu:
http://d-h.st/7UC
Greet serge
Sent from my Incredible S using XDA Premium App
Click to expand...
Click to collapse
Thank you 77777777777777,
i tried what you said. relocked the boot loader and then ran the RUU you recommended.
I still get the same error
Nav
In fastboot usb to pc !
press power button to select fasboot
And on your phone is (fastboot USB) visible ? Yes
Than install the ruu !
Sent from my Incredible S using XDA Premium App
nvnran said:
Help, I am trying to Install custom rom and i get the Error[155] Unknown Error while trying to S-Off the Device.
Earlier i had tried to S-Off and had done it successfully, somewhere, somehow, i had managed to screwup the phone where it would not pass the the HTC screen. so i had to try and get the phone back to stock and i guess thats where the issue began. I downloaded the RUU "RUU_VIVO_ICS_35_S_hTC_Asia_WWE_4.10.707.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266513_signed" and was successful in installing, after which any RUU i run, i get the Error 155. the RUU is a Asian release and not happy with it as there is no English UK or US in it.
currently the details of my Device are as Follows
Security: S-On
HBoot: 2.02.0002
Radio: 3831.18.00.11_M
Bootloader: Unlocked
Managed to install ROM "vivo_signed_WWE_4.10.405.1_ICS_SENSE36_8" today. But i desperately want to install a ROM with Sense 4. Any help is appreciated. Thanks in advance.
Nav
Click to expand...
Click to collapse
With an unlocked bootloader, you simply need to flash a custom Recovery to your device and then you will be able to flash any custom ROM you want. The only drawback is to remember to manually flash the ROM's boot.img file in FASTBOOT USB mode since you have an unlocked bootloader.
There is a sticky thread that details how to install a custom recovery and flash custom ROMs. It's title indicates HBOOT 1.16 and 2.00, but it will also work with unlocked 2.02.0002. that you have also.
If you really insist of getting S-OFF back, then you will need to visit the Downgrade Script sticky post and use that procedure to downgrade your ROM and HBOOT.
I do Have ClockworkMod Recovery Installed.
Thanks 77777777777777 and tpbklake
Tried what you both have mentioned. Now i got a New Error. Error [140]: BOOTLOADER VERSION ERROR
please advise
Nav
nvnran said:
Thanks 77777777777777 and tpbklake
Tried what you both have mentioned. Now i got a New Error. Error [140]: BOOTLOADER VERSION ERROR
please advise
Nav
Click to expand...
Click to collapse
You are not going to be able to flash an official RUU because you currently have the most recent one installed and you cannot downgrade without using the Downgrade script.
Beside, you said you want a ROM with Sense 4 so your only choice is going to be a custom ROM. So just unlock your bootloader and go to the Development section and try out the different Sense 4 ROMs and quit trying to get a RUU going.
tpbklake said:
You are not going to be able to flash an official RUU because you currently have the most recent one installed and you cannot downgrade without using the Downgrade script.
Beside, you said you want a ROM with Sense 4 so your only choice is going to be a custom ROM. So just unlock your bootloader and go to the Development section and try out the different Sense 4 ROMs and quit trying to get a RUU going.
Click to expand...
Click to collapse
Thank you tpbklake,
I did try to use the Custom Rom by Nik (Nik's Project X)
After installing the ROM, the boot process does not pass beyond the Initial HTC Screen. It gets stuck there. also triedleaving it at the same screen for over an hour.
Any thoughts on that?
Nav
Tried Installing IceCold Sandwich 8.3 and Cooldroid 6.1 (previously Nik's Project X)
All of them give the same result.
after installing the rom, restart, Initial HTC Screen, and stuck there.
your thoughts please.
Nav
nvnran said:
Tried Installing IceCold Sandwich 8.3 and Cooldroid 6.1 (previously Nik's Project X)
All of them give the same result.
after installing the rom, restart, Initial HTC Screen, and stuck there.
your thoughts please.
Nav
Click to expand...
Click to collapse
Try to fastboot flash boot boot.img
Steps are outlined in the sticky by lynt in this forum
Sent from my Nexus 7
nvnran said:
Thank you tpbklake,
I did try to use the Custom Rom by Nik (Nik's Project X)
After installing the ROM, the boot process does not pass beyond the Initial HTC Screen. It gets stuck there. also triedleaving it at the same screen for over an hour.
Any thoughts on that?
Nav
Click to expand...
Click to collapse
nvnran said:
Tried Installing IceCold Sandwich 8.3 and Cooldroid 6.1 (previously Nik's Project X)
All of them give the same result.
after installing the rom, restart, Initial HTC Screen, and stuck there.
your thoughts please.
Nav
Click to expand...
Click to collapse
Once again, when you have the unlocked bootloader and you are flashing a custom ROM via Recovery, you then need to extract the boot.img file that is in the ROM's zip file and flash it manually in FASTBOOT USB mode! That is how you get around the issue with hanging at the HTC Screen and that is the step you have missed. I even gave you a link yesterday to the thread that tells you how to flash a custom ROM on the unlocked hboot.
So please read the posts to your questions very carefully and completely.
---------- Post added at 07:41 AM ---------- Previous post was at 07:40 AM ----------
markj338 said:
Try to fastboot flash boot boot.img
Steps are outlined in the sticky by lynt in this forum
Sent from my Nexus 7
Click to expand...
Click to collapse
Maybe if he hears it from someone else he might get it. Thx.

HTC Raider Messed...

Im with rogers and my HTC Raider was working fien then today i dropped it and it turned off and wouln't get passed the white htc screen so i looked it up and basically people said to factory reset which didn't do anything still stuck at the hboot screen and i got the PH39IMG.ZIP and put it on the micro sd but it said Main Version is older update failed and i have no idea what to do If i get this fixed ill try and pay you on paypal or something
If you can get into hboot try to run the stock ics ruu file .
If your boot loader is unlocked then in order for the ruu to except install you will need to relock it.
Bigtjmc said:
If you can get into hboot try to run the stock ics ruu file .
If your boot loader is unlocked then in order for the ruu to except install you will need to relock it.
Click to expand...
Click to collapse
Installing right now fingers crossed to work thank you man
Let us know how it goes .
Thanks man raider is working
Good deal.

[Q] SXL wont allow me to install correct ruu, any solutions?

***UNLOCKED***
RUNNYMEDE PVT SHIP S-ON
HBOOT-1.28.0003
RADIO-3831.15.00.20_M
eMMC-boot
Mar 16 1012, 12:04:51
RUU
Security fail!
Update fail!
Any idea of how to fix this error? i attached the ruu error with this post!

			
				
s-off phone
It was, installing the ruu turned s-on
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Try relocking the bootlaoder that should work
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Tried that, still didn't work, I went through the log at and its some weird cid error, it doesn't authenticate, I'm searching for a method on how to skip that step during the ruu flash process, but I do have the correct ruu, also the phone does not let me change cid so other then thatbtheres nothing I can do:/
Sent from my Sensation XL with Beats Audio X315e
using xda premium
To install RUU:
SW version of RUU must be newer or the same as max version ever installed in the phone(including fota).
CID must match.
Bootloader MUST be relocked.
That is basically it. No point of skipping anything, the bootloader in the phone performs the check there is no way to fool it. Making it s-off is also pointless since RUU flashes new bootloader first, then reboots the device to flash everything else, your phone will become s-on.
How I fix this? JTAG.
skas_2002 said:
To install RUU:
SW version of RUU must be newer or the same as max version ever installed in the phone(including fota).
CID must match.
Bootloader MUST be relocked.
That is basically it. No point of skipping anything, the bootloader in the phone performs the check there is no way to fool it. Making it s-off is also pointless since RUU flashes new bootloader first, then reboots the device to flash everything else, your phone will become s-on.
How I fix this? JTAG.
Click to expand...
Click to collapse
Back in the day that I had major issues I did s off and everything then flashed GB ruu and it went fine. Ofc you will still need the correct cid or follow the guide in Dev section on how to flash a ruu with different cid.
Sent from my Sensation XL using XDA Premium HD app
It think it is much easier to flash CWM stock rom, then kill recovery and relock bootloader and wait for newer RUU. The phone will be "stock" basically.
And also this: http://forum.xda-developers.com/showpost.php?p=26318550&postcount=2
I could not get to work on the phone after latest FOTA.
Making the phone S-OFF if it does not boot is also a pain in the but))).
skas_2002 said:
It think it is much easier to flash CWM stock rom, then kill recovery and relock bootloader and wait for newer RUU. The phone will be "stock" basically.
And also this: http://forum.xda-developers.com/showpost.php?p=26318550&postcount=2
I could not get to work on the phone after latest FOTA.
Making the phone S-OFF if it does not boot is also a pain in the but))).
Click to expand...
Click to collapse
Yes s off needs a booting system usually it will fail otherwise. Perhaps using dd commands from recovery or boot loader will do the trick but from me its untested.
Sent from my Sensation XL using XDA Premium HD app
I did solve this problem with a purpose brick then riffbox JTAG (full wipe, s-off, deleted recovery partition and relocked boot loader) also i noticed after tagging my phone, i was still curious about why it wasn't flashing the ruu, i downloaded the one dazz provided(ics) and i got an older version (GB) i tried ICS first.. Fail! I tried GB... Success i think it might be a corrupted ruu file, but then again the link that anders gave The ruu didn't work either...
Sent from my HTC SENSATION XL using xda premium
you need to relock bootloader before you use rru,
fastboot oem lock
Click to expand...
Click to collapse
also you need the correct rru, or change your cid in phone, download the latest rru for your CID
also are you on vodaphone?
the latest rru is ICS 2.31.401.2 this may be slightly different for ausie
austrailian cids are:
023 htc
001 hutchinson 3g, optus
021 vodaphone austrailia
The ruu is the correct one (VODAPO21) and it does not let me install ICS based ruu
Sent from my HTC SENSATION XL using xda premium

Categories

Resources