Database Users

Flash Stock Android Kernel (or Emulator ROM)

Hey,
I've just recently started Android development and I'm keen to learn as much as I can about the whole system, not just about SDK app development. As such I'm interested in attempting to build my own ROM completely from scratch. I've downloaded the Android Source (and Galaxy S source) and would like to try my luck.
First I've been mucking around creating custom ROMs with the emulator, moving apps from the Galaxy S ROM I dumped from my device onto the stock emulator ROM and testing things out.
Anyway I'm at the point where I'm wondering if it's possible to flash the stock emulator ROM onto a Galaxy S phone? I know the Galaxy S source includes a lot of device specific stuff however I'm not interested in getting the camera, bluetooth or anything hardware specific working just yet.
If I flash a ROM with a stock kernel, drivers etc. onto my phone will it work? Has anyone done this? Will it just brick my phone?
Any help would be appreciated.
Cheers,
Ben

Anyone?
Also, I know people have flashed AOSP ROMs on other phones, does anyone know if they required modifications or whether they are in fact stock ROMs?

nje, can't work. why?
1) different bootloaders
2) different partition layout
3) different (kernel)drivers
4) different vendor setup
etc.
it is possible to flash the emulator image onto a dev device (dream/sapphire) but even then a lot will not work properly!
if you want to learn about the android architecture you should start with building a kernel (there is already a thread about that here) and playing around with stuff like the (file)system and utilities...

Thanks jodue.
Yeah my long term intentions were definitely to build the Galaxy S kernel and any necessary libraries and drivers specifically necessary for the apps I decide to include in a custom ROM.
I was hoping that I'd be able to start out by tweaking a minimalistic/generic ROM (the AOSP default ROM) on my Galaxy S. However, as you've pointed out I'll have to start out with the kernel and all the device specific stuff first.
I've got quite a bit of information on building an Android/linux kernel both from the thread you mentioned and also the official AOSP page. However information on putting together a complete working ROM seems a bit sparse. Does anyone know where I can find some information on the topic?
I'm also curious to learn about the list of things jodue mentioned i.e. Android bootloaders, partition layouts and drivers (generic and Galaxy S specific). I assume detailed information about particular devices and drivers probably isn't available but if anyone even knows where I can learn detailed information about default AOSP ROMs I'd be extremely interested know.

[Q] What does it take to build AOSP 4.x for the A7+?

I would really like to get the OS updated on this device, I'm sure I'm not alone.
I've been following many of the guides on this forum, or youtube videos, but with no luck.
Is there anyone who can help me to figure this out better?
Building AOSP or Porting Cyanogen mod would be ideal, is this possible?

I have had the original a7 since it was released and the major hangup has always been, the kernel. The kernel source for 2.2 froyo has been released, but, no one has made or ported a kernel past that. Dexter the great did a lot with only that kernel, CM7 and Honeycomb, but limited because the old kernel. We need a 3.0 kernel for CM9/10 to really move. There are similar tegra devices that have Honeycomb and beyond, but swapping kernels has been reported to only partially work. I hope that it will happen one day, this baby is powerful.
So beyond my ranting we need, device tree, drivers, and a kernel.

I have been trying myself to push all sorts of Linux for Tegra (ubuntu, gentoo, and geexbox) as well as trying to figure out how dexter had started running ICS on his before he dropped the project.
What is known: this is an abnormal Harmony tegra 2.
What you need to know for APX: A7+ uses hsmmc interface, so all nvflash designed for nand or emmc will inherently fail (or at least has been the case thus far)
I dont know how exactly this is, but due to its odd nature most prepackaged or script made bootloaders will fail. I'd love to see ICS or JB on this device for sure, but making an APX backup would need a new bootloader, or at least a new boot.img for sure.
I'm a tinkerer, with very little programming skill. I can google as good as anybody though lol.
Somebody needs to design an uber cross-compiler that can just transform the kernel to 3+ so we can stop wishing for new firmware and just have it lol

[Q] Galaxy s4 I9505 with Google edition andriod

Hello guys, i just have a (few) question(s)
So, last week i installed Google Edition Andriod Kitkat 4.4.4 on my galaxy S4 I9505.
This rom is till now, still amazing, fast and better than touchwiz in any way. But i can't seem to find on the internet how and which version of xposed framework i need to install, since it is per model (i think?) which model do i choose?
since i have a Galay S4 but my rom is not from a galaxy S4, i get confused which one i have to install.
Some links to downloads would be great!
Thanks in advance
Dylan

dylanbos1996 said:
Hello guys, i just have a (few) question(s)
So, last week i installed Google Edition Andriod Kitkat 4.4.4 on my galaxy S4 I9505.
This rom is till now, still amazing, fast and better than touchwiz in any way. But i can't seem to find on the internet how and which version of xposed framework i need to install, since it is per model (i think?) which model do i choose?
since i have a Galay S4 but my rom is not from a galaxy S4, i get confused which one i have to install.
Some links to downloads would be great!
Thanks in advance
Dylan
Click to expand...
Click to collapse
Hi mate
Basically it works in any android 4.0 + base rom device see from one of his threads
For which devices/ROMs does it work?
I develop the Xposed framework based on the AOSP sources. I'm personally using CM10.2 on an I9100 (Samsung Galaxy S2, bought in Germany). Basically, it should work on any phone which with a ROM based on Android 4.0 or later and an ARM or x86 processor (this is the processor architecture, almost all smart phones and tablets have either of those). Exceptions might be ROMs which are different from the original Android code in some very internal, central code parts (which don't need to be touched for most theming and enhancement modifications). But this is related to the ROM, not the phone itself.
The modules target higher-level code, so they are more likely to be incompatible with your ROM. Basically, the question is whether the methods and resources which the module modifies are similar on your ROM and on the developer's ROM. Let's say a module needs to modify the result of a certain method call. For this, it needs to specify the exact name and parameters that identify that method. If the in your ROM, an additional parameter has been added, the module can't find the method anymore and won't work. If the method can still be found, it will probably work (unless the rest of the app/ROM has changed too much).
There is not definite answer whether it will work. Just try it (of course, making a nandroid backup before is never a bad idea). If it doesn't work, just disable the module. You might want to inform the module developer (not me!) about this fact and provide details (e.g. a logcat and/or the content of /data/data/de.robv.android.xposed.installer/log/debug.log).
Try with latest 2.6.1
http://forum.xda-developers.com/xposed/xposed-faq-issues-t2735540
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053

Thank You!
MAX 404 said:
Hi mate
Basically it works in any android 4.0 + base rom device see from one of his threads
For which devices/ROMs does it work?
I develop the Xposed framework based on the AOSP sources. I'm personally using CM10.2 on an I9100 (Samsung Galaxy S2, bought in Germany). Basically, it should work on any phone which with a ROM based on Android 4.0 or later and an ARM or x86 processor (this is the processor architecture, almost all smart phones and tablets have either of those). Exceptions might be ROMs which are different from the original Android code in some very internal, central code parts (which don't need to be touched for most theming and enhancement modifications). But this is related to the ROM, not the phone itself.
The modules target higher-level code, so they are more likely to be incompatible with your ROM. Basically, the question is whether the methods and resources which the module modifies are similar on your ROM and on the developer's ROM. Let's say a module needs to modify the result of a certain method call. For this, it needs to specify the exact name and parameters that identify that method. If the in your ROM, an additional parameter has been added, the module can't find the method anymore and won't work. If the method can still be found, it will probably work (unless the rest of the app/ROM has changed too much).
There is not definite answer whether it will work. Just try it (of course, making a nandroid backup before is never a bad idea). If it doesn't work, just disable the module. You might want to inform the module developer (not me!) about this fact and provide details (e.g. a logcat and/or the content of /data/data/de.robv.android.xposed.installer/log/debug.log).
Try with latest 2.6.1
http://forum.xda-developers.com/xposed/xposed-faq-issues-t2735540
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Click to expand...
Click to collapse
Thank you so much for your help. I think it is pretty clear for me now.
Dylan

dylanbos1996 said:
Thank you so much for your help. I think it is pretty clear for me now.
Dylan
Click to expand...
Click to collapse
Any time mate.

Asus ZenPad 8.0 (Z380M/P00A ver) Firmware Hacking

(Since I'm a newbie, I can't post in development forums, so I guess this goes here for now. If this is the wrong place, I apologise.)
I have an Asus Zenpad 8.0 (Z380M/P00A), which doesn't seem to have any support from the custom rom community. This is not surprising as it's a fairly uncommon device, and until recently, Asus has been less than helpful. However, the latest firmware update (supposedly; I haven't pulled the trigger yet) allows the Asus bootloader unlock utility to work on this tablet.
I've wanted to replace Asus's firmware since I bought the thing. I know that it's an uncommon device, so I'll have to do all the work myself. I'm an experienced Linux hacker, so I know how to configure and build kernels, how Linux OS images are constructed, how to read/write C, etc. However, I'm a bit of an Android newbie.
I figured the first step would be to port TeamWin recovery, so I'd have a way out if I brick the thing. But (from what I've been able to find) porting TeamWin requires a working CM or (preferably) Omni port. So it's kinda a chicken and egg problem. Do people just port roms using stock recovery and hope for the best? Or is there a (more involved, I'm sure) way of porting TeamWin that doesn't require an existing port? Or is there some other recovery (I don't know about) that's more standalone?
And then there's the issue of porting the OS itself. For thier part, Asus provides kernel souces, firmware images, and the aforementioned boot loader unlock utility. I imagine to get started, one has to compile a kernel and combine it with binary blobs extracted from the firmware image, but I'm not entirely sure.
I've looked around for porting information, but the guides I found all seem to assume you've got a working device tree from one mod that you want to graft onto another. I couldn't find much about really starting from (nearly) nothing. I'd like to say I'm surprised Google doesn't have something written up, but given how unhelpful I've found a lot of thier Android docs in the past, I'm not.
I'm mostly interested in porting AOSP to start, but I'd be willing to start somewhere else if some other ROM is easier to work with. Anyway, thanks in advance for any suggestions or advice you might have to offer.

Any progress on this? I was able to flash twrp and root my Asus Zenpad 8.0 (Z380M/P00A), but had no luck finding a compatible rom. Did you get to compile one? Thanks!

How would you unlock the bootloader for this device?

Will we get an unofficial LineageOS for Lenovo TAB M10?

Lenovo TAB M10 is a cheap 10" tablet. It seems that currently there are no custom ROMs for it. Given the fact that Lenovo will probably never provide software update for it, without custom ROM, it will become a paperweight fast.
So, I wonder how likely if someone creates an unofficial LineageOS build for it in about a year or so. Are Lenovo's tablets generally hard to create a custom ROM for?

Let's say that it would be nice to have a custom rom, but first a recovery would help.
I am trying to develop something, but unfortunately I have no experience building the vendor/device folders required, fundamental to perform this activity.
Moreover, considering that the device is still pretty new, I don't know.
Tbh, I was thinking about installing debian or archlinux on it: mine has no 3g, and a pure Linux would likely extend the device supported

Any updates to M10 custom ROMs...?

The partial good news is that Lenovo has actually provided an Android 10 update, and TWRP is available for the M10. As far as I can tell there are still no custom roms though; I'd love to put LineageOS on it.

M10 FHD Plus user here... I've unlocked the bootloader, installed twrp and magisk, but where can I find custom roms?

I flashed Ubuntu Touch on my M10 FHD Plus a few days ago. The process was alright, though I had some trouble using SP flash utility. Didn't need to use TWRP. Charging is abysmally slow, so there's definitely room for improvement of the ROM's compatibility with the device.
Here are the resources I used:
https://gitlab.com/ubports/communit...vo-tab-m10-fhd-plus/lenovo-x606/-/tree/master
https://forum.xda-developers.com/t/...sp_flash_tool_linux-mtk-mediatek-soc.3160802/
https://forum.xda-developers.com/t/root-guide-lenovo-tab-m10-fhd-plus-tb-x606x.4328859/
https://appuals.com/how-to-install-sp-flash-tool-on-ubuntu-for-mediatek-android-flashing/
https://spflashtools.com/linux/sp-flash-tool-v5-2136-for-linux
http://www.lieberbiber.de/2015/07/04/mediatek-details-partitions-and-preloader/
SP flash V5 works better than v6, at least on my linux machine.
https://www.one-tab.com/page/0asPOcZpQV-NdWx37c_e1g

Any news to this so far? I found a guide on tweakdroid but to me that looks like it's autogenerated nonsense. I would try it though, if nothing comes up anywhere else

I would like to buy it... Is it dead in modding?