Related
I just moved from Pure Nexus 7.1 to SuperXE 8.1. I think I forgot to flash vendor image but otherwise did full clean flash. ROM boots but when trying to connect to WiFi there is voice input but no keyboard. Haven't ever seen something like this before... Added vendor image and redid full/clean flash multiple times with same result. Unfortunately, activity on that ROM thread is a bit slow and I'm down without my phone so decided to ask for help here.
Adding $20 bounty for help fixing. Serious withdrawal mode without my phone. I have a backup phone but it is nearly unusable...
Solution here https://forum.xda-developers.com/showpost.php?p=76126862&postcount=263
Since you are coming from Nougat to Oreo i would suggest you first flash the full oreo factory image before flashing the oreo custom rom. Its not usually a must but solves a lot of minor problems
Hello Friends
I have experimented with flex1911's camera and finaly succeded to make flashable zip of Huawei camera for Treble GSI roms.
Camera has only been tested on Havoc 2.9 ROM for now and everything is working.
Feel free to try it on other ROMs and report.
Installation:
Flash Treble Pie GSI (fastboot)
Flash TWRP recovery (fastboot)
Flash Camera (TWRP)
Big thanks to flex1911 and Phie, without their work this would not be possible.
Download:
https://mega.nz/#!U8InwYLS!K0zpjYdNSzC6iX8XkzUVvM0IG_dssfAagfowo1BudgI
Thanks for the zip:good:
aand since you also got a P9 running havoc 2.9 gsi, may I ask you whether bmgr backupmanager works for you, if you can access all apps in play store (ie whatsapp) or pass safetynet with any Magisk version higher than 19.3? That are the remaining issues I have using this rom, aside from wifi hotspot and network signal indication.
I've seen this thread from @Hami_Do over at the P10 lite forums and thought maybe we can do something similar and collect fixes for hi3650 specific issues on gsi roms.
https://forum.xda-developers.com/p10-lite/how-to/gsis-manual-fixes-hi6250-devices-t3936745
What totally works on the P9 as well is their offline charging animation fix.
And what also makes quite a difference is the 'Hwcomposer' fix, which basically brings stock-like smoothness and screen quality on gsi, and even seems to save some battery.
I doubt their zip works on hi3650 devices but I've collected the files from vendor and the trick does work on our devices too, but it's not yet flashable. Maybe you want to help.
BlurryUi workaround in phh treble app needs to be checked (debug.hwui.profile=true) and disable hw-overlays in developer option toogled few times to get it started.
lo_ol said:
Thanks for the zip:good:
aand since you also got a P9 running havoc 2.9 gsi, may I ask you whether bmgr backupmanager works for you, if you can access all apps in play store (ie whatsapp) or pass safetynet with any Magisk version higher than 19.3? That are the remaining issues I have using this rom, aside from wifi hotspot and network signal indication.
I've seen this thread from @Hami_Do over at the P10 lite forums and thought maybe we can do something similar and collect fixes for hi3650 specific issues on gsi roms.
https://forum.xda-developers.com/p10-lite/how-to/gsis-manual-fixes-hi6250-devices-t3936745
What totally works on the P9 as well is their offline charging animation fix.
And what also makes quite a difference is the 'Hwcomposer' fix, which basically brings stock-like smoothness and screen quality on gsi, and even seems to save some battery.
I doubt their zip works on hi3650 devices but I've collected the files from vendor and the trick does work on our devices too, but it's not yet flashable. Maybe you want to help.
BlurryUi workaround in phh treble app needs to be checked (debug.hwui.profile=true) and disable hw-overlays in developer option toogled few times to get it started.
Click to expand...
Click to collapse
I have not tried backup manager. Whatsapp is not in play store. Not passing safetynet, and Magisk is version 20.1.
For those fixes i think it would be best to ask guys on original thread can we use their stuff as a base and than start making those fixes one by one.
I have not really tried to fix all that stuff couse this is my backup phone. We can try for sure.
So for a start I came up with a quick& dirty playstore fix.
Booted emui, compared its reported features and plainly copied everything over that was missing from havoc report. Result is attached. Copy to /system/etc/sysconfig chmod 644, clear playstore data and reboot. All apps will appear. Also no fc anymore when trying to access nfc/bluetooth settings from menu. Backup manager still fails though
Also found an app in Playstore that can show the real network signal values on gsi despite the OS failure. Network Cell Info Lite https://play.google.com/store/apps/details?id=com.wilysis.cellinfolite&hl=de
Maybe we can debug and look what it does differently from @phhusson implementation to fix it
[
lo_ol said:
Thanks for the zip:good:
aand since you also got a P9 running havoc 2.9 gsi, may I ask you whether bmgr backupmanager works for you, if you can access all apps in play store (ie whatsapp) or pass safetynet with any Magisk version higher than 19.3? That are the remaining issues I have using this rom, aside from wifi hotspot and network signal indication.
I've seen this thread from @Hami_Do over at the P10 lite forums and thought maybe we can do something similar and collect fixes for hi3650 specific issues on gsi roms.
https://forum.xda-developers.com/p10-lite/how-to/gsis-manual-fixes-hi6250-devices-t3936745
What totally works on the P9 as well is their offline charging animation fix.
And what also makes quite a difference is the 'Hwcomposer' fix, which basically brings stock-like smoothness and screen quality on gsi, and even seems to save some battery.
I doubt their zip works on hi3650 devices but I've collected the files from vendor and the trick does work on our devices too, but it's not yet flashable. Maybe you want to help.
BlurryUi workaround in phh treble app needs to be checked (debug.hwui.profile=true) and disable hw-overlays in developer option toogled few times to get it started.
Click to expand...
Click to collapse
TNX BRO for your great work
but can you explain more ? how to this?
HTML:
phh treble app needs to be checked (debug.hwui.profile=true)
and this attachment file just flash frm twrp and done?
Phh treble app is in settings menu, on any phh based gsi rom I guess. Just scroll down a bit? Checking the option just sets the property. You can also add the line to build.prop or use an init script as well. It's not a flashable zip, files need to get copied over either via adb or root explorer. A good app to notice the difference is cpu-z. If it's text is always sharp like in the screenshot, it's working and if it comes up blurry, it's not
Thanks for the zip for gsi.
@lo_ol on gsi phh app no choice that !
What copy exactly to fix blurry ? Can explain more and simply , thanks ^_^
edint3000 said:
Hello Friends
I have experimented with flex1911's camera and finaly succeded to make flashable zip of Huawei camera for Treble GSI roms.
Camera has only been tested on Havoc 2.9 ROM for now and everything is working.
Feel free to try it on other ROMs and report.
Installation:
Flash Treble Pie GSI (fastboot)
Flash TWRP recovery (fastboot)
Flash Camera (TWRP)
Big thanks to flex1911 and Phie, without their work this would not be possible.
Download:
https://mega.nz/#!U8InwYLS!K0zpjYdNSzC6iX8XkzUVvM0IG_dssfAagfowo1BudgI
Click to expand...
Click to collapse
anyone tryed this on android 10 gsi?
reynard1 said:
anyone tryed this on android 10 gsi?
Click to expand...
Click to collapse
I tried to boot Havoc 3.0 but it bootlooped. So no.
edint3000 said:
I tried to boot Havoc 3.0 but it bootlooped. So no.
Click to expand...
Click to collapse
expressluke roms bootloop on p9 ,idk why but im working on it
you can use phh version
Is there any camera fix for aosp 10?
photos can't be saved to SD, it says that the SDCard is ful when it runs on HAVOS 2.9
Anyone got this working for android 10 phh-based roms?
shyvanna said:
Anyone got this working for android 10 phh-based roms?
Click to expand...
Click to collapse
I'd like to know too
Hi, I open this thread because I wanted to kindly ask for advice on what the best bootstack to install Pie Roms like Resurrection Remix 7.0.2 or ViperOS 6.7 might be.
I have already used the A2017x_LineageOS15.1_UniversalBootstack_v2_by_DrakenFX but, when I flash it, even with TWRP_3.2.3-0L_v1.3-Axon7-Labs_Mod and its Remove Message function, I cannot remove the Bootloader Unlock Warning and I cannot boot directly into recovery (either from the phone off with the combination of keys or through the advanced restart of the Roms) without pressing the VolumUp key 2 or 3 times on the Bootloader Unlock Warning screen.
It's not a particularly annoying thing but it led me to wonder if there was a better Bootstack (in the past I tried the Axon7_RR-O_B32-B10_TREBLE-Ready_Oki20180803_FULL_EDL by Oki and I liked his Customized Bootstack with the personalized boot image)
So I wanted to kindly ask if anyone is aware of a better or more stable or more updated Boostack than this (all 3 would be better :fingers-crossed.
I accept any advice and I thank in advance anyone who will know how to help me and the whole forum to keep this device still alive (a special thanks to Raystef66, Oki, NFound and DrakenFX for all the work and guides that have been very useful to me in recent days).
Hi,
When flashing full EDL from DrakenFX, did you put a generic splash.img in the specific "splash" folder located in EDL TOOL ? If I remember correctly, this could delete annoying warning message when booting.
Volumetrik said:
Hi,
When flashing full EDL from DrakenFX, did you put a generic splash.img in the specific "splash" folder located in EDL TOOL ? If I remember correctly, this could delete annoying warning message when booting.
Click to expand...
Click to collapse
I downloaded A2017x_LineageOS15.1_UniversalBootstack_v2_by_DrakenFX.zip and flashed it with A2017G-O-B04-MODEM.zip from TWRP before flashing the rom.
Punisherk said:
I downloaded A2017x_LineageOS15.1_UniversalBootstack_v2_by_DrakenFX.zip and flashed it with A2017G-O-B04-MODEM.zip from TWRP before flashing the rom.
Click to expand...
Click to collapse
OK, I made a mistake, full EDL is by Oki and not DrakenFX. This is in full EDL package the abitility to flash "splash.img".
This operation can be performed in EDL mode, that's what I meant in my previous post.
In the past, I tried your method (flashing by TWRP) , but I can't help since it didn't work for me.
Volumetrik said:
OK, I made a mistake, full EDL is by Oki and not DrakenFX. This is in full EDL package the abitility to flash "splash.img".
This operation can be performed in EDL mode, that's what I meant in my previous post.
In the past, I tried your method (flashing by TWRP) , but I can't help since it didn't work for me.
Click to expand...
Click to collapse
Thanks for the answer, I have already tried Oki's EDL in the past (Axon7_RR-O_B32-B10_TREBLE-Ready_Oki20180803_FULL_EDL) but, I experienced some problems flashing an alternative recovery to NFound's 3.2.1-7 present inside the package after the installation.
If I'm not mistaken then it seems to me that the DrakenFX boostack is more recent and updated (I'm not an expert, I only compared the modification and creation dates of the files and the original creation dates of the ZTE boostacks, modified and used by Oki , and LineageOS used by DrakenFX, and so it seemed to me ).
I will try again and see how it goes.
For the moment the combination of A2017x_LineageOS15.1_UniversalBootstack_v2_by_DrakenFX with A2017G-O-B04-MODEM (especially this because the A2017G_OreoModem proposed by DrakenFX to be combined with his bootstack is more dated and, here in Italy, with the latest original modem published by ZTE, the reception in LTE with Fastweb is much better) and RR-P-v7.0.2-20200112-axon7-OFFICIAL works beautifully without bugs (or at least I haven't experienced it yet :fingers-crossed.
Can I kindly ask you if you know any other modified bootstack besides Oki's and DrakenFX's that are worth trying?
PS: I apologize if there are grammatical errors but my English is a bit rusty and I am helping myself with Google Translate to write these messages .
I didn't try another kernel/bootstack. However, many users talk about baddar kernel.
If you can try it (or another one) , I am very interested by your feedback [emoji39]
Volumetrik said:
I didn't try another kernel/bootstack. However, many users talk about baddar kernel.
If you can try it (or another one) , I am very interested by your feedback [emoji39]
Click to expand...
Click to collapse
If I remember correctly the Resurrection Remix 7.0.2, which I am currently using, it is based on the Baddar kernel RC1.2 (OrdenKrieger's work).
I am currently using it with great satisfaction and it works beautifully.
For the activities that I have done so far I have not encountered any bugs, the phone works fast and smooth and the battery lasts 90-100% longer than before (more than 2 days between a recharge, for a battery older than 2 years , it's miraculous).
Punisherk said:
Hi, I open this thread because I wanted to kindly ask for advice on what the best bootstack to install Pie Roms?
Click to expand...
Click to collapse
Saw your post and you reminded me about AEX 5.8 ROM by NFound. One of the versions had a great battery life, and there was bootstack transition recommended by NFound itself.
Not sure, but he suggest to use A2017U B12 Oreo beta bootstack instead of A2017U B35 Nougat on later versions. Why? I don't know.
Most of people will use Universal v2 by DrakenFX, some may stay on Verequies no splash (B20 US?)/NFound (B12 US?) bootstack/Oki.
Did anyone stayed with Nougat bootstack on Oreo/Pie and have an opinion about this mix?
Few minutes ago, I jumped to b12 bootstack, with TWRP 3.2.1-8 treble and no issues so far.
klałn said:
Saw your post and you reminded me about AEX 5.8 ROM by NFound. One of the versions had a great battery life, and there was bootstack transition recommended by NFound itself.
Not sure, but he suggest to use A2017U B12 Oreo beta bootstack instead of A2017U B35 Nougat on later versions. Why? I don't know.
Most of people will use Universal v2 by DrakenFX, some may stay on Verequies no splash (B20 US?)/NFound (B12 US?) bootstack/Oki.
Did anyone stayed with Nougat bootstack on Oreo/Pie and have an opinion about this mix?
Few minutes ago, I jumped to b12 bootstack, with TWRP 3.2.1-8 treble and no issues so far.
Click to expand...
Click to collapse
If I'm not mistaken, NFound's guide to installing AEX plans to Treblelize the phone by creating multiple partitions and formatting Data and Cache in f2fs file system instead of ext4.
I tried this solution about a year ago, following a guide, but the result, even after a couple of attempts, was not satisfactory in my case (long-term instability problems, sometimes abnormal battery consumption and not really working fluid).
At the end of the tests I had returned to the original system making myself lean towards waiting for new solutions.
I haven't tried AEX since, but I think I'll think about it since time and updates have gone by.
For Verequies, if I remember correctly, it should be included in one of the two EDL packages proposed in the Oki guide [GUIDE] [TREBLE] Axon 7 Custom OREO ROM installation for newbies - 2018.08.05.
I also tried this system but, for the results obtained, I preferred to use another solution.
Currently I have installed the RR 7.0.2 with the DrakenFX Universal Boostack, even if with another Modem compared to the one proposed by him for the A2017G (i.e. the A2017G-O-B04-MODEM of the original Oreo update of the ZTE because, here in Italy with Fastweb operator, it has better reception in LTE +).
Everything works beautifully, smoothly, without bugs or crashes (with formatting in ext4 because, in f2fs instead, crashes started already after 2 days without restarting the device) and the battery consumption is halved (two days between a charge and the other that, for a battery 2 years old and more, seems almost a miracle).
I also really like the enormous possibility of personalization that RR brings with it.
I will try to experiment an installation with the original Nougat boostack, as you suggested, to see the results and compare them.
For the TWRP to be used, do you suggest the NFound 3.2.1-8 or the TWRP_3.2.3-0L_v1.3-Axon7-Labs_Mod made in collaboration (personally I prefer the second one for the multi language besides other things)?
Punisherk said:
If I'm not mistaken, NFound's guide to installing AEX plans to Treblelize the phone by creating multiple partitions and formatting Data and Cache in f2fs file system instead of ext4.
I tried this solution about a year ago, following a guide, but the result, even after a couple of attempts, was not satisfactory in my case (long-term instability problems, sometimes abnormal battery consumption and not really working fluid).
At the end of the tests I had returned to the original system making myself lean towards waiting for new solutions.
I haven't tried AEX since, but I think I'll think about it since time and updates have gone by.
For Verequies, if I remember correctly, it should be included in one of the two EDL packages proposed in the Oki guide [GUIDE] [TREBLE] Axon 7 Custom OREO ROM installation for newbies - 2018.08.05.
I also tried this system but, for the results obtained, I preferred to use another solution.
Currently I have installed the RR 7.0.2 with the DrakenFX Universal Boostack, even if with another Modem compared to the one proposed by him for the A2017G (i.e. the A2017G-O-B04-MODEM of the original Oreo update of the ZTE because, here in Italy with Fastweb operator, it has better reception in LTE +).
Everything works beautifully, smoothly, without bugs or crashes (with formatting in ext4 because, in f2fs instead, crashes started already after 2 days without restarting the device) and the battery consumption is halved (two days between a charge and the other that, for a battery 2 years old and more, seems almost a miracle).
I also really like the enormous possibility of personalization that RR brings with it.
I will try to experiment an installation with the original Nougat boostack, as you suggested, to see the results and compare them.
For the TWRP to be used, do you suggest the NFound 3.2.1-8 or the TWRP_3.2.3-0L_v1.3-Axon7-Labs_Mod made in collaboration (personally I prefer the second one for the multi language besides other things)?
Click to expand...
Click to collapse
Have been on B12 Nougat bootstack and I don't recommend it.
- Offline charging worked when ROM was installed, without ROM, offline charging still worked but broke Oreo recovery.
- Fastboot worked - like above
- B04 modem worked
- Different BMS/battery behaviour on low health battery (72%) - SOT was same, no shutdowns on low battery, better battery percentage calculation.
(Could be placebo due to battery health and warmer weather)
- Colder phone on low tasks (placebo)
It isn't worth to stay on B12 bootstack.
Everything was fine, until played with him, then **** happened.
3.2.1-8, 3.2.3 with vendor support and 3.2.3 oki recovery doesn't work, if they are flashed on clean B12 - 3 blinks.
They only work, when flashed on DrakenFX bootstack and moving to B12 bootstack.
On first boot to recovery on DFX, they doesn't work, but on second boot they are working.
After flashing no splash message aboot on B12 it worked, until i tried fastboot - everything broke up, incl. system partitions.
I know that there is a method to unlock the bootloader of the V35, and that seems to be the only prerequisite to get a treble GSI on a device. I was wondering if anyone here has tried a GSI on the V35? I'd love to try an AOSP experience on the V35, but I'm unaware of the potential issues that may come from using GSI's on the V35.
EDIT: For anyone that wants to know how treble GSIs(specifically HavocOS 2.9) are on the LG V35; it's pretty buggy and unusable in its initial state(audio not working through audio jack, buggy vibration, double tap to wake not working, auto brightness, etc). To remedy some of the issues, I created an overlay for the V35(which I will attach to this post) that fixes the jack audio(not sure if the DAC is working though), the vibration, and auto brightness. Just put the overlay into /system/overlay/ and reboot 1-2 times. The overlay makes HavocOS 2.9 usable enough as a daily driver for me; the only immediate large issue I still have is that double tap to wake still doesn't work.
GSI in general lack the following feature:
VoLTE
Resolution switch
Double tap to wake
DAC
Screen Casting/Mirroring
Always on Display (Can be 'fixed' by using an overlay, refer to https://github.com/phhusson/vendor_hardware_overlay/tree/master/LG/G7 )
Pie GSI in general works, some have vibration issue that can be fixed by patching the device fingerprint with the original V35 one.
Working ones:
Havoc OS
ArrowOS
AOSIP
Lineage
Common problem with Q GSI:
Most won't boot (can possibly be fixed by applying the selinux permissive patch
Screen won't light up after device goes to sleep
WiF's not working properly
Q GSI that boots:
Some of the ErfanGSIs
kaneorotar said:
GSI in general lack the following feature:
VoLTE
Resolution switch
Double tap to wake
DAC
Screen Casting/Mirroring
Always on Display (Can be 'fixed' by using an overlay, refer to https://github.com/phhusson/vendor_hardware_overlay/tree/master/LG/G7 )
Pie GSI in general works, some have vibration issue that can be fixed by patching the device fingerprint with the original V35 one.
Working ones:
Havoc OS
ArrowOS
AOSIP
Lineage
Common problem with Q GSI:
Most won't boot (can possibly be fixed by applying the selinux permissive patch
Screen won't light up after device goes to sleep
WiF's not working properly
Q GSI that boots:
Some of the ErfanGSIs
Click to expand...
Click to collapse
Thanks! How did you go about installing the GSIs? Even though they sound glitchy, I would like to try a GSI. I am currently running stock rooted.
Generic123. said:
Thanks! How did you go about installing the GSIs? Even though they sound glitchy, I would like to try a GSI. I am currently running stock rooted.
Click to expand...
Click to collapse
Well, you can try "following" the instructions here (only works if you are on stock Pie): https://github.com/kaneorotar/LG-V35-Tinkering-Instructions (haven't had time to write the English version)
Basically you need to first install TWRP, then flash the Universal DM-Verity, ForceEncrypt zip, followed by Formatting Data and you will be good to go.
Hello everyone!
I have a Moto G5 plus which still works quite well as my only phone, but I'm curious to experiment.
Seeing as official support and security updates have ended, I don't think I'm missing out on anything by leaving stock.
I'm looking for recommendations on which ROM to use, as well as any tips or advice you can give.
Top priorities:
Security and stability (as much as possible)
Connectivity (4G LTE, Wifi without any hiccups)
Bluetooth (support for as many audio codecs as possible, especially Aptx)
Camera should be fully functional
I can't think of any other priorities right now, but maybe narrows the field of options a bit.
I have never installed a ROM nor rooted a device, but I am a quick learner.
Also a quick question, is rooting the phone required? And even if it's not required, do I get any benefit from doing so?
Any input will be greatly appreciated!
Thanks in advance!!
Spektater said:
Hello everyone!
I have a Moto G5 plus which still works quite well as my only phone, but I'm curious to experiment.
Seeing as official support and security updates have ended, I don't think I'm missing out on anything by leaving stock.
I'm looking for recommendations on which ROM to use, as well as any tips or advice you can give.
Top priorities:
Security and stability (as much as possible)
Connectivity (4G LTE, Wifi without any hiccups)
Bluetooth (support for as many audio codecs as possible, especially Aptx)
Camera should be fully functional
I can't think of any other priorities right now, but maybe narrows the field of options a bit.
I have never installed a ROM nor rooted a device, but I am a quick learner.
Also a quick question, is rooting the phone required? And even if it's not required, do I get any benefit from doing so?
Any input will be greatly appreciated!
Thanks in advance!!
Click to expand...
Click to collapse
Hello. I can only speak to LineageOS. I have tried others and had bugs that I could not live with. Most new ROMs may have them until they get some exposure and support. Motorola quit supporting the G5 Plus in the early part of 2019, I think. Seems like a lot of support for software in a lot of devices disappears in 2 years or so. GothicIV has been applying android security patches for this year, every month as google releases them.
I have never had any 4G LTE or wireless problems. I use a Verizon virtual mobile carrier.
Can't tell you about Bluetooth codecs, other than I use a plantronics bluetooth set and it works fine.
LineageOS has a built in no frills movie/still camera that works. But if you have google support, you can download the original motorola camera and it works fine. I also use the FV-5 still and FV-5 Cinema camera's out of the play store (paid app) and they work fine.
Rooting is not required, but it allows you to get to the operating system. In Linux (which android is based on) You have ordinary user privileges to install and remove apps. A super user can add/remove/delete files to the OS and change configuration files. When you root a phone, you are being elevated to super user (SU). A bunch of folks and google warn against this, its because they want you to use the system as they provided, like "look - but - dont touch", The concerns are valid, but if you are a linux user, you can make up your own mind. I feel their warnings are over rated, personally. Magisk , a common rooting program will only allow super user to programs you authorize to have super user access.
Basically, you have to unlock the boatloader - and that voids your warranty, but your probably out of that. I think motorola will only allow you to unlock the bootloader if you bought it retail. After unlocking the bootloader, install TWRP a program for backup and restore, which most everybody uses to install ROMs. A lot of ROMs require the memory to be un-encrypted to work, sometimes TWRP can do this, sometimes you need a SU and de-crypter helper program to do this.
Also, I cannot stress this more, after you install TWRP, back up the phone. The Persist and EFS files are individualized files for you phone. Basically radio calibrations and every phone is different.
I wrote a procedure for this, a PDF, its at http://s000.tinyupload.com/?file_id=30022986655137330218 . Its my documentation for future reference if something goes wrong. I have three Moto G5+ and all are on LineageOS.
Hope that helps.
Nivead said:
Hello. I can only speak to LineageOS. I have tried others and had bugs that I could not live with. Most new ROMs may have them until they get some exposure and support. Motorola quit supporting the G5 Plus in the early part of 2019, I think. Seems like a lot of support for software in a lot of devices disappears in 2 years or so. GothicIV has been applying android security patches for this year, every month as google releases them.
I have never had any 4G LTE or wireless problems. I use a Verizon virtual mobile carrier.
Can't tell you about Bluetooth codecs, other than I use a plantronics bluetooth set and it works fine.
LineageOS has a built in no frills movie/still camera that works. But if you have google support, you can download the original motorola camera and it works fine. I also use the FV-5 still and FV-5 Cinema camera's out of the play store (paid app) and they work fine.
Rooting is not required, but it allows you to get to the operating system. In Linux (which android is based on) You have ordinary user privileges to install and remove apps. A super user can add/remove/delete files to the OS and change configuration files. When you root a phone, you are being elevated to super user (SU). A bunch of folks and google warn against this, its because they want you to use the system as they provided, like "look - but - dont touch", The concerns are valid, but if you are a linux user, you can make up your own mind. I feel their warnings are over rated, personally. Magisk , a common rooting program will only allow super user to programs you authorize to have super user access.
Basically, you have to unlock the boatloader - and that voids your warranty, but your probably out of that. I think motorola will only allow you to unlock the bootloader if you bought it retail. After unlocking the bootloader, install TWRP a program for backup and restore, which most everybody uses to install ROMs. A lot of ROMs require the memory to be un-encrypted to work, sometimes TWRP can do this, sometimes you need a SU and de-crypter helper program to do this.
Also, I cannot stress this more, after you install TWRP, back up the phone. The Persist and EFS files are individualized files for you phone. Basically radio calibrations and every phone is different.
I wrote a procedure for this, a PDF, its at *link* . Its my documentation for future reference if something goes wrong. I have three Moto G5+ and all are on LineageOS.
Hope that helps.
Click to expand...
Click to collapse
Hello Nivead!
I could not have hoped for a more detailed answer!!
Once I make up my mind, I will most definitely use your guide! The PDF was crystal clear! I thank you deeply for all the effort that you clearly put into helping others
I'm still in doubt due to an important difference; you used a 4gb RAM version, but mine is only 2gb RAM (XT1681)
I've heard that with only 2gb RAM, I should give up on Custom ROMs, and that I won't get better performance than Stock.
I was hoping that a custom rom, with optimizations taken from Android 9, 10 and 11, or even with user designed tweaks, could improve performance, even by a small margin, over the stock Android 8.1.
But I do understand 2gb is VERY low by today's standards, and that most custom roms are designed with double that RAM in mind.
Knowing that my device has only 2gb RAM total, would you still recommend LineageOS in my quest for a slight performance boost, or should I just do a clean install of regular old stock 8.1?
Thank you very much in advance for your time and kindness!
Spektater said:
Hello Nivead!
I could not have hoped for a more detailed answer!!
Once I make up my mind, I will most definitely use your guide! The PDF was crystal clear! I thank you deeply for all the effort that you clearly put into helping others
I'm still in doubt due to an important difference; you used a 4gb RAM version, but mine is only 2gb RAM (XT1681)
I've heard that with only 2gb RAM, I should give up on Custom ROMs, and that I won't get better performance than Stock.
I was hoping that a custom rom, with optimizations taken from Android 9, 10 and 11, or even with user designed tweaks, could improve performance, even by a small margin, over the stock Android 8.1.
But I do understand 2gb is VERY low by today's standards, and that most custom roms are designed with double that RAM in mind.
Knowing that my device has only 2gb RAM total, would you still recommend LineageOS in my quest for a slight performance boost, or should I just do a clean install of regular old stock 8.1?
Thank you very much in advance for your time and kindness!
Click to expand...
Click to collapse
When I wrote the procedure, I was taking a phone back to LineageOS 15.1 . One should be able to substitute any ROM in place of the LineageOS and the procedure should still work. I have used LineageOS 14 (Vache), also LineageOS 16 (Coldhans) and LineageOS 17.1 (thread by Riyan65) and Pixel Experience AOSP (thread by ZjRDroid).
I do not know about the 2/4 GB performance issues/differences. I would research the forum threads on the ROM and see if problems were reported, and if the ROM requires a 4 GB memory. Also, bear in mind that memory works different in android/linux compared to windows.
I do not know if LineageOS would give you a performance boost. You would have to try it and see, I will say, that the google play store and its related apps put a performance drain on android. They are constantly checking in with google when you use the apps, and constantly looking for updates. That means battery is being used by the radio modems in the background. If you do not need playstore access, its a boost. Or you could use the nano gapps to have just play store access without all the other google apps the were installed by default in android 7/8.1.
I would not re-install stock moto 8.1 as a performance issue. I would do a factory erase, it should return the phone back to the state of when the phone was upgraded to stock 8.1. Bear in mind that all data, photos and apps you added will be erased. I would only re-install moto stock 8.1 if I was coming back from a ROM and going to a different ROM. Most ROMs start with stock moto 8.1 and just lay their code on top of it. So parts of the stock firmware gets over written and parts of it remain stock.
If you can afford to purchase a new phone - and do without your G5 plus, because you bricked it - I would try a ROM. If you can not do without your phone, I would leave it alone. I trashed one of my phones and it took me a day to recover it back to stock. That is one of the main reasons I wrote the procedure.
Sorry, I could not help some more...
Nivead said:
When I wrote the procedure, I was taking a phone back to LineageOS 15.1 . One should be able to substitute any ROM in place of the LineageOS and the procedure should still work. I have used LineageOS 14 (Vache), also LineageOS 16 (Coldhans) and LineageOS 17.1 (thread by Riyan65) and Pixel Experience AOSP (thread by ZjRDroid).
I do not know about the 2/4 GB performance issues/differences. I would research the forum threads on the ROM and see if problems were reported, and if the ROM requires a 4 GB memory. Also, bear in mind that memory works different in android/linux compared to windows.
I do not know if LineageOS would give you a performance boost. You would have to try it and see, I will say, that the google play store and its related apps put a performance drain on android. They are constantly checking in with google when you use the apps, and constantly looking for updates. That means battery is being used by the radio modems in the background. If you do not need playstore access, its a boost. Or you could use the nano gapps to have just play store access without all the other google apps the were installed by default in android 7/8.1.
I would not re-install stock moto 8.1 as a performance issue. I would do a factory erase, it should return the phone back to the state of when the phone was upgraded to stock 8.1. Bear in mind that all data, photos and apps you added will be erased. I would only re-install moto stock 8.1 if I was coming back from a ROM and going to a different ROM. Most ROMs start with stock moto 8.1 and just lay their code on top of it. So parts of the stock firmware gets over written and parts of it remain stock.
If you can afford to purchase a new phone - and do without your G5 plus, because you bricked it - I would try a ROM. If you can not do without your phone, I would leave it alone. I trashed one of my phones and it took me a day to recover it back to stock. That is one of the main reasons I wrote the procedure.
Sorry, I could not help some more...
Click to expand...
Click to collapse
Not at all! You have been incredibly helpful and informative!
I could probably afford a new phone if it came to that, but I was hoping to improve the performance of the G5 Plus so that it could get me by for 1 or 2 more years, until 5G becomes more widespread and good cheap 5G phones become available.
Maybe I could try Lineage and see how it goes. I've heard that even if I brick it, it is usually reversible with some effort... how true do you feel this is?
If bricking is irreversible, maybe it is not worth the risk, as the phone still works quite well, and would be a nice gift for a friend when I decide to buy a new one.
And a final question, if I decide to try out a ROM, I can always go back to stock by doing a factory reset right?
Thank you very very much for all your patience!
Spektater said:
Not at all! You have been incredibly helpful and informative!
I could probably afford a new phone if it came to that, but I was hoping to improve the performance of the G5 Plus so that it could get me by for 1 or 2 more years, until 5G becomes more widespread and good cheap 5G phones become available.
Maybe I could try Lineage and see how it goes. I've heard that even if I brick it, it is usually reversible with some effort... how true do you feel this is?
If bricking is irreversible, maybe it is not worth the risk, as the phone still works quite well, and would be a nice gift for a friend when I decide to buy a new one.
And a final question, if I decide to try out a ROM, I can always go back to stock by doing a factory reset right?
Thank you very very much for all your patience!
Click to expand...
Click to collapse
I am also hanging on to my G5+'s as long as I can. 5G implementation has started, but its ways off for full coverage.
I asked about bricking, as it can happen if one does not follow procedures, or have a hardware failure. . Usually when a phone is bricked, its unrecoverable. Sometimes a professional may be able to recover the phone, they do this by opening the phone and making direct connections to the NAND memory. If they are able to communicate with the memory and the hardware is OK, they can reinstall an image of the operating system. If it boots, you have a operating phone. I just wanted to be clear, there is a risk.
If you put a ROM on the phone, its a new operating system. If it has problems, or does not boot, etc - you usually can "fastboot" the original moto 8.1 firmware and the phone should be OK.
If you put a new operating system on the phone and do a factory reset, you are still inside the new operating system - your just wiping it clean. In order to get back to the moto 8.1 stock firmware, you will either have to install backup image via TWRP - which does not always work - or - fastboot the original moto 8.1 firmware, which usually works.
Fastboot is a command in the Android Device Bridge terminal program. ADB is a command line terminal program that runs on your computer and is used to move firmware from the computer to the phone. Fastboot also has some maintenance and housekeeping commands.
My advice, is to read up on all the required tasks, so you know how things react. Also keep a log of what you did, so if something goes wrong, you can attempt to back track to the problem. XDA forums has a lot of info available on all the task required. Also if something goes wrong, you can stop and ask for help on the forum.
Nivead said:
I am also hanging on to my G5+'s as long as I can. 5G implementation has started, but its ways off for full coverage.
I asked about bricking, as it can happen if one does not follow procedures, or have a hardware failure. . Usually when a phone is bricked, its unrecoverable. Sometimes a professional may be able to recover the phone, they do this by opening the phone and making direct connections to the NAND memory. If they are able to communicate with the memory and the hardware is OK, they can reinstall an image of the operating system. If it boots, you have a operating phone. I just wanted to be clear, there is a risk.
If you put a ROM on the phone, its a new operating system. If it has problems, or does not boot, etc - you usually can "fastboot" the original moto 8.1 firmware and the phone should be OK.
If you put a new operating system on the phone and do a factory reset, you are still inside the new operating system - your just wiping it clean. In order to get back to the moto 8.1 stock firmware, you will either have to install backup image via TWRP - which does not always work - or - fastboot the original moto 8.1 firmware, which usually works.
Fastboot is a command in the Android Device Bridge terminal program. ADB is a command line terminal program that runs on your computer and is used to move firmware from the computer to the phone. Fastboot also has some maintenance and housekeeping commands.
My advice, is to read up on all the required tasks, so you know how things react. Also keep a log of what you did, so if something goes wrong, you can attempt to back track to the problem. XDA forums has a lot of info available on all the task required. Also if something goes wrong, you can stop and ask for help on the forum.
Click to expand...
Click to collapse
Ok, I will definitely keep that in mind.
To say the truth, I'm still on the fence on whether to use a Custom Rom or not, as many people have told me I won't get better performance with any custom than I would with Stock. This appears to be especially true given the low RAM of my device (just 2 GB).
Regardless of what I end up doing, I would like to deeply thank you for all the time and dedication you put into your replies.
If everyone was as willing and helpful as you, the world would be a better place!
I too recommend LineageOS. I'm still running 15.1 (Oreo) on my 2GB G5. @gothicVI has a bunch of versions, with security updates, available here.
Zojak said:
I too recommend LineageOS. I'm still running 15.1 (Oreo) on my 2GB G5. @gothicVI has a bunch of versions, with security updates, available here.
Click to expand...
Click to collapse
Well, two different opinions both recommending LineageOS definitely sounds appealing. I've heard ArrowOS is quite good as well. So many options!! I was hoping to get a ROM with Android 11 features, but maybe I'm aiming too high, considering its only a 2gb device
I tried PixelExperience and ArrowOS. Mainly to see if I could get gcam's nightsight to work with 2GB. Despite my attempts, with roms and tweaking system memory settings, I couldn't get nightsight working. So I went back to LOS 15.1 for the Xposed support. In 2019 I picked up a Moto G7+ (running LOS 17.1) and haven't touched my G5 much. Just flashing @gothicVI's security updates on it every so often.
Zojak said:
I tried PixelExperience and ArrowOS. Mainly to see if I could get gcam's nightsight to work with 2GB. Despite my attempts, with roms and tweaking system memory settings, I couldn't get nightsight working. So I went back to LOS 15.1 for the Xposed support. In 2019 I picked up a Moto G7+ (running LOS 17.1) and haven't touched my G5 much. Just flashing @gothicVI's security updates on it every so often.
Click to expand...
Click to collapse
I see... I was really hoping to get a working GCam on a 2GB device, but I guess I'll have to give up on that. So you would recommend LOS over ArrowOS or DirtyUnicorns?
I'm sorry if I ask too many questions, there are so many options that a beginner like myself gets confused!
Thank you very much for all your help!
Well I haven't tried DirtyUnicorns. My time with ArrowOS was brief. I'd say try them all and see which you like best.
Google released GCam Go for low end devices. I haven't tried it but maybe it'll run better on our device.
Zojak said:
I tried PixelExperience and ArrowOS. Mainly to see if I could get gcam's nightsight to work with 2GB. Despite my attempts, with roms and tweaking system memory settings, I couldn't get nightsight working. So I went back to LOS 15.1 for the Xposed support. In 2019 I picked up a Moto G7+ (running LOS 17.1) and haven't touched my G5 much. Just flashing @gothicVI's security updates on it every so often.
Click to expand...
Click to collapse
I see. Maybe a GCam Go port could give good results, it would be interesting to see some tests on that on this device.
I'll see which ROMs I end up trying, IF I gather the courage to try custom roms jaja.
Thank you very very much for all your help!
https://www.celsoazevedo.com/files/android/google-camera/f/changelog1447/
Neat. This version seems to work on my G5. Night mode too in the settings.
Zojak said:
https://www.celsoazevedo.com/files/android/google-camera/f/changelog1447/
Neat. This version seems to work on my G5. Night mode too in the settings.
Click to expand...
Click to collapse
Will definitely keep that one in mind. Thank you!