yashsingh1/xdaforums huggingface dataset:
[One (M7) Android Development] HolyAngel:
small update being uploaded, just added trickstermod app selection with joey kernel and updated the print during install and in aroma. will take 10min or so to finish uploading so hold off for a min.. Anyone currently running 3.0.5 need not redownload as it's no issue.
[One (M7) Android Development] HolyAngel:
Edit: uploaded and working perfectly :good:
[One (M7) Android Development] middaymoon:
I tried this fix but it didn't fix the issue with the welcome screen bootloop.

Also, Aroma shows a "status 7" error on its last screen (before the phone jumps back to TWRP) is that a separate issue? It happened with both rom zips (with/without a boot.img) I'm m7ul
[One (M7) Android Development] HolyAngel:
Yeah I was hoping with the fix, pulled it from the op as it doesn't work sadly :( have to be S-Off for it to work.

I believe the 'status 7' is an entirely separate issue, any way to save a log from the attempt? There's no issue flashing on philz/cwm, philz at least will allow you to use your twrp backups. If no one has a log I'll work on reflashing twrp myself and seeing if I can find the problem and fix it..
[One (M7) Android Development] HolyAngel:
Hmm.. Well I just flashed twrp 2.6.3.3 and did a full wipe and install and it worked fine.. I fully converted my m7att to Google however when I got it, my device reads m7_ul. I checked my updater script and it doesn't even ask what device you're trying to install it on so its not that either.. Still working on what it could be.

Edit: I will definitely *need* a log from someone that's having this error if I am to fix it as I can't reproduce it myself :/
[One (M7) Android Development] middaymoon:
Just to be absolutely clear, I flash the zip with NO boot.img, then boot to bootloader (from within TWRP) to do the fastboot, right? No rebooting or anything in between? And does the full wipe refer to the option in Aroma or from TWRP? I was doing it in TWRP, I'm about to try Aroma now.
[One (M7) Android Development] HolyAngel:
Leave the boot.IMG in the root of the ROM zip or it will error during install, just copy the boot.img to your PC's adb folder to flash with fastboot. You'll want to boot the phone to bootloader mode(power+vol down) and choose fastboot, connect to PC with USB cable and type the fastboot flash boot boot.img, when it's done type fastboot reboot-bootloader, once your back in bootloader then choose recovery to boot into twrp.

Can full wipe in twrp if you like but you must choose full wipe in aroma. Go through aroma steps and make sure at kernel selection you leave it at stock kernel. That should about do it. :good:

I'm not sure it will work though, I've had a couple people s-on try this and they got as far as the welcome screen before it would reboot by itself :(
[One (M7) Android Development] HolyAngel:
[MENTION=5641133]middaymoon[/MENTION] you could also try flashing the ROM, and then rebooting into bootloader, fastboot, flash the boot.IMG and reboot the phone and see If that works. Dunno if its been tried yet. There's also an option in the kernel I can try changing to see if it will allow booting on s-on but not sure about it.. Won't be able to until tomorrow though
[One (M7) Android Development] middaymoon:
OK I'll try that tonight. flash first, wipe in Aroma, default kernel, keep boot.img. But it's pretty late and I won't have much time this week, so any further testing will have to wait. Assuming it doesn't work tonight, I'd be willing to test your tweak next weekend. Thanks for the help, night.
[One (M7) Android Development] HolyAngel:
Ok, no problem ^^

That'll give me time to make the modification to the kernel to see if that will make a difference at all if it doesn't work tonight. Would love to get it working for s-on.

Thanks for trying :good:
[One (M7) Android Development] Jibreil:
With 3.0.5D, did a Full Wipe flash the ROM with Stock Kernel. Google+ doesn't work, it doesn't crash either just keeps telling us to Re-install. Removed it via Titanium and Installed it via Play Store and its working fine.Should I move it to Systems via Titanium backup or just leave it as it is.?

Flash ElementalX 11.4 with your Battery Saving tips, getting awesome battery, lost 4% battery during 7hrs of Standby.

EDIT

: Update your OP mentioning everyone to keep Beats Audio OFF for true Project ERA v11 sound quality.
[One (M7) Android Development] HolyAngel:
Ah yeah Google plus, I haven't been installing it lately and totally forgot to replace the apk :x will get that fixed!. You can leave it in data/app, won't hurt anything ^^

Great to hear on the battery life!

And I will add that to the OP, thank you!
[One (M7) Android Development] LRNZ09:
Hi, I have "Installation failed" at the end of flashing with Status 7...

But ROM boots normally!

:confused:

Here is the log: https://mega.co.nz/#!hchVmJaD!TD2JEFbpacUnz41oPB4OVBYvkohnvVO0Ubj_eCd816k :good:
[One (M7) Android Development] HolyAngel:
THANK YOU for the log!!

Totally found the problem and will have it fixed soon along with that pesky google+ apk ^^
[One (M7) Android Development] LRNZ09:
Your welcome ;)

Thanks to you for your hard work!
[One (M7) Android Development] HolyAngel:
Ok, Believe I have the status 7 error fixed, Google+ fixed, and updated SuperSU to 1.89, for both roms. Also updated gravitybox on the deodexed rom. Just gotta do some quick testing to make sure everything works and will upload and post 3.0.5.1 :good:

edit: Also changed the aosp keyboard to a different one thats been updated to have a row on top with all the numbers, seems a bit easier to use and quicker.

2nd edit: google+ is defeating me haha, will be a bit longer :P everything else is fixed ^^
[One (M7) Android Development] HolyAngel:
Ok, OP updated with fixed builds, kept the original AOSP keyboard but made sure it was %100 up to date, the new modified one was nice but not fully functional aesthetically. Google plus is %100 working for me now with no error. :good:
[One (M7) Android Development] aussie1234:
Noozxoide EIZO-rewire™ PRO

Hi

I have been using this GPE ROM for almost 2 weeks now and I love it. Thank you to the developer!

I have flashed Elemental Kernel and have enjoyed a ROM that is very snappy.

My favourite audio app is Noozxoide EIZO-rewire™ PRO but I find that it installs ok but does not work.

MusicFX seems to dominate, even when I select EIZO in the Settings --> Sound. I do not flash any other audio enhancement.

Can anyone shed some light on this? Perhaps the app is not compatible with GPE ROMS?

Once again thanks HolyAngel for this ROM.

Cheers

Aussie
[One (M7) Android Development] HolyAngel:
Aw, nice, thank you and you are very welcome ^^

I have used that app/mod on sense but never tried on GPE. I know with Project ERA I had to remove musicfx during install of it in aroma.. I can definitely see what it'll take to run on GPE and post it if no one else does by then. And can also see about baking it into aroma as an installable option if it can be used. Adding elementalx kernel is also a thing on my to-do list ;)

Thanks again for the kind words, glad you enjoy it :good:
[One (M7) Android Development] HolyAngel:
Hmm so far I can't find anything specific but I'm betting on needing to uninstall musicfx with titanium backup or romtoolbox (backup the app before uninstalling in case of problems) after installing eizo to get it to work properly if it doesn't by default. If that fails I'd recommend one of the two sound mods I already have cooked in to aroma. Will keep looking into it ^^
[One (M7) Android Development] daffie:
Hi,

Just saw your post regarding GPE FW 3.62.1700.1. I'm on 3.58 currently but would like to flash newest version. Could you let me know if this version has boot.img? Is it safe to flash...will SD content be deleted (so I need to make backup first)?

Many thanks!
[One (M7) Android Development] HolyAngel:
The 3.62.1700.1 firmware on the OP contains boot.img, rpm.img, and hboot.img. it should not affect SD card content at all and is totally safe to flash. Its pulled directly from the last ota.
[One (M7) Android Development] daffie:
Cheers for that. Just one last question... will it interfere with my current custom recovery or hboot? Thanks again.
[One (M7) Android Development] HolyAngel:
It will overwrite your hboot. Can open the zip and remove it before flashing though so it won't ^¥
[One (M7) Android Development] daffie:
I have just flashed the new firmware according to steps explained here :

http://xdaforums.com/showpost.php?p=46513625&postcount=1

(using GPE FW 3.62.1700.1, with hboot.img removed)

After second time executingstep "fastboot flash zip C:\adb\firmware.zip", I didn't see the info as in screenshot, but again the exact same info/overview as after first time executing the command. Wonder if removing hboot.img is the reason for this? Maybe something went wrong?

Ps Bootloader does indicate the new FW.

But after restarting the phone, I found that some apps were removed and I tried reinstalling them from Google Play store. But it fails each time.

Sd card is intact and can be found. So now I'm copying all content to computer first...just to be safe.

I have reflashed new FW, but now with hboot.img intact.

fastboot getvar all info :

C:\adb>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.54.0000

(bootloader) version-baseband: 4A.21.3263.04

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 3.62.1700.1

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

(bootloader) serialno: SH34GW903307

(bootloader) imei: 354436055227621

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: 11111111

(bootloader) battery-status: good

(bootloader) battery-voltage: 4288mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-0e82187e

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.070s
[One (M7) Android Development] HolyAngel:
Boot image needs reflashed if you're getting the play store 'can't install to usb or storage card' error. It's the stock stock boot image and not rooted or unsecured, custom kernel would be easiest to flash to fix it. And its probably not giving you all the info from that screenshot as the android-info.txt still references the hboot to be installed. not an issue though as the rest flashed. HBoot version is still 1.54. i don't know that they did anything to that as thats the same version number from 3.58.
[One (M7) Android Development] daffie:
Thanks a lot for your help...much appreciated (as I seem to be in a bit of a bind here). I'll reflash custom kernel right now and see if it solves this problem...

EDIT : that did the trick! Immediately after flashing ElementalX kernel and rebooting phone, my MIUI theme for Nova Launcher was activated again (it was missing before, after flashing new FW) and I can again install fine again from Google Play Store.

Many thanks for your help!
[One (M7) Android Development] HolyAngel:
No problem! :good:

happy to help ^^
[One (M7) Android Development] middaymoon:
Something I forgot to mention, earlier when 3.0.5 I could see from the Aroma log that it was trying to install trickster but it failed. I see from the OP that it's only supposed to be for the Joey kernel, I was trying stock and Tbalden. Have you addressed this (Is it even a real issue?)

Does the new update have the fix you wanted me to try, or no?
[One (M7) Android Development] HolyAngel:
Yeah I fixed that in 3.0.5.1 ^^ it didn't affect the phone booting in 3.0.5 just always got the error in install.

New update does not have the kernel fix, lemme see if I can get that to ya here shortly. Been absolutely slammed at work here since yesterday :/
[One (M7) Android Development] aussie1234:
Eizo

Thank you again!

If Eizo does not work then we will just have to use another sound app/mod - thanks for trying. It's a pity as Eizo (in my opinion) is much better than any other sound app I have tried.

No matter what sound mod you use your ROM is still on my phone as it is the snappiest and most reliable I've used out of all the GPE ROMS.

Thank you again for your quick response.

Aussie
[One (M7) Android Development] middaymoon:
No rush.
[One (M7) Android Development] HolyAngel:
Working on more things for the next update whenever that is. Got Elementalx working in aroma so that will be there. Still trying to get info on EIZO..

How is 3.0.5/1 for everyone?

[MENTION=5641133]middaymoon[/MENTION] still working on a way to get this to work for S-On, did not forget about you ;)
[One (M7) Android Development] aussie1234:
3.0.5.1

The latest GPE ROM very snappy. I have removed animations (developer options) and use Nova Launcher (purchased the full version) and also sped up animations within its settings.

Using latest Elemental X GPE Kernel and also flashed the "PurePerformances™X_Stock.1.4.zip" mod.

All features working very well. Use CPU Tweaks App to customise CPU speed and voltages (I've chosen only to 1.89Ghz) and SD card cache to 2048.

ROM is

very

responsive and no FC, however I am not a heavy user of apps. Eizo has been the best sound mod especially for any music and livens up Tune Radio. Another great sound mod is with a dry toothbrush cleaning One's speaker grills :D

I use my phone for work, fun and personal use. Thanks Holy Angel for such a great ROM. Stock is never enough and a fast and stable ROM is very important to me. Keep up the great work!!

Cheers

Aussie
[One (M7) Android Development] starlitjessi:
I'm not the most tech savvy, but I have definitely flashed multiple roms and kernels to multiple devices. I'm no coder by any means, but..

So I went to flash this to my HTC one. I did a full wipe of everything, flashed this ROM, and now...

I get an HTC plain boot screen, then the screen goes black. It then goes to reboot to recovery, Clockwork Mod Touch shows up for a split second, and then it goes to reboot plain. Then it goes to reboot to recovery, Clockwork Mod Touch shows up for a split second... loop. -_-

I'm about to, right now, find a way to somehow get TWRP or some other recovery on here but in the meantime, does anyone have any suggestions to save my phone from potentially becoming a brick?
[One (M7) Android Development] HolyAngel:
Hmm I haven't seen that one before :/ As long as you are s-off it should definitely work.

Also you should be able to just hold power+vol down to force it into bootloader and then either choose fastboot to flash another recovery or try going back into recovery and restoring a backup or trying again or whatever you wanna do. Won't be a brick at all.
[One (M7) Android Development] starlitjessi:
Currently able to get it into bootloader. I can get it to fastboot, but for some reason, it was recognizing USB earlier and it isn't recognizing it now. I guess it's time to try other computers and reboot my current one. *sigh* This is a pain in the butt. Oh ****. I'm S-on. What the hell, when did that happen? I guess it's time to S-off somehow. *sigh* Now it's time for me to figure out how to get it to S-off again. This one is a replacement for my last damaged one. That old one must have been S-off.
[One (M7) Android Development] HolyAngel:
Hmm.. I know in fastboot it won't show a pop up or anything on your computer when connected, just have to open command prompt (or terminal for Linux/Mac) and go to the adb folder with the recovery.img you want to flash in it and just type:

fastboot flash recovery recovery.img

and it should work.

For s-off, if you're on a hboot higher than 1.44 you'll need to look at the rumrunner guide for how to get s-off. Flash one of the 4.3 Roms like arhd or stock Rom and proceed from there.
[One (M7) Android Development] starlitjessi:
Well, in the meantime, I managed to flash TWRP, and it shows me TWRP for a couple of seconds and then dies. So although I successfully got TWRP on there, it's still doing the same loop. -_-

-----

My HBOOT is 1.44.0000

I can get it into Fastboot USB which is how I got TWRP on there. I'm not sure what else I can do from simply the bootloader... -_-

-----

So I am trying to do the steps using Revone to get this thing to go to S-OFF and it keeps saying: "adb server out of date. killing..."

Just giving updates as I'm getting them in hopes that someone has an idea as to what's going on and can perhaps suggest a fix. :(

-----

So... It says my adb server is out of date. I'm trying to figure out how to get it up to date so I can push things to my device. -_- I've got the Android SDK Manager up because the last time I messed with this was June of last year, but I'm pretty sure that's where I got my adb things? I'm not finding where adb is, am I in the entirely wrong place?

----

So I got the most up to date adb and it's still telling me that adb is out of date. I plug the USB and it tells me that I'm in fastboot usb, but any adb commands take a good 20 seconds to process, and then it tells me that the device isn't found, but it still says fastboot usb on the screen. -_- I've tried looking for unbricking processes. I've tried flashing other recoveries (but they only show up for a fraction of a second and reboot the phone). I'm trying to get in through fastboot but even adb is saying it's out of date when I just downloaded the most recent version. I'm running out of ideas. Please does anyone have ANY suggestion that can save my phone? :(

----

So I have been using fastboot to get the most up to date versions of TWRP and clockwork pushed to recovery, but it still reboots almost immediately after showing the splash screen or initial screen for these custom recoveries. Any ideas? Please?

-----

THIS WHOLE THING WAS SOLVED WITH A SIMPLE "fastboot erase cache"
[One (M7) Android Development] jirkab:
I had the same problem. No drivers for Windows do not help - the device can not be connected to a PC. I solved flash fw via an external flash disk using a Y cable. Here is a description of the cable.
[One (M7) Android Development] HolyAngel:
Sorry, I passed out after a long day at work. Glad you were able to get it working. Totally forgot about that command earlier :x

I take it you got adb working? Have to open the sdk manager and update the platform tools in order to make sure you have the latest adb drivers. Should be able to S-OFF from there.
[One (M7) Android Development] Jibreil:
[MENTION=1211160]HolyAngel[/MENTION]

Are you releasing a newer version? As I was about to download 3.0.5.1

Joey Kernel 16 Jan version released.

EDIT: v16 version has battery issues. Stick with 8th Jan version.

Keep up the great work.
[One (M7) Android Development] HolyAngel:
Ah, noted! I had updated the build with the jan16th version but can easily revert it to the 8th, thanks for that :good:

I won't be releasing 3.0.5.2 just yet, thinking this weekend at the earliest as I still have some things to do on it so probably safe to grab 3.0.5.1 for now ^^
[One (M7) Android Development] ShatteredAxe:
Is there any way closing the standard play store when installing the rom? I don't really like the dark version.
[One (M7) Android Development] HolyAngel:
yeah not a problem! can make dark version optional :good:
[One (M7) Android Development] Jibreil:
Heads up

Lux Auto Brightness or Lux Lite with Joey Kernel 8th Jan is a lethal combo. Drains battery every minute at 4% or more. There is some issue between Joey Kernel settings and Lux Auto Brightness which causes this issue.

Resolution

: Upon Uninstalling Lux Auto Brightness, the issue has got solved.
[One (M7) Android Development] HolyAngel:
Yeah lux by itself has been a big battery drainer lately, I actually haven't been running it myself the last couple weeks and have had no issues since then.. you think remove lux from aroma?
[One (M7) Android Development] Jibreil:
It's been working healthy with ElementalX 11.4 kernel. I did a fresh install with 3.0.5.1 with Joey Kernel and started noticing these issues upon installing Lux app. Yeah for the moment I reckon you can keep it off AROMA for sure.
[One (M7) Android Development] HolyAngel:
Cool, thanks for the info! Will make the changes, and hopefully we'll get a new joey kernel by the time I'm ready to release :good:

Also may update the 4.3 build here at some point for the s-on people, think I can definitely improve upon my last 4.3 release ;)
[One (M7) Android Development] genocide_ru:
How long should it take for first boot?

Wiped phone in recovery, installed ROM and it stays on boot animation for about 5 minutes already
[One (M7) Android Development] HolyAngel:
First boot should only be about 2 min or so at most.
[One (M7) Android Development] COCODRILO45:
Hey wandering if WiFi tether works on this awesome Rom I'm on tmobile thanks in advance
[One (M7) Android Development] HolyAngel:
Yep should definitely work! :good:
[One (M7) Android Development] ShatteredAxe:
If you have issues with it enabled but not letting data transfer, check your lte apn settings. I believe under type there should be "dun" added in there somewhere.
[One (M7) Android Development] HolyAngel:
Working on 4.3 again and getting it updated, got aroma ported and most of the apps. Need to revert the kernel to stock and add a few and update the gapps and it should be good to go.

In other news in 4.4.2 land :p looks like the new joey kernel is in the works, got lux removed, and working on a couple other things. Hopefully will get that update out at the same time. Hoping for a Sunday release but we'll see what happens ^^
[One (M7) Android Development] Jibreil:
Update

: Sudden battery drains issues erupted probably along with Greenify. Battery started draining 3-4% after 10-20 seconds after a 100% charge and the battery % jumped alternate numbers.

Also Audio files couldnt be played completely on WhatsApp - probably because of Project ERA + IntenseBlast or Project ERA + Joey Kernel. Not sure what caused what.

I did a FULL Wipe. No Greenify, Using SoundExplosion MOD instead with Joey Kernel 8 Jan and everything is working smoothly. It would be nice if someone with a similar setup as mine, can test out what is clashing with what.
[One (M7) Android Development] HolyAngel:
Ah, things with project era:

A ) I need to move the install of it to after the kernel is installed as it alters kernel files and I didn't realize it until earlier today, will have fixed in next update.

B ) I'm pretty sure you're not supposed to use it with other sound mods.. Same with sound explosion which I personally prefer(and that doesn't alter kernel files)

That could be the issue with the sound..

As for battery drain.. I'm not too sure. I know greenify running will cause a little drain but it should theoretically be nonexistent by greenifying the other apps.. Losing 3-4% off the bat isn't unheard of at all, the kernel default in pretty much every kernel out there(and htc did this) is the phone will report %100 at 96% actual charge, and will report %0 at %4 actual charge left.

More testing is of course needed, I would but I'm working on 3 different Roms at the moment so it'll be a few days for me to get an accurate test :/
[One (M7) Android Development] Jibreil:
BUG Report:

- After a prolonged use the call screen doesn't appear during an incoming call

- Trickster App doesn't get installed when selected in AROMA during ROM installation.
[One (M7) Android Development] HolyAngel:
hmm.. i could swear trickster was working on install.. will double check that for sure, thanks!

As for call screen.. I didn't edit anything that would mess with that, only thing I can think of is xposed..
[One (M7) Android Development] HolyAngel:
Gonna be another day or two for an update at least. Still working on other roms at the moment. But will have latest project era in this one and fixed install for it, latest Joey kernel, elementalx kernel, fixed trickstermod, removed lux, updated apps, and a couple other overall Rom improvements. Oh plus an updated 4.3 Rom with most of the improvements from 4.4.2.

Lots to do!