yashsingh1/xdaforums huggingface dataset:
[One (M7) Android Development] winch3rry:
So guys are we gonna see a version of Android Revolution 6.2 with 4.4.3 KitKat??Because right now i have the Sense version and i want to change it..
[One (M7) Android Development] Vel-San:
I'm still waiting too :( i want to change and try the new one !
[One (M7) Android Development] synt3k:
Curious if there has even been any confirmation if mike1986 is even working on new GPE ROM.
[One (M7) Android Development] Nic2112:
It's not like 4.4.3 is very different, other that the dialer, people can't really see a difference between 4.4.2 and 4.4.3.
[One (M7) Android Development] scutworker:
I agree. Better to wait for i/o in two weeks time and see what the new version of Android brings...
[One (M7) Android Development] synt3k:
I feel like 4.4.3 feels more responsive then 4.4.2 in normal everyday usage.. Mind you, I don't have any benchmarks or other performance metrics to back this claim up, just that seat of the pants feeling like it's running a bit smoother..
[One (M7) Android Development] vbauer86:
Dialer is the maybe the one visible change but there are over 7000 small under the hood changes/fixes from 4.4.2 to 4.4.3 what ur talking about...

Gesendet von meinem HTC One mit Tapatalk
[One (M7) Android Development] adambala:
Yup a lot of changes but camera is still crup compare to sense...so for me no chance go flash a gpe rom
[One (M7) Android Development] Mr. Jedge:
its not that hard..
[One (M7) Android Development] commencal661:
Why don't you do it, then?
[One (M7) Android Development] Mr. Jedge:
I meant to say that 'it isn't that bad', with regards to the camera.
[One (M7) Android Development] sl8125:
First of all, been running this rom ever since it came out. Everything running flawless.

Few month ago found out there was a stock option for encrypting the data. After the process everything worked great. However, I decided to try out a different rom and rebooted to the phone into recovery mode. Come to find out it's also locked out by the encryption. First reaction was awesome, android got this on a lock down on all sides. Here comes the bad news. My normal encryption password does not work with the recovery encryption password. It keeps telling me I got the wrong password. It's seems I can't make any changes anymore. I am currently running twrp 2.6.3.3. Can't flash, wipe or change anything else anymore.

Any suggestion will be appreciated. I just don't want to brick the device.
[One (M7) Android Development] scutworker:
The reason for this is that HTC doesn't use the normal Android encryption system but one of their own. Your recovery cannot read HTCs encryption so your password will never work. What this means is you cannot access the data partition when in recovery, only system. Your options are: flash a new ROM from a USB stick you have inserted or flash a RUU to reset the phone to stock. This will erase everything on the phone of course

What you do next depends on what you want to do with your phone: if you just need to flash a new zip or upgrade to a new release of the ROM, then copy it to a USB stick, boot it to recovery, mount it and flash. If you want to try a whole new ROM (and would normally wipe data), then you need to connect your phone to your PC and run a RUU. That will give a stock phone without encryption but will erase everything including your "SD card"

It is a massive pain in the arse that HTC does this. I have encrypted my phone but I don't update the ROM that often, but when I have done so it drives me up the wall having to copy everything off, RUU it, copy it all back then flash the new ROM.

If you need to do a nandroid, your best bet is to use onandroid which can do a live backup when Android is running.

Anyway, good luck with it all. I bet you wish you didn't bother with encryption now!
[One (M7) Android Development] sl8125:
How can I find out the password for the twrp recovery encryption?

In recovery, it won't even detect my SD card. I don't even know if I can use an commands to push a new ROM. I hope this option is possible.

---------- Post added at 02:40 PM ---------- Previous post was at 02:26 PM ----------

Got another idea.

Would flashing new recovery to CWM or update to new TWRP get rid the password requirements. At try find solution from losing all info on my phone.

Sent from my HTC One
[One (M7) Android Development] scutworker:
I don't know what recovery password you mean. If you used the stock encryption in Android then your data partition and your SD card are encrypted and you cannot access it from recovery no matter what. Flashing a new TWRP or CMW will not change this.

You can only access your phone when it is booted into android. From there you can copy everything off and then use a RUU to reset the phone and remove all data to set it up again.

If recovery is asking for a password it means the android boot password, but it doesn't matter if you know it or not because you will not be able to access anything other than the system partition if your phone is encrypted
[One (M7) Android Development] trjlive:
This is some good info. I played around with the HTC encryption a while back, and always thought I had done something wrong when I couldn't mount the data partition in recovery. I eventually just decided that the HTC encryption wasn't worth the trouble for someone who flashes things often for development and testing. Thanks for the explanation! :good:
[One (M7) Android Development] sl8125:
Yeah its android password. Once you enter the correct password I assume sdcard is loaded and able to read and flash ROM and etc. But I can't do nothing. I feel I got jacked by encrypting. Should of left things alone.

Sent from my HTC One
[One (M7) Android Development] scutworker:
Yes, the sdcard is loaded after the correct password is entered IF you are using standard encryption and NOT HTC encryption. With the HTC One, TWRP will still ask for the password, but it will never work. Just press cancel to enter recovery but remember: you will not be able to access the SD card or the data partition.

This is a real pain and I guess that if you frequently flash roms, you are probably best off without encryption as the only way out is to back everything up to your PC, flash a RUU to wipe the phone, copy everything back from the PC, reflash recovery and go from there.
[One (M7) Android Development] Sheetzie03:
Anyone know if there are plans for arhd to go to .4.3.3? Is it just that the op didn't get to it just yet? Thank u
[One (M7) Android Development] Aisfkhan:
Is there anymod available for this rom like we use in ARHD 71.1 sense 6 toolbox???
[One (M7) Android Development] trjlive:
GravityBox is designed for GPE and Nexus devices and includes dozens of available options for tweaking the OS functionality.
[One (M7) Android Development] Aisfkhan:
Thanks man :)

---------- Post added at 12:47 AM ---------- Previous post was at 12:33 AM ----------

Is there anyway to make status bar transparent???
[One (M7) Android Development] trjlive:
I would recommend asking GravityBox-specific questions in the GB thread, you'll get quicker and more knowledgable answers. ;)

But the short answer is that status-bar (and navigation-bar) transparency depend on launcher support. So if your launcher supports transparency, then yes you can enable it. For example, on my Nexus 5, the default launcher is the Google Now Launcher, and it has transparent status and nav bar by default. On my Nexus 7, the default launcher does not support transparency, but I just installed the GNL from the Play Store, and now it also has status and nav bar transparency.

If I remember correctly, the stock GPE launcher for the HTC devices does not support transparency either, but it has been a while since I've used an HTC device. You might try the Google Now Launcher and see if it gives you what you want, or try asking about transparency in the GB thread to see if anyone else has any suggestions. :good:
[One (M7) Android Development] Aisfkhan:
Again thankyou so much :) GNL solved it :)
[One (M7) Android Development] trjlive:
Glad it worked for you!
[One (M7) Android Development] belek1979:
mike, there is 4.4.4! ane chaces? please don't abandon such wonderful rom...
[One (M7) Android Development] Arkanius:
I don't think there is a 4.4.4 version for yet for the Google Play devices.

And the 4.4.3 version had a security flaw, hence why it was pulled.
[One (M7) Android Development] belek1979:
I've already received an OTA official update on Google 4.4.3 GPE HTC One ROM.
[One (M7) Android Development] nerdAFK:
This rom is abandoned?
[One (M7) Android Development] Vel-San:
I dnt think so, maybe mike is waiting for the 4.4.4 update.. So just wait :) subscribe to the thread and you'll be notified
[One (M7) Android Development] Silence66:
i also received the 4.4.3 update notification today. what will happen if install this directly? is this even possible with this rom or do i loose root afterwards?
[One (M7) Android Development] trjlive:
You can't install an OTA over a custom ROM, or for that matter, even a stock ROM if you've made even a single modification to the /system partition (such as root, install Xposed, etc.) The OTA is not a full ROM, it's not even full files. It's only a bit-diff, also called a "delta update", that contains only the code changes (additions/deletions) to apply over the top of the stock ROM. So if even a single file in the system is not stock, then the OTA usually will not even run because it won't know how to deal with the file that's different. Does it add code to it, or does it remove code? It won't know. So even if you download the OTA, it will simply fail if you try to run it.

However, please don't try to run it to see what happens, there have been reports of curious users doing just that, and depending on exactly when HTC does the file verification stage, if the update starts to write some data to the system and then gets halted because of non-stock files, you could end up with a non-booting device. A failed OTA on a stock device isn't that big of a deal, just reboot and start it again. Because any files it did copy are all stock anyway. But if it copies stock files over the custom ROM files, it could cause serious issues. You would probably have to re-flash your entire ROM again and set up from scratch.

So if you really want to get the OTA, you need to return your device to 100% stock, no need to lock the bootloader however. But that means stock ROM, stock recovery, no root or any mods whatsoever. There are several threads in this forum on how to return to stock by using the RUU method. It will completely erase your device and return it to stock "out of the box" condition. Then you can download the OTA, keep in mind the OTA will also update your firmware. This could be an issue if you do not yet have s-off, so you should make sure you s-off before your bootloader gets updated to a version that can't s-off.

Hope that helps! :good:
[One (M7) Android Development] Silence66:
great, thanks for the perfect answer. did think it will replace some files, so it could be possible. didn't know that it's just a delta update. thanks
[One (M7) Android Development] rm83855:
OTA update 4.4.3 fails

I keep getting push notifications for 4.4.3 update however they always fail. The update dowloads and reboots into recovery however the installation always aborts then reboots the phone?
[One (M7) Android Development] BouncingObject:
See the below post. It was right there...
[One (M7) Android Development] xsystem1:
This rom is not dead. Its far from dead. This rom is going to get some serious users with google L version release. I am thinking it is even better than sense.
[One (M7) Android Development] belek1979:
I made an OTA on custom rooted/odexed/busybox Bigxie's and it works:

http://xdaforums.com/showpost.php?p=53705782&postcount=2282

Not possible with ARHD.
[One (M7) Android Development] synt3k:
I wish I could believe this, but unfortunately this ROM has missed both the 4.4.3 & 4.4.4 updates that have been officially released. When I saw ARHD GPE was not getting any updates, I flashed [MENTION=780894]graphix[/MENTION]nyc GPE RUU, then rooted with SuperSU, and installed xposed w/GravityBox so I could tweak everything. Sure, it would be easier to just flash a new version of this ROM, but mike1986 is nowhere to be found here and it appears to be abandoned. Maybe it will come back to life in a few months when 5.0/L is released, but until then.. Every man for himself!
[One (M7) Android Development] BouncingObject:
Mike has 2 other VERY popular ROM's here on XDA that he supports and the guy is only human after all. His philosophy is quality over quantity. If you're looking for someone that releases a new ROM a week after a new version of Android is released then does bug fix releases after bug fix releases, then you'll need to find another GPE ROM. Any long-time GPE ARHD user knows that Mike makes quality ROM's and does his best to get them right the first time. When he feels there's the need to update this version, then he will. Simple as that.
[One (M7) Android Development] synt3k:
While I understand that he has other projects going on, he has been completely silent in this thread since March 18th.. If he chooses to focus on Sense based ROMs, that is fine. Nobody is forcing him to do anything, all I was saying is that this particular ROM seems to be abandoned.
[One (M7) Android Development] Oneiros42:
Has anyone gotten Chromecast screen mirroring to work using this ROM? When I try, it goes "connecting" then immediately "disconnecting". I'm trying to figure out if it's the ROM that's preventing it or something else.
[One (M7) Android Development] stone13:
Yes, Rom-based!
[One (M7) Android Development] Oneiros42:
Which ROMs allow it to work?
[One (M7) Android Development] synt3k:
I imagine that Sense based ROMs that are close to stock should work. The Sense version of ARHD would be my first guess, since the HTC One is advertised as supporting the feature..

Disclaimer: I pulled this all out of my ass.
[One (M7) Android Development] Oneiros42:
HTC One GE is supported as well.
[One (M7) Android Development] srideep:
This is pretty much dead now. It's only normal that he would move on to newer devices. I wouldn't expect anything here anymore.
[One (M7) Android Development] Stephen:
Moderator Information,

I have cleaned a few posts. Can we get back on topic now please.

Many thanks,

Ghost
[One (M7) Android Development] JaRa76:
Mike, please do not let it die, I would like to continue using ARHD with my M7... It has been the only ROM that I have used until recently.
[One (M7) Android Development] blast1987:
Can you post the link where you found the GPE RUU? i'd like to do the same, stock rom rooted and with xposed
[One (M7) Android Development] nisby:
http://xdaforums.com/showthread.php?p=43459658
[One (M7) Android Development] DasDanger:
chromecast

i am also having the same problem. in addition, there is the notification that says "connecting..." that wont go away either. Is there a way to get this to work? thanks!
[One (M7) Android Development] Oneiros42:
I ended up abandoning this ROM and setting the phone to stock Android using the link in the previous post. When it was done updating I tried Chromecast and screen mirroring worked perfectly. Not sure if it was something in the ROM or if mirroring only works properly on 4.4.4, but there you go.
[One (M7) Android Development] crogue5:
I did the full GPe conversion after trying this rom and liking it. So I am on 4.4.4 official GPe and screen mirroring works perfectly.
[One (M7) Android Development] gelo01:
i've noticed only 1 bug (as of now), but it's not totally a bug at all i guess. here it is, something is appearing in my status bar, a small triangle with an exclamation point in the middle, it appears only for a millisecond before i receive a text or after i send a message.. it doesn't happen all the time either.. i can't provide a sample screenshot because the appearance of the said notification icon is really really fast to disappear. the thing is, i don't know if it was really an expected event in sense 6? any replies would be appreciated.. thanks guys. :)
[One (M7) Android Development] Newcron:
This is a GPE ROM thread so there's no Sense 6. Which ROM are you on?
[One (M7) Android Development] gelo01:
oh sorry.. i've posted on the wrong thread. kindly disregard it guys. i'm on ARHD 71.1 though. ;)
[One (M7) Android Development] nirez:
I am experiencing same thing. I think its normal.
[One (M7) Android Development] dy2592:
Trying to do some research for someone about flashing a GE rom on their m7. Does all the gravity box features work on this rom? Also what about the HTC apps, can those be downloaded via the Playstore?
[One (M7) Android Development] BouncingObject:
All the Gravity Box functions work on this ROM, and some HTC apps work. You can go into the Play Store after you flash the ROM and the compatible ones will show up in the Play Store.
[One (M7) Android Development] bambam1978:
So can I flash this with the latest cwm recovery?

Edit- also are you planning an upgrade to 4.4.4.

Sent from my HTC One using Xparent Green Tapatalk 2
[One (M7) Android Development] BouncingObject:
Read the OP.

You must use TWRP 2.6.3.3(recommended) or later

AND

be S-OFF to flash this ROM correctly.

As for 4.4.4, I'm sure this ROM will eventually be updated. There has been no timetable set.
[One (M7) Android Development] msprag13:
Read the OP

You don't have to be s-off
[One (M7) Android Development] BouncingObject:
Yes you do. If not, after you flash the ROM, you'll get to the HTC screen and boot loop.

See below.
[One (M7) Android Development] trjlive:
Yeah you do. It's clearly indicated in bright orange letters next to the download link that

s-off is required

. But who knows, maybe you'll be the first person to make it work with s-on... ;)
[One (M7) Android Development] king_david43:
Some of the other gpe roms have worked for s-on users I think they had to flash the boot.img for it to work
[One (M7) Android Development] Rix70:
the flashable firmware in OP for the ROM where is downlodable?

tnx
[One (M7) Android Development] trjlive:
The firmware link in the OP is correct. On the linked thread, there is a download link, I just verified it works. You need to read the entire linked firmware thread OP, and then if you still have questions, post in that thread.

---
[One (M7) Android Development] Rix70:
sorry, you are right! usually i read everything but... i'm Finally S-OFF since two days and FINALLY i can flash a GE ROM ..in optimal configuration! :D

Hurry for this!!

tnx
[One (M7) Android Development] Lazdaa:
I might be wrong, but reading back a page you guys are saying you need to be s-off.

But the op states:

So supposedly i should be able to flash while still s-on?
[One (M7) Android Development] BouncingObject:
Read the requirements above the download link in the OP. You MUST be S-OFF to flash this ROM or you'll go into a boot loop on the initial boot after flash. It has been well documented on this page, as well as in the thread itself.

It was originally believed that you could flash this ROM S-ON and be okay, but Mike had people test it out early on and S-OFF was the only way to get the ROM to boot correctly.
[One (M7) Android Development] Lazdaa:
Okay Thanks! Guess i'll be going s-off then.

Any cons for being s-off?
[One (M7) Android Development] gelo01:
Imo, the only cons of being s-off is that you are more prone for bricking your device IF and ONLY IF you are a flashaholic and/or you don't fully read or understand what you are going to flash. Anything is about knowledge and presence of mind. But let me tell you, there are countless of pros for being s-off. ;)
[One (M7) Android Development] Lazdaa:
I succesfully s-off'ed my phone and installed the rom so hurray!

Now i just need some time getting used to the stock android :)

Also is there a way to map the vol down button to wake/lock the device?
[One (M7) Android Development] gelo01:
You could try some xposed modules, i can't remember the exact module but there is one that can remap all the buttons including the volume buttons.. on sense 6 based roms, sense 6 toolbox would be enough.. :)
[One (M7) Android Development] CarlHutson:
can anyone tell me what i can do if i already flashed ... but didnt know i have S-ON ...

now im stuck in bootloop, unable to push any new files to my phone?!?! please help

the twrp recovery adb sideload feature doesnt load ....

im a bit ****ed right now :(:(:(
[One (M7) Android Development] BouncingObject:
Can you still boot to recovery?
[One (M7) Android Development] CarlHutson:
yes i can ... but the only rom ive put into the internal sd card is this here... im a bit :silly::silly: right now
[One (M7) Android Development] trjlive:
Boot into recovery, and then use ADB to push another ROM file to the sdcard and then flash it like normal after doing a full wipe of the system and cache volumes.

adb push rom.zip /sdcard
[One (M7) Android Development] BouncingObject:
Do you happen to have a USB OTG cable(micro-USB to full size USB adapter)? Could copy 71.1 to a USB drive then wipe, mount the USB drive in TWRP and flash from that.

Does ADB Sideload error out when you try to activate in TWRP?
[One (M7) Android Development] CarlHutson:
problem with this one is that the ADB wont load within recovery..

it doesnt error out... its stuck @ "starting adb sideload feature ......"

the USB OTG thing sound good to me, i just need to find a shop nearby wich has this adapter ... :-/
[One (M7) Android Development] smgulsby:
On first boot ota for 4.4.3 downloaded but never gave me the option to install. Would like to install, any thoughts?
[One (M7) Android Development] trjlive:
You can't install an OTA update over the top of a custom ROM. If you want to install the 4.4.3 OTA, you must first revert your device to 100% stock. If you want to continue using ARHD GPE ROM, then I recommend you wait until it gets updated with 4.4.3, and then you will be able to flash the update over what you currently have.
[One (M7) Android Development] CarlHutson:
i´ve organised 2 - usb-otg devices . booth wont be recognized in TWRP .. IM A BIT :mad:
[One (M7) Android Development] trjlive:
Are you mounting the OTG device in TWRP? It won't auto-mount, you have to specifically go in and select it, to mount it. I've also sometimes had to select it to mount, but it still wouldn't see it even though it said it was mounted, but then rebooting TWRP got it to see it. But from my experience, the OTG is not really that stable, and I don't like using it.

I'm not understanding why you can't use ADB to push the ROM zip file to your device. You didn't explain what the problem was, just said it didn't work. So what didn't work? Did you get an error message in TWRP, on the ADB command line, during the file push, after the push, does ADB even recognize your device?

Try seeing if Fastboot recognizes your device, because this has nothing to do with recovery. If fastboot lists no devices, then it is either your device is bad, or you don't have the correct drivers installed. If fastboot sees it, then you should be able to go into recovery, and then use adb push to send a file to the sdcard.

It's also possible your installation of TWRP is bad. You could re-download the TWRP file and install it to your device using fastboot, and then do fastboot erase cache, and see if that helps get TWRP working.

So do this, give me your steps that aren't working with ADB and I'll review them to make sure you're not missing anything. Don't skip any or assume I'll know, I'm going to follow exactly what you write to the letter, and nothing else. Tell me what you tap on, what options, etc. That way I can see if there's something you're missing.