Asus ZenPad 8.0 (Z380M/P00A ver) Firmware Hacking - Asus Zenpad 8.0 Questions & Answers

(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?

Related

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.

Building from Cyanogem source and flash to atrix

Hello everybody,
I'm an Android app developer for some time, but from some time ago until now I have been tweaking the framework, trying to enhance, customize and maybe correcting bugs, so I'm working on the emulator, but I would like to test it on my device (Atrix).
Since I'm a newbie on this matters and I found plenty of threads and sites/blogs, I got a little confused on what are the steps to be made, specially because I would like to build from source as to have my modifications flashed. I'm aware of the hardware implications for my specific device, so I decided to use a reported working rom source code for my device, but i'm a little lost. I thoutgh to be using Cyanogem but I don't know the specifics.
Since I already have the source code AOSP, I think It would be painful to make it work on my device (drivers, kernel, so on...).
I just want (for now) see my framework modifications on device. Anyone could point me to the right direction?
I thought of using this firmware here.
Thank you all.

[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

Port of lineageOS

Hello Guys,
Today I woke up with a new idea; I want to port LineageOS to the LG V20 version H990DS. I was tinkering with this idea for about one year, but never actually wanted to make the step. Until today. I used LineageOS and CyanogenMod since 2012.
The reason why I want to create the first port is because I have the time at the moment, so why not help the community? I do have four years of programming skills C/C++. Run Linux as daily driver etc... Do know how to use git, linux, autotools etc... The tricky part however is: I never compiled a Lineage OS rom from source and I don't think the compiling would be a problem, but the LG V20 H990DS isn't officially supported. My question is: Where do I start to program? How can I compile and build a working Lineage OS for the LG H990DS. Are there any good website I can read from?
I saw this:
https://www.youtube.com/watch?v=MGI3NSJFtKA&feature=youtu.be
https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484
http://www.lineageosrom.com/2017/01/how-to-build-lineageos-rom-for-any.html
https://www.reddit.com/r/LineageOS/comments/6iie9l/how_to_compile_lineage_os_141_for_unsupported/
https://www.reddit.com/r/LineageOS/comments/684qkp/help_noob_compile_lineageos/
So to make it easy: I want to program a working LineageOS for the LG H990DS, but don't have any understanding about where to start. I do have four years of programming skills, not so much, but know C and C++ well.
Thanks in advance,
Maurice
English isn't my native language, sorry for grammars.
someone help this man up.
Did you check the existing LineageOS thread?
https://forum.xda-developers.com/v20/development/dev-cm14-t3509953/post74550386#post74550386
If you want to help, I'd suggest asking him if there's anything you can do.
Thank you for your response. I do watch that thread, because I want lineageOS for the h990ds device. The problem however is that I don't want to jump right into the code. I want to know what I am doing with each line of code. At the moment I think I have to change some things in the kernel so that it can boot, but I don't know if that's true. And there is so many documentation about how to compile lineageOS, which I don't want to do. I want to program and compile lineageOS. Every tutorial skips the program parts and just compiles lineageOS.
So maybe a good programmer can give my some advice? Where to start and where can I find some documentation?
Best regards,
Maurice
Welcome!
First off, I recommend using Ubuntu 16.04 (I personally use 16.10 however). Be sure to follow the guide you linked from chef central carefully.
For the dual SIM variant, I don't believe any current source exists. Although with the similar hardware and if you have decent skills, you could get it going.
Take a look at the existing v20 trees:
V20-common: https://github.com/LineageOS/android_device_lge_v20-common
Msm8996-common: https://github.com/LineageOS/android_device_lge_msm8996-common
H918 (as a reference): https://github.com/LineageOS/android_device_lge_h918
Kernel: https://github.com/LineageOS/android_kernel_lge_msm8996
Vendor: https://github.com/TheMuppets/proprietary_vendor_lge
Those are the basics to check out. Now I did see someone converted the H918 tree to H990. Here's a link to that for reference: https://github.com/android-device-lge-h990/android_device_lge_h990
You will definitely need to make a custom defconfig in kernel sources. The device tree changes should be rather easy. You'll need to pull vendor files from stock and import the drivers and dts files from stock kernel source. If/when you get a working kernel and device trees there's a 99% chance you will need to Port other drivers and vendor files as stock files don't play nice in aosp. If I were you, I'd start looking through commit history on GitHub to see how the other devices we're brought up. That is how I learned everything.
Also, git will be your best friend when bringing up large projects, like kernel. Learn git, get comfortable with it. Cherry-picking and merging is what keeps us going.
Best of luck!
I suppose you could say there are dueling work-in-progress H990 trees since the other one is: https://github.com/x86cpu/android_device_lge_h990
The one you pointed to is mine. I was hoping for some collaboration with @x86cpu on there (in theory @x86cpu also has permissions to modify that repository, assuming I've set things up correctly). While the initial steps have been done, it is not finished! Some issues are left for getting LineageOS operational on H990 devices.
Of crucial note the modem fix in its current form is unacceptable to LineageOS (despite working). I've got two variants of one solution almost ready, but they're yet ready.
Thank you for your answer and I will look into it. I sure hope that I can help you some day, but first I want to understand the repository. After that I will help you both to code.
Really thank you and I will do my best to catch up with you.
As for the Ubuntu version. I personally use arch Linux (with plasma), because I like it more than Ubuntu. I don't think that's a problem and else I will compile the Ubuntu programs to arch. And I know my way around got. Use it for about 4 years now and now what merging/branching rebasing etc means and know how to use it.
@emdroidle I could help

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?

Categories

Resources