[Q] Stuck installing Google Play Store - Fire TV Q&A, Help & Troubleshooting

So, I'm newly rooted trying to install Google Play Store on my Fire TV
CWM recovery
running 51.1.4.0_514006420 pre-rooted ROM
installed the XPOSED FRAMEWORK and HDXPOSED.APK
rebooted and now it's stuck at the Amazon splash screen. Did I brick it?
Any ideas of what I can do now?
Thanks

detatched said:
So, I'm newly rooted trying to install Google Play Store on my Fire TV
CWM recovery
running 51.1.4.0_514006420 pre-rooted ROM
installed the XPOSED FRAMEWORK and HDXPOSED.APK
rebooted and now it's stuck at the Amazon splash screen. Did I brick it?
Any ideas of what I can do now?
Thanks
Click to expand...
Click to collapse
Try giving more info. I assume it was working fine before you installed xposed? By splash screen you mean just "amazon" white or the colored logo?
I never had any issues with xposed but if theres anything you can add someone might be able to help.

Sorry, yeah it was working fine with Kodi and Llama installed and configured. Streamed the NBA finals game fine. Then I installed and launched those 2 apps and rebooted. Now it's stuck at the Black and white Amazon screen. Not the colored logo. I tried unplugging it and plugging back in but no luck
i can still adb connect to it's ip, but i can't do adb shell or ping it.

detatched said:
Sorry, yeah it was working fine with Kodi and Llama installed and configured. Streamed the NBA finals game fine. Then I installed and launched those 2 apps and rebooted. Now it's stuck at the Black and white Amazon screen. Not the colored logo. I tried unplugging it and plugging back in but no luck
i can still adb connect to it's ip, but i can't do adb shell or ping it.
Click to expand...
Click to collapse
If you can connect adb you should be able to reboot recovery. From there you can do a factory reset. This will wipe data, but root will remain intact (might need to reinstall busybox, not sure.) You can try that or see if anyone else has an easier solution. I'm really puzzled why your stuck. Lots of people using that xposed mod.

KLit75 said:
If you can connect adb you should be able to reboot recovery. From there you can do a factory reset. This will wipe data, but root will remain intact (might need to reinstall busybox, not sure.) You can try that or see if anyone else has an easier solution. I'm really puzzled why your stuck. Lots of people using that xposed mod.
Click to expand...
Click to collapse
I tried that, but nothing happens. It lets me connect to the ip, but it doesn't take any commands. I can't adb shell or even ping it. It's weird, when I try to ping it, the response is from a different ip address that says it is unreachable

fixed
Well after letting it sit unplugged overnight I plugged it back in today and it booted up ok. I finished installing the Play Store and it seems to work fine.
I let it sit on the black and white splash screen for an hour or so last night before unplugging it for the night. I don't know what happened, but glad it's back up and not bricked.
Thanks for the help!

Related

[Q] Kindle Fire keeps restarting to yellow triangle

Three days ago I went through the process of rooting my kindle fire using KFU. Being a noob, this took me many many hours. I got everything to work, GO Launcher, Google Play, Amazon App store. I even used the Voodoo OTA Rootkeeper to temporily un-root so that I can watch amazon streaming videos. I was feeling pretty good about my accomplishment.
Late last night, for no apparent reason, the Kindle Fire restarted itself and got stuck on the yellow triangle (is this FireFireFire?). I got nervous, freaked out a little. I plugged into my computer and tried to restart the Kindle after selecting 'Recovery (5001)'. No luck. I then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief. It booted up just fine. This was about 2 hours ago.
But, now, my Kindle randomly goes back to the yellow triangle and hangs there. I need to go through the same process above to fix things. This has happened at least four times already. It did not seem to happen while the Kindle was "connected" to my computer. It happens once I 'disconnect'.... usually after about 10 - 20 minutes. It has happened while using both GO Launcher EX and the Amazon Launcher. Any idea?
You've got the same issue I do - the kindle keeps trying to apply the new update, and it isn't working, dumping it into recovery mode. I haven't figured out an answer to getting the update successfully applied yet (will work on that tonight), but until that happens, you should be able to remove the update from the sdcard /kindleupdates, and through something like root explorer rename /etc/security/otacerts.zip to something like /etc/security/otacerts.bak (or better yet, move it to the sdcard). That will stop it from redownloading the update and auto-rebooting.
Look Here
Have you looked at this http://forum.xda-developers.com/showthread.php?t=1417234 thread. The video explains the most common fix, and he goes through it step by step.
Also, so you grow a thick skin for posting on this forum, check out this link http://forum.xda-developers.com/showthread.php?t=1633343.
Hope this helps
Thanks for listening.
Sincerely,
William
[Kindle Fire: gedeROM v1.2 {3.0 Kernel, CM9, Android 4.0.4} - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
Ok. I just tested it, and had it also confirmed in another thread, but here is one way to get 6.3.1 on when the update fails to apply, putting you into the recovery, force to normal boot, kindle updates, back to recovery loop:
if you have a copy on your device, copy the update to the root of the sdcard volume or download it from amazon. Rename the file update.zip, then reboot into recovery.
Under install, install the update.zip. Once it is done, you'll have 6.3.1 applied. Now, you'll have to both reroot, and reinstall recovery, but since you just did it with KFU a few days ago, it should be pretty quick. Then go move/rename the otacerts.zip file to prevent the next unexpected update.
There might be another way that doesn't blow away recovery, but this worked for me.
Thanks so much for all of the help! It looks like everything is working again. I got 6.3.1 installed (not really sure how that happened but it did!). Also got re-rooted and reinstalled TWRP and did a backup. I renamed the otacerts.zip. There is also a cacerts.bks file in the /etc/security directory... what does that do?
Also... will I ever want/need the updates? I assume renaming the otacerts.zip stops the updates indefinitely. Will this ever be a problem?
Thanks again!
Moving the otacerts.zip prevents the kindle from automatically downloading updates. When a new update has been released, you can download it from amazon's site manually, or put back the cert file to enable the download. Since updates often break root, this method will help keep you rooted until it is known how to root the new versions. As for want/needing them, it'll depend on what changes, but as long as they are rootable, they should generally bring improvements for the device.
The. bks file is a keystore for the certificate authority certs. You shouldn't need to ever touch that file.
powers down
Ok, I've got the exact same issue but one glaring difference. That after using KFU to boot to normal, it within 10-20sec powers down. Starting the bootloop all over. Don't know what to do, please help.
Does it actually fully boot into the kindle os? I haven't heard of it trying to apply the update that fast after start up, but not saying that it won't do that.
If using twrp, you can mount the kindle over usb from twrp - mount, and then move the update file out of kindleupdates. That should stop the boot cycle if it is being caused by the update. Another thing to check would be to look at the twrp console and make sure it is complaining about the update failing and not something else.
When I try to mount it ask me to format the drive, is that safe? Won't I lose everything then? Also, it won't allow me to select just the sd, it only allows me to select system.
ms6146 said:
Ok, I've got the exact same issue but one glaring difference.
Click to expand...
Click to collapse
That sounds eerily familiar...Where have I seen that before?
That after using KFU to boot to normal, it within 10-20sec powers down. Starting the bootloop all over. Don't know what to do, please help.
Click to expand...
Click to collapse
Only kidding...Actually that problem isn't the same at all and is described in detail here: http://forum.xda-developers.com/showthread.php?p=25400963
ms6146 said:
When I try to mount it ask me to format the drive, is that safe? Won't I lose everything then? Also, it won't allow me to select just the sd, it only allows me to select system.
Click to expand...
Click to collapse
Formatting your sdcard will erase everything on it. Besides trying to mount your sdcard, what are you trying to accomplish?
Well I'm stuck in bootloop with the powering off problem. The kindle is not recognized on the computer. All I want is to get the kindle back working. I have tried the unbrick utility but I think that made it worse. Getting back to a regular firmware even if its the latest would be fine. However being the noob that I am, I need step by step instructions. Thanks in advance.
ms6146 said:
Well I'm stuck in bootloop with the powering off problem. The kindle is not recognized on the computer. All I want is to get the kindle back working. I have tried the unbrick utility but I think that made it worse. Getting back to a regular firmware even if its the latest would be fine. However being the noob that I am, I need step by step instructions. Thanks in advance.
Click to expand...
Click to collapse
Your problem can still be fixed, but considering the fact you can't get the computer to recognize your device, you only have a couple of options left:
You could acquire a factory cable which would directly power your device in order to replace the bootloader.
If you don't have the means to acquire a factory cable you need to mount your sdcard in order to transfer FFF1.4 for flashing in recovery. From what I understand in your earlier post, it would in your case, require formatting your sdcard
yellow triangle and restart, please help
Jarden said:
Three days ago I went through the process of rooting my kindle fire using KFU. Being a noob, this took me many many hours. I got everything to work, GO Launcher, Google Play, Amazon App store. I even used the Voodoo OTA Rootkeeper to temporily un-root so that I can watch amazon streaming videos. I was feeling pretty good about my accomplishment.
Late last night, for no apparent reason, the Kindle Fire restarted itself and got stuck on the yellow triangle (is this FireFireFire?). I got nervous, freaked out a little. I plugged into my computer and tried to restart the Kindle after selecting 'Recovery (5001)'. No luck. I then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief. It booted up just fine. This was about 2 hours ago.
But, now, my Kindle randomly goes back to the yellow triangle and hangs there. I need to go through the same process above to fix things. This has happened at least four times already. It did not seem to happen while the Kindle was "connected" to my computer. It happens once I 'disconnect'.... usually after about 10 - 20 minutes. It has happened while using both GO Launcher EX and the Amazon Launcher. Any idea?
Click to expand...
Click to collapse
Hello Jarde, I have the same problem but I am super noob, my kindle is restarting at the yellow triangle every 3 seconds, you said " then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief", what do you mean selecting 'Normal (4000)', how can I do this?, and finally how did you solve the problem, thanks a lot and sorry for my poor english.
notforever said:
Hello Jarde, I have the same problem but I am super noob, my kindle is restarting at the yellow triangle every 3 seconds, you said " then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief", what do you mean selecting 'Normal (4000)', how can I do this?, and finally how did you solve the problem, thanks a lot and sorry for my poor english.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=25400963
I had the same issue - shutdown after a few seconds after boot, then the KF boots back into yellow triangle error.
I was able to get out of this loop by booting into recovery and wiping the cache partition (and the Dalvik cache for good measure) to remove the downloaded update file. After wiping the caches, my KF rebooted normally without issue. I could then us Root Explorer to rename the /etc/security/otacerts.zip file to something else as suggested in an earlier post. I have not had a problem since.

Just got Factory Cable from SKORPN, now what? Lol

I believe im having the "5 second bootloop" problem, no idea why since my KF was never rooted, flashed, or modified in any way. I plugged the Micro B in the KF (KF was off) and then plugged the Type-A end into my PC, the KF turned on in like 10 seconds (maybe less) and it isn't doing the bootloop anymore which i guess is a good thing but its been like 10 minutes and it still just says kindle fire (with a green light on the bottom). What should I do from here for my specific situation? Any help would be great! Thanks in advance!
edit: just wanted to add that before when i would plug it in, it would keep rebooting and usually not even get to the slide to unlock screen, but sometimes it would and then instantly reboot again.
First off...what bootloader do you have installed?
How could I find out? I never modified it if that helps? So it should be stock everything.
also i downloaded KFU and installed the drivers, but it does not recognize my device, altho when i first plugged it in after installing the drivers it said kindle in Device Manager, since it didnt go anywhere i unplugged the kindle and turned it off, when i tried again it installed ADB, but still doesnt recognize it (it also prompted me to restart, which i did right before i posted this reply, and still not recognized, also still at the kindle fire screen with green light on)
Untraumatized said:
How could I find out? I never modified it if that helps? So it should be stock everything.
also i downloaded KFU and installed the drivers, but it does not recognize my device, altho when i first plugged it in after installing the drivers it said kindle in Device Manager, since it didnt go anywhere i unplugged the kindle and turned it off, when i tried again it installed ADB, but still doesnt recognize it (it also prompted me to restart, which i did right before i posted this reply, and still not recognized, also still at the kindle fire screen with green light on)
Click to expand...
Click to collapse
ok so i read that sometimes it just wont read that it worked... so i check device manager, it said android phone, went to KFU, still said unknown after 0+enter, then i tried 3, it said it worked and to press any key to reboot, i pressed a key but the kindle didnt reboot, is it supposed to? also i tried 4 then like i read to do and it says the download path is incorrect so whats wrong?
Untraumatized said:
ok so i read that sometimes it just wont read that it worked... so i check device manager, it said android phone, went to KFU, still said unknown after 0+enter, then i tried 3, it said it worked and to press any key to reboot, i pressed a key but the kindle didnt reboot, is it supposed to? also i tried 4 then like i read to do and it says the download path is incorrect so whats wrong?
Click to expand...
Click to collapse
sorry for triple posting i will fix it but i dont want to confuse you on the timing of these events lol... so i figured out that CWM may be broken right now??? anyways since twrp worked i insatlled FFF with worked and now its at a menu that is kindle fire but BLUE fire text and says press power button for boot menu, but when i do that it doesnt do anything, do i need to unplug it?
Untraumatized said:
sorry for triple posting i will fix it but i dont want to confuse you on the timing of these events lol... so i figured out that CWM may be broken right now??? anyways since twrp worked i insatlled FFF with worked and now its at a menu that is kindle fire but BLUE fire text and says press power button for boot menu, but when i do that it doesnt do anything, do i need to unplug it?
Click to expand...
Click to collapse
you still there buddy? lol, i unplugged it and ya that worked, so now im at TWRP, just because it seems like a good idea i am backing up the things that were already checkmarked when i clicked backup
but now im afraid to continue without help, what step am i at exactly now? lol
EDIT: stuck at the end of the backup, been stuck there a while, will probably try to turn it off in a few minutes or so... anybody have some advice?
How about a little more information about what it is you intend to accomplish with your device?
soupmagnet said:
How about a little more information about what it is you intend to accomplish with your device?
Click to expand...
Click to collapse
i just want it to work! my power went out one day while i was sleeping and it was charging, for some reason it was dead (had been at 100% so shouldnt have drained, but the power going out messed with it) and when i tried to charge it, it bootloops
right now i have TWRP installed and FFF installed, what should i do now? i have tried booting it up and it just gets to the slide to unlock screen and then resets back to the blue kindle fire screen
i also just tried to install permanent root with superuser and it seemed to be working then said rebooting and "please wait...." and it never did anything (except the kindle booted back to the blue kind fire screen)
Untraumatized said:
i just want it to work! my power went out one day while i was sleeping and it was charging, for some reason it was dead (had been at 100% so shouldnt have drained, but the power going out messed with it) and when i tried to charge it, it bootloops
right now i have TWRP installed and FFF installed, what should i do now? i have tried booting it up and it just gets to the slide to unlock screen and then resets back to the blue kindle fire screen
i also just tried to install permanent root with superuser and it seemed to be working then said rebooting and "please wait...." and it never did anything (except the kindle booted back to the blue kind fire screen)
Click to expand...
Click to collapse
ANY help would be appreciated... im sitting here screwing with it waiting for a reply....
Untraumatized said:
ANY help would be appreciated... im sitting here screwing with it waiting for a reply....
Click to expand...
Click to collapse
well i managed to fix it by just factory resetting it with no help AT ALL
Very likely the factory reset had nothing to do with it. Just simply having it plugged in via USB may have given it enough time to charge. Questions of this nature are best handled in q & a not in development.
Untraumatized said:
well i managed to fix it by just factory resetting it with no help AT ALL
Click to expand...
Click to collapse
I'm sorry for not sitting at my computer, waiting with baited breath for you to respond, so I can devote all of my attention to your problem. I hope you can forgive me.
I wasnt trying to be offensive lol I was just proud to figure it out with NO HELP AT ALL! But anyways I am pretty sure it wasnt the charge because it was at 56% before and after i did the factory reset, and after the factory reset i backed it up and it finished that time (last time i had to unplug the KF and hard reset it)... Also I tried resetting it a couple times before the factory reset and it always rebooted once it got to the slide to unlock screen. Anyways it works, I am probably going to give it to my mom because of the simplicity (she just needs email, and internet... lol) and I might try to get my hands on a Nexus 7
AND HOW DO I DELETE ALL THOSE REPOSTS? THE DELETE BUTTON ISNT WORKING FOR ME ^__^'
Untraumatized said:
I wasnt trying to be offensive lol I was just proud to figure it out with NO HELP AT ALL! But anyways I am pretty sure it wasnt the charge because it was at 56% before and after i did the factory reset, and after the factory reset i backed it up and it finished that time (last time i had to unplug the KF and hard reset it)... Also I tried resetting it a couple times before the factory reset and it always rebooted once it got to the slide to unlock screen. Anyways it works, I am probably going to give it to my mom because of the simplicity (she just needs email, and internet... lol) and I might try to get my hands on a Nexus 7
AND HOW DO I DELETE ALL THOSE REPOSTS? THE DELETE BUTTON ISNT WORKING FOR ME ^__^'
Click to expand...
Click to collapse
Correct me if im wrong but you can't delete posts....but this thread should not be in Android Dev section, it should be in Q and A... Not to be mean or anything I am going to report this thread so it can be moved to the right section (to help the mods out)
OP, First This Thread Is In The Wrong Place. And It Appears To Me Users Where Trying To Help, On Limited Information. But You Figure It Out On Your Own Great.
Thank You And Thread Closed.

[Q] Kindle Fire 1st gen Un-romming

The Problem I am having seems to be a Infinite boot logo after Undoing a custom Otter jelly bean KF rom. I went through the motions of ADB KFU booting into recovery. I factory restored, wiped and attempted to install my back up of the stock kindle fire rom. wiped caches, and then let it do its "boot up" how ever it did not move past that point, and has been stuck at the "kindle fire" logo screen.
Is there anyway to fix what I probably broke?
KFU Utility vers 0.9.6
TWRP vers 2.4.4
OS version Windows 8 X64
Kindle fire Rom version 6.2.1
Otter jelly bean was 4.2.1 a release sometime in February is the closest I can get. I can't exactly roll back now can I?
Any other information I forgot or neglected to supply on first post was unintentional. First time I have ever had a problem.
Thanks in advance
~ Zach
I had that problem awhile back. What I ended up doing was flashed another ROM and then see if it worked(it did). Then I flashed the stock ROM again and deleted everything. Cache, SD, factory reset etc. After that it seemed to be working just fine.
Sent from my Nexus 7 using xda app-developers app
jakeyablosky said:
I had that problem awhile back. What I ended up doing was flashed another ROM and then see if it worked(it did). Then I flashed the stock ROM again and deleted everything. Cache, SD, factory reset etc. After that it seemed to be working just fine.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
My problem is, I can't get the device out of this logo "loop" it won't let me install TWRP or the other one. Let alone get into the TWRP currently installed. I wonder if I can get Screen Shots up on here.
leroy329 said:
My problem is, I can't get the device out of this logo "loop" it won't let me install TWRP or the other one. Let alone get into the TWRP currently installed. I wonder if I can get Screen Shots up on here.
Click to expand...
Click to collapse
I think you're having the same problem I'm having. If you look at my post regarding stuck at logo that I posted yesterday see if it's the same.
What is your logo doing? Does it stay bright or does it turn on and blink and then fade?
Based on what I've read we need them to get them into fastboot and then side load TWRP and FFF and start again.
I think what we've done is removed or cleared too much in TWRP and our bootloaders are broken, but I could be talking out of my you know what.
Good luck to you and I will follow your thread and you may want to follow mine.
The only thing I can think of is getting a Factory Cable and reset you Kindle Fire
Sent from my Nexus 7 using xda app-developers app
Leroy,
I think Jakey has it.
I was just about ready to pitch this thing in the trash and I decided to plug in my factory cable one last time and run KFU.
For whatever reason I decided to select the root option again even though it said status offline and it rerooted my device.
My logo is now white/blue and I think I can get a rom back onto it.
You may want to hit Skorpn up for a cable, he shipped it super fast and it's great work.
Leroy,
Since it seems you are having the same problem I was and replies are pretty slow in here these days (I'm sure most people are tired of repeat posts like mine), I thought I would post precisely what I did to fix mine.
I too had the infinite boot logo that stayed bright and tried everything from KFU, to unbrick tool, to Soupkit, nothing seemed to work. I bought a factory cable from Skorpn, but didn't really understand how to use it. I think there is so much information here and many various ways to get things fixed it takes awhile to digest it.
Right before I got ready to pitch it in the trash I figured I would try KFU one more time even though it wasn't seeing my Kindle. Device manager saw the ADB drivers in Android device though.
I plugged in the factory cable
Launched KFU
Device said "offline"
Tried various options until I finally saw the install permanent root with superuser (option 2)
That did the trick
I then unplugged my factory cable from both the PC and KF and booted the KF into recovery
I downloaded a ROM (Hashcodes and GAPPS) and side loaded them
That did it!
I'm not sure how or why since it said it was offline but it fixed it.
Again, Skorpn was awesome to work with and sent the cable to me quickly.
Good luck to you!

[Q] My rooted FTV will be in recovery in the morning.

I have a rooted FTV with rbox newest prerooted firmware. The last few days I noticed that my FTV is on the CWM recovery screen in the morning and I need to find the keyboard to boot up.
I was wondering why it is doing this. I usually leave my FTV in Kodi before bed and don't usually exit out so it usually stays on. I haven't done anything different but still don't know why it's doing this.
Any suggestions?
yazyazoo said:
I have a rooted FTV with rbox newest prerooted firmware. The last few days I noticed that my FTV is on the CWM recovery screen in the morning and I need to find the keyboard to boot up.
I was wondering why it is doing this. I usually leave my FTV in Kodi before bed and don't usually exit out so it usually stays on. I haven't done anything different but still don't know why it's doing this.
Any suggestions?
Click to expand...
Click to collapse
My guess is you didn't disable updates. To do so connect over adb, drop down to adb shell then type pm disable com.amazon.dcp

Rooted FTV2 - Wiped System, Bricked?

Hey guys,
So it's been a while since updated my rooted FTV2 but decided to updated it to the latest prerooted image found on XDA. It had some freezing issue and I wiped the system and rebooted (didn't know I shouldn't reboot after a wipe). Now the fire tv is stuck on the white amazon logo with the black background. I can't access TWRP.
Is it bricked? Is there anyway I can restore it (considering I had TWRP on it before)? I tried connecting it via a USB A-A and on my Mac, with the android file transfer application, it would show could not connect to device. I tried listing the devices through "fastboot devices" but nothing shows up.
Is there any hope? Thank you.
DVO99 said:
Hey guys,
So it's been a while since updated my rooted FTV2 but decided to updated it to the latest prerooted image found on XDA. It had some freezing issue and I wiped the system and rebooted (didn't know I shouldn't reboot after a wipe). Now the fire tv is stuck on the white amazon logo with the black background. I can't access TWRP.
Is it bricked? Is there anyway I can restore it (considering I had TWRP on it before)? I tried connecting it via a USB A-A and on my Mac, with the android file transfer application, it would show could not connect to device. I tried listing the devices through "fastboot devices" but nothing shows up.
Is there any hope? Thank you.
Click to expand...
Click to collapse
It has been discovered that It is almost impossible to completely brick these devices by software only.
There is always a way to revive these devices and methods to recover them are becoming easier.
So don't throw them away and keep an eye on the other thread, there is hope.
.:HWMOD:.
hwmod said:
It has been discovered that It is almost impossible to completely brick these devices by software only.
There is always a way to revive these devices and methods to recover them are becoming easier.
So don't throw them away and keep an eye on the other thread, there is hope.
.:HWMOD:.
Click to expand...
Click to collapse
Thank you for the reply. I will definitely not throw them away. It was my fault that I didn't re-read all the warnings (lesson learned). Hopefully something comes up for it soon.
DVO99 said:
Thank you for the reply. I will definitely not throw them away. It was my fault that I didn't re-read all the warnings (lesson learned). Hopefully something comes up for it soon.
Click to expand...
Click to collapse
I did the same thing last night, not paying attention. I have two FTV2 though, managed not to mess up the other one. Here's hoping one day we can bring them back to life. :highfive:
Seriiez said:
I did the same thing last night, not paying attention. I have two FTV2 though, managed not to mess up the other one. Here's hoping one day we can bring them back to life. :highfive:
Click to expand...
Click to collapse
Haha, yeah it sucks. The worst part is in Canada there is only fire tv sticks, so I'm kinda stuck unless I get another android tv box.
Me too,
i tried to install Gapps, but with no success, the AFTV gen2 was rooted and working nice.
To eliminate the leftovers i tried to restore a /System and /Data backup with TWRP, but the system was wiped and the partitions was not maked again.
now i have a brick, with no fastboot and only amazon black&white logo
Any Ideas?

Categories

Resources