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.
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
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.
The display stopped responding to touch out of the blue. I want to access my data urgently. I'll just explain the situation point by point.
1. This happened about 3 months back. There were posts on the forum saying that it might be because the software has damaged the hardware on the screen in some way (i wouldn't know, i'm a novice when it comes to this)
2. USB debugging is turned off. So i can't access ADB
3. OTG is on timeout. It has to be turned back on again to use a mouse over OTG
4. Bluespark TWRP 3.2.something is installed but since the device is encrypted it asks for the password, which i can't insert.
5. Fastboot works
What can i do to get my stuff back? is there any solution to this besides replacing the screen? Because i can't afford to do that right now.
use a mouse and connect it via otg extension. unlock it with pattern it and enable usb debugging
MuminMohamed said:
use a mouse and connect it via otg extension. unlock it with pattern it and enable usb debugging
Click to expand...
Click to collapse
As i said in the description OTG is on a 30 minute time out. It turns off automatically after 30 minutes of inactivity. So i can't connect a mouse.
Helhound0 said:
As i said in the description OTG is on a 30 minute time out. It turns off automatically after 30 minutes of inactivity. So i can't connect a mouse.
Click to expand...
Click to collapse
I don't think there's a way to recover your data without OTG/ADB available, fastboot alone doesn't offer a solution either, only way I could think of is to fastboot flash another ROM (well you can't really flash whole ROMs but only boot.img,system.img, etc.) without the OTG restrictions or maybe even have ADB enabled by default (I think I saw such thing before on custom ROMs), this would however lead you to a total trail 'n error kind of situation were you potentially could lose all data too (in best case you could access /sdcard but definitely would lose everything not on the internal storage).
All this is very experimental and probably sheer luck if you ever succeed, so it's probably best to wait until you can replace the screen as there's no real good solution to the problem with the given possibilities...
Sent from my OnePlus5T using XDA Labs
If you reboot the phone does the OTG timeout reset?
Essentially, you need to get past the security gate to decrypt your data because even if you could get it off without decrypting it, it would be useless to you.
You're absolutely going to need to be able to enter your PIN somehow to proceed.
Pro Tip: always leave adb debugging enabled.
Sam Nakamura said:
I don't think there's a way to recover your data without OTG/ADB available, fastboot alone doesn't offer a solution either, only way I could think of is to fastboot flash another ROM (well you can't really flash whole ROMs but only boot.img,system.img, etc.) without the OTG restrictions or maybe even have ADB enabled by default (I think I saw such thing before on custom ROMs), this would however lead you to a total trail 'n error kind of situation were you potentially could lose all data too (in best case you could access /sdcard but definitely would lose everything not on the internal storage).
All this is very experimental and probably sheer luck if you ever succeed, so it's probably best to wait until you can replace the screen as there's no real good solution to the problem with the given possibilities...
Sent from my OnePlus5T using XDA Labs
Click to expand...
Click to collapse
I was thinking about that too, though i haven't found a ROM with ADB or OTG enabled by default. I'm pretty sure that can be done. Where do i find one?
djmcnz said:
If you reboot the phone does the OTG timeout reset?
Essentially, you need to get past the security gate to decrypt your data because even if you could get it off without decrypting it, it would be useless to you.
You're absolutely going to need to be able to enter your PIN somehow to proceed.
Pro Tip: always leave adb debugging enabled.
Click to expand...
Click to collapse
Yeah... and have OTG on all the time maybe. I learned a lot because of this.
Hi,
I'm wanting to try Lineage OS on this device, to see if I can get the default (or change) media player to play LATM AAC.
Anyway's, I've flashed a few phones in my time, so easy I thought.
However, I 'cannot' get this thing into TWRP.
I've enabled USB debugging, and can reboot the device into 'bootloader'....
It's unlocked and when I issue the 'fastboot flash recovery twrp-........img it appears to go ok.
But I cannot get the device into the GUI for twrp.
The best I've been able to do, is to get the device into some other sort of recovery mode.
It doesn't go straight into it, instead goes into the droid robot, flat on his back, tummy open and underneath 'no command'.
By fluke, I can press every key on the controller and eventually I enter a 'text based', which has options for adb and usb uploading etc, but any attempts to install from this fail.
Someone 'please' put me out of my misery and tell me where I'm going wrong.
This overpriced junk is doing my suede in now.
Thanks
Neil
Not any help but just because you can't make it do something it is not intended to do doesn't make it "over priced junk"
Huawei P30 Pro (VOG-L29) using Tapatalk
Yea, perhaps my statement is a 'little' rash, but its annoying how a premium product cannot play AAC_LATM using the native media player, when cheaper Xiaomi units can.
And yes, I've contacted Nvidia about this and they think I should contact Freeview UK and ask them to change their encoding profiles.
If you're wondering, 'native' decoding is required for google live channels to be able to play 'said' streams
i have not used twrp on the shield in years, but instead of flashing twrp, have you tried just booting to it?
fastboot boot recovery twrp-xxxx.img
also, my shield tv was always a little finicky on which usb port i used on my computer, so try different ones. original cable is only one that works for me as well.
skiv71 said:
Hi,
I'm wanting to try Lineage OS on this device, to see if I can get the default (or change) media player to play LATM AAC.
Anyway's, I've flashed a few phones in my time, so easy I thought.
However, I 'cannot' get this thing into TWRP.
I've enabled USB debugging, and can reboot the device into 'bootloader'....
It's unlocked and when I issue the 'fastboot flash recovery twrp-........img it appears to go ok.
But I cannot get the device into the GUI for twrp.
The best I've been able to do, is to get the device into some other sort of recovery mode.
It doesn't go straight into it, instead goes into the droid robot, flat on his back, tummy open and underneath 'no command'.
By fluke, I can press every key on the controller and eventually I enter a 'text based', which has options for adb and usb uploading etc, but any attempts to install from this fail.
Someone 'please' put me out of my misery and tell me where I'm going wrong.
This overpriced junk is doing my suede in now.
Thanks
Neil
Click to expand...
Click to collapse
Better to fastboot twrp not flash it on the shield, also twrp will not show up on a 4k tv this is a limitation of twrp on the shield. I personally stopped using twrp after software version 6 of the shield, just too many headaches and I just use adb
I have 2 firestick 4ks.
Both identical in that they are rooted and debloated with (the same) various system apps frozen...
Both been running fine for a month or so...
Where I live I get frequent power cuts.
Yesterday after a power cut... one reboots correctly the other just goes to a black screen.
I connected it to my PC and ADB into it, I reenabled all apps via adb and rebooted, it just went to the same black screen.
So I booted to TWRP and reflashed RBoxes prerooted image, still nothing...
I then installed a stock image (Skel40's).... Still nothing.
Up to this point I had only been wiping Cache & Dalvik and dirty flashing.
I figured that there was a corrupted file that was affecting full boot, so I made the mistake of wiping data and installing stock again...
When I rebooted I had lost ADB!
I could still see the firestick in windows, however it just comes up as "Fire" in device manager with no ADB..
I grabbed an OTG cable and booted to TWRP and tried a few more times... each time gave exactly the same black screen (no orange amazon logo).
Finally I tried wiping system as well in case something was corrupted and reflashed stock.... Still nothing!
So I don't really know where to go from here... (I'm going to backup the other firestick and restore that over this one then reflash stock and see where that gets me...)
Does anyone have any ideas! I can get into TWRP, but I'm not sure it's wiping or flashing things correctly...
Any help greatly appreciated... Thx
Have you done any of the ideas listed in the other thread? Let me know if i can help #lockdown
Michajin said:
Have you done any of the ideas listed in the other thread? Let me know if i can help #lockdown
Click to expand...
Click to collapse
Hi Michajin...
Thanks for taking the time to help
I'll fill you in as to what I have and haven't tried...
I have wiped all standard partitions ( cache, dalvik, data, system) and reflashed both rooted and stock images *.*.6.8 and *.*.7.1
I think I may have wiped the Vendor partition, I'm not sure.
Under backup in TWRP I can see the Vendor partition, however under Wipe I see an extra 2 partitions (both) called storage and having not made a backup (I know!... )
I did'nt realise that the storage partition(s) may have been the Vendor partition.
After wiping cache, dalvik, data, system partitions and then flashing stock and rooted images multiple times and still getting a black screen... I tried wiping the one storage then the other and then finally Internal.
A couple of points that I can tell you...
I can boot to TWRP
I can reboot to hacked Bootloader
When I connect the firestick to my windows PC It's senses it straight away for a bout 10 seconds then drops it... It then senses it again and stays connected to my PC.
Windows recognizes it under portable devices as simply "fire" and an empty explorer window pops up, if I right click on the firestick in windows explorer (it shows as drive) I can pull a properties page which shows its serial number...!
On both my firesticks I have modified my build.prop for a faster boot which doesn't show the splash screen.
Both sticks were modified identically about a month ago and once setup had nothing added to them. They just get used for Kodi and catch-up TV apps.
I root them so as to boot directly into Kodi and freeze the bloat.
Both sticks have been rebooted multiple times.. This one failed after a powercut...
I been reading in the main rooting thread and have come across something about sticks not booting properly due to dm_verity failing and having to flash magisk before (or after... I'm not sure) the image flash.
I'm still reading through the thread so haven't tried anything yet... When i get head round what it is, I'll try.
The other 2 ideas I thought to try was to
1) flash an image directly from the bootloader (if possible.. I need to find more info on this) and
2) taking a backup of the working stick and trying that (It's in use a lot... due to #TotalLockdown! we're at 4 weeks with heavy police curfew! So I haven't had access to it)
If have any ideas or thoughts... I would be very grateful. Also I'm happy to try anything...
tinybilbo said:
Hi Michajin...
Thanks for taking the time to help
I'll fill you in as to what I have and haven't tried...
I have wiped all standard partitions ( cache, dalvik, data, system) and reflashed both rooted and stock images *.*.6.8 and *.*.7.1
I think I may have wiped the Vendor partition, I'm not sure.
Under backup in TWRP I can see the Vendor partition, however under Wipe I see an extra 2 partitions (both) called storage and having not made a backup (I know!... )
I did'nt realise that the storage partition(s) may have been the Vendor partition.
After wiping cache, dalvik, data, system partitions and then flashing stock and rooted images multiple times and still getting a black screen... I tried wiping the one storage then the other and then finally Internal.
A couple of points that I can tell you...
I can boot to TWRP
I can reboot to hacked Bootloader
When I connect the firestick to my windows PC It's senses it straight away for a bout 10 seconds then drops it... It then senses it again and stays connected to my PC.
Windows recognizes it under portable devices as simply "fire" and an empty explorer window pops up, if I right click on the firestick in windows explorer (it shows as drive) I can pull a properties page which shows its serial number...!
On both my firesticks I have modified my build.prop for a faster boot which doesn't show the splash screen.
Both sticks were modified identically about a month ago and once setup had nothing added to them. They just get used for Kodi and catch-up TV apps.
I root them so as to boot directly into Kodi and freeze the bloat.
Both sticks have been rebooted multiple times.. This one failed after a powercut...
I been reading in the main rooting thread and have come across something about sticks not booting properly due to dm_verity failing and having to flash magisk before (or after... I'm not sure) the image flash.
I'm still reading through the thread so haven't tried anything yet... When i get head round what it is, I'll try.
The other 2 ideas I thought to try was to
1) flash an image directly from the bootloader (if possible.. I need to find more info on this) and
2) taking a backup of the working stick and trying that (It's in use a lot... due to #TotalLockdown! we're at 4 weeks with heavy police curfew! So I haven't had access to it)
If have any ideas or thoughts... I would be very grateful. Also I'm happy to try anything...
Click to expand...
Click to collapse
It's really strange. Usually these steps should fix the issue :
1) Factory Reset from TWRP
2)Wipe System from TWRP
3) Flash full stock (non rooted) firmware
Of course, you could try flashing each image with hacked fastboot, or just boot, system and vendor with TWRP, which also have an option (install image) for that.
But you will have to convert system and vendor from sparse (.dat) to . img before being able to flash them.
Wiping these should have taken care of you issue.
"After wiping cache, dalvik, data, system partitions and then flashing stock and rooted images multiple times and still getting a black screen... I tried wiping the one storage then the other and then finally Internal."
What stock did you flash from where?
When you flash stock are there any errors?
You should be able to take a backup from you other one also for other one (if you are doing a full backup/restore, i would wipe data and cache after restore)
Thanks guys for the replies, I couldn't respond earlier due to an 8 hr powercut today!
Pretoriano80 said:
It's really strange. Usually these steps should fix the issue :
1) Factory Reset from TWRP
2)Wipe System from TWRP
3) Flash full stock (non rooted) firmware
Of course, you could try flashing each image with hacked fastboot, or just boot, system and vendor with TWRP, which also have an option (install image) for that.
But you will have to convert system and vendor from sparse (.dat) to . img before being able to flash them.
Click to expand...
Click to collapse
Hi Pretoriano80
Yeah... It's really weird... I'm starting to think that the stick is damaged in some way, although the fact I can get in both the hacked bootloader and TWRP confuses me!
I've even wiped each partition 3 or 4 times (and rebooted back into recovery to remount) before writing the new image just to make sure.!
I'm ready to try anything at this point, since the stick is a brick at this point.
I'm not really sure how or what to flash from the bootloader, I'll read up a bit before I try especially your tips about converting from sparse to .img.
(I may have some further questions for you, if that's alright )
I will try to restore a backup from another stick first (if I can get access to that stick for long enough...)
Michajin said:
Wiping these should have taken care of you issue.
"After wiping cache, dalvik, data, system partitions and then flashing stock and rooted images multiple times and still getting a black screen... I tried wiping the one storage then the other and then finally Internal."
What stock did you flash from where?
When you flash stock are there any errors?
You should be able to take a backup from you other one also for other one (if you are doing a full backup/restore, i would wipe data and cache after restore)
Click to expand...
Click to collapse
Hi Michajin
Thanks again for taking the time to reply... much appreciated...
I have tried this stock image update-kindle-mantis-NS6271_user_2493_0003590962564
https://forum.xda-developers.com/fire-tv/general/official-stock-image-fire-tv-stick-4k-6-t4059777
as well as a update-kindle-mantis-NS6268_user_2315_0003255372676 image (stock that I think i got from the main rooting thread)
I've also used Rboxes pre-rooted image mantis-6.2.6.8-rooted_r1
which was the image that worked fine on both boxes...
I'm happy to try any other image that you might have a link for.....
When I wipe the partitions there are no errors, except for when I wiped the storage partitions - they did throw up an error - although at this point I had already tried flashing new images at least a dozen times,
All the images flash without error as well!
I'm stumped... I've never had any android device brick before... (soft bricks many times! but never a hard brick), and it's weird since I have access to both the bootloader and TWRP.
Tomorrow I'll be able to get a restore image from the other stick, Then I'll try flashing from bootloader..
The only other thing i thought to try was to crack the case open and redo the the whole root procedure from scratch...
Sorry to double-post...
However I wanted to add this as a separate post rather than an edit.
After playing with my firestick for a few days, during which I tried a working backup and erasing from the bootloader and then restoring multiple images (stock and prerooted), as well running the exploit again.
I realised that the OS was loading (I regained ADB after the full restore) despite not giving an image over HDMI (just a black screen).
I was about to give up when I happened to be going through the options in ADBLink and I found the screenshot button.
I gave it a try and to my surprise it sent back an image of the stick with a working OS/screen.
I even manged to navigate through the settings and do a full reset from within FireOS by taking screengrabs.
After the reset it still gave a black screen, I re-enabled ADB from TWRP and was able to verify that it had reset correctly...
From ADB I ran a logcat...
I'm not really familiar with logcat but a couple of things seemed to jump out...
Code:
1) 596 617 I DisplayManagerService: Display device changed: DisplayDeviceInfo{"Built-in Screen": uniqueId="local:0", 720 x 480, modeId 4, defaultModeId 1, supportedModes [{id=1, width=1920, height=1080, fps=60.000004}, {id=2, width=1920, height=1080, fps=59.94}, {id=3, width=720, height=576, fps=50.0}, {id=4, width=720, height=480, fps=60.000004}], colorMode 0, supportedColorModes [0], HdrCapabilities [email protected], density 320, 213.0 x 216.0 dpi, appVsyncOff 1000000, presDeadline 16666666, touch INTERNAL, rotation 0, type BUILT_IN, state ON, FLAG_DEFAULT_DISPLAY, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
2) 1145 1145 I AmazonHdmiServiceManager: resolution applied and hdmi turned off
3) 596 2438 E AmazonHdmiService: Settings client binder died.
Seeing that there were some issues with the HDMI display (Display device change to built-In screen? and HDMI turned off?), I used the screengrab to navigate my way to display settings which wouldn't allow me to change resolution
So to sum it up...
Everything is loading and running correctly, however I can't get an image over HDMI only by getting screengrabs via ADBlink.
Maybe something on the chip (HDMI output) is damaged, I've had the stick for a while and it's had heavy usage, or something has stuck in a toggled state.
I don't know....
If anyone has any ideas how to test it I have full root access via TWRP and probably can get it over ADB, so any help or commands to try would greatly appreciated....
Thanks :good:
tinybilbo said:
Sorry to double-post...
However I wanted to add this as a separate post rather than an edit.
After playing with my firestick for a few days, during which I tried a working backup and erasing from the bootloader and then restoring multiple images (stock and prerooted), as well running the exploit again.
I realised that the OS was loading (I regained ADB after the full restore) despite not giving an image over HDMI (just a black screen).
I was about to give up when I happened to be going through the options in ADBLink and I found the screenshot button.
I gave it a try and to my surprise it sent back an image of the stick with a working OS/screen.
I even manged to navigate through the settings and do a full reset from within FireOS by taking screengrabs.
After the reset it still gave a black screen, I re-enabled ADB from TWRP and was able to verify that it had reset correctly...
From ADB I ran a logcat...
I'm not really familiar with logcat but a couple of things seemed to jump out...
Code:
1) 596 617 I DisplayManagerService: Display device changed: DisplayDeviceInfo{"Built-in Screen": uniqueId="local:0", 720 x 480, modeId 4, defaultModeId 1, supportedModes [{id=1, width=1920, height=1080, fps=60.000004}, {id=2, width=1920, height=1080, fps=59.94}, {id=3, width=720, height=576, fps=50.0}, {id=4, width=720, height=480, fps=60.000004}], colorMode 0, supportedColorModes [0], HdrCapabilities [email protected], density 320, 213.0 x 216.0 dpi, appVsyncOff 1000000, presDeadline 16666666, touch INTERNAL, rotation 0, type BUILT_IN, state ON, FLAG_DEFAULT_DISPLAY, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
2) 1145 1145 I AmazonHdmiServiceManager: resolution applied and hdmi turned off
3) 596 2438 E AmazonHdmiService: Settings client binder died.
Seeing that there were some issues with the HDMI display (Display device change to built-In screen? and HDMI turned off?), I used the screengrab to navigate my way to display settings which wouldn't allow me to change resolution
So to sum it up...
Everything is loading and running correctly, however I can't get an image over HDMI only by getting screengrabs via ADBlink.
Maybe something on the chip (HDMI output) is damaged, I've had the stick for a while and it's had heavy usage, or something has stuck in a toggled state.
I don't know....
If anyone has any ideas how to test it I have full root access via TWRP and probably can get it over ADB, so any help or commands to try would greatly appreciated....
Thanks :good:
Click to expand...
Click to collapse
Just checking, but have you tried another HDMI cable and different TV? Somehow it is not recognizing the format in the OS. TWRP uses a lower format i believe. I have had a power surge before damaging HDMI here, but I wouldn't get anything with it plugged in.
Michajin said:
Just checking, but have you tried another HDMI cable and different TV? Somehow it is not recognizing the format in the OS. TWRP uses a lower format i believe. I have had a power surge before damaging HDMI here, but I wouldn't get anything with it plugged in.
Click to expand...
Click to collapse
Hi Michajin,
Thanks for your reply...
Yes I have tried multiple TV's, Monitors , and cables... Including the TV that it had been running on for almost a year...
I get frequent powercuts where I live, and often power surges when the power comes back on...
I do use surge protectors, however they don't always work....
One time the electricity board double one of the phases to 440v and knocked out £5k worth of equipment!
So between that and the humidity I think there is some minor damage to the stick... shame because it's still running.
I'm going to see if I can get a logcat from TWRP and see what it says about the HDMI output, not that it'll help...
tinybilbo said:
Hi Michajin,
Thanks for your reply...
Yes I have tried multiple TV's, Monitors , and cables... Including the TV that it had been running on for almost a year...
I get frequent powercuts where I live, and often power surges when the power comes back on...
I do use surge protectors, however they don't always work....
One time the electricity board double one of the phases to 440v and knocked out £5k worth of equipment!
So between that and the humidity I think there is some minor damage to the stick... shame because it's still running.
I'm going to see if I can get a logcat from TWRP and see what it says about the HDMI output, not that it'll help...
Click to expand...
Click to collapse
So you get a display in TWRP, but go black after booting? I wonder if you can force whatever display mode and setting as used in TWRP as your display mode in FireOS. Had you tried another wall outlet (higher mA) ? A long shot at this point that you havent tried it....
Michajin said:
So you get a display in TWRP, but go black after booting? I wonder if you can force whatever display mode and setting as used in TWRP as your display mode in FireOS. Had you tried another wall outlet (higher mA) ? A long shot at this point that you havent tried it....
Click to expand...
Click to collapse
Correct, I can get a display with TWRP, but it goes black when it boots into FireOS (from which I can get screengrab via adblink of the stick displaying FireOS or whatever app is running).
Up until now (for almost a year) I've just used the power adapter that came with the stick, but it's a good idea to try something more powerful (I have a 2.4a one that I'll try a little later).
Another thing I'm going to try is "adb shell wm size ***x***" "adb shell wm density ***" command to change the resolution & pixel density (I think).
I hadn't thought about power being an issue up until you mentioned it (because so far it hasn't been), but maybe a component has (or is) failed (or failing) so it might need more power...
I can't try until a little later this evening, but at least I have something to try now cheers! I'll let you know how I get on....
tinybilbo said:
Correct, I can get a display with TWRP, but it goes black when it boots into FireOS (from which I can get screengrab via adblink of the stick displaying FireOS or whatever app is running).
Up until now (for almost a year) I've just used the power adapter that came with the stick, but it's a good idea to try something more powerful (I have a 2.4a one that I'll try a little later).
Another thing I'm going to try is "adb shell wm size ***x***" "adb shell wm density ***" command to change the resolution & pixel density (I think).
I hadn't thought about power being an issue up until you mentioned it (because so far it hasn't been), but maybe a component has (or is) failed (or failing) so it might need more power...
I can't try until a little later this evening, but at least I have something to try now cheers! I'll let you know how I get on....
Click to expand...
Click to collapse
Hey I have a debloated clean stable rom that will be available soon. You can try that and you need to be sure to have either a usb otg or a hub for transferring this backup which will be titled ftvs4kdebloatedv1.0. Paste this folder to TWRP/BACKUPS/YOUR SERIAL #/ftvs4kdebloatedv1.0.
Skel40 said:
Hey I have a debloated clean stable rom that will be available soon. You can try that and you need to be sure to have either a usb otg or a hub for transferring this backup which will be titled ftvs4kdebloatedv1.0. Paste this folder to TWRP/BACKUPS/YOUR SERIAL #/ftvs4kdebloatedv1.0.
Click to expand...
Click to collapse
Thanks Skel40
I'll definitely give the clean rom a go
I have an OTG & Hub and the serial number already
hi guys
i have a firestick 2th gen model ly78pr its brick stock on logo , the problem is usb debbug was off and i tried with the key board and otg cable pressing alt + printscreen + i and it does not work as , i tried different combination and nothing help , also i connected to the pc and it does not work with adb it doesnt reconize , if anyone can help to find any solution