yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] lsv-1:
I was using the same version, but when I applied the OTA I lost root, so I had to install TWRP to root it again. Busybox was still there... I have not tried a different music app, I will try another one to see how it goes...
[One (M8) Android Development] metaphz:
Increased internal storage is something to consider as well
[One (M8) Android Development] spadeace9:
Any reason why my camera stopped working after OTA update? It says cannot connect to camera camera.
[One (M8) Android Development] graffixnyc:
Yes, the reason is you didn't read the bold red text in the op

TO GET OTA UPDATES AND NOT HAVE THEM FAIL YOU WILL HAVE TO CHANGE YOUR CID TO MATCH THE GPE CID,

In fastboot mode type fastboot oem writecid GOOGL001. If you take the OTA without having your Cid set to GOOGL001 the firmware in the ota does not get flashed and anything controlled by the kernel won't work (camera, wifi etc) you must set your Cid BEFORE taking the update.
[One (M8) Android Development] spadeace9:
thank you! You're a little rude...but awesome .

"TO GET OTA UPDATES AND NOT HAVE THEM FAIL YOU WILL HAVE TO CHANGE YOUR CID TO MATCH THE GPE CID(it has yet to be determined if the mid must match the GPE as well)

In fastboot mode type fastboot oem writecid GOOGL001. If you take the OTA without having your Cid set to GOOGL001 the firmware in the ota does not get flashed and anything controlled by the kernel won't work (camera, wifi etc) you must set your Cid BEFORE taking the update. "

I did this GPe conversion as soon as I got the phone, months ago. I did the OTA update today at work and did not think about reading this forum first.
[One (M8) Android Development] petiha1:
So right now I'm at a point where I have to ask for help...

I have stock recovery, stock kernel... everything stock, but the OTA won't update neither in recovery nor through the system. Basically it tells me that the "system/app/YouTube.apk has unexpected contents" which refers to me having altered something with the app. When I converted I had to uninstall youtube (for certain reasons) with Titanium Backup and I re installed it from the Play Store.

I have tried making youtube a system app with several methods, but didn't work. I have also tried erasing and then flashing the system image from the 4.4.2 RUU but when I erase it says no permission and when I just try to flash this is what comes back:

E:\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash
system system.img
target reported max download size of 1830715392 bytes
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.003s

My next guess would be to extract the youtube.apk and the odex (if there is odex file for youtube?) from the system.img but I have no clue how to make that work as a system app on the phone after that...

Anyone with any ideas, solutions? :confused:

Thanks! :good::highfive:

EDIT:

So I extracted the YouTube.apk from the system.img and adb pushed it to /system/app and now the error I get when updating through stock recovery is "/system/build.prop has unexpected contents"

maaaan... :(:confused:
[One (M8) Android Development] graffixnyc:
I find it rude to not at least read the OP fully.. That's what it's there for ;)
[One (M8) Android Development] graffixnyc:
Something in your build.prop was changed...nothing in the original system can really be altered(root, busybox can be added, and other things can be added but nothing that was included in the original rom can be altered) as it patches some files and if they have been modified it will fail the OTA patch check.

The best bet is download the stock 4.4.2 rom version I have of stock and unzip and grab whatever you need out of there and replace your files that it's complaining about with the ones from here: http://www.androidfilehost.com/?fid=23329332407584491
[One (M8) Android Development] petiha1:
Thanks for your reply, but after having changed build.prop with the oirignal one, I think I bricked my phone. :crying:

Black screen, doesn't turn on just vibrates. Also, no bootloader, no recovery... nothing. :(
[One (M8) Android Development] rbouza1:
you realize he meant the apps you need not the build prop file itself. thats unique to your phone
[One (M8) Android Development] petiha1:
yeah, when I said original one I meant the one I backed up prior to rooting etc.
[One (M8) Android Development] mikeyinid:
youre not bricked. not from changing the build.prop. hold power + vol up + vol down for a long time. as long as it takes to get something to happen. do it over and over if you have to. try plugged in and not plugged in. itll come back to life. my advice would be to run the ruu once you do get it back up.

---------- Post added at 01:22 PM ---------- Previous post was at 01:16 PM ----------

you didnt put a sense build.prop in with the gpe system did you?
[One (M8) Android Development] petiha1:
When I hold power+volup+voldown the Google boot logo shows up but then the screen goes black. Basically, this is the issue here

as for the build.prop, no I didn't. :)

btw, thanks for the answers guys! :highfive:
[One (M8) Android Development] EddyOS:
Any UK users had experience with using a different radio at all? Just wondering if there's one better for reception over here?
[One (M8) Android Development] Zeebz:
Thanks, both of you! I think I am going to convert to the GPE edition. I'm excited to do it. I like Sense a lot, but I miss stock Android a lot more.
[One (M8) Android Development] skulldreamz:
I think 32gb plus up to a 128gb sdcard is plenty of storage lol :)
[One (M8) Android Development] Zeebz:
Just converted my phone to the GPE. Everything worked flawlessly. Thanks for this, graffixnyc.
[One (M8) Android Development] mbarrera_xda:
after i did the RUU, my phone start with the Google logo and then enter into flashboot.. never boots into the OS.. anyone know what happens here?
[One (M8) Android Development] Zeebz:
What carrier are on you on? Are you rooted and do you have S-off?
[One (M8) Android Development] mbarrera_xda:
It's a verizon version..

Yes, its rooted, s-off and changed cid to CID-GOOGL01
[One (M8) Android Development] thekalby:
This is for GSM devices only.

On a separate note, I'm getting really bad touch issues after upgrading to 4.4.3. There is a persistent ghost touch in the upper left hand corner. The phone thinks its getting repeatedly touched there. I tried flashing a different rom, I tried messing with settings, I tried everything yet the problem persists.

Any idea whats going on and how to fix it?
[One (M8) Android Development] Zeebz:
Ahh, that's the issue then. To convert to the Google Play Edition you need to have a GSM phone. GSM phones are compatible with AT&T and T-Mobile in the U.S. Verizon and Sprint use CDMA, so the GPE conversion will not work on either of those carriers.
[One (M8) Android Development] lsv-1:
Is GPE ever gonna get the photo editor update with the UFocus improvements? :rolleyes:
[One (M8) Android Development] mbarrera_xda:
There is any way to convert this verizon version to a developer edition?
[One (M8) Android Development] Zeebz:
I am not sure, honestly. I think the Developer Edition M8 is based off of the AT&T model (like the GPE) making it a GSM phone.
[One (M8) Android Development] mbarrera_xda:
So, just to double check..

my next step is to go back to sense (there is no other way since this is of GSM phones).. the link posted to back to sense is usefull for CDMA phones?
[One (M8) Android Development] Zeebz:
I would assume so. In the back to Sense thread it doesn't specify that the phone has to be GSM, but at the same time it's written for phones that were converted to GPEs so I am not sure if it assumes that you're using a GSM phone or if it applies to all types. I'd go into that thread and ask as someone might be able to provide much better insight into it than I can.
[One (M8) Android Development] EddyOS:
It already does. Open the camera app, then swipe to open a photo then go to Edit and select HTC Photos and voila - uFocus is available! :D

---------- Post added at 09:37 AM ---------- Previous post was at 09:36 AM ----------

The link won't work for CDMA, only GSM. If you have the Verizon RUU you can just flash that I suppose but I honestly don't know...
[One (M8) Android Development] leon912:
HTC has updated the htc gallery app. Now ufocus can change the level of background blur.

How can the GPE version get this update?
[One (M8) Android Development] EddyOS:
I'd assume GPe might get the update at some point if HTC/Google agree it needs to be added but as the GPe doesn't actually have HTC Gallery installed it may not arrive...
[One (M8) Android Development] EddyOS:
Thought I'd post a mirror of the unrooted 4.4.3 RUU...

https://www.hightail.com/download/ZUcwblRqaytGOFJnRXNUQw
[One (M8) Android Development] faresrouabah:
screenshots not working

I flashed this ruu, the rooted version,and everything is working perfectly. Except I'm unable to take a screenshot for some reason. I've tried every combination of the power button, and can't get it working. Did I get something wrong or is there some weird combination for GPE?

Thanks

Figured it out. I feel dumb. Sorry and disregard this.
[One (M8) Android Development] newstar:
what is actual MID for cid GOOGL1 ? i mean actual mid for GPE ?
[One (M8) Android Development] BrandonPrice31:
I'm wondering this as well? How do we change MID as well?
[One (M8) Android Development] newstar:
There is thread in forum , follow it

---------- Post added at 05:31 AM ---------- Previous post was at 05:30 AM ----------

I flash 4.4.2 and change mid to 12000 and almost try every cid , but nothing give me ota update ...
[One (M8) Android Development] BrandonPrice31:
Your MID didn't fit into the 6 ones that are in the update?
[One (M8) Android Development] drawde40599:
I would assume never since play phones are "AOSP" . if its that good someone may get a working port but I wouldn't hold my breath waiting for it or anything else sense .
[One (M8) Android Development] rbouza1:
ive got htc photo edit built in 4.4.3 gpe and ufocus works great.
[One (M8) Android Development] drawde40599:
Then what's the other guy asking for it then ;P
[One (M8) Android Development] rbouza1:
maybe not doing it right. long press pic in gallery and go to 3 dot button and choose edit. from there you can select.htc photo . im mostly stock
[One (M8) Android Development] rbouza1:
sorry graffixnyc for non ruu posts. ?
[One (M8) Android Development] a1428185:
Hi,

when I got my M8, I made it s-off, flashed PhilZ Touch and installed the GPE ROM regarding to this thread.

As this is not able to use OTA updates, I switched to the 4.4.2 RUU today. (I used 4.4.2 so it was easier to backup and restore all apps and settings.)

Now I have some questions:

Does the RUU also flash the recovery, or should I do it my self? What version do I need (the "GPE" [1.16.1700.16] recovery or my Vodafone recovery [which I don't have])?

Currently I have installed the recovery.img from the RUU.zip, but if I boot into recovery, I get an android holding a red sign.
[One (M8) Android Development] rbouza1:
ruu flashes stock recovery. and what you see with red sign is stock recovery.
[One (M8) Android Development] a1428185:
Thank you for your answer.

I thought a menu has to show up instantly, and the android-logo was a sign for a broken recovery. ;) I missed the point, that I have to hold volume up and press the power button.

So now I just have to wait for the OTA message to see if everthing is working.
[One (M8) Android Development] mikeyinid:
Make sure you read the OP concerning the OTA. You have to have Google cid or the boot.img wont install and camera will be broke and other issues.
[One (M8) Android Development] a1428185:
I already have the Google CID. ;)

If something will go wrong, I have everything backed up, so I can reinstall the 4.4.2 RUU.

*EDIT*

As soon as (and IF) I get the OTA notification, I will give it a try. A report will follow.
[One (M8) Android Development] BrandonPrice31:
Let us know if you get the OTA and if it works.
[One (M8) Android Development] ammurad:
OTA help with MID

Hey folks,

Probably a really silly question. I've done everything for GPE conversion on my m8 - all working OK (s-off, change cid, flashRUU). my CID is GOOGL001

I just checked my MID though and it's 0P6B10000, is this still ok for OTA updates in the future? Just want to be sure that i dont have to change it, the OP didn't mention this particular MID.

Love the stock android feel. Thanks to all for making this happen with S-off
[One (M8) Android Development] newstar:
I think we all don't know real MID for CID GOOGL1 , because i try all MID`s in OP and try all cid`s in OP and flash 4.4.2 GPE but none of mid/cid Push me 4.4.3 OTA

---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------

That is the question No one knows yet :) .. either CID is enough for GPE or MID also ......
[One (M8) Android Development] ammurad:
Thanks. I also flashed 4.4.2 with a GOOGL001 CID and MID updated in the txt file of the zip file, but like you 4.4.3 was not pushed to my device. :(
[One (M8) Android Development] newstar:
Until is some other one share good matched MID or CID, this will be remain a question :)

Some one with developer edition and on 4.4.2 can confirm if he get ota for 4.4.3

Posted From HTC 1 M8 via TapaTalk Pro .
[One (M8) Android Development] mikeyinid:
A whole bunch of people have received the OTA.
[One (M8) Android Development] Henry_Jones:
Hello,

I've used the former 4.4.2 RUU to convert to GPE. Unfortunately I missed the change to the first entry in the thread (about the Google cid) and took the OTA with the original T-Mobile CID.

The OTA failed completely, no part was installed. I'm still on 4.4.2 and WiFi and camera are working.

After I changed the cid to GOOGL001 and some restarts I don't get offered the update again. I also cleared the data in the "Google Framework" and restarted as suggested by someone in this thread, but to no avail.

I had copied the OTA file after it was downloaded completly, if this is any help. Maybe it must only be copied to the right place and the phone started in (factory) recovery mode ?

Any ideas ?

Or if this is not possible, is there another way to update to 4.4.3 with keeping the conversion benefits ? I've seen it mentioned in the thread as well, but was unable to find something like it.
[One (M8) Android Development] ammurad:
You can do what I did, which is flash the 4.4.3 RUU (in the OP). I had the same issue, my cid was GOOGL001 and mid matched fine however, ota wasn't getting pushed on 4.4.2. Could be a google server issue?!
[One (M8) Android Development] Henry_Jones:
Yeah, thought about that, but as I need the device everyday, the prospect of having half a day work with backup and restore, the need for the update must grow for a while ;)

I found some People mention to Flash the update zip with a custom recovery, but I guess this will not work, will it ?
[One (M8) Android Development] Zeebz:
I would think you'd be able to just sideload it with adb. Put the update.zip into your Android SDK folder, then open command prompt from within the folder, then type 'adb reboot bootloader' without the quotes, then when you're in the bootloader type 'adb sideload update.zip' again, without the quotes. That should push the update to your device manually.
[One (M8) Android Development] BrandonPrice31:
Is pocket detection built into stock kernel?

Meaning when you put your phone into your pocket double tap 2 wake and other gestures won't work.

Is this part of the stock kernel?

Seems to be on my stock kernel?
[One (M8) Android Development] HolyAngel:
If you have the 4.4.3 ota zip and on 4.4.2 gpe, just flash the stock gpe recovery, put the ota on sdcard and flash it through the gpe stock recovery. it'll install just fine. Thats how I did it to make a clean nand.
[One (M8) Android Development] graffixnyc:
I believe the Developer edition has the same MID as the AT&T version as does the GPE (I'm pretty sure I confirmed that but I could be wrong) I forget if the TMO one had the same MID I THINK it did as well, but I do remember those 3 having the same MID IIRC.

What we really need is someone with a completly different MID to tell us if they got the OTA update.. OR someone who has the same MID that got the OTA before change it to a different one, flash the 4.4.2 RUU and see if they get the OTA.. if not, switch it back.

I would do this but don't really have the time.. I'm in an accelerated summer semester and already have a midterm tomorrow, then final in a couple weeks before I start a 2nd half of the summer semester class which is one week shorter then the first half :eek:
[One (M8) Android Development] hasteveha:
I have an at&t htc one m8 that I flashed to a gpe edition. Everything has been working great. I just noticed the flash for the camera is not working. I downloaded a flashlight app also to test it. Anyone else have this problem? Any suggestions?

Thanks,

Steve
[One (M8) Android Development] EddyOS:
I'm gonna guess that you've not read the red writing in the OP telling you that you HAVE to have the GOOGL001 CID set on the phone otherwise things break...
[One (M8) Android Development] Henry_Jones:
Hm, tried that. It works (Android with some kind of cube rotating) for a while but finally showing an Android on its back with a red triangle and the message "kein Befehl". Maybe "no command" in english. It's the same result if I Keep the original Name or rename it update.zip. It tries to do something with the file, if I delete it, the rcovery only results in a black Screen.

Still have to try the sideload procedure.

Has someone the OTA file and can give me the hash of it ? Maybe I changed it somehow, not that I knew when or how.

---------- Post added at 09:19 AM ---------- Previous post was at 09:11 AM ----------

Hello, after the first command I end up in FASTBOOT USB Mode, is this correct ? In this mode the adb commands do not work, as far as I know. The second command replies with "error: device not found" which seems to be consistent ;)
[One (M8) Android Development] HolyAngel:
The no command/android on its back is normal for stock recovery, when it gets there you need to press power+volume up for a second or two and it'll give you a menu in recovery. Then choose update from sdcard or whatever and find and choose the ota zip and flash it, itll work. Don't need to rename it or anything.
[One (M8) Android Development] Henry_Jones:
Will there ever be a time when one knows everything about Android ;) I guess not. Never knew that there is a menu in stock recovery.

Anyway it fails now after some checks with ""/System/priv-app/SystemUI.apk" has unexpected contents. I'm quiet sure I never changed this file.

You still have an idea ?

Ok, edit: Found it ! Yeah 4.4.3 running now !! Thank you very much.

I extracted the SystemUI.apk from the RUU 4.4.2 I still had and replced the one on the phone (which was different). Then the update run through.

The only idea about that, I use SoftKeyz to resize the softbuttons to a smaller kind. Maybe this app changes the SystemUI.apk ?

Root was lost in the process but was easily restored with cwm and SuperSu.zip.
[One (M8) Android Development] HolyAngel:
Hash checking failed so the file has been touched by something. Only thing to do at that point is either reflash ruu or find a 100% stock ROM and replace your systemui.apk with one from the stock ROM zip and then retry the ota in stock recovery.
[One (M8) Android Development] Henry_Jones:
You're right, I had the same idea and edited the former post to reflect that.

Thank you again, I've learned a lot today.
[One (M8) Android Development] hasteveha:
I did do that part. I didn't need to accept any over the air updates either.

I ended up charging the phone over night, and rebooting in the morning. The camera flash works. Maybe the battery was low.

Thanks,
[One (M8) Android Development] Zeebz:
There's also a chance you had HDR on. If you have HDR on it disable the camera flash. Someone had that issue somewhere else in the thread where their flash was grayed out in the camera app and it turned out it was because they had HDR enabled.

As for the error with sideloading, did you try typing adb devices once you were in the bootloader to make sure your device was recognized? Maybe I am just wrong about sideloading and you can't do it. I did it on my Nexus 4 and figured since a lot of the adb commands are similar for the M8 that you could sideload through adb, also.
[One (M8) Android Development] PatrickVas:
Figured out the correct MID

So just to figure out this OTA situation, I flashed the older 4.4.2 RUU to my T-Mobile M8. Before I did though, I changed the CID to GOOGL001, and here comes the important part, I changed the MID to 0P6B17000, which thanks to some digging around in the change MID thread and Anandtech, turned out the be the real GPE MID. After I booted into 4.4.2, the phone instantaneously notified me of an OTA, 4.4.3, and it successfully updated!

tl;dr - the correct GPE MID is 0P6B17000, OTAs will work after changing it to this
[One (M8) Android Development] cc999:
MID

Whats the procedure to change MID to 0P6B17000?

CC
[One (M8) Android Development] EddyOS:
I don't quite get how this works as the android-info.txt in the OTA list ALL M8 variant MIDs as compatible...

modelid: 0P6B10000

modelid: 0P6B50000

modelid: 0P6B60000

modelid: 0P6B12000

modelid: 0P6B13000

modelid: 0P6B11000

modelid: 0P6B15000

modelid: 0P6B16000

modelid: 0P6B17000

cidnum: GOOGL001

mainver: 2.10.1700.4

btype:0

aareport:1

hbootpreupdate:3

So therefore the MID shouldn't matter...

---------- Post added at 11:59 AM ---------- Previous post was at 11:47 AM ----------

And to prove my point, just flashed the 4.4.2 stock, unrooted RUU, changed CID to GOOGL001 but left MID as the EU unbranded phone and just got the 4.4.3 OTA
[One (M8) Android Development] ammurad:
What was your MID?

Also did you change cid after your flashed the RUu?
[One (M8) Android Development] EddyOS:
From the beginning...

I was on 100% stock (bar S-OFF) 1.54.401.10, CID HTC__001, MID 0P6B10000 - literally standard EU unbranded

I booted in fastboot and first changed the CID to GOOGL001 (fastboot oem writecid GOOGL001)

I then booted into RUU mode (fastboot oem rebootRUU) and flashed the 4.4.2 RUU

I then rebooted the phone and on first boot it gave me the OTA to 4.4.3

Literally as simple as that

---------- Post added at 02:22 PM ---------- Previous post was at 02:09 PM ----------

Here's my getvar all read out for reference after updating to 4.4.3...

C:\Users\eosullivan>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.18.0.0000

(bootloader) version-baseband: 1.14.21331931.LA02_2G

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 2.10.1700.4

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno: ************

(bootloader) imei: ***************

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B10000

(bootloader) cidnum: GOOGL001

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 01eccc75

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.018s
[One (M8) Android Development] a1428185:
I changed the CID to GOOGL001 before flashing the 4.4.2 RUU (after I made the mistake to install the GPe ROM ;)). I did'nt change the MID.

It took some time (you have to hit the rollout wave), but today I got the OTA notification and I was able to successfully install 4.4.3.
[One (M8) Android Development] iOSecure:
I'll just wait for Google to push 4.4.4 to GPE devices and let you know, should be soon now. OTA went out for Nexus devices this morning