Well looks like I bricked my Kindle. (Gen 1)
I've been running root since my wife gave it to me for Christmas back in 2011.
I was following this post trying to get SwiftKey installed when I borked-up my Kindle. (Never mod stuff when tired)
Now the Kindle is stuck in a boot loop. (I edited the setting.db, I have the original backed up on the Kindle but can't access it or replace the bad version.)
When I attach my Kindle to the PC in recovery mode (TWRP v 2.8.5.0) I am unable to access the Kindle's "SD card."
I get a ghost Removable drive. (Drive F)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When selecting Mount from the TWRP menu the Kindle disconnects from the PC and won't remount.
When I try to access the Kindle via ADB, I get a strange prompt while in ADB Shell. (Note the ←[6n after the #)
When I try to run any commands from the shell I get errors saying that the command is not found.
When in recovery the Kindle is using the "ADB interface" drivers.
I used SafeRoot to reroot my Kindle (This Post)
My Kindle was running version 6.3.3
I used TWRP v2.8.5.0 (file name "openrecovery-twrp-2.8.5.0-otter.img")
FFF v 1.5 (file name "fff-u-boot_v1.5.bin")
I do have a Fastboot Factory cable.
Please let me know what other information you might need.
Any help would be appreciated.
blkdimnd said:
Well looks like I bricked my Kindle. (Gen 1)
I've been running root since my wife gave it to me for Christmas back in 2011.
I was following this post trying to get SwiftKey installed when I borked-up my Kindle. (Never mod stuff when tired)
Now the Kindle is stuck in a boot loop. (I edited the setting.db, I have the original backed up on the Kindle but can't access it or replace the bad version.)
When I attach my Kindle to the PC in recovery mode (TWRP v 2.8.5.0) I am unable to access the Kindle's "SD card."
I get a ghost Removable drive. (Drive F)
When selecting Mount from the TWRP menu the Kindle disconnects from the PC and won't remount.
When I try to access the Kindle via ADB, I get a strange prompt while in ADB Shell. (Note the ←[6n after the #)
Click to expand...
Click to collapse
That's normal
When I try to run any commands from the shell I get errors saying that the command is not found.
When in recovery the Kindle is using the "ADB interface" drivers.
I used SafeRoot to reroot my Kindle (This Post)
My Kindle was running version 6.3.3
I used TWRP v2.8.5.0 (file name "openrecovery-twrp-2.8.5.0-otter.img")
FFF v 1.5 (file name "fff-u-boot_v1.5.bin")
I do have a Fastboot Factory cable.
Please let me know what other information you might need.
Any help would be appreciated.
Click to expand...
Click to collapse
I would flash openrecovery-twrp-2.7.1.0-blaze.img in bootloader
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.0-blaze.img
see Flashing Twrp in FFF bootloader with fastboot.exe
This for the help!!
Got the Kindle to mount.
Only issue now is when I use adb shell, then try to get root with "su", I get and error saying su is not available.
Also when I try to CD to /data/data I get and error saying unable to CD.
But right now I'm installing CM11 on the Kindle just to get it working again.
Thank you again for the help.
Related
Okay guys, I'm trying to root my Fire 6.3 using KFU 0.9.5 (on Win7 Ultimate). I installed the drivers correctly and device manager shows "Android Composite ADB Interface". So I load up KFU and it says:
ADB Status: Online
Boot Status: Unknown
If I hit option 2 to install Perm Root, it gets to the part where it checks for twrp.img, then sets to fastboot mode. The kindle does reboot into fastboot, but then gets stuck on the "Kindle Fire" logo. Also, KFU just sits there waiting. See screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I terminate the batch, then rerun KFU, goto Bootmode Menu and set to Normal, I can get the kindle to reboot back to normal mode and all is good. I've tried searching the forum and all through Vashypooh's thread here, tried various tricks, but still have been unable to get it to work. Tried different USB ports, different cables (none are kindle oem), still nothing. Anyone else have this issue or know a way to fix it?
You could install twrp manually.
Get into fastboot mode (4002)
Shift + right click on your KFU "tools" folder containing fastboot.exe
Select the option that says something to the effect of "Run as command"
In the command window that pops up, enter:
fastboot -i 0x1949 flash recovery /path/to/twrp.img
!!VERY IMPORTANT!! Make sure you use that command with the twrp that comes with KFU. Accidentally using it on an older version could cause problems that you don't want to deal with.
When finished, reboot and change your bootmode back to normal.
soupmagnet said:
fastboot -i 0x1949 flash recovery /path/to/twrp.img
Click to expand...
Click to collapse
Tried this, it just said waiting for devices. One thing I noticed is when it's in fastboot, it doesn't even show in device manager. I read in a post about a separate driver for fastboot. Anyway, now it's stuck in fastboot...trying to get it back into normal mode.
You must be in fastboot mode and at the Kindle Fire logo/yellow triangle before issuing the command.
If that doesn't work hold the power button until your device shuts down and enter the command again. Turn it back on when it says 'waiting for device"
If that doesn't work, it is a driver failure. Uninstall/delete/reinstall your drivers and try again.
[Edit:] There are no separate drivers for fastboot
I switched to a different USB port and was able to use KFU to get it back to normal mode. I tried switching back to fastboot and this time it does show up in device manager in fastboot, but not with the yellow ! on it. It shows up as "Android ADB Interface". Running fastboot devices gives me a blank list.
I'm starting to wonder if it's the cable I'm using. It's my transfer cable for my EVO Design. Wondering if I should just get a factory cable and see if that fixes the problem.
Just because Windows says the drivers are there doesn't mean they're working properly. It is a well known issue with Windows and KFU.
Uninstall/delete/reinstall
[Edit:] You may have to do it twenty times or so, be patient with it.
:crying: :crying:
hi
i have a kindle fire. i rooted it on6.2.2 after that in re covery installed the 6.3.3 to unroot it . but this time i forgot to wipe it before update.
so now
theris no twrp no custom recovery no thing . same as unrooted device.
it shown me a page with this message:
---------------------------------------------------------------
your kindle has detected a problem and must clear app storage
---------------------------------------------------------------
in adb i can not see shell command and it is in recovery
adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
2XXXXXXXXXXXX recovery
adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
i can not do anything
no fastboot & nothing else
am i need to factory cable?
how can i solve my problem. my kindle is bricked for 1 month and in
[HOW TO] Unbricking/Restoring your Kindle Fire
topic no one answered me.
plz help me
anything yet
so have you ever found a sulition for this problem, i am in the same boat here. no usb connection, no adb, no recovery.... BRICKED and have not found a answer yet...... termanel commands do not work for me....... and the kindle unbricker is of no use to me as there is no connection.....
salehi186 said:
:crying: :crying:
hi
i have a kindle fire. i rooted it on6.2.2 after that in re covery installed the 6.3.3 to unroot it . but this time i forgot to wipe it before update.
so now
theris no twrp no custom recovery no thing . same as unrooted device.
it shown me a page with this message:
---------------------------------------------------------------
your kindle has detected a problem and must clear app storage
---------------------------------------------------------------
in adb i can not see shell command and it is in recovery
adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
2XXXXXXXXXXXX recovery
adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
i can not do anything
no fastboot & nothing else
am i need to factory cable?
how can i solve my problem. my kindle is bricked for 1 month and in
[HOW TO] Unbricking/Restoring your Kindle Fire
topic no one answered me.
plz help me
Click to expand...
Click to collapse
You need to get into fastboot to flash twrp recovery and start over. If you can't boot your kindle normally, then the only ways to do this are with a factory cable, or by cracking the case open.
Sent from my Amazon Kindle Fire using xda app-developers app
Is your boot animation an endless loop of the following?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jrl022 said:
Is your boot animation an endless loop of the following?
Click to expand...
Click to collapse
ROFL I get it!
Sent from my Amazon Kindle Fire using xda app-developers app
I bricked mine the similiar way. I flashed the stock software and the accidentally cleared system from TWRP. Do you have FireFireFire installed? If not the only way to unbrick it is the factory cable. Dont worry it's just normal cable with +5v on the normally not connected 4-th pin. There is a description howto build in some sticky post about unbricking.
--
Sent from my Kindle Fire using xda app-developers app
salehi186 said:
adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
This means your shell is either corrupt or missing. You need the shell to change bootmodes to fastboot without a custom bootloader. For that, you need a factory cable.
my kindle fire 2 is stuck in the blue whit fire-fire screen
I can access the twrp recovery but after a incorrect wipe i have no android or so i am assuming.
i have installed the Google usb drivers through adb but the tablet will not show up i explorer
it will show as a android device but will not load anything else.
i have also booted into the twrp and attempted to mount it and it didn't work
lastly i have tried to use a fastboot cable. i get a screen on the device that says fastboot and what looks like a stoplight with the green blinking but again will not show up in explorer
dyson77 said:
my kindle fire 2 is stuck in the blue whit fire-fire screen
I can access the twrp recovery but after a incorrect wipe i have no android or so i am assuming.
i have installed the Google usb drivers through adb but the tablet will not show up i explorer
it will show as a android device but will not load anything else.
i have also booted into the twrp and attempted to mount it and it didn't work
lastly i have tried to use a fastboot cable. i get a screen on the device that says fastboot and what looks like a stoplight with the green blinking but again will not show up in explorer
Click to expand...
Click to collapse
First check you have fastboot drivers installed correctly:
Plug the cable into your device and then the computer. Reboot the Kindle. It *SHOULD* show a Fastboot screen. Once at the screen use this command on your computer:
fastboot -i 0x1949 devices
You should see something like this:
0123456789ABCDEF
Click to expand...
Click to collapse
Then enter these commands one at a time
fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
fastboot -i 0x1949 flash boot otter2-freedom-boot-10.4.6.img
fastboot -i 0x1949 flash recovery otter2-twrp-2.6.3.0-recovery.img
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
kidicarus1602 said:
First check you have fastboot drivers installed correctly:
Then enter these commands one at a time
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B0q-ce_LYNLFQW16QWFEbDlKSUk/edit?usp=sharing
the unit wont show up in explorer at all,I have tried to run the command listed and it just says waiting for device.
I have tried rebooting into recovery reboot and still locks up
any other ideas
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is what device manager says
dyson77 said:
View attachment 2709099
View attachment 2709100
View attachment 2709101
this is what device manager says
Click to expand...
Click to collapse
any ideas?
Manually install the drivers.
-》Sent from my mind to your screen.
i have installed the google and adb drivers what other ones are there
dyson77 said:
i have installed the google and adb drivers what other ones are there
Click to expand...
Click to collapse
MANUALLY install the adb drivers.
-》Sent from my mind to your screen.
ok I have manually installed the drivers.
it then was showing up as a Otter-2
I then went through the same steps to add the drivers for it as a google usb driver.
but its still not showing up in my explorer and when i do a adb devices it doesn't show up
mind you that was all with the fastboot cable
when I hook it up with a standard usb and gho into the teamwin twrp it shows as a Kindle fire 2
and adb devices finds it as 0123456789abcdef
see attached pics
Ok I have been able to push a file to the fire 2 but the only file that will install is cm-10.1.3-otter2.zip
when i try to install anything else i get a error 7 and then it wont boot at all when i reboot it just goes into a loop.
would like to put cm 11 on there seems a little better
You need to update your recovery.
Sent from my Galaxy Nexus using Tapatalk
Bro you are in the wrong section. I repoted you so this thread should be in the right section soon.
I have a 1st gen fire, and I attempted to root it, it froze on the startup logo screen. Now I tried to reconnect it to my computer to use unbrock utility and it won't recognize the device. Did a clean install of adb drivers and I still cant find my kindle.
Thanks for the time.
You are probably stuck in fastboot. Get the necessary fastboot executable and files and run command 'fastboot devices' to ses if your serial number comes up.
Sent from my Nexus 7 using Tapatalk
SwoRNLeaDejZ said:
You are probably stuck in fastboot. Get the necessary fastboot executable and files and run command 'fastboot devices' to ses if your serial number comes up.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
And i do that how?
I tried installing twrp recovery using kfu 0.9.9 and it stops at fast reboot says waiting for device.
[fastboot] stock 6.2.1 fastboot mode without rooting or cables
http://forum.xda-developers.com/showthread.php?t=1414832
Sent from my XT894 using Tapatalk
sd_shadow said:
[fastboot] stock 6.2.1 fastboot mode without rooting or cables
http://forum.xda-developers.com/showthread.php?t=1414832
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
So i downloaded the file, what do i do with it? Im very noob at this, i rooted my HTC one no problem but this is kicking my butt lol
Wish I could just pay someone to fix this.
You need to use the adb and fastboot.exe files that are included with KFU, to push the files to the kindle.
Some basic adb instructions in my list. sd_shadow's collection of links for: Kindle Fire 1
Sent from my XT894 using Tapatalk
Im doing the manual install of the drivers and when i select the "findle fire drivers" in my download folder, it says was unable to install driver could not find driver for your device.
Did you unzip drivers?
Did you uninstall old drivers?
May need to reboot pc a couple of times
Sent from my XT894 using Tapatalk
Yes
Yes
No
Im running 8.1 if that makes a difference.
I restarted the computer and it says the same thing.
I tried to manually install the drivers from KFU and it gave me this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried another driver and got this.
Omg I finally fixed it. Just a quick run down of what I did.
Windows 8.1
Stuck on boot logo
Drivers wouldn't load.
Had to disable driver signature
manually installed adb drivers (ignored the warnings)
unpluged kindle and plugged it back in
ran KFU hit recovery.
great, I don't have win 8, and forgot about the disabling driver signature trick
kfu
Try to get your kindle fire recognize by your Pc... run Krupp. Get your adb status online..enter boot menu boot normal mode 4000
I have ADB installed, Android SDK.
I've tried to sideload and I get the error message "can't read".
Should I be changing the directory in terminal?
This is frustrating.
Thanks.
Anyone? Lol
koooba said:
Anyone? Lol
Click to expand...
Click to collapse
Is your phone coming up after using the command ADB devices?
What are you trying to sideload
No for whatever reason it's not.
I have the drivers installed, debugging on phone set.
Didn't list when I type advice devices.
What directory should terminal be in?
Wondering if I'm in the wrong directory perhaps?
Thanks
ADB could be anywhere and it'll work, double check the drivers and make sure the ADB drivers are installed and not just the MTP drivers.
What are you sideloading btw?
ADB can be anywhere, okay good to know. Thanks.
I'm trying to sideload Oxygen 3.2.1 since I'm having microphone issues - people can't hear me sometimes or my voice gets all messed up.
Apparently sideloading this update fixes this issue, at least for a few people it did.
When I connect the phone to the computer in regular mode, the device is listed.
When I go into RECOVERY mode with the phone, the computer doesn't find the device at all.
I'm going by the OnePlus instructions to turn it off and go into this mode.
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.1/
unlock bootloader
install twrp
make Nandroid Backup
download FreedomOS 3.2.1
move to phone
Wipe Caches and system, no need to wipe data (in TWRP)
Install FreedomOS ( u may need to redownload SU and flash manually if not working in FreedomOS Aroma)
Done... If still issues do a clean flash, go to twrp and Advance Wipe (Caches, Data, System) DO NOT DO STORAGE!!!!
No this will not Void your warranty with OnePlus
Click here for better instructions
Thanks Brad, first I'd like to try sideload method first if at all possible.
I can't figure out why the computer won't recognize the device in RECOVERY MODE...? Tried everything, I have to be doing something wrong.
Drivers are okay when it's not in recovery mode
The weird thing is, when the phone is OFF and plugged into the computer, the computer recognizes the device when I type "adb devices".... WTH????
koooba said:
Thanks Brad, first I'd like to try sideload method first if at all possible.
I can't figure out why the computer won't recognize the device in RECOVERY MODE...? Tried everything, I have to be doing something wrong.
Drivers are okay when it's not in recovery mode
The weird thing is, when the phone is OFF and plugged into the computer, the computer recognizes the device when I type "adb devices".... WTH????
Click to expand...
Click to collapse
what drivers did u install, so when u type "adb devices" nothing at all comes up?
I installed the drivers that are on the phone when you plug it in.
When the phone is on and plugged into the computer, it recognizes it.
This is what I get -> http://imgur.com/B3a8AMg
When I turn it off and plug it in, it recognizes the device.
When I'm in recovery mode, it doesn't recognize it at all.
i am not sure how stock recovery works, but if u are in fastboot mode, does it recognize?
with it unathurized that means u did not check the box on the phone when plugged in to ur computer.... u should get this on your phone when booted into the OS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i would try to boot into fastboot mode and push the file to ur phone and install via zip in stock recovery
and try this: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
I checked that box off, yes.
I'm about to give up, now it's not even showing a "storage" folder at all when plugged in.
Cannot even copy files into the phone, no storage showing.
OP, so many problems and it's only 4 days old.
anyone, please