Related
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
So long story short, I messed up and wiped my OS off my phone via TRWP. After reinstalling and looking/asking around on the forums, I managed to reinstall it, but the WiFi is no longer working. Then after some more looking/asking, I gave up and sent in to a store for repairs. It came back and the guy said he couldn't do anything to fix it.
So... now I'm here asking again. Does anyone have any idea how to fix this?
Here's an image of my bootloader
http://imgur.com/SswEXd2
As you can see, the OS- is blank. I'm not sure if that's normal or not, but I'm 99% sure that there's supposed to be some code following OS-
You likely flashed a ROM that is a different version from what you had before, and does not match your firmware (hboot, radio, WiFi, etc. - modules that do NOT get updated when you flash a ROM).
Your hboot goes with Android 4.4.3, or software number 2.x. So flash a stock or custom ROM based on software 2.x, and WiFi should work again.
You likely flashed a ROM based on Android 4.4.4 or 5.0, and therefore no WiFi.
And no OS number listed on hboot screen is a common bug found on older TWRP versions.
Which ROM do you recommend?
Xenosaki said:
Which ROM do you recommend?
Click to expand...
Click to collapse
Most custom Sense ROMs based on software 2.xx should work.
You might also be able to use 1.xx software based ROMs, as well. Firmware is usually "backwards compatible" (with older ROMs) but never forwards compatible.
Also, next time make a backup of your stock ROM. One of the great things you can do once you have TWRP installed.
redpoint73 said:
Most custom Sense ROMs based on software 2.xx should work.
You might also be able to use 1.xx software based ROMs, as well. Firmware is usually "backwards compatible" (with older ROMs) but never forwards compatible.
Also, next time make a backup of your stock ROM. One of the great things you can do once you have TWRP installed.
Click to expand...
Click to collapse
I'm looking for a 2.xx rom right now.
Also, another question, could I update the firmware without flashing the ROM first? Or do I need to do that prior to updating the firmware?
EDIT: I'm unable to find a sense 2.xx for the HTC ONE M8. Or does the phone type not matter as long as it's a sense 2.xx?
What's your device CID & MID ?
ckpv5 said:
What's your device CID & MID ?
Click to expand...
Click to collapse
How would I go about finding it?
Xenosaki said:
I'm looking for a 2.xx rom right now.
Also, another question, could I update the firmware without flashing the ROM first? Or do I need to do that prior to updating the firmware?
EDIT: I'm unable to find a sense 2.xx for the HTC ONE M8. Or does the phone type not matter as long as it's a sense 2.xx?
Click to expand...
Click to collapse
No. You want to update the firmware first. You should also update your recovery before flashing the new firmware. Then your OS won't be blank anymore (after you flash new firmware).
If you want a 2.xx based ROM,. you could try ViperOneM8 2.5.0
It's a solid Sense based ROM with a lot of customization options.
---------- Post added at 05:12 PM ---------- Previous post was at 05:08 PM ----------
Xenosaki said:
How would I go about finding it?
Click to expand...
Click to collapse
Find it by hooking up to your PC, getting into ADB/fastboot and entering fastboot getvar all
The CID is listed as CID
The MID is listed as modelid
Xenosaki said:
I'm looking for a 2.xx rom right now.
Also, another question, could I update the firmware without flashing the ROM first? Or do I need to do that prior to updating the firmware?
Click to expand...
Click to collapse
You're talking about 2 different approaches now. You can either:
1) Flash a ROM that is supported by your (2.xx) firmware.
2) Update the firmware that matches your current ROM (but not sure what version that would be).
You don't need to do both (flash new firmware and flash a 2.xx ROM). Although you can, as long the ROM is supported by the firmware (otherwise you will still have broken WiFi and possibly other severe bugs).
Also, keep in mind that if you are s-on, you can only flash a firmware that is signed and corresponds with your CID.
Xenosaki said:
I'm looking for a 2.xx rom right now.
EDIT: I'm unable to find a sense 2.xx for the HTC ONE M8. Or does the phone type not matter as long as it's a sense 2.xx?
Click to expand...
Click to collapse
It absolutely matters. NEVER EVER EVER flash a ROM meant for another device. If you are s-on, it probably won't flash anyway. But if it does, it either won't work, or may even brick your device.
You likely just didn't browse back far enough (or didn't use the proper search string, if you used the XDA search function) to find a 2.xx based ROM for the M8. ROM base 2.xx is pretty old, so I see a couple started on Page 5 of 7 in the M8 Development section. What I see are:
http://forum.xda-developers.com/showthread.php?t=2702765
http://forum.xda-developers.com/showthread.php?t=2794008
redpoint73 said:
You're talking about 2 different approaches now. You can either:
1) Flash a ROM that is supported by your (2.xx) firmware.
2) Update the firmware that matches your current ROM (but not sure what version that would be).
You don't need to do both (flash new firmware and flash a 2.xx ROM). Although you can, as long the ROM is supported by the firmware (otherwise you will still have broken WiFi and possibly other severe bugs).
Also, keep in mind that if you are s-on, you can only flash a firmware that is signed and corresponds with your CID.
It absolutely matters. NEVER EVER EVER flash a ROM meant for another device. If you are s-on, it probably won't flash anyway. But if it does, it either won't work, or may even brick your device.
You likely just didn't browse back far enough (or didn't use the proper search string, if you used the XDA search function) to find a 2.xx based ROM for the M8. ROM base 2.xx is pretty old, so I see a couple started on Page 5 of 7 in the M8 Development section. What I see are:
http://forum.xda-developers.com/showthread.php?t=2702765
http://forum.xda-developers.com/showthread.php?t=2794008
Click to expand...
Click to collapse
Sorry if I'm asking too many questions. If I go with the updating the firmware route first, do I have to do anything specific? Like for example update from 2.x.x -> 5.0. Or does it not matter what version I'm currently on to update to 5.0. Also, I'm seeing a lot of issues concerning which carrier the phone is from. Is there a way to check that? I *think* mine might be some asian branded version, but I'm unsure.
Also, I'm checking the phone's firmware and it's saying that it's 4.4.4. http://imgur.com/rbLpjl1
All the pic info you provided not really can give proper help.
I'm asking again, maybe for the last time .. what's your device CID & MID ?
Xenosaki said:
Sorry if I'm asking too many questions. If I go with the updating the firmware route first, do I have to do anything specific? Like for example update from 2.x.x -> 5.0. Or does it not matter what version I'm currently on to update to 5.0. Also, I'm seeing a lot of issues concerning which carrier the phone is from. Is there a way to check that? I *think* mine might be some asian branded version, but I'm unsure.
Click to expand...
Click to collapse
It absolutely matters what firmware you pick and whether or not it corresponds to your CID. For one thing, with s-on, you can only flash the firmware for your CID, plus the firmware has to be signed.
Another thing, the firmware will update your radio baseband version. So if you flash firmware for a different CID, you may change the band support, and find you no longer have 3G or 4G connection (depending on what firmware you flash, what bands used by your local carrier, etc.).
Also, don't confuse software version with Android version (you've mixed the 2 together above). The Android version is Google's numbering scheme. Software number is HTC's numbering scheme.
Software version 2.xx corresponds to Android version 4.4.3.
Android version 5.0 (Lollipop) corresponds to software version 4.xx.
Its been requested a couple times now that you do adb getvar all to determine your CID and MID. We can't help if you are guessing or don't know the carrier version.
Xenosaki said:
Also, I'm checking the phone's firmware and it's saying that it's 4.4.4. http://imgur.com/rbLpjl1
Click to expand...
Click to collapse
The photo has nothing to do with your firmware number. The firmware number is best determined with adb getvar all, and is displayed as "main version".
What your picture shows simply means the ROM you flashed is based on Android 4.4.4, and software 3.28.401. The software number of the ROM is completely different from your present firmware number; and the very reason why your WiFi is broken.
I've already determined from the pic in your first post that your firmware is 2.xx (corresponding to Android 4.4.3). To get the more specific numbers (after the "2") you need to do adb getvar all.
Also, if you post the getvar output, be sure to delete your IMEI and serial number, as these are private info.
ckpv5 said:
All the pic info you provided not really can give proper help.
I'm asking again, maybe for the last time .. what's your device CID & MID ?
Click to expand...
Click to collapse
redpoint73 said:
It absolutely matters what firmware you pick and whether or not it corresponds to your CID. For one thing, with s-on, you can only flash the firmware for your CID, plus the firmware has to be signed.
Another thing, the firmware will update your radio baseband version. So if you flash firmware for a different CID, you may change the band support, and find you no longer have 3G or 4G connection (depending on what firmware you flash, what bands used by your local carrier, etc.).
Also, don't confuse software version with Android version (you've mixed the 2 together above). The Android version is Google's numbering scheme. Software number is HTC's numbering scheme.
Software version 2.xx corresponds to Android version 4.4.3.
Android version 5.0 (Lollipop) corresponds to software version 4.xx.
Its been requested a couple times now that you do adb getvar all to determine your CID and MID. We can't help if you are guessing or don't know the carrier version.
The photo has nothing to do with your firmware number. The firmware number is best determined with adb getvar all, and is displayed as "main version".
What your picture shows simply means the ROM you flashed is based on Android 4.4.4, and software 3.28.401. The software number of the ROM is completely different from your present firmware number; and the very reason why your WiFi is broken.
I've already determined from the pic in your first post that your firmware is 2.xx (corresponding to Android 4.4.3). To get the more specific numbers (after the "2") you need to do adb getvar all.
Also, if you post the getvar output, be sure to delete your IMEI and serial number, as these are private info.
Click to expand...
Click to collapse
Not sure if I got the right ones, but here you go. Let me know if I didn't do it right.
http://imgur.com/a/C8hcK#0
The first picture is getting the CID and MID by following some guide off of google, so I don't know if that's right or not.
The second and third picture are the adb getvar all that you suggested me doing.
See ... you're on T-Mobile network but your device is not a TMOB and not a EU but a TW device.
CID HTC__621
MID 0P6B11000
This is my suggestion to fix whatever problem you have currently (without S-Off).
1. Restore 2.22.709.3 TWRP backup as your device hboot is 3.18.0000
2. install 2.22.709.3 stock recovery after restore
3. do multiple OTA to the latest lollipop version : 2.22.709.3 --> 3.28.709.6 --> 4.16.709.9 --> 4.24.709.2
4. Then if you like to install custom ROM, install TWRP again and install any custom ROM that you like - now you should not have any wifi problem
All the needed files / how-to is here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You guys are absolutely amazing. Thank you so much for the help and patience. I followed all the steps (except for the multiple OTA updates, which I'm in the process of right now) and the wifi problem seems to be fixed.
On an off note, does it matter that in the bootloader, it says
*** Software status: Modified ***
*** UNLOCKED ***
?
And should I go through the process of S-Off-ing my phone? Does it benefit me to do it?
Again, thank you so much
Xenosaki said:
I followed all the steps (except for the multiple OTA updates, which I'm in the process of right now) and the wifi problem seems to be fixed.
On an off note, does it matter that in the bootloader, it says
*** Software status: Modified ***
*** UNLOCKED ***
?
Click to expand...
Click to collapse
UNLOCKED is fine. OTAs will install whether its locked or not. Better to leave it as-is (relocking only needed and recommended to run RUU or signed firmware zip).
The software modified flag is a bit puzzling. It usually indicated the ROM has been modified. If you installed the stock TWRP backup for your CID, it shouldn't say this. And software modified will prevent OTA from installing.
Are you sure you installed the stock TWRP backup (exactly correct software number) that ckpv5 indicated?
Xenosaki said:
And should I go through the process of S-Off-ing my phone? Does it benefit me to do it?
Click to expand...
Click to collapse
It depends on what you want to do with the phone. For most things (root, flashing custom ROMs, kernels, etc.), s-off is not needed. But it can be handy if you want to flash radios, modified hboots, convert to another CID or MID, and some other things.
---------- Post added at 10:22 AM ---------- Previous post was at 10:18 AM ----------
Xenosaki said:
The second and third picture are the adb getvar all that you suggested me doing.
Click to expand...
Click to collapse
The pics do not show the expected output for adb getvar all.
My guess is that you tried to run the commands same as the other (fastboot) commands, while in fastboot mode. adb commands can only be run while booted into OS (and with Debugging enabled in phone settings) or in recovery. Only fastboot commands work in fastboot mode.
redpoint73 said:
The software modified flag is a bit puzzling. It usually indicated the ROM has been modified. If you installed the stock TWRP backup for your CID, it shouldn't say this. And software modified will prevent OTA from installing.
Are you sure you installed the stock TWRP backup (exactly correct software number) that ckpv5 indicated?
Click to expand...
Click to collapse
That's the same as "TAMPERED" on hboot 3.18.0000 as seen on his first screenshot.
MODIFIED is on hboot 3.19.0000
That usually come after the bootloader is unlocked.
That can be change on S-Off device.
I installed the Venom ROM so that's probably the reason why it's showing that then. Thanks for everything guys
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
Guys, I got my m8 about 5 days back. I think it's international Taiwan version. I have attached the images of current software version I am on.
Currently the phone is asking me about 3 very small updates available. I have attached that image also. I don't know what these updates are for.
Shall I update?
Will my phone remain unlocked after these updates?
If after these updates I get prompted for real marshmallow update, shall I update to marshmallow.
Does marshmallow offer much better and some desirable features which we currently don't have?
Btw, I am currently highly satisfied with my current lollipop version.
This thing has really surpassed my expectations. I previously had LG g pro and Xperia z ultra.
Yes, I would definitely update. The phone seems smoother and less laggy on android M. A few new features. Lollipop felt like a beta version of M.
There is really no point to not update.
lekhwani said:
I think it's international Taiwan version.
Click to expand...
Click to collapse
That's not Taiwan version but Asia WWE
ckpv5 said:
That's not Taiwan version but Asia WWE
Click to expand...
Click to collapse
I installed the 3 small updates. Phone prompted me to restart.
So I restarted.
Then I again check software updates and get this prompt:
After hitting the download button, I let it download as it starts downloading some 1.14 gb update. I also put it to charge.
But when after an hour so when I picked up the phone got the message given in second attached picture.
Can someone guide what is the issue?
That means your device is not the original Asia WWE ... I guess you don't bought a new device from authorized HTC dealer.
To know which device that originally is, you need to get the fastboot getvar all result.
Also what's written on the bootloader
ckpv5 said:
That means your device is not the original Asia WWE ... I guess you don't bought a new device from authorized HTC dealer.
To know which device that originally is, you need to get the fastboot getvar all result.
Also what's written on the bootloader
Click to expand...
Click to collapse
It was a new sealed pack I got from eBay. But why it throws up the second message about variant. (I mean when it says mm software update available) ?
It says an update available because the software version no. installed on device is 4.19.707.4 and there is an update to 6.14.707.1
But the second message says it can't install the update because the model-ID in incorrect. It expect model-ID for 4.19.707.4 which is 0P6B11000 but your device may have a different model-ID
That's why we need the fastboot getvar all to determine your original device variant
ckpv5 said:
It says an update available because the software version no. installed on device is 4.19.707.4 and there is an update to 6.14.707.1
But the second message says it can't install the update because the model-ID in incorrect. It expect model-ID for 4.19.707.4 which is 0P6B11000 but your device may have a different model-ID
That's why we need the fastboot getvar all to determine your original device variant
Click to expand...
Click to collapse
But why doesn't it check for the compatible version automatically.
I mean it should say software update is not available for mobile.
It shouldn't prompt in the first place.
The update should automatically check which version or software or hardware I am on.
Btw I have hit the download button again and it's downloading. It's been about 10 minutes and 13% progress.
If this doesn't work this time again, I suppose will have to do getvar thing.
Btw, can the information given on following link solve my problem?
It says don't restart after installing 3 small updates.
But think that guys problem was a bit different
https://www.reddit.com/r/htcone/comments/41809r/marshmallow_update_question/
Those questions only HTC can answer. If I am HTC .. I don't expect the device is modified and I won't check whether the device is modified or not. Most important what is the software version no. because things like model-ID is something in the hardware not the software and users are not supposed to modify hardware.
Sorry ... I don't read outside link ... only XDA for problem reported on XDA.
If you don't feel like to fix it ... just hit don't install, don't check auto checking and block the notification ...
Good luck .. I have to go now .. bed time.
Maybe someone else will help you.
ckpv5 said:
Those questions only HTC can answer. If I am HTC .. I don't expect the device is modified and I won't check whether the device is modified or not. Most important what is the software version no. because things like model-ID is something in the hardware not the software and users are not supposed to modify hardware.
Sorry ... I don't read outside link ... only XDA for problem reported on XDA.
If you don't feel like to fix it ... just hit don't install, don't check auto checking and block the notification ...
Good luck .. I have to go now .. bed time.
Maybe someone else will help you.
Click to expand...
Click to collapse
Thanks for your help so far. Actually its bed here for me as well.
Am already in bed actually.
I have only very occasionly done those fastboot thing.
Suppose will have to do it through laptop tomorrow (when I find time)
Will report here again.
ckpv5 said:
Those questions only HTC can answer. If I am HTC .. I don't expect the device is modified and I won't check whether the device is modified or not. Most important what is the software version no. because things like model-ID is something in the hardware not the software and users are not supposed to modify hardware.
Sorry ... I don't read outside link ... only XDA for problem reported on XDA.
If you don't feel like to fix it ... just hit don't install, don't check auto checking and block the notification ...
Good luck .. I have to go now .. bed time.
Maybe someone else will help you.
Click to expand...
Click to collapse
Buddy, today I found some time and installed adb and fastboot.
After going to fasboot I got to see that my device is s off.
Also ran the getvar all command.
Attached both pics.
Kindly let me know guys , what does my current configuration / status means?
And , what options I have to upgrade to marshmallow?
Here are the pics
lekhwani said:
Here are the pics
Click to expand...
Click to collapse
Your device is m8_ul_ca means it is originally an AT&T or a Developer Edition device.
Now it's running Asia WWE ROM, the CID is SuperCID (which is good) but the MID is EU MID
So .. you have to decide ..what you want your device to be ?
Most important where your location is then make it suitable for your current location.
The easiest is change it to EU WWE ... you don't need to change anything ... only run the EU WWE RUU
ckpv5 said:
Your device is m8_ul_ca means it is originally an AT&T or a Developer Edition device.
Now it's running Asia WWE ROM, the CID is SuperCID (which is good) but the MID is EU MID
So .. you have to decide ..what you want your device to be ?
Most important where your location is then make it suitable for your current location.
The easiest is change it to EU WWE ... you don't need to change anything ... only run the EU WWE RUU
Click to expand...
Click to collapse
Thanks for the quick reply.
I am from India. Is there any method by way of which I can install ota which currently throws the system variant issue after downloading the full 1.14 gb download.
Can this be due to s off?
can I just s on from s off and this will resolve my current issue.
Or its not possible now ?( Because it's modified too far?)
read just a few minutes back in one m8 thread on xda only that with a fastboot command (fastboot own writesecurflag 3) we can convert to s on but everything should be stock for this.
As I mentioned earlier, the system variant error is due to wrong MID on the device, nothing to do with S-Off/S-On status.
You would not have the system variant error if the MID is 0P6B11000 ( read back my post #7 )
To ensure a successful OTA installation ... both software version no. and MID must correct .. same goes for CID but since yours is SuperCID then it is universal for any variant.
Give you a few examples of correct version no. & MID
Asia WWE - x.xx.707.x - MID - 0P6B11000
EU WWE - x.xx.401.x - MID - 0P6B10000
India WWE - x.xx.720.x - MID - 0P6B65000
Your current configuration is wrong, that's why the system variant error.
I suggest to install EU WWE RUU so you save the headache to change this and that.
Read this for the driver part that you need on your PC - http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
Read this for the EU RUU and How-to : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Or if the above is not possible, I am ready to flash ruu. Then kindly guide me how and what ruu to flash? Will I have to unlock also?
lekhwani said:
read just a few minutes back in one m8 thread on xda only that with a fastboot command (fastboot own writesecurflag 3) we can convert to s on but everything should be stock for this.
Click to expand...
Click to collapse
Don't do this when you have this kind of wrong configuration on your device.
You'll regret your action as you won't be able to do anything not even OTA until you spend another USD25 to S-Off it again and correct the configuration.
---------- Post added at 09:28 PM ---------- Previous post was at 09:26 PM ----------
lekhwani said:
Or if the above is not possible, I am ready to flash ruu. Then kindly guide me how and what ruu to flash? Will I have to unlock also?
Click to expand...
Click to collapse
Read what I posted earlier ... that's all you need to do .. no need to unlock but you can unlock if you want to.
My mied reads 000000.. does this mean eu mied?
Or its just because it's not a cdma device?