Hi. I'm a 17-year old developer from the Netherlands, who was the first to get Ice Cream Sandwich booting on the HTC Desire. Then I released MIUI, CM7 and AOKP for the HTC Flyer and I was the first with every one of them
I have also been repackaging factory images for Android 4.3 for the Nexus 7 to make flashable ZIPs, and I released a nightly build of OmniROM. In case you're wondering why OmniROM Unofficial Build is not getting an update: I preferred to spend my time to prepare for KitKat.
But now that KitKat is available, I want to work as quick as possible to give you the latest best stuff for our Nexus 7. A custom ROM with features from Android 4.3 custom ROMs is what I strive to. However, I don't have a server or fast machine which is capable of compiling Android in a few hours (my machine with a dual core E2180 takes about 9 hours). This is really counter-productive as I need that box for other purposes as well. So I was wondering if anyone can give me access to a Linux box, with SSH access, and at least about 50GB free space (Ubuntu preferred). That way, I can release updates for unofficial builds of KitKat with new features much quicker.
If you think you have a machine that may be suitable for this, please reply And thanks in advance!
Sorry, I do not own such a machine, but I came here to vouch for this guy.
He was an excellent guy to have around the Flyer forums, and is sure one heck of a developer.
If you do have a box to spare, I would recommend giving it to Chaosz-X
I still use my Nexus 4 happily and recently started modding the kernel a bit.
This led me to the question in the first hand, because it is possible to upgrade minor versions (3.4.0 -> 3.4.105)
The thing is, N4 uses google_msm 3.4 sources
shamu is pretty new, uses google_msm too but 3.10
I've tried by bluntly downloading shamu's kernel source, placing mako_defconfig in arch/arm/configs and updating the defconfig with make menuconfig.
As expected didn't work out, but i'm just a little modder cherry-picking stuff i'd like to have, so in reality i have no clue how to archieve that, or if it is even possible with some modifications.
I've also tried with the standard 3.18 Linux kernel too before, but got the same expected result.
Did someone actually tried this and got a bit further, is this something simply not posiible or too much work to get it going?
I thought I'd post here my (and the people who helped me) progress on porting MultiROM to the HTC Nexus 9.
Contributors (so far, tell me if I miss anyone)
@Bogdacutu for his port of MultiROM on the Shield Tablet (The arm stuff)
@USBhost for testing as well as helping with the patch (patch is still WIP, more on this later)
@Tasssadar for MultiROM all together
@Unjustified Dev for his influence
Progress
Working: Multirom TWRP has been successfully compiled for flounder and has working ADB and MTP.
Partially Working WIP: MultiROM boot selector source has been ported to work with arm64. The multirom boot selector compiles for flounder in zip format and launches at device boot. However, touch does not work and there is no ADB at the moment.
Not Working WIP: The kexec hardboot patch currently does not work so the Nexus 9 is currently unable to boot another ROM other than the primary one.
Source
All sources can be found here (I know some of them may not work and may be a little messy but this is still a work in progress)
Device Tree
Kernel
MultiROM
MultiROM TWRP
Building Notes
I compile this with the CyanogenMod Device Tree. Instructionsfor building multirom can be found on the multirom wiki found here
Note: adbd and kexec-tools need to be replaced with these versions that are arm64 compatible
adbd kexec-tools
If you would like to contact me on hangouts about this, please PM me your Gmail.
Reserved
One more
I might have found a repository that may help us out with the kexec hardboot patch on arm64.
There are many commits here that relate to kexec on arm64
Very glad to hear!! Sooper work :thumbup::thumbup: :beer:
This may also pose useful for the arm64 instructions
...
Looks like kexec-tools may need to have a lot of changes for arm64.
There are the changes made on a more recent version or android tools (not the one for android/multi-rom). I think this commit may be helpful but changes would have to be made.
Re-based many of the repositories on MR64 the other day. Now I need to test....
Also, the kexec tools function for flounder is completely re-written so maybe kexec will work?
I'll have to try to test when I have a lot of free time...
Is this going to work to get Linux kexecboot working? I really would like to have Linux running natively on this tablet....
Any updates on the project?
Any news on this, hoping for developments so that progress can be made for oneplus2 and multirom?
Thanks
Hello, and whether support for Nexus 9?
@Hashbang173
What's the status of this ?
omerjerk said:
@Hashbang173
What's the status of this ?
Click to expand...
Click to collapse
I have tabled development for this until further notice.
Hashbang173 said:
I have tabled development for this until further notice.
Click to expand...
Click to collapse
Is there any deving goin on on this? I think its way too hard. kexec isnt x64 compatible. (The binary itself isnt. How will youll port hardboot ) First we will have to add x64 support to that. I have seen your commits. That isnt x64 supported too.
Please update me on this, im building on op2 if this works. Thanks <3
regalstreak said:
Is there any deving goin on on this? I think its way too hard. kexec isnt x64 compatible. (The binary itself isnt. How will youll port hardboot ) First we will have to add x64 support to that. I have seen your commits. That isnt x64 supported too.
Please update me on this, im building on op2 if this works. Thanks <3
Click to expand...
Click to collapse
I'm no dev but could this be helpful for kex ec on ARM64? https://www.spinics.net/lists/arm-kernel/msg462969.html
Hashbang173 said:
I have tabled development for this until further notice.
Click to expand...
Click to collapse
I know you've put this project on hold for the time being, but I would like to jump in on this dev-tastic venture. I got a Nexus 9 (LTE) for Christmas*, and wanted to let you know that you don't have to bear the burden of building/testing/debugging/etc. all by yourself. I am fairly well versed in the mechanics of MultiROM, and have been (and still am) a user of MR on my Nexus 7 (2013) since v28 . . and honestly, without MR on my Nexus 7, I probably wouldn't have the pen. testing abilities that have enabled me to offer those additional services to my clients (i.e., security consultation, data breach prevention, etc.).
My point is that I owe a lot to Tasssadar and the "MultiROM for Android" concept in general, so I am happy to give back in any way that I can.
The Nexus 9 has been my dream Android device ever since the rumor mill was buzzing with notions of a Nexus tablet with an ARM v8 (ARM64) based Tegra variant!!
Let me know if/when you wanna get this thing off the ground again, and I'll make myself available as much as possible.
FULL DISCLOSURE: Although I am fairly versed regarding MultiROM and it's mechanics (kexec-hardboot, modifications to TWRP, etc.), I don't have much experience when it comes to ARM v8. However, I am pretty fluent regarding desktop x64 programming applications and coding, so it shouldn't be too hard for me to wrap my head around this whole ARM v8, 64-Bit SoC/MoP revolution. If you (or anyone who knows) could fill me in on the challenges we are facing regarding kexec and hardboot in a 64-bit scenario, that'd be swell. In the mean time, I will do my best to get up to speed regarding the repos & commits you have referenced/linked up to this point.
THANK YOU FOR ALL OF YOUR HARD WORK THUS FAR, AND LET'S GET 'ER DONE MY FRIENDS!!
:fingers-crossed:
*BEST . . CHRISTMAS . . PRESENT . . EVER!!!!!!
Thanks Mom!!
They have a Multirom version working for the Nexus 6P which is an arm64 device using the kexec method. Here is the link if it helps you devs.
http://forum.xda-developers.com/nexus-6p/development/mod-multirom-v33-beta-1-t3313291
rifraf1 said:
They have a Multirom version working for the Nexus 6P which is an arm64 device using the kexec method. Here is the link if it helps you devs.
http://forum.xda-developers.com/nexus-6p/development/mod-multirom-v33-beta-1-t3313291
Click to expand...
Click to collapse
yep, I ported it to clark already, maybe I'll try porting it to flounder in the future
Multirom for yureka aka tomato (64bit snapdragon 615) is also coming today with kexec-hardboot patch. Hope other devices also get this fast
Howdy XDAers,
So I'm currently in the process of trying to complete my Kegbot install. I have a Nexus 7 (Grouper) that was upgraded to Lollipop (5.0.2) and was following the instructions as given at <DEFEAT ROBOT>https://forum.kegbot.org/t/howto-root-nexus-7/203/7</DEFEAT ROBOT>. The problem is that post was written for the Kit Kat version of Android. And unfortunately the Kangaroo kernels they have linked to have been replaced by someone trying to install malware on my system (the nerve). So that was a dead end.
Anyway I am looking for a kernel that allows me to use USB OTG and charge my Nexus at the same time while on Lollipop. Does such a kernel exist yet? About 45 minutes of Googling has yielded nothing. If not can someone point me to where I can find a Kit Kat kernel with the aforementioned support and an accompanying ROM to go with it. I can handle the rest from there. Thanks gents (and ladies if any are in here).
[ EDIT ] : Spelling and Grammar.
Hi Stieg.
Did you ever figure this out? i`m in the same situation myself. just started my kegbot build but i am trying to run the server directly from the Tablet.
I need the OTG camera function, but don`t want to to back to stock. Would i have to recompile the kernel to enable it?
I just encountered the same issue while trying out my brand-new USB endoscope camera with a recent version of Lineage OS 14.1. I just wondered if you already tried to build a custom image?
Sharing some useful or not so useful bit of information. It seems that the custom-built kernel from Dorimanx for Android 4.4.2 had at least the driver source in place. *Edit* I'm not allowed to post Links just yet, sry! *Edit*
If nobody else is commenting, I will probably take the time to set up a Build-VM at the weekend and try building my first custom ROM. How hard can it be, right
daFritz84 said:
I just encountered the same issue while trying out my brand-new USB endoscope camera with a recent version of Lineage OS 14.1. I just wondered if you already tried to build a custom image?
Sharing some useful or not so useful bit of information. It seems that the custom-built kernel from Dorimanx for Android 4.4.2 had at least the driver source in place. *Edit* I'm not allowed to post Links just yet, sry! *Edit*
If nobody else is commenting, I will probably take the time to set up a Build-VM at the weekend and try building my first custom ROM. How hard can it be, right
Click to expand...
Click to collapse
Good luck, i went back to stock, really miss the snappiness of los.