Related
Hey!
Lately I kept on playing with my kindle until the battery reached 0.
So I charged it but its stuck at the yellow Triangle and it turns off after a second or two.
Your problem is invaluable to the continued efforts of the developers.
Hey Im looking for a proper answer.
JoshuaLintag said:
Hey Im looking for a proper answer.
Click to expand...
Click to collapse
Maybe youll find a proper answer....in the proper forum...aka not the DEVELOPMENT forum ;D
Reported so it could be moved to the proper thread so you wont get flamed q&a
Sent from my Kindle Fire using Tapatalk 2
Help!
Anyone?
Adb does not detect it.
Sadly I am in the same boat! I am not getting anything to work.
http://forum.xda-developers.com/showthread.php?p=25400963
http://forum.xda-developers.com/showthread.php?p=25598837
THANKS!
BUT ADB DOES NOT DETECT IT.
sorry for caps
JoshuaLintag said:
THANKS!
BUT ADB DOES NOT DETECT IT.
sorry for caps
Click to expand...
Click to collapse
Did you happen to READ THE LINKS GIVEN TO YOU?
not sorry for caps
Your battery is near dead. You probably won't get anything to connect at this point without a factory cable. Which you would have known by READING THE LINKS GIVEN TO YOU.
I couldn't even charge mine
Okay, (even though I know this has been covered in the link I gave you) I'll be nice considering the possibility of a language barrier.
You need to get a factory programming cable (which I've said) so you can get into fastboot. Read about the factory cable and it's purpose here:
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
...and here:
http://forum.xda-developers.com/showthread.php?p=20317299
Then learn how to fix your drivers in case that's also contributing to the problem:
http://forum.xda-developers.com/showthread.php?p=23747671
Pay attention. The fix for this requires installing a new bootloader which (if you aren't careful) can PERMANENTLY brick your device.
Thanks for the links, btw.
I'm 13 and I don't know about making a factory cable, the steps on the links
is quite complicated. And Maybe risky.
Your only option then, would be to get a fastboot connection to flash the new FFF 1.4
This you may need to do several times to get it to work, if it works at all.
Make sure you know how to use fastboot
With the Kindle turned off, enter the following command:
Code:
fastboot flash bootloader /path/to/FFF1.4.bin
When you see "waiting for device" turn your kindle on.
If the installation takes place, all you need to do at that point is plug it into the wall charger.
If after several tries it still doesn't work you may want to try fixing your fastboot drivers. http://forum.xda-developers.com/showthread.php?p=23747671
Otherwise, a factory cable is your only option.
oh crap.
I think it's really dead.
It doesn't work, my computer won't detect it and it won't even show up
on device manager when I turn it on.
sorry man
Hi , I do apologies if this is a repeated thread. I am very new with KF. My friend gave his KF which the model says 3HT7G and I guess is the 2nd gen KFHD 8.9". This KF doesn't power on at all.I tryied to hold the power button for 20 sec. and nothing happened. Did it again and connect to the power and nothing happened. I connected to 2 different win 7 pcs one of them didn't recognised at all. The other ine says unknow device. Even unistall driver and use the driver which I found on this website didn't work at all. What I know is that my friend tryied to root it maybe with the wrong version (for 1st gen?). My question is , is there any chance to try to recover it ?
carmocci said:
Hi , I do apologies if this is a repeated thread. I am very new with KF. My friend gave his KF which the model says 3HT7G and I guess is the 2nd gen KFHD 8.9". This KF doesn't power on at all.I tryied to hold the power button for 20 sec. and nothing happened. Did it again and connect to the power and nothing happened. I connected to 2 different win 7 pcs one of them didn't recognised at all. The other ine says unknow device. Even unistall driver and use the driver which I found on this website didn't work at all. What I know is that my friend tryied to root it maybe with the wrong version (for 1st gen?). My question is , is there any chance to try to recover it ?
Click to expand...
Click to collapse
If he tried to use kindle fire utility on a kindlfe fire 8.9" then it is ruined, only way to recover from that is to solder a sdcard reader to the motherboard and reflash the bootloader from a linux os. I havent checked to see if that is definately the 8.9" model or not. Usually its hard bricked if it wont even power on.
Thank you very much for your reply. Do you know where to find a guide about how to do that. Anyway it is a8.9"
I also saw that is possible to change the motherboard is that true?
Thanks again.
carmocci said:
Thank you very much for your reply. Do you know where to find a guide about how to do that. Anyway it is a8.9"
I also saw that is possible to change the motherboard is that true?
Thanks again.
Click to expand...
Click to collapse
You can replace the motherboard, but if you want any of your data back frist i suggest the other method. Lemme find a link: http://forum.xda-developers.com/showthread.php?t=2581124
i Don't remember if it has the instructions or not so lemme find the kf2 thread that has the instructions, The instructions are basically the same, only difference is that the pinouts for what to solder where are different and when you finally do get it working you have substitute the bootloader with the correct one for the kindl efire 8.9" rather than the kf2's.
http://forum.xda-developers.com/showthread.php?t=2415870
stunts513 said:
You can replace the motherboard, but if you want any of your data back frist i suggest the other method. Lemme find a link: http://forum.xda-developers.com/showthread.php?t=2581124
i Don't remember if it has the instructions or not so lemme find the kf2 thread that has the instructions, The instructions are basically the same, only difference is that the pinouts for what to solder where are different and when you finally do get it working you have substitute the bootloader with the correct one for the kindl efire 8.9" rather than the kf2's.
http://forum.xda-developers.com/showthread.php?t=2415870
Click to expand...
Click to collapse
I just wanted to verify replacing the motherboard would fix the problem. I have hard bricked my wife's Kindle Fire 8.9 HD. Can't turn it on, no response with connected to a computer. I tried detaching and reattaching the battery but no luck. If replacing the motherboard will work, I am willing to give it a try.
Yea you can replace the motherboard to fix a hard brick, but if you have a soldering iron then you could fix it without replacing the motherboard.
Hey guys,
i just wiped my system and accidently plugged it off at recovery, now im stucked on the amazon logo. :good:
im not sure if my amazon is unlocked, i guess not. All i did was kingroot it, flash the preroot and install the twrp recovery.
So i guess i did a great job... there isnt a way in unbrick it, is there?
Another question, is amazon able to find anything rooted if i send them my firetv to let them repair it?
the only thing that i didnt wipe was the internal drive...
Thanks for any help...
http://forum.xda-developers.com/fir...anced-wipe-t3398644/post67404870#post67404870
THIS METHOD ONLY WORKS WITH FIRE TV UNLOOCKED
so nothing for me? found that already :/
my device need to get unlocked seperate, right? my procedure didnt do anything with the bootloader?
something noticeable after wiping for amazon? thinking of sending them my device with the reason update failed or something.
im still on guarantee
is there still no other option to save the firetv?
I think there was someone that was unlocking theirs in fastboot with cuberHDX, if that works, you should be able to recover. Also, if amazon cared, yes they could tell you messed with it.
Unlikely, but did you see if ADB connects, and you can su? usb a-a cable
hey, thanks for ur reply. No i didnt, because until now i had no need to use an a-to-a usb... but im thinking to buy one now...
are u sure they could tell? its very unlikely to have a system completely erased with internalstorage and co, isnt it? :/ sigh
so i bought an a-to-a USB and my pc is recognizing my firetv as firetv but soon after its disconnecting. Is there still hope with cuberhdx? or anything? and could someone post me a guide?
This FireTV has never been opened. I blocked updates per Aftvnews guide. ALso from AFTVnews serial conversion to software showed version 51.1.01 or 51.1.02. Unfortunately, I did not recall these version will not get past update screen if you are blocking updates. I had let sit at the update screen for over 30 minutes, then pulled plug. Now no lights, nothing. Tried ALT-PrtSCr-i and ALT-SysRq nothing. I bought USB A-A cable and windows shows QUB-xxxxx(or close to this from memory). Downloaded Ubuntu LiveCD and it shows 6 partitions from 17MB, 6.1GB, 2x 805MB, 2 x 8.4MB.
So not unlocked bootloader, no CWM, no TWRP nothing becasue this was A Virgin AFTV 1.
I have searched, requested help in other threads and no response and do not know what else can be done.
I do not know linux, but can follow steps and have updated 2 AFTV1 with rbox methods.
Is there anyway to save this Virgin AFTV1?
Im in the exact same boat.. But in deeper waters.. Fire Tv is only recognized as Qualcomm com port (Qualcomm HS QDLoader 9008) without showing the partitions, either in windows or linux... Never tried to install a recovery like Twrp, to unlock the bootloader, just had root since day one. But suddenly, when installing the last update something happened after the "Optimizing system storage and applications" menu. A bricked fire tv. Unfortunatelly i cant find a single trick to work... And yes.. I looked everywhere for a solution..
jj^2 said:
This FireTV has never been opened. I blocked updates per Aftvnews guide. ALso from AFTVnews serial conversion to software showed version 51.1.01 or 51.1.02. Unfortunately, I did not recall these version will not get past update screen if you are blocking updates. I had let sit at the update screen for over 30 minutes, then pulled plug. Now no lights, nothing. Tried ALT-PrtSCr-i and ALT-SysRq nothing. I bought USB A-A cable and windows shows QUB-xxxxx(or close to this from memory). Downloaded Ubuntu LiveCD and it shows 6 partitions from 17MB, 6.1GB, 2x 805MB, 2 x 8.4MB.
So not unlocked bootloader, no CWM, no TWRP nothing becasue this was A Virgin AFTV 1.
I have searched, requested help in other threads and no response and do not know what else can be done.
I do not know linux, but can follow steps and have updated 2 AFTV1 with rbox methods.
Is there anyway to save this Virgin AFTV1?
Click to expand...
Click to collapse
Was it a refurb? I had a refurb that had no power out of the box. Sent it back.
cancelyourcable said:
Was it a refurb? I had a refurb that had no power out of the box. Sent it back.
Click to expand...
Click to collapse
No, brand New.
Does the update work thru the usb?
walkabouts said:
Im in the exact same boat.. But in deeper waters.. Fire Tv is only recognized as Qualcomm com port (Qualcomm HS QDLoader 9008) without showing the partitions, either in windows or linux... Never tried to install a recovery like Twrp, to unlock the bootloader, just had root since day one. But suddenly, when installing the last update something happened after the "Optimizing system storage and applications" menu. A bricked fire tv. Unfortunatelly i cant find a single trick to work... And yes.. I looked everywhere for a solution..
Click to expand...
Click to collapse
Yes, I thought we would get some responses from somebody. Possibly even @rbox and @aftvnews.
I wish i was in your situation... You can always dd the partitions again, and eventually fix the brick... In my case (QDLoader 9008) there is nothing i can do. Eventually i could theoretically reprogram the emmc chip, but.. not going to happen. I presume you are in stuck in the Qualcomm HS QDLoader 9006, that should be fixable, since you can write to the partitions. There is a post from Rbox where he tells in detail what to do. Best of luck!
Since your FTV its still showing its partitions (unlike me!) you should be successful with these instructions. https://forum.xda-developers.com/showpost.php?p=66961740&postcount=676
walkabouts said:
Since your FTV its still showing its partitions (unlike me!) you should be successful with these instructions. https://forum.xda-developers.com/showpost.php?p=66961740&postcount=676
Click to expand...
Click to collapse
Thanks for the idea, but i did not have any chance to unlock my bootloader. So, this will not help.
jj^2 said:
Thanks for the idea, but i did not have any chance to unlock my bootloader. So, this will not help.
Click to expand...
Click to collapse
You're absolutely right... Unfortunately.. Perhaps someone in a near future discover a way to bring it to life. But for now we're holding useless bricks..
walkabouts said:
You're absolutely right... Unfortunately.. Perhaps someone in a near future discover a way to bring it to life. But for now we're holding useless bricks..
Click to expand...
Click to collapse
Has anyone been able to download update files and put on usbdrive and have the AFTV read the usb?
Please Help
jj^2 said:
Has anyone been able to download update files and put on usbdrive and have the AFTV read the usb?
Please Help
Click to expand...
Click to collapse
From my experiences, won't work. The fire tv don't read the update.zip. Without access to a workable recovery, a unlocked bootloader, or functional ADB, there is no way to revive this thing. I would love to be wrong, though..
walkabouts said:
From my experiences, won't work. The fire tv don't read the update.zip. Without access to a workable recovery, a unlocked bootloader, or functional ADB, there is no way to revive this thing. I would love to be wrong, though..
Click to expand...
Click to collapse
Walkabout,
Thanks for the feedback. Really disappointed of the lack of responses from the XDA Community
jj^2 said:
Walkabout,
Thanks for the feedback. Really disappointed of the lack of responses from the XDA Community
Click to expand...
Click to collapse
To be honest, me too. But probably, since they all have hardware in working conditions, they aren't facing the same problems as us. Perhaps one of this days Rbox bricks his AFTV, and we get a way to solve our problem..
Any news on your brick? Just had an idea, although don't know if it works, and I don't have another working fire TV. But if a backup is made on QPST from a working fire TV, and then restore that same backup on the bricked unit (using again QPST) it might restore the unit. Mmmm.. Eventually! Damn, unfortunately I don't have a good unit to backup!
walkabouts said:
Any news on your brick? Just had an idea, although don't know if it works, and I don't have another working fire TV. But if a backup is made on QPST from a working fire TV, and then restore that same backup on the bricked unit (using again QPST) it might restore the unit. Mmmm.. Eventually! Damn, unfortunately I don't have a good unit to backup!
Click to expand...
Click to collapse
Still bricked, put in box hoping later someone could find a way. Ido have a workingAFTV1, but is rooted and updated to OS5. IF you have any idea how to do this I may entertain.
jj^2
Thanks for the reply! After thinking better about my approach, its pretty much pointless, since to make a backup via QPST we have to enter in EDL mode. And there is no way to make a healthy fire TV enter service mode, not even via fastboot. My bricked fire TV is just like yours, sitting in a drawer. But I haven't given up. At least my mind is busy!
Hey guys I've tried to install https://forum.xda-developers.com/fire-tv/development/firetv-1-bueller-twrp-recovery-t3383286,
I did the steps for the locked bootloader and I didn't notice that there were errors.
It is rooted and busybox is installed. But it's stuck at the amazon logo while booting.
Do you think it's possible to unbrick it when I buy an USB-A to USB-A cable?
Version is: 51.1.5.0 30720
Thanks for your help!
Update: Ok I was able to open the stock recovery mode and it was reseting but it still won't boot.
I've waited six hours still didn't boot.
Need help
I messed up with amazon fire tv first generatio, it's now not booting up, no light nothing... when i put male-male usb cable i see its storage but that's all. adb can't find device etc.. any help will be appreciated.
As the title states, my 2nd Gen Fire TV 's ethernet port stopped working.
I'm not sure when this happened as it was also connected to the wifi before so whenever it stopped working it must have just changed over to the wifi unbeknownst to me.
Anyway, I have an ethernet cable hooked up to it but it doesn't recognize it.
I have checked the ethernet cable on another Fire TV that I have and it works fine on that one.
I was just curious if this is a common problem with these boxes or is there anything I can check or try to get it working again?
Both of my Fure TVs are rooted although that shouldn't matter other than possibly making them easier to check or change stuff on.
KB! said:
As the title states, my 2nd Gen Fire TV 's ethernet port stopped working.
I'm not sure when this happened as it was also connected to the wifi before so whenever it stopped working it must have just changed over to the wifi unbeknownst to me.
Anyway, I have an ethernet cable hooked up to it but it doesn't recognize it.
I have checked the ethernet cable on another Fire TV that I have and it works fine on that one.
I was just curious if this is a common problem with these boxes or is there anything I can check or try to get it working again?
Both of my Fure TVs are rooted although that shouldn't matter other than possibly making them easier to check or change stuff on.
Click to expand...
Click to collapse
From twrp do a full wipe and reflash fireos firmware.
You're ethernet should then work again.
Bertonumber1 said:
From twrp do a full wipe and reflash fireos firmware.
You're ethernet should then work again.
Click to expand...
Click to collapse
So you think it is a software problem?
I was thinking it may be a hardware issue since it was working fine and then just stopped all of a sudden.
I will definitely try your suggestion though as I plan on unlocking the bootloader on this one as well.
KB! said:
So you think it is a software problem?
I was thinking it may be a hardware issue since it was working fine and then just stopped all of a sudden.
I will definitely try your suggestion though as I plan on unlocking the bootloader on this one as well.
Click to expand...
Click to collapse
Yes, sometimes ethernet/wifi drivers and files can become corrupted.
Flashing fresh firmware should sort your problem.
Let me know how you get on.
Regards
Bertonumber1 said:
Yes, sometimes ethernet/wifi drivers and files can become corrupted.
Flashing fresh firmware should sort your problem.
Let me know how you get on.
Regards
Click to expand...
Click to collapse
I will definitely update this thread. I am hoping to maybe try this tonight.
KB! said:
I will definitely update this thread. I am hoping to maybe try this tonight.
Click to expand...
Click to collapse
If you're not unlocked or don't want to unlock your bootloader just flash rbox latest prerooted again. This should solve your ethernet issues.
Leave the ethernet cable disconnected whist you do so and complete registration via wifi til you get to home screen. Then enter network settings and plug your ethernet cable back in.
Regards
Bertonumber1 said:
If you're not unlocked or don't want to unlock your bootloader just flash rbox latest prerooted again. This should solve your ethernet issues.
Leave the ethernet cable disconnected whist you do so and complete registration via wifi til you get to home screen. Then enter network settings and plug your ethernet cable back in.
Regards
Click to expand...
Click to collapse
So unlocked the bootloader and flashed the latest stock OS 5.2.7.7 and Magisk and plugged in the ethernet cable after setting everything up over Wi-Fi and it still doesn't recognize that there is an ethernet cable plugged in.
I know the ethernet cable is good as it works perfectly with my other Sloane Fire Tv.
Any other suggestions?
Are there any commands I could run in ADB to check or enable the ethernet port?
KB! said:
So unlocked the bootloader and flashed the latest stock OS 5.2.7.7 and Magisk and plugged in the ethernet cable after setting everything up over Wi-Fi and it still doesn't recognize that there is an ethernet cable plugged in.
I know the ethernet cable is good as it works perfectly with my other Sloane Fire Tv.
Any other suggestions?
Are there any commands I could run in ADB to check or enable the ethernet port?
Click to expand...
Click to collapse
Hey , I don't think there is im afraid . If you're ethernet isn't showing up after reinstalling firmware its looking more like a hardware fault after all.
You could disconnect WiFi enable usb debugging and run:
logcat
via adb to see what errors are showing .
Regards