Database Users

[Q] Support for LG G3 with Cyanogenmod 12?

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!

Stock Recovery and possibly Kernel for XT1621 needed

Hello! So, I'm going to update from MM to N. I have TWRP and ElementalX installed and I wondered if any of you have the flashable zips or img's of the stock Marshmallow 6.0.1 for the XT1621 or another working ver.
I know I could download the firmware and just flash the both of them but my internet is not capable of downloading large files. I want to say that I have backed up the "Boot" partition with TWRP before flashing ElementalX but I don't know if this could help. I'm sorry if these files where to be found in this forum since I can't find them.
Thank you in advance! I would love if you could help me!
EDIT: I couldn't update to Nougat officially. As I said, I used Xposed, and some other apps that modify the System Partition. I found a Lineage OS ROM that had everything I wanted, in Nougat. It's working perfectly now! The battery life is so much better! If you want a link, PM me. I'll be pleased!

Restore backup of Boot,
Download recovery from here : https://moto.shreps.fr/?dir=Moto G4 (athene)/recovery

__Madddy said:
Restore backup of Boot,
Download recovery from here : https://moto.shreps.fr/?dir=Moto G4 (athene)/recovery
Click to expand...
Click to collapse
Thank you so much! Is it indifferent if I download any of the recovery_stock files? They have the same name

polykiwi316 said:
Thank you so much! Is it indifferent if I download any of the recovery_stock files? They have the same name
Click to expand...
Click to collapse
They don't have same name !!
Read complete name, rotate your phone to landscape..

__Madddy said:
They don't have same name !!
Read complete name, rotate your phone to landscape..
Click to expand...
Click to collapse
I missed two digits, sorry for bothering and thank you again! Stock kernel and recovery working!

polykiwi316 said:
I missed two digits, sorry for bothering and thank you again! Stock kernel and recovery working!
Click to expand...
Click to collapse
I can only stock recovery image no stock kernel.....Are those in the image

Ayan0 said:
I can only stock recovery image no stock kernel.....Are those in the image
Click to expand...
Click to collapse
I'll give you my backup ASAP.
I couldn't update to the official N. I downloaded a Nougat ROM instead (lineage OS, working better than stock). If you want the link just tell me! ????

Ayan0 said:
I can only stock recovery image no stock kernel.....Are those in the image
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B2roAcfgEAbxcjVpNEtzR1BKSjA
There you go!
This is for the Moto G4 I specified up there! Keep in mind this might not work in a different model, good luck! :highfive:

Dumb Question
Hello, I am new to XDA, and I've been looking all over the internet for the answer to the following question: Is the Moto G4 XT1621 same or similiar to other models on XDA? i.e, I have a Moto G4 XT1621 but all I see is ROMs for XT1641 or higher, even if they are the same. Can't even find root for this phone. I know the phone code is same (ATHENE) but I don't want to jump ahead and try and so something when I may not have the community's support for rooting, custom ROMs etc..
Can someone just help me by letting me know if flashing TWRP for Athene would work on XT1621 (RetLA, DualSIM) as it would on an XT164x etc. Thanks.
PS: if on the wrong thread please direct me to the correct one, there's not much info on the main G4 Menu...

mgk3431 said:
Hello, I am new to XDA, and I've been looking all over the internet for the answer to the following question: Is the Moto G4 XT1621 same or similiar to other models on XDA? i.e, I have a Moto G4 XT1621 but all I see is ROMs for XT1641 or higher, even if they are the same. Can't even find root for this phone. I know the phone code is same (ATHENE) but I don't want to jump ahead and try and so something when I may not have the community's support for rooting, custom ROMs etc..
Can someone just help me by letting me know if flashing TWRP for Athene would work on XT1621 (RetLA, DualSIM) as it would on an XT164x etc. Thanks.
PS: if on the wrong thread please direct me to the correct one, there's not much info on the main G4 Menu...
Click to expand...
Click to collapse
It will work just fine, the process for flashing TWRP is the same for all xt16xx models.
After flashing TWRP you can flash a custom kernel like ex kernel and root your phone using any method for it.
Take a look over here
https://forum.xda-developers.com/showthread.php?t=3587918
Enviado desde mi Moto G⁴ #StayUnbeaten

syverman said:
It will work just fine, the process for flashing TWRP is the same for all xt16xx models.
After flashing TWRP you can flash a custom kernel like ex kernel and root your phone using any method for it.
Take a look over here
https://forum.xda-developers.com/showthread.php?t=3587918
Enviado desde mi Moto G⁴ #StayUnbeaten
Click to expand...
Click to collapse
Thank you! I haven't rooted or flashed anything yet on my Xt1621, as I got a XT1687 and got to play with it.
Sent from my Moto G5 Plus (XT1687)
✓ PureExperience 8.1.0
✓ Cricket Wireless LTE
✓ TWRP 3.2.0
on TapaTalk

7.1.2 Dirty Unicorns Rom

This is just a heads-up about a 7.1.2 Rom by Anderson Mendes. Saw it somewhere and downloaded it, works very well. You need to flash a zip called motoactionfix with the Rom. Latest beta SuperSu works, as does 7.1 Gapps.
Rom
https://www.androidfilehost.com/?fid=817550096634759986
Motoactionfix
https://www.androidfilehost.com/?fid=457095661767151817

well, but I get a configuration error on the start screen ...... what happend.... I flashed the pico gaaps

Yes. Its working well. I am using it from 2 days. Only one random reboot initially after installing. Till now all basic things working.
Installing ROM and gapps together gives setup widget fc.
But Flashing ROM, reboot, flash gapps works fine.

Installed it, works really well.
Was able to install Substratum with 7.1.1 Themes.
THANKS!

You CAN'T' post any DU roms on XDA. Ffs, take this down.

Pulse not working properly & equalizer too..

here guys dirty 11.3 for titan motoaction bug is fixed in this version
https://www.androidfilehost.com/?fid=673368273298946068

evandro_stan said:
You CAN'T' post any DU roms on XDA. Ffs, take this down.
Click to expand...
Click to collapse
That's not actually true. An "Urban Myth" perhaps.

Any bugs?

Well the only bug, and it seem to be common on AOSP roms, is that the Navbar Editor is listed in Settings but it can't be invoked.
Anyone know a workaround to change the order of the navbar buttons?

Same error
rickseth said:
well, but I get a configuration error on the start screen ...... what happend.... I flashed the pico gaaps
Click to expand...
Click to collapse
I flash ROM + gapps + zipmoto and get eroor .. I flash 11.3 if not return to lineageos )

Till get fixed only replace SetupWizzard after flashing gapps & don't forget give permissions

I didn't get any problems with 11.2 , used without gapps.
Today I've installed 11.3 build made by @Kranoner, In this I didn't have apns , I've created manually but I get 2G connection only.
Pulse doesn't show up with poweramp .

Flash Rom + Supersu
Boot
Boot to Recovery, flash GApps

raj_45 said:
I didn't get any problems with 11.2 , used without gapps.
Today I've installed 11.3 build made by @Kranoner, In this I didn't have apns , I've created manually but I get 2G connection only.
Pulse doesn't show up with poweramp .
Click to expand...
Click to collapse
i build this blind also i cant test it or fix any bug i use dirtyunicorns 11.3 of my pixel and my mi 5 and i have no bugs sorry for your guys but buy a new phone this solved alot of bugs then in the future i dont think any one will bring new stuff for moto g 2014 its to old and 1 gb ram is to low and the kernel version is horror 3.4.xxx all good feats come in kernel version 3.10 and up

Kranoner said:
i build this blind also i cant test it or fix any bug i use dirtyunicorns 11.3 of my pixel and my mi 5 and i have no bugs sorry for your guys but buy a new phone this solved alot of bugs then in the future i dont think any one will bring new stuff for moto g 2014 its to old and 1 gb ram is to low and the kernel version is horror 3.4.xxx all good feats come in kernel version 3.10 and up
Click to expand...
Click to collapse
Thank u for making this , even without having device in hand
I have only problems
1.
2.I don't get voice from earpiece when making call after unplugging charger, to get voice I have reboot.

raj_45 said:
Thank u for making this , even without having device in hand
I have only problems
1.
2.I don't get voice from earpiece when making call after unplugging charger, to get voice I have reboot.
Click to expand...
Click to collapse
This also happened with me even old builds. I need to switch to other 7.1.2 coz of this issue.
Still great ROM. Many thanks @Kranoner

Hi guys, any hope for a new update to 11.4 or 11.5?

can it be used for moto g falcon as both models are almost same????

SHIVAM1198 said:
can it be used for moto g falcon as both models are almost same????
Click to expand...
Click to collapse
No

Network location in Android 7.1.2 [tasker]

I tried now lineage, xenon hd and resurrection. In every 7.1.2 ROM I am unable to get the network based location.
Unfortunately the only way I I know to read this battery saving location is by using tasker(which need to work for me)
Google maps is working without GPS. But I think just because near WiFi.
Can anyone check to read the network based location with tasker in a 7.1.2. ROM?
I already checked my APN settings,my sim card and the android right policies for tasker.... No luck at all

It seems that you have similar problem like me and others:
"Network Location Provider" doesn't work with up-to-date Google Play Services
Location not correct when indoors

Thanks for the links. And indeed, it seems like the same problem.
What surprises me is that this bug dont appeal to this community here. For me it is an important feature of google service which we cant use with our OP2.
Furthermore i dont understand why this bug seems to be a bug according to our device.
For me it is ja software bug with no relation to our hardware?
I hope this error gets more pushed soon

mr_krabbs said:
...Furthermore i dont understand why this bug seems to be a bug according to our device.
For me it is ja software bug with no relation to our hardware?..
Click to expand...
Click to collapse
For me, this is also a big problem, because I often need to see geotags in my picture where I made this or that photo. But geotags are not recorded in photos, but if they are recorded, then only one place even if I have already passed 2 kilometers.
There are two solutions - to put Google-camera, but there is very dark video in case of insufficient illumination, the second - to put another ROM. I tried almost all the firmware and only two did not have problems:
Resurrection Remix M [5.7.4]
LineageOS 13.0
But one more problem because of which I will soon change my OP2 is a poor autonomy.

mr_krabbs said:
I tried now lineage, xenon hd and resurrection. In every 7.1.2 ROM I am unable to get the network based location.
Unfortunately the only way I I know to read this battery saving location is by using tasker(which need to work for me)
Google maps is working without GPS. But I think just because near WiFi.
Can anyone check to read the network based location with tasker in a 7.1.2. ROM?
I already checked my APN settings,my sim card and the android right policies for tasker.... No luck at all
Click to expand...
Click to collapse
Just flash latest stock firmware , I.e. 3.6.0 for op2 solved my problem hope it does yours

veeranna said:
Just flash latest stock firmware , I.e. 3.6.0 for op2 solved my problem hope it does yours
Click to expand...
Click to collapse
Thanks. As far as i know the 3.6.0 updates is based on Android 6.0.1. and therefore no android 7.1.x
However you are right, it seems to be the only fix for now. No Android 7 With this feature.
I am just wondering why

mr_krabbs said:
Thanks. As far as i know the 3.6.0 updates is based on Android 6.0.1. and therefore no android 7.1.x
However you are right, it seems to be the only fix for now. No Android 7 With this feature.
I am just wondering why
Click to expand...
Click to collapse
Just flash firmware file not whole rom. Then flash your desired ROM and Gapps

[Q] firmware flash
veeranna said:
Just flash firmware file not whole rom. Then flash your desired ROM and Gapps
Click to expand...
Click to collapse
i am struggling with how to flash a firmware
my source for the firmware is:
https://www.androidfilehost.com/?w=files&flid=53150
when i flash the firmware 3.6.0 in twrp my sim card isnt recognized anymore
if i use the app "[root] FlashFire" i can see i have a new version of baseband but still no luck with the network based location
How do u flash your firmware?
Edit: I did a clean flash
1. firmware
2. latest aospExtended rom
3.gapps
4. magisk and root
i have a new baseband now. but for me my network location is always in the middle of germany. It is not even close to my postion =)

mr_krabbs said:
i am struggling with how to flash a firmware
my source for the firmware is:
https://www.androidfilehost.com/?w=files&flid=53150
when i flash the firmware 3.6.0 in twrp my sim card isnt recognized anymore
if i use the app "[root] FlashFire" i can see i have a new version of baseband but still no luck with the network based location
How do u flash your firmware?
Edit: I did a clean flash
1. firmware
2. latest aospExtended rom
3.gapps
4. magisk and root
i have a new baseband now. but for me my network location is always in the middle of germany. It is not even close to my postion =)
Click to expand...
Click to collapse
Clean installed
Flashed firmware and then RR ROM and gapps wipe cache dalvik cache that's it and one thing don't flash magisk with RR rom had terrible delay in first boot u can flash anytime after first boot this is what I have done and I'm from India and no network issue volte working fine

Need Help Rooting (solved)

Hello XDA,
I have been using Samsung phones all my life , Rooted (odin) a lotta phones installed countless custom roms and finally i thought its time for pure android experience . I bought a moto g4 plus from a friend of mine and have been going through the g4 + forum for 2 days now . I have not got the slightest of idea how you root / install custom rom on this device . Its so different from how you do it on a Samsung device so finally I have decided to ask for your help .
Info I would like to share :
1.The boot loader is locked
2.The device is a XT1643
3. 3 GB / 32 GB
4. December 1 , 2017 security patch
5. NPJS25.93-14-13
6. There was a OTA update when I received the phone which I didn't update
As mentioned earlier It looks like I am a complete noob when it comes to this device and I would need all the possible help I can get .
If anybody would be kind enough to guide me through this initial learning phase I will be very grateful and would even share my whisky ( which I usually don't do )
If you need any more information please ask
Thanks and Regards
DW

Drunken-warlord said:
Hello XDA,
I have been using Samsung phones all my life , Rooted (odin) a lotta phones installed countless custom roms and finally i thought its time for pure android experience . I bought a moto g4 plus from a friend of mine and have been going through the g4 + forum for 2 days now . I have not got the slightest of idea how you root / install custom rom on this device . Its so different from how you do it on a Samsung device so finally I have decided to ask for your help .
Info I would like to share :
1.The boot loader is locked
2.The device is a XT1643
3. 3 GB / 32 GB
4. December 1 , 2017 security patch
5. NPJS25.93-14-13
6. There was a OTA update when I received the phone which I didn't update
As mentioned earlier It looks like I am a complete noob when it comes to this device and I would need all the possible help I can get .
If anybody would be kind enough to guide me through this initial learning phase I will be very grateful and would even share my whisky ( which I usually don't do )
If you need any more information please ask
Thanks and Regards
DW
Click to expand...
Click to collapse
I'm sorry to reprimand you, but you really need to follow the rules here. It took me all of a few moments to find exactly what you're looking for simply by searching.
https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Don't hesitate to ask questions in the future, but only if you've exhausted all other avenues.

Ragarianok said:
I'm sorry to reprimand you, but you really need to follow the rules here. It took me all of a few moments to find exactly what you're looking for simply by searching.
https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Don't hesitate to ask questions in the future, but only if you've exhausted all other avenues.
Click to expand...
Click to collapse
Hello Mate
As mentioned above I have been searching the forum for almost 2 days before I thought of asking for help . I did go through the thread( that you have mentioned ) earlier today but it looks a bit old to me . The link on how to flash twrp comes back with a 404 error . The last few posts are helpful (as it deals with the same build) but again as am new to the particular device It would be helpful if someone could give me a noob friendly procedure . I am not here to break the rules just trying to learn without bricking my device
Thanks and Regards
DW

yeshwanthvshenoy said:
Flashing TWRP:
>>> Flashing TWRP or Rooting will void your warranty. Please ask anything before doing, if your not fully confident on what to be done. <<<
Get the TWRP image file from http://forum.xda-developers.com/mot...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
Next, get the adb and mfastboot from https://drive.google.com/file/d/0B5jlU9JnLAZGbVU0UzJ3N3p4X2M/view?usp=sharing
Unzip the file and place the image file inside the extracted folder.
Reboot to Bootloader (power off, then press the power and volume down buttons simultaneously).
Open a new command prompt or terminal window and do the following:
Code:
mfastboot flash recovery twrp_*version*_athene.img
Rooting Device:
>>> The old guide is outdated. Will be updated shortly. <<<
Click to expand...
Click to collapse
Drunken-warlord said:
Hello Mate
As mentioned above I have been searching the forum for almost 2 days before I thought of asking for help . I did go through the thread( that you have mentioned ) earlier today but it looks a bit old to me . The link on how to flash twrp comes back with a 404 error . The last few posts are helpful (as it deals with the same build) but again as am new to the particular device It would be helpful if someone could give me a noob friendly procedure . I am not here to break the rules just trying to learn without bricking my device
Thanks and Regards
DW
Click to expand...
Click to collapse
Sorry for being so short earlier. We have quite a few members here who constantly post issues without using the search function.
You can try to post I quoted above to flash TWRP. It's fairly straight forward.
Are you planning on flashing a Nougat ROM or are you going the adventurous route and flashing an Oreo ROM? The TWRP version mentioned in the quoted post should be fine for flashing Nougat and 32-bit based Oreo ROMs, but you'll need 64-bit TWRP for 64-bit Oreo ROMs.
Use this as a reference for 32-bit and 64-bit Oreo ROMs: https://forum.xda-developers.com/moto-g4-plus/how-to/oreo-roms-table-t3717226
64-bit TWRP: https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206
Once you've flashed TWRP, you can either flash different versions through TWRP itself or through the Play Store app.
As far as ROMs, I'd recommend Official Lineage OS 14.1 for Nougat: https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101
And I'd recommend Official AICP 13.1 for Oreo: https://forum.xda-developers.com/mo...om-aicp-13-1-o-8-1-0-official-weekly-t3731269 (You'll need to download the 20180212 build since most recent builds either have a broken camera or won't boot.)
Any other questions, don't hesitate to ask.

Drunken-warlord said:
Hello Mate
As mentioned above I have been searching the forum for almost 2 days before I thought of asking for help . I did go through the thread( that you have mentioned ) earlier today but it looks a bit old to me . The link on how to flash twrp comes back with a 404 error . The last few posts are helpful (as it deals with the same build) but again as am new to the particular device It would be helpful if someone could give me a noob friendly procedure . I am not here to break the rules just trying to learn without bricking my device
Thanks and Regards
DW
Click to expand...
Click to collapse
Hello and welcome, Please have a look in each device forum for a newbie help thread https://forum.xda-developers.com/moto-g4-plus/help/help-thread-question-noob-friendly-t3526598 where you can ask questions that are repeatedly asked and where you'll be guided to the right threads to help you further :good:
This keeps the forum clean and everything at a glance so you'll be find easily topics

@Ragarianok
I am going to try the Oreo builds as I have never got a chance to try it on my previous devices so I guess I will be using a 64bit version of twrp.
This is what am planning to do :
1. Unlock the bootloader
2. Flash an official version of TWRP
2.a Take a backup
3. Flash a custom kernel through twrp
4. Flash Super Su / Magisk
5. Flash a 64 bit version of twrp using TWRP
6. Flash a custom ROM
Please correct me if I am wrong
Thanks a lot for the detailed guide
Thanks and Regards
DW

Drunken-warlord said:
@Ragarianok
I am going to try the Oreo builds as I have never got a chance to try it on my previous devices so I guess I will be using a 64bit version of twrp.
This is what am planning to do :
1. Unlock the bootloader
2. Flash an official version of TWRP
2.a Take a backup
3. Flash a custom kernel through twrp
4. Flash Super Su / Magisk
5. Flash a 64 bit version of twrp using TWRP
6. Flash a custom ROM
Please correct me if I am wrong
Thanks a lot for the detailed guide
Thanks and Regards
DW
Click to expand...
Click to collapse
If you want 64bit Oreo roms it's a little bit different
1. Unlock the bootloader
2. Flash a 64 bit version of twrp
2.a Take a backup and safe it off your phone
3. Flash a Oreo 64bit custom ROM
3.a flash gapps package arm64 (8.0 or 8.1 depending on rom version)
4. Flash magisk 15.3
If you want to root the stock nougat rom steps 1-4 of your list are correct.

Drunken-warlord said:
@Ragarianok
I am going to try the Oreo builds as I have never got a chance to try it on my previous devices so I guess I will be using a 64bit version of twrp.
This is what am planning to do :
1. Unlock the bootloader
2. Flash an official version of TWRP
2.a Take a backup
3. Flash a custom kernel through twrp
4. Flash Super Su / Magisk
5. Flash a 64 bit version of twrp using TWRP
6. Flash a custom ROM
Please correct me if I am wrong
Thanks a lot for the detailed guide
Thanks and Regards
DW
Click to expand...
Click to collapse
Not quite. You'll want to go in this order:
1. Unlock bootloader
2. Flash TWRP
3. Backup
4. Wipe (Wipe/Advanced Wipe; ART/Dalvik, System, Data, Cache)
5. Flash ROM
6. Flash Gapps
7. Reboot
8. Go through setup wizard and let everything settle for ~10 minutes
9. Boot into TWRP and flash SuperSU or Magisk (I would suggest Magisk), then flash kernel and reboot
You'll need to flash the unofficial 64-bit TWRP mentioned in my previous post to flash a 64-bit Oreo ROM, otherwise you'll get an error message when flashing ROM.
You'll also need to use unofficial Gapps since there aren't any official Gapps for 8.1 just yet. I'd recommend either mini or micro here: https://sourceforge.net/projects/unofficial-opengapps-8-1/files/arm64/20180225/
You should be able to flash the most recent Magisk located here: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
If you do flash a custom kernel, I'd highly suggest Frostbitten: https://forum.xda-developers.com/mo...s-frostbitten-kernel-moto-g4-g4-plus-t3649155
@strongst
Just noticed that you posted a similar set of instructions and now I feel like a goober.

Ragarianok said:
Just noticed that you posted a similar set of instructions and now I feel like a goober.
Click to expand...
Click to collapse
What's a goober there are every time different ways users must decide which one to choose :laugh:

strongst said:
What's a goober there are every time different ways users must decide which one to choose :laugh:
Click to expand...
Click to collapse
In this context, it basically means I did something silly.

Ragarianok said:
In this context, it basically means I did something silly.
Click to expand...
Click to collapse
Nope you didn't

@strongst @Ragarianok
I am glad that I got the G4+. With amazing people like you on the forum it's guaranteed to be fun-filled learning experience
Thanks again for the support
Regards
DW

Drunken-warlord said:
@[email protected]
I am glad that I got the G4+. With amazing people like you on the forum it's guaranteed to be fun-filled learning experience
Thanks again for the support
Regards
DW
Click to expand...
Click to collapse
Thanks, you're welcome :good:

Ota ? ..... Was it jan security patch update ?

pang12345 said:
Ota ? ..... Was it jan security patch update ?
Click to expand...
Click to collapse
If it was an OTA update, it looks likely to be more the February 2018 security patch rather than the January 2018 patch.
Credit https://forum.xda-developers.com/moto-g4-plus/how-to/athene-security-patch-usa-february-t3745147

echo92 said:
If it was an OTA update, it looks likely to be more the February 2018 security patch rather than the January 2018 patch.
Credit https://forum.xda-developers.com/moto-g4-plus/how-to/athene-security-patch-usa-february-t3745147
Click to expand...
Click to collapse
The op was talking about xt1643 ,and this model is for india. And the link that you mentioned is for us model .

pang12345 said:
The op was talking about xt1643 ,and this model is for india. And the link that you mentioned is for us model .
Click to expand...
Click to collapse
That is true, however for our devices we have generally been issued the same security patch level regardless of region. It may be different builds for particular regions (e.g NPJS25.93-14-13 for India, Brazil and EU, and NPJ25.93-14.7-3 for US) but they are both the December 2017 security patch.
Regardless, we've still yet to see an OTA newer than December.

@strongst @Ragarianok @echo92
Evening ,
Thanks For all the support i finally rooted MY phone
But
I ran into a bit of a problem " Sim Cards Not Detecting "
This is What i did
1. Unlocked My bootloader
2. flashed twrp-3.1.1-athene_shreps
3. Took a backup of everything
4. flashed ElementalX-G4-2.00.zip
5. flashed Magisk 16.0
reboot : No sim cards detected
After which I flashed lineage-14.1-20180219-nightly-athene-signed.zip and the gapps provided
experienced the same error again .
uninstalled magisk and flashed the latest Super Su (V2.82) with no positive results
not sure what went wrong ...is there any way out of it ?

Drunken-warlord said:
@strongst @Ragarianok @echo92
Evening ,
Thanks For all the support i finally rooted MY phone
But
I ran into a bit of a problem " Sim Cards Not Detecting "
This is What i did
1. Unlocked My bootloader
2. flashed twrp-3.1.1-athene_shreps
3. Took a backup of everything
4. flashed ElementalX-G4-2.00.zip
5. flashed Magisk 16.0
reboot : No sim cards detected
After which I flashed lineage-14.1-20180219-nightly-athene-signed.zip and the gapps provided
experienced the same error again .
uninstalled magisk and flashed the latest Super Su (V2.82) with no positive results
not sure what went wrong ...is there any way out of it ?
Click to expand...
Click to collapse
First, I'm a little confused about the fact that you flashed that version of TWRP instead of the one located here: https://dl.twrp.me/athene/
Second, I've never had that happen when flashing, so I'm not really sure what to recommend. If I had to guess, I would say the best route would be to restore your backup and see if the SIM is detected.
I have found at least one thread with a similar issue; might be worth a look: https://forum.xda-developers.com/moto-g4-plus/how-to/fix-sim-card-issue-t3751679
Let us know what happens.

Ragarianok said:
First, I'm a little confused about the fact that you flashed that version of TWRP instead of the one located here: https://dl.twrp.me/athene/
Second, I've never had that happen when flashing, so I'm not really sure what to recommend. If I had to guess, I would say the best route would be to restore your backup and see if the SIM is detected.
I have found at least one thread with a similar issue; might be worth a look: https://forum.xda-developers.com/moto-g4-plus/how-to/fix-sim-card-issue-t3751679
Let us know what happens.
Click to expand...
Click to collapse
I went through that before posting my question .. the paper does not help .
Is it okey if I flash the twrp that you have mentioned over the existing twrp?
Thanks and regards
DW
Edit : I have restored my backup but still the same issue.
Edit : flashed the official TWRP . still the same results
EDIT : After 3 hours + Countless reboots the issue solved on its own ... I am not sure what really happened.. lol
Thanks for the Support
DW