"Factory" Recovery for MTCx PX3, PX5 and PX6 SOM.
UPDATED" 26.06.2023 - Before doing this, try your Headunit USB cable first - Some headunits support OTG directly on the headunit USB cable.
Come here after using paid Software "Mod" tools like Modinstaller?
This method is the factory method, which can completely recover a "bricked" SOM, recover from failed "modinstaller" or failed upgrade of Paid mods.
Finally - OTG for all without modifying your head-unit. With only basic electronic/soldering skills, get OTG and fearlessly flash or recover a 'bricked' MTCD/E (HCT printed on SOM) Rockchip PX3, PX5 SOM.
See attached pics for making an OTG cable from a USB cable and two resistors.
Resistors are 12K and 15k (22k is probably better) or anyone of the following. combinations. These resistors are necessary as 'voltage dividers', with a value between 1.8v and 3.3 OK. These simply place a logic '1' on recovery and USB-OTG to 'tell' the SOM to go into OTG recovery mode.
R1 | R2
-------------------
1K | 1.8K
2.2K | 3.3K
10K | 18K
12K | 22K
Get Windows Driver [Driver assistant - v5.11] and [RKDevTool 2.93] for direct/OTG SOM flashing:
1. From a chinese Firefly site here
or
2. My Google Drive here
[RKDevTool] .ini file is set English, otherwise tool will be rendered in Chinese.
This tool for dumping / getting full backup of SOM
Excellent tool, thanks @RedScorpioXDA
Note - all tools and driver have equivalent Linux versions.
26.06.2023 - Android Tool is now RkDevTool
PX5 Android 9 Update.img - suitable for flashing via rockchip tools - https://yadi.sk/d/umCvHqCDzHccr/RockChip PX5 Android 9/YB
The image is located in px5 android 9/yb. The file has "_img_" listed in the filename.
Note Android 10 has an img file too - located in px5 android 10/chs.
PX5 Android 8 Oreo full Partition extract suitable for recovering SOM, flashing via rockchip tools - https://drive.google.com/drive/folders/1P703unZDA_TdRzl6fjkkb-YUB-KpTViW
Using the RockChip RKDevTool:
For OREO: Unzip and flash all partitions in the ZIP file [px5_OREO_Full_13032018-UseToRecoverOrCreateNew.7zip here
For Android 6, flash the latest update.img file in RKDevTool
There are guides to partition flashing found on the internet, would be great if anyone could contribute by posting step-by-step instructions or a video to assist others (there are now posts in this thread...)
A generic guide to the RockChip RKDevTool, flashing partitions or image files is here as previously posted.
Credit (thanks!) to @scorillo_ro for the detailed image/connections diagram.
Worst case - SOM doesn't respond - force 'maskrom' detailed here explaining what MaskRom is and here on how to for your PX5 (px3 is similar.) Steps are: Power Off SOM and disconnect USB to PC. Use Tweezers, apply power/connect USB. Hold until Windows Device chime is heard (within about 2 seconds of power on.) See attached pic.
Warning : Use thin pins for OTG cable in order to avoid the damage of the SOM connectors, although along the thread it has been noted many times that damage to the SOM socket is very likely to happen if thick pins are used...OR buy SOM header from Aliexpress, digikey etc.[/COLOR]
17/11/2019 - Edit: Corrected URL for Windows and Linux Rockchip tools
04/04/2020 - link to px5 android 9 full update.img
20.06.23 - Update broken links to driver and tool. Update Name of tool (was) Android Tool - (now) RKDevTool
Nice work @marchnz !
A full step by step and pictures howto should be made now and all those PX5 users without sdcard slots will be able to use this method to get Android8!
LE. I drew a schema
scorillo_ro said:
Nice work @marchnz !
A full step by step and pictures howto should be made now and all those PX5 users without sdcard slots will be able to use this method to get Android8!
LE. I drew a schema
Click to expand...
Click to collapse
So with this methon, will be possible to flash on 6.0 unity, the recovery and the system of android 8.0?
lucajust said:
So with this methon, will be possible to flash on 6.0 unity, the recovery and the system of android 8.0?
Click to expand...
Click to collapse
Absolutely! I've done it a bunch of times. You can either use the sdupdate.img from the Oreo upgrade thread to load the Oreo recovery and then install the oreo .zip from recovery OR a full set of partition images.
I have a full set of partition images if needed, they're about 25gb but should compress right down (that 25gb includes [user] partition which is an empty partition.
Good... I'll try... But the process Need a PC no? Becouse with the unit with SD card slot needs PC only to prepare the sd card for android 8 recovery
Inviato dal mio Mi A1 utilizzando Tapatalk
lucajust said:
Good... I'll try... But the process Need a PC no? Becouse with the unit with SD card slot needs PC only to prepare the sd card for android 8 recovery
Inviato dal mio Mi A1 utilizzando Tapatalk
Click to expand...
Click to collapse
Yes, PC. I've updated the post to include links to tools and driver. Driver 4.5 & Android tool works on Win7 - Win 10, x86 and x64.
For those without SDCard wanting to upgrade to Oreo:
You could try OTG flashing the Oreo sdupdate.img, fit SOM back to headunit and then try loading the Full Oreo update.zip from USB. Otherwise I will need to upload the full Oreo partitons dump with instructions....over the next few days....
marchnz said:
Yes, PC. I've updated the post to include links to tools and driver. Driver 4.5 & Android tool works on Win7 - Win 10, x86 and x64.
For those without SDCard wanting to upgrade to Oreo:
You could try OTG flashing the Oreo sdupdate.img, fit SOM back to headunit and then try loading the Full Oreo update.zip from USB. Otherwise I will need to upload the full Oreo partitons dump with instructions....over the next few days....
Click to expand...
Click to collapse
Thanks... What are the "SOM"?
Inviato dal mio Mi A1 utilizzando Tapatalk
It is my understanding that I can flash the SOM without the rest of the board?
So just disconnect the SOM then hook up the USB as per the diagram and it will be detected by windows. Use android tool / RockChip Batch Tool with a android 6/8 recovery.
The issue I have is that the nand doesn't look like its recognised after an attempt to flash oreo. Please see attached picture.
Harsesis said:
It is my understanding that I can flash the SOM without the rest of the board?
So just disconnect the SOM then hook up the USB as per the diagram and it will be detected by windows. Use android tool / RockChip Batch Tool with a android 6/8 recovery.
The issue I have is that the nand doesn't look like its recognised after an attempt to flash oreo. Please see attached picture.
Click to expand...
Click to collapse
Yes, you understood correctly. This method may save you...
scorillo_ro said:
Yes, you understood correctly. This method may save you...
Click to expand...
Click to collapse
You mentioned a full partition dump. I'm hoping I don't need this. I remember reading that the partition structure needed to be changed for android 8. Do you have any idea how to do this via the tools? I remember reading about something called a storagemap that rockchip uses.
Harsesis said:
You mentioned a full partition dump. I'm hoping I don't need this. I remember reading that the partition structure needed to be changed for android 8. Do you have any idea how to do this via the tools? I remember reading about something called a storagemap that rockchip uses.
Click to expand...
Click to collapse
Wait for @marchnz to put this information here. Meanwhile you can start building your USB JIG.
Will try this, just have to buy resistord.
One question... How to download from Github?
Regards
Edit: Found it
Clandaries said:
Will try this, just have to buy resistord.
One question... How to download from Github?
Regards
Click to expand...
Click to collapse
Move one level up to https://github.com/rockchip-linux/rkbin then use the green "Clone or download" button, then select "Download ZIP"
Finally I hear the Windows connecting sound. But my Device is still not detected. It says "usb device not recognized". I thaught it would be the driver but I installed the v4.5 Driver. Any Ideas?
Maybe you need to switch green and white usb data wires...
scorillo_ro said:
Maybe you need to switch green and white usb data wires...
Click to expand...
Click to collapse
Yeah already tried that. Also tried it with a different PC both Windows 10 but same problem. I also tried to a other SoM but this one got the same problem. I really dont know anymore what to do
Malle355 said:
Yeah already tried that. Also tried it with a different PC both Windows 10 but same problem. I also tried to a other SoM but this one got the same problem. I really dont know anymore what to do
Click to expand...
Click to collapse
Strange. I only used Windows 7.
You can also try using a powered usb switch. Maybe the USB ports you used does not provide sufficient power? This is just an assumption.
Or, as @marchnz said, you can try enter maskrom mode.
scorillo_ro said:
Strange. I only used Windows 7.
You can also try using a powered usb switch. Maybe the USB ports you used does not provide sufficient power? This is just an assumption.
Or, as @marchnz said, you can try enter maskrom mode.
Click to expand...
Click to collapse
My Device is only getting detected in MaskRom Mode. Its not getting detected in Normal Mode. But as I said it says "usb device not recognized".
Malle355 said:
My Device is only getting detected in MaskRom Mode. Its not getting detected in Normal Mode. But as I said it says "usb device not recognized".
Click to expand...
Click to collapse
Did you try to upload a firmware image from maskrom mode? The other mode, not working for you, is called loader mode and is provided by software that might be corrupted.
scorillo_ro said:
Did you try to upload a firmware image from maskrom mode? The other mode, not working for you, is called loader mode and is provided by software that might be corrupted.
Click to expand...
Click to collapse
Cant upload the Firmware from MaskRom Mode. I got the "usb device not recognized" error. I never goth my the device in the loader mode. My PC never detected the SoM in loader mode.
Related
RCA 10" Touchscreen Tablet PC/DVD Combo Featuring Android 6.0 (Marshmallow)
*No idea why it says PC/DVD as its Android not Windows.
ASIN/Model numbers: ASIN: B077L4VBHK Model: DRP2091
RCA typical RCT number: RCT6603W47M7
Chipset/CPU: MT8127
Ports: 1x Mirco USB (supports ADB! etc. unlike VikingPRO), 1xUSB A, 1xHDMI (mini i believe), 1xMicroSD slot (supports up to 128GB)
Special: 1xDVD/CD Reader/Drive. has unlockable bootloader via fastboot oem unlock
Root Attempts: (Failed: KingoRoot, SRS, KingRoot, RootMaster)
MTK Droid Root & Tools and SP Flash Tools don't seem to work right with this cant create scatter etc. (i assume because of MT8127)
Links:
Walmart/Wally World
Amazon
if any dev could help me root this and get custom recovery would be great.
UPDATE: Thanks to NepoRood (and my testing) theres now CWM recovery (attached to post extract zip and flash img via fastboot flash recovery command.) unfortunately we were still unable to get root access.. if anyone has this device or wants to help root this pm me.
Additional files attached maybe someone can build me cwm or twrp for this as i could never get anything to build for mtk devices.
darkensx said:
Additional files attached maybe someone can build me cwm or twrp for this as i could never get anything to build for mtk devices.
Click to expand...
Click to collapse
I found various firmware downloads, but need to know the exact type of firmware you are running.
Example of one I found: rct6603w47m7-android6.0-v23-v2.15.80 (<-- underlined part is what matters)
If you boot into recovery, it should show you the type of firmware you have.
NepoRood said:
I found various firmware downloads, but need to know the exact type of firmware you are running.
Example of one I found: rct6603w47m7-android6.0-v23-v2.15.80 (<-- underlined part is what matters)
If you boot into recovery, it should show you the type of firmware you have.
Click to expand...
Click to collapse
DRP2091-android6.0-v62-v1.19.90-E02
*also says on very bottom of screen "supported API: 3"
**DRP2091 is rct6603w47m7 not sure why there's so many different model/serial numbers referencing the same exact device...
also i managed to dump the whole device via SP tools readback on linux so if anything beyond recovery or boot img are needed i should have it.
darkensx said:
DRP2091-android6.0-v62-v1.19.90-E02
*also says on very bottom of screen "supported API: 3"
**DRP2091 is rct6603w47m7 not sure why there's so many different model/serial numbers referencing the same exact device...
also i managed to dump the whole device via SP tools readback on linux so if anything beyond recovery or boot img are needed i should have it.
Click to expand...
Click to collapse
That version isn't on the site (or any v1.19.x), I'll download the images from the OP in a bit and see what's inside...
NepoRood said:
That version isn't on the site (or any v1.19.x), I'll download the images from the OP in a bit and see what's inside...
Click to expand...
Click to collapse
Had the same issue also I came across a bunch of ota test files on a Chinese site but links were dead and because no ota update is available i can't grab the ota url or file name. So ended up hitting a dead end.
Would it be possible to bypass the activation code screen with cwm or twrp? Or maybe put a different version of android on the tablet, other than marshmallow.?
darkensx said:
Additional files attached maybe someone can build me cwm or twrp for this as i could never get anything to build for mtk devices.
Click to expand...
Click to collapse
I'm having same problem could someone help me root this tablet explain as easy as possible and slow and clear directions
I have no idea
johnnymack said:
I'm having same problem could someone help me root this tablet explain as easy as possible and slow and clear directions
Click to expand...
Click to collapse
I've got the RCT6603W47M7 tablet, but here in the UK it goes by the name of RCA Neptune 10.1L.
Problem is I have bricked it and I am now trying to recover it using SP Flash Tools. I have tried 2 different stock ROMs, only to have nothing but errors and interruptions during flashing. (errors 2004 and 4008). My tablet is fully charged yet it will randomly disconnect during flashing. I've tried both the MTKAllInOne.bin and DA_SWSEC.bin but I still get the same problem either way.
I've tried different USB ports, different cables and the two download agents that I just mentioned but I am stumped.
I wanted to try the ROM found here https://www.needrom.com/download/rca-rct6603w47m7/
But as I don't have a premium account I cannot access it.
Any ideas? This is very frustrating.
BP9375 said:
I've got the RCT6603W47M7 tablet, but here in the UK it goes by the name of RCA Neptune 10.1L.
Problem is I have bricked it and I am now trying to recover it using SP Flash Tools. I have tried 2 different stock ROMs, only to have nothing but errors and interruptions during flashing. (errors 2004 and 4008). My tablet is fully charged yet it will randomly disconnect during flashing. I've tried both the MTKAllInOne.bin and DA_SWSEC.bin but I still get the same problem either way.
I've tried different USB ports, different cables and the two download agents that I just mentioned but I am stumped.
I wanted to try the ROM found here https://www.needrom.com/download/rca-rct6603w47m7/
But as I don't have a premium account I cannot access it.
Any ideas? This is very frustrating.
Click to expand...
Click to collapse
problem with the cwm recovery if i remember correctly is any thing flashed by it doesnt take the device will just bootloop
i no longer have the device currently i might pickup another at some point... i cant remember if i used the micro usb port to flash or if i had to use a usb male to male cable..
darkensx said:
problem with the cwm recovery if i remember correctly is any thing flashed by it doesnt take the device will just bootloop
i no longer have the device currently i might pickup another at some point... i cant remember if i used the micro usb port to flash or if i had to use a usb male to male cable..
Click to expand...
Click to collapse
Thank you for your reply, I was worried that this discussion was dead. That's frustrating to say the least! Damn! Well, I don't know if this will work but I found another device that is also a MT8127 and has exactly the same spec of this tablet. My point being is that I found a TWRP image for that device, and because it's the same chip set I assume that it'll work for this device too?
If I can get my bricked tablet to even turn on I shall try it. It also makes me wonder that if we were able to root the device, would we be able to access the internal storage by normal means? By using the micro USB ? Either way it'd be great to have it rooted.
I stayed up all night last night trying to flash this tablet and still no luck, it keeps disconnecting half way through.
My Chinese Android car head unit is stuck in a bootloop (the home screen shows but the unit reboots after a few seconds). I got a firmware zip file from the manufacturer (the zip contains files like scatter.txt, ramdisk2.img, boot.img and so on). However, I'm unable how to find out how on earth I can install this firmware and get out of my bootloop.
I have no access to Android itself (the system reboots too soon). There are no physical buttons to activate recovery mode. When I use a USB keyboard I can get into recovery by pressing ALT GR and PRT SCR but after a reset "no command" shows up and I'm stuck again...
Any help please?
Flashing instructions
[Apologies for the lengthy reply, I have to assume that you have no experience in flashing MTK SoC]
Sorry to hear that! I am also contemplating t buy a Chinese Android headunit with GPS but I am still contemplating. Reason being which model to buy? I am an avid Lenovo devices fan because in my part of the world models from Lenovo uses a lot of MTK SoC. (Any other other brand I buy is also a must to be on MTK SoC)
Ok! Now based on your short description I saw "scatter.txt" file mentioned so it is definitely an MTK devices, 100%.. When you boot loop you definitely will not be able to access any function, more so with a head unit that dont provide hardware buttons. I can only help you understand the method to reflash the firmware on MTK devices the rest you have to figure it out yourself.
The USB port is your key here. If the manufacturer did not provide you with USB "IN" (female) port which is not normal and only provide you with USB connectors you will have to decode/or just connect the wiring from the connectors to a USB female Port (which what China manufacturers do at the back of the head unit). There are also head units that provide ready to use USB port on the facia.
Whatever it is I cant tell you which port to use. This where you will have to experiment yourself.
Download MTK flashing tool "SP Flashtool" (find the ones that is suitable upto MTK device 6592 because it should be back ward compatible with older devices) The Chinese dont use the latest MTK SoC for their head units, that is only reserved for the high end heads.
Read up on how to install SP Flashtool on your PC and other accompanying Drivers you have to install, (if you only have a Mac go borrow somebodys Win7 or Win10 PC) there are no Mac SPFlashtool.
Once you have install according to SPFlashtool instructions you read. (It has to follow a certain sequence) e.g "1- ADB Driver" so on and so forth because if you dont follow the sequence it might fail to start the flashing operation. (You will not know it but I am pretty damn sure you will be cussing me).
First read up on how to install ADB driver for MTK devices correctly. Confident? Now try connecting your device to the PC experimenting to identify the correct USB port to use. If the ADB is installed correctly and you got the right USB from the device connected your PC wil give an audible sound( it should unconnected to condition evreytime you test). OK good connection! Only then try installing SP Flash tool and try a dry running the SPFT. If your installation is correct there should be either color changes to the SPFT window because it doesnt detect any devices.
You are good to go! Your MTK Android device should be in the "OFF" condition (after every shutdown there are still some operation running in the background,so it is a good practice to wait at least 5 seconds for it to be 100% OFF.) Run the SPFT fully loaded with the firmware dislayed in the SPFT window. Then initiate "Download" (make sure all indicators is at "download only" do not change this option or you are gonna have a really dead duck.) At this point the SPFT is active and waiting for you to attach the device to PC (before running make sure the PC and device is not connected yet!). If everything is per instructed ADB, USB Cables/Ports, SPFlashTool (download only) you will see color lines in the SPFT Window, wait till the end of process it will display notificatio. If the firmware is correct and you have attached and 12V DC source to the device it should boot up as fresh as new.(provided that the supplier gave you the correct firmware).
A word of advise these cheap head units normally bluff their actual Android version e.g actual KitKat advertised and displayed as Marshmallow. Best of luck!
The zip file attached are screenshots of the flashing process.
Thanks for your very elaborate information, but it won't work. The ZIP I got is an OTA zip file. The scatter.txt inside those zips isn't compatible with the SP Flash Tool.
wimpie3 said:
Thanks for your very elaborate information, but it won't work. The ZIP I got is an OTA zip file. The scatter.txt inside those zips isn't compatible with the SP Flash Tool.
Click to expand...
Click to collapse
Doesnt the seller provide you with the original firmware? He only gave you an OTA?? Oh $#it! The OTA file is small probably a few Mb? The full firmware in your case should be around 800Mb upwards. You are right an OTA cannot use SPFT it can only be flash through the original recovery (not custom recovery). If its a popular Chinese model ML-CK1018 or Joying brand ( I assume you bought a Joying? Thats the only brand that release an OTA not long ago) There is remote possibility of getting the firmware.Anyway just give your brand and model number. I will try to look on Russian or Chinese site but no promises! Will try.
But I am pretty sure it is an MTK SoC since you can unzipped and it shows "scatter.txt" file. Most other SoC arent normally in zip format and have scatter file.
Sent from my HT70 using Tapatalk
The OTA ZIP file is about 900MB.
It's a NAVITOPIA 9 inch 4G LTE WIFI Head Unit with Android 6.0 2G + 32G.
I'm in the same boat, have a plastic bookend at the moment, will not connect to the PC because flashed and formatted my device with the update firmware!!!
Good night I hope your team will help me update my box TV Knowing that the device has an
Android version 6.0
Amlogic S905x
P212
I would like to update it to the latest version of android to take advantage of installing applications can you help me
Attached are photos from inside the device
edisondweikat said:
Good night I hope your team will help me update my box TV Knowing that the device has an
Android version 6.0
Amlogic S905x
P212
I would like to update it to the latest version of android to take advantage of installing applications can you help me
Attached are photos from inside the device
Click to expand...
Click to collapse
you can try my custom rom for s905x
aidanmacgregor said:
you can try my custom rom for s905x
Click to expand...
Click to collapse
How to download a ROM and install it on your Xbox TV ??
aidanmacgregor said:
you can try my custom rom for s905x
Click to expand...
Click to collapse
How to download a ROM and install it on your Xbox TV
And knowing the appropriate system for the device, knowing there are many versions upon download
If you don't know your WiFi chipset open you box to find it and download the corresponding rom from Aidan's download repo , if your not sure post pictures of it and it will be identified
jimenis said:
If you don't know your WiFi chipset open you box to find it and download the corresponding rom from Aidan's download repo , if your not sure post pictures of it and it will be identified
Click to expand...
Click to collapse
According to what I saw on the AIDA64 app
It appeared to me that the Wifi Recieves is the type and model of the telink company
Quick Google of the board I see an ap6212 but really you need to open your box and see what's printed on the WiFi chipset . attached is what I found so check against yours and remember you will loose any widevine certification install a new firmware
AP6212
Download the ampak ap6212 version listed and install with usb burn tool https://androidmtk.com/download-amlogic-usb-burning-tool
Remember to uncheck erase bootloader and have a mouse and keyboard just incase your remote won't work
Do I only deselect the erase bootloader .. or is there something else
I hope to explain how to connect the device to the computer and install the ROM
You will load the IMG file first , deselect erase bootloader to connect use a double male usb lead to connect box to pc , try first by simply inserting see if it shows as connected if not locate the recovery button and depress while inserting the usb once connected press start and wait till it completed to 100%. I would try usb port nearest power supply or marked otg ...good luck
jimenis said:
You will load the IMG file first , deselect erase bootloader to connect use a double male usb lead to connect box to pc , try first by simply inserting see if it shows as connected if not locate the recovery button and depress while inserting the usb once connected press start and wait till it completed to 100%. I would try usb port nearest power supply or marked otg ...good luck
Click to expand...
Click to collapse
What is the redeem button and where do I find it ??
As for the program, this is as good as the picture ??
Currently, I will be looking for a dual male usb cable in the store
Use version 2.2.4 of usb burn tool , it will show normal erase use that setting , uncheck erase bootloader have the rom you want loaded by going to file select IMG .never heard redeem button ...
jimenis said:
Use version 2.2.4 of usb burn tool , it will show normal erase use that setting , uncheck erase bootloader have the rom you want loaded by going to file select IMG .never heard redeem button ...
Click to expand...
Click to collapse
When connecting the cable, does it connect automatically, or does it need to press a specific button?
All boxes are different, some just connect others need reset button held down with toothpick and you have to find the correct usb port like advised or you can short the band using a pin .Another way to upgrade is by using burn card maker to create bootable SD from the image once made insert SD card and if your system is booted use a program like terminal emulator to reboot and start the update the command is reboot update
I installed the system on the box TV and it worked perfectly, but the problem was that it did not recognize the remote. What is the solution to control it? I hope you will benefit
Good for the remote maybe somebody else will point you in right direction it involves taking files from old IMG and modifications to kernel , a good solution is to buy a cheap Bluetooth remote or usb remote , some game controllers work or just use a usb keyboard and mouse
Who is the person who will define the old remote control on the system and where to find it
You could try asking the owner of the rom under his thread https://forum.xda-developers.com/t/...date-tv-netflix.4191157/page-37#post-85043449
Hi everyone,
Updates:
2021-08-17 - Added patched Magisk boot for this device. (Conceptum Stock ROM)
I'm starting this thread to collect information and files regarding this particular version of X96 box and to explain to anyone interested what I have discovered so far..
The company who has repackaged the firmware for this box for the Greek market, CONCEPTUM, refuses to release the original firmware for this device.
So currently, I have dumped two types of firmware from a stock box in case it is needed. A standard TWRP backup, and a dd image.
At the moment, I actually am NOT having any luck restoring the firmware using the TWRP restore. Not sure why.
I was able to restore the original firmware using the dd image. So for anyone who screws up their stock firmware, you can use the dd image from the mega drive. Punchline: The stock image has terrible wifi speed as well. I have yet to try restoring the firmware via dd yet but when I do I will write if it works or not.
Here is a link to the folder where I will be updating what compatible files I can find.
4.38 GB folder on MEGA
13 files and 6 subfolders
mega.nz
This post is very incomplete and I will be adding to it shortly.
--------------------------------------
SPECIFICATIONS
4GB RAM/32GB Storage
Ethernet Speed: 1000mbps / 1gbs
Ethernet Chipset: Realtek RTL8211F
Wifi : 5ghz & 2.4 ghz support
Wifi / Bluetooth Chipset: Cdtech 4761743 (which is a Qualcomm QCA6174A design? See links below.)
https://discourse.coreelec.org/t/looking-for-users-with-no-working-wifi-or-bt/9649/248
https://discourse.coreelec.org/t/looking-for-users-with-no-working-wifi-or-bt/9649/249
https://blog.csdn.net/u012851408/article/details/86605778
Motherboard Markings: BM805H_141 V3.2 20352 4020
Motherboard Sticker: 4+32+CDW ZF210129
---------------------------
How to get into recovery
The button needed to access recovery is hidden. It is deep inside the stereo jack. (You can see it if you shine a flashlight into there.
My suggested tool to press this button easily is a qtip with the cotton from one end removed.
Insert the tool, and press it in until you feel the click.
Apply power to the device and as soon as you can see the logo come on, release the tool pressure.
It should enter recovery in 5 to 10 seconds.
---------------------------
CoreELEC
I was able to boot CoreELEC via sdcard, with bluetooth and wifi working with the following device tree:
sm1_s905x3_4g_1gbit.dtb
I forgot to check the speed of the wifi, but if I recall, both 2.4 & 5ghz was working with that dtb.
---------------------------
TWRP
The TWRP_AML_ViT_3.3.1_2020.zip (in the Mega folder) is a "hinged" version. Not sure if its the right term, but it can be run from the stock recovery, (Apply update from external). It does NOT install, it just runs it and lets you do stuff from there.
If anyone knows the source or an update for the Amlogic TWRP Hinged version, please post it here.
I used a previous "hinged version" TWRP_322.zip but this version did not backup properly all the partitions, ex it totally skipped the Vendor partition, which is why I have 2 of these Tvboxes as my first one the backup was bad and it was essentially bricked.
---------------------------
Amlogic USB Burning Tool
This seems to work fine, but something that is always missing from peoples instructions,
The Male to Male USB cable, on this device must be plugged into the USB 3 port.
The power cable must also be removed, and when plugging in the USB cable to the correct port, will provide power for the "fastboot" equivalent mode needed to flash from the Amlogic tool.
So the procedure to flash is (after installing the USB Flash tool)
Device is powered off.
Insert USB cable into your pc end.
Insert tool and press recovery mode button.
Plug in other end of USB cable into the tvbox.
It should power on, keep the recovery button pressed until you hear the device connect to Windows (USB being plugged in sound)
They you should be able to flash.
---------------------------
Compatible ROMS
Long story short, due to a initial TWRP backup that was missing certain important partitions, I bricked my first box.
While trying to get the box working again, I have found the following firmware to work mostly. I am not reccomending them, as I am not sure they are working optimally, but if needed these can boot the system and work in some capacity.
X96Max_Plus_Q2_20201209-1446.img
Original firmware for X96 Max Plus Q2 version
sbx_x96max_plus_q2_v12
Slimbox Version 12 for X96 Max Plus Q2
This version does not come with Google framework which I needed so I didn't work with it much.
---------------------------
Magisk
Patched boot image for this device.
9.67 MB file on MEGA
mega.nz
Download and extract this file and put it somewhere you can flash from.
Install Magisk Manager.
Boot from Hinged TWRP, goto Install, Install image, select the file and flash to Boot partition. BE CAREFUL AND DON'T FLASH TO BOOTLOADER
Magisk Should be working, try running a root app and magisk should pop up
Magisk is complicated. On all the Amlogic boxes as far as I know, Magisk will install but NOT function properly.
The geniuses at 4pda have figured out a procedure to make Magisk work properly, but it requires hex editing the boot partition and reflashing it.
I have done the procedure successfully when I was using the X96Max_Plus_Q2_20201209-1446.img firmware. It does work.
I will upload this to the mega folder when I have time.
When I manage to hex edit the stock boot image, I will also upload it. Its an involved process and takes some time.
Reserved for future shenanigans.
my device has the same mainboard as you mentioned above ,but mine is 4/64 , my device bricked after burning non related image and after i plug in the power , for first 5 minutes nothing happens and then in vfd it shows boot and then clock and on tv screen only boot logo appears after 5 min but non consistent if you change tv source and back again it shows no hdmi connection and nothing more happens.
i tried out all p3 version of x96 air images but useless because they have different main board i wanted to try your dd imade backup (twrp is impossible bacause of no recovery) and burn it with amlogic usb tool but extraction of image ended with error with more than 15 gigabytes .
i appreciate anyone who can help me to unbrick my device , i am hopeless because this device has no support mine is named,x96 air 4/64
effgee said:
Hi everyone,
Updates:
2021-08-17 - Added patched Magisk boot for this device. (Conceptum Stock ROM)
I'm starting this thread to collect information and files regarding this particular version of X96 box and to explain to anyone interested what I have discovered so far..
The company who has repackaged the firmware for this box for the Greek market, CONCEPTUM, refuses to release the original firmware for this device.
So currently, I have dumped two types of firmware from a stock box in case it is needed. A standard TWRP backup, and a dd image.
At the moment, I actually am NOT having any luck restoring the firmware using the TWRP restore. Not sure why.
I was able to restore the original firmware using the dd image. So for anyone who screws up their stock firmware, you can use the dd image from the mega drive. Punchline: The stock image has terrible wifi speed as well. I have yet to try restoring the firmware via dd yet but when I do I will write if it works or not.
Here is a link to the folder where I will be updating what compatible files I can find.
4.38 GB folder on MEGA
13 files and 6 subfolders
mega.nz
This post is very incomplete and I will be adding to it shortly.
--------------------------------------
SPECIFICATIONS
4GB RAM/32GB Storage
Ethernet Speed: 1000mbps / 1gbs
Ethernet Chipset: Realtek RTL8211F
Wifi : 5ghz & 2.4 ghz support
Wifi / Bluetooth Chipset: Cdtech 4761743 (which is a Qualcomm QCA6174A design? See links below.)
https://discourse.coreelec.org/t/looking-for-users-with-no-working-wifi-or-bt/9649/248
https://discourse.coreelec.org/t/looking-for-users-with-no-working-wifi-or-bt/9649/249
https://blog.csdn.net/u012851408/article/details/86605778
Motherboard Markings: BM805H_141 V3.2 20352 4020
Motherboard Sticker: 4+32+CDW ZF210129
---------------------------
How to get into recovery
The button needed to access recovery is hidden. It is deep inside the stereo jack. (You can see it if you shine a flashlight into there.
My suggested tool to press this button easily is a qtip with the cotton from one end removed.
Insert the tool, and press it in until you feel the click.
Apply power to the device and as soon as you can see the logo come on, release the tool pressure.
It should enter recovery in 5 to 10 seconds.
---------------------------
CoreELEC
I was able to boot CoreELEC via sdcard, with bluetooth and wifi working with the following device tree:
sm1_s905x3_4g_1gbit.dtb
I forgot to check the speed of the wifi, but if I recall, both 2.4 & 5ghz was working with that dtb.
---------------------------
TWRP
The TWRP_AML_ViT_3.3.1_2020.zip (in the Mega folder) is a "hinged" version. Not sure if its the right term, but it can be run from the stock recovery, (Apply update from external). It does NOT install, it just runs it and lets you do stuff from there.
If anyone knows the source or an update for the Amlogic TWRP Hinged version, please post it here.
I used a previous "hinged version" TWRP_322.zip but this version did not backup properly all the partitions, ex it totally skipped the Vendor partition, which is why I have 2 of these Tvboxes as my first one the backup was bad and it was essentially bricked.
---------------------------
Amlogic USB Burning Tool
This seems to work fine, but something that is always missing from peoples instructions,
The Male to Male USB cable, on this device must be plugged into the USB 3 port.
The power cable must also be removed, and when plugging in the USB cable to the correct port, will provide power for the "fastboot" equivalent mode needed to flash from the Amlogic tool.
So the procedure to flash is (after installing the USB Flash tool)
Device is powered off.
Insert USB cable into your pc end.
Insert tool and press recovery mode button.
Plug in other end of USB cable into the tvbox.
It should power on, keep the recovery button pressed until you hear the device connect to Windows (USB being plugged in sound)
They you should be able to flash.
---------------------------
Compatible ROMS
Long story short, due to a initial TWRP backup that was missing certain important partitions, I bricked my first box.
While trying to get the box working again, I have found the following firmware to work mostly. I am not reccomending them, as I am not sure they are working optimally, but if needed these can boot the system and work in some capacity.
X96Max_Plus_Q2_20201209-1446.img
Original firmware for X96 Max Plus Q2 version
sbx_x96max_plus_q2_v12
Slimbox Version 12 for X96 Max Plus Q2
This version does not come with Google framework which I needed so I didn't work with it much.
---------------------------
Magisk
Patched boot image for this device.
9.67 MB file on MEGA
mega.nz
Download and extract this file and put it somewhere you can flash from.
Install Magisk Manager.
Boot from Hinged TWRP, goto Install, Install image, select the file and flash to Boot partition. BE CAREFUL AND DON'T FLASH TO BOOTLOADER
Magisk Should be working, try running a root app and magisk should pop up
Magisk is complicated. On all the Amlogic boxes as far as I know, Magisk will install but NOT function properly.
The geniuses at 4pda have figured out a procedure to make Magisk work properly, but it requires hex editing the boot partition and reflashing it.
I have done the procedure successfully when I was using the X96Max_Plus_Q2_20201209-1446.img firmware. It does work.
I will upload this to the mega folder when I have time.
When I manage to hex edit the stock boot image, I will also upload it. Its an involved process and takes some time.
Click to expand...
Click to collapse
i have a full twrp backup but unable to go to recovery to unbrick my device or will you change twrp backup to img file so that i can burn that with usb burning tool ? full detail of the problem in the previous post
reza0511 said:
i have a full twrp backup but unable to go to recovery to unbrick my device or will you change twrp backup to img file so that i can burn that with usb burning tool ? full detail of the problem in the previous post
Click to expand...
Click to collapse
Regular Air firmware's do not work.
P1-P3 don't work for sure, P4 I don't know but I think not.
I haven't found a photo yet of the P4 hardware.
Try USB Flashtool 4/64 image for X96Max_Plus_Q2 to get your recovery back if such a firmware exists, otherwise try the 4/32. X96 Max Plus Q2 firmware (X96Max_Plus_Q2_20201209-1446.img)
You should be able to get recovery back via flashing one of those images.
X96 Max Plus Q2 firmware is compatible, but if you use the 4/32 image you will only see the half of your storage.
Restoring your TWRP full backup again once you get the max firmware (for twrp) installed will not work unfortunately. Already went through this.
reza0511 said:
my device has the same mainboard as you mentioned above ,but mine is 4/64 , my device bricked after burning non related image and after i plug in the power , for first 5 minutes nothing happens and then in vfd it shows boot and then clock and on tv screen only boot logo appears after 5 min but non consistent if you change tv source and back again it shows no hdmi connection and nothing more happens.
i tried out all p3 version of x96 air images but useless because they have different main board i wanted to try your dd imade backup (twrp is impossible bacause of no recovery) and burn it with amlogic usb tool but extraction of image ended with error with more than 15 gigabytes .
i appreciate anyone who can help me to unbrick my device , i am hopeless because this device has no support mine is named,x96 air 4/64
Click to expand...
Click to collapse
You have a Conceptum box or just the same motherboard?
If you have a Conceptum, you are pretty much ****ed. They wont release the original firmware. You will have to buy a second box and get the image via dd.
I had to buy a second box and get the disk image via dd, and then restore the dd image using dd from within TWRP, overwriting the entire storage with the image. This was using the terminal built into TWRP.
In general, restoring from TWRP doesn't work well on these boxes, especially going from rom to rom as the partition layouts are different and TWRP doesn't handle it correct.
Conversion of the dd image to usb flashable is tricky and I haven't done it.
The person that MAY be able to do such a thing is Ricky ( https://forum.xda-developers.com/t/...w-milestone-donate-version-available.3786991/ ) but I dont know and I don't think there is any point as my dd image has partition layout for 32 gb version, you will lose half your storage unless he can also expand the partition.
Even if you manage to get TWRP back, there will probably be a partition layout difference from the firmware you use to get TWRP on the box, and the TWRP image backup you did. It probably will not work.
You need to get your original firmware, or a dd image of the same box.
You can also use the Slimbox for x96max_plus_q2. I did NOT like Slimbox 12 because it was missing google play and a lot of other things. But it will restore recovery.
solved !!
i save my box by below two steps
1- burning veitnami atv version of x96air img file (google for link )
2- restoring my full twrp via recovery
reza0511 said:
решено !!
Я сохраняю свою коробку, выполнив следующие два шага
1- сжигание veitnami atv версии файла img x96air (гугл для ссылки)
2- восстановление моего полного twrp через рекавери
Click to expand...
Click to collapse
is there a link?
Я уже решил свой вопрос. Спасибо за ваш сайт. Меня интересовало восстановление кирпича x96air_100. Я из Украины.
I have already solved my question. Thank you for your site. I was interested in the restoration of the brick x96air_100. I am from Ukraine.
How you did get MAGISK working? I own x96 AIR P3 and would like to use MAGISK
Soldiaz said:
How you did get MAGISK working? I own x96 AIR P3 and would like to use MAGISK
Click to expand...
Click to collapse
Hi.
To get Magisk working, its a bit of a difficult process.
Essentially, Amlogic released / built their kernels with a kernel boot option "skip_initramfs" which magisk needs "want_initramfs" for this to work.
The process is complicated as you must hex edit your boot.img after you have patched it with the Magisk Manager patching method called "Recovery Mode"
4pda where this was discovered - https://4pda.to/forum/index.php?showtopic=774072&st=25020#entry91068157
Video from 4PDA that shows the hex editing process - https://mega.nz/file/pJ1RTChR#b5rLNs-4GF2qlZXKzbL0P5lmAeLLYObJ_w3_Yf8h16U
You can also get the video from the above thread but if I recall you must register to download and unless you know russian its difficult to register there.
A guide I wrote that you can follow along with the video to understand the process - https://rentry.co/wgu9u
Every detail matters, I studied the video for many hours to understand the process, good luck.
My thread about this process here: https://forum.xda-developers.com/t/...ide-to-accompany-video.4320923/#post-85493037
Thanks!!!! Dam looking not that easy .
The Boot img from x96 Air you edited, is it Stock?
Sorry i dont check my mesages here very often.
I don't know which boot image you are talking about, it would be very helpful for you to link me which one specifically I need to answer the question for..
If you are talking about the image for my Air Extreme, it is stock and patched by magisk, and then hex edited for magisk. But I dont know its compatibility for any of the other Air versions.
effgee, just wanted to let you know there is a lot of information and multiple versions of the X96 Air TV Box Firmware available at...
Original Google link... (Vietnamese)
https://www.google.com/url? sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwiDtPO9yZj0AhUOXM0KHYnzCIUQFnoECA8QAQ&url=https %3A%2F%2Ftinhte.vn%2Fthread%2Ftong-hop-cac-ban-firmware-cua-android-tv-box-x96- air.3050996%2F&usg=AOvVaw1it1QO7hR_e5XsrdSZH-Rj
Google Translated (English) link...
https://tinhte-vn.translate.goog/thread/tong-hop-cac-ban-firmware-cua-android-tv-box-x96-air.3050996/? _x_tr_sl=vi&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=nui,sc
Direct link... (Vietnamese)
https://tinhte.vn/thread/tong-hop-cac-ban-firmware-cua-android-tv-box-x96-air.3050996/
"X96 Air" search via direct link... (Vietnamese)
https://tinhte.vn/search/333184298/?q=x96+air&o=relevance
Hope they help!
Mr350
Ps... If you have trouble with the Google translation links not working try a Google search for... x96 air tinhte.vn ... that might work then click Translate this page.
Hi dear friends,
thank you in advance for your help. I have a strange stuation (at least for me) with this box from Foyu x96 mini.As you can see in photo and also written on paper box , it has Amlogic S905W 4G 32G rom, but if i go inside Kodi for example in System it says it has Rockchip 3229... then also on recovery mode on boot mode it states "android recovery rockchip 322x ..... I've tried with Amlogic burning tool but it doesn't recognize the hub connection and it doesn't burn another rom for S905w. I've tried shortening nand pins..nothing
Have you got any suggestions to erase all and burn an Amlogic s905w Rom , considering there's an S905w cpu?? i don't think it's a false one! there's no Rockchip inside!
thank you
Isn'it strange? Any suggestions?
..seems i found the million dollar question.. the only post that puts in crisis all the forum...
ive seen amlogic devices recovery reporting as rockchip, its usally just a mismatched recovery, i would try and figure out mask rom mode for this board, see my video here for some info
aidanmacgregor said:
ive seen amlogic devices recovery reporting as rockchip, its usally just a mismatched recovery, i would try and figure out mask rom mode for this board, see my video here for some info
Click to expand...
Click to collapse
Thank you for your kind answer,but i tried also with mask mode,it only sound but no connection. For me it's a fake chip,otherwise why with rockchip tool it normally connects? Also on kodi it's incredibly slow,and in system maximum resolution is 1280*720!! Absurd
Hi , I have exactly the same problem with a tv box x96 mini locked in the logo screen. If you find a way to recover, please post it.
gherghe said:
Hi , I have exactly the same problem with a tv box x96 mini locked in the logo screen. If you find a way to recover, please post it.
Click to expand...
Click to collapse
I can't see if yours has amlogic s905w chip,anyway mine it's not locked,you can try with rockchip tool to burn image if you got Rockchip inside
yes I have a S905x chip, it doesn't look very good but I managed to take a picture.I tried with usb burninig tools but my box is not seen by the computer and I don't know how to use the nand method.
If your x96mini is not locked, you can help me with a stock firmware of your box, to try a rewrite of my box with the sd card method. Thanks anyway for the help. I have been looking for a solution to unlock the box for some time.
gherghe said:
If your x96mini is not locked, you can help me with a stock firmware of your box, to try a rewrite of my box with the sd card method. Thanks anyway for the help. I have been looking for a solution to unlock the box for some time.
Click to expand...
Click to collapse
Yours is s905w, seems same situation.. i haven't got original firmware,in my case mine is made by Foyu,you can try to find them on internet, i don't know.. don't know why they're recognized as Rockchip..
ok , thanks
cipposo said:
...i don't know.. don't know why they're recognized as Rockchip..
Click to expand...
Click to collapse
Maybe, because is it "faked" remarked RK3229 as S905W.
Try to setup mSD card with LibreELEC...
Release RK322x first mainline release · knaerzche/LibreELEC.tv
Kernel 5.5.0 uboot 202001 lima drm / mesa 20.0 (beta) hdmi up to 2160p hantro video hw decoding for MPEG2/VP8/H264 up to 1080p Wifi only for chipsets that have mainline support no preconfigured rc ...
github.com
mAtvXk said:
Maybe, because is it "faked" remarked RK3229 as S905W.
Try to setup mSD card with LibreELEC...
Release RK322x first mainline release · knaerzche/LibreELEC.tv
Kernel 5.5.0 uboot 202001 lima drm / mesa 20.0 (beta) hdmi up to 2160p hantro video hw decoding for MPEG2/VP8/H264 up to 1080p Wifi only for chipsets that have mainline support no preconfigured rc ...
github.com
Click to expand...
Click to collapse
Sure,probably it is,but with librelec would be only kodi...
Hello, thank you for your help. If I install the firmware from the link you sent me, can I then write another firmware? If I find the original firmware.
cipposo said:
Sure,probably it is,but with librelec would be only kodi...
Click to expand...
Click to collapse
Just to confirm if you have Rockchip inside, anyway LE is runned from SD card, nothing will be installed onto the box.
Ok thank you.
Hi, I tried LibreELEC but it doesn't work. I'm attaching the image with the received error, maybe you know what the problem is. Thanks
gherghe said:
Hi, I tried LibreELEC but it doesn't work. I'm attaching the image with the received error...
Click to expand...
Click to collapse
Did you create bootable media...
Create Media - LibreELEC.wiki
wiki.libreelec.tv
Yes I created a bootable sd card, with LibreELEC rk322x the box does not start, the LED remains off.
Well it look like you guys have a fake amlogic like me on the tag is 4GB RAM and 32GB flash store. All the inside chip has been marked like the real one but are fake. Main chip is RK3229 and the ram is just 1GB and 8GB flash. I successfully unbrick this **** using rkfactory tool and a rom for RK3229 chip. step to follow: 1. install rockcip drivers, 2. start factory tool, 3. load firmware in factory tool, 4. conect USB A - A cable to pc, 5. tooth pick in the AV port and pres the restore switch from inside, 6. connect USB A - A to the OTG USB port on the box the port is the one next to the tf card reader, 7, the hub is recognized by the pc and it be detected by the tool factory, 8. flash the firmware, enjoy.
Files:
1 Drivers: https://mega.nz/file/q8kk0ayA#XA3ZCoZK-Lu0LW1alqq6qKBmzFTj4gDDnlLWqq0Joso
2 factory tool: https://mega.nz/file/ihVnBC5L#Ri-IY7uVxcbaXEMkgb_bSXKMcwbkbAnYFxnEuizREaE
3 firmware: https://mega.nz/file/2k8EzJxY#cY_NWvIyof8Rnd7syOK9OYc5Fot19Ub76L46nzTrAAU