[STOCK] Guides and Stock Backups/Recovery/OTA/RUU - HTC 10 Guides, News, & Discussion

HTC 10
Stock Collection​Hi, I'm creating this thread for people to find all possible files from official HTC.
People can also post backups from your own device here, so people can find files they want easily.
I'll start with me
Latest Update (August 23): 1.9X.XXX.X (TWRP & OTA & RUU)​
TWRP Backup (Untouched System Image + Boot)
CID: HTC__001/HTC__034/HTC__A07/HTC__J15/HTC__M27/HTC__016/HTC__002 | MID: 2PS620000
1.80.401.3 (by @baadnewz)
1.80.401.3 (by @baadnewz)
1.80.401.1 (by @baadnewz)
1.30.401.1 (by @LeeDroid)
CID: HTC__621 | MID: 2PS620000
1.92.709.1 (by @topjohnwu)
1.80.709.1 (by @topjohnwu)
1.55.709.5 (by @topjohnwu)
1.30.709.1 (by @topjohnwu)
1.21.709.2 (by @topjohnwu)
CID: HTC__039/OPTUS001/VODAP021/TELNZ001 | MID: 2PS620000
1.21.710.10 (by @TRLOS)
CID: EVE__001 | MID: 2PS620000
1.21.91.4 (by @squ89r97)
CID: O2___102 | MID: 2PS620000
1.21.206.5 (by @HTCnerdYoda)
CID: BS_US001/BS_US002 | MID: 2PS650000
1.80.617.1 (by @baadnewz)
1.53.617.5 (by @Captain_Throwback)
1.21.617.3 (by @george241312)
CID: T-MOB010 | MID: 2PS650000
1.21.531.1 (by @pbaldw10)
CID: HTC__332 | MID: 2PS650000
1.02.600.3 (by @Sleep-_-23)
Stock Recovery
CID: HTC__001/HTC__034/HTC__A07/HTC__J15/HTC__M27/HTC__016/HTC__002 | MID: 2PS620000
1.30.401.1
CID: HTC__621 | MID: 2PS620000
1.92.709.1
1.80.709.1
1.55.709.5
1.30.709.1
CID: HTC__039/OPTUS001/VODAP021/TELNZ001 | MID: 2PS620000
1.21.710.10 (by @TRLOS)
CID: O2___102 | MID: 2PS620000
1.21.206.5 (by @0xLeon)
CID: BS_US001/BS_US002 | MID: 2PS650000
1.53.617.5
1.21.617.3 (by @Ratief)
OTA
CID: HTC__001/HTC__034/HTC__A07/HTC__J15/HTC__M27/HTC__016/HTC__002 | MID: 2PS620000
1.80.401.3 -> 1.90.401.5 (by @Captain_Throwback)
1.80.401.1 -> 1.80.401.3 (by @baadnewz)
1.30.401.1 -> 1.80.401.1 (by @Hawk19)
1.21.401.4 -> 1.30.401.1 (by @Captain_Throwback)
CID: HTC__621 | MID: 2PS620000
2.41.709.3 -> 2.41.709.7 (by @topjohnwu)
1.98.709.5 -> 2.41.709.3 (by @topjohnwu)
1.92.709.1 -> 1.98.709.5 (by @topjohnwu)
1.96.709.5 -> 1.98.709.5 (by @topjohnwu)
1.80.709.1 -> 1.92.709.1 (by @topjohnwu)
1.55.709.5 -> 1.80.709.1 (by @topjohnwu)
1.30.709.1 -> 1.55.709.5 (by @topjohnwu)
1.21.709.2 -> 1.30.709.1 (by @topjohnwu)
CID: HTC__039/OPTUS001/VODAP021/TELNZ001 | MID: 2PS620000
1.53.710.6 -> 1.80.710.1 (by @morgy59)
1.21.710.10 -> 1.53.710.6 (by @morgy59)
CID: TELST001 | MID: 2PS620000
1.21.841.8 -> 1.53.841.6
CID: T-MOB101 | MID: 2PS620000
1.21.111.4 -> 1.53.111.7 (by @amq)
CID: BS_US001/BS_US002 | MID: 2PS650000
1.80.617.1 -> 1.91.617.1 (by @Captain_Throwback)
1.53.617.5 -> 1.80.617.1 (by @Captain_Throwback)
1.21.617.3 -> 1.53.617.5 (by @Captain_Throwback)
CID: HTC__332 | MID: 2PS650000
1.02.600.3 -> 1.53.600.31 (by @alexalanis)
RUU Zip (Stock Signed)
CID: HTC__001/HTC__034/HTC__A07/HTC__J15/HTC__M27/HTC__016/HTC__002 | MID: 2PS620000
1.90.401.5 (by @djluisbento)
1.80.401.1 (by @djluisbento)
1.30.401.1 (by @Mux89)
1.21.401.4
Stock RUU EXE
CID: BS_US001/BS_US002 | MID: 2PS650000
1.80.617.1
1.53.617.5
XDA:DevDB Information
Stock Collection, ROM for the HTC 10
Contributors
topjohnwu
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Stable
Created 2016-04-15
Last Updated 2017-02-02

How to Create My Own System Backup​If you cannot find a system dump of your current system, and fortunately you've not done any modifications to your system, we need your contribution!
Flash TWRP in download mode
Boot into TWRP, then choose "Mount system as read-only" when it asks you. This is important!!
Backup your device choosing "System Image" (not "System") and "Boot".
Copy the files to your PC, zip them into file and upload to a hosting site I can easily download.
I'll re-host your uploaded files to my personal AFH account, so you don't have to keep the files online forever if your storage is limited.
How to Get The OTA Link From HTC​Some time ago, HTC changed the place where the OTA files are stored. It used to be stored in internal storage.
The OTA zip will now be downloaded to the following directory:
Code:
/data/data/com.htc.updater/files
This directory is protected and cannot be accessed without root permission.
So here are two methods you can use to get the OTA link directly from HTC servers.
Please share the links in this thread so people unable to get OTAs can download them and apply them manually.
Method 1: Use Network Monitoring Applications
Requirements: You are able get the update notification; you can download the OTA on your phone.
Won't work: Unfortunate devices stuck with the situation stated here.
By monitoring all network traffic on the device, it is obvious that you can get the OTA links, because your phone is also downloading from the link.
Here I use a paid app called "Charles Web Debugging Proxy" for example. The trial mode can have the job done with no issues.
Download the app to your computer from the official site. It supports all platforms.
Open the app and let it initialize the network settings.
Go back to the phone, connect to the same network as your computer. Open Wi-Fi settings, long press your current connection, select "Edit connection".
Scroll to the bottom, enable proxy. Enter your computer's local network IP for server (search the web for guides to find the IP), and insert "8888" in port, then press save.
On your computer, Charles should detect that your phone is trying to connect the computer. Accept it and you should see all network traffic from your phone.
Back to the phone, go to settings and check for system updates and download the update
You should see some addresses related to HTC/OTA inside Charles, test the links and try if you can download the OTA zip file.
Method 2: Use Logcat And Guess the Download Link
This will work on all devices, include those who cannot even receive OTA discussed here.
Remember to enable "USB Debugging" on your phone
Connect your phone to your computer.
Type following commands, but don't press enter yet
Code:
adb logcat > log.txt // This will store logs in a file called log.txt
Go to settings on your phone, press enter on computer to start logging your device right before you tap on the "Check for updates" on your phone (this is for reducing the length of the logs)
After it notifies there is an update available, or saying that your system is corrupt, press "Ctrl + C" to stop logging.
View the logs, you should find something similar to this:
Code:
11353 11803 D UpdaterAPK | UpdaterNetworkCheck: isIPTOn() IPTInfo is null
1600 1600 D htcCheckinService: onStartCommand()
1600 1600 D htcCheckinService: onStartCommand() the action name = com.htc.checkin.HTC_CHECKIN
1600 1600 W Settings: Setting device_provisioned has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
1600 1600 D htcCheckinService: Roaming is :false
1600 1600 I htcCheckinService: == Checkin triggered == A8.0(M)
11353 11536 V UpdaterAPK | DownloadProvider: starting query, database is not null; projection[0] is _id; projection[1] is entity; projection[2] is status; projection[3] is _data; projection[4] is lastmod; selection is hint=?; selectionArgs[0] is OTA_PERFUME_UHL_M60_SENSE80GP_hTC_Asia_TW_1.30.709.1_R-1.21.709.2_R2_release_477314i6fyk64xlvy886ba.zip; sort is null.
11353 11536 V UpdaterAPK | DownloadProvider: created cursor [email protected] on behalf of 1600
1600 11804 D PMS : acquireWL(6ee6ed9): PARTIAL_WAKE_LOCK htcCheckinService_300 0x1 1600 1000 null
2827 2827 D HtcTelephonyInternal: CMD_GET_ALL_DEVICE_ID_INFO
1600 11804 W htcCheckinService.CheckinProtocol: the build rom task id = 475995
For the example above, you can found out that the expected OTA update zip filename is
Code:
OTA_PERFUME_UHL_M60_SENSE80GP_hTC_Asia_TW_1.30.709.1_R-1.21.709.2_R2_release_477314i6fyk64xlvy886ba.zip
Finally, put the file name after the following web address:
Code:
http://fotadl-az.htc.com/secure/
With the example, the final result is
Code:
http://fotadl-az.htc.com/secure/OTA_PERFUME_UHL_M60_SENSE80GP_hTC_Asia_TW_1.30.709.1_R-1.21.709.2_R2_release_477314i6fyk64xlvy886ba.zip
(Note: I'm not sure if every OTA files follows the same rules, this is why I said this is "guessing" the download link)

How to Use The TWRP Backups​The zip file you download has the following structure:
Code:
A.BB.CCC.D.zip
|--boot.emmc.win
|--system_image.emmc.win
|--recovery.log
Every device has an TWRP directory in your internal/external storage with the following structure:
Code:
Storage Root
|--BACKUPS
|--(Your Device ID)
|--(Backup Name, any name is OK)
|--boot.emmc.win
|--system_image.emmc.win
|--recovery.log
If you don't have a similar folder structure, backup a small file in TWRP (eg. boot), TWRP will create the structure for you.
After extracting the TWRP backup downloaded above, remember to put the files into a correct place so TWRP can detect the backup files.
How to Manually apply OTA Updates​Before we get started, note that in order to install OTA, you are required to have
100% unmodified system (can be restored from TWRP backup provided in OP)
Stock recovery (can download from OP)
It is not required to have the exact matching recovery to manually apply OTAs, recoveries that aren't too many versions away should function the same, and thus accept OTA flashings
Place your OTA file to external sdcard, and reboot to stock recovery (if you don't have SD Card use adb sideload instead, search the web for simple instructions):
Code:
adb reboot recovery
After booting to the recovery, you'll see a large exclamation mark on the screen.
Press the power button, then short press volume up + volume down to activate the HTC recovery menu.
Use your volume keys to navigate through items. Navigate to "Apply update from SD card", and press power button to select.
Navigate to your file and press power button to apply
The recovery will now install the OTA.
After reboot, the recovery should automatically install the firmware for you.
How to Get The Firmware For a Particular Version​Download the OTA zip of the version you're interested in. Inside the zip, it will contain a zip called "firmware.zip".
This zip contains a portion of the firmware, you can flash it by rebooting into download mode and use this command:
Code:
fastboot flash zip (path to zip)

I see you said that HTC does not support fastboot. How did you install twrp? Also we found on the Nexus 6P that fastboot was having issues and a newer version was found and worked. Have a look in this thread: [GUIDE] Unlock/Root/Flash for Nexus 6P should be newer versions of fastboot that work with Android 6.

Stephen said:
I see you said that HTC does not support fastboot. How did you install twrp?
Click to expand...
Click to collapse
I believe he said unable to fastboot boot twrp in order to backup the stock recovery and fastboot flash twrp is not a problem.
@topjohnwu thanks for your contribution

Stephen said:
I see you said that HTC does not support fastboot. How did you install twrp? Also we found on the Nexus 6P that fastboot was having issues and a newer version was found and worked. Have a look in this thread: [GUIDE] Unlock/Root/Flash for Nexus 6P should be newer versions of fastboot that work with Android 6.
Click to expand...
Click to collapse
ckpv5 said:
I believe he said unable to fastboot boot twrp in order to backup the stock recovery and fastboot flash twrp is not a problem.
@topjohnwu thanks for your contribution
Click to expand...
Click to collapse
What I mean is the 10 cannot use the fastboot boot XXX.img function, the image was sent successfully but it is stuck at the cmd line showing "booting". I had to flash the TWRP directly to recovery in order to make it boot up.
And about the fastboot version, I always keep two versions of fastboot in my computer, one is directly from Android Studio (which will automatically update to the latest version), and another is from HTC Dev website. It seems that several HTC specific commands on newer HTC devices requires the HTC Dev fastboot to work. Just keep this in mind.

Ah ok, I had read it that you could not get fastboot to communicate to the device at all! Odd that the command did not work to allow temp boot. Could possibly be a bug in TWRP.

Stephen said:
Ah ok, I had read it that you could not get fastboot to communicate to the device at all! Odd that the command did not work to allow temp boot. Could possibly be a bug in TWRP.
Click to expand...
Click to collapse
Nothing to do with TWRP. HTC disabled fastboot boot on the A9 as well. It doesn't even work with the stock recovery.

Captain_Throwback said:
Nothing to do with TWRP. HTC disabled fastboot boot on the A9 as well. It doesn't even work with the stock recovery.
Click to expand...
Click to collapse
Thats good to know thanks! Last HTC I had was the m8, It is a shame they have disabled that feature, it was very useful.

topjohnwu said:
System Backup (TWRP with Untouched System Image)
CID: HTC__621
1.21.709.2
Click to expand...
Click to collapse
Is this the unlocked version or a region specific one? On old HTC phones, I thought the unlocked version was .401???
There has been talk of 1.21.x, 1.22.x to 1.24.x having been pushed as well. Any chance to check for updates or is that off table now that twrp has been installed?

rav101 said:
Is this the unlocked version or a region specific one? On old HTC phones, I thought the unlocked version was .401???
Click to expand...
Click to collapse
.401 htc Europe unlocked version
.709 htc Asia - Taiwan unlocked version

ckpv5 said:
.401 htc Europe unlocked version
.709 htc Asia - Taiwan unlocked version
Click to expand...
Click to collapse
Thanks for the info.

rav101 said:
Is this the unlocked version or a region specific one? On old HTC phones, I thought the unlocked version was .401???
There has been talk of 1.21.x, 1.22.x to 1.24.x having been pushed as well. Any chance to check for updates or is that off table now that twrp has been installed?
Click to expand...
Click to collapse
I will update this post as soon as I receive an update, since I do serious backups for my phone before messing around. And as long as I still have my 10 (which will likely be two years), I will keep maintaining this thread. I hope people can help adding content to this thread by sharing their own backups, so users may find a way back to stock for OTAs.
The Taiwanese carriers are following the international standards, and there are no sim lock / region lock / bootloader lock BS (like China and US), so consider this version nearly the same as an international one.

topjohnwu said:
I will update this post as soon as I receive an update, since I do serious backups for my phone before messing around. And as long as I still have my 10 (which will likely be two years), I will keep maintaining this thread. I hope people can help adding content to this thread by sharing their own backups, so users may find a way back to stock for OTAs.
The Taiwanese carriers are following the international standards, and there are no sim lock / region lock / bootloader lock BS (like China and US), so consider this version nearly the same as an international one.
Click to expand...
Click to collapse
That's confirmed by the Model ID (2PS620000) and device ID (pmeuhl) being the same as the Europe/Int'l variant. It seems that there will be only 3 total variants of the 10 (at least the one with the S820) once they're all released.

Much appreciated buddy, and I will be up for providing back ups. Though with the European unlocked version, I dont think there will be any shortage of backups for that model...

@topjohnwu
Could you possibly to test this HTC 10 Deodexed Rom on your device ?
1.21.709.2 Base
Used sparse_dat perm type for more efficient space usage
Unpacked boot.img and repacked keeping ramdisk
Added init.d support
Added insecure boot
Disabled dm-verity and forceencrypt
Debloated
Deodexed with oat2dex method
Zipaligned all apk and framework apk files
hc10_deodexed_marshmallow.zip
MD5: 4653b96454365206111760d4f641e81c

coolberry said:
@topjohnwu
Could you possibly to test this HTC 10 Deodexed Rom on your device ?
1.21.709.2 Base
Used sparse_dat perm type for more efficient space usage
Unpacked boot.img and repacked keeping ramdisk
Added init.d support
Added insecure boot
Disabled dm-verity and forceencrypt
Debloated
Deodexed with oat2dex method
Zipaligned all apk and framework apk files
hc10_deodexed_marshmallow.zip
MD5: 4653b96454365206111760d4f641e81c
Click to expand...
Click to collapse
If you built this ROM with @SuperR.'s Kitchen, be aware that on the A9, sparse_dat ROMs wouldn't flash at all - they would just get stuck. Set_metadata had to be used to produce a working ROM. Also, I'm assuming you removed the device assert too? Because the current available version of TWRP doesn't have the proper device name in there. I'll be updating it today, most likely.

Captain_Throwback said:
If you built this ROM with @SuperR.'s Kitchen, be aware that on the A9, sparse_dat ROMs wouldn't flash at all - they would just get stuck. Set_metadata had to be used to produce a working ROM. Also, I'm assuming you removed the device assert too? Because the current available version of TWRP doesn't have the proper device name in there. I'll be updating it today, most likely.
Click to expand...
Click to collapse
Kitchen showed device assert as " htc_pmeuhl " and I corrected it as " htc_pmeuhl,htc_pmeul "

coolberry said:
Kitchen showed device assert as " htc_pmeuhl " and I corrected it as " htc_pmeuhl,htc_pmeul "
Click to expand...
Click to collapse
There is no htc_pmeul, and like I said, those asserts won't work at all with the currently released TWRP. I am in the process of updating it now.

coolberry said:
Kitchen showed device assert as " htc_pmeuhl " and I corrected it as " htc_pmeuhl,htc_pmeul "
Click to expand...
Click to collapse
Posted an updated TWRP in the TWRP thread: http://forum.xda-developers.com/htc...ery-twrp-touch-recovery-t3358139/post66393936
@topjohnwu you should update to this version for the device asserts to be correct .

Related

[Q] Stock Nandroid Backup Help

Hi I have an HTC One M8 from Canada locked to Wind Mobile and I am having trouble finding a stock backup and stock rom for it online. If anyone can help or refer me to somewhere that would be appreciated.
Which software version ? Post your fastboot getvar all (minus serial no. & imei no.)
I may have them.
ckpv5 said:
Which software version ? Post your fastboot getvar all (minus serial no. & imei no.)
I may have them.
Click to expand...
Click to collapse
This is a screen shot of the info:
*removed the link*
AbdulJohn said:
This is a screen shot of the info:
Click to expand...
Click to collapse
Remove that screenshot as it has your Serial no. & Imei no.
One info is missing .. just write here the hboot no.; is it 3.16.00000 or 3.18.0000 ?
ckpv5 said:
Remove that screenshot as it has your Serial no. & Imei no.
One info is missing .. just write here the hboot no.; is it 3.16.00000 or 3.18.0000 ?
Click to expand...
Click to collapse
It is 3.16.0.0000
1.55.1500.4
CID GLOBA001
MID 0P6B13000
1. Install TWRP 2.8.1.0 - http://techerrata.com/browse/twrp2/m8
command fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
2. Download TWRP backup 1.55.1500.4 - https://mega.co.nz/#!n8AAQYbK!_N-Y8HYXnCzQjqrEOmqvLKJK9qnYZ83W2yjwQA0IZXg
3. Download stock 1.55.1500.4 recovery - http://sourceforge.net/projects/htconem8/files/Recovery/1.55.1500.4_recovery.img/download
4. Extract the downloaded 1.55.1500.4_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. Reboot, connect device to PC then open Internal Storage, TWRP/BACKUPS/SerialNo./
7. Transfer the extracted 1.55.1500.4 folder (not 1.55.1500.4_ckpv5 folder) and its content to the backup path on your device
TWRP/BACKUPS/SerialNo./1.55.1500.4
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
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery 1.55.1500.4_recovery.img
12. reboot - check for OTA, download, install
13. repeat step 12 until the last OTA 4.20.1500.1
14. done
If you want to flash TWRP again, use the latest TWRP 2.8.5.0 after last OTA 4.20.1500.1
ckpv5 said:
1. Install TWRP 2.8.1.0 -
command fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
2. Download TWRP backup 1.55.1500.4 -
3. Download stock 1.55.1500.4 recovery -
4. Extract the downloaded 1.55.1500.4_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. Reboot, connect device to PC then open Internal Storage, TWRP/BACKUPS/SerialNo./
7. Transfer the extracted 1.55.1500.4 folder (not 1.55.1500.4_ckpv5 folder) and its content to the backup path on your device
TWRP/BACKUPS/SerialNo./1.55.1500.4
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
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery 1.55.1500.4_recovery.img
12. reboot - check for OTA, download, install
13. repeat step 12 until the last OTA 4.20.1500.1
14. done
If you want to flash TWRP again, use the latest TWRP 2.8.5.0 after last OTA 4.20.1500.1
Click to expand...
Click to collapse
Thanks!!
AbdulJohn said:
Thanks!!
Click to expand...
Click to collapse
No problem ...
After restore, do OTA
1.55.1500.4 --> 2.23.1500.2 --> 3.34.1500.4 --> 4.20.1500.1
I know this thread is almost a month old, but I figured I'd post here since I found it through Google.
I have the same story as AbdulJohn (Canadian WIND htc One with no stock backup) and I was wondering if anybody could help.
My software version is 3.34.1500.4
superspence said:
I know this thread is almost a month old, but I figured I'd post here since I found it through Google.
I have the same story as AbdulJohn (Canadian WIND htc One with no stock backup) and I was wondering if anybody could help.
My software version is 3.34.1500.4
Click to expand...
Click to collapse
Here is the stock backup : https://mega.co.nz/#!RAAnUBzJ!ajF8_nfr8LGdE7WCo5ugiLjyWk_264-ctSGOYjczSWs
Here is the stock recovery : http://sourceforge.net/projects/htconem8/files/Recovery/3.34.1500.4_recovery.img/download
Thank you so very much!!
No problem
ckpv5 said:
No problem
Click to expand...
Click to collapse
Hey would you be able to direct me also?
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.16.21331931.LA11G
version-cpld: None
version-microp: None
version-main: 1.58.502.1
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0
y0yerrj0sh said:
Hey would you be able to direct me also?
Click to expand...
Click to collapse
Yours is AT&T device, check here, they have RUU for your version
http://forum.xda-developers.com/showthread.php?t=2751432
Or here for nandroid backup
http://forum.xda-developers.com/att...nt/att-stock-backups-recoveries-otas-t2855966
I have a Wind Phone Just like the first one but the download for the backup has been taken down. If I could get the link, that'd be great
Cookie_Fusion said:
I have a Wind Phone Just like the first one but the download for the backup has been taken down. If I could get the link, that'd be great
Click to expand...
Click to collapse
Ask in the right thread, you'll get the link.
Which software version no. ? 1.55.1500.4 or 3.34.1500.4 ?
Let me know in this thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
and I will reupload the link in that thread.

Can't escape from boot menu. Help with installing any rom.

I tried to update my phone to 6.0 from 4.4.2 with ADB. Came with an error "System partition size error". It doesn't see the SD card when I tried to install from it.
My phone stuck at hboot screen. I can only access recovery and hboot menu. And when I tried to update to Lolipop with exe from a computer it says "Error 155: Unknown error". Xp 32 bit USB 2.0.
After I said reboot system through TWRP and it said No OS installed! .
But I have already installed ViperOne 3.2.1 Kitkat and Stock 4.4.4 before without any error still can't escape from boot menu. Any help would appreciate.
Here is some information:
S-OFF
Unlocked
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.14.2133156.UA24G
version-cpld: None
version-microp: None
version-main: 1.12.401.17
version-misc: PVT SHIP S-OFF
serialno: FA43CSF00379
imei: ***********
imei2: Not Support
meid: 99000499006617
product: m8_whl
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 0a41237a
hbootpreupdate: 11
gencheckpt: 0
And I think the device was T-Mobile 13000 at first but I'm not sure about it.
Did you update the firmware? I ran into a similar issue because my device shipped out with 4.4.2.
To update the firmware, you have to do the following:
Set your OEM's CID. Do not use SUPERCID.
My device was GPE, so [fastboot oem writecid GOOGL001]
Re-lock your Bootloader using Fastboot.
[fastboot oem lock ] then [fastboot reboot ruu]
You'll see the device logo centered onscreen.
Flash a firmware update file (does NOT have to be a whole ROM) and you'll be able to update to the threshold of that firmware.
I have Marshmallow firmware. So I can use MM or LP as well as KK ROMs now without bootloop.
Be sure to hit thanks if I helped! Be even more sure to PM me if you need help (like firmware files if you have the same variant).
Sent from my HTC M8 GPE
? Mass Transit Honchkrow ?
My current firmware is: 3.28.401.9. Which one do you suggest to install? And I would really appreciate if you send me firmware files. I'm not sure which variant's firmware I should use.
Edit: By the way I can install roms but ruu.exe gives me error.
DreamGod said:
My current firmware is: 3.28.401.9.
Click to expand...
Click to collapse
wrong ...
your firmware is 1.12.401.17 as shown on your getvar details on post #1.
and your device is a sprint device (m8_whl) and you should not flash any GSM firmware.
Sprint & GSM has different System partition size (your error)
change your model-ID currently shown as 0P6B10000 back to to sprint 0P6B70000
and install Sprint RUU or firmware. You can find them on Sprint forum.
furboom1240 said:
Did you update the firmware? I ran into a similar issue because my device shipped out with 4.4.2.
To update the firmware, you have to do the following:
Set your OEM's CID. Do not use SUPERCID.
My device was GPE, so [fastboot oem writecid GOOGL001]
Re-lock your Bootloader using Fastboot.
[fastboot oem lock ] then [fastboot reboot ruu]
You'll see the device logo centered onscreen.
Flash a firmware update file (does NOT have to be a whole ROM) and you'll be able to update to the threshold of that firmware.
I have Marshmallow firmware. So I can use MM or LP as well as KK ROMs now without bootloop.
Be sure to hit thanks if I helped! Be even more sure to PM me if you need help (like firmware files if you have the same variant).
Sent from my HTC M8 GPE
Mass Transit Honchkrow
Click to expand...
Click to collapse
He is S-Off. No need to relock the bootloader ever.
And for S-On users, the only time you will need to relock the bootloader is for running an RUU
Also, superCID will work with any firmware. No need to set the CID to his carrier's (not OEM's) CID
xunholyx said:
He is S-Off. No need to relock the bootloader ever.
And for S-On users, the only time you will need to relock the bootloader is for running an RUU
Click to expand...
Click to collapse
I thought so too. I'm also s-off but my firmware update stalled code 20 until I relocked the bootloader. But when I was finished I reversed that course [fastboot OEM unlock] and then dismissed the warning.
That's exactly what I did. Note that I mention RUU in my Fastboot instructions. :\
Sent from my HTC M8 GPE
? Mass Transit Honchkrow ?
furboom1240 said:
I thought so too. I'm also s-off but my firmware update stalled code 20 until I relocked the bootloader. But when I was finished I reversed that course [fastboot OEM unlock] and then dismissed the warning.
That's exactly what I did. Note that I mention RUU in my Fastboot instructions. :\
Sent from my HTC M8 GPE
Mass Transit Honchkrow
Click to expand...
Click to collapse
Error 20? Never heard of that one, no idea what it is.
ckpv5 said:
wrong ...
your firmware is 1.12.401.17 as shown on your getvar details on post #1.
and your device is a sprint device (m8_whl) and you should not flash any GSM firmware.
Sprint & GSM has different System partition size (your error)
change your model-ID currently shown as 0P6B10000 back to to sprint 0P6B70000
and install Sprint RUU or firmware. You can find them on Sprint forum.
Click to expand...
Click to collapse
Thank you I will try and tell the results. I though that my device was GSM didn't even know that it was Sprint. I was totally wrong at first then.
xunholyx said:
Error 20? Never heard of that one, no idea what it is.
Click to expand...
Click to collapse
Something I got in the Fastboot.
You open a command window and reference the file.
You either get a OKAY (milliseconds taken) or FAILED (error##). Some errors are obvious, like the cable disconnected, your recovery is out of date, update your SDK.
Sent from my HTC M8 GPE
? Mass Transit Honchkrow ?
furboom1240 said:
Something I got in the Fastboot.
You open a command window and reference the file.
You either get a OKAY (milliseconds taken) or FAILED (error##). Some errors are obvious, like the cable disconnected, your recovery is out of date, update your SDK.
Sent from my HTC M8 GPE
Mass Transit Honchkrow
Click to expand...
Click to collapse
Yeah, I know what the error codes are. LOL! I'm far from new at this.
I just haven't heard of error 20
xunholyx said:
Yeah, I know what the error codes are. LOL! I'm far from new at this.
I just haven't heard of error 20
Click to expand...
Click to collapse
Sometimes remembering this stuff makes my head hurt. I often went to webchat to diagnose issues or find similarities.
Sometimes it's how I word a problem, the other time its the problem itself that throws off a bit... ?
Sent from my HTC M8 GPE
? Mass Transit Honchkrow ?
ckpv5 said:
wrong ...
your firmware is 1.12.401.17 as shown on your getvar details on post #1.
and your device is a sprint device (m8_whl) and you should not flash any GSM firmware.
Sprint & GSM has different System partition size (your error)
change your model-ID currently shown as 0P6B10000 back to to sprint 0P6B70000
and install Sprint RUU or firmware. You can find them on Sprint forum.
Click to expand...
Click to collapse
Hello, it's me again. I'm trying to change my model-id but it shows like that:
P6B7\ (enter)
0000
My device won't open (only hboot and fastboot, no recovery) so I'm not sure how I can use adb since it doesn't show my device and its serial number. I appreciate your help...
DreamGod said:
Hello, it's me again. I'm trying to change my model-id but it shows like that:
P6B7\ (enter)
0000
My device won't open (only hboot and fastboot, no recovery) so I'm not sure how I can use adb since it doesn't show my device and its serial number. I appreciate your help...
Click to expand...
Click to collapse
How did you do that ? You wrote the code on your own instead of copy paste the whole code ? I don't know whether can fix that ... let's try again.
1. You need to install the old version TWRP recovery as your current hboot is 3.16.0.0000
install TWRP 2.8.1.0 - https://dl.twrp.me/m8/
2. After TWRP 2.8.1.0 installed, boot to recovery
mount - system
3. connect to PC and open a command prompt from your fastboot/adb folder then run command
adb shell
then this code (copy and paste .. don't write them on command prompt on your own)
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x37\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
exit
on recovery select reboot - bootloader
then run command fastboot getvar mid - you should have 0P6B70000 now (hopefully)
ckpv5 said:
How did you do that ? You wrote the code on your own instead of copy paste the whole code ? I don't know whether can fix that ... let's try again.
1. You need to install the old version TWRP recovery as your current hboot is 3.16.0.0000
install TWRP 2.8.1.0 - https://dl.twrp.me/m8/
2. After TWRP 2.8.1.0 installed, boot to recovery
mount - system
3. connect to PC and open a command prompt from your fastboot/adb folder then run command
adb shell
then this code (copy and paste .. don't write them on command prompt on your own)
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x37\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
exit
on recovery select reboot - bootloader
then run command fastboot getvar mid - you should have 0P6B70000 now (hopefully)
Click to expand...
Click to collapse
Firstly I want to thank you with your help I've changed model-id.
Then I installed this firmware: https://www.androidfilehost.com/?fid=24391638059059188
and the screen was like that: http://hizliresim.com/4lZjAL
I've succeeded to open boot menu. Then I tried to install this version: https://www.androidfilehost.com/?fid=24052804347796593
but sd card gave me "wrong zippe image!". When I tried to install with .exe it gave me "Error: 155 Unknown error". Couldn't install with command either. I think something is wrong with firmware or rom. By the way there's a text "OP6B100x" behind my phone. Are we sure about the variant of my phone? I'm not even sure which firmware and rom I should install. I appreciate all your help.
DreamGod said:
Firstly I want to thank you with your help I've changed model-id.
Then I installed this firmware: https://www.androidfilehost.com/?fid=24391638059059188
and the screen was like that: http://hizliresim.com/4lZjAL
I've succeeded to open boot menu. Then I tried to install this version: https://www.androidfilehost.com/?fid=24052804347796593
but sd card gave me "wrong zippe image!". When I tried to install with .exe it gave me "Error: 155 Unknown error". Couldn't install with command either. I think something is wrong with firmware or rom. By the way there's a text "OP6B100x" behind my phone. Are we sure about the variant of my phone? I'm not even sure which firmware and rom I should install. I appreciate all your help.
Click to expand...
Click to collapse
Text "OP6B100x" behind your phone most probably due to change of back cover.
Your getvar on post #1 clearly shown it is Sprint
meid: 99000499006617
product: m8_whl
where the "OP6B100x" should read
meid: 00000000000000
product: m8_ul
After you installed 6.20.651.3_full_firmware.zip, you should run the 6.20.651.3 RUU.exe (you should not get error 155)
but instead, you tried a lower version RUU.zip which require a htc_fastboot to flash it. I don't know what you meant by "sd card gave me "wrong zippe image!"". Was it you tried with external_sd method ?
about the screen that you get .. I don't know for sure .. maybe it's because your ROM version is wrong for the firmware that newly installed ... and maybe (the one that I'm always scare of) .. you previously installed GSM firmware 1.12.401.17 on a CDMA device which may altered some of your system partition tables.
That's why there's a big warning here : http://forum.xda-developers.com/showpost.php?p=51700638&postcount=2
warning! provided only for folks who have changed their mid and realized they shouldnt have,or achieved s off via a java card. DO NOT change a gsm or vzw device to this in attempts to use it on sprint and convert to a sprint device(or vice versa).​
Can you post current fastboot getvar all result after you made all these changes ? You may need to reflash the 6.20.651.3 and run 6.20.651.3 RUU.exe after the firmware installed.
ckpv5 said:
Text "OP6B100x" behind your phone most probably due to change of back cover.
Your getvar on post #1 clearly shown it is Sprint
meid: 99000499006617
product: m8_whl
where the "OP6B100x" should read
meid: 00000000000000
product: m8_ul
After you installed 6.20.651.3_full_firmware.zip, you should run the 6.20.651.3 RUU.exe (you should not get error 155)
but instead, you tried a lower version RUU.zip which require a htc_fastboot to flash it. I don't know what you meant by "sd card gave me "wrong zippe image!"". Was it you tried with external_sd method ?
about the screen that you get .. I don't know for sure .. maybe it's because your ROM version is wrong for the firmware that newly installed ... and maybe (the one that I'm always scare of) .. you previously installed GSM firmware 1.12.401.17 on a CDMA device which may altered some of your system partition tables.
That's why there's a big warning here : http://forum.xda-developers.com/showpost.php?p=51700638&postcount=2
warning! provided only for folks who have changed their mid and realized they shouldnt have,or achieved s off via a java card. DO NOT change a gsm or vzw device to this in attempts to use it on sprint and convert to a sprint device(or vice versa).​
Can you post current fastboot getvar all result after you made all these changes ? You may need to reflash the 6.20.651.3 and run 6.20.651.3 RUU.exe after the firmware installed.
Click to expand...
Click to collapse
After I installed Marshmallow, I can open phone now. Thank you for your all help.
Oh, thanks

Solved: Bootloop to bootloader, can't find RUU for 3.35.166.12

Hi!
I unlocked my BL and flashed TWRP and CM13 on my M9. After that my mobile data doesn't worked anymore. So I wanted to update the firmware/radio. For S-OFF the Sunshine.apk doesn't work on CM13. So I relocked my BL for RUU. But, after relocking BL my phone is in bootloop to the bootloader. Only bootloader and download mode are possible, no recovery.
Now I'm looking for a RUU, but can't find any working :crying:
May somebody help me finding a RUU or rescue my phone anyway please?
S-ON
RELOCKED
kernel: lk
product: htc_himauhl
version: 1.0
imei: *****
version-main: 3.35.166.12
boot-mode: download
version-baseband: 01.01_U11440792_96.00.51201G_F
version-bootloader: 1.0.0.0000
mid: 0PJA10000
cid: VODAP110
Vater said:
Hi!
I unlocked my BL and flashed TWRP and CM13 on my M9. After that my mobile data doesn't worked anymore. So I wanted to update the firmware/radio. For S-OFF the Sunshine.apk doesn't work on CM13. So I relocked my BL for RUU. But, after relocking BL my phone is in bootloop to the bootloader. Only bootloader and download mode are possible, no recovery.
Now I'm looking for a RUU, but can't find any working :crying:
May somebody help me finding a RUU or rescue my phone anyway please?
S-ON
RELOCKED
kernel: lk
product: htc_himauhl
version: 1.0
imei: *****
version-main: 3.35.166.12
boot-mode: download
version-baseband: 01.01_U11440792_96.00.51201G_F
version-bootloader: 1.0.0.0000
mid: 0PJA10000
cid: VODAP110
Click to expand...
Click to collapse
You're pretty ahead of the game - and with access to bootloader & download mode, you're in good shape. Since you already have your CID, all you need to do is look it up in the list created by Sneakyghost/Behold_this and then find the matching RUU in Flippy498's spreadsheet. Follow his instructions for applying the RUU via the SD card method and you'll be back to stock.
I've got both in my signature below (use the spoilers buttons).
-----------------------
Useful links for modding your HTC M9
Flippy498's Google Sheet
- the end-all, be-all resource for HTC M9 restoration
SKU-, CID- and MID-List by Sneakyghost and Behold_this
- a spreadsheet for using your CID & MID to identify your phone
HTC Sync Manager
- installs the necessary drivers & ADB tools for the HTC M9
Instructions for obtaining your CID, MID & software version on Windows:
a. Install HTC Sync Manager (this will install the necessary drivers & ADB tools)
b. Boot your phone into download mode (from a powered off state, turn on by holding the POWER+DOWNVOL)
c. Connect your phone to your PC
d. Open a command prompt window
e. Navigate to the ADB tools folder, typically C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync
- assuming the path is correct, you can cut & paste this command into your terminal: cd C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync
f. Execute the following command in a terminal (command prompt): fastboot getvar all
g. Copy the lines that mention product, version-main, mid, and cid.
Thx for your helpfull post!
My problem is finding a RUU for VODAP110 and x.xx.166.x.
Or can I flash x.xx.161.x without bricking?
Your phone won't accept the 161 RUU since your phone is S-ON. In other words there is no risk of bricking.
As already written on Handy-FAQ: If you can't re-unlock your phone you will either need to pay for ir-file.com to get a 166 RUU or you will have to pay for llabtoofer's RUU service. I couldn't find any other sources for the RUU you need.
If you are able to re-unlock then you can flash a Sense rom like Viper and get S-OFF afterwards. With S-OFF you can change your CID and flash an international, unbranded 401 RUU.
Sent from my HTC One M9 using XDA Labs
Problem solved. Special thx to Flippy498!
Solution:
Copy 0PJAIMG_HIMA_UHL_M60_SENSE70_MR_Vodafone_CH-DE_3.35.166.12_Radio_01.01_U11440792_96.00.51201G_F_release_470274_combined_signed.zip (ir-file.com/show.php?token=43046) named as 0PJAIMG.zip on SD and boot to download mode -> vol+ to flash.
After that i had stock ROM.
Now I'll unlocking bootloader, installing TWRP, flashing Viper, S-Off with Sunshine and Super-CID
Vater said:
Problem solved. Special thx to Flippy498!
Solution:
Copy 0PJAIMG_HIMA_UHL_M60_SENSE70_MR_Vodafone_CH-DE_3.35.166.12_Radio_01.01_U11440792_96.00.51201G_F_release_470274_combined_signed.zip (ir-file.com/show.php?token=43046) named as 0PJAIMG.zip on SD and boot to download mode -> vol+ to flash.
After that i had stock ROM.
Now I'll unlocking bootloader, installing TWRP, flashing Viper, S-Off with Sunshine and Super-CID
Click to expand...
Click to collapse
Hi can you share the ruu 3.35.166.12 please ?
Envoyé de mon Moto G (4) en utilisant Tapatalk
Hi gents, here is the RUU in question: https://mega.nz/#!4eZSlZwC!P7gypLvDCZLGkUvXn5q843IMzg_TpHEpY-08hRsmuUo
P$YCH0 said:
Hi gents, here is the RUU in question: https://mega.nz/#!4eZSlZwC!P7gypLvDCZLGkUvXn5q843IMzg_TpHEpY-08hRsmuUo
Click to expand...
Click to collapse
If you provide the MD5 check sum for the file then I can add the link to the ReadMe thread.
Edit: Nevermind. I just noticed that it's a combined_signed RUU. Therefore, only users with S-OFF can use it and adding it to the ReadMe thread isn't a good idea.
P$YCH0 said:
Hi gents, here is the RUU in question: https://mega.nz/#!4eZSlZwC!P7gypLvDCZLGkUvXn5q843IMzg_TpHEpY-08hRsmuUo
Click to expand...
Click to collapse
Hi
Thanks but my device is S-on and i don't know if i can flash this
Envoyé de mon Moto G (4) en utilisant Tapatalk
Flippy498 said:
If you provide the MD5 check sum for the file then I can add the link to the ReadMe thread.
Edit: Nevermind. I just noticed that it's a combined_signed RUU. Therefore, only users with S-OFF can use it and adding it to the ReadMe thread isn't a good idea.
Click to expand...
Click to collapse
Are you sure about this? I personally flashed this file while my phone was unrooted and S-ON when my stock rom got corrupted a couple of months ago. It was only afterwards that I rooted, flashed custom recovery and did S-OFF.
UPDATE: I think this is the MD5 (I ran the windows CertUtil to calculate it):
ff 9d ad b4 c6 78 de 5b c3 e8 d4 69 dc e9 78 c3
Click to expand...
Click to collapse
So far, all combined_signed RUUs that I've faced during the last couple of years were only flashable with S-OFF.
Those aren't official RUUs (which are only labeled as signed). The combined_signed ones (that I've seen so far) are custom made and comparable with Sneakyghost's firmware files. The files inside the *.zip are official and correctly signed by HTC but the *.zip itself is custom made and therefore not correctly signed. S-ON devices refuse to get flashed with *.zip files that aren't signed properly since that's the whole purpose of S-ON. It should prevent you from flashing unofficial files on your phone.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
So far, all combined_signed RUUs that I've faced during the last couple of years were only flashable with S-OFF.
Those aren't official RUUs (which are only labeled as signed). The combined_signed ones (that I've seen so far) are custom made and comparable with Sneakyghost's firmware files. The files inside the *.zip are official and correctly signed by HTC but the *.zip itself is custom made and therefore not correctly signed. S-ON devices refuse to get flashed with *.zip files that aren't signed properly since that's the whole purpose of S-ON. It should prevent you from flashing unofficial files on your phone.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thanks for the explanation Flippy It makes sense. So in worse case scenario the phone won't event attempt a flash if the signature is unsigned? If that is the case it might be worth a shot?
Now I'm very surprised how this worked for me. I was 100% S-On at that time.
The only explanation that I have is that the file might be wrongly labeled...
Sent from my HTC One M9 using XDA Labs

Htc one m8 unable to find correct firmware and rom

THANKS IN ADVANCE
hi being long period user of android phone still facing many problems to get OTA update on my phone. I was excited about my phone HTC one M8 and wanted to install OTA update there was not any software update option in my phone and than i ran for internet search spent regular three days to find correct firmware get back to stock which totally different from samsung phones. I gone through all the the threads and option provided on internet tried to get back to stock. I need help of professional
who can sort out this problem. HTC PHONE IS NOW BOOTLOADER LOCKED S-OFF KITKAT INSTALLED SUPERCID software number 1.54.651.8
PLEASE GIVE LINK TO GET STOCK RECOVERY AND HOW TO INSTALL OR FLASH IT.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.05.20.0321_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ***********
(bootloader) imei: ***********
(bootloader) imei2: Not Support
(bootloader) meid: **************
(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: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s
http://forum.xda-developers.com/showthread.php?t=2729173
http://forum.xda-developers.com/show....php?t=2729173
Click to expand...
Click to collapse
THANKS ckpv5 I WILL GIVE YOU WHOLE INFO. ABOUT MY PROBLEM
As i changed my MID and flashed wrong zip of HTC europe rom on HTC SPRINT which drained everything including my custom TWRP. I was totally new to HTC totally messed up everything. its been more than five days my phone had stuck at hboot screen i know you guy are genius can save my hundard of BUCKs as its new phone bought 15 days ago it was rooted.
I WAS TRYING TO INSTALL SPRINT FIRMWARE TOO BECAUSE I HAD ALREADY FLASHED THAT FIRMWARE ACCORDING TO EUROPE ROM. NOW THE PROBLEM IS THAT I AM UNABLE TO FLASH FIRMWARE DUE TO CHANGED MID (talked earlier) CANNOT UNDERSTAND WHAT TO DO.
Do you still have TWRP installed ?
If no, install one
If yes,
Boot to TWRP recovery, select mount - system
open command prompt from your adb/fastboot folder then run command
adb shell
then this code
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x37\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
Make sure you copy the code, not write it yourself
then exit
then select reboot - bootloader
then run
fastboot getvar mid
you should see your mid now read 0P6B70000
(you don't need "su" command)
Now you can install Sprint RUU - http://www.htc.com/us/support/htc-one-m8-sprint/news/
or check those in Sprint section that I linked above
Note : You will get your device running again but you maybe lost the 3G/4G and only can get 2G. Reason is you flashed wrong radio meant for GSM on your CDMA, this usually brick the radio. If you're lucky enough, this is not happening.
ckpv5 said:
Do you still have TWRP installed ?
If no, install one
If yes,
Boot to TWRP recovery, select mount - system
open command prompt from your adb/fastboot folder then run command
adb shell
then this code
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x37\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
Make sure you copy the code, not write it yourself
then exit
then select reboot - bootloader
then run
fastboot getvar mid
you should see your mid now read 0P6B70000
(you don't need "su" command)
Now you can install Sprint RUU - http://www.htc.com/us/support/htc-one-m8-sprint/news/
or check those in Sprint section that I linked above
Note : You will get your device running again but you maybe lost the 3G/4G and only can get 2G. Reason is you flashed wrong radio meant for GSM on your CDMA, this usually brick the radio. If you're lucky enough, this is not happening.
Click to expand...
Click to collapse
this is what now comes up when i try to flash TWRP
C:\Users\USER\Desktop\fastboot_adb\fastboot_adb>fastboot flash recovery "twrp-2.8.5.0-m8_whl.img."
target reported max download size of 1826418688 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.501s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.516s
i'm brain dead nothing works SUGGEST SOMETHING
EVEN UNABLE TO UNLOCK BOOTLOADER NOW
You can't fastboot flash recovery while the bootloader is locked/relocked.
You need a microSD.
Download the 0P6BIMG.zip that I posted here : http://forum.xda-developers.com/showpost.php?p=67526388&postcount=387
No need to worry what OS it is written for now, it will get fixed when you install RUU.
Place the 0P6BIMG.zip on root of microSD (means not in any folder)
Then put your phone on hboot, it will scan the file. Volume up to update (install). Once done, it will ask you to reboot but you know that your device is bootlooping, just put the device on bootloader (remove the microSD to delete the 0P6BIMG.zip)
Now you can boot to TWRP recovery and do the rest as described above.
ckpv5 said:
You can't fastboot flash recovery while the bootloader is locked/relocked.
You need a microSD.
Download the 0P6BIMG.zip that I posted here : http://forum.xda-developers.com/showpost.php?p=67526388&postcount=387
No need to worry what OS it is written for now, it will get fixed when you install RUU.
Place the 0P6BIMG.zip on root of microSD (means not in any folder)
Then put your phone on hboot, it will scan the file. Volume up to update (install). Once done, it will ask you to reboot but you know that your device is bootlooping, just put the device on bootloader (remove the microSD to delete the 0P6BIMG.zip)
Now you can boot to TWRP recovery and do the rest as described above.
Click to expand...
Click to collapse
:fingers-crossed: Thanks man you are really great now these are the outcomes
C:\Users\USER\Desktop\fastboot_adb\fastboot_adb>fastboot getvar mid
mid: 0P6B70000
finished. total time: -0.000s
Now it want follow your command give me further steps. Thanks Again
Moreover, i made mistake that i also had flashed firmware file according to htc europe rom. Now which one should choose.
Doesn't matter about the firmware now .. just install RUU.
That was the guide written above.
1. Change MID
2. Install RUU exe that is linked above.
Make sure you have windows PC with usb2.0 and the latest htc usb drivers are installed.
HTC USB drivers - Install HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
- it will install the needed drivers then uninstall the HTC Sync Manager but leave the drivers.
Or you can use RUU zip
0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU.zip that you can get in Sprint thread.
Rename it to 0P6BIMG.zip and install the same way as you installed TWRP above (microSD method)
ckpv5 said:
Doesn't matter about the firmware now .. just install RUU.
That was the guide written above.
1. Change MID
2. Install RUU
Make sure you have windows PC with usb2.0 and the latest htc usb drivers are installed.
HTC USB drivers - Install HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
- it will install the needed drivers then uninstall the HTC Sync Manager but leave the drivers.
Click to expand...
Click to collapse
0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU
sorry it could be silly but which one is right one in both of it or give the link to particular one because i am afraid don't mess anything again. Thanks man
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
What's this RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.154 0.4 got do with your device ?
All my links are referred to RUU 6.20.651.3 on post #2, #4 & #8
ckpv5 said:
What's this RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.154 0.4 got do with your device ?
All my links are referred to 6.20.651.3 on post #2, #4 & #8
Click to expand...
Click to collapse
Sorry bro i sent you by mistake i got it i will flash 0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU file through HBOOT and i will post the outcome whatever there will be but you are great. You saved me. Thanks a lot bro
It says that Device halted due large image update file
What do you suggest now.
Then install 6.20.651.3 Signed Full Firmware first, see whether it can be installed.
Rename it to 0P6BIMG.zip and install it microSD method. If successful then install RUU.
(This is the problem .. I don't have Sprint device, unable to test)
ckpv5 said:
Then install 6.20.651.3 Signed Full Firmware first, see whether it can be installed.
Rename it to 0P6BIMG.zip and install it microSD method. If successful then install RUU.
(This is the problem .. I don't have Sprint device, unable to test)
Click to expand...
Click to collapse
There is another problem occured i flashed signed firmware now phone only shows the HTC logo and unable to restart what should do now???
Was the firmware installation successful ? This is important.
When you reboot, there is no OS, you need to put back to bootloader then install RUU.
(Same way after you installed TWRP before)
I think this is easier.. instead of going to Marsmallow, install the lollipop first just to get your phone up & running.
Install this 0P6BIMG_Sprint_HTC_One_M8_4.25.651.18_RUU.zip, for this you don't need to install firmware.
Once successful, then you can try again to install Marshmallow 0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU.zip but
you need to install 6.20.651.3 Firmware first.
ckpv5 said:
Was the firmware installation successful ? This is important.
When you reboot, there is no OS, you need to put back to bootloader then install RUU.
(Same way after you installed TWRP before)
I think this is easier.. instead of going to Marsmallow, install the lollipop first just to get your phone up & running.
Install this 0P6BIMG_Sprint_HTC_One_M8_4.25.651.18_RUU.zip, for this you don't need to install firmware.
Once successful, then you can try again to install Marshmallow 0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU.zip but
you need to install 6.20.651.3 Firmware first.
Click to expand...
Click to collapse
Thanks man we made it IT IS FINALLY WORKING you are really great Man this info will HELP SOMEONE AS WELL..
Great ..
Now I can sleep well.. it's 1.00 am here... good night
ckpv5 said:
Great ..
Now I can sleep well.. it's 1.00 am here... good night
Click to expand...
Click to collapse
Thanks you spent much time to solve my problem rest of the phone is working fine and it shows one error of something that attached a screenshot also attached screenshot of networks please tell there is 3g and 4g Thank you great man
There is also portable wifi hotspot is missed. Need help where to find it.
karamghumaan said:
There is also portable wifi hotspot is missed. Need help where to find it.
Click to expand...
Click to collapse
Did you find it? And how did you changed WiFi and signal status bar icon? Which htc theme did you use?
Sent from my HTC One_M8 using Tapatalk
Zile995 said:
Did you find it? And how did you changed WiFi and signal status bar icon? Which htc theme did you use?
Click to expand...
Click to collapse
Hello mate No it is till missing and official theme and i also want change that icon but i couldn't find that option too. Are you able to give me that solution how i can do it. More there is activating device window at start up how can i remove that?
karamghumaan said:
Thanks you spent much time to solve my problem rest of the phone is working fine and it shows one error of something that attached a screenshot also attached screenshot of networks please tell there is 3g and 4g Thank you great man
Click to expand...
Click to collapse
SO you have no cell data access?
What bands does your carrier uses for 3G and LTE (what band for each of those - they are 2 different things).
karamghumaan said:
There is also portable wifi hotspot is missed. Need help where to find it.
Click to expand...
Click to collapse
Hotspot is locked out on most US carrier versions. If you don't see Hotspot as an available "tile" in the notification quick settings, and no Hotspot widget, than the feature has been disabled on your stock ROM.
Easiest way to enable Hotspot is with the proper custom ROM (supports Sprint version M8).

Trouble locating origin of One m8

Hello to you all,
I thought about asking in the help thread but my post will be somewhat long XD
I'm having trouble locating the origin of my HTC One M8 that I bought 2 days ago in bulk from a local shop. It's new, SIM Unlocked, but apparently rooted and S-OFF, figured it was needed in order to unlock it from it's former carrier, which brings me to my question : I want to know it's original carrier and region in order to safely select RUU and ROMs and preferably I would like to do OTAs too. I want to know whether I'll have problems updating to Marshmallow in the future.
Now, in the back of the phone is written : model OP6B700, that would make it a Sprint device right ? which from what I read is pretty delicate to work with, being CDMA and all.
CID Getter gave me : OPTUS_001
And here is my fastboot getvar all :
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.708.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT548WMxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I noticed I have superCID ... why doesn't CID Getter report it ? If I want to revert it back which one do I input ? I don't know the stock value.
I noticed my MID is OP6B65000 what model is this ?
Really confused right now should I go ahead and install OTA ? I have one notification version 4.16.401.13 that wants to be installed.
Also I have "unknown" under HTC SDK API level, don't know why.
It seems I have the 2.5Ghz version of S801, but some utilities report AC variant some others AB. I got 63k on AnTuTu 6.2.6
Other than that the phone seems to be running really good, snappy, no lag, gets a bit warm with light usage, I don't think I got a fake one but correct me if I'm wrong.
It's in airplane mode, haven't put a SIM card in yet.
So what do you guys think ? I surely appreciate any insight you might have
ELS28 said:
I want to know whether I'll have problems updating to Marshmallow in the future.
Click to expand...
Click to collapse
You don't have to wait to update to Marshmallow if you want to, you can do it now.
ELS28 said:
...in the back of the phone is written : model OP6B700, that would make it a Sprint device right ? which from what I read is pretty delicate to work with, being CDMA and all.
Click to expand...
Click to collapse
That's only back cover get replaced. You getvar result doesn't show it is a Sprint device.
Sprint product is M8_WHL and yours is GSM M8_UL
ELS28 said:
CID Getter gave me : OPTUS_001
And here is my fastboot getvar all :
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-main: 4.18.708.12
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: 11111111
bootloader) security: off
I noticed I have superCID ... why doesn't CID Getter report it ? If I want to revert it back which one do I input ? I don't know the stock value.
I noticed my MID is OP6B65000 what model is this ?
It seems I have the 2.5Ghz version of S801
Click to expand...
Click to collapse
Based of the info above especially the MID 0P6B65000 & 2.5Ghz .. that's an Optus device ... originally from Australia. The original CID is OPTUS_001
ELS28 said:
Really confused right now should I go ahead and install OTA ? I have one notification version 4.16.401.13 that wants to be installed.
Click to expand...
Click to collapse
You can't do OTA to 4.16.401.13, won't work .. you'll get system variant error with OTA.
ELS28 said:
It's in airplane mode, haven't put a SIM card in yet.
Click to expand...
Click to collapse
You should put a SIM to test whether it's really SIM unlocked from Optus.
Also to check whether LTE is working fine.
Where are you located ? You have a S-Off device, you can install any region GSM RUU (if available) but not OTA to 4.16.401.13 when your OS on bootloader is shown as Hong Kong and MID is Optus Australia.
ckpv5 said:
You don't have to wait to update to Marshmallow if you want to, you can do it now.
That's only back cover get replaced. You getvar result doesn't show it is a Sprint device.
Sprint product is M8_WHL and yours is GSM M8_UL
Based of the info above especially the MID 0P6B65000 & 2.5Ghz .. that's an Optus device ... originally from Australia. The original CID is OPTUS_001
You can't do OTA to 4.16.401.13, won't work .. you'll get system variant error with OTA.
You should put a SIM to test whether it's really SIM unlocked from Optus.
Also to check whether LTE is working fine.
Where are you located ? You have a S-Off device, you can install any region GSM RUU (if available) but not OTA to 4.16.401.13 when your OS on bootloader is shown as Hong Kong and MID is Optus Australia.
Click to expand...
Click to collapse
Thank you for replying
To answer your question, my location is north africa. Tomorrow I'll get a nano SIM to try.
The information you provided raised some more questions :
1- I can't do OTAs, so the only way to update for me is through RUU or custom ROMS ?
2- I have a Hong Kong OS, can I change it ? will I have to change the MID and CID accordingly ? I can choose whatever values I want it won't cause any problems ?
3- How come while in OS I have different build numbers than in Bootloader ? in OS I have build version : 4.16.401.10. That's europe version right ?
4- Let's say I want to revert everything back to stock international version with Sense etc, to be able to do OTAs, what do I have to do ?
ELS28 said:
Thank you for replying
To answer your question, my location is north africa. Tomorrow I'll get a nano SIM to try.
Click to expand...
Click to collapse
Do that first .. see any problem with network.
ELS28 said:
1- I can't do OTAs, so the only way to update for me is through RUU or custom ROMS ?
Click to expand...
Click to collapse
You can do OTA only if you put the Optus ROM in your device. The problem is back to Optus and do OTA may break the SIM unlock.
But why do you want to OTA ? You can manually direct update it to Marshmallow if that is your intention.
ELS28 said:
2- I have a Hong Kong OS, can I change it ? will I have to change the MID and CID accordingly ? I can choose whatever values I want it won't cause any problems ?
Click to expand...
Click to collapse
You don't need to change the CID, let it be SuperCID but you may need to change MID (some people said no need to change MID when SuperCID but personally I don't experience a success firmware flashing without proper MID)
You can only choose any value meant for GSM but not CDMA. While on SuperCID, you need only change MID or change it to SuperMID.
ELS28 said:
3- How come while in OS I have different build numbers than in Bootloader ? in OS I have build version : 4.16.401.10. That's europe version right ?
Click to expand...
Click to collapse
Bootloader info is your firmware info.
OS no. in settings is Software info.
So this is like you're running a custom ROM, running a Europe ROM on Hong Kong firmware.
ELS28 said:
4- Let's say I want to revert everything back to stock international version with Sense etc, to be able to do OTAs, what do I have to do ?
Click to expand...
Click to collapse
Depends on which International version .. let say it is Europe version
1. I suggest to change the MID to 0P6B10000 - http://forum.xda-developers.com/showthread.php?t=2708581
2. Install latest Europe RUU - http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
(skip the relocking part)
ckpv5 said:
Do that first .. see any problem with network.
You can do OTA only if you put the Optus ROM in your device. The problem is back to Optus and do OTA may break the SIM unlock.
But why do you want to OTA ? You can manually direct update it to Marshmallow if that is your intention.
You don't need to change the CID, let it be SuperCID but you may need to change MID (some people said no need to change MID when SuperCID but personally I don't experience a success firmware flashing without proper MID)
You can only choose any value meant for GSM but not CDMA. While on SuperCID, you need only change MID or change it to SuperMID.
Bootloader info is your firmware info.
OS no. in settings is Software info.
So this is like you're running a custom ROM, running a Europe ROM on Hong Kong firmware.
Depends on which International version .. let say it is Europe version
1. I suggest to change the MID to 0P6B10000 - http://forum.xda-developers.com/showthread.php?t=2708581
2. Install latest Europe RUU - http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
(skip the relocking part)
Click to expand...
Click to collapse
Hi, sorry for delayed answer.
Bought a new nanoSIM today, seems to be working fine, made a few calls etc... LTE isn't available in my municipality yet, it will be in the upcoming months but I have the option to select it. I did test HSPA though and it works fine. I guess it's fully sim unlocked then
Regarding OTA, I just saw it as an easier way to update than the commands I had to enter to flash via RUU and all... I guess now I have to learn them alright
So it's my firmware that's from Hong Kong, I didn't know that thanks for the clarification.
Sorry I have more questions
1-Now that I'm running HK firmware and corresponding MID but EU ROM, you suggested I change to EU MID, but won't that cause issues with firmware being HK ?
2- If I flash the EU RUU you sent me, I assume the firmware will no longer be HK, correct ? and after that I can just keep to install EU roms and be trouble free ?
3-I assume that my simUnlock is definitive now, correct ?
4-You seem to be certain I have superCID, so bootloader info trumps CIDgetter info, but I'm curious, why the value differs between the two ? does the app not report it correctly after changing the value ?
5-I will be downloading the files from the links you sent me, and doing my homework too but for information's sake, when I boot in bootloader, I have the "locked" banner, but you know that already I also have "software status : official" does it indicate that the Lollipop EU ROM I currently have is a stock signed one ?
6-My device came rooted but I don't see Superuser installed, I assume I'll have to root it again after the update, correct ?
A Big Thank you for the big help :good:
1-Now that I'm running HK firmware and corresponding MID but EU ROM, you suggested I change to EU MID, but won't that cause issues with firmware being HK ?​You have OS Hong Kong no. which I assume it's HKG firmware but your MID is not HKG but it can be Australia and it can be India. I assume it is Australia as it has 2.5 Ghz and CID OPTUS001 (as you mentioned it)
Change it to EU MID won't cause any issue but a better option as the current ROM on your device is EU 4.16.401.10 and that's why you get notification for OTA to 4.16.401.13
2- If I flash the EU RUU you sent me, I assume the firmware will no longer be HK, correct ? and after that I can just keep to install EU roms and be trouble free​You need to change MID first to EU then install EU RUU. The firmware will be EU, no more HKG. You can install any GSM ROM after that, trouble free.
3-I assume that my simUnlock is definitive now, correct ?​Yes it is SIM unlocked, the reason why I don't recommend Australia Optus firmware & ROM so it won't get SIM locked again. The best option is EU as you're in North Africa.
4-You seem to be certain I have superCID, so bootloader info trumps CIDgetter info, but I'm curious, why the value differs between the two ? does the app not report it correctly after changing the value ?​That's what shown on getvar result. No idea about the app. I tried, it can't read my CID as I'm running Nougat ROM. You can try Simple CID Getter to recheck.
But getvar is always correct and the best option.
5-I will be downloading the files from the links you sent me, and doing my homework too but for information's sake, when I boot in bootloader, I have the "locked" banner, but you know that already I also have "software status : official" does it indicate that the Lollipop EU ROM I currently have is a stock signed one ?​Most probably.
If you want to see whether it is stock non-rooted, you change MID to EU then you can accept the OTA and see whether it will be successful to install.
As you have a LOCKED bootloader, you need different method to change the MID .. you need to install a flashable TWRP and do the MID change while in recovery.
But why want to waste time checking, downloading and installing OTA when RUU is available and you can directly update to the latest.
6-My device came rooted but I don't see Superuser installed, I assume I'll have to root it again after the update, correct ?​How do you know that it is currently rooted ? OTA won't work on a rooted ROM.
Yes, you have to root again after each update (when you need a rooted stock ROM). If you want to install custom ROM, no need to root .. only install TWRP and install custom ROM. Custom ROM mostly come pre-rooted.
ckpv5 said:
1-Now that I'm running HK firmware and corresponding MID but EU ROM, you suggested I change to EU MID, but won't that cause issues with firmware being HK ?​You have OS Hong Kong no. which I assume it's HKG firmware but your MID is not HKG but it can be Australia and it can be India. I assume it is Australia as it has 2.5 Ghz and CID OPTUS001 (as you mentioned it)
Change it to EU MID won't cause any issue but a better option as the current ROM on your device is EU 4.16.401.10 and that's why you get notification for OTA to 4.16.401.13
2- If I flash the EU RUU you sent me, I assume the firmware will no longer be HK, correct ? and after that I can just keep to install EU roms and be trouble free​You need to change MID first to EU then install EU RUU. The firmware will be EU, no more HKG. You can install any GSM ROM after that, trouble free.
3-I assume that my simUnlock is definitive now, correct ?​Yes it is SIM unlocked, the reason why I don't recommend Australia Optus firmware & ROM so it won't get SIM locked again. The best option is EU as you're in North Africa.
4-You seem to be certain I have superCID, so bootloader info trumps CIDgetter info, but I'm curious, why the value differs between the two ? does the app not report it correctly after changing the value ?​That's what shown on getvar result. No idea about the app. I tried, it can't read my CID as I'm running Nougat ROM. You can try Simple CID Getter to recheck.
But getvar is always correct and the best option.
5-I will be downloading the files from the links you sent me, and doing my homework too but for information's sake, when I boot in bootloader, I have the "locked" banner, but you know that already I also have "software status : official" does it indicate that the Lollipop EU ROM I currently have is a stock signed one ?​Most probably.
If you want to see whether it is stock non-rooted, you change MID to EU then you can accept the OTA and see whether it will be successful to install.
As you have a LOCKED bootloader, you need different method to change the MID .. you need to install a flashable TWRP and do the MID change while in recovery.
But why want to waste time checking, downloading and installing OTA when RUU is available and you can directly update to the latest.
6-My device came rooted but I don't see Superuser installed, I assume I'll have to root it again after the update, correct ?​How do you know that it is currently rooted ? OTA won't work on a rooted ROM.
Yes, you have to root again after each update (when you need a rooted stock ROM). If you want to install custom ROM, no need to root .. only install TWRP and install custom ROM. Custom ROM mostly come pre-rooted.
Click to expand...
Click to collapse
Alright thanks for reassuring me.
For the CID, with Simple CID Getter I get the same OPTUS_001... no idea why XD
Upon installing CPU-Z to have more information about the device I noticed "root access : yes" so I installed Root checker and indeed it told me I have root access, that's how I knew about it. Well then I don't plan to OTA anymore XD
The first method to change MID that you sent me doesn't work even if I'm S-off ? so I'll need to use this tool ? http://forum.xda-developers.com/showthread.php?t=2779524 if so then the sequence order should be : Unlock bootloader from htcdev, then flashing TWRP like you said here http://forum.xda-developers.com/htc-one-m8/help/unlock-bootloader-install-custom-t3371328 then using the MID changer tool ?
I don't need to revert to stock recovery and locked bootloader before flashiing with RUU ?
ELS28 said:
1. For the CID, with Simple CID Getter I get the same OPTUS_001... no idea why XD
2. The first method to change MID that you sent me doesn't work even if I'm S-off ? so I'll need to use this tool ? http://forum.xda-developers.com/showthread.php?t=2779524 if so then the sequence order should be : Unlock bootloader from htcdev, then flashing TWRP like you said here http://forum.xda-developers.com/htc-one-m8/help/unlock-bootloader-install-custom-t3371328 then using the MID changer tool ?
3. I don't need to revert to stock recovery and locked bootloader before flashiing with RUU ?
Click to expand...
Click to collapse
1. No idea why these app read differently. Just ignore it for now .. that can be fixed later
2. Don't follow those guide .. I'll give you the guide below
3. No need
First - you need to install TWRP.
a- Download the hboot flashable zip here : http://forum.xda-developers.com/showpost.php?p=70210155&postcount=19
b- put it on root of your microsd
c- boot to bootloader then select hboot - it will ask you to update, volume up to update .. let it finish, reboot once completed. Delete/remove the 0P6BIMG.zip from your microsd.
Second - you need to unlock bootloader as it is easier to thing with unlocked bootloader
a- boot to bootloader - select hboot then recovery
b- once in recovery, select mount and mount system
c- open a command prompt from your adb/fastboot folder then type (one after another - suggest you copy paste the code, don't manually type them
adb shell
Code:
[B]echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796[/B]
exit
reboot to bootloader .. you should see the bootloader is now unlocked.
Third - change MID to EU MID 0P6B10000
a- boot to bootloader - select hboot then recovery
b- once in recovery, select mount and mount system
c- open a command prompt from your adb/fastboot folder then type (one after another - suggest you copy paste the code, don't manually type them
adb shell
Code:
[B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
exit
reboot to bootloader
open a command prompt from your adb/fastboot folder then type
fastboot getvar mid
you should see the MID now read as 0P6B10000
Fourth - your device is ready, you can install RUU as per my earlier guide.
Note : if there is error related to CID ... we'll fix it after you tried the RUU. If the SuperCID is correct, the installation should be fine.
Credit to @scotty1223 for his threads as reference
http://forum.xda-developers.com/showthread.php?t=2708571
http://forum.xda-developers.com/showthread.php?t=2708581
ckpv5 said:
1. No idea why these app read differently. Just ignore it for now .. that can be fixed later
2. Don't follow those guide .. I'll give you the guide below
3. No need
First - you need to install TWRP.
a- Download the hboot flashable zip here : http://forum.xda-developers.com/showpost.php?p=70210155&postcount=19
b- put it on root of your microsd
c- boot to bootloader then select hboot - it will ask you to update, volume up to update .. let it finish, reboot once completed. Delete/remove the 0P6BIMG.zip from your microsd.
Second - you need to unlock bootloader as it is easier to thing with unlocked bootloader
a- boot to bootloader - select hboot then recovery
b- once in recovery, select mount and mount system
c- open a command prompt from your adb/fastboot folder then type (one after another - suggest you copy paste the code, don't manually type them
adb shell
Code:
[B]echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796[/B]
exit
reboot to bootloader .. you should see the bootloader is now unlocked.
Third - change MID to EU MID 0P6B10000
a- boot to bootloader - select hboot then recovery
b- once in recovery, select mount and mount system
c- open a command prompt from your adb/fastboot folder then type (one after another - suggest you copy paste the code, don't manually type them
adb shell
Code:
[B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
exit
reboot to bootloader
open a command prompt from your adb/fastboot folder then type
fastboot getvar mid
you should see the MID now read as 0P6B10000
Fourth - your device is ready, you can install RUU as per my earlier guide.
Note : if there is error related to CID ... we'll fix it after you tried the RUU. If the SuperCID is correct, the installation should be fine.
Credit to @scotty1223 for his threads as reference
http://forum.xda-developers.com/showthread.php?t=2708571
http://forum.xda-developers.com/showthread.php?t=2708581
Click to expand...
Click to collapse
Thank you for taking up the time to write this guide,
I'm in second step, when I select mount, I have multiple cases to tick, do I untick them all but system or do I leave Cache, Data and microSD ticked with system as well ? sorry super noob question xD
ELS28 said:
Thank you for taking up the time to write this guide,
I'm in second step, when I select mount, I have multiple cases to tick, do I untick them all but system or do I leave Cache, Data and microSD ticked with system as well ? sorry super noob question xD
Click to expand...
Click to collapse
Doesn't matter what already ticked, the important part is mount system (tick) as it is not mounted at default. The rest let them be as what they are when you select mount menu.
I'll check tomorrow your progress .. time to sleep now as it's over 1.30 am here.
Good luck.
ckpv5 said:
Doesn't matter what already ticked, the important part is mount system (tick) as it is not mounted at default. The rest let them be as what they are when you select mount menu.
I'll check tomorrow your progress .. time to sleep now as it's over 1.30 am here.
Good luck.
Click to expand...
Click to collapse
alright thank you and good night
EDIT : I successfully unlocked and changed MID to 0P6B10000 there seems to be no problem at all and the phone is running fine I don't get the red developpement message on boot to OS, only when I boot to recovery, it doesn't really bother me for now. I don't plan to update to MM immediately though, this has been a lot of new manoeuvers to learn in one take plus I want to read more about eventual issues with apps after I update, so I'll be using the current ROM some time before using your guide again and updating. Thank you so much for taking me through this process, I learned a lot
ELS28 said:
I successfully unlocked and changed MID to 0P6B10000 there seems to be no problem at all and the phone is running fine
Click to expand...
Click to collapse
:good::good:

Categories

Resources