Well i have one htc one m8 from usa. Im in europe now. I need to change it to completely stock version. I dont really know whatbthat guy from whom i took the phone did on it, but im completely lost.
Its rooted with custom recovery and custom rom. I try many guides woth adb and staff and i fail.
If there is enybody who can guide me step by step will solve my problem.
Please help me.
First of all, there is a forum section for help and questions.
Secondly, what's the problem? You need to describe the problem (and provide specific details), if you want help.
Post more info, and I'll try to help; and also ask the mods to move this thread to the Q&A Help section.
Sorry about the thread on here and i beg mods to move it.
My problem is that i want to turn this mobile comepletely to stock version and ota updates.
p00tin said:
Well i have one htc one m8 from usa.
Click to expand...
Click to collapse
What version? If it Sprint or Verizon, you can't convert it.
If its T-Mobile US or AT&T, you can.
Or some smaller US carrier version?
p00tin said:
I try many guides woth adb and staff and i fail.
Click to expand...
Click to collapse
This statement doesn't tell us anything, and is close to useless.
What specific steps did you follow? What steps fail, or what is the specific result/issue?
You need to sort this out, since without adb/fastboot, you really can't do the conversion you want.
p00tin said:
If there is enybody who can guide me step by step will solve my problem.
Click to expand...
Click to collapse
I don't really do "step by step" but I'll help. I leave it up to the individual to do the proper learning, so they can actually understand and gain some knowledge instead of just being spoon fed (and much of the info is already well explained in guides).
In general, you need to:
1) Get adb/fastboot working (you need to provide the proper info before I can help)
2) s-off with sunshine app ($25 US license): http://theroot.ninja/
3) Change CID and MID to the version desired: http://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
4) Run the desired RUU.
But as already mentioned, this depends on what version you have. Don't even try this with Sprint or Verizon. It won't work, and will probably brick the phone.
Its unbranded version not in belongs to any carrier as i search about it. The cid is WWE.
p00tin said:
Its unbranded version not in belongs to any carrier as i search about it. The cid is WWE.
Click to expand...
Click to collapse
I'm skeptical of both those statements.
Unbranded US versions do exist, but are fairly uncommon. Its more likely a branded version, that has had its branding removed.
"WWE" is not a valid CID. Where are you getting this from?
You need to get fastboot working, so you can give us getvar data, so we can get the proper info on what version this is.
I have flashboot working. How can i see the proper cid?
p00tin said:
I have flashboot working. How can i see the proper cid?
Click to expand...
Click to collapse
You aren't reading very carefully, are you? "flashboot" isn't a thing. Please use the correct terminology.
Use the command: fastboot getvar all
The command won't work if you type "flashboot" :crying:
Post the output, but be sure to delete your IMEI and serial number before posting, as these are private info.
I try all you recomend. Still nothing working. My cid is like i said wwe. Htc_001
Version 0.5
Version-bootloader 3.19.0.0000
Version l-baseband 1.24.21331147A1.09G
Version-cpld none
Version-microp none
Version misc PVT SHIP S-ON
Product m8_ul
Platform htcbmsm8974
Modelid 0P6B10000
Cidnum HTC__001
I try to change cid and mid but when i do command adb shell i get error that my device not found
p00tin said:
I try all you recomend.
Click to expand...
Click to collapse
No you didn't (at least not successfully). The phone is still s-on. You skipped (or tried and failed) the step of getting s-off.
This step is not optional. s-off is required to change CID and MID.
But read more below, as I'm not sure you need s-off, or to change the CID/MID.
p00tin said:
My cid is like i said wwe. Htc_001
Click to expand...
Click to collapse
First of all, you only said the CID was "WWE" which is just a description, and not an actual CID. You should have supplied the specific CID. WWE version has at least 15 different CIDs. When you ask for help, you need provide the info requested, and to be specific as possible.
Further, the CID as you typed it (Htc_001) is not correct. It needs to be in CAPS, 8 characters long, with 2 underscores: HTC__001
Most importantly, if the CID is in fact HTC__001, its already an unbranded Euro version, not US as you originally claimed. And if that is the case, you don't need to s-off or change the CID, MID.
Something doesn't seem right here. I need more information before we should proceed any further. You really need to do fastboot getvar all, and post the output (which I previously requested, but you chose to ignore). Be sure to delete IMEI and serial number before posting the getvar output.
I really need this data, before I can give you any further instructions.
Related
Hello guys,
I have my M8 bought from US, Verizon and I am living in Netherlands. The problems is that I cannot get the updates from Verizon because as you know is CDMA so I have been trying to find a way to convert my M8 Verzion into an international M8.
First step: I flashed @Mike1986's One_M8_2.22.401.4_odexed and everything workes on my phone, even wifi and I also receive notification about software updates, the only problem is that when I try to install that updates ( see the error in the attached image).
My question is : what do i need to modifiy to make the phone 100% international version ?
I have to mention that I have S-off already
Is your network carrier a cdma or gsm network? If it's gsm network, it will not work.
It's gsm.
Yes I read that it won't work if you are on a gsm network it will not work but technically Verizon M8 has the same hardware as the international version so logically it should be possible to convert it, I just don't know what do i need to do.
"logical" or not, the internal electronics are different in the radio section, so you will not be able to get it to work as you would like..
S0wL said:
It's gsm.
Yes I read that it won't work if you are on a gsm network it will not work but technically Verizon M8 has the same hardware as the international version so logically it should be possible to convert it, I just don't know what do i need to do.
Click to expand...
Click to collapse
I don't know much about Verizon and I maybe wrong but if it is a GSM and S-Off (as you mentioned that you flash mike's ROM and it works flawlessly and you received OTA) then what you need is the right combination of CID and MID.
For e.g an Intl GSM EU_WWE, the MID is 0P6B10000 and for CID you can make it SuperCID.
Check your current MID - command fastboot getvar mid
ckpv5 said:
I don't know much about Verizon and I maybe wrong but if it is a GSM and S-Off (as you mentioned that you flash mike's ROM and it works flawlessly and you received OTA) then what you need is the right combination of CID and MID.
For e.g an Intl GSM EU_WWE, the MID is 0P6B10000 and for CID you can make it SuperCID.
Check your current MID - command fastboot getvar mid
Click to expand...
Click to collapse
My MID is 0P6B20000
S0wL said:
My MID is 0P6B20000
Click to expand...
Click to collapse
Yeah, International version is 0P6B10000
S0wL said:
My MID is 0P6B20000
Click to expand...
Click to collapse
That's explained the error that you posted in your screenshot because the OTA expect that you have MID 0P6B10000
You can change MID as in this guide : http://forum.xda-developers.com/showthread.php?t=2708581
The only question is whether the conversion will really work or not. I have no idea about verizon so not so sure. I only assume it will work based on your own comment that said Mike's ROM works flawlessly on your device. If this is true, then it should work.
Damn...it's really late over here ... gotta go now... maybe someone else have better idea for you ... good luck
S0wL said:
My MID is 0P6B20000
Click to expand...
Click to collapse
You'll need to change your MID if you're trying for International WWE.
enter the following:
adb shell
su (if needed to get a # prompt)
Code:
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]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify 0P6B10000 for modelid
fastboot reboot
Credit for code goes to @scotty1223 [how to] change your MID without an eng bootloader
---------- Post added at 08:29 PM ---------- Previous post was at 08:29 PM ----------
ckpv5 said:
That's explained the error that you posted in your screenshot because the OTA expect that you have MID 0P6B10000
You can change MID as in this guide : http://forum.xda-developers.com/showthread.php?t=2708581
The only question is whether the conversion will really work or not. I have no idea about verizon so not so sure. I only assume it will work based on your own comment that said Mike's ROM works flawlessly on your device. If this is true, then it should work.
Damn...it's really late over here ... gotta go now... maybe someone else have better idea for you ... good luck
Click to expand...
Click to collapse
You keep jumping ahead of me by mere minutes
:good:
ckpv5 said:
That's explained the error that you posted in your screenshot because the OTA expect that you have MID 0P6B10000
You can change MID as in this guide : http://forum.xda-developers.com/showthread.php?t=2708581
The only question is whether the conversion will really work or not. I have no idea about verizon so not so sure. I only assume it will work based on your own comment that said Mike's ROM works flawlessly on your device. If this is true, then it should work.
Damn...it's really late over here ... gotta go now... maybe someone else have better idea for you ... good luck
Click to expand...
Click to collapse
Thanks, I changed MID, I will try now the software update to see what happens, I will be back with a reply
Q&A for [OTA] 1.32.401.15 + Firmware + NoRedText ABOOT + RUU
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [OTA] 1.32.401.15 + Firmware + NoRedText ABOOT + RUU. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
HTC One M9
Hello,
I wonder why the HBOOT is now called ABOOT with the One M9.. is it just because it`s new design.. or are there more changes that we should be careful with?
Thanks a lot
pipapoananas said:
Hello,
I wonder why the HBOOT is now called ABOOT with the One M9.. is it just because it`s new design.. or are there more changes that we should be careful with?
Thanks a lot
Click to expand...
Click to collapse
I think its mainly like the HBOOT on the M8, maybe only a name change, but i can't say, because i did not diff the files and i'm not really into digging into
bootloader images, i only do the needed edits and then i'm done.
Mismatched MID and CID
Hello. I just got S-off on my HTC one M9 Developer Edition in order to flash this firmware, but found (through getvar all) that my MID and CID are not the same. Why is this, and is there a way to fix it?
MID: OPJA11000
CID: BS_US002
BananaMasamune said:
Hello. I just got S-off on my HTC one M9 Developer Edition in order to flash this firmware, but found (through getvar all) that my MID and CID are not the same. Why is this, and is there a way to fix it?
MID: OPJA11000
CID: BS_US002
Click to expand...
Click to collapse
Of course they're not the same it wouldn't be good for your device if they were.
MID: a combination of numbers, letters and/or additional characters that identify your the device (as for example a HTC M9)
CID: a combination of numbers, letters and/or additional characters that identify the country of origin of your device and whether it's branded and sold by a carrier or not.
For example the MID and CID of an european M9 which is unbranded and sold in Germany are 0PJA10000 (that's a zero at the beginning not an O) and HTC__102.
Edit: Both, your MID and your CID, are the correct ones for the developer edition.
Sorry
Flippy498 said:
Of course they're not the same it wouldn't be good for your device if they were.
MID: a combination of numbers, letters and/or additional characters that identify your the device (as for example a HTC M9)
CID: a combination of numbers, letters and/or additional characters that identify the country of origin of your device and whether it's branded and sold by a carrier or not.
For example the MID and CID of an european M9 which is unbranded and sold in Germany are 0PJA10000 (that's a zero at the beginning not an O) and HTC__102.
Edit: Both, your MID and your CID, are the correct ones for the developer edition.
Click to expand...
Click to collapse
I didn't mean mismatched as in not the same, I meant as in unable to flash this firmware for that reason (that they do not match any provided MID or CID).
BananaMasamune said:
I didn't mean mismatched as in not the same, I meant as in unable to flash this firmware for that reason (that they do not match any provided MID or CID).
Click to expand...
Click to collapse
Ok, sorry for missunderstanding your post. Well, the x.xx.401.xx firmware versions are meant to be used on the international version of the M9 which can be identified by the supported MID and CIDs. You could change both IDs using fastboot commands but since the hardware of the U.S. variants is slightly different* I don't think it is a good idea to flash this firmware on your phone. In the worst case you might get a nice new paperweight if your phone is not compatible with that firmware. Besides I don't think it'll take too long until the official 1.40.xxx.xx firmware is going to be distributed via the OTA function of the stock HTC rom.
*Blame the fact that U.S. carriers use the CDMA network standard while most other parts of the world are using GSM.
Isn't it GSM?
Flippy498 said:
Ok, sorry for missunderstanding your post. Well, the x.xx.401.xx firmware versions are meant to be used on the international version of the M9 which can be identified by the supported MID and CIDs. You could change both IDs using fastboot commands but since the hardware of the U.S. variants is slightly different* I don't think it is a good idea to flash this firmware on your phone. In the worst case you might get a nice new paperweight if your phone is not compatible with that firmware. Besides I don't think it'll take too long until the official 1.40.xxx.xx firmware is going to be distributed via the OTA function of the stock HTC rom.
*Blame the fact that U.S. carriers use the CDMA network standard while most other parts of the world are using GSM.
Click to expand...
Click to collapse
Last I checked, only Verizon and Sprint are CDMA. Does Developer Edition include that functionality?
BananaMasamune said:
Last I checked, only Verizon and Sprint are CDMA. Does Developer Edition include that functionality?
Click to expand...
Click to collapse
Seems like you're right. As far as I read the developer edition is almost the same as the AT&T version which uses GSM. I thought every U.S. carrier uses CDMA. Nevertheless there must be a difference since your MID differs from the international one. If the hardware were the same there would be no need to use a different MID. Of course you could try installing the 1.40.401.xx firmware using the commands in the hide box but I cannot garantee that it will work or that your phone is still usable afterwards. I would actually suggest you to ask here whether you won't brick your phone by flashing the x.xx.401.xx version.
Code:
fastboot oem writecid <input desired CID without "<" and ">"here>
Code:
fastboot oem writemid <input desired MID without "<" and ">" here>
Edit: Seems like it won't "hurt" your phone to convert it to the international version.
developer editions on GSM
Hi all
i am wondering if the 1.32.617.30 developer firmware and RUU stuff will work on a GSM phone or more to the point a European phone.
The phone in question is mine it is unlocked and s-off and on super sid i just wanna make sure i still get phones call and stuff
any help or advise would be great
thanks guys
Hi thabks..is there any release date for the internatuonal 2.10 ruu??
Hi guys, need help here
I relocked my M9 and make it S-ON. im using firmware 2.7.401.1 I cannot install from any RUU, it seems there is no RUU that match with my firmware. I make mistake should S-ON the device later, but i already did it, so now i cannot use the phone because there is no OS on it.
I try to unlock bootloader, and cannot retrieve the token when using fastboot oem get_identifier_token. I read that since 5.1 you need to turn on unlock option in developer options, but i cannot do that, since the OS is already wiped
Is there any solution for this ?
Thanks.
when will we have the ruu zip 2.10.401.1 so we may be able to apply the SDCARD method to have a full clean stock flash?
I would like to have flashed in this way instead of going all the hard way in flashing ruuzip stock 1.40 and then upgrading by ota´s.
Thanks for all efforts, Nepht Legion.
need help to remove red text
Hi,
I have a HTC m9 asian variant ( on the download menu i get 2.1.709.1) . I have an unlocked bootloader, twrp , root, S-off, supercid installed.
I am running Maximus 6.0 rom based on 2.1.401.
I need to get the red text removed and have tried all the mentioned ways via adb to no success. I have very limited knowledge in this area, Can someone please help me ?
Thanks in Advance.
hi peep's, can we downgrade firmware with s-on and locked boot-loader. or do i need s-off and unlocked boot-loader sorry noob to htc devices regard's Joe.
joecool666 said:
hi peep's, can we downgrade firmware with s-on and locked boot-loader. or do i need s-off and unlocked boot-loader sorry noob to htc devices regard's Joe.
Click to expand...
Click to collapse
hi, you need s-off and a locked bootloader to be able to do that
maxx2210 said:
hi, you need s-off and a locked bootloader to be able to do that
Click to expand...
Click to collapse
okay thanks for your time and help regard's Joe.
Hi All,
Apologies if this is the wrong thread to post this in, just wanted to find out if anyone else has tried to manual install an ota on a M9 s-off.
I copy it to my SD and select to install it via stock recovery. It checks the file and starts the update and not once have i spotted an error, but once it is back up and running android, it is still on the old version.
I'm currently trying to go from 2.10.401.1 to 2.10.401.180, and if I go to aboot, it actual says the new version, but the OS version is still the old.
I would seem that the system partition isn't being updated.
Is there something i'm doing wrong? I tried the usual, googling and searching xda, but haven't found a solution yet.
Thanks
Sent from my HTC One using Tapatalk
Anyone can tell me how to extract the firmware from an OTA zip so I could upgrade my M9 firmware while being S-on? Thank you
Sent from my HTC One M9 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=3378388
Sent from my HTC One M9 using XDA-Developers mobile app
Guys i am desperated and depressed i got this phone htc one m8 yesterday and since yesterday i am on it trying to fix it .
i unlock and root the phone and install skydragon custom rom on it wihout first backing up my custom rom ( so stupid of me ) with youtube video guide .. now the reason i wanna change this and go back to normal is because i cannot get 4g networks running for my mobile data on my device which it is for me annoying and at the same time very important .
So please i will give what information i can so you can guide me and give me the correct rom for my device please i will highly appreciated it
i went to my carrier shop today and took a screenshot of one of there m8 there custom rom info so i guess i need this
kernel version
3 4 0-g6af28ec
[email protected] #1
SMP PREEMPT
Baseband version
1.25.214500021.06G_20.684196t.01_F
build number
4.16.401.10 CL448934 release-keys
Please help me find this rom
thank you
First .. we need to know your device current hboot, CID, MID & etc.
Put your device in bootloader mode and connect to PC and open a command prompt from where you have your fastboot/adb files. then run this command in the command prompt
fastboot getvar all
copy the result and post here but delete the IMEI no & Serial no.
If you don't have fastboot/adb installed, read this : http://forum.xda-developers.com/showthread.php?t=2317790
ckpv5 said:
First .. we need to know your device current hboot, CID, MID & etc.
Put your device in bootloader mode and connect to PC and open a command prompt from where you have your fastboot/adb files. then run this command in the command prompt
fastboot getvar all
copy the result and post here but delete the IMEI no & Serial no.
If you don't have fastboot/adb installed, read this : http://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
here is what you asked thank you for you assistance
what is the next step please
Hmmm... m8_ul_ca ... means it's not a HKG device and not a EU device
If I'm not wrong m8_ul_ca is either AT&T or Developer Edition device. (m8_ul_ca I believe is a US device)
but previously S-Offed to change the MID to EU and SuperCID.
And that's explain your 4G problem in your country, most probably is the radio band version which I'm not familiar with.
@redpoint73 - can you help on this radio matter as you are more expert on this
You can try either using EU 4.16.401.10 RUU.exe - http://forum.xda-developers.com/showpost.php?p=56140330&postcount=1
you need to relock bootloader and make backup of your internal storage important data as this will wipe everything
Or you install latest TWRP and restore 4.16.401.10 backup (no need to relock bootloader)
then check whether your 4G is working or not.
ckpv5 said:
Hmmm... m8_ul_ca ... means it's not a HKG device and not a EU device
If I'm not wrong m8_ul_ca is either AT&T or Developer Edition device. (m8_ul_ca I believe is a US device)
but previously S-Offed to change the MID to EU and SuperCID.
And that's explain your 4G problem in your country, most probably is the radio band version which I'm not familiar with.
@redpoint73 - can you help on this radio matter as you are more expert on this
You can try either using EU 4.16.401.10 RUU.exe - http://forum.xda-developers.com/showpost.php?p=56140330&postcount=1
you need to relock bootloader and make backup of your internal storage important data as this will wipe everything
Or you install latest TWRP and restore 4.16.401.10 backup (no need to relock bootloader)
then check whether your 4G is working or not.
Click to expand...
Click to collapse
hey mate here what i found after a quick search on google and of caurse with your help and inspiration
http://droider.eu/2014/09/20/htc-one-m8-models/http://http://droider.eu/2014/09/20/htc-one-m8-models/
ckpv5 said:
Hmmm... m8_ul_ca ... means it's not a HKG device and not a EU device
If I'm not wrong m8_ul_ca is either AT&T or Developer Edition device. (m8_ul_ca I believe is a US device)
but previously S-Offed to change the MID to EU and SuperCID.
And that's explain your 4G problem in your country, most probably is the radio band version which I'm not familiar with.
@redpoint73 - can you help on this radio matter as you are more expert on this
You can try either using EU 4.16.401.10 RUU.exe - http://forum.xda-developers.com/showpost.php?p=56140330&postcount=1
you need to relock bootloader and make backup of your internal storage important data as this will wipe everything
Or you install latest TWRP and restore 4.16.401.10 backup (no need to relock bootloader)
then check whether your 4G is working or not.
Click to expand...
Click to collapse
so what we do with it now . how do install the latest twrp on my device i would like to try your second suggestion for my problem . when you mention to restore the 4.16.401.10 backup how do i do that ? sorry if i fur stated you .
at the end of this "toleration" if there is a way to say thank you and show my respect please let me know
italianveins said:
so what we do with it now . how do install the latest twrp on my device i would like to try your second suggestion for my problem . when you mention to restore the 4.16.401.10 backup how do i do that ? sorry if i fur stated you .
at the end of this "toleration" if there is a way to say thank you and show my respect please let me know
Click to expand...
Click to collapse
The how-to is in my thread that you posted before .. linked in my signature
my model on the back phone it is written like 0P6B110 so according to the website is australia if i am correct
italianveins said:
my model on the back phone it is written like 0P6B110 so according to the website is australia if i am correct
Click to expand...
Click to collapse
Not all Australia device has 0P6B110, Optus is 0P6B650
and mine an Asian one has 0P6B110 too. Eventhough that website say Taiwan has 0P6B150 but that is for m8_ul_tw because the regular Taiwan m8_ul is 0P6B110
So don't worry so much on this what written on the back because it's getting weird for a m8_ul_ca to have 0P6B110 instead of 0P6B120
ckpv5 said:
Not all Australia device has 0P6B110, Optus is 0P6B650
and mine an Asian one has 0P6B110 too. Eventhough that website say Taiwan has 0P6B150 but that is for m8_ul_tw because the regular Taiwan m8_ul is 0P6B110
So don't worry so much on this what written on the back because it's getting weird for a m8_ul_ca to have 0P6B110 instead of 0P6B120
Click to expand...
Click to collapse
i forgot to mention that the phone i bought it from ebay and it came from hong kong ... is that make any sense ?
is this any good ?
http://forum.xda-developers.com/showthread.php?t=2705292
With your current hboot, you should be able to run any lollipop ROM. You can give that ROM a try .. maybe some configuration in that ROM will help your radio (4G) problem.
ckpv5 said:
With your current hboot, you should be able to run any lollipop ROM. You can give that ROM a try .. maybe some configuration in that ROM will help your radio (4G) problem.
Click to expand...
Click to collapse
which one please can you link it here so i can download it and flash it and see if it's going to work ? thank you
ckpv5 said:
@redpoint73 - can you help on this radio matter as you are more expert on this
Click to expand...
Click to collapse
Coming from someone of your knowledge, I consider that quite a complement!
Ironically, the radio number is neither for AT&T or Dev Edition. But actually matches what is listed for the Euro RUU you linked:
ckpv5 said:
You can try either using EU 4.16.401.10 RUU.exe - http://forum.xda-developers.com/showpost.php?p=56140330&postcount=1
you need to relock bootloader and make backup of your internal storage important data as this will wipe everything
Click to expand...
Click to collapse
To the OP, what country are you in?
Who is your carrier, and do you know what LTE bands they use?
You asked about a ROM then you ask me to link a ROM ...
that's something that I cannot do because I don't use any of those custom ROMs as I'm on my own made ROM (including SkyDragon is part of my ROM).
I believe all ROMs are good. You just need to try all of them and see which is best suit you. SkyDragon you have 4G problem.. then try MaximusHD, LeeDroid, Viper, InsertCoin & etc.
Maybe try MaximusHD first as this is close to stock custom ROM so less modding/tweaking for you to handle.
You need to see whether 4G is working on this ROM then later try other ROM too ... that's all
ckpv5 said:
it's getting weird for a m8_ul_ca to have 0P6B110 instead of 0P6B120
Click to expand...
Click to collapse
I agree, its really strange the product ID (m8_ul_ca is for AT&T) does not match the MID (0P6B110) on back of the phone.
The phone was also likely s-off previously, as the CID was clearly changed (to SuperCID) and the MID listed in the getvar output is 0P6B100 (also probably changed by the previous owner).
redpoint73 said:
I agree, its really strange the product ID (m8_ul_ca is for AT&T) does not match the MID (0P6B110) on back of the phone.
The phone was also likely s-off previously, as the CID was clearly changed (to SuperCID) and the MID listed in the getvar output is 0P6B100 (also probably changed by the previous owner).
Click to expand...
Click to collapse
Yeah .. believe that's the case .. and I guess on the back of the phone it is written as M8x as 0P6B110 usually for M8x.
But product ID is m8_ul_ca suggests the back cover is most probably just a replacement cover.
ckpv5 said:
But product ID is m8_ul_ca suggests the back cover is most probably just a replacement cover.
Click to expand...
Click to collapse
Ah yes, a replacement cover, what makes much more sense now!
So its most likely an AT&T variant, with replacement back cover, that was previously s-off, changed to Euro MID, SuperCID, and Euro firmware flashed (maybe all Euro software before the OP started modding it).
I recommend again that the OP verify that his carrier is using bands that are supported by the Euro version (at least tell us what country, carrier, and what LTE bands that carrier uses, if known). My guess is "no" and in which case, OP will probably need to s-off and flash the proper radio that supports the required LTE bands.
redpoint73 said:
..... OP will probably need to s-off and flash the proper radio that supports the required LTE bands.
Click to expand...
Click to collapse
I always wonder if a device was S-Offed with SunShine by the previous owner, then the new owner use SunShine to S-Off again, I think the SunShine apk will run and will not request for payment.
What I know SunShine should work on the same device multiple times provided the motherboard is not changed.
Something for OP to try.
redpoint73 said:
Coming from someone of your knowledge, I consider that quite a complement!
Ironically, the radio number is neither for AT&T or Dev Edition. But actually matches what is listed for the Euro RUU you linked:
To the OP, what country are you in?
Who is your carrier, and do you know what LTE bands they use?
Click to expand...
Click to collapse
hello mate thank you for you time taken to help and reply on this . they do support here LTE ( 4G) and my carrier is MTN and i i live in cyprus . i think the band they use is 1900?? not too sure as i am not much into that
but i am under depression really i am willing to pay someone to get me the original custom rom for my phone and be out of this awful stress ;(
There's something that I'm a bit unclear on when it comes to RUUs
Let's say that I'd like to try out the latest Marshmallow release without waiting for the OTA and use the HTC-provided RUU .exe (3.35.617.12)
I'm on a T-Mobile branded M9 and would like to keep WiFi Calling and Visual Voicemail. If I find that I am unable to use these features in the non-branded HTC MM release, will I simply be able to use the T-Mobile branded RUU .exe (2.11.531.19) to revert back or will I be unable to as it's an older version (Android 5.1)
I'm currently still locked and S-ON
I seem to remember downgrades not being possible on my M7 once the hboot was updated to a newer version, but am a bit confused about the specifics of the M9
Thank you, and my apologies if this is a dumb question -- I've done my best to find an answer through searching
You cannot flash RUU that does not match your device variant. In this case, you would need 3.35.531.xx RUU, to try marshmallow. 3.35.617.xx won't install on your phone, unless you S-off and change the variant CID.
But once your phone is S-OFF then you are able to downgrade, too. (Although it doesn't matter whether you use a RUU.zip or a RUU.exe.)
asestar said:
You cannot flash RUU that does not match your device variant. In this case, you would need 3.35.531.xx RUU, to try marshmallow. 3.35.617.xx won't install on your phone, unless you S-off and change the variant CID.
Click to expand...
Click to collapse
Well, now I'm a bit confused as far as variants are concerned. This HTC release page states
This software upgrade comes in the form of two sequential updates. The first update will install software version 2.11.617.180 , which does not include the Android OS upgrades. The following update will install software version 3.35.617.12 , which includes the changes to the Android OS.
Click to expand...
Click to collapse
Am I correct in understanding now that the '617' portion of those two versions is what indicates the device variant? And that my device's variant is '531'?
So then it appears that the only ways for me to try out Marshmallow at this point would be:
1) Wait until HTC/T-Mobile unleash their official release and update via OTA or RUU
2) Unlock my bootloader, flash TWRP, and install whatever ROM I please
3) Unlock bootloader, S-OFF, and RUU as I please
Flippy498 said:
But once your phone is S-OFF then you are able to downgrade, too. (Although it doesn't matter whether you use a RUU.zip or a RUU.exe.)
Click to expand...
Click to collapse
And so long as I'm S-OFF I could use this particular T-Mobile RUU executable to revert back to stock at any point and then re-lock my bootloader, correct? But as long as I'm S-ON, then downgrading is not an option, even using an RUU of the '531' variant?
(bootloader) kernel: lk
(bootloader) product: htc_himaul
(bootloader) version: 1.0
(bootloader) imei: REDACTED
(bootloader) version-main: 2.11.531.19
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_86.09.50731G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA12000
(bootloader) cid: T-MOB010
Click to expand...
Click to collapse
Miguel_Lancaster said:
Am I correct in understanding now that the '617' portion of those two versions is what indicates the device variant? And that my device's variant is '531'?
Click to expand...
Click to collapse
Correct. 617 is the SKU for the unlocked/developer edition and 531 belongs to T-Mobile US.
Miguel_Lancaster said:
So then it appears that the only ways for me to try out Marshmallow at this point would be:
1) Wait until HTC/T-Mobile unleash their official release and update via OTA or RUU
2) Unlock my bootloader, flash TWRP, and install whatever ROM I please
3) Unlock bootloader, S-OFF, and RUU as I please
Click to expand...
Click to collapse
1) Correct.
2) You can't flash Android M Sense roms when your phone is using the Android L firmware. So you need to look for the Android L versions of the roms (e.g. ARHD 14.0 or Viper 3.5). Sense-less Android M roms like CM should be fine, though.
3) Correct.
Miguel_Lancaster said:
And so long as I'm S-OFF I could use this particular T-Mobile RUU executable to revert back to stock at any point and then re-lock my bootloader, correct? But as long as I'm S-ON, then downgrading is not an option, even using an RUU of the '531' variant?
Click to expand...
Click to collapse
Correct (both times). Although you should keep in mind that your phone will bootloop if it's not 100% stock and you lock or relock the bootloader. (I personally think there is no benefit in locking/re-locking or even setting S-OFF back to S-ON unless you want to send your phone to HTC for warranty claims.)
asestar said:
2) You can't flash Android M Sense roms when your phone is using the Android L firmware. So you need to look for the Android L versions of the roms (e.g. ARHD 14.0 or Viper 3.5). Sense-less Android M roms like CM should be fine, though.
3) Correct.
Click to expand...
Click to collapse
Hmm, and here I was thinking that ROMS included the firmware and both could be flashed through TWRP. Guess I was mistaken. Or...
asestar said:
Correct (both times). Although you should keep in mind that your phone will bootloop if it's not 100% stock and you lock or relock the bootloader. (I personally think there is no benefit in locking/re-locking or even setting S-OFF back to S-ON unless you want to send your phone to HTC for warranty claims.)
Click to expand...
Click to collapse
Phone was just purchased used, so if there's any warranty period left it probably isn't for very much longer. In the past I've gone S-OFF for all my HTC devices (Incredible, then One S, then One M7) but they've always seemed to have their own unique quirks and this M9 appears to be no different.
My main reasoning for staying S-ON/Stock at the moment is just in case I find a reason to return the device to the seller. After a few days when I'm sure everything is alright with it, I'm sure I'll be less reluctant to tweak.
Is a bootloop easily fixable?
So, to clarify (again!) --
In my phone's current state, I would be limited to Lollipop ROMs when flashing via TWRP?
So then, the shortest route to flashing custom Marshmallow ROMs would be to S-OFF and then RUU to an International Marshmallow firmware? Would I need to change CID manually or is that handled during RUU so long as I'm S-OFF?
And the safest route (in which S-OFF would be completely optional) would be to wait for the T-Mobile OTA release for Marshmallow before unlocking the bootloader and flashing TWRP?
Thanks a bunch for your responses. I'm sure this stuff gets answered all the time, but it can sometimes be difficult to find a specific answer in the depths of these boards. Plus, I find it hard to keep 100% on all development when I only buy a new device every couple of years.
I used the ARHD rom on my last device and quite liked it, but there was a T-Mobile specific variant that kept WiFi calling and all the other carrier-specific stuff. I'm pretty sure the developer has since long given up on maintaining those features., but it's my understanding that ViperOne may still have them.
Miguel_Lancaster said:
Hmm, and here I was thinking that ROMS included the firmware and both could be flashed through TWRP. Guess I was mistaken. Or...
Click to expand...
Click to collapse
The difference between rom and firmware.
Miguel_Lancaster said:
Is a bootloop easily fixable?
Click to expand...
Click to collapse
Just reflash a RUU. The problem for most non-US firmwares is that HTC doesn't provide RUUs so sometimes there is no freely accessible RUU for a specific firmware version. (The only other method besides flashing a RUU is restoring a TWRP backup or re-/flashing a custom rom which needs an unlocked bootloader and TWRP.) If someone decides to re-S-ON and to lock/relock and the rom doesn't boot then that person might not be able to fix that bootloop without this RUU service. (The same applies to S-ON users who decide to relock if the rom doesn't boot.) HTC introduced a new security feature with Android 5.1 (firmware 2.x and higher). It prevents the bootloader unlock if the option OEM Unlock isn't activated in developer options. That's why I recommend everyone staying S-OFF and unlocked unless you need to send your phone back to HTC for a warranty claim since even OTAs can be installed with an unlocked bootloader. Well, RUU.exe deny to flash with S-ON and an unlocked bootloader but there are not many RUU.exe for non-US firmware versions and you can always extract the RUU.zip from a RUU.exe. (RUU.zip files can be flashed via an external SD card even if the bootloader is unlocked.)
Miguel_Lancaster said:
In my phone's current state, I would be limited to Lollipop ROMs when flashing via TWRP?
Click to expand...
Click to collapse
Correct if you're talking about Sense roms.
Miguel_Lancaster said:
So then, the shortest route to flashing custom Marshmallow ROMs would be to S-OFF and then RUU to an International Marshmallow firmware? Would I need to change CID manually or is that handled during RUU so long as I'm S-OFF?
Click to expand...
Click to collapse
Or you use an unlocked/dev edition RUU. There is no big difference between the firmware of those two M9 versions. Nevertheless you need to change both the CID and the MID. The commands are fastboot oem writecid <enterwhicheverCIDisneeded> and fastboot oem writemid <enterwhicheverMIDisneeded>. (SKU 617 - unlocked/dev edition - CID: BS_US002 - MID: 0PJA11000; SKU 401 - international version - CID: HTC__001 - MID: 0PJA10000; SKU 531 - T-Mobile US - CID: T-MOB010 - MID: 0PJA12000)
Miguel_Lancaster said:
And the safest route (in which S-OFF would be completely optional) would be to wait for the T-Mobile OTA release for Marshmallow before unlocking the bootloader and flashing TWRP?
Click to expand...
Click to collapse
Correct.
Miguel_Lancaster said:
I used the ARHD rom on my last device and quite liked it, but there was a T-Mobile specific variant that kept WiFi calling and all the other carrier-specific stuff. I'm pretty sure the developer has since long given up on maintaining those features., but it's my understanding that ViperOne may still have them.
Click to expand...
Click to collapse
Don't know about ARHD but Viper has that feature.
Btw: Getting S-OFF is quite easy but it costs 25 USD. You simply need to use the Sunshine App. (Or you look for someone who has a java card.)
Thank you for taking the time to answer all of my questions.
No problem. Maybe those detailed answers might help other users as well. (That's at least what I hope. )
Flippy498 said:
Or you use an unlocked/dev edition RUU. There is no big difference between the firmware of those two M9 versions. Nevertheless you need to change both the CID and the MID. The commands are fastboot oem writecid <enterwhicheverCIDisneeded> and fastboot oem changemid <enterwhicheverMIDisneeded>. (SKU 617 - unlocked/dev edition - CID: BSUS_002 - MID: 0PJA11000; SKU 401 - international version - CID: HTC__001 - MID: 0PJA10000; SKU 531 - T-Mobile US - CID: T-MOB010 - MID: 0PJA12000)
Click to expand...
Click to collapse
**** --
I changed my MID to the Developer edition, but I accidentally used the letter O and not the number 0 -- so OPJA11000
Then I attempted an RUU and now my phone is stuck in the RUU screen and I can't even turn it off. Is there any way to recover this? I don't even think I can use ADB anymore.
edit: I got it to reboot by holding BOTH volume buttons and POWER. What a stupid mistake. I'll leave this here though so hopefully no one else does anything so stupid.
Yikes :silly:
edit 2: Hmm, changed MID to the correct value but I'm still getting ERROR 131 CUSTOMER ID ERROR during RUU. Will have to investigate this further. Maybe I need to relock the bootloader.
P.S. The command to change the MID actually seem to be writemid, not changemid -- figured that out through trial and error
edit 3: Relocking the bootloader still gives the same error RUU. Now I'm stumped.
edit 4: Turns out the CID should actually be BS_US002, not BSUS_002, as you told me in the earlier reply.
edit 5: Yup, fixing the CID solved the problem
Miguel_Lancaster said:
P.S. The command to change the MID actually seem to be writemid, not changemid -- figured that out through trial and error
Click to expand...
Click to collapse
Ah, sorry. I don't know why I wrote changemid. It wasn't intended. Of course it has to be writemid. I will correct the post.
Miguel_Lancaster said:
Turns out the CID should actually be BS_US002, not BSUS_002, as you told me in the earlier reply.
Click to expand...
Click to collapse
Sinc I don't know every CID by heart I copied it from a CID list I found with google. I'm going to correct that mistake, too. Thanks for clarifying.
Sorry for the hassle.
Flippy498 said:
Ah, sorry. I don't know why I wrote changemid. It wasn't intended. Of course it has to be writemid. I will correct the post.
Sinc I don't know every CID by heart I copied it from a CID list I found with google. I'm going to correct that mistake, too. Thanks for clarifying.
Sorry for the hassle.
Click to expand...
Click to collapse
I didn't brick anything and got it all figured out in the long run, so no worries. I may not have attempted this in the first place without everything explained so concisely by you earlier, so thank you. Hopefully this thread (mistakes and all) can be beneficial to others.
Seriously though, who decided it was a good idea to put a zero before 'PJA' for the CID? That's just asking for trouble.
Miguel_Lancaster said:
I didn't brick anything and got it all figured out in the long run, so no worries. I may not have attempted this in the first place without everything explained so concisely by you earlier, so thank you. Hopefully this thread (mistakes and all) can be beneficial to others.
Seriously though, who decided it was a good idea to put a zero before 'PJA' for the CID? That's just asking for trouble.
Click to expand...
Click to collapse
That whole "0" or "O" bull**** ...
Cost me 3 days of heartache getting errors...
Yeah....that structure is a horrible idea....g
modelid: 0P6B20000konoto
how to change the modelID of verizon one m8. adb method not working and i am stuck with this model id.
I want to convert it back to stock verizon. please help.
device is s off and bootloader is unlocked with latest firmware running on viperone m8
Hello
I had mounted the viperOne without backup m8 with tim cid, to return stock I had to find a tim backup with the same cid and installation is successful, need to change anything.
Why you have to change mid?
you have to change mid or cid?
however I'm not sure but they should s-off to make these changes, and the only way it should be app sunshine at 20€
Inviato dal mio HTC One_M8 utilizzando Tapatalk
---------- Post added at 08:58 AM ---------- Previous post was at 08:49 AM ----------
I found my backup there
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Inviato dal mio HTC One_M8 utilizzando Tapatalk
As I clearly mentioned I am talking about the MID here. My MID is messed up and I want the ways to repair it. aDB method ain't working.
P.S- I am on super cid so cid is not an issue
shkhr1 said:
aDB method ain't working.
Click to expand...
Click to collapse
What do you mean that it's not working? Did you get an error message? Do you have adb connectivity?
Did you change the MID in the first place (or was it done by someone else)? Changing the MID on the Verizon device is not a good idea. Nothing good can come from it. Folks usually change, in order to flash another version's firmware or RUU. But these are not compatible with the VZN version, and can lead to permanent damage.
MatteoMarsala said:
I found my backup there
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
As the OP already noted, what he is asking (how to change MID) has nothing to do with restoring a TWRP backup.
Also, the thread you linked doesn't apply to the Verizon version.
I know you are new to the forum. But please make sure you understand the question, and the proper answer, before trying to help.
In particular, giving someone the wrong advice on a Verizon device, can lead to permanent damage.
I changed my MID in order unlock the bootloader as I already gained s off earlier. As a matter of fact htc wont allow verizon m8's to unlock the bootloader so I changed the MID to that of sprint's to unlock BL. But now my modelID is somewhat like that I mentioned in the title.
Any suggestions?
Adb not working I mean that all process ran fine in command window but no results MID remains the same. No error in adb and fastboot.
redpoint73 said:
What do you mean that it's not working? Did you get an error message? Do you have adb connectivity?
Did you change the MID in the first place (or was it done by someone else)? Changing the MID on the Verizon device is not a good idea. Nothing good can come from it. Folks usually change, in order to flash another version's firmware or RUU. But these are not compatible with the VZN version, and can lead to permanent damage.
As the OP already noted, what he is asking (how to change MID) has nothing to do with restoring a TWRP backup.
Also, the thread you linked doesn't apply to the Verizon version.
I know you are new to the forum. But please make sure you understand the question, and the proper answer, before trying to help.
In particular, giving someone the wrong advice on a Verizon device, can lead to permanent damage.
Click to expand...
Click to collapse
I changed my MID in order unlock the bootloader as I already gained s off earlier. As a matter of fact htc wont allow verizon m8's to unlock the bootloader so I changed the MID to that of sprint's to unlock BL. But now my modelID is somewhat like that I mentioned in the title.
Any suggestions?
Adb not working I mean that all process ran fine in command window but no results MID remains the same. No error in adb and fastboot.
shkhr1 said:
I changed my MID in order unlock the bootloader as I already gained s off earlier. As a matter of fact htc wont allow verizon m8's to unlock the bootloader so I changed the MID to that of sprint's to unlock BL.
Click to expand...
Click to collapse
So you actually changed to Sprint MID, and then went through HTCDev.com process to unlock the bootloader?
Yeah, I know bootloader unlock is not available through HTCDev.com for the Verizon M8. But I've never seen anyone do that way (change to Sprint MID) before. Do you see someone else do it this way, or advise you to?
It seems roundabout to do it that way. Since with s-off, all you need to do is change the bootloader flag with a few adb command (HTCDev.com not needed): https://forum.xda-developers.com/showthread.php?t=2708571
shkhr1 said:
But now my modelID is somewhat like that I mentioned in the title.
Adb not working I mean that all process ran fine in command window but no results MID remains the same. No error in adb and fastboot.
Click to expand...
Click to collapse
So you ran the command exactly as described in this thread? https://forum.xda-developers.com/showthread.php?t=2708581
You sure there was no typos (cut and paste to be sure)?
If so, maybe change back to Sprint, then run the command to make it VZN MID again? That is all I can think of. No other way to get to VZN MID, that I know of.
yeah my commands were exactly same and output too as shown on the thread. all process ran fine but when i check again no change in MID . IDk what's the problem here . is there any other method you know apart from adb method.
shkhr1 said:
is there any other method you know apart from adb method.
Click to expand...
Click to collapse
I already answer that.