Before we start this: I am new to Android, especially FIRE OS, and really need some help. Also, this is refering to a Amazon Kindle Fire 7" 2nd Generation.
Lets start from the beginning. I decided to root my kindle, and I installed Google Play Services on it. I then updated, and decided to wipe the services (It was causing some problems) and reinstall it. Because "vending.app" is the main files that runs the services (I thought), I found a "Vending" folder under /SYS in the file directory. Me being an idiot, I deleted it, and it froze my kindle, I forced a restart, but then all I got was the Blue "Kindle Fire" screen. It would show the logo, crash, then restart again, basically a boot-loop. I did some research, and decided to fastboot my kindle, wipe it clean, and install a recovery. I bought a FACTORY CABLE, and successfully fast-booted my device. I then installed a portion of (what I think) is the Android Developer thing-a-ma-bob that contains the ABD and fastboot files. The thing is, I have my fastbooted kindle connected to the computer via USB, but ADB AND FASTBOOT DOES NOT RECOGNIZE IT. All its says is "<waiting for device>". Does this have something to do with the "Vending" File I deleted, or is it a computer problem.
PS: I have a MAC, and(I don't think) requires drivers, so drivers is not the cause. I also cannot use any 3rd party recovery softwares due to not being able to run .bat and .exe
THINGS I HAVE TRIED:
-Switching to the normal Kindle Charger (USB)
-Hard Starting the Kindle
-Trying to boot into recover w/ VOLUME UP (Does not Work)
-Changing USB Ports
Any Help Will Be Appreciated, Thanks!
utskids said:
Before we start this: I am new to Android, especially FIRE OS, and really need some help. Also, this is refering to a Amazon Kindle Fire 7" 2nd Generation.
Lets start from the beginning. I decided to root my kindle, and I installed Google Play Services on it. I then updated, and decided to wipe the services (It was causing some problems) and reinstall it. Because "vending.app" is the main files that runs the services (I thought), I found a "Vending" folder under /SYS in the file directory. Me being an idiot, I deleted it, and it froze my kindle, I forced a restart, but then all I got was the Blue "Kindle Fire" screen. It would show the logo, crash, then restart again, basically a boot-loop. I did some research, and decided to fastboot my kindle, wipe it clean, and install a recovery. I bought a FACTORY CABLE, and successfully fast-booted my device. I then installed a portion of (what I think) is the Android Developer thing-a-ma-bob that contains the ABD and fastboot files. The thing is, I have my fastbooted kindle connected to the computer via USB, but ADB AND FASTBOOT DOES NOT RECOGNIZE IT. All its says is "<waiting for device>". Does this have something to do with the "Vending" File I deleted, or is it a computer problem.
PS: I have a MAC, and(I don't think) requires drivers, so drivers is not the cause. I also cannot use any 3rd party recovery softwares due to not being able to run .bat and .exe
THINGS I HAVE TRIED:
-Switching to the normal Kindle Charger (USB)
-Hard Starting the Kindle
-Trying to boot into recover w/ VOLUME UP (Does not Work)
-Changing USB Ports
Any Help Will Be Appreciated, Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=37472472
[BOOTLOADER] 2nd-bootloader for Custom ROMs on KFireHD 7" [06/24 CM12.1/TWRP 2.8.7.0]
Sent from my XT894 using Tapatalk
sd_shadow said:
http://forum.xda-developers.com/showthread.php?p=37472472
[BOOTLOADER] 2nd-bootloader for Custom ROMs on KFireHD 7" [06/24 CM12.1/TWRP 2.8.7.0]
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
That is the problem. That is what I want to install, but can't because I can't access fastboot.
utskids said:
That is the problem. That is what I want to install, but can't because I can't access fastboot.
Click to expand...
Click to collapse
http://www.jayceooi.com/how-to-install-kindle-fire-adb-usb-driver/
You have used the preferred driver from here Kindle_Fire_HD_ADB_Drivers.zip
What is your windows version?
---------- Post added at 06:48 PM ---------- Previous post was at 06:47 PM ----------
right you have a Mac
---------- Post added at 06:50 PM ---------- Previous post was at 06:48 PM ----------
do you have access to a windows pc?
---------- Post added at 07:19 PM ---------- Previous post was at 06:50 PM ----------
Or another android device?
Most android devices have a fastboot mode, but don't use the fastboot cable unless you are sure it's compatible.
Sent from my XT907 using Tapatalk
sd_shadow said:
http://www.jayceooi.com/how-to-install-kindle-fire-adb-usb-driver/
You have used the preferred driver from here Kindle_Fire_HD_ADB_Drivers.zip
What is your windows version?
---------- Post added at 06:48 PM ---------- Previous post was at 06:47 PM ----------
right you have a Mac
---------- Post added at 06:50 PM ---------- Previous post was at 06:48 PM ----------
do you have access to a windows pc?
---------- Post added at 07:19 PM ---------- Previous post was at 06:50 PM ----------
Or another android device?
Most android devices have a fastboot mode, but don't use the fastboot cable unless you are sure it's compatible.
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
I can get access to a windows, but it will be a hassle. As for the android question, no, the kindle is my only Android-Based device. I'm pretty sure the factory cable is capable. The fastboot logo appears when I plug it in on my kindle fire.
I still can't figure this out.....can anyone else help me?
have you tried windows or any other computer apart from that mac?
also, you use fastboot cable to just boot fastboot, nothing else, once in fastboot, switch to a normal cable, from what I read.
bangdosa said:
have you tried windows or any other computer apart from that mac?
also, you use fastboot cable to just boot fastboot, nothing else, once in fastboot, switch to a normal cable, from what I read.
Click to expand...
Click to collapse
I have switched chord, but have not tried it on a different computer. That will probably be my next step, and I will tell you how it goes...
Related
Hello!
I'd appreciate it if anybody could make a backup image of his KFHD and post it here. Pls make a backup after 2nd part of rooting, as it said http://forum.xda-developers.com/showthread.php?t=1930656
Thx in advance!
Yes please .... you will help a lot of depressed users
This evening I'm going to set everything back to stock(except for su binary) on my system partition and will post it here when I finish. You will need a factory cable to enable fastboot
Sent from my SCH-I500 using xda app-developers app
In case you have tried downloading these files and were not able to, I have changed the links below(the others were disabled by dropbox for too much traffic). You must now unzip these files before use!!
Here are copies of backups I created from KFHD(Don't think this will work with KF2).
WARNING!!!- use at your own risk, I am not responsible for anything you do to your device. If you do not know what these .img files are for you should not be using them. See- http://forum.xda-developers.com/showthread.php?t=1930656 for directions on restoring with fastboot
System.img-(with su binary, vending.apk, and latest versions of go-launcher ex and apex launcher. Note: you will still need superuser.apk to obtain root and googleservicesframework.apk to access play store) These new links have zipped files, you MUST unzip before using :
https://docs.google.com/open?id=0B4lZEJI5lYeMR2k3NW1QRUR3dzg
System.img-(with su binary only. Note: same as above plus vending.apk), Also this file is named [system(2)] you may want to rename to [system] These new links have zipped files, you MUST unzip before using :
https://docs.google.com/open?id=0B4lZEJI5lYeMcldVWUwzd3BqRUE
I just noticed on Play that go-launcher ex has been updated so the above image does not have latest go-launcher ex, but will still work, just update in Play store
I messed up my kindle and now i have to restore a backup, do I have to have one of these cables that is mentioned? because in my country there is no kfhd much less these cables? please help this kfhd of mine has been giving me hard time since I got it.
You are the hero. Thank you.
hamidwt said:
I messed up my kindle and now i have to restore a backup, do I have to have one of these cables that is mentioned? because in my country there is no kfhd much less these cables? please help this kfhd of mine has been giving me hard time since I got it.
Click to expand...
Click to collapse
Yes you must have a factory cable to enable fastboot(unless you still have the ability to download and open an app with root access). Check out this link- http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9. They say they ship international and pricing is extremely cheap with what looks to be good quality. Personally I made mine, It is pretty simple if you have a spare micro usb cable, a 1k resistor, and a soldering iron. Just google factory cable kindle fire. Be very careful it might be simple but there is the potential to ruin your device and fry the usb board on your computer(at the minimum) if not done correctly. I do not say this lightly be absolutely sure of everything you are doing before attempting.
Works like a dream
Thanks for the image! I used it revive my dead kindle and it works!
Only thing right now is that my Date and time settings seems to have greyed out. I will need to figure this out as the date and time is wrong.
Also, i didn't use a factory cable - I had an issue with a blank screen appearing after the words Kindle Fire upon start up. So I got into fastboot by using the ADB: Fastboot reboot-bootloader
Cheers1
onemeila said:
Sorry this took so long just wanted to make sure I had the files straight and they worked
Here are copies of backups I created from KFHD(Don't think this will work with KF2).
WARNING!!!- use at your own risk, I am not responsible for anything you do to your device. If you do not know what these .img files are for you should not be using them. See- http://forum.xda-developers.com/showthread.php?t=1930656 for directions on restoring with fastboot
System.img-(with su binary, vending.apk, and latest versions of go-launcher ex and apex launcher. Note: you will still need superuser.apk to obtain root and googleservicesframework.apk to access play store) :
https://www.dropbox.com/s/y90vk1igk0ml5qv/system.img
System.img-(with su binary only. Note: same as above plus vending.apk), Also this file is named [system(2)] you may want to rename to [system] :
https://www.dropbox.com/s/t5rarzakk9p1to5/system (2).img
I just noticed on Play that go-launcher ex has been updated so the above image does not have latest go-launcher ex, but will still work, just update in Play store
Click to expand...
Click to collapse
onemeila said:
Yes you must have a factory cable to enable fastboot(unless you still have the ability to download and open an app with root access). Check out this link- http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9. They say they ship international and pricing is extremely cheap with what looks to be good quality. Personally I made mine, It is pretty simple if you have a spare micro usb cable, a 1k resistor, and a soldering iron. Just google factory cable kindle fire. Be very careful it might be simple but there is the potential to ruin your device and fry the usb board on your computer(at the minimum) if not done correctly. I do not say this lightly be absolutely sure of everything you are doing before attempting.
Click to expand...
Click to collapse
thank you for your help
my kindle is working , I download and install easily but I have problem with Google play and also logging into Imo and I'm+ , I did some factory reset but still nothing ,that got me thinking there must be something wrong with system. so considering what I said , do I still need this cable?
hamidwt said:
thank you for your help
my kindle is working , I download and install easily but I have problem with Google play and also logging into Imo and I'm+ , I did some factory reset but still nothing ,that got me thinking there must be something wrong with system. so considering what I said , do I still need this cable?
Click to expand...
Click to collapse
No you wouldn't need a factory cable but if the device is still working then the best thing would be to figure what mods you made to the system and reverse them before flashing an image in fastboot. If you cant figure that out and need to flash the system.img, the post above said they were able to get into fastboot through cmd window(though I think because the device was frozen, I was not able to do this with my working device, then again i could be doing something wrong). I know that if you use the app- Rom Toolbox Lite and under the rebooter section there is an option to reboot bootloader, that will boot into fastboot. Then you can use a regular cable.
---------- Post added at 11:37 AM ---------- Previous post was at 11:31 AM ----------
Arithon said:
Thanks for the image! I used it revive my dead kindle and it works!
Only thing right now is that my Date and time settings seems to have greyed out. I will need to figure this out as the date and time is wrong.
Also, i didn't use a factory cable - I had an issue with a blank screen appearing after the words Kindle Fire upon start up. So I got into fastboot by using the ADB: Fastboot reboot-bootloader
Cheers1
Click to expand...
Click to collapse
Glad it helped. With the date and time mine are grayed out as well(think its like that from factory, don't remember noticing since date and time were changed during initial setup), you just need to select the right time zone and it automatically changes to proper time.
Also are you still able to get into fastboot via cmd prompt now that your device is working properly? If so what commands did you use?
cmd
onemeila said:
No you wouldn't need a factory cable but if the device is still working then the best thing would be to figure what mods you made to the system and reverse them before flashing an image in fastboot. If you cant figure that out and need to flash the system.img, the post above said they were able to get into fastboot through cmd window(though I think because the device was frozen, I was not able to do this with my working device, then again i could be doing something wrong). I know that if you use the app- Rom Toolbox Lite and under the rebooter section there is an option to reboot bootloader, that will boot into fastboot. Then you can use a regular cable.
---------- Post added at 11:37 AM ---------- Previous post was at 11:31 AM ----------
Glad it helped. With the date and time mine are grayed out as well(think its like that from factory, don't remember noticing since date and time were changed during initial setup), you just need to select the right time zone and it automatically changes to proper time.
Also are you still able to get into fastboot via cmd prompt now that your device is working properly? If so what commands did you use?
Click to expand...
Click to collapse
fastboot reboot-bootloader
---------- Post added at 02:23 AM ---------- Previous post was at 01:58 AM ----------
Arithon said:
fastboot reboot-bootloader
Click to expand...
Click to collapse
sorry it was "adb reboot-bootloader"
Arithon said:
fastboot reboot-bootloader
---------- Post added at 02:23 AM ---------- Previous post was at 01:58 AM ----------
sorry it was "adb reboot-bootloader"
Click to expand...
Click to collapse
Are you still able to do this with the device working? I couldn't.
adb
onemeila said:
Are you still able to do this with the device working? I couldn't.
Click to expand...
Click to collapse
Yes - but i think you must turn it (ADB) on in 'Settings'....
Another Beg!
I am adding a BEG!!!
Anyone have a system.img file for the 10.2.1 Kindle Fire 2 device?
Please..
I did a backup when I was on 10.1.3 and it wont let me restore that system..img file!!!!!!!
I get this error!
fastboot -i 0x1949 flash system system.img
sending 'system' (907264 KB)...
FAILED (remote: data too large)
finished. total time: 0.188s
[edit:] nevermind
Thanks the image files has saved my Kindle Fire HD!
I know this is a system.img but I really need a boot.img for the fire hd 7" can someone please post one it would be greatly appreciated thanks
dark_samus said:
I know this is a system.img but I really need a boot.img for the fire hd 7" can someone please post one it would be greatly appreciated thanks
Click to expand...
Click to collapse
Look here:
http://forum.xda-developers.com/showthread.php?t=1951254
mm
brandon_scott said:
Hello, I have used this site to solve many problems but I could not find an answer to my current predicament anywhere on the site so I made an account. I was on twrp and I accidentally wiped the os completely off my phone. I tried to run the ruu but because my phone is 1.31 and that version isn't out yet I wasn't able to do it. I know turn the s-on to s-off but I can't. I used both revone and moonshine neither worked. I can no longer access twrp only the normal recovery. When I hook my phone up to my computer it says fastboot usb but for some reason the adb can't find the device in cmd when I type in adb shell and when I try adb devices nothing comes up. I have uninstalled and reinstalled drivers. I have taken off htc sync manager. When I look at all the drivers and devices on my computer I do see the phone and everything seems fine on that end. I can not sideload anything either. If I could just get my device recognized or turn off s-on I could fix it. I locked the bootloader to run the ruu but since that wasn't working now I decided to unlock the bootloader again hoping maybe I could just use cmd to fix it. Are there any commands I could use to turn s-off? Or maybe flashing a specific software. Once again my problem is that I idiotically deleted my os off my htc one. Now when I turn my phone on it just goes to the splash screen and then if I hold the power and volume down it turns off and when I turn it back on while holding the volume down it takes me to the bootloader where I can set it to fastboot usb but that's it. Are there maybe any ways I could control the phone using only my computer. Im stuck in what I believe to be a softbrick and I have tried every way I found online on youtube and xda and every thing else that I found on google and bing. I have spent 10 hours trying every method I could find and still nothing.
Click to expand...
Click to collapse
you have to flash a custom recovery (twrp/cwm) so you can be able to sideload a rom and install it.
Rename the attached recovery to recovery.img and place it in your adb folder then put your phone into fastboot mode and run this command
fastboot flash recovery recovery.img
Then use the all-in-one toolkit to sideload your Rom
Twrp for HTC One
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.0-m7.img
Toolkit
http://forum.xda-developers.com/showthread.php?t=2364445
Hope this helps
---------- Post added at 04:22 PM ---------- Previous post was at 04:08 PM ----------
Also , never try to s-on a modified h-boot as you could brick your device
Sent from my HTC One using xda app-developers app
.
craigmoly said:
Rename the attached recovery to recovery.img and place it in your adb folder then put your phone into fastboot mode and run this command
fastboot flash recovery recovery.img
Then use the all-in-one toolkit to sideload your Rom
Twrp for HTC One
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.0-m7.img
Toolkit
http://forum.xda-developers.com/showthread.php?t=2364445
Hope this helps
---------- Post added at 04:22 PM ---------- Previous post was at 04:08 PM ----------
Also , never try to s-on a modified h-boot as you could brick your device
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I tried to flash the recovery and it didn't work it might have to do with the adb not being able to find my phone. Fastboot devices shows my phone but adb devices shows nothing and adb shell says device not found. Ive updated drivers and that doesn't work. mtp driver won't install correctly for what ever reason. That toolkit won't work everything on there does nothing except for the basic fastboot controls.
Adb will only see your phone when it's on and booted , fastboot sees your device when in bootloader/fastboot
Sent from my HTC One using xda app-developers app
---------- Post added at 07:31 PM ---------- Previous post was at 07:20 PM ----------
Try this thread http://forum.xda-developers.com/showthread.php?t=2325853
Sent from my HTC One using xda app-developers app
---------- Post added at 07:35 PM ---------- Previous post was at 07:31 PM ----------
Might be a daft question but are you sure you've placed the recovery in the right folder , you want it in the folder with adb.exe and fastboot.exe and rename it to recovery.img
Have u tried using the toolkit , use it to flash the Twrp recovery that is in the list then sideload https://www.dropbox.com/sh/9wxc0gm0j7emp15/xnwTSxfg6n
Sent from my HTC One using xda app-developers app
I'm new to this forum, so bear with me if I have created this in the wrong area.
I'm trying to un-brick a (I think 1st gen.) Kindle Fire HD with a Fastboot cable on a Mac.
All it does is stay at the KindleFire boot screen. At first I thought it was the battery so I replaced it but that didn't do the trick.
So, I got the fast boot cable and now I feel that I am lost within a sea of different methods and tool kits to try and get the device restored to factory settings.
I've gone through the process of downloading the Android SDK so I can get fastboot and adb.
When I connect the Kindle Fire to the fastboost USB to my Mac, it will go to the fastboot screen.
When I run
Code:
adb devices
it doesn't show that anything is connected.
However, if I run
Code:
fastboot -i 0x1949 getvar product
it appears that it's connected via fastboot:
Code:
product: Tate-PVT-08
finished. total time: 0.000s
But I'm kinda lost after that. Seems like most of the guides out have a slew of different options and boot loaders and I'm not sure which one will get back to the default factory settings. Most of what I've seen is that you need to enable ADB on the device, but since I can't boot into the device, I'm not too sure what I need to do to get it to reset.
I've read through this post: http://forum.xda-developers.com/showthread.php?t=1399889
but it says that it cannot recognize the device when I attempt to do this on Windows. And when I launch the device manager, it shows that it is connected as Kindle Fire as Android ADB Interface.
Kindle fire first gen and kindle fire HD are 2 different devices
From your fastboot devices reply looks like you have an HD, so do not use anything created for first gen.
Sent from my XT907 using Tapatalk
---------- Post added at 02:10 PM ---------- Previous post was at 02:07 PM ----------
Fastboot commands only work in fastboot mode.
ADB commands only work in recovery and rom
Sent from my XT907 using Tapatalk
---------- Post added at 02:21 PM ---------- Previous post was at 02:10 PM ----------
Fastboot commands seem to be working fine so should just need to flash a bootloader and recovery.
see [REF]All Things About Kindle Fire HD 7"
Crap.
Well, I think that I may have bricked it forever. Didn't realize the difference between 1st and 2nd gen. devices.
Damn.
If fastboot is working, its not bricked
Sent from my XT907 using Tapatalk
You can use these images to unbrick your Kindle.
http://forum.xda-developers.com/showthread.php?t=1951254
Hy everyone.
I have kindle fire HD 7" ( 1 gen if i remember right). It is successfully rooted, and has CM 12.1. Being not able to install "Google Play Game" app, i read that the solution can be to reset factory settings. And i did it. So what i have now: it's loading with yellow label, than with blue. Than it show Teamwin logo, and going looping (logo periodically redrawing).
The system have sound that some device is connecting, but i can't find it in Device Manager. Adb devices says that there no device.
What should i do now ?
kseon12 said:
Hy everyone.
I have kindle fire HD 7" ( 1 gen if i remember right). It is successfully rooted, and has CM 12.1. Being not able to install "Google Play Game" app, i read that the solution can be to reset factory settings. And i did it. So what i have now: it's loading with yellow label, than with blue. Than it show Teamwin logo, and going looping (logo periodically redrawing).
The system have sound that some device is connecting, but i can't find it in Device Manager. Adb devices says that there no device.
What should i do now ?
Click to expand...
Click to collapse
I manage to resurrect my Kindle. So what i did:
- I loaded to fastboot, using handmade factory cable (actually i just closed first and fife pins);
- Then i switched to normal USB cable;
- Since PC didn't recognize device by default, i went to Device Manager and set "ADB fastboot driver ... " to my unknown device;
- I find new version of TWRP and flashed it using fastboot.
After that, it rebooted, tried to access to TWRP, installed some script and rebooted again. After that i have only CM12 logo. So, i rebooted to recovery, and successfully entered there. And it even automatically mount it as storage to PC. But i have cm12 already there, so i flashed it with Gapps and everything are working perfectly.
Hope this will help someone.
P.S.
I even managed to install Google Play Game app. It didn't install through Play market again. I just download official apk somewhere else, and install it through file manager. And its working now
Hi..
I have exactly the very same problem....
(see http://forum.xda-developers.com/kin...lp/kf-hd-7-tate-recovery-loop-cm12-1-t3138998)
TWRP loop after CM12.1 factory reset.
I tried the same things. Today I received my fastboot cable. I just tried to flash TWRP 2.7.0.0 from CM. But this results in the very same TWRP loop. Which TWRP version did you flash?
Where did you get it from?
Thanks!
---------- Post added at 11:32 PM ---------- Previous post was at 11:15 PM ----------
Ok...
I am one step further now.
I did a
Code:
fastboot -i 0x1949 -w
to format userdata and cache. Now it boots into my TWRP 2.7.0.0.
Lets see how far I come now....
Real_Rosch said:
Hi..
I have exactly the very same problem....
(see http://forum.xda-developers.com/kin...lp/kf-hd-7-tate-recovery-loop-cm12-1-t3138998)
TWRP loop after CM12.1 factory reset.
I tried the same things. Today I received my fastboot cable. I just tried to flash TWRP 2.7.0.0 from CM. But this results in the very same TWRP loop. Which TWRP version did you flash?
Where did you get it from?
Thanks!
---------- Post added at 11:32 PM ---------- Previous post was at 11:15 PM ----------
Ok...
I am one step further now.
I did a
Code:
fastboot -i 0x1949 -w
to format userdata and cache. Now it boots into my TWRP 2.7.0.0.
Lets see how far I come now....
Click to expand...
Click to collapse
got the same issue like you but when i type in that command, it stays on waiting for device. at it just get stuck there.
I'm using the cable i received with my kindle. can you kindly post a screenshot of your device manager to see if the adb driver i installed is the same you used?
many thanks man!
Po5tHuMaN said:
got the same issue like you but when i type in that command, it stays on waiting for device. at it just get stuck there.
I'm using the cable i received with my kindle. can you kindly post a screenshot of your device manager to see if the adb driver i installed is the same you used?
many thanks man!
Click to expand...
Click to collapse
You need a fastboot cable to do this. It is not working with a regular USB cable!
When plugin in this cable your device should switch to "fastboot" mode...
It can be seen with a orange "fastboot" label on the screen.
BTW:
In the meantime i flashed TWRP 2.8.7.0 from hashcode here in the forum. Then I reinstalled CM 12.1 and I am now back in business for some days now...
Oh yes tablet is back wohoooooooo thanks man!
An app in google play store wasn't installing correctly and I was told a factory reset would fix my issue but now when the Kindle HD reboots it stays on the blue screen teamwin logo and keeps looping. How do I solve this ?
p.s my fastbooy cable is coming tomorrow but not sure what to do with it
did you manage to sort this im in the exact same position. factory reset within a custom rom! in windows its recognised in adb but not authorised and cant get it to recognise whilst in fastboot
KindleFireHD7" said:
did you manage to sort this im in the exact same position. factory reset within a custom rom! in windows its recognised in adb but not authorised and cant get it to recognise whilst in fastboot
Click to expand...
Click to collapse
Yeah I got it up and running again NO help to this site ... anyways
First I bought this Fastboot cable
www.amazon.com
Second install these Drivers:
http://forum.xda-developers.com/attachment.php?attachmentid=1337103&d=1348009415
Third install 2nd set of drivers if you need them/Used this tool to restore the kindle
https://drive.google.com/file/d/0B14UeDuAgQxRSjdzNGFDMzVRcms/view?usp=sharing
option 2 if that one didn't work or if you want to restore with root access
http://androidcowboy.com/2013/07/how-to-recover-bricked-kindle-fire-hd/
meowmix2 said:
Yeah I got it up and running again NO help to this site ... anyways
First I bought this Fastboot cable
www.amazon.com
Second install these Drivers:
http://forum.xda-developers.com/attachment.php?attachmentid=1337103&d=1348009415
Third install 2nd set of drivers/Used this tool to restore the kindle
https://drive.google.com/file/d/0B14UeDuAgQxRSjdzNGFDMzVRcms/view?usp=sharing
option 2 if that one didn't work or if you want to restore with root access
http://androidcowboy.com/2013/07/how-to-recover-bricked-kindle-fire-hd/
Click to expand...
Click to collapse
Will give this a go later on , I have fastboot cable just having serious trouble trying to pc to recognize it whilst in fast boot mode. It recognizes it in adb but it's unauthorized so that's no help. Thanks for reply will let you know how I get on
---------- Post added at 10:50 PM ---------- Previous post was at 10:40 PM ----------
meowmix2 said:
Yeah I got it up and running again NO help to this site ... anyways
First I bought this Fastboot cable
www.amazon.com
Second install these Drivers:
http://forum.xda-developers.com/attachment.php?attachmentid=1337103&d=1348009415
Third install 2nd set of drivers if you need them/Used this tool to restore the kindle
https://drive.google.com/file/d/0B14UeDuAgQxRSjdzNGFDMzVRcms/view?usp=sharing
option 2 if that one didn't work or if you want to restore with root access
http://androidcowboy.com/2013/07/how-to-recover-bricked-kindle-fire-hd/
Click to expand...
Click to collapse
its failing to install the first set of drivers any suggestions?? thanks
KindleFireHD7" said:
Will give this a go later on , I have fastboot cable just having serious trouble trying to pc to recognize it whilst in fast boot mode. It recognizes it in adb but it's unauthorized so that's no help. Thanks for reply will let you know how I get on
---------- Post added at 10:50 PM ---------- Previous post was at 10:40 PM ----------
its failing to install the first set of drivers any suggestions?? thanks
Click to expand...
Click to collapse
continue to second set maybe the first set of drivers is what worked for me maybe you don't need them . I'll try to find the source where i found them maybe you need a different set that was provided
update* ok heres the source of the ADB drives that finally worked for me
http://forum.xda-developers.com/showthread.php?t=1893838
Your goal is for the unbrick tool to detect your device. so find right combination of drives that work for you. some people even go to thier driver manager and uninstall / refresh them from there. If it still not working try uninstalling all previous drives and do a clean install with the two i gave you
Fix...
meowmix2 said:
An app in google play store wasn't installing correctly and I was told a factory reset would fix my issue but now when the Kindle HD reboots it stays on the blue screen teamwin logo and keeps looping. How do I solve this ?
p.s my fastbooy cable is coming tomorrow but not sure what to do with it
Click to expand...
Click to collapse
Hello,
Fortunately, i was in the same position as you and that too, for a whole year and 3 months. But I was a noob at that time. With your fastboot cable to be usable(no drivers needed but just a simple program), you need to get (Minimal ADB and Fastboot. The link is provided for download. Now you need to do some research. For me I found out that the main problem was that it was a TWRP problem and nothing else. So I am guessing you ahve the exact same. You need to go to CyanogenMod Wiki(discountinued so you'll have to wait until Lineage OS gets their Wiki up and then figure it out) and from there find your device and then the installation instructions whihc include the downlaod link for TWRP. From there download the recovery(it will link you to android file host or something like that). Now you can install Minimal Adb and Fastboot(MAF) and install it wherever convenient to you. Now you can place the zip file of recovery in the folder where MAF is installed and rename it to recovery.zip for your convenience. In that folder, open the exe that says "MAFAF" or something to that extent(dont' have it memorized lol). Now connect your fastboot cable to your Kindle and it should turn on with a screen on the kindle that says Fastboot and then Kindle. Now on your MAF, you cna check it's working by typing
Code:
fastboot devices
or
Code:
adb devices
. In theory, you should get something like " recovery (device number[random letters and numbers])". From this you can now type in
Code:
fastboot flash recovery recovery.zip
as done to flash our TWRP recovery. When this finishes(shouldn't take to long), you can detach the fastboot form the computer and device. Next, hodl down power to turn it off. Wait like 5 seconds after shut down and then turn the Kindle back on. This should momentarily boot into TWRP and then it will take off into your ROM or whatever OS you have installed. Now you should have not jsut fixed your problem but got TWRP to work too and from there it is easy to do stuff without the need of a PC. Hope this helps and feel free to quote me with a post if something didn't work or messed up. Sorry for bad grammer and spelling. Thanks!
meowmix2 said:
continue to second set maybe the first set of drivers is what worked for me maybe you don't need them . I'll try to find the source where i found them maybe you need a different set that was provided
update* ok heres the source of the ADB drives that finally worked for me
http://forum.xda-developers.com/showthread.php?t=1893838
Your goal is for the unbrick tool to detect your device. so find right combination of drives that work for you. some people even go to thier driver manager and uninstall / refresh them from there. If it still not working try uninstalling all previous drives and do a clean install with the two i gave you
Click to expand...
Click to collapse
Sorted thank you!