Related
Hi everyone,
This is my first post on XDA and i'm actually thrilled.
So I have the Taiwanese unlocked model of the HTC One (M8) and I'm thinking over fully converting it to a GPE with the famous RUU.
I tried searching the forums but couldn't find a strict answer for my issue: If I fully convert my device, I know this means the radio image will also change to the stock one of the GPE version.
What does it mean? Will I lose signal because this is a different radio image than the Asian one? Do I have to change the radio image after installing the RUU.zip?
I'm fairly new to modifying my devices so take it easy on me.
THANK YOU SO MUCH IN ADVANCE.
Nimi.
If it's anything like the regular M8, you can just reflash the radio of your choice.
HTC One M8
Elisha said:
If it's anything like the regular M8, you can just reflash the radio of your choice.
HTC One M8
Click to expand...
Click to collapse
Yes, It is anything like the regular GSM M8, just the CPU runs at 2.5GHZ rather than 2.3 on US models, and of course it supports different bands.
So, I do everything just like the tutorials say and after im finished I can reflash the Taiwanese radio for example? Will I still get OTA updates?
Thanks!
You should be able to. But you may want to wait until someone with the Asian version can confirm. If you want to test it out, flash the 4.4.3 GPE ruu and see if you get the 4.4.4 OTA.
HTC One M8
Elisha said:
You should be able to. But you may want to wait until someone with the Asian version can confirm. If you want to test it out, flash the 4.4.3 GPE ruu and see if you get the 4.4.4 OTA.
HTC One M8
Click to expand...
Click to collapse
Sounds like a good idea, Thanks!
Anyone here with the Asian model that has converted to GPE?
Please.
UP!
Please, Anyone else can help here..?
Thanks!
nimrodiny said:
UP!
Please, Anyone else can help here..?
Thanks!
Click to expand...
Click to collapse
I have Asian version. And I have rooted to convert to GPE. Everytime I install the GPE rom or OTA update. I always have to flash the asian radio so that I will get signal. I wish there was a way such that OTA will install and know that an Asian radio is required; or maybe something that will prevent my radio from being overwritten.
About the question if you'll get OTA updates automatically, I remember you have to modify you CID or MID or something. You will have to look up for that...
I have the Asian model as well, I converted over and placed the asian radio in the ruu zip before flashing, and now whenever i get an ota it doesnt change the radio
I converted my SIM Free GSM HTC One M8 to a GPE at the end of December.
Everything works and I'm really enjoying the experience.
However, I have since found out that I needed to change the MID and the CID. All I did was change the CID to GOOGL001. Will I receive OTA's from Google and will they install properly or do I also need to change the MID? Thanks
Goldenears2015 said:
I converted my SIM Free GSM HTC One M8 to a GPE at the end of December.
Everything works and I'm really enjoying the experience.
However, I have since found out that I needed to change the MID and the CID. All I did was change the CID to GOOGL001. Will I receive OTA's from Google and will they install properly or do I also need to change the MID? Thanks
Click to expand...
Click to collapse
best to change the MID too, its just as easy to change the MID as the CID.
Goldenears2015 said:
I converted my SIM Free GSM HTC One M8 to a GPE at the end of December.
Everything works and I'm really enjoying the experience.
However, I have since found out that I needed to change the MID and the CID. All I did was change the CID to GOOGL001. Will I receive OTA's from Google and will they install properly or do I also need to change the MID? Thanks
Click to expand...
Click to collapse
Your going to want to change the MID to match GPE and when your ready to take the OTA your going to want the stock recovery that matches the current OS your on.
Also make sure your system is not modified at all for instance (platform.xml) witch most people have altered when they use "sdcardfix" app for read/write permissions
Will the OTA just fail without the correct MID or will it brick the phone?
I don't have access to a PC at the moment, just a Chromebook. To change the MID, do I need root access? I've downloaded the terminal Emulator for Android but it says device not found.
Yes you need to change the MID.
yes you will need root .I'm not familiar with the chromebook so I'm not sure
For OTA updates you definitely need the CID, I didn't need to change MID when I was converted
EddyOS said:
For OTA updates you definitely need the CID, I didn't need to change MID when I was converted
Click to expand...
Click to collapse
Thanks for the reply. Did you update to Lollipop from KitKat through an OTA after conversion? also, is your M8 a UK model? The reason I'm asking is because if I can avoid changing the MID I will. It was a bit of a headache converting it in the first place.
Yes to the above. The OTA files seem to work with all MIDs but the CID is crucial otherwise the FW won't flash
I've converted to GPE two times and each time I ruu the earliest ruu so I could OTA up to the latest firmware/version (I followed the guide 100% and it included changing the MID)
I also change the CID to the specific variant it's supposed to be .I recently converted back to Sense Dev edition and changed everything to match so I could update to Dev lollipop, now I run the Dev lollipop firmware with a stock GPE lollipop ROM and it's great
EddyOS said:
Yes to the above. The OTA files seem to work with all MIDs but the CID is crucial otherwise the FW won't flash
Click to expand...
Click to collapse
That's good news, I'll leave it as is then, the CID is GOOGL001 .
jball said:
I've converted to GPE two times and each time I ruu the earliest ruu so I could OTA up to the latest firmware/version (I followed the guide 100% and it included changing the MID)
I also change the CID to the specific variant it's supposed to be .I recently converted back to Sense Dev edition and changed everything to match so I could update to Dev lollipop, now I run the Dev lollipop firmware with a stock GPE lollipop ROM and it's great
Click to expand...
Click to collapse
I was looking at a GPE ROM yesterday and tbh, I was thinking that it should be the official ROM because of the additional features and extra settings available.
This is the ROM I used up until two days ago.
http://forum.xda-developers.com/showthread.php?t=2706441
Now I'm checking out Liquidsmooth 5.0.2
Well, i got my M9 as a christmas present, thinking that it was the unlocked variant, and when i receive it i inmediately start going through all the updates and when i finish, i asked myself, where is the 6.0 update? so i started diggin, and found out that my M9 is the australian variant, with CID OPTUS001, but the weird thing is that it is unlocked. So i ask, does it mean i wont be able to get the updates first? if the answer is no, then what do i have to do to convert my M9 to the international version, so i can get the updates first?
P.S: i already have experience with rooting, S-off, ROMS, etc on my M7 and i have already unlocked the bootloader of my M9
robertoferrer27 said:
Well, i got my M9 as a christmas present, thinking that it was the unlocked variant, and when i receive it i inmediately start going through all the updates and when i finish, i asked myself, where is the 6.0 update? so i started diggin, and found out that my M9 is the australian variant, with CID OPTUS001, but the weird thing is that it is unlocked. So i ask, does it mean i wont be able to get the updates first? if the answer is no, then what do i have to do to convert my M9 to the international version, so i can get the updates first?
P.S: i already have experience with rooting, S-off, ROMS, etc on my M7 and i have already unlocked the bootloader of my M9
Click to expand...
Click to collapse
The US dev edition is the one that got the update, you'd have to covert to that to update it now or just wait for your edition to be updated
Sent from my HTC One M9 using Tapatalk
robertoferrer27 said:
Well, i got my M9 as a christmas present, thinking that it was the unlocked variant, and when i receive it i inmediately start going through all the updates and when i finish, i asked myself, where is the 6.0 update? so i started diggin, and found out that my M9 is the australian variant, with CID OPTUS001, but the weird thing is that it is unlocked. So i ask, does it mean i wont be able to get the updates first? if the answer is no, then what do i have to do to convert my M9 to the international version, so i can get the updates first?
P.S: i already have experience with rooting, S-off, ROMS, etc on my M7 and i have already unlocked the bootloader of my M9
Click to expand...
Click to collapse
See my signature for converting your phone to US DevEd
Hello there, guys.
I am getting into this whole "Android" thing and realizing it is fun and sometimes complex. A co-worker bought an unlocked HTC One M9 at the beginning of the year, and it came with Android 5.1.1 - the firmware was 2.11.531.19, which belongs to T-Mobile. There was no way to update it OTA, but she was happy so that was it.
Now, having finally been able to update an AT&T Note 5 withough being in the US, I thought the process would be somewhat similar with the M9. Knowing it was a T-Mobile device - the 531 in the firmware is T-Mobile's SKU - I downloaded the RUU from HTC with version 3.39.531.41
No go. Not only did it fail, it left the device in a somewhat bricked state. I tried downloading different RUU's, tried getting the rom.zip in a SD card, but it all failed. Then, just for kicks, I downloaded the RUU for the Unlocked/Developer version, which is 3.35.617.31 BAM! It worked without a problem.
Being curious, I used ADB to look what the CID/MID values were for the device, and found something funny. The MID is 0PJA11000, which I believe belongs to Dev/Unlocked/AT&T, but the CID is set to 11111111 (SuperCID). Whut!
I also see the product is "htc_himaulatt", which I guess means this was an AT&T device... that had a T-Mobile SKU installed? The device is S-ON, by the way.
What does this mean for future updates? Should I/she continue to use the RUU for the Unlocked/Developer devices? Should I set her device to S-OFF? Also, she received an OTA notification for version 4.x.xxx.xx that incloudes Nougat, but upon download it said that the devices software had been modified and it couldn't install that update.
Thanks in advance for any guidance!
KillerFry said:
Hello there, guys.
I am getting into this whole "Android" thing and realizing it is fun and sometimes complex. A co-worker bought an unlocked HTC One M9 at the beginning of the year, and it came with Android 5.1.1 - the firmware was 2.11.531.19, which belongs to T-Mobile. There was no way to update it OTA, but she was happy so that was it.
Now, having finally been able to update an AT&T Note 5 withough being in the US, I thought the process would be somewhat similar with the M9. Knowing it was a T-Mobile device - the 531 in the firmware is T-Mobile's SKU - I downloaded the RUU from HTC with version 3.39.531.41
No go. Not only did it fail, it left the device in a somewhat bricked state. I tried downloading different RUU's, tried getting the rom.zip in a SD card, but it all failed. Then, just for kicks, I downloaded the RUU for the Unlocked/Developer version, which is 3.35.617.31 BAM! It worked without a problem.
Being curious, I used ADB to look what the CID/MID values were for the device, and found something funny. The MID is 0PJA11000, which I believe belongs to Dev/Unlocked/AT&T, but the CID is set to 11111111 (SuperCID). Whut!
I also see the product is "htc_himaulatt", which I guess means this was an AT&T device... that had a T-Mobile SKU installed? The device is S-ON, by the way.
What does this mean for future updates? Should I/she continue to use the RUU for the Unlocked/Developer devices? Should I set her device to S-OFF? Also, she received an OTA notification for version 4.x.xxx.xx that incloudes Nougat, but upon download it said that the devices software had been modified and it couldn't install that update.
Thanks in advance for any guidance!
Click to expand...
Click to collapse
I would say leave it as is, if you change the cid to the appropriate one for the developer edition(BS_US001), the otas wont fail.
Sent from my HTC One M9 using XDA-Developers mobile app
sssssbarn said:
I would say leave it as is, if you change the cid to the appropriate one for the developer edition(BS_US001), the otas wont fail.
Sent from my HTC One M9 using XDA-Developers mobile app
Click to expand...
Click to collapse
But in order to change the cid I need to have S-Off which in turn needs the device to be rooted, or am I wrong?
KillerFry said:
But in order to change the cid I need to have S-Off which in turn needs the device to be rooted, or am I wrong?
Click to expand...
Click to collapse
Probably but would have to be s off to get to super cid tl begin with. What does it say in the bootloader
Sent from my HTC One M9 using XDA-Developers mobile app
sssssbarn said:
Probably but would have to be s off to get to super cid tl begin with. What does it say in the bootloader
Sent from my HTC One M9 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's S-On, heh.
Id try it through fastboot but probably gonna need sunshine
Sent from my HTC One M9 using XDA-Developers mobile app
I have a T-mobile M9 however it is not receiving the 7.0 update. I am wondering if I can just use the unlocked RUU in order to upgrade to 7.0.
Thanks
Alederangle said:
I have a T-mobile M9 however it is not receiving the 7.0 update. I am wondering if I can just use the unlocked RUU in order to upgrade to 7.0.
Thanks
Click to expand...
Click to collapse
Check out the readme thread - it'll give you instructions about changing your MID & CID to match the developer or WWE SKU to convert your phone to those versions and receive the Nougat update. Be advised that wifi calling is not available if you switch.
computerslayer said:
Check out the readme thread - it'll give you instructions about changing your MID & CID to match the developer or WWE SKU to convert your phone to those versions and receive the Nougat update. Be advised that wifi calling is not available if you switch.
Click to expand...
Click to collapse
I don't have s-off and can't afford sunshine so
I'm afraid you're stuck and will have to wait for T-mobile to release the update.
computerslayer said:
I'm afraid you're stuck and will have to wait for T-mobile to release the update.
Click to expand...
Click to collapse
If I do try to use the stock ruu, what's the worst thing that can happen?
Alederangle said:
If I do try to use the stock ruu, what's the worst thing that can happen?
Click to expand...
Click to collapse
Exactly what the readme spells out: if you correctly flash the RUU corresponding to your SKU and OS version, your phone will be wiped & reset to stock.
All other RUUs with detect the mismatch and fail.