yashsingh1/xdaforums huggingface dataset:
[One (M9) General] DeadPotato:
Depends on what are you coming from, if you had 1.40 base the battery seems pretty similar, if you're coming from an 1.32 base, you'll notice improvements

And yes it's too soon to make a final conclusion

---------- Post added at 01:41 AM ---------- Previous post was at 01:40 AM ----------

The M9 is block based OTA, if you have anything that's not expected on the partitions the OTA will fail, that of course includes SU binaries
[One (M9) General] matthewstice:
I thought the base for the roms u want to try have to match your firmware version .. or maybe you just have to have firmware versions "equal to or above" what is used as the roms base for them to function without reboots etc.

Updated to 2.8.617

So I can use all the roms(viper,eragon,maximum,arhd) based still on the 2.6 leaked firmware etc and have no issues since both are Android 5.1?
[One (M9) General] fernandezhjr:
The ones you have already been playing with should be good. You are not likely to see any battery difference going from 2.7 to 2.8.
[One (M9) General] slvrhwk:
Sorry to ask a noob question, but I just want to be doubly sure and not brick my device. I have a Dev edition (bootloader unlocked) with stock rom, stock firmware, rooted and S-On. Can someone please tell me how do I upgrade my device to 5.1? Is it possible to do it without deleting any user data (dirty flash)? Do I need to flash the firmware as well? Please help me out, thanks.
[One (M9) General] kamocheng:
Big/noticable changes? Hmm

1. No longer options for saving mode (cpu max,brightnes,etc). Once u choose save mode then that's it

2.Play store is kinda different i guess?

3.Camera is quiet improved

4.Battery? Not sure yet i think its better

5.Heat issue? Well i live in tropical country so it feels no different

6.Flashlight app!! lel

Overall? Go for the update!! Its totally worth it!!!!
[One (M9) General] matthewstice:
S off to be safe. Make sure to supercid 1111111 or set appropriate cid and flash away firmware any 2.8 is newest.

---------- Post added at 07:20 AM ---------- Previous post was at 07:18 AM ----------

Did not notice any difference besides better camera. Battery same if not worse need to try all roms as its new

---------- Post added at 07:22 AM ---------- Previous post was at 07:20 AM ----------

Sorry flash twrp recovery as well via fastboot
[One (M9) General] dratsablive:
But you already had a flashlight in the dropdown quick settings.

---------- Post added at 04:59 PM ---------- Previous post was at 04:58 PM ----------

I had a problem sending MMS messages, and found that ADBLOCK was preventing me from sending them.
[One (M9) General] DeadPotato:
Super CID will cause issues on the M9 with OTAs, pick a CID matching the region of the OTA. I think you could but since there's a change on the major version, a full wipe it's highly recommended.

EDIT: didn't notice you're on stock ROM. If you're rooted you may have problems with the OTA, unroot first and dirty flash is possible. You can also run an RUU, but that will wipe your user data
[One (M9) General] RCGodward:
Anybody having trouble with LTE on this update? My phone will show a strong signal but most web pages will stall out before they finish loading. Setting my network mode to 2G/3G will fix it. Rolled back to 1.32... last night and it worked fine, but the problem came back after I installed the OTA.
[One (M9) General] jollywhitefoot:
LTE works awesome here. No trouble what so ever. See attachment.
[One (M9) General] RCGodward:
That's the strange thing. I'll get great (for my area) speed tests and most other apps work well, but Chrome and Firefox won't load sites on LTE.
[One (M9) General] fergie_uk:
Hello,

I have a stock locked bootloader M9, can someone run through the processes to convert to a GPE please?

Kind regards

David
[One (M9) General] jollywhitefoot:
Sorry, but there's no google play edition for the m9.
[One (M9) General] fergie_uk:
Oh my mistake I misread the thread.

I'm after a pure android experience.

Kind regards

David
[One (M9) General] jollywhitefoot:
CM is coming, but there are still issues. You can follow it in the original development thread and the Q&A section
[One (M9) General] nuts77:
Hi there !

quick question, as I just switched to developer edition (my M9 has s-off) to try the update. I changed MID to 0PJA11000 and CID to BS_US002, flashed 1.32.617 RUU and flashed OTA to 2.18.617.4 manually through stock recovery. Everything worked flawlessly. But I'm just wondering why I get the red warning flag when booting up, since my bootloader is relocked (I need to have it locked as I'm using MobileIron for work) and software status appears as "official" in the bootloader... Does every DevEd phone has the red warning in the ABoot?

Thanks!
[One (M9) General] jollywhitefoot:
You get the red warning because you're S-off. You can find versions of aboot in the development section where the red text has been removed.

http://xdaforums.com/one-m9/development/firmware-red-t3097678
[One (M9) General] nuts77:
Oh, OK. I thought the red warning was only when bootloader was unlocked. Thanks !
[One (M9) General] MegaGalan:
M9 Developers Edition 5.1 Full RUU is out now :

http://www.htc.com/us/support/htc-one-m9/news/
[One (M9) General] blueberry60:
I think this RUU is corrupt,I have extracted as ruu.zip from Ruu.exe,Ruu zip files that I have extracted from other official RUU.exe files work properly.You can try on to validate.I recommend you not to flash for security and brick probability.
[One (M9) General] marksedge:
Hey as a side note running the dev edition kills my thrill to flash roms ..so cheers to no more sleepless nights and xda on the jon
[One (M9) General] clsA:
Did you use htc_fastboot

Normal fastboot won't work on rom.zip pulled from the RUU. It will also flash fine by renaming and flashing from ex_sdcard
[One (M9) General] blueberry60:
I didn't flash ROM.zip file as 0PJAIMG that I pulled from the RUU with "%temp%" method .I controlled various rom.zip files that I pulled from other official RUU exe files with %temp% method (e.g.1.32.401.17 RUU),I could have extracted android-info.txt and boot,dzdata files to desktop succesfully,but I couldn't have extracted this files to desktop because of corrupted archive error in only 2.8.617.4 RUU.
[One (M9) General] clsA:
It's encrypted

You can't just extract it, theirs a thread in the developer section on how to extract the contains of rom.zip using 7zip

http://xdaforums.com/showthread.php?t=3062808

[DEV] How to extract One M9 ROM and dump system image
[One (M9) General] blueberry60:
But I extracted easily the contains of rom.zip related to 1.32.401.17 RUU.exe,I haven't got any problem on that.

I run the RUU as administrator and opened the start menu and run " %temp%" command .I wrote "zip" to AppData-->Local-->Temp window,choosed rom,copied and paste rom.zip to the desktop when RUU runs as administrator.
[One (M9) General] clsA:
Read the thread I linked, I'm confident you'll figure it out
[One (M9) General] blueberry60:
I think creating rom.zip from RUU is different than extracting rom zip I couldn't explain my process to you accurately.
[One (M9) General] clsA:
Did you try it?

Use 7 zip you'll see
[One (M9) General] Strangeland16:
just installed and ruu is working fine. only question i have is whenever i reinstall a ruu.zp or a ruu.exe i still get the red warning a boot its not a problem as ill just flash moded a boot but i thought flashing a official ruu should stop the red a boot text so why do i still get the warning please ??
[One (M9) General] clsA:
I think it's because of S-Off
[One (M9) General] DeadPotato:
Indeed it is, actually you also get a message on the first setup saying despite of the privacy policies that's an HTC testing device and the reporting can't be disabled as a consequence of being S-OFF
[One (M9) General] ozo1ozo:
Yep
[One (M9) General] robstunner:
Anyone try the M9 with a Turbo Charger? It doesnt quick charge :(
[One (M9) General] blueberry60:
I tried to extract rom.zip that I created from 2.8.617.4 RUU.exe with 7 zip and I opened rom.zip archive (2nd one with the arrow) > #. I opened 2.zip and 4 zip in archive to an empty folder,but there is no system.img_0 file in neither 2.zip nor 4.zip:
[One (M9) General] clsA:
Yeah your getting their

I'm away from my PC, but I recall having 4 zips in the rom.zip not 2
[One (M9) General] blueberry60:
It is very strange.I created rom.zip with different method named as Mıcrosoft Process Monitor,but I am having 2.zip and 4.zip again.

How to extract rom.zip from RUU ?

http://xdaforums.com/showthread.php?t=2534428
[One (M9) General] clsA:
you should get this from the rom.zip
[One (M9) General] blueberry60:
But this is 1.32.502.9 Ruu,I mentioned about 2.8.617.4 Ruu,my rom.zip has been pulled from last 2.8.617.4 RUU.exe .
[One (M9) General] muayyadf1:
It works for me. Take out any case you have on the phone to dissipate heat better. Also, don't use the phone while charging.
[One (M9) General] robstunner:
weird, no case no problems with other phones.
[One (M9) General] clsA:
it was an example

seems the new Developer Edition RUU Rom.zip 2.8.617.4 posted below has a new Encryption on it ..i can't extract it either

maybe [MENTION=2605798]nkk71[/MENTION] would like to take a crack at it

I'll post the link to it here >> RUU_HIMA_UL_L51_SENSE70_ATT_MR_NA_Gen_Unlock_2.8.617.4_Radio_01.01_U11440601_76.03.50611G_F_release_439079_signed_2_rom.zip
[One (M9) General] muayyadf1:
When temperature reaches 110 F, QC2 switches to slowest normal charging setting to let the battery cool down.
[One (M9) General] robstunner:
it was just charging on its own, wasnt using it. just noticed when i turned it on the notification of slow charging on the lock screen. oh well.
[One (M9) General] muayyadf1:
You have a bad cable. Try another one.
[One (M9) General] robstunner:
I will tonight. Not a bad cable though, my S6 quick charges from it just fine.
[One (M9) General] fernandezhjr:
Then you have a bad phone, possibly the charging port. Send it off for repair.
[One (M9) General] nkk71:
hmm, close but not just yet :o

nkk71@ubuntu:/mnt/hgfs/W/zUBUNTU/m9encRUU$ ./ruuveal -K bin2 2.8.617.4_rom.zip BLA1.zip
ruuveal
-------

Large zip format detected containing 7 zipfile(s)
Decrypted RUU (zip) written to: 01_BLA1.zip
Decrypted RUU (zip) written to: 02_BLA1.zip
Decrypted RUU (zip) written to: 03_BLA1.zip
Decrypted RUU (zip) written to: 04_BLA1.zip
Decrypted RUU (zip) written to: 05_BLA1.zip
Decrypted RUU (zip) written to: 06_BLA1.zip
invalid htc aes encrypted zip file!
nkk71@ubuntu:/mnt/hgfs/W/zUBUNTU/m9encRUU$ unzip -t '*_BLA1.zip'
Archive: 01_BLA1.zip
testing: android-info.txt OK
testing: aboot_signed.img OK
testing: radio.img OK
testing: rcdata.img OK
testing: splash1.nb0 OK
testing: adsp.img OK
testing: ramdisk.img OK
testing: modem_st1.img OK
testing: modem_st2.img OK
testing: android-info2.txt OK
testing: sensor_hub.img OK
testing: tp_MXM11876.img OK
testing: sdi.img OK
testing: emmc_appsboot.mbn OK
testing: cir.img OK
testing: persist.img OK
testing: dt.img OK
testing: sbl1-8994-1.img OK
testing: tp_SYN3351.img OK
testing: bootloader OK
testing: gpt_main_32g.img OK
testing: gpt_main_64g.img OK
testing: pmic-8994-1.img OK
testing: cpe.img OK
testing: pg2fs_ship_signkey.img OK
testing: apppreload.img OK
testing: rpm-8994-1.img OK
testing: tz-8994-1.img OK
testing: hyp-8994-1.img OK
testing: cota.img OK
testing: recovery_signed.img OK
testing: hosd_signed.img OK
testing: boot_signed.img OK
testing: backup_android-info.txt OK
No errors detected in compressed data of 01_BLA1.zip.

Archive: 02_BLA1.zip
testing: system.img_00 OK
testing: android-info.txt OK
No errors detected in compressed data of 02_BLA1.zip.

Archive: 03_BLA1.zip
testing: system.img_01 OK
testing: android-info.txt OK
No errors detected in compressed data of 03_BLA1.zip.

Archive: 04_BLA1.zip
testing: system.img_02 OK
testing: android-info.txt OK
No errors detected in compressed data of 04_BLA1.zip.

Archive: 05_BLA1.zip
testing: system.img_03 OK
testing: android-info.txt OK
No errors detected in compressed data of 05_BLA1.zip.

Archive: 06_BLA1.zip
testing: system.img_04
error: invalid compressed data to inflate
testing: android-info.txt OK
At least one error was detected in 06_BLA1.zip.

5 archives were successfully processed.
1 archive had fatal errors.

more testing later...
[One (M9) General] Prasad:
No TMo update in sight ?
[One (M9) General] blueberry60:
Congratulation !.. How did you manage to that? You had extracted all system.img_0* files.
[One (M9) General] nkk71:
everything looks good:

nkk71@ubuntu:/mnt/hgfs/W/zUBUNTU/m9encRUU/2.8.617.4_rom_decrypted/system$ e2fsck -nvf system_hima.img
e2fsck 1.42 (29-Nov-2011)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

4521 inodes used (1.58%)
0 non-contiguous files (0.0%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 4369
978920 blocks used (85.36%)
0 bad blocks
0 large files

3728 regular files
652 directories
0 character device files
0 block device files
0 fifos
0 links
132 symbolic links (132 fast symbolic links)
0 sockets
--------
4512 files

file list attached (it's kinda long :p)

EDIT: [MENTION=2895182]clsA[/MENTION] you got a hash for an untouched system partition? wanna compare to the "concatenated" one and try to figure out why/if they dont match
[One (M9) General] OGhoul:
Hahaha, so true.
[One (M9) General] clsA:
The TWRP system.img is in my AFH folder. It was 4.4 gb
[One (M9) General] nkk71:
okay i'm confused now, 4.4GB but your afh says:

my hashes show:

nkk71@ubuntu:/mnt/hgfs/W/zUBUNTU/m9encRUU/2.8.617.4_rom_decrypted/system$ sha1sum system_hima.img
6ec11277985063491d8fc62bbce49c6646cdfca1 system_hima.img

nkk71@ubuntu:/mnt/hgfs/W/zUBUNTU/m9encRUU/2.8.617.4_rom_decrypted/system$ md5sum system_hima.img
c60d5b340231e3827a339bdd69faf0ba system_hima.img

EDIT, nvm, it is actually 4GB+, since you have the OTA's, would you mind checking the SHA-1 sum(s) in there?
[One (M9) General] clsA:
I had to reup that file 3 times .. the AFH stats are wrong the file downloads 4.4gb and md5 is correct in my notes

the SHA-1 = C:\adb>F:\Downloads\sha1sum.exe E:\2.8.617.4_system.img

6ec11277985063491d8fc62bbce49c6646cdfca1 E:\2.8.617.4_system.img
[One (M9) General] muayyadf1:
So I have been testing the m9's compatibility with qc2.0 and it appears that the phone doesn't like QC adapters. It stops charging as a result of battery reaching over temperature. I will not use QC adapters with this phone. The M8 was just fine though.
[One (M9) General] hamdir:
enable powersaver during QC and you should be fine, especially on the 2.x firmware
[One (M9) General] muayyadf1:
I don't think that will make a difference. The back of the phone feels normal but battery temp shows 45C when phone stops charging. Battery gets warm internally but phone never gets too hot. Also, I noticed temp drops immediately after stopping charging by at least 4 degrees in less than 30 seconds. This tells me the battery sensor placed where battery gets hot the most preventing QC.
[One (M9) General] clsA:
[MENTION=3182548]coolberry[/MENTION]

the file is on my AFH now >> Removed until I test it further

Thanks for all your help and hard work nkk71
[One (M9) General] nkk71:
sure no problem,

did you try it? is the M9 able to properly unzip the ZIP64 ruu?
[One (M9) General] clsA:
no I'm a little busy this week .. it would be the weekend before i could test it
[One (M9) General] jollywhitefoot:
I'll probably test this tonight. I was going to run the ATT ruu to get the new att update anyway.

Edit: I can't get it to work. I renamed to 0PJAIMG.ZIP and placed in the root of external SD, reboot to download mode, but don't get prompted to install it. I tried flashing via htc_fastboot, but that gives me a fastboot crash (htc_fastboot has stopped responding). I am able to unzip the file on my PC, so I don't think it's an upload/download issue.
[One (M9) General] clsA:
Alright, I'll recompress it and upload it again tonight after I test it my self
[One (M9) General] effortless:
Tmo and Verizon update on the 20th
[One (M9) General] anandlal:
QC works great on the 2.8 firmware for me. I use an Aukey charger. Phone gets hot while charging but cools off once it gets to 90%.
[One (M9) General] nkk71:
1- Isn't the filename case sensitive "0PJAIMG.zip" even if it's unable to unzip properly, it should at least prompt you (note that I haven't used the sdcard method ever since the HTC Sensation days)

2- which htc_fastboot -version are you using, the one in the 2.8.617.4 RUU.EXE is htc_fastboot version 3.0.9.2

(are you running it in an admin command prompt)

I've tried various compression methods, but given the size of the files, it will most likely always be a zip64 archive.

Only alternatives I can think of:

Remove system.img from the zip, and flash that manually

Create an unencrypted LargeZip like the original ruu, which kinda defeats the purpose since you cant "easily" extract stuff from it

Create one zip for everything except system, and another one for system (but even system would have to be split up)

though I'm slightly surprised that zip64 isnt supported, these ruu's are getting bigger and bigger, so HTC should start supporting it

EDIT: sorry I can't test it myself at the moment, but need the phone up and running :o
[One (M9) General] jollywhitefoot:
zip was lower case. that was a typo in my post. I've never used 0PJAIMG method before either, so I may have done something wrong, but it seems pretty straight forward.

My htc_fastboot is older (2.0.8). Do you have the new version extracted anywhere that I can download? I did not run command prompt as admin. I've flashed the 1.32.617 zip many times without issue, but I know that's no guarantee that the same methods will work for the newer packages.

I might have time to test more tonight.
[One (M9) General] nkk71:
I've never used the sdcard method myself, so can't help much there, though it is (or at least should) probably the "easiest" method

the newer fastboot is in my dropbox folder (for now) here https://www.dropbox.com/s/tvw2tif4l2hgx4r/htc_fastboot_3.0.9.2.exe?dl=0

note that windows defender doesnt like it, so you may get a "virus" warning, my AV didnt have anything to object, and i did run it through

https://www.virustotal.com/en/file/...94cffcfcf39dcd7f4eeb3e12/analysis/1436873161/

so i guess it's safe, not sure why the warnings, etc. but I pulled it from the RUU.EXE downloaded directly from HTC's site (not a third party site)
[One (M9) General] jollywhitefoot:
Thanks. I got the new version and will try it out when I have time.
[One (M9) General] nkk71:
Cool, good luck, and keep us posted

also try the sdcard method again since that's seems to be many people's preference, if i get a chance (backup :crying:), i may try myself

EDIT: hmm, i could just try the system partition in ruu-zip format :rolleyes::eek:
[One (M9) General] clsA:
Using windows send to compressed folder dooms to work. I have it re zipped but like you I need the phone the next couple days and have little time to test

The was uploading when I left for work

Same filename with REDO.zip added
[One (M9) General] nkk71:
i dont see how "windows send to" command could do a better conversion. there are limits, but since i never tested myself, i cant say :cyclops:

---------- Post added at 22:10 ---------- Previous post was at 22:07 ----------

and if i remember correctly, your sdcard has to be FAT32 and small-ish, or something along those lines :p
[One (M9) General] clsA:
The windows compression is what I use with Roms downloaded from TortoiseSVN (never fails)

tried both your's and mine renamed to 0PJAIMG.zip on 32gig sdcard both failed (first image)

used the rom.zip from the RUU same sdcard same file named flashed first try (second image)
[One (M9) General] nkk71:
Error 12 would indicate "out of memory" (i think), which would make perfect sense, where would it even be able to unzip 5GB (the unzipped size of the entire ruu) :eek:

the phone only has 3GB of RAM, and not all that would be available either

the encrypted RUU, is compromised of 7 zips, the largest of which is around 800MB
[One (M9) General] nkk71:
Unfortunately, a couple of problems with that, amongst them

We can't tell ruu flash what to do, that's hardcoded by HTC

I'm not even sure that's the error, or if it's just unable to decompress a zip64 zip

RUU will wipe the filesystem, so it'll be a catch 22

in case the filesystem is encrypted, it's going to be hard to use it

I honestly haven't tried myself, but I guess there are options one could try, but obviously the easiest would be:

a) remove the system.img from the zip, flash remaining RUU normally, then "htc_fastboot flash system system.img"

Since android-info, has the "resparseoption: -S800M", one could try

b) using htc_fastboot (v 3.0.9.2), see if it's able to send it "in parts"

c) try zipping it with the original system_00.img through system_05.img and see if that works

but I guess option a would be the easiest and should work fine (alternatively just use the encrypted RUU)

Unfortunately RUUing is not my favourite thing to do, as I do use my M9 as my daily phone, so need it up and running most of the time
[One (M9) General] LLegion:
really? sirs....just do the sdcard method is the fastest and safest way to do it just in a manner of few hits, you have to consider that the cid/mid must match for the ruu-zip and thats all, i just didt for myself with chingonazo´s file at no issue at all!!! just flash twrp2.8.7.1-b and supersu 2.49beta it works amazing!!!!
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] rgerrans:
I saw a few posts about the loss of face unlock in 5.1 but stumbled on to it in trying to find out where trusted device settings went.

In the Security settings at the bottom there is an option for 'Trusted Agents'

Within that you need to enable 'Smart Lock'

That creates a new 'Smart Lock' section within the Security settings page

That contains trusted devices and face unlock but also adds location, carry and other unlock options as well.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] flyingyogi:
Thanks for the info, I really like the unlock features especially in the at home mode.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] demmo86rt:
Thanks for posting, I stumbled upon this myself after a while, but at first I thought Verizon had pulled the feature.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] CrazyRussianXDA:
Thanks for posting this
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] CaptCuervo:
Thanks, Face unlock works again.
[Galaxy S 5 Q&A, Help & Troubleshooting] tornido067:
Is there any custom kernel for g900h ?
[Galaxy S 5 Q&A, Help & Troubleshooting] yanis488:
aqua kernel by sandeepEmekar

Custom kernel for sm galaxy g900h :There is aqua kernel by

SandeepEmekar or use search in forum good luck
[Huawei Ascend Mate 2] xordos:
Carrier text, this can be disabled in settings - Display.
[Huawei Ascend Mate 2] ArkAngel06:
Nice, I was hoping something's would be easy.
[Huawei Ascend Mate 2] Iguanadon:
Only launcher I have found with transparent navbar is Holo Launcher HD

[URL="https://play.google.com/store/apps/details?id=com.mobint.hololauncher.hd"]https://play.google.com/store/apps/details?id=com.mobint.hololauncher.hd[/URL]
[Huawei Ascend Mate 2] medwatt:
The app "Browser" doesn't work at screen dpi 264 & 268. I've tried other higher values, however the soft menus at the bottom of the screen are not properly centered.

Is there a way to change app dpi without using xposed?
[Huawei Ascend Mate 2] ArkAngel06:
Nope. You can either keep upping the whole phone DPI little by little, or maybe use a different browser. I haven't noticed any discrepancies yet in my apps with 264.
[Huawei Ascend Mate 2] medwatt:
Is the "browser" app launching in your phone?
[Huawei Ascend Mate 2] tdamocles:
I'm at 240 dpi and it doesn't open for me.
[Huawei Ascend Mate 2] medwatt:
It opens at dpi 270+ but the soft buttons at the buttom of the screen are not centered!
[Huawei Ascend Mate 2] ArkAngel06:
No, I just checked, it just crashes. I always freeze that app though.