Hey,
I recently bought me a Kindle Fire HD, assuming that rooting and custom roms are no problem.
But I can't even root my device. I tried to use this file but the batch just stucks.
When I try to find my device in console via "adb devices" it's not listet. But I have adb drivers installed.
Any suggestions? I'm really clueless.
schwixxer said:
Hey,
I recently bought me a Kindle Fire HD, assuming that rooting and custom roms are no problem.
But I can't even root my device. I tried to use this file but the batch just stucks.
When I try to find my device in console via "adb devices" it's not listet. But I have adb drivers installed.
Any suggestions? I'm really clueless.
Click to expand...
Click to collapse
so it shows up as a adb device in the device manager?
No, it doesn't. I guess thats why the batch won't work. I just dont understand why the adb driver doesn't work.
Gesendet von meinem MK16i mit Tapatalk 2
But you've ADB enabled in System Settings?
BTW - rooting ist the only thin you can do with Fire HD 7 (2013) there are no Customs in Moment.
Regards
Yeah, i read that far already. Rooting is fine for the moment to remove the amazon ads and to install play. Customs will come earlier or later
Adb is activated on my Kindle
Gesendet von meinem MK16i mit Tapatalk 2
schwixxer said:
Yeah, i read that far already. Rooting is fine for the moment to remove the amazon ads and to install play. Customs will come earlier or later
Adb is activated on my Kindle
Gesendet von meinem MK16i mit Tapatalk 2
Click to expand...
Click to collapse
You know that you have to use a Factory Cable? For Rooting 11.3.2.1 you've to Downgrade bootloader (the script is dealing with that automaticaly) but you have to be in fastboot mode, and fastboot mod is only possible with a factory cable (as far as I know)
BTW "adb devices" doesn't show me my device either.
Regards
dvb127 said:
You know that you have to use a Factory Cable? For Rooting 11.3.2.1 you've to Downgrade bootloader (the script is dealing with that automaticaly) but you have to be in fastboot mode, and fastboot mod is only possible with a factory cable (as far as I know)
BTW "adb devices" doesn't show me my device either.
Regards
Click to expand...
Click to collapse
I've read that "factory cable" before, I just thought that it refers to the cable that came with the kindle. Is that wrong? Where do I get a factory cable?
schwixxer said:
I've read that "factory cable" before, I just thought that it refers to the cable that came with the kindle. Is that wrong? Where do I get a factory cable?
Click to expand...
Click to collapse
I built one myself. if you ask Google for a factory cable Motorola then you'll find a very good how to . I don't know where to buy.
regards
Its better to call it a fastboot cable, I think factory cable is misleading unless you look it up.
Sent from my Amazon Kindle Fire HD using Tapatalk
Okay, solderd a Factory cable and now I'm able to access fastboot mode.
But the batch still stucks here:
//Edit1:
Okay, Windows reconized the Kindle as "soho pvt prod 07". Had to update driver manually in order to work.
Now im stuck here: nothing seems to happen anymore. Why?
//Edit2:
Seems to have a brick. Kindle won't boot anymore. I can still access fastboot mode but kindle wont show up in adb devices, so i cant flash the other boot img. Help?
//Edit3:
Okay, was able to flash the new image without having kindle in the adb devices list. This brings me back to Edit1: Why does the batch stop?
schwixxer said:
Okay, solderd a Factory cable and now I'm able to access fastboot mode.
But the batch still stucks here:
//Edit:
Okay, Windows reconized the Kindle as "soho pvt prod 07". Had to update driver manually in order to work.
Now im stuck here: nothing seems to happen anymore. Why?
Click to expand...
Click to collapse
Power Off your Kindle, then connect your "fastboot cable" --> then your Kindle should power on autom. and show a screen like attached, if not you've problem with your cable. If it shows the screen then there is a Problem with fastboot driver.
dvb127 said:
Power Off your Kindle, then connect your "fastboot cable" --> then your Kindle should power on autom. and show a screen like attached, if not you've problem with your cable. If it shows the screen then there is a Problem with fastboot driver.
Click to expand...
Click to collapse
Well, it works to this point. I have the fastboot logo on my kindle. The batch flahes the boot image. And then everything stops.
Edit:
Okay, the Problem seems to be, that after the downgrade the kindle does not show up as adb device anymore. It works fine with the new image though.
Is that a driver related problem? Do I need a different driver for the old boot image?
Edit2:
Just noticed that the Kindle never shows up under "adb devices" when in fastboot mode. It dows work when I boot the Kindle normal though.
So the batch stucks naturally an "adb wait-for-device"
schwixxer said:
Well, it works to this point. I have the fastboot logo on my kindle. The batch flahes the boot image. And then everything stops.
Edit:
Okay, the Problem seems to be, that after the downgrade the kindle does not show up as adb device anymore. It works fine with the new image though.
Is that a driver related problem? Do I need a different driver for the old boot image?
Click to expand...
Click to collapse
How long did you wait? It'll take a few minutes. When your Kindle is powered on do you've an "adb" connection?
dvb127 said:
How long did you wait? It'll take a few minutes. When your Kindle is powered on do you've an "adb" connection?
Click to expand...
Click to collapse
I waited a few minutes. I also tried to do it manually. I typed:
Code:
fastboot -i 0x1949 flash boot old-boot-prod.img
On my kindle then appears "Start downloading", "writing boot.....done"
Code:
fastboot -i 0x1949 continue
I hear now the usb-disconnect and afterwards the connect sound of windows, no change on my kindle
Code:
adb wait-for-device
and then I can wait forever. Nothing happens here. Only thing I can do is ctrl+c.
Ok. I tried again with my notebook (still running WinXp) and... it worked. On the second try.
Device is rooted now, annoying ads are gone. Thank god.
Why this did not work under Win7....I have no idea.
Last quastion: How to get GooglePlay now? And i read that I can't use the Amazon store anymore, will I need it for some Apps?
schwixxer said:
Ok. I tried again with my notebook (still running WinXp) and... it worked. On the second try.
Device is rooted now, annoying ads are gone. Thank god.
Why this did not work under Win7....I have no idea.
Last quastion: How to get GooglePlay now? And i read that I can't use the Amazon store anymore, will I need it for some Apps?
Click to expand...
Click to collapse
In the post you downloaded your root Script you'll find a link in Signature of the Poster to his playstore Script (To Root your KFSOWI and install working Google Play Click Here)
And yes if playstore ist installed Amazon Downloads are not possible anymore, but you can save all files named “DownloadProvider***.apk/odex“ out of /system/apps before using Playstore Script. You'll find such files also in playstore Script. Than you can always change files. Take the files out of org. Firmware to Download from Amazon and reverse to Download Form google.
dvb127 said:
In the post you downloaded your root Script you'll find a link in Signature of the Poster to his playstore Script (To Root your KFSOWI and install working Google Play Click Here)
And yes if playstore ist installed Amazon Downloads are not possible anymore, but you can save all files named “DownloadProvider***.apk/odex“ out of /system/apps before using Playstore Script. You'll find such files also in playstore Script. Than you can always change files. Take the files out of org. Firmware to Download from Amazon and reverse to Download Form google.
Click to expand...
Click to collapse
Are there special app's that I might need the amazon-appstore for later?
Also, is there a way to change the lockout-screen? Im glad that the ad's are gone now, but just black is boring, too.
schwixxer said:
Are there special app's that I might need the amazon-appstore for later?
Also, is there a way to change the lockout-screen? Im glad that the ad's are gone now, but just black is boring, too.
Click to expand...
Click to collapse
Waht I know ist that only need DownloadProvider** Files (*. odex and *.apk). I don't know how to change the lockscreen, but I think you mean that there is no possibitly to set a wallpaper --> than look at here.
schwixxer said:
Okay, solderd a Factory cable and now I'm able to access fastboot mode.
But the batch still stucks here:
//Edit1:
Okay, Windows reconized the Kindle as "soho pvt prod 07". Had to update driver manually in order to work.
Now im stuck here: nothing seems to happen anymore. Why?
//Edit2:
Seems to have a brick. Kindle won't boot anymore. I can still access fastboot mode but kindle wont show up in adb devices, so i cant flash the other boot img. Help?
//Edit3:
Okay, was able to flash the new image without having kindle in the adb devices list. This brings me back to Edit1: Why does the batch stop?
Click to expand...
Click to collapse
Congrats on rooting your Soho! I'm having similar problems that you did initially. The device is recognized in adb. I bought a fastboot cable. The devices comes up in fastboot mode using the fastboot cable but is not recognized in Windows and so 'fastboot devices' comes up empty. You said you fixed that by updating the drivers manually. Can you share exactly what you did please? This has been driving me nuts for over a week. Thanks!
djlman said:
Congrats on rooting your Soho! I'm having similar problems that you did initially. The device is recognized in adb. I bought a fastboot cable. The devices comes up in fastboot mode using the fastboot cable but is not recognized in Windows and so 'fastboot devices' comes up empty. You said you fixed that by updating the drivers manually. Can you share exactly what you did please? This has been driving me nuts for over a week. Thanks!
Click to expand...
Click to collapse
fastboot devices never promted anything for me, either.
I had to go to the Device Manage in Windows, look for the Kindle and manually update the driver to the "android_winusb.inf"
Related
Hello, So I'm new to the Android Operating system, a bit of a windows guy, but not so much for linux. I Rooted my Kindle Fire HD, got the apex launcher, chrome...etc... I was removing amazon stuff that i didnt want and I accidentally removed SetupWizard.apk I noticed my navigation bar was gone. Here's were the true stupidity comes in. I Deleted SetupWizard.apk, I then reinstalled SetupWizard.apk from a Galaxy something
Now when i turn on my device, it loads up, says "Setup Wizard has stopped" and contiunes to inform me this everytime I hit ok. Can't change any settings, and the device is not able to be switched into adb mode, but it is recognized as simply a kindle on my PC. Is there any hope?? if i could get to settings im sure i could figure something out.
microsynth said:
Hello, So I'm new to the Android Operating system, a bit of a windows guy, but not so much for linux. I Rooted my Kindle Fire HD, got the apex launcher, chrome...etc... I was removing amazon stuff that i didnt want and I accidentally removed SetupWizard.apk I noticed my navigation bar was gone. Here's were the true stupidity comes in. I Deleted SetupWizard.apk, I then reinstalled SetupWizard.apk from a Galaxy something
Now when i turn on my device, it loads up, says "Setup Wizard has stopped" and contiunes to inform me this everytime I hit ok. Can't change any settings, and the device is not able to be switched into adb mode, but it is recognized as simply a kindle on my PC. Is there any hope?? if i could get to settings im sure i could figure something out.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=36647251
Sent from my KFTT using xda premium
It is not really bricked. Just wait, I will post a copy of setup wizard soon within an hour or two.
Sent from my KFTT using xda app-developers app
microsynth said:
Hello, So I'm new to the Android Operating system, a bit of a windows guy, but not so much for linux. I Rooted my Kindle Fire HD, got the apex launcher, chrome...etc... I was removing amazon stuff that i didnt want and I accidentally removed SetupWizard.apk I noticed my navigation bar was gone. Here's were the true stupidity comes in. I Deleted SetupWizard.apk, I then reinstalled SetupWizard.apk from a Galaxy something
Now when i turn on my device, it loads up, says "Setup Wizard has stopped" and contiunes to inform me this everytime I hit ok. Can't change any settings, and the device is not able to be switched into adb mode, but it is recognized as simply a kindle on my PC. Is there any hope?? if i could get to settings im sure i could figure something out.
Click to expand...
Click to collapse
Do you have a factory cable?
If you don't you can order one from skorpn
or you can make one if you know how to solder
Once you have it, it's easy to deal with your problem
AmrBanawan said:
Do you have a factory cable?
If you don't you can order one from skorpn
or you can make one if you know how to solder
Once you have it, it's easy to deal with your problem
Click to expand...
Click to collapse
That is the cable that came with the device right?
microsynth said:
That is the cable that came with the device right?
Click to expand...
Click to collapse
The factory cable is a little different. But, you may not need one.
Turn your device off and enter the following command:
Code:
fastboot -i 0x1949 getvar product
When you see "waiting for device" turn your KFHD on and that should put it in fastboot mode. In fastboot, you will be able to restore a stock "system.img" and repair your device.
soupmagnet said:
The factory cable is a little different. But, you may not need one.
Turn your device off and enter the following command:
Code:
fastboot -i 0x1949 getvar product
When you see "waiting for device" turn your KFHD on and that should put it in fastboot mode. In fastboot, you will be able to restore a stock "system.img" and repair your device.
Click to expand...
Click to collapse
Will this work without Adb mode, I cannot enable it at the moment
microsynth said:
Will this work without Adb mode, I cannot enable it at the moment
Click to expand...
Click to collapse
Fastboot and ADB are two completely different programs that work in completely different modes. As long as your drivers are in good working order, you should have nothing to worry about.
soupmagnet said:
Fastboot and ADB are two completely different programs that work in completely different modes. As long as your drivers are in good working order, you should have nothing to worry about.
Click to expand...
Click to collapse
Ok, I have the computer at waiting for device, after downloading an image to restore. The Kindle is now black, nothing on the screen. Is it working? or should I try to turn it off and on again
microsynth said:
Ok, I have the computer at waiting for device, after downloading an image to restore. The Kindle is now black, nothing on the screen. Is it working? or should I try to turn it off and on again
Click to expand...
Click to collapse
UMM...Where did you get this image that you restored to the device? What command did you use to flash it into place?
soupmagnet said:
UMM...Where did you get this image that you restored to the device? What command did you use to flash it into place?
Click to expand...
Click to collapse
Im using the software from the link above, In that I used step 3
microsynth said:
Im using the software from the link above, In that I used step 3
Click to expand...
Click to collapse
[Edit:] Never mind that. It's pretty obvious what happened in your case.
I'll quote the creator of the tool you used to restore your Kindle:
prokennexusa said:
WARNING! THIS TOOL CAN PERMANENTLY DAMAGE THE KINDLE IF IT IS NOT USED PROPERLY. DO NOT FLASH THE
KINDLE FIRE 2 IMAGE TO A KINDLE FIRE HD OR FLASH A KINDLE FIRE HD 7" TO A KINDLE FIRE 8.9" DEVICE. THIS
WILL CAUSE PERMANENT DAMAGE THAT CAN NOT BE REVERSED. ONLY FLASH THE CORRECT MODEL SOFTWARE
TO YOUR DEVICE.
Click to expand...
Click to collapse
soupmagnet said:
[Edit:] Never mind that. It's pretty obvious what happened in your case.
I'll quote the creator of the tool you used to restore your Kindle:
Click to expand...
Click to collapse
He has a KFHD 7" and he chose the correct restore option, What makes you say that?!
It is okay, Don't panic.
But you really need a fastboot/factory cable now, Once you have it,
Let us try something a little different, You now have 3 .img files in you backup folder in C:\KFFirstAide\backup, Correct?
Take those files outside the folder now they are in C:\KFFirstAide
Hold down Shift and right click anywhere in the folder
Choose Open command window here
Turn off your device and then connect the fastboot cable, The device should power up and then fastboot logo is displayed
Copy and paste these commands in the command prompt window
fastboot -i 0x1949 flash boot boot.img
Should say
sending...
okay (time)
writing...
okay (time)
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img
AmrBanawan said:
He has a KFHD 7" and he chose the correct restore option, What makes you say that?!
Click to expand...
Click to collapse
I hope you're right...
microsynth said:
Ok, I have the computer at waiting for device, after downloading an image to restore. The Kindle is now black, nothing on the screen. Is it working?
Click to expand...
Click to collapse
...but, I've rarely seen this situation turn out for the better.
It was never actually confirmed what Kindle Fire HD he is using.
I've flashed my system.img dozens of times and I've never seen anything like he's describing. From what I've seen, and considering the system.img was sent, we're looking at two possible scenarios; there was a malfunction in prokenexxusa's software OR user error played a part in the the resulting outcome.
Of the two, it's generally safe to assume the latter.
soupmagnet said:
I hope you're right...
...but, I've rarely seen this situation turn out for the better.
It was never actually confirmed what Kindle Fire HD he is using.
I've flashed my system.img dozens of times and I've never seen anything like he's describing. From what I've seen, and considering the system.img was sent, we're looking at two possible scenarios; there was a malfunction in prokenexxusa's software OR user error played a part in the the resulting outcome.
Of the two, it's generally safe to assume the latter.
Click to expand...
Click to collapse
It is a kindle fire HD 7; 16 GB it was on 7.2.3.
So is it fixed?
Sent from my KFTT using xda premium
Hello,
Let me start by saying I have looked a searched through several other threads but cannot seem to find anything that mimics my problem 100%. I had rooted the Kindle Fire HD 7" a few weeks ago and have been going along with no problem. One day (cannot remember what I installed) the KFHD crashed on me and wanted me to Restore the device in a "download mode" type of screen (used the volume buttons to select restore and power to confirm selection.) The device restarted just fine and was working normally. I went through the KFFirstAide root process again, root checker told me it was rooted. Starting using the options in KFFA to diable OTA, install play store, install google apps, installed Holo Launcher.. Some of the programs did not seem to install properly and didn't like the way things were behaving so I went to the Settings/Device/Restore to Factory Defaults...
After that process finished I am not at an Android setup screen. It has a blue Welcome at the top, select Language below that, Start below that, and a green outlined Android guy below that. When I hit start it says Just a sec.... and eventually get the message Setup Wizard has Stopped.. I can no longer see Kindle Fire ADB in the Device Manger.. Nothing seems to work on KFFA.. I have tried using the fastboot command in a command prompt (says waiting for device) and never does anything..
Basically I would like to know, what steps I may have to take to get the device to load properly again, and hopefully root the device again. IIRC the software version I last saw was 7.3.1...
Thank you for your time and assistance and appologize if it has been discussed before, but I just couldn't seem to find it and not sure what this problem is called to be able to properly search for it..
Before. it says "waiting for device", you should have the kindle powered off and disconnected from the computer. Plug it in after it says "waiting for device" and it should boot into fastboot.
Sent from my CyanogenFire HD7
Krsmqn said:
Before. it says "waiting for device", you should have the kindle powered off and disconnected from the computer. Plug it in after it says "waiting for device" and it should boot into fastboot.
Sent from my CyanogenFire HD7
Click to expand...
Click to collapse
Yep, it is powered off and the cable is disconnected. I plug it in after it says waiting for device and it powers up to the Welcome Setup screen.the command prompt on the computer still says < waiting for device >
When I hold one of the volume buttons and press power on it says Safe Mode at the bottom of the screen. Might there be something I can work with in that? Is there another boot method similar to "download" mode on the GalaxySIII?
jhutch825 said:
Yep, it is powered off and the cable is disconnected. I plug it in after it says waiting for device and it powers up to the Welcome Setup screen.the command prompt on the computer still says < waiting for device >
Click to expand...
Click to collapse
Sounds like you just need to get a factory cable and use that to get into fastboot mode. If the device is not recognized by adb using the fastboot cmds will not work on the 7" variant, that only works on the 8.9".
Is there a way to make on or do I have to order it?
Just ordered a factory cable ... what should I do when I get it?
onemeila said:
Sounds like you just need to get a factory cable and use that to get into fastboot mode. If the device is not recognized by adb using the fastboot cmds will not work on the 7" variant, that only works on the 8.9".
Click to expand...
Click to collapse
You can get fast boot on the KFHD7 using the stock cable and adb by issuing the adb commands then running "adb reboot bootloader" I think it was. I did it this afternoon when coming off the stock ROM to cm10.1
Edit: n/m, I though he had adb but it wouldn't boot fastboot on a restart with the cable. Guess it doesn't help his case if adb itself won't show.
-Ken
---------- Post added 30th April 2013 at 12:03 AM ---------- Previous post was 29th April 2013 at 11:41 PM ----------
jhutch825 said:
Just ordered a factory cable ... what should I do when I get it?
Click to expand...
Click to collapse
Since your boot loader is still starting up okay, when powered up with the factory/fastboot cable attached it should jump straight into fastboot. You can then use the fast boot command line tool in the adb kit from Google to push either a backup you made previously, or one from a recovery thread back onto your device. Check in the android development section, there's plenty on info on using fastboot.
-Ken
codepoet82 said:
You can get fast boot on the KFHD7 using the stock cable and adb by issuing the adb commands then running "adb reboot bootloader" I think it was. I did it this afternoon when coming off the stock ROM to cm10.1
Edit: n/m, I though he had adb but it wouldn't boot fastboot on a restart with the cable. Guess it doesn't help his case if adb itself won't show.
-Ken
---------- Post added 30th April 2013 at 12:03 AM ---------- Previous post was 29th April 2013 at 11:41 PM ----------
Since your boot loader is still starting up okay, when powered up with the factory/fastboot cable attached it should jump straight into fastboot. You can then use the fast boot command line tool in the adb kit from Google to push either a backup you made previously, or one from a recovery thread back onto your device. Check in the android development section, there's plenty on info on using fastboot.
-Ken
Click to expand...
Click to collapse
Ok. I will try that forum when it arrives.. To the best of my knowledge, I had not created a backup at any time so I will search out something from the Recovery Thread.
Thank you
-Joe
I am just 100% confused now.. I have searched and searched and everything I am reading is just making me more confused.
The cable will put the device into fast boot and will show up in Device Manager as an ADB Device.. I ran option 3 on KFFA and I don't believe the entire system image downloaded as now I am stuck on a screen with a red triangle asking to reboot or restore the device. Neither option does anything.
I have looked in recovery threads for fresh stock images but only find links and directions to TWRP.. Which, if I understand correctly, needs a 2nd bootloader.. And still will need a fresh stock image from amazon. Also, in KFFA it says to connect the device with a normal cable, not fastboot cable, in ADB mode for TWRP and the second bootloader.. I cannot get into the KF to enable ADB like it asks because I cannot get anything to load..
I have downloaded kfhd7-amazon-os-7.3.1 from goo.im and it comes in a zip file. I am not really sure of what to do..
I looked in the Android Development section of this forum and there are only 18 threads that don't talk about fastboot either. Do I need to go to a general Android Development section, not in the Kindle Fire Forum Sections?
I just want to go back to 100% factory original and start over from there..
Also, the KindleFireFirstAide dropbox seems to be overloaded and suspended, so I cannot get the images from there at the moment through their tool.
jhutch825 said:
Just ordered a factory cable ... what should I do when I get it?
Click to expand...
Click to collapse
You didn't need a fast boot cable. All you needed to do was setup ADB drivers and issue the command "adb reboot bootloader"
Sent from my KFTT using xda app-developers app
-a- said:
You didn't need a fast boot cable. All you needed to do was setup ADB drivers and issue the command "adb reboot bootloader"
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Even though the device was no longer showing up in the windows device manager as Kindle Fire ADB? The Kindle was being recognized under Mobile Devices.
I don't know if I will be able to do that now that I used Fastboot to reload Factory Reset through KindleFire First Aide (option 3).. I don't think the entire system.img downloaded before it tried to install it and their dropbox server is down now so I can't rerun the command right now.
Solved
Found a link, finally, to onemeila's KFHD System.img Restore tool... Used the fastboot cabled and got it installed and everything seems to be running flawlessly.
Same Story Here...
jhutch825 said:
Even though the device was no longer showing up in the windows device manager as Kindle Fire ADB? The Kindle was being recognized under Mobile Devices.
I don't know if I will be able to do that now that I used Fastboot to reload Factory Reset through KindleFire First Aide (option 3).. I don't think the entire system.img downloaded before it tried to install it and their dropbox server is down now so I can't rerun the command right now.
Click to expand...
Click to collapse
Hello, after looking through many, many threads..I have finally found this one. Same story here..I have not order the factory cable. I have the original cable that came with my kindlehd. Before I go and buy the cable I wanted to see if this question can be addressed?
Dnoob, it's been a while don't remember the solution but I did get a factory cable and worked everything out through fast boot
Sent from my Amazon Kindle Fire HD using Tapatalk now Free
I can put myself into fastboot. I can see my KFTT. The bootloader is broken, the recovery is broken, the boot image is broken. I am in need of drastic measures. There has to be someone that has figured this out. There must be a hardware way to access the storage as it is flash memory. Has someone figured this out? please help. Already tried firstaide I have tried everything on xda please help.
Opideousneo said:
I can put myself into fastboot. I can see my KFTT. The bootloader is broken, the recovery is broken, the boot image is broken. I am in need of drastic measures. There has to be someone that has figured this out. There must be a hardware way to access the storage as it is flash memory. Has someone figured this out? please help. Already tried firstaide I have tried everything on xda please help.
Click to expand...
Click to collapse
Flash Amazon OS 7.2.3. http://forum.xda-developers.com/showthread.php?t=1951254
thank you
seokhun said:
Flash Amazon OS 7.2.3. http://forum.xda-developers.com/showthread.php?t=1951254
Click to expand...
Click to collapse
I can get to fastboot but it wont detected fastboot. It just sits there on the fast boot screen. I'm hoping for something a little more drastic.
Opideousneo said:
I can get to fastboot but it wont detected fastboot. It just sits there on the fast boot screen. I'm hoping for something a little more drastic.
Click to expand...
Click to collapse
Type "fastboot devices" when your device is in fastboot mode and is connected to the computer. If you see no line of crazy numbers and characters, you can't use fastboot mode, in which case, you have a fancy paperweight. Unless you're in warranty, in which case, contact Amazon for an exchange.
I dont think
seokhun said:
Type "fastboot devices" when your device is in fastboot mode and is connected to the computer. If you see no line of crazy numbers and characters, you can't use fastboot mode, in which case, you have a fancy paperweight. Unless you're in warranty, in which case, contact Amazon for an exchange.
Click to expand...
Click to collapse
Just attempted "fastboot devices" nothing said no internal or external command. Should i do this from adb shell? Where should i do this from? How should i run it? Maybe I'm doing it all wrong. Also they will be able to see that it was my fault since i have a blue Kindlefire logo....
Opideousneo said:
Just attempted "fastboot devices" nothing said no internal or external command. Should i do this from adb shell? Where should i do this from? How should i run it? Maybe I'm doing it all wrong. Also they will be able to see that it was my fault since i have a blue Kindlefire logo....
Click to expand...
Click to collapse
Type "fastboot devices" and hit Enter.
You have the 2nd-bootloader installed? That won't do. You're stuck with the paperweight.
Opideousneo said:
Just attempted "fastboot devices" nothing said no internal or external command. Should i do this from adb shell? Where should i do this from? How should i run it? Maybe I'm doing it all wrong. Also they will be able to see that it was my fault since i have a blue Kindlefire logo....
Click to expand...
Click to collapse
If you can still get the device into fastboot then you still have ways to fix your device. [Fastboot devices] will always show nothing. Use this cmd:
Code:
fastboot -i 0x1949 getvar product
If nothing happens then you just have a driver issue. If you get a response saying "tate-something-something" Then you can proceed to using fastboot to reflash your backups or a backup.
You are amazing
onemeila said:
If you can still get the device into fastboot then you still have ways to fix your device. [Fastboot devices] will always show nothing. Use this cmd:
Code:
fastboot -i 0x1949 getvar product
If nothing happens then you just have a driver issue. If you get a response saying "tate-something-something" Then you can proceed to using fastboot to reflash your backups or a backup.
Click to expand...
Click to collapse
I'm not gay but I would marry you after a week of trying to get help you solved it thank you.
My kindle is brick,too
My kindle fire hd 7" is bricked 3 hours ago. I was trying to install 2nd boot loader and twrp recovery for the first time. i made one mistake. I didn't check one box of fireflash1.1. So, after reboot, my kindle is showing red screen. i want to know whether i can get to fastboot with fastboot cable(i don't have one right now but i'll order or make one my own). Also, i want to know how you brick your kindle.
myatkaung said:
My kindle fire hd 7" is bricked 3 hours ago. I was trying to install 2nd boot loader and twrp recovery for the first time. i made one mistake. I didn't check one box of fireflash1.1. So, after reboot, my kindle is showing red screen. i want to know whether i can get to fastboot with fastboot cable(i don't have one right now but i'll order or make one my own). Also, i want to know how you brick your kindle.
Click to expand...
Click to collapse
Yep, you can get to fastboot with a factory cable. I haven't used fire flash so I'm not sure what this red screen is, but the factory cable should work.
onemeila said:
If you can still get the device into fastboot then you still have ways to fix your device. [Fastboot devices] will always show nothing. Use this cmd:
Code:
fastboot -i 0x1949 getvar product
If nothing happens then you just have a driver issue. If you get a response saying "tate-something-something" Then you can proceed to using fastboot to reflash your backups or a backup.
Click to expand...
Click to collapse
How would i reflash a backup?
I got it..
myatkaung said:
My kindle fire hd 7" is bricked 3 hours ago. I was trying to install 2nd boot loader and twrp recovery for the first time. i made one mistake. I didn't check one box of fireflash1.1. So, after reboot, my kindle is showing red screen. i want to know whether i can get to fastboot with fastboot cable(i don't have one right now but i'll order or make one my own). Also, i want to know how you brick your kindle.
Click to expand...
Click to collapse
Droidit! I got it remember I used fire flash. Anyway tell me what you checked and what the partions have in them boot and recovery.
---------- Post added at 08:20 AM ---------- Previous post was at 08:18 AM ----------
myatkaung said:
My kindle fire hd 7" is bricked 3 hours ago. I was trying to install 2nd boot loader and twrp recovery for the first time. i made one mistake. I didn't check one box of fireflash1.1. So, after reboot, my kindle is showing red screen. i want to know whether i can get to fastboot with fastboot cable(i don't have one right now but i'll order or make one my own). Also, i want to know how you brick your kindle.
Click to expand...
Click to collapse
Get a factory cable even if you problem is solved with out the cable they are still nice to have just in-case.
CVanB said:
Droidit! I got it remember I used fire flash.
Click to expand...
Click to collapse
Ahh, ok. Got ya now :good:
onemeila said:
If you can still get the device into fastboot then you still have ways to fix your device. [Fastboot devices] will always show nothing. Use this cmd:
Code:
fastboot -i 0x1949 getvar product
If nothing happens then you just have a driver issue. If you get a response saying "tate-something-something" Then you can proceed to using fastboot to reflash your backups or a backup.
Click to expand...
Click to collapse
im havveing the same problem mine just says waiting for devices . i am in fastboot im useing a mac and fastboot was working when i tried to flash second bootloader
xiro49 said:
im havveing the same problem mine just says waiting for devices . i am in fastboot im useing a mac and fastboot was working when i tried to flash second bootloader
Click to expand...
Click to collapse
Uninstall and then reinstall drivers
CVanB said:
Uninstall and then reinstall drivers
Click to expand...
Click to collapse
im on a mac i dont have drivers
xiro49 said:
im on a mac i dont have drivers
Click to expand...
Click to collapse
Oh can you get access to a windows pc
CVanB said:
Oh can you get access to a windows pc
Click to expand...
Click to collapse
yeah
xiro49 said:
yeah
Click to expand...
Click to collapse
Use a pc and install the drivers. then go through your process
Cool But would like to know whats up with my mac.
the macs usb ports work fine
The kindle charges
so wheres the problem?
note adb was off when this happen but that shouldnt mess with fastboot?
Hello.
After hours of struggling and Googling (and reading mostly from this forum) I managed to root my KFHD 7.4.6 using bin4ry method. I have two questions about where I'm at right now.
Question 1: While struggling to get adb to recognize my KF, I realized that the problem was quite simple: after installing the special adb drivers, I would plug the Kindle back in and Windows would recognize the device and install the Microsoft drivers - completely ignoring the driver I had just installed. The only way I managed to get around this was to quickly interrupt Windows 7's driver installation and tell it to NOT install drivers from Windows Update.
However, I'm sure there must have been a more elegant way of accomplishing this. What would have been the correct way to do this?
Question 2: Now that adb finally recognizes the KF, and the KF shows up as "Android Composite ADB Interface" in device manager, I want to put Android 4.2.2 on the KF - so CM 10.1. I'm doing preparatory research so I can learn about what I need to do. The big concern for me now is that my KF version is 7.4.6. There seems to be relatively little information about this, and I've seen it explicitly indicated in a few places that only versions before 7.3.something have the exploit available. Does this mean I must first downgrade from 7.4.6? I've had trouble pinning resources down that would help me answer this question - so if anyone has any solid tips about this, I'd appreciate it! I'd really rather not brick it :silly:
Thanks! :good:
SpidaFly said:
Question 2: Now that adb finally recognizes the KF, and the KF shows up as "Android Composite ADB Interface" in device manager, I want to put Android 4.2.2 on the KF - so CM 10.1. I'm doing preparatory research so I can learn about what I need to do. The big concern for me now is that my KF version is 7.4.6. There seems to be relatively little information about this, and I've seen it explicitly indicated in a few places that only versions before 7.3.something have the exploit available. Does this mean I must first downgrade from 7.4.6? I've had trouble pinning resources down that would help me answer this question - so if anyone has any solid tips about this, I'd appreciate it! I'd really rather not brick it :silly:
Click to expand...
Click to collapse
I just found this:
http://forum.xda-developers.com/showthread.php?t=2271909
So the answer to my question appears to be "YES", correct? It appears that I need to flash back to 7.2.3?
Question 1 still remains unsolved.
Well you could downgrade it, I don't know if the latest update causes problems, but the thing that needs downgrading isn't the os, its the bootloader. I suggest the fireflash method in seokhuns tutorial, the one you linked. Just make sure to check the first box at the top in fire flash or you will have a red screen brick, which requires a fastboot cable to fix. Also I have never heard of windows update having drivers for the kindle, I mean I usually hit skip anyways, I believe the more elegant solution may have come with kindle fire first aid, not positive though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thanks!
I'm having another little inconsistency now.
I disconnect and power off my KF.
I run in cmd: fastboot -i 0x1949 getvar product
It says < waiting for device >
I then plug in my (powered off) KF, and it boots up NORMALLY, and fastboot doesn't return the expected tate-xxx.
Any ideas why?
My ADB is seeing the device. (ie. adb devices is returning one device).
Your fastboot drivers aren't working.
soupmagnet said:
Your fastboot drivers aren't working.
Click to expand...
Click to collapse
Indeed. Can this be solved by wiping existing drivers and reinstalling Amazon's USB drivers from sdk/extras/amazon ?
EDIT: I've attempted reinstall twice with no improvement. ADB works, fastboot won't.
Um I thought that command only worked on a 8.9" kindle to get it into fastboot.try this instead:
Adb shell su -c "reboot bootloader"
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Um I thought that command only worked on a 8.9" kindle to get it into fastboot.try this instead:
Adb shell su -c "reboot bootloader"
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Interesting. I tested that. adb shell su -c "reboot bootloader" does indeed put my device in fastboot mode, and fastboot -i 0x1949 reboot takes it out.
Interesting. Seokhun's tutorial seems to indicate that fastboot -i 0x1949 getvar product should do it as well... so it seems that my fastboot drivers are... kinda half working? Or something?
SpidaFly said:
Interesting. I tested that. adb shell su -c "reboot bootloader" does indeed put my device in fastboot mode, and fastboot -i 0x1949 reboot takes it out.
Interesting. Seokhun's tutorial seems to indicate that fastboot -i 0x1949 getvar product should do it as well... so it seems that my fastboot drivers are... kinda half working? Or something?
Click to expand...
Click to collapse
That option may have been removed in later versions of the bootloader. Some have had success with it while others apparently haven't. If the reboot command works, your drivers should be working properly.
soupmagnet said:
That option may have been removed in later versions of the bootloader. Some have had success with it while others apparently haven't. If the reboot command works, your drivers should be working properly.
Click to expand...
Click to collapse
Sounds good, thanks. I'm following that tutorial even though it's for 7.4.3, and I'm on 7.4.6. I hope that doesn't cause any issues - but 7.4.6 looks like it's pretty new, so I don't see other options.
Ok - I've followed the aforementioned tutorial precisely up to step 4. When I try to boot the kindle up, it shows orange logo, then blue logo, then looks like it's trying to boot normally, then sends me into TWRP.
Is this what is called "boot loop"?
At this point my PC doesn't see the sdcard so I can't get CM/Gapp copied over.
Would it be safe to push CM & Gapp to the sdcard using adb, then resume with TWRP?
EDIT: Still can't boot into the system. Just sideloaded CM 10.1 ROM onto the sdcard. Safe to continue with Step 4, wipe stuff, and install the CM rom?
SpidaFly said:
EDIT: Still can't boot into the system. Just sideloaded CM 10.1 ROM onto the sdcard. Safe to continue with Step 4, wipe stuff, and install the CM rom?
Click to expand...
Click to collapse
This ended up working.
However, now with CM 10.1, my PC isn't recognizing the device for MTP. It still does recognize it as an ADB device, but ADB doesn't see it.
Odd that MTP isn't working, u can always switch to pptp mode if that helps, but everything goes to the dcim folder on the sdcard.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Odd that MTP isn't working, u can always switch to pptp mode if that helps, but everything goes to the dcim folder on the sdcard.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Got it working. Basically just uninstalled the existing drivers and reinstalled standard drivers. Works like a charm. I love CM, this is great! Thanks all, for the help!
I'll worry about getting adb going again later.
just as the title says! its my moms. any help or links to get help would be nice. most of the stuff i find is able to turn on or must be rooted.
joeyx2 said:
just as the title says! its my moms. any help or links to get help would be nice. most of the stuff i find is able to turn on or must be rooted.
Click to expand...
Click to collapse
ok well in either situation your going to need a fastboot cable/adapter, i recommend getting the blackhat adapter mentioned in hashcodes 2nd bootloader + twrp tutorial. Now for the other thing i need to know, is this a 2012 or 2013 model? (2013 has no front facing camera)
It does have a front facing camera. Can you give me a link? First time looking in the Kindle fire section.
joeyx2 said:
It does have a front facing camera. Can you give me a link? First time looking in the Kindle fire section.
Click to expand...
Click to collapse
Ok lemme grab 2 links you will need.
The thread i was talking about it this: http://forum.xda-developers.com/showthread.php?t=2128848
I personally recommend a custom rom over amazon os so that tutorial could be useful to you in the future should you decide to flash a custom rom on it. There's a link towards the top that goes to the site where you get the fastboot adapter.
Alright and secondly you will need this: http://forum.xda-developers.com/showthread.php?t=2096888
Read its instructions or you might have issues. Also when you plug in your kindle with the fastboot adapter it will show up as a tate device in the device manager, download the drivers in my signature and extract them somewhere on your computer, then in the device manager right click the tate device and hit update drivers and choose a place to search for them and choose where you extracted my drivers and it should install the drivers. If you are on windows 8 you will have to disable driver signature enforcement first though. Once drivers are working you should be able to restore with kffa.
well i ordered the fastboot adapter and it does go into fastboot mode but i have tried a few utilities and they all seem to blow right threw the process. its like it seeing the phone but not doing anything. the only thing i can think of is USB debugging was not turned on and that may be why i cant get it to act right. of course i cant turn it on cause i'm stuck at the logo so is there a way around that or is there a program like Samsung has called Odin that i can use to flash stock everything on?
Nonono. Adb has nothing to do with fastboot. Adb commands can't even be used with fastboot, only fastboot commands can. Try opening a command prompt that's cd'd into a directory with fastboot in it (kffa or SRT) and run "fastboot -i 0x1949 getvar product", if it reports back something then we can establish that fastboot is atleast working.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Nonono. Adb has nothing to do with fastboot. Adb commands can't even be used with fastboot, only fastboot commands can. Try opening a command prompt that's cd'd into a directory with fastboot in it (kffa or SRT) and run "fastboot -i 0x1949 getvar product", if it reports back something then we can establish that fastboot is atleast working.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
ok sorry but i havent played with the kindle much as far as rooting, or with command prompt on any device so im kinda lost on what to do and not sure what kffa or srt is.
joeyx2 said:
ok sorry but i havent played with the kindle much as far as rooting, or with command prompt on any device so im kinda lost on what to do and not sure what kffa or srt is.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1951254
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Kffa was one of the links I sent you.... download and extract it. Shift + right click it's folder and hit New command window here. Then run that command I mentioned.
Sent from my LG-P769 using Tapatalk
i did what you said and at first i didn't but eventually got the command you told me to put in to recognize and read something tate in the command window but i did not see tate in device manager and the utilities still blows though really fast and dont work. im on vista so do you think that is the problem? this is really pissing me off that i cant get this figured out. im about to uninstall everything and delete everthing and start over.
joeyx2 said:
i did what you said and at first i didn't but eventually got the command you told me to put in to recognize and read something tate in the command window but i did not see tate in device manager and the utilities still blows though really fast and dont work. im on vista so do you think that is the problem? this is really pissing me off that i cant get this figured out. im about to uninstall everything and delete everthing and start over.
Click to expand...
Click to collapse
well the good news is that means fastboot is working, it only is called a tate device in the device manager initially, once you isntall th edrivers it will show up a s a adb interface which is confusing becuase you don't use adb with fastboot. Anyways you should be able to attempt manualyl flashing the device from that command prompt now using certain commands like
Code:
fastboot -i 0x1949 flash <partition name> imagename
so something like
Code:
fastboot -i 0x1949 flash system system.img
it could be that kffa failed to retreive the files or something so it dint flash, sometimes its download links don't work, try srt i think linear posted the link to it, it might actually work out of the box.