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?
Related
Hi
Sorry to bother, but i just got a new Star B92M but im having a rough time trying to update it and flash it with SP Flash Tool
So far, i have tried this
To flash with the SP_Flash_Tool_v3.1224.01 (i get BROM 3013 error)
To flash with the SP_Flash_Tool_v3.1224.0.sn85 ( i get the 8038 error)
I have tried to run each of them as administrator
I have tried to click on Firmware-> Upgrade as someone suggested on a post
I have installed the preloader drivers
I have tried by taking our the battery and plugging in then put the battery on
But i havent been able to flash it. The phone is not bricked, it runs as nothing has happened, i do think although, that recovery is messed after so many tries since there is the red triangle when i try it.
I dont know if it is normal, but everytime i plug the phone when its off for flashing, is like it gets connected by usb for 2 seconds then disconnected, but its weird because when the phone is on, the usb works like charms, no problems on computer ports either or the usb cable, it just happens when i connect it when the phone is off (preloader i guess), yet i have installed the proper drivers read in many tutorials
Is there any other way to flash it? or any solution to this problem? Sorry for the bad english
Thanks in advance.
Hello all,
I have a rooted Micromax A58 which was perfectly working. I did a full nandroid backup of it 2 days ago. On yesterday, I was moving some system app (google maps, play store etc) to SD with some software) so that I could increase the internal memory and install some other softwares. But, unfortunately, after that modification, the phone stopped working properly (it was stucking up when the BOLT logo was reached). So, I started it in recovery and do a wipe cache and factory reset. After that, the phone is always going to Factory Mode.
Then I tried to Flash the Stock ROM using Flash Tool but was unsuccessful multiple times. After the scatter file selected, when I clicked the 'Download' (or even firmware upgrade), all time time, the phone was disconnecting/reconnecting every now and then and nothing happened after (even though I already installed the Vcom and PdaNet driver in the PC). So, I had to quit. I am attaching herewith the logs of the Flash Tool lastly tried.
Now, when I am starting the phone power button, nothing is happening.. NOTHING but black screen...
I am a bit worried.. your help very much appreciated. Please let me know for any information needed. Thanks.
'No com port detected' error
I tried another time and the problem still there.. When in SP Flash Tool, I select scatter file, click 'Download' and connect the phone to PC, the process doesn't progress further. So, I have to finally click 'Stop' to quit. In the logs, it shows--
"No com port detected.."
Attaching the trace logs file herewith.
Please advice how to resolve the issue.. I am totally stuck now. Thanks.
Androhelp said:
Hello all,
I have a rooted Micromax A58 which was perfectly working. I did a full nandroid backup of it 2 days ago. On yesterday, I was moving some system app (google maps, play store etc) to SD with some software) so that I could increase the internal memory and install some other softwares. But, unfortunately, after that modification, the phone stopped working properly (it was stucking up when the BOLT logo was reached). So, I started it in recovery and do a wipe cache and factory reset. After that, the phone is always going to Factory Mode.
Then I tried to Flash the Stock ROM using Flash Tool but was unsuccessful multiple times. After the scatter file selected, when I clicked the 'Download' (or even firmware upgrade), all time time, the phone was disconnecting/reconnecting every now and then and nothing happened after (even though I already installed the Vcom and PdaNet driver in the PC). So, I had to quit. I am attaching herewith the logs of the Flash Tool lastly tried.
Now, when I am starting the phone power button, nothing is happening.. NOTHING but black screen...
I am a bit worried.. your help very much appreciated. Please let me know for any information needed. Thanks.
Click to expand...
Click to collapse
Try changing the ports, Cable etc or better off try on a different computer .
Port/Cable/PC change didn't help
kapil_dheer said:
Try changing the ports, Cable etc or better off try on a different computer .
Click to expand...
Click to collapse
Hello Kapil,
Thanks for the response. Yesterday I tried with separate laptop, but the same problem was there. Today, I tried with the different USB port.. but didn't help.
It seems that the driver can not recognize the device and when I connect the phone, it is just in a loop of disconnecting/re-connecting. Please advice further. Thanks.
Only option now seems is Service Centre.
The guys are pretty dumb. I've tested samsung motorola etc.....they don't even know what root is.
Maybe they'll be unable to identify what you tried to do.
You can give any reason for it not functioning.
Good luck.
kapil_dheer said:
Only option now seems is Service Centre.
The guys are pretty dumb. I've tested samsung motorola etc.....they don't even know what root is.
Maybe they'll be unable to identify what you tried to do.
You can give any reason for it not functioning.
Good luck.
Click to expand...
Click to collapse
Thank you Kapil for the advice. As Micromax service centre is not having a good reputation regarding these, so I would go for that option as the last resort.
Before that, can I please ask the other members for giving further advice if there is any option to try with.. Thanks for your help.
Managed to get phone reconized in PC usb-pls help further
Androhelp said:
Thank you Kapil for the advice. As Micromax service centre is not having a good reputation regarding these, so I would go for that option as the last resort.
Before that, can I please ask the other members for giving further advice if there is any option to try with.. Thanks for your help.
Click to expand...
Click to collapse
I have managed to get the phone recognized by PC usb now. But, when I try try the SP Flash utility to either Format or Download or Firmware update etc, it is throwing error like below--
09/16/2014 09:56:32.640 FlashTool[2212][3912][D]: APCore::Connection::ConnectDA(): Failed to Connect DA: S_FT_ENABLE_DRAM_FAIL(..\QT_FlashTool_Refactor\Conn\Connection.cpp,126)
09/16/2014 09:56:38.140 FlashTool[2212][3912][D]: BackgroundWorker::run(): BROM Exception! ( BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032)
[EMI] Enable DRAM Failed!
[HINT]:
Please check your load matches to your target which is to be downloaded.)((APCore::Connection::ConnectDA,..\QT_FlashTool_Refactor\Conn\Connection.cpp,127))(..\QT_FlashTool_Refactor\UI\src\BackgroundWorker.cpp,94)
09/16/2014 09:56:58.765 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device Removed.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,483)
09/16/2014 09:56:59.750 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device plug in.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,478)
09/16/2014 09:57:33.828 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device Removed.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,483)
09/16/2014 09:57:34.812 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device plug in.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,478)
09/16/2014 09:58:08.890 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device Removed.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,483)
09/16/2014 09:58:10.375 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device plug in.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,478)
I tried the above multiple times but everytime same error as above.
When tried to connect the phone (without battery) it is disconnect/reconnect in an endless loop.
When try to connect with battery, the disconnect/reconnect loop is gone (i.e.-stable) but sometime it can not identity phone ('Unknown Device').
Also tried to press volume down button along with battery inside, but showing 'Unknown Device' and Flash tool getting hanged.
I used the Stock Rom downloaded from xda site for my phone detailed below---
Android 4.2.2
Model Micromax A58
BaseBand version- MOLY.WR8.W1315.MD.WG.MP.V1.P11 2013/09/04 15:51
Kernel 3.4.5 [email protected] #1
Build Number Micromax A58_T09
I also have the good nandroid backup (if it could be of any use) but phone is dead now. Confused how to go forward. Please help.
Download in SP Flash Tool successful
Androhelp said:
I have managed to get the phone recognized by PC usb now. But, when I try try the SP Flash utility to either Format or Download or Firmware update etc, it is throwing error like below--
09/16/2014 09:56:32.640 FlashTool[2212][3912][D]: APCore::Connection::ConnectDA(): Failed to Connect DA: S_FT_ENABLE_DRAM_FAIL(..\QT_FlashTool_Refactor\Conn\Connection.cpp,126)
09/16/2014 09:56:38.140 FlashTool[2212][3912][D]: BackgroundWorker::run(): BROM Exception! ( BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032)
[EMI] Enable DRAM Failed!
[HINT]:
Please check your load matches to your target which is to be downloaded.)((APCore::Connection::ConnectDA,..\QT_FlashTool_Refactor\Conn\Connection.cpp,127))(..\QT_FlashTool_Refactor\UI\src\BackgroundWorker.cpp,94)
09/16/2014 09:56:58.765 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device Removed.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,483)
09/16/2014 09:56:59.750 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device plug in.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,478)
09/16/2014 09:57:33.828 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device Removed.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,483)
09/16/2014 09:57:34.812 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device plug in.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,478)
09/16/2014 09:58:08.890 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device Removed.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,483)
09/16/2014 09:58:10.375 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device plug in.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,478)
I tried the above multiple times but everytime same error as above.
When tried to connect the phone (without battery) it is disconnect/reconnect in an endless loop.
When try to connect with battery, the disconnect/reconnect loop is gone (i.e.-stable) but sometime it can not identity phone ('Unknown Device').
Also tried to press volume down button along with battery inside, but showing 'Unknown Device' and Flash tool getting hanged.
I used the Stock Rom downloaded from xda site for my phone detailed below---
Android 4.2.2
Model Micromax A58
BaseBand version- MOLY.WR8.W1315.MD.WG.MP.V1.P11 2013/09/04 15:51
Kernel 3.4.5 [email protected] #1
Build Number Micromax A58_T09
I also have the good nandroid backup (if it could be of any use) but phone is dead now. Confused how to go forward. Please help.
Click to expand...
Click to collapse
In the meanwhile, when trying to resolve the issue, I tried the following steps and after that, I lastly managed to 'download' the Stock ROM successfully in my phone (using the Windows XP OS)--
1) As I was always getting the SP Flash Tool error 4032 for last couple of days and which was clearly describing 'please check your load matches your target which is to be downloaded', so was investigating the root cause in details. Upon searching in the internet, I downloaded multiple version of Stock ROMs for my Micromax A58 model from different sources to give a try. When trying to 'Download' (in SP Flash Tool), the 'T_09' ROM (link given by 'alanvmathew') in the below mentioned URL worked for me.
http://forum.xda-developers.com/showthread.php?t=2610046&page=2
It is to be noted from the link that Micromax A58 model have 2 different Stock ROMs (i.e.- 'T_07' and 'T_09') which info I was missing all the time.
2) After identifying the scatter file in the SP Flash Tool and clicking the 'Download' option, I inserted battery in the phone and pressing the 'Power + Volume down' button, connected the device into the PC USB. Upon connected, the 'DA USB VCOM PORT' driver automatically installed and the 'Download' started and flashing of ROM went smooth. Finally, it ended up with green 'Download OK' message. Also attaching the snapshots herewith.
Will check the mobile and its performance further and revert back accordingly.
Lately during the morning after having my P9000 charged overnight it suddenly shut down and after that was completely unresponsive:
I tried powering it back on but it wouldn't (neither by pressing the power button nor in combination with volume+ or any other button).
I tried charging it again but the LED isn't lighting up so I'm guessing it's not actually charging either.
Then I tried to reanimate it with SPFT but realized that the phone wasn't recognized by the pc. When I pressed the volume+ button it was recognized as "MediaTek USB Port (COM3)" for some seconds but then disappeared again.
Despite of that I tried to flash the stock ROM 20160810 (as well as others - no difference). Every time I get the same error:
BROM ERROR: STATUS_DA_HASH_MISMATCH (-1073283068)
Also I tried to flash preloader only, without any difference.
Then I opened the cover, removed the battery and tried again - nothing changed: The pc recognizes my phone only when I'm pressing volume+ but throws the error above when trying to flash.
Next I shortened the GND point on the phone's mainboard to any test points, but couldn't bring the pc to recognize the phone.
Any ideas...? Does someone know what the error message means? I know that DA stands for "download agent".
You haven’t said much about as to what you had done with this phone prior to your issue, whether you have left your P9000 as standard with OTA updates or perhaps you have rooted, flashed a different Rom or changed its Kernel ?
It’s hard for anyone to give help easily without some background from you.
You're right, I bought it two weeks ago as a used part. To my knowledge it was left as standard (previous owner didn't seem to be skilled too much since some of his folders remained on the phone) and as far as I remember the installed ROM was 20160810, although I'm not 100% sure since I'm also new to android / not experienced with ROM versions and didn't write it down. At the end I believe the phone had never been rooted or changed kernel.
Maybe worth mentioning: The last two days before failure I noticed that the phone restarted one or two times per day.
@brager
There are two possibilities (or more)
1. It's hard bricked, so Google for a mtk hard unbrick guide
2. It's a battery related problem
Keep it two days plugged, or replace it
Keep in mind that the newest mtk software has to be installed on your computer
And try another cable first of all
1. It's hard bricked, so Google for a mtk hard unbrick guide
Click to expand...
Click to collapse
I've already performed all the steps in these mtk hard unbrick guides. I'm able to enter META mode but when I try to flash the preloader I get the error described above [BROM ERROR: STATUS_DA_HASH_MISMATCH (-1073283068)]
2. It's a battery related problem
Keep it two days plugged, or replace it
Click to expand...
Click to collapse
As far as I understand it flashing can/should be done without battery.
Keep in mind that the newest mtk software has to be installed on your computer
Click to expand...
Click to collapse
I was using SPFT 5.1524.00, now updated to SPFT 5.1628 and get nearly the same error: BROM ERROR: STATUS_DA_HASH_MISMATCH (0xC0070004)
And try another cable first of all
Click to expand...
Click to collapse
...didn't change anything.
I think the phone has a hardware problem and went to heaven.
Brom error: Status_da_hash_mismatch
brager said:
Lately during the morning after having my P9000 charged overnight it suddenly shut down and after that was completely unresponsive:
I tried powering it back on but it wouldn't (neither by pressing the power button nor in combination with volume+ or any other button).
I tried charging it again but the LED isn't lighting up so I'm guessing it's not actually charging either.
Then I tried to reanimate it with SPFT but realized that the phone wasn't recognized by the pc. When I pressed the volume+ button it was recognized as "MediaTek USB Port (COM3)" for some seconds but then disappeared again.
Despite of that I tried to flash the stock ROM 20160810 (as well as others - no difference). Every time I get the same error:
BROM ERROR: STATUS_DA_HASH_MISMATCH (-1073283068)
Also I tried to flash preloader only, without any difference.
Then I opened the cover, removed the battery and tried again - nothing changed: The pc recognizes my phone only when I'm pressing volume+ but throws the error above when trying to flash.
Next I shortened the GND point on the phone's mainboard to any test points, but couldn't bring the pc to recognize the phone.
Any ideas...? Does someone know what the error message means? I know that DA stands for "download agent".
Click to expand...
Click to collapse
google translate
Hello
I had the same problem, (error BROM ERROR: STATUS_DA_HASH_MISMATCH)
what I did: I use Windows 7 System
1- clear all drivers for smartphones with "usbdeview-2-17"
2- install Drivers "Drivers_Auto_Installer_v1.1236.00"
3- install "PdaNetA4170"
4- use "SP_Flash_Tool_v5.1708_Win" to flash the rom. first flash the preloader alone and then flash the others.
the problem was the bad installation of the drivers, after that everything went well for me.
try it can work for you too.
the mentioned software is easy to find on google
Help,I have the same problem
mmakdz said:
google translate
Hello
I had the same problem, (error BROM ERROR: STATUS_DA_HASH_MISMATCH)
what I did: I use Windows 7 System
1- clear all drivers for smartphones with "usbdeview-2-17"
2- install Drivers "Drivers_Auto_Installer_v1.1236.00"
3- install "PdaNetA4170"
4- use "SP_Flash_Tool_v5.1708_Win" to flash the rom. first flash the preloader alone and then flash the others.
the problem was the bad installation of the drivers, after that everything went well for me.
try it can work for you too.
the mentioned software is easy to find on google
Click to expand...
Click to collapse
It has been 2 days that i try to fix this problem,because i thought it was a driver problem i formatted my windows 7 and reinstalled everything.
This issue still persists and my phone is brand new.
Hello,
May be someone can help me
My box is bricked...
Every time i tried to flash with usb burning tool, the flash stop at 2% and I have this error:
[0x10105002]Romcode/Initialize DDR/Read Initialize status/USB Controm setup error
So I flash with SD all gone fine put I don't like the rom, so I retry with SD and now: no screen..
Original build was 709D0
I changed pc, I shortened usb cable, I try with and without power supply, I always push the restore button, I try different usb burning tool version and different stock firmware...
Same error code at 2% again and again..
I don’t know what to do...
HELP!
Thanks
Hello!!
Anybody can help please? I didn't find the solution...
Thanks
I've been booting LibreELEC/CoreELEC from SD card on my AZW (Beelink) W95 (S905W) box for years now. Yesterday I tried booting into the stock Android system (7.1 I think- I haven't done it for a while) but it wouldn't boot. Not being one to leave well enough alone I decided to try a reset using a toothpick in the reset hole by the power plug. It flashed the start screen for a split second and then stopped. After that it wouldn't boot off the CoreELEC SD card either.
I've tried a clean CoreELEC install, stock firmware, Amlogic Burn Card Maker, and TWRP on the SD card - none of them get me past a black screen.
I don't think the reset button is doing anything (I depress it while plugging in the power jack). In fact, I don't know if it ever worked. My box had previously always booted off a SD card if it was inserted in the slot without having to do anything special.
My box isn't completely dead but comatose. The signs of life are:
1) The blue LED comes on when I plug in the power cord.
2) After about 20 minutes or so the blue LED will go off. If I press the power button on the remote it comes back on.
3) My router sees it on my network as active. But I get connection refused when I try access it using Windows File Explorer or try to SSH into it using Putty.
4) When I insert a SD card into the slot it writes Andriod and LOST.DIR folders to it.
I haven't tried the Amlogic USB Burning Tool yet because I don't have an USB 2.0 Type A male to male cable - but I've ordered one. My concern is I won't be able to put it in reset mode since I'm not sure the reset button does anything (but I can feel it click).
Is there anything else I should try while I'm waiting for my cable to arrive?
Any recommendations on how I should proceed once my cable arrives?
Thanks
RKCRLR said:
I've been booting LibreELEC/CoreELEC from SD card on my AZW (Beelink) W95 (S905W) box for years now. Yesterday I tried booting into the stock Android system (7.1 I think- I haven't done it for a while) but it wouldn't boot. Not being one to leave well enough alone I decided to try a reset using a toothpick in the reset hole by the power plug. It flashed the start screen for a split second and then stopped. After that it wouldn't boot off the CoreELEC SD card either.
I've tried a clean CoreELEC install, stock firmware, Amlogic Burn Card Maker, and TWRP on the SD card - none of them get me past a black screen.
I don't think the reset button is doing anything (I depress it while plugging in the power jack). In fact, I don't know if it ever worked. My box had previously always booted off a SD card if it was inserted in the slot without having to do anything special.
My box isn't completely dead but comatose. The signs of life are:
1) The blue LED comes on when I plug in the power cord.
2) After about 20 minutes or so the blue LED will go off. If I press the power button on the remote it comes back on.
3) My router sees it on my network as active. But I get connection refused when I try access it using Windows File Explorer or try to SSH into it using Putty.
4) When I insert a SD card into the slot it writes Andriod and LOST.DIR folders to it.
I haven't tried the Amlogic USB Burning Tool yet because I don't have an USB 2.0 Type A male to male cable - but I've ordered one. My concern is I won't be able to put it in reset mode since I'm not sure the reset button does anything (but I can feel it click).
Is there anything else I should try while I'm waiting for my cable to arrive?
Any recommendations on how I should proceed once my cable arrives?
Thanks
Click to expand...
Click to collapse
Hi, your device seems to be in a strange state currently, only thing i can reccomend is trying a few firmwares to see what works for you, you should be able to flash most s905w based roms, if your device cant be detected by USB burn tool you might need to use ask Rom Mode" to force your box to be detected by burn tool, this makes it almost impossible to brick a box
Thanks for the suggestions, I'm a complete newbie at this.
Is the Ask ROM Mode an option in USB Burning Tool?
I have an OEM W95 firmware update file (in both .img and and an OTA in .zip format) but they may be older than what is currently on the box. I also found a TWRP file for the S905W. But I don't know how to use any of these.
I downloaded the AMLogic Tools 6.0.0 and tried the AMLogic Flash Tool since it seems to work through the Ethernet port. I assumed this because you access the box via an IP address but I really don't know. I watched the video but couldn't find any detailed instructions on how to use it.
When I pressed the Connect button it said it connected and I had the green Connected display (I was connecting through my LAN - I don't know if I should connect directly with an ethernet cable). I loaded my .img file and said Flash. It says it is flashing and a second or so later it says SUCCESS! However the box still doesn't boot. I tried both Boot and Recovery (I don't know which option I should choose). I think that the SUCCESS! message is incorrect since I get the message even if I press the Flash button without the box connected. However, I can't connect to the box without the ethernet cable connected so the connected message seems correct.
Am I using the AMLogic Flash Tool correctly?
I was thinking about trying the S905W atvExperience ROM but thought I'd wait until I got my USB cable before before doing something more drastic.
Any other suggestions?
Thanks
OK, so my male to male USB cable arrived and I managed to get my box un-bricked using AMLogic USB Burning tool with a factory .img file. It took several tries. I kept getting errors when it tried to erase the bootloader or would get to 7%, progress would stop for about a minute, and then Burning Tool would close.
I finally got it to proceed all the way by holding in the reset button, plugging in the USB cable (no power cable), and keeping the reset button pushed the whole time (I don't know if this was just a coincidence). Also, I hadn't closed Burning Tool after the previous error erasing the bootloader. I'm posting all this in case someone else has a similar problem.
After that, it still wouldn't boot of the CoreELEC SD card with the reset button pushed down. It would go straight into the Android OS. I got it to boot into CoreELEC by installing the Reboot to LibreELEC app. Now it always restarts in CoreELEC the way it used to when the SD card is left in. I think this is how I got LibreELEC working years ago.
So, now I'm contemplating installing atvXperience but I have a couple of questions:
What would be the best way to install atvXperience without being able to the reset button to put the box into recovery mode?
What would be the best way to prepare for not being able to use the reset button to put the box into recovery mode if something were to go wrong during flashing?
Thanks for any help.
OK, so my male to male USB cable arrived and I managed to get my box un-bricked using AMLogic USB Burning tool with a factory .img file. It took several tries. I kept getting errors when it tried to erase the bootloader or would get to 7%, progress would stop for about a minute, and then Burning Tool would close.
I finally got it to proceed all the way by holding in the reset button, plugging in the USB cable (no power cable), and keeping the reset button pushed the whole time (I don't know if this was just a coincidence). Also, I hadn't closed Burning Tool after the previous error erasing the bootloader. I'm posting all this in case someone else has a similar problem.
After that, it still wouldn't boot of the CoreELEC SD card with the reset button pushed down. It would go straight into the Android OS. I got it to boot into CoreELEC by installing the Reboot to LibreELEC app. Now it always restarts in CoreELEC the way it used to when the SD card is left in. I think this is how I got LibreELEC working years ago.
So, now I'm contemplating installing atvXperience but I have a couple of questions:
What would be the best way to install atvXperience without being able to the reset button to put the box into recovery mode? (I did try flashing atvXperience once using USB Burning Tool but I got the same error erasing bootloader)
What would be the best way to prepare for not being able to use the reset button to put the box into recovery mode if something were to go wrong during flashing?
Thanks for any help.
Another follow up post for anyone with the same problem. I did some searching and found out I'm not the only one with a box that the reset button doesn't work. A work around for them was to connect the male to male USB cable, load the image into Burning Tool, press Start, and then plug in the power supply. The image file would then start flashing.
However, my box would start booting as soon as I connected the USB cable (didn't need the power supply). So I loaded the image into Burning Tool, pressed Start, and then connected the USB cable. This appears to be the work around for my box (I probably did this when I got my box to recover the first time - holding the reset button was probably irrelevant).
This procedure works for the stock firmware but when I try to flash the atvXperience image file the box hangs at 7%. So I still need some help there.
Also, is there a ATV ROM better suited for my S905W box (2/16 GB)?
W95 is really ****ing box whenever you feel you get off from the current problem will be into next one.
I have installed atvx Rom but afterthat when I tried adian rom my device bricked.
Without Ubt flashing it's connect but as I start flash it's sound unknown device and give flash error