Related
How to get root using Magisk for HU (Allwinner T8) with firmware versions V9.2.2... (Android 7), v9.3.1... (Android 8), V9.4.1... (Android 9)
Denial of responsibility. At one's own risk.
Spoiler: How to root device (you must have factory firmware)...
Your firmware must be installed on your Head Unit (HU).
You must install the Magisk-manager.apk on your HU.
Official Magisk (see Downloads section on the first page).
You must decrypt the file with Kaier support tool
b1604ca8-7757-11e7-906d-3390eed0c0c2 for V9.2.2...
21a4f59a-0a56-11e8-91c9-971a30d57911 for V9.3.1...
c1434ea2-a146-11e9-8113-67e2f4bd95ae for V9.4.1... (Magisk must be v22.1 and above )
Save file as boot.img
You must patched the boot.img file on your HU.
Encrypt patched boot.img with Kaier support tool and save as original filename.
You must do the update using only one this file.
Put the file to the root folder of the usb flash drive.
Connect usb flash drive to HU.
Choose Settings-Car settings-System update and choose USB.
HU will reboot and flash boot.
Spoiler: If you do not have factory firmware,
then take the already patched boot for your firmware version from
Already patched boot.img and ready to update (V9.3.1, V.9.4.1)
Extract the file from the archive to the root folder of the usb flash drive.
Connect usb flash drive to HU.
Choose Settings-Car settings-System update and choose USB.
HU will reboot and flash boot.
Note. You also need to install Magisk Manager.
Spoiler: Tested
Folder V9.3.1_20181130_HC1(HC2)-FD.
Suitable for firmware version
V9.3.1_20181130.092616_HC1-FD. Thanks @laserman123. Tested.V9.3.1_20181128.105007_HC2-FD. Thanks @rocknrod. Tested.V9.3.1_20181109.180710_JP3-FD. Thanks @Goof757. Tested.v9.3.1_20181109.104149_TW2-i140. Thanks @mickchip . Tested.Folder V9.4.1
V9.4.1_20200406 - @****-jones .Tested.
Special thanks to AtlonX2, Weddnessday from 4PDA
Особая благодарность товарищам AtlonX2, Weddnessday с 4PDA
Hello, I have version 9.3.1 with android 8.1
I flash the boot file .img via magisk, I did not find file "21a4f59a-0a56-11e8-91c9-971a30d57911" but magisk produce mi file named "magisk_patched.img"
I send you link to this file PM. (can't post links).
Can you help me, what to do as next steps?
Thank you in advance!
Divisekk7 said:
Hello, I have version 9.3.1 with android 8.1
I flash the boot file .img via magisk, I did not find file "21a4f59a-0a56-11e8-91c9-971a30d57911" but magisk produce mi file named "magisk_patched.img"
I send you link to this file PM. (can't post links).
Can you help me, what to do as next steps?
Thank you in advance!
Click to expand...
Click to collapse
I need exactly what your firmware is.
Show screen shot about device (Like this https://drive.google.com/file/d/1-0buFZ_U0VVGSTE3_2Z060fVg36Msolq)
It is desirable to link to the firmware itself.
Ok, I uploaded pictures on mediafire, I send you link PM.
It seems, my system have some strange cutted android..
OS version:
KC1D01H1-O36-3.0.4.3.5 IVT - 20190311 - 701F
MCU Version:
STM8-20190111-1-KC2-16
Divisekk7 said:
Ok, I uploaded pictures on mediafire, I send you link PM.
It seems, my system have some strange cutted android..
OS version:
KC1D01H1-O36-3.0.4.3.5 IVT - 20190311 - 701F
MCU Version:
STM8-20190111-1-KC2-16
Click to expand...
Click to collapse
This is another modification of the HU.
Other firmware, not the same as discussed here.
I wrote in a PM.
Hi my friend,
Thank you for helping to root my unit.
Since rooting the 'Developer Option' has disappeared.
Do you have any ideas?
Also, my sdcard and usb drives are always mounted as read only. So anything plugged into the usb cables or microsd plugged into unit is read only. The only writable drive is internal memory. Do you have any ideas on this?
I tried editing the platform.xml file but this caused a boot-loop and I had to redo the firmware.
Many thanks for your time.
laserman123 said:
Hi my friend,
Thank you for helping to root my unit.
Since rooting the 'Developer Option' has disappeared.
Do you have any ideas?
Also, my sdcard and usb drives are always mounted as read only. So anything plugged into the usb cables or microsd plugged into unit is read only. The only writable drive is internal memory. Do you have any ideas on this?
I tried editing the platform.xml file but this caused a boot-loop and I had to redo the firmware.
Many thanks for your time.
Click to expand...
Click to collapse
I don't well know Magisk.
Perhaps this is due to Magisk or you are using the NTFS file system.
Try using this https://forum.xda-developers.com/apps/magisk/module-exsdcard-write-access-enabler-t3670428
Or look for a solution here https://forum.xda-developers.com/apps/magisk
[/COLOR]For anyone stuck at Android logo this method works to recover:
1. Format a USB flash drive in FAT32, copy 4/5 firmware files to it.
2. Insert the USB flash drive into the USB device slot.
3. Turn the key to the ACC position.
4. Press and release the Reset button, then immediately turn off the ACC key.
5. Then after 5 seconds, turn the key to the ACC position.
6. The head unit will automatically go into update mode.
Thanks go to someone at 4PDA.net
---------- Post added at 06:50 PM ---------- Previous post was at 06:12 PM ----------
Perhaps this is due to Magisk or you are using the NTFS file system.
This works
Try using this https://forum.xda-developers.com/apps/magisk/module-exsdcard-write-access-enabler-t3670428
laserman123 said:
Hi my friend,
Thank you for helping to root my unit.
Since rooting the 'Developer Option' has disappeared.
Do you have any ideas?
Click to expand...
Click to collapse
Maybe so https://github.com/topjohnwu/Magisk/issues/946
Some ROMs need to have ro.build.type set to "userdebug" (MagiskHide changes it to "user") for Developer options to appear. Maybe this is related? Try turning off MagiskHide and reboot. If that has any effect you can use the MagiskHide Props Config module to change whatever prop it is that's needed back to it's original value.
Click to expand...
Click to collapse
****-jones said:
How to get root using Magisk for HU (Allwinner T8) with firmware versions V9.2.2... (Android 7), v9.3.1... (Android 8)
Denial of responsibility. At one's own risk.
How to...
Your firmware must be installed on your Head Unit (HU).
You must install the Magisk-manager.apk on your HU.
Official Magisk (see Downloads section on the first page).
You must give me a link to the file b1604ca8-7757-11e7-906d-3390eed0c0c2 for V9.2.2...
21a4f59a-0a56-11e8-91c9-971a30d57911 for V9.3.1... from your firmware or a link to the entire firmware.
I'll give you back a link to the boot.img file.
You must patched the boot.img file on your HU and give me back a link to the patched boot.img.
https://youtu.be/xEpT5JbW7lo
I'll give you back a link to the file 21a4f59a-0a56-11e8-91c9-971a30d57911 (for V9.3.1 ...) to the flash.
You must do the update using only one this file.
Already patched boot.img and ready to update
Note. You also need to install Magisk Manager.
Folder V9.3.1_20181130_HC1(HC2)-FD.
Suitable for firmware version V9.3.1_20181130.092616_HC1-FD. Thanks @laserman123. Tested.
V9.3.1_20181128.105007_HC2-FD. Thanks @rocknrod. Tested.
V9.3.1_20181109.180710_JP3-FD. Thanks @Goof757. Tested.
Special thanks to AtlonX2, Weddnessday from 4PDA
Особая благодарность товарищам AtlonX2, Weddnessday с 4PDA
Click to expand...
Click to collapse
Hey this is the link to the firmware that I'm using, http://filefactory.com/file/3782g7m...18 universal car DVD player firmware pack.zip looking to hear from you! thanks! also if you need a sn pm me and ill send one.
anthonym1012 said:
Hey this is the link to the firmware that I'm using, http://filefactory.com/file/3782g7m...18 universal car DVD player firmware pack.zip looking to hear from you! thanks! also if you need a sn pm me and ill send one.
Click to expand...
Click to collapse
Upload the firmware to another file exchanger, for example, google disk or wetransfer.com
Download file size of 500Mb for two and a half hours is a mockery
anthonym1012 said:
Hey this is the link to the firmware that I'm using, http://filefactory.com/file/3782g7m...18 universal car DVD player firmware pack.zip looking to hear from you! thanks! also if you need a sn pm me and ill send one.
Click to expand...
Click to collapse
boot.img
for V9.3.1_20181120.103131_SPX2-FD-1
https://drive.google.com/open?id=1vs2dlUk8f_mL_i7RXaJ8drmo7Fs6VwU2
Need Magisk
hi @****-jones
i'll PM you to send my link file.
Plz help me to Update the given below navi to Android 8 or 9
****-jones said:
boot.img
for V9.3.1_20181120.103131_SPX2-FD-1
https://drive.google.com/open?id=1vs2dlUk8f_mL_i7RXaJ8drmo7Fs6VwU2
Click to expand...
Click to collapse
Hi @****-jones can u plz help me to update my navi to Android 8 or 9. Its 2 GB ram and 16 GB rom. I don't know its manufacturer name. MCu, processor and Other info available in attached image. Plz help
Hello
Hello sir, Plz reply. @****-jones
rizwan400 said:
Hi @****-jones can u plz help me to update my navi to Android 8 or 9. Its 2 GB ram and 16 GB rom. I don't know its manufacturer name. MCu, processor and Other info available in attached image. Plz help
Click to expand...
Click to collapse
****-jones said:
How to get root using Magisk for HU (Allwinner T8) with firmware versions V9.2.2... (Android 7), v9.3.1... (Android 8)
Denial of responsibility. At one's own risk.
How to...
Your firmware must be installed on your Head Unit (HU).
You must install the Magisk-manager.apk on your HU.
Official Magisk (see Downloads section on the first page).
You must give me a link to the file b1604ca8-7757-11e7-906d-3390eed0c0c2 for V9.2.2...
21a4f59a-0a56-11e8-91c9-971a30d57911 for V9.3.1... from your firmware or a link to the entire firmware.
I'll give you back a link to the boot.img file.
You must patched the boot.img file on your HU and give me back a link to the patched boot.img.
https://youtu.be/xEpT5JbW7lo
I'll give you back a link to the file 21a4f59a-0a56-11e8-91c9-971a30d57911 (for V9.3.1 ...) to the flash.
You must do the update using only one this file.
Already patched boot.img and ready to update
Note. You also need to install Magisk Manager.
Folder V9.3.1_20181130_HC1(HC2)-FD.
Suitable for firmware version V9.3.1_20181130.092616_HC1-FD. Thanks @laserman123. Tested.
V9.3.1_20181128.105007_HC2-FD. Thanks @rocknrod. Tested.
V9.3.1_20181109.180710_JP3-FD. Thanks @Goof757. Tested.
Special thanks to AtlonX2, Weddnessday from 4PDA
Особая благодарность товарищам AtlonX2, Weddnessday с 4PDA
Click to expand...
Click to collapse
hi,
i have allwinner t3 p1 android 8.1, will this method work in it?? i want to root my device to install another fm apk
ash0072010 said:
hi,
i have allwinner t3 p1 android 8.1, will this method work in it?? i want to root my device to install another fm apk
Click to expand...
Click to collapse
yep
can you help me root this device?
badwax said:
can you help me root this device?
Click to expand...
Click to collapse
https://drive.google.com/file/d/1GD49e6GHyrpRWaQACT1yY7fXCXgKHvNK/view?usp=drivesdk
Since we're active... any Root access for this HU?
UltraOcta-T8
7.1.2
MCU
5.3.19-7-10-656201-170227
system ver
V9.2.2_20180119.113653_TW2
Thanks in Advance.
EDIT: used V9.2.2_20180201.161555_KED7-mod works. BT may not be working.. But everything else is.. (root). BT sucks on this HU anyways.
Hi,
I would like to use my FireHD 10 tablet with as few connections to Amazon as possible. I have noticed that you can download the stock system updates as a .bin file directly from Amazon however I haven't found a way to install them.
https://www.amazon.com/gp/help/customer/display.html?nodeId=G2JXLC4L34GX73TE
A few tutorials mention booting into recovery and sideloading it there but unfortunately I don't have a sideloading option with my FireHD10.
Is there any other way to install this update? Can you place it an a certain directory so the online updater recognizes this file?
If I remember correctly, with the original Fire HD7, if you copied the update.bin file to the root directory and rebooted it would install the update. I don't know if this works on current models.
anyone23 said:
Hi,
I would like to use my FireHD 10 tablet with as few connections to Amazon as possible. I have noticed that you can download the stock system updates as a .bin file directly from Amazon however I haven't found a way to install them.
https://www.amazon.com/gp/help/customer/display.html?nodeId=G2JXLC4L34GX73TE
A few tutorials mention booting into recovery and sideloading it there but unfortunately I don't have a sideloading option with my FireHD10.
Is there any other way to install this update? Can you place it an a certain directory so the online updater recognizes this file?
Click to expand...
Click to collapse
To access OTA dashboard. You can tap the search box on Fire launcher, type ;dx and hit enter, and select OTA Dashboard.
Hello there, I've never rooted a phone before but would love to try it with Android 12 finally coming out as stable on the OnePlus 8 Pro. So as a complete noob, can anyone walk me through it, or does anyone have a handy thread that takes me through all of it? Thank you!
Same method with OOS11 (other thread), u need full OTA OOS 12 to detached the boot.img and patch it with magisk.
- Or easier just on OOS11 rooted => update to OSS 12 (after install finished, dont reboot, go to magisk select install to inactive slot, now reboot)
dangtoi1993 said:
Same method with OOS11 (other thread), u need full OTA OOS 12 to detached the boot.img and patch it with magisk.
- Or easier just on OOS11 rooted => update to OSS 12 (after install finished, dont reboot, go to magisk select install to inactive slot, now reboot)
Click to expand...
Click to collapse
Thank you! Although as I said I'm very new So if you could explain in a biiiit more noob friendly words, that would be appreciated!
andylmfao said:
Thank you! Although as I said I'm very new So if you could explain in a biiiit more noob friendly words, that would be appreciated!
Click to expand...
Click to collapse
As i know, there is still no downloadable full OTA file for stable OOS 12,
then root method is root at OOS 11 then update after.
to do that, imo, u need to find read and research some old thread to know about that phone before.
its easier than someone will write here for you.
dangtoi1993 said:
As i know, there is still no downloadable full OTA file for stable OOS 12,
then root method is root at OOS 11 then update after.
to do that, imo, u need to find read and research some old thread to know about that phone before.
its easier than someone will write here for you.
Click to expand...
Click to collapse
Ah okay, thank you! Do you know how long it usually takes for an OTA file to come out? Or, if you could, help me through going back to OOS11, rooting it, and then updating to OOS12 and keeping root?
andylmfao said:
Ah okay, thank you! Do you know how long it usually takes for an OTA file to come out? Or, if you could, help me through going back to OOS11, rooting it, and then updating to OOS12 and keeping root?
Click to expand...
Click to collapse
I posted the patched boot img from latest OO12 Ota to another thread.
Flash it via fastboot and your are good.
BootIMG-Magisk24.3_IN2025_11_C.11
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
xtcislove said:
I posted the patched boot img from latest OO12 Ota to another thread.
Flash it via fastboot and your are good.
BootIMG-Magisk24.3_IN2025_11_C.11
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Oh wow, thank you! How do i flash it via fastboot?
andylmfao said:
Oh wow, thank you! How do i flash it via fastboot?
Click to expand...
Click to collapse
I guess you already setup adb/fastboot on your pc. If not google it.
-connect phone to the pc and activate usb debugging in your phones developer settings(unlock developer settings by tapping 5 times about phone)
-run a windows shell in the folder where you setup adb and fastboot.exe
-type the following in shell
adb reboot bootloader
Your phone will boot into the bootloader
type:
fastboot flash boot BootIMG-Magisk24.3_IN2025_11_C.11.img
xtcislove said:
I guess you already setup adb/fastboot on your pc. If not google it.
-connect phone to the pc and activate usb debugging in your phones developer settings(unlock developer settings by tapping 5 times about phone)
-run a windows shell in the folder where you setup adb and fastboot.exe
-type the following in shell
adb reboot bootloader
Your phone will boot into the bootloader
type:
fastboot flash boot BootIMG-Magisk24.3_IN2025_11_C.11.img
Click to expand...
Click to collapse
And that's just it? Wow! Thank you!
Edit- It just say "Waiting for the device in the Shell. What do I do? And it doesn't show up with "fastboot devices" It also says there's no driver under windows device manager.
edit 2 - nvm I figured it out, turns out I hadn't installed the USB drivers
andylmfao said:
And that's just it? Wow! Thank you!
Edit- It just say "Waiting for the device in the Shell. What do I do? And it doesn't show up with "fastboot devices" It also says there's no driver under windows device manager.
edit 2 - nvm I figured it out, turns out I hadn't installed the USB drivers
Click to expand...
Click to collapse
I hope it works for you now. Have fun.
Hi, will this boot.img work for 11 C.16? If not, do you know where i can get it? Thanks
paq1170 said:
Hi, will this boot.img work for 11 C.16? If not, do you know where i can get it? Thanks
Click to expand...
Click to collapse
IDk but i installed C.16 lately and have the patched image on my pc.
boot_11.C16
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Extracted from OnePlus8ProOxygen_11_C.16_15.E.16_OTA_1036_all_2204222258_57eced36 and patched with Magisk24.3.
I'm guessing that it's not a good idea to OTA root from oos11 to 12?
omega552003 said:
I'm guessing that it's not a good idea to OTA root from oos11 to 12?
Click to expand...
Click to collapse
What do you mean? To preserve root with the inactive slot method within magisk?
I root my device with flashing a patched boot img.
xtcislove said:
What do you mean? To preserve root with the inactive slot method within magisk?
I root my device with flashing a patched boot img.
Click to expand...
Click to collapse
Well that how yo'd normally do it, but for some reason when you do that on the OOS12 upgrade its get really weird.
xtcislove said:
IDk but i installed C.16 lately and have the patched image on my pc.
boot_11.C16
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Extracted from OnePlus8ProOxygen_11_C.16_15.E.16_OTA_1036_all_2204222258_57eced36 and patched with Magisk24.3.
Click to expand...
Click to collapse
Do you have C.20 version?
gzyms said:
Do you have C.20 version?
Click to expand...
Click to collapse
No.
Simply download the Prebuild binaries from here.
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com
Edit: That is the payload dumper im using.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
6.58 MB folder on MEGA
4 files and 3 subfolders
mega.nz
And download the C.20 update from here.
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Use payload dumper to extract the boot image and copy it to yout device
Install Magisk apk on your device (does not matter if it has root or not)
patch the boot image, copy the patched image to your pc and you have a patched boot image for C.20.
xtcislove said:
No.
Simply download the Prebuild binaries from here.
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com
And download the C.20 update from here.
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Use payload dumper to extract the boot image and copy it to yout device
Install Magisk apk on your device (does not matter if it has root or not)
patch the boot image, copy the patched image to your pc and you have a patched boot image for C.20.
Click to expand...
Click to collapse
This is not as easy as you might think. The default payload dumper (and the Go version) cannot handle these incremental OTAs:
Processing boot partitionUnsupported type = 9 · Issue #10 · vm03/payload_dumper
Hi, @vm03! :) Is there a solution to this problem? Only boot.img didn't succeed. I have Nokia 4.2 Thanks! Log: (.py) PS D:\Downloads\1> python payload_dumper.py --diff payload.bin Processing aboot ...
github.com
Instead you need to use this:
GitHub - mrslezak/update_payload_extractor
Contribute to mrslezak/update_payload_extractor development by creating an account on GitHub.
github.com
Unfortunately, this payload extractor fork is broken on windows. I had to set up a Ubuntu VM to run it.
The entire process took the majority of my afternoon
Attached is the extracted boot.img, both magisk patched and unpatched. Hopefully it saves others some time.
Swap_File said:
This is not as easy as you might think. The default payload dumper (and the Go version) cannot handle these incremental OTAs:
Processing boot partitionUnsupported type = 9 · Issue #10 · vm03/payload_dumper
Hi, @vm03! :) Is there a solution to this problem? Only boot.img didn't succeed. I have Nokia 4.2 Thanks! Log: (.py) PS D:\Downloads\1> python payload_dumper.py --diff payload.bin Processing aboot ...
github.com
Instead you need to use this:
GitHub - mrslezak/update_payload_extractor
Contribute to mrslezak/update_payload_extractor development by creating an account on GitHub.
github.com
Unfortunately, this payload extractor fork is broken on windows. I had to set up a Ubuntu VM to run it.
The entire process took the majority of my afternoon
Attached is the extracted boot.img, both magisk patched and unpatched. Hopefully it saves others some time.
Click to expand...
Click to collapse
You are right. I posted the wrong payload dumper.
I am using the one from here and it worked with every payload i tried.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
6.58 MB folder on MEGA
4 files and 3 subfolders
mega.nz
I guess the other one is quicker but im using this and it works. I edit my old post.
Swap_File said:
This is not as easy as you might think. The default payload dumper (and the Go version) cannot handle these incremental OTAs:
Processing boot partitionUnsupported type = 9 · Issue #10 · vm03/payload_dumper
Hi, @vm03! :) Is there a solution to this problem? Only boot.img didn't succeed. I have Nokia 4.2 Thanks! Log: (.py) PS D:\Downloads\1> python payload_dumper.py --diff payload.bin Processing aboot ...
github.com
Instead you need to use this:
GitHub - mrslezak/update_payload_extractor
Contribute to mrslezak/update_payload_extractor development by creating an account on GitHub.
github.com
Unfortunately, this payload extractor fork is broken on windows. I had to set up a Ubuntu VM to run it.
The entire process took the majority of my afternoon
Attached is the extracted boot.img, both magisk patched and unpatched. Hopefully it saves others some time.
Click to expand...
Click to collapse
Can we use this attached boot img on IN2011_11_C.20 (India)?
List of official Amazon firmware URLs for the FireTV 2nd gen Cube (raven - 2019). Visit the github mirror for additional stock apps, source code, and firmware links.
Downloader app code for this page: 111590
Read here for instructions on how to flash firmware.
For other FireTV device firmware check the following:
Fire TV 2 box (sloane - 2015)
2nd gen Stick (tank - 2016)
4k Stick (mantis - 2018)
3rd gen Stick (sheldon/p - 2020)
4k Max (kara - 2021)
Full Firmware Bins
DateVersionDownloadSizeMD52020-05-15FireOS 7.2.1.2 (PS7212/1333)update-kindle-raven-PS7212_user_1333_0017951962500.bin869.7MB9fbbd2490d4232af91940e0ad73f2e6f2020-12-21FireOS 7.2.2.9 (PS7229/1853)update-kindle-raven-PS7229_user_1853_0019562708356.bin871.4MB20f0759aba774eb98d2e67231ac1a53f2022-03-15FireOS 7.2.4.2 (PS7242/3516)update-kindle-raven-PS7242_user_3516_0021710617732.bin877.7MB4fff4d20b8eb4a71c3e0eed2f38dad7a2022-03-24FireOS 7.2.7.3 (PS7273/2625)update-kindle-raven-PS7273_user_2625_0022851240324.bin885.3MB21aaa390ceda55ad1d6f035f055d1e7d2022-04-07FireOS 7.2.7.9 (PS7279/2766)update-kindle-raven-PS7279_user_2766_0023253929604.bin878.5MB59eb447ac768ddcf2ca6c40a39c1072c2022-05-26FireOS 7.2.8.5 (PS7285/2877)update-kindle-raven-PS7285_user_2877_0023723720068.bin872.8MB9d8b64c9e1634292651b292c0ad2a0a62022-06-28FireOS 7.2.8.5 (PS7285/2880)update-kindle-raven-PS7285_user_2880_0023723720836.bin873.9MB32b851ee658481d97a29d9b9e461ef692022-07-27FireOS 7.2.9.2 (PS7292/2982)update-kindle-raven-PS7292_user_2982_0024126400132.bin864.9MBa0617b8b14aa6c337ec2486913cfea192022-08-23FireOS 7.2.9.2 (PS7292/2984)update-kindle-raven-PS7292_user_2984_0024126400644.bin864.9MB6d8be6d630a11781736217852be3d24a2022-09-20FireOS 7.6.0.3 (PS7603/3110)update-kindle-raven-PS7603_user_3110_0025065956996.bin861.4MB1d7b57a994e3445f785731bdadb2e7ab2022-10-12FireOS 7.6.0.8 (PS7608/3614)update-kindle-raven-PS7608_user_3614_0025468739204.bin863.1MB6ffa919f98f10fb7879a08de0e6ee6112022-11-19FireOS 7.6.1.4 (PS7614/3227)update-kindle-raven-PS7614_user_3227_0025938402180.bin870.2MB2ee4993e33e6ec725aa48fd90360f4072023-01-24FireOS 7.6.2.4 (PS7624/3337)update-kindle-raven-PS7624_user_3337_0026810845572.bin847.2MBc925977c1fd35eeb7f0be92a4df52f7e2023-03-29FireOS 7.6.3.3 (PS7633/3445)update-kindle-raven-PS7633_user_3445_0027347744132.bin843.5MBd69687d36269b2a2f8b5b54c09703c2a2023-05-23FireOS 7.6.4.6 (PS7646/3550)update-kindle-raven-PS7646_user_3550_0028085968516.bin835.4MB8bb4424d113c6c98f806066dd8ac7db9
Differential Firmware Bins
DatePre-update VersionPost-update VersionDownloadSizeMD52021-12-11FireOS 7.2.2.9 (PS7229/1856)FireOS 7.2.4.2 (PS7242/3515)update-raven-diff-PS7229_1856_0019562709124-to-PS7242_user_3515_0021710617476.bin316.4MB3d5bdb26d4e6832ccd8ca27fdd4ce1442021-12-11FireOS 7.2.4.2 (PS7242/2906)FireOS 7.2.4.2 (PS7242/3515)update-raven-diff-PS7242_2906_0021710461572-to-PS7242_user_3515_0021710617476.bin63.1MB3a1b460e0c82d03eaad7a7f71ea296322022-03-15FireOS 7.2.2.9 (PS7229/1856)FireOS 7.2.4.2 (PS7242/3516)update-raven-diff-PS7229_1856_0019562709124-to-PS7242_user_3516_0021710617732.bin316.5MB8f0a0d19599b7d9bf9ec50eaa1c10da22022-03-24FireOS 7.2.4.2 (PS7242/3515)FireOS 7.2.7.3 (PS7273/2625)update-raven-diff-PS7242_3515_0021710617476-to-PS7273_user_2625_0022851240324.bin270.3MB1097276bfb648e9c405926be4b1473872022-03-24FireOS 7.2.4.2 (PS7242/3516)FireOS 7.2.7.3 (PS7273/2625)update-raven-diff-PS7242_3516_0021710617732-to-PS7273_user_2625_0022851240324.bin271.0MB18bf38f8f333dac2dde56bec9d4d80e72022-04-07FireOS 7.2.0.6 (PS7206/1098)FireOS 7.2.7.9 (PS7279/2766)update-raven-diff-PS7206_1098_0017683466884-to-PS7279_user_2766_0023253929604.bin523.3MB655ba089f01f5267bf52e50eaf8357912022-04-07FireOS 7.2.2.9 (PS7229/1856)FireOS 7.2.7.9 (PS7279/2766)update-raven-diff-PS7229_1856_0019562709124-to-PS7279_user_2766_0023253929604.bin397.3MB5c21eb690c8126b0661add40a98cd2e22022-05-26FireOS 7.2.2.9 (PS7229/1856)FireOS 7.2.8.5 (PS7285/2877)update-raven-diff-PS7229_1856_0019562709124-to-PS7285_user_2877_0023723720068.bin400.8MB1749a7607898eb12338c108a9b6cbcba2022-06-28FireOS 7.2.8.5 (PS7285/2877)FireOS 7.2.8.5 (PS7285/2880)update-raven-diff-PS7285.2877N_2877_0023723720068-to-PS7285_user_2880_0023723720836.bin36.6MB5609154748559eee52439e4eaf31f4e22022-07-27FireOS 7.2.8.5 (PS7285/2880)FireOS 7.2.9.2 (PS7292/2982)update-raven-diff-PS7285.2880N_2880_0023723720836-to-PS7292_user_2982_0024126400132.bin134.0MBdfef05e4bebe2cb467bea9fa69186ced2022-08-23FireOS 7.2.9.2 (PS7292/2982)FireOS 7.2.9.2 (PS7292/2984)update-raven-diff-PS7292.2982N_2982_0024126400132-to-PS7292_user_2984_0024126400644.bin35.5MBa0511b1d7ff483bd3f989a2705a058dc2022-09-20FireOS 7.2.9.2 (PS7292/2984)FireOS 7.6.0.3 (PS7603/3110)update-raven-diff-PS7292.2984N_2984_0024126400644-to-PS7603_user_3110_0025065956996.bin136.8MBab82ecead2ae69b3149aeb70437446492022-10-12FireOS 7.6.0.3 (PS7603/3110)FireOS 7.6.0.8 (PS7608/3614)update-raven-diff-PS7603.3110N_3110_0025065956996-to-PS7608_user_3614_0025468739204.bin48.7MB67f7939754e282c95f28855436aa9e582022-11-19FireOS 7.6.0.8 (PS7608/3614)FireOS 7.6.1.4 (PS7614/3227)update-raven-diff-PS7608.3614N_3614_0025468739204-to-PS7614_user_3227_0025938402180.bin153.5MB0ca668980ec077279f5f6cb554eaad012023-01-24FireOS 7.6.1.4 (PS7614/3227)FireOS 7.6.2.4 (PS7624/3337)update-raven-diff-PS7614.3227N_3227_0025938402180-to-PS7624_user_3337_0026810845572.bin158.8MBc77f4bdced70693a0426444c3d72e54f2023-03-29FireOS 7.6.2.4 (PS7624/3337)FireOS 7.6.3.3 (PS7633/3445)update-raven-diff-PS7624.3337N_3337_0026810845572-to-PS7633_user_3445_0027347744132.bin130.7MB3ac69ff74afca7c75f22bec19ea4990f2023-05-23FireOS 7.6.3.3 (PS7633/3445)FireOS 7.6.4.6 (PS7646/3550)update-raven-diff-PS7633.3445N_3445_0027347744132-to-PS7646_user_3550_0028085968516.bin114.9MB632eae416a901e835dfe17a77dd1210b
Added PS7285/2877, PS7285/2880, PS7292/2982
Because there are now a number of full bins, I'll stop adding differential bins. But I'll try to keep adding the diff bins between consecutive releases, to make it easier to find what's been added/changed.
Added PS7285/2877 --> PS7285/2880 and PS7285/2880 --> PS7292/2982
Added PS7292/2984 full bin
Added PS7292/2982 --> PS7292/2984 diff bin (35.5MB)
Thank you.
Is there a guide to manually install a specific firmware on my Fire Cube?
sylvio2000 said:
Is there a guide to manually install a specific firmware on my Fire Cube?
Click to expand...
Click to collapse
You should only need to download the full firmware file and rename the .bin extension to .zip, then flash it with TWRP. You would need to unlock the Cube to do this, but that requires a firmware older than PS7273/2625.
At the moment this firmware list is mostly a research and development resource for the Cube.
Added PS7603/3110 full bin (861.4MB)
Added PS7292/2984 --> PS7603/3110 diff bin (136.8MB)
FireTV FireOS7 started with PS7202, this is the first major numerical jump. It might just be a necessity since PS7300 is reserved for FireHD tablet devices. The differential file doesn't look particularly much bigger than any other update.
If anyone is curious enough to check, this is the firmware extraction procedure on Linux/Ubuntu:
1) Rename firmware *.bin extention to *.zip, and unzip
2) Decompress brotli file (*.br file) to sparse image (*.dat file)
Install brotli [sudo apt-get install -y brotli]
Code:
brotli -d system.new.dat.br
3) Convert sparse image to ext4 image (*.img file)
Download sdat2img
Code:
./sdat2img.py system.transfer.list system.new.dat system.img
4) Mount ext4 image
Code:
sudo mount -t ext4 -o loop system.img /mnt
5) Unmount the image when you are done
Code:
sudo umount /mnt
Pro-me3us said:
You should only need to download the full firmware file and rename the .bin extension to .zip, then flash it with TWRP. You would need to unlock the Cube to do this, but that requires a firmware older than PS7273/2625.
Click to expand...
Click to collapse
Are you saying that the newest full ota can be installed via TWRP without losing dfu access in the process? I'm still using the build that came on the device (PS7229/1856) because I don't know which newer ota can be installed without losing dfu access, or if there is even any major feature benefit to installing a newer build. That's the idea I got from what you said here.
Pro-me3us said:
Added PS7603/3110 full bin (861.4MB)
Added PS7292/2984 --> PS7603/3110 diff bin (136.8MB)
FireTV FireOS7 started with PS7202, this is the first major numerical jump. It might just be a necessity since PS7300 is reserved for FireHD tablet devices.
Click to expand...
Click to collapse
When you say "necessity", you mean the jump in the numerical naming convention, not that it would be a necessity to upgrade to this build of the firmware, right?
goapy said:
Are you saying that the newest full ota can be installed via TWRP without losing dfu access in the process?
Click to expand...
Click to collapse
Sorry, I may have been unclear there. You can only update to PS7242/3516 without losing DFU access, the next update disables DFU (PS7273/2526). I don't know if there are any notable benefits of PS7242/3516 (March 2022) over PS7229/1856 (January 2021).
I've used burn mode, fastboot, and TWRP to make backups. I never tried flashing an OTA bin through TWRP, I hadn't had a reason to try yet but it should be fine. To be cautious I'd first use TWRP to make a full backup, then use TWRP to flash that backup, to confirm there's no issues. As long as there's DFU access, the Cube will always be able to boot TWRP / fastboot / burn mode.
goapy said:
When you say "necessity", you mean the jump in the numerical naming convention, not that it would be a necessity to upgrade to this build of the firmware, right?
Click to expand...
Click to collapse
Yes, just necessary by Amazon's FireOS naming convention. PS7300 --> PS7400 numbering indicates the firmware is for a FireHD tablet. Superficially, jumping from firmware number PS7292 --> PS7603 looks like a major update, but I think it's just a regular update, no bigger than PS7285 --> PS7292 two months ago.
Added PS7608/3614 full bin (863.1MB)
Added PS7603/3110 --> PS7608/3614 diff bin (48.7MB)
Added PS7614/3227 full bin (870.2MB)
Added PS7608/3614 --> PS7614/3227 diff bin (153.5MB)
Added PS7624/3337 full bin (847.2MB)
Added PS7614/3227 --> PS7624/3337 diff bin (158.8MB)
Instructions for how to flash firmware have been added here
Added PS7633/3445 full bin (843.5MB)
Added PS7624/3337 --> PS7633/3445 diff bin (130.7MB)
Added PS7646/3550 full bin (835.4MB)
Added PS7633/3445 --> PS7646/3550 diff bin (114.9MB)
New
/system/priv-app/
com.amazon.device.lowstoragemanager
com.amazon.minitv.android.app-stub
com.amazon.storage.manager
com.amazon.vizzini.ftvcds-stub
com.fireos.sdk.ftve.addp
Gone
/system/priv-app/
com.amazon.alexa.datastore.app-stub
com.amazon.alexashopping
New
system/app/
areyoustillwatchingdialog
Gone
system/app/
firetvlowstoragemanager
Is it possible to update the fire tv manually with no root ? I've downloaded a bin file but don't know how update can be applied
No, the update bins have to be served directly from Amazon to the FireTV
If users could update with their own local bin files, you'd have a lot of people downgrading their firmware, and Amazon would not like that lol.