Anyone have the steps to take to preform a hard reset of fix a non booting device?
I am stuck on the amazon Fire TV part where the boot animation is doing nothing. Can't get past this screen and have been stuck for the last 10 minutes.
jamesrascal said:
Anyone have the steps to take to preform a hard reset of fix a non booting device?
I am stuck on the amazon Fire TV part where the boot animation is doing nothing. Can't get past this screen and have been stuck for the last 10 minutes.
Click to expand...
Click to collapse
End Result. If you brick you box Amazon has no troubleshooting steps outside of rebooting the box. Once you get past that step and your still having an issue Amazon will issue you a replacement FireTV.
You will need to call Amazon as the Live chat is useless: 866-216-1072 Press 0 and ask to be transferred to the Fire TV department.
jamesrascal said:
Anyone have the steps to take to preform a hard reset of fix a non booting device?
I am stuck on the amazon Fire TV part where the boot animation is doing nothing. Can't get past this screen and have been stuck for the last 10 minutes.
Click to expand...
Click to collapse
Oh, boy. That is unfortunate. What did you do that lead to bricking your box?
I am in the same situation with one of my FireTV box. What caused it was one of the SQLite editor I used to explore the settings database: it changed the permissions on the files. I only realized the problem once I rebooted it
On the other box, I used the SQLite3 command line client from TitaniumBackup instead, and directly did my edit as root. No problem there.
Unfortunately, I am not in US; so if there is a way to do a hard reset, I would be glad to know.
if you bought yours at a local best buy and are a select customer, you may have an extended return policy.
You must have edited something you shouldn't have with the sqlite editor. I edited mine to allow package installs and did a factory reset and its all good. Did you only disable the updates through pm disable com.amazon.dcp or did you also edit the /etc/hosts? Lets get this figured out so others don't end up the same way.
Stupid question, did you pick TWRP as a method of recovery during the rooting process? I did that on my note 10.1 and boy did it mess up that tablet when I tried to recover it. Luckily I had Odin at the time.
Sent from my SM-N900V using Tapatalk
arman68 said:
I am in the same situation with one of my FireTV box. What caused it was one of the SQLite editor I used to explore the settings database: it changed the permissions on the files. I only realized the problem once I rebooted it
On the other box, I used the SQLite3 command line client from TitaniumBackup instead, and directly did my edit as root. No problem there.
Unfortunately, I am not in US; so if there is a way to do a hard reset, I would be glad to know.
Click to expand...
Click to collapse
Do you recall which sqlite editor app you used that caused the problem?
Be interesting to know if there's a stock recovery, and if there is, if it's looking for an update.zip file on a thumb drive in the USB slot. We can tell that USB slot is getting polled at start time by the way that certain connections to it will hang the device.
If it were me, 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.
The idea is that if there's a stock recovery it may be able to see that USB storage and read the OTA file as a recovery source.
roustabout said:
Be interesting to know if there's a stock recovery, and if there is, if it's looking for an update.zip file on a thumb drive in the USB slot. We can tell that USB slot is getting polled at start time by the way that certain connections to it will hang the device.
If it were me, 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.
The idea is that if there's a stock recovery it may be able to see that USB storage and read the OTA file as a recovery source.
Click to expand...
Click to collapse
There might be something to this idea. There was a review posted on Amazon and the reviewer had a Best Buy box that wouldn't go past the Amazon screen. They said Amazon told them how to use the USB to get it to work. A couple people asked for more info but they never responded. I have tried going back through the reviews to see if they ever did, but there are almost 6000 reviews.
kairnage said:
There might be something to this idea. There was a review posted on Amazon and the reviewer had a Best Buy box that wouldn't go past the Amazon screen. They said Amazon told them how to use the USB to get it to work. A couple people asked for more info but they never responded. I have tried going back through the reviews to see if they ever did, but there are almost 6000 reviews.
Click to expand...
Click to collapse
i have only sideloaded a few apps , no root or root attempt was made before issues.
i have a similar boot issue ( stops at amazon first screen and led flashes white) . i believe my remote is fried , batteries heated up while pressing the home button to pair remote , i removed battery and found the plastic wrap on one starting to burn . i believe remote is toast .
can anyone verify that the boot will stop until remote is paired ?
ps : amazon phone help mentioned reset on remote was hold right arrow key ( ie right circle ) and home button for 10 secs , to reset just the remote ,. nothing helped mine , i say its dead. another is on the way ,. he also said the lack of pairing with remote should not have stopped the ftv boot , it should have gone past first amazon screen . other than restarting the ftv by disconnecting power he offered no other reset method .
bkdg100 said:
i have a similar boot issue ( stops at amazon first screen and led flashes white) . i believe my remote is fried , batteries heated up while pressing the home button to pair remote , i removed battery and found the plastic wrap on one starting to burn . i believe remote is toast .
can anyone verify that the boot will stop until remote is paired ?
Click to expand...
Click to collapse
Removed batteries from remote and rebooted FTV, boots like normal, could not find a way to delete a paired remote otherwise I would have tried that too,
userr12 said:
Removed batteries from remote and rebooted FTV, boots like normal, could not find a way to delete a paired remote otherwise I would have tried that too,
Click to expand...
Click to collapse
thanks ,. i called amazon they confirmed normal boot even without pairing ,. also said how to reset "just the remote" ,. right tab and home for 10secs.
kairnage said:
There might be something to this idea. There was a review posted on Amazon and the reviewer had a Best Buy box that wouldn't go past the Amazon screen. They said Amazon told them how to use the USB to get it to work. A couple people asked for more info but they never responded. I have tried going back through the reviews to see if they ever did, but there are almost 6000 reviews.
Click to expand...
Click to collapse
I'm trying to find that review now. so far nothing
fireTVnews.com said:
Do you recall which sqlite editor app you used that caused the problem?
Click to expand...
Click to collapse
I have reviewed the logs of what I did, and it was my fault:
I used a non-root SQLite editor, which means I had to give -rw-rw-rw- access to the database folder and content, which I did.
With the SQLite editor, all I did was to explore the database structure.
Once done, I restored the original permissions, fist -rw------- (chmod 660) on the database folder and database file itself.
Finally I restored read-only -r-------- (chmod 600) to the extra files (settings-*), and that was my mistake: I did not notice my chmod line had 2 entries, with the first one being the database folder (wrong)
If only I would have root write access to the file system with adb, I could easily fix it, with a simple chmod 660 on the database folder.
In hindsight, I was very careless to do that directly on the FireTV; I should have taken a copy of settings.db, and explore it on the PC.
Luxferro said:
I'm trying to find that review now. so far nothing
Click to expand...
Click to collapse
Yeah I took a look again today. Their search doesn't really drill down very well.
Luxferro said:
I'm trying to find that review now. so far nothing
Click to expand...
Click to collapse
kairnage said:
Yeah I took a look again today. Their search doesn't really drill down very well.
Click to expand...
Click to collapse
Here are all the reviews with the word "USB" in them on one page:
http://firetvnews.com/review_usb.html
I skimmed through it but couldn't find the elusive review.
@Firetv: please review post #15 in this thread, and consider adjusting the post on your website accordingly - when I saw your site, it was stating that adjusting values in the settings databases risked changing the permissions on those databases.
That does not appear to be the case, but rather reflected confusion on the part of the person who was doing the settings changes and permissions changes from the shell at the same time.
I haven't seen a db editor that changes the permissions of the dbs themselves....'
Back to softbricked devices: I see that Amazon sells a thing called a "fastboot cable" which in theory forces the Kindle Fires to reboot into fastboot mode if attached to a computer. I'd be interested in what one of these did in conjunction with an A to A converter, since I haven't seen fastboot mode available yet (that I know of)
roustabout said:
@Firetv: please review post #15 in this thread, and consider adjusting the post on your website accordingly - when I saw your site, it was stating that adjusting values in the settings databases risked changing the permissions on those databases.
That does not appear to be the case, but rather reflected confusion on the part of the person who was doing the settings changes and permissions changes from the shell at the same time.
I haven't seen a db editor that changes the permissions of the dbs themselves....'
Back to softbricked devices: I see that Amazon sells a thing called a "fastboot cable" which in theory forces the Kindle Fires to reboot into fastboot mode if attached to a computer. I'd be interested in what one of these did in conjunction with an A to A converter, since I haven't seen fastboot mode available yet (that I know of)
Click to expand...
Click to collapse
I've definitely been tempted to remove the warning about SQLite databases after reading arman68's update. I haven't, however, because I've been individually contact by someone stating they used a free SQLite app from the Google Play store which caused them to lose their ethernet connection and soft-bricked after a restart.
I have gone ahead and updated the post to reduce the concern and stated that the SQLite Editor app everyone is using here seems to be safe.
Also, a fastboot connection can be achieved with any A to A USB cable. You simply need to boot the Fire TV while it's connected to a computer and it will boot into fastboot. I've done this myself with a Mac (have not tried a PC). The Fire TV displays a white Amazon logo on the screen and stays there until you reboot it without the cable plugged in. There doesn't seem to be much that can be done with the locked bootloader, but then again, I'm not the one to know as that is all new territory for me. Got any suggestions on things to try with fastboot?
fireTVnews.com said:
I've definitely been tempted to remove the warning about SQLite databases after reading arman68's update. I haven't, however, because I've been individually contact by someone stating they used a free SQLite app from the Google Play store which caused them to lose their ethernet connection and soft-bricked after a restart.
I have gone ahead and updated the post to reduce the concern and stated that the SQLite Editor app everyone is using here seems to be safe.
Also, a fastboot connection can be achieved with any A to A USB cable. You simply need to boot the Fire TV while it's connected to a computer and it will boot into fastboot. I've done this myself with a Mac (have not tried a PC). The Fire TV displays a white Amazon logo on the screen and stays there until you reboot it without the cable plugged in. There doesn't seem to be much that can be done with the locked bootloader, but then again, I'm not the one to know as that is all new territory for me. Got any suggestions on things to try with fastboot?
Click to expand...
Click to collapse
I didn't mean to say you can't hose your device by changing settings with an editor, just that I don't think any of them change permissions. so using them to look but not change is pretty safe, IMO, and I'd hate to see folks discouraged from doing so.
I'm surprised that there's not a better onboard recovery on this device, or at least not one anyone's figured out how to get moving. I'dthink it'd be cheaper for Amazon if the devices had a viable recovery, or if there was a solid reset to factory which actually did a full reinstall of the OS.
Interesting about the fastboot mode - when i connect the FTV to my laptop using an A to A cable I don't get a device recognized in fastboot, but it may be down to not having a driver for it.
Related
I've been working on this for the past week. Every exploit I've tried just hangs after a while. I've gotten much further manually. I've got unbuntu and been working using various manual methods. The thing I've noticed is that there is no system folder in root. There is a system partition in which app and bin folders exist. Later today I'm going to have time to try some more. If it weren't for these silly rules id reply to somebody elses post, but I guess reading in forums for 3 years as a registered user doesn't count. Never a need to post as I've always found something using a search. And now I've got a phones that's been out for a week and there's no info out on it so I guess I get to develop myself. Not a hard thing...just time consuming and I've got better things to do, but these pink apps gotta go and I need wired or wireless tehter again. Hopefully I have succcess later today and can post how I accomplished it.
I'll be waiting anxiously. please post updates in this thread with your progress!
Any progress on this? I have been attempting but no luck.
update on progress
jb0ne said:
I'll be waiting anxiously. please post updates in this thread with your progress!
Click to expand...
Click to collapse
ok so here's what i've learned so far from trying every method that i can find...
when you boot the phone into the pink screen (volume up and volume down plus power) there is a partition containing 1 folder with 5 files. That folder is called image and the file inside are amss.mbn, boot.img, cust.img, emmcboot.mbn, and recovery.img
The Ascend G300 is a similar phone to the G312 and there is a filed called superrecovery which changes the recovery to set ADB with root priveliges and installs SU in system. If we use the recovery from that batch file made by PauloBrien and push it to the device while in pink screen mode and then reboot into recovery the phone won't power on. You can return to the pink screen and change back to the original recovery, but you can not boot the device into recovery nor regularly. Now this gave me an idea as i'm typing. what if i change it and issue the command in ADB as ADB works during the pink screen. I'm going to try that now.
But this can't be done when in bootloader, only in pinkscreen which makes me think it's fastboot USB mode, but fastboot commands dont work uless you are in the bootloader with the huawei logo which you can only get into by issuing the reboot-bootloader command through adb. once you enter bootloader mode via ADB reboot command then you are able to issue some fastboot commands.
ok so that didn't work...basically when the files in the imge folder are changed the device won't boot into anything but the pink screen mode.
the original recovery file size is 6340KB and the one from PauloBrien is smaller at 5074KB. I'm wondering if file size has something to do with why it won't boot, however, i'm not familiar with what's inside of these files. So...as i reasearch how to build our own clockworkmod recovery i'm wondering if there's a way to change the ADB command inside from not root to root. if it's a on off selecton i'm not sure how i'd affect file size. this is where we get into the realm of knowledge that i don't possess.
so if anybody can offer up some knowledge from where i stand now... please do so.
on a side note, when running exploits, (gingerbreak, zergrush, doomsomething, psneuter, etc)...they all hang.
in linux when trying to drop a file into /system/bin the terminal read out says something about failing to cycle power, not certain what this means.
as i learn a bit more, i'll go ahead and add more...
I am hopeful to hear back from you with a successful root method for this device. I myself just purchased this phone for myself and would really love to see more development on it. Seems like a solid phone with a low entry price. Look forward to seeing what you come up with.
I'm also waiting anxiously for someone to figure this out. I just got this phone and while I really like it, there is just so much packed on this thing that I want to get rid of before I can really enjoy the phone.
I'll be watching this thread as well hopefully OP or someone else will figure out the trick to rooting this phone, like others I have used the usual methods but no luck. I've counted no less than 13 programs I'd uninstall right off the bat.
For what its worth the phone seems to not be considered part of the Ascend models of phones although they are quite similar our model is called the Unite U8680 and the Unite Q U8730 (the slider version). I've sent a email to Huawei lets see if they respond at all.
It's pretty much useless but this is all I can find on the G312 on the Huawei website:
http://www.huaweidevice.com/worldwide/technicaIndex.do?method=gotoProductSupport&productId=4086&tb=0
I'll be watching this thread as well. According to a post on another forum regarding a different Huawei model, dialling *#*# 2846579 #*#* and making some changes in the log file settings suddenly made their phones rootable for some reason. However while the same # gets you into the service mode on this phone, the log file changes made no difference.
I wonder, though, there are quite a few other options in that service mode. Maybe something in there that could be useful.
Edit: There's one menu that looks interesting, the USB one. You can change it to all sorts of modes including "Manufacture mode" whatever that is. Afraid to try it, don't want to brick my wife''s new phone
I've been playing with this menu as well and some of the USB modes do seem interesting. I was hoping this would let me find the product ID for the phone cause I found a link on the Huawei homepage to register to get an unlock code for the boot loader on this phone. If anyone is interested here is a link to the page and sadly the method they say to find the product ID doesn't work on our phone.
http://www.huaweidevice.com/worldwide/servicePolicy.do?method=toApplyUnlock
huawei says the product ID is an 8 digit number. I've been trying to dump the log files so i can scan them for some kind of 8 digit number. i've also tried all the different USB modes as well as a few other changes in the project menu that we're able to access. These haven't given me any success in changing the ownership of the folders needed to gain root access. i've not had any time to tear apart the recovery image to figure out what it's doing. but all in due time somebody will figure this out. still haven't been able to get fastboot to work properly either. am running through the usb modes on that now.
Yes please help i cannot figure out out either
builder.clockworkmod.com
so i've been working on building a recovery image for this devices using koush's site and have been able to build it, but the device won't boot into recovery yet. not sure how to fix this, gonna mess around and keep on trying. i can get it to boot back up and can get it to respond to adb commands when in the mode that just shows the android 4g logo. but i can't get into recovery. not through adb and not through using the power and volume buttons.
still working on it... any body else have anything yet?
No info on rooting this phone but Huawei just posted on their website the open source gingerbread kernel for the G312 U8680 here is a link to it:
http://www.huaweidevice.com/worldwi...=toDownloadFile&flay=software&softid=NDY3MzU=
It's been rooted!
Yep, it's a simple one too. Happy to have my wife's phone rooted Removing bloat, however, is tricky -- it's hidden in an inaccessible partition and when you erase it, it restores it on next reboot.
http://forum.xda-developers.com/showthread.php?p=31237225#post31237225
http://www.droidrzr.com/index.php/topic/4276-how-to-root-huawei-mytouch-4g/
Big thanks to mattlgroff for cracking this nut!
jb0ne said:
Yep, it's a simple one too. Happy to have my wife's phone rooted Removing bloat, however, is tricky -- it's hidden in an inaccessible partition and when you erase it, it restores it on next reboot.
http://forum.xda-developers.com/showthread.php?p=31237225#post31237225
http://www.droidrzr.com/index.php/topic/4276-how-to-root-huawei-mytouch-4g/
Big thanks to mattlgroff for cracking this nut!
Click to expand...
Click to collapse
When you install an update to one of these apps lets use the, yahoo mail on for example, it will show in the /system/app or /data/app. The problem is the apk before the update is in /cust/t-mobile/us/app which is read only and unable to be mounted as R/W and that is why Titanium backup is unable to uninstall it.
I have tried moving it and deleting it manually with no luck. I have not tried through ADB yet but may give that a try next.
jamonthis said:
When you install an update to one of these apps lets use the, yahoo mail on for example, it will show in the /system/app or /data/app. The problem is the apk before the update is in /cust/t-mobile/us/app which is read only and unable to be mounted as R/W and that is why Titanium backup is unable to uninstall it.
I have tried moving it and deleting it manually with no luck. I have not tried through ADB yet but may give that a try next.
Click to expand...
Click to collapse
If you figure it out and find anything out I would love to know about it. Where should I watch for an update in case someone does get that sorted out?
Recovery mode
There is an accessible recovery mode, at least on my querty version of the phone. You have to completely pull the battery first. Put the battery back in, hold Volume up, and then hit power. I held the power button for a couple seconds, and volume up for maybe 6-8 seconds, then started hitting volume up repeatedly. The key is to pull the battery each time you try, I think. It looks like powering off from the phone's power menu just puts it in a suspend sort of mode. (Compare boot times when rebooting, and when pulling battery)
Apparently the bootloader is locked, so not sure how useful it is yet.
For anyone with a T-Mobile MyTouch Q (Huawei U8730), I created a wiki page for it, and we should post in the New Device Forum Requests thread so we have a specific place to post info.
I just purchased a U8730 today and will definitely be figuring out how to root it at some point.
For anyone that cares here's a link in case you haven't registered at the other site.
http://j.gs/1U5q
I'm hoping we can get some development going for this phone. I just picked one up for my daughter a month ago and it's giving her memory filled messages already. It'd be great if we can get it permanently rooted and remove bloat to start... then possibly move onto Cyanogen... considering she had the horrible Comet (also by Huawei) previously and it had development for CM7. I may be taking a leap from my contract soon, but can't go to Straight Talk with her phone unless it's unlocked
I have a Kindle Fire that is stock and was NEVER rooted. It was being used and the user said it told them that the space was getting full. He began to remove apps in order to free up space (he's a novice user) and as he was doing this it rebooted and is now stuck in a boot loop. It will flash the kindle fire logo for a few seconds, screen goes black, etc.
I was able to get it connected and accept adb commands. I first was able to reboot it (./adb reboot) and then see it listed as a device (./adb devices). However, it still wouldn't boot up all the way. I've rooted a number of devices before and work with computers for a living so I'm pretty familiar with what's going on, however I know that every device is different. I looked into the different things to do with a Kindle Fire and decided I should try to push the fbmode app to the kindle. When I tried that I got an error saying:
failed to copy 'fbmode' to '/data/local/temp': No space left on device
Any idea what I should do? I don't really want to root the device if I can just get it to run first. What is the best way to free up some storage so that it might boot again?
UPDATE: I've sent the wipe_data and wipe_cache commands to the KF. The screen kinda turns yellow for a second and then reboots and goes back into a boot loop. I can't seem to find another way to clean up space. Help?
Same here
I'm having the same problem. Did you ever find a solutions?
dawn12123 said:
I'm having the same problem. Did you ever find a solutions?
Click to expand...
Click to collapse
No. I'm still searching or hoping someone else might have an answer.
carlowahlstedt said:
No. I'm still searching or hoping someone else might have an answer.
Click to expand...
Click to collapse
I started a new thread about it. Here is the link:http://forum.xda-developers.com/showthread.php?p=40509965#post40509965
arestspubs
Thanks! Looks like you might be getting somewhere. I'll be anxious to see what you figure out.
Connect it to computer and navigate to Android/data/com.amazon.venezia/cache and delete the entire folder.
This took about 3.51 GB of the Kindle's 4.99 GB of Space!When clearing up after receiving a low storage notification, i saw that the Android folder had over 3 GB so i decided to see if i could clean anything over there.Once I saw that this had 3.51 GB in a cache folder,I googled com.amazon.venezia to see if i could delete it and this post was the first link.:good:Thanks this really helped me a lot and i have no idea why amazon follows this method
I need to come up with the best way to control recovery for the FireTV Stick. Right now, I'm leaning towards requiring USB ADB and having people use the mouse emulator. And then the bootmenu would not auto boot and you would need to manually select what to boot every time. Unless someone else has any better ideas?
rbox said:
I need to come up with the best way to control recovery for the FireTV Stick. Right now, I'm leaning towards requiring USB ADB and having people use the mouse emulator. And then the bootmenu would not auto boot and you would need to manually select what to boot every time. Unless someone else has any better ideas?
Click to expand...
Click to collapse
Would you not be able to make it boot normally like it auto loads on the aftv2 but instead of saying select left to boot normal or right for recovery you could say you have 6 seconds to use a certain adb command to enter recovery? (But not in those words HAHA) maybe auto display the ip address of the stick on-screen at the same time at the top of the screen?) I don't know if this is possible or not but just helping with sum ideas? Good luck mate
deanr1977 said:
Would you not be able to make it boot normally like it auto loads on the aftv2 but instead of saying select left to boot normal or right for recovery you could say you have 6 seconds to use a certain adb command to enter recovery? (But not in those words HAHA) maybe auto display the ip address of the stick on-screen at the same time at the top of the screen?) I don't know if this is possible or not but just helping with sum ideas? Good luck mate
Click to expand...
Click to collapse
I guess I could autoboot after some long delay, I don't think 6 seconds is enough, something like 10 or 15 would probably work. It would have to be USB ADB, and not network ADB, because getting wifi to work is a little tricky. I looked into it when I was working on the FireTV2 stuff, and wound up shelving the idea.
So I found some information for setting up an ad-hoc wifi network, so I'll look into if that can be used for easier wifi...
rbox said:
I guess I could autoboot after some long delay, I don't think 6 seconds is enough, something like 10 or 15 would probably work. It would have to be USB ADB, and not network ADB, because getting wifi to work is a little tricky. I looked into it when I was working on the FireTV2 stuff, and wound up shelving the idea.
Click to expand...
Click to collapse
Sounds ok though, for a working recovery I'm sure most users wouldnt mind waiting a few more seconds so if something goes wrong It can be undone/saved via a backup
---------- Post added at 01:36 AM ---------- Previous post was at 01:31 AM ----------
rbox said:
So I found some information for setting up an ad-hoc wifi network, so I'll look into if that can be used for easier wifi...
Click to expand...
Click to collapse
You know best mate
Is there any way to see if it got stuck or didn't boot last time, and then boot to recovery once after that? like a file that gets touched early in boot and then deleted later? not sure if that really would make sense, but an auto recovery on failed boot would be pretty awesome. maybe ANY adb input on boot at all, counts as boot recovery so it can be faster? 1,
enter or something?
Any way to just detect if a pc is connected via adb and if so, then boot recovery?
Not sure if these will be useful, but wanted to share the ideas that came to my mind. I definitely would like it to standard boot to OS if possible though.
edit: actually if a-a cable was used on original fire tv didn't it auto go to fastboot?
ImCoKeMaN said:
Is there any way to see if it got stuck or didn't boot last time, and then boot to recovery once after that? like a file that gets touched early in boot and then deleted later? not sure if that really would make sense, but an auto recovery on failed boot would be pretty awesome. maybe ANY adb input on boot at all, counts as boot recovery so it can be faster? 1,
enter or something?
Any way to just detect if a pc is connected via adb and if so, then boot recovery?
Not sure if these will be useful, but wanted to share the ideas that came to my mind. I definitely would like it to standard boot to OS if possible though.
edit: actually if a-a cable was used on original fire tv didn't it auto go to fastboot?
Click to expand...
Click to collapse
So I can't figure out what happened the previous boot. Would need to modify the kernel for that. So I can detect if you're plugged in to the wall versus plugged in to a computer. But I think some people plug theirs into the tv usb port, and it would probably detect that the same as the computer. So maybe if it's wall, always boot straight, and if it's not plugged in to the wall, it's either plugged in to a tv or a computer, then it will show the bootmenu. You'll have I don't know, 10 or 20 seconds to adb shell in and run a command that will boot to recovery, otherwise it'll boot normally.
I was playing around with adhoc wifi, and I coudln't seem to get anything to work. Once I get recovery starting I may play around with it some more. The good news is I'm like 95% done for FireTV1... I think I figured out all the way I can possibly brick the stick, so I can avoid doing it. Haha. That was one of the reasons I wanted to get the FireTV1 working first. Because FireTV1 and FireTV2 I have ways to recover, the stick if anything goes wrong it's pretty much a lost cause.
Unfortunately, I'm not going to be able to work on much in a few days, for a while, so it'll probably be 2 weeks before I can release something for FireTV1 and really get stuff going for the Stick.
If I remember correctly one or more android devices I have seen would auto boot recovery if device failed to boot a certain number of times. A delay at boot could be as long as you wanted since its not like people reboot the device often. Another though is if the stick can detect the difference between a reboot and a power-on, maybe the delay could be different between them. If I wanted to reboot to recovery there are apps that can do that, so delay for a reboot could be shorter than one for power-on.
highspeedfelon said:
If I remember correctly one or more android devices I have seen would auto boot recovery if device failed to boot a certain number of times. A delay at boot could be as long as you wanted since its not like people reboot the device often. Another though is if the stick can detect the difference between a reboot and a power-on, maybe the delay could be different between them. If I wanted to reboot to recovery there are apps that can do that, so delay for a reboot could be shorter than one for power-on.
Click to expand...
Click to collapse
Thanks. I'll play around with some of these ideas too.
The PC with dual operating systems come to mind. Where 1 OS is set as default and you have 30 seconds (default time, but adjustable) to choose the 2nd OS. If no choice is made it boots to the default.
2WhlWzrd said:
The PC with dual operating systems come to mind. Where 1 OS is set as default and you have 30 seconds (default time, but adjustable) to choose the 2nd OS. If no choice is made it boots to the default.
Click to expand...
Click to collapse
That's how it works, the problem is how to make the selection. On FireTV1 and 2 it's with a keyboard. But you can't do that for the stick.
Use the power cycle as the trigger. The bootloader should have a time window (6 seconds) where a file (/cache/boot_recovery) is written to flash and removed after the time window has closed. If someone power cycles the device during this window, the file remains and can be checked during start up and evaluated.
For example.
0s Booting up.
0.1s checking file which indicates recovery in (/cache/boot_recovery) -> none found
1s Show begin of recovery time window -> touch /cache/boot_recovery -> countdown 6 seconds
2s user power cycle
0s Booting up.
0.1s checking file which indicates recovery in (/cache/boot_recovery) -> found
0.2s booting recovery
0s Booting up.
0.1s checking file which indicates recovery in (/cache/boot_recovery) -> none found
1s Show begin of recovery time window -> touch /cache/boot_recovery -> countdown 6 seconds
7s rm /cache/boot_recovery
7.2 booting normal image
malfino said:
Use the power cycle as the trigger. The bootloader should have a time window (6 seconds) where a file (/cache/boot_recovery) is written to flash and removed after the time window has closed. If someone power cycles the device during this window, the file remains and can be checked during start up and evaluated.
For example.
0s Booting up.
0.1s checking file which indicates recovery in (/cache/boot_recovery) -> none found
1s Show begin of recovery time window -> touch /cache/boot_recovery -> countdown 6 seconds
2s user power cycle
0s Booting up.
0.1s checking file which indicates recovery in (/cache/boot_recovery) -> found
0.2s booting recovery
0s Booting up.
0.1s checking file which indicates recovery in (/cache/boot_recovery) -> none found
1s Show begin of recovery time window -> touch /cache/boot_recovery -> countdown 6 seconds
7s rm /cache/boot_recovery
7.2 booting normal image
Click to expand...
Click to collapse
Interesting... very brute forcy, but it could work.
...in Addition, one could think of a small little app called reboot to recovery, that does nothing more than writing that little file to cache and reboot?
Edit: and thank you so much rbox for your efforts! Im on aftv1 and completely rely on your magic thanks mate!
dafunkydan said:
...in Addition, one could think of a small little app called reboot to recovery, that does nothing more than writing that little file to cache and reboot?
Edit: and thank you so much rbox for your efforts! Im on aftv1 and completely rely on your magic thanks mate!
Click to expand...
Click to collapse
That would be a great idea, maybe put the apk as a systems app so it can't be deleted by mistake would also be a good move
Sent from my SM-G900F using Tapatalk
OK. So time for some good news. I figured out how to get wifi going on the FireTV2. So using the same method, I'm pretty sure I'll be able to get it going on the Fire Stick. If it all works out, you won't need USB to control it. In other news, I think I've figured out how the wifi remote works, and I think I may be able to make it work in recovery too. I won't hold up the FireTV 1 recovery for it, so I'll release that as is without wifi and without the remote working, and then as I'm working on recovery for the Stick, I'll get wifi and remote working for everything. I had some issues with the FireTV1, so I don't know if I'll be able to get wifi working for it.
Hmm will the new WiFi remote be a requirement? I have the original with the bt remote. I did like that timing method as an option though as I plan to have stick to travel and not have otg most of the time so slightly faster default boot would be nice.
ImCoKeMaN said:
Hmm will the new WiFi remote be a requirement? I have the original with the bt remote. I did like that timing method as an option though as I plan to have stick to travel and not have otg most of the time so slightly faster default boot would be nice.
Click to expand...
Click to collapse
No. There will be a few options.
ImCoKeMaN said:
Hmm will the new WiFi remote be a requirement? I have the original with the bt remote. I did like that timing method as an option though as I plan to have stick to travel and not have otg most of the time so slightly faster default boot would be nice.
Click to expand...
Click to collapse
I think by wifi remote he means the app for android not another device. If you havent tried the app its pretty handy.
highspeedfelon said:
I think by wifi remote he means the app for android not another device. If you havent tried the app its pretty handy.
Click to expand...
Click to collapse
No, I mean the physical "Voice Remote" that uses Wifi Direct. I think the android app probably uses a complicated Amazon protocol that requires more than I can throw at it in recovery.
Nexus 7 (2013) multiple "Unfortunately..." after motherboard swap / image reflash
Hello all - I'm hoping someone can provide some assistance / suggestions...
A few months ago, my son's tablet went for a quick swim (dropped into the toilet ) Unfortunately, I wasn't at home (on a business trip) to immediately power it down and pull the battery. I'm not sure if it was turned off / back on / off again or what, but it was quickly put into a bag of rice to try and minimize the damage until I came home to review.
Inspection of the tablet confirmed it was dead - no response to either buttons or plugging in the charger. Found the ifixit how-to, and after obtaining some tools I popped the back case off to see what was what. Disassembly revealed an nice scorch mark on the underside of the motherboard, right where the main chip was, so it was pretty obvious what the failure was.
I decided that I'd give repairing it a go, and bought a replacement motherboard from ebay a couple of weeks ago. Swapping the board over was no problem, and I was happy to see that after letting it charge fully, it booted up and went into the 'Setup' routine.
However, this is where the problems started - as it was working through the setup (language / wifi / copy apps/data from other device etc) there were numerous "Unfortunately, xxx has stopped" messages. I kept 'ok'ing them, and the tablet made it to the point where it was starting to download the saved apps etc from the playstore before it rebooted.
When it powered back up, the 'Unfortunately" pop ups were worse than before, so after doing some searching I decided to try flash a factory image (razor-mob30x) , as per the link on the Nexus help forum. The flash seemed to work (no errors in fastboot mode, laptop was communicating with the tablet) but the pop ups were still as plentiful as before. I have tried the flash multiple times, even going back to lollipop, but with no real improvement. The last thing I tried tonight was to start the recommended flash process from step 1, re-downloading and installing all the required programs, but without success.
I'm not sure what else to try, as the factory image reflash should erase all the installed files.
My only thought is maybe trying to sideload the correct gapps / play services / etc in fastboot mode?
Any suggestions appreciated,
Roadie73
Update..
So, because I'm a glutton for punishment, I've been playing with the N7 again this evening...
Grabbed my old laptop, and went through the complete routine again - loading adb and fastboot onto the laptop, then the N7 factory image - and ended up with basically the same result - the tablet will look like the files have taken, but almost immediately after restarting and loading to the blue set up screen, the "Unfortunately..." messages start again.
I was able to get all the way through the set up, and have it copy and start to download the files off the tablet I was using previously, but the pop ups persisted, and it gets to a point where it is looking for a google play services update, and the process comes to a screeching halt.
I found another 'How To" and tried sideloading a rescue OTA update, which might be a little better, but the messages persist....
I'm almost wondering if it's worth reflashing the factory image back to whatever the N7 shipped with, and then trying updates from there, as it seems to be the play services / store / apps that is the issue.
The other strange thing is that when I sign in with my google account, it shows as a Nexus 7 2012, even though it's a 2013 - might the original software on the replacement motherboard have been corrupt?
Still trying...
Roadie73 said:
it shows as a Nexus 7 2012, even though it's a 2013 - might the original software on the replacement motherboard have been corrupt?
Click to expand...
Click to collapse
Interesting, please post the output of the 2 commands...
boot the Nexus in fastboot mode (when off press power+vol.dn)
connect it to your PC
on PC run:
fastboot getvar all
fastboot oem gpt-info
If you can, also attach logs...
download get-logs.zip to a FAT32 flash drive
connect the flash drive to your N7 with OTG adapter
download TWRP to your folder with fastboot and adb apps
boot the Nexus in fastboot mode (when off press power+vol.dn)
on PC run: fastboot boot twrp-3.1.0-0-flo.img
when TWRP is up, go: install/select-storage/usb-otg/get-logs.zip/flash
logs.tgz will be saved on the flash drive
attach logs.tgz here
It's simpler if you have TWRP already installed. You can also use get-logs.zip from internal storage.
Hi k23m,
I ran the two commands you suggested (getvar all and oem gpt-info) , and grabbed the outputs of both as screen captures and dumped them into a ppt file (which I can't seem to attach - there is no 'manage attachments' option I can see )
I installed TWRP on the N7, but was unsuccessful in creating / grabbing logs.tgz file - which might have to do with the USB connector on the N7 being flaky - if the otg cable wasn't held in exactly the right way it wouldn't recognize the flash drive.
If I can figure out how to add the attachment I will in a separate post, or I can always email it to you direct.
Thanks,
Roadie
Hello k23m,
Finally ad a couple of minutes to play with the N7 again - copied the get-logs file over to the tablet (that was behaving for once).
Unfortunately, despite copying the file off the N7 onto the laptop, a *.tgz file can't be attached. So I did the next best thing and copied the screen caps into an excel doc, which is one of the valid extension.
Please see the attached file - I had a look at the output, but it means nothing to me...
Thanks,
Roadie
added 'logs.tgz' file run previously - please rename from *.xls
Hopefully it might provide some insights into why the N7 is mis-behaving.
Thanks,
Roadie
The logs are OK.
Roadie73 said:
when I sign in with my google account, it shows as a Nexus 7 2012, even though it's a 2013
Click to expand...
Click to collapse
If you have followed the factory image installation instructions and you see the error messages before setup's initial sign in, then your hardware is faulty.
If it happens after sign in, then perhaps Google has corrupt account data ("it shows as a Nexus 7 2012"). Try a new account. Try a custom ROM with Gapps.
Ok, thanks.
Just tried a factory reflash as per the link, but fastbooted the individual files (boot / recovery / system / userdata / cache) separately as from what I have read using the 'flash-all' batch file has intermittent results.
Looked like the files loaded in successfully, but I'm still getting the "Unfortunately.." messages popping up on the initial sign in screen for set-up
So, based on k23m's assessment above, it sounds like it's a hardware problem
As far as I know the touch screen is ok (it's responsive in all areas, as far as I can tell). The daughterboard is not the original (that took a swim) - it was swapped out of another N7 when the charging port started to spread (and that tablet was issue free) So it looks as if the issue is in the replacement motherboard.
I guess I could try removing and reinstalling it, on the off chance it's a flaky connection somewhere.
I will also check to see if there was any sort of gaurentee / replacement policy for the replacement mobo, but it sounds like I'm out of luck
Any other suggestions / checks I can perform to see if I can narrow down where the issue lies?
Thank you,
Roadie
Until yesterday I had a functional FTV stick, now paperweight.
I installed an application for watching TV. The application installed ok but, when launched, told me it needs the Google Play services.
So I went and installed the Google Play services, which also installed ok.
I relaunched the application, which this time just froze, and I could not back out of it. So I rebooted the FTV, with the result that now it starts booting, gets to the white Amazon logo with music and from there it boots again, and again in an infinite loop.
I tried powering it from an external supply - no change. I tried the Right button/Back button remote combination - no change. I did NOT unlock the bootloader (did not expect such a problem and was not aware that it is doable); I do not have ADB enabled.
I read that there is a way to unbrick using a USB keyboard combination but I only have one micro-USB port on the stick which is used for power supply, so I don't see how I can connect a keyboard.
Any suggestions how to proceed from here will be most welcome. Thanks in advance.
Hi there,
Same happened to me. I received a brand new 4k Stick.. it worked like a charm for 20 min, I installed a few thing, and then when I rebooted it started the loop with the amazon logo. 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?
Thanks!!
ddoouubbllee said:
Hi there,
Same happened to me. I received a brand new 4k Stick.. it worked like a charm for 20 min, I installed a few thing, and then when I rebooted it started the loop with the amazon logo. 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?
Thanks!!
Click to expand...
Click to collapse
I contacted Amazon customer support (via online chat) and told them the story. In spite of me not being able to offer any proof of purchase (all went to the bin as the FTV worked so well - until it didn't anymore) they offered me the choice between a 40% discount on a new unit, or a free replacement they could only ship to an US address. As I live in Europe I don't have such an address BUT - I found a company that will receive a shipment on my behalf at an US address and will forward it to my European address for the shipping cost plus a small fee. So I chose this option and I just got an email that the replacement was shipped to the US address.
So, bottom line, I will end up with a new unit (which first thing I will open up all the possible ways - unlock bootloader, enable ADB etc.) and, if ever I will succeed to salvage the old one, I will have a spare for free
Anyway, kudos to Amazon for a great customer support experience.
avidav said:
I contacted Amazon customer support (via online chat) and told them the story. In spite of me not being able to offer any proof of purchase (all went to the bin as the FTV worked so well - until it didn't anymore) they offered me the choice between a 40% discount on a new unit, or a free replacement they could only ship to an US address. As I live in Europe I don't have such an address BUT - I found a company that will receive a shipment on my behalf at an US address and will forward it to my European address for the shipping cost plus a small fee. So I chose this option and I just got an email that the replacement was shipped to the US address.
So, bottom line, I will end up with a new unit (which first thing I will open up all the possible ways - unlock bootloader, enable ADB etc.) and, if ever I will succeed to salvage the old one, I will have a spare for free
Anyway, kudos to Amazon for a great customer support experience.
Click to expand...
Click to collapse
Lucky you; i live in Chile and they dont want to send me anything. I need to fix the unit I have..
If anybody can help me ill be very gratefull!
Same with me, and i have fix as below video, please find fix description, i hope also you will fix it.
https://youtu.be/R7EA_VLDxZ4
erolmutlu said:
Same with me, and i have fix as below video, please find fix description, i hope also you will fix it.
https://youtu.be/R7EA_VLDxZ4
Click to expand...
Click to collapse
Does not work. ADB does not find any device attached.
Does anyone have any news on how to solve the problem? please help
avidav said:
Does not work. ADB does not find any device attached.
Click to expand...
Click to collapse
hi! I have tried to adb link my fire stick when I got the stick from amazon,but failed.Tried thousands times,then I found something that may help:
Unplug the usb port from the amazon charger,plug it directly into the usb hole on PC.
Open the adb window on PC,may be at this time the adb can find the device.
Maybe you could use the adb on PC connect another android phone at first,if it succeed so you will know the adb software on PC is all right.
I found there is something wrong with the last version of the adb software:"the port missing.....".You may try an old version of adb.
Good Luck!
I've tried USB Keyboard <ALT> + <Print> + <i> , also + <Shift> and + <Ctrl>, several combinations / orders.
Seems not to work anymore - keeps looping
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.
I have to admin that patient i the best way to solve that problem.
It helped me also. I wait for about 24h and it boot up to system and now i'm restored it to default and all works fine
abdel85 said:
I have to admin that patient i the best way to solve that problem.
It helped me also. I wait for about 24h and it boot up to system and now i'm restored it to default and all works fine
Click to expand...
Click to collapse
Did you keep your TV POWER ON during the bootloop process?
Fell into it and fixed it twice
Hey guys , I had this problem twice already because of trying to install google services on it and i was searching for hours and hours and i came to this thread and i had no choice but try the solution offered by @iwl in the first time ,because i had never authorised any computer to connect to this stick before, i didnt even knew about it, so i left the FireStick 4K connected to TV and its adapter normally and let it loop as much as it wanted, i actually went to bed and on the next day it was back on, i did a mistake a didnt reset it immediately so later on i had another half a day of bootlooping and when it was up again after a few hours i reset it and of course all apps were lost , not a big deal as long as my FS is back to life.
Now is the nice part that made any bootloop later on a piece of cake, i went immediately and connected the stick to to Minimal ADB via WIFI so i could authorise the computer to connect to it( it is a one time thing, there are some videos about how to do that from which i also learnt the method).
The second time i was prepared so i took the risk and wanted to install Play services in order to get some other app work and not for the sake of google, so i fell into the loop, disconnected the Stick from TV and connected it with the USB cable only to my computer which i authorised before on this specific stick, ran Minimal ADB and fastboot and ran the following commands in the shell (use commands between the " ")
"adb kill-server"
"adb start-server"
to make sure that i am connected to the stick "adb devices"
-you will get list of connected devices
Then unistall the nasty app , in my case it was google so it used these commands
"adb uninstall com.google.android.gms"
in case you have a problem with another app , you could check the app's name with the following command "adb shell pm list packages -f"
find it's and use it the abovementioned uninstall command.
Then in the end , disconnect the device properly with "adb disconnect" and then "adb kill-server"
Voila , back on , all apps were there and only the nasty app was gone
I hope i could be helpful to someone
Mine over 24 hrs still in bootloop. I hope you're telling the truth.
Thank you, I fixed my bootloop with this method.
For me the TV USB 1A didn't work (1st day) and the PC USB also didn't work (2nd day) , only when I plugged it to an USB (2A? 2.5A?) direct to a power outlet that it got able to boot after 8 hours.
Use the included USB Power Adapter and Cable. Especially many other USB Cables are weak and can't transport 1 Amp.
PC USB 2.0 provides only 0,5 Amps, 3.0 0,7 (or 0,8?) Amps but not 1.
Tried to repair it, but nothing helps. Anybody could check, which app could cause bootloop?
package:com.android.cts.priv.ctsshim
package:com.amazon.net.smartconnect
package:com.amazon.tv.resolutioncycler
package:com.google.android.athome.globalkeyinterceptor
package:com.amazon.recess
package:com.amazon.platform.fdrw
package:com.amazon.ssmsys
package:com.android.providers.calendar
package:com.amazon.tv.ime
package:com.amazon.whisperplay.contracts
package:com.android.providers.media
package:com.amazon.device.rdmapplication
package:com.amazon.dcp.contracts.library
package:com.android.wallpapercropper
package:com.amazon.metrics.api
package:com.amazon.vizzini
package:com.amazon.tv.devicecontrolsettings
package:com.amazon.bueller.notification
package:com.amazon.connectivitycontroller
package:com.ivona.orchestrator
package:com.amazon.device.sync
package:amazon.fireos
package:com.amazon.device.logmanager
package:com.android.documentsui
package:com.android.externalstorage
package:com.android.htmlviewer
package:com.amazon.ceviche
package:com.amazon.alta.h2clientservice
package:com.amazon.advertisingidsettings
package:com.android.providers.downloads
package:com.amazon.tv.parentalcontrols
package:com.android.providers.tv
package:com.amazon.whisperjoin.provisioner.middleware.controller
package:com.amazon.ftv.glorialist
package:com.amazon.dp.logger
package:com.amazon.ods.kindleconnect
package:com.android.defcontainer
package:com.android.providers.downloads.ui
package:com.android.pacprocessor
package:com.amazon.tv.intentsupport
package:com.amazon.sharingservice.android.client.proxy
package:com.amazon.webview
package:com.amazon.android.marketplace
package:com.android.certinstaller
package:com.android.carrierconfig
package:com.amazon.device.backup.sdk.internal.library
package:android
package:com.amazon.tifobserver
package:com.amazon.dialservice
package:com.amazon.client.metrics.api
package:com.amazon.aca
package:com.amazon.cpl
package:com.amazon.dcp
package:com.amazon.imp
package:com.amazon.ssm
package:com.amazon.sync.service
package:com.amazon.fireinputdevices
package:com.amazon.whisperjoin.provisioner.middleware.firetv
package:com.android.backupconfirm
package:com.amazon.logan
package:com.amazon.tahoe
package:com.amazon.tcomm
package:com.android.statementservice
package:com.amazon.naatyam
package:com.amazon.storm.lightning.tutorial
package:com.amazon.identity.auth.device.authorization
package:com.amazon.kindle.cms
package:com.android.providers.settings
package:com.amazon.kindleautomatictimezone
package:com.android.sharedstoragebackup
package:com.amazon.uxcontrollerservice
package:com.android.printspooler
package:com.fireos.arcus.proxy
package:com.amazon.tv.fw.metrics
package:com.android.dreams.basic
package:com.amazon.device.backup
package:com.amazon.firehomestarter
package:com.amazon.securitysyncclient
package:com.amazon.unifiedshare.actionchooser
package:com.amazon.firerestapiframework
package:com.amazon.tv.routing
package:com.amazon.device.messaging
package:com.amazon.device.bluetoothkeymaplib
package:com.amazon.device.metrics
package:com.amazon.device.messaging.sdk.internal.library
package:com.amazon.providers
package:com.amazon.tv.devicecontrol
package:com.amazon.tv.ottssocompanionapp
package:android.ext.shared
package:com.android.onetimeinitializer
package:com.android.keychain
package:com.amazon.device.sale.service
package:com.amazon.cardinal
package:android.ext.services
package:com.android.packageinstaller
package:com.svox.pico
package:com.amazon.tcomm.client
package:com.amazon.tv.forcedotaupdater.v2
package:com.amazon.client.metrics
package:com.amazon.device.settings.sdk.internal.library
package:com.android.proxyhandler
package:com.amazon.autopairservice
package:amazon.jackson19
package:com.android.managedprovisioning
package:com.amazon.tmm.tutorial
package:com.mediatek.atci.service
package:com.amazon.device.software.ota
package:com.amazon.wifilocker
package:com.amazon.dcp.contracts.framework.library
package:com.amazon.device.bluetoothdfu
package:com.amazon.storm.lightning.services
package:com.amazon.whisperlink.core.android
package:com.amazon.device.messaging.sdk.library
package:com.amazon.tv.notificationcenter
package:com.amazon.tv.support
package:com.amazon.tv.nimh
package:com.amazon.tv.oobe
package:com.amazon.sync.provider.ipc
package:com.amazon.tv.legal.notices
package:com.android.settings
package:com.amazon.tv.settings.core
package:com.amazon.firebat
package:android.amazon.perm
package:com.android.cts.ctsshim
package:com.amazon.tv.keypolicymanager
package:com.amazon.android.service.networkmonitor
package:com.amazon.providers.contentsupport
package:com.amazon.avl.ftv
package:com.android.vpndialogs
package:com.amazon.awvflingreceiver
package:com.amazon.device.crashmanager
package:com.amazon.application.compatibility.enforcer
package:com.amazon.whisperplay.service.install
package:com.ivona.tts.oem
package:com.android.shell
package:com.android.wallpaperbackup
package:com.amazon.uxnotification
package:com.android.providers.userdictionary
package:com.amazon.cast.sink
package:com.amazon.device.software.ota.override
package:com.android.location.fused
package:com.android.systemui
package:com.amazon.alexashopping
package:com.amazon.franktvinput
package:com.android.bluetoothmidiservice
package:com.amazon.aria
package:com.amazon.avod
package:com.amazon.communication.discovery
package:com.amazon.alexa.externalmediaplayer.fireos
package:com.amazon.tv.releasenotes
package:com.amazon.ssdpservice
package:com.amazon.device.settings
package:com.amazon.tv.livetv
package:com.amazon.device.sync.sdk.internal
package:com.amazon.connectivitydiag
package:com.android.bluetooth
package:com.amazon.device.lowstoragemanager
package:com.android.providers.contacts
package:com.amazon.providers.tv
package:com.amazon.webview.chromium
package:com.amazon.bueller.music
package:com.amazon.hedwig
package:com.amazon.kindle.devicecontrols
package:com.amazon.application.compatibility.enforcer.sdk.library
Problem solved!
What worked for me?
adb shell pm list packages -f
Then copy output to notepad and uninstall all listed apps. Every single one. After this fire tv restarted few times and i have it working again.
Took some time do do it, but it is working now.
I have waited for 5 days without success, but this worked.
Firestick 4k Boot loop issue solved using Y-OTG cable
Hello, I had the same problem. I did not have my fire stick 4k connected to my laptop adb before I installed Google play so I could not uninstall play store and play services using adb. I came across this link and followed exactly what mentioned, It let me boot in to safe mode then I uninstalled play store and play services then did a normal boot. It works well now. (This url is non-English so allow google translate to English)
I got y-otg cable from Amazon, I Kept holding ctrl+alt+menu+printscreen keys while another person assisted to plug in the fire stick power adapter. I kept hitting the "i" key. It started the regular white screen with orange amazon logo after few moments darkscreen+safemode in left bottom appeared then I got my screen. clicked "your applications" and uninstalled both culprits then power off and power on.
(Both blue tooth and usb key board supports to invoke the safe mode)
(add https www to the url)
android-hilfe.de/forum/amazon-fire-tv-stick.2146/google-apps-bootloop-praevention-und-infos-fuer-den-ernstfall-fire-tv-4k.918292.html
How to unbrick or factory reset...
avidav said:
Until yesterday I had a functional FTV stick, now paperweight.
I installed an application for watching TV. The application installed ok but, when launched, told me it needs the Google Play services.
So I went and installed the Google Play services, which also installed ok.
I relaunched the application, which this time just froze, and I could not back out of it. So I rebooted the FTV, with the result that now it starts booting, gets to the white Amazon logo with music and from there it boots again, and again in an infinite loop.
I tried powering it from an external supply - no change. I tried the Right button/Back button remote combination - no change. I did NOT unlock the bootloader (did not expect such a problem and was not aware that it is doable); I do not have ADB enabled.
I read that there is a way to unbrick using a USB keyboard combination but I only have one micro-USB port on the stick which is used for power supply, so I don't see how I can connect a keyboard.
Any suggestions how to proceed from here will be most welcome. Thanks in advance.
Click to expand...
Click to collapse
....
To unbrick or factory reset it, you will need an OTG cable with charger and USB conector to connect an logitech keyboard or another multimedia keyboard.
Then with the fire tv turning on ( in loop status ), push at the same time ( ctrl+alt+del ) and when it restart push ( FN key+ Option key -square with lines ) over and over again, until it enter in SAFE MODE. Then, go to my fire tv and push factory reset. ... Good luck. ( if you request the video i going to upload soon in youtube).