Related
I have a question about making a universal android-info.txt for use with splash screens.
I make the M8 BIOS Splash Screens and want to make them universally flashable. I know that the MIDs and CIDs for the variants need to be included, and I have what I think is a comprehensive list of them. Many people are SuperCID anyway, so this isn't as big of a concern.
My concern is the "mainver." Can I leave it at the default value (from the splash screen creator's original android-info.txt): 1.54.401.5?
Or should I update it to be more in-line with the 4.4.3 update on the international version: 2.22.401.4?
Also, would this have any effect on flashing the zips via this command for all the variants?
Code:
fastboot flash zip splash.zip
I am on the T-Mo variant.
Thanks for any help on this!
I'm mostly looking to increase battery and just make it more snappy and fluent Will I be able to keep my camera effects?
Anything I should know? My last question is how difficult is it to do? I'm not a newb when it comes to phones but I'm not the most confident.
Thanks guys!
L1qu1d said:
I'm mostly looking to increase battery and just make it more snappy and fluent Will I be able to keep my camera effects?
Anything I should know? My last question is how difficult is it to do? I'm not a newb when it comes to phones but I'm not the most confident.
Thanks guys!
Click to expand...
Click to collapse
If you convert to GPE you probably won't keep your camera effects as it comes with HTC's Sense and I don't think anyone ported it for GPE? I could be wrong, but that's something you can look into.
If you convert to Developer edition you'll keep the camera effects though as it's HTC Sense 6.
You'll need S-OFF in order to do conversions between different variants, you'll need to change the MID/CID and of course for the flashing of the relevant firmwares. So that's the first step, get S-OFF if you don't have it already, you can get S-OFF by buying it through Sunshine S-OFF. You can try Firewater first(It's free) but it doesn't work for most devices with newest software on it(4.4.2 & 4.4.3).
Some of the steps you'll take once you have the necessary stuff in place(S-OFF)
Get a developer edition nandroid backup and stock recovery - COLLECTION of Stock backup's
Get an older version nandroid backup for developer edition, this is important to test if you get OTA updates after the conversion and of course you'll update phone as you go. So get an older one...
Boot into bootloader, connect phone to pc, open command prompt for adb/fastboot. Grab the info for your device:
Code:
fastboot getvar all
Note the CID & MID, both for future references and of course if the MID is not the same as the developer edition one, which it isn't, you'll need to change the MID.
[how to] change your MID without an eng bootloader Follow instructions given by Scotty how to change it. The Rogers one is in post 2.
Next you'll want to change the CID to Developer edition one (BS_US002) I think BS_US001 is unlocked version but they use the same software anyways so:
Code:
fastboot oem writecid BS_US002
After that type
Code:
fastboot reboot-bootloader
That is to check if the CID changed like it's supposed to do.
Next you'll want to flash the stock recovery for the developer edition, of course make sure all the relevant files are in the relevant places.
Code:
fastboot flash recovery recovery.img
fastboot erase cache
Boot a custom recovery(I'm not sure if you can just skip the above flashing of stock recovery and flash a custom one right away )
Code:
fastboot boot name_of_custom_recovery.img
I don't know if TWRP will boot or not, might influence the step with the stock recovery, can probably flash custom recovery right of the bat, but I'm not sure about that again... anyways.
Inside the custom recovery just clear the partitions(dalvik, cache etc) then restore the nandroid backup you downloaded afterwards you can reboot the phone again. Now you're developer edition and once it starts up we'll see if you get OTA prompt or not, hence why a bit of an older version was needed. Of course you'll definitely need the stock recovery to actually do the OTA. It'll update the firmware as the OTA's install.
That's about it I think
@ckpv5 should be able to help with anything else, looks like he's done quite a few conversions with all the different variant OTA/backups he's sharing on here.
BerndM14 said:
If you convert to GPE you probably won't keep your camera effects as it comes with HTC's Sense and I don't think anyone ported it for GPE? I could be wrong, but that's something you can look into.
If you convert to Developer edition you'll keep the camera effects though as it's HTC Sense 6.
You'll need S-OFF in order to do conversions between different variants, you'll need to change the MID/CID and of course for the flashing of the relevant firmwares. So that's the first step, get S-OFF if you don't have it already, you can get S-OFF by buying it through Sunshine S-OFF. You can try Firewater first(It's free) but it doesn't work for most devices with newest software on it(4.4.2 & 4.4.3).
Some of the steps you'll take once you have the necessary stuff in place(S-OFF)
Get a developer edition nandroid backup and stock recovery - COLLECTION of Stock backup's
Get an older version nandroid backup for developer edition, this is important to test if you get OTA updates after the conversion and of course you'll update phone as you go. So get an older one...
Boot into bootloader, connect phone to pc, open command prompt for adb/fastboot. Grab the info for your device:
Code:
fastboot getvar all
Note the CID & MID, both for future references and of course if the MID is not the same as the developer edition one, which it isn't, you'll need to change the MID.
[how to] change your MID without an eng bootloader Follow instructions given by Scotty how to change it. The Rogers one is in post 2.
Next you'll want to change the CID to Developer edition one (BS_US002) I think BS_US001 is unlocked version but they use the same software anyways so:
Code:
fastboot oem writecid BS_US002
After that type
Code:
fastboot reboot-bootloader
That is to check if the CID changed like it's supposed to do.
Next you'll want to flash the stock recovery for the developer edition, of course make sure all the relevant files are in the relevant places.
Code:
fastboot flash recovery recovery.img
fastboot erase cache
Boot a custom recovery(I'm not sure if you can just skip the above flashing of stock recovery and flash a custom one right away )
Code:
fastboot boot name_of_custom_recovery.img
I don't know if TWRP will boot or not, might influence the step with the stock recovery, can probably flash custom recovery right of the bat, but I'm not sure about that again... anyways.
Inside the custom recovery just clear the partitions(dalvik, cache etc) then restore the nandroid backup you downloaded afterwards you can reboot the phone again. Now you're developer edition and once it starts up we'll see if you get OTA prompt or not, hence why a bit of an older version was needed. Of course you'll definitely need the stock recovery to actually do the OTA. It'll update the firmware as the OTA's install.
That's about it I think
@ckpv5 should be able to help with anything else, looks like he's done quite a few conversions with all the different variant OTA/backups he's sharing on here.
Click to expand...
Click to collapse
HOLY MOLY!
Wow that's a lot of info, I'll give it a shot in the next couple of days! looks difficult but ur instructions are super clear:victory:
I'll report back, hopefully this gives me more battery life, I might be switching to the note 4/edge so decided to see if I can avoid that!
L1qu1d said:
HOLY MOLY!
Wow that's a lot of info, I'll give it a shot in the next couple of days! looks difficult but ur instructions are super clear:victory:
Click to expand...
Click to collapse
To add even more information, maybe the thread helps as well:
GPE conversion
It's a RUU conversion guide by @graffixnyc.
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
I received a refurbished phone after my old m8 gave out. Now that I have rooted it, I seem to only be able to flash sense roms in recovery, AOSP and GPE just give me bootloops. I even tried flashing xposed, and I got the message, "error executing updater binary" in the latest TWRP. Anybody know what this could be?
That happens when a rom zip looks for a specific or list of certain models. If you are only rooted and still have s-on and a stock carrier MODELID the zip/rom you are trying to flash likely does not have it as supported model.
There are a couple things you can do.
unzip the zip on a pc/mac and look in META-INF\com\google\android\Updater-script and see what models its looking for. While in fastboot (bootloader) use a terminal/command prompt and enter the command "fastboot getvar all"
that will give you all kinds of info about your device as far as modelID, serial, imei. Which you can compare to what the zip is specifically looking for.
Or if you are S-OFF and using a GSM M8 change your modelID/CID to a developer unlocked or international M8 and more than likely its supported by all roms zips.
If I'm not mistaken that would cause your issue. Also XDA is full of threads with instructions on how to do almost anything, its only a matter of searching.
Tachi91 said:
That happens when a rom zip looks for a specific or list of certain models. If you are only rooted and still have s-on and a stock carrier MODELID the zip/rom you are trying to flash likely does not have it as supported model.
There are a couple things you can do.
unzip the zip on a pc/mac and look in META-INF\com\google\android\Updater-script and see what models its looking for. While in fastboot (bootloader) use a terminal/command prompt and enter the command "fastboot getvar all"
that will give you all kinds of info about your device as far as modelID, serial, imei. Which you can compare to what the zip is specifically looking for.
Or if you are S-OFF and using a GSM M8 change your modelID/CID to a developer unlocked or international M8 and more than likely its supported by all roms zips.
If I'm not mistaken that would cause your issue. Also XDA is full of threads with instructions on how to do almost anything, its only a matter of searching.
Click to expand...
Click to collapse
What if I have an S-off CDMA?
Stick to roms/kernels that specifically state they support Verizon/Sprint. If you're attempting to install a rom that claims support for your carrier model than it could be something else.
At that point seek support from that developer. I could sit here and post all manners of ideas and possible ways to get a clearer answer as to why it gives you that error.
But it can also be solved by looking around in a roms/kernels thread to see if any one else is having or had a similar issue.
hello guy's, i'm a real noob with htc or "rooting" etc and i'm facing a problem. I just bought a htc one m9 with android 6. I think its refurbished because it look like new but the left speaker is louder than the right, and are not loud at all. So I thought I would update it for maybe solve the problem, but I have the update notification and when i click on it, it say the sytem is not stock so can't update. The phone isn't root so i don't know why i'm facing this, so after a long research i did many things like try to install RUU..exe or with RUU;zip and no one want to install. At one moment i change the CID and the OTA begin the update by itself (don't show the "not stock system" message anymore" but stop at 25% and reboot. I'm really confused and don't understand anythings, last thing i did is unlock the bootloader but doesn't change anythings. Is it possible to reinstall a pure stock version ? and after update it ? I am not interested by rooting the phone, i just want pure stock version and be able to update the phone, is it possible to get help? Thanks !
What's the current CID of the phone? Which firmware version is currently installed? Which model name is engraved on the backside of the phone? Is the phone S-ON or S-OFF?
Please read the ReadMe thread in the general section if you don't know how to answer any of the questions.
Flippy498 said:
What's the current CID of the phone? Which firmware version is currently installed? Which model name is engraved on the backside of the phone? Is the phone S-ON or S-OFF?
Please read the ReadMe thread in the general section if you don't know how to answer any of the questions.
Click to expand...
Click to collapse
current cid : htc 001 (don't remember what it was before i change it, something like 1111111)
firmware : 3.35.401.12
model : nothing on the backside (just htc) but on download mode i see "product: htc_himauhl"
S-OFF
Ok. The SuperCID (11111111) was the culprit of your initial problem. On older HTC phones it was a way to unlock kind of a region free mode. On the M9 however, that CID prevents official updates from being installed.
Is your current CID really htc 001? Or is it HTC__001? Only the latter one is written in the legit format. The former one won't work.
HTC__001 is one of the CIDs that would match your current SKU (401).
The model name in download mode can be changed via RUUs. As long as no one changed the backplate, only the engraving on the backside of the phone shows the true model name. The engraving is quite small on the downer part of the backplate. Can you please take another look and see if you can find it? The ReadMe contains some commonly asked questions. There should be one that covers the engraving.
We should only proceed with flashing RUUs if we know the model name of your phone. It's not wise to flash GSM RUUs on a CDMA phone or vice versa.
Flippy498 said:
Ok. The SuperCID (11111111) was the culprit of your initial problem. On older HTC phones it was a way to unlock kind of a region free mode. On the M9 however, that CID prevents official updates from being installed.
Is your current CID really htc 001? Or is it HTC__001? Only the latter one is written in the legit format. The former one won't work.
HTC__001 is one of the CIDs that would match your current SKU (401).
The model name in download mode can be changed via RUUs. As long as no one changed the backplate, only the engraving on the backside of the phone shows the true model name. The engraving is quite small on the downer part of the backplate. Can you please take another look and see if you can find it? The ReadMe contains some commonly asked questions. There should be one that covers the engraving.
We should only proceed with flashing RUUs if we know the model name of your phone. It's not wise to flash GSM RUUs on a CDMA phone or vice versa.
Click to expand...
Click to collapse
real cid is : HTC__001 (from getvar all)
I search everywhere with camera and there is nothing about the model, the person I bought it from told me it was refurbished, maybe thats a false case ? am I stuck ?
It's up to you to decide whether you want to try flashing the 3.35.401.12 RUU or not. All clues imply that you have a 0PJA10000. However, we don't know for sure.
In case you want to proceed: Check the MD5 sum of the file that you can find in the ReadMe thread. Flash it with the instructions for the SD card method.
Afterwards the phone should be working normally, again. Unless it's not a CDMA variant. In the latter case you would at least get problems with network reception.
Edit with another thougt that comes to my mind: What's the fastboot getvar result for your MID. Since the refurbisher used the SCID they most likely didn't know that the M9 behaves differently than older HTC phones and probably didn't change the original MID.
the getvar mid is : 0PJA10000 but i change it too and don't know the initial.
I will try the process, i don't understand what you mean by "check the MD5"
is this file is good ? : https://androidfilehost.com/?fid=23991606952597788
Is it possible to flash it with the pc instead of sd card ? if it's mandatory the sd card I will buy one
Well, if you manually changed the MID, didn't write down the original MID and there's no engraving on the backside of the phone then there's no way to know for sure which variant you own.
C.f. https://en.m.wikipedia.org/wiki/MD5
Tl;dr: Check whether the file didn't get broken during download (e.g. due to connectivity issues). The ReadMe thread suggests useful programs for that purpose.
Flashing broken files might lead to unrecoverable bricks; especially on S-OFF phones. "Good" file hosts like AndroidFileHost will always mention the reference MD5 value for their downloads.
The SD card method is the most fail safe method for flashing RUUs on a M9. That's why I recommend to use it, always. You'll want to get a card that has not more than 32 gb due to the needed format. Those cards should cost less than 10 €.
Edit: You can't use the RUU that you linked. Please read the ReadMe thread, thoroughly. That RUU uses a different encryption key. Everything you need can be found in the ReadMe thread. Trying to flash just any random RUU is quite dangerous on a S-OFF device due to the security checks being turned off. You might risk a brick.