Database Develop

[Q] busybox and nandroid issues

I have been experimenting with my new droid/milestone the past couple of days, odd problems which I am past now but still curious about.
Firstly after flashing the 2.1 sbf with rsd it will autoboot and screen slider will be there, then when I reboot, screen slider will be missing. This only happend when I flashed an sbf from the sbf site(2.1 uk version, not service), doing a factory reset didn't have any problem -could reboot as many times and slider would be there.... then suddenly after factory boot it would dissapear after first boot. Anyway solved this problem by installing screen mode widget after first boot after flash, solved problem, but still weird. Fixed this now but still curious about it.
Next, nandroid backup is missing from recovery menu, I have rooted and can execute root commands after typing "su" via Android Terminal emulator, so pretty sure is rooted. So why no nandroid? I thought I could do nandroid backup after rooting.
Next busybox won't install, tried the app, did the "searching system" for over an hour(not exagerrating), eventually gave up and uninstalled.
Trying to do a "manual busybox install" now, using this guide:
Busybox How-to? - Android Forums
Can't execute commands via usb/adb in recovery mode as the other guy suggested so been trying these commands both with terminal emulator on phone, and usb-debugging mode with windows shell. Using these I can go "su" and type "ls" to see files on my droid phone....but when I try to "mount /system" or /sdcard from windows I just get a print about mount options, when I try to "cat /sdcard/busybox > /system/xbin/busybox" I get a "file is read only" error.
I would like advice on how to install busybox, I would like to do it manually(because the app seems to not work for me, remember I waited over an hour while it "searched") and I want to learn to manually do stuff anyway. I tried to chmod /system/xbin too, but that didn't seem to change it from read only.
Also any thoughts on why nandroid backup is missing from my recovery menu even though my droid is rooted. I thought it was meant to appear.
I am still learning and researching, and appreciate any links or tips.

droidtech1 said:
Next, nandroid backup is missing from recovery menu, I have rooted and can execute root commands after typing "su" via Android Terminal emulator, so pretty sure is rooted. So why no nandroid? I thought I could do nandroid backup after rooting.
Click to expand...
Click to collapse
This is odd. Which OpenRecovery did you install? Androidiani? GOT? Or the "original" OpenRecovery? Are you aware, that you come into OpenRecovery by starting Recovery Mode and apply update.zip?
droidtech1 said:
Next busybox won't install, tried the app, did the "searching system" for over an hour(not exagerrating), eventually gave up and uninstalled.
Trying to do a "manual busybox install" now, using this guide:
Busybox How-to? - Android Forums
Click to expand...
Click to collapse
Using the app from the market worked like a charm for me. No idea, what might have gone wrong for you...
droidtech1 said:
Can't execute commands via usb/adb in recovery mode as the other guy suggested so been trying these commands both with terminal emulator on phone, and usb-debugging mode with windows shell. Using these I can go "su" and type "ls" to see files on my droid phone....but when I try to "mount /system" or /sdcard from windows I just get a print about mount options, when I try to "cat /sdcard/busybox > /system/xbin/busybox" I get a "file is read only" error.
Click to expand...
Click to collapse
For remounting, try "mount -o rw,remount /dev/block/mtdblock6 /system" and for undoing this, use "ro" instead of "rw".
droidtech1 said:
I would like advice on how to install busybox, I would like to do it manually(because the app seems to not work for me, remember I waited over an hour while it "searched") and I want to learn to manually do stuff anyway. I tried to chmod /system/xbin too, but that didn't seem to change it from read only.
Click to expand...
Click to collapse
You should download busybox and put the "busybox"-file in the directory /sdcard. After that do:
Code:
# su
# mount -o rw,remount /dev/block/mtdblock6 /system
# cp /sdcard/busybox /system/xbin
# cd /system/xbin
# chmod 755 busybox
# ./busybox --install
# mount -o ro,remount /dev/block/mtdblock6 /system
One thought at the end: How did you root?

I rooted by flashing "vunerable recovery" using RSD lite, copied milestone-root.zip to sd card, renamed it update.zip, rebooted into recovery mode, flashed update.zip from there.
I didn't realise I had to install something like open recovery, think because I remember not having to do that on my pulse? Anyway will try and install one of those now.
Thanks those commands at the end helped, actually managed to copy busybox to /system/xbin, however the 2nd last one "./busybox --install" gave me a load of errors -all being no such file or directory, for example "/usr/bin/wc: no such file"
about 30 of those path errors. Maybe the command path "./busybox" needs to be something else?

ah, okay. sorry, I thought you already installed an openrecovery. for many cool features you will need it (e.g. nandroid, for overclocking it's not a must but a nice-to-have). please don't use GOT, it's rather old already. androidiani is okay, I think.
I think your previous attempts to install busybox via the app etc. mixed up some internal links in the device. please reboot and try again (the above steps except the "cp ..."). seems like the app tried to install busybox to /usr/bin but failed... I hope this failed attempt will be fixed by a simple reboot. otherwise it would be great to have the output of:
Code:
# su
# ls /usr/bin

No I re-flashed my main sbf and also did a factory reset to do a clean start, only thing since that full wipe I have done is rooting in the method I described, installed the screenmode widget, textedit, and android terminal emulator.
I have no such file /usr, are you sure I should have this in droid/milestone?
Here is my full output of my root system using ls:
tmp
pds
cdrom
sqlite_stmt_journals
config
cache
sdcard
d
etc
system
sys
sbin
proc
init_prep_keypad.sh
init.rc
init.mapphone_umts.rc
init.mapphone_cdma.rc
init.goldfish.rc
init
default.prop
data
root
dev
perhaps "/usr" is a sub inside one of the above folders? I tried using "find" to find it but that command dosn't seem to work since it won't even find the ones I can see with ls

I found it, /usr is inside /system... so if busybox was moved to /system/xbin, I'm guessing the ./ means install it to the parent directory which was /system which /usr is also in.
The errors I got said no such file "/usr" so It seems like it is trying to install to the wrong directory.... perhaps the command should be "busybox --install" or "/busybox --install" I don't want to experiment and mess things up before your opinion on this.
*edit almost forgot, output of /system/usr is
keychars
bin
srec
keylayout
share
output of /system/usr/bin is
panic_daemon
gki_pd_notifier
nvm_daemon
clean_dex.sh
brcm_guci_drv
bplogd_daemon

This is really strange. Maybe your busybox-file is corrupt.
Where did you download the busybox-file?
Which sbf did you flash?
So for explanation-purposes: When you put an executable or script file in any directory, you can execute it by first making it executable ("chmod 755 /system/xbin/busybox"), changing to that directory ("cd /system/xbin") and then executing it by adding "./" in front of it. The dot slash always stands for the _current_ directory. The _parent_directory has two dots "../".
If you want, you may try:
# /system/xbin/busybox --install
instead of
# ./busybox --install
Or maybe try this one:
# /system/xbin/busybox --install -s /system/xbin
Last time, I installed busybox into the directory /data/busybox, which worked brilliantly, but this path turned out to be unpractical. So I wanted to reinstall it in a different directory. I removed everything from /data/busybox including the directory itself and tried to start the whole procedure with /system/xbin. But that time it protested, that there were no files in "/data/busybox/...". Conclusion: The last busybox-install affected the second one. When I remember correctly I rebooted after that and used the app from the market *g*

My main sbf I flashed was android 2.1(uk version).
I downloaded busybox 1.17.2(won't let me post url here), was from droidforums dot net.
I don't remember if I tried all of his commands, but the last one on that forum seems to have worked.. I think......... it was:
"busybox --install /system/xbin/"
After remounting with your commands and typing the above command, I didn't get any errors, I synced and rebooted and now when I "ls /system/xbin" it shows a bunch of files/names which look like busybox commands. When I type "busybox" it outputs a bunch of commands too... so I am guessing this means it has succesfully installed? I can't say I tried these before attempting install so I have no comparison but I assume I would have a different output if busybox wasn't installed.
So assuming it worked, why would
"busybox --install /system/xbin/" work, and
"/system/xbin/busybox --install" not?
I also managed to install open recovery and do a nandroid backup succesfully
I have another short question, not specific to android but happens in all terminals I use, windows and linux alike. Sometimes I cannot execute commands anymore and it just becomes text in the terminal(just re-echo'ing my text output, without executing any functions)... can't remember specifically when it happened on my windows or linux pc shells, but on my android it happens whenever I have to give "SU" permission to the terminal, I have to quickly close the terminal and reload it again to get su access. I'm sure there is a name for this "state" where you are locked out of using commands in the shell and just typing text but I can't find a way to get out of it(without closing and re-opening terminal), there must be some key combination to be able to execute commands again in the current terminal session. If you have any idea what I am talking about?
Thanks for all your help so far.

droidtech1 said:
My main sbf I flashed was android 2.1(uk version).
Click to expand...
Click to collapse
Don't want to try one of the 2.2?
droidtech1 said:
I downloaded busybox 1.17.2(won't let me post url here), was from droidforums dot net.
I don't remember if I tried all of his commands, but the last one on that forum seems to have worked.. I think......... it was:
"busybox --install /system/xbin/"
After remounting with your commands and typing the above command, I didn't get any errors, I synced and rebooted and now when I "ls /system/xbin" it shows a bunch of files/names which look like busybox commands. When I type "busybox" it outputs a bunch of commands too... so I am guessing this means it has succesfully installed? I can't say I tried these before attempting install so I have no comparison but I assume I would have a different output if busybox wasn't installed.
Click to expand...
Click to collapse
Yes, this sounds very much like installation was successful.
droidtech1 said:
So assuming it worked, why would
"busybox --install /system/xbin/" work, and
"/system/xbin/busybox --install" not?
Click to expand...
Click to collapse
typing "busybox" without the path in front of it worked, because busybox is in the directory /system/xbin, which is already in your $PATH-variable (try "echo $PATH"). So the command interpreter (shell) will automatically look up "busybox" in /system/xbin.
I had a look at the busybox syntax and it's actually
Code:
busybox --install [-s] [INSTALLDIR]
So you have to put the directory you want to install in at the end. That's what your last command makes use of
droidtech1 said:
I have another short question, not specific to android but happens in all terminals I use, windows and linux alike. Sometimes I cannot execute commands anymore and it just becomes text in the terminal(just re-echo'ing my text output, without executing any functions)... can't remember specifically when it happened on my windows or linux pc shells, but on my android it happens whenever I have to give "SU" permission to the terminal, I have to quickly close the terminal and reload it again to get su access. I'm sure there is a name for this "state" where you are locked out of using commands in the shell and just typing text but I can't find a way to get out of it(without closing and re-opening terminal), there must be some key combination to be able to execute commands again in the current terminal session. If you have any idea what I am talking about?
Click to expand...
Click to collapse
Sounds like this is just the state, when shell is busy, i.e. when the last process you started is still running and no prompt ($ or #) is displayed. You may kill the last process in linux using CTRL+C, which will hopefully bring back the shell prompt. No idea which shortcut replaces this on the milestone/droid. I never use any android terminals, but only the ADB-Shell: http://developer.android.com/guide/developing/tools/adb.html

I'm learning to build apps for android so I thought having 2.1 on my droid would be better for testing (instead of 2.2). I also have a Nexus-S with 2.3 and a tmobile-pulse with 1.5. So I want to keep the most native version on each phone since most consumers won't install custom roms, although some will get updates anyway.
I use my droid a lot when I am out and use the terminal a lot so having busybox too has given me more to play around with. I actually find my droid much better working on than the nexus s, love the keyboard and dpad.

Droid root issues: update.zip successful but no root

I've been trying to figure this out all day and I'm stumped.
My stock Droid recently failed to get past the bootloader.
I'm following the directions from the CM Wiki titled "Motorola Droid: Full Update Guide" (no direct link because of my new account, sorry) and others I've found and they all seem to be exactly the same.
I've got SPRecovery installed no problem and after I run the update.zip I get a successful install message, including "enjoy your root".
The problem is in the next step where I ADB it doesn't appear I actually have root access.
I think this may be because I'm connecting to my phone from the SPRecovery menu, but I'm not sure.
This is what my cmd screen looks like when I try to follow the steps under "Installing ClockworkMod Recovery" > "Second Method (manual method)".
Code:
C:\Users\XXXX>adb shell
/ # su
su
/system/bin/sh: su: not found
I noticed that in SPRecovery there are "mount options", so I tried mounting /system and trying again and I get basically the same thing, but without the "/" and without the directory
Code:
C:\Users\XXXX>adb shell
# su
su
su: not found
I'm not Linux savvy enough to know the difference unfortunately. I've tried 3 different update.zip from 3 different sources, but all appear to be the exact same thing.
Typing "busybox" in the ADB shell kicks back all the functions so it appears to be installed.
"adb devices" kicks back "040388990E0EDITED recovery"
Any ideas would be greatly appreciated, it's getting very frustrating.

Do you have the opportunity to root your phone from the Recovery-Menu?
I have OpenRecovery (OR) and when I boot in OR i can manually chose to root my phone.

----wrong----

Quinity said:
You can also simply download the SuperUser App from the market. This roots your phone.
Click to expand...
Click to collapse
I'm about 99% certain that is false. If it was that easy, I would have heard about it. Plus the only SU app on the market states " Grant and manage Superuser rights for your phone. This app requires that you already have root.."

HELP!!!! trying Install CWM on zv8

Ok so here it is almost day 2 trying to install CWM on zv8 after using "mt's easiest way to keep root thru zv8'. (Oh and by the way MT your the MAN). Now getting to zv8 was easy, But getting the recovery installed is another issue all together. First started with the AIO bat. file which installs cwm (kudos to MT and djrbliss). And it reads
"system cannot find the path specified'.
SO ok well apparently the computer isnt reading the phone found out the driver has issue shows the error message(on both my laptops).
ok lets try the terminal emulator with
brad6360 said:
1) Download the cwmrecovery.img to your SD. ( I downloaded MT's zip file and then extracted all with root explorer, but you only need the cwmrecovery.img file.)
2) Use root explorer to copy or move it to the /data/local/tmp directory (make sure permissions are set to r/w/exe).
3) Launch terminal emulator and type these commands:
su
mount -orw,remount /dev/block/system /system
mount -orw,remount /dev/block/data /data
dd if=/data/local/tmp/cwmrecovery.img of=/dev/block/mmcblk0p14 bs=4096
rm /data/local/tmp/* 2>/dev/null
4) exit terminal emulator and then reboot.
You can then try the vol down+power button combo upon boot to enter CWM.
Good luck.
Click to expand...
Click to collapse
didn't work and I the local.prop file in the data folder.
Someone PLEASE HELP!!!
(not a noob or expert but I can read and follow directions lol)

Are you sure you still have root level access?
Does adb detect your phone at all?

Still have root access I used root explorer to add the local.prop.
Adb recognizes my phone it shows a serial number under adb devices
Is there a way I can flash cwm in adb?
Sent from my VS910 4G using XDA

Use the newest aio from Mt. It worked for me. The simplest way is to flash the v7.tot then 'JUST' root, create the local.prop file, then ota to v8. Then continue on with Mt's aio to install cwm. Don't worry about having complete root access (cuz I didn't, but had cwm). Flashed broken out and haven't looked back.
--My REVO is Broken, tweaked, SC'd, and TB'd. Just awesome!

Thats where I'm stuck. I'm on zv8, using mt's easiest AIO to update from zv7. The AIO for cwm isn't installing nor through the terminal emulator. Any other suggestions?
Sent from my VS910 4G using XDA

What happens when you go into recovery? Is it the stock recovery? Stock v8 didn't have the option to boot into recovery. Just a thought. When I did it I got a lot of errors, but it took.
--My REVO is Broken, tweaked, SC'd, and TB'd. Just awesome!

mrand1 said:
Thats where I'm stuck. I'm on zv8, using mt's easiest AIO to update from zv7. The AIO for cwm isn't installing nor through the terminal emulator. Any other suggestions?
Sent from my VS910 4G using XDA
Click to expand...
Click to collapse
I have the same problem, Even when i Flash zv7 tot and try old AIO it says
Cannot find specified path
and i am not a noob and have broken out an old revo with mt's help but this new one with pre loaded zv8...No luck yet
had to manually push

I'm glad that I'm not the only one having this issue

Can you use Root Explorer to check and make sure adb is pushing the image file to your phone? Look in this directory: /data/local/tmp/cwmrecovery.img
You could always do this manually using adb. Here's how.
1. Open the ZV8CWMRecovery folder on your PC.
2. Double click the 'Files' folder to go into that directory.
3. Highlight/select and copy the address of your current folder location on your PC. It will look something like this:
Code:
C:\Documents and Settings\username\My Documents\Downloads\ZV8CWMRecovery\Files
4. Click Start>Run>type 'cmd' and hit enter/return to open your command prompt.
5. Type 'cd', hit your spacebar, then paste your address which you copied in step 3 into your command prompt, hit enter/return.
6. You should now be positioned in the folder containing the adb and CWMRecovery files.
7. Type the following to copy the CWMRecovery image to your phone:
Code:
adb devices
adb remount
adb push cwmrecovery.img /data/local/tmp/cwmrecovery.img
adb shell dd if=/data/local/tmp/cwmrecovery.img of=/dev/block/mmcblk0p14 bs=4096
adb shell "rm /data/local/tmp/* 2>/dev/null"
adb shell rm /system/etc/install-recovery.sh
adb shell rm /system/recovery-from-boot.p
adb shell rm /data/local.prop
adb reboot
Phone should reboot. Try and boot into CWMRecovery after it reboots.

idk if I'm not doing something right or wrong. I have usb debugging and internet connection, and I'm getting "remount failed: operation not permitted".

I had the same issue but following these instructions helped me, what finally helped me was typing a wrong command wich gave me a help menu with all the commands, the important one being "adb reboot [Recovery:Bootlaoder]"
adb reboot recovery did the trick, then wiped flashed broken out and sooo happy to be done with it.
after pushing CWM in command prompt of course

I'm also getting "remount failed: operation not permitted" when trying adb remount in the command prompt just as mrand1 apparently did.
I (perhaps noobishly) skipped that step and did adb push cwmrecovery.img /data/local/tmp/cwmrecovery.img but after trying the next step got cannot open for write: Permission denied.
I'm trying to get back to Broken Out 1.1 - when it first came out I successfully downgraded to zv7 by flashing the .tot and then doing the OTA update, but now when I try to do that I can't seem to get the OTA to start downloading. I flashed zv8 tot in order to test the latest root method (which works) I just can't get CWM on there now - I don't seem to have any recovery at all actually. Any help would be appreciated.

slimzim said:
I'm also getting "remount failed: operation not permitted" when trying adb remount in the command prompt just as mrand1 apparently did.
I (perhaps noobishly) skipped that step and did adb push cwmrecovery.img /data/local/tmp/cwmrecovery.img but after trying the next step got cannot open for write: Permission denied.
I'm trying to get back to Broken Out 1.1 - when it first came out I successfully downgraded to zv7 by flashing the .tot and then doing the OTA update, but now when I try to do that I can't seem to get the OTA to start downloading. I flashed zv8 tot in order to test the latest root method (which works) I just can't get CWM on there now - I don't seem to have any recovery at all actually. Any help would be appreciated.
Click to expand...
Click to collapse
I did the same thing, flashed to zv8 tot, was able to root but was unable to flash cwm recovery. I tried manually doing it and running MT's AIO. It's telling me permission denied on all of the steps except the push cwmrecovery.img. It appears I do not have any recovery either. Trying to get to Broken Out! Any help is appreciated, thanks guys!

asauber said:
I tried ... running MT's AIO. It's telling me permission denied on all of the steps except the push cwmrecovery.img.
Click to expand...
Click to collapse
For what it's worth I also tried that with the same results.

I finally got this to work much more easily thanks to a quick talk with mtmichaelson. Here's the method:
1) Get to ZV8 (I got there via LGNPST)
2) Root using the tool found here: http://forum.xda-developers.com/showthread.php?t=1621625
3) Open a Terminal Emulator
4) Type: su
5) Hit enter
6) Type: echo 'ro.kernel.qemu=1' > /data/local.prop
7) Press enter
8) Reboot
9) Use the ZV8CWMRecovery.bat found here: http://forum.xda-developers.com/showthread.php?t=1583023
Good luck!

slimzim said:
I finally got this to work much more easily thanks to a quick talk with mtmichaelson. Here's the method:
1) Get to ZV8 (I got there via LGNPST)
2) Root using the tool found here: http://forum.xda-developers.com/showthread.php?t=1621625
3) Open a Terminal Emulator
4) Type: su
5) Hit enter
6) Type: echo 'ro.kernel.qemu=1' > /data/local.prop
7) Press enter
8) Reboot
9) Use the ZV8CWMRecovery.bat found here: http://forum.xda-developers.com/showthread.php?t=1583023
Good luck!
Click to expand...
Click to collapse
Man, that was too easy!
Thanks for posting this slimzim. This worked straight away for me, I'm installing Broken Out as I type! I'm actually a little glad this happened because now I'm a little more familiar with terminal emulator and what local.prop does. Never had to use it in the past. This is exactly the second phone I've ever rooted and am usually able to just use AIOs.
And of course, thanks to mtmichaelson for chatting with you about it and doing all the hard work in the first place!

slimzim said:
I finally got this to work much more easily thanks to a quick talk with mtmichaelson. Here's the method:
1) Get to ZV8 (I got there via LGNPST)
2) Root using the tool found here: http://forum.xda-developers.com/showthread.php?t=1621625
3) Open a Terminal Emulator
4) Type: su
5) Hit enter
6) Type: echo 'ro.kernel.qemu=1' > /data/local.prop
7) Press enter
8) Reboot
9) Use the ZV8CWMRecovery.bat found here: http://forum.xda-developers.com/showthread.php?t=1583023
Good luck!
Click to expand...
Click to collapse
So far not working...repeating process now...

da_morales said:
So far not working...repeating process now...
Click to expand...
Click to collapse
If you've done all steps exactly it should work. I went through a ton of other "fixes" that didn't work, I believe the key here is when you use the terminal emulator directly on the phone to create local.prop. I was trying to create local.prop in every way but that, and until I did it directly on the phone did I have success.
Good luck!

local.prop missing
I used the Easy ZV8 All in One Rooting Tool, and have no sound at all like a couple of other users. One of the suggestions was to rename the local.prop file in the /data folder to local.prop.bak.
I assume this is the /data folder in the internal folder? When I did the steps for the all in one rooting tool (coming from rooted zv7), there is no local.prop file in my /data folder to rename, yet I still have no audio for ringtones, phone calls, etc. except for the boot up sound on the splash page.
Any ideas why my local.prop file isn't even there? I even tried copying the one from the mtmichelson zip file into there, still no avail. Thanks!

I have the same issue. I used the echo command in term emulator and the local.prop file was there. rebooted and the file is gone. I have root but cannot install cw recovery. I have tried AIO, adb, and terminal emulator but nothing makes it stick. Any help would be greatly appreciated
Rob

Root/Android JB Kindle fire 10.2.3

So for the last 7 hours i've been researching how to root/ install JB or another rom onto this brand new kindle i have running 10.2.3.
I've got ADB running and i've tried Sparkym3 and a few other root methods and i keep getting permission denied when i go to write fbmode or su
SO i'm at a loss, i'd really like to get this installed and working for my handicapped father's new kindle, its his xmas gift, and i know i'd prefer he be able to use google play and stuff.
Any help would be fantastic, this is really rattling my brain.

Unfortunately, you're out of luck with a custom ROM/Jelly Bean, but you can gain access to the play store and lose the ads with root. I tried the automated method in the link below with no success. The qemu tool just quit after step two.
Is this the method you tried?
http://forum.xda-developers.com/showthread.php?t=1893838
I just followed this video to the letter, and I was golden. HOWEVER, I was on 10.2.1. I don't know if it will work with .3. Keep me posted because my other daughter's KF2 received the update before I attempted root, and I haven't attempted root on it yet . I renamed the otacert.zip file to prevent the update on the alreay-rooted tablet.
http://forum.xda-developers.com/showthread.php?t=1891939

scubamike said:
Unfortunately, you're out of luck with a custom ROM/Jelly Bean, but you can gain access to the play store and lose the ads with root. I tried the automated method in the link below with no success. The qemu tool just quit after step two.
Is this the method you tried?
http://forum.xda-developers.com/showthread.php?t=1893838
I just followed this video to the letter, and I was golden. HOWEVER, I was on 10.2.1. I don't know if it will work with .3. Keep me posted because my other daughter's KF2 received the update before I attempted root, and I haven't attempted root on it yet . I renamed the otacert.zip file to prevent the update on the alreay-rooted tablet.
http://forum.xda-developers.com/showthread.php?t=1891939
Click to expand...
Click to collapse
The commands:
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
abd reboot
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
adb install Superuser.apk
^^^ Method i tried, and failed, wont allow remount, gives me permission denied, i didnt try Qemu at all.
If i could get access to play store i'd be fine keeping it on stock, i just want my dad to be able to use this thing with standard apps.
I think this method is strictly for the kindle fire HD and i'm trying to do it on a standard Kindle Fire.

Hi there,
I,ve got the same issue with my brand new KF Gen2 FW 10.2.3. During the 1st run everythings seems fine (all commands were accepted),
but in the end I was not able to get root access by the superuser-app.
After that I decided to reset the device to factory defaults, but now I'm not able to create any file under /data (echo 'ro.kernel.qemu=1' > /data/local.prop).
Has anyone a good idea which way we have to choose to get root access on the KF2 (FW10.2.3)?
Thanks yanzz

yanzz said:
Hi there,
I,ve got the same issue with my brand new KF Gen2 FW 10.2.3. During the 1st run everythings seems fine (all commands were accepted),
but in the end I was not able to get root access by the superuser-app.
After that I decided to reset the device to factory defaults, but now I'm not able to create any file under /data (echo 'ro.kernel.qemu=1' > /data/local.prop).
Has anyone a good idea which way we have to choose to get root access on the KF2 (FW10.2.3)?
Thanks yanzz
Click to expand...
Click to collapse
My device lets me punch in the echo command but once i hit mount or push i'll get permission denied so i'm at a loss myself. I hope one of these higher end techies can help us make this happen before Christmas time or my dads kindle stays stock :crying:

I actually was able to root my 10.2.1 yesterday, but overnight it appears to have upgraded itself to 10.2.3, and now it's unrooted again.
The original technique to root fails on this step:
<code>
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: cannot create /data/local.prop: Permission denied
</code>
Anyone have any luck?
I'd love any ideas to override the bootloader on thing, since I'm about sick and done with the stock rom.

arcymag said:
I actually was able to root my 10.2.1 yesterday, but overnight it appears to have upgraded itself to 10.2.3, and now it's unrooted again.
The original technique to root fails on this step:
<code>
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: cannot create /data/local.prop: Permission denied
</code>
Anyone have any luck?
I'd love any ideas to override the bootloader on thing, since I'm about sick and done with the stock rom.
Click to expand...
Click to collapse
If you put the 10.2.1 rom back in the kindleupdates folder on the SDCard and go the setting to update the kindle I wonder if it will reset back to 10.2.1. Atleast you could re-root and then try to block the OTA so it wont go back to 10.2.3.

bodi524 said:
If you put the 10.2.1 rom back in the kindleupdates folder on the SDCard and go the setting to update the kindle I wonder if it will reset back to 10.2.1. Atleast you could re-root and then try to block the OTA so it wont go back to 10.2.3.
Click to expand...
Click to collapse
I tried that last night, but it didn't work for me. Does anyone know if the .bin files from Amazon are flashable through fastboot... It would definitely be worth building/buying a factory cable if we could fastboot flash back to 10.2.1, root, and block ota updates.

Not to beat a dead horse but I am having the same trouble with Kindle Fire 2. Lost Root access last night when Amazon pushed 10.2.3. I tried to down-date to 10.2.1 but the .bin file keeps getting deleted from the kindleupdates folder after I press the update button in "settings-device-about". Unfortunately I learned about disabling automatic updates a little too late. Thank you in advance for helping us out. We are not worthy.

arcymag said:
I actually was able to root my 10.2.1 yesterday, but overnight it appears to have upgraded itself to 10.2.3, and now it's unrooted again.
The original technique to root fails on this step:
<code>
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: cannot create /data/local.prop: Permission denied
</code>
Anyone have any luck?
I'd love any ideas to override the bootloader on thing, since I'm about sick and done with the stock rom.
Click to expand...
Click to collapse
Thats exactly where it fails for me :/
Oh kindle hacking gods have mercy on us.

xiastro1ix said:
Thats exactly where it fails for me :/
Oh kindle hacking gods have mercy on us.
Click to expand...
Click to collapse
I am willing to try the hack posted for the 8.9" bootloader.
However I want to know the restore process works first.
If someone will pull the partitions to restore, zip them and post them I will try the backup on my KindleFire2.
See Here:
http://forum.xda-developers.com/showthread.php?t=2032822
Mine is bricked as of now so trying to restore it won't harm it anymore that it already is.
Once we having a working restore I will try the bootloader crack....and in an exchange with
Hashcode he said he thinks the Original KF roms will then work (WITH SOME KERNEL CHANGES)
for the KindleFire2.

this thread
http://forum.xda-developers.com/showthread.php?t=2033297
claims that they've got root working on the current version, but I tried and it doesn't even recognize my device is plugged in. Several confirmations in that thread that people have it working though.

confrmed root access on 10.2.3
http://forum.xda-developers.com/showthread.php?t=2033297
Just completed hooray!
Now to replace ROM
well it claims its rooted and it has super user installed, but i still cant get past permission denied messages when trying to go ahead and get a new rom on it.
Not sure what to do here, i want to get google aps on it and i'll be fine, but i don't know what file explorer would be good for the stock rom that i can get through the amazon store :\
I'm actually not sure if it is rooted, the first method installed SU onto the phone, but i don't actually see the second portion processing the exploit, its getting permission denied aswell, the kindle has superuser on it, but now i'm completely lost, i still cant get it to do anything....
Edit- ALL DONE YAY
Got googleplay and 1mobile installed, just had to purchase ES file explorer and play around a bit

Any idea why I can't seem to get past these root methods even seeing my kindle is plugged in? I KNOW one of the methods came bundled with some kinda drivers ... I'm just at a loss for what I'm doing wrong because I've tried all sorts of stuff from various posts and instructions...
Running Win7 x64 if that helps any.

Trendy Ideology said:
Any idea why I can't seem to get past these root methods even seeing my kindle is plugged in? I KNOW one of the methods came bundled with some kinda drivers ... I'm just at a loss for what I'm doing wrong because I've tried all sorts of stuff from various posts and instructions...
Running Win7 x64 if that helps any.
Click to expand...
Click to collapse
Step one is getting ADB hooked up and installed on your computer
if youre telling me your computer is seeing "kindle" then youre already doing it wrong. In order for these methods to work upon plugging in your kindle, device manager should say Android- ADB composite device, or something along those lines,

xiastro1ix said:
Step one is getting ADB hooked up and installed on your computer
if youre telling me your computer is seeing "kindle" then youre already doing it wrong. In order for these methods to work upon plugging in your kindle, device manager should say Android- ADB composite device, or something along those lines,
Click to expand...
Click to collapse
I was trying to use the ADB drivers found here,
http://forum.xda-developers.com/showthread.php?t=1893838
but when installed they didn't say anything like that in the final step that showed me what was installed, it said amazon kindle somethingorother.
Device manager went from showing
Portable devices
|
_ Kindle
To now
Kindle Fire
|
_ Kindle
Installing the driver manually gets me something that looks like ADB Kindle Fire but now it doesn't show up in My Computer at all, and the root with restore
http://forum.xda-developers.com/showthread.php?t=1886460
doesn't "see" my kindle...
I'm rather lost.
Here's a log of as far as I've gotten so far:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (22.11.2012) v17 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
.
Normal Mode enabled!
.
Pushing busybox....
failed to copy 'stuff/busybox' to '/data/local/tmp/./busybox': Permission denied
Pushing su binary ....
failed to copy 'stuff/su' to '/data/local/tmp/./su': Permission denied
Pushing Superuser app
failed to copy 'stuff/Superuser.apk' to '/data/local/tmp/./Superuser.apk': Permi
ssion denied
Making busybox runable ...
Unable to chmod /data/local/tmp/busybox: No such file or directory
.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
error: device not found
Waiting for device to show up again....
Going to copy files to it's place
/system/bin/sh: /data/local/tmp/busybox: not found
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
It's only "Seeing" my kindle if I power it down, plug in the USB, and then it seems to "catch" it while it's booting up. And it remains caught until the tool lets go of it and then it goes to the lock screen as normal.
on this step
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
I get no restore option, probably because my kindle is in a booting state when this is all happening.

I was able to root my Kindle Fire 2 on 10.2.3 doing a combination of:
http://forum.xda-developers.com/showthread.php?t=1891939
and
http://forum.xda-developers.com/showthread.php?t=1894717
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
This step in red no longer works!
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
Instead do...
4) Restore the fake "backup": adb restore fakebackup.ab Note: do not click restore on your device. Just enter the command into the command prompt on your PC and press the enter key.
5) Run the "exploit": adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" Note: when you enter this command, you should see your adb window flooded with errors -- this is what is supposed to happen.
6) Now that the "exploit" is running, click restore on your device.
7) Once it finishes, reboot your device: adb reboot Note: Do not try and use your device when it reboots. Running this exploit will reboot your device into emulator mode, so it will be laggy and the screen will flicker -- this is normal.
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
adb install Superuser.apk

Deflection said:
I was able to root my Kindle Fire 2 on 10.2.3 doing a combination of:
http://forum.xda-developers.com/showthread.php?t=1891939
and
http://forum.xda-developers.com/showthread.php?t=1894717
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
This step in red no longer works!
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
Instead do...
4) Restore the fake "backup": adb restore fakebackup.ab Note: do not click restore on your device. Just enter the command into the command prompt on your PC and press the enter key.
5) Run the "exploit": adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" Note: when you enter this command, you should see your adb window flooded with errors -- this is what is supposed to happen.
6) Now that the "exploit" is running, click restore on your device.
7) Once it finishes, reboot your device: adb reboot Note: Do not try and use your device when it reboots. Running this exploit will reboot your device into emulator mode, so it will be laggy and the screen will flicker -- this is normal.
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
adb install Superuser.apk
Click to expand...
Click to collapse
I have a new Kindle Fire (1st gen) and all your steps were perfect until I tried to install the SuperUser.apk where it says I dont have permissions to copy to /data/tmp... ans fails to install superuser.
Any ideas? Maybe chmod of /data getting in emulator mode?
Thanks

reyvaj said:
I have a new Kindle Fire (1st gen) and all your steps were perfect until I tried to install the SuperUser.apk where it says I dont have permissions to copy to /data/tmp... ans fails to install superuser.
Any ideas? Maybe chmod of /data getting in emulator mode?
Thanks
Click to expand...
Click to collapse
There is a whole forum for kf1. Kf1 runs 6.something not 10.2...

Hi, i need help, i want root my kindle fire first generation 7 on 10.2.3_user_2313820 sw version, many thanks

[Q] Lost Root After Jelly Bean OTA Update

Ok, I don't think I'm the only one out there that lost root after the JB OTA update today... Anybody else? I was using Voodoo OTA RootKeeper and everything.... Crap... Any news on an exploit yet?

Lost root too. Rootkeeper didn't do it's job. Now just waiting for a solution.

Not sure how useful but someone on the main JB update thread mentioned they were able to restore with a few adb commands. Apparently for some OTA keeps root but doesn't reinstall it correctly with the button and a few adb's will regain it. FWIW.

Odd, mine kept root without an issue. I'm curious why it's different for some.

Mine kept it but I did the full download and booted to stock recovery and did flash update.zip. then restored root
Sent from my DROID BIONIC using xda app-developers app

neo1738 said:
Not sure how useful but someone on the main JB update thread mentioned they were able to restore with a few adb commands. Apparently for some OTA keeps root but doesn't reinstall it correctly with the button and a few adb's will regain it. FWIW.
Click to expand...
Click to collapse
I've looked and looked for any ADB commands to fix root and cant find them, do you have a link to the post? Thanks

Ok, I've also tried Dan Rosenburg's Motochopper exploit and that didn't work either.... We might be stuck without root until a viable exploit pops up.

awaiting for root too.

Hmmm. I kept root using ota root keeper. Just selected protect root and ashed in recovery the new jb
Sent from my DROID BIONIC using xda app-developers app

have you try the razr-blade exploit?

Updated SU with stock ICS, installed Voodoo, backed up root, flashed JB and restored root. I have SU and voodoo says successful but superuser is not working. Tried, razr-blade, and MotoChopper, both a no-go.

I used Voodoo, Updated to JB, and re-rooted unsuccessfully. I've even tried to go in and restore Su manually and change it's permissions but nothing seems to be working. :/

I lost root, but you can bring it back! NOTE: This will ONLY work if you backed up root with Voodoo OTA RootKeeper prior to updating to Jelly Bean!!!
Make sure you have android debugging enabled and mount it as a media device.
Follow these instructions: (copied from another site)
1) Download the unsure su from here and put it somewhere on your C Drive. It will be used in the following push step (Assuming windows) (This is a WIDE OPEN su without any controls). (sparky root i believe?)
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
2) start a CMD window and logon to adb (type "adb shell" without the quotes to log on)
3) su -
4) verify you have root:
id
uid=0(root) gid=0(root)........
If you don't you can try these instead of 'su':
"/system/su-backup" or "/system/su_backup"
5) remount system as RW:
mount -o remount,rw /dev/block/mmcblk0p1 /system
6) make a backup of current su just in case in adb
cat /system/bin/su > /system/bin/su1
7) open a new CMD window and push the su binary from step 1 to the sdcard using the path from where ever you put it.
adb push c:\<some path>\su /sdcard/
8) Then copy it to /system/bin from the adb session where you su'd.
cat /sdcard/su > /system/bin/su
9) Change permissions for SU
chmod 6755 /system/bin/su
10) download superuser (NOT SUPERSU) from play store if you do not have it already.
11) have superuser upgrade the su binary. It may fail to remount system as RO. Just rerun the update in superuser and it will work the 2nd time. You don't need to remount system as RO manually since superuser update of SU will do that for you.
12) congrats. your now rerooted.
13) remove the backup after you know your OKAY.
mount -o remount,rw /dev/block/mmcblk0p1 /system
rm /system/bin/su1
mount -o remount,ro /dev/block/mmcblk0p1 /system
Hope this helps you guys!

Does anyone have the fixed dropbox link for the post above?

So I managed to get root back. Then I downloaded SuperSU and when I tried to update binaries, I lost root. Is there a fix for that?

https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
I just googled part of the text and found the source I think

chetmichaels said:
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
I just googled part of the text and found the source I think
Click to expand...
Click to collapse
Yup, that looks right. If this ceases to work soon as well I will go ahead and upload it to my Dropbox as I still have the su file. I included that link you provided into my post above.

Frankie1588 said:
I lost root, but you can bring it back!
Follow these instructions: (copied from another site)
1) Download the unsure su from here and put it somewhere on your C Drive. It will be used in the following push step (Assuming windows) (This is a WIDE OPEN su without any controls). (sparky root i believe?)
2) start a CMD window and logon to adb
3) su -
4) verify you have root:
id
uid=0(root) gid=0(root)........
If you don't you can try these instead of 'su':
"/system/su-backup" or "/system/su_backup"
5) remount system as RW:
mount -o remount,rw /dev/block/mmcblk0p1 /system
6) make a backup of current su just in case in adb
cat /system/bin/su > /system/bin/su1
7) open a new CMD window and push the su binary from step 1 to the sdcard using the path from where ever you put it.
adb push c:\<some path>\su /sdcard/
8) Then copy it to /system/bin from the adb session where you su'd.
cat /sdcard/su > /system/bin/su
9) Change permissions for SU
chmod 6755 /system/bin/su
10) download superuser (NOT SUPERSU) from play store if you do not have it already.
11) have superuser upgrade the su binary. It may fail to remount system as RO. Just rerun the update in superuser and it will work the 2nd time. You don't need to remount system as RO manually since superuser update of SU will do that for you.
12) congrats. your now rerooted.
13) remove the backup after you know your OKAY.
mount -o remount,rw /dev/block/mmcblk0p1 /system
rm /system/bin/su1
mount -o remount,ro /dev/block/mmcblk0p1 /system
Hope this helps you guys!
Click to expand...
Click to collapse
your download link is not working can you check the link.

briafalk said:
your download link is not working can you check the link.
Click to expand...
Click to collapse
Check now. I fixed the link. Sorry about that guys!

Frankie1588 said:
Check now. I fixed the link. Sorry about that guys!
Click to expand...
Click to collapse
I am stuck at steps 3 and 4, it does not seem to be working for me. I am not getting root through adb.