Related
Hi all,
I have One X purchased in China, but did not write initial software # and CID # before unlocked it. Then all the data was lost due to system and sdcard format. No backup was made.
Current ## are:
CID (got by "readcid" command) 02__001
Software 3.37.1400.11
radio 1.1204.104.14
HBOOT 0.96
Tried many RUU images: Asia, Europe, China, always get error #131
Could someone help to find right RUU image software?
That version-main doesn't exist!
You could try the latest RUU for O2__001.
hi every one
i have a desire 616 with mediatek chip , and i want to change default cid !!
default cid : htc_038
i changed default cid to htc_J15 from this path : system/htc resource/default cid , but after factory reset my device shown below error:
nv cid is modifed to a invalid value
-----------------------------------------------
current cid : Htc_038
nvm cid : A07
valid cid: HTC_038, HTC_059, HTC_044, HTC_622
nvm cid is invalid, if yes ,it will do factory reset and apply the current cid HTC_038 to replace.
Click to expand...
Click to collapse
when i press ok my device do factory reset but the problem remains and again shown top errors .
whats problem ?
how to change default cid correctly ?
i just bought HTC M8 Days ago but it was pre rooted and on the 5.0.1 i cant update it to marshamllow
it S-Off and when i try to update it says you have the latest update
Software number
4.18.708.12
i tried to install OTA Flash via stock recovery but i got error
how i updaate manually or enable OTA's
dont wanna root now
please help me here
You can't install OTA on rooted ROM ... it needs pure non-rooted stock ROM.
You can try to restore only the system partition from non-rooted backup.
You can get the backup and stock recovery for 4.18.708.12 here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
i deleted root before doing any thing
can i do it without rooting or unlocking bootloader because i dont know how to do it on HTC Phone and those CID and stuff really bug me out
itried flashing ota with stock recovery got this error
http://prntscr.com/bivh4o
whats wrong here ?
Why on post #1 you said you have HKG 4.18.708.12
But in your screenshot you tried to install EU 6.12.401.4 OTA
and it failed because your stock recovery is TMOB US.
Post here fastboot getvar all result without serial & imei no.
We need to make sure the correct version that you have.
ckpv5 said:
Why on post #1 you said you have HKG 4.18.708.12
But in your screenshot you tried to install EU 6.12.401.4 OTA
and it failed because your stock recovery is TMOB US.
Post here fastboot getvar all result without serial & imei no.
We need to make sure the correct version that you have.
Click to expand...
Click to collapse
which one shoud i download
look at this photo
https://scontent-cai1-1.xx.fbcdn.ne...=ff0997ed8a4598b2c6cfe73d1dc0fc42&oe=576EED9B
iDuc said:
which one shoud i download
look at this photo
https://scontent-cai1-1.xx.fbcdn.ne...=ff0997ed8a4598b2c6cfe73d1dc0fc42&oe=576EED9B
Click to expand...
Click to collapse
The photo is not helpful enough.
One more time I request for fastboot getvar all result.
You may need this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
Htc one m8 not getting the OTA marshmallow
Hey i have htc one m8 running 4.4.4 and i am not getting the OTA update so i searched ur site and first of all i run a command fastboot getvar it says that my phone version is 0P6B130 and carrier is T-mobile so i downloaded the ruu from htc.com for t mobile and try to install but nothing happens and then i searched more and more about mid and cid i installed a app from playstore it shows main cid is T-MOB010 but i red it in detail its shows two mids and two cids.my bootloader version is 3.19.0.0000 and s-off and its locked and status is official.
maincid:Htc_001
Modelid:0P6B10000
Bootloader:3.19.0.0000
Ro.cid:T-MOB010
Ro.mid:0P6B13000
I just wana update my phone to official marshmallow update dont wana root it.plz guide me or give me link for OTA update for my phone so i can install through its stock recovery. Thanks in advance
Demigodlovesu said:
Hey i have htc one m8 running 4.4.4 and i am not getting the OTA update so i searched ur site and first of all i run a command fastboot getvar it says that my phone version is 0P6B130 and carrier is T-mobile so i downloaded the ruu from htc.com for t mobile and try to install but nothing happens and then i searched more and more about mid and cid i installed a app from playstore it shows main cid is T-MOB010 but i red it in detail its shows two mids and two cids.my bootloader version is 3.19.0.0000 and s-off and its locked and status is official.
maincid:Htc_001
Modelid:0P6B10000
Bootloader:3.19.0.0000
Ro.cid:T-MOB010
Ro.mid:0P6B13000
I just wana update my phone to official marshmallow update dont wana root it.plz guide me or give me link for OTA update for my phone so i can install through its stock recovery. Thanks in advance
Click to expand...
Click to collapse
if the first cid and mid is the current now you can't flash Tmobile RUU
( there is a simple fix for this issue as you said your device is s-off but i'm afraid to say it,then you screw up )
so post the result of fastboot getvar all ( after removing serial and imei numbers ) to be certain what you need to do
and don't use an app to read cid and mid
Ok.i dont know how to add a image there so i am writing it
Version Bootloader 3.19.0.0000
VersionBaseband:1.21.21331147A1.19_2g
version Cpld:none
Version main: 3.28.401.6
Version misc pvt ship s-off
Meid 00000000000000
Product m8_ul
Platform htcBmsm8974
Modelid 0P6B13000
Cidnum 11111111
Partion layout generic
Security off
Buildmode SHIP
boot mode fastboot
Commitno-bootloader df77f8b7
Hbootpreupdate 11
Gencheckpt 0
Demigodlovesu said:
Ok.i dont know how to add a image there so i am writing it
Version Bootloader 3.19.0.0000
VersionBaseband:1.21.21331147A1.19_2g
version Cpld:none
Version main: 3.28.401.6
Version misc pvt ship s-off
Meid 00000000000000
Product m8_ul
Platform htcBmsm8974
Modelid 0P6B13000
Cidnum 11111111
Partion layout generic
Security off
Buildmode SHIP
boot mode fastboot
Commitno-bootloader df77f8b7
Hbootpreupdate 11
Gencheckpt 0
Click to expand...
Click to collapse
Are you located in US and on T-Mobile network ?
If no, I suggest you to change the MID to EU MID 0P6B10000 then install EU Marshmallow RUU.
Some say once you have SuperCID, there is no need to change MID as SuperCID will override MID but in my experience that will never happen (flashing a modded firmware.zip is different as it has almost all MID in its android-info.txt). Unless you MID is SuperMID, you need to change MID to EU if you want to install EU RUU.
You can follow this guide to change MID - https://forum.xda-developers.com/showthread.php?t=2708581
then install RUU - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
If yes, in US and on T-Mobile network, you need different approach.
I am in pakistan
Demigodlovesu said:
I am in pakistan
Click to expand...
Click to collapse
Then go for the option that I mentioned earlier.
First - change MID
Second - install RUU
Change MID
What you need to do .. boot to bootloader and install TWRP - maybe version 2.8.7.0 will do
https://dl.twrp.me/m8/
after you install TWRP - boot to recovery
Mount - system
then open command prompt from your adb/fastboot folder
then type
adb shell
follow by
Code:
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
don't write yourself the code, copy and paste
then type exit
select reboot menu, select bootloader
then install RUU
Edit : your bootloader is locked, relocked or unlocked ? If locked and relocked, you can't fastboot flash the TWRP in normal way.
Download this : https://forum.xda-developers.com/showpost.php?p=70439093&postcount=412
No worry about the OS no. that will be changed later once you install RUU
fastboot oem rebootRUU
fastboot flash zip 0P6BIMG.zip
fastboot reboot-bootloader
then follow with the above to change MID
Install RUU
Follow this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
There is something i didnt mention earlier i have ruu.exe for Tmobile htc one m8 which i downloaded from htc.com and when i try to install it nothing happens why is that?
Demigodlovesu said:
i have ruu.exe for Tmobile htc one m8 which i downloaded from htc.com and when i try to install it nothing happens why is that?
Click to expand...
Click to collapse
Not enough info to say, for sure.
Which RUU number?
Exactly where does it get stuck? Any error messages?
After double clicking the ruu the installaion wizard pops up and after selecting the next option the installion bar goes to full and after that installion wizard vanishes and nothing happens.
Demigodlovesu said:
After double clicking the ruu the installaion wizard pops up and after selecting the next option the installion bar goes to full and after that installion wizard vanishes and nothing happens.
Click to expand...
Click to collapse
You didn't answer all the questions, what RUU number?
6.20.531.5
Demigodlovesu said:
6.20.531.5
Click to expand...
Click to collapse
RUU problems are usually on the PC end. Try a different USB port, or different cable. Try to re-install HTC Sync and HTC drivers.
Thanks man.you are a great help ?
I managed to run a ruu.now it is giving a error 155 unkown error and its says please find a correct ruu?
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:
I have M8 sprint version, M8_WHL. the mobile is stuck on logo and whenever I try to flash it; it fails due to wrong Model ID (MID).
Here the info of the device:
Security status: S-OFF
Model Id: 0P6B10\x000���������������������
Custom Id: 11111111 (ALL)
Serial number: HT446SF00917
Product: m8_whl
IMEI: XXXXXXXXXXXXXXXX
Platform: hTCBmsm8974
Bootloader ver: 3.19.0.0000
Baseband ver: 1.08.20.0916
Cpld verersion: None
Microp version: None
Main version: 2.16.654.4
Battery Status: good
Battery Volt: 0mV
PartitionLayout: Generic
Commitno bl: 8a0f02ff
Hbootpreupdate: 11
--------------------
Now what to do, I thought about reflashing Hboot 3.19 or only modify the MID but didn't find the way, I'd really appreciat your help
mohammedsh9124 said:
I thought about reflashing Hboot 3.19 or only modify the MID but didn't find the way
Click to expand...
Click to collapse
Did you try to modify the MID (and made it the way it is), or was it done by someone else?
Flashing HBoot won't fix the MID, if that is what your thinking was. Did you try the adb command to make it back to the Sprint MID?
I've seen some folks with the Sprint M8, with similar issue, with the MID is corrupt or weird or whatever you might call this situation. And I don't think there was a solution found. Trying to change the MID with adb failed in the situations I've read.
One workaround might be to unlock the bootloader (if not already - does it say UNLOCKED, RELOCKED or LOCKED on the bootloader screen?) flash TWRP and restore a 2.16.654.4 stock backup, if you can find one. Or a 2.xx based custom ROM intended for Sprint. You might get the phone back up and working that way, although it will still be on Kitkat.
Or you can try one of the modified firmware 6.20.651.3 zips, to see if they will flash. Although I'm thinking those might still fail MID check. But if it did work, your firmware would be updated to Marshmallow, and you can then restore a stock Sprint MM backup (6.20.651.3 ), or MM custom ROM for Sprint. https://forum.xda-developers.com/showthread.php?t=2729173
So the short story, I don't know if the MID can be fixed. But you can probably get the phone back up and running.
redpoint73 said:
Did you try to modify the MID (and made it the way it is), or was it done by someone else?
Flashing HBoot won't fix the MID, if that is what your thinking was. Did you try the adb command to make it back to the Sprint MID?
I've seen some folks with the Sprint M8, with similar issue, with the MID is corrupt or weird or whatever you might call this situation. And I don't think there was a solution found. Trying to change the MID with adb failed in the situations I've read.
One workaround might be to unlock the bootloader (if not already - does it say UNLOCKED, RELOCKED or LOCKED on the bootloader screen?) flash TWRP and restore a 2.16.654.4 stock backup, if you can find one. Or a 2.xx based custom ROM intended for Sprint. You might get the phone back up and working that way, although it will still be on Kitkat.
Or you can try one of the modified firmware 6.20.651.3 zips, to see if they will flash. Although I'm thinking those might still fail MID check. But if it did work, your firmware would be updated to Marshmallow, and you can then restore a stock Sprint MM backup (6.20.651.3 ), or MM custom ROM for Sprint. https://forum.xda-developers.com/showthread.php?t=2729173
So the short story, I don't know if the MID can be fixed. But you can probably get the phone back up and running.
Click to expand...
Click to collapse
thx for reply Mr.redpoint73, I've unlocked the bootloader and flashed twrp with supersu, and tried to modify MID via adb but no success, now I got simple question, which stock backup can I restore, should it be the same exact version or any other kitkact backup ?
https://forum.xda-developers.com/showthread.php?t=2701376
http://forum.gsmhosting.com/vbb/f485/htc-m8-collection-stock-backups-1882892/
There are a lot of backups, but all for m8_ul not sprint, I don't know if some may work ?
mohammedsh9124 said:
tried to modify MID via adb but no success
Click to expand...
Click to collapse
What does this mean specifically? Did you use the command for the Sprint MID, or otherwise? What was the result: did it say it was successful, or was there an error code, etc. Clearly the MID didn't change, so I realize that much. But it may help to know the rest.
---------- Post added at 09:24 AM ---------- Previous post was at 09:13 AM ----------
mohammedsh9124 said:
There are a lot of backups, but all for m8_ul not sprint, I don't know if some may work ?
Click to expand...
Click to collapse
They won't work. The Sprint M8 uses a different kernel, so you would need a backup or ROM intended specifically for they Sprint M8.
First, I'd like to see if you can run one of the "modified" 6.20.651.3 firmware zips from here (use fastboot method): https://forum.xda-developers.com/showthread.php?t=2729173
I'm hoping that since they are modified, they may not have the MID check. I'm not too optimistic, but it's worth a try.
Reason I want to try this, is that since you are still on Kitkat firmware, you will be limited to Sprint Kitkat ROMs, which is very limiting. Flashing anything but Kitkat will likely result in broken WiFi, extreme long boot, audio issues, etc.
So try flashing one of the modified 6.20.651.3 firmwares, and tell me whether it works or not (and the error message, if it doesn't work). If you get an error to "flush again immediately" that is a good thing, just use the command to flash the firmware again.
redpoint73 said:
I've seen some folks with the Sprint M8, with similar issue, with the MID is corrupt or weird or whatever you might call this situation. And I don't think there was a solution found. Trying to change the MID with adb failed in the situations I've read.
Click to expand...
Click to collapse
This usually happened because they personally wrote the code instead of copy paste the provided code
OP has this 0P6B10\x000��������������������� because the MID was intended to change from Sprint to EU but in the code, it was written \x but missing 00 where the correct one is \x00 means blank, the blank is needed in between digit & alphabet.
(Checked old thread - this \x happened when a space is there between codes - x00\ x30 when the correct one should be x00\x30)
So to write 0P6B10000 correctly
0 - \x30
blank - \x00
P - \x50
blank - \x00
6 - \x36
blank - \x00
B - \x42
blank - \x00
1 - \x31
blank - \x00
0 - \x30
blank - \x00
0 - \x30
blank - \x00
0 - \x30
blank - \x00
0 - \x30
so the full EU code is \x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30
I suggest OP to write the MID back to Sprint 0P6B70000
Copy & paste the 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
then advise the result. If there is some weird character after 0P6B70000, those weird character can be replace with a blank, then firmware will read 0P6B70000 and ignore the extra
Used to fix something like 0P6B100000000 back to 0P6B10000 by placing blank on those extra zero
ckpv5 said:
This usually happened because they personally wrote the code instead of copy paste the provided code
OP has this 0P6B10\x000��������������������� because the MID was intended to change from Sprint to EU but in the code, it was written \x but missing 00 where the correct one is \x00 means blank, the blank is needed in between digit & alphabet.
(Checked old thread - this \x happened when a space is there between codes - x00\ x30 when the correct one should be x00\x30)
So to write 0P6B10000 correctly
0 - \x30
blank - \x00
P - \x50
blank - \x00
6 - \x36
blank - \x00
B - \x42
blank - \x00
1 - \x31
blank - \x00
0 - \x30
blank - \x00
0 - \x30
blank - \x00
0 - \x30
blank - \x00
0 - \x30
so the full EU code is \x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30
I suggest OP to write the MID back to Sprint 0P6B70000
Copy & paste the 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
then advise the result. If there is some weird character after 0P6B70000, those weird character can be replace with a blank, then firmware will read 0P6B70000 and ignore the extra
Used to fix something like 0P6B100000000 back to 0P6B10000 by placing blank on those extra zero
Click to expand...
Click to collapse
The code worked for me via TWRP and restored the MID back to its original status, reflashed RUU and the phone is back to life.
Thx for your help