i tried to partition my kf using fireparted and inevitably, i failed. now the kindle is stuck on the cm9 booting screen. while browsing the forums for a solution, i saw that fastboot oem format might fix it. i know this is a noob question but, how do i issue the command?
Related
hi
I was attempting (ok tempting fate) repartitioning my app space using the fireparted utility (yeah, I know it breaks stuff) and you guessed it... (it broke stuff)
So my partitions 10 and 11 are now gone.
How do I restore the partitions back to oem? I read about using firefirefire to do it, but I dunno what I'm doing. can someone walk me through it?
I have adb access, and I have the latest firefirefire I think (I ran kfu and it said it installed and I noticed my boot logo changed to the green android over Kindle Fire)
I tried running fastboot oem format and it gave me:
... FAILED (remote failure)
but it could be I just don't know how or when to run it.
I did a fastboot devices and right now it's giving me
0123456789ABCDEF fastboot
Thanx for your help.
berighteous said:
hi
I was attempting (ok tempting fate) repartitioning my app space using the fireparted utility (yeah, I know it breaks stuff) and you guessed it... (it broke stuff)
So my partitions 10 and 11 are now gone.
How do I restore the partitions back to oem? I read about using firefirefire to do it, but I dunno what I'm doing. can someone walk me through it?
I have adb access, and I have the latest firefirefire I think (I ran kfu and it said it installed and I noticed my boot logo changed to the green android over Kindle Fire)
I tried running fastboot oem format and it gave me:
... FAILED (remote failure)
but it could be I just don't know how or when to run it.
I did a fastboot devices and right now it's giving me
0123456789ABCDEF fastboot
Thanx for your help.
Click to expand...
Click to collapse
"fastboot oem format" is only available on FFF versions 1.1 and greater. Version 1.0 (i.e. the one installed by TWRP 2.0.0) does not have this feature.
Install this first: http://forum.xda-developers.com/showthread.php?t=1541043
Then try fastboot oem format
Thanks. When it happened I went to KFU and installed the latest firefirefire, and then went to install latest twrp, which must have downgraded firefirefire back. D'oh.
I knew I must have been missing something simple.
I ran the oem format and then restored a backup I had on it. So it looks like it's working again. Thanks.
I was really hoping to find a better way of repartitioning the apps space. 1gb is not enough by a long shot.
I used Hashcode's method to install a second bootloader and to install recovery and CM10.1. After I flashed CM10.1 like normal, I didn't like it, as the screen resolution was way out of whack. So, I restore using fastboot the stock .img backups that I created prior to rooting.
Well, now my Kindle gets stuck on the Kindle splash screen, and no matter what I do to flash stock back onto it, every time it reboots, it has the same problem. I have tried the KFHD restore tool (none of the commands work), KFFirstAide (the same problem as KFHD restore), I even tried doing the rooting process again, with the same results. I cannot get this cursed device to boot into stock OS, and I have burned out on trying to fix it. I've had this thing for one day.... :crying:
ironbesterer said:
I used Hashcode's method to install a second bootloader and to install recovery and CM10.1. After I flashed CM10.1 like normal, I didn't like it, as the screen resolution was way out of whack. So, I restore using fastboot the stock .img backups that I created prior to rooting.
Well, now my Kindle gets stuck on the Kindle splash screen, and no matter what I do to flash stock back onto it, every time it reboots, it has the same problem. I have tried the KFHD restore tool (none of the commands work), KFFirstAide (the same problem as KFHD restore), I even tried doing the rooting process again, with the same results. I cannot get this cursed device to boot into stock OS, and I have burned out on trying to fix it. I've had this thing for one day.... :crying:
Click to expand...
Click to collapse
Do you have a factory cable or is your KFHD an 8.9"?
soupmagnet said:
Do you have a factory cable or is your KFHD an 8.9"?
Click to expand...
Click to collapse
Sorry, I should've specified. Yes, it is an 8.9"
Code:
ironbesterer said:
Sorry, I should've specified. Yes, it is an 8.9"
Click to expand...
Click to collapse
Which splash to you become stuck at? White and orange logo or white and blue? If you get stuck at the white and orange it is a stack installation failure. If you get stuck at the white and blue logo the system is likely broken. Can you access recovery? Get it into fastboot and try
Code:
fastboot -i 0x1949 erase cache
Code:
fastboot -i 0x1949 erase userdata
at the userdata part it could hang just let it sit for ten minutes or so. Then
Code:
fastboot -i 0x1949 reboot
side note this will wipe your sdcard so all backups and rom files will be gone. So best you transfer all you wish to keep to your pc.
Thepooch said:
Code:
Which splash to you become stuck at? White and orange logo or white and blue? If you get stuck at the white and orange it is a stack installation failure. If you get stuck at the white and blue logo the system is likely broken. Can you access recovery? Get it into fastboot and try
Code:
fastboot -i 0x1949 erase cache
Code:
fastboot -i 0x1949 erase userdata
at the userdata part it could hang just let it sit for ten minutes or so. Then
Code:
fastboot -i 0x1949 reboot
side note this will wipe your sdcard so all backups and rom files will be gone. So best you transfer all you wish to keep to your pc.
Click to expand...
Click to collapse
With a lot of persistence, I finally restored it. I had to use KFFA. It was ver likely that it was a stack failure, as when I was using Hashcode's method to root, I never pushed a new stack (because adb wasn't working).
But all is good now, I fixed it! :victory:
After the fact
I suppose it's not much a help now but using fastboot has helped me a lot with my kindle. I've locked it up several times to the point I thought it was broken. Usually it seems if you can turn it on and you see anything, you still can fix it.
I got a KFHD 2G (2013) from a friend and the problem was simple: when the lock screen came up, he couldn't enter in his passcode because the keyboard wouldn't show up. There was no way to get into ADB since I couldn't get in. I tried to do a factory reset via recovery, but there is no recovery. I built a fastboot cable and tried "fastboot -w" but the partitions could not be formatted. This device seems completely screwed, I trued grabbing the factory update from amazon, but it's in BIN format and won't flash in Fastboot. Inside the BIN file, it seems to just be a recovery-flashable zip, however, it will not boot into recovery so i can't install it. Fastboot reports that two .txt files are missing. I tried extracting recovery.img from the zip and booting it as a ramdisk, however, this just causes it to boot normally. I ended up flashing userdata with boot.img as a way of formatting it, which got the keyboard back, but puts it on a screen saying "Enter password to decrypt Kindle." The password, "LOVE" is not accepted and entering 4 incorrect codes does not prompt a format. I'm at a loss here, it seems like it's just nt possibe for this thing to be screwed completely, but im out of options. what should i do?
HELP!!!
Also, I just realized this thread should be in "7" Kindle Fire HD Q&A, Help & Troubleshooting"
Um so now it's to the point where it's asking to format it because the password is wrong so wouldn't that be the same as formatting it as you had intended on doing earlier? BTW fastboot commands on a kindle fire have to be prefixed with "fastboot -i 0x1949", also I don't know off hand if that command you were going to run is a user data wipe or a complete wipe and a complete wipe would been bad. So at this point if the lock screen asks you to format it and you don't have adb enabled then you probably will have to format it, I thought the new gen had adb access from early on in the boot process but I could be wrong, I suggest looking in the hdx section.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Um so now it's to the point where it's asking to format it because the password is wrong so wouldn't that be the same as formatting it as you had intended on doing earlier? BTW fastboot commands on a kindle fire have to be prefixed with "fastboot -i 0x1949", also I don't know off hand if that command you were going to run is a user data wipe or a complete wipe and a complete wipe would been bad. So at this point if the lock screen asks you to format it and you don't have adb enabled then you probably will have to format it, I thought the new gen had adb access from early on in the boot process but I could be wrong, I suggest looking in the hdx section.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
sadly, no adb, its not an HDX because it's only dualcore. i now need a system.img and userdata.img.. i flashed the img from the ADK for this device and now all i get is fastboot.. i need ripped imgs from an actual device. the command i was running was a userdata/cache wipe, and i did prefix it but fastboot couldnt format the partitions because the filesystem wasnt compatible. The lock screen flat out wouldnt ask me to format, and the back button never showed up, which leades me to believe the system image was corrupt too. if anyone can give me system.img and userdata.img i would be eternally grateful! thank you for replying
Ah I knew it wasn't an hdx but they some things on that device that are similar to the hdx, like I think they disabled some fastboot commands from working and such. Hopefully someone more familiar with 2nd gen hd's can help you out more.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Ah I knew it wasn't an hdx but they some things on that device that are similar to the hdx, like I think they disabled some fastboot commands from working and such. Hopefully someone more familiar with 2nd gen hd's can help you out more.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
so i borrowed a friends kindle and backed up his /system. i then sparsed it and it installed fine. when i booted up, i got a red flash and it threw me into fastboot. i then flashed the u-boot from the update file and now im bricked beyond all reair.. i run lsusb and get no mention of the device with my factory cable, and i cant get back in fastboot. the 2nd gen hd's suck so much..
Ouch, was his kindle a second gen HD?
Sent from my Amazon Kindle Fire HD using Tapatalk
I looked on all the other forums and found nothing...
ok so my friend's kindle got stuck in a bootloop somehow (i don't know how)
so they asked me to fix it since i have the fastboot cable...
it boots into fastboot perfectly so stupidly i wipe every partition without backing up
i tried to flash twrp via fastboot so now i'm stuck at the boot logo (non animated)
anyway i think what i need is system.img and boot.img i'm not sure though...
if anyone could upload those somewhere i could probably fix this thing...
EDIT: Nevermind I fixed it, extracted the system.img, boot.img, etc. from another kindle.
Hey, I know that there are many threads with this issue. However none of them seem to work. My phone got stuck in a bootloop about a year ago - I just put it back in the box and threw it in a draw... - and it would be nice to fix this now.
So far I have installed the USB Drivers, ADB software and connected my phone and put it within Fastboot Mode. I can send commands to the phone successfully.
My issue is that I never enabled "OEM unlocking" whilst the phone was booted, can no longer do that due to being unable to boot it.
I have tried the following commands, none work:
fastboot flashing unlock
fastboot flash boot *image*
fastboot flash recovery *image*
fastboot format userdata
fastboot format cache
They all return the same error:
FAILED (remote: device is locked. Cannot flash images)
Click to expand...
Click to collapse
What are my options? Also, even if I manage to flash my device, will it get stuck in this bootloop again as I have read that it is possibly a hardware issue.
If it is a hardware issue, can I easily fix it or do I need tools for removing chips etc...