Related
I have superuser in my app drawer, but some root apps won't run. I can't install busybox, unroot through EasyRoot, or get setCPU to work in anything other than read-only mode. Is there a way to fix my root?
Also, force re-root doesn't work in EasyRoot.
I'm in the same boat, any advice anyone?
I was experiencing the exact same thing
I did the steps here http://forum.xda-developers.com/showthread.php?t=766767 and now I have root back
... I'm not really all that technologically proficient. I don't even know how to get ADB.
silversonic1 said:
... I'm not really all that technologically proficient. I don't even know how to get ADB.
Click to expand...
Click to collapse
I just downloaded the android sdk zip (software development kit) and extracted it to a folder on my c:\ drive
theres a tools folder with "adb.exe" in it.. you just "cd" into the tools directory and type adb and the commands the guides tell you... just make sure your phone is in usb debuging mode
i have a htc wildifire, which has been rooted and installed with openfire rom. But i would like to install a custom boot animator, after reading posts i have realised that you have to gain adb access to your phone if im right?
i dont understand what is meany by that, i know how to access recovery, but how can i gain access to my phones system so im eligible to change the boot animator?
any suggestions are much apreciated.
same problem , you need to use root explorer , or this one ,adb, i download root explorer but dont now how to run it and try adb but it was difficult to me (adb,java,eclipse) ??????
ive tried using root explorer, but it dosent allow me to replace the bootanimation.zip.
i have not yet tried, adb could anyone link me to how adb works?
thanks
Ninja10 said:
ive tried using root explorer, but it dosent allow me to replace the bootanimation.zip.
i have not yet tried, adb could anyone link me to how adb works?
thanks
Click to expand...
Click to collapse
dl a bootanimation.zip file you want to use
place it into your android sdk tools folder (im assuming you have the android sdk installed)
e.g. mine is C:/android-sdk_r06-windows/android-sdk-windows/tools (yours would be different obviously if you installed it somewhere else)
reboot phone into recovery (well i do anyway)
run a command prompt
CD to your tools directory
type adb remount
type adb push bootanimation.zip /data/local/bootanimation.zip
type adb reboot
I am having a bit of difficulty rooting my g2. I am not sure if its related to my os or not but i can not get it to work.
I have followed this and tried it all kinds of different ways.
addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/[/url]
I can get to my run command after doing all of that and it shows my serial number after typing adb devices but after that i can't enter any info in the sdk run command promt.
I have not been able to gain temp root yet because it won't let me enter the commands. I went to try to re-install java/sdk manager yet again and now it says java is not in the right path.
Any help?
If you're having troubles with ADB, why use it? You don't need ADB anymore to root the G2. It can all be done by placing the files on the SD card and running Terminal Emulator on the phone. You can run any of the prompts from ADB in the phone instead. I rooted my first G2 this way. It took some getting used to coming from a phone with a 1-click root, but it wasn't hard.
Check the Wiki, pretty sure it outlines this method as well.
martonikaj said:
If you're having troubles with ADB, why use it? You don't need ADB anymore to root the G2. It can all be done by placing the files on the SD card and running Terminal Emulator on the phone. You can run any of the prompts from ADB in the phone instead. I rooted my first G2 this way. It took some getting used to coming from a phone with a 1-click root, but it wasn't hard.
Check the Wiki, pretty sure it outlines this method as well.
Click to expand...
Click to collapse
Do you have a link for that method i would be glad to try it but i am not sure what to search for, cant find it under rooting g2 with sd card
Also i am trying to gain permanent root if possible
901-Memphis said:
Do you have a link for that method i would be glad to try it but i am not sure what to search for, cant find it under rooting g2 with sd card
Also i am trying to gain permanent root if possible
Click to expand...
Click to collapse
Yep let me grab a link for you (theres actually a video tutorial I wanna try and find). But basically instead of using ADB to push the files to the correct location, you just have to manually put the files in the right locations on the SDcard, which is where ADB pushes them anyways.
K so I followed this method: http://www.youtube.com/watch?v=tU9zn_BEth4
The files he refers to are in this thread: http://forum.xda-developers.com/showthread.php?t=833965
Now different people have had different issues with this. I personally had some issues where it tells you to run #sync, because my perm root wouldn't stick properly after reboot. If this doesn't work properly, I'm sure someone can help you with your drivers to get ADB working.
I should also say that you don't necessarily have to do this method with the initial temp root via visionary, you can simply do the one outlined in the Wiki for rooting (aka http://forum.xda-developers.com/showthread.php?t=834228 ), but just place the files manually and run the commands in terminal emulator.
If you got the adb devices command to work you are actually in good shape. You are supposed to enter all of the commands from what you are calling the "run command" prompt anyway (the one you used for adb devices).
martonikaj said:
I should also say that you don't necessarily have to do this method with the initial temp root via visionary, you can simply do the one outlined in the Wiki for rooting (aka http://forum.xda-developers.com/showthread.php?t=834228 ), but just place the files manually and run the commands in terminal emulator.
Click to expand...
Click to collapse
Unfortunately this won't work (if you don't want to use ADB, Visionary must be used to get temp root). ADB is needed in order to push the files directly to the phone. If you try copying the files to the SD card first, you won't have the correct permissions to copy the files to the phone in Terminal. You are also not allowed to execute programs directly from the SD card (mounted as noexec), so you can't try to obtain temp root from there. If you want to use the gfree method of rooting without using ADB, I made a guide using Visionary for the temp root here: http://forum.xda-developers.com/showthread.php?t=928160.
But the OP actually has ADB working, so he should be able to use any of the guides.
This is the error i get now if i try to enter anything in the sdk manager run prompt box. Is there some place else i should be entering the commands?
Uploaded with ImageShack.us
901-Memphis said:
This is the error i get now if i try to enter anything in the sdk manager run prompt box. Is there some place else i should be entering the commands?
Click to expand...
Click to collapse
You are supposed to be using the regular command prompt (I think you referred to it as the "run command prompt" earlier). It is the prompt in which you successfully ran the "adb devices" command. That is the only prompt you need to use.
Do i enter commands 1 at a time or all at once?
901-Memphis said:
Do i enter commands 1 at a time or all at once?
Click to expand...
Click to collapse
First off, Yes you enter each line as you see it.
Second just to make sure you are in the right area to enter these commands, to get to command prompt you can either search for it from the start menu or hold the "windows button + R".
That opens your run command from there type in "cmd" and that opens command prompt.
Next make sure your current directory is the one you installed adb into. To get to that you can type "cd C:/...... whatever folder you installed it to."
To make sure my adb is working I usually type "adb devices" and see if my phone shows up.
Good luck
Glad to see someone else from the good ole 901 around here =)
Sent from my HTC Vision using XDA App
Okay does anyone have a better guide to rooting?
I got all the way to pushing all the files on the sd card and running the terminal emulator where it shows forked children, reboots the terminal emulator and then i can not enter /data/local/gfree -f
sync
It wont find that file
901-Memphis said:
Okay does anyone have a better guide to rooting?
I got all the way to pushing all the files on the sd card and running the terminal emulator where it shows forked children, reboots the terminal emulator and then i can not enter /data/local/gfree -f
sync
It wont find that file
Click to expand...
Click to collapse
try pushing the file to that folder again
Re-Tried everything at least 3 times, including pushing the files that didn't go.
I give up Ive spent so much time on this only to have it fail at the most unlikely times.
Will wait for another method to root come available
You could try downloading and installing Droid Explorer. It installs adb and fastboot files in its install folder.
Are you sure you actually pushed all of the needed files to your phone correctly (i.e., no errors appeared when doing so)? Which guide are you following and what were the specific errors you are getting? Once you have temp root, running gfree and obtaining permanent root only takes a few more minutes...
Also, did you try any other guides (like the one I linked to earlier)? If you are waiting for a new method of rooting, you might be waiting for a while (since the existing methods work, I don't know how actively people are working on new methods).
ianmcquinn said:
Are you sure you actually pushed all of the needed files to your phone correctly (i.e., no errors appeared when doing so)? Which guide are you following and what were the specific errors you are getting? Once you have temp root, running gfree and obtaining permanent root only takes a few more minutes...
Also, did you try any other guides (like the one I linked to earlier)? If you are waiting for a new method of rooting, you might be waiting for a while (since the existing methods work, I don't know how actively people are working on new methods).
Click to expand...
Click to collapse
Using this guide
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
I get an error when i attempt to enter this into the emulator on my phone
adb shell chmod 777 /data/local/gfree
and it doesn't do anything
901-Memphis said:
Using this guide
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
I get an error when i attempt to enter this into the emulator on my phone
adb shell chmod 777 /data/local/gfree
and it doesn't do anything
Click to expand...
Click to collapse
You are supposed to do that command from your computer. (The instructions state "On the computer, open terminal and type the following commands".) Here, terminal means the command prompt that you've been running all of you other ADB commands from.
If you wanted to run the command from terminal on your phone, you would just type "chmod 777 /data/local/gfree".
You don't need ADB for G2s.
trance2315 said:
You don't need ADB for G2s.
Click to expand...
Click to collapse
Can someone link me a better guide for my G2 so that i can try this 1 more time ?
Maybe a link to the top choices for versions of android to run once i get it rooted?
Hello all,
I'll preface this by saying that I'm completely new to android phones and rooting them so I apologize for being noob in advance.
I have been following this guide (wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide) to a tee and have ended up stuck at #6 with failed to copy/permission denied errors when I attempt to push busybox, superuser, or temp root over to my phone. I believe I have everything in order, such as: having the latest java sdk, installing the latest android sdk at c:\, downloading and installing the latest platform-tools (rev 4) and google usb driver, and changing the variable value section of path to "%SystemRoot%;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools", but i just cannot seem to execute the commands and I'm not sure what I'm doing wrong. I will also add that my phones settings are enabled for usb debugging and disk drive connection to PC.
This is exactly the command I'm trying:
C:\Users\thepaperescape>cd c:\android-sdk-windows\platform-tools
c:\android-sdk-windows\platform-tools>adb push su /sdcard/su
failed to copy 'su' to '/sdcard/su': Permission denied
Any help would be awesome. And sorry to make a new post... I've tried searching for 3 hours but cannot find the exact same incident.
Thanks
thepaperescape said:
Hello all,
I'll preface this by saying that I'm completely new to android phones and rooting them so I apologize for being noob in advance.
I have been following this guide (wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide) to a tee and have ended up stuck at #6 with failed to copy/permission denied errors when I attempt to push busybox, superuser, or temp root over to my phone. I believe I have everything in order, such as: having the latest java sdk, installing the latest android sdk at c:\, downloading and installing the latest platform-tools (rev 4) and google usb driver, and changing the variable value section of path to "%SystemRoot%;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools", but i just cannot seem to execute the commands and I'm not sure what I'm doing wrong. I will also add that my phones settings are enabled for usb debugging and disk drive connection to PC.
This is exactly the command I'm trying:
C:\Users\thepaperescape>cd c:\android-sdk-windows\platform-tools
c:\android-sdk-windows\platform-tools>adb push su /sdcard/su
failed to copy 'su' to '/sdcard/su': Permission denied
Any help would be awesome. And sorry to make a new post... I've tried searching for 3 hours but cannot find the exact same incident.
Thanks
Click to expand...
Click to collapse
You need to have VISIONary.apk downloaded and installed on your phone. and make sure to run it with Visionary.sh and Set system to r/w both checked. And try it again.
How ever their are much easier methods. This being one of them. Makes sure to go to page two.
neidlinger said:
You need to have VISIONary.apk downloaded and installed on your phone. and make sure to run it with Visionary.sh and Set system to r/w both checked. And try it again.
Click to expand...
Click to collapse
The guide I am using gives instructions on how to root specifically without visionary so I'd like to stick to it's outline but just find guidance on how to make it work.
thepaperescape said:
The guide I am using gives instructions on how to root specifically without visionary so I'd like to stick to it's outline but just find guidance on how to make it work.
Click to expand...
Click to collapse
okay.
I've seen alot of people try this method and very little come out okay.
you need SU access to push objects to the phone. The phone is seeing it as a foreign object and is wanting to prevent it from being pushed. The only other option you'd have is to turn on mass media storage and drop/drag the objects to the root of the SDcard.
Agreed with neidlinger, if I'm not mistaken you must have atleast temproot to be able to use the command 'SU' as it stands for superuser and as ridiculous as it sounds you are not the superuser of your phone, Google is
Sent from my HTC Glacier using XDA Premium App
Nicgraner said:
Agreed with neidlinger, if I'm not mistaken you must have atleast temproot to be able to use the command 'SU' as it stands for superuser and as ridiculous as it sounds you are not the superuser of your phone, Google is
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
SU was actually Switch User but Super User is used ATM due to the confusion it created to the newbies a decade ago who didn't understand how permission base structure on *nix worked. Which always required chmod and whole rwx thing even made it more confusing so they preallocated it with [email protected] with UiD:0 as default permission.
Now what I like to know is why are you using that howto? As neidlinger stated just run VISIONary+ to get TempROOT and then do root.sh to obtain PermROOT. If you need to unlock the CiD just call TMo and get the code free as no need to risk it. But if you still want Radio S=OFF then just do the simple gfree step and you will have it.
You shouldn't need temproot to push a file to your sd card. Have you made sure the file is in the same folder as adb directory?
UsrBkp said:
Now what I like to know is why are you using that howto?
Click to expand...
Click to collapse
Well for one, I chose that guide because my goal is to install cyanogen and that is found directly off their site regarding my phone. My expectation is that a group of developers so renowned for their contributions should be able to correctly explain how to get to the point of install. Still I know it's a wiki, and things are constantly changing (generally faster than the wiki). For instance, I did notice that the wiki was incorrect about the location of the google usb drivers post download. I assume that is due to the newer version of the sdk i installed. And the jdk r25 is pretty new and I believe that to be one of the other things causing me problems, but I don't know for sure.
neidlinger said:
The only other option you'd have is to turn on mass media storage and drop/drag the objects to the root of the SDcard.
Click to expand...
Click to collapse
I tried doing this for those two files (su and superuser) that are supposed to be pushed onto the sd root and i thought it worked. cmd allowed me to push the other three files into /data/... no problem. chmod to 0755 even seemed to work (it neither explicitly approved or denied). but then when I got to step 8, terminal on the phone said i did not have access to run that command.
shuka325 said:
You shouldn't need temproot to push a file to your sd card. Have you made sure the file is in the same folder as adb directory?
Click to expand...
Click to collapse
That's what I figured based off of the guide (since it's a guide on GETTING TO temproot, but what do I know... i'm supernoob. I've attached an image to see if you can see ANYTHING wrong with what I'm trying to do.
Thanks for everything guys!
I would give up that guide and use VISIONary to gain Temp Root & Root.sh to obtain perm Root. Then install the latest rom manager and make sure CWM sticks. Then you can flash CM7, or any other ROM for that matter.
Is there any guide you all think stands above the rest?!?!
thepaperescape said:
Is there any guide you all think stands above the rest?!?!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=13989736&postcount=6
The method is similar to the original Root tutorial before but with help of kindleroot_androidpolice.apk released from http://www.androidpolice.com as more obstacles in 6.2.1.
1. Download kindleroot_androidpolice.apk
http://www.androidpolice.com/2011/1...on-kindle-regardless-of-its-software-version/
2. Copy kindleroot_androidpolice.apk to your Kindle Fire device and install it.
3. Run it! Click Agree > You Rock > Root
4. Now you can connect your Kindle fire to your PC with USB line.
For the Windows System:
Start > Run > CMD
Code:
cd C:\Program Files\Android\android-sdk\platform-tools
(I installed the SDK by default so you can see my directory above that way)
If you installed your SDK to C:\Android then you should
Code:
cd C:\Android
If you download some guy's package for ADB and unzipped it to C:\adb, simply you should enter command
Code:
cd C:\adb
5. Download the latest version for SuperOneClickv2.3.2-ShortFuse from official site http://shortfuse.org/?p=171
Unzip the package and Run SuperOneClick.exe
Click Root Button
Unfortunately you will find that the commands will stop at WaitForDevice.
What should we do now?
6. Don't be panic! Just Run these lines in your command window:
Code:
adb root
adb kill-server
adb remount
Everything is okay now and the commands will be continued to END
Root completely
You can check SuperUser working well again on your KF
Screenshot images and package files are post in a Chinese Kindle Fire Forum, just check them at:
http://www.92kindle.com/thread-2905-1-1.html
Damn I think I'm gonna try that after installing 6.2.1 but it better work.
Sent from my Kindle Fire using Tapatalk
Anyone tried this method yet and can confirm that it works?
The method on androidpolice works. I am running 6.2.1 rooted right now!
Course BurritoRoot works, with a name like that it has to
edit
trollololololol
Actually this method works better. There seems to be a problem with the su program on androidpolice. It gives root alright but some programs don't get root access for some reason. SuperOneClick works better.
jlocohustler said:
Actually this method works better. There seems to be a problem with the su program on androidpolice. It gives root alright but some programs don't get root access for some reason. SuperOneClick works better.
Click to expand...
Click to collapse
i dont know if u read! but superoneclick was broken after last update, and jcase was nice enough to root this blindly so we could root !!!
jlocohustler said:
Actually this method works better. There seems to be a problem with the su program on androidpolice. It gives root alright but some programs don't get root access for some reason. SuperOneClick works better.
Click to expand...
Click to collapse
SuperOneClick can not root 6.21. Hence the use of BurritoRoot in the OP.
Methods to gain root are the same, since they use the same app to do it.
There was a problem with the su binary on AP but its been replaced.
I can verify the Android Police method works just fine without the SuperOneClick. Triedit twice, rooted then unrooted so I could watch Prime Video, then rerooted so I can install OTA Rootkeeper so I could watch video without unrooting. Only difference for me was I had SuperUser already from my pre-6.2.1 root but its the same as the the one AP distributes.
FYI my computer is a Mac so this was executed from shell.
Ibis, can you give me some more information on how you did this on a Mac?
I tried and it seemed to work but don't think it took as I cant copy the framework Apk to system/apps and when I try to run market it force closes with a vending error.