Related
I've looked around the forums and I am not finding instructions on how to unbrick a Kindle Fire that has ClockworkMod installed. I installed ClockworkMod and installed a late ICS build with kernel 3.0 and the Fire is stuck in an infinite boot loop with the Kindle Fire/Android mascot logo.
I can get into ClockworkMod but re-flashing with the CM9 that I have doesn't do anything to fix it.
I know that if I were able to put the stock Kindle firmware on that /sdcard volume I can fix this but how do I do this with ClockworkMod?
I've tried all the unbricking utils (even the Java front-end) and they act like they're fixing things but they all make no changes.
I do have the correct drivers and can send adb commands to fastboot, normal boot, recovery boot, so I'm pretty sure I'm just missing how to unbrick a Kindle that is using ClockworkMod.
Thanks in advance.
aegrotatio said:
I've looked around the forums and I am not finding instructions on how to unbrick a Kindle Fire that has ClockworkMod installed. I installed ClockworkMod and installed a late ICS build with kernel 3.0 and the Fire is stuck in an infinite boot loop with the Kindle Fire/Android mascot logo.
I can get into ClockworkMod but re-flashing with the CM9 that I have doesn't do anything to fix it.
I know that if I were able to put the stock Kindle firmware on that /sdcard volume I can fix this but how do I do this with ClockworkMod?
I've tried all the unbricking utils (even the Java front-end) and they act like they're fixing things but they all make no changes.
I do have the correct drivers and can send adb commands to fastboot, normal boot, recovery boot, so I'm pretty sure I'm just missing how to unbrick a Kindle that is using ClockworkMod.
Thanks in advance.
Click to expand...
Click to collapse
When you say "infinite bootloop" do you mean the device turns on, shows the boot logo, then reboots?
If so... http://forum.xda-developers.com/showthread.php?p=25400963
Also CWM will not work with the latest versions of ICS, you need to flash TWRP.
I recommend people copy both the Kindle standard image as well as the customized image to the /sdcard volume. That way if you're stuck with a bricked Kindle at least you can re-install the original Kindle image and get back to where you were before.
I ordered a factory cable to get it to boot into factory recovery mode, which I know works in all cases.
In the meantime I'm going to attempt to try the steps in that post.
After that I'll try to mount the original Kindle system image from a USB drive (using the USB boot feature of CWM) and then try to install it from there and then go back to TWRP or FireFireFire.
I've successfully used FireFireFire before, but using CWM bricked my Kindle hard. I'll update this thread when it's working again.
Thanks for the info.
Okay, I successfully unbricked it.
It wasn't so much a hard brick or a soft brick but more of a firm bricking.
I went into CWM and told it to mount the USB volume. The 5 gigabyte drive appeared on my computer and I formatted it.
I took the Amazon stock update and changed its file extension to zip.
I then copied it from the computer to the mounted volume.
I chose the zip for installation and then installed it from CWM.
After shutting down and rebooting a few times it worked.
I didn't even have to do any ADB tricks. This is because I had a working CWM boot image.
Now it's off to more hacking!!
I am having the same problem... how did you get into clockwork? it doesnt stay on long enough for me to connect it to the KFU
I did the same thing. You'll need to go into CWM and mount it as usb storage and then it will show up on your desktop as a disk drive. Format it from there to wipe out the crap that's hanging it up and then reinstall either your rom or stock amazon rom.
HaNNibalHector said:
I am having the same problem... how did you get into clockwork? it doesnt stay on long enough for me to connect it to the KFU
Click to expand...
Click to collapse
I am int he same boat. How did you or can I get into Clockwork
I'm not very knowledgeable about CWM but I do have an idea. Try turning off kindle by holding down power button, plug kindle in to computer and turn it on. Open KFU, if it says that adb is online, then you have your fix. Just set the boot mode to recovery and you should boot right in to cwm.
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
My Kindle was rooted but I decided to try my hand at installing a custom ROM. However, the ROM I tried would not work and the screen stayed black. However, thanks to TWRP I could install Kindle from Amazon again. The installation went thru smoothly, or so I thought. Now, when I boot the Kindle, I see the Kindle Fire Logo and it stays there. The Computer can see the Kindle as an Android device, Android Composite Device. But Kindle Fire Utility cannot see it so I could try and re-install it again. Any suggestions?
Lacking information, so I'll just fill the voids with assumptions.
I *assume* you didn't wipe cache, dalvik-cache and most important when switching from a ROM to another, Factory Reset - this is the reason said custom ROM wouldn't work, and the reason flashing back update.zip (as you said you installed it, rather than restoring a backup) caused your KF to get stuck in a semi brick.
The most important question here is, do you have FFF installed?
If you do, fixing this is trivial. Just get into TWRP from FFF, wipe cache, dalvik-cache and factory reset and then install whatever ROM you'd like to try or use.
If you don't have FFF installed, then your solutions are to either get a factory cable (recommended) or to crack open the case and do the USB pin short trick. From there you can use fastboot to install FFF and boot into TWRP.
Alternatively, you can try "fastboot getvar product" or "adb shell idme bootmode 5001" to see if you get lucky.
Dasanko said:
Lacking information, so I'll just fill the voids with assumptions.
I *assume* you didn't wipe cache, dalvik-cache and most important when switching from a ROM to another, Factory Reset - this is the reason said custom ROM wouldn't work, and the reason flashing back update.zip (as you said you installed it, rather than restoring a backup) caused your KF to get stuck in a semi brick.
The most important question here is, do you have FFF installed?
If you do, fixing this is trivial. Just get into TWRP from FFF, wipe cache, dalvik-cache and factory reset and then install whatever ROM you'd like to try or use.
If you don't have FFF installed, then your solutions are to either get a factory cable (recommended) or to crack open the case and do the USB pin short trick. From there you can use fastboot to install FFF and boot into TWRP.
Alternatively, you can try "fastboot getvar product" or "adb shell idme bootmode 5001" to see if you get lucky.
Click to expand...
Click to collapse
I tried the USB pin short trick but now my Kindle won't turn on at all nor will it charge. Thanks anyways!
i have similar problem ......please need help
After successfully rooting kf with kfu and making a backup ... I did factory reset and flashed a custom rom ... now kindle is stuck on " kindle fire" logo and just keeps flashing and rebooting . My computer recognizes it as android phone ( android adb ) and kfu does too but only for a couple of seconds . During those few seconds I try recovery ... fast boot ...normal boot... n none seem to work . Kf just reboots n returns to boot loop . Any advice is appreciated .. thanks
Start a new thread when you're posting your own issues.
What colour is the "kindle fire" logo when you turn on your KF?
Force Kindle into Fastboot
Ok, so I have finally got my Kindle to turn on, using the USB Short Trick. Now my only question is about getting the Kindle to boot into fastboot mode so I can re-format the sdcard partition and finally load a new ROM. I have tried several different commands and they all seem to miss the window of opportunity to start the kindle in fastboot mode. Is there any way, short of a factory cable, that one can make the kindle start in fastboot mode?
Not fastboot get var
ComputerGenuis2.0 said:
Ok, so I have finally got my Kindle to turn on, using the USB Short Trick. Now my only question is about getting the Kindle to boot into fastboot mode so I can re-format the sdcard partition and finally load a new ROM. I have tried several different commands and they all seem to miss the window of opportunity to start the kindle in fastboot mode. Is there any way, short of a factory cable, that one can make the kindle start in fastboot mode?
Click to expand...
Click to collapse
fastboot getvar product doesn't seem to do the trick. The kindle seems to be in fastboot mode but the adb shell cannot access the device.
The problem is that you don't have the fastboot drivers installed (also, ADB will not work while fastboot is active) - Windows is painfully slow at detecting a device and installing its drivers, so by the time it even notices anything, the fastboot window is already over.
To solve this, use firekit: http://forum.xda-developers.com/showthread.php?t=1430038
The script that will probably suit your needs the most is usb_install_fff_twrp.
Used Firekit
Dasanko said:
The problem is that you don't have the fastboot drivers installed (also, ADB will not work while fastboot is active) - Windows is painfully slow at detecting a device and installing its drivers, so by the time it even notices anything, the fastboot window is already over.
To solve this, use firekit: http://forum.xda-developers.com/showthread.php?t=1430038
The script that will probably suit your needs the most is usb_install_fff_twrp.
Click to expand...
Click to collapse
I have TWRP and FFF installed. However, upon booting into TWRP, the sdcard partition cannot be mounted, to the Kindle that is, and as such, I cannot mount the sdcard to the computer. When I researched this some more, I found that I can fix this by using a command via adb shell. The guide instructed using fastboot to achieve this. When would be the best time to use adb shell?
What's the output of partitions.txt? (type the following from TWRP)
adb shell parted /dev/block/mmcblk0 p > partitions.txt
Can't use adb
Dasanko said:
What's the output of partitions.txt? (type the following from TWRP)
adb shell parted /dev/block/mmcblk0 p > partitions.txt
Click to expand...
Click to collapse
The problem at hand is using adb. I can never time it exactly right to open adb. I always get an "error: device not found". Windows even recognizes that Android ADB Interface is plugged in.
Okay, things are getting awfully confusing here.
What exactly is it that you can do and that you cannot do?
For example, are FFF and TWRP functional?
GOT IT!
Thank you! I finally figured out that the wrong driver had reinstalled and that was causing my computer to not be able to use adb shell. I fixed that and voila, I am now running CM9. Thanks again!
I tried to flash my Kindle Fire and I forgot to flash it system. Then the bootanimaton took to long and I wiped the whole thing in TWRP. Then It would nt mount to my computer despite adding the drivers. Then I put it into fastboot. Also Adb wont work. HELP ME PLEASEEEEEEEE
If possible team viewer.
TWRP ok but no OS?
Did you wipe data in TWRP and no OS? Actually ADB will work if you let it boot to blue kindle file logo and let it sit there. If adb is working and your device is detected:
1. adb push <rom name>.zip /data/media , do the same process in gapps (Rom should already in the same folder as adb/fastboot files)
2. boot to TWRP and install rom.
If you boot to TWRP and can't find your rom during install even though push via adb success restore your kindle using the steps below:
1. Go to advance and terminal command and select any folder then enter fastboot -i0x1949 oem idme bootmode 1. Reboot, fastboot should be working.
2. Plug in to you PC and your device should be recognize, if not install kindle drivers (search this forum you can easily find it). You can check if your device was detected by typing fastboot -i0x1949 devices. You can also check by going to devices and printers in windows your device should register as Fastboot or Otter*** something like that. If you see this move to the fun part:
3. follow this thread http://forum.xda-developers.com/showthread.php?t=2096888, don't be afraid to read the very long steps since it's very easy it took me less than 30 mins to restore my kindle. You should restore your kindle back to stock.
4.If restore success, root your stock kindle using the same tool above in this point you should already at ease in using the tool. If you get the flickering screen in rooting don't mind it, it should be gone after few restart or you're gonna reinstall cm10 anyway.
5.Your SDCARD should now be detected by your pc, transfer the ROM/Gapps to SD.
6.Install TWRP using the tool above or the apk file (I use this apk file since I already tried that it's working). Device will reboot and boot to TWRP
7.Install custom ROM and do not wipe data if you don't want to redo the same process again
and you're done!:good:
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.