I have for a long time wanted a Android TV.
But those are expensive. So I still have my good old flat screen upgraded whit a chromcast 2.
BUT I WANT MORE!!! And i came across a project here on xda (details to come).
A ported Android TV ROM to a pi 3 B.
The problem is that I have a pi 3 B+.
There for I won't work.
Also... I want some extra features like twrp recovery and root.
I have tryed to swap files, flash files, extract files, making searches on google. And nothing.
All I know is that the system is a Sony elf system and even that did not help my just a tiny bit.
So my question is how do I get "under the hood" of this ROM that I want to mod?
pi 3 b+ and pi 3b kernels are different so you must compile a new rom with pi 3 b+ source code and android tv source code
That was kinda the plan.
I am working on building a new ROM at the time but I have no idea of what I am doing.
Related
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.
I'm developing some apps for Firefox OS, but am currently limited to doing so on the Firefox OS Simulator. I'd like to flash Firefox OS onto a real device, but I own none of the supported devices, and of some of them I can't even find a single mention anywhere on the internet with the exception of the wiki.
Now I have this very slow Cherry Mobility Android JB (originally ICS) tablet lying around. Would there be any chance of getting Firefox OS running properly on this device, or is it a lost case? If I remember correctly, it has Linux 3.2 underneath it (the Android ROM which is currently on the tablet, I mean). Would I be able to extract the drivers from the Android ROM and use them with Firefox OS?
if you play around with the manifest xml files, you might have some success. You could have a look at the threads of the nexus (forum.xda-developers.com/showthread.php?t=1924367) or samsung ports () to get a better idea of porting. You can also have a look at B2G, might help you out.
Hey folks,
I've an old banana pi m2 berry which is working with armbian.
I just found an Tutorial to install Android TV on an Raspberry via LineAgeOS.
I tried LineAgeOS but it seems to won't work on my Banana Pi.
Any fast solution? Also would be fine to switch the OS of my Device again. Just want this for streaming etc on my TV.
I'm not an expert, but my guess is it's unlikely as Android TV is a modified version of Android, and Android is a long ways away from its original source of Linux. The reason Konstakang used Lineage is likely because it's based on android.
Maybe I find some other android Version which works on my device, thanks for the hint.
Hello XDA community,
After months of struggling im in desperate need of your help.
What is my goal?
To compile our own kernel so we can mess around with Qualcomm's trustzone.
Where did it all start?
It all started a few months ago back in November 2021 when me and a friend read a blog about a Trustzone exploit in Qualcomm's MSM8974 processor. (link to the blog)
Big noobs as we where, we where getting hyped an bought ourselves a Samsung Galaxy Note 3 with a MSM8974 processor. After messing around with the device we learned more and more about android and the workings of the software. We first started to root the phone and play around with ADB. After that we found that we can use Frida aswell. But all of it didn't lead to the result we wanted. So we started to dig deeper in to the write-up of the blog. We soon came to the conclusion that we where not even close to doing the right thing.
What happend next?
After we came to the conclusion that ADB and Frida is not enough we understood we need to build our own kernel for this exploit to work. So we do what we always do and that was start googling and watch YouTube. By doing that we found 2 different kernels:
Lineage 18.1
SM-N9005_EUR_LL_Opensource
We where over the moon because inside the folders we found the the files that need to be replaced for the exploit to work. So we replaced the files and try to compile the kernel by using this YouTube tutorial. Everything seemed to go well, we made the
Code:
make msm8974_sec_defconfig
and we run
Code:
make menuconfig
so far so good. the last and final step should be to run
Code:
make
to compile the kernel. And that is where it went wrong an ran in to a error.
Then what?
Then we started to compare the original files with the modified files and we found out that it wasn't just a few modifications in the code but the code was different. So we did what we always do, go back to the source. So back at the blog we thought maybe its because they modified a Nexus 5 at android 4.4.4.
Now what?
Now im trying to find the source of a android 4.4.4 kernel of msm8974 so we can compare those files to the modified files. So if anyone has useful info or knows where to find a kernel for android 4.4.4 for a Samsung Galaxy Note 3 (SM-N9005).
TLDR;
Im looking for a source of android 4.4.4. for a Samsung Galaxy Note 3 (SM-N9005) (hlte)
Well, unfortunately today almost no one uses android 4.4.4. even that have the exact same device, I am using Android 11 on my phone.
I recommend not wasting your time on a kernel for Android 4.4.4. And if you really want to make a kernel for this device I need one for Android 10 and above.
Also I think making a kernel for AOSPs like LineageOS or HavocOS or crDroid ETC is much easier.
A.M.2.K.M said:
Well, unfortunately today almost no one uses android 4.4.4. even that have the exact same device, I am using Android 11 on my phone.
I recommend not wasting your time on a kernel for Android 4.4.4. And if you really want to make a kernel for this device I need one for Android 10 and above.
Also I think making a kernel for AOSPs like LineageOS or HavocOS or crDroid ETC is much easier.
Click to expand...
Click to collapse
Thanks for your response I will look in to it. not sure if it will be easier because the files that needed to be changed are:
arch/arm/mach-msm/scm.c
arch/arm/mach-msm/include/mach/scm.h
drivers/misc/qseecom.c
SwAgLaNdeR said:
Thanks for your response I will look in to it. not sure if it will be easier because the files that needed to be changed are:
arch/arm/mach-msm/scm.c
arch/arm/mach-msm/include/mach/scm.h
drivers/misc/qseecom.c
Click to expand...
Click to collapse
Well, I don't know much about kernels.
I said it's easier because I thought it's a pure and raw operating system. But now according to your post it turns out it's not easier.
Plus almost no developers left for this now very old model .
Hi, I have an Android TV based set-top box using Hi3798mv100 chip. Does anyone have Android TV AOSP firmware for this chip?
I found repo have part of AOSP source code, but it miss some important files. https://github.com/wudilsr/HiSTBAndroid
P/s: I am new to AOSP as long as Android TV build. Have any guide build Android TV firmware from source? Thank everyone!
0x2f0713 said:
Hi, I have an Android TV based set-top box using Hi3798mv100 chip. Does anyone have Android TV AOSP firmware for this chip?
I found repo have part of AOSP source code, but it miss some important files. https://github.com/wudilsr/HiSTBAndroid
P/s: I am new to AOSP as long as Android TV build. Have any guide build Android TV firmware from source? Thank everyone!
Click to expand...
Click to collapse
Hi! It's been almost one and a half month since I began experimenting with this TV box. Still can't get to Android recovery mode. We can work together to achieve this goal! Regards! Sebastian.