project slimBOXtv
- Thread starter SlimHouse
- Start date
I already tried with Aidan's ROM. In this ROM the box is always in BOOT. I chose the correct version, but Aidan's ROM does not work on the A95X F3 Air Amlogic S905x3.
Can you help me certify the box?
I think it is possible using this utility, but the folder is empty:
Downloads for : -Android- Utilities | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
Attachments
Android 9.0 is the last upgrade that will see on this device, Amlogic has dropped support for S905W chipset while ago.
something like this...
i mean that old android smart phone never get update officialy thats why aosp lineage os avilable..i mean unofficially
Phones are sold in an larger quantities and are more spread than TV boxes, i.e. greater possibilities of (unofficial) support.
The S905W is a relatively old chipset and underpowered, compared to the newer S905X2 (G12) and S905Y2 (SM1) SoC's, i dont expect any more support in the future.
Help with TWRP?
I have have followed directions from https://slimboxtv.ru/twrp-vremennoe/
1. Downloaded TWRP . - TWRP_AML_SlimHouse_3.5.2.zip
2. Copied flash drive.
3. Rebooted to the stock recovery with Slimbox extended reboot.
4. Selected " Apply update from EXT "
5. Update from udisk
6. Selected "TWRP_AML_SlimHouse_3.5.2.zip"
Screen shows TWRP Spalsh screen and locks on it.
Power off/on reboots to stock recovery.
Amlogic s905x 2g/8g Slimbox AOSP 15.4.7
I just want to be able to back up box before modifications.
I do not want to install TWRP permanately
I have have followed directions from https://slimboxtv.ru/twrp-vremennoe/
1. Downloaded TWRP . - TWRP_AML_SlimHouse_3.5.2.zip
2. Copied flash drive.
3. Rebooted to the stock recovery with Slimbox extended reboot.
4. Selected " Apply update from EXT "
5. Update from udisk
6. Selected "TWRP_AML_SlimHouse_3.5.2.zip"
Screen shows TWRP Spalsh screen and locks on it.
Power off/on reboots to stock recovery.
Amlogic s905x 2g/8g Slimbox AOSP 15.4.7
I just want to be able to back up box before modifications.
I do not want to install TWRP permanately
Yes I'm using slim firmware and slimhouse twrp.
Slimhouse TWRP is what's getting stuck.
I need to load it from a usb drive because the sdcard is being used as adoptable system memory.
I don't want to install twrp permanently as that will prevent patches from the slimbox system settings.
Alpha works but can be quirky.
Okay
Put temporary twrp on USB
From settings use install patch
Think it is in slimbox settings
System will see USB with twrp
Install
Hi , i got a TX3 MINI+ , installed slimBOXtv 16.4.5 on it.
Put slimhouse TWRP on a USB stick, went into recovery, aply update fom Udisk.
Getting error " E:Unexpected ota package type, expects AB, actual block. Installation aborted "............... Wat shud i do now
Put slimhouse TWRP on a USB stick, went into recovery, aply update fom Udisk.
Getting error " E:Unexpected ota package type, expects AB, actual block. Installation aborted "............... Wat shud i do now
Here is method of madness I use
First enable root
Place temporary twrp on 32 gig usb drive
From slim settings
Installing patch
Select twrp
Will install from there
Or take you to recovery
From there
Apply from ext
Select udisk
Install
Change language (if required)
Create backup
By default will go to internal
I use Select storage
Move to otg udisk(same usb temporary twrp is on)
Create backup
Reboot
Remove usb and keep in safe place
There are other methods with terminal/adb
I prefer slow manual method
Good luck
Happy Testing
Hi , i have no "installing patch" option in Slimbox settings (also not in normal settings, i checked everywhere). My Slimboxtv rom is 16.4.5 AOSP
Okay
I test atv version
Ignore that part
Boot to recovery (toothpick method)
From there
Apply from ext....
Etc
Etc
Happy Testing
I did that and that gives me the error from my first post.
"error " E:Unexpected ota package type, expects AB, actual block. Installation aborted "
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2
Due diligenceIf you have a high quality T.V.:
* Capable of 600 -- 2000 nits (more is better).
* Dynamic tone-mapping
* Inky blacks supported by superior locl dimming.
HDR, HDR10, HDR10+ Dolby Vision(work in progress) can be amazing .
Peak brightness is probably one of the most important aspects of HDR. If a TV has llittle (100-400 nits) HDR peak brightness, it won't display all the highlights of the content.
High contrast ratio and a local dimming feature is important for a good HDR experience; the TV can display bright and dark highlights without loss of details.
xx My current (and previous T.V.) does Dolby Dark(...Dolby Murky) with muddy grey blacks. 4K Bluray was miserable to view !.
Due diligence: Check for your T.V.'s implementation of Dolby Vision (work in progress - dark and broken even on High end T.V.'s .) Being replaced by Dolby (Luminace?)?
This is Most Excellent Reaper Man !!!!
Have been researching Dolby Vision for the last 6 months or so.
Especially with all the work/ progress from
CoreELEC..
Only to find out we have Samsung TV.s
They Do Not Support Dolby Vision
Theu use HDR10+
Which is Dolby Vision competitor
Or Samsung equivalent to...
So not only would I need a Box with suffix -J/K
I would also need new TV.s
Dolby Vision is overrated
Hahaha
Happy Testing2
Tried using this method for H96 Pro+, took the files from 7.1.2 SHMOD and packed them into the H96 Pro Plus listed on Slimbox webpage (listed ones are only for LPDDR3, and mine is DDR3.), but no luck. Flash was successful, however it got stuck on the Slimbox boot animation, never progressed to the animated one.
However, I managed to successfully find a working version afterall. My H96 Pro+ is a CZ-S32-V2.2, 64GB/3GB DDR3, qca9377 with Gigabit LAN.
First version that I found here was X92 SBX, flashed successfully, remote worked, but Bluetooth kept constantly crashing.
Second version was recommended to me in the SBX Telegram group. It was the Tronsmart Vega S96 SBX. That one flashed successfully, everything seems to be working fine, LAN didn't test yet, but since both are Gigabit, I'd expect it to work. Only thing was the Remote control did not work. So I unpacked the X92, where the remote worked, to Level 1, found the files in vendor/etc and used a USB and MiXplorer on my H96 to replace the files in vendor/etc (requires Root) and presto, remote working again.
Maybe I could try swapping the bootloader files from X96 to H96, but don't see much point as everything so far seems to be working. Very nice upgrade from Android 7.1.2 to 9.13 afterall.
Leaving this wall of text here, hopefully it helps out someone in a similar situation.
P.S. Now if I could only figure out how to properly flash Magisk...1
It's really revision 5 so I was duped! I opened a dispute. And the unbrick? Can anyone advise? Thank you
It's already done! I found it on YouTube.1
Thanks sesdave, I sorta figured that because my 922s don't run near as hot. I think that's a lot of my problems. I'm going to look for some now. -
120
A project to create firmware for TV boxes and sticks with an Amlogic processor.
Amlogic S905X, S905X2, S905X3, S912, S922, S905W, S905W4, S905Y2, S905L (Android 9)
Amlogic S905X4, S905W2, S905Y4 (Android 11)
slimBOXtv ATV and AOSP are two custom firmwares suitable with some modifications for many android TV boxes.
Version 9.3 (Android 9)
Version 42.5, 54.5 (Android 9)
Version 11.4 (Android 11)
Version 114.3 for Ugoos X4, X4Q, AM7, TOX3 (Android 11)
Supported TV boxes
Download
Contacts
8SLIMBOX ver 8
• Updated google services and apk
ВЂ Returned the choice in the settings of a dark or white theme
• Returned additional image settings
• Updated firmware
• In AOSP, I returned the recent stocks and closed the menu button
• Added debug settings
• Added additional power settings
• Various system corrections8slimBOXtv 9.7 (Android 9)
Changes:
• Replaced video to adjust the image to better
• Added Convolver presets for ViPER4AndroidFX
• Added to the settings Dynamic background for TVLauncher (ATV)
• Increased selection of color themes up to 16
• Returned the installation of their backgrounds for TVLauncher, copy your picture to the UpdateSBXtv folder on the internal memory (ATV)
• Activation without rebooting colored settings icons and background for TVLauncher
• Added to settings Download patch with updates
• Added to settings Ad blocking using hosts
• Added to settings Use Google DNS servers
• Added to settings Improve network speed
• Added to the settings Force wifi
• Amendments to the update installation mechanism
• Cleaning in TVLauncher replaced by rocket (ATV)
• Fixed black screen on first system startup
• System amendments
Download ATV or AOSP7I have found out how to root SlimRom with Magisk:
1. Root SlimRom via the settings
Then you will have "Superuser" rooting.
2. Install TWRP
You don't need to, but you can install your TWRP image permanently via the TWRP app:
3. Extract boot.img
You need to extract "boot.img" in TWRP:
Code:cat /dev/block/boot > /sdcard/boot.img
4. Patch the stock boot.img with Magisk manager app
Install Magisk manager apk.
Press the upper install button and select the stock boot.img.
Magisk will create a patched boot.img.
5. Now unroot in SlimBox settings
6. Flash the patched boot.img in TWRP by selecting install, then image, then choose the file, to "boot"
7. Finally flash Magisk.zip in TWRP
Thats it.53. Extract boot.img from stock firmware
You need to have a stock rom for your device.
Ideally a zipped rom, so that you can extract the "boot.img" out of it.
In case you have an img-file, than you need to extract "boot.img" out of it via Amlogic toolkit:
GitHub - natinusala/linux-amlogic-toolkit: Allows to unpack and repack AMLogic images for Android 7 without the Customization Tool
Allows to unpack and repack AMLogic images for...
github.com
By this you can extract the stock boot.img from the stock firmware.
This is only good for android 7 images, Android 9 (which most people are using) is totally different.
To root slimbox you only need patch the current boot.img
In twrp :
cat /dev/block/boot > /sdcard/boot.img
Then use magisk to patch the img
Reboot to twrp
Flash the patched boot.img to boot.
Reboot
New posts
-
can't flash anything, bootloader fails- Latest: fonodebende
