unlock bootloader 1.50 ruu gives 156 image error - HTC EVO 3D

Can someone please help me out, ive searched but have not found a solution. Long story short. I have an evo3d 1.50 locked bootloader, I am trying to unlock using htc method. I get stuck at step 12 after trying to unlock code bin file. My unit is a refurb it came with hboot 1.50. I read about installing the 2.08 ruu then try to complete the unlock process, I did this. When I try to run the ruu, it gives me a 156 image no image error. I redownloaded 3 times same thing, please someone help me out, I really like to unlock and root this device just like my original evo. Thanks in advance.

Where did you get the Ruu?
I got one from shipped-roms.com and didn't have any problems. Try Them if you didn't already. Maybe just a bad ruu.
Sent from my PG86100 using XDA App

Related

2.08.652.2 ruu file

Does any 1 have the ruu file for the ota update? I need it b/c apparently I'm stuck trying to unlock this stupid 1.50 bootlader and it stops when I unlock the token and I have to run this file to get it to work or do u guys thk I should way for rev root?
black3188 said:
Does any 1 have the ruu file for the ota update? I need it b/c apparently I'm stuck trying to unlock this stupid 1.50 bootlader and it stops when I unlock the token and I have to run this file to get it to work or do u guys thk I should way for rev root?
Click to expand...
Click to collapse
if i were stuck with the latest version of hboot i would probably use htc's method since revolutionary hasn't released an update.
from actual experience, i bought my device on release day and was able to use revolutionary to unlock.
ruu files can be found on goo-inside.me/shooter
I have the same issue, I wish someone would post the file. There is a ruu for hboot 1.50, but everytime I try using it, it gives me a 156 image error.
I found it at shipped-roms.com
I've used Ruu's from them in the past with luck.
Sent from my PG86100 using XDA App
http://www.multiupload.com/09NOXKCUN0
That is where I got the MIRROR for the 2.08 RUU. Haven't tried it yet, but let me know if it works...
That is the link I have used for both ruu's. Each one I tried flashing gave me an image error 156.
As requested
http://shipped-roms.com/index.php?category=android&model=Shooter

[Q] Stuck at HBOOT with fastboot only

Hi,
Well, i got myself into this mess and after 3 days of trying to fix it, i give up and call for your assistance.
I had a working S-ON HBOOT 0.47 rooted Legend running CM7.2 and recently changed to Jelly_Bean_Extras_HomICS_2.0_Venus.
I liked the new rom but link2sd didn't work.
My guess was that i need to have it S-OFF.
So... i headed to HTCDEV but first i needed to be on one of the listed RUU.
My original RUU was RUU_Legend_HTC_ISR_2.05.461.52_Radio_47.39.35.09_7.08.35.21_release_140015_signed.zip
I used the LEGEIMG.zip method to flash the RUU and then i flashed the one from HTCDEV which holds "hboot_legend_7227_1.02.0000_111223.nb0" only.
Now the HBOOT got to be 1.02.0000
After flashing this, i got stuck.
No recovery - i get signature failed message - even after putting CWM update.zip on the SD.
No ADB - at all states, only fastboot sees the device.
RUU update gets fails either due to version 3.30.0000, signature or device.
fastboot flash - i thought i will manually flash the various parts. i get FAILED (remote: signature verify fail).
CID was HTC__K18
did a new goldcard based on the old mail i had (from 2010) with the goldcard file (thank you gmail).
but nothing seems to help.
I read a lot of forum posts and tried many things over these 3 days but i'm willing to start over, step by step, with anyone willing to assist.
Hopefully this step by step will assist me and will be a reference guide for others.
Guy
guyvago said:
Hi,
Well, i got myself into this mess and after 3 days of trying to fix it, i give up and call for your assistance.
I had a working S-ON HBOOT 0.47 rooted Legend running CM7.2 and recently changed to Jelly_Bean_Extras_HomICS_2.0_Venus.
I liked the new rom but link2sd didn't work.
My guess was that i need to have it S-OFF.
So... i headed to HTCDEV but first i needed to be on one of the listed RUU.
My original RUU was RUU_Legend_HTC_ISR_2.05.461.52_Radio_47.39.35.09_7.08.35.21_release_140015_signed.zip
I used the LEGEIMG.zip method to flash the RUU and then i flashed the one from HTCDEV which holds "hboot_legend_7227_1.02.0000_111223.nb0" only.
Now the HBOOT got to be 1.02.0000
After flashing this, i got stuck.
No recovery - i get signature failed message - even after putting CWM update.zip on the SD.
No ADB - at all states, only fastboot sees the device.
RUU update gets fails either due to version 3.30.0000, signature or device.
fastboot flash - i thought i will manually flash the various parts. i get FAILED (remote: signature verify fail).
CID was HTC__K18
did a new goldcard based on the old mail i had (from 2010) with the goldcard file (thank you gmail).
but nothing seems to help.
I read a lot of forum posts and tried many things over these 3 days but i'm willing to start over, step by step, with anyone willing to assist.
Hopefully this step by step will assist me and will be a reference guide for others.
Guy
Click to expand...
Click to collapse
Have actually flashed hboot 1.02 yet?
Have followed ALL the instructions at htcdev?
Have you followed all the instructions sent to you via email about how to unlock the locked hboot 1.02, the email also includes a unlock.bin attached to the email which you need in order to unlock your boot loader?
If you had read ANY of the other question thread about this subject (there are a few) you would have found out that after you unlock your boot loader with hboot 1.02 you can no longer use update.zip cwm recovery, you can only use the S-OFF recovery method...
Sent from my Legend using xda app-developers app
I was expecting feeling stupid, missing something simple.
Originally, I couldn't get to step 8 since it requires that the unit didn't respond to fastboot command and while trying to find a fix, i got stuck with only fastboot and didn't remember that this was the step i was stuck in.
Anyway, your response had me go back to htcdev just to prove my point and i found that i can continue.
Finally.
Now i am unlocked and can continue with S-OFF methods.
Thank you.
Guy
Currently the phone starts with:
*** LOCKED (OOW) ***
LEGEND PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0816
TOUCH PANEL-SYN07_0103
RADIO-7.08.35.21
Dec 23 2011, 16:36:48
Guy
Have actually flashed hboot 1.02 yet?
Have followed ALL the instructions at htcdev?
Have you followed all the instructions sent to you via email about how to unlock the locked hboot 1.02, the email also includes a unlock.bin attached to the email which you need in order to unlock your boot loader?
If you had read ANY of the other question thread about this subject (there are a few) you would have found out that after you unlock your boot loader with hboot 1.02 you can no longer use update.zip cwm recovery, you can only use the S-OFF recovery method...
Click to expand...
Click to collapse
Guess what, your phone is still locked, you typed it yourself, you still need to unlock it using the bin file sent to you in the email.
Don't feel stupid mate, this rooting thing can be confusing and fearsome at times. Even I had that "can't use update.zip" issue and thought my phone was f'ed till I realised I needed to flash the recovery image.
Sent from my Legend using xda app-developers app
ok.
now everything is ok.
flashed cwm.
got the rom back
and restored almost everything.
thank you
just to point out
Jelly_Bean_Extras_HomICS_2.0_Venus is not ROM
If you flashed a good ROM and your stuck in hboot, use fastboot and use the following command 'fastboot oem boot' that should force your phone to boot.

HELP! Can't find Stock VM RUU!

Hey, I'm going to make this short because I'm freaking out right now like the noob I am.
I was going through Closeone's downgrade S-OFF/Downgrade Bootloader tutorial and and relocked my phone. OK. I AM ON STOCK, I MADE A BACKUP AS SOON AS I UNLOCKED USING HTC DEV. That's what I restored before I relocked. But I'm still getting a security warning.
THE PROBLEM:
I cannot find the stock RUU for the Evo V 4G anywhere. I've checked here, VMROMs and Phandroid, nothing. They all lead to the same goo.manager link that says the file cannot be found.
PLEASE help, I'm stuck in bootloader and don't know what to do.
Thank you for your time...
OFFICIALLY FIXED... SORT OF
So I relocked using HTC Dev and from there attempted a reboot. It boots!.. up to the end of the animation, from there it stops. So unfortunate. Any ideas?
I cannot get to bootloader by any normal means (via commands or volume rockers).
SOLVED
With some help from LeslieAnn and a couple of other people over at VMroms.com I was able to boot again.
http://www.vmroms.com/index.php?topic=370.0
Will try the wire trick tomorrow.

Process to fix

I've been restraining myself from posting this for a few days, while browsing and looking through threads trying to figure out my answers. Something is wrong within my device, something is corrupted. Phone keeps rebooting on phone calls, and my UI is trashed, its all zoomed out and looking crazy. Flashing different ROMs has not helped. I have taken under advisement to RUU. However, I just want to make sure there is nothing I need to do before RUU'ing to keep from screwing up the device. Here is my current status: the only things I have done to this device since I got it last may are root and unlock using moonshine. So I have had no OTAs that I know of. This is the RUU I have:
RUU_DLX_WL_JB_50_S_VERIZON_WWE_3.06.605.4_Radio_1.01.01.1112_NV_VZW_4.46_002_release_340974_signed_2
I just want to make sure I only need to run that, and don't need to flash anything else (such as hboot, etc)
Thanks.
UPDATE: I tried running the RUU. I got Error 158. I was watching, and I had the phone in fastboot already, and when the screen said Rebooting Bootloader, then Waiting for Bootloader..... I never saw the phone actually boot to bootloader again, it just stayed black. then the program kept running like the phone was responding, and eventually shot out Error 158. should I follow this method http://forum.xda-developers.com/showthread.php?t=2293919 and relock the bootloader and then RUU? and does anyone know if I will be able to unlock again after I do this?
UPDATE: This is my main question if anyone can help. I have the above RUU, and I got error 158. Since I used moonshine's method, I am under the impression I need to re-lock bootloader, and THEN RUU. However, can someone please tell me if I need a different hboot version or if I'm just fine to go ahead like this? my hboot is below. I ask this because last failed RUU, i had to re-install the ROM im using to boot the phone, and if I re-lock I dont want to be in a position where the RUU fails and I can't get into recovery to re-flash a ROM.
BTW : My hboot version is 1.33.4444
lemonoid said:
UPDATE: I tried running the RUU. I got Error 158. I was watching, and I had the phone in fastboot already, and when the screen said Rebooting Bootloader, then Waiting for Bootloader..... I never saw the phone actually boot to bootloader again, it just stayed black. then the program kept running like the phone was responding, and eventually shot out Error 158. should I follow this method http://forum.xda-developers.com/showthread.php?t=2293919 and relock the bootloader and then RUU? and does anyone know if I will be able to unlock again after I do this?
UPDATE: This is my main question if anyone can help. I have the above RUU, and I got error 158. Since I used moonshine's method, I am under the impression I need to re-lock bootloader, and THEN RUU. However, can someone please tell me if I need a different hboot version or if I'm just fine to go ahead like this? my hboot is below. I ask this because last failed RUU, i had to re-install the ROM im using to boot the phone, and if I re-lock I dont want to be in a position where the RUU fails and I can't get into recovery to re-flash a ROM.
BTW : My hboot version is 1.33.4444
Click to expand...
Click to collapse
Manually boot the phone to the bootloader before you start and it will go. For whatever reason it doesn't do it itself so manually doing it will give you success.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
lemonoid said:
UPDATE: I tried running the RUU. I got Error 158. I was watching, and I had the phone in fastboot already, and when the screen said Rebooting Bootloader, then Waiting for Bootloader..... I never saw the phone actually boot to bootloader again, it just stayed black. then the program kept running like the phone was responding, and eventually shot out Error 158. should I follow this method http://forum.xda-developers.com/showthread.php?t=2293919 and relock the bootloader and then RUU? and does anyone know if I will be able to unlock again after I do this?
UPDATE: This is my main question if anyone can help. I have the above RUU, and I got error 158. Since I used moonshine's method, I am under the impression I need to re-lock bootloader, and THEN RUU. However, can someone please tell me if I need a different hboot version or if I'm just fine to go ahead like this? my hboot is below. I ask this because last failed RUU, i had to re-install the ROM im using to boot the phone, and if I re-lock I dont want to be in a position where the RUU fails and I can't get into recovery to re-flash a ROM.
BTW : My hboot version is 1.33.4444
Click to expand...
Click to collapse
error 158= wrong Hboot ; Solution *You need to Update Hboot to 1.54 in order to Run RUU 3.06
http://forum.xda-developers.com/showpost.php?p=42352912&postcount=4
Jaggar345 said:
Manually boot the phone to the bootloader before you start and it will go. For whatever reason it doesn't do it itself so manually doing it will give you success.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I started the RUU with the phone in fastboot. I'm going to try to upgrade to 1.54 then RUU

[Q] How do I unlock my htc glacier with hboot 0.89.0006

Pls I've been unable unlock the bootloader of my htc glacier
I've tried htcdev but the ruu update is telling to get a utility software for my device.
I've also tried htc bootloader unlocker (one click unlock) but its not finding my device
GLACIER PVT SHIP S-OFF
HBOOT-0.89.0006
MICROP-0429
RADIO-26.13.04.19_M
eMMC-boot
Jul 15 2011, 16:45:17
Pls I'll be so glad if I can find some help.
You're already S-Off, why are you trying to unlock via htcdev.com?? To unlock via htcdev.com (which is not a complete unlock, unlike S-Off) then you have to be on the newest bootloader version. HBOOT-0.89.0007. I thought there was actually a link to the little RUU update that is just for the bootloader on the bottom of the walkthrough @ htcdev? It's been awhile since I played with one, but I'm sure it was there. If not, I can upload it. I am sure it's hanging around somewhere. But yea, unless you relocked it and stayed S-Off, all the htcdev stuff would not be needed.
Exactly as stated above
If there is an engineering bootloader for your phone you should get that as well, if I'm not mistaken the proper way of rooting your device is to exploit it with gfree, similar to the vision a phone I used for a long time, all info should be in the xda wiki to see if greed was used to exploit and how to flash the eng hboot
Sent from my Nexus 7 using XDA Premium 4 mobile app
So pls how do I update to the latest hboot 0.89.0007
So pls how do I update to the latest hboot 0.89.0007 or how else can I unlock the bootloader and root?
What do you mean? It's the very beginning of the steps on how to unlock @ htcdev.com (and the RUU is there, just like I mentioned earlier). Are you certain that you need to do this? It seems like you have not done much research and might be getting yourself into more work than is needed.
so pls can I flash custom rom just with my s-off
Yes, you just need a custom recovery such as twrp, cwm, 4ext
But what you should do is go to the xda wiki or cyanogen wiki and follow the steps for rooting, these guides will give you true radio s-off, an engineering bootloader and a custom recovery so you can easily flash ROMs and easily fix your phone if issues come about
To answer you directly, yes you should be able to flash custom ROMs as is, but having to ask that questions makes me think you should read more about your device or the next thread you make will probably ask for help fixing a brick
Sent from my Nexus 7 using XDA Premium 4 mobile app
If you need help still, let me know. I just did 2 of my glaciers
Sent from my awesome ass HTC MyTouch 4G

Categories

Resources