RUU.exe Error 155 - One (M7) Q&A, Help & Troubleshooting

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.

Related

Will a RUU return me to S-ON?

I used alpharevX to S-OFF my Incredible S... I flashed cyanogenmod on it, but it can't send receive MMS without data being on, so I want to flash on the gingerbread RUU. My question is... will it bring my phone back to S-ON? I would like to keep S-OFF for rooting.
Sent from my Incredible S using XDA App
Flashing RUU will return S-ON.
I've S-OFF my phone with alpharevx and then flashed official GB RUU - phone was S-ON again.
However its not a big deal since you can use alpharevx trick again - phone will be S-OFF again (worked for me)
But alpharevx will work on all?
Works on most. If it doesn't move to a RUU which it does work on like the Optus/Virgin AU RUU ROMs.
just open ruu installer
run %TEMP%
grab the rom.zip
copy it somewhere
remove hboot out of the zipfile and the hboot line in the txt file (last line)
save it up (repack it)
name it PG32IMG.zip
put it on your sdcard
flash into hboot
tada miracles happen....
(note, might need an goldcard with this as well...)
Alright thank you for your help. I will try your method on the Optus RUU... I made a goldcard the day I bought this phone waiting for this day.
Sent from my Incredible S using XDA App
Ok, so I downloaded the the RUU and extracted it... But when I try to install it using the method sticked in this section I get an error saying: "Model ID incorrect". I have a Bell(Canada) IS and saw that someone else is having the same issue flashing a radio... Do I have to install ENG HBOOT to continue? Or is that only possible for factory S-OFF users?
All help is appreciated.
Did you make a goldcard correctly? some sdcards won't be a goldcard. you can try on other sdcard.
in some case, downgrading radio causes error. so try to remove radio_signed.img from your
PG32IMG.zip. (IMO, only boot_signed.img (not hboot) and system.img are needed)
modelid (PG32*****) is displayed in fastboot screen.
if it is not same as modelid line in android-info.txt, you can change that line.
for example, if modelid line in txt is "PG3213000" and fastboot screen displays "PG3212***" or
"PG3212000", change the modelid line "PG3213000" to "PG3212000".

[Q] Telstra 3.44 RUU

I know that many people have had problems with 3.44 ruu not being available. I want to go back to the stock rom using the ruu but i can't seem to find it and when i try to use the latest available ruu it comes with a error bootlaoder version. Could someone please help me.
HTCdev
select 'vivid' and 'telstra' than 'find files' .
I think the first one is the one you are searching for, it says 3.44.841.3 in description.
Thats a kernel source file not the ruu
No RUU exists for 3.44. AFAIK, it was a kernel patch for a minor issue. Just flash the normal Telstra RUU, and try to OTA to 3.44.
You get error 140 when you use a earleir ruu
WildfireDEV said:
You get error 140 when you use a earleir ruu
Click to expand...
Click to collapse
Two things:
Make sure your bootloader is relocked.
Extract the rom.zip from the RUU (C:\Users\[YOU]\AppData\Local\Temp\{garbage numbers}), rename to PH39IMG.zip, paste on external SD's root, and reboot to bootloader. Accept update. Should not throw errors; I've used this method to downgrade countless times.

[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] Cannot flash back to stock ROM?

So I accidentally deleted my os, rom, everything and for the past day or so I have been trying to go back to stock and I simply can't. I downloaded both an RUU.zip and exe and made sure the android-info.txt file had the same modelid and cidnum but it still fails. I will post images below of where my problem arises. I have s-off unlocked bootloader and was able to go from 1.56 hboot back to the 1.44 hboot no problem. In the second image I tried using an RUU, stock odexed rom, and then a firmware update but all failed . The errors occur when checking the info parsing or model id.
xXgOrAiZeXx said:
So I accidentally deleted my os, rom, everything and for the past day or so I have been trying to go back to stock and I simply can't. I downloaded both an RUU.zip and exe and made sure the android-info.txt file had the same modelid and cidnum but it still fails. I will post images below of where my problem arises. I have s-off unlocked bootloader and was able to go from 1.56 hboot back to the 1.44 hboot no problem. In the second image I tried using an RUU, stock odexed rom, and then a firmware update but all failed . The errors occur when checking the info parsing or model id.
Click to expand...
Click to collapse
first you can not use "fastboot flash zip" to flash odexed rom or any other roms, they must be flashed using a custom recovery. Only firmware pacakge and ruu can be flashed this way.
I also see that your version main is 1.10.605.10 which is for verizon phones MID: PN0731000 (yours is PN0713000) and cid VZW__001 (yours is T-MOB010). It looks like you have flashed a verizon firmware on your t-mobile phone which is not a good thing.... Dont know what you have previously done to this phone but it looks like you are trying to hard brick it
Dont understand neither why you are trying to flash the 6.09.401.5 odexed rom that doesnt match your phone info...
Here are the ruu for your phone (PN0713000 and T-MOB010):
http://www.htc1guru.com/dld/ruu_m7_...0-20_10-40-1150-04_release_324846_signed-exe/
http://www.htc1guru.com/dld/ruu_m7_...3_10-38m-1157-04_release_336982_signed_2-exe/
http://www.htc1guru.com/dld/ruu-zip...157-04_release_336982_signed_2_decrypted-zip/
use one of them and see if your phone can recover (I hope that flashing the wrong firmware did not bricked it)
@alray Thanks for much for the info! Can't believe I was trying to flash the wrong ruu's :/. I will download the ones you provided and report back in few hours when I get home and hopefully my phone can still be saved.

Htc One AT&T trying to upgrade to lollipop using official RUU - get error 155

Have a Htc One (AT&T, but unlocked) and it is running Android 4.4.2 . I see there is an update for lollipop in form of the RUU officially from HTC (7.23.502.9).
http://www.htc.com/us/support/htc-one-att/news/
I attempted to install it but get an error 155.
Using Windows 10.
Drivers are installed.
Tried several RUU's but with same result. Tried it on 2 laptops (both windows 10), have no accesss to windows 7 or windows xp at the moment to try anything else.
Attaching a screenshot of the bootloader screen of my phone.
Any help is appreciated.
Thank you,
BorisZX6R said:
Have a Htc One (AT&T, but unlocked) and it is running Android 4.4.2 . I see there is an update for lollipop in form of the RUU officially from HTC (7.23.502.9).
http://www.htc.com/us/support/htc-one-att/news/
I attempted to install it but get an error 155.
Using Windows 10.
Drivers are installed.
Tried several RUU's but with same result. Tried it on 2 laptops (both windows 10), have no accesss to windows 7 or windows xp at the moment to try anything else.
Attaching a screenshot of the bootloader screen of my phone.
Any help is appreciated.
Thank you,
Click to expand...
Click to collapse
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...
alray said:
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...
Click to expand...
Click to collapse
Thank you for your time and response. I will think about what RUU is best for me. I am currently on the T-Mobile network with this phone and so far there is no indicator that will change anytime soon. I will try and post my response.
Thank you again!
alray said:
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...
Click to expand...
Click to collapse
Unfortunately I am still hunting for an RUU that will bring the hboot to version 1.57. All the ones I tried either fail with error 155 or they leave me on the same version of hboot. Trouble finding an appropriate RUU... If you know where I can get one that will upgrade the hboot to 1.57 please guide me in the right direction.
Thank you!
BorisZX6R said:
Unfortunately I am still hunting for an RUU that will bring the hboot to version 1.57. All the ones I tried either fail with error 155 or they leave me on the same version of hboot. Trouble finding an appropriate RUU... If you know where I can get one that will upgrade the hboot to 1.57 please guide me in the right direction.
Thank you!
Click to expand...
Click to collapse
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)
alray said:
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)
Click to expand...
Click to collapse
Thank you very much, I will attempt to do this and I will post my results once I had a chance to try it.
One more thing, isn't having a super CID an advantage?! Is 11111111 a super CID?!
Thank you!
BorisZX6R said:
Thank you very much, I will attempt to do this and I will post my results once I had a chance to try it.
One more thing, isn't having a super CID an advantage?! Is 11111111 a super CID?!
Thank you!
Click to expand...
Click to collapse
Yes, supercid is 11111111 so your CID isn't a problem. Just make sure that your MID also match the ruu you want to use (or change it if needed). If you MID is still the original, it should be PN0712000 so you can either use an AT&T or Developer Edition RUU (x.xx.1540.x). Otherwise if you want to use the WWE version (x.xx.401.x) You'll have to change your MID to PN0710000.
alray said:
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)
Click to expand...
Click to collapse
It worked. For a moment the output in the command window seemed like it was giving errors (unfortunately it was very late and I did not copy the output) but in the end I realized it updated the hboot and I was able to flash a different RUU.
Thank you for all your help!

Categories

Resources