Develop Bugs

HTC One X Stock Firmware JB 4.2.2 S5

Hi Guys,
It's been a while since I wrote on this forum... I may be tired, but I can't work out a few things:
I have a T-Mobile UK HTC One X, due to some circumstances I needed to completely wipe...
I was already running an unbranded stock firmware on it, but after the complete wipe i wanted to install JB 4.2.2 S5 - I usually unlock the bootloader, install clockworks, copy the original unedited complete firmware zip on it and install it via the recovery, then relock the bootloader and job done, but I cannot seem to find a complete unedited rom, is either RUU.exe (which I cannot run as the PC wont see the phone due to no firmware on it, I think) or nandrom backups which I don't really want, all the OTA ones seem to just be updates and am stuck with a phone that only has clockwork recovery on it....
Where can I get an official unedited zip that I can install via clockworks?
Thanks

LondonVirus said:
Hi Guys,
It's been a while since I wrote on this forum... I may be tired, but I can't work out a few things:
I have a T-Mobile UK HTC One X, due to some circumstances I needed to completely wipe...
I was already running an unbranded stock firmware on it, but after the complete wipe i wanted to install JB 4.2.2 S5 - I usually unlock the bootloader, install clockworks, copy the original unedited complete firmware zip on it and install it via the recovery, then relock the bootloader and job done, but I cannot seem to find a complete unedited rom, is either RUU.exe (which I cannot run as the PC wont see the phone due to no firmware on it, I think) or nandrom backups which I don't really want, all the OTA ones seem to just be updates and am stuck with a phone that only has clockwork recovery on it....
Where can I get an official unedited zip that I can install via clockworks?
Thanks
Click to expand...
Click to collapse
Give the result from command fastboot getvar version-main

Thant said:
Give the result from command fastboot getvar version-main
Click to expand...
Click to collapse
version-main: 3.16.110.4
cidnum: T-MOB005
But as I said, I want a non branded, complete flash room please

LondonVirus said:
version-main: 3.16.110.4
cidnum: T-MOB005
But as I said, I want a non branded, complete flash room please
Click to expand...
Click to collapse
sorry fastboot getvar all and delte your S/N and IMEI from the info I didn't read what you wamt you want rom with sense 5 give the result to see your hboot version

Thant said:
sorry fastboot getvar all and delte your S/N and IMEI from the info I didn't read what you wamt you want rom with sense 5 give the result to see your hboot version
Click to expand...
Click to collapse
C:\Android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.39.0000
(bootloader) version-baseband: 5.1204.163R.30
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.110.4
(bootloader) serialno: -
(bootloader) imei: -
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: low
(bootloader) battery-voltage: 3446mV
(bootloader) devpower: 0
(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.826s
Sorry it took me a while... life and kids eh lol... I am trying to sort this phone for the MRS, I have a Galaxy S5, great device
I must say I would even be happy with the TMO UK RUU, this pone is doing my head in at the moment and really don't have the time to be messing with it now, just need it working...
I wanted to change Super CID it but apparently it will need to be s-off and cant get round to do that, I wanted to install a non branded RUU but this is not allowed due to the wrong CID arg, stupid phones, was easier to flash unbranded firmware to old Nokia on Symbian...

LondonVirus said:
C:\Android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.39.0000
(bootloader) version-baseband: 5.1204.163R.30
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.110.4
(bootloader) serialno: -
(bootloader) imei: -
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: low
(bootloader) battery-voltage: 3446mV
(bootloader) devpower: 0
(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.826s
Sorry it took me a while... life and kids eh lol... I am trying to sort this phone for the MRS, I have a Galaxy S5, great device
I must say I would even be happy with the TMO UK RUU, this pone is doing my head in at the moment and really don't have the time to be messing with it now, just need it working...
I wanted to change Super CID it but apparently it will need to be s-off and cant get round to do that, I wanted to install a non branded RUU but this is not allowed due to the wrong CID arg, stupid phones, was easier to flash unbranded firmware to old Nokia on Symbian...
Click to expand...
Click to collapse
You have good hboot for sense 5 rom 4.2.2 install MaximusHD or ARHD or any sense 5 rom and you are ready to go.

I wanted a stock ROM, the Mrs is not very technical minded lol and a customer ROM won't help her, either TMO UK or in branded, where can I get the RUU for it?
Thanks all

Unfortunately T-Mobile skipped the sense 5, 4.2.2 update, I have the same device and cid and called them countless times, spoke to managers and had it escalated to the highest level only to be told they would not be updating past 4.1.1
Every other network pushed that but them, if you stick to stock T-Mobile ROM you would be missing 2 very important updates, one being the heartbleed patch.
Just grab MaximusHD from the development forum, its the best sense 5 ROM out there and has important ota updates too.

I suppose I will have install it via the custom recovery, could I not install the unbranded RUU 4.2.2? Does anyone know how to s-off correctly, so that I can change the CID.
By the way thank you all for your replies

LondonVirus said:
I suppose I will have install it via the custom recovery, could I not install the unbranded RUU 4.2.2? Does anyone know how to s-off correctly, so that I can change the CID.
By the way thank you all for your replies
Click to expand...
Click to collapse
NO S-OFF for HOX

Thant said:
NO S-OFF for HOX
Click to expand...
Click to collapse
I assume that HOX means Htc One X lol... so I will not be able to change the CID?
Any "re-pack" unedited versions of the genuine unbranded europe RUU that I can install via custom recovery?
Thanks again all

There must be a way to s-off the Maximus HD ROM says "1. Make sure your device is unlocked or have s-off"
Why would it say that on "http://forum.xda-developers.com/showthread.php?t=2410320" if there was no s-off ways? am confused lol

LondonVirus said:
There must be a way to s-off the Maximus HD ROM says "1. Make sure your device is unlocked or have s-off"
Why would it say that on "http://forum.xda-developers.com/showthread.php?t=2410320" if there was no s-off ways? am confused lol
Click to expand...
Click to collapse
Don't be confused mate..HOX can s-off but via java card( will cost money to make it).In here no have chance to be s-off.

Installation of Maximus HD no hanging on this screen, flashed Kernel and wiped the memory fkn phones!

LondonVirus said:
Installation of Maximus HD no hanging on this screen, flashed Kernel and wiped the memory fkn phones!
Click to expand...
Click to collapse
Never mind, seems to have worked lol

LondonVirus said:
Never mind, seems to have worked lol
Click to expand...
Click to collapse
Phone hanging on boot screen don't know why...

LondonVirus said:
Phone hanging on boot screen don't know why...
Click to expand...
Click to collapse
are you flashed the boot.img from maximushd archive via fastboot with the command fastboot flash boot boot.img

Thant said:
are you flashed the boot.img from maximushd archive via fastboot with the command fastboot flash boot boot.img
Click to expand...
Click to collapse
Thank you for your reply, I did flash the boot via the "Kernel+Flasher+21.0.0" looking at the coding inside the batch file, it calls a batch in a sub-folder with the command fastboot flash boot boot.img, and I did run it and got Okay message in the command window...

LondonVirus said:
Thank you for your reply, I did flash the boot via the "Kernel+Flasher+21.0.0" looking at the coding inside the batch file, it calls a batch in a sub-folder with the command fastboot flash boot boot.img, and I did run it and got Okay message in the command window...
Click to expand...
Click to collapse
do it manually like I write you in my post not with flasher or tool

Thant said:
do it manually like I write you in my post not with flasher or tool
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------------------
C:\Android\sdk\platform-tools>fastboot flash zip rom.zip
sending 'zip' (716000 KB)...
OKAY [ 90.451s]
writing 'zip'...
(bootloader) Can not find [android-info.txt] in zipped image!
FAILED (remote: 24 parsing android-info fail)
finished. total time: 125.830s
---------------------------------------------------------------------------------------------------------------------
fastboot oem rebootRUU
fastboot flash zip rom.zip <----- This is Maximus HD....
and this is after a flashed the correct kernel/boot.img....

[Q] Stuck in bootloader with Security warning.

I have been rooted for a few weeks and decided to go back. Well I had S-off but when I started the transition to stock I turned s-on and that is when the **tampered** flag came on. I stupidly continued using the code (fastboot oem lock) which gave me the **Relocked** status but now I have a security warning and It will ONLY boot into bootloader. I have tried multiple times re-flashing TWRP and I cant get it to go into recovery. From what I have read I need to flash stock rom onto it but I cant get into the recovery to flash or even sideload. So where should I go from here? Everything I need to do requires S-off and I cant seem to get it.
*ALSO I am currently on InsertKoin ROM* <--That might change something
*HtcDev will not work for my phone.*
fastboot oem unlock gives ERR [command error]
Last flashed TWRP version was 2.7.0.1
Specs.
M7_WLV PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OpenDSP-v32.120.274.0909
OS-3.11.605.1
eMMC-boot 2048MB
GetVar info below also.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3B6S906771
(bootloader) imei: 990004282795917
(bootloader) meid: 99000428279591
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4134mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
Oh! If someone would mind explaining what any of that means (even just an acronym) would help for me learning this!
Thank you in advance. John

I've been S-Off since day one so double check everything but this will get you in the right direction. You need to S-off and unlock, flash an RUU and then relock (to remove the red text warning). Going back to S-on I understand is pretty dangerous and appears to be unnecessary. Go to this thread and start with the 3rd tutorial to re-S-off. If you can get S-off'd the rest should be pretty easy.

jman036 said:
I have been rooted for a few weeks and decided to go back. Well I had S-off but when I started the transition to stock I turned s-on and that is when the **tampered** flag came on. I stupidly continued using the code (fastboot oem lock) which gave me the **Relocked** status but now I have a security warning and It will ONLY boot into bootloader. I have tried multiple times re-flashing TWRP and I cant get it to go into recovery. From what I have read I need to flash stock rom onto it but I cant get into the recovery to flash or even sideload. So where should I go from here? Everything I need to do requires S-off and I cant seem to get it.
*HtcDev will not work for my phone.*
fastboot oem unlock gives ERR [command error]
Last flashed TWRP version was 2.7.0.1
Specs.
M7_WLV PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OpenDSP-v32.120.274.0909
OS-3.11.605.1
eMMC-boot 2048MB
GetVar info below also.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3B6S906771
(bootloader) imei: 990004282795917
(bootloader) meid: 99000428279591
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4134mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
Oh! If someone would mind explaining what any of that means (even just an acronym) would help for me learning this!
Thank you in advance. John
Click to expand...
Click to collapse
That should be early enough to use Firewater on. Let me know if you run into problems because I can help via team viewer.

@pmterp & @dottat Thanks for the reply and that sounds like a good idea but I have to push the file via adb. I cannot get there because I am stuck in the fastboot section. So I don't think firewater or anything that uses adb will work.

Crud. I don't remember if you can get to RUU mode without being S-off. In fastboot the command is fastboot OEM rebootRUU If you can then you could re-RUU but I'm thinking you have to be S-off to get there. Hopefully someone else will chime in with some better ideas.

pmterp said:
Crud. I don't remember if you can get to RUU mode without being S-off. In fastboot the command is fastboot OEM rebootRUU If you can then you could re-RUU but I'm thinking you have to be S-off to get there. Hopefully someone else will chime in with some better ideas.
Click to expand...
Click to collapse
You can go into ruu mode while s-on, but need a signed ruu. Last signed ruu we had was 2.x
Sent from my HTC6500LVWBLU using XDA Free mobile app

pmterp said:
Crud. I don't remember if you can get to RUU mode without being S-off. In fastboot the command is fastboot OEM rebootRUU If you can then you could re-RUU but I'm thinking you have to be S-off to get there. Hopefully someone else will chime in with some better ideas.
Click to expand...
Click to collapse
I tried that command and it did do something different now. It is an all black screen with silver HTC however it is not doing anything.

jman036 said:
I tried that command and it did do something different now. It is an all black screen with silver HTC however it is not doing anything.
Click to expand...
Click to collapse
That is RUU mode and will accept an RUU file to flash at this point. I believe Uzephi is correct that the RUU you flash must be signed (which I think is the same as encrypted). I'm not sure where you would find them but I'm sure Google will be your friend on that. Be careful what version you flash because I think it can cause problems if you move down. I'm not sure how open he is to helping via PM (he's super helpful but also very busy) but if it were me I'd reach out via PM to @santod040 and ask for advice. He's a highly skilled dev who's been with this device a long time.

I think I might be in the same boat as jman036, only difference being that I'm on a later OS version (5.28.605.2). I've tried flashing signed RUUs for my particular OS version from both santod's and dottat's AndroidFileHosts but both give me this error:
"(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)"
Sucks man.

tflogic said:
I think I might be in the same boat as jman036, only difference being that I'm on a later OS version (5.28.605.2). I've tried flashing signed RUUs for my particular OS version from both santod's and dottat's AndroidFileHosts but both give me this error:
"(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)"
Sucks man.
Click to expand...
Click to collapse
Both of their 5.28.605.2 ruus are decrypted and thus unsigned. You will get a signature check fail if you are s-on
Sent from my HTC6500LVWBLU using XDA Free mobile app

Uzephi said:
Both of their 5.28.605.2 ruus are decrypted and thus unsigned. You will get a signature check fail if you are s-on
Click to expand...
Click to collapse
Dang really? I thought they would be since they both have "signed" in the filenames.
HSM_M7_WL_K443_SENSE60_VZW_MR_VERIZON_WWE_5.28.605.2_HSM_Radio_1.13.41.0702_NV_VZW_4.64_002_release_387332_signed.zip
Click to expand...
Click to collapse
Any idea what to do then?

tflogic said:
Dang really? I thought they would be since they both have "signed" in the filenames.
Any idea what to do then?
Click to expand...
Click to collapse
Yes. Will fail. You should try installing the latest HTC sync and seeing if the repair button lights up for you on the home page of the app.
---------- Post added at 10:55 PM ---------- Previous post was at 10:55 PM ----------
Uzephi said:
Both of their 5.28.605.2 ruus are decrypted and thus unsigned. You will get a signature check fail if you are s-on
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
Actually I have one of each ?
---------- Post added at 10:58 PM ---------- Previous post was at 10:55 PM ----------
jman036 said:
I tried that command and it did do something different now. It is an all black screen with silver HTC however it is not doing anything.
Click to expand...
Click to collapse
See if you can flash this zip while your phone is in this ruu mode.
Fastboot flash zip firmware3.zip
May require flashing twice.
https://www.androidfilehost.com/?fid=23681161096070340

dottat said:
Yes. Will fail. You should try installing the latest HTC sync and seeing if the repair button lights up for you on the home page of the app.
Click to expand...
Click to collapse
HTC Sync doesn't recognize the phone. Getting a "no phone connected" message. Any other ideas?

tflogic said:
HTC Sync doesn't recognize the phone. Getting a "no phone connected" message. Any other ideas?
Click to expand...
Click to collapse
If installed drivers are correct htc sync will see the phone. I just responded to your post in a different thread. Can you try that first before we troubleshoot drivers?

pmterp said:
Crud. I don't remember if you can get to RUU mode without being S-off. In fastboot the command is fastboot OEM rebootRUU If you can then you could re-RUU but I'm thinking you have to be S-off to get there. Hopefully someone else will chime in with some better ideas.
Click to expand...
Click to collapse
Fastboot oem rebootRUU mode is supported in both s on/off scenarios. An s on user can always use this to reflash same firmware or even upgrading to newer firmware. Bootloader unlocked phones often take advantage of this before s off exploits are found.

Uzephi said:
Both of their 5.28.605.2 ruus are decrypted and thus unsigned. You will get a signature check fail if you are s-on
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
Yeah I cant seem to find any RUU files that match my phone!
dottat said:
Fastboot oem rebootRUU mode is supported in both s on/off scenarios. An s on user can always use this to reflash same firmware or even upgrading to newer firmware. Bootloader unlocked phones often take advantage of this before s off exploits are found.
Click to expand...
Click to collapse
Well I made it one step further with it recognizing that I have a phone connected but said "no software available."
I think if I can find a signed RUU file then I can fix this. I just have to find it.....

See if you can flash this zip while your phone is in this ruu mode.
Fastboot flash zip firmware3.zip
May require flashing twice.
https://www.androidfilehost.com/?fid=23681161096070340
Click to expand...
Click to collapse
Well I tried this and sadly I can send it but it always gets signature check fail. :/ (I ran it twice also)

Prep M8 for donation (factory restore)

Hi all,
So I have my old M8 doing nothing (switched to Note 4)...
It's running a custom venom rom, and basically I want to put it completely back to factory state.
If you could help a guy that's moderately good at this stuff, I would be greatly appreciated.
Thanks!!

Post the output from fastboot getvar all and we'll tell you what to do

Thanks for that, err - I haven't got the tools installed any more, could you point in the direction of the tools again sorry!

Ok, getvar just sits at waiting for device...?

Ok sorry, turns out I'm just rusty!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(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
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__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.020s

1. remove the imei no. & serial no. in your above post.
2. check EddyOS thread : http://forum.xda-developers.com/showthread.php?t=2735235
You have everything that you need there. The guide will put your device back to stock but updated to the latest lollipop stock ROM

Done, and thanks!

Sorry to be a pain, is there another way to achieve S-Off without paying sunshine?
Thanks

Shozuki said:
Sorry to be a pain, is there another way to achieve S-Off without paying sunshine?
Thanks
Click to expand...
Click to collapse
No other way, only sunshine.
But you don't need S-Off to revert to stock with that thread guide, you need to relock bootloader then follow all the steps.
The only thing is without S-Off, your bootloader will show RELOCKED instead of LOCKED.

Ah cool, minor.
Thanks

S-OFF would probably add a bit to resale value so might be worth doing - up to you of course!

EddyOS said:
S-OFF would probably add a bit to resale value so might be worth doing - up to you of course!
Click to expand...
Click to collapse
Indeed, but I'm literally giving it my uncle and let him use it.
If I may ask one more thing though, when sending the ruu.zip
I get:
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 3(s)
Any ideas??
Thanks for your help sirs.

That seems to come up randomly and doesn't really appear to point to anything in particular. You've definitely got a locked bootloader and are using the htc_fastboot?

EddyOS said:
That seems to come up randomly and doesn't really appear to point to anything in particular. You've definitely got a locked bootloader and are using the htc_fastboot?
Click to expand...
Click to collapse
Unfortunately it's still unlocked, but I can't seem to change that either. I'm using minimal adb and fastboot, but the htc_bootloader is in the folder.
Am I supposed to use that from the start, as I only see reference in the final stage.
Apologies, if I'm misreading!
EDIT, I followed the guide starting with recovery which kept failing... That must be the issue...
from your guide EDIT: Thread I meant:
"Well lord knows what's going on here...
I started by flashing the recovery to the one linked here. It won't boot into recovery at all it just sits at "entering recovery..."
I was using a venom custom rom and TWRP 2.8.5.0 touch recovery.
I can boot into the phone, use fastboot and adb - but can't go any further in restoring the handset back to factory... All help appreciated."

ckpv5 said:
1. remove the imei no. & serial no. in your above post.
2. check EddyOS thread : http://forum.xda-developers.com/showthread.php?t=2735235
You have everything that you need there. The guide will put your device back to stock but updated to the latest lollipop stock ROM
Click to expand...
Click to collapse
does it matter which region it's from? I am using a canadian Carrier (rogers). And I can't really find ruu for Canadian carrier. Any help/ guidance would be appreciated thanks.

crazyandroider said:
does it matter which region it's from? I am using a canadian Carrier (rogers). And I can't really find ruu for Canadian carrier. Any help/ guidance would be appreciated thanks.
Click to expand...
Click to collapse
Yeah, That guide is for EU M8's only...
really struggling getting mine back to factory...

crazyandroider said:
does it matter which region it's from? I am using a canadian Carrier (rogers). And I can't really find ruu for Canadian carrier. Any help/ guidance would be appreciated thanks.
Click to expand...
Click to collapse
That depends. Are you s-off? If so, you can run a WWE RUU, and go back to basically stock. WWE is compatible with Rogers. You won't get OTAs though. You'll have to update firmware manually, but with s-off, that's easy to do.

My apologies, I failed to use my eyes.
All solved. Many thanks!!

Shozuki said:
My apologies, I failed to use my eyes.
All solved. Many thanks!!
Click to expand...
Click to collapse
What was it?

EddyOS said:
What was it?
Click to expand...
Click to collapse
Well basically I was following the instructions as if I were S-Off.
Instead I just to use: fastboot oem lock and completely skimmed over the text failing to read it!
My uncle is happy now and thats fine with me!
Thanks for your help!

HTC M8S VODA firmware

Somebody can link me a Vodafone UK firmware zip, I have to flash it in RUU mode in order to make my phone working again.
Thank you in advance

Check post #1 and ask here : http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
I can't help much as I don't have a M8s

ckpv5 said:
Check post #1 and ask here : http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
I can't help much as I don't have a M8s
Click to expand...
Click to collapse
Yeah, checked multiple times, but I didn't find any proper files according to my problem. I mean , I've got the RUU files there, but I have to flash through ruu only the firmware zip because I've relocked the bootloader, and since I have wrong recovery flashed (simple M8 recovery) can't do anything else. I think this is the only solution.
Btw thanks for replying.

I don't get it ...
If there is RUU for your device version, use the RUU to fix the problem.
You don't need firmware.zip when there is RUU available (when you install the same version as your current firmware written on bootloader)

ckpv5 said:
I don't get it ...
If there is RUU for your device version, use the RUU to fix the problem.
You don't need firmware.zip when there is RUU available (when you install the same version as your current firmware written on bootloader)
Click to expand...
Click to collapse
I need the firmware cause the RUU for my HTC doesn't works, it starts flashing the file but shuts down with an error ... Sorry for not mentioning that . Flashing the firmware I think the only solution for me :/

Hi GombaFelho,
I had the same problem, always the wrong firmware error message.
I unlocked and did again an "oem lock". Check again the drivers for RUU.
In end it worked for me with the ARUWizard.exe and this version:
RUU_M8_QL_UL_L50_SENSE60_Vodafone_UK_1.11.161.1_Radio_1.0.U20410.1G50408_15.00_016_F_release_430447_signed
First there is a downgrade and after that you can uprade the software on the fly.

realclone1000 said:
Hi GombaFelho,
I had the same problem, always the wrong firmware error message.
I unlocked and did again an "oem lock". Check again the drivers for RUU.
In end it worked for me with the ARUWizard.exe and this version:
RUU_M8_QL_UL_L50_SENSE60_Vodafone_UK_1.11.161.1_Radio_1.0.U20410.1G50408_15.00_016_F_release_430447_signed
First there is a downgrade and after that you can uprade the software on the fly.
Click to expand...
Click to collapse
Hi ! Thanks for the answer
I tried that one too, but some magical way my update stuck at 0/8 so idk what should I do ..
I've read somewhere a solution for this, but can't remembere where

When you have that stuck problem, that's pc usb connection problem not RUU.
You need latest htc usb drivers and use usb2.0
Read this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4

ckpv5 said:
When you have that stuck problem, that's pc usb connection problem not RUU.
You need latest htc usb drivers and use usb2.0
Read this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
Click to expand...
Click to collapse
Tried it now, says the bootloader verison not correct... im really unlucky

Back to basic ... most important data in order to get help.
Post your fastboot getvar all result (remove serial & imei no.)

ckpv5 said:
Back to basic ... most important data in order to get help.
Post your fastboot getvar all result (remove serial & imei no.)
Click to expand...
Click to collapse
Okay, as soon as I can get my phone load up . Thanks for your patience and sorry for my idiotism..
EDIT : so here are the results
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.21.161.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: VODAP102
(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: 7900fbfd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001

Unfortunately neither firmware nor RUU available on the net for this version.
When you said you wait for it to load up .. are you saying your device is in working condition, only wrong recovery installed ?

ckpv5 said:
Unfortunately neither firmware nor RUU available on the net for this version.
When you said you wait for it to load up .. are you saying your device is in working condition, only wrong recovery installed ?
Click to expand...
Click to collapse
I shouldn't wait for anything , right ? I mean it's not that new phone, so I assume there aren't going to be a new firmware for this version...
It was in a working condition, but after I relocked the bootloader, it went off. Had to start with the Pow+Vol.Up+Vol.Down combo, it worked but now just stops at the HTC ONE screen...
Anyways I really appreciate that you took the time to help me

I was wondering if there is some way to unlock the bootloader without using the HTCDev ? (cause I can't factory reset my phone) that would be so good...

I have an M8s too, and had the same issue.
To fix this. First try to relock and unlock the your bootloader it will prompt yes or no bla bla... Tick yes
If none of this work. Install the latest recovery from lalleman's server and pick a custom ROM, I recommend CM12 since you don't a choice cause Pandora is a little buggy.
This should work for you. Good luck with that

HTC One M8 Sprint

Hi, I have a htc one m8 and I believe it is a sprint. I bought this of ebay and did not realise it was a sprint version as I wanted a GSM version. I noticed the phone is s-off and has a cidnum of 11111111.
It has problems. If you boot into fastboot, it will stay in fastboot for say 10 seconds then reboot back into the system automatically. OS is not working correctly.
I have downloaded the up to date sprint RUU and this is titled 'RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe'
I tried flashing this from windows 10 as an exe file but this does not work. (Error 155)
Here is the getvar all data minus imei and serial number:
C:\Users\uggitt\Desktop\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.08.20.0916
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.30.654.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000499237405
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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: d4c3cae5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
I need to get the phone working again and any help would be most appreciated. If anyone needs any further info please let me know.
Mark

Try this RUU: link

lucyr03 said:
Try this RUU: link
Click to expand...
Click to collapse
Thank you and I will give it a go later today

uggitt said:
Thank you and I will give it a go later today
Click to expand...
Click to collapse
Just tried the RUU from your link and I get the same error 155.

uggitt said:
Just tried the RUU from your link and I get the same error 155.
Click to expand...
Click to collapse
Hmm error 155 is related to bootloader status(needs to be locked/relocked) but your device is s-off so you don't need to relock for ruu.
Anyway try to relock your bootloader and come back with the results.

lucyr03 said:
Hmm error 155 is related to bootloader status(needs to be locked/relocked) but your device is s-off so you don't need to relock for ruu.
Anyway try to relock your bootloader and come back with the results.
Click to expand...
Click to collapse
I tried to relock the bootloader but it came back as already locked.

uggitt said:
I tried to relock the bootloader but it came back as already locked.
Click to expand...
Click to collapse
What says in hboot? locked/relocked/unlocked ?

lucyr03 said:
What says in hboot? locked/relocked/unlocked ?
Click to expand...
Click to collapse
locked in hboot

uggitt said:
locked in hboot
Click to expand...
Click to collapse
So.. you have s-off but never unlocked the bootloader? This is strange...
Try to unlock it and see if works.

I have tried to unlock the bootloader but as it keeps rebooting when in Fastboot on the phone after 10-15 seconds. I cannot seem to get the token.
I feel something is wrong with the phones fastboot/hboot but this is only a guess.
I bought the phone like this and I did not s-off etc.

uggitt said:
I have tried to unlock the bootloader but as it keeps rebooting when in Fastboot on the phone after 10-15 seconds. I cannot seem to get the token.
I feel something is wrong with the phones fastboot/hboot but this is only a guess.
I bought the phone like this and I did not s-off etc.
Click to expand...
Click to collapse
I think it's because the battery, I just saw in your getvar the battery reported charged capacity is 0...

lucyr03 said:
I think it's because the battery, I just saw in your getvar the battery reported charged capacity is 0...
Click to expand...
Click to collapse
Ok, phone is on and showing 100%.. Do you think the actual battery is faulty and is causing the problems?

uggitt said:
Ok, phone is on and showing 100%.. Do you think the actual battery is faulty and is causing the problems?
Click to expand...
Click to collapse
If the battery acts normally when phone is on it's not because a battery problem...
The phone stay in hboot without cable connected more than 10 secs?
Sent from my HTC One M9 using Tapatalk

lucyr03 said:
If the battery acts normally when phone is on it's not because a battery problem...
The phone stay in hboot without cable connected more than 10 secs?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
No, reboots out of hboot with cable or without cable plugged in

uggitt said:
No, reboots out of hboot with cable or without cable plugged in
Click to expand...
Click to collapse
In RUU mode too?(fastboot oem rebootRUU)
Sent from my HTC One M9 using Tapatalk

lucyr03 said:
In RUU mode too?(fastboot oem rebootRUU)
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Hi Just tried and goes into ruu mode and then restarts after say 10 seconds

uggitt said:
Hi Just tried and goes into ruu mode and then restarts after say 10 seconds
Click to expand...
Click to collapse
That's strange behavior... Idk what to say..
Sent from my HTC One M9 using Tapatalk

lucyr03 said:
That's strange behavior... Idk what to say..
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Thanks for trying and for your help. I think it is destined for the bin....

uggitt said:
I have downloaded the up to date sprint RUU and this is titled 'RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe'
I tried flashing this from windows 10 as an exe file but this does not work. (Error 155)
Click to expand...
Click to collapse
You need to flash firmware 6.20.651.3. before the RUU will install. It's a peculiar requirement on US Marshmallow RUUs, that updating by RUU from any lower version (Lollipop, Kitkat) you need to flash firmware first, before RUU, otherwise you will have Error 155.
Firmware and instructions for flashing if can be found here (as well as all Sprint RUUs):
https://forum.xda-developers.com/showthread.php?t=2729173
But if the phone will not stay in hboot (or RUU mode) it may be a problem flashing firmware and/or RUU. May possibly even brick the phone. If flashing firmware or RUU, the process is interrupted when updating hboot partitions, a brick is almost certain. But on the other hand, it looks like you are close to binning it anyway, so maybe the risk is not significant (and worth trying). It's up to your judgment.

redpoint73 said:
You need to flash firmware 6.20.651.3. before the RUU will install. It's a peculiar requirement on US Marshmallow RUUs, that updating by RUU from any lower version (Lollipop, Kitkat) you need to flash firmware first, before RUU, otherwise you will have Error 155.
Firmware and instructions for flashing if can be found here (as well as all Sprint RUUs):
https://forum.xda-developers.com/showthread.php?t=2729173
But if the phone will not stay in hboot (or RUU mode) it may be a problem flashing firmware and/or RUU. May possibly even brick the phone. If flashing firmware or RUU, the process is interrupted when updating hboot partitions, a brick is almost certain. But on the other hand, it looks like you are close to binning it anyway, so maybe the risk is not significant (and worth trying). It's up to your judgment.
Click to expand...
Click to collapse
Thank you for the reply and I may give it a go later when back from work