yashsingh1/xdaforums huggingface dataset:
[Moto G 2014 LTE Android Development] Rox5:
[MENTION=9152969]Wattsensi[/MENTION]

You should may be not spend so much energy to demonstrate that Titan build is fully not compatible with Thea hardware, because you know that Titan/Thea are perfect twins.

We don't care about battery capacity difference between XT1072 and XT1069.

Marketing is making different models with same hardware to fit region countries requirements, and propose different pricings ... with the same devices with very small limitation differences (like enabling or not 4G/LTE).

Wattsensi /21st October 2018,

This was already known in this forum since 2016.

I am curious / I have tested Titan build on Thea: nothing wrong I think, I am free to test what I want, until LOS 15 or 16 is available for Thea.

It is a fact that Titan builds are usually more available (same remark for Ubuntu touch available for Titan, but not Thea).

Hope this is clear now.

The situation I understand:

* gothicVI is trying to make a working LOS15 build for Thea since at least October 2018, has time to do it, but is missing a piece of the puzzle (RIL);

* you claim to have the solution, but do not have enough time (for the moment) to make builds for Thea.

Depending on when you think you will have time to make Thea build, and inform when, would it be crazy to propose your help to gothicVI to finalize his build, so that at least one backup solution is available the day you won't have time anymore to make builds ?

This is just an open question, and I do not want to interact with "fights" between maintainers that I don't understand without enough background.

Wattsensi to gothicVI, on 27th February 2019,
[Moto G 2014 LTE Android Development] Wattsensi:
[MENTION=5706262]Rox5[/MENTION] You are the only one who sees this as a 'fight'. This is an argument.

First of all, having the same baseboard doesn't necessarily guarantee cross-device compatibility although it works between Titan/Thea as you discovered. But an unwritten rule of ROM flashing is that you should never flash device specific things meant for another model.

Second, it's in my best interests for users to not to brick their devices. Just look how easy is to hard brick an XT1072 by flashing an XT1064 bootloader by mistake because the Titan uses an older bootloader. Look at the Q&A section and see how many people either hard bricked/perma-crippled their phones by flashing a wrong firmware or flashed a wrong TWRP just to be surprised when they couldn't flash Thea ROMs.

Although having no LTE is better than no RIL at all like my builds.

I claimed that I solved the vendor image mismatch issue, not the RIL issue. Yeah, I can't just prepare git and do a pull request because I really don't have time. I was in high school when I built those ROMs. I am a busy college student now, but I'll still try to help here despite not having a Thea anymore.
[Moto G 2014 LTE Android Development] Rox5:
Right. The vendor image mismatch issue also needs to be clarified, although may be just a warning message without real consequences.

Concerning RIL, and lack of SIM card detection, these are the RIL files available after installation:

/system/app/qcrilmsgtunnel/qcrilmsgtunnel.apk

/system/bin/rild

/system/etc/init/rild.rc
/system/etc/init.qcom.ril.sh
/system/etc/permissions/qcrilhook.xml

/system/framework/qcrilhook.jar

/system/lib/libbrillo-stream.so
/system/lib/libbrillo.so
/system/lib/libreference-ril.so
/system/lib/libril.so
/system/lib/librilutils.so

/system/vendor/lib/libril-qc-qmi-1.so
/system/vendor/lib/libril-qcril-hook-oem.so

According to this [ How to use rild command ], I wonder if a symlink is not missing somewhere to activate/initiate ril-daemon service, to be placed somewhere in an init script.

Just to give ideas / for investigation...

service ril-daemon /system/bin/rild -l /system/lib/libreference-ril.so -- -d /dev/ttyUSB2
[Moto G 2014 LTE Android Development] Rox5:
EDIT:

May be something important.....

LineageOS 14 has a '/system/bin/rild' file and not LOS15

LineageOS 15 has a '/vendor/bin/hw/rild', which should may be copied or symlinked to /system/bin/rild

This could explain that rild is not launched.
[Moto G 2014 LTE Android Development] Wattsensi:
When I was testing my own builds, rild would be terminated with SIGKILL immediately upon launch when manually launched. IDK if that happens in gothic's builds. Can you check dmesg please?

EDIT: Does symlinking rild solve the issue?
[Moto G 2014 LTE Android Development] Rox5:
I currently do not have LOS 15 installed, because ... I need my phone to phone.

I have extracted on my PC the LOS15 build to investigate and compare with LOS14 installation.

The RIL initialization process should be accurately investigated, because there is a serious probability that the SIM card is not detected, simply because rild process is not launched at all.

EDIT: to be investigated: /vendor/etc/init/hw/init.qcom.rc

LOS15:

service ril-daemon /vendor/bin/hw/rild

LOS16:

service ril-daemon1 /vendor/bin/hw/rild -c 2
[Moto G 2014 LTE Android Development] Rox5:
@ gothicVI

'ro.board.platform' should be declared in build.prop

ro.board.platform=msm8226
ro.product.board=MSM8226

+ if you launch the command below in a terminal from the root of your build tree, what does it report ?

egrep -r "ro.*.build.(fingerprint|description)" ./
[Moto G 2014 LTE Android Development] Rox5:
+ EDIT:

Those files are missing in lineage-15.1-20190303-UNOFFICIAL-thea build

/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/init/hw/init.qcom.usb.rc
[Moto G 2014 LTE Android Development] Numberone2022:
Hello... I have moto g2 xt 1072.. I Trier installing the lineage 15.1 and lineage 16 , I'm using the bootloader thea... It's my SIM not recognized... I deleted the check lines before installation /META-INF/com/android/metadata and /META-INF/com/google/android/updater-script ... In metadata I changed titan for names to thea And the bootloader version... If i have to change anything else help me???

---------- Post added at 03:22 AM ---------- Previous post was at 03:16 AM ----------

Can I test the versions as soon as I fix RIL
[Moto G 2014 LTE Android Development] goosnarrggh:
There's no agreement to sign.

If you have received a piece of compiled software that was originally created under the GPL, then you automatically have the right to demand access to the source code corresponding to the exact version of the software you received. You also have permission to reverse-engineer it, and to modify it to suit your needs. After making modifications, as long as you keep you modified software private for your own personal use, you have no additional obligations.

However, If you choose redistribute any GPL software that you modified to anybody else in compiled form, then you are automatically obliged to make the exact modified source code available to them. And then, they also automatically get all the same rights and obligations that you had.

That all being said, Android consists of a whole lot of software, and not all of it is covered by the GPL. The most prominent GPL part would probably be the Linux kernel (specifically, GPL version 2.0). The device tree* (that is, the repository named android_device_motorola_thea in this case) is almost certainly NOT released as GPL software. In general, any device tree that is derived from something that was at one point officially supported by the LineageOS project will have been released under the Apache 2.0 license.

The terms of the Apache license are different, and there is no obligation to disclose source code along with modified binaries.

______________

* The term device tree also has a special meaning in the context of the Linux kernel. You may also see it referred to as dts and dtb files. If an Android boot.img file has a dtb appended, then there are tools available to extract the appended dtb and decompile it back into a machine-generated dts source.
[Moto G 2014 LTE Android Development] Numberone2022:
can you help in RIL correction ???? Moto G2 Thea has no rom upgraded ... or in the correction of lineage 16 titan to thea???

---------- Post added at 04:08 PM ---------- Previous post was at 04:01 PM ----------

[MENTION=7615920]goosnarrggh[/MENTION] as rox5 installed and its sim was recognized .... in my region it sold thea and titan
[Moto G 2014 LTE Android Development] Rox5:
titan builds (LinageOS, RRemix etc) work fine on Moto G XT****_thea, but only if you know what are: brotli, bootloader, recovery, fastboot, adb etc etc....., and you understand what you do, i.e.: not just copy/pasting code lines.

If not, don't try it.

I did not find any solution, even very tricky (...) to enable 4G/LTE on titan builds (=> only H+ available).

The bottom line:

Not sure after 6 months of effort to debug the RIL part of LOS_15 build, it is still really relevant to persist, instead on focusing now on LOS16.
[Moto G 2014 LTE Android Development] Numberone2022:
how then is the correct way to install and edit the script and metadata ??? ... I used twrp ... everything worked except the SIM .... Which tutorial to enable the 4g ?? how to send a link or explain how it is done ???? I really want to use lineage 16 ... my bootloader is 0x4822
[Moto G 2014 LTE Android Development] Numberone2022:
ota-property-files=metadata:69:409

ota-required-cache=0

ota-type=BLOCK

post-build=motorola/lineage_titan/titan:9/PQ2A.190305.002/45:userdebug/test-keys

post-build-incremental=45

post-sdk-level=28

post-security-patch-level=2019-03-05

post-timestamp=1552263538

pre-bootloader=0x4822|0x4883|0x4886|0x4887

pre-device=thea,titan_umts,titan_udstv,titan_umtsds,titan_retaildsds,XT1068,XT1064,XT1063,XT1072

---------- Post added at 09:18 PM ---------- Previous post was at 09:14 PM ----------

assert(getprop("ro.product.device") == "thea" || getprop("ro.build.product") == "thea" ||

getprop("ro.product.device") == "titan_umts" || getprop("ro.build.product") == "titan_umts" ||

getprop("ro.product.device") == "titan_udstv" || getprop("ro.build.product") == "titan_udstv" ||

getprop("ro.product.device") == "titan_umtsds" || getprop("ro.build.product") == "titan_umtsds" ||

getprop("ro.product.device") == "titan_retaildsds" || getprop("ro.build.product") == "titan_retaildsds" ||

getprop("ro.product.device") == "XT1068" || getprop("ro.build.product") == "XT1068" ||

getprop("ro.product.device") == "XT1064" || getprop("ro.build.product") == "XT1064" ||

getprop("ro.product.device") == "XT1063" || getprop("ro.build.product") == "XT1063" ||

getprop("ro.product.device") == "XT1072" || getprop("ro.build.product") == "XT1072" || abort("E3004: This package is for device: titan,titan_umts,titan_udstv,titan_umtsds,titan_retaildsds,XT1068,XT1064,XT1063,XT1069; this device is " + getprop("ro.product.device") + "."););

assert(getprop("ro.bootloader") == "0x4822" ||

getprop("ro.bootloader") == "0x4883" ||

getprop("ro.bootloader") == "0x4886" ||

getprop("ro.bootloader") == "0x4887" || abort("This package supports bootloader(s): 0x4882, 0x4883, 0x4886, 0x4887; this device has bootloader " + getprop("ro.bootloader") + "."););

---------- Post added at 09:46 PM ---------- Previous post was at 09:18 PM ----------

Does the speed in h+ work as 3g or 4g??? The setting in *#*#4636#*#* valid?? The 4g it just appears as h+?..
[Moto G 2014 LTE Android Development] Rox5:
@ Numberone2022

How to install a titan build in a thea model is really not the subject, but to help you a little bit, assuming you know what you do, there are two possibilities:

1 - bypass Error 7 when install the ROM.zip with TWRP => what you did

2 - extract boot.img and system.new.dat.br from ROM.zip, decompress system.new.dat.br (.br => brotli compression algorithm) to system.new.dat, and convert system.new.dat to system.img, and then flash boot.img and system.img with fastboot in bootloader mode.

Risk is close to zero to brick something, as long as GPT and bootloader are not touched/modified, because fastboot mode will still be alive.

You can always reinstall an official stock ROM from scratch to reactivate your Moto G, in case of real trouble.

I hope you correctly cleaned cache, dalvick-cache and data before going to conclusion.

You should also try to erase modemst1 and modemst2 (in fastboot mode), and reboot.

However, I noticed a difference with your XT1072.

My bootloader is 0x4821, and yours is 0x4822 : I don't know if this is a significant difference.

Take care.

Not 100% yet sure of the conclusion but quite sure it is really H+ HSPA (WCDMA network).

The european radio band is not seen in the radio configuration (only US or automatic mode).

The situation for me:

- thea LOS_15.1 build does not work with my XT1072_thea (no SIM card detected)

- titan LOS_16 build works fine on my XT1072_thea with one identified problem: impossible to activate 4G/LTE (I tried a lot of dirty solutions with no success).

Getting working thea builds for thea Moto G would be preferable anyway.
[Moto G 2014 LTE Android Development] Numberone2022:
I live in America my band LTE / UMTS she is compatible in lineage titan?

Can later install the ROM stock from scratch??? I use some program to convert or just switch to .img??

---------- Post added at 10:56 PM ---------- Previous post was at 10:48 PM ----------

Can I chance the name of moto g2 2014 to moto g2 2014 LTE?? In build.prop?? What are these filea named modem for??? I will only use these files to install lineage... System. Img and boot.img??? Or will I need to flash the .zip after??? Is this metadata and script presente in the .dat??
[Moto G 2014 LTE Android Development] Rox5:
@ Numberone2022

Your questions are not all very clear, but in summary:

- if you live in America, US radio band should be just fine for you !

- as long as you don't try to modify GPT and bootloader, you can always reinstall an official Moto G build in bootloader mode with fastboot;

- to convert system.new.dat.br to system.new.dat, you need to install brotli package, available for Linux;

- to convert system.new.dat to system.img, you need a python program called "sdat2img.py" (I will not detail here)

- changing "Moto G2 2014" to "Moto G2 2014 LTE" with build.prop ? I did not succeed.....

- your question about erasing modemst1 and modemst2 ? If you know how to install a stock ROM, you should know because it is part of the process.....

- keep in mind that the memory partition of Moto G is composed of 42 different blocks !!

This is why it is always advised to understand what you do, before operating.

+ I confirm: No LTE / HSPA+ only : I've installed "LTE discovery tool" to confirm
[Moto G 2014 LTE Android Development] Numberone2022:
Not Worked...system.img Image Size in fastboot
[Moto G 2014 LTE Android Development] Rox5:
You may be don't use the right tool.

I use fastboot version 1:8.1.0 in linux, and no problem at all. system.img file is automatically sparsed in two parts.

sudo fastboot flash system system.img

I have tested many things, and I confirm what I told you: you absolutely need the wipe cache+dalvick-cache+data and modemst1/2 to have any chance to get your SIM card detected.

I've tested AICP titan build, and did not have any SIM detected without erasing modemst1/2.

sudo fastboot erase modemst1
sudo fastboot erase modemst2

nb: "sudo" means in linux that the command needs to be done as root user.

I've no idea how it works in windows, in case you are still a windows user.

Your problem is not the way you bypass the Error 7 during installation , but your process is not clean enough before jumping to conclusion.

BTW, I have now the same bootloader as you: 0x4822.
[Moto G 2014 LTE Android Development] Numberone2022:
Thank You!!! The cleaning of the system, cache should i do in Abd fastboot or twrp??? After installation the system i can install the gapps and root??? Do you think it's just lineage 14.1 thea or lineage 16 titan???? Lineage 16 updates should I Always losing adb data or can I use twrp??
[Moto G 2014 LTE Android Development] Rox5:
'adb fastboot' is impossible, as far as I know. I don't know where you find that..

fastboot is a very low-level command which can only be executed in bootloader mode (which is not recovery mode).

With TWRP recovery, adb command can be executed, with the phone rebooted in in recovery mode.

You should go step by step, and take more time to better understand. what you do.

I already gave you the commands to erase modemst.

To erase caches, you can execute 'fastboot erase cache' in bootloader mode, but better also reboot in TWRP recovery mode to wipe all caches.
[Moto G 2014 LTE Android Development] androbag:
Hello, I was able to install lineage-16.0-20190311-UNOFFICIAL-titan on my thea XT1072, after a complete cleaning of the phone from TWRP and after applying the modifications described in posts #42 and #58.

Everything is working well, including making and receiving calls and SMS and all the sensors. Mobile data work well with H+, but I can't test LTE, because my mobile offer does't provide it.
[Moto G 2014 LTE Android Development] Rox5:
The titan/thea compatibility is not a mystery, both based on Snapdragon 400 (LTE compatible, without VoLTE only available on 410 => Moto G Osprey)

The Moto G2 2014 memory is divided in 42 blocks:

adb shell ls -l /dev/block/platform/msm_sdcc.1/by-name|cut -d\ -f8-

DDR -> /dev/block/mmcblk0p3
aboot -> /dev/block/mmcblk0p4
abootBackup -> /dev/block/mmcblk0p11
boot -> /dev/block/mmcblk0p32
cache -> /dev/block/mmcblk0p41
cid -> /dev/block/mmcblk0p26
clogo -> /dev/block/mmcblk0p29
deviceinfo -> /dev/block/mmcblk0p34
dhob -> /dev/block/mmcblk0p21
frp -> /dev/block/mmcblk0p16
fsc -> /dev/block/mmcblk0p23
fsg -> /dev/block/mmcblk0p22 -> mounted on /fsg
ftmlog -> /dev/block/mmcblk0p35
hob -> /dev/block/mmcblk0p20
keystore -> /dev/block/mmcblk0p38
kpan -> /dev/block/mmcblk0p36
logo -> /dev/block/mmcblk0p28
logs -> /dev/block/mmcblk0p9
misc -> /dev/block/mmcblk0p31
modem -> /dev/block/mmcblk0p1 -> mounted on /firmware
modemst1 -> /dev/block/mmcblk0p18
modemst2 -> /dev/block/mmcblk0p19
oem -> /dev/block/mmcblk0p39
padA -> /dev/block/mmcblk0p10
padB -> /dev/block/mmcblk0p17
padC -> /dev/block/mmcblk0p37
pds -> /dev/block/mmcblk0p27
persist -> /dev/block/mmcblk0p30
recovery -> /dev/block/mmcblk0p33
rpm -> /dev/block/mmcblk0p5
rpmBackup -> /dev/block/mmcblk0p12
sbl1 -> /dev/block/mmcblk0p2
sdi -> /dev/block/mmcblk0p7
sdiBackup -> /dev/block/mmcblk0p14
sp -> /dev/block/mmcblk0p25
ssd -> /dev/block/mmcblk0p24
system -> /dev/block/mmcblk0p40 -> mounted on /system
tz -> /dev/block/mmcblk0p6
tzBackup -> /dev/block/mmcblk0p13
userdata -> /dev/block/mmcblk0p42 -> mounted on /data
utags -> /dev/block/mmcblk0p8
utagsBackup -> /dev/block/mmcblk0p15

The titan/thea difference is the modem firmware provided by Motorola from stock ROM:

/dev/mmcblk0p22 filled by NON-HLOS.bin

/dev/mmcblk0p1 filled by fsg.mbn

modemst1-2 blocks are only modem cached values, recreated at boot if empty.

The only problem I understand is that thea builds cannot be provided if the builder cannot test his build.

A ROM builder will however never be able to test his build on Asia/USA/China/Europe mobile networks, and only users can give feedback.

Then should each thea Moto G owner try to make his own build for his personal use ?

May be not the best solution.

To be investigated => how to provide a thea build based on titan build with very limited effort.

May be the builds should be stamped something like LineageOS_thea_totally_unoffical_very_dangerous.zip to be sure users are very well informed of the risk they take by installing a thea build which is not "official".
[Moto G 2014 LTE Android Development] s_dino:
@ Rox5

I has flashed lineage-16.0-20190311-UNOFFICIAL-titan on my XT1077, sim1 can be detected, but sim2 can't, is there need something to do? or just one sim card can be used. thanks!
[Moto G 2014 LTE Android Development] Rox5:
Difficult to say because I even don't know if Dual SIM is working on "unofficial" LOS_16_titan build (I have a XT1072 mono SIM).

However, dual SIM detection problem seems to be very common.

https://xdaforums.com/moto-g4-plus/help/moto-g4-plus-sim-card-detected-flashing-t3685847

https://forums.lenovo.com/t5/Moto-G...SIM-card-not-detected-dissapears/td-p/3399130

etc etc....

But in your very specific case of titan build on thea model, did you really really wiped everything before reboooting : all data + cache + dalvick-cache + modemst1-2 ? ...assuming you saved your precious data before, of course (...)

Cannot tell more.
[Moto G 2014 LTE Android Development] Numberone2022:
I gave up ... tried and did not detect my SIM ... the funny thing is that the tolkit of chip 1 appears ... I only did lineage 16.0 installation without gapps and root

I forgot to inform my MOTO g2 thea is the xt 1078

---------- Post added at 04:06 PM ---------- Previous post was at 04:03 PM ----------

I already downloaded aicp and also presents the same problem .... only the toolkit of chip 1 appears .... and the data, calls, sms do not work and does not detect the chip 1 nor the chip 2
[Moto G 2014 LTE Android Development] s_dino:
I did everything, but I can't find the Sim 2 setting, it seems like a single Sim Phone.
[Moto G 2014 LTE Android Development] Numberone2022:
[MENTION=5895297]gothicVI[/MENTION] [MENTION=5706262]Rox5[/MENTION] I contacted [MENTION=7344859]RenanQueiroz[/MENTION] in the forum .. It could help in the development for thea ... Any bug fix in this rom of the 24th ???
[Moto G 2014 LTE Android Development] AndroMani:
Hi gothicVI,

As I am using Oreo from LuK1337 without any major issues, I didn't try any other Oreo builds.

I also noticed that development for Moto G2 4G Thea device was stopped almost a year ago. There are no stable builds of Oreo ROM OR Pie release for Thea.

So, Thea seems to have reached the end when it comes to active Android development. However, I see some Pie ROM builds released for the 1st Gen Moto G, which is Peregrine.
[Moto G 2014 LTE Android Development] Numberone2022:
unfortunately .. works better than lineage 14.1 ???

How do I make port 15.1 with updated security patch?
[Moto G 2014 LTE Android Development] Rox5:
The vendor mismatch error comes from framework-res.apk, but why this error ? Still unclear since March 2018.

framework-res/res/values/strings.xml:
<string name="lineage_system_error_manufacturer">A vendor image mismatch has been detected. Typically this means your vendor image is out of date. Please ensure your vendor image matches %1$s.</string>

The build process provides a /system/build.prop file with noticeable difference between both build versions:

lineage-15.1-20180313_131048-UNOFFICIAL-thea_unified

# begin build properties
# autogenerated by vendor_buildinfo.sh
ro.product.board=MSM8226
ro.board.platform=msm8226
ro.vendor.product.manufacturer=motorola
ro.vendor.product.model=thea
ro.vendor.product.brand=motorola
ro.vendor.product.name=lineage_thea
ro.vendor.product.device=thea
# end build properties

>>> NOT in lineage-15.1-20190317-UNOFFICIAL-thea

Then probably something wrong with vendor build setup.
[Moto G 2014 LTE Android Development] Numberone2022:
Bugs:: Offline Charger, video recorder, kernel linux permissive, SIM (SIM 1 and 2 is not detect)....