yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo General] iykeDROID™:
OKAY, THANKS.

I think all what I can do now is to Return it or to sell it.

Thanks to you all for your contribution.
[Verizon Motorola Droid Turbo General] ChazzMatt:
From our official Quark TWRP maintainer [MENTION=5747496]bhb27[/MENTION]...

TWRP update

twrp-3.1.0-0_MOD_1-quark.img

https://www.androidfilehost.com/?fid=457095661767143958
[Verizon Motorola Droid Turbo General] Einheit-101:
You should add to the FAQ "how to mount the system writable" because all bloatware returns after a reboot because system is read only, even when BL is unlocked/twrp installed/ xposed installed.
[Verizon Motorola Droid Turbo General] ChazzMatt:
Your statement is unclear. How are you attempting to remove the bloatware?

1) Do you mean it's read-only when you are in your normal Android GUI?

This would be the only time xposed is used so you must mean that, as xposed is not used within TWRP. That's what SuperSu is for, to give a file manager app read-write ability. I use Root Explorer, myself. For instance, when I attempt to replace the Wi-Fi .ini file with one that makes my Wi-Fi faster, my file manager (or maybe SuperSu?) says "This folder is read only, do you wish to write to this folder?" (or something like that) I click YES, and then I can replace the file in that folder.

You don't turn the whole system to be writable all the time. That's what SuperSu is for to elevate your root privileges when you need them -- like for removing bloatware or doing other functions. Apps I give SuperSu privileges all the time, can do their functions, but even the Root Explorer needs a YES from me to turn some system folders from read-only to writable.

So, again, I'm asking HOW did you attempt to remove bloatware? Because SuperSu normally asks you to grant first time permission to some app. Either you didn't see the request and it timed out (you can go to the SuperSu log and see past requests) or you didn't grant the temporary request to change the read-only permission of a folder so you could delete bloatware. But that's very puzzling because then it would have clearly told you that you couldn't do that. NO REBOOTING WOULD BE NEEDED.

So, are you trying to do this within the TWRP GUI?

2) Do you mean within TWRP?

Not sure why you then mentioned xposed in your post -- as xposed has nothing to do with TWRP. The purpose of this guide is not to tell you how to use TWRP or the TWRP file manager. Yes you have to mount data in TWRP. If I tell you where to buy a car, I'm going to assume you know how to drive a car. There's plenty of guides on how to use TWRP.
[Verizon Motorola Droid Turbo General] Einheit-101:
I simply use Titanium Backup with root access to uninstall bloat stuff.

It says uninstall successful, but that stuff comes back after rebooting. I will try again when Magisk is installed successfully.

I mentioned xposed because I had the case that it suddenly worked after I flashed xposed some time ago, I thought maybe xposed mounted the system writable. I guess I was wrong and something else made it work. But Idk.
[Verizon Motorola Droid Turbo General] ChazzMatt:
OK then that is a problem with Titanium Backup. I had an issue recently where I attempted to uninstall a system app (a camera) and I got the same result you did. Normally Titanium Backup is able to uninstall system apps.

But also, in Titanium Backup, you can make "system apps" into "user apps" and then attempt to do a regular uninstall?

OR you can use a file manager like Root Explorer (there are others, too, that's just my favorite), where you can go into system folders and remove those apps. Yes, you have to know where they live (which system folder), but Google is your friend. You can Google for that Verizon app and where it's located -- as I'm sure many other people have done the same thing!
[Verizon Motorola Droid Turbo General] Einheit-101:
K thx however I am almost sure it is possible with tbkp aswell, I will find a way and report why it did not work^^
[Verizon Motorola Droid Turbo General] ChazzMatt:
Since Titanium Backup does have root privileges I don't know why removing the system app did not work -- for me (on the camera) or for you. But the workaround to convert the system app to a "user app", then remove it should work.

And Titanium Backup will warn you if it does not have root privileges. If the app has root privileges (and you can also check the SuperSu settings to see, as a double check) and the app still does not do what it should, it IS a problem with the app itself. It's not a problem with this guide or how you are rooted or TWRP or anything else. Just to make that clear. ;)

Have you tried FREEZING the bloatware apps in Titanium Backup? Yes, I know that does not recover internal memory space, but it does "remove" them from working and from being seen by you. I froze that system camera app since I couldn't easily remove it, and I was afraid that for some reason that file needed to be there for any camera to work. I installed another Moto camera as a user app, and am using that. But I froze the system camera to make sure there are no conflicts and so I wouldn't see "two" cameras in my app drawer.
[Verizon Motorola Droid Turbo General] TheSt33v:
The glory days of TiBu are over. The app sucks now. Every time I try to make a user app into a system app, the thing processes indefinitely. Try this one https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp
[Verizon Motorola Droid Turbo General] ChazzMatt:
Yes, it does process indefinitely if you just let it run... but then when you reboot the phone, you see the app has now become a system app. ;) I let it run for like 5 minutes just to make sure everything has finished (even though it will NEVER notify you it has finished), before I reboot.

I do it all the time when I flash ROM updates, because I have a few app like my volume control app and my data manager app that work better as system apps. They get removed by ROM update flashes, and when I restore them via Titanium backup they are restored first as user apps (even though they were backed up as system apps), and I re-convert them into system apps. It's not my choice they are restored as regular user apps, that's just how Titanium Backup does it. It doesn't restore them as system apps, even though they were previously converted to system apps and the backup is of a system app. Go figure. :rolleyes:

I also find I can't restore app + data in one step with those apps. I have to restore the app, then restore data, then convert back to system app. Yes, Titanium Backup has some issues, but I've used it for years so I stuck with it.

---------- Post added at 11:45 AM ---------- Previous post was at 11:37 AM ----------

Thanks, that does sound like a great app. Always nice to have tool choices.
[Verizon Motorola Droid Turbo General] TheSt33v:
Yes, it does dump the app into the /system/app folder, but that hasn't been the correct way of doing that since kitkat. You still need to go in there with a browser, make a folder for the app and put the app in it, which is absurd considering this app has been the gold standard for this sort of thing for pretty much forever. How is such a basic, glaring flaw for such a commonly used operation still in there? Also, disclaimer, I've never used that other app. It just got good reviews and has been updated within the past year.
[Verizon Motorola Droid Turbo General] Einheit-101:
When I convert a user app into a system app, does that free some space on the user storage partition? Or are both app types on the same partition?

I have a feeling that there is a lot of unused space on my device that cannot be accessed because the system partition is way larger than needed
[Verizon Motorola Droid Turbo General] TheSt33v:
Yes it would. System apps live on /system and user apps live on /data, but there's two reasons why that doesn't matter:

1. The average android app is like, what, 10 MB? Add in a few MB for cache/app data and we'll say 15 MB for the sake of argument. Who cares?

2. The app will live in /system, but if you ever update that app, those updates live on /data. Officially speaking, the /system partition is never, ever modified except during OTA updates. So you're not really saving any space unless you never update that app.

As for the system partition size, there's not a lot you can do about that. If the system partition is 500 MB in size total, and you are somehow are only using 300 MB, that extra 200 MB still belongs to /system. So no matter how much you debloat, /data will be exactly the same size. The only way to change this would be to resize the system partition and extend the /data partition, but as far as I can tell, that's crazy difficult to do and requires editing the bootloader files.
[Verizon Motorola Droid Turbo General] sd_shadow:
I just freeze system apps with Titanium

works even if system is not writable

as long as it's rooted

no reason to move apps to system unless you are moving apps every time there is an update

---------- Post added at 12:02 PM ---------- Previous post was at 12:01 PM ----------

or there is a function that only works if it's a system app

---------- Post added at 12:08 PM ---------- Previous post was at 12:02 PM ----------

as far as move apps to /system

with Titanium not working

try unchecking

mount namespace separation

in SuperSU settings (it's checked by default)

reboot, then try moving apps
[Verizon Motorola Droid Turbo General] Einheit-101:
Hm thx that's nice to know. Anyway TiBkp reported it may not work with Magisk SU and it really doesn't. The name space separation solves it for super SU however.

I used root uninstaller and it's fine.

Now I try moving stuff like Pacific front (90MB) to system manually.
[Verizon Motorola Droid Turbo General] ChazzMatt:
I know we've already discussed a lot but here's also this suggestion. You can install this stock-based (Verizon Motorola XT1254) Marshmallow, debloated, tweaked ROM. It is NOT rooted by default, it only has root if you wish to activate root. It does have a tweaked kernel, audio tweaks and several other things (see below). Magisk even works with it, if that's what people want. You can also install xposed.

My point is for people with an XT1254 who need Verizon VoLTE who want to unlock bootloader to remove bloat on stock Marshmallow Verizon firmware, they might as well go ahead and install this stock-based ROM. It's already been done for you -- plus more. For people who don't use Verizon (and don't need VoLTE) or Verizon users who want even more options (but are willing to trade off VoLTE for those options), that's what

the other custom ROMs are for.

Computerfreek274_MM_1.0.7 Marshmallow 6.0.1 Tether,De-bloated,Root Volte 3/6/17

https://xdaforums.com/droid-turbo/development/computerfreek274mm1-0-android-6-0-1-t3503634
[Verizon Motorola Droid Turbo General] Einheit-101:
Thx but i am done with all my debloating stuff and finished everything :D

I am actually very impressed how well this new Marshmallow works. It is like a dream compared with crappy Lollipop. Especially with support of all new stuff (Magisk, bhb27 kernel.....)
[Verizon Motorola Droid Turbo General] lnlogauge:
Sunshine not working

Droid Turbo, 6.0.1. sunshine says it can't do it's thing. Anyone else having issue, or a solution?
[Verizon Motorola Droid Turbo General] TheSt33v:
Section 0, step 1, last 3 sentences
[Verizon Motorola Droid Turbo General] ChazzMatt:
RE: Sunshine not working

WHAT firmware are you on? The fact that you didn't mention that detail leads us to believe you already know the reason, or at least suspect it?

IF you even read the guide, then you know it matters very much which version firmware you are on. Sunshine only works on SU4TL-44, SU4TL-49 or MCG24.251-5.

(For reasons I won't go into here it's preferred you be on MCG24.251-5 when starting the bootloader unlock process -- even though Sunshine will also work on SU4TL-44, SU4TL-49.)

However, even if you are on a firmware EARLIER than SU4TL-44 (2015), then this guide will help you to update to the firmware version you need.

So, really this bootloader unlock guide will work on any Verizon Droid Turbo XT1254 firmware --

EXCEPT for the very latest from March 2017 (MCG24.251-5-5). You cannot downgrade a locked bootloader Droid Turbo to an earlier version firmware.

This is what [MENTION=5901115]TheSt33v[/MENTION] referenced in his reply, with my annotations in blue and red...

So, WHAT firmware are you on?

If you are on a lesser firmware than the March 2017 update (MCG24.251-5-5), there may be another reason Sunshine is not working, but it can be fixed. We still need to know the firmware version.
[Verizon Motorola Droid Turbo General] Spadizzle:
I will give 2 Disney world/land tickets that are one day any park and expire in about a year or so.

I updated to the infamous 5-5 and then I started thinking about custom. In the meantime I have totally enjoyed lineage on my Nvidia tablet. Anyways I'm looking for ideas! :)
[Verizon Motorola Droid Turbo General] TheSt33v:
No amount of Disney magic can save you from your fate, I'm afraid.
[Verizon Motorola Droid Turbo General] Azeem Shah:
Moderator Edit: Entire OP quote removed...

Hello

My framwre is MCG24.251-5-5

If I do this one framwere flash will not have my mobile bootloop
[Verizon Motorola Droid Turbo General] TheSt33v:
Yes. Not only will it bootloop, it will explode and destroy everyone you love.

Your questions were answered in the previous thread that you started. The answers will not change here. And don't quote an entire long post just to ask a question.
[Verizon Motorola Droid Turbo General] ChazzMatt:
Please do not quite the entire op for a question.

1) it's bad manners

2) We already know what it says.

If there's a specific section you wish to reference, you can quote that one part. But your question didn't need any quoting.

You can only reflash the complete version of the firmware you already have. MCG24.251-5-5.

If you tried to flash a lower version yes, you may have corrupted something. So, that may be the cause of your bootloops. Reflashing the complete version of the MCG24.251-5-5 firmware may fix that.

If that is your question? I'm not entirely sure of your question.
[Verizon Motorola Droid Turbo General] Azeem Shah:
My English is bad

I don't know what's you but Google translate very helping but not work properly

thanks

---------- Post added at 04:43 AM ---------- Previous post was at 04:10 AM ----------

Give me this framwere MCG24.251-5-5. Version link
[Verizon Motorola Droid Turbo General] catman1900:
Asopextended link is dead you should probably remove it. Otherwise thanks for the clear cut guide and all the ROM links :)
[Verizon Motorola Droid Turbo General] ChazzMatt:
That ROM still exists. The dev had it killed and resurrected it because he changed his XDA user name. So, the new thread (same ROM) now has a new link.

Here's the list of Nougat and Marshmallow ROMs for our device. All except one - CF's Marshmallow ROM -- is for all Quarks; his is for Droid Turbo only for now. The Marshmallow ROMs that not under current development I wouldn't bother with. For instance you will probably not find download links anymore for official CM13 (Marshmallow).

[ROMs][Quarks][List for Moto Maxx and Droid Turbo]

https://xdaforums.com/showpost.php?p=71821604&postcount=73

---------- Post added at 10:37 AM ---------- Previous post was at 09:57 AM ----------

______________

NOTE: For other people reading this bootloader unlock thread, this firmware I list below is only FOR REPAIR PURPOSES ONLY. It's for people with locked bootloader who already on this firmware. Their phones are somehow messed up because of either

a botched OTA of this firmware (something went wrong) or

they were already on this firmware and tried to downgrade to a lower firmware with a locked bootloader (which will mess up your phone).

If you are on this firmware with a locked bootloader, you can NOT unlock your bootloader at this point in time. So, IF you are NOT YET on this firmware -- if you have a lower, earlier version on your phone -- please do NOT flash this firmware below. Read this guide from page 1 and unlock your bootloader first.

However, if you are already on this firmware, you have a locked bootloader and you have messed up your phone, then re-flashing the full firmware version is the way to get back to a working phone. REPEAT: you will NOT be able to unlock your bootloader.

This note above is not for [MENTION=7075650]Azeem Shah[/MENTION]. We've established many, many times he's already on MCG24.251-5-5. The note above is for people who are on earlier firmware than the March 2017 MCG24.251-5-5. (Somewhat confusing, but the version right before this version is MCG24.251-5 , without the extra "-5". With MCG24.251-5, you can still unlock your bootloader!)

________________________

[MENTION=7075650]Azeem Shah[/MENTION], Here's FOUR places to download Verizon MCG24.251-5-5.

I would start with the XDA thread first.

[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5

XDA THREAD:

https://xdaforums.com/droid-turbo/development/fxz-official-stock-firmware-6-0-1-mcg24-t3569334

QUARK_VERIZON_6.0.1_MCG24.251-5-5_cid2_subsidy-DEFAULT_CFC.xml.zip

Download Link : https://mega.nz/#!dd4wXYiI!sRgo3aathlCDcg4YqBLxrRrd2ZK4u8BbnvHSCDoP7hE

______________

also:

XT1254_Moto_QUARK_VERIZON_6.0.1_MCG24.251-5-5_cid2_subsidy-DEFAULT_CFC.xml.zip

https://firmware.center/firmware/Mo...CG24.251-5-5_cid2_subsidy-DEFAULT_CFC.xml.zip

________________

and (very slow):

XT1254_Moto_QUARK_VERIZON_6.0.1_MCG24.251-5-5_cid2_subsidy-DEFAULT_CFC.xml.zip

https://www.filefactory.com/file/6q..._MCG24.251-5_cid2_subsidy-DEFAULT_CFC.xml.zip

______________

and

XT1254_Moto_QUARK_VERIZON_6.0.1_MCG24.251-5-5_cid2_subsidy-DEFAULT_CFC.xml.zip

https://easy-firmware.com/index.php?a=browse&b=file-info&id=80611
[Verizon Motorola Droid Turbo General] Azeem Shah:
Moderator Edit:

Please quit with the post quoting... thanks.

Thanks man

You're genius

Driod tarbo got my new life
[Verizon Motorola Droid Turbo General] BrianRC:
Need help installing TWRP.

I have a new Droid Turbo Android 5.1 Build number SU4TL-49.

I followed TheSt33v’s instructions on page 1 of this thread and successfully unblocked the bootloader. However, I am having problems with Section 2: Installing TWRP. It is not clear from my command prompt window if my flash was successful.:

----------------------------------------------------------

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot--suffixes: not found

(bootloader) has-slot: recovery: not found

target reported max download size of 536870912 bytes

sending 'recovery' (12488 KB)...

OKAY [ 0.633s]

writing 'recovery'...

OKAY [ 0.435s]

finished. total time: 1.078s

-----------------------------------------------------

In step 13 of the instructions TWRP does not boot.

I Tried Method 2 of TheSt33v’s instructions in a later version dated March 8, 2016, I opened SunShine and the message says “Your device is already s-off, SunShine has nothing to do.” So I am not able to obtain root access.

Am I doing something wrong? Is there another way to gain root access so I can install TWRP?

I’d appreciate any help you senior members can offer.

Thanks in advance.
[Verizon Motorola Droid Turbo General] ChazzMatt:
You install TWRP first, THEN gain root access by flashing SuperSu in TWRP.

You've unlocked the bootloader, so now you should be able to install TWRP.

Let's figure out why you haven't been able to install TWRP.

These are steps quoted from the op in this thread. Flash it again and be sure to follow steps 11 and 12, too. Because you will still be on the bootloader screen after flashing TWRP. AFTER you flash it, you will then use your volume button to arrow up (or down, doesn't matter) until you see "recovery". THEN, you will press the power button to choose that selection (recovery).

If you have tried this, what happens when you choose recovery and hit the power button to choose that selection?

Also, this may help below. I also wrote a guide for the other Quarks. After you unlock the bootloader, it's basically the same steps as for the Droid Turbo to install TWRP, SuperSu, etc.

Go to this page and looks at "Section 2: INSTALLING TWRP".

https://xdaforums.com/moto-maxx/general/guide-how-to-unlock-moto-maxx-moto-t3455341

It's the same steps but written a little differently. Maybe there's something you are not understanding and reading it in a slightly different style will help?
[Verizon Motorola Droid Turbo General] BrianRC:
Wow. Thanks for the fast response ChazzMatt!

I followed your instructions above and successfully installed TWRP. I used the same files I had downloaded last night so I am not sure what I did differently. I will continue reading your instructions to install SuperSu, etc.

Thanks so much!

Brian
[Verizon Motorola Droid Turbo General] kreg1744hp:
Need help
[Verizon Motorola Droid Turbo General] ChazzMatt:
Well, at least HERE you didn't quote the ENTIRE OP like you did on my Quark guide.

THAT is what you posted in my thread, after quoting the ENTIRE GUIDE.

WHY are you posting in Motorola Quark forums? On a PC, see the search box, upper right, on this XDA page? Type your device into that and it will take you to the HTC forum.

Or go to Google, type in your device and add the word XDA, then hit enter. You can easily find the correct XDA forum for your device and those users can help you.
[Verizon Motorola Droid Turbo General] LenAsh:
Chap - go to this FORUM, not here.
[Verizon Motorola Droid Turbo General] sefirosu0522:
Hey guys just a quick, hopefully easy question. I don't want to unlock anything. My dad lives in Uruguay South America. He's looking for a better phone than what he has. I'm traveling down there in a few months. If he just gets a new sim for it, will it work down there or do I need to do any of the steps in this thread?
[Verizon Motorola Droid Turbo General] TheSt33v:
No idea. You should probably compare the GSM and LTE bands that the Turbo is capable of receiving vs. the bands used by the carrier that your dad will be using.

But to answer your question, no. Nothing in this thread will help you with that.
[Verizon Motorola Droid Turbo General] sefirosu0522:
Thank you. I figured it out. Glad I don't have to do any of the stuff in this thread. Thanks again!
[Verizon Motorola Droid Turbo General] jcase:
I need a person competent with both adb/fastboot and has a droid turbo on MCG24.251-5-5 that has not been unlocked yet.

We are ready to release a new sunshine build for the latest turbo firmware, I just need someone to test.

Please email jcase@cunninglogic.com if you can test.

If you are NOT competent with adb/fastboot, or cant follow directions, please just wait until release, dont contact me
[Verizon Motorola Droid Turbo General] KARIM9377:
Hi [MENTION=2376614]jcase[/MENTION]

Good news about Droid turbo I am ready to help and sent email to you
[Verizon Motorola Droid Turbo General] TheDubsteppingNinja:
I'm willing to test it, sent an email an hour ago.
[Verizon Motorola Droid Turbo General] parker.stephens:
[MENTION=2376614]jcase[/MENTION] I just shot off an email about the new Sunshine build.
[Verizon Motorola Droid Turbo General] yakaaithiri:
[MENTION=2376614]jcase[/MENTION] .. i am interested to test. I just sent an email . thanks
[Verizon Motorola Droid Turbo General] yakaaithiri:
I got a new Droid Turbo as a gift from my Gf .

It comes loaded with the latest firmware and there is no further updates available for the phone.

When i try to download any app from play store or update any current app , i am getting error saying that it cant be updates and error No 400 and 961 .

i tried all the methods told in google with vain and XDA is my last resort.

Please help me in getting the device play services working again .

Something i observed.

1. Everytime i download or update a app , it will get downloaded twice before giving the error.

2. Apps get struck in INSTALLING screen after a while. This wont go off until is clear cache.

can someone help me getting this resolved , i cant send this phone back as its not warranty covered. Please help