yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] mikey6283:
Xposed Framework Error 1 in TWRP recovery,

Hi,

I flashed the xposed-v80-sdk22-arm64.zip to a sdcard & USB and received the following message both times :

Installing Zip File xposed '/usb/xposed-v80-sdk22-arm64.zip'

Checking for MD5 file...

Skipping MD5 check : no MD5 file Found

**********************************

Xposed Frameworkl Installer zip

********************************

- Mounting /system and /vendor read-write

- Checking environment Xposed verison 80

- Placing Files

chown: /system/lib/libart.so.org.gz: read-only files system,

Updater process ended with error :1

Error installing zip file '/usb/xposed-v80-sdk22-arm64.zip'

Any ideas on where i am going wrong.
[Fire TV Android Development] TROJAN4EVR:
On a post at aftvnews.com regarding double image, someone mentioned that you need to connect the fire tv to a newer display tv to finish the rooting process. Once rooted you can connect it to the older tv with double image and it will display correctly...
[Fire TV Android Development] elliwigy:
asking the same question multiple times wont get a resolution any quicker lol.

I assume you didnt flash the pre rooted rom from [MENTION=3991724]rbox[/MENTION] did you?
[Fire TV Android Development] Takeoo111111:
I think the problem could be that, /system is always mounted read only. I tried, but couldn't fix it manually by remounting.

I wrote about this here: klick.

Can you verify or disproof this? That would be interesting for further investigation...

It also would be interesting if you also reflashed recovery (rbox warned not to do this!) or if it also happens with the original installation.

While flashing everything went as expected? No "error: source file is larger than target file!" or something else?
[Fire TV Android Development] elliwigy:
i think most everyone had this issue unyil flashing the pre rooted rom.. if you used the pre rooted rom your system can be mounted and ive not got the read only error since then
[Fire TV Android Development] mikey6283:
Hi I am a novice I rooted ATV2 ( zeroepoch ) was rooted prior to installed rbox recovery 3.0.0.3 thru ADB shell no problems. and worked a treat so i thought. I am not sure what i need to do now. Are you saying that I should Flash the Recovery 3.0.0.3 or perform a Root again?
[Fire TV Android Development] Largewoodenspoon:
Ok guys. I plugged into my third tv and all went swimmingly! My old don't Bravia only gets 1080i. That was the issue at the start of the boot menu process! I am happy!!!
[Fire TV Android Development] bula1ca:
That is not what he meant. Download and install latest pre-rooted image from here ( http://xdaforums.com/fire-tv/development/firetv-2-sloane-prerooted-stock-images-t3309783 ) using Flash Recovery 3.0.0-2 (this is the latest v3 file)
[Fire TV Android Development] elliwigy:
That is most likely your issue. If you were already rooted and just installed recovery the stock rom was not writeable out of the box.

Therefore you need to flash [MENTION=3991724]rbox[/MENTION] pre rooted rom then I had 0 issues flashing zips in recovery as it was writeable with his pre rooted rom.

Correct.. thanks for posting the links!
[Fire TV Android Development] vrl2:
It is a relief to know that you've got one under development - thank you! I can connect and handshake via USB (but haven't figured out a way to run ADB over usb to attempt to rewrite /system) so it looks like by best shot is to wait for the unbrick rom -- I appreciate it.

My AFTV2 was initially running stock 5.0.4. which I rooted it with the original ~2 hour patching process for stock devices.

I then installed FireTV Recovery v1 (non-auto-installer method), and successfully flashed pre-rooted stock Image 5.0.4_r1. When pre-rooted 5.0.4_r2 was released, I successfully flashed that as well (which also installed TWRP 3.0.0-2). Worked great until I accidentally wiped /system.

Currently, the AFTV2 starts and quickly flashes the amazon logo before the screen goes black, and network ADB doesn't connect. Should anything be attempted at this point over the USB connection? Is it worth attempting to re-do the process with one of the recovery installers (or repeat the original ~2 hour root) to rewrite /system, or would I be barking up the wrong tree?

Thanks!
[Galaxy S6 Edge Q&A, Help & Troubleshooting] supernab12:
Hi,

first sorry for my bad english! :)

My S6 Edge have a issue.

I tried to go back to Firmware 5.0.1 (I know very bad idea) and then my phone bricked.

So I tried go back to Original Firmware 5.1.1.

I flashed the FIrmware with Odin but It has everytime Error message : Hidden.img failed.

So i renamed the hidden.img and then It worked and the flash was completly.

But then its stucks everytime on samsung logo. (I also tried with samsung switch and kies to flash it but the same thing happend)

So then I install/flashed the Kernel: Unibase and then the phone worked.

But now is my problem that the phone everytime reboot it selfs.

Example: When i chat via whatsapp = Its boot from himself

or when I look videos. Even when I dont use the phone. Everytime the same issue. It makes everytime a new start.

Pls help me!
[Galaxy S6 Edge Q&A, Help & Troubleshooting] xstokerx:
Now that u got it to boot have u tryed odin back to stock or smart switch or dis u try those after booting?
[Galaxy S6 Edge Q&A, Help & Troubleshooting] supernab12:
Yes i did both but same issue. Everytime it sucks on: Samsung s6 Edge logo

Even everytime After I Flash via odin the : unibase Kernel it works and the phone boots and all works. Only The problem is that The phone power off himself every 10-20 Minutes and reboots everytime...
[Galaxy S6 Edge Q&A, Help & Troubleshooting] supernab12:
No one can help? :/
[Shield Android TV Q&A, Help & Troubleshooting] jst07:
I've had my Shield TV for about 3 months. Recently it's started not having any network connectivity (not even local) at times. It seems to be after it goes to sleep and wakes up, but I'm not sure that it happens every time yet. The Shield says its connected to my wifi, but does recognize there is a problem because it has a ! on the wifi symbol. I have to either restart or disconnect/reconnect to get it to work. Does anyone have a similar problem like this?
[Shield Android TV Q&A, Help & Troubleshooting] visitor29:
Same here

This is kind of bug

Restarting console helps save some time, then trying figure out the problem.

Sent from my Nokia 3310 using free xda app
[Shield Android TV Q&A, Help & Troubleshooting] kutulu32:
the only way I found to have very few disconnections is not to have a lot of devices connected to the same channel of the rooter. 2-3 max included shield.

this issue affects a lot of users included me and you.
[Fire TV Android Development] AFTVnews.com:
Awesome work!

For those who need a step-by-step guide with screenshots:

[GUIDE] How to Root a Fire TV 2 by installing rbox's Pre-Rooted Image

[VIDEO GUIDE]

[YOUTUBE]XYyR-kCW4aA[/YOUTUBE]
[Fire TV Android Development] wadisnake:
Awesome! Thanks !
[Fire TV Android Development] dk1keith:
Awesome! Thanks for all your great work!
[Fire TV Android Development] ians325:
Any one with Mac Guide Please help
[Fire TV Android Development] elliwigy:
awesome sauce!
[Fire TV Android Development] Takeoo111111:
Hi,

I ended up with following message during image installation:

[...]
Coping system image...
Updater process ended with signal: 7
Error installing zip file '/usb/sloane-5.0.4-rooted_r2.zip'
Updating partition details...
...done

And, no wonder... after power cycling (I had to do so, since recovery seemed to be frozen) it stuck in a bootloop.

But I still can access recovery!

Any ideas? Is there any way to get a more verbose output?

(Used recovery 3.0.0-2 and recovery_installer v3)

Edit:

Now there is no /system Partition mounted

Edit2:

I was able to mount /dev/block/mmcblk0p13 manually to /system but it seems that I can't mount it in rw mode.

If I do so, it switches back to ro when I there the folder. (I think, that could be the error during image installation)

What's strange is: If I enter /system/lib I can't execute any command (like "ls" "touch" etc. only cd is working) I get following output:

/system/lib # ls
CANNOT LINK EXECUTABLE DEPENDENCIES: "libc.so" is 32-bit instead of 64-bit
# echo $LD_LIBRARY_PATH
.:/sbin

File libc.so is existing, but I can't finde a way to get the file type data

Edit3:

More strange things:

I was wrong! I am able to write to /system till the point when I execute a "ls" :eek:

Than its back to ro.

Edit4:

I tried to reflash recovery and the following error:

Locating the target file...

[...]
Reading 05055F000: 100%
Opening the target file...
Reading 01D947000: 100%
error: source file is larger than target file!

No shure if that was there when I flashed it first.

Related to this post
[Fire TV Android Development] Hoggels:
re-rooted works fine !

its full Google Play Store Support possible ?
[Fire TV Android Development] elliwigy:
yes.. its been done already but some users are having issues
[Fire TV Android Development] rbox:
If you reboot in the middle of flashing the ROM, you're /system is going to be corrupt. It's a miracle recovery is still working. The reason the installer is failing is because you can only use it for 100% stock roms. Once you start using recovery and flashing things, you cannot (and should not) use the installer. I will add a warning.

If recovery hangs again, you can run

killall recovery

from adb shell and it will restart. It is extremely important never to reboot if you have a failure. As for logs... /tmp/recovery.log has the full log. Have you verified the file transfer properly before trying to flash?
[Fire TV Android Development] Hoggels:
Google Playstore

Who can find it? Itsca zip to Flash with Recovery or gapps.org?

For gapps.org what for options i must select it? Thx
[Fire TV Android Development] bula1ca:
Read this tread: http://xdaforums.com/fire-tv/help/q-guide-to-getting-google-play-rbox-t3310974
[Fire TV Android Development] elliwigy:
haha thx for posting the link..

amazing how much tunnel vision exists as theres threads for most anything but somehow some fail to find them lol
[Fire TV Android Development] bula1ca:
LOL
[Fire TV Android Development] TorqueWrench001:
Success!! I have the issue with the recovery screen being scrambled. Switched to another tv got through recovery and installed rom, then the screen would be blank when booting to system. After 2 hours of reading and trying.... Went back to the original tv , the tv recognizes the home screen display. Apparently whatever the issue with the recovery screen is prevented the home screen from being visible on the second tv. anyway all good now!
[Fire TV Android Development] elliwigy:
i think someone else had the same issue and i think it was the tv lol

what do you have the fire tv set to in the display settings? If you had it set to a certain setting such as 1080p but the tv is in a different setting could be the issue.. or something like that lol
[Fire TV Android Development] krawhitham:
5.0.5_r1 installed perfectly
[Fire TV Android Development] dk1keith:
how did you install....did you update recovery first then flash 5.05_r1?

thanks
[Fire TV Android Development] AFTVnews.com:
Someone in the comments of my guide said the scrambled screen issue was due to incompatibility with 1080i TVs. I'm curious [MENTION=3310430]TorqueWrench001[/MENTION] is your scrambled TV a 1080i set that's not capable of 1080p ?
[Fire TV Android Development] Largewoodenspoon:
Mine is a 1080i tv. Old sony bravia. Great picture and sound though. The display is most definitely tits up on twrp. However, I have a broken tiny cheap wall mounted 1080i flatscreen, with no sound, which is now my dedicated 2nd aftv monitor, just for twrp purposes. It even fits snug under my living room tv unit out of sight.

I am awaiting funds for a new samsung curved 55inch beast. But, I think it will have to wait until the sony bravia dies on me! lol
[Fire TV Android Development] Hooners96:
The box won't boot which means I won't be able to boot into recovery. I tried doing the alt I print screen but the box won't even power the usb port
[Fire TV Android Development] wdcspurs:
I am still fairly new to utilizing adb via command prompt. I successfully installed the prerooted 5.0.5.1 r1 yesterday and verified root in the steps outlined and got the SU request to popup on my TV. I went back in today to disable the amazon auto updates and such laid out on AFTVnews and I get to the point on the command prompt where I need to gain root access. I type in SU and it says su not found. What am I doing wrong? SU app is still on the AFTV and it boots into recovery. This means I still have root correct? If so, why am I not able to access it via adbshell/command prompt?
[Fire TV Android Development] D-an-W:
I presume you selected "Grant" on the TV screen when you first ran "su"? When you confirmed root with "su" did the command prompt change from "shell@sloane:/ $" to "root@sloane:/ #" ok?

EDIT: Forgot to say...its also case sensitive, so make sure you use su and not SU.
[Fire TV Android Development] Leedsgreen:
I'm planning to root my AFTV2 this weekend and have a question if OK. In his guide to rooting using A-to-A USB Elias on AFTVnews recommends 'downloading the latest Pre-Rooted Fire TV 2 ROM' (from this topic) which is currently 5.0.5.1_r1. However, I'd rather put my AFTV2 back to 5.0.5 so that FireStarter will work as it did before Amazon rolled out 5.0.5.1.

Can I ask, even though my AFTV2 is now on 5.0.5.1 is it OK to use pre-root 5.0.5_r4 straight away or do I need to first root with 5.0.5.1_r1 before going back to 5.0.5_r4? (Sorry if this is a simple question but I've read through most of the posts in this thread and can't find an answer).

Thanks for any help.
[Fire TV Android Development] westc0ast:
After this update. I lost root. But still have twrp. and a non working supersu What can I do?
[Fire TV Android Development] wdcspurs:
Flash the pre-rooted version of this update in TWRP. The link is in the op for this thread!
[Fire TV Android Development] PhoenixMark:
You would flash 5.0.5 pre-rooted. The trick will be when connecting it to the internet to not let the device download the software update that it will automatically seek out. It will see 5.05 and want to put you right back on 5.0.5.1. Read this page for tips on this: http://www.aftvnews.com/how-to-complete-the-fire-tv-initial-setup-without-updating/
[Fire TV Android Development] Leedsgreen:
Hi PhoenixMark, thanks very much for your reply, which is something I hadn't considered. However, please can I check, does the 'Reboot System' (the less step in TWRP process to install the pre-rooted rom) always take you to the Fire TV initital setup phase (where it checks for software update)? I assumed the 'Reboot System' would just initiate the usual AFTV2 power-up sequence (i.e. colourful Fire TV logo) before going to the homescreen (i.e. without checking for software update immediately)? I was hoping this would then give me chance to block updates. Thanks for any further clarification :)
[Fire TV Android Development] PhoenixMark:
It's going to take you to the screen where it asks boot normally or launch recovery. If you don't do anything it times out and boots normally. You're only worried about your initial boot because your setting up your network. Once you've blocked updates (which you need to do on initial boot after rooting) you don't need to worry about rebooting any more because it will be blocked from checking for updates.
[Fire TV Android Development] Leedsgreen:
Thanks PhoenixMark for reply again, that helps and is good to know. It's hard to fully understand the process without rooting before. Much appreciated again.
[Fire TV Android Development] dailo_wai:
I only get the white amazon logo regardless of which pre-rooted bundle I install. I can however get into recovery mode, so are there any log files I could look at to give me a clue why it won't boot normally? May just be a hardware issue.
[Fire TV Android Development] wohltat:
Hey,

thanks for our awesome work. I just installed 5.0.5.1_r1 yesterday. However, I got a little problem.

I thought the images were prerooted. Today I tried to install Paragon NTFS and it tells me that I do not have root. When I use su after ADB Shell. I get

Any idea what I could have done wrong and how to fix it? I did the factory reset in TWRP and all the other steps according to this guide. http://www.aftvnews.com/start/
[Fire TV Android Development] OpenSkyz:
If you get the connection to ui timed out:

Just reflash the 5.0.5.1_r1 again in TWRP, if you put it on your sdcard it will still be there. I had same issue, and it took care of it and first time I used "su" it popped up on screen like it should.

Good Luck!
[Fire TV Android Development] robertjw:
Getting root gives users some amount of control, but with selinux standing over the show, even root is a small player. Google/Amazon still have control of the devices we have purchased since selinux always trumps the user, even if the user is root.

Ok, enough of the ranting about the "cat and mouse game" being played by vendors of secret software. Ok, at least Google's software is semi-secret, but there is definitely a strong leaning against giving users control.

Today I've attempted with some amount of difficulty and yet some small amount of success the installation of optware in a rooted FireTV2. There are over 17,000 FREE and open source software packages in the optware repository and I'm struggling to bring this wonderful capability to life on the FireTV2. But there are issues and it appears that they are mostly pointing at intervention from selinux rules enforcement.

I'm wondering if anyone else has been working in this direction.
[Fire TV Android Development] rbox:
If selinux is being a pain, disable it.

setenforce 0

from adb shell after running su.
[Fire TV Android Development] robertjw:
Sweet! Where were you at 5AM this morning when I needed you. This solves a lot of problems.
[Fire TV Android Development] rbox:
Sleeping :)
[Fire TV Android Development] robertjw:
Well, we are on a roll now. My other roadblocks are:

1. Where in $REALM did google/amazon put /etc/rc.local? In other words, where/how can I launch my initialization script on each boot.

2. How to keep "vold" from threatening to reformat my state-of-the-art ext4 external sd with FAT. (this is really just a minor annoyance and I could live with vold's threats if I really had to)
[Fire TV Android Development] rbox:
They didn't put it anywhere. There is no concept of rc.local in Android because it makes no sense. SuperSU has /system/su.d/ that serves a similar purpose. You can read about it here: https://su.chainfire.eu/#selinux-policies-supolicy

Have you tried creating 1 tiny FAT partition at the beginning and then a 2nd ext4 partition afterwards?
[Fire TV Android Development] robertjw:
Two great tips. You are a time saver! I love the tiny FAT partition workaround. That should work perfectly.

That was enough to get Optware up and running. Now I'm off loading up some of those 17000 FOSS packages. Python and Ruby both install and run fine on the FireTV2 and these languages are now available for more advanced scripting. This is starting to look good...
[Fire TV Android Development] robertjw:
Unfortunately it looks like scripts placed in /system/su.d/ are not being executed at boot time in the FireTV2.

This script placed in /system/su.d/

#!/system/bin/sh

echo "running /system/su.d/" >> /sdcard/local/messages

runs fine from an adb shell root prompt, but it does not run automatically on system reboot.
[Fire TV Android Development] rbox:
/sdcard might not be set up when the script runs. Try using /data/media/0 instead of /sdcard.
[Fire TV Android Development] Ewle:
I extracted the 5.0.5 image and updated the recovery to 3.0.0-5 then rezipped it.

When I go to install the zip TWRP says it's corrupt when it's not. What am I doing wrong?

Also whats the best way to image and clone a AFTV2? Ideally I'd like to install a preconfigured build but restoring a backup is an option too though there isn't a way to restore backups from other device IDs within TWRP without creating a new file folder and moving the backup over plus it does some weird stuff not restoring data for Kodi and screws with the amazon account.
[Fire TV Android Development] robertjw:
Switching to /data/media/0 gives the same results, works from an adb shell root prompt, but not automatically on reboot.

Here's another interesting datapoint. Putting this script in /system/su.d/

#!/system/bin/sh

setenforce 0

Then after a reboot, you see this:

root@sloane:/ # getenforce
Enforcing

so it appears that the script was not executed at boot time, or at least not executed with root permissions.
[Fire TV Android Development] rbox:
I've never actually used it. Assumed it would work. Did you make sure the permissions are set right?
[Fire TV Android Development] robertjw:
The instructions recommended setting permissions at 700 for both /system/su.d/ and the script file(s). I did that and tested it by running manually noticing the correct results. I also tried an experiment with permissions set to 755 with identical results. Both tests ran fine from an adb root shell but failed at a reboot.
[Fire TV Android Development] rbox:
I could probably add init.d support to 2ndinit, but that is more of a long term goal, after releasing firetv1 and fire stick stuff, so not for many months probably. You could try https://play.google.com/store/apps/details?id=com.androguide.universal.init.d If you have an android phone or tablet to download it on and then pull the apk.
[Fire TV Android Development] elliwigy:
i can confirm universal init.d works.. i have been using it from the start and have an sepolicy fix running at boot automatically for my viper4android to work properly.

it essentially appears to not kick in until device is up a few seconds but it hasnt let me down yet and will pop up a little message once it kicks in (similar to other apps that run at start up such as wukong remote.)
[Fire TV Android Development] robertjw:
Have you actually tried init.d on a FireTV2? When I adb install the Universal init.d app, the app appears on the FireTV2 but its "OFF/ON" button is greyed out and a test shows that it does not run scripts placed in /system/etc/init.d/ on this device.
[Fire TV Android Development] zeroepoch:
There is also the option of using Ubuntu on the device depending on your needs. This gives you access to the entire Ubuntu repository. Mainly depends on if you plan to still use Android apps or the display. See http://xdaforums.com/fire-tv/orig-development/fire-tv-2-ubuntu-headless-install-guide-t3323351
[Fire TV Android Development] robertjw:
That is certainly very interesting. Thanks for letting me know about this option.

In my case I'm still wanting to use my FireTV2 to drive Amazon/Netflix content to my 2160p (4K) TV, so it looks like Optware is still the best fit for my use case. I'm ssh'ing into the box and need a fairly complete set of shell utilities at my fingertips.
[Fire TV Android Development] tselling:
Hi, I wanted to check and see if you have had any luck with getting scripts to run at boot? I also found that scripts in /system/su.d did not run. I want to mount an ext4 partition as well at boot time. I want to link the data/app and data/data folders to the external sdcard and am not having much luck. I also like to use "mount -o bind" to bind stuff like the internal Android folder to the external sdcard but I need something that runs my script(s) at every boot.

Thanks for any insight you might have!