fastboot on kf2? cwm?
you can get into fastboot with a factory usb cable
Reflexdarky said:
you can get into fastboot with a factory usb cable
Click to expand...
Click to collapse
what about idme bootmode? also is there a recovery?
fmkilo said:
fastboot on kf2? cwm?
Click to expand...
Click to collapse
if you have root access, you can try this code in adb mode
Code:
adb shell
su
reboot bootloader
padest.com said:
if you have root access, you can try this code in adb mode
Code:
adb shell
su
reboot bootloader
Click to expand...
Click to collapse
yes, I know how to use adb and reboot. Typing that does not work. It just reboots normally. Some people have reported the ability to type reboot recovery and get to fastboot. But the recovery on this device is the screen that says that your kindle cannot boot.
I recommend investing in a factory/fastboot cable if you are planning to do any type of modifcations to your device.
They only cost like 6 dollars and mine has saved my ass way more than I'd like to admit.
reverendkjr said:
I recommend investing in a factory/fastboot cable if you are planning to do any type of modifcations to your device.
They only cost like 6 dollars and mine has saved my ass way more than I'd like to admit.
Click to expand...
Click to collapse
I have been thinking about making one. I have a great cable for it, I just have to sit down and do it.
Is there any way besides the factory cable to get to fastboot on kf2?
Read this before you buy anything
Before you go for the fastboot cable - read this:
http://forum.xda-developers.com/showpost.php?p=33807375&postcount=34
Apperently the size of the restore image is to big for fastboot.
irve said:
Before you go for the fastboot cable - read this:
http://forum.xda-developers.com/showpost.php?p=33807375&postcount=34
Apperently the size of the restore image is to big for fastboot.
Click to expand...
Click to collapse
Sparse image. Strip apps that can be restored.
All I want fastboot for is a bootloader and recovery. Not a restored system image.
I did actually get to fastboot. I modified a samsung micro b cable. I didn't solder anything, and as soon as it showed up as fastboot, I switched the cable to a good cable I knew would work.
apparently, it is the only way to get to fastboot on this device, and I'm glad I know how to recognize it on this device now.
how did you modify it ?
Hondologe said:
how did you modify it ?
Click to expand...
Click to collapse
if you are asking about my fastboot cable, I spliced a wire into the red line in the usb cord then wrapped that tightly around pin 4 and replaced all covers so that it lined up correctly with the pins of the device.
fmkilo said:
fastboot on kf2? cwm?
Click to expand...
Click to collapse
adb shell su -c 'idme bootmode 4'
fmkilo said:
adb shell su -c 'idme bootmode 4'
Click to expand...
Click to collapse
I personally just used
Adb shell
Su
Reboot boot loader
Then verified with fastboot -i 0x1949 devices
Worked great. Fmkilo thanks for convincing Hashcode to work on this, you need any testers or anything pm me
I bought a Factory Cable
As soon as I plug in the cable, and my Kindle startint and i see fastboot screen,
My pc find a new Device and cant install driver " Otter2-Prod-04". (Win7 x64)
what do you do then?
How can I get the drivers?
how can I install twrp.
avathor said:
I bought a Factory Cable
As soon as I plug in the cable, and my Kindle startint and i see fastboot screen,
My pc find a new Device and cant install driver " Otter2-Prod-04". (Win7 x64)
what do you do then?
How can I get the drivers?
how can I install twrp.
Click to expand...
Click to collapse
Your main problem is windows. Kfu has the drivers, but if you already rooted of, you can try to use the method here you do not need a factory cable.
avathor said:
I bought a Factory Cable
As soon as I plug in the cable, and my Kindle startint and i see fastboot screen,
My pc find a new Device and cant install driver " Otter2-Prod-04". (Win7 x64)
what do you do then?
How can I get the drivers?
how can I install twrp.
Click to expand...
Click to collapse
Your main problem is windows. Kfu has the drivers, but if you already rooted of, you can try to use the method here you do not need a factory cable.
fmkilo said:
Your main problem is windows. Kfu has the drivers, but if you already rooted of, you can try to use the method here you do not need a factory cable.
Click to expand...
Click to collapse
There is a special version of KFU for Kindle Fire 2 ?
I know the other method where I do not need Factory cable.
What if it goes wrong?
what do I do?
My other PC find also not a driver for it.
avathor said:
There is a special version of KFU for Kindle Fire 2 ?
I know the other method where I do not need Factory cable.
What if it goes wrong?
what do I do?
My other PC find also not a driver for it.
Click to expand...
Click to collapse
No, there is not. Get the KFU for the original Fire and that will get you the drivers. That's all you're getting from it. Don't bother with anything else in the tool.
If it goes wrong, you're screwed most likely.
You get a fastboot/factory cable.
Skorpn sells some nice ones, you can look him up on XDA.
Odds are things shouldn't go wrong, but IF they do, you will need a fastboot cable to fix things.
It's up to you how you want to go about that.
Does anyone have any idea why the Fasbootdriver does not work with me?
Have just used the normal usb cable, via ADB Shell "reboot recovery"
booted into fastboot,
then used "fasboot devices" and my Tableed was visible.
"fastboot reboot" works too.
But when I bring my tablet with the fastboot cable into recovery mode,
shows me "fasboot devices" nothing.
To root my kindle I have also long search for the right driver, not a driver of all guides worked for me.
Only the Amazon driver from SDK manager works. I have here 3 PC´s and 1 Notebook (alls PC´s Win7 and Notebook Win8)
I tested it on alls PC´s, but it still dnot work.
Related
Hi, I recently bought a factory cable because my Kindle is bricked. I'm stuck at the kindle fire logo with no adb shell and fastboot says "waiting for device". I got in this situation by doing a wipe from twrp and then flashing the stock recovery (dumb, I know).
Anyway, with a regular cable I can do basic adb commands (adb reboot, etc).
With the factory cable my kindle isn't showing up under adb devices. Windows recognizes it and it shows up in the device manager. I've already re-installed the drivers and everything.
Here's an outline of what happens when I plug in the factory cable. This is starting with the kindle off.
Kindle turns on and goes tot he kindle fire logo and freezes. The power button is green with the factory cable. I noticed that with the normal cable it's orange. I'm not sure if this has any relevance at all.
Anyway, I'm wondering what I can do to get my kindle to show up in adb while using the factory cable.
If you need more info from me let me know and I'll add it.
A factory cable puts the device in fastboot mode, therefore will only accept fastboot commands.
soupmagnet said:
A factory cable puts the device in fastboot mode, therefore will only accept fastboot commands.
Click to expand...
Click to collapse
I'm not sure if I'm missing something, but fastboot commands aren't working either. It's not showing up under fastboot devices and fastboot flash recovery hangs at "waiting for device".
WhatTheFiber said:
I'm not sure if I'm missing something, but fastboot commands aren't working either. It's not showing up under fastboot devices and fastboot flash recovery hangs at "waiting for device".
Click to expand...
Click to collapse
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
The second post is about device drivers and what to look for in the device manager when your device is in fastboot mode.
It's also possible that you aren't including the vendor ID in your fastboot command. That's covered in the third post.
kinfauns said:
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
The second post is about device drivers and what to look for in the device manager when your device is in fastboot mode.
It's also possible that you aren't including the vendor ID in your fastboot command. That's covered in the third post.
Click to expand...
Click to collapse
Thank you so much! I was able to flash twrp by using fastboot -i 0x1949. Now I've just got to choose a new rom to flash .
So, I know not supposed to post questions that are lame, but I can't seem to figure this out. I will state my specs/situation:
I am stuck on the first step of installing FFF on my first Kindle Fire 1st gen.
I am on a Macbook Pro Retina 15" mid-2012 (USB3.0/2.0 mix ports only)
I am using KFU on a Win8 64-bit Virtual Machine (VMWare latest version)
The kindle fire is in fastboot mode (I'm pretty sure, at least).
It is stuck on the stock Kindle fire boot-up logo.
install_Drivers was run successfully after enabling unsigned driver installs.
Run.bat was executed
selected Option 5 first, to install FFF
FFF was downloaded by KFU, the Fire rebooted and then got stuck.
As it rebooted, I had forgotten to automatically have my Fire connect to the Virtual Machine, so VMWare prompted my with what system I wanted the fire connected to. I'm not sure if that delay has something to do with the stall and failure of KFU to install FFF or get out of fastboot.
KFU doesn't recognize the Kindle ("waiting for device" message; ADB: Offline; Boot Status:Unknown).
In my "other devices" on Windows Device Manager I see "Base System Device" and "Unknown Device"
My questions are:
1. How do I go about getting it out of fastboot mode even though KFU can't see the device.
2. What was I doing wrong in the first place?
Before you tell me:
I have read through the Guide
I have read through and searched much of the KFU dev thread
I have searched the forums, without a clear solution.
Thank you very much for your help!!!
escoloader said:
2. What was I doing wrong in the first place?
Click to expand...
Click to collapse
This:
I am on a Macbook Pro Retina 15" mid-2012 (USB3.0/2.0 mix ports only)
I am using KFU on a Win8 64-bit Virtual Machine (VMWare latest version)
Click to expand...
Click to collapse
Use breakdroid instead
Sent from my Amazon Kindle Fire HD using Tapatalk 2
soupmagnet said:
This:
Use breakdroid instead
Click to expand...
Click to collapse
How do I get it back to normal booting first?
Thanks for your help!
escoloader said:
How do I get it back to normal booting first?
Thanks for your help!
Click to expand...
Click to collapse
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot
Thepooch said:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Thank you for the help, but could you please explain how I use that code, step by step if possible?
Thanks a lot
EDIT: I guess I should specify, I do NOT have a fastboot factory cable. Do I need one?
Okay since you can use windows on a vm start there. Shift+right click on the tools folder inside KFU select open command window here, plug in the kindle, type the first command hit enter, type the second command hit enter if all goes well it should reboot normally. Same concept on a mac whatever directory adb and fastboot are in open a terminal, same commands same method. Good luck
Edit: in fact you can just copy paste my commands then you know you got it right. Dunno about the cable yet see if the commands work.
Thepooch said:
Okay since you can use windows on a vm start there. Shift+right click on the tools folder inside KFU select open command window here, plug in the kindle, type the first command hit enter, type the second command hit enter if all goes well it should reboot normally. Same concept on a mac whatever directory adb and fastboot are in open a terminal, same commands same method. Good luck
Edit: in fact you can just copy paste my commands then you know you got it right. Dunno about the cable yet see if the commands work.
Click to expand...
Click to collapse
Did the first one, but still says "waiting for device" and nothing is happening. :/ (EDIT: for clarity's sake, nothing happening means its still stuck on the kindle fire white/orange stock boot logo)
btw, thank you for your help.
Hold the power button to turn the device off. Enter the command, and turn the device on when you see "waiting for device".
soupmagnet said:
Hold the power button to turn the device off. Enter the command, and turn the device on when you see "waiting for device".
Click to expand...
Click to collapse
still says "waiting for device" in the terminal.
also, windows still comes up with "usb unrecognized" message at the bottom right of my screen.
What's next?
Thanks for joining to help, soupmagnet
Okay rerun the driver.bat packaged with kfu then plug the device in see if it comes up in device manager.
Thepooch said:
Okay rerun the driver.bat packaged with kfu then plug the device in see if it comes up in device manager.
Click to expand...
Click to collapse
Still doesn't show up. (It also occasionally crashes my mac system when I plug the kindle in now :/ )
If I get a factory cable, will that likely solve this easily?
Well I'm not a Mac person but it's far better with drivers than Windows ever will be maybe google how to setup and and fastboot on a Mac and go from there. Download install breakdroid that should be accompanied with the drivers.
Thepooch said:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Thepooch said:
Well I'm not a Mac person but it's far better with drivers than Windows ever will be maybe google how to setup and and fastboot on a Mac and go from there. Download install breakdroid that should be accompanied with the drivers.
Click to expand...
Click to collapse
Got it! Using Breakdroid, I was able to capture the Kindle as it powered on. I believe my main problem was that there was a significant enough delay in connecting the Kindle via USB to the Windows Virtual Machine, that the ADB couldn't access it in time to capture it. Or whatever.
Solution: I used BreakDroid on my Mac. Turned the kindle off, then back on while Breakdroid was waiting for my device to perform Step 1 on Breakdroid's Kindle Tools. Then it immediately captured the Kindle when I powered it on. Went through the steps on Breakdroid, and it's working with bootloader and recovery
Works great! Have all my stuff back. And...it's rooted
THANKS FOR ALL YOUR HELP, GUYS!
EDIT: Now how do I install Google Play?
Hello,
Still working on my kids KF2. I got root, yeah! However at some point it updated to 10.3. Can someone point me in the right direction for getting its bootloader downgraded from a Windows 7 x64 platform? I can use a RHEL box at work if I really need to, but rather not.
so I get CM on this thing
thanks!
http://forum.xda-developers.com/showthread.php?t=2100963
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2100963
Click to expand...
Click to collapse
Does that mean I need a fastboot cable? I can make one no problem... but better if I don't have to
I ran: fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin, device off, it said waiting for device, but then it just boot up to the lock screen.
Sorry im a little confused on this one.
Code:
adb shell su -c "reboot bootloader"
soupmagnet said:
Code:
adb shell su -c "reboot bootloader"
Click to expand...
Click to collapse
Thanks for the info.. but im gonna be a noob here...
What do I do with that? run it from command prompt? with the device booted, not booted? before the fastboot -i 0x1949 flash bootloader ?
s10010001 said:
Thanks for the info.. but im gonna be a noob here...
What do I do with that? run it from command prompt? with the device booted, not booted? before the fastboot -i 0x1949 flash bootloader ?
Click to expand...
Click to collapse
That is a command to be run from the command lint to put your device in fastboot mode without a factory cable. Once your device is in fastboot, then you can continue with the fastboot commands. If you are in fastboot and you still get "<waiting for device>", you need to make sure your drivers are configured properly.
soupmagnet said:
That is a command to be run from the command lint to put your device in fastboot mode without a factory cable. Once your device is in fastboot, then you can continue with the fastboot commands. If you are in fastboot and you still get "<waiting for device>", you need to make sure your drivers are configured properly.
Click to expand...
Click to collapse
Thanks a ton! Ill give it a try tonight when I get home.
In theroy:
Fastboot with that command
Install downgraded bootloader
install TWRP
Install rom
enjoy...
s10010001 said:
Thanks a ton! Ill give it a try tonight when I get home.
In theroy:
Fastboot with that command
Install downgraded bootloader
install TWRP
Install rom
enjoy...
Click to expand...
Click to collapse
Close
Make backups
Fastboot with that command
Install downgraded bootloader
Install 2nd bootloader
Install TWRP & kernel(boot.img)
Factory Reset in TWRP
Install rom
enjoy..
Enjoyment is relative, of course
Well bummer. I got into fast boot. I think I got a backup. But on a reboot, it just looks the Orange Kindle Fire logo...
Now I really need a fast boot cable hua? Assuming a fastboot cable will let me fast boot. Once there again what can I do?
s10010001 said:
Well bummer. I got into fast boot. I think I got a backup. But on a reboot, it just looks the Orange Kindle Fire logo...
Now I really need a fast boot cable hua? Assuming a fastboot cable will let me fast boot. Once there again what can I do?
Click to expand...
Click to collapse
Hold the power button to turn your device off, enter the following command and boot it up again...
Code:
fastboot -i 0x1949 getvar product
...dose your device boot into fastboot? If so, start over and try again. If not, you'll need a factory cable.
soupmagnet said:
Hold the power button to turn your device off, enter the following command and boot it up again...
Code:
fastboot -i 0x1949 getvar product
...dose your device boot into fastboot? If so, start over and try again. If not, you'll need a factory cable.
Click to expand...
Click to collapse
it was worth a shot, but no Ill be needing that cable
When I make one, will it just boot into fastboot upon boot if the cable is in? Just pins 1 and 4 right?
s10010001 said:
it was worth a shot, but no Ill be needing that cable
When I make one, will it just boot into fastboot upon boot if the cable is in? Just pins 1 and 4 right?
Click to expand...
Click to collapse
If your device is completely off, and you plug a working factory cable in, it will boot into fastboot.
Info on pin layout
You need a 5-pin usb cable BTW.
Cool, thanks for all the help.
One more question. Do you have one of the guides you specially recommend once I do get the cable made?
s10010001 said:
Cool, thanks for all the help.
One more question. Do you have one of the guides you specially recommend once I do get the cable made?
Click to expand...
Click to collapse
Were you able to successfully backup your boot, recovery, and system partitions before everything went wrong?
No I was looking at it, I think it errored out.
I can just fastboot with cable and start over with hash's guide?
s10010001 said:
No I was looking at it, I think it errored out.
I can just fastboot with cable and start over with hash's guide?
Click to expand...
Click to collapse
Possibly, but depending on where things went wrong, you may have to restore first. Do you know what the error was?
Something like this max-download-size: 486,539,264
s10010001 said:
Something like this max-download-size: 486,539,264
Click to expand...
Click to collapse
You are supposed to save your partition images with the 'dd' command using the shell:
Hashcode said:
STEP 1. Backup your stock partitions to your own HD for later if you need disaster recovery:
Code:
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img" # This will take a few minutes
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img # This will take a few minutes
Take those files and put them somewhere safe.
Click to expand...
Click to collapse
You won't see a "max-download-size" message unless you are using fastboot to flash those images.
ohh ok.. so I dont have a backup
But the fastboot cable is working! Im in fastboot
keeps telling me no device found
do I want the "Android ADB Interface" or "Andriod Composite ADB Interface"?
Also once booted in to fastboot with the cable, do I just leave the cable or put the stock cable back in? Shouldnt matter... but just want to make sure.
I have been researching and trying various things for a week now, including soupkit.
Every partition on the Kindle had been wiped, so there is no OS installed.
I am able to boot my kindle into fastboot mode using fastboot -i 0x1949 oem idme bootmode 4002 which lets me flash a bootloader, firefirefire 1.4a and a recovery TWRP 2.6
However nothing I do will get the kindle to register over USB unless its in fastboot mode. I have been in linux and it does not even detect the kindle when it is plugged in. Therefore I can not mount the USB drive and put a factory image on the sdcard to flash through recovery nor can I push a factory image with adb to the sdcard to flash through recovery.
It seems my only option would be to flash a system.img through the fastboot mode which i am still able to enter, but I am unable to find a good copy of stock 6.3.2 or any other system.img that would able my kindle to boot again or possibly re-enable the ability to use adb or mount the usb drive. Hopefully someone could point me in that direction or give some other suggestion.
Maybe I'm missing something, but why can't you boot into recovery (by pressing the power button while booting to get the Recovery option) , connect via a standard USB cable (not a factory cable) from the KF to your computer, and then use 'adb push <pathname> /sdcard/' to copy to the KF whatever ROM you want to install, and then install it using the TWRP commands on the KF?
aarons510 said:
Maybe I'm missing something, but why can't you boot into recovery (by pressing the power button while booting to get the Recovery option) , connect via a standard USB cable (not a factory cable) from the KF to your computer, and then use 'adb push <pathname> /sdcard/' to copy to the KF whatever ROM you want to install, and then install it using the TWRP commands on the KF?
Click to expand...
Click to collapse
I can boot into recovery, but when I plug in a USB cable at that point, the kindle does not register on a computer. Like I said, I even tried in Linux using the command lsusb, it does not show, it will only be on the list if in fastboot mode.
Maverickwolf said:
I can boot into recovery, but when I plug in a USB cable at that point, the kindle does not register on a computer. Like I said, I even tried in Linux using the command lsusb, it does not show, it will only be on the list if in fastboot mode.
Click to expand...
Click to collapse
The answers to the following questions are probably all in the affirmative, but, just to be sure, I'll ask anyway:
Does your computer recognize other devices when they are plugged into the same cable?
Have you tried other cables?
Does the Kindle work as it should when in recovery, aside from not being recognized by your computer?
aarons510 said:
The answers to the following questions are probably all in the affirmative, but, just to be sure, I'll ask anyway:
Does your computer recognize other devices when they are plugged into the same cable?
Have you tried other cables?
Does the Kindle work as it should when in recovery, aside from not being recognized by your computer?
Click to expand...
Click to collapse
My computer does recognize other devices as well as the kindle in fastboot mode.
I have tried different cables as well.
The kindle functions in recovery aside from not being recognized. I have also tried flashing older versions of TWRP and CWM and no detection on those either.
Hi,
I've wrote some days ago this post
Hi there!! First of all thanks for the explanation! I've try to understand in wich position is my KF.... but nothing...
A little bit of history:
KF HXD 8,9
I've rooted the KF, after that I've install Safestrap Recovery APK and successfully flash/install 2 different rom into 2 different rom slot not in the stock rom(backed up in the device).
Great! I've tested both and chose one running well. I've chose to delete one and give to the one more space... 7GB.
Well after the installation I've reboot the device........ white fix logo (all white) on screen.... after some reboot pushing the power button (I don't how) it show a screen where I can chose restore device or reboot. I've restored the device to the default factory...
Well now I really don't know what can I do. The command adb devices doesn't recognize any device. Fastboot: ./fastboot getvar product is waiting for the device...
p.s. Only one positive thing is when I plug the KF with the usb in my MAC start Android Transfer Tool.
Any help or suggestions are welcome.
Thanks.
sorry for the bad english
Click to expand...
Click to collapse
and they move me to this section....
Well now I really don't know what I have to do. And in wich state is my kf... brick/no brick
Plase can you suggest me the right way?
Now I'm using an ubuntu 12.04 as pc, there are some tool or script that can I run into ubuntu?
Thanks.
You should be able to get it into fastboot.
Make sure the tablet is off then run the command.
fastboot -i 0x1949 getvar product
Then turn it back on
macman005 said:
You should be able to get it into fastboot.
Make sure the tablet is off then run the command.
fastboot -i 0x1949 getvar product
Then turn it back on
Click to expand...
Click to collapse
I've run the fastboot command from the platform-tools folder into the Android sdk and...
still < waiting for device >
I think it might be a driver issue. If you open the driver manager does something flash on the screen when the tablet turns on?
macman005 said:
I think it might be a driver issue. If you open the driver manager does something flash on the screen when the tablet turns on?
Click to expand...
Click to collapse
with the mac it's start Android Transfer tool but it say that it can't find the device, into ubuntu 12.40 nothing.