Database Users

Default android lockscreen

Is it possible to change the lockscreen to the default android, i'm new to android nd still tryna get a hold of things. Thanks
-------------------------------------
Sent via the XDA Tapatalk App

lakeside00 said:
Is it possible to change the lockscreen to the default android, i'm new to android nd still tryna get a hold of things. Thanks
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
you can remove the HtcLockScreen.apk from /system/app/ and it will default to the stock android one. Problem is that is suffers from the same fate as many others where the slder is up/down and the time is jummbeled on the left side.
Oh and of course to remove/rename the file in /system/app/ you must be rooted and in recovery mode.
I'm working on how to fix the screen. Flipz did it for android 2.0 but it isn't the same fix in 2.1. If I get more info I'll post back.

I tried to remove HtcLockScreen.apk via adb but I don't think we have system write access yet. even through adb. someone correct me if I'm wrong but I believe this is true.
Edit: As said above... you have to be in recovery. I stand corrected. don't listen to me!
edit #2: tried it in recovery... couldn't even remount. I don't think I did anything wrong...

gmelchert said:
I tried to remove HtcLockScreen.apk via adb but I don't think we have system write access yet. even through adb. someone correct me if I'm wrong but I believe this is true.
Edit: As said above... you have to be in recovery. I stand corrected. don't listen to me!
edit #2: tried it in recovery... couldn't even remount. I don't think I did anything wrong...
Click to expand...
Click to collapse
LOL! love the step by step edits...
I have a script that makes it easy, it is just a modified version of Toast's. It cuts it down to one command input instead of three.
Any way here are the steps:
With phone on plug it into your computer. Open two command windows. Navigate one to the folder you have downloaded toasts recovery script to.
1) In the window that is at evo-recovery> type: adb reboot recovery
This boots you in to the stock recovery
2)in the same window type windows-recovery.bat (adjust for your OS)
This gets you into Amon-RA's recovery
3) Wait for the phone to get the new recovery screen. In the other command window type: adb shell mount -a
Step 3 can be adb remount or you can type adb shell then at the # type #mount -t yaffs2 -o remount,rw /dev/block/mtdblock4 /system
Any way after that point you can exit adb shell back to the command prompt and push/pull anything to /system
unfortunately you can't see it right away and have to wait for reboot. Also this limits some of the apps that we can install because some will need to write to /system and cannot once rebooted.

[Q] Is it possible to push apps via adb to an encrypted xoom?

the subject says it all. I've been trying to push apps to my encrypted xoom all afternoon without any luck...
I'll go ahead and admit upfront that I am a noob when it comes to using the sdk... so that could also be a major factor.

adb install (insert exact location+ filename.apk for the app you want to install)
I just tested it out
for example
adb install C:/abc.apk

What command are you using? What error message are you getting? Did you do a adb remount to make sure that the /system/app path is writable?
You can always do an adb install [package name].apk as well.

scsa20 said:
What command are you using? What error message are you getting? Did you do a adb remount to make sure that the /system/app path is writable?
You can always do an adb install [package name].apk as well.
Click to expand...
Click to collapse
I just tried to execute adb remount (I had not until you mentioned it), but I get a "remount failed: operation not permitted".
Code:
Hannibal:platform-tools dmoore$ ./adb install /Users/dmoore/Documents/android-sdk/platform-tools/AsusReader.apk
1259 KB/s (7747001 bytes in 6.007s)
pkg: /data/local/tmp/AsusReader.apk
Failure [INSTALL_FAILED_DEXOPT]
Additional information: I am on a MacBook Pro using the latest version of the SDK (downloaded it yesterday).

try typing "adb devices" if it does not list your xoom try installing or re-installing the motorola usb drivers
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
just noticed the macbook part
http://www.samsung-tablets.com/motorola-xoom-usb-driver-for-pc-and-mac-download.html/

Ok... back to me being a complete when it comes to the SDK (and the Xoom in particular)...
My Xoom is completely stock... it has not been rooted or otherwise modified.
With that being said, is there some trick to getting the file system to mount as r/w? Do I need to reboot in to recovery before adb remount will work?

Sic123 said:
just noticed the macbook part
http://www.samsung-tablets.com/motorola-xoom-usb-driver-for-pc-and-mac-download.html/
Click to expand...
Click to collapse
I've already installed the Android File Transfer app... it only allows me to browse the SD card - not the root fs... unless there's something I'm missing...

dmoore44 said:
Ok... back to me being a complete when it comes to the SDK (and the Xoom in particular)...
My Xoom is completely stock... it has not been rooted or otherwise modified.
With that being said, is there some trick to getting the file system to mount as r/w? Do I need to reboot in to recovery before adb remount will work?
Click to expand...
Click to collapse
you dont have to be in recovery (recovery wont do any good unless you install clockwork recovery) for adb remount to work but if your not rooted you cant push files into the system folder thats the whole point of rooting is to unlock the system files also if your pushing it into /system/app the rom is odexed so you will need the apk plus the odex file

Sic123 said:
you dont have to be in recovery (recovery wont do any good unless you install clockwork recovery) for adb remount to work but if your not rooted you cant push files into the system folder thats the whole point of rooting is to unlock the system files also if your pushing it into /system/app the rom is odexed so you will need the apk plus the odex file
Click to expand...
Click to collapse
I have the odex file, so i'm not terribly worried about that.
My major question would be this though... Do I need to go full blown root, or can I just unlock the device?

[Solved] 6.2.2 Bricked Please Help

Ok, so I did something stupid, I tried to install a slider lock theme on my kindle and probably screwed up the Framework-Res. I did not have TWRP or a backup of any kind.
Now the kindle just sits at the boot splash screen.
The device was running on 6.2.2 and most tutorials seem to be made for 6.2.1
I have tried a few manual commands but remount is just say "Operation Not Permitted" (I cant figure out how to fix this either.
Running automated programs like Unbrick Utility just don't work, it says it has completed but you can see a bunch of errors saying it could not copy or not permitted etc...
At this point I just want my kindle fire back even if that means a complete restore, can someone please try to help or point me in the right direction I am about to go insane.
Added Info: To be more exact, I tried to use metamorph to install a slider lock theme, nothing seemed to happen so I closed the app. I thought everything was fine so I put the kindle to sleep, but I could not wake it up. I tried restarting it and that's how I got to were I am now.
Update:
Thanks to b63 I was able to get this fixed, I cant thank him enough.
Ok here is how I got it fixed
First I followed the directions given to me below by b63
he told me to refer to this http://forum.xda-developers.com/show...8&postcount=29 which I did, however When I got to 8 I did something different, I did not need to re install the whole Rom because I had only messed up the Framework-res.apk
So instead I pulled the Framework-res.apk from /system/framework in the official kindle 6.2.2 update.zip
I then used these commands to replace the broken apk on the device and restart in normal boot mode.
4. "adb remount"
5. "adb push framework-res.apk /system/framework/framework-res.apk"
6. "adb shell chown root /system/framework/framework-res.apk"
7. "adb shell chmod 644 /system/framework/framework-res.apk"
8. "adb shell idme bootmode 4000"
9. "adb reboot"
I know that this explanation is not super descriptive but most of what you need can be found below in the thread.
This problem is rather specific to my situation so if you are having the same problem and you can't figure it out send me a PM or reply to this thread.

Anyone? I'm starting to think i should just try to return it.

would need some more concrete information:
is it rooted only ?
what is the boot splash screen "kindle fire" (static or animated) or yellow triangle ?
do you have kfu available ?
moved and renamed so that it is at c:\kfu ?
patched the run.bat of kfu ?
what are the 3 status lines of kfu when you just start it ? - please don't do any option at the moment
os/bit of computer ?
driver status in device manager ?

b63 said:
would need some more concrete information:
is it rooted only ?
what is the boot splash screen "kindle fire" (static or animated) or yellow triangle ?
do you have kfu available ?
moved and renamed so that it is at c:\kfu ?
patched the run.bat of kfu ?
what are the 3 status lines of kfu when you just start it ? - please don't do any option at the moment
os/bit of computer ?
driver status in device manager ?
Click to expand...
Click to collapse
Thank you for the response, I'm not at my normal Computer now, but I will answer what I can from here.
Yes I believe it is rooted only, no roms or anything installed.
The Splash screen is Kindle Fire, It is static (no shine animation). I also never installed TWRP or firefirefire so I don't think it should be yellow. (I tried though)
I do have KFU available, but I'm getting operation not permitted errors
No I did not move/rename it (maybe that's the not permitted issue?)
Three Lines: ADB Status: Online ADB Rooted: No (it was rooted) Boot Status: 4000
Vista 32 Bit
Cant check at the moment (however I believe the drivers are working properly)
Thank you for the response Ill try to help the best I can, Im pretty techy but Ill admit I'm a noob at ADB

Damieok said:
Thank you for the response, I'm not at my normal Computer now, but I will answer what I can from here.
Yes I believe it is rooted only, no roms or anything installed.
The Splash screen is Kindle Fire, It is static (no shine animation). I also never installed TWRP or firefirefire so I don't think it should be yellow. (I tried though)
I do have KFU available, but I'm getting operation not permitted errors
No I did not move/rename it (maybe that's the not permitted issue?)
Three Lines: ADB Status: Online ADB Rooted: No (it was rooted) Boot Status: 4000
Vista 32 Bit
Cant check at the moment (however I believe the drivers are working properly)
Thank you for the response Ill try to help the best I can, Im pretty techy but Ill admit I'm a noob at ADB
Click to expand...
Click to collapse
ok i see a lot out of this - thanks
would recommend to do the move/rename of kfu to sort out any additional problems
you should have adb commands available and the kf is in normal boot mode
now the ultimate test is to issue:
"adb shell"
- if it goes into the shell ($ or # prompt) you can resume
- if it responds something like <exec "system/bin/sh": No such file or directory> then there is no possibility to get to fastboot mode to install fff and twrp which is necessary to install a fresh rom - if this is the case your only solution is to build or buy a "factory cable" - look at this thread :
http://forum.xda-developers.com/showthread.php?t=1392693

b63 said:
I would recommend to do the move/rename of kfu to sort out any additional problems
you should have adb commands available and the kf is in normal boot mode
now the ultimate test is to issue:
"adb shell"
- if it goes into the shell ($ or # prompt) you can resume
- if it responds something like <exec "system/bin/sh": No such file or directory> then there is no possibility to get to fastboot mode to install fff and twrp which is necessary to install a fresh rom - if this is the case your only solution is to build or buy a "factory cable" - look at this thread :
http://forum.xda-developers.com/showthread.php?t=1392693
Click to expand...
Click to collapse
Ok so I renamed the "Kindle Fire Utility" folder to "kfu" moved it to C:\
(if this is incorrect please let me know.)
And good news, adb shell responds with $, were should I go next. (also I have access to my normal computer now)
Thanks again for helping me out with this.

great !!! - simply try to follow this post starting at point 2:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
place the downloaded files in the tools folder of kfu since you are doing the commands from there

b63 said:
great !!! - simply try to follow this post starting at point 2:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
place the downloaded files in the tools folder of kfu since you are doing the commands from there
Click to expand...
Click to collapse
Im a little confused at this guide are the commands being entered into adb or in kfu? Were does kfu come into play?
Sorry the guide is a little hard to understand

it' not so complicated as it sounds ...
open a elevated command prompt and cd to c:\kfu\tools
here are all commands you need and where kfu comes in play
- you don't need kfu itself - only the tools folder
- leave the command window open all the time

[Q] Editing Build.prop results in failure to boot [bricked]

As you may know, some Android games especially most Gameloft games are not compatible with the Kindle Fire. So in efforts to find a way to make certain Gameloft games to work such as Modern Combat 2 and Shrek Kart and others, I resorted to editing my build.prop in the systems folder to make my device compatible with the apps. So I copied the original build.prop file, renamed it, and saved it to my SD Card folder. I took the copy I made and I then replaced it with the build.prop from HTC Glacier. (I never knew what could possibly happen) So then to apply those settings you have to reboot the device. I rebooted the Kindle and now it won't boot up. It get's to the Kindle Fire screen when booting up but after several seconds it just shows a black screen. No physical damage has been incurred to it but I feel like my stupid mistake of modding the build.prop resulted in the Kindle Fire unable to boot up correctly. It also isn't recognized by the PC when I hook it up to a USB cable. So far I've found nothing that could help to solve this. I've seen a Factory Default Settings Cable which is a special cable to reverts the device to its factory default settings but I'm not too sure if that would work. I'm in desperate need of help as in I use my Kindle Fire for everyday work and play. Thanks.
EDIT: I've tried adb push and renaming and moving the build.prop into the /system/ but returns that it is a Read-File System Only. Also adb shell and su doesn't work as in it ends up with segmentation fault. I've tried to zergRush root it and permanently root it using KFU but it ends up with 'Cannot Access Package Manager. Is System running?' Also the mount -o rw,remount.....command doesn't work either as it says Permission Denied. All of this would be easy to accomplish if only it ADB allowed me to write onto the /system file.
EDIT**: The biggest issue I'm faced with is the permission settings that prevent my from editing anything. You cannot simply change it from RO to RW because apparently the ADB is not rooted. And I also can't root it because problems exist when accessing either Package Manager or Activity Manager. What I need is a way to access the /system files without a root (non-rooted). Either that or enable fastboot because I cannot access that either. On a reply on the second page is the resulting lines when changing bootmodes on the KFU.

Don't know how to fix your problem, but just wondering, did you just completely replace the kindle fire build.prop with the HTC glacier? Because you can't do that, it will, as you have learned, mess up your device.. Your supposed to edit the build.prop and just change a few things. Next time read up on the subject before deciding to mod the device you use everyday...

the cable you'r talking about is a "factory cable" it forces the kf to fastboot mode - it don't restore any settings !
you need fastboot mode to install fff (firefirefire - custom bootloader) and twrp (recovery)
do you allready have installed fff & twrp (or cwm) ?
if you have twrp installed and booted into then you have adb command available and can copy back the original build.prop

Did you remember to restore the read/write permissions to build.prop? It should be set to 644.

As already stated, your not supposed to replace the whole file, build.prop tells android which device you have, so now Android thought and configured itself to different hardware config. which is not available to it. Adb seems like the only option.

I should have really looked more into it before modifying the build.prop. I replaced the ENTIRE build prop with the build.prop of HTC Glacer. (I know, i know I was stupid) And referring to the factory cable, I don't think I'll resort to that: too time consuming. In regards to the last person that posted before me who said that my only option was ADB could you elaborate? Thanks for all your feedback.

gococogo321 said:
I should have really looked more into it before modifying the build.prop. I replaced the ENTIRE build prop with the build.prop of HTC Glacer. (I know, i know I was stupid) And referring to the factory cable, I don't think I'll resort to that: too time consuming. In regards to the last person that posted before me who said that my only option was ADB could you elaborate? Thanks for all your feedback.
Click to expand...
Click to collapse
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium

You dont have access to recovery? Either TWRP or CWM?

daggy1985 said:
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I tried doing that but it says something like Access Denied or Read-Only File System when i try to push the build.prop into it.

gococogo321 said:
I tried doing that but it says something like Access Denied or Read-Only File System when i try to push the build.prop into it.
Click to expand...
Click to collapse
Did you use the 'adb remount' command? Sometimes, when attempting to push a file to the system, I get the 'read-only file system' and I have to issue adb reboot followed by adb remount and then push the file again. It seems after a time the mount system as read write automatically goes back to read-only.
Sent from my ADR6400L using xda premium

Have you got TWRP or ClockworkMod?
Because you could flash a new rom then.

abd - root mode
Perhaps, running adb in root mode will
allow you to push the original build.prop
back. Then execute "adb remount / rw" to mount the
root directory as read/write. Hopefully you will be able to push
it then follow daggy1985's instructions.
* In Win 7, type "cmd " at the 'SEARCH/RUN' and hold
shift + ctrl while hitting 'Enter' to put yourself
in Admin mode which apparently makes adb work in root mode when you launch it.
* Xda-dev is the coolest site for Android that I have seen. Kudo's to everyone participating.

sum1nil said:
Perhaps, running adb in root mode will
allow you to push the original build.prop
back. Then execute "adb remount / rw" to mount the
root directory as read/write. Hopefully you will be able to push
it then follow daggy1985's instructions.
* In Win 7, type "cmd " at the 'SEARCH/RUN' and hold
shift + ctrl while hitting 'Enter' to put yourself
in Admin mode which apparently makes adb work in root mode when you launch it.
* Xda-dev is the coolest site for Android that I have seen. Kudo's to everyone participating.
Click to expand...
Click to collapse
Thanks but I have actually been running it from Administrator from the very beginning. I've used Kindle Fire Utility KFU and it says that ADB Server is Online and my Bootmode is 4000 but it says ADB root: No. And whenever I choose any bootmode whether it be Normal, Fastboot, or Recovery, it always shows this:
***********************************************
* Activating Normal (4000) *
***********************************************
Installing BurritoRoot, Courtesy of Jcase of TeamAndIRC!
1393 KB/s (1164225 bytes in 0.816s)
Error: Could not access the Package Manager. Is the system running?
Activating BurritoRoot...
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system
running?
Elevating the Shell...
* daemon not running. starting it now *
* daemon started successfully *
/data/local/tmp/BurritoRoot3.bin: permission denied
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: No such file or directory
Unable to chmod /system/rbfb: No such file or directory
mount: Operation not permitted
mount: Operation not permitted
***********************************************
* Root Activated *
***********************************************
The kindle is successfully running in root mode.
<idme> Invalid permission
reboot: Operation not permitted
Same goes for the Temp Burrito Root and installing FFF and TWRP. It always shows something about cannot access Package manager. I have no clue what the Package Manager even does but apparently I cannot find a solution to that.

I think you need to get a factory programming cable like we talked about on gtalk. I'm confident that will fix this.
Sent from my DROIDX using Tapatalk

I used android commander for windows, mounted system in TWRP and used android commander to copy a new working build.prop to the right place.
With a cable from my htc desire.

would make a little test:
issue "adb shell"
if you get a error message your up to a factory cable because the system shell is messed up and you have no possibility to get to fastboot mode to install fff & twrp
if you get a $ or # prompt you can resume and try "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" to mount system in read/write mode

daggy1985 said:
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
hey, I've tried to remount my rooted galaxy y, fall in for same problem.but there show this message; "remount failed: Operation not permitted"
my device's usb debugging mode was off in last entire.
what I have to do now?

how did u edit build.prop in the first place if u don't have root and this might help
http://yaseminavcular.blogspot.com/2012/01/how-to-get-bricked-kindle-fire-back-to.html?m=1
Sent from my R800i using Tapatalk

[HOW-TO] Root / Install a ROM / Unroot / Revert to Stock (A KFFB Supplement)

This how-to originally started out as a part of the Kindle Fire For Beginners (KFFB) guide, but evolved into this supplemental guide. Because of its origin, this guide assumes the reader is already familiar with KFFB, so reading it is a mandatory prerequisite. Users who post questions in this thread already covered in KFFB will be directed to go back and read it again.
My motives for writing this guide are very much in line with the reasons why I wrote KFFB. I'm hoping users will take the time to learn what they are doing and why they are doing it instead of crossing their fingers and hitting a button on an automated program. While I understand this is the more tedious route to their destination, the knowledge gained here can be used to get back on track when things go wrong or methods inevitably change over time.
The first post in this series details the process of rooting and installing a ROM on a stock device. The two share many of the same preliminary steps, so it makes sense to go over both at the same time.
Preparations
Again, please read Kindle Fire For Beginners before continuing. The conventions introduced in KFFB (e.g. having KFU installed in "C:\kfu") will continue to be used here. Make sure the battery is fully charged. A drained battery is not something you'll ever want to encounter and especially not while in the middle of this process. Create a new folder "C:\kfu\software" on your hard drive. Downloaded software to be installed on the Kindle Fire will be moved there.
Download and install WinMD5Free to some place on your Computer. The developers for most of the software you'll download for the Kindle Fire will provide an MD5 checksum. The checksum is used to verify the integrity of downloaded file, so you can be sure that you haven't gotten a bad download or a corrupted file. Tell WinMD5Free what file you want to check and compare the calculated checksum with the one provided by the developer. If the two match, you can be confident about installing it on your Kindle Fire.
For all required software listed in this document...
Extract (unzip) the files from the compressed archive (unless otherwise noted)
Verify the MD5 checksums if they have been provided
Move them to the C:\kfu\software folder
As with any other how-to guide, it's always a good idea to just read through the document first to get a basic idea of the process involved. Once you are comfortable with the concepts, then go back through and actually perform the steps required.
Getting to fastboot mode
The first step to modifying the Kindle Fire is to get the device into fastboot mode. The easiest and safest way to do this on a stock device is to use a factory cable. The factory cable is safe because it does not require the bootmode to be changed on the device. If something unexpected happens, you'll be able to disconnect the factory cable and reboot straight back into the stock software.
If you choose not to use a factory cable and change the bootmode to get into fastboot mode, you'll be taking a small gamble that you'll be able to issue fastboot commands to the device and change the bootmode back to normal. If you cannot change the bootmode back for some reason (e.g. your device drivers for fastboot mode fail to recognize the device), the device will be stuck in fastboot mode until you find a way to do so. In nearly every case, if you are able to issue the adb commands to get into fastboot mode, you should be able to send the fastboot commands necessary to get out of it. This is just a fair warning out of an abundance of caution... make sure you've done everything to ensure the ADB device drivers have been installed properly.
If you have a factory cable, you can turn the Kindle Fire off and connect the cable to the device, then the computer. The Kindle Fire will power up and put you directly into fastboot mode. You can then skip the rest of this section and go directly to flashing a recovery and bootloader. Otherwise...
Required software:
pokey9000's fbmode​
1) Boot up the Kindle Fire normally and connect a USB cable to the device and computer.
2) Copy pokey9000's fbmode program into a user writeable location on the Kindle Fire...
Code:
adb push C:\kfu\software\fbmode /data/local/tmp/
3) Change the permissions on the fbmode program so it can be executed (run) on the device...
Code:
adb shell chmod 755 /data/local/tmp/fbmode
4) Execute (run) the fbmode program to change the bootmode to fastboot...
Code:
adb shell /data/local/tmp/fbmode
5) Reboot the device...
Code:
adb reboot
Note: In case you are wondering why the "adb shell idme bootmode 4002" command previously discussed in KFFB was not used here, that command requires root privileges not available in the stock configuration. Without root privileges, the above workaround is required.
Installing a recovery and custom bootloader
Required software:
FIREFIREFIRE bootloader
TeamWin Recovery Project (TWRP) recovery
Note: Do not extract the contents of the FIREFIREFIRE bootloader zip file. It will be flashed as-is with TWRP recovery.​
1) Install the TWRP recovery...
Code:
fastboot -i 0x1949 flash recovery C:\kfu\software\openrecovery-twrp-2.2.2.1-blaze.img
2) Set the bootmode to recovery (5001)...
Code:
fastboot -i 0x1949 oem idme bootmode 5001
3) Reboot the device into TWRP recovery. If you used a factory cable to get into fastboot mode, turn off the device by holding down the power button for about 20 seconds. Replace the factory cable with a generic USB cable and the device will start up again automatically. Otherwise...
Code:
fastboot -i 0x1949 reboot
4) Copy the FIREFIREFIRE bootloader zip file to the /sdcard directory on the Kindle Fire...
Code:
adb push C:\kfu\software\fff-u-boot_v1.4a.zip /sdcard/
5) From the main menu of TWRP, press the "Install" button to flash the FFF bootloader onto the bootloader partition. Navigate to the /sdcard directory on the left (should be the default the first time you use TWRP) and select the file from the list on the right. Then simply "Swipe to Confirm Flash" to install.
6) Optional: Make a nandroid backup of the stock software. From the main menu of TWRP, press the "Backup" button and then "Swipe to Back Up" to create a snapshot of the stock system. If you change your mind later about rooting or have second thoughts about the ROM, just "Restore" the backup and return to the stock configuration.
Rooting the stock software
Users interested in flashing a custom ROM may elect to skip this section. Rooting the stock software is not a requirement to flash a custom ROM because the custom ROM will completely overwrite the stock software. However, if you are undecided on the question of rooted stock vs. custom ROM, root the stock software first and try that out for a while. The option to flash a custom ROM will still be available at a later time.
The following method of rooting the Kindle Fire stock software has been tested on 6.3.x and 6.2.x systems. Skip step #5 when rooting 6.2.x systems because the root checker does not exist in those versions.
Required software:
Superuser by ChainsDD
Note: Two separate files will be needed from the contents of this zip file: the su binary from the system\bin folder and the Superuser.apk file from system\app folder.​
This section assumes the device is already booted into TWRP recovery.
1) Remount the /system partition in read/write mode...
Code:
adb shell mount system
2) Copy the su binary onto the device...
Code:
adb push C:\kfu\software\su /system/xbin/
3) Change the owner of the su binary to root...
Code:
adb shell chown root:root /system/xbin/su
4) Set permissions for the su binary to run as root...
Code:
adb shell chmod 6755 /system/xbin/su
5) Disable the root checker by renaming the check_rooted executable...
Code:
adb shell mv /system/bin/check_rooted /system/bin/check_rooted.bak
6) Change the bootmode back to normal...
Code:
adb shell idme bootmode 4000
7) Reboot the system...
Code:
adb reboot
8) Once the Kindle Fire has rebooted into the system, install the Superuser app...
Code:
adb install C:\kfu\software\Superuser.apk
Congratulations! You have gained root privileges on the stock Kindle Fire software!
Installing a custom ROM
It should go without saying, but users who intend on staying with a rooted stock device need to skip this section. Flashing a custom ROM will overwrite the stock software and leave no trace of the original Kindle Fire interface.
Required software:
Any ROM you choose to install. Check the KF Development List as a starting point.
Note: Do not extract the contents of the ROM archive. The recovery program will need the actual zip file to install.​
This section assumes the device is already booted into TWRP recovery.
1) Carefully read the ROM thread for specific directions and warnings provided by the developer when flashing any new ROM.
2) Copy the custom ROM zip file to the /sdcard directory on the Kindle Fire...
Code:
adb push C:\kfu\software\ROM.zip /sdcard/
You must replace the "ROM.zip" part of the above command to the actual name ROM's zip file you've downloaded.
3) From the main menu of TWRP, "Wipe -> Factory Reset" to remove the existing files in the data and cache partitions that could interfere with the operation of the new system software. A "Factory Reset" will delete any installed apps, software/network settings, etc. It will not touch the /sdcard directory that contains music, eBooks, and files of that nature.
4) From the main menu of TWRP, "Install" to flash the ROM onto your device. Navigate to the /sdcard directory on the left (should be the default the first time you use TWRP) and select the file from the list on the right. Then simply "Swipe to Confirm Flash" to install.
5) From the main menu of TWRP, "Reboot -> System" to boot into the newly flash ROM.
Congratulations! You have completely replaced the stock Kindle Fire software with a custom ROM!
Cleaning up
The zip files pushed onto the /sdcard during installation are only necessary during the installation process and do not need to take up space on the device after completing the install. Use a file manager or mount the storage device on the host computer to delete the files and reclaim the used space.
Coming soon...?
I've got some other topics in mind, but like I did with the KFFB, I'll see how users respond to this post before I continue. Please feel free to comment and make suggestions. I may not respond to everything, but I will keep the helpful comments in mind if/when I decide to expand this how-to guide. Thanks for reading.
Credits
jcase - For providing the basis for this guide and lending his expertise in rooting devices
pokey9000 - For his work on FFF and providing the fbmode exploit
TeamWin and Dees_Troy - For providing the TWRP recovery and continuing its development
ChainsDD - For the Superuser package​

Unroot or Revert to Stock Software
This second post in the series details the procedures required to undo the steps taken in the first. Use it to unroot or revert back to the stock software like it just came from the factory. If you tried out the rooted stock software or a custom ROM for a while, but just prefer the no-frills stock software, you've come to the right place.
Unrooting the stock software
Required software:
None​
This section assumes the device is already booted into the system software.
1) Uninstall the Superuser app
Code:
adb uninstall com.noshufou.android.su
2) Optional: Set the bootmode to recovery. Alternatively, use the recovery selection feature in FFF to boot into recovery during startup without manipulating the bootmode setting here. If you are more comfortable setting the bootmode directly...
Code:
adb shell su -c 'idme bootmode 5001'
3) Reboot the device into recovery...
Code:
adb reboot
4) Mount the data partition...
Code:
adb shell mount data
5) Optional: Delete the files that the Superuser app left behind...
Code:
adb shell rm -rf /data/data/com.noshufou.android.su
6) Mount the system partition...
Code:
adb shell mount system
7) Re-enable the root checker by renaming the check_rooted executable...
Code:
adb shell mv /system/bin/check_rooted.bak /system/bin/check_rooted
8) Delete the su binary from the device...
Code:
adb shell rm /system/xbin/su
9) From the main menu of TWRP, "Reboot -> System" to restart the device into the system software.
Congratulations! You have unrooted the stock Kindle Fire software!
Reverting to stock software
Required software:
Amazon Kindle Fire Software Update​
Warning: Installing the Amazon Kindle Fire Software Update will not only replace the system software, but also overwrite the bootloader and recovery with the stock versions. Any custom bootloader and recovery like FFF and TWRP will be overwritten in the process.
This section assumes the device is already booted into TWRP recovery.
1) Copy the update bin file to the /sdcard as update.zip
Code:
adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip
2) From the main menu of TWRP, "Wipe -> Factory Reset" to remove the existing files in the data and cache partitions that could interfere with the operation of the new system software. A "Factory Reset" will delete any installed apps, software/network settings, etc. It will not touch the /sdcard directory that contains music, eBooks, and files of that nature.
3) From the main menu of TWRP, press the "Install" button to flash the stock software onto your device. Navigate to the /sdcard directory on the left and select the "update.zip" file from the list on the right. Then simply "Swipe to Confirm Flash" to install.
4) Optional: From the main menu of TWRP, "Wipe -> SD Card" to remove all files on the USB mountable storage space. This step will permanently delete all of the files that appear on a computer when the device is connected as a USB storage device.
5) From the main menu of TWRP, "Reboot -> System" to restart the device into the system software.
Congratulations! You have reverted the device to a completely stock Kindle Fire!

KFFB Supplement Post #3
Reserved...

Great explanations!
I wanted to thank you for explaining everything clearly so that people can understand what they are doing when installing their bootloader, recovery and new ROMs.
Thanks again... plee3

Thanks so much!
This worked flawlessly. I had gotten stuck trying to root with KFU (I think the driver is slightly funky in fastboot - so KFU failed to flash either recovery or bootloader and left me in fastboot mode) but using the '-i 0x1949' option with fastboot made everything work perfectly.

Once again you have done a beautiful guide. You are very good at this, and always look forward to more guides from you.
Keep um coming !!
Cheers

Thibor69 said:
Once again you have done a beautiful guide. You are very good at this, and always look forward to more guides from you.
Keep um coming !!
Cheers
Click to expand...
Click to collapse
I know, right?

can i follow this to root 6.3.1?

xXezmacXx said:
can i follow this to root 6.3.1?
Click to expand...
Click to collapse
Yes, it's been tested to work from 6.2.0 and up.

Needs Sticky
Great Work. Gets my vote (and really needs) to be sticky'd.
Thanks for listening
Sincerely,
William
[Kindle Fire: gedeROM v1.25 [KeyClicks Added] {3.0 Kernel, CM9, Android 4.0.4} - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.

Thanks to all. I'm glad some of the readers got some use out of it.
Docs009 said:
Great Work. Gets my vote (and really needs) to be sticky'd.
Thanks for listening
Sincerely,
William
[Kindle Fire: gedeROM v1.25 [KeyClicks Added] {3.0 Kernel, CM9, Android 4.0.4} - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
Click to expand...
Click to collapse
If you think this guide will be useful to other users here, you can ask the moderators to review the thread and possibly make it a sticky. I would ask, but it seems a bit... uncouth to nominate my own post for sticky status.
Thanks for reading!

Gotta tell you, there should be some warnings/things to look out for in this guide. If you install all the latest Android SDKs (I pretend to develop in my spare time) it loads the wrong drivers. It will show up as "Android Device" or something like that. The correct drivers have it show up as "Android Composite Device". If you have the SDK in your path (which you need for Eclipse) after the first reboot it might load the wrong drivers again as it did with me which are the wrong ones and basically you won't be able to communicate with the Kindle again.
Took me almost an hour to get this thing off the "Kindle Fire" loading screen because of this problem/unawareness.

ExploreMN said:
Well, I followed the instructions. Got as far as "adb shell reboot" after the fbmode command. Now it just sits at "kindle fire" and shows up as an unknown device in device manager.
Is there anyway to recover from this or did I just junk my fire?
Click to expand...
Click to collapse
Your Kindle Fire is fine... it's in fastboot mode. The computer is most likely the problem. You'll have to make sure your device drivers are working properly, so the computer can send fastboot commands to the device.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2

kinfauns said:
Your Kindle Fire is fine... it's in fastboot mode. The computer is most likely the problem. You'll have to make sure your device drivers are working properly, so the computer can send fastboot commands to the device.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
Thanks Kinfauns. I actually got it fixed without even reading about it...I get a little medieval on things that frustrate me and eventually got it figured out...I edited my post to warn people about what tripped me up!

ExploreMN said:
Gotta tell you, there should be some warnings/things to look out for in this guide. If you install all the latest Android SDKs (I pretend to develop in my spare time) it loads the wrong drivers. It will show up as "Android Device" or something like that. The correct drivers have it show up as "Android Composite Device". If you have the SDK in your path (which you need for Eclipse) after the first reboot it might load the wrong drivers again as it did with me which are the wrong ones and basically you won't be able to communicate with the Kindle again.
Took me almost an hour to get this thing off the "Kindle Fire" loading screen because of this problem/unawareness.
Click to expand...
Click to collapse
Well, I actually tell you at the beginning of this guide to read my guide for beginners. In that guide, I tell you to use the driver installer included in KFU. Any how-to guide has to make some set of assumptions and I made the assumption that you'd actually follow the previous set of instructions before proceeding onto the next. I think you'd agree that I cannot possibly account for every possible deviation a user might take away from my actual directions. If I even attempted such a thing, this guide would turn into Encyclopedia Britannica.
In addition, I also gave you ample warning about putting your device into fastboot mode by manipulating the bootmode. I made a clear suggestion for you to get a factory cable and use it to get into fastboot mode the "safe" way. I've never seen any other rooting guide/utility even make mention of this possibility, so I've gone above and beyond what you'd get anywhere else.
With those things together, I believe I've done the very best I can to minimize the possibility that you might get stuck and have to "get a little medieval" on your device. Regardless, I'm glad you got it figured out. Good luck with the rest of it.

kinfauns said:
Well, I actually tell you at the beginning of this guide to read my guide for beginners. In that guide, I tell you to use the driver installer included in KFU.
Click to expand...
Click to collapse
True enough. Just didn't think it would keep reloading the drivers from the SDK if the SDK was in the path for Eclipse. I'm guessing anyone who set up Eclipse would not think this is an issue and might get stuck like I did...so it's still worth mentioning. (to me at least)

The second installment of this how-to guide has been posted. Included are instructions on unrooting and reverting back to the stock software. Suggestions and comments are always appreciated. Thanks!

Thank you for the excellent guide.
For what it's worth, this guide is very helpful for the admitted "noob" who has somehow failed with a utility like KFU and needs to go back and work through the pieces step by step. Thank you for laying out an instruction manual with enough detail to not only do the steps needed - but also to begin to understand what I'm doing.
I've rooted my KF (thanks to your assistance) so that I could install Swype. I then was able to use OTA-Rootkeeper to "hide" my SU file so that I can use Amazon media on my Fire as I want to, but still get the benefits I wanted from a rooted device (primarily the use of the Android Market, "Google Play", and the use of Swype).
For those that don't *really* want to unroot but do want to still use the Amazon content tools, I HIGHLY recommend the OTA-Rootkeeper utility.
Thanks again!

Kinfauns,
My Kinde Fire was bricked, with power problems. So I did the short trick to repair the bootloaders, using the linux stick and this script here, provided by firekit: usb_fix_parts_and_install_fff_twrp
When I look into device manager i have "Android Phone - Android Composite ADB Interface", at printers and devices the name shows as Kindle.
Can I go direct to these instructions here?
Rooting the stock software
Users interested in flashing a custom ROM may elect to skip this section. Rooting the stock software is not a requirement to flash a custom ROM because the custom ROM will completely overwrite the stock software. However, if you are undecided on the question of rooted stock vs. custom ROM, root the stock software first and try that out for a while. The option to flash a custom ROM will still be available at a later time.
The following method of rooting the Kindle Fire stock software has been tested on 6.3.x and 6.2.x systems. Skip step #5 when rooting 6.2.x systems because the root checker does not exist in those versions.
Required software:
Superuser by ChainsDD
Note: Download the latest zip for Gingerbread/ICS (the filename should end in "efghi-signed.zip"). Two separate files will be needed from the contents of this zip file: the su binary from the system\bin folder and the Superuser.apk file from system\app folder.
This section assumes the device is already booted into TWRP recovery.
1) Remount the /system partition in read/write mode...
Code:
adb shell mount system
2) Copy the su binary onto the device...
Code:
adb push C:\kfu\software\su /system/xbin/
3) Change the owner of the su binary to root...
Code:
adb shell chown root:root /system/xbin/su
4) Set permissions for the su binary to run as root...
Code:
adb shell chmod 6755 /system/xbin/su
5) Disable the root checker by renaming the check_rooted executable...
Code:
adb shell mv /system/bin/check_rooted /system/bin/check_rooted.bak
6) Change the bootmode back to normal...
Code:
adb shell idme bootmode 4000
7) Reboot the system...
Code:
adb reboot
8) Once the Kindle Fire has rebooted into the system, install the Superuser app...
Code:
adb install C:\kfu\software\Superuser.apk
Congratulations! You have gained root privileges on the stock Kindle Fire software!
Click to expand...
Click to collapse

DuendePaladino said:
Kinfauns,
My Kinde Fire was bricked, with power problems. So I did the short trick to repair the bootloaders, using the linux stick and this script here, provided by firekit: usb_fix_parts_and_install_fff_twrp
When I look into device manager i have "Android Phone - Android Composite ADB Interface", at printers and devices the name shows as Kindle.
Can I go direct to these instructions here?
Click to expand...
Click to collapse
If you used that script in Firekit, you should have FFF 1.2 and TWRP 2.0.0 installed, so technically, yes.... you can boot into TWRP and start following those directions. However, I would recommend that you upgrade your bootloader and recovery to the versions I have in the previous section... FFF 1.4a and TWRP 2.1.1. I won't go into all the reasons why, but they are "better" and likely to keep you out of trouble in the future. Since you already have FFF installed, it will be easy for you to get into fastboot mode. Once you are in fastboot mode, start with flashing TWRP and continue on from there.