Develop Bugs

Hi, need some help

Ive been reading this section of the forum for 2 nights now. read various threads and none the wiser.
Ive unlocked my htc one x using the windroid htc one app which worked fine, but installing a rom was not as easy. now < i admit, i dived in and installed a ROM without seeing what else it needs to work ( am used to flashing nexus roms) and now its stuck at the HTC screen. Now i've tried various ways to rectify the proplem. uisng various roms, flashing boot.img before flashing the rom, no go. tried older roms, no go.
I know the hboot needs updating, but without a cid id then i cant find a matching firmware.zip.
Ive tried to do a RUU boot by locking the bootloader but get this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip rom.zip
sending 'zip' (153709 KB)...
OKAY [ 19.444s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 29.009s
So am at a loss and asking for help.
(bootloader) version: 0.5a
(bootloader) version-bootloader: 0.95.0000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.11
(bootloader) serialno: HT
(bootloader) imei:
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: None
(bootloader) battery-status: good
(bootloader) battery-voltage: 3990mV
(bootloader) devpower: 82
(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
hope the above info helps.

ajg008 said:
Ive been reading this section of the forum for 2 nights now. read various threads and none the wiser.
Ive unlocked my htc one x using the windroid htc one app which worked fine, but installing a rom was not as easy. now < i admit, i dived in and installed a ROM without seeing what else it needs to work ( am used to flashing nexus roms) and now its stuck at the HTC screen. Now i've tried various ways to rectify the proplem. uisng various roms, flashing boot.img before flashing the rom, no go. tried older roms, no go.
I know the hboot needs updating, but without a cid id then i cant find a matching firmware.zip.
Ive tried to do a RUU boot by locking the bootloader but get this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip rom.zip
sending 'zip' (153709 KB)...
OKAY [ 19.444s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 29.009s
So am at a loss and asking for help.
(bootloader) version: 0.5a
(bootloader) version-bootloader: 0.95.0000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.11
(bootloader) serialno: HT
(bootloader) imei:
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: None
(bootloader) battery-status: good
(bootloader) battery-voltage: 3990mV
(bootloader) devpower: 82
(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
hope the above info helps.
Click to expand...
Click to collapse
Lock your bootloader fastboot oem lock after this run RUU 1.29.401.11 as administrator and follow the instruction. After RUU finish update the phone to latest JB from Settings/About/Software Updates!
Report back

thanks. Downloading now, will try when i return home from work

Thant said:
Lock your bootloader fastboot oem lock after this run as administrator and follow the instruction. After RUU finish update the phone to latest JB from Settings/About/Software Updates!
Report back
Click to expand...
Click to collapse
thanks for your help that got the phone back to booting properly
I flashed it and it worked. I got myself back to the latest update. Now i tried various roms again as i'm one for experimenting but some of the newest ones dont seem to want to work.
ones i've tried>
Android_Revolution_HD-One_X_33.1
HTC_One_X_-_MaximusHD_21.0.0
OneX The Next Chapter! v1.2
but none of them worked for me.
So i went lower with
cm-10.1.3-endeavoru which worked
then updated to
cm-10.2.0-endeavoru and flashed the boot.img for it to work.
Now for the other roms, what am i missing? is it the firmware.zip? hboot level?
Am bowing down to Thant, and hoping he can tell a mere minion what he's doing wrong

I don't think you updated far enough ! Post the outcome of :
Fastboot getvar version-main
Edit :
I see thant is offline, so i chip in......

Mr Hofs said:
I don't think you updated far enough ! Post the outcome of :
Fastboot getvar version-main
Edit :
I see thant is offline, so i chip in......
Click to expand...
Click to collapse
the result is:
version-main: 2.17.401.2

What i thought. You need to run another ruu and update many more ota's
Here is the ruu
http://www.persianhtc.net/index.php...Radio_2.1204.135.20_release_274900_signed.exe

Mr Hofs said:
What i thought. You need to run another ruu and update many more ota's
Here is the ruu
[ul]h*tp://w*w.persianhtc.net/index.php?dir=One%20X%28Endeavor%29/rom/original/exe/&file=RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe[/url]
Click to expand...
Click to collapse
downloading now, but need sleep now and will report back tomorrow.
thanks very much for your help.
bows to Mr Hofs

Same here.

cyanogenmod stable rom not recognising sim, and not being recognised by htc sync
Hi i just unlocked and rooted my phone. one of the first things i did after having rooted it was go into rom-manager and download the highest rated cyanogen mod stable rom...expecting it to reboot itself and do the update automatically once id downloaded the file i was suprised when nothing happened...so i put it into recovery mode myself and searched the phone's storage for the rom file...it was infact two files, one the rom, the other gapps...i installed both of them and rebooted the phone...at first i was left on cyanogenmod bootloop...after a few restarts, and factory resets, i eventually got past the cyanogen mod intro wheel, to its actual introduction *asking me to choose a language*, as soon i choose my language i get notification asking me to insert my simcard (it already is, OF COURSE...), as i go through the rest of the setup there is no network coverage or internet..so i cant simply download rom-manager and try another flash..it also wont come up as a recognised device on my macbook...ive downloaded another flash of cyanogenmod on my laptop along with a new gapps, but im utterly lost about what to do now...i cant even put them on the phone....
wud love any help
The recovery version I'm using is clockworkMod Recovery v5.8.2.7
And here is my bootloader
ENDEAVORU PVT SHIP 2-ON RL
HBOOT-1.72.0000
CPLD-None
RADIO-5.1204.167.31
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Jun 21 2013,18:24:21

tekkr said:
Hi i just unlocked and rooted my phone. one of the first things i did after having rooted it was go into rom-manager and download the highest rated cyanogen mod stable rom...expecting it to reboot itself and do the update automatically once id downloaded the file i was suprised when nothing happened...so i put it into recovery mode myself and searched the phone's storage for the rom file...it was infact two files, one the rom, the other gapps...i installed both of them and rebooted the phone...at first i was left on cyanogenmod bootloop...after a few restarts, and factory resets, i eventually got past the cyanogen mod intro wheel, to its actual introduction *asking me to choose a language*, as soon i choose my language i get notification asking me to insert my simcard (it already is, OF COURSE...), as i go through the rest of the setup there is no network coverage or internet..so i cant simply download rom-manager and try another flash..it also wont come up as a recognised device on my macbook...ive downloaded another flash of cyanogenmod on my laptop along with a new gapps, but im utterly lost about what to do now...i cant even put them on the phone....
wud love any help
The recovery version I'm using is clockworkMod Recovery v5.8.2.7
And here is my bootloader
ENDEAVORU PVT SHIP 2-ON RL
HBOOT-1.72.0000
CPLD-None
RADIO-5.1204.167.31
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Jun 21 2013,18:24:21
Click to expand...
Click to collapse
Rom manager not working on S-ON devices flash the boot.img manually from fastboot with command fastboot flash boot boot.img take the boot.img from rom arhiv wich you want to install

Thant said:
Rom manager not working on S-ON devices flash the boot.img manually from fastboot with command fastboot flash boot boot.img take the boot.img from rom arhiv wich you want to install
Click to expand...
Click to collapse
the reason i'm so frustrated is aside from the supposedly stable build of cyanogen mod i downloaded in rommanager not working, the rom doesnt recognise my sim, i dont have access to the internet, so i cant simply download a new rom to flash straight from rom manager...as well as this the wifi doesn't seem to work on this flash...and to make matters worse it's not being recognised by the drivers...i'm using htc sync manager..when i plug in the phone it will open htc sync manager but wont show that a phone is paired to my macbook
...when u say manually can i do this directly from my phone or do i need to connect it to a computer?

You must connect it to PC..And then go to fastboot and flash boot.img file..Then you will have signal,wifi etc..

big noob said:
You must connect it to PC..And then go to fastboot and flash boot.img file..Then you will have signal,wifi etc..
Click to expand...
Click to collapse
its not being recognised as a device since i flashed the *cyanogen mod stable rom*...i plugged it to my computer though, and put it into fastboot and it says FASTBOOT USB...the options it gives me from here are
HBOOT
REBOOT
REBOOT BOOTLOADER
POWER DOWN

Here is guide how to use ADB on macbook:
http://forum.xda-developers.com/showthread.php?t=1917237
And then you can use fastboot commands..

Mr Hofs said:
What i thought. You need to run another ruu and update many more ota's
Here is the ruu
[ul]ht*p://w*w.persianhtc.net/index.php?dir=One%20X%28Endeavor%29/rom/original/exe/&file=RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe[/url]
Click to expand...
Click to collapse
ive tried that but keep getting signature error

ajg008 said:
ive tried that but keep getting signature error
Click to expand...
Click to collapse
Relocked the bootloader ?

Mr Hofs said:
Relocked the bootloader ?
Click to expand...
Click to collapse
yep fastboot oem lock

Then it might be easier to flash the 3.14.401 firmware to upgrade the hboot to 1.39. Then you can flash any rom you want, and there is also a ruu for that. Sorry i have no time to explain now (heading home from work)
Look for the firmware placeholder thread, read the instructions and download the 3.14.401 firmware.zip from there.
http://forum.xda-developers.com/showthread.php?t=1957376

Mr Hofs said:
Then it might be easier to flash the 3.14.401 firmware to upgrade the hboot to 1.39. Then you can flash any rom you want, and there is also a ruu for that. Sorry i have no time to explain now (heading home from work)
Look for the firmware placeholder thread, read the instructions and download the 3.14.401 firmware.zip from there.
[rl]htp://forum.xda-developers.com/showthread.php?t=1957376[/url]
Click to expand...
Click to collapse
i already had the ota 3.14.401 and got the firmware.zip from there.
its installed fine and i now can put most roms onto it.
:victory: thank you Mr Hofs
So i get this right in my head. The phones firmware.zip needed updated so it would update hboot and other things.
Now to flash roms is the procedure to flash the boot.img contained inside first then install the rom <----which is they way ive being doing it

No OS installed. Can't transfer files.

Alrighty, so I was rooting my Htc m8 and installing a rom called android revolution and something went wrong. Now my phone won't go past the htc bootscreen or would get stuck in a loop.
On bootloader mode I can see instead of S-Off, I see Tampered.
I'm currently on TWRP 2.7.0.2 and while trying to fix this, i erased cashe and wiped and on doing so, I wiped the OS. So when I try to reboot, it says no OS installed.
I read online on how to fix this and it said to install another rom over it, that way it can boot into the rom. However, I can't transfer any files onto my phone while its in recovery mode.
I checked how to transfer files and tried using adb push. That didn't work either. When i used the command prompt and wrote 'adb devices' It said ''list of devices attached'' without anything underneath where there shouldve been a serial number. So when I wrote adb push, there were no devices attached.
I tried to reinstall adb drivers twice and I definitely see its there.
Am I wrong somewhere? How do I fix my phone? Is there an easier way to transfer files onto my phone?

I can suggest to flash the latest twrp recovery. It mounts the sdcard as a mtp and as a disk drive (in my case) or get an sdcard with a reader and put a rom on it via the pc and insert it in the phone and flash the rom

I don't really have an sdcard or reader. I'll try the new twrp but how is it any different than this? Will it help me transfer more easily?
update: I tried adb sideload with two roms, but of them loaded to 100% on cmd prompt, but on my phone it says:
ADB sideload complete
Failed
update 2: when flashing the recovery, it said:
waiting 'flash' ...<bootloader> signature checking...
FAILsignature verify fail
FAILED <remote: signature verify fail>

Shiverfire said:
I don't really have an sdcard or reader. I'll try the new twrp but how is it any different than this? Will it help me transfer more easily?
update: I tried adb sideload with two roms, but of them loaded to 100% on cmd prompt, but on my phone it says:
ADB sideload complete
Failed
update 2: when flashing the recovery, it said:
waiting 'flash' ...<bootloader> signature checking...
FAILsignature verify fail
FAILED <remote: signature verify fail>
Click to expand...
Click to collapse
hmm can you post the outcome of :
fastboot getvar all (delete the imei and serial before posting it)

(bootloader) version-baseband: 1.16.21331931.LA11
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(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: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

I'm missing the bootloader info, what hboot is the device on ? (3.16/3.18/3.19) CWS thats at&t device right ?

this is exactly what it says on the hboot mode:
M8_UL_CA PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.1621331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 18 2014, 16:06:33.0
and yes, its an at&t, but im not in the usa.

The latest twrp probably doesn't work because of the lower (3.16) hboot. Adb sideload should work or get a sdcard that's the easiest way

Mr Hofs said:
The latest twrp probably doesn't work because of the lower (3.16) hboot. Adb sideload should work or get a sdcard that's the easiest way
Click to expand...
Click to collapse
adb sideload didnt work like I said. I just got an sdcard. Trying that now. WIll let you know.

Shiverfire said:
adb sideload didnt work like I said. I just got an sdcard. Trying that now. WIll let you know.
Click to expand...
Click to collapse
Ah yes i know that it didn't work here in your case but in general it should work. Not sure as i never needed it myself

I tried flashing two different roms with an external sd card and it failed almost immediately.
Is there anything else I can do? Does anyone have a backup I can restore to?

Shiverfire said:
I tried flashing two different roms with an external sd card and it failed almost immediately.
Is there anything else I can do? Does anyone have a backup I can restore to?
Click to expand...
Click to collapse
What's the error ? What failed ? You can't flash the newer roms due to your low hboot.
Ow and there is a great backup thread stickied in the general section. It's worth a lot to have careful read there !

here is what it says on my twrp:
Updating partition details. . .
Full SELinux support is present.
Installing '/external_sd/rom.zip' . . .
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
Verifying zip signature. . .
E:Zip signature verification failed: 1
Error flashing zip '/external_sd/rom.zip'
Updating partition details. . .
Failed
ok so can you suggest what rom I use? and what update of the rom that will work on my hboot? Anything will do, I just need to get my phone running.
After that, I can try updating the hboot so the newer roms work.
For reference, the roms I was using Android Revolution (the Lolipop verision) and Skydragon.

You got to get your hands on a older kitkat based roms. When you go for a rom based on 1.54.xxx you are good to go.

Mr Hofs said:
You got to get your hands on a older kitkat based roms. When you go for a rom based on 1.54.xxx you are good to go.
Click to expand...
Click to collapse
ok im currently downloading this:
Download Android Revolution HD 22.2
Stock ROM's (Android 4.4.4 + HTC Sense 6.0 | Latest: 3.28.401.9)
In the meantime, do you have any idea how to update my hboot so the newer roms work? Is the Tampered bar have to do with any of this?

Sorry for double posting, but I used the sdcard to download a kitkat rom and it worked. The bootscreen takes about 5-10 minutes and still has the following error:
This build is for
development purposes only
Do not distribute outside of HTC
without HTC's written permission
Failure to comply may
lead to legal action
however, the phone works fine. Thank you!

H3G__001 stock lollipop nandroid

Hi im trying to update to lollipop on my 3 UK branded m8 but im having serious issues upgrading to 4.4.4 eye experience version 3.32.771.3 was wondering if anyone has or could get a nandroid of the stock 4.20.771.2 ROM. I can see an OTA in http://forum.xda-developers.com/showthread.php?t=2701376 but I have no idea how to use those OTA files. Any help would be appreciated.

Post your fastboot getvar all result (minus serial no. & imei no.)
then we know which backup that you really need.
No point to give you 4.20.771.2 backup for now.

ckpv5 said:
Post your fastboot getvar all result (minus serial no. & imei no.)
then we know which backup that you really need.
No point to give you 4.20.771.2 backup for now.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.771.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
hmmm it says OS version 4.20.771.2 there but in about phone --> software info. it says 2.22.771.5 for software number. not sure what that means?!

Try restore my backup and see how it goes : http://forum.xda-developers.com/showpost.php?p=58781201&postcount=4598

ckpv5 said:
Try restore my backup and see how it goes : http://forum.xda-developers.com/showpost.php?p=58781201&postcount=4598
Click to expand...
Click to collapse
cool thanks. I tried your nandroid backup and it starts up fine but I cant connect to my wifi network. It sees the network but it wont connect. It does allow me to connect to another open network I can see but not my own. This happened on one of the stock updates I did too. Any ideas why this might be? or how it might be fixed?

f_padia said:
cool thanks. I tried your nandroid backup and it starts up fine but I cant connect to my wifi network. It sees the network but it wont connect. It does allow me to connect to another open network I can see but not my own. This happened on one of the stock updates I did too. Any ideas why this might be? or how it might be fixed?
Click to expand...
Click to collapse
There are two options :
1. Restore 3.32.771.10 backup and its stock recovery image then do OTA to 4.20.771.2
You can have all the needed files here : http://forum.xda-developers.com/showpost.php?p=55322461&postcount=1897
Or
2. Reflashed the untouched 4.20.771.2 firmware that linked here : http://forum.xda-developers.com/showpost.php?p=58781201&postcount=4598
but you need to relock bootloader in order to do that.
a. put your device in bootloader/fastboot mode
b. relock bootloader - fastboot oem lock
c. run these commands
fastboot oem rebootRUU
fastboot flash zip 4.20.771.2_firmware.zip
fastboot flash zip 4.20.771.2_firmware.zip .....( again for the 2nd time)
fastboot reboot
d. check your wifi
For me .. 1st option is a better choice

ckpv5 said:
There are two options :
1. Restore 3.32.771.10 backup and its stock recovery image then do OTA to 4.20.771.2
You can have all the needed files here : http://forum.xda-developers.com/showpost.php?p=55322461&postcount=1897
Or
2. Reflashed the untouched 4.20.771.2 firmware that linked here : http://forum.xda-developers.com/showpost.php?p=58781201&postcount=4598
but you need to relock bootloader in order to do that.
a. put your device in bootloader/fastboot mode
b. relock bootloader - fastboot oem lock
c. run these commands
fastboot oem rebootRUU
fastboot flash zip 4.20.771.2_firmware.zip
fastboot flash zip 4.20.771.2_firmware.zip .....( again for the 2nd time)
fastboot reboot
d. check your wifi
For me .. 1st option is a better choice
Click to expand...
Click to collapse
so I tried option 2 first and that didnt work Then I tried option 1. Flashing 3.32.... worked ok wifi working etc. I then did the OTA that popped up. That flashed and it boots up but system ui force closes and wifi doesnt turn on at all Is there anyway to flash your OTA update specifically and avoid downloading and flashing the one that pops up on screen?

f_padia said:
so I tried option 2 first and that didnt work Then I tried option 1. Flashing 3.32.... worked ok wifi working etc. I then did the OTA that popped up. That flashed and it boots up but system ui force closes and wifi doesnt turn on at all Is there anyway to flash your OTA update specifically and avoid downloading and flashing the one that pops up on screen?
Click to expand...
Click to collapse
You can't flash OTA manually because your device is S-On.
When you have system ui force close and wifi doesn't turn on at all ... that's a good sign.
What you need to do now is unlock bootloader again with unlock_code.bin that you received from HTC. Then install TWRP 2.8.5.0. Boot to TWRP recovery, select mount - advance - format data - yes
Reboot - check your wifi again - system ui should work and wifi should work too.
Then restore my 4.20.771.2 backup (reason is when re-unlock bootloader and format data .. all data files such as calculator & flashlight & etc are removed)
EDIT : before you do the above, please try boot to recovery where you see the red triangle .. press & hold volume up & press power once.
In stock recovery, select factory reset/wipe data ... reboot

ckpv5 said:
You can't flash OTA manually because your device is S-On.
When you have system ui force close and wifi doesn't turn on at all ... that's a good sign.
What you need to do now is unlock bootloader again with unlock_code.bin that you received from HTC. Then install TWRP 2.8.5.0. Boot to TWRP recovery, select mount - advance - format data - yes
Reboot - check your wifi again - system ui should work and wifi should work too.
Then restore my 4.20.771.2 backup (reason is when re-unlock bootloader and format data .. all data files such as calculator & flashlight & etc are removed)
EDIT : before you do the above, please try boot to recovery where you see the red triangle .. press & hold volume up & press power once.
In stock recovery, select factory reset/wipe data ... reboot
Click to expand...
Click to collapse
before I saw your message I did a factory rest from stock recovery as you suggested in your edit and system ui force close was fixed and wifi does turn on... but im back to the problem of not being able to connect to my wifi network. I've managed to connect to 2 separate open (public) networks fine but cant connect to mine for some reason. I cant understand why this might be happening.
Thanks for all the help by the way really appreciate it!

That's something I'm not familiar with as I never have that problem before. I read a few thread of this kind of wifi problem .. there are a few suggestions such as reset the router, try change wifi password and a few more like 2.4GHz & 5.0 GHz problem
Maybe someone else more familiar with this kind of problem will step in.

ckpv5 said:
That's something I'm not familiar with as I never have that problem before. I read a few thread of this kind of wifi problem .. there are a few suggestions such as reset the router, try change wifi password and a few more like 2.4GHz & 5.0 GHz problem
Maybe someone else more familiar with this kind of problem will step in.
Click to expand...
Click to collapse
I had a look around and came across this http://www.pcadvisor.co.uk/how-to/g...llipop-solve-wi-fi-problems-on-nexus-devices/ where it suggests changing wifi router channel. I did and it works
Cant thank you enough dude. i've tried to thank all your posts to reflect how many thanks you deserve! At one point when one of the software updates went bad and the screen wouldnt turn on I was told HTC would charge around £200 to fix it! so yeah, thanks

Great :good::good:
Will keep that in mind in case someone else has same problem

-deleted-

Lost RUU backup
Hi I to am trying to revert back to stock on my HTC one M8 (Three UK H3g__00)1 but I have lost my original backups do to an hdd fail the RUU files you posted on here I believe I could have used but the links no longer work
My phone is in a bad way at the moment it is softbricked with the latest version of CWRM on and no OS currently installed, is this why my version main appears blank?
My phone has ended up in this state after trying to install the latest android revolution rom (5.0.1). The rom seemed to install ok booted and setup fine but my Wifi wouldn't turn ON at all. After I rebooted the phone for the first time it got stuck in a boot loop.
I deally would like to get lollipop on the phone and doing some reading I believe with the situation I'm in I have to go back to stock and do the OTA updates to raise my hboot version to 3.18 or above, that way I could install cyanogen 12.1
Apologies for noob question still learning.
My bootloader (3.16) is tampered, unlocked and S-ON
D:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s

lv426HuDz said:
Hi I to am trying to revert back to stock on my HTC one M8 (Three UK H3g__00)1 but I have lost my original backups do to an hdd fail the RUU files you posted on here I believe I could have used but the links no longer work
My phone is in a bad way at the moment it is softbricked with the latest version of CWRM on and no OS currently installed, is this why my version main appears blank?
My phone has ended up in this state after trying to install the latest android revolution rom (5.0.1). The rom seemed to install ok booted and setup fine but my Wifi wouldn't turn ON at all. After I rebooted the phone for the first time it got stuck in a boot loop.
I deally would like to get lollipop on the phone and doing some reading I believe with the situation I'm in I have to go back to stock and do the OTA updates to raise my hboot version to 3.18 or above, that way I could install cyanogen 12.1
Apologies for noob question still learning.
My bootloader (3.16) is tampered, unlocked and S-ON
Click to expand...
Click to collapse
First - remove the serial no. & imei no. on your above post.
Second - install TWRP 2.8.1.0, don't use CWM recovery.
Third - read this thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
for how-to and restore 1.54.771.9 backup & its matching recovery then do multiple OTAs up to the latest 4.xx.771.x

ckpv5 said:
First - remove the serial no. & imei no. on your above post.
Second - install TWRP 2.8.1.0, don't use CWM recovery.
Third - read this thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
for how-to and restore 1.54.771.9 backup & its matching recovery then do multiple OTAs up to the latest 4.xx.771.x
Click to expand...
Click to collapse
Hi ckpv5, thanks I will give this a try now, I did try to flash TWRP 2.8.7.0 recently but when I tried to enter the recovery it just hung and I never figured out why. I will give 2.8.1.0 a go now.
Last night, just to get my phone working I flashed on cm-11-20141112-SNAPSHOT-M12-m8 with open_gapps-arm-4.4-mini-20151203. It all seemed to be working fine and I liked the look and feel of the KitKat cyanogenmod but after I received my first phone call my phone speaker went crazy and gave some nasty distortion out, I rebooted the phone to stop it and now I have the noise on everything if I turn my volume up to mid/high, I'm worried my speakers are damaged. I followed a couple of threads to install the viperapp but with no success, any ideas on this one?
Cheers,

Thanks
CHeers ckpv5 Ifollowed the guide used the files and its all sorted now.
Looks like CM11 has damaged my bottom speaker though i have ordered a replacement.
I do have 1 last question, after all the updating i have now put cm12.1 on and it seems to be running ok however when im booted into the OS my SD card is not being detected. If i drop back into TWRP recovery it does recognise the SD card, any ideas? im searching for a solution now.

I can't comment anything on CM as I never use one .. no experience on CM .. sorry.

Unrooted HTC M8 Stock Converted to GPE - Won't OTA and Phone Signal Issues

Hi All,
I did a Flash conversion from Stock HTC Sense to GPE on my Taiwan Purchased unlocked unrooted HTC M8. After reboot the phone will not do the OTA even thought it reminds me there is one and the signal strength has been really bad (goes to 0 all the time where it previously was 100% under sense).
These were the steps I followed:
1. Installed TWRP
2. Wiped with TWRP
3. With TWRP i flashed the GPE Rom : MRA58k.h6 release keys - Please not i tried other versions but they all had mid5 failures.
4. rebooted without the root.
After rebooting the phone is fine except the signal strength goes to 0 all the time and i receive the notification for :
system update: "Android M Upgrade for user/release-keys... The message goes on to say, "This is an operating system upgrade for MRA58k.H8. This software will upgrade your device to Android version M including December Security Updates....
After it prepared to install it reboots to twrp. I can find the update in the cache but it fails to install.
I would be happy with either GPE or Sense. Any advice you can offer would be great. Thanks

Post fastboot getvar all result (without serial & imei no.) then we'll see what actually you need to do

Here you go:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.709.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *************
(bootloader) imei: *************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s

NYTWBEN said:
Here you go:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-main: 6.12.709.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) security: on
Click to expand...
Click to collapse
You getvar show that there was never a conversion done. What you did only running a GPE ROM on your device. You can't do conversion on a S-On device.
Since you want to run a GPE ROM .. you should run the latest GPE which is Marshmallow same as your getvar.
You can try what I'm running now - http://forum.xda-developers.com/htc...om-htc-one-m8-gpe-stock-custom-aroma-t3254245
or just search and try other GPE with tag MRA85K.H8 in Development section - there are three of them if I'm not wrong

ckpv5 said:
You getvar show that there was never a conversion done. What you did only running a GPE ROM on your device. You can't do conversion on a S-On device.
Since you want to run a GPE ROM .. you should run the latest GPE which is Marshmallow same as your getvar.
You can try what I'm running now - http://forum.xda-developers.com/htc...om-htc-one-m8-gpe-stock-custom-aroma-t3254245
or just search and try other GPE with tag MRA85K.H8 in Development section - there are three of them if I'm not wrong
Click to expand...
Click to collapse
I tried to flash the Aroma Rom from your link and unfortunately got the following failure message:
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1826418688 bytes
sending 'zip' (733155 KB)...
OKAY [ 27.528s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 28.514s

You don't need to all those firmware flashing ... remember your device is S-On ?
Won't work for you
Have you ever install a custom ROM before ?
Install TWRP recovery
download the ROM zip
put the ROM zip on your sdcard (either internal or external, your choice)
boot to recovery
select install and browse the ROM zip
install ROM
done... reboot

This is my first time playing with Roms -- Hopefully i will get better over time.
I tried what you said but something NEW is going wrong.
I copied the files to the internal sd card and when i look for them in TWRP they are gone. I rebooted and looked for the files from the file explorer on my computer and they are there now. Also, the files are visible from the ES file explorer app i use. Previously when flashed the rom i was able to copy files onto my internal SD from my desktop.

I don't quite understand what you mean .. but I guess you can see the ROM zip in your internal storage when you connect to PC.
Check which version of TWRP that you installed. You need to use TWRP 2.8.7.0
When in recovery, check mount - enable MTP, you can see the file on PC. If yes, your TWRP should see your ROM zip when select Install menu - make sure the storage is internal storage/sdcard

ckpv5 said:
I don't quite understand what you mean .. but I guess you can see the ROM zip in your internal storage when you connect to PC.
Check which version of TWRP that you installed. You need to use TWRP 2.8.7.0
When in recovery, check mount - enable MTP, you can see the file on PC. If yes, your TWRP should see your ROM zip when select Install menu - make sure the storage is internal storage/sdcard
Click to expand...
Click to collapse
Ok, I had the removable SD card shared as part of of the internal memory (not sure how to describe that). After I separated the removable sd I was able to copy the files over without a problem and the install worked smoothly. Also, the signal strength seems to have improved a bit. It still seems to pop down to no signal at all sometimes but much less frequently.
Thanks for your help!

Ok, So the signal LTE issue is really bad.
With the stock sense rom i was always at full LTE signal now the phone shows either no signal or very low.
Is there an easy way to flash the HTC Sense Rom back on with the phone in its current state (unrooted converted to GPE via TWRP Flash)? I have seen some threads but they all are talking about rooted phones.

Thanks.

With a proper s-off device what's the proper setting/command to get the OTA updates to work?

I had previously modified the CID without any issue - Then via searching, I realized I hadn't changed the MID.
I did that, to match the GPE one, and well I now broke it - Phone wouldn't boot. Did a quick side-load which apparently wiped my entire phone and failed.
So now I have no phone :[ back to the grind with a clean slate I guess

TeckniX said:
I had previously modified the CID without any issue - Then via searching, I realized I hadn't changed the MID.
I did that, to match the GPE one, and well I now broke it - Phone wouldn't boot. Did a quick side-load which apparently wiped my entire phone and failed.
So now I have no phone :[ back to the grind with a clean slate I guess
Click to expand...
Click to collapse
Post fastboot getvar all (without serial & imei no.) .. maybe something can be done to your device.

TeckniX said:
I had previously modified the CID without any issue - Then via searching, I realized I hadn't changed the MID.
I did that, to match the GPE one, and well I now broke it - Phone wouldn't boot. Did a quick side-load which apparently wiped my entire phone and failed.
Click to expand...
Click to collapse
I'm confused about your description. What exactly is the state of the phone (screen won't turn on? Any charge LED?), and did it get that way immediately after issuing the adb command to change the MID? What does this have to do with sideload?
Where did you get the command to change MID, and did you copy/paste it exactly?

How did he convert an "S-ON" phone from stock SENSE to GPE ? Correct me if I am wrong, with Security ON,you cannot write some partitions of system (obviously sense and gpe uses different firmwares and partitions), I think he should flash SENSE or GPE RUU to fix all problems right?

Which version is the M8 I bought ? Tampered/compromised phone ?

Hello, sorry for the probably completely noob question that might have already been answered but I searched for this answer and dinn't find anything really relevant.
I'd like to check the version of the unit I received so I can install a proper ROM without killing the phone as I'm aware certain versions of the M8 (GSM/CDMA) might get into troubles if wrong roms are used.
So I bought this phone from a chinese reseller. Phone is obviously refurbished (phone was rooted "out of the box" with all bloatware removed). There is a sticker on the back of the phone with 3 barcode (P/N, S/N amnd IMEI). What's strange is IMEI is similar on sticker and "about phone" but S/N doesn't match, as if it had been tampered/manually modified... So, definitely, the motherboard or the case had been replaced and I couldn't rely on the model number wirtten on the back of the phone.
First thing I tried was using the IMEI to check version but it matches an HTC Desire 820, I wasn't aware you could modify IMEI or dupe. Anyway, I moved on to the next step, which was going into bootloader. Bootloader says CID-1111111, which is, from my understanding, a way of making the phone open to any roms, from any country. Ok, one more info that doesn't help.
So I used the fastboot getvar all and it gave me this :
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.708.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC******
(bootloader) imei: 35************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(bootloader) cidnum: 11111111
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I googled "0P6B6****" (it comes with the ****, I didn't replaced any digits, only hidden IMEI and S/N) and it didn't gave me any solid information. Since phone was rooted and seemingly heavily tampered, I went back to stock and possibly get OTA to get Marshmallow (current os is 4.18.708.12) but there's no more updates so I'm "stuck" with 5.0.1. I thought the phone was initially a taiwanese version since it had the Snapdragon [email protected] but there's a lot of chinese bloatware.
So I can't update to M and therefore convert the phone to GPe or even use any custom roms (unless I missed something and I'm completely wrong). Can you help me trying to figure out what I received and if there's anything I can do with it or if I'm stuck with the stock rom.
Thank you.

Your device is GSM which is good if you're not on US CDMA carrier.
0P6B6**** is SuperMID, 11111111 is SuperCID.
Depends on what you want your device to be, I suggest to change SuperMID to actual MID of your intended region.
If EU, change it to 0P6B10000, leave SuperCID as it is now then install latest Marshmallow RUU. You also can try to install RUU with SuperMID and see whether it works or not. AFAIK it should work with SuperMID.

Thank you for your quick answer. Yes, I use it in Europe so it works fine with my carrier (even if LTE B20 is missing but it's ok). I'll do as you suggested. I'm glad I got a GSM-only phone, I thought I received a hybrid unit. Thank you again.

ckpv5 said:
Your device is GSM which is good if you're not on US CDMA carrier.
0P6B6**** is SuperMID, 11111111 is SuperCID.
Depends on what you want your device to be, I suggest to change SuperMID to actual MID of your intended region.
If EU, change it to 0P6B10000, leave SuperCID as it is now then install latest Marshmallow RUU. You also can try to install RUU with SuperMID and see whether it works or not. AFAIK it should work with SuperMID.
Click to expand...
Click to collapse
Ok, so I modifed MID 0P6B10000 and then tried to install latest Marshmallow RUU 6.12.401.4 via fastboot but phone is not booting up (stuck on HTC One logo). So i restored with my previous clean Nandroid backup. I'm back to 4.18.708.12 (phone is 100% working)
First question : bootloader tells me os is 6.12.401.4 while I'm actually running 4.18.708.12. Is it a problem or not ?
Second question : in order to have a working (eu) MM rom on my phone, I guess I'm supposed to flash the firmware to the latest right (which is something I haven't done in my previous attempt to flash MM) ? But which one am I supposed to grab ? 6.12.401.4 or 6.16.708.1 ? I'll use your guide to do it (https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5). Can you confirm updating the firmware is mandatory before flashing stock MM rom when upgrading from Lollipop stock ? I can't install MM RUU, coming from LP, without flashing the fw first ?
Once firmware is updated, I can safely flash MM 6.12.401.4 ? I might as well flash to MM with TWRP and use one of your stock MM backup. Can it be done coming from my current LP rom version ?
Last question : let's say I flash the 6.12.401.4 firmware and keep the 4.18.708.12 LP rom, phone won't boot right ? Keep in mind I have a phone with a ModelID 0P6B10000 and a stock LP rom 4.18.708.12
I'm sorry for the noob questions and to bother you with these but I tried a lot of different things (and I don't want to go to fast and kill the phone) without any success, and since this is my first HTC phone, there are some novelties in the flashing process. And I recovered the phone several times so I might run out of luck next time.
Thank you again for your help.

Which RUU you tried ?
Try this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Your bootloader now 6.12.401.4, is it written as single not double in red ? If single then it is ok
Lollipop ROM can work when firmware is MM.
Most of the time you need to install MM firmware first to install MM RUU but the above linked RUU, you don't need to.
Since your firmware already updated to 6.12.401.4 you can restore 6.12.401.4 backup available in my backup thread to have stock ROM running or install any custom ROM that you like. You don't really need to make it stock MM rom first if your plan is to install custom rom. Only you need MM firmware installed, install latest TWRP 3.x then install rom
To your last question, when you have lollipop rom running and you flash only MM firmware, it won't boot as boot.img installed now is MM and the LP rom needs LP boot.img to boot

ckpv5 said:
Which RUU you tried ?
Try this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Your bootloader now 6.12.401.4, is it written as single not double in red ? If single then it is ok
Lollipop ROM can work when firmware is MM.
Most of the time you need to install MM firmware first to install MM RUU but the above linked RUU, you don't need to.
Since your firmware already updated to 6.12.401.4 you can restore 6.12.401.4 backup available in my backup thread to have stock ROM running or install any custom ROM that you like. You don't really need to make it stock MM rom first if your plan is to install custom rom. Only you need MM firmware installed, install latest TWRP 3.x then install rom
To your last question, when you have lollipop rom running and you flash only MM firmware, it won't boot as boot.img installed now is MM and the LP rom needs LP boot.img to boot
Click to expand...
Click to collapse
OS line is green and single so I'm good.
So if I'm understanding correctly, if OS in bootloader says 6.12.401.4, then it means firmware actually installed on phone is 6.12.401.4.
Now, when installing the RUU zip provided there (https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6), the file is corrupt, on both links. File size is correct in Windows but when I open the archive (for example to add 11111111 in android-info.txt), it says archive is corrupt and file size of the different files in this archive are way too small.
I'm gonna try Nandroid backup.

Don't do thing that is not in the instructions. No where I wrote you need to add anything to the RUU zip. It's simple process, why need to make it harder ?
RUU zip is a htc signed zip. No windows archiver such as winzip, winrar, 7-zip and etc can properly open it and you're not supposed to open it.
Read the instruction again. No need to add 11111111 to the zip as there is no such thing as SuperRUU or SuperFirmware. 11111111 is for the device which means your M8 is SuperCID and you can install the zip regardless what your device CID is.

You are absolutely right about me doing unnecessary steps. That probably explain why I didn't manage to get it working. Anyway, I used twrp to restore one the MM Nandroid backup you provided in one of your post (+ recovery) and it went smoothly. I'm now on MM and phone is working fine. I'll see if it's worth flashing a custom rom if I can find one that fits my needs.
Thank you for your answers, it did help me quite a lot. Your guides (+ all the different files you provide) are excellent, as long as you follow the instructions and don't do unnecessary steps
Have a nice day/evening.

hi,
I also have a htc m8 with modelid: 0P6B6**** and sid=1111111 which I want to use in the UK, but mine is the dual sim version of the phone
I tried following the instructions at https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
It seemed to be installing but after about 20mins it failed with the error - "(bootloader) shift signature_size for header checking...FAILED (remote: 32 header error)"
I then found another RUU which I think is the correct one but received the same error (0P6BIMG_M8_DUGL_M60_SENSE70_MR_HTC_Europe_6.16.401.1_Radio_1.24.30336021.13G_30.69.336021.00_F_release_465001_signed.zip)
btw - i tried changing the mid to 0P6B10000 but this also failed (i downloaded an app which runs in twrp to do it, is this the correct way?)
----------------- my current phone info ------------
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.30336021.13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.30.401.15
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4BRY-----
(bootloader) imei: -----
(bootloader) imei2: ----
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 49d38c68
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

alanes said:
I also have a htc m8 with modelid: 0P6B6**** and sid=1111111 which I want to use in the UK, but mine is the dual sim version of the phone
Click to expand...
Click to collapse
Finally you post your question in right section instead of ROM development thread.
I read all your questions before but I ignored them as they were posted in wrong section as I don't want to clutter ROM development thread with Off-Topics.
I don't think you can update your device directly to the latest Marshmallow as your current firmware is Lollipop. In order to do that you need to install Marshmallow firmware first then RUU but I don't see Marshmallow firmware is available anywhere except the RUU.
So my suggestion is install the Lollipop RUU then do OTA to Marshmallow. You may need to do 2 or 3 OTAs to reach that level.
1. No need to change anything to your MID yet. Let it be as it is now 0P6B6****
Only when the RUU fails to install due to MID error, then you need to change it to 0P6B64000 NOT 0P6B10000
https://forum.xda-developers.com/showthread.php?t=2708581
2. Download 0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F__signed.zip
from here - https://easy-firmware.com/home/browse/category/id/7825/
3. Install the RUU as instructed here - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but use the above downloaded RUU
or you can rename it to 0P6BIMG.zip and place it on your microsd and boot to bootloader to install.
Make sure you don't rename it to 0P6BIMG.zip.zip

ckpv5 said:
Finally you post your question in right section instead of ROM development thread.
I read all your questions before but I ignored them as they were posted in wrong section as I don't want to clutter ROM development thread with Off-Topics.
Click to expand...
Click to collapse
Hi,
Thanks for your reply - sorry if I posted in the wrong place etc. - I struggle as I can't get the xda search to work so find it difficult to find anything.
As you know I keep giving up on this but then end up trying again and spending all night messing about with it.....
I tried installing *0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F__signed.zip* but get the same error.
I am not sure if this includes the firmware or if that is separate to the RUU (as I have tried to install new firmwares so the installed one may well not be the correct one).
update: I have now installed the firmware to match (i.e. a 40mb zip file version 4.30.40 1.15) but still getting the error when i try to install the RUU
btw - I tried copying to the sd card but that gives error "device halted due to large image update fail"
---------
This I think is the info from my phone when I first received it
info on my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.18.30306251.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4...............
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(bootloader) cidnum: 11111111
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6b903f73
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks again
Alan.

I guess you need to change your MID 0P6B6**** to 0P6B64000
then try again the RUU.
I already gave you link on how to do it as in item #1

ckpv5 said:
I guess you need to change your MID 0P6B6**** to 0P6B64000
then try again the RUU.1
Click to expand...
Click to collapse
I changed the MID but then when I rebooted in to fastboot I was no longer able to connect via the fastboot command on my computer (just stayed in "waiting for device" although ADB still works ok).....
But I copied the RUU to the SD card and it installed ok
I am just doing a first boot in to android and will let you know how it goes
Thanks again for your help
Alan
---------- Post added at 08:42 AM ---------- Previous post was at 08:20 AM ----------
update: Well, a partial success
The update applied ok and I booted in to the new version of android no problem
but still when I try to use fastboot it just stays in "waiting for device" on my computer (Linux) so I am now stuck as you need fastboot to be able to install twrp.
bootloader on the phone detects when I plug the pc in with "BOOTLOADER USB". This text is highlighted in red, I think this is normal?
"htc-fastboot devices" shows nothing
btw - I have tried it on another computer and is the same

alanes said:
I changed the MID but then when I rebooted in to fastboot I was no longer able to connect via the fastboot command on my computer (just stayed in "waiting for device" although ADB still works ok).....
But I copied the RUU to the SD card and it installed ok
I am just doing a first boot in to android and will let you know how it goes
Thanks again for your help
Alan
---------- Post added at 08:42 AM ---------- Previous post was at 08:20 AM ----------
update: Well, a partial success
The update applied ok and I booted in to the new version of android no problem
but still when I try to use fastboot it just stays in "waiting for device" on my computer (Linux) so I am now stuck as you need fastboot to be able to unlock the device (i.e. fastboot oem get_identifier_token)
bootloader on the phone detects when I plug the pc in with "BOOTLOADER USB". This text is highlighted in red, I think this is normal?
btw - I have tried it on another computer and is the same
Click to expand...
Click to collapse
First thing is why did you relock bootloader. I never say you need to that because your device is S-Off
I'm not familiar with linux, never see BOOTLOADER USB, only FASTBOOT USB. Do you have access to any windows PC ?
You don't really need to do fastboot oem get_identifier_token to unlock bootloader, what you need is only a flashable TWRP zip and use adb command to unlock bootloader. Later tonight when I'm home I'll upload the flashable TWRP zip and instructions on how to unlock it.
Mean time please advise the OS no. written on bootloader so I can write the same to TWRP zip.

ckpv5 said:
First thing is why did you relock bootloader. I never say you need to that because your device is S-Off
I'm not familiar with linux, never see BOOTLOADER USB, only FASTBOOT USB. Do you have access to any windows PC ?
You don't really need to do fastboot oem get_identifier_token to unlock bootloader, what you need is only a flashable TWRP zip and use adb command to unlock bootloader. Later tonight when I'm home I'll upload the flashable TWRP zip and instructions on how to unlock it.
Mean time please advise the OS no. written on bootloader so I can write the same to TWRP zip.
Click to expand...
Click to collapse
Hi,
I had assumed it had re-locked the bootloader but later realised it was still S-off
and you are right it is "FASTBOOT USB", not "BOOTLOADER USB" - sorry for the confusion
My phone shows OS-4.30.401.15
I can use a friends Windows laptop and will see if I can give it a try
On another subject, the GPS on this phone seems to be dead (it has never seen a single satellite), is this a known problem with these phones do you happen to know?
thanks
Alan

alanes said:
My phone shows OS-4.30.401.15
Click to expand...
Click to collapse
I thought you want to update to the latest so you can install LOS14 or LOS15 or any custom ROM later.
Once you successfully back on stock 4.30.401.15, you should check for OTA and install. I believe you will have 2 or 3 OTA to get to Marshmallow firmware.
Have you check for OTA & update ?
About GPS, maybe you have faulty gps cable in it. I don't have M8 dual SIM but no reason why it is not working unless it is hardware issue. I can't help when it comes to hardware.
Read this - https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999

ckpv5 said:
I thought you want to update to the latest so you can install LOS14 or LOS15 or any custom ROM later.
Have you check for OTA & update ?
Read this - https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999
Click to expand...
Click to collapse
Hi,
I think you are making the mistake in thinking I have some idea what I am doing - lol
I just want to get LiniageOS 14 installed - I have never done anything like this before on my phone and this is a new phone I was not at all familiar with to start with, it has so far been a bit of a nightmare.......
thanks - I will read the link you provided and see if I can get it updated then get back to you

alanes said:
Hi,
I think you are making the mistake in thinking I have some idea what I am doing - lol
I just want to get LiniageOS 14 installed - I have never done anything like this before on my phone and this is a new phone I was not at all familiar with to start with, it has so far been a bit of a nightmare.......
thanks - I will read the link you provided and see if I can get it updated then get back to you
Click to expand...
Click to collapse
I don't make mistake as I understand what you are trying to do. If you unlock bootloader and install twrp now, you're back to earlier problem.
To install LOS 14, you must have Marshmallow firmware installed. Now you're on stock 4.30.401.15. You don't need to do unlocking & install twrp yet. You need to do OTA until you get final OTA either 6.16.401.1 or 6.16.401.101 then only you proceed to unlock bootloader and install twrp and install LOS 14.
Forget about link to GPS matter for now as that require device teardown.
Most important now OTA. Without OTA it serves no purpose on what you're doing now and intend to do later.

ok - thanks, I think I now know what I need to do (how many times have I thought that in the last few days - lol)
I Just tried fastboot on a windows laptop and it works! (no idea what is going on there - but at least I can now use it again)
it now shows modelid = 0P6B640000
BTW-I think the universe has it in for me regarding this project as apart from wanting to use LineageOS, the main reason I bought a new phone is that my existing phones GPS stopped working.........

alanes said:
ok - thanks, I think I now know what I need to do (how many times have I thought that in the last few days - lol)
I Just tried fastboot on a windows laptop and it works! (no idea what is going on there - but at least I can now use it again)
it now shows modelid = 0P6B640000
BTW-I think the universe has it in for me regarding this project as apart from wanting to use LineageOS, the main reason I bought a new phone is that my existing phones GPS stopped working.........
Click to expand...
Click to collapse
In case you're not sure what OTA I'm talking about, go to settings - about - software update - check here for OTA. When there is one, download and install. Again repeat the process until it says there is no update available.
Every time you install OTA, you OS no. on bootloader will change to current firmware. You need this until the OS no. is written as 6.16.401.1 or 6.16.401.101.
Then only you unlock bootloader and install latest twrp 3.x and install LOS 14