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.
Related
hey guys
I just rooted my HTC ONE X using a Mac and tried to install CM 10 onto the phone. After loading the boot.img file onto the phone, the phone is now not starting up.. it keeps turning on and going as far as the screen that says, 'htc quietly brilliant'..
i am unsure on how to get the phone back to just functioning normally. I am using a Mac and finding it hard to find help on how to revert back to original
any tips?
cheers
Did you do the command 'fastboot erase cache' after you flashed the boot.img file??
Get into fastboot reflash the boot image most of the time the error is the user not typing in the correct procedure to flash ie : fastboot flash boot boot.img hence you get the white screen simply restarting the process in fastboot always seems to work , fastboot wipe cache , then head to recovery to install Rom , you should be fine from there.
try another Kernel, it will fix my solution
Hello guys,
So today I was doing what I usually o with my Galaxy Nexus. Tested the last daily image of Ubuntu Touch, flashed factory images, then CM 10.1 and AK kernel, and started to use the phone.
A few hours later I had to get a file from my phone, connected it to my Ubuntu 13.04 machine and got the files. While I was there, I uploaded a zip to my phone too, but the screen went black and it did not woke up, so I performed a battery pull.
After that, the phone got stuck at Google logo. Sometimes it shows the ROM's boot animation, sometimes it just stays at Google logo. I thought I could have corrupted the file system, so I installed the 4.2.2 factory images again, but I'm still stuck.
Anyone know what could be happening and know how to fix this, please? Thank you in advance
did you flash the entire factory image or just system.img?
Zepius said:
did you flash the entire factory image or just system.img?
Click to expand...
Click to collapse
The entire image, using the flash-all.sh script.
try not using the flash all script and erase all the partitions before you flash them all
fastboot erase boot
fastboot erase system
fastboot erase userdata
*note: this will delete all data on the phone
then fastboot flash each individual img file.
Zepius said:
try not using the flash all script and erase all the partitions before you flash them all
fastboot erase boot
fastboot erase system
fastboot erase userdata
*note: this will delete all data on the phone
then fastboot flash each individual img file.
Click to expand...
Click to collapse
Will do that. Thanks for the advice
R: [Q] Device stuck at Google logo, even after installing factory images
It 'happened to me (not with Ubuntu OS) ... I just flash the stock ROM partition at a time with fastboot (un zip the stock and flash boot, system, data, recovery etc...), erase cache , reboot and thanks the sky
From Gnex with Tapatalk 2
Zepius said:
try not using the flash all script and erase all the partitions before you flash them all
fastboot erase boot
fastboot erase system
fastboot erase userdata
*note: this will delete all data on the phone
then fastboot flash each individual img file.
Click to expand...
Click to collapse
I think the device is gone. I erased the partitions, flashed all the files back and when the "X" boot animation appeared, the screen flickered and the animation froze. Then the phone rebooted and right now, it's still stuck at Google logo. So sometimes it boot to boot animation, sometimes it won't...
Is it really gone?
I guess I will try two more things: flash Ubuntu Touch to see if that works or flash Android 4.1.2. Otherwhise, bye bye Nexus...
Did you resolve the problem?
julian_fern said:
I guess I will try two more things: flash Ubuntu Touch to see if that works or flash Android 4.1.2. Otherwhise, bye bye Nexus...
Click to expand...
Click to collapse
I would like to know if you were able to resolve this issue. I am facing a similar problem and so far I have not been successful. For me, the device doesn't power on unless connected to a power source (in my case I'm using a USB cable) even though the battery is full. So far I have tried reinstalling the Android 4.4.2 factory image but to no avail. The device gets stuck on the 'Google' screen. This is so annoying.
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.
Hi everyone, im just new here in kindle fire 2 dev page. My KF2 was stuck at bootloop specifically at 'kindle fire' logo. I followed exactly what hashcode's tutorial on how to install twrp and CM. I don't have fastboot cable but i did tried to boot it at fastboot mode, i was able to fastboot it followed until flash the twrp then fastboot reboot. then it just stuck there, i can't use adb and now I'm building my own factory cable, but after I finished it nothing happens.
How can I fix this?
If my cable wiring was correct, should it boot to fastboot mode after I plugged it?
any help will greatly appreciated thanks.
+1 here
I got a fast boot cable, I can access twrp just need to restore it and it does not work...
I used KFFirstAide with no success all I get is solid kindle fire logo when trying to boot normally.
Hi everyone,
I attempted, and succeeded, at installing a 2nd-Bootloader + TWRP using the complete guide found in these forums. Afterwards, I was able to boot into TWRP but the Kindle itself would not boot, just sat on the blue "fire" logo. I first tried to use the KFHD_SRT_v2.1 to recover, but that resulted in where I am now, just the standard orange Kindle Fire logo (no blue) and nothing beyond that. I then tried the Kindle Fire First Aid tool to perform a "full restore", which appeared to be successful, but again with the same result; it just sits on the standard Kindle Fire logo. I've let it sit, and waited, for upwards of half an hour after each tool, it won't budge.
At this point I can get into Fastboot using the command prompt: fastboot -i 0x1949 getvar product
And the info does show up correctly. So I assume this means my device isn't complete shot?
After a few hours of poking around, I learned how to use various fastboot commands to push stuff into the Kindle, and it seems to respond. However, I can't, for the life of me find the stock Kindle partition files anywhere on the internet. If I understand correctly, I need the bootloader partition (.bin?), boot partition (.img), recovery partition (.img), and system (.img).
Help??
I don't recommend flashing the bootloader partition in this scenario, mainly because in doubt it is damaged and a bad bootloader flash can kill your kindle. What needs to be reflashed is usually recovery, system, and bootimg. Kffa downloads them off the net and stores them in a folder, SRT comes with them.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
I don't recommend flashing the bootloader partition in this scenario, mainly because in doubt it is damaged and a bad bootloader flash can kill your kindle. What needs to be reflashed is usually recovery, system, and bootimg. Kffa downloads them off the net and stores them in a folder, SRT comes with them.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Thanks for the info stunts. I did try both SRT and KFFA, with the same negative result, but I did not know that kffa stores these images locally.
I went ahead and extracted the boot, recovery, and system images from kffa directories and manually flashed them in fastboot. And it worked!
Which still leaves the question as to why the tool itself didn't fix my issue when it had the resources to do so? strange, anyways thanks! :good: