yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] Flakie:
Sorry, meant to post back. I have it working now. I had flashed the Magisk Zip though. Was trying that and the rooted rom.

It was hit and miss if they brought up the confirmation to allow root once the 4K was booted and su command issued.

I missed it once as i wanted to take a pic to make a readme doc. Took the pic and missed the timeout. Lesson learnt.

Eventually it worked and all is good now. All I mainly want to do is to create an image I can use on all the firesticks I manage and that should be possible now. Hopefully anyway. If so its going to save me many hours of work so much kudos to all involved in getting root and twrp working on this device.
[Fire TV Original Android Development] Sus_i:
If you think about a TWRP backup from a working stick, restored on all sticks you manage, that will only work for restoring the OS on /system

If you restore a full backup with data partition of a registered stick to a second stick = aka. clone the first stick to the second, the second one uses the account, serial, app data and such stuff of the first one. You may get DRM/Account errors, if more than one stick is online, prime/netflix and so on won't play anymore ;)

So, if you like to clone data to other sticks, make sure that only one stick is online at the same time :p

Anyway, if you try it, let me know how long it takes, until amaz. blocks/banned the serial :D
[Fire TV Original Android Development] Flakie:
Ah ok thanks. I was hoping this might be possible but now I can see it will not.

Still, I can at least set each one up individually (I know all the Amazon account details) and then create an image of them individually and use that to restore if any problems (keep one image on the stick and a copy on my laptop)?

If this is possible, it will take a bit more time (but no more than it currently does) to do the initial setups, but restorations will be much quicker.

I will write an app to automate a lot of it (like adblink). I already have one I wrote last year and can modify this (saves all that typing or copy/pasting of adb commands).

Though I have noticed the adb in twrp is a bit limited compared to when the 4K is fully booted, it should not be a big issue (no IP connection and cannot use scrcpy etc).

Currently I occasionally must do a repeat full setup of the 4K's, as sometimes they seem to automatically do a full reset of themselves. Though one person told me it happened after they sat on the remote (it is possible they are playing in the settings and do this themselves?).
[Fire TV Original Android Development] Sus_i:
Yes :good:

Best is if you do a backup after the full setup, then its easy to restore.

Thats right. But aside from the magisk install, you can do anything from fireOS adb.

lol, sat on the remote :D yeah, I think there is an remote key combination that does such a factory reset.

You can do an factory reset from the settings too.

If all the sticks are in your network, you can manage all of them without a hassle. You can push ota updates (renamed to zip) with adb to cache, write TWRP cache recovery commands followed by an adb reboot recovery. Only thing to avoid is wiping data.
[Fire TV Original Android Development] Flakie:
This is interesting. Thanks.

Most of the 4K sticks (I support over 30 remotely but more with physical visits) are currently not in my own network (except for my own 2) but with my own developed app I am able to control them remotely (install/update/uninstall apk, list 3rd Party and system apk, reboot, and run scrcpy with parameters directly from my app). I can save the config for each device too (ip address/port/scrcpy parameters amongst other things). Of course, I do have to visit once to configure their router to allow my network access to theirs on 5555, 5556 etc). I handle multiple devices in one location by port forwarding 5555/5555, 5556/5555, 5557/5555 etc. The app works with other devices too but was designed with the 4K in mind. I am working on an updated version that does much more. (turns on ip mode for usb connected phone without the ip address being entered, amongst other things).

Will the push of ota with adb to cache allow me to do more than I already do? With my network allowed access to theirs would I be able to do this remotely? They all have fast internet connections.
[Fire TV Original Android Development] Sus_i:
Adb works the same. You can do what you want, if you know the IP and the port.

But maybe it is better, if you choose a port far away from a standard port range ;)

The cache recovery command allows you to place TWRP commands with adb.

An example is the code from post 3:

echo "--update_package=/path/to/zipfile" > /cache/recovery/command
echo "--wipe_cache" >> /cache/recovery/command
reboot recovery

With that, physical access to the stick or an adb connection while booted into TWRP isn't necessary, you can do TWRP stuff remotely.
[Fire TV Original Android Development] Flakie:
Thats great. I will have alook at this. I don't suppose it can reboot out of twrp when done?

Think I need to post about how to do a full backup this way too, though I am thinking its not possible with commands in twrp (but hope I am wrong).
[Fire TV Original Android Development] Sus_i:
If a command file is present, the recovery does all queued commands in there and reboots ;)

I don't know all AOSP recovery commands, but I think you find a list somewhere.
[Fire TV Original Android Development] tech3475:
I just purchased a Fire Stick 4K and I’m thinking of rooting it, it’s been a while though since I’ve used Fire TV root wise though, could anyone please tell me if there any known issues with certain apps caused by rooting? E.g. DRM/playback errors, particularly with Youtube, Amazon Video, Netflix, Apple TV and Disney+.

I know Google Play Store was broken last I tried on my rooted FTV2.
[Fire TV Original Android Development] dcarvil:
I've had no problems with Netflix/Apple TV on my rooted 4k. I don't use the other apps you mentioned, so I can't comment.

I have seen several posts on this forum with people who have tried to install Google Play Store experiencing boot loops and other problems, so I would not try to install it.
[Fire TV Original Android Development] Flakie:
I have done 5 of these now with no problems.

The last one I just did it got all through the process of running the exploit which all completed as normal with no errors.

But TWRP never loaded.

When it rebooted it just went to a black screen with firetv on it.

If I unplug it and plug back in it is the same black screen.

Trying to run the exploit again it does not even seem to see the 4K.

Usually if the short is not on correct it fills the terminal with code that ends with something like:

ERROR: Serial protocol Mismatch. Expected 0001 got 0000

Now the terminal is empty (remains at 'waiting for bootrom'), whether I have the short on or not and after a few seconds the black screen appears.

Bricked?

Update: I cannot see DATO or CHK so I have been shorting on CMD.

I just removed the heatshield frame and shorted on CHK (DATO is way too small for me) and the black screen does not appear but the terminal is still 'waiting for bootrom'.

Update 2: All the capacitors look good. I have ordered an OTG which is meant to arrive today. Maybe that will kickstart twrp.

[IMG="Close-up of 4K chip"]https://flakie.co.uk/images/sandisk-close-up.jpg[/IMG]

Update 3:

After connecting and reconnecting the power many times it is finally at twrp

Update 4:

It is now working OK. I unplugged it and put it back in the casing and it was on the black screen again for a few seconds before finally booting normally.

I missed a detail in above post (sorry). I had tried the exploit again a few times since first post. Removing the power and hdmi each time.

Mostly it would not respond in the terminal and remain at waiting for bootrom with either the black screen (so short proably not on correctly?) or with no screen at all (hdmi stating no connection, so short good?).

The last one, with it shorted to CHK the exploit was run again (about the 10th attempt). This time I had left it unplugged for many minutes before trying. I completed OK this time.

Not sure if it was over heated before?? Or if I had bad connections??

All good now though.

I will add I do not recommend taking off the heatshield frame (even partially like I did). This is a pain to get back on and took some fiddling to get the heatshield to sit back on it correctly.
[Fire TV Original Android Development] BLACKPHOENIXRIZIN:
Hey k4y0z. #1, thx so very much 4 the mad work u & the othez put into this (ISO) file. I just need 2 know wut program did u use 2 get ur bootable (ISO) file? Bcuz I tried using rufus 2 burn 2 a usb drive but ran into prob. (This image uses Syslinux 6.04/pre2-11-gbf6db5b4 but this application only includes the installation files for Syslinux 6.03/2014-10-06. Two additional files must be downloaded from the internet [ldlinux.sys and ldlinux.bss]). I tried 2 find them on the net, but no luck. Hopefully u can help with this matter. Thx much, peace.
[Fire TV Original Android Development] Flakie:
I did the same and Rufus automatically downloaded the files for me.
[Fire TV Original Android Development] Sus_i:
Hey

Maybe you shorted the wrong side?

I hope its ok for you, used your detailed picture from your post and painted two red circles into your close-up:

-One of the red points must be shorted, in order to get the bootrom.

-The black circle side is already ground, a short on that side won't work at all.

-Many people don't notice that fact, because bridging works too (aka. bridge the red and the black point with tinfoil).

Take a look at the attachment (picture rights by [MENTION=4563980]Flakie[/MENTION]), please let me know if you want me to remove it^^
[Fire TV Original Android Development] Flakie:
Thanks and for adding the circles to the picture.

Sorry I just added an update 3 to my post (we must have posted at same time).

It has finally booted into twrp. I tried rebooting it many times.

The last one I left unplugged from the hdmi and power for some time and it booted up the straight into twrp.

Maybe it was overheated? Not sure about that though.

I think I am going to flash stock or the ready rooted rom and see if ok after that.
[Fire TV Original Android Development] Flakie:
I have created a guide that is aimed at Linux newbies like myself. It details the unlocking and rooting processes and contains some close-up pictures.

I created it as the first time I went to do this I was unsure what to do and lots of searching was necessary to complete all the steps with some confidence.

It also contains some advice and additional information provided by members here. Thanks for that :)

I would be incredibly grateful for anyone that could proofread it, offer criticism and corrections.

When final I will put on a web page somewhere with a html version (it is currently pdf only, from MS Word).

Firestick 4K Unlock and Root

Thanks.

---------- Post added at 12:17 PM ---------- Previous post was at 11:27 AM ----------

Are you sure for the CMD point it is the left-hand part we short to?

I have used macro camera mode to help to attach a really fine pointed bit of foil and am certain there is a good connection to left hand side of CMD but dont seem able to make it work.

Took ages to get this connection perfect so dont want to remove it to test other side just yet.

I am making a newbie guide so want to be certain I have this correct.

Cheers :)
[Fire TV Original Android Development] BLACKPHOENIXRIZIN:
Post in the wrong place, plz see post on pg 90. Thx.

---------- Post added at 01:58 PM ---------- Previous post was at 12:59 PM ----------

Thx so very much 4 the quick reply Flakie. If it worked 4 u, it should work 4 me as well, I'm thinkin I probably did something wrong. So could u walk me through exactly wut u did & how u did it plz. And which did u download & use? Did u use the iso file or the zip file or both? I so want my fire stick rooted.
[Fire TV Original Android Development] Flakie:
I downloaded Rufus from here (the top file, not the portable one):

https://rufus.ie/

I downloaded the ISO from the opening post.

I opened Rufus (the below are my settings but they may have been default. I cannot remember now).

I selected my usb device.

Boot Selection: I selected the fireiso-1.0.0.iso file

Partition Scheme: MBR

Target system: BIOS or UEFI

File System: Large fat32

Clustuer Size: 32

I hit start and when prompted about missing file I clicked Yes.

The files should be downloaded to the Rufus folder.

e.g.

c:\Rufus\rufus_files\syslinux-6.04\

ldlinux.bss and ldlinux.sys

And:

c:\Rufus\rufus_files\syslinux-6.04\pre2-11-gbf6db5b4

ldlinux.bss and ldlinux.sys

Try again and if not working I can zip and upload the files somewhere.

---------- Post added at 02:25 PM ---------- Previous post was at 02:18 PM ----------

Oh BTW, you mentioned ISO or Zip.

The ISO is to make the boot drive.

The zip is to run the exploit once you have the boot linux up and running (download the zip from within the running boot linux os and extract the kamakiri folder somewhere (I put it on the desktop).
[Fire TV Original Android Development] BLACKPHOENIXRIZIN:
Ok, I'll give it another try with ur new info. Will let u know how thingz turned out. Thx a mill 4 the reply & info, greatly appreciate mate, cheerz!
[Fire TV Original Android Development] BLACKPHOENIXRIZIN:
[MENTION=4563980]Flakie[/MENTION] Downloaded & used the newest top version of rufus (3.11) as u suggested, & waz able without any problemz 2 burn the linux (ISO) 2 my flash drive. Waz then able 2 boot into the linux (ISO) file, after that every screen waz unstable & jumping. Have any idea why my screen wazn't stable & wut might be the fix? And also, after I'm in the linux program, where is the (KAMAKIRI) zip file located & how do I get 2 it? Thx.

---------- Post added at 03:55 PM ---------- Previous post was at 03:50 PM ----------

[/COLOR [MENTION=4563980]Flakie[/MENTION] Downloaded & used the newest top version of rufus (3.11) as u suggested, & waz able without any problemz 2 burn the linux (ISO) 2 my flash drive. Waz then able 2 boot into the linux (ISO) file, after that every screen waz unstable & jumping. Have any idea why my screen wazn't stable & wut might be the fix? And also, after I'm in the linux program, where is the (KAMAKIRI) zip file located & how do I get 2 it? Thx.
[Fire TV Original Android Development] Flakie:
Thats good then, so far, so good. I am not the best to hlep with the unstable/jumping screem. I am linux newbie except for some use on my Pi.

The exploit zip is in the opening post of this thread. About 12-13 lines down (Current Version: kamakiri-mantis-v1.2.zip).

I click on it an choose open, not save.

Then when it opens I drag and drop the kamakiri folder to the desktop.

I then right-click the folder and choose the option to run a terminal.
[Fire TV Original Android Development] Sus_i:
You see, the points for shorting were only guessed... considering that picture you see in the OP, without the real hardware in hands.

Months ago, I've measured some parts and since that I'm sure none of the points are CMD or CLK ;)

Could be wrong, but in my opinion is that line the internal power node connection, called: VDDi, used to stabilize the eMMC regulator output to core logics.

Doesn't matter if you short the left or the right red circle (I've made in your picture), since it is the same connection.

Best reliable shorting method (for me) can you see here in this posting.
[Fire TV Original Android Development] BLACKPHOENIXRIZIN:
[MENTION=4563980]Flakie[/MENTION] Also the missing rufus filez I mentioned 2 u earlier, they just magically appeared in user download folder. Where do they go, & how do I get them 2 their proper home? Thx again.

---------- Post added at 04:43 PM ---------- Previous post was at 04:35 PM ----------

Ok Flakie, I give that info a try, will report back with resultz. As alwayz, thx so very much 4 ur help with this project.
[Fire TV Original Android Development] Flakie:
Thanks, but I can hear the whooosh where that went over my head ;)

I redone the connection so it was the same and it worked ok then. I am thinking it was loose at the other end (the earth connection to the frame).

I do like the method in the image. Nice and simple. Will give that a go on the next one :) Should save me a lot of time if it works for me.

[MENTION=5213625]Sus_i[/MENTION]

I had 10 goes at shorting using this method and it worked first time, every time. I will update my guide as this being the easiest and recommended method. Thanks.
[Fire TV Original Android Development] BLACKPHOENIXRIZIN:
When I right click on the (KAMAKIRI) folder I don't have a option 2 run a terminal. Could that possibly be bcuz I'm running windowz & not linux?
[Fire TV Original Android Development] Flakie:
Yes, you need to run the exploit from the boot linux usb you created with Rufus.
[Fire TV Original Android Development] BLACKPHOENIXRIZIN:
Ok, got u Flakie, but like I said previously, when I boot into the linux (ISO) the screen jumpz so badly that it'z almost impossible 2 try 2 do anything! I'm gonna try it again, once I'm in the linux (ISO), how do I get 2 the exploit file?
[Fire TV Original Android Development] Flakie:
Same way as you did in Windows. From the opening post in this thread.
[Fire TV Original Android Development] BLACKPHOENIXRIZIN:
Ok Flakie, leme see wut I can figure out. Be in touch soon. Thx 4 ur input. Peace.:o
[Fire TV Original Android Development] BLACKPHOENIXRIZIN:
Another question Flakie. The rufus folder & it'z filez that showed up on my desk top, do u by chance know where they r suppose 2 go? And do u think that they may have something 2 do with my jumping screen issue in the linux (ISO)?
[Fire TV Original Android Development] BLACKPHOENIXRIZIN:
2 anyone & everyone on this site that may have info on the matter. After having successfully installed the linux (ISO) file on my PC 2 ultimately root my firestick 4K I've run into an issue that I need some help with. When I boot into the linux (ISO) & select the file option 2 boot from my screen startz to crazily & continually jump, even after the booting process is complete & I'm in the linux program it still continuez 2 crazily jump. Anybody have any ideaz wut might be causing this issue? Thx all, peace.
[Fire TV Original Android Development] Mogul345:
Well, I was ultimately successful. Thanks OP for this good work.

The caution about not using tweezers is legit. I thought I was being smart using the tip of a very fine multimeter probe. Still manged to knock off the cap labeled CMD in the picture. But as some other people have said it still seems to work after you knock it off. And it made it super easy to short out the left pad of the CMD cap, so in a weird way it made things easier to achieve. Was able to install Magisk and disable OTAs just fine. If it eventually dies oh well, it's cheap.
[Fire TV Original Android Development] Flakie:
question about using vncserver on this arch linux installation deleted.
[Fire TV Original Android Development] Flakie:
Anyone from the UK tried this OTG splitter (or US etc if available there)?

https://www.amazon.co.uk/gp/product/B072Z9QHYR/

I have no access to ADB through it. Keybpad works to get me into TWRP but ADB does not.

No devices are listed.

Same when booted normally and if I restart the 4K into recovery.

Device not listed at all. Only way is through IP when booted up fully.

If I remove the OTG then the device is listed when booted normally and in recovery and I can perform the usual ADB actions.

I have noticed in Win10 there is no nice USB connect notification sound when I plug it in with the OTG l;ike there is with the cable alone.

Dead device (its my first OTG)?

Need to know before I return/bin it.

Cheers.
[Fire TV Original Android Development] Sus_i:
That OTG cable is fine :good:

Unfortunately, ADB doesn't work at all over OTG cables...
[Fire TV Original Android Development] Flakie:
Ah OK thanks.

That's a shame.
[Fire TV Original Android Development] chinkster:
Does anyone know why when I use a otg cable and also try to use a hub then connect a USB receiver mouse, it won't detect the pointer. Unless I plug it in directly to the otg cable without the hub, then it will work
[Fire TV Original Android Development] Sus_i:
Unpowered hub? Sounds like there isn't enough power...
[Fire TV Original Android Development] chinkster:
oh really didn't even think about that. i tried it before and it was able to work before without me powering it up with a separate power source. i'm not even sure if i am able to power it up like that but i do see a micro-usb port on the hub as well
[Fire TV Original Android Development] Flakie:
Not sure, but I thought I read it won't work in a Virtual Machine?

I just tried in in virtualbox from a Win10 PC and the process nearly completed fully.

It finished sending and writing recovery but then gave an error after that.

For the final part of the script that usually takes 2 seconds to complete.

The final reboot command maybe?

It took about 10 minutes to complete in the VM as apposed to a couple of minutes or so on my laptop.

I can live with that if the flash is working OK.

It is all working but hard to tell if process is good as the stick had been flashed already and I wont have another to test for a couple of days.

Has anyone else had any luck with a VM?

The below is a screenshot on my laptop using normal flash with USB drive boot media.

[IMG="Normal Flash"]https://flakie.co.uk/downloads/normal-flash.jpg[/IMG]

The below is a screenshot on a vm on my PC:

[IMG="VM Flash"]https://flakie.co.uk/downloads/vm-flash2.jpg[/IMG]
[Fire TV Original Android Development] Sus_i:
Can work too, but nobody cares, since booting the ISO as a live system is well tested.

A VM is a bit tricky. Each boot stage (like the bootrom, preloader, fastboot and so on) has its own usb vid/pid numbers and you have to make sure all of them are granted to the VM, not to the host.

That is your problem at the last picture, the stick does a reboot, the vid/pid changed and the error pops up because the stick is connected to the host.
[Fire TV Original Android Development] Flakie:
H'mmm this person cares ;)

Space is a premium here and I have been doing this with a laptop on the floor. Chronic back ache too so its not helping that.

Was going to buy a USB hub for my PC where I can work in a little comfort (not a lot though) but that is more clutter for my desk.

I have lots of these sticks to manage and they are adding at at least 2 a week so if I can do the initial setup in some comfort a VM is definitely for me.

No rebooting the PC each time either. Plus I can save the state of the VM whereas I had no luck with making the ISO work with a persistent partition at all.

Plus I have terabytes of stoarge space available for the backups.

So yep, I care :)

I will test with a fresh stick over the weekend.

But thanks very much for the info. Always interesting to read your posts.

Fingers crossed, for me at least, the VM works.
[Fire TV Original Android Development] BLACKPHOENIXRIZIN:
PICZ

Can someone tell me how do I place picz in posts? Thx, peace.:)
[Fire TV Original Android Development] Michajin:
Exactly... Just follow the directions!!!!
[Fire TV Original Android Development] Flakie:
Childish comments removed (I was having a bad day).
[Fire TV Original Android Development] Michajin:
ok, so how is this innovation? It takes all of 5 minutes to make a live disk and follow the directions? When you have a lot of people following many different paths and add a lot of variables that people do not understand. Just because it works does not mean it was the easiest or best way. Great, you got it to work good for you! Are you going to troubleshoot others who may not have the right drivers installed? Might be running a different VM? You posted yourself about an issue! No one here is being paid, unless you donate? Have you donated to the cause that created this? It is about following the directions... A live disk was created for in people who have issues. A VM takes far longer to install, so are you helping or contributing to more confusion? No response is needed, just saying, congratulations, you did it!