im try to root my Fire v6.3 with KFU v0.9.5. The drivers are installed corrected and my ADB status - online and Boot status - 4000. But when i try and root with option 2(or use any option actually) i see /local/data/fbmode: permission denied
Can anyone tell me what my issue is?
thanks guys.
Change the permissions of fbmode. In command prompt, navigate to the KFU folder that contains adb.exe and enter...
adb shell chmod 775 /data/local/fbmode
...and try again
Sent from my Amazon Kindle Fire using xda premium
i tried that and i'm still getting permission denied. I've been messing about with this for a few days now. I just copied and pasted what you told me to type. I actually tried "adb shell chmod 755 /data/local/fbmode" i saw that on another website. Still no working!
Any other tips?
thanks
[Edit:] I changed my mind
Instead, try rooting manually. Without KFU.
http://forum.xda-developers.com/showthread.php?p=24124828
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
[Edit:] I changed my mind
Instead, try rooting manually. Without KFU.
http://forum.xda-developers.com/showthread.php?p=24124828
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
i just finished trying that and got permission denied on this line "adb shell /data/local/fbmode". I'm quickly exhausting all options. I've tried on 2 pc's, one running xp and one running windows 7 and get to the same stage!
Did you "adb root" and "adb remount" to mount system as read/write?
Sent from my Amazon Kindle Fire using xda premium
i managed to get it rooted manaully using /tmp/ in the comand lines as below.
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
Came across it on a thread on here. Thank for you help man
Related
Here's how to unroot Kindle fire using adb, works on Windows, Mac, and Linux:
Step 1. Download adb.zip and unzip, you should get a folder called adb.
Download adb.zip
Step 2. Open up a command prompt or terminal and type:
For Windows:
cd \adb
For Mac or Linux:
cd /adb
Step 3. Type the following to get into ADB shell:
For Windows:
adb shell
For Mac:
./adb-mac shell
For Linux:
./adb-linux shell
Step 4. Copy and paste the following to enable read/write on filesystem:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Step 5. Type the following to remove rooting files:
rm /system/app/Superuser.apk
rm /system/bin/su
rm /system/xbin/su
Step 6. Type the following to reboot and your Kindle Fire should be fully unrooted!
reboot
Excellent instructions for both root and unroot, thank you. I wasn't aware of typing "su" though before step 4. Thankfully you covered that in the video.
Yes, should edit to mention su
Awesome!
Sent from my Kindle Fire using Tapatalk
Yep, nice concise post, but need to add a couple of things:
1. su before the mount command.
2. /system/bin/su doesn't always exist as it depends on what root method you used.
For me, only the xbin version existed, so people shouldn't freak out if they get a "No such file or directory" message!
Ota rootkeeper
Once the Kindle Fire is rooted, OTA ROOTKEEPER app allows you to easily root/unroot (i.e. you want to see Amazon Premium videos. Only allowed if unrooted.)
Once you unroot/root with OTA Rootkeeper, you will need to restart for new settings to take.
To see youtube video, search OTA Rootkeeper Kindle.
Download via Google Android Market.
Works great
ByByIpad said:
Once the Kindle Fire is rooted, OTA ROOTKEEPER app allows you to easily root/unroot (i.e. you want to see Amazon Premium videos. Only allowed if unrooted.)
Once you unroot/root with OTA Rootkeeper, you will need to restart for new settings to take.
To see youtube video, search OTA Rootkeeper Kindle.
Download via Google Android Market.
Works great
Click to expand...
Click to collapse
Definitely and so easy.
ByByIpad said:
Once you unroot/root with OTA Rootkeeper, you will need to restart for new settings to take.
Click to expand...
Click to collapse
I'll save you the trouble of rebooting...
Just stop the Amazon video app. There is no need to reboot. I use Advance Task Manager Pro personally because I purchased it for use with my Archos tablets but it isn't necessary you can do it through Settings-> Applications also.
Sent from my HTC Flyer P512 using Tapatalk
ByByIpad said:
Once the Kindle Fire is rooted, OTA ROOTKEEPER app allows you to easily root/unroot (i.e. you want to see Amazon Premium videos. Only allowed if unrooted.)
Once you unroot/root with OTA Rootkeeper, you will need to restart for new settings to take.
To see youtube video, search OTA Rootkeeper Kindle.
Download via Google Android Market.
Works great
Click to expand...
Click to collapse
Thanks SO MUCH! Definitely add this to your Kindle if you're trying to keep hacking it but can't stand to be without all six seasons of LOST.
Mount Issue
When I run the command to mount i get the following error:
mount: Operation not permitted
I'm using Mac OS 10.7.2
Nevermind!! Just had to see the "su" command in the tutorial. Sorry.
I have to unroot so I can send my KF back to Amazon.
If I user the OTA RootKeepr, is their anyway for them to figure out it was rooted? Once I use that app, I just wipe my KF? Thats it?
Just update to 6.2.1 and it should wipe it.
Sent from my Kindle Fire using xda premium
borborpa said:
Just update to 6.2.1 and it should wipe it.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I apologize but do I update? My KF says 6.2_user right now.
---------- Post added at 07:53 AM ---------- Previous post was at 07:07 AM ----------
c:\>cd adb
c:\adb>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
What am I doing wrong?
OTA Rootkeeper is freaking awesome! My mom was so bummed after I rooted her KF and found out she couldn't watch movies anymore. This saved my bacon.
Sent from my EPAD using xda premium
I unrooted but still cannot view prime videos. Any suggestions?
Hi... I have a kindle fire ver 6.3 I am trying to unroot it but when i get to adb shell, it said device not found... i have installed android sdk, and kindle driver but no help... please advise!
Thanks for the nice contribution! Covered both! No need to worry how to root or unroot.
Would like to read more tips on using the Kindle Fire as the tablet column I came across in aneesoft.
Cheer!
I followed the method and unrooted my kindle. I found one issue after rebooting , it gave error " android.process.acore" has stopped working. As per Zedomax suggestion, I did Factory reset and problem was solved
Thanks for helping!!
hello,
this is a quick guide i made to help make it easier to install recovery tools and custom roms
I found that all the other guides were half correct and found myself referencing many different guides to figure it out
so after spending 5 hours doing my first kindle fire
about 1 hour on my second kindle fire
and about 5 mins on my third kindle fire
I think this guide should help some people out
thanks in advance to everyone and please leave constructive criticism or comments!!
//after rooting
---------------------------------
make sure you have in >C:\program files\android\android-sdk\platform-tools
---------------------------------
-log
-last log
-update.zip
-updaterecovery.img //if you are using Clockwork Mod
or
-twrp.img //if you are using TWRP recovery
---------------------------------
//cmd.exe
>cd C:\program files\android\android-sdk\platform-tools
>adb devices
//make sure device shows up
>adb shell
>cd cache
>mkdir recovery
>exit
>adb push log /cache/recovery/
>adb push last_log /cache/recovery/
>adb push update.zip /sdcard/
>adb push updaterecovery.img /sdcard/
>adb shell
>dd if=/sdcard/updaterecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
>idme bootmode 0x5001
>reboot
//on kindle go through CM recovery and install update.zip
>adb reboot
>adb shell
>mount sdcard
>exit
>adb push stockrecovery.img /sbin/
>adb shell
>dd if=/sbin/stockrecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
>idme bootmode 0x5001
>exit
>adb reboot
follow this lower section if you are using TWRP 2.0
----------------------------------------------------------------
//if you are using twrp you need to change
//"updaterecovery.img" >to> "twrp.img" ---see below
// "dd if=/sdcard/twrp.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
//
>adb push twrp.img /sdcard/
// if you are using twrp.img and are stuck in bootloop
//you need to do the following commands after twrp 2.0 installs and reboots
>adb shell
>idme bootmode 4000
>reboot
----------------------------------------------------------------
//all done
Why not just use KFU? It does great with all this being scripted, etc.
---Saving For Later---
DeerSteak said:
Why not just use KFU? It does great with all this being scripted, etc.
Click to expand...
Click to collapse
Where might that be??
Sent from my ICS Captivate
The sticky at the top of the Kindle Fire forum?
Kindle Fire Utility...its in the very first post in this forum, stickied at the top.
It took me 5 minutes to root mine and that was before kfu was released. Biggest problem I had was when it was in fastboot mode, windows dropped the drivers. Only took a second to see the issue and correct it and finish it out. I did keep mine stock but rooted and no recovery till 6.2.1 came out. Then I installed twrp and installed pre-rooted 6.2.1. Now I'm running cm7 until ics is worked out.
Good option
Another good option over the KFU. If you want to play around yourself so you can learn more about adb and cmd prompts this is a good way to do things. This is way simpler than some of the old instructions, but more hands on than the KFU.
installing twrp thru this method won't work, twrp installs fff at the same time so
Sent from my HTC Glacier using xda premium
smirkis said:
installing twrp thru this method won't work, twrp installs fff at the same time so
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
then how do i have twrp and fff on my kindle fire?
Hi all,
I have a kindle fire with system version 6.3_user_4019920.
I used Kindle Fire Utility 0.9.5, installed TWRP, FFF and Permanent Root with Superuser (option 2).
I did NOT installed Google Apps/Go Luncher EX though!
Everything went just fine with no errors at all.
I installed ProxyDroid 2.6.2 and that tells me that I am not root. I checked also to see if the device is rooted installing Root Checker app and that tells me also: "Sorry, you don't have root access"
Any help would be appreciated!
Regards,
osceoladad said:
Hi all,
I have a kindle fire with system version 6.3_user_4019920.
I used Kindle Fire Utility 0.9.5, installed TWRP, FFF and Permanent Root with Superuser (option 2).
I did NOT installed Google Apps/Go Luncher EX though!
Everything went just fine with no errors at all.
I installed ProxyDroid 2.6.2 and that tells me that I am not root. I checked also to see if the device is rooted installing Root Checker app and that tells me also: "Sorry, you don't have root access"
Any help would be appreciated!
Regards,
Click to expand...
Click to collapse
I have this problem too, KFU doesn't seem to copy su binary to /system/xbin, so just do it your self from adb (su binary located in the "files" folder inside KFU), then set permission to it as 06755, finally open install Superuser.apk.
Reboot into recovery mode
adb shell mount system
adb push ..\files\su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install ..\files\Superuser.apk
Thank you.
I did all steps, but at the last command (adb install ..\files\Superuser.apk) I got the following error:
/sbin/sh: pm: not found
osceoladad said:
Thank you.
I did all steps, but at the last command (adb install ..\files\Superuser.apk) I got the following error:
/sbin/sh: pm: not found
Click to expand...
Click to collapse
You must boot out of recovery and back into the system before executing the adb install command.
kinfauns said:
You must boot out of recovery and back into the system before executing the adb install command.
Click to expand...
Click to collapse
Thanks,
I saw that KFU was showing 5000 status mode. So, I did: "fastboot oem idme bootmode 4000" I got an OKAY on the PC screen and now the Kindle Fire is stucked at the logo (I cannot even power it off). I disconnected and reconnected but know even the computer is not recognizing it.
Any other suggestions?
osceoladad said:
Thanks,
I saw that KFU was showing 5000 status mode. So, I did: "fastboot oem idme bootmode 4000" I got an OKAY on the PC screen and now the Kindle Fire is stucked at the logo (I cannot even power it off). I disconnected and reconnected but know even the computer is not recognizing it.
Any other suggestions?
Click to expand...
Click to collapse
That only changes the bootmode. You need to actually tell it to reboot.
Code:
fastboot reboot
Maybe you want to read the first few posts of this link...
http://forum.xda-developers.com/showthread.php?t=1552547
It will help you understand what you are doing rather than just typing commands.
kinfauns said:
That only changes the bootmode. You need to actually tell it to reboot.
Code:
fastboot reboot
Maybe you want to read the first few posts of this link...
http://forum.xda-developers.com/showthread.php?t=1552547
It will help you understand what you are doing rather than just typing commands.
Click to expand...
Click to collapse
That is exactly the article from were I have the command. Unfortunetly because the kindle is now stucked at the logo (cannot turn it off) even if I issue fastboot reboot is waiting for a device that is not recognized.
osceoladad said:
That is exactly the article from were I have the command. Unfortunetly because the kindle is now stucked at the logo (cannot turn it off) even if I issue fastboot reboot is waiting for a device that is not recognized.
Click to expand...
Click to collapse
Hold the power button until it shuts off. Then restart.
First what is the charge level on your battery that can happen from your battery being flat also maybe try powering it off by holding the power button for 20 seconds till it does completely power down some say to reinstall your drivers but I can't imagine why how and where they could have changed considering how far you have gotten
It worked and I was able to finishe the rooting also.
Thanks for all guys who replied, wasted their time and helped me out!
I needed all this because of a Europe trip and I run a Squid proxy here in US that I want to use it for netflix. Hopefully ProxyDruid will help me out.
Best,
I'm having a similar problem. I used KFU 0.9.6 and installed permanent root and twrp. I've even flashed the latest jandycane ROM. It's super stable and have had no problems except that I can't run apps that require root. The root checker says I don't have root. I tried running the above adm commands but with no luck. Any help is appreciated.
Sent from my Amazon Kindle Fire using Tapatalk 2
mcqueena9845 said:
I'm having a similar problem. I used KFU 0.9.6 and installed permanent root and twrp. I've even flashed the latest jandycane ROM. It's super stable and have had no problems except that I can't run apps that require root. The root checker says I don't have root. I tried running the above adm commands but with no luck. Any help is appreciated.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Enter the following command and post the results:
adb shell ls /system/xbin | grep '\bsu\b'; echo $?
Click to expand...
Click to collapse
soupmagnet said:
Enter the following command and post the results:
Click to expand...
Click to collapse
I'm not on mac or linux so the grep command fails. The output of
Code:
adb shell ls /system/xbin/su
is
Code:
/system/xbin/su
---------- Post added at 04:39 PM ---------- Previous post was at 03:57 PM ----------
I ran the utility again. Now /system/xbin/su is a symbolic link to /system/bin/su. The output of
Code:
adb shell ls -al /system/xbin/su
is
Code:
lrwxrwxrwx root root 2012-10-10 16:29 su -> /system/bin/su
and the output of
Code:
adb shell ls -al /system/xbin/su
is
Code:
-rwsr-sr-x root root 173934 2008-08-01 08:00 su
Sorry, it's easy for me to forget about you windows users
Do you have terminal emulator?
See if the "su" command is successful.
soupmagnet said:
Sorry, it's easy for me to forget about you windows users
Do you have terminal emulator?
See if the "su" command is successful.
Click to expand...
Click to collapse
Code:
/system/bin/sh: /system/bin/su: not executable: magic 7F45
Apparently your su binary is corrupt. Use adb shell to remove it and then adb push a new version to your /system/xbin folder. Afterwards (adb shell) chown and chmod to give it the proper ownership/permissions and try again.
I'm assuming you already know how to do this.
---------- Post added at 05:06 PM ---------- Previous post was at 04:59 PM ----------
Upon further inspection, it seems as though you installed the wrong su binary. There are two available; x86 and ARM. You need ARM.
Thanks for the help. I pushed a new su file. Now it says permission denied. What should the permissions be set to? I tried 06755 as above but no luck.
Sent from my PC36100 using Tapatalk 2
Code:
adb shell
chown 0.0 /system/xbin/su
chmod 755 /system/xbin/su
Then try su in terminal emulator
Still getting permission denied.
Sent from my Amazon Kindle Fire using Tapatalk 2
mcqueena9845 said:
Still getting permission denied.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Sorry, I told you wrong.
Code:
adb shell chmod 06775 /system/xbin/su
Last night I tried to root a Fire (6.3.1) for the first time using KFU and briefly saw something flash by about a problem with check_rooted. Someone on the KFU thread mentioned this also. Does this mean the rooting process is incomplete?
Proceeding further, I attempted to install the optional apps and received permission denied errors when abd went to push the vending GoogleCalendarSyncAdapter and GoogleContactsSyncAdapter apk files to /system/app.
Reading further on the KFU thread, someone else suggested sideloading superuser. I did this and still was unable to manually push the files (following the batch file as a model to mount read/write, push the apps, then mount read-only).
The goal was to add access to Google Play to an otherwise stock 6.3.1 operating system. Short of loading a new rom, is there something else I might try?
SLOmtb said:
Last night I tried to root a Fire (6.3.1) for the first time using KFU and briefly saw something flash by about a problem with check_rooted. Someone on the KFU thread mentioned this also. Does this mean the rooting process is incomplete?
This is typically nothing to worry about. You will receive an error if the "check_rooted" folder didn't exist to begin with. Normal
Proceeding further, I attempted to install the optional apps and received permission denied errors when abd went to push the vending GoogleCalendarSyncAdapter and GoogleContactsSyncAdapter apk files to /system/app.
Reading further on the KFU thread, someone else suggested sideloading superuser. I did this and still was unable to manually push the files (following the batch file as a model to mount read/write, push the apps, then mount read-only).
Click to expand...
Click to collapse
The method for doing this is
Code:
adb root
adb remount
adb push ≤filename1≥ /system/app
adb push ≤filename2≥ /system/app
...when finished...
Code:
adb remount
adb kill-server
The goal was to add access to Google Play to an otherwise stock 6.3.1 operating system. Short of loading a new rom, is there something else I might try?
Click to expand...
Click to collapse
To make things simple, the MoDaCo rom has the exact same interface as stock, except it comes pre rooted with all of the Google apps and services already installed. No work is necessary.
Wow! I'll give it a try tonight. Thanks!
soupmagnet said:
The method for doing this is
Code:
adb root
adb remount
adb push ≤filename1≥ /system/app
adb push ≤filename2≥ /system/app
...when finished...
Code:
adb remount
adb kill-server
To make things simple, the MoDaCo rom has the exact same interface as stock, except it comes pre rooted with all of the Google apps and services already installed. No work is necessary.
Click to expand...
Click to collapse
Well, darn. I tried "adb root" and it says: "adbd cannot run as root in production builds." So I guess it isn't really rooted, after all.
Maybe the MoDaCo rom is the way to go, after all. Thanks, anyway!
adb devices
list of device attached
5A5A5A5A5A5A..... (NOT CORRECT)
adb shell
[email protected]
adb push flash_image /dev/
failed .... permission denied
adb push recovery.img /dev/
failed .... permission denied
what should I do ?
sabithpkcmnr said:
adb devices
list of device attached
5A5A5A5A5A5A..... (NOT CORRECT)
adb shell
[email protected]
adb push flash_image /dev/
failed .... permission denied
adb push recovery.img /dev/
failed .... permission denied
what should I do ?
Click to expand...
Click to collapse
The which system version?
Sent from my XT894 using Tapatalk
sd_shadow said:
The which system version?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Thanks for interesting ,,
I am on leave for many days over my exam fear ..
any way , I am having Android 4.1.1 JB tablet
sabithpkcmnr said:
Thanks for interesting ,,
I am on leave for many days over my exam fear ..
any way , I am having Android 4.1.1 JB tablet
Click to expand...
Click to collapse
That's Android version, not system version
Sent from my XT907 using Tapatalk
I rooted my KFHD 8.9, installed the Play Market, Go Launcher HD, and a few other things. Everything went smoothly...until I decided to install TSF Shell 3d. I moved it to system/app, changed permissions, and rebooted. Now, TSF is stuck in a loop and I can't access ES File Explorer long enough to delete it from the device. When I try using Android Commander, it shows "No Root" and I'm not very experienced at ADB. Is there some way to get this off my device so it's usable again?
When I boot up, it boots normally, then before I can unlock the lockscreen, I get "TSF Shell has Stopped" with a button below it to ok the message. When I tap it, it goes away for a split second, then comes right back...over and over.
Any tips or advice would be greatly appreciated. Thanks.
(I posted this here because I did not see a Q and A or Help section that was KFHD 8.9 specific. If it needs to be moved, feel free and I apologize.)
couple of things to try. if you can access the pull down menu go to more settings, applications then find tsf shell and clear defaults. reboot.
if that doesn't work reboot to recovery and do a factory reset.
adb reboot recovery.
I will try the adb reboot recovery option. I can't get into anything on the device itself long enough to do anything. Also, I didn't even set TSF as default home. I'm thinking (the way adb is acting), that I don't have full root privileges. When I try to delete the file using adb, I get a permission denied error.
slim6596 said:
I will try the adb reboot recovery option. I can't get into anything on the device itself long enough to do anything. Also, I didn't even set TSF as default home. I'm thinking (the way adb is acting), that I don't have full root privileges. When I try to delete the file using adb, I get a permission denied error.
Click to expand...
Click to collapse
Have you tried:
Code:
adb shell su -c "rm /path/to/TSF.apk"
...replacing "/path/to/TSF.apk" with the actual path to the actual name of the TSF app you want deleted? Just be sure to leave the quotes around the command or it may not work.
soupmagnet said:
Have you tried:
Code:
adb shell su -c "rm /path/to/TSF.apk"
...replacing "/path/to/TSF.apk" with the actual path to the actual name of the TSF app you want deleted? Just be sure to leave the quotes around the command or it may not work.
Click to expand...
Click to collapse
I tried adb shell su -c rm/system/app/TSF Shell 3D
"permission denied" and then "device not found" when I tried editing the pathname. What am I missing? The path to the Kindle?
slim6596 said:
I tried adb shell su -c rm/system/app/TSF Shell 3D
"permission denied" and then "device not found" when I tried editing the pathname. What am I missing? The path to the Kindle?
Click to expand...
Click to collapse
There is a space between the 'rm' command and the path. Also you need to get the exact name of the file you want removed...
Code:
adb shell su -c "ls /system/app"
And again, don't forget the quotes...meaning leave them there.
"Is" or "rm"?
........and thanks for trying to help me out. I really appreciate it.
slim6596 said:
"Is" or "rm"?
........and thanks for trying to help me out. I really appreciate it.
Click to expand...
Click to collapse
'ls' is the list command. Use it to list the contents of either the '/system/app' directory or the '/data/app' directory to find the exact name of the 'apk' that is causing problems, then use the 'rm' (remove) command to get rid of it.
I got it to work. TSF is gone (yahoo!). So now I get to start over. What I finally did was to do a total restore using KFFirstAide. Thanks you guys for pitching in and helping a newb. I appreciate it to no end.