originally came in with a @9 startup logo, nothing else.
Tried the Matricom rescue, sd wih the HDDGURU burner, again, Matricom logo stuck.
Tried another, cant remeber, but, aml8726 HD18 compatable, and now got a black screen, unable to sd rescue, with any other rescue firmware or method!.
I do not need to push the reset button when connected to various versions of the Amlogic burning tool, I get HUB connected, strange?
But, when trying to burn with various firmware, the tool stops at 2%DDR with this messege:
[0x10105002]Romcode/InitializeDDR/Read initialise status/USB Control setup error
and remains in a loop! . I have tried to Maskrom, shorting pins 5 and 6, no change! Tried different USB cables, and USB sockets, to no vail
The box does not show up as a connected device on My Computer (Windows 10), but I get a sound that it is connected.
The box is not detected by other tools, like Moboro, Airdroid, Phoenix Suite,Iroot
The World Cup drivers are installed !
When the box is connected only with USB, not the power supply, the blue light is on and get a sound as if connected, without resetting the reset switch.
Any comments please ?
Related
I've searched around a few threads but not having much luck on this. I've started on a different computer totally from scratch several times and it just doesn't recognise that the phone has been plugged in. It's really quite irritating as the ODIN CF root method is literally 5 clicks and should take about 10 seconds to do.
I plug the phone into my PC while it's on and it detects it as the USB device and I can go into the folders and copy music on etc etc.
I switch it to download mode, plug it in and it does sod all. No windows beep to say it's plugged in a USB device. If I open ODIN then plug it in it's not doing the COM added.
I've tried installing then uninstalling kies then rebooting, installing just the USB driver, uninstalling, rebooting, reinstalling, rebooting. Just NOTHING seems to make my PCs detect that I've plugged the damn phone in when it's in download mode. It should be such an easy process but I'm left banging my head against the wall mid way through because it just refuses to acknowledge the device. I unplug, switch it on, plug back in and there it is, device connected. I've tried different computers, different USB ports. It doesn't show up in device manager even.
So my question: any idea as to why it will detect when the phone is on normally, but will not even think it's plugged in when switch on in download mode? And of course, how to fix it would be useful!
OK I fixed it.
I uninstalled the USB driver and restarted.
Downloaded/installed a new USB driver (specifically SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.23.0-retail).
Went to download mode and it picked it up straight away! ODIN worked in 10s as expected.
Found the instructions here, for reference. http://www.modaco.com/topic/361286-...-phones-15230-for-win-87vistaxp-adb-fastboot/
I installed a firmware I didn't like on my Scishion V88 PRO. I opened USB BURNING TOOL, connected my TV BOX (which does not have a reset button, not even inserting a toothpick into the AV input) to reinstall the previous firmware. But by connecting the USB cable to the PC, USB BURNING TOOL no longer detects the BOX! What may have happened? There is a solution?
NB: Before restarting the restoration, I had reset the device, and when I turn it on, only the AMLOGIC form appears and remains locked on it.
Thank you for those who will try to help me
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
Hello guys, recently my box (it's labelled as OTT A95X Pro, has an S905W, 2gigs of RAM and 16gb flash memory) died probably because I plugged it out of power while it was updating (didn't do it on purpose) and it seems that I have a corrupt bootloader. I can only see a red light now with the blue light never coming to life. I have tried a lot of ways to recover from this but I always get to a dead end. These are the following things I've tried:
- Used USB Burner Tool from AMLogic, my computer recognized the box straight away but I always can't get pass 2% when burning an image. Have tried over 15 different images for S905w and over 5 different versions of the tool with no success. Also tried changing the cable and even connected the box straight to the PC's motherboard USB header. Have also tried to burn in Windows 10, 7 and XP, unfortunately with the same results.
- Used AMLogic SD Card Burner, created the bootable SD card and actually the box managed to recognize it (blue light was on), but always after the updating screen I was getting an android logo with a cross next to it and was stuck there, like the image wasn't correct or something.
- Decided not to flash a firmware at all and run LibreELEC (and CoreELEC) straight from an SD card. Downloaded the specific version for s905w, tried a lot of different devices trees (dtb files) but the box didn't even boot.
Before powering the box I was pressing the reset button for the recovery on the AV port. The only thing I haven't tried is short pinning but correct me if I'm wrong I think this is done only when your PC doesn't recognize the box, so I don't know if it will be any useful at all. Also I don't have a UART-USB converter, so I cannot connect to serial for terminal. Is there a way to recover from this? I'm in desperate need of help! Thanks for your time.
Hi all,
I'm in a complete head spin so I'm hoping someone here could shed some light on an issue I'm facing.
As the title says, I currently have a Buzz TV XPL 3000 android box. I'm trying to flash "Aidan's Android TV Custom Rom" onto it. But no matter what I try to do, I simply cannot get the Buzz TV box to interact with my Windows 10 PC.
I have 2 different male-to-male USB cables that I've tried plugging into the box and into my PC, but there is no link between them. The PC nor the Android box don't acknowledge any kind of connection. I know a lot of people will probably say that my cables aren't data cables, but I've actually used one of them previously to flash another Android device.
Whenever I plug the USB cables into my Android box and PC, the ONLY thing that happens, is the PC powers up the Android box. I've tried turning on USB debugging tools from the developer menu, but nothing. The PC doesn't even make a sound when I plug the cable in and there is nothing listed under device manager. Nothing appears on USB Burning Tools under devices.. Just nothing.
I've tried plugging in the USB cable, while holding down the reset button (located on the bottom of the box), but all that does is power on the Android box and load into "Android Recover". Still nothing detected on USB Burning Tools and still no acknowledgement from the PC that a USB device has been connected.
The options I get in the Android Recovery menu are:
Reboot System Now
Apply Update From EXT
Apply Update From Data
Wipe Data/Factory Reset
Wipe Cache Partition
Burn Keys
I've tried selecting "Apply Update From EXT" and manually selecting the .img file. But it says it cannot verify the signature.
I'm literally out of ideas. Can anyone who knows what they're doing please help me!
TheOneIsBack said:
Hi all,
I'm in a complete head spin so I'm hoping someone here could shed some light on an issue I'm facing.
As the title says, I currently have a Buzz TV XPL 3000 android box. I'm trying to flash "Aidan's Android TV Custom Rom" onto it. But no matter what I try to do, I simply cannot get the Buzz TV box to interact with my Windows 10 PC.
I have 2 different male-to-male USB cables that I've tried plugging into the box and into my PC, but there is no link between them. The PC nor the Android box don't acknowledge any kind of connection. I know a lot of people will probably say that my cables aren't data cables, but I've actually used one of them previously to flash another Android device.
Whenever I plug the USB cables into my Android box and PC, the ONLY thing that happens, is the PC powers up the Android box. I've tried turning on USB debugging tools from the developer menu, but nothing. The PC doesn't even make a sound when I plug the cable in and there is nothing listed under device manager. Nothing appears on USB Burning Tools under devices.. Just nothing.
I've tried plugging in the USB cable, while holding down the reset button (located on the bottom of the box), but all that does is power on the Android box and load into "Android Recover". Still nothing detected on USB Burning Tools and still no acknowledgement from the PC that a USB device has been connected.
The options I get in the Android Recovery menu are:
Reboot System Now
Apply Update From EXT
Apply Update From Data
Wipe Data/Factory Reset
Wipe Cache Partition
Burn Keys
I've tried selecting "Apply Update From EXT" and manually selecting the .img file. But it says it cannot verify the signature.
I'm literally out of ideas. Can anyone who knows what they're doing please help me!
Click to expand...
Click to collapse
Hi, You Might Have To Try And Figure Out Mask rom Mode To Force your Device To Be Detected By USB Burn Tool If Using The Reset Button is Unsuccessful, Look For Mask rom Mode Information, You Can Upload Pictures Of Both Sides Of Your Logic Board we can try and figure it out
aidanmacgregor said:
Hi, You Might Have To Try And Figure Out Mask rom Mode To Force your Device To Be Detected By USB Burn Tool If Using The Reset Button is Unsuccessful, Look For Mask rom Mode Information, You Can Upload Pictures Of Both Sides Of Your Logic Board we can try and figure it out
Click to expand...
Click to collapse
Hey man,
Thanks for taking the time to reply.
I managed to get it working. Decided to give it another shot this morning and for some reason, first time around it worked. USB Burning Tool instantly picked the box up, installed perfectly and now I have it up and running!! It definitely seems a lot more snappier than my last firmware.
I do have a question though. With the previous stock firmware, my TV would pick the Android box up with a HDR signal. It no longer does this now. Is that to be expected with this rom or is there something I need to do?
Sir
TheOneIsBack said:
Hi all,
I'm in a complete head spin so I'm hoping someone here could shed some light on an issue I'm facing.
As the title says, I currently have a Buzz TV XPL 3000 android box. I'm trying to flash "Aidan's Android TV Custom Rom" onto it. But no matter what I try to do, I simply cannot get the Buzz TV box to interact with my Windows 10 PC.
I have 2 different male-to-male USB cables that I've tried plugging into the box and into my PC, but there is no link between them. The PC nor the Android box don't acknowledge any kind of connection. I know a lot of people will probably say that my cables aren't data cables, but I've actually used one of them previously to flash another Android device.
Whenever I plug the USB cables into my Android box and PC, the ONLY thing that happens, is the PC powers up the Android box. I've tried turning on USB debugging tools from the developer menu, but nothing. The PC doesn't even make a sound when I plug the cable in and there is nothing listed under device manager. Nothing appears on USB Burning Tools under devices.. Just nothing.
I've tried plugging in the USB cable, while holding down the reset button (located on the bottom of the box), but all that does is power on the Android box and load into "Android Recover". Still nothing detected on USB Burning Tools and still no acknowledgement from the PC that a USB device has been connected.
The options I get in the Android Recovery menu are:
Reboot System Now
Apply Update From EXT
Apply Update From Data
Wipe Data/Factory Reset
Wipe Cache Partition
Burn Keys
I've tried selecting "Apply Update From EXT" and manually selecting the .img file. But it says it cannot verify the signature.
I'm literally out of ideas. Can anyone who knows what they're doing please help me!
Click to expand...
Click to collapse
i just bought this buzz tv box. can you guide me ? Like how to root? Which is the best rom? Best apps ? Adaway etc?