I am not sure about developement goals,

As well as I have question to One Android developers and need some kind of support:

minimize ability to brick device.

Hello, hihihiI am, member of, probably some of you already know me by older projects related with famous(Leo).Nowdays HTC Leo become too old, while hardware abilties are growing very fast nowdays(huh, already phones with 64 bit CPUs and 4 Gb RAM? Wtf my old PC from 2008 has 4 Gb ram too)So I decided to switch hobby phone, finally I got(thank all contributors),so I am with you nowI am doing it for fun, but probably it will be something like:1)Oldschool WM61/65 port2)Windows RT and/or Windows Phone 83)Own bootloaderOfcourse I no idea about port quality - things like ultrapixel camera can be impossible to bring up.But it's hobby, not attempt to do a work instead of a big company.I am already started to work onfor HTC One.Then I am planning to bring UEFI up.Will keep community in sync about development status.Releases are going to be more often.About different models support: there are many different HTC One revisions around, I will try to support as much as possible of them.It seems S-OFF is mandatory requirement.I am going to divide the biggest "userdata" partition to grab a space for another OS.userdata it seems is EXT4 formatted.I don't want to modify primary GPT (at eMMC sector 0) toMy current idea is a hack inside Linux GPT parser to replace userdata partition bounds.In such scheme Linux kernel must be modifed to use/ another OS.But I don't know how Android will like unformatted userdata partition. Anyone knows?Or maybe someone can suggest better scheme?