Hi,
I recently got some boxes from hong kong and i normally install gbox 1.16 and then cronic corey;s new mtd mx linux. However these boxes are not flashing normally. Well that's a lie they do flash normally but the outcome is not what i normally get.
The boxes are listed as meson m6 g18ref and in xbmc g02ref but look identical to all the other boxes i have had. I have opened one up and i see the board is rev 1.1 which i understand is an old board. The kernel 3.5.0 and the firmware is jdq39.20140605
I cannot connect via ssh to check mtd. When flashed the red led stay on when on and blue led when off. The boxes don't shut down or restart via the red button on the remote neither. But otherwise are ok.?
Has anyone come across this problem before? And any idea's how i could resolve this i seen someone had a similar issue and overcame this by flashing a droid tv firmware first but this would not flash at all.
Any help massively appreciated as I am fairly new to this.
desmondo123 said:
Hi,
I recently got some boxes from hong kong and i normally install gbox 1.16 and then cronic corey;s new mtd mx linux. However these boxes are not flashing normally. Well that's a lie they do flash normally but the outcome is not what i normally get.
The boxes are listed as meson m6 g18ref and in xbmc g02ref but look identical to all the other boxes i have had. I have opened one up and i see the board is rev 1.1 which i understand is an old board. The kernel 3.5.0 and the firmware is jdq39.20140605
I cannot connect via ssh to check mtd. When flashed the red led stay on when on and blue led when off. The boxes don't shut down or restart via the red button on the remote neither. But otherwise are ok.?
Has anyone come across this problem before? And any idea's how i could resolve this i seen someone had a similar issue and overcame this by flashing a droid tv firmware first but this would not flash at all.
Any help massively appreciated as I am fairly new to this.
Click to expand...
Click to collapse
I have managed to get a remote.conf from a working android box of the same build is it possible to insert this in the linux images, sorry i am fairly new to this and this is well above my expertise.
Have you had any luck?, I am trying to see if it's possible to install Linux on the mx2 with oscam.
Hi,
Just bought this tv-box and while trying to update it with a different rom bricked it. It shows just red LED and nothing happens, also while trying go into recovery (toothpick + power cable).
Does anybody have detailed tutorial how to unbrick the box ?
Thanx in advance.
I am in your very same situation. Tried the sd card burning method and also the usb one, but no success at all. Hope there is some solution.
resadent said:
I am in your very same situation. Tried the sd card burning method and also the usb one, but no success at all. Hope there is some solution.
Click to expand...
Click to collapse
Maybe someone could place a foto with indicated pins (to make circuit on flash chip) to go into recovery mode ?
etemmu666 said:
Hi,
Just bought this tv-box and while trying to update it with a different rom bricked it. It shows just red LED and nothing happens, also while trying go into recovery (toothpick + power cable).
Does anybody have detailed tutorial how to unbrick the box ?
Thanx in advance.
Click to expand...
Click to collapse
Head over to FreakTab, they have tutorials on how to unbrick it
Patrck744 said:
Head over to FreakTab, they have tutorials on how to unbrick it
Click to expand...
Click to collapse
We, or at least I, have tried all the tutorials on freaktab and read a lot of things on the matter but nothing seems to do the trick. It's really frustrating.
rubbish
resadent said:
We, or at least I, have tried all the tutorials on freaktab and read a lot of things on the matter but nothing seems to do the trick. It's really frustrating.
Click to expand...
Click to collapse
There might be a hardware change for those boxes, the Nexus ROM TV Stock thread has pics on what changed. Best to watch that thread since a solution might be posted soon
I am in the same situation. I tried the sd card burning method and also by the usb cable, but no success at all.
I have got m8s pro+ 2/16gb s905x, The device was purchased on the gearbest website.
some news from my yesterday fight:
sd card burning - many variants of rom, after restart, but on the mainboard there was not observed the reset button, only place named "k1" -> I soldered two points from "k1 place" to make a reset
after that
try by male-male usb cable and usb burning tool 2.0.8, Error result: [0x10105002]Romcode/Initialize DDR/Read initialize status/USB Control setup error
I tried 4 different firmware's, and the same happens every time. Can anyone suggest something?
I can copy whole error if it can help determine the problem.
found on the internet
Romcode / Initialize DDR / Read initialize status / USB Control setup error
-> An error occurs when memory chips do not match. Firmware with ubut for some, but sew on others. It remains to ask the seller about the original firmware: (or shovel (look) available.
resadent said:
We, or at least I, have tried all the tutorials on freaktab and read a lot of things on the matter but nothing seems to do the trick. It's really frustrating.
Click to expand...
Click to collapse
I'm in the same situation!
gearbest give me a link for downloading yhe firmware but that don't work for me :
mega.nz/#F!gqgXwSCa!sFNDXrV_EMzAYAcJ68dV0w
If that can help someone.
Regards,
Cody57 said:
I'm in the same situation!
gearbest give me a link for downloading yhe firmware but that don't work for me :
mega.nz/#F!gqgXwSCa!sFNDXrV_EMzAYAcJ68dV0w
If that can help someone.
Regards,
Click to expand...
Click to collapse
I gave up after 3 days of wasting time with tools and this box... Ordered xiaomi mi box this time.
etemmu666 said:
I gave up after 3 days of wasting time with tools and this box... Ordered xiaomi mi box this time.
Click to expand...
Click to collapse
I will do the same....
i brick mine.....
Any help?
Where can i find *.img file and instruction to brink back in life?
Please help
I can help. My xiaomi mi box has just arrived, after a couple of hours of testing i can say, put that **** (m8s) to trash, buy xiaomi. I am happy that m8s was hard bricked now.
leonkoum said:
i brick mine.....
Any help?
Where can i find *.img file and instruction to brink back in life?
Please help
Click to expand...
Click to collapse
I trie so many roms... without success....:crying:
Cody57 said:
I trie so many roms... without success....:crying:
Click to expand...
Click to collapse
it's not the deal with ROM but with bootloader and recovery. Because it's not working rest of the problems are what box buy now ? Xiaomi or if are rich, nvidia. Screw that chinese scum. Try MI BOX and you'll find that xiomi is the real proffesional android tv (it's quick, responsive and my wife can handle it so it's the best user freiendly commercial )
etemmu666 said:
it's not the deal with ROM but with bootloader and recovery. Because it's not working rest of the problems are what box buy now ? Xiaomi or if are rich, nvidia. Screw that chinese scum. Try MI BOX and you'll find that xiomi is the real proffesional android tv (it's quick, responsive and my wife can handle it so it's the best user freiendly commercial )
Click to expand...
Click to collapse
I have a nvidia shield and I order a xiaomi mi box....
it was just to test a new box and it wasn't too bad.... before testing a new firmware
HELLO the solution for reinstall your rom
hello i have found the solution for you i have received my mecool m8SPRO+ today and i search button recovery
i have found this on freaktab :
You need to press the hidden reset switch (accessed via pinhole on bottom of case) when you connect the USB cable, and it's got to connect to the USB OTG jack, which is the one closer to the power jack.
or see on this video youtube on front panel : xxxxs://XXXX.youtube.com/watch?v=WpThZ2sgkhUt
or maybe same at this video an other place : xxxs://youtu.be/N27pAxtcDSg?t=268
if is not clic take a pinhole if is ok you arrived after bootloader MECOOL ON menu
and take a factory reset
if you don t boot
try method with microsdcard take on sdcard the firmware ota here only the file M8SPRO ota
xxxxs://mega.nz/#F!gqgXwSCa!sFNDXrV_EMzAYAcJ68dV0w
and renom on update.zip
then take power off if is ok you screen apperead with logo android green updating
or do method with usb burning tools
replace xx on web link the correct http
Unbrick the M8S Pro+ 2/16
Hi everyone,
I know how you're guys feel... Is there any new idea or suggestions to unbrick the devices?
After OTA Update the box only shows red and blue at the same time, no boot, no detection of windows with reset button or / with holding the circuit shortcut at "K1".
Can't believe that Amlogic is even worse than the Rockchip boxes to unbrick...
How to factory reset mecool m8s pro plus ? S905w android tv os
Guys i am in trouble with new mecool m8s pro plus ATV i bought..
I am new to xda ..
On the setup
Ipaired my remote
And then connected to my wifi
I then chose the option to put my email and password for the account..it signed in but in the end it was asking for location access i gave it but then i receive an error saying google sign in has stopped
And now i am stuck ..even whei restart box always stuck at the same loop
Guys i dont know what to do...i havent even seen its home screen ..i am in the loop of setting up device
I think maybe faftory resetting it may solve it...but i dont know how to do it ..as i dont know how to open recovery mode...
Hey there!
I somehow managed to red light brick my x96 mini s905 1gb/8gb, p282 board!
Now the reset button does nothing. I can't boot from any Burn Cards I've made.
Using USB Burn Tool, yields an error at 4% (for every ROM I try including stock rom)
I now have to short the pins to get my pc to even recognize the box and when it does, it fails at 4% in usb burn tools. No matter what settings I use (erase bootloader, erase flash ect)
I've been told these amlogic devices are next to impossible to actually KILL! So is there anyone around XDA that can guide me here?
I'm not new to flashing ROMs (been doing it since my samsung s3 lol) and I have flashed plenty of android boxes without error until this one!
I have a feeling I somehow deleted the bootloader! WHAT DO I DO NOW?!?!
Thanks in advance. Hopefully I've given enough information.
no solution ever for this brick?
found a possible solution
Hi, I just openend a thread where I was able to unbrick my x96mini box
https://forum.xda-developers.com/an...lved-bricked-x96mini-red-led-display-t3992403
I think the problem with this is the power cable is not being conncted after USB detection.
The board doesn't have enough power through USB alone to properly work, so connecting the power jack is mandatory. I failed the first flashing attempt for this reason.
Hope this helps, even when it has been months since OP.
Hi folks, I'm hoping someone can help me unbrick my MXQ Pro 4k. I've searched high and low for the stock firmware but it is nowhere to be found. My box seems to be a peculiar variant and the specs are as follow:
S905x 1GB/8GB S905XQ_V2.0 2017.05.16
SV6051P Wifi
SK Hynix H27UCG812ETR DDR3
It became bricked when I tried to flash different atvXperience firmware img files with the Amlogic USB burn tool. I had successfully flashed it with a version posted by minixfreak on the freaktab forums.
Although not with exactly the same specs, it worked pretty well except for the remote control wouldn't function. So I tried to flash again with what I thought was the stock firmware but unfortunately, that bricked the box pretty good. I tried to revert to the atvXperience firmware that worked from the post, but it now always fails at 7% when trying to format with USB tool. In all cases, I've tried every possible combination of pushing in the reset button in the AV port, shorting the NAND pins, switching the order of USB ports... The box always has a red light when powered and is always recognized by the USB Burn Tool driver when connected to the OTG port on the box but always stops at 7% when it attempts to format.
I hooked up a serial usb/ttl cable to capture boot output, turned on the box and it seems the box is in an infinite loop with the following output:
LOOP:8F;EMMC:800;NAND:85;SD:800;USB:8;LOOP:90;EMMC :800;NAND:85;SD:800;USB:8. It appears the bootloader is corrupt or maybe has been erased.
I tried making a bootable sd card using both burncard maker and bootcard maker but that didn't work either as it can't get past intial boot attempt, even pressing reset or shorting nand pins. I'm not sure if it's because of the boot loop or perhaps incorrect firmware. I haven't been able to find the definitive stock firmware anywhere. I would appreciate help in finding this elusive firmware.
I've scoured the internet for a solution and tried many different things but nothing can get me out of this loop. I'm now at a dead end.
I once had a bricked router that I was able to fix by connecting usb/ttl and putty and repeatedly hitting Ctrl-C after rebooting to get a CFE prompt. At that point I was able to manually flash the router with firmware and revive it. Maybe there's a tool available that would possibly do something like that with the android box?
Also possible I guess that something in the hardware is toast and it's just a paper weight now. Anyway, any help and suggestions would be appreciated.
So, i hope someone can help me with my project, or else i can kiss my plans goodbye...
A while ago i bought a Google Nest Hub (1st gen) to run my own software/dashboard. At first i tried to 'Cast' it as webpage to the device, but that is not fully stable. Especially now that they updated the Hub to run Fuchsia OS.
So, my plan is to OR alter the Google firmware to run my own stuff on top of Fuchsia. Maybe create my own Flutter app or something. OR build linux from source, which is available for the S905D2 u200, which is the CPU of the Nest Hub. The latter gives me more control but i would have to get all hardware running in linux.
Both options give me some problems though:
The hub has a USB port under the foot. If you press both volume buttons while booting, you get the Amlogic Worldcup device where you can talk to it with the Amlogic burn tool. You can flash firmware here or even dump firmware from it. Problem is: Google password protected this so you first have to upload a password.bin file before you can use the tool. Something that i presume is not possible to bruteforce...
When you push one of the volume buttons while booting, you boot to Fastboot mode. Hey, that's familliar. So i tried some commands. fastboot unlock, does not work. flashing an own rom, not allowed. Flashing my own recovery image is allowed and completes succesfully. But, while trying to boot to recovery it sais: "Hash of data does not match digest in descriptor.". So it verifies the image which it cannot do.
The other volume button boots to the recovery image, which is a google's own thing where you can reset the device to factory defaults if you want..
The pcb viewed from the backside of the device.Notice the two wires next to the pink heat gum stuff. That's my RX and TX(?). Two pins next to each other seemed like a logical attempt.
So i teared the device down, got to the PCB and found a RX/TX port. At least, i noticed that i got uart data when connecting to it. But, i can only read, it does not respond to keyboard presses. I don't know if the other pin is just no TX pin or that there is no software that will respond to keypresses.
My question, what else can i try, or did Google just lock it's hard-/software very well? Of course i could chip-off the NAND chip, but then reflowing it on the device after altering the NAND is almost impossible, especially if you have to do it a lot of times... What else can i do?
keerttttt said:
So, i hope someone can help me with my project, or else i can kiss my plans goodbye...
...
Click to expand...
Click to collapse
You ever get anywhere with this? Just curious, thanks.