Help with installing AT&T Ruu - One (M8) Q&A, Help & Troubleshooting

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

Related

[SOLVED] T-Mobile M8 Stuck In Recovery With ReLocked Bootloader and No ROM!

The title basically says it all but I'll describe what I did so hopefully you guys can help.
Today I got tired of the ROM I was running and I figured I'd update my firmware before I flashed a new one just cause I hadn't done it in months. So I went and followed this guide: http://forum.xda-developers.com/showthread.php?t=2696282
I used this firmware: https://www.androidfilehost.com/?w=files&flid=32788
My CID is T-MOB010 just like the firmware's and I thought it would be a pretty simple thing, so I got to work.
First I rebooted to fastboot USB and did fastboot getvar all to make sure everything lined up, then I relocked the bootloader and did fastboot oem rebootRUU, all successfully.
Then I flashed the firmware and it all went great but I forgot to flash it a second time. I'm not sure if it's required, but anyway...
After it flashed successfully I did a fastboot reboot and my phone tried to reboot but it stalled on the white HTC splash screen, then went black, then the splash screen returned, then black, then it went into the stock recovery.
The stock recovery functions just fine and I attempted to just clear the cache and reboot but it did the exact same thing.
I don't currently have a stock Nandroid or RUU on my phone and I'm not even sure I have a way to get one on there besides using someone else's phone to put one on my SD.
Can anyone help me out? Is it even possible to get out of this? My bootloader is relocked and my phone can't get S-OFF (tried awhile ago multiple times). As of now I am all out of ideas/experience so I'm hoping you guys can help me. Thank you!!
UPDATE: I got myself into the HBOOT so I think I should be good now but I'll keep this around just in case.
Update: Once I got into hboot all was well, I just flashed TWRP again and got it going. Thanks everyone for the help!
Did you get it going again?
_jakeryan said:
I don't currently have a stock Nandroid or RUU on my phone
Click to expand...
Click to collapse
Just use the official RUU.exe which runs from a PC (with phone connected), not from the phone.
http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
RUU will also update your firmware.
Also, the firmware you linked is not the latest. Its the Android 4.4.4 firmware. The 5.0 (Lollipop) firmware would be 4.20.531.4
hack14u said:
Did you get it going again?
Click to expand...
Click to collapse
I did! Thank you redpoint for the help anyway!
_jakeryan said:
I did! Thank you redpoint for the help anyway!
Click to expand...
Click to collapse
Maybe add 'solved' to the topic? If that's still a thing.
_jakeryan said:
I did! Thank you redpoint for the help anyway!
Click to expand...
Click to collapse
Its not what your top post says, so its not clear whether you were trying to put the RUU.exe on the phone (which is incorrect), unsuccessful in putting on the phone or running an RUU.zip, or did the latter in addition to trying to run the RUU.exe from the PC (which was not originally mentioned). If the last one didn't work, it would help to have more details on failure mode, error messages, etc.
---------- Post added at 09:25 AM ---------- Previous post was at 09:23 AM ----------
_jakeryan said:
UPDATE: I got myself into the HBOOT so I think I should be good now but I'll keep this around just in case.
Click to expand...
Click to collapse
So is your issue resolve or not? Able to get a ROM or nandroid on the phone and flash/restore it?
---------- Post added at 09:26 AM ---------- Previous post was at 09:25 AM ----------
voidzero said:
Maybe add 'solved' to the topic? If that's still a thing.
Click to expand...
Click to collapse
Not everyone does it, but its certainly good to do, and still done from time to time. Its helpful so folks don't click on a link, intending to help someone that doesn't need the help anymore.
Same kinda problem.
I'm stuck in bootloader.
Any key I just brings me back to this again.
Even in HBOOT selecting Recovery or Factory reset does nothing other than bring up this screen.
Powering down and then on again has the same result.
I was trying to get back to stock. Typed in fastboot oem lock and after that... the problem started!!
Any ideas??
morgansgrandad said:
I'm stuck in bootloader.
Any key I just brings me back to this again.
Even in HBOOT selecting Recovery or Factory reset does nothing other than bring up this screen.
Powering down and then on again has the same result.
I was trying to get back to stock. Typed in fastboot oem lock and after that... the problem started!!
Any ideas??
Click to expand...
Click to collapse
This is intentional. When you relock the bootloader, it renders the phone unbootable and expects the RUU to be run.
redpoint73 said:
This is intentional. When you relock the bootloader, it renders the phone unbootable and expects the RUU to be run.
Click to expand...
Click to collapse
Ok. I'd downloaded what I assume is the correct RUU.exe. Ran it from the computer and I get a 131 error. Not the correct RUU !!
Stuck for a solution now!!
morgansgrandad said:
Ok. I'd downloaded what I assume is the correct RUU.exe. Ran it from the computer and I get a 131 error. Not the correct RUU !!
Stuck for a solution now!!
Click to expand...
Click to collapse
You shouldn't be assuming what RUU to run. What is your CID and hboot number? What RUU did you try to run?
HBOOT is 3.19.0.0000 CID, can't find.
RUU is M8_4.16.401.10_Europe.exe
morgansgrandad said:
HBOOT is 3.19.0.0000 CID, can't find.
RUU is M8_4.16.401.10_Europe.exe
Click to expand...
Click to collapse
The OS number (3.32.206.9) shown on your hboot screen (pic in your top post) indicates that is not the right RUU. The number in the x.xx.206.x is carrier specific,and seems to indicate that your phone is the O2 UK version. Running an RUU with version x.xx.401.x won't work. The number in the "401" spot would need to "206" for it to be the right RUU.
Not sure, but I don't think your CID has RUUs. If that is the case, your best bet it to unlock the bootloader again, flash TWRP back to the phone, and restore a nandroid with your software number (3.32.206.9) if you can find it. Then flash stock recovery back to the phone. That is as close to "stock" as you will get, if there is no RUU for your CID version.
redpoint73 said:
The OS number (3.32.206.9) shown on your hboot screen (pic in your top post) indicates that is not the right RUU. The number in the x.xx.206.x is carrier specific,and seems to indicate that your phone is the O2 UK version. Running an RUU with version x.xx.401.x won't work. The number in the "401" spot would need to "206" for it to be the right RUU.
Not sure, but I don't think your CID has RUUs. If that is the case, your best bet it to unlock the bootloader again, flash TWRP back to the phone, and restore a nandroid with your software number (3.32.206.9) if you can find it. Then flash stock recovery back to the phone. That is as close to "stock" as you will get, if there is no RUU for your CID version.
Click to expand...
Click to collapse
Thanks redpoint73. Looks like that's the only way to go!!
By looking at the radio, you need the Euro Version RUU. Looks like we gotta be detectives sometimes, lol.
Ok, I've unlocked the bootloader and am back to where it was.
It's running 5.0.1, Sense 6.0 and Android Revolution HD 34.6 by mike1986
I would like to clear that off and get back to stock with OTT updates.
Revolution HD 34.6 seems to use an awful lot of data. My other M8 has stock on-board, has identical apps etc and doesn't use nearly as much data as this one!!
Any further ideas??
morgansgrandad said:
Ok, I've unlocked the bootloader and am back to where it was.
It's running 5.0.1, Sense 6.0 and Android Revolution HD 34.6 by mike1986
I would like to clear that off and get back to stock with OTT updates.
Revolution HD 34.6 seems to use an awful lot of data. My other M8 has stock on-board, has identical apps etc and doesn't use nearly as much data as this one!!
Any further ideas??
Click to expand...
Click to collapse
Why not just set it up for Dev / Unlocked Edition?
http://www.htc.com/us/support/htc-one-m8/news/
hack14u said:
Why not just set it up for Dev / Unlocked Edition?
http://www.htc.com/us/support/htc-one-m8/news/
Click to expand...
Click to collapse
I'm downloading that now. BUT...........
Because of all my faffing on!! there's NO OS on the phone.
I'm really struggling now:crying:
This is my position now. Totally unusable phone!!
I would appreciate ANY help on getting back to as near as normal as possible.
Thank you.
I should add, the RUU messages are from trying post #16.
And the saga continues!
I found a nandroid backup with the same s/w number as mine, downloaded it from MEGA (it seemed to d/l ok).
When I ran it through TWRP I got signature verification failed.
This phone could end up in the depths of the river Tyne
morgansgrandad said:
This is my position now. Totally unusable phone!!
I would appreciate ANY help on getting back to as near as normal as possible.
Thank you.
I should add, the RUU messages are from trying post #16.
Click to expand...
Click to collapse
What hack14u neglected to mention, is that to run another version's RUU, you need s-off ($25 by sunshine), and then you need to change your MID and CID.
Relocking the bootloader (to run RUU) renders the phone with no OS, this is by design.
---------- Post added at 09:41 AM ---------- Previous post was at 09:34 AM ----------
morgansgrandad said:
And the saga continues!
I found a nandroid backup with the same s/w number as mine, downloaded it from MEGA (it seemed to d/l ok).
When I ran it through TWRP I got signature verification failed.
This phone could end up in the depths of the river Tyne
Click to expand...
Click to collapse
Hang in there, modding phones can often be an exercise in frustration. But the phone is quite recoverable, as long as you perform the correct steps.
A nandroid is not a flashable zip (such as a ROM). It needs to be restored in a very different way, its described in Post 3 of the stock nandroid thread (assuming that is where you go it from) under Question & Answers.
To summarize, you need to:
1) Unpack the zipk, which is a number of folders
2) Move the folders to the proper location on the phone's internal storage (removable SD is also possible, if you setup TWRP to back and restore to that location)
The exact location if very important (its described in Post 3 of the stock nandroid thread), since when restoring a nandroid, TWRP will not see the file to restore if you have it wrong. This is in direct contrast to installing a ROM zip, in which TWRP allows you to browse anywhere on the storage to find the file to flash.
3) Choose the menu option to RESTORE, not INSTALL

HTC M9 won't boot after update - can't flash anything, factory reset or unlock bl..?!

Hey guys
got a HTC M9 with cid "O2___102" which won't boot up after stock update.
Phone was not modified yet.
1. Can't unlock bootloader (says: "(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock") - so no way to install custom recovery + custom rom to revive
2. Can't boot into recovery (shows phone with a red exclamation mark but no menu) so no way to factory rest
3. can't find a matching RUU for the "O2___102" CID ...
PLEASE HELP =(
At the screen with the red triangle and exclamation mark, press and hold the power button. While holding the power button, quickly press and release the volume + button. If this gets you to recovery, try a factory reset.
fernandezhjr said:
At the screen with the red triangle and exclamation mark, press and hold the power button. While holding the power button, quickly press and release the volume + button. If this gets you to recovery, try a factory reset.
Click to expand...
Click to collapse
got into the recovery menu, thanks.
But damn phone is still not booting.
Guess I need to get factory image or custom rom on there but bootloader cant be unlocked and there is no damn RUU for this CID out is there?
zroice said:
Hey guys
got a HTC M9 with cid "O2___102" which won't boot up after stock update.
Phone was not modified yet.
1. Can't unlock bootloader (says: "(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock") - so no way to install custom recovery + custom rom to revive
2. Can't boot into recovery (shows phone with a red exclamation mark but no menu) so no way to factory rest
3. can't find a matching RUU for the "O2___102" CID ...
PLEASE HELP =(
Click to expand...
Click to collapse
as for the bootloader unlock go into settings>developer options>check oem unlocking. then you can unlock bootloader.
Aldo101t said:
as for the bootloader unlock go into settings>developer options>check oem unlocking. then you can unlock bootloader.
Click to expand...
Click to collapse
the damn thing is not booting.... =( Stuck at HTC logo - or else I would do that off course
zroice said:
the damn thing is not booting.... =( Stuck at HTC logo - or else I would do that off course
Click to expand...
Click to collapse
lol, sorry missed that part
---------- Post added at 07:50 PM ---------- Previous post was at 07:26 PM ----------
zroice said:
the damn thing is not booting.... =( Stuck at HTC logo - or else I would do that off course
Click to expand...
Click to collapse
I do believe if you can get to download mode you can do a factory nreset from there, if that will help you.
zroice said:
got into the recovery menu, thanks.
But damn phone is still not booting.
Guess I need to get factory image or custom rom on there but bootloader cant be unlocked and there is no damn RUU for this CID out is there?
Click to expand...
Click to collapse
What about flashing an older RUU and trying to take the update again?
fernandezhjr said:
What about flashing an older RUU and trying to take the update again?
Click to expand...
Click to collapse
cant find any ruu for that branding - if you see/saw one please let me know.
zroice said:
cant find any ruu for that branding - if you see/saw one please let me know.
Click to expand...
Click to collapse
The UK ones for O2 can be used with the German O2 CID, too. You can find them for example in my Collection of Back-to-Stock Files or on androidRUU. But I'm not sure whether a downgrade from android 5.1 is possible with S-ON. The only confirmed downgrades with S-ON were from 1.32.XXX.15 to 1.32.XXX.8. And from my experiences with Denis Meissner and Amr Nasser I would say that a downgrade isn't possible with S-ON if the first and/or the second number of the actual firmware version differ from the ones of the firmware you want to downgrade to.
Flippy498 said:
The UK ones for O2 can be used with the German O2 CID, too. You can find them for example in my Collection of Back-to-Stock Files or on androidRUU. But I'm not sure whether a downgrade from android 5.1 is possible with S-ON. The only confirmed downgrades with S-ON were from 1.32.XXX.15 to 1.32.XXX.8. And from my experiences with Denis Meissner and Amr Nasser I would say that a downgrade isn't possible with S-ON if the first and/or the second number of the actual firmware version differ from the ones of the firmware you want to downgrade to.
Click to expand...
Click to collapse
*downloading with fingers crossed*
Failed: -2, 19 to flash via downloadzip or smth like that
Can you flash twrp recovery? If you can, maybe you can flash a stock backup from someone else.
zroice said:
Failed: -2, 19 to flash via downloadzip or smth like that
Click to expand...
Click to collapse
Yeah, would have suprised me if it worked. As said before even downgrading from 1.40.XXX.X to 1.32.XXX.X seems to be impossible with S-ON. How long did you actually wait until you thought that you phone doesn't boot? The update to android 5.1 and the first boot took around an hour for me. Maybe you just need to wait a little longer. If your phone was unlocked I would suggest you to flash TWRP and use one of my stock backups but...
The only other option I can see right now is trying to find someone who has a java card. With S-OFF you should be able to downgrade with the RUU. (If I remember correctly there were one or two shops advertising their java card services on Android-Hilfe.) This option may not be for free but it should still be cheaper than sending your phone to HTC's repair service or buying a new phone.
Flippy498 said:
Yeah, would have suprised me if it worked. As said before even downgrading from 1.40.XXX.X to 1.32.XXX.X seems to be impossible with S-ON. How long did you actually wait until you thought that you phone doesn't boot? The update to android 5.1 and the first boot took around an hour for me. Maybe you just need to wait a little longer. If your phone was unlocked I would suggest you to flash TWRP and use one of my stock backups but...
The only other option I can see right now is trying to find someone who has a java card. With S-OFF you should be able to downgrade with the RUU. (If I remember correctly there were one or two shops advertising their java card services on Android-Hilfe.) This option may not be for free but it should still be cheaper than sending your phone to HTC's repair service or buying a new phone.
Click to expand...
Click to collapse
whats that java card you're talkin about? Never heard of that.
An appropiate RUU with the latest version should theoretically also work, right?
Problem ist that I cant flash anything custom because bootloader locked and I cant get inside the system to enable the bootloader unlock... =( and the thing has a visually broken volume up key for dropping down, so the htc support won't fix it (for free) I fear.. otherwise I would just give it to them since it has not been modified yet. (not my phone ..)
P.S:
OS Version is 2.10.206.2 - thats the latest one right?
zroice said:
whats that java card you're talkin about? Never heard of that.
An appropiate RUU with the latest version should theoretically also work, right?
Problem ist that I cant flash anything custom because bootloader locked and I cant get inside the system to enable the bootloader unlock... =( and the thing has a visually broken volume up key for dropping down, so the htc support won't fix it (for free) I fear.. otherwise I would just give it to them since it has not been modified yet. (not my phone ..)
P.S:
OS Version is 2.10.206.2 - thats the latest one right?
Click to expand...
Click to collapse
Yes, 2.10.206.2 is the latest version for now. If there were a RUU with your firmware version then using it would be the easiest way to solve your problems. But as far as I know the only existing ones for O2 are for 1.32.206.6 and 1.32.206.15. But with S-OFF you would be able to use the older RUUs, too.
I never used a java card so my knowledge about this topic isn't that outstanding. I know that it is a small, SIM-Card-like looking thing that allows you to S-OFF your phone. Usually they cost several hundred euros/dollars and the number of times you can use them is limited. Since verizon blocks bootloader unlocking these cards are the only option if a verizon users wants to flash anything on his/her phone. Some German phone shops offered S-OFF by java card, too, before sunshine got updated for the M9. That's why I gave you the link to Android-Hilfe. (And that's actually all I know about that topic.)
i need this rru please any one have to uplode link
thanks
Just as an update, I recently bricked this phone trying to flash lineage to it. To fix it, I went to HTC.com and downloaded the current RUU and put the phone into download mode. I know some people say you don't need to "relock" the device, but I don't get errors during the installation with RUU when relocked. Plus, I am running with S-on.
theadra said:
Just as an update, I recently bricked this phone trying to flash lineage to it. To fix it, I went to HTC.com and downloaded the current RUU and put the phone into download mode. I know some people say you don't need to "relock" the device, but I don't get errors during the installation with RUU when relocked. Plus, I am running with S-on.
Click to expand...
Click to collapse
Bootloader and s status are irrelevant. The phone will flash regardless.

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!

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

Updating to Android 6.0 not possible?

Hello,
I am in need of some help.
2 weeks ago i bought the HTC One M9.
A few days ago the update to android 6.0 message popped up.
I have probably tried updating it like 15 times already, but everytime the first part is downloaded, and my phone reboots, after 1/4th of the updating it shows a red triangle with an exclamation point in it.
I have tried wiping the cache, it didn't help.
Honestly i don't have a clue what's wrong, or where i can find out what went wrong, so i would really appriciate all the help i can get.
Example of what happens:
malmgrens [dot] org/bilder/htc_recovery_mode [dot] jpg
A few more details will be helpful:
- what variant do you have (locale & carrier)?
- is your phone modified (ie, custom recovery and/or root)?
In order to take an over-the-air update, the phone must be completely stock. If it is not, you'll need an RUU to restore your phone to stock (be sure to backup your information first). Then you'll be able to take the OTA update.
computerslayer said:
A few more details will be helpful:
- what variant do you have (locale & carrier)?
- is your phone modified (ie, custom recovery and/or root)?
In order to take an over-the-air update, the phone must be completely stock. If it is not, you'll need an RUU to restore your phone to stock (be sure to backup your information first). Then you'll be able to take the OTA update.
Click to expand...
Click to collapse
Hey, thanks so much for your reply
I am pretty sure i got the dutch version, it might be belgium.
The carrier is vodafone.
I am pretty sure its not rooted etc, since i didn´t do anything with it.
What does stock and RUU mean?(I am a total noob with this.)
appie.0606 said:
Hey, thanks so much for your reply
I am pretty sure i got the dutch version, it might be belgium.
The carrier is vodafone.
I am pretty sure its not rooted etc, since i didn´t do anything with it.
What does stock and RUU mean?(I am a total noob with this.)
Click to expand...
Click to collapse
Hi there,
To clarify - your phone boots to its current software with no problem, right? If so, it would be a wise thing for you to determine your MID (model ID) and CID (carrier ID). There are a number of guides - Google is your friend. I recommend looking up ADB installation, your OS (Mac, Windows, Linux) and going from there.
Once you know your MID & CID, we can help you find out what firmware is available for you.
To learn about RUUs, VenomROM has a great page that explains about what they are and how to use them.
Peace,
Computerslayer
computerslayer said:
Hi there,
To clarify - your phone boots to its current software with no problem, right? If so, it would be a wise thing for you to determine your MID (model ID) and CID (carrier ID). There are a number of guides - Google is your friend. I recommend looking up ADB installation, your OS (Mac, Windows, Linux) and going from there.
Once you know your MID & CID, we can help you find out what firmware is available for you.
Peace,
Computerslayer
Click to expand...
Click to collapse
Yes my phone boots to current software without any problems right now.
Some info i found:
CID: VODAPE17
MID did not show for some reason. I tried multiple ways using adb shell and fastboot, but shell doesnt show anything and fastboot gets stuck at waiting for device.
Is finding my MID nessecary to fix this update problem? If so how can i find it?
Power of your M9
Power on & press at the same time to enter in the bootloader, volume -
on the top of the screen, is it writed locked or unlocked?
You can see more information in download mode...
bzhmobile said:
Power of your M9
Power on & press at the same time to enter in the bootloader, volume -
on the top of the screen, is it writed locked or unlocked?
You can see more information in download mode...
Click to expand...
Click to collapse
Hey thanks for your reply.
It says unlocked. Is that normal or could it be an/the issue?
If you are unlocked, it's related to your issue.
You have to flash a RUU to be "stock" and ready for the OTA...
bzhmobile said:
If you are unlocked, it's related to your issue.
You have to flash a RUU to be "stock" and ready for the OTA...
Click to expand...
Click to collapse
Alright, so if i understand correctly i can flash a RUU (whatever it is lol) without having to backup without doing a clean install. The phone wont wipe my data?
Would this guide be what you mean?
how-to-flash-ruu-firmware-htc-one-m9/
from naldotech
com
If you flash an RUU....your device will be wiped clean....as it came out of the box...
Then you can OTA on a clean....stock rom....g
The Thread is a good one.
More explication of what is needed in post2 or post 3 of TWRP thread (about Google's new limitation for the OTA).
Beware flashing a RUU will wipe everything, don't forget to backup all you take care...

Categories

Resources