Related
Originally posted by Stetsonaw at androidforums...
Please be aware that I did not write these instructions. I only posted them. Stetsonaw wrote these instructions. While comfortable in ADB and have rooted my phone many times in testing as well as rolled back the versions etc... I have no more insight into how or why it is not working for you. If you followed the directions exactly on a version 4 phone, this should work no problem.
Haxcid
Links to the necessary files are listed at the bottom.
Remember, I am not at fault if you brick your phone, now, proceed.
Connect your phone in charge only mode to install the LG Bootstrapper and drivers, or grab the LG Universal Drivers.
Change your USB Mode to Internet Connection
Go into Settings/Applications/Development and ensure USB Debugging is turned on
If all goes according to plan, you should see the ADB Ladybug icon in your notification bar
I updated the Rootzwiki page with the same info found below.
Busybox actually comes installed by LG on the Revo, how awesome is that??
Download the rageagainstthecage binary
Download the SU binary
Move these files to the same directory your adb.exe is in.
Code:
The > and # characters below illustrate the prompt
you should have, if you have the $ when you go into adb shell,
exit out and type 'adb usb' then go back into adb shell and
you should see the #
Open Command prompt (either use the Windows Key+R and type cmd or start/run, then type cmd)
32-bit users: >cd c:\program files\android\android-sdk\platform-tools
64-bit users: >cd c:\program files (x86)\android\android-sdk\platform-tools
Or >cd (whatever directory adb is in)
>adb devices (verifies you are connected)
>adb push rageagainstthecage-arm5.bin /data/local/temp/rage
(if the above command fails due to read-only, type 'adb usb' then 'adb root' to validate root status, then 'adb devices' again to verify connection)
>adb push su /data/local/temp/su
>adb shell chmod 777 /data/local/temp/rage
>adb shell ./data/local/temp/rage
>adb shell (If this gives you a $ prompt instead of a # prompt, type 'su', if that fails, 'exit', 'adb usb' like above.)
#mount -o remount,rw -t ext3 /dev/mmcblk0p12 /system
#busybox cp /data/local/temp/su /system/bin/su
#chmod 6755 /system/bin/su
Verify the file is in place w/correct permissions
#cd /system/bin
#ls -l *su
After the ls command you should see the following returned by the system:
-rwsr-sr-x root root 26248 2011-05-29 01:09 su
At this point, you may way to remove the files you put in /data/local/temp (optional):
#rm /data/local/temp/su
#rm /data/local/temp/rage
continue with commands
#reboot
Download and install SuperUser from the Market
Thanks Zennmaster, _mrbirdman_ for finding the linux routes and birdman for helping me out, and droidx8971 for helping me find all the information possible!
http://wikifilez.com/Root Files/revolution/rageagainstthecage-arm5.bin
http://wikifilez.com/Root Files/revolution/su
https://market.android.com/details?id=com.noshufou.android.su&feature=search_result
http://www.lg.com/us/support/mc-support/drivers/LGAndroidDriver_Ver_1.0_All.exe
Just a note for some. The rageagainstthecage bin file may be detected as a virus/trojan. It is not. You may want to disable your antivirus before downloading the .bin file.
I run avira on my desktop and it caught the file as a virus everytime I downloaded it and then deleted it. Avast on my laptop however did not.
Root is simple if you follow the instructions. You need to make sure that adb recognizes your device. Takes 5 minutes to complete, took me longer to install adb again and update it.
Any reason to not use the one click method? Seems to be working
bwhxeon said:
Any reason to not use the one click method? Seems to be working
Click to expand...
Click to collapse
No idea. I have not used the one click. Create a thread for it. I posted what I know which is adb.
Successfully Rooted
with RootzWiki instructions for Windows, needed the remount and busybox lines to overcome the permission denied when pushing su.
Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .
MXFrodo195 said:
Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .
Click to expand...
Click to collapse
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
Oh ya I know, I just always keep a stock one, on the Inc if you factory reset from an AOSP rom, you'd bootloop, so you had to make sure you were on a Sense 1.0 or stock rom(from my experience), so I was just making sure it was no big deal to go back.
Any idea when we will have cw on this?
Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
I tried the factory reset. I am still rooted.
navycow said:
I tried the factory reset. I am still rooted.
Click to expand...
Click to collapse
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App
MXFrodo195 said:
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App
Click to expand...
Click to collapse
If you have to return your device, simply remove the superuser app, after you unfreeze anything you may have frozen then factory reset. They honestly will never know it was rooted. The only way now that you can really tell is the super user app from market.
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Thank you for confirming this. My revolution just came in the mail today!
Thanks for posting this here for me Haxcid!
Sent from 1885
navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Cool thanks for checking. Any benefits for ADB over S1C? Can't wait to finally root and freeze half these apps. I think we need a few more twitters to praise koush for a recovery on this beast.
Sent from my VS910 4G using XDA Premium App
Is there recovery for this now? Did I miss something?
stetsonaw said:
Is there recovery for this now? Did I miss something?
Click to expand...
Click to collapse
No No, I was saying we need to praise Koush's good work so he will make one faster .
And Stetsonaw, any idea if I root through ADB, can I unroot with S1C, since it uses the same idea.
S1C for whatever reason will not run(tried three computers, a XP, Vista, and Win7 lol), it keeps freezing at the same spot, everytime.
Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.
stetsonaw said:
Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.
Click to expand...
Click to collapse
Hmmm, ya now my computer for whatever reason won't open up ADB through command. This is getting irritating lol. Should be nice and simple, but it just won't go through. If I downloaded the SDK Manager like 4 months ago, it shouldn't matter, correct?
make sure you change directory to wherever your adb.exe is located... as in:
Code:
cd C:\Program Files\Android\android-sdk-windows\platform-tools
I got an OTA update to 10.2.1 on my Kindle Fire 2 (not HD) before I had a chance to try to root while on 10.1.3. Have any of you KF2 owners tried to root on the new ROM version?
Thanks,
KindofBlues71
yup
Got it to root but I can't get my Holo Launcher HD to work. Does anyone have a fix for this?
strat6 said:
Got it to root but I can't get my Holo Launcher HD to work. Does anyone have a fix for this?
Click to expand...
Click to collapse
just rooted my kindle fire 2 and wanted to know if there is a possibility to prevent it from auto-updating in the future?!
strat6 said:
Got it to root but I can't get my Holo Launcher HD to work. Does anyone have a fix for this?
Click to expand...
Click to collapse
How did you get it to root? I followed the instructions given in
'[VIDEO] How to Root the Amazon Kindle Fire HD Tablet'
http://forum.xda-developers.com/showthread.php?t=1891939
-----
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
-----
I typed in the directions as shown. On the step,
'adb install Superuser.apk'
I got an error that said the file was already there. I suspect that it didn't install. All other steps seemed to complete properly. I also tried the 'rootQemu.Bat' file way shown in,
http://forum.xda-developers.com/showthread.php?p=31759763&postcount=10
But it didn't complete.
Any help?
Patrick
---------- Post added at 05:47 PM ---------- Previous post was at 05:32 PM ----------
PMcHargue said:
How did you get it to root? I followed the instructions given in
'[VIDEO] How to Root the Amazon Kindle Fire HD Tablet'
http://forum.xda-developers.com/showthread.php?t=1891939
-----
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
-----
I typed in the directions as shown. On the step,
'adb install Superuser.apk'
I got an error that said the file was already there. I suspect that it didn't install. All other steps seemed to complete properly. I also tried the 'rootQemu.Bat' file way shown in,
http://forum.xda-developers.com/showthread.php?p=31759763&postcount=10
But it didn't complete.
Any help?
Patrick
Click to expand...
Click to collapse
Well, managed to get root again by folowing the above using copy/paste. Had to unplug/plug in the KF each time. What a pain. Amazon sucks for doing this to a good piece of HW.
That's what worked for me. Also reinstalled the Holo HD launcher and its working again. I saw people in other forums trying to remove the navigation bar in the go launcher, Holo gives you an option to hide it(It still pops up occasionally though). You can also add a home button to the screens so when you're looking at all your apps there's a touchscreen home button.
They definitely made this tablet time consuming to customize but with root and a custom launcher I still think this things a steal at $159.
lost root, adds are back
I recieved the ota update10.2.1 and lost root. Was able to gain root again and since then lost root and adds are back. Didn't loose launcher though. I'm going to try to Root again and try to block the ota this time.
Root problem kindle fire 10.2.1
strat6 said:
I recieved the ota update10.2.1 and lost root. Was able to gain root again and since then lost root and adds are back. Didn't loose launcher though. I'm going to try to Root again and try to block the ota this time.
Click to expand...
Click to collapse
Hi, I have the kindle fire 2 10.2.1, but I have trouble making the root.
Which method I can use to do this?
Must be the same as the kindle fire HD?
thanks
Describing the kind of trouble are you having would be a good place to start...
"That's a special kind of stupid. The kind that makes me laugh"
soupmagnet said:
Describing the kind of trouble are you having would be a good place to start...
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
I used "Qemu automated root" and it said it was successful and I see the SU App. I am not able to go to root explorer in ES file explorer (SU permissions denied) and the Root Explorer paid APP, I am not able to change permissions of any files/folders from Read only to R/W
I guess this means I am not rooted or there a step I missed? I did end up doing it manually by copy and pasting the code into cmd window but same results...
I followed the instructions exactly but now device not found and I folowed the video exactly, su is in the folder (((
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
The adverts are back on the screen, what do I do please
Its nearly 2am in the morning
device is found now, what point do I pick up the command prompts up at?
please
Rovers82517 said:
please
Click to expand...
Click to collapse
ah, man, I'm seriously lost, it fails everytime with these 2 commands,
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
the su file is definately in the platform-tools folder :/
Rovers82517 said:
ah, man, I'm seriously lost, it fails everytime with these 2 commands,
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
the su file is definately in the platform-tools folder :/
Click to expand...
Click to collapse
If your drivers are installed correctly now, use the root tool in development section. Then there are no mistakes. If you insist on the manual method though, you need to put the su file and superuser.apk in your folder titled carol and Start over completely
onemeila said:
If your drivers are installed correctly now, use the root tool in development section. Then there are no mistakes. If you insist on the manual method though, you need to put the su file and superuser.apk in your folder titled carol and Start over completely
Click to expand...
Click to collapse
the files are in there, I've checked and double checked.
when I can get it to see the device again the command prompt has a # instead of a $
I can't afford to brick this thing, I don't know of any other methods, can you tell me what you mean or post the link?
It's gone 2am now I could do with even a little sleep tonight
Thank you for replying
ah, my bad, I know what tool you mean cheers dude
Rovers82517 said:
the files are in there, I've checked and double checked.
when I can get it to see the device again the command prompt has a # instead of a $
I can't afford to brick this thing, I don't know of any other methods, can you tell me what you mean or post the link?
It's gone 2am now I could do with even a little sleep tonight
Thank you for replying
ah, my bad, I know what tool you mean cheers dude
Click to expand...
Click to collapse
No problem, sometimes it just takes a lot of banging your head.
still no luck
I've copied both files to 'carol' as well as platform-tools, what have I done wrong?
Fixed but I'm not sure how
It repeatedly said file not found but in the end I decided to skip to step 4 on QemuRoot and it had worked lol very strange
Think I'll leave it a while before I attempt custom roms lol
Thanks for your help peeps
Rovers82517 said:
It repeatedly said file not found but in the end I decided to skip to step 4 on QemuRoot and it had worked lol very strange
Think I'll leave it a while before I attempt custom roms lol
Thanks for your help peeps
Click to expand...
Click to collapse
From my personal experience is best way how to root kindle fire by qemu (development part of forum) its quite easy... to solve problem if your device isn't found I had to create folder .android in my “documents“ like it is when you will instantly sdk
You have to create it via command line... mkdir .android
Create there required file how it is described in qemu thread. Reinstal kindle adb drivers and try qemu once more.. that worked for me like a charm.
Tomorrow when I will be on PC I will post step by step guide
Kerbik
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
Well I have Kindle Fire 7 at home and I wanted to install android on,so first I have to root it but I can not describe you how many times and solutions I have tried,Binary root,Qemu root, KF First Aide.So first two works like a charm and after "Root" is done I try to test it with ES file explorer and root is not applied.I really don't know what I can do more.
I am at version 11.3.2.5
What can I do?
duvnjak said:
Well I have Kindle Fire 7 at home and I wanted to install android on,so first I have to root it but I can not describe you how many times and solutions I have tried,Binary root,Qemu root, KF First Aide.So first two works like a charm and after "Root" is done I try to test it with ES file explorer and root is not applied.I really don't know what I can do more.
I am at version 11.3.2.5
What can I do?
Click to expand...
Click to collapse
My kindle is this model: kindle fire p48wvb4
duvnjak said:
My kindle is this model: kindle fire p48wvb4
Click to expand...
Click to collapse
BUMP Please help me
duvnjak said:
bump please help me
Click to expand...
Click to collapse
**** you everyone **** youuuuu!
mine just updated to 11.3.2.6 yesterday w/o my knowledge
ugh, I'll never get to root this guy
duvnjak said:
**** you everyone **** youuuuu!
Click to expand...
Click to collapse
No need to flame. We all saw your request.
Head over to kfsowi.com which will porbably redirect you to another site where you can find a rooting guide.
Root for "11.3.2.6_user_326002520"
It´s still possible to root 11.3.2.6 with KindleSuite with a small tweak:
1.) Get an actual version from KindleSuite: https://github.com/secretdevwork/KindleSuite/wiki
2.) Extract the archive and search in folder "/resources/tools" for the file "11325.bat" and make a backup of this file
3.) open "11325.bat" in a text editor
4.) search for the code line
Code:
adb shell chmod 755 /data/local/tmp/*
replace this line with the following code lines:
Code:
adb shell chmod 755 /data/local/tmp/su
adb shell chmod 755 /data/local/tmp/exploit
adb shell chmod 755 /data/local/tmp/rootme.sh
5.) save the edited file
6.) start KindleSuite, go to Root section and select the "11.3.2.5" entry (which leads to the edited Batch skript)
7.) start the rooting procedure as described by KindleSuite
8.) profit
This is just a small tweak to fix the chmod permission problems with the original script but I think KindleSuite will be updated in a few days.
P.S.: the KindleSuite root procedure does restore 11325-boot.img but nevermind it is binary the same as in the original 11.3.2.6_user_326002520 image included.
Calibaan said:
It´s still possible to root 11.3.2.6 with KindleSuite with a small tweak:
1.) Get an actual version from KindleSuite:
2.) Extract the archive and search in folder "/resources/tools" for the file "11325.bat" and make a backup of this file
3.) open "11325.bat" in a text editor
4.) search for the code line
Code:
adb shell chmod 755 /data/local/tmp/*
replace this line with the following code lines:
Code:
adb shell chmod 755 /data/local/tmp/su
adb shell chmod 755 /data/local/tmp/exploit
adb shell chmod 755 /data/local/tmp/rootme.sh
5.) save the edited file
6.) start KindleSuite, go to Root section and select the "11.3.2.5" entry (which leads to the edited Batch skript)
7.) start the rooting procedure as described by KindleSuite
8.) profit
This is just a small tweak to fix the chmod permission problems with the original script but I think KindleSuite will be updated in a few days.
P.S.: the KindleSuite root procedure does restore 11325-boot.img but nevermind it is binary the same as in the original 11.3.2.6_user_326002520 image included.
Click to expand...
Click to collapse
Just says waiting for device after i select 11.3.2.5
Of course you still need an ADB connection and a fastboot cable for rooting the 7" Kindle and according to the "Waiting for device..." ADB connection is not established.