Related
I have bricked Kindle fire while trying to install Android Market. To the point that shell doesn't work.
I made myself a factory cable. So I can easily go into fastboot mode. I tried various ways that people post in different threads. None seem to work as expected.
Is there a way to completely flash the original amazon ROM in fastboot?
Update: fastboot gives me < waiting for device > now. I'm still using the same factory cable that I made myself and KF looks like it is in fastboot state - the logo shows up on the screen.
I will recheck factory cable a little later. Maybe it broke or something. Though KF still recognizes it and goes into fastboot mode.
Any ideas?
There seems to be very little help on how to use a factory cable. I am in a similar boat as you. Shell works for me but adb commands do not. I can't push or pull or install. I can navigate, change file names, and move files to some directories. My problem is that I don't know how to put the stock rom on and flash it. I actually have 6.2 on the sdcard but don't know what to do with it.
As for your problem, I experienced the same thing. adb devices didn't list my KF but I could see it in lsusb. I typed the usb description at $ "1949:0006 Lab126" and it called me an idiot or something but then I typed ./adb shell and vioala. I'm sure that didn't do anything and won't ever work again but there you have it.
I have a couple of open questions out there to see if we can get help and if I learn anything I will make sure you hear it next.
ToonaKan
Dmitry_G said:
Update: fastboot gives me < waiting for device > now. I'm still using the same factory cable that I made myself and KF looks like it is in fastboot state - the logo shows up on the screen.
I will recheck factory cable a little later. Maybe it broke or something. Though KF still recognizes it and goes into fastboot mode.
Any ideas?
Click to expand...
Click to collapse
You must insert cable, when switch off kindle by pressing button about 20sec and press once again, kindle will be in fastboot.
After kindle will be in fastboot, with Kindle Fire Utility v.6 install TWRP recovery and with recovey install stock or CM7 firmaware.
Admittedly, I am a little green when it comes to this but I never got it to list in fastboot devices either with a cable (and I am not sure I am supposed to), you can check if its connected in fastboot mode by:
fastboot -i 0x1949 getvar product
it should return "kindle"
from there I did:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
fastboot oem idme bootmode 4000
fastboot reboot
To get twrp up and running then I flashed the prerooted 6.2.1. Going back to the orginal rom should be similar
Ok. Passing "-i 0x1949" to fastboot helped and now I can communicate with KF in fastboot.
But a new problem has surfaced. I'm trying to install TWRP:
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
It writes "downloading 'boot.img'" and gets stuck there. I waited for 15 minutes.
Ideas?
You need to now check to make sure your drivers are now up to date.
So it seems that I can't really do any operations with fastboot. Every command just freezes at the first thing it does. Weird.
I'm on a mac. I never installed any drivers for KF - it just worked. Do I even need a driver for KF on a mac?
There must have been something with the factory cable. I finally managed to load TWRP.
Now I'm trying to install stock ROM renamed to update.zip. I push it into /sdcard. Then in TWRP I tap on Install and select update.zip.
I get:
E:failed to mount /sdcard (Invalid argument)
E:Can't mount /sdcard/update.zip
What does that mean?
Ok guys. I found the solution. "E:failed to mount /sdcard (Invalid argument)" tells you that your sdcard is not formatted correctly. Here is the fix I did.
I already have TWRP installed and also have a factory cable. But I still have a few questions.
1. With a factory cable, is there any way to directly flash the stock firmware or do you always have to install and use TWRP?
2. From reading about TWRP, it seems that after installing it, you can then load the stock firmware onto the sdcard directory and then complete the restore operation. As a safeguard, and to make things easier, I have already put a copy of 'update.zip' on there just in case I need it. My question is - on an unrooted Fire, would it not be a good idea to stick 'update.zip' on the sdcard before rooting? That way if something goes wrong, all you need to do is get TWRP on there and the restore file is already in place. Or am I being overly cautious?
Hello all,
I've got a bricked droid, and haven't been able to find a fix that worked in other threads here.
I rooted my droid successfully, and installed GO Launcher EX, along with the android market, and a number of apps from there.
Among those, busybox, metamorph (which i then used to change the wallpaper), titanium backup, etc. I had successfully rebooted after all these installations and after changing the wallpaper.
I was getting on a plane the other day and turned off the KF, and havent been able to get it to boot since.
Originally it was in a boot loop, getting to the kindle fire icon and rebooting every 3 seconds.
I tried using the KFU, but it was unsuccessful at changing the boot mode (drivers were successfully installed).
Failing at that, i tried following the instructions in http://forum.xda-developers.com/showthread.php?t=1414832
After the reboot, it is now just stuck in the kindle fire screen, and i cant run any adb commands, device not found.
Am I straight up screwed now? or anything I might be able to do at this point.
Much appreciated, thanks for any advice.
Do you have fastboot access? Try running the following...
fastboot -i 0x1949 oem idme bootmode 4000
Try this: http://forum.xda-developers.com/showthread.php?t=1422832
Thanks guys, ill try those and post back w the results.
so i tried fastboot -i 0x1949 oem idme bootmode 4000
and it seems to have been successful, in that it is now back to its original boot loop state. however, it is still not booting fully.
it seems that adb commands are now working, i can do adb shell, and navigate root folders (system etc).
zombie, i havent had much luck with that route, i had tried that earlier.
I've seen people mentioning that the cause for their brick had something to do with permissions, so i did ls -l in the adb shell, here are the permissions for some of the relevant folders. if there are any others that might be helpful, let me know.
root -> drwx------
system -> drwxr-xr-x
sdcard -> lrwxrwxrwx
oh and framework-res.apk -> -rw-r--r-- (same as all other files in that directory)
i did modify the framework-res to change the background image. it successfully booted at least once after the modification - i used metamorph, i loaded the file, then rebooted for it to take effect. this was successful, but i believe it was the next reboot which did my kindle in, so possibly related.
i rambled a bit, but maybe if i replaced the current framework-res.apk with the stock framework-res.apk, that might be worth trying? are all stock framework-res.apk files the same at stock? because i don't have a copy of the original that came with my kindle.
i would go back into fastboot and then flash over TWRP... and then reinstall your os from scratch. it would probably be easier than trying to root around fixing it from the inside.
Thanks xrishox, I might do that. Is there a thread detailing how to do that?
When I tried doing fastboot I lost the ability to use adb commands so I'm not sure how to go about flashing twrp.
Download the fbmode binary and TWRP image. Then run the following.
Code:
adb push fbmode /data/local/temp
adb shell /data/local/tmp/fbmode
arbiter reboot
Your device should reboot and be stuck on the Kindle bootscreen. You are currently in fastboot mode. Now run the following...
Code:
fastboot -i 0x1949 poem idme bootmode 4000
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.image
Your device will reboot after that last command. It will boot into the TWRP installer. When it completes, tap "Reboot". Then boot into TWRP recovery and install the factory update, or a custom image that won't replace FireFireFire and TWRP.
jackofaiitrades said:
Hello all,
I've got a bricked droid, and haven't been able to find a fix that worked in other threads here.
I rooted my droid successfully, and installed GO Launcher EX, along with the android market, and a number of apps from there.
Among those, busybox, metamorph (which i then used to change the wallpaper), titanium backup, etc. I had successfully rebooted after all these installations and after changing the wallpaper.
I was getting on a plane the other day and turned off the KF, and havent been able to get it to boot since.
Originally it was in a boot loop, getting to the kindle fire icon and rebooting every 3 seconds.
I tried using the KFU, but it was unsuccessful at changing the boot mode (drivers were successfully installed).
Failing at that, i tried following the instructions in http://forum.xda-developers.com/showthread.php?t=1414832
After the reboot, it is now just stuck in the kindle fire screen, and i cant run any adb commands, device not found.
Am I straight up screwed now? or anything I might be able to do at this point.
Much appreciated, thanks for any advice.
Click to expand...
Click to collapse
Howdy!
I recently just dealt with this same issue. My KF was stuck in boot loop and wouldn't be recognized by my computer. I left it in bootloop until it ran out of battery. Once it was completely drained, I connected it to my computer and my computer recognized it, I then reinstalled the drivers. Right after that I used KFU to change bootmode to normal boot and let it fully charge! Good to go! Hope this helps someone.
from the op of kfu:
Known Tricks
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
•If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Click to expand...
Click to collapse
and here is a note from vashypooh - the op of kfu
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
maybe it helps someone ...
Thanks guys, I won't be near a computer until tonight but will try these out as soon as I get back
lmntone said:
Download the fbmode binary and TWRP image. Then run the following.
Code:
adb push fbmode /data/local/temp
adb shell /data/local/tmp/fbmode
arbiter reboot
Your device should reboot and be stuck on the Kindle bootscreen. You are currently in fastboot mode. Now run the following...
Code:
fastboot -i 0x1949 poem idme bootmode 4000
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.image
Your device will reboot after that last command. It will boot into the TWRP installer. When it completes, tap "Reboot". Then boot into TWRP recovery and install the factory update, or a custom image that won't replace FireFireFire and TWRP.
Click to expand...
Click to collapse
Tone you're a life saver, thanks. I'm up and good to go.
good that it's working again !
have you seen this one in the dev section - could save a lot of handwork:
http://forum.xda-developers.com/showthread.php?t=1428428
Also, when I get back to my computer again, ill update my OP to include the solution so that others might benefit. its like a 20 minute fix but took me days to resolve it (largely due to lack of comp access but that's beside the point).
UPDATE 3: I've got it back to as stock as I can get it. I think I'm going to just return it and get a new one. Thank you all for your help.
UPDATE 2: As of right now, I'd like to completely remove FFF from the device, but I can only use fastboot to do it. I have absolutely no adb access. Is there a way?
UPDATE: Here is a video showing what is happening to my KF: http://www.youtube.com/watch?v=MH6oUg1NmC0
I hate to start another thread about boot loops/bricking, but I'm not sure what's going on with my fire.
I had CM7 installed successfully since the day after Christmas. This morning I woke up and my Fire was being really sluggish, so I rebooted it (I did not select reboot into recovery).
After it powered on, I was stuck at the CM7 boot screen (with the skateboarding android). I let it sit, but no luck. I went into TWRP to try and restore the backup I made of the stock rom. It looked successful, but when I rebooted I was stuck at the Kindle Fire boot screen.
Next, I tried wiping the device and re-installing CM7, but I received an error (something along the lines of E:Error unable to find /tmp/sideload/blahblah).
So I again restored my backup of the stock rom. Now when I power on my Fire I see the yellow triangle, then the kindle fire logo, yellow triangle, kindle fire logo, and it just keeps repeating. The problem is I am unable to connect to adb because the PC only seems to recognize the adb device for a few seconds after the yellow triangle, which does not give me enough time to fix the problem.
Any ideas?
looks like you'r out of battery ! the kf is rebooting !
would take the wall charger and charge for an hour
it's not possible to charge with the computer - it lasts forever
then it should respond in a stable state
b63 said:
looks like you'r out of battery ! the kf is rebooting !
would take the wall charger and charge for an hour
it's not possible to charge with the computer - it lasts forever
then it should respond in a stable state
Click to expand...
Click to collapse
Recovery shows my battery level to be at 53%. I've got it on the charger now, but I have a feeling there is something else going on.
Also, I am unable to mount my Fire's SD to my computer in recovery. It looks like it is working, but my computer never acknowledges it.
maybe because your last installation failed
nevertheless i would try to charge and then go in twrp and retry the installation
if that's not sucessful i would try to switch the kf to fastboot and copy a new rom. stock or prerooted stock or cm7 - whatever you like
in twrp there is a point "mount" - sdcard - then you should get it from computer
b63 said:
maybe because your last installation failed
nevertheless i would try to charge and then go in twrp and retry the installation
if that's not sucessful i would try to switch the kf to fastboot and copy a new rom. stock or prerooted stock or cm7 - whatever you like
in twrp there is a point "mount" - sdcard - then you should get it from computer
Click to expand...
Click to collapse
Thanks for the reply. Is adb required to get into fastboot? The problem is that I am unable to get into adb because my computer only sees the Fire for about 1 second. When I go into device manager, I don't see it at all.
EDIT: Yeah, I see the mount in TWRP, but it does not do anything when I select it.
Hi Im a beginner but Id like to try to help :
In case you become desperate ignore twrp's battery display and try wall charger.
Anorher idea id have is to shut down throughr twrp and start up then instead of rebooting.
ADB is needed to get into fastboot, but it's quick. If you use KFU, you can probably hit the option during the couple seconds you have available. I would say your best bet, however, is booting into twrp, doing a full wipe of system, cache, davlik cache, and maybe data, and then trying the rom install again.
skourg3 said:
ADB is needed to get into fastboot, but it's quick. If you use KFU, you can probably hit the option during the couple seconds you have available. I would say your best bet, however, is booting into twrp, doing a full wipe of system, cache, davlik cache, and maybe data, and then trying the rom install again.
Click to expand...
Click to collapse
So this time it looks like the installation worked in TWRP, but after reboot now I'm stuck at the CM7 boot screen. This is at least some progress, so when I get home I'll see what I can do.
Sent via my internet connected mobile cellular telephone.
Well, the battery is definitely not the issue. I've been trying to get fastboot, but the problem is the fact that I can not get adb. Has anyone else had issues with getting adb? I've already tried to install the drivers, and that doesn't work.
EDIT: I've tried issuing "adb devices" from the command prompt repeatedly as soon as I hear the ding until it disconnects a second later, but still I have had no luck.
Also, I found this thread in which someone else appears to have had a similar issue to mine.
[Q] New kind of unfixable Super Brick?
at the moment adb is useless - you should try to get the device in fastboot mode - correctly recognised from your computer - then work with fastboot commands - if you don't get that then your next opinion is buying or making a factory cable - but we should try to avoid that ...
b63 said:
at the moment adb is useless - you should try to get the device in fastboot mode - correctly recognised from your computer - then work with fastboot commands - if you don't get that then your next opinion is buying or making a factory cable - but we should try to avoid that ...
Click to expand...
Click to collapse
I can not seem to get fastboot to work either. Does fastboot rely on adb? Or do you just run the .exe file? I tried to run it, and nothing happened.
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
b63 said:
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
Click to expand...
Click to collapse
Just wanted to let you know I updated the OP with a video showing what is happening to my KF.
Haven't tried that particular rom yet, but I have wiped data and cache and attempted to re-install CM7.
great idea with the video !!!
b63 said:
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
Click to expand...
Click to collapse
OK, so I restored my original rooted kindle rom, but I still can't get into fastboot because of the problem I showed in the video. It is doing exactly the same thing, just instead of the CM7 boot screen, it is the Kindle Fire boot screen.
Is is possible to get into fastboot without the computer? Can anyone think of a reason why I would not be able to mount my device in TWRP?
I just want to understand something about fastboot... can you upload and flash roms with it? Or can you only get TWRP / FFF with it? I ask because I already have them, and I still can't do anything (mount from inside TWRP doesn't work). Thanks!
Sent via my internet connected mobile cellular telephone.
with fastboot you can install the newest fff and if you need twrp
but with the newest fff you can issue ""fastboot oem format"
see here:
http://forum.xda-developers.com/showthread.php?t=1369405
that should solve every issue ...
b63 said:
with fastboot you can install the newest fff and if you need twrp
but with the newest fff you can issue ""fastboot oem format"
see here:
http://forum.xda-developers.com/showthread.php?t=1369405
that should solve every issue ...
Click to expand...
Click to collapse
Cool. I just ordered one of SkOrPn's cables, so once I get it I'll be sure to give an update. Thanks for all the help so far!
The cable isn't need when you have the FFF bootloader, in fact, when your computer does see the device for the short amount of time shown in the video, fastboot is active. It's a feature of FFF. Fastboot is a command line tool like adb but is used for different things. It comes in Android sdk which if you have that, you should update the tools packages in the Android manager and it will update adb and fastboot. It looks like something is not working correctly in twrp and the OS is failing to load. I'm not sure you need to oem format tho.....
At some point you had to have used fastboot to install twrp and/or FFF.... Unless you used adb dd? :what:
Anyway, I can help more but it's late where I am, need to sleep. Was going to write more but... Need sleep lol. I'll post some questions and check back tomorrow.
Have you used adb before? Do you know if platform-tools is in your environment variables PATH? In other words, can you open up cmd and type adb or do you need to "cd" to platform-tools then use adb? If you know where adb is located? If so, is a file called fastboot in there? (Maby called fastboot.exe)
foxdog66 said:
The cable isn't need when you have the FFF bootloader, in fact, when your computer does see the device for the short amount of time shown in the video, fastboot is active. It's a feature of FFF. Fastboot is a command line tool like adb but is used for different things. It comes in Android sdk which if you have that, you should update the tools packages in the Android manager and it will update adb and fastboot. It looks like something is not working correctly in twrp and the OS is failing to load. I'm not sure you need to oem format tho.....
At some point you had to have used fastboot to install twrp and/or FFF.... Unless you used adb dd? :what:
Anyway, I can help more but it's late where I am, need to sleep. Was going to write more but... Need sleep lol. I'll post some questions and check back tomorrow.
Have you used adb before? Do you know if platform-tools is in your environment variables PATH? In other words, can you open up cmd and type adb or do you need to "cd" to platform-tools then use adb? If you know where adb is located? If so, is a file called fastboot in there? (Maby called fastboot.exe)
Click to expand...
Click to collapse
Yep, I've used adb successfully, and it is set up as an environmental variable. I actually installed FFF and TWRP with the KFU. Problem is I think something else is botched; perhaps it is TWRP itself, since I am unable to mount from TWRP. I'll try again when I get home.
Sent via my internet connected mobile cellular telephone.
So I was messing around with my rooted Kindle Fire trying to apply a new theme to my Ice Cream Sandwich Launcher with metamorph and totally screwed everything up. I rebooted my Kindle Fire and it was stuck on the kindle fire logo screen. This morning I tried to unbrick it with the Kindle Fire Unbrick utility but it screwed up everything even more. Now i'm stuck on the yellow triangle screen (firefirefire), I realized that I totally screwed up the framework apk in the system folder. My computer will recognize the Kindle Fire but it comes up as "kindle" in the Other Devices in the "Device Manager". I tried to update the driver but the wizard will say that it cannot find any driver. What should I do? I already read many other posts but throughout the steps I get stuck on one and cannot continue.
I suggest try the following:
Adb kill-server
Adb start-server
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb shell reboot
Good luck
Sent from my Amazon Kindle Fire using Tapatalk
I know how to fix the yellow triangle, do this
1.Download kindle fire utility
2.Unzip kindle fire utility
3.To install the driver,its easy,just plug in your kindle, when it pops up with the install wizard say pick from the location of: KindleFireUtility>drivers>kindle 4.run kindle fire utility,select 1 then select 1 again
That's it, hope it helps
fedorp said:
So I was messing around with my rooted Kindle Fire trying to apply a new theme to my Ice Cream Sandwich Launcher with metamorph and totally screwed everything up. I rebooted my Kindle Fire and it was stuck on the kindle fire logo screen. This morning I tried to unbrick it with the Kindle Fire Unbrick utility but it screwed up everything even more. Now i'm stuck on the yellow triangle screen (firefirefire), I realized that I totally screwed up the framework apk in the system folder. My computer will recognize the Kindle Fire but it comes up as "kindle" in the Other Devices in the "Device Manager". I tried to update the driver but the wizard will say that it cannot find any driver. What should I do? I already read many other posts but throughout the steps I get stuck on one and cannot continue.
Click to expand...
Click to collapse
First off, what rom are you running on you Kindle stock 6.2.2, CM7, CM9? Did you make a backup of the original framework-res.apk? If so follow these instructions (assuming you have adb working):
if original framework-res.apk is stored on you computer:
from command prompt (start -> in search box type cmd then enter) cd to where you have backed up the original file if it's on your computer
then type the following commands
adb devices
adb remount
adb push framework-res.apk /system/framework
adb shell chmod 644 /system/framework/framework-res.apk
adb reboot
if the original file is stored on your kindle:
adb devices
adb remount
adb mv /path-to-original/framework-res.apk /system/framework/framework-res.apk (fill in actual path in "path-to-original")
adb shell chmod 644 /system/framework-res.apk
adb reboot
Hint: If you didn't make copy of original framework-res.apk, you can always download and open up the install zip for your rom and extract the original file. Good Luck!
Kindle Fire Bricked PLEASE HELP!!!
So like every other noob with a new kindle fire 6.2.2 i tried to root it, after nearly 3 days of trying different ways i was able to root it i then proceeded to install go launcher ex once i selected go launcher it froze and i have not been able to boot sense.i was stuck on kindle fire logo and it would not do anything i tried to run the unbrick utility 1.1 and 1.0 i get device not found but it does say it was unbricked but it is not, now let me say how stupid i was to not create a backup i know i know ugh im kicking myself now... my computer sees it under device manager as android adb interface when pluged in and i see the usb connection in the task bar on WIN 7, but i cannot access it as a protable drive. when i turn it on it will only load twrp.im guessing im screwed and everything is gone... any help will be much much appreciated, im not sure what other info you may need at this point and i am sorry for my ignorance in advance. thank you for any help!
and yes i have tried several things to get it working again which has gotten me to this worse point...i was able to see it normaly as protable device but i dont know what i did to get this.
somebodyssomewhere:
- boot to twrp
- open shell -> "adb shell"
- issue "echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file"
- now the sdcard should mount to the computer
now you can delete the faulty .apk of go launcher with adb commands or install a new rom:
- now you can download and copy your new rom to sdcard (ie prerooted stock)
- mount sdcard -> "mount /sdcard"
- exit adb shell -> "exit"
- tap install in twrp and install the new rom
- ignore errors about volume "misc" - the kf don't have a volume "misc"
- on the screen where you return after installation tap clear dalvik/cache
in eighter case set the bootmode back to normal:
- set boot mode to normal -> "adb shell idme bootmode 4000"
- reboot -> "adb reboot"
thank you for your replies i will try them all as well as let my friend know who is coming over to try to fix my stupid lol thank you all for your suggestions.
Update - Here is the Fix
With a bit of research and lots of help from b63 I got my Kindle Fire to work again:
1. Booted into TWRP (Recovery Mode).
2. Flashed new MD5 zip (Kindle Fire Stock 6.2.2).
3. Wiped all data off the sd card except the TWRP folder and the MD5.
4. Booted the Kindle Fire and it went straight to the lockscreen.
Thanks for all your help!
Fedor
Still am sorta stuck
Ok, so I tried to flash a MIUI ICS rom using TWRP and followed the (apparently crappy) instructions here. So, I'm stuck on the TWRP logo and have used the Kindle Fire Utility to try and reset the bootmode to no avail (it does set it and it reboots but still never progresses into the actual TWRP menu.
Any ideas?!
karlhafer said:
Ok, so I tried to flash a MIUI ICS rom using TWRP and followed the (apparently crappy) instructions here. So, I'm stuck on the TWRP logo and have used the Kindle Fire Utility to try and reset the bootmode to no avail (it does set it and it reboots but still never progresses into the actual TWRP menu.
Any ideas?!
Click to expand...
Click to collapse
would try to follow this:
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
i did finally get my kindle working again after several reboots of the pc and kindle and re installing the drivers a couple times it is now recognized. after almost a week of messing with this i have found that rooting this is alot more simple then many people are giving directions for.
what i did:
download kindlefireutility1.1
download what apps you want BEFORE you root, i have found many apps work when installed before rooting some apps may still not work..
once kindle fire utility is downloaded extract it to your c: drive
go into the kindle fire utility folder in the c drive and install the usb drivers if you need them,if not click run this will open the utility make sure you have a fresh reboot of both the kindle and pc, plug the usb cable into the kindle and pc leave it on usb mass storage mode, move any apps or files you want and press 5 to install the latest twrp MAKE A BACKUP IN TWRP BACKUP ITS EASY, DO NOT PRESS CONTINUE UNTIL KINDLE IS BACK ON THE HOME SCREEN it will say press any key a few times when using this utility.
once done you will want to install the google frame work and Go Launcher.The kindle will reboot a couple times during all this and can take up to 5 min to load so be patient.
go back into the kindle utility and then press 7 and then press #2
once this is done you can then root so hit # 3 for perm install of burrito and super user
now once those are done and you are back into the kindle home screen click on the super user icon looks like an android dude and click ok. if you dont see ok then it didnt work and try again
then click on the burrito root guy he looks like an android cop open him and if you see exit then ur good if not try again.
now your kindle should be rooted. now if you want to install a custom ROM do the same exact steps but then when it is rooted power off the kindle and press the power button once and immediately again press and hold the power button for 7 seconds until it turns orange you will then see the yellow triangle for about 2 min then it will load twrp
once in twrp go tot he folder where you saved your ROM onto your kindle, i like to copy files to the download folder..
select your rom then click on flash, you may get a couple errors but ignore them. make sure to wipe the cashe and then hit reboot and you should be good...i hope this help someone and if you need help feel free to send me a msg. im no expert but ill try
Aim rrawrimakitty
1. Download stock firmware 6.3.2 (latest KFU will get it for you)
2. Copy stock firmware to internal storage on Kindle Fire (boot up Kindle Fire and plug into your computer)
3. Download TWRP 2.2.2.1 from here. (thanks sd_shadow).
4. Download latest FFF using KFU
5. Put TWRP and FFF into a folder on your computer that contains fastboot.exe
6. Make a factory cable (google "make Motorola factory usb cable") or you can buy a premade one or an adapter. Here's an example.
7. Turn off your Kindle fire and unplug it from your computer.
8. Plug one end or your factory cable into your computer.
9. Open a windows command prompt from the folder with fastboot.exe in it.
10. While the Kindle Fire is turned off, plug in the other end of your factory cable into the Kindle fire. This should throw the KF into fastboot mode.
If you have created the factory cable correctly you should see the red Kindle screen but it should stay there and you should get a new driver install notification in Windows. Install the driver for the Kindle Fire bootloader.
11. From your Windows command prompt run these commands (substituting the names for whatever your TWRP and FFF files are called)
Code:
fastboot -i 0x1949 flash recovery twrp.img
fastboot -i 0x1949 flash bootloader fff.bin
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Now you should see the FireFireFire blue screen and you can push the power button to boot into TWRP. From TWRP you can wipe everything and install the 6.3.2 file you placed on the Kindle Fire earlier (if you want to flash a KitKat ROM like CM11 or others then you must re flash recovery with latest TWRP from here). After you are using 6.3.2 you can run latest KFU and it will work just fine.
A couple of points.
If you downgrade from 6.3.3 to 6.3.2 once you connect to wifi kindle will just download 6.3.3 update again, reinstall, and you will be right back where you started, or update will fail, and it will just reboot once an hour trying to install update. So I suggest if you want a rooted Kindle do not use a stock rom till a root method for 6.3.3. is found., or a way to stop updates.
The first time use install twrp with KFU, it will download latest, and install it, KFU will not check for updates to TWRP, it will just use the version in the recovery folder.
Once you have TWRP and FireFireFire bootloader installed, you have several options to update/downgrade TWRP... Flashify app (in rom), Fastboot.exe (in bootloader mode), Zip versions (install TWRP in TWRP).
---------- Post added at 09:08 AM ---------- Previous post was at 08:57 AM ----------
Fastboot.exe Files
There are a few options for getting Fastboot.exe, if you downloaded KFU you already have it, look in Kindle Fire Utility v0.9.9/tools folder, install SDK, or download adb-fastboot.zip
sd_shadow said:
A couple of points.
If you downgrade from 6.3.3 to 6.3.2 once you connect to wifi kindle will just download 6.3.3 update again, reinstall, and you will be right back where you started, or update will fail, and it will just reboot once an hour trying to install update. So I suggest if you want a rooted Kindle do not use a stock rom till a root method for 6.3.3. is found., or a way to stop updates.
The first time use install twrp with KFU, it will download latest, and install it, KFU will not check for updates to TWRP, it will just use the version in the recovery folder.
Once you have TWRP and FireFireFire bootloader installed, you have several options to update/downgrade TWRP... Flashify app (in rom), Fastboot.exe (in bootloader mode), Zip versions (install TWRP in TWRP).
---------- Post added at 09:08 AM ---------- Previous post was at 08:57 AM ----------
Fastboot.exe Files
There are a few options for getting Fastboot.exe, if you downloaded KFU you already have it, look in Kindle Fire Utility v0.9.9/tools folder, install SDK, or download adb-fastboot.zip
Click to expand...
Click to collapse
All really great points. I guess the purpose of the guide really comes down to showing you how to get into fastboot mode on stock firmware 6.3.3 because every software option that I tried to get into fastboot didn't work. They worked on 6.3.2 but gave write errors on 6.3.3. Only factory USB cable worked on 6.3.3
After that you're just best to go to a custom ROM to avoid all the auto-updating that you mentioned.
or my prerooted 6.3.3 zip
Sent from my DROIDX using Tapatalk
Blocking Updates On The Kindle Fire
Blocking updates on the Kindle fire is easily done once the device is rooted. Just download an Android Firewall App for the Kindle Fire. I used the DroidWall App as it was a Free Download. once installed, the DroidWall App has two methods of blocking connections to the net, White Wall and Black Wall. With the white wall you check the ones that you want to allow. With the Black Wall you check the ones you want to block. Two ways to the same result. I used the White Wall, fewer checks to block what you want and allow what you want to allow. I just went through the White Wall and checked the ones that I though needed to be allowed and it worked like a charm the first try. When checking blocks on the White Wall, make sure to not leave the pertinet block white to allow the blocking of all Apps. If you blocked the Netflix app, for instance, you could not watch any movies on Netflix. And believe me, when you have headphones or ear buds plugged into the audio jack, you could not find a nicer way to view movies without disturbing any one else. The only thing, to view netflex you have to have WiFi available.
Grampo
sd_shadow said:
A couple of points.
If you downgrade from 6.3.3 to 6.3.2 once you connect to wifi kindle will just download 6.3.3 update again, reinstall, and you will be right back where you started, or update will fail, and it will just reboot once an hour trying to install update. So I suggest if you want a rooted Kindle do not use a stock rom till a root method for 6.3.3. is found., or a way to stop updates.
The first time use install twrp with KFU, it will download latest, and install it, KFU will not check for updates to TWRP, it will just use the version in the recovery folder.
Once you have TWRP and FireFireFire bootloader installed, you have several options to update/downgrade TWRP... Flashify app (in rom), Fastboot.exe (in bootloader mode), Zip versions (install TWRP in TWRP).
---------- Post added at 09:08 AM ---------- Previous post was at 08:57 AM ----------
Fastboot.exe Files
There are a few options for getting Fastboot.exe, if you downloaded KFU you already have it, look in Kindle Fire Utility v0.9.9/tools folder, install SDK, or download adb-fastboot.zip
Click to expand...
Click to collapse
Before I invest in a "factory cable" ...
It would appear that following these 11 steps is my only option to go forward to modify/gain root access on my 6.3.3 Kindle 1st Gen.
Do you think this can be successful even though I kept getting a "ADB Status: Online / Boot status: Unknown" error while attempting to use KFU 0.9.9?
On my Windows 7 Desktop PC, First time plugged in - Device Manager shows up as "Other devices - Kindle with a yellow exclamation point and "Portable devices G:\"
After running KFU 0.9.9 "install_drivers.bat" - It shows as "Android Phone - Android ADB Interface" And "portable Devices" Disappears
[How To][Root] Kindle Fire 1 update 6.3.3 [2014]
and
Flashing FFF and TWRP without Fastboot Cable
---------- Post added at 10:19 AM ---------- Previous post was at 10:10 AM ----------
Lunarino said:
It would appear that following these 11 steps is my only option to go forward to modify/gain root access on my 6.3.3 Kindle 1st Gen.
Click to expand...
Click to collapse
[How To][Root] Kindle Fire 1 update 6.3.3 [2014]
Do you think this can be successful even though I kept getting a "ADB Status: Online / Boot status: Unknown" error while attempting to use KFU 0.9.9?
Click to expand...
Click to collapse
don't use KFU to root or flash FFF/TWRP see [6.3.3] Flashing FFF and TWRP without Fastboot Cable
On my Windows 7 Desktop PC, First time plugged in - Device Manager shows up as "Other devices - Kindle with a yellow exclamation point and "Portable devices G:\"
Click to expand...
Click to collapse
drivers were incorrect
After running KFU 0.9.9 "install_drivers.bat" - It shows as "Android Phone - Android ADB Interface" And "portable Devices" Disappears
Click to expand...
Click to collapse
That is correct
Everything worked fine until I tried "Flashing FFF and TWRP without Fastboot Cable"
sd_shadow said:
[How To][Root] Kindle Fire 1 update 6.3.3 [2014]
and
Flashing FFF and TWRP without Fastboot Cable
---------- Post added at 10:19 AM ---------- Previous post was at 10:10 AM ----------
[How To][Root] Kindle Fire 1 update 6.3.3 [2014]
don't use KFU to root or flash FFF/TWRP see [6.3.3] Flashing FFF and TWRP without Fastboot Cable
drivers were incorrect
That is correct
Click to expand...
Click to collapse
Howdy I was very happy to have had excellent success with the preceding steps. Thanks again!
I then went on to the next step - http://forum.xda-developers.com/showpost.php?p=54124313
Or actually following along with the video - https://www.youtube.com/watch?v=OJwF26qlAyc (At about 5:44 of 8:59 still on pause on our older pc)
All went well until I attempted "fastboot -i 0x1949 flash recovery openrecovery-twrp-2.2.2.1-blaze.img"
The command window reported "waiting for device"
I waited and waited then decided to take the dog for a walk while it did it's thing. That's when my daughter came home and restarted windows on me to log into her profile AND disconnected the KF and plugged it back into the wall charger!
Now win 7 device manager reports it as "Other Devices - Kindle" again and the KF screen just says Kindle in white and fire in orange static. Is that an indicator that it's stuck in Fastboot mode?
I told her that she just may have destroyed her KF making it a brick. Do we have any options to continue, restart or abort this operation?
Lunarino said:
Howdy I was very happy to have had excellent success with the preceding steps. Thanks again!
I then went on to the next step - http://forum.xda-developers.com/showpost.php?p=54124313
Or actually following along with the video - https://www.youtube.com/watch?v=OJwF26qlAyc (At about 5:44 of 8:59 still on pause on our older pc)
All went well until I attempted "fastboot -i 0x1949 flash recovery openrecovery-twrp-2.2.2.1-blaze.img"
The command window reported "waiting for device"
I waited and waited then decided to take the dog for a walk while it did it's thing. That's when my daughter came home and restarted windows on me to log into her profile AND disconnected the KF and plugged it back into the wall charger!
Now win 7 device manager reports it as "Other Devices - Kindle" again and the KF screen just says Kindle in white and fire in orange static. Is that an indicator that it's stuck in Fastboot mode?
I told her that she just may have destroyed her KF making it a brick. Do we have any options to continue, restart or abort this operation?
Click to expand...
Click to collapse
if there is no animation, then it should be in fastboot mode.
may need to reinstall drivers.
Kindle Fire Stuck in Fastboot Mode
sd_shadow said:
if there is no animation, then it should be in fastboot mode.
may need to reinstall drivers.
Click to expand...
Click to collapse
I have been able to fix the windows device drivers so that it shows up properly again.
I am unsure where to proceed from here now. Any guidance is appreciated.
Lunarino said:
I have been able to fix the windows device drivers so that it shows up properly again.
I am unsure where to proceed from here now. Any guidance is appreciated.
Click to expand...
Click to collapse
In command prompt
Fastboot devices
Should get something like 123456789
If yes retry the
Fastboot flash twrp command from before
Success!
We are all most fortunate to have such patient, knowledgeable and generous contributors in this wonderful community such as yourself!
:good:Now she's got me searching for that list of compatible flash Roms here ... FUN-FUN-FUN
Is there a particular thread that someone may point us to please?
Tip: Don't use edit to add info, just quick reply, edits don't sent out notifications.
---------- Post added at 03:57 PM ---------- Previous post was at 03:56 PM ----------
[INDEX] Kindle Fire Development *REVISED*
---------- Post added at 03:58 PM ---------- Previous post was at 03:57 PM ----------
and quick replies just get added on, if no one else has posted
Root Kindle 6.3.4
Hi all,
is it possible to downgrade to 6.3.2 if the Kindle was upgraded to 6.3.4?
Thanks
sergio.afiliado said:
Hi all,
is it possible to downgrade to 6.3.2 if the Kindle was upgraded to 6.3.4?
Thanks
Click to expand...
Click to collapse
yes, any version of firmware can be installed at any time
Sent from my XT1254 using XDA Labs