[Unofficial] - 6.0.1 Marshmallow ROM for the U1

If I check the USB connections it does recognize the Minix because it is listed in the "Devices & Printers" tab of windows.
If I check the USB Tool it does not appear.

Edit: Tried with a different cable and switching off and on several times and it suddenly popped up.
 
Last edited:
Just installed today as I was having issues with stock firmware.
Couple of things to note:
- SuperSU fails to update, but if you install/update the latest apk manually, it works fine.
- The power button "app " is not there? A pity, that's what I was using all the time to power off the box.

Otherwise, thanks for the firmware, I already found 1 game that refused to install under Lollipop and works fine with Marshmallow.
 
MooseJaw said:
WARNING!

These modifications are not officially supported by Minix. If something bad happens to your box while installing this ROM, you are the sole person responsible.

aae741ca2b.jpg


With that being said, I have tested this ROM for a couple of months without any issue. It's also very easy to revert back to a stock Minix firmware with the USB Burning Tool. ​


DOWNLOADS:
U1 Custom 6.0.1 Marshmallow ROM (CFW002):
https://mega.nz/#!1Oo0mRgD!DjMXeQj8yz4M_moB8EOTSLZW2wpcjMvsrHWPbRhaghk
(Install with the USB Burning Tool)

TWRP (optional):
https://mega.nz/#!VPIQgDxZ!Wxl72C3EVPicQaVls3hHOmU9LtmF4-hK2UZ42wwmzBk

Patched Netflix (optional):
https://mega.nz/#!9WYU0JBb!JH6aZS2m3Ns5p2APC4QypzpurLhaQktJyojOVOLbEdw
(don't know if it works anymore after the Netflix crackdown)

Minix MOUSE pointer (optional):
https://mega.nz/#!FS4CxAbD!ivPfC2IKpVleChzS36LetPFVk-9GBv_-8SyYqIuT_28
(TWRP flashable zip)

----

INSTALLATION:
Use winrar or 7zip to extract the .img file from the .rar. Install the ROM with the USB Burning Tool (included in the ROM download). Please see the attached PDF below for install instructions.

----

CHANGELOG:
Code: 
 CFW002:
- Fixed Bluetooth discovery
- Optimized performance
- Fixed a TV Settings bug

CFW001:
- Initial release


----

BUGS:
- 3.5mm port doesn't work.
- Remote can only wake the box from a sleep state, not a powered off state.
- Power led color scheme is screwed up

* Otherwise, the ROM is stable *

----

TIPS:
Root:
Navigate to Settings/Minix Settings and select root. Follow the prompts. Once done, reboot the U1 and let SuperSU update via the Play Store.

Unroot:
Navigate to Settings/Minix settings and select unroot. Follow the prompts. Once done, reboot the U1.

----

WARNING:
If rooted, please unroot before doing a factory reset or you will run the risk of encountering a bootloop. In the case of a bootloop, simply reflash my ROM with the burning tool.

----

OLD VERSIONS:
CFW001:
https://mega.nz/#!FbAR2TwJ!v8UK7obXzQwe5zojoZNtRNHSl71kr4loL8fSfap8hFE

ENJOY!​
Click to expand...
It works fine. IR Touch Overlay is also working fine. Moreover, Orientation controle is also built-in.
Overall it is great! Thumbs up!
 
Yup, works well for me too, with root and both A2 Lite and Rii8 controllers. Thanks MooseJaw!

Something I forgot to mention: my U1 was rooted on OFW, and I accidentally rooted it twice with SuperSU via TWRP, so I wasn't able to revert root from SuperSU. But after flashing CFW Marshmallow with USB burning tool, it booted just fine. Just mentioning that as the tutorial says that if your U1 is rooted, it will be stuck in a boot loop, which wasn't the case for me.
 
Azam said:
@MooseJaw Can you please guide how to change boot animation or logo in NEO U1.
Click to expand...

It should be the same as any other Android device:
https://safetricks.com/change-boot-animation-android/

Even if you mess it up, you should be able to do it/fix it from the TWRP file explorer. TWRP is provided by MooseJaw in the 1st post, just copy it on a SD card and boot from it. Of course, if you activated root, you shouldn't need TWRP at all.

@MooseJaw: speaking of which, I notice that your TWRP posted in the 1st post is different from the "official" one:
https://twrp.me/minix/minixneou1.html

Yours has a smaller file size. Are you recommending to use yours, or is the "official" more up to date?

Thanks!
 
MooseJaw said:
@Azam - If you want to create a rom with a different boot animation/logo, use the amlogic customization tool. Otherwise, follow the advice above.

@Pingouin - It's been a while since testing it, but I believe the "official" version will not work. It was built for the wrong version of Android. You could try booting to it from your sd card. No harm in trying.
Click to expand...

@MooseJaw & @Pingouin
Thanks! I have changed the animation with my customized images but an image is still present in startup. a picture is attached.
Do I need to customize the ROM to change this image?
 
This weekend I finally decided to bite the bullet and install this ROM in my U1. I am happy to report that everything went smoothly and I have it working without a problem. A couple of comments:

- I initially thought that upon installing the ROM I would lose all the installed software, so I made a list of what I had installed, saved configuration files where necessary... only to find out after installing the ROM that everything was still there, nothing was lost. Good!

- In response to some of the comments in this thread about the "need" to upgrade to Android 6. In my particular case, the need to upgrade stems from two specific applications requiring at least this version of Android: Skype and Cisco Webex meetings. Older versions of these apps (I of course tried to go back to those) will not let the user join calls and meetings, requiring a mandatory upgrade. I realized that Skype did not work any longer a few months ago (it did work a year ago), but I do not use it that much, many people have switched to Zoom. The final straw, however, was Webex: it is the app used in my daughter's school for all the videoconferences, and with the pandemic situation there are A LOT of videconferences lately, teachers use this tool profusely, so if I wanted her to be able to join these online meetings using the TV box (plus a webcam, of course) I needed to upgrade to Android 6.

- I realize that some hardware elements do not work, as documented in the first post. I myself do not use the 3.5 mm jack, and the only functionality that I really miss is powering the box on with the remote: now I need to use the physical button on the side of the box to power it on. This only happens when the box is off but the front LED is on (red color), btw. When the front LED is off (like for example if you have previously unplugged the box) the remote power-on works, I imagine because the ROM is not loaded yet. Once you load it, that functionality is lost. Oh well, it is a small price to pay for a working Android 6.

Just to finish... Kudos to the OP for creating this ROM and making it available to us. I for one do appreciate it enormously. Thanks!!!!
 
I've tried a few times to do this now but I keep getting errors in the USB Burning Tool. I've followed all the instructions in the first post but maybe I've missed something silly?

Can anyone help with what I've done wrong please?

I've tried ticking and unticking all options and still get errors, just different ones.

1612375208918.png
 
Could you try with a different version of the USB burning tool?
I've had occurences when one version didn't work, but another did.
 
I have CFW001 and Ive noticed that I cant use anything with blutooth lol. Must I download CFW002 to fix this? No other way?
 
MooseJaw said:
Yeah. There was a bluetooth discovery issue with CFW001. CFW002 fixed it. I don't know the specific details of your issue, but bluetooth was optimized with the newest version.
Click to expand...

Well it doesnt discover my wireless keyboard and I have issues with connecting my ps3 controller. I'm rooted and I downloaded sixaxis controller app and it finds MAC when I press pair controller and when I press start it connects but the lights on my controller keep flashing. it seems the final step isnt working in actually connecting the controller to neo u1. Even using it wired with otg usb cable doesnt help. Ive seen youtube videos of people just plugging in their otg usb cable on their phones and minix tv boxes and it gets instant recognized and they can use the controller as input right away.

In the minix keyboardsettings it does have sixaxis controller and I enable it but still nothing. is that because of the bluetooth issues you mentioned? Also Im not 100% sure which version I have maybe 001 or 002. Is there a way to find out? I remember downloading your firmware 2 years ago. It could be that I already have 002.

Also ever since I upgraded to your firmware Ive been having annoying issues with Kodi. Kodi crashes alot not right away, it could be after 1h or 3 hours watching movies on Kodi it suddenly crashes to desktop or minix main menu with all the big tiles. Ive been always running the latest kodi version, always updating whenever there is a newer version. Is Kodi too much for neo u1? Maybe too low RAM for Kodi? 2GB in total is not much and there's only 900MB usuable RAM left and of that Kodi is only using around 300MB. So no wonder Kodi is very slow, almost like lagging and crashes alot. I didnt have those problems on android 5.1.1 the original firmware of neo u1.
 
Last edited:
MooseJaw said:
To see the firmware version you're on, go to settings / system / about.

For apps crashing back to the launcher, have you tried clearing the app's cache and system cache?
Click to expand...

Ouch I already have CFW002 lol. So what you make of my bluetooth problems? Is it known with this version? Why cant I use bluetooth on any device? The device detects my ps3 controller for example otherwise sixaxis controller wouldnt show up in keyboard settings. But I can't really connect with the controller. And shouldn't connecting with OTG USB cable work anyways? It's a direct wired connection, so it doesnt make any sense. is CFW002 missing some crucial system files or something? Can you tell me if neo u1 supports ps3 controller or not? I'm thinking out loud here, I'm wondering is it maybe because of the custom rom you created and somehow messed some bluetooth settings up and maybe thats why bluetooth doesnt work, because I remember when I had android 5.1.1 on the latest official firmware my ps3 controller worked wired with OTG USB cable and also my wireless keyboard worked. So can you please recall what settings did you delete or change on your custom rom. Maybe you can fix it. Because I dont wanna downgrade to 5.1.1 because majority of apps dont even run on that, you need atleast android 6 for apps.

Yes ofcourse I do that daily clearing all cache. Also since yesterday Minix Metro has been crashing constantly, this never happened before.
 
Last edited:
You must log in or register to reply here.
Back
Top