Related
status: HTC One X, s-off, unlocked, no reliable firmware or ROM
the last things I've done are to follow steps in this thread: http://forum.xda-developers.com/showthread.php?t=2598659
synopsis:
unlocked phone, changed CID to HTC__E11,
relocked phone, flashed firmware 3.14.401.31, ran RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed.exe
unlocked phone, flashed CWM recovery 5.8.4.0
problem: ROM will not start up and run reliably. I can't start recovery from bootloader, so I can't install another rom.
current getvar all:
Code:
version: 0.5a
version-bootloader: 1.39.0000
version-baseband: 5.1204.162.29
version-cpld: None
version-microp: None
version-main: 3.14.401.31
serialno: FA2A4W102453
imei: 35399505028163
product: endeavoru
platform: HBOOT-T30S
modelid: PJ461****
cidnum: HTC__E11
battery-status: low
battery-voltage: 3527mV
devpower: 0
partition-layout: None
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
further details
further history:
phone was imported into new zealand from unknown origin
when I started working on the phone, I remember is having CID: 11111111, and had HBOOT 0.96
I think Hong Kong zoned firmware and RUU 1.29.708.15 were a combination which allowed me entry to CWM successfully, though low hboot version limited me from flashing cyanogenmod 10.1/ 10.2. Didn't try other ROMs
when I was flashing earlier, the battery charge was above 4000mV, it seems to have lost a lot of charge overnight
any help or advice around finding the right firmware/RUU that might help me install a working ROM would be amazing.
if I'm barking up the wrong tree also happy to explore other leads.
thanks in advance
okey..for working recovery download cwm.img and flash it from FASTBOOT..then you can restore stock backup or flash custom rom..
Sent from my EndeavorU using Tapatalk 2
whimful said:
further history:
phone was imported into new zealand from unknown origin
when I started working on the phone, I remember is having CID: 11111111, and had HBOOT 0.96
I think Hong Kong zoned firmware and RUU 1.29.708.15 were a combination which allowed me entry to CWM successfully, though low hboot version limited me from flashing cyanogenmod 10.1/ 10.2. Didn't try other ROMs
when I was flashing earlier, the battery charge was above 4000mV, it seems to have lost a lot of charge overnight
any help or advice around finding the right firmware/RUU that might help me install a working ROM would be amazing.
if I'm barking up the wrong tree also happy to explore other leads.
thanks in advance
Click to expand...
Click to collapse
first of all flash again the same RUU 3.14.401.31 after this receive all update to latest JB and after this install Philz recovery and custom rom the 3.14 is not the lastest firmware for the HOX it is 4.20.401.3
whimful said:
status: HTC One X, s-off, unlocked, no reliable firmware or ROM
the last things I've done are to follow steps in this thread: http://forum.xda-developers.com/showthread.php?t=2598659
synopsis:
unlocked phone, changed CID to HTC__E11,
relocked phone, flashed firmware 3.14.401.31, ran RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed.exe
unlocked phone, flashed CWM recovery 5.8.4.0
problem: ROM will not start up and run reliably. I can't start recovery from bootloader, so I can't install another rom.
current getvar all:
Code:
version: 0.5a
version-bootloader: 1.39.0000
version-baseband: 5.1204.162.29
version-cpld: None
version-microp: None
version-main: 3.14.401.31
serialno: FA2A4W102453
imei: 35399505028163
product: endeavoru
platform: HBOOT-T30S
modelid: PJ461****
cidnum: HTC__E11
battery-status: low
battery-voltage: 3527mV
devpower: 0
partition-layout: None
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
Click to expand...
Click to collapse
can u guide me how u changed ur cid because i also want to change my cid i am using one x with CID Orange_001
ahmed309 said:
can u guide me how u changed ur cid because i also want to change my cid i am using one x with CID Orange_001
Click to expand...
Click to collapse
fastboot oem writecid 11111111
11111111 - Super CID other CID you can check in nandroid backup thread mine is HTC__032 x.xx.401.x WWE base
phone no longer booting
thanks for everyone's suggestions.
since the first post I haven't been able to try anything, because phone seems unresponsive (will not boot at all).
I've tried leaving it all night plugged into a wall charger (while off).
If it is battery, I'm aware of charging issues this phone has and the batchfile/ cwm 5.8.4.0 workarounds, but I can't get into recovery nor bootloader. If it's charge is there any way to get the phone enough charge?
Is the phone bricked?
phone now has some charge, still being awkward
ok have access to bootloader again. I'm trying rerunning the RUU, but having trouble... RUU tries to restart phone but fails.
I'm wondering if i've misunderstood how the region matters. the only stability i have seen is with old honkkong region firmware and old RUU (RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.29.708.15_Radio_2.1204.122.17_release_268338_signed.exe)
can anyone give me a clear idea of whether using x.xx.401.xx on an s-off phone makes any difference ...
or should i be looking for x.xx.708.xx ruu and 708/hongkong firmware?
1. Make sure you already have TWRP installed.
Recommended:
TWRP 2.8.1.0 for 1.xx.xxx.x & 2.xx.xxx.x TWRP backup
TWRP 2.8.3.0 for 3.xx.xxx.x TWRP backup
TWRP 2.8.4.0 or 2.8.5.0 or 2.8.6.0 and highly recommended 2.8.7.0 or latest for 4.xx.xxx.x & 6.xx.xxx.x TWRP backup
Install TWRP 2.8.1.0 -
command fastboot flash recovery twrp-2.8.1.0-m8.img
Install TWRP 2.8.3.0 -
command fastboot flash recovery twrp-2.8.3.0-m8.img
Install TWRP 2.8.4.0 -
command fastboot flash recovery twrp-2.8.4.0-m8.img
Install TWRP 2.8.5.0 -
command fastboot flash recovery twrp-2.8.5.0-m8.img
Install TWRP 2.8.6.0 -
command fastboot flash recovery twrp-2.8.6.0-m8.img
Install TWRP 2.8.7.0 -
command fastboot flash recovery twrp-2.8.7.0-m8.img
The basic idea is : fastboot flash recovery NameOfRecovery.img
Download TWRP - https://twrp.me/htc/htconem8gsm.html
2. Download TWRP backup - link in post #2 (for KitKat & Lollipop) and post #3 (for Marshmallow)
3. Download stock recovery - link in post #4
4. Extract the downloaded x.xx.xxx.x_ckpv5.zip on PC
5. Boot to TWRP recovery and make a backup of boot only, this is to see where the backup goes on your device.
6(a). Reboot, connect device to PC then
open Internal Storage - TWRP/BACKUPS/SerialNo./ (if backup is set to internal storage)
open SD Card - TWRP/BACKUPS/SerialNo./ (if backup is set to MicroSD)
6(b). For those with no OS, connect device to PC. In TWRP recovery go to mount, make sure MTP is enabled.
Then you can open Internal Storage - TWRP/BACKUPS/SerialNo./ (if backup is set to internal storage)
7. Transfer the extracted x.xx.xxx.x folder (not x.xx.xxx.x_ckpv5 folder) and its content to the backup path on your device, so it looks like this :
TWRP/BACKUPS/SerialNo./x.xx.xxx.x
8. Reboot to TWRP, wipe your device - in TWRP go to wipe - advance - select dalvik cache, cache, data, system (only these)
9. Restore the transferred backup - make sure all boot, data & system are ticked - swipe to restore
10. In reboot menu select bootloader (when TWRP asks whether you want to root your device, select do not install)
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery x.xxx.xx.x_recovery.img
12. reboot - check for OTA, download, install
13. you may have multiple OTA when your device currently on a lower version
14. done
If you want to flash TWRP again, use the latest TWRP after last OTA
NOTE : There is no need to relock bootloader when doing the nandroid way to revert to stock and do OTA.
My TWRP backup collections I
hboot 3.16.0000 - 1.xx.xxx.x
hboot 3.18.0000 - 2.xx.xxx.x
hboot 3.19.0000 - 3.xx.xxx.x (KitKat)
hboot 3.19.0000 - 4.xx.xxx.x (Lollipop)
hboot 3.19.0000 - 6.xx.xxx.x (Marshmallow) - see post #3
CID ORANG001
MID 0P6B10000 - x.xx.61.x
2.26.61.1
3.33.61.9
4.19.61.2
4.19.61.3
CID ORANGB10
MID 0P6B10000 - x.xx.69.x
1.54.69.5
1.70.69.2
2.26.69.1
3.33.69.1
4.19.69.3
4.19.69.4 - thanks @Petert87
CID ORANG309
MID 0P6B10000 - x.xx.75.x
1.54.75.5
2.26.75.1
3.33.75.1
4.19.75.2
4.19.75.3
CID T-MOB101
MID 0P6B10000 - x.xx.111.x
4.19.111.2
4.19.111.3
4.19.111.4
CID T-MOB102
MID 0P6B10000 - x.xx.112.x
2.23.112.3
3.29.112.9
4.19.112.2
4.19.112.3
4.19.112.4
CID T-MOB003
MID 0P6B10000 - x.xx.114.x
3.29.114.9
4.19.114.2
4.19.114.3
4.19.114.4
CID T-MOB009
MID 0P6B10000 - x.xx.118.x
1.57.118.2
2.23.118.3
3.29.118.9
4.19.118.2
4.19.118.3
4.19.118.4
CID VODAP001, VODAP102, VODAPE17, VODAP405, VODAP304, VODAPD18
MID 0P6B10000 - x.xx.161.x
1.12.161.17 - thanks @Petert87
1.54.161.5 - thanks @Petert87
1.54.161.10
1.54.161.10 - thanks @Petert87
2.22.161.6
2.22.161.6 - thanks @Petert87
3.29.161.5 - thanks @Petert87
3.29.161.9 - thanks @Petert87
4.19.161.2
4.19.161.2 - thanks @Petert87
4.19.161.3
4.19.161.3 - thanks @Petert87
4.19.161.4 - thanks @Petert87
CID VODAP203
MID 0P6B10000 - x.xx.163.x
4.19.163.3
CID VODAP110 & VODAP120
MID 0P6B10000 - x.xx.166.x
4.19.166.2 - thanks @Pagrio for the backup
4.19.166.3 - thanks @percusion for the backup
CID O2___001 & O2___102
MID 0P6B10000 - x.xx.206.x
1.54.206.10
2.22.206.6
3.32.206.9
4.20.206.1
4.20.206.2
CID HTC__001, HTC__J15, HTC__E11, HTC__203, HTC__102, HTC__405, HTC__Y13, HTC__A07, HTC__304, HTC__032, HTC__016, HTC__M27, HTC__K18, HTC__002, HTC__A48
MID 0P6B10000 - x.xx.401.x
2.22.401.5
3.28.401.6
3.28.401.7
3.28.401.9
4.16.401.10
4.16.401.13
CID CWS__001
MID 0P6B12000 - x.xx.502.x
1.58.502.1
2.23.502.3
3.42.502.1
4.28.502.1
4.28.502.2
CID T-MOB010
MID 0P6B13000 - x.xx.531.x
4.20.531.5
CID HTC__332
MID 0P6B16000 - x.xx.599.x
1.57.599.1
2.25.599.1
3.36.599.2
4.20.599.3
4.20.599.4
CID HTC__332
MID 0P6B16000 - x.xx.600.x
1.12.600.20
4.32.600.2
CID ROGER001
MID 0P6B16000 - x.xx.631.x
2.23.631.2
3.34.631.4
4.20.631.2
4.20.631.3
CID TELUS001
MID 0P6B16000 - x.xx.661.x
3.34.661.4
4.20.661.2
4.20.661.3
CID BM___001 & SASKT001
MID 0P6B16000 - x.xx.666.x
1.55.666.4
2.23.666.2
3.34.666.4
4.20.666.1
4.20.666.2
CID HTC__044 & HTC__059
MID 0P6B11000 - x.xx.707.x
1.54.707.7
2.22.707.4
3.32.707.9
4.19.707.2
4.19.707.4
CID HTC__622
MID 0P6B63000 - x.xx.708.x
1.60.708.2
2.11.708.2
3.32.708.4
4.18.708.12
CID HTC__621
MID 0P6B11000 - x.xx.709.x
1.54.709.12
2.22.709.3
3.28.709.6
4.16.709.9
4.24.709.2
4.24.709.3
CID HTC__039 & VODAP021
MID 0P6B11000 - x.xx.710.x
1.54.710.8
2.23.710.1
3.32.710.9
4.20.710.5
4.20.710.7
4.20.710.9
CID HTC__038
MID 0P6B65000 - x.xx.720.x
4.18.720.8 - thanks @n1234d for the backup
4.18.720.10
CID H3G__001, H3G__106, H3G__402, H3G__G04
MID 0P6B10000 - x.xx.771.x
1.54.771.9
2.22.771.5
3.32.771.10
4.20.771.2
4.25.771.6
CID TELST001
MID 0P6B11000 - x.xx.841.x
1.54.841.8
2.23.841.1
3.32.841.9
4.19.841.5
4.19.841.9
CID TIM__401
MID 0P6B10000 - x.xx.901.x
2.22.901.5
3.31.901.9
4.20.901.3
4.20.901.4 - thanks @Petert87
CID OPTUS001
MID 0P6B65000 - x.xx.980.x
1.54.980.5
2.07.980.2
3.32.980.4
4.18.980.9
4.18.980.11
CID HTC__247
MID 0P6B10000 - x.xx.1020.x
3.31.1020.9
4.21.1020.1
CID GLOBA001
MID 0P6B13000 - x.xx.1500.x
1.55.1500.4
2.23.1500.2
3.34.1500.4
4.20.1500.1
4.20.1500.2
CID BS_US001, BS_US002
MID 0P6B12000, 0P6B13000 - x.xx.1540.x
2.22.1540.4
4.16.1540.8
4.17.1540.9
M8 Dual-SIM only
CID HTC__001, HTC__A07, HTC__J15, HTC__A48, HTC__Y13, HTC__032 & HTC__102
MID 0P6B64000 & 0P6B68000
4.30.401.16
M8 EYE only
CID HTC__001 & HTC__J15
MID 0P6B81000
1.82.401.7 - thanks @Hazem99922 for the backup
CID HTC__038
MID 0P6B90000
1.80.720.1 - thanks @Shreyas for the initial backup
My TWRP backup collections II
hboot 3.19.0000 - 6.xx.xxx.x (Marshmallow)
CID ORANG001
MID 0P6B10000
6.12.61.4
CID ORANGB10
MID 0P6B10000
6.14.69.4 - thanks @Petert87
CID ORANG309
MID 0P6B10000
6.14.75.4 - thanks @Petert87
CID T-MOB101
MID 0P6B10000
6.12.111.4
CID T-MOB102
MID 0P6B10000
6.12.112.4 - thanks @Imotep95
CID T-MOB003
MID 0P6B10000
6.12.114.4 - thanks @Petert87
CID T-MOB009
MID 0P6B10000
6.12.118.4
CID VODAP001, VODAP102, VODAPE17, VODAP405, VODAP304, VODAPD18
MID 0P6B10000
6.12.161.4 - thanks @Petert87
CID VODAP203
MID 0P6B10000
6.12.163.4
CID VODAP110 & VODAP120
MID 0P6B10000
6.12.166.4 - thanks @percusion
Try this link : https://mega.nz/#!z4RC3QzK!ZfX3xTFSRnl4QPMqRhT5ssbNRaZ-mhGvwoDUcjBr77c
CID O2___001 & O2___102
MID 0P6B10000
6.13.206.5
CID HTC__001, HTC__J15, HTC__E11, HTC__203, HTC__102, HTC__405, HTC__Y13, HTC__A07, HTC__304, HTC__032, HTC__016, HTC__M27, HTC__K18, HTC__002, HTC__A48
MID 0P6B10000
6.12.401.4
6.12.401.4 - thanks @t-ryder
CID HTC__001 & HTC__J15
MID 0P6B67000
6.21.401.1
CID T-MOB010
MID 0P6B13000
6.20.531.5
CID HTC__332
MID 0P6B16000
6.14.599.1
CID HTC__332
MID 0P6B16000
6.17.600.3
CID ROGER001
MID 0P6B16000
6.13.631.7
CID TELUS001
MID 0P6B16000
6.13.661.9
6.13.661.9 - thanks @shaboobla
CID BM___001 & SASKT001
MID 0P6B16000
6.13.666.7
CID HTC__044 & HTC__059
MID 0P6B11000
6.14.707.1
6.14.707.1 - thanks @Bobbi lim and @huyhoangytn
CID HTC__622
MID 0P6B63000
6.16.708.1
CID HTC__621
MID 0P6B11000
6.12.709.4
6.20.709.2
CID HTC__039 & VODAP021
MID 0P6B11000
6.12.710.4
6.24.710.1
CID HTC__038
MID 0P6B65000
6.15.720.2
CID H3G__001, H3G__106, H3G__402, H3G__G04
MID 0P6B10000
6.13.771.4
CID TELST001
MID 0P6B11000
6.12.841.4
6.24.841.1
CID OPTUS001
MID 0P6B65000
6.12.980.5
6.24.980.1
CID HTC__247
MID 0P6B10000
6.13.1020.4
CID GLOBA001
MID 0P6B13000
6.13.1500.7
CID BS_US001 & BS_US002
MID 0P6B12000 & 0P6B13000
6.12.1540.4
Google Play Edition (GPE)
CID GOOGL001, 11111111, CWS__001, T-MOB010
MID 0P6B10000, 0P6B11000, 0P6B12000, 0P6B13000, 0P6B11000, 0P6B15000, 0P6B16000, 0P6B17000
Thanks @[B]Petert87[/B] for his collections -
https://forum.xda-developers.com/showpost.php?p=70965379&postcount=2198
https://forum.xda-developers.com/showpost.php?p=70978970&postcount=2202
M8 Dual-SIM only
CID HTC__001, HTC__A07, HTC__J15, HTC__A48, HTC__Y13, HTC__032 & HTC__102
MID 0P6B64000
6.16.401.101 - thanks liviumustata
M8 EYE only
CID HTC__001 & HTC__J15
MID 0P6B81000
5.07.401.1 - thanks @[B]sunny6478[/B]
My Stock Recovery Collections
1.xx.xxx.x
1.54.69.5 - not available, use 1.70.69.2
1.70.69.2
1.54.73.5
1.70.73.2
1.54.75.5 - not available, use 2.26.75.1
1.57.111.2
1.57.118.2
1.12.161.17 - thanks @Petert87
1.54.161.5 - thanks @Petert87
1.54.161.10
1.54.161.10 - thanks @Petert87
1.54.206.10
1.54.401.10
1.58.502.1
1.57.599.1 - not available, use 2.25.599.1
1.12.600.20 - not available, use 4.32.600.2
1.55.666.4
1.54.707.7
1.60.708.2
1.54.709.12
1.56.720.6
1.54.771.9
1.54.841.8
1.54.980.5
1.55.1500.4
2.xx.xxx.x
2.26.61.1 - not available, use 3.33.61.9
2.26.69.1
2.26.75.1
2.23.112.3
2.23.118.3
2.22.161.6
2.22.161.6 - thanks @Petert87
2.22.206.6
2.22.401.4
2.22.401.5
2.23.502.3 - not available, use 3.42.502.1
2.25.599.1
2.23.631.2
2.23.666.2
2.22.707.4
2.11.708.1
2.11.708.2
2.22.709.3
2.22.709.4
2.23.710.1
2.22.771.5
2.23.841.1
2.22.901.5
2.07.980.2
2.23.1500.2
2.22.1540.3
2.22.1540.4
3.xx.xxx.x
3.33.61.9
3.33.69.1
3.33.75.1
3.29.112.9
3.29.114.9 - not available, use 4.19.114.2
3.29.118.9
3.29.161.5 - thanks @Petert87
3.29.161.9 - thanks @Petert87
3.32.206.9
3.28.401.6
3.28.401.7
3.28.401.9
3.42.502.1
3.36.599.2
3.34.631.4
3.34.661.4
3.34.666.4
3.32.707.9
3.32.708.4
3.28.709.5
3.28.709.6
3.32.710.9
3.35.720.1
3.32.771.10
3.32.841.9
3.31.901.9
3.32.980.4
3.34.1500.4
3.28.1540.5
4.xx.xxx.x
4.19.61.2
4.19.61.3
4.19.69.3
4.19.69.4
4.19.75.2
4.19.75.3
4.19.111.2
4.19.111.3
4.19.111.4
4.19.112.2
4.19.112.3
4.19.112.4
4.19.114.2
4.19.114.3
4.19.114.4
4.19.118.2
4.19.118.3
4.19.118.4
4.19.161.2
4.19.161.2 - thanks @Petert87
4.19.161.3
4.19.161.3 - thanks @Petert87
4.19.161.4 - thanks @Petert87
4.19.163.3
4.19.166.2
4.19.166.3
4.20.206.1
4.20.206.2
4.16.401.10
4.16.401.13
4.28.502.1
4.28.502.2
4.20.531.5
4.32.598.1
4.20.599.3
4.20.599.4
4.32.600.2
4.20.631.2
4.20.631.3
4.20.661.2
4.20.661.3
4.20.666.1
4.20.666.2
4.19.707.2
4.19.707.4
4.18.708.12
4.16.709.9
4.24.709.2
4.24.709.3
4.20.710.5
4.20.710.7
4.20.710.9
4.18.720.8
4.18.720.10
4.20.771.2
4.25.771.6
4.19.841.5
4.19.841.7
4.19.841.9
4.20.901.3
4.20.901.4
4.18.980.9
4.18.980.11
4.21.1020.1
4.21.1020.2
4.20.1500.1
4.20.1500.2
4.16.1540.8
4.17.1540.9
6.xx.xxx.x
6.12.61.4
6.14.69.4
6.14.75.4
6.12.111.4
6.12.112.4
6.12.114.4
6.12.118.4
6.12.161.4
6.12.163.4
6.12.166.4
6.13.206.5
6.12.401.4
6.21.401.1
6.20.502.5
6.20.531.5
6.14.599.1
6.17.600.3
6.13.631.7
6.13.661.9
6.13.666.7
6.14.707.1
6.16.708.1
6.12.709.4
6.20.709.2
6.12.710.4
6.24.710.1
6.15.720.2
6.13.771.4
6.12.841.4
6.24.841.1
6.12.980.5
6.24.980.1
6.13.1020.4
6.13.1500.7
6.12.1540.4
M8 Dual-SIM only
3.33.401.6
4.30.401.15
4.30.401.16
4.30.401.18
6.16.401.101
M8 EYE only
1.82.401.7 - thanks to @Hazem99922
4.30.720.4
4.30.720.5
Google Play Edition (GPE)
Thanks @[B]Petert87[/B] for his collections
1.16.1700.16
2.10.1700.4
2.12.1700.1
3.11.1700.5
4.04.1700.4
4.04.1700.5
4.04.1700.6
4.04.1700.9
4.04.1700.10
5.07.1700.6
5.07.1700.8
5.07.1700.9
For those who need the signed firmware, below are the Marshmallow firmware that I have :
Important : If you're flashing this Marshmallow firmware on top of a lollipop and there are two Marshmallow versions,
install the first version then follow by the second version.
Don't install directly the second version as it is only partial firmware (except fw_6.20.709.2);
without the first version is installed prior to the second version your device firmware won't be correctly updated
CID ORANG001
MID 0P6B10000
fw_6.12.61.4
CID ORANGB10
MID 0P6B10000
fw_6.14.69.4
CID ORANG309
MID 0P6B10000
fw_6.14.75.4
CID T-MOB101
MID 0P6B10000
fw_6.12.111.4
CID T-MOB102
MID 0P6B10000
fw_6.12.112.4
CID T-MOB003
MID 0P6B10000
fw_6.12.114.4
CID T-MOB009
MID 0P6B10000
fw_6.12.118.4
CID VODAP001, VODAP102, VODAPE17, VODAP405, VODAP304, VODAPD18
MID 0P6B10000
fw_6.12.161.4
CID VODAP203
MID 0P6B10000
fw_6.12.163.4
CID VODAP110 & VODAP120
MID 0P6B10000
fw_6.12.166.4
CID O2___001 & O2___102
MID 0P6B10000
fw_6.13.206.5
CID HTC__001, HTC__J15, HTC__E11, HTC__203, HTC__102, HTC__405, HTC__Y13, HTC__A07, HTC__304, HTC__032, HTC__016, HTC__M27, HTC__K18, HTC__002, HTC__A48
MID 0P6B10000
fw_6.12.401.4
CID HTC__001 & HTC__J15
MID 0P6B67000
fw_6.21.401.1 - thanks @umesh.lk
CID CWS__001
MID 0P6B12000
fw_6.20.502.5
CID T-MOB010
MID 0P6B13000
fw_6.20.531.5
CID HTC__332
MID 0P6B16000
fw_6.14.599.1
CID HTC__332
MID 0P6B16000
fw_6.17.600.3
CID ROGER001
MID 0P6B16000
fw_6.13.631.7
CID TELUS001
MID 0P6B16000
fw_6.13.661.9
CID BM___001 & SASKT001
MID 0P6B16000
fw_6.13.666.7
CID HTC__044 & HTC__059
MID 0P6B11000
fw_6.14.707.1
CID HTC__622
MID 0P6B63000
fw_6.16.708.1
CID HTC__621
MID 0P6B11000
fw_6.12.709.4
fw_6.20.709.2
CID HTC__039 & VODAP021
MID 0P6B11000
fw_6.12.710.4
fw_6.24.710.1 * install this firmware only after you have fw_6.12.710.4 already installed
CID HTC__038
MID 0P6B65000
fw_6.15.720.2
CID H3G__001, H3G__106, H3G__402, H3G__G04
MID 0P6B10000
fw_6.13.771.4
CID TELST001
MID 0P6B11000
fw_6.12.841.4
fw_6.24.841.1 * install this firmware only after you have fw_6.12.841.4 already installed
CID OPTUS001
MID 0P6B65000
fw_6.12.980.5
fw_6.24.980.1 * install this firmware only after you have fw_6.12.980.5 already installed
CID HTC__247
MID 0P6B10000
fw_6.13.1020.4
CID GLOBA001
MID 0P6B13000
fw_6.13.1500.7
CID BS_US001 & BS_US002
MID 0P6B12000 & 0P6B13000
fw_6.12.1540.4
How to install firmware :
1. You need the drivers : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. If the bootloader is UNLOCKED (for S-On device only), relock it with commands:
fastboot oem lock
fastboot reboot-bootloader
If the bootloader is LOCKED, skip the above.
3. Download the official signed fw_x.xx.xxx.x.zip
4. Put the device in bootloader/fastboot mode and connect to PC, run these commands
fastboot oem rebootRUU
fastboot flash zip fw_x.xx.xxx.x.zip
you'll see ERROR/FAILED, repeat
fastboot flash zip fw_x.xx.xxx.x.zip
fastboot reboot-bootloader
then you can proceed the next step that you need to do like installing a RUU
or fastboot reboot (to directly reboot device if you already have a working OS)
Note : unlocking bootloader will wipe your internal storage, copy your files like photos, music & etc to PC first
I would like to request a backup from 3.29.166.9 or 4.19.166.2
Thank you very much!
Thank you so much!
thank you for great work @ckpv5
i need a stock rom ( or ) stock back up for my HTC One M8 - Developer Edition .. CID is ( BS_US001 )
Thanks bro..nice job..
Thank you very much!!!
thanks for the great help! your the best! godbless!
I found a TWRP backup for 4.19.166.2
please add it to your list
https:// lsifiler.centersystems.com/filevista/public/1923/2015-05-04-01-23-12-lrx22c-release-keys.rar
Pagrio said:
I found a TWRP backup for 4.19.166.2
please add it to your list
https:// lsifiler.centersystems.com/filevista/public/1923/2015-05-04-01-23-12-lrx22c-release-keys.rar
Click to expand...
Click to collapse
Thanks for file.
I'll update the list after I redo the backup to remove root and add in the missing preload files.
EDIT : link updated
Questions on Stock Restore HTC M8
Friends,
It has been ages since I have flashed a new rom, performed a nanoandroid restore so will need a little
help.
Currently, my HTC M8 device is rooted with s-on. I am running the MIUI V5 rom since last August. Now, I would like to return back to stock and grab all the updates for the OTA etc. Right now, I am running twerp 2.7.0.2 on my phone.
T-Mobile USA
Status: S-ON/Unlocked
HBOOT 3.18.0.0000
RADIO: 1.19.213311491.03G
So here are my questions?
1. If I perform a nano-restore to stock does this mean that the root is lost? Not that it matters I can just re-root after the OTA etc..
2. Reading this thread honestly intimidated by all these versions to choose from for returning to stock. Not sure what to go by?
3. Last but not least, will this break my recovery mode when I perform the nanoandroid restore back to stock?
I don't mind paying a few dollars and having someone give me a hand with this that *knows* the art of flashing and not bricking.
My goal is go back to stock, updates with the OTA etc.. Re-root and try a rom like sky dragon, viper and see if I want to go into that direction.
Please advise and Thank You
tvos
tvos said:
Friends,
It has been ages since I have flashed a new rom, performed a nanoandroid restore so will need a little
help.
Currently, my HTC M8 device is rooted with s-on. I am running the MIUI V5 rom since last August. Now, I would like to return back to stock and grab all the updates for the OTA etc. Right now, I am running twerp 2.7.0.2 on my phone.
T-Mobile USA
Status: S-ON/Unlocked
HBOOT 3.18.0.0000
RADIO: 1.19.213311491.03G
So here are my questions?
1. If I perform a nano-restore to stock does this mean that the root is lost? Not that it matters I can just re-root after the OTA etc..
2. Reading this thread honestly intimidated by all these versions to choose from for returning to stock. Not sure what to go by?
3. Last but not least, will this break my recovery mode when I perform the nanoandroid restore back to stock?
I don't mind paying a few dollars and having someone give me a hand with this that *knows* the art of flashing and not bricking.
My goal is go back to stock, updates with the OTA etc.. Re-root and try a rom like sky dragon, viper and see if I want to go into that direction.
Please advise and Thank You
tvos
Click to expand...
Click to collapse
You have a T-MOB US device .. the best thread for all your needed files either stock backups and RUUs are here : http://forum.xda-developers.com/showthread.php?t=2714456
My advise is don't use that outdated TWRP 2.7.0.2 but use the updated ones like 2.8.3.0 and newer.
1. Basically - yes, you'll lose root when the nandroid backup is pure unrooted stock.
2. I don't list the backup for your version here - because the correct one for your device is there in link that I mentioned above.
3. TWRP Nandroid will not replace your current recovery. You need to manually flash the recovery image.
I don't mind to walk you through the process but unfortunately I don't have time at the moment as I'm busy with my vacation preparation.
For everyone - I will be away on holiday from 8/5 to 18/5 - so any request or question I will reply when I'm back from holiday.
Hello Ckpv5,
In response #2
2. I don't list the backup for your version here - because the correct one for your device is there in link that I mentioned above.
Not sure which one that I need for my device? Please let me know the name of the file or the link I should grab for this stock recovery. There are so many it's just confusting
Last but not least, can I flash the stock rom in TWRP or RUU?
Please advise
Dave
tvos said:
Not sure which one that I need for my device? Please let me know the name of the file or the link I should grab for this stock recovery. There are so many it's just confusting
Click to expand...
Click to collapse
You need to find the stock recovery that corresponds to the stock ROM for your CID.
tvos said:
Last but not least, can I flash the stock rom in TWRP or RUU?
Click to expand...
Click to collapse
The whole point of the instructions in the first post is to tell you how to restore the stock nandroid.
When a nandroid backup is restored, do I need to flash boot.img?
I'm refering to this post here http://forum.xda-developers.com/showpost.php?p=60937883&postcount=5509
"For stock stock stock all...
Flash stock nandroid backup
Flash boot img stock
Flash stock recovery
Re lock bootloader"
Thank you.
irawanjohan said:
When a nandroid backup is restored, do I need to flash boot.img?
I'm refering to this post here http://forum.xda-developers.com/showpost.php?p=60937883&postcount=5509
"For stock stock stock all...
Flash stock nandroid backup
Flash boot img stock
Flash stock recovery
Re lock bootloader"
Thank you.
Click to expand...
Click to collapse
When a nandroid backup is restored and boot is selected then there is no need to separately flash boot.img
Follow all steps in post #1 (see step #9 for your question)
and there is no need to relock bootloader
1.55.1500.4
Cookie_Fusion said:
1.55.1500.4
Click to expand...
Click to collapse
Link at post #2 for the TWRP Nandroid backup
Link at post #4 for the stock recovery image
So I just S-Off'd with Sunshine and when I type fastboot getvar all It is not giving me my CID/MID. fastboot oem readcid doesnt work either. I want to convert to the T-Mobile RUU but wanted to find out my CID and MID first beofre I go changing things. Any idea as to what I am doing wrong? Also to use the T-Mobile RUU and have it succeed I only need to change the CID to T- Mobile correct?
Vondis said:
So I just S-Off'd with Sunshine and when I type fastboot getvar all It is not giving me my CID/MID. fastboot oem readcid doesnt work either. I want to convert to the T-Mobile RUU but wanted to find out my CID and MID first beofre I go changing things. Any idea as to what I am doing wrong? Also to use the T-Mobile RUU and have it succeed I only need to change the CID to T- Mobile correct?
Click to expand...
Click to collapse
There aren't result because you need enter the command ( fastboot getvar all) in " Download Mode"
Mutasek24 said:
There aren't result because you need enter the command ( fastboot getvar all) in " Download Mode"
Click to expand...
Click to collapse
Thanks!! Slightly different than the M8 :laugh:
simple cid getter on google play i think im bit late for this post ehehehe
xstatik said:
simple cid getter on google play i think im bit late for this post ehehehe
Click to expand...
Click to collapse
Would anyone know why I would get a different CID from simple cid getter than the one that is displayed in download mode. I changed the cid to 11111111 and that is what is displayed in download mode now, but simple cid getter still shows VZW__001.
Presto2601 said:
Would anyone know why I would get a different CID from simple cid getter than the one that is displayed in download mode. I changed the cid to 11111111 and that is what is displayed in download mode now, but simple cid getter still shows VZW__001.
Click to expand...
Click to collapse
It's because there are two places the CID is stored, and cid getter is pulling it from the place that doesn't get changed by oem writecid. The version that shows in download mode is the one that matters.
Vondis said:
So I just S-Off'd with Sunshine and when I type fastboot getvar all It is not giving me my CID/MID. fastboot oem readcid doesnt work either. I want to convert to the T-Mobile RUU but wanted to find out my CID and MID first beofre I go changing things. Any idea as to what I am doing wrong? Also to use the T-Mobile RUU and have it succeed I only need to change the CID to T- Mobile correct?
Click to expand...
Click to collapse
same problem but i dont know how to fix my problem.
heres mine.
C:\fastboot_adb\fastboot_adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 357226062906524
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__J15
all:
finished. total time: 0.072s
C:\fastboot_adb\fastboot_adb>
I have Htc one m8 unlocked bootloader 3.19, was rooted but doesn't seem to be anymore. firmware is 4.16.401.10, supercid (was roger001). I'm not sure what I am doing wrong, I tried to flash a RUU after flashing the firmware first and i get an error 32-header error. Phone just reboots onto white HTC screen then gives me the red exclamation mark. Booting into recovery gives red exclamation mark. Not sure what else I can try, any suggestioins would be greatly appreciated. (note: tried to flash the RUU here I could be way off but I am stuck.)
Anyone have any assistance? I tried changed the mid so I could flash a RUU but still got the 32-header error. There has to be a simpler way to do this, I just want to get back to stock.
Are you s-on or s-off? Do adb getvar all and post the output (delete your IMEI and serial number, as these are personal data).
With the Rogers variant, you can't flash the Euro RUU unless you change the MID (s-off required).
Also, you need to relock the bootloader to run the RUU if you are s-on. But that doesn't matter as the RUU will fail MID check, anyway.
What exactly are you trying to accomplish by running the RUU?
redpoint73 said:
Are you s-on or s-off? Do adb getvar all and post the output (delete your IMEI and serial number, as these are personal data).
With the Rogers variant, you can't flash the Euro RUU unless you change the MID (s-off required).
Also, you need to relock the bootloader to run the RUU if you are s-on. But that doesn't matter as the RUU will fail MID check, anyway.
What exactly are you trying to accomplish by running the RUU?
Click to expand...
Click to collapse
Thanks, I am on S-off. I thought that if you are s-off you didn't need to change mid but clearly i am wrong. I am just trying to restore to stock, I screwed up the phone trying to flash a zip and my recovery didn't work. I'll post that info in one sec
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(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
redpoint73 said:
Are you s-on or s-off? Do adb getvar all and post the output (delete your IMEI and serial number, as these are personal data).
With the Rogers variant, you can't flash the Euro RUU unless you change the MID (s-off required).
Also, you need to relock the bootloader to run the RUU if you are s-on. But that doesn't matter as the RUU will fail MID check, anyway.
What exactly are you trying to accomplish by running the RUU?
Click to expand...
Click to collapse
Would flashing a recovery .img , for example >recovery_4.16.401.10.img< allow me to return to stock??
Kevinj17 said:
Thanks, I am on S-off. I thought that if you are s-off you didn't need to change mid but clearly i am wrong.
Click to expand...
Click to collapse
Yes, that is incorrect. CID and MID need to match what the RUU is looking for. SuperCID will pass the CID check. But the MID check will still fail if you try to run the Euro RUU (MID = 06PB10000) on a Rogers version M8 (MID = 06PB16000).
Also, are you actually using the phone on Rogers' network? If so, I do not think that returning to stock Euro WWE version by RUU is what you want. From this webpage, it looks like Rogers uses Bands 4,7, and 17 for LTE. The Euro RUU will install a full stock image, including radio firmware, and according to these specs, the Euro version (EMEA) is missing 2 of the 3 bands (Bands 4 and 17) needed for LTE to work on Rogers network.
Kevinj17 said:
I am just trying to restore to stock, I screwed up the phone trying to flash a zip and my recovery didn't work.
Click to expand...
Click to collapse
What zip did you try to flash exactly?
---------- Post added at 09:41 AM ---------- Previous post was at 09:23 AM ----------
Kevinj17 said:
Would flashing a recovery .img , for example >recovery_4.16.401.10.img< allow me to return to stock??
Click to expand...
Click to collapse
That would just be the actual stock recovery program that installs of OTA updates, etc.
Its not the actual stock OS or firmware, if that is what you are thinking.
The red exclamation indicates you are already on a stock recovery. Flashing this won't help you at all.
Yeah haha I figured that out right after posting. Thanks though. I re-flashed TWRP now and gonna try restoring from a nandrod backup i found then flash the matching firmware. see how that goes. The similiar names is what throws me off sometimes, so many different recoverys n sh*t lol
I was tryign to use a sixaxis controller to play games but kept getting and error about 'position executable variables' when loading the sixaxis app so i downloaded something called 'bypass pie' and flashed it. Clearly i should have backed up first. It was just inpatient, but it unrooted my phone and stuff so i tried to restore from a backuop like 2 weeks ago and it was corrupt so it messed things up
My HTC one m8 is S-OFF and it is SuperCID(11111111), I'm running the software 4.16.1540.8. I received a message to update my device and when try to do that, I get the message "We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone...". Is there a way I can update my phone ?
MotoXor said:
My HTC one m8 is S-OFF and it is SuperCID(11111111), I'm running the software 4.16.1540.8. I received a message to update my device and when try to do that, I get the message "We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone...". Is there a way I can update my phone ?
Click to expand...
Click to collapse
sorry cant help / suggest something that can help you as i am new also
MotoXor said:
My HTC one m8 is S-OFF and it is SuperCID(11111111), I'm running the software 4.16.1540.8. I received a message to update my device and when try to do that, I get the message "We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone...". Is there a way I can update my phone ?
Click to expand...
Click to collapse
Wrong MID
The same me
My phone S-ON, supercid 11111111,MID 0P6B1000, I installed ROM 4.19.707.2, now I can't update ota to 4.19.707.4, I don't know CID or MID is reason I can't ota update, I can't change CID or MID because my phone S-ON
ckpv5 said:
Wrong MID
Click to expand...
Click to collapse
What do you mean by MID ? Are you referring to the super CID ? Do you suggest another CID ?
MotoXor said:
What do you mean by MID ? Are you referring to the super CID ? Do you suggest another CID ?
Click to expand...
Click to collapse
CID and MID are two different things.
Your SuperCID is good for any version but MID must be correct.
For 4.16.1540.8, the correct MID 0P6B12000 or 0P6B13000 for OTA to work.
Your current one most probably not these MID.
Boot to bootloader and check your current MID. Run command fastboot getvar mid
---------- Post added at 09:46 PM ---------- Previous post was at 09:42 PM ----------
shotokan2011 said:
The same me
My phone S-ON, supercid 11111111,MID 0P6B1000, I installed ROM 4.19.707.2, now I can't update ota to 4.19.707.4, I don't know CID or MID is reason I can't ota update, I can't change CID or MID because my phone S-ON
Click to expand...
Click to collapse
Your MID is wrong for 4.19.707.2. The correct MID is 0P6B11000.
Your current MID 0P6B10000 is EU WWE version not Asia WWE.
How do you change to SuperCID ? It must have S-Off before.
Your current CID/MID combination is meant for EU WWE 4.16.401.10 then OTA to 4.16.401.13
Yes, I buy used phone that have supercid but S-ON, I flash RUU 4.19.707.2 to have Vietnamese language but can't update ota. So, can I reflash ROM 4.16.401.10 and update ota to 4.16.401.13 ? Thanks
ckpv5 said:
Your MID is wrong for 4.19.707.2. The correct MID is 0P6B11000.
Your current MID 0P6B10000 is EU WWE version not Asia WWE.
How do you change to SuperCID ? It must have S-Off before.
Your current CID/MID combination is meant for EU WWE 4.16.401.10 then OTA to 4.16.401.13
Click to expand...
Click to collapse
shotokan2011 said:
Yes, I buy used phone that have supercid but S-ON, I flash RUU 4.19.707.2 to have Vietnamese language but can't update ota. So, can I reflash ROM 4.16.401.10 and update ota to 4.16.401.13 ? Thanks
Click to expand...
Click to collapse
You flashed 4.19.707.2 RUU or you restored a backup ? AFAIK RUU 4.19.707.2 won't run your device.
If the 4.16.401.10 is non-rooted ROM, yes you can do OTA to 4.16.401.13.
Later if you want, you can restore a backup 4.19.707.4 (I don't remember 4.16.401.x has Vietnamese language or not). You should see 4.19.707.4 backup in my thread later tonight or tomorrow - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I flash RUU.exe 4.19.707.2 while old version is xx.401.xx, CID is 11111111, S-ON It's run good and I've used for 1 month Yesterday OTA have 4.19.707.4 I can't update, I think because my CID or MID number. This is my info about phone:
(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.19.707.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH52DWM01xxx
(bootloader) imei: 357336064xxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
ckpv5 said:
You flashed 4.19.707.2 RUU or you restored a backup ? AFAIK RUU 4.19.707.2 won't run your device.
If the 4.16.401.10 is non-rooted ROM, yes you can do OTA to 4.16.401.13.
Later if you want, you can restore a backup 4.19.707.4 (I don't remember 4.16.401.x has Vietnamese language or not). You should see 4.19.707.4 backup in my thread later tonight or tomorrow - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
ckpv5 said:
CID and MID are two different things.
Your SuperCID is good for any version but MID must be correct.
For 4.16.1540.8, the correct MID 0P6B12000 or 0P6B13000 for OTA to work.
Your current one most probably not these MID.
Boot to bootloader and check your current MID. Run command fastboot getvar mid
---------- Post added at 09:46 PM ---------- Previous post was at 09:42 PM ----------
You're right. My MID is 0P6B10000. How do I change it to 0P6B12000 ?
Click to expand...
Click to collapse
shotokan2011 said:
I flash RUU.exe 4.19.707.2 while old version is xx.401.xx, CID is 11111111, S-ON It's run good and I've used for 1 month Yesterday OTA have 4.19.707.4 I can't update, I think because my CID or MID number.
Click to expand...
Click to collapse
OK .. never see a successful run of Asia WWE RUU on a EU WWE MID before.
Anyway .. you just confirm the original is x.xx.401.x. So if you flash a x.xx.401.x then you can do OTA to x.xx.401.x with no problem as long as the ROM is not rooted.
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
MotoXor said:
You're right. My MID is 0P6B10000. How do I change it to 0P6B12000 ?
Click to expand...
Click to collapse
See this thread on how-to : http://forum.xda-developers.com/showthread.php?t=2708581
ckpv5 said:
OK .. never see a successful run of Asia WWE RUU on a EU WWE MID before.
Anyway .. you just confirm the original is x.xx.401.x. So if you flash a x.xx.401.x then you can do OTA to x.xx.401.x with no problem as long as the ROM is not rooted.
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
See this thread on how-to : http://forum.xda-developers.com/showthread.php?t=2708581
Click to expand...
Click to collapse
I can't seem to find the code to change the developer edition. All codes are listed but mine :crying:
MotoXor said:
I can't seem to find the code to change the developer edition. All codes are listed but mine :crying:
Click to expand...
Click to collapse
-AT&T, unlocked, developer MID:
ckpv5 said:
-AT&T, unlocked, developer MID:
Click to expand...
Click to collapse
Thank you so much, that might help. I'll try that once I finish my issue with the adb shell since it doesn't show my device.
MotoXor said:
Thank you so much, that might help. I'll try that once I finish my issue with the adb shell since it doesn't show my device.
Click to expand...
Click to collapse
It finally worked. I appreciate your help
Hi,
I tried reinstalling ROM 4.16.401.10 (RUU.EXE) but it was an "error 140 bootloader version". I tried to recovery using TWRP as your post is restored version 4.16.401.10 but the information in OS bootloader is 4.19.707.2 and I still can not update via OTA, I restored by 4:19 .707.4 is ok but information in bootloader OS still 4.19.707.2. I do not understand why my current phone S-ON, supercid 11111111, MID 0P6B1000 can not install ROM RUU.EXE 401 , you can help me? I think that by version HBoot 319 is high? Can I fix this problem without S-OFF to downgrade HBboot, change CID,change MID?
ckpv5 said:
You flashed 4.19.707.2 RUU or you restored a backup ? AFAIK RUU 4.19.707.2 won't run your device.
If the 4.16.401.10 is non-rooted ROM, yes you can do OTA to 4.16.401.13.
Later if you want, you can restore a backup 4.19.707.4 (I don't remember 4.16.401.x has Vietnamese language or not). You should see 4.19.707.4 backup in my thread later tonight or tomorrow - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
shotokan2011 said:
Hi,
I tried reinstalling ROM 4.16.401.10 (RUU.EXE) but it was an "error 140 bootloader version". I tried to recovery using TWRP as your post is restored version 4.16.401.10 but the information in OS bootloader is 4.19.707.2 and I still can not update via OTA, I restored by 4:19 .707.4 is ok but information in bootloader OS still 4.19.707.2. I do not understand why my current phone S-ON, supercid 11111111, MID 0P6B1000 can not install ROM RUU.EXE 401 , you can help me? I think that by version HBoot 319 is high? Can I fix this problem without S-OFF to downgrade HBboot, change CID,change MID?
Click to expand...
Click to collapse
Can you post your fastboot getvar all result (minus serial & imei no) ? I don't see in any of your previous post. Then we'll see what we can do.
Hi, This my phone information:
(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.19.707.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH52DWMxxxx
(bootloader) imei: 3573360644xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.008s
ckpv5 said:
Can you post your fastboot getvar all result (minus serial & imei no) ? I don't see in any of your previous post. Then we'll see what we can do.
Click to expand...
Click to collapse
I'm scare nothing much can be done without S-Off. Seems like you have the Asian WEE bootloader with wrong MID and that's why the 4.16.401.10 RUU failed to run
Have you try to run the SunShine apk and see whether it asks for payment ? If the previous owner use SunShine to S-Off, no payment is required for the second time.
(you need a rooted stock ROM for that)
You can't downgrade hboot without S-Off.
I still feel strange that you managed to run 4.19.707.2 RUU on a x.xx.401.x before.
Okay, I'll try to Re S-OFF because I've buy an old devide
ckpv5 said:
I'm scare nothing much can be done without S-Off. Seems like you have the Asian WEE bootloader with wrong MID and that's why the 4.16.401.10 RUU failed to run
Have you try to run the SunShine apk and see whether it asks for payment ? If the previous owner use SunShine to S-Off, no payment is required for the second time.
(you need a rooted stock ROM for that)
You can't downgrade hboot without S-Off.
I still feel strange that you managed to run 4.19.707.2 RUU on a x.xx.401.x before.
Click to expand...
Click to collapse