Database Develop

RUU.exe Error 155

So I've asked this question before and I remember people telling me an RUU is capable of removing an HBoot and installing a new one under the conditions that the CID and MID are matching the RUU. My phone is S-On and my HBoot is GPE, but my CID and MID are T-Mobile and I want to return back to stock T-Mobile Sense 5. The new RUU has an HBoot higher than my 1.54 GPE HBoot so it should work... I haven't unlocked my phone through the HTCDev site, if that matters; I unlocked it through adb commands on GPE but I've tried relocking it via adb commands and I still get the error when I run the .exe file... My device is not recognized on HTC Sync Manager and there is no status bar on the "fastboot oem rebootRUU" menu like the instructions says there will... I tried flashing GPE recovery and even Sense 5 recovery; neither worked... I'm on ARHD 3.06.1700.10 ROM because I can't seem to flash stock ROM due to S-On... I'm starting to think that I get the error because of the GPE HBoot and S-On... Am I just screwed? Is it not possible to run an RUU if you have a different HBoot and S-On at the same time? Is it an issue with my drivers? Or is it because I haven't unlocked my device on the HTCDev site?

I'm sure it's due to you not having unlocked the phone
Vomers guide is very helpful
http://forum.xda-developers.com/showthread.php?t=2365506&page=4

Check this thread

Guich said:
Check this thread
Click to expand...
Click to collapse
Sorry about the late reply; since my phone is so messed up, I was trying to fix it with another route by doing Rumrunner S-Off first, but that isn't working out so well... So I'm back here trying to get past this error. The file in that thread cannot be used with my CID due to the .txt file inside the .zip file, and whenever I try to edit it with Notepad++ (the program that supposedly doesn't corrupt .txt files), it always corrupts the .txt file. Is it possible you or anyone (pretty please) could edit the .txt file inside the .zip file to have "T-MOB010" and send it to me somehow?
Edit: The download link is http://d-h.st/qfc by the way.

[Q] RUU update: stuck @ 5% checking headers

HTC One
Tamperd
Relocked
2.24.401.8
S-ON
Cidnum HTC_Y13
Hboot: 1.54.0
I'm using this RUU:
RUU M7 UL K44 SENSE55 MR HTC Europe 4.19.401.9 R Radio 4A.23.3263.28 10.38r.1157.04L Release 353069 Signed 2-1
I double checked my fastboot connection, every thing seems to be working just fine.
Everytime i try to run it it get stuck at checking headers (5%)
what am i doing wrong ?

I think there is something wrong with that ruu. I have not been able to run the 4.x RUU

SaHiLzZ said:
I think there is something wrong with that ruu. I have not been able to run the 4.x RUU
Click to expand...
Click to collapse
Any other RUU suggested ?, i'm currently stuck with the bootloader, can i even normally boot up the device with the current ROM ?

SaHiLzZ said:
I think there is something wrong with that ruu. I have not been able to run the 4.x RUU
Click to expand...
Click to collapse
S7atem said:
what do you suggest i should do ?, i'm currently stuck with the bootloader, can i even normally boot up the device with the current ROM ?
Click to expand...
Click to collapse
It does actually work, just seems very sensitive to OS, USB ports, drivers, (possibly even locale), etc.
Recommend you use a plain vanilla Win7 PC with USB2 port.

Try extract Rom.zip & flash with fastboot
from HTC One

yatindroid said:
Try extract Rom.zip & flash with fastboot
from HTC One
Click to expand...
Click to collapse
where can i find the .ZIP of this ROM ?

S7atem said:
where can i find the .ZIP of this ROM ?
Click to expand...
Click to collapse
you can extract it from current ruu exe
Follow thread http://forum.xda-developers.com/showthread.php?t=2497614
from HTC One

I had this exact problem trying to go back from 5.11.401.10. When i extracted the rom.zip, fastboot came back with remote: 02 data length is too large.
I had already unlocked with HTCDev, flashed TWRP and s-off. i just wanted a stock ruu to go back to sense 5.5. In the end, i found TeHashX has created a twrp flash here: Link I flashed that without root, with radio and recovery and I'm back to stock. You'll probably need to be s-off for this but I'm not sure. I kept s-off and the unlocked bootloader.
Ps. You can remove the tampered with a rooted rom in the process.
Craig

craiglay said:
I had this exact problem trying to go back from 5.11.401.10. When i extracted the rom.zip, fastboot came back with remote: 02 data length is too large.
I had already unlocked with HTCDev, flashed TWRP and s-off. i just wanted a stock ruu to go back to sense 5.5. In the end, i found TeHashX has created a twrp flash here: Link I flashed that without root, with radio and recovery and I'm back to stock. You'll probably need to be s-off for this but I'm not sure. I kept s-off and the unlocked bootloader.
Ps. You can remove the tampered with a rooted rom in the process.
Craig
Click to expand...
Click to collapse
I have also been unable to use any of the 4.xx RUU... They worked once but none of them work now. Anyway I just wanted to say I also created a Guru Reset for the 5.21.502.2 (AT&T) here >> http://www.androidfilehost.com/?fid=23501681358545274 to go along with the files posted by @TeHashX

The only thing i can think of was the hboot prevents it now but i wasnt going to play with that. I personally went to 4.xx to get away from sense 6

Is there any other maybe older stock ROM i can try ?

I tried 1.29.401.x and that failed too. There was a note with the download saying you need to flash hboot 1.44 which i didn't bother with.

[Q] Can I downgrade 6.06 to 1.29 with S-OFF

Hi all, I was just wondering if I should run the RUU ZIP or EXE if I am on S-OFF.
I currently have the 6.06.401.1 firmware along with the stock 6.06.401.1 rom. I need to return to the stock 1.29.707.1 for my HTC__044 before taking the latest OTA to Android Lollipop.
So far, I have used my S-OFF to change my bootloader to *LOCKED* and flashed stock recovery and stock rom for the 6.06.401.1.
I currently have both the 1.29.707.1 RUU EXE and ZIP. Which one should I use? I read that I need to have the 1.44 Hboot but I currently have the 1.54 Hboot.
Halp?

uhm, what? this is nonsense , the lastest available RUU is "4.19.401.9" which must be flashed under hboot 1.56 ... there is no need to go to initial release of android 4.1!
WARNING!!! YOU MUST FLASH HBOOT 1.56 BEFORE APPLYING 4.19.401.9 RUU
RUU: http://d-h.st/KmT
+There is no need to LOCK your bootloader to get an OTA update... Mine is always unlocked and never had a problem with OTA's
+RUU's work only under S-OFF

Androidian10 said:
Hi all, I was just wondering if I should run the RUU ZIP or EXE if I am on S-OFF.
I currently have the 6.06.401.1 firmware along with the stock 6.06.401.1 rom. I need to return to the stock 1.29.707.1 for my HTC__044 before taking the latest OTA to Android Lollipop.
So far, I have used my S-OFF to change my bootloader to *LOCKED* and flashed stock recovery and stock rom for the 6.06.401.1.
I currently have both the 4.20.707.1 RUU EXE and ZIP. Which one should I use? I read that I need to have the 1.44 Hboot but I currently have the 1.54 Hboot.
Halp?
Click to expand...
Click to collapse
you can use the RUU you have fine 4.20.707.1, you'll just have to make sure your cid and mid match first, and also just flash the 4.20.707.1 firmware first, this will put you on the correct HBOOT and system files for the RUU, no need to lock your bootloader with s-off.
or you can skip all of that and just flash the 7.19.401.2 RUU right now as your phone is as your already on the 6.xx.401.x firmware.
you don't really have any reason to back flash.

Seanie280672 said:
you can use the RUU you have fine 4.20.707.1, you'll just have to make sure your cid and mid match first, and also just flash the 4.20.707.1 firmware first, this will put you on the correct HBOOT and system files for the RUU, no need to lock your bootloader with s-off.
or you can skip all of that and just flash the 7.19.401.2 RUU right now as your phone is as your already on the 6.xx.401.x firmware.
you don't really have any reason to back flash.
Click to expand...
Click to collapse
But I can't seem to find a 4.20.707.1 RUU. I only have the 1.29.707.3 firmware. I need a region specific one because I need to trade my phone in.
Could you point me in the direction of a 4.20.707.1 RUU zip?
Also, is it safe to OTA update if I flash back to 1.29 with S-OFF?
Edit: Crap I made a typo in my OP, I mean that I have the 1.29 RUU EXE and ZIP right now.

Androidian10 said:
But I can't seem to find a 4.20.707.1 RUU. I only have the 1.29.707.3 firmware. I need a region specific one because I need to trade my phone in.
Edit: Crap I made a typo in my OP, I mean that I have the 1.29 RUU EXE and ZIP right now.
Could you point me in the direction of a 4.20.707.1 RUU zip?
Also, is it safe to OTA update if I flash back to 1.29 with S-OFF?
Click to expand...
Click to collapse
I thought you said you had the 4.20.707.1 RUU
if not then you'll have to use the 1.29.707 one that you have, you'll just have to flash the 1.44 hboot first or the firmware that matches the RUU.

Seanie280672 said:
I thought you said you had the 4.20.707.1 RUU
if not then you'll have to use the 1.29.707 one that you have, you'll just have to flash the 1.44 hboot first or the firmware that matches the RUU.
Click to expand...
Click to collapse
Yeah I had a typo.
So yeah, I have both the EXE and ZIP RUU.
I'm thinking that the ZIP RUU has the 1.44 hboot no?
Also, most importantly, can I take official OTA updates while I am S-OFFed?

Androidian10 said:
Yeah I had a typo.
So yeah, I have both the EXE and ZIP RUU.
I'm thinking that the ZIP RUU has the 1.44 hboot no?
Also, most importantly, can I take official OTA updates while I am S-OFFed?
Click to expand...
Click to collapse
yes you can take OTA's whilst s-off, do not go s-on at any point.
I would also say try the RUU.zip first.

Seanie280672 said:
yes you can take OTA's whilst s-off, do not go s-on at any point.
I would also say try the RUU.zip first.
Click to expand...
Click to collapse
Righto. Will report back again.
I hope the guy at the store doesn't go into the bootloader when I trade my m7 in. Even then I already set the flag to locked so I think he'll miss that S-OFF portion.

Androidian10 said:
Righto. Will report back again.
I hope the guy at the store doesn't go into the bootloader when I trade my m7 in. Even then I already set the flag to locked so I think he'll miss that S-OFF portion.
Click to expand...
Click to collapse
cid and mid need to match the ruu your flashing first.

Seanie280672 said:
cid and mid need to match the ruu your flashing first.
Click to expand...
Click to collapse
Already checked with fastboot getvar all.

Seanie280672 said:
cid and mid need to match the ruu your flashing first.
Click to expand...
Click to collapse
Actually, problem. :/
I have a matching CID which is HTC__044 but the modelid is PN0714000.
The RUU's android-info has a matching CID of HTC__044 but a modelid of PN0711000.
What now?

Androidian10 said:
Actually, problem. :/
I have a matching CID which is HTC__044 but the modelid is PN0714000.
The RUU's android-info has a matching CID of HTC__044 but a modelid of PN0711000.
What now?
Click to expand...
Click to collapse
unlock your bootloader, flash twrp recovery and change your mid, are you sure your using the RUU for the M7_UL as that looks a lot like the M7_U mid too me, can you give me a link for the RUU's you downloaded please.
---------- Post added at 11:05 AM ---------- Previous post was at 10:57 AM ----------
here you go, do this instead, this is going to be a bit backwards and forwards.
Unlock your bootloader, and flash TWRP recovery, then use the mid change tool to change your mid to the correct one.
https://www.androidfilehost.com/?fid=23622183712469376
next copy this guru reset file to your internal storage and flash it, select no to stock radio and no to stock recovery: http://www.htc1guru.com/2013/11/guru-reset-3-63-707-4-stock-rom/
now lock your bootloader
and finally flash the matching firmwqare from here: http://d-h.st/BWu this will put stock recovery and stock radio on your phone.

Seanie280672 said:
unlock your bootloader, flash twrp recovery and change your mid, are you sure your using the RUU for the M7_UL as that looks a lot like the M7_U mid too me, can you give me a link for the RUU's you downloaded please.
Click to expand...
Click to collapse
I actually ran the RUU. It's now stuck on waiting for device after the usual flush after 90 hboot pre-update.
I changed the modelid in the android-info.txt since it was decrypted.

Anyone help me?
My computer can't see the device anymore after flashing the hboot!

Androidian10 said:
Anyone help me?
My computer can't see the device anymore after flashing the hboot!
Click to expand...
Click to collapse
if your using windows 8 or higher then that's the problem, HBOOT 1.44 doesn't work with it, there is a fix around here somewhere by @clsA but ive never had to use it myself.
trouble with changing the android-info text file is all of the OTA's will fail due to you having the wrong mid on your phone, you'll have to change your phones mid as soon as possible.

Seanie280672 said:
if your using windows 8 or higher then that's the problem, HBOOT 1.44 doesn't work with it, there is a fix around here somewhere by @clsA but ive never had to use it myself.
trouble with changing the android-info text file is all of the OTA's will fail due to you having the wrong mid on your phone, you'll have to change your phones mid as soon as possible.
Click to expand...
Click to collapse
Ok, I have changed to an old Windows 7 laptop and tried doing the fastboot flash zip again. After I press enter, nothing happens at all. Not a single code at all. Just a blinker.
Edit: Started moving again. Phew. I almost had a heart attack.
So now do I do the fastboot writemid command?

Androidian10 said:
Ok, I have changed to an old Windows 7 laptop and tried doing the fastboot flash zip again. After I press enter, nothing happens at all. Not a single code at all. Just a blinker.
Edit: Started moving again. Phew. I almost had a heart attack.
So now do I do the fastboot writemid command?
Click to expand...
Click to collapse
to change the mid you need to use the mid change tool I posted a link to it earlier, install it inside twrp recovery then select the mid you require from the list it gives you.

Seanie280672 said:
to change the mid you need to use the mid change tool I posted a link to it earlier, install it inside twrp recovery then select the mid you require from the list it gives you.
Click to expand...
Click to collapse
It's okay now. I found a matching mid RUU for my phone.
But my question now is should I go S-ON to remove the red "This is a test device. Accordingly, to collect critical information about the device, Tell HTC is enabled and cannot be turned off regardless of device settings" warning? Or just leave it S-OFF and hope that the techies at the store doesn't notice it?

More questions
I have done all the OTAs now so should I do the fastboot oem writesecureflag 3 as the final step before putting the phone aside to trade it in?

Androidian10 said:
More questions
I have done all the OTAs now so should I do the fastboot oem writesecureflag 3 as the final step before putting the phone aside to trade it in?
Click to expand...
Click to collapse
no, leave it s-off, if you turn it back s-on now you will get the tampered flag back.

Need RUU for version 4.20.707.6 and above

Hi guys,
I have soft bricked my device and currently the only way I see out of this is to flash RUU but then my version is way too high than the RUU available on the internet I've gone through. My current version is 4.20.707.7 but so far I've only found 1.29.707.3 the highest RUU version available on the internet.I have SuperCID but device is currently relocked and S-ON. I tried flashing other region's RUU which has higher version than mine believing the fact that I can flash it because I have SuperCID but I failed and received an error 155 which I searched and it means I'm using the wrong RUU. So I guess I can't flash other region's RUU and have to stick with my current region's.
Question:
1) Is it possible to flash the same version of RUU with the device?
2) Is it possible to flash other region's RUU if I have S-OFF? If yes, I only have access to fastboot and recovery and as far as I know, you only can S-OFF with a working homescreen, so how do I S-OFF while I only have access to fastboot and recovery?
If yes, does anyone have RUU for version 4.20.707.7 ( my current version ) or above?
If no, does anyone have RUU for version above 4.20.707.7?
Please help. Replies are much appreciated. Thank you And sorry for the tiny misleading information on the title. My current version is 4.20.707.7 not 4.20.707.6.

chaun1308 said:
Hi guys,
I have soft bricked my device and currently the only way I see out of this is to flash RUU but then my version is way too high than the RUU available on the internet I've gone through. My current version is 4.20.707.7 but so far I've only found 1.29.707.3 the highest RUU version available on the internet.I have SuperCID but device is currently relocked and S-ON. I tried flashing other region's RUU which has higher version than mine believing the fact that I can flash it because I have SuperCID but I failed and received an error 155 which I searched and it means I'm using the wrong RUU. So I guess I can't flash other region's RUU and have to stick with my current region's.
Question:
1) Is it possible to flash the same version of RUU with the device?
2) Is it possible to flash other region's RUU if I have S-OFF? If yes, I only have access to fastboot and recovery and as far as I know, you only can S-OFF with a working homescreen, so how do I S-OFF while I only have access to fastboot and recovery?
Click to expand...
Click to collapse
Yes, with s-on you can flash same or newer ruu version to your phone as long that it match your MID/CID + Firmware base (x.xx.707.x)
Yes you can flash other region RUU if s-off. You might need to change your CID and MID which can be done from fastboot (CID) and from recovery (MID). You can flash a close to stock rom like arhd to achieve s-off.
If yes, does anyone have RUU for version 4.20.707.7 ( my current version ) or above?
If no, does anyone have RUU for version above 4.20.707.7?
Click to expand...
Click to collapse
Many option for you.
You can restore the 4.20.707.7 version using the 4.20.707.7 stock reset rom (to be flashed in custom recovery)
You can flash the 7.21.707.5 ruu but in order to do that, your phone firmware must be at least 6.xx.707.x or 7.xx.707.x so it will requires to flash one of these firmware before the ruu.
Honestly I would simply flash the 4.20.707.7 reset rom, simple to do. When installing the rom, select "yes" to stock recovery and radio. Select "no" for root. when flashed, take all ota updates until you are on latest (7.21.707.5). From there you can flash a custom recovery and root if you want and returning back to stock from this point (if something else happen) will be as simple as flashing the 7.21.707.5 ruu.

alray said:
Yes, with s-on you can flash same or newer ruu version to your phone as long that it match your MID/CID + Firmware base (x.xx.707.x)
Yes you can flash other region RUU if s-off. You might need to change your CID and MID which can be done from fastboot (CID) and from recovery (MID). You can flash a close to stock rom like arhd to achieve s-off.
Many option for you.
You can restore the 4.20.707.7 version using the 4.20.707.7 stock reset rom (to be flashed in custom recovery)
You can flash the 7.21.707.5 ruu but in order to do that, your phone firmware must be at least 6.xx.707.x or 7.xx.707.x so it will requires to flash one of these firmware before the ruu.
Honestly I would simply flash the 4.20.707.7 reset rom, simple to do. When installing the rom, select "yes" to stock recovery and radio. Select "no" for root. when flashed, take all ota updates until you are on latest (7.21.707.5). From there you can flash a custom recovery and root if you want and returning back to stock from this point (if something else happen) will be as simple as flashing the 7.21.707.5 ruu.
Click to expand...
Click to collapse
@alray
Hey man, thanks for the useful information. I flashed the 4.20.707.7 reset ROM and did what you have told me but then the problem in the end is still the same as flashing other ROMs ( custom and stock ). The problem will be after unlocking the screen, green HTC logo appears and stays there for quite some time while dialer keeps crashing from time to time, and after few minutes, reboots by itself. This cycle will go on forever. Any advice ? Thanks again bro.

chaun1308 said:
@alray
Hey man, thanks for the useful information. I flashed the 4.20.707.7 reset ROM and did what you have told me but then the problem in the end is still the same as flashing other ROMs ( custom and stock ). The problem will be after unlocking the screen, green HTC logo appears and stays there for quite some time while dialer keeps crashing from time to time, and after few minutes, reboots by itself. This cycle will go on forever. Any advice ? Thanks again bro.
Click to expand...
Click to collapse
Looks like an hardware problem. Is your phone still having an IMEI # when doing "fastboot getvar all" ?

[Q] M7_U TW won't revert to stock

Hi there. I've got a taiwanese M7_U on my hands. Someone before me tried to flash custom ROM and failed dramatically. It's unlocked, has TWRP, but has no ROM flashed. I tried to reinstall stock ROM, but it fails as well: any Sense-based zip ROM goes into bootloop. I tried latest Android Revolution, ViperOne and stock zip repacks. I was able to capture logcat of ViperOne but couldn't find any obvious reasons of bootloops, so it is attached. Only ROM I got to boot on this device at least was CM12.1 nightly build. The worst - i can't install RUU for some reason, even after bootloader relock and flashing stock recovery. I suspect that the trouble is because of incompatible MID (PN0711000) and CID (HTC__621) for most RUU packages. The only compatible RUU build I was able to find is obviously outdated (1.20.709.101 vs current mainver of 7.18.709.102). I can't get S-OFF because HBOOT is already updated to 1.61.
I guess that if I want to get a stock-ish ROM running on that device my options are:
1. Figuring out why ViperOne and AndroidRevolution are bootloopin' (again, logcat attached)
2. Getting latest RUU for MID = PN0711000 and CID = HTC__621
3. Managing to get S-OFF for HBOOT 1.61, changing MID and CID and flashing common M7_UL RUU
4. Patching common M7_UL RUU to bypass MID/CID check.
I would appreciate any help in getting any of these options to work. I might've missed some importand guides, but quick search didn't help much, any help with finding guides or compatible RUUs would be appreciated as well.

k3lwin said:
Hi there. I've got a taiwanese M7_U on my hands. Someone before me tried to flash custom ROM and failed dramatically. It's unlocked, has TWRP, but has no ROM flashed. I tried to reinstall stock ROM, but it fails as well: any Sense-based zip ROM goes into bootloop. I tried latest Android Revolution, ViperOne and stock zip repacks. I was able to capture logcat of ViperOne but couldn't find any obvious reasons of bootloops, so it is attached. Only ROM I got to boot on this device at least was CM12.1 nightly build. The worst - i can't install RUU for some reason, even after bootloader relock and flashing stock recovery. I suspect that the trouble is because of incompatible MID (PN0711000) and CID (HTC__621) for most RUU packages. The only compatible RUU build I was able to find is obviously outdated (1.20.709.101 vs current mainver of 7.18.709.102). I can't get S-OFF because HBOOT is already updated to 1.61.
I guess that if I want to get a stock-ish ROM running on that device my options are:
1. Figuring out why ViperOne and AndroidRevolution are bootloopin' (again, logcat attached)
2. Getting latest RUU for MID = PN0711000 and CID = HTC__621
3. Managing to get S-OFF for HBOOT 1.61, changing MID and CID and flashing common M7_UL RUU
4. Patching common M7_UL RUU to bypass MID/CID check.
I would appreciate any help in getting any of these options to work. I might've missed some importand guides, but quick search didn't help much, any help with finding guides or compatible RUUs would be appreciated as well.
Click to expand...
Click to collapse
What is your custom recovery version?
7.18.709.120 ruu here: http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/M7_U/
Requires s-off
Won't work. You can only flash signed ruu on a s-on phone. Any alteration of the ruu will prevent it to be flashed.

alray said:
What is your custom recovery version?
7.18.709.120 ruu here:
Requires s-off
Won't work. You can only flash signed ruu on a s-on phone. Any alteration of the ruu will prevent it to be flashed.
Click to expand...
Click to collapse
1. Tried flashing Viper and ARHD with both TWRP 2.8.6.0 and CWM Touch 6.0.4.8, no luck.
2. I've got 7.18.709.102 and 7.21.707.105 RUU zips, installation via fastboot of both fails with error (remote: 02 data length is too large).
I think that exe RUU of 7.18.709.102 might work, but I can't find it anywhere. Any suggestions?

k3lwin said:
1. Tried flashing Viper and ARHD with both TWRP 2.8.6.0 and CWM Touch 6.0.4.8, no luck.
2. I've got 7.18.709.102 and 7.21.707.105 RUU zips, installation via fastboot of both fails with error (remote: 02 data length is too large).
I think that exe RUU of 7.18.709.102 might work, but I can't find it anywhere. Any suggestions?
Click to expand...
Click to collapse
Try with twrp 2.6.3.3
you need to use htc_fastboot.exe not the regular (google) fastboot.

alray said:
Try with twrp 2.6.3.3
you need to use htc_fastboot.exe not the regular (google) fastboot.
Click to expand...
Click to collapse
With TWRP 2.6.3.3 I still got bootloop after flashing ARHD, but flashing RUU with htc_fastboot finally got this device working. Thanks a lot!