Related
For those of you with Mac OSX or Linux, you can root it using this method:
Step 1. Go to Settings->More->Device and make sure “Allow Installation of Applications” is checked “ON”.
Step 2. Connect your Kindle Fire to your computer via micro-USB cable. And hit “Disconnect” to turn off the USB disk drive mode.
Step 3. Download KindleFireRootMacLinux.zip and unzip to the root directory of your hard disk such as c:\KindleFireRoot.
Download KindleFireRootMacLinux.zip
Step 4. Open up a terminal.
Step 5. Browse to the KindleFireRootMacLinux directory by typing:
cd Downloads/KindleFireRootLinux
Step 6. Type:
mkdir ~/.android
cp adb_usb.ini ~/.android/.
*Note – You might have to add “sudo” for Ubuntu
Step 7. Type:
For Mac:
./adb-mac kill-server
./adb-mac devices
For Linux:
./adb-linux kill-server
./adb-linux devices
If you get a bunch of numbers and letters, that means you are good to go.
Step 8. Type:
For Mac:
sh runmemac.sh
For Linux:
sh runmelinux.sh
Step 9. Your Kindle Fire should do its rooting and reboot.
You can verify you have SuperUser app by going to Settings->More->Applications->All Applications.
Yay!
I do not have anything show up when I do the devices command. I am running a mac.
soundslikemitch said:
I do not have anything show up when I do the devices command. I am running a mac.
Click to expand...
Click to collapse
What do you get?
Did you do this step?
cp adb_usb.ini ~.android/.
soundslikemitch
I had this issue as well and zedomax is correct, you have to make sure that this file resides in your own $HOME/.android folder. While cp adb_usb.ini ~.android/. works you may want to try 'cp adb_usb.ini $HOME/.android` as well. I also had the issue where my fire wasn't being shown while executing ./adb devices which required me to reboot and then it seemed to start getting picked up without issue.
Hope this helps and thanks zedomax for the tutorial
There's a problem with the original instructions: adb needs to be restarted after editing adb_usb.ini. You need to run
./adb-mac kill-server
or
./adb-linux kill-server
to make it work without rebooting your computer.
SifJar said:
There's a problem with the original instructions: adb needs to be restarted after editing adb_usb.ini. You need to run
./adb-mac kill-server
or
./adb-linux kill-server
to make it work without rebooting your computer.
Click to expand...
Click to collapse
thanks forgot to put that in the instructions, fixed!
Moving it to my home folder in .android worked!
But apparently this broke the video store.
No-go for me. Tried all above instructions and nothing shows up in devices. The thing that had me thrown off a bit is the instructions don't exactly match.
I want to follow exactly so is step 6 necessary since the zip file already has the android directory with the file already in it?
soundslikemitch said:
Moving it to my home folder in .android worked!
But apparently this broke the video store.
Click to expand...
Click to collapse
I figured out how to fix the video store. Amazon seems to be looking for the existence of the file /system/bin/su so just rename it if you want to watch videos.
i.e.
Code:
mv /system/bin/su /system/bin/su2
reboot
I am still able to type "su2" and get root and I am able to play videos.
Another solution is installed voodoo OTA rootkeeper (free) from the market place. Once installed you can temporarily remove root, then restart the amazon video service and voila. Once the service is started you can re-enable root for the duration that the service is active (not rebooted) you will have root and amazon video.
you have "mkdir ~.android"
The more common syntax, and what worked for me as your syntax didn't, is:
mkdir ~/.android
This is under Mac OS X 10.6.8
None of these instructions have worked for me, I have spent countless hours trying to do this via Windows (the windows tutorial) and on mac. My device never shows up and it does not root. I have tried restarting my fire, unplugging and plugging back in, etc. I am running Lion 10.7.1. Please help, if possible, pm me so we can chat via Google Chat or something.
Also had the same problem (with Lion 1.7.2 ): Waiting for device...
I used this commands to get it working: (first you have to follow instructions from zedomax step 1-5)
cd downloads/
cd KindleFireRootMacLinux/
mkdir ~/.android
cp adb_usb.ini ~/.android
./adb-mac kill-server
./adb-mac devices
after device is shows up enter:
sh runmemac.sh
After this the KF will reboot and get rooted!
The OSX instructions did not work for me either. I ended up busting out my Windows Laptop and followed the guide and programs from rootkindlefire.com
masterc1111 said:
Also had the same problem (with Lion 1.7.2 ): Waiting for device...
I used this commands to get it working: (first you have to follow instructions from zedomax step 1-5)
cd downloads/
cd KindleFireRootMacLinux/
mkdir ~/.android
cp adb_usb.ini ~/.android
./adb-mac kill-server
./adb-mac devices
after device is shows up enter:
sh runmemac.sh
After this the KF will reboot and get rooted!
Click to expand...
Click to collapse
Doesnt work, it still does not show up under devices and the command runemac.sh just says it is waiting for the device.
I don't know why this may work, but try adding a trailing slash to the cp command; cp adb_usb.ini ~/.android/
Also, this works great under (Sabayon) Linux. Very great little script you have here. Only way it could be easier would be if it did the copying and all that on its own.
The problem I had was that the terminal kept saying "waiting for device." I originally downloaded the "KindleFireRootMacLinux" folder to my desktop. I substituted "desktop" for "download" in the prompts. I tried to root it at least 10 times with no success. The terminal never recognized my kindle. Then I moved the "KindleFireRootMacLinux" folder to the "Downloads" folder and it worked the first time. I'm assuming that some of the code is looking in the downloads folder. Try to move it there and see if that works.
bsoplinger said:
you have "mkdir ~.android"
The more common syntax, and what worked for me as your syntax didn't, is:
mkdir ~/.android
This is under Mac OS X 10.6.8
Click to expand...
Click to collapse
Dude! Thanks so much for pointing out the syntax issue. I tried to do this for nearly an hour... couldn't get it to see my device. But after adding the "/" as you so cleverly suggested, voila. Success!
Thanks a million!
root ran ok
should su show up in apps? Nevermind found it
I searched for the voodoo file and it doesn't show up in the app store. If its on the Android Market then I guess you'd have to download and install that first right?
EDIT: which is explained here - how to get market on fire
http://forum.xda-developers.com/showthread.php?t=1349902
For 6.3 see http://forum.xda-developers.com/showthread.php?p=24129239
Please do not reupload/redistribute BurritoRoot2/BurritoRoot3, instead link directly to my hosting. I own the server, it will no go away any time soon. This allows me to update it if a bug is found.
BurritoRoot3 is not opensource, it is free, but it is not free to distribute. Please do not redistribute it.
Tested on 6.2, 6.2.1 and 6.2.2
Disclaimer:
BurritoRoot3 may void your warranty. While it was tested, over and over, a chance of data loss or hardware damage always exists. If something bad happens due to your use of BurritoRoot3, well it is your fault not our's, don't blame any of us.
Wine/Coffee/Device Funding:
To donate to jcase of TeamAndIRC for BurritoRoot go here:
http://forum.xda-developers.com/donatetome.php?u=2376614
To donate to pokey900 for the FireFireFire Bootloader go here:
http://forum.xda-developers.com/donatetome.php?u=466725
Download:
http://download.cunninglogic.com/BurritoRoot3.apk
BurritoRoot3 is an all in one package, to root and install the custom bootlaoder, FireFireFire, onto the KindleFire.
Instructions are pretty plain and simple, however you will have to get adb working on your own (if you have written, or know of adb guides for the Kindle Fire please PM me to list them here).
ADB GUIDES
MAC GUIDE: http://forum.xda-developers.com/showthread.php?t=1443071
WINDOWS GUIDE: http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
LINUX GUIDE: http://forum.xda-developers.com/showthread.php?p=22067293
What it does:
Gains root, installs superuser, installs su and installs the FireFireFire bootloader.
At this time, we do not have permission to distribute any recovery, once one is available for our use, we will add auto flashing of recovery.
How to use:
adb shell chmod 777 /data/local/tmp
Run app, follow directions given by the app.
Usage example :
[email protected]:~$ adb shell chmod 777 /data/local/tmp <---- This one is important, it may not create BurritoRoot3.bin if this is not done
[email protected]:~$ adb install BurritoRoot3.apk
4897 KB/s (1151520 bytes in 0.229s)
pkg: /data/local/tmp/BurritoRoot3.apk
Success
<go open the app now>
[email protected]:~$ adb shell /data/local/tmp/BurritoRoot3.bin --root
BurritoRoot3 Installer 0.1 by TeamAndIRC
#########################################################################
Usage: BurritoRoot3.bin <parameter>
--root - Restart adbD as root, and install Superuser app
--install - Install su
#########################################################################
Gaining root...
Installing Superuser APP, if it erros as already exists, please ignore the error.
pkg: /data/data/net.andirc.burritoroot3/bin/Superuser.apk
Success
Restarting adbD as root...
Please run adb shell /data/local/tmp/BurritoRoot3.bin --install
[email protected]:~$ adb shell /data/local/tmp/BurritoRoot3.bin --install
BurritoRoot3 Installer 0.1 by TeamAndIRC
#########################################################################
Usage: BurritoRoot3.bin <parameter>
--root - Restart adbD as root, and install Superuser app
--install - Install su
#########################################################################
BurritoRoot3 kroot 0.1 - TeamAndIRC
Remounting /system...
Cleaning up, ignore any errors
rm failed for /system/xbin/su, No such file or directory
rm failed for /system/bin/su, No such file or directory
Installing su...
Remounting /system..
Root installed
Starting: Intent { act=android.intent.action.MAIN cmp=net.andirc.burritoroot3/.FireFireFire }
Please check your Kindle's screen
[email protected]:~$
If you already have root, and want to safely install the FireFireFire bootloader, you can use the app, just install, open/close the app then
adb shell am start -a android.intent.action.MAIN -n net.andirc.burritoroot3/net.andirc.burritoroot3.FireFireFire
To install the CWR recovery by DoomLord after gaining root:
Download it, and push it to your Kindle
adb push <filename> /data/local/recovery.img
adb shell dd if=/data/local/recovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
Would you support the archos G9 devices
jutley said:
Would you support the archos G9 devices
Click to expand...
Click to collapse
Doesn't archos sign or lock system?
I love you Devs so much. I just got a Kindle today, but as I watched the video your Kindle shows up under Other Devices as if it didn't install the device driver. Mine is installed under portable devices. Can I just update that one or is there a debug mode for the Kindle that I'm missing?
Thanks for all you do!
---------- Post added at 10:06 AM ---------- Previous post was at 09:55 AM ----------
CharlieBoy808 said:
I love you Devs so much. I just got a Kindle today, but as I watched the video your Kindle shows up under Other Devices as if it didn't install the device driver. Mine is installed under portable devices. Can I just update that one or is there a debug mode for the Kindle that I'm missing?
Thanks for all you do!
Click to expand...
Click to collapse
LoL Nevermind I think I know why mine isn't there... I've already installed ADB from before. I shall continue on and see what happens :-D
I'm currently running Ubuntu 11.10(Without access to a windows computer to do so.) And after following the steps within the BurritoRoot I get error: insufficient permissions for device when entering adb root. I've rebooted my kindle and laptop as well as changed usb ports.
I've set it up so that it's acknowledged within /.android. Am I perhaps missing something sdk wise? The usb configuration install for extras within it says Linux isn't compatible. But any insight into this would be appreciated I'm not new to Android or adb for that matter. Things seem to be done differently for the Kindle is all.
Thanks guys.
AproSamurai said:
I'm currently running Ubuntu 11.10(Without access to a windows computer to do so.) And after following the steps within the BurritoRoot I get error: insufficient permissions for device when entering adb root. I've rebooted my kindle and laptop as well as changed usb ports.
I've set it up so that it's acknowledged within /.android. Am I perhaps missing something sdk wise? The usb configuration install for extras within it says Linux isn't compatible. But any insight into this would be appreciated I'm not new to Android or adb for that matter. Things seem to be done differently for the Kindle is all.
Thanks guys.
Click to expand...
Click to collapse
adb kill-server
sudo -s
adb devices
should see it now
Quit following me around jcase
Unheard said:
Quit following me around jcase
Click to expand...
Click to collapse
Hah Where you been?
I can not get ADB to recognize the device for the life of me.
I know I have the drivers installed the Fire is recognized as "android composite adb interface" under the Android Phone category in Device manager. But I can not get adb to see it.
"Adb kill-server"
"adb devices"
and it shows no devices attached. Ive done a factory reset on the tablet just to see (knowing it wouldn't make a difference)
Im running Windows XP
if someone could help me out.
notsointeresting said:
I can not get ADB to recognize the device for the life of me.
I know I have the drivers installed the Fire is recognized as "android composite adb interface" under the Android Phone category in Device manager. But I can not get adb to see it.
"Adb kill-server"
"adb devices"
and it shows no devices attached. Ive done a factory reset on the tablet just to see (knowing it wouldn't make a difference)
Im running Windows XP
if someone could help me out.
Click to expand...
Click to collapse
I'm sure its related to windows' drivers but I have no clue. Sorry
jcase said:
adb kill-server
sudo -s
adb devices
should see it now
Click to expand...
Click to collapse
Thanks man, I knew I must have failed to do something. It's much appreciated.
Dis this last night and it worked fine. Thanks!
I did have a few minor stumbles though. It seems the newest version of the software changed the name of the superuser app but the guide still uses the old name in the install command. Once I realized this I just changed the name in the command and it went right in.
Also for some reason I couldn't select the text in the adb box on the web page so I had to enter the commands by hand. No big deal but I would have felt more secure if the commands were in simple text so I could have copy/paste them in.
Like I said though everything worked and I have the market installed now. Thanks for the hard work!
I'm having some trouble with mine...I am trying to follow the video instructions to the link but it shows downloading a .android folder and extracting it to my user name on desktop but there is no such link. I have downloaded SDK and installed google usb drivers as well. I have 6.2.1 firmware and downloaded kindleroot_androidpolice.apk and placed on my kindle and I also downloaded superuser-2. I am not able to install the driver to the fire either. I go to my computer, manage, device manager, kindle, update driver software, browse my computer, etc. I have no INF file to choose under my .android folder.
Any help would be appreciated
My sd card is showing up as unmounted and not sure how to remount it. I sent adb remount and it didn't work. Any help would be appreciated.
Fee454 said:
I'm having some trouble with mine...I am trying to follow the video instructions to the link but it shows downloading a .android folder and extracting it to my user name on desktop but there is no such link. I have downloaded SDK and installed google usb drivers as well. I have 6.2.1 firmware and downloaded kindleroot_androidpolice.apk and placed on my kindle and I also downloaded superuser-2. I am not able to install the driver to the fire either. I go to my computer, manage, device manager, kindle, update driver software, browse my computer, etc. I have no INF file to choose under my .android folder.
Any help would be appreciated
Click to expand...
Click to collapse
would suggest to use this:
http://forum.xda-developers.com/showthread.php?t=1399889
[/COLOR]
b63 said:
would suggest to use this:
http://forum.xda-developers.com/showthread.php?t=1399889
Click to expand...
Click to collapse
This tool will attempt to install the correct Drivers for the Kindle Fire.
It will also perform the setup required for adb_usb.ini in .android for you.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
Press any key to continue . . .
I tried to install the drivers for the kindle but i receive the above message
---------- Post added at 09:56 PM ---------- Previous post was at 09:07 PM ----------
My issue is it cannot find my device...where can I find the kindleADB.zip I keep hearing about?
did you do install_drivers.bat first ?
take a look:
http://forum.xda-developers.com/showpost.php?p=20698002&postcount=283
that should correct the path issue
You should get the same files from the android Sdi. Good luck.
Jcase, I know that you said the unroot button did not work, but is there a method of unrooting?
b63 said:
did you do install_drivers.bat first ?
take a look:
http://forum.xda-developers.com/showpost.php?p=20698002&postcount=283
that should correct the path issue
Click to expand...
Click to collapse
Yes thank you. Moving it to the same as the run.bat seemed to have worked as it shows online now when running the Kindle Fire Utility. I switched it to fast boot but now seems to have been frozen at the kindle fire logo for quite some time now. I heard you have to switch to fastbook to install TWRP first before rooting?
I am not sure if I should attempt to somehow reboot this as it seems to be stuck at the boot up screen
wrong - switch back to normal boot and use the utility
THIS GUIDE NO LONGER WORKS BECAUSE ANDROID ISN'T WHAT IT USED TO BE BACK IN 2013-14.
PLEASE STOP WASTING TIME TO FOLLOW THIS OBSOLETE METHOD 1. PLEASE REFER ONLY TO METHOD 3
The Ultimate Guide to Rooting any Android Device Manually !!!!
Wanting to ROOT Your Phone but can't do Because Of No rooting Guides or want to learn to root any device ? Then , This Guide Is For YOU
OK So lets start....
**What You Need**
1.Your Unrooted Android Device.
2.ADB Drivers Installed On Your PC. If you Don't Have Download From Here :
Code:
adbdriver.com/
3. The Most Inportant Root Kit Made By Me (N'ayam Amarsh'e) - Download From The Attachment.
4.Strength And Courage 'Coz Rooting Voids Your Warranty... If You have a samsung device then Don't Worry Your warranty is gone forever... But if you own any other, maybe you can void it or maybe......
I've Written Android Device as ADV to make it more easy....
**Steps**
So you have the adb drivers installed let's go....
1. Open The root kit by Extracting The Rootkit with WinRAR....
2.Turn 'USB DEBUGGING' 'ON' in your ADV...
3. Connect your ADV to Your PC...
4.In the root kit Open Cmd.exe File ... [ IF YOU CAN'T OPEN CMD, GOTO C:/WINDOWS/SYSTEM32/ COPY CMD .EXE TO YOUR ROOTKIT FOLDER]
5. In CMD window Type the following command...
Code:
->adb devices *Your device will get listed in the window if it doesn't check your adb drivers or if you have followed the steps properly...
->adb push busybox /data/local/tmp
->adb push su /data/local/tmp
->adb push Superuser.apk /data/local/tmp
If you Succeed Move On ...
6.Then You need Root Shell Type :
Code:
adb shell
Note that you see a "$" sign in the command prompt. That means you are not in 'su' shell.
7.Next run the following commands in the shell to change permissions and get some limited privileges for the Superuser files:
Code:
->chmod 6755 /data/local/tmp/su
->chmod 755 /data/local/tmp/busybox
->chmod 644 /data/local/tmp/Superuser.apk
{Note}The names of the files are case sensitive!
8.Done ? Now You need to open a copy of linux which has nautilus... So enter your linux (I recommend using ubuntu 11.4) and type in the terminal (ctrl+alt+T)
Code:
->sudo nautilus
this will open nautilus with root privileges...
You can just boot it from USB so no hassle of installing it... http://www.cyberciti.biz/tips/download-ubuntu-linux-11-04-iso-cd-dvd-images-natty-narwhal.html
Having your ADV connected with USB to PC switch it off and put it in download/recovery mode...
superlouro said:
DEVICE OFFLINE?
! SOLUTION ! (click me)
Click to expand...
Click to collapse
9.In The Exploring Window navigate to
Code:
/data/local/tmp
and move/cut 'su' and 'busybox' to
Code:
/system/bin
...
10.From the tmp Folder you went earlier Move/cut 'Superuser.apk' to
Code:
/system/app
11.Now Reboot You ADV ... Congrats ! You're now ROOTED !
Many Users Are Having Problem with This Method, If you can't do the method 1. Try Method 2.
METHOD 2
PLEASE DON'T ASK ME ABOUT THIS METHOD, THIS IS JUST FOR A TRY, MY BROTHER FOUND THIS METHOD TO BE WORKING, I HAVEN'T TRIED IT YET!
This is linux based method, It's quite easy if you follow every step correctly...
You need to download psneuter, https://github.com/tmzt/g2root-kmod/tree/master/scotty2/psneuter
When you have it execute the following...
Code:
adb devices
Code:
adb push psneuter /data/local/tmp
This will copy the file to your device and now we'll execute it..
Code:
adb shell
cd /data/local/tmp
chmod 777 psneuter
./psneuter
Now You'll see
Code:
adb kill-server
adb devices
adb shell
now # will appear in place of $, or after typing $su.
Code:
# mount -o remount,rw -t rfs /dev/block/st19/system
# exit
$ adb push busybox /system/bin
$ adb push su /system/bin
$ adb install Superuser.apk
$ adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19/system
# exit
$ adb reboot
Now your device will reboot and you can see SuperUser App in your app drawer...
----------------------------------------------------------------------
METHOD 3
There is no chance of the phone not getting rooted with my method but If you don't want to do the above methods, Try these, I'm pretty sure they will root your device with ease...
1. Framroot App [Not On Google Play]-http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
2.KingoRoot App - www.kingoapp.com
3.One Click Root Free/Pro (My Favorite app, roots many devices with No-Brick Guarantee) - www.oneclickroot.com
4.Root Master App - forum.xda-developers.com/showthread.php?t=2672150
5.z4root App - http://forum.xda-developers.com/showthread.php?t=833953
6.Easy rooting toolkit App-http://forum.xda-developers.com/showthread.php?t=1321582
7.Vroot Software - http://vrootdownload.info/ or http://www.mgyun.com/en/getvroot
8.SRSRoot Software - http://www.srsroot.com
9.Unlock Root Software - http://www.unlockroot.com/download.html
10.Universal Androot App - forum.xda-developers.com/attachment.php?attachmentid=391774
ONLY FOR MTK DEVICES- MTK DROID TOOLS- http://forum.gsmhosting.com/vbb/f60...3-2014-imei-repair-rooting-tool-more-1780568/
HOPE THESE WILL DO....
Press Thanks To appreciate me to Work On Other Guides And Roms....
Your Appreciation Is Needed...
And This GUIDE IS Originally By N'ayam Amarsh'e
I have any error. Device is offline.
---------- Post added at 09:13 AM ---------- Previous post was at 09:02 AM ----------
uukasz92 said:
I have any error. Device is offline.
Click to expand...
Click to collapse
Problem solved i download another adb drivers and work fine
In /UserData/local/tmp i only have one file "directory" and nothing else. It's look like something block the data folder.
uukasz92 said:
In /UserData/local/tmp i only have one file "directory" and nothing else. It's look like something block the data folder.
Click to expand...
Click to collapse
that means you have not properly pushed the files into the directory.... Try installing adb drivers again and do the same steps...Good luck
When you open cmd just type ' adb devices' if your device gets listed then you can start if it doesn't check your drivers...
After uinstall all adb drivers and phone drivers comand prompt shows me a device code and status ofline. At the begining i install atached to therad package of adb drivers. But lately some where in Internet I find some update package of adb drivers. And there was the same sort of files like in your package. I put them there and replace and after that adb shows the device is working and status is online but your guide still does not work. Question is where is real problem ? I checked and Debug Mod is on, drivers are installed.
Try this , download android commander and try to copy the busybox , su and superuser to data/local/tmp
N'ayam Amarsh'e said:
Try this , download android commander and try to copy the busybox , su and superuser to data/local/tmp
Sent from my Mi-492 using xda app-developers app
Click to expand...
Click to collapse
I used the same files in android commander because program can't finde my device to.
Which phone you have.... Try to download its original drivers this might help...
I using Samsung Galaxy Grand Neo (GT-I9060) Jelly Bean 4.2.2
Now is working. But how to move "su" and busybox into system/bin ? Android commander says " You need root to do this." when i try to copy does files into system/bin. Folders are protected and I dont have premission to do anything with them.
uukasz92 said:
I using Samsung Galaxy Grand Neo (GT-I9060) Jelly Bean 4.2.2
Now is working. But how to move "su" and busybox into system/bin ? Android commander says " You need root to do this." when i try to copy does files into system/bin. Folders are protected and I dont have premission to do anything with them.
Click to expand...
Click to collapse
Sorry I forgot that Android Commander works only for rooted phones... Silly Me...
OK you will need to do it with Droid Explorer
OR
linux and in the linux you'll have to type 'sudo nautilus' it'll open it with root privilages...
N'ayam Amarsh'e said:
Sorry I forgot that Android Commander works only for rooted phones... Silly Me...
OK you will need to do it with Droid Explorer
OR
linux and in the linux you'll have to type 'sudo nautilus' it'll open it with root privilages...
Click to expand...
Click to collapse
And in your guide need little correct. In step 9 should be /data/local/tmp not /UserData/local/tmp. Does are two diffrent folders. And before I think I do something wrong when all files be already on right place
Droid Explorer cant change folders premission too. Command prompt says : Read-only drirectory. I don't know what to do now.
uukasz92 said:
And in your guide need little correct. In step 9 should be /data/local/tmp not /UserData/local/tmp. Does are two diffrent folders. And before I think I do something wrong when all files be already on right place
Click to expand...
Click to collapse
thanks.... Guide is updated now
Good 1 helped alot
harmeet singh said:
Good 1 helped alot
Click to expand...
Click to collapse
I am happy that I helped....
Hi! First thank you for that guide. I rooted several devices but with a noname(10.1" A10 dual core) china tablet I have some problems so I hope your solution works.
I have some problems/questions:
1. Step 5: Are you sure it's:
Code:
adb push su /data/local/tmp
instead of
adb push su /data/local/tmp[B][SIZE="5"]/[/SIZE][/B]
I'm currently not able to look at the data folder but if I change the directions e.g to /test/local/tmp it just creates a "tmp" file and overwrites the file with every push command.
2. Step 6: If it's a $ it's not rootet, what should be there if it's rooted? I have a # there. Rootchecker says it's rooted since the beginning, but I cant access with superuser/supersu etc.
3. Step 8 doesn't work. I use a virtual box with ubuntu 13.10(Stinson: new is always better?) for the first time. With "sudo nautilus" I get the message that root access is not granted(failed to register client). I used "gksudo nautilus" instead... does that matter?
4. I can't connect my device to the virtual box. I tried to add the usb device but didn't work. USB Developer Android[0223] is in virtual box connected. However, I dont know where to find it in ubuntu. I'm a ubuntu noob sorry :/
5. Is there another way to get rw permissions?
Thanks in advance :good:
thankyou for information i think is hard for me
Very nice, ty
Humbel said:
Hi! First thank you for that guide. I rooted several devices but with a noname(10.1" A10 dual core) china tablet I have some problems so I hope your solution works.
I have some problems/questions:
1. Step 5: Are you sure it's:
Code:
adb push su /data/local/tmp
instead of
adb push su /data/local/tmp[B][SIZE="5"]/[/SIZE][/B]
I'm currently not able to look at the data folder but if I change the directions e.g to /test/local/tmp it just creates a "tmp" file and overwrites the file with every push command.
2. Step 6: If it's a $ it's not rootet, what should be there if it's rooted? I have a # there. Rootchecker says it's rooted since the beginning, but I cant access with superuser/supersu etc.
3. Step 8 doesn't work. I use a virtual box with ubuntu 13.10(Stinson: new is always better?) for the first time. With "sudo nautilus" I get the message that root access is not granted(failed to register client). I used "gksudo nautilus" instead... does that matter?
4. I can't connect my device to the virtual box. I tried to add the usb device but didn't work. USB Developer Android[0223] is in virtual box connected. However, I dont know where to find it in ubuntu. I'm a ubuntu noob sorry :/
5. Is there another way to get rw permissions?
Thanks in advance :good:
Click to expand...
Click to collapse
For Your First Answer You Need not to worry /tmp and /tmp/ are the same...
2.Have you tried typing 'adb shell' then ' su ' if yes there's your solution.... If not then you have problem with su binary or busybox....
3.You have an Ubuntu 11.4 .iso file so burn it to a blank disk and boot your live disk .... It should be all right then...
4.Answer in 3....
5.Answer in 3....
6.Press Thanks if I helped...
bro im confused wt to do exactly in that sudo ... step pls give a brief explaination
Hello Everyone! I would like to make a guide for Rooting our Sony Xperia Z1s for T-mobile, I tried this with Android 4.3 Firmware 14.2.C.0.159.
This is my first Post so if i make a mistake please let me Know.
Thanks to Jcase and his pwn file to make this root Posible.
This is just the way how i did it and worked for me.
I AM NOT RESPOSIBLE FOR BRICKED DEVICES, THIS IS JUST A GUIDE FOR THOSE WHO DON'T KNOW HOW TO USE THE JCASE EXPLOID.
Requirements:
Well, first of all you have to make sure that your computer have the correct adb drivers installed and you can go into it.
Debugging mode On. (Developer options, USB Debugging Checked)
Download the JCASE pwn (http://forum.xda-developers.com/showpost.php?p=53407127&postcount=1004)
Download the Adb Drivers Updated (http://www.mediafire.com/download/41lx6p71xxit1ax/ADB+Drivers_Updated.zip) Thanks to Droidextra.org, UJJWAL KUMAR.
Process:
1- With the two zip files downloaded you will unzip it in the Local Disk (C), Create a folder with a name like "Root Tool" And unzip the files there, just like these: Check attached picture.
2- Press Shift on the keyboard and right click and then "open a Command Prompt here"
3- Check if your Sony Xperia Z1s its working well in the adb typing: adb devices. If it says failed, you have to check your adb drivers, if not, you're going good.
4- So if all its going well, just type this on command prompt (Thanks JCASE)
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
5- wait for the adb to finish.
6- Unplug you're phone and restart it.
7- Install Super Su apk (Can download it from Play Store or latest Apk)
8- Open SuperSu and update binarys with Normal Mode
Now you must be Root, if SuperSu can't update Binarys try again from 2.
If you are not able to Write to system try this: http://forum.xda-developers.com/show...57358331140130
If this works for you please say thanks to Jcase who made this can be possible.
I tried this but nothing happens I attached what happens in cmd
Sent from my C6916 using XDA Free mobile app
---------- Post added at 08:12 PM ---------- Previous post was at 08:06 PM ----------
not working for me this is what I get in CMD
C:\Root Tool>adb push pwn /data/local/tmp/pwn
2792 KB/s (574722 bytes in 0.201s)
C:\Root Tool>
C:\Root Tool>adb shell chmod 755 /data/local/tmp/pwn
C:\Root Tool>
C:\Root Tool>adb shell /data/local/tmp/pwn
superangel16 said:
Hello Everyone! I would like to make a guide for Rooting our Sony Xperia Z1s for T-mobile, I tried this with Android 4.3 Firmware 14.2.C.0.159.
This is my first Post so if i make a mistake please let me Know.
Thanks to Jcase and his pwn file to make this root Posible.
This is just the way how i did it and worked for me.
I AM NOT RESPOSIBLE FOR BRICKED DEVICES, THIS IS JUST A GUIDE FOR THOSE WHO DON'T KNOW HOW TO USE THE JCASE EXPLOID.
Requirements:
Well, first of all you have to make sure that your computer have the correct adb drivers installed and you can go into it.
Debugging mode On. (Developer options, USB Debugging Checked)
Download the JCASE pwn (http://forum.xda-developers.com/showpost.php?p=53407127&postcount=1004)
Download the Adb Drivers Updated (http://www.mediafire.com/download/41lx6p71xxit1ax/ADB+Drivers_Updated.zip) Thanks to Droidextra.org, UJJWAL KUMAR.
Process:
1- With the two zip files downloaded you will unzip it in the Local Disk (C), Create a folder with a name like "Root Tool" And unzip the files there, just like these: Check attached picture.
2- Press Shift on the keyboard and right click and then "open a Command Prompt here"
3- Check if your Sony Xperia Z1s its working well in the adb typing: adb devices. If it says failed, you have to check your adb drivers, if not, you're going good.
4- So if all its going well, just type this on command prompt (Thanks JCASE)
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
5- wait for the adb to finish.
6- Unplug you're phone and restart it.
7- Install Super Su apk (Can download it from Play Store or latest Apk)
8- Open SuperSu and update binarys with Normal Mode
Now you must be Root, if SuperSu can't update Binarys try again from 2.
If this works for you please say thanks to Jcase who made this can be possible.
Click to expand...
Click to collapse
Just use z2 exploit 11 run it twice.
Sent from my C6916 using xda premium
Im getting this error whenever I try open SuperSU.. Tried your method about 6 or 7 times, same error everytime.. any advice?
48bloo said:
Im getting this error whenever I try open SuperSU.. Tried your method about 6 or 7 times, same error everytime.. any advice?
Click to expand...
Click to collapse
Sorry about that, SuperSu its giving to you this error because the rooting it's not done, please check that your phone its adb recognizable with "adb devices" in CMD, Remember to Unistall Super Su if you get the error and Reboot in order to try again.
Damented said:
I tried this but nothing happens I attached what happens in cmd
Sent from my C6916 using XDA Free mobile app
---------- Post added at 08:12 PM ---------- Previous post was at 08:06 PM ----------
not working for me this is what I get in CMD
C:\Root Tool>adb push pwn /data/local/tmp/pwn
2792 KB/s (574722 bytes in 0.201s)
C:\Root Tool>
C:\Root Tool>adb shell chmod 755 /data/local/tmp/pwn
C:\Root Tool>
C:\Root Tool>adb shell /data/local/tmp/pwn
Click to expand...
Click to collapse
Please try again pressing enter just once at each code.
superangel16 said:
Sorry about that, SuperSu its giving to you this error because the rooting it's not done, please check that your phone its adb recognizable with "adb devices" in CMD, Remember to Unistall Super Su if you get the error and Reboot in order to try again.
Click to expand...
Click to collapse
Okay so after working at this for a couple of hours I finally got it to work. For some reason, I wasn't able to uninstall SuperSu because it had been installed as a system app and I could only disable it, or uninstall updates from it. After trying over and over, I found this link.
http://forum.xda-developers.com/showpost.php?p=53442704&postcount=1075&nocache=1&z=9157358331140130
Here, they include the exact same method in this thread, with one extra step; creating a boot script to maintain root/system permissions. Im not exactly sure how it works, but i followed the instructions provided by the links and then, after rebooting, was able to install binaries, and achieve full root (FINALLY!!) So if anybody has the same problem I did, try this out
48bloo said:
Okay so after working at this for a couple of hours I finally got it to work. For some reason, I wasn't able to uninstall SuperSu because it had been installed as a system app and I could only disable it, or uninstall updates from it. After trying over and over, I found this link.
http://forum.xda-developers.com/showpost.php?p=53442704&postcount=1075&nocache=1&z=9157358331140130
Here, they include the exact same method in this thread, with one extra step; creating a boot script to maintain root/system permissions. Im not exactly sure how it works, but i followed the instructions provided by the links and then, after rebooting, was able to install binaries, and achieve full root (FINALLY!!) So if anybody has the same problem I did, try this out
Click to expand...
Click to collapse
Nice! I'm happy To heard that! JCase said in his post that some people will have this problem to write to system, but in my case i was able to, now we have to find a working recovery in order to have a custom rom or something like that, Some people say that xzdualrecovery works for z1s, but it is in beta version, if you find something please let us know.
Guys not to be mean but we posted this a while back shows you how to root what to install for recovery as well as a deodex and perm root http://forum.xda-developers.com/showthread.php?t=2783626
Tactic13 said:
Guys not to be mean but we posted this a while back shows you how to root what to install for recovery as well as a deodex and perm root http://forum.xda-developers.com/showthread.php?t=2783626
Click to expand...
Click to collapse
Oh! Excellent! thank you so much now we can all get the final access, i searched before but no luck, thank you. Now just have to buy a new phone, mine was robbed on friday , just 3 days of use .......
superangel16 said:
Oh! Excellent! thank you so much now we can all get the final access, i searched before but no luck, thank you. Now just have to buy a new phone, mine was robbed on friday , just 3 days of use .......
Click to expand...
Click to collapse
Not full access bootloader is still locked but you can flash things onto your phone and as well as backups. Also sorry on the phone thing.
Tactic13 said:
Not full access bootloader is still locked but you can flash things onto your phone and as well as backups. Also sorry on the phone thing.
Click to expand...
Click to collapse
Hey Thanks for Reply, that's the reason because i said de Final Acces, because we can acces to bootloader because branded phones can't have bootloader unlocked.:fingers-crossed:
Has anyone taken the update? Will we lose root?
POMF2K said:
Has anyone taken the update? Will we lose root?
Click to expand...
Click to collapse
I can't be sure of that because is a said I lose my phone, but ever when you do a official update you lose root.
Sent from my C6603 using XDA Free mobile app
superangel16 said:
I can't be sure of that because is a said I lose my phone, but ever when you do a official update you lose root.
Sent from my C6603 using XDA Free mobile app
Click to expand...
Click to collapse
I did not lose root. I check the box in SuperSU to try to retain root.
Kept root, now I just have to fix all the issues 4.4 has created.
POMF2K said:
I did not lose root. I check the box in SuperSU to try to retain root.
Kept root, now I just have to fix all the issues 4.4 has created.
Click to expand...
Click to collapse
Which box in SuperSU was it?
Doc
superangel16 said:
Please try again pressing enter just once at each code.
Click to expand...
Click to collapse
So you have to enter each line and then enter and then the next line and enter. Correct?
Sent from my C6916 using Xparent Cyan Tapatalk 2
superangel16 said:
Hello Everyone! I would like to make a guide for Rooting our Sony Xperia Z1s for T-mobile, I tried this with Android 4.3 Firmware 14.2.C.0.159.
This is my first Post so if i make a mistake please let me Know.
Thanks to Jcase and his pwn file to make this root Posible.
This is just the way how i did it and worked for me.
I AM NOT RESPOSIBLE FOR BRICKED DEVICES, THIS IS JUST A GUIDE FOR THOSE WHO DON'T KNOW HOW TO USE THE JCASE EXPLOID.
Requirements:
Well, first of all you have to make sure that your computer have the correct adb drivers installed and you can go into it.
Debugging mode On. (Developer options, USB Debugging Checked)
Download the JCASE pwn (http://forum.xda-developers.com/showpost.php?p=53407127&postcount=1004)
Download the Adb Drivers Updated (http://www.mediafire.com/download/41lx6p71xxit1ax/ADB+Drivers_Updated.zip) Thanks to Droidextra.org, UJJWAL KUMAR.
Process:
1- With the two zip files downloaded you will unzip it in the Local Disk (C), Create a folder with a name like "Root Tool" And unzip the files there, just like these: Check attached picture.
2- Press Shift on the keyboard and right click and then "open a Command Prompt here"
3- Check if your Sony Xperia Z1s its working well in the adb typing: adb devices. If it says failed, you have to check your adb drivers, if not, you're going good.
4- So if all its going well, just type this on command prompt (Thanks JCASE)
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
5- wait for the adb to finish.
6- Unplug you're phone and restart it.
7- Install Super Su apk (Can download it from Play Store or latest Apk)
8- Open SuperSu and update binarys with Normal Mode
Now you must be Root, if SuperSu can't update Binarys try again from 2.
If you are not able to Write to system try this: http://forum.xda-developers.com/show...57358331140130
If this works for you please say thanks to Jcase who made this can be possible.
Click to expand...
Click to collapse
Hello, three commands you wrote down. Do I need to write them exactly like that with a space in between each line and then enter? Or do I need to type one command and then ENTER after each command?
Thanks in advance
Sent from my C6916 using Xparent Cyan Tapatalk 2
superangel16 said:
Hello Everyone! I would like to make a guide for Rooting our Sony Xperia Z1s for T-mobile, I tried this with Android 4.3 Firmware 14.2.C.0.159.
This is my first Post so if i make a mistake please let me Know.
Thanks to Jcase and his pwn file to make this root Posible.
This is just the way how i did it and worked for me.
I AM NOT RESPOSIBLE FOR BRICKED DEVICES, THIS IS JUST A GUIDE FOR THOSE WHO DON'T KNOW HOW TO USE THE JCASE EXPLOID.
Requirements:
Well, first of all you have to make sure that your computer have the correct adb drivers installed and you can go into it.
Debugging mode On. (Developer options, USB Debugging Checked)
Download the JCASE pwn (http://forum.xda-developers.com/showpost.php?p=53407127&postcount=1004)
Download the Adb Drivers Updated (http://www.mediafire.com/download/41lx6p71xxit1ax/ADB+Drivers_Updated.zip) Thanks to Droidextra.org, UJJWAL KUMAR.
Process:
1- With the two zip files downloaded you will unzip it in the Local Disk (C), Create a folder with a name like "Root Tool" And unzip the files there, just like these: Check attached picture.
2- Press Shift on the keyboard and right click and then "open a Command Prompt here"
3- Check if your Sony Xperia Z1s its working well in the adb typing: adb devices. If it says failed, you have to check your adb drivers, if not, you're going good.
4- So if all its going well, just type this on command prompt (Thanks JCASE)
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
5- wait for the adb to finish.
6- Unplug you're phone and restart it.
7- Install Super Su apk (Can download it from Play Store or latest Apk)
8- Open SuperSu and update binarys with Normal Mode
Now you must be Root, if SuperSu can't update Binarys try again from 2.
If you are not able to Write to system try this: http://forum.xda-developers.com/show...57358331140130
If this works for you please say thanks to Jcase who made this can be possible.
Click to expand...
Click to collapse
Hey boss, I did everything exactly as instructed and my phone has no problem being identified in adb devices but every time I run the commands I get the first 2 commands looking like it went OK but the last command just can't execute.
C:\Users\TEMP\Downloads\xperia root>adb devices
List of devices attached
CB5A1Z18JC device
C:\Users\TEMP\Downloads\xperia root>adb push pwn /data/local/tmp/pwn
2806 KB/s (574722 bytes in 0.200s)
C:\Users\TEMP\Downloads\xperia root>adb shell chmod 755 /data/local/tmp/pwn
C:\Users\TEMP\Downloads\xperia root>adb shell /data/local/tmp/pwn
/system/bin/sh: /data/local/tmp/pwn: can't execute: Is a directory
C:\Users\TEMP\Downloads\xperia root>
Please help.
Bill Idol said:
Hey boss, I did everything exactly as instructed and my phone has no problem being identified in adb devices but every time I run the commands I get the first 2 commands looking like it went OK but the last command just can't execute.
C:\Users\TEMP\Downloads\xperia root>adb devices
List of devices attached
CB5A1Z18JC device
C:\Users\TEMP\Downloads\xperia root>adb push pwn /data/local/tmp/pwn
2806 KB/s (574722 bytes in 0.200s)
C:\Users\TEMP\Downloads\xperia root>adb shell chmod 755 /data/local/tmp/pwn
C:\Users\TEMP\Downloads\xperia root>adb shell /data/local/tmp/pwn
/system/bin/sh: /data/local/tmp/pwn: can't execute: Is a directory
C:\Users\TEMP\Downloads\xperia root>
Please help.
Click to expand...
Click to collapse
Thank yoy sir for follow my instructions, i am sorry for the delay to answer, i lost my phone. Well i see you are getting a problem to get into the last step in this guide, please check the Jcase post to get you're problem solved; http://forum.xda-developers.com/showpost.php?p=53407127&postcount=1004.
Hope you can solve it!
I am having issues. The first time I tried this I thought it was a success as I went through the steps and got the loading screen on the fire tv to come up. I waited for about 10 minutes and then the firetv reset but Kodi did not install.
Now I am trying to do it and when I hit enter after the string to sideload the .apk nothing happens. I get no response in the terminal and it just goes to the next line. I cannot figure this out for the life of me.
I am using terminal on a mac. This method http://sideloadfiretv.com/sideload-apps-amazon-fire-tv-mac/
please help.
Try the additional "-r" option during install ('-r' means reinstall the app, keeping its data).
For e.g.:
Code:
adb install -r kodi.apk
Calibaan said:
Try the additional "-r" option during install ('-r' means reinstall the app, keeping its data).
For e.g.:
Code:
adb install -r kodi.apk
Click to expand...
Click to collapse
Thanks - I am brand new to mac so this is new to me. So basically my string would be
./adb install /Users/YourUserName/Desktop/-r filename.apk
?
seagood3 said:
Thanks - I am brand new to mac so this is new to me. So basically my string would be
./adb install /Users/YourUserName/Desktop/-r filename.apk
?
Click to expand...
Click to collapse
No. The option "-r" must be used before the complete path to the APK file. Have a look:
Code:
./adb install -r /Users/YourUserName/Desktop/filename.apk
Calibaan said:
No. The option "-r" must be used before the complete path to the APK file. Have a look:
Code:
./adb install -r /Users/YourUserName/Desktop/filename.apk
Click to expand...
Click to collapse
I just tried this and got the same issue where when I hit return, it just drops down to the next line. I don't understand this.
seagood3 said:
I just tried this and got the same issue where when I hit return, it just drops down to the next line. I don't understand this.
Click to expand...
Click to collapse
Couldn't you use adbfire on your mac..... it's available from this link http://forum.xda-developers.com/showthread.php?t=2786505 it might make things a little easier...
slackbladder said:
Couldn't you use adbfire on your mac..... it's available from this link http://forum.xda-developers.com/showthread.php?t=2786505 it might make things a little easier...
Click to expand...
Click to collapse
I haven't used that because I am running into all kinds of issues. First I got the "Can't create log file" error. I googled that and see that I need to drag the app onto the desktop or into the applications folder. The problem is when I try to move it I get another error message "The operation can’t be completed because you don’t have permission to access some of the items". I feel like such a newb with this Mac. I have no clue how to troubleshoot.
any help?
Any chance you have a Windows PC connected to your network that you can try? I did this (http://sideloadfiretv.com/sideload-apps-amazon-fire-tv-windows/) and had no issues.
If you can get ES File Explorer onto the FireTV, then you can go to Network/Cloud and add an account, connected it to a Dropbox account, then just download apks and open them from ES File Explorer, you won't need the PC or adb any more.
seagood3 said:
I just tried this and got the same issue where when I hit return, it just drops down to the next line. I don't understand this.
Click to expand...
Click to collapse
Can you even connect to the aTV?
Try some ADB commands to see if ADB does really work:
Code:
adb devices
This should list all via ADB connected devices. If the list is empty you´re not connected.
When your device is connected try some basic shell commands:
Code:
adb shell
This opens a bash shell. Within this shell type
Code:
ls
and the directory content of the actual folder should be listed.
ADB shell can be left with:
Code:
exit
If this isn´t working, check your ADB version you have installed and try to install a newer/other one. I had such an issue once on Windows with an Android tablet which couldn´t be connected with the ADB version I had already installed on my PC so I took another ADB version and it worked. Of course this shouldn´t be but it seems that this can happen.
Another hint might be your problems regarding adbfire. Perhaps your user restrictions prevent ADB from proper working. I´m not firm on MAC´s but I think they support the "sudo" command (explanation: http://en.wikipedia.org/wiki/Sudo). So try your ADB commands again with an additional sudo before similiar like this:
Code:
sudo adb install kodi.apk
I can't figure this out - I am following this (http://sideloadfiretv.com/sideload-apps-amazon-fire-tv-mac/) perfectly and I got it to work the first time but it just didn't complete it for some reason and now every time when I hit enter on the last step nothing happens.
I can't use the adbfire app because of the other issue.
WTF? why isn't the method through terminal working?
seagood3 said:
I can't figure this out - I am following this (http://sideloadfiretv.com/sideload-apps-amazon-fire-tv-mac/) perfectly and I got it to work the first time but it just didn't complete it for some reason and now every time when I hit enter on the last step nothing happens.
I can't use the adbfire app because of the other issue.
WTF? why isn't the method through terminal working?
Click to expand...
Click to collapse
I don't know...on mac you need to use ./ unless you configure it otherwise so to connect I'd type ./adb connect myipaddress
If you are connecting then you have adb working. I use adbfire but here's what I'd do...
I like keeping my adb folder with platform tools on my desktop. Put the apk you want to install in that folder
type "cd" <space> then drag the whole folder into the terminal--hit enter
now type ./adb connect youripaddress--hit enter
if it says connected type ./adb install<space>then drag the apk from inside your adb folder right into the terminal--hit enter
If you did it right nothing will happen instantly. It depends on how fast your connection is. Wait up to 5 minutes I'd say and you'll either get a success message of an error. If it's the latter, post it here.
Did you read my previous topic and tried what I´ve written?
Forget this Howto since it is just a general guideline and it can´t help you with your actual problem since it is more or less a first time installation guideline but you have already had a previous installation which makes the difference. It can also not deal with restrictions on your system side for e.g. if ADB wouldnt´be allowed to access USB.
If you´re sure that your system is not restricted anyway and ADB should work and if you still prefer to work only with this guideline do a factory reset within your FireTV. This should set the box in a state back again where this guideline should work how it is intended.
Or try SPMC from Amazon App Store which would be the easiest way:
http://www.amazon.com/Semperpax-SPMC/dp/B00MK49LL8