Related
See: https://forum.xda-developers.com/g4/development/lineageos-unofficial-builds-h815-t3726177
So, one can just flash this over the most recent official build, using e.g. TWRP? I mean, one doesn't have to wipe or anything like that?
Also, just curious, how much work was it getting from the last official to this, in terms of time spent "changing code"?
Wuddelchen said:
So, one can just flash this over the most recent official build, using e.g. TWRP? I mean, one doesn't have to wipe or anything like that?
Also, just curious, how much work was it getting from the last official to this, in terms of time spent "changing code"?
Click to expand...
Click to collapse
I think you can't flash this over the latest official build, because of the different signatures. I haven't tryed it, so I don't know, but I guess it won't work.
If you try it, write back if it works or not, so that other users know
I haven't changed the code of lineage, since it works so far without changes.
It is nearly vanilla lineage, just with updated:
- security patches
- features
- proprietary blobs
Bleuzen said:
I think you can't flash this over the latest official build, because of the different signatures. I haven't tryed it, so I don't know, but I guess it won't work.
If you try it, write back if it works or not, so that other users know
I haven't changed the code of lineage, since it works so far without changes.
It is nearly vanilla lineage, just with updated:
- security patches
- features
- proprietary blobs
Click to expand...
Click to collapse
Well, you can't flash over it, that much I can tell.
I just wonder how long the official build is gonna take, the phone is "new" (empty), but still, it takes time to set stuff up after a wipe...
Wuddelchen said:
Well, you can't flash over it, that much I can tell.
I just wonder how long the official build is gonna take, the phone is "new" (empty), but still, it takes time to set stuff up after a wipe...
Click to expand...
Click to collapse
Nobody knows. The bug exists since 2017-04-30, but nothing happens. And until the bug is not fixed, we don't get new official builds.
If you want to take the time to wipe and (re)setup your device is your decision.
But if you have the time, I would recommend it, mainly because of the security updates.
Do you know that I build unofficial? https://forum.xda-developers.com/g4/development/rom-lineage-os-14-1-lg-g4-t3704019
But we are now focused on Oreo. AOSCP is ready, I should have LOS 15 done in January. Do want to help us? We can add you to our telegram group.
tulen_kobi said:
Do you know that I build unofficial? https://forum.xda-developers.com/g4/development/rom-lineage-os-14-1-lg-g4-t3704019
But we are now focused on Oreo. AOSCP is ready, I should have LOS 15 done in January. Do want to help us? We can add you to our telegram group.
Click to expand...
Click to collapse
No, I didn't know that
Uh, there is work going on? This is great! I thought the device is dead, because nothing happens anymore on the LineageOS GitHub page for it. There is still no LOS 15.0 or 15.1 branch.
Great to her that there is still developing going on
Well, I help where I can. But I'm new to Android.
I have experience with Linux, use it every day, and now I know how to build LineageOS. I also can do Java programming.
But I never developed something with Android already. So I don't know how much I can help.
Bleuzen said:
I thought the device is dead, because nothing happens anymore on the LineageOS GitHub page for it. There is still no LOS 15.0 or 15.1 branch.
Click to expand...
Click to collapse
I'm pretty sure that LG has announced they will release an official Oreo build for the G4.
Perhaps the LOS people are waiting for that to happen so they can use some of their sources as a jumping-off point for LOS Oreo? I got the impression that happens in some cases but I'm not a dev so not clear on the specifics.
Exabyter said:
I'm pretty sure that LG has announced they will release an official Oreo build for the G4.
Perhaps the LOS people are waiting for that to happen so they can use some of their sources as a jumping-off point for LOS Oreo? I got the impression that happens in some cases but I'm not a dev so not clear on the specifics.
Click to expand...
Click to collapse
Where did you read this? I never read this somewhere and I don't think that there will ever be an official Oreo build for the G4.
They not even bring Nougat to all G4s, why they should work on Oreo for this old device?
I think from LGs side, the G4 is dead.
Bleuzen said:
Where did you read this? I never read this somewhere and I don't think that there will ever be an official Oreo build for the G4.
They not even bring Nougat to all G4s, why they should work on Oreo for this old device?
I think from LGs side, the G4 is dead.
Click to expand...
Click to collapse
Hmm, perhaps I confused it with one of the other devices I had been investigating as a possible future project. (Eg, the HTC 10, LG V20, Moto Z, etc)
Someone in the following thread claimed it would happen for the G4, but others disputed it and a quick web search tends to reinforce that:
https://forum.xda-developers.com/tmobile-g4/general/android-8-0-oreo-thread-h811-t3680209
On the other hand, I think these people have released an Oreo ROM for the G4:
https://forum.xda-developers.com/g4/development/g4-cypheros-t3680102
Exabyter said:
Hmm, perhaps I confused it with one of the other devices I had been investigating as a possible future project. (Eg, the HTC 10, LG V20, Moto Z, etc)
Someone in the following thread claimed it would happen for the G4, but others disputed it and a quick web search tends to reinforce that:
https://forum.xda-developers.com/tmobile-g4/general/android-8-0-oreo-thread-h811-t3680209
On the other hand, I think these people have released an Oreo ROM for the G4:
https://forum.xda-developers.com/g4/development/g4-cypheros-t3680102
Click to expand...
Click to collapse
Yep, looks good. I already tryed Oreo but it isn't complete already. But I'm looking forward to use and recommend it as new daily driver when it's ready
Hey everyone I just wanted to ask what this trebel label means, my lack of understanding and research tells me its kinda like OTA but for a more secure way to push updates to devices? being someone who has been using my device fine, am just a bit wonderous wondering what this Trebel means for my favorite ROM, Recovery and Kernel
dalebaxter01 said:
Hey everyone I just wanted to ask what this trebel label means, my lack of understanding and research tells me its kinda like OTA but for a more secure way to push updates to devices? being someone who has been using my device fine, am just a bit wonderous wondering what this Trebel means for my favorite ROM, Recovery and Kernel
Click to expand...
Click to collapse
for the moment, forget about it
it's very green and brings more troubles than solutions or any gain in particular. We will see how things develop with time.
You can read more about treble in here
https://www.xda-developers.com/how-project-treble-revolutionizes-custom-roms-android-oreo/
bornlivedie said:
for the moment, forget about it
it's very green and brings more troubles than solutions or any gain in particular. We will see how things develop with time.
You can read more about treble in here
https://www.xda-developers.com/how-project-treble-revolutionizes-custom-roms-android-oreo/
Click to expand...
Click to collapse
Reading the article I'm still a bit confused by what all this would mean for the end user, I really enjoy AEX since I moved from RR and it seems like this is the "latest and greatest" type of situation, yeah okay launches are tough but when everything smoothed out what would this treble allow us all to do?
dalebaxter01 said:
Reading the article I'm still a bit confused by what all this would mean for the end user, I really enjoy AEX since I moved from RR and it seems like this is the "latest and greatest" type of situation, yeah okay launches are tough but when everything smoothed out what would this treble allow us all to do?
Click to expand...
Click to collapse
In reality, it means little to the end user. It could theoretically mean that ROMS require less development time, since all roms in theory are based on a single image.
You can kinda of see this with Google's OEM Partners. At Google I/O they listed a number of partner OEMs that were the first to use treble and for the most part they have released upgrades quicker and more reliably then there non-treble counter parts. This also can be extended to the modding community and in general means that porting roms and developing them on a new phone should be easier.
This is all part of a bigger push by Google to gain uniformity across devices. They started requiring security updates in there SLA's and now are pushing treble.
Trebles's All the benifits goes to vendor and stock rom users Rights. As we are Custom Rom users what are the benefits we getting from Treble Projects?
https://www.androidpolice.com/2018/05/13/project-treble-impact-android-custom-rom-community/
alwynjoshy said:
Trebles's All the benifits goes to vendor and stock rom users Rights. As we are Custom Rom users what are the benefits we getting from Treble Projects?
Click to expand...
Click to collapse
In the future you will be able to flash the custom treble image specific for your hardware, and then a GSI (Generic System Image) of your choice: RR, AEX, DU, Tesla, etc... that will be generic and able to be flashed in any hardware. That means that GSI development teams will be able to maintain their roms and apply the security fixes without the need to create custom rom versions for each hardware. So, finally we will have real OTA updates for custom ROMs. We all hope LineageOS 16 to have more or less this philosophy too. Well see it in September.
So, benefits for the user:
More ROMs to choose for your device (actually all of them!!!)
More frequent upgrades from custom GSI teams.
Oki said:
In the future you will be able to flash the custom treble image specific for your hardware, and then a GSI (Generic System Image) of your choice: RR, AEX, DU, Tesla, etc... that will be generic and able to be flashed in any hardware. That means that GSI development teams will be able to maintain their roms and apply the security fixes without the need to create custom rom versions for each hardware. So, finally we will have real OTA updates for custom ROMs. We all hope LineageOS 16 to have more or less this philosophy too. Well see it in September.
So, benefits for the user:
More ROMs to choose for your device (actually all of them!!!)
More frequent upgrades from custom GSI teams.
Click to expand...
Click to collapse
thanks you well explained ?️.
I have question, If we flashed treble once, are we able to flash any treble based rom, for example any devices treble roms
alwynjoshy said:
thanks you well explained ?️.
I have question, If we flashed treble once, are we able to flash any treble based rom, for example any devices treble roms
Click to expand...
Click to collapse
Once you have the Treble framework in place and have then flashed a device specific vendor image you can from that point on flash any GSI ROM. The thing to note is that so far NFound's Treble ROMs have included vendor image files in them which makes them device specific, you need to check for and remove any vendor image files from Treble ROMs created for other devices if you wish to try the ROM on a device other than what it was made for.
alwynjoshy said:
thanks you well explained ?️.
I have question, If we flashed treble once, are we able to flash any treble based rom, for example any devices treble roms
Click to expand...
Click to collapse
A treble rom is hardware specific, so you cant flash a treble rom designed for a different device. Only GSIs are compatible with multiple devices, and it is this way since the hardware dependant part is only in the treble rom.
Right now there are not fully treble roms available for the Axon7. The currently available roms labeled as treble are delivered and work as a usual full rom. The treble and system parts are still mixed up in those roms. It will take some time until we could enjoy a fully wotking treble rom in the Axon7.
I'm currently using LOS 15.1 for my axon 7 but since it's not maintained anymore, I was wondering if there were any other ROMs that were being made or maintained for this device. Thanks in advance!
Im currently using stock A2017G B03 and move on with Huawei Mate 20x, i have been there done that with all known working GSI Roms and to be honest nothing feels as stable as stock especially when you need dolby atmos and banking apps, but if your device is not your primary device then you can try GSI Roms from Erfan or nFound.
Blankisblank said:
I'm currently using LOS 15.1 for my axon 7 but since it's not maintained anymore, I was wondering if there were any other ROMs that were being made or maintained for this device. Thanks in advance!
Click to expand...
Click to collapse
A lot of people have Treble'd their device and went with GSIs
I'm on LiquidRemix which seems to work nice with Speedy Vendor and Baddar Kernel
ibphantom said:
A lot of people have Treble'd their device and went with GSIs
I'm on LiquidRemix which seems to work nice with Speedy Vendor and Baddar Kernel
Click to expand...
Click to collapse
So I'm a bit confused, is LOS not made from a GSI? Or what's the difference between GSI's like LiquidRemix versus LOS?
Blankisblank said:
So I'm a bit confused, is LOS not made from a GSI? Or what's the difference between GSI's like LiquidRemix versus LOS?
Click to expand...
Click to collapse
When you Treble your device you split some partitions of your phone, particularly the vendor partition which opens the possibility of using ROMs from other phones. LOS offers a ROM version and GSI. The ROM versions are usually made just within the threads of the particular device. Some GSIs are broken, but that's because of a hardware mismatch but an updated vendor usually takes care of any mismatches. Each GSI/ROM has it's own custom set of features.
If you like LOS, you could try out the latest LOS16
But check out Havoc or LiquidRemix if you want to test GSIs
Keep in mind that we *may* have one official ROM supported for our phone. But GSIs are usually built monthly by a group of devs and they keep the security features up to date and make small changes like the AOSP public chain from Google.
ibphantom said:
When you Treble your device you split some partitions of your phone, particularly the vendor partition which opens the possibility of using ROMs from other phones. LOS offers a ROM version and GSI. The ROM versions are usually made just within the threads of the particular device. Some GSIs are broken, but that's because of a hardware mismatch but an updated vendor usually takes care of any mismatches. Each GSI/ROM has it's own custom set of features.
If you like LOS, you could try out the latest LOS16
But check out Havoc or LiquidRemix if you want to test GSIs
Keep in mind that we *may* have one official ROM supported for our phone. But GSIs are usually built monthly by a group of devs and they keep the security features up to date and make small changes like the AOSP public chain from Google.
Click to expand...
Click to collapse
So GSI's like LiquidRemix or Havoc are supported across multiple devices while ROM's are built more to match that specific device? Would that be correct? And we have a supported ROM still?
Blankisblank said:
So GSI's like LiquidRemix or Havoc are supported across multiple devices while ROM's are built more to match that specific device? Would that be correct? And we have a supported ROM still?
Click to expand...
Click to collapse
Yeah. GSIs are meant to be shared across devices with similar hardware and issues with a broken GSI are tweaked by having an updated Vendor file. ROMs are specifically made to match all the hardware in a particular model of phone. I think all the ROMs for the Axon 7 are unofficially supported at this point, which means a 3rd party dev decided to pull the source code of a popular ROM like Lineage and build it for our particular model just because they were feeling nice and appreciated by the people who use it.
ibphantom said:
When you Treble your device you split some partitions of your phone, particularly the vendor partition which opens the possibility of using ROMs from other phones. LOS offers a ROM version and GSI. The ROM versions are usually made just within the threads of the particular device. Some GSIs are broken, but that's because of a hardware mismatch but an updated vendor usually takes care of any mismatches. Each GSI/ROM has it's own custom set of features.
If you like LOS, you could try out the latest LOS16
But check out Havoc or LiquidRemix if you want to test GSIs
Keep in mind that we *may* have one official ROM supported for our phone. But GSIs are usually built monthly by a group of devs and they keep the security features up to date and make small changes like the AOSP public chain from Google.
Click to expand...
Click to collapse
ibphantom said:
Yeah. GSIs are meant to be shared across devices with similar hardware and issues with a broken GSI are tweaked by having an updated Vendor file. ROMs are specifically made to match all the hardware in a particular model of phone. I think all the ROMs for the Axon 7 are unofficially supported at this point, which means a 3rd party dev decided to pull the source code of a popular ROM like Lineage and build it for our particular model just because they were feeling nice and appreciated by the people who use it.
Click to expand...
Click to collapse
Okay so one last question, is there anything that you lose from moving to a GSI compared to a ROM? Like for example, would I still be able to use the superior audio DAC of the axon 7 or would that not be possible since that's too device specific? Thanks in advance!
Blankisblank said:
Okay so one last question, is there anything that you lose from moving to a GSI compared to a ROM? Like for example, would I still be able to use the superior audio DAC of the axon 7 or would that not be possible since that's too device specific? Thanks in advance!
Click to expand...
Click to collapse
Not that I know of. I'm able to use VoLTE and Viper4Android for the HD DAC and I'm on GSI.
Edit: And now that I remember, you should check out raystef66 ROMs. Those are still active for our phone and from an awesome dev.
Hi,
I have not yet done so, but I plan on installing e.foundation's OS to my Essential Phone. Before I start, I would like to ensure that I can reinstall or switch back to Android, in case I muck it up. Is there a way to backup the installed Android or switch back?
I've heard of Nandroid (https://forum.xda-developers.com/showthread.php?t=459830), but I'm not sure if it will do what I need (A full backup and restore over another ROM). For example, if on Linux, I could use "dd" to copy an entire partition, and write it back later.
Also, as I understand it from (https://mata.readthedocs.io/en/latest/), the phone contains two sets of partitions (slots). If I install the custom ROM to one slot, can I switch back to Android by executing the adb command to change the active slot?
Thanks in advance for help on this. I would very much like to avoid bricking my phone.
Cheers.
neXussT said:
Hi,
I have not yet done so, but I plan on installing e.foundation's OS to my Essential Phone. Before I start, I would like to ensure that I can reinstall or switch back to Android, in case I muck it up. Is there a way to backup the installed Android or switch back?
I've heard of Nandroid (https://forum.xda-developers.com/showthread.php?t=459830), but I'm not sure if it will do what I need (A full backup and restore over another ROM). For example, if on Linux, I could use "dd" to copy an entire partition, and write it back later.
Also, as I understand it from (https://mata.readthedocs.io/en/latest/), the phone contains two sets of partitions (slots). If I install the custom ROM to one slot, can I switch back to Android by executing the adb command to change the active slot?
Thanks in advance for help on this. I would very much like to avoid bricking my phone.
Cheers.
Click to expand...
Click to collapse
I would HIGHLY recommend not installing /e/
It is old... And unsupported.. and unless your tinfoil hat is itchy...
It's just LineageOS and MicroG...
rignfool said:
I would HIGHLY recommend not installing /e/
It is old... And unsupported.. and unless your tinfoil hat is itchy...
It's just LineageOS and MicroG...
Click to expand...
Click to collapse
It is not unsupported. It is not old (though it is Nougat). Constantly updated. Is more than just LineageOS and microG.
Do not spread FUD. Seriously.
@neXussT, I would suggest downloading the latest various stock ROMs, Pie, Oreo, Nougat, whichever or all. Have them at the ready on your PC/laptop. You could always fastboot flash the originals if things don't work out.
https://forum.xda-developers.com/showthread.php?t=3701681
[STOCK][DUMPS][FIRMWARE] Essential stock firmware and rom dumps
You'll have to downgrade to Nougat firmware first before trying /e/OS anyway so I doubt you can have Pie or Oreo on one slot and /e/OS on the other.
I have /e/OS on the Essential and Axon 7 (multiboot with other ROMs). Last update was about a day ago.
Essential PH-1, /e/OS 0.7-n ROM, microG (NoGapps), XDA Legacy
Thanks marcdw. Those are good tips. I would never have thought of a version difference causing issues. Cheers.
marcdw said:
It is not unsupported. It is not old (though it is Nougat). Constantly updated. Is more than just LineageOS and microG.
Do not spread FUD. Seriously.
@neXussT, I would suggest downloading the latest various stock ROMs, Pie, Oreo, Nougat, whichever or all. Have them at the ready on your PC/laptop. You could always fastboot flash the originals if things don't work out.
https://forum.xda-developers.com/showthread.php?t=3701681
[STOCK][DUMPS][FIRMWARE] Essential stock firmware and rom dumps
You'll have to downgrade to Nougat firmware first before trying /e/OS anyway so I doubt you can have Pie or Oreo on one slot and /e/OS on the other.
I have /e/OS on the Essential and Axon 7 (multiboot with other ROMs). Last update was about a day ago.
Essential PH-1, /e/OS 0.7-n ROM, microG (NoGapps), XDA Legacy
Click to expand...
Click to collapse
I see your definition of old (3 versions behind) is different than mine...
Also... Merging 2 year old security patches and updating that which even CAF has moved on from... Is what I would call unsupported...
Alrighty then.
I personally don't adhere to the notion that folks must run the latest and (not so) greatest because it's there. Let folks run what they want to run, be it old or new. Discouraging folks doesn't seem too cool. IMNSHO of course.
Moto G5s Plus XT1806, OmniROM 8.1.0, NanoDroid, MultiROM, XDA Legacy
I have the unofficial LOS 19.1 currently installed. Other than the lack of TWRP, I'm satisfied with it. But I see there are two other options available. official and crDroid. Is there any reason I should switch to one of those two? Are there differences in the recovery versions? If TWRP was available, I'd just make a backup of my current ROM and give the other two a try. But as it stands, getting back to my working current version isn't that simple.
Why do you have unofficial?
Wobbo-Q said:
Why do you have unofficial?
Click to expand...
Click to collapse
Because it came out first and I haven't been given a sound reason to switch. Why fix what ain't broken?
I like to use the official version. They provide weekly firmware updates.
Wobbo-Q said:
I like to use the official version. They provide weekly firmware updates.
Click to expand...
Click to collapse
To each his own. Personally, I don't care about weekly updates. Unless an update fixes something that I use, or it includes a major security update, I don't care about it. Manually updating every couple of months does it for me.
I am also in unofficial build for now but the official thing is making me wanna try it...but should we just flash it and format data or should be flash recovery provided too?
I would follow LineageOS guide. You will use something other than TWRP. You then use one of LineageOS. This one is quite limited but looks nice (not very important). But I don't need all the features of TWRP, I don't understand it anyway. LOL
https://wiki.lineageos.org/devices/gta4xl/install