Hello, okay I have a Motorola Moto one 5G ace/ Android. How do I got about rooting and getting the crap off this phone. And help would be greatly appreciated because if I did it on my own I'd probably destroy the phone
A phone's Android is rooted when the SU-binary ( read: Switch User ) is present in Android's filesystem. Hence push a suitable SU-binary ( ~110 KB ) to Android and make it executable
Example:
Code:
adb devices
adb push <LOCATION-OF-SU-BINARY-ON-PC> /data/local/tmp/
adb shell "chmod +x /data/local/tmp"
First you need to unlock your bootloader. If you have the Verizon or AT&T phones, this is essentially impossible. The guides on here are accurate.
Related
I been looking for an ATT Avail root guide since january, I found this page today and I am wondering if anyone has done this successfully?
if you google "root att avail" it is the top search result link right now and it is at a site called android police.
here is a copy/paste of the article:
New root methods show up all the time, so it's not a huge deal that a rather unknown phone on AT&T is now rooted. So why are we posting about it? Because the root method used is, well... interesting.
It was uncovered by our own Justin Case from TeamAndIRC, and while a big part of the process will look very familiar to some of you, there is one step that induces a wait, what? moment.
Before you get started throwing commands at the little guy, though, you need to grab this file. After that, commence command throwing.
adb shell rm -r /data/local/logs (if this command gives you an error, do not worry, it is precautionary)
adb shell mkdir /data/local/logs
adb shell ln -s /data/local.prop /data/local/logs/loglast1.tar.gz
Dial *983*7668# on your phone. This does a few things, it mounts /system as writable on boot, and creates the loglast1.tar.gz.
Wait about 10 seconds, then continue.
adb shell echo 'ro.kernel.qemu=1' > /data/local.prop (Nod to Rosenberg here)
adb reboot
Once the phone reboots, continue
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm -r /data/local/logs
adb shell rm /data/local.prop
adb shell rm /data/property/persist.sys.ztelog.enable
adb shell rm -r /data/local/rwsystag
Head into the Market and grab the Superuser app.
Done.
Catch that bold part? Looks like someone at ZTE dropped the ball and left seventy-nine developer codes in the retail version of the device. Oops.
Of course, their mistake is your gain. Hell, there's even a code to disable Carrier IQ: *983*24737#. Enter the code, ???, profit.
While this is definitely an unusual and unique find, it's also quite dangerous. This means that any app can mount the system as writable and, from there, basically control everything. As a result, JCase contacted ZTE to let them know of their oversight.
Click to expand...
Click to collapse
if someone could let me know if this is legit, that would be a fantasticism.
yes that is legit.
see my thread:
http://forum.xda-developers.com/showthread.php?t=1437032
Jcase broke it, the loon created a batch file to make it easier
http://forum.xda-developers.com/showpost.php?p=21627136&postcount=37
thats the last version of the batch file
Cool, thanks, for some reason I cannot connect to my avail via usb, I have it in developer mode and unknown sources checked, I ran adb devices command and it does not find my phone and when I try to run or debug in eclipse it does not find my phone there either.
I used it, and now have root. I wish all phones were this easy to root.
Requirements and rooting process
1 > Your pitiable unrooted Karbonn A9 Android device
2 > ADB drivers for your device installed on your pc (I used WinXP. You may use Win 7/Vista or the Linux distro of your choice)
3 > su , busybox , Superuser.apk
4 > A working linux distro with Nautilus (use a live usb stick of Ubuntu 11.04)
5 > Strength, courage and whatever makes you a man !!!!!
Rooting Process
To start, you must have adb installed on the OS of your choice.
I used my trusty WinXP system .
To confirm your device is properly detected, in the command prompt , run -
CODE -
adb devices
Now copy busybox, su, superuser.apk to /data/local/tmp/ using adb.
CODE -
adb push busybox /data/local/tmp
adb push su /data/local/tmp
adb push Superuser.apk /data/local/tmp
Now run adb shell .
CODE -
adb shell
Note that you see a "$" sign in the command prompt. That means you are not rooted . Next run the following commands in the shell to change permissions and get some limited privileges for the Superuser files:
CODE -
chmod 6755 /data/local/tmp/su
chmod 755 /data/local/tmp/busybox
chmod 644 /data/local/tmp/Superuser.apk
Note that the names of the files are case sensitive.
Done?
Turn off your Android device using the power button.
Now you need to reboot your system into a Linux distro which has Nautilus.
Android and Linux, having a similar heritage, makes it possible for us to get root access over the Android phone if you are running with root privileges within Linux. I used an Ubuntu 11.04 Live USB disk to save the hassle of installing another os.
When you have booted into Linux, open up terminal and type:
CODE -
sudo nautilus
This would open up the Nautilus file browser with root privileges.
Now put your Android device into Download mode . for the karbonn A9 the method is to hold down the Volume up button and simultaneously turn on the phone using the power on switch.
Once in download mode, connect the Android device using the microusb cable to the computer.
Now using the open Nautilus window, navigate to /UserData/local/tmp/ folder and verify that you have the files you sent to the device viz. su, busybox and Superuser.apk
Move/cut-paste su and busybox to /system/bin/ using Nautilus.
Move/cut-paste Superuser.apk to /system/app/ using Nautilus.
Now pull out the battery from your Android device.
Now simply turn on your device.
You must now have root.
Verify by running:
CODE -
adb shell
su
You'll note that the "$" prompt will turn into a "#" and you'll be prompted by a Superuser permission notification on your
device
WOOHOO !!!! YOU NOW HAVE ROOT ON YOUR PHONE !!!!
Important -
1 > For all purposes, consider that your warranty will be void if you follow these steps
2 > I am not responsible for any loss, monetary or otherwise arising as a result of this article.
If you don't feel up to it, quit now and close this web page .
3 > I must assert that although I am aware of no reason why this should not work on *any* Android device, phone or tablet, I have only tested this on my GALAXY s3 .
4 > I have tried to explain it in the easiest way I can, but I must state here that this is by no means an easy task and you must persevere. If you can't follow the steps to the letter, its better you don't follow them at all and wait for a single click app for this or a custom rooted firmware.
RESERVED
reserved .......................
RESERVED
reserved .......................
Doesnt work,Already tried it a week ago.
THis technique doesnt work.I have already tried it a week ago.
here's the original link:
http://www.erodov.com/forums/how-root-any-android-device-manually/43325-page2.html
The problem is that nautilus just wont list our device's folders.
And download mode is opened by pressing Vol down + power for A9,
Vol up + Power opens fastboot.
Hi, I'm having trouble choosing the right section, anyway..
After more than a year i managed to correctly install ADB drivers, because before i installed Google driver, when i noticed i must install Motorola driver , the removing of previous one did not successful done, so the Motorola one did not installed well, by manually removing files it succeed.
But now another annoying not previewed issue, i need to exchange a file in /system/etc both in my tablet and my Motorola moto C tel. , it needs to remount system part. in r/w but to do this need to restart adb as root but with 'adb root' this is the answer:
adbd cannot run as root in production builds
my system is 7.0, what can i do?
You can install a temporary root to run shell-commmands what require root-rights like mount in ADB:
Code:
adb devices
adb push <FULL-PATH-TO-SU-BINARY-ON-PC> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
adb shell "/data/local/tmp/su -c 'mount -o rw,remount,rw /system'"
I have two questions, i don't find any su command available in the net.
I don't understand how it is possible to have to do all these hard maneuvers with a debug tool, i think it might be simpler.. why there's a command remount or root if it doesn't work?
hello i have my device SM A202F ANDROID 11 so i tried to root it but not working i have tried with kingroot ADB and Odin to flash twrp but not works if someone have the file to root it please share it thx
Every Android OS is rooted if a single binary called su is presnt in the Android ecosystem.
You at any time can add this binary by means of ADB
Code:
adb devices
adb push <LOCATION-OF-SU-BINARY-ON-COMPUTER> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
The matching SU-binary you extract from su-ARM.zip what you can download from
here.
jwoegerbauer said:
Every Android OS is rooted if a single binary called su is presnt in the Android ecosystem.
You at any time can add this binary by means of ADB
Code:
adb devices
adb push <LOCATION-OF-SU-BINARY-ON-COMPUTER> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
The matching SU-binary you extract from su-ARM.zip what you can download from
here.
Click to expand...
Click to collapse
am i undesrstand i have unlocked the bootloader but can you make a video about abd push i dont understand
Hi, I got a new phone recently, as the name implies it's a CC Core-m5, I would like to root this device but unfortunately there isn't anything on internet and the guys working at CC doesn't want to give me the firmware so that I can patch the boot using magisk.
Can someone help please ?
If someone manage to get temporary root access (even if it can't remount partitions) can he post how he managed to do it ? That way we could build our own TWRP image
Temporary root access is easy to realize: simply put a suitable su binary into Android's filesystem and make it executable:
Code:
adb devices
adb push <FULL-PATH-OF-SU-BINARY-ON-PC> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
xXx yYy said:
Temporary root access is easy to realize: simply put a suitable su binary into Android's filesystem and make it executable:
Code:
adb devices
adb push <FULL-PATH-OF-SU-BINARY-ON-PC> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
Click to expand...
Click to collapse
Thanks a lot, Im gonna try that, I thought of that technic but wasn't sure if it was possible
Hmm, look like this isn't possible anymore, or Im doing it wrong. Im using lineageOS 18.1 su binary, when executing it threw the shell I get the error code 255. Weird
Using the SU binaries you provided in an other thread I get the error code 1. Nothing more
xXx yYy said:
Temporary root access is easy to realize: simply put a suitable su binary into Android's filesystem and make it executable:
Code:
adb devices
adb push <FULL-PATH-OF-SU-BINARY-ON-PC> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
Click to expand...
Click to collapse
xXx yYy said:
Temporary root access is easy to realize: simply put a suitable su binary into Android's filesystem and make it executable:
Code:
adb devices
adb push <FULL-PATH-OF-SU-BINARY-ON-PC> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
Click to expand...
Click to collapse
You won't get root access this way, as root access is allowed for binaries in root partition.
As you can't write this partition <=> you can't put any binary on it.
idem-bis-repetita
As seen in this thread https://forum.xda-developers.com/t/rooting-crosscall-core-m5.4359409/ there is a way to get temporary root access.
@xXx yYy Any further ideas ? Thanks btw
Might be resolved once we get more informations on dirty-cred, as it may affect the android kernel too.
Bricked my phone lol, no working recovery