Hello
i tryed to flash a new rom on a Mxq Pro 4k s905w
and now i have bricked it
the board code is S905xQ4_V3.0 218.10.16 but the chip is a s905w
i tried various roms
burning tool recognizes it every time
but at burning tool i get a [0x32030201]Uboot/Get result/DiskInitial error
without erase bootloader a [0x10302001]Romcode/Switch status/Check connect/Enum device error
with burn sd card maker the update starts but then hangs i tested it 8 hours
can anyone help to unbrick it ?
https://drive.google.com/open?id=15HZVAGyQU-KN2_9V-PqMFQMZVoUdvC9l
try this with the included burn tool
udaredme said:
https://drive.google.com/open?id=15HZVAGyQU-KN2_9V-PqMFQMZVoUdvC9l
try this with the included burn tool
Click to expand...
Click to collapse
i tried this but sadly the same error
i tried to short the nand maybe i fryed the nand ?
here is my log:
[17:31:21 378][Global][Inf]--Get burning key
[17:32:08 369][Global][Inf]--User click start button
[17:32:08 369][Global][Inf]--SetErase
[17:32:08 369][Global][Inf]--Enable burning 1
[17:32:08 369][Global][Inf]--Scan usb device
[17:32:08 369][Global][Inf]--Aml scan WorldCup Device
[17:32:08 384][HUB1-6][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#5&1275f893&0&6#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 0x0000035c
[17:32:08 384][Global][Inf]--Host: VIA USB erweiterter Hostcontroller
[17:32:08 384][Global][Inf]--DevPath:\\?\pci#ven_1106&dev_3104&subsys_72531462&rev_86#3&2411e6fe&0&84#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[17:32:08 384][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&9d04f33&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[17:32:08 384][Global][Inf]-------->[Port0]Other device
[17:32:08 384][Global][Inf]-------->[Port1]NoDeviceConnected
[17:32:08 384][Global][Inf]-------->[Port2]NoDeviceConnected
[17:32:08 384][Global][Inf]-------->[Port3]NoDeviceConnected
[17:32:08 384][Global][Inf]-------->[Port4]NoDeviceConnected
[17:32:08 400][Global][Inf]-------->[Port5]\\?\usb#vid_1b8e&pid_c003#5&1275f893&0&6#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
[17:32:08 400][Global][Inf]-------->[Port6]Other device
[17:32:08 400][Global][Inf]-------->[Port7]NoDeviceConnected
[17:32:08 400][Global][Inf]--Host: VIA Rev 5 oder höher USB universeller Hostcontroller
[17:32:08 400][Global][Inf]--DevPath:\\?\pci#ven_1106&dev_3038&subsys_72531462&rev_a0#3&2411e6fe&0&81#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[17:32:08 400][Global][Inf]---->Roothub:USB#ROOT_HUB#4&17f3b721&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[17:32:08 400][Global][Inf]-------->[Port0]Other device
[17:32:08 400][Global][Inf]-------->[Port1]Other device
[17:32:08 400][Global][Inf]--Host: VIA Rev 5 oder höher USB universeller Hostcontroller
[17:32:08 400][Global][Inf]--DevPath:\\?\pci#ven_1106&dev_3038&subsys_72531462&rev_a0#3&2411e6fe&0&83#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[17:32:08 400][Global][Inf]---->Roothub:USB#ROOT_HUB#4&1cc4e64&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[17:32:08 430][Global][Inf]-------->[Port0]NoDeviceConnected
[17:32:08 430][Global][Inf]-------->[Port1]NoDeviceConnected
[17:32:08 430][Global][Inf]--Host: VIA Rev 5 oder höher USB universeller Hostcontroller
[17:32:08 430][Global][Inf]--DevPath:\\?\pci#ven_1106&dev_3038&subsys_72531462&rev_a0#3&2411e6fe&0&80#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[17:32:08 430][Global][Inf]---->Roothub:USB#ROOT_HUB#4&53a067c&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[17:32:08 445][HUB1-6][Inf]--CloneImageProxy
[17:32:08 456][Global][Inf]-------->[Port0]NoDeviceConnected
[17:32:08 456][Global][Inf]-------->[Port1]NoDeviceConnected
[17:32:08 456][Global][Inf]--Host: VIA Rev 5 oder höher USB universeller Hostcontroller
[17:32:08 456][Global][Inf]--DevPath:\\?\pci#ven_1106&dev_3038&subsys_72531462&rev_a0#3&2411e6fe&0&82#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[17:32:08 456][Global][Inf]---->Roothub:USB#ROOT_HUB#4&2aad67c6&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[17:32:08 456][HUB1-6][Inf]--Connect path=VIA USB erweiterter Hostcontroller/P0/P5
[17:32:08 456][HUB1-6][Inf]--Start burning...
[17:32:08 483][Global][Inf]-------->[Port0]NoDeviceConnected
[17:32:08 483][Global][Inf]-------->[Port1]NoDeviceConnected
[17:32:08 483][Global][Inf]--Scan USB host controller complete
[17:32:08 483][Global][Inf]--Update data center with HubMap
[17:32:08 483][Global][Inf]--Update hub1 device data
[17:32:08 483][Global][Inf]--Update HUB1-1
[17:32:08 483][HUB1-1][Inf]--Update device path
[17:32:08 483][Global][Inf]--Update HUB1-2
[17:32:08 483][HUB1-2][Inf]--Update device path
[17:32:08 483][Global][Inf]--Update HUB1-3
[17:32:08 483][HUB1-3][Inf]--Update device path
[17:32:08 483][Global][Inf]--Update HUB1-4
[17:32:08 483][HUB1-4][Inf]--Update device path
[17:32:08 483][Global][Inf]--Update HUB1-5
[17:32:08 483][HUB1-5][Inf]--Update device path
[17:32:08 483][Global][Inf]--Update HUB1-6 \\?\usb#vid_1b8e&pid_c003#5&1275f893&0&6#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
[17:32:08 483][HUB1-6][Inf]--Update device path
[17:32:08 483][Global][Inf]--Update HUB1-7
[17:32:08 483][HUB1-7][Inf]--Update device path
[17:32:08 483][Global][Inf]--Update HUB1-8
[17:32:08 483][HUB1-8][Inf]--Update device path
[17:32:08 546][HUB1-6][Inf]--------------ERASE BOOTLOADER------------
[17:32:08 561][HUB1-6][Inf]--0-7-0-16
[17:32:08 561][HUB1-6][Inf]--Identify status success
[17:32:08 561][HUB1-6][Inf]-- low_power
[17:32:08 561][HUB1-6][Inf]--Low power command success
[17:32:08 561][HUB1-6][Inf]--Read low power success
[17:32:08 561][HUB1-6][Inf]--bootloader_is_old
[17:32:08 561][HUB1-6][Inf]--Bootloader command success
[17:32:08 577][HUB1-6][Err]--failed: bootloader is new
[17:32:08 577][HUB1-6][Inf]--Bootloader is new
[17:32:08 577][HUB1-6][Inf]-------------Download DDR.USB-----------
[17:32:08 577][HUB1-6][Inf]--Close device handle 0x0000035c
[17:32:08 655][HUB1-6][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#5&1275f893&0&6#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 0x0000035c
[17:32:08 717][HUB1-6][Inf]--0-7-0-16
[17:32:08 717][HUB1-6][Inf]--No need download
[17:32:08 717][HUB1-6][Inf]-------------Download UBOOT.USB-----------
[17:32:08 717][HUB1-6][Inf]--0-7-0-16
[17:32:08 717][HUB1-6][Inf]--No need download
[17:32:08 717][HUB1-6][Inf]-- low_power
[17:32:08 717][HUB1-6][Inf]--Send command success
[17:32:08 717][HUB1-6][Inf]--Read command status success
[17:32:08 717][HUB1-6][Inf]-------------Download meson1.dtb-----------
[17:32:08 717][HUB1-6][Inf]--0-7-0-16
[17:32:08 749][HUB1-6][Inf]-- download mem dtb normal 88064
[17:32:08 749][HUB1-6][Inf]--Send download command success
[17:32:08 764][HUB1-6][Inf]--Read command status success
[17:32:08 780][HUB1-6][Inf]--Transfer complete
[17:32:08 780][HUB1-6][Inf]--Send download get_status command succeed
[17:32:08 780][HUB1-6][Inf]--get_status success
[17:32:09 295][HUB1-6][Inf]-------------ERASE FLASH-----------
[17:32:09 295][HUB1-6][Inf]--disk_initial 1
[17:32:09 295][HUB1-6][Inf]--Send command success
[17:32:09 514][HUB1-6][Err]--failed:[17:32:09 514][HUB1-6][Err]--Check command return failed
[17:32:09 561][HUB1-6][Err]--[0x30201004]UBOOT/Disk initialize/Send command/Error result
[17:32:09 561][HUB1-6][Inf]--Close device handle 0x0000035c
[17:33:01 577][Global][War]--User click stop button
[17:33:01 577][Global][Inf]--Enable burning 0
Hmm. I haven't seen that issue yet. I bricked mine so many times playing lol. Always able to recover, well so far...have you tried installing twrp and recovery that way? How far does it go when trying with burn tool? 4%?
udaredme said:
Hmm. I haven't seen that issue yet. I bricked mine so many times playing lol. Always able to recover, well so far...have you tried installing twrp and recovery that way? How far does it go when trying with burn tool? 4%?
Click to expand...
Click to collapse
burn tool hangs at 4% then the device disconnects
twrp sounds good how to flash it?
do you have a link ?
It it hangs at 4% that's a key sign it's the wrong firmware. Have you tried contacting the seller you purchased it from for factory firmware? It's so difficult to find compatible factory firmware for these boxes, hence me doing what I do. I have a few more variants, I'll host them for you to try. It's an annoying time consuming process but maybe we can get lucky.
udaredme said:
It it hangs at 4% that's a key sign it's the wrong firmware. Have you tried contacting the seller you purchased it from for factory firmware? It's so difficult to find compatible factory firmware for these boxes, hence me doing what I do. I have a few more variants, I'll host them for you to try. It's an annoying time consuming process but maybe we can get lucky.
Click to expand...
Click to collapse
https://drive.google.com/drive/folders/1BkeycJHxBl6bVLMbqxyabRcH4ZaWfYNx?usp=sharing
heres twrp and a few variants of stock fw
udaredme said:
https://drive.google.com/drive/folders/1BkeycJHxBl6bVLMbqxyabRcH4ZaWfYNx?usp=sharing
heres twrp and a few variants of stock fw
Click to expand...
Click to collapse
how long have you had the box? Going by the sticker numbers it could be a newer box. They have different firmware that i'm not as familiar with. I'll do some searching if the above firmwares do not work. Hope this helps.
---------- Post added at 11:40 AM ---------- Previous post was at 11:30 AM ----------
udaredme said:
how long have you had the box? Going by the sticker numbers it could be a newer box. They have different firmware that i'm not as familiar with. I'll do some searching if the above firmwares do not work. Hope this helps.
Click to expand...
Click to collapse
https://www.youtube.com/redirect?q=...m7Lto1njUpCqvf7h8MTU1MjM4NjgwM0AxNTUyMzAwNDAz
udaredme said:
how long have you had the box? Going by the sticker numbers it could be a newer box. They have different firmware that i'm not as familiar with. I'll do some searching if the above firmwares do not work. Hope this helps.
---------- Post added at 11:40 AM ---------- Previous post was at 11:30 AM ----------
https://www.youtube.com/redirect?q=...m7Lto1njUpCqvf7h8MTU1MjM4NjgwM0AxNTUyMzAwNDAz
Click to expand...
Click to collapse
many thanks for the help :good:
but i give up
i have found a s905x box for 15 € i will try this one
here are some pictures of the board:
Never give up! I cant count how many firmware variations I went thru trying with my mxq pro box...If I had given up I wouldnt have been able to port the atvxperience rom over to it!
I would ask the company you purchased it from for the firmware, if you havent already..
i found out that i really damaged the emmc
i made a sd with boot card maker with the right uboot from an image and have it up and runnunig from sd card
Glad you found a way to get it up and going! nice troubleshooting!
timelord666 said:
i found out that i really damaged the emmc
i made a sd with boot card maker with the right uboot from an image and have it up and runnunig from sd card
Click to expand...
Click to collapse
How did you find out that you damaged the emmc?
AzorAhai2222 said:
How did you find out that you damaged the emmc?
Click to expand...
Click to collapse
i have got a 905x box and tested flashing with this box no problems at all
i have shorted the 905w very hard because i dont find a shot manual for it
so i guessed it
i have found this thread:
https://discourse.coreelec.org/t/tr...s-like-corrupted-dead-internal-memory/1452/64
and this worked for me
i wanted to use coreelec mainly and android as second to play
so now i use this box only with coreelec
timelord666 said:
i have got a 905x box and tested flashing with this box no problems at all
i have shorted the 905w very hard because i dont find a shot manual for it
so i guessed it
i have found this thread:
------
and this worked for me
i wanted to use coreelec mainly and android as second to play
so now i use this box only with coreelec
Click to expand...
Click to collapse
You was using the wrong img file i'm 100% sure
Let me tell you something about china. THERE'S NO COPYRIGHT THERE. You have an mxq pro 4k s90w box with s905xq4_v3 board inside. Your box use the same code like a tx3 mini. It's like you have a BMW with Mercedes Motor. That's china (Beautiful).
How ever...
The correct img for your box is "TX3Mini-20181210.img" google for it.
1. Download the TX3Mini-20181210.img (EXACTLY THIS IMAGE)
2. Download USB Burning Tool v2.1.3 / v2.1.6 and install it
2.1 //Start USB Burning Tool and connect your box usb to be sure your driver is installed and loaded//
2.2 //If Driver is installed remove the usb cable again.
3. Load img file in Burning Tool and press Start
4. connect again the usb cable without pressing the reset button. (This mainboard have a reset button but it's not needed)
5. Wait for 100%
6. Enjoy your new tx3 mini in a mxq pro4k case
Edit: There's a zip update for the tx3 to use libreelec and android dual boot. Not sure if it will works for that board.
AzorAhai2222 said:
You was using the wrong img file i'm 100% sure
Let me tell you something about china. THERE'S NO COPYRIGHT THERE. You have an mxq pro 4k s90w box with s905xq4_v3 board inside. Your box use the same code like a tx3 mini. It's like you have a BMW with Mercedes Motor. That's china (Beautiful).
How ever...
The correct img for your box is "TX3Mini-20181210.img" google for it.
1. Download the TX3Mini-20181210.img (EXACTLY THIS IMAGE)
2. Download USB Burning Tool v2.1.3 / v2.1.6 and install it
2.1 //Start USB Burning Tool and connect your box usb to be sure your driver is installed and loaded//
2.2 //If Driver is installed remove the usb cable again.
3. Load img file in Burning Tool and press Start
4. connect again the usb cable without pressing the reset button. (This mainboard have a reset button but it's not needed)
5. Wait for 100%
6. Enjoy your new tx3 mini in a mxq pro4k case
Edit: There's a zip update for the tx3 to use libreelec and android dual boot. Not sure if it will works for that board.
Click to expand...
Click to collapse
didn't try the edit so can't say if that works. The above portion was a lifesaver and fixed my mxq pro s905w 2019 with s905xq4_v3.0 mb.
Same Box Same Problem
I tried to flash TWRP and box got bricked (MXQ Pro 4k S905W with android 7.1.2). Now there is no recovery in it and the box won't start. Every time I switch it on, the box shows up a blue light, then a green green comes up on TV for a fraction of a second and the black screen. Tried PC and SD card version firmwares to flash, but the box is not recognized by the burner. Anybody got any solution, please...
MXQ Red Light
Ok Heres my problem, I have a MXQ Pro 4K in the board it says MXQ S905W V2.0 another sticker says MXQ S905w 6051-7118052
it was working fine but stopped working and has only the red light. I have tried many times to flash the firmware and only goes to 7% I have not taken the heat sink off to see wish chip it has because I am afraid to loosen other components and not being able to fix the box. I don't know the boot loader number. do you guys have any suggestion on what I can do to un brick this box and have it working again? please help me:crying:
timelord666 said:
i found out that i really damaged the emmc
i made a sd with boot card maker with the right uboot from an image and have it up and runnunig from sd card
Click to expand...
Click to collapse
Hello, help me by indicating how you did it or leave me your email to write to you. I thank you in advance :dedos cruzados:
Deleted
Sorry, replying to a year old post
Related
Hello to all,
Everything went wrong on flashing with SP Flash tool. The Preloader of Scattered file was checked and all others.
The problem is strange for me and I see that there are other with the same issue without an answer.
Fist of all I did everything described in forums. The driver of MT Preloader Vcom port is installed correctly. In Device Manager LTP com port is detected and as it is normal it disconnects in 2-5 seconds. If I change the USB port on PC it changes the COM port which is the previous detected.
The issue is that my latest SP Flash Tool 5.14 or even 3.13 older one, can't establish permanent connection with the COM port of the MTK 6589. I tested with different cables and different OS (XP and Windows 7 32 bit) on different computers with first pressing Download button of SP Flash Tool and then plugging the cable. If I don't press Volume Down button of my Huawei Ascend G610s it can't be dected of SP Flash. After pressing Volume Down the enters into Meta mode BUT .... SP Flash Tool report:
BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004)
[H/W] Fail to download DA to baseband chip's internal SRAM
[HINT]: 1. There's an cable communication problem between FlashTool and BootROM.
2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION]
1. Try again.
2. Proceed H/W checking in download cable and target side com port.
3. Monitor if power-drop occured in target side.
At some reason COM port is constantly disconnecting and connecting without establishing permanent connection with SP Flash Tool. The red bar pops up and shows 100% done.
Any idea for this issue? You will help a lot of people which don't have the answer what to do.
Best Regards
niki_help said:
Hello to all,
Everything went wrong on flashing with SP Flash tool. The Preloader of Scattered file was checked and all others.
The problem is strange for me and I see that there are other with the same issue without an answer.
Fist of all I did everything described in forums. The driver of MT Preloader Vcom port is installed correctly. In Device Manager LTP com port is detected and as it is normal it disconnects in 2-5 seconds. If I change the USB port on PC it changes the COM port which is the previous detected.
The issue is that my latest SP Flash Tool 5.14 or even 3.13 older one, can't establish permanent connection with the COM port of the MTK 6589. I tested with different cables and different OS (XP and Windows 7 32 bit) on different computers with first pressing Download button of SP Flash Tool and then plugging the cable. If I don't press Volume Down button of my Huawei Ascend G610s it can't be dected of SP Flash. After pressing Volume Down the enters into Meta mode BUT .... SP Flash Tool report:
BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004)
[H/W] Fail to download DA to baseband chip's internal SRAM
[HINT]: 1. There's an cable communication problem between FlashTool and BootROM.
2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION]
1. Try again.
2. Proceed H/W checking in download cable and target side com port.
3. Monitor if power-drop occured in target side.
At some reason COM port is constantly disconnecting and connecting without establishing permanent connection with SP Flash Tool. The red bar pops up and shows 100% done.
Any idea for this issue? You will help a lot of people which don't have the answer what to do.
Best Regards
Click to expand...
Click to collapse
I have the same problem please help
Hi ...what is the phone model?
In my case the issue was solved with a hardware "kick" with button combination because at some reason the MTK preloader was put the phone in nonsense turning on and off the without being able to establish permanent connection. I tried all the MTK drivers but the issue was some kind of bug which actually was constant switching off. My model phone was Huawei G610s. What I did was to hold Power, +, - button together for about 5 seconds then release power still holding + and - button, and after 4-5 seconds release + button while holding - button for 4 seconds. This kicked out from the constant disconnection and SP flash tool was able to finalize the flash. Without this every time the error was as your have described.
Hello everyone,
I have a situation that has around 4 months now, and I can't fix it even after reading every piece of information I could grab on this forum and google.
I'm usually the guy that prefers to play safe and not flash any kind of Android device to avoid this kind of headaches, but out of the blue (i believe it was a power grid failure), my box wouldn't boot past the logo. It's a Mini M8S II (S905X). I contacted the support at Gearbest (where I bought it) and they said it could not be fixed and refunded half the money. So no luck there.
After 4 months of research and testing and failing to unbrick this box, here are the conclusions I took:
- When I try to flash any firmware with USB Burning Tool it recognizes easily, but always stops at 7% (U-Boot/Send Command Error or something like that). Tried 2 cables, 2,0 and 3.0 USB ports, and different versions of USB Burning Tool (had time to try many combinations)
- When I try to flash any firmware with SD Card, it shows the cute and lovely android but ends up with a red cross on the end. (tried all kinds of combinations with the erasing flash option, all types of firmwares I could find for this box, etc)
- When I try to access the recovery without SD Card using the toothpick, nothing happens.
- I tried the "sd_MINIM8SII_rv102" extracted to the sd card, nothing happened.
- Tryed many firmwares with USB Burning Tool, rv109, rv112, and others for S905X...... nothing goes in this box =/
After some deeper research, I tried extracting the "update.zip" from "sd_MINIM8SII_rv102" to sd card and replacing the recovery.img with the one from TWRP for S905X v3.0.2. It boots successfully to TWRP asking if I want to keep the system read-only. (at this point I saw the light at the end of the tunnel) Tried right away to flash a firmware from it, failing with messages saying the are no mounting points for /data and no /system partition and what not. Then I noticed the internal memory says 0Mb, in the recovery. Is that the problem?
I've also seen stuff like dropping a u-boot.bin (tried botfap's u-boot.bin.sd.bin) and stopping u-boot to access u-boot shell. From there you can flash the recovery.img and dtb.img and stuff like that. Can't find much information on that and didn't had much luck with it either.
What am I missing? what can I do? I'm up for anything other than using this Box as a tall beer coaster.
How about the short circuit method? I'm lost.... I just want it working again =(
Here goes some images with the error from USB Burning Tool:
imgur.com/a/GFhJu
imgur.com/a/5LIn5
Have you tried starting usb tool flash and then plugging in the box after flashing already started in software? That worked for me. Found the fix on another forum.
Sent from my SM-G900V using Tapatalk
Koognod said:
Have you tried starting usb tool flash and then plugging in the box after flashing already started in software? That worked for me. Found the fix on another forum.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
If you mean pressing start on usb burning tool and then plug the USB cable. Then yes, tryed it several times with many diferent ROM's =( always the same output.
It was one of the many tricks/tips i've found. But still no difference..... thank you tho!
when u get error message at usb burning tool after press start, just continue with reconecting usb cable with and w/o press reset button..
actually last hour i get some trouble like you, error in usb burning tool because device disconected automaticly after 10 second maybe, but i just try recconect the usb cable, n viola, usb burning working n install my rom..
i think if your pc still recognizing ur tv box via usb cable, u still can doing flash with that usb burning..
clasie said:
when u get error message at usb burning tool after press start, just continue with reconecting usb cable with and w/o press reset button..
actually last hour i get some trouble like you, error in usb burning tool because device disconected automaticly after 10 second maybe, but i just try recconect the usb cable, n viola, usb burning working n install my rom..
i think if your pc still recognizing ur tv box via usb cable, u still can doing flash with that usb burning..
Click to expand...
Click to collapse
Thats what I thought, if the USB Burning Tool recognizes there is hope!! lol
but the truth is.... I keep hearing the "Keep trying" on several forum topics...... I try reconnecting and refreshing several times..... I tryed with several USB Burning Tool versions, I tryed with several combinations of installing drivers with and without the reset button when connecting...... several things....... the computer sometimes recognizes as "GX-CHIP" and sometimes as "Worldcup Device"........ would there be the problem? I keep hiting the 7% wall with the "UBOOT/Disk initialize/Send command/Error result" message..... very frustrating! =/
Here goes more information from the error log:
[20:04:54 876][HUB1-2][Inf]--Device is connected
[20:04:54 876][HUB1-2][Inf]--Close device handle 0x00000660
[20:04:54 938][HUB1-2][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#5&1003806&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 0x000008c0
[20:05:00 001][HUB1-2][Inf]--0-7-0-16
[20:05:00 002][HUB1-2][Inf]--CheckFileRunState succeed
[20:05:00 002][HUB1-2][Inf]-- low_power
[20:05:00 007][HUB1-2][Inf]--Send command success
[20:05:00 010][HUB1-2][Inf]--Read command status success
[20:05:00 010][HUB1-2][Inf]-------------Download meson1.dtb-----------
[20:05:00 012][HUB1-2][Inf]--0-7-0-16
[20:05:00 012][HUB1-2][Inf]-- download mem dtb normal 79872
[20:05:00 012][HUB1-2][Inf]--Send download command success
[20:05:00 025][HUB1-2][Inf]--Read command status success
[20:05:00 037][HUB1-2][Inf]--Transfer complete
[20:05:00 037][HUB1-2][Inf]--Send download get_status command succeed
[20:05:00 041][HUB1-2][Inf]--get_status success
[20:05:00 542][HUB1-2][Inf]-------------ERASE FLASH-----------
[20:05:00 542][HUB1-2][Inf]--disk_initial 1
[20:05:00 542][HUB1-2][Inf]--Send command success
[20:05:01 671][HUB1-2][Err]--failed:[20:05:01 671][HUB1-2][Err]--Check command return failed
[20:05:01 688][HUB1-2][Err]--[0x30201004]UBOOT/Disk initialize/Send command/Error result
have you ever managed to resolve this issue?
Hello everyone. I was trying to downgrade from emui 8.1 to emui 8 using the dload method. Everything was fine until the phone rebooted and nothing was showing on the display. I let it sit for about an hour and still nothing. The phone was completely unresponsive. Plugging it into a computer, windows recognized it as a kedacom usb device named Android bootloader interface. At this point, I tried to flash the board software using the image downloader software for Hisilicon devices. Unfortunately, it did not work and gave me error 29. I realized at this point I needed to put my phone into com1 mode, so I opened it up and found the probe point near the lcd connector. I disconnected the battery and lcd connector and plugged the phone into my laptop. I shorted that test point with ground and windows still recognized it as kedacom usb device named Android bootloader interface. I tried reinstalling the huawei drivers provided by the software, but I just can't get windows to recognize it as huawei com1 interface. Am I doing something wrong here? Is it the wrong probe point I am shorting? Any help would be appreciated! Btw the bootloader is locked and phone is not rooted.
Phone's actual configuration - for whatever reson - is to boot into it's bootloader.
Try
Code:
fastboot devices
fastboot reboot
to get phone booted in default mode.
jwoegerbauer said:
Phone's actual configuration - for whatever reson - is to boot into it's bootloader.
Try
Code:
fastboot devices
fastboot reboot
to get phone booted in default mode.
Click to expand...
Click to collapse
Yes I have tried that and still nothing shows up on the screen. Device manager still shows it as a kedacom device called android bootloader interface.
WayneSeng said:
Yes I have tried that and still nothing shows up on the screen. Device manager still shows it as a kedacom device called android bootloader interface.
Click to expand...
Click to collapse
Get rid of KEDACOM USB DEVICE DRIVER, what is for Xiaomi devices, AFAIK.
Install the HUAWEI ANDROID USB DRIVER: this driver resolves all USB connection issues between Huawei Android Smartphone / Tablet and Windows 10/8.1/7 PC. It addresses all connection issues, be it transferring files between Huawei device and PC, or debugging over ADB and Fastboot.
jwoegerbauer said:
Get rid of KEDACOM USB DEVICE DRIVER, what is for Xiaomi devices, AFAIK.
Install the HUAWEI ANDROID USB DRIVER: this driver resolves all USB connection issues between Huawei Android Smartphone / Tablet and Windows 10/8.1/7 PC. It addresses all connection issues, be it transferring files between Huawei device and PC, or debugging over ADB and Fastboot.
Click to expand...
Click to collapse
Ok, so I uninstalled the kedacom usb driver and installed the huawei usb drivers. After restarting my laptop and plugging in my phone, device manager shows it as Android phone called Android sooner single adb device. Flashing the board software using Hisilicon image tool gave me error 39.
WayneSeng said:
Flashing the board software using Hisilicon image tool gave me error 39.
Click to expand...
Click to collapse
Can't help you further: don't have a device based on Hisilicon Kirin chipset.
jwoegerbauer said:
Can't help you further: don't have a device based on Hisilicon Kirin chipset.
Click to expand...
Click to collapse
What do you mean? I have a mate 10 pro bla-al00 with a kirin 970 chipset. My issue is not with connection, but with getting the phone into com1 mode and flashing the board firmware in order to unbrick the phone. Here is a tutorial I am following to do this: https://www.youtube.com/watch?v=SJxKH_unwAI&ab_channel=GSMTechZambia
I just can't get the phone into com1 mode. I short the testpoint shown in the video to ground with a piece of wire and all it does is reset the connection and device manager shows an adb device not the com port. Is it the wrong test point I am shorting to ground or am I doing something else wrong? Thanks
WayneSeng said:
What do you mean? I have a mate 10 pro bla-al00 with a kirin 970 chipset. My issue is not with connection, but with getting the phone into com1 mode and flashing the board firmware in order to unbrick the phone. Here is a tutorial I am following to do this:
I just can't get the phone into com1 mode. I short the testpoint shown in the video to ground with a piece of wire and all it does is reset the connection and device manager shows an adb device not the com port. Is it the wrong test point I am shorting to ground or am I doing something else wrong? Thanks
Click to expand...
Click to collapse
If You didnt solve, take a look at this:
HUAWEI MATE 10 HARD BRICK
Hello, i have a hard bricked Huawei mate 10 ALP-l29 with all partitions deleted. Bootloader is locked and no chance to unlock. Tried all services - nothing! Is it any hope? I like this phone damn.
forum.xda-developers.com
Hi community.
I have a problem with my Android Box X96 Max Plus with the Amlogic S905x3 Chip.
The problem is that i can't install anything on it. I sign in with my google account and i got Error 403 and error 192 when i tried to install something from the playstore.
So i cleared the data and the cache for the playstore and i tried another account. I also did a factory reset on the box. Nothing works.
After this i tried to install an apk from a usb stick with setting unknown sources "on" but this also didn't work (installation abort).
Next step i downloaded the latest firmware for the box and tried to installed it on recovery mode but the error 21 appeared.
I also tried to flash TRWP in recovery mode (with a usb stick) but the error 21 also appeared.
Do i have to unlock the bootloader first or is the only way to flash a firmware on the box with a flash tool and the connected box on the PC (with)?
Whats wrong with this box or is something wrong with me?
Can you help me?
Thanks
Matthias
hello
i had the same problem the only thing that fixed it is to update firmware but to do that you need to identify your box model first
1-then download latest firmware
2-download and install usb burning tools : https://androidmore.com/download/4004/?dlm-dp-dl-force=1&dlm-dp-dl-nonce=baef81bb4a
3- open the usb burning tools application
4- Click the second option on the top bar to reveal the option for changing the language to english
5- click on the File option and click import image to import your firmware .img file.
6- Make sure to untick the overwrite key box
7-connect your box using male to male usb cable (plug it in the blue usb 3.0) and wait for drivers to be installed
8- unplug your box
9-go back to application and click start
8-connect your box and wait for the flash processes to finish
9-when flash is done unplug your box and click stop close usb burning tools
connect your box to your tv and enjoy
SlamD said:
hello
i had the same problem the only thing that fixed it is to update firmware but to do that you need to identify your box model first
1-then download latest firmware
2-download and install usb burning tools : https://androidmore.com/download/4004/?dlm-dp-dl-force=1&dlm-dp-dl-nonce=baef81bb4a
3- open the usb burning tools application
4- Click the second option on the top bar to reveal the option for changing the language to english
5- click on the File option and click import image to import your firmware .img file.
6- Make sure to untick the overwrite key box
7-connect your box using male to male usb cable (plug it in the blue usb 3.0) and wait for drivers to be installed
8- unplug your box
9-go back to application and click start
8-connect your box and wait for the flash processes to finish
9-when flash is done unplug your box and click stop close usb burning tools
connect your box to your tv and enjoy
Click to expand...
Click to collapse
Thank you for your help
This will be my next step when I get the usb a to usb a cable.
Can you recommend any custom rom for the x96 max plus box?
Thank you in advance.
Beerle said:
Thank you for your help
This will be my next step when I get the usb a to usb a cable.
Can you recommend any custom rom for the x96 max plus box?
Thank you in advance.
Click to expand...
Click to collapse
you need to identify your box model first ( Plus , Plus2 , Plus100, etc )
if you have the 1000Mb Ethernet chip ( RTL8211F ) then you can try SLIMBOX ATV and AOSP last firmware (best one i have tested ):
project slimBOXtv
A project to create firmware for TV boxes and sticks with an Amlogic processor. Amlogic S905X, S905X2, S905X3, S912, S922, S905W, S905W4, S905Y2, S905L (Android 9) Amlogic S905X4, S905W2, S905Y4 (Android 11) slimBOXtv ATV and AOSP are two...
forum.xda-developers.com
I really like the slim box Version but i have another problem.
My internal storage says that I only have 32 GB but i ordered the 4/64gb Version (which also stand on the back of the Box). What's the problem?
ok i have figured out that i had a fake firmware on my box preinstalled when the box arrived. So i unfortunately have a 4/64 gb model.
For the solution in the topic, only flashing another firmware helped.
Kudos to SlamD for the help.
Hello, I wanted to flash a generic media box with Amlogic S912 chipset, and I was able to get TWRP installed, but unfortunately I forgot to make a backup of my official recovery. Now, I can't use the SDCard Burn tool or the USB Burning tool. If anyone could help me find a way to get the OG recovery back or flash the device using another method, that would be nice. Below I have listed some specs of the device:
Amlogic S912 CPU
2GB RAM/16GB Internal Storage
6.0.1 userdebug build rooted with Magisk (TWRP Installed)
hashbrun444 said:
...Now, I can't use the SDCard Burn tool or the USB Burning tool...
Click to expand...
Click to collapse
Is your device not detected in burnning tool anymore, find NAND Chip Mask ROM Mode Short Location !?