So I'm trying to revive my wifes old kindle fire that's been sitting in the bottom of our cabinent for about 4 months now. I rooted the thing when I bought it (valentines day last year) and put a custom rom on it, but when I powered it on yesterday, it was weird, the boot animation was zoomed in a little and distorted, and it was moved over to the right side of hte screen, so you could only see about half of it. And that's all it did. So i booted into recover (clockwork v5.0.2.7 FULL) to restore or reflash the zip, and there is ABSOLUTELY nothing anywhere, so I mounted the usb storage to the computer, and there is nothing, and i mean nothing on the kindle. So anyways, I donwnloaded a couple roms and put them on the kindle, boot into recovery, flash the rom, and it's the same thing. I reboot after a successful flash the boot image is distorted and out of place, and it just hangs there. Any ideas?
You're doing a full wipe/factory reset first, right?
Sent from my GT-p511x
vballrkc said:
So I'm trying to revive my wifes old kindle fire that's been sitting in the bottom of our cabinent for about 4 months now. I rooted the thing when I bought it (valentines day last year) and put a custom rom on it, but when I powered it on yesterday, it was weird, the boot animation was zoomed in a little and distorted, and it was moved over to the right side of hte screen, so you could only see about half of it. And that's all it did. So i booted into recover (clockwork v5.0.2.7 FULL) to restore or reflash the zip, and there is ABSOLUTELY nothing anywhere, so I mounted the usb storage to the computer, and there is nothing, and i mean nothing on the kindle. So anyways, I donwnloaded a couple roms and put them on the kindle, boot into recovery, flash the rom, and it's the same thing. I reboot after a successful flash the boot image is distorted and out of place, and it just hangs there. Any ideas?
Click to expand...
Click to collapse
The boot animation starting half off the screen is a bug that effects all CM ROMs. Other than it being ugly, it has no effect on the normal usage of the ROM itself. It looks like you received an OTA update from Cyanogenmod and it's possible that may have had some unintended side effects. Reinstalling the ROM, while being sure to factory reset in recovery, should fix the problem...assuming you aren't dealing with something more serious.
The point of that last statement is to highlight the fact that CWM recovery for kindle fires is NOT safe to use. Some versions contain a bug that can create bad blocks which, in effect, renders the device (mostly) useless. If nothing else, you definitely need to install a more current custom recovery for the Kindle Fire. If you like CWM, Cannibal Open Touch Recovery is based off of it and will be very familiar to what you're used to, except significantly safer and more stable. I would say replace your recovery first and then deal with any remaining problematic symptoms.
soupmagnet said:
The boot animation starting half off the screen is a bug that effects all CM ROMs. Other than it being ugly, it has no effect on the normal usage of the ROM itself. It looks like you received an OTA update from Cyanogenmod and it's possible that may have had some unintended side effects. Reinstalling the ROM, while being sure to factory reset in recovery, should fix the problem...assuming you aren't dealing with something more serious.
The point of that last statement is to highlight the fact that CWM recovery for kindle fires is NOT safe to use. Some versions contain a bug that can create bad blocks which, in effect, renders the device (mostly) useless. If nothing else, you definitely need to install a more current custom recovery for the Kindle Fire. If you like CWM, Cannibal Open Touch Recovery is based off of it and will be very familiar to what you're used to, except significantly safer and more stable. I would say replace your recovery first and then deal with any remaining problematic symptoms.
Click to expand...
Click to collapse
Well the only recovery downloads i can find are apk's that need to be installed and then downloaded within the app. As I cannot actually get into any rom (i've tried flashing 3, same thing, weird distorted boot image off to the side) I will need a .zip that i can flash.
vballrkc said:
Well the only recovery downloads i can find are apk's that need to be installed and then downloaded within the app. As I cannot actually get into any rom (i've tried flashing 3, same thing, weird distorted boot image off to the side) I will need a .zip that i can flash.
Click to expand...
Click to collapse
Here, let me Google that for you
http://forum.xda-developers.com/showthread.php?t=2025793
BTW, you can still install a recovery.img in recovery without it being a flashable .zip...
adb push recovery.img /sdcard/
adb shell dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p5
soupmagnet said:
Here, let me Google that for you
http://forum.xda-developers.com/showthread.php?t=2025793
BTW, you can still install a recovery.img in recovery without it being a flashable .zip...
adb push recovery.img /sdcard/
adb shell dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p5
Click to expand...
Click to collapse
I see no download for a .zip file that can be flashed from recovery. All I get is a .img file.
vballrkc said:
I see no download for a .zip file that can be flashed from recovery. All I get is a .img file.
Click to expand...
Click to collapse
Did you happen to read what I wrote, or did you just go straight to the link?
Yes I did. And if you read mine you would know that I asked for a flashable zip. Not a method of flashing a .img from recovery. But thank you for your effort it.is appreciated.
vballrkc said:
Yes I did. And if you read mine you would know that I asked for a flashable zip. Not a method of flashing a .img from recovery. But thank you for your effort it.is appreciated.
Click to expand...
Click to collapse
I did read and I'm well aware of what you're asking for. I even made mention of it in a previous post. The problem here is that Cannibal Open Touch recovery doesn't have a flashable .zip, and there's a strong possibility that installing TWRP will only compound your problems. I'm trying to point you in the right direction, but I'm having trouble understanding your aversion to using the command line, which is essentially faster and more straightforward to begin with.
soupmagnet said:
I did read and I'm well aware of what you're asking for. I even made mention of it in a previous post. The problem here is that Cannibal Open Touch recovery doesn't have a flashable .zip, and there's a strong possibility that installing TWRP will only compound your problems. I'm trying to point you in the right direction, but I'm having trouble understanding your aversion to using the command line, which is essentially faster and more straightforward to begin with.
Click to expand...
Click to collapse
Thank you.
ok, so I'm really trying to avoid using adb or anything, but i may have to before this all said and done. But just for grins I tried flashing an older rom, i believe it was the cm-9 rom, and now it just boot loops. Its not the same issue, just a new one. Any ideas?
vballrkc said:
ok, so I'm really trying to avoid using adb or anything, but i may have to before this all said and done. But just for grins I tried flashing an older rom, i believe it was the cm-9 rom, and now it just boot loops. Its not the same issue, just a new one. Any ideas?
Click to expand...
Click to collapse
I mentioned earlier that using CWM recovery is not safe to use. There's a bug in some versions that can result in the dreaded EMMC superbrick. Don't use it. On top of that, all of the cm9 roms are quite unstable as well, including issues that can prevent the device from charging.
From the looks of it, your bootloop is from flashing CM9 in CWM, which in most cases, the two aren't compatible. So, before you get yourself into any more trouble, I need to ask....
1) Do you have FireFireFire installed? If so, what version (yellow triangle or blue & white KF logo)?
2) Do you still have access to custom recovery?
soupmagnet said:
I mentioned earlier that using CWM recovery is not safe to use. There's a bug in some versions that can result in the dreaded EMMC superbrick. Don't use it. On top of that, all of the cm9 roms are quite unstable as well, including issues that can prevent the device from charging.
From the looks of it, your bootloop is from flashing CM9 in CWM, which in most cases, the two aren't compatible. So, before you get yourself into any more trouble, I need to ask....
1) Do you have FireFireFire installed? If so, what version (yellow triangle or blue & white KF logo)?
2) Do you still have access to custom recovery?
Click to expand...
Click to collapse
you'll have to pardon my lack of knowledge, as it's been at least a year since i've messed with this and I have several android devices, each with their own set of jargen. I know I HAVE installed firefirefire. as to what version, i'm sorry, I don't know. And I do have access to clockwork recovery, but that's it. I can not get into any rom, i've flashed probably 10 different ones.
vballrkc said:
you'll have to pardon my lack of knowledge, as it's been at least a year since i've messed with this and I have several android devices, each with their own set of jargen. I know I HAVE installed firefirefire. as to what version, i'm sorry, I don't know. And I do have access to clockwork recovery, but that's it. I can not get into any rom, i've flashed probably 10 different ones.
Click to expand...
Click to collapse
Okay, don't flash any more ROMs in clockwork recovery. I can't stress that enough.
In order to move forward from here, you need to be able to communicate with the device over ADB, so open a command prompt, change directories (cd) to the one containing adb.exe, and enter 'adb devices' while booted into recovery Does it show that a device is connected?
soupmagnet said:
Okay, don't flash any more ROMs in clockwork recovery. I can't stress that enough.
In order to move forward from here, you need to be able to communicate with the device over ADB, so open a command prompt, change directories (cd) to the one containing adb.exe, and enter 'adb devices' while booted into recovery Does it show that a device is connected?
Click to expand...
Click to collapse
ok hang on, i don't even have adb installed on this computer. been a while since i've used it too. is there a thread in this forum that will help me with that?
vballrkc said:
ok hang on, i don't even have adb installed on this computer. been a while since i've used it too. is there a thread in this forum that will help me with that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
That should do the trick
ok, all the threads and "how-to's" i'm finding require that you be able to access the tablets settings to enable ADB. As I cannot do that, i'm not sure what to do now. I mean, is this really that hard? I feel like there is an easy answer out there for me to be able to flash a new recovery....maybe i'm wrong. does ANYONE have an idea on how I can flash a different recovery other then clockwork. Again, I CONNOT do anything on this tablet other then access clockwork recovery andboot loop, that it all.
Very similar similar situation after flashing a rom. Please help me
Hello,
I am running into the a very similar situation. I am running 6.3.2
First I ran KFU 0.9.9, this installed FFF with no problem. KFU downloaded "most recent twrp" and installed it (but does not work, freezes at teamwin logo). and it had trouble installing su.
After looking around for ways to root kindle fire 6.3. without using KFU. I found a tutorial on the following website Eputor.com. (google search eputor how to root kindle fire)
after downloading the recommended files, I ran these comands using cmd
1. adb push fbmode /data/local/fbmode
2. adb shell chmod 755 /data/local/fbmode
3. adb shell /data/local/fbmode
4. adb reboot
after booting into Fastboot mode, I use the following commands
1. fastboot -i 0x1949 flash bootloader u-boot.bin
2. fastboot -i 0x1949 flash recovery twrp.img
3. fastboot -i 0x1949 oem idme bootmode 4000
4. fastboot -i 0x1949 reboot
after booting into recover I use the following commands:
1. adb shell mount system
2. adb push su /system/xbin/su
3. adb shell chown 0.0 /system/xbin/su
4. adb shell chmod 06755 /system/xbin/su
After installing SU and gapps I believe I have accessed root because when I install 3rd party apps SU asks for permission to grant permission.
I have had to manually flash twrp 2.4 because every time I flash a newer twrp and boot into twrp, twrp gets stuck at at the teamwin logo then reboots with no access to recovery, only the teamwin logo. Ive flashed every twrp version from 2.6.3.1 going down the list of twrp downloads provided by the website that (sorry, I would provide the link but can't because I have not have 10 posts yet.) the twrp website provide but the only recovery to actually work on my kindle is twrp 2.4.0.0.
after flashing twrp 2.4, I flashed 3 different roms and have had no luck.
1st rom - I wiped cache, dalvik cache, factory rest and then flashed jb-4.2.2-kfire-hashcode-2013-02-12.
wiped cache again after install was complete, then flashed gapps and after that , wiped cache again.
after rebooting, I get stuck on a the boot animation. It then freezes for a few minutes then it reboots back into FFF then loops back same boot animation loop.
2nd rom - I then proceed to wiped cache, dalvik cache, factory rest and then flash Cm - 10.1 - 20130724 - 1413 - otter-sgt7.zip, wiped cache again after install was complete, then flashed gapps and after that , wiped cache again and reboot.
After rebooting, I get stuck on a the boot animation very similar to the previous rom, it boots up to the boot animation, but the difference is that the boot animation is off centered and cut off. It then freezes for a few minutes then it reboots back into FFF then loops back same boot animation loop.
3rd rom -I do the exact same with Pac_otter_4.3-build.1.RC_20130824- 144117.zip and the exact same thing happens boot loop with off centered boot logo. then reboots into fff and off centered boot logo.
I cant find a rom that will work. I really hope this is enough information, I hope someone out there can help me.
In this thread, it was advised to wipe data. in twrp 2.4.0.0, the wipe options are cache, dalvik cache, factory reset, system, external storage, and android secure. Is it nececary to wipe external storage, system and android secure? I have only wiped cache, dalvik cache, factory reset, system. Please advise.
MasterLarry said:
Hello,
I am running into the a very similar situation. I am running 6.3.2
First I ran KFU 0.9.9, this installed FFF with no problem. KFU downloaded "most recent twrp" and installed it (but does not work, freezes at teamwin logo). and it had trouble installing su.
After looking around for ways to root kindle fire 6.3. without using KFU. I found a tutorial on the following website Eputor.com. (google search eputor how to root kindle fire)
after downloading the recommended files, I ran these comands using cmd
1. adb push fbmode /data/local/fbmode
2. adb shell chmod 755 /data/local/fbmode
3. adb shell /data/local/fbmode
4. adb reboot
after booting into Fastboot mode, I use the following commands
1. fastboot -i 0x1949 flash bootloader u-boot.bin
2. fastboot -i 0x1949 flash recovery twrp.img
3. fastboot -i 0x1949 oem idme bootmode 4000
4. fastboot -i 0x1949 reboot
after booting into recover I use the following commands:
1. adb shell mount system
2. adb push su /system/xbin/su
3. adb shell chown 0.0 /system/xbin/su
4. adb shell chmod 06755 /system/xbin/su
After installing SU and gapps I believe I have accessed root because when I install 3rd party apps SU asks for permission to grant permission.
I have had to manually flash twrp 2.4 because every time I flash a newer twrp and boot into twrp, twrp gets stuck at at the teamwin logo then reboots with no access to recovery, only the teamwin logo. Ive flashed every twrp version from 2.6.3.1 going down the list of twrp downloads provided by the website that (sorry, I would provide the link but can't because I have not have 10 posts yet.) the twrp website provide but the only recovery to actually work on my kindle is twrp 2.4.0.0.
after flashing twrp 2.4, I flashed 3 different roms and have had no luck.
1st rom - I wiped cache, dalvik cache, factory rest and then flashed jb-4.2.2-kfire-hashcode-2013-02-12.
wiped cache again after install was complete, then flashed gapps and after that , wiped cache again.
after rebooting, I get stuck on a the boot animation. It then freezes for a few minutes then it reboots back into FFF then loops back same boot animation loop.
2nd rom - I then proceed to wiped cache, dalvik cache, factory rest and then flash Cm - 10.1 - 20130724 - 1413 - otter-sgt7.zip, wiped cache again after install was complete, then flashed gapps and after that , wiped cache again and reboot.
After rebooting, I get stuck on a the boot animation very similar to the previous rom, it boots up to the boot animation, but the difference is that the boot animation is off centered and cut off. It then freezes for a few minutes then it reboots back into FFF then loops back same boot animation loop.
3rd rom -I do the exact same with Pac_otter_4.3-build.1.RC_20130824- 144117.zip and the exact same thing happens boot loop with off centered boot logo. then reboots into fff and off centered boot logo.
I cant find a rom that will work. I really hope this is enough information, I hope someone out there can help me.
In this thread, it was advised to wipe data. in twrp 2.4.0.0, the wipe options are cache, dalvik cache, factory reset, system, external storage, and android secure. Is it nececary to wipe external storage, system and android secure? I have only wiped cache, dalvik cache, factory reset, system. Please advise.
Click to expand...
Click to collapse
Thanks for taking the time to share your experience. I too hope that someone can help us with this. I'm confident someone will. I've never had a problem that the good folks at XDA couldn't help me fix.
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
Hi everyone, I have two kindle fire, I messed with both of them.
I've root them the first one has the problem with the yellow triangle logo stucked. And the other one I've tried to reset it to the factory settings and everything was cool until I hit the TWRP utility and I think I erased everything.
I've see tons of posts regarding rooting and troubleshooting related to rooting and i'm pretty sick of rooting, I think that 3 months is sufficient time, please DON'T POST anything related to rooting.
I'm here asking if anyone knows how to flash all the data ofthe kindle from the pc and been able to install the factory software, firmware (I don't know) from scratch from my pc. Anyone, please?
The first one is probably stuck in fastboot. Try giving it a go with "fastboot oem idme bootmode 4000 && fastboot reboot".
For the second one, "I think I erased everything" is as descriptive as not wanting people to post about your procedure is helpful. What exactly is going on with it? For future reference: http://forum.xda-developers.com/showthread.php?t=1644970
You should also update both FFF and TWRP on both devices once they are working normally.
If i may suggest flashing modaco first after a good wipe everything except your sdcard I believe this will make a smoother transition if you desire to return to stock before returning to stock always do a good wioe to remove remnants of previous roms download the latest stock bin and rename it to update.zip do not place it in any folder just at the root of your sdcard flash in twrp this will also wipe out twrp and fff I really dont recommend doing this lots of people fail at doing the procedure correcty modaco is stock with only the market added try this approach first then you can retain fff and twrp for custom backups.
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
I really, don't want to try the adb commands (I've tried them before), nor follow any tutorial about root troubleshooting.
I'm really sick of them and of all that mal-functioning software that you have to download(Eg. Not-responding superOneClick, kindleFireUnbrickUtility saying in one line <No device found> <Processing something> <Congrats, your kindle is good to go! (When it's not)>, Eternal loading Android Commander)
With all due respect I DON'T want any more of those, as I said, 3 months is sufficient time, I feel so frustrated.
jRam90 said:
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
I really, don't want to try the adb commands (I've tried them before), nor follow any tutorial about root troubleshooting.
I'm really sick of them and of all that mal-functioning software that you have to download(Eg. Not-responding superOneClick, kindleFireUnbrickUtility saying in one line <No device found> <Processing something> <Congrats, your kindle is good to go! (When it's not)>, Eternal loading Android Commander)
With all due respect I DON'T want any more of those, as I said, 3 months is sufficient time, I feel so frustrated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=25730666&postcount=2
Read from "Reverting to stock software". You can manually rename the file and then copy it into the KF instead of using ADB for it, just make sure the extension is .zip and not .zip.bin (Windows hides extensions per default settings).
jRam90 said:
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
Click to expand...
Click to collapse
To restore back to full factory
1. Download Kindle Fire Software Update Version 6.3.1
2. Rename the file to update.zip
3. Get in to TWRP and mount USB drive
4. Copy update.zip to Kindle Fire
5. Unmount USB drive
6. Do factory reset, then wipe system cache, and dalvik cache
7. Flash the update.zip
8. Let it bootloop about 3 times or so...
If you want FFF and TWRP then flash Stock 6.3.1 Basic from TWRP. This has no root or gapps.
Dasanko said:
http://forum.xda-developers.com/showpost.php?p=25730666&postcount=2
Read from "Reverting to stock software". You can manually rename the file and then copy it into the KF instead of using ADB for it, just make sure the extension is .zip and not .zip.bin (Windows hides extensions per default settings).
Click to expand...
Click to collapse
When trying to execute the adb shell commands all I get is:
- exec 'system/bin/sh' failed: No such file or directory (2) -
I've also tried, fastboot update | flash | boot | flash:raw
This is with one kindle, with the other one, I can't even get the PC to recognized it as a USB
Is there any tool, that really erases everything and take the stock ROM to be installed again? Software, script?
jRam90 said:
When trying to execute the adb shell commands all I get is:
- exec 'system/bin/sh' failed: No such file or directory (2) -
I've also tried, fastboot update | flash | boot | flash:raw
This is with one kindle, with the other one, I can't even get the PC to recognized it as a USB
Is there any tool, that really erases everything and take the stock ROM to be installed again? Software, script?
Click to expand...
Click to collapse
Ahh, that's a bother. It's a pretty annoying error. Could be something messed with your TWRP (I'm assuming you tried the commands from there).
There isn't one, but there's really no need for it... you just rename the ROM to update.zip, wipe cache, dalvik-cache and factory reset, and install update.zip. If you just want to flash stock because you like it better for whatever reason, you could also just look at the MoDaCo custom ROM instead, as it is stock based.
As for the other KF... you can't get it recognized, from where? The ROM? TWRP? Fastboot?
Dasanko said:
Ahh, that's a bother. It's a pretty annoying error. Could be something messed with your TWRP (I'm assuming you tried the commands from there).
There isn't one, but there's really no need for it... you just rename the ROM to update.zip, wipe cache, dalvik-cache and factory reset, and install update.zip. If you just want to flash stock because you like it better for whatever reason, you could also just look at the MoDaCo custom ROM instead, as it is stock based.
As for the other KF... you can't get it recognized, from where? The ROM? TWRP? Fastboot?
Click to expand...
Click to collapse
Both of the kindles, are damaged. I can't access them. I just can access one by USB.
For future reference:
This user's issues have been partially dealt with.
The first KF will require a factory cable to be fixed.
The second KF was soft bricked (there were a few corrupt partitions) after a bad flash attempt of the stock ROM. Luckily, FFF was still installed, but the Windows fastboot drivers weren't. Reinstalled FFF+TWRP from Firekit, and then fixed the partitions, wiped and flashed the stock ROM.
Dasanko said:
For future reference:
This user's issues have been partially dealt with.
The first KF will require a factory cable to be fixed.
The second KF was soft bricked (there were a few corrupt partitions) after a bad flash attempt of the stock ROM. Luckily, FFF was still installed, but the Windows fastboot drivers weren't. Reinstalled FFF+TWRP from Firekit, and then fixed the partitions, wiped and flashed the stock ROM.
Click to expand...
Click to collapse
Thanks a LOT, Dasanko !!!!
jRam90 said:
Thanks a LOT, Dasanko !!!!
Click to expand...
Click to collapse
Ok, So, I have the factory cable. How can I test its Ok?
I have another question, the kindle is pratically empty no system, no sdcard memory, probably corrupted ¿How do I use the factory cable, to format the Kindle and install the Stock ROM again?
With the KF off and unplugged, type "fastboot getvar product" on a shell (KFU/tools).
Then plug in the KF using the factory cable. If you get anything listed or returned, it should be working fine. Otherwise, if you wait a few seconds and still nothing, you'll have to check the drivers to make sure the correct fastboot ones are installed.
To check the partitions, you can just "fastboot boot twrp.img" to load a TWRP into memory, and then "adb shell parted /dev/block/mmcblk0 p" to print all partitions' information.
Dasanko said:
With the KF off and unplugged, type "fastboot getvar product" on a shell (KFU/tools).
Then plug in the KF using the factory cable. If you get anything listed or returned, it should be working fine. Otherwise, if you wait a few seconds and still nothing, you'll have to check the drivers to make sure the correct fastboot ones are installed.
To check the partitions, you can just "fastboot boot twrp.img" to load a TWRP into memory, and then "adb shell parted /dev/block/mmcblk0 p" to print all partitions' information.
Click to expand...
Click to collapse
Well, I'm at my job now. So I will try this at home, but the shell is not working since system/sh (shell) it's not in the Kindle. I was trying to boot it yesterday with "fastboot boot twrp.img" and nothing. I also tried: "fastboot getvar product" and nothing but I only used the console. Anyway, let's see what happens...
Quick question, I've read that the factory cable puts the Kindle straight into bootmode, ¿So the color of the power button, has something to do with it? ¿I mean how do I know the kindle has entered factory mode? ¿The orange light is an indicator? (With a standard USB Cable I only get the green light with the power button, with the factory cable I first get green light, then orange light)
I've also read that if I can see the Kindle fire logo, the bootloader is Ok. Hence my Kindle is OK, but I can't enter fastboot mode. ¿Can anyone confirm this?
It'll get stuck in the bootloader screen, and fastboot commands should work as well, provided the drivers are properly installed and working.
Dasanko said:
It'll get stuck in the bootloader screen, and fastboot commands should work as well, provided the drivers are properly installed and working.
Click to expand...
Click to collapse
OK, I've finally made myself a working factory cable. And in the device manger I can see the kindle listed as "Android phone" and in that root it says "Android ADB Interface". Look like drivers are not working. Where can I download them?
Those are the proper drivers for fastboot you should be able to use kfu to send twrp and fff to the device if that doesn't work you will need to fastboot flash them
All I get is < waiting for device>. Looks like the drivers are not installed.
Simply hold the power button down while connected when it says waiting then power it back on and it should send also try unplug replug when it says waiting
---------- Post added at 03:49 PM ---------- Previous post was at 03:44 PM ----------
If you would like some help I have some time before work but you must finish your thread for the benefit of others
So today i dug up my Kindle fire [rooted and running ICS] and decided to flash the jellybean mod, so i did the usual and wiped the caches and did a factory reset however being an absolute retard i was hoping i could have a clean system so i wiped every single category. Including Cache,Dalvik Cache,Factory Reset,Battery Stats,Rotation,System,SD card, and SD,Ext. after this i have a Kindle undetectable and without any firmware but i can still acces all recovery menus, otherwise its a sleek black paper weight that freezes at the "Kindle Fire" logo. I am new to the forums and didn't want to be a nuisance but i saw no other solved threads with this problem. Any help to restoring my kindle to stock or to jellybean would be greatly appreciated thanks
You need to access recovery, via either fastboot commands (changing bootmode) or the boot menu (FFF 1.4x only). Once you're in recovery, you can use either adb commands to push a new rom to the sdcard OR mount your sdcard as an external drive and transfer the rom respectively. Then, flash as usual.
soupmagnet said:
You need to access recovery, via either fastboot commands (changing bootmode) or the boot menu (FFF 1.4x only). Once you're in recovery, you can use either adb commands to push a new rom to the sdcard OR mount your sdcard as an external drive and transfer the rom respectively. Then, flash as usual.
Click to expand...
Click to collapse
i dont have fff 1.4 and im not sure how to change my bootmode without using a computer..
??
If you cannot use kfu to alter the boot modes and you can't get commands to work to access recovery here is one of your better bets http://forum.xda-developers.com/showthread.php?t=1392693&highlight=info+factory+cable get a factory cable get it into fastboot ,,, fastboot flash fff bin so that you can access recovery...
same thing happened to me
This happened to me too. I fixed this by going on my computer downloading the ROM and gapps files and then sending them to my kindle fire by USB and then open twrp and flash them.......then your done. I hope this helped you
Trying to go to 100% back to stock for resale. I downloaded the 6.3.1 bin file and renamed to update.zip and installed with TWRP. Everything seemed to go fine but after rebooting I get a constant android.process.acore force close and it just keeps rebooting every 15 seconds. It wont stay up long enough to get through the menus to do a factory reset and KFU shows its ONLINE with a 4000 boot status but every time I try to install permanent root or install TWRP or any other recovery it says failed to copy permission denied...
Not sure what to do here. Every time I try to do anything with KFU it tells me the "directory data/local.fbmode: not found". I also have the problem that I have 2 more Kindle Fires I need to restore to stock but I don't really dare try anything after this for fear the same thing might happen. Any friendly advice out there?
Help?
GrandMasterB; said:
data/local.fbmode
Click to expand...
Click to collapse
Is that a typo or is that how you're entering the command? Also, did you make sure to push fbmode to /data/local before trying to execute?
That's using Kindle Fire Utility. I'm not entering any commands myself, just menu selections. So is that in relation to the" permission denied" error I'm getting first? Is that not allowing it to push the fbmode file? Why would I get a permission denied all the sudden? It has always worked fine on all 3 of our Fires.
GrandMasterB said:
That's using Kindle Fire Utility. I'm not entering any commands myself, just menu selections. So is that in relation to the" permission denied" error I'm getting first? Is that not allowing it to push the fbmode file? Why would I get a permission denied all the sudden? It has always worked fine on all 3 of our Fires.
Click to expand...
Click to collapse
I should have known...silly me.
No. What I'm saying is, in your previous message, the string of text that you posted: "directory data/local.fbmode: not found" is incorrect...Did you copy and paste that exactly as is or did you type it? The answer could mean a completely different solution.
Sorry, that's a typo on my part. I'll copy and paste exactly what i am seeing below.
***********************************************
* Recovery Installer *
***********************************************
***********************************************
* WARNING *
***********************************************
Make sure to read each screen carefully!
Make sure to follow instructions given to you!
twrp.img has been found.
***********************************************
* NOTICE *
***********************************************
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
***********************************************
* Activating Fastboot (4002) *
***********************************************
failed to copy 'files\fbmode' to '/data/local/fbmode': Permission denied
Unable to chmod /data/local/fbmode: No such file or directory
/data/local/fbmode: not found
The kindle has been told to reboot in Fastboot Mode.
< waiting for device >
You're actually very lucky because you are able to connect to the kindle using adb, which when I had this problem was completely out of the question. I would try to send the commands manually using command prompt. You may not be able to do that unless you're in fastboot mode though which can be done by (I don't have a windows PC with me at the moment to check this but I believe that is) option 1 in KFU for bootmodes and then option 2 for fastboot. You're going to need to download KindleADB which I just so happen to have available on my mediafire account: http://www.mediafire.com/download.php?1fb30q3wqf95b3i
I would also recommend downloading this TWRP.img which is TWRP 2.1.1 rather than the most recent 2.2.0 which has seemed to cause some issues recently during flashing.: http://www.mediafire.com/download.php?f3sr33214229pr2 and place that in your KindleADB folder after you have downloaded and extracted it. and this is the file for fff v.1.4a which is the current version as far as I know. http://www.mediafire.com/?el5lxqvoasa8uer also place that file into your KindleADB folder and rename it to fff.bin (not fff.bin.bin).
For convenience, place the KindleADB folder on the root of your C: Drive (not in any folders or anything)
To flash TWRP use these commands one line at a time:
Code:
cd /
cd KindleADB
fastboot flash recovery twrp.img
To flash fff you should already be in the KindleADB directory so you can just enter these commands:
Code:
fastboot flash bootloader fff.bin
fastboot reboot
Please understand though that even though I have a lot of experience with android and Kindle Fire and I am fairly confident that this should get you in the right direction I would really appreciate if someone else could confirm that this would work before you try it. (I'm actually more worried about getting you stuck in fastboot than anything else). If this doesn't work you're probably going to need to get a factory cable
After you have TWRP and FFF reflashed to your device, you want to place the update.zip on your SD if it isn't still there and make sure you do a factory reset and wipe EVERYTHING (DATA, CACHE, SYSTEM, DALVIK) before you flash it, that is how you wound up in this situation to begin with. With your other devices which already have twrp and fff installed, that is all you will have to do.
nschiwy said:
You're actually very lucky because you are able to connect to the kindle using adb, which when I had this problem was completely out of the question. I would try to send the commands manually using command prompt. You may not be able to do that unless you're in fastboot mode though which can be done by (I don't have a windows PC with me at the moment to check this but I believe that is) option 1 in KFU for bootmodes and then option 2 for fastboot. You're going to need to download KindleADB which I just so happen to have available on my mediafire account: http://www.mediafire.com/download.php?1fb30q3wqf95b3i
I would also recommend downloading this TWRP.img which is TWRP 2.1.1 rather than the most recent 2.2.0 which has seemed to cause some issues recently during flashing.: http://www.mediafire.com/download.php?f3sr33214229pr2 and place that in your KindleADB folder after you have downloaded and extracted it. and this is the file for fff v.1.4a which is the current version as far as I know. http://www.mediafire.com/?el5lxqvoasa8uer also place that file into your KindleADB folder and rename it to fff.bin (not fff.bin.bin).
For convenience, place the KindleADB folder on the root of your C: Drive (not in any folders or anything)
To flash TWRP use these commands one line at a time:
Code:
cd /
cd KindleADB
fastboot flash recovery twrp.img
To flash fff you should already be in the KindleADB directory so you can just enter these commands:
Code:
fastboot flash bootloader fff.bin
fastboot reboot
Please understand though that even though I have a lot of experience with android and Kindle Fire and I am fairly confident that this should get you in the right direction I would really appreciate if someone else could confirm that this would work before you try it. (I'm actually more worried about getting you stuck in fastboot than anything else). If this doesn't work you're probably going to need to get a factory cable
After you have TWRP and FFF reflashed to your device, you want to place the update.zip on your SD if it isn't still there and make sure you do a factory reset and wipe EVERYTHING (DATA, CACHE, SYSTEM, DALVIK) before you flash it, that is how you wound up in this situation to begin with. With your other devices which already have twrp and fff installed, that is all you will have to do.
Click to expand...
Click to collapse
Thank you. This is exactly what I was looking for. BUT right before you posted this I was finally able to get through the menu and initiate a factory reset that was able to finish and reboot itself before it rebooted unexpectedly again. Every time I tried it before I would get a reboot before it was finished with the factory reset.
Anyways, its back up and running fine now. Connected to my wifi and downloading some apps now. I do have a question though, I did a factory reset and wiped dalvic/cache before installing the update.zip and I wiped dalvic/cache after the install before rebooting and I had this problem. I did not wipe SYSTEM because the guide I followed for back to stock didn't say to wipe system and also because many months ago I was switching ROMs and I wiped everything including stystem (like I do on my Galaxy Nexus) before the install and it wouldn't boot past the FIRE logo. Luckily at that time I still had TWRP installed and was able to easily fix it. But you are saying that I SHOULD wipe system on the other 2 Kindle Fires before I install the update.zip? Just want to make sure I don't have to go through this 2 more times today...
Thanks again for the helps guy. I am extremely thankful.
GrandMasterB said:
Thank you. This is exactly what I was looking for. BUT right before you posted this I was finally able to get through the menu and initiate a factory reset that was able to finish and reboot itself before it rebooted unexpectedly again. Every time I tried it before I would get a reboot before it was finished with the factory reset.
Anyways, its back up and running fine now. Connected to my wifi and downloading some apps now. I do have a question though, I did a factory reset and wiped dalvic/cache before installing the update.zip and I wiped dalvic/cache after the install before rebooting and I had this problem. I did not wipe SYSTEM because the guide I followed for back to stock didn't say to wipe system and also because many months ago I was switching ROMs and I wiped everything including stystem (like I do on my Galaxy Nexus) before the install and it wouldn't boot past the FIRE logo. Luckily at that time I still had TWRP installed and was able to easily fix it. But you are saying that I SHOULD wipe system on the other 2 Kindle Fires before I install the update.zip? Just want to make sure I don't have to go through this 2 more times today...
Thanks again for the helps guy. I am extremely thankful.
Click to expand...
Click to collapse
All you need to do is run the factory reset from TWRP... I know people suggest you wipe the cache and dalvik cache as well, but if you pay attention to the output from doing a factory reset, you'll see it's all inclusive. A factory reset will reformat /data and /cache. Wiping the cache reformats /cache. Wiping the dalvik cache erases /data/dalvik-cache and /cache/dalvik-cache. If redundancy matters to you, it won't hurt to do it all, but you absolutely must perform a factory reset.
I'm not calling you a liar, but despite your claims, I suspect you missed the factory reset part and the /data partition wasn't wiped clean. This is backed up by the fact that the factory reset from the stock system software fixed things for you. The two are pretty much the same, but the stock software will also wipe the /sdcard clean.
As for wiping the system, you don't need to do that before returning to stock. Essentially all ROM/stock zips include a line like this in their updater-script...
format("ext4", "EMMC", "/dev/block/platform/mmci-omap-hs.1/by-name/system");
The above is from the 6.3.1 update zip archive. That takes care of making sure the system is clear of any files before anything else gets written to it. Again... it's not going to hurt if you take that extra step, but it's unnecessary.
That concludes my lecture on everything you never cared to know about factory reset and wiping the system.
Guys,
Need some help now..
I have done a preliminary search but I haven't got an answer, hence the New thread.. Sorry about it if it's well explained elsewhere.
I have been using the fire since beginning of 2012 and rooted it and I was running a custom rom (I think Gederom) from one of the devs until yesterday.
It is on twrp 2.1.1
The rom seemed a bit laggy and I decided to try out another last night. So i downloaded the hellkat linaro 4.4.2 2013-12-30 version and the gapps to flash.
I went into recovery and wiped Cache , Dalvik , factory reset and flashed the rom.
Now, the flashing ended with an unsuccessful message and I am stuck on bootloop since there is no active rom on my fire.
Should I update twrp? If so, how?
Or what else am I supposed to do now, to get it up and running?
You need to flash TWRP 2.6.3.1 in order to flash a 4.4.2 ROM. Flashing on any other version of TWRP will cause an unsuccessful error. I believe Hashcode posted an updated TWRP that while it still states 2.6.3.0, it is actually updated to 2.6.3.1. You need to find it, download it, go back into recovery, go to mount, and mount only USB storage with your kindle connected to your computer. This will allow you to copy files to your kindle from recovery. Copy the recovery to your kindle and flash it like you would flash anything else. Power off your kindle and power it back on, and boot into recovery again. This time, flash the ROM like you normally would, and you should be all set.
EDIT: Did ya one better I still had the zip on my Kindle, so I uploaded it for you. It will still say 2.6.3.0 but it is really 2.6.3.1. Enjoy
TWRP 2.6.3.1 for first gen Kindle Fire
Sent from my Nexus 7 using Tapatalk
I had this exact same issue. Sadly, I cannot boot into recovery to mount my device.
purplelightsaber said:
I had this exact same issue. Sadly, I cannot boot into recovery to mount my device.
Click to expand...
Click to collapse
If you can get your computer to recognize the kindle when it is in the bootloader through adb then you can boot into recovery by downloading the latest twrp recovery IMG file. Get the TWRP IMG file downloaded and then run the adb commands to get into fastboot mode.
Rooted stock:
Code:
adb shell su -c 'idme bootmode 4002'
ROM with root access:
Code:
adb shell idme bootmode 4002
Once you are in fastboot mode you can enter recovery without actually having it flashed to your device by issuing the following fastboot command
Code:
fastboot boot recovery path/to/recovery.img
Replace the path/to/recovery with the actual path and name of the recovery image for example if its on your C drive it would be something like "C:/TWRP.2.3.6.1_otter.img"
That will give you full access to the newest TWRP without actually having it flashed on your device and once you save you kindle you can actually permanently flash the recovery.
To get out of fastboot issue the following command.
Code:
fastboot oem idme bootmode 4000
fastboot reboot
Sent from my Nexus 7 2013 using Tapatalk 4
SwoRNLeaDejZ said:
You need to flash TWRP 2.6.3.1 in order to flash a 4.4.2 ROM. Flashing on any other version of TWRP will cause an unsuccessful error. I believe Hashcode posted an updated TWRP that while it still states 2.6.3.0, it is actually updated to 2.6.3.1. You need to find it, download it, go back into recovery, go to mount, and mount only USB storage with your kindle connected to your computer. This will allow you to copy files to your kindle from recovery. Copy the recovery to your kindle and flash it like you would flash anything else. Power off your kindle and power it back on, and boot into recovery again. This time, flash the ROM like you normally would, and you should be all set.
EDIT: Did ya one better I still had the zip on my Kindle, so I uploaded it for you. It will still say 2.6.3.0 but it is really 2.6.3.1. Enjoy
TWRP 2.6.3.1 for first gen Kindle Fire
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I flashed that zip and it still says v2.0.0.0 in recovery