can someone help me remove custom recovery and the 2nd bootloader i have the stock amazon rom installed
Thanks in advance
Usually updating the stock ROM will do it, if you made backups of the partitions like the tutorials tell you to do you can simply reflash them in fastboot mode.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Usually updating the stock ROM will do it, if you made backups of the partitions like the tutorials tell you to do you can simply reflash them in fastboot mode.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Never made any back ups
I told someone else to try updating to the latest amazon os using Amazon's manual update the other day to fix this but it for some reason didn't work... But if you download the latest amazon is and update it it should work, however if it doesn't and it boot loops, technically you can go into twrp and tell it to reboot to boot loader (fastboot) and pull the boot loader IMG and recovery IMG from Amazon's update zip file on your PC and flash them via fastboot. If you need me to elaborate any just ask.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I told someone else to try updating to the latest amazon os using Amazon's manual update the other day to fix this but it for some reason didn't work... But if you download the latest amazon is and update it it should work, however if it doesn't and it boot loops, technically you can go into twrp and tell it to reboot to boot loader (fastboot) and pull the boot loader IMG and recovery IMG from Amazon's update zip file on your PC and flash them via fastboot. If you need me to elaborate any just ask.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
do you know of any tutorials on this? i could not find anything and as u can see i dont know much about this stuff so it would be appreciated.
Thanks
Wanna mention ahead of time, i am not responsible if you hard brick your kindle by doing this, i dont like messing with the kindles bootloader unless i have to personally.
Ok follow the instruction on Amazon's Website for manually updating a kindle. This might either bootloop/go straight to recovery once you do this, if not your probably on stock unrooted without twrp or 2nd bootloader, usually you can tell pretty easily since the kindle logo would be blue if it wasn't stock, assuming that for some reason it either does bootloop/go straight to recovery or for some reason works but has twrp and second bootloader please read on.
Keep a copy of the update on your pc. Now this gets a bit more complicated because i realized the update is a bin file, but if i remember correctly it should just be a zip file, so either tell windows open with winrar or 7zip, winzip, etc, or try enabling file extensions in your folder options on windows, and changing the extension to .zip. Once you do that extract u-boot.bin and recovery.img from the recovery folder. Put your kindle into fastboot mode(hit reboot then bootloader in twrp). Now you need a copy of fastboot.exe, so use a utility like kindle fire first aid and remember to put the recovery.img and u-boot.bin into the folder with fastboot.exe. Open a command prompt and cd into the directory that the fastboot command is in (in kffa) and verify we have a connection to the kindles fastboot by running "fastboot -i 0x1949 getvar product"(if it hangs on waiting for device, open your task manager and update the driver for the device with a triangle next to it named jem with the drivers in my signature
.) Once that command can run successfully, run these three commands:
fastboot -i 0x1949 flash bootloader u-boot.bin
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 reboot
Now pray everything went well, because if your bootloader had a bad flash your going to have a hard brick. It should boot into stock os. Tada! I'm going to get soupemagnet to make sure i explained this correctly just to make sure i didn't miss something, you don't want to hard brick the kindle, that's a pain to even attempt to recover from without a major understanding of to solder and hookup an emmc to an sdcard reader.
stunts513 said:
Wanna mention ahead of time, i am not responsible if you hard brick your kindle by doing this, i dont like messing with the kindles bootloader unless i have to personally.
Ok follow the instruction on Amazon's Website for manually updating a kindle. This might either bootloop/go straight to recovery once you do this, if not your probably on stock unrooted without twrp or 2nd bootloader, usually you can tell pretty easily since the kindle logo would be blue if it wasn't stock, assuming that for some reason it either does bootloop/go straight to recovery or for some reason works but has twrp and second bootloader please read on.
Keep a copy of the update on your pc. Now this gets a bit more complicated because i realized the update is a bin file, but if i remember correctly it should just be a zip file, so either tell windows open with winrar or 7zip, winzip, etc, or try enabling file extensions in your folder options on windows, and changing the extension to .zip. Once you do that extract u-boot.bin and recovery.img from the recovery folder. Put your kindle into fastboot mode(hit reboot then bootloader in twrp). Now you need a copy of fastboot.exe, so use a utility like kindle fire first aid and remember to put the recovery.img and u-boot.bin into the folder with fastboot.exe. Open a command prompt and cd into the directory that the fastboot command is in (in kffa) and verify we have a connection to the kindles fastboot by running "fastboot -i 0x1949 getvar product"(if it hangs on waiting for device, open your task manager and update the driver for the device with a triangle next to it named jem with the drivers in my signature
.) Once that command can run successfully, run these three commands:
fastboot -i 0x1949 flash bootloader u-boot.bin
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 reboot
Now pray everything went well, because if your bootloader had a bad flash your going to have a hard brick. It should boot into stock os. Tada! I'm going to get soupemagnet to make sure i explained this correctly just to make sure i didn't miss something, you don't want to hard brick the kindle, that's a pain to even attempt to recover from without a major understanding of to solder and hookup an emmc to an sdcard reader.
Click to expand...
Click to collapse
Okay, let me stop you right there. There's no need to manually flash those images in fastboot and, as you are aware, it isn't the safest option.
To revert to stock (safely), download the appropriate software update for the device from Amazon (onto the device itself), rename it from update.bin to update.zip (very important), factory reset in recovery (extremely important), then install the update.zip in recovery.
Upon rebooting, there will no longer be a 2nd bootloader or custom recovery, and everything will have been reverted back to pure stock.
^^ what he said, I wasn't aware the amazon zip was compatible with twrp, it has files that a flashable zip tend to have but I never looked into it. Now I know something new for future reference. xD
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
soupmagnet said:
Okay, let me stop you right there. There's no need to manually flash those images in fastboot and, as you are aware, it isn't the safest option.
To revert to stock (safely), download the appropriate software update for the device from Amazon (onto the device itself), rename it from update.bin to update.zip (very important), factory reset in recovery (extremely important), then install the update.zip in recovery.
Upon rebooting, there will no longer be a 2nd bootloader or custom recovery, and everything will have been reverted back to pure stock.
Click to expand...
Click to collapse
did what you said but install failed so pushed cynagamod to it and installed now i am stuck on kindle logo cant do nothing not even boot to twrp.
Time for a fastboot mode and kffa... If you at some point installed the drivers for fastboot then this should go smoothly, if not you will have to keep your device manager open I. With does and update the unknown jem device that's detect to the drivers in my signature. Once you do manage to make sure that the jem device is detected and has its drivers installed turn the kindle off and unplug it, then on your PC run "fastboot -i 0x1949 getvar product", once it says waiting for device plug your kindle in. It should go into fastboot mode, once there use kindle fire first aid to restore the system partition.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Time for a fastboot mode and kffa... If you at some point installed the drivers for fastboot then this should go smoothly, if not you will have to keep your device manager open I. With does and update the unknown jem device that's detect to the drivers in my signature. Once you do manage to make sure that the jem device is detected and has its drivers installed turn the kindle off and unplug it, then on your PC run "fastboot -i 0x1949 getvar product", once it says waiting for device plug your kindle in. It should go into fastboot mode, once there use kindle fire first aid to restore the system partition.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
lol i am so lost.
Basically you need to get a copy of kindle fire first aid from the 7" general section of the forum(yes I know it says 7" but its more liken all second generation kf's), open a command prompt as admin, and CD into the kindle fire first aid directory, run the command mentioned in my last post and plug the kindle in while its off. If it goes into fastboot mode then great, if not you have to install the fastboot mode drivers, you must open the device manager, and when you power on the kindle it should briefly show a jem device, you have to update its drivers to the ones in my signature before the device disappears. Once that is working run the command again. and do as previously mentioned.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
soupmagnet said:
To revert to stock (safely), download the appropriate software update for the device from Amazon (onto the device itself), rename it from update.bin to update.zip (very important), factory reset in recovery (extremely important), then install the update.zip in recovery.
Upon rebooting, there will no longer be a 2nd bootloader or custom recovery, and everything will have been reverted back to pure stock.
Click to expand...
Click to collapse
Thank you so much for this solution. Although I get my 7HD to enter fastboot mode with cable - I can't get these other solutions to work.
In TWRP I REBOOT and see RECOVERY - but when I hit RECOVERY it just boots back to TWRP. Is that all I'm looking to do before going to INSTALL the .bin file (now renamed as .zip)???? thanks much...
rightjb said:
Thank you so much for this solution. Although I get my 7HD to enter fastboot mode with cable - I can't get these other solutions to work.
In TWRP I REBOOT and see RECOVERY - but when I hit RECOVERY it just boots back to TWRP. Is that all I'm looking to do before going to INSTALL the .bin file (now renamed as .zip)???? thanks much...
Click to expand...
Click to collapse
Flash from TWRP and then reboot into system. You'll need to Swipe to factory reset first.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
Flash from TWRP and then reboot into system. You'll need to Swipe to factory reset first.
Click to expand...
Click to collapse
That worked perfectly. Thank you so very much
Related
Help, after a day or so of use, I rooted my kindle and installed google apps cause I couldn't install apps from the amazon apps store, i live abroad.
So, I was done modding my kindle, and after a day of regular use, my kindle began to shut down by itself and then it turns itself on and gets stuck in boot logo, I can manage to reboot it again using the normal boot command in kindle fire utility, but after 1 or 2 seconds of being on normally, its shuts itself down again and gets back to boot logo, any idea?
I would like to restore it to the original software (6.2.2) and try all over again if its possible, I can't send it back to amazon for warranty, I live outside the US so its not an option,
Please help!
Here is a video of what happens
http://www.youtube.com/watch?v=5zYtNZkpy7Y
luishawk said:
Help, after a day or so of use, I rooted my kindle and installed google apps cause I couldn't install apps from the amazon apps store, i live abroad.
So, I was done modding my kindle, and after a day of regular use, my kindle began to shut down by itself and then it turns itself on and gets stuck in boot logo, I can manage to reboot it again using the normal boot command in kindle fire utility, but after 1 or 2 seconds of being on normally, its shuts itself down again and gets back to boot logo, any idea?
I would like to restore it to the original software (6.2.2) and try all over again if its possible, I can't send it back to amazon for warranty, I live outside the US so its not an option,
Please help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1623244
luishawk said:
I tought it was a driver issue cause whenever i tell my kindle to reboot into fastboot I can give the commands to reboot into normal again, but I cant seem to see it using fastboot devices, there are somethings I need to check before doing the push fbmode cause I dont quite get it yet, actually my plan is to get it back to stock somehow and then start from there.
Click to expand...
Click to collapse
You are in fastboot mode.
The following will cover the fastboot commands you need...
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
You will use those fastboot commands to install TWRP and then use TWRP to install FFF.
Follow the instructions on installing these components described here...
http://forum.xda-developers.com/showthread.php?t=1638452
You will use TWRP to revert back to the stock software.
kinfauns said:
You are in fastboot mode.
The following will cover the fastboot commands you need...
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
You will use those fastboot commands to install TWRP and then use TWRP to install FFF.
Follow the instructions on installing these components described here...
http://forum.xda-developers.com/showthread.php?t=1638452
You will use TWRP to revert back to the stock software.
Click to expand...
Click to collapse
Ok, I've managed to install the drivers in the kf utility,
When i use this command "fastboot -i 0x1949 getvar product" I get the reply "kindle" so I assume my kindle is booting in fastboot mode as you said, so it must mean I'm still on the stock bootloader if I'm not wrong ,
So, I think what I should do is either flash a stock rom or flash a new bootloader and new recovery using both of this commands, correct?
fastboot -i 0x1949 flash bootloader c:\kfu\restore\u-boot.bin
fastboot -i 0x1949 flash recovery c:\kfu\restore\recovery.img
If i want to flash it back to stock should i should use:
fastboot -i 0x1949 flashall c:\kfu\restore\update-kindle-6.3.1_D01E_4107720.bin correct?
I ask cause I wanna be sure, dont wanna mess up even further, I must get now bootloaders and recoveries in .bin and .img extensions right?
I don't think that last one will work. I believe I tried it that way before and it didn't work.
You can flash the bootloader and recovery the way you have it there. Normally, I would suggest you get into recovery first and flash your bootloader there, but I think you said your /sdcard won't mount, so this will be preferable in your case.
While you are at it, flash TWRP 2.1.1 and FFF 1.4a. FFF 1.4a is distributed as a zip file. DO NOT FLASH THE ZIP FILE. I cannot stress that enough. Download the FFF zip file, check the md5 sum and make sure it matches what's on the OP. Then, you must unzip it and dig out the .bin file in there. I think it's in the cache folder if I remember correctly. Once you have both of those in place, you should be able to get your /sdcard partition fixed.... hopefully.
EDIT: I think I confused you with another guy... I think you should flash TWRP, boot into that and then flash FFF. Look at this page...
http://forum.xda-developers.com/showthread.php?t=1638452
Under the "Installing a recovery and custom bootloader" section are the exact commands in the order you need to do them. As it shows in the section, TWRP uses the zip file to flash the bootloader, you don't need to unzip it if you are going to do it that way.
kinfauns said:
I don't think that last one will work. I believe I tried it that way before and it didn't work.
You can flash the bootloader and recovery the way you have it there. Normally, I would suggest you get into recovery first and flash your bootloader there, but I think you said your /sdcard won't mount, so this will be preferable in your case.
While you are at it, flash TWRP 2.1.1 and FFF 1.4a. FFF 1.4a is distributed as a zip file. DO NOT FLASH THE ZIP FILE. I cannot stress that enough. Download the FFF zip file, check the md5 sum and make sure it matches what's on the OP. Then, you must unzip it and dig out the .bin file in there. I think it's in the cache folder if I remember correctly. Once you have both of those in place, you should be able to get your /sdcard partition fixed.... hopefully.
EDIT: I think I confused you with another guy... I think you should flash TWRP, boot into that and then flash FFF. Look at this page...
http://forum.xda-developers.com/showthread.php?t=1638452
Under the "Installing a recovery and custom bootloader" section are the exact commands in the order you need to do them. As it shows in the section, TWRP uses the zip file to flash the bootloader, you don't need to unzip it if you are going to do it that way.
Click to expand...
Click to collapse
Awesome!! brother you are full of win! it worked, I'm out of the boot logo loop, now I'm gonna flash the recovery
well, I've managed to messed up again, now its in some kinda of a twrp boot loop, everytime I reboot It goes back into twrp, I cant seem to go back into fastboot, I must investigate further.
luishawk said:
well, I've managed to messed up again, now its in some kinda of a twrp boot loop, everytime I reboot It goes back into twrp, I cant seem to go back into fastboot, I must investigate further.
Click to expand...
Click to collapse
If you installed TWRP 2.1.1 and you are using "Reboot -> System" to restart your device, the device should boot into the system. If it looks like it's booting properly, but it still comes back to recovery, something is wrong with your system software or more likely your storage partitions. This is often the case when some partitions are not available and the system software wants them fixed. It will boot into recovery, so it can be fixed, and the recovery restarts the device again in normal mode. However, you've replaced that stock recovery with TWRP and that's where it sits because TWRP isn't designed to automatically fix anything and it doesn't restart on its own.
Boot into TWRP, and get parted's partition table information...
Code:
adb shell parted /dev/block/mmcblk0 print
... and paste it here.
Alternatively, you can download the Kindle Fire software update from Amazon, change the suffix to .zip, extract the contents of the zip file, get the recovery.img out of it, flash it in fastboot, and restart. That might fix whatever problem is causing the reboots into recovery. Make sure you have the FFF bootloader installed before you do that so you can flash TWRP back again if that doesn't help.
kinfauns said:
If you installed TWRP 2.1.1 and you are using "Reboot -> System" to restart your device, the device should boot into the system. If it looks like it's booting properly, but it still comes back to recovery, something is wrong with your system software or more likely your storage partitions. This is often the case when some partitions are not available and the system software wants them fixed. It will boot into recovery, so it can be fixed, and the recovery restarts the device again in normal mode. However, you've replaced that stock recovery with TWRP and that's where it sits because TWRP isn't designed to automatically fix anything and it doesn't restart on its own.
Boot into TWRP, and get parted's partition table information...
Code:
adb shell parted /dev/block/mmcblk0 print
... and paste it here.
Alternatively, you can download the Kindle Fire software update from Amazon, change the suffix to .zip, extract the contents of the zip file, get the recovery.img out of it, flash it in fastboot, and restart. That might fix whatever problem is causing the reboots into recovery. Make sure you have the FFF bootloader installed before you do that so you can flash TWRP back again if that doesn't help.
Click to expand...
Click to collapse
Brother, my kindle is alive again! everythink works, thank you!
kinfauns said:
Alternatively, you can download the Kindle Fire software update from Amazon, change the suffix to .zip, extract the contents of the zip file, get the recovery.img out of it, flash it in fastboot, and restart. That might fix whatever problem is causing the reboots into recovery. Make sure you have the FFF bootloader installed before you do that so you can flash TWRP back again if that doesn't help.
Click to expand...
Click to collapse
This worked for me as well. Thanks!
My kindle only reboots by itself after it goes into sleep mode. if it is powered on, it does not reboot.
When in sleep mode, it reboots by itself and ends up in the TWRP screen.
bigric_tx said:
flash it in fastboot
Click to expand...
Click to collapse
Could someone please provide me with a step by step guide as to how to execute this part?
stanusj said:
My kindle only reboots by itself after it goes into sleep mode. if it is powered on, it does not reboot.
When in sleep mode, it reboots by itself and ends up in the TWRP screen.
Could someone please provide me with a step by step guide as to how to execute this part?
Click to expand...
Click to collapse
Guessing Kindle is trying to install update, but fails because you replaced stock recovery with TWRP.
Watch my [Video] Installing update-kindle-prerooted.6.3.3.v1.zip in TWRP
just download my update-kindle-prerooted.6.3.3.v1.zip and install in TWRP,
[2014][Pre-Rooted][Stock]System Version 6.3.3-Original Kindle Fire Only
I rooted my Kindle Fire two weeks ago and updated it to jellybean 4.2 using the ROM developed by hashcode. Now after the update, I feel like I bricked my device. Because first of all TWRP (blue Kindle fire logo with boot options below) is not loading in startup but regular Kindle fire logo is seen. And I can't install TWRP using Kindle Fire Utility because my device is now a different ROM and KFU can't detect my Kindle. And I'm not at all satisfied with the battery life of Kindle Fire on JB 4.2 and it gets hot like red-hot-iron even just when I watch a video. Somebody please help me to at least to get TWRP on my kindle so I could just set it to default ROM or any other. Or please tell me a way to get out of this condition.
Sent from my Amazon Kindle Fire using xda app-developers app
srvrpc said:
I rooted my Kindle Fire two weeks ago and updated it to jellybean 4.2 using the ROM developed by hashcode. Now after the update, I feel like I bricked my device. Because first of all TWRP (blue Kindle fire logo with boot options below) is not loading in startup but regular Kindle fire logo is seen. And I can't install TWRP using Kindle Fire Utility because my device is now a different ROM and KFU can't detect my Kindle. And I'm not at all satisfied with the battery life of Kindle Fire on JB 4.2 and it gets hot like red-hot-iron even just when I watch a video. Somebody please help me to at least to get TWRP on my kindle so I could just set it to default ROM or any other. Or please tell me a way to get out of this condition.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
The blue & white Kindle Fire logo with boot options is FireFireFire, not TWRP. You may or may not have TWRP installed but without access to it you'll probably never know.
If you have root permissions, the easiest and most straight forward way of getting FFF installed is to do so through terminal emulator on your device (install it if you have to).
1) Download FFF1.4.zip onto your device and extract it. That should put the resulting folder in /sdcard/extracted. There, find the uboot.bin file and move it directly to the root of your sdcard (i think it's named something like "firefirefire1.4u-boot.bin"...rename it to "u-boot.bin").
2) Then open terminal emulator and enter the following commands:
Code:
su
dd if=/sdcard/uboot.bin of=/dev/block/mmcblk0p[B]2[/B][COLOR=Red]<---This is a [U]TWO[/U][/COLOR]
That will overwrite your bootloader partition with the new u-boot.bin. Just reboot and it should work. The problem with that is, if you get a corrupt download, it may hard-brick your device. Be sure to do an md5 check.
A safer way to do this is through TWRP. You can install and access TWRP relatively in the same manner with terminal emulator.
1) Download the TWRP.img and the FFF1.4.zip (don't extract it) onto your device and place them on the root of your sdcard. (rename TWRP to "twrp.img" to make things easier)
2) In terminal emulator, enter the following commands:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p[B]5[/B][COLOR=Red]<---This is a [U]FIVE[/U], not a TWO...pay attention[/COLOR]
idme bootmode 5001
reboot
3) In TWRP, flash the FFF1.4.zip, but don't wipe anything. This method will automatically check the md5 of FFF before installing it and reduce the possibility of accidentally bricking the device.
Reboot and all will be well.
soupmagnet said:
The blue & white Kindle Fire logo with boot options is FireFireFire, not TWRP. You may or may not have TWRP installed but without access to it you'll probably never know.
If you have root permissions, the easiest and most straight forward way of getting FFF installed is to do so through terminal emulator on your device (install it if you have to).
1) Download FFF1.4.zip onto your device and extract it. That should put the resulting folder in /sdcard/extracted. There, find the uboot.bin file and move it directly to the root of your sdcard (i think it's named something like "firefirefire1.4u-boot.bin"...rename it to "u-boot.bin").
2) Then open terminal emulator and enter the following commands:
Code:
su
dd if=/sdcard/uboot.bin of=/dev/block/mmcblk0p[B]2[/B][COLOR=Red]<---This is a [U]TWO[/U][/COLOR]
That will overwrite your bootloader partition with the new u-boot.bin. Just reboot and it should work. The problem with that is, if you get a corrupt download, it may hard-brick your device. Be sure to do an md5 check.
A safer way to do this is through TWRP. You can install and access TWRP relatively in the same manner with terminal emulator.
1) Download the TWRP.img and the FFF1.4.zip (don't extract it) onto your device and place them on the root of your sdcard. (rename TWRP to "twrp.img" to make things easier)
2) In terminal emulator, enter the following commands:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p[B]5[/B][COLOR=Red]<---This is a [U]FIVE[/U], not a TWO...pay attention[/COLOR]
idme bootmode 5001
reboot
3) In TWRP, flash the FFF1.4.zip, but don't wipe anything. This method will automatically check the md5 of FFF before installing it and reduce the possibility of accidentally bricking the device.
Reboot and all will be well.
Click to expand...
Click to collapse
Thanks for the help! But I have a doubt, because my Kindle is on Jelly Bean, it is on MTP mode when connected to computer. Will it be a problem? And where do i get a non-corrupted FFF1.4.zip ?
srvrpc said:
Thanks for the help! But I have a doubt, because my Kindle is on Jelly Bean, it is on MTP mode when connected to computer. Will it be a problem? And where do i get a non-corrupted FFF1.4.zip ?
Click to expand...
Click to collapse
Terminal emulator is an app that is run on the device, not the computer, so it doesn't matter what settings you have enabled or whether your drivers are working properly. And there is one main source for FFF1.4. Corruption, if it happens, usually happens when downloading so an md5 check needs to be done before flashing the file you downloaded to your bootloader partition.
Background
1) got this kindle fire for my mom a month or two after it first released, the dev scene was very new back then and I did a basic root so that I can sideload some stuff onto it to get around the amazon store
2) adb and fastboot should have been installed back then (i recall doing an adb push)
------
Problem
1) I needed to flash a new rom that'll properly support youtube for my mom. After some reading, it seemed like the first thing i need to do was install FFF and TWRP
2) I downloaded the KFU, hit install FFF and then it reboot to the orange kindle fire logo (not blue, not flickering or anything else)
3) from here, I can't really do anything. the KFU and unbrick utility both cannot detect it (error: device not found or "waiting for device")
4) I followed a thread and went into the .android folder to add the needed lines to a file, and then to the folder in programsx86 and added a few lines, this made it so when i plugged in the stuck logo my computer made a badoop sound (which it didn't before)
5) If i try typing fastboot or adb into my cmd prompt, it just says its not recognized as a command even though i'm sure it should be installed
At this point, from my understanding...
I need to get into fastboot somehow (i'm not sure if i need a factory cable to do this)
and then try to go from there?
I'm very unfamiliar with working with fastboot and adb, i only have previous experience with my galaxy phones which never used any of these, so clear instructions are greatly appreciated.
Sorry for the long post,
Thank you for any help
L
To use adb or fastboot you need to cd ("change directory") in command prompt.
Ex. cd: C:\Users\Admin\Program Files.... etc, ad nauseum to wherever you installed KFU. You can also open up the folder where kfu is installed and drag adb.exe or fastboot.exe directly into command prompt.
Sent from my Nexus 7 using Tapatalk
jma9454 said:
To use adb or fastboot you need to cd ("change directory") in command prompt.
Ex. cd: C:\Users\Admin\Program Files.... etc, ad nauseum to wherever you installed KFU. You can also open up the folder where kfu is installed and drag adb.exe or fastboot.exe directly into command prompt.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I feel silly...thanks. I managed to get it to boot up again.
Now to proceed forward and flash another rom, i just wanted to double check something
Follow these videos: http://forum.xda-developers.com/showthread.php?t=2150317
Use KFU to install TWRP
Install FFF
And from there its just like normal where i reboot into recovery, wipe everything, flash the zip, and then off i go?
Thanks again for your help
Yep! One quick tip: It's always a good idea to make a backup before flashing anything, just in case of something possibly going bad.
Sent from my Nexus 7 using Tapatalk
projectvirtue said:
I feel silly...thanks. I managed to get it to boot up again.
Now to proceed forward and flash another rom, i just wanted to double check something
Follow these videos: http://forum.xda-developers.com/showthread.php?t=2150317
Use KFU to install TWRP
Install FFF
And from there its just like normal where i reboot into recovery, wipe everything, flash the zip, and then off i go?
Thanks again for your help
Click to expand...
Click to collapse
The purpose of the thanks button was not for you to say thanks in a post.
Sent from my Amazon Kindle Fire using xda app-developers app
I have a kindle fire HD 8.9, where a system framework file was edited and turns out to be bad.
When i try to boot it fails and defaults to recovery where i have two options, to reboot, or wipe data (which i have done extensively). I want to flash a full brand new system image to get the kindle like new, (note: It was on system 8.4.6 i believe) so that i can go the road of android. If possible, please leave a way to revert to an old system version.
Also, this cannot be recognized in fastboot because it boots straight to the recovery when given the fastboot command to boot to fastboot.
Much thanks.
@Hashcode (I figure youd be able to help the most)
michaelg117 said:
I have a kindle fire HD 8.9, where a system framework file was edited and turns out to be bad.
When i try to boot it fails and defaults to recovery where i have two options, to reboot, or wipe data (which i have done extensively). I want to flash a full brand new system image to get the kindle like new, (note: It was on system 8.4.6 i believe) so that i can go the road of android. If possible, please leave a way to revert to an old system version.
Also, this cannot be recognized in fastboot because it boots straight to the recovery when given the fastboot command to boot to fastboot.
Much thanks.
@Hashcode (I figure youd be able to help the most)
Click to expand...
Click to collapse
the fastboot 0x1949 getvar product doesnt seem to work now, it just shows the charging sign
michaelg117 said:
the fastboot 0x1949 getvar product doesnt seem to work now, it just shows the charging sign
Click to expand...
Click to collapse
turn off the kindle, type the fastboot command, when it says "waiting", then plugin the kindle
This is always a pain, if you have never installed the fastboot driver you will have to install the driver when it briefly appears before that command will work, that's why this process is so much easier on Ubuntu 13.10. If you boot a live CD there's no drivers to install, you just need to run a few commands, 2 for the package manager then the fastboot command itself.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
This is always a pain, if you have never installed the fastboot driver you will have to install the driver when it briefly appears before that command will work, that's why this process is so much easier on Ubuntu 13.10. If you boot a live CD there's no drivers to install, you just need to run a few commands, 2 for the package manager then the fastboot command itself.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I was able to do this with modded drivers when it popped up in device manager, after removing driver verification(stupid windows 8...) , then use one of the various tools to get into fastboot because for some reason the normal command wouldn't do the job, then i used yet another tool to revert to 8.1.4, and i am now happily running ParanoidAndroid
EDIT: Thanks for the drivers by the way!
So i been trying to find the answer to my issue everywhere. everything i try fails.
So basically my Kindle fire hd 8.9 is in a constant boot loop. it goes from orange w/animation, then blue w/animation... then after a period of time it says that it cant boot gives me option to factory restore (which does nothing).
when i have it hooked up to a computer, it connects for 1 second, then quickly disconnects. In device manager it comes up as "jem-pvt-prod-04" with the yellow "!". i even tried to use the amazon drivers from another post on xda, in that split second it would appear in device manager, i would update device and point it to the driver. then i will get an error saying it encountered an error installing Android ADB interface. problem encountered while trying to add driver.
Does anyone have any tips for me. im kinda stuck here and desperate with a very expensive paperweight. very upsetting!
I never tried to root, or mod this kindle fire. this problem happened on its own. or possibly after an update of some sort.
thanks guys.
piffdaddy420 said:
So i been trying to find the answer to my issue everywhere. everything i try fails.
So basically my Kindle fire hd 8.9 is in a constant boot loop. it goes from orange w/animation, then blue w/animation... then after a period of time it says that it cant boot gives me option to factory restore (which does nothing).
when i have it hooked up to a computer, it connects for 1 second, then quickly disconnects. In device manager it comes up as "jem-pvt-prod-04" with the yellow "!". i even tried to use the amazon drivers from another post on xda, in that split second it would appear in device manager, i would update device and point it to the driver. then i will get an error saying it encountered an error installing Android ADB interface. problem encountered while trying to add driver.
Does anyone have any tips for me. im kinda stuck here and desperate with a very expensive paperweight. very upsetting!
I never tried to root, or mod this kindle fire. this problem happened on its own. or possibly after an update of some sort.
thanks guys.
Click to expand...
Click to collapse
You're not hopelessly bricked if your Kindle still boots to the orange logo.
Might I ask what Windows version you're using? Newer versions enforce driver signatures, and that enforcement will cause failed installations in Windows 8+ unless you disable the enforcement before installing the drivers. I would also suggest installing ADB and fastboot if you haven't already done so. (Use the 15 second ADB installer - it's on XDA, and it works wonders!)
Sent from my Amazon Jem using XDA Labs
monster1612 said:
You're not hopelessly bricked if your Kindle still boots to the orange logo.
Might I ask what Windows version you're using? Newer versions enforce driver signatures, and that enforcement will cause failed installations in Windows 8+ unless you disable the enforcement before installing the drivers. I would also suggest installing ADB and fastboot if you haven't already done so. (Use the 15 second ADB installer - it's on XDA, and it works wonders!)
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Yes, actually i am using windows 10. My thinkpad has windows 7, so i will try to do this using windows 7. i will post back with results. its funny, out of everywhere i looked nobody mentioned windows 8+ having to disable enforcement. actually it will probably just be easier just to disable the enforcement. ill give it a try and report back.
still no luck. i was able to install the driver. but it still does the same thing. only connects for 1 second when i first turn it on. idk where to go from here? any suggestions?
piffdaddy420 said:
still no luck. i was able to install the driver. but it still does the same thing. only connects for 1 second when i first turn it on. idk where to go from here? any suggestions?
Click to expand...
Click to collapse
Completely turn off the kindle and unplug it from your PC if it's connected. Open Command Prompt and type fastboot -i 0x1949 getvar product. Plug in the kindle when you see <waiting for device> outputted. The kindle should now boot into fastboot mode, from which point you can reflash the bootloader, TWRP, and the freedom-boot image in Hashcode's thread.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Completely turn off the kindle and unplug it from your PC if it's connected. Open Command Prompt and type fastboot -i 0x1949 getvar product. Plug in the kindle when you see <waiting for device> outputted. The kindle should now boot into fastboot mode, from which point you can reflash the bootloader, TWRP, and the freedom-boot image in Hashcode's thread.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
ok so im in fastboot mode now. i checked out that thread that you sent. but i have another problem, how am i supposed to get cm and gapps onto the kindle? is there a command i can use to put the files on the internal sd card? and i cant do the adb commands to push the stack, and do the other commands adb since i couldnt get it loaded to begin with, i am not able to enable developer mode. it would be nice if i could do those commands in fastboot mode. there has to be a way to do this....
maybe if someone can send me the stock partitions that they backed up stock boot partititons when they did it. maybe if i flashed them onto my kindle it will allow me to get it to atleast boot up so i can get into adb.
right now this is completely bricked.
can anyone help me? i just need the original boot loader, boot, recovery... basically whatever was backed up before you flashed it.
i aam looking for the original because i know mine was corrupt to begin with. my theory is if i load the original boot loaders and everything then maybe i can get into the kindle just so i can run the abd commands and then put cyanogenmod on it. unless someone has a suggestion on how i can get my device to be detected by adb ? the furthest i can get into is fastboot.
piffdaddy420 said:
can anyone help me? i just need the original boot loader, boot, recovery... basically whatever was backed up before you flashed it.
i aam looking for the original because i know mine was corrupt to begin with. my theory is if i load the original boot loaders and everything then maybe i can get into the kindle just so i can run the abd commands and then put cyanogenmod on it. unless someone has a suggestion on how i can get my device to be detected by adb ? the furthest i can get into is fastboot.
Click to expand...
Click to collapse
Once you're in fastboot, you should run these fastboot commands (most of which I ripped from Hashcode's thread) to flash the bootloader, etc.:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 oem recovery
after that, you should be in TWRP, from which point you can use ADB sideload (enable in TWRP through Advanced -> ADB sideload) to flash CM. After running ADB sideload, you need to re-enable it in TWRP for each subsequent zip you want to flash.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Once you're in fastboot, you should run these fastboot commands (most of which I ripped from Hashcode's thread) to flash the bootloader, etc.:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 oem recovery
after that, you should be in TWRP, from which point you can use ADB sideload (enable in TWRP through Advanced -> ADB sideload) to flash CM. After running ADB sideload, you need to re-enable it in TWRP for each subsequent zip you want to flash.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Yes, i did all of those steps, however i never did the final step the oem recovery one...
everytime i try it now the screen turns completely red and stays there.
piffdaddy420 said:
Yes, i did all of those steps, however i never did the final step the oem recovery one...
everytime i try it now the screen turns completely red and stays there.
Click to expand...
Click to collapse
That's going to be a problem... hold down the Kindle till it completely powers off. Then open command prompt, type fastboot -i 0x1949 getvar product , and plug in the Kindle when you see <waiting for device>. Does this get you into fastboot mode?
Sent from my Amazon Jem using XDA Labs
monster1612 said:
That's going to be a problem... hold down the Kindle till it completely powers off. Then open command prompt, type fastboot -i 0x1949 getvar product , and plug in the Kindle when you see <waiting for device>. Does this get you into fastboot mode?
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
yes it does
piffdaddy420 said:
yes it does
Click to expand...
Click to collapse
It sounds like you've got a newer bootloader that's been patched. Go ahead and download the files from Hashcode's thread, and type in all of the commands exactly as given in step 5. Those should fix the red screen issue and allow you to boot normally (or into TWRP, from which point you can ADB sideload CM).
Sent from my Amazon Jem using XDA Labs
monster1612 said:
It sounds like you've got a newer bootloader that's been patched. Go ahead and download the files from Hashcode's thread, and type in all of the commands exactly as given in step 5. Those should fix the red screen issue and allow you to boot normally (or into TWRP, from which point you can ADB sideload CM).
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
i followed that exact, i tried it a couple times before you even mentioned it. but i did it again, i redownloaded everything and did it again. just to be sure. but it still continues to do the same thing with the red screen. it goes from kindlefire for 2 seconds then red screen comes across it and stays red. idk what to do. i am so upset.
piffdaddy420 said:
i followed that exact, i tried it a couple times before you even mentioned it. but i did it again, i redownloaded everything and did it again. just to be sure. but it still continues to do the same thing with the red screen. it goes from kindlefire for 2 seconds then red screen comes across it and stays red. idk what to do. i am so upset.
Click to expand...
Click to collapse
Do you happen to have any stock OS backups? If you do, you should remain able to flash those over fastboot.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Do you happen to have any stock OS backups? If you do, you should remain able to flash those over fastboot.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
no, i wish i did. the whole reason i started trying this was because the kindle was in a bootloop without even trying to flash it. it would go from kindlefire (orange) then blue, then it will ask me to do factory reset. and nomatter what i did i would keep going in the same bootloop.
so i turned to here for help, and following instructions now i am in this situation.
unfortunatley since i wasnt able to get into the kindle, i was never able to do any abd backups. so i just took my chances with it.
i was actually originally asking if anyone had the original files they can send me so i can try to flash those. atleast i can get it up and running because i really have a feeling this isnt working because i need to push the stack file over thru abd first.
piffdaddy420 said:
no, i wish i did. the whole reason i started trying this was because the kindle was in a bootloop without even trying to flash it. it would go from kindlefire (orange) then blue, then it will ask me to do factory reset. and nomatter what i did i would keep going in the same bootloop.
so i turned to here for help, and following instructions now i am in this situation.
unfortunatley since i wasnt able to get into the kindle, i was never able to do any abd backups. so i just took my chances with it.
i was actually originally asking if anyone had the original files they can send me so i can try to flash those. atleast i can get it up and running because i really have a feeling this isnt working because i need to push the stack file over thru abd first.
Click to expand...
Click to collapse
You should be able to separately flash the system.img, boot, and recovery from this tool via fastboot. It's stock OS 8.1.4, but it should work.
monster1612 said:
You should be able to separately flash the system.img, boot, and recovery from this tool via fastboot. It's stock OS 8.1.4, but it should work.
Click to expand...
Click to collapse
ok, it provided me with all the files except the bootloader. i did it step by step... but it only gave me original recovery, and original boot.img but it didnt give me the bootloader (and yes it is still turning red)
piffdaddy420 said:
ok, it provided me with all the files except the bootloader. i did it step by step... but it only gave me original recovery, and original boot.img but it didnt give me the bootloader (and yes it is still turning red)
Click to expand...
Click to collapse
anyone have any suggestions or can help me with my situation?? i am wondering if maybe someone could just send me the original backed up bootloader, boot, and recovery. i tried the original ones that were posted with that srt file. but it included everything but the bootloader. which is what i need. i know that in original thread they recommended to back up your original files (i was unable to do so because my kindle woulnt boot so i couldnt use adb to back up these files).
so if someone on here can send me the original files so i can try to get my kindle booted back up. that so far is my only theory because i tried everything else. i know people with advance knowledge would be able to help me in a heartbeat. any devs out there wanna help me out? i would greatly appreciate it!
anyone?