hi, i accidentally bricked my fire stick 1st gen (montoya) by flashing magisk. i had twrp recovery before and was stupid enough to flash magisk without knowing it would brick my fire stick. it only boots up to the white amazon logo. i am able to send fastboot commands but it says the bootloader is locked when i try to flash the boot and recovery.
is there anything i can do? i tried searching but i could only find the 2nd gen bootloader unlock.
Related
Hi,
currently I am stuck at the non flashing "kindlefire" bootlogo.
I cant access TWRP anymore and my computer also does not recognize the kindle fire.. what options do I have to get a bootable kindle fire again?
What I have done in the last 4 hours to end up in that state:
follow this thread: http://forum.xda-developers.com/showthread.php?t=2105077
IMPORTANT: WHEN COMING FROM STOCK AMAZON OS
-Make sure you wipe everything while in TWRP before you flash anything!
Click to expand...
Click to collapse
I did like statet and ended up without OS because I wiped everything like statet.
Then, after booting into fastboot I tried that tool:
http://forum.xda-developers.com/showthread.php?t=2096888
It said that I recovered my kindle to stick firmware but In fact I am stuck now with the bootscreen.
Can anyone help me please?
after following this thread
Do you have a KF1 or KF2?
As soup said, are you sure you have a Kindle Fire 2?
Did you buy it new, and did it come in a brown or black box?
You might be OK to flash TWRP again, then use ADB push command to get a 10.1 ROM onto your Kindle. I would talk with Soup a bit in case there is an issue with his tool.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Please forgive my noob-ness. I've done some research but i can't figure out whats up with this device.
I have a Kindle Fire first gen that is stuck in a boot loop. I get the boot logo with "Kindle Fire" and a flicker effect but that is it. This is NOT my device i'm trying to fix it for a non-technical family member. I know they didn't try to root it or any of that. It just stopped working for them one day.
after installing / removing / reinstalling the drivers a million times i finally got the kindle fire utility to see the device as online. its seems like no matter what i do the device goes back to the boot loop and KFU gives me "waiting for device'. anyone have any ideas? do i need the factor cable to get this working again??
according to FAQ 16 Frequently Asked Questions - Amazon Kindle Fire
If the Kindle Fire logo you're talking about flashes and goes dim after being brightly lit for a few seconds, then your device is trying to boot normally to a malfunctioning operating system, likely caused by not wiping the data partition (factory reset) before flashing a ROM. If that's the case, you will likely need a factory cable to get into fastboot mode so you can access or (if needed) install custom recovery, then reinstall a ROM properly.
Click to expand...
Click to collapse
yes you need a fastboot cable
or
there is a [UTILITY] Kindle Fire Unbrick Utility V1.1! that you can try
kfs325 said:
Please forgive my noob-ness. I've done some research but i can't figure out whats up with this device.
I have a Kindle Fire first gen that is stuck in a boot loop. I get the boot logo with "Kindle Fire" and a flicker effect but that is it. This is NOT my device i'm trying to fix it for a non-technical family member. I know they didn't try to root it or any of that. It just stopped working for them one day.
after installing / removing / reinstalling the drivers a million times i finally got the kindle fire utility to see the device as online. its seems like no matter what i do the device goes back to the boot loop and KFU gives me "waiting for device'. anyone have any ideas? do i need the factor cable to get this working again??
Click to expand...
Click to collapse
Not sure of the state of your Kindle Fire G1 (It's not rooted? Are you sure?), but this sounds similar to what I ran into trying to install CM11.
What version of TWRP do you have installed? If it's 2.2.2.1 and you're trying to install a ROM with KitKat (CM11) you can run into this. I did. When I installed TWRP 2.7.0.1 I could install CM11 just fine without the boot loop.
To install TWRP 2.7.0.1 I found that you could only do so by:
When you turn Kindle Fire on, hold down the power button to cycle through the options when you see the Kindle Fire logo. You want to land on the Recovery option.
Mount storage from TWRP 2.2.2.1 on a PC and copy CM10.x.x and related GApps to SDCARD
Factory reset then reinstall CM10.x.x (with Gapps for that version)
Install Flashify from the PlayStore
Download the latest TWRP for otter/Kindle Fire G1 (2.7.0.1)
Install it with Flashify
Download CM11 and related ZIPs (GApps kk, Change to Nexus 7, etc) to Downloads directory
Restart into TWRP recovery (should be 2.7.0.1 now), and factory reset/reinstall CM11 and related ZIPs from Downloads directory
Should be fine now.
I found that I could only do it this way because for some reason Kindle Fire Utility Kit and ADB couldn't work with my Kindle anymore with TWRP 2.2.2.1 (don't ask, I don't know why). This way works. Just make sure you have a copy of a version of a ROM and GApps on SDCARD at all times since mounting storage might not work anymore in TWRP (again, I'm not sure why). I tried it again and again, but I couldn't get it to work and it might be the same for you. Keep in mind this is for CM11. If you're using stock, then follow sd_shadow's advice.
So I am brand new to rooting and just rooted my 1st gen kindle yesterday and found an ROM that I like. It however is set up for flashing to the primary partition and I need help with getting it to flash to my alternate boot partition. Thanks
I rooted my kindle and installed a 2nd bootloader and TWRP it worked fine for a few days but then i decided to upgrade my TWRP and i some how corrupted my bootloader and now my kindle is stuck on the boot screen which shows the logo Kindle in White and Fire in Orange it does not go ahead. My pc does not even detect my kindle so I read this thread
http://forum.xda-developers.com/show....php?t=1869297
but i am not able to solve this problem.
It does not go into fastboot.
I tried to upgrade from TWRP 2.6.0.0 to 2.8
I think the problem was that i did not install FireFireFire in my kindle
I used usb 3.0 to do all of this.
Please Help
check here for solution
http://forum.xda-developers.com/showpost.php?p=59900685&postcount=4
Finally I've got to the point where a faulty usb stick bricked my Fire TV Gen 1.
Short story: wanted do downgrade to an older rb_firmware on my device. My device was rooted and on the latest rbox firmware (5.2.6.6). So downloaded a former rbox firmware and wiped in twrp recovery everything except the usb drive...after selecting the rbox firmware and installing it, it stopped and didn't get further then copying image...after a while the fire tv rebooted itself and tada a black screen with a white amazon logo appeard and nothing more.
What I've tried: using fastboot commands by wireing the fire tv with an A to A usb cable....did not work, maybe because I have an only partial unlocked bootloader and no full unlock.
Is there a hardware method (emmc flash) or am I good to go and throw my fire tv in the trash.
assyriska said:
Finally I've got to the point where a faulty usb stick bricked my Fire TV Gen 1.
Short story: wanted do downgrade to an older rb_firmware on my device. My device was rooted and on the latest rbox firmware (5.2.6.6). So downloaded a former rbox firmware and wiped in twrp recovery everything except the usb drive...after selecting the rbox firmware and installing it, it stopped and didn't get further then copying image...after a while the fire tv rebooted itself and tada a black screen with a white amazon logo appeard and nothing more.
What I've tried: using fastboot commands by wireing the fire tv with an A to A usb cable....did not work, maybe because I have an only partial unlocked bootloader and no full unlock.
I had same happen as I tried to root a Gen 1.
There is a article here on how you can get into the AFTV1 via keyboard strokes. From there you try to reset to default. I got to the menu from the keyboard but did not work for me. Maybe someone can point to where the article is here or search it. Good luck!!
Click to expand...
Click to collapse