Develop Bugs

Problems with Wifi [Not scanning]

Hi guys,
This is my first thread here in XDA, so, forgive me by a possible mistake.
I recently bought a HOX, the seller said that is the international version.
I'm in 4.0.3, with software version 1.29.707.11 (already checked for updates, but phone says its up to date)
So, sometimes when i turn my wifi on, he doesn't connect in my network (already saved), i go to wifi settings, put to scan, and, aparently, the phone don't scan the networks and doesn't found my network too.
Obviously, im on the range of the network, and don't have that factory problem with bad wifi signal.
And, sometimes too, phone takes a lot of time to get carrier signal, so i turn on plane mode, then turn off, and finally get carrier signal.
My question is: is this normal? What can i try to fix it? (Thinked on a factory reset)
I don't tried anything yet.
If anyone could help, i'll appreciate and if the thread is on the wrong place, please move it

Just try flashing the RUU, which will delete everything and return it to stock.

BenPope said:
Just try flashing the RUU, which will delete everything and return it to stock.
Click to expand...
Click to collapse
Thanks for the help Pope!
I am VERY noob in HTC tools, can you say me what exactly is this "RUU", and where i can get it?
Its basically, a factory reset right? What is the difference from normal FR to this RUU tool?

lock! said:
Thanks for the help Pope!
I am VERY noob in HTC tools, can you say me what exactly is this "RUU", and where i can get it?
Its basically, a factory reset right? What is the difference from normal FR to this RUU tool?
Click to expand...
Click to collapse
The difference is that it will reflash the ROM from scratch, it's the first thing HTC do when you take your phone for repair. It's very safe (when flashed with decent remaining battery) and very thorough.
Check the Shipped ROM sticky in the development section.

I am searching about the Rom Update Utility, but i'm not finding a good tutorial to follow, explaining the whole process.
If anyone could help me in the process :laugh:
Edit:
Thanks again Pope! I'll look in dev section

You just have to charge the phone, put the phone in fastboot mode (hold down the volume down key when switching on the phone, then navigate from there), plug phone into Windows PC and double click RUU.
You may want to do an "adb backup" (you'll have search for this) beforehand, flash RUU, test and then restore.

BenPope said:
You just have to charge the phone, put the phone in fastboot mode (hold down the volume down key when switching on the phone, then navigate from there), plug phone into Windows PC and double click RUU.
You may want to do an "adb backup" (you'll have search for this) beforehand, flash RUU, test and then restore.
Click to expand...
Click to collapse
I'm not finding the correct RUU file for the One X, can you help me? Or just show me a place to search... (Some links here at job are blocked --') Basically finding the correct RUU file i'll do the rest without problem...
This "restore" you mean in the end, its the factory reset in the phone? Or another restore?
Don't need a backup, i got the phone 2 days ago hehehe

My HOX is totally clean.
No unlocked bootloader, no root.
This will not be a problem doing the flash with the stock RUU right?

lock! said:
My HOX is totally clean.
No unlocked bootloader, no root.
This will not be a problem doing the flash with the stock RUU right?
Click to expand...
Click to collapse
No, that's perfect, you don't need anything other than stock, and it will remain stock.
http://www.filefactory.com/file/5c0...Radio_1.1204.105.14_release_260743_signed.exe

BenPope said:
No, that's perfect, you don't need anything other than stock, and it will remain stock.
http://www.filefactory.com/file/5c0...Radio_1.1204.105.14_release_260743_signed.exe
Click to expand...
Click to collapse
Ben sorry for tons of questions hehe
I'm reading a tutorial, and on it said that i need my CID number, in order to download the correct RUU file for the correct region of my HOX. How can i know if this RUU you posted is the correct for my HOX?
I've tried to get my CID number (downloaded the fastboot flasher tool) but when i put the cid command he returns: CID > None lol
I Know that my HOX is from Shangai (has a SH in serial number) and got my MID number.
So, i just need to know which file i need to download, the right one of course hehehe
If i will need the CID to know, i'll ask for the files for fastboot commands (i don't found them)
If not, just confirm the link you posted ealier if its the correct RUU for my case.
PS.: This link posted is only for premium users, and i don't have a premium acc, can you provide in another mirror?

You can't flash the wrong RUU, the phone won't let you.
You don't need your CID as you are not unlocked, knowing that you are 1.29.707.x is enough. It's the right RUU.
I'm sure you don't need me to hold your hand whilst you use google to find that file somewhere else. The sticky dev thread I previously mentioned will likely have a ton of mirrors for the file.

So.. i'll look fot the file in other places.
Today, i've connected in my wifi network, and the phone says there's an update...
It's the same update announced days ago, but in my case with a different update number...
Phone has been upgraded to ICS 4.0.4 and Sense 4.1.
If the problems persist, i will flash the RUU anyway, but, because of this update, nothing changes right? The RUU file you posted still valid for my HOX?

Not any more, you've updated your hboot, so you'll need an updated RUU (you can't install on older hboot, packaged with an older RUU).
You're lucky:
http://www.filefactory.com/file/3rc...Radio_2.1204.135.20_release_278245_signed.exe
and
http://forum.xda-developers.com/showpost.php?p=30273253&postcount=1724

BenPope said:
Not any more, you've updated your hboot, so you'll need an updated RUU (you can't install on older hboot, packaged with an older RUU).
You're lucky:
http://www.filefactory.com/file/3rc...Radio_2.1204.135.20_release_278245_signed.exe
and
http://forum.xda-developers.com/showpost.php?p=30273253&postcount=1724
Click to expand...
Click to collapse
HELL YEAH!
I'll test for 2 ~ 3 days, if i note the same problem i'll flash it!
Thanks for all the help Pope!

With this 707 update I got better WiFi ..smooth, fast...amazing
Sent from my HTC One X using XDA Premium HD app

dragonesdenano said:
With this 707 update I got better WiFi ..smooth, fast...amazing
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Same here man...
In a network that once stood in 40% signal, now i'm getting almost 100%!
Apparently, carrier signal is working fine too.. i'll test for more 3 days...

no easy access or UI after deleting internal storage (newbie)

Hi,
Here's my story: I have a factory unlocked M9 bought in Belgium. After reading in XDA, I unlocked the loader, and install TWRP (2.8.5.0). I then made a backup and installed ARHD 5.2.
Everything worked fine, until I decided to sell my device (I live in Argentina, and although I bought the international version, it does not cover 4G band 4). So in order to sell it I wanted to wipe everything back to factory settings. I went ahead and restore my backup. Again everything worked flawlessly, but then I saw some folders in the internal storage that were not supposed to be there (such as maildroid folder, among others). So I went back to TWRP, wipe, advanced, "delete internal SD". oops, wrong choice...
I rebooted and then notices appeared "Unfortunately UI has stopped..../ unfortunately easyaccess has stoped...", losing all functionalities (no touch buttons, I had to restart every time I wanted to change menus).
I restored again the backup...no luck. I then installed again AR 5.2...no luck.
I wanted to RUU (I am not sure I know what it is, but I do know how to follow step by step guides...well at least sometimes...). my phone is S-ON. I tried installing sunshine to S-OFF, but I got the message "No SD card", so it wouldn't let me install it. in fact when I use the HTC file explorer it looks as if there is nothing in the internal storage.
I don't think I can fastboot (USB not recognized). I read that phones needed to be S-OFF ( http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545 ), so I don't know what else to do.
I really tried all related posts but I can't find the answer....
Any help is really appreciated (of course I couldn't sell the phone). Thanks.

A RUU is a Rom Update Utility. It's a little program made by HTC to reinstall a stock firmware and/or rom on a phone that is S-ON. Depending on the build number and the CID of your phone the needed RUU is an *.exe or a *.zip.
Are you still able to enter Settings>About>Software Information>More? (Not completely sure whether these are the correct english terms. On my phone it's Einstellungen>Info>Software-Informationen>Mehr.) There you can find the build number of the installed firmware if you are on stock rom.
Otherwise you need to boot into download mode where you can find the build number (written in the line with "OS" at the beginning) and the CID of your phone. Since you never mentioned any branding and you bought the phone in Belgium I'm assuming that the CID is something like HTC__*** and that you can use a European RUU.
Next you need to download the corresponding RUU for your build number (just use Ctrl+F for easier searching) and your CID. Since the CID isn't explicitly mentioned in the RUU names you may have to search for the meaning of your phones CID (for example in a list like this one).
If the needed RUU is a *.zip then you have to rename the file to 0PJAIMG.zip (that's a zero not an O), copy it on an external sd card that is not bigger than 32gb and formatted to fat32 and put the sd card into your phone. If you now enter download mode your phone should guide you through the rest of the procedure.
If the needed RUU is an *.exe then you just have to connect you phone to your pc and start the file (on windows).

Flippy498 said:
Are you still able to enter Settings>About>Software Information>More? (Not completely sure whether these are the correct english terms. On my phone it's Einstellungen>Info>Software-Informationen>Mehr.) There you can find the build number of the installed firmware.
Click to expand...
Click to collapse
I had access, the build number is 1.32.401.17 CL506785 release keys. However from download mode I got Mainversion: 1.32.401.15. So I guess I have to use the latter right? I do not need to be S-OFF, because I can't make it....
Flippy498 said:
Then you need to downlad the corresponding RUU (just use Ctrl+F and enter the build number for easier searching), rename it to 0PJAIMG.zip (that's a zero not an O), copy it on an external sd card that is not bigger than 32gb and formatted to fat32. If you put this sd card into your phone and enter download mode your phone should guide you through the rest of the procedure.
Click to expand...
Click to collapse
Ok there are two 1.32.401.15 version for Europe,that only differs in the release: Which should I use
1. 0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_426891_signed.zip
2. 0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R2_Radio_01.01_U11440261_56.02.50306G_2_F_release_427846_signed.zip
Flippy498 said:
Edit2: I forgot another important thing. (Sorry, I'm in a little hurry right now.) Your CID needs to correspond to the RUU you want to run. Since you never mentioned any branding I'm assuming that it is something like HTC__*** so that you can use a European RUU. You can find out by booting into download mode. (I'm not completely sure whether it's written there if you are S-ON. If not you can either try using an app like CID Getter or the fastboot command "fastboot getvar all".) If your CID differs from HTC__*** I would suggest you to post it here together with the build number so that it's easier for me or someone else to guide you to the correct RUU.
Click to expand...
Click to collapse
I cannot install anything as the internal storage is not recognized by the OS. However I was able to fastboot:
OS-1.32.401.15
HTC__031
Kernel: lk
Thank you for your help!

gsember said:
I had access, the build number is 1.32.401.17 CL506785 release keys. However from download mode I got Mainversion: 1.32.401.15. So I guess I have to use the latter right? I do not need to be S-OFF, because I can't make it....
Click to expand...
Click to collapse
I think that the original stock was 1.32.401.15 as ARHD 5.2 that I flashed comes with the 1.32.401.17

Yes, that's right. Since there has not been an aboot update until now you can also try to install the 1.32.401.8 RUU and then update via the stock OTA function. I've done this with my phone before I got S-OFF so I know that it works. This way you can be sure that the correct version of the 401.15 firmware gets installed.

Flippy498 said:
Yes, that's right. Since there has not been an aboot update until now you can also try to install the 1.32.401.8 RUU and then update via the stock OTA function. I've done this with my phone before I got S-OFF so I know that it works. This way you can be sure that the correct version of the 401.15 firmware gets installed.
Click to expand...
Click to collapse
Ok, I already installed the first release of 1.32.408.15. it worked flawlessly. Should I relock (or lock) the phone to receive OTA?
Use a 32 GB card tip saved my day! ( I had a 128 GB which the phone didn't read)
Thank you all.

I am now trying the second release as the first one did not recognize 5G wifi networks.
Is it possible to receive OTA once you have an unlocked bootloader? XX.15 is the latest version? because ARHD has XX.17?
thanks again

Actually I don't know whether it's necessary to relock the bootloader if you want to install an OTA but I would guess it is. The 401.15 version is the latest European one. 401.17 is only receivable on HTC__J** but llabtoofer stated on his twitter account that the next European update is waiting around the corner.
You mentioned earlier that you cannot connect your phone with your PC and that fastboot isn't working. Did you try to connect your phone to another PC/Laptop (maybe your parents/siblings/friends can help you out if you don't own another one)? As far as I know there is no way to relock bootloader without a PC.

Flippy498 said:
Actually I don't know whether it's necessary to relock the bootloader if you want to install an OTA but I would guess it is. The 401.15 version is the latest European one. 401.17 is only receivable on HTC__J** but llabtoofer stated on his twitter account that the next European update is waiting around the corner.
You mentioned earlier that you cannot connect your phone with your PC and that fastboot isn't working. Did you try to connect your phone to another PC/Laptop (maybe your parents/siblings/friends can help you out if you don't own another one)? As far as I know there is no way to relock bootloader without a PC.
Click to expand...
Click to collapse
Thanks. Everything is working smoothly. Actually fastboot is working. I won't continue to play.....
Appreciate your answers

Returning to stock issues.

I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!

Webbage said:
I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!
Click to expand...
Click to collapse
You don't provide much information so it's hard to help. So let's start at the bginning: What firmare version are you using? (It's stated in Download Mode in the line with "OS" at the beginning.)
You tried to flash a RUU? Which one? Have there been any error outputs? If yes, which ones? Since you're S-OFF flashing a RUU should not be a problem at all so these outputs are very important if you want any help.

I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?

Webbage said:
I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?
Click to expand...
Click to collapse
As far as I know Sneakyghost doesn't provide any RUUs. Those are only firmware packages that do not contain a rom. So it's no miracle that you're still booting ARHD.
You can download O2 RUUs from here, here or here. Any of the X.XX.206.X files will work since you are S-OFF. Do you have a SD card that is not bigger than 32gb? If yes, format it to fat32, copy one O2 RUU to its root directory and rename that file to "0PJAIMG.zip". If you then boot to Download Mode you will be asked to push the Volume Up button and the RUU will start flashing. If it reboots to system instead of rebooting to Download Mode you will have to power off your phone and boot to Download Mode manually. The RUU will continue then. At the end you will be asked to push the power button so that your phone gets shut down. If you now start your phone you will be back on a stock system.
Be aware that there is no RUU for your current firmware. Since you're S-OFF that doesn't matter but your phone will be downgraded at the end.

Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?

Webbage said:
Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?
Click to expand...
Click to collapse
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...

Agreed, use the s-off command to change back to "LOCKED" and leave it s-off. Too much of a risk otherwise.
If in the unlikely event they see it, you can play dumb, because a few rare people have gotten s-off phones from the factory and it doesn't prove you did anything.

Flippy498 said:
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...
Click to expand...
Click to collapse
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?

Webbage said:
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?
Click to expand...
Click to collapse
Didn't the RUU flash the corresponding stock recovery?

Flippy498 said:
Didn't the RUU flash the corresponding stock recovery?
Click to expand...
Click to collapse
My bad, I didn't check.
All sorted now, thanks again bud!

Bricked HTC One M8

Hi
Please can anyone help please?
Got a HTC One M8 on o2. I installed a custom rom (Viper One) and used it fine for over a year.
I've since changed to a S6 edge and wanted to revert my old phone back to stock rom unrooted.
In doing so I messed up!!!
I'm now stuck with a handset, everything wiped (including the operating system and backups)
I have TWRP recovery and need to re-install stock rom.
Can anyone help?
Thank you

This section is absolutely filled with the same question.
Have a GOOD read here
http://forum.xda-developers.com/showthread.php?t=3086860

Ah right sorry, thanks... Will check it out

bah77 said:
I'm now stuck with a handset, everything wiped (including the operating system and backups)
Click to expand...
Click to collapse
If I'm understanding you correctly, you wiped the OS, not realizing it would cause your phone to be without . . . an operating system?

NO, the operating was wiped by accident

bah77 said:
NO, the operating was wiped by accident
Click to expand...
Click to collapse
Well the easiest way without going through any hassle to fix your phone and make it Stock/Like Brand New is to run a RUU.
I will explain how to do this process with a PC and you should be good to go :good:
1. Download HTC drivers for your PC if you haven't already Here, install and uninstall HTC Sync Manager while KEEPING "HTC Driver Installer".
2. Download the RUU that best matches your phone Here, you can possibly find a O2 RUU on xda but I did not find one my self for you unfortunately, otherwise if your phone is a GSM variant phone you can flash the international RUU from Here (Instructions would be different in this case)
3. Get your phone into bootloader by TWRP or if your phone is off then hold down VOL DOWN and POWER BUTTON at the same time until HBOOT shows up.
4. Plug your device via USB into the computer and verify that you see "Fastboot USB" on your phone's screen.
5. Run the RUU .exe file, I recommend you "Run as Administrator".
6. Follow the on screen instructions and sit back 10-20 minutes as your phone becomes brand new, do not interupt the process or you could have a permanent phone brick.

bah77 said:
Ah right sorry, thanks... Will check it out
Click to expand...
Click to collapse
Is your problem fixed ? Do you still need a RUU for this ? Or the TWRP backup that you found in that link is good enough ?

Sorry not had time to try yet but hoping to in the next day or two
Thanks for the help guys, will let you know how i get on

bah77 said:
wanted to revert my old phone back to stock rom unrooted.
In doing so I messed up!!!
I'm now stuck with a handset, everything wiped (including the operating system and backups)
I have TWRP recovery and need to re-install stock rom.
Click to expand...
Click to collapse
Seems (from the vague description) that a few things went wrong:
1) You may have been proceeding without the proper knowledge of how to return to stock, and at least somewhat, "making it up" as you went along or "experimenting". This is not the proper way to go about things when modding (or in this case "unmodding") a phone. Stick to specific instructions and guides, as already pointed out the process to return to stock is well documented.
2) No degree of wiping or factory resets is going to restore a stock ROM, if you have a custom ROM installed (if that is what you were trying to do); which is a somewhat common misconception. Also, wiping things without understanding the result is a bad idea. The Wipe options are called "Advanced" for a reason. If you don't understand what it is (or the results of wiping it) than don't do it.
The process to return to working stock has been outlined by others. But if you want more specific help, you will need to do a getvar all and post the output (being sure to delete your IMEI and serial number, as those are personal info) so we can better determine the way forward. But in summary, you have 2 choices:
a) Relock the bootloader and run the proper RUU, of one exists for your CID version.
b) Restore the stock nandroid that corresponds to your CID and main version (firmware), then flash the correct corresponding stock recovery.

Been stuck like this for 40 minutes

bah77 said:
Been stuck like this for 40 minutes
Click to expand...
Click to collapse
What did you do ?
Do you have right RUU ? Can you give the RUU name that you are using ?
I saw you use a ROM.zip .. AFAIK your O2 RUU is an exe file.
You also need USB 2.0 and latest HTC USB Drivers installed.

Do i need to re lock the bootloader first?

Discussion has resumes here:
http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-brick-t3243115
Thread closed.

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