Related
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
Hi
I manually updated my M8 (un rooted) to 6.00 using google play addition. i live in UK but think this update is US version don't know if that matters.
had to update manually as kept getting no updates available message. bought phone from ebay over a year ago now and was told by HTC representative on their site chat that phone is genuine but software is not original (don't know what that means and he wouldn't give much away)
Kernel 3.4-perf-gd7aafa47 android gpe#1
build number MRA58K.H15 release keys
so now I've updated i can no longer see my version of sense as it no longer gives me that info. so I am thinking maybe it needs installing. Have lost my motion gesture options. i only have double tap to wake (can no longer double tap to sleep)
also lost the HTC music player which i thought was superb as i could change tracks without unlocking screen. tried installing that with an apk but wouldn't work.
could you please advise me
@ZZ77
build number MRA58K.H15 release keys
i believe you convert your device to GPE by accident
if you want to go back to sense
can you post getvar all after removing serialno and imei ??
someone could help you if i can't :good:
hi
I did update from SD card was this one - 6.0 Stock Non-Rooted GPE RUU - 6.0 MRA58K.H6 - 5.07.1700.6
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.23.213311491.A13G
OpenDSP-v50.2.2-00591-M8974_FO.0810
OS-5.07.1700.15
eMMC-boot 2048MB
Android version 6.0 build number MRA58k.H15 release-s
I hope that's enough info for you guys to help me out. I want to have marshmallow and keep sense too
The info you provided, was not what was asked for. And not sufficient to provide proper guidance.
You need to do fastboot getvar all, and post the results, deleting IMEI and serial number. He was not asking for IMEI and serial number.
Meaning you should not have posted your IMEI and serial number. Those are personal info, which should never be posted online. And further, they are not needed in order for us to help you.
ZZ77 said:
so now I've updated i can no longer see my version of sense as it no longer gives me that info. so I am thinking maybe it needs installing. Have lost my motion gesture options. i only have double tap to wake (can no longer double tap to sleep)
Click to expand...
Click to collapse
GPE by definition does not include Sense, and you just can't "install it" on a GPE converted phone. As previously commented, you would need to reverse the conversion, and convert back to Sense using RUU.
---------- Post added at 09:17 AM ---------- Previous post was at 09:15 AM ----------
ZZ77 said:
I manually updated my M8 (un rooted) to 6.00 using google play addition.
bought phone from ebay over a year ago now and was told by HTC representative on their site chat that phone is genuine but software is not original (don't know what that means and he wouldn't give much away)
Click to expand...
Click to collapse
That means it wasn't a GPE phone originally (from the factory), and either you or a previous owned hacked (software modifications) to make it s-off, SuperCID 11111111, and GPE.
As you mention you "manually updated" to GPE, it to me implies you did the modifications. But if that is not the case, you should clarify what you meant by that.
Was it GPE when you received/bought the phone?
cant work out fastboot getvar all. followed instructions but not getting anywhere. I pasted cmd in platform-tools folder then commands adb devices not getting anywhere with that
I only installed 6.0.0 on phone did nothing else. I didn't hack anything and was not told that phone had been hacked when I bought it.
don't know if it was GPE previously. sorry but I'm a complete beginner so Tuesday was the first time I went into bootloader and updated to 6.0.0 that way
after spending ages I think I got the info you guys asked for
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 1.23.213311491.A13G
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 5.07.1700.15
INFOversion-misc: PVT SHIP S-OFF
INFOserialno: REMOVED
INFOimei: REMOVED
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: m8_ul
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B13000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 11459804
INFOhbootpreupdate: 11
INFOgencheckpt: 0
ZZ77 said:
I only installed 6.0.0 on phone did nothing else. I didn't hack anything and was not told that phone had been hacked when I bought it.
Click to expand...
Click to collapse
It was definitely hacked/modified, if not by you, then the previous owner.
Not necessarily a bad thing. But you'll need to go through some steps to get it back to Sense. You'll probably need to change your MID, then flash the desired Marshmallow firmware, then RUU. What version firmware and RUU depends on what version (CID) you want to "convert" to. Unbranded Euro may be the best bet. But it depends on what bands your carrier uses for 3G and LTE.
@ZZ77
your mid belong to T-Mobile US device
you need to do as @redpoint73 said
change the mid to WWE mid then flash stock MM WWE firmware and flash stock MM RUU in this order
redpoint73 please correct me if i'm wrong
ahmed.ismael said:
@ZZ77
your mid belong to T-Mobile US device
you need to do as @redpoint73 said
change the mid to WWE mid then flash stock MM WWE firmware and flash stock MM RUU in this order
redpoint73 please correct me if i'm wrong
Click to expand...
Click to collapse
I agree.
redpoint73 said:
It was definitely hacked/modified, if not by you, then the previous owner.
Not necessarily a bad thing. But you'll need to go through some steps to get it back to Sense. You'll probably need to change your MID, then flash the desired Marshmallow firmware, then RUU. What version firmware and RUU depends on what version (CID) you want to "convert" to. Unbranded Euro may be the best bet. But it depends on what bands your carrier uses for 3G and LTE.
Click to expand...
Click to collapse
thanks guys appreciate the help.
I would like to go with unbranded euro I'm with EE so will that be okay?
I will have to research changing MID and flashing with RUU. cause I haven't a clue what that means hopefully not too complicated.
ZZ77 said:
I would like to go with unbranded euro I'm with EE so will that be okay?
Click to expand...
Click to collapse
Most likely, yes. Do you know what bands EE uses for 3G and LTE?
ZZ77 said:
I will have to research changing MID and flashing with RUU. cause I haven't a clue what that means hopefully not too complicated.
Click to expand...
Click to collapse
Its slightly complicated. You'll need to use adb and fastboot. Make sure you understand all the steps, before you do them. Enter all commands exactly as stated in the guides.
Guide for changing MID is here: http://forum.xda-developers.com/showthread.php?t=2708581
6.12.401.4 firmware zip, and instructions on how to flash are here: http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Obviously, you should be sure that you want to "convert" back to Sense before undertaking what is a significantly lengthy process. The good thing about being on the Sense partitions scheme, is that you can still flash GPE based custom ROMs, you just won't have the GPE partitions scheme (smaller OS/system partitions makes user data partition slightly larger) or GPE updates (although there probably won't be any major updates at this point, anyway).
Just had a look online
EE 3G 2100MHz & 4G LTE 1800MHz & 2600MHz
I will have a look at those links tomorrow when I have a few hours. I'm not very technical so will take my time with it.
I am having trouble with changing the MID
C:\Users\LB>cd c:\miniadb_M8
c:\miniadb_M8>adb devices
List of devices attached
SERIAL NUMBER device
c:\miniadb_M8>adb reboot bootloader
c:\miniadb_M8>fastboot devices
SERIAL NUMBER fastboot
c:\miniadb_M8>fastboot reboot
rebooting...
finished. total time: 0.020s
c:\miniadb_M8>adb shell
error: device offline
c:\miniadb_M8>
c:\miniadb_M8>adb shell
[email protected]_m8:/ $ echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\
x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384 <
dd: /dev/block/mmcblk0p5: Permission denied
1|[email protected]_m8:/ $
getting permission denied message. please advise
ZZ77 said:
c:\miniadb_M8>adb shell
error: device offline
Click to expand...
Click to collapse
The phone should be booted into OS when you issue this (or any adb) command. Is that the case (booted into OS)?
You also need to have Debugging toggled on in Settings>Developer Options. But I think you already do, since the command "adb devices" seemed to return the proper response (otherwise, the would not list the device, or list it as "offline").
hi
after following those instructions fastboot reboot took me back to OS so not sure what I did wrong
ZZ77 said:
hi
after following those instructions fastboot reboot took me back to OS so not sure what I did wrong
Click to expand...
Click to collapse
you forget (( su ))
to get root access
ahmed.ismael said:
you forget (( su ))
to get root access
Click to expand...
Click to collapse
just tried that same problem
C:\miniadb_M8>adb devices
List of devices attached
Removed device
C:\miniadb_M8>adb shell su
/system/bin/sh: su: not found
C:\miniadb_M8>adb shell
[email protected]_m8:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]_m8:/ $ ((su))
((su))
1|[email protected]_m8:/ $ echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x3
0\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384 <
dd: /dev/block/mmcblk0p5: Permission denied
1|[email protected]_m8:/ $
ZZ77 said:
/system/bin/sh: su: not found
Click to expand...
Click to collapse
I forgot you were not rooted. You need to be rooted to do this, that is what su (superuser) means.
You'll need to flash custom recovery TWRP, using the instructions here (also use the latest version TWRP 3.0.2 at the "Downloads" link): https://twrp.me/devices/htconem8gsm.html
Then download the SuperSU zip 2.78 from here (use the link for TWRP flashable zip): http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
After that, you will be rooted, and should be able to proceed with changing MID.
Suffice it to say, "converting" this device back to Sense is not for the faint of heart! You'll be an "expert" with fastboot and adb by the end of this!
@ZZ77 @redpoint73
if he flashed twrp recovery no need to flash supersu as he can running the command while booting into the twrp without "su"
flashed TWRP 3.0.2.
downloaded zip (TWRP / FlashFire installable ZIP) installed with TWRP from SD card. after installation got a message saying done and also updating partition details.... failed to mount '/carrier' (invalid argument) also tried this from internal storage and had same outcome
still cant access SU. please advise
Hello to all, I have an HTC One m8 that doesnt work 4g. I think this is an HTC m8 USA Version, but now It have superCID 11111111, custom-rom, S-Off ecc.. pls, help me. How to see the values on mmcblk0p6.img? I already have that file. @alray
Francesco0301 said:
Hello to all, I have an HTC One m8 that doesnt work 4g. I think this is an HTC m8 USA Version, but now It have superCID 11111111, custom-rom, S-Off ecc.. pls, help me. How to see the values on mmcblk0p6.img? I already have that file. @alray
Click to expand...
Click to collapse
Not really sure why I was mentioned here, never participated to the M8 forums, neither had the chance to play with this model, but I'll try to help anyway. If i'm correct, partition p6 on the M8 is the pg2fs partition, what info are you trying to get from this? Can you also post your "fastboot getvar all" (hide imei/serial). Btw you can read hex data from your pg2fs using HxD
alray said:
Not really sure why I was mentioned here, never participated to the M8 forums, neither had the chance to play with this model, but I'll try to help anyway. If i'm correct, partition p6 on the M8 is the pg2fs partition, what info are you trying to get from this? Can you also post your "fastboot getvar all" (hide imei/serial). Btw you can read hex data from your pg2fs using HxD
Click to expand...
Click to collapse
Hi bro, thanks for reply. I mentioned you because a lot of time ago, You have seen the right CID, model ecc of an HTC M7 with mmcblk0p6.img of an user from XDA. He sent to you his mmcblk0p6.img and You have seen the right values.. help me
Francesco0301 said:
Hi bro, thanks for reply. I mentioned you because a lot of time ago, You have seen the right CID, model ecc of an HTC M7 with mmcblk0p6.img of an user from XDA. He sent to you his mmcblk0p6.img and You have seen the right values.. help me
Click to expand...
Click to collapse
Ok I understand now, you are looking for your original CID and MID. These values are stored on the MFG partition which is p6 on the M7. The M8 does not have the same partition layout as the M7. From what I can see from another thread, the MFG partition for the M8 is located at p5 not p6. So dump your p5 partition and then open it using HxD, hit control+F to open the search box and type "0P6B", should bring you to the lines where you can see your original MID. The original CID, Serial number, IMEI, Manufacturing date etc... should all be in the same spot (if the M8 MFG structure is similar to the M7). If you're not sure you can pm me a link to your p5 and I'll take a look for you.
I'm assuming that if you are doing all this, you already have double checked your APN settings, your SIM card and also called your provider to make sure everything was fine on their side?
Might be making this more complicated than it needs to be:
1) What is your exact purpose in finding the "original" MID, CID? If its simply to find the proper RUU or firmware, its somewhat irrelevant. All the "GSM" M8 versions are identical in hardware. So unless you have a CDMA variant (Verizon, Sprint) you can use almost any RUU, firmware, since you are SuperCID and s-off.
2) May be able to determine the original version by looking at the product ID (or at least narrow down the possibilities). So I'd like to see the fastboot getvar out, as requested by a previous response (delete IMEI and serial number before posting).
3) If the intent is merely to determine the LTE band support, all you need to look at is the firmware number. Again, we need to see fastboot getvar output. Band support is determined by firmware, so its not relevant what the "original" CID,MID were. Just the current firmware number.
4) Model number on back cover may give a clue, what does it say? Although we've seen a good number of back covers replaced to remove carrier logos (usually US carrier logos in particular). So its hardly conclusive. But it may be another clue.
Note that if you do have a CDMA variant (Sprint, Verizon) you should not flash another versions RUU or firmware in an attempt to "convert" to another version, or modify band support. Doing so may result in a permanent radio brick. So again, we really need to see fastboot getvar output, in order to determine how to proceed.
alray said:
Ok I understand now, you are looking for your original CID and MID. These values are stored on the MFG partition which is p6 on the M7. The M8 does not have the same partition layout as the M7. From what I can see from another thread, the MFG partition for the M8 is located at p5 not p6. So dump your p5 partition and then open it using HxD, hit control+F to open the search box and type "0P6B", should bring you to the lines where you can see your original MID. The original CID, Serial number, IMEI, Manufacturing date etc... should all be in the same spot (if the M8 MFG structure is similar to the M7). If you're not sure you can pm me a link to your p5 and I'll take a look for you.
I'm assuming that if you are doing all this, you already have double checked your APN settings, your SIM card and also called your provider to make sure everything was fine on their side?
Click to expand...
Click to collapse
So, I have to start my phone with normal boot to Android, activate debug, connect to PC, open ADB and send commands:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p5 of=/sdcard/mmcblk0p5.img
If I do these steps, and I type "0P6B" on search box with HxD, nothing appaer. This is download link of my mmcblk0p5.img: https://www.mediafire.com/?87v1klu51476cqf Help me, give It a look if You can, thanks bro..
alray said:
Ok I understand now, you are looking for your original CID and MID. These values are stored on the MFG partition which is p6 on the M7. The M8 does not have the same partition layout as the M7. From what I can see from another thread, the MFG partition for the M8 is located at p5 not p6. So dump your p5 partition and then open it using HxD, hit control+F to open the search box and type "0P6B", should bring you to the lines where you can see your original MID. The original CID, Serial number, IMEI, Manufacturing date etc... should all be in the same spot (if the M8 MFG structure is similar to the M7). If you're not sure you can pm me a link to your p5 and I'll take a look for you.
I'm assuming that if you are doing all this, you already have double checked your APN settings, your SIM card and also called your provider to make sure everything was fine on their side?
Click to expand...
Click to collapse
redpoint73 said:
Might be making this more complicated than it needs to be:
1) What is your exact purpose in finding the "original" MID, CID? If its simply to find the proper RUU or firmware, its somewhat irrelevant. All the "GSM" M8 versions are identical in hardware. So unless you have a CDMA variant (Verizon, Sprint) you can use almost any RUU, firmware, since you are SuperCID and s-off.
2) May be able to determine the original version by looking at the product ID (or at least narrow down the possibilities). So I'd like to see the fastboot getvar out, as requested by a previous response (delete IMEI and serial number before posting).
3) If the intent is merely to determine the LTE band support, all you need to look at is the firmware number. Again, we need to see fastboot getvar output. Band support is determined by firmware, so its not relevant what the "original" CID,MID were. Just the current firmware number.
4) Model number on back cover may give a clue, what does it say? Although we've seen a good number of back covers replaced to remove carrier logos (usually US carrier logos in particular). So its hardly conclusive. But it may be another clue.
Note that if you do have a CDMA variant (Sprint, Verizon) you should not flash another versions RUU or firmware in an attempt to "convert" to another version, or modify band support. Doing so may result in a permanent radio brick. So again, we really need to see fastboot getvar output, in order to determine how to proceed.
Click to expand...
Click to collapse
1) I bought this phone already used from another person and He gived to me already S-off, rooter, with twrp, cm14.1, MID and CID already changed ecc. So, I cant realize what are the LTE Bands used from my phone (I think USA LTE Bands);
2)
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.1540.4
(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: 0P6B10\x000
(bootloader) cidnum: HTC__001
(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
But I have changed now superCID to > HTC_001
3) Look at answer #2.
4) My back cover is empty, Only the text "HTC" at the center of the cover is written.
Bro, I already know that if I flash a different RUU, I will brick my phone. I already flashed last RUU for EU Version through an .exe file, and if I write on dialer *#*#4636#*#*, I go phone information, I click on 3dot menu in the upper right and I do another click on 'Select radio's bands', I can only select 'Automatic' and 'USA Band'.. and if I flash EU RUU, Firmware, Radio ecc the phone works normalli without a problem, the only thing that doesnt works is 4g/lte. What's wrong with my HTC?
Francesco0301 said:
(bootloader) version-main: 6.12.1540.4
(bootloader) modelid: 0P6B10\x000
Click to expand...
Click to collapse
The main version number indicates the phone is running the firmware and radio baseband for the US Developer's Edition (which also is the same band support at the AT&T version). That version supports LTE bands 2, 4, 5, 7 and 17. You haven't mentioned what LTE band (or bands) your carrier uses for LTE.
Although it should be mentioned, that we've seen many cases where a phone "converted" to the proper band support, will sometimes still not get LTE service. I haven't seen a satisfactory explanation or fix for this. But just keep in mind, that even with the proper band support, it is still possible you will not have LTE.
The model number looks weird. I've never seen the characters "\x" as part of the model ID. It looks like an error may have been made while trying to modify it?
It would have been better to leave the phone SuperCID. With SuperCID, the MID check is bypassed, so it doesn't matter what the MID is. There is no benefit to having the WWE CID versus SuperCID.
Francesco0301 said:
4) My back cover is empty, Only the text "HTC" at the center of the cover is written.
Click to expand...
Click to collapse
There is no small gray/silver print near the bottom of the back cover?
Again, its not that critical what the back cover says; as we often see them replaced. But its more of a curiosity question.
Francesco0301 said:
Bro, I already know that if I flash a different RUU, I will brick my phone.
Click to expand...
Click to collapse
This statement taken literally, is incorrect; or at least incomplete. If you mean flashing RUU for another hardware, or the CDMA version, than that is a completely different statement. You can flash RUU for most other GSM M8 versions, without harm to the phone.
Francesco0301 said:
I already flashed last RUU for EU Version through an .exe file
and if I flash EU RUU, Firmware, Radio ecc the phone works normalli without a problem, the only thing that doesnt works is 4g/lte.
Click to expand...
Click to collapse
The EU RUU and/or firmware did not flash properly. Otherwise, the main version in getvar would have changed to 6.12.401.4 for Marshmallow. It would be changed to something with "401" in it, which explicitly means the EU version.
Did you get any error messages when flashing the EU RUU? I would expect it to fail the MID check, since your MID looks like its incorrect format.
Also, what RUU (or RUUs) and firmware did you try (exact file names, and links)? Because I've never seen a .exe format of the EU RUU (only a zip version of the MM RUU).
redpoint73 said:
The main version number indicates the phone is running the firmware and radio baseband for the US Developer's Edition (which also is the same band support at the AT&T version). That version supports LTE bands 2, 4, 5, 7 and 17. You haven't mentioned what LTE band (or bands) your carrier uses for LTE.
Although it should be mentioned, that we've seen many cases where a phone "converted" to the proper band support, will sometimes still not get LTE service. I haven't seen a satisfactory explanation or fix for this. But just keep in mind, that even with the proper band support, it is still possible you will not have LTE.
The model number looks weird. I've never seen the characters "\x" as part of the model ID. It looks like an error may have been made while trying to modify it?
It would have been better to leave the phone SuperCID. With SuperCID, the MID check is bypassed, so it doesn't matter what the MID is. There is no benefit to having the WWE CID versus SuperCID.
There is no small gray/silver print near the bottom of the back cover?
Again, its not that critical what the back cover says; as we often see them replaced. But its more of a curiosity question.
This statement taken literally, is incorrect; or at least incomplete. If you mean flashing RUU for another hardware, or the CDMA version, than that is a completely different statement. You can flash RUU for most other GSM M8 versions, without harm to the phone.
The EU RUU and/or firmware did not flash properly. Otherwise, the main version in getvar would have changed to 6.12.401.4 for Marshmallow. It would be changed to something with "401" in it, which explicitly means the EU version.
Did you get any error messages when flashing the EU RUU? I would expect it to fail the MID check, since your MID looks like its incorrect format.
Also, what RUU (or RUUs) and firmware did you try (exact file names, and links)? Because I've never seen a .exe format of the EU RUU (only a zip version of the MM RUU).
Click to expand...
Click to collapse
I've used an app that can determine what bands I can use, and they are bands that can used in Canada. This is the file that I used to flash RUU: https://www.androidfilehost.com/?fid=24269982087015187 Simply this application, do all the steps automatically for flashing RUU and It incorporate a RUU firmware. 0P6B10\x000 stay for 0P6B10000, its a binary's alghoritm, I have already read this thing in another forum.
Francesco0301 said:
I've used an app that can determine what bands I can use, and they are bands that can used in Canada. .
Click to expand...
Click to collapse
This isn't specific enough. Each carrier in Canada uses different LTE bands, its not standardized for the whole country:
http://www.worldtimezone.com/gsm.html
Francesco0301 said:
This is the file that I used to flash RUU: https://www.androidfilehost.com/?fid=24269982087015187 Simply this application, do all the steps automatically for flashing RUU and It incorporate a RUU firmware.
Click to expand...
Click to collapse
This isn't the Euro RUU (you stated Euro RUU in previous post). Its the US Developer's Edition RUU. But it may be sufficient (as far as band support) depending on what carrier you use specifically, and which exact LTE bands are needed.
Francesco0301 said:
0P6B10\x000 stay for 0P6B10000, its a binary's alghoritm, I have already read this thing in another forum.
Click to expand...
Click to collapse
Incorrect. The command to modify the MID utilizes a binary code. But it should be displayed as 0P6B10000 in getvar.
The command was not executed properly. I don't need another forum, to know this:http://forum.xda-developers.com/showthread.php?t=2708581
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 freeYou 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 freeYou 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:
Guys, my htc one m8 tmobile op6b130 ( bootloader looked, s-off) current software 4.16.1540.8. ... It does not install the update and says that i must revert back to original system software because it is modified version.
so please guide me how to get it done.. how do i install the update. Thanks
What do you mean by software number (where are you reading the nubmer)? Best thing to go by, is the OS number listed on the bootloader screen.
Also, an OTA will fail if the phone is rooted, custom ROM, or even unrooted (needs to be a never rooted stock ROM).
If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Otherwise, did you change the CID or MID (and know what they currently are)?
Bootloader screen is like
Software status official
***locked*** S -off
cid -11111111
OS 4.16.1540.8
The model written at rear bottom of my htc is Op6b130 .
i get update with a number 4.17.1540.9 which does not install.
Thats the real confusion with me .. so please tell me the way how do i install the next updates.
mfaizi16 said:
Bootloader screen is like
Software status official
***locked*** S -off
cid -11111111
OS 4.16.1540.8
The model written at rear bottom of my htc is Op6b130 .
i get update with a number 4.17.1540.9 which does not install.
Thats the real confusion with me .. so please tell me the way how do i install the next updates.
Click to expand...
Click to collapse
The phone is heavily modified. It has some point been rooted, SuperCID (11111111) and had the US Developers Edition (4.16.1540.8) firmware and/or RUU applied.
Do you know the history of these mods; did you do them, or did someone else mod the phone?
Can't say for certain, unless I know more details. But the easiest way to update to the latest (MM) version may be to flash 6.12.1540.4 firmware, then flash the 6.12.1540.4 RUU.
I did not do anything like that. I got my htc in this form.
so if MM update is better. Can you please tell me the procedure of installing firmware and ruu file as you said. I would be very grateful to you for this.
Would this procedure be right for me?
https://forum.xda-developers.com/ht...uide-htc-one-m8-to-developer-edition-t3331854
mfaizi16 said:
Would this procedure be right for me?
https://forum.xda-developers.com/ht...uide-htc-one-m8-to-developer-edition-t3331854
Click to expand...
Click to collapse
Yes, that would actually work, and describes what I was talking about. Nice work finding it yourself!
I'm not sure whether you need to change the MID or not. CID is fine to run the 6.12.1540.4 firmware and RUU. And SuperCID will actually bypass the MID in some situations (but not all). Plus, with the info given so far, I can't tell what the current MID is (it may already have been changed).
If you do need to change the MID, you will also need root. So that would be more steps.
So my advice is to first skip the steps of changing CID and MID. Just go to the steps of flashing the 6.12.1540.4 firmware and RUU. If the firmware fails due to wrong MID, it will tell you that via an error message; and we can tackle that issue if it comes up. But if it works on the current MID, then we've saved some steps.
Best (most accurate) way to determine the current MID, is to do command: fastboot getvar all
Then post the output (delete IMEI and serial number before posting).
This will also give us a lot more useful info on the device.
You'll need to use fastboot anyway (for the guide you linked), if you don't already know how. So you may as well figure it out now. The command should also work with the htc fastboot given in the thread you linked, but would be: htc_fastboot getvar all
in fastboot getvar all ... i got
version bootloader: 3.19.0.0000
version baseband: 1.24.21331147A1.09G
version cpld: none
version microp: noone
version mics: pvt ship s-off
meid: 00000000000000
Os : 4.16.1540.8
product: m8_ul
platform: hTCBmsm8974
modelid: OP6B13000
cidnum: 11111111
partition layout: generic
security: off
buld mode: ship
boot mode: fastboot
mfaizi16 said:
in fastboot getvar all ... i got
version bootloader: 3.19.0.0000
version baseband: 1.24.21331147A1.09G
version cpld: none
version microp: noone
version mics: pvt ship s-off
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: OP6B13000
cidnum: 11111111
partition layout: generic
security: off
buld mode: ship
boot mode: fastboot
Click to expand...
Click to collapse
Good to go with 6.12.1540.4 flashing from the guide you linked
Flash the firmware.zip in RUU mode then reboot to bootloader make sure the new os number is 6.12.1540.4 then proceed to flash the RUU.exe
Good luck
Sent from my HTC M8 using XDA Labs
do I need to change Cid & Mid?
when i typed adb.exe shell .. it gave me error that no device is there .
although it showed me my serial number when typed adb devices. it ran fine.
but what's the problem with adb.exe shell?
secondly, is it ok to jump from 4.16.1540.8 to directly 6.12.1540.4?
mfaizi16 said:
do I need to change Cid & Mid?
when i typed adb.exe shell .. it gave me error that no device is there .
although it showed me my serial number when typed adb devices. it ran fine.
but what's the problem with adb.exe shell?
Click to expand...
Click to collapse
no need to change anything you have supercid and the right mid,it will pass the check
it's "adb shell" not "adb.exe shell"
---------- Post added at 07:43 PM ---------- Previous post was at 07:42 PM ----------
mfaizi16 said:
secondly, is it ok to jump from 4.16.1540.8 to directly 6.12.1540.4?
Click to expand...
Click to collapse
yes but use the steps in the guide flash firmware.zip then flash the RUU.exe
While flashing ruu file, when I typed fastboot flash zip rom.zip
It said that targeted maximum download reported 1825********* bytes.
And my pc stucks there and htc stuck there with htc logo..
So what do i do now?
mfaizi16 said:
While flashing ruu file, when I typed fastboot flash zip rom.zip
It said that targeted maximum download reported 1825********* bytes.
And my pc stucks there and htc stuck there with htc logo..
So what do i do now?
Click to expand...
Click to collapse
try another usb port ( use usb 2 not 3 ) and make sure the drivers are installed properly
mfaizi16 said:
While flashing ruu file, when I typed fastboot flash zip rom.zip
It said that targeted maximum download reported 1825********* bytes.
Click to expand...
Click to collapse
You need to use the htc_fastboot to flash the RUU, as indicated in the guide you linked (and required files downloaded from there as well). The "generic" Android fastboot can't handle files that big.
Although, you should drop the ".exe" (indicated in the guide) from all the fastboot commands. I've never seen ".exe" included on fastboot and adb commands, and it will probably cause you an error like it did when flashing firmware. So the command should be:
htc_fastboot oem rebootRUU
htc_fastboot flash zip rom.zip
---------- Post added at 09:51 AM ---------- Previous post was at 09:47 AM ----------
mfaizi16 said:
secondly, is it ok to jump from 4.16.1540.8 to directly 6.12.1540.4?
Click to expand...
Click to collapse
Yes, that is fine. Which is why I told you to do it. If anything else needed to be done, I would have indicated that.
RUU doesn't need to be installed in sequence, meaning you can skip a version(s). RUU is different from OTA, as OTA typically does need to be installed in sequence.
With s-off, you can even go backwards with RUU. Which is also something you can't do with OTA.
while flashing firmware , it first said 'failed' and then automatically came with 'finished and time' .
When i went to ruu .. i first used htc_command .. but it said that ' this command is not in internal and external blaa blaa'. So i went without htc_ and got stuck and waited about half hour for that. Then , knowing nothing i did factory reset with wipe cache to restore my phone back to 4.16.1540.8.
Are there any pre-requisites that phone shold be unlocked and rooted (as i saw some videos on youtube)?
My phone is s-off, bootloader locked and no root access.
mfaizi16 said:
while flashing firmware , it first said 'failed' and then automatically came with 'finished and time' .
Click to expand...
Click to collapse
If it gave a message about "flush image immediately" this just means you need to flash the firmware again (needing to flash 2 times is normal and expected).
If the firmware installed correctly, you will see OS 6.12.1540.4 on the bootloader screen, and also see 6.12.1540.4 for "version-main" if you do fastboot getvar all.
You must have 6.12.1540.4 firmware properly installed, in order to flash the RUU.
mfaizi16 said:
When i went to ruu .. i first used htc_command .. but it said that ' this command is not in internal and external blaa blaa'.
Click to expand...
Click to collapse
You are getting that message, since you are not executing the command from the folder where htc_fastboot.exe is located. After you download htc_fastboot from the thread you linked, open Command Prompt in the folder (Left Shift + Right Mouse Click) and run the commands.
Leaving off the "htc" means you are trying to use the "generic" fastboot tool (fastboot.exe). Which would also confirm the fact you are probably running the command from the wrong folder. Again, using the regular fastboot will never work, since it can't handle the file size of the RUU.
mfaizi16 said:
Are there any pre-requisites that phone shold be unlocked and rooted (as i saw some videos on youtube)?
My phone is s-off, bootloader locked and no root access.
Click to expand...
Click to collapse
You mean prerequisites for the RUU? If so, saying bootloader unlocked and rooted are prerequisites is false and incorrect. If you saw it on a YouTube, you are confusing RUU with something else.
Bootloader locked is normally (s-on) a requirement for RUU. But since you are s-off, it will run with the bootloader unlocked, locked or relocked.
Root has no effect on RUU. RUU will run, whether the phone is rooted or not.
---------- Post added at 11:43 AM ---------- Previous post was at 11:41 AM ----------
mfaizi16 said:
Then , knowing nothing i did factory reset with wipe cache to restore my phone back to 4.16.1540.8.
Click to expand...
Click to collapse
What exactly are you trying to "restore" or accomplish with this? It's not clear you have even installed anything past 4.16.1540.8, to begin with.
Finally did it successfully!
Thank you everyone for guiding me.
redpoint73 said:
What do you mean by software number (where are you reading the nubmer)? Best thing to go by, is the OS number listed on the bootloader screen.
Also, an OTA will fail if the phone is rooted, custom ROM, or even unrooted (needs to be a never rooted stock ROM).
If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Otherwise, did you change the CID or MID (and know what they currently are)?
Click to expand...
Click to collapse
Hi I can see you are kind on HTC M8. Can you help me? My phone don't see updates. It sprint version.
The was changed to super cid. HTC sync manager don't recognise it Nobody from HTC can help me. They don't know what to do.
pablo_com said:
Hi I can see you are kind on HTC M8. Can you help me? My phone don't see updates. It sprint version.
The was changed to super cid. HTC sync manager don't recognise it Nobody from HTC can help me. They don't know what to do.
Click to expand...
Click to collapse
If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Basically, Sprint (and most US carrier versions of the M8) won't update if not connected to that actual US carrier (Sprint, in your case). Also, you can NOT "modify" the Sprint version to make it another version (such as Euro), and the reason for that is that the Sprint version you will radio brick the device doing this! So don't try it!
You can update using the RUU meant for the Sprint M8 (and only the RUU meant for the Sprint M8, for the reason mentioned above). Whether you need to update or not (by RUU) depends on what it says in the getvar info I asked for above.