Hey guys, let's start with the basics.
1st . I am an idiot who managed to brick his kindle and then made the things even worse by trying to fix it
2nd. I am a noob so you most probably will get frustrated by my idiotic questions-please don't be mad at me I'm really trying to calm myself and fix it
so here is what happened:
1. I rooted my kindle fire 2 and installed android 4.2.2 with few apps
2. I tried installing Chainfire3D pro 3.30 and this prevented me from booting in Android but I still had recovery
3. I ran the recovery and enabled fast boot
4. I used this : http://forum.xda-developers.com/showthread.php?t=2035047 and clicked option 2
5. I disabled the fastboot and rebooted
6. Instead of booting into newly installed Amazon os it keeps trying to boot,displays the boot logo for few secs and then the screen goes black and starts all over again
So 2 simple questions: can it be fixed?do I need some special cable in order to fix it-I read this somewhere
Edit : I'm still reading any possible source I could grasp my hands on,so now almost 100% sure that it I need fastboot cable and that it will fix my problem. Am I right? If so where is the best place to order one- I'm currently living n UK if this helps you to guide me to someone/somewhere I'll get it faster.Also is there a way to create one myself?(I guess no but have to ask)
I got my fastboot cable from Honk Kong - It was like 6 $, I got it in 10 days and was able to fix all the mess.
You can close and delete the topic if you want
Related
Hi all, I am completley new to all of this side of technology, and rooting my kindle fire seemed an easy task, and it probably is but i think i have well and truly messed it up and any help will make me a happy man again!!!
I carried out the procedure using the KFU, at first my device was not online, so i used the method described via device manager which worked fine, the device was online and i carried out the permanent root with super user, everything went fine, i then went on to install from the extras the google play bit.
This is where things have gone wrong i think, as now the kindle will turn on but it gets stuck on a screen with kindle fire written across it the fire bit is an orange colour, i can get it to boot into twrp screen via the recovery boot aswell.
But everytime i try to connect to the KFU its always say offline no matter what i do. Is there a way to start over agan????
Like i said im new to all of this and have read a few how to's and explanation threads but i get easily confused, lol!!!!
Cheers
You can try clearing the cache/dalvik cache using TWRP and rebooting, but that probably won't help. If you are prepared to lose all of your settings, installed apps, etc. do a factory reset in TWRP and reboot. It should complete the boot process then. Otherwise, you're looking at reflashing the stock software and starting over... in which case, I recommend you just flash modaco and be done with it.
Whatever the case may be, learning about how your device works will help you out in the long run...
http://forum.xda-developers.com/showthread.php?t=1552547
Go back to the Kindle fire utility and press option 1(bootmode) then normal boot (4000) no matter if it says offline it will still work m8.:good:
Give it a shot
Hey Everyone,
I have been using these forums for the last year and a half and It has helped me a whole bunch to successfully root all of the android devices my family has. I have however ran into a problem with a 1st gen Kindle Fire. It is stuck at the orange and white kindle fire logo. So a little background, I have rooted this Kindle in the past and succeeded in flashing Cyanogenmod's jb. I changed it back to the old Kindle interface so that my sisters can use it for reading but they wanted to use it for games. I decided that I should just change it back to jb since I would have to go through the trouble of flashing google play. Now, here's when things go wrong.
I started by using KFU 0.9.6 since I was lazy and didn't want to go through my old method. I granted SU and also installed TWRP and FireFireFire. now, I found a rom by Cyanogenmod cm10.1.3otter and decided to flash it onto my device. Everything went fine but it wouldn't boot past the Cyanogenmod boot screen. So I put another rom on (cm10.1.2) and flashed that. It worked and i started using it under the assumption there was nothing wrong. I later discovered when entering the internet password that my keyboard was not working and nothing would allow it to work. I then decided that I would get the kindle rom back on and factory reset and wipe the device. When I flashed the Kindle rom and restarted it, It got stuck and would not boot past the Orange and white kindle fire logo. After 2 full charges and 48 hours, it is still stuck. I tried to check if the kindle showed up under ADB devices and it does but when I run adb shell(for one of the guides) it comes up with "no such file or directory." When I run KFU, adb is online but boot status is unknown. When I try to run any of the tools in KFU, waiting for device is shown and does not go away despite disconnecting and reconnecting/ power on and off.
I have been looking nonstop for the past two days without any help. I have tried to follow many of the guides online, but I never succeed. Can someone please help me solve this problem, I am completely stuck.
jaredahuey said:
Hey Everyone,
I have been using these forums for the last year and a half and It has helped me a whole bunch to successfully root all of the android devices my family has. I have however ran into a problem with a 1st gen Kindle Fire. It is stuck at the orange and white kindle fire logo. So a little background, I have rooted this Kindle in the past and succeeded in flashing Cyanogenmod's jb. I changed it back to the old Kindle interface so that my sisters can use it for reading but they wanted to use it for games. I decided that I should just change it back to jb since I would have to go through the trouble of flashing google play. Now, here's when things go wrong.
I started by using KFU 0.9.6 since I was lazy and didn't want to go through my old method. I granted SU and also installed TWRP and FireFireFire. now, I found a rom by Cyanogenmod cm10.1.3otter and decided to flash it onto my device. Everything went fine but it wouldn't boot past the Cyanogenmod boot screen. So I put another rom on (cm10.1.2) and flashed that. It worked and i started using it under the assumption there was nothing wrong. I later discovered when entering the internet password that my keyboard was not working and nothing would allow it to work. I then decided that I would get the kindle rom back on and factory reset and wipe the device. When I flashed the Kindle rom and restarted it, It got stuck and would not boot past the Orange and white kindle fire logo. After 2 full charges and 48 hours, it is still stuck. I tried to check if the kindle showed up under ADB devices and it does but when I run adb shell(for one of the guides) it comes up with "no such file or directory." When I run KFU, adb is online but boot status is unknown. When I try to run any of the tools in KFU, waiting for device is shown and does not go away despite disconnecting and reconnecting/ power on and off.
I have been looking nonstop for the past two days without any help. I have tried to follow many of the guides online, but I never succeed. Can someone please help me solve this problem, I am completely stuck.
Click to expand...
Click to collapse
You must enable adb on cm10 for one and the driver has to be modified for the pc to detect it due to pid and vid changes in cm10.
Thepooch said:
You must enable adb on cm10 for one and the driver has to be modified for the pc to detect it due to pid and vid changes in cm10.
Click to expand...
Click to collapse
I am aware of that however, I cannot boot to cm10. If i could boot to cm10, I would know what to do but right now I am still stuck at the kindle fire logo.
Hello,
I have recently attempted to install the 2nd bootloader, TWRP, and CM-10.2 mods on my Kindle FIre HD 8.9 and ended up with a bootlooping brick. Being as inexperienced as I am, I took the risky road and did not back up my device before attempting this... Lesson learned (Spent days on this problem when a back up takes minutes...) Currently, I can access fastboot and flash files but nomatter what I end up with a similar result of a static boot screen (Orange). I have tried KFHD System.img Restore Tool (Here) many times on different machines. I have tried KFFirstAide and it refuses to let me download from the server and thus aborts re-flashing the kindle. I have tried manually flashing 8.1.4 system, boot, and recovery images again with no results (As well as cleared the cache and userdata each time). I have downgraded the bootloader to 8.1.4 using the file given in Hashcode's Guide to install TWRP (Here). I have flashed these files from a Windows, a Mac, and now a Linux PC. Currently the Kindle is staring at me with a Kindle Fire Orange static boot logo. It is recognized by a computer for about 1-2 seconds after I first hit the power switch(I can catch it in fastboot here). Then it disappears and sits idly at the boot logo. Sometimes it reboots and then repeats the process, sometimes it just stays this way until I turn it off via hard reset.
I check the MD5 sums on each of the files and none of them have been corrupted while downloading. So now after looking through every forum I can bear, I come here. Am I missing something simple? Or is my device a devil spawn that refuses to return to stock images?
Hmm, off flashing from fastboot should typically work, since you were attempting to flash cm 10.2 I have to ask something because I am slightly uncertain of this myself, but did you ever get twrp running at one point before all this happened, and second if so did you ever wipe any of the partitions or try to flash the ROM?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Unfortunately no. I was never able to get into TWRP as the blue logo has never appeared. Directly after my first attempt at this I rebooted and got the red screen or wall of fire. I "fixed" that by reflashing stock boot, bootloader, recovery, and system image partitions to 8.1.4. Yet instead of a working device I now have either a boot loop or a fixed orange logo. I have gotten the device into stock recovery once (haven't been able to reproduce this result) but it shutdown while the process was underway(About half way??). I have also gotten the device to boot into a animated logo that then proceeded to a data corruption screen, but before I could even read the entire message the device shut off and began another set of boot loops. It looked like a amazon stock os prompt screen. Before this even began I had a normal Kindle fire that I had rooted. I forget what software version it was on before all of this unfortunately.
Sounds like the system image is slightly corrupted or something if the os had that kind of error about data corruption but you said the md5's march so that is weird. You try reflashing the boot partition again since reflashing system didn't work? This is frustrating, mainly because with out adb access from a decent recovery I have no Linux commands to work with, if worst comes to worst I think there's a way to reform at the system partition from fastboot but I wouldn't go for that just yet, I don't know the command offhand but if you did the wrong one I think there's a way it would clear all data on all partitions which would be very very bad. I'll ask hashcode what he thinks cause this is weird.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I have tried flashing all partitions before. Will try again soon. Also, I have another piece of information as well even if it isn't relevant. I originally bricked my Kindle at first, flashed the wrong bootloader. So I bought a for-parts Kindle (Same model) that had a busted screen and took out its motherboard and placed it into my device. Then I rooted the stock os on the new MB and the rest of the story is already in this thread. It still charges and fastboots but nothing other than a static orange boot screen so far. Thank you for helping me out on this; really hope that this can be fixed.
Thinkwithportals said:
Hello,
I have recently attempted to install the 2nd bootloader, TWRP, and CM-10.2 mods on my Kindle FIre HD 8.9 and ended up with a bootlooping brick. Being as inexperienced as I am, I took the risky road and did not back up my device before attempting this... Lesson learned (Spent days on this problem when a back up takes minutes...) Currently, I can access fastboot and flash files but nomatter what I end up with a similar result of a static boot screen (Orange). I have tried KFHD System.img Restore Tool (Here) many times on different machines. I have tried KFFirstAide and it refuses to let me download from the server and thus aborts re-flashing the kindle. I have tried manually flashing 8.1.4 system, boot, and recovery images again with no results (As well as cleared the cache and userdata each time). I have downgraded the bootloader to 8.1.4 using the file given in Hashcode's Guide to install TWRP (Here). I have flashed these files from a Windows, a Mac, and now a Linux PC. Currently the Kindle is staring at me with a Kindle Fire Orange static boot logo. It is recognized by a computer for about 1-2 seconds after I first hit the power switch(I can catch it in fastboot here). Then it disappears and sits idly at the boot logo. Sometimes it reboots and then repeats the process, sometimes it just stays this way until I turn it off via hard reset.
I check the MD5 sums on each of the files and none of them have been corrupted while downloading. So now after looking through every forum I can bear, I come here. Am I missing something simple? Or is my device a devil spawn that refuses to return to stock images?
Click to expand...
Click to collapse
"I have recently attempted to install the 2nd bootloader, TWRP, and CM-10.2 mods on my Kindle FIre HD 8.9 and ended up with a bootlooping brick."
I have the same problem but when I try fastboot mode the computer wont even find the device
Alrighty, well. I woke up this morning and decided to re download all of the system, boot, and recovery image files. I flashed them to the device and it again boot-looped for about an hour. I set it up next to me and started reading through the forums for repair via soldering eMMC to SD card reader. I look down and what is starting back at me? A fully working Kindle waiting in initial setup for input... Yet within about a minute it is back into the old boot looping game again. Hardware problem? A short maybe???
possibly or maybe it has a bad emmc chip.
Sent from my LG-P769 using xda app-developers app
Hm, well I think I might just give up on this MB then. I am considering looking into my hard-bricked motherboard and using Kurohyou's pin-out. Even if my soldering skills are a bit rusty.
Thank you anyway for your help. I will report my progress in the other thread from here on out.
Careful not to melt the contact pads, I just ruined one of my Xbox 360 controllers today unsoldering a trigger, cheap parts.... Long story short controller falls in dogs water bowl, circuit board goes in rice, rice gets stuck under a trigger, I ruin controller unsoldering trigger... Least I have 4 more. But anyways yea careful, I suggest at least an st7 tip and not to let it get to hot, read someone else managed to melt a contact on a kf2 I think it was.
Sent from my Amazon Kindle Fire HD using Tapatalk
hello i recently rooted and installed cm11 on my FP, i just did a clean system partition flash, then flashed pa_gapps. now screen is stuck at black screen with amazon logo. what should i do? i did get the phone to connect to the pc, i got it working using the stock usb cord phone came with. now the phone not connecting to pc anymore.
what can i do to return the phone to factory setting? or at least to get the cm11 running.
azheng said:
hello i recently rooted and installed cm11 on my FP, i just did a clean system partition flash, then flashed pa_gapps. now screen is stuck at black screen with amazon logo. what should i do? i did get the phone to connect to the pc, i got it working using the stock usb cord phone came with. now the phone not connecting to pc anymore.
what can i do to return the phone to factory setting? or at least to get the cm11 running.
Click to expand...
Click to collapse
You mentioned clean partition flash and pa gapps but you didn't say you flash the cm11 zip. I assume you did? If not there's no os. Twrp will notify if the os isn't there but not sure about safestrap. I'd assume you need to flash it in fastboot now unless there's a button combo that can be utilized.
I'd take this to the cm11 thread. ggow might be able to assist.
KLit75 said:
You mentioned clean partition flash and pa gapps but you didn't say you flash the cm11 zip. I assume you did? If not there's no os. Twrp will notify if the os isn't there but not sure about safestrap. I'd assume you need to flash it in fastboot now unless there's a button combo that can be utilized.
I'd take this to the cm11 thread. ggow might be able to assist.
Click to expand...
Click to collapse
well problem is i cant even get into safestrap recovery right now. when i hard reset the phone, try to boot it. its stuck at amazon screen. good thing right now is when i plug the phone in the pc, it makes connection. maybe i can sideload a os using the pc?
azheng said:
well problem is i cant even get into safestrap recovery right now. when i hard reset the phone, try to boot it. its stuck at amazon screen. good thing right now is when i plug the phone in the pc, it makes connection. maybe i can sideload a os using the pc?
Click to expand...
Click to collapse
That probably IS a good thing. But if there's no OS installed I'd think it would automatically boot to recovery? I've only owned this phone a short time and before last week never used safestrap. Normally I'd either try to boot recovery with a button combo (haven't needed to on this phone.) Or connect via adb and use the command "adb reboot recovery".
I'd say you have a better chance or at least a quicker response if you head over to ggow's thread. Good luck
KLit75 said:
That probably IS a good thing. But if there's no OS installed I'd think it would automatically boot to recovery? I've only owned this phone a short time and before last week never used safestrap. Normally I'd either try to boot recovery with a button combo (haven't needed to on this phone.) Or connect via adb and use the command "adb reboot recovery".
I'd say you have a better chance or at least a quicker response if you head over to ggow's thread. Good luck
Click to expand...
Click to collapse
thanks for the help, i think recovery went bye bye along with the OS lol
Hi,
any update on this thread? I've been stuck also. I had safestrap. I supposed to flash a cleamsystempartion but I accidentally restart it without flashing new rom and now i am stuck in Fire Phone Logo. I still can access the stock recovery tho. Please help :crying::crying::crying:
try to flash your phone back to stock rom
any solution to this problem? I am stuck with same problem.
siddharth_bhal said:
any solution to this problem? I am stuck with same problem.
Click to expand...
Click to collapse
same problem here: can't start safe stripe and stuck at Amazon. tried to start the phone pressing volume up and power button, see if you can get into the build-in recovery. if it works, you can wipe the data and then use ADB sideload to flash in official rom (should be a bin file, i tried 4.6.1 version) and bring back your phone .
fire phone keep rebooting
my fire phone is keep rebooting with amazon logo up to 5 minutes and suddenly turned of i want to know the problem and how to fix it so please help me.
Have any of you guys tried the instructions in this thread: https://forum.xda-developers.com/fire-phone/general/reverting-fire-phone-to-stock-t3288890
I have bricked Fire phone quite a few times and everytime I followed his instructions and the lifehacker instructions that he linked to install adb and ADB sideloaded 4.6.6.1. without any problems.
My fire keeps rebooting and gets stuck with the amazon logo on it pls i need ur help urgently
Bahdtyga said:
My fire keeps rebooting and gets stuck with the amazon logo on it pls i need ur help urgently
Click to expand...
Click to collapse
U need a new fire phone, talk with amazon from your country or region or the seller from where you got fire phone!
Hi all, I basically registered here to ask this question, so I hope there's somebody can help me.
I've just applied the rbox root process as defined here : <link removed as I'm a new user and can't post urls, but it's basically the instructions on aftvnews>
There were a few ups and downs along the way, but I sorted out all the minor things in the end and completed the process. Unfortunately my FireTV is now stuck at the white amazon logo.
I can access TWRP recovery, and while I am here I can connect via adb.
I applied rbox's unbrick process to see if that helped matters, power cycled and came back to TWRP (I think I should have been expecting to go to a direct boot there, but not entirely sure). From TWRP I went to do a reboot but it asked me if I was really sure as there was no OS. That sounded like a bad idea to reboot so I reapplied the rooted 5.0.5.1 r1 image that was sitting in my /sdcard directory. Back to the original problem - stuck at the white amazon logo.
I've cleared the cache, cleared the system, reapplied the rooted rom and everything else I can think of, but I always end up back at the same issue. All roms applied using md5 checking, so the files weren't corrupted when I transferred them via adb or anything.
Since I can access TRWP I can't be competely screwed. Really hoping somebody has a suggestion (that will also get my kids off my back as they are currently without netflix )
Nobody?
I can't help feeling this is almost there if I can just get over this last problem!
[SOLVED] (sort of)
OK, in case anybody reads this, this one solved itself. I basically left the fireTV plugged in for several days and when I connected it back to the screen it was working. Not a clue what it was that sorted itself out, but very odd