Posts: 25
Joined: Apr 2013
Reputation:
0
Hi, & yes you've guessed right again another day another brick, this time it's a nano slim+ M3 box I thought I was sure that I was putting in the right firmware (Droidtv M3 20130520), However, after inserting the sd card holding the reset & plugging it in the big green man appeared staring at me from the screen menacingly almost threatening & then he was gone & I have not seen him since, the screen went black for a few seconds & then I got the onscreen message telling me to to check the cable etc. as nothing connected to hdmi. I would like to say I'm sorry & i am for having to keep coming here for help but I enjoy playing about with them so I'm not sorry for that every body needs something to occupy them. Thanks again for any help offered.
Josh.
Posts: 306
Joined: Jul 2013
Reputation:
4
Oh rotten luck mate, sorry to hear that. Hmm sounds just possible that you may have a dodgy HDMI lead (yes I have had two of them over the past couple of years) or the HDMI connection to your TV is not fully pushed home. Could be the graphics chip in the box has blown but again that would be rare as never come across this happening. Just double check out all your connections and even try it with a different TV or using a different HDMI socket on the TV too. Those M3 boxes did put out I think 480 line low res output in recovery mode and I have had some TVs that are not able to display that res properly if at all, so try with another TV that is definitely capable of displaying 480 line input (most modern TVs do but not all) . Just some other ideas worth a try Joshua
Otherwise it is most likely bricked of course and you will need to carry out one of the many unbricking procedures discussed in these forums many times. Probably the shorting of the two pins procedure may be the way for you, again all well documented in this forum with photos too.
Posts: 25
Joined: Apr 2013
Reputation:
0
Hi Raymw, thanks for the reply, I've been going through the posts on here & can find the pin shorting method but most of the files are for the M6 or MX have I got to use a specific file on the bootable sd card or just an old rom.
cheers. josh
Posts: 18
Joined: Jan 2014
Reputation:
0
Finally I went and upgraded my ATV520e from Geniatech Linux running Frodo. For whatever reason I chose first to go for MX Linux Helix 14.2. My choice was affected probably most that I didn't want to go through reverting to Android, as some recommended with EmbER.
I did straight upgrade. Easy and fast. Everything seemed to work well, alhtough I had red leds on all the time. I liked especially being able to shutdown and power on the box with remote. Some problems with some of the mythtv recordings, but really minor things.
Then I read about others experiences in EmbER. I downloaded 1.01 release, which is latest as of now. I didn't want to go through Android this time either, so I did straight upgrade. No problems this time either. Remote does not power off the box, but it powers it on. Any chance get that to work with remote.conf?
I like EmbER, and I think I will stick with that. I use my box mostly for livetv with mythtv pvr addon and watching recordings. I have same issue with same recording as I noticed with MX Linux running Helix 14.2. Couple of crashes too, but I'm impressed.
I'm escpecially interested in OTA upgrade as an option, since tell you the truth, everytime I have to flash the box, I'm afraid I will brick it.
Posts: 834
Joined: Jan 2012
Reputation:
24
2015-06-25, 06:13
(This post was last modified: 2015-06-25, 06:15 by ed_davidson.)
If you have the kr60 remote the 4 button is on I think. But never mind you can't power off.
Posts: 5
Joined: Jan 2014
Reputation:
0
2015-06-30, 07:38
(This post was last modified: 2015-06-30, 07:41 by widdly.)
I have installed both the Helix 14.1 and 14.2 builds from the first page on my Mygica ATV1200 and they boot up but end up with a black screen. I've tried this with both the HDMI and component outputs.
After power on, I see the MX-Linux penguin screen and then the Kodi Loading scree. After that it goes to a black screen. The box can be rebooted by pressing ctrl-alt-delete using a usb keyboard. Anyone got any ideas why this might be happening? Any tips for debugging?
The Geniatech Frodo and the XDA Gotham builds both work fine for me.
Posts: 306
Joined: Jul 2013
Reputation:
4
Is that Ember Helix 14.2 or the MX Linux Helix 14.2 version from Auxbox ?? Have no problems with Auxbox's compile Helix 14.2 at all, but have had some issues with Ember which I think and hope they are working on currently . So what box are you using ? I use primarily MyGica ATV1200 and 1220 boxes which are G02Ref based boxes.
You could try reverting to Android first using one of the first;page links and make sure that it boots okay and then try flashing to Helix 14.2 from there. Obviously make sure your HDMI lead is fully pushed home but if not then you would not see the initial boot up KODI screen of course.
Posts: 5
Joined: Jan 2014
Reputation:
0
It is with the MX Linux Helix. Same issue with both the MX linux 14.1 and 14.2. I've not tried Ember. I'm using a MyGica ATV1200.
I haven't tried reverting to Android first. I'll give that a try.
Posts: 5
Joined: Jan 2014
Reputation:
0
Haven't had a chance yet Ray. I will post my results once I do.