yashsingh1/xdaforums huggingface dataset:
[One (M7) Android Development] Larvitarrr:
I just removed the format system line from updater-script. I always format it manually before flashing any ROM, and I don't have to downgrade TWRP.

Edit: It might have been another GPE ROM. I can't remember now, and I didn't fully understand at which point Aroma stops for you. Anyway if I'm wrong just ignore ;).
[One (M7) Android Development] Claydelas:
I am unable to boot the plus version with multirom and I have no idea why... I even left it overnight as opposed to 5-10 minutes but no luck. Any idea what could be wrong ? Using latest recovery from MultiROM.
[One (M7) Android Development] santod040:
I don't use Multi Rom.

That Multi Rom recovery is probably incompatible with the installer script.

Are you s-on? If so, did you fastboot flash the boot.img?
[One (M7) Android Development] Claydelas:
I did flash the whole rom and then flashed the boot.img, and once I tried before hand.. Neither worked so far. How could the installer script have anything to do with the installation ?
[One (M7) Android Development] santod040:
Umm, the installer script is 100% responsible for the installation.

That and the recovery used are your essential variables.

I know the script works, so It's your specific Twrp build that's not working with it.

Try a different version of Twrp or use a different rom, those are your options.
[One (M7) Android Development] pwraggcan:
I have had this issue. Delete the wpa_supplicant.conf file from data/misc/wifi and the dchp folder from data/misc. Reboot and that should fix it although you'll have to enter your wifi passwords again it should then remember them.
[One (M7) Android Development] nkk71:
HTC-ONE-M7_GPE-5.1_LMY47O.H19-stock_062416.zip works just fine in secondary.... always has :)

Works perfectly, nothing incompatible with the installer-script :good:

I don't believe that's necessary (even with s-on) on the M7 or higher.... and this shouldnt be done in MultiROM anyway, as it would overwrite the primary ROM's boot.img
[One (M7) Android Development] santod040:
The Plus Edition uses Aroma.

Aroma tends to be more touchy with different Twrp versions.

I know the latest official Twrp for m7vzw works just fine for the Plus Edition/aroma installer.

But as I said, I don't use Multi Rom anymore, not since my last build/port from over a year ago, so I can't vouch for that.

All I can do, is go by what the above user stated was his result.

As for fastboot flashing a boot.img, sometimes it's needed when overwriting a secure boot with s-on. An insecure boot would be different and fastboot flashing unnecessary. (I'll just agree that we disagree on this)

I appreciate your input, but without an install log or more in depth knowledge of his multi rom setup, I can't be sure what his issue was...
[One (M7) Android Development] nkk71:
sorry for the OT

the Plus Edition works fine too

flashed it twice, once with the normal binaries, once with the updated ones (they show more progress during installation)

MultiROM TWRP is pretty much up to date, the M7 version could use a little nudge for the latest commits, but they havent interfered

boot up took just above 11mins

i selected all defaults, including "random" bootanim... and got the triangle one, on both counts :)

if you need or want any logs, just lemme know

regarding s-on insecure boot, i'm very open to understanding what you meant... i have not encountered it personally, so i cannot say

but very curious to understanding what you meant
[One (M7) Android Development] Mark0322:
Hello,santod040

Does "Disable-Stock-Kernel-WriteProtect_M7_GPE_H18" supports lastest H19 version?

Have a good day:)
[One (M7) Android Development] mitas35:
I use multirom and the plus edition and its working fine without flashing the boot img.
[One (M7) Android Development] mokazas:
How do I get rid of "get now cards"? I don't need it, or any other Google widget at all.. Is it possible to completely remove, or shall I just use other ROM?
[One (M7) Android Development] Wonderman29:
Hello sorry to be a pest but I thought it said the sim card was fixed in this version? Mine still won't work :(
[One (M7) Android Development] santod040:
Disable Google Now, or simply use a different launcher....

Sim card has always worked, there's nothing to be fixed.

You probably need to update your firmware.

Current firmware version?

Which rom?

What carrier?
[One (M7) Android Development] Mark0322:
Hello,santod040

Does your kernel "Disable-Stock-Kernel-WriteProtect_M7_GPE_H18" supports H19 version?
[One (M7) Android Development] Wonderman29:
hey santod its saying my baseband version is unknown?
[One (M7) Android Development] santod040:
Same reply.....

Without knowing your firmware or which rom, I can't help you.

You also need to make sure you're flashing the GSM version of you're device is GSM.

Or flashing the Verizon version, if you're on Verizon.

They are not interchangeable and posted in their respective forums for this reason.

So either supply me with more info, or I won't be able to assist any further.
[One (M7) Android Development] shawek:
This is the thread where i want to say Goodbye to m7.Big thanks to Santod for all his work last few years on m7 phone,hes my favorite rom and tweak developer,always fast and first on cooking and fixing errors, always here to help.I moved to M8 few months ago,but nothing new for me there, boring and unreliable phone.Yesterday i bought LG G4,just to play with something else other than m8(and to test that famose camera),now when I have job and I can afford it(in Cro,decent job is hard to find)..M7 I gived away this morning,it was hard move and i almoust cry ,cuz its still working and looking like "out of the box first day".Ill be checking forum,now and then,cuz it's hard to kick out old habbit that last few years.Thanks for everything m7 forum people,love ya all ;)

Sent from my HTC One M7[5.0.1 Gpe] & One M8 [6.0 Gpe] & Lg G4 [stock]
[One (M7) Android Development] boris1993:
Same issue here. I'm using ADB 1.0.36. When I type "adb devices", it gave me a bunch of same device, and list kept growing, just see the screenshot.

I've tried the SD card fix in post #2, rebooted, but this problem still not solved.
[One (M7) Android Development] santod040:
Using which rom and what kernel?

Adb won't work with an insecure boot.img.

That's likely your issue, but without more info about which rom and what kernel, I can't say for sure.
[One (M7) Android Development] boris1993:
Thank you for the reply.

Rom: Google-Plus-Edition-LP_m7_v4.7_010616

Kernel: 3.4.10-NuK3rn3l-m7-Lollipop_v8.00 santod@DevBoX #1 Sun Jul 5 15:56:57 PDT 2015

By referring the install procedure, I made a full wipe(system, data, dalvik, cache), then flashed the boot.img from /boot in the zip file, then flashed the zip from TWRP.

---------- Post added at 10:56 AM ---------- Previous post was at 10:43 AM ----------

Forgot to mention, my 801e is S-ON

And I solved this by flashing the boot.img from post #4568, after that my kernel changed to 3.4.10-ge0627be android@gpe #1 Tue Aug 25 00:13:26 CST 2015

So maybe I can't use a custom kernel in a S-ON device?

---------- Post added at 11:00 AM ---------- Previous post was at 10:56 AM ----------

Awesome, this solved my problem too!

And I found that this boot.img changes my kernel from 3.4.10-NuK3rn3l-m7-Lollipop_v8.00 santod@DevBoX #1 Sun Jul 5 15:56:57 PDT 2015 to 3.4.10-ge0627be android@gpe #1 Tue Aug 25 00:13:26 CST 2015.

My device is S-ON so maybe I can't use a custom kernel in a S-ON device?
[One (M7) Android Development] AlexLink89:
Hi, I'm on this rom (GPE+) since december and everything is fine except for one thing: sometimes people cannot hear me during calls and I have to restart the phone to solve...Anyone experiencing this problem or it could be hardware related?

Thank you
[One (M7) Android Development] millicent:
I am trying to flash from full 6.04.1700.13 stock firmware (with full wipe), downloaded from first post . The first flash command didn't finish. I interrupted it (CTRL+C) after a while. The download file seems fine, but will download it again.

I am starting from stock sense 5.0.1 s-off, supercid, modelid: PN0712000

What may be the problem?
[One (M7) Android Development] santod040:
What you're doing wrong, is you didn't put it in RUU mode first.

First command needs to put the device into RUU mode.

See my firmware instructions from my m7vzw stock thread, but do not use any files from there, they are for Verizon model only, just use the guide as a reference.

http://xdaforums.com/showthread.php?p=46506621

And FYI, Lollipop Sense firmware is sufficient, no need to flash GPE firmware to run these roms...
[One (M7) Android Development] millicent:
Thanks for your quick reply.

The device seem to be in ruu mode (black background, only htc logo showing).

here is the full cmd line
[One (M7) Android Development] santod040:
Looks correct, so....

Possible issues:

Need to update fastboot/USB drivers (yours are quite old)

Need a different USB cable

Need to try a different USB port

Need to reboot PC or Device or both
[One (M7) Android Development] santod040:
Alright folks,

I've been working on a a Google Plus+ Edition update, on and off for a couple months now.

Much time spent on it and many changes made....

I believe it's about ready for prime-time. (Release within a day or so, maybe less)

Are folks still interested?

Replies aren't really necessary, a simple like on this post is sufficient.

Thanks for the support all this time...
[One (M7) Android Development] kyeljnk:
My life is complete now :good:
[One (M7) Android Development] Neruul:
I get this 'Android L keys update' from January 2016, however, It doesnt install it when i click download and install / reboot. It just reboots in recovery and does nothing. Anyone know how to fix this? I have the GPE plus edition btw.
[One (M7) Android Development] natzy85:
Will Google update M for their Google Edition M7 or only M8?
[One (M7) Android Development] dorsetqpr:
same here.:confused::confused::confused:
[One (M7) Android Development] santod040:
Search the thread for the answer...
[One (M7) Android Development] ptaeck:
Great news santod! Can't wait for the new version!
[One (M7) Android Development] kyeljnk:
Stock GPE is great, cant wait for the new release of GPE+ xD
[One (M7) Android Development] seqas:
Been waiting for and hoped you would make the plus edi. Thanks a lot can't wait to try it out and run it. Thank you pal :)
[One (M7) Android Development] rekull:
Can't wait for the release of GPE+

Thanks for putting the time and effort!
[One (M7) Android Development] Aveiur:
how do i remove the vibration when i press the back/home buttons? on the latest version
[One (M7) Android Development] santod040:
Isn't it still under Sound Settings?

I don't have my m7 on me at the moment....
[One (M7) Android Development] Mikecosta64:
Yeah in the sounds section. There is section named Other sounds. Tap on it and then uncheck the box for Vibrate on touch.
[One (M7) Android Development] OrangeBlack:
Please share the link to the post if you guys find it. I can't remember the exact key number so my search through the thread wasn't fruitful.

Installed GPE+ for the very first time yesterday. Still getting used to not using Sense and loving it! Thanks santod040 :).

If I want to update to the next GPE+ release from you, do I simply flash the new Zip and clear the caches or is there more involved?
[One (M7) Android Development] goofoon:
Never install ota updates

Verstuurd vanaf mijn HTC One met Tapatalk
[One (M7) Android Development] OrangeBlack:
Why is that?
[One (M7) Android Development] goofoon:
Because.. this is a custom rom and the ota is a Google update.

Verstuurd vanaf mijn HTC One met Tapatalk
[One (M7) Android Development] Neruul:
Not neccesarely true.
[One (M7) Android Development] santod040:
Google PLUS+ Edition Updated to v5.0

Google Play PLUS+ Edition

Android 5.1

Lollipop

6.04.1700.19 CL536258

__________________

ChangeLog

v5.0

Updated Base to 6.04.1700.19 CL536258 release-keys

Includes all of the latest *security enhancements and fixes

Updated to latest SuperSu

Updated Busybox

Updated optional Xposed framework to v86

Removed optional Sensify Xposed Module

Added optional *N-ify Xposed Module

Enabled all chosen Xposed modules in aroma on first boot

Updated optional *Dark Themed Gapps

Updated optional *Viper4Android app and drivers to v2.4.0.1

Updated *Viper4Android Dark and Lite Material themes

Enabled Viper4Android driver on first boot if chosen, no reboot needed

Updated optional *Dolby Atmos app and drivers

Updated aroma configs for better Dolby+V4A compatibility

Updated all Market apps to latest versions

Updated *HTC Sense Home option to Sense 8 w/Freestyle Layouts/themes

Enabled HTC 10 Default Wallpaper if HTC Sense chosen in aroma

Added HTC 10 bootanimation to aroma options

Added HTC M8 and *HTC 10 Sense keyboard options to aroma

Updated entire Aroma/installer theme and icons with Dark material design

Added optional Sony Xperia Home Launcher w/themes

Added optional Sony app Play Store compatibility

Added optional Sony Xperia Keyboard

Added optional Asus ZenUI Launcher w/themes

Added optional new* Nexus Android 7.0 Launcher (compatible w/Dark UI)

Much more...

IMPORTANT NOTES:

If you choose the HTC Sense 8 Launcher during install, DO NOT UPDATE it in the Play Store, you WILL break it! (disable auto-updates for it)

If you choose the Dark UI, you will find a themed flashable zip for the latest Google Contacts on your SD card after install (flash ONLY after you have booted the rom at least once)

​
[One (M7) Android Development] mitas35:
Thanks boss you are the best:good:
[One (M7) Android Development] archioptrics:
Installed the latest plus edition was working fine at first but for some unknown reason my phone has stopped connecting to Mobile data WiFi works fine. Edit I found the problem.
[One (M7) Android Development] Mark0322:
Sorry,I have a question.

I found latest plus version has NuK3rn3l_m7_GPE-5.1_v8.0 kernel.

And post#3 kernel is 7.0 version…if it's possible to update it?

If I have offended, I say sorry in advance.
[One (M7) Android Development] OrangeBlack:
Can anyone please tell me if I can simply flash the new Zip on a previous GPE+ version to update or do I need to perform a fresh install? Couldn't find an answer to this in the main post.

EDIT: Found my answer here: http://xdaforums.com/showpost.php?p=67532335&postcount=4961 Trying it out right now.
[One (M7) Android Development] davidcie:
Having the same problem. Windows, adb version 1.0.32, Google-Plus-Edition-LP_m7_v5.0_080916.zip. Changing SELinux mode (using SELinuxModeChanger) to permissive or enforcing (with a reboot after change) does not help; I am never asked to accept my PC fingerprint and device always shows as offline.

Any ideas? Does adb work for anyone running Google Plus Edition?
[One (M7) Android Development] santod040:
Adb requires a Ramdisk edit (set as secure) to be made to the boot.img.

I will post one in a little while, which will allow it to work for you, or anyone else who may need it...
[One (M7) Android Development] davidcie:
Thanks! One more thing — am now on your rooted stock HTC-ONE-M7_GPE-5.1_LMY47O.H19-stock_062416.zip. Was hoping to remove some Google apps that I do not use (like News & Weather, Play Games, and a dozen other). To do this I did what I've always done on rooted ROMs:

adb shell
su
mount -o rw,remount /system
rm -fr /system/app/Hangouts

...but apps keep coming back after a reboot! The su binary also wants to update itself but is unable to. How do I go about modifying the system partition? This is my first GPE ROM so please excuse if it's something simple. Would post in a Q&A thread but didn't see a link to one in the OP.
[One (M7) Android Development] santod040:
That's what the insecure ramdisk edit is for on G Plus.

To allow system changes while booted, but it does break adb.

Stock rom and kernel are secure, so you have adb, but system is write protected.

Wanna remove stuff from stock system? Do it through Twrp file manager or a flashable script.

Sounds like I shouldn't bother posting the other edited file for you now, since you're back on stock...
[One (M7) Android Development] davidcie:
Thanks for the explanation. Please do post the edited file, GPE was meant to be a temporary measure while I wait for it :) One thing is not clear to me thou: how is it that other ROMs allow /system modifications *and* still have a working adb?
[One (M7) Android Development] santod040:
They simply make the ramdisk secure and include a kernel with a system write protection module which was compiled with the kernel.

Mine has that as well, so technically doesn't need to be set as insecure, which is why I offered to post it as such...
[One (M7) Android Development] santod040:
NuK3rn3l v8.0 stand-alone Aroma Installer added to post #3

NuK3rn3l v8.0

For 5.1 S-On and S-Off users

NuK3rn3l_m7-GSM_GPE-5.1_v8.0_081216_AROMA

NuK3rn3l v8.0 from Google Plus+ Edition v5.0, packaged into a stand-alone Aroma Installer for use with GPE based roms only!

Contains all wake features+:

DoubleTap2Wake

Sweep2Sleep

Sweep2Wake

Logo2Wake

Logo2Menu

Fast Charge

OC/UC

UV

Lots of governors

System R/W

SeLinux Permissive (optional)

ADB enabled

and more....

DOWNLOAD v8.0

Added to Post #3 for your convenience.

ENJOY!
[One (M7) Android Development] iVeras:
Hello, i'm having issues with this ROM, wish i could get some help.

Yesterday, i was using my phone while charging and suddenly it rebooted. When it got back on, it started Optimizing apps but after

the process was done, it stood in the boot animation and it has been like that since last night. I already flashed the rom, both dirty and clean but no success on booting. Anything else i might try?

Device is S-OFF and Unlocked Bootloader. T-Mobile M7 with SuperCID.
[One (M7) Android Development] santod040:
S-on?

S-off?

What aroma options did you choose?

Default kernel settings?

Xposed?

Are you sure the kernel is flashing?

Is your firmware updated for Lollipop?

I've had absolutely zero reboots on any of my test revisions for months now.

Need more info at the very least, or an adb log of the crash to even attempt to help.
[One (M7) Android Development] iVeras:
S-OFF, T-Mobile One M7, SuperCID.

I've been using it approximately for a month without any major issues. No Xposed, OC'd CPU to 1.9ghz and GPU to 450mhz.

How do i get a adb log, sorry for my ignorance in first place. Thanks for your fast response, hope this helps a little.
[One (M7) Android Development] santod040:
Your device isn't liking your overcook, sounds like.

Still not sure of your current firmware and Google will show you many ADB guides and apps for grabbing a log.
[One (M7) Android Development] iVeras:
I think that should be a problem. I came from 5.0.2 stock firmware and flashed this rom, is the .zip provided in the first thread flashable through TWRP? I'll be working on how to get a log right now.
[One (M7) Android Development] iVeras:
I got a log from TWRP, does it work for this kind of situation? I tried flashing Firmware>Rom>Kernel but still in the same spot. Just to clarify things, phone goes to Android is Starting screen Optimizing app xx of xxx. When that process finishes, it just goes back to the boot animation and does the same thing again.

The TWRP log is here. http://pastebin.com/t9UDAV6C
[One (M7) Android Development] santod040:
That recovery log doesn't show anything about the insulation.

For that, I would need the aroma log.

Last screen of install when it's all done, there's a 3-dot menu button in the navbar of the installer.

Press that and "save log".

That would show me way more...

Still no idea why you're having an issue.

There's been over 300 downloads of the latest Plus Edition release and nobody else has said anything about not booting.

Please find the current Sense firmware for your T Mobile device.

The firmware files in the OP are for actual GPE devices mainly and unless you've been flashing them incrementally, you're not gonna get a full firmware update from there.

I would also suggest installing the latest official Twrp.
[One (M7) Android Development] iVeras:
Alright, already flashed the TMO FW, updated TWRP to 3.0.2.0. and tried flashing but when i press save log, it doesn't save anything. I don't really understand why this happened because this is the only ROM i've used since i rooted my M7 (not long ago). I appreciate your help anyway, will see what i can do to pull a log.
[One (M7) Android Development] OrangeBlack:
So I performed a dirty flash and everything updated correctly. However, when I try to switch the DPI in System Settings > Personalize > Display, the System Settings window crashes. I have granted the necessary permissions in SuperSU, but still instead of displaying the reboot dialog it just crashes. When I go back in I see the updated DPI value, but the UI does not update after a manual reboot. I even cleared the Dalvik Cache and Cache twice, but no luck. It still crashes. Has anyone else experienced this?
[One (M7) Android Development] Skix122:
Hey, just wanna say that i've been using Google Plus for a while now and this roms is the reason why i don't wanna let go of my m7. I does everything i want it to do. Sure, the system does crash on power savior, but i rarely see it since the battery life is amazing. :good::good:

I sure hope you get Ambient display working right, that would be dope. :p

Keep up the amazing work. Thanks again. :good:

Cheers mate.
[One (M7) Android Development] santod040:
S-on ?
[One (M7) Android Development] OrangeBlack:
Yes.
[One (M7) Android Development] santod040:
That's why then.

S-on prevents the build.prop from changing while booted into the OS.

S-off doesn't have that problem.

My suggestion, edit the build.prop file on a PC to reflect your DPI of choice and put it into a flashable zip to be flashed in recovery mode.

I'm always s-off on my devices, so I don't ever face these limitations.
[One (M7) Android Development] OrangeBlack:
Will try that, thanks! I have tried Sunshine to get S-off before, but it did not succeed on a custom ROM. Looks like I will have to go back to Stock first to achieve S-off and then install GPE+.
[One (M7) Android Development] OrangeBlack:
Unfortunately, that did not work. The DPI in System Settings by default shows as 400 upon Boot, but the UI does not reflect 400. Cleared both the caches as well. Here is what I changed in the final build.prop file:

#
#system props for display
#
debug.sf.hw=1
debug.composition.type=gpu
ro.hwui.renderer.disable_opaque=true
[COLOR="Red"]ro.sf.lcd_density=400[/COLOR]
persist.hwc.mdpcomp.enable=true

Do I need to change anything else?
[One (M7) Android Development] santod040:
That's all you need to change.

Are you sure that you flashed/replaced it properly?

Can you check using a file explorer, to see if the change in build.prop took?

If it did, there's no reason the UI wouldn't recognize the change.

Not all launchers may reflect it, but most all apps and system UI should have.
[One (M7) Android Development] OrangeBlack:
Yes, what I copy-pasted above is directly from the Zip that I flashed. I also made sure I selected 400 in AROMA before installing the ROM. The UI elements look quite bigger than what they are @ 400 on GPE+ v4.7.
[One (M7) Android Development] santod040:
When you say "UI" are you referring to system UI or your home screen launcher or everything?

Attach a screenshot of the main settings screen, without scrolling down at all.

Edit:

I just changed it from default to 400 on both my m7 and my DNA, both running this ROM.

They changed just fine and there is a noticeable difference, as I literally watched the statusbar shrink when the System UI rebooted.

If you're using a Launcher like the new Sense 8 Home that's included, it uses the same size icons and layout, regardless of your DPI.

As I said, not all apps will reflect a difference with a DPI change.

You can go in and set your font size to small, if you wanna shrink most things down a bit more....

But I believe your DPI is changed, you're just using a different/newer launcher probably.