Database Develop

[Q] Atrix HD Developer Edition

Greetings All -
First time post...lurked for a while. Just recently purchased an Atrix HD Dev. Edition. I guess I'm a little bit confused...I got an unlocked bootloader etc., but no su executable or Superuser.apk. Motorola gives no instructions on getting root, just how to unlock your bootloader.
I realize I could flash the phone and run a different image/ROM etc, but I want to just use the current generic ICS install for the time being.
I've rooted multiple other Android devices, so I get the idea of using an exploit to get root, install su/busybox/superuser.apk etc. If I want to get root on this install of ICS 4.0.4 do I still need an exploit to get root? With adb I can manually move over su, busybox etc. but I can't remount system and can't put su in place and change it's perms in order to "SU". I thought that a dev edition phone was supposed to be at least partially "rooted"? Am I missing something here?
Thanks in Advance

If your on ics then there is a 1 click root in the android development section.
sent from my JokerMATRIX HD MAXX

developer edition on ICS, no root
deeje00 said:
If your on ics then there is a 1 click root in the android development section.
sent from my JokerMATRIX HD MAXX
Click to expand...
Click to collapse
I've been searching the forums off and on since January, trying to see if anyone has successfully rooted an unlocked Atrix HD developer edition, ICS 4.0.4. No luck finding anything, so this is my first post. At least I'm not the only one with this problem.
I've tried motofail2go many times but it says "exploit failed" and I verify with Root Check Basic, which confirms that it's not rooted. USB debugging is on, and I've tried it while connected as mass storage and media device. I've tried replacing adb that came in the zip file with a newer version, and also other versions of su and superuser that were suggested.
The volume up + power never seemed to give a unique vibrate; I tried it with screen lock and without, hundreds of times. I also tried running adb bugreport from a separate cmd window, which did produce a double vibration but didn't make a difference.
Is there some reason that this won't work with an unlocked bootloader?

Some of the time you can root generically, try rooting with this "universal root 4.0.4" guide.
Also your "partially" rooted I think you can try installing Super User from the play store
here.

[Q] Root on JB - SAMBA Exploit Permissions No Longer Working?

I am attempting the SAMBA Root Exploit as outlined in this thread:
http://forum.xda-developers.com/showthread.php?t=2143437
I've run into the same issue as this post:
http://forum.xda-developers.com/showpost.php?p=39186782&postcount=275
I received this phone just last week, and applied the JB update (to 4.1.2) upon receiving it.
I am worried that the SAMBA exploit no longer works, and that permissions/owner for all files mounted via SMB are reset to system:sdcard_rw which won't allow the pwn script to run.
I've confirmed on the Ubuntu side that the permissions/owner are properly set to 6755 root:root, but once mounted via SMB and accessed through the ADB shell, the owner is reset to system:sdcard_rw
That's at least 2 people now who've encountered the same problem. Is anyone else seeing this?
Here are the versions of everything I have:
Ubuntu Live USB 12.10
System Version: 98.6.11.MB886.BellMobility.en.CA
Baseband Version: MB886_BP_100740.071.65.61P
Build Number: 9.8.2Q-8_MB886_FFW-11

I just did it two nights ago on Ubuntu 12.10
No problems at all.

It we works fine always check your debug settings every time u type a command it some how kept turnin my settings off on my debug also make sure u set pass word for guest I lacked that for an hour
.and it might help to redo ure ROM back to stock jellybean and then uninstall updates for sure stock file apk.
Sent from my DROID RAZR HD using xda app-developers app

The problem is - BELL atrix HD, i can not root it on 4.1.2 so maybe someone can root bell?? AT&T versions rooted with no problems.

I can't root the bell version too.
Sent from my MB886 using xda app-developers app

Out At&t phones were on 4.1.1 while rooting,
may be the procedure doesnt work with 4.1.2

[Q] bionic jb 98.72.22 su binary help! root access?

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.

App that runs the 2 Pie root commands from the phone

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.

Android L keyboard

Hey all. Just seen an article about getting the new L keyboard on any kit kat or newer devices. It does however require root. I'm not willing to root until the bootloader issue is fixed.
Will all these neccesary steps be possible with abd over USB, I have used adb but only for updating my HTC one so not an expert by any means.
Steps to Install Android 5.0 Keyboard on Any Device Running KitKat or Jellybean
Download and Install a root explorer app such as ES File Explorer app (download here).Go ahead and install*Android 5.0 Keyboard APK*from the download link above.Browse to*/system/lib*directory on your phone and rename thelibjni_latinimegoogle.so*file tolibjni_latinimegoogle.so.bak, using a file explorer app of your choice. Ensure the file permissions are set to rw-r--r--.
Note:This is to ensure that you backup the current .so file before replacing it with the new version in next step.
Copy the new libjni_latinimegoogle.so file you downloaded earlier to the /system/file directory on your phone.You can now try launching the newly installed keyboard and check its functionality. If it fails to launch, just reboot the device once and it should work.
Cheers guys
Sent from my D5833 using Tapatalk

Just wait for the android upgrade in January.. Then you will not require root..
Sent from my D5803 using XDA Free mobile app

" I'm not willing to root until the bootloader issue is fixed."
The Bootloader wont be "fixed" its not broken.

King p1n said:
" I'm not willing to root until the bootloader issue is fixed."
The Bootloader wont be "fixed" its not broken.
Click to expand...
Click to collapse
Really? I said the bootloader issue. It's an issue that you have to unlock the bootloader and effectively remove warranty for root. That's an issue for some for us. It may not be for you, but it's a fair reason to wait for an exploit.
Do any of you know the answer to the question?

AKZam said:
Really? I said the bootloader issue. It's an issue that you have to unlock the bootloader and effectively remove warranty for root. That's an issue for some for us. It may I get not be for you, but it's a fair reason to wait for an exploit.
Sent from my D5833 using Tapatalk
Click to expand...
Click to collapse
The wording made it seem to me like it was a bug that Sony is working to be fixed.

Sorry for the confusion then
Sent from my D5833 using Tapatalk

I'm a bit confused here. Beenbusing the L Keyboard just fine. It does not require root. The apk is posted on this forum. Use google search.

tofu- said:
I'm a bit confused here. Beenbusing the L Keyboard just fine. It does not require root. The apk is posted on this forum. Use google search.
Click to expand...
Click to collapse
Yeah I just found a working copy here http://forum.xda-developers.com/android/apps-games/lollipop-keyboard-phones-root-t2910268. Tried a couple along the way that didnt work though also.
Cheers for the heads up!