M8s ORANG001 OTA - One (M8) Q&A, Help & Troubleshooting

Hi all,
Trying to return this phone to stock to use since my HTC 10 is playing up and not sure what to buy as a replacement, yet.
Anyway, it's soft bricked and unable to flash the RUU as it gives a Failed (remote: 22) error.
I believe it's because it has updated hboot and it can now no longer read the encrypted rom. To fix it I (think) need a ORANG001 OTA to flash. I have tried a Europe one but that fails.
Anyone know where I can get one?
Or how would I get SuperCID so I can flash any?
My knowledge falls down here so any help would be great
Bootloader is relocked.
Version: 0.5
Version-bootloader: 3.19.0.0000
Version-baseband: [email protected]
Version-main:
Version-misc: PVT SHIP S-ON
Product: m8ql_ul
Modelid: 0PKV10000
cidnu: ORANG001
Click to expand...
Click to collapse

Hello,
I think you have to:
- Unlock and S-OFF again your bootloader
- Try to downgrade it
- Flash ORANG001 CID through fastboot command prompt
- Flash through official RUU (or install the 0P6BIMG.zip that you can find inside from the bootloader)
- Maybe relock the bootloader if you want
You can take a look at this post for giving you an idea on how to downgrade (be careful that proposed ROMs are for Verizon M8 and won't work for yours):
https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845

Hi John, I don't think we can S-OFF the M8s. It's not the same as the M8.

Related

[Q] Pls help - HTC One X stuck on quietly brilliant screen and won't restore

Hi Friends,
First things first - I have looked up and tried several things that other folks facing similar issues have tried. None of it has worked for me.
Coming to the problem now.
It all began when I decided to unroot and install a custom ROM on my stock HTC One X and downloaded a stable build from http://wiki.cyanogenmod.org/w/Install_CM_for_endeavoru.
I followed the tutorials and unlocked my device and started off with CWM recovery 5.8.2.7. Did some experiemenation with backup and recovery. So far, so good.
I decided to use the 4.4 ROM and as per some information available it needed me to update to CWM 6.0.4.8. I did so but when I tried to go in recovery, the screen went blank. Tried it multiple times without luck.
Then I switched over to TWRP 2.7.1 and used it to install the cm-11-20141112-SNAPSHOT-M12-endeavoru.zip. It failed with status 7. Assert checks on bootloader ver failed (as per checks it would need anything 1.28 or higher). I am on hboot 1.12. I extracted the boot.img from the rom zip and flashed it from fastboot. It showed no change in hboot version (maybe this is where I faulted). It still won't install rom zip as I would expect.
Now the phone won't go beyond "Quietly Brilliant" screen on power on. Recovery to saved backup says its successful but it still gets stuck at same screen on reboot.
Would appreciate help and pointers from anyone who could help.
Thanks in advance,
Kunal
koolvirgo said:
Hi Friends,
First things first - I have looked up and tried several things that other folks facing similar issues have tried. None of it has worked for me.
Coming to the problem now.
It all began when I decided to unroot and install a custom ROM on my stock HTC One X and downloaded a stable build from http://wiki.cyanogenmod.org/w/Install_CM_for_endeavoru.
I followed the tutorials and unlocked my device and started off with CWM recovery 5.8.2.7. Did some experiemenation with backup and recovery. So far, so good.
I decided to use the 4.4 ROM and as per some information available it needed me to update to CWM 6.0.4.8. I did so but when I tried to go in recovery, the screen went blank. Tried it multiple times without luck.
Then I switched over to TWRP 2.7.1 and used it to install the cm-11-20141112-SNAPSHOT-M12-endeavoru.zip. It failed with status 7. Assert checks on bootloader ver failed (as per checks it would need anything 1.28 or higher). I am on hboot 1.12. I extracted the boot.img from the rom zip and flashed it from fastboot. It showed no change in hboot version (maybe this is where I faulted). It still won't install rom zip as I would expect.
Now the phone won't go beyond "Quietly Brilliant" screen on power on. Recovery to saved backup says its successful but it still gets stuck at same screen on reboot.
Would appreciate help and pointers from anyone who could help.
Thanks in advance,
Kunal
Click to expand...
Click to collapse
give me the result from command fastboot getvar version-main. And after this we will see haow to upgrade your hboot you are with too low hboot version
Thant said:
give me the result from command fastboot getvar version-main. And after this we will see haow to upgrade your hboot you are with too low hboot version
Click to expand...
Click to collapse
Hi,
Thanks pal ! Here is the output of fastboot getvar version-main
version-main: 0.0.0.178434
thanks,
Kunal
Ok.....so as I mentioned in my first post, I did play around with CWM 5.8.2.7 at the beginning and had made a backup. So I flashed CWM again and was able to restore my device.
Now, I need to update to CM11 ROM and would need help with that please. I guess what I already have is there in the first post I put in this thread. Here's the dump of fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.12.2000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 0.0.0.178434
(bootloader) serialno: HT22WW100191
(bootloader) imei: 3591*********75
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ461****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4217mV
(bootloader) devpower: 100
(bootloader) partition-layout: None
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
thanks again in advance,
Kunal
koolvirgo said:
Ok.....so as I mentioned in my first post, I did play around with CWM 5.8.2.7 at the beginning and had made a backup. So I flashed CWM again and was able to restore my device.
Now, I need to update to CM11 ROM and would need help with that please. I guess what I already have is there in the first post I put in this thread. Here's the dump of fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.12.2000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 0.0.0.178434
(bootloader) serialno: HT22WW100191
(bootloader) imei: 3591*********75
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ461****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4217mV
(bootloader) devpower: 100
(bootloader) partition-layout: None
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
thanks again in advance,
Kunal
Click to expand...
Click to collapse
No problem you are S-OFF Download this RUU relock your bootloader or if it's locked leave it locked and run the RUU this will upgrade your phone to 3.14.401.31 then upgrade to latest 4.18.401.4 after this you can unlock the bootloader and flash custom recovery latest TWRP or CWM or Philz and flash what you want
Thant said:
No problem you are S-OFF Download this RUU relock your bootloader or if it's locked leave it locked and run the RUU this will upgrade your phone to 3.14.401.31 then upgrade to latest 4.18.401.4 after this you can unlock the bootloader and flash custom recovery latest TWRP or CWM or Philz and flash what you want
Click to expand...
Click to collapse
Hi Thant,
Thanks for your tip. I will give this a try (though I will be able to try it out someone later this week only and provide update how it went).
Having said that, I have one question though - the link to RUU you specified looks like for unlocked HTC Europe version. I'm from India and I found that there might be one with same radio for India here.
Not doubting your advice, but just want to know what is the basis for knowing what RUU one must use ?
Also, can I choose the one for India (RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_India_3.14.720.24_Radio_5.1204.162.29) ?
thanks,
Kunal
koolvirgo said:
Hi Thant,
Thanks for your tip. I will give this a try (though I will be able to try it out someone later this week only and provide update how it went).
Having said that, I have one question though - the link to RUU you specified looks like for unlocked HTC Europe version. I'm from India and I found that there might be one with same radio for India here.
Not doubting your advice, but just want to know what is the basis for knowing what RUU one must use ?
Also, can I choose the one for India (RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_India_3.14.720.24_Radio_5.1204.162.29) ?
thanks,
Kunal
Click to expand...
Click to collapse
yes if you want, most of the people like European version not Asian. It is your choice you are S-OFF and you can flash what you want on your phone. And the radio is the same
Thant said:
yes if you want, most of the people like European version not Asian. It is your choice you are S-OFF and you can flash what you want on your phone. And the radio is the same
Click to expand...
Click to collapse
Hi Thant,
I did try the RUU you told me to use but update failed with error 159.
There are some RUUs for Indian models at http://www.androidruu.com/?developer=Endeavor and http://forum.xda-developers.com/showthread.php?t=2189048 but none for JB.
I have provided the getvar dump earlier but can't seem to find what I need to use (sorry for being a noob here). Please suggest what I can do more.
Merry Christmas and a Happy New Year.
thanks,
Kunal
koolvirgo said:
Hi Thant,
I did try the RUU you told me to use but update failed with error 159.
There are some RUUs for Indian models at http://www.androidruu.com/?developer=Endeavor and http://forum.xda-developers.com/showthread.php?t=2189048 but none for JB.
I have provided the getvar dump earlier but can't seem to find what I need to use (sorry for being a noob here). Please suggest what I can do more.
Merry Christmas and a Happy New Year.
thanks,
Kunal
Click to expand...
Click to collapse
are you charge your phone before run the RUU are you reloack the bootloader before run the RUU???
Thant said:
are you charge your phone before run the RUU are you reloack the bootloader before run the RUU???
Click to expand...
Click to collapse
Yes, I did both !!
koolvirgo said:
Yes, I did both !!
Click to expand...
Click to collapse
Are your phone say Endeavoru PVT in bootloader or say Endeavoru XE?
I have the same issue, I used the WinDroid toolkit but somehow I got stuck in the boot. I can go in recovery. My phone says endeavoru pvt. I also have the S-on.
INFOversion: 0.5a
INFOversion-bootloader: 1.72.0000
INFOversion-baseband: 5.1204.167.31
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.18.401.4
INFOserialno: HT23NW107620
INFOimei: 359188041361783
INFOproduct: endeavoru
INFOplatform: HBOOT-T30S
INFOmodelid: PJ4610000
INFOcidnum: HTC__405
INFObattery-status: good
INFObattery-voltage: 3660mV
INFOdevpower: 3
INFOpartition-layout: None
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: None
INFOhbootpreupdate: 2
INFOgencheckpt: 0
Click to expand...
Click to collapse
What I have to do?? Thanks for the help you are saving me!!
lollerz46 said:
I have the same issue, I used the WinDroid toolkit but somehow I got stuck in the boot. I can go in recovery. My phone says endeavoru pvt. I also have the S-on.
What I have to do?? Thanks for the help you are saving me!!
Click to expand...
Click to collapse
Okay I solved my problem, my issue was the boot.img that was different from the one inside the custom rom! Hope this helps
Thant said:
Are your phone say Endeavoru PVT in bootloader or say Endeavoru XE?
Click to expand...
Click to collapse
It says Endeavoru XE
koolvirgo said:
It says Endeavoru XE
Click to expand...
Click to collapse
Than this is bad news try to download ICS Asian RUU and restore it, then try to update to latest Asian rom if this not work you maust to update your hboot manualy the XE variant have a lot of problems with the update but first try to run ICS Asian RUU then check for update and then update Try this RUU
Thant said:
Than this is bad news try to download ICS Asian RUU and restore it, then try to update to latest Asian rom if this not work you maust to update your hboot manualy the XE variant have a lot of problems with the update but first try to run ICS Asian RUU then check for update and then update Try this RUU
Click to expand...
Click to collapse
Hi Thant,
I have not yet tried tried the ICS RUU you suggested. But before I go ahead, here's some more info.
The Android version, HTC Sense version both say "Protected"
Software number is "Unknown"
HTC SDK API level is 4.23
Kernel is 2.6.39.4-g7ecc196
Baseband version is 2.1204.135.20
Build no. is 0.1.0.0 (20130509 EndeavorU_Generic_WWE#178434)
Boot loader says -
ENDEAVORU XE ENG S-OFF RH
CID-11111111
HBOOT- 1.12.2000 (PJ461****)
CPLD-None
MICROP-None
RADIO-2.1204.135.20
Now, should I go ahead with the ICS RUU ?
How do I know what Android version I'm on ? Why would it say protected ? Any command I can fire from fastboot/adb ?
[getvar says (bootloader) version-main: 0.0.0.178434]
Thanks for all your time & help,
Kunal
koolvirgo said:
Hi Thant,
I have not yet tried tried the ICS RUU you suggested. But before I go ahead, here's some more info.
The Android version, HTC Sense version both say "Protected"
Software number is "Unknown"
HTC SDK API level is 4.23
Kernel is 2.6.39.4-g7ecc196
Baseband version is 2.1204.135.20
Build no. is 0.1.0.0 (20130509 EndeavorU_Generic_WWE#178434)
Boot loader says -
ENDEAVORU XE ENG S-OFF RH
CID-11111111
HBOOT- 1.12.2000 (PJ461****)
CPLD-None
MICROP-None
RADIO-2.1204.135.20
Now, should I go ahead with the ICS RUU ?
How do I know what Android version I'm on ? Why would it say protected ? Any command I can fire from fastboot/adb ?
[getvar says (bootloader) version-main: 0.0.0.178434]
Thanks for all your time & help,
Kunal
Click to expand...
Click to collapse
You are S-OFF you can run any RUU but your problem is that your phone say XE not PVT the XE edition have problem with the update hboot
Thant said:
You are S-OFF you can run any RUU but your problem is that your phone say XE not PVT the XE edition have problem with the update hboot
Click to expand...
Click to collapse
Hi Thant,
I tried it and failed Needless to say I made sure all the prerequisites were met.
Can you please tell me how to manually update hboot ?
thanks,
Kunal
koolvirgo said:
Hi Thant,
I tried it and failed Needless to say I made sure all the prerequisites were met.
Can you please tell me how to manually update hboot ?
thanks,
Kunal
Click to expand...
Click to collapse
fastboot oem lock - relock the bootloader
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip (AGAIN)
fastboot reboot-bootloader
fastboot flash unlocktoken Unlock_code.bin
then like normal flash recovery and then rom
You can find firmware.zip from OTA on the page with the RUU choice one OTA and flash it try with this one in attachment
Thant said:
fastboot oem lock - relock the bootloader
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip (AGAIN)
fastboot reboot-bootloader
fastboot flash unlocktoken Unlock_code.bin
then like normal flash recovery and then rom
You can find firmware.zip from OTA on the page with the RUU choice one OTA and flash it try with this one in attachment
Click to expand...
Click to collapse
Hi Thant,
Before trying what you suggested (for manual update) I tried the ICS RUU once again. It went through fine this time not sure why, then I did an OTA upgrade and now I'm on Android 4.0.4 hboot 1.12 (same as before but on 2.17.720.2). There are no more OTA updates available, though HTC india website says there is one available for 3.14.720.24 which is JB version and should automatically update my hboot which I can then hopefully use to update to 4.4 ROM. Do you think what I think is going to work ?
But I can't find the OTA firmware for 3.14.720.24. There was one available here but no more.
There's one here but not sure about the authenticity of this.
I have downloaded the firmware zip you shared but it seems the file is corrupt.
Thanks,
Kunal

[Q] One M8 HTC__001 CID, Firmware/No Wifi problem

Hello, I've been a long time xda lurker (Never thought I could really add much anyhow) since I had my Dell Streak and I think for the first time since I got my M8 I need a bit of help.
They rolled out the lollypop OTA update here in Ireland and figured It was time to update to a stock ROM from here or a slightly improved one but ever since then I have lost my WiFi completely.
Sorry If this makes no seance- at all I'm a little burnt out trying to solve this on my own but even going back to 4.4.3 ROMs I still have no WiFi at all and any help at all would be greatly appreciated.
This is all the info I took from fastboot and the bootloader I thought would be needed
Bootloader Info
*** Tampered ***
*** Unlocked ***
M8_UL PVT SHIP S-ON
HBOOT - 3.18.0.0000
RADIO - 1.19.21331147A1.09G
OpenDSP - v38.2.2-00542-M8974.0311
OS - 2.22.401.4
Fastboot Getvar All Info
version: 0.5
version-bootloader: 3.18.0.0000
version-baseband: 1.19.21331147A1.09G
version-cpld: None
version-microp: None
version-main: 2.22.401.4
version-misc: PVT SHIP S-ON
serialno: xxx
imei: xxx
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 5e4b24e4
hbootpreupdate: 11
gencheckpt: 0
Thanks again for even looking!
First - remove the serial no. & imei no. as those are sensitive info.
The details that you have does not show that you did OTA. You are still two versions behind.
Restore your stock ROM, flash a matching stock recovery (no custom recovery) then do OTA ... multiple OTAs up to the latest 4.16.410.10
If you're willing to set the phone up from scratch you can just update straight to Lollipop using the RUU available on here. If you want to go that route then you can following this guide I wrote:
http://forum.xda-developers.com/showthread.php?t=2735235
Basically, step 3 covers what you need to do as step 1 and 2 are already done and at least once that's done if you still have issues you know it's not the software on the phone
ckpv5 said:
First - remove the serial no. & imei no. as those are sensitive info.
The details that you have does not show that you did OTA. You are still two versions behind.
Restore your stock ROM, flash a matching stock recovery (no custom recovery) then do OTA ... multiple OTAs up to the latest 4.16.410.10
Click to expand...
Click to collapse
Thank you I didn't even think of that I edited them out.
EddyOS said:
If you're willing to set the phone up from scratch you can just update straight to Lollipop using the RUU available on here. If you want to go that route then you can following this guide I wrote:
http://forum.xda-developers.com/showthread.php?t=2735235
Basically, step 3 covers what you need to do as step 1 and 2 are already done and at least once that's done if you still have issues you know it's not the software on the phone
Click to expand...
Click to collapse
I will try that right away thank you for your help I'll post back here when I'm done
No luck, kept getting error 99 with the 'htc_fastboot" from the thread and with my normal fastboot it gives me the error 32 'header error' I only noticed the thread was for s-off phones, I don't care about my phone saying tampered, unlocked or anything but I'm assuming that's stopping the flash from happening.
You must relock your device first ... then try again with flash the ruu.zip
Isotopes said:
You must relock your device first ... then try again with flash the ruu.zip
Click to expand...
Click to collapse
Haha yeah that worked now, ignoring the guide at the start and just leaving it with the relocked warning it's flashing now via the RUU
Thanks to the both of you for your help.

HTC M8 T-mobile GPE conversion screw up - Hboot 3.18.0.0000 and S-ON

Hey everyone, this is my first post on xda and I'm hoping I could get some help regarding my HTC M8. A while back I attempted to convert my M8 to GPE, but alas the process was unsuccessful (at least for the most part). I don't quite remember the cause because it was several months ago, but I'm pretty sure I made a mistake and took an OTA incorrectly. After the failed attempt, my phone ended up soft-bricked and displayed nothing but a black screen. Luckily, I was somehow able to get to CWM recovery and flash Skydragon GPE 4.4.4, which at least got the phone working for the most part. Unfortunately after the whole fiasco, the M8's bootloader background became black and displayed a broken "Android" lying on it's back. To make matters worse, the bootloader was S-ON and displayed the Hboot as 3.18.0.0000 (which to my understanding is the GPE Hboot and puts me in a catch 22). The Radio and OpenDSP displayed "INVALID_VER_INFO" and the OS displayed "1.57.531.7 (2.12.1700.1)". I recently flashed TWRP and the OS became blank.
I would really appreciate some help restoring my bootloader screen to normal and/or accomplishing one of two things:
Upgrade my phone from 4.4.4 to 5.x.x (The only rom which has worked was Sky Dragon 5.0.1, but Wi-Fi doesn't work which I've read is because of my current firmware.)
Restore my M8 back to stock sense with root.
I've tried flashing GPE and Sense Firmwares/Hboots, but all failed and gave me something like "error 99" (likey because it's S-ON).
I've tried gaining S-Off through Sunshine, but Sunshine says it needs a rom or kernel closer to stock in order to work.
I've tried flashing stock roms to get Sunshine to work, but they all fail and either get stuck at HTC load screen or give "error 7" (also assuming because Hboot is GPE and not Sense).
I've tried several different versions of alternative roms that could work with Sunshine such as ARHD as well as Maximus HD, but all fail and give "error 7".
I've tried to restore to stock with several T-Mobile RUU's, but they all fail and gave me "error 159" (probably because of conflicting Hboot 3.18).
So, is there anything else I can do? Any help is greatly appreciated. Thanks!
Below is some information pulled from ADB to possibly help shed more light on the situation.
version: 0.5
version-bootloader: 3.18.0.0000
version-baseband: INVALID_VER_INFO
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA46RWM19558
imei: 352628061928554
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B13000
cidnum: T-MOB010
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 6e0f5a3d
hbootpreupdate: 11
gencheckpt: 0​
Did you make the phone s-on, or did it somehow get that way itself?
The Sense ROMs will all fail to install, since you've converted to GPE partitioning, the system partition is now too small to accept any Sense ROMs.
Thursday41 said:
I've tried flashing GPE and Sense Firmwares/Hboots, but all failed and gave me something like "error 99" (likey because it's S-ON).
Click to expand...
Click to collapse
You will only be able to flash firmware that is signed, and for T-Mobile. So if you are trying to flash any firmware that doesn't meet that description, its a waste of time, as they will fail.
Also, your bootloader needs to be LOCKED or RELOCKED to flash a signed firmware or RUU.
Thursday41 said:
I've tried to restore to stock with several T-Mobile RUU's, but they all fail and gave me "error 159" (probably because of conflicting Hboot 3.18).
Click to expand...
Click to collapse
Possibly due to the 3.18 hboot. But make sure the RUUs correspond to hboot 3.19, which would be either 3.xx or 4.xx RUUs (Android 4.4.4 or 5.0). Older RUUs will have hboot numbers 3.16 and 3.17, which are guaranteed to fail (no downgrading of hboot allowed with s-on). So again, its a waste of time to try.
I would try to find and flash the T-Mobile 4.20.531 firmware, then try the 4.20.561 RUU.

Need help to return to stock rom

Hello,
I bought a M8s (m8ql_ul), but I found it rooted.
How can I return to stock rom ?
The OS version is unknown : the version-main is empty (listed by : fastboot getvar all)
My M8s is :
- Unlocked
- Rooted
- S-ON
------------------------------
version-bootloader: 3.19.0.0000
version-baseband: [email protected]
version-main:
version-misc: PVT SHIP S-ON
serialno: ---------
imei: -------------------------
product: m8ql_ul
platform: hTCBmsm8939
modelid: 0PKV10000
cidnum: HTC__102
security: on
--------------------------------
Can I use an international stock rom x.x.401.x ?
Do you have a link to it ?
Thank you.
TF85 said:
Hello,
I bought a M8s (m8ql_ul), but I found it rooted.
How can I return to stock rom ?
The OS version is unknown : the version-main is empty (listed by : fastboot getvar all)
My M8s is :
- Unlocked
- Rooted
- S-ON
------------------------------
version-bootloader: 3.19.0.0000
version-baseband: [email protected]
version-main:
version-misc: PVT SHIP S-ON
serialno: ---------
imei: -------------------------
product: m8ql_ul
platform: hTCBmsm8939
modelid: 0PKV10000
cidnum: HTC__102
security: on
--------------------------------
Can I use an international stock rom x.x.401.x ?
Do you have a link to it ?
Thank you.
Click to expand...
Click to collapse
Its out there. I put it on the sd external card. I rename it 0PKVIMG.zip and start into bootloader where it gets read instantaneously and begins to install the sense 7.0 Android 6.0. IF you have first relocked your bootloader at htcdev .
It is explained by htcdev
You can do it too as I did.
Hello,
Then I can try with any stock rom having the Sense 7 and Android 6 ?
Like : 2.10.401.1
Thank you
TF85 said:
Hello,
Then I can try with any stock rom having the Sense 7 and Android 6 ?
Like : 2.10.401.1
Thank you
Click to expand...
Click to collapse
There is only one I have seen that is out there to download. It worked and my phone can be completely restored to the basic MM. It then immediately prompts to update as it is the initial MM 6.0 to start. Then it may update a 2nd time. It is sense 7 and android 6 Marshmallow. It is EU vsn. Don't know about other continents and carrier versions.
Hello,
I downloaded this one :
0PKVIM[email protected]60201_20.05_018_F_release_479349_combined_signed.MD5.zip
I'll try do flash it.
thank you
TF85 said:
Hello,
I downloaded this one :
0PKVIM[email protected]60201_20.05_018_F_release_479349_combined_signed.MD5.zip
I'll try do flash it.
thank you
Click to expand...
Click to collapse
How did it go? Did it went?
Hello,
I downloaded it at this link :
https://www.androidfilehost.com/?fid=24591023225176246
Good luck
Did it work for you ? I'm also trying to go back to stock on my m8s. Tell me how did you do it if it worked.
Hello,
I could not flash it, TWRP print several errors.
I tried the TWRP-4.16.401.13.zip, TWRP sent me errors like : <Could not find "META-INF/com/google/android/update-binary" in the zip file>
No idea.
Hello,
I had to lock the bootloader, before flashing the zip file.
This flash is now installed (0PKVIM[email protected]60201_20.05_018_F_release_479349_combined_signed.zip), and it works.
This version is compatible with these CID :
HTC__001,
HTC__102,
HTC__032,
HTC__Y13,
HTC__031,
HTC__M27,
HTC__002,
HTC__A07.
and for the modelid : 0PKV10000
The OTA will work.
How to do :
This flash is for
Firstly, charge the M8s to 100%.
1- Lock the bootloader, it became "RELOCKED".
2- With your PC, copy this zip file into an SD card, remane it : 0PKVIMG.zip (it starts with zero)
3- Insert the sd card into M8s and boot into bootloader,
4- It takes at least 10 minutes to finish the new flash.
Good luck.
I want to flash the same version too but when I relock the bootloader there is some bugs that make that the flash doesn't work. Please help.

Bought a new unlocked phone, been a while, what's next?

Greetings,
Would appreciate any help/direction. It's been a while since I bought a new phone to mess with, even longer since it was GSM.
Picked up a new unlocked HTC10, I want to get it updated to Oreo firmware and ready to go for US Carrier Ting (well, T-Mobile). Will probably run Leedroid's ROM, but may test others.
I have done HTCDev unlock and installed TWRP, what's next to get Oreo Firmware before flashing ROMs?
I'm also guessing I'll need to change the CID, and maybe the MID.
Download mode info:
*** UNLOCKED ***
htc_pmeuhl PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.8996.00007_0809
OS-2.41.401.4
Jan 25 2017 , 18:33:04(857212)
fastboot getvar all
kernel: lk
product: htc_pmeuhl
version: 1.0
max-download-size: 1579200000
serialno:
current-slot:
imei:
version-main: 2.41.401.4
boot-mode: download
version-baseband: [email protected]
version-bootloader: 1.0.0.0000
mid: 2PS620000
cid: 11111111
Once again, thanks for any assistance.
Change your CID to HTC__034, after that flash this ruu in download mode, boot the device and check for the OTA oreo update.
https://androidfilehost.com/?fid=889964283620778317
Mr Hofs said:
Change your CID to HTC__034, after that flash this ruu in download mode, boot the device and check for the OTA oreo update.
https://androidfilehost.com/?fid=889964283620778317
Click to expand...
Click to collapse
Thanks for the info. Do I need to get S-OFF before I can change the CID?
Attempting to change it now results in: FAILED (remote: WRITE CID PERMISSION ERROR)
Also, the current CID is the "SuperCID" 11111111. Do I really need to change it?
Thanks again!
zisix said:
Thanks for the info. Do I need to get S-OFF before I can change the CID?
Attempting to change it now results in: FAILED (remote: WRITE CID PERMISSION ERROR)
Also, the current CID is the "SuperCID" 11111111. Do I really need to change it?
Thanks again!
Click to expand...
Click to collapse
I thought it was S-OFF (i know it says S-ON in your info though) because supercid like you have can only be written with S-OFF.
Try the ruu without changing the CID but it may fail due to incompatible CID. If that is so run the S-OFF sunshine tool just for fun to see if it has been used.
Mr Hofs said:
I thought it was S-OFF (i know it says S-ON in your info though) because supercid like you have can only be written with S-OFF.
Try the ruu without changing the CID but it may fail due to incompatible CID. If that is so run the S-OFF sunshine tool just for fun to see if it has been used.
Click to expand...
Click to collapse
That worked. Afterwards I installed TWRP again, then Leedroid.
All set now, thanks!

Categories

Resources