Develop Bugs

error 130: Bootloader Error

Hi all,
I'm new with the HTC (S-On).
I want to unlock the phone, but get the wrong version of the ROM.
So, here is what I already done:
1. Install the ROM RUU_Marvel_S_HTC_Europe_2.13.401.2_Radio_47.23a.35.3035H_7.53.39.03M_release_225747_signed.exe. And when I search the RUU to unlock it, I get the version 401.3.
2. Since I just see the 401.3, I installed this ROM RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe.
3. Well, it's totally wrong, because the last RUU on the HTC Dev is 2.13.401.3. So I install the correct one RUU_Marvel_S_HTC_Europe_2.13.401.3_Radio_47.23c.35.3037_7.54.39.28M_release_236989_signed.exe, but I get the error.
:crying:
Error 130: (I forget the error, it said about bootloader error).
Please help.
Thankyou

awn88 said:
Hi all,
I'm new with the HTC (S-On).
I want to unlock the phone, but get the wrong version of the ROM.
So, here is what I already done:
1. Install the ROM RUU_Marvel_S_HTC_Europe_2.13.401.2_Radio_47.23a.35.3035H_7.53.39.03M_release_225747_signed.exe. And when I search the RUU to unlock it, I get the version 401.3.
2. Since I just see the 401.3, I installed this ROM RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe.
3. Well, it's totally wrong, because the last RUU on the HTC Dev is 2.13.401.3. So I install the correct one RUU_Marvel_S_HTC_Europe_2.13.401.3_Radio_47.23c.35.3037_7.54.39.28M_release_236989_signed.exe, but I get the error.
:crying:
Error 130: (I forget the error, it said about bootloader error).
Please help.
Thankyou
Click to expand...
Click to collapse
If you are in the process of unlocking bootloader skip the RUU section and proceed to STEP 1
Hit thanks if i helped

vedang81 said:
If you are in the process of unlocking bootloader skip the RUU section and proceed to STEP 1
Hit thanks if i helped
Click to expand...
Click to collapse
that's the error. I need to downgrade it. Found a solution here (http://forum.xda-developers.com/showthread.php?t=1445867), but it also failed.
I want to try this http://forum.xda-developers.com/showthread.php?t=1540952&highlight=downgrade, but it says I need to flash the CWM first. How I supposed to be able flash it when my phone still on locked state?

awn88 said:
that's the error. I need to downgrade it. Found a solution here (http://forum.xda-developers.com/showthread.php?t=1445867), but it also failed.
I want to try this http://forum.xda-developers.com/showthread.php?t=1540952&highlight=downgrade, but it says I need to flash the CWM first. How I supposed to be able flash it when my phone still on locked state?
Click to expand...
Click to collapse
check ur pm
Sent from my Android lappy

[Q] HTC One X - Can't Install RUU

Hi,
I've managed to mess up my HTC One X quite badly.
From poking around with fastboot I've got the following information from it;
PJ4610000
Main Version 1.26.401.2
Cid - none
Radio 1.1204.90.13
0.43.0000
I know how I messed it up. I'd not realised you couldn't install Jellybeam roms onto 0.43.000. One Cyanogenmod (cm-10.2.0-endeavoru) later and bingo, bootloop.
Didn't help that I had less than 30% battery life.
Anyway, I've now used a script to get the battery life up - but I haven't been able to run any RUU's on this - I downloaded two;
RUU_ENDEAVOR_U_ICS_40_O2_UK_1.26.206.2_Radio_1.1204.90.13_release_251230_signed
and
RUU_ENDEAVOR_U_ICS_40_S_Vodafone_UK_2.17.161.4_Radio_2.1204.137D1.21_release_280390_signed
I'm thinking now that I cant do these either because I'm on 0.43.000 or because I need generic.
Ideally I want it to be latest Android and generic stock. It's for my wife, so she doesn't need superuser - but I'd like it so If I can get there too, great.
i've read through the main sticky's, but can't work out what the steps are I should be taking to get it out of the bootloop it's in and onto stock
What do I download? Do I need to do this;
http://forum.xda-developers.com/showthread.php?t=1660807
Or this;
http://forum.xda-developers.com/showthread.php?t=2069904
whilst I do it?
Help much appreciated, as I seem to be stuck at this stage.

Download a 1.26.401 Ruu or a 1.29.401 Ruu. You are trying to install the wrong ruu because the main number is different !
My advice :
Download the 1.29.401 ruu and relock the bootloader, put the phone in fastboot usb mode. Then install the ruu with admin rights and let it install. Reboot the phone and go to settings-about-software updates and check for ota....if they are there install all of them you can get !
If there are no ota's available you look for the 2.17.401 ruu and install that the same way as the 1.29 and then do the ota........still no ota, download the 3.14.401 ruu and install that too. After that you can install any rom out here.

Mr Hofs said:
Download a 1.26.401 Ruu or a 1.29.401 Ruu. You are trying to install the wrong ruu because the main number is different !
My advice :
Download the 1.29.401 ruu and relock the bootloader, put the phone in fastboot usb mode. Then install the ruu with admin rights and let it install. Reboot the phone and go to settings-about-software updates and check for ota....if they are there install all of them you can get !
If there are no ota's available you look for the 2.17.401 ruu and install that the same way as the 1.29 and then do the ota........still no ota, download the 3.14.401 ruu and install that too. After that you can install any rom out here.
Click to expand...
Click to collapse
Right so;
1 - Download a 1.29.401 Ruu.
Ok, so like -
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.12_Radio _2.1204.127.19_release_271851_signed.exe?
Having real problems finding a rom download, these all seem to be on bugsylawson.com which my ISP blocks, or Hotfile which is down, but I'll look into that.
So I run that, with the device in Fastboot and enough battery life, which I use my batch script for?
2. Then 'relock the bootloader'. Is that running fastboot oem lock, when in fastboot, using the .exe in the folder and a command line?
Any special to do 'admin rights'? Or is that my local Windows account you mean?
I'm a bit worried about running OTA as apparently, some of these RUU's for the One X the OTA updates don't work - 401.6, I think?
Not sure if this affects the one I suggested?
3. Then run another RUU to upgrade if OTA doesn't work?
Is that about right (and thanks for the help, obviously!)

1 correct, try this thread for download links
http://forum.xda-developers.com/showthread.php?t=2094113
2: fastboot command is correct, leave the phone in the bootloader and start the ruu.exe from the pc, right click the file and select run as administrator
Ota should be there unless HTC/carrier has took them from the server, hence the advise that if it doesn't work to install a higher ruu after you tried.
3: correct

Mr Hofs said:
1 correct, try this thread for download links
http://forum.xda-developers.com/showthread.php?t=2094113
2: fastboot command is correct, leave the phone in the bootloader and start the ruu.exe from the pc, right click the file and select run as administrator
Ota should be there unless HTC/carrier has took them from the server, hence the advise that if it doesn't work to install a higher ruu after you tried.
3: correct
Click to expand...
Click to collapse
No joy with that site, I get;
This website has been reported as unsafe
www.androidruu.com
Then if I proceed;
"Warning: mysql_connect(): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) in /home/ruu/public_html/admin/dbconnect.php on line 11
Could not connect: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)" when I try to download any RUU.

Site works fine here, sorry

See

Maybe Google the whole ruu name, there a couple of them on hotfile hosting.
I was planning to put a small selection to nu dev host. Nut thats of no use now. Not earlier than tonight

Actually I don't know the programing language, it may be PC or network security something like that.
We can do download at this site no problem.

Mr Hofs said:
Maybe Google the whole ruu name, there a couple of them on hotfile hosting.
I was planning to put a small selection to nu dev host. Nut thats of no use now. Not earlier than tonight
Click to expand...
Click to collapse
The site works to the page you showed, I got that SQL issue from any rom link.
But luckily I've found RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.12_Radio_2.1204.127.19_release_271851_signed
elsewhere.
Running it now and it failed.
So now I'm showing;
Radio as 2.1204.127.19
And bootloader as 0.43.
Oh no, hang on, I've not locked the bootlader, maybe that's why. I'll try again.

Yep try again, it must be locked

Mr Hofs said:
Yep try again, it must be locked
Click to expand...
Click to collapse
I get an error when unlocking. It says "status read failed, too many links"
But on reboot, I get "Reloocked" at the top, so I've tried again and it seemed to work, well enough to get me to an OS!
Only thing is, my home buttons etc don't work.

Hmm that's weird. Rerun the ruu. And in OS try to update
Ow or look for the 2.17.401 ruu and install that also !
And do not unlock it until you are updated high enough ! You need at least a hboot of 1.36/1.39 which is common in 401 software numbers.

Mr Hofs said:
Hmm that's weird. Rerun the ruu. And in OS try to update
Ow or look for the 2.17.401 ruu and install that also !
And do not unlock it until you are updated high enough ! You need at least a hboot of 1.36/1.39 which is common in 401 software numbers.
Click to expand...
Click to collapse
Been locked out of my wireless for the moment, but am downloading RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
at the moment.

That's good :thumbup:

Mr Hofs said:
That's good :thumbup:
Click to expand...
Click to collapse
http://www.androidruu.com/ Reported for problem with MSQL: Warning: mysql_connect(): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) in /home/ruu/public_html/admin/dbconnect.php on line 11
Could not connect: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
and fixed now

Awesome thant, although the 2.17.401 ruu there is messed up. It's only 80 Mb and that's way to little !

OK, got it up to the latest official version and the screen was broken, so had that replaced.
Now need to get Cyanogenmod on it.
First thing - relocking, right?

First thing is reading and understand the things you need to do. If you start by saying to relock it we are off for a bad start !
Read the stickies and guides first on what you need to do before messing around !

Mr Hofs said:
First thing is reading and understand the things you need to do. If you start by saying to relock it we are off for a bad start !
Read the stickies and guides first on what you need to do before messing around !
Click to expand...
Click to collapse
Sorry, didn't mean to cause concern - I meant, now my screen is repaired and I'd got a stock rom onto it- then upgraded the stock rom several times, the first thing I needed to do was unlock the bootloader again.
I went off, read up on rooting again and followed several guides. Rooted, unlocked bootloader and I've got it to the stage now where we're on a decent level of bootloader, Cyanogenmod 10.2 (stable) is running and the phone works.
So thank you very much for that.
Only issue I have now is the battery life has nose dived. It's barely doing 12 hours.
Screen seems to be mostly responsible according to the stats, 52%.
Might just try replacing the Kernel before I go stomping back to Fonedoctors about the replacement screen.
I've made so many changes to os, bootloader etc during this process I may well have missed a step with wiping the caches or similar.
I made a full backup of the stock os before I went to Cyanogenmod, so I can drop back to that now to check it's not the os if I need.
Any thoughts on a good Kernel? Or advice on how to most easily change kernel with minmal risk? I really don't want to dabble anymore, so it's tempting to go back to stock 4.2.2 and just strip out sense 5 - which I disliked.

Full stock Dev Ed M8 won't take OTA or RUU for MM

I have a Dev edition M8 that i zip RUU'ed back to lollipop. i took a security update successfully, then the 3 preinstall updates in prep for marshmallow. however, I now get an error when taking the actual OTA for marshmallow. I am s-off and bootloader unlocked. I then downloaded the RUU from HTC to run the exe, but i always get error 155. I read @Sneakyghost post about firmware and it said it was either region ID's not matching, or the bootloader being unlocked. I don't see why the unlocked bootloader would be a problem when im s-off and its a dev edition, which is bootloader unlocked out of the box. Anyone know what is causing this?

fyarf said:
I have a Dev edition M8 that i zip RUU'ed back to lollipop. i took a security update successfully, then the 3 preinstall updates in prep for marshmallow. however, I now get an error when taking the actual OTA for marshmallow. I am s-off and bootloader unlocked. I then downloaded the RUU from HTC to run the exe, but i always get error 155. I read @Sneakyghost post about firmware and it said it was either region ID's not matching, or the bootloader being unlocked. I don't see why the unlocked bootloader would be a problem when im s-off and its a dev edition, which is bootloader unlocked out of the box. Anyone know what is causing this?
Click to expand...
Click to collapse
Haha nice man I just finished downloading that exact RUU and I have that exact phone in the exact same state. I got it from someone in the US.
I'll let you know how it goes on mine...

Sneakyghost said:
Haha nice man I just finished downloading that exact RUU and I have that exact phone in the exact same state. I got it from someone in the US.
I'll let you know how it goes on mine...
Click to expand...
Click to collapse
heres my recovery message, just to maybe help troubleshoot it. it mentions userdata being busy (i got an error in the zip ruu flash for userdata, had to flash the ruu zip twice to get an okay), then kidmode missing. not sure what to do besides flash the firmware from http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894

Modified system apps, sir. That's what it is. Did you root your system?
Edit:
Maybe not. Maybe just can't find those apps cuz it can't mount data.
Something wrong there.
No idea.
I'll see where I end up.

Sneakyghost said:
Modified system apps, sir. That's what it is. Did you root your system?
Edit:
Maybe not. Maybe just can't find those apps cuz it can't mount data.
Something wrong there.
No idea.
I'll see where I end up.
Click to expand...
Click to collapse
i did a factory reset from stock recovery, and kid mode is present now, maybe im onto something...
Edit: not rooted directly from a factory ruu zip (well, hopefully the zip creator did a factory dump and was unmodified) but kid mode wasnt an option before the factory reset

fyarf said:
i did a factory reset from stock recovery, and kid mode is present now, maybe im onto something...
Edit: not rooted directly from a factory ruu zip (well, hopefully the zip creator did a factory dump and was unmodified) but kid mode wasnt an option before the factory reset
Click to expand...
Click to collapse
Unfortunately, I'm with family tonight and won't be able to assist until much later. But note this: the factory reset could well help. I can explain later.

Sneakyghost said:
Unfortunately, I'm with family tonight and won't be able to assist until much later. But note this: the factory reset could well help. I can explain later.
Click to expand...
Click to collapse
ok so i got mine to work.. apparently the zip RUU isnt good. i ran the exe 4.16.1540.8 from here http://forum.xda-developers.com/showthread.php?t=2701376 and then updated ota from there without issue. so my guess is the RUU zip wasnt perfect system-wise,while the exe is straight from htc.

fyarf said:
ok so i got mine to work.. apparently the zip RUU isnt good. i ran the exe 4.16.1540.8 from here http://forum.xda-developers.com/showthread.php?t=2701376 and then updated ota from there without issue. so my guess is the RUU zip wasnt perfect system-wise,while the exe is straight from htc.
Click to expand...
Click to collapse
ok. Where you got that zip from? Cuz I downloaded the 6.xx RUU.exe straight from HTC USA...

Sneakyghost said:
ok. Where you got that zip from? Cuz I downloaded the 6.xx RUU.exe straight from HTC USA...
Click to expand...
Click to collapse
zip was from the same thread, i tried the exe instead because it was an HTC file instead of a contributor. now on MM sense. The 6.xx RUU refused to work no matter what i did, so i OTA'd to the latest version.

fyarf said:
zip was from the same thread, i tried the exe instead because it was an HTC file instead of a contributor. now on MM sense. The 6.xx RUU refused to work no matter what i did, so i OTA'd to the latest version.
Click to expand...
Click to collapse
I seem to be having an entirely different problem. After swapping cables, phones and laptop ports as well as updating drivers, it appears that the usb port of my M8 is broken. I'll have to see at someone else's computer, maybe tomorrow. Pretty frustrating right now as I'm liking the M8 better than my M9 and M7.
[EDIT]
I could stabilize the connection enough to run another, international RUU. The RUU worked fine while the 6.12.1540.4 kept getting stuck at either "checking header" or "sending" - both times with a successfully established connection. I already tweeted HTC asking to have that RUU checked. I assume your findings were correctly indicating a bad RUU, since a.) It also didn't work here and b.) people from my team have confirmed seeing several fail scenarios with that RUU spread over XDA.
Guess that's that then. Thanks for raising the issue. I would have messed around with it much longer otherwise since the error messages are not clearly pointing towards a broken RUU.
[EDIT]
More updates: searching the M8 forum for 6.12.1540.4 turned up this: http://forum.xda-developers.com/showthread.php?p=64320571
That'd mean the RUU fails at the hboot pre-update reboot. All that's needed apparently is to flash only the hboot manually first, so it can proceed. Hence also error 155 which usually indicates issues with the system image. You experienced that most likely because the older hboot couldn't extract the system.img from the rom.zip.
Usually, the procedure is:
RUU updates hboot
RUU reboots to boatloader
RUU updates rest of firmware
RUU sends over the system image in parts
Hboot now decrypts and flashes the part.zips
It just looks like mandatory hboot-first-flash didn't happen right, either not rebooting after it or not flashing it at all.
However, this seems to be fixable by running the hboot/firmware package first and then the complete RUU.

Sneakyghost said:
I seem to be having an entirely different problem. After swapping cables, phones and laptop ports as well as updating drivers, it appears that the usb port of my M8 is broken. I'll have to see at someone else's computer, maybe tomorrow. Pretty frustrating right now as I'm liking the M8 better than my M9 and M7.
[EDIT]
I could stabilize the connection enough to run another, international RUU. The RUU worked fine while the 6.12.1540.4 kept getting stuck at either "checking header" or "sending" - both times with a successfully established connection. I already tweeted HTC asking to have that RUU checked. I assume your findings were correctly indicating a bad RUU, since a.) It also didn't work here and b.) people from my team have confirmed seeing several fail scenarios with that RUU spread over XDA.
Guess that's that then. Thanks for raising the issue. I would have messed around with it much longer otherwise since the error messages are not clearly pointing towards a broken RUU.
[EDIT]
More updates: searching the M8 forum for 6.12.1540.4 turned up this: http://forum.xda-developers.com/showthread.php?p=64320571
That'd mean the RUU fails at the hboot pre-update reboot. All that's needed apparently is to flash only the hboot manually first, so it can proceed. Hence also error 155 which usually indicates issues with the system image. You experienced that most likely because the older hboot couldn't extract the system.img from the rom.zip.
Usually, the procedure is:
RUU updates hboot
RUU reboots to boatloader
RUU updates rest of firmware
RUU sends over the system image in parts
Hboot now decrypts and flashes the part.zips
It just looks like mandatory hboot-first-flash didn't happen right, either not rebooting after it or not flashing it at all.
However, this seems to be fixable by running the hboot/firmware package first and then the complete RUU.
Click to expand...
Click to collapse
I'm not sure about OP, but that worked perfectly for me. I wonder how HTC let a broken RUU.exe past testing?

Double_a2013 said:
I'm not sure about OP, but that worked perfectly for me. I wonder how HTC let a broken RUU.exe past testing?
Click to expand...
Click to collapse
They frequently do. Nothing exciting. That's why I notified HTC. They take their time with fixing them. The earlier the better.

Sneakyghost said:
They frequently do. Nothing exciting. That's why I notified HTC. They take their time with fixing them. The earlier the better.
Click to expand...
Click to collapse
Wow, I didn't realize that. Now if only they'd fix the ATT LTE issues on the dev rom :silly:

Double_a2013 said:
Wow, I didn't realize that. Now if only they'd fix the ATT LTE issues on the dev rom :silly:
Click to expand...
Click to collapse
My ota to the latest dev version got lte on at&t no problem, sure your apn settings are correct?

fyarf said:
My ota to the latest dev version got lte on at&t no problem, sure your apn settings are correct?
Click to expand...
Click to collapse
I've never had to reconfigure them before, regardless of if I'm using GPE or Sense RUUs. I'll give it another shot, and get back in a more timely manner
Edit: Apn settings seem fine. It's using the Nextgenphone one from ATT
Edit #2:
http://forum.xda-developers.com/att...ming-calls-lte-mode-m8-att-arhd-34-0-t3026710
Found this thread about a similar issue. I guess I'll disable HD Voice (Honestly, its borderline useless anyway) and see if that solves anything

Help with installing AT&T Ruu

I'm a very new android user, so please forgive my ignorance.
I'm using a sim unlocked AT&T M8 outside USA with a different carrier. Right now, the bootloader is Locked, CID is 11111111 and S-OFF. I've downloaded the official marshmallow AT&T RUU for m8 from htc website.
I follow the install instructions until the update actually starts. Then it stops after about 10-20 seconds and shows Error 155: unknown error and enters into the recovery steps (in the RUU). My current software number is 4.28.502.2 and im trying to update to RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5
Can someone please help me out with this? I've been trying for over a week now. I will never receive the OTA's since I'm not using an AT&T sim. So RUU is the only other option left. Thanks a lot in advance.

http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23

ckpv5 said:
http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
Click to expand...
Click to collapse
Thanks for your reply man, but im extremely lost here. Could you please guide me step by step? I've downloaded the firmware. Where do I put it? I've tried the adb folder. But it show error: can not locate firmware.zip.
Edit: Another question. Is that firmware applicable for my device?

The firmware is applicable BUT since you're using your device outside USA and not on AT&T carrier, S-Off .. the best thing for you to do is fully convert your device to other region, maybe a EU region or Dev Edition .. more suitable for you.
I read somewhere, with the latest firmware you may have calls problem due to Voice HD implemented by AT&T
If you're interested in converting, I will guide you (when I am available)

ckpv5 said:
The firmware is applicable BUT since you're using your device outside USA and not on AT&T carrier, S-Off .. the best thing for you to do is fully convert your device to other region, maybe a EU region or Dev Edition .. more suitable for you.
I read somewhere, with the latest firmware you may have calls problem due to Voice HD implemented by AT&T
If you're interested in converting, I will guide you (when I am available)
Click to expand...
Click to collapse
That would be very kind of you, thanks. Though, i think I've already messed up my phone. I finally got to update with the firmware in the link. The RUU was going on smoothly as well, until it reached 38% when Error 155 showed up again. The phone then went on to the bootloader screen with no options for fastboot, restore or such. I restarted it and entered the bootloader. My firmware is being shown as 6.20.502.5 but when rebooting the phone it won't go past the screen with the HTC logo. I'd be extremely grateful if you could help me out of this mess.
Also, when i open htc sync man, OS number and HTC Sense number shows up as blank, while the firmware number is shown as 6.20.502.5

Big-Bonsai said:
Also, when i open htc sync man, OS number and HTC Sense number shows up as blank, while the firmware number is shown as 6.20.502.5
Click to expand...
Click to collapse
Aren't you supposed to uninstall Htc Sync Manager before you run the RUU ?
That was clearly stated in link that I gave you earlier, and you also need PC with USB 2.0
Uninstall HTC Sync Manager but leave HTC USB drivers then try again to run RUU after you put the device on bootloader/fastboot mode.

ckpv5 said:
Aren't you supposed to uninstall Htc Sync Manager before you run the RUU ?
That was clearly stated in link that I gave you earlier, and you also need PC with USB 2.0
Click to expand...
Click to collapse
Yeah I did. I re-installed it later to see if it would show any information.

Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.

ckpv5 said:
Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.
Click to expand...
Click to collapse
So I'm gonna try the RUU again. I'll keep you updated. You've been a big help. Thanks a lot!!

Big-Bonsai said:
I'm a very new android user, so please forgive my ignorance.
I'm using a sim unlocked AT&T M8 outside USA with a different carrier. Right now, the bootloader is Locked, CID is 11111111 and S-OFF. I've downloaded the official marshmallow AT&T RUU for m8 from htc website.
I follow the install instructions until the update actually starts. Then it stops after about 10-20 seconds and shows Error 155: unknown error and enters into the recovery steps (in the RUU). My current software number is 4.28.502.2 and im trying to update to RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5
Can someone please help me out with this? I've been trying for over a week now. I will never receive the OTA's since I'm not using an AT&T sim. So RUU is the only other option left. Thanks a lot in advance.
Click to expand...
Click to collapse
I don't know if it's the problem,but did you try the RUU after unlocking your bootloader as you are S-OFF?
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Why don't you try a EU RUU?Mine was also a AT&T device,but I converted it.

Jongla said:
I don't know if it's the problem,but did you try the RUU after unlocking your bootloader as you are S-OFF?
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Why don't you try a EU RUU?Mine was also a AT&T device,but I converted it.
Click to expand...
Click to collapse
Hey man, thanks for replying here. I sent you a pm. Could you please check?

ckpv5 said:
Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.
Click to expand...
Click to collapse
Hello there. I kind of made it work. What I did was take the rom.zip from the ruu file and flash it via htc fastboot special. And it worked well. The only problem I'm facing now is that the boot animations are EXTREMELY slow. But once it's past that, everything seems pretty normal. I wiped the cache from recovery but that didn't help. Do you have any suggestions for me?

Big-Bonsai said:
\The only problem I'm facing now is that the boot animations are EXTREMELY slow. But once it's past that, everything seems pretty normal. I wiped the cache from recovery but that didn't help.
Click to expand...
Click to collapse
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
Jongla said:
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Click to expand...
Click to collapse
Neither of those statements is entirely correct.
With s-off, you can run an RUU with bootloader locked or relocked. Essentially, the check for the bootloader unlocked condition is bypassed with s-off.
But having the bootloader locked still means its locked (even with s-off). Meaning you can't do things like flash custom recovery with bootloader locked (even with s-off).

redpoint73 said:
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
Hello there. Thanks for the reply. What I meant was, the boot animations are slow every time I reboot the device.
Things I have already done:
1. Flashed the rom.zip again.
2. Factory reset.
3. Wiped the cache from recovery multiple times.
4. Restarted in all possible ways. Normal restart. Power off, wait 10 minutes and power on again. Pressed the power and volume up button for restarting. Reboot via fastboot.
I'd really appreciate if you could help me out.
Click to expand...
Click to collapse

redpoint73 said:
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
Neither of those statements is entirely correct.
With s-off, you can run an RUU with bootloader locked or relocked. Essentially, the check for the bootloader unlocked condition is bypassed with s-off.
But having the bootloader locked still means its locked (even with s-off). Meaning you can't do things like flash custom recovery with bootloader locked (even with s-off).
Click to expand...
Click to collapse
Hello there. Thanks for the reply. What I meant was, the boot animations are slow every time I reboot the device.
Things I have already done:
1. Flashed the rom.zip again.
2. Factory reset.
3. Wiped the cache from recovery multiple times.
4. Restarted in all possible ways. Normal restart. Power off, wait 10 minutes and power on again. Pressed the power and volume up button for restarting. Reboot via fastboot.
I'd really appreciate if you could help me out.

Since you've already flashed the RUU again, I don't think there is much else you can do. Maybe its a common issue with the new build?

redpoint73 said:
Since you've already flashed the RUU again, I don't think there is much else you can do. Maybe its a common issue with the new build?
Click to expand...
Click to collapse
Man I searched EVERYWHERE. People dont seem to have any problems like this. What I did find out was that this might happen if the firmware or kernel numbers dont match (or something?). Can you tell me if I did anything wrong?

Big-Bonsai said:
What I did find out was that this might happen if the firmware or kernel numbers dont match (or something?).
Click to expand...
Click to collapse
That only applies to flashing ROMs in custom recovery. WHich is completely different from RUU. RUU re-writes all partitions, including firmware, kernel, ROM, and a bunch of others. So there isn't a possibility of a mismatch; as long as the RUU ran properly. And since you ran the RUU twice, you pretty much eliminated the possibility it didn't install completely.
Some other options you may consider:
1) Unlock the bootloader, flash TWRP custom recovery, flash a different ROM and see if the slow boot issue persists.
2) Change CID and/or MID (which you are free to do since you are s-off) and try another RUU; such as Developer's Edition or Euro.

redpoint73 said:
That only applies to flashing ROMs in custom recovery. WHich is completely different from RUU. RUU re-writes all partitions, including firmware, kernel, ROM, and a bunch of others. So there isn't a possibility of a mismatch; as long as the RUU ran properly. And since you ran the RUU twice, you pretty much eliminated the possibility it didn't install completely.
Some other options you may consider:
1) Unlock the bootloader, flash TWRP custom recovery, flash a different ROM and see if the slow boot issue persists.
2) Change CID and/or MID (which you are free to do since you are s-off) and try another RUU; such as Developer's Edition or Euro.
Click to expand...
Click to collapse
Thank you so much for the reply. I'd like to take your second suggestion. Can you please point me to the right direction? Or guide me through the steps. I don't know if it's asking too much of you. Thanks anyways.

Big-Bonsai said:
Thank you so much for the reply. I'd like to take your second suggestion. Can you please point me to the right direction? Or guide me through the steps.
Click to expand...
Click to collapse
Which version do you want to "convert" to?
Dev Ed is easy, it shares the same model ID (MID) as AT&T, and you already have SuperCID. So all you would need to do is run the MM Dev Ed RUU: http://dl3.htc.com/application/RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
Euro is a bit more steps, you would need to change to the Euro MID: http://forum.xda-developers.com/showthread.php?t=2708581
Then run Euro MM RUU, noting that relocking bootloader is not needed for you (since you have s-off): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6

Htc M9 no os

To sum up i wanted to wipe the date and i "accidentaly"(how can be accidentantaly?well i am an idiot) delete the os of my htc m9. I was stucked in the starting logo for ages.I have acess to download and recovery mode.I tried to flash a custom rom i found in the forums using the twrp all went good it flashed the rom.When it reached the part where it says android application updating 0-189 it did everything.After that it kept showing me the htc logo i could restart shutdown lock and power up and down the volume but nothing else and the logo kept in front.Any idea?can it be fixxed?s-on.Thanks for your time

You need to flash a stock firmware. The same firmware as what was on it before it borked.
Beamed in by telepathy.

shivadow said:
You need to flash a stock firmware. The same firmware as what was on it before it borked.
Beamed in by telepathy.
Click to expand...
Click to collapse
i ve been trying all day.now i flashed a rom the phone will open but it has no signal.cant i just install the stock rom with odin?and be like it was?thanks

So i am in a loop here.I flashed a rom which is not working.Twrp is not working so i cant flash a new rom.Also my pc wont "see" my phone when i am plugging in my phone it does that connect disconnect sound all the time like crazy so i cant install twrp again.Please help me

anon_1993_ said:
So i am in a loop here.I flashed a rom which is not working.Twrp is not working so i cant flash a new rom.Also my pc wont "see" my phone when i am plugging in my phone it does that connect disconnect sound all the time like crazy so i cant install twrp again.Please help me
Click to expand...
Click to collapse
Have you read through the readme thread? One of your previous posts referenced ODIN, which is a Samsung tool. If you've read through the readme thread we will have a common foundation of understanding - and you may discover the solution to your problem there.
It sounds like you need to flash a RUU to your phone. The pre-requisites and guide to doing so are laid out in the readme thread. If you have any questions after reading through it, please post them here and we'll help out as best we can.

i am sorry for asking so much.But in order to flash a RUU it says that you need a rooted device.How i am gonna root my device since i cant connect it to my pc?

anon_1993_ said:
i am sorry for asking so much.But in order to flash a RUU it says that you need a rooted device.How i am gonna root my device since i cant connect it to my pc?
Click to expand...
Click to collapse
Where does my ReadMe thread say what I highlighted in the quote?

Flippy498 said:
Where does my ReadMe thread say what I highlighted in the quote?
Click to expand...
Click to collapse
so i downloaded thr ruu many times but i am keep receiving 22 RU_HEADER_ERROR. what i am doing wrong?

anon_1993_ said:
so i downloaded thr ruu many times but i am keep receiving 22 RU_HEADER_ERROR. what i am doing wrong?
Click to expand...
Click to collapse
Which RUU are you exactly trying to flash (link it please)? What's your current firmware version? Have you checked the MD5 checksum of the downloaded file? What's the size of the SD card you're using? What's its format?

Flippy498 said:
Which RUU are you exactly trying to flash (link it please)? What's your current firmware version? Have you checked the MD5 checksum of the downloaded file? What's the size of the SD card you're using? What's its format?
Click to expand...
Click to collapse
i followed the guide its 32 giga exfat. My firmware is 3.35.401.12 and i am trying to install this one https://pa1.androidfilehost.com/dl/...1_U11440792_97.00.51203G_F_release_signed.zip

That RUU got successfully flashed by S-ON users in the past and it's the correct one for your current firmware. So either the file got corrupted during the download (you didn't mention whether the MD5 checksum matched) or your SD card is broken.
Sent from my HTC One M9 using XDA Labs

sorry for not responding.today i had my day off and tried once again to fix the phone and Ruu is working.It was the cable i went and bought a new genuine one.Atm the phone is blank from Os when ill turn it on it will automatically take me to the bootloader.I tried to run a ruu.exe but i got a 155 error saying i am using the wrong ruu.I locked the bootloader using oem lock to try if that was the problem but aparrently it wassnt. the phone was from Europe and was working with differents sims in greece and uk so i assume its unlocked.Cant i just install a the stock rom with twrp?

I actually won't answer in this thread, anymore. You already got told to read the ReadMe thread and to follow its instructions. That thread clearly explains how to find the correct RUU and how to flash it. Besides, it tells you not to (re-)lock the bootloader and why you shouldn't do so.
If you ignore all these information and prefer to try out wrong RUUs and to relock your bootloader then there's nothing I can do for you.

Flippy498 said:
I actually won't answer in this thread, anymore. You already got told to read the ReadMe thread and to follow its instructions. That thread clearly explains how to find the correct RUU and how to flash it. Besides, it tells you not to (re-)lock the bootloader and why you shouldn't do so.
If you ignore all these information and prefer to try out wrong RUUs and to relock your bootloader then there's nothing I can do for you.
Click to expand...
Click to collapse
thank you and i am sorry for the stupid questions and actions.