Hi everyone,
So couple of year ago I worked at a start-up company that had an Android project. So I'm not new to flashing images (ROM, Recovery, radio...), and I know most basic tools like ADB (and I'm technical person in my daily life). That being said - I remember the pain when the Radio image doesn't fit the firmware, and you have to play around with stuff to make reception work again. or the Recovery image won't fit the ROM etc etc. I'm not sure if any of this probably still happen TODAY, but back then when I got my LG-G2 - I decided not to touch it. I don't need anything besides the basic options (making calls, taking pictures).
I'm still using Stock with 4.4.2 - and the phone is getting lagy each passing day to the point it's time to root it and install a custom rom.
As I mentioned above, I want it to be quick and painless. Sadly, I don't have the time to do insane amount of research right now, mainly because I have a 3 weeks old born at home - and I prefer to use my free time hanging with it that Q&N issues with my phone
So here's what I need your help with:
1. A recommendation for a tool to save all phone settings. Mostly - App settings, and OS settings (even though I probably not going to go for Stock again, but it doesn't hurt to back it up).
2. An instruction how to flash D802 (there' so many options this days...). My Kernel version is 3.4.0.
3. Recommended ROM to use. Here's what I need from a ROM.
a. I probably want to upgrade to more safe rooted Android version (I can't for example handle permissions on 4.4.2).
b. With that, I don't want to install the latest Android only to figure it's running slowly on LG G2, I want the interface to be snappy (the Stock was snappy for a while).
c. I prefer Minimal ROM if possible with Google Apps installed. If I'll need something, I can install it myself.
d. One of the reason I didn't root up until now, was because people mentioned camera quality is meh with non stock roms. If possible, I will like to have a decent Camera quality.
e. I use my phone as a music player often. So good sound quality is important to me (and maybe even build in Parametrized EQ?).
Thank you!
Reading around the forum would have taken just about the same amount of time than writing your post. A post, mind you, that will get you the same as what you can already find with ease.
You managed to write with your kid around. Last time I checked, browsing takes less effort.
Rant out.
Instead of a rant, here's an actual help for people who might find it useful in the future and lack the time to do some proper research (as it took more than the 5 minutes it took me to write the original post). Please note that I won't take any responsibility for possible damages you may do to your system. Please use at your own risk. Also, note that I only tried it on LG G2 802 with Stock Kit Kat (4.2.2) and other version/OS version might not work.
I wasn't clear to me if 'One Click Root' work with Kit Kat bootloader, so I used 'ioroot'. When your done rooting your phone, you will need to flash a TWRP recovery. The easiest way to do it is by using AutoRec. However, the TWRP recovery installed with AutoRec doesn't have Thermal protection, and is dangerous to use according to the forums. So the next thing will be flashing a new TWRP version from the recovery. Blastgater have tweaked TWRP Recovery for LG devices. You can download the latest version here. It's basically a zip file you flash from within your old TWRP.
Regarding ROM, after doing some research - it looks like Lineage will be the best 'all-around' rom to use. Liveage 15/16 were too slow for my liking, so I went with 14.1 (Android 7.1) which was enough for me and snappy to use. However, the tricky part if your plan on using Lineage, is to flash a bootstack as the one coming with Stock won't work. It's just another zip to flash directly from the recovery and can be found here.
So this is just the high-level process, and I highly suggest checking the specific on the links I sent. It also helps if you know how to handle 'adb' and know the basic stuff like what bootloader and recovery are
Good luck.
Related
I'm writing this as a new Nexus 7 2013 owner so that people with a moderate level of tech savvy and are still on the fence about unlocking and flashing their device can check it out from a non expert perspective. I think a lot of times people are afraid after reading tutorials and a bit intimidated by the procedures (and XDA).
I decided to get a nexus device because they are very well supported here on XDA and the general consensus is they are nearly impossible to hard brick barring a hardware issue or the user doing something really really dumb
After unboxing the device I put it on charge while making some final decisions on what direction I wanted to go with the "rebuild". As you will see some of these decisions will have cascading effects...
I settled on cleanrom 2.6 and the elementalx kernel, I also decided I wanted to use CWM (non touch) recovery instead of TWRP because I'm familiar with it and hoped that I would not spend enough time to justify having a gui.( and ... to be honest I am not a fan of TWRPs gui ).
So now that I have made my decisions for better or for worse it is time to proceed. I powered on and configured the device for the first time. Since I wasn't paying attention Google started downloading all my apps from Play. This was not a big deal but folks on a data plan might want to make sure they read the screens and decide not to restore their apps. The option for OTA upgrade was available from jellybean to kitkat, so I went ahead and proceeded with the OTA. In retrospect it was a waste of time because you can download the stock images and reflash them later if you want.
ADB and FASTBOOT were already on my Debian desktop and working properly so I went ahead and unlocked the bootloader, then rebooted and flashed CWM. I them installed supersu from CWM. (I left out the part about using adb to push the files but you get the picture...) So far so good except there was a fatal flaw in my plan. Cleanrom and ElementalX both use aroma installer, which doesn't work on CWM. So as I was doinking around In CWMs advanced options looking for a slim possibility of salvaging the situation I managed to end up in the key test application. The problem here being that since the device doesn't have a back button there was no way to get out of they key test. No worries though I simply connected the USB cable fired up adb and did "adb reboot". A few minutes later I had downloaded and installed TWRP and was ready to pick up where I left off.
Here is a note for folks doing this for the first time, read the instructions and erratta for your new kernel and ROM carefully before you proceed so that you avoid time consuming issues. By reading up a little before I started the project I knew that the ROM and kernel were compatible and work well together. I also knew that I would need to install the ROM first, then the kernel, because I I installed the Kernel first I would have to re-install it after flashing the ROM. No point in doing it twice, right?
SO I fired up TWRP and did a factory reset in preparation for flashing the ROM. So far so good. Cleanrom installed, but AROMA did not ask for my installation options. Fearing something was wrong, I clean flashed (wipe first then flash) the ROM 2 more times with the same result. After the third flash I said wth, as long as the ROM flashed and works I can always change software on my own. So a quick reboot and test drive of the device confirmed the ROM was installed and there appeared to be no glaring issues, so I went back to recovery and flashed the kernel. BTW I did check the md5sums and verified that the files were correct and not corrupted.
I know there is an option to flash more than one update with TWRP but since the install did not occur the way I expected I chose to install the ROM and kernel separately, I'm sure some more experienced members of XDA will agree with this decision and others will say that "it's nexus, go ahead and flash the ROM and kernel at the same time, you can't break it
Anyhow the kernel installation went fine and AROMA prompted me as expected before installing. Note to newbies like me, reading the thread really helps, Knowing exactly how you want to configure your kernel before you install it will save you hassles down the line. Expect the first boot to take a little extra time.
In nutshell, there really is no reason to be afraid of installing a custom kernel on your Nexus device. Sure the possibility is there for you to screw things up, but unless you do something very drastically wrong you wont brick the device, trust me -- If I can do it you can do it. Just think ahead a little and prepare yourself by downloading the files you need and maybe even writing yourself an outline of the steps. I'm sure that I could do this again and again now without referring to notes or tutorials, but having them readily available for guidance and reference was comforting.
I could continue with the saga of getting Debian to recognize the tablet in MTP mode but this post has already gone long and that is a rite of passage...
I have a stock note3 and since the Kitkat update, lost ability to record calls - nothing works, just static noise from all of them.
Also Gmail app and K9 failed. Aquamail works a treat tho'.
I'm sure there are other bits n bobs (sd access, battery life etc) that are flaky but I haven't fully tested the phone.
A call recorder is essential in my line of work so guess I need to 'fiddle' with my OS, never done it before.
So can anyone tell me what I need to do, i.e; rooting, flashing, decent custom ROM or at least a quick and pain-free mod...i don't do command line stuff and I 'm not a programmer, so anything in plain English would be helpful.
I don't mind keeping Kitkat looking as it is. I've seen my mate's customised rom note2 purchased from ebay and looks like its designed by a 14 yr old gaming nerd.- yuk.
I am very time poor so won't be able to spend hours and hours tinkering.
Thanks in advance
bornatheist said:
I have a stock note3 and since the Kitkat update, lost ability to record calls - nothing works, just static noise from all of them.
Also Gmail app and K9 failed. Aquamail works a treat tho'.
I'm sure there are other bits n bobs (sd access, battery life etc) that are flaky but I haven't fully tested the phone.
A call recorder is essential in my line of work so guess I need to 'fiddle' with my OS, never done it before.
So can anyone tell me what I need to do, i.e; rooting, flashing, decent custom ROM or at least a quick and pain-free mod...i don't do command line stuff and I 'm not a programmer, so anything in plain English would be helpful.
I don't mind keeping Kitkat looking as it is. I've seen my mate's customised rom note2 purchased from ebay and looks like its designed by a 14 yr old gaming nerd.- yuk.
I am very time poor so won't be able to spend hours and hours tinkering.
Thanks in advance
Click to expand...
Click to collapse
call record is fine if you use custom rom, most of them have a modded call recorder and work fine.
To be frank, when I was still on stock 4.4.2 unrooted, I can use gmail with no problem.
rooting => find cf-autoroot at android original development note 3.
recovery => there's twrp, philz cwm, and chenglu cwm. I use chenglu cwm. twrp & philz u can find at android original development note 3. whereby chenglu cwm you can find at android development note 3. I personally use chenglu cwm.
custom ROM => you can pick anything u want, and try. no harm trying. If you got not much time, I suggest you just pick 2 or 3 then download all of them first, copy to your sdcard, and try one by one. so, you will no need to wait again next time to download another one. I have 4 custom ROM that I like inside my sdcard. anytime I want to change I just flash them, no need to wait to download again (because each rom is quite huge around 1.5gb+).
To flash rooting, recovery and custom ROM, you have to bear in mind :
do back up your efs (I personally use dr. ketan efs backup after I root my device. this tool need device to be rooted). You can find at android themes & apps note 3
when you want to flash custom rom, remember to do nandroid backup from recovery (in case anything bad happened). Touch wood, so far I don't need to use this backup.
please do a check on the MD5 hash, to be matched with the one provided on the download thread. If not match means you have a bad download, try to download again till the MD5 is matched. Sometimes, due to file size very huge, and if your internet link down, it might cause a bad download. Don't blame on the OP/devs.
The most important before you continue all those process (rooting, recovery and custom rom), READ the thread and FOLLOW the instructions carefully. Most of the time if you follow carefully, nothing harm will happen. And... all the thread are in simple english, no coding words on the OP thread.
cheers.
bornatheist said:
I have a stock note3 and since the Kitkat update, lost ability to record calls - nothing works, just static noise from all of them.
Also Gmail app and K9 failed. Aquamail works a treat tho'.
I'm sure there are other bits n bobs (sd access, battery life etc) that are flaky but I haven't fully tested the phone.
A call recorder is essential in my line of work so guess I need to 'fiddle' with my OS, never done it before.
So can anyone tell me what I need to do, i.e; rooting, flashing, decent custom ROM or at least a quick and pain-free mod...i don't do command line stuff and I 'm not a programmer, so anything in plain English would be helpful.
I don't mind keeping Kitkat looking as it is. I've seen my mate's customised rom note2 purchased from ebay and looks like its designed by a 14 yr old gaming nerd.- yuk.
I am very time poor so won't be able to spend hours and hours tinkering.
Thanks in advance
Click to expand...
Click to collapse
to get call recording to work, use NC2 FW/rom and use NB2 modem or higher..
try clearing gmail`s data in settings, i have had zero issues with gmail..
for root/recorvery check the guide that is linked in my sig, it has step by step instructions..
as for rom i personally recommend xnote and lean kenrel to everyone..
For the exact same main reason (call recording) I've requested to the seller to solve the problem (my seller was also the carrier provider: orange).
They've changed my phone with a new one with latest 4.3, after a long conversation between orange and samsung tech support, only because my complaints about 4.4.2 implementation on note 3.
Maybe this thread is of use for you:
http://forum.xda-developers.com/showthread.php?t=2709623
Good luck,
Hi guys, have a few questions...
For starters, I have a Samsung Galaxy S4 / AT&T
Running Android 4.4.2 Rooted with Towel Root
Connected on Straight Talk
~NC1
SafeStrap 3.72 (TWRP v2.7.0.0) Installed.
Im new to all this ROM/Modules and Rooting stuff.
Last time i fully customized stuff was on my Motorola RZR ages ago
making my keypad/ LED light blink with calls, and replacing the Cingular Logo
with a Pirate/2 Swords Logo. hah... good times.
I mean there was jail-breaking and whatnot but...that's easy stuff.
Any who, Im a quick learner so on to the subject.
My original idea was to FULLY customize this phone and install ROMS/other OS, thats
what im all about, customization. Sadly, i realized im on a NC1 which its Boot loader is
locked if im understanding correctly preventing me from installing other? ROMS?
However if i understood correctly, we still can install certain ROMS? Whats the difference?
Is there any ROM i can install that is clean? no bloatware? but with everything I need?
Whats the best, fastest and best looking ROM i can get? or they dont look different because the
boot loader thing? Or they can only be Samsung/AT&T roms? This stuff can be confusing. lol
Module wise, why do i need them? why arent they included in the actual ROM?
Also, is there any App/or way for me to know what causes my phone to randomly crash/reboot?
A few months ago I was at the GYM and my phone randomly shut off. It didnt want to turn back on.
After a while it turned back on, then it would randomly reboot. That eventually went away.
Last night, i was with some friends in a bar and my phone just turned off again. Didnt wanna turn
on...then the same reboot thing happened again.
Today, is working fine. I thought maybe it was an overheat issue but, i wasnt doing anything on my
phone and on top of that im using a CPU tempt program installed through xPosed and according to the
readings it wasnt hot, as it was in the 50-55c (or is that too hot?) Im at home now and its reading
36c but i dont have its case on (if that makes any difference)
There are 3 kind of "ROM"s :
1- Official ones. made by samsung. flashable via odin exclusively. not rooted
2- A bit modified (maybe more than a bit) Official ones, modified by people, flashable via odin or recovery (1), usually already rooted
3- Completely rewritten ROMS, almost made from scratch (Cyanogenmod, MIUI for exemple...), installable via recovery. already rooted
Now, your phone can be in two states : Rooted or not rooted.
From factory, your phone is not rooted (you can compare it to jailbreak)
with root, you become a "super user", which means you have rights on almost every single aspect of your phone, and you give authorisations to apps so they can act on system files (for exemple, they can get hidden informations, they can automatically install apps etc... infinite possibilites there are.)
As for the best rom there is, is like asking what is the best music ever, it depends on the user, you have to try by yourself to find the one that satisfies you the most.
For random reboots, i personally think that it is comparable to windows Blue Screen of Deaths. you maybe messed up something while installing something. your phone can't handle the bug, so it restart or shut down itself. so the safest way to get rid of this problem is to factory reset your phone (via the recovery)
if you are looking for stableness, don't opt for completely remade ROMS, they are usually experimental. but personally i use MIUI and i didn't have any problem and i love this ROM.
Hope i answered every question.
Thanks a lot for the reply.
I understand a bit better now...
That MIUI looks interesting... Reminded me of DreamPassport for my Sega Dreamcast, hah...
I'm guessing I cant install that one huh? Lol
well since you already have a custom recovery you can... just download a miui rom (one for your phone version (be carefull about the model) ) then put it on the root of your sd card, go to the custom recovery and flash zip from sdcard and choose it... but i advice you to factory reset your phone first in order to fix your reboot problem.
also, make sure you have installed the right android version before installing the equivalent miui version (for exemple if you want to install miui that requires 4.2, install an official 4.2 rom first) via odin.
Gotcha. Thanks.
One last question....
If I want my phone with the original OS it came with. But with all the bloatware removed...
which rom would be the best? , since I want the stock experience but no bloatware.
Also...
I noticed when you click to see how much ram is being used, it says
800/1.77GB
Isnt my phone suppose to have 2GB? Can I do something to get that back? is it cause the bloatware?
I appreciate the help.
Raging Tiger said:
Gotcha. Thanks.
One last question....
If I want my phone with the original OS it came with. But with all the bloatware removed...
which rom would be the best? , since I want the stock experience but no bloatware.
Also...
I noticed when you click to see how much ram is being used, it says
800/1.77GB
Isnt my phone suppose to have 2GB? Can I do something to get that back? is it cause the bloatware?
I appreciate the help.
Click to expand...
Click to collapse
I don't think the above information is correct.
From what I know the AT&T has a locked bootloader. So you can run custom roms, just not all of them. I think only custom roms that match the version you are using.
You could better read in the section for the AT&T (this section is for a different model).
http://forum.xda-developers.com/galaxy-s4-att
Hello guys,
I'm a complete novice on rooting or flashing cellphones, I'm just a regular user of a Moto X Play XT1563 (bought in Colombia / South America) that wants to upgrade to Nougat 7.1.2.
I want the 7.1.2 just for a regular usage: apps, internet, bluetooth, NFC, camera, GPS, phone calling and of course a good battery performance.
I want to kindly ask for your guidance in all steps required for the backup and upgrade, so if you can please guide me about the whole process I will appreciate it a lot.
Thanks
jramirezdev said:
Hello guys,
I'm a complete novice on rooting or flashing cellphones, I'm just a regular user of a Moto X Play XT1563 (bought in Colombia / South America) that wants to upgrade to Nougat 7.1.2.
I want the 7.1.2 just for a regular usage: apps, internet, bluetooth, NFC, camera, GPS, phone calling and of course a good battery performance.
I want to kindly ask for your guidance in all steps required for the backup and upgrade, so if you can please guide me about the whole process I will appreciate it a lot.
Thanks
Click to expand...
Click to collapse
Hello!
In short, the process for our phone would be...
0. Backup data.
1. Unlock bootloader. This will void your warranty. Unlocking bootloader allows you to use fastboot mode to flash custom images to your phone from a computer.
2. Flash TWRP Recovery. This is done in fastboot mode. Once you have TWRP, you can flash on to or modify the system partition (and other partitions) of your phone on the go.
3. Format the /system partition to get rid of the existing ROM (stock in your case) and then flash whatever ROM you want. This is done using TWRP.
4. There's no fourth step.
Its pretty straightforward, detailed guides to each of the steps are available in this forum. You should use the Index Thread pinned on the General forum to get the links to the required guides at one place. Use the search if you encounter trouble. Then there's the forum to ask.
DragonClawsAreSharp said:
Hello!
In short, the process for our phone would be...
0. Backup data.
1. Unlock bootloader. This will void your warranty. Unlocking bootloader allows you to use fastboot mode to flash custom images to your phone from a computer.
2. Flash TWRP Recovery. This is done in fastboot mode. Once you have TWRP, you can flash on to or modify the system partition (and other partitions) of your phone on the go.
3. Format the /system partition to get rid of the existing ROM (stock in your case) and then flash whatever ROM you want. This is done using TWRP.
4. There's no fourth step.
Its pretty straightforward, detailed guides to each of the steps are available in this forum. You should use the Index Thread pinned on the General forum to get the links to the required guides at one place. Use the search if you encounter trouble. Then there's the forum to ask.
Click to expand...
Click to collapse
Thanks for your response,
I bought my cellphone two years ago so It already went out of warranty so no issues with that step, I already found the guide to "Unlock bootloader" but before I start with it I would like to ask if after that the phone will be unuseful? I mean, after unlocking the bootloader can I start the phone and continue using it? It's my only cell phone so I want to be aware if I will stay long time uncommunicated.
My second question is about the new ROM I will flash, I've no idea about what "versions" exists or where I can download them... so is there some kind of "most stable" version using Nougat 7.1.2? or some "ROM Reliable supplier"?
Thanks
jramirezdev said:
Thanks for your response,
I bought my cellphone two years ago so It already went out of warranty so no issues with that step, I already found the guide to "Unlock bootloader" but before I start with it I would like to ask if after that the phone will be unuseful? I mean, after unlocking the bootloader can I start the phone and continue using it? It's my only cell phone so I want to be aware if I will stay long time uncommunicated.
My second question is about the new ROM I will flash, I've no idea about what "versions" exists or where I can download them... so is there some kind of "most stable" version using Nougat 7.1.2? or some "ROM Reliable supplier"?
Thanks
Click to expand...
Click to collapse
Unlocking bootloader will wipe all your data (it will trigger Factory Reset on your phone). Other than that, your phone will be 100% usable.
Roms are available in Android Development and Original Android Development sections of this forum. Just check the threads that include [ROM] in their title. You have to decide for yourself which rom suits you the best - read its description and what users say in comments.
jramirezdev said:
Thanks for your response,
I bought my cellphone two years ago so It already went out of warranty so no issues with that step, I already found the guide to "Unlock bootloader" but before I start with it I would like to ask if after that the phone will be unuseful? I mean, after unlocking the bootloader can I start the phone and continue using it? It's my only cell phone so I want to be aware if I will stay long time uncommunicated.
My second question is about the new ROM I will flash, I've no idea about what "versions" exists or where I can download them... so is there some kind of "most stable" version using Nougat 7.1.2? or some "ROM Reliable supplier"?
Thanks
Click to expand...
Click to collapse
As said, after unlocking bootloader the device will be wiped- You will have to reenter your Google account and reinstall applications etc. Not a big deal.
Custom ROMs sometimes take a few iterations until some bugs here and there are ironed out. Sometimes it happens, in others one may end up switching to a complete fresh ROM. In such instances, you will usually have to make a "clean install" (i.e. a factory reset) and then reenter the Google account and reinstall everything again... It sounds irritating, but nowadays it's pretty much straight forward, and if you don't have hundreds of apps it usually is finalized in 10-15 minutes and is semi automatic.
Updating to a newer version of the same ROM sometimes can be "dirty flashed" (i.e. without wiping all your data) so in a couple of minutes you are set up and ready to go. More convenient, but if something isn't working right and you complain in the thread, certain chances are you will be politely asked to make a clean install first amd some users may flame or grill you alive for dirty flashing and complaining at that :laugh:
Most custom ROMs are usually based on either AOSP or Lineage OS (aka LOS) with some custom modifications. The first post in a ROM thread usually mentions all the rich features (or lack of), how to install (pretty much the same: make a backup in twrp, wipe data/system/cache/dalvik, flash ROM zip file, flash Google gapps zip, flash some additional optional zips such as supersu/magisk/whatever for root etc). Then some download links, faq etc.
It's good practice to read the first post (aka OP), then at least the last page to get a feel of the ROM (e.g. see what others are praising or complaining about this or that), then search for specific stuff that may concern you. For example, some ROMs had this cellular data bug that it got disconnected and required restart. You may decide this os crucial for you and choose another ROM, others may use the device for other things and couldn care less about cellular data bug...
Enjoy, it always feels good tp flash a new ROM, a new version . F!ck LeMoto for delaying the update for so long- You may have been waiting for update to Nougat as early as last year's November or October. Well, on custom ROMs it's here for many months!
On the other hand, they usually say stock ROM is more stable, and in many cases it is also true...
Now you know more or les what you're dealing with: free choice vs. waiting forever.
jaibar said:
As said, after unlocking bootloader the device will be wiped- You will have to reenter your Google account and reinstall applications etc. Not a big deal.
Custom ROMs sometimes take a few iterations until some bugs here and there are ironed out. Sometimes it happens, in others one may end up switching to a complete fresh ROM. In such instances, you will usually have to make a "clean install" (i.e. a factory reset) and then reenter the Google account and reinstall everything again... It sounds irritating, but nowadays it's pretty much straight forward, and if you don't have hundreds of apps it usually is finalized in 10-15 minutes and is semi automatic.
Updating to a newer version of the same ROM sometimes can be "dirty flashed" (i.e. without wiping all your data) so in a couple of minutes you are set up and ready to go. More convenient, but if something isn't working right and you complain in the thread, certain chances are you will be politely asked to make a clean install first amd some users may flame or grill you alive for dirty flashing and complaining at that :laugh:
Most custom ROMs are usually based on either AOSP or Lineage OS (aka LOS) with some custom modifications. The first post in a ROM thread usually mentions all the rich features (or lack of), how to install (pretty much the same: make a backup in twrp, wipe data/system/cache/dalvik, flash ROM zip file, flash Google gapps zip, flash some additional optional zips such as supersu/magisk/whatever for root etc). Then some download links, faq etc.
It's good practice to read the first post (aka OP), then at least the last page to get a feel of the ROM (e.g. see what others are praising or complaining about this or that), then search for specific stuff that may concern you. For example, some ROMs had this cellular data bug that it got disconnected and required restart. You may decide this os crucial for you and choose another ROM, others may use the device for other things and couldn care less about cellular data bug...
Enjoy, it always feels good tp flash a new ROM, a new version . F!ck LeMoto for delaying the update for so long- You may have been waiting for update to Nougat as early as last year's November or October. Well, on custom ROMs it's here for many months!
On the other hand, they usually say stock ROM is more stable, and in many cases it is also true...
Now you know more or les what you're dealing with: free choice vs. waiting forever.
Click to expand...
Click to collapse
Thanks for your thoughts,
After reading here and there I finally was able to flash AOSP Extendend v4.4 on my cellphone, it seems to be working fine.
As I said I was not looking something specific I was just annoyed of waiting so long for the official update (it seems it will never happen) and wants to be in touch with Android Nougat, maybe now I will use my piggy bank to save for a Pixel phone
Thanks guys for your guidance
jramirezdev said:
After reading here and there I finally was able to flash AOSP Extendend v4.4 on my cellphone, it seems to be working fine.
Click to expand...
Click to collapse
Hi,
How it is working? Did you found any bugs? eg. problem with battery, with mobile data, lte, camera?
Hello folks, My friend has a Moto G5 plus and she is also Visually Impaired. There are some issues, with talkback she is having that I am thinking may be 7.0 related, Also there are changes in 8.0 that she really is quite excited about. I am wondering if going to a custom ROM that is an up to date version and will probably hit Oreo before Moto ever gets to it wouldn't help her out, Also some of the custom roms seem to have some feature themselves that might be handy. So I have been researching how to go about this.
Basically what I THINK I want is pretty close to stock and most recent and least buggy version of android., But I know she watches Netflix and other things, so Since I have to root on the G5 to load any rom I believe the only way to do it and maintain things like netflix is with Magisk, Is this correct? So I am looking at Lineage OS or RR, leaning toward Lineage.
There is overwhelming amount of info on this so I want to do this correct, So here is a rough of what I understand the process to be.
First step is to unlock the boot loader
then load latest TWRP 3.1.1.1 custom recovery or is SuperSu better, this one of the parts got me little confused.
Once that is done, this I need to create a Nandroid backup and go ahead an wipe/reset the phone.
From here I use the TWRP recovery to install nstall no-verity-opt-encrypt-5.1.zip"(FLASH IT) and Magisk, and flash "no-verity-opt-encrypt-5.1.zip", correct?
Then Flash Magisk again and allow it to update, is that about right?
Then flash the Rom?
Last but not least flash the GAPPS, of which there seem to be a few to chose from. Still unsure the differences, Thinking just Open GAPPS.
So can anyone tell me does that sound about right? Is there a stupid NewB guide somewhere? Can anyone give me heads up or some of the pitfalls I may have missed or such?
Any help would be awesome.
Most of what I'm reading looks correct. It's been a few months since I rooted mine and I can't remember the exact process but I do remember some of my problems and questions. Make sure you have all files downloaded and copied to your phone. If possible have a backup on a micro SD in case you accidently erased the internal storage. Unlock bootloader, install twrp ( magisk is the way to go for root but several roms don't come prerooted so u can still use wallet, Netflix, etc). I personally didn't install no verity. Install the rom you want and your sound as a pound.
https://www.google.com/amp/s/forum.xda-developers.com/g5-plus/how-to/how-to-root-moto-g5-plus-t3579659/amp/
Thank you. I actually flash Lineage using a youtube video I found that seemed to cover what I needed to know. Things seem to be working well, many of the bugs I seemed to deal with in stock 7.0 rom, one I thought to actually be hardware thing, seem to have vanished and maybe it's just in my mind, but seems to be much more snappy. I haven't tried any apps that I know have issues w/ root and unlocked bootloaders, but sofar so good with most the apps I have tried, in fact some seem to work better.
I just want to say thank you to developers of these roms and all the tools, We really appreciate you.