OTT TV BOX, GooBang Doo M8S-II, M8S-II, AMlogic s905_v3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
External:
OTT TV BOX Action 4K AS-14 64bit
4x CPU Cortex A53 5X GPU Mali-450
2GB RAM
16GB ROM
Internal:
S905_V03 2016.04.15
M8_IO V3_0_20150110
AP6330
I have two of these... wonderful /s devices. both ended up in a bad way. One was OTA update that nuked it and the other was me playing with it. :crying:
Years go by and every so often I see if they can be salvaged, but to no avail. Recovery is working, holding the reset button does nothing; just a blaack screen and then the tv turns off due to no signal. Finally a break through, the USB Burning Tool provided by Amlogic. After a ton of trial and error and the destruction of two many usb cables; i was able to find the combo to restore the both systems.
WARNING
This is not an upgrade guide. This is a use at your own risk, get this thing working, hail mary kinda thing. I cant help or guarantee anything, just after countless hours of seeing unanswered forum posts and scattered info, i had to do something. Again, AT YOUR OWN RISK!
Reqs:
USB MALE A to MALE A
Havit 2-Feet USB 2.0 Type A Male to Type A Male Cable, Black (1pack)
https://www.amazon.com/gp/product/B00UF8SEA0/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1
(attempted making my own, but neither functioned properly)
Amlogic USB Burning Tool v2.1.6.8
update_minim8s_rv104L03.img
http://www.mediafire.com/file/clodv5h2c8c5y9c/oct_M8S-II_RecoveryPack.7z/file
(both are 7zipped in this location)
extract the .img file and burning tool to the desktop.
Install the burning tool, the driver should also install.
import .img into tool, leave all settings default.
connect usb, in my case i had to connect the power cord as well.
press start
install takes about 8 minutes. after it finishes let it sit for another 3-5 minutes, (why not!)
click stop, disconnect usb and then power if needed.
connect to hdmi and plug back in - should be about 10 to be back in the os
REMOTE MAY OR MAY NOT WORK! one did one didnt, idk, im not a doctor.
Hopefully this helps someone else with a bricked device.
I tried a ton of other images floating around out there, but none did the trick. this got me back into the os and operational.
FOLLOW UP
Was able to get Batocera 5.10 running.
burn image to sd card or usb.
Copy dtb.img into boot folder
profit.
LINK
Related
So, I've bought a Xiaomi Mi Pad 3 with a Chinese Rom, and I was following a tutorial to flash a new rom into it.
I basically did the following:
Installed MediaTek Drivers on PC
Opened "Smart Phone Flash Tool"
Specified Download-Agent as DA_SWSEC.bin and Scatter-loading File as the ROM
Unchecked preloader and clicked on "Download"
Connected the Xiaomi Mi Pad 3 to the computer while pressing Volume Down
Then, at this point, the computer crashed with a blue screen of death with the error "BUGCODE_USB_DRIVER". Here is the diagnosis of the error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that, the Mi Pad won't turn on, won't respond to any button and is not recognized by the computer.... I think I might have hard-bricked it.
I've found a tutorial about recovering a Mi Pad 1, but one of the steps is to make a bridge in the SD Card slot, which Mi Pad 3 don't seem to have.
I'm a developer myself, I know my way on things, I have a VM Linux, I'm willing to open the tablet and do whathever it costs to recover it.
Please, what can I do??
Please, anyone?
I FUC*ING RECOVERED MY FUC*ING TABLET. FUC* YEAH!!!!!!!!!!!!!!
I don't know exactly what it was, but I kinda did the following:
- Installed the latest SP Flash tool from spflashtool.com on my PC
- Installed Mi PC Suite for drivers and such
- To help debug, I had a freeware called "Free Device Monitoring Studio", to better understand what's going on on my USB ports
- I was playing a little with the connection/desconnection of the device on my computer, trying to understand how it was. I saw that Kali Linux running under Oracle VM kinda recognized it as a Mediatek device, but couldn't do anything else than that. With that info, my hopes went a little higher, because it wasn't completely dead after all.
- I opened Flash tool, configured it to used the same ROM and files I was using when I bricked it, because I'm pretty sure they weren't the cause of the brick and clicked "Download"
- Then I began messing with the tablet trying to make it be recognized by SP Flash Tool, upon turning it on and off and switching USB ports and connecting them directly to the motherboard USB ports instead of the frontal USB ports
- Then at one point it suddenly recognized and started downloading and flashing the new ROM. I faced some errors but with Format all + Download and having to disconnect/reconnect the batery to make it recognizable again and some little tweaks here and there, it ended up working.
My tablet is working fine now
I bricked my Macigsee C400 Plus box flashing this image:
https://forum.xda-developers.com/showthread.php?t=3840103
Now it doesn't output image and I can't get it to be detected in USB Burning Tool.
Can someone please help me out. Is there another way of burning it or something that I can do to try and fix it?
Thx in advance.
Hi there is a way which i have make you must open inside. Open usb burning tool add orginal .img file. Press start in program. Than on main board near nand disk (SEC JHY) there are 48 pin slots. With a screwdrive or another things short pin 40 end 41 together. (Or when you say left top pin is first. Pin 8 end 9 short) then connect c400 with back side usb port to pc when usb tool say connected then release pins. May you have to try 4 - 5 time but lastly unbrick. Good luck. ?
Here is pins.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
speed86 said:
Hi there is a way which i have make you must open inside. Open usb burning tool add orginal .img file. Press start in program. Than on main board near nand disk (SEC JHY) there are 48 pin slots. With a screwdrive or another things short pin 40 end 41 together. (Or when you say left top pin is first. Pin 8 end 9 short) then connect c400 with back side usb port to pc when usb tool say connected then release pins. May you have to try 4 - 5 time but lastly unbrick. Good luck.
Here is pins.
View attachment 4621183
Click to expand...
Click to collapse
Thanks mate, you saved it!
After shorting the pins I connected it to USB and it was detected, I then started flashing it but it outputted a connection error. After that I did it again, but this time I only broke the short when the usb tool was already on flashing the system part system (about ~20% in), the process continued to 98% and then it froze, at this part I tried it again but without shorting the pins (with the toothpick trick) and this time (probably because boot and recovery partition where already flashed) it was immediately detected by usb burnig tool and started flashing all the way to 100%.
So once again thank you very much, you da real mvp.
I know whats the lost a device. I have been 3-4 day try all things before find this method. Your welcome. Have a nice day. ??
I have a "H96 Pro H3 S905X" Dongle and I think I bricked it... Please help!!!
(This is a repost of a thread I created here. I think I posted in the wrong section.)
Hi guys,
As the title says...
I have the following H96 Pro H3 S905X dongle
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've been trying to find information about my issue now for hours and I've tried various different methods and I just cant seem to get my issue resolved. So let me give you some background information and then I'll tell you what I've tried.
Basically the device came rooted with an app called "SuperUser" (I think???) and I wanted to install Supersu. So I tried to install the APK and when I opened the app, it wanted to do something with the binaries, which I let it do. I got a message saying "If nothing has happened within 5 minutes, then I should reboot my device.". So I let it sit for about 2 minutes and the installation (or whatever it was doing), failed.. It told me to "Reboot my device and try again". So I rebooted the dongle, I got the normal H96 Pro screen and then after about 10 seconds I got the "MBOX: Make yourself colorful" splash screen. Now usually this takes about 5-10 seconds and my dongle boots into the Android OS. But not anymore... It just sits on that splash screen and does absolutely nothing.
So I've come to the conclusion that I've probably bricked my device...
I've found a LOT of guides online regarding my device but most of them are for the box version of my device and the one video I did find for a H96 dongle was for a different version, it wasn't the S905X.
The first guide I found was to download the .img file for my dongle (which I did) and use an app called "USB Burning Tool". But I quickly realised that to do this, you need a USB Male-to-Male cable, which I don't have. So I couldn't progress with this any further.
Luckily, I found another guide which used an app called "Burn Card Maker", which I could load the .img file onto a micro SD card and boot from it on the dongle. This is the path I decided to take...
So I downloaded:
Code:
s905x016.H96_PRO_Dongle_2G(16)_HS2734A_7.1.2018.01.27.16.15.img
I used the app to write it to the SD card (2gb) and when it was finished, I ended up with 3 files:
Code:
[LIST]
[*]s905x016.H96_PRO_Dongle_2G(16)_HS2734A_7.1.2018.01.27.16.15.img
[*]aml_sdc_burn.UBOOT
[*]aml_sdc_burn.ini
[/LIST]
I popped the micro SD card into my dongle and this is where I'm stuck... I cannot get the dongle to boot the SD card.
I've tried just putting the SD card in, powering the dongle on and waiting,
I've tried popping off the dongle case and holding down the tiny reset button with my nail,
I've tried holding down the tiny reset button before powering the device,
I've tried powering the device and then holding down the tiny reset button,
I've tried rapidly pressing the tiny reset button,
I've tried pressing the tiny reset button 3x and then holding it...
Everything I try just leads to the same outcome... H96 Pro screen for 10 seconds, MBOX spash screen...
Please someone help me!! I'd appreciate it so much, Its doing my head in.. I've learnt my lesson.. Never to mess with root
Hello XDA community! I need help putting this Tomate S905XQ box in bootloader mode so I can flash it using USB Burning tool.
I tried everything without luck.
What I have done so far:
Plugged the USB cable in the PC, hold the visible RESET then UPDATE buttons but unfortunelly, no dice. (Do I have to plug the ac adapter)
Also tried holding the "hidden inside" UPDATE button but also without any luck.
I want to flash Aidan's Custom ROM v9 on this box (1GB/8GB).
Any help is really appreciated, including how to backup this firmware because I haven't found any version on internet.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try shorting it , the pins are on the chip just above where it says 905x , have the box attached via usb and have the usb burn tool open , get somehing like sim tray tool and one by one place it in between the pins untill it shorts it will connect ...you may or may not need power plugged in and make sure you use the otg usb slot..
Good luck
Thank you very much for your reply! I'll try that on the weekend.
as mentioned above shorting the pins AKA Mask ROM Mode will be your awnser, look at this thread, look for same type of chip as you have (M logo) even if chip aint the same number mask rom mode will probobly (but not always) be the same, there are 2 chips similar to yours in the thread, so try with those 2 first
NAND Chip Mask ROM Mode Short Location - FreakTab
Hi Everyone We have created this thread to collect all the NAND pin Short to Mask ROM Mode locations for all our members. Because firmware comes on android
forum.freaktab.com
Guys, few days agoI flashed my X96max S905X3 with v7. 1 Aidan V9 .img for H96 Max X3 with USB burning tool V2.2.0, and after flashing was done, removed USB cable, stooped the USB tool, and then I tried to power it up, but it won't start at all. It's completely dead.
Any advice please?
please use Slimbox rom ur box will be live again you might have to open the box and short two pins but here is the link
https://slimboxtv.ru/glavnaya/x96max-plus/ on right select English.
saleen_gt said:
please use Slimbox rom ur box will be live again you might have to open the box and short two pins but here is the link
https://slimboxtv.ru/glavnaya/x96max-plus/ on right select English.
Click to expand...
Click to collapse
Thx.
However, in meantime I've sent box for warranty claim, hope they will not detect that flash went wrong :/
If, not, I will try that method. Will update what happened.
bro you can not brick these boxes i have 4 amlogic chip boxes always play around with different roms and if end up bricked just open box and short two pins together and volla.
saleen_gt said:
bro you can not brick these boxes i have 4 amlogic chip boxes always play around with different roms and if end up bricked just open box and short two pins together and volla.
Click to expand...
Click to collapse
Got the new box from store
Hope this one will not brick again
Bad luck.
This time flashed with Slimhouse v11.4 but he same happened.
Perfect time for using the screwdriver
Succesfully unbricked via NAND mask mode.
Had to connect this pin to USB ground. Straight forward job.
This time I flashed my box with Slimbox ATV V11.6
It booted correctly this time.
Everything works
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jucca said:
Succesfully unbricked via NAND mask mode.
Had to connect this pin to USB ground. Straight forward job.
This time I flashed my box with Slimbox ATV V11.6
It booted correctly this time.
Everything works
View attachment 5369295
Click to expand...
Click to collapse
Glad it worked out for you