FORUMS
Remove All Ads from XDA

[DEV][TEMPLATE] AnyKernel3 - Easily Mod ROM Ramdisk + Pack Image.gz [Flashable Zip]

13,800 posts
Thanks Meter: 30,579
 
By osm0sis, Recognized Developer / Recognized Contributor on 5th March 2014, 03:32 AM
Post Reply Email Thread
10th April 2014, 11:51 PM |#21  
Alkemix's Avatar
Senior Member
Flag Italy
Thanks Meter: 228
 
More
Quote:
Originally Posted by osm0sis

It would go against the idea of AnyKernel to include the file like that. Remember, everything automatically comes from the original ramdisk, I just give you the ability to alter those files to add tweaks.



I've applied new anykernel 2.0 ramdisk and It works great also on cyano11. Now I I will carry out some changes ...

Thanks a lot, osm0sis, perfect job!
The Following User Says Thank You to Alkemix For This Useful Post: [ View ] Gift Alkemix Ad-Free
16th May 2014, 01:57 AM |#22  
osm0sis's Avatar
OP Recognized Developer / Recognized Contributor
Flag Halifax
Thanks Meter: 30,579
 
Donate to Me
More
@Alkemix @boype @aosp @bsmitty83

Pushed some updater-script fixes to the example repo for a weird issue that kept AnyKernel2 from unpacking/repacking (at least) on TWRP 2.7:
https://github.com/osm0sis/AnyKernel...d8dc889ba1cd35

The Following 3 Users Say Thank You to osm0sis For This Useful Post: [ View ]
16th May 2014, 02:02 AM |#23  
aosp's Avatar
Inactive Recognized Developer
Thanks Meter: 5,028
 
Donate to Me
More
Quote:
Originally Posted by osm0sis

@Alkemix @boype @aosp @bsmitty83

Pushed some updater-script fixes to the example repo that kept it from unpacking/repacking (at least) on TWRP:
https://github.com/osm0sis/AnyKernel...d8dc889ba1cd35

Boss!

You better be getting ready for some f2fs converting check out those scripts I linked you in DirtyVille 😉
The Following 2 Users Say Thank You to aosp For This Useful Post: [ View ] Gift aosp Ad-Free
20th May 2014, 08:07 AM |#24  
osm0sis's Avatar
OP Recognized Developer / Recognized Contributor
Flag Halifax
Thanks Meter: 30,579
 
Donate to Me
More
Just pushed another commit replacing the binaries with statically linked ones since on some non-AOSP devices (or other unknown circumstances involving TWRP) dynamically linked binaries will seg fault in recovery:
https://github.com/osm0sis/AnyKernel...7612161ae194ef

Thanks @tdhite for asking about the binary linking in my Android Image Kitchen thread, which got me thinking about the execution from /tmp issue and how it could be related to that and the seg fault issues @boype reported. Also thanks @Modding.MyMind for hunting down more info from TWRP which verifies the seg fault issue and solution (below), and for testing to make sure the seg faults were resolved on his device with the new binaries.

Quote:
Originally Posted by Modding.MyMind

Here is a similiar problem that was found with vrthemes a while back that TeamWin posted about. Most likely the same problem with trying to use these current binaries as well. Would seem any binary you try to use must be statically linked or it will cause problems amongst other devices when using them in TWRP.

http://teamw.in/VRThemes

The Following 2 Users Say Thank You to osm0sis For This Useful Post: [ View ]
Modding.MyMind
21st May 2014, 06:50 AM |#25  
Guest
Thanks Meter: 0
 
More
Exclamation
@osm0sis, to add more clarity, the binaries are best to be statically linked when compiled because by doing so you package the needed library(ies) with the binary thus making it very diverse and usable across many different phone platforms because you aren't having to rely on high hopes as to whether or not they may have the needed files for the chosen binary to officially work. Comes down to dynamic versus static lol.
The Following User Says Thank You to For This Useful Post: [ View ] Gift Ad-Free
8th June 2014, 02:12 AM |#26  
osm0sis's Avatar
OP Recognized Developer / Recognized Contributor
Flag Halifax
Thanks Meter: 30,579
 
Donate to Me
More
Pushed a new commit with the latest mkbootimg and unpackbootimg binaries and added board support:
https://github.com/osm0sis/AnyKernel...4340acbb0968b7

Binary patches on my mkbootimg repo:
https://github.com/osm0sis/mkbootimg/commits/master

Should help expand device support some more.
The Following 2 Users Say Thank You to osm0sis For This Useful Post: [ View ]
Modding.MyMind
8th June 2014, 02:17 AM |#27  
Guest
Thanks Meter: 0
 
More
Quote:
Originally Posted by osm0sis

Pushed a new commit with the latest mkbootimg and unpackbootimg binaries and added board support:
https://github.com/osm0sis/AnyKernel...4340acbb0968b7

Binary patches on my mkbootimg repo:
https://github.com/osm0sis/mkbootimg/commits/master

Should help expand device support some more.

Been waiting on this so I could snoop around haha. Thanks man.

Sent from my C525c using Tapatalk
The Following User Says Thank You to For This Useful Post: [ View ] Gift Ad-Free
20th August 2014, 10:02 AM |#28  
Member
Thanks Meter: 4
 
More
Just a quick question. Where would I put the modules I've compiled along with the zImage? in the ramdisk folder?
The Following User Says Thank You to khoanguyen96 For This Useful Post: [ View ] Gift khoanguyen96 Ad-Free
20th August 2014, 10:20 AM |#29  
osm0sis's Avatar
OP Recognized Developer / Recognized Contributor
Flag Halifax
Thanks Meter: 30,579
 
Donate to Me
More
Quote:
Originally Posted by khoanguyen96

Just a quick question. Where would I put the modules I've compiled along with the zImage? in the ramdisk folder?

Good question!

Depends on what your purpose is. I know on a lot of devices' modules are large and should be pushed to /system since you wouldn't want them bloating up your ramdisk, but I also know some devices do include a few in their ramdisks.

Pushing them is easily accomplished with a little bit of shell (busybox mount /system and mv), so I didn't feel the need to build a method for it.

I just noticed today that @ak has started using AK2 () on his OnePlusOne kernel, and it uses modules, so you should be able to use his changes as a guide.

https://github.com/anarkia1976/AK-On...ab69242f1dc3f2

He put the modules in patch but you could just as easily give them their own top level (of the zip) directory and add it to the list near the top in anykernel.sh.
The Following User Says Thank You to osm0sis For This Useful Post: [ View ]
20th August 2014, 03:19 PM |#30  
bigsupersquid's Avatar
Senior Member
Flag BFE, MO
Thanks Meter: 1,674
 
Donate to Me
More
can this handle the dell proprietary header in a streak 7 boot.img? regular mkbootimg fails.
so does abootimg and the old .pl split scripts.
20th August 2014, 03:46 PM |#31  
osm0sis's Avatar
OP Recognized Developer / Recognized Contributor
Flag Halifax
Thanks Meter: 30,579
 
Donate to Me
More
Quote:
Originally Posted by bigsupersquid

can this handle the dell proprietary header in a streak 7 boot.img? regular mkbootimg fails.
so does abootimg and the old .pl split scripts.

Another good one.

Not out of the box. You'd have to compile the tools you need for ARM (instead of unpackbootimg and mkbootimg) and swap them in the script.
Post Reply Subscribe to Thread

Tags
anykernel, flashable zip, kernel, scripting, template

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes