My Box: Eny OTT M8 K200
PCB: M8 V8_1 201501418
The purpose for this post is as follows: (so read/ignore as appropriate)
1. Proper method to identify Box specs
2. Why it didn't go into recovery mode
3. Give kudos to this forum for Unbrick'ing my box
4. Proper method to be prepared for brick condition in future
5. Feedback on OpenElec and other boxes
1. Per Method to Identify Box Specs
What is the proper method to identify exactly what I have? It appears to have different assembled parts.
- Box case is Eny OTT M8
- Settings in ADB GUI says: K200, Android 4.4.2, ubuntu@google-server#1 3.10.33, build KOT49H20150623 test-keys
- Board has M8 V8_1 201501418
- When it boots, CPU says M9 and other details
- LED portion of board (which obv doesn't matter) has different stamp
- Check CPU or memory chip on board?
- If I have M8S, what is M8S vs M8s+?
2. Why No Recovery Mode?
After I unbrick'd my box with m8s_ap6330_8g2g_150818_USB升级.rar (Details at bottom of this post),
- I made a SDcard with some firmware of my choice
- Plugged in HDMI, and nice to haves (wireless keyboard, Ethernet), and started the box with toothpick method.
This did not go into recovery mode rather just booted into ADB GUI. Why? It doesn't really matter because the box booted up and if I want to apply an update now I can just go into the ADB GUI Update&Backup program, but it would be good to understand.
3. Give Kudos to this Forum
Kudos to JustMe, perpetual, Ploggy, hipisxbit, etc. I mostly used these to get to the solution: (details of unbrick at bottom of this post):
4. Proper Recovery Preparedness
What are the detailed steps of the proper method to proactively prepare for recovering your system due to flashing bad ROM or other? I guess this would be some ongoing method of grabbing last known firmware, etc. and making backup. Going back to an OEM firmware like I did should be the last resort.
5. OpenElec, Firmware, Other Boxes
I would have already had OpenElec installed if the recovery step mentioned in #2 above had worked but now I am questioning my approach. In my house we mainly only use Kodi (and some Hulu which can be ignored here). I have had a Nexus Player 5, Nvidia Shield, WDTV. From what I have read, it appears OpenElec will be a better Kodi experience in terms of buffering, etc.
This is an example of a pretty scientific approach for choosing a box aka focusing on performance:
- Any favorites out there?
- On best boxes?
- Going to OpenElec?
- Going to WeTek since OpenElec is native?
- Going to CuBoxTV
- Best Amlogic boxes?
- Or best boxes that support OpenElec?
Which OpenElec builds?
From http://amlinux.ru
JustMe's: http://justmeroms.com/
For Firmware updates, is this the main source? It seems difficult to match up these coddled together boxes from all sorts of 3rd parties to the proper Firmware? So why take the risk unless you are having an issue that the firmware fixes?
My Unbrick Details:
I brick'd my box installing OpenElec from the OpenElec Amglogic builds (because for the board 'M8 V8_1 201501418' I learned from this forum it is the wrong ROM).
There was no indication that power was reaching the board at all.
After many iterations and failed Firmware imgs and error messages in USB Burning tool, these were the steps:
- At windows boot menu press F8 and Disabled Signature Verification for Drivers
- USB burning tool and World Cup drivers need libusb-win32-bin-1.2.1.0 but 1.2.6 is already part of Windows 7 so can ignore unless on Windows 8+
- Downloaded and install USB Burning tool, version setup_v2.0.4.3.
- The libusb-win32 World Cup drivers are needed which is part of the USB Burning tool install however I downloaded Windows 7 - World Cup Drivers.zip here:
- This is just for FYI but at the USB Burning tool install step it will launch setup for World Cup drivers, I initially canceled out of that setup.
- Holding the reset button (the toothpick method), aka press and hold the audio/video insert, connected USBA to USBA from the Box to the Win7 PC.
- The Box was immediately recognized by Windows (let go of audio/video reset button) and Windows tried to install drivers automatically and failed (which is fine).
- WithOut World Cup drivers it shows up as 'M8-Chip' device in Windows Device Manager Once the device shows up as 'M8-CHIP' in Windows Device manager, right mouse click 'Update Driver Software', choose to specify the location yourself and point to the folder where you extracted World Cup Drivers
- Unplug USBA to USBA
- Reboot PC
- With World Cup drivers it shows up as 'World Cup' device in Windows Device Manager
- Downloaded m8s_ap6330_8g2g_150818_USB.rar, started USB Burning tool with that img imported, and then the toothpick method and USBA-to-USBA
- Firmware update still failed in USB tool ([0x10302001]Romcode/Switch status/Check connect/Enum device...)
- I applied Power Adapter and then Firmware update succeeds
I didn't short any pins, which seems to mostly be for using a different boot sequence such as booting off SDcard, setting up and booting off OTG. This is only for when you can't use USB Burning tool.
ming
PCB: M8 V8_1 201501418
The purpose for this post is as follows: (so read/ignore as appropriate)
1. Proper method to identify Box specs
2. Why it didn't go into recovery mode
3. Give kudos to this forum for Unbrick'ing my box
4. Proper method to be prepared for brick condition in future
5. Feedback on OpenElec and other boxes
1. Per Method to Identify Box Specs
What is the proper method to identify exactly what I have? It appears to have different assembled parts.
- Box case is Eny OTT M8
- Settings in ADB GUI says: K200, Android 4.4.2, ubuntu@google-server#1 3.10.33, build KOT49H20150623 test-keys
- Board has M8 V8_1 201501418
- When it boots, CPU says M9 and other details
- LED portion of board (which obv doesn't matter) has different stamp
- Check CPU or memory chip on board?
- If I have M8S, what is M8S vs M8s+?
2. Why No Recovery Mode?
After I unbrick'd my box with m8s_ap6330_8g2g_150818_USB升级.rar (Details at bottom of this post),
- I made a SDcard with some firmware of my choice
- Plugged in HDMI, and nice to haves (wireless keyboard, Ethernet), and started the box with toothpick method.
This did not go into recovery mode rather just booted into ADB GUI. Why? It doesn't really matter because the box booted up and if I want to apply an update now I can just go into the ADB GUI Update&Backup program, but it would be good to understand.
3. Give Kudos to this Forum
Kudos to JustMe, perpetual, Ploggy, hipisxbit, etc. I mostly used these to get to the solution: (details of unbrick at bottom of this post):
4. Proper Recovery Preparedness
What are the detailed steps of the proper method to proactively prepare for recovering your system due to flashing bad ROM or other? I guess this would be some ongoing method of grabbing last known firmware, etc. and making backup. Going back to an OEM firmware like I did should be the last resort.
5. OpenElec, Firmware, Other Boxes
I would have already had OpenElec installed if the recovery step mentioned in #2 above had worked but now I am questioning my approach. In my house we mainly only use Kodi (and some Hulu which can be ignored here). I have had a Nexus Player 5, Nvidia Shield, WDTV. From what I have read, it appears OpenElec will be a better Kodi experience in terms of buffering, etc.
This is an example of a pretty scientific approach for choosing a box aka focusing on performance:
- Any favorites out there?
- On best boxes?
- Going to OpenElec?
- Going to WeTek since OpenElec is native?
- Going to CuBoxTV
- Best Amlogic boxes?
- Or best boxes that support OpenElec?
Which OpenElec builds?
From http://amlinux.ru
JustMe's: http://justmeroms.com/
For Firmware updates, is this the main source? It seems difficult to match up these coddled together boxes from all sorts of 3rd parties to the proper Firmware? So why take the risk unless you are having an issue that the firmware fixes?
My Unbrick Details:
I brick'd my box installing OpenElec from the OpenElec Amglogic builds (because for the board 'M8 V8_1 201501418' I learned from this forum it is the wrong ROM).
There was no indication that power was reaching the board at all.
After many iterations and failed Firmware imgs and error messages in USB Burning tool, these were the steps:
- At windows boot menu press F8 and Disabled Signature Verification for Drivers
- USB burning tool and World Cup drivers need libusb-win32-bin-1.2.1.0 but 1.2.6 is already part of Windows 7 so can ignore unless on Windows 8+
- Downloaded and install USB Burning tool, version setup_v2.0.4.3.
- The libusb-win32 World Cup drivers are needed which is part of the USB Burning tool install however I downloaded Windows 7 - World Cup Drivers.zip here:
- This is just for FYI but at the USB Burning tool install step it will launch setup for World Cup drivers, I initially canceled out of that setup.
- Holding the reset button (the toothpick method), aka press and hold the audio/video insert, connected USBA to USBA from the Box to the Win7 PC.
- The Box was immediately recognized by Windows (let go of audio/video reset button) and Windows tried to install drivers automatically and failed (which is fine).
- WithOut World Cup drivers it shows up as 'M8-Chip' device in Windows Device Manager Once the device shows up as 'M8-CHIP' in Windows Device manager, right mouse click 'Update Driver Software', choose to specify the location yourself and point to the folder where you extracted World Cup Drivers
- Unplug USBA to USBA
- Reboot PC
- With World Cup drivers it shows up as 'World Cup' device in Windows Device Manager
- Downloaded m8s_ap6330_8g2g_150818_USB.rar, started USB Burning tool with that img imported, and then the toothpick method and USBA-to-USBA
- Firmware update still failed in USB tool ([0x10302001]Romcode/Switch status/Check connect/Enum device...)
- I applied Power Adapter and then Firmware update succeeds
I didn't short any pins, which seems to mostly be for using a different boot sequence such as booting off SDcard, setting up and booting off OTG. This is only for when you can't use USB Burning tool.
ming
Comment