Droid Turbo (XT1254) autoiniroot problem - Verizon Motorola Droid Turbo Q&A, Help & Troublesh

Droid Turbo (XT1254) autoiniroot problem - Verizon Motorola Droid Turbo Q&A, Help & Troublesh

Hey.
I have a Droid Turbo XT1254 with bootloader locked (I am planning to unlock soon).
Recently, I stumbled across the thread and saw that someone had made rooting MCG25.251-5-5 possible and it made me want to try it out.
Anyways, I downloaded all the files (magisk and autoinitroot) and was able to root my phone just fine.
I tried giving Super user permission to some apps, and it worked flawlessly. I then tried to install Magisk module but oddly enough it failed.
It gave me an error that magisk was not properly installed. Also the SafetyNet check failed.
I decided to uninstall root, factory reset my device and root the device again.
Now the thing is that when I booted back into fastboot and ran the command that was meant to uninstall the root, it failed.
Obviously, I made sure that I was typing the correct command, I didn't even miss the "" marks. But it still didn't work.
It only gave me an error that the command 'confirm' doesn't exist.
I tried running the autoinit script and I booted just fine.
But the problem is that magisk isn't working properly and I'm unable to uninstall the autoinit root.
Any help will be greatly appreciated.
Also, Im using minimal adb and fast boot setup. Not sure if that's what causing the uninstall to fail or not.
TL; DR: Magisk doesn't work properly after doing the autoinitroot and I'm unable to uninstall the root by using the command that was mentioned in the original post.
Thanks for taking the time to read it

DuringSummer said:
Hey.
I have a Droid Turbo XT1254 with bootloader locked (I am planning to unlock soon).
Recently, I stumbled across the thread and saw that someone had made rooting MCG25.251-5-5 possible and it made me want to try it out.
Anyways, I downloaded all the files (magisk and autoinitroot) and was able to root my phone just fine.
I tried giving Super user permission to some apps, and it worked flawlessly. I then tried to install Magisk module but oddly enough it failed.
It gave me an error that magisk was not properly installed. Also the SafetyNet check failed.
I decided to uninstall root, factory reset my device and root the device again.
Now the thing is that when I booted back into fastboot and ran the command that was meant to uninstall the root, it failed.
Obviously, I made sure that I was typing the correct command, I didn't even miss the "" marks. But it still didn't work.
It only gave me an error that the command 'confirm' doesn't exist.
I tried running the autoinit script and I booted just fine.
But the problem is that magisk isn't working properly and I'm unable to uninstall the autoinit root.
Any help will be greatly appreciated.
Also, Im using minimal adb and fast boot setup. Not sure if that's what causing the uninstall to fail or not.
TL; DR: Magisk doesn't work properly after doing the autoinitroot and I'm unable to uninstall the root by using the command that was mentioned in the original post.
Thanks for taking the time to read it
Click to expand...
Click to collapse
1) why are you waiting to unlock your bootloader? Temp root is unstable and won't give you what you want.
2) of course Magisk won't work until you unlock your bootloader. Why would you think otherwise? On Motorola phones you have to unlock the bootloader to make changes like permanent root, install custom recovery, etc. Magisk just hides that.
3) you SAY you typed the correct command but after having a back-and-forth for two days over three pages with someone else who claimed the same thing and was WRONG, I'm skeptical.
Type exactly what you think is the correct command. Don't copy and paste anything. Actually type it out.
Better yet, post screenshot. That's how we proved to the other guy he was not reading what we had written.
"Oh, I didn't know."
Yes he did. It was in post #2, the very FIRST reply in the thread, which I wrote. And I told him over and over to go re-read that post!

Thanks for replying.
The answer to the first question is that I don't have $$$ right now. Will do it next month or so.
#2: Hahah. I did read that thread, and I'm pretty sure I'm not making that mistake, In any case I'll attach screenshots.

This is the screenshot. This time I tried specifying the directory to the fastboot.exe that came with autoinitroot, still no luck. Same error comes up regardless of whether I specify the directory or just use normal fastboot the came with minimal ADB.
And yes. I did it while I was in fastboot mode.
For some reason the app won't let me upload screenshot. Here is the link instead
http://i.imgur.com/Y5L5kvw.png

ChazzMatt said:
1) why are you waiting to unlock your bootloader? Temp root is unstable and won't give you what you want.
2) of course Magisk won't work until you unlock your bootloader. Why would you think otherwise? On Motorola phones you have to unlock the bootloader to make changes like permanent root, install custom recovery, etc. Magisk just hides that.
3) you SAY you typed the correct command but after having a back-and-forth for two days over three pages with someone else who claimed the same thing and was WRONG, I'm skeptical.
Type exactly what you think is the correct command. Don't copy and paste anything. Actually type it out.
Better yet, post screenshot. That's how we proved to the other guy he was not reading what we had written.
"Oh, I didn't know."
Yes he did. It was in post #2, the very FIRST reply in the thread, which I wrote. And I told him over and over to go re-read that post!
Click to expand...
Click to collapse
Yeah but in the original thread by autoprime, users have posted that they managed to install modules like "xposed systemless" etc. No reason it shouldn't work on mine.
Edit: Furthermore, autoptime himself mentioned that we can use custom magisk script to avoid boot loop, as far as I understand that's only possible when magisk recognizes modules.
Thing is that I have root, I can even use apps like titanium backup and whatnot. I can't use the script he mentioned unless magisk allows me to install something.

DuringSummer said:
This is the screenshot. This time I tried specifying the directory to the fastboot.exe that came with autoinitroot, still no luck. Same error comes up regardless of whether I specify the directory or just use normal fastboot the came with minimal ADB.
And yes. I did it while I was in fastboot mode.
For some reason the app won't let me upload screenshot. Here is the link instead
http://i.imgur.com/Y5L5kvw.png
Click to expand...
Click to collapse
{
"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"
}
Your screenshot shows you typed "confirm". That's not the right command. It's "config".
fastboot oem config fsg-id ""

ChazzMatt said:
Your screenshot shows you typed "confirm". That's not the right command. It's "config".
fastboot oem config fsg-id ""
Click to expand...
Click to collapse
Oh. Hell. I feel stupid. I kinda copied from one the comments in OP. Will update brb.

Still doesn't work. This time it gave me error (bootloader) something-suffixes: false.
Etc etc. Will post screenshot.
EDIT: It WORKED. I placed the autoinitroot to desktop and changed the directory along with folder names. Ran the command, seems to have worked. Thanks anyways.
Probably had something to do with really long directory name. Idk.

DuringSummer said:
Yeah but in the original thread by autoprime, users have posted that they managed to install modules like "xposed systemless" etc. No reason it shouldn't work on mine.
Click to expand...
Click to collapse
Show me examples of that with Motorola phones.
I also have extensive experience with LG phones, and many of those (like LG G2 and LG G3) do not need bootloader unlock to root and install custom recovery. Whereas, Motorola phones require unlocked bootloader.
---------- Post added at 03:27 PM ---------- Previous post was at 03:21 PM ----------
DuringSummer said:
Still doesn't work. This time it gave me error (bootloader) something-suffixes: false.
Etc etc. Will post screenshot.
EDIT: It WORKED. I placed the autoinitroot to desktop and changed the directory along with folder names. Ran the command, seems to have worked. Thanks anyways.
Probably had something to do with really long directory name. Idk.
Click to expand...
Click to collapse
Yes, the suffixes errors are normal. Only by rebooting do you see if it worked.

ChazzMatt said:
Show me examples of that with Motorola phones.
I also have extensive experience with LG phones, and many of those (like LG G2 and LG G3) do not need bootloader unlock to root and install custom recovery. Whereas, Motorola phones require unlocked bootloader.
Click to expand...
Click to collapse
http://i.imgur.com/u06AaAV.png
http://i.imgur.com/7AHc5Bk.png
He explicitly mentioned that about bootloader locked Moto. Also the tool only works on Moto so.

DuringSummer said:
http://i.imgur.com/u06AaAV.png
http://i.imgur.com/7AHc5Bk.png
He explicitly mentioned that about bootloader locked Moto. Also the tool only works on Moto so.
Click to expand...
Click to collapse
Well, I know he was wrong about one thing. When the phone reboots it doesn't just boot into a stock system. Instead it bootloops and gets hung on the Moto logo. It never finishes booting until you run that end temp root command in fastboot.
Go to the thread and ask him how to do what he describes.... He is an expert and knows a lot more than me.
But also remember if your phone reboots in any way while you are away from your computer with fastboot installation, your phone will be totally useless until you get back to your computer and temp re-root or run that end temp root command.

ChazzMatt said:
Well, I know he was wrong about one thing. When the phone reboots it doesn't just boot into a stock system. Instead it bootloops and gets hung on the Moto logo. It never finishes booting until you run that end temp root command.
Click to expand...
Click to collapse
Oh that. What he meant was that if you place the custom magisk script in the right folder it will avoid boot loop and will boot into stock system, from there you'll have to use autoinitroot tool from pc again to re-root it, the script is handy if you're going somewhere and won't have access to pc. In which case, even if your phone gets turned off or reboots, it won't bootloop like crazy and you get access to stock system. Though you won't have root until you run autoroot script again from PC.
Also, it does provides full root. The only downside is that it isn't permanent. So as long as you're careful and don't mess with system and only use systemless modifications using magisk, you're safe. In worst case scenarios you'll only have to run the unroot command and factory reset to go back to 100% stock.
It's useful for those who can't get their bootloader unlocked.
Sadly, In my case magisk isn't working properly. That's why I'll factory reset and try again. Hopefully it'll work then.
Also do you by any chance know how and where to place custom scripts of magisk? Will be doing that after factory reset.
Also you helped a lot. Thanks, mate

DuringSummer said:
Oh that. What he meant was that if you place the custom magisk script in the right folder it will avoid boot loop and will boot into stock system, from there you'll have to use autoinitroot tool from pc again to re-root it, the script is handy if you're going somewhere and won't have access to pc. In which case, even if your phone gets turned off or reboots, it won't bootloop like crazy and you get access to stock system. Though you won't have root until you run autoroot script again from PC.
Also, it does provides full root. The only downside is that it isn't permanent. So as long as you're careful and don't mess with system and only use systemless modifications using magisk, you're safe. In worst case scenarios you'll only have to run the unroot command and factory reset to go back to 100% stock.
It's useful for those who can't get their bootloader unlocked.
Sadly, In my case magisk isn't working properly. That's why I'll factory reset and try again. Hopefully it'll work then.
Also do you by any chance know how and where to place custom scripts of magisk? Will be doing that after factory reset.
Also you helped a lot. Thanks, mate
Click to expand...
Click to collapse
His post #2 seems to talk about folders.

ChazzMatt said:
His post #2 seems to talk about folders.
Click to expand...
Click to collapse
Yeah. Saw that. Couldn't find those folders. Checked both root and normal storage.
Thanks anyway.

The whole temp root thing is really just a way to proceed with the bootloader unlock. to use temp root on any daily driver just seems like more trouble than its worth. Hurry up and find 25 bucks!!!
My opinion is that for the work that these guys do its a small price to pay and was money well spent

bigmatt503 said:
The whole temp root thing is really just a way to proceed with the bootloader unlock. to use temp root on any daily driver just seems like more trouble than its worth. Hurry up and find 25 bucks!!!
My opinion is that for the work that these guys do its a small price to pay and was money well spent
Click to expand...
Click to collapse
Actually, I don't have any problem paying 25 bucks. The thing is that I'm planning to buy a new phone. Seems really pointless spending 25$ on something that I'll replace in a few months. At first I thought that I should get it unlocked, however, this phone is 3 years old. I decided that I should upgrade to current technology.

ChazzMatt said:
Show me examples of that with Motorola phones.
I also have extensive experience with LG phones, and many of those (like LG G2 and LG G3) do not need bootloader unlock to root and install custom recovery. Whereas, Motorola phones require unlocked bootloader.
---------- Post added at 03:27 PM ---------- Previous post was at 03:21 PM ----------
Yes, the suffixes errors are normal. Only by rebooting do you see if it worked.
Click to expand...
Click to collapse
Caution thread jacking...... since you are very familiar with LG phones. What are the chances of the verizon g6 ever getting root?
Sent from my VS988 using XDA-Developers Legacy app

Related

[TOOLKIT] Shield Root and More! [Shield RAM V1.1]

Shield RAM V1.1
<<< Shield Root and More >>>
I'm happy to present my first release.
{
"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"
}
FEATURES:
◄Unlock Bootloader►
◄Flash ClockWorkMod Recovery/Stock Recovery►
◄Root►
◄Debloat System►
◄After all it's a gaming console, who needs calendar's and books and crap ►
◄Restore to Factory Stock (erases all user data in the process)►
◄More to Come!!!►
NEWB INSTRUCTIONS:Make sure you have the naked driver installed from this THREAD first. There is an install guide in the thread describing how to get the driver's configured properly. However I'll try to sum it up. Once you have USB Debugging enabled windows will try finding the driver's but won't be able to, go into device manager and right click the device you need to install the driver for. For the ADB driver right click it and go to Update Driver Software >>> Browse my computer for driver software >>> Click the browse button and find the folder where you have extracted the naked drivers. Hit next, it should scan the folder, find the driver and then install it. For the fastboot driver you need to power your shield off, boot into the bootloader, and then plug your USB Cable in. Windows should look for the driver software and once again, it won't be able to find it. Do the same thing, go to device manager and right click Fastboot and select Update Driver Software. Select Browse my computer for driver software again but this time select Let me pick from a list of device drivers on my computer. Highlight Show All Devices and select Next. Select Have Disk at the bottom, and then Browse. Find the Naked Driver folder once again and then select android_winusb.inf and hit Open. Select ok, scroll to the bottom, highlight Nvidia Shield Fastboot, hit Next and accept the warning dialog. The Fastboot driver should now be installed. Extract Shield RAM.zip, open the folder, and all you have to do at this point is double click Shield RAM.exe to start the process. I made this about as simple as it get so someone with no rooting experience should have no problem. Happy Modding!!!
ADVANCED INSTRUCTIONS:
Make sure to have your adb and fastboot driver's installed, start Shield RAM
DISCLAIMER:If you do not know what root is, or have no need to use root, then you probably shouldn't be rooting your shield. I have tested this multiple times, and on multiple different shield units. This tool should be 100% safe however when it comes to flashing/rooting, modifying android device's in general there are certain inherent risks involved. I take no liability towards your device and the harm you could potentially cause to it. By now we should all know the risk involved with rooting, flashing, etc.
▲▲▲!!!AVAST AND POSSIBLY OTHER ANTIVIRUS PROGRAMS WARNING!!!▲▲▲
Avast wanted to run this in sandbox mode, if yours does the same let it sit for about 20 seconds and then hit continue execution.
Not really sure why it's doing it, I dont think Kwongger's tool tripped my avast.
Credits/Thanks:
Minimal ADB and Fastboot - Shimp208
CWM Recovery - Clockworkmod and Agrabren for porting it to the shield
Kwongger - Using his toolkit is what made me want to make my own
<<< DOWNLOAD >>>
Feel free to ask any question's, post any comment's or concern's, or make suggestion's for thing's you might like to see
Donation's are never expected,
and always appreciated. Please
leave your XDA username in the
field box so that I can say thank
you here for it.
THANK YOU FOR DOWNLOADING!!!

Changelog for 1.1:
With all the people not wanting to update to 77 I left 68
Changed some of the messages that are echoed
Added Koush's superuser App
Added a failsafe so if a wrong key is entered the program exits
Example:Requires a Y/N input if you hit 6 or M it will exit
Donation List
Budokaiboy
THANK YOU VERY MUCH!!!

Hey, are you planing on add an option to "ota ready" the device? You need to create a script that flash system, boot and recovery from stock, without a factory reset or userdata flashing, so, you can full unroot and full disable all system level changes in order to update I personally do this on my GF nexus 7 and my shield and everything work great

Antara33 said:
Hey, are you planing on add an option to "ota ready" the device? You need to create a script that flash system, boot and recovery from stock, without a factory reset or userdata flashing, so, you can full unroot and full disable all system level changes in order to update I personally do this on my GF nexus 7 and my shield and everything work great
Click to expand...
Click to collapse
There's an option to flash it back to the newest ota, but ya changing that will be easy. And you just gave me a good idea too.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.

Very nicely done always glad to see people developing tools for the community, and intergrating Minimal ADB and Fastboot into their projects!

shimp208 said:
Very nicely done always glad to see people developing tools for the community, and intergrating Minimal ADB and Fastboot into their projects!
Click to expand...
Click to collapse
Thanks alot. Your tool made it much easier to get everything up and running

Just finished adding Wipe and No Wipe System Restore options for the next release.

Thanks for your work , but one question the CWM recovery that will be flashed with your script is the recovery with the OTA installation allowed ?, another think the stock recovery is the 4.3 recovery ?, the last time i flashed a custom recovery to my shield i had to return out of the box to get all the new otas

Thank You so much OP! I just got my SHield about 2 weeks ago and thought all Dev was dead for it. Glad to see someone stilling messing around with stuff.:good:

Both of you, are most welcome. I enjoyed putting together, and I enjoy it even more when I hear people are using it.
psycho1200 said:
Thanks for your work , but one question the CWM recovery that will be flashed with your script is the recovery with the OTA installation allowed ?, another think the stock recovery is the 4.3 recovery ?, the last time i flashed a custom recovery to my shield i had to return out of the box to get all the new otas
Click to expand...
Click to collapse
Im misunderstanding your first question but ya the stock recovery you can flash is 4.3 i think i mentioned it somewhere but i need to go back and make sure i do have it mentioned in the thread and in the RAM file. Maybe I'll go back and add an option for the 4.2 recovery since there are probably still a few shields using it. In my next release There is a no wipe option for system recovery so it wont touch any of your apps or data and it will flash your device back to stock, remove root and the supersu app, making it OTA ready.
synplex said:
Thank You so much OP! I just got my SHield about 2 weeks ago and thought all Dev was dead for it. Glad to see someone stilling messing around with stuff.:good:
Click to expand...
Click to collapse
Oh yeah, there's a little bit of life left in the shield. I use to have the model of galaxy s4 that had the exploitable bootloader, but the speaker went out and warrantied it, so lost the aforementioned and all I really have on it now is root. Since the shield is easily mod-able I decided to start doing some stuff up for it. I do have a couple of other things planned for it :thumbup:

Attention K-Mart Staff! Massive clean up in Aisle 6!!
Ok, all cleaning done from the very first mention of the dispute. Sorry if some good arguments got caught up in the cleaning process, but in reality, they had absolutely "0" to do with the tool's functionality (issues, features, bugs, etc)
If you do not like a tool, for whatever reason, kindly move along to something that more suites your needs, Without.. posting things that have nothing to do with the tool itself. And this includes "all" parties who participated.
Keep it On Topic folks.
Cheers
MD

Thanks.
Nvidia Shield Root and More
Doing a little bit of reading goes a long way.

Do I need to unlock the Bootloader first before flashing Recovery and Super SU? also does unlocking the bootloader remove all installed apps? I just want root access. Thanks in advance

rylen said:
Do I need to unlock the Bootloader first before flashing Recovery and Super SU? also does unlocking the bootloader remove all installed apps? I just want root access. Thanks in advance
Click to expand...
Click to collapse
Yes you have to unlock the bootloader before doing root. It states right in the menu i believe the order theyre presented in is also the flashing order. Unlocking bootloader does basically do a factory data reset so yes youll lose everything in the process as well. Hope i answeres all your questions
Nvidia Shield Root and More
Doing a little bit of reading goes a long way.

hexitnow said:
Yes you have to unlock the bootloader before doing root. It states right in the menu i believe the order theyre presented in is also the flashing order. Unlocking bootloader does basically do a factory data reset so yes youll lose everything in the process as well. Hope i answeres all your questions
Nvidia Shield Root and More
Doing a little bit of reading goes a long way.
Click to expand...
Click to collapse
Thanks :good: I'm just making sure because I've already put a lot of apps and don't want to reinstall everything, but I went ahead and did all the steps because I really want to have root access. I'm currently reinstalling my apps now. Thanks again for making a simple program for noobs like me my Shield finally have root access (also debloated ).
I apologize for my bad grammar, English is not my native language.

rylen said:
Thanks :good: I'm just making sure because I've already put a lot of apps and don't want to reinstall everything, but I went ahead and did all the steps because I really want to have root access. I'm currently reinstalling my apps now. Thanks again for making a simple program for noobs like me my Shield finally have root access (also debloated ).
I apologize for my bad grammar, English is not my native language.
Click to expand...
Click to collapse
Your English isnt bad I couldn't tell it was your second language. Thanks though I appreciate it
Nvidia Shield Root and More
Doing a little bit of reading goes a long way.

Worked just fine once I got the windows 8.1 driver funstuff squared away. Great work hexitnow! And shout out to 1wayjohnny and wwjoshdew for the driver work around! The Shield is an awesome toy!!!

mta1981 said:
Worked just fine once I got the windows 8.1 driver funstuff squared away. Great work hexitnow! And shout out to 1wayjohnny and wwjoshdew for the driver work around! The Shield is an awesome toy!!!
Click to expand...
Click to collapse
Thanks alot man i appreciate it. The naked driver and fastboot/adb minimal setup made it easy to get up and running in a matter of minutes
:thumbup:
Nvidia Shield Root and More
Doing a little bit of reading goes a long way.

Hey, huge thanks for this. Wouldn't have rooted my shield without it!

f3tf said:
Hey, huge thanks for this. Wouldn't have rooted my shield without it!
Click to expand...
Click to collapse
No problem glad you liked it

[Q] Play Store crashes on download, then continues to crash

First, I apologize if this is the wrong place to post this. I am new to these forums.
Essentially, the other day, my Google services stopped working, due to something in my hosts file. I booted into recovery, and commented out android.clients.google.com mtalk.google.com, which had pointed to 74.125.93.113
After booting up normally, and logging in to my Google account again, I was able to access the play store among other apps normally.
However, when I went on the Play store to download an app, the store immidiatlely closed and prompted me with "Unfortunately, Google Play Store has stopped."
I have tried the following to solve my issue, none of which have worked.
Factory Reset
Clear Cache\Data
Reinstall from APK
Uninstall updates
Log out of google, restart, log back in
Wipe data from Titanium Backup and install anew
I have yet to find a solution to my problems.
My System Specs:
{
"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"
}
(Rooted 4.4)
Help would be much appreciated.
Thanks!

Any help please?

Did I post this in the wrong section?
Is there something wrong with my post?
Am I being ignored by the "great XDA minds" because apparently I'm stupid?
I still cannot fix my play store, and I would appreciate any form of help, please.

Delete please , this great mind did not read the op!
Tough problem.
Edit try clearing data for the play & play service app?

See edit

aviwdoowks said:
Delete please , this great mind did not read the op!
Tough problem.
Edit try clearing data for the play & play service app?
Click to expand...
Click to collapse
Already done that, no success.

themsftcpu said:
Already done that, no success.
Click to expand...
Click to collapse
Switch the dev runtime to the other try it & switch back. ART or dalvik.

Not to be bumping old threads, but I still have not resolved this issue. For now I am using an alternative app store, but I would like to know what the issue is.
I manually reinstalled gapps through adb, directly into /system, and it changed nothing. Any help would be appreciated.

themsftcpu said:
Not to be bumping old threads, but I still have not resolved this issue. For now I am using an alternative app store, but I would like to know what the issue is.
I manually reinstalled gapps through adb, directly into /system, and it changed nothing. Any help would be appreciated.
Click to expand...
Click to collapse
IF you have an unlocked bootloader (I'm assuming that you do, since you mention booting into recovery):
Follow the "Return to Stock" thread to flash the entire 4.4.2 SBF for your carrier (AT&T, I'm assuming - based on your screenshots).
I suggest using the manual method. If a factory reset did not help, this is likely your only hope.
SBFing back to stock can actually FIX a corrupt filesystem - a factory reset can not.
Everything you need is listed in that thread, including links to the SBF files themselves, and all drivers you may need (which are probably already installed since you mention booting into recovery and modifying your 'hosts' file).
If you do NOT have an unlocked BL, let me know. I will help you with alternative instructions, if you tell me which exploit you are using, and whether or not you are using safestrap, and which android version you are on (4.4?)
DON'T flash the 4.4.2 SBF if you are not unlocked or you will never be able to root and achieve write-protect-disable.
Good Luck

samwathegreat said:
IF you have an unlocked bootloader (I'm assuming that you do, since you mention booting into recovery):
Follow the "Return to Stock" thread to flash the entire 4.4.2 SBF for your carrier (AT&T, I'm assuming - based on your screenshots).
I suggest using the manual method. If a factory reset did not help, this is likely your only hope.
SBFing back to stock can actually FIX a corrupt filesystem - a factory reset can not.
Everything you need is listed in that thread, including links to the SBF files themselves, and all drivers you may need (which are probably already installed since you mention booting into recovery and modifying your 'hosts' file).
If you do NOT have an unlocked BL, let me know. I will help you with alternative instructions, if you tell me which exploit you are using, and whether or not you are using safestrap, and which android version you are on (4.4?)
DON'T flash the 4.4.2 SBF if you are not unlocked or you will never be able to root and achieve write-protect-disable.
Good Luck
Click to expand...
Click to collapse
Unfortunately I do not have an unlocked bootloader, as there is no way that I am aware to unlock the Moto X. When I said booting into recovery, I meant /system read\write mode. I am running Android 4.4 still, never updated to 4.4.2. I have adb, mfastboot (as well as fastboot on the device), and RSD Lite for flashing images to the device.

themsftcpu said:
Unfortunately I do not have an unlocked bootloader, as there is no way that I am aware to unlock the Moto X. When I said booting into recovery, I meant /system read\write mode. I am running Android 4.4 still, never updated to 4.4.2. I have adb, mfastboot (as well as fastboot on the device), and RSD Lite for flashing images to the device.
Click to expand...
Click to collapse
OK. Yes, there is a possibility to unlock your device. See the "China Middleman Back?" thread for details.
Anyways, since you are on 4.4, I assume you are using the "Slap My Moto" exploit + MotoWpNoMo (write protect disable exploit). (I asked which exploit you used, but you didn't advise)
What YOU will need to do (with locked BL) is follow the instructions in the "Return to Stock" thread, but instead of what I mentioned earlier, flash the entire 4.4 SBF for YOUR CARRIER (you never confirmed AT&T...)
After you have flashed the entire 4.4 SBF, you will need to re-apply the exploits to re-gain root and Write Protect Disable.
Once this is finished, your device should work 100% properly.
BE VERY CAREFUL. It seems you aren't aware of many of the nuances regarding the Moto X, so here is some info for you:
1. If you EVER attempt to downgrade your software version, you will brick your phone - possibly permanently. This applies to ALL Moto X phones - locked, unlocked, rooted, or not.
2. Additionally, if you ever update to 4.4.2, you will completely/permanently LOSE the ability to root and achieve write protect disable (unless you unlock the BL). There is a new temporary root method that works on 4.4.2, but it does not disable write protect, so you cannot write to /system, cannot flash custom recovery, and every time you reboot your device, you will have to re-run the exploit to gain root back again.
3. There is a gentleman from China who is selling bootloader unlock codes for the Moto X. He somehow has access to some of Motorola's database. Currently, he can unlock most devices that have a manufacture date of 2014 (he doesn't have access to 2013 codes). The cost is $45 (very reasonable, IMO), and you can find all the details in the "China Middleman Back?" thread. If you DO decide to try this unlock method and are successful, you will need to re-flash the entire stock SBF to remove the 'exploits' you are using. Also, with unlocked BL, you can successfully root and flash recovery (and write to /system) no matter which android version you are on.
Hope this clears everything up for you. Let me know if you have questions.

samwathegreat said:
OK. Yes, there is a possibility to unlock your device. See the "China Middleman Back?" thread for details.
Anyways, since you are on 4.4, I assume you are using the "Slap My Moto" exploit + MotoWpNoMo (write protect disable exploit). (I asked which exploit you used, but you didn't advise)
What YOU will need to do (with locked BL) is follow the instructions in the "Return to Stock" thread, but instead of what I mentioned earlier, flash the entire 4.4 SBF for YOUR CARRIER (you never confirmed AT&T...)
After you have flashed the entire 4.4 SBF, you will need to re-apply the exploits to re-gain root and Write Protect Disable.
Once this is finished, your device should work 100% properly.
BE VERY CAREFUL. It seems you aren't aware of many of the nuances regarding the Moto X, so here is some info for you:
1. If you EVER attempt to downgrade your software version, you will brick your phone - possibly permanently. This applies to ALL Moto X phones - locked, unlocked, rooted, or not.
2. Additionally, if you ever update to 4.4.2, you will completely/permanently LOSE the ability to root and achieve write protect disable (unless you unlock the BL). There is a new temporary root method that works on 4.4.2, but it does not disable write protect, so you cannot write to /system, cannot flash custom recovery, and every time you reboot your device, you will have to re-run the exploit to gain root back again.
3. There is a gentleman from China who is selling bootloader unlock codes for the Moto X. He somehow has access to some of Motorola's database. Currently, he can unlock most devices that have a manufacture date of 2014 (he doesn't have access to 2013 codes). The cost is $45 (very reasonable, IMO), and you can find all the details in the "China Middleman Back?" thread. If you DO decide to try this unlock method and are successful, you will need to re-flash the entire stock SBF to remove the 'exploits' you are using. Also, with unlocked BL, you can successfully root and flash recovery (and write to /system) no matter which android version you are on.
Hope this clears everything up for you. Let me know if you have questions.
Click to expand...
Click to collapse
Sorry, I didn't see the exploit, but yes I am using the SlapMyMoto exploit .here Yes I am using ATT
In reponse to
1. Got it, don't downgrade whatever I do.
2. I actually disabled the OTA updater app because the 4.4.2 update notification was stupid, and I accidentally hit "Yes, update."
3. I have the XT1058, which is the 2013 model. Besides that, not sure I want to be giving my money to a (hacker?).
As for the instructions above that: I will try in the morning, I have an important phone call to take tomorrow and I can't afford to have my phone acting up.

themsftcpu said:
Sorry, I didn't see the exploit, but yes I am using the SlapMyMoto exploit .here Yes I am using ATT
In reponse to
1. Got it, don't downgrade whatever I do.
2. I actually disabled the OTA updater app because the 4.4.2 update notification was stupid, and I accidentally hit "Yes, update."
3. I have the XT1058, which is the 2013 model. Besides that, not sure I want to be giving my money to a (hacker?).
As for the instructions above that: I will try in the morning, I have an important phone call to take tomorrow and I can't afford to have my phone acting up.
Click to expand...
Click to collapse
samwathegreat said:
1. Great!
2. Good idea. Disabling the OTA updater is wise to prevent the possibility of losing root/write protect.
3. What is important is the date YOUR phone was manufactured. If you purchased it in 2013, obviously it has a 2013 manufacture date, but the Moto factory is still churning out brand new XT1058s. If you are curious, the manufacture date is listed on the box, OR you can find it by issuing "fastboot getvar all". I understand your reluctance to send money to this gentleman - fortunately you never updated to 4.4.2 so you can still use the 4.4 exploits. This is the ONLY option to achieve full root for those on 4.4.2+
Again, I highly recommend using the manual method (using fastboot/mfastboot) listed in the Return to Stock thread. Faster and easier than using RSD Lite, IMO.
Please let us know if the procedure I outlined fixes your problem once you have completed all the steps.
Click to expand...
Click to collapse
I must make a slight revision to my previous statements:
We always advise users to never downgrade, because IF the bootloader OR gpt.bin (partition table) changed between the updates, the phone will be a brick. There is one exception: You CAN successfully downgrade 4.4 to the 4.2.2 Post-Camera Update firmware (NOT the original 4.2.2), because this is the only version where neither the bootloader, nor partition table was updated.
Upon reading up on SlapMyMoto, it is necessary to 'downgrade' to the 4.2.2 Post-Camera Update.
Please do not use the guide you linked from Reddit -- jcase has since released a NEW version of SlapMyMoto, and you should follow the new guide here: http://forum.xda-developers.com/moto-x/orig-development/4-4-root-slapmymoto-1-0-motowpnomo-t2538896
Also, you won't be flashing the 4.4 SBF as I had previously stated, but rather the Post-Camera Update firmware that is linked in jcase's thread.
Flash the AT&T file linked in jcase's thread, per the "Return to Stock" manual method, then follow the instructions in his thread.
This should fix your issues.
Sorry for the confusion....I haven't used SlapMyMoto personally, as I have an unlocked bootloader. In hindsight, I should have read up on SlapMyMoto before I advised you....

themsftcpu said:
Essentially, the other day, my Google services stopped working, due to something in my hosts file. I booted into recovery, and commented out android.clients.google.com mtalk.google.com, which had pointed to 74.125.93.113
Click to expand...
Click to collapse
From the OP, it looks like you edited the HOSTS file and have had problems since, but you do not say if you un-did your host file edit.
Did you?
If no, you should try that first. try and put the original, unmodified hosts file on there.

Gear Live Stock Firmware Image - 24JUL14 & Bootable Root ADB image

Hi guys, I just managed to pull the stock firmware image off the Sprat, with the assistance of @Dees_Troy. We've been working on this for a few days. Lots of highs and lots of lows. Lots of hardware glitches, device overheating, reading kernel logs to troubleshoot problems... And you know what? All of it could have been avoided if Samsung had released a stock image.
Without any further ado, though, you can find a factory image for this device here: https://builds.casual-dev.com/index.php?dir=random/sprat/
Here is the first custom kernel created for this device. It's mostly dees troy's work, he compiled it and made it operate, but I had to reimage it a few times to make it operate properly. If you absolutely need root for checking something out right now, you can fastboot boot this image and get it.
If you'd like to pull your OWN firwmare including the EFS(serial info) for the device, you can use this command in adb root shell after booting the above image.
Code:
cd /dev/block/platform/msm_sdcc.1/by-name;
f=`ls`;
for f in $x;
do
dd if=$f of=/data/local/tmp/$f.img;
done;
rm /data/local/tmp/userdata.img
exit;
adb pull /data/local/tmp/
the contents of the entire device will come to your computer
now clean up the temp folder.
Code:
adb shell rm /data/local/tmp/*
You now have the firmware above + EFS data.
[rant]
I mean seriously.. Samsung, WTF? I've been working on this for 5 straight days now.
Why did I have to go through the process of keeping this Quad-core watch cool while i tinkered with UART, and continuously rebooted it?
{
"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"
}
Why did I have to wade knee deep in your kernel problems to get this done?
Is it becoming apparent that Samsung doesn't want people messing with their "open devices"? I mean, I can think of no other reason they haven't released a stock image for a device which can be destroyed with a bad flash.
[/rant]
Either way, we finally have a stock image and that means Dees_Troy can release a TWRP, ROM devs can begin working with the system, and those in need of stock firmware now have access to it. Pretty good news if you ask me.

Thank you Adam and I suppose I can speak for every Live owner here when I say we really do appreciate it. I can't wait to start tinkering with it and lets hope we can get that WatchFace API soon. I'm dying for a more sophisticated looking face with a more blue and silver brushed metal look to it. Can't find one anywhere. Thanks again Adam. What would we do without u?
---------- Post added at 09:03 PM ---------- Previous post was at 09:01 PM ----------
Oh and if you add any more green text to your display... just go head on and Follow The White Rabbit....

Sweet Adam, you made a lot of progress since Friday

thanks for all this work! Now to start working on port for Gear 1... Haven't messed with this stuff since HD2 days....Ugh.
Chris

I'd like to get someone to test some TWRP images for me. Need someone that's set up to use adb and fastboot and has basic working knowledge of how to use them. Find me in #twrp on Freenode.

Dees_Troy said:
I'd like to get someone to test some TWRP images for me. Need someone that's set up to use adb and fastboot and has basic working knowledge of how to use them. Find me in #twrp on Freenode.
Click to expand...
Click to collapse
Contacting now.

Dees_Troy said:
I'd like to get someone to test some TWRP images for me. Need someone that's set up to use adb and fastboot and has basic working knowledge of how to use them. Find me in #twrp on Freenode.
Click to expand...
Click to collapse
Incase you missed the link on iirc, http://pastebin.com/5rUD9X0t

Annnnnd this is why i ditched Samsung after the SGSII, Im so glad I got the G Watch instead.
Seems to be a Thing now that Samsung is playing hard to beat with factory images and source, Devs should jump on some form of anti Sammy bandwagon because although this is sure a great feat in hacking but for people here who Crack flash and test stuff for devs on their devices this is a pain and slows down evolution.
if sammy continue with his imagine all the ideas they can't steal from the clever devs here at XDA, I say screw them and buy devices from companies who truly keep android open source

Can this be used in Odin?

Krunk_Kracker said:
Can this be used in Odin?
Click to expand...
Click to collapse
No, it is a fastboot image

How do I actually use this!? Sorry for the noobness haha. I understand I have to unlock my bootloader first, but how do I actually obtain root after I do that? TIA!

Joe0113 said:
How do I actually use this!? Sorry for the noobness haha. I understand I have to unlock my bootloader first, but how do I actually obtain root after I do that? TIA!
Click to expand...
Click to collapse
Hello,
As these are ADB/Fastboot packages, you will need do the following
1) Setup the Android SDK (for ADB and Fastboot)
2) Unlock the bootloader
3) Use the "fastboot boot <filename.img>" (replace this with the location of the extracted content from the zip file)
I honestly would recommend against trying this unless you are a bit seasoned as breakage is possible.

Boot into TWRP
Mount the system
Use the TWRP terminal emulator
rm /system/app/SuperSU.apk
OK so these are the instructions I was given to root. I am currently sitting in TWRP, system was mounted, when I hit reboot system, it told me I wasnt rooted, so I swiped to root...rebooted back to recovery...clicked terminal command which opened up a directory telling me to choose a starting folder :|
this is where im lost.. Also how do I type anything into the terminal commands once I get it open since theres no keyboard lol
Manually removed it using the file manager though its called superuser.apk and it works..Guess im rooted given I can use the rebooter that Adam posted!

KMyers said:
Hello,
As these are ADB/Fastboot packages, you will need do the following
1) Setup the Android SDK (for ADB and Fastboot)
2) Unlock the bootloader
3) Use the "fastboot boot <filename.img>" (replace this with the location of the extracted content from the zip file)
I honestly would recommend against trying this unless you are a bit seasoned as breakage is possible.
Click to expand...
Click to collapse
Do we have to do each individual img? I downloaded the file, extracted it and theres 23 img files lol. I have yet to do anything with a .tar file also
Im debating on returning to stock and taking the watch back to wait for the 360,

Instructions on returning to Stock??
Could someone please post some instructions on returning to Stock? I flash the Octa Rom and did not make a back up and then tried returning to stock by flashing the system.img and it would not boot. I have returned to stock with Nexus devices in the past but looking at the stock firmware image files here I'm not getting how this works. PLEASE HELP

AdamOutler said:
Hi guys, I just managed to pull the stock firmware image off the Sprat, with the assistance of @Dees_Troy. We've been working on this for a few days. Lots of highs and lots of lows. Lots of hardware glitches, device overheating, reading kernel logs to troubleshoot problems... And you know what? All of it could have been avoided if Samsung had released a stock image.
Without any further ado, though, you can find a factory image for this device here: https://builds.casual-dev.com/index.php?dir=random/sprat/
Here is the first custom kernel created for this device. It's mostly dees troy's work, he compiled it and made it operate, but I had to reimage it a few times to make it operate properly. If you absolutely need root for checking something out right now, you can fastboot boot this image and get it.
If you'd like to pull your OWN firwmare including the EFS(serial info) for the device, you can use this command in adb root shell after booting the above image.
Code:
cd /dev/block/platform/msm_sdcc.1/by-name;
f=`ls`;
for f in $x;
do
dd if=$f of=/data/local/tmp/$f.img;
done;
rm /data/local/tmp/userdata.img
exit;
adb pull /data/local/tmp/
the contents of the entire device will come to your computer
now clean up the temp folder.
Code:
adb shell rm /data/local/tmp/*
You now have the firmware above + EFS data.
[rant]
I mean seriously.. Samsung, WTF? I've been working on this for 5 straight days now.
Why did I have to go through the process of keeping this Quad-core watch cool while i tinkered with UART, and continuously rebooted it?
Why did I have to wade knee deep in your kernel problems to get this done?
Is it becoming apparent that Samsung doesn't want people messing with their "open devices"? I mean, I can think of no other reason they haven't released a stock image for a device which can be destroyed with a bad flash.
[/rant]
Either way, we finally have a stock image and that means Dees_Troy can release a TWRP, ROM devs can begin working with the system, and those in need of stock firmware now have access to it. Pretty good news if you ask me.
Click to expand...
Click to collapse
Hi adam i have a Gear Live with Build KMV78Y and when i fastboot boot rootADB.img my device freezes at the bootloader screen and never reboots. i have to adb reboot to get out of it. which is the funny part since i am still on the bootloader screen but adb works. any idea of what is going on here thanks.
Tom
Edit Never Mind i got it just wasnt expecting it to work this way. pretty funny temp root. why not make it perminant root?

Tomsgt said:
Hi adam i have a Gear Live with Build KMV78Y and when i fastboot boot rootADB.img my device freezes at the bootloader screen and never reboots. i have to adb reboot to get out of it. which is the funny part since i am still on the bootloader screen but adb works. any idea of what is going on here thanks.
Tom
Edit Never Mind i got it just wasnt expecting it to work this way. pretty funny temp root. why not make it perminant root?
Click to expand...
Click to collapse
Hiyas Tom..did you really get your Gear?!?!?!

Tower1972 said:
Hiyas Tom..did you really get your Gear?!?!?!
Click to expand...
Click to collapse
yes got it today and working on the Restore Tool like my LG G Watch restore tool. right now its tested and working just cleaning it up

Tomsgt said:
yes got it today and working on the Restore Tool like my LG G Watch restore tool. right now its tested and working just cleaning it up
Click to expand...
Click to collapse
That's the best news I've heard all day!

Tower1972 said:
That's the best news I've heard all day!
Click to expand...
Click to collapse
Samsung Gear Live Tool is up click here and enjoy

How to Root my N6 w/o PC?

Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!

shabydog said:
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!
Click to expand...
Click to collapse
AFAIK you will need a pc to 1)unlock your bootloader and 2)flash TWRP. After that the rest can be done locally. I also never used any toolkit. Making it easy is making it more dangerous IMHO.

Droidphilev said:
I also never used any toolkit. Making it easy is making it more dangerous IMHO.
Click to expand...
Click to collapse
Second that.
shabydog said:
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Click to expand...
Click to collapse
So at least once you need to connect your phone to a desktop computer. It can be practically running anything, within reason of course: Wiindows. Mac OSX, Linux (almost any distro).
You need to unlock your bootloader with one command, but a warning here: Unlocking the bootloader will erase everything from your phone..
Then you need to install a custom recovery, preferably TWRP. After that everything can be done from the phone itself. Well at least until you soft brick it somehow, then you'll might have to use the PC again.
Also two things:
1. No OTAs for rooted phones
2. Don't lock your bootloader if you want to mess with it, because with a locked bootloader, and Enable OEM Unlocking set to off, and without TWRP, if you soft brick it accidentally, you are boned.

Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use?
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
And i really prefer to do it on the device and not by ADB commands.
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!

shabydog said:
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!
Click to expand...
Click to collapse
Well, you still will have to unlock it, if you want root, or want to flash a custom recovery.
Sent from my Nexus 6 running cyosp using Tapatalk

shabydog said:
......I really don't like the issue of trying to set the drivers of fastboot/google and so on!
Click to expand...
Click to collapse
Than do not 'root' your phone.

hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:

simms22 said:
hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:
Click to expand...
Click to collapse
Ha ha, or I don't want my birthday to be on the day I was born every year ?

I can recommend the NTRT, the Nexus Telepathic Rooting Tools.

OK.
I want to do that with a toolkit, only bcs it install the drivers.
What Is the most recommended and easiest to use?
I do looking for the 1 click do all.
Does NTRT do that?
Thank you all.

we are eventually goung to have a "my n6 is bricked, how do i fix it with one click" thread here. seriously though, thats what happens when you use toolkits, but do no real research about modding your device.

Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Sent from my Nexus 6 using Tapatalk

shabydog said:
Could anybody guide me through the steps, if needed?
Click to expand...
Click to collapse
<prev> step <next>

simms22 said:
seriously though, thats what happens when you use toolkits, but do no real research about modding your device.
Click to expand...
Click to collapse
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
wtherrell said:
Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Click to expand...
Click to collapse
It is fairly enough to read directions and slowly-slowly.
NLBeev said:
<prev> step <next>
Click to expand...
Click to collapse
Thanks!
==========================================================
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?

shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
Click to expand...
Click to collapse
i agree with you. if there is somebody who knows the ins and outs already, a one click root would be great. and there will be. problem is that marshmallow just came out, and a few things have changed, like like yoe also need a custom kernel to have root on marshmallow.

shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
It is fairly enough to read directions and slowly-slowly.
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?
Click to expand...
Click to collapse
There is a reason you're pushing this topic, and I'm quite sure it's because you would feel safer, if there was a tool that did the scary things instead of you. Well, there's no such tool. If you were willing to search XDA, you would find out that the first two weeks after Marshmallow came out were about people bricking their Nexus 6s with toolkits. Then the toolkit got updated and suddenly it knew that is has to flash a modified boot.img too for the root not to brick the phone. But for two weeks it didn't know, because it wasn't necessary for Lollipop. And it will only work until the next security update comes out. And that's once a month.
Meanwhile those who were willing to use the search function, and learned the five minute procedure, were able to update their rooted phones to the next security update and were able to root it as soon as the new modified boot image came out.
And this above is not something somebody will put in a help, or instructions for future updates.

Actually, this is my first time and I was able to do it pretty easily.
fastboot devices
fastboot oem unlock
my bootloader was unlocked within 30 seconds of turning it on.
then, you can easily root via CF Auto root. Just put it into fastboot then doubleclick on the windows, then root, etc....
or.............go into fastboot flash recovery twrpxxxx.img, then it always offers to run SuperSU, and you get custom recovery and root at the same time, etc......
actually the biggest pain is unlocking the bootloader. My Galaxy S4 already was unlocked, so all I did was use goomanager, flash TWRP which always offers to run SuperSU if you don't have it.
Pretty easy, I did unlock bootloader, root, and custom recovery in 10 min.
---------- Post added at 01:48 AM ---------- Previous post was at 01:44 AM ----------
............................Then I got sick of stock Google's ROM in 15 min and wiped it and put a custom ROM instead.

Thank you all so much...
@mikeprius
Thank you so much for the info'!
But, could you plz write more details? such as:
1. How did you installed the drivers? (from my expirience, many times the pc dosent install this easily).
I just need the Google oem driver and that's it?
2. When drivers was set - did you made anything in your phones settings? Which?
3. What did you had to do before pushing the files? (Like...put all the files in the same folder? *which files?)
4. And then entered to fastboot mode and typed in these commands in pc:
fastboot devices
fastboot oem unlock
Regarding your last sentence ("or...."):
If i just flash the recovery via fastbot mode I can enter to twrp recovery and it offers to flash the SuperSU?
Sounds to me the best option.
Thanks!

1. The drivers were set from a previous device, so I didn't have to set them, but they can be downloaded and set though.
2. You need to enable developer options and select OEM unlock and USB debugging.
3. I didn't push the files, I just had them on my computer and ran fastboot commands.
4. Those commands are to unlock the bootloader.
There are a lot of different ways to do the same thing (Root, custom recovery, unlock bootloader)
1. Run CF Auto Root on a locked bootloader. It will unlock it automatically (Chainfire has it set that way), root, then download Flashify app and flash the latest img of TWRP.
2. Run fastboot commands to manually unlock the bootloader, flash TWRP, then use TWRP's SuperSU which will root it.
3. Run fastboot commands to unlock bootloader, run CF Autoroot which will root and load SuperSU, then flash TWRP via Flashify or fastboot.
There are many different ways to do the same thing. I actually just googled youtube videos and watched them.
TWRP has SuperSU and root built in. TWRP knows if you don't have it and offers to load it for you.
I went the scenic route just because, but presumably you can achieve all (3) using Option #1 without having to deal with fastboot, adb, etc.....Chainfire's script runs automatically.

I realy try to help people but users that run into problems because of the usage of tookits (and innability to solve problems and/or even lack the most basic knowledge needed) should ask the toolkit dev. for support imo, and not boughter users that have invested time and effort to gain that knowledge to clean up their mess. Period

Flashing from Build Number SU3TL-39 to SU4TL-44

Please excuse me if this is a simple process, but I cannot seem to locate a thread on how to flash to -44, as I am slowly in the process of trying to root my Turbo.
Currently living off of FoxFi USB tethering, but finally would like to obtain root access since it is available as I miss having wifi tethering!
I'd like to add, that the process of rooting this phone is a bit more advanced than what I have done over the years. I'm used to plugging the phone in the PC, installing a software on the PC, then "one click" root and reboot.
Any insight or recommendations is greatly appreciated! Tethering is my main reason for root, but I'd still like the versatility of having root access.
Thanks XDA!

coconutt said:
Please excuse me if this is a simple process, but I cannot seem to locate a thread on how to flash to -44, as I am slowly in the process of trying to root my Turbo.
Currently living off of FoxFi USB tethering, but finally would like to obtain root access since it is available as I miss having wifi tethering!
I'd like to add, that the process of rooting this phone is a bit more advanced than what I have done over the years. I'm used to plugging the phone in the PC, installing a software on the PC, then "one click" root and reboot.
Any insight or recommendations is greatly appreciated! Tethering is my main reason for root, but I'd still like the versatility of having root access.
Thanks XDA!
Click to expand...
Click to collapse
THIS METHOD WILL VOID YOUR WARRANTY. But if you're on xda, chances are you knew that. It's also irreversible.
If you're not unlocked and not rooted, take the OTA that is available to get you to -44. 44 is the most recent version available, so there is no risk of updating too far.
Once you're on 44, download the Kingroot apk and install it. http://www.kingroot.net/
Then download this version of Sunshine and install it. http://forum.xda-developers.com/showpost.php?p=64027688&postcount=4064
Once both are installed, open Kingroot and follow the instructions to try and get temporary root. It doesn't always work, and sometimes you have to try multiple times. If it fails, uninstall Kingroot, reboot the phone and try again. Wiping cache in the recovery menu sometimes helps too.
After Kingroot says it is successful, run Sunshine and follow the prompts. Sunshine costs $25, so if you're not cool with that, don't try this method. If Sunshine succeeds, your phone will reboot and instead of the Motorola M that you usually see at boot, you'll see a bootloader unlocked warning message. If Sunshine fails, uninstall Kingroot, reboot, reinstall and try again.
Once your bootloader is unlocked, you need to get a custom recovery installed (TWRP), which you can get here http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308. The easiest way to flash that in my opinion is with Fastboot. The easiest way to install Fastboot is by installing this: http://forum.xda-developers.com/showthread.php?t=231779. You'll also need to make sure you have the appropriate drivers so that your PC will recognize your phone. This will ensure that: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Put the TWRP .img file that you downloaded into the folder that you installed Minimal ADB and Fastboot to, boot your phone in bootloader mode, plug it in to the computer, start Minimal ADB and Fastboot, and type the following command:
fastboot flash recovery <name of TWRP .img file>
Once you have that, the sky is the limit. If you only want to add permanent root to your phone, download this: http://forum.xda-developers.com/showthread.php?t=1538053, put it somewhere on your phone, boot into recovery mode (which will now be TWRP instead of the stock recovery), select install, navigate to the .zip file and flash it. That's it. If you want to try cyanogenmod or any other custom rom, see their respective xda threads for details.
Oh, and as for enabling tethering for free, which is only necessary if you have an unlimited data plan (if not, it's free already, just use Verizon's app to do it), find any root browser, search for a file called build.prop, open it with the browser's text editor and add this line to the end of it:
net.tethering.noprovisioning=true
Remember to save when you're done.
---------- Post added 7th December 2015 at 12:00 AM ---------- Previous post was 6th December 2015 at 11:45 PM ----------
If you need more help, this guy might explain better than I did: http://forum.xda-developers.com/droid-turbo/general/videos-tutorials-root-restoring-droid-t3076456

http://forum.xda-developers.com/showthread.php?t=2317790
Link for minimal adb and fastboot, I think this is the right one?

TheSt33v said:
THIS METHOD WILL VOID YOUR WARRANTY. But if you're on xda, chances are you knew that. It's also irreversible.
If you're not unlocked and not rooted, take the OTA that is available to get you to -44. 44 is the most recent version available, so there is no risk of updating too far.
Once you're on 44, download the Kingroot apk and install it.
Oh, and as for enabling tethering for free, which is only necessary if you have an unlimited data plan (if not, it's free already, just use Verizon's app to do it), find any root browser, search for a file called build.prop, open it with the browser's text editor and add this line to the end of it:
net.tethering.noprovisioning=true
Remember to save when you're done.
Click to expand...
Click to collapse
Sorry for the late reply as I'm having the free time to fidget with the phone.
To my understanding about taking the OTA that is available to me is not the Marshmallow update? I have a screenshot of the OTA when it pops up each night, but not sure if I'm allowed to img code it on here. But it displays "New version: 23.21.44.en.US"... I'd just like for you to confirm that this is the -44 update before I advance, thanks a bunch!
Also, I tried the buildprop edit on my current -39 version and it won't let me save the file. I take it this can be done after rooting though.

coconutt said:
Sorry for the late reply as I'm having the free time to fidget with the phone.
To my understanding about taking the OTA that is available to me is not the Marshmallow update? I have a screenshot of the OTA when it pops up each night, but not sure if I'm allowed to img code it on here. But it displays "New version: 23.21.44.en.US"... I'd just like for you to confirm that this is the -44 update before I advance, thanks a bunch!
Also, I tried the buildprop edit on my current -39 version and it won't let me save the file. I take it this can be done after rooting though.
Click to expand...
Click to collapse
Yep. That's it. The marshmallow update isn't out yet, so it cannot be the marshmallow update. Build.prop is located on the system partition, which is write-protected on a stock Turbo. Once you unlock with Sunshine (just rooting with Kingroot isn't good enough), you will be able to edit it. Also, Sunshine no longer needs Kingroot. Simply download the latest version here http://theroot.ninja/download.html and use it to unlock once you're on -44.

TheSt33v said:
Yep. That's it. The marshmallow update isn't out yet, so it cannot be the marshmallow update. Build.prop is located on the system partition, which is write-protected on a stock Turbo. Once you unlock with Sunshine (just rooting with Kingroot isn't good enough), you will be able to edit it. Also, Sunshine no longer needs Kingroot. Simply download the latest version here therootdotninja/download and use it to unlock once you're on -44.
Click to expand...
Click to collapse
Well that was easy! Bootloader unlocked!! Thanks.
Now on to the rooting process. Currently getting my Moto drivers updated on the PC, and I've also downloaded the TWRP file onto the PC as well. As for Fastboot, the link you've provided takes me to a 2005 thread! I'm sure I can find a link to Fastboot to download, but I wanna make sure I get the one I need, if that makes any sense? (Don't mind me being paranoid)

TheSt33v said:
Put the TWRP .img file that you downloaded into the folder that you installed Minimal ADB and Fastboot to, boot your phone in bootloader mode, plug it in to the computer, start Minimal ADB and Fastboot, and type the following command:
fastboot flash recovery <name of TWRP .img file>
Click to expand...
Click to collapse
For an update, I got everything I needed downloaded. I am stuck at this point though, as I can't get passed this point when I input the above command!
EDIT:
I skipped the recovery flash, and went ahead with just the build prop edit for tethering after installing King Root. Rebooted it and still have root, and tethering works. Thanks a bunch!!

coconutt said:
For an update, I got everything I needed downloaded. I am stuck at this point though, as I can't get passed this point when I input the above command!
EDIT:
I skipped the recovery flash, and went ahead with just the build prop edit for tethering after installing King Root. Rebooted it and still have root, and tethering works. Thanks a bunch!!
Click to expand...
Click to collapse
If you want twrp flashify works well.

Database Develop

welcome