Develop Bugs

KF Failed Root

Hi guys! I'm new to the forum but not new to the IT world and not new to Linux or Android devices.
I'm stuck at the Kindle Fire screen after a failed attempt to root the device. Here's what I did. I'm hoping somebody can please help me. I did lots of Google searches to try to solve my issue and I can't seem to find the right solution.
So here's the background. I tried to root my KF by using this process http://www.pcworld.com/article/244303/how_to_root_your_kindle_fire.html on an Windows 7 VM. Then I found that SuperOneClick didn't work for KF6.3. So then I tried to KF Utility v.0.9.5 http://forum.xda-developers.com/showthread.php?t=1399889
I selected the option to root the KF. After it went through the process and I got the Kindle Fire screen (which is sounds like the KF is in the fastboot process) I couldn't get anything to work at that point. I couldn't get the VM to even see the KF nor Ubuntu (which is the main OS of that laptop). So then I figured I bricked the device. So I followed these instructions http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/ but that won't work ecause the KF isn't being recognized by the OS. SO at that point, I couldn't get anything to work. So I rebooted the laptop (which is running Ubuntu 12) and the KF booted back up and it fired back up.
If I power off the KF and turn it back on, it gets stuck at the KF bootup screen.
So at that point I decided to throw Windows 7 on a different laptop that I have and see if I can get it to work. So I installed java & Android ADK for my OS (Windows 7). I installed the USB driver and updated the packages. So I go through these instructions first http://forum.xda-developers.com/showthread.php?t=1568340 and I can't get the KF to be recognized as a device through adb. So I go back to the PC World instructions (linked above) and I follow steps through step 8. And I still can't get the KF to be displayed through adb. When I try to kill the adb server and then enter adb devices, I still can't get the KF to be recognized.
Oh and btw, Windows 7 does recognize the device as a "Kindle".
Any help would be greatly appreciated.
Sparty On!

Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works:
Sent from my Amazon Kindle Fire using Tapatalk 2

Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.

I'm having the same problem I think since windows doesn't recognize my kindle I can't install the drivers.

AndroidSparty said:
Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.
Click to expand...
Click to collapse
Us the same commands without -i 0x1949
fastboot oem idme bootmode 4000
fastboot reboot
Sent from my Amazon Kindle Fire using Tapatalk 2

ammubarak said:
Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works
Click to expand...
Click to collapse
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567

From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA

I received mine with 6.3 and KFU wouldn't recognize it even after using the driver installation. BUT I found way around it. You need to install the drivers manually, and then KFU will work. Download the drivers, then extract the .android folder (create it if you don't have one) to
C:\Documents and Settings\YOURUSERNAME\.android open up your device manager, click on the Kindle and follow the UI to select the .android folder. Restart and use KFU. Enjoy!

soupmagnet said:
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567
Click to expand...
Click to collapse
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
backspacepc said:
From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!

AndroidSparty said:
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!
Click to expand...
Click to collapse
Actually it will, status will still be off line, just select the boot mode option, and then on the next screen select normal bootmode
Sent from my MB860 using XDA

For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.

soupmagnet said:
For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.
Click to expand...
Click to collapse
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA

backspacepc said:
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Actually...I'm a she.
Since I have both available to me...it sounds like I should scrap the Windows (which is an understatement anyway) and use Linux/Ubuntu. That I can do!

I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.

AndroidSparty said:
I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA

backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
You may also want to try to rerun your root script, oddly enough I've had that work before too.
Sent from my MB860 using XDA

AndroidSparty said:
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Did you notice the second post in the Linux tutorial?
kinfauns said:
Thanks for the guide on setting this up for linux. I just wanted to point out a small error in the instructions. The echo command above is incorrect and will not do what you intended. It should be corrected to
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
Click to expand...
Click to collapse

backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
I just ran kfu and I I was able to get it to do a normal boot. YAY!
Then I ran the .bat file in the KFU and I selected the permanent root. During the activating fastboot, it said that "Oops something went wrong...." it couldn't find the kindle. Then it installed twrp.img is missing and it downloaded successfully. So then I got the Notice, and it's installing TWRP and it's waiting for the device. I turned the Kindle off & on a few times to get the KFU to recognize the Kindle, and no luck. At least I was able to boot into the KF while it's still still waiting for the device. BUT....at this point during the TWRP install process, it's waiting for the device and not recognizing it.

soupmagnet said:
Did you notice the second post in the Linux tutorial?
Click to expand...
Click to collapse
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.

AndroidSparty said:
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.
Click to expand...
Click to collapse
I can't imagine why using vi would make any difference but you could try gedit to see if it works.
As for TWRP, you could install it manually (Windows). Make sure you have a connection with adb/fastboot and use KFU to set your device to fastboot mode. Keep in mind when you do this that you may have to go through the whole process of fixing your drivers again (blame Windows/KFU).
When you're in fastboot mode, hold the power button until the device shuts down.
Shift + right click the KFU folder that contains fastboot (tools) and open as a command
In the prompt that comes up, enter:
Code:
fastboot -i 0x1949 flash recovery /path/to/twrp2.1.img
When your prompt says "waiting for device", turn the device back on.
Make sure it's twrp 2.1 Version 2.0 is installed in a different manner and will most likely cause problems if installed with the "flash recovery" command.

Kindle Fire Brick Utility not working

So i think I bricked my kindle fire. It is rooted and when trying to install a new ROM, i accidentally selected the fastboot option. Now, when I power it on, all i get is the logo and it never loads. I cannot get into the boot manager to try anything. I have tried the Kindle Unbrick utility from this link: http://forum.xda-developers.com/showthread.php?t=1428428 and it says waiting for device when I run the stuck on logo option. Is there anything else I can do? I really dont want to get another one. Any help would be appreciated! I can't post in the development forum so thats why i posted here. Thanks everyone.

What version of Windows are you using?

Read the WHOLE first post of the Unbrick Utility thread. It's a driver problem.

Thanks I got it to work now but now when I plug it into the USB, it does not show that I can open it and drop files. I go into TWRP and try to mount the USB and it will not let me and I am unsure what to do!

roykurka said:
Thanks I got it to work now but now when I plug it into the USB, it does not show that I can open it and drop files. I go into TWRP and try to mount the USB and it will not let me and I am unsure what to do!
Click to expand...
Click to collapse
If you're using an ICS ROM I don't believe mounting "mass storage" works on all of them.
Does it saying anything when trying to mount USB in TWRP? What does "won't let me" imply? Windows or TWRP throws an error message?

When I go into TWRP and go to MOUNT and then try to select Mount SDCard it will not let me check the box. I have a ROM running on it now but I cannot access the SD card when I plug it into the computer.

roykurka said:
When I go into TWRP and go to MOUNT and then try to select Mount SDCard it will not let me check the box. I have a ROM running on it now but I cannot access the SD card when I plug it into the computer.
Click to expand...
Click to collapse
What ROM are you using?

nchevaux said:
What ROM are you using?
Click to expand...
Click to collapse
i am using CyanogenMod 9.0.0-RCO-otter-UNNOFFICIAL
Also, when i go to the about tablet on the Kindle and look at Model Number, it shows Galaxy Nexus.....

Any other suggestions or help?

roykurka said:
Any other suggestions or help?
Click to expand...
Click to collapse
Boot into TWRP and get to a prompt using adb shell. Then use this command to open parted...
Code:
parted /dev/block/mmcblk0
When you get to the "(parted)" prompt...
Code:
print
The last line, the media partition, is what gets mounted as /sdcard on your device. It should have a "fat32" file system type. If you don't have that, you need to make a new filesystem on that partition.
Code:
mkfs 12 fat32
12 is the partition number and fat32 is the filesystem type you want to use to format the partition. If memory serves, parted will ask you for this information again to confirm. Remember... 12 and fat32. Once you are done, you can...
Code:
quit
Once you've done that, TWRP should be able to see the partition and allow you to mount it on your host computer. You might have to restart TWRP... I don't remember.

I have not been able to get adb to run. When i boot to TWRP and go to the command prompt and type adb devices it says " 'adb' is not recognized as an internal or external command, operable program or batch file."
I set the path to where the android sdk is located and it still doesnt work.
Im sure I sound like a newb or something but I am just not as tech savy with these kind of things. thanks everyone for your help with this.

roykurka said:
I have not been able to get adb to run. When i boot to TWRP and go to the command prompt and type adb devices it says " 'adb' is not recognized as an internal or external command, operable program or batch file."
I set the path to where the android sdk is located and it still doesnt work.
Im sure I sound like a newb or something but I am just not as tech savy with these kind of things. thanks everyone for your help with this.
Click to expand...
Click to collapse
Find the adb executable through Windows Explorer. Once you find the folder containing adb, shift-right-click inside that folder and select "Open command window here" and then you'll be able to use the adb command.
Another way to do it is to download the Kindle Fire Utility distribution and follow the third post in this link...
http://forum.xda-developers.com/showthread.php?t=1552547
You don't have to set the path to anything special if you do it one of those two ways.

roykurka said:
I have not been able to get adb to run. When i boot to TWRP and go to the command prompt and type adb devices it says " 'adb' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
It seems you have set your path incorrectly. I found it easiest to just copy the entire platform-tools folder to the root of C:\ and run adb from there (You could also use a Windows shortcut to cmd with "start in" filled out, or use shift-right click through explorer).
Definitely try to get adb working; when I first rooted my Kindle it took me an hour to fix a boot-loop without adb (damn drivers), and only seconds with adb.

kinfauns said:
Boot into TWRP and get to a prompt using adb shell. Then use this command to open parted...
Code:
parted /dev/block/mmcblk0
When you get to the "(parted)" prompt...
Code:
print
The last line, the media partition, is what gets mounted as /sdcard on your device. It should have a "fat32" file system type. If you don't have that, you need to make a new filesystem on that partition.
Code:
mkfs 12 fat32
12 is the partition number and fat32 is the filesystem type you want to use to format the partition. If memory serves, parted will ask you for this information again to confirm. Remember... 12 and fat32. Once you are done, you can...
Code:
quit
Once you've done that, TWRP should be able to see the partition and allow you to mount it on your host computer. You might have to restart TWRP... I don't remember.
Click to expand...
Click to collapse
When i try the first command, i get the same response saying parted is not recognized as an internal or external command, operable program or batch file.
I have the kindle in TWRP and connected to the PC. What do I do now?

roykurka said:
When i try the first command, i get the same response saying parted is not recognized as an internal or external command, operable program or batch file.
I have the kindle in TWRP and connected to the PC. What do I do now?
Click to expand...
Click to collapse
okay... I'm going to make this super easy for you... get ADB working...
1. Download attached "adb.zip"
2. Extract adb.zip to a folder
3. Double-click "CLICK ME!!!"
4. Type "adb" and see instructions come up
5. Type "adb devices" and see a 12-digit code
now reread your own thread and try all those instructions again in ADB
P.S. type "ADB shell" before trying the instructions from kinfauns

When I type the adb devcies it says "list of devices attached but does not show anything.
I apologize for probably something so simple

roykurka said:
When I type the adb devcies it says "list of devices attached but does not show anything.
I apologize for probably something so simple
Click to expand...
Click to collapse
I think you should back up a bit and read this...
http://forum.xda-developers.com/showthread.php?t=1552547
Start at post #1... follow the steps in #2 and confirm your device drivers are getting loaded properly... study #3 for fastboot and adb commands.
#2 is going to be the most important for you because it looks like there's a problem with your device drivers or you are missing a necessary initialization file. Following the directions there will get you fixed up.
After doing all that, go back to my previous post.

It works, I got to mount the SD card and everything. Thank You everyone for all of your help!

[Q] hot to get into fastboot mood!!!!

hi guys,,
love your forum....
simple NOOB question plzzzzzzzzzzzzz...
how do i get into fastboot,,,,
i have a kf and installe dthe drivers and every thing but no fastboot no adb nor even the KF tookit can detect my KF.... just cant get it into fastboot mood..

http://forum.xda-developers.com/showthread.php?t=1552547
http://forum.xda-developers.com/showthread.php?t=1668159

thanks for your reply.... i v been reading these to threads for very long time,,,, i just cant get the damn thing into fastboot mood... the KFU tool cant communicate with the device at all
i know im a noob but really need help
thanks

My Kindle is never recognized by KFU . Here's what you need:
Android SDK
Working adb and fastboot
KFU
On windows 7 shift+right click in your KFU tools directory and click "open command window here"
Here are the commands:
adb devices (your device should be listed)
adb shell (make sure it shows up as root, there will be a #, if not su)
idme bootmode 0x4002
reboot
Then your device should be booted into fastboot mode

He could be having the same problem I had, no /system/bin/sh so the adb technique will not work. I had to make a factory cable, which got me into fastboot mode (but ROMS still are not applying right, that question is in another thread).

gdjy said:
i have a kf and installe dthe drivers and every thing but no fastboot no adb nor even the KF tookit can detect my KF.... just cant get it into fastboot mood..
Click to expand...
Click to collapse
This is a shot in the dark, but have you checked that there is a .android directory under your user profile? Does it contain the adb_usb.ini configuration file? For some unknown reason the first time I tried, the install_drivers batch file didn't make the directory, so adb didn't initialize. Windows wouldn't let me make a new folder named .android so I had to go to the command prompt and make the directory myself using the old MS-DOS md command then copy the configuration file.
There is a section in Kindle Fire For Beginners that describes how to verify the drivers are loading. If you haven't seen it, it's worth the read.

SLOmtb said:
This is a shot in the dark, but have you checked that there is a .android directory under your user profile? Does it contain the adb_usb.ini configuration file? For some unknown reason the first time I tried, the install_drivers batch file didn't make the directory, so adb didn't initialize. Windows wouldn't let me make a new folder named .android so I had to go to the command prompt and make the directory myself using the old MS-DOS md command then copy the configuration file.
There is a section in Kindle Fire For Beginners that describes how to verify the drivers are loading. If you haven't seen it, it's worth the read.
Click to expand...
Click to collapse
Thanks for the KFFB plug. Just as an FYI, fastboot doesn't look at the adb_usb.ini file... adb is the only thing that looks at it.
gdjy said:
thanks for your reply.... i v been reading these to threads for very long time,,,, i just cant get the damn thing into fastboot mood... the KFU tool cant communicate with the device at all
i know im a noob but really need help
thanks
Click to expand...
Click to collapse
I just updated my fastboot guide (the second link I gave you) with details on how to get the hardware IDs and identify whether or not you are in fastboot mode. Take a look again and see what your hardware IDs are. If that doesn't help you, post a more detailed description of what you are doing, what the device is doing, what errors you get, etc. The more details you can provide, the easier it will be for your helpers to determine what's happening. Look at the sticky post at the top of this section.

i know this is also a stupid question, but how do i issue the "fastboot oem format" command? i tried partitioning my kf but it failed....

Forgot to transfer ROM

I tried to root my Nexus to get Jellybean...all went well till I realized I forgot to get the ROM onto the phone.
I made a backup onto the computer but didn't do it after I booted into clockwork mod. I wiped the cache etc. and installed the Gapps and that is when I realised the ROM wasn't on the phone. My phone wont connect to the computer and the only backup I have is on my computer.
Is there a way to get the stock ICS on the phone or somehow get the JB ROM onto my phone?

Not an expert, but fastboot and flash stock???
Sent from my Galaxy Nexus using Tapatalk 2

If your phone is recognized by the PC, push the ROM with ADB. You can then flash it.
Code:
adb push rom-file.zip /sdcard/
Alternatively if you just want to return to stock, flash the images via fastboot: http://forum.xda-developers.com/showthread.php?t=1626895

martonikaj said:
If your phone is recognized by the PC, push the ROM with ADB. You can then flash it.
Code:
adb push rom-file.zip /sdcard/
Alternatively if you just want to return to stock, flash the images via fastboot: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Phone is not recognized by the computer. It tries to install the driver then says it can't.

adb push it.
You can adb push from a custom recovery (CWM)

Jubakuba said:
adb push it.
You can adb push from a custom recovery (CWM)
Click to expand...
Click to collapse
I can't find the AndroidSDK folder on my computer at all...
edit-
downloaded and installed Android SDK.
edit-
got to cmd....I get to the point where I need to adb push but I get this message: 'adb' is not recognized as an internal or external command, operable program or batch file.
and on cwm, I can't toggle the /sdcard to unmount. It stays on mount.

cwpmz3 said:
I can't find the AndroidSDK folder on my computer at all...
edit-
downloaded and installed Android SDK.
edit-
got to cmd....I get to the point where I need to adb push but I get this message: 'adb' is not recognized as an internal or external command, operable program or batch file.
and on cwm, I can't toggle the /sdcard to unmount. It stays on mount.
Click to expand...
Click to collapse
You need to be in the sdk folder where the adb.exe is located, and the file you want to push must be in the same folder aswell.
Swype'ed on my CM10 Galaxy Nexus

cwpmz3 said:
I can't find the AndroidSDK folder on my computer at all...
edit-
downloaded and installed Android SDK.
edit-
got to cmd....I get to the point where I need to adb push but I get this message: 'adb' is not recognized as an internal or external command, operable program or batch file.
and on cwm, I can't toggle the /sdcard to unmount. It stays on mount.
Click to expand...
Click to collapse
Open the directory where you put the adb.exe file. Shift+Right Click the blank screen. Click Run Command Prompt Here. Now you should be able to use adb and all its commands when your phone is in recovery mode and connected to computer. Just to make sure, you can always do "adb devices" to check it the phone is recognized.
Also make sure that the ROM you want to transfer is in the same directory as adb.exe.
After you've done that, do "adb push NAME OF THE ROM.zip /sdcard/"
Now use CWM to flash that zip file and you're good to go.

Thanks everyone! Got it working!
Definitely made my heartdrop before haha but man I learned a lot haha again, Thanks!:good:

[Q] TWRP problem

I was just messing around with TWRP trying to flash a new ROM. I forgot to make a backup and wiped the internal storage + system (in other word I wiped everything) I have the files in my computer but I don't know how to access them since the computer can't recognize my device. Any suggestions? :crying:

You need to enter recovery and adb push the files to your sdcard. Open a command window where adb is located
Code:
adb push rom.zip/sdcard/

Thepooch said:
You need to enter recovery and adb push the files to your sdcard. Open a command window where adb is located
Code:
adb push rom.zip/sdcard/
Click to expand...
Click to collapse
Since the device can't be recognized I would try to search for the ADB drivers. This happened to me on my kindle fire hd 7" and the only way I could fix it was by doing "adb sideload filenamehere.zip" after going into Advanced > ADB Sideload.
Hope I could help!

I'm very grateful
thanks

you rock bro
Thepooch said:
You need to enter recovery and adb push the files to your sdcard. Open a command window where adb is located
Code:
adb push rom.zip/sdcard/
Click to expand...
Click to collapse
Im new to this world of tablets and all the commands and prompt, etc... but I thought that I would never solve my problem lol. I'm still a noob but
Thank you for all what you did for my kindle fire hd. I just wanna let people know you helped me unbrick my kindle ( you worked more than 4 hours to be exactly on my kindle) not many people in this forum would do that :good: and thanks to all the developers and mods you nailed it quite well on unbricking my kindle using the programs they have developed.
Editing the drivers so they could work on my machine (I live in El Salvador so my region is a problem when i try to install the drivers) was no easy quest and using teamviewer for letting you work was cool, but the best part is that you installed the cm10.1 by Hash which I had before bricking my device. You saved my kindle bro, thanks A LOT!!!!! I appreciate it. :victory: