yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] miki4:
If you go to this link and download the "Firmware without stock recovery & Boot IMG" which samhhmobil flashed, you will notice that it only has about 500 kB and when you open it, you will see that it only contains hboot.

The version number which changed in his screenshot is hardcoded in the hboot. You can change it with a hex editor to whatever you want.

EDIT: Mistake. It is written in the android-info.txt and you can change it with a text editor. However, there are other plain text passages in hboot you can alter with a hex editor.

---------- Post added 20th June 2017 at 00:13 ---------- Previous post was 19th June 2017 at 23:53 ----------

If it is true that [MENTION=8300892]samhhmobil[/MENTION]'s problems have gone after flashing said file, then it is dependant on the HBOOT. To change HBOOT from Sense to GPE or vice versa you need to be S-OFF. That also applies to downgrading HBOOT. If you are S-OFF you can also just flash the full GPE firmware package from Slim Jim Guy.
[One (M7) Original Android Development] FeelThePoveR:
Yep, but firmware and HBOOT are provided within this one file (look around the forum if you don't believe me - every firmware available comes with HBOOT included).
[One (M7) Original Android Development] plazma247:
[MENTION=5078473]FeelThePoveR[/MENTION] got dolby atmos going... but it sound pants lol, gona wipe system and reflash 14.1 but try with Magisk 12 for root and then try sauron again as you said it needs magisk by the looks of it... going back to the tap 2 wake thats awesome thanks for posting that :) although as the kernel version is older now do you think its wise to flash it? I was planning to give it a couple of days, take a nandroid and then take a pop and see if it has any noticeable battery impact... my only concern is i would be using an out of date kernel... due to the lack of hardware button on m7, maybe this is something the dev could build into the 14.1 m7 rom and have an option to enable/disable at some point in the future.
[One (M7) Original Android Development] FeelThePoveR:
It's as stable as the current one it just lacks some of the new CVE patches.
[One (M7) Original Android Development] miki4:
Which file exactly do you mean? And what do you mean when you say firmware?

Usually you are right, when you mean that in a "firmware" package there is radio, touchpad drivers, radio config data, hboot and several others. But in this particular case, the file which samhhmobil flashed, the package

only

contained hboot_signedbyaa.img and android-info.txt.
[One (M7) Original Android Development] plazma247:
Ok flashing again with 13 :) intrestingly even though ive wiped system, when flashing i just noticed it says:

target: htc/m7_google/m7:5.1/LMY470.H18

Ive formatted system between flashes, so maybe the previous GPE did update something else on another partition?
[One (M7) Original Android Development] FeelThePoveR:
It's 45 minutes past midnight where I live and I have an exam tomorrow so...

https://en.m.wikipedia.org/wiki/Firmware

What you keep refering as "full firmware package" is just software+firmware+HBOOT+radio+kernel+recovery so basically full stock GPE factory image.

---------- Post added at 11:55 PM ---------- Previous post was at 11:50 PM ----------

It's normal I'm S-ON on Sense based firmware with only radio updated and that's the same thing that pops up for me.
[One (M7) Original Android Development] miki4:
Hey, then we're in the same time zone. ;)

I know what a firmware is. I asked, what you mean by firmware as it is not well-defined. If you had read my previous messages properly and had taken a look at the firmware packages (or flashable ZIP if you want to call it that) then you would know that I'm not talking about full factory images.
[One (M7) Original Android Development] FeelThePoveR:
I mean technically I'm not wrong either way as bootloader is a part of firmware anyway, what I was saying was that for me it doesn't make sense that only updating HBOOT would fix anything as It's responsible for booting other stuff, so I thought that there had to be something else.

Anyway our device is weird (it supposedly has 4 bootloader partitions i.e.) so what do I know ;)

EDIT: Slim Jim Guy thing is what I reffered to as a full factory image.

EDIT2: Well it looks like I got confused and thought about what n0j0e linked, so yeah my bad.
[One (M7) Original Android Development] Spaeger:
Flashing GPE firmware

Could someone please help me flashing the GPE firmware to my Htc One m7_ul?

I've got LineageOS 14.1 installed, s-on, hboot 1.61, radio 4T.35.3218.16, bootloader unlocked and the phone is encrypted.

My thoughts on this are:

Do I have to remove encryption to do this? (I would do this by flashing the HTC Recovery and doing a factory reset)

First of all I will have to do a sunshine s-off. Since it only works on Sense ROMs, I would start flashing the latest Viper ROM and then going s-off (I bought sunshine over a year ago, I hope it works a second time).

Then I would flash SlimJimGuy's RUU (https://xdaforums.com/showpost.php?p=67457487&postcount=4921). Do I need the stock or pre-rooted version? The flash I would do according to this instruction: (https://hafizimtiaz.wordpress.com/2...-one-to-official-google-play-edition-htc-one/). In this instruction the cid gets changed, is this necessary?

When having flashed the GPE RUU, do I still need to do a OTA or is SlimJimGuy's RUU completely up-to-date?

At the end I should be able to flash the latest LineageOS 14.1 Version and have the GPE firmware installed. :)

Is this the correct way or am I missing something?

Sorry if these are noob questions, but I hope you can help me to turn my m7 into a better phone. ;)

Thanks for maintaining the m7! :)
[One (M7) Original Android Development] plazma247:
[MENTION=8354947]Spaeger[/MENTION] what issue do you have using the 1.61 hboot, ok ive not been using very long, but other than what appears to be a little heavier battery use im yet to see any side effects and im still running s-on and originally had a sense rom, im curious as to what issues you have?
[One (M7) Original Android Development] Spaeger:
I hope to get a better battery life and the gpe firmware is more bugfree.
[One (M7) Original Android Development] camambeou:
Installed target of m7 LOS 14.1 is firmware 5.1.1 so you absolutely get upgraded to that firmware
[One (M7) Original Android Development] crashdjent:
Yep, mobile data dosn't work:crying:
[One (M7) Original Android Development] nsanzumuhire:
Is mobile data not working on international m7 or sprint and verizon
[One (M7) Original Android Development] hfhahn@vodafone.de:
My device is an international m7. With the earlier build mobile data is working perfectly.
[One (M7) Original Android Development] miinos:
I have sent you a message with the mobile data logfile. I hope it is so right
[One (M7) Original Android Development] crashdjent:
M7 int with build 17.01.12
[One (M7) Original Android Development] LXL_FXG:
downloading spr:)
[One (M7) Original Android Development] Flyhalf205:
Can you guys download an app from play store to switch from enforcing to permissive in selinux and reboot and see if mobile data is working then.
[One (M7) Original Android Development] crashdjent:
Dosnt work. With permissive or enforcing
[One (M7) Original Android Development] saturday_night:
Maybe someone could test the kernel from xenonHD with your rom to see if it is kernel or rom related. Mobile Data is working on xenonhd.
[One (M7) Original Android Development] aljo2207:
mobile data not work on m7ul latest lineage

i tried cm14 kernel with wake gestures not work mobile data,gestures work
[One (M7) Original Android Development] mchowdhury:
Confirm it works, running 20170111 on Verizon.

Any update on getting the microphone to work better on handset mode during calls? When you speak right next to the mic it works fine, but when you back away a little bit the sound if extremely muffled. I believe it's a noise cancelling issue, where too much noise is being filtered out. NOTE: this is only in handest mode, on speakerphone the microphones work great!
[One (M7) Original Android Development] LXL_FXG:
new build is work good for me:), thx

from m7spr
[One (M7) Original Android Development] tzadkiel:
Sorry... Really bad day, will try bluetooth tomorrow hopefully...
[One (M7) Original Android Development] nsanzumuhire:
M7 International users?? What about the new build
[One (M7) Original Android Development] crashdjent:
What kind of build, you say?

12.01.2017 mobile data doesn't work. Or you are so lazy to read reviews written above?
[One (M7) Original Android Development] Frodo723:
Awesome ROM, you’re doing it very well mister! Wasn’t expecting such stability from beta.

Tested 01.11 build. The only thing that is seriously messed up for me is calls. Sometimes people can't hear me when they call me. Sometimes my voice is very quiet or during one call they hear me normally and then can't hear me anymore. And occasionally calls won't show up at all when someone is calling me.

Another bug I’ve encountered so far is when you pass lock an app and try to launch it Pixel launcher will crash. I can send you a logcat on that, not sure if bugs related to gapps are of your concern though. Also I had a random reboot over night, while the phone was idle. GPS works. Wi-Fi is fast and fluent. Didn’t test BT.

M7_U, latest firmware, S-ON
[One (M7) Original Android Development] aljo2207:
for me works great,i didnt find any bug,using cm14 kernel with wake gestures

but i love miui 8 and using that rom now,because lineage havent theme engine

htc one m7ul international s-on 1.57 hboot

---------- Post added at 02:06 PM ---------- Previous post was at 01:59 PM ----------

i have one question

why qualcomm porting is not same as mtk

i have ported few mtk roms,but every try to port qualcomm stuck on bootanim

same hardware of base and port device

thank you
[One (M7) Original Android Development] crashdjent:
Doesnt work
[One (M7) Original Android Development] 93zx7:
I'm running 20170112 VZW build. BT seems to be working fine. Wifi is still randomly dropping, but not as often as it was. I dirty flashed over a previous december build and wiped cache/dalvik. Are there any t/sing steps I should perform or are other VZW users experiencing same issue?
[One (M7) Original Android Development] tzadkiel:
Tried bluetooth, with m7spr 1.12 build... Worked fine on my speaker... I did have to reboot first, as the toggle on said it was on in the quick settings, but off in main settings... I did not try microphone... If i have reproducible issues I will catlog...
[One (M7) Original Android Development] plazma247:
[MENTION=8354947]Spaeger[/MENTION] Actually, i had previously flashed the tap2wake kernel last night, however i noticed it had an issue with the screen not responding after some reboots.. anyway flashed lineage 14.1 back over the top (to reset the kernel) and i would say so far the battery life is at least on par with the original 5.1 GPE rom i running before... that i can see so far... Additionally ive had 0 issues with stability, the only issues i had were related to the tap2wake kernel. Im not sure what issues your suppose to get, but so far ive seen none, phone, camera, battery life all seams good for me.
[One (M7) Original Android Development] Spaeger:
And you also got hboot 1.61 installed? I've got some restarts in the last days, but I have an older Version (from March or something) of LOS installed. This could be the problem.

Could someone explain which hboot version is the latest and which the best, especially for LOS 14.1?
[One (M7) Original Android Development] plazma247:
The only reboot ive had was when using the tap2wake kernel and i tried to hard limit the clock speed down to 1500mhz, apart from that its been solid as a rock. (yes im also hboot 1.61 s-on), i did however flash the radio update a few pages back, this came from the last GPE, so i would also do that... If you upgrade to this version i would wipe cache, data, dalvik, system and do a clean install from the latest build (again a few pages back).

Phones had some light to medium use in the last 1 1/2 hours since i took it off charge and im down to 94%... which is about on par with what i would normally expect the battery use to be by now. Its early days so far, but its not been bad so far since switch back to the proper kernel.

Also ive set hotmail to be in exchange mode at the moment... which probably does not help... im going to swap it over to iamp tomorrow and see what impact it makes, but every time ive tried in in the past exchange mode = bad battery life.
[One (M7) Original Android Development] FeelThePoveR:
[MENTION=511296]plazma247[/MENTION]

The issue with screen not responding with DT2W only appears when you set it to start at boot.
[One (M7) Original Android Development] plazma247:
It only happened if the phone forced reboot (crashed after clock max set) and when the phone was connected to charge AC during boot, the rest of the time it worked without issue... However as the kernel is behind there is something in there that was effecting the rate of battery drain not sure if it was something else in the older kernel or the tap2wake, but if you look at the last thread you will see it appears a few people had reported issues with it.. anyway ive set the volume rocker to wake and i can live with this for now.... never did get viperaudio working either with 14.1 so gave up on that, the sounds not awful and i dont use headphones, i only play the music on the speakers occasionally, the rest of the time i stream using bluetooth so i can live with the stock audio manager for now.

Thanks again for your help yesterday.
[One (M7) Original Android Development] FeelThePoveR:
Anytime :)

I had that issue too, but as I said it only appeared when I set DT2W on boot and it could be "bypassed" by unlocking the phone after boot and waiting for a second or two.

Battery drain was probably caused by DT2W as the kernel itself is almost identical to LOS one from a month ago (I know it says it's from march but it was officially dropped then and only recently it's being revived) and it didn't have any particular issues then.

You could also try XenonHD kernel as it also contains DT2W (this kernel was a little bit different than LOS the last time I used it though) or Resurrection Remix one (the latest build is from 08.05).
[One (M7) Original Android Development] samhhmobil:
[MENTION=8354947]Spaeger[/MENTION]

I can tell you *if* your phone is UNLOCKED *and* S-OFF, you can flash the GPE-firmware (without recovery and without boot-img) even on your encrypted phone without danger. I did it (2days ago) on my encrypted phone, and everything was well.

But if you're S-ON, you need to go S-OFF first. Isn't it possible to install sunshine even from LOS? It should... you only need root! But this I don't know, I made that years ago with rooted StockROMs on several devices.

-------------------------------------

But...

If you have no data on the phone that you want keep, the easiest way is flashing the correct HTC-Sense StockROM at first.

Then install TWRP-3.0.2-0 recovery, then root your phone: ATTENTION: the version of SuperSU 2.82 in the playstore (or "downloaded from TWRP") is broken yet and will lead your phone with HTC StockROM into a bootloop. So you need the SuperSU-apk in 2.82 DIRECTLY from Chainfire, or an older release like 2.76 for example.

Then S-OFF your phone with sunshine.

Then you can either install first the hboot-firmware from GPE and after that LOS 14.1, or even first LOS, and after that GPE-hboot-firmware. Both ways are possible.

Good luck!

---------- Post added at 06:41 PM ---------- Previous post was at 06:24 PM ----------

I can confirm now:

On a phone for daily use, LOS 14.1 encrypted running, European HTC-Sense firmware with hboot 1.61 (August 2015), battery handling was totally broken. The phone crashed with approx 60% battery down to zero!

The phone is unlocked and S-OFF.

I installed via fastboot the GPE-firmware (hboot only), after that it is hboot 1.54 (December 2015), and the complete (encrypted) system was untouched and did boot cleanly after flashing.

And now the battery is going down totally stable until 1% without crashing the phone. :laugh::good:

SO IF THERE ARE BATTERY PROBLEMS ON "EUROPEAN" M7's, THIS SMALL FIRMWARE FLASH IS THE SOLUTION!!!
[One (M7) Original Android Development] Spaeger:
[MENTION=8300892]samhhmobil[/MENTION] Thank you. Yes, I've got the european Htc One. So I'll probably have to do this.
[One (M7) Original Android Development] samhhmobil:
[MENTION=8354947]Spaeger[/MENTION]

Just one word more, if the firmware is changed, and LOS 14.1 is installed (and rooted), one should delete the battery calibration file, to get a new fitting calibration by charging to 100% and going down to 1% without charging, and charge again to 100% without interruption, and doing these last two steps three or four times will calibrate a good battery behaviour. I did it (the calibration file deletion) with "Root Essentials" from the PlayStore, and my impression is: it helps! From cycle to cycle the battery lives longer...
[One (M7) Original Android Development] Spaeger:
[MENTION=8300892]samhhmobil[/MENTION] Okay, I've got it. But as usual it was not going as expected. ^^

The full wipe corrupted the encrypted data partition and I had to remove the encryption via stock recovery factory reset.

When new gpe firmware was installed, twrp 3.1 didn't start anymore and twrp 3.0.2 couldn't mount the partitions. I've got twrp version 2.8.7 installed now, with which I eventually was able to flash the LOS ROM.

I am currently charging my phone and will do the battery calibration later.

Thank you for your help! :)
[One (M7) Original Android Development] saturday_night:
Download twrp v3.1 from here, that works with GPE Firmware https://dl.twrp.me/m7univ/
[One (M7) Original Android Development] Spaeger:
[MENTION=7715118]saturday_night[/MENTION] Works! Thanks! :)
[One (M7) Original Android Development] mchowdhury:
I'm committed to keep maintaining LOS for this device but I know very little about firmware. Would [MENTION=5236274]Slim Jim Guy[/MENTION] or anyone else be willing to build a firmware package derived from the GPE firmware that will work on the M7vzw? (remember the M7vzw was never a GPE device)

At the very least, is there any way to isolate certain parts of the GPE firmware that would be safe to flash on the M7vzw?
[One (M7) Original Android Development] plazma247:
[MENTION=8300892]samhhmobil[/MENTION] Actually i have s-on the phone was a European sense based rom original, still on hboot 1.61 and ive had NO battery issues what so ever so far.

The only issue ive ran into (happened today) is i noticed bluetooth would not see my laptop, i tried to turn off and on again and it would not turn back on... After a reboot it turned on fine and could see things correctly, having a quick flick back through the post it appears its a known issue... its something i can live with for now.

Battery life wise, after turning off exchange mode for gmail (hotmail) and swapping to a 30 min imap poll, im losing just over 1 percent per hour of battery life on standby, which is on par with what i had previously on the GPE rom.

Yet to try gps, i did see some people posted potential issues with this on the earlier threads, so i will give this a test.
[One (M7) Original Android Development] Slim Jim Guy:
It can be flashed, because of the same parition layout, but it won't boot because of the CDMA radio.

So nearly nothing is usable from a GSM firmware for a Verizon device, but if you start changing certain parts of the GPE firmware, then in the end, you will end up with a Verizon firmware.
[One (M7) Original Android Development] mchowdhury:
What would happen if you removed all the radio stuff and flashed everything else? Would other things need to be modified still?

Would you be willing to work on a modified GPE firmware for the m7vzw?
[One (M7) Original Android Development] Slim Jim Guy:
It would not work because the GPE firmware is for a GSM device and Verizon is CDMA.

The firmware has other parts on the device which won't work with a GSM bootloader.

You cannot convert a Verizon M7 to any other variant.
[One (M7) Original Android Development] hrockh:
I would like to install this LOS on a device for an inexperienced user.

I am flashing it right now and will try to test it over the next couple of days. How stable is for you guys? I'd rather not go back to stock 5.x
[One (M7) Original Android Development] oznate:
It's pretty good. The known bugs are there (Bluetooth, speaker phone, battery management depending on your firmware) but I haven't found any general stability problems. Much better than version 5 stock in my experience.
[One (M7) Original Android Development] plazma247:
Ok so i would just post by my experience as i bit the bullet and paid the S-OFF tax a few days back (to allow me to supercid and do the full GPE conversion from a phone that was original a sense rom hboot 1.61 and s-on).

Under the sense base i had two forced reboots, strangely they were almost exactly 24 hours apart, battery life was not bad (at least on par with how it was before) and bluetooth when turned off would not turn back on again until i rebooted. Other than that i saw nothing else that was a major issue, or i couldnt work around.

After going s-off and flashing the phone completely to the GPE, the forced reboot issue is gone, bluetooth issue is gone and interestingly the battery life on idle appears to be a little better than previously as well.

I did also experience the volume bug, this was after connecting to bluetooth music and then going back to using the local speaker and the volume was much lower than it should have been, however i flashed sauron and have not had the bug since.

Observations that the dev could probably investigate and maybe fix:

1. Only once the app switcher page (recent apps) only wanted to work in portrait, this is a bit annoying if your holding the phone in landscape, however later on this worked... Maybe this was something to do with the app i switch from, i will keep an eye on this and see if i can reproduce the result.

2. For some reason the spell checker does not work in gmail, how it does work in other apps like signal, i tried it with the gboard keyboard but this didnt help the issue, it does underline the text, but wont allow you to get the corrected word when you click on it. From memory i used the pico gapps from the first thread.

3. The audio fx app says speaker, regardless of playing over bluetooth, speaker or headphone and wont let you adjust bass option for headphones. Im guessing its either not got the profiles for the other outputs or is unable to detect properly to switch between them, i did try previously flashing viper (but this was when i was on the sense base) and couldnt get it to work, but if the issue with the audio profile in audiofx could be fix that would be great.

All in very happy with this rom and a big thank you to Flyhalf205 and everyone involved for your hard work in continuing to move the lineage rom forward for our m7 phones :)

As a side note: for anyone wanting to get desktop mode working with chrome in android N, ive worked out how to make this work here.
[One (M7) Original Android Development] saturday_night:
I think here are most users active so i gone post it here too.

Official Update for TWRP for all m7 devices ver 3.1.1.0 https://dl.twrp.me/m7univ/

Changelog: https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
[One (M7) Original Android Development] oznate:
I have flashed the firmware by [MENTION=5236274]Slim Jim Guy[/MENTION] mentioned earlier in this thread. (Page 96, complete firmware without boot.img and recovery.img).

Battery handling appears to have improved and I used the YouTube app while under 40 percent charge. Previously this caused the phone to reboot.

So far so good. Some of the stability and battery stuff I blamed on LOS was probably the firmware.

Correction: I have not flashed the firmware after all, just thought so. So disregard above. See here.
[One (M7) Original Android Development] devsk:
what steps did you follow to flash this firmware?