If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Somehow my MX3 box just shutdown and doesn't restart anymore. I've a red led light on the power button and that's it. What I've tried:
With burning tool load original firmware from beelink, no success. It gets around 2% and aborts with error message something about usb...
Tried 3 different usb ports and 2 different otg cables, no success same issue.
Tried the toothpick pick sd card method, no success.
It seems like I can't get into recovery!
I've recovery once a bricked s89 model by shorting 2 pins, but don't know which ones on this unit.
Try yo change the poder adapter forma another with the ssme specs (5v - 2000mA). I had the same issue and fix it replacing the poder adapter.
Good luck!
Somehow my MX3 box just shutdown and doesn't restart anymore. I've a red led light on the power button and that's it. What I've tried:
With burning tool load original firmware from beelink, no success. It gets around 2% and aborts with error message something about usb...
Tried 3 different usb ports and 2 different otg cables, no success same issue.
Tried the toothpick pick sd card method, no success.
It seems like I can't get into recovery!
I've recovery once a bricked s89 model by shorting 2 pins, but don't know which ones on this unit.
Somehow my MX3 box just shutdown and doesn't restart anymore. I've a red led light on the power button and that's it. What I've tried:
With burning tool load original firmware from beelink, no success. It gets around 2% and aborts with error message something about usb...
Tried 3 different usb ports and 2 different otg cables, no success same issue.
Tried the toothpick pick sd card method, no success.
It seems like I can't get into recovery!
I've recovery once a bricked s89 model by shorting 2 pins, but don't know which ones on this unit.
I had the same issue at the very start of my unboxing it, and trying unsuccessfully flashing the incorrect version (M8/S82), of TWRP on my M82 (1G/8G) Box. which lead to a Blue Light of Death. I could power up the Device, and the Light would have gone from Red, to Blue. But, the Screen would remain Black. Though both the HDMI, and the SD AV Cable. Not knowing any better at the time I then flashed what must have been either an M8 or, S82 Firmware, which promptly bricked my MXIII into the described state above.
Why nobody want's to listen to me I have no idea. The "trick" to getting past the ~3% Crash is to make sure that the WorldCup Driver is NOT only installed on your Windows PC, as such... Windows 8.x People will have to figure out how to re-admit unsigned Drivers again, before they can actually even install 'em. This shouldn't be that difficult on a Windows 7, Vista or XP System though.
The "Trick" here is when you finally start the Amlogic USB Burning Tool, and you've switched it from Chinese, to Engrish mode, and loaded the hopefully correct *.img File into memory. With all the correct hookups (i.e. Power, OTG-USB -> PC,) connected. You need to press, AND THEN HOLD the Reset Switch (Hidden from within the AV Port!), with either some kind of Toothpick, or an old Q-Tip with the Cotton ends striped off. before your power up the Device.
Heres where most of you are getting it wrong...
The Device Powers up, and the "Device" pops up in the List of USB Device. Before the WorldCup Driver has had a chance to actually load up! Yeah I fell for that One too!! e.g. the never ending parade of ~3% CRASH!(ing).
After you power up the Device you MUST keep the Reset Switch firmly held down for ~90 Seconds till Windows ITSELF (Not, just the AUBT!), finds the "Device", and then loads the correct Driver. Only then will it work!
Assuming that you are still having problems in actually finding the correct USB Driver, you can use USBDView to remove any traces of the WorldCup Driver you see there. and, then reinstall it again the way I described above then it'll work.
One other thing... I don't think it matters much on Firmwares at, or BEFORE 110k4, but these new AiO Firmwares post 111k4 do not like to have any of the Erase Radio Buttons checked! Having any of these options checked will also lead to a crash ~ca. 3~4%. This affects 111k4, 112k4, 113k4 & 114k4 *.img ROMs.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment