yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo Android Development] y8s:
n00b question time:

Magisk 11.6 is out and allegedly compatible with the Droid Turbo.

Since your ROM is pre-rooted and we flash the Beta SuperSU, is it even possible to revert to a stock boot.img and use the built-in Magisk SU app which will allow Magisk to hide SU?

I assume a stock boot.img means losing all of your kernel work and maybe more.

(showing my lack of knowledge about the guts of android--I usually just carefully follow instructions for flashing stuff)

Thanks

y8s
[Verizon Motorola Droid Turbo Android Development] 3Dota:
this ROM isn't pre-rooted ... you need to doing step 3 to root this rom ...

so if you skip step 3 ... you'll have stock de-bloat

ps : apparently Magisk detect that bootloader been pre-patched by SU and you can restore untouched bootloader from https://xdaforums.com/droid-turbo/development/fxz-official-stock-firmware-6-0-1-mcg24-t3531571 ...

working just fine ...
[Verizon Motorola Droid Turbo Android Development] y8s:
I guess I misunderstood what "prerooted" in the room filename meant. Go look at the download link.

Still, I'd like to know what I lose with changing out my bootloader.
[Verizon Motorola Droid Turbo Android Development] 3Dota:
the bootloader should be stock ... not sure why magisk detect that it's been modified ...

[MENTION=6076132]computerfreek274[/MENTION] ... could you clarify this m8?
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
I would have to look at it my self but if it is talking about the bootloader then that has nothing to do with the ROM. Apps like Google pay and stuff is still not going to work unless you relock your bootloader. As for prerooted ROM the last build is kind of. Test by flashing 1.0.4-1.0.5 of my ROM only the new ROM pre-installs root when flashing it 1.0.7 and maybe 1.0.6 I can not remember right now. If it is because of the bootloader you will not get around that.

Yes my ROM is stock based rooted no depends on the build SE above.

I will check tomorrow myself if I get time.
[Verizon Motorola Droid Turbo Android Development] jchisena:
I re-flashed version version 1.06 of this rom, and Majisk 11.6 works ok and passes safety net. Android pay working as well.

1.07 for some reason Majisk works.. But detects supersu even when its not installed.. Fails safety net as well.

Just some info for those who may be interested.

Right now if you want majisk to work with safety.net, etc.. You can go with version 1.06. So far it seems to be working pretty well
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
I will be sure in 1.0.8 to make it without no root code as in 1.0.6.

Thanks
[Verizon Motorola Droid Turbo Android Development] Dabrador:
Quick question on this ROM. I installed the February OTA update version for rooted/unlocked Turbo's and since then battery life has gotten worse and the phone in general has become less than ideal, i.e. delays after screen selections, notification shade delays, screen stutters, etc.

Is it possible to install this ROM without doing a FDR? If so, is there anything additional that needs to be installed beyond the ROM itself?

Thanks in advance.
[Verizon Motorola Droid Turbo Android Development] jackle188601:
I know earlier it was stated not to run greenify. What are the thoughts on amplify or forcedoze?
[Verizon Motorola Droid Turbo Android Development] newbe1droidx:
Hey all, have a vzw newer antenna about 7 miles away in a small town. Went there had full 4g but no CDMA. Wiped everything and clean installed 1.0.7 pre rooted. Let itboot and signed in. While trying to update before installing apps, play store kept crashing. Cleaned cache on store rebooted tried again. Still crashed while trying to update apps before installing other apps. Decided to try aosp extended until can be figured out. Now see why advance calling over 4g is needed. Any idea how long before CDMA is shut down?
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
They will not shut down or off cdma it is used in tracphones to wireless alarm systems.

Sounds like your radios are off from using cm based roms i have seen this before where radios and phones get all messed up.

I think you should flash stock image firmware from very setup and test if everthing is good after that. Then refresh my rom.
[Verizon Motorola Droid Turbo Android Development] newbe1droidx:
K I try that tomorrow, refresh with yours, I thought about that but didn't do it. Haaa. Thanks for the help!
[Verizon Motorola Droid Turbo Android Development] y8s:
^^ This would explain why I had no data in the DC Metro system!
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
Less than two years.

YES, they will. 2019. Old news. Long been announced by Verizon. These articles are from July 2016 setting definite date:

Verizon will shut down its 2G CDMA network by 2019

http://www.digitaltrends.com/mobile/verizon-cdma-2g-shutdown/amp/

Verizon to shut down 2G CDMA 1X network by the end of 2019

http://www.fiercewireless.com/wireless/verizon-to-shut-down-2g-cdma-1x-network-by-end-2019
[Verizon Motorola Droid Turbo Android Development] newbe1droidx:
Volte it will be then! Thanks
[Verizon Motorola Droid Turbo Android Development] harrykon:
No service

Hi, I have the droid turbo marshmallow 6.0.1 , sunshine, twrp, and supersu 2.79 and xposed installed. I have not updated any ROM yet. The problem is I am in India but I do not get a service (though netwrok bars are visible) - when I try calling via VODAFONE i get "Cellular network not available"

I want to try your VOLTE ROM update so may be the phone will work via the new JIO network rollout since this network requires VOLTE

should I just install the RADIO files and flash the rooted version supplied by you. Let me know some direction to procede

Thanks
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
Sounds like an APN issue. When you see bars but can't actually connect it's usually an authentication issue.

In India, Vodafone mostly uses LTE bands 3 and 40. One article says

they also have LTE band 1 in one area

, but the Droid Turbo does not receive LTE bands 1 or 40. You'll get LTE only on LTE band 3. Vodafone of course also uses 2G and 3G, so you can also get coverage there for places that might have only LTE band 40.

This is why the XT1225 was released as the Quark for India two years ago (March 2015), as it at least has LTE bands 3 and 5 -- plus GSM/HSPA bands. That was before most carriers had yet rolled out LTE yet, but it was already known LTE bands 3 and 5 would be two of the LTE bands when they did roll out.

The XT1225 and XT1254/XT1250 all share LTE bands 2, 3, 4, 7.

The XT1225 additionally has LTE band 5 and 17.

___________________

FCC ID IHDT56PK2

____________________

The XT1254/XT1250 instead has LTE band 13 (Verizon LTE band), plus CDMA bands. While it does have some HSPA bands, there's not as many as in the XT1225.

FCC ID IHDT56PK1

______________________

The VoLTE in this Verizon stock-based ROM only works with Verizon -- just like the stock Marshmallow Verizon firmware you now have installed. Plus, with India JIO, the Droid Turbo XT1254 will only have one LTE band available of the three LTE bands JIO uses. Also JIO does NOT have any 2G or 3G spectrum, JIO is an LTE-only carrier. You will be in a world of hurt with JIO as you will not be able to make any phone calls and will only have data in areas where JIO has LTE band 3. (For instance, in the chart above, says JIO only has LTE band 40 in Punjab and Bihar.)

https://www.frequencycheck.com/carriers/jio-india
[Verizon Motorola Droid Turbo Android Development] harrykon:
Thanks for a detailed reply, however I am not talking of APN and net connectivity but regular voice calling. The sym card is inserted, but can not call or receive. OR

is there any way to change the band as you put so that the Motorola droid works with Vodafone for voice calling etc.
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
Don't be so quick to dismiss the APN possibility.

1) "connect" includes voice calling. Of course you have a SIM card in or you wouldn't even see bars. The problem is it seems you are not authorized to connect to the network, which is usually an APN issue or related.

2) Also make sure you don't have "LTE only" or something silly like that chosen in your settings. That would also cause voice calls to fail since you will not have VoLTE. You will only be able to make voice calls on GSM or HSPA bands.

There's one more thing to check...

3) Your phone may be defaulting to LTE/CMDA mode instead of LTE/HSPA/GSM mode. If so, you need to flash ADB instructions to change the settings. To enable SIM card auto-detection:

Droid TURBO XT1254 - but set as GSM phone:

fastboot oem config fsg-id verizon_gsm

This will make your Droid Turbo see your SIM card as being from an LTE/HSPA/GSM carrier. You are running stock Verizon Marshmallow firmware, and it's possible it's not detecting your carrier SIM card (Vodafone) as being LTE/HSPA/GSM. So, when you try to make a phone call, it can't use VoLTE and of course there's no CDMA signal available.
[Verizon Motorola Droid Turbo Android Development] harrykon:
Hey thanks. I did the APN settings for VODAFONE, but still no calling enabled. in the settings

Settings-->Cellular Networks-Select Network-> I set it to "GSM only", I tred AUTO also

Settings-->Cellular Networks->Preferred Network Type -> I set it to LTE/GSM/UMTS

Settings-->Mobile Network Type-->displays GSM=-99dBm

Settings->Network Operators->Displays all the operators (when I choose Vodafone) - a dialog pops up saying Registering on Vodafone In network- after about a minute a displays "your sim card does not allow a connection to this network." The sim works fine on my other phones. Also another message box pops up saying "Network Error" NO LTE/GSM/UMTS networks were found. Do you want to switch to Global mode.

The command which you have given "fastboot oem config fsg-id verizon_gsm" can it directly be given on fastboot or does anything have to be downloaded. I have fastboot workable.

Thanks for any help
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
It's a simple fastboot command, nothing is necessary to download.

However, downloading and flashing [MENTION=5747496]bhb27[/MENTION]'s Clean Modem file in TWRP beforehand can't hurt. It's for all Quarks. It clears the cache of your modem, so you have a "fresh" radio/modem. A lot of people use it when flashing ROMs as the modem sometimes hangs on to previous data and GPS then doesn't work. I know you don't have GPS issues, your issue is phone calls and connecting to your carrier. The fastboot command I mentioned may solve the problem, but flashing this file in TWRP recovery before running that fastboot command can't hurt and may help.

[MENTION=5747496]bhb27[/MENTION] Clean_modem_status

https://www.androidfilehost.com/?fid=24531035584725320

What happens when you switch to Global mode?
[Verizon Motorola Droid Turbo Android Development] harrykon:
I did both as advised. 1. Clean_modem_status as well as the fastboot oem config verizon_gsm

Rebooted the device. Chose Vodafone as the carrier - No change - "again your sim card does not allow a connection of this type."

Your earlier question - what happens in global mode - Basically network bars visible, can not dial or receive and in settings I can not choose/search a network carrier (vodafone) - the menu is grayed out.

Any other thing which can be tried out. ?. I am giving the fastboot output below for reference

The output for fastboot was

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

...

(bootloader) <UTAG name="fsg-id" type="str" protected="false">

(bootloader) <value>

(bootloader) verizon_gsm

(bootloader) </value>

(bootloader) <description>

(bootloader) FSG IDs, see http://goo.gl/gPmhU

(bootloader) </description>

(bootloader) </UTAG>
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
your PC does recognize your phone in ADB however? If you give ADB fastboot commands like to re-flash the modem, it confirms?
[Verizon Motorola Droid Turbo Android Development] harrykon:
Yes, to both. Sorry saw the reply late, i was checking the previous page.
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
Could the Vodafone SIM card be locked to the phone it came from? There's something that is not authorizing correctly...

That's why I thought it was an APN issue, you said it's not.

I thought maybe the phone's firmware is not auto-detecting the right caterory LTE SIM card (LTE/HSPA/GSM, not LTE/CDMA), so I gave you the fastboot command to force auto-detection of a GSM-based SIM card.

Do you have any friends who have Vodafone? Can you try their SIM card in your phone?
[Verizon Motorola Droid Turbo Android Development] harrykon:
No the Vodafone card is not locked. I can use it in other mobiles. I tried a different SIM card both from Vodafone as well as AIRTEL. The same issue.

Regarding APN, I do not know where it is an issue, I thought APN related only to the internet portion, and I wanted the call receive/make to function, hence I said APN would not be applicable. The IMEI is also not blacklisted - I checked :)

Something to do with VERIZON since it keeps a regular notification saying the SIM is not from VERIZON
[Verizon Motorola Droid Turbo Android Development] jbeenemd:
Maybe the Droid Turbo is somehow locked to Verizon .
[Verizon Motorola Droid Turbo Android Development] harrykon:
Is there any way to check this ? also what are the various alternatives now if any ?
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
No, it's not.

http://www.verizon.com/about/consumer-safety/device-unlocking-policy

This policy has been in effect well before the Droid Turbo was released in 2014. If it matters to you, the Droid Turbo was a premium "postpaid" device for Verizon. It was never sold under their "prepaid" program, which does allow locking for a period of time. The DROID TURBO is not and was never "SIM locked".

Verizon no longer locks their LTE phones as of 2012. Part of the FCC requirement for them to get additional spectrum. And there's plenty of Droid Turbo phones being used around the world and even in the U.S. (AT&T, T-mobile) with GSM-based carriers. Normally you just pop in a new SIM card and it works. But as discussed there's a fastboot command to force GSM SIM card detection. Sometimes people have to use that only when flashing a custom ROM, and even then not every time.

It really, really seems to be to be the auto-detect SIM card issue. It's looking for an LTE/CDMA SIM card (Verizon), when it has a GSM SIM card installed.

Run the GSM fastboot commands again, make sure you're doing it right. You mentioned some weird error message where it says it can't detect the SIM card slots? As a last resort, try reflashing the radio file itself. Here's the latest Droid Turbo XT1254 radio file, TWRP flashable:

It's some kind of permission/authentication issue. Your bootloader is unlocked, you have TWRP, you have SuperSu. You flashed [MENTION=5747496]bhb27[/MENTION] Clear Modem status file... Everything should be fine.

I really can't tell you much more. I hate to take up space here in CF's ROM thread, when this is not really a ROM issue. You are running stock Marshmallow. We will probably need to open a Q&A thread to continue the discussion.
[Verizon Motorola Droid Turbo Android Development] newbe1droidx:
OK clean flashed bootloader and radio, then prootedd 1.0.7. play store crashes while trying to do initial updates before installing my apps. Tried deleting data and cache on app. Wiped dalvick and cache, still crashing. It will let me install an app but won't mass update apps on its own. Google services is updated to 10......

Well now I can't update one by one anymore, hahaaaaaa
[Verizon Motorola Droid Turbo Android Development] vulcanrvn:
Hello,

I'm running 1.0.7 and magisk 11.6, everything is great except I can't update to magisk 12. I think it may tie to the supersu issue with the preroot mentioned earlier in the thread. Computerfreak I know you said that in 1.0.8 you'd fix the preroot issue which would allow us to install magisk and use magisk supersu. I wanted to know what the boot.img file actually does, and how to edit it ourselves if possible. Also does the kernel that comes with your rom have all the tweaks and changes you made on it to make the rom run the way it does? I installed your rom then BHB27-Kernel and was curious if this would have been pretty much the same thing as flashing a stock factory debloated image and using BHB27-Kernel.

Thanks
[Verizon Motorola Droid Turbo Android Development] newbe1droidx:
Well had to go back to RR-N, even non rooted 1.0.7 wouldn't work on play store. Kept crashing.
[Verizon Motorola Droid Turbo Android Development] Chilipepprflea:
Has anyone had issues with GPS/location after updating to 1.0.7 prerooted? I didn't have the issue with the regular 1.0.7, but I'm not sure if the issue started when I installed prerooted. I wiped data/all, but restored apps+data with Titanium Backup and am still having issues. I can't figure it what it could be.
[Verizon Motorola Droid Turbo Android Development] johnjingle:
I am using the prerooted 1.07 and using the GPS Status app right now. I am connected to 14 of 19 satellites and have no problems with location accuracy.

I don't know if it would make any difference, but you could try flashing the clean_modem_status.zip in TWRP. Just a thought.
[Verizon Motorola Droid Turbo Android Development] Chilipepprflea:
I think clean_modem_status.zip worked, thanks!
[Verizon Motorola Droid Turbo Android Development] jweakley:
I am having the same issue. I rooted in January and I would randomly have to close maps due to not responding. In the last few weeks almost every app, especially google apps are not responding. I have tried clearing the caches, factory resetting and reinstalling. I have also tried the updated version, not prerooted and am still having the same issue.

Do you think flashing the clean modem status would solve the issue? If so where do I get the file to flash? and is the process to flash the same?
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
It's a file by [MENTION=5747496]bhb27[/MENTION] who is the major dev for our Quark phones. He's not only the official TWRP maintainer, he also develops a custom kernel, and maintains two Nougat ROMs and had also maintained Marshmallow ROMs.

When flashing a custom ROM on our Quarks, GPS especially was a complaint. There were workarounds to fix it as early as 2015, but then [MENTION=5747496]bhb27[/MENTION] came up with the [MENTION=5747496]bhb27[/MENTION] Clear Modem File. You flash that in TWRP. In simplistic terms it clears the cache of your modem. It has helped countless people, with Droid Turbo/Moto Turbo/Moto Maxx. The file is for ALL Quarks, even though it's listed under Moto Maxx. Moto Maxx was the global name for Quarks -- Verizon demanded a fake "exclusive" name they could tout and so call theirs "Droid Turbo". (The U.S. Moto Maxx XT1250 is an exact clone of the Droid Turbo, same FCC ID, same radio bands -- runs on Verizon with Verizon SIM card -- except you can easily unlock the XT1250 bootloader for free.)

Often just that fixes any issues, but you can also then take the next step of re-flashing the most current radio/modem for the Droid Turbo.

ROMs don't have radio/modems included inside the ROM. When you flash a custom ROM, it uses the radio you already have. Clearing the cache, and reflashing makes everything new again.

* Here's the Clear Modem File, also called the Clean Modem file:

[MENTION=5747496]bhb27[/MENTION] Clean_modem_status

https://www.androidfilehost.com/?fid=24531035584725320

*Here's the latest TWRP-flashable Marshmallow radio/modem for the XT1254 Droid Turbo.
[Verizon Motorola Droid Turbo Android Development] bruceman200:
I tried both these methods posted by [MENTION=5901115]TheSt33v[/MENTION] with CF 1.0.7 ROM (fully wiped phone, never installed root or xposed) and safetynet does not pass. The same methods do work for me on the latest 100% stock rom.

According to user [MENTION=6682862]joekitch[/MENTION] in the the above quoted thread, they worked with CF 1.0.4 but stopped working with CF 1.0.5 and beyond. [MENTION=6076132]computerfreek274[/MENTION] or anyone else can you tell what would have changed between 1.0.4 and 1.0.5 to stop safetynet from passing even when the unlocked bootloader made invisible by these patches? Would love to use this streamlined CF ROM instead of stock if possible. Im also considering I could use 1.0.4 but would prefer the latest and not even sure if 1.0.4 is from before the latest verizon OTA update?

Any thoughts greatly appreciated!
[Verizon Motorola Droid Turbo Android Development] jweakley:
Well, I appreciate the help but I am still having the same issue. I flashed the Clear modem. It drastically sped my device up. Until then it would take a few minutes to reboot after clearing the cache. This was even after a complete factory reset.

When I realized I was still having the same issues I then cleared the cache, and flashed the latest TWRP radio. Cleared the cache again and rebooted. Everything seemed fine for a few hours. The GPS stayed locked, maps worked great, GPS continued to respond... but I soon had the recurrence of programs not responding. I am noticing it mainly with the maps and the phone. They are extremely slow to respond. In maps it will pull up the screen and show my previous location and the map but will not update for a few minutes. When I get the chance to force close the map it updates in the background. With the phone if I call a number or answer an incoming call the voice works, but the phone screen won't update. I just get the blue screen.

right now I am running:

Android 6.0.1 - patch level January 1, 2017

Version: l15.MOT.XT1254.0

Baseband: MDM9625_41.51.07.22.04R QUARK_CUST

Kernel: 3.10.40-perf-g1577812

hudsoncm@ilclbld33 #1

Mon Jan 30 08:46:52 CST 2017

System: 24.91.5.quark-version.veriszon.en.US

Build: Computerfreak274_.MM1.0.7_

This is the first device I have ever rooted so I do not doubt I have done something wrong. Any ideas?
[Verizon Motorola Droid Turbo Android Development] jchisena:
It works for me on cf 1.06.

It has to do with 1.07s hooks to SuperSU.

If you are failing safety net. Make sure it says magisk installed, not supersu. And make sure adb USB debugging is turned off. Plus a restart is needed if this was previously turned on.
[Verizon Motorola Droid Turbo Android Development] bruceman200:
Youre right! 1.0.6 works with the patch. Guess its just 1.0.5 and 1.0.7 that should be avoided for anyone looking to pass safetynet.

Thanks.
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
Well, your issues aren't GPS related.

You've got some kind of UI lag that is affecting your whole phone after it's running for awhile. I know Android is supposed to close apps in the background when you get low on RAM, but that is really what is sounds like. Sounds like your phone is getting bogged down and not enough free RAM.

When this starts happening, go to your recent apps view, see how much stuff is there still open, and swipe some closed -- see if that helps? I periodically hit "clear all" to close all the recent apps still running in the background which I am not currently using, and my phone has a snappier response. I know there are people who say not to do this and they are wrong. ;)

___________

You can also use the Kernel Adiutor app and adjust the "low memory killer" settings. Look at the Motorola default for our phone.... I would choose either "Agressive" or "Very Aggressive".

You would want to switch on the "Apply on Boot".

Here's the Google Play store version:

Kernel Adiutor (ROOT)

https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=en

but [MENTION=5747496]bhb27[/MENTION] offers a customized version with more settings which are enabled if your kernel can handle them:

KernelAdiutor-0.9.9.4.+39.BHB27-Mod.apk

https://www.androidfilehost.com/?w=files&flid=48767

And this is what those numbers mean -- but I can't take a screenshot of all the settings....