Database Users

How to push files through ADB

Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish

usadevil7193 said:
hi mate...i m new to android..i own a nexus1..hav rooted without unlockin d bootloader..i am tryin to push d track ball to wake mod...evry time i type adb remount it says permission denied..any ideas to get things workin...???????
Click to expand...
Click to collapse
Welcome to XDA and Android! Are you trying to get help for your Nexus One? This forum here is specifically for the HTC Hero CDMA.
You will probably find better and more specific help in the Nexus One forums which are here: http://forum.xda-developers.com/forumdisplay.php?f=556

Great post, very easy to follow, thank you.

yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help

this also works for the samsung Galaxy S in recovery mode.

mikeybonez28 said:
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
Click to expand...
Click to collapse
mine shows up but then says error, device offline

hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx

yogi2010 said:
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
Click to expand...
Click to collapse
i had the same issue with something i was trying to push. I think you need to make sure you have exactly the same file name like caps and all. i was trying to push rootexplorer.apk and i got the same message but i then changed it to RootExplorer.apk and it work.(notice the difference in caps)

just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers

Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?

{LCD}Stelios said:
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
Click to expand...
Click to collapse
Make sure your have the drivers for your phone installed first of all.....Then, in your command prompt you have to change directories to the sdk (which you made harder by not installing to C:\
Try: cd Program Files\Android\android-sdk\tools
Then type: adb devices
That should return "xxxxxxdevice" connected....Then you know you have it set up.

Look in kyouko sig he has all the commands for adb
Sent from my HERO200 using XDA App

Bierce22 said:
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Click to expand...
Click to collapse
great video arse....thanks for the help donkey

Flashing fresh ROM via ADB in Linux
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo

pacut said:
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
Click to expand...
Click to collapse
There is a thread somewhere on how to flash without a SD card and flashed using adb I believe, but don't take my word for it. Adb works fine with Linux, just have to set it up differently. Look in my sig and select the compile aosp on Ubuntu one and follow instructions on getting the USB set up.
Sent from Dorian's HTC Hero CDMA

Yes, I saw it. It's http://forum.xda-developers.com/showthread.php?t=911228
The fact is...still have to navigate through menu via VolumeUp/volumeDown buttons

Maybe through ROM manager, premium, I can install ROM direclty.
I am gonna trying
YES ! It works !

Hi I need help. I accidentally wipped my phone in CWM and now I'm trying to use adb push to push the update.zip into my phone sd everything seems to work but then in CMW it says there are no files..
any suggestions?
[Edit]
nevermind
I kept trying different locations
not sure which one did the trick but I'll list the one's I tried
so \update.zip /sdcard/
.... /sdcard/update.zip
(note I put "/update.zip" thinking maybe it needed to be reallocated to the same file/destination

Can i use adb push *.apk /system/app to push several files at once, and then repeat but using *.odex instead of *.apk? I keep ending up getting the same error, and i want to find out which app is messing with me...

rulermon said:
Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
Click to expand...
Click to collapse
Hey guys ...
I have also rooted my phone , everything was OK until one day i tried to write something to /system/app and i recieve this error:
in Addition , i am writing "adb shell" and it shows me $
if i am doing adb shell --> $ --> su --> it shows #
Can some1 knows what is the problem?

Corrupt settings.db

Here's one for the genius'
1. I rooted my phone successfully
2. I edited the settings.db file to allow side apps
3. I copied to copy the original settings.db file (that I think I may have corrupted) back and when I restarted my phone, I get a blank screen.... it will not boot into android.
I have a backup of the original settings.db file, but I need to know if there is there a way that I can copy this file back from recovery mode so that I can boot. I do get command line access in through adb, but it will not let me gain su access. Any help would be great.

I would say just hard reset the phone. It'll restore the settings.db back to the factory one.

masterofthebass said:
I would say just hard reset the phone. It'll restore the settings.db back to the factory one.
Click to expand...
Click to collapse
is it possible to do a hard reset without booting into android? I didn't know about that drats!

systoxity said:
is it possible to do a hard reset without booting into android? I didn't know about that drats!
Click to expand...
Click to collapse
I'm fairly sure there's a way to completely reset the phone while in recovery mode. Haven't done it, but I read about it somewhere.

I did a reset, but the phone still goes blank after the Galaxy logo. If I can mount the sdcard in recovery I think I can fix it. But I can't get it mounted.

take it back and ask for a replacement. Use your imagination.
If this fails and you have a brick phone that you cant do anything with, then i personally would try to open it up and see if that internal microsd card can be removed and hooked up to a card reader. Ofc this is very risky, and i am in no way telling you that you should follow in my theoretical footsteps. Be careful and good luck.

Is there a way to mount the internal sdcard. I have adb access in recovery mode, but not root. I have removable sdcard, but it does not seem to access that one from the recovery mode.

Also, I see the drives in "My Computer", but when I click them they ask me to insert a card. Is there a way to manually mount it from the ADB shell?

you have adb access? So when you have it plugged in and you go to cmd and type adb devices, the phone pops up as connected?

Yes... I have shell access, just can't get root or mount anything. I had already rooted the phone before all this began.

Try this.
Boot into recovery and type this into your computer
"adb shell"
"mount /sdcard"
"exit"
"adb push <whateverfile> /<path>/<whateverfile>"
"adb shell"
"umount /sdcard"
"exit"
I haven't tried this on my phone, but it should work. Please post back if you have any problems.

That will fail because /<path>/<whateverfile> isn't readable/writeable by non-root users (aka adbd). It's /dbdata or something like that, if memory serves.
For the record, booting into recovery mode and clearing all user data will NOT restore a working settings.db. I think the OP is SOL, although I'd love to learn that I'm wrong! :-(

Yeah I tried "mount /sdcard" already.... No luck, it just tells me "usage: mount [-r] [-w] [-o options] [-t type] device directory"

I forgot that you can't get root. The only thing i can tell you is to wait for the dump of the original rom whenever that comes out or take it to your ATT store and tell them it broke.

Mostly new to android, but could you create an update.zip which contains a valid dbsettings file and run it using the bootloader (hold down volume buttons and power up)? Would that then install it to the appropriate place?

If you can't recover the settings.db just take it back to the store and tell them the phone just started booting into a black screen. Leave it at that, turn it on for them to show them it does indeed do that. Then they will exchange it for you because it is so soon after the release date. (ask me how I know) :-/. Always check the db file before you copy it over.

centex99 said:
Mostly new to android, but could you create an update.zip which contains a valid dbsettings file and run it using the bootloader (hold down volume buttons and power up)? Would that then install it to the appropriate place?
Click to expand...
Click to collapse
tbae2 said:
If you can't recover the settings.db just take it back to the store and tell them the phone just started booting into a black screen. Leave it at that, turn it on for them to show them it does indeed do that. Then they will exchange it for you because it is so soon after the release date. (ask me how I know) :-/. Always check the db file before you copy it over.
Click to expand...
Click to collapse
both posts +1

If you can access the phone in adb shell, then you might be able to access the recovery console by going to your computer's command line, getting into the SDK tools folder, and typing "adb shell reboot recovery"

Trying to root but can't get ADB working

I've finally decided to try to root my G2 but can't get past the ADB setup. I downloaded the SDK, but when I open the manager and try to install platform tools it goes through the motions and then tells me nothing was installed. When I open a command prompt and type "ADB devices" it doesn't recognize anything. What am I doing wrong??
EDIT: specifically, when I try to install platform-tools it tells me it couldn't create a directory and nothing was installed.

66 people have read this and nobody has any suggestions to help?

i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....

I have a problem after rebooting my PC: <Java not found...> Reinstalling doesn't help, adding environment variables too. Any idea?

Just root using the rage/visionary method. No adb needed and very easy to do. Here is the linkhttp://forum.xda-developers.com/showthread.php?t=834228
Sent from my SilverBullet 'HTCDesireZ running CM7'

juvanni said:
i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....
Click to expand...
Click to collapse
I don't understand? I'm trying to root following the recommended wiki instructions, and I haven't been able to get adb to work so I haven't gotten past that step.

Are you running windows x64? Cause the android installer has issues detecting java on x64 systems.
When it says 'Can't find java' or whatever the error is, click back, then next again, it should find it the second time around. Well thats what happened for me anyway.
-Nipqer

If you're on froyo just use the app z4 root or universal androot
You can also use superoneclick root 2.11
Its very easy and it only take about 3 minutes
Stewie just said that!

I appreciate the help so far, but my problem is I have gingerbread and everything I've read requires froyo for root, and the only way I've read to downgrade uses ADB, so any non-ADB rooting method still won't work for me. I've followed the "ADB for dummies" thread and the other instruction thread and everything seems fine, but when I type in the first command for the downgrading it says adb isn't a recognized command. Am I in the wrong command prompt? I feel like its probably something really dumb I'm doing or not doing but for the life of me I can't figure it out.

Navigate to the folder adb is in.
Hold shift, right click in the folder (make sure nothing is selected)
select 'Open command window here' (or something along those lines)
Adb should work.
-Nipqer

OK, so I'm definitely in the right folder, I read and followed ADB for Dummies thread. Trying to follow this direction:
"Run the following command to verify the exploit has access to what it needs. (Only the first line is the command. The second line should be the result returned if all goes well.)
Code:
$ adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length"
When I type that in, should there be spaces between the "adb" and "shell"? Should there be a space after the command prompt and before "adb"? I've tried several variations of it and it keeps telling me "adb is not recognized as an internal or external operable program or batch file."

ok you need to run the command from the folder with adb.exe in it, type it as adb<space>shell<space>cat<space>/dev/msm_rotator
If you are getting an error search for adb.exe and once found try the command again from this folder,if as you say you are in the right folder then I think you will have to reinstall adb as I just ran the command in the form above and it works so if you still get an error then something has gone wrong with the install
P.S Another way to make sure that adb is working and recognises your phone is to type adb devices, if your phone is attached and recognised then it will return a number

Thank you! I had to uninstall and reinstall the package, I don't know what was wrong but it seems to be working now. Also, I knew I was probably doing something stupid, and I was. I wasn't in the platform-tools directory for my command prompt, I was in the TOOLs directory. Just so I'm clear, every command I type into the terminal should be in the Platform-tools directory, correct?
Now, assuming I can follow all the other directions with no problems, once I get to the downgrade pushing steps, I will lose all my current settings, right? It will be a fresh froyo 2.2 like it came to me originally? Other than using Appbrain to back up my current apps, how else should I make a backup?
Final question, do I need to follow the temp root directions and push the downgrade all at one time? Or can I do the temp root and come back at a later time to push the downgrade?

First problem solved then!
Yes but follow this Step 4
Now we need to update your Path variable. This lets you run adb on your PC from a command window no matter which directory you are in (which makes things a lot easier). If you don't setup your Path, then every time you want to run adb, you will either have to type the whole long pathname where you put adb, or cd to where you've put adb and run it from there (which could be inconvenient if you are transferring files to/from your phone).
On your PC, right-click on "My Computer" and select "Properties". (on Vista, click on "Change Settings"). Go to the "Advanced" tab, then select "Environment Variables". Find the "Path" variable in the list of variables that it shows (you might need to scroll), and then double-click on that entry to edit it. Add the full path of the "tools" and "platform-tools" folders of the SDK to your path. e.g. if the SDK has been installed in "c:\Program Files\android-sdk-windows", then add to your Path "c:\Program Files\android-sdk-windows\tools;c:\Program Files\android-sdk-windows\platform-tools" (Please Note - don't put any spaces between the semi-colon and pathname, otherwise it won't work !)if you want to.
Once done you can use ADB from the command prompt in ANY folder,very handy IMO.
If I was you I would set aside enough time and see it through,no point to temp rooting alone.
Get Titanium backup from the market an absolute essential app with this you can backup,upload to dropbox(Another essential app) uninstall apps and a host of other useful tools.
Read the guide first as well,good luck.

[Q] Broke Screen, Want to Backup files

Hi,
So today the front of my Nexus 4 cracked and rendered it completely dysfunctional. The worst part is that there's a screen lock, making it impossible for me to access through Android File Transfer. I was reading that you could use adb and screencast to access the phone and to unlock it, allowing for me to retrieve files. But after installing and running commands, it seemed like I couldn't find a device when I inputted the command 'adb devices'. I know, I searched it up and I think the reason is that usb debugging was not enabled (I don't remember if I did or didn't enable it at all). I've read past threads which explain how to enable it even with a cracked screen but I'm just too confused on how to do it. All this SDK and AVD stuff confuses the heck out of me (I'm fairly new to the whole Android notion) so I practically have the IQ of a 5 year old. My phone is rooted (In which it did wipe the memory so that may be why debugging could be off) and I'm currently flashing Cyanogenmod. Could someone please explain to me how do I enable debugging with a dysfunctional screen like I'm 5? Also, if there were an easier alternative to retrieving/backing up my files that would be nice knowing too because all of this stuff is currently doing my head in.
Thanks!

You can try to access adb from recovery too.
Turn off phone and start by holding VOL-DOWN and POWER together. You will boot into BOOTLOADER mode and there switch to RECOVERY MODE by VOLUME button (2 times press is this mode). If you have installed CyanogenMOD, then you have probably advanced recovery (CWM or TWRP). Now try command "adb devices".
If you haven't CWM or TWRP recovery installed, boot again into BOOTLOADER mode and flash recovery by fastboot.

xjcook said:
You can try to access adb from recovery too.
Turn off phone and start by holding VOL-DOWN and POWER together. You will boot into BOOTLOADER mode and there switch to RECOVERY MODE by VOLUME button (2 times press is this mode). If you have installed CyanogenMOD, then you have probably advanced recovery (CWM or TWRP). Now try command "adb devices".
If you haven't CWM or TWRP recovery installed, boot again into BOOTLOADER mode and flash recovery by fastboot.
Click to expand...
Click to collapse
Thanks for the quick reply,
After I hit advanced recovery and selecting my backup, which option do I press? Do I restore the boot, system, data, cache, or sd-ext?
Also typing in adb devices only lists the recovery device and I don't seem to be able to access it through Android File Transfer, what do I do with the serial number it tells me?
By the way I don't have any backups when I had no screen pattern so wouldn't recovering those areas still give get me locked out?

loolnicetry said:
Thanks for the quick reply,
After I hit advanced recovery and selecting my backup, which option do I press? Do I restore the boot, system, data, cache, or sd-ext?
Also typing in adb devices only lists the recovery device and I don't seem to be able to access it through Android File Transfer, what do I do with the serial number it tells me?
By the way I don't have any backups when I had no screen pattern so wouldn't recovering those areas still give get me locked out?
Click to expand...
Click to collapse
Android File Transfer is not working in recovery mode, but you can pull required files by "adb pull /sdcard/some-file-or-folder/ /to/some/path/on/your-system/". Of course you can pull whole /sdcard/. You can try also adb backup (I didn't try it yet). From recovery you can also make nandroid backup of the system and transfer to computer by adb pull.
In recovery mode you have access to full system (maybe you must mount some partitions), that means you can use magic command "adb shell", to get shell (in shell you can use "ls" for list files, "cd" for change directory) and do what you want. To remove screen lock try some guide from XDA, I've found for example [GUIDE][HOW-TO]Crack android pattern lock! or [EASIEST]Crack Android Pattern/Pin/Password Lockscreen without root.
I hope this will help you.

xjcook said:
Android File Transfer is not working in recovery mode, but you can pull required files by "adb pull /sdcard/some-file-or-folder/ /to/some/path/on/your-system/". Of course you can pull whole /sdcard/. You can try also adb backup (I didn't try it yet). From recovery you can also make nandroid backup of the system and transfer to computer by adb pull.
In recovery mode you have access to full system (maybe you must mount some partitions), that means you can use magic command "adb shell", to get shell (in shell you can use "ls" for list files, "cd" for change directory) and do what you want. To remove screen lock try some guide from XDA, I've found for example [GUIDE][HOW-TO]Crack android pattern lock! or [EASIEST]Crack Android Pattern/Pin/Password Lockscreen without root.
I hope this will help you.
Click to expand...
Click to collapse
I CANNOT THANK YOU ENOUGH! You were easy to understand and got straight to the point which was perfect! On a side note, do you know if there's a way I can extract and save my sms messages and read them on my computer? I know I can take out the .db file but it's complicated to open on a Mac and it's quite an effort. (Considering my phone still has a lock on it)

loolnicetry said:
I CANNOT THANK YOU ENOUGH! You were easy to understand and got straight to the point which was perfect! On a side note, do you know if there's a way I can extract and save my sms messages and read them on my computer? I know I can take out the .db file but it's complicated to open on a Mac and it's quite an effort. (Considering my phone still has a lock on it)
Click to expand...
Click to collapse
I'm really happy that I helped you!
Android is storing messages, contacts in SQLite database, there is not another way to grab these files from recovery. But it's not complicated to extract these files. Download for Mac OS X sqlite-shell-osx-x86-XXX.zip from SQLite Download Page and extract it somewhere.
Then pull messages by
Code:
cd /path/where/is/extracted-sqlite
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db .
Finally you can list your messages by
Code:
./sqlite3 mmssms.db 'select address,body from sms'
If last command is not working try make it executable and repeat previous step
Code:
chmod +x sqlite3

xjcook said:
I'm really happy that I helped you!
Android is storing messages, contacts in SQLite database, there is not another way to grab these files from recovery. But it's not complicated to extract these files. Download for Mac OS X sqlite-shell-osx-x86-XXX.zip from and extract it somewhere.
Then pull messages by
Code:
cd /path/where/is/extracted-sqlite
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db .
Finally you can list your messages by
Code:
./sqlite3 mmssms.db 'select address,body from sms'
If last command is not working try make it executable and repeat previous step
Code:
chmod +x sqlite3
Click to expand...
Click to collapse
For the pulling of the .db file, it says the remote object does not exist, what should I do?

loolnicetry said:
For the pulling of the .db file, it says the remote object does not exist, what should I do?
Click to expand...
Click to collapse
Hmm that is strange, maybe this will help you (especially check first answer): http://stackoverflow.com/questions/12266374/backup-full-sms-mms-contents-via-adb
Sent from my Nexus 4 using Tapatalk

xjcook said:
Hmm that is strange, maybe this will help you (especially check first answer):
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
When I try to enter the $mkdir command it says it's not found. Am I meant to include the $ in the command?

xjcook said:
Hmm that is strange, maybe this will help you (especially check first answer): http://stackoverflow.com/questions/12266374/backup-full-sms-mms-contents-via-adb
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I FIXED IT MYSELF! I'm feeling a bit smart haha, it turns out my system and data wasn't mounted and all I had to do was mount it through cwm. Thanks a lot friend you were a great help, I'd be panicking a substantial amount without you!

How to root 4.4.2 Att and Vzn guide (tethered)

Before we start this you will need a few files, you need jcases pie root, the android sdk and the drivers installed for your device.
I've included his package from his thread.
Now I installed SuperSU first before even starting the root process because root isn't needed to just instal the app itself, it will just close once it's open.
Make sure you enable USB debugging and unknown sources before continuing. Extract the two files pie.jar and root.sh to the folder "platform-tools"
This folder should be on your desktop, at least thats where I put adt-bundle folder at. Once placed in to the folder hold shift and right and select "open command window here" and your command prompt should pop up. Connect your device and make sure you're powered on. Type "adb devices" and you should get an access message on your phone just give your phone the authorization. Type "adb devices" once more to make sure your device is listed.
Now to Semi-root the phone
These are to be entered one by one, just copy and paste them one by one.
adb push pie.jar /data/local/atvc
adb push root.sh /data/local/atvc
adb shell chmod 755 /data/local/atvc/root.sh
adb shell /data/local/atvc/root.sh
Your phone itself should disconnect from your computer (at least thats what mine did) and reconnect.
So far I haven't figured out how to work exposed but busy box and adblock plus and other simple root apps work just fine.
Remember this is a tethered root so if you shut off your phone you will have to redo the process every single time you do a hard reboot. Soft reboots work without problems, so unless your battery dies you really have no reason to restart your phone.

I believe @jcase is the developer of the root method and he has instructions for his method on his thread. You are stealing and violating XDA policies! Please report to any mod
MOTO X

I imagine he thought he was being helpful...but yeah, OP should take the link down, and instead, post a link to @jcase 's thread....unless he has given you explicit permission to re-post his file.

As far as using Xposed, OP, you need to download the latest framework from here.
Next, open the app and select Framework. To install, click the very first option which is "Install/Update". (NOTE: Classical installation mode will not work with this type of root!)
After installing the framework it will prompt you for a reboot. Select cancel and then on the same screen as the Install/Update button select the second to last option labeled "Soft Reboot". This is the only kind of reboot you can do to preserve root!

Please delete my binaries, as i update them from time to time, and the ones here would not be updated.
http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623 is the supported guide, with up to date binaries
super65man said:
Before we start this you will need a few files, you need jcases pie root, the android sdk and the drivers installed for your device.
I've included his package from his thread.
Now I installed SuperSU first before even starting the root process because root isn't needed to just instal the app itself, it will just close once it's open.
Make sure you enable USB debugging and unknown sources before continuing. Extract the two files pie.jar and root.sh to the folder "platform-tools"
This folder should be on your desktop, at least thats where I put adt-bundle folder at. Once placed in to the folder hold shift and right and select "open command window here" and your command prompt should pop up. Connect your device and make sure you're powered on. Type "adb devices" and you should get an access message on your phone just give your phone the authorization. Type "adb devices" once more to make sure your device is listed.
Now to Semi-root the phone
These are to be entered one by one, just copy and paste them one by one.
adb push pie.jar /data/local/atvc
adb push root.sh /data/local/atvc
adb shell chmod 755 /data/local/atvc/root.sh
adb shell /data/local/atvc/root.sh
Your phone itself should disconnect from your computer (at least thats what mine did) and reconnect.
So far I haven't figured out how to work exposed but busy box and adblock plus and other simple root apps work just fine.
Remember this is a tethered root so if you shut off your phone you will have to redo the process every single time you do a hard reboot. Soft reboots work without problems, so unless your battery dies you really have no reason to restart your phone.
Click to expand...
Click to collapse

jcase said:
Please delete my binaries, as i update them from time to time, and the ones here would not be updated.
http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623 is the supported guide, with up to date binaries
Click to expand...
Click to collapse
I try to make a simple guide for people who don't want to dig and they get mad..... If I wanted to take the fame of you would I even have credited you at all? lol Man I had to go to a complete different site in order to learn because I was to lazy to dig through yours. My bad if it upset you man, as for everyone else I could care less, you can't please everyone.

super65man said:
I try to make a simple guide for people who don't want to dig and they get mad..... If I wanted to take the fame of you would I even have credited you at all? lol Man I had to go to a complete different site in order to learn because I was to lazy to dig through yours. My bad if it upset you man, as for everyone else I could care less, you can't please everyone.
Click to expand...
Click to collapse
I did not accuse you of anything, I simply asked that you remove the binary so that I could have a centralized point of distribution, to help prevent distribution of older binaries.
IE if you had took the first release, everyone who used your guide would be back here complaining, and blaming me since I can't update this guide.

Thread closed.
Please use the developer supported thread below.
jcase said:
Please delete my binaries, as i update them from time to time, and the ones here would not be updated.
http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623 is the supported guide, with up to date binaries
Click to expand...
Click to collapse