Been using st0kes' thread (http://forum.xda-developers.com/showthread.php?t=709105) and have checked out the AOSP tree, and build a ROM from it that boots on my phone, however....
How do I get the build to stop including things like the recovery image (rather than deleing the folder from the final zip)?
How do I get the build to include additional repo's, such as superuser?
I attempted to follow the guide myself, but when it comes to the command :
source build/envsetup.sh
I just get a "Bash: file not found"
But i don't know anything about the recovery...have you tried the cyanogen wiki?
Josh.
sounds like you're not in the correct folder..
Anyway, in answer to my original question... I found some useful posts on http://howto.ccroms.net/:
http://howto.ccroms.net/android_project/build/mod/recovery
http://howto.ccroms.net/android_project/build/mod/busybox
and
http://howto.ccroms.net/android_project/build/mod/root
I've got Superuser.apk / bash / busybox included, and my compile box is running with the changes from the /recovery howto now (Thank God for 24 core boxes, it compiles a full otapackage in ~10-15 minutes!)
What I have done so far:
1) setup cross compiling
2) downloaded the HTC-provided kernel source
3) wrote my own lkm & Makefile
4) grabbed .config from /proc/config.gz off the phone
The problem though is that the distributed HTC kernel is only the source and it doesn't have the compiled files used in the kernel module building processing. It also doesn't have the autoconf files are shown here in the make error:
" ERROR: Kernel configuration is invalid.
include/linux/autoconf.h or include/config/auto.conf are missing.
Run 'make oldconfig && make prepare' on kernel src to fix it."
So I am wondering, do I have to compile my own kernel in order to be able to compile modules or is there someway to make it work with the stock HTC kernel? Loadable modules are enabled in the stock kernel, but unless I am missing something I don't see how you can actually compile modules for it.
Thanks for any help, and I am very experienced with kernel development (on Intel) so feel free to provide any technical details.
This is Superuser open source app for my roms. It is based on excellent work of Koush and @phhusson who keeps this app active.
SuperSU is a great app, but it is closed source. Without casting any shadow on great developer Chainfire, a proprietary app that manages root and has literally total control over your device is not good security. Period. Well, if you don't believe me, then you should believe Koush:
Why another Superuser?
Superuser should be open source. It's the gateway to root on your device. It must be open for independent security analysis. Obscurity (closed source) is not security.
Superuser should be NDK buildable. No internal Android references.
Superuser should also be AOSP buildable for those that want to embed it in their ROM.
Superuser should also be AOSP embeddable, meaning a ROM can easily embed it into their Settings app.
Maintenance and updates on both the market and source repositories should be timely.
I want to be able to point users of my app to a Superuser solution that I wrote, that I know works, and that I can fix if something is wrong.
Handle multiuser (4.2+) properly
Handle concurrent su requests properly
So, this is a zip for flashing in recovery. It puts:
1. Freshly built Superuser.apk into /system/app; and
2. SU binary into /system/xbin
Nothing else is required. After reboot, you will have a working open source Superuser. If you are on Jaguar with Supersu, just reinstall the latest release (dirty) and flash the attached Superuser_Jan6.zip.
In case you would want to return to Chainfire's SuperSU, you'll just need reflash SuperSU zip.
The app is confirmed to work on Jaguar and my unofficial builds of Tesla-Redux, LiquidSmooth and DirtyUnicorns. It should also work without any problems on other roms including stock, if your Selinux is either disabled or set to permissive.
Source: https://github.com/phhusson/Superuser
Credit: @phhusson
Screenshots
Screenshots added.
optimumpro said:
This is Superuser open source app for my roms. It is based on excellent work of Koush and @phhusson who keeps this app active.
SuperSU is a great app, but it is closed source. Without casting any shadow on great developer Chainfire, a proprietary app that manages root and has literally total control over your device is not good security. Period. Well, if you don't believe me, then you should believe Koush:
Why another Superuser?
Superuser should be open source. It's the gateway to root on your device. It must be open for independent security analysis. Obscurity (closed source) is not security.
Superuser should be NDK buildable. No internal Android references.
Superuser should also be AOSP buildable for those that want to embed it in their ROM.
Superuser should also be AOSP embeddable, meaning a ROM can easily embed it into their Settings app.
Maintenance and updates on both the market and source repositories should be timely.
I want to be able to point users of my app to a Superuser solution that I wrote, that I know works, and that I can fix if something is wrong.
Handle multiuser (4.2+) properly
Handle concurrent su requests properly
So, this is a zip for flashing in recovery. It puts:
1. Freshly built Superuser.apk into /system/priv-app; and
2. SU binary into /system/xbin
Nothing else is required. After reboot, you will have a working open source Superuser. Just delete Chainfire's supersu from /system/
In case you would want to return to Chainfire's SuperSU, you'll just need reflash SuperSU zip.
The app is confirmed to work on Jaguar and my unofficial builds of Tesla-Redux, LiquidSmooth and DirtyUnicorns. It should also work without any problems on other roms including stock, if your Selinux is either disabled or set to permissive.
Source: https://github.com/phhusson/Superuser
Credit: @phhusson
Click to expand...
Click to collapse
Thanks for this. Do you think there should be any problem using this app on touchwiz roms? I'm currently on GN4 with 5.1.1 touchwiz. Thanks.
Kul_dood said:
Thanks for this. Do you think there should be any problem using this app on touchwiz roms? I'm currently on GN4 with 5.1.1 touchwiz. Thanks.
Click to expand...
Click to collapse
I don't see why not. You would need selinux set to permissive...
Superuser updated
New release: this time no problems after install + there is a dark theme included. Flash in recovery. See OP for download.
P.S. If you have installed Supersu, deleting it won't do. You need to reinstall the latest rom and then flash the Superuser_Jan6.zip
Hey guys
Right now I've succesfully built CM13 from sources for the Z00A but I need to change a few things for a project here at work. We need to use ALSA instead of tinyalsa because of some hard-coded things in that mentioned project, that doesn't work with tinyalsa but with ALSA.
Till now I used alsa-lib and alsa-utils from the Marshmallow branch of Android x86 project as external packages. They compiled without any big bug and here comes my problem: All of those little ALSA tools (aplay, amixer, arecord, etc) aren't build through the make-process and won't be integrated into the image as a result. When I compile them separately and copy them into /system/bin with corresponding access rights, they can't be used in the shell. It tell's me they cant be found - even with correctly installed libasound.so.
Any hint or tipp what I'm doing wrong?
Hi,
Amazon release source code as is required by GPL. That is great but to reproduce a binary needs compiler information.
All the stuff I find here on modifying these devices seems to be based on downloading someone else's binaries and hoping they are clean and actually relate to the OS version I have. This info does not always seem to be provided.
If I want to build busybox and su using gcc and copy them across using adb , where can I find the required build info ?
I guess guys here building ROMs must be doing this.
Thanks.