yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] rbox:
Installing Magisk should already be installing Magisk Manager for you. It's required to use Magisk I believe. But like the quote you pasted says "Don't flash boot/recovery images from FireOS". It says nothing about installing Magisk manager.
[Fire TV Android Development] urbanman2004:
Ok... So w/ all that being said, after everything is said and done, will this exploit/root procedure definitively unlock the bootloader of the 4k firetick device?
[Fire TV Android Development] Sus_i:
You see, the mtk boot process boots only signed images on consumer devices. It definitively can't be unlocked at all. ;)

The exploit uses bugs in the SOCs bootrom and in LK, makes the preloader thinking it's running on one of the rare unlocked developer devices. On this devices running unsigned images is a thing and therefore loading unsigned twrp is possible with that exploit. Magisk.zip works fine but you have to sideload the Manager App to get it working. You can't software brick that stick, as the bootrom can't be patched, it's burned into the SOC.

Anyhow, that's what I think at this time about how the exploit works, can't tell in detail, as I'm waiting for the promised writeup from xyz :p
[Fire TV Android Development] Velcro31:
I flashed 6.2.6.8_r1 after opening and rooting my newly bought 4k yesterday. I have the same "there's an internal problem with your device contact your manufacturer for details" error when i boot up. I'm not to troubled by it, just wanted to let you know. Thanks for maintaining this!
[Fire TV Android Development] ChronoWerX:
Hi, I do that and all is working perfect, like Netflix, Kodi, Youtube. But when I start a film or something on Amazon Prime Video, is loading and loading, and after few minutes it says my connection is slowly and it loading infinte. It's not a Amazon or network failure. On PS4 it works perfect and with 6.2.6.6 I have no problems.

Any solution? I wiped cache, install again and so on.
[Fire TV Android Development] tsynik:
Probably best solution is to flash stock OTA with 6.2.6.6 (update-kindle-mantis-NS6266_user_2292_0003054040196.zip) + Magisk and stick with it, if it works for you. I don't have prime so can't comment.

---------- Post added at 08:25 AM ---------- Previous post was at 08:24 AM ----------

Yes, it is.

---------- Post added at 08:27 AM ---------- Previous post was at 08:25 AM ----------

It's common issue with prerooted 6.2.6.8. Reflash stock OTA + Magisk from TWRP without wipes to fix.
[Fire TV Android Development] ChronoWerX:
Can I downgrade so easy? Have you pls the link for me?
[Fire TV Android Development] tsynik:
Here it is:

https://d1s31zyz7dcc2d.cloudfront.n...dle-mantis-NS6266_user_2292_0003054040196.bin

Just rename it to .zip after download.
[Fire TV Android Development] ChronoWerX:
After playing a little bit doctor, I found the problem.

Install 6.2.6.8 Prime Video works. Now install Magisk 20.1 for root, etc and Prime Video don't work.
[Fire TV Android Development] tsynik:
Maybe you need to add it to MagiskHide list on Magisk Manager. Also, it can detect and fail on Xposed Framework (if installed) - this one can't be hided from apps.
[Fire TV Android Development] Masterofchicken:
Can I just update to 6.2.6.8 through magisk because I'm unable to connect my PC to control twrp ?
[Fire TV Android Development] brosmitch:
magisk update

Well I think i've done it ! Just looped my Firestick after upgrading Magisk in Magisk (I know not supposed to do that!) .... Now looping at the firetv logo on black screen ,,, unable to get to recovery.

any suggestions ? tried the usual trick with keyboard pushing control alt menu and printscreen... not getting anywhere.

thanks for the help!

EDIT: got out of it :) had to do the full rooting procedure , finaly got TWRP re-installed image and new version of Magisk. Voilà!
[Fire TV Android Development] Phe0nix_:
Because the .iso i had to boot my PC to was named fireiso-1.0.0.iso i had thought when it was posted "Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.) "

I though it meant there were images available and not to flash them from the ISO i was booted into but was safe by other methods. I didn't realize when i was in the Magisk Manager

and was notified updates were available and once i hit update and install that it was going to write the images the post refers to.

Thank you for your post for the TWRP commands as i don't know linux. I was able to short the device and install the exploit package again and flash the rom to correct the

bootloop my device was in. Only lost 20 min or so .

Q1. By the way can you recommend an app that will allow me to boot into recovery. I want to get rid of Magisk Manager so my kids don't do what i did.

Q2. In your example you referenced to pre-rooted rom version 6.2.6.5 and because rbox states since 6.2.6.6 Magisk is included and because i was flashing 6.2.6.8

i didn't install Magisk-v19.3. Would you agree i didn't need to run that command twrp install /sdcard/Magisk-v19.3.zip ?
[Fire TV Android Development] Sus_i:
IDK. You can boot into recovery with adb shell, command is 'reboot recovery'

If you don't need root access, uninstall the manager app (in settings or with adb).

Since Magisk is necessary to avoid SELinux and/or dm verity problems, I would vote for the magisk.zip flashing... i.e. if you touch the system partition (edit a file or whatever), you may get a bootloop without a flashed magisk.zip. But if I remember right, the magisk.zip flashing is also integrated in the latest prerooted rom, you're right just to skip this command. :good:
[Fire TV Android Development] Phe0nix_:
Working on my 3rd one just because it's there and i want to climb the mountain. I skipped it on my 3rd stick and they are all running the same version of Fire OS ( 6.2.6.8 ) and it's not in

a boot loop and i can run command reboot recovery and get back into TWRP.

I want to flash Magisk while in TWRP from command line. I pushed the latest version ( Magisk-v20.2 ) to /sdcard/ and but i can't get it to install. I must be using the wrong commands.

I ran these commands :

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

echo "--wipe_cache" >> /cache/recovery/command

reboot recovery

Still no Magisk , going to try the following command : twrp install /sdcard/Magisk-v20.2.zip

Update:

Yea i'm sure you already know. That twrp install command did it. Odd that it was installed on the other two devices and i didn't type that twrp command.

I guess the above command echo "--update_package=/path/to/zipfile" > /cache/recovery/command is what installed it idk ?
[Fire TV Android Development] Sus_i:
Did you edit the cache recovery command like this?

echo "--update_package=/sdcard/Magisk-v20.2.zip" > /cache/recovery/command
[Fire TV Android Development] Phe0nix_:
while in the directory Magisk-19.3.zip was located in i opened a terminal and copied the file to /sdcard/

adb push Magisk-v19.3.zip /sdcard/

And so where is said path/to/zipfile i used the location on the device i pushed/copied to and the filename

echo "--update_package=/sdcard/Magisk-v19.3.zip" > /cache/recovery/command

I used Magisk-v19.3 on the first 2 and then found 20.2 on the forums here and used it the 3rd around.

I'm sure that is what it meant. Sorry i pasted the same code from the forum without editing it. I really enjoyed

doing this. I'm thinking about doing a 4th and using my Elgato to post a video because i'm confident i followed

the instructions correctly. I Used a video that was very long with no audio narration and it play faster than

real time and it made it difficult to take notes. The only problem is i capturing both the TV Screen and the PC

at the same time. I would need two capture cards or root 2 more Fire TV Sticks and capture the PC 1st and then

root a 2nd and capture the TV screen .

I guess it's pointless really because Amazon will probable change the hardware.

I would like to thank you again Sus_i for your post showing the TWRP commands to install

the roms. I rooted the Fire TV Gen 1 and 2 but i had a keyboard and here your stuck unless you have a OTG cable

and a USB hub. I've read a lot of your posts and they helped me a lot.
[Fire TV Android Development] Lei_Wulong:
A question for the sake of better understanding:

I unlocked the bootloader and installed TWRP (the routine from here: https://xdaforums.com/fire-tv/orig-development/unlock-fire-tv-stick-4k-mantis-t3978459), then via TWRP I installed Magisk 20.2 (and StickMount). That allows me getting root access when required. So far so good, everything went fine.

Now I wonder, what is the difference of doing that compared to installing the pre-rooted image from this thread? It also contains Magisk, but what else?
[Fire TV Android Development] Sus_i:
addon.d support
[Fire TV Android Development] vetmike:
Link is broken to the 6.2.6.6 image...anyone have a copy?

I'm working on getting rid of the license_error and looks like I need to install that first before going to 6.2.6.8...

Thanks!
[Fire TV Android Development] rbox:
I fixed the link for 6.2.6.6.
[Fire TV Android Development] avdo06:
Great work, I love the look of the launcher.
[Fire TV Android Development] gggirlgeek:
I am wondering this myself. Do we need the ROM for Root or not?

Also, is the ROM advisable currently on v6.2.6.8? I'd like to try it but...

A quote from [MENTION=5213625]Sus_i[/MENTION] Here: "After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen)."

Thanks for your hard work guys. Firestick sucks without it.
[Fire TV Android Development] Sus_i:
You may don't need it for now, in case your stick runs already the latest OS and you've installed magisk...

but if not, its an easy way to update + it adds addon.d support if you need that ;)

The context of my post was that if you update the stick to 6.2.6.8 just infront of an unlock attempt, it doesn't make sense to apply the same update twice... waste of time ;)
[Fire TV Android Development] gggirlgeek:
Already flashed it. :) Works great so far.

I thought this Rom would overwrite my old setup but it didn't. All my apps and settings are still intact but I now have root (verified.) Very nice! I didn't expect that.

All I had to do, after unlocking the boot loader and flashing this ROM, was install the Magisk Manager apk, open it and grant SuperSu for "shell", then disable OTA updates via ADB commands.

You should tell folks that they can backup/restore their Data partition in TWRP before flashing, JIK they need to restore factory settings. Didn't know this Rom would work with my old Data.

Now I will commence screwing everything up to my hearts content. :D

Thank you!
[Fire TV Android Development] funnypanks:
I finally updated the firmware to rooted 6.2.6.8 from rooted 6.2.6.6, and now on startup I get a dialog box that says:

"there is an internal problem with your device. contact your manufacturer for details"

Any idea what this could be? The box seems to work fine thought.
[Fire TV Android Development] theflashfromthecw:
Delete the old build.prop file in /vendor/build.prop because it contains old 6.2.6.6 files. Then reboot. This fixes the "There is an internal problem with your device. Contact your manufacturer for details"
[Fire TV Android Development] funnypanks:
Thanks, can I just delete it, or do I need to delete it and reinstall the firmware or something? I remember back in the day the device wouldn’t start without a build.prop.
[Fire TV Android Development] theflashfromthecw:
You can just delete it. No need to reinstall anything. This is a different build.prop with the information relating to the past update. It's responsible for the fingerprints and system version data inside the build.prop in the vendor folder so there's no need to worry about it not starting. It's only if you delete the build.prop in /system which is different from the one found inside vendor
[Fire TV Android Development] funnypanks:
Thanks, worked perfectly!
[Fire TV Android Development] avdo06:
How can I return to stock? I'm selling mine.
[Fire TV Android Development] theflashfromthecw:
Amazon released a new version for the Fire TV Stick 4K. Fire OS (6.2.7.1) (3590962564). Hey [MENTION=3991724]rbox[/MENTION], how long does it usually take to push updates out to the Fire TV devices after the original update has been available? Thanks!
[Fire TV Android Development] michael.santos:
There is an error in the update script from 6.2.6.8 where [MENTION=3991724]rbox[/MENTION] is trying to write the "system" to "vendor"... ;)
[Fire TV Android Development] chinkster:
Is there even anything different?
[Fire TV Android Development] Michajin:
post #147 -

Delete the old build.prop file in /vendor/build.prop because it contains old 6.2.6.6 files. Then reboot. This fixes the "There is an internal problem with your device. Contact your manufacturer for details"

it works... see post 149 also...
[Fire TV Android Development] Sus_i:
Thanks, I've updated that posting...

Best regards^^
[Fire TV Android Development] johnny_cage:
deleted
[Fire TV Android Development] Michajin:
If anyone is interested in updating to 6.2.7.1. I flashed the update in TWRP, flashed magisk (20.3) again and I'm updated. All settings and blocked apps do not change. I flashed over 6.2.6.8 without issues. Update file located in this thread....

Official Stock Image for Fire TV Stick 4K (6.2.7.1, 3590962564)

https://xdaforums.com/fire-tv/general/official-stock-image-fire-tv-stick-4k-6-t4059777

Credits to [MENTION=10414053]Skel40[/MENTION]
[Fire TV Android Development] Retch_100:
What to wipe before flashing? Is this a full image so i can wipe all partitions before flashing?
[Fire TV Android Development] Michajin:
what are you on? i didn't wipe anything coming from 6.2.6.8 prerooted, just flashed it over it and flashed magisk.
[Fire TV Android Development] Retch_100:
[MENTION=4914529]Michajin[/MENTION]

I don't know on what i was on, but i've got this problem, maybe it is better to post the thread instead of explaining it again here.

https://xdaforums.com/fire-tv/help/fire-tv-4k-to-set-t4070841/post82085631#post82085631
[Fire TV Android Development] Michajin:
It is possible your device has a OTA in the folder for update. (folder = root>data>ota and root>data>ota_package). You should still have access to TWRP, so from there (make a backup first) wipe system data and cache, install 6.2.7.1 (and magisk if you want root, but not required and you can add it later if you want). Then reboot. It will take 5-10 minutes to boot up to go through the initial setup. This is where i would start. I screwed up my first try with a bad OTG that caused me to have to wipe system and flash 6.2.7.1. If you can connect with adb, i would disable the OTA with

adb shell pm disable-user --user 0 com.amazon.device.software.ota

adb shell pm disable-user --user 0 com.amazon.device.software.ota.override
[Fire TV Android Development] Retch_100:
I managed to install the 6271, but the same error occurs. I don't have adb access during boot/ in the setup screen.

Is it possible to pass the updater or set it up without network access?

The ota folders were empty btw
[Fire TV Android Development] Michajin:
did you wipe anything?

I don't know if there is a way around it anymore.
[Fire TV Android Development] Retch_100:
I wiped everything. Seems that i have to wait for lineage to release ;)
[Fire TV Android Development] Michajin:
"wiped everything" can you give more details? You could be waiting for a LONG time for lineage. I dont think anyone is actively working on it and lineage for the stick is very buggy.

You can always take a full back up from one of your other 4k's, and restore it then wipe data and cache.
[Fire TV Android Development] Retch_100:
I attached a photo. TWRP is only installed on the broken one, because i don't want to break the warranty of the others.
[Fire TV Android Development] Michajin:
When you get the error about the update "after language and network setup" is it after a reboot or just pop up. Maybe it is looking for stock recovery...
[Fire TV Android Development] Retch_100:
When it searches for an update after the language and wifi setup the error appears, maybe i can find any information looking into wireshark.

I got it used, maybe it has to do sth with it.
[Fire TV Android Development] Michajin:
It connects to Wifi then looks for an update and errors? almost making me think it might be blacklisted (if you bought it used)...
[Fire TV Android Development] passionicon:
Hi guys, I'm new to 4k firestick rooting and all that. But I'd love a summary of the benefits. Will i get free tv or something?
[Fire TV Android Development] Michajin:
No free TV, no piracy, nothing illegal, it will void your warranty if amazon knows you did it. The main benefits i get is tweaking it to work better with some of the mods. You can make backups of the rom. You can change the CPU to performance. You can install the play store (although i have not seen it stable yet). Installing 3rd party apps does not require root. You can install adblockers (but doesnt block everything). You can change launchers. Basically it makes the device yours to change, but with this you can also brick it. Eventually someone will develop a custom rom (likely lineage 14.1 with tv launcher) and you could install it. I have not seen anyone cause a permanent brick. Basically it gives you freedom on the device. Each person will have a series of benefits for rooting.
[Fire TV Android Development] rbox:
Mine is saying "up to date" on 6.2.6.8 so it's possible Amazon pulled the 6.2.7.1 update. I will not be releasing a rom for this until I know they're pushing it again.
[Fire TV Android Development] Bluetoth10:
Sorry for offtopic. [MENTION=4196591]sconnyuk[/MENTION], were you able to flash and use 4k sticks blocked by Amazon? Pls see PM
[Fire TV Android Development] sconnyuk:
Yes but its not straight forward to setup. When it is set up its fine apart from the use of Prime video.

If i have time later ill post the process i used.
[Fire TV Android Development] Donphillipe:
I was going along fine after initially unlocking, and installing TWRP via the unlock procedure using the USB iso stick. I got TWRP up and backed up my system. No one would respond on what to back up so I backed up everything (selected all the buttons). Then I installed Magisk 20.3 and restarted. I then installed AFTV tools and rebooted OK. I installed Kodi and other apps and everything has been working several days.

Todayl I tried to use the Leanback "move icon function" with a long hold of the Learn keyboard(?) icon and my system started rebooting and kept rebooting in a loop, still stopping at TWRP and continuing after the timeout each time. I tried to restore all the directories that I had backed up and first I received the message:

Failed to mount '/storage' (Invalid argument) and it locked on the initial white over black screen.

So I went through the entire unlocking procedure the second time and successfully got back to TWRP again.

This time when I tried to restore I got the message:

Failed to mount '/vendor' (Invalid argument)

Then I tried to load the mantis-6.2.6.8-rooted_r1.zip via the Install option of TWRP and all through the output, the error repeated over and over

Failed to mount '/vendor' (Invalid argument)

So for now it looks like I am bricked.
[Fire TV Android Development] Michajin:
I downloaded 6.2.7.1 and just flashed it. Flashed it right over 6.2.6.8 prerooted rom. I didnt have any issues. I am not sure, seems like if you are flashing back ups you need to do the full images for system and vendor. I could be wrong, but i will test it. But if you want to flash the full update here is the link. I actually bricked mine last week, wiped system,data,cache and flashed 6.2.7.1 and it booted right up. That is what worked for me anyways... here is a link to the file for the full 6.2.7.1 ..

https://xdaforums.com/fire-tv/general/official-stock-image-fire-tv-stick-4k-6-t4059777

If you want to test it on your bricked 4k. I am assuming it still boots into TWRP with a OTG?

I did find this bit on vendor image and system image -

NOTE: When backing up or restoring stock ROM (or any other ROM that has dm-verity enabled) make sure to select "System Image" instead of "System" (And "Vendor Image").

Not sure it that is relevant to the issues here...
[Fire TV Android Development] @Bill_Dollar:
It does and I can't for the life of me determine how to get the .zip onto the stick. Adb sideload isn't recognized. How do you transfer the .zip file to the stick? Thank you very much for the help btw.
[Fire TV Android Development] Michajin:
Do you have a OTG? With a OTG you can use a flash drive, otherwise you can probably sideload it. Do you have access to a OTG or can you get into TWRP?
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] haky 86:
Screenshots

Reserved, check my own screens.
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] Mark455:
suuuuuper smooth:svetius: thank u
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] haky 86:
22/10/2019

22/10/2019

Fix Camera.

Fix Dual SIM.

Fix Internal Storage.

Fix Screenshots.

aosp_figo-android-10.0-22102019-emui9.x-by-haky86.zip
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] Billabomb75:
Imma wait till Offline Charger works and fingerprint works...
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] Billabomb75:
What is meant with the offline charger
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] haky 86:
Doesn't show charging status while is turned off.
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] Bassman's:
Great progress with resolving known issues, however, I will wait for the fingerprint fix. Btw, how is battery life?
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] haky 86:
seems good, I can't tell my review because each one of us have different opinions.

BTW, NFC has been fixed I hope for fingerprint too. check my screenshot attached below.
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] Billabomb75:
Okay i want to know do i put this on ?
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] haky 86:
** New Progress **

Screen locked.

Scanner Fingerprint.

check screenshot below.
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] Billabomb75:
Does the bootloader need to be unlocked in order to work ?
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] haky 86:
Yes, I'll write a guide for debranding and unlocking bootloader in a separate topic under guides section.
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] Billabomb75:
Thank you, i currently have the FIG-LX1 C02
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] haky 86:
the C02 boot only GSI, you have to be on C432 to boot my roms too.
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] Billabomb75:
GSI ?
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] haky 86:
27/10/2019

27/10/2019

Android 10.0 R9

Fix NFC.

Fix screen lock.

Fix fingerprint option in security but still there are issues with enrollments

aosp_figo-android-10.0-27102019-emui9.x-by-haky86.zip
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] Billabomb75:
How do i rebrand my phone to C432
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] mortezaali:
Hello

Is this for FIG-LA1???

Does it support fig-la1???
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] haky 86:
it should boot in theory but I'm using C432.
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] mortezaali:
I have C185 ....

if I flash a C432 , can I use this rom on my fig-la1?

---------- Post added at 08:06 PM ---------- Previous post was at 07:50 PM ----------

I have a fig la1 with stock emui 9.1.0.121(C185)

if I want to flash this rom what should I do?

is it possible?
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] haky 86:
I post the steps in the main post.
[Huawei P Smart ROMs, Kernels, Recoveries, & Other ] haky 86:
29/10/2019

Fix Gestures.

aosp_figo-android-10.0-29102019-emui9.x-by-haky86.zip

for Fingerprint and offline charger it is depend from GSI developments so all we have to is sit and wait.