Related
I'm not a developer and i've just arrived into the LG world with the new LG L4-II, a slightly smaller and cheaper version of the L5-II, but with exactly the same base hardware.
I have already rooted it using the tutorial here, available for the L5-II, but i've yet to see any ROM development for this new line of devices, so i decided to share a link with the community that shows that the full Source Code for these devices has already been released by LG.
I hope it will be useful for the developers, so that some day in the near future we see some custom Roms for these new devices.
https://www.lg.com/global/support/o...tegoryId=CAT00000001&osCategoryId=CAT00000002
Cheers to all.
Thank you about the link and the information. I do hope someone takes the second generation ( II ) of the L models seriously. Almost no one is working which makes most of us sad
Could you be so kind to give me a link to the rooting tutorial? And may be the steps you've followed? Because I want to root my phone too.
Thanks and cheers to all guys who share useful info and modded roms with us!
thanks for this man. it helps a lot
BL unlock needed!
This is kind of useless, untill we get bootloader unlock. I've managed to build recovery.img for MT6575 chipset with some tools and also flashed it to E440, but bootloader is blocking the recovery boot due to security reasons, but boots in normal mode(Android)... i can share recovery.img if someone need it.
Update: I have boot.img and bootloader image, too - everithing except /system and /data
Added: Ops... My bad. now I think it is kernel related security check, will take a look at the kernel source and try again. I'm not a DEV, just playing.
nasko_spasko said:
This is kind of useless, untill we get bootloader unlock. I've managed to build recovery.img for MT6575 chipset with some tools and also flashed it to E440, but bootloader is blocking the recovery boot due to security reasons, but boots in normal mode(Android)... i can share recovery.img if someone need it.
Update: I have boot.img and bootloader image, too - everithing except /system and /data
Added: Ops... My bad. now I think it is kernel related security check, will take a look at the kernel source and try again. I'm not a DEV, just playing.
Click to expand...
Click to collapse
you will be king if you get this right. I am wanting to unlock my bootloader for the l5 II as well. if you get this right please share with us the method of how you do it.
Thanks this is very helpful, I wanted to start development anyway
JBolho said:
I'm not a developer and i've just arrived into the LG world with the new LG L4-II, a slightly smaller and cheaper version of the L5-II, but with exactly the same base hardware.
I have already rooted it using the tutorial here, available for the L5-II, but i've yet to see any ROM development for this new line of devices, so i decided to share a link with the community that shows that the full Source Code for these devices has already been released by LG.
I hope it will be useful for the developers, so that some day in the near future we see some custom Roms for these new devices.
https://www.lg.com/global/support/o...tegoryId=CAT00000001&osCategoryId=CAT00000002
Cheers to all.
Click to expand...
Click to collapse
Thank You :good:
Hi all,
TWRP doesn't seem to be working on the Android N beta. Does anyone know how to build TWRP for Nougat on our device or if possible could someone point me in the right direction?
I would really like to get Google Assistant working and build prop editing seems to be the only way.
Regards
Lee
i`m already in contact with one dev from the honor 8 forum and testing twrp for nougat. at now it is booting but there are some things to fix before it is ready for release. i would stay away from it at now because you could not flash anything with it. i will tell him to start a thread here after the relevant fixes are done.
paratox said:
i`m already in contact with one dev from the honor 8 forum and testing twrp for nougat. at now it is booting but there are some things to fix before it is ready for release. i would stay away from it at now because you could not flash anything with it. i will tell him to start a thread here after the relevant fixes are done.
Click to expand...
Click to collapse
Thank you very much for all that you and your fellow dev are doing.
If he wouldn't mind starting a thread to keep us updated that would be brilliant.
I am willing to help where I can if needed.
Regards
This is awesome...thanks so much
Sent from my EVA-L19 using Tapatalk
Hello my P8 Lite 2017 brought me here and I started to download roms and try them. The problem is recently I've seen that haky86, one of the main dev of this forum started to close threads without finishing his works. That mean This rom for exemple is impossible to use for me. I reported it and he say he'll fix that and then he say "update canceled" and close the thread. Thanks ? I don't know if it's just me but we don't have AOSP for P8 Lite on 7.1 now.
So he have his reasons and I don't really want to heard what happened exactly in his life but what will happen to those ROM's ? Will someone revive them ?
I'm not really a active member as you can see so I'm not part of this community I just ask for news and future. Thanks.
as i see it, it all happened first with a dispute/argument in a development thread of haky 86 for Android P.. there was a member that posted a bad opinion to dil3mm4.dev then haky "quoted" and replied to it that dil3mm4.dev's rom wont flash on the phone.. dil3mm4.dev then replied to haky to stop talking ****, which I think was just a misunderstanding on his part and haky is the wrong person to reply that...
then "indirect" blaming happens, and I think haky just got tired of it and decided to stop/switch device and focus on other device since two developers are developing the same roms already... moderators cleaned the posts afterwards.
anyways, i think the cause why the rom wont flash is that haky's treble rom is based on European firmware while dil3mm4.dev's treble rom is probably based on Chinese firmware.. they have different system size partitions so errors are likely to occur when treble roms based on the other firmware is installed on the other one.
https://forum.xda-developers.com/showpost.php?p=76441127&postcount=96
https://forum.xda-developers.com/showpost.php?p=76446600&postcount=254
so i think it all started with misconduct, misunderstandings and quick outbursts of emotions, in my own opinion. maybe there's more in the story than just that? idk..
It's just because he wants to work on P8lite 2015. He already stated it in his Android Oreo Thread
---------- Post added at 04:24 PM ---------- Previous post was at 04:20 PM ----------
baπdit said:
It's just because he wants to work on P8lite 2015. He already stated it in his Android Oreo Thread
Click to expand...
Click to collapse
https://forum.xda-developers.com/p8...oid-source-project-oreo-t3767623/post76451158
HidingNemo420 said:
as i see it, it all happened first with a dispute/argument in a development thread of haky 86 for Android P.. there was a member that posted a bad opinion to dil3mm4.dev then haky "quoted" and replied to it that dil3mm4.dev's rom wont flash on the phone.. dil3mm4.dev then replied to haky to stop talking ****, which I think was just a misunderstanding on his part and haky is the wrong person to reply that...
then "indirect" blaming happens, and I think haky just got tired of it and decided to stop/switch device and focus on other device since two developers are developing the same roms already... moderators cleaned the posts afterwards.
Click to expand...
Click to collapse
Oh, this happened? I've been inactive for a while. Sad to see it end like this, nothing to do about it now.
Why is dil3mm4.dev account currently disabled?
Edit: I hope it's only temporary. Can't have no developers, developing on the device. Even Android P development has been stopped and haky 86's files for P8 Lite 2017, have been deleted. I'm greeted with a 404 - Page Not Found.
HidingNemo420 said:
as i see it, it all happened first with a dispute/argument in a development thread of haky 86 for Android P.. there was a member that posted a bad opinion to dil3mm4.dev then haky "quoted" and replied to it that dil3mm4.dev's rom wont flash on the phone.. dil3mm4.dev then replied to haky to stop talking ****, which I think was just a misunderstanding on his part and haky is the wrong person to reply that...
then "indirect" blaming happens, and I think haky just got tired of it and decided to stop/switch device and focus on other device since two developers are developing the same roms already... moderators cleaned the posts afterwards.
anyways, i think the cause why the rom wont flash is that haky's treble rom is based on European firmware while dil3mm4.dev's treble rom is probably based on Chinese firmware.. they have different system size partitions so errors are likely to occur when treble roms based on the other firmware is installed on the other one.
https://forum.xda-developers.com/showpost.php?p=76441127&postcount=96
https://forum.xda-developers.com/showpost.php?p=76446600&postcount=254
so i think it all started with misconduct, misunderstandings and quick outbursts of emotions, in my own opinion. maybe there's more in the story than just that? idk..
Click to expand...
Click to collapse
Wtf how old they are ? 15 ? He give me the impression that he just think about himself, developing only while he have this device and asking for donations several times in a small signature on forums... So now all the P8 users are stuck with unfinished work and misundersting, and they talk about incompetence...
So anyway for now I just need to make the AOSP rom work with my device. How can I do that ? Since it's a know problem (error 7) and the solution (remove assert) doesn't work for me. I'm just doing something dumb for sure, I posted the screenshot of the file and he closed the thread, not giving a **** of my message which is certainly easy for him to answer...
If nobody can't really answer It's ok, I'll install official roms anyway... I think we can't really trust ppl like that
What a joke, now we have no developers for P8 Lite 2017
I still don't understand why haky deleted all of his ROMs and TWRP, Now how am I going to flash the Oreo TWRP in case I need to backup something or install a Custom ROM?
Also, if anyone has any ROM or Recovery that was hosted by haky, I would suggest to post it here, it would help a lot of people
Here's haky TWRP 3.2.1 for EMUI 5 ROM in case anyone needs it https://dbr.ee/vSH6 (I don't have the Oreo EMUI 8 one unfortunately)
@HidingNemo420
So this thread is where it all happened? Android P was supposedly on the way, for our device.
I think there are posts missing or probably deleted by moderators, between Post#9 and with a sarcasm in Post#10.
CrimsonBloodfang said:
Why is dil3mm4.dev account currently disabled?
Edit: I hope it's only temporary. Can't have no developers, developing on the device. Even Android P development has been stopped and haky 86's files for P8 Lite 2017, have been deleted. I'm greeted with a 404 - Page Not Found.
Click to expand...
Click to collapse
idk if its temporary or not. as ive read that "account currently disabled" is same as banned but it would depend of the severity of the offence.. https://forum.xda-developers.com/showthread.php?t=620206
and he did break some rules https://forum.xda-developers.com/announcement.php?a=81
CrimsonBloodfang said:
@HidingNemo420
So this thread is where it all happened? Android P was supposedly on the way, for our device.
I think there are posts missing or probably deleted by moderators, between Post#9 and with a sarcasm in Post#10.
Click to expand...
Click to collapse
yep dats the one.. wut a waste huh??
---------- Post added at 03:42 PM ---------- Previous post was at 03:41 PM ----------
all we can do is wait for good news..
CrimsonBloodfang said:
Oh, this happened? I've been inactive for a while. Sad to see it end like this, nothing to do about it now.
Why is dil3mm4.dev account currently disabled?
Edit: I hope it's only temporary. Can't have no developers, developing on the device. Even Android P development has been stopped and haky 86's files for P8 Lite 2017, have been deleted. I'm greeted with a 404 - Page Not Found.
Click to expand...
Click to collapse
Good morning
Maybe dil3mm4 has disabled his xda account ?
Maybe it's time to leave Huawei...
omega_55_lul said:
What a joke, now we have no developers for P8 Lite 2017
I still don't understand why haky deleted all of his ROMs and TWRP, Now how am I going to flash the Oreo TWRP in case I need to backup something or install a Custom ROM?
Also, if anyone has any ROM or Recovery that was hosted by haky, I would suggest to post it here, it would help a lot of people
Here's haky TWRP 3.2.1 for EMUI 5 ROM in case anyone needs it https://dbr.ee/vSH6 (I don't have the Oreo EMUI 8 one unfortunately)
Click to expand...
Click to collapse
I'm looking for haky86's most recent copy of TWRP for EMUI 8. Anyone still got it? His link is down.
XDA XILFY said:
I'm looking for haky86's most recent copy of TWRP for EMUI 8. Anyone still got it? His link is down.
Click to expand...
Click to collapse
Like I previously said, I don't have it, however I would suggest using Askuccio's TWRP since it's better anyway (it's based on the latest version 3.2.3-0), I currently have that one installed and it works flawlessly with stock EMUI 8
Here's the link https://forum.xda-developers.com/p8.../recovery-twrp-3-2-3-0-huawei-hi6250-t3859959
omega_55_lul said:
Like I previously said, I don't have it, however I would suggest using Askuccio's TWRP since it's better anyway (it's based on the latest version 3.2.3-0), I currently have that one installed and it works flawlessly with stock EMUI 8
Here's the link https://forum.xda-developers.com/p8.../recovery-twrp-3-2-3-0-huawei-hi6250-t3859959
Click to expand...
Click to collapse
Sweet, thanks. Just got that one installed. Did everything work perfectly for you after that? I've been having loads of trouble installing ROMs and then getting the eRecovery to come back each time.
Have any ROMs worked out for you? Any notable ones? I really like Resurrection Remix but I gave that a go on different TWRPs and it gave me a bootloop (some treble ROM)
XDA XILFY said:
Sweet, thanks. Just got that one installed. Did everything work perfectly for you after that? I've been having loads of trouble installing ROMs and then getting the eRecovery to come back each time.
Have any ROMs worked out for you? Any notable ones? I really like Resurrection Remix but I gave that a go on different TWRPs and it gave me a bootloop (some treble ROM)
Click to expand...
Click to collapse
No idea, I never installed any custom ROMs so far
I'm really annoyed at the fact we still haven't have got an official twrp build. There are beta builds of course but has lots of bugs. A lot of users (including me) would really want a stable build ( I mean who wouldn't?)
It can be hard but it's been months...
Please ........
TWRP only bring out stable versions if anyone in their development team has this device. I have asked them this question ages ago on a different device and that is the answer a was given.
skooter32 said:
TWRP only bring out stable versions if anyone in their development team has this device. I have asked them this question ages ago on a different device and that is the answer a was given.
Click to expand...
Click to collapse
Thanks for clearing that up man. I don't think anyone in their team would buy a budget phone ?
Going through all close to stock roms for the N9 and thought I would try N960FXXS2ARL4 from the following thread, that was a mistake. And I would have posted this in the above thread to make people aware, but its been closed. -
- https://forum.xda-developers.com/ga.../n960f-fd-rom-devbase-modified-final-t3903293
I ended up going down this rabbit hold because the N960FXXS2ARL3 listed in the OP failed to flash, I thought nothing of this and as I have seen this issue with many other roms in the past and figured it was just a corrupt file. So I wiped and proceeded to flash an earlier version of Alexandr's DevBase (based on Android 8.x) and it was at this point I start seeing the no-entry icon in-place of the signal meter.
According to the OP in that thread N960FXXS2ARL4 is supposed to be the lastest Rom/Bootloader for Android 8.1 and I thought I was safe to flash this rom via TWRP, as I had been specifically avoiding upgrading to any stock Android 9.x rom's due to the known issue of not being able to downgrade to either stock or custom Android 8.x roms. So I flashed Android 9.0 version of Alexanders Devbase and sure enough the signal meter is back, indicated that N960FXXS2ARL4 bootloader/rom from the Da-Boss thread for want of a better word f***ed something. Because even flashing the pure stock rom based on N960FXXS2ARL4 that this handset(SM-N960F) came with when I bought it will not get the signal meter to come back.
Can someone confirm if N960FXXS2ARL4 bootloader allow's backwards flashing? if yes what could have possible happened that's causing my issue?
Ok so to my chargrin after searching through Alexandr repo on androidfiles I see he had a version on his own thread that was newer than the one in Da-Boss thread. So currently I am trying various rom's to see if there is even a nats chance I can get this device back to 8.1 compliant.
plz dont post in the rom development section. post in the Q n A or general discussion sections.
also plz search about bootlaoder downgrades and revision number and modems and firmware files.
ud have seen that once you are on a revision, you cant downgrade to a lower one. BL rev is usualy 5 th character starting from the right. both your firmwares you point to are on rev 2. just check in system/software info. to know. moreover CP aka baseband aka modem dont always play nice when they arent in sync with a particular rom/base.
try this,
wipe everything > > flash latest csg5 bootloader > flash rom > flash latest csg2 modem and reboot for the first boot.
it should work properly.
bober10113 said:
plz dont post in the rom development section. post in the Q n A or general discussion sections.
moreover CP aka baseband aka modem dont always play nice when they arent in sync with a particular rom/base.
Click to expand...
Click to collapse
I posted here because the thread with the ROM responsible for all my aggravation is in this section.
I didn't flash the modem to start with, just flashed the p.o.s. ROM from Da-Boss thread, which I can only assume tried to flash the bloody bootloader/modem which would be a feet in of itself as the flash in twrp failed. Also as I said previously this Note 9 came with N960FXXS2ARL4. Which is actually a newer version then the one in the Da-Boss thread, so flashing (or having the fail to flash) should not have caused the issue with the bootloader/modem it now has.
@mods, feel free to move this to another section, but can I request the download links in the Da-Boss thread be removed please -
As the thread is closed
It has been demonstrated here and in that thread that this ROM is badly broken.
moderndaycowboy said:
wipe everything > > flash latest csg5 bootloader > flash rom > flash latest csg2 modem and reboot for the first boot..
Click to expand...
Click to collapse
Read the OP fella, I specifically stated I do NOT want to go to Android 9.0
Unless your saying that CSG5 Modem/Bootloader allow downgrading? if so got evidence of this...
b1k3rdude said:
I posted here because the thread with the ROM responsible for all my aggravation is in this section.
I didn't flash the modem to start with, just flashed the p.o.s. ROM from Da-Boss thread, which I can only assume tried to flash the bloody modem which would be a feet in of itself as the installed failed. Also as I said this Note 9 came with N960FXXS2ARL4, an actually newer version then the one in the Da-Boss thread.
@mods, feel free to move this to another section, but can I request the download links in the Da-Boss thread be removed please -
As the thread is closed
It has been demonstrated here and in that thread that this ROM is badly broken.
Click to expand...
Click to collapse
btw which twrp version did you use to flash rom?
bober10113 said:
btw which twrp version did you use to flash rom?
Click to expand...
Click to collapse
3.2.3.0
b1k3rdude said:
Read the OP fella, I specifically stated I do NOT want to go to Android 9.0
Unless your saying that CSG5 Modem/Bootloader allow downgrading? if so got evidence of this...
Click to expand...
Click to collapse
I dont say you go for android 9.0 either.
if you dont flash latest bootloader and latest modem, you are unable to use android 8.1, I am using ASB1 oreo now.
you can downgrade BL and modem, but your modem wont work if you boot your ARL4.
thats why after rom is installed you have to flash latest modem for made it work.
I have reported the Da-BOSS thread requesting the download link be removed due to the rom being broken, so that other dont have to deal with the same aggravation I did.
moderndaycowboy said:
thats why after rom is installed you have to flash latest modem for made it work.
Click to expand...
Click to collapse
Ok, let me flash CSG5 as I haven't got anything to loose at this point.
moderndaycowboy said:
if you dont flash latest bootloader and latest modem, you are unable to use android 8.1, I am using ASB1 oreo now.
Click to expand...
Click to collapse
b1k3rdude said:
Ok, let me flash CSG5 (BL/Modem) as I haven't got anything to loose at this point.
Click to expand...
Click to collapse
The above suggestions/advice and resulted in a softbrick, where the phone would not boot. So now I am having to do what I didn't want to do and upgrade all the way to Android 9.0 just to get a working phone. To say I am unimpressed at this point is an understatement.
And to add insult to injury, I now no longer have the OEM unlock option in the dev options, for which there is no current work around.... happy ***ing days.
maybe @Da-BOSS should come and see what you went through and explain why originally you had issues and tell if it has anything to do with him requesting the rom thread to be closed.(if it was a known issue why not edit out rom links to save users from the problems...transparency is key...)
this situation reminds me of the broken twrp 3.3.1 thread from arteuse) ive asked it to be closed or at least edited to warn users about the issue with parsing scripts while flashing zip but i was told that as xda users, we should be aware that flashing what ever we find here is at or own risk. even if many have pointed out issues, they won't censure nor close anything.(mod told me this) funny how comments and posts are censured and deleted every day for foul language though....double standard maybe?
The ROM is no longer maintained and no longer supported by me so any issues you are having it surely not my fault especially if the thread are already closed due to Alexndrs already have the latest Oreo version which is ASB1 so... there's no need for ARL4 to be supported by me after ASB1 got released... why the duplication?
Why would you use something that its thread are closed? Even at the first page of the thread.. it will tell you that [Thread Closed] at the first sight ! so... it is good that you reported about the link! I didn't know that! it was taking space on my cloud drives for nothing
Edit:-
Removed the file from my drive! To prevent any new accidents from new people on xda.
Da-BOSS said:
The ROM is no longer maintained and no longer supported by me so any issues you are having it surely not my fault especially if the thread are already closed due to Alexndrs already have the latest Oreo version which is ASB1 so... there's no need for ARL4 to be supported by me after ASB1 got released... why the duplication?
Why would you use something that its thread are closed? Even at the first page of the thread.. it will tell you that [Thread Closed] at the first sight ! so... it is good that you reported about the link! I didn't know that! it was taking space on my cloud drives for nothing and Removed the file from my drive! To prevent any new accidents from new people on xda.
Click to expand...
Click to collapse
I didn't say it was your fault in any of the thread's I have mentioned this specific issue, how ever in your thread a number of people mentioned having the same issue of the ROM not flashing correctly from twrp so imho you should/could have removed the link at that point. And I didn't know Alexandr's file repo was browseable untill after the fact, otherwise I would have never even looked at your thread.
Because I wanted de-bloated version of the rom already on the phone, grand atleast something good came of it and thank you for removing the link. I didnt think to email you directly about it mainly because the devs on this forum are on for the most part very busy individuals.
I gave up the fight with the Note9 in the end as I had to flash it to stock Android 9 which for me is a non-starter for the time being (no reliable xposed, so no Xprivacy), that and the CSG5 removes the OEM unlock option so no rooting and no twrp.
Da-BOSS said:
this situation reminds me of the broken twrp 3.3.1 thread from arteuse) ive asked it to be closed or at least edited to warn users about the issue with parsing scripts while flashing zip but i was told that as xda users, we should be aware that flashing what ever we find here is at or own risk. ?
Click to expand...
Click to collapse
learning from my exp. I would ask have you contacted the OP or reported the thread or was this a long time ago.
b1k3rdude said:
learning from my exp. I would ask have you contacted the OP or reported the thread or was this a long time ago.
Click to expand...
Click to collapse
its been reported many many many times. I've had pm and posted thread comments to the dev.
dev only made a rant reply about it and never modiyed his op. since many people have had the issue and what's deceiving is they each report the problem and blame the rom( multiple report on ambasadii and light rom threads) because they don't realize its not the rom but twrp that's not flashing correctly the rom. anyways i think it's time to ask an mod to move this thread via PM or something.
btw since ure on pie now. try ambasdii rom v5. its fully pack with features. the Rom Control is nice.
b1k3rdude said:
learning from my exp. I would ask have you contacted the OP or reported the thread or was this a long time ago.
Click to expand...
Click to collapse
Asked permission from Alexndr ROM=Yes , Reported the thread = yes, long time ago = Yes
Da-BOSS said:
yes, long time ago)
Click to expand...
Click to collapse
Sorry fella, didn't mean to sound condescending - I was referring to the twrp 3.3.1.0 thread.
bober10113 said:
blame the rom( multiple report on ambasadii and light rom threads) because they don't realize its not the rom but twrp that's not flashing correctly the rom. anyways i think it's time to ask an mod to move this thread via PM or something.
btw since ure on pie now. try ambasdii rom v5. its fully pack with features. the Rom Control is nice.
Click to expand...
Click to collapse
Ok we are getting a bit off topic here but @ XDA mods, WTF like! Anyway this rings a bell so I take it the current consensus is to avoid 3.3.1.0 on all devices and use the previous version for the time being?
Im not, I sold the Note9 today. Android 9 is a non-starter for the time being (no reliable xposed, so no Xprivacy), that and the CSG5 removes the OEM unlock option so no rooting and no twrp. May get a s10 or s10e once we have a working & reliable magisk, twep and xposed.