[ROM][UNOFFICIAL] Lineage OS 13 For Obake [22/2/17]

[.: SID :.]

The August updates were finally merged and I built a new release yesterday evening

Many thanks for new builds. What's the difference between root and non-root build? Is it possible to use just Magisk with non-root build?

 

[pbarrette]

Awesome.
There are two files (one is with 'root' and the other without); which one should I use for my Droid Maxx?

Many thanks for new builds. What's the difference between root and non-root build? Is it possible to use just Magisk with non-root build?

LineageOS, by default, does not have root capability baked in, but a developer can include it via a compile time switch.
I prefer to have the LineageOS native root, but I understand that others may not want it included, so I build the image both ways.

The only difference between the two is that the "root" image has the native LineageOS root baked into the ROM and it can be enabled through the developer options in the Settings menu and the permissions are controlled via the native LineageOS user interfaces.

Other people have used Magisk with other LineageOS ROMs, so I assume that it will work with this one, but I haven't tried it personally.
If you are going to use Magisk, I'd start with the non-root version and use the flashable Magisk zip.

 

[s_u_n]

Which gapps should I use?

 

[pbarrette]

Which gapps should I use?

Hi s_u_n,

That's up to you. Personally, I use the Stock GApps with a "gapps-config.txt" file to exclude the apps I don't want.
Instructions for that can be found here.

 

[westhaking]

@pbarrette Thanks for keeping these updated with the latest security patches for those of us still using this phone but I have a small issue that maybe you can help me with. I read in an earlier reply that you are on Verizon. I am too but I can no longer receive text messages after flashing this. I can make and receive calls and send text but I just can't receive them. Mind to share your mobile network settings (with screenshots maybe)? What is your preferred network type in Phone Information after dialing *#*#4636#*#* What about APN settings? Thanks in advance and hoping you can help.

 

[pbarrette]

@pbarrette Thanks for keeping these updated with the latest security patches for those of us still using this phone but I have a small issue that maybe you can help me with. I read in an earlier reply that you are on Verizon. I am too but I can no longer receive text messages after flashing this. I can make and receive calls and send text but I just can't receive them. Mind to share your mobile network settings (with screenshots maybe)? What is your preferred network type in Phone Information after dialing *#*#4636#*#* What about APN settings? Thanks in advance and hoping you can help.

Hi westhaking,

1] Which ROM are you coming from?
I flashed LOS from the last Verizon stock ROM.
Did you do a full wipe before you installed the ROM?

2] Can you send MMS, but not SMS?
SMS but not MMS?
Do you have data working?

3] Screenshots of the test menu are attached.
The second screenshot shows the SMSC number which was populated by hitting the "Refresh" button.
I didn't input that anywhere. It was picked up as part of the standard registration.

4] The APN settings are tricky to get to and seem to be mostly disabled for CDMA phones on LineageOS.
I didn't enter APN info, but you could always try:
Name: Verizon
APN: VZWINTERNET
MMSC: http://mms.vtext.com/servlets/mms
MCC: 311
MNC: 480
APN Type: default,dun,supl

5] Is it possible that you configured this phone as a GSM phone previously?
You may need to change the boot-up carrier mode with "fastboot oem config carrier vzw".
Check "adb shell getprop ro.boot.carrier" and see if it returns "vzw". If not, run the fastboot command.

6] Your Verizon SIM should already have all of the settings you need on it. It could be that you need a new SIM.

 

[westhaking]

Hi westhaking,

1] Which ROM are you coming from?
I flashed LOS from the last Verizon stock ROM.
Did you do a full wipe before you installed the ROM?

2] Can you send MMS, but not SMS?
SMS but not MMS?
Do you have data working?

3] Screenshots of the test menu are attached.
The second screenshot shows the SMSC number which was populated by hitting the "Refresh" button.
I didn't input that anywhere. It was picked up as part of the standard registration.

4] The APN settings are tricky to get to and seem to be mostly disabled for CDMA phones on LineageOS.
I didn't enter APN info, but you could always try:
Name: Verizon
APN: VZWINTERNET
MMSC: http://mms.vtext.com/servlets/mms
MCC: 311
MNC: 480
APN Type: default,dun,supl

5] Is it possible that you configured this phone as a GSM phone previously?
You may need to change the boot-up carrier mode with "fastboot oem config carrier vzw".
Check "adb shell getprop ro.boot.carrier" and see if it returns "vzw". If not, run the fastboot command.

6] Your Verizon SIM should already have all of the settings you need on it. It could be that you need a new SIM.

1] I came straight from stock 4.4.4

2] I can send both sms and mms but if I receive any back it is only a single reply then no others show up. I only receive the remaining replies back after a reboot of the phone. After I reboot, all the text,mms that were previous sent (minus a single one) suddenly show up. It's seems that somehow after I get the first sms back that something (service?) is being killed and is only restarted after a reboot which then allow all backlogged sms to go through.

3] I flashed back to stock to look and the settings there and they are definitely different between stock and LOS13. The attached photos show comparisons of the #*#*4636*#*# settings (stock of the left/LOS on the right). The Set preferred network type available in stock is different than what shows up in LOS13. In fact, the LTE/CDMA/EvDo/GSM/WCDMA network type doesn't even show up on this page under LOS13. The SMSC was initially blank but I hit refresh and the same number showed up for me.

4] The settings you listed show up under the APN settings page for VZWINTERNET on LOS13 (I was able to get there through an app on the app store), but what shows up on Stock 4.4.4 is:
Name: Verizon
APN: VZWINTERNET
MMSC: http://mms.vtext.com/servlets/mms
MCC: 311
MNC: 480
APN Type: default,dun,stdhipri,supl

The difference is the addition of stdhipri in the APN type on stock.

5] The phone is provisioned for vzw as indicated by 'adb shell getprop ro.boot.carrier'

6] Went to Verizon yesterday and got a new SIM card and still no luck

Any ideas? Do you know what would allow only one sms to come through until a reboot is performed?

 

[pbarrette]

1] I came straight from stock 4.4.4

2] I can send both sms and mms but if I receive any back it is only a single reply then no others show up. I only receive the remaining replies back after a reboot of the phone. After I reboot, all the text,mms that were previous sent (minus a single one) suddenly show up. It's seems that somehow after I get the first sms back that something (service?) is being killed and is only restarted after a reboot which then allow all backlogged sms to go through.

If you send me a logcat showing the behavior, I can try to take a look at it to see if something is getting killed.

3] I flashed back to stock to look and the settings there and they are definitely different between stock and LOS13. The attached photos show comparisons of the #*#*4636*#*# settings (stock of the left/LOS on the right). The Set preferred network type available in stock is different than what shows up in LOS13. In fact, the LTE/CDMA/EvDo/GSM/WCDMA network type doesn't even show up on this page under LOS13. The SMSC was initially blank but I hit refresh and the same number showed up for me.

The options are the same. They just appear different in LOS. If the SMSC is good, you should be able to send and receive correctly.

4] The settings you listed show up under the APN settings page for VZWINTERNET on LOS13 (I was able to get there through an app on the app store), but what shows up on Stock 4.4.4 is:
Name: Verizon
APN: VZWINTERNET
MMSC: http://mms.vtext.com/servlets/mms
MCC: 311
MNC: 480
APN Type: default,dun,stdhipri,supl

The difference is the addition of stdhipri in the APN type on stock.

This shouldn't cause any problems. The absence of a HIPRI type is basically overridden by the presence of "default".

5] The phone is provisioned for vzw as indicated by 'adb shell getprop ro.boot.carrier'

6] Went to Verizon yesterday and got a new SIM card and still no luck

Any ideas? Do you know what would allow only one sms to come through until a reboot is performed?

1] It could be a modem initialization issue.
Do you get proper GPS location data?
I had to erase modemst1 and modemst2 to get GPS working correctly, so there may be a modem cache problem:
fastboot erase modemst1
fastboot erase modemst2

2] Instead of rebooting, have you tried toggling airplane mode?
Also, is WiFi off when you're receiving SMS's?

3] What's your baseband in "About Phone"?
Mine is MSM8960PRO_BP_23255.132.81.03R

 

[westhaking]

If you send me a logcat showing the behavior, I can try to take a look at it to see if something is getting killed.

I will see about getting a logcat. Never done it so I will need to read up on it.

1] It could be a modem initialization issue.
Do you get proper GPS location data?
I had to erase modemst1 and modemst2 to get GPS working correctly, so there may be a modem cache problem:
fastboot erase modemst1
fastboot erase modemst2

I had previously run these commands. GPS seems to be working fine.

2] Instead of rebooting, have you tried toggling airplane mode?
Also, is WiFi off when you're receiving SMS's?

Toggling airplane mode makes no difference. Wifi is usually on.

3] What's your baseband in "About Phone"?
Mine is MSM8960PRO_BP_23255.132.81.03R

I have MSM8960PRO_BP_23255.132.81.01R. I thought I had the latest with ...81.01R. Where did you get ...81.03R? Are you able to share it by chance?

 

[dDefy]

No Sound for incoming calls

I'm glad to see that this topic is still alive.
Installed both notz and pbarrette ROM's and they added a new life to my Droid Mini.
The only thing that is not working is that on incoming calls I don't have any sound nor the caller can hear me, the interesting part is that if I call them back all works as it should.
Any fix to this or what possibly could I've done wrong ?

Thanks, David

 

[pbarrette]

I will see about getting a logcat. Never done it so I will need to read up on it.

I had previously run these commands. GPS seems to be working fine.

Toggling airplane mode makes no difference. Wifi is usually on.

I have MSM8960PRO_BP_23255.132.81.01R. I thought I had the latest with ...81.01R. Where did you get ...81.03R? Are you able to share it by chance?

Hi Westhaking,

The .03R baseband came with the last official update: SU6-7.7, while .01R is usually associated with the SU6-7.3 update.

Edit: To get a logcat, do a reboot and reproduce the behavior, then run the command:
adb shell logcat -d -b all > logcat.log

I'm glad to see that this topic is still alive.
Installed both notz and pbarrette ROM's and they added a new life to my Droid Mini.
The only thing that is not working is that on incoming calls I don't have any sound nor the caller can hear me, the interesting part is that if I call them back all works as it should.
Any fix to this or what possibly could I've done wrong ?

Thanks, David

Hi David,

I haven't heard of this problem before. Before you flashed LOS were you on the latest official ROM (SU6-7.7)?

 

[dDefy]

Hi David,

I haven't heard of this problem before. Before you flashed LOS were you on the latest official ROM (SU6-7.7)?

I've had the 5.1.1 ASOP from notz, now I'm back on that.
Cleaned up all the mess, and pushed them trough TWRP, but still nothing.

 

[pbarrette]

All,

The September 2017 security patches have been released and I compiled a new ROM.
I am not going to release it at this time because the merged code completely breaks SSL certificate validations.
This means that virtually all applications and services that rely on internet functions are crashing.

I will keep tracking this and post an update when the issue is corrected.

 

[dDefy]

Still no idea what have could be wrong, I'm open to any ideas.
Thank you

 

[pbarrette]

Still no idea what have could be wrong, I'm open to any ideas.
Thank you

Hi David,

1] Which bootloader and baseband are you on?

2] What was the last official firmware version your phone was on?

3] Did you do a clean install of LOS 13 or are you trying to install over CM-12?
By clean install, I mean:
a] Wipe of System, Cache, Dalvik Cache, Data, Internal Storage.
b] adb push of "lineage-13.0-20170901-UNOFFICIAL-obake[-root].zip" to /sdcard
c] Optional adb push of your GApps to /sdcard.
d] Install the ROM
e] Optional install of GApps.
(I use a USB stick instead of "adb push", same thing).

4] Which dialer are you using? The LOS dialer or a Google dialer from your GApps?
If it's the GApps phone, which version of GApps did you install?

5] Does speakerphone work, bluetooth? Does the mic work if you switch between speakerphone or bluetooth? How about a wired headset?

The thing is, you're not really giving us any information to work with, other than "It doesn't work", so we don't really know what to tell you.
I've also got the Droid Mini, so I know that it can work.

 

[westhaking]

My texting issue are resolved now. I've updated my radio to MSM8960PRO_BP_23255.140.93.00R found in the stock 5.1 Moto X rom. I've been on a journey since my last post that involved lots of reading and running Moto X roms but now I'm back again with a newer and better radio baseband! Looking forward to the newest September patches....

 

[pbarrette]

My texting issue are resolved now. I've updated my radio to MSM8960PRO_BP_23255.140.93.00R found in the stock 5.1 Moto X rom. I've been on a journey since my last post that involved lots of reading and running Moto X roms but now I'm back again with a newer and better radio baseband! Looking forward to the newest September patches....

Excellent!

Moto X (2013 version) are a good place to look because the obake (Ultra, Mini, Maxx) platform uses the ghost (Moto X) kernel.

 

[dDefy]

Hi David,

1] Which bootloader and baseband are you on?

2] What was the last official firmware version your phone was on?

3] Did you do a clean install of LOS 13 or are you trying to install over CM-12?
By clean install, I mean:
a] Wipe of System, Cache, Dalvik Cache, Data, Internal Storage.
b] adb push of "lineage-13.0-20170901-UNOFFICIAL-obake[-root].zip" to /sdcard
c] Optional adb push of your GApps to /sdcard.
d] Install the ROM
e] Optional install of GApps.
(I use a USB stick instead of "adb push", same thing).

4] Which dialer are you using? The LOS dialer or a Google dialer from your GApps?
If it's the GApps phone, which version of GApps did you install?

5] Does speakerphone work, bluetooth? Does the mic work if you switch between speakerphone or bluetooth? How about a wired headset?

The thing is, you're not really giving us any information to work with, other than "It doesn't work", so we don't really know what to tell you.
I've also got the Droid Mini, so I know that it can work.

1. I don't know, using TWRP 2.8.4.0, baseband MSM8960PRO_BP_2323.011.75.00R

2. The last one was [ROM][5.1.1_r8][23/7/15] AOSP by notz

3. I've tried wipeing and formating before pushing using adb the lineage and the gapps images.

4. Have tried the LOS and Google's dialer too, using the open_gapps-arm-6.0-pico-20170918.

5. Yes, both the speakerphone and bluetooth works when I'm making the call, but when I get an incomming nothing works. Have to call them back

Thank you for your patience and asking the questions I never tought about.

 

[pbarrette]

1. I don't know, using TWRP 2.8.4.0, baseband MSM8960PRO_BP_2323.011.75.00R

2. The last one was [ROM][5.1.1_r8][23/7/15] AOSP by notz

This is likely your problem. That modem firmware seems to be associated with the original official 4.2.2 firmware.
Also, AOSP is not an official, Motorola firmware. I was asking which official, from the manufacturer, firmware version you had installed.

You should probably flash the last official firmware version to ensure you're on a current bootloader and baseband.

Instructions to flash stock firmware:
https://forum.xda-developers.com/showthread.php?t=2580060

Stock firmware image:
https://firmware.center/firmware/Motorola/Droid Mini (XT1030)/Stock/
You want: CFC_obakem_verizon-user-4.4.4-SU6-7.7-release-keys.xml.zip

Flash that and boot up at least once to ensure the modem gets initialized.
Then you can go back to fastboot and flash TWRP.
Finally, from TWRP, flash LOS and your GApps.

 

[dDefy]

Thank you for your answer, will try this.