I have a KF1 I had bought off ebay to try to repair so I know I was pretty much throwing money away but it was a rather cheap buy so I went ahead and bought it. The condition was stated "Freezes" but overall physical appearance was near mint.
On receiving the KF it would not power up, no power light, no logo, no nothing. So I plugged it in let it charge for a while. Still no light or any response from hitting or holding the power button. So I thought maybe it has a bad usb connection/battery. Took it apart and got my Multimeter out and measured voltage at the battery. 3.7V while plugged in. Took the battery out and measured voltage at the charge port solder connections, can't remember what the reading was (3.7 - 4.1 ?) but I knew the port was undamaged anyway. Pulled out my factory cable and plugged it into my computer. Still nothing. No signs of life at all.
At this point I went and did some research and found the "Firekit LiveUSB kit 1.1" followed instructions and after several attempts finally got it to boot into recovery by shorting usb bootmode trick and using the "usb_fix_parts_and_install_fff_twrp" script. However I could not do much else. It would not mount anything. No sdcard, no cache, no system, no nothing.
I did some more research and found the How To thread for fixing failure to mount xxxxx. Followed those steps but nothing worked. when trying to run parted on /dev/block/mmcblk0 it would always say "unable to stat device" or something like that. I could not do much with the recovery that was loaded with the firekit either so I thought I would download the newest recovery and try that with the "usb_fix_parts_and_install_fff_twrp" script. Once I got a newer recovery up I could use the file manager and look inside /dev/block/. There was no mmcblk0 in there at all. all that was there was a bunch of "loop" files and "ram" files. nothing else.
I did some more research and found the EMMC curruption fix by Hashcode. Tried running that several times but would always have problems using the mmc_utils. It would always hang. I thought I would try anyway to leave the mmc_utils vendor 0 and vendor 4 commands running for 5 minutes each and continue with the next steps. Moving from the next steps in that forum I was not able to get into recovery. it would always stay at the TWRP splash screen (although ADB commands would still work).
At this point I was ready to give up. I shut everything down pulled the battery out and was looking to see if I could find any info on the motherboard. When I put the battery back in it booted up the kindle and got stuck in a bootloop of the Yellow triangle (FFF) then kindle logo. Before this I always had to do the usb boot shorting method to get it to boot, so at least I'm getting somewhere. I then used fastboot commands to perform oem format and flash the xloader, fff1.4a bootloader, and recovery. succeeded on all of those so I thought I had got it working. Rebooted device and it would get to the FFF1.4a blue kindle logo, I could then hit the power button and select recovery. Unfortunately it would just sit there and not do anything.
I rebooted the device and did the fastboot command to boot the recovery image. Stuck at TWRP splash just like before. Rebooted device again and this time used fastboot commands to flash recovery followed by boot the same recovery image I just used to flash the recovery. Success! was able to get into TWRP. But I'm still stuck! lol. Can't do anything with it since it cannot mount any partition. mmcblk0 or any other partition does not exist in /dev/block/. Can't even mount the sdcard yet somehow adb push xxx /sdcard works and I can view sdcard inside the file manager in recovery. Can't wipe anything, can't install anything. Always get errors. I was able to copy recovery log to sd card from the advanced menu and pull it to my computer with adb pull.
So as to the reason I'm posting this. What now? lol. I'm at a loss for what to do.
Since you apparently have access to fastboot and can flash new bootloader and recovery images, try flashing these as well and see if it makes any difference...
http://www.adrive.com/public/fAJGAH/KF1.system.boot.PAC.zip
soupmagnet said:
Since you apparently have access to fastboot and can flash new bootloader and recovery images, try flashing these as well and see if it makes any difference...
http://www.adrive.com/public/fAJGAH/KF1.system.boot.PAC.zip
Click to expand...
Click to collapse
No luck. farthest I can get is booting into recovery after I do the fastboot commands:
fastboot flash recovery twrp2610.img
fastboot boot twrp2610.img
note: I have to flash recovery before being able to use the boot command, otherwise it stays at the TWRP splash and goes no further.
flashing the boot and system images report success although for some reason both boot and system images write in 1.23s exactly each and say OKAY. I cannot issue any reboot commands through fastboot, they all cause the kindle to reboot with no display. Have to hard reset to get back to the bootloader. Cannot boot the kernel either using fastboot (boot.img you gave me).
I'm not much of a Linux person at all, but is there some commands I can try to get a detail on all the hardware devices detected? Seems weird that it always fails to mount everything as well as not detecting any partitions or emmc.
Jeffjb said:
No luck. farthest I can get is booting into recovery after I do the fastboot commands:
fastboot flash recovery twrp2610.img
fastboot boot twrp2610.img
note: I have to flash recovery before being able to use the boot command, otherwise it stays at the TWRP splash and goes no further.
flashing the boot and system images report success although for some reason both boot and system images write in 1.23s exactly each and say OKAY. I cannot issue any reboot commands through fastboot, they all cause the kindle to reboot with no display. Have to hard reset to get back to the bootloader. Cannot boot the kernel either using fastboot (boot.img you gave me).
I'm not much of a Linux person at all, but is there some commands I can try to get a detail on all the hardware devices detected? Seems weird that it always fails to mount everything as well as not detecting any partitions or emmc.
Click to expand...
Click to collapse
There is one option that I know of. A user in the KF2 forums was able to mount the eMMC to his Linux computer, but it's slightly more advanced than entering a few commands in the terminal. If no one else chimes in with the appropriate amount of knowledge, it may be your only option.
http://forum.xda-developers.com/showthread.php?t=2391047
http://forum.xda-developers.com/showthread.php?p=44873922
The motherboard is the same on both the KF1 and KF2 so the instructions for setting it up would be the same as well. Once mounted, you may have to repartition/reformat the device accordingly.
soupmagnet said:
There is one option that I know of. A user in the KF2 forums was able to mount the eMMC to his Linux computer, but it's slightly more advanced than entering a few commands in the terminal. If no one else chimes in with the appropriate amount of knowledge, it may be your only option.
http://forum.xda-developers.com/showthread.php?t=2391047
http://forum.xda-developers.com/showthread.php?p=44873922
The motherboard is the same on both the KF1 and KF2 so the instructions for setting it up would be the same as well. Once mounted, you may have to repartition/reformat the device accordingly.
Click to expand...
Click to collapse
I have been following those threads closely for a while; will try that method once I get more practice soldering lol. I appreciate all the help.
As an update I ran the command : dmesg | grep mmc0
message returned was: mmc0: error -110 whilst initialising MMC card
I guess that means its dead? Anyone else see something like that?
Related
So I was messing with my kindle and it was trying to upgrade it to jelly bean and i guess i missed one of the steps and bricked it. I was going through the process of unbricking but when i was trying to do extract the update.zip folder it would not allow me to because it could not mount the SD card. All i need to figure out how to do is get the SD slot mounted. I am slowly picking up on command prompt and still trying to figure out adb shell but that is all i need help with.
I can unbrick it if someone knows how i can get my kindle to mount back to my computer!
Any advice or step by step for it would be very helpful, Thanks guys
Could you be more specific as to how your Kindle is "bricked"?
soupmagnet said:
Could you be more specific as to how your Kindle is "bricked"?
Click to expand...
Click to collapse
I can only get to CWM. It does nothing but boot loop and does not go any farther then that. I can plug it into the computer and get the drivers connected and KFU can recognize it. when i put it in cwm this is the first thing i see
Forgive my redundancy but please describe the "boot loop". Does it just sit at the Kindle Fire logo? Does the Kindle Fire logo flash, or change brightness? Does it make it to the boot animation? Black screen?
soupmagnet said:
Forgive my redundancy but please describe the "boot loop". Does it just sit at the Kindle Fire logo? Does the Kindle Fire logo flash, or change brightness? Does it make it to the boot animation? Black screen?
Click to expand...
Click to collapse
It will go to the kindle fire logo and then it would go to a black screen. It makes no boot animation. It will change some brightness. The words kindle fire are in white and blue. It flashes where is needs to do the boot animation and then just goes to a black screen
dontgoback4cody said:
I can only get to CWM. It does nothing but boot loop and does not go any farther then that. I can plug it into the computer and get the drivers connected and KFU can recognize it. when i put it in cwm this is the first thing i see
Click to expand...
Click to collapse
The image shows a very low battery. The behavior you describe suggests a low battery. You're in a boot loop caused by no power.
Let it sit for several hours (better...over night).
Edit:...ie. let it sit with your charger attached.....
---------- Post added at 11:14 AM ---------- Previous post was at 10:46 AM ----------
dontgoback4cody said:
I can only get to CWM. It does nothing but boot loop and does not go any farther then that. I can plug it into the computer and get the drivers connected and KFU can recognize it. when i put it in cwm this is the first thing i see
Click to expand...
Click to collapse
It might be a good idea to consider installing TWRP rather than using CWM. CWM is known to have problems with some newer ROMs.
acii22 said:
The image shows a very low battery. The behavior you describe suggests a low battery. You're in a boot loop caused by no power.
Let it sit for several hours (better...over night).
Edit:...ie. let it sit with your charger attached.....
---------- Post added at 11:14 AM ---------- Previous post was at 10:46 AM ----------
It might be a good idea to consider installing TWRP rather than using CWM. CWM is known to have problems with some newer ROMs.
Click to expand...
Click to collapse
I have tried to install it from KFU but it is always has a problem doing so. I let it charge over night and it is still doing the same thing. Here is what is says when i try to install twrp
Replace the TWRP.img that comes with KFU, with the ACTUAL one from the TWRP website.
soupmagnet said:
Replace the TWRP.img that comes with KFU, with the ACTUAL one from the TWRP website.
Click to expand...
Click to collapse
Ok i did that but it still will not let me connect the kindle to the computer it keeps giving me sdcard errors. any idea how to fix the sd card issue?
Hey were u able to fix it??
Had the same problem with mine when I used TWRP to format my SD card..but was able to solve it..
What I did was a very simple thing..got the kindle recognised as a drive..used windows partition manager to format it
It worked.. I tx the stock and installed it
Try it and let me know
Sent from my MB526 using Tapatalk 2
I had the same problem before and only had to reboot the kindle.
Nothing is working. i have given up all hope. Like this is crazy. It is screwed up for good. I cant get it to mount. If anyone wants to take a shot at it just shoot me a pm with an address and we can discuss something about trying to fix it or what the hell i did to it. Its crazy! and really messed up.
dontgoback4cody said:
Nothing is working. i have given up all hope. Like this is crazy. It is screwed up for good. I cant get it to mount. If anyone wants to take a shot at it just shoot me a pm with an address and we can discuss something about trying to fix it or what the hell i did to it. Its crazy! and really messed up.
Click to expand...
Click to collapse
I have an Idea. If you have fastboot working on your computer. You could try flashing a rom from your computer by typing
fastboot -w(wipes device)
fastboot update <path to rom> (flashes rom)
If it works, you can then fix the sdcard easier with adb/shell/partition manager. Its worth a shot.
I also found this on a website
ROM update without SDcard
If you don't have an sd card, or your slot is broken you can try this trick, but you will need a custom recovery like Clockwork.
Boot up your phone to recovery. And move your rom file to the adb directory, and start a command line ( cmd )
adb shell
mount data
adb push D:\custom_rom.zip /data/
Wait until the push finised, and restart your device to recovery again with "adb reboot-bootloader"
mount data
mount /data /sdcard ( mount the data folder into your sdcard folder, so your recovery will think that you have an sdcard installed )
Locate the ROM .Zip file you wish to flash.
Confirm the flash by following the on-screen instructions (ie: pressing the trackball, pressing the call button, etc.)
If no errors arise during the flashing process then the ROM flash was successful, Reboot the device.
With some root file explorer, remove the rom file if you don't need it anymore, to free up space.
Or use adb to remove the custom recovery
adb shell rm data/custom_rom.zip
I will give it a shot. Only thing is i dont think there is even any software on here. when i try to get it into fastboot mode here is what it says.
Then you need a factory cable to get into fastboot.
dontgoback4cody said:
I will give it a shot. Only thing is i dont think there is even any software on here. when i try to get it into fastboot mode here is what it says.
Click to expand...
Click to collapse
Hey i had the same exact problem and i had posted what i did to recover it.. did you try..
I know it sounds too simple.. but it worked for me
sometimes its the way you have formatted ur sd card
kishorev said:
Hey i had the same exact problem and i had posted what i did to recover it.. did you try..
I know it sounds too simple.. but it worked for me
sometimes its the way you have formatted ur sd card
Click to expand...
Click to collapse
When you see the error message:
Code:
- exec '/system/bin/sh' failed: No such file or directory (2)
It means you don't have access to the shell in order to switch bootmodes and access recovery, which is needed to fix this type of problem. The only way to change bootmodes without access to the shell, is in fastboot. Unfortunately, you need access to the shell to change the bootmode to fastboot as well...catch-22.
For this, you need a factory cable. The factory cable will tell the device to boot into fastboot without the need for a shell. Even with a factory cable, and access to recovery, you'll still likely need to either reformat, or repartition your sdcard in order to get it to mount.
soupmagnet said:
When you see the error message:
Code:
- exec '/system/bin/sh' failed: No such file or directory (2)
It means you don't have access to the shell in order to switch bootmodes and access recovery, which is needed to fix this type of problem. The only way to change bootmodes without access to the shell, is in fastboot. Unfortunately, you need access to the shell to change the bootmode to fastboot as well...catch-22.
For this, you need a factory cable. The factory cable will tell the device to boot into fastboot without the need for a shell. Even with a factory cable, and access to recovery, you'll still likely need to either reformat, or repartition your sdcard in order to get it to mount.
Click to expand...
Click to collapse
You are right..
But i too was had the same msg when i was trying to fastboot it.. but then it worked.. I had formatted it and then tx the stock rom and flashed it..
Probably i missing something here..
Anyways thnx
Can't mount SD card on kindle fire
I was in a similar situation and after reading the various forums i came across this action "hold down the power button until the kindle goes off and continue to hold for about 30 seconds I believe this resets the kindle and then tick debugging and mount usb storage the sdcard will open on your pc" and then you can go from there. Worked for me so good luck.
I accidently erased everything from the KF2, all I have on it now is the recovery.
How can I get a rom back on the device?
When I plugged it in the computer under Device Manager it says Portable Devices >> F:/
When I go to my computer to try to enter f:/ its inaccessible.
How can I fix this?
Thanks!
Same issue here. Understood the instruction to wipe everything before installing ROM to mean "System" and "Internal Storage" as well. Now the downloaded ROM and "gapps" zip files are gone...
Found something called "ADB Sideload" in TWRP, could that help?
Like the OP, would appreciate some help. Kindle is a brick for now...
chipsndukes
Back Up & Running
First You need a Fastboot Cable.
Run The Recovery Tool. (Options 1 then 2)
When its completed unplug the Fastboot Cable and press and hold the power button until the KF2 turns off.
Turn it back on and you are all set to Root it!
Rooting
[ONE-CLICK] Automated Freedom-Boot and TWRP installer
OK, thanks LEGEND94, that helped !
Only difference to above: did not use a Fastboot cable to get into fastboot mode, rather fmkilo's technique here: http://forum.xda-developers.com/showthread.php?t=2117224
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Am restarting root and ROM flashing, hopefully will work this time.
Thanks again,
chipsndukes
chipsndukes said:
OK, thanks LEGEND94, that helped !
Only difference to above: did not use a Fastboot cable to get into fastboot mode, rather fmkilo's technique here: http://forum.xda-developers.com/showthread.php?t=2117224
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Am restarting root and ROM flashing, hopefully will work this time.
Thanks again,
chipsndukes
Click to expand...
Click to collapse
even though legend was OP, his method was a bit overkill, but totally fine.
Once you have recovery, or even the bootloader, you should NEVER need to restore. From the bootloader you can get into fastboot now, and from fastboot you can get the recovery.
As for putting files on, I'm not sure. I could look it up but you both got your issues solved. If someone coming here does need the help, PM me and I can look it up, but from what i remember on other android devices, usually the recovery somewhere has an option to mount USB like a storage device (probably bad wording there) but basically just like when you "turn on usb storage" in the android OS.
I am ASSUMING TWRP has something similar, and if I'm wrong, I'm sure you can always ADB to push the files onto the device from your PC in fastboot mode.
iytrix said:
even though legend was OP, his method was a bit overkill, but totally fine.
Once you have recovery, or even the bootloader, you should NEVER need to restore. From the bootloader you can get into fastboot now, and from fastboot you can get the recovery.
As for putting files on, I'm not sure. I could look it up but you both got your issues solved. If someone coming here does need the help, PM me and I can look it up, but from what i remember on other android devices, usually the recovery somewhere has an option to mount USB like a storage device (probably bad wording there) but basically just like when you "turn on usb storage" in the android OS.
I am ASSUMING TWRP has something similar, and if I'm wrong, I'm sure you can always ADB to push the files onto the device from your PC in fastboot mode.
Click to expand...
Click to collapse
Unfortunately usb Mount doesn't work in the kf2 twrp. I would love the option.
You CAN adb sideload from twrp though.
--
Sent from my Kindle Fire 2, CM 10.1
What I did above is the easiest way, the sideload didn't even work!
chipsndukes said:
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Click to expand...
Click to collapse
One change to the above statement. I did have to get out of fastboot mode, but it was confusing how because the terminal emulator was now gone.
I did this instead via a command window with the Fire plugged into the computer. I sent the "fastboot -i0x1949 oem idme bootmode 1" command while in the root directory for the KF2_SRT_10.2.3 restore package, there is a fastboot.exe file there.
Hope that helps.
chipsndukes
* WARNING: This post contains very loose instructions for COMPLETELY erasing the MMC chip on the Kindle Fire 1st Gen. USE WITH CAUTION *
THIS IS NOT FOR KINDLE FIRE 2 USERS WHO HAVE BRICKED IN SOME WAY. THIS IS FOR KINDLE FIRE 1ST GEN USERS WHO EXPERIENCED MMC CORRUPTION DUE TO UNFORSEEN CHANGES IN THE EARLY DEVELOPMENT OF THE 3.0 KERNEL.
----------------------
BACKGROUND:
So, yesterday I was in IRC and @Entropy512 mentioned they had found a leaked moviNAND spec sheet. This is some of the technical data for the mmc chip in our Kindle Fires:
http://web3032.sh1.magic2008.cn.m1.magic2008.cn/uFile/3032/201144131450191.pdf
In that spec sheet he pointed out CMD62 which is used to resize the boot0/boot1 partitions and a quote from the following paragraph (on page 11 of the PDF, section 4.1.3)
After setting the boot partition size, all of data in the moviNAND is removed. And the value of EXT_CSD [227:226] and SEC_COUNT is automatically changing. So user should be careful changing boot partition size.
Click to expand...
Click to collapse
He also pointed out a git location for the mmc-utils source code (a binary used to read/write/manipulate MMC via some of the pre-determined MMC_CMDs). And that in theory it should be possible to add some kind of command there to use CMD62 in a way to perform this "reset".
https://kernel.googlesource.com/pub/scm/linux/kernel/git/cjb/mmc-utils/
I forked this over to:
https://github.com/Hashcode/mmc-utils
Then, added a new variant to the command:
mmc_utils vendor <size> <device>
This implements CMD62 using the techsheet's instructions. And when run, it COMPLETELY ERASES the mmc chip. Everything goes. The partition tables, the boot0/boot1 contents and everything in your partitions. This should only be used if you have EMMC corruption caused by the early versions of the 3.0 kernel (You know if you have it).
----------------------
INSTRUCTIONS
Before using this, you want to backup your boot0/boot1 blocks if you can access them. They contain the MAC address info and serial #'s for your device. If you cannot access them, just know that you will need to generate a new mac and use idme to set it later, or you will have wifi issues. And you will never be able to use the Amazon OS due to security checks against the original serial # / MAC.
I'm going to paraphrase very loosely how I restored my Kindle using Ubuntu with adb already installed and configured (not going to cover that here):
Download all the files here and place them in 1 directory:
http://goo.im/devs/Hashcode/otter/unbrick
(NOTE: I've included 2 files created by @pokey9000 in this folder: aboot.bin and usbboot. He built them for use w/ Firekit. He's an awesome dev and deserves the credit for these files.)
[optional] You may or may not be able to boot to recovery depending on the emmc damage / current state of your Kindle. I recommend you try and adb pull as many of your partitions as you can for backup. To help you reboot successfully, I recommend trying the following at the very least from recovery (if you can get there):
adb pull /dev/block/mmcblk0boot0
adb pull /dev/block/mmcblk0boot1
Download TWRP for Kindle Fire 1st Gen and place this in the same directory (used with usbboot to enter recovery when there's no recovery on the device):
http://techerrata.com/file/twrp2/blaze/openrecovery-twrp-2.6.0.0-otter.img
To use usbboot to load recovery from USB go into the directory where you downloaded everything and run the following command:
Code:
./usb_boot_twrp
It should be waiting for USB connection to the device.
Now you need to take the cover of the device off and short the test point located here to the surrounding metal wall (using a paper clip or some other metal object):
http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51
This should trigger usbboot and it will attempt to load to recovery.
Once recovery is loaded:
(WARNING THE COMMANDS BELOW WILL COMPLETELY RESET YOUR EMMC CHIP. BE SURE YOU TRIED TO BACKUP BOOT0/BOOT1 ABOVE)
Code:
adb push mmc_utils /sbin
adb shell
mmc_utils vendor 0 /dev/block/mmcblk0
# (wait about a minute)
mmc_utils vendor 4 /dev/block/mmcblk0
# (wait another minute)
At this point your ENTIRE mmc has been erased and you should probably reboot w/ usbboot again but instead use this command:
Code:
./usb_boot_reformat
This resets your partition table to the stock Amazon layout. And then loads recovery.
Now, once back in recovery, the first thing you'll want to do is reformat the "media" partition:
Using TWRP go into "Wipe" -> "Advanced Wipe" -> checkbox "sdcard" and "Swipe to Wipe"
To format the "cache" partition as ext4 via adb:
Code:
adb shell
mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
mount /cache
exit
Then you can attempt to reload the initial set of partitions:
If you were able to backup the boot0/boot1 blocks above use this step. If not, skip this part and goto the next step.
Code:
adb push mmcblk0boot0 /sdcard
adb push mmcblk0boot1 /sdcard
adb shell
cd /sys/block/mmcblk0boot0
echo 0 > force_ro
cd /sys/block/mmcblk0boot1
echo 0 > force_ro
dd if=/sdcard/mmcblk0boot0 of=/dev/block/mmcblk0boot0
dd if=/sdcard/mmcblk0boot1 of=/dev/block/mmcblk0boot1
exit
Now we can restore the first set of partitions to make the device bootable to recovery:
Code:
adb push mmcblk0p1 /sdcard
adb push mmcblk0p2 /sdcard
adb push openrecovery-twrp-2.6.0.0-otter.img /sdcard
adb shell
dd if=/sdcard/mmcblk0p1 of=/dev/block/platform/omap/omap_hsmmc.1/by-name/xloader
dd if=/sdcard/mmcblk0p2 of=/dev/block/platform/omap/omap_hsmmc.1/by-name/bootloader
dd if=/sdcard/openrecovery-twrp-2.6.0.0-otter.img of=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
exit
At this point you *should* be able to reboot the device w/o the use of usbboot, and get a normal bootloader screen where you can use the power button to choose a recovery boot.
To complete your device recovery you need to find your preferred ROM (or download from http://get.cm/?device=otter), and place that on your sdcard and flash w/ gapps like any normal ROM install.
For those who couldn't restore the boot0/boot1 partitions, you will want to use the "idme" command to reset the following field, or else wifi will probably have issues.:
Code:
idme mac <a random MAC addr>
Enjoy.
PS. The instructions above were completely written from memory AFTER I had fixed my device. I'm looking for any comments / cleanup you might experience if you try these instructions.
RESERVED
Thanks Hash!
Very nice write up @Hashcode. Im just wondering what "unforseen changes" would you be talking about?
Sent from my TF300T using Tapatalk 4
tobiascuypers said:
Very nice write up @Hashcode. Im just wondering what "unforseen changes" would you be talking about?
Sent from my TF300T using Tapatalk 4
Click to expand...
Click to collapse
There were a few devices which were running a CWM recovery built from the initial 3.0 kernel back in May 2012. That kernel was not patched for MMC_CAP_ERASE, and on our emmc chip it caused a wear levelling bug which basically made the device unusable.
The entire thread is here:http://forum.xda-developers.com/showthread.php?t=1651413
This issue should not be hit by current Kindle Fire users.
Hashcode said:
There were a few devices which were running a CWM recovery built from the initial 3.0 kernel back in May 2012. That kernel was not patched for MMC_CAP_ERASE, and on our emmc chip it caused a wear levelling bug which basically made the device unusable.
The entire thread is here:http://forum.xda-developers.com/showthread.php?t=1651413
This issue should not be hit by current Kindle Fire users.
Click to expand...
Click to collapse
This is a major victory in the fight against Superbrick.
Unfortunately, the users hit hardest by the Superbrick bug (Samsung Galaxy S2 family) have devices that cannot be USB-booted in any way.
Also, you might want to rename the command to be more descriptive. "vendor" could be anything - this is a very specific vendor command sequence here.
Entropy512 said:
This is a major victory in the fight against Superbrick.
Unfortunately, the users hit hardest by the Superbrick bug (Samsung Galaxy S2 family) have devices that cannot be USB-booted in any way.
Also, you might want to rename the command to be more descriptive. "vendor" could be anything - this is a very specific vendor command sequence here.
Click to expand...
Click to collapse
Yeah I'll probably set it up "mmc_utils vendor bootsize <size> <device>" as there is a report summary I may add later.
@Hashcode my device suffered from the brick but i could "fix" it, but i lost some blocks on my partitions. I had to shrink some partitions, so i could use the device again.
Doing this process can fix this for me, will i have back all my partition size right?
vbdss said:
@Hashcode my device suffered from the brick but i could "fix" it, but i lost some blocks on my partitions. I had to shrink some partitions, so i could use the device again.
Doing this process can fix this for me, will i have back all my partition size right?
Click to expand...
Click to collapse
It should. Unlike workarounds that avoid touching damaged areas, this resets the chip so completely that the corrupted wear leveller data structures are reset. At least that was the theory, and Hashcode's results with his Superbricked KFire confirm that this appears to be the case.
Entropy512 said:
It should. Unlike workarounds that avoid touching damaged areas, this resets the chip so completely that the corrupted wear leveller data structures are reset. At least that was the theory, and Hashcode's results with his Superbricked KFire confirm that this appears to be the case.
Click to expand...
Click to collapse
Great! Now all we have to do is get him to brick his HD
Wow cool!
I had this exact problem back in days. You've helped me on that and most user find out that it was probably a emmc bricked problem.
Fortunately, I had no problem to get a new one from amazon. I was happy after weeks working on it. I even tried to restore it from knoppix.
For now, I'm running the most recent roms on the board, hope this problem will never come back.
If it does, you'll be my hero.
Greetings, @Hashcode!
Got bricked Kindle Fire 1st Gen with also cracked battery pins, so I can't even tell if my battery is working or not. Battery is working. Tried this new method and got this:
Code:
./usb_boot_twrp
Loading bootloader through USB...
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
Loading TWRP through fastboot...
< waiting for device >
Should I try few more times or is battery some internal/external loose connection the cause of problem (e.g can't power on screen/something, load bootloader, enter fastboot, load TWRP, etc.)?
Thank you very much. Miss you and your work since that brick.
alarien said:
Greetings, Hashcode!
Got bricked Kindle Fire 1st Gen with also cracked battery pins, so I can't even tell if my battery is working or not. Tried this new method and got this:
Code:
./usb_boot_twrp
Loading bootloader through USB...
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
Loading TWRP through fastboot...
< waiting for device >
Should I try few more times or is the battery the cause of problem (e.g can't power on screen, load TWRP, etc.)?
Thank you very much. Miss you and your work since that brick.
Click to expand...
Click to collapse
When you get to that point, leave the script running, power the device completely down, and put the device into usbboot again.
soupmagnet said:
When you get to that point, leave the script running, power the device completely down, and put the device into usbboot again.
Click to expand...
Click to collapse
Unfortunately, that didn't work.
I think, before loading recovery, we send bootloader on the device for a reason.
Thank you for your help and thoughts, anyway.
Edit. Also, I can feel that on
Code:
Loading TWRP through fastboot...
< waiting for device >
step chipset is warm (memory and CPU, at least) and power button LED is on and green.
my kindle has become bricked im not really sure but if i plug it in it says device not recagnized and it only boots to the kindle fire logo and sits there any idea what i can do? any help is appreciated
alarien said:
I think, before loading recovery, we send bootloader on the device for a reason.
Thank you for your help and thoughts, anyway.
Click to expand...
Click to collapse
What does that have to do with anything that I said?
Just tinkering around and testing various things on my device, I've used usbboot w/shorting trick to replace my bootloader and recovery more times than I care to imagine. In maybe 80% of those cases, I've run into the exact same problem that you are dealing with right now.
When you put the device in usbboot using the shorting trick, fastboot is only available for a short period of time, which is why the script sometimes hangs at "waiting-for-device". When this happens, you have to power the device completely off, unplug it, then put it in usbboot with the shorting trick to get fastboot working again. Once fastboot is available, the script will pick up where it left off.
If you aren't getting the right results, there's a good chance you're not doing it correctly. Timing and technique have a lot to do with whether or not it will work properly, and many times you'll have to go through the same process over and over again before getting it right.
I'm willing to bet that your cracked battery pin has nothing at all to do with the fact that you have been unsuccessful in your attempts to restore the device, unless you are (for some strange reason) trying to unplug it beforehand.
Oh, and you might want to be sure to check the md5sums of the files you downloaded to make sure you don't have any corrupted files.
[Edit:] The fact that your first and second stage bootloaders have been installed and your power LED is lit, suggests that there is something wrong with your display, or that you may have a loose connection somewhere (not in your battery). If you have a factory cable, plug it in and see if you get a response from...'fastboot getvar product'
soupmagnet said:
What does that have to do with anything that I said?
Just tinkering around and testing various things on my device, I've used usbboot w/shorting trick to replace my bootloader and recovery more times than I care to imagine. In maybe 80% of those cases, I've run into the exact same problem that you are dealing with right now.
When you put the device in usbboot using the shorting trick, fastboot is only available for a short period of time, which is why the script sometimes hangs at "waiting-for-device". When this happens, you have to power the device completely off, unplug it, then put it in usbboot with the shorting trick to get fastboot working again. Once fastboot is available, the script will pick up where it left off.
If you aren't getting the right results, there's a good chance you're not doing it correctly. Timing and technique have a lot to do with whether or not it will work properly, and many times you'll have to go through the same process over and over again before getting it right.
I'm willing to bet that your cracked battery pin has nothing at all to do with the fact that you have been unsuccessful in your attempts to restore the device, unless you are (for some strange reason) trying to unplug it beforehand.
Oh, and you might want to be sure to check the md5sums of the files you downloaded to make sure you don't have any corrupted files.
[Edit:] The fact that your first and second stage bootloaders have been installed and your power LED is lit, suggests that there is something wrong with your display, or that you may have a loose connection somewhere (not in your battery). If you have a factory cable, plug it in and see if you get a response from...'fastboot getvar product'
Click to expand...
Click to collapse
I'm sorry, didn't mean to sound rude at all.
I just thought that usbbooting bootloader is making fastboot available and if my device is Superbricked, the bootloader will not be saved after complete power off. So fastboot will not be available on next usbboot. @Hashcode may correct me, though.
MD5 checked, of course.
You think, before loading bootloader/accepting fastboot commands, it checks availability of the display? I'll check my connection, you mean PC to device or some internal parts of the device? Unfortunately, I got no fastboot cable, it would be simple otherwise.
Thank you very much once more. Will try further. Your help is greatly appreciated.
Edit. Used another USB cable, result is the same.
Also tried another bootloaders, fff-1.4a and pokey9000's u-boot.bin from FireKit with the same result except for no LED at all.
To exclude timing problem, also opened 2 Terminal windows with
Code:
sudo ./usbboot ./aboot.bin ./fix2-u-boot.bin
and
Code:
sudo fastboot boot ./openrecovery.img
Didn't worked as well.
Tried for approximately 100 times with no luck.
Just can't get into fastboot mode.
Please, tell me, what else can I do? Is there another way, except getting fastboot cable?
One more update.
So, I just got fasboot cable. Tried simply plugging it in when device is completely off with no luck.
Also, tried plugging it in with the shorting trick, running ./usb_boot_twrp script with the same output as if I was using regular USB cable. Also, no response from
Code:
fastboot getvar product
.
May it be a sign of totally bricked eMMC chip = no bootloader to enter fastboot, or should fastboot cable work without bootloader?
And if some parts of the device is broken (eg, display) would it be possible to add/remove check of them from the bootloader? As LED seems working, simple blinking if something is broken and bootloader can't be loaded would be enough.
What should I try next?
alarien said:
One more update.
So, I just got fasboot cable. Tried simply plugging it in when device is completely off with no luck.
Also, tried plugging it in with the shorting trick, running ./usb_boot_twrp script with the same output as if I was using regular USB cable. Also, no response from
Code:
fastboot getvar product
.
May it be a sign of totally bricked eMMC chip = no bootloader to enter fastboot, or should fastboot cable work without bootloader?
And if some parts of the device is broken (eg, display) would it be possible to add/remove check of them from the bootloader? As LED seems working, simple blinking if something is broken and bootloader can't be loaded would be enough.
What should I try next?
Click to expand...
Click to collapse
Believe it or not, there is no such thing as "totally bricked". The usbboot solves that for us. If done correctly, it will boot your device to a usable state and you can re-write literally every partition from backups.
I'm sort of with @soupmagnet on this one. Booting from usbboot is alot about timing and technique. If it doesn't look like it's working then it's best to long press the power button and try it again. I have the fortunate ability to watch serial output while it's coming up, so I immediately know if usbboot is working or not. For the normal user it will be trial and error.
Definitely give it another shot.
Thank you very much.
I will try more. If I correctly understand you, usbboot and fastboot is a single process in this case and despite of usbboot success ("sending image to target" message) and green LED etc. almost every time I try it, if fastboot commands (e.g. "fastboot boot ./recovery.img") failed on "waiting for device" message, than whole "usbboot" process is failed, too.
And one more question, is fastboot cable useless for now, until chip is fixed?
Thank you once more for your time. I'm sorry if my questions are too stupid.
When I boot to twrp in recovery, I am unable to accomplish anything -- wipe or install. When I try to do either I get an error about "unable to mount sdcard". I have seen this thread, but cannot find the zip mentioned anywhere. I am able to run "adb push" to /sdcard and then to actually see the file pushed there in twrp recovery. I'm just not able to do anything with the pushed file in the install function.
Tried mounting with adb shell, but kept getting error of "Invalid argument". Did discover that /sdcard is /dev/block/mmcblk0p36, and using fdisk in adb shell found that it "doesn't contain a valid partition table". I'm not concerned about losing data. Everything was backed up, but anybody know how to create the correct partition table so I can install a ROM?
Original post:
So I screwed up. I rooted my phone according to this post. Unfortunately I then did something stupid when trying to flash a new recovery and get actual SU privileges to remove bloatware. Instead of going back to the first page in that thread and seeing the links to use there, I followed this guide. Unfortunately, when I ran the script, install-insecure-linux.sh, it flashed the boot.insecure.img and then spit out errors related to incompatibility with the ncurses version on my laptop. It seems difficult if not impossible to downgrade the ncurses without causing a ton of other headaches. It went to reboot and just stayed dead.
Thought I was hosed, but then after charging for a while I got signs of life. Managed to boot to fastboot. Connected back up to the laptop and decided to follow the cyanogenmod guide for installing CM11. Flashed the CM recovery img file successfully but after rebooting I can't do anything.
I still occasionally get into the fastboot on the phone. Running fastboot devices on the laptop lists the phone. Running adb devices does not. Running any other fastboot command sticks at either nothing or <waiting for device>. Running any adb command gives "error: Device not found". I added a udev rule and adb_usb.ini with the device id "0bb4" and mode 0666, but no joy.
I only have a linux machine available at the moment, so I'd prefer suggestions for working in linux. If someone knows of a good Windows solution, I can probably try that in a few days. Thanks in advance.
EDIT: Progress
Noticed that for a second when I first connect to the laptop USB the fastboot menu showed in red FASTBOOT USB before going back to just FASTBOOT. Managed to tee up the command for flashing the twrp recovery img and ran it immediately upon plugging in. Was then able to boot to recovery. Not sure what my next step to getting a working phone is though. Help still appreciated.
My last post got swallowed by the ether I guess. I was able to fix it by formatting the sdcard using mkdosfs -F 32 -n INT_SD -s 64 /dev/block/mmcblk0p36. Then rebooting, wiping, and installing CM11. All is good again.
I've searched this and other forums, and tried virtually everything that has been suggested or that I can think of.
I have a Zenfone 2 Laser ZE551ML rooted. Phone has worked like a dream. Installed TWRP 3.0, made and saved several backups in several different places, internally and externally.
Two days ago, flashed a TWRP recovery (I was looking to get back some data I had deleted inadvertently), seemed to go well until it booted, and could not get past the screen that says "Fastboot Mode!!!". Connected to a PC and was able to execute fastboot commands; supposedly can flash various recoveries, and seemingly does so, with everything looking right on the PC, and the phone actually rebooting. But always stops at the same screen.
ADB, on the other hand, shows no devices listed. Every command results in "Error: Missing Device."
I have done everything I can think of...uninstalled and reinstalled the ADB drivers, used different ADB drivers, removed the external SD card, removed the battery (which is the ONLY way the phone will shut off...pressing the on/off button for 10 seconds just results in it booting up to the same screen. Have tried the fastboot wipe command, again it seems to do so, but always comes back to the same screen. Fastboot flashing a recovery.img appears to successfully write a recovery, then goes to same screen upon reboot.
Any ideas? I've only had this phone a couple of weeks, and really like it. But flashing what was apparently a bad TWRP backup seems to have destroyed it.
Thanks so much for any suggestions!
i have the same problem.. please help!
i have the exact same problem you had.. please tell me how you restored it
As i have a similar problem i cannot help you on the technical side.
But isn't the laser 551 KL instead of ML. Maybe you flashed the wrong files trying to restore the phone
BeachNYC said:
I've searched this and other forums, and tried virtually everything that has been suggested or that I can think of.
I have a Zenfone 2 Laser ZE551ML rooted. Phone has worked like a dream. Installed TWRP 3.0, made and saved several backups in several different places, internally and externally.
Two days ago, flashed a TWRP recovery (I was looking to get back some data I had deleted inadvertently), seemed to go well until it booted, and could not get past the screen that says "Fastboot Mode!!!". Connected to a PC and was able to execute fastboot commands; supposedly can flash various recoveries, and seemingly does so, with everything looking right on the PC, and the phone actually rebooting. But always stops at the same screen.
ADB, on the other hand, shows no devices listed. Every command results in "Error: Missing Device."
I have done everything I can think of...uninstalled and reinstalled the ADB drivers, used different ADB drivers, removed the external SD card, removed the battery (which is the ONLY way the phone will shut off...pressing the on/off button for 10 seconds just results in it booting up to the same screen. Have tried the fastboot wipe command, again it seems to do so, but always comes back to the same screen. Fastboot flashing a recovery.img appears to successfully write a recovery, then goes to same screen upon reboot.
Any ideas? I've only had this phone a couple of weeks, and really like it. But flashing what was apparently a bad TWRP backup seems to have destroyed it.
Thanks so much for any suggestions!
Click to expand...
Click to collapse
fastboot --cmdline "lge.kcal=0|0|0|x" boot twrp.img
where TWRP.img is the directory of twrp
then you should get back to TWRP
flash TWRP image again in TWRP itself because the method on line 1 only temporary flashes TWRP and will auto discard TWRP after a reboot