Database Develop

[Q] root problem

my moto g 2014 titan_retaildsds in not compatible with chainfire auto root zip titan_retaildsds and its not rooting please can anyone help me????:crying:

syash01 said:
my moto g 2014 titan_retaildsds in not compatible with chainfire auto root zip titan_retaildsds and its not rooting please can anyone help me????:crying:
Click to expand...
Click to collapse
1. Follow Motorola's instructions to
unlock the bootlader.
2. Flash TWRP 2.8.5 with fastboot.
3. Flash latest SuperSU with TWRP.
4. Enjoy

syash01 said:
my moto g 2014 titan_retaildsds in not compatible with chainfire auto root zip titan_retaildsds and its not rooting please can anyone help me????:crying:
Click to expand...
Click to collapse
Well, flashing with TWRP only worked for me on KitKat, it stopped working for 5.02, but what I did was used auto root for Lollipop, I was told this is the only supported method for this device on Lollipop, are you still on 4.4.4 or did you receive the OTA 5.02?
And as you are trying Auto Root, are you sure you are choosing the correct one for your device, it took me an hour or so to ensure that it was the correct one, I analysed all the tags and compared them with my version, there was a few for my device so I had to make sure everything matched.
This is the one I used, it works but best check if it fits your device: download(dot)chainfire(dot)eu/603/CF-Root/CF-Auto-Root/CF-Auto-Root-titanumtsds-titanretaildsds-xt1068.zip
You need to add the http protocol and replace (dot) with .
It won't let me post links.

TchTlk said:
Well, flashing with TWRP only worked for me on KitKat, it stopped working for 5.02
Click to expand...
Click to collapse
How so?

doppelhelix said:
How so?
Click to expand...
Click to collapse
After the flash was successful with TWRP, I launched the SU app and it said something along the lines of 'SuperUser is not installed correctly' I used the exact same method as I did on KitKat, I then learned that this is no longer the way of rooting the device on Lollipop, I installed TWRP for nothing.

After rooting via TWRP 2.8.5.0 try to change the mode with SELinux Mode Changer: https://play.google.com/store/apps/details?id=com.mrbimc.selinux&hl=de

TchTlk said:
I then learned that this is no longer the way of rooting the device on Lollipop, I installed TWRP for nothing.
Click to expand...
Click to collapse
?
There was and is only one correct way to install SuperSU regardless of lollipop or kitkat
· Flash TWRP 2.8.5 with fastboot.
· Flash latest SuperSU with TWRP.
Wolfcity said:
change the mode with SELinux Mode Changer:
Click to expand...
Click to collapse
Chainfire himself is strictly against changing SELinux. That's why he had to invest so much time and even bought a Moto G (2014) so he can fix any error resulting of enforced SELinux. SuperSU 2.45 was the result of his investigation into the XT106x.

doppelhelix said:
?
There was and is only one correct way to install SuperSU regardless of lollipop or kitkat
CR Auto Root is the only method that worked for me since the lollipop update, I tried the SU zip with TWRP, i t was successful, however the SU app just displayed an error message saying that if wasn't installed correctly.
I did exactly the same thing as before, the only thing that changed was the new update.
Click to expand...
Click to collapse

TchTlk said:
.
I did exactly the same thing as before, the only thing that changed was the new update.
Click to expand...
Click to collapse
Maybe your twrp version was outdated?

doppelhelix said:
?
There was and is only one correct way to install SuperSU regardless of lollipop or kitkat
· Flash TWRP 2.8.5 with fastboot.
· Flash latest SuperSU with TWRP.
Chainfire himself is strictly against changing SELinux. That's why he had to invest so much time and even bought a Moto G (2014) so he can fix any error resulting of enforced SELinux. SuperSU 2.45 was the result of his investigation into the XT106x.
Click to expand...
Click to collapse
Thx for that info. Didn´t heard that and if Chainfire said so it´s better to follow that.
And btt,flashing TWRP 2.8.4.0 or 2.8.5.0 with latest superSU (2.46 at the moment) should work with 5.0.2 without any other variations.

[Q] Which auto root software

Hi
Is there a suitable auto root file that I can use for my Motorola G (2014) 2nd generation XT-1068 with Android 5.0.2?
I've found Chainfire's Moto G 2014 XT1068 (titan_retaildsds) and Moto G 2014 XT1068 (titan_retde), but neither of these seem to me to be an obvious match for my phone's system version 22.41.16.titan_retailgb.retgball.en.GB retgb.
Thanks

Can u send me a screenshot of ur about phone settings
Sent from my XT1068

Vedant Mistry said:
Can u send me a screenshot of ur about phone settings
Sent from my XT1068
Click to expand...
Click to collapse
Hi Vedant Mistry
Thanks for your prompt response – screenshot attached of the lower half of the About phone screen.
Does this affect your previous reply about flashing TWRP 2.8.6.0 recovery and then installing supersuv2.46.zip?

I know this is not what you're asking for, but honestly, I think it's easier to simply flash SuperSU using TWRP recovery.
Use TWRP 2.8.6.0 and SuperSU 2.4.6, both should be easy to find and install.

mpeL said:
I know this is not what you're asking for, but honestly, I think it's easier to simply flash SuperSU using TWRP recovery.
Use TWRP 2.8.6.0 and SuperSU 2.4.6, both should be easy to find and install.
Click to expand...
Click to collapse
Hi mpeL
Thanks for taking the time to reply. I think that's the route I'll now follow – I've already downloaded these files and will be good to go with the rooting in the morning – too late to start with a clear head now! :fingers-crossed:

Thalarctos said:
Hi mpeL
Thanks for taking the time to reply. I think that's the route I'll now follow – I've already downloaded these files and will be good to go with the rooting in the morning – too late to start with a clear head now! :fingers-crossed:
Click to expand...
Click to collapse
Good luck bud! Make sure you have the fastboot drivers installed in order to install the custom recovery.

[SuperSU][System-Mode][2.82 SR5]

This is SuperSU that installs always in System-Mode.
Instructions
1 - Download zip
2 - Go in recovery & make a backup (optional, but recommended)
3 - Flash zip
Changelogs here & here
Special thanks to @aufarxda (the original creator of this thread) @Chainfire @CCMT

binaries failed to update
Just installed the lastest security update (6.01) from google on my nexus 6. Flashed v2.66 and binaries will not update. Any suggestions?

Thanks My Brother ?

Reflash the kernel.
Unroot.
Reroot.
Should work.
Hope that helps.

aufarxda said:
Reflash the kernel.
Unroot.
Reroot.
Should work.
Hope that helps.
Click to expand...
Click to collapse
I am on CM13 1/6/2016 nightly on angler, and this is causing a bootloop now. Before this newest nightly, I was able to install with no problem. Systemless also still works.

fpqc said:
I am on CM13 1/6/2016 nightly on angler, and this is causing a bootloop now. Before this newest nightly, I was able to install with no problem. Systemless also still works.
Click to expand...
Click to collapse
Nightly comes with problems.Look Angler's XDA thread and ask others which nightly is the most stable build.
Hope that helps.

aufarxda said:
Nightly comes with problems.Look Angler's XDA thread and ask others which nightly is the most stable build.
Hope that helps.
Click to expand...
Click to collapse
The reason I think is that this is the first update with the newest vendor.img. That's the only thing that seems out of the ordinary.

fpqc said:
The reason I think is that this is the first update with the newest vendor.img. That's the only thing that seems out of the ordinary.
Click to expand...
Click to collapse
Well, just reflash last update before this one.
Or, just wait another update with the fix.

I have the Verizon SCH-I545, MDK bootloader, and am running JDC Team's AOSP 6.0.
I am unable to install any version of SU above 2.52. TWRP 2.8.7.0 and 2.8.7.2 by Antaresone and the official 2.8.7.0 all fail with the same message.
Recovery.log
https://www.dropbox.com/s/kmc3bafuvlfq20v/recovery.log?dl=0

FernBch said:
I have the Verizon SCH-I545, MDK bootloader, and am running JDC Team's AOSP 6.0.
I am unable to install any version of SU above 2.52. TWRP 2.8.7.0 and 2.8.7.2 by Antaresone and the official 2.8.7.0 all fail with the same message.
Recovery.log
https://www.dropbox.com/s/kmc3bafuvlfq20v/recovery.log?dl=0
Click to expand...
Click to collapse
Solution 1(Tricky, and may not work) :
Try to mount data and system using mount option and remove mounting script on the updater-binary.
Then, use TWRP file manager to remove /supersu manually.
At last, install the zip again.
Solution 2 (not really a solution) :
If you really cant mount data or system, ask the rom dev or someone on your phone's forum for solution.
Solution 3 (1% chance of working) :
Dont bother about the bootloader.
Check your boot image instead.
Solution 4 :
Check if you have chcon on system/bin.
If not download this file and move it into system/bin.
Link :Drive

Hi,
Thanks! This version finally works for secondary roms in Multrirom!!!

Droidphilev said:
Hi,
Thanks! This version finally works for secondary roms in Multrirom!!!
Click to expand...
Click to collapse
Nice to know.

Can this be flashed over systemless root to convert to system root or will I have to flash my system.img backup then this. I'm running systemless root on Htc M9 Marshmallow dev edition
Sent from my HTC One M9 using Tapatalk

I installed 2.64 beta via TWRP. It installed successfully however upon reboot it shows i still have 2.52. Is that normal?

slick97477 said:
I installed 2.64 beta via TWRP. It installed successfully however upon reboot it shows i still have 2.52. Is that normal?
Click to expand...
Click to collapse
Don't know. Maybe install the app on the zip manually. Update the binary and if updating fails, full unroot and re-root with the new zip.

krazyace35 said:
Can this be flashed over systemless root to convert to system root or will I have to flash my system.img backup then this. I'm running systemless root on Htc M9 Marshmallow dev edition
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
No, full unroot first.
Then, remove /su
Replace the kernel with new custom one.
And then, flash the system mode zip.

aufarxda said:
No, full unroot first.
Then, remove /su
Replace the kernel with new custom one.
And then, flash the system mode zip.
Click to expand...
Click to collapse
Cool thanks for the info
Sent from my HTC One M9 using Tapatalk
---------- Post added at 06:00 PM ---------- Previous post was at 05:30 PM ----------
@aufarxda I'm guessing there are no custom kernels yet for Marshmallow? I can't find one I also noticed flar2 said the kernel source hasn't been released yet
Sent from my HTC One M9 using Tapatalk

krazyace35 said:
@aufarxda I'm guessing there are no custom kernels yet for Marshmallow? I can't find one I also noticed flar2 said the kernel source hasn't been released yet
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Maybe not avaiable for your phone.
But most Marshmallow phone devs already made custom kernels for their phones.

Thanks for this, @aufarxda. Can you tell us what you did and made it always install in System mode?

KreAch3R said:
Thanks for this, @aufarxda. Can you tell us what you did and made it always install in System mode?
Click to expand...
Click to collapse
I moved v2.52 script with little modifications (aside from the ui_print).

Progress towards Root/Twrp/Roms

This thread is strictly for info regarding Root/Twrp/Roms
If you have any ideas or have tried anything please post here
I AM IN NO WAY A DEV ,i am using google and common sense
Here is the link to the sprint boot.img (https://drive.google.com/file/d/0B9Vkl8ldvnNdOGlyLW4wOXNDRUk/view?usp=drivesd)-Thanks to @XirXes
Heres what i have tried
-So far i have tried signing the sprint boot.img to magisk with no luck,it gives me files are read only errors.I was able to get past the the first two steps of this post for systemless root via adb (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
-Flashing the stock sprint boot.img to confirm compatibility hint hint its compatible
ROOT HAS BEEN ACHEIVED!!
UPDATE- As of 9/13/17 we now have root in the form of a patched boot.img thanks to @themustached for patching the boot.img so gracefully for us
To install the boot img you need to reboot to fastboot and run the command "fastboot flash boot (name of boot.img).img
https://drive.google.com/file/d/0B8kodjBRTHoZR2Zob1VLX0xOVkU/view?usp=sharing
Just a update as I have been away from this phone for a bit
We have kernel source now (like 2 months ago) and there are 3 AOSP ROMs that I know about being worked on so far I don't know any details or anything but what I do know is that they completed the build process they are working on getting it running on our phone
joemossjr made the the ncp Rom and got TWRP for us so big thanks to him!
Substratum works on legacy with root and newest version of TWRP just in case anyone was wondering.

https://pastebin.com/uk8uCTX2 created one!
---------- Post added at 12:36 AM ---------- Previous post was at 12:31 AM ----------
https://drive.google.com/file/d/0B1tqDJm_qQf4Y2VibG5fZ3NzZmc/view?usp=sharing

joemossjr said:
https://pastebin.com/uk8uCTX2 created one!
---------- Post added at 12:36 AM ---------- Previous post was at 12:31 AM ----------
https://drive.google.com/file/d/0B1tqDJm_qQf4Y2VibG5fZ3NzZmc/view?usp=sharing
Click to expand...
Click to collapse
Booted but no root
Also when toying around do not do Fastboot flash, do fastboot boot. We dont have a clean T Mobile kernel and could really wind up in a bad place due to a bad flash.

altimax98 said:
Booted but no root
Also when toying around do not do Fastboot flash, do fastboot boot. We dont have a clean T Mobile kernel and could really wind up in a bad place due to a bad flash.
Click to expand...
Click to collapse
i tried flashing to the a and b partition no luck used the magisk 13.6 thinking we need to get hold of the pixel magisk

I have insurance and I'm willing to risk my device worst case,it's not a problem,I've noticed if you boot it,it doesn't like to set correctly

joemossjr said:
i tried flashing to the a and b partition no luck used the magisk 13.6 thinking we need to get hold of the pixel magisk
Click to expand...
Click to collapse
I totally forgot about the dual partitions with this.
We really need the stock recovery to get TWRP built. Even the Sprint/AT&T versions should be fine
Sent from my Moto Z (2) using Tapatalk

Downloaded them all found no recovery

Verified ATT & Sprint boot.img works om Tmobile
Ok I have verified these 2 posted images boot ok on the TMobile Z2 Force. What do I need to do to use fastboot to extract system images? I cant use adb to get any system partition yet. I dont have the info, I tried to use adb and it would not let me read /dev/ permission denied. If you tell me what to do from fastboot or adb I can dump it, bootloader is already unlocked. Thanks!

bart bart said:
Ok I have verified these 2 posted images boot ok on the TMobile Z2 Force. What do I need to do to use fastboot to extract system images? I cant use adb to get any system partition yet. I dont have the info, I tried to use adb and it would not let me read /dev/ permission denied. If you tell me what to do from fastboot or adb I can dump it, bootloader is already unlocked. Thanks!
Click to expand...
Click to collapse
We are all in this situation. It is likely going to be quite some time before we get root due to the dual partition system.
Based on the Pixel info, we need TWRP first
Sent from my Moto Z (2) using Tapatalk

The recovery is in the boot.img of 7.1 and up devices

Dumper US Cellular Boot.img
altimax98 said:
I totally forgot about the dual partitions with this.
We really need the stock recovery to get TWRP built. Even the Sprint/AT&T versions should be fine
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
Here is dumped boot.img of US Cellular Boot.img. There is a recovery under sbin folder. Hopefully you can make a bootable TWRP from it?
https://www.dropbox.com/s/hjfr8wj2da...ootus.zip?dl=0

If anyone wants to join our efforts the let us know and we can add you in

I want to join your efforts.

Figured I'd give a status update on people looking for root. So as it looks roots gonna have to be put on the back end for right now as magisk isn't updated to 13.6 for the Google pixel it's on 13.4 which means we can't use the 13.6 manual boot image patching funtionallity. The reason we are using the pixel is because as of right now it's the only other device to use the a and b partitioning that has magisk. So what this all means is we need to try to get twrp going so we can at least get backups going and pre rooted roms. I personally have pmed everyone I could with little to no response. I'll update when I get any responses.

joemossjr said:
Figured I'd give a status update on people looking for root. So as it looks roots gonna have to be put on the back end for right now as magisk isn't updated to 13.6 for the Google pixel it's on 13.4 which means we can't use the 13.6 manual boot image patching funtionallity. The reason we are using the pixel is because as of right now it's the only other device to use the a and b partitioning that has magisk. So what this all means is we need to try to get twrp going so we can at least get backups going and pre rooted roms. I personally have pmed everyone I could with little to no response. I'll update when I get any responses.
Click to expand...
Click to collapse
Thank you
Sent from my SM-N930F using XDA-Developers Legacy app

Deleted

Any progress? Anything I can do to help? I have T Mobile variant with unlocked bootloader.

We brought in another guy from the pixel forum who made their twrp recovery he's going to take a look and see what can be done

Question before I delve further.
fastboot -i 0x2b4c flash:raw boot <kernel> [ <ramdisk> ] rather than just flash <partition> [ <filename> ] perhaps for the twrp? Just a spit ball idea as I wrap my head around. Been a few years since I bothered with phones rather than.. other systems. I'm sure this round probably already been tried but curious of the turn before I fry the new toy xD.

joemossjr said:
If anyone wants to join our efforts the let us know and we can add you in
Click to expand...
Click to collapse
I can test stuff when the time comes.

[help] XT1921-1 root

Hello all,
I was wondering if there has been any development / root process for the E5 Play XT1921-1?
Thanks

smeogle said:
Hello all,
I was wondering if there has been any development / root process for the E5 Play XT1921-1?
Thanks
Click to expand...
Click to collapse
If you have unlocked your bootloader, you should be able to use @CodyF86's TWRP and root method from this thread. https://forum.xda-developers.com/mo...very-twrp-moto-e-5-play-james-t3796323/page23
The xt1921-1 appears to be the unbranded variant of xt1921-5.

MotoJunkie01 said:
If you have unlocked your bootloader, you should be able to use @CodyF86's TWRP and root method from this thread. https://forum.xda-developers.com/mo...very-twrp-moto-e-5-play-james-t3796323/page23
The xt1921-1 appears to be the unbranded variant of xt1921-5.
Click to expand...
Click to collapse
I will give it a go, thank you for your info!

smeogle said:
I will give it a go, thank you for your info!
Click to expand...
Click to collapse
To play it completely safe, instead of actually flashing TWRP as an initial step, use the boot-only method:
fastboot boot twrp.img
This way, you can ascertain whether the TWRP build functions on your device normally before flashing the /recovery partition.

MotoJunkie01 said:
To play it completely safe, instead of actually flashing TWRP as an initial step, use the boot-only method:
fastboot boot twrp.img
This way, you can ascertain whether the TWRP build functions on your device normally before flashing the /recovery partition.
Click to expand...
Click to collapse
Well, it worked!. I had to flash your stock ROM in TWRP due to it being stuck in a bootloop, but overall, it runs well! I guess the steps outlined for 1921-5 are confirmed to work for XT1921-1. Thank you again for your help!

smeogle said:
Well, it worked!. I had to flash your stock ROM in TWRP due to it being stuck in a bootloop, but overall, it runs well! I guess the steps outlined for 1921-5 are confirmed to work for XT1921-1. Thank you again for your help!
Click to expand...
Click to collapse
Very glad you tried and confirmed this. I'll add the info to my stock ROM thread regarding the intercompatability between these two devices.

MotoJunkie01 said:
Very glad you tried and confirmed this. I'll add the info to my stock ROM thread regarding the intercompatability between these two devices.
Click to expand...
Click to collapse
Upon further use, there is some stability issues. When I navigate to Settings -> System -> About Phone -> Hardware Information, the popup 'Motorola Settings has stopped' appears. Additionally, camera doesn't launch.

smeogle said:
Upon further use, there is some stability issues. When I navigate to Settings -> System -> About Phone -> Hardware Information, the popup 'Motorola Settings has stopped' appears. Additionally, camera doesn't launch.
Click to expand...
Click to collapse
Interesting. That would appear to indicate some minor differences between the two devices in terms of firmware configurations. Try this, using the factory firmware package for your device, flash the /boot and /oem partitions only (since the camera drivers are located in /boot). Then boot into TWRP recovery and flash Magisk (or a no-verity script) in order to disable dm-verity and for root patching. Wipe the cache and Dalvik and reboot system.
If that doesn't do the trick, do a clean firmware install and do a TWRP dump of your system image and /boot partition. Upload them to a host like Google Drive, send me a link, and I'll build you a TWRP flashable stock ROM specifically for xt1921-1.

MotoJunkie01 said:
Interesting. That would appear to indicate some minor differences between the two devices in terms of firmware configurations. Try this, using the factory firmware package for your device, flash the /boot and /oem partitions only (since the camera drivers are located in /boot). Then boot into TWRP recovery and flash Magisk (or a no-verity script) in order to disable dm-verity and for root patching. Wipe the cache and Dalvik and reboot system.
If that doesn't do the trick, do a clean firmware install and do a TWRP dump of your system image and /boot partition. Upload them to a host like Google Drive, send me a link, and I'll build you a TWRP flashable stock ROM specifically for xt1921-1.
Click to expand...
Click to collapse
After following the flash boot and oem steps, it got caught in a bootloop. Once that occurred, I wiped and reflashed your stock rom (followed by Magisk). Once it booted again, the previously mentioned instability (camera and hardware settings) have disappeared. Good job!

smeogle said:
After following the flash boot and oem steps, it got caught in a bootloop. Once that occurred, I wiped and reflashed your stock rom (followed by Magisk). Once it booted again, the previously mentioned instability (camera and hardware settings) have disappeared. Good job!
Click to expand...
Click to collapse
Give me a TWRP backup of your system image and boot partition and I'll make a TWRP flashable stock ROM for the XT1921-1.
Thanks for testing. I'll add the intercompatability info to my stock ROM and firmware threads.

Unlocking Bootloader on XT1921-1
Just wondering how you unlocked your Bootloader??? Motorola site states it is unlockable?
---------- Post added at 09:57 PM ---------- Previous post was at 09:46 PM ----------
smeogle said:
Well, it worked!. I had to flash your stock ROM in TWRP due to it being stuck in a bootloop, but overall, it runs well! I guess the steps outlined for 1921-5 are confirmed to work for XT1921-1. Thank you again for your help!
Click to expand...
Click to collapse
Just wondering how you unlocked your Bootloader??? Motorola site states it is unlockable?

dcluvsme said:
Just wondering how you unlocked your Bootloader??? Motorola site states it is unlockable?
---------- Post added at 09:57 PM ---------- Previous post was at 09:46 PM ----------
Just wondering how you unlocked your Bootloader??? Motorola site states it is unlockable?
Click to expand...
Click to collapse
I followed the guide the on the following Motorola website:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a

Thanks
smeogle said:
I followed the guide the on the following Motorola website:
Click to expand...
Click to collapse
Using Linux, I was refused, did the exact same thing in Windows,and it worked.
Who knows.
Thanks for the tip.

dcluvsme said:
Using Linux, I was refused, did the exact same thing in Windows,and it worked.
Who knows.
Thanks for the tip.
Click to expand...
Click to collapse
When you tried in Linux, what do you mean it did not work? I performed mine with Linux Mint. Did you get any specific error? How did you install adb and fastboot?

smeogle said:
When you tried in Linux, what do you mean it did not work? I performed mine with Linux Mint. Did you get any specific error? How did you install adb and fastboot?
Click to expand...
Click to collapse
I used Puppy Xenial,but I also have Linux Mint. I am sure it was an error on my part. No worries.

smeogle said:
Well, it worked!. I had to flash your stock ROM in TWRP due to it being stuck in a bootloop, but overall, it runs well! I guess the steps outlined for 1921-5 are confirmed to work for XT1921-1. Thank you again for your help!
Click to expand...
Click to collapse
can u please help me i think im stuck in the same boat you were in

MotoJunkie01 said:
If you have unlocked your bootloader, you should be able to use @CodyF86's TWRP and root method from this thread. https://forum.xda-developers.com/mo...very-twrp-moto-e-5-play-james-t3796323/page23
The xt1921-1 appears to be the unbranded variant of xt1921-5.
Click to expand...
Click to collapse
is there a way to do it without twerp? my phone is in a boot loop i installed the wrong rom i think i cant find the correct one for this phone.