Hello everyone,
First of all I want to thanks community and congratulations for all this great information.
I'm working in my final career project, and I want to present a tool for helping in static and dynamic analysis of APKs ( if somebody want to take a look it is AndroidSwissKnife in github) .
The dynamic analysis I took the code from the project DroidBox (mentioned in my code), I updated it to Python 3 (fixing some problems). But now I have a problem, the system image that comes with DroidBox is an android 4.1.
As part of my project I want to update my tool to support Android 5.1, or even Android 6 and I need to modificate in any way the android image to hook some method calls, and I thought in Xposed framework.
I would like if anyone can give me information to start learning in the android's security world, custom ROMs and Xposed framework.
Thanks to every one. Kind regards.
Related
Hello all,
Is there a way to port Snort to Android OS? I have already ported
libpcap to Android and I have made some simple native sniffers which worked
perfectly.To do this, I used the NDK development kit that offers you some
tools for cross compiling C programs to ARM architecture.
Is this possible to do it for Snort. I know that Snort is a big project that
contains many source files and uses many modules such as Libpcap, PCRE,
Libdnet, Barnyard2, DAQ. I am wondering if is there a way to build
this code for Android.. E.g. by statically link all this modules.. Moreover an
other potential problem may be the fact that Android uses a subset of libc
(bionic), so maybe some basic functions are not available..
Have anyone done it before? Or, can some one give me some help on how
to start?
Thank you in advance,
Thanasis
I have successfully built a AOSP ROM I think.
I now have recovery.img, boot.img, userdata.img, system.img
Is there a way of making a n update.zip with these?
This should be moved to Q & A.
Yes, it's about development BUT, it's a question about development and therefore does not belong here.
Pipsqueak approved this message
Come on man do a Google search. There is information for making AOSP ROMs all over the place.
With that said, I strongly recommend heeding this advice:
cyanogen said:
Here's my advice for those looking to make their own Android ROMs.. Stop. Write an app or two first, learn how the system works from a developer standpoint. Learn some Java. Read the developer documentation. Learn how to use Git. Then learn how to build AOSP from source. Read the porting guides, and learn how the build system works (the links below have almost everything you could possibly want to know). Now try to put your new found skills to work on enhancing the platform by writing code or making theme overlays. And share! And put that **** on your resume. There is a *ton* of information out there but any kind of "step-by-step rom cooking guide" is going to be a complete fail- it's too broad of a subject.
Android Developer Guides: http://d.android.com
Working with AOSP source: http://source.android.com
Platform Developer Guide: http://pdk.android.com
Android Gitweb: http://android.git.kernel.org
Git Ready (Git tips and tricks): http://www.gitready.com/
Building CyanogenMod: http://wiki.cyanogenmod.com/index.php/Building_from_source
How Dexopt works and what are those odex files: http://android.git.kernel.org/?p=pl...bcd225e47b2cc7abb2a366112d3aeb45936;hb=master
The PDK site is absolutely vital if you are going to work on custom ROMs. Read every single page. Twice. Some of the info isn't up to date, but you'll get a really good idea about what goes into actually configuring Android to work on a real device.
Click to expand...
Click to collapse
Hi,
I'm an advanced Android developer but now I was required to create a custom Android Build for a client, but I have no experience with this.
Does anyone know any training or any hacker that could give me a training on this? Basically, it would be like using the busybox tools, download and build custom Android images, install images on the device and everything related.
I'm from Brazil but I can travel to US if necessary.
Thanks for any help with this.
Marcio Alexandroni.
I'm a kind of lazy man and not good in English. Building a whole rom from source code can be a hard work for me since I have no experience about dealing with any programming except porting rom for a device. I haven't done this for a long time since 4 years ago. But Google's project treble was an brilliant news for me.
I want to try for a Chinese rom called Smartisan OS, and also noticed that Pixel/XL has so less developer, unlike Nexus5, which has so many custom roms for flashing.
But I don't understand project treble completely, only heard the news. Is there any official or unofficial documents teaching us to use this function for developing custom-made roms?
Will it be necessary to build a rom from source code from project treble, or just simply doing some copy and paste (kind of like the roms I've made for a Chinese tablet. I was only unpack the kernel as well as rom zips and paste some stuff then repack them, it did worked)?
BTW, Smartisan OS seems to be based on Android 7.x and no official news about supporting project treble, I don't know can it be done if the target rom don't support project treble at all.
Forgive me if I'm too nasty, just curious.
Hi,
I‘m looking for a tablet as a development platform for gettting into custom android firmware development. What device (current or discontinued) is the most painless to compile a custom rom for with a current android regarding unlocking and driver support in 2021?
I‘m an electronics engineer and have worked on firmware for arm microcontrollers and did some kernel development for embedded linux (yocto) before.
I have the idea of creating an open source custom android for elderly people and small children that is pretty much locked down and has a simplified interface without cryptic messages. All settings, app installation and user support should be done from an app on another device. I think all the building blocks for this exists, I just want to put them together in one package. If you have suggestions for an existing base rom to build this on I‘d be happy to hear about it.
Cheers,
Rick