I bricked with my X96 MINI while flashing the update firmware using an SD card. I used Burn_Card_Maker to make an SD card for the update, but unfortunately, the X96 Mini LED turns red and the box does not boot, then I try to use the PC USB_Burning_Tool and my X96mini is detected by USB_Burning_Tool
But It stops at 1% with ]--[0x10103005]Romcode/Initialize DDR/Download buffer/Read item data failed
Error in all versions of the USB burning tool
Only version 2.0.1 shows 1% low_power failed and the log is as follows
Code:
[16:34:08 696][HUB1-4][Inf]--Start burning...
[16:34:09 211][HUB1-4][Inf]--------------ERASE BOOTLOADER------------
[16:34:09 211][HUB1-4][Inf]-- low_power
[16:34:13 368][Global][Inf]--User click refresh button
[16:34:39 212][HUB1-4][Err]--IOCTL_BULK_CMD_Handler ret=-116,bulk_cmd= low_power error_msg=libusb0-dll:err [control_msg] sending control message failed, win error: The I/O operation has been aborted because of either a thread exit or an application request.
One thing I have not tried yet is the short NAND method because my box is shown on the USB burning tool.
Please help me to fix this device. I have tried many ways to flash the ROM using USB burning tools and sd card maker tool but no succeed so far.
jami.xda
I've had the same problem. The problem is the usb port or a wrong rom Image. I have 8 ports And 2 works. And the image must exactly for your prozesor. S905w, S905x and other have been installed. Try your luck here forum.freaktab.com/forum/tv-player
. But it also exists at xda developers firmware for x96 mini
---------- Post added at 12:38 AM ---------- Previous post was at 12:33 AM ----------
jami.xda said:
I bricked with my X96 MINI while flashing the update firmware using an SD card. I used Burn_Card_Maker to make an SD card for the update, but unfortunately, the X96 Mini LED turns red and the box does not boot, then I try to use the PC USB_Burning_Tool and my X96mini is detected by USB_Burning_Tool
But It stops at 1% with ]--[0x10103005]Romcode/Initialize DDR/Download buffer/Read item data failed
Error in all versions of the USB burning tool
Only version 2.0.1 shows 1% low_power failed and the log is as follows
Code:
[16:34:08 696][HUB1-4][Inf]--Start burning...
[16:34:09 211][HUB1-4][Inf]--------------ERASE BOOTLOADER------------
[16:34:09 211][HUB1-4][Inf]-- low_power
[16:34:13 368][Global][Inf]--User click refresh button
[16:34:39 212][HUB1-4][Err]--IOCTL_BULK_CMD_Handler ret=-116,bulk_cmd= low_power error_msg=libusb0-dll:err [control_msg] sending control message failed, win error: The I/O operation has been aborted because of either a thread exit or an application request.
One thing I have not tried yet is the short NAND method because my box is shown on the USB burning tool.
Please help me to fix this device. I have tried many ways to flash the ROM using USB burning tools and sd card maker tool but no succeed so far.
Click to expand...
Click to collapse
Look at the last post
Cable
It is looks like your cable is not strong enough. try a new male to male cable.
jami.xda said:
I bricked with my X96 MINI while flashing the update firmware using an SD card. I used Burn_Card_Maker to make an SD card for the update, but unfortunately, the X96 Mini LED turns red and the box does not boot, then I try to use the PC USB_Burning_Tool and my X96mini is detected by USB_Burning_Tool
But It stops at 1% with ]--[0x10103005]Romcode/Initialize DDR/Download buffer/Read item data failed
Error in all versions of the USB burning tool
Only version 2.0.1 shows 1% low_power failed and the log is as follows
Code:
[16:34:08 696][HUB1-4][Inf]--Start burning...
[16:34:09 211][HUB1-4][Inf]--------------ERASE BOOTLOADER------------
[16:34:09 211][HUB1-4][Inf]-- low_power
[16:34:13 368][Global][Inf]--User click refresh button
[16:34:39 212][HUB1-4][Err]--IOCTL_BULK_CMD_Handler ret=-116,bulk_cmd= low_power error_msg=libusb0-dll:err [control_msg] sending control message failed, win error: The I/O operation has been aborted because of either a thread exit or an application request.
One thing I have not tried yet is the short NAND method because my box is shown on the USB burning tool.
Please help me to fix this device. I have tried many ways to flash the ROM using USB burning tools and sd card maker tool but no succeed so far.
Click to expand...
Click to collapse
Thanks, I will check with new male to male cable and let you know the result
zusatzmetall said:
It is looks like your cable is not strong enough. try a new male to male cable.
Click to expand...
Click to collapse
I checked with the new male to male cable but the USB burning tool shown the same error
[0x10103005]Romcode/Initialize DDR/Download buffer/Read item data failed
Code:
[18:16:11 844][HUB1-3][Inf]--Start burning...
[18:16:11 907][HUB1-3][Inf]--------------ERASE BOOTLOADER------------
[18:16:11 907][HUB1-3][Inf]--2-2-0-0
[18:16:11 907][HUB1-3][Inf]-------------Download DDR.USB-----------
[18:16:11 907][HUB1-3][Inf]--2-2-0-0
[18:16:11 907][HUB1-3][Inf]--Control write pll reg1 0xd9000000:0x000000b1
[18:16:12 423][HUB1-3][Inf]--Control write pll reg1 0xd9000000:0x00005183
[18:16:12 938][HUB1-3][Inf]--Write initial succeed
[18:16:12 938][HUB1-3][Inf]--Upload encrypt at 0xc8100228
[18:16:12 938][HUB1-3][Inf]--ulValue = 0xbdfc31bc
[18:16:12 938][HUB1-3][Inf]--File change to DDR_ENC.USB
[18:16:12 938][HUB1-3][Inf]--Read encrypt value succeed
[18:16:12 938][Global][Err]--DDR_ENC.USB
[18:16:12 938][Global][Err]--DDR_ENC.USB
[18:16:12 938][HUB1-3][Err]--Read item data error, code -1
[18:16:12 938][Global][Err]--DDR_ENC.USB
[18:16:12 969][HUB1-3][Err]--[0x10103005]Romcode/Initialize DDR/Download buffer/Read item data failed
[18:16:12 969][HUB1-3][Inf]--Close device handle 0x00000714
[18:16:15 579][Global][War]--User click stop button
[18:16:15 579][Global][Inf]--Enable burning 0
[18:16:19 547][Global][War]--Close tool
[18:16:20 062][Global][Inf]--Burning thread HUB1-3 end run
[18:16:20 062][Global][Inf]--Burning thread HUB1-3 exit
[18:16:20 593][Global][War]--Controler exit
Try to load your firmware in the burning tool software.
Then press START and after connect your box to computer with A-A USB cable
manu_manu4 said:
Try to load your firmware in the burning tool software.
Then press START and after connect your box to computer with A-A USB cable
Click to expand...
Click to collapse
I am doing exactly the same thing you said, loading the firmware, press start then connect the A-A USB cable. but it failed by flashing at 1% with the error
[0x10103005]Romcode/Initialize DDR/Download buffer/Read item data failed
In the log file, it shows:
[18:16:12 938][HUB1-3][Err]--Read item data error, code -1
[18:16:12 938][Global][Err]--DDR_ENC.USB
[18:16:12 969][HUB1-3][Err]--[0x10103005]Romcode/Initialize DDR/Download buffer/Read item data failed
[18:16:12 969][HUB1-3][Inf]--Close device handle 0x00000714
[18:16:15 579][Global][War]--User click stop button
Please help me to unbrick the x96 mini.
Thanks
If you are getting a low Power fault are you connecting the power source while you were trying to flash because maybe that's needed as well
I had the exact same issue with an x96 mini that I just got. There was nothing I could do to get past the 'Romcode/Initialize DDR/Download buffer/Read item data failed' error. Tried different cables, different computers, win 7, win 10, win xp. They would all give the same result. I think the newer x96 minis are locked some how so you can't flash anything on it. I couldn't even boot libreelec or coreelec off of an sdcard. That's why I tried flashing atxperience and that's what bricked mine.
In the end I ordered a new box and won't try to flash it.
https://blog.danman.eu/bricking-and-unbricking-vontar-x96-mini/
Hi I have the same problem.
I bricked mine while trying to install magisk because I lost the faulty root that the box came with while trying to fix it with kingroot but magisk just made it worse.
Were you able to get past the error:- [0x10103005]Romcode/Initialize DDR/Download buffer/Read item data failed
connect usb to usb and start the program and load image file , keep shorting the point to ground until it recognize the port and will burn the image
asegura074 said:
connect usb to usb and start the program and load image file , keep shorting the point to ground until it recognize the port and will burn the image
Click to expand...
Click to collapse
while shorting the pin i can successfully connect the box to my pc but the usb burn tool fails at 4% with error:
"romcode/switch status/identify/error result"
any advice?
JG420 said:
while shorting the pin i can successfully connect the box to my pc but the usb burn tool fails at 4% with error:
"romcode/switch status/identify/error result"
any advice?
Click to expand...
Click to collapse
I'm struggling with the same problem. I found what may be an alternate image for the 1GB/8GB hardware.
T95R-905WB-1G8G-TW00023-R1648.zip - I can't post the link for this, but if you google it, you can access the cached version of a page that has a link to a google drive archive.
I have the 2GB/16GB version, so this doesn't work for me. I end up failing with a NAND error furthing into the programming. I'm still looking for a way to get my box working again - another image or a way to change the RAM/ROM spec in this image.
I hope this is helpful to you.
bobbyskillz said:
I'm struggling with the same problem. I found what may be an alternate image for the 1GB/8GB hardware.
T95R-905WB-1G8G-TW00023-R1648.zip - I can't post the link for this, but if you google it, you can access the cached version of a page that has a link to a google drive archive.
I have the 2GB/16GB version, so this doesn't work for me. I end up failing with a NAND error furthing into the programming. I'm still looking for a way to get my box working again - another image or a way to change the RAM/ROM spec in this image.
I hope this is helpful to you.
Click to expand...
Click to collapse
Please if you find any way let me know, I have the same here.
Thanks.
I have the same problem. Here is the story:
I bought X96 MINI Amlogic S905W, 2GB/16GB, Android 7.1.2. It worked fine one week. Then just stopped to work. The problem is when I plug in the power cable, only the red light is on and the device is dead. The seller told me I have to try pressing the AV reset button 1 - 2 minutes with tooth pick to reset the device. Nothing. Then the seller said I have to flash the firmware with USB burning tool. I tried with two different versions of USB burning tool (2.1.2 and 2.0.8) with several .img files. But every time I get this error, that is discussing here. I cannot find any solution. I still don't want to disassemble it, because it's new ...
By the way, is there any other procedure to "wake up" the device, without flashing the firmware?
I have the exactly same problem. Flash always fails with read data item failed error in my bricked tanix tx3 mini with all the roms I tried so far. Is there any way I can flash twrp in this device? I made a backup in twrp before i started the process. I was able to flash atvx rom only once with erase bootloader unchecked. Since then I am not even able to enter recovery. Device gets connected in flash mode but always fails with read data item failed.
bobbyskillz said:
I'm struggling with the same problem. I found what may be an alternate image for the 1GB/8GB hardware.
T95R-905WB-1G8G-TW00023-R1648.zip - I can't post the link for this, but if you google it, you can access the cached version of a page that has a link to a google drive archive.
I have the 2GB/16GB version, so this doesn't work for me. I end up failing with a NAND error furthing into the programming. I'm still looking for a way to get my box working again - another image or a way to change the RAM/ROM spec in this image.
I hope this is helpful to you.
Click to expand...
Click to collapse
I have a Mega link for that T95R ROM you mentioned. If anyone needs it just inbox me...I'm not sure if I can post links
---------- Post added at 11:36 PM ---------- Previous post was at 11:32 PM ----------
For anyone with the CLONE x96 mini 1gb/8gb...
This here is the ONLY rom that flashed and worked successfully for me! In hosting it in my Mega account. I hope this helps a few people here. Again this is ONLY for the 1gb/8gb clone x96 mini. I hold NO responsibility for any damages caused.
https://mega.nz/#F!2gpBXaSQ!2H7bG5bylktXF69wpC9ePg
Will it support bluetooth dongle?
HI everyone! I have two X96 mini tv boxes with different stocks.
One of them opens this program without any problem. Link for program is here:
https://cloud.mail.ru/stock/7uRgfhaTfR9ebxC4Nj58cd9X
Another tv box doesn't open this program. Opens then closes in a few seconds. Can u help me please. what is the prolem?
I need this program!
Thank you for your attention!
ayon115 said:
I have the exactly same problem. Flash always fails with read data item failed error in my bricked tanix tx3 mini with all the roms I tried so far. Is there any way I can flash twrp in this device? I made a backup in twrp before i started the process. I was able to flash atvx rom only once with erase bootloader unchecked. Since then I am not even able to enter recovery. Device gets connected in flash mode but always fails with read data item failed.
Click to expand...
Click to collapse
Hey Ayon Bro.. Did you fixed it? I have also the same problem bro.. Read data item failed error ..
Related
https://mega.nz/#!BKQS2a4K!G5YrKHWUy2HvL2TOqOlLzwn7Sulp7q8i7-h8uVi0uk8
UNIVERSAL V2 - IF TOP DONT WORK
https://mega.nz/#!bphxHJBB!jRhp0AeNa8orSwscFJHJdE7M14_GxQgbHpnbq-21vy8
Step 1 Download & Extract the bundle for your device
You will be getting either a zip or 7z file, personally I would use 7zip to extract these files, you should get a recovery.img and also a folder called TWRP. If you have these two things move on to step 2
Step 2 - Locations
Both SD Card and USB being formatted Fat32 - Some boxes except most s905 you can use the SD card for both TWRP folder and recovery.img, Regardless I use SD only for recovery.img, so drag and drop the recovery.img onto the Fat32 SD Card and Drag and drop the TWRP folder onto the Fat32 USB drive. Done
Step 3 - Formatting before installing.
Connect everything but the power - Connect a real USB mouse/Airmouse to the box due to the regular remote will not work, connect the USB drive and connect the SD Card, Everything but power. Some boxes have a reset button on the side and some the reset button is inside the AV jack, you will feel it, If in the AV jack simply use a toothpick or use a Q Tip with the cotton end removed and slide it in the AV jack and you will feel the button.
HOLD THIS BUTTON AND DO NOT LET GO - At the same time plug it in and keep holding, boxes with physical power button press this now. You will be presented with a blue screen, you will get a read only scren most likely, slide to proceed.
First thing first I always recommend backing up partitions incase something is to go wrong. There are tons of cloned boxes its hard to cover them all. I personally would go to backup. Locate where it says storage, and change from internal to usb otg for USB drive or external sd for your SD Card. Backup all your partitions.
When done, go back. Press the little house button on the screen or the back button until back at the TWRP menu, go to restore, Make sure usb otg or external sd is chosen, wherever you put the TWRP folder, If you are using a box not from me PM me the model and I will confirm what to restore, for example, M8, M8S BCM and AP models, MX3, M10, You can restore all, S912 boxes some are different so PM me to be safe. After I tell you what to restore do so. Let it do its thing. Once done, reboot and enjoy. If it fails by any means. Do not reboot, just go back and choose wipe, format data, type yes press enter. Once done just go back and restore data JUST BY ITSELF so untick everything but data, once finished restore all the other partitions. All done
Enjoy the build - When you first boot my firmware let it sit after it boots for a good minute or two. It will auto load my custom firmware patches and more.
If you are using M8, M8S, M10, MXq you need to follow below -
When you start the TV box. Let it sit a few minutes and first things first. In Android applications click on No Frills CPU - the accelerometer and when it opens click apply and than exit. It is super important with my custom rom to unlock the other 2 CPU Cores and the other 4 GPU Threads. If this does not make sense just go into my apps and look for no frills, same app as on the desktop you will just see the name instead.
NOT EVERY FIRMWARE HAS NO FRILLS - IF NOT DO NOT WORRY ABOUT IT.
i do not own the firmware
credits go to ghostware.
Congrats!
Just a clarification, which ROM are you using as "skeleton", and what ROM did you take the /system partition from?
MyM8SFinallyWorks said:
Just a clarification, which ROM are you using as "skeleton", and what ROM did you take the /system partition from?
Click to expand...
Click to collapse
i used a m8s+ rom and the 5.1.1 rom from acemax the only problem is with the m8s+ rom is ethernet dont work so by doing this i got ethernet to work.
Thanks for this link
Hello, I just want to ask how do you know if your box is the "ap3660" box and how can you find out?
my box is the m8s amlogic s812
thanks.
lutty321 said:
Hello, I just want to ask how do you know if your box is the "ap3660" box and how can you find out?
my box is the m8s amlogic s812
thanks.
Click to expand...
Click to collapse
you have to open it and look inside
Hi. I cannot get my box to the boot menu with the toothpick reset?!? It just loops into rebooting and goes back to original setup. I have disabled the restore from backup too but still? Pls help!!!!
Tazosman said:
Hi. I cannot get my box to the boot menu with the toothpick reset?!? It just loops into rebooting and goes back to original setup. I have disabled the restore from backup too but still? Pls help!!!!
Click to expand...
Click to collapse
if you have the recovery.img file on the root of the sd card, toothpick method should take you to TWRP where you can then flash the zip. did you give it some time (with the reset button pressed in)? it can take approx 10 seconds sometimes.
Failed signiture
Hi guys i have tried to flash my box with the firmware that was posted here by daniel and i am getting the problem of it saying....
"E: failed to verify whole-file signiture
E: signiture verification failed
Installation aborted "
Ive tried it a few times and still no luck.
Could anyone point me in the right direction of a successful flash please?
Thanks in advance
Hi
i just tryed this metod but my M8S does not respound anymore(no on light) it seems dat it is deed???Has any body iedea what can i do now?
Hey is there any way to fix the remote volume problem? I restored my remote config from 4.4 but everything worked except the volume button. BTW I have the remote with the red, green, yellow and blue buttons at the volume control.
Devmau53 said:
Hi guys i have tried to flash my box with the firmware that was posted here by daniel and i am getting the problem of it saying....
"E: failed to verify whole-file signiture
E: signiture verification failed
Installation aborted "
Ive tried it a few times and still no luck.
Could anyone point me in the right direction of a successful flash please?
Thanks in advance
Click to expand...
Click to collapse
Either your download is corrupt, or you are not using TWRP to perform the update.
Has anyone been having random freezing and reboots?
wolfpack64 said:
Hey is there any way to fix the remote volume problem? I restored my remote config from 4.4 but everything worked except the volume button. BTW I have the remote with the red, green, yellow and blue buttons at the volume control.
Click to expand...
Click to collapse
I also had that problem even though I flashed the square remote zip after the lollipop update. I might have flashed the M8N remote though to be honest and I don't have the box anymore to test more remote patches.
You can try the M8S remote zip from the link below and report back if it worked for you.
http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s802/eny-acemax-ott/firmware-roms-tools-af/18312-s802-multi-remote-patcher-zips
Hi,
Did install this rom provided by d4nielr on my device M8S CS 812M8 V1.3 20150921
Install was perfect boot once and there was a working 5.1 rom with ethernet
Only if i reboot my device its bricked. red licht only recover whith USB burning tool
This is the 5.1 firmware that reboot correctly but ethernet is not working (M8S(n200c)_to_M8S+ 5.1 20151022-aml_upgrade_package) here https://mega.nz/#!ZUxQSJQK!nt8g1nGV6...aLQuUIGK-c-jbg
Can someone help me with this
highpoiss said:
Hi,
Did install this rom provided by d4nielr on my device M8S CS 812M8 V1.3 20150921
Install was perfect boot once and there was a working 5.1 rom with ethernet
Only if i reboot my device its bricked. red licht only recover whith USB burning tool
This is the 5.1 firmware that reboot correctly but ethernet is not working (M8S(n200c)_to_M8S+ 5.1 20151022-aml_upgrade_package) here https://mega.nz/#!ZUxQSJQK!nt8g1nGV6...aLQuUIGK-c-jbg
Can someone help me with this
Click to expand...
Click to collapse
I had the exact same problem when trying to upgrade to something M8S+ based. Worked perfectly the first time, but I could not start it up after a cold boot. Have you tried my original approach instead using the Team DevDigitel ROM?
MyM8SFinallyWorks said:
I had the exact same problem when trying to upgrade to something M8S+ based. Worked perfectly the first time, but I could not start it up after a cold boot. Have you tried my original approach instead using the Team DevDigitel ROM?
Click to expand...
Click to collapse
Yes did try your approach only the acemax 5.1 firmware wil instal but i have a direct brick at first boot red licht only recover whith USB burning tool
highpoiss said:
Yes did try your approach only the acemax 5.1 firmware wil instal but i have a direct brick at first boot red licht only recover whith USB burning tool
Click to expand...
Click to collapse
And what happens if you first go back to your stock Kitkat 4.4 ROM (with USB burning tool), and then try with my original approach (with SD card)?
MyM8SFinallyWorks said:
And what happens if you first go back to your stock Kitkat 4.4 ROM (with USB burning tool), and then try with my original approach (with SD card)?
Click to expand...
Click to collapse
Same problem installing acemax firmware over original 4.4 rom wil brick my device brick at first boot.
Help needed M8S ap6360 v1.3 20150921
Can someone make a TRWP backup from this rom ? specially the boot file
Also want to know where to download the M8s+ rom what daniel uses in this treat
Thanks
Hi d4nielr,
Wanted to thank you for the excellent work in compiling this ROM to support m8s app6330.
After trying out various ROMs and in the process bricking my device several times and un-bricking it using the burning tool, I finally came across your forum.
Thanks for the wonderful rom and the installation was a breeze and smooth sailing throughout.
Btw, for the installation I can only use the other most USB port. If I insert the sd card into the inner most usb port, it will take me to the bootloader.
So, for the TEAMWIN logo to appears, I need to put the sd card into the outer most usb port which is located at the back of my m8s unit.
cheers.......
Update.....
Unfortunately, after a cold boot, it doesn't work any longer. Back to kitkat using usb burning tool.
"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.
Hey there!
I somehow managed to red light brick my x96 mini s905 1gb/8gb, p282 board!
Now the reset button does nothing. I can't boot from any Burn Cards I've made.
Using USB Burn Tool, yields an error at 4% (for every ROM I try including stock rom)
I now have to short the pins to get my pc to even recognize the box and when it does, it fails at 4% in usb burn tools. No matter what settings I use (erase bootloader, erase flash ect)
I've been told these amlogic devices are next to impossible to actually KILL! So is there anyone around XDA that can guide me here?
I'm not new to flashing ROMs (been doing it since my samsung s3 lol) and I have flashed plenty of android boxes without error until this one!
I have a feeling I somehow deleted the bootloader! WHAT DO I DO NOW?!?!
Thanks in advance. Hopefully I've given enough information.
no solution ever for this brick?
found a possible solution
Hi, I just openend a thread where I was able to unbrick my x96mini box
https://forum.xda-developers.com/an...lved-bricked-x96mini-red-led-display-t3992403
I think the problem with this is the power cable is not being conncted after USB detection.
The board doesn't have enough power through USB alone to properly work, so connecting the power jack is mandatory. I failed the first flashing attempt for this reason.
Hope this helps, even when it has been months since OP.
Hi folks, I'm hoping someone can help me unbrick my MXQ Pro 4k. I've searched high and low for the stock firmware but it is nowhere to be found. My box seems to be a peculiar variant and the specs are as follow:
S905x 1GB/8GB S905XQ_V2.0 2017.05.16
SV6051P Wifi
SK Hynix H27UCG812ETR DDR3
It became bricked when I tried to flash different atvXperience firmware img files with the Amlogic USB burn tool. I had successfully flashed it with a version posted by minixfreak on the freaktab forums.
Although not with exactly the same specs, it worked pretty well except for the remote control wouldn't function. So I tried to flash again with what I thought was the stock firmware but unfortunately, that bricked the box pretty good. I tried to revert to the atvXperience firmware that worked from the post, but it now always fails at 7% when trying to format with USB tool. In all cases, I've tried every possible combination of pushing in the reset button in the AV port, shorting the NAND pins, switching the order of USB ports... The box always has a red light when powered and is always recognized by the USB Burn Tool driver when connected to the OTG port on the box but always stops at 7% when it attempts to format.
I hooked up a serial usb/ttl cable to capture boot output, turned on the box and it seems the box is in an infinite loop with the following output:
LOOP:8F;EMMC:800;NAND:85;SD:800;USB:8;LOOP:90;EMMC :800;NAND:85;SD:800;USB:8. It appears the bootloader is corrupt or maybe has been erased.
I tried making a bootable sd card using both burncard maker and bootcard maker but that didn't work either as it can't get past intial boot attempt, even pressing reset or shorting nand pins. I'm not sure if it's because of the boot loop or perhaps incorrect firmware. I haven't been able to find the definitive stock firmware anywhere. I would appreciate help in finding this elusive firmware.
I've scoured the internet for a solution and tried many different things but nothing can get me out of this loop. I'm now at a dead end.
I once had a bricked router that I was able to fix by connecting usb/ttl and putty and repeatedly hitting Ctrl-C after rebooting to get a CFE prompt. At that point I was able to manually flash the router with firmware and revive it. Maybe there's a tool available that would possibly do something like that with the android box?
Also possible I guess that something in the hardware is toast and it's just a paper weight now. Anyway, any help and suggestions would be appreciated.
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