ROMS for LG G2 mini. (Scarcity)

ROMS for LG G2 mini. (Scarcity) - LG G2 Mini

I've been thinking about the myriad of "old" gadgets that are alive thanks to the variety of ROMs available these days.
But a fact that intrigues me is why this device has very few ROMs available ... it really is something that draws the attention precisely because it has a good potential to receive them.

I have been around the G2 Mini forums since, pretty much, when the device was released. If you have a look at the oldest posts, some of them are mine.
In that time, I have seen many devs, at first trying to unlock the bootloader of the device, with Zaaap finally succeeding, by figuring out how the Russians at 4pda hacked the bootloader of the L90, and then he, and others, made some ROMs.
Since then, the only ROM dev that seems to still be working on our device is @mobiusm . Other that him, I still work on my kernel, with the help of @likeadracula . (However, he is very busy and I don't have any features to add, so there is little work done lately)
I don't know why there aren't any other devs, although, I believe it's because of the initial price (250-300 €) so no dev got it, and, even when the price dropped, it was already "old".
So, yeah, that's what I think.
P.S.: This is not a development thread, but a discussion. It belongs in G2 Mini General.
EDIT: Thread moved by mod.

For me, one developer who works on ROMs and one on Kernels, seems like a lot for a nearly 4 year old, non flagship device.
Also, having the newest Recovery & newest ROM which are worked out properly + a neat kernel with all the features you desire should not be taken for granted.
I am very grateful for all the development that has been done and will be done and I wouldn't know why I should get a new phone, 'cause this one works just fine, at least for me.

My surprise in relation to this fact is related that this device does not differ in anything from the L90 in terms of hardware, and the boot unblocking is the same, same procedures, so it is common to see roms for L90 and not for the G2m. This is something I'm surprised about. Obviously I am happy that there is still developer for this device, particularly the rom of my preference that is the LOS, did not abandon it, so 2..3 or more roms for it does not make as much difference since I just like to use the LOS on my devices, for the stability, performance and commitment of the team to all supported devices, however, is my view, other people have divergent thoughts.

Oshmar said:
My surprise in relation to this fact is related that this device does not differ in anything from the L90 in terms of hardware, and the boot unblocking is the same, same procedures, so it is common to see roms for L90 and not for the L90. G2m, this is something I'm surprised about. Obviously I am happy that there is still developer for this device, particularly the rom of my preference that is the LOS, did not abandon it, so 2..3 or more roms for it does not make as much difference since I just like to use the LOS on my devices, for the stability, performance and commitment of the team to all supported devices, however, is my view, other people have divergent thoughts.
Click to expand...
Click to collapse
Actually, precisely because of the similar hardware, it's very easy for the L90 ROMs to be ported to the G2M.
One the devs that have made ROMs for the g2m recently told me that he is using the L90 for initial testing and then uses the blobs for the g2m to make it work. (I don't actually know, but I think that the only problem with the L90 blobs is the camera or the WiFi, if anything)
In fact, it's so easy that anyone, with the most basic knowledge of Linux, can get it to work. I think. I haven't actually tried.
So, find a ROM of the L90 that you like and give it a shot. Just follow an online tutorial and you should be able to port it.
If you need any help, just let me know. Or anyone on the forum (though, some, myself included, are busy)

I was thinking once before to try Slim Rom from l90, but I was afraid to ruin my phone

Boki11111 said:
I was thinking once before to try Slim Rom from l90, but I was afraid to ruin my phone
Click to expand...
Click to collapse
Just make a backup in recovery
If it works, let us know!
I might even make a small zip that modifies the build props to say the correct information.
P.S.: As always, I take no responsibility. Your phone, your fault. (Disclaimer)

Vagelis1608 said:
Just make a backup in recovery
If it works, let us know!
I might even make a small zip that modifies the build props to say the correct information.
P.S.: As always, I take no responsibility. Your phone, your fault. (Disclaimer)
Click to expand...
Click to collapse
If I try, I'll report

Complicated ... but as I said, it was only a sudden surprise because there were few roms, however, for my daily use, LOS I like, of course some options are always welcome, but if it is not possible, good size too.

Vagelis1608 said:
Just make a backup in recovery
If it works, let us know!
I might even make a small zip that modifies the build props to say the correct information.
P.S.: As always, I take no responsibility. Your phone, your fault. (Disclaimer)
Click to expand...
Click to collapse
not working,error in start installing zip,probably should first edit build.prop and kernel

Boki11111 said:
not working,error in start installing zip,probably should first edit build.prop and kernel
Click to expand...
Click to collapse
In the install script in the zip, there is a command "assert" that checks the device.
Remove that line and it will install.

I would like your opinion if it is worth changing my devices; Moto G Falcon and the LG D618, both in perfect condition, for a Moto G4 Play?

Oshmar said:
I would like your opinion if it is worth changing my devices; Moto G Falcon and the LG D618, both in perfect condition, for a Moto G4 Play?
Click to expand...
Click to collapse
Do you know in which parts the G Falcon and the G4 Play differ?

Is it possible for g2m to die if you try to install a rom of the L90?

Oshmar said:
Is it possible for g2m to die if you try to install a rom of the L90?
Click to expand...
Click to collapse
Nope. Only soft brick (a.k.a. bootloop)
Just restore the backup you (hopefully) made before flashing
Or, wipe /system /data and /cache and then flash a ROM for the g2m.
Still, no responsibility taken

They released an unofficial version of the android Oreo for the L90.

Related

D803 Rom "porting" requests, please write them here!

Mods, if this is in the wrong section, please move it.
*sorry for the bad english*
Alright, the purpose of this thread is simple. I made this with the intention of uniting all of the d803 users, and give them the opportunity to post a request for a rom they would like to see on their d803's that is available for other variants such as the d802. At the moment, I've found a way to "port" only d802 roms to the d803, and by port I mean making some slight changes that allow the rom to boot in our devices without any or with the least issues possible. These two devices are very similar hardware-wise, so software wise it doesnt change much.
If there's any D802 rom that you would like to see on our D803, feel free to leave a reply and I will do my best to move my gears and upload it so you guys can have it! As we all know, the development scene for the Canadian variant isnt as active as the d801 or D802, and with this I aim to end that barrier by trying to make those roms available to our device
Too long didnt read version:
If the rom exists for the D802, post a reply and I will try to make it available for the D803
Disclaimer:
I am in no way a developer, I simply edit files and put them in the right place so it boots for us. I do this to help fellow d803 users.
If I helped with a file, always make a nandroid backup just in case things go haywire. Anything that happens to your phone is your responsibility.
Everything I submit gets tested rigorously on my own G2 before being posted to ensure its working, but we all get different results, so the experience might vary. Just a heads up.
Click to expand...
Click to collapse
Any suggestions or edits by mods to the post are welcome.

[email protected] said:
Mods, if this is in the wrong section, please move it.
*sorry for the bad english*
Alright, the purpose of this thread is simple. I made this with the intention of uniting all of the d803 users, and give them the opportunity to post a request for a rom they would like to see on their d803's that is available for other variants such as the d802. At the moment, I've found a way to "port" only d802 roms to the d803, and by port I mean making some slight changes that allow the rom to boot in our devices without any or with the least issues possible. These two devices are very similar hardware-wise, so software wise it doesnt change much.
If there's any D802 rom that you would like to see on our D803, feel free to leave a reply and I will do my best to move my gears and upload it so you guys can have it! As we all know, the development scene for the Canadian variant isnt as active as the d801 or D802, and with this I aim to end that barrier by trying to make those roms available to our device
Too long didnt read version:
If the rom exists for the D802, post a reply and I will try to make it available for the D803
Disclaimer:
Any suggestions or edits by mods to the post are welcome.
Click to expand...
Click to collapse
To port any ROM to any version just download your devices patch from dr87's Mahdi ROM thread then all u gotta do is change out the boot IMG, a few lines in the build prop n updater script then flash ROM, gapps, the patch then your good. We had a similar patch for toro on the gnex forum and I was waiting for the day someone put one together for us seeing as all g2's use the same mainboard. The days of worrying about whether your variant will get support is finally over, for aosp Roms at least. I'm gonna try doing it w a stock ROM to see if that works cuz that's something I'd really love to see. Cuz as a vs980 owner I can say from experience that our stock ROM development is lacking compared to the d802 or f320

blazewit said:
To port any ROM to any version just download your devices patch from dr87's Mahdi ROM thread then all u gotta do is change out the boot IMG, a few lines in the build prop n updater script then flash ROM, gapps, the patch then your good. We had a similar patch for toro on the gnex forum and I was waiting for the day someone put one together for us seeing as all g2's use the same mainboard. The days of worrying about whether your variant will get support is finally over, for aosp Roms at least. I'm gonna try doing it w a stock ROM to see if that works cuz that's something I'd really love to see. Cuz as a vs980 owner I can say from experience that our stock ROM development is lacking compared to the d802 or f320
Click to expand...
Click to collapse
Well I meant it more in a way for those who don't understand much about editing the updater script and exchanging the boot.IMG. with what I'm offering all they have to do is ask the ROM and I'll post it online with said changes in case they don't know how to do it. Something like a small favor for everyone, but thanks for the reply!

Request
If you could please port this rom I would very much appreciate it
http://forum.xda-developers.com/showthread.php?t=2609355
---------- Post added at 08:48 AM ---------- Previous post was at 08:38 AM ----------
blazewit said:
To port any ROM to any version just download your devices patch from dr87's Mahdi ROM thread then all u gotta do is change out the boot IMG, a few lines in the build prop n updater script then flash ROM, gapps, the patch then your good. We had a similar patch for toro on the gnex forum and I was waiting for the day someone put one together for us seeing as all g2's use the same mainboard. The days of worrying about whether your variant will get support is finally over, for aosp Roms at least. I'm gonna try doing it w a stock ROM to see if that works cuz that's something I'd really love to see. Cuz as a vs980 owner I can say from experience that our stock ROM development is lacking compared to the d802 or f320
Click to expand...
Click to collapse
Could you possibly make a quick tutorial on how to do this? or possibly direct me to where i could find one?

Hi, I was looking at your old thread about how you could port d802 roms to d803. I was wondering if you could port cyanogenmod 11 snapshot m12. http://download.cyanogenmod.org/?device=d802 i would really appreciate it. and it seems like u are good at what u do so you should maybe consider building for d803 for cyanogenmod. thousands of d803 users have been waiting for cyanogenmod support but to this day have recieved none. anyways if u could port it i would really appreciate it! thanks!

can you make lollippop rom pls
http://forum.xda-developers.com/lg-g2/development/rom-android-lollipop-fast-clean-t2941922

CM12 !
PLZ !

Looking for an Alpha Lollipop build for the G2? Look no further!

"The G2 Dream Team" (and they well deserve that name) has released not one, but TWO lollipop builds for the LG G2. Both ROMs are based on the same build tree, but one ROM is CM12 and the other is a LiquidSmooth 4.0 ROM. Despite being built from the same build tree, they carry different features. They are stable and usable for daily drivers, but they may carry some bugs, like a non-functional video playback, NFC issues for LS/VS980 but it should all be sorted out in the near future. Head over to the threads to read more!:
Liquidsmooth 4.0:
http://forum.xda-developers.com/lg-g2/development/rom-liquidsmooth-v4-0-lg-g2-t2948395
CM12:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269
Older posts:
An increasing amount of devices have been receiving unofficial Android Lollipop 5.0 ports, like the HTC One M8 and the LG Optimus L9. Today another device can be added to the list of phones receiving a treatment with the taste of Android Lollipop, the LG G2. While there generally has been a wide contribution from the community; testing, sharing files and giving ideas, two XDA members stood out in particular in order to create the build, @ylukasy and @InfinitusDesigner. The port is still in a very early pre-alpha stage, and the bugs are barely known yet, but the ROM boots and has even been rooted! While it might be wisest to wait until an official thread has been made before grabbing your devices and start flashing, @ylukasy has already provided a download link for the ROM, and calls for people to help discover the bugs so that they can be eliminated. Please notice that the ROM might not be stable enough to be used as a daily driver, but owners of a LG G2 are officially an important step closer to having a stable Lollipop ROM!
If this post caught your interest and you're willing to take the risk, head over to the last pages in the following thread: http://forum.xda-developers.com/lg-g2/general/unofficial-cm12-nexus-5-posted-t2936398
As previously mentioned, a lot of things are not sorted out yet, and the build might not be for your device number, so make sure you read the entire thread before continuing, or simply wait untill an official thread is made.
Update:
An official thread has been posted and it can be found by following this link: http://forum.xda-developers.com/lg-g2/development/rom-android-lollipop-fast-clean-t2941922
The build is a port of the Nexus 5 ROM, and users of the ROM have been saying that the rom is very fast and fluid, calls work, camera works (although the quality is inferior), but other users have been reporting random reboots and incompatibilities with certain apps such as YouTube or WhatsApp.
by vPro97
This post will be updated regularly when new information regarding Lollipop ports surface.

Fantastic News! Will get round to trying it shortly, thanks for the link!

While I have my doubts about it being functional (or even booting) on my LS980, I'll give it a shot and see what happens.
Nice to see things moving at breakneck speeds these days.
On a side note, I just read the AnandTech review of the Nexus 6 and am happy to report that my well over a year old G2 beats it in several benchmarks so I'm pretty satisfied at the moment, especially considering I got it for free. I mean really...

In before "no build for xxxx?!?!?!?"

Anyone know how to port a d802 rom to d800?

Ready to try it out and see what happened..??

his build is from the same source the other was he doesn't deserve credit for it. it's using cm12 kernel and dev claims it's using nexus 5 port yet requires gapps and no signs of any nexus 5 code at all.

Wouldn't it be alot easier to just post the download link here?
₪LG G2₪

Zyner said:
Wouldn't it be alot easier to just post the download link here?
₪LG G2₪
Click to expand...
Click to collapse
It's not my work, and there are some steps which must be followed in order to make it work. I am just objectively informing any news regarding Android Lollipop for the LG G2.
OP has been updated.

The download link was removed before i could get the v3 version so im stuck with v2 and ive been using it as my daily (yeah it reboots every 5 minuets and i can leave wifi on or it will bootloop) But honestly thats the fun in testing this stuff out

MrNegative370 said:
The download link was removed before i could get the v3 version so im stuck with v2 and ive been using it as my daily (yeah it reboots every 5 minuets and i can leave wifi on or it will bootloop) But honestly thats the fun in testing this stuff out
Click to expand...
Click to collapse
Me too.
Is there anyone that can share privately the V3 version with me ? :fingers-crossed:

here is something better:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269

Jam4l said:
here is something better:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269
Click to expand...
Click to collapse
TY !

Can anyone port the Nexus 5 ROM?

Updating this thread later today if nothing gets in the way.

Hi everybody!!
I need a tester please:
I built pure AOSP for the D802 from sources of Android right now, has anybody time to test it?
It is an experimental build and I didn't test it right now, so I don't know if it is working, please make a backup from your current rom.
The build comes with an built in CWM recovery and should be with root access. It can be flashed with the same instructions like the CM 12 build.
Edit: Bootloop right now ... Anybody, can you take a logcat?
http://builds.hubdroid.com/otherroms/aosp_d802-ota-102.zip
Thank you in advance!! Please anybody who tries it: can you send me a pm?

Flo0008 said:
Hi everybody!!
I need a tester please:
I built pure AOSP for the D802 from sources of Android right now, has anybody time to test it?
It is an experimental build and I didn't test it right now, so I don't know if it is working, please make a backup from your current rom.
The build comes with an built in CWM recovery and should be with root access. It can be flashed with the same instructions like the CM 12 build.
http://builds.hubdroid.com/otherroms/aosp_d802-ota-102.zip
Thank you in advance!! Please anybody who tries it: can you send me a pm?
Click to expand...
Click to collapse
I'd love to test this for you, but I'm on Sprint LS980 Would you mind making a build for us?

iamterence said:
I'd love to test this for you, but I'm on Sprint LS980 Would you mind making a build for us?
Click to expand...
Click to collapse
Yes sure, but right now, I have to solve the bug, that the d802 wouldnt boot, so this may take some more time until I build it for other devices too.
Regards

[DISCUSSION]Cyanogenmod 12 for LG L3 II(E430), what do we have, and what do we need?

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

Question Successfully rooted Metro Pcs variant w/ Magisk and stock rom

Ive been rooting and tinkering with various different android phones for years now . Motorola has always been my favourite when it comes to rooting . Now my question is now what? I would love to finally pitch in on development starting with this device seeing as there is very little on this one as far as custom roms and what not. This device reminds me of the G7 Power with the A/B format. I was looking in on possibly bringing Ubuntu Touch to this device and as far as i can tell I just would need to make a halium kernal for it . Can someone maybe help me or tell me how incan possibly help on makimg that happen? Please bare with me . This is my very first time posting on this website . Im very savy when it comes to the android, ios and computers in general , Im running the stock rom and have done very little besides install some root apps. I would love to help out with any kind of development so please someone let me know . Ill be regularly checking my notifications and messages . Cheers!

I'm not a programmer, but I'd love to have LineageOS on my device. I haven't had the opportunity to play with Ubuntu Touch, but I assume that the F-droid store alone surpasses the app development for the Ubuntu Touch. Have fun!

Im suprised more people arent all over this device like when the G7 came out ....this device is awesome and the battery life alone is enough reason to want to buy it ...Guanma FTW!!

majormolineoux said:
I'm not a programmer, but I'd love to have LineageOS on my device. I haven't had the opportunity to play with Ubuntu Touch, but I assume that the F-droid store alone surpasses the app development for the Ubuntu Touch. Have fun!
Click to expand...
Click to collapse
What i found appealing about Ubuntu Touch is i recently read that you can now run android apps on it and i totally agree Lineage would be awesome and an obvious first step to take with this device now that we know it can be rooted...also TWRP development is a must

So far I'm really happy with it. The only thing is with how big it is, people with smaller/weaker hands are going to have a tough time. Good to know about Ubuntu Touch supporting android apps!

I too just got a G Play (2021), after spending the past 8 yrs. with my beloved HTC Ones (m7,m9). Ironically, it was Motorola that I left for HTC. I've been somewhat impressed with this phone's performance in stock bloat (I mean stock TRIM). I came in here today not expecting to see much, if anything, on this phone; but I've found enough info to get me started.
TY XDA, for all your hard work.

xXmazingmeloXx said:
Ive been rooting and tinkering with various different android phones for years now . Motorola has always been my favourite when it comes to rooting . Now my question is now what? I would love to finally pitch in on development starting with this device seeing as there is very little on this one as far as custom roms and what not. This device reminds me of the G7 Power with the A/B format. I was looking in on possibly bringing Ubuntu Touch to this device and as far as i can tell I just would need to make a halium kernal for it . Can someone maybe help me or tell me how incan possibly help on makimg that happen? Please bare with me . This is my very first time posting on this website . Im very savy when it comes to the android, ios and computers in general , Im running the stock rom and have done very little besides install some root apps. I would love to help out with any kind of development so please someone let me know . Ill be regularly checking my notifications and messages . Cheers!
Click to expand...
Click to collapse
How did you install magisk did you find a unofficial twrp or something?

TypicalGellert said:
How did you install magisk did you find a unofficial twrp or something?
Click to expand...
Click to collapse
I believe the OP use followed this guide.
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com

Null

Unofficial twrp ftw!
If you want an installable recovery, use this: https://forum.xda-developers.com/t/...st-port-but-everything-works-amazing.4330775/

dwycoff2013 said:
Unofficial twrp ftw!
If you want an installable recovery, use this: https://forum.xda-developers.com/t/...st-port-but-everything-works-amazing.4330775/
Click to expand...
Click to collapse
I have a new Moto G Stylus Metro. Anything for this yet?

Question Looking for a little general direction

I picked up one of these bad boys on a pretty deep discount to use as a dedicated retro gaming device. I’m interesting in tinkering a bit and am wondering if anyone has any thoughts or suggestions on a good rom choice for my use case ? I’ve already gotten my unlock code and I’m pretty much ready to go at this point !

Most people say CorvusOS and EvolutionX are good gaming ROMs, they both seem to be fast. Some people talk about some sort of ROG gaming rom, though ive never heard of it, or tried it.

But, uhm... upon looking at this devices page.. there aren't ANY custom roms available for your device.

Wow really? That's unfortunate.

Is there any point to Unlocking and installing TWRP / Rooting my device then?

bdizzo2l7 said:
Is there any point to Unlocking and installing TWRP / Rooting my device then?
Click to expand...
Click to collapse
I fiundbthat this is a device good for being your experimental toy-around gadget for tweaks and other such root related changes fun to play around with what you can do but from what I know so uncommonly rooted or used by devs that have any influence on the releases of these roms to really give you the full experience of having a rooted device.

bdizzo2l7 said:
Is there any point to Unlocking and installing TWRP / Rooting my device then?
Click to expand...
Click to collapse
You can root it for kernel optimisations and debloating, while also giving you more customisation control over your device.

TWRP is available, so rooting should be possible with magisk.
There's also this thread:
Flash RETUS Android 11 now that its available 12/10/2021
Hi again I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE! (if you do it right I doubt you will but just in case) BACK UP YOUR STUFF JUST IN CASE BEFORE YOU DO THIS AS YOU WILL WIPE YOUR USERDATA! We now have access to RETUS Android 11! Download...
forum.xda-developers.com

Better Mobile App

welcome