Correct. From what it looks like my change should fix it but I'm not sure. You can ask a dev who uses aroma to update it with my commit , though. If they do let me know if it fixes it all
Sent from my 831C using Tapatalk
Will do.
Correct. From what it looks like my change should fix it but I'm not sure. You can ask a dev who uses aroma to update it with my commit , though. If they do let me know if it fixes it all
Sent from my 831C using Tapatalk
Because they dont have the same touch driver we do
https://github.com/amarullz/AROMA-Installer/pull/19 that may work though. I havent tested it at all
@simonsickle I found a possibly major flaw in your recovery, I have the sprint htc one m8 HK edition and at some point it stopped being able to properly flash or restore roms. What happened was any time I'd go to flash a rom it would fail then instantly reboot, and if I tried a full restore of a backup (system, boot and data partitions) it would also fail to restore and instantly reboot. Even if I just wiped system, data, cache and dalvik cache to prepare for flashing a new rom it would complete the wipes but then instantly reboot as well.
I did manage to restore a backup but only by skipping the restore of the data partition, but I still could not install a new rom or wipe without the instant reboots.
I was about to flash a ruu, but then I decided to at least try a different recovery just hoping to not have to start from scratch and viola philz touch recovery worked perfectly.
The issues i had with your twrp leads me to believe that somehow your twrp recovery might not be properly formatting the partitions in some causes causing any modifications to that partition (data partition?) to not execute properly and hence cause a failed flash and reboot.
Hopefully you have some insight into what the cause may be and can get it fixed (I've always been a fan of twrp and hate not being able to use it)
If it will help I can attempt to try your twrp again, maybe wiping and flashing in philz touch somehow fixed things so twrp will work again?
This was never released for HK. Issues probably exist. I have a unified one flash twrp coming eventually. Give me a while for that.
Sent from my 831C using Tapatalk
True, but the hk version supposedly is exactly the same as the regular version for sprint except for some software included in the stock rom, apparently there is some difference somewhere then. Hopefully the new unified version will fix it, if you need any testers later on, I'm certainly up for it
That's good to know, as I now have an HK M8. I'm not exactly looking to flash right away, though. I only want root & S-Off, so I will happily wait for a unified TWRP to be released.Hboot and drivers are actually different too.
Sent from my 831C using Tapatalk
The official build is already unified.Okay guys so I've figured out the unification of recovery. I will have this handled shortly.
I have fixed a few npe in the kernel when using older hboots and it handles zip verification better. Twrp and cannibal open touchThe official build is already unified.
No sense 'figuring out' what's already been figured out. See my github: https://github.com/CaptainThrowback/omni_device_m8_TWRP
That's what the official is based off of now.
P.S. And when I say "unified," I mean it works for all M8 variants, not just both Sprint variants.
Okay. Did you enable support for MTP and UMS as well?I have fixed a few npe in the kernel when using older hboots and it handles zip verification better. Twrp and cannibal open touch
I look forward to seeing your results.I have but I'm also working on a way to mount /system into the computer as well so that people can modify it too
I have but I'm also working on a way to mount /system into the computer as well so that people can modify it too
They're not full reboots (read: not kernel panic) they're ui reboots. I saw this issue with TWRP before on my Jewel when I had pulled in some specific patches on Gerrit (which have since been merged after being updated).
I still believe the issue is there, personally. I will continue investigating, as will @simonsickle I'm sure.
Don't think I can make it through the weekend without rooting, but there are like 3 or 4 different recoveries floating around out here and all of them seem shaky at best. I don't need exFAT support, but I would like one that doesn't have "bad code" and doesn't reboot randomly.
Thanks.