Related
Anyone knows how to install busybox?
I've tried to follow some guides but ends up with:
Code:
215:Desktop ricardo$ adb push busybox /data/local
580 KB/s (1083568 bytes in 1.823s)
215:Desktop ricardo$ adb shell
$ su
# cd /system/xbin
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cat /data/local/busybox > busybox
cannot create busybox: not enough memory
or
$ su
# cd /data/local
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# dd if=/data/local/busybox of=/system/xbin/busybox
/system/xbin/busybox: cannot open for write: Out of memory
or
$ su
# cd /data/local
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# ./busybox cp /data/local/busybox /system/xbin
cp: can't create '/system/xbin/busybox': Cannot allocate memory
same here. cannot write to rw-mounted /system.
sucks
Try my zip file. Woked for me
The only thing that I want to change and I can't is the init.rc file. I tried to mount the / (rootfs) with rw, but every time I restart my device the file is copied, again, from the ramdisk image.
I have the same problem
ricardoft said:
Try my zip file. Woked for me
The only thing that I want to change and I can't is the init.rc file. I tried to mount the / (rootfs) with rw, but every time I restart my device the file is copied, again, from the ramdisk image.
Click to expand...
Click to collapse
What should I do with your files?
Nobody has a solution to this?
I don't think this is a memory issue though, .. added 512mb swap and still it claimed to be out of memory, ..
also I figured maybe hd space .. however when i ln /data/local/tmp/busybox to /system/xbin it had the same error.
I both tried ln from the system and ln from busybox both had same result.
It's not a memory problem! In order to install it you have to be in recovery mode.
Try:
While in recovery mode use adb to connect to our phone. Now transfer the zip file (busybox.zip) to your phone and install it via clockwork recovery -> install zip file -> select my zip file.
can anyone post the proper busybox file cause for some reason the file signature verification failed.
adb push busybox-signed.zip /sdcard/busybox-signed.zip
rebooted phone held down volume button while booting ..
choose recovery, ..
choose install zip from sdcard..
then i see a lot of no and one yes .. so i choose yes but the installation is aborted.
Just install titanium backup and click on 'problems?' at the bottom. It will install BusyBox for you.
it has error during installation at line 4 with your busybox.zip
somethinf like can not chmod
(rooted buzz with stock rom)
Elibongo said:
Just install titanium backup and click on 'problems?' at the bottom. It will install BusyBox for you.
Click to expand...
Click to collapse
Do what this guy said.
titanium install in /sdcard busybox, not in /system/bin (xbin) , so it is not usuable by other apps
i have installed it in during recovery mode in /system/xbin
how now to specify PATH for using commands from it?
kevin2516 said:
Do what this guy said.
Click to expand...
Click to collapse
you have read my mind especially since that isn't free software.
hellysmile said:
i have installed it in during recovery mode in /system/xbin
how now to specify PATH for using commands from it?
Click to expand...
Click to collapse
i think you need to create aliases however why install it in xbin anyways then, .. if you need to create aliases or links in bin.. ?
example
$ ln -s /data/local/tmp/busybox ls
$ ./ls
if it is in a path that is included in PATH executing a command will auto look for it in all directories defined in PATH env so basicly you could just create all the directories under /data/local/tmp/bin
and just then append that to PATH env echo $PATH then append :/data/local/tmp/bin to it and busybox should work as well.
Ofloo said:
you have read my mind especially since that isn't free software.
Click to expand...
Click to collapse
titanium backup is free software... look on the market, there's a free version and a donate version.
i have aliases in /system/xbin
they was created after busybox --instal -s
but in system allready exists some commands like ls => i want to use ls from busbox, not from system
and terminal emulator dont anderstand ^[ likes bindings
is there a definitive way to do this. There seems to be no clear way of doing it.
matpol said:
is there a definitive way to do this. There seems to be no clear way of doing it.
Click to expand...
Click to collapse
Maybe this helps:
fang0654 said:
To install:
1) extract and push busybox to your sdcard, reboot into recovery
2) mount /system
3) if you don't have /system/xbin (you should), create it
adb shell:
# mkdir /system/xbin (if necessary)
dd if=/sdcard/busybox of=/system/xbin/busybox
cd /system/xbin
chmod 755 busybox
./busybox --install .
4) reboot and done
OPTIONAL - before rebooting replace the busybox installed by the root process in /system/bin
1) mv /system/bin/busybox /system/bin/busybox.bak
2) cp /system/xbin/busybox /system/bin/busybox
Click to expand...
Click to collapse
from this site: http://forum.xda-developers.com/showthread.php?t=702634
The above is pretty straightforward. The only thing is you need to download the zip in the other thread and 'busybox' refers to the binary in the zip rather than the whole directory - as I understand it. Correct me if I am wrong but trying the dd command on the dir will not work.
matpol said:
The above is pretty straightforward. The only thing is you need to download the zip in the other thread and 'busybox' refers to the binary in the zip rather than the whole directory - as I understand it. Correct me if I am wrong but trying the dd command on the dir will not work.
Click to expand...
Click to collapse
You dont have to extract the binary into a folder, just extract the busybox file direct on your sdcard. Than the dd command should work, on my phone it works fine.
But if not, does the command cat in the adb shell work?
If so, try istead of the dd comand:
Code:
mount /sdcard
cat /sdcard/busybox > /system/xbin/busybox
And remember to start your wildfire in the recovery mode, that was the mistake I had done...
This howto is for those people who are unable to root their Galaxy Tab using any of the automated procedures and do not suffer from CLPS (command-line-phobia-syndrome).
My story: After upgrading my EURO (GSM) Galaxy Tab to JM6 my persistent efforts to root the device using either the z4root or SuperOnClick methods have all been unsuccessful. z4root (v1.3.0) kept crashing at different stages, apparently depending on which and how many background apps were running. With SuperOneClick I never managed to get beyond the "changing permissions" stage.
Since both methods are basically wrappers of the rageagainstthecage application, I tried to perform the rooting procedure manually. Guess what, that worked without any problem and it is pretty easy to do.
The basic steps of the rooting process are:
1) use rageagainstthecage to get a temporary root shell
2) use the temporary root shell to copy three files to the read-only system partition the device
While I find the outlined procedure straightforward, you may not. Anyhow, try this at your own risk.
==== Prerequisites ====
I used Ubuntu 10.10 for this, but it should work on any other distro and on Windows just as well. Whatever OS you use, you need a working adb connection to your Galaxy Tab. Odin or Kies are of no use here.
You need the following binaries
* su
* busybox
* Superuser.apk
* rageagainstthecage
To get the all required files, simply download "SuperOneClickv1.5.5-ShortFuse.zip". That's what I used.
Get it here: http://forum.xda-developers.com/showthread.php?t=803682
Extract the contents of the ZIP, open a command-prompt on your computer and change to the directory where the extracted files are located.
Some advice if shell commands are not your regular cup of tea.
The following instructions show the shell commands. Some are executed on the host computer. Others are executed on the Galaxy Tab. You can differentiate between the two easily: All commands which start with "> " need to be executed in a shell on the host computer. Commands which are prefixed with "$ " are executed on the Galaxy Tab. In both case the ">" and the "$" must not be typed. If you copy+paste from this howto, make sure only to copy the commands and leave out the prompt.
==== Step 1: getting a temporary root shell ====
Copy the rageagainstthecage exploit to a temporary directory.
Code:
> adb push rageagainstthecage /data/local/tmp
263 KB/s (5392 bytes in 0.020s)
Change the file permissions and execute the exploit.
Code:
> adb shell
$ cd /data/local/tmp
$ chmod 777 rageagainstthecage
$ ./rageagainstthecage
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
(other output truncated)
Your shell session will be terminated which will throw you back to the regular command prompt of your host computer.
==== Step 2: restart adb server ====
Now stop and restart the adb server process.
Code:
> adb kill-server
> adb start-server
* daemon not running. starting it now *
* daemon started successfully *
Now reconnect to the Galaxy Tab again. Notice the '#' prompt. This means you have a temporary root shell now. We use this to execute some privileged commands which make the rooting permanent.
==== Step 3: making it permanent ====
First, make the system partition writeable. We need this to be able to copy su, busybox and Superuser.apk to the required locations. Then exit the android shell again.
Code:
> adb shell
# mount -o remount,rw -t rfs /dev/block/stl9 /system
# exit
Now we push busybox and su via adb. Then we install Superuser.apk.
Code:
> adb push busybox /system/bin
> adb push su /system/bin
> adb install Superuser.apk
The final steps are to change the file permissions for su and busybox and then remount the system partition as read-only again.
Code:
> adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/stl9 /system
# exit
That should be all. Try a reboot and some apps which require root, like Titanium Backup. The Superuser.apk should popup a dialog requesting permission.
Hope this helps. Happy rooting.
[update]
This process worked for JMA and JMD as well.
"adb install" Superuser.apk instead of "adb push"
[/update]
It will help me !
Merci ;-)
Fantastic! This is just what I was looking for, thank you! I feel dumb now, because I started a thread of my own right as you posted this. You must just type faster than me
I ran a quick test, and it all looks good. One quick question actually. Why do you mount like this:
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
When most instructions for the Galaxy Tab have you doing something like this:
Code:
# mount -o remount,rw -t rfs /dev/block/stl9 /system
I'm not saying it is wrong, in fact, it actually worked for me. I'm just curious as to why it works like that? My understanding of mounting partitions and such in Linux is a little bit weak, so I like to indulge my curiousity by bugging fine people like yourself
Anyway, thanks again, this did exactly what I needed it to. Well done, I appreciate it.
DavidThompson256 said:
One quick question actually. Why do you mount like this:
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
When most instructions for the Galaxy Tab have you doing something like this:
Code:
# mount -o remount,rw -t rfs /dev/block/stl9 /system
I'm not saying it is wrong, in fact, it actually worked for me. I'm just curious as to why it works like that? My understanding of mounting partitions and such in Linux is a little bit weak, so I like to indulge my curiousity by bugging fine people like yourself
Click to expand...
Click to collapse
Thanks for pointing that out! Actually both the filesystem type and blockdevice name were totally wrong. Apparently the mount command ignores both parameters - at least when they are wrong.
I just verified this as self-punishment for not paying attention:
Code:
# mount
(...)
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
(...)
/system is mounted read-only to /dev/block/stl9. This is the normal state of things.
Now I remount this without the fstype parameter and using a wrong blockdevice name:
Code:
# mount -o remount,rw /dev/block/xyz /system
# mount
(...)
/dev/block/stl9 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
(...)
Surprise, this actually remounts /system in read-write mode. This is why my original howto worked despite using the wrong parameters.
Thanks again. I corrected the HOWTO.
It works for me, but i get now error message: The application calendar save (proces com.android.providers.calendar) is unexpecly stopt. Try again. Forced closing
I had this also with SuperOneClick.
When i want to start the calender in the applications i get it also.
The application wil not run anymore.
How can i resolved this.
Thnx
leonreijnders said:
It works for me, but i get now error message: The application calendar save (proces com.android.providers.calendar) is unexpecly stopt. Try again. Forced closing
I had this also with SuperOneClick.
When i want to start the calender in the applications i get it also.
The application wil not run anymore.
How can i resolved this.
Thnx
Click to expand...
Click to collapse
That is strange. The result of the rooting process is just adding three files to the system partition. I find it hard to believe that this could lead to the problem you describe. However, while experimenting with z4root I had the the effect that there were many rageagainstthecage processes running in the background and the Galaxy Tab slowed down considerably. Perhaps there is something similar going on.
Have you tried rebooting after completing the rooting process?
Try shutting down the Tab completely.After rebooting get a shell on the Tab with "adb shell" and execute "ps". That shows the process list. If that looks normal, I would try a factory reset of the device. Which ROM version are you running?
BlackLevel: Thank you soooooooooo much... I don't get how to hit the Thanks Meter thing, but here is the old fashioned way. I used a MacBook to accomplish your perfect, step by step rooting of an AT&T Galaxy Tab i987. It helps that I'm more comfortable at the command line than with most GUI systems.
I could put this into a bash script, but that could be dangerous. People really need to look at whats happening with 'adb' and have some idea of what adb is for. I did renamed your 'adbmac' to 'adb', then I could cut and paste from your instructions except for adding ./ before the adb... ie. ./adb shell
Again, wonderful work at pulling this all together in one place.
Jeff
This guide worked perfectly! I love a nice quiet clean root and it doesn't get any better than this. You my friend deserve a cookie!
Hi Guys,
I flashed to JMA, rooted it with One Click Root, and everxthing seemdet to be okay, but activating OCLF failed....is there anybody with the same problem?
Jan
Thanks a lot !. It's clean and doesn't need a kies ...
Just a question : after reboot I have to use "su" after "adb shell" to become root.
Is there any way to be root directly after adb shell ?
And thanks again ...
Mike
mbaroukh said:
Just a question : after reboot I have to use "su" after "adb shell" to become root.
Is there any way to be root directly after adb shell ?
Click to expand...
Click to collapse
The reason is that "/sbin/adbd" (the adb daemon) is running as the shell user. It would need to run as root user instead. This requires changes to the initial ram disk where adbd the relevant settings are stored.
Dealing with "insufficient permissions for device"
Thanks, this worked for me.
One small thing: running from a Linux sustem (Ubuntu 9.04), to overcome a "insufficient permissions for device" problem, I had to put my Ubuntu terminal session into su mode and restart the ADB server -- cf. groups.google.com /group/android-discuss/browse_thread/thread/f85a795644e65b59?pli=1 :
[[
adb kill-server
sudo adb start-server
adb devices
]]
gklyne said:
One small thing: running from a Linux sustem (Ubuntu 9.04), to overcome a "insufficient permissions for device" problem, I had to put my Ubuntu terminal session into su mode and restart the ADB server -- cf. groups.google.com /group/android-discuss/browse_thread/thread/f85a795644e65b59?pli=1 :
[[
adb kill-server
sudo adb start-server
adb devices
]]
Click to expand...
Click to collapse
Thanks for the feedback. On my Ubuntu 10.10 adb runs under my regular user-id (1000) and I do not have to use sudo or run the local adb server as root. That might be due to the way the udev rules are set up. Mine are rather unrestrictive and look like this:
Code:
$ cat /etc/udev/rules.d/51-android.rules
SUBSYSTEMS=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEMS=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
How do yours look like?
Which is the more simple method for root of galaxy tab euro ?are there ?
the incredible said:
Which is the more simple method for root of galaxy tab euro ?are there ?
Click to expand...
Click to collapse
Try z4root or SuperOneClick. Both methods are wrappers of the rageagainstthecage exploit and try to automate the manual process outlined here.
This thread should be a sticky. Worked like a charm.
z4root is very simple method..thanks.
thanks to Germany...
I agree, this thread should be sticky. Finaly some sense in android devel section...
Thank you very much for your guide!
I followed all the instructions in your guide, everything seems fine until I try to push the busybox and su to my Galaxy Tab.
blacklevel said:
Now we push busybox and su via adb. Then we install Superuser.apk.
Code:
> adb push busybox /system/bin
> adb push su /system/bin
> adb install Superuser.apk
[/update]
Click to expand...
Click to collapse
I received an error: "failed to copy 'busybox' to '/system/bin/busybox' : No space left on device\"
the same error for the 'su' too
(No space left on device) is impossible, my tab is brand new sealed when i got it.
I have been trying the z4root and SuperOneClick procedure to root this tab but are all unsuccessful.
I am not sure if it is because of my tab needed a "NAND unlock" (I cannot find any guide about the NAND unlock) because I received this message when I tried to install busybox from the market.
Please help! My tab is carrier locked to Bell Canada, I really wanna to unlock it and root it~
Thanks!
gummo6869 said:
I received an error: "failed to copy 'busybox' to '/system/bin/busybox' : No space left on device\"
the same error for the 'su' too,
Click to expand...
Click to collapse
The `no space left on device` message indicates that the /system partition is still read-only. That means the mount command in step 3 was unsuccessful. Did you get any error message when you executed it?
im trying to remove apps using adb but its not workin when i hit su// i dont get a screen on my epic.. but im able to hit adb shell and go into ls and see files .. im trying to remove sms app but its not letting me it says denied i also tryed to mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system but that doesnt work ... wat am i doing wrong
C:\Users\Home>cd c:\androidsdk\tools
c:\androidsdk\tools>adb shell
$ su
su
adb remount
adb remount
adb Permission denied
$ adb: not found
$ devices
adb devices
adb: not found
$ adb devices
adb devices
adb: not found
$ exit
exit
c:\androidsdk\tools>adb devices
List of devices attached
D7005e7accfe device
U need root + super user
I would recommend u use sdx app remover instead of adb
Its simpler and it backups ur app
Sent from my SPH-D700 using XDA Premium App
If you are rooted
Adb shell
Su
Remount system rw
Mv /system/app/mms.apk /sdcard/mms.apk
Sync
Reboot
That will move the stock mms app to the sdcard..
Sent from my SPH-D700 using XDA App
There is already an excellent write-up on how to use SuperOneClick to root your Optimus V.
Unfortunately, you may not have a Windows machine available to run the util, or your PC hates the LG drivers, or you may wish to control how you go about rooting your device.
Hence this short write-up which, obviously, relies on pieces I got from that other write-up.
I. Rooting your device
1. You still need ADB!
2. Download the LG Optimus V Tools package from http://nexus.zteo.com/projects/tools/
3. Unzip it
4. Command-line:
Code:
adb push psneuter /data/local/tmp/
adb push su /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 777 psneuter
chmod 777 su
./psneuter
5. You should be kicked out of the shell
6. Command-line:
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
cat /data/local/tmp/su > /system/bin/su
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
(Oh look you are root!)
That's it. You now have permanent root access.
After rebooting your phone, adb should be back to logging you in as a regular user but typing "su" will do the trick.
Note: I realize that the version of SuperUser.apk that comes with SuperOneClick might be re-usable here. I haven't had any success with it but you may.
II. Flashing a new ROM
1. After rooting your device, obviously...
2. Get an image for the ROM you wish to flash...
Currently, my favourite one is a fairly recent version of Zefie's CM7.
You can find it by googling "update-cm-7-04282011-NIGHTLY-thunderc-Xionia-signed.zip" -- I will refer to it, below, as <your_rom_zip_file>
3. Get a minimum Google Apps package for flashing as well.
Here, I would google "gapps-gb-20110325-signed.zip" -- I will refer to it, below, as <your_gapps_zip_file>
3. Command-line:
Code:
adb push flash_recovery /data/local/tmp/
adb push recovery.img /sdcard/
adb push Debug-FormatSYSTEM.zip /sdcard/
adb push <your_rom_zip_file> /sdcard/
adb push <your_gapps_zip_file> /sdcard/
adb shell
su
chmod 777 /data/local/tmp/flash_recovery
/data/local/tmp/flash_recovery /sdcard/recovery.img
reboot recovery
4. In recovery: Flash Debug-FormatSYSTEM.zip
5. In recovery: Wipe cache and dalvik-cache
6. In recovery: Flash <your_rom_zip_file> -- this will take a while
7. Do not reboot!
8. In recovery: Flash <your_gapps_zip_file>
9. Now, reboot.
10. Let your phone think about life for a few minutes
11. Select "Skip" when your phone asks you to create/enter your account info
12. Launch the market; now, enter your main account information
Hey first of all let me tell you that I appreciate this guide. Now my problem is that I am such a noob that I may be doing this wrong.I download the file to my optimus.Then in an explorer I extract it, correct? After that once I put in the first line of command on terminal emulator I get an error that says "adb: permission denied". Please help this guide is my last resort.Whatever I do I can not root through windows.It would be nice if you could explain in more detail every step. Thanks!
help
can u please add a little more detail thank u very much appreciated.
SouthParkFan15:
adb is a tool that you run on your computer; it is available for Windows, Mac OS X and Linux. It is part of the Google SDK.
thizizjohnny:
Could you give me a little more detail regarding what detail you are interested in?
How do I unzip?.. is extract the same thing? I'm running Linux mint 10. How do I get adb? Excuse my noobness.
Sent from my VM670 using XDA App
Oh and one last thing.. does this work on android version 2.2.1?
Sent from my VM670 using XDA App
Yes this works with 2.2.1.
On Linux Mint, you can use the package manager or the unzip command in a terminal window.
apk:
Download the SDK at http://developer.android.com/sdk/index.html
Install it, then run "android" and select "Install platform tools"
I finally got adb on my system, but when I type in "adb devices" nothing comes up and when I do any command that involves the phone i get "error:device not found".Yes I have usb debugging on and yes I have all the right drivers installed and yes I have tried rebooting a million times, and no my computer has never recognized my phone the way it should.Let me also point out that though pdanet or droid explorer they can't find my device. Help please I'm desperate!
Oh, my. Sorry to read that.
Problem is, in 2.2.x, the exploits that give you root access rely on ADB itself so you couldn't be more out of luck.
On second thought...this may seem a bit weird but there may be a way. I have to think about it. It would involve using a file manager that agrees to "see" /data/local/tmp, running psneuter from there and keeping our fingers crossed. I'll keep you updated.
Alright thanks cyansmoke! Keep me informed.
I ran all of the steps for rooting and I didn't get one error. It didn't seem to work though. When I launch adb again after rebooting my phone I get permission denied when I try to run su.
Here is the cap from my command line. I have no idea why it didn't take.
C:\phone\LGOptimusVTools>adb shell
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 777 psneuter
chmod 777 psneuter
$ chmod 777 su
chmod 777 su
$ ./psneuter
./psneuter
property service neutered.
killing adbd. (should restart in a second or two)
C:\phone\LGOptimusVTools>adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /data/local/tmp/su > /system/bin/su
cat /data/local/tmp/su > /system/bin/su
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
# exit
exit
C:\phone\LGOptimusVTools>adb shell
$ su
su
su: permission denied
$
It's possible that you have another su in your path that takes precedence.
Please try typing:
/system/bin/su
Hey, do you know if there is a way to upgrade my device to froyo 2.2.2? It's currently 2.2.1 and whenever I go to update system it says something like "Your system is up to date".Incase you have forgotten I have the optimus v that can't establish connections with the computer.So what I could do?I'm thinking that If I do that then maybe it could fix all of my problems (or some of them).Thanks
I don't think that it will help you no.
OK it's taking longer than I thought because my wife's LGV, after I restored it to stock, decided that it would not allow psneuter anymore.
Thus, I will need you to run these commands for me and let me know how that went:
1. First, copy psneuter to the root of your SD Card.
2. Then, download Terminal Emulator from the market
3. Run Terminal Emulator, type:
Code:
cp /sdcard/psneuter /data/local/tmp/
chmod 777 /data/local/tmp/psneuter
/data/local/tmp/psneuter
Now, if we are lucky, you should get kicked out of the terminal app (I know it's weird but there is a claim that it goes through adb(!))
Restart the terminal emulator. If we are double-lucky, your prompt should have changed from '$' to '#'
Fingers crossed. Still surprised to hear that terminal emulator would go through adb. No, let me rephrase that: I am moderately surprised, in fact, considering the limitations put on non-rooted apps.
After I put psneuter on the root of my sdcard.I go to terminal emulator and put in the first code and it says "cp: permission denied".Any suggestions?
SouthParkFan15 said:
After I put psneuter on the root of my sdcard.I go to terminal emulator and put in the first code and it says "cp: permission denied".Any suggestions?
Click to expand...
Click to collapse
Ah, my bad, no "cp" by default.
New instructions:
Code:
cat /sdcard/psneuter > /data/local/tmp/
chmod 777 /data/local/tmp/psneuter
/data/local/tmp/psneuter
After I put in the first code I get an error message saying "cannot create /data/local/tmp/: is a directory".
*facepalm*
Of course I should have written:
Code:
cat /sdcard/psneuter > /data/local/tmp/psneuter
I put in "cat /sdcard/psneuter > /data/local/tmp/psneuter" and I get an error message saying "cannot create /data/local/tmp/psneuter: directory nonexistent".
Any suggestions?
I thought I'd let folks know what I did in order to root on 8.5.1 and not have slowness. This isn't a complete walkthrough and assumes you have ADB drivers installed and working and access to ADB.
First I used the exploit found in this thread.
http://forum.xda-developers.com/showthread.php?t=2544736
I downloaded kindlehd2013_root.zip and also got the zip copy of superuser from
http://download.clockworkmod.com/superuser/superuser.zip
I extracted all to a folder. I then replaced the su from the kindlehd2013_root.zip with the superuser.zip armeabi folder version. Then you run the commands it has in the post.
adb push su /data/local/tmp/
adb push rootme.sh /data/local/tmp/
adb push exploit /data/local/tmp/
adb shell chmod 755 /data/local/tmp/rootme.sh
adb shell chmod 755 /data/local/tmp/exploit
Before I ran this last line I made sure su had the correct permissions:
type adb shell:
then ran the command
chmod 6755 /data/local/tmp/su
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
now you can get root via ADB by going into
adb shell
then run the command su
from there I made sure the su had the correct permissions again in the new location:
mount -o remount,rw /system
I had a complaint about space so I just removed the officesuite.apk in /system/apps to the sdcard
chown 0:0 /system/xbin/su
chmod 6755 /system/xbin/su
Then using the superuser.apk from the zip installed it.
adb install superuser.apk
Hope this helps others have success. From here you can follow the tutorials to get Google apps and such. I'd love to run an alternative ROM but have the LTE version and haven't been able to find one that has working LTE.
Hi Macman005!!
I want to use your method to root my Hd 8.9, I dont want too install a room, only install google services to use my chromecast. But before I want to Know:
How I move the officesuite.apk in /system/apps to the sdcard, if I have the space complaint you had?
I really appreciate any help you can provide
jaramosparra said:
Hi Macman005!!
I want to use your method to root my Hd 8.9, I dont want too install a room, only install google services to use my chromecast. But before I want to Know:
How I move the officesuite.apk in /system/apps to the sdcard, if I have the space complaint you had?
I really appreciate any help you can provide
Click to expand...
Click to collapse
On device you can use es file explorer -> enable root explorer from the left side the click on root explorer -> mount r/w -> then make sure /system is rw
Via ADB
adb pull /system/app/OfficeSuite.apk
adb shell
su for root
mount -o remount,rw /system
rm /system/app/OfficeSuite.apk
Hi Macman005
I had follow your instructions and I had manage to root my hd 8.9, total success!!!
Thanks!!
hi there folks,
so i've read through a bunch of guides and steps to accompish getting root on a kindle fire hd 8.9 running 8.5.1
i followed your above steps to the T but everytime i try and execute the exploit i get a error like this
***********
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x80008000 form iomem
Attempt put_user exploit...
write: No space left on device
************
i read further into this post and in others that moving files around was the answer but i'm unable to move the files using
Code:
./adb shell
mv /system/OfficeSuite.apk /sdcard
i get a error like "failed cross device link"
so i'm guessing i'll only have access after rooting to move or delete files in /system
************
Code:
$ df
Filesystem Size Used Free Blksize
/dev 383M 32K 383M 4096
/mnt/asec 383M 0K 383M 4096
/mnt/obb 383M 0K 383M 4096
/system 872M 872M 0K 4096
/data 13G 372M 12G 4096
/cache 639M 10M 628M 4096
/efs 15M 4M 11M 4096
/mnt/sdcard 13G 372M 12G 4096
[email protected]:/system/app $
*********
any suggestions tips or links would be appreciated
Use adb pull to get the file out of /system/app then just try to delete it. I'm guessing it won't work though without root.
Did you check to see if su was in the /system/xbin/su dir?
macman005 said:
Use adb pull to get the file out of /system/app then just try to delete it. I'm guessing it won't work though without root.
Did you check to see if su was in the /system/xbin/su dir?
Click to expand...
Click to collapse
already tried rm -rf OfficeSuit.apk
pulling it leaves the file inplace
su is in place in xbin
Code:
[email protected]:/ $ cd /system/xbin/
[email protected]:/system/xbin $ ll
-rwxr-xr-x root shell 59392 2008-08-01 12:00 dexdump
-rwxr-xr-x root shell 63448 2008-08-01 12:00 hciconfig
-rwxr-xr-x root shell 36776 2008-08-01 12:00 hcitool
-rwxr-xr-x root shell 5608 2008-08-01 12:00 hdcp-test
-rwsr-sr-x root root 94208 2014-11-19 22:25 su
127|[email protected]:/sdcard $ su --help
Segmentation fault
139|[email protected]:/sdcard $ su touch test
Segmentation fault
139|[email protected]:/sdcard $ su
Segmentation fault
139|[email protected]:/sdcard $
i've tried tinkering with permissions with no luck
i'm not worried about root on the kindle os, i mostly want to stick CM11 on it - i recall reading a article on cyanogenmod's page about flashing the CM11 rom on the kindle it didn't mention that root was required i just kind of assumed it was to be able to install a second bootloader etc
If you don't need to follow my root you just use this tutorial. The root being slow isn't a big deal since you'll replace it with cm11
http://forum.xda-developers.com/showthread.php?t=2789289
macman005 said:
If you don't need to follow my root you just use this tutorial. The root being slow isn't a big deal since you'll replace it with cm11
http://forum.xda-developers.com/showthread.php?t=2789289
Click to expand...
Click to collapse
sweet thanks for the tip - i'll give this one a try (i'd tried a couple other methods with no success)
Everything good for me until:
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
Then I get:
Code:
Device detected: KFJWI (IMM76D)
Attempt acdb exploit...
KFJWI (IMM76D) is not supported.
Attempt fj_hdcp exploit...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x80008000 form iomem
Attempt put_user exploit...
After that nothing works. Any ideas where i might have taken the wrong turn?
Do you have su in the /system/xbin folder?
macman005 said:
Do you have su in the /system/xbin folder?
Click to expand...
Click to collapse
Thanks for reply macman.
I gave up... Followed the instructions you gave and all seemed well until step: adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
So not sure but will check when I can try again. Would love to totally clean out amazon junk and turn into android pad.
Im having the same problem as Justanumber, and I'm not sure if I have the su in the /system/xbin folder
I was able to root 8.5.1. What I did was try the Bin4ry method, first option 1, when that didn't work option 2. It made my kindle run slow and was almost unusable. Being very patient due to the slowness, I tried the QEMU method. It seems like some things transferred to the kindle and others didn't and I got an error. I then went back to Bin4ry and ran unroot and got an error. The last thing I tried was to run root option 2 once more and success. I then went right to Hashcodes post and installed a second bootloader and cm11. I'm not a developer so I put everything I did. Maybe someone who knows what they are doing can figure out what is needed from all that. Whatever I did though, I got for on 8.5.1 without any issues once it went through
Sent from my HTC6525LVW using XDA Premium 4 mobile app
worked perfectly for me on 8.5.1, always a bit nervous messing with the kindle but no problems . Big thanks to the op. I didn't have any complaints about space, and there was none of the slowdown problems so many people complain about after rooting the new firmware. Now i have installed hashcode's cm12 port and its like a brand new gadget...
I got as far as "adb shell", but the su command returns "permission denied"
What exactly do you mean when you say "check su permissions." First time using ADB.
please help me
macman005 said:
I thought I'd let folks know what I did in order to root on 8.5.1 and not have slowness. This isn't a complete walkthrough and assumes you have ADB drivers installed and working and access to ADB.
First I used the exploit found in this thread.
http://forum.xda-developers.com/showthread.php?t=2544736
I downloaded kindlehd2013_root.zip and also got the zip copy of superuser from
http://download.clockworkmod.com/superuser/superuser.zip
I extracted all to a folder. I then replaced the su from the kindlehd2013_root.zip with the superuser.zip armeabi folder version. Then you run the commands it has in the post.
adb push su /data/local/tmp/
adb push rootme.sh /data/local/tmp/
adb push exploit /data/local/tmp/
adb shell chmod 755 /data/local/tmp/rootme.sh
adb shell chmod 755 /data/local/tmp/exploit
Before I ran this last line I made sure su had the correct permissions:
type adb shell:
then ran the command
chmod 6755 /data/local/tmp/su
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
now you can get root via ADB by going into
adb shell
then run the command su
from there I made sure the su had the correct permissions again in the new location:
mount -o remount,rw /system
I had a complaint about space so I just removed the officesuite.apk in /system/apps to the sdcard
chown 0:0 /system/xbin/su
chmod 6755 /system/xbin/su
Then using the superuser.apk from the zip installed it.
adb install superuser.apk
Hope this helps others have success. From here you can follow the tutorials to get Google apps and such. I'd love to run an alternative ROM but have the LTE version and haven't been able to find one that has working LTE.
Click to expand...
Click to collapse
Please help sir can you do a video of it on how to root the version 8.5.1 cause I cnt follow hard instruction pls lemme see
macman005 said:
Do you have su in the /system/xbin folder?
Click to expand...
Click to collapse
Could you specify a little on how to find this out?
I'm also getting stuck after:
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
"Attempt acdb explot...
KFJWI <IMM76D> is not supported.
Attempt fj_hdcp exploit...
Attempt msm-cameraconfic exploit...
Detected kernel physical address at 0x80008000 from iomem
Attempt put_user exploit...
Thanks
macman005 said:
I thought I'd let folks know what I did in order to root on 8.5.1 and not have slowness. This isn't a complete walkthrough and assumes you have ADB drivers installed and working and access to ADB.
First I used the exploit found in this thread.
http://forum.xda-developers.com/showthread.php?t=2544736
I downloaded kindlehd2013_root.zip and also got the zip copy of superuser from
http://download.clockworkmod.com/superuser/superuser.zip
I extracted all to a folder. I then replaced the su from the kindlehd2013_root.zip with the superuser.zip armeabi folder version. Then you run the commands it has in the post.
adb push su /data/local/tmp/
adb push rootme.sh /data/local/tmp/
adb push exploit /data/local/tmp/
adb shell chmod 755 /data/local/tmp/rootme.sh
adb shell chmod 755 /data/local/tmp/exploit
Before I ran this last line I made sure su had the correct permissions:
type adb shell:
then ran the command
chmod 6755 /data/local/tmp/su
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
now you can get root via ADB by going into
adb shell
then run the command su
from there I made sure the su had the correct permissions again in the new location:
mount -o remount,rw /system
I had a complaint about space so I just removed the officesuite.apk in /system/apps to the sdcard
chown 0:0 /system/xbin/su
chmod 6755 /system/xbin/su
Then using the superuser.apk from the zip installed it.
adb install superuser.apk
Hope this helps others have success. From here you can follow the tutorials to get Google apps and such. I'd love to run an alternative ROM but have the LTE version and haven't been able to find one that has working LTE.
Click to expand...
Click to collapse
I'm pretty proficient with ADB, so your steps were easy to follow. Now I have a rooted Kindle Fire HD 8.9 on 8.5.1.
Thank you
Hello,
I'm following these instructions. When I run su, i get "Permission Denied."
Any ideas? The steps before seem to run fine.
When i run the exploit, i see the follwing:
Device detected: KFJWI (IMM76D)
Attempt acdb exploit...
KFJWI (IMM76D) is not supported.
Attempt fj_hdcp exploit...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x80008000 form iomem
Attempt put_user exploit...
---------- Post added at 04:27 PM ---------- Previous post was at 03:48 PM ----------
I got it to work.
I enterd adb shell, then exploit again, without the rootme.sh argument.
Then su worked and I was able to get everything to run
Thanks for the instructions!