First up I love the google dialer but when I install it it works fine unless I go to recent calls then it force closes. Is there a fix to this?
Also it took me going back to a stock ROM to get firewater to work I am s off now but how do I get the latest firmware on my phone. Also what is the latest firm ware. I would like to use the latest stock sense ROMs.
Thanks in advance.
Anyone?
Poo
Hi,
regarding Google dialer I can't tell. Are you using the GPE or GSM edition?
Assuming you are using GSM. Please name your MID/CID to be abled to check what the latest stock ROM version - and thus firmware - is.
In case of WWE with CID HTC__001 I could tell you that it is Android 4.4.3 with version number 2.22.401.5 and the corresponding firmware.
Sent from my HTC One_M8 using XDA Free mobile app
HTCNerdYoda said:
Hi,
regarding Google dialer I can't tell. Are you using the GPE or GSM edition?
Assuming you are using GSM. Please name your MID/CID to be abled to check what the latest stock ROM version - and thus firmware - is.
In case of WWE with CID HTC__001 I could tell you that it is Android 4.4.3 with version number 2.22.401.5 and the corresponding firmware.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Is there a how to video on how to do this? I did the boot loader root and s- off by myself because they had a how to video. Is there a how to video to do this?
Better do it according to one of the manuals that can be found here. As I wanted to guide you I asked for the MID/CID. Can you provide this, as then I would be able to help you flashing newest firmware.
Sent from my HTC One_M8 using XDA Free mobile app
HTCNerdYoda said:
Better do it according to one of the manuals that can be found here. As I wanted to guide you I asked for the MID/CID. Can you provide this, as then I would be able to help you flashing newest firmware.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
where do i get this number from??
Boot into bootloader, connect your M8 to PC and run
fastboot getvar all
in cmd. Paste here what you got. But remove your IMEI and serial number.
Sent from my HTC One_M8 using XDA Free mobile app
HTCNerdYoda said:
Boot into bootloader, connect your M8 to PC and run
fastboot getvar all
in cmd. Paste here what you got. But remove your IMEI and serial number.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
waiting for device >
bootloader) version: 0.5
bootloader) version-bootloader: 3.16.0.0000
bootloader) version-baseband: 1.16.21331931.LA11G
bootloader) version-cpld: None
bootloader) version-microp: None
bootloader) version-main:
bootloader) version-misc: PVT SHIP S-OFF
bootloader) serialno:
bootloader) imei:
bootloader) imei2: Not Support
bootloader) meid: 00000000000000
bootloader) product: m8_ul_ca
bootloader) platform: hTCBmsm8974
bootloader) modelid: 0P6B12000
bootloader) cidnum: CWS__001
bootloader) battery-status: good
bootloader) battery-voltage: 0mV
bootloader) partition-layout: Generic
bootloader) security: off
bootloader) build-mode: SHIP
bootloader) boot-mode: FASTBOOT
bootloader) commitno-bootloader: c3d94491
bootloader) hbootpreupdate: 11
bootloader) gencheckpt: 0
As far as I an see a backup and stock recovery can be found here. But it still is the 1.xx.xxx . Nevertheless you could install this and run an OTA to get the latest 2.xx.xxx ROM and firmware vetsion.
Edit:
Regarding your bootloader version 3.16 you are still on 1.xx.xxx firmware so the backup and stock recovery on the link given above are going to work. After this you can go for the OTA. So - assuming again that you are on the stock ROM as written in you first post - what I would do is:
1) download CWS stock recovery and flash it:
adb reboot bootloader
fastboot flash recovery recoveryname.img
2) fastboot reboot
3) check for OTA and install the latest to get onto 2.xx.xxx ROM an firmware
Now you can flash custom revocery and either root the stock ROM or install a custom ROM designed for 2.xx.xxx firmware.
Alternatively the 1) you could download a CWS firmware.zip (don't know where to find it right away) and flash it:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
ATTENTION: DO THIS TWICE FOR FIRMWARE TO BE FLASHED COMPLETELY
fastboot flash zip firmwarename.zip
fastboot reboot
Sent from my HTC One_M8 using XDA Free mobile app
****.......this is soooo over my head.....thanks for your help but I don't want to mess my phone up. If there was a video on exact how to do it i would do it but all that looks confusing.
According to my experience video tutorials lead to more confusion and cause more havoc on the phone than to follow a good written guide and some help by the members of this forums.
The problem of video tutorials is that you never collect the experience in what your doing causes and thus do not understand why problems may arise, let alone how to solve them.
Sent from my HTC One_M8 using XDA Free mobile app
Related
After an OTA update my htc one x got into boot loop and the battery also stopped charging.
i charged the battery with the help of fashboot script and unlocked my boot loader and installed custom recovery. After that i charged my phone fully but still it is not starting. stuck at boot loop.
now i want to install stock ruu so please help to find the right ruu for my htc one x
CID-11111111
version-main-2.17.401.2
S-OFF
i tried to install /RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radi o_5.1204.162.29_release_298897_signed.exe
this one but it gave an error "Error [159]:image error. choose the correct rom.
please help thanks in advance:crying:
You have S-OFF and SuperCid, so I think the RUU method should work, but maybe first change the CID to another like HTC__001 or HTC__E11 using command like in fastboot mode:
"fastboot oem writecid HTC__001"
Yep should work
Or flash the 1.39 hboot firmware and then the 3.14 ruu
Sent from my HTC One X using XDA Premium 4 mobile app
Mr Hofs said:
Yep should work
Or flash the 1.39 hboot firmware and then the 3.14 ruu
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mr Hofs thanks for your kind reply
i tried JB FW easy flasher tool. It changed my CID from 11111111 to HTC_621 and tried to flash firmware but it got stuck at sending 'zip' and phone remains at silver htc logo.
so far i tried to run RUU with my cid as 11111111
shall i try to run RUU after my cid changed to HTC_621
and i dont know how to upgrade hboot.
sir please guide
So your fastboot works......well download the 3.14.401 firmware zip file from the firmware placeholder thread (where you also posted in)
Rename the zip file to firmware.zip and flash it
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
This all needs to be done with a locked/relocked bootloader.
Sent from my HTC One X using XDA Premium 4 mobile app
[SOLVED] HTC stuck in boot loop after OTA update
Mr Hofs said:
So your fastboot works......well download the 3.14.401 firmware zip file from the firmware placeholder thread (where you also posted in)
Rename the zip file to firmware.zip and flash it
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
This all needs to be done with a locked/relocked bootloader.
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mr Hofs first of all thank you very much for your help.
here is my story. i bought HTC one x 10 days ago. i am not aware of initial CID, hboot etc. i bought it from Taiwan and presently i am in india.
After two days there was an OTA i got my phone updated and all the problems started. it got into bootloop. This is the time i look for help on XDA. I did factory reset but of no use. After some time i realized battery is also not charging. Every time i plug the phone to pc or wall charger it starts automatically and gets into bootloop. With the help of XDA i found the fastboot script for charging the battery. After that i unlocked my phone and flashed the CWM recovery and got battery charged.
It is the time i came know about
UNLOCKED
S-OFF
version-main-2.17.401.2
Hboot-1.12.0000
CID-11111111
But the problem of not booting up still persisting.
i downloaded and tried
1. RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed_2
2. ruu_endeavor_u_jb_45_s_htc_europe_3.14.401.27_radio_5.1204.162.29_release_298897_signed
3. RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_TW_3.14.709.20_Radio_5.1204.162.29_release_292865_signed_2
and
4. RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed_2
first three RUU stuck at sending file and after 10 minutes or so gave error [159]:image error
The fourth one installed successfully without giving any error but the phone was still in bootloop.
I tried custom rom cyanogenmod 10.1 but it didnt install, it required higher version of Hboot.
Tried MIUI rom it got installed but the touch screen not working.
After that as you suggested i tried to update the firmware 3.14.401. The link you gave was not working may be temporarily. But it was already there on my pc. I didnt flashed it earlier because i was not sure whether this was correct firmware for my phone.
A week passed in above mentioned research.
Today i flashed the firmware and it gave and error with the message to flash it again immediately. So again i run the command but noting happened. so after 15 minutes i removed the phone from pc and restarted it and there it was Hboot-1.39.
So i tried the RUU no. 3 (mentioned above). This time it stuck at erasing user data for about 30 minutes so again i removed the phone from pc.
After that i installed cyanogenmod 10.1 nightly.
Now the phone is working put some features are not working like camer. i think this may be the fault of rom..
Sir should i flash the firmware again?
What i do know to go back to stock or custom rom fully functional and similar to stock.
Well anyway i had lost the hope and with your kind support i made is of some use. Thanks again
Try any other sense based rom, all roms should work on that hboot (1.39) even all sense 5 roms.
So try SD rom, or viper x 4....just to name a few....or arhd, doesn't matter wich one actually. Just try one and get back
Sent from my HTC One X using XDA Premium 4 mobile app
Mr Hofs said:
Try any other sense based rom, all roms should work on that hboot (1.39) even all sense 5 roms.
So try SD rom, or viper x 4....just to name a few....or arhd, doesn't matter wich one actually. Just try one and get back
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So there is no need of flashing the firmware again?
poonforce said:
So there is no need of flashing the firmware again?
Click to expand...
Click to collapse
Nope !
Sent from my HTC One X using XDA Premium 4 mobile app
Mr Hofs said:
Nope !
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sir now the camera is not working. when i switch on the camera it displays distorted static colors instead of image, its totally garbled.
and in SD rom the even after inserting the sim there is no network.
whereas in cyanogenmod network was there. only the camera was having the same problem.
and sometimes there is error "command write failed" using fastboot commands
And sir sometimes commands does not works. It hangs at sending .... even in ruu also it stuck at erasing data, sometime at rebooting to bootloader and sometime at sending... dont know what is happening .
And after flashing firmware 3.14. when i boot into boot loader there is one thing which comes in red for around one second or so.. "[preload] Failed to open usb mass storage" something like that..
dont know how to fix it.
poonforce said:
Sir now the camera not working in any custom rom. when i switch on the camera it displays the multicolor bars.
and in SD rom the even after inserting the sim there is no network.
whereas in cyanogenmod network was there. only the camera was having the same problem.
and sometimes there is error "command write failed" using fastboot commands
And sir sometimes commands does not works. It hangs at sending .... even in ruu also it stuck at erasing data, sometime at rebooting to bootloader and sometime at sending... dont know what is happening .
And after flashing firmware 3.14. when i boot into boot loader there is one thing which comes in red for around one second or so.. "[preload] Failed to open usb mass storage" something like that..
dont know how to fix it.
Click to expand...
Click to collapse
Run the command fastboot oem writecid HTC__032 and run RUU 3.14.401.27 and report what will happend
Thant said:
Run the command fastboot oem writecid HTC__032 and run RUU 3.14.401.27 and report what will happend
Click to expand...
Click to collapse
it gave an error "write failed invalid cid"
Try to use a USB 2.0 port (no USB 3.0)
You could try to disable virusscannersoftware
Download the stock recovery and boot.img from a 3.14.401.31 and flash them via fastboot firmware 3.14.401.31
Write CID to HTC__E11
Relock your bootloader
Flash a RUU via PC (execute .exe file) download RUU. I recommend a re-download, cause you had img error before.
webpatrick said:
Try to use a USB 2.0 port (no USB 3.0)
You could try to disable virusscannersoftware
Download the stock recovery and boot.img from a 3.14.401.31 and flash them via fastboot firmware 3.14.401.31
Write CID to HTC__E11
Relock your bootloader
Flash a RUU via PC (execute .exe file) download RUU. I recommend a re-download, cause you had img error before.
Click to expand...
Click to collapse
Sir i am using windows8 and not able to extract recovery and boot image from the RUU 3.14.401.31. any idea how to extract on windows.
The firmware is a zip file open it with 7zip and copy the boot.img and recovery from it and flash it
And btw, flashing boot and recovery files has to be done with a UNLOCKED bootloader, installing ruu files and flashing firmware files has to be done with a LOCKED/RELOCKED bootloader !
sent from my .......
Thanks to XDA and all the members who helped me in repairing my HTC ONE X.
continuing from last post.
As suggested by Webpatrick i installed stock recovery and boot image extracted from firmware 3.14.401.31.
tried to change my cid to HTC_E11 but it gave an error. i could change my cid to HTC_621 only.
so after done above i tried to install ruu http://htc.vi8.info/hTC-One-X/RUU_E...Radio_5.1204.162.29_release_302015_signed.exe
It gave cid error. So i changed my cid back to Supercid and again run the said RUU.
This time it flashed my HOX successfully. now i have stock rom.
Soon i will post the nandroid backup of my phone hoping it will help somebody like me..
once again thanks to all.
poonforce said:
Thanks to XDA and all the members who helped me in repairing my HTC ONE X.
continuing from last post.
As suggested by Webpatrick i installed stock recovery and boot image extracted from firmware 3.14.401.31.
tried to change my cid to HTC_E11 but it gave an error. i could change my cid to HTC_621 only.
so after done above i tried to install ruu http://htc.vi8.info/hTC-One-X/RUU_E...Radio_5.1204.162.29_release_302015_signed.exe
It gave cid error. So i changed my cid back to Supercid and again run the said RUU.
This time it flashed my HOX successfully. now i have stock rom.
Soon i will post the nandroid backup of my phone hoping it will help somebody like me..
once again thanks to all.
Click to expand...
Click to collapse
Good for you!
Thanks for this latest update, it could help some people. Everybody should give such a detailed update after success, but many forget!
Unable to flsh with ruu
version: 0.5a
version-bootloader: 1.36.0000
version-baseband: 5.1204.162.29
version-cpld: None
version-microp: None
version-main: 3.14.720.24
serialno: HT245W121191
imei: 35918XXX1XXX301
product: endeavoru
platform: HBOOT-T30S
modelid: PJ461XX00
cidnum: HTC__038
battery-status: low
battery-voltage: 2854mV
devpower: 0
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
Can Any one suggest me which Ruu should i boot for this device i have tried falsshing
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_India_1.26.720.2_Radio_1.1204.90.13_release_251419_signed ---> its showing 140 Boot vershion error please help me ASAP my phone is not booting into os as well please let me know thanks in advance
lico1021 said:
This is assuming you didnt completely brick your phone which, was my situation. also assuming you can still access your start menu:
click start>settings> on the bottom next to Personal tab, select System.
now select Clear Storage(the icon should be a garbage can with files going into it)
I believe it prompts you to give it the okay. I dont remember if it told me i was going to lose all saved applications and contacts, BUT yeah I did lose all that stuff. That was more than fine considering my phone was ****ED! No apps would open there were errors all over the place and I couldnt get it to flash. Anyway, it hard resets, you see the att screen and it literally goes thru the whole customization setup you went thru when you first turned it on. THATS A GOOD SIGN! haha. it works perfectly.
CONCLUSION: This simple way put my phone right back to its original ATT settings down to the very last piece of crap, lol. BUT i was MOREEE than happy to see it. From there I was able to flash HardSPL(ROM that allows flashing of any other ROM your heart desires)...and the rest is history!
Hope this helps.
Click to expand...
Click to collapse
Answered you in another thread where you posted this. Do not spam this all over and wait at one place to get a responce. We have otherwise no idea where to answer anymore !
poonforce said:
Sir i am using windows8 and not able to extract recovery and boot image from the RUU 3.14.401.31. any idea how to extract on windows.
Click to expand...
Click to collapse
firmware link broken bro send fix it bro
cid: HTC__038
finished. total time: 0.106s
E:\htc\Fastboot HTC\Fastboot HTC\Fastboot HTC>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.72.0000
(bootloader) version-baseband: 3.1204.171.33
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.18.707.6
(bootloader) serialno: FA356W100083
(bootloader) imei: 353XXXXXXXXXX
(bootloader) product: enrc2b_u
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM3511000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3877mV
(bootloader) devpower: 58
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.478s
WILL DA ROM WORK IN THIS?
Hello,
I tried searching for htc's new firmware that came with sense 6 lollipop update anyone mind linking me to it please?
Depends if you have an unbranded device or one from your network. Post the results of fastboot getvar all (without your IMEI or serial number) and we'll go from there
EddyOS said:
Depends if you have an unbranded device or one from your network. Post the results of fastboot getvar all (without your IMEI or serial number) and we'll go from there
Click to expand...
Click to collapse
It's unbranded with S-OFF can change to super cid if needed
Code:
version: 0.5
version-bootloader: 3.19.0.000
version-baseband: 1.21.2133114
version-cpld: None
version-microp: None
version-main: 3.28.401.7
version-misc: PVT SHIP S-OFF
serialno: SH44XWM01171
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: df77f8b7
hbootpreupdate: 11
gencheckpt: 0
OK. Well the latest firmware is in the latest OTA so you can just download that and extract it from the OTA zip file. If you're wanting to update your device to Lollipop it's easier to just flash the 4.16.401.10 RUU (LINK) but obviously that'll wipe the phone but at least you'd know it's 100% stock and ready to go
EddyOS said:
OK. Well the latest firmware is in the latest OTA so you can just download that and extract it from the OTA zip file. If you're wanting to update your device to Lollipop it's easier to just flash the 4.16.401.10 RUU (LINK) but obviously that'll wipe the phone but at least you'd know it's 100% stock and ready to go
Click to expand...
Click to collapse
I already have my device running 5.0.2 cm12 but I'm still on old firmware from sense 6 kitkat, would you mind linking me to the OTA zip.
It's in the OTA thread in General, but here you go
https://www.androidfilehost.com/?fid=95916177934519040
I'd use 7-Zip for the extraction process
EddyOS said:
It's in the OTA thread in General, but here you go
https://www.androidfilehost.com/?fid=95916177934519040
I'd use 7-Zip for the extraction process
Click to expand...
Click to collapse
Thanks for the link got it downloaded now. Double checking it's the firmware.zip yes?
I been using winrar for over 8 years now never liked 7-zip
Yep, firmware.zip is what you want. Flash it in RUU mode and you're good to go
I use 7-Zip as it's free and not intrusive but each to their own
EddyOS said:
Yep, firmware.zip is what you want. Flash it in RUU mode and you're good to go
I use 7-Zip as it's free and not intrusive but each to their own
Click to expand...
Click to collapse
I have flashed it and i seemed to soft brick it any suggestions?
How did you flash the file (type the commands you used)?
EddyOS said:
How did you flash the file (type the commands you used)?
Click to expand...
Click to collapse
i typed
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip (FAILED)
fastboot flash zip firmware.zip (This one worked)
fastboot reboot
Of course after flashing new firmware it got rid of TWRP so I flashed the latest 2.8.5.0 then downloaded my rom again and dirty flashed it and it is working now.
Yeah, it does fail the first time and you then run it again and it flashes
EddyOS said:
Yeah, it does fail the first time and you then run it again and it flashes
Click to expand...
Click to collapse
It's all good mate, cheers for advice and help.
I went thru a few threads but couldn't find any direct tutorial to flash my m9. I downloaded ota, but i cant s-off my unit(sunshine doesn't work), thus i cant flash it. maybe its running new OS?
I wanted to flash any rom to my m9, either stock or wwe or cyanogenmod, but all seems to require s-off.
my play store is missing & even though i did a master reset(tried from normal menu n also bootloader mode), playstore just wont appear.
here are my details :
Non-rooted
S-ON
LK-1.0.0.0000
firmware 3.42.708.3
fastboot result :
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: Mod Edit: Removed
(bootloader) version-main: 3.42.708.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440801_97.04.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__044
I went thru about 5 threads but cant find a direct solution, I hope I'm not asking something that is widely posted here, seems i just can't S-off. Any helps to flash roms in my situation?
Anyone care to help out?
There is no other publicly available RUU for your SKU than a 1.32.708.15 one which you can't use due to downgrades not being possible without S-OFF.
Taken from my sticky thread in the general section:
Flippy498 said:
Llabtoofer's RUU Service
he can help you out if there is no freely available RUU for your phone​
Click to expand...
Click to collapse
dear flippy, can i install custom rom while its S-ON? I know how 2 do it on prev HTCs(unlock bootloader, flash recovery, flash rom, flash boot.img), but no sure if m9 is applicable..
Yes, you can. However you need to re-flash the stock boot.img of your phone afterwards or you'll loose your mobile reception (this only applies to sense-based roms). If you want to use a non-sense-based rom like cm you need to flash thicklizard's mono kernel instead of the stock boot image.
Sent from my HTC One M9 using XDA Labs
Hi,
A few weeks ago my M8 developed a serious problem - basically all calling functionality stopped working. The android basic dialer get's stuck dialing a number and eventually the system presents the standard 'Dialer is not responding' message, calling my number from another phone always gets an engaged tone, Skype and Whatsapp calling fails without any error messages. Also data connection fails, text messaging fails intermittently, music player fails to play through speakers and fails intermittently through Bluetooth.
This didn't occur after the install of any apps and the phone didn't experience any physical shocks, but seemed to happen after a Skype call.
Naturally, I tried factory reset first, but to no avail.
As the phone is now out of warranty I rooted it and installed the Android Revolution ROM onto it. (PS thanks to everyone for the wealth of help and guides to carrying this out.) I was hoping a new ROM would fix the problem, but it hasn't.
So, I'm assuming the problem is at a very low level, with some device driver(s).
My question is, does the ROM include all of the device drivers? Do I need to do something else to get the basic device drivers reinstalled? I note the download site for the Android Revolution ROM also has links to firmware downloads - should I also install the firmware download?
Any help would be much appreciated.
usmhot
I'd try RUU, if you M8 version has one. Otherwise, yes, I'd try to flash firmware, than re-install stock or custom ROM onto the phone. I don't think the AR firmware collection is very current. I'd use the stock, signed firmwares from ckpv5's thread (post #5): https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
If you need help determining if your version has RUU, or what firmware number to use, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
redpoint73 said:
I'd try RUU, if you M8 version has one. Otherwise, yes, I'd try to flash firmware, than re-install stock or custom ROM onto the phone. I don't think the AR firmware collection is very current. I'd use the stock, signed firmwares from ckpv5's thread (post #5): https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
If you need help determining if your version has RUU, or what firmware number to use, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
Mine's an Irish (so I assume international) variant - so I'm not sure if there's an RUU available (some google result seemed to imply HTC only release RUUs for the States??)
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.12G
version-cpld: None
version-microp: None
version-main: 6.13.771.4
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: H3G__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 76df2b54
hbootpreupdate: 11
gencheckpt: 0
Bump. Can anyone tell me if there is an RUU available for my variant?
usmhot said:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.12G
version-cpld: None
version-microp: None
version-main: 6.13.771.4
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: H3G__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 76df2b54
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
usmhot said:
Mine's an Irish (so I assume international) variant - so I'm not sure if there's an RUU available (some google result seemed to imply HTC only release RUUs for the States??)
Click to expand...
Click to collapse
Some other versions (besides US) have RUU, but unfortunately I don't think your version (H3G) is one of those.
One idea, which I touched upon before, is to flash the firmware (since you don't think flashing the ROM alone won't help - the firmware is basically the "lower level drivers" you are talking about), then restore a stock TWRP backup (ROM). Its as close to a RUU "factory image" as you'll get, since there is no RUU (that I am aware of).
To do this, you'll need to relock the bootloader, and flash the 6.13.771.4 from Post #5 of the following thread:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Then you'll need to unlock the bootloader again, install TWRP back to the phone (flashing the firmware overwrites TWRP with stock recovery). Then flash the stock TWRP backup 6.13.771.4 from Post #3 of the same thread, using instructions in Post #1.
redpoint73 said:
To do this, you'll need to relock the bootloader, and flash the 6.13.771.4 from Post #5 of the following thread:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Then you'll need to unlock the bootloader again, install TWRP back to the phone (flashing the firmware overwrites TWRP with stock recovery). Then flash the stock TWRP backup 6.13.771.4 from Post #3 of the same thread, using instructions in Post #1.
Click to expand...
Click to collapse
I've had a go at relocking the bootloader following the instructions in http://www.droidviews.com/how-to-reset-unlocked-status-to-locked-on-htc-one-m8/
i.e. using the following sequence of commands
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
exit
Click to expand...
Click to collapse
but it's not working for me - it still shows as *** Unlocked ***
Couple of things:
1. if I issue the command adb devices (after a full reboot to system) first I get an error message "adb server version (31) doesn't match this client (36)" and my device id is listed anyway, but if I reissue the command I get my device id listed without the error. Do I need a different version of adb?
2. do I need to unroot as well as relock? (If so, is there a guide somewhere?)
usmhot said:
I've had a go at relocking the bootloader following the instructions in http://www.droidviews.com/how-to-reset-unlocked-status-to-locked-on-htc-one-m8/
Click to expand...
Click to collapse
You're making much harder on yourself than need be.
The process to relock the bootloader is in the instructions for flashing the firmware, which I already directed you to (Post #5 of the previously linked thread). Near the bottom of that post, below all the download links (so maybe you missed seeing the instructions).
Relocking the bootloader is a single, easy fastboot command:
fastboot oem lock
This will make the bootloader say RELOCKED, which is sufficient to flash the firmware.
The guide you linked is to make it say LOCKED (versus RELOCKED) and the only reason to do that is to fool HTC into thinking it was never UNLOCKED for warranty purposes. You don't need to do this, and you can't since the guide clearly says s-off is required, which you do not have (you are s-on).
Sorted :good:. And it did indeed fix the core problem with the dialer etc. I know have an apparently fully working phone again.
Many many thanks for this.
usmhot said:
Sorted :good:. And it did indeed fix the core problem with the dialer etc. I know have an apparently fully working phone again.
Many many thanks for this.
Click to expand...
Click to collapse
Glad it worked. You're quite welcome, and happy to have helped!
After a long wait I finally got my ota update to Nougat.
But there is another problem, I cant finish the update because my phone showed that error.
I'm on stock M9 in bootloader it says software status official, locked, and s-on. No root, as I have checked it using root checker. Recovery is there.
I never modified my phone. And its fine back when I updated from lollipop to mm via ota, there is no problem.
And as far as I know, my phone is on correct mid and cid, SKU 708, mid 0PJA10000 exactly the same with mid engraved on my phone, and cid HTC__044
But when I update mm to nougat, this variant system version error shows up
I have tried to flash RUU of my current firmware, but still nothing.
Please help me, where did I do wrong? or how can I solve this problem?
Bumping this because I got the same thing too.
My device is not even rooted!
Did you guys flash a RUU for your current firmware and try to download the OTA, again?
Flippy498 said:
Did you guys flash a RUU for your current firmware and try to download the OTA, again?
Click to expand...
Click to collapse
I did, but the problem stays there.
Flippy498 said:
Did you guys flash a RUU for your current firmware and try to download the OTA, again?
Click to expand...
Click to collapse
I dont know how to flash the RUU.
But anyway, is there a way to check whether i can flash the OTA on my own?
vglaksana said:
I did, but the problem stays there.
Click to expand...
Click to collapse
Can you please copy and paste the fastboot getvar all output here (without your IMEI!)? It might help us to help you.
-marco- said:
I dont know how to flash the RUU.
Click to expand...
Click to collapse
Well, there is a thread pinned above all the other threads in this section that is even called "ReadMe" and people still tend to completely ignore it...
-marco- said:
But anyway, is there a way to check whether i can flash the OTA on my own?
Click to expand...
Click to collapse
If you can't flash an OTA via the software update function then you can't flash it via fastboot, either. Your phone doesn't pass the security checks that google implemented with android 5 so the method you use for flashing the OTA doesn't matter.
Flash a RUU and re-try to install the OTA. If that still doesn't matter then please copy and paste your fastboot getvar all output here (without your IMEI!), as well.
Flippy498 said:
Can you please copy and paste the fastboot getvar all output here (without your IMEI!)? It might help us to help you.
Click to expand...
Click to collapse
Here it is
C:\Users\Vito G. Laksana\Desktop\New folder>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 3.42.708.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U114,10801_97.64.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC 044
all: inished. total time: 0.016s
Above is getvar all from before I flashed my current RUU. I believe it wouldn't change anything, as I can't get fastboot getvar all working now.
vglaksana said:
(bootloader) cid: HTC 044
Click to expand...
Click to collapse
If that is an exact copy of the output then it's no miracle that you can't install the OTA. That CID doesn't exist. It needs to be HTC__044 (8 letters, numbers or symbols in total and no spaces). You need S-OFF for being able to correct your CID.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
If that is an exact copy of the output then it's no miracle that you can't install the OTA. That CID doesn't exist. It needs to be HTC__044 (8 letters, numbers or symbols in total and no spaces). You need S-OFF for being able to correct your CID.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Ah my bad. The correct CID is HTC__044, as I mentioned in the thread first post.
I just using image to text converter because I have screencap of the output and didn't see that straight away.
Ah ok. And I already hoped that we found the cause of the problem... There have been some threads about devices that got bought in the US, S-OFFed and reflashed to non-US versions for selling them in other countries, in the past (around the time when firmware 2.x was the latest one). In most cases the sellers didn't convert the phones correctly and the buyers faced similar errors to your one when they tried to install an OTA.
Unfortunately there's nothing strange I can find in that output, then.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Ah ok. And I already hoped that we found the cause of the problem... There have been some threads about devices that got bought in the US, S-OFFed and reflashed to non-US versions for selling them in other countries, in the past (around the time when firmware 2.x was the latest one). In most cases the sellers didn't convert the phones correctly and the buyers faced similar errors to your one when they tried to install an OTA.
Unfortunately there's nothing strange I can find in that output, then.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thanks for helping me figuring out the problem.
If that is the problem, then why I have successfully update from lollipop to mm?
Yes i did buy it second hand, he said that the phone is from Singapore, and from the getvar output it is make sense that my phone came from Singapore.
Soo...I believe my only option is to S-OFF and convert to other version to get the update, is that correct?
I just re-read your opening post. Looks like I missed the part with the engraving. The US variant has a different engraving than the one you mentioned. So my assumption is probably wrong.
Since I have no clue what might cause your problem I actually don't see any other solution than getting S-OFF and converting the phone.
If there was a publicly available 4.x RUU for your SKU you could have asked Sneakyghost whether he creates a firmware package for you. By flashing that (S-OFF needed) you would have been able to use the 4.x RUU although you never installed the corresponding OTA. This way you could have kept your SKU. However, I haven't seen a public download link for such a RUU, yet. Therefore, you'll need to convert to a different SKU if you want the latest firmware.
Since you're still on firmware 3.x you need to flash one of Sneakyghost's 4.x packages before you can flash a 4.x RUU of the SKU that you want to convert to. Or you use a 3.x RUU for converting and try to install the OTA of the new SKU, afterwards. (The latter will probably take longer in total.)
Alternatively, you can wait some more days and see if some else has a better idea.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Can you please copy and paste the fastboot getvar all output here (without your IMEI!)? It might help us to help you.
Click to expand...
Click to collapse
I rebooted into bootloader to get the getvar but it doesnt work.
adb lists no devices.
Also, see the enclosed pic. that's as far as i managed to get.
Adb won't work if the device isn't booted to system or recovery mode.
And since the fastboot mode doesn't exist anymore on the M9 and all newer HTC phones you need to boot to download mode.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Adb won't work if the device isn't booted to system or recovery mode.
And since the fastboot mode doesn't exist anymore on the M9 and all newer HTC phones you need to boot to download mode.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
booted to system: adb sees device but says it's offline
booted to dl mode: adb can't see the device.
anyway, i took picture of what dl mode looks like. Attached.
Yeah, that's how it's supposed to be. ADB can only be used if the phone is booted to the system or the recovery mode. You can't use ADB commands while it's booted to the bootloader or the download mode. You need to use fastboot commands in these modes.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Yeah, that's how it's supposed to be. ADB can only be used if the phone is booted to the system or the recovery mode. You can't use ADB commands while it's booted to the bootloader or the download mode. You need to use fastboot commands in these modes.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
apparently i had a problem with drivers. i have fixed it now, that's why it gave empty devices.
Ok went back to bootloader mode. run fastboot getvar all:
Code:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT54GYJ05021
all:
finished. total time: 0.132s
this is instead the same taken from dl mode:
Code:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.42.708.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440801_97.04.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__044
all:
finished. total time: 0.006s
what now?
Mhm, there's nothing strange in that output, either.
Can you flash a RUU and re-try installing the OTA? If that doesn't fix the problem then the only other option is converting the phone as I already suggested to vglaksana.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Can you flash a RUU and re-try installing the OTA?
Click to expand...
Click to collapse
can you point me to a guide on how to do this?
and also where can i find my relevant RUU?
thanks.
I already did so in my first reply to you.
Sent from my HTC One M9 using XDA Labs