Related
Hi, I've read that support for LG G3 is in the works but is or will there be support for the G3 running CM12?
I've just tested this, even bought the version from Play store and for me it doesn't work. Is there a Kernel requirement for FM radio which CM12 may not have? I could supply any log data you request.
Thanks and great work so far.
Yup, i confirm, doesn't work on lg g3. Pitty.
joergherzinger said:
Hi, I've read that support for LG G3 is in the works but is or will there be support for the G3 running CM12?
I've just tested this, even bought the version from Play store and for me it doesn't work. Is there a Kernel requirement for FM radio which CM12 may not have? I could supply any log data you request.
Thanks and great work so far.
Click to expand...
Click to collapse
Sorry for my delay. I started a re-coding "marathon" on the weekend and it stretched for a week.
I intend to support the LG G3 as well as I possibly can, on any ROM. I have almost bought a G3 for testing a few times, but haven't gone through with it yet.
The CM12 kernel does not at present include the needed Qualcomm V4L FM radio "IRIS" driver.
I will try to submit the tiny 2 line config file change needed for that and see if they respond.
Someone built an FM friendly kernel and it worked, but there are/were still some audio issues. We can work around this with the new analog mode being added to Spirit2, and this should be properly resolved at some point.
Oh, thats great to hear.
For the Cyanogen part: They actually have a section in their bugtracker for FM Radio [1]. Once you have done that could you post the links to the pull request and the bug entry here. I will follow it and update my phone as soon as the fix is built. If there is anything I can do to help you please let me know.
[1] https://jira.cyanogenmod.org/secure...=+"FM+Radio"+ORDER+BY+priority+DESC&mode=hide
joergherzinger said:
Oh, thats great to hear.
For the Cyanogen part: They actually have a section in their bugtracker for FM Radio [1]. Once you have done that could you post the links to the pull request and the bug entry here. I will follow it and update my phone as soon as the fix is built. If there is anything I can do to help you please let me know.
[1] https://jira.cyanogenmod.org/secure...=+"FM+Radio"+ORDER+BY+priority+DESC&mode=hide
Click to expand...
Click to collapse
OK.
Last night I submitted the same patch for Xperia Z1 and it seems well received. First time I ever built a CM ROM and it took a few days to get everything downloaded and built and figure out how to submit CM patches etc.
My response time to posts and emails has increased, and my responses are more brief, because I have decided to spend more time doing what needs to be done and less time talking about it.
WOW great news!!
Thank's very much :victory:
mikereidis said:
OK.
Last night I submitted the same patch for Xperia Z1 and it seems well received. First time I ever built a CM ROM and it took a few days to get everything downloaded and built and figure out how to submit CM patches etc.
My response time to posts and emails has increased, and my responses are more brief, because I have decided to spend more time doing what needs to be done and less time talking about it.
Click to expand...
Click to collapse
Great! I'm trying CM12 in my G3 and, despite some typical nightly bugs, it's working quite well. I only really miss FM radio! :fingers-crossed:
Any progress ?
ariek44 said:
Any progress ?
Click to expand...
Click to collapse
Is the needed FM driver in the CM12 kernel for LG G3 now ?
And is the remaining problem that the sound sounds horrible ?
See my posts 9001 and 9002 for info on the new March 6 beta release. 9002 has link to the free version to try: http://forum.xda-developers.com/showthread.php?t=1059296&page=901
will not start
mikereidis said:
Is the needed FM driver in the CM12 kernel for LG G3 now ?
And is the remaining problem that the sound sounds horrible ?
See my posts 9001 and 9002 for info on the new March 6 beta release. 9002 has link to the free version to try: http://forum.xda-developers.com/showthread.php?t=1059296&page=901
Click to expand...
Click to collapse
New beta app says no tuner in current cm12 nightly. Tried flashing a different kernel - resin - but same result.
Phenax said:
New beta app says no tuner in current cm12 nightly. Tried flashing a different kernel - resin - but same result.
Click to expand...
Click to collapse
If you have the T-Mobile variant, I do not think FM can ever work for you.
As with the LG G2, only the Sprint and International variants have the FM antenna pin connected as needed to the headset jack for the antenna.
Other variants are purposely and permanently "broken" by shorting the pin to ground.
There was rumor here and there that other variants might work, but I think that was based on Spirit not showing a specific error at one point.
So, AFAICT, only the International D855 and Sprint's model.
joergherzinger said:
Hi, I've read that support for LG G3 is in the works but is or will there be support for the G3 running CM12?
I've just tested this, even bought the version from Play store and for me it doesn't work. Is there a Kernel requirement for FM radio which CM12 may not have? I could supply any log data you request.
Thanks and great work so far.
Click to expand...
Click to collapse
I have built a CM12 based kernel that I think should work.
I do not have a G3 so I can not test it.
I can not make any guarantees that it will boot and won't harm anything.
This is a boot.img file. Anyone flashing it should understand how to flash such a file so I won't explain.
I will submit the patches to CM once someone can verify.
md5sum ~/mikes_boot_fm_12-20150307-UNOFFICIAL-d855.img
d8080528d3f37448e57a6da84162d4df
Thanks !
Genius, it works. Sound quality seems fine to me. Just send me the link to the patch you will send in and I can confirm the cm guys, that it is working if you want.
Edit: I just noticed that wake up by double tap does not work. I assume that just because you used a different kernel config to the stock cm one...
joergherzinger said:
Genius, it works. Sound quality seems fine to me. Just send me the link to the patch you will send in and I can confirm the cm guys, that it is working if you want.
Edit: I just noticed that wake up by double tap does not work. I assume that just because you used a different kernel config to the stock cm one...
Click to expand...
Click to collapse
Great !
I did not touch the kernel config at all. I used this one, stock as of this morning, AFAICT: https://github.com/CyanogenMod/andr...0/arch/arm/configs/cyanogenmod_d855_defconfig
The config has this, unchanged:
Code:
CONFIG_RADIO_IRIS=y
CONFIG_RADIO_IRIS_TRANSPORT=y
All I did to patch/fix was this:
Code:
cp kernel/motorola/msm8226/drivers/media/radio/radio-iris-transport.c kernel/lge/g3/drivers/media/radio/radio-iris-transport.c
cp kernel/motorola/msm8226/drivers/media/radio/radio-iris.c kernel/lge/g3/drivers/media/radio/radio-iris.c
This copied the Qualcomm fix from the MotoG kernel source that allows radio-iris-transport to work built into the kernel, instead of only as a module.
joergherzinger said:
Genius, it works. Sound quality seems fine to me. Just send me the link to the patch you will send in and I can confirm the cm guys, that it is working if you want.
Click to expand...
Click to collapse
Patch is here: http://review.cyanogenmod.org/#/c/90794/
I played around with it a bit more. FM worked like a charm, but several other things didn't work at all. Most importantly Settings crashed for me when I tried to open display settings. I assume that is because my CM is a little more than a week old while your build is just a few days old. I reverted by to my old boot.img but I will test the first nightly with your patch in it.
joergherzinger said:
I played around with it a bit more. FM worked like a charm, but several other things didn't work at all. Most importantly Settings crashed for me when I tried to open display settings. I assume that is because my CM is a little more than a week old while your build is just a few days old. I reverted by to my old boot.img but I will test the first nightly with your patch in it.
Click to expand...
Click to collapse
Maybe.
I've seen Settings crash on a few devices/ROMs.
Common AOSP Lollipop ROMs still have lots of problems.
They ALL have a nasty memory leak that gets bigger every time Spirit sends an RDS update to notification shade/remotes/lockscreen. I have to reboot my test phones every day or so to avoid unpredictable restarts when Android system_server fills its' internal table maxed at 51,200.
Stock Lollipop ROMs don't have this problem, so IMO must be some common bug in CM12 I think. (I could/should verify if Nexus/pure AOSP shares this.)
Well, it doesn't look too good. They seem to want this as a loadable module, which you explicitly stated different in your commit message. Any ideas an what to do next?
joergherzinger said:
Well, it doesn't look too good. They seem to want this as a loadable module, which you explicitly stated different in your commit message. Any ideas an what to do next?
Click to expand...
Click to collapse
Yes, I think so, it's just taking me a long time to do it.
The patches I provided WORK. The complaint was that IF they re-configure the kernel to use modules, then the kernel will not build and he did not like that.
Many kernels have removed modules now and it is rare to go back to modules, so I find this a bit strange, but I am not the one maintaining kernels.
The patches were not really "developed" by me. I just grabbed the very similar files from the MotoG CM12 kernel thinking they would not complain; it was just aligning the code between CM12 kernels.
My plan since the patches were rejected is to use the files from (I think) a Sony CM12 kernel that I think should work with or without modules.
But I have had a LOT of trouble getting d855 kernels and ROMs to build since my initial changes that worked AND it can take hours to build a new ROM and I still have not figured out how to build just the kernel, which is much faster.
This is the problem I had last night and the night before and I am not a ROM dev so it takes time for me to figure out what is wrong or how to fix (maybe a "make clean" or similar"):
creating userdata.img...
Running: mkf2fsuserimg.sh /tmp/tmpqdNGFw 12297699328
in mkf2fsuserimg.sh PATH=/home/m/android/system/out/host/linux-x86/bin:/usr/lib/jvm/java-1.7.0-openjdk-amd64/bin:/home/m/android/system/out/host/linux-x86/bin:/home/m/android/system/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin:/home/m/android/system/prebuilts/gcc/linux-x86/:/home/m/android/system/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin:/home/m/android/system/development/scripts:/home/m/android/system/prebuilts/devtools/tools:/home/m/android/system/prebuilts/android-emulator/linux-x86_64:/home/m/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/jvm/jdk1.8.0_25/bin:/home/m/b:/home/m/b/android-studio//bin/:/home/m/b/android-sdk//platform-tools/:/home/m/b/android-sdk//tools/:/home/m/b/android-sdk//build-tools/21.1.2/:/home/m/b/android-ndk-r10//build/tools/:/home/m/b/android-ndk-r10//
make_f2fs -l 12297699328 /tmp/tmpqdNGFw
/home/m/android/system/out/host/linux-x86/bin/mkf2fsuserimg.sh: line 31: 23180 Segmentation fault $MAKE_F2FS_CMD
Traceback (most recent call last):
File "./build/tools/releasetools/add_img_to_target_files", line 261, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/add_img_to_target_files", line 255, in main
AddImagesToTargetFiles(args[0])
File "./build/tools/releasetools/add_img_to_target_files", line 241, in AddImagesToTargetFiles
AddUserdata(output_zip)
File "./build/tools/releasetools/add_img_to_target_files", line 156, in AddUserdata
assert succ, "build userdata.img image failed"
AssertionError: build userdata.img image failed
make: *** [/home/m/android/system/out/target/product/d855/obj/PACKAGING/target_files_intermediates/cm_d855-target_files-079aa1bcfa.zip] Error 1
make: *** Deleting file `/home/m/android/system/out/target/product/d855/obj/PACKAGING/target_files_intermediates/cm_d855-target_files-079aa1bcfa.zip'
Click to expand...
Click to collapse
With troubles like these, and ROM builds taking hours and my lack of a G3 to test, this is moving slowly.
Add the fact that I am exhausted from the last few months of MORE major changes to Spirit2, some time spent with my family and looking into Android Auto and things move even more slowly.
...And the build guide for G3 seems to have disappeared too: http://wiki.cyanogenmod.org/w/Build_Guides#vendor=%22LG%22;
...And... any chance you know the OFFICIAL CM12 way of switching between module and non-module kernels ? I know the defconfig "CONFIG_MODULES=y" thing, but I'm not sure if other changes are needed. I can do a "make menuconfig" but I'm not sure if I should write .config to the defconfig. "make config" gives a million options; I tried that and produced a kernel that probably won't even boot on a G3.
Perhaps I should post in a G3 forum section asking for help.
I posted on that patch now: http://review.cyanogenmod.org/#/c/90794/
Hi, I don't understand half you are talking about
I'm just an user who wants CM12 and FmRadio.
That being said, I can read this changelog in 777 kernel thread (http://forum.xda-developers.com/lg-g3/development/kernel-777-kernel-t3003115). Did anyone try this "radio" builds?
02/08/15
- R6
- Fix Powersuspend
- CM kernel updates
- Synaptic touch firmware update
- Separate d855 builds with fm radio module
Click to expand...
Click to collapse
(EDIT: Tried by myself. Radio works with 777 kernel. However, audio quality is quite bad.)
Second, I would like to test any beta kernels, spirit app, or whatever in my G3 D855, in order to help making it work. Please tell me how can I do it.
Thank you very much!
The A7U with MM (as I have modified it) has been very satisfactory, but I continue to debate over the upgrade to N7.0.
I did try some early Nougat versions on the old Nexus 5 and a Samsung tablet and ended up reverting back due to various performance issues, but that was a while ago.
Also, some here have reported problems either with the process or with the function of the end resut, so I am looking for some recommendations pro or con about making the move to B15.
Thanks
amphi66 said:
The A7U with MM (as I have modified it) has been very satisfactory, but I continue to debate over the upgrade to N7.0.
I did try some early Nougat versions on the old Nexus 5 and a Samsung tablet and ended up reverting back due to various performance issues, but that was a while ago.
Also, some here have reported problems either with the process or with the function of the end resut, so I am looking for some recommendations pro or con about making the move to B15.
Thanks
Click to expand...
Click to collapse
I'm on N and the only reason im on N is because ZTE fixed the VoLTE and its not roaming on Verizon any more. Pretty much works as it should and acts just like a Verizon device which is impressive, because we never get to play with unlocked devices on Verizon.
Now to the actual B15 stuff. Its a bit more laggy then MM and a few apps are pretty much unusable on N. Those are WhatsApp and LinkedIn on my device. I think I've seen another one or two somewhere else.
Camera is definitely better for me. Battery is great for me but it was great before the update.
Pretty sure im forgetting a few things. Overall im happy with the device and even happier that VoLTE works now.
7.1.1 should be out soon, hopefully that takes care of these few issues.
All of this is covered in the nougat thread.
Seeing a higher build number in About Device
lafester said:
All of this is covered in the nougat thread.
Click to expand...
Click to collapse
Thanks for your typical, cryptic response. I see lot of ROM threads and conflicting guides, but certainly no "Nougat thread". Can you offer a link?
Regards.
amphi66 said:
Thanks for your typical, cryptic response. I see lot of ROM threads and conflicting guides, but certainly no "Nougat thread". Can you offer a link?
Regards.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3552251
This is the thread that was started when nougat was released.
It mostly covers flashing issues but there is feedback as well.
You can also read the zte forum for lots of N opinions, probably more then anyone could ever need.
Personally I think its ok, but only with custom kernel to speed it up. Hoping 7.1.1 will be better.
lafester said:
https://forum.xda-developers.com/showthread.php?t=3552251
This is the thread that was started when nougat was released.
It mostly covers flashing issues but there is feedback as well.
You can also read the zte forum for lots of N opinions, probably more then anyone could ever need.
Personally I think its ok, but only with custom kernel to speed it up. Hoping 7.1.1 will be better.
Click to expand...
Click to collapse
Thanks, hadn't seen it & gave it a read. I loaded Stock (rooted) 7.0 and found it fine. Perhaps a touch slower than MM, but certainly no noticeable problems (or benefit).
I had Substratum working 98% (including Android System) in MM so missed the darker theme. Also TB was unable to see its archive on the extSDcard, although worked fine when I moved it to the internal storage.
Also tried RR, but couldn't get Gapps to install over the ROM (TWRP errors: either unsupported device or incompatible ROM errors), so reverted back to B29 for now.
I saved a TWRP BU of B15 w/ all data for a starting point when 7.1 is released.
So, from searching this forum it seems like people think the V20 doesn't support Treble. I've seen articles that state with Oreo it will. I am running the unofficial Los 15.1 build and downloaded the app that checks for Treble compatibility and it states my phone is treble ready though I don't have the A/B setup. Now looking at treble project builds there are many that state they are a only as well as a/b.
So, is the rooted v20 treble ready with Oreo firmware?
Also, when I do this cmd in terminal - getprop ro.treble.enabled, it returns true.
Is it possible, yes, will they do it, probably not.
You can set the boot LUN now, without Oreo, and force the phone to boot from the *bak partitions (xblbax, abootbak, lafbak, recoverybak, etc)
Notice there is one important partition missing .. bootbak. We don't have it. That would require the phone to be repartitioned, and I just don't see LG risking that.
It is hard enough to repartition a UFS NAND via a firehose, it would be insane to try it via an OTA update.
-- Brian
Thanks Brian. Guessing these treble check apps should have a big warning plastered on them for the less savvy in the android intricacies such as myself. Glad I posted before going ham on trying to install Treble roms
Actually we have xbl2 and xbl2bak that could be repurposed. They aren't actually used as part of the boot process (they are identical copies of xbl and xblbak).
However, that still leaves system. In order to have a systembak, they would have to shrink userdata which is currently 52.2G, so plenty of room, but that is VERY risky.
Again, though, this is very doable. Heck, even if they don't do it, the AOSP builds for the V20 could support it with the tweaks stated above.
-- Brian
runningnak3d said:
Actually we have xbl2 and xbl2bak that could be repurposed. They aren't actually used as part of the boot process (they are identical copies of xbl and xblbak).
However, that still leaves system. In order to have a systembak, they would have to shrink userdata which is currently 52.2G, so plenty of room, but that is VERY risky.
Again, though, this is very doable. Heck, even if they don't do it, the AOSP builds for the V20 could support it with the tweaks stated above.
-- Brian
Click to expand...
Click to collapse
So, does the V30 have all these partitions set up? It's my understanding that the V30 is definitely going to be treble supported so I'm curious if it already has these partitions in place or needs modifying (in which case I imagine some crafty bastard will be able to replicate the process).
Or along those lines, several of the supported current phones I don't believe shipped with Oreo so they had to undergo the reformatting process, I wonder if there's anything to glean from them. I'll have to see if I can wrap my head around this whole deal.
Also, is this what we are lacking? https://forum.xda-developers.com/pr.../tool-capire-le-treble-terble-vendor-t3774629
Wow, I should really drink at least 3 cups of coffee before posting.
What I was referring to was A/B system updates which I swore had a code name, but damn if I can find it now.
Anyway, yes, even Project Treble will still require repartitioning since we don't have a vendor partition (vendor is on system). Much easier to implement than A/B system updates, but I still don't think LG will do it.
We will just have to wait and see...
EDIT: good read on A/B system updates: https://source.android.com/devices/tech/ota/ab/ab_implement
-- Brian
LG may not add /vendor partition, but if you put the pieces together from some of the posts around the dev section theres work being done to add one in Lineage, though it hasnt been done yet.
runningnak3d said:
Anyway, yes, even Project Treble will still require repartitioning since we don't have a vendor partition (vendor is on system).
Click to expand...
Click to collapse
Just FWIW, Treble doesn't necessarily require repartitioning.
PhantomGamers said:
Just FWIW, Treble doesn't necessarily require repartitioning.
Click to expand...
Click to collapse
i've been following project treble for sometimes and there are lot of misunderstanding
1. having custom oreo roms doesnt mean you had treble support. it is true most treble phone coming with oreo by default
2. even if your phone has official oreo rom doesnt mean it support treble project ( like samsung S8 or note 8)
3. there are some devices with unnoficial treble support like oneplus devices but it still in development and as brian said we need repartition and needs lot of work. and your link above still on experiment.
i didnt say its impossible, but its far away for our devices not to mention we still need to dealing with ARB and lafs. just hope more devs joining on LG development and not rush them ( i saw lot of people doing that on brian's thread) . remember they did it for free while risking their devices on the process.
Loopback mounting is by far the safest method. You mess that up, and you phone just doesn't load the OS. You try and shrink a partition, and you mess up, and you could be toast. It isn't just shrinking, you also have to add a new entry to the GPT .. that is dangerous.
Also, if you do succeed, you will never be able to flash a stock ROM unless you put things back. For one thing stock system would no longer fit
-- Brian
What about this
www.getdroidtips.com/lg-v20-android-9-0-pie/
walidham said:
What about this
www.getdroidtips.com/lg-v20-android-9-0-pie/
Click to expand...
Click to collapse
Has someone tried this? Sorta feels like he just took that article and just keeps adding phone models to it without trying it.
walidham said:
What about this
www.getdroidtips.com/lg-v20-android-9-0-pie/
Click to expand...
Click to collapse
I saw that article -- and had also come across phhusson treble_experimentations on github -- and am also wondering if anyone has tried it for the LG V20, in particular the H918. LG V20 is not listed in the vendor-HAL directory of the github repo. I'd love to hear from anyone who has tried this with the H918.
stcr1 said:
I saw that article -- and had also come across phhusson treble_experimentations on github -- and am also wondering if anyone has tried it for the LG V20, in particular the H918. LG V20 is not listed in the vendor-HAL directory of the github repo. I'd love to hear from anyone who has tried this with the H918.
Click to expand...
Click to collapse
you can't just grab random drivers (that's what these HALs are) and hope they fit your device. x86cpu got close to a working treble implementation, but LG's camera drivers wern't compatible and has since put off that project and is working more on lineage 16 (pie). IF LG ever does release a stock version of pie, perhaps a newer version of the camera driver might be compatible, but perhaps not.
Phoenix591 said:
you can't just grab random drivers (that's what these HALs are) and hope they fit your device. x86cpu got close to a working treble implementation, but LG's camera drivers wern't compatible and has since put off that project and is working more on lineage 16 (pie). IF LG ever does release a stock version of pie, perhaps a newer version of the camera driver might be compatible, but perhaps not.
Click to expand...
Click to collapse
OK. Got it. So it seems that LG is going to give the V20 a Pie update. There are announcements to that affect. Assuming LG follows through, the Pie update may or may not be Treble compatible. With Oreo, device OEMs were required (??) to be Treble compatible on new Oreo devices, but could provide non-Treble Oreo updates to existing devices. That's what I gathered. So with Pie, what you are saying is that it will be the same: OEMs are not necessarily going to package Treble support in Pie updates to existing devices. But if LG does provide a Pie update, AND if the update is Treble compatible, then things will be easy-peasy for ROM developers to port their wares to it because drivers -- like the troublesome camera driver -- will be abstracted and basically have the same abstraction across all Android devices. Is that right?
stcr1 said:
OK. Got it. So it seems that LG is going to give the V20 a Pie update. There are announcements to that affect. Assuming LG follows through, the Pie update may or may not be Treble compatible. With Oreo, device OEMs were required (??) to be Treble compatible on new Oreo devices, but could provide non-Treble Oreo updates to existing devices. That's what I gathered. So with Pie, what you are saying is that it will be the same: OEMs are not necessarily going to package Treble support in Pie updates to existing devices. But if LG does provide a Pie update, AND if the update is Treble compatible, then things will be easy-peasy for ROM developers to port their wares to it because drivers -- like the troublesome camera driver -- will be abstracted and basically have the same abstraction across all Android devices. Is that right?
Click to expand...
Click to collapse
LG released oreo without treble support, LG releasing a pie update for the V20 is doubtful at best and if they do it more than likely it won't have treble support either
Sent from my LG-H910 using XDA Labs
walidham said:
What about this
www.getdroidtips.com/lg-v20-android-9-0-pie/
Click to expand...
Click to collapse
warwagon19792 said:
Has someone tried this? Sorta feels like he just took that article and just keeps adding phone models to it without trying it.
Click to expand...
Click to collapse
stcr1 said:
I saw that article -- and had also come across phhusson treble_experimentations on github -- and am also wondering if anyone has tried it for the LG V20, in particular the H918. LG V20 is not listed in the vendor-HAL directory of the github repo. I'd love to hear from anyone who has tried this with the H918.
Click to expand...
Click to collapse
I did know of someone who tried this. And it seemed to work but it never passed from the booting animation screen. He tried to go back and the phone was rendered useless. (and he was a developer). SOOOOO no.... I don't recommend attempting this.
Folks,
I finally decided to go for LineageOS 16.0 on my Moto G5+ and i am currently on the stock Oreo firmware. I have tried multiple methods to ensure that TWRP sticks (as described in various threads) but so far it doesn't seem to work. I think it would be great if one of you could put together a fresh post on how to get this done including the links to the custom TWRP images (if needed), Magisk etc. Otherwise there are just too many conflicting threads out there. Can someone help?
Thanks a ton in advance.
I literally just did this to my stock 8.1 RETUS and it was a little scattered around, but manageable to do. Here are some links that I used that may help:
1. These are the correct steps to follow in order still https://forum.xda-developers.com/g5-plus/how-to/how-to-root-moto-g5-plus-t3579659
2. This is a pretty decent video showing the above steps https://www.youtube.com/watch?v=0fGmDNZxn2g
All I can say that is really different from the provided links I gave you is: make sure you are using the latest stable version of magisk (v17.1), and I used the "lazyflasher file" from the youtube video instead of the "no verify" file from the xda post. I think I did this because I the link to the xda file no longer worked? And I also used the latest TWRP 3.2.2? But like I said, this is all actually pretty simple in the end. I haven't rooted a phone since my Note 3 with KNOX LOL. Hope I helped, feel free to ask questions.
Hi,
I'm looking to root G7:
Model - XT1962-6
Software - retin
Build - QPUS30.52-16-2-7-7
I simply want to get LineageOS with TWRP and Root. I have searched but have not found anything related to my model. I don't want to brick the device so if anyone can assist me by directing to the correct method, it will be a great help!
Thanks in advance
Hi dcybergeek,
Welcome. I have the exact same than that you do. I started here looking to do a twrp/magisk root like I did back with my Motp G5 Plus...was np prob find everyone did it. NOT SO for our plain G7. Being a novice, I gave up.
Now I drop to look and ask (beg) to see if anyone knows of magisk root...with or without using twrp if need be. The silence has been deafening...no yes or no or maybe...after nearly begging.
No pne could be bothered to give a simple reply...over n over as can be seen all over! And I thought was THE PLACE on to net for help, but no.
Luckily YES...Lineage 17.1 does work on our phone!! I'm about to just give up on on findi ANY FORM of a Magisk root, I guess.
Simply go hrre:
[OFFICIAL] [NIGHTLIES] LineageOS 17.1
Moto g7 - Your warrenty is now void. - You have been warned. - Use at your own risk. Introduction: This is the Official Lineage OS 17.1 thread for the Motorola Moto g7, codename river. How to Install: Please follow the...
forum.xda-developers.com
and
Motorola moto g7 - LineageOS 17.1
LineageOS 17.1 Changelog for Motorola moto g7 (river). This page is listing the official LineageOS 17.1 (Android 10 10.0) changes and downloads for Motorola moto g7 (river).
www.lineageoslog.com
or
Download and Install Lineage OS 17.1 for Motorola Moto G7 based on Android 10 Q
Finally, Android 10 Q is official and so the AOSP 10 Source code. Motorola Moto G7 (river) is now getting the official version of Lineage OS 17.1
www.getdroidtips.com
Plenty of help...unless you wanna do a twrp + magisk root...no one will even bother to confirm OR deny anything u ask.The following guide looks good but I can't gey ANY of the XDA Pros to respond! Smdh...
Moto G7/G7 Plus Guide: Unlock Bootloader, Install TWRP, and Root with Magisk
In this guide, we will show you how to unlock the bootloader, install TWRP recovery, and subsequently root the Moto G7 and Moto G7 Plus using Magisk. The instructions will work on any Moto G7 or G7…
www.thecustomdroid.com
I hope all work out for you. I gotta buy a diff. phone if I want a magisk root...I think but not sure. Looks like a usedPixel 3 XL or a used Pixel 4a.
Cheers...
Zaxx32 said:
Hi dcybergeek,
Welcome. I have the exact same than that you do. I started here looking to do a twrp/magisk root like I did back with my Motp G5 Plus...was np prob find everyone did it. NOT SO for our plain G7. Being a novice, I gave up.
Now I drop to look and ask (beg) to see if anyone knows of magisk root...with or without using twrp if need be. The silence has been deafening...no yes or no or maybe...after nearly begging.
No pne could be bothered to give a simple reply...over n over as can be seen all over! And I thought was THE PLACE on to net for help, but no.
Luckily YES...Lineage 17.1 does work on our phone!! I'm about to just give up on on findi ANY FORM of a Magisk root, I guess.
Simply go hrre:
[OFFICIAL] [NIGHTLIES] LineageOS 17.1
Moto g7 - Your warrenty is now void. - You have been warned. - Use at your own risk. Introduction: This is the Official Lineage OS 17.1 thread for the Motorola Moto g7, codename river. How to Install: Please follow the...
forum.xda-developers.com
and
Motorola moto g7 - LineageOS 17.1
LineageOS 17.1 Changelog for Motorola moto g7 (river). This page is listing the official LineageOS 17.1 (Android 10 10.0) changes and downloads for Motorola moto g7 (river).
www.lineageoslog.com
or
Download and Install Lineage OS 17.1 for Motorola Moto G7 based on Android 10 Q
Finally, Android 10 Q is official and so the AOSP 10 Source code. Motorola Moto G7 (river) is now getting the official version of Lineage OS 17.1
www.getdroidtips.com
Plenty of help...unless you wanna do a twrp + magisk root...no one will even bother to confirm OR deny anything u ask.The following guide looks good but I can't gey ANY of the XDA Pros to respond! Smdh...
Moto G7/G7 Plus Guide: Unlock Bootloader, Install TWRP, and Root with Magisk
In this guide, we will show you how to unlock the bootloader, install TWRP recovery, and subsequently root the Moto G7 and Moto G7 Plus using Magisk. The instructions will work on any Moto G7 or G7…
www.thecustomdroid.com
I hope all work out for you. I gotta buy a diff. phone if I want a magisk root...I think but not sure. Looks like a usedPixel 3 XL or a used Pixel 4a.
Cheers...
Click to expand...
Click to collapse
Hi Zaxx32 , thanks for putting this up for me.
True that regarding the pixel 4a. I am thinking of moving on to that or even if I could get a better deal on the 3a.
I am still thinking to try out these guides. Worse scenario, dead phone and a chance to buy a new one
Update for someone else if looking for help/advice:
The LineageOS 17.1 nightlies works well. Managed to install Lineage OS 17.1 from XDA with TWRP. Next up will try Magisk and share the progress
I wish u the best of luck...unfortunately, you're gonna need it...esp if u have questions. When I asked just the BASIC question 'if river could successfully be magisk rooted via twrp now that a new version of twrp for river had been released?'...the silence was...still, deafening. Either there are still issues or it now works but those who know how have taken an oath os secrecy OR they just can't be bothered to help those of us stil 'learning android'...I dunno which! My point being...if it doesn't work...JUST SAY SO! lol
Zaxx32 said:
I wish u the best of luck...unfortunately, you're gonna need it...esp if u have questions. When I asked just the BASIC question 'if river could successfully be magisk rooted via twrp now that a new version of twrp for river had been released?'...the silence was...still, deafening. Either there are still issues or it now works but those who know how have taken an oath os secrecy OR they just can't be bothered to help those of us stil 'learning android'...I dunno which! My point being...if it doesn't work...JUST SAY SO! lol
Click to expand...
Click to collapse
Thanks, could be the model is getting old. Hence the support is dying? But yea myself too didn't expect that from XDA.
dcybergeek said:
Thanks, could be the model is getting old. Hence the support is dying? But yea myself too didn't expect that from XDA.
Click to expand...
Click to collapse
Yes, that adds as a contributing factor. But I think it's still well-supported (at least for now).
Anyways, back to your original question. The first thing you need is to unlock the bootloader.
But before that:
1) Take a backup as everything will be erased during bootloader unlock.
2) Download and set up Android SDK platform-tools on your computer.
Omg...DJBhardwaj...do you know how to root the G7 via twrp + Magisk??
DJBhardwaj said:
Yes, that adds as a contributing factor. But I think it's still well-supported (at least for now).
Anyways, back to your original question. The first thing you need is to unlock the bootloader.
But before that:
1) Take a backup as everything will be erased during bootloader unlock.
2) Download and set up Android SDK platform-tools on your computer.
Click to expand...
Click to collapse
I have unlocked, twrp with magisk on Lineage already.
But tbh it cannot be used as a daily driver
Zaxx32 said:
Omg...DJBhardwaj...do you know how to root the G7 via twrp + Magisk??
Click to expand...
Click to collapse
Yes, it's quite easy if you know the right steps.
dcybergeek said:
I have unlocked, twrp with magisk on Lineage already.
But tbh it cannot be used as a daily driver
Click to expand...
Click to collapse
Have you tried other available ROMs?
What issues are you exactly facing with LOS 17.1? Are there any known bugs?
DJBhardwaj said:
Yes, it's quite easy if you know the right steps.
Click to expand...
Click to collapse
That's what I was thinking...and is why I got my unlock but just can't pull the trigger cuz I'm not 100% confident I have the order correct. Been searching even harder since the latest twrp releases but no two guides are the same!! ...and I can't risk bricking my phone. Is there anyway I could convince you to show me the correct order/steps? I'd be happy to compensate you for your time...
Zaxx32 said:
That's what I was thinking...and is why I got my unlock but just can't pull the trigger cuz I'm not 100% confident I have the order correct. Been searching even harder since the latest twrp releases but no two guides are the same!! ...and I can't risk bricking my phone. Is there anyway I could convince you to show me the correct order/steps? I'd be happy to compensate you for your time...
Click to expand...
Click to collapse
IMO, always be ready for a brick when dealing with such things for the first time. It's not like it's bound to happen, but it could. Especially with all the confusion because of all the different tutorials out there.
Rooting/TWRP/ROMs only deal with non-critical partitions, so even if it gets brick, you can easily recover.
LOL no, please. No need to compensate for anything. It's a public forum, and we all are here voluntarily.
Just hit me up on PM, Telegram, or Discord.
Gotcha. I only recently lost my 'root-cherry' to my G5+ which was a great first root but I didn't do my homework re: the' seamless' update system that google said would be a requirement moving forward..(then back-tracked on it in short order..). So my single slot learning experience was pretty straight forward...but reading all the posts on the G7 left my head spinning. I'll hit you tomorrow via PM if that's ok cuz I have to use the on-screen keyboard as I lack the dexterity to type/use a normal kb...1 clk per character is too damn slow for real-time chat...lmao Ttys...and thank you for sharing your brain-power! Gonna do my backups and transfer everything to the pc tonight. Thx again...
Zaxx32 said:
Gotcha. I only recently lost my 'root-cherry' to my G5+ which was a great first root but I didn't do my homework re: the' seamless' update system that google said would be a requirement moving forward..(then back-tracked on it in short order..). So my single slot learning experience was pretty straight forward...but reading all the posts on the G7 left my head spinning. I'll hit you tomorrow via PM if that's ok cuz I have to use the on-screen keyboard as I lack the dexterity to type/use a normal kb...1 clk per character is too damn slow for real-time chat...lmao Ttys...and thank you for sharing your brain-power! Gonna do my backups and transfer everything to the pc tonight. Thx again...
Click to expand...
Click to collapse
Sure. I will try and help as much as possible. It was confusing at first to me as well, but I managed to wrap my head around with enough reading (thanks to some awesome members of the community).
No doubt...I was 'mentored' thru my first root by Wolfcity. The kicker was I'd never used a smart phone til about 8 months b4. Always been a Windows Desktop PC guy n feature phone (burner) user. Leaned a lot...quickly..lol
Ttys...need some rest atm.
DJBhardwaj said:
Have you tried other available ROMs?
What issues are you exactly facing with LOS 17.1? Are there any known bugs?
Click to expand...
Click to collapse
Bugs I am facing are hangs some random times. Plus K-9 does not seem to be working well. I delete mails but on desktop it still shows.
dcybergeek said:
Bugs I am facing are hangs some random times. Plus K-9 does not seem to be working well. I delete mails but on desktop it still shows.
Click to expand...
Click to collapse
Have you tried shifting to a custom kernel? Are all users of LOS 17.1 facing sudden hangs?
As for K-9, I believe it's more related to syncing issues. It could be that the K-9 app is not able to run background sync.
Zaxx32 as stated above by both me and DJBhardwaj the very best rather than PM, offsite links would be to go through any XDA related thread.
I understand you are looking for root on stock and not lineage and or any other roms.
If it is to regain privacy I still recom you simply go lineage and or other rom.
And if you still want to root on stock, then there is a high chance it won't work based on the -6 model you own. The best I would suggest is disable unwanted apps if unable to delete. Keep google to the bare minimum (do not sync them all). Use unrooted adblockers, set permissions accordingly and set custom dns under network settings.
DJBhardwaj said:
Have you tried shifting to a custom kernel? Are all users of LOS 17.1 facing sudden hangs?
As for K-9, I believe it's more related to syncing issues. It could be that the K-9 app is not able to run background sync.
Click to expand...
Click to collapse
I cannot speak for them all, but yes I too suspect kernal issue as the lineage is supported for my -6 model but I suppose not to a full 100%. Other than this, I am not facing any hard errors just sometimes random freezes for 2-3 seconds but to me it is bearable.