Related
I am basically a noob when it comes to rooting, coding and other enthusiast level stuff !
But today I Unlocked the bootloader, installed CWM, Rooted(SuperSU) my Moto G(xt 1033) running 4.4.4 , My question is would I be able to get the Lollipop OTA ? If not what steps would I have to take to get it on my phone !
All help is appreciated , Thank you.
and this has been answered in about 3000 other threads already...
As @scott_doyland already said, this has been answered many times here. On the other hand, some of those answers are incorrect, so lets sum it up.
So far updating has worked with rooted phones as long as you had not touched any of the files that were going to be updated (like build.prop edits, new Adreno libraries or custom kernel and modules). However, you needed either stock recovery or PhilzCWM or TWRP. Stock CWM doesn´t work with OTA updates on Moto G.
With Lollipop it should be pretty much the same, but I have seen reports about TWRP and PhilzCWM not working this time. Not sure if was PEBKAC or there really is a problem, but stock recovery is always a safe way to go.
And one more thing. On Nexus 5 the update fails even if you just touch the system partition*. The update process doesn´t check for files anymore - it calculates a partition checksum and then updates it on filesystem level. We have not seen this yet on Motorola phones, but it may happen in the future. For now, rooted Moto phones are OK with OTA.
* Rooting installs su binary on the /system partition.
I'm fairly new at using custom ROMs on my phone (Moto G 2013 XT1304) and I want to get some answers that I've not been able to find, at least clearly, on my own. I'll ask all in one go in case others might benefit. I appreciate any help or confirmation in response.
GAPPS
Following the guide on xda, I installed CM 12.1 successfully and also installed the gapps package from July located in the cgapps site (can't post links yet). I was confused about the other option being called "OpenGApps" and thought they were the ASOP vs Google version. Once booted, Google Play Services updated but I've still had a few "Google Plays Services has stopped working" issues. My question is this, should I reflash and use the latest nano install from OpenGApps or does the play store update these relevant apps and framework once up and running anyway? Which is best?
Nandroid Backups
I want a way to fully backup the entire phone and system so that I can fully restore if something should get botched - something like a full drive image on a computer. Using TWRP backup, if I were to backup the system, data and boot partitions, would restoring those to a completely wiped phone bring it back to the state it was in when backed up? And do those partitions need to be wiped before restore or does the restore process do that anyway? Last, is is this the best way to do this sort of backup?
ROM updates
First, if "Check for Cyanogenmod updates" is set on the phone, and I have a snapshot installed, will this only provide an update if another snapshot is released? If not, how does that work since there is a new nightly releases every day.
Second, I've read a lot of negative about downgrading ROMs, but it seems ok to flash a newer version of the same one while keeping the data in place. Is this correct? Is there a "best practices" post on this somewhere?
I'm experienced with Linux, and feel somewhat at home with Android because of that, but I only switched to CM12.1 recently because Motorola had done nothing about the choppy bluetooth audio in the Lollipop update for the Moto G 2013. I use the feature extensively and it was left too broken to enjoy, but works perfectly in the CM ROM. Now I'm hooked and want to go further. Thanks for any help or direction.
Moto G 16MB (2013)
CyanogenMod 12.1 (Snapshot 11/17)
TWRP 2.8.7.0 (h2064)
I have a stock unrooted Motorola Droid Razr M xt907
4.4.2 OTA OS, but I DID remove a few stock items.
Sys Ver: 182.46.15.XT907.Verison.en.US
Kernel is: July 29 2014
I have never owned or worked with a smartphone before, but have OC exp dating back to MS Dos 1.x-2.1 and have some Linux exp using OpenSuse
If I understand correctly I need to back upi the system files BEFORE ROOTING the device to protect myself in the event I go to far while rooted and bootloop or brick the device.
I am trying to understand how to create a Nandroid backup without rooting, but I'm not understanding quite enough to have any great success.
I''d rather not wipe all the installed apps, but if I need to I'd like to know if I can
- back up apps and settings using a utility that does not require root access
- do a reset
- then back up the virgin unrooted 4.4.2 system files
- Then root
- Then install CM11 (KitKat 4.4.4 based)
- The restore the apps and settings fromt eh (non Nandroid) backup I need to do a real OTA reset because I killed some of the stock apps already. (At least, that's my understanding)
I really appreciate you all being here to help folks! Many thanks in advance!
XDA Visitor said:
I have a stock unrooted Motorola Droid Razr M xt907
4.4.2 OTA OS, but I DID remove a few stock items.
Sys Ver: 182.46.15.XT907.Verison.en.US
Kernel is: July 29 2014
I have never owned or worked with a smartphone before, but have OC exp dating back to MS Dos 1.x-2.1 and have some Linux exp using OpenSuse
If I understand correctly I need to back upi the system files BEFORE ROOTING the device to protect myself in the event I go to far while rooted and bootloop or brick the device.
I am trying to understand how to create a Nandroid backup without rooting, but I'm not understanding quite enough to have any great success.
I''d rather not wipe all the installed apps, but if I need to I'd like to know if I can
- back up apps and settings using a utility that does not require root access
- do a reset
- then back up the virgin unrooted 4.4.2 system files
- Then root
- Then install CM11 (KitKat 4.4.4 based)
- The restore the apps and settings fromt eh (non Nandroid) backup I need to do a real OTA reset because I killed some of the stock apps already. (At least, that's my understanding)
I really appreciate you all being here to help folks! Many thanks in advance!
Click to expand...
Click to collapse
Unlock your bootloader.
Flash the latest TWRP recovery in fastboot.
Make a backup with TWRP.
THEN flash SuperSU to gain root using the TWRP Recovery.
It's actually a great idea to hold onto a non-rooted backup, in case you want to return to stock one day to get an OTA update.
Okay, in looking for directions to unlock the bootloader, I'm jsut finding a lot of hits that begin y saying the phone needs to be rooted first, so I could use a push in the right direction there.
The forum linked here:
http://forum.xda-developers.com/showthread.php?t=2226729
should give you all of the info that you need.
xunholyx said:
The forum linked here:
http://forum.xda-developers.com/showthread.php?t=2226729
should give you all of the info that you need.
Click to expand...
Click to collapse
I'm so confused. The first instruction in the first post is to root the phone, but then how can I get an unrooted Nandroid backup?
I believe the answer I need may be covered here, but I'm not sure I follow how to flash this properly BEFORE rooting the phone. I intend to make a walkthrough on another forum once I get this all sorted, and would be happy to plug XDAD and you for the help.
There is a broken link in the guide you linked me to. I just wanted to make you aware. I have the motorola driver loaded on my Win 7 Ultimate Retail 64 bit driven PC, so I'm good, but the link for the drivers is returning a 404
I'm the one who is confused.
Sorry, I should have read the OP in that link better.
You can backup all of your data using ADB: adb backup -apk -shared -all -f C:\Users\NAME\backup.ab
And restore it using this command: adb restore C:\Users\NAME\backup.ab
Replace "NAME" with your Windows username of course.
There is a more comprehensive guide here.
Read the OP, then go to the last 10pgs or so to see if there is new info (didn't read that far, but the thread is still active).
Okay, I suspect this last link is probably more what I'm after, but before I do that, I'm HOPING it is possible to back up the installed apps and their respective settings first. The reason for this is that I really do want a squeaky clean, uprooted Nandroid backup of the last OTA update supported which, (no surprise), is 4.4.2, which includes the handy Heartbleed bug "feature" and makes the Razr M all but useless.
Of course, as we know, 4.4.4 runs very well on the Razr M and the Heartbleed bug is easily solved by it, but Motorola prefers you buy a new phone, so they introduce a bug, load it on everyone's 1-1/2 year old devices, and they refused to fix it by not allowing users access to the "new" unbroken OLD KitKat platform! You can only run that LAST version of the OLD KitKat on NEW HARDWARE!
The other tactic used on consumers by Motorola and others is not allowing customers to purchase new factory fresh batteries for their devices, whether "non-replaceable" or not. These are two strong-arm tactics adopted that now dominate cellular and other technologies.
I digress.
I am going to HAVE to restore this phone before making the Nandroid because I pulled some stock 4.4.2 Motorola firmware bloat out of it, adn now I need iot back for that backup to be truly virgin. :/
Soooooooo . . . .
The first order of business is to determine if I can add the stock stuff back, or if I have to actually do a reset on the phone. I fear adding the stock items back MAY still leave changes in the system folder, which is not acceptable to me. *IF* I CAN successfully add the stock bloat back in and get a clean Nandroid, I'd be happy about that, though I'd be concerned about it working properly none-the less.
This is why I ask if I can back up apps and app data and later successfully restore that stuff that was backed up under 4.4.2 once I have successfully loaded the (KitKat 4.4.4 based) CM11 Mod.
If the backup of apps and app settings WILL restore to 4.4.4, I'd like to:
- > back up all apps, app data adn user data > reset the phone loading the 4.4.2 OTA BONE STOCK > make my Nandroid of the bone stock unrooted 4.4.2 > Root > Load CM11 MOD ROM > Restore my apps and user data.
I will work on learning to make the unrooted Nandroid some while I wait for a reply, as I'm going to have to do that as a later step.
Giving this a try. I'm about to crash. I'm pretty zonked out.
If all that you want is to save apps and app data, and not system and boot partitions, then use the ADB commands that I posted. That will do exactly what you want.
Oh no no, that's not all I want to do by any means. I am going to load the KitKat 4.4.4 based CM11 ROM, but before I do that I want a clean OTA backup of the stock unrooted KitKat 4.4.2 so I have that to fall back on.
To that end, in preparation for the new ROM I'd like to back up all apps that are currently loaded along with the current app data, and also to back up all personal data.
Once that is done, I need to do a reset to get 4.4.2 back into it;s stock trim as this will be my original 4.4.2 OTA Nandroid.
THEN I will root and install CM11
Then, if it's possible, I'd like to restore all of my current apps and app data.
I've been working on understanding the steps needed to make that unrooted 4.4.2 Nandroid while awaiting suggestions about how to do the app/app data and personal data backup., as well as a yea or neigh about if the app backup can even be successfully restored under the new (4.44 based) os.
I can not install twrp recovery and make root (supersu) in the marhsmallow rom stock of my xt1225, when I install twrp and do root I have an eternal looping .. And I need to add virtual navigation buttons because the capacitive navigation buttons are failing and I need add in the build.prop.
I would be really happy if someone help me with a flashable [slim] stock rom or in any other way.
Thank you in advance for the help.
I'm using bhb27's CrDroid and it comes rooted and has on-screen navigation buttons in the CrDroid settings. Just follow the directions here: (https://forum.xda-developers.com/mo...crdroid-android-t3491257/page144#post71458779).
Guth13 said:
I can not install twrp recovery and make root (supersu) in the marhsmallow rom stock of my xt1225, when I install twrp and do root I have an eternal looping.
Click to expand...
Click to collapse
Are you using the correct SuperSu? You're using my guide?
UPDATED GUIDE: How to unlock your MOTO MAXX/MOTO TURBO bootloader/install TWRP/root
https://forum.xda-developers.com/showthread.php?t=3455341
If so, then you know with stock Marshmallow from Motorola you NEED a specific beta version of SuperSu for initial root. AFTER that, then you can update to newer versions of SuperSu. Go read that guide if you haven't. It was updated when Motorola released Marshmallow last July (2016).
I do have images with very old TWRP in another thread, but they're 4.4.4 Kitkat images from 2 years ago...
Moto Maxx - Moto Turbo XT1225 factory images (Mexico | Puerto Rico | India | Brazil)
https://forum.xda-developers.com/moto-maxx/development/moto-maxx-moto-turbo-xt1225-factory-t3078274
Be better if you flashed newer TWRP and used the correct SuperSu.
I use this method but I can not understand why infinite looping.
Do you have the rom 6.0.1 with patch of January (2017) ??
Would you like to do something like that in a ROM compatible with our device ??
https://forum.xda-developers.com/dr.../computerfreek274mm1-0-android-6-0-1-t3503634
Guth13 said:
I can not install twrp recovery and make root (supersu) in the marhsmallow rom stock of my xt1225, when I install twrp and do root I have an eternal looping ..
Click to expand...
Click to collapse
1) But you can install TWRP recovery, right?
It's just the SuperSu you are having trouble flashing? Please post a screenshot of the SuperSu file you are trying to flash. It should be in your Download folder. This would be the SuperSu file you are trying to "install" in TWRP.
Also post a screenshot of the TWRP version you are using, please.
Guth13 said:
And I need to add virtual navigation buttons because the capacitive navigation buttons are failing and I need add in the build.prop.
I would be really happy if someone help me with a flashable [slim] stock rom or in any other way.
Click to expand...
Click to collapse
2) If you want virtual navigation buttons, the easiest way is to install a custom ROM like RR 6.X or even a Nougat custom ROM -- not a stock-based ROM. Virtual buttons are an option in many, if not all the Quark custom ROMs.
3) Right now with TWRP you can flash any of the custom ROMs. You don't need to flash SuperSu. In fact on the RR 7.X, @bhb27 doesn't like SuperSu. You can get root from within the ROM if you want it on 6.X or 7.X ROMs.
4) Tell me why you think a slim stock ROM is what you need. Everything you have said so far points to a custom ROM.
Flashable stock ROMs are mostly for people who either get a custom ROM (LG devices where the bootloader is locked, but they can still get root and flash "images") or stock has some feature like VoLTE that can''t be ported over to custom ROMs (yet). That's the reason for the Verizon stock based ROM you mention below. Even then, many Droid Turbo users are still flocking to the custom ROMs because custom ROMs offer more features than stock -- even Verizon customers who could use VoLTE.
Why do you think there are SIX custom Nougat ROMs for the Quark? And in this forum there are NO "stock-based" ROMs? The only reason there's stock-based ROM over in the Droid Turbo section is because of Verizon VoLTE.
Back in late 2014 and early 2015 I had rooted stock ROM only because there were no custom ROMs. I ran xposed with Gravity Box to emulate a ROM.
I even flashed my Puerto Rico XT1225 and Mexico XT1225 to India Moto Turbo firmware so I could get 5.0.2. Motorola didn't release 5.0.2 until later for the Latin America XT1225, but it launched on Moto Turbo XT1225 in March 2015.
We then got CM12, and CM12.1. When CM12.1 was stable enough, I switched over and stayed on it for well over a year.
I wouldn't go back to stock if you paid me.
Guth13 said:
Would you like to do something like that in a ROM compatible with our device ??
https://forum.xda-developers.com/dr.../computerfreek274mm1-0-android-6-0-1-t3503634
Click to expand...
Click to collapse
Because custom ROMs are much better.
Do what I said up top, post the screenshots -- let's figure out your Supersu issues if you want, but it's not necessary to have root before flashing a custom ROM. And once a custom ROM is flashed, there's a root switch built in to most.
ChazzMatt said:
1) But you can install TWRP recovery, right?
It's just the SuperSu you are having trouble flashing? Please post a screenshot of the SuperSu file you are trying to flash. It should be in your Download folder. This would be the SuperSu file you are trying to "install" in TWRP.
Also post a screenshot of the TWRP version you are using, please.
2) If you want virtual navigation buttons, the easiest way is to install a custom ROM like RR 6.X or even a Nougat custom ROM -- not a stock-based ROM. Virtual buttons are an option in many, if not all the Quark custom ROMs.
3) Right now with TWRP you can flash any of the custom ROMs. You don't need to flash SuperSu. In fact on the RR 7.X, @bhb27 doesn't like SuperSu. You can get root from within the ROM if you want it on 6.X or 7.X ROMs.
4) Tell me why you think a slim stock ROM is what you need. Everything you have said so far points to a custom ROM.
Flashable stock ROMs are mostly for people who either get a custom ROM (LG devices where the bootloader is locked, but they can still get root and flash "images") or stock has some feature like VoLTE that can''t be ported over to custom ROMs (yet). That's the reason for the Verizon stock based ROM you mention below. Even then, many Droid Turbo users are still flocking to the custom ROMs because custom ROMs offer more features than stock -- even Verizon customers who could use VoLTE.
Why do you think there are SIX custom Nougat ROMs for the Quark? And in this forum there are NO "stock-based" ROMs? The only reason there's stock-based ROM over in the Droid Turbo section is because of Verizon VoLTE.
Back in late 2014 and early 2015 I had rooted stock ROM only because there were no custom ROMs. I ran xposed with Gravity Box to emulate a ROM.
I even flashed my Puerto Rico XT1225 and Mexico XT1225 to India Moto Turbo firmware so I could get 5.0.2. Motorola didn't release 5.0.2 until later for the Latin America XT1225, but it launched on Moto Turbo XT1225 in March 2015.
We then got CM12, and CM12.1. When CM12.1 was stable enough, I switched over and stayed on it for well over a year.
I wouldn't go back to stock if you paid me.
Because custom ROMs are much better.
Do what I said up top, post the screenshots -- let's figure out your Supersu issues if you want, but it's not necessary to have root before flashing a custom ROM. And once a custom ROM is flashed, there's a root switch built in to most.
Click to expand...
Click to collapse
I use RR 5.7.4 based on android 6.0.1 but I'm going to give this device to my mother because I bought a LTE MI4. And a slim rom stock I would add a navbar using a tutorial I saw on youtube. She already used and complained that the custom rom unloads very fast and takes time to load but her main complaint was of force closed. I can not report the closed forces because I use themes and applications with root access as well as I already got to use xposed in a RR (I am not currently using and I still suffer enough closed forces and other bugs). And I also believe that a slim rom stock would be very useful for a lot of us users. I've had several devices and have always seen a flashable rom stock and sometimes with a slim version.
I know how to install twrp, do root and use xposed but I can not do such thing in rom stock since its version with pacth of September 2016 (recently released with patch in January 2017) and in turn I could not do in previous version of android 6.0 .1. And my device has problems with the capacitive buttons.
I also tried copying the build.prop edit (added the capacitive buttons) and flashing via twrp but with no success. I've always used the official twrp. Do you think that if I use a twrp mod (has topic here in xda) can solve my problems ??
Do you disagree that a flash rom [slim] stock would be a way to reinstall the original rom even faster ??
Guth13 said:
I use RR 5.7.4 based on android 6.0.1 but I'm going to give this device to my mother because I bought a LTE MI4. And a slim rom stock I would add a navbar using a tutorial I saw on youtube. She already used and complained that the custom rom unloads very fast and takes time to load but her main complaint was of force closed. I can not report the closed forces because I use themes and applications with root access as well as I already got to use xposed in a RR (I am not currently using and I still suffer enough closed forces and other bugs).
Click to expand...
Click to collapse
Sounds like you need to do a clean install of the ROM? My wife and I are using RR 6.X Marshmallow on two XT1225 and we don't have any force closed apps. In fact it's so stable that's why I don't want to go to Nougat right now and I hope @bhb27 does at least one more update of that ROM.
In TWRP, you can clear all caches and reboot and that may help your issue, but since you are giving the phone to your mother, just do a clean install.
That RR 6.X ROM also lets you do virtual buttons. Have you tried using that feature?
Guth13 said:
I know how to install twrp, do root and use xposed but I can not do such thing in rom stock since its version with pacth of September 2016 (recently released with patch in January 2017) and in turn I could not do in previous version of android 6.0 .1.
And my device has problems with the capacitive buttons.
I also tried copying the build.prop edit (added the capacitive buttons) and flashing via twrp but with no success. I've always used the official twrp. Do you think that if I use a twrp mod (has topic here in xda) can solve my problems ??
Do you disagree that a flash rom [slim] stock would be a way to reinstall the original rom even faster ??
Click to expand...
Click to collapse
I'm a little confused here. Are you saying you want to go to a previous version of Marshmallow but can't? You obviously have an unlocked bootloader. You can even flash Kitkat if you wish, just omit gpt.bin.
Some patch from Motorola means nothing. You have an unlocked bootloader. You have god powers. I'm not sure why you are blaming some patch on not being able to root an unlocked bootloader phone. No one else has this issue.
You say you know how to root, but I have my doubts since you are having trouble flashing the version of SuperSu which is needed. Have you ever rooted stock Marshmallow on this Motorola device? When you unlocked your bootloader, what version of stock firmware were you on? Lollipop? The procedure has changed. That's why I want to see a screenshot of the version of SuperSu in your download folder you are trying to flash over your stock Marshmallow ROM. You can only root with ONE specific SuperSu version and you haven't convinced me you are using that version.
Guth13 said:
Do you think that if I use a twrp mod (has topic here in xda) can solve my problems ??
Do you disagree that a flash rom [slim] stock would be a way to reinstall the original rom even faster ??
Click to expand...
Click to collapse
Modded TWRP is always better than "official" TWRP. Until the recent 3.1 update, the official version was almost a year behind the modded versions. Even now, the modded version can do more stuff.
This is the most recent version as of the date I type this:
twrp-3.1.0-MOD_1-quark.img
https://www.androidfilehost.com/?fid=457095661767143958
This is the SuperSu version you should be using and ONLY this version until you achieve initial root. After you have initial root and reboot back and verify, then you can update to newer versions of SuperSu.
Download
BETA-SuperSU-v2.62-3-20151211162651.zip
Guth13 said:
Do you disagree that a flash rom [slim] stock would be a way to reinstall the original rom even faster ??
Click to expand...
Click to collapse
Why is how fast you install a ROM the question? How about how the ROM runs, what features it has?
Then why not flash @iiWoodstocK's stock ROM in TWRP? It's based on Brazil stock Marshmallow, but he adapted it so it would install/run on all Quarks, including the Droid Turbo.
[ROM][6.0.1][Stock][Odexed]MPG24.107-70.2 Brazilian 6.0.1 for XT1254[TWRP Flashable]
Stock 6.0.1 MPG24.107-70.2 (Brazil) for Verizon XT1254
http://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
You keep the radio you already have, but in TWRP you can flash that ROM and have stock Marshmallow Motorola firmware.
That ROM will work on all Quarks (XT1254/XT1250/XT1225). It has a custom kernel, and uses whatever radio you already have. But @iiWoodstocK made it specifically to work on the XT1254, since at that time Verizon had not yet released stock Motorola Marshmallow for the Verizon Droid Turbo.
He includes a script to run which debloats the ROM somewhat to remove apps most people don't need. Go to the thread and read. He obviously directed it to Droid Turbo users, to give them "stock" Marshmallow since it was MONTHS before Verizon did, but it will also work on XT1225.
However, it won't help you use virtual buttons instead of capacitive buttons like a custom ROM will, unless you install something yourself that does that. Custom ROMs like RR already have that functionality built in.
But it's a TWRP flashable stock ROM, which is what you seem to want for reasons I don't understand.
Now you may have solved the problem, I did not know there was a specific version of the supersu. The supersu I wore was the "SuperSU-v2.79-201612051815". I will now test this supersu that indicated me and I will come back to give the feedback. I always do a clean flash of rom marking all the sections restarting recovery, avoiding and doing rom flash, gapps and any necessary file after ..
Guth13 said:
Now you may have solved the problem, I did not know there was a specific version of the supersu. The supersu I wore was the "SuperSU-v2.79-201612051815". I will now test this supersu that indicated me and I will come back to give the feedback. I always do a clean flash of rom marking all the sections restarting recovery, avoiding and doing rom flash, gapps and any necessary file after ..
Click to expand...
Click to collapse
I said it many times. You aren't listening. That's why i asked to see screenshot for you to prove to me you were using the right version!
This was my original post to you and even the follow-up:
ChazzMatt said:
Are you using the correct SuperSu? You're using my guide?
UPDATED GUIDE: How to unlock your MOTO MAXX/MOTO TURBO bootloader/install TWRP/root
https://forum.xda-developers.com/showthread.php?t=3455341
If so, then you know with stock Marshmallow from Motorola you NEED a specific beta version of SuperSu for initial root. AFTER that, then you can update to newer versions of SuperSu. Go read that guide if you haven't. It was updated when Motorola released Marshmallow last July (2016).
Be better if you flashed newer TWRP and used the correct SuperSu.
Click to expand...
Click to collapse
Yes, all that important stuff was bolded and capitalized on that day.
You replied YES, you were using that.
ChazzMatt said:
1) But you can install TWRP recovery, right?
It's just the SuperSu you are having trouble flashing? Please post a screenshot of the SuperSu file you are trying to flash. It should be in your Download folder. This would be the SuperSu file you are trying to "install" in TWRP.
Click to expand...
Click to collapse
But I didn't believe you so I asked for a screenshot of the SuperSu you were using -- and you still said you knew what you were doing. And you wouldn't provide the screenshot, which made me very suspicious.
ChazzMatt said:
I said it many times. You aren't listening. That's why i asked to see screenshot for you to prove to me you were using the right version!
This was my original post to you and even the follow-up:
You said YES, you were using that.
But I didn't believe you so I asked for a screenshot, and you still said you knew what you were doing.
Click to expand...
Click to collapse
Congratulations my friend!! You solved my root problem. But
Why only this supersu version compatible?
And why can not I make any changes to build.pop?
Example:
Change DPI - ro.sf.lcd_density = 550
Adding virtual navigation buttons - qemu.hw.mainkeys = 0
rooting Motorola Marshmallow 6.0.1 firmware
Guth13 said:
Congratulations my friend!! You solved my root problem.
But why only this supersu version compatible?
Click to expand...
Click to collapse
Well, I solved it April 7, the very day you posted. It just took until April 12 for me to repeat it two more times for you to actually listen.
Using so-called stable or even newer SuperSu for initial root will cause bootloops for Motorola Marshmallow 6.0.1. Only that older beta SuperSu works on many Motorola Marshmallow firmware. I'm not going to say "all" Motorola Marshmallow firmware -- but many, many, many. AFTER you get initial root and confirm that status (after reboot), then you can update to newest SuperSu. It's only an problem on initial (first) root.
We discovered it in the Moto Quark (Moto Maxx/Moto Turbo/Droid Turbo) phones, as well as Moto Kinzie (Moto X Force), and here's even a thread for 2015 Moto G3 with the same issue:
How to get root 2015 Moto G3 With Stock Android Marshmallow 6.0 (XT1541)
https://forum.xda-developers.com/2015-moto-g/general/root-how-to-root-moto-g-2015-android-t3320113
I wrote the bootloader unlock and rooting guide for the 2014 Moto XT1225 and Moto XT1250 (Moto Turbo/Moto Maxx) and it's in there.
UPDATED GUIDE: How to unlock your MOTO MAXX/MOTO TURBO bootloader/install TWRP/root
https://forum.xda-developers.com/showthread.php?t=3455341
Months later when the sibling Quark Droid Turbo XT1254 was updated to Marshmallow, that beta SuperSu requirement still applied.
[GUIDE] How to unlock your Droid Turbo bootloader, install TWRP and gain root access
https://forum.xda-developers.com/showthread.php?t=3292684
Also applies for 2015 Kinzie, the Moto X Force (sibling to the Droid Turbo 2)...
[ROOT][INFO][MARSHMALLOW] How to Root Moto X Force 6.0 [TESTED]
https://forum.xda-developers.com/droid-turbo-2/general/root-how-to-root-moto-x-force-6-0-t3282151
and probably many other Motorola phones.
With the Quark phones, we first discovered it with Moto Maxx/Moto Turbo XT1225 in July 2016. I updated my bootloader unlock/TWRP/root GUIDE for the XT1225 to include that information specific to stock Motorola Marshmallow firmware. The XT1250 Moto Maxx has still not received official Marshmallow but it will apply to them also if/when it happens.
THEN, in December 2016 when the Droid Turbo XT1254 got Marshmallow they ran into the same problem -- but the XT1225 is identical Quark phone except for radio (and the Droid Turbo has a Verizon-mandated locked-down bootloader which has to be jimmied with Sunshine). We XT1225 owners already knew what to do and told them! So, @TheSt33v updated his Droid Turbo guide to convey the same information.
It was the first thing I told you if you look back up the this post thread. I asked if you were using the correct SuperSu for Motorola Marshmallow and that the procedure had changed, so my guide was updated in July 2016 to reflect that. That's why I even put "UPDATED" in my guide title. And I also said after you get initial root (and confirm), then you can update the SuperSu to newest if you wish.
_____________
Guth13 said:
And why can not I make any changes to build.pop?
Example:
Change DPI - ro.sf.lcd_density = 550
Adding virtual navigation buttons - qemu.hw.mainkeys = 0
Click to expand...
Click to collapse
What build prop editor are you using? I use this one:
BuildProp Editor
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en
You also have to give your build prop editor app root privileges in SuperSu. Go into the SuperSu settings and see all the apps which have root approval. In the SuperSu logs you can also see the apps which had been denied root privileges. In the SuperSu app settings, I always change the pop up root request to "30 seconds" so I am sure to see the root request.
Do NOT try to do both build prop changes at the same time. Let's keep it simple. Do the DPI change first, reboot, see if it took effect, then do the other. You can easily mess up your phone trying to do too many changes at the same time.
Make sure you have a TWRP backup before doing any build prop changes. It might be the ONLY way to recover from a disaster.
1) DPI
Be careful about messing up your display. For instance Motorola stock Quark DPI is 640, which I actually prefer. But @bhb27 and other ROM developers make the DPI smaller to a default 560 DPI. For instance, in Resurrection Remix in Settings/Display here's the choice to go larger and smaller, if you wish.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But 550 is NOT one of those choices. Maybe that's a strange DPI our 1440p AMOLED displays can't handle? Try 560 and see what happens. If it still doesn't change, we'll discuss further.
2) VIRTUAL KEYS
Guth13 said:
And why can not I make any changes to build.pop?
Adding virtual navigation buttons - qemu.hw.mainkeys = 0
Click to expand...
Click to collapse
You are SURE this is the correct command for our Quarks? There's TWO different commands for virtual button prop edits for Android phones all over the internet:
http://forums.androidcentral.com/showthread.php?t=390680&p=5262529&viewfull=1#post5262529
qemu.hw.mainkeys=0
if this doesn't work for you,
try this one :
same thing do this at the end of your build prop.
"ro.show.navigationbar=yes"
(without the quotes)
save changes, before you close.
Reboot.
to disable, just type "no" in stead of yes.
(without the quotes, again.)
Click to expand...
Click to collapse
Which one works with our Quarks? I don't know. Also mentioned in this article:
Disable or Enable The On-screen / Virtual Software keys In Android!
http://www.gizbeat.com/2021/disable-or-enable-the-on-screen-virtual-software-keys-in-android/
I haven't found either command in my build prop editor on Resurrection Remix -- a ROM which allows virtual buttons to be enabled. Maybe because I haven't actually enabled virtual buttons and the ROM would add those commands when I did so? Anyway try BOTH commands -- but not at the same time! Try one, reboot. If it doesn't work, try the other. You may have to add the lines manually in edit mode, but again make a TWRP backup first before making any changes.
If neither command works, then you'll have to ask one of the Quark ROM devs what command they use to permit virtual buttons to be enabled.
ChazzMatt said:
But 550 is NOT one of those choices. Maybe that's a strange DPI our 1440p AMOLED displays can't handle?
Click to expand...
Click to collapse
Android and our display will probably use anything (well, within reason, someone should try 100) we throw at it...a perk of having pixels for days.
Insistence on increments of 40 could be a scaling thing for touch detection. I was trying to use odd numbers between 480 and 520 in 7.1 to start with, and it badly screwed up DPI-specific apps (most notably Moto Camera's touch regions were off enough that the tutorials couldn't all be skipped). I finally stopped trying to be a rebel and settled on 480, and while the touch regions are still very slightly off, they're close enough to use without any difficulty.
THREAD UPDATED 4/22/19
So I started having pre-flash errors, boot looping, and bricked modem problems from just flashing the modems so I decided to upload the entire stock firmware for Nougat and Marshmallow. It's the same process but you have to flash the entire firmware then flash TWRP to use custom roms. Just click the FLASH-ALL.bat in the Nougat or Marshmallow folder and it will flash the firmware automatically and reboot. If you have any issues please report it here. I also included TWRP and the stock boot images all in one package just go into the folder and hit FLASH-ALL.bat. Everything is automated no more looking for firmware and flashing manually.
Link 1:
https://mega.nz/#!K1o0XIDS!taCkfjVbWunmkEOFVrqUaFeTLEQZ-JQACqO2EpebnAo
Queston - just got done replacing the LCD-Digitizer and battery (Moto X Pure XT1575) with the iFixit repair kit and got it up and running again (cracked the display in an auto accident and never had time to fix it until now)- while it was out of service I've been using a Moto G Play XT1607 as a backup for the last couple years... anyway now that it's working again I ran the factory reset and checked the Android version and it's at 6.0 (MarshMellow?) ... am a novice and wondering if it should upgrade at least to 7.0 (Nougat) eventually, in a day or so(?) when it synchronizes somehow - or if i should go ahead and do it manually myself ... and/or if manually updated go straight to whatever the current version is (Oreo 8 or Pie 9) ... If this is the right place, I may need some pointers getting started in the right direction ... In comparison the Moto G Play is at 7.1.1 ...any suggestions?
jabberjaw007 said:
Queston - just got done replacing the LCD-Digitizer and battery (Moto X Pure XT1575) with the iFixit repair kit and got it up and running again (cracked the display in an auto accident and never had time to fix it until now)- while it was out of service I've been using a Moto G Play XT1607 as a backup for the last couple years... anyway now that it's working again I ran the factory reset and checked the Android version and it's at 6.0 (MarshMellow?) ... am a novice and wondering if it should upgrade at least to 7.0 (Nougat) eventually, in a day or so(?) when it synchronizes somehow - or if i should go ahead and do it manually myself ... and/or if manually updated go straight to whatever the current version is (Oreo 8 or Pie 9) ... If this is the right place, I may need some pointers getting started in the right direction ... In comparison the Moto G Play is at 7.1.1 ...any suggestions?
Click to expand...
Click to collapse
If you want stock Nougat go ahead and update to it but I had battery drain issues on the Nougat modem from personal experience. If you decide to update you can use this thread and downgrade to stock 6.0.
Hi, I downloaded the Nougat and tried the command "Flash-all.bat" while in windows 10 ( I have the device booted up in bootloader mode. ) nothing happens. The screen flashes something too quick for me to see what it is. I must be doing something dumb. Do I need to go into command mode to do this "Flash-all.bat" or can I do it in the windows screen ?
AndroidMilos said:
Hi, I downloaded the Nougat and tried the command "Flash-all.bat" while in windows 10 ( I have the device booted up in bootloader mode. ) nothing happens. The screen flashes something too quick for me to see what it is. I must be doing something dumb. Do I need to go into command mode to do this "Flash-all.bat" or can I do it in the windows screen ?
Click to expand...
Click to collapse
Okay if the terminal window flashes really fast and you can't read it that usually means it can't write to the phone. Either your bootloader isn't unlocked or your usb cable doesn't support data transfer. If that isn't the issue make sure you install Motorola device manager and the adb fastboot sdk drivers which can be found on XDA. More than likely you're getting a remote failure error I have this problem myself a lot on Windows 10.
Thank you for your reply. I will follow through with the info you gave me.
I no longer own this device so I will no longer participate in any Moto X Pure threads. FYI if you flash the Nougat firmware in this thread you have to OTA to the final update for Nougat ROMs to work.