Develop Bugs

RUU Stock

Hi
I have accidentaly wiped system and sd card in CWM and cant mount via usb. I cannot find a stock HTC One X RUU and I had downloaded o2 RUU (would prefer carrier branded as want to return!!! although doesn't matter) but that was corrupted and downloaded off a chiness site that has stopped hosting it!
Please help me!
Doesnt matter if all you can find is a recovery that you can mount USB!! That would be great!!
Thank you very much guys!!!!!!!!!!!!!!!!!!!!!!!!!!!
-----------------------------------------------------------------------------------------------------------------------------------------------------
Thank you very much for all of your help! I have solved my issue.
I needed to download the stock o2 uk RUU and relock the bootloader and run the program in fast boot. I have just made my nandroid backup and planning to upload it so anyone else can use it! (it wont have my details on, just as if the os has been installed from scratch)
Steven

Please read before posting/flashing/wiping.
What is the CID of your device. You can only flash a stock RUU with matching CID.
So you need to download the correct RUU for your device.
All stock RUUs available are here

.
Keep thread on topic please

How do I find my CID?

stevepork said:
Hi
I have accidentaly wiped system and sd card in CWM and cant mount via usb. I cannot find a stock HTC One X RUU and I had downloaded o2 RUU (would prefer carrier branded as want to return!!! although doesn't matter) but that was corrupted and downloaded off a chiness site that has stopped hosting it!
Please help me!
Doesnt matter if all you can find is a recovery that you can mount USB!! That would be great!!
Thank you very much guys!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
If you would have spent 10 seconds looking in the Dev thread you would have found a list of all the available RUU's to download.
(http://forum.xda-developers.com/showthread.php?t=1543604)
Download your required RUU, boot into Fastboot-USB and run.
Next time be more careful and fully understand what you are doing before doing it otherwise you will end up with a £600 paperweight.

dr9722 said:
If you would have spent 10 seconds looking in the Dev thread you would have found a list of all the available RUU's to download.
(http://forum.xda-developers.com/showthread.php?t=1543604)
Download your required RUU, boot into Fastboot-USB and run.
Next time be more careful and fully understand what you are doing before doing it otherwise you will end up with a £600 paperweight.
Click to expand...
Click to collapse
That is why I started this thread!!! I don't know which is the correct one!!! I started on o2 uk rom and then flashed android revolution!!!

You've just answered your own question - look for the RUU with o2 UK in the name...

stevepork said:
That is why I started this thread!!! I don't know which is the correct one!!! I started on o2 uk rom and then flashed android revolution!!!
Click to expand...
Click to collapse
Flash the one that says o2 UK then?
Though I also wonder. How do you match CID to the firmware package? When I try to get my CID in fastboot or w/e, it says no CID like i've read around here. Any thoughts?

EddyOS said:
You've just answered your own question - look for the RUU with o2 UK in the name...
Click to expand...
Click to collapse
i unlocked the bootloader so if the op did the same their CID will be "none" and therefore the RUU wont flash.

treebill said:
i unlocked the bootloader so if the op did the same their CID will be "none" and therefore the RUU wont flash.
Click to expand...
Click to collapse
Ahh, that is what I did. Does anyone know how to get around this or relock it. I understood that when you relock it, the CID doesnt change

stevepork said:
Ahh, that is what I did. Does anyone know how to get around this or relock it. I understood that when you relock it, the CID doesnt change
Click to expand...
Click to collapse
You can't get around it nor you can change the CID unless we get S-OFF.

shadowboy23 said:
You can't get around it nor you can change the CID unless we get S-OFF.
Click to expand...
Click to collapse
Okay, I guess i will have to wait until the clockwork recovery gets USB mount!

Sorry but if you just want to return to stock you can do
1. Restore you nandroid backup, flash stock recovery and then relock the bootloader.
OR
2. You can flash stock recovery, relock bootloader and then run the RUU that corresponds to your CID/region.

I am probably answering my own question my CID is H3G_001. There doesnt appear to a 3 mobile ruu at all. Any help here? Fortunately its not urgent but may be handy if/when they release the upgrade

oisindubh said:
I am probably answering my own question my CID is H3G_001. There doesnt appear to a 3 mobile ruu at all. Any help here? Fortunately its not urgent but may be handy if/when they release the upgrade
Click to expand...
Click to collapse
Is your ROM the O2 UK?
Ooops sorry about that.

shadowboy23 said:
Sorry but if you just want to return to stock you can do
1. Restore you nandroid backup, flash stock recovery and then relock the bootloader.
OR
2. You can flash stock recovery, relock bootloader and then run the RUU that corresponds to your CID/region.
Click to expand...
Click to collapse
Thank you, very much. That was all I needed. Why does everyone have to bee rude? Be kine to a newbie!! I have only had an iPhone and a Dell Streak before this device!

You have to relock the bootloader to flash the RUU
Sent from my HTC Sensation Z710e using xda premium

how are you guys checking CID?
Using terminal emulator? do you need root?
I tried ADB shell command since the fastboot command doesn't work, and I get error:device not detected

pewpewbangbang said:
how are you guys checking CID?
Using terminal emulator? do you need root?
I tried ADB shell command since the fastboot command doesn't work, and I get error:device not detected
Click to expand...
Click to collapse
CID getter from the market.

I dont know, sorry. I do know though that mine came originally with 02 uk rom and that CID will only work with the one rom that came originally with your phone. It may be different for unlocked devices.
Thank you very much for everyone's help
Steven

[Q] How do I change my CID (and get EU RUU)

I have gotten myself a s-offed HTC One X from a local carrier with their firmware on it so I have no real hope of fast updates...
CIDgetter says in the top left I have CID of 11111111, yet going down to ro.aa.maincid says TELENZ001 - the carrier
Obviously I am s-offed and can get into the bootloader, how do I go about changing my CID and flashing a European RUU?

Have you tried just plugging in when in fastboot and running the RUU? If you really do have Super CID it'll just work

Sorry to ask this but have you contacted the guys in the s-off thread? They may be interested in hearing from you.
http://forum.xda-developers.com/showthread.php?t=1604300
Sent from my HTC One X using xda premium

Mind giving me a walk through guide Eddy? With a $600 toy I don't wanna mess anything up...
Will post in that thread badger and see if I can be of any use

Can you make a picture of the bootloader. To see what version HBOOT and radio you have. Maybe this is causing the issue.

P1n3apqlExpr3ss said:
Mind giving me a walk through guide Eddy? With a $600 toy I don't wanna mess anything up...
Will post in that thread badger and see if I can be of any use
Click to expand...
Click to collapse
Boot phone into fastboot, connect to PC, run RUU - not a lot else to do!
It'll either work or give you an error and reboot, with no changes made

Cid-11111111
hboot-0.43.0000
radio-1.1204.90.13

P1n3apqlExpr3ss said:
I have gotten myself a s-offed HTC One X from a local carrier with their firmware on it so I have no real hope of fast updates...
CIDgetter says in the top left I have CID of 11111111, yet going down to ro.aa.maincid says TELENZ001 - the carrier
Obviously I am s-offed and can get into the bootloader, how do I go about changing my CID and flashing a European RUU?
Click to expand...
Click to collapse
wawawawa!
Don't change your CID! a CID of 11111111 should be able to flash anything. SuperCID!
---------- Post added at 04:13 AM ---------- Previous post was at 04:12 AM ----------
Doombadger said:
Sorry to ask this but have you contacted the guys in the s-off thread? They may be interested in hearing from you.
http://forum.xda-developers.com/showthread.php?t=1604300
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Please!

Supaiku said:
wawawawa!
Don't change your CID! a CID of 11111111 should be able to flash anything. SuperCID!
Click to expand...
Click to collapse
I realise that ofcourse, its the maincid I want changing. I assume flashing the EU RUU will change that maincid?
On that note can anyone link me to the RUU I would want?
Oh and I did post in the s-off thread, skimmed through the pages since my post and no one seemed to say anything in regards to my post

P1n3apqlExpr3ss said:
I realise that ofcourse, its the maincid I want changing. I assume flashing the EU RUU will change that maincid?
On that note can anyone link me to the RUU I would want?
Oh and I did post in the s-off thread, skimmed through the pages since my post and no one seemed to say anything in regards to my post
Click to expand...
Click to collapse
Bump

P1n3apqlExpr3ss said:
Bump
Click to expand...
Click to collapse
If you have superCID then choose whatever RUU you want from HERE. It will not change your CID if you flash a particular RUU.

May I hook on to this.
My CID is O2__001. So I want to change it into 111111.
When I boot into fastboot and give 'fastboot oem writecid 11111111' it says:
FAILED (status read failed (Too many links).
I've tried different usb-ports, different usb-cables
Or is there another way to change the CID?
Bootloader is unlocked (HTCDev)
HBoot: 0.43.0000
Softwareversion is still 1.26.206.2, no updates available
Someone can help me?
Thanks in advance

almanbrother said:
May I hook on to this.
My CID is O2__001. So I want to change it into 111111.
When I boot into fastboot and give 'fastboot oem writecid 11111111' it says:
FAILED (status read failed (Too many links).
I've tried different usb-ports, different usb-cables
Or is there another way to change the CID?
Bootloader is unlocked (HTCDev)
HBoot: 0.43.0000
Softwareversion is still 1.26.206.2, no updates available
Someone can help me?
Thanks in advance
Click to expand...
Click to collapse
You can't without S-OFF, so you will only get updates from o2 or you can go custom

EddyOS said:
You can't without S-OFF, so you will only get updates from o2 or you can go custom
Click to expand...
Click to collapse
Thanks for your fast replay!
How do I change S-ON to S-OFF

You can't, and this is why the OP has a rare phone...
Go do some reading and you'll see why we can't get it

You're really fast! Thanks, I will search.

shadowboy23 said:
If you have superCID then choose whatever RUU you want from HERE. It will not change your CID if you flash a particular RUU.
Click to expand...
Click to collapse
Sorry for not just going ahead and flashing it but...
a) Do I need root/htcdev to flash? (im assuming not)
b) If I flash the EU RUU will I get OTA updates as theyre pushed out (im assuming so)
EddyOS said:
You can't, and this is why the OP has a rare phone..
Click to expand...
Click to collapse
Straight from HTC, that's why review phones sent out to media (at least in New Zealand) are also s-offd

P1n3apqlExpr3ss said:
Sorry for not just going ahead and flashing it but...
a) Do I need root/htcdev to flash? (im assuming not)
b) If I flash the EU RUU will I get OTA updates as theyre pushed out (im assuming so)
Straight from HTC, that's why review phones sent out to media (at least in New Zealand) are also s-offd
Click to expand...
Click to collapse
If you have S-OFF you don't have any need for HTCdev. Being superCID your phone can get OTA updates as long as you have stock recovery.

shadowboy23 said:
If you have S-OFF you don't have any need for HTCdev. Being superCID your phone can get OTA updates as long as you have stock recovery.
Click to expand...
Click to collapse
Thought that might be the case, as for flashing the RUU, is it the standard CWM way or with the fastboot files you mentioned in the video in your sig? Do the same instructions apply from it for me?

P1n3apqlExpr3ss said:
Thought that might be the case, as for flashing the RUU, is it the standard CWM way or with the fastboot files you mentioned in the video in your sig? Do the same instructions apply from it for me?
Click to expand...
Click to collapse
bump

Just got an M9 today and need some tips...

Hello everyone, I I just got an M9 at my local Telus store and I would like to be able to do everything with it like I am able to do with my M7, so I know I will need to use sunshine to get S-OFF and I would also like to be able to change everything from the rom to the kernel to the OS, everything, so I was just wondering if someone could let me know the best order to go about doing things, meaning should I do sunshine first then worry about flashing a recovery and all that, or should I do the recovery first so that I can backup the phones current state? The phone currently says this in the hboot screen:
*** LOCKED ***
LK-1.0.0.0000
OS-1.32.661.6
and this is what it says on the phones Setting-About-Software screen:
Android version
5.0.2
HTC Sense version
7.0
Like I mentioned before, it would probably be best if I can make a backup of the phones current state just in case there are any issues, so to do that I know I need a recovery, but do I need to do the HTC Dev unlocker before I can do so? or do I have to flash a recovery first before everything else?
Now, before anyone gets upset with me for asking these questions because they have most likely been asked 1000 times before, I am not asking to be spoon feed all the details step by step, I am just asking to be pointed in the right direction and asking for you guy's opinions on the best way to go about doing things so that I do them right the first time... So if anyone could please take a minute to help me out and get me pointed in the right direction then it would be greatly appreciated... thank you very much...

apaquette420 said:
So if anyone could please take a minute to help me out and get me pointed in the right direction then it would be greatly appreciated... thank you very much...
Click to expand...
Click to collapse
First thing you should do is unlock your bootloader. After that you can install twrp and flash supersu (most can be found here) Once you are rooted run sunshine. After that the sky is the limit. You will be free to flash anything and everything. I know because I've done it. If you want to convert to a developers edition there is a post here. Personally I do not use my stock recovery or system image backups to download ota's. I prefer to run an RUU and do fresh installs. Reason why is because I am constantly changing firmware and roms. A lot of roms are based on the WWE firmware.
let me know if you have any more questions

bigp951 said:
First thing you should do is unlock your bootloader. After that you can install twrp and flash supersu (most can be found here) Once you are rooted run sunshine. After that the sky is the limit. You will be free to flash anything and everything. I know because I've done it. If you want to convert to a developers edition there is a post here. Personally I do not use my stock recovery or system image backups to download ota's. I prefer to run an RUU and do fresh installs. Reason why is because I am constantly changing firmware and roms. A lot of roms are based on the WWE firmware.
let me know if you have any more questions
Click to expand...
Click to collapse
Thank you very much for the tips.. Do I use the HTC Dev website to unlock the bootloader? I seen a link in the dev thread that said Unlock bootloader without HTCDev(root required), but I bet that the HTCDev way is probably the best best. which did you use? I'm not at home right now so I will begin when I get home later on tonight and if I need anything else I will post back, plus I post back to say how everything goes.. Thanks again for help, it is very much appreciated...

apaquette420 said:
Thank you very much for the tips.. Do I use the HTC Dev website to unlock the bootloader? I seen a link in the dev thread that said Unlock bootloader without HTCDev(root required), but I bet that the HTCDev way is probably the best best. which did you use? I'm not at home right now so I will begin when I get home later on tonight and if I need anything else I will post back, plus I post back to say how everything goes.. Thanks again for help, it is very much appreciated...
Click to expand...
Click to collapse
I've used htcdev for all 2 out o 3 of my m9's. third one is a developer edition so it wasn't needed.
just note download mode is fastboot mode on the m9. htcdev says to boot to fastboot mode and if you do not know than you can waste hours trying to figure it out.

bigp951 said:
I've used htcdev for all 2 out o 3 of my m9's. third one is a developer edition so it wasn't needed.
just note download mode is fastboot mode on the m9. htcdev says to boot to fastboot mode and if you do not know than you can waste hours trying to figure it out.
Click to expand...
Click to collapse
lol I so would have gotten caught up on that lol thanks again man!!! will post back later on...

cool..let me know if you get stuck anywhere

Ok so I got the bootloader unlocked and TWRP installed, right now I am taking a backup of the phones current state just in case. Now I just need to flash the SuperSU beta from the link you provided and then run sunshine, after that I would like to flash the latest OS for my phone, but I am not sure which version to use, I think this one is correct http://forum.xda-developers.com/one-m9/development/firmware-red-t3097678 but I am not 100% sure, do you know if this is the correct latest version for my phone?
Also should I supercid my phone before updating the firmware by entering "fastboot oem writecid 11111111" while in download mode? because my cid is TELUS001 and I do not see that cid listed in the androidinfo.txt file that is in the firmware zip...
Thanks again for all your help...
**UPDATE** I now have S-OFF, I can't believe how smooth the whole process is now with sunshine compared to almost all of my other HTC phones, hats off to those guys for sure... Thank you very much for getting me this far!!! I appreciate it very much...

apaquette420 said:
Ok so I got the bootloader unlocked and TWRP installed, right now I am taking a backup of the phones current state just in case. Now I just need to flash the SuperSU beta from the link you provided and then run sunshine, after that I would like to flash the latest OS for my phone, but I am not sure which version to use, I think this one is correct http://forum.xda-developers.com/one-m9/development/firmware-red-t3097678 but I am not 100% sure, do you know if this is the correct latest version for my phone?
Also should I supercid my phone before updating the firmware by entering "fastboot oem writecid 11111111" while in download mode? because my cid is TELUS001 and I do not see that cid listed in the androidinfo.txt file that is in the firmware zip...
Thanks again for all your help...
**UPDATE** I now have S-OFF, I can't believe how smooth the whole process is now with sunshine compared to almost all of my other HTC phones, hats off to those guys for sure... Thank you very much for getting me this far!!! I appreciate it very much...
Click to expand...
Click to collapse
I was actually just going to tell you to type
Code:
fastboot getvar all
while in download mode and to copy and paste that into a file a text file somewhere so you always have it. then you can supercid. I actually have never seen any firmware for your carrier. what is your mid? this is where I get all of my firmware from. I learned how to remove the red text using hex editor and I also throw in a custom splash screen before I flash.
Here is a link for your stock firmware. not sure what the most up to date is but most custom roms are using the WWE firmware anyways.
p.s. either quote me or tag me if you need a faster response. I'm not getting notifications otherwise.

bigp951 said:
I was actually just going to tell you to type
Code:
fastboot getvar all
while in download mode and to copy and paste that into a file a text file somewhere so you always have it. then you can supercid. I actually have never seen any firmware for your carrier. what is your mid? this is where I get all of my firmware from. I learned how to remove the red text using hex editor and I also throw in a custom splash screen before I flash.
Click to expand...
Click to collapse
My mid is 0PJA11000 but the one that is listed in the androidinfo.txt file of the firmware that I linked earlier is 0PJA10000, does this mean I cant use it? in all I plan to flash ViperOneM9 3.5.0 for the rom and it says it requires 2.10 but my phone is currently at 1.32

apaquette420 said:
My mid is 0PJA11000 but the one that is listed in the androidinfo.txt file of the firmware that I linked earlier is 0PJA10000, does this mean I cant use it?
Click to expand...
Click to collapse
I honestly don't know if the hardware is any different but it looks like your mid is the same as the dev ed. check this one out. @clsA is very knowledgeable on the m9. I learned a lot of what I know from his posts.
Personally I have gotten so relaxed that I just change my mid and cid to whatever it is I want to flash and just go for it. But I also understand that I'm risking a brick by doing so..lol

bigp951 said:
I honestly don't know if the hardware is any different but it looks like your mid is the same as the dev ed. check this one out. @clsA is very knowledgeable on the m9. I learned a lot of what I know from his posts.
Personally I have gotten so relaxed that I just change my mid and cid to whatever it is I want to flash and just go for it. But I also understand that I'm risking a brick by doing so..lol
Click to expand...
Click to collapse
took a look at the thread and it looks like all I need to do to flash 2.10 which is the international version is type fastboot oem writemid 0PJA10000 while in downloader mode because like you said and which I also confirmed in the other thread that my phone is the same as the dev ed and I should be able to switch back and forth with the same command

apaquette420 said:
took a look at the thread and it looks like all I need to do to flash 2.10 which is the international version is type fastboot oem writemid 0PJA10000 while in downloader mode because like you said and which I also confirmed in the other thread that my phone is the same as the dev ed and I should be able to switch back and forth with the same command
Click to expand...
Click to collapse
If going to dev ed I have had better luck running an RUU and accepting ota's as far as the radio goes. my reception went from 2 bars to full bars doing it that way verses just flashing the newest firmware. But it is a very long and tedious process and since you just got your m9 I'm sure you want to use it already..
What rom are you thinking about flashing?

bigp951 said:
If going to dev ed I have had better luck running an RUU and accepting ota's as far as the radio goes. my reception went from 2 bars to full bars doing it that way verses just flashing the newest firmware. But it is a very long and tedious process and since you just got your m9 I'm sure you want to use it already..
What rom are you thinking about flashing?
Click to expand...
Click to collapse
I am hoping to flash ViperOneM9 3.5.0, it was the only rom I ran on my M7 and I loved it, so I'm really hoping to have it on this phone too... I just asked in the roms thread to see if anyone else there is on my same network to see how they got it working... and to be honest I don't mind waiting in order to get things done the right way the first time, know what I mean...

apaquette420 said:
I am hoping to flash ViperOneM9 3.5.0, it was the only rom I ran on my M7 and I loved it, so I'm really hoping to have it on this phone too... I just asked in the roms thread to see if anyone else there is on my same network to see how they got it working... and to be honest I don't mind waiting in order to get things done the right way the first time, know what I mean...
Click to expand...
Click to collapse
Viper is one of my favorites. Was using it for months. They are good about replying too... A little too good because you get spoiled. Then when you post on other roms and nobody ever replies you realize how good those guys are..haha
check out the second line on this thread to reclaim 3 gb of data after using sunshine. I've been s-off for months and just saw this today.

bigp951 said:
Viper is one of my favorites. Was using it for months. They are good about replying too... A little too good because you get spoiled. Then when you post on other roms and nobody ever replies you realize how good those guys are..haha
check out the second line on this thread to reclaim 3 gb of data after using sunshine. I've been s-off for months and just saw this today.
Click to expand...
Click to collapse
do you know where I can find the latest international RUU? what rom are you running now?

@bigp951
Ok so I got the firmware updated to the latest international version 2.10 and was able to flash the ViperOne Rom and I love it just like I did for my M7... Everything is working great, except I have the problem that you mentioned would happen, I only show 1 bar for my signal strength, could you please let me know exactly what you had to do to fix it? Also, I would just like to say thank you once more, you helped me out a great deal and you made my upgrade to the M9 an absolute cake walk, so thank you very much for everything and for explaining the proper steps to take, I appreciate it very much...

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

boot loader . .

How do I unlock the boot loader when there is no oem setting to allow unlocking the boot loader in developer options? I have the token the phone is running marshmallow. It is S off and has CID 11111111. One thing can I flash TWRP to my phone without messing with the boot loader. If so then I can just use TWRP to flash the model ID and EU RRU thanks in advance. Just read I cannot flash TWRP without unlocking the boot loader.

jconradb said:
How do I unlock the boot loader when there is no oem setting to allow unlocking the boot loader in developer options? I have the token the phone is running marshmallow. It is S off and has CID 11111111. One thing can I flash TWRP to my phone without messing with the boot loader. If so then I can just use TWRP to flash the model ID and EU RRU thanks in advance. Just read I cannot flash TWRP without unlocking the boot loader.
Click to expand...
Click to collapse
I'm not sure what your exact situation is but i don't think OEM unlocking through Settings is an option. Have you tried this ... See link below
https://forum.xda-developers.com/showthread.php?t=2708571

Aimless Rambler said:
I'm not sure what your exact situation is but i don't think OEM unlocking through Settings is an option. Have you tried this ... See link below
https://forum.xda-developers.com/showthread.php?t=2708571
Click to expand...
Click to collapse
Yes my comment is vague, I want to unlock my boot loader but cannot. All settings on the M8 are set such as USB debugging and I have the unlocking code from HTC. When I proceed to unlock the phone and choose option to unlock the phone, phone reboots but the boot loader is still locked. On the HTC web site it states with Marshmallow this can happen and you must go to developers options and highlight OEM option to unlock the boot loader but the option is not there and I'm stuck. Thank you for your reply

Did you try fastboot oem unlock? If it's soff and supercid, should be all that is needed

miffymiffy said:
Did you try fastboot oem unlock? If it's soff and supercid, should be all that is needed
Click to expand...
Click to collapse
Thank you so much I will try that later today and get back to you. Again thanks for the reply ?

miffymiffy said:
Did you try fastboot oem unlock? If it's soff and supercid, should be all that is needed
Click to expand...
Click to collapse
Far as I know, this will not work.
May need to use the following method (if unlock token doesn't work) and root is also required:
https://forum.xda-developers.com/showthread.php?t=2708571
---------- Post added at 12:27 PM ---------- Previous post was at 12:16 PM ----------
jconradb said:
If so then I can just use TWRP to flash the model ID and EU RRU thanks in advance. Just read I cannot flash TWRP without unlocking the boot loader.
Click to expand...
Click to collapse
It is correct, you cannot flash TWRP with a locked bootloader (needs to be unlocked) by definition.
But you also don't flash an RUU in TWRP. You also may not need to change the MID, depending on what version you have.
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting). Need to verify some details before supplying advice, which may be harmful to your device.

redpoint73 said:
Far as I know, this will not work.
May need to use the following method (if unlock token doesn't work) and root is also required:
https://forum.xda-developers.com/showthread.php?t=2708571
---------- Post added at 12:27 PM ---------- Previous post was at 12:16 PM ----------
It is correct, you cannot flash TWRP with a locked bootloader (needs to be unlocked) by definition.
But you also don't flash an RUU in TWRP. You also may not need to change the MID, depending on what version you have.
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting). Need to verify some details before supplying advice, which may be harmful to your device.
Click to expand...
Click to collapse
Here you go and thanks

jconradb said:
Here you go and thanks
Click to expand...
Click to collapse
What RUU are you trying to run, and how exactly (command syntax, etc.)?
Are you actually getting a model ID error when running the RUU?

redpoint73 said:
What RUU are you trying to run, and how exactly (command syntax, etc.)?
Are you actually getting a model ID error when running the RUU?
Click to expand...
Click to collapse
I want to change to EU RUU so as I understand I must change model id as mine is developer model id as is my RUU. Plus rooting would be nice

jconradb said:
I want to change to EU RUU
Click to expand...
Click to collapse
I should have been more specific. What RUU number, and where did you get it from?
jconradb said:
I want to change to EU RUU so as I understand I must change model id as mine is developer model id as is my RUU.
Click to expand...
Click to collapse
Your model ID (MID) is for AT&T and Developer's Edition.
You may or may not need to change the MID, in order to run the Euro RUU. Sometimes (often) having SuperCID (11111111) will bypass the MID check for RUUs. So I would suggest running the RUU, and see if it gives you model ID error, or if it just work (before messing with the MID, if you don't have to).

redpoint73 said:
I should have been more specific. What RUU number, and where did you get it from?
Your model ID (MID) is for AT&T and Developer's Edition.
You may or may not need to change the MID, in order to run the Euro RUU. Sometimes (often) having SuperCID (11111111) will bypass the MID check for RUUs. So I would suggest running the RUU, and see if it gives you model ID error, or if it just work (before messing with the MID, if you don't have to).
Click to expand...
Click to collapse
Actually this whole thing started when I installed the developer RUU on the phone. After this I noticed when I launched the camera a message came that the lens is blocked. I think it's a RUU issue. You see the RUU I had before which was Kit Kat camera worked but many other issues. The marshmallow RUU was downloaded from a member of this forum forget his name

jconradb said:
Actually this whole thing started when I installed the developer RUU on the phone. After this I noticed when I launched the camera a message came that the lens is blocked. I think it's a RUU issue.
Click to expand...
Click to collapse
Unlikely an issue with the RUU itself. I was on the Dev Edition RUU for a while (as have many others), and the camera worked fine. But it's not a bad idea to try the Euro RUU, and see if that helps.
jconradb said:
The marshmallow RUU was downloaded from a member of this forum forget his name
Click to expand...
Click to collapse
Wow, that is remarkably vague. The file doesn't have a version number, or name? Not providing any useful info, forces us to guess. Lucky for you, I have a pretty good guess.
Try the following Euro RUU, and instructions:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Alternately, if you have an SD card, rename the RUU zip to 0P6BIMG.zip put the file on the SD card, insert in phone, and reboot to bootloader, and it should install automatically.
Let us know if it installs, or if you get error messages (and what the error messages are, specifically).

redpoint73 said:
Unlikely an issue with the RUU itself. I was on the Dev Edition RUU for a while (as have many others), and the camera worked fine. But it's not a bad idea to try the Euro RUU, and see if that helps.
Wow, that is remarkably vague. The file doesn't have a version number, or name? Not providing any useful info, forces us to guess. Lucky for you, I have a pretty good guess.
Try the following Euro RUU, and instructions:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Alternately, if you have an SD card, rename the RUU zip to 0P6BIMG.zip put the file on the SD card, insert in phone, and reboot to bootloader, and it should install automatically.
Let us know if it installs, or if you get error messages (and what the error messages are, specifically).
Click to expand...
Click to collapse
Ckpv5 was his name on this forum he uploaded the file

jconradb said:
Ckpv5 was his name on this forum he uploaded the file
Click to expand...
Click to collapse
So to do your install I can do this with the standard recovery and model id I have

jconradb said:
So to do your install I can do this with the standard recovery and model id I have
Click to expand...
Click to collapse
Recovery doesn't matter for RUU install, it will be overwritten by stock recovery regardless of what is presently there.
Model ID is what I mentioned before. The RUU may or may not work with your MID. If it fails with model ID error, we know we need to change the MID. If it works, then it works.

redpoint73 said:
Recovery doesn't matter for RUU install, it will be overwritten by stock recovery regardless of what is presently there.
Model ID is what I mentioned before. The RUU may or may not work with your MID. If it fails with model ID error, we know we need to change the MID. If it works, then it works.
Click to expand...
Click to collapse
Hello I am worried to flash the RUU because I tried to change the mid to EU using adb she'll message permission denied oem blocked, stupid at&t

jconradb said:
Hello I am worried to flash the RUU because I tried to change the mid to EU using adb she'll message permission denied oem blocked, stupid at&t
Click to expand...
Click to collapse
AT&T has nothing to do with it, it's not what "oem blocked" means. This is probably pilot error. Do you have root, since it's required to change the MID?
And you are not following my advice why, because of some assumed or imagined fear that isn't based on any fact? Flashing the RUU with the wrong MID is not going to harm the device. The worst that will happen is an error message (wrong model) and the RUU will not install. The phone remains exactly as it was before you tried the RUU. And meaning you have to change the MID to run the RUU.
Best case, the RUU works, and you no longer have to mess with changing the MID.

redpoint73 said:
AT&T has nothing to do with it, it's not what "oem blocked" means. This is probably pilot error. Do you have root, since it's required to change the MID?
And you are not following my advice why, because of some assumed or imagined fear that isn't based on any fact? Flashing the RUU with the wrong MID is not going to harm the device. The worst that will happen is an error message (wrong model) and the RUU will not install. The phone remains exactly as it was before you tried the RUU. And meaning you have to change the MID to run the RUU.
Best case, the RUU works, and you no longer have to mess with changing the MID.
Click to expand...
Click to collapse
OK I will follow your advice thank you for your time and effort

redpoint73 said:
AT&T has nothing to do with it, it's not what "oem blocked" means. This is probably pilot error. Do you have root, since it's required to change the MID?
And you are not following my advice why, because of some assumed or imagined fear that isn't based on any fact? Flashing the RUU with the wrong MID is not going to harm the device. The worst that will happen is an error message (wrong model) and the RUU will not install. The phone remains exactly as it was before you tried the RUU. And meaning you have to change the MID to run the RUU.
Best case, the RUU works, and you no longer have to mess with changing the MID.
Click to expand...
Click to collapse
OK let's assume this RUU works will try tomorrow I think. How would I root this phone remembering the issues to unlock the boot loader. The unlock code did not work because of the oem option missing developer

jconradb said:
OK let's assume this RUU works will try tomorrow I think. How would I root this phone remembering the issues to unlock the boot loader. The unlock code did not work because of the oem option missing developer
Click to expand...
Click to collapse
oem unlocking being "missing" is not the problem. It wasn't on most OS builds for the M8, and was only added later. In fact, I'm not sure it was ever present on this device (or maybe just some versions). If it's not there, you don't need to enable it. Unlocking the bootloader should work normally.
So clearly, something is wrong, if you are doing the bootloader unlock, and it doesn't work. Let's try to run the RUU, and go from there.