Database Users

[Solved] Kindle fire stuck at "kindle fire title" (No animation)

First of all, i would like to thank alot Mr. "b63" without him my kf stuck and bricked forever.
I Initially putted the following question/problem:
.I have a problem with kindle fire, as i installed TWRIP program to try to install android 4.0 ice cream sandwich, but i failed, and screen remain to TWRIP software every time i try to boot the fire, at this step i am able to mount kindle fire, and what i did also is flashing KF (i made every kind of flash), i noticed that when i mounted KF all system files are deleted!, i tried to return back to my old software by downloading KF firmware update 6.2.1 and transfer it to kf, then install it, after that, and from this time the KF stuck at KF logo every time i start it, also it can't be mounted anymore, when i plug KF into the pc, it show me removable device but not accessible, i tried kindle fire utility and KindleUnbrickUtilityV1.0.zip but every order the software is waiting for the device and remain as it is, it seems that my KF bricked forever because i tried everything and it is now a challenge to return KF to it's original state or install android and make it workable again, can any one help me please?
i tried to make the following:
1. download the kindle fire utility
2. I used fastboot without rooting rooting (thanks to pokey9000 )
3. I used
Code:
fastboot -i 0x1949 getvar product
to search my kindle fire
4. I downloaded the fastboot file HERE then extract the files into the kindle fire utility folder
5. then we use this code
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
to install fastboot mode
6. then the screen will display the "install complete" word and button called reboot now click it after rebooting you should find the yellow triangle
7. Now use thee commands
Code:
fastboot -i 0x1949 oem idme bootmode 5001
fastboot -i 0x1949 reboot
if it cannot find a device and the locate driver window opens define the kf again
8. Now you can download the rom hat ever you want
9. click the mount button from the recovery mode
10. copy the rom into it
11. install the rom and i the install screen click the mall button have "X md5" or something like that(if you don't do this the kf will not install the rom)
12. clear the dalvik/cache
13. run thee commands
Code:
adb shell idme bootmode 4000
adb reboot
but unfortunately can't be done because there was some system shell files deleted, so i made factory cable and repeated the previous steps, it worked and i successed to install twrp s/w.
Also i downloaded modaco custom rom and installed it but it did not work for me.
Then i installed preroted unsecure rom from the following link:
http://www.multiupload.com/ZQ065JFSMR
Transferred it to kf, installed it and it works fine except the Android market icon
Also i made the following command before turning on the wifi:
adb shell rm /system/etc/security/otacerts.zip
to delete ocacerts.zip file to overcome amazone delete for the fff and twrp software.
to solve the problem of android market i did the following:
download from this post:
http://forum.xda-developers.com/show...42&postcount=8
and
http://www.xageek.com/software/FileE...9_GKWeb_EN.apk
and
http://61.145.124.93/soft/3GHeart/go...r_EX_V2.77.apk
and place all files in the tools directory of kfu
then some commands:
adb install GO_Launcher_EX_V2.77.apk
adb install FileExpertSigned_4.0.9_GKWeb_EN.apk
On My device (either click disconnect or unplug it temporarily) go to Apps and run the File Expert application we installed earlier. Click the Menu button at the bottom of the screen → More → Settings → File Explorer Settings and check “Root Explorer”, clicking “Allow” to the access dialogue. After this, back out to the Home screen of File Expert. From here click My Files → Phone Internal Storage → sdcard, then tap Menu → More → Mount → Mount as Read Write. Now do this for one more location, so tap the back arrow, then go to system → app and tap menu → More → Mount → Mount as Read Write.
adb push GoogleServicesFramework.apk /sdcard/
adb push Vending.apk /system/app
adb shell chmod 644 /system/app/Vending.apk
On My device, open File Expert (if you closed it) and go to My Files → Phone Internal Storage → sdcard and tap GoogleServicesFramework.apk (if you don't see it, back up a directory and come back). Tap Install. Once it finishes, click “Done”. Now tap back, then system → app. From here tap Vending.apk and Install it. Choose OK to Replace Application. Once finished click “Done”.
Reboot My Kindle Fire.
Go to Apps and launch Go Launcher. From inside of Go Launcher I should be able to visit and use the Android Market. Now when you press the Home Key you'll be prompted to choose either the Amazon launcher or the Go Launcher. They both have their uses.
but mounting for read & write failed for unknown reason.
I overcome this by doing the following:
issued "adb remount" and resume with the next 3 adb commands above
it works very nice for me, i tried to install from android market and it worked very nice, i enjoy my kf, thanks again to b63 and XDA-developer forum.

Kindle HD 7 Rooted? Directions

Looks like Root has been achieved as there is the following guide on AndroidGeeks.
I am not responsible if you try this, I am just passing along information.
How to root the Kindle Fire HD 7 by pushing SuperUser via ADB commands
1. Download the SU zip file from HERE.
2. Extract the contents from the SuperUser zip in a single folder on your desktop.
3. Go to the newly created folder and open the ‘system’ directory, then open ‘bin’ and copy the ‘SU’ file and paste it in the folder you’ll be working from. Then, open ‘system’ directory and then ‘app’ folder and copy the ‘SuperUser.apk’ file and paste it in the same folder as the ‘SU’ file.
4. Connect your Kindle Fire HD 7 tablet to your PC via the original USB cable. Open Settings app on your Kindle Fire HD 7 and then select ‘Security’ and now you need to enable the ‘adb’.
5. Go to the folder that contains the SU and the SuperUser apk files. Press and hold ‘shift’ key and at the same time right-click in the folder’s white space. Select ‘Open command window here’.
6. Now you will need to push the files by using the command lines below:
adb shell
rmdir /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
7. Your device will restart and the local temp file was removed and now you will have a false link to the whole data directory. After the device reboots you have to enter the following commands:
adb shell
echo ‘ro.kernel.quemu=1′ > /data/local.prop
exit
adb reboot
8. The Kindle Fire HD 7 will now reboot and you need to push the SU binary files. Enter the following commands:
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
9. A new restart will be applied and now you can push the SuperUser apk file. Enter this final command line:
adb install Superuser.apk
10. That is it. You’ve finally flashed the root on your Amazon Kindle Fire HD 7 tablet.
If you didn’t manage to flash this tutorial, then you should ask for more help in comments.
Have a question or issue ? Ask it here !

JaxDomino said:
Looks like Root has been achieved as there is the following guide on AndroidGeeks.
I am not responsible if you try this, I am just passing along information.
How to root the Kindle Fire HD 7 by pushing SuperUser via ADB commands
1. Download the SU zip file from HERE.
2. Extract the contents from the SuperUser zip in a single folder on your desktop.
3. Go to the newly created folder and open the ‘system’ directory, then open ‘bin’ and copy the ‘SU’ file and paste it in the folder you’ll be working from. Then, open ‘system’ directory and then ‘app’ folder and copy the ‘SuperUser.apk’ file and paste it in the same folder as the ‘SU’ file.
4. Connect your Kindle Fire HD 7 tablet to your PC via the original USB cable. Open Settings app on your Kindle Fire HD 7 and then select ‘Security’ and now you need to enable the ‘adb’.
5. Go to the folder that contains the SU and the SuperUser apk files. Press and hold ‘shift’ key and at the same time right-click in the folder’s white space. Select ‘Open command window here’.
6. Now you will need to push the files by using the command lines below:
adb shell
rmdir /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
7. Your device will restart and the local temp file was removed and now you will have a false link to the whole data directory. After the device reboots you have to enter the following commands:
adb shell
echo ‘ro.kernel.quemu=1′ > /data/local.prop
exit
adb reboot
8. The Kindle Fire HD 7 will now reboot and you need to push the SU binary files. Enter the following commands:
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
9. A new restart will be applied and now you can push the SuperUser apk file. Enter this final command line:
adb install Superuser.apk
10. That is it. You’ve finally flashed the root on your Amazon Kindle Fire HD 7 tablet.
If you didn’t manage to flash this tutorial, then you should ask for more help in comments.
Have a question or issue ? Ask it here !
Click to expand...
Click to collapse
thanks, but you realize this has been posted here twice with two different methods (manual and automated) right?

May as well add the link. This autmated way ensures that you won't mistype some lnyx command. (as they are so logical, and English-y) :silly:
http://forum.xda-developers.com/showthread.php?t=1893838
I used this method, and it worked for me.

ffs something always goes wrong
would appreciate help on the command prompt part

How to unbrick soft-bricked device

Today I tried to do some modification on my rooted Kindle 7 HD and in the end it was stuck in a bootloop. I tried a few "tricks" and searched in the board about solutions but nothing worked out.
This is the scenario:
Code:
your device is rooted
you know which file caused the bootloop (in my case it was services.odex)
your device gets recognized in adb (it may take some time, just wait)
What will not work:
Code:
abd shell -> su will freeze (because of superuser)
adb uninstall com.noshufou.android.su will give an error
--> NO way to get root
Now what you have to do:
Code:
adb reboot recovery
Restore the Kindle -> device will reboot
device is still bricked
but superuser is away (root too)
now re-root device
reboot device
start adb shell
su
now mount system rw with "mount -o rw,remount /system"
now delete/edit the file causing the bootloop
adb reboot
-> Device unbricked

I have excatly the same problem. Bricked my KF HD 7 2013, while replacing the services.odex Do you find a solution?

Follow the steps I did.

Hey. I tested your steps and I will be able to fix that. But after reset the device, I lose my Backup of the working files on internal memory. Would be great, if you can provide me this files (if you also use the Kindle Fire HD 7 13'). See here: http://forum.xda-developers.com/showthread.php?t=2584494&highlight=services+odex

Thanks much for your instruction. My kindle is back
Here are my steps:
adb shell
su
mount -o rw,remount /system
chmod 777 /system/framework
exit
exit
adb push services.odex /system/framework
adb reboot

KFSOWI v11.3.1.0_user_310084920 bricked
KFSOWI v11.3.1.0_user_310084920 bricked while enabling mock location for bluetooth gps
My steps:
1. KFSOWI v11.3.1.0_user_310084920 succesfull rooted
2 . next steps like http://forum.xda-developers.com/showthread.php?t=2019571
but different:
3. renamed the original "settings.db" to "settings.db.org"
4. copyd the modified "settings.db" back in the original folder
After shutdown and restart the KFSOWI remains in a loop showing colored "KindleFire"
Was my mistake renaming "settings.db" instead of overwriting?
The command "adb devices" shows still the device id.
The command "adb reboot" reboots the KFSOWI - but without success.
Which commands are necessary for solving the problem?
Please write the steps very detailed - I´m an new linux user.
A lot of thanks to the community for answering

TWRP in 10 minutes or 30 minutes :

A bit of a brain dump, for reference.
I just rooted 3 newly arrived Fires each under 10 minutes (all were FireOS 4.1.1, but this will work all the way to FireOS 4.5.3).
If you have 4.5.4, 4.5.5, turn WiFi off, downgrade via the earliest dev preview update-kindle-devpreview_ariel-20.5.2.0_user_520033250.bin (just copy it to the device, into /sdcard ):
https://www.dropbox.com/s/38i2lqq5p...review_ariel-20.5.2.0_user_520033250.bin?dl=0
Then upgrade to 4.5.3 (again copy *.bin to /sdcard):
http://forum.xda-developers.com/fire-hd/general/fire-hd-rom-links-t3173102
(this is why 30 minutes !)
If you have 4.5.5.1, stay put.
Workflow (FireOS <= 4.5.3).
boot Fire, no Wireless yet (leave unconnected)
check OS, if <=4.5.3, proceed
Touch 7 times serial number, enable developers options
Enable ADB debug
Enable app from unknown sources
Attach to a computer, install ADB drivers (on PC side)
Authorize ADB access
In a DOS window with adb type:
Code:
adb devices
adb shell pm block com.amazon.dcp
adb shell pm block com.amazon.otaverifier
adb install NewKingrootV4.80_C135_B242_en_release_2016_01_20_105203.apk
adb install gscript-android.apk
adb install ES_File_Explorer_3.2.5.5.apk
adb shell
[email protected]:/ $ mkdir /sdcard/gscript
mkdir /sdcard/gscript
[email protected]:/ $ exit
exit
adb push flash453.zip /sdcard/gscript
adb push 453_key_images.zip /sdcard/gscript
Connect wireless.
Launch KingRoot, let it root, done.
If you already have 4.5.3, just use Flashify to flash TWRP ( Install Flashify like this : > adb install flashify.apk )
If not :
Launch ES explorer, head over to /sdcard/gscript, unpack the 2 zips (*.sh scripts and *.img files).
In Gscript, pick flash_453.sh , say yes to root, launch.
The fire reboots straight into TWRP. If needed, reboot to system, you will end up in whatever FireOS you had (4.1.1 in my case).
More detailed instructions on Gscript & TWRP flashing mechanics (after you get root), this saves a lot of time if the FireOS is not 4.5.3 when you start (path A) :
http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2

Remove Forever Lock Screen Ads [NO ROOT] FIRE OS 6.3.0.0 and up. 8th GEN.

I recently got a Kindle Fire HD 8, with special offers. And obviously I didn't want the adds. I tried several methods to remove the ads, but found the solution within the methods that that Rortiz2 had posted in his How - to.
I have an 8th gen kindle. And the method outlined by Rortiz2 for 8th gen didn't work. But mixing both methods, older gen and newer gen worked. I imagine this may work with newer gen's as well. But I have no way to test.
Before you begin make sure you have ADB drivers installed. I am using Linux. ADB drivers are there by default which is nice.
1. Download latest mtk-su
2.Unzip arm/mtk-su somewhere. On linux, the desktop is fine, or home folder. On windows, it's probably easier to put in the ADB Folder.
**** NOTE **** You must disable the kindle.kso app on each account on the Fire. As well disable the ads in settings for each account. If you don't, when you switch to that account, it will have kindle.kso active, and will turn on the show ads to 1. If you create a new account the same thing will happen. I am looking into killing this completely.
3. Enable USB Debugging. If when you run a command and get a no permission message, go on the Fire, go into connection settings and switch it to file transfer.
4. Open terminal, (Or CMD on win)
5. Push the mtk-su to the Fire.
Code:
adb push mtk-su /data/local/tmp/mtk-su
6. Make mtk-su executable.
Code:
adb shell chmod 755 /data/local/tmp/mtk-su
7. Open an ADB Shell.
Code:
adb shell
8. Navigate to tmp directory.
Code:
cd data/local/tmp
9. Run mtk-su to get a root shell.
Code:
./mtk-su
10. Disable kindle.kso
Code:
pm disable com.amazon.kindle.kso
11. Change settings to turn off the ads on the lock screen.
Code:
- adb shell settings put global LOCKSCREEN_AD_ENABLED 0
- adb shell settings put global ksoHash 0
You should now have no ads. And they should not come back.
I'd like to thank Rortiz2 for doing the work he did. I just figured out that I had to mix a little of both methods to get it to work on 6.3.0.0 or better.