yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] hk73:
Fire iso (xFce 4.14 portable) bug

Systems frezees requires reboot when click on hardware brightness button.....? That's crazy bug in fire iso (xfce 4.14 portable)
[Fire TV Original Android Development] hk73:
Anyone pls suggest List of apps for rooted lineage

For :-

1) Easy navigations & app drawer etc

2) casting

3) Bluetooth sharing,

4) screen in portrait mode for mobile version apps

5) volume control with fire remote

6) others (Browsers, live TV, utilies etc.)
[Fire TV Original Android Development] ktjensen:
is anyone doing this ROOT process as a service if you mail the firestick to them? Cant really see the capacitor that needs to be shorted. Just the quick install of TWRP under the fireOS *.3 with return postage provided.
[Fire TV Original Android Development] Bertonumber1:
Hi there, I had messaged you offering to help you out, however it would be better for you to carry this out yourself as it is really easy to do, once you prise the shield off to get to the board, you only have to fold a small piece of tinfoil up and wedge it into the curved side at the top as long as there is about a mm protruding onto the board you're good to go.

Honestly it is by far the easiest short to carry out. I will try and locate a better diagram for you and mark it out.
[Fire TV Original Android Development] 0815hoffi:
.. 4k
[Fire TV Original Android Development] Bertonumber1:
[MENTION=10401573]0815hoffi[/MENTION] Yes definitely the easiest stick to short unlock and root,

The hardest part was plugging in the MicroUSB I think [emoji106] Hopefully this helps the member out.

if they really want it # and struggling I will do it not a problem, I have a few mantis already unlocked on latest Debloated pre-rooted with updated magisk and launcher, plus bromite webview etc.
[Fire TV Original Android Development] cyberfrog77:
Problem starting the fireiso

Hi everyone!

i need ur help. i´m stuck right in the beginning of rooting the fire tv stick.

everytime i try to run the fire iso i get this (see pictures) . can anyone help me?

what am i doing wrong?? i have no clue
[Fire TV Original Android Development] totbl:
Hi! Anyone get anywhere unblacklisting the 4K sticks? Mine is just a paperweight after buying it new from Amazon. They said it was reported lost and I was not able to fix the situation with them.
[Fire TV Original Android Development] Bertonumber1:
Yeah if you do the unlock process, and install the magisk ATV addon module it should bypass Amazon altogether, even ftvlaunchx on a rooted firmware and custom launcher should work..... then you can just sideload or download whatever apps you need via easyfiretools or pc.

Note: you won't have access to appstore for things like prime. But it saves you a waste of money and let's you remove your doorstop and close the door
[Fire TV Original Android Development] test10000001:
how is it possbile to remove twrp? i need to send it to amazon :)
[Fire TV Original Android Development] Sus_i:
You need a stock update .bin file.

It must be the same OS version, that is installed on the stick.

If you can't find a bin file for your OS version, grab one available (rename it to .zip) and flash it with TWRP.

Extract the boot.img out of the bin file.

You need fastboot/adb drivers on your PC.

Boot into TWRP, connect with adb to the stick and type:

adb shell reboot-amonet

or use the button in TWRP to boot unlocked fastboot.

Then check with:

fastboot devices

if there is any device.

If yes, type:

fastboot flash boot boot.img

Watch out for errors.

If you need to factory reset the stick, run:

fastboot erase userdata

then

fastboot reboot

Edit: Just forgot, if you have done any modifications on /system, you have to flash the stock update with TWRP infront a boot.img restore.
[Fire TV Original Android Development] SweenWolf:
adb reboot recovery

Then

adb shell reboot-amonet

And the other are same

I don't know if you rooted after unlocking or not, but if you aren't rooted then you first need to open recovery, then from there open hacked bootloader and then revert to stock, by using the described commands
[Fire TV Original Android Development] Sus_i:
Thanks, forgot the TWRP shell.

Whats do you mean about rooted or not? Isn't that all the same?
[Fire TV Original Android Development] SweenWolf:
I don't know if any prerooted rom has binary present or not.

Other is simple, you need TWRP to open "hacked BL", and you need adb to open TWRP, because we are doing everything from PC.

So yeah, rooted or not everything is same.
[Fire TV Original Android Development] Sus_i:
Yeah, that is ofc the best. :good:

Although some guys like to play with TWRP via an OTG cable + mouse and they claimed that an exchange of the otg to an usb data cable works, if you change it quickly enough after the 'boot unlocked fastboot' button press :p

Another (uncomfortable) way to boot unlocked fastboot, from rooted fireOS for example, is to write

FASTBOOT_PLEASE

to MISC partition.
[Fire TV Original Android Development] alias100:
How can i flash the Original update.zip without TWRP?

After removing TWRP, i can't make a factory reset. The Stick only remove the User Account, but don't erase the data.
[Fire TV Original Android Development] Skel40:
There's no way to flash the .zip without TWRP. Unless you reboot to the hacked fastboot and type in fastboot flash system update.bin but it bricks the whole device so here's what I did to successfully remove TWRP on two 4k's that I have. Firstly install the stock image non-rooted .bin on Windows, make sure to have ADB and Fastboot installed on Windows, plug in your 4k to your conputer, make an ADB connection and reboot into TWRP and type in adb shell, twrp wipe /system, twrp sideload, ADB sideload update.zip (rename to .zip), let it continue then adb push the boot.img (extract the .zip) and flash the image to the boot partition, after that make a backup of the boot then restore. Once you finished doing that type in adb shell reboot-amonet and fastboot flash boot boot.img.

The reason why restoring the boot.img and backing it up in TWRP is simply due to TWRP automatically patching the boot patch for it to continue using TWRP. I may be wrong. This occurs each time you flash a .zip
[Fire TV Original Android Development] alias100:
Okay, thank you. I will try it.
[Fire TV Original Android Development] alias100:
How can i get a ADB USB connection with adblink ? I only get a connection over Network....and the Network doesn't work in TWRP...

THX
[Fire TV Original Android Development] SweenWolf:
Don't know about adblink (never used it)

But if you connect your stick directly to your pc via usb then your pc will detect it without any problem

To check

adb devices
[Fire TV Original Android Development] alias100:
It doesn't work.

The adb Devices list is empty.

Adb usb gives me an error:

Device '(null)' not found.
[Fire TV Original Android Development] 0815hoffi:
Use Amazon Cable, maybe you use a OTG cable.

OTG not works with adb.
[Fire TV Original Android Development] fourlans:
I'm trying to run the exploit using a VirtualBox Virtual Machine and I'm receiving the error 'device reports readiness to read but returned no data (device disconnected or multiple access on port?)'. I've executed the exploit before using exactly the same setup with no problems. Does this error indicate that that I'm not shorting the device properly or something else ?

I'm having to do it again because my FireTV froze up last night and now only displays only the FireTV logo.

---------- Post added at 11:47 AM ---------- Previous post was at 11:47 AM ----------

I'm trying to run the exploit using a VirtualBox Virtual Machine and I'm receiving the error 'device reports readiness to read but returned no data (device disconnected or multiple access on port?)'. I've executed the exploit before using exactly the same setup with no problems. Does this error indicate that that I'm not shorting the device properly or something else ?

I'm having to do it again because my FireTV froze up last night and now only displays only the FireTV logo.
[Fire TV Original Android Development] SweenWolf:
You dont have short again, just connect your stick to pc and run

fastboot-step.sh
[Fire TV Original Android Development] fourlans:
using a fresh piece of foil for shorting, I managed to run the exploit to the end and then went onto rooting the device. 'adb devices' showed that the firestick was attached, i rebooted into recovery and installed Magisk, wiped the cache and dalvik, and used 'reboot -p' to check for root. After reboot I got errors from 'shell' & 'su' commands and then discovered that the device was no longer visible to adb devices nor fastboot devices. It looks like I'm back to square one. i.e. A black screen with the FireTV logo displayed. Can you suggest what I should do next ? Do I need to redo the exploit ?
[Fire TV Original Android Development] totbl:
That's great to hear! Can you point me to an easy to follow tutorial for getting that far? Thanks!!
[Fire TV Original Android Development] Bertonumber1:
Not sure if this is allowed so mods please delete if inappropriate and accept my apologies in full.

I would have a look here :

https://docs.google.com/document/u/0/d/1zYtqmf4RfLOkrPyPjf1C0CjAZf_0E1JohIlTyVY5kGs/mobilebasic

And the files here :

https://drive.google.com/drive/u/0/mobile/folders/1GbMTBHuFhwT_uyZaJs0ApsG_RQ5Wg_7F

If you can't get into settings or menu then I would try following the instructions in the OP first and then the above.
[Fire TV Original Android Development] KR_83:
Bootloop after flashing prerooted stock image and updating Magisk

Hi,

I opened my Fire 4K and shortened the pin, then I flashed the prerooted Stock Image 6.2.7.1_r1 and booted into FireOS. Magisk Manager informed me, that the prerooted image has Magisk v20.1 installed and there is an update available to Magisk v20.4

So I did update from within the Manager and did a reboot. As I learned afterwards that was stupid, should have downloaded the 20.4.zip instead and installed it via TWRP.

Now I'm stuck in boot loop (dark grey FireTV screen showing for 1 minute, then restarting). I cannot access TWRP, so I tried to start from scratch, opening the case and shortening the pin, but when I run the kamakiri bootrom-step.sh, it never continues but is stuck saying "Waiting for bootrom"

Dmesg also looks strange, it shows the stick is recognized as MT65xx Preloader from MediaTek, saying nothing about Amazon Fire (as I think it should). Please see attachment.

Any advice what I could do? Thanks a lot.
[Fire TV Original Android Development] fodbrothers:
4k firestick

having an issue and would really appreciate help,

so the firestick 4k was blocked by amazon and I cant get passed the initial setup as it asks for wifi info and then tried an update then asks to contact amazon.

I have completed the steps ./bootrom-step.sh and ./fastboot-step.sh

I then went on to do the following using a video I found on youtube

adb reboot recovery

adb push /root/Desktop/Magisk-v20.4.zip /sdcard/

adb shell

twrp install /sdcard/Magisk-v20.4.zip

twrp wipe cache

twrp wipe dalvik

reboot -p (HERE)

adb shell

su

so where it says (HERE) the 4k stick rebooted and I lost adb connection totally I have tried absolutly everything even connecting via ip connection, using just usb, using otg cable with and without power and still nothing.

I have tried multiple things but no connection I have a otg cable and usb hub so I can access twg and get to the terminal

after reading this post I saw this

"""""""""""""""""""""

You can activate ADB from within TWRP terminal:

mount data

echo -n 'mtp,adb' > /data/property/persist.sys.usb.config

mount system

echo '' >> /system/build.prop

echo '# Enable ADB' >> /system/build.prop

echo 'persist.service.adb.enable=1' >> /system/build.prop

echo 'persist.service.debuggable=1' >> /system/build.prop

echo 'persist.sys.usb.config=mtp,adb' >> /system/build.prop

I had to do this to activate ADB as I couldn't get into the home screen as my stick I have is blocked by Amazon. I also had to install magisk and magisk manager for root authorisation. However after doing this you still are required to give permission on screen to anything that connects to it, but I guess you could quickly do it and turn the stick off before it upgrades.

"""""""""""

but as soon as I type mount data it says to fails or is busy.

I haven't got a clue what to do next.

appreciate any help what so ever. and please reply very simply so I can follow steps (dont assume I know anything lol)
[Fire TV Original Android Development] 0815hoffi:
You can activate ADB from within TWRP terminal:

mount data

echo -n 'mtp,adb' > /data/property/persist.sys.usb.config

mount system

echo '' >> /system/build.prop

echo '# Enable ADB' >> /system/build.prop

echo 'persist.service.adb.enable=1' >> /system/build.prop

echo 'persist.service.debuggable=1' >> /system/build.prop

echo 'persist.sys.usb.config=mtp,adb' >> /system/build.prop

+

Delete oobe

rm -r /system/priv-app/com.amazon.tv.oobe

Flash my launcher in twrp

https://xdaforums.com/attachment.php?attachmentid=5104329&d=1601060272
[Fire TV Original Android Development] fodbrothers:
thanks for this reply but as I said before when I type mount data

it says it is busy /dev/block/mmcblk0p13 busy
[Fire TV Original Android Development] 0815hoffi:
Try

adb shell "mount -o rw /system"

In TWRP

Then

Delete oobe

rm -r /system/priv-app/com.amazon.tv.oobe

Flash my launcher in twrp

https://xdaforums.com/attachment.php?attachmentid=5104329&d=1601060272
[Fire TV Original Android Development] fodbrothers:
thanks for your reply

adb shell "mount -o rw /system"

gives an error of

sh: adb: not found
[Fire TV Original Android Development] 0815hoffi:
On twrp?

If yes, dont use otg cable, try with Amazon usb cable.

With otg cable you cant use adb.
[Fire TV Original Android Development] fodbrothers:
I cant access twrp without otg it will not prompt on boot and no mouse to use
[Fire TV Original Android Development] 0815hoffi:
Try

Without adb shell

mount -o rw /system
[Fire TV Original Android Development] fodbrothers:
it says

mounting /dev/block/mmcblk0p11 on system failed: device or resource busy
[Fire TV Original Android Development] 0815hoffi:
Try to flash this in twrp.

adb.oobe.launcher.zip

if this also fails,

Just do the unlock procedure again to access twrp over adb.
[Fire TV Original Android Development] fodbrothers:
that worked really well, it booted up i went to the app that was on thre installed it. it rebooted and now the device is stick on firetv screen. cant get out of it or do anything.

no twrp as it doesnt prompt and cant do a system recovery with the remote as it doesnt do anything.

help
[Fire TV Original Android Development] 0815hoffi:
You must use tv remote over cec to pair firetv remote.

Remote pairing is a part of oobe......

You must press Homebutton to set default launcher.

Try to access over adb.

If you cant boot

Do the unlock procedure again to access twrp.

Reflash rom.

---------- Post added at 06:44 PM ---------- Previous post was at 06:36 PM ----------

Or try to use usb keyboard/mouse

I have no Experience with otg.

---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------

If you can boot and have adb access,

Run this to set oobe Donald.

adb shell settings put secure install_non_market_apps 1

adb shell settings put global adb_enabled 1

adb shell settings put global setup_wizard_has_run 1

adb shell settings put secure user_setup_complete 1

adb shell settings put global device_provisioned 1
[Fire TV Original Android Development] fodbrothers:
Thanks for your help I have now shaped it in half. Too much effort and this way I don't waste any more time on it
[Fire TV Original Android Development] matrixddl:
[MENTION=7104332]k4y0z[/MENTION], i am trying to restore to stock by following instructions from this post but unable to remove twrp. I have tried multiple times still no luck.

I was on mantis-6.2.6.8-rooted_r1 and from there i used the stock update-kindle-mantis-NS6276_user_2933_0004396381572 to restore.
[Fire TV Original Android Development] matrixddl:
[MENTION=7104332]k4y0z[/MENTION], [MENTION=10401573]0815hoffi[/MENTION] helped me resolve the issue. Details are posted here.
[Fire TV Original Android Development] totbl:
I've come across that before. And yeah, can't get into settings. Can't even get past the first screen when signing in.

I guess I'll try the OP. I'm really mad at Amazon for not rectifying this but I will try this. I appreciate the help.

Any other info?
[Fire TV Original Android Development] Bertonumber1:
Yeah mate I think this is for the tank only, this is all the info I've had on it, dunno if it works.

---------- Post added at 11:40 AM ---------- Previous post was at 11:07 AM ----------

That is normal, run adb reboot recovery.

To check if you still have recovery, if you do :good: just do a full wipe and reflash rom, magisk again. If not you'll have to do unlock process over

Please always follow OP to the letter guys. A guaranteed brick will happen if you update magisk ramdisk via the magisk app. Always update to the latest by flashing magisk zip in TWRP
[Fire TV Original Android Development] KR_83:
Didn't have adb connection anymore, but starting from the scratch (including shortening) worked, by stick is running, rooted and debloated now. Thanks a lot, will use TWRP in the future to update Magisk (as a matter of fact, I just updated the 20.1 to 20.4 from within TWRP just now).
[Fire TV Original Android Development] Bertonumber1:
Excellent :good:

Hey so does this bypass registration screen and does it work on tank?

I'm thinking this would be a good to block the updates quicker.

When I flashed 6.2.7.1 it was a mad dash getting to settings to "forget WiFi connection" then stop the stick updating the newest ota.

This would be better as the way I usually do it is.

I boot system up, go through registration and then into network settings, enable adb and unknown sources, disconnect WiFi, install magisk manager, push es file explorer and give it root permission, then I set about deleting the ota apks in system> priv-app.

Does this way do it quicker?

---------- Post added at 05:25 PM ---------- Previous post was at 05:04 PM ----------

What you snapped it?? Why?? You could have sent it to one of the developers who could have unbricked it and used it for testing.

You're stick wasn't dead mate. I had the same before when I broke the clk. But I sent it to a member who fixed it and got it working. Rather someone got use of it than the bin.

Food for thought
[Fire TV Original Android Development] 0815hoffi:
No its not quicker, you need cec remote and its not so simple to enable adb.

Also you need to sideload all Apps.

Should also work on tank maybe , not realy tested
[Fire TV Original Android Development] Bertonumber1:
I tried the oobe bypass you pm, stuck on "unable to update firetv stick, please try again later , if problem continue please contact amazon.com/support
[Fire TV Original Android Development] 0815hoffi:
Have you replaced the oobe.apk and wipe data in twrp?
[Fire TV Original Android Development] Bertonumber1:
Yes I wiped after replacing new oobe with old stripped down oobe via twrp, stick is stuck on screen, I don't have otg atm so will later,

Edit #### it worked bro I wiped, data dalvik, cache rebooted and it went right to launcher ??❤️❤️❤️❤️ we will have to maybe find way to be able to download apps from amazon store, I ran your debloat script and am left with just the ribs??, I will flash pre-rooted again, replace oobe and see how it goes. Thanks again hoffi, excellent work
[Fire TV Original Android Development] 0815hoffi:
??

If you have testet this, maybe you can Post a guide here on XDA.
[Fire TV Original Android Development] Sus_i:
lol, maybe don't debloat the stick like this ;)

Whats your goal about disabling OOBE and such stuff (aside from non-paid blacklisted sticks)?

Maybe I don't get it, but why not let the oobe do its thing, then install the update with TWRP and all is fine!?
[Fire TV Original Android Development] Bertonumber1:
Really just messing around [MENTION=5213625]Sus_i[/MENTION] bored.... You know?:)

Just seeing what you can and cannot do with these sticks but I can't get in now, stuck on unable to update screen as it goes to registration.

I'm now using skel40 Debloated rom but device won't let me adb reboot recovery or show up at all.

I done the unlock process again and flashed same Skel40 Debloated 6.2.7. 3 and its just not happening for me I'm getting this :

"unable to update firetv stick 4k disconnect power and try later or contact us"

Could big A have barred this stick? Or is just this is Debloated so is missing vital apks?
[Fire TV Original Android Development] Skel40:
I may need to take a look at the rom today because removing the ota_certs bypasses the update. If that's the case, re-add ota_certs to the system then try again. I have the list of removed files except for the boot animation below my debloated rom as you scroll down. I think some time I will post a downgraded rom of 6.2.7.1 93 that's able to skip the update screen
[Fire TV Original Android Development] Bertonumber1:
Yeah bro as soon as I flashed pre-rooted 6.2.7. 1 it updated to 6.2.7.6 then I just flashed your rom.

Will stick with launcher manager as some apps not work with hoffis launcher replacement zip, dunno if it's to do with ftv launcher/ home starter being Uninstalled.

:good: great, update screen is a pain but not that much to worry about. But yeah excellent work skel mate ? boot animation is good so are the build prop tweaks (on tank its some improvement too)

Has amazon patched or done any hardware mods to recent 4k sticks does anyone know?
[Fire TV Original Android Development] teephart:
I have unlock my boot loader and installed twrp using the kamakiri exploit method above,

but i'm unable to flash either the stock rom or the prerooted rom.

i did the following:

"adb push update.zip /sdcard"

"adb shell"

"twrp install /sdcard/update.zip"

and i get the following error

# twrp install /sdcard/update.zip

Installing zip file '/sdcard/update.zip'

Checking for Digest file...

[amonet] Load microloader from recovery...

[amonet] Failed to open the recovery device

[amonet] Remove boot patch...

[amonet] Failed to open the boot device

[amonet] Install boot patch...

[amonet] Failed to open the boot device

[amonet] Install recovery patch...

[amonet] Failed to open the recovery device

Error installing zip file '/sdcard/update.zip'

Done processing script file

i have tried different roms.

my device is not booting

Twrp said No OS installed
[Fire TV Original Android Development] Sus_i:
What happens if you try to flash the kamakiri-mantis-v1.2.zip with twrp?

Mounting system and data works?

Are there errors in the recovery log in tmp folder?
[Fire TV Original Android Development] 0815hoffi:
You can also run this commands to disable the Launcher, this is the Same as launcher manager do.

adb shell "pm disable-user --user 0 com.amazon.tv.launcher"

wait 5 seconds

adb shell "pm disable-user --user 0 com.amazon.firehomestarter"

But then you need a app to access the settings.

For this you can my norootsettings app.

But i think in future Updates it will be blocked by Amazon, you can see it on Tank with 5.2.7.6.

There you cant run this commands Because of safety restrictions.

And Yes , with ota-certs rename you are not able to pass the update Screen.

[MENTION=10414053]Skel40[/MENTION]

Maybe you can just replace the oobe.apk from your 6.2.7.3 Rom with the one from 6.2.7.1, should have the same effect.

But this is only such an idea.. ;)
[Fire TV Original Android Development] teephart:
i don't understand your question,

i downloaded kamakiri-mantis-v1.2.zip, followed the instruction and finally boot to twrp.

but i can't flash any rom in twrp
[Fire TV Original Android Development] Sus_i:
What happens if do this:

adb push kamakiri-mantis-v1.2.zip /sdcard
adb shell
twrp install /sdcard/kamakiri-mantis-v1.2.zip

Any errors?