How about adding dtb.img support for arm64 devices as @Tasssadar did it here for arm devices?
Other arm64 have dtb.img and zImage separately. So would be good for those devices![]()
U could always cherry pick it and build yourself
How about adding dtb.img support for arm64 devices as @Tasssadar did it here for arm devices?
Other arm64 have dtb.img and zImage separately. So would be good for those devices![]()
The dtb from the kernel is not used: the hardboot patch exports the dtb used to boot the device, so that's used instead.How about adding dtb.img support for arm64 devices as @Tasssadar did it here for arm devices?
Other arm64 have dtb.img and zImage separately. So would be good for those devices![]()
The dtb from the kernel is not used: the hardboot patch exports the dtb used to boot the device, so that's used instead.
Does anyone want to take over development of this project? I'm not sure if I have the time or the experience needed to keep this project updated (the kernel is still from the January security update) or to fix issues such as the fingerprint sensor and the /vendor partition.
The dtb from the kernel is not used: the hardboot patch exports the dtb used to boot the device, so that's used instead.
Does anyone want to take over development of this project? I'm not sure if I have the time or the experience needed to keep this project updated (the kernel is still from the January security update) or to fix issues such as the fingerprint sensor and the /vendor partition.
Don't pass in a dtb (I never tried this), and you need to pass in the Image.gz not the entire boot.img (use Tassadar's bbootimg to split boot.img into a kernel and ramdisk)Hey did you have to do anything special in kexec-tools arm64 image load elf checks to get kernels to be accepted? I'm having a hard time getting anything I pass as a kernel to load (I'm not using multirom or your sources for kexec tools or kernels, I'm just learning/researching)
I looked over your sources but didn't see anything that would have affected this. I always get elf parsing errors it seems.
Don't pass in a dtb (I never tried this), and you need to pass in the Image.gz not the entire boot.img (use Tassadar's bbootimg to split boot.img into a kernel and ramdisk)
./kexec -l --load-hardboot ./Image.gz --type=gzip-image-arm64 --dtb=./dtb.img --mem-min=4 --reuse-cmdline
Are you building kexec-tools from https://github.com/multirom-nexus6p/kexec-tools on the arm64 branch? That command line looks reasonable.That's the thing though, I am passing Image.gz
This is my command line args
Code:./kexec -l --load-hardboot ./Image.gz --type=gzip-image-arm64 --dtb=./dtb.img --mem-min=4 --reuse-cmdline
Same outcome regardless of whether I pass dtb or not, also it should dynamically add dtb initrd no? From the output of the dtb segments I didn't see anything that jumped out besides the fdt err. I'm guessing it's my kexec-tools source, I thought I'd just ask in case you mightve dealt with the same thing. Thanks
Are you building kexec-tools from https://github.com/multirom-nexus6p/kexec-tools on the arm64 branch? That command line looks reasonable.
First of all, this is a great work, for which I was waiting since I purchased the device 3-4 months back. Using stock MMB29Q with as primary and a non CM custom ROM as secondary. The usage and switching is very smooth. As mentioned in the OP multirom app is not compatible, so never tried it. There are a few problems as well- a) Cannot delete files on both the ROMs b) Some apps unable to write the internal SD on both ROMs c) Nexus imprint not working on secondary ROM.
One question too- How to take backup of individual ROMs or all the ROMs.
First of all, this is a great work, for which I was waiting since I purchased the device 3-4 months back. Using stock MMB29Q with as primary and a non CM custom ROM as secondary. The usage and switching is very smooth. As mentioned in the OP multirom app is not compatible, so never tried it. There are a few problems as well- a) Cannot delete files on both the ROMs b) Some apps unable to write the internal SD on both ROMs c) Nexus imprint not working on secondary ROM.
One question too- How to take backup of individual ROMs or all the ROMs.
yea thats a great way to motivate someone (who's been the only one able to port it over) to keep working on it. tell him everything thats wrong, that'll inspire him
The dtb from the kernel is not used: the hardboot patch exports the dtb used to boot the device, so that's used instead.
Does anyone want to take over development of this project? I'm not sure if I have the time or the experience needed to keep this project updated (the kernel is still from the January security update) or to fix issues such as the fingerprint sensor and the /vendor partition.
yea thats a great way to motivate someone (who's been the only one able to port it over) to keep working on it. tell him everything thats wrong, that'll inspire him
Android development involves users reporting problems for the benefit of all. It's always helpful to the dev if logs are included, but this isn't about someone disparaging the developers work.
I'm in for the latter, and have time to do so. Do you have a hangouts I could talk to you on?
Deleted my post.
I think StarShoot97 is testing the official version of TWRP.
It has recently been released on TWRP's website: https://dl.twrp.me/angler/twrp-3.0.3-0-angler.img.html
As for Multirom, I don't know, but there are some new commits on npjohnson's fork: https://github.com/npjohnson/Team-Win-Recovery-Project