Hi guys,
I'm not a Dev but I want to talk about something interesting in the Android modding scene.
A Dev called Michael Zimmermann is developing a Grub version fof Qualcomm Android Devices (LG G2...!).
I know there is a petition made by Sebastian Jena asking LG an Unlock software for LG Devices, but this could be an alternative too.
Here some information about the project thanks to Joey Rizzoli:
Code:
Let me talk about #GRUB4Android ( #G4A ).
You might have eared something about it, not much up to now because there's nothing released for users.
Let's start: what's it?
First of all this amazing project is developed by +Michael Zimmermann I am NOT the dev��
G4A is a port of the well-known GNU GRUB bootloader to Qualcomm (up to now) (android) devices.
Many when it was announced asked: will we be able to boot windows or <insert Linux distro here> ?
The answer is partially no. At least it's not the main goal of the project, bit grub is able to boot a linux distro,
cuz it's the same bootloader you may have on your pc. Actually G4A is used as multiboot solution for android, like multirom.
Android ROMs are not designed for multiboot and you see that (for example) on multirom: you need a kernel with kexec-hardboot, a custom recovery and huge crazy hacks on ramdisk.
Damn, this makes your device crazy... G4A is different. Totally different. Much easier. Better.
So how does it works?
One of the rules is to make the less impact on system as possible. G4A only needs a custom boot loader.
Qualcomm released LK (their bootloader that every qcom device uses) sources.
This bootloader support almost all qcom soc, even old ones such as msm7x27.
This bootloader was hacked with some additions like uboot api (that's used to load grub).
Now the problem is booting that lk. There are two ways: let's start with the easier:
Some devices allow us to boot unsigned bootloader images (that's dangerous on security side) but we use that to write our hacked lk that will boot grub and stop. Other (and most) devices don't support unsigned bootloaders.
The bootloader is flashed both on boot and recovery partitions. Then the magic show starts.
We call this 2th boot: the stock bootloader thinks it's booting a kernel (or recovery) while it's booting another bootloader, stunningly easy and stupid.
The 2th bootloader will detect from which partition is loaded and it will choose to boot straight to recovery or of it has to load grub.
Grub is placed on a folder (boot/grub) placed on NAND, usually on sdcard and protected from user by fuse and rw permissions.
When you boot android, the bootloader will load grub, this one will make you choose what to boot recovery, system, a multibooted system, recovery running "on" a multibooted system etc.
Ofc the ramdisk has to be hacked, but to keep rom intact, the hacks are done on-the-go.
How can I install it/ manage multibooted systems?
G4A will be releases with an app called 'GRUB Manager' that will install it with a few clicks,
you just need root and an unlocked bootloader.
This app will help you creating and managing systems by adding entries to grub.cfg (for who knows how grub works).
Which devices will be supported?
Almost all qcom-powered devices can run this, the port is surprisingly easy (for devs ofc), it may take you just an half hour. Currently official supported devices are: Xiaomi Mi2(s), Motorola Moto E and Xiaomi Redmi 1s.
If you're an expert dev and you've done a port for your device/ you're interested in, hangout me.
ETA?
Sorry not eta allowed, the first build will be for devs and advanced users (I remember that on some devices we write on bootloader partition, if something goes wrong, it's not so easy to recover it) when multiboot will be fully working (now about 80%).
To sum up
> G4A is an opensource project that has the goal to provide the best multiboot solution for qcom devices
> There are two ways to install this: on bootloader and 2th boot
> The GRUB Manager app will install G4A and it will manage multibooted systems
> It can support almost all qcom devices
> It will be released soon for devs and advanced users as a first public beta
Some links:
Follow +GRUB4Android for news
Official website
Sources
Community
News: Please, see also Dual-boot stock 4.4.2/cloudyG3 and SLIMROM!
EDIT: LG starts to unlock bootloader, first of all the new LG G4:
- LG Developers
Damn, LG International decided to DO NOT UNLOCK Bootloader of any previously launched model before LG G4 H815.
See the image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Woot woot!
Great news!
=)
iall5tar said:
Woot woot!
Great news!
=)
Click to expand...
Click to collapse
I hope to see a super DEV or maybe a Dev Team that could port this Bootloader to LG G2!
Interesting. Will definitely stay tuned in for this.
Maxximo88 said:
I hope to see a super DEV or maybe a Dev Team that could port this Bootloader to LG G2!
Click to expand...
Click to collapse
There's no need of a super-dev team to do that, the port can be done in a few minutes (if you're lucky) and if you have an UART to debug the bootloader.
Btw since I guess that the phone doesn't accept unsigned images this bootloader won't replace the stock one but u can use its fastboot mode to have fun with fastboot without have to worry about the stock bootloader.
Me too!ahahaha
tsunamical said:
Interesting. Will definitely stay tuned in for this.
Click to expand...
Click to collapse
Me tooo!
Any good news then guys
Sent from my LG-D802 using xda premium
serseri22 said:
Any good news then guys
Sent from my LG-D802 using xda premium
Click to expand...
Click to collapse
I'm not a Dev, I just want to share with G2 Community this news!
So is there any Dev that interesting to port this to our LG g2 or no one really bothered
Sent from my LG-D802 using xda premium
serseri22 said:
So is there any Dev that interesting to port this to our LG g2 or no one really bothered
Sent from my LG-D802 using xda premium
Click to expand...
Click to collapse
Yes, this is the right question! Ehehe
This won't help you to unlock your devices, but once you got support by LGE or sbd. hacked the bootloader you/we/I can port GRUB to this device
Two things, first, who's SBD? And second, does this not allow you to bypass the bootloader similar to loki? As it said something along those lines for phones with locked bootloaders?
m11kkaa said:
This won't help you to unlock your devices, but once you got support by LGE or sbd. hacked the bootloader you/we/I can port GRUB to this device
Click to expand...
Click to collapse
plasmaboltrs said:
Two things, first, who's SBD? And second, does this not allow you to bypass the bootloader similar to loki? As it said something along those lines for phones with locked bootloaders?
Click to expand...
Click to collapse
@m11kkaa he's right, with Loki g2 users can bypass bootloader and flash bootimgs and recoveries, so I don't see problems if they use 2thboot cuz u can write on boot and recovery. @plasmaboltrs sbl is second boot loader, it's a partition u have where u can find the 2th bloader
Sent from my mi²s
he meant "sbd."=somebody
Also, Loki is a exploit. It worked because LK(the (stock) bootloader) did not check if the kernel loading address covers bootloader memory. This has been fixed already - at least by qcom.
What you say sounds like this device has LOKI already. in this case there's no reason why you shouldn't be able to flash custom kernels and ROM's.
@m11kkaa and @linuxxxx, thanks for explaining to my ignorant self.
Well, hopefully we'll see some progress on this, cause I have no idea how to do anything but flash ROMs haha
I have to learn at some point, but exams now.
Anyway, thanks for the help,
plasmaboltrs
@m11kkaa, I do already have a custom rom that I run (CloudyG3), it works well, but I want many more ROMs. Cause, as above, I'm a flashaholic
I did have multirom but that didn't work for stock AND aosp based ROMs, it was one or the other; so seeing as there hasn't been much progress there, I hoped this would take off.
Well, we(I)'ll have to wait and see,
plasmaboltrs
It's nice to see interest on this topic..Loki bypass the locked bootloader, but Multirom needs to go ahead..
Multirom doesn't work due to the locked bootloader which means it can't kexec boot the second kernel. There was interest in autoboot by @savoca which may fix this but then it died away.
Hopefully someone who knows more than me will put this together and make it work, so I can be a flashaholic
I'll learn the basics these coming holidays hopefully, though not much as I'm away for most of it.
plasmaboltrs said:
Multirom doesn't work due to the locked bootloader which means it can't kexec boot the second kernel. There was interest in autoboot by @savoca which may fix this but then it died away.
Hopefully someone who knows more than me will put this together and make it work, so I can be a flashaholic
I'll learn the basics these coming holidays hopefully, though not much as I'm away for most of it.
Click to expand...
Click to collapse
There is already a multiboot alpha that is working on original dev forum
@Raagh, I'm guessing you mean multirom not multiboot. I do know of this, as mentioned above, however it misses the crucial feature of allowing one to have both stock and AOSP based ROMs. This is due to the fact it cannot boot the second kernel.
Ideally, this would fix that, similar to @savoca's autoboot.
I have no idea how these things work, only how to flash haha. So, guys, developers, anyone who has a clue, please take a look and see if you may break through and succeed in patching something together for me and my fellow flashaholics
Thanks in advance,
plasmaboltrs
Related
The term BUMPed is the only term I am unfamiliar with as I delve deeper into Android modification. I constantly hear the term BUMPed recovery, BUMPed bootloader, This will only work if you're bumped, etc. Everytime I google this question I find people referencing the term bump as a forum post method, nothing to do with android modification.
I appreciate anyone who takes the time to respond and will indeed be sure to give thanks.
Regards, d00lz.
Me too, I have never heard ppl talking about differences between "bumped" and "non-bumped"
It is what is needed to flash custom stuff on an some newer LG devices due to its locked down nature.
zelendel said:
It is what is needed to flash custom stuff on an some newer LG devices due to its locked down nature.
Click to expand...
Click to collapse
that's pretty much it. bumped essentially just means signed. "bumping" an image is required for LG devices with locked bootloaders, it's basically just signing the image with LG keys to bypass the bootloader's security checks.
EDIT: We got it! It boots. But some things like RIL and audio are not working, but we'll get this sorted out soon.
Official thread here: http://forum.xda-developers.com/opt...opment/rom-cyanogenmod-12-1-lg-l3-ii-t3297897Hey guys! It seems like Caio has left the "scene", and we're left with CM11... Is there anyone able to "take over" the development of CM12 for E430? I know a little bit, but I can't do it myself....
Alright, what do we have?
A local manifest: https://github.com/TeamVee/android_.repo_local_manifests/tree/cm-12.1 that includes:
A device tree for CM11: https://github.com/TeamVee/android_device_lge_vee3
Vendor files for CM11: https://github.com/TeamVee/android_vendor_lge
Kernel for KitKat: https://github.com/TeamHackLG/lge-kernel-lproj
Display CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_display
Media CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_media
Shared L1/L3/L7 II files for CM12.1: https://github.com/TeamVee/android_device_lge_vee-common/tree/cm-12.1
We also have a build of CM12.1 recovery for E430 by me. Nevermind, broken.
L5's device tree for CM12.1: https://github.com/aidasaidas75/android_device_lge_e610
L5's vendor propretiary files for CM12.1: https://github.com/aidasaidas75/proprietary_vendor_lge/tree/cm-12.1-new/e610
What do we probably need?
A device tree for CM12.1 for L3 IINot needed.
Vendor files for CM12.1 for L3 IINot needed.
Lollipop kernel.Not needed.
We need a skilled developer/group of developer to do this. Anyone willing to participate? Any help is appreciated
Some more details: when I build CM12.1, it stops after building surfaceflinger. If you got any questions, ask me
Feel free to join me at the IRC channel for a little mindstorm: http://webchat.quakenet.org/?channels=teamvee
EDIT: I managed to build CM12.1 for LG L3 II, but I don't know if it's working or not - download here and tell me: https://www.androidfilehost.com/?fid=24345424848488130
Everyone, if you can help us create CM12.1, PM me your Telegram username (a great IM), I'll add you to a group chat. @aidasaidas75 @IGGYVIP and other devs are welcome.
dadziokPL said:
Hey guys! It seems like Caio has left the "scene", and we're left with CM11... Is there anyone able to "take over" the development of CM12 for E430? I know a little bit, but I can't do it myself....
Alright, what do we have?
A local manifest: https://github.com/TeamVee/android_.repo_local_manifests/tree/cm-12.1 that includes:
A device tree for CM11: https://github.com/TeamVee/android_device_lge_vee3
Vendor files for CM11: https://github.com/TeamVee/android_vendor_lge
Kernel for KitKat: https://github.com/TeamHackLG/lge-kernel-lproj
Display CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_display
Media CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_media
We also have a build of CM12.1 recovery for E430 by me. It's the only thing we can build with the local manifest. Download here: https://mega.nz/#!Io0xxBrR!gCin0V8pDZ_-PqAGTC05PfUEWTbdLhgqdBBMjnBrhdI (I would put it in the attachments, but it's 0.43 MB too big... Dammit :/
What do we probably need?
A device tree for CM12.1
Vendor files for CM12.1
Lollipop kernel.
We need a skilled developer/group of developer to do this. Anyone willing to participate? Any help is appreciated
Some more details: when I build CM12.1, it stops after building surfaceflinger. If you got any questions, ask me
Feel free to join me at the IRC channel for a little mindstorm: http://webchat.quakenet.org/?channels=teamvee
Click to expand...
Click to collapse
First you forgeted https://github.com/TeamVee/android_device_lge_vee-common and second i will still here if anyone need, i builded CM12.1 but, without any reason, the ROM not boot, but i not tried again.
Possible, maybe, i try to build this again after update of MK.
And my last TWRP is from CM12.1
Caio99BR said:
First you forgeted https://github.com/TeamVee/android_device_lge_vee-common and second i will still here if anyone need, i builded CM12.1 but, without any reason, the ROM not boot, but i not tried again.
Possible, maybe, i try to build this again after update of MK.
And my last TWRP is from CM12.1
Click to expand...
Click to collapse
Yeah, it's that recovery I built Also, I can't test ROMs for L3 II anymore, I changed to Windows Phone But I think my cousin still has my old L3 II. I'll see. BTW I got a new PC, with a quad-core Intel Core i5-4460, and I set up a VM on it, so can build and build and build BTW You don't have to build, it's not building...
I can test anything I've got dev phone e430 and not scared of bricks. So dangerous builds send to me first before you flash yourself new paper weight ...
Caio where did you get drivers for kk ? What device ? Does it have lollipop?
Also I'm not sure if possible to get lollipop working at all since bootloader will need upgrade too :/
IGGYVIP said:
I can test anything I've got dev phone e430 and not scared of bricks. So dangerous builds send to me first before you flash yourself new paper weight ...
Caio where did you get drivers for kk ? What device ? Does it have lollipop?
Also I'm not sure if possible to get lollipop working at all since bootloader will need upgrade too :/
Click to expand...
Click to collapse
I'm a noob. Explain to me, why will the bootloader need an upgrade? It worked fine from 4.1 to 4.4. Has Lollipop brought some new kinda... thing? I was also wondering how Caio got the drivers... And have you tried that recovery for CM12.1? Is it working? I can't test myself since I don't have that phone anymore. Technically I do, but I can't brick it.
Need more info and need a dev
dadziokPL said:
I'm a noob. Explain to me, why will the bootloader need an upgrade? It worked fine from 4.1 to 4.4. Has Lollipop brought some new kinda... thing? I was also wondering how Caio got the drivers... And have you tried that recovery for CM12.1? Is it working? I can't test myself since I don't have that phone anymore. Technically I do, but I can't brick it.
Click to expand...
Click to collapse
The bootloader I'm not 100% sure but all older devices needed bootloader upgrade before they booted into lollipop from kk.
Something about secure boot and the new way it handles things.
Not tested the recovery yet but no point yet really
first we need more info on what we stand on in terms of bootloader / drivers
Caio99BR are you here ?
What device did you use as base for cm11 on L3II ?
Also I think this phone has already done very big jump with 4.4.4 and running over 150% intended level.
Lets face it Lollipop will never be stable enough to be daily driver specially that making custom lollipop kernel is near impossible without proper sources ... And stock one (still not existing lollipop one) will be super slow with no useful functions.
I would like to see it happen but it will take pain and broken fingers from hitting keyboards
I'm just not sure if it makes sense since screen resolution is so low and general hardware is not ready for functions brought by 5.1
Basically there will be more pain than gain good for side project but not really something for public
4.4.4 on it is great and I think it should gracefully get old here with all the tweaks we managed
IGGYVIP said:
The bootloader I'm not 100% sure but all older devices needed bootloader upgrade before they booted into lollipop from kk.
Something about secure boot and the new way it handles things.
Not tested the recovery yet but no point yet really
first we need more info on what we stand on in terms of bootloader / drivers
Caio99BR are you here ?
What device did you use as base for cm11 on L3II ?
Also I think this phone has already done very big jump with 4.4.4 and running over 150% intended level.
Lets face it Lollipop will never be stable enough to be daily driver specially that making custom lollipop kernel is near impossible without proper sources ... And stock one (still not existing lollipop one) will be super slow with no useful functions.
I would like to see it happen but it will take pain and broken fingers from hitting keyboards
I'm just not sure if it makes sense since screen resolution is so low and general hardware is not ready for functions brought by 5.1
Basically there will be more pain than gain good for side project but not really something for public
4.4.4 on it is great and I think it should gracefully get old here with all the tweaks we managed
Click to expand...
Click to collapse
Ohh, secure boot, alright. I see.
I heard that Lollipop actually runs better than KitKat, and it was optimized for devices with 512 MB of RAM.
At least we can try and get it to build. We can build a recovery, which is a first step according to the porting wiki
So, I was right, we need device files, vendor files, and a kernel for Lollipop?
If Caio could tell us where he got the files for KitKat, we could do something....
IGGYVIP said:
I can test anything I've got dev phone e430 and not scared of bricks. So dangerous builds send to me first before you flash yourself new paper weight ...
Caio where did you get drivers for kk ? What device ? Does it have lollipop?
Also I'm not sure if possible to get lollipop working at all since bootloader will need upgrade too :/
Click to expand...
Click to collapse
First only the Adreno is not updated, because of vsync is broken and new Adreno Blobs use hwcomposer and this is broken because vsync. When i tried to test in KK with new Adreno Blobs this happened:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Second from L5, and yes but @aidasaidas75 confused all commits, and not said the recipe to anyone.
And last i have thought this but no way to change this, the display driver of bootloader is hard edited by LG, yes i tried.
Note: No one build can make a brick of device, only if fstab is edited
dadziokPL said:
I'm a noob. Explain to me, why will the bootloader need an upgrade? It worked fine from 4.1 to 4.4. Has Lollipop brought some new kinda... thing? I was also wondering how Caio got the drivers... And have you tried that recovery for CM12.1? Is it working? I can't test myself since I don't have that phone anymore. Technically I do, but I can't brick it.
Click to expand...
Click to collapse
And not say drivers, say vendor blobs or kernel drivers, this not is windows
IGGYVIP said:
The bootloader I'm not 100% sure but all older devices needed bootloader upgrade before they booted into lollipop from kk.
Something about secure boot and the new way it handles things.
Not tested the recovery yet but no point yet really
first we need more info on what we stand on in terms of bootloader / drivers
Caio99BR are you here ?
What device did you use as base for cm11 on L3II ?
Also I think this phone has already done very big jump with 4.4.4 and running over 150% intended level.
Lets face it Lollipop will never be stable enough to be daily driver specially that making custom lollipop kernel is near impossible without proper sources ... And stock one (still not existing lollipop one) will be super slow with no useful functions.
I would like to see it happen but it will take pain and broken fingers from hitting keyboards
I'm just not sure if it makes sense since screen resolution is so low and general hardware is not ready for functions brought by 5.1
Basically there will be more pain than gain good for side project but not really something for public
4.4.4 on it is great and I think it should gracefully get old here with all the tweaks we managed
Click to expand...
Click to collapse
I think you wanted to say the kernel and ramdisk.
Use "@" i will see this in seconds
I used L5/L7/MSM7x27a-Common/and some others msm7x27a devices
I think this cant be able to daily usage, but with DualBootPatcher, all will be possible.
I have through this too, but the Android Wear saved us , and if this work is a good progess, btw the last.
dadziokPL said:
Ohh, secure boot, alright. I see.
I heard that Lollipop actually runs better than KitKat, and it was optimized for devices with 512 MB of RAM.
At least we can try and get it to build. We can build a recovery, which is a first step according to the porting wiki
So, I was right, we need device files, vendor files, and a kernel for Lollipop?
If Caio could tell us where he got the files for KitKat, we could do something....
Click to expand...
Click to collapse
Device tree, vendor files and kernel need someone with experience to this, like @aidasaidas75, but him left L5 CM12 support.
My english is bad and my keyboard too
Sorry for mistypes and long post.
Topic subscript agan of right way now!
---------- Post added at 10:54 PM ---------- Previous post was at 10:52 PM ----------
See DualBoot Custom ROMs on the LG L3 II (via PC) in TOP FORUM DISCUSSIONS -------------------->
Just for case
Caio99BR said:
First only the Adreno is not updated, because of vsync is broken and new Adreno Blobs use hwcomposer and this is broken because vsync. When i tried to test in KK with new Adreno Blobs this happened:
Second from L5, and yes but @aidasaidas75 confused all commits, and not said the recipe to anyone.
And last i have thought this but no way to change this, the display driver of bootloader is hard edited by LG, yes i tried.
Note: No one build can make a brick of device, only if fstab is edited
And not say drivers, say vendor blobs or kernel drivers, this not is windows
I think you wanted to say the kernel and ramdisk.
Use "@" i will see this in seconds
I used L5/L7/MSM7x27a-Common/and some others msm7x27a devices
I think this cant be able to daily usage, but with DualBootPatcher, all will be possible.
I have through this too, but the Android Wear saved us , and if this work is a good progess, btw the last.
Device tree, vendor files and kernel need someone with experience to this, like @aidasaidas75, but him left L5 CM12 support.
My english is bad and my keyboard too
Sorry for mistypes and long post.
Topic subscript agan of right way now!
---------- Post added at 10:54 PM ---------- Previous post was at 10:52 PM ----------
See DualBoot Custom ROMs on the LG L3 II (via PC) in TOP FORUM DISCUSSIONS -------------------->
Just for case
Click to expand...
Click to collapse
Thanks for clearing up some stuff Caio!
Ok, so here are propertiary files for L5(for CM12.1): https://github.com/aidasaidas75/proprietary_vendor_lge/tree/cm-12.1-new/e610
And here are device blobs for L5(also for CM12.1): https://github.com/aidasaidas75/android_device_lge_e610
Let's see what we can do, we got @IGGYVIP, he knows a lot, and he pretty much started everything with modding L3 II, we can bring CM12.1 for our L3 II together!
I am the orders! e-e
Wow! Let's see what we can do, I can help them in some respects too, and I can test whatever they want. I'm not afraid to have a paperweight, and I know it will be worth it. If they need a Tester, I am the orders!
It's great idea to build CM12 on LG L3 II, and if we need testers, I have working E430 phone, and I can test unstable versions of this ROM.
MinusThousand said:
It's great idea to build CM12 on LG L3 II, and if we need testers, I have working E430 phone, and I can test unstable versions of this ROM.
Click to expand...
Click to collapse
Okay, but we need to get it to build first. It won't build, there are errors, we need a proper device tree and proprietary blobs for CM12.1.
dadziokPL said:
Hey guys! It seems like Caio has left the "scene", and we're left with CM11... Is there anyone able to "take over" the development of CM12 for E430? I know a little bit, but I can't do it myself....
Alright, what do we have?
A local manifest: https://github.com/TeamVee/android_.repo_local_manifests/tree/cm-12.1 that includes:
A device tree for CM11: https://github.com/TeamVee/android_device_lge_vee3
Vendor files for CM11: https://github.com/TeamVee/android_vendor_lge
Kernel for KitKat: https://github.com/TeamHackLG/lge-kernel-lproj
Display CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_display
Media CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_media
Shared L1/L3/L7 II files for CM12.1: https://github.com/TeamVee/android_device_lge_vee-common/tree/cm-12.1
We also have a build of CM12.1 recovery for E430 by me. It's the only thing we can build with the local manifest. Download here: https://mega.nz/#!Io0xxBrR!gCin0V8pDZ_-PqAGTC05PfUEWTbdLhgqdBBMjnBrhdI (I would put it in the attachments, but it's 0.43 MB too big... Dammit :/
L5's device tree for CM12.1: https://github.com/aidasaidas75/android_device_lge_e610
L5's vendor propretiary files for CM12.1: https://github.com/aidasaidas75/proprietary_vendor_lge/tree/cm-12.1-new/e610
What do we probably need?
A device tree for CM12.1 for L3 II
Vendor files for CM12.1 for L3 II
Lollipop kernel.
We need a skilled developer/group of developer to do this. Anyone willing to participate? Any help is appreciated
Some more details: when I build CM12.1, it stops after building surfaceflinger. If you got any questions, ask me
Feel free to join me at the IRC channel for a little mindstorm: http://webchat.quakenet.org/?channels=teamvee
Click to expand...
Click to collapse
Actually device l5 is not set correctly in your tread tbh almost all l5 dependencies set wrong in op even display caf
aidasaidas75 said:
Actually device l5 is not set correctly in your tread tbh almost all l5 dependencies set wrong in op even display caf
Click to expand...
Click to collapse
Yo dude long time no see
Any chance you could make git group with correct base set of whats there that can be used to build for vee3 ? (I'm aware there will be a lot to do and missing stuffs but nice set from you would be a great start )
IGGYVIP said:
Yo dude long time no see
Any chance you could make git group with correct base set of whats there that can be used to build for vee3 ? (I'm aware there will be a lot to do and missing stuffs but nice set from you would be a great start )
Click to expand...
Click to collapse
I started building again so it might be lucky day for e430
@aidasaidas75 happy days pure cm or else ?
@freeusername
Yo santy
Would you be interested in the challenge of kernel ?
We could really use your experience with custom building this
MERRY CHRISTMAS ALL
IGGYVIP said:
@aidasaidas75 happy days pure cm or else ?
@freeusername
Yo santy
Would you be interested in the challenge of kernel ?
We could really use your experience with custom building this
MERRY CHRISTMAS ALL
Click to expand...
Click to collapse
Kernel is easy peazy lemon squizy. I was hooked on csgo but now synched cm12.1 and and started messing around it . I have new git and started everything from scratch for e610 and e430
aidasaidas75 said:
Kernel is easy peazy lemon squizy. I was hooked on csgo but now synched cm12.1 and and started messing around it . I have new git and started everything from scratch for e610 and e430
Click to expand...
Click to collapse
Cool, seems like the Optimus L series won't die so quick! Thanks to people like you, IGGYVIP or Caio the L3 II is usable. My Lumia 535 was sent to repair a MONTH ago, and they are still waiting for parts to arrive. I got a substitute device from my carrier, and surprise surprise, it's the L3 II. I know it's not my device, and that I'll have to pay if they figure out that I installed a custom ROM, but I couldn't resist. I installed CM11. The stock ROM is complete ****, it's laggy and unusable. I don't know for how much longer, but I can test. And when I'll have to return the L3 II, my cousin that got my old L3 II from me said that he'll test for me
I created this thread to encourage people to keep making ROMs for this phone, and it seems like we got our best developers back! I'll help you as much as I can, but I'm not as advanced as you guys! Although I learned how to build Cyanogenmod from source, and I got a great PC, building CM11(with cache enabled)on a VM took not even an hour! If you want me to do something, just tell me, I got lots of free time, and I'll do what I can to help!
Good luck to y'all, let's see what we can make together!
dadziokPL said:
Cool, seems like the Optimus L series won't die so quick! Thanks to people like you, IGGYVIP or Caio the L3 II is usable. My Lumia 535 was sent to repair a MONTH ago, and they are still waiting for parts to arrive. I got a substitute device from my carrier, and surprise surprise, it's the L3 II. I know it's not my device, and that I'll have to pay if they figure out that I installed a custom ROM, but I couldn't resist. I installed CM11. The stock ROM is complete ****, it's laggy and unusable. I don't know for how much longer, but I can test. And when I'll have to return the L3 II, my cousin that got my old L3 II from me said that he'll test for me
I created this thread to encourage people to keep making ROMs for this phone, and it seems like we got our best developers back! I'll help you as much as I can, but I'm not as advanced as you guys! Although I learned how to build Cyanogenmod from source, and I got a great PC, building CM11(with cache enabled)on a VM took not even an hour! If you want me to do something, just tell me, I got lots of free time, and I'll do what I can to help!
Good luck to y'all, let's see what we can make together!
Click to expand...
Click to collapse
Wow, you will gonna have a bad time if something goes wrong with you substitute device , just for case not test the CM12 builds, and i updated device tree (vee-common) and local manifests, these are the Display and Media repos used in CM12.1 by @aidasaidas75:
https://github.com/SlimLP-Y300/android_hardware_qcom_display-caf
https://github.com/SlimLP-Y300/hardware_qcom_media
Just for case (i like this phrase ), my inspiration is people like you and these awesome devs who cares for keep this device alive (but sometimes get crazy and disappear sometimes because they are also people ).
Note: i will be still here, just for case :silly::victory:
Caio99BR said:
Wow, you will gonna have a bad time if something goes wrong with you substitute device , just for case not test the CM12 builds, and i updated device tree (vee-common) and local manifests, these are the Display and Media repos used in CM12.1 by @aidasaidas75:
https://github.com/SlimLP-Y300/android_hardware_qcom_display-caf
https://github.com/SlimLP-Y300/hardware_qcom_media
Just for case (i like this phrase ), my inspiration is people like you and these awesome devs who cares for keep this device alive (but sometimes get crazy and disappear sometimes because they are also people ).
Note: i will be still here, just for case :silly::victory:
Click to expand...
Click to collapse
These are for Huawei Y300/G510. Are you sure these are gonna work?
Also, my carrier valued the phone at around 25 euro, If they figure out, I'll just have to pay it, but I can keep the phone forever, no big deal
To start off...
Im aware this question has been asked before. But instead of leading with "does someone want to do this for me" while I make zero contribution is not my aim.
I have compiled what seems to me a valid course of action to Port MIUI 8 to Angler and am looking for a couple Devs/Hobbyists that want to hop in with me and get it done.
Dont like MIUI?
Think it's a waste of time?
Cool, There are a ton of Xposed and Stock rom threads to go and spend your time trolling on.
Now, on to the data...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There have been a lot of setbacks in the last couple years when it comes to MIUI. The OS itself was dated and based off of 4.4 Kit Kat. There weren't many advantages to porting MIUI 7 to Hammerhead. And since Hammerhead shipped with 5.0 out of the box, it also was an uphill climb that no one wanted to take on, Understandably.
But now with Angler and Hammerhead being 6.0.1 as well as MIUI 8 being based on 6.0.1 the process becomes a lot more clear.
How Clear? There are even SnapDragon 810 devices now (Mi Note Pro) that are OEM MIUI 8.
I have made some progress in porting MIUI 8 to Angler based off of CM13 but have ran into some snags and need some Dev's/Advanced users who are much smarter than me to get it done.
Following this thread:
http://www.osbusters.net/2015/11/how-to-port-miui-7-rom-to-qualcomm-smartphones.html
I have been making headway and just got my Macbook Air formatted with ubuntu and got the kitchen and various other tools installed to start making needed adjustments. But honestly I feel like what is needed to get this project off the ground is some simple optimizations and changes through linux that I just truly dont have experience with.
So, you do?
And you want to lend some time possibly?
Let me know.
Thanks, AdA.
MIUI 8
AndroiddiordnA said:
To start off...
Im aware this question has been asked before. But instead of leading with "does someone want to do this for me" while I make zero contribution is not my aim.
I have compiled what seems to me a valid course of action to Port MIUI 8 to Angler and am looking for a couple Devs/Hobbyists that want to hop in with me and get it done.
Dont like MIUI?
Think it's a waste of time?
Cool, There are a ton of Xposed and Stock rom threads to go and spend your time trolling on.
Now, on to the data...
There have been a lot of setbacks in the last couple years when it comes to MIUI. The OS itself was dated and based off of 4.4 Kit Kat. There weren't many advantages to porting MIUI 7 to Hammerhead. And since Hammerhead shipped with 5.0 out of the box, it also was an uphill climb that no one wanted to take on, Understandably.
But now with Angler and Hammerhead being 6.0.1 as well as MIUI 8 being based on 6.0.1 the process becomes a lot more clear.
How Clear? There are even SnapDragon 810 devices now (Mi Note Pro) that are OEM MIUI 8.
I have made some progress in porting MIUI 8 to Angler based off of CM13 but have ran into some snags and need some Dev's/Advanced users who are much smarter than me to get it done.
Following this thread:
http://www.osbusters.net/2015/11/how-to-port-miui-7-rom-to-qualcomm-smartphones.html
I have been making headway and just got my Macbook Air formatted with ubuntu and got the kitchen and various other tools installed to start making needed adjustments. But honestly I feel like what is needed to get this project off the ground is some simple optimizations and changes through linux that I just truly dont have experience with.
So, you do?
And you want to lend some time possibly?
Let me know.
Thanks, AdA.
Click to expand...
Click to collapse
Hi, I recently made an attempt at porting it from the Yu Yureka and could not get it to boot. I would be happy to share my work with you because I would like to use this rom on my Nexus 6P.
I would be extremely happy to see that happing. Don't know if I can contribute (always failed when trying to port previous miui versions) but I will mark this thread !!!
-As far as I understand there is no miui 8 global beta for xiaomi note pro, or did I miss anything?
-I tried the suggested JoelDroid Lollipop Batch Deodexer tool with MIUI 7.5 and it failed at "Boot.oat Extraction"
-> so I am stuck at the very beginning...
Sent from my Nexus 6P using XDA-Developers mobile app
mrmad23 said:
I would be extremely happy to see that happing. Don't know if I can contribute (always failed when trying to port previous miui versions) but I will mark this thread !!!
-As far as I understand there is no miui 8 global beta for xiaomi note pro, or did I miss anything?
-I tried the suggested JoelDroid Lollipop Batch Deodexer tool with MIUI 7.5 and it failed at "Boot.oat Extraction"
-> so I am stuck at the very beginning...
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
There's currently an alpha for the mi note pro (I'm running it on my note pro) however it's based on lollipop not Marshmallow
Sent from my Nexus 6P using Tapatalk
You should use the same Android version, otherwise it will be too complicated or impossible at all.
how far did you get into the process? looping boot animation? Splash screen? does it boot into the OS? Have any logs? I would be willing to help in this process.
So turns out skw5115 is correct. The Xiaomi Mi Note and Mi Note "Pro" are completely different chipsets. The Note "Pro" being Snapdragon 810 and the Regular Note being 801. After looking more deeply into my extracted port rom it became very apparent that I had over looked that minute but critical piece of information.
What is strange is that the 810 is running 5.1 Lollipop and from what I can tell from some digging that the 801 is indeed running 6.0.1?
The Snapdragon 820 is in the Mi5/Pro.
Anyone have any input on whether it would be better to try and make a stab at porting the Mi Note 6.0.1 Rom or the Mi5/Pro 6.0.1 rom?
Thanks, AdA
mattlowry said:
how far did you get into the process? looping boot animation? Splash screen? does it boot into the OS? Have any logs? I would be willing to help in this process.
Click to expand...
Click to collapse
I had not tried to flash anything quite yet I was going to submit my current Port Rom to someone who wanted to take a look at it before I pulled the trigger on a flash.
The internet was down for pretty much the entire state of Florida from 10am till about 4pm today so once I get home tonight and get a chance to get in front of my desktop and ubuntu machine I can't send you what I got. But I will.:fingers-crossed:
Appreciate it,
AdA
AndroiddiordnA said:
I had not tried to flash anything quite yet I was going to submit my current Port Rom to someone who wanted to take a look at it before I pulled the trigger on a flash.
The internet was down for pretty much the entire state of Florida from 10am till about 4pm today so once I get home tonight and get a chance to get in front of my desktop and ubuntu machine I can't send you what I got. But I will.:fingers-crossed:
Appreciate it,
AdA
Click to expand...
Click to collapse
So you are not willing to flash it but want others to? You really need to test it yourself. What kind of snags did you run into? Also, Linux is not required for porting miui. All the tools you need are available for windows
mattlowry said:
So you are not willing to flash it but want others to? You really need to test it yourself. What kind of snags did you run into? Also, Linux is not required for porting miui. All the tools you need are available for windows
Click to expand...
Click to collapse
I had not tried to flash anything quite yet I was going to submit my current Port Rom to someone who wanted to take a look at it before I pulled the trigger on a flash.
Click to expand...
Click to collapse
Wow, No. Never said that. just never ported any stuff 6.0 related. Thought someone could look through it and see if they see anything that I might have messed up on. The .Dat files are all new to me as well so decompressing and recompressing them was a new treat.
I appreciate your willingness to get involved but lets keep from jumping to conclusions...
Im not a Dev. Just a guy trying to get this done in his spare time, following a guide, running into snags, researching them, and now that I felt like I had a better grip on what I was getting into I decided to reach out for some second opinions/guidance. I have bricked enough phones in my lifetime, so sending what I got to someone with some more knowledge to look it over before I pull the trigger isn't unreasonable...
Any input on whether I should try to make a new build based off of the Snapdragon 820 or 801 based 6.0.1? Instead of the Mi Note Pro 5.1...
Thanks,
AdA
AndroiddiordnA said:
Wow, No. Never said that. just never ported any stuff 6.0 related. Thought someone could look through it and see if they see anything that I might have messed up on. The .Dat files are all new to me as well so decompressing and recompressing them was a new treat.
I appreciate your willingness to get involved but lets keep from jumping to conclusions...
Im not a Dev. Just a guy trying to get this done in his spare time, following a guide, running into snags, researching them, and now that I felt like I had a better grip on what I was getting into I decided to reach out for some second opinions/guidance. I have bricked enough phones in my lifetime, so sending what I got to someone with some more knowledge to look it over before I pull the trigger isn't unreasonable...
Any input on whether I should try to make a new build based off of the Snapdragon 820 or 801 based 6.0.1? Instead of the Mi Note Pro 5.1...
Thanks,
AdA
Click to expand...
Click to collapse
Sorry didn't mean to sound like a douche. Im not a dev either but miui does not require a dev to port it. The Mi5 with the 820 would be the one I would try first. Where are you getting your miui Roms from? You shouldn't have to recompress the day images either, unless you want to. Do you have a Windows PC? Hit me up on hangouts [email protected]
mattlowry said:
Sorry didn't mean to sound like a douche. Im not a dev either but miui does not require a dev to port it. The Mi5 with the 820 would be the one I would try first. Where are you getting your miui Roms from? You shouldn't have to recompress the day images either, unless you want to. Do you have a Windows PC? Hit me up on hangouts [email protected]
Click to expand...
Click to collapse
Roms I am using are found here.
http://en.miui.com/thread-306329-1-1.html
mattlowry said:
Sorry didn't mean to sound like a douche. Im not a dev either but miui does not require a dev to port it. The Mi5 with the 820 would be the one I would try first. Where are you getting your miui Roms from? You shouldn't have to recompress the day images either, unless you want to. Do you have a Windows PC? Hit me up on hangouts [email protected]
Click to expand...
Click to collapse
I have found a Fastboot image for the Mi5 but no recovery .zip yet. But miui 8 for mi5 sd820 does exist.
http://www.xiaomidevice.com/blog/miui-8-china-alpha-rom-download/
I don't think it is a good idea to port a ROM bases on a different Android version AND/OR CPU chipset.
It's late, way later than I thought I would be up messing around with this project but I have it bootlooping! Have it uploading now, will post the link in the morning if anyone wants to mess around with it. Tomorrow ill run some logcats and see where im at and post a more detailed update of what needs to be done.
Gnight ,
AdA
https://www.androidfilehost.com/?a=show&w=files&flid=18823 this is where I get the miui roms from. these are already decompressed and easy to edit.
---------- Post added at 10:16 AM ---------- Previous post was at 10:14 AM ----------
mrmad23 said:
I don't think it is a good idea to port a ROM bases on a different Android version AND/OR CPU chipset.
Click to expand...
Click to collapse
good thing we are using the same android version then
Upload froze last night while I was sleeping, Cant upload it until I get home tonight. But nice find on the .zips :good:
AndroiddiordnA said:
Upload froze last night while I was sleeping, Cant upload it until I get home tonight. But nice find on the .zips :good:
Click to expand...
Click to collapse
what about your logs? can you upload those?
mattlowry said:
what about your logs? can you upload those?
Click to expand...
Click to collapse
Not getting an ADB connection or any connection for that matter when it is at bootscreen and plugged in.
Is there another way of getting a Logcat? Not too familiar with that process...
I attempted to port MIUI v7 from Mi5 using CM13.0 nightly. I got adb running at boot, it is clearly in bootloop mode throwing some sick fatal codes in logcat. Could be something I did, could be numerous things. I'll post the boot.img, the flashable ZIP I created, will also post a logcat shortly.
Boot.img (flash using Fastboot method):
https://drive.google.com/open?id=0B-XY4f_OwITFc2tKNExjb2tSbE0
If you want the zip I created send me a PM I'll send the link, I'm pretty sure I know what happened but then again I could be wrong. I might just try to get v8 alpha for Mi5 and port it using stock mtc19x...
I have flashed both worst thing that happened was my phone got encrypted again but simple fix.
**BUT SERIOUSLY CANNOT EMPHASIZE THIS ENOUGH MAKE A BACKUP IN TWRP AND TO BE SAFE COPY IT TO YOUR PC**
Just to be clear I am not responsible for your device messing up in anyway, I am not a developer just followed instructions from another forum.
______
UPDATE:
Ported using Mi5 6.7.11_v8-6.0 ... good news is yes it flashes but still getting bootloop logcat shows LESS fatal/errors than my previous build but still not booting up fully... I'd be happy to share the zip with anyone who wants it again just PM me. Logcats will be available later gonna try to narrow it down myself... we will see how that goes.
I see many tutorials talking about how to compile a rom from source (with an already existing device tree, vendor tree etc), but how do you go about making a custom ROM (and TWRP) from scratch? I already have programming experience with quite some programming languages (including Java, which I heard is important for custom ROM dev), but I can't figure out looking at device trees why people do certain commits.
Oh and by the way, would the process be much different on a treble device? The device I want to build for (huawei P Smart) supports project Treble.
ahmed.al said:
Oh and by the way, would the process be much different on a treble device? The device I want to build for (huawei P Smart) supports project Treble.
Click to expand...
Click to collapse
Hi! If your phone supports "Treble", you can directly boot a GSI (Generic System Image) build of any custom ROM. Check "Phh-Treble". Treble means having /vendor partition outside of the traditional /system partition. Before /vendor used to be mounted by using /system/vendor. Good Luck!
What's the phone's kernel version currently? If the SoC is released before 2017 it would most probably be 3.18 or if it released after 2017 it must be 4.4+.
pvineeth97 said:
Hi! If your phone supports "Treble", you can directly boot a GSI (Generic System Image) build of any custom ROM. Check "Phh-Treble". Treble means having /vendor partition outside of the traditional /system partition. Before /vendor used to be mounted by using /system/vendor. Good Luck!
What's the phone's kernel version currently? If the SoC is released before 2017 it would most probably be 3.18 or if it released after 2017 it must be 4.4+.
Click to expand...
Click to collapse
I changed my mind. I think a Moto G6 (plus) would be a better buy. It's going to be released in 3 days (don't know if you can buy it right away). Anyway since it's so new it should be 4.4+
pvineeth97 said:
Hi! If your phone supports "Treble", you can directly boot a GSI (Generic System Image) build of any custom ROM. Check "Phh-Treble". Treble means having /vendor partition outside of the traditional /system partition. Before /vendor used to be mounted by using /system/vendor. Good Luck!
What's the phone's kernel version currently? If the SoC is released before 2017 it would most probably be 3.18 or if it released after 2017 it must be 4.4+.
Click to expand...
Click to collapse
This is not the case. The only reason those boot on those devices is because it was made to. There are things the users are not being told to get them behind this. Even though it will not do a lot for updates or anything else.
ahmed.al said:
I changed my mind. I think a Moto G6 (plus) would be a better buy. It's going to be released in 3 days (don't know if you can buy it right away). Anyway since it's so new it should be 4.4+
Click to expand...
Click to collapse
Check if the SoC is released in 2017. If SoC is released in 2017 or later then it should have Linux kernel 4.4+.
---------- Post added at 09:04 PM ---------- Previous post was at 08:59 PM ----------
zelendel said:
This is not the case. The only reason those boot on those devices is because it was made to. There are things the users are not being told to get them behind this. Even though it will not do a lot for updates or anything else.
Click to expand...
Click to collapse
Treble can guarantee at least 4 - 5 major updates for phones having it. Even if you don't get updates you can flash a GSI build of any custom ROM.
Problems come when implementing treble because it is not that easy to implement it. Even very old phones having msm8916 are getting treble support now unofficially using Phh-Treble.
pvineeth97 said:
Check if the SoC is released in 2017. If SoC is released in 2017 or later then it should have Linux kernel 4.4+.
---------- Post added at 09:04 PM ---------- Previous post was at 08:59 PM ----------
Treble can guarantee at least 4 - 5 major updates for phones having it. Even if you don't get updates you can flash a GSI build of any custom ROM.
Problems come when implementing treble because it is not that easy to implement it. Even very old phones having msm8916 are getting treble support now unofficially using Phh-Treble.
Click to expand...
Click to collapse
Is that what you think? You do know the only reason it is working right is is because of the available kernels out. Just because aosp has to load for the oem on say 9.0 that doesn't mean the oem has to release the kernel that allows aosp to boot.
I along with many of the devs have been following this closely. Notice how not many are really working on it outside of remote devices. Things like honor and Xiaomi.
Only time will tell how useful it is. To be honest I have not seen anything major. It is pretty much the same as last year. Sure there is one image for some devices but that means nothing. Custom rom devs all will have to make their own anyway. So not a big deal.
zelendel said:
Is that what you think? You do know the only reason it is working right is is because of the available kernels out. Just because aosp has to load for the oem on say 9.0 that doesn't mean the oem has to release the kernel that allows aosp to boot.
Click to expand...
Click to collapse
Correct me if I'm wrong, but aren't OEMs forced to release their kernel source? Since Android is licensed under the GPL.
ahmed.al said:
Correct me if I'm wrong, but aren't OEMs forced to release their kernel source? Since Android is licensed under the GPL.
Click to expand...
Click to collapse
Only for OS they ship out. If they, never release a build say aosp then they are not required to post it. There are many internal kernel builds that never see the light of day to users.
Again. Android is not licensed under the gpl. Only the kernel is. Android is under the apache license. Meaning they own all code. They use. The reason for no source for this gs like TouchWiz, sense or any of the other oem distros.
So in theory. The oem could easily pass by getting it to boot aosp in, house and never release the kernel they used.
zelendel said:
Only for OS they ship out. If they, never release a build say aosp then they are not required to post it. There are many internal kernel builds that never see the light of day to users.
Again. Android is not licensed under the gpl. Only the kernel is. Android is under the apache license. Meaning they own all code. They use. The reason for no source for this gs like TouchWiz, sense or any of the other oem distros.
So in theory. The oem could easily pass by getting it to boot aosp in, house and never release the kernel they used.
Click to expand...
Click to collapse
I see, thank you.
Anyway, I saw somewhere mentioned that little changes should be made to the GSI (if issues are present). Since this is much different from traditional porting (with a device, vendor and kernel tree), where should the changes be made? There are no docs or anything inside this repo.
ahmed.al said:
I see, thank you.
Anyway, I saw somewhere mentioned that little changes should be made to the GSI (if issues are present). Since this is much different from traditional porting (with a device, vendor and kernel tree), where should the changes be made? There are no docs or anything inside this repo.
Click to expand...
Click to collapse
I am not using his work so I am not sure. There are some that are doing it on our own.
zelendel said:
Only for OS they ship out. If they, never release a build say aosp then they are not required to post it. There are many internal kernel builds that never see the light of day to users.
Again. Android is not licensed under the gpl. Only the kernel is. Android is under the apache license. Meaning they own all code. They use. The reason for no source for this gs like TouchWiz, sense or any of the other oem distros.
So in theory. The oem could easily pass by getting it to boot aosp in, house and never release the kernel they used.
Click to expand...
Click to collapse
True that. Most of the Chinese companies don't release their kernel sources and it seems like FSF doesn't care much about it.
---------- Post added at 01:08 PM ---------- Previous post was at 01:04 PM ----------
ahmed.al said:
I see, thank you.
Anyway, I saw somewhere mentioned that little changes should be made to the GSI (if issues are present). Since this is much different from traditional porting (with a device, vendor and kernel tree), where should the changes be made? There are no docs or anything inside this repo.
Click to expand...
Click to collapse
There will never be a guide on it since it is not easy to write completely about porting Android in a guide and also it depends on hardware, OEM specific changes and upstreaming the kernel for newer Android version (OMG, I did this once yet I ended up having kernel build errors but afterwards I applied specific commits on top of Nougat kernel for OREO and it worked!).
Just 2 days back I built new Android 8.1 ROM for LG G4c and I will trebelize it in future,
https://forum.xda-developers.com/g4/development/rom-lineageos-15-1-t3768654
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pvineeth97 said:
There will never be a guide on it since it is not easy to write completely about porting Android in a guide and also it depends on hardware, OEM specific changes and upstreaming the kernel for newer Android version (OMG, I did this once yet I ended up having kernel build errors but afterwards I applied specific commits on top of Nougat kernel for OREO and it worked!).
Just 2 days back I built new Android 8.1 ROM for LG G4c and I will trebelize it in future
Click to expand...
Click to collapse
I stopped following your g4c custom ROMs, because I have replaced my phone with an iPhone 6s (temporary, cause IOS is gross). Anyway how in the world are you going to trebelize it? Trebilizing it would require changing partitions, which is a pretty dangerous thing to do.
ahmed.al said:
I stopped following your g4c custom ROMs, because I have replaced my phone with an iPhone 6s (temporary, cause IOS is gross). Anyway how in the world are you going to trebelize it? Trebilizing it would require changing partitions, which is a pretty dangerous thing to do.
Click to expand...
Click to collapse
@Anghirrim told me long back that you replaced your phone.
So I didn't bother about it much. I was just showing you that I could boot Oreo and next I will port P without treble on a msm8916 device.
I need not create any new partition. There are some patches that I need to apply for the kernel and use Oreo blobs of a known msm8916 device then I will proceed with other things I need to do. If I need to create one there is cust/ partition which is handy for storing vendor blobs. I am not planning on it yet. I will just merge newer patches for P and modify the device trees for newer Android versions.
pvineeth97 said:
@Anghirrim told me long back that you replaced your phone.
So I didn't bother about it much. I was just showing you that I could boot Oreo and next I will port P without treble on a msm8916 device.
I need not create any new partition. There are some patches that I need to apply for the kernel and use Oreo blobs of a known msm8916 device then I will proceed with other things I need to do. If I need to create one there is cust/ partition which is handy for storing vendor blobs. I am not planning on it yet. I will just merge newer patches for P and modify the device trees for newer Android versions.
Click to expand...
Click to collapse
Sounds nice and all, but shouldn't you rather focus more on make your ROMs actually usable? Last time I checked your g4c ROMs, they were full of bugs and there were very few things working.
ahmed.al said:
Sounds nice and all, but shouldn't you rather focus more on make your ROMs actually usable? Last time I checked your g4c ROMs, they were full of bugs and there were very few things working.
Click to expand...
Click to collapse
Ohh when did you check? You must be dreaming... Please check my threads before you speak... I already fixed everything in Nougat for G4c this March itself even the sound and camera. Now will complete LOS 15.1 before I go to USA in 3 months.
My latest LOS 14.1 builds for March/April which are very stable (already tested by Paul, DonOleq and Anighirrim). Even Anghirrim flashed my AEX ROM on his wife's G4c phone because he liked it a lot and it is very stable with SELinux Enforced. It's their daily driver now. It's your loss if you didnt check my latest builds.
On heavy usage of Nougat ROM on G4c some lags are encountered because of limited RAM - 1 GB and slower flash memory.
https://forum.xda-developers.com/g4/development/rom-lineageos-14-1-t3668489
pvineeth97 said:
Ohh when did you check? You must be dreaming... Please check my threads before you speak... I already fixed everything in Nougat for G4c this March itself even the sound and camera. Now will complete LOS 15.1 before I go to USA in 3 months.
You keep telling me right - "Check before you speak". Don't be a hypocrite.
https://forum.xda-developers.com/g4/development/rom-lineageos-14-1-t3668489
Click to expand...
Click to collapse
No need to be so mad lol. A simple "I've already fixed the bugs" would've been enough.
ahmed.al said:
No need to be so mad lol. A simple "I've already fixed the bugs" would've been enough.
Click to expand...
Click to collapse
Again check my post xD. I am not at all mad/angry lol.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
• Android OS version: 7.1.2
• For devices: S905X
• Recovery: TWRP
• Thread Made By: N'ayam Amarsh'e
__________________________________
FIX FOR A95X S905X WIFI:
Here is a fix:
- download and unzip this ap6330 folder
https://mega.nz/#!QAQ3mSBK!0ku...bWcw0xHXr2t9jYwtB8iYiHZo66begA
- use X-plore file manager app (with superuser+moutable system file option) copy all ap6330 folder to /etc/wifi/. Then reboot.
______________________________________
Attention:
I don't force you to use our(yeah, our, we are a team of 3) ROM. It's stable and can be used as daily driver.
If you don't like something, please ask me on how to remove/add it.
I am doing my best to provide you the best ATV Experience.
THIS ROM CAN BE FLASHED OVER 6.0 AS WELL.
Based on AndroidTV OS & AOSP. Has all the features of an Android TV + Extras.
please consider donating if you appreciate our hard work - https://paypal.me/atvXperience
ROM DEVELOPMENT, UX, UI : Me and Carmine Rovito(@Carmine)
WEBSITE, BRANDING, UX, UI: Taylor Stephen Hadden(@stephenh)
v2E onwards, Credit Goes to Minixfreak for his contributions towards atvX builds.
HOW TO FLASH IMG VERSION:
VIDEO TUTORIAL:
TEXT TUTORIAL:
1. Download ROM, the file must be a .rar, extract it with WinRAR, 7Zip or any other archive extractor. Now you'll get an IMG. Just rename the IMG to atvx so it now becomes atvx.img.
2. Download Amlogic Burn card maker http://www81.zippyshare.com/v/ZoilYyaS/file.html
3. Get an EMPTY SD Card
4. INSERT THE MEMORY CARD INTO YOUR COMPUTER WITH A USB CARD READER.
4. OPEN THE TOOL AND SELECT THE IMG ROM FILE. NOW SELECT THE SD CARD DRIVE.
5. SELECT *FORMAT* OPTION, DESELECT ERASE BOOTLOADER. NOW, LEAVE OTHER SETTINGS AS IS.
NOW CLICK ON (MAKE)
6. IT WILL TELL YOU TO FORMAT MEMORY CARD. FORMAT MEMORY CARD WITH FAT FILESYSTEM AND USE QUICK FORMAT.
7. IT WILL NOW FLASH THE ROM IN MEMORY CARD.
8. INSERT MEMORY CARD IN BOX.
9. USE A MATCHSTICK AND PUT IT IN THE AV PORT HOLE OF THE ROM.
10. NOW PUSH THE MATCHSTICK INSIDE THE HOLE TO PRESS THE BUTTON. KEEP IT PRESSED AND TURN ON THE POWER.
11. WAIT FOR 5 MINUTES TO FLASH.
12. ALL DATA WILL BE WIPED.
13. ENJOY!
HOW TO FLASH ZIP VERSION:
1. DOWNLOAD THIS http://www57.zippyshare.com/v/85eCS93k/file.html and put it into sdcard.
2. Download the rom and put it into sdcard.
3. Open Update&Backup App, Click on select and select TWRP311.zip, now hit UPDATE.
4. Now you'll be in TWRP. If you aren't, select Update from EXT and select sdcard, now again select TWRP311.zip
5. Now once in TWRP, Swipe if you get a warning.
6. [OPTIONAL] Go to Backup and select SYSTEM, DATA, LOGO, BOOT, RECOVERY and swipe to backup. Now go back to home.
7. Go to Wipe - Advance Wipe - Select Data, system, Dalvik cache and cache and Swipe to wipe.
8. Go back and select install. Now Click on select storage and select External sd card, ATVXperience zip file. Now, swipe to flash.
9. Once rom is flashed, select Reboot system.
10. Enjoy!
v2E
• Based on latest AndroidTV OS, made to be compatible with all S905XDevices.
• Leanback UI
• All Google Apps Work!
• Pre-installed with exclusive atvXperience apps!
• Recommendations work great! To turn off go to Settings - Home
• Chromecast Works
• Comes with latest AndroidTV OS.
• Latest Security Patches from Google and MANY MORE!!
• COMPATIBLE WITH ALL S905X DEVICES!!
Please consider donating if you appreciate our hardwork.
https://paypal.me/atvXperience
ROM OS Version: 7.1.2 Nougat
ROM Kernel: Linux 3.10.x
Based On: AOSP, AndroidTV
Version Information
Status: Stable
XDA:DevDB Information
[ROM][S905X]atvXperience : The Ultimate AndroidTV experience!, ROM for the Android Stick & Console Computers
Contributors
N'ayam Amarsh'e
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: A compatible Processor Type
Based On: atvXperience Project
Version Information
Status: Stable
Current Stable Version: v2F
Stable Release Date: 2018-09-10
Created 2018-09-05
Last Updated 2018-09-12
Reserved
so already posting donation links when no rom is available?
or is it you get "early access" if you pay forit?
either way, pretty sure place holder roms arent allowed but i could be wrong
elliwigy said:
so already posting donation links when no rom is available?
or is it you get "early access" if you pay forit?
either way, pretty sure place holder roms arent allowed but i could be wrong
Click to expand...
Click to collapse
Actually, the atvXperience project has already been released for s905w and I did something similar(coming soon thread) back then for it too. This thread acts as a deadline for me. I'll release the public release of the rom in 2 weeks and as usual, people who have donated to s905w know what my rom promises and will get the s905x version 5 days before the Joe Public release If mods have any problem with this thread, they can delete it without any problem
N'ayam Amarsh'e said:
Actually, the atvXperience project has already been released for s905w and I did something similar(coming soon thread) back then for it too. This thread acts as a deadline for me. I'll release the public release of the rom in 2 weeks and as usual, people who have donated to s905w know what my rom promises and will get the s905x version 5 days before the Joe Public release If mods have any problem with this thread, they can delete it without any problem
Click to expand...
Click to collapse
Hi,
is it for ANY S905x Box?? My Box have Android 6.0..is it Possible??
Thx
MarkyMan said:
Hi,
is it for ANY S905x Box?? My Box have Android 6.0..is it Possible??
Thx
Click to expand...
Click to collapse
Yes, universally for any s905x box. It will probably be Nougat but atvXperience v3 will be Oreo.
N'ayam Amarsh'e said:
Yes, universally for any s905x box. It will probably be Nougat but atvXperience v3 will be Oreo.
Click to expand...
Click to collapse
Sorry for Another Question.
So I can just install the Rom over it no preference which Android version I have ?? So whether 6.0 or 7.0 for example?
Probably Yes.
I'll release an IMG version first so it will overwrite the whole android system.
MarkyMan said:
Sorry for Another Question.
So I can just install the Rom over it no preference which Android version I have ?? So whether 6.0 or 7.0 for example?
Click to expand...
Click to collapse
N'ayam Amarsh'e said:
Probably Yes.
I'll release an IMG version first so it will overwrite the whole android system.
Click to expand...
Click to collapse
So I have to wait for the image or just go?
MarkyMan said:
So I have to wait for the image or just go?
Click to expand...
Click to collapse
You'll probably have to wait till I release the rom for s905x. If you have an s905w device, atvXperience is already available for download.
N'ayam Amarsh'e said:
You'll probably have to wait till I release the rom for s905x. If you have an s905w device, atvXperience is already available for download.
Click to expand...
Click to collapse
Ok, so i´m wait for my S905x Device. THX!!!
elliwigy said:
so already posting donation links when no rom is available?
or is it you get "early access" if you pay forit?
either way, pretty sure place holder roms arent allowed but i could be wrong
Click to expand...
Click to collapse
Down be so harsh, atleast he is posting the rom after properly testing it and NOT labelling it "(Testers Needed)".
There is also a flag button if you need it, either use it or make your way out of this thread.
Besides, Donation for early releases? sounds good to me, why shouldnt donators get early access? after all they are contributing to resources aswell as the future of this project.
Ricky Divjakovski said:
Down be so harsh, atleast he is posting the rom after properly testing it and NOT labelling it "(Testers Needed)".
There is also a flag button if you need it, either use it or make your way out of this thread.
Besides, Donation for early releases? sounds good to me, why shouldnt donators get early access? after all they are contributing to resources aswell as the future of this project.
Click to expand...
Click to collapse
Just going based off personal experience as I have seen people get warnings or banned for posting threads just like this one..
There is no readily available free version of his rom and links take users off xda with promise if they pay up they will get access to the rom before a public release is made
Wasjust giving a warning that he might have issues with this post from one dev to another but I suppose I can formally complain about the thread since you suggest that would be a better option.
Sent from my SM-G965U using Tapatalk
elliwigy said:
Just going based off personal experience as I have seen people get warnings or banned for posting threads just like this one..
There is no readily available free version of his rom and links take users off xda with promise if they pay up they will get access to the rom before a public release is made
Wasjust giving a warning that he might have issues with this post from one dev to another but I suppose I can formally complain about the thread since you suggest that would be a better option.
Sent from my SM-G965U using Tapatalk
Click to expand...
Click to collapse
atvXperience is a free firmware. The s905w chipsets already have it and I do redirect to our website but it's not virus or something lol. It already has 6k downloads and everybody having an s905w device has it.
Anyway, if you're so keen for a download link. I'll post a link of the unfinished rom.
elliwigy said:
Just going based off personal experience as I have seen people get warnings or banned for posting threads just like this one..
There is no readily available free version of his rom and links take users off xda with promise if they pay up they will get access to the rom before a public release is made
Wasjust giving a warning that he might have issues with this post from one dev to another but I suppose I can formally complain about the thread since you suggest that would be a better option.
Sent from my SM-G965U using Tapatalk
Click to expand...
Click to collapse
Well, you have done one great deed for the AMLogic community, zip version is up and available publicly!
Would be great to get a great dev like yourself around here, the amlogic community are dying for a decent ROM and tools to modify firmware, i assure you, AMLogic firmware is literally about 10x harder to work with than any other firmware and the only tools created to modify firmware are made by me
So if you get a device, feel free to jump onboard with some of my projects that noone else has been able to deliver to this date
N'ayam Amarsh'e said:
atvXperience is a free firmware. The s905w chipsets already have it and I do redirect to our website but it's not virus or something lol. It already has 6k downloads and everybody having an s905w device has it.
Anyway, if you're so keen for a download link. I'll post a link of the unfinished rom.
Click to expand...
Click to collapse
youre missing the point lol.. this thread is for the s905x, not s905w and a rom isnot available for the s905x.. but if you donate money, you will get "early access" with no publicly available alternative for s905x..
sort of click bait too when clicking a s905x thread link it takes you to a website offxda for another chipset?
This thread is basically a "place holder" thread and shouldnt be asking for donations until a public free version is available.
I was just tryna give you a tip as I have seen devs get warnings and/or banned posting threads just like this one but hey, last time i try to help someone out lol
carry on and ignore me lol
Ricky Divjakovski said:
Well, you have done one great deed for the AMLogic community, zip version is up and available publicly!
Would be great to get a great dev like yourself around here, the amlogic community are dying for a decent ROM and tools to modify firmware, i assure you, AMLogic firmware is literally about 10x harder to work with than any other firmware and the only tools created to modify firmware are made by me
So if you get a device, feel free to jump onboard with some of my projects that noone else has been able to deliver to this date
Click to expand...
Click to collapse
no biggie, i personally use the international version of the mibox3.. i mainly work with cell phones, not android tv boxes..
I have used your kitchens a while back but have since moved to other methods..
i was not questioning yours or anyone elses work by any means, was just giving a tip as I have been warned years ago for far less infractions, not a big deal lol i can just be ignored, wasnt trying to offend anyone
elliwigy said:
no biggie, i personally use the international version of the mibox3.. i mainly work with cell phones, not android tv boxes..
I have used your kitchens a while back but have since moved to other methods..
i was not questioning yours or anyone elses work by any means, was just giving a tip as I have been warned years ago for far less infractions, not a big deal lol i can just be ignored, wasnt trying to offend anyone
Click to expand...
Click to collapse
No problem, but the mods of this forum won't mind me posting a coming soon rom because I already have done the same for s905w. You can check out the first few posts on this forum where people were commenting "Waiting for this rom"
elliwigy said:
no biggie, i personally use the international version of the mibox3.. i mainly work with cell phones, not android tv boxes..
I have used your kitchens a while back but have since moved to other methods..
i was not questioning yours or anyone elses work by any means, was just giving a tip as I have been warned years ago for far less infractions, not a big deal lol i can just be ignored, wasnt trying to offend anyone
Click to expand...
Click to collapse
Well jump on board!
TV Boxes are much more fun.
I know your intentions are good you just came across rude in the first post!
The moderators around here will be happy your looking out for the forum.
Yeah my Kitchens are obsolete and useless now, Android is not what it was a few years back.
Ricky Divjakovski said:
Well jump on board!
TV Boxes are much more fun.
I know your intentions are good you just came across rude in the first post!
The moderators around here will be happy your looking out for the forum.
Yeah my Kitchens are obsolete and useless now, Android is not what it was a few years back.
Click to expand...
Click to collapse
agreed, ive actually moved more into exploits/security since SamPWND on the S8/S8+ and a pixel 2 xl somore so building from source these days..
i found an exploit for VZW tab s3 but reported it to Samsung as that device is not popularand it didnt seem to work on other samsung devices..
i am currently working on exploits for US variants of S9/S9+..
With that being said, root was easy on the mibox3 with userdebug firmware but with the way security is going with android was only able to use tethered root due to selinux needing to be manually set to permissive after each reboot..
i really dont use it for anything other than media.. the mibox3wasalso just updated to oreo so its nice.. plus i havent found a quality box outside of mibox3 or shield tv..
I used to buy and sell android tv boxes so ive tried a ton and the quality has been hit or miss for me..
one thing i can say for certain is for the international mibox3 having a locked bl sucks..
Sent from my SM-G965U using Tapatalk