yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo Android Development] Coronado is dead:
Ok, install radios, then install rom.

Gonna be a fun day tomorrow, thanks CF. You are the man :)
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
New build Uploading now 1.3.5a Non-Verizon build. It is hard to get it to work for US and European users on other networks. When I 1st posted it I was thinking that it was going to need tweaking for all users. I think this build will fix it it will be up Soon. it is like 80% up now.
[Verizon Motorola Droid Turbo Android Development] joeriv5692:
When I installed the new radios and updated Verizon cf rom, I kept getting "Google gapps have stopped and Google play services have stopped. I dirty flashed, followed the instructions to a T and I got those messages. Any ideas other than fully wiping and clean install? Thanks
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
It will go away it was just the dirty flash. Go back into twrp and wipe cache. If you still get it go wipe cache and data on Google play services and the play store. Your not coming from CM are you? If so it may not like that.
[Verizon Motorola Droid Turbo Android Development] joeriv5692:
No cm on my phone. I'll go ahead and try that method. Thanks for all the hard work.
[Verizon Motorola Droid Turbo Android Development] cdudeman:
I installed the nonverizon as described, but I am getting no sim card and wifi is grayed out. I installed the img and radio zip beforehand. I have also installed the verizon build and still didnt work. any ideas?

EDIT: I flashed CM13 and was able to get everything working again. I am going to try and flash back to this rom and see if it is working now.
[Verizon Motorola Droid Turbo Android Development] roman.ramirez.12:
I always get the best results when I do a full wipe before flashing any one of CF's Roms. Whether or not I try a new Rom from CM or R Remix. If I backup and restore. Full wipe before restore and all is good. If you have a cloud storage or an on the go USB driver or ext SD card backing up and doing a full wipe should be no problem. Most times ,not all times, if you flash a ROM that everyone else is having no issues with, it's most likely you didn't do a full wipe before flashing.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Did u download the new build I just uploaded? 1.3.5a non Verizon?
[Verizon Motorola Droid Turbo Android Development] Wynnded:
Verizon wouldn't bother to waste the time and effort.
[Verizon Motorola Droid Turbo Android Development] cdudeman:
I originally installed the one you took down. I just got the new one installed and everything is working fine now. Thanks for responding and for all of your work.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Yeah seems it did not like other sim cards on the one I took down. Think this build will work real nice for all non verizon users.
[Verizon Motorola Droid Turbo Android Development] gangrenius:
CF do you know where all these trusted credentials came from I went to try and take off my lock screen and it said I could because of 1of 3 reasons accessibility encryption which I don't have or entrusted credentials which I never had but all the sudden have tons of trusted credentials in a list I have no clue where it came from!
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Well there not in there as part of the firmware 100% came from your apps you installed.

Some apps that will do this. VPN, Tor, firewall apps, data saving apps,
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Holly crap dude.. I went over to the other threads why did you even ask me where they came from then you posted this stop wasting my time

You posted QUOTE=gangrenius;66904881]I block access to this app with a firewall! I personally have seen them use the app to reactivate an app on my gf turbo! It also asked me for root access one time I had to deny it.[/QUOTE]

Where do you think it came from? Just in case you missed it firewall app is the key here.
[Verizon Motorola Droid Turbo Android Development] Steve One:
I always clean flash and then set up as a new device without any problems. Thank you very much for sharing this with all of us Sir.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
So this update ota looks like we also have the new Google keyboard I need my dark theme back. Well here is the information on the new update for this.

http://9to5google.com/2016/05/02/google-keyboard-5-0-features/
[Verizon Motorola Droid Turbo Android Development] soccertolive:
Just wanted to say thank you for the update! Just did a full wipe/clean flash, everything so far is working flawlessly. You are da man!

[MENTION=6076132]computerfreek274[/MENTION]
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Arabic fonts I believe it is fixed and this version. 1.3.5 Verizon and Non-verizon builds.
[Verizon Motorola Droid Turbo Android Development] joekitch:
Since the small update from Verizon my phone will not charge to 100% on a standard charger I only use it overnight and if I check it straight off the charger it says I have 7hrs of battery left wtf I have been on 1.2.9 since it was available it worked great for me now the last two days something shady happened since the vzw update I don't trust them !!!
[Verizon Motorola Droid Turbo Android Development] Metfanant:
speaking of the new Google keyboard...anyone else having issues swiping between the emoji pages?...

like it seems like your finger needs to slide a significantly further distance to get the page to "turn." it crops up when trying to rapidly scroll through the emojis to find the one youre looking for...

im almost positive its nothing to do with the ROM build because everything else works as intended so im thinking its the app update...
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Let me try!

????

Seems it is only doing it on the flags on me but I do is what u mean.
[Verizon Motorola Droid Turbo Android Development] Wynnded:
I had the keyboard prior to the Verizon update, and I noticed that as well. You have to be much more... Deliberate.
[Verizon Motorola Droid Turbo Android Development] Metfanant:
does it equally on all the pages for me, but im glad others notice it, and im not crazy

its not really a Verizon update, its Google updating their keyboard...but yes, deliberate is exactly how to describe it...prior to the new update it only required a "flick" to move the page, just like homescreens in the launcher...now you REALLY need to swipe a much further distance to change pages
[Verizon Motorola Droid Turbo Android Development] gangrenius:
Where do you think it came from? Just in case you missed it firewall app is the key here.[/QUOTE]

Dude why are you trolling my convo with someone else about the My Verizon app? It had nothing to do with what I asked you! What's wrong with you guy?
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Dude why are you trolling my convo with someone else about the My Verizon app? It had nothing to do with what I asked you! What's wrong with you guy? [/QUOTE]

Just trying to help you asked I helped I answered everyone one of your questions. I was not trolling I was on that thread and why post a reply there taking up space there. Why not put it here where it was 100% relevant to your question.

Your welcome.
[Verizon Motorola Droid Turbo Android Development] gangrenius:
CF please go back and reread that thread I was commenting on a guys post about the My Verizon app and conspiracy theory.... I said I block it with a firewall app. Jeez man give me a break. By the way thanks for the rom it's doing better than all the others especially on battery it seems
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
The firewall app is where I was saying that you most likely gained the trusted credentials you where asking about. I am just trying to help you understand where they came from that was your question.

Your right battery seems to be fixed also advanced calling is working great even in my low 4g lte area.

Anyways happy it is working good for almost all users. I can now focus on my home life spring cleaning and more. Till we get marshmallow!!!
[Verizon Motorola Droid Turbo Android Development] joeriv5692:
CF, did a full a wipe and all is good! Thank you for everything. [emoji41]
[Verizon Motorola Droid Turbo Android Development] lukappaseidue:
Hi CF

I have some difficult to flash latest CF135a non verizon.

I am coming from stock rooted and unlocked

go to TWRP Official 3.0.20

wipe cache, dalvik, data, system

flash zip with modem and wipe cache and dalvik

flash CF135a Non verizon latest version and wipe cache dalvik

Reboot

I can choose language but I can see the my sim card is not recognized ... after several minute a warning show that there is no SIM, so try activating by Wifi, as suggested... but even Wifi in non available.

Please, help me

Where am Idoing wrong?
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
I am starting to wonder if the new modem is not liking the non Verizon sims.

After your flashed the ROM reflash the radios and reboot see if that helps
[Verizon Motorola Droid Turbo Android Development] lukappaseidue:
Just done it

but no luck

---------- Post added at 07:38 PM ---------- Previous post was at 07:30 PM ----------

how to return back to stock .44 ? (SU4TL-44 Stock Image for XT1254)
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Can u please flash the Verizon build of 1.3.5 .

Also under network select the last one not global and see if it finds your sim then
[Verizon Motorola Droid Turbo Android Development] lukappaseidue:
I am downloading it
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
If you still have the other build in goto settings then more then Preferred Network and set it to the last one.
[Verizon Motorola Droid Turbo Android Development] lukappaseidue:
@ now I just go back to stock .44 and sim is rightly recognized
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Ok I will keep looking into it. Sorry don't know why .49 is doing this to non Verizon users even the Verizon build is doing the same thing I don't get it.
[Verizon Motorola Droid Turbo Android Development] lukappaseidue:
I am finishing downloading verizon 135 version and let you know how it goes
[Verizon Motorola Droid Turbo Android Development] RLShiftyDoggit:
Hey [MENTION=355004]Computerfreak[/MENTION]274 is there anyway to just flash the radios if someone is running CM/RR?
[Verizon Motorola Droid Turbo Android Development] jbeenemd:
I was on 1.30 Non-Verizon. Flashed the radios and image. Cleared cache, etc. Just for grins and giggles rebooted to see if just doing that helped with reception. Dangit, no radio or wifi. Went back and installed the ROM. Cleared everything. As before no radio or wifi. Checked the image of the radio file and MD5 matches. Reflashed it a couple of times. And on it finally worked. I think it is something with the radio image and not the ROM. Been running all day without issues on 1.3.5. Will try the Non-Verizon ROM tonight.

Sent from my Moto Turbo
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Don't know I don't use cm or RR check over on there threads to see if they he new modem is work.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
I guess the that can be the case. Check your radio build numbers maybe it is not taking on 1st flash. Hard to tell on my end as I had to do stock + .49 update in that order as I had to build the rom from that. So I did not flash it from twrp.

Maybe it is not flashing modem.img right you can do.

Fastboot flash modem modem.img from bootloader.

Get the modem.img from the .zip of my IMG pack.
[Verizon Motorola Droid Turbo Android Development] RLShiftyDoggit:
I haven't seen anything on it over there yet (the reason why I thought to ask you) do you have just the modems in a flashable zip without the ROM update that I could try what's the worst that would happen needed to restore to a back up lol
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Under settings and about what is your baseband version I don't think your radios are updating.
[Verizon Motorola Droid Turbo Android Development] jbeenemd:
It is on the proper radio now. Forgot to mention that I flashed from TWRP 3.0.0.0. I think that I did check after the first flash and it did show the 49 radio. Was going to flash back to 44 but kept trying with the 49 IMG until it worked. Why it worked after 3 attempts, I don't know. Cleared cache and Dalvik after each flash. Same procedure each time. So have no idea what I did wrong the first two times.

Sent from my Moto Turbo
[Verizon Motorola Droid Turbo Android Development] pete355sb:
I apologize if I'm asking the obvious but I'm a little slow lol. With the new bootloader and radios should we stay on your latest rom and any other rom moving forward? Thanks Pete

---------- Post added at 01:38 AM ---------- Previous post was at 01:05 AM ----------

How do I check my radio and bootloader to make sure I did everything right? My phone works great as it always does with your roms and I was just wondering how to double check myself. Thanks Pete
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Yes I will keep my Tom's updated to Verizon updates do just stay with it. I am not saying that you have to take every update I post. Most if my updates are just tweaks anyways unless there was something major I will post that if info. Let's up the next time you flash one of my Tom's it us marshmallow!

To check your radios go to settings then about and somewheres in there look for baseband ending in 16.03r
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Yes see my op it is with the 1.3.5 folder on my Android file host.
[Verizon Motorola Droid Turbo Android Development] RLShiftyDoggit:
OK I'm going to assume this radio zip is for Verizon users right?
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Well droid turbo is a global phone so no it is for the droid turbo it is the newest radios from Verizon/ Motorola from ota .49 update. I suppose you can say just Verizon seeing the droid turbo is a Verizon only phone.
[Verizon Motorola Droid Turbo Android Development] lukappaseidue:
this is what i can read:

MDM9625_104651.11.05.16.03R QUARK_ CUST

Now I am on 135 verizon build and modem is working (GPS not tested)

No APN (But I know this)
[Verizon Motorola Droid Turbo Android Development] gangrenius:
I wanna flash a Tom! Is that new? ???
[Verizon Motorola Droid Turbo Android Development] RLShiftyDoggit:
OK so these will work for Verizon users as well as non Verizon users I take it

---------- Post added at 11:58 PM ---------- Previous post was at 11:43 PM ----------

OK flashed it on RR works just fine
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
So your good with modem. I don't know why it is doing this with no sim I think you can try and reflash Non-verizon build without wiping anything but cache I think it may work for you now. Last night I took my dim card out stuck an old T-Mobile card in I got no sim I left it in and a few hours later it was working. Has something to do with .49 update and most likely with the sim manager app. I will keep looking into it.
[Verizon Motorola Droid Turbo Android Development] lukappaseidue:
well. waiting for your reply

I think to not flash non verizion version, as at now everything is work good.

Thank for your work

Luca (from Italy)
[Verizon Motorola Droid Turbo Android Development] platypied50:
I hope I'm wrong, but for anyone who has been using tap-to-pay through the Capital One app, I suspect that the Verizon update implemented here finally flags our unlocked bootloader phones and conveys this to the app. I've been getting along great using tap to pay using the Cap One app, as long as I kept Supersu disabled after making my changes. For the first time, with Supersu disabled tap to pay attempts using this app prompts the dreaded "suspected root" message and denies its use. Ouch. I will go home and clear all caches, etc., and see if I can spot any other reason for the new failure. I updated to 1.3.5 (and radios) last night. Darn!
[Verizon Motorola Droid Turbo Android Development] ahaynes42:
I just tested mine and it's still working on 1.3.5. This may be that I have the xposed module root cloak hiding root from the app. It doesn't work with Android pay but it's still working for Capital One wallet.
[Verizon Motorola Droid Turbo Android Development] platypied50:
I hope you are right. I haven't been using that cloak module. That module never worked for me hiding enabled SU. I didn't care, because I didn't really have a need to have root running at all times. What I'm worried about is that it may now be detecting Xposed. SU was disabled when the rejection occurred. I'll keep tinkering. Your message is reassuring.

---------- Post added at 06:37 PM ---------- Previous post was at 06:17 PM ----------

Also, very quickly, CF, I just noticed that the Play Store is now showing me an update for Verizon apps: Cloud, Messaging and Support & Protection. Were these apps disabled in 1.3.0? I'm trying to figure out if these were amongst some of the bloat apps that are safe for removal and whether I should disallow the updates. Is 1.3.5 as debloated as your earlier versions? Will you be creating a battery saver version of 1.3.5? Thanks so much for the great ROM.

By the way, I sent you a small donation via PayPal about a month ago in appreciation. Great job!
[Verizon Motorola Droid Turbo Android Development] Wynnded:
1.3.5 isn't debloated....yet, CF hasn't had the free time. I think that Cloud, Messaging and Support & Protection were removed, BUT My Verizon Mobile is required for Advanced Calling to function, and it's an update to the app. I got it shortly after the OTA dropped. I just try to not notice it in my app drawer.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
If you guys are looking for the 6.01 emojs you can flash this one here. I did not include them in 1.3.5. I will at some point unless we see a MM soak test next week. If a MM soak test comes you can bet your ass I will have a ROM within a day or two.

I know 1.3.5 is not as clean as the other builds I am aware of that and I posted that in the change log. I will also work on that next week just a few more apps needs to be removed from 1.3.5.
[Verizon Motorola Droid Turbo Android Development] Steve One:
Didn't work for me CF sir.

---------- Post added at 11:41 AM ---------- Previous post was at 10:55 AM ----------

May be needs to be baked in.
[Verizon Motorola Droid Turbo Android Development] iCe87:
hi guys i've tried to install .49 radio package but sim and wifi are not working.. [MENTION=4740437]Baseband[/MENTION] i've an empty string and also restoring a previous backup i can't resolve! any ideas? i'm on 1.3.5 non-verizon
[Verizon Motorola Droid Turbo Android Development] jbeenemd:
Ice87, I had to flash it 3 times before it worked for me.

Sent from my Moto Turbo
[Verizon Motorola Droid Turbo Android Development] iCe87:
thanks for reply..for me is about ten times that's not working! :mad::mad:
[Verizon Motorola Droid Turbo Android Development] jbeenemd:
Did you clear cache and Dalvik before and after flash? I used the zip to flash from TWRP 3.0.0-0

Sent from my Moto Turbo

---------- Post added at 11:04 AM ---------- Previous post was at 10:58 AM ----------

Also after flashing, turn it off and reboot. Let it sit for a period of time. Might need to repeat this process one or two times.

Sent from my Moto Turbo
[Verizon Motorola Droid Turbo Android Development] iCe87:
seems that modem.img can't be wrote on system..also by fastboot flash!

---------- Post added at 06:33 PM ---------- Previous post was at 06:22 PM ----------

yes i've tried with wipe..but seems that baseband remain empty
[Verizon Motorola Droid Turbo Android Development] jbeenemd:
I'm stumped. I would try going back to the 44 radios to see if you can get your phone back and functional.

Sent from my Moto Turbo
[Verizon Motorola Droid Turbo Android Development] iCe87:
i've tried also to flash by fastboot and by recovery the 44 Package..nothing!
[T-Mobile Samsung Galaxy S6] Tcrazz:
I have the model SM-G920T S6, I was attempting to root my phone and must of used the wrong file and now its stuck in bootloop with "Recovery Is Not Seandroid Enforcing" in red in the upper left corner. I've attempted to put it into recovery mode to flash my ROM...which it wouldn't allow me. I'm not quite sure how to fix this issue, I've been trying some videos I've seen on YouTube with no results. Does anyone know the way to fix this?
[T-Mobile Samsung Galaxy S6] JustZaphod:
Use ODIN "Attached below" Flash the Stock ROM: https://www.androidfilehost.com/?fid=24269982086998283

That will get it back to Stock.. Just select AP

Then use odin to flash recovery..

Edit any recovery other than Stock will give you "Recovery Is Not Seandroid Enforcing", anyone with a custom recovery will have the same notification.. If you need further assistance, feel free to PM me..

Also, you asked a very easy question that you could of done on your own time, we all learned the same way..

XDA is not a place where simple questions get answered trust me on that one..
[T-Mobile Samsung Galaxy S6] Tcrazz:
I managed to get it to work last night after a bit of messing around on Odin. Thank you for the help though, I am new to the whole rooting phones, flashing the ROM, etc. Gradually learning but there are a many of things I don't know how to proficiently do.
[T-Mobile Samsung Galaxy S6] JustZaphod:
Flashing is a very dangerous thing to the uninitiated, before attempting to do something that can make your 700 dollar device into a worthless brick..

It is good to read as much as you can, don't rush the process or you will end up here asking a question that no one will answer..

I know because everytime I ask a question that to me appears to be legit, it ends up being ignored..

Now not everyone will ignore, but a good 98 percent will.. XDA is not a Support site, its a development directed at development..
[T-Mobile Samsung Galaxy S6] Tcrazz:
Are there any sites that you might suggest that would help me learn a bit more. At the moment I have just been trying to root my phone before attempting anything else.
[Galaxy Note5 Q&A, Help & Troubleshooting] RashidAlawadi:
I have the 920C variant and running arter97 ver. 9.4.

I've been having some issues with the auto brightness, because I usually keep it on auto and let it adjust accordingly, however, lately I've noticed that the auto brightness is not adjusting the brightness according to ambient light. Even when I put my finger on the sensor, nothing changes.

The second problem I have is when I turn my phone to silent and then back to normal, for some reason the notification sound slider stays mute, the rest go back to normal. I don't know what's causing this.

I'm not sure if these problems are related to the kernel or from the phone itself. I'm running rooted stock rom with arter97 kernel.
[Galaxy Note5 Q&A, Help & Troubleshooting] RashidAlawadi:
Ok I think I figured out the problem with silent notifications. I have Don't Pause app installed which was running in the background for some reason, so I uninstalled it, so sound is back to normal now I think. But I still have the brightness issue.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] RCizzle65:
I don't know what may have caused this, but, here's what happens for both phones. They both boot up fine. Then after a minute or two, I can't access the status bar, but the phone still functions. Eventually, the Xperia launcher crashes, then it says System UI crashes. Then I can't do anything, then the phone eventually reboots. This happened on my Z3C a week ago, and now it just happened to my daily driver, the Z5C. It takes a little longer for things to happen on the Z5C, as in, I have Twilight installed on both, and Twilight doesn't even boot up oin the Z3C, but it still boots on the Z5C before everything crashes. What the heck is going on with my phone?