Hi, during a failed coreelec installation attempt, I bricked my box. Is there any solution to unbrick this model (905x procesor, 2gb ram) My PC don't reconize the device.
I bricked mine with Adrians ROM !!!!
rafix095 said:
Hi, during a failed coreelec installation attempt, I bricked my box. Is there any solution to unbrick this model (905x procesor, 2gb ram) My
Formingus said:
I bricked mine with Adrians ROM !!!!
Click to expand...
Click to collapse
PC don't reconize the device.
Click to expand...
Click to collapse
You may need to use mask rom mode, i have one of these boxes and it should work with my rom, how did you update? Usung USB urning tool? The SD cadrd methis of updating wont work ONLY usb burning tool works to upgrade to android 9 from amd older version see video i made here on how to unbrick
Updated via USB Burning tool that will no more work.. Device will not get recognized after flashing [v7.5] (MXQ) Aidan's ROM [S905X] [P212, P214 & P242] MXQ Pro 4K 1GB 2GB+ (720pUI & 210DPI)ky mut.img.
Can we please focus on one thread to avoid any mistake and make thing easier for both of US ?
aidanmacgregor said:
You may need to use mask rom mode, i have one of these boxes and it should work with my rom, how did you update? Usung USB urning tool? The SD cadrd methis of updating wont work ONLY usb burning tool works to upgrade to android 9 from amd older version see video i made here on how to unbrick
Click to expand...
Click to collapse
OK Problem is solved via MAskMode or as i call TestPoint ---- Now device is alive again
Formingus said:
OK Problem is solved via MAskMode or as i call TestPoint ---- Now device is alive again
Click to expand...
Click to collapse
Thanks once more for your support
Related
"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.
Hello, attempting to flash [S905X][FINAL]atvXperience seems to have hard bricked my Beelink Mini MX II III. Flashing failed with an X in front of the android guy, and now the box shows no signs of life. Any ideas for a fix?
Pictures of the board
https://imgur.com/a/ODPBNoZ
joeshmoe1 said:
Hello, attempting to flash [S905X][FINAL]atvXperience seems to have hard bricked my Beelink Mini MX II III. Flashing failed with an X in front of the android guy, and now the box shows no signs of life. Any ideas for a fix?
Pictures of the board
https://imgur.com/a/ODPBNoZ
Click to expand...
Click to collapse
Same hear, thats will happen when we flash some Andriano ROM and whatever they are called!! Nooobies rom
I have this device, try my android tv 9 rom and here is a video i made of how to unbrick your box
And see my rom here https://aidansrom.ml
aidanmacgregor said:
I have this device, try my android tv 9 rom and here is a video i made of how to unbrick your box
And see my rom here https://aidansrom.ml
Click to expand...
Click to collapse
Your rom bricked mine device. Mine device dont have TP
Formingus said:
Your rom bricked mine device. Mine device dont have TP
Click to expand...
Click to collapse
TP? not sure what you mean here, and are you installing using USB Burning Tool? this is the only way to upgrade to android 9, the SD card method wont work as android 9 has significant changes to partitions that the SD card method cant make
aidanmacgregor said:
TP? not sure what you mean here, and are you installing using USB Burning Tool? this is the only way to upgrade to android 9, the SD card method wont work as android 9 has significant changes to partitions that the SD card method cant make
Click to expand...
Click to collapse
Actually, i write to you on message and on the forum also and describe mine problem. Probably you didn't get or missed.
Downloaded all your ROMs for s905x and decide to test them.
Flashed few times two ROM's and everything was OK. Flashing via USB Burning Tool
1.[v7.5] (Nexbox) Aidan's ROM [S905X] Nexbox a95x 1GB 2GB+.img
2.[v7.5] (UNIVERSAL) Aidan's ROM [S905X] 1GB 2GB+.img
After i flash [v7.5] (MXQ) Aidan's ROM [S905X] [P212, P214 & P242] MXQ Pro 4K 1GB 2GB+ (720pUI & 210DPI).img
Box won't go anymore in Recovery mode.
USB Burn Tool will not recognize as a device anymore even reinstalled LIB Drivers and tested on 2 PC with Win 7 and Win 10
Via SD Card will not be recognized too - Fashing not start at all possible due missing recovery.
This Box don't have TP. There was no need to press the reset button to be connected when i flash with success, only inserting USB was enough. Now Box will start and hang on Aidans TV Logo and stay there forever. About Hardware its not 100% .
Mine Box is Beelink Mini MXIII 2GB-32GB S905X AnyHelp will be appreciated.
This is mine Box from hardware
Formingus said:
This is mine Box from hardware
Click to expand...
Click to collapse
Heres My Board & Points To Short
Your browser is not able to display this video.
Try just waiting.
Open USB, load other image which you knows it worked before, press Start immediately in USBT, than plug in your USB A-A and push the recovery button with toothpick. And than just wait. 5-15mins
Works every time with my box. No need to short anything.
/
severing77 said:
Hi! I am new here and I hope that I choose right spot for posting a thread.
Would someone be kind to help me please?
I have Android Box A95X F3, never had any issue. This morning I made some stupid mistake and I installed Magisk on it which flashed and booted some image. After it finished and I restarted device, system disappeared (dead Android logo is on screen). I tried to wipe data and do factory reset, but every time I press reboot system now it goes back to boot screen with dead Android logo.
Same screen as here appear: https://i.ytimg.com/vi/7E81YRF9ieY/maxresdefault.jpg
Can someone help me and say what should I do?
I have some experience with booting custom ROMs on Android phones, but I am not sure how to fix this on Android Box.
P.S. For booting system external to the device, how can I connect it with my PC? Do I need macho to macho USB cable?
Thanks in advance
Click to expand...
Click to collapse
i think you can't repair the system better to flash it using the usb burning tools and the last firmware for your box format img
SlamD said:
i think you can't repair the system better to flash it using the usb burning tools and the last firmware for your box format img
Click to expand...
Click to collapse
Can you give me guide to flash my a95x f3 air!!
SlamD said:
i think you can't repair the system better to flash it using the usb burning tools and the last firmware for your box format img
Click to expand...
Click to collapse
Hey friends,
Have you got any solution for this.
Because same thing happened with my A95x f3 box. I tried flashing rom by using burning tools but. Some error comes after 1 % process. May be I am flashing wrong image.
Can some please guide me where I can get correct from
Thanks
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
Hello everyone! I just found out my OTT Android TV from SDMC so if anyone have same device with me can you help me to get original firmware and probably custom rom? or maybe if anyone successfully rooted this device. thank you in advance.
I managed to unlock the bootloader but I can't go into mask mode & not detecting any devices in Amlogic Burn Tool
Try reboot update and then quickly plugging in usb cable. It should then be recognised by the burning tool.
kalehrl said:
Try reboot update and then quickly plugging in usb cable. It should then be recognised by the burning tool.
Click to expand...
Click to collapse
Same result, still not recognized by burning tool, but i have fastboot access
Maybe i need to change my M2M Cable?
Chicada said:
I managed to unlock the bootloader but I can't go into mask mode & not detecting any devices in Amlogic Burn Tool
Click to expand...
Click to collapse
what version Amlogic Burn Tool are you use ?
Refer to kalehrl's post below.
Normally yes, but oftentimes the operators disable the normal use of their device once the contract has expired and customers don't want to continue using the service. After a reset, you are greeted by a screen with the serial number of the device and you cannot proceed. So the only option is to flash the box with custom firmware loosing the widevine L1 and Google certification with Google chromecast in the process.
kalehrl said:
So the only option is to flash the box with custom firmware
Click to expand...
Click to collapse
I have deleted my opinion since you seem so sure about this. With such certitude, you couldn't possibly be wrong. Although you are.
kalehrl said:
Normally yes, but oftentimes the operators disable the normal use of their device once the contract has expired and customers don't want to continue using the service. After a reset, you are greeted by a screen with the serial number of the device and you cannot proceed. So the only option is to flash the box with custom firmware loosing the widevine L1 and Google certification with Google chromecast in the process.
Click to expand...
Click to collapse
I saw someone had success to connect the box with UBT , Thank you very much for your help and the tips!
nightbb said:
what version Amlogic Burn Tool are you use ?
Click to expand...
Click to collapse
V3.1.0