Related
I am trying to install a second bootloader on my Kindle Fire HD in order to install the Kinology ROM. I am using these instructions: http://forum.xda-developers.com/showthread.php?t=2128848. On the 5th step, it requires me to be in fastboot mode. Do I need a special cable for this? I tried doing as the post said with the charging cable my Kindle came with, and instead of starting in fastboot mode, it boots to the stock OS. What am I doing wrong? Thanks.
DungeonxDragpm said:
I am trying to install a second bootloader on my Kindle Fire HD in order to install the Kinology ROM. I am using these instructions: http://forum.xda-developers.com/showthread.php?t=2128848. On the 5th step, it requires me to be in fastboot mode. Do I need a special cable for this? I tried doing as the post said with the charging cable my Kindle came with, and instead of starting in fastboot mode, it boots to the stock OS. What am I doing wrong? Thanks.
Click to expand...
Click to collapse
To reboot your device into fastboot mode you need to enter this command in CMD wherever you have access to adb
adb shell su -c "reboot bootloader"
Then continue with step 5
and make sure you transfer kinology files to your kindle before you proceed so you can flash it right after you flash TWRP.
but note that if something goes wrong and you find yourself in a bootloop, then this command will not work since adb only works when the OS boots, and you WILL need a fastboot cable to get out, This is a special cable that can be made by making a simple modification to any micro USB cable like the one that came with the device, Believe me you will need one sooner or later.
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.
I have Kindle Fire HD 7 - 11.3.1.0
I am an adb users. I know how to use it. If that helps. My problem is that I cannot get the device to boot into fastboot. I run the command adb devices and it sees my device.. I reboot it, shell, etc. But when I run the "fastboot -i 0x1949 getvar product" command it stays on wait for device. I am using the factory cable that came with the device. It is new. I have run out of ideas... I start with a powered off device (adb is enabled in the settings).. I run the command on the command line.. its now sitting on waiting for device....I plug in the cable .. it powers up.. but just boots. I was able to root the device.. but will NOT boot to fast boot...
Please let me know if I am missing something..
Thanks
Glen
adkg12 said:
I have Kindle Fire HD 7 - 11.3.1.0
I am an adb users. I know how to use it. If that helps. My problem is that I cannot get the device to boot into fastboot. I run the command adb devices and it sees my device.. I reboot it, shell, etc. But when I run the "fastboot -i 0x1949 getvar product" command it stays on wait for device. I am using the factory cable that came with the device. It is new. I have run out of ideas... I start with a powered off device (adb is enabled in the settings).. I run the command on the command line.. its now sitting on waiting for device....I plug in the cable .. it powers up.. but just boots. I was able to root the device.. but will NOT boot to fast boot...
Please let me know if I am missing something..
Thanks
Glen
Click to expand...
Click to collapse
So no help this early in the day.. ?
It will not boot into FASTBOOT..oh well
Thanks
Glen
If its rooted run this
Code:
adb shell "su -c 'reboot bootloader'"
What exactly are you trying to achieve with fastboot, that's a 2013 HD, we only have root access so I don't know what you want to use fastboot for.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
If its rooted run this
Code:
adb shell "su -c 'reboot bootloader'"
What exactly are you trying to achieve with fastboot, that's a 2013 HD, we only have root access so I don't know what you want to use fastboot for.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I want to flash it back to the earlier version .. is this not possible.. it seems to be...reading that it needs to be reverted to 7.3 or something..
And no.. running that command doesnt work either.. It reboots, but only boots up to a normal boot..
Thanks
Glen
bleeds said:
I want to flash it back to the earlier version .. is this not possible.. it seems to be...reading that it needs to be reverted to 7.3 or something..
And no.. running that command doesnt work either.. It reboots, but only boots up to a normal boot..
Thanks
Glen
Click to expand...
Click to collapse
Woooo, slow down. You have the 2013 Kindle Fire HD 7 and there are no exploit for the bootloader yet. You're gonna brick your tablet. That exploit is for the 2012 Kindle Fire HD 7 only. Stop now and know there is only root available for your tablet at the moment.
Hi.
I've got the same problem - but got 2012 device ( no. D059, camera on left (or right/down/up if you like ) side of screen )
I use typical usb cable, got root acces, adb see my device. But when I plug after typing "fastboot -i 0x1949 getvar product" its normally booted up to system
any advices?
bleeds said:
I want to flash it back to the earlier version .. is this not possible.. it seems to be...reading that it needs to be reverted to 7.3 or something..
And no.. running that command doesnt work either.. It reboots, but only boots up to a normal boot..
Thanks
Glen
Click to expand...
Click to collapse
Woa there don't attempt that. 2013 kindle fire hd's aren't supposed to run a 7.x.x os, that's the version used on the previous years, your is supposed to be 11.x.x.
Sent from my Amazon Kindle Fire HD using Tapatalk
anybody?
I look for factory cable, but in Poland it is unavailable anywhere is there possibility to do something with normal usb cable?
"adb reboot bootloader", also what are you attempting to do with fastboot, just wanna make sure you aren't trying to downgrade to an os not meant for your device (aka anything besides 11.x.x is not meant for your device and will brick it).
Sent from my Amazon Kindle Fire HD using Tapatalk
I want to flash custom rom.
Read my first post in this thread - my Kindle is 2012 device.
But problem is same that adkg12's so I post here, altough write new one
Eh I would just use the fireflash method as it doesn't require fastboot access, though if you don't see the checkbox next to the red text and leave it unchecked your kindle will have a red screen that only a fastboot cable can fix. Might be less dangerous for you to just use the method you are using then, as long as you check everything's md5sum then its a lot safer for you since you can't get your bands on a fastboot cable.
Sent from my Amazon Kindle Fire HD using Tapatalk
Hi there,
I have a new KFHD 7" with bootloader version 7.4.9, which I tried to put a custom ROM with the How-To from the Cyanogen website (Install_CM_for_tate).
I have a fastboot cable and everything went fine, after flashing the files, the device started TWRP. I pushed the CyanogenMod and Gapps over, which completed successfully and then back-upped as recommended.
After that, I was asked if I wanted it to install SU which I accepted. In the next reboot, I got into a bootloop with the kindle logo not turning blue anymore.
I tried to reflash, but that resulted also in a bootloop without getting into TWRP.
Any ideas what I should try next? Thanks!
3rd gen.
2012
Tate-PVT-08
thatissounfair said:
Hi there,
I have a new KFHD 7" with bootloader version 7.4.9, which I tried to put a custom ROM with the How-To from the Cyanogen website (Install_CM_for_tate).
I have a fastboot cable and everything went fine, after flashing the files, the device started TWRP. I pushed the CyanogenMod and Gapps over, which completed successfully and then back-upped as recommended.
After that, I was asked if I wanted it to install SU which I accepted. In the next reboot, I got into a bootloop with the kindle logo not turning blue anymore.
I tried to reflash, but that resulted also in a bootloop without getting into TWRP.
Any ideas what I should try next? Thanks!
3rd gen.
2012
Tate-PVT-08
Click to expand...
Click to collapse
Use the KFHD system restore tool. Make sure it's for the 7" tablet. You'll need a fastboot cord to restore.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
Use the KFHD system restore tool. Make sure it's for the 7" tablet. You'll need a fastboot cord to restore.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your reply!
I tried following the instructions from Thread 1951254.
Problem is, I plugged in the fastboot cable, the Kindle shows the fastboot logo, I enter
Code:
adb shell su -c "reboot bootloader"
and get
Code:
error: device not found
When entering
Code:
fastboot -i 0x1949 getvar product
the product type is printed.
I thought adb commands don't work in fastboot mode?
Is it maybe the Kindle boot version that I have? I think it was 7.4.9...
Adb takes adb commands.
Fastboot takes fastboot commands.
There is no need to issue a reboot command because you are already in bootloader mode (fastboot).
thatissounfair said:
Thanks for your reply!
I tried following the instructions from Thread 1951254.
Problem is, I plugged in the fastboot cable, the Kindle shows the fastboot logo, I enter
Code:
adb shell su -c "reboot bootloader"
and get
Code:
error: device not found
When entering
Code:
fastboot -i 0x1949 getvar product
the product type is printed.
I thought adb commands don't work in fastboot mode?
Is it maybe the Kindle boot version that I have? I think it was 7.4.9...
Click to expand...
Click to collapse
The ADB commands are there in case you still have access to your OS and root. That's when this can be done with a regular USB cord. You don't have that so use your fastboot cord to enter fastboot automatically (should.) Run the bat and choose option 3.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
The ADB commands are there in case you still have access to your OS and root. That's when this can be done with a regular USB cord. You don't have that so use your fastboot cord to enter fastboot automatically (should.) Run the bat and choose option 3.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Awesome, it worked!! Thanks for the explanation too, very helpful!
I would like to retry the flashing. Any recommendations or tips I need to follow?
Got it, thanks everyone!!
thatissounfair said:
Awesome, it worked!! Thanks for the explanation too, very helpful!
I would like to retry the flashing. Any recommendations or tips I need to follow?
Click to expand...
Click to collapse
If you want the 2nd bootloader and TWRP,use FireFlash or Flasher or flash them manually
Sent from my device running CyanogenMod 11
Hey guys, I've got a KFHD 7" running system 7.4.9 and I was able to root it today successfully and I would like to install the LiquidSmotth 4.4.4 ROM on it.
The problem that I'm having is that I need a recovery likw TWRP 2.7+ but the instructions are way too complicated and they mention a 2nd bootloader which requires a special cable, what the hell, is it that complex?
I appreciate if anyone can point out a more human way of getting TWRP 2.7 or CWM for KK on my Kindle v 7.4.9.
Thanks!
theplagueisback said:
Hey guys, I've got a KFHD 7" running system 7.4.9 and I was able to root it today successfully and I would like to install the LiquidSmotth 4.4.4 ROM on it.
The problem that I'm having is that I need a recovery likw TWRP 2.7+ but the instructions are way too complicated and they mention a 2nd bootloader which requires a special cable, what the hell, is it that complex?
I appreciate if anyone can point out a more human way of getting TWRP 2.7 or CWM for KK on my Kindle v 7.4.9.
Thanks!
Click to expand...
Click to collapse
Alright. Let's get you started.
First of all,use the Kindle fire system restore tool to downgrade to 7.4.6 OR 7.2.3. Either will do. Next,root it using the Bin4ry tool and download the TWRP 2.7.0.0 image with the freedom boot image that is corresponding to your software version. Then,flash them using FireFlash or Flasher or manual method.
Bingo.
Sent from my device running CyanogenMod 11
SafinWasi said:
Alright. Let's get you started.
First of all,use the Kindle fire system restore tool to downgrade to 7.4.6 OR 7.2.3. Either will do. Next,root it using the Bin4ry tool and download the TWRP 2.7.0.0 image with the freedom boot image that is corresponding to your software version. Then,flash them using FireFlash or Flasher or manual method.
Bingo.
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
Hi man, I'm getting "No such file or directory" when I try to reboot in fastboot mode, here's the output:
Code:
C:\AndroidSDK\sdk\platform-tools>adb devices -l
List of devices attached
D025A0A024121UQQ device
C:\AndroidSDK\sdk\platform-tools>adb shell su -c "reboot bootloader"
[-] exec: No such file or directory
C:\AndroidSDK\sdk\platform-tools>
When I ran that command on the Kindle I got a root prompt and I allowed it.
Under the device manager I have listed: N2A ADB Mode / Kindle ADB Mode | HD 7
theplagueisback said:
Hi man, I'm getting "No such file or directory" when I try to reboot in fastboot mode, here's the output:
Code:
C:\AndroidSDK\sdk\platform-tools>adb devices -l
List of devices attached
D025A0A024121UQQ device
C:\AndroidSDK\sdk\platform-tools>adb shell su -c "reboot bootloader"
[-] exec: No such file or directory
C:\AndroidSDK\sdk\platform-tools>
When I ran that command on the Kindle I got a root prompt and I allowed it.
Under the device manager I have listed: N2A ADB Mode / Kindle ADB Mode | HD 7
Click to expand...
Click to collapse
Turn it off,type in this:
Code:
fastboot -i 0x1949 getvar product
and plug it in.
SafinWasi said:
Turn it off,type in this:
Code:
fastboot -i 0x1949 getvar product
and plug it in.
Click to expand...
Click to collapse
The problem is, I don't have a fastboot cable and I would like to try to enter fastboot without buying that cable if possible.
SafinWasi said:
Turn it off,type in this:
Code:
fastboot -i 0x1949 getvar product
and plug it in.
Click to expand...
Click to collapse
Ok, I did that and it kept saying "aiting for device".
i'm going to try again, hold on.
theplagueisback said:
The problem is, I don't have a fastboot cable and I would like to try to enter fastboot without buying that cable if possible.
Click to expand...
Click to collapse
This command will work with a normal cable if you have root.
SafinWasi said:
This command will work with a normal cable if you have root.
Click to expand...
Click to collapse
So I ran it again and it kept says "waiting for device", my Kindle is rooted with "Mulai Root" and I used root checker to confirm that it is rooted.
I turned the Kindle off.
I issued the command on the command prompt.
The command prompt said "waiting for device".
I plugged in the USB cable.
The Kindle turned on.
The Kindle booted all the way to the launcher.
The command prompt kept saying "waiting for device".
I would appreciate any more ideas.
Thank you!
theplagueisback said:
So I ran it again and it kept says "waiting for device", my Kindle is rooted with "Mulai Root" and I used root checker to confirm that it is rooted.
I turned the Kindle off.
I issued the command on the command prompt.
The command prompt said "waiting for device".
I plugged in the USB cable.
The Kindle turned on.
The Kindle booted all the way to the launcher.
The command prompt kept saying "waiting for device".
I would appreciate any more ideas.
Thank you!
Click to expand...
Click to collapse
Odd... can you use FireFlash?
SafinWasi said:
Odd... can you use FireFlash?
Click to expand...
Click to collapse
Yes, I just installed and ran it using root access. But I'm running system 7.4.9, what should I do now with the app open to downgrade?
The program states "Warning: current bootloader is not kfhd7-u-boot-prod-7.2.3.bin"
Can you help me using FireFlash to downgrade?
Thanks
The culprit was the chinese or vietnamise root, I rooted again using qemu and now I was able to boot into fastboot mode.
I hae a big problem, I sued the Kindle Fire First Aid to restore to 7.2.3 and now my kindle stays on the boot logo.
How can I restore it now?
EDIT: Never mind, it actually booted up.
Hey, I managed to get downgraded and now I'm on this part:
TWRP 2.7.0.0 image with the freedom boot image that is corresponding to your software version.
I'm confused if I should install a 2nd-bootloader or not, I installed fire flash already, let me know if you can help me with a link with the next steps to perform.
Thanks
I think I kind of managed to do it, the problem now is that TWRP loads but the ROM I flashed didn't boot (Liquid Smotth 4.4.4), I'm going to start a new thread.
Thanks