yashsingh1/xdaforums huggingface dataset:
[Fire TV General] tillaz:
Could someone from uk with FTV3 pull itv hub, my5 and all4 for me please? hoping they were updated for later versions of android
[Fire TV General] Ronin3178:
As I haven't found anything yet, I know its brand new, this 3rd Gen FTV is my first, I assume someone is working on root access, or do older routes work, if anyone knows. TIA.
[Fire TV General] JeffDC:
Well, I packed up my Fire TV 3 today and have a pickup/return to Amazon scheduled for tomorrow.

Overall the Fire TV 3 worked ok. It was quick 'enough', etc, but after gaging against Fire TV 2, other than HDR, I don't feel there were benefits sufficient to change from the Fire TV 2. Given our poor internet here, just getting by with 1-3 Mbs, currently, I need the ethernet. I also did not like the SD slot being removed from the Fire TV 3.

Overall, other than the HDR addition, the Fire TV 3 seems a step down from the Fire TV 2. It is a little slower than the Fire TV 2 in testing, but not notably by 'experience' of daily use.

I have an Nvidia Shield coming this week, and will see how that compares.
[Fire TV General] JeffDC:
So far I've have not seen any for this device.
[Fire TV General] rodalpho:
How? There's a whole thread on it in this forum and the conclusion is the banner can't be disabled on the FTV1/2 with current software. Is the FTV3 software different in that?
[Fire TV General] JeffDC:
I'm back to my Fire TV 3, after having the Nvidia Shield Pro for about a week. The first one arrived, started updating, got to about 15% download, went black, and could not be hard reset. Returned.

Got a replacement Shield and have been messing about with that for the last 4-5 days, along with hours with Amazon support and Nvidia support. In the end it turns out that the Shield can not do Dolby or HDR in some standard format, so Netflix 4K HDR & Dolby out. That's how I get the ending, at any rate. Remote is abysmal. That Shield is going back.

Now back to the Fire TV 3. Simply, easy to use, and the remote is effective, over all.
[Fire TV General] JeffDC:
I don't think there is much, if any, info on the Fire TV 3. I sure haven't seen any.
[Fire TV General] rodalpho:
The guy said the banner could be disabled on the FTV3. I don't have a FTV3; I have a FTV2 and would live very much to disable that banner.
[Fire TV General] fred_rum:
My Fire TV 3 seems to have trouble remembering what resolution it should use. I have a 4k TV and with the resolution set to either 4k or Auto, the Fire TV regularly reverts to 1080p or sometimes 720p.

It also will not use 5ghz. I have dual band router with the same ssid but the Fire TV only connects to the 2.4ghz one.
[Fire TV General] schneid:
I tried a Shield Pro 2017 in July. Remote was DOA. No DD+. No IR. Would not connect to my Harmony Hub. Gave up. Sent it back. Miss my rooted FTV 1 as I could use Nova Launcher and have a more android experience. Unfortunately, many apps started balking at its root. Despite the kludgy interface FTV 3 is much faster than my FTV 1 and plays nice with my Harmony Hub. Using a powered USB hub to support Ethernet and my Logitech K400 keyboard works fine. Sometimes box will not start requiring a cold boot.

I would also like to the Ad Banner go.
[Fire TV General] JeffDC:
I'm with you about the Ad Banner. I haven't had the 3 version up and running long enough, as I just really got it fully setup last night, after plugging it in earlier this week and leaving it. I had the same issues with the 2 version needing an occasional, sometimes several times a week, cold boot. I am waiting for the ethernet gadget to arrive in early Dec and, like you, will put on a hub to get some expansion space/wired ethernet. It is just hard to imagine why they'd put out such a half-measure, half-baked gadget, other than wanting to get in on the Christmas/holiday sales rush.

I made sure I let Amazon customer service know why I disliked version 3 when we were on the phone trying to solve the Nvidia Shield "subscription" issues for several hours, and again after getting the Shield Amazon Prime subscriptions all working, and then discovering that getting it working on the Shield had muxed up the Prime accounts on my two Fire TV 2's, and the LG built in Amazon app. They could not solve that during that afternoon (long) call.

Amazon and I spent hours again on the phone trying to unravel the muxed up Prime accounts for the FireTV's to no avail, earlier this week. Another reason to get rid of the Shield. Got the Fire TV's Prime accounts up and running again last night after a few hours of messing about with the Amazon 'devices', 'channels' and 'subscriptions'. There is no single place which clearly has your subscriptions and devices. Subscriptions may be called subscriptions, or "channels", sometimes both.

It's good to get back to a basic, working setup. Now for Amazon to figure out why their app does not work on the built in LG tv app, despite full TV resets, removing the app, de-auth'ing, attempts to auth via the Amazon official sig-in or via internet with a 'code'....... which I suspect may never be 'fixed'. The LG is on it's newest firmware.
[Fire TV General] vanzan:
Possible stupid question: I debloated my Fire Stick 2 with the guide on these forums. Would the same guide also work on the Fire TV 3? Same software isn't it?
[Fire TV General] Garfield9992003:
Firetv3 isn't worth the money, cause it's slow and hasn't ethernet.

Every Android S10-box is much better than the firetv3.

I received the ftv3, tested it and returned to amazon.
[Fire TV General] schneid:
Maybe that is why they are on sale for 50 bucks today.
[Fire TV General] djRamage:
Got a FTV3 for $50 to set up for the father. Works about the same as my FTV2 for my needs. Obviously the Android version bump from 5 to 7 speeds many things up like app installs, ADB links. Vysor seems to glitch the 3 though, after being connected for 30 min i'll get black waves moving from one corner diagonally into the other corner and need to restart. Also, framerate seems to only go up to 59 rather than the 60 I get on the 2.
[Fire TV General] schneid:
I think he likes it ;):rolleyes:
[Fire TV General] seungbaekm:
Is it possible to make Fire TV shortcut to go directly Youtube App or Kodi app? I only use these two apps.

My old parents are confused by so many icons at the main page and keep pressing and buying some free, non-free apps and movies.
[Fire TV General] Hannover2k:
Didn't like Fire TV 3

I got a fire TV3 for Christmas from my GF. I already have a couple fire sticks but thought this might be a little better with the faster processor. I played with it for a couple days but I was not able to connect apps like Apps2Fire or adbLink . The connections were always denied by the device. even though I had enabled debugging and Dev options. I had to FTP in with ES file explorer than manually install the apps.

I went ahead and returned it and bought a used FireTV Gaming edition from ebay. At least it has the SD slot, etc. for installing more apps.

-han
[Fire TV General] schneid:
In a word NO! Waiting for a Channel Master Stream+. Android TV plus OTA tuner, Guide, and DVR.
[Fire TV General] JeffDC:
Adblink (Mac) still works to connect up and push installs.
[Fire TV General] masta_orc:
I tried to install Google Play Store as i did at Fire TV Stick 2.

But it didnt work as it did at Fire TV Stick 2, anyone know how to install Google Play Store at Fire TV 3?
[Fire TV General] atlkidz:
Is there a way to debloated my fire tv 3 like fire stick 2?
[Fire TV General] joe7dust:
Probably but not if you have fireos 6.
[Fire TV General] skorpeo:
mouse toggle not working

I had the same issue with the mouse toggle and I think that amazon deactivated the ability for it to work. I found an app on the amazon appstore called remote mouse for fire tv, (go figure) it was $1.99 and you have to install it both on the fire tv and on an android phone, which is a bit of a hassle, but it works after restarting the ADB a few times. you have to play with the muse speed a bit to have a bit more control over it but it does work, hope this helps.
[Fire TV General] JeffDC:
Thanks for that info. I will try that out, however, I don't usually care to use my phone to navigate the FireTV, too cumbersome and adds to another 'remote' to find in the bed!

Re: Mouse Toggle:

1. I don't think it has been disabled by Amazon. The mouse still moves around, it 'location' is just way off, always in the same relationship to where it 'ought' to be. Because of that

2. I believe that a code writer can create a simple routine to detect the screens (correct) resolution and set the mouse position accordingly, or

3. add a menu option for the user to make X and Y adjustments by pixels, or the like, though a code routine to check resolution would work better across the FireTV3's changing resolutions.

4. Amazon has added a working mouse in their Youtube work arounds for the 2 new browser applications.
[Fire TV General] skorpeo:
fire tv
[Fire TV General] schneid:
Edit: My paid for in January Channel Master Stream+ finally arrived un the country and was shipped on 3/14. The Post Office last tracked it on 3/17. The PO and CM don't care much, so I reversed the charge with Citibank. So, I am liking my 3 better now as it's the only game for me. Just added a 65" LG OLED to my 5.2.2 Atmos AVR and HDR and DV are outstanding on the TV as DD+ Atmos is on the AVR. Amazon Prime and Netflix have WebOS apps on the TV so I can't complain. I have also re-evaluted my effort to ditch DirecTV satellite. I discover the streamers and OTT's like Now, Hulu, Sling, HBO, Sho, Vue, are all 2-channel stereo on the boxes like FireTV. What is this? The 90's? DirecTV has them all in 5.1 and will stream and DVR.

As for the Stream+ AndroidTV boxes they appear to be a bust. Only place you can read about them is on AVSforum. Was a bold idea but nothing seems to work well. Biggest issue is no Netflix or Amazon on them. People are complaining about no 5.1 but that may be that it is not pushed by the providers.

There is a rumor Amazon is thinking about a new FireTV with OTA tuning and DVR. More vaporware for now. Compared to what is out there my DirecTV sat with 1080, some 4K, and DD 5.1 is pretty good. Watched Billions and Homeland recordings on it from Sunday. Both in 5.1 audio on DirecTV while just Stereo on the FireTV ShowtimeAnytime app.

---------- Post added at 06:10 PM ---------- Previous post was at 05:58 PM ----------
[Touch Dual, MDA Touch Plus ROM Development] medowance:
Noob on TOUCH asking is Manila = TouchFlo 2.0?? or a customizeable TouchFlo menu :D??
[Galaxy S 4 Q&A, Help & Troubleshooting] LexHimself:
Hi,

I'm an Arch Linux user myself using the latest ADB and Heimdall available from the repository.

For as far as my knowledge goes, Samsung devices do not support fastboot mode, and therefor it is correct that you can not use it with the device. (I might be wrong though.)

I encountered Heimdall failing in Linux, this was only because is did not run the program with sudo. After that all went fine.

It also has a GUI called heimdall-frontend, which you want to start from terminal with: sudo heimdall-frontend

Also, the bootloader mode is called Download mode, using: "adb reboot download" will present you with the same screen.

Thank you for the guide :good:
[Galaxy S 4 Q&A, Help & Troubleshooting] myudkowsky:
Thanks for the tip about fastboot for Samsung; I hadn't heard that before.

Also, thanks for bringing up the subject of "sudo" and heimdall. I tried heimdall with both standard user and "sudo" access (actually, while logged in via "su root"), and heimdall failed. I also tried to update udev rules as per advice in various places on StackOverflow, but even with these changes I was unable to get heimdall to work on my Linux. heimdall-frontend also failed when I tried it, of course. As an aside, I couldn't quite figure out how heimdall-frontend was supposed to work, because it kept searching for *.tar.gz files, and TWRP is a zip file. I thought I might unzip it and then create my own tar/gzip file, but in the end decided that using the command line with "recovery.img" was good enough.

Thanks for the tip about "adb boot download."

Glad you enjoyed the guide (my first-ever post here!). You're quite welcome and thanks for the detailed feedback.
[Galaxy S 4 Q&A, Help & Troubleshooting] LexHimself:
Hi,

Heimdall does use a different format to flash, never used a complete package with it. I did use the frontend for flashing individual files, and will show it with a video, since i am bad at explaining :)

Will not let me embed it: https://youtu.be/P8ZrjX-ngBw

What i do in the video is basically what you do from the command line. The gui will show however which file you would want to add for a certain flash, like modem, boot, system etc. Sorry about the small pause, had to reboot the phone.

You can flash *img files from zips with it, and also stock firmware from let's say sammobile. Rename the *.tar.md5 to *tar, and extract it, it will leave you with all the firmware files, and these you can add in Heimdall.

[IMG="Heimdall version"]https://i.imgur.com/X7Hyma8.png[/IMG]

About Heimdall not working in Linux for you, only thing i can think of is missing packages. Perhaps if you have more information about the error you received i could help, but that does not belong in the topic i guess :)
[Galaxy Tab 2 Q&A, Help & Troubleshooting] balums:
The title pretty much sums it up my doubt. I got one of this little babies for a while and I want to give it another try just to read some books and for college purposes (to see buildings, houses, etc - architecture student here :P)
[Galaxy Tab 2 Q&A, Help & Troubleshooting] john99ap:
Check out this thread https://xdaforums.com/galaxy-tab-2/help/best-kernel-rom-t3695023
[Android General] Schwester_Gabi:
Cubot Note Plus Stock Rom:

V8:

Mirror 1

V7:

Mirror 1	/ Mirror 2

SP Flash Tool for Cubot Note Plus Stock Rom:

Mirror 1 / Mirror 2

Cubot Note Plus Stock Scatter File for flashing:

Mirror 1 / Mirror 2

RoCuNo+_v0.1(Alpha):

Mirror 1 / Mirror 2

RoCuNo+_v0.2:

Mirror 1 / Mirror 2

RoCuNo+_v0.3:

Mirror 1
[Android General] Schwester_Gabi:
Problems:

i got some problems with dumping boot.img. the partiton size is 16M and the dd dump is also 16M but if i try to flash it back fastboot says the file is to large for partition. thats why unroot doesent work for now. Magisk patch the boot.img and resize them to 8M. than flashing works fine and all works. if someone can point me in the right direction would be very nice. if you have some questions please write here or pm me.

if someone can make a scatter file for this phone or had the scatter file it would be nice to share so we can try to backup the phone with SP Flash Tool. thanks.

if you found some bugs please tell it here so i can fix it.
[Android General] DarkWolf:
Nice
[Android General] Matthius:
Thanks for this great work, worked flawlessly. Just wondered, now we've got this root, is there any custom recovery we can install for it? (I realise many things will be available through Magisk's modules already, but still just wondered.)
[Android General] Schwester_Gabi:
not now. i hope that someone can make an TWRP or CWM for the Cubot and share it with us.
[Android General] Schwester_Gabi:
did you use the RoCuNo+ Programm or have you done all by yourself ? what do you use ? step by step or the AIO routine ?
[Android General] Matthius:
I had already unlocked the bootloader myself prior to this, looking for a way to root it before I saw this article (I gather this is the first available root method for this device), and also manually installed MagiskManager and the MTK-Engineering-Mode apk's and from then on I used the ruCuNo+ bat to complete it.

I followed stage 6, then 7, then 3. Pointed the Magisk to the original boot img, got it patched, sent it to PC and flashed the boot image with ADB. After turning on the phone, Magisk ended up with two green ticks so everything was good to go.
[Android General] Schwester_Gabi:
yes it is. i searched over a week to find a root solution but nothing found. so i make it by my self and want to share this with the world :highfive:

thats also a way :good: maybe i implement this for users who already unlockt the bootloader. then the the phone must not be factory reset again. :good: thanks for telling me this way i dont think of bevor :)
[Android General] Matthius:
No worries, great work :) - hopefully, we may see some custom recovery to come in the future from someone. Wish this phone actually had its own page on XDA, but I doubt it has enough widespread support for that, who knows.
[Android General] Schwester_Gabi:
Yes. custom recovery for the phone would be great. if I knew better, I would make one myself. but I've read a lot. maybe I'll try it in future to make one.

i think this phone dont get his own page. but maybe the Cubot vendor get his own where we can put all related Cubot threads together in his own sub section. :good:
[Android General] spunky1a:
i got a error after "fastboot oem unlock" -> "FAILED (remote:Unlock operation is not allowed)". i think, bootloader is not unlocked, what can i do?

oops: had forget "OEM UNLOCKING in DevMenu"
[Android General] Schwester_Gabi:
yes. that was the point. :good:
[Android General] francwalter:
I think the sequence in the Guide is a bit wrong. In the Guide I read:

If I follow this I get (in very small fonts) as another user here in this thread:

And no unlock of the bootloader seems possible.

Because first I need to do OEM UNLOCKING in the Dev. Options, which seems very clear. Only after I can fastboot oem unlock

What I further not quite understand in this post, is it either the Guide or the Batchfile I have to follow? Or is it a mixture of both what I need to do?

As I think the Batchfile cannot enable the Developer Tools in the System, or?

Lastly and most important: on my phone I don't see a mmcblk07p only a mmcblk0p7, so this throws an error:

I guess that mmcblk0p7 is ment, so I did a dd with mmcblk0p7, and I let patch this file with Magisk to the file: patched_boot.img

But here I am very not sure and if I flash now a wrong img-file with this:

I strongly guess that is it with my new phone :)

So could you please confirm that it was just a typo in the first post here?

How can I know which of these files in /dev/block is the boot.img?

Thank!!!
[Android General] Schwester_Gabi:
For this Problem the batch says first enable dev options and OEM unlock and than go to next step.

Yes. Its a typo. You can flash it.

Btw i am on the way to rework the whole Programm for better use and better instructions. Give me some time because iam very busy at the moment. But I will update it soon.

And remember its an 0.1ALPHA for now. So its not perfect :angel:
[Android General] francwalter:
Oh Great! It works :)

Thank a lot for your work!!!
[Android General] Noobius:
As a noob, I did not get what to do after installing the Magisk manager. So I have it installed, but it shows no root. How can I then install the root?

I used the "RoCuNo+_v0.2.bat" in admin mode and although I got through the unlock and root, I am stuck on what to do on Magisk in the phone.

I was able to root my galaxy tab, but perhaps I am too noob for these instructions?

(Btw while booting I get the "this phone is unlocked and cannot be trusted" text)
[Android General] Matthius:
Ran into a bit of an issue here, I received an official OTA so I uninstalled Magisk by clicking uninstall within the APK, now my phone is stuck on the boot logo. I've tried to flash the original boot img, but I can't get into the system to confirm flashing it on the device. It displays under <adb devices> but when issuing the <fastboot flash boot> command it says <waiting for any device> and nothing occurs.

Not sure how to proceed without wiping the whole thing. Anything I can try?
[Android General] Noobius:
So I did a factory reset and used the "RoCuNo+_v0.2.bat" again as follows:

First enabled developer mode, USB Debugging unknown sources, OEM unlock

Then ran the tool:

1 - unlock bootloader - success

3 - root - success

5 - install magisk - here the phone first boots, then it erases data, then does again all the "setup your phone, wifi, accounts etc"

"Orange state - this device is unlocked..." appears in the boot

Magisk is not installed in the apps.

OEM unlock is greyed out (but enabled)

So the tool worked differently, or I am missing something.

Perhaps there are new versions of this phone?
[Android General] Noobius:
...aaaand it's rooted.

I did everything again using the adb -command instructions.

So did not use the .bat tool.

Used the step-by-step instructions.

Thanks a lot! Finally I can use macrodroid properly.
[Android General] francwalter:
OH!

Was it not possible to flash the Update without removing Magisk?

I got also a System Update, see attachment, but I doubt I could install it with having Magisk on my phone (and the rest: Magisk modules, root, Xposed with modules...).

Is it possible to install the update without uninstalling Magisk?

If this were possible, is Magisk after gone?
[Android General] Matthius:
I'm honestly not so sure - I soft-bricked my phone and had to use SP Flash tools to install the stock ROM again, wiping everything.

If there is a procedure for doing this without a custom recovery, I'd like to know. But, what I would definitely recommend is to not hit the "uninstall magisk" button.
[Android General] Schwester_Gabi:
Sorry for not responding here. I had some personal problems in real life. In the next days i take a look on the New update and rework the Programm. Sorry for that and for every one who get in trouble.
[Android General] Schwester_Gabi:
So i testet the New update with RoCuNo v0.2 and magisk. It works like befor. But i didnt recive the update via ota. So i had to flash it manualy with the flash tool. And after i flash the patched_Boot.IMG and reboot i have to flash the magisk.ZIP with magisk again but in flash mode (recomned and only availible after flashing magisk via Boot.IMG). But after this all works. I flashed than the magisk busybox Modul and after reboot it works. Busybox APP detect the busybox and also titanium backup found it and works with it. So nothing changes to the root Methode. But i will update the guide and also the RoCuNo tool with updated files and i will delet some features from Programm (like unroot until i get it to work. Sorry for this.) if someone recive the update via ota and can verify that magisk works after update please write it here for other users.
[Android General] Hobler:
Sorry, I don't get it :( "i had to flash it manualy with the flash tool" means you had to flash the full stock rom (V8) with SP Flash Tool?
[Android General] francwalter:
Verstehe ich das richtig, die V8 ist das komplette ROM nach dem Update vom ca. November 17 ?

EN: understand I this right, the V8 is the complete ROM after the Update from around Nov. 2017?
[Android General] Daniel 9999:
Hai Bro,i m using a china phone mtk 6737T android 6.01+ and can i use this to root my phone ? Thank.
[Android General] aiaco:
V09_20171210 is out and downloadable from cubot's forum site (however i get it via OTA after having installed v08).

I have tried to modify the system image system.img (by only changing one line in build.prop, related to language) and then flashed it using spflashtool but i obtained a bootloop, solved by flashing again the original unmodified system.img. It seems like some king of integrity check is performed on system files....

Any idea why it happens and how to solve this problem?

Thanks in advance.
[Android General] Schwester_Gabi:
Only if you dont get it via ota update. With ota update you must not install it via flash tool. But after some Tests and flashing i found out that installing root with my tool the magisk and su dont work complete as it should. So after flashing magisk with tool and Boot.IMG and after phone boots into Android you have a third Option in magisk manager app on install button. There you can flash magisk.ZIP with the magisk app. If you do that all should work as if you flash magisk over recovery.