Minix U9-H won't start

Yes i know he tried to acess recovery menu but he can try again.
Also he can try again with usb burning tool.

For example i was a time ago with a state of brick on one of my routers, i never gave up, i tried many times, learning and searching for more information.
Day after day i tried until i had sucess, i left the device rest for a time to think about it lol :), and me with a fresher mind :)

Using a JTAG procedure was last resort but it was not needed.

Have you had a U9-H "stuck" at the MINIX splash screen lol ;)???
 
Have you had a U9-H "stuck" at the MINIX splash screen lol ;)???
That problem i never had but i had others (minix included)
The worst and more difficult i had was on that particular router, I had a lot of headaches (that router has a custom firmware dd-wrt, but it's worth it to me, i have others routers with the same dd-wrt :))

He can try previous solutions suggested and see if can have sucess.
 
That problem i never had but i had others (minix included)
The worst and more difficult i had was on that particular router, I had a lot of headaches (that router has a custom firmware dd-wrt, but it's worth it to me, i have others routers with the same dd-wrt :))

He can try previous solutions suggested and see if can have sucess.

I only ask as when we say it's "stuck" at the initial MINIX splash screen followed by the completely blank display, & everything else listed also then subsequently fails as well, we truly do mean it's "stuck" in every possible sense of the word ;). Stuck, unresponsive, frozen, jammed or locked up lol ;) :).

I've repeatedly tried entering the recovery menu when these lock ups happen, (well in excess of 60-70 attempts over the span of it happening 13 or 14 times to the one device). Trust me when I tell you, stuck absolutely means stuck lol ;). The device simply will not respond to, or do anything until re-flashed, at which point the device immediately springs back to life & for most they'll luckily never see the same issue ever again :). Swapping my devices around was the only resolution & the weird thing is, 2 IDENTICAL U9-H's that have spent considerable time in the same output on the AVR haven't experienced it once!! Discovering a cause would be the singular most helpful thing we could do for this particular issue but it's entirely random too. Thankfully, outside of me having one device that just did it repeatedly, it's relatively rare as this thread can attest to :).
 
2 IDENTICAL U9-H's that have spent considerable time in the same output on the AVR.

"output"?? They work a whole lot better connected to the "inputs" lol ;). (I was obviously miles away there.)

Ok, fortunately that never happened to me

Honestly, I hope it never does happen to you mate ;)!! The general inconvenience of it aside, obviously an immediate wipe is required without the opportunity to grab anything you might have forgotten to move etc. lol. (Not that I tend to use my U9-H for much more than a media player but that isn't always the case for others.)

We might never see you again for 4 months as you spend every possible waking hour trying to fix it without re-flashing it too PMSL ;) :). A minimum of 72 attempts per day to enter the recovery menu over & over, never giving up ;). LOLOL.

The end result of course would be inevitable & we'd probably later learn that you'd gone completely mad, taken it out back & shot it after it had defeated you hehe. GAME OVER ;)!!!
 
@ArcticWolf i'm not confusing anything.He tried USB burning tool but my suggestion to him that he try again. There are few versions of USB burning tool.Some of them will work and if he can he can try on another pc with USB 2.0 port on the other pc.
 
I have found the 6 second hold down power button never enough, I slowly count to 16 and up it pops, so worth a try to boot into the recovery menu again. There is also a red light visible in the rear of the box seen near the ethernet port that would indicate if the power supply is working. Good luck.
 
I have found the 6 second hold down power button never enough, I slowly count to 16 and up it pops, so worth a try to boot into the recovery menu again. There is also a red light visible in the rear of the box seen near the ethernet port that would indicate if the power supply is working. Good luck.
16 seconds?
I don't think so.

If i count 16 seconds the device is already booting for a time.

I tested at least two times and the instructions are correct:

https://theminixforum.com/index.php?threads/neo-u9-h-factory-reset.225/
 
I have found the 6 second hold down power button never enough, I slowly count to 16 and up it pops, so worth a try to boot into the recovery menu again. There is also a red light visible in the rear of the box seen near the ethernet port that would indicate if the power supply is working. Good luck.
16 seconds?
I don't think so.

If i count 16 seconds the device is already booting for a time.

I tested at least two times and the instructions are correct:

https://theminixforum.com/index.php?threads/neo-u9-h-factory-reset.225/
I usually keep pressed for 8 secs. :)

No harm though keeping pressed until the Recovery Menu appears! ;)
 
  • Like
Reactions: gdf
I usually keep pressed for 8 secs. :)

No harm though keeping pressed until the Recovery Menu appears! ;)
I am afraid of damaging recovery button by pressing for too long or in this case for U9-H power button.

So i prefer pressing for the exact time or even less ☺
 
I am afraid of damaging recovery button by pressing for too long or in this case for U9-H power button.

So i prefer pressing for the exact time or even less ☺
And what about the 30-30-30 Hard Reset Rule for Routers?! :unsure:
 
And what about the 30-30-30 Hard Reset Rule for Routers?! :unsure:
?. Yep. I upgraded one firmware (dd-wrt) on one of my routers (tp link wr 1043nd) , to a newer dd-wrt version and the device was in a state of brick.
Now i am with a stable dd-wrt version and i will stay with that.

That procedure of 30-30-30 did not work, however i installed a recovery firmware and later again dd-wrt ?.
After a few days and a lot of headhaches there i got ?.
Router is alive ☺
 
He can't unfortunately. His device won't advance past the initial splash screen!!





I think you're confusing @dig 's own actual post with @notrui mate lol ;). (It was dig himself that listed number 6 as something he tried & he specifically mentions trying the USB Burning Tool ;).)

Ergo, he did already try the USB Burning Tool.

@dig ,

I'd say you've posted in the correct place for your specific issue so don't worry about that :).

What will the device do right now? (Blue LED lit on the front & you still get the splash screen or absolutely nothing at all?) If you still have the MINIX splash screen & a blue LED it would tend to indicate all is not necessarily lost just yet :)!! Additionally, if you no longer have the blue LED have you retested the PSU's voltage since that happened?

1. Try completely uninstalling the USB Burning Tool from your laptop. When you reinstall the tool ensure that the accompanying USB drivers are installed with it.
2. If you have an older version of the USB Burning tool, try updating it to the latest version. (Do a fresh uninstall/reinstall.)
3. If you already have the latest version of the USB Burning Tool, try uninstalling it & downgrading to an older version. (I.e. try v 2.0.6.2.) In some circumstances the latest version isn't necessarily always the best one to have. (An older version worked flawlessly for me for a long time but the more recent version has of itself caused a few problems for me recently as well.)
4. As has been pointed out, this could be an issue with specific USB ports on your laptop, anti viral software, firewalls, anti malware, the list goes on. Do you possibly have another PC or laptop you can try or kindly ask a friend/family to install the burning tool purely to allow you to flash your image? They can immediately uninstall it again afterwards if successful.

I've had this exact scenario happen with 2 of the 3 U9-H's I have access to with the devices inexplicably becoming stuck at the initial MINIX splash screen. (One has only done this once with no problems at all ever since the firmware was re-flashed. The other did it repeatedly specifically when connected to an AVR with no other apparent cause, reason or trigger. (It was swapped around to be used as a beta test device with "other than stock firmware" & a direct to TV connection, that's also been fine since the swap around too. I really have no clue what triggers it despite seeing it well over a dozen times with that single device, all within a very short time period as well!!)

The only way I could resolve the problem each time I experienced it was a completely fresh flash of the firmware. (I tried pretty much everything you've listed each time before resorting to flashing too.) Obviously, you need to get that USB Burning Tool issue fixed first so that you can proceed as normal. It's a vital link in the chain & as long as that's potentially got problems it won't matter what you do with anything else until that's first rectified. Additionally, whilst it's not a given/absolute, some users have reported that the re-flashing process would only work with the original MINIX OTG cable, or a micro USB cable with the slightly longer 6mm connectors. Conversely, other users have also reported everyday/run of the mill micro USB "data" cables (4mm connectors) working absolutely fine as well. (It's anyone's guess what exactly causes this but with the massive array of laptops floating around out there, or pre-built/custom built desktop PC's, it does seem to be highly subjective to any given hardware. Add in the endless number of individual apps/software options individual users install on their laptops/PC's & the variables involved add up to truly staggering numbers rapidly heading for the infinite lol ;).)

In your instance, there's a minimal chance it's a mix of both problems if you've tried the USB Burning Tool over & over with multiple USB cables as well. (However, the USB Burning Tool is more likely to be what's holding you back. Are all of the micro USB cables you tried definitely data cables & not just charging cables as well, or are they even all of the same batch/brand/source etc.?). Ideally, the original OTG would be your best option if you have it? Failing that, can you borrow another quality data cable to try as well?

Let us know where you currently stand, there may still be a small glimmer of hope :).

When i do the 6 seconds+ button hold, the splash screen stays on longer than the ordinary bootup sequence, but eventuall (say 15 sec) goes to blank screen as before.
The blue "on" light works normally
The red glow from the spdif connector still present
I will try a second computer with the burning tool, it will be a laptop with XP so i hope that is compatable.
When i test USB cables connected to the PC, I get the windows audible "connect" signal with a cable that works, no signal with certain other usb cables i've tried.
Thanks to everyone who has replied to my problem, i will report back when, or if, i get the burning tool to work, it seems as this is the only solution to restoring functionality to the U9
 
Tried the usb burning tool on XP, had trouble displaying the burning tool panel, so abanded that option.
Went back to w7 deskop and tried again, only this time i removed the SD card before connection, now the burning tool "sees" the minix, so i rewrote the firmware and all works, except i lost my Kodi addons. I should have tried to boot up minix without SD card, normally, to tv, it may have worked.
I do not understand why the SD card played a part as i have not accessed the card for a long time, IE nothing changed for months of use.
Thanks to everyone who replied with ideas.
 
Before USB burning tool you must disconnect everything you connected external hard drive,usb flash drive and micro sd card.
 
Tried the usb burning tool on XP, had trouble displaying the burning tool panel, so abanded that option.
Went back to w7 deskop and tried again, only this time i removed the SD card before connection, now the burning tool "sees" the minix, so i rewrote the firmware and all works, except i lost my Kodi addons. I should have tried to boot up minix without SD card, normally, to tv, it may have worked.
I do not understand why the SD card played a part as i have not accessed the card for a long time, IE nothing changed for months of use.
Thanks to everyone who replied with ideas.

Well done :).

The main thing is you're all sorted now :).

I've flashed & re-flashed countless times with SD cards still being present in the slot & never had one cause any issues. It's certainly possible something on the card had become corrupted affecting both a normal boot, & the flash procedure.

Format the SD card in question as well less it causes you problems again in the future. Better to be safe than sorry ;).

RE Kodi add-ons. Obviously a flash is essentially a total system wipe & reinstallation. Use Kodi's backup add-on. Once you've got Kodi back how you like it, take a backup image & you can restore it to its current state again should you need it. Otherwise, just make another backup in the future if you make any major changes to Kodi.

Enjoy :).
 
  • Like
Reactions: gdf
Tried the usb burning tool on XP, had trouble displaying the burning tool panel, so abanded that option.
Went back to w7 deskop and tried again, only this time i removed the SD card before connection, now the burning tool "sees" the minix, so i rewrote the firmware and all works, except i lost my Kodi addons. I should have tried to boot up minix without SD card, normally, to tv, it may have worked.
I do not understand why the SD card played a part as i have not accessed the card for a long time, IE nothing changed for months of use.
Thanks to everyone who replied with ideas.
Well done :).

The main thing is you're all sorted now :).

I've flashed & re-flashed countless times with SD cards still being present in the slot & never had one cause any issues. It's certainly possible something on the card had become corrupted affecting both a normal boot, & the flash procedure.

Format the SD card in question as well less it causes you problems again in the future. Better to be safe than sorry ;).

RE Kodi add-ons. Obviously a flash is essentially a total system wipe & reinstallation. Use Kodi's backup add-on. Once you've got Kodi back how you like it, take a backup image & you can restore it to its current state again should you need it. Otherwise, just make another backup in the future if you make any major changes to Kodi.

Enjoy :).
I thought i had fixed this problem, the SD card was removed and still the unit failed (again), i have had to reburn firmware a couple of times since my last post, I am now using FW007A in an atempt to isolate the firmware version as a possible culprit.
I turn the unit off, operating OK, next turn on displays the splash screen momentarily then a blank screen, no fault patern that i can determine.
I am losing patience with my u9, it is very close to being relegated to the ribbish bin and replaced with a differnt brand
 
I thought i had fixed this problem, the SD card was removed and still the unit failed (again), i have had to reburn firmware a couple of times since my last post, I am now using FW007A in an atempt to isolate the firmware version as a possible culprit.
I turn the unit off, operating OK, next turn on displays the splash screen momentarily then a blank screen, no fault patern that i can determine.
I am losing patience with my u9, it is very close to being relegated to the ribbish bin and replaced with a differnt brand

Is your U9-H connected through an AVR?

I've only seen this behaviour of re-flashing the image & the device would work normally for a while, then get stuck at the splash screen over and over again with one U9-H. It only happened when that particular U9-H was connected to an AVR.

I could never determine a cause, it was 100% random. That U9-H is now used for beta testing/testing the CE ROM & it hasn't done it since. Entirely up to you if you'd like to give the CE ROM a trial!!
 
u9 connected directly to TV first, audio is then fed from the TV to an AVR via the TV TOSLINK connection.
I am currently still using the FW007A firmware expecting a failure, but hoping for success. If the current firmware fails I would like to give the CE firmware a go, I have nothing to loose.
Although i am testing the firmware I am unsure if my fault is a firmware or hardware fault. Thanks for the help
 
Back
Top