Related
Here's my issue:
I create a folder on my Nexus ".A." primarlily because it'd be first up top, well I realized after I wiped all data/cache/system that my phone doesn't recognize this folder with the ROM I have in it via Clockwork. So I reboot my phone, stuck in Google boot logo. I'm able to get into Fastboot mode, and my phone shows up when I ./fastboot-mac devices
However, adb devices lists nothing, and adb shell says device not found.
I'm trying to push this AOKP zip file to the phone so that I can boot back into recovery and flash it.
Any ideas on what I need to do to make this happen?
MacPro:android-sdk Home$ fastboot flash boot boot.img
sending 'boot' (3776 KB)...
OKAY [ 0.428s]
writing 'boot'...
OKAY [ 0.257s]
finished. total time: 0.685s
MacPro:android-sdk Home$ adb push update.zip /sdcard/update.zip
error: device not found
boot.img was taken from AOKP 38
i then changed the name of the rom zip to update and tried to adb push it and received this error. :/
followed these instructions :
Android 4.0.2 factory images
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
fastboot reboot-bootloader
got past the google start up screen and it looks like i'm now boot looping on the stock nexus boot screen
fastboot flash'd clockwork mod recovery, cleared data system wiped
now i'm stuck on google boot, however this time instead of just sitting on the google logo it's rebooting itself every 10 seconds and vibrating each time.
pulled battery, rebooted, same thing.
letting it sit and continue to do this.
phone still not showing up in adb devices
Just in case you didn't know, adb doesn't work when you're in bootloader mode, only in recovery mode and when you're booted will adb work. Regarding your boot looping problem, I'm not too sure but are you flashing the correct image and is it not corrupted? Check the hash for the zip and compare it.
Hi, it's the second time i try to install TWRP recovery v2.2.0+ and each time it keeps getting stuck at the boot with the message
Bootloader version 0.03.06-ics unlock mode
Booting recovery kernel image.
Waited for more than 10 minutes and nothing happened.
i can reboot and and log into ics normally i just don't have access to a recovery.
---I want to know how to properly install twrp , what went wrong and how to fix it.:
the script:
@echo off
cls
echo reboot to bootloader
adb wait-for-device
adb shell su -c "mount -o remount, rw /system/ && mv /etc/install-recovery.sh /etc/install-recovery.offsh;"
adb reboot-bootloader
echo flashing recovery
fastboot flash recovery recovery-A100ICS-TWRP-2.2.0.img
echo -
echo -
fastboot reboot
adb wait-for-device
echo check the recovery XXXXXXXXXXXXXXXX--This is where i'm stuck at.
adb reboot recovery
MY SETUP:
ROM FLEX-A100-REAPER-RELIX_Rev2 , OC A 1500, CWM was working ok.
WIN64
I would suggest downloading the image again, then trying the install script after you delete the current image with the newly downloaded image.
If you feel OK using a terminal its pretty straight forward
Open a terminal and CD to the folder with adb fast boot and recovery image
Example
cd c:\recovery
If powered on type
adb reboot bootloader
After it boots into download protocol type
fastboot erase recovery
fastboot flash recovery twrp.img
Twrp.IMG being whatever the file name is.
fastboot reboot
Let it boot into android then
adb reboot recovery
See what it does.
Tapatalked from my Galaxy S II.
a100/openrecovery-twrp-2.2.2.1-a100.img
renamed to recovery.img and flashed properly.
Same problem. Can it be related to the bootloader number ?
IamModeste said:
a100/openrecovery-twrp-2.2.2.1-a100.img
renamed to recovery.img and flashed properly.
Same problem. Can it be related to the bootloader number ?
Click to expand...
Click to collapse
That's the only boot loader we can flash on so that's fine. Did you download the image again?
Tapatalked from my Galaxy S II.
pio_masaki said:
Did you download the image again?
Click to expand...
Click to collapse
yes i did , donloaded openrecovery-twrp-2.2.2.1-a100.img,
renamed to recovery.img and flashed without any problem.
I redownloaded and flashed it again,
To no avail...
Nothing else to suggest ? I'd like to use a touch enabled recovery.
Sent from the usual suspects.
IamModeste said:
I redownloaded and flashed it again,
To no avail...
Nothing else to suggest ? I'd like to use a touch enabled recovery.
Sent from the usual suspects.
Click to expand...
Click to collapse
Did you erase recovery before flashing?
Theonew said:
Did you erase recovery before flashing?
Click to expand...
Click to collapse
Agreed.
I would try again make sure to: 'fastboot erase recovery', then 'fastboot flash recovery recoveryname.img' (make sure it's recovery [space] then the img name).
You can also try Zeronull's 2.1.1/2.2.0 and Linuxsociety's 2.2.2.0. It could be a bad upload of the 2.2.2.1 img
Answer
There's a file in /system/etc/ called install_recovery.sh that may need to be deleted for the custom recovery to stick. You need root to remove it.
sounds like you may need to start fresh.
Use fastboot to erase the system, boot, recovery and cache, perform a fastboot -w and then install the new recovery and ROM. Erasing the system will kill that recovery file from above.
Let me know. There are a couple of other options that I can think of.
---------- Post added at 06:48 AM ---------- Previous post was at 06:32 AM ----------
Here is what it should look like in fastboot on the command prompt yours will be different of course because mine is setup differently. But basically load up fastboot on windows or whatever you use and first erase the recovery then run fastboot -w and then flash the twrp recovery image and finally fastboot reboot. After reboot hold down volume button and enter recovery as usual. Should work then. My explanation is above. It's the install_recovery.sh file fastboot -w takes care of it! Sorry for bumping and old thread. But it doesn't look like it ever got solved.
Code:
C:\>C:/android/fastboot.exe erase recovery
erasing 'recovery'... OKAY [ 0.733s]
finished. total time: 0.734s
C:\>C:/android/fastboot.exe -w
erasing 'userdata'... OKAY [ 5.480s]
erasing 'cache'... OKAY [ 2.052s]
finished. total time: 7.533s
C:\>C:/android/fastboot.exe flash recovery C:/recoverytwrp.img
sending 'recovery' (4410 KB)... OKAY [ 0.491s]
writing 'recovery'... OKAY [ 0.255s]
finished. total time: 0.746s
C:\>C:/android/fastboot.exe reboot
rebooting...
finished. total time: 0.001s
I'm confused.... I'm following all the instructions using the toolkit v10.
I was able to unlock the bootloader without an issue, but when it comes to rooting, I'm having problems.
I use option 16 for the build, then option 4 to root. In the fastboot screen, the bottom Fastboot status says FAILInvalid Command as soon as it pulls up, then it goes to "reboot" after the 30 second wait.
It doesn't reboot automatically, so I press the power button to reboot it myself. then it reboots and then goes back into fastboot with the fail invalid command. Then this comes up:
downloading 'boot.img'
FAILED (remote: Invalid Command)
finished. total time: 0.006s
Waiting for device.
I'm at a loss. I feel like last time did this, I had to get the factory image and the boot.img file from somewhere and place them in the folders within the c:/galaxy nexus toolkit folder.
Any help would be greatly appreciated!
Thanks,
Nick
put on your big boy pants and root your phone this way:
http://forum.xda-developers.com/showthread.php?t=1529058
I have tried that... i get a similar message:
sending 'recovery' (5990 KB)
FAILED (remote: Invalid Argument)
finished. total time: 0.006s
then the fastboot status on the phone changes to "download 005d9800"
not sure what to make of that either.
is the cwm/twrp image actually named recovery? and is it in the fastboot.exe directory?
are you typing the command correctly? ( fastboot flash recovery nameofrecovery.img
It's in the same "platform-tools" folder that the fastboot.exe file is in. it's called recovery-clockwork-touch-6.0.2.3-toro.img, so i type fastboot flash recovery recovery-clockwork-touch-6.0.2.3-toro.img and hit enter. That's what made sense to me in reading that post.
waldo22 said:
It's in the same "platform-tools" folder that the fastboot.exe file is in. it's called recovery-clockwork-touch-6.0.2.3-toro.img, so i type fastboot flash recovery recovery-clockwork-touch-6.0.2.3-toro.img and hit enter. That's what made sense to me in reading that post.
Click to expand...
Click to collapse
Yep that's it
Sent from my Galaxy Nexus using Tapatalk 2
I'm guessing you mean that that's the correct way to do it and not, "yep that's you're problem." Any ideas where to go from there?
crazy... I switched to a different computer, and used the most up to date pdanet drivers, and it's going like a champ.
Hi, my kf2 is stucked at fastboot, i'm not able to boot into recovery or system, i have succesfully installed fff-1.4a using a factory cable (because it was bricked with the stock bootloader) and have installed the otter2-twrp-2.4.4.0-recovery.img from hashcode..
It boots and i see the blue kindle logo, and have a menu, but when i select recevery it just turns on the amber light and stays there, i have left it for about 5 minutes waiting to see if it get to revery with no luck.
I tried this:
Code:
sudo fastboot -i 0x18d1 getvar product
< waiting for device >
product: kindle
finished. total time: 0.000s
sudo fastboot -i 0x18d1 oem format
...
OKAY [ 0.068s]
finished. total time: 0.068s
Then
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
< waiting for device >
sending 'boot' (243 KB)...
OKAY [ 0.065s]
writing 'boot'...
OKAY [ 0.051s]
finished. total time: 0.115s
sudo fastboot reboot
rebooting...
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
< waiting for device >
sending 'boot' (243 KB)...
OKAY [ 0.065s]
writing 'boot'...
OKAY [ 0.051s]
finished. total time: 0.115s
It succeed as you can see, it has the fff bootloader and twrp recovery is installed!!
Then i tried
Code:
sudo fastboot -i 0x18d1 flash zip cm-10.1-20130704-NIGHTLY-otter2.zip
< waiting for device >
sending 'zip' (155204 KB)...
OKAY [ 38.806s]
writing 'zip'...
FAILED (remote: partition does not exist)
finished. total time: 38.813s
It seem like a partition table problem maybe because i'm trying to install Cyanogenmod and not a stock image...
I think maybe i must reformat the partitions but i only have access to fastboot and i have read the documentation of Android Fastboot in OmapPedia but i'm not sure it's a "generic" information and don't want to mess up things more.
I have read many trheads in the forum but all of them use adb and there's not a thread with instructions about it..
Or maybe i need to flash all the images (system, kernel, etc..) with fastboot but i don't know where to get it, the main problem is that i'm not able to boot into recovery and maybe that point to the real problem
Any help is appreciated !!
Thank's
You can't write CyanogenMod from fast boot.
Sounds like somewhere in there you formatted the system partition. You need the stack file on the system partition in order to boot into recovery.
Restore to stock using fast boot and try again.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
How?
mindmajick said:
You can't write CyanogenMod from fast boot.
Sounds like somewhere in there you formatted the system partition. You need the stack file on the system partition in order to boot into recovery.
Restore to stock using fast boot and try again.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Maybe it is the problem as fastboot oem format seems to do the job...
I have downloaded the stock update-kindle-6.3.2_D01E_4110520.bin, please can you point to the thread explainig how to do that using fastboot or it's just as easy as rename the file to update.zip and flash it directly?
Edited: also i'm not completely sure it's a kf2 and can't get a hint on how to discover it without knowing the is version :banghead: I've looked one the motherboard and is a MB0090 F3F.
I've downloaded the stock bin for the kf2 too...
Thank' for your quick reply
Well. If you have a kf2... The update you downloaded is wrong. IT'S FOR THE ORIGINAL KINDLE FIRE.
Without knowing what device u have u better slow down a sec. Any advice i give COULD permabrick u of you're on the wrong device.
What color was the BOX it came in? What is the model# on the back? (Same for kf1 AND 2 BUT NOT THE KF HD 7" OR 8").
Be advised- this device is EASY TO BRICK. BE CAREFUL.
--
Sent from my mind to your screen.
---------- Post added at 02:48 AM ---------- Previous post was at 02:40 AM ----------
Also. The correct update file wont work either.
You can only flash image files from fastboot.
--
Sent from my mind to your screen.
It's apparent you have a KF1 and not a KF2. The command "fastboot -i 0x18d1..." would not work on the KF2 because it still has the stock bootloader (unless something miraculous happened while I was AFK). The stock bootloader has a VID of 1949, and will not answer to commands using a different VID. 18d1 is Goggle's VID and is indicative of having FFF installed (KF1 only).
BTW, the "-i 0x18d1" part is completely unnecessary on FFF.
That's not your biggest problem though....
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
That command is completely wrong. What you're doing there is flashing the bootloader (fff-u-boot_v1.4a.bin) to the boot (kernel) partition. Obviously, there is no way that could possibly would work out for you. After the "fastboot" portion of the command, you need to specify what you want done with the image in question: flash or boot. "Flash" is persistent, "boot" is for one boot only. In the next part of the command, you need to specify which partition the image in question goes to; bootloader, recovery, boot, etc.
What you need to do is get an actual recovery.img and flash it to your recovery partition before you can even think of accessing said recovery to flash a ROM and get your device working again.
soupmagnet said:
It's apparent you have a KF1 and not a KF2. The command "fastboot -i 0x18d1..." would not work on the KF2 because it still has the stock bootloader (unless something miraculous happened while I was AFK). The stock bootloader has a VID of 1949, and will not answer to commands using a different VID. 18d1 is Goggle's VID and is indicative of having FFF installed (KF1 only).
BTW, the "-i 0x18d1" part is completely unnecessary on FFF.
That's not your biggest problem though....
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
That command is completely wrong. What you're doing there is flashing the bootloader (fff-u-boot_v1.4a.bin) to the boot (kernel) partition. Obviously, there is no way that could possibly would work out for you. After the "fastboot" portion of the command, you need to specify what you want done with the image in question: flash or boot. "Flash" is persistent, "boot" is for one boot only. In the next part of the command, you need to specify which partition the image in question goes to; bootloader, recovery, boot, etc.
What you need to do is get an actual recovery.img and flash it to your recovery partition before you can even think of accessing said recovery to flash a ROM and get your device working again.
Click to expand...
Click to collapse
Well you are completely right!! Didn't realize I was flashing it to the kernel partition, I bought this on eBay and it was already bricked, when I used the factory cable first time I got a lab26 device, and it was a 1949 so, if I'm right it's a kf2.
I've already flashed a twrp recovery but it won't boot.. I'll try sintering else and post the results here
Sent from my SPH-D710 using xda premium
LUC4X said:
when I used the factory cable first time I got a lab26 device, and it was a 1949 so, if I'm right it's a kf2.
I've already flashed a twrp recovery but it won't boot.. I'll try sintering else and post the results here
Click to expand...
Click to collapse
No. The stock bootloader on all generations and variants of Kindle Fires have vendor IDs of 1949. The fact that your device responds to the "fastboot -i 0x18d1..." clearly means you have a custom bootloader installed in its place. If you have an actual custom bootloader installed (not 2nd bootloader) then you clearly cannot possibly have a KF2.
In this thread, you say you have installed recovery twice, but the information given seems to suggest otherwise.
So to try and get to the root of the problem, what is the exact command you used to install custom recovery, and what custom recovery (version) did you install?
Glad you are here soupmagnet!
I didn't even look at the commands he was using but i definitely learned stuff from your posts. Thanks again
--
Sent from my mind to your screen.
Commands used
soupmagnet said:
No. The stock bootloader on all generations and variants of Kindle Fires have vendor IDs of 1949. The fact that your device responds to the "fastboot -i 0x18d1..." clearly means you have a custom bootloader installed in its place. If you have an actual custom bootloader installed (not 2nd bootloader) then you clearly cannot possibly have a KF2.
In this thread, you say you have installed recovery twice, but the information given seems to suggest otherwise.
So to try and get to the root of the problem, what is the exact command you used to install custom recovery, and what custom recovery (version) did you install?
Click to expand...
Click to collapse
Sorry guys i was out of town...
These are the commands (bootloader & recovery) i've used till now:
sudo fastboot -i 0x18d1 flash bootloader fff-u-boot_v1.4a.bin
< waiting for device >
sending 'bootloader' (243 KB)...
OKAY [ 0.065s]
writing 'bootloader'...
OKAY [ 0.083s]
finished. total time: 0.148s
sudo fastboot -i 0x18d1 flash recovery otter2-twrp-2.4.4.0-recovery.img
sending 'recovery' (8153 KB)...
OKAY [ 2.042s]
writing 'recovery'...
OKAY [ 2.705s]
finished. total time: 4.748s
Click to expand...
Click to collapse
Also tryed the twrp from teamw's site in both versions (otter & blaze) just to make sure, by issuing the following commands:
sudo fastboot -i 0x18d1 flash recovery openrecovery-twrp-2.5.0.0-blaze.img
< waiting for device >
sending 'recovery' (6144 KB)...
OKAY [ 1.540s]
writing 'recovery'...
OKAY [ 1.514s]
finished. total time: 3.054s
Click to expand...
Click to collapse
With this, when i reboot and select the recovery it turns on the amber light for 2 seconds and shuts down.
Then when i install the other recovery version (blaze from teamw):
sudo fastboot -i 0x18d1 flash recovery openrecovery-twrp-2.5.0.0-otter.img
< waiting for device >
sending 'recovery' (6144 KB)...
OKAY [ 1.540s]
writing 'recovery'...
OKAY [ 0.684s]
finished. total time: 2.224s
Click to expand...
Click to collapse
When select recovery i get the same result: amber light for 2 seconds and turns off.
And with hashcode otter2-twrp-2.4.4.0-recovery.img:
sudo fastboot -i 0x18d1 flash recovery otter2-twrp-2.4.4.0-recovery.img
< waiting for device >
sending 'recovery' (8153 KB)...
OKAY [ 2.042s]
writing 'recovery'...
OKAY [ 0.894s]
finished. total time: 2.937s
Click to expand...
Click to collapse
It hangs on amber light and i have to manually turn it off holding the power buttom for 10 seconds...
So you think it is a kf1 based on the device id?, it shows that id after i installed the fff-u-boot_v1.4a.bin from hashcode that i intended for the kf2...
Well, based on that i have installed a kf1 bootloader:
Downloaded the Kindle Fire Utility v0.9.9.zip from http://forum.xda-developers.com/showthread.php?t=2192818
Unzipped it (as i'm GNU/Linux)
"Grepped" recursively till find the web address to download files from
Downloaded fff-u-boot_v1.4a.bin
Downloaded openrecovery-twrp-2.4.4.0-blaze.img
Followed the install procedure
Same result !!, still can't get it to boot into recovery...
Really i hope someone here can point me to the right direction to fix this tablet, can't figure out what's wrong with kf(?)
LUC4X said:
So you think it is a kf1 based on the device id?, it shows that id after i installed the fff-u-boot_v1.4a.bin from hashcode that i intended for the kf2...
Well, based on that i have installed a kf1 bootloader:
Downloaded the Kindle Fire Utility v0.9.9.zip from http://forum.xda-developers.com/showthread.php?t=2192818
Unzipped it (as i'm GNU/Linux)
"Grepped" recursively till find the web address to download files from
Downloaded fff-u-boot_v1.4a.bin
Downloaded openrecovery-twrp-2.4.4.0-blaze.img
Followed the install procedure
Same result !!, still can't get it to boot into recovery...
Really i hope someone here can point me to the right direction to fix this tablet, can't figure out what's wrong with kf(?)
Click to expand...
Click to collapse
Lets get a few things clear right off the bat. The file named fff-u-boot_v1.4a.bin is the custom bootloader for the KF1. The bootloader flashed in the KF2 2nd bootloader installation is named otter2-u-boot-prod-10.2.4.bin. If you flash the fff-u-boot_v1.4a.bin (FFF1.4a) onto a KF2, you would end up with something that is slightly less useful than a doorstop.
Why you re-installed it is a mystery to me. You already had FFF1.4a installed. I know this (as I explained earlier) by the fact that your commands, using the "-i 0x18d1" switch, were successful. If you had a stock bootloader, no commands containing that particular vendor ID would work at all. If you had a KF2, there is absolutely NO WAY you would have a device that responds to fastboot commands using "-i 0x18d1". Even with a modified KF2, with 2nd bootloader installed, the vendor ID would still be 1949 and all fastboot commands must include "-i 0x1949" or they will not work. You can confirm the fact that you have FireFireFire installed by entering a fastboot command without adding "i- 0x18d1". With FireFireFire (KF1 only), the commands will still work because it is unnecessary to specify the vendor ID.
That being said, I'm not entirely sure what's going on with TWRP using both "otter" and "blaze" for the board name (I think it has something to do with Goo Manager?), but anything you get from the TWRP website should work for the KF1 (for the time being at least). Anything you get from Hashcode will be for the 2nd generation KFs.
I would suggest, to avoid complicating things any further, that you download Cannibal Open Touch recovery, confirm that the MD5sums match after downloading, and flash it to recovery in fastboot. COTR only works for the KF1 (not made for the 2nd Generation devices yet) so there is "practically" no way you can get the wrong one. If that works and you still want to try TWRP, download the one for Blaze, check the MD5 (as you should with everything), and try flashing it in recovery again.
If you still can't get your device to boot into recovery, try the command again, but replace the word "flash" with the word "boot" and leave out the partition (i.e. 'fastboot boot openrecovery-twrp-2.4.4.0-blaze.img'). If the device boots into recovery, then you know you have the right one and you may have bad blocks in your recovery partition preventing it from booting, but you won't know for sure without checking a few things out first.
Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, but where can i get those files?
What do you think?
soupmagnet said:
Lets get a few things clear right off the bat. The file named fff-u-boot_v1.4a.bin is the custom bootloader for the KF1. The bootloader flashed in the KF2 2nd bootloader installation is named otter2-u-boot-prod-10.2.4.bin. If you flash the fff-u-boot_v1.4a.bin (FFF1.4a) onto a KF2, you would end up with something that is slightly less useful than a doorstop.
Why you re-installed it is a mystery to me. You already had FFF1.4a installed. I know this (as I explained earlier) by the fact that your commands, using the "-i 0x18d1" switch, were successful. If you had a stock bootloader, no commands containing that particular vendor ID would work at all. If you had a KF2, there is absolutely NO WAY you would have a device that responds to fastboot commands using "-i 0x18d1". Even with a modified KF2, with 2nd bootloader installed, the vendor ID would still be 1949 and all fastboot commands must include "-i 0x1949" or they will not work. You can confirm the fact that you have FireFireFire installed by entering a fastboot command without adding "i- 0x18d1". With FireFireFire (KF1 only), the commands will still work because it is unnecessary to specify the vendor ID.
That being said, I'm not entirely sure what's going on with TWRP using both "otter" and "blaze" for the board name (I think it has something to do with Goo Manager?), but anything you get from the TWRP website should work for the KF1 (for the time being at least). Anything you get from Hashcode will be for the 2nd generation KFs.
I would suggest, to avoid complicating things any further, that you download Cannibal Open Touch recovery, confirm that the MD5sums match after downloading, and flash it to recovery in fastboot. COTR only works for the KF1 (not made for the 2nd Generation devices yet) so there is "practically" no way you can get the wrong one. If that works and you still want to try TWRP, download the one for Blaze, check the MD5 (as you should with everything), and try flashing it in recovery again.
If you still can't get your device to boot into recovery, try the command again, but replace the word "flash" with the word "boot" and leave out the partition (i.e. 'fastboot boot openrecovery-twrp-2.4.4.0-blaze.img'). If the device boots into recovery, then you know you have the right one and you may have bad blocks in your recovery partition preventing it from booting, but you won't know for sure without checking a few things out first.
Click to expand...
Click to collapse
Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, i've found you uploaded a system.img to androidfilehost...
What do you think?
I posted that ages ago. I'm not even sure what device it's for.
Check the file size. If it's around 350MB go ahead. If it's closer to 500MB then it's probably for the HD.
I can't imagine why you couldn't load recovery using the 'fastboot boot recovery.img' command. Did you receive any errors when trying?
soupmagnet said:
I posted that ages ago. I'm not even sure what device it's for.
Check the file size. If it's around 350MB go ahead. If it's closer to 500MB then it's probably for the HD.
I can't imagine why you couldn't load recovery using the 'fastboot boot recovery.img' command. Did you receive any errors when trying?
Click to expand...
Click to collapse
There's not error message, this is the output:
Code:
sudo fastboot boot CannibalOpenTouch-v2.1_otter.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.394s]
booting...
OKAY [ 0.004s]
finished. total time: 1.398s
But it never boots up and stays off.
I'm seriously thinking it may be a hardware failure but i wont give up until i'm completely sure about it.. that's why i though i should reformat partitions at the first time but the fastboot oem format command "seems" to work, perhaps it takes very short time to execute 0.068s and it is a very short time, so i though maybe it isn't really formatting anything, is it a "normal time"?
Right now i'm downloading the file it's 380MB maybe something good could happen!!
I'll try the following and will post the results:
Code:
fastboot flash system system.img
fastboot erase userdata
fastboot erase cache
fastboot reboot
LUC4X said:
There's not error message, this is the output:
Code:
sudo fastboot boot CannibalOpenTouch-v2.1_otter.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.394s]
booting...
OKAY [ 0.004s]
finished. total time: 1.398s
But it never boots up and stays off.
I'm seriously thinking it may be a hardware failure but i wont give up until i'm completely sure about it.. that's why i though i should reformat partitions at the first time but the fastboot oem format command "seems" to work, perhaps it takes very short time to execute 0.068s and it is a very short time, so i though maybe it isn't really formatting anything, is it a "normal time"?
Right now i'm downloading the file it's 380MB maybe something good could happen!!
I'll try the following and will post the results:
Code:
fastboot flash system system.img
fastboot erase userdata
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
The command 'fastboot oem format' will only make sure the partition layout is stock, it does not format the partitions themselves. The information within the limits of the partitions will remain untouched, so it won't do you much good in this situation. The only way to properly format any partition is with recovery (or 'parted' which is usually run from recovery anyway). Your situation is rather unique because the "fastboot boot' command doesn't write anything to the recovery partition. It loads the disk image you choose, into active memory, as if your computer were a separate partition on which that image is stored. There shouldn't be any reason for it to not work properly.
Try to flash the system partition you downloaded and see how it goes. I would also suggest that you make absolutely sure the md5sums match before installing any image to your device, including the recovery images you downloaded before.
soupmagnet said:
The command 'fastboot oem format' will only make sure the partition layout is stock, it does not format the partitions themselves. The information within the limits of the partitions will remain untouched, so it won't do you much good in this situation. The only way to properly format any partition is with recovery (or 'parted' which is usually run from recovery anyway). Your situation is rather unique because the "fastboot boot' command doesn't write anything to the recovery partition. It loads the disk image you choose, into active memory, as if your computer were a separate partition on which that image is stored. There shouldn't be any reason for it to not work properly.
Try to flash the system partition you downloaded and see how it goes. I would also suggest that you make absolutely sure the md5sums match before installing any image to your device, including the recovery images you downloaded before.
Click to expand...
Click to collapse
Code:
sudo fastboot flash system system.img
sending 'system' (389120 KB)...
OKAY [ 97.308s]
writing 'system'...
OKAY [ 36.819s]
finished. total time: 134.131s
sudo fastboot erase userdata
erasing 'userdata'...
OKAY [116.935s]
finished. total time: 116.935s
sudo fastboot erase cache
erasing 'cache'...
OKAY [ 29.189s]
finished. total time: 29.189s
sudo fastboot reboot
rebooting...
finished. total time: 0.000s
Must be hardware, it's sad... if it where a SMD flash memory i would try to changed it but it's a tyni BGA chip...
Thank you very much for your help
I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.
soupmagnet said:
I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.
Click to expand...
Click to collapse
I'll try tonight !!
Sent from my SPH-D710 using xda premium
soupmagnet said:
I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.
Click to expand...
Click to collapse
./usb_fix_parts_and_install_fff_twrp
Loading FFF through USB...
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
Fixing partitions...
< waiting for device >
... OKAY
Installing x-loader...
sending 'xloader' (128 KB)... OKAY
writing 'xloader'... OKAY
Flash FFF...
sending 'bootloader' (211 KB)... OKAY
writing 'bootloader'... OKAY
Flash TWRP...
sending 'recovery' (5260 KB)... OKAY
writing 'recovery'... OKAY
Resetting bootmode to standard boot...
... OKAY
Loading TWRP...
downloading 'boot.img'... OKAY
booting... OKAY
Click to expand...
Click to collapse
Same as before, it won't reboot after sending the boot to recovery command and if try to get into recovery it turns off after an amber light..
LUC4X said:
Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, but where can i get those files?
What do you think?
Click to expand...
Click to collapse
At the begining i saw you were using "fastboot flash zip...." that's wrong command.. should be "fastboot flash update xxxx.zip"
so if you find the totally package, youcan use it.
also you has mixture the boot.img and bootloader.bin..
recovery is not needed if you can flash the right bootloader and boot.:laugh:
First off download the following files
KFHD_SRTv2.1- 8.1.4
img files
KFFirstAide32
or
KFFirstAide64
Extract KFFirstAide whichever version 32 or 64
Copy the folder to c:\
rename it to just KFFirstAide
add that to your path
Code:
;C:\KFFirstAide
Open the folder KFHD_SRTv2.1 then open images folder and copy system.img
paste it into the KFFirstAide folder
then open the two other img files you downloaded and paste them into the KFFirstAide folder as well
you should now have:
system.img
boot.img
recovery.img
All three files in the KFFirstAide folder
now
Open up an Administrative Command Prompt from within the KFFirstAide
go to the c:\ drive hold the shift key and right click on the folder KFFirstAide then select Open a command prompt here.
enter this command at the prompt
Code:
fastboot -i 0x1949 getvar product
it should come back with
< waiting for device >
If you are stuck at the red triangle screen
Make sure your device is totally off hold the power button for like 30 seconds until it turns off
next plug in your device with the usb cable
it should boot into fastboot mode
and show something like:
product: Jem-PVT-Prod-04
finished. total time: 0.009s
then type this command
Code:
fastboot -i 0x1949 devices
should come back with something like this
7EE400003C002FFF fastboot
then type this command
Code:
fastboot -i 0x1949 flash system system.img
should come back with something like
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 48.857s]
writing 'system'...
OKAY [ 60.331s]
finished. total time: 109.193s
next command
Code:
fastboot -i 0x1949 flash boot boot.img
should show something like
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.449s]
writing 'boot'...
OKAY [ 0.571s]
finished. total time: 1.024s
next command
Code:
C:\KFFirstAide>fastboot -i 0x1949 flash recovery recovery.img
should see something like
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 0.449s]
writing 'recovery'...
OKAY [ 0.565s]
finished. total time: 1.020s
these next commands take forever
Code:
fastboot -i 0x1949 erase cache
should come back with
erasing 'cache'...
OKAY [ 47.246s]
finished. total time: 47.250s
Code:
fastboot -i 0x1949 erase userdata
should come back with
erasing 'userdata'...
OKAY [2149.490s]
finished. total time: 2149.494s
and finally
Code:
fastboot reboot -i 0x1949
once it starts rebooting disconnect the USB cable
once you are back up and running you will be at version 8.1.4
to get to current version
you can use KFFirstAide and this time run
c:\KFFirstAide\RunMe.bat
use the option enable OTA updates
you will have to make sure ADB is enabled under security first on your kindle
once you enable OTA updates then unplug the USB
Next :
Charge the battery, and then connect to a Wi-Fi network.
Swipe down from the top of the screen, and then tap Sync.
The software update automatically downloads in the background and installs after the download is complete and the device is asleep.
Your Kindle Fire will restart during the software update. After the restart, the message “Kindle is updating” will appear on the screen and when it's finished you will be at the latest software version.
i ****ing love you, may you breed with amany and spread your DNA far and wide
Lamere said:
First off download the following files
KFHD_SRTv2.1- 8.1.4
img files
KFFirstAide32
or
KFFirstAide64
Extract KFFirstAide whichever version 32 or 64
Copy the folder to c:\
rename it to just KFFirstAide
add that to your path
Code:
;C:\KFFirstAide
Open the folder KFHD_SRTv2.1 then open images folder and copy system.img
paste it into the KFFirstAide folder
then open the two other img files you downloaded and paste them into the KFFirstAide folder as well
you should now have:
system.img
boot.img
recovery.img
All three files in the KFFirstAide folder
now
Open up an Administrative Command Prompt from within the KFFirstAide
go to the c:\ drive hold the shift key and right click on the folder KFFirstAide then select Open a command prompt here.
enter this command at the prompt
Code:
fastboot -i 0x1949 getvar product
it should come back with
< waiting for device >
If you are stuck at the red triangle screen
Make sure your device is totally off hold the power button for like 30 seconds until it turns off
next plug in your device with the usb cable
it should boot into fastboot mode
and show something like:
product: Jem-PVT-Prod-04
finished. total time: 0.009s
then type this command
Code:
fastboot -i 0x1949 devices
should come back with something like this
7EE400003C002FFF fastboot
then type this command
Code:
fastboot -i 0x1949 flash system system.img
should come back with something like
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 48.857s]
writing 'system'...
OKAY [ 60.331s]
finished. total time: 109.193s
next command
Code:
fastboot -i 0x1949 flash boot boot.img
should show something like
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.449s]
writing 'boot'...
OKAY [ 0.571s]
finished. total time: 1.024s
next command
Code:
C:\KFFirstAide>fastboot -i 0x1949 flash recovery recovery.img
should see something like
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 0.449s]
writing 'recovery'...
OKAY [ 0.565s]
finished. total time: 1.020s
these next commands take forever
Code:
fastboot -i 0x1949 erase cache
should come back with
erasing 'cache'...
OKAY [ 47.246s]
finished. total time: 47.250s
Code:
fastboot -i 0x1949 erase userdata
should come back with
erasing 'userdata'...
OKAY [2149.490s]
finished. total time: 2149.494s
and finally
Code:
fastboot reboot -i 0x1949
once it starts rebooting disconnect the USB cable
once you are back up and running you will be at version 8.1.4
to get to current version
you can use KFFirstAide and this time run
c:\KFFirstAide\RunMe.bat
use the option enable OTA updates
you will have to make sure ADB is enabled under security first on your kindle
once you enable OTA updates then unplug the USB
Next :
Charge the battery, and then connect to a Wi-Fi network.
Swipe down from the top of the screen, and then tap Sync.
The software update automatically downloads in the background and installs after the download is complete and the device is asleep.
Your Kindle Fire will restart during the software update. After the restart, the message “Kindle is updating” will appear on the screen and when it's finished you will be at the latest software version.
Click to expand...
Click to collapse
well this procedure saved me thanks but now using KFFaide i run diagnostics on my machine and test fastboot commands it sits at waiting for device and windows say device is not responding to simple fastboot commands check device manager no yellow triangles what to do now? I am rooted and have a 8.9 running 8.4.8 just completed recovery to 8.4.1 and updated to 8.4.8 b4 root flashed a new boot system and recovery image using command prompt but don't know why fastboot isn't working now????? Thanks
larryb1951 said:
well this procedure saved me thanks but now using KFFaide i run diagnostics on my machine and test fastboot commands it sits at waiting for device and windows say device is not responding to simple fastboot commands check device manager no yellow triangles what to do now? I am rooted and have a 8.9 running 8.4.8 just completed recovery to 8.4.1 and updated to 8.4.8 b4 root flashed a new boot system and recovery image using command prompt but don't know why fastboot isn't working now????? Thanks
Click to expand...
Click to collapse
had the same problem on windows 8.1 moved to my windows 7 box and it worked so 8.4.8 didn't kill fastboot at least
I get to.....
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 48.857s]
writing 'system'...
FAILED <remote: write partition>
Can anyone help?
Got my kindle back
Just want to vouch for this procedure. I followed it and got my Kindle back to its stock settings. It is 8.4.8. I was able to root it, but when I tried installing the bootloader, I must have done something wrong (wrong version maybe?). It hung on a reboot and just sat there with the orange Kindle Fire logo. Volume buttons did nothing. I was able to get it to go into fastboot, so I figured it wasn't a total loss. After trying about everything else, including using KFFirstAide just by itself, this procedure finally did the trick. I unrooted it now, and I don't think I'll make a second attempt.
what can i fix this...?
When i try to reboot my Kindle in fastboot mode, i see his logo for one second only and then the system restart normally...
Sorry for my bad english but i'm italian
I killed my KFHD8.9 by some naughty fastboot command.. Had twrp and some older CM rom but everything was buggy so I was trying to update when I did something I shouldn't have apparently (I think the last command was a fastboot command before everything died). The kindle won't boot up, no screen, nothing. It just heats up if you connect it to charge is all I can tell.
I downloaded everything per instructions in this thread but after the first fastboot command nothing happens it just stays at "< Waiting for device >". Also, 'adb devices' doesn't report anything connected. All my other devices connect fine. I have also pressed the power button for 30s to make sure the kindle is off prior to connecting for fastboot command...
Can this be fixed? Thanks!
mrgv said:
I killed my KFHD8.9 by some naughty fastboot command.. Had twrp and some older CM rom but everything was buggy so I was trying to update when I did something I shouldn't have apparently (I think the last command was a fastboot command before everything died). The kindle won't boot up, no screen, nothing. It just heats up if you connect it to charge is all I can tell.
I downloaded everything per instructions in this thread but after the first fastboot command nothing happens it just stays at "< Waiting for device >". Also, 'adb devices' doesn't report anything connected. All my other devices connect fine. I have also pressed the power button for 30s to make sure the kindle is off prior to connecting for fastboot command...
Can this be fixed? Thanks!
Click to expand...
Click to collapse
Try holding down the power button only for 2 minutes. Right around the 90 second to 120 second point, the device should reboot.
Damocles66 said:
Try holding down the power button only for 2 minutes. Right around the 90 second to 120 second point, the device should reboot.
Click to expand...
Click to collapse
Sry about the delay.. I was counting on an email notification but never got one.. Anyway.
Tried it several times and this didn't work. The tablet doesn't boot up with this 2min+ power button press. Anyone have any other ideas please?
KatanAlive said:
what can i fix this...?
When i try to reboot my Kindle in fastboot mode, i see his logo for one second only and then the system restart normally...
Sorry for my bad english but i'm italian
Click to expand...
Click to collapse
Not sure what Kindle you have since you did not say.
The HD Kindles as far as I know will not boot into fastboot using commands so, your is normal.
Regards
---------- Post added at 07:31 AM ---------- Previous post was at 07:26 AM ----------
mrgv said:
Sry about the delay.. I was counting on an email notification but never got one.. Anyway.
Tried it several times and this didn't work. The tablet doesn't boot up with this 2min+ power button press. Anyone have any other ideas please?
Click to expand...
Click to collapse
I am pretty sure your tablet is not recoverable depending on what fastboot commands you were trying when it stopped booting.
Do you remember what you were attempting to do?
If an incorrect non-signed partition was flashed to the tablet (e.g., from some other Kindle model), the tablet will be bricked.
If the wrong image was flashed to the bootloader partition, you are also bricked since the bootloader is key to turning on the tablet.
If your tablet is warm when plugged in, it means it charges at least.
Since the tablet will not turn on, or get into fastboot using the command line on your PC, there is nothing else to do.
The 8.9 tablet does not support the use of a fastboot cable.
Lamere said:
First off download the following files
KFHD_SRTv2.1- 8.1.4
img files
KFFirstAide32
or
KFFirstAide64
Extract KFFirstAide whichever version 32 or 64
Copy the folder to c:\
rename it to just KFFirstAide
add that to your path
Code:
;C:\KFFirstAide
Open the folder KFHD_SRTv2.1 then open images folder and copy system.img
paste it into the KFFirstAide folder
then open the two other img files you downloaded and paste them into the KFFirstAide folder as well
you should now have:
system.img
boot.img
recovery.img
All three files in the KFFirstAide folder
now
Open up an Administrative Command Prompt from within the KFFirstAide
go to the c:\ drive hold the shift key and right click on the folder KFFirstAide then select Open a command prompt here.
enter this command at the prompt
Code:
fastboot -i 0x1949 getvar product
it should come back with
< waiting for device >
If you are stuck at the red triangle screen
Make sure your device is totally off hold the power button for like 30 seconds until it turns off
next plug in your device with the usb cable
it should boot into fastboot mode
and show something like:
product: Jem-PVT-Prod-04
finished. total time: 0.009s
then type this command
Code:
fastboot -i 0x1949 devices
should come back with something like this
7EE400003C002FFF fastboot
then type this command
Code:
fastboot -i 0x1949 flash system system.img
should come back with something like
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 48.857s]
writing 'system'...
OKAY [ 60.331s]
finished. total time: 109.193s
next command
Code:
fastboot -i 0x1949 flash boot boot.img
should show something like
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.449s]
writing 'boot'...
OKAY [ 0.571s]
finished. total time: 1.024s
next command
Code:
C:\KFFirstAide>fastboot -i 0x1949 flash recovery recovery.img
should see something like
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 0.449s]
writing 'recovery'...
OKAY [ 0.565s]
finished. total time: 1.020s
these next commands take forever
Code:
fastboot -i 0x1949 erase cache
should come back with
erasing 'cache'...
OKAY [ 47.246s]
finished. total time: 47.250s
Code:
fastboot -i 0x1949 erase userdata
should come back with
erasing 'userdata'...
OKAY [2149.490s]
finished. total time: 2149.494s
and finally
Code:
fastboot reboot -i 0x1949
once it starts rebooting disconnect the USB cable
once you are back up and running you will be at version 8.1.4
to get to current version
you can use KFFirstAide and this time run
c:\KFFirstAide\RunMe.bat
use the option enable OTA updates
you will have to make sure ADB is enabled under security first on your kindle
once you enable OTA updates then unplug the USB
Next :
Charge the battery, and then connect to a Wi-Fi network.
Swipe down from the top of the screen, and then tap Sync.
The software update automatically downloads in the background and installs after the download is complete and the device is asleep.
Your Kindle Fire will restart during the software update. After the restart, the message “Kindle is updating” will appear on the screen and when it's finished you will be at the latest software version.
Click to expand...
Click to collapse
Amazing! THANKS!! after weeks stuck in FB and logo, I'm back. cheers
ant17 said:
Amazing! THANKS!! after weeks stuck in FB and logo, I'm back. cheers
Click to expand...
Click to collapse
Do I need to let it update before root and twrp install?
mrgv said:
Sry about the delay.. I was counting on an email notification but never got one.. Anyway.
Tried it several times and this didn't work. The tablet doesn't boot up with this 2min+ power button press. Anyone have any other ideas please?
Click to expand...
Click to collapse
Hi, my Kindle 2nd gen 8.9" HD will not power up at all either after flashing the wrong bootloader. Did you ever figure out how to start up your Kindle. Thanks.
Hi! Amazon Fire HD 8.9”. How to Install Google OS? Chromium? ArnoldTheBat? FydeOS? CloudReady?
My 8.9" gets to the TWRP 3.0.2.0 splash screen, but not past that... adb sees the device as being in recovery, but the device doesn't respond to adb commands, and fastboot doesn't see the device.
The 2-min power button trick powered the device off, but not back on.
Any recommendations?
llleonid said:
Hi! Amazon Fire HD 8.9”. How to Install Google OS? Chromium? ArnoldTheBat? FydeOS? CloudReady?
Click to expand...
Click to collapse
Hi there! Can Windows 8 be installed? As?
brilliant
ibrahimsow1 said:
i ****ing love you, may you breed with amany and spread your DNA far and wide
Click to expand...
Click to collapse
simply superb , it was brutal trying to find the recovery img as all links were to dev host mostly. i got an old recovery.img file from an old zip . hey were back to stock. time to root again . thanks m8 excellent guide and work
llleonid said:
Hi there! Can Windows 8 be installed? As?
Click to expand...
Click to collapse
Hello illeonid. Yes you have to search thread for disable driver signature enforcement. There is a thread somewhere on here with how to do windows 8 driver for firehd. I haven't time just now to find it. Will post back later
---------- Post added at 06:40 PM ---------- Previous post was at 06:38 PM ----------
llleonid said:
Hi! Amazon Fire HD 8.9”. How to Install Google OS? Chromium? ArnoldTheBat? FydeOS? CloudReady?
Click to expand...
Click to collapse
You cannot install these on the firehd the chipset just is not capable of handling such sofware with the paltry 1gb ram being main culprit. This is mostly tied up with fireOS and system apps already