How I was able to unbrick my Kindle Fire - Kindle Fire General

Hi everyone.
I managed to brick my kindle fire within an hour of purchasing it, but using the suggestions on this forum, I was able to get it back up and running in a few hours.
The method that I had to use involved suggestions grabbed from several threads, so I wanted to provide instructions on exactly how I managed to fix mine in case someone ends up in the same situation as me.
For starters, I had just updated my Kindle Fire to 6.2.1 and I was messing around with trying to get the google app manager installed. I rooted the device, and I was changing permissions in the /system/app directory when the device crashed and became stuck on the boot animation. I did not have TWRP installed at the time.
So if you are like me, or in a similar situation, this may be applicable.
These instructions assume that you have adb on your computer.
First, ensure that you are able to communicate with your device using ADB. Verify this by using the command:
adb devices
Click to expand...
Click to collapse
or by using the kindle fire utility and ensuring that the status is online.
If you are not able to communicate with your device AND have the boot animation (right to left reflection across the "Kindle Fire" logo text), you likely have a driver issue.
Several possible ways to resolve this. First, I recommend going to device manager and unistalling the driver for the android phone adb interface. Unplug the kindle fire and plug it in again. The device should show up without a driver as "kindle". Manually apply the proper driver again and check the adb connection. If this does not work, uninstall the driver again and add 0x18d1 at the end of adb_usb.ini on a line underneath "0x1949" and reapply the driver. Toss in a few shutdowns in between some of these steps if you are still having trouble. Hopefully you now have a connection to your device.
If you are not able to communicate with your device AND do not have the boot animation (right to left reflection across the "Kindle Fire" logo text), your kindle fire is in the wrong bootmode (likely fastboot).
To fix this, download fastboot.exe (if you don't already have it) and run the following command, even if you don't have an adb connection)
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
or if that doesn't work
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
Click to expand...
Click to collapse
Your kindle fire should restart and now be stuck at the logo with animation, and you should have the ability to communicate with your device through adb now.
Now, you should download the kindle fire firmware (6.2.1 as of the time of writing this) from http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620. Rename this to update.zip and drop it in the same directory as adb.exe on your pc. Execute the following command.
adb push update.zip /sdcard/
Click to expand...
Click to collapse
Now, you need to use fbmode to enable the fastboot mode, per pokey9000's instructions at http://forum.xda-developers.com/showthread.php?p=20755810
Assuming that that was able to complete successfully, you need to flash TWRP 2.0 per pyrostic's instructions at http://rootzwiki.com/topic/12363-ho...our-kindle-fire/page__pid__301703#entry301703
You now should be stuck at a screen with a yellow triangle. Pressing the power button several times until it turns orange should bring you into the recovery screen. Do the following:
Wipe cache
Wipe dalvik cache
Factory reset
Go back to the home screen and select install -> update.zip
And when that's done, you can tell it to reboot.
It'll think for a minute or two at the kindle fire boot, and then it will go into the initial setup screen. You're now the proud owner of a working fact0ry default kindle fire!
Quick note: I wrote this from memory quickly to try to help anyone experiencing problems. I'm no android expert, so if there are ways to improve on this or corrections to be made, please let me know so that the community can benefit.
And I don't want to appear to take undue credit for any of these instructions. I did not come up with anything on this guide on my own, everything came from various threads on this forum. These are just the steps that I followed to successfully bring my kindle fire back from death.

Man, My Kindle Fire does not even get detected by my PC

Now, you need to use fbmode to enable the fastboot mode, per pokey9000's instructions at http://forum.xda-developers.com/show...php?p=20755810
Assuming that that was able to complete successfully, you need to flash TWRP 2.0 per pyrostic's instructions at http://rootzwiki.com/topic/12363-how...03#entry301703
You now should be stuck at a screen with a yellow triangle. Pressing the power button several times until it turns orange should bring you into the recovery screen. Do the following:
Wipe cache
Wipe dalvik cache
Factory reset
Go back to the home screen and select install -> update.zip
And when that's done, you can tell it to reboot.
It'll think for a minute or two at the kindle fire boot, and then it will go into the initial setup screen. You're now the proud owner of a working fact0ry default kindle fire!
****When I run the fbmode I am getting stuck on the boot logo screen. Can someone please help me??

that is normal - you are in fastboot mode now - adb commands don't work in this mode - fastboot commands do - resume with the description ...

Thanks for your post.
I also "bricked" my kindle the day I got it but my issue was not having the correct drivers installed when I started the rooting process. My drivers would recognize the Kindle when it was booted normally but when it went into fastboot mode the Kindle would just show as "Unknown Device" in device manager. In windows you can't remove the drivers for unknown device so I had no way of backing out the old drivers.
What I ended up doing was grabbing my other laptop and making sure I had the correct drivers installed, then connected the kindle and was able to back it out of fastboot mode.
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
umarsl said:
Man, My Kindle Fire does not even get detected by my PC
Click to expand...
Click to collapse
Does it show up as "unknown Device" in device manager?

you can uninstall the drivers
win 7:
http://www.petri.co.il/removing-old-drivers-from-vista-and-windows7.htm
xp:
http://www.techrepublic.com/article/removing-unused-device-drivers-from-windows-xp-machines/6017628

Just wanted to say thanx for the post. I ran into the exact same condition that the op did where I inadvertently screwed up the permissions on the /system/app directory which caused the kf to wig out and brick. I wished I had seen your post earlier because I ended up going to many posts and piecing together the information which was a little confusing at times. The op is great and I just wanted to point out two observations that seemed to me the most confusing working through the issue and getting it unbricked and hopefully will bring some clarity for folks.
1. Understanding the different states of the "kindle fire" logo.
- Shimmering animation and appears to loop = normal boot mode and is the state that you should be able to communicate with adb. This is the state where you can push files to the kf like twrp and fbmode which is what is needed to get kf in fastboot mode when bricked like this.
- The logo is static and does not "wink" out or loop = fastboot mode. This is when you use fastboot commands on your PC to change boot modes and also execute files such as twrp to get it installed once you pushed it to the kf with adb.
2. USB Drivers.
- This can be a real killer. After playing with this for hours, the one thing that I found that helped the most was when the driver stopped working I would unplug the kf from the PC and then hard reboot the kf (hold on/off ~20 seconds) then just plug back in, don't use on/off. Keep the device manager open on the PC and watch. You will soon start to see a pattern when you have the right driver and do this a few times.
Once these things are ironed out all eventually works out. BTW, this occurred after my kf was upgraded to 6.2.2. So the instructions and tools and everything else you will find still works. Good luck to anyone working through this issue. Just remember, if you can communicate with it, it's almost certain there is a way to recover it.

Related

Do I Now Own A Brick?

So im stuck on the kindle fire logo on boot after using kindle fire utility V .8 and well i think im bricked. No commands are working and the power button is basically useless. My main question is ive seen some people say they sent it to amazon and got a new one. How would i go about doing this?
Why don't you go read the many threads describing your exact same problem you can fix it.
No you can not return it your warranty is now void.
go into irc with vashypool and he might be able to fix it, donate if u can..
mguinta25 said:
So im stuck on the kindle fire logo on boot after using kindle fire utility V .8 and well i think im bricked. No commands are working and the power button is basically useless. My main question is ive seen some people say they sent it to amazon and got a new one. How would i go about doing this?
Click to expand...
Click to collapse
It does seem that this is a very popular problem... I am not sure what amazon's requirements are exactly on returns once bricked especially if you rooted, but I will say with how popular this problem seems to be, I am sure many of the experienced devs on this site are working on a fix for this (hopefully)... If not I would suggest donating to one of your choice if possible for the work that they have already put into it, explain your problem to them and I am sure it would motivate them to come up with an easy fix for this. Whatever happens you should definitely post back with your findings so that you can help the comunity further with knowledge...
it's not bricked - i never saw a really bricked one
he's in the wrong bootmode - a common problem and a matter of minutes
read the kfu thread in the dev section !!!
basically here are the following things to do:
1. run kfu - select change bootmode - select normal -> success ?
if not
2. shutdown kf by holding button for ~20 sec and power back up - then point 1 -> success ?
if not
3. disconnect and shutdown KF - shutdown computer and turn on again (no restart) - connect kf (don't turn it on - kf will do at connect) - then point 1 -> success ?
if not
4. you have a driver issue - did you run install_drivers.bat before using KFU ? - correct your driver problem - then point 1 -> success ?
if not
5. ask further
b63 said:
it's not bricked - i never saw a really bricked one
he's in the wrong bootmode - a common problem and a matter of minutes
read the kfu thread in the dev section !!!
basically here are the following things to do:
1. run kfu - select change bootmode - select normal -> success ?
if not
2. shutdown kf by holding button for ~20 sec and power back up - then point 1 -> success ?
if not
3. disconnect and shutdown KF - shutdown computer and turn on again (no restart) - connect kf (don't turn it on - kf will do at connect) - then point 1 -> success ?
if not
4. you have a driver issue - did you run install_drivers.bat before using KFU ? - correct your driver problem - then point 1 -> success ?
if not
5. ask further
Click to expand...
Click to collapse
Thank you just had to change the bootmode!
My KF is in a boot loop. Boots to the kindle fire logo, sometime does the animation (highlights letters from right to left), sometimes doesnt.
I've downloaded the KFU and installed the drivers. When I run the bootmode menu, it says ADB Status online, ADB rooted no (even though my kindle IS rooted).
When I try to change bootmode to normal, I get a number of errors:
Error: Could not access the Package Manger. Is the system running?
Error type 2
android.util.AndroidException: Can't connect to the activity manager; is the system running?
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
mount: Operation not permitted
mount: Operation not permitted
then it says root activated and that the kindle is running in root mode
<idme> Invalid permission
reboot: Operation not permitted
Then despite all the errors, says kindle has been told to reboot in normal mode.
Kindle still gets stuck in boot loop when I try to power on. I've tried powering off the kindle and then on and retrying, I've tried powering off and disconnecting the kindle and computer, still no luck.
Any advice?
if your kf is constantly rebooting (2-3 sec) read this thread:
http://forum.xda-developers.com/showthread.php?t=1424379
if not and you can connect via kfu set bootmode to normal or do it manually depending on the bootstate your in:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
FWIW, Amazon are really liberal when it comes to returns on the entire Kindle family.
At a X-Mas Eve party, a friend dedcided it would be a good idea to stream some things with AirTwist and left his KF laying on a table, it recieved some pretty serious damage from being dropped, stepped on and having stuff spilled in it, we dont know how, but Amazon replaced it.
So I would say your best bet in case of brick is to at least simulate damage=\
b63 said:
1. run kfu - select change bootmode - select normal -> success ?
Click to expand...
Click to collapse
Thank you.
I just wanted to mention this "as it might help others": I was stuck in Kindle fire screen, can't boot, and can't see the ADB status.
In the device manager I was seeing the yellow mark.
I restarted the device, then the yellow mark went.
Selected change bootmoe -> normal from KFU (even though the status is offline), and worked!
Thank you again.
Having this issue
b63 said:
it's not bricked - i never saw a really bricked one
he's in the wrong bootmode - a common problem and a matter of minutes
read the kfu thread in the dev section !!!
basically here are the following things to do:
1. run kfu - select change bootmode - select normal -> success ?
if not
2. shutdown kf by holding button for ~20 sec and power back up - then point 1 -> success ?
if not
3. disconnect and shutdown KF - shutdown computer and turn on again (no restart) - connect kf (don't turn it on - kf will do at connect) - then point 1 -> success ?
if not
4. you have a driver issue - did you run install_drivers.bat before using KFU ? - correct your driver problem - then point 1 -> success ?
if not
5. ask further
Click to expand...
Click to collapse
I am having this exact issue and i have tried to install drivers but it will not install the drivers it just brings up a code 10 this device cannot start. The device is in my DM as android ADB Interface but it has the yellow "!" sign. kfu when trying to fastboot just says waiting for device and none of the drivers i have tried allow KFU to do its thing and normal boot it.
I just wanted to add, I just had a similar issue last night. I was loading up the MIUI ICS rom, wiped like normal and rebooted to the firefirefire triangle. ...Did not like... Anyhow, I was following the many unbrick guides and couldn't get anything to work. The KF would reboot, and my system (win 7 x64), would see the KF as an unknown device with, "error 43", device cannot start. Then the unit would disconnect(windows sound) from usb, and reconnect and disconnect and then go no where. Each time I rebooted the KF it would do the same thing, also would not go into recovery if I hit the power button during boot. I made a factory cable from an extra usb micro cable I had, to force it into fastboot, and it would come up in device manager as an android usb device. still could not see it via adb directly or in KFU. I found it was the android sdk drivers messing it up. I uninstalled the Android SDK and reinstalled the KF driver package that came with the KFU and viola! I was able to run the TWRP install, and successfully get into recovery. I tried the MIUI ICS Rom install again with a new download just in case, but with the same results. wash, rinse, repeat. I restored my previous ROM in recovery and it booted up like a champ. I'm assuming that since the SDK drivers were causing the issue, I could have probably got the fastboot in firefirefire(during boot) to work properly, and not needed the factory cable. Just wanted to share my late evening fun.
Cheers!
Rob
alfy984 said:
I am having this exact issue and i have tried to install drivers but it will not install the drivers it just brings up a code 10 this device cannot start. The device is in my DM as android ADB Interface but it has the yellow "!" sign. kfu when trying to fastboot just says waiting for device and none of the drivers i have tried allow KFU to do its thing and normal boot it.
Click to expand...
Click to collapse
maybe this helps to sort out the driver issue:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6

[Q] [Solved] Kindle fire stuck on yellow triangle and no working drivers.

So I JUST got this thing today, and was trying to get android marketplace.
here is the list of things that have happened so far:
1. after moving vending.apk to apps folder, main GUI crashes and hitting the home button only switches through apps
2. decide to reboot since it is the next step for installing marketplace anyway
3. stuck in boot loop with shiny animations
4. manage to get TWRP installing
5. post says I need to hit 'reboot' on my kindle. I do.
6. stuck on yellow triangle, with all the drivers no longer working no matter what I do.
known fixes I've tried:
-uninstalling and reinstalling drivers
-rebooting computer and kindle multiple times
-selecting 'android driver' or whatever
-pressing the home button right after startup to try and get back into recovery mode
when looking in the device manager, it used to come up as 'kindle' with the yellow exclamation mark. now it only shows up as 'unknown device'
I JUST got this thing, and it wasn't from an official seller, so im basically on my own... anyone know what I should do?
EDIT: now the device manager IS saying 'android composite ADB interface' but it still wont how up in the kindle fire utility...
EDIT2: I was able to get it into restore mode, and get TWRP to pop up. I then have it clear the cache, and restored back to factory defaults. when I told it to reboot, it rebooted back to recovery mode. I then used the Kindle Fire Utility to set it to normal boot mode.
NOW, the problem im having is that it is stuck in a boot look with the animated 'kindle fire' logo.
Click to expand...
Click to collapse
Its working now! turns out that originally, all I needed to do was change the system permissions back to 755.
Do you have TWRP installed?
If so this link may be helpful to you. I've read a lot of jayceooi's stuff; he may be able to help you.
http://forum.xda-developers.com/showthread.php?t=1430446&highlight=jayceooi
ra0ultortugas said:
Do you have TWRP installed?
If so this link may be helpful to you. I've read a lot of jayceooi's stuff; he may be able to help you.
http://forum.xda-developers.com/showthread.php?t=1430446&highlight=jayceooi
Click to expand...
Click to collapse
Yes, I have twrp 2.0 installed. It had worked fine until yesterday.
have a .android folder in your home dir ?
should have adb_usb.ini in it with this entry: 0x1949 and 0x18D1 - if not add it
then it should show up in kfu
to test manually:
cd with an (elevated) command promt to the tools folder of kfu and do:
adb devices - should return serialnumber and bootmode
b63 said:
have a .android folder in your home dir ?
should have adb_usb.ini in it with this entry: 0x1949 and 0x18D1 - if not add it
then it should show up in kfu
to test manually:
cd with an (elevated) command promt to the tools folder of kfu and do:
adb devices - should return serialnumber and bootmode
Click to expand...
Click to collapse
When I went thru this procedure it says "list of devices attached"
and empty line (So no devices found).
I think my problem is drivers. Since my pc recognizes kf for several seconds only.
During those several seconds nothing really I can do.
Use the liux method. Worked for me.
http://forum.xda-developers.com/showthread.php?t=1430038
wigsey said:
Use the liux method. Worked for me.
http://forum.xda-developers.com/showthread.php?t=1430038
Click to expand...
Click to collapse
thanks. will give it a try.

[Q] Kindle fire stuck at kindle logo

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?
you have "kindle fire" logo - static - not animated - right ?
then it should be in fastboot mode
try to update the drivers manually - the right driver for this mode is "android adb interface"
now you should be able to communicate
try "fastboot -i 0x1949 getvar product" -> it should return "kindle"
then try to follow this thread starting at point 4:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
Thank you
Thank you for replay, but i don't know where i should wright this command for fastboot, is it at command prompt? and should i wright also the drive letter for kindle fire? please advice and don't be annoyed from my simple question because i did not try to wright commands before but i usually use KF utilities!
a bit more information would be helpful:
what computer (os/bit) ?
to start recovering some things would be good to talk from the same things:
if you allready have the newest kfu (0.9.2) please move it to c:\ and rename it from "kindle fire utility" to "kfu"
now you can open a (elevated) command prompt and cd to c:\kfu\tools
here are all necessary commands
this is where you write the commands and leave this window open - you will need it all the time
now you should be able to follow my last post

[Q] Silly me, bricked my kindle fire after TWRP seemed to fail.

So, as many new KF rooters have, I seem to have bricked my KF. I rooted it just fine, but when installed TWRP through KFU .93 the process seems to have stopped. After waiting over an hour and reading countless "I've been stuck installing TWRP through KFU .93" threads, and seeing many "I switched to .91 and it worked fine" responses, I decided to give that a shot. After unplugging and hard resetting my KF, it is still stuck on the KF logo screen. No yellow box, just the logo screen.
When I plug the KF into my computer, the device is recognized and the proper KF drivers are installed, but I can't get adb to work at all. Every attempt returns a "Device not found" or a "Server didn't ACK." The device does not show up on my list of attached devices, but in Device Manager it is loaded.
I'm unsure of what the next step should be, as I can't get the hardware to respond to anything but resets, and I can't get the software to communicate with the hardware from my PC. I really don't want to admit defeat and contact Amazon.
*edit* Through more research I've made some progress. Opening KFU and selecting the bootmode option, and then when it says "waiting for device" hard resetting the KF and letting KFU change the bootmode to Recovery has done some things. I got a message saying "Failed ..." but it flashed too fast for me to read. Then, upon several restarts, I received a message saying that the KF needed to factory reset, which it is doing now.
As of right now I have a Factory Resetted, working KF. My updated question is now "Where did I go wrong?"
I assume it had to do with TWRP, as it was working until then. Should I redo the whole process using KFU .91 instead of .93? The root went of without a hitch, but the TWRP was what killed me.
Also, do I do Root THEN TWRP, or TWRP THEN Root? I guess I might need Root access to install a Recovery console, but I'm unsure.
use KFU to root, then hit up my gscript install method in the development thread. easy peasy.
but for the record, you were in fastboot, so it won't see adb commands..
fastboot -i 0x1949 oem idme bootmode 4000 maybe woulda saved you. but avoid fast boot entirely, n use my gscript method.
heres how i did it
I was trying to unbridled my kindle fire all last night and about 5hours today.here is how I did it (don't get your hopes up too high,it might not work)
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

Fastboot discussion.

I have searched and couldn't find a fastboot thread. So here it is.
I found out fastboot is working on Linux.
Bad news is Windows seems to need another driver for fastboot.
Please help look for a windows driver or make one.
The fastboot commands all seem to work fine.
Here you guys go! Enjoy.
Code:
[SIZE=5][SIZE=3][SIZE=5][SIZE=3]adb reboot-bootloader
fastboot -i 0x1949 command_here[/SIZE][/SIZE][/SIZE][/SIZE]
Just noticed pokey9000 said this but it was overlooked.
pokey9000 said:
That's it. And you're running fastboot as "fastboot -i 0x1949 your_command_here", and you have udev set to allow permissions for that VID (or are running as root) in Linux?
Click to expand...
Click to collapse
Thank you.
Still don't believe me, look at the last picture.
I'm having issues with some commands. Please test it out and enjoy!
shimp208 said:
In the Fire TV section a fastboot cable was created by splicing two USB A to B cables together, so that the A to A ends were together which when connected from your computer to the Fire TV on bootup put the device in fastboot mode, in the process then your computer recognized (Running Windows 8 was the example given) the device and installed the proper drivers. Since the devices are similar, a potential solution would be use the cable, have the computer recognize it and install the drivers, then backup the drivers, and share them here for others to use.
Click to expand...
Click to collapse
I'm quite sure the cable isn't the issue. Also that's just it, I can't get windows to recognize it or find much info about it. The adb driver for the device isn't enough I guess. The funny thing is windows says it's working properly as 'Kindle' for a little while when you plug it in (while in bootloader) then device manager refreshes and reports 'cannot start'. I tried launching 'fastboot devices' many times but still nothing. I think it needs a software fix and not a hardware one but I have no past experience using fastboot. So... noob alert.
btw the driver windows tries to use is ms_comp_mtp(Generic driver installed=true) and adb uses the Amazon one on the fourm here.
DevNode status Value:
01802400
DN_HAS_PROBLEM
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER
Also Bus reported device description Value:
fastboot
VID=1949 & PID=000C
(0x1949 && 0x000c)
Current Driver files:
\system32\DRIVERS\UMDF\WpdMtpDr.dll
\system32\DRIVERS\winusb.sys
\system32\DRIVERS\WUDFRd.sys
\system32\WpdMtp.dll
\system32\WpdMtpUS.dll
We need someone good on this.
I have a problem
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Hashcode said:
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Click to expand...
Click to collapse
Is flashing the stock .bin file any different than doing a factory reset?
I am bricked, have root, have adb, can get fastboot using adb reboot-bootloader in windows 8. I also have a Linux box if necessary.
saphi95 said:
I have a problem
Click to expand...
Click to collapse
I would recommend taking a look at this thread here, specifically the "Fixing No Permissions Error" section which should allow you to fix the problem your encountering.
dcoig1 said:
Is flashing the stock .bin file any different than doing a factory reset?
I am bricked, have root, have adb, can get fastboot using adb reboot-bootloader in windows 8. I also have a Linux box if necessary.
Click to expand...
Click to collapse
Fastboot works with win8? Not with win7.1 If you have fastboot working with win8 please go to device manager (when your in the bootloader) click properties on the device then look for what driver it uses.
Hashcode said:
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Click to expand...
Click to collapse
My main reason is to get fastboot working with windows. I just can't. Linux seems to work with fastboot but I can't access it via windows.
Just uninstall the kindle driver and replace it with the generic fastboot one
hello all,
i've kindle fire hdx 7" , no adb, grey screen logo then shutdown and goes to black screen.
when connected using cable, it show new devices... QHSUSB_BULK and sometime unknown devices.
press hold power button and volume up only go to recovery mode, but cannot recovery the system..
always go to grey screen logo...
sorry for my bad english language...
hope all of you, understand what i mean here
i need solution for fix the problem soon. thanks
I think all that works is reboot into fastboot mode. Windows 8 says no drivers are loaded. I tried a command (can't remember what) and it just went out to lunch so... I guess windows 8 isn't working either. Only to put the device in fastboot.
there are three oem commands:
oem device-info
oem idme
oem relock
Click to expand...
Click to collapse
but it doesn't support oem unlock so there must be another way of unlocking the bootloader, when you try some of the commands the device returns "not allowed for locked hw". Does anyone know what the "hw" is ?
hw = hardware?
MaximilianOzora said:
hello all,
i've kindle fire hdx 7" , no adb, grey screen logo then shutdown and goes to black screen.
when connected using cable, it show new devices... QHSUSB_BULK and sometime unknown devices.
press hold power button and volume up only go to recovery mode, but cannot recovery the system..
always go to grey screen logo...
sorry for my bad english language...
hope all of you, understand what i mean here
i need solution for fix the problem soon. thanks
Click to expand...
Click to collapse
Read up on this bud.
Hi,
I have a bricked kindle hdx 8.9 that stops at "Kindle Fire" boot screen. I am a newbie at these things.
Just discovered that it still respond to some adb queries. Sounds like there is still hope to recover... Could it be the bootloader is messed up? Anyway to reload an image boot file to repair?
Also "fastboot reboot-bootloader" puts it into fastboot mode...with the status "ready"....and i just dont know how to proceed. Any one can help?
uhg
Facepalm
just back a little: was rooted in April but with subsequent amazon auto updates - didn't have su status. But I was able to load apps & files, installed vpns, quite a few docs,mp4 files, etc. Not really using much of the new freedom or whatever was left of it... Nothing exciting.
Was working well until one fine sunday afternoon, just 2 weeks ago when it just simply stopped after rebooting from a previous low battery charge. Was told it could be an interrupted routine update when the battery power just fell below threshold - but thot it wouldn't have erase the previous image before the new update is effective. Or it could possibly be a deleted file that is related to the booting process as I did a bit of clean up prior to the last reboot?
In the meantime, I did some adb shell/pull to explore or extract the files, photos,etc in /sdcard & other places back to my PC just in case they were not backup by the cloud. Maybe it was not bricked...but just lost a boot file or something...
In a bad situation, have absolutely zero ADB access as my build.prop is botched (bad permissions) and I did a factory reset in hopes of recovering. There is a "fastboot cable" on amazon that says it will reboot a hdx into fastboot mode, but I'm unsure of it's legitimacy. Help?
here try
Tumbtack said:
In a bad situation, have absolutely zero ADB access as my build.prop is botched (bad permissions) and I did a factory reset in hopes of recovering. There is a "fastboot cable" on amazon that says it will reboot a hdx into fastboot mode, but I'm unsure of it's legitimacy. Help?
Click to expand...
Click to collapse
This thread.read read read http://forum.xda-developers.com/showthread.php?t=2588608
I don't quite understand. Why is a special cable required for this? What makes it any different from the standard one that comes with the device?
I don't know if this will add anything to the discussion...but I can confirm fastboot is working on Ubuntu 14.04. I am using a kindle fire HDX 7" and it detects it on devices..and most commands work. Sometimes the terminal must be closed and reopened for commands to go through..
fastboot oem unlock works..or rather it says "Okay" but I'm unable to flash anything.

Categories

Resources