HI
As title said, I accepted the official update from HTC and now my phone won't start.
All I know is I have S-ON and I don't want to do factory wipe.
I did try wipe cache partition multiple times.
here is the info from download mode:
*** LOCKED***
htc_himaulatt PVT S-on
LK-1.0.0.0000
RADIO-01.01_U11440221_62.05.503205G_F
OpenDSP-v20.2.6-00452-M8994_0216
OS-1.32.661.31
APR 1 2014,21:58:13 (506785)
I believe is the 5.1 update
Thank you very much
You did leave it long enough to update?
It took over an hour to update mine and that's not including downloading.
If you power cycled your phone thinking it was stuck you probably borked the update process.
If your device is carrier locked then you'll have to wait for the official ruu.
If you have a wwe (World Wide English) then you can use the 5.1 ruu.
Otherwise you'll have to bite the bullet and reset it, losing all data.
I wish I stole my HTC M9. It's a pile of ****.
shivadow said:
You did leave it long enough to update?
It took over an hour to update mine and that's not including downloading.
If you power cycled your phone thinking it was stuck you probably borked the update process.
If your device is carrier locked then you'll have to wait for the official ruu.
If you have a wwe (World Wide English) then you can use the 5.1 ruu.
Otherwise you'll have to bite the bullet and reset it, losing all data.
I wish I stole my HTC M9. It's a pile of ****.
Click to expand...
Click to collapse
5.1ruu?
where can i find the ruu.
I don't think i needed the 5.1 one
jeff741258 said:
HI
As title said, I accepted the official update from HTC and now my phone won't start.
All I know is I have S-ON and I don't want to do factory wipe.
I did try wipe cache partition multiple times.
here is the info from download mode:
*** LOCKED***
htc_himaulatt PVT S-on
LK-1.0.0.0000
RADIO-01.01_U11440221_62.05.503205G_F
OpenDSP-v20.2.6-00452-M8994_0216
OS-1.32.661.31
APR 1 2014,21:58:13 (506785)
Click to expand...
Click to collapse
We need more information than this to help. What exactly did you do, and what happened when you accepted the ota? By "won't start" what do you mean? A bootloop or is it completely dead?
From your info, it appears the ota never took, as you're still on 1.32 firmware.
To my knowledge, there are no ruus of any sort for Telus. You may need to unlock, install custom recovery, and then flash a backup to get back up.
iElvis said:
To my knowledge, there are no ruus of any sort for Telus.
Click to expand...
Click to collapse
At least no free RUUs.
iElvis said:
We need more information than this to help. What exactly did you do, and what happened when you accepted the ota? By "won't start" what do you mean? A bootloop or is it completely dead?
From your info, it appears the ota never took, as you're still on 1.32 firmware.
To my knowledge, there are no ruus of any sort for Telus. You may need to unlock, install custom recovery, and then flash a backup to get back up.
Click to expand...
Click to collapse
It said i have an available update, so i accepted and took more than an hour to finished the update. After the update, It just keep looping in the HTC logo screen. I can still go into the bootloader, download mode and recovery mode, but pretty much it. In recovery mode, it can't even open the files in the internal memory. I also did a factory reset/wipe, It didn't work.
How do you know my phone is from telus? I didn't get my phone from carriers, it is unlocked.
jeff741258 said:
How do you know my phone is from telus? I didn't get my phone from carriers, it is unlocked.
Click to expand...
Click to collapse
That Information can be gained from your firmware version.
How to "read" firmware versions
Sneakyghost's & Behold_this' SKU, CID & MID List
Ahhh thank you very much
I also did some digging. I find a website under HTCDEV. I can't post outside link yet. But is it useful in my situation?
I don't really want to root my phone unless i have no other choices.
I have root my previous phones before, but it is more for trying different rom instead of rescuing the phone.
jeff741258 said:
Ahhh thank you very much
I also did some digging. I find a website under HTCDEV. I can't post outside link yet. But is it useful in my situation?
I don't really want to root my phone unless i have no other choices.
I have root my previous phones before, but it is more for trying different rom instead of rescuing the phone.
Click to expand...
Click to collapse
As far as I can see you have two choices:
Option 1 is trying to get the correct RUU for your firmware. I posted a source earlier but it's not for free. Some other users here on xda already have an account for that website so maybe one of them is kind enough to help you out. Nevertheless flashing a RUU will wipe everything on your phone so all your data you didn't backup before all this hassle started is lost.
Option 2 is trying to unlock your bootloader via HTCDdev which will erase everything on your phone, too. After that you are able to flash the custom recovery TWRP. If you are able to find someone else's backup for the firmware version you have you are able to get back to a working stock system, too. But I'm not sure whether an unlock is possible without a booting system because I never faced that situation.
jeff741258 said:
Ahhh thank you very much
I also did some digging. I find a website under HTCDEV. I can't post outside link yet. But is it useful in my situation?
I don't really want to root my phone unless i have no other choices.
I have root my previous phones before, but it is more for trying different rom instead of rescuing the phone.
Click to expand...
Click to collapse
Can you post what's in your Download mode screen (except imei and s/n)? You say the update completed, but the OP lists a 5.0 firmware version. This matters for whether you can unlock and root.
It's possible your phone can't be fixed in its current state and will have to be replaced. This is because of security features that have been added to 5.1, if you indeed got that update.
iElvis said:
Can you post what's in your Download mode screen (except imei and s/n)? You say the update completed, but the OP lists a 5.0 firmware version. This matters for whether you can unlock and root.
It's possible your phone can't be fixed in its current state and will have to be replaced. This is because of security features that have been added to 5.1, if you indeed got that update.
Click to expand...
Click to collapse
*** LOCKED***
htc_himaulatt PVT S-on
LK-1.0.0.0000
RADIO-01.01_U11440221_62.05.503205G_FOpenDSP-v20.2.6-00452-M8994_0216
OS-1.32.661.31
APR 1 2014,21:58:13 (506785)
jeff741258 said:
*** LOCKED***
htc_himaulatt PVT S-on
LK-1.0.0.0000
RADIO-01.01_U11440221_62.05.503205G_FOpenDSP-v20.2.6-00452-M8994_0216
OS-1.32.661.31
APR 1 2014,21:58:13 (506785)
Click to expand...
Click to collapse
Okay, that's good. It means the 5.1 update did not take, which means you can still unlock via htcdev if you choose, or that RUU linked above ought to clear things up.
Hey thank you for everyone helps. Since my phone still under warranty, i have decided to send my phone back to HTC. Once again, thank you for everyone who read my post and help me.
I'm quite sure the device restarts a few times after the update. I remember a black htc screen then a couple of reboots (my arse was twitching like a rabbit's nose) then after a short while it booted into the homescreen.
I'd leave it running and connected to the internet overnight and see if it resolves itself. If not then send it to HTC.
I wish I stole my HTC M9. It's a pile of ****.
Related
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.
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!
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
Hi
htc_pmeuhl PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.8996.00007_0809
OS-2.41.401.41
Aug 2 2017
I've put my HTC 10 back to stock using a RUU.zip (2.41.401.41) so I can sell it.
MY bootloader says RELOCKED which i expected and am not worried about but my software status still says MODIFIED.
I think i read somewhere that a RUU.exe will bring the software status back to OFFICIAL but i can not find one.
My question is can i still take OTA's with a software MODIFIED status without problems?
Would not want to sell the phone to someone who is going to have problems updating in the future.
P.S. During the setup wizard after doing the RUU i had a pre-ticked option to install 3rd party apps that i don't recall seeing when i first set the phone up. Is this normal or have i used a dodgy RUU?
Thanks in advance
Bootloader status has no bearing on OTA so you should be be fine.
Ignore
Thanks @Tarima
This is a picture of the app installer that appears during the set-up wizard. Is this normal?
Cheers
fgw3987 said:
Thanks @Tarima
This is a picture of the app installer that appears during the set-up wizard. Is this normal?
Cheers
Click to expand...
Click to collapse
No worries. I've honestly never seen that myself on my phone but I have US Unlocked. Maybe it's baked in the ruu? Is it a carrier branded 10? Either way if you flashed the ruu made for your phone then there is not much else to do.
The phone is factory unlocked and it is the correct RUU for this device. I wonder if it's a touchpal keyboard or news republic thing. Anyway it doesn't matter as long as it's stock and fresh for the next person to enjoy.
Cheers
So as some backstory, I recently bought a second-hand HTC ONE M8 and it was working in perfect condition. All the trouble started when I attempted to update the phone to android version 6.0 and the update failed at around 80%. This lead me to a constant reboot state from the HTC logo to the screen with the triangle with an exclamation mark in the middle.
As of right now I have tried every single option on the bootloader to try to fix the issue with no success. I have also attempted to install multiple RUU's to reset the phone but I have no found one RUU that matches my phone's software status (Phone bootloader information below). It is also worth to mention that the phone is an optus (Australia Version). Here are my phone's specifications:
*** Software status: Official ***
*** LOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-V51.2.2-00593-M8974_FO.1015
OS-6.12.980.5
eMMC-boot 2048MB
Dec 1 2015,18:43:39.0
Some side notes:
When trying to install an RUU, the log, when failing, suggests that my device has htc/optus_au/htc_m8: 6.0/MRA58K/663331.5:user/release-keys
This device has not been modified by myself nor the previous owners
A user over at android forums had a similar problem (post name was: 'Help! HTC One M8 stuck on Fastboot screen'), but that post is dead with one very informative reply that doesn't help solve the issue .
Th3CobaltLlama said:
I have also attempted to install multiple RUU's to reset the phone but I have no found one RUU that matches my phone's software status
When trying to install an RUU, the log, when failing, suggests that my device has htc/optus_au/htc_m8: 6.0/MRA58K/663331.5:user/release-keys[/LIST]
Click to expand...
Click to collapse
The RUU has to be exactly for your version, Optus and version number 6.12.980.5. I don't know if your version has RUU. So if you don't have that exact RUU, you can run a million different RUUs, and million times, and it will fail every single time, guaranteed.
If no RUU, your best bet is to unlock the bootloader, flash TWRP custom recovery, and either flash a custom ROM, or restore the stock TWRP backup (6.12.980.5) from here:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
redpoint73 said:
The RUU has to be exactly for your version, Optus and version number 6.12.980.5. I don't know if your version has RUU. So if you don't have that exact RUU, you can run a million different RUUs, and million times, and it will fail every single time, guaranteed.
If no RUU, your best bet is to unlock the bootloader, flash TWRP custom recovery, and either flash a custom ROM, or restore the stock TWRP backup (6.12.980.5) from here:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
Thanks for the help! I'm trying it out now, just learning how to do all the jazz with TWRP (Kind of confusing to me, if you know a reliable video tutorial could you link me?). I'll repost once I have made some proper progress.
It's Fixed, Many Thanks!
redpoint73 said:
The RUU has to be exactly for your version, Optus and version number 6.12.980.5. I don't know if your version has RUU. So if you don't have that exact RUU, you can run a million different RUUs, and million times, and it will fail every single time, guaranteed.
If no RUU, your best bet is to unlock the bootloader, flash TWRP custom recovery, and either flash a custom ROM, or restore the stock TWRP backup (6.12.980.5) from here:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
You're an actual legend! It's fixed now! I've never met anyone as helpful as you online redpoint73. Good luck to you in future mate, you deserve whatever good comes your way! :good:
Th3CobaltLlama said:
You're an actual legend! It's fixed now! I've never met anyone as helpful as you online redpoint73. Good luck to you in future mate, you deserve whatever good comes your way! :good:
Click to expand...
Click to collapse
You're quite welcome. Glad you worked it out. The instructions on how to restore a stock TWRP are not trivial; but it's all there, if you are patient and careful enough to work through it (as it appears you've done)!