Ever since I upgraded to 1.28.x I have an annoying bug (phone hangs when trying to play any sound without having the headphones on - music, ringtone etc) and phone reboots soon after..
How do I go back to the previous version?
If I were you, I'd factory reset the phone first, because this shouldn't happen
just did, no luck.. it seems the problem lies within the 1.28 update.. I might screwed it up by not having enough battery to finish the process... I was borderline 35% (but plugged in) I think when I went to see my phone after the upgrade it was switched off... I should try (somehow) to re-apply the 1.28 upgrade...
gkatsanos said:
just did, no luck.. it seems the problem lies within the 1.28 update.. I might screwed it up by not having enough battery to finish the process... I was borderline 35% (but plugged in) I think when I went to see my phone after the upgrade it was switched off... I should try (somehow) to re-apply the 1.28 upgrade...
Click to expand...
Click to collapse
Okay, you should download the original RUU from HTC, and install the OTA update afterwards (on a charged batt).
Is there a how-to / manual on how to do that?
"Do not update while the charger is plugged in, this may cause interuptions"
There you go.
Root and flash a custom firmware or any firmware you want.
Better than having a half working phone.
crap, where was that written?
RomNoR said:
"Do not update while the charger is plugged in, this may cause interuptions"
There you go.
Root and flash a custom firmware or any firmware you want.
Better than having a half working phone.
Click to expand...
Click to collapse
You could do that, but if you don't want do take the risk of S-offing/rooting your phone/installing another recovery img, I'd install the RUU.
A RUU is a windows executable file containing the official ROM (no su, just std). You can download it here http://www.filefactory.com/f/7cc7b2fbdd03c031/. Choose the right version for your location (1.26), plugin your phone on USB and run the RUU. It'll revert the OTA changes.
Thanks! Any other way to get links for these RUU? (filefactory is quite busy..) Are these RUU in the official HTC website? (safer)
I don't believe so, HTC hasn't officialy released a RUU (yet) :S
Those RUU's are leaked (though final) versions of the htc one x rom. Agreed it would be safer if HTC released them...
You can't roll back without S-OFF as you can't downgrade the HBOOT
no clue what S-OFF is! are you sure it won't work?
gkatsanos said:
Thanks! Any other way to get links for these RUU? (filefactory is quite busy..) Are these RUU in the official HTC website? (safer)
Click to expand...
Click to collapse
Before you click "OK" to install, same as the 35% battery warning.
EddyOS said:
You can't roll back without S-OFF as you can't downgrade the HBOOT
Click to expand...
Click to collapse
you actually can I just did it, installed 1.26 RUU over 1.28 one..
gkatsanos said:
you actually can I just did it, installed 1.26 RUU over 1.28 one..
Click to expand...
Click to collapse
How did you install 1.26 RUU over 1.28 one?
It gives me error!!!
don't know, just did.. no errors... phone is unlocked (no carrier)
thats where I got the RUU from http://www.xdafileserver.nl/index.php?dir=HTC/One+X/Stock+Rom/Endeavour then I got HTC SYNC from http://www.htc.com/uk/help/?dl_id=1073&news_id=910 et voila...
i'll be trying this right away. i tried rolling back from OTA 1.28 with RUU 1.26 from filefactory (took 6 hours to download!) but it gave me a bootloader version error at the end. although my phone was unlocked, recovery changed, changed back, relocked. maybe that makes a difference.
I tried with no luck
gkatsanos said:
you actually can I just did it, installed 1.26 RUU over 1.28 one..
Click to expand...
Click to collapse
Then you're the first person in history to do it without S-OFF as you can update an HBOOT but can't go back in normal circumstances
maybe his specific ota update to 1.28 didn't include the new bootloader...
Related
i found it it working for me my htc is back to life
Link plz...
asifpm said:
Link plz...
Click to expand...
Click to collapse
Here you go:
rogersnm said:
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.28.401.9_Radio_1.1204.103.14_release_256469_signed
MD5 Checksum: 347335388666a64f35b894c5baafd727
SHA1 Checksum: 2749ef0de5e518dcc4031602eb602ebc085514e6
File Size: 573.4 MB
Code:
hoxroms.serveftp.com/RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.28.401.9_Radio_1.1204.103.14_release_256469_signed.exe
Click to expand...
Click to collapse
This won't work on a branded 02 device right?
Sent from my HTC One X using Tapatalk 2
BigladUK said:
This won't work on a branded 02 device right?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
if your firmware version has 401 included then it will.
eg: 1.xx.401.x
Haba1205 said:
if your firmware version has 401 included then it will.
eg: 1.xx.401.x
Click to expand...
Click to collapse
Rubbish :-( mine is 1.26.206.2
Si
BigladUK said:
Rubbish :-( mine is 1.26.206.2
Si
Click to expand...
Click to collapse
hey buddy now i am on 1.28 but did not update through the ota but just by flashing custom rom..if i was to flash this baby over my custom rom and did full wipe first would that work?
apologies if this sounds stupid..still learning you see
i will but u need first relock your bootloader then instal ruu
Thank you
thank you for starting this thread. This helped me update to 1.28
Flashing RUU 1.28 over existing
Hey guys, I am already running ruu 1.28 but I want to install it again over the existing system so I can start fresh. I tried flashing the img from the bootloader and via fastboot but nothing changes. I am running unlocked and rooted.
thanks for you help, i think im missing something really simple but im getting frustrated.
briken.one said:
Hey guys, I am already running ruu 1.28 but I want to install it again over the existing system so I can start fresh. I tried flashing the img from the bootloader and via fastboot but nothing changes. I am running unlocked and rooted.
thanks for you help, i think im missing something really simple but im getting frustrated.
Click to expand...
Click to collapse
You need the flash the stock recovery, relock the bootloader and then run the RUU. That will return you to stock firmware.
briken.one said:
Hey guys, I am already running ruu 1.28 but I want to install it again over the existing system so I can start fresh. I tried flashing the img from the bootloader and via fastboot but nothing changes. I am running unlocked and rooted.
thanks for you help, i think im missing something really simple but im getting frustrated.
Click to expand...
Click to collapse
No need to flash anything, just re-lock your device and run the RUU.exe.
I am trying to put my phone back to vodafone stock ROM,
phones with hboot 0.94.000?
its vodafone UK phone, I am trying to flash 1.26 RUU as there is not 1.28 RUU for vodafone uk yet, but it keeps giving error 140 bootload version error.
and everytime i relock my bootloader i get
RELOCKED
SYSTEM WARNING
after above phone keeps going back in to boot loader and the way it comes out and goes back to old ROM is by unlocking the boot loader again.
can any one help?
thanks
rohitbaba said:
I am trying to put my phone back to vodafone stock ROM,
phones with hboot 0.94.000?
its vodafone UK phone, I am trying to flash 1.26 RUU as there is not 1.28 RUU for vodafone uk yet, but it keeps giving error 140 bootload version error.
and everytime i relock my bootloader i get
RELOCKED
SYSTEM WARNING
after above phone keeps going back in to boot loader and the way it comes out and goes back to old ROM is by unlocking the boot loader again.
can any one help?
thanks
Click to expand...
Click to collapse
hboot 0.94 comes with 1.28, this means you won't be able to run a 1.26 RUU - you can only run 1.28 RUUs or newer. If you can't get the 1.28 RUU for your CID you won't be able to run a RUU. You can still flash custom ROMs though, so if your phone is bootlooping that's your way out.
rogersnm said:
hboot 0.94 comes with 1.28, this means you won't be able to run a 1.26 RUU - you can only run 1.28 RUUs or newer. If you can't get the 1.28 RUU for your CID you won't be able to run a RUU. You can still flash custom ROMs though, so if your phone is bootlooping that's your way out.
Click to expand...
Click to collapse
I need to send my phone back to Vodafone for repair so i need to find a way to restore Vodafone ROM on the phone.
is there any other way i can get Voda rom back on the phone, also should the security warning be on the boot loader.
thanks
Dev
rohitbaba said:
I need to send my phone back to Vodafone for repair so i need to find a way to restore Vodafone ROM on the phone.
is there any other way i can get Voda rom back on the phone, also should the security warning be on the boot loader.
thanks
Dev
Click to expand...
Click to collapse
Are you on vodafone UK? The 1.28 RUU is available for that carrier.
Even after relocking the bootloader and running a RUU, it's impossible (without S-OFF) to remove any trace that you unlocked it. The repair centre will still be able to tell.
rogersnm said:
Are you on vodafone UK? The 1.28 RUU is available for that carrier.
Even after relocking the bootloader and running a RUU, it's impossible (without S-OFF) to remove any trace that you unlocked it. The repair centre will still be able to tell.
Click to expand...
Click to collapse
1.28 RUU is is only OTA not full unless there is one.
if there is can you forward me the link
thanks
rohitbaba said:
1.28 RUU is is only OTA not full unless there is one.
if there is can you forward me the link
thanks
Click to expand...
Click to collapse
It's in my sig
http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_256488_signed.exe
rogersnm said:
It's in my sig
http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_256488_signed.exe
Click to expand...
Click to collapse
thanks for the link, so from what you have told me there is no way put the phone back to how it came from vodafone.
thanks
Dev
rohitbaba said:
thanks for the link, so from what you have told me there is no way put the phone back to how it came from vodafone.
thanks
Dev
Click to expand...
Click to collapse
Essentially no. Once you unlock it, even if you relock it it won't be exactly the same. The bootloader will remember that it was previously unlocked and repair centres will be able to see it. That said, restoring the RUU is better than nothing, but from what I've heard the repair centres like to bill you for a motherboard replacement if you unlock your device.
UK law does give you a large degree of protection if you wanted to take it to court though (assuming you're returning it due to a fault that was not caused by unlocking the device)
I have a O2 UK branded hox, which i've unlocked and use on Tesco Mobile's network (actually uses O2 network) but just wondering if I would still receive OTA updates if I revert back to stock, as it was my understanding they were pushed out by the network providers?
Yes you can still receive OTA updates if you revert back to stock .
The phone checks HTC servers for updates using the Internet. It has nothing to do with the provider.
BenPope said:
The phone checks HTC servers for updates using the Internet. It has nothing to do with the provider.
Click to expand...
Click to collapse
Correct. It's the software build you're using that determines the updates. For example, if you're running x.xx.61.x (Orange UK) and you don't change this bar using a different SIM card you'll only get update that have x.xx.61.x in it
Thanks guys just gotta figure out how to put it back to stock now....
What HBOOT are you on? If you're on an earlier one you might be able to get away with the 1.2x RUU but if you had the 2.17.61.x OTA update recently I believe you're stuck as that RUU hasn't surfaced yet
EddyOS said:
What HBOOT are you on? If you're on an earlier one you might be able to get away with the 1.2x RUU but if you had the 2.17.61.x OTA update recently I believe you're stuck as that RUU hasn't surfaced yet
Click to expand...
Click to collapse
0.96 is my hboot
Pretty sure the existing Orange UK RUU will do the job for stock in that case, then
EDIT: This one should do...
http://htcruu.com/Endeavor/RUU_ENDE...Radio_1.1204.105.14_release_260736_signed.exe
EddyOS said:
Pretty sure the existing Orange UK RUU will do the job for stock in that case, then
EDIT: This one should do...
http://htcruu.com/Endeavor/RUU_ENDE...Radio_1.1204.105.14_release_260736_signed.exe
Click to expand...
Click to collapse
Ah sorry i just changed my avatar, just changed last month from orange to tesco mobile, but my phone is a O2 branded handset which is why i'd need an O2 RUU
EddyOS said:
What HBOOT are you on? If you're on an earlier one you might be able to get away with the 1.2x RUU but if you had the 2.17.61.x OTA update recently I believe you're stuck as that RUU hasn't surfaced yet
Click to expand...
Click to collapse
All this RUU stuff pickles me.
How do you know the correct RUU for your model?
Thanks !
Wilks3y said:
All this RUU stuff pickles me.
How do you know the correct RUU for your model?
Thanks !
Click to expand...
Click to collapse
If you've not unlocked/rooted/gone custom at all it's very simple! Go to Settings>About phone>Software information and make a note of the build number, e.g. 2.17.401.2
THEN see if it's available for download. In this case, it is...
http://htcruu.com/?dir=Endeavor
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
Having the RUU for your phone to hand makes it a LOT easier to get back to stock should you need to
To the OP, this one should do the job but can't guarantee...
RUU_ENDEAVOR_U_ICS_40_O2_UK_1.26.206.2_Radio_1.1204.90.13_release_251230_signed.exe
EddyOS said:
To the OP, this one should do the job but can't guarantee...
RUU_ENDEAVOR_U_ICS_40_O2_UK_1.26.206.2_Radio_1.1204.90.13_release_251230_signed.exe
Click to expand...
Click to collapse
Ok thats the one I have thanks, just need to figure out which boot img to flash as there are 2 on the guide i read 1.26 or 2.17 or something
Take the boot.img from the RUU...although you don't need to if you're going to flash the RUU. All you have to do is relock the bootloader and run it when the phone is in fastboot mode - it'll put it back to 100% stock
Many thanks, just found my original Nandroid too should I need it
EddyOS said:
If you've not unlocked/rooted/gone custom at all it's very simple! Go to Settings>About phone>Software information and make a note of the build number, e.g. 2.17.401.2
THEN see if it's available for download. In this case, it is...
http://htcruu.com/?dir=Endeavor
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
Having the RUU for your phone to hand makes it a LOT easier to get back to stock should you need to
To the OP, this one should do the job but can't guarantee...
RUU_ENDEAVOR_U_ICS_40_O2_UK_1.26.206.2_Radio_1.1204.90.13_release_251230_signed.exe
Click to expand...
Click to collapse
Cheers bud, theres so many terms etc for Android, RUU, Endevour etc etc, some of them are just tricky to get your head round
Endeavoru is the HTC codename for the One X, in the same way Pyramid is the Sensation
EddyOS said:
Endeavoru is the HTC codename for the One X, in the same way Pyramid is the Sensation
Click to expand...
Click to collapse
Ahhh, thanks for that info mate much appreciated.
Managed to do it by restoring my original nandroid I did as soon as I unlocked the bootloader, at first it was boot looping but i flashed the boot.img from nandroid and it is fine, ota showed the 4.0.4 update immediately and managed to download it, now back onto arhd 9.7.2 so at least I know I can get back, will just have to relock it next time and flash stock recovery. will just have to figure out which recovery would be needed.
You don't need to relock to install OTA.
So everytime my screen turns off it turns off my phone itself and I have to restart it. It turns my whole phone off.
I am currently running stock rooted with s-off. It just started happening after I restored phone from a previous backup. Everything went great and worked but when I turn off screen it turns off my phone.
UnknownPopo said:
So everytime my screen turns off it turns off my phone itself and I have to restart it. It turns my whole phone off.
I am currently running stock rooted with s-off. It just started happening after I restored phone from a previous backup. Everything went great and worked but when I turn off screen it turns off my phone.
Click to expand...
Click to collapse
Did you update your firmware at any point? And how old is the backup? Because this sounds like a firmware conflict between 1.32 and later bases. If you're running 1.4 or later firmware, and the backup was on 1.32, that's your problem.
Oh **** me I love you yes, backup was before firmware update, how can I update?
iElvis said:
Did you update your firmware at any point? And how old is the backup? Because this sounds like a firmware conflict between 1.32 and later bases. If you're running 1.4 or later firmware, and the backup was on 1.32, that's your problem.
Click to expand...
Click to collapse
So how do I update my firmware? Software number right now is 1.32.661.31, custom rom I installed was 2.10.401.1,
UnknownPopo said:
So how do I update my firmware? Software number right now is 1.32.661.31, custom rom I installed was 2.10.401.1,
Click to expand...
Click to collapse
Well, that's your problem. You've got a few options:
-Go back to stock and get the OTA
-Relock and run a RUU for your phone
-S-off and update manually
The last option is my preference since you can get the latest no matter where you are, but you do have to pay $25 for Sunshine.
iElvis said:
Well, that's your problem. You've got a few options:
-Go back to stock and get the OTA
-Relock and run a RUU for your phone
-S-off and update manually
The last option is my preference since you can get the latest no matter where you are, but you do have to pay $25 for Sunshine.
Click to expand...
Click to collapse
I dont think you do need to relock phone for ruu. I may be wrong but I dont think I did when I used ruu for OTA.
SmIzUrF said:
I dont think you do need to relock phone for ruu. I may be wrong but I dont think I did when I used ruu for OTA.
Click to expand...
Click to collapse
Go for the sunshine method mate. Once you've finished doing the run route it may happen again in the future, by that point 25 dollars will seem like nothing for the trouble... In the state you're in you could also change the kernel you're using and that will also fix the issue.
SmIzUrF said:
I dont think you do need to relock phone for ruu. I may be wrong but I dont think I did when I used ruu for OTA.
Click to expand...
Click to collapse
You are correct. I am unlocked, and have used the RUU.exe method a few times now.
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 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