Related
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.
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.
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).
Hi all!
Some days ago I urooted my TV android tv box with superSU and then I restarted it. From that moment when I plug the device it only reach the T9 logo (not the android one) and don't go further.
I've tried different ways to try to unstuck it, but nothing has worked.
I tried:
- enter recovery boot by holding the button in the av hole -> nothing happens
- install new firmware with adb sideload with both ubuntu and windows 10 -> always get errors (often error: closed, sometime other errors that at the moment don't remember)
- install new firmware with sd card using SDCard Installer -> the device doesn't boot when the sd is inserted
Moreover, with adb in ubuntu sometimes it recognises the device and I can enter the adb shell (but obtain errors when try any tipe of command), and sometimes don't (after adb devices I see list of attached devices: ??????????????? offline)
Now I'm thinking to try to install an ubuntu like on an usb pendrive...
I will be very grateful of any help/suggestion to how to revive my device :fingers-crossed:
Thank you!!!
Does this happen to be a pendoo model? I have a pendoo x10 MAX and i actually simply just installed supersu while it was rooted. Since then, I haven't gotten this thing to boot. Just stays on the boot screen the entire way. I wiped in recovery, knew that'd do nothing. I just wanted a root MANAGER. I tried Magisk, my favorite.. no go.. so then I went a bit old school.. so I tried ChainFire's SuperSU.. and THAT updated the SU binary! It said it succeeded.. it asked to do recovery install or normal install.. on phones, I've always done normal.. so I chose normal. Plus.. this thing has no custom recovery. I found it on Amazon. Overpriced, but great with the controller it had. It looks like I'll need a replacement and maybe a request to ask this guy if he could possibly NOT use something like KingRoot/KingoRoot/AmaraRoot or ANY One click root tool.. they just cause more bloatware, inciting boot issues and problems within the Android box itself. These One Click Root tools are out of control. It's to the point where I need to find a way in to adb and find the firmware for the latest version of this thing... X10Max from Pendoo.. I have not found a thing anywhere regarding firmware, and their website is ****. NOTHING *anywhere* on these things.. hell I'm about to return it as I bought it for $72. I have another one, same model.. wondering if the root method was different. About to boot that up and find out. I'll even swap the board. At this point.. he rooted it.. the WRONG way.. you can MOUNT THE /SYSTEM PARTITION IN RECOVERY. THIS IS ANDROID 9 we're talking about--the recovery supported by API v3.
This can and should have a TWRP custom recovery. If none exists, don't bother. As long as you can mount /system then you have a chance, at least, to root the damn thing.. which is why I'm still messing with it. I have another two weeks to return it. I'll give it another couple of days before I call it off and just switch out the good board for the bad one, return it, then return the other one and just use it until I find a way to use a custom recovery on this thing. There has to be.. unless there is no firmware available in sight (for an RK3318 or 3328, can't tell.. recovery mode says 3328, model name says RK3318. I see no difference at the moment aside from processor naming at this point--maybe speed?)
I'm still a nub with Android TV boxes so don't hold it against me for updating the damn root binary. If I could find a way to just reinstall the entire firmware and delete all previous stuff, I would. It would be worth it to learn. I would then mount /system in recovery and soldier on.
One little issue with this thing.. there's only one USB port that actually works. Same applies for the same exact product, a replication of the same thing.. was a "replacement" that still have/has the same qualities.
I've ranted enough. I vote more research into RK33xx processors and possible custom recoveries. I'm about to look for it based on only the device itself.
Note: Been stuck at boot screen ever since the binary was updated. I felt it was necessary to have a boot manager. I don't know where to even find the firmware. Can.. anyone point me in any direction? Something that MIGHT work on this thing? Android 6 or 7 would even suffice, return or no return, as "stuck on boot screen" will be my complaint. That's.. the actual complaint. I can't just *flash it* like the old days.. and maybe the original Android 9.0 firmware would suffice.. I don't know, but Pendoo.. wouldn't that be preferred?
You will need an SDcard to recover this box. I think the T9 32GB 4GB rom will do the job since its a cut down version.
Make a update SDcard and pop it in and power on the box. It will start the recovery on its own.
hello, sorry for my English I live in France I would have a question about the box: TV T9 RK3318, 4gb / 64gb. the problem is that the time is desynchronized on restart and creates problems to connect to applications when the time is out of order, I tried everything changed the time zone to deactivate and entered the time Manual it goes out of order all the time . is there a custom version or a version 10?
Very cook did I checked this out awhile back alot of good information that's for your contribution
So I bought a new phone since my old Onyx (One+ X) died (cracked screen and charging port is getting iffy). And finally I decided on this one, a cheap Chinese docomo branded one off Ebay.
I was so exited when it arrived, the UPS truck was at my gate when I got home that day, ready to leave, but the driver was nice enough to wait and give me my package then and there. Pheew.
Well, now to my, bootloader unlocking, recovery flashing, after market os installation and rooting story...
Bootloader:
The phone was supposed to be unlocked, and I guess that only meant SIM unlocked, because the service menu read "Bootloader unlock allowed: no". Damn.
A few Duckduckgo searches later, turned up I needed the "S!Unlock tool" which I found a copy off online, but username/password fields needed to be filled in, and I think I found a pirated s/n which didn't seem to work, (might have if I had tried harder).
But since it was just over £22 at https://networkunlocking.com/ I thought I could spare that on the off chance it worked. I was very surprised when it finally did, truth, I needed a few tries. And it actually did turn that service menu's pesky "no" to a thumbs-up "yes". Yay!
So now, pulling the cable, holding "volume up" and inserting cable for that blue light goodness, and running the "flashtool.exe -i 0x???? oem unlock bootloader 0x????????????" comand.
Not so fast, that doesnät work with newer flashtool versions...
Finding the old one from my Xperia Arc days and runnning it again, Yay!
(Wish I had read ahead and done that temporary root trick to rip my DRM codes off my phone first. But I don't plan to revert to stock, and I gather (might be wrong) that the DRM is only needed for stock roms, and not Lineage OS and such.)
Recovery (TWRP):
Now the problems start for real, getting into recovery was a **** and a half. Most guides for the phone says to push "volume up" multiple times during the boot-process. This turns out to be plain wrong. The actual button combo is holding "volume down" and "power" button together atleast until the screen goes blank after the unlocked bootloader warning.
Now, I wanted 17.1 on the phone and the recommended TWRp is 3.1.1 or something, and this works to install lineage fine, but don't forget to erase /data partition as I did. Stupid mistake that made wifi fail miserably, and probably a lot of other stuff, that I never tried before noticing my mistake.
However trying to get my own set of ringtones on the phone turned out to be another issue, going back into recovery when I noticed my ringtone.zip had failed. Obviously the media folder had moved since los 15.1,so no wonder right? Turns out it wasn't the only problem. TWRP 3.1.1 (or something) failed to unencrypt the root partition, so changing anything via recovery was a lie. fortunately the latest recovery, 3.5.2_9 did. So after installing that everything was rosy peaches.
Rooting:
SuperSU? forget it.
Magisk? yeah, but how? No really good step by step guide out there, except download from the github page, but what version?
A little trial and error, tried with the arm64 version and it turned out to be the right one. (Sometimes you just get it right on the first try...)
Renamed the apk to .zip put it on the phones memory, entered recovery and installed the zip, et voi effing la, Magisk root installed.
Root checker verifies root status, TitaniumBackup and RootExplorer works. Yes, my phone is playing ball.
Final notes:
This above looks simple right? In fact this was a two day process since the guides are surely lacking for this phone, a lot of trial and error, the greatesthurdle was getting into Recovery, until I found the right button combo I accidently managed to enter it once making me believe I had the right combo and something was wrong with the phone. 4 hours or so wasted trying different versions rebooting and flashing. Getting back my Viber messages turned out to be a problem to, TitaniumBackup got the messages back, but the db had references to my old images on my old phone, and probable pointed at the wrong directory so trying to send images either from gallery or take new photos crashed the app. Solution, backup the messages to my google account, uninstall and reinstall viber and restore from that backup. TitaniumBAckup is good but no magic bullet, it's a ***** that we have to rely on Google for backups though, I am allergic to the cloud, something about it makes my skin crawl.
Otherwise I like the phone, it says docomo on the back, something I can live with. The Chinese vendor even supplied one glass screen protector for the phone and a clear soft plastic case, in case I wanted some extra protection. I only wish there was a screen protector that had the same surface as the one that was on the phone in the box, that slightly opaque cloudy feel was so nice on my finger.
Can I recommend this phone? Nah, if noone writes a step by step guide that will cut down the time I spent on making this phone palpatable, I can't. But if you, like me, don't mind to tinker and don't want a phablet or spend way too much for the privilege to get a screen size you don't want, then sure. But why do we have to get them from China?
My trusty xz1 compact is slowly dieing on me and i am looking for a replacement how much did you pay for yours and is a really new or just refurbished ?
"Final notes:
This above looks simple right? In fact this was a two day process since the guides are surely lacking for this phone, a lot of trial and error, the greatesthurdle was getting into Recovery, until I found the right button combo I accidently managed to enter it once making me believe I had the right combo and something was wrong with the phone"
This Phone is in the mobile Sphere already ancient. Don't expect to get any help here or newer hot to guides.
my biggest problem is the fastboot recognition of my Windows. If this would work reliable i could better flash the phone but getting the right driver is a kind of roulette for this phone.
muhschaf said:
my biggest problem is the fastboot recognition of my Windows. If this would work reliable i could better flash the phone but getting the right driver is a kind of roulette for this phone.
Click to expand...
Click to collapse
Also had a non-connecting fastboot issue on Windows until I ran into this guide showing me it was not about a driver but an installation method:
How to install Sony Xperia Drivers Manually (Super Easy Guide)
Step-by-Step guidelines to install Sony Xperia Drivers Manually (this method can be used on Windows XP, Vista, Windows 7, Windows 8, 8.1 and Windows 10).
xperiausbdriver.com
4qx said:
Also had a non-connecting fastboot issue on Windows until I ran into this guide showing me it was not about a driver but an installation method:
How to install Sony Xperia Drivers Manually (Super Easy Guide)
Step-by-Step guidelines to install Sony Xperia Drivers Manually (this method can be used on Windows XP, Vista, Windows 7, Windows 8, 8.1 and Windows 10).
xperiausbdriver.com
Click to expand...
Click to collapse
Handy cannot boot now anyway so i would probably not able to recover anyway.
muhschaf said:
cannot boot now anyway so i would probably not able to recover anyway.
Click to expand...
Click to collapse
The phone completely refuses to boot?
Do you have recovery installed? If not, are you able to install it via fastboot on linux?
4qx said:
The phone completely refuses to boot?
Do you have recovery installed? If not, are you able to install it via fastboot on linux?
Click to expand...
Click to collapse
okay i will explain.
i had this common issue with this running out of internal space (13GB pictures i could not find, only 300MB left) and after looking into it i figured, that, due to my constant app installing and deinstalling, i had literrally thousends of little images (thumbnails, icons, you name it) that got not deintalled for whatever reason and clogged up my internal memory. So i made a Backup and decided to completly wipe and flash the newest lilac from Modpunk (18.1) and did a big Mistake here. i go into recovery and wiped EVERYTHING...without checking that recovery is untouched. then during the same session i installed the ROM and rebooted...so far all nice and dandy. Setting up the Phone, then get the newsest Gapps and then try to reboot into recovery to install them...well did i mentioned that i had wiped EVERYTHING? Well, there was no recovery anymore. Not my first rodeo i headbutt myself into the desk and spun up ADB/fastboot...only to run into the same problem i run everytime due to improper intalled driver i forgot already about. Longs story short: after some time handy refused to boot also into system.
Phone is now unbootable into any state, but Black screen fastboot over hardware buttons...
i COULD still try to make a blind fastboot flash after following the driver install instruction from above, but consider my lucky or clumsyness i will **** this up too and only waste time. and due to my current covid recovery i have not the energy nor the patient to diddle around with this sorry excuse of an absolute restrictive Phone and rather get me a S5 mini or something else that has no bootlock whatsoever and let you flash it from the very start.
i am plain running out of patient with sonys harassment.
/€: Also the constant "cannot get root" on a rooted phone is plain BS³. having permanent trouble to install adaway or use my sdcard proper is so friggin annoying that i now will search for a android version that got rid of this bull**** and will buy any phone that is suported by that ROM.
It is MY phone, and not Goolge nor the the phone company will dictade what i can or cannot install on it. i decide and i carry the risk, period. and the biggest security reason holds the phone anyway.
@muhschaf okay so it doesn't seem bricked. Pretty sure you just need to flash the recovery through fastboot and flash a ROM. Try that on Windows with the driver method; if that fails boot a Linux distro e.g. EndeavourOS, even from a USB without installing no adb/fastboot driver is necessary for Linux, it just works. You can do it.
4qx said:
@muhschaf okay so it doesn't seem bricked. Pretty sure you just need to flash the recovery through fastboot and flash a ROM. Try that on Windows with the driver method; if that fails boot a Linux distro e.g. EndeavourOS, even from a USB without installing no adb/fastboot driver is necessary for Linux, it just works. You can do it.
Click to expand...
Click to collapse
i known, the question is more "i really want that?" like i said i struggle with this phone ever since. and i realized yesterday the problem is not the phone itself, it's the bull**** of androids security architecture. Google seems to be very prone to make sure that they can shove any amount of advertisements down your throat. Given that they earn their money with ad network it doesn't surprise me.
i came to the conclusion that in reality i want to have a reliable way to install ad away on any given phone i own. i archive similar things on my desktop with Firefox and umatrix and ublock. And what can is say: Having Advertisment fee Internet is a bliss and i not care a bit about "but the free stuff" and i incrisingly fury about my inability to archive similar things on my phone i rely quite a bit.
@muhschaf I get it but you know what they say: good things require effort. But I find that once I set my Android up, I'm happy to have done it.
In regards to ads, you can actually install uBO on Android Firefox now, and many other addons also.
So i gave it a try again and the result was that it detects now a "?" under fastboot but ADB can't see anything failing sucsequently to flash recovery. i am also seemingly unable to get even into hardware fastboot anymore. But could be quite possible that the battery is already drained again. so i recharge it the night.
4qx: i was going away from uBO several years ago. Wonder that he has survived the drain after his "whitelist" decision, but it seems like.
Adaway block advertisement in apps and this is mainly the feature i wanted, see advertisment have gotten out of the browser itself into the Base/apps systems (Android, Windows) and therefore the Adblocker have to go with it. under windows i can control the System itself pretty easy and throughoutly with Powershell and package debloating scripts or regedit. under Android i haven't this option and have to rely on app like adaway. This shortcoming is pretty frustraing for an "Open Source" OS
After nearly a Year i stumble upon something windows related and now i have finally my xz1c back:
Windows USB Hubs of ANY kind (Monitor USB Hubs, Powers external USB Hubs, hell sometimes even the PCH, that is technical also a USB Hub), can and sometime WILL prevent proper lowlevel access to devices like...USB Headsets (Logitech Pro X) and Mobile Phones in fastboot mode (xz1c).
To circumvent this you have to connect the phone to a USB Port on the Back of your PC Motherboard DIRECTLY. every other Port can have an USB Hub in between that alters your write or readout and therefore failed the flashing.