since the phone maintains the 2 pushed files on the phone after reboot, is it possible to make an app that can be run from the phone itself to run the two adb commands of Pie root that do the rooting?
Well Google now doesn't work worth an iPhone. .I've spoken those last two lines ADB shell commands out loud for the past 15 minutes and I don't get root
You cannot do it from the phone. That method lacks sufficient permissions
Sent from my XT1058 using XDA Free mobile app
Neighbor808 said:
You cannot do it from the phone. That method lacks sufficient permissions
Sent from my XT1058 using XDA Free mobile app
Click to expand...
Click to collapse
I'm starting to believe you....
doitinthedirt said:
I'm starting to believe you....
Click to expand...
Click to collapse
We KNOW that the commands MUST be run from ADB (and not from a SHELL, as your screenshot shows you have tried).....
But before we discount the idea completely, perhaps an experienced DEV could commend on this possibility:
Guys, have a look at this thread regarding running adb commands (through adb wireless) from another android device:
http://androidforums.com/android-applications/783226-run-adb-shell-another-android-phone.html
See the last 2 posts. This user successfully connected one android device to another via WiFi and was able to run adb commands.
Now first, I know that "ADB Wireless" requires root access, however there are 2 non-root variants aptly called "ADB Wireless (No Root)" -- see the play store.
Having read up on those specific apps, I've found that they require you to first connect the USB cable to the PC, and run an adb command to activate ADB over WiFi. What I'm not sure about is if you must do this each time the phone is rebooted. If not, then we have the possibility to actually run adb commands through TCP/IP possibly from the phone itself.
Consider the possibility of using the loop-back address...for instance: adb connect 127.0.0.1 in order to achieve a connection to the device itself.
If the adb command to activate adbwireless on non-rooted devices must be run each time the phone is rebooted, then this solution is probably going to go nowhere....but its worth checking out nonetheless....
We would definitely need a working adb binary for the Moto X in order for this to be possible at all.
See this link: http://forums.androidcentral.com/be...ol-native-adb-fastboot-your-phone-tablet.html
This user has repacked the adb and fastboot binaries (called "kadb" and "kfastboot") so they can be run on an android device itself. The intention is to use USB-OTG to connect another android device and run adb commands on the connected device.
^^ This definitely shows that it is possible to at least run adb commands from another android device connected via USB-OTG.
I know that many users are looking for a way to use PIE without having to connect to the PC after each reboot, hence the reason the "TowelRoot" app has had so much interest...
Unfortunately, TowelRoot has inherent limitations, because of the SU context (Non--Trusted App) as I understand. Several of us (myself included) have attempted to reach out to the developer for comment as to why this SU context is being used, and whether or not it can be modified to use the "Kernel" SU context that jcase is using with PIE, but none of us have received a response....
Do any experienced DEVS care to comment on the possibility of using the methods I have described, or something similar?
EDIT: Also, @doitinthedirt : have you tried to unlock your bootloader via the middleman? Or do you have a 2013 variant that he can not access the code for? The BL unlock solution is far superior to any of these temp-root methods, and it is permanent. (disregard if you already know this and are unable to obtain a code...)
I was running those commands from the same phone.. it was on a wifi network only to access internet. i used an app https://play.google.com/store/apps/details?id=com.spartacusrex.spartacuside
Only had about 10 minutes to mess around with it.. going to experiment more tonight.. and another app https://play.google.com/store/apps/details?id=jackpal.androidterm
The wireless from my nexus 7 was going to be my next try if i I couldnt get anywhere running from phone itself. And no I have not tried the middleman.. phone is july 3 2014 make so going to send a paypal to him and see if i get a code to unlock.
Getting nowhere..
doitinthedirt said:
Getting nowhere..
Click to expand...
Click to collapse
I appreciate your enthusiasm, but you are still trying to run the commands from a terminal SHELL. We -know- that this won't work. I'm not sure you understand what I was trying to express in my earlier post. I will attempt to experiment with the kadb binary, but you shouldn't continue trying to do this from ANY terminal emulator - it simply won't work, as @Neighbor808 has correctly advised...
Both of the apps you have linked ARE terminal emulators (hence running from SHELL).
If an experienced DEV could read my post, they might be able to comment further.
EDIT: I believe this is a lost cause:
From the dev who compiled the kadb binary: "Note : You do not need to be rooted, you do however need a custom recovery or temp boot a custom recovery."
This means that it should -absolutely- work for those of us who are unlocked, but definitely not temp-rooted.
Additionally, the AdbWireless method seems to fall short as well. It will probably work, but only if you connect to your PC first to run an ADB command to activate adb over WiFi, which defeats the whole idea of not having to use a PC.
The only method that IS viable for those of you using PIE, is the USB-OTG method. If you have ANOTHER android device (NOT your X) that:
1. has custom recovery
and
2. supports USB-OTG
Then you could purchase a USB-OTG cable, install the flashable zip containing the kadb and kfastboot binaries from the post I linked earlier, and run the ADB commands FROM the 2nd device.
This may be an option for you. Assuming you have installed custom recovery on your Nexus 7 (it definitely supports USB-OTG), you should be able to install the flashable zip, and run the commands from your Nexus 7 (just like you would from a PC, except using the command "kadb" instead of "adb".....i.e.:
kadb shell chmod 755 /data/local/atvc/root.sh
kadb shell /data/local/atvc/root.sh
I see no reason that this would not work....all the other methods I suggested have been eliminated as possibilities during my research/testing.
I don't, however, see how this is any better than simply connecting to your pc and running the adb commands the traditional way.
Good Luck
---------- Post added at 02:48 AM ---------- Previous post was at 02:19 AM ----------
doitinthedirt said:
Well Google now doesn't work worth an iPhone. .I've spoken those last two lines ADB shell commands out loud for the past 15 minutes and I don't get root
Click to expand...
Click to collapse
Oh wow! I missed this post. You are joking, right? You've --spoken-- the commands to Google Now?!?! LMFAO + ROFL + LOL....I just can't find a way to express just how humorous this post is
Good One :silly:
Use towel root if your trying to root from your phone.
Sent from my XT1058 using XDA Premium 4 mobile app
Thanks Sir, towelroot does not root my moto X
[email protected] said:
Use towel root if your trying to root from your phone.
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This:
samwathegreat said:
I know that many users are looking for a way to use PIE without having to connect to the PC after each reboot, hence the reason the "TowelRoot" app has had so much interest...
Unfortunately, TowelRoot has inherent limitations, because of the SU context (Non--Trusted App) as I understand. Several of us (myself included) have attempted to reach out to the developer for comment as to why this SU context is being used, and whether or not it can be modified to use the "Kernel" SU context that jcase is using with PIE, but none of us have received a response....
Click to expand...
Click to collapse
samwathegreat said:
This:
Click to expand...
Click to collapse
Oh yeah? What about this?
Sent from my XT1058 using XDA Premium 4 mobile app
[email protected] said:
Oh yeah? What about this?
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Um... Pointing out the inherent limitations of the towel root and why it doesn't work for many and causes issues for others. I'm going to assume that because you are using the XDA app, you didn't see the quote attached to my post, but if you view it in a browser you should understand the point I was making...
I'm glad that towel root is actually working for you. Are you experiencing the random reboots?
[email protected] said:
Use towel root if your trying to root from your phone.
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
towel root will not work on the motoX
it doesn't work for Him I get that same screen saying you should have root but if he would bother checking with file explorer root access he will find out he doesn't have root
yamaha83 said:
towel root will not work on the motoX
Click to expand...
Click to collapse
Not entirely accurate. Some have managed to use after rooting with PIE, but it does cause issues for many and (once again) has inherent limitations due to the SU context being used.
---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------
doitinthedirt said:
it doesn't work for Him I get that same screen saying you should have root but if he would bother checking with file explorer root access he will find out he doesn't have root
Click to expand...
Click to collapse
I don't think hovax is foolish enough to mistakenly believe he has root when he does not lol. He has obviously managed to get it to work for him, as have many others. I am curious if he is experiencing the problems that many others are with towel root, however.
a simple screenshot showing root access in system folder like this one from my other moto x running ios 4.4 rooted with slap, that will convince me
doitinthedirt said:
is it possible to make an app that can be run from the phone itself to run the two adb commands of Pie root that do the rooting?
Click to expand...
Click to collapse
If it was possible, I would have thought JCASE would have released it that way, instead of having to do the process while connected to the PC.
doitinthedirt said:
a simple screenshot showing root access in system folder like this one from my other moto x running ios 4.4 rooted with slap, that will convince me
Click to expand...
Click to collapse
You have to realize that many users including hovax are much more experienced than you seem to be. All the proof you should need is located in the towel root discussion thread.
Remember: you were trying to -speak- adb commands using Google now in order to root your phone...
Some of your comments are likely being taken as insults...
EDIT: I won't be posting any further in this thread. This idea is going nowhere and (obviously) does not belong in the original android development sub-forum.
EDIT2: Mods moved the thread to the appropriate location, so I will continue posting here.
I dont believe anyone has ever rooted an x with tr. all you get is the page pictured in the post above by the guy saying tr says you should have root... ive got it on two moto xs a broken one and a replacement one both on 4.4.2 and fx explorer and root checker confirm no root. one is 15 april 2014 build and the other is 03 july 2014 build. both fail under tr.
Related
Okay everybody, first off let me apologize, as I am sure that this is asked quite a bit. However, I am not very savvy with using terminal and such to enable sideloading on my Captivate, and I cannot get any of the methods to work properly.
I started off with the Unleash the Beast root on my phone, then for some reason I thought that froyo was out as an official update, because when I went to check for an update, it would download a package, reboot my phone, then tell me that the update could not be applied. So, thinking that it was due to the root, I had to use Odin to get Unleash the Beast off the phone; however, whatever "update" the phone was attempting to apply still would not work. So I reverted back to root the phone. I have used the One Click Root to program, I have installed BusyBox, and allowed SuperUser access. I am trying to enable sideloading so that I can download the Market Access app, but I am having troubles getting it to work. I have a Mac, and I have used many methods to try and enable it, but no matter what I do it will not work.
Again, I apologize for my ignorance. I have searched all over, and I still can't get this stuff to work. If anybody could provide any assistance, it would be greatly appreciated.
Thanks
goosefraba91 said:
Okay everybody, first off let me apologize, as I am sure that this is asked quite a bit. However, I am not very savvy with using terminal and such to enable sideloading on my Captivate, and I cannot get any of the methods to work properly.
I started off with the Unleash the Beast root on my phone, then for some reason I thought that froyo was out as an official update, because when I went to check for an update, it would download a package, reboot my phone, then tell me that the update could not be applied. So, thinking that it was due to the root, I had to use Odin to get Unleash the Beast off the phone; however, whatever "update" the phone was attempting to apply still would not work. So I reverted back to root the phone. I have used the One Click Root to program, I have installed BusyBox, and allowed SuperUser access. I am trying to enable sideloading so that I can download the Market Access app, but I am having troubles getting it to work. I have a Mac, and I have used many methods to try and enable it, but no matter what I do it will not work.
Again, I apologize for my ignorance. I have searched all over, and I still can't get this stuff to work. If anybody could provide any assistance, it would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
Could you provide a little more information about your phone? Is it stock JF6 with just root? If not provide firmware information and anything else that might be useful
P.S. Questions belong in the Q&A section
I'm not really sure what JF6 is haha...After I used Odin and set it back to stock conditions, the only thing I did was use the One Click Root.
As far as sideloading goes, the One Click De-Cripple method on page 2 of the general forum worked for me. If you want to know what version your phone is, go to the about phone section under your settings menu. If you need or want to upgrade to JH7, which was the last OTA update from ATT, do a search and there are a few options out there for that.
Well unfortunately I cannot use OCD on Mac..I tried to do the command prompts, but the su is asking for a password, which is odd because the way I understand it, it shouldn't be doing that
goosefraba91 said:
Well unfortunately I cannot use OCD on Mac..I tried to do the command prompts, but the su is asking for a password, which is odd because the way I understand it, it shouldn't be doing that
Click to expand...
Click to collapse
You did type adb shell first right? Then you should get a "$" where you then type su. It then echoes back su and you should see a "#".
From what you just said, it sounds like you're attempting to get root access on your mac through terminal, which in that case should be your password.
miztaken1312 said:
You did type adb shell first right? Then you should get a "$" where you then type su. It then echoes back su and you should see a "#".
From what you just said, it sounds like you're attempting to get root access on your mac through terminal, which in that case should be your password.
Click to expand...
Click to collapse
Ok, I got that to work. Now I'm just having trouble entering the code for mac. Like I said, I'm not very savvy with this stuff, so pardon my ignorance, haha.
I'm using the method in the "How to: Remove (Almost) Every Trace of AT&T" thread. (I would post a link, but since I'm a new user, it won't let me)
Is there anything different that I need to put into terminal other than the "./adb"?
I tried to paste the link to this thread but being a new member I am not allowed to post a link because of spam issues. Do a google search for "how to enable non market apps on captivate consolidated" and this will be the first xda thread that comes up.
This thread gives several methods for permanent enabling of sideloading. Being a noob, all of them were a little intimidating to me except for METHOD 3. You don't need a computer and you can do it all on your phone with Root Explorer, SQ Lite, and Terminal Emulator which are all available on the market. The step by step is pretty good and I have done it twice with no issues.
Roof King said:
I tried to paste the link to this thread but being a new member I am not allowed to post a link because of spam issues. Do a google search for "how to enable non market apps on captivate consolidated" and this will be the first xda thread that comes up.
This thread gives several methods for permanent enabling of sideloading. Being a noob, all of them were a little intimidating to me except for METHOD 3. You don't need a computer and you can do it all on your phone with Root Explorer, SQ Lite, and Terminal Emulator which are all available on the market. The step by step is pretty good and I have done it twice with no issues.
Click to expand...
Click to collapse
That method worked great. Thank you!
No prob!
Happy Modding!
Glad you got it working. For the record, the next time you guys wanna post links, just replace the http in the front with hxxp. Most people will fix it when they copy/paste it
Sent from my Captivate
We've heard that you can root the LG Optimus 2X with Z4Root. Is it permanent or temporary?
No supporting evidence just yet, but rooting this phone should be a piece of cake.
I used Z4root on two samples of the 2X, no issues what so ever. These were however pre-release roms, but I couldn't imagine any differences from the final release.
And yes, it's permanent. I had some app testing to do and tried Z4root just for fun and it worked like a charm.
//Dave
Cool. I have already ordered one. Is the root reversible? E.g. can one root an unroot as if nothing happened?
I'm holding the 2x in my hand right now and unrooted it. (didn't try adb on it for confirmation but tried clocksync, which refused access (superuser has disappeared as well). Rerooting at the moment.
Once again this is a pre relase rom so I can't guarantee that the final ROM will have the same functionality.
//Dave
dave79 said:
I'm holding the 2x in my hand right now and unrooted it. (didn't try adb on it for confirmation but tried clocksync, which refused access (superuser has disappeared as well). Rerooting at the moment.
Once again this is a pre relase rom so I can't guarantee that the final ROM will have the same functionality.
//Dave
Click to expand...
Click to collapse
Thanks. Can't wait to get my hands on one.
Good news dave. My understanding is that the main issues with the Optimus 2x so far have been regarding the massive amount of bloat apps as well as some instability in day to day operations (browser and messaging seems to crash from time to time).
Are you experiencing these? Would you be able to remove some of the bloat apps and see if it breaks anything in the LG rom?
UHOH!
Bantu85 said:
Good news dave. My understanding is that the main issues with the Optimus 2x so far have been regarding the massive amount of bloat apps as well as some instability in day to day operations (browser and messaging seems to crash from time to time).
Are you experiencing these? Would you be able to remove some of the bloat apps and see if it breaks anything in the LG rom?
Click to expand...
Click to collapse
I'll take a look at it, I've got an early version of the 2x which I'll try to push the new system dump to. I've rooted it and while using adb shell it looks like I've bricked it! uhoh!
Bricking a pre-production version of the best phone on the planet isn't quite what I wanted to do! I'm stuck in a boot loop and I manage to get a limited connection when booting it into the bootloader. However, probably because of pre-production status, the bootloader will let me go up and down using the volume keys, but it won't let me select any of the options!
When in the bootloader, I do have some type of recognized connection via the PC. DDMS recognizes the phone, ADB doesn't let me access it.
I'll chill on doing anything to the "good" phone for now (hope you understand)... but if I get the bricked one started, I'm back in the game .
Feel free giving me tips or trix to get it up and running.
from a somewhat uneasy Dave
dave79 said:
Feel free giving me tips or trix to get it up and running.
from a somewhat uneasy Dave
Click to expand...
Click to collapse
Have you tried using the power button or one of the other buttons to select an option in the bootmenu?
GIR said:
Have you tried using the power button or one of the other buttons to select an option in the bootmenu?
Click to expand...
Click to collapse
I sure did, thanx anyways. I've used every button available incl, the touch screen corners, tapping on the selection itself.
//Dave
Z4root doesn't work with my sample
No way to root
pocketAM said:
Z4root doesn't work with my sample
No way to root
Click to expand...
Click to collapse
Do you have a preproduction model like Dave or a sales sample?
On mine Z4root simply quits...after saying "Aquiring root shell" ... will try an other version, hope that will work...
Do you have a temporary root? After z4root locks? I tried with a later rom and got the same issue. However after accessing it with ADB shell it clearly has root "#" is showing and I have permissions I otherwise wouldn't have. However it seems like the root is temporary. Weird thing... I'll continue hunting for alternative solutions.
BTW, my other X2 may rest in peace. After a friend helping me out we managed to get the phone into fastboot, the kernel must have been intact, the system was completely wiped. Pushed the system through ADB and rebooted. Now we can't get it into fastboot at all... RIP ;(
//Dave
dave79 said:
Do you have a temporary root? After z4root locks? I tried with a later rom and got the same issue. However after accessing it with ADB shell it clearly has root "#" is showing and I have permissions I otherwise wouldn't have. However it seems like the root is temporary. Weird thing... I'll continue hunting for alternative solutions.
BTW, my other X2 may rest in peace. After a friend helping me out we managed to get the phone into fastboot, the kernel must have been intact, the system was completely wiped. Pushed the system through ADB and rebooted. Now we can't get it into fastboot at all... RIP ;(
//Dave
Click to expand...
Click to collapse
Wow, sorry to hear your loss...sad story.
Anyway, I heard that it is possible to root 2.2.1 devices with Super One Click, but I can't get my Optimus 2x connected to adb, somehow Windows 7 doesn't wanna install the downloaded Google USB Drivers...
The reason Z4root doesn't work on firmwares 2.2< is that the exploit it uses to gain root rights has been fixed in those newer versions
GIR said:
Do you have a preproduction model like Dave or a sales sample?
Click to expand...
Click to collapse
sales sample x press
After update OTA to version LS670ZVC, machine is unable to be rooted at this time. I am sure someone is working on it.
I returned this previously rooted phone Saturday feb 12 for replacement due to HW fault. Got new phone home and saw the phone was auto-updating to the LS670ZVC version. Which kept me from using Zroot as I did in the past. Drat! Tried many tricks found on other android forums to try and root.
The skinny of it is, if this update was applied OTA, we are SOL for now. If you updated using LG software via computer, you can root it still. If you haven't updated from version 9, don't do it until an exploit is released.
I have another thread going on this same issue. I have tried using superoneclick. Even though everything looked ok it didn't make a difference. Did a root checker it said busybox was ok and I know that SU is ok. Just looks like they "fixed" the exploit for now...
Sent from my LS670 using XDA App
domi007 said:
Wow, sorry to hear your loss...sad story.
Anyway, I heard that it is possible to root 2.2.1 devices with Super One Click, but I can't get my Optimus 2x connected to adb, somehow Windows 7 doesn't wanna install the downloaded Google USB Drivers...
The reason Z4root doesn't work on firmwares 2.2< is that the exploit it uses to gain root rights has been fixed in those newer versions
Click to expand...
Click to collapse
Mmmm, sad about the old one, however I got my second device so I'll unroot my it and then try the SuperOneClick option.. I'll let you know. Once again this is a sample but the rom is dated from 2010-12-14 so it must be quite close to production ROMs.
//Dave
Post removed by User.
So from the beginning I updated from notification on phone from 4.0.4 to 4.1.2. Then bricked after trying to gain root acess. Finally able to flash jb 98.72.22. Tried for days to find a root that worked. Couldn't get motochopper to gain root. Tried god knows how many others. Finally got virtual box, imported Root_Bionic_JB.ova and still wouldn't work. Keep coming across su binary issues. The closest i got was with the virtual box installing superuser. But when I trying to update the binary says unable and to send a log report. What am i doing wrong? is it a step im missing when unzipping to desktop? everything goes smooth until cmd gets to rooting, then says failed. cleaning. press enter to reboot and close. Im about to lose my mind! Please some assistance. I sick of failing every attempt from every suggest forum (quietly sobbing )
You need to go back to what has been proven to work. Moto chopper 2. Not to be insulting BUT I know from experience, just BC you can't get something to work the first couple of times you try it doesn't mean it does not work. Period. Now, where did you get hung up on the Ubuntu exploit? List all that you did.
Sent from my XT875 using xda premium
linux minimal screen shot, and unbuntu hang up
DanRyan85 said:
You need to go back to what has been proven to work. Moto chopper 2. Not to be insulting BUT I know from experience, just BC you can't get something to work the first couple of times you try it doesn't mean it does not work. Period. Now, where did you get hung up on the Ubuntu exploit? List all that you did.
Sent from my XT875 using xda premium
Click to expand...
Click to collapse
Well, not to be insulting, but it was my understanding that moto chopper would only work if temp rooted or had gained root acess previously? I may be wrong. Anyways, the prob. with unbuntu is thing i guess froze (but still ran) after patiently running it like six hours. Last screen at was installing-reinstalling previous "somethings" but I figured need a system clean and would try again. gotta be easier way. so here is my linux minimal screenshot attempt. running root bionic jb ovf file. noticed where it starting going wrong is
chmod: pwn: operation not permitted.
rooting phone...
phone may appear to.......
/system/bin/sh: /storage/rfs0/pwn: not found <-------Right here i noticed the file path on the phone and it's ---> storage/rfs1 Would that have something to do w/ it?
nothing ever vibrates and reboots in flash. got bad flash or something?
MotoChopper works on non TI (OMAP) CPus that are in Motoroal devices.
Coincidentally, it also works on ASUS Tranformer Infinity (and the Prime as well, IIRC).
It does not work on the BIONIC.
The method that works on rooting the JB build on the BIONIC is one that is based upon the older RAZR method - see http://www.droidrzr.com/index.php/topic/16518-root-motoshare-2-old-bug-new-exploit/
Bionic and JB OVA flash superuser binary outdated
Naughtybutbritt said:
So from the beginning I updated from notification on phone from 4.0.4 to 4.1.2. Then bricked after trying to gain root acess. Finally able to flash jb 98.72.22. Tried for days to find a root that worked. Couldn't get motochopper to gain root. Tried god knows how many others. Finally got virtual box, imported Root_Bionic_JB.ova and still wouldn't work. Keep coming across su binary issues. The closest i got was with the virtual box installing superuser. But when I trying to update the binary says unable and to send a log report. What am i doing wrong? is it a step im missing when unzipping to desktop? everything goes smooth until cmd gets to rooting, then says failed. cleaning. press enter to reboot and close. Im about to lose my mind! Please some assistance. I sick of failing every attempt from every suggest forum (quietly sobbing )
Click to expand...
Click to collapse
I am having same issue. Using Marty OVA in virtual box. works great, no issues w/ samba or USB. Root is successfully run. however.
root checker indicated that I am not rooted and as mentioned above, superuser needs to update the binaries.
" the Superuser binary (su) must be updated
please choose an installation method
recovery mode installation is recommended for HTC devices.
Cancel <> Recovery Install<> Install
hit install
there was an error installing superuser. Please send a log of the error to the developer.
<ok>
wonder if I could replace the superuser.adk file in the /home/guest/share directory with a newer adk file?
could not get post on droidrzr.com on a thread there. ( link not permitted by Noobs )
Marty45714 informed us He posted this here as well. can anyone answer this?
T
To Naughty: Sorry about the mix up that was what I meant to say Moto share 2 NOT Motochopper. I had all the same problems as you after some number of tries with motoshare2 I was in business.
To martin: have you already tried the motoshare 2 on Ubuntu?
Sent from my XT875 using xda premium
toddmartin- you're gonna love me...i gotcha
toddmartin said:
I am having same issue. Using Marty OVA in virtual box. works great, no issues w/ samba or USB. Root is successfully run. however.
root checker indicated that I am not rooted and as mentioned above, superuser needs to update the binaries.
" the Superuser binary (su) must be updated
please choose an installation method
recovery mode installation is recommended for HTC devices.
Cancel <> Recovery Install<> Install
hit install
there was an error installing superuser. Please send a log of the error to the developer.
<ok>
wonder if I could replace the superuser.adk file in the /home/guest/share directory with a newer adk file?
could not get post on droidrzr.com on a thread there. ( link not permitted by Noobs )
Marty45714 informed us He posted this here as well. can anyone answer this?
T
Click to expand...
Click to collapse
Ok so using virtual box the ova Root_Bionic_JB_20130501-4 the fourth ubdate of the orginal release. Now i suggest erasing all superuser apps installed your self and anything to do with them. When it's done right, it will appear on it's own and work flawlessly. No uncertianties about it. Then i've posted a screen shot of the commands with notes to help understand easiest. The instant the command to press hardware key or power/or each volume itself is the instant you want to press it. Now the reboot is instantious kinda itself and gotta be noticing phone unless have ungodly long boot up let me know if the screen shot helped what you were asking.
I have a Verizon Moto X Developer Edition. I upgraded to 4.4 but have since reverted to 4.2.2. However, as soon as i turn my phone on MotorolaOTA starts downloading 4.4 again. I need root so that Titanium Backup can freeze the OTA and keep me where i want to be in 4.2.2.
For the life of me I can't figure out how to root this effing device. I started trying to figure out RockMyMoto but could never get the IP address of my phone. adb devices shows my phone but adb shell getprop dhcp.wlan0.ipaddress returns nothing. Anyway, after searching around I found that TWRP might be a better/easier option for me given I have a Dev Edition phone. I think the bootloader needs to be unlocked before i can do this but all the threads I'm finding are referencing 4.4 and TWRP not 4.2.2.
Would someone please tell me what my best option is to gain root and could you share the thread link to instructions?
Why would adb not return an ip address?
thanks in advance for the help. i'm obviously not a tech genius just need a little hand holding to make sure what i'm doing to my phone is the "right" thing to do lest i brick it.
thanks.
texaslegend said:
I have a Verizon Moto X Developer Edition. I upgraded to 4.4 but have since reverted to 4.2.2. However, as soon as i turn my phone on MotorolaOTA starts downloading 4.4 again. I need root so that Titanium Backup can freeze the OTA and keep me where i want to be in 4.2.2.
For the life of me I can't figure out how to root this effing device. I started trying to figure out RockMyMoto but could never get the IP address of my phone. adb devices shows my phone but adb shell getprop dhcp.wlan0.ipaddress returns nothing. Anyway, after searching around I found that TWRP might be a better/easier option for me given I have a Dev Edition phone. I think the bootloader needs to be unlocked before i can do this but all the threads I'm finding are referencing 4.4 and TWRP not 4.2.2.
Would someone please tell me what my best option is to gain root and could you share the thread link to instructions?
Why would adb not return an ip address?
thanks in advance for the help. i'm obviously not a tech genius just need a little hand holding to make sure what i'm doing to my phone is the "right" thing to do lest i brick it.
thanks.
Click to expand...
Click to collapse
Unlock the bootloader
https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth
and then flash twrp
http://forum.xda-developers.com/showthread.php?t=2534850
and here is a noob proof guide to rockmymoto
http://forum.xda-developers.com/showthread.php?t=2509676
and as for your ip address you phone and computer must be on the same network. so your phone must be connected to you home wifi in order to get you IP
Unlocking the bootloader working
for me
---------- Post added at 11:59 AM ---------- Previous post was at 11:55 AM ----------
Unlocking the bootloader working for me
yghrv said:
Unlock the bootloader
https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth
and then flash twrp
http://forum.xda-developers.com/showthread.php?t=2534850
Click to expand...
Click to collapse
This is what you want to do with a DE. It's the easiest way to get root, period. TWRP will prompt you when you exit to install SU, you say yes, update it in the play store and you're done.
Why do so many people buy the dev edition yet have no clue what to do with it?
thanks
nhizzat said:
Why do so many people buy the dev edition yet have no clue what to do with it?
Click to expand...
Click to collapse
because at the time i needed a phone it was the only moto x available from VZN with 32GB of storage.
thanks to everyone else for the help. i appreciate the help!
nhizzat said:
Why do so many people buy the dev edition yet have no clue what to do with it?
Click to expand...
Click to collapse
I find it preferable to those who don't buy the DE and then ask when someone is going to unlock the bootloader.
Honestly, unless you've had a nexus device, you're probably used to having to jump through some hoops to get a phone unlocked and rooted. Combine that with most of the information on the forum being about rooting the locked version, I can see how it can be confusing.
i guess i'm just a raging idiot.
i got my unlock code from moto but i can't figure out step 5 of https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-c ....change the directory? i changed to the folder where the tools are but $ fastboot oem unlock UNIQUE_KEY (+my key) doesn't do anything i get some sytax telling me i'm stupid. i tried doing this with minimal adb and fastboot app and got an "okay" but my device didn't unlock.
driving me crazy. i've rooted razr m, inc2 and haven't had this many problems and this is suppose to be easier? lol
even once i get the damn thing unlocked i fear getting the twrp img to the device...i'm sure that will be a joy too.
texaslegend said:
i guess i'm just a raging idiot.
i got my unlock code from moto but i can't figure out step 5 of https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-c ....change the directory? i changed to the folder where the tools are but $ fastboot oem unlock UNIQUE_KEY (+my key) doesn't do anything i get some sytax telling me i'm stupid. i tried doing this with minimal adb and fastboot app and got an "okay" but my device didn't unlock.
driving me crazy. i've rooted razr m, inc2 and haven't had this many problems and this is suppose to be easier? lol
even once i get the damn thing unlocked i fear getting the twrp img to the device...i'm sure that will be a joy too.
Click to expand...
Click to collapse
Just open the folder your platform tools is in and hit shift and the right button on your mouse to open the command window. You don't need the $ sign, just the command with your key.
Sent from my XT1060 using XDA Premium 4 mobile app
Ryno77 said:
Just open the folder your platform tools is in and hit shift and the right button on your mouse to open the command window. You don't need the $ sign, just the command with your key.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks and i did that...got the same message but phone didn't unlock.
Don't type unique_key, that is just where you put your unique key.
Sent from my Nexus 10 using Tapatalk
tcrews said:
Don't type unique_key, that is just where you put your unique key.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
*embarrassed*
*relieved*
*depressed*
what the heck does a fail due to too many links mean?
on reboot my phone went through an initial setup process. is that usual?
i powered down and back up into fastboot and device says its UNLOCKED status code: 3.
so i'm guessing i'm good and all thanks to you guys for helping me out! really....THANK YOU!
Device setup? Yes. You wiped data and starting fresh :thumbup:
well hells bells....
thanks again for all the support. superb!
32gb?
Where you bought the 32 gb version? It is only to developers?
fernandogtg said:
Where you bought the 32 gb version? It is only to developers?
Click to expand...
Click to collapse
You can buy it directly from Motorola. moto.com
I am asking for some help on this. I have always previously used toolkits to root and install recovery but I have a new N6 and I would like to learn to use ADB and fastboot. I have read several help guides and it all seems pretty straight forward except when i query the N6 with "adb devices", it does not return anything. However, if I enter the boot loader and query with "fastboot devices", it recognizes my N6. I have tried several different cables and ports, switching from mtp to ptp, resetting RSA keys, all with no success. I am using the latest adb, version 1.0.32 and my phone is stock 5.1.1. I am not a MAC power user by any means, so if someone can help, please use the simplest terms possible. Many Thanks
Update!....I had used EasyTether a few years ago and it was still in my extensions folder. I had unloaded it but not removed it with no success. Today, I removed it completely and now ADB recognizes my N6!! Thanks to all who commented.
jacksradio said:
I am asking for some help on this. I have always previously used toolkits to root and install recovery but I have a new N6 and I would like to learn to use ADB and fastboot. I have read several help guides and it all seems pretty straight forward except when i query the N6 with "adb devices", it does not return anything. However, if I enter the boot loader and query with "fastboot devices", it recognizes my N6. I have tried several different cables and ports, switching from mtp to ptp, resetting RSA keys, all with no success. I am using the latest adb, version 1.0.32 and my phone is stock 5.1.1. I am not a MAC power user by any means, so if someone can help, please use the simplest terms possible. Many Thanks
Click to expand...
Click to collapse
Did you enable USB debugging in Developer options for Android ADB?
danarama said:
Did you enable USB debugging in Developer options for Android ADB?
Click to expand...
Click to collapse
Yes, I forgot to say that in OP.
jacksradio said:
Yes, I forgot to say that in OP.
Click to expand...
Click to collapse
Is the android screen lock unlocked when you type the command?
jacksradio said:
Yes, I forgot to say that in OP.
Click to expand...
Click to collapse
Follow this guide, works like a champ. It's just like windows, CD to the location that contains your adb and fastboot (tools) and open terminal there.
ADB devices
danarama said:
Is the android screen lock unlocked when you type the command?
Click to expand...
Click to collapse
yes
jawmail said:
Follow this guide, works like a champ. It's just like windows, CD to the location that contains your adb and fastboot (tools) and open terminal there.
ADB devices
Click to expand...
Click to collapse
what guide?
Additional information......I keep seeing a reference to device drivers but I always thought Mac's did not require a driver to use ADB. Am I correct? Also, Android File Transfer works perfectly when I connect my N6 so the computer itself seems to be recognizing it. It also shows up as a Nexus 6 under "USB" in the system report.
This is the guide I used to set up ADB https://www.google.com/url?q=http://forum.xda-developers.com/showthread.php%3Ft%3D1917237&sa=U&ved=0CA4QFjAEahUKEwjvraDV2K7IAhWEoogKHbJPAxc&client=internal-uds-cse&usg=AFQjCNFwMzlRqY6AK7bv2ue6HmnF74sPjw
jacksradio said:
Additional information......I keep seeing a reference to device drivers but I always thought Mac's did not require a driver to use ADB. Am I correct? Also, Android File Transfer works perfectly when I connect my N6 so the computer itself seems to be recognizing it. It also shows up as a Nexus 6 under "USB" in the system report.
This is the guide I used to set up ADB https://www.google.com/url?q=http://forum.xda-developers.com/showthread.php%3Ft%3D1917237&sa=U&ved=0CA4QFjAEahUKEwjvraDV2K7IAhWEoogKHbJPAxc&client=internal-uds-cse&usg=AFQjCNFwMzlRqY6AK7bv2ue6HmnF74sPjw
Click to expand...
Click to collapse
Drivers I'm not sure. For linux, sometimes we have to do extra work (UDEV rules) but I can't say for Mac. What are these references to drivers and where are you seeing them?
danarama said:
Drivers I'm not sure. For linux, sometimes we have to do extra work (UDEV rules) but I can't say for Mac. What are these references to drivers and where are you seeing them?
Click to expand...
Click to collapse
I have been researching and reading guides on this site for almost 2 days just gathering infomation. Today I used the guide i referenced in above post to install ADB on my Mac. Most of the information and guides written on this site are for PC users, so that is where I kept seeing a reference to device drivers, but I just wanted to clarify in case I missed something that was assumed I should already know about using a Mac to root. I am guessing that since my computer recognizes my N6 in system report, that it does not need a driver, but since I am very much a novice, I wanted to ask.
jacksradio said:
I have been researching and reading guides on this site for almost 2 days just gathering infomation. Today I used the guide i referenced in above post to install ADB on my Mac. Most of the information and guides written on this site are for PC users, so that is where I kept seeing a reference to device drivers, but I just wanted to clarify in case I missed something that was assumed I should already know about using a Mac to root. I am guessing that since my computer recognizes my N6 in system report, that it does not need a driver, but since I am very much a novice, I wanted to ask.
Click to expand...
Click to collapse
Fair enough. In my adb and fastboot thread, there is a link to a tool that installs adb and fastboot on mac and that is literally all it does, so I don't think there is anything else for you to do. It seems to me that the issue may be on the device side, but unless you have parallels or bootcamp, I'm not going to be able to help you troubleshoot that.
danarama said:
Fair enough. In my adb and fastboot thread, there is a link to a tool that installs adb and fastboot on mac and that is literally all it does, so I don't think there is anything else for you to do. It seems to me that the issue may be on the device side, but unless you have parallels or bootcamp, I'm not going to be able to help you troubleshoot that.
Click to expand...
Click to collapse
Thank you for trying, I appreciate it and hopefully someone else may have some insight
jacksradio said:
Additional information......I keep seeing a reference to device drivers but I always thought Mac's did not require a driver to use ADB. Am I correct? Also, Android File Transfer works perfectly when I connect my N6 so the computer itself seems to be recognizing it. It also shows up as a Nexus 6 under "USB" in the system report.
This is the guide I used to set up ADB https://www.google.com/url?q=http://forum.xda-developers.com/showthread.php%3Ft%3D1917237&sa=U&ved=0CA4QFjAEahUKEwjvraDV2K7IAhWEoogKHbJPAxc&client=internal-uds-cse&usg=AFQjCNFwMzlRqY6AK7bv2ue6HmnF74sPjw
Click to expand...
Click to collapse
That's what I meant to attach No drivers needed for your Mac btw.
---------- Post added at 07:16 AM ---------- Previous post was at 07:12 AM ----------
OP did you get your ADB working?
jawmail said:
That's what I meant to attach No drivers needed for your Mac btw.
---------- Post added at 07:16 AM ---------- Previous post was at 07:12 AM ----------
OP did you get your ADB working?
Click to expand...
Click to collapse
I did not. However, I was able to root and flash recovery using fastboot. I can't for the life of me figure out why ADB isn't working though. I stumbled across an article which referenced EasyTether and how that can interfere with ADB and I remembered a few years ago, I had used that app on a different phone. I looked in the folder mentioned in the article and sure enough, the file extension was still there, so I unloaded it but even that did not help. I am wondering if there might be something else associated with EasyTether affecting it, but have no idea where to look or even how to completely uninstall it.
SOLVED
How do I marked thread solved?