Related
After I rooted my kindle and installed adw.launcher everything was going fine. I rebooted my kindle and out of nowhere it refuses to start. Absolutely nothing shows up at all. The screen doesn't come on, the logo, nothing. The battery was at 75% when it was working. Even when I plug it in the orange charge light doesn't even come on. I need help badly and I would prefer not to have to send it in to get a replacement. The entire reason I created this xda account was to fix this. Please I need help.
That doesn't sound good. Press and hold the on button for like 20 seconds and see if anything happens.
jaredkzr said:
After I rooted my kindle and installed adw.launcher everything was going fine. I rebooted my kindle and out of nowhere it refuses to start. Absolutely nothing shows up at all. The screen doesn't come on, the logo, nothing. The battery was at 75% when it was working. Even when I plug it in the orange charge light doesn't even come on. I need help badly and I would prefer not to have to send it in to get a replacement. The entire reason I created this xda account was to fix this. Please I need help.
Click to expand...
Click to collapse
Try the Hard reset option as explained by GBH2 and if it doesn't help, then please list down what exactly did you do to root your device, stock FW version etc.
Sent from my GT-I9100 using XDA App
I have already tried the hard reset but to no avail. I have no idea what happened to it. I think I will just have to get a replacement. I followed instructions off of mobilemag and of course I can't place the link in this post.
I literally just had same issue... holing power button for 20+ seconds did the trick here.
Running CM7 w/ MAC address fix.
mine's bricked too
I also have a bricked Kindle and not sure what to do about it.
I had my KF rooted and working. Then, I followed these instructions to get a better keyboard. In short, I edited one row of the secure table in settings.db, trying to enable Hackers Keyboard. I followed the instructions very carefully, including changing permissions. When I rebooted, it stuck at the kindle fire logo, and it is still stuck there.
I can connect via adb, but can no longer burrito root. Can't run 'su'. I'm searching these forums trying to figure what to do next.
do you have twrp available ?
if not you could follow this post: http://forum.xda-developers.com/showthread.php?t=1414832
fixed
Thanks. I found that thread via http://forum.xda-developers.com/showthread.php?t=1356257&page=61 and it saved the day.
I was able to fastboot, twrp, and eventually solve my problem.
I had updated settings.db, then used `adb push` to put it in the right place. Then, I chmod-ed it as the instructions warned. However, it was owned by root not system! With twrd, I was able to get back into adb. Chown-ing and chgrp-ing that file to system solved my problem.
(Unfortunately some of the other stuff I did along the way broke a few apps... anyway I'm happy to have a working KF again.)
good to hear !!!
Did you ever get your KF to work? I can not get mine to turn on after KFU 0.9.5 used to do perm root. Now nothing works at all
Kindle fire wont power on /boot
I'm facing the same issue here, i have FFF 1.4a and TWRP 2.2.2.1 installed and JB 4.2.1 from twv. However i noticed whenever i pressed reboot from menu or power it off, i cannot turn it on again.
Luckily i have an OTG cable which help me force boot it, but i want to solve the issue coz i dont want to use the OTG cable always to turn it on.
Note: Holding power button for 20secs did not solve the issue
hi vertcam9 how do you force boot it please.
omniac
omniac said:
hi vertcam9 how do you force boot it please.
omniac
Click to expand...
Click to collapse
Hello, i have a Factory Cable (USB cable) with a different pin configuration. Basically if you have a working bootloader, you just plug it in (with a PC) and it will go to the FFF screen.
I think my issue is a busted USB port already.
ok thanks tried that, but it is deader than that.
omniac
Dead is right on the mark for mine also. With pc never detecting my CM9 , I updated my TWRP to v2.2.2.1, in hopes to go to CM10
And for first time saw *bootloader* as an option in TWRP . Screeching halt!!! Beware.
Seriously people...
vertcam9 said:
I'm facing the same issue here, i have FFF 1.4a and TWRP 2.2.2.1 installed and JB 4.2.1 from twv. However i noticed whenever i pressed reboot from menu or power it off, i cannot turn it on again.
Luckily i have an OTG cable which help me force boot it, but i want to solve the issue coz i dont want to use the OTG cable always to turn it on.
Note: Holding power button for 20secs did not solve the issue
Click to expand...
Click to collapse
vertcam9 said:
Hello, i have a Factory Cable (USB cable) with a different pin configuration. Basically if you have a working bootloader, you just plug it in (with a PC) and it will go to the FFF screen.
Click to expand...
Click to collapse
Normally I would assume you had a 2nd generation device and tried to modify it, but I see your first post was made back in April and then edited two days ago?!? Is this a new problem or the same problem you had eight months ago?
I'm pretty sure your USB port isn't bad and you just have a broken bootloader. If you have a 1st generation device, the Firekit w/shorting trick to put the device in USBboot will do the trick.
omniac said:
hi vertcam9 how do you force boot it please.
omniac
Click to expand...
Click to collapse
omniac said:
ok thanks tried that, but it is deader than that.
omniac
Click to expand...
Click to collapse
How about some details...better yet, start a new thread...In the Q&A section.
Smmoph said:
Dead is right on the mark for mine also. With pc never detecting my CM9 , I updated my TWRP to v2.2.2.1, in hopes to go to CM10
And for first time saw *bootloader* as an option in TWRP . Screeching halt!!! Beware.
Click to expand...
Click to collapse
This sounds like a completely different problem. You should probably start a new thread as well...In the Q&A section.
I have the exact same problem!!!!!!!!!
After I rooted my kindle, everything was going fine. My kindle turned off and when I rebooted, it got stuck in a bootloop. I tried to fix it by reflashing a fresh image and out of nowhere it refuses to start. Absolutely nothing shows up at all. The screen doesn't come on, the logo, nothing. The battery was at 75% when it was working.
This has been the problem since 5 months...
I am using a kindle fire 5th generation and don't have a factory cable.
Can somebody plz help!!!!!!!!!!!!
If so, can someone post a link for a cheap factory cable however I really don't want to use/buy one.
Thanks!
samiultahir said:
I have the exact same problem!!!!!!!!!
After I rooted my kindle, everything was going fine. My kindle turned off and when I rebooted, it got stuck in a bootloop. I tried to fix it by reflashing a fresh image and out of nowhere it refuses to start. Absolutely nothing shows up at all. The screen doesn't come on, the logo, nothing. The battery was at 75% when it was working.
This has been the problem since 5 months...
I am using a kindle fire 5th generation and don't have a factory cable.
Can somebody plz help!!!!!!!!!!!!
If so, can someone post a link for a cheap factory cable however I really don't want to use/buy one.
Thanks!
Click to expand...
Click to collapse
this is only for Kindle Fire 1 (2011)
there is a separate section for your device see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum link
Sent from my XT1028 using XDA Labs
sd_shadow said:
this is only for Kindle Fire 1 (2011)
there is a separate section for your device see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum link
Sent from my XT1028 using XDA Labs
Click to expand...
Click to collapse
Oh Thanks Anyways but do you know a fix for this?
BTW I think my device is hard bricked. :crying:
samiultahir said:
Oh Thanks Anyways but do you know a fix for this?
BTW I think my device is hard bricked. :crying:
Click to expand...
Click to collapse
post in the correct forum
Sent from my sailfish using XDA Labs
Hello,
I have the Galaxy S II T989 (Tmobile) and the screen got broken and is completely black. But The phone is working and i can start it and feel the vibe at start and after it starts, i cant tap the bottom 4 buttons and they light up.
My phone was protected by pattern password. So when i connect the phone to USB and launch Kies , it asks me to unlock it...
But i can't since my screen is broken and doesn't light up.
Is there a way to download the internal contents of the flash memory (not the SD card) to the PC somehow?
I have tons of pictures and video clips that are very important to me.
Please help.
Paul.
Is USB debugging enabled? If so, you may be able to pull the files that way. You may also be able to do it through recovery (hold both volume buttons down at powerup while not USB connected). If you can get adb access, you can use it to pull the pictures that way.
Sent from my Polaroid Tablet using Tapatalk 2
Boot into recovery. Connect USB to PC Mount drives. Success!!
Sent from my SGH-T989 using xda premium
LoopDoGG79 said:
Boot into recovery. Connect USB to PC Mount drives. Success!!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
When you say to boot into recovery, do you refer to VOL_UP + VOL_DOWN + PWR buttons at boot ? When you get to the menu that you can select between Device reboot, Firmware update using external memory, etc...
Or are you referring to something else?
Thanks much!
laker4ever said:
When you say to boot into recovery, do you refer to VOL_UP + VOL_DOWN + PWR buttons at boot ? When you get to the menu that you can select between Device reboot, Firmware update using external memory, etc...
Or are you referring to something else?
Thanks much!
Click to expand...
Click to collapse
Dont know how broken your screen is or what recovery you have, but yes, that's what I mean. There is an option somewhere in recovery to mount drives.
Sent from my SGH-T989 using xda premium
What recovery you have? Being that your LCD is shattered I could guide you step by step on how many clicks on the volume rocker to access on latest cmw. Since it doesnt work the same on twrp I can you guesstimate the location on touch and maybe your screen could recognize it enough to enable you to mount from recovery..
Sent from my SGH-T989 using xda app-developers app
Best bet is either through ADB access either with USB Developer Mode turned on or using ADB in recovery to pull the files. Neither one of those options requires using the phone more than turning it on. How was the phone set up before the LCD broke? Did you root it? Did you put a new recovery on it? Or was it completely stock. If it was completely stock, go fix the LCD and then access it, there's no way around it... well... actually, you could get into Download Mode, flash a recovery, then access it that way.
h.nocturna said:
Best bet is either through ADB access either with USB Developer Mode turned on or using ADB in recovery to pull the files. Neither one of those options requires using the phone more than turning it on. How was the phone set up before the LCD broke? Did you root it? Did you put a new recovery on it? Or was it completely stock. If it was completely stock, go fix the LCD and then access it, there's no way around it... well... actually, you could get into Download Mode, flash a recovery, then access it that way.
Click to expand...
Click to collapse
I'm able to use the HDMI converter and "SEE" the screen of the phone on my TV. However, i cannot unlock it (it had the pattern lock) because the touch screen is not responding to my touch. I guess the touch sensor is broken.
It is a stock phone. never rooted it.
I was trying to get to recovery mode by pressing POWER and VOL UP and DN, but i wasn't able to see anything on my TV. Could it be that the HDMI converter into TV only works when the phone is booted normal and doesn't work in recovery mode.
How can i get it to download mode and flash the recovery?
datrapstar said:
What recovery you have? Being that your LCD is shattered I could guide you step by step on how many clicks on the volume rocker to access on latest cmw. Since it doesnt work the same on twrp I can you guesstimate the location on touch and maybe your screen could recognize it enough to enable you to mount from recovery..
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
The touch sensor is not working as i was able to see the screen on my TV( with the MHA - hdmi adapter) but touching the screen on the phone did nothing...
laker4ever said:
I'm able to use the HDMI converter and "SEE" the screen of the phone on my TV. However, i cannot unlock it (it had the pattern lock) because the touch screen is not responding to my touch. I guess the touch sensor is broken.
It is a stock phone. never rooted it.
I was trying to get to recovery mode by pressing POWER and VOL UP and DN, but i wasn't able to see anything on my TV. Could it be that the HDMI converter into TV only works when the phone is booted normal and doesn't work in recovery mode.
How can i get it to download mode and flash the recovery?
Click to expand...
Click to collapse
Yeah, I don't think the drivers to show on the TV screen would be loaded while in Download Mode.
There's still hope, you can still install a recovery without actually needing the touchscreen. Once in recovery, you'll be able to access your system files through adb and pull whatever you need onto your computer.
You'll have to do it all blind though because you won't be able to see if the phone has successfully rebooted into recovery. I can walk you through it step-by-step if you feel it's that important to you to recovery whatever data is on the phone.
Buy a new Phone.
h.nocturna said:
Yeah, I don't think the drivers to show on the TV screen would be loaded while in Download Mode.
There's still hope, you can still install a recovery without actually needing the touchscreen. Once in recovery, you'll be able to access your system files through adb and pull whatever you need onto your computer.
You'll have to do it all blind though because you won't be able to see if the phone has successfully rebooted into recovery. I can walk you through it step-by-step if you feel it's that important to you to recovery whatever data is on the phone.
Click to expand...
Click to collapse
Update:
I got a replacement phone and using some youtube clips and info, i swapped the boards between the two phones. So I was able to start the phone (old board, new screen), and simply transferred all data to the computer.
Now, i will put it back together and be all done.
I also enabled USB debug mode...for next time....
Thank you so much for the help.
h.nocturna said:
Yeah, I don't think the drivers to show on the TV screen would be loaded while in Download Mode.
There's still hope, you can still install a recovery without actually needing the touchscreen. Once in recovery, you'll be able to access your system files through adb and pull whatever you need onto your computer.
You'll have to do it all blind though because you won't be able to see if the phone has successfully rebooted into recovery. I can walk you through it step-by-step if you feel it's that important to you to recovery whatever data is on the phone.
Click to expand...
Click to collapse
Hello Senior Member ,
I too have a similiar dilemma. My Note 2 has a cracked screen and its all black . I am not sure the digitizer is in working condition . Although I have alot of files I wish to recover. Its been nearly a year Ive held on to it just to recover data. My phone is stock , NO ROOT and unfortunately USB Debugging has been turned off. Mind you, its a korean version, model SHVE250K . I do not want to chance rooting if I can not see the screen . I am afraid of making a mistake. ANY advice and ideas would be greatly appreciated. I would feel more confident working on it, with someone more experienced guiding me along the way.
Three letters with one word= MHL cable. I do it all the time with one of my t989's.
Now im soo broke, I cant even pay attention!
---------- Post added at 12:52 AM ---------- Previous post was at 12:47 AM ----------
laker4ever said:
I'm able to use the HDMI converter and "SEE" the screen of the phone on my TV. However, i cannot unlock it (it had the pattern lock) because the touch screen is not responding to my touch. I guess the touch sensor is broken.
It is a stock phone. never rooted it.
I was trying to get to recovery mode by pressing POWER and VOL UP and DN, but i wasn't able to see anything on my TV. Could it be that the HDMI converter into TV only works when the phone is booted normal and doesn't work in recovery mode.
How can i get it to download mode and flash the recovery?
Click to expand...
Click to collapse
If the HML cable works but doesn't respond to touch, then both the lcd AND digitizer are broken. Replacement screens have gotten sooo much cheaper than a year ago, they're like $65 now. I fix em all the time.
Now im soo broke, I cant even pay attention!
Not sure if its really bricked or not but Its all messed and wont fully boot so it doesnt have lan access anymore for ssh and adb over wifi. I have a male to male usb cable and my pc is recognizing when its plugged in but there are no device drivers installed and adb/fastboot wont recognize (no usb debugging enabled?) so it just hangs on <waiting on device> any idea how I can install devices drivers and move forward with restoring backup of the file I fuxored? Thx guys!
Have you tried disconnecting that A to A cable? When I tried using an A A cable from my laptop to the Fire, it hung when it booted.
It powered on, went to the first white on black Amazon logo, and halted. Disconnecting the cable and power cycling let it complete the boot cycle.
Havnt got that far yet myself but the way i tinker i will be there shortly .. but as a warning to others, if you are not 100% sure what you are doing, dont muck around especially if you remount /system as rw.
Playing around will be much safer once we get recovery..
Building a recovery shouldnt be too difficult.. its booting a custom recovery that will be the trick.. Jcase had allready said he has figured it out perhaps he will share now that root is out.
roustabout said:
Have you tried disconnecting that A to A cable? When I tried using an A A cable from my laptop to the Fire, it hung when it booted.
It powered on, went to the first white on black Amazon logo, and halted. Disconnecting the cable and power cycling let it complete the boot cycle.
Click to expand...
Click to collapse
Ive got fastboot connected now so it appears it was some funky unknown issue. Fastboot isnt like adb tho and the only time ive ever used it was to re-write whole img files so is that my only option or is there some way I can push stuff through fastboot? The OTA firmware links posted a few weeks back are now dead too..
You can download the OTA updates (they are complete roms). http://forum.xda-developers.com/showthread.php?t=2709811 - links still work, i just redownloaded them (not sure where I put my old ones).
Only problem is the recovery looks for them at /cache/, which isn't writable w/o root. I'm not sure of the functions available via fastboot w/ Fire TV (don't have a cable), but if you can't get into the recovery from fastboot, you can always try to boot a dumped recovery.img from fastboot... but still not sure how you can work around the stock recovery looking for the update file at /cache/
edit: actually don't think fastboot will be of much use with a locked bootloader.
Luxferro said:
You can download the OTA updates (they are complete roms). http://forum.xda-developers.com/showthread.php?t=2709811 - links still work, i just redownloaded them (not sure where I put my old ones).
Only problem is the recovery looks for them at /cache/, which isn't writable w/o root. I'm not sure of the functions available via fastboot w/ Fire TV (don't have a cable), but if you can't get into the recovery from fastboot, you can always try to boot a dumped recovery.img from fastboot... but still not sure how you can work around the stock recovery looking for the update file at /cache/
edit: actually don't think fastboot will be of much use with a locked bootloader.
Click to expand...
Click to collapse
Im rooted already, but basically what youre saying is to wait until bootloader is unlocked then flash that via fastboot and then flash recovery via fastboot. I feel like there has to be an easier way lol but im a noob so who knows.
Im not have any luck with those links either ive even tried assigning a static public dns to make sure my opendns stuff was no longer blocking. Does anyone have an alternate link?
alwaysbless said:
Im rooted already, but basically what youre saying is to wait until bootloader is unlocked then flash that via fastboot and then flash recovery via fastboot. I feel like there has to be an easier way lol but im a noob so who knows.
Click to expand...
Click to collapse
Nah, not saying that at all - would love for an unlocked bootloader, but you might be waiting forever.
this is also one of the reasons that jcase hasn't released what he had (according to his G+ page). since if you bork the stock rooted rom, you'll have a hard time getting it fixed (since the rooted rom is the only current way in). If you can't boot the rom, then you can't fix anything. I'm no expert, so maybe one will chime in. But I think the next step after rooting, is to have a custom recovery, and a way to boot into it if the rom breaks - which we don't have yet.
I had a similar instance. Gained root messed around too much and got it to not boot. Amazon is sending a replacement... But if there is a way around that in the future I would love to just fix it my self.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Luxferro said:
Nah, not saying that at all - would love for an unlocked bootloader, but you might be waiting forever.
this is also one of the reasons that jcase hasn't released what he had (according to his G+ page). since if you bork the stock rooted rom, you'll have a hard time getting it fixed (since the rooted rom is the only current way in). If you can't boot the rom, then you can't fix anything. I'm no expert, so maybe one will chime in. But I think the next step after rooting, is to have a custom recovery, and a way to boot into it if the rom breaks - which we don't have yet.
Click to expand...
Click to collapse
So I couldnt even take the system.img and rewrite it using fastboot without having an unlocked bootloader? Sounds like the only way this thing will recover is install cwm/twrp recovery.img whenever that becomes available and then reflash w/ custom recovery.
alwaysbless said:
So I couldnt even take the system.img and rewrite it using fastboot without having an unlocked bootloader? Sounds like the only way this thing will recover is install cwm/twrp recovery.img whenever that becomes available and then reflash w/ custom recovery.
Click to expand...
Click to collapse
Except you won't be able to install a custom recovery since only your ROM has root access and it doesn't boot.
Sent from my Nexus 5 using Tapatalk
Luxferro said:
Except you won't be able to install a custom recovery since only your ROM has root access and it doesn't boot.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Got you now. So this is def the first bricked fire tv lol. Guess ill just sit it to the side and see if someone smarter than I can figure something like this out in the future.
Have you tried fastboot boot commands? Like fastboot boot blahblahblah.img? If it is softbricked i guess it can't hurt to try rite?
I don't know if this will work or not, but if you've already tried pulling the power, pulling USB and powering on the next thing I'd try is to obtain a 1 gig or so USB drive, format it fat32 and copy the OTA update to it.
- Leave it zipped.
- Name it update.zip
- pull the plug on the FTV
- put the USB stick in
- power it on and leave it for a bit. Watch it - is the power LED going out? If so, it may doing a recovery install of the signed OTA and rebooting - many Android devices will install anything on the sdcard called Update.zip if it's there at boot time.
What you're hoping is that the USB mass storage is mounted as a possible recovery source at power on and that the OTA is isntalled via the stock recovery. If it works, great, if it doesn't, too bad.
another brick on the wall ?
Dear OP ' i think you are not the only one .
im not sure if im bricked or plain noob
after i rooted successfully and did the blocking through host editor guide in fire tv news and for a good measure i run this command "su
pm disable com.amazon.dcp" . all was good and i had an issue with audio in xbmc and in my great wisdom i did a reset to factory settings.
since then i can not register to amazon i believe because it can not accsses amazon site for verification. so im stuck in there.
i tried to SSH and through command line no device was recognized .
any assistance to this stupidity will be much appericiated
thanks yigo
Yigo said:
after i rooted successfully and did the blocking through host editor guide in fire tv news and for a good measure i run this command "su pm disable com.amazon.dcp" .
Click to expand...
Click to collapse
Afraid I can't help you, but in light of preventing other people (and me) to have the same issues:
I assume the /etc/hosts file will survive factory-resets, it's a file that probably is not restored (so immediatly removed the host-lines from mine), but wonder if the pm disable dcp will also survice a reset ? I assume not (core funcationality for amazon, likely in factory-reset group), but you never know, esp. not in the v1 versions we are running.
Anybody knows if this is the case ? I like the pm disable solution, but if this means that borking up my installation will prevent me from ever restoring it (as unable to connect to amazon), I'll have to fall back to the router-blockage solution, and would suggest other ppl to do that as well
Deregistering AFTV may help with registration issue.
I had problems registering after factory reset.
I only disabled my amazon.dcp nad had dns and router blocks to prevent updates.
I did not edit my host file.
To de-register your Fire TV-
1 - log on to your amazon account
2 - Hold the mouse over where it says 'Your Account" but do not click. You will get a list of options.
3 - Click "Manage Your Content and Devices"
4 - Click the center tab "Your Devices"
5 - Click on your Fire TV.
6 - Click "Deregister" right below your Fire TV.
You will ge a message saying it there may be a delay for it to take effect.
[email protected] said:
I had problems registering after factory reset.
I only disabled my amazon.dcp nad had dns and router blocks to prevent updates.
I did not edit my host file.
Click to expand...
Click to collapse
So (while you need to de register the FTV itself within amazon), it looks like you can factory reset after disabling the amazon.dcp service.
Which is good news, as this allows easier disabling of update checks on machine level instead of router level (which not everybody will be able to do) and disabling the update service is better then overlooking a (hidden) fallback URL.
N=1 though, so'll have to wait if more confirmations come in, or somebody will be brave enough to try it
Still Learning - Passing it on.
JPDeckers said:
So (while you need to de register the FTV itself within amazon), it looks like you can factory reset after disabling the amazon.dcp service.
Which is good news, as this allows easier disabling of update checks on machine level instead of router level (which not everybody will be able to do) and disabling the update service is better then overlooking a (hidden) fallback URL.
N=1 though, so'll have to wait if more confirmations come in, or somebody will be brave enough to try it
Click to expand...
Click to collapse
I read your other posting about update blocking.
Seems I did not have my amazon.dcp disabled.
I was not in SU mode when executing command and amazon.dcp was just killed not disabled.
Sorry for any confusion. Thanks
JPDeckers said:
So (while you need to de register the FTV itself within amazon), it looks like you can factory reset after disabling the amazon.dcp service.
Which is good news, as this allows easier disabling of update checks on machine level instead of router level (which not everybody will be able to do) and disabling the update service is better then overlooking a (hidden) fallback URL.
N=1 though, so'll have to wait if more confirmations come in, or somebody will be brave enough to try it
Click to expand...
Click to collapse
I hope one of the folks with a softbricked device gets a chance to see what happens with the over the air update file copied to a fat32 formatted USB stick and renamed update.zip.
With luck, at power on if there is media present, the stock recovery is looking to removable media to see if there's a file named update.zip it can process.
I don't want to softbrick mine to test, though.
So if I am understanding correctly, you should enable updates before you factory reset?
I followed the AFTV guide to a T. Flashed 51.1.4.0, had the boot menu, CWM and everything was golden. Pushed 51.1.5.3 to the SD, rebooted to CWM, flashed, now stuck in a loop. I cant even connect to it with the adb connect command. Am I screwed? Is this thing done? I dont understand. It doesnt even show the boot menu anymore. Just straight to the looping firetv logo. Was i supposed to reflash the boot menu after installing prerooted 51.1.4.0? This sucks if it's done for.....
Have a look here:
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/
Calibaan said:
Have a look here:
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/
Click to expand...
Click to collapse
Thanks man. Hopefully one of those methods works. I've been at this for 4 hours carefully working my way through every single step. The highest high of the one last flash to go, turning into the gut wrenching sickness of a boot loop is too much for tonight and I'll try tomorrow.
On a side note: who runs that site? Guy is a God and needs a golden fire TV sent to him.
supremekizzle said:
On a side note: who runs that site? Guy is a God and needs a golden fire TV sent to him.
Click to expand...
Click to collapse
LOL! Glad you're finding the site useful. Sorry you ran into issues, but if you unlocked your bootloader already, then you should be able to recover. Follow the guide Calibaan linked.
Maybe I should write a "Hello, I'm Elias" post to put a face to my work.
AFTVnews.com said:
LOL! Glad you're finding the site useful. Sorry you ran into issues, but if you unlocked your bootloader already, then you should be able to recover. Follow the guide Calibaan linked.
Maybe I should write a "Hello, I'm Elias" post to put a face to my work.
Click to expand...
Click to collapse
Yea bootloader is unlocked. I was literally at the step of flashing the newest prerooted version when it happened. So, if I get past the bootloop, which step should I continue with?
supremekizzle said:
Yea bootloader is unlocked. I was literally at the step of flashing the newest prerooted version when it happened. So, if I get past the bootloop, which step should I continue with?
Click to expand...
Click to collapse
Once you get into recovery, you should follow the "Resetting with Recovery Mode" section found here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3.2
Some of the steps will likely be redundant and unnecessary, but it ensures everything is in a good state to proceed. Most likely something went wrong when you installed the boot menu, so be sure to verify the boot menu is working by using it to enter recovery mode BEFORE flashing the 51.1.5.3 ROM.
AFTVnews.com said:
Once you get into recovery, you should follow the "Resetting with Recovery Mode" section found here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3.2
Some of the steps will likely be redundant and unnecessary, but it ensures everything is in a good state to proceed. Most likely something went wrong when you installed the boot menu, so be sure to verify the boot menu is working by using it to enter recovery mode BEFORE flashing the 51.1.5.3 ROM.
Click to expand...
Click to collapse
Thank you. I'm perfectly fine redoing all the steps no matter how redundant. I just want to make sure it's OK to reflash some of the stuff without first deleting the old. Will it just overwrite?
supremekizzle said:
Thank you. I'm perfectly fine redoing all the steps no matter how redundant. I just want to make sure it's OK to reflash some of the stuff without first deleting the old. Will it just overwrite?
Click to expand...
Click to collapse
Yes, it's alright to re-flash anything. You should manually delete any files you "pushed" to the Fire TV and re-push them to ensure a corrupted file wasn't the cause of the boot loop. (You don't want to use the same corrupted file when you re-do things.)
AFTVnews.com said:
Yes, it's alright to re-flash anything. You should manually delete any files you "pushed" to the Fire TV and re-push them to ensure a corrupted file wasn't the cause of the boot loop. (You don't want to use the same corrupted file when you re-do things.)
Click to expand...
Click to collapse
doesnt matter. just tried to fastboot and it isnt detecting any. I know the bootloader was unlocked. I did the adb shell command and it showed unlocked bootloader. WTF happened? EVERYTHING was followed.
OK tried just fastboot device minus the "s" and it's just waiting on device.
It's dead. Isn't it?
OMG OMG OMG OMG OMG!!!!!!!!!! Keyboard trick worked! It didnt work last night, but hitting the keys in quick succession finally made it boot into recovery!!!! What is the BEST way to proceed now that I'm here. I cannot eff this up!
supremekizzle said:
doesnt matter. just tried to fastboot and it isnt detecting any. I know the bootloader was unlocked. I did the adb shell command and it showed unlocked bootloader. WTF happened? EVERYTHING was followed.
OK tried just fastboot device minus the "s" and it's just waiting on device.
It's dead. Isn't it?
Click to expand...
Click to collapse
The Fire TV will still connect via fastboot even if the bootloader is locked. You just can't flash anything if the bootloader is locked.
While it's powered off, connect it to your PC using the A-to-A USB cable. Then plug in the Fire TV power. When it powers on, see if it's stuck on the white Amazon logo. If it is, then you're in fastboot mode, which means it's just an issue with PC drivers. If it's still doing a boot loop, then it's either too far damaged, or there's something wrong with your USB cable/USB port. As for PC drivers, I don't have an exact driver to tell you to use because, at the time I tried many and am not sure which one ultimately worked. It's something I;ve been meaning to figure out.
When the Fire TV detects power coming in through the USB port while it's booting, it enters fastboot mode (indicated by the stuck white Amazon logo).
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
supremekizzle said:
OMG OMG OMG OMG OMG!!!!!!!!!! Keyboard trick worked! It didnt work last night, but hitting the keys in quick succession finally made it boot into recovery!!!! What is the BEST way to proceed now that I'm here. I cannot eff this up!
Click to expand...
Click to collapse
If you're in recovery, install 51.1.4.0 and then proceed with the guide I linked.
AFTVnews.com said:
The Fire TV will still connect via fastboot even if the bootloader is locked. You just can't flash anything if the bootloader is locked.
While it's powered off, connect it to your PC using the A-to-A USB cable. Then plug in the Fire TV power. When it powers on, see if it's stuck on the white Amazon logo. If it is, then you're in fastboot mode, which means it's just an issue with PC drivers. If it's still doing a boot loop, then it's either too far damaged, or there's something wrong with your USB cable/USB port. As for PC drivers, I don't have an exact driver to tell you to use because, at the time I tried many and am not sure which one ultimately worked. It's something I;ve been meaning to figure out.
When the Fire TV detects power coming in through the USB port while it's booting, it enters fastboot mode (indicated by the stuck white Amazon logo).
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
If you're in recovery, install 51.1.4.0 and then proceed with the guide I linked.
Click to expand...
Click to collapse
THANK YOU! While doing the keyboard trick there were a couple of times it stuck on the static amazon logo so it must have detected that, but 4 or 5 times connecting to my computer trying to fastboot it did not. I have to go to the Zoo right now, but will continue this later. Just one more question: As long as I'm now in recovery, I should be able to recover. Right? I already went out and bought another rootable FTV, but if this one is saved I can just go return that one.
supremekizzle said:
THANK YOU! While doing the keyboard trick there were a couple of times it stuck on the static amazon logo so it must have detected that, but 4 or 5 times connecting to my computer trying to fastboot it did not. I have to go to the Zoo right now, but will continue this later. Just one more question: As long as I'm now in recovery, I should be able to recover. Right? I already went out and bought another rootable FTV, but if this one is saved I can just go return that one.
Click to expand...
Click to collapse
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.
AFTVnews.com said:
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.
Click to expand...
Click to collapse
So, should I be using the ip shown as "current ip address in CWM" for ADB or the one I had written down from when it was working?
Nevermind. Cannot connect to either IP from adb
lol. I'm dumb. Gotta connect the ethernet.
.....flashed 51.1.4.0 annnnnnnddddd boot loop again gaaaahhhhhhhhhh. Help me fix AFTVNews and I will make a nice donation to you
BOOTED!!!!
AND.... On latest rooted version. Thanks for bearing with me through that emotional roller coaster of despair and hope. None of this would be possible without AFTVNews collecting all of the information into one place and all of the others who put so much work into this like rbox. Round of beers going out to those two via donation. Thank you!
AFTVnews.com said:
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.
Click to expand...
Click to collapse
Any suggestions?:
http://forum.xda-developers.com/fire-tv/help/fire-tv-boots-white-amazon-logo-screen-t3139511
supremekizzle,
Glad it worked out for you.:good:
supremekizzle said:
So, should I be using the ip shown as "current ip address in CWM" for ADB or the one I had written down from when it was working?
Nevermind. Cannot connect to either IP from adb
lol. I'm dumb. Gotta connect the ethernet.
.....flashed 51.1.4.0 annnnnnnddddd boot loop again gaaaahhhhhhhhhh. Help me fix AFTVNews and I will make a nice donation to you
BOOTED!!!!
AND.... On latest rooted version. Thanks for bearing with me through that emotional roller coaster of despair and hope. None of this would be possible without AFTVNews collecting all of the information into one place and all of the others who put so much work into this like rbox. Round of beers going out to those two via donation. Thank you!
Click to expand...
Click to collapse
Glad it all worked out and glad I could help!
For future reference, when you edit a post, it doesn;t trigger XDA to send out a notification to the user you're quoting (me). That's why I didn't respond to your last message until now (when I manually checked it). Post a reply and use the '@' symbol (like this: @supremekizzle ) to ensure the user gets notified.
Hi guys,
I received a brand new 4k Stick yesterday.. it worked like a charm for 20 min, I installed a few thing (some regular apps), and then when I rebooted it started the loop with the amazon logo over and over again --> youtube.com/watch?v=zK5a-2MILOU
I dont know what to do; my FireStick is not rooted so I cant fastboot or adb it; I cant enter anywhere!
I dont have any OTG to connect a keyboard, neither a keyboard. I have been traying to solve with a thousand of ways which i read on this forum, but nothing fixed it.
I have 2 options, and i dont know if they will work:
1.- Buy o make a fastboot cable. I dont know if it works for Firestick, and I dont know what to do if it works! Should I install a new rom? Which one?!
2.- Buy a OTG and a keyboard to try to enter to the recovery mode. But if I actually enter in there, would I be able to fix it?
What do you guys think? What else can I do? Also I live in Chile, thereby Amazon dont want to send my a replacemente. :crying:
Thanks!!
try unbrick room
ruizit0 said:
try unbrick room
Click to expand...
Click to collapse
Yeah, but i cant install it... i cant enter with fastboot or adb because is unroot.
The fire stick 4k can be fickle little sod. Been trying to get play going so side loaded some stuff myself.
Mine will get stuck in a loop after a reboot yet a hard cut of power then it boots every time. So, have you unplugged it? I'm guessing you would of by now but you never know
ddoouubbllee said:
Hi guys,
I received a brand new 4k Stick yesterday.. it worked like a charm for 20 min, I installed a few thing (some regular apps), and then when I rebooted it started the loop with the amazon logo over and over again --> youtube.com/watch?v=zK5a-2MILOU
I dont know what to do; my FireStick is not rooted so I cant fastboot or adb it; I cant enter anywhere!
I dont have any OTG to connect a keyboard, neither a keyboard. I have been traying to solve with a thousand of ways which i read on this forum, but nothing fixed it.
I have 2 options, and i dont know if they will work:
1.- Buy o make a fastboot cable. I dont know if it works for Firestick, and I dont know what to do if it works! Should I install a new rom? Which one?!
2.- Buy a OTG and a keyboard to try to enter to the recovery mode. But if I actually enter in there, would I be able to fix it?
What do you guys think? What else can I do? Also I live in Chile, thereby Amazon dont want to send my a replacemente. :crying:
Thanks!!
Click to expand...
Click to collapse
You use the power brick that comes included with the firestick 4K?
Having the same problem with mine. I accidentally unplugged it without proper shutdown and when I re-plug it, it just loops endlessly. Using all the stock parts.
Even tried different chargers as suggested on reddit (Samsung fast charger, rated the same as the original Amazon charger), but nothing works.
Can't find any reset buttons or anything on this 4k stick.
Any suggestions?
doclucas said:
Having the same problem with mine. I accidentally unplugged it without proper shutdown and when I re-plug it, it just loops endlessly. Using all the stock parts.
Even tried different chargers as suggested on reddit (Samsung fast charger, rated the same as the original Amazon charger), but nothing works.
Can't find any reset buttons or anything on this 4k stick.
Any suggestions?
Click to expand...
Click to collapse
Just wait until @k4y0z ports his [UNLOCK][ROOT][TWRP][UNBRICK] Solution to the new FireTV 4k stick... or try to changing the stick at amazon.
Here is the thread for the 2gen stick (non4k version)
https://forum.xda-developers.com/fire-tv/development/unlock-fire-tv-stick-2nd-gen-tank-t3907002
Does anyone have any news on how to solve the problem?
After Looping about half a day 4K came up once.
You have to do a factory reset then, otherwise another half day on next boot up.
Network was USB-Hub - USB-Ethernet, don't know if important.