yashsingh1/xdaforums huggingface dataset:
[Meizu Pro 5 ROMs, Kernels, Recoveries, & Other Dev] PYCON:
Really nice and wonderful job !!! :good:

Let me ask some details :

* there're some apps to try in ubuntu ?! 'cause if I remember well, one of the big obstacle of ubuntu phone was the lack of apps / programs to install in the system...

* once done this procedure, TWRP Recovery ( your version, in this case ), will remain ?! Or it's been overwritten / disappeared ?! :crying:

* In above case, imaging that TWRP is still present, what's the procedure to go back to an Android system ( Flyme e.g. or RR or whatever ) ?

:highfive:
[Meizu Pro 5 ROMs, Kernels, Recoveries, & Other Dev] st0rm77:
Yes, but not until you flash the Ubuntu recovery manually.

Extract /partitions/recovery from the device-*.xz

Flash this to recovery via fastboot.
[Meizu Pro 5 ROMs, Kernels, Recoveries, & Other Dev] st0rm77:
Look in the Ubuntu store, lets say its somewhat limited.

TWRP remains, it does not touch recovery at all.

Backup you current state (flyme/aicp/cm/rr).

Install Ubuntu

If you do not like it, reboot into TWRP and restore from backup.

Just follow the instructions in post 1.
[Meizu Pro 5 ROMs, Kernels, Recoveries, & Other Dev] PYCON:
* Ok, nice... I'll try to look for some apps like them I'm using :)

* Nice ! It's the most important thing :silly:

* Ya, I've asked to u this 'cause for example, when I want to delete CM13 ( RR ) and return to Flyme, I cannot simply restore the nandroid of previous Flyme' based rom ;) I've to flash a Flyme rom FIRST and only then I'll be able to restore the nandroid ;)
[Meizu Pro 5 ROMs, Kernels, Recoveries, & Other Dev] st0rm77:
...... i wonder if that could be the reason why i patched the recovery ?

I think it is ;)

And you know what the beauty is of this ?

You can now do it too :laugh:

(no more reflashing of flyme, just backup/restore in twrp)
[Meizu Pro 5 ROMs, Kernels, Recoveries, & Other Dev] PYCON:
U'r a genius man, thank u very much ! :highfive:
[Meizu Pro 5 ROMs, Kernels, Recoveries, & Other Dev] Benni009:
Done. Thanks man. Nice work =) It's not simple to get from chinese-version with former owner logged in to pro5 ubuntu OTA 13 =) You made it easier.

Lets wait for OTA 14
[Meizu Pro 5 ROMs, Kernels, Recoveries, & Other Dev] st0rm77:
So you cant get root ? I have something that might work, but its early stage and you might be the perfect person to test this.

PM me
[Meizu Pro 5 ROMs, Kernels, Recoveries, & Other Dev] dugu1248:
good job
[Meizu Pro 5 ROMs, Kernels, Recoveries, & Other Dev] Benni009:
Sry for my late answer. Today I tried to upgrade to OTA 14 but the update was not downloaded nor installed. Do you have successfully updated to OTA 14?

BTW: Yes I think I get root with the flyme account

Edit: It seems the OTA-Update to OTA-14 works fine. It only takes a while :)
[Meizu Pro 5 ROMs, Kernels, Recoveries, & Other Dev] Mollic:
i was trying to mess around with this along side with multirom from faust, after some problem i actually thought it was going to work, but after installing the zip i get an error " ! failed, verify error on bootlogo " and even tho the installation conclude it doesn't boot afterward, any clue on how to fix this?
[Meizu Pro 5 ROMs, Kernels, Recoveries, & Other Dev] w4r10ck01:
Video??
[Meizu Pro 5 ROMs, Kernels, Recoveries, & Other Dev] SIeniuss:
Flashing bootlogo error. On TWRP 3.0. Tryed on OTA 12 and OTA 13
[Meizu Pro 5 ROMs, Kernels, Recoveries, & Other Dev] pippideniro:
anyone successful with this guide?
[Meizu Pro 5 ROMs, Kernels, Recoveries, & Other Dev] Jorge R:
hello, I tried it in ubuntu touch of Canonical and it works, also with the ubuntu 15.04 but it does not work with the 16.04
[Meizu Pro 5 ROMs, Kernels, Recoveries, & Other Dev] TamashiiTora:
Any thing new?

I know its been a while but I'm still using my Meizu Pro5. It was an Ubuntu edition. I've been using A custom rom for a couple of yrs now. I'm ready to go back to Ubuntu because there hasn't been any updates from the Rom creators for a couple yrs now and I want to keep the phone updated. so I followed this process but upon install phone says

" could not find 'META-INF/com/google/android/update binary' "

and after reboot wont move past white "Meizu Powered by ubuntu" screen...:confused:I did get it back to recovery. So If at all possible is there something that I can do? I'm trying to install the new Ubuntu touch on my phone but it wouldn't proceed with out an older version running on the phone...
[Meizu Pro 5 ROMs, Kernels, Recoveries, & Other Dev] stradfred:
Get OTA update with this TWRP BACKUP.

My device updated with OTA-14 ;)
[Android Head-Units] Zaphod-Beeblebrox:
**Reserved **

First!
[Android Head-Units] sinnedone:
Second! Lol :p

I'm not a developer so unfortunately I can't contribute, but hopefully those who can will.

At the very least I can beta test when its a little more complete.:D
[Android Head-Units] sun.valeo:
Android port system less complicated than the application Bonovo.app and MCU. Good luck and patience.
[Android Head-Units] apollo1976:
Black're a legend !!

Your project is great !!! see Android 6.0 on Carpad would be great.

Thanks for the great effort you make for all
[Android Head-Units] vip-25:
Woooow great !!

Good luck
[Android Head-Units] robertusIT:
nice one, i hope a very important feature:

"that can be use apps, which require android +4.4.4, like lollipop"

I say that because android auto "stand alone" coming soon, so if will be possible install this app in the radio, we have android auto pure, ( not automate that is awesome but is not the same like original ), and maybe mp3 stuttering from usb can be solved in this rom.

keep up work!
[Android Head-Units] foldedpaper:
Thanks for the sneak peak, looks promising. I'll gladly help sponsor a new device if you happen to brick yours. I love this headunit and how far the community has gotten in supporting it.
[Android Head-Units] vivacious:
I want to buy NU3001 now, is there any way to get it?
[Android Head-Units] VBlack:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
[Android Head-Units] vivacious:
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?

---------- Post added at 01:48 AM ---------- Previous post was at 01:43 AM ----------

I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
[Android Head-Units] VBlack:
I just put NU3001 to aliexpress search bar and found a lot of propositions, I think there should be available one.
[Android Head-Units] apollo1976:
Hi VBlack,

it's nice to know you're making progress on the new ROM CM13. All are rooting for you !! Your work would be wonderful !!

I have only one question:

With the ROM of XDAuto I found an annoying problem that occurs when i turn off and then relight the Carpad.

When the power back very often the Carpad car remains with black screen until i touch it with my finger.

I think the problem is somehow related to the USB ports.

Even with your ROM does this happen ?? When you turn on the car, the Carpad remains ever with black screen ??

Thank you!!
[Android Head-Units] Zaphod-Beeblebrox:
Do you have your efforts posted on github anywhere? Would you mind doing so?

There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.

If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.

Thanks,
[Android Head-Units] VBlack:
Nice to hear from you. Sure I will share. Current situation is next:

CM13 - no wifi (looks like netfilter from userspace not match netfilter from our outdated kernel), no selinux (completely disabled), and increased system partition to be able to add opengapps, twrp - works.

AOSP 7 - it is strongly rely on selinux, so i could not just disable it, and now I'm trying to merge new selinux with our old kernel...

So, i will upload CM13 in current state, and continue on aosp 7, if i fail with aosp 7 i will back to cm13. This is current plan.
[Android Head-Units] VBlack:
I update first post with sources and build information
[Android Head-Units] shatteredsilicon:
[MENTION=229050]VBlack[/MENTION], you mention "our outdated kernel". Does this imply that the kernel sources aren't available? I am very interested in this project because I am looking for a head unit with fully update firmware that can be kept up to date with security patches, and some of the Android security patches include the kernel (e.g. the recent "dirty cow" vulnerability).
[Android Head-Units] VBlack:
No, we have kernel sources, but our kernel version 3.0.36 and looks like nobody release Android kernel 3.14 or 3.18 for rk3188. 3.14 and 3.18 mostly used in Android M and N. So combining Android M or N with such outdated kernel is not a trivial task. Because of this incompatibility we currently have all networks issue on this CM13 project.
[Android Head-Units] shatteredsilicon:
Kernel 3.0.36 is 4.5 years old. The 3.0 branch is no longer maintained with security patches, and hasn't been maintained in over 3 years. There have been numerous security exploits in the Linux kernel since then, many of which are applicable to Android. Is it worth even persevering with this under such an extreme kernel constraint?
[Android Head-Units] VBlack:
You'd be surprised how many phones in the market use old kernels (3.0 is not too old for Android - it is about 2-3years off from active development).. But true is that Android kernel despite it's version less vulnerable than Desktop one, and has many fixes included (it is does not increase kernel version, like mainline kernel). Because of this it is generally hard to say which security issue will be there for sure. But on the other hand Android N and Android M has SELinux enabled, and Android N could not have it disabled. It is dramatically increase overall security of the system. But for the most of traditional Android user kernel exploits does not produce many harm - it is not a corporate server with sensitive information. And many of them used to obtain root on bootloader locked systems.

So generally for what I have in mind:

1. If succeeded just with CM13 - I have disable SELinux there - it is will be not less secure than original 4.x release - just system/google components will be upgraded, which allow us use modern UI features from Android M, and also adds more compatibility with new applications revisions.

2. If succeeded with AOSP 7.0 - SELinux will be enabled there, so we will have security addition on top of old kernel, which actually will increase security alongside allowing UI features from Android N.

So in any case it is very nice to have.
[Android Head-Units] Black6spdZ:
how difficult would it be to port the PX3/RK3188 based roms to the NU/NR series radios?
[Android Head-Units] VBlack:
If you want to bump Android version up - short answer almost impossible, if you want to have Android 6.0, but from PX3 - it could be possible, but you need to leave kernel part intact.
[Android Head-Units] krembuk:
anybody want to sell the rk3188 box from this head unit? i want to upgrade mine, mine is still the first release, rk3066
[Android Head-Units] sterod:
In the end, this is a car head unit, for me, it plays music, videos, handles calls and provides a visual interface for my bt enabled radar detector. There is nothing on it I have any concern about from a security standpoint. If we can squeeze a little more life out of it, even going just one notch up to Lollipop, its worth the effort IMO.
[Android Head-Units] shatteredsilicon:
The device does have access to the owner's Google account, which in turn almost certainly contains a LOT of sensitive information. This is my main motivation for being interested in aftermarket firmware for an Android head unit, since that can be kept up to date with Android's monthly security releases. And then there's the matter of plugging in a head unit with kernel based privilege escalation exploits into the vehicle's CAN bus.
[Android Head-Units] VBlack:
Again the main point, it is not became less secure with cm13 port than it is now, but it could became more secure.
[Android Head-Units] Stormbringer!:
Its been a month, any progress?
[Android Head-Units] VBlack:
Sorry, not too much, has been in business trip to Japan, and now spending a lot of time to CES 17 preparations. I will return to this after NY holidays.
[Android Head-Units] apollo1976:
Hi VBlack,

some good news ??? how's it work ??
[Android Head-Units] Stormbringer!:
Put a fork in it... lol
[Android Head-Units] vip-25:
any progress?
[Android Head-Units] VBlack:
I'm already spending some time with this project after CES, and now I have some issues with SELinux core, basically it is compilable but not bootable, however recovery is working.
[Android Head-Units] mobark:
Good luck

We are waiting for good news
[Android Head-Units] Zaphod-Beeblebrox:
So I pulled the sources and built the image. It built fine with no issues. I tried to flash it on a spare android box I have, but it failed with an error about not being able to mount /system. Note that this is a severely compromised box to start with, so it may be something wrong with the box.

I've broken the mini-usb connector off of it, and I think there is a bad solder joint on it somewhere, as I can press down on the case and the video gets garbled and the system locks up :) I was hoping that if I was 'gentle' with it, I could still use it as a bench-test device.

At any rate, just wondering if there were any special issues/considerations for flashing this? I don't remember what version of TWRP he have in xdAuto, but that's what I was using to try and flash the build.

Lastly, had any free time to work on it lately? :)
[Android Head-Units] VBlack:
Unfortunately, not too much free time. But I try to do my best, I driving with one unit on stock FW, and have spare on bench.

Regarding your issue - I flashing board using rkflashtool like this:

rkflashtool w system < system.img.raw

But i figured out that boot image going as builded, but system image should be converted to raw format for this tool:

simg2img system.img system.img.raw

after this -it is mounting for me.
[Android Head-Units] VBlack:
Quick update: I have good news and not so good news :)

Let's start with not so good one - looks like I give up on Android 7.0 porting.... Kernel part and Android part way to different... SELinux depends on everything and could not be cut from the 7.0 system.

Good news: I will come back to 6.0 to fix networking issue, and start porting bonovo staff...
[Android Head-Units] Danny.69:
Did you get it to work wifi and bluetooth?
[Android Head-Units] VBlack:
I definitely will
[Android Head-Units] apollo1976:
We can hope for a release shortly ??
[Android Head-Units] ElfinJNoty:
This is the same thing as asking for an ETA which is against XDA rules, and simply, poor edicate. The guy will share with us what he has, for free, at his own schedule. Don't annoy the devs with these types of questions :good:
[Android Head-Units] apollo1976:
Really unnecessary response.

To ask is permitted, to respond is courtesy

renewing all the esteem in VBlack for the great work he is doing and I do not intend to hurry.
[Android Head-Units] ElfinJNoty:
Apollo, what I said is fact. It is against the rules. Don't ask for eta's. Sorry that is not to your liking... But is NOT permitted. Please feel free to review the XDA rules before making your 51st post here in the forums.

I'm not trying to be a jerk man, it just really is frowned upon.

Let us agree together that vblack is doing great work and we thank him for it :good:
[Android Head-Units] VBlack:
I fix a lot of build/image staff and align images (sizes, locations) with current xdauto build. So it should be fine now. Jenkins build N2 should be ready soon:

https://jenkins.nc.org.ua/job/nu3001_cm13/2/

And you could do "repo sync" to obtain latest sources update.
[Android Head-Units] Stormbringer!:
Jenkins build? what is that?
[Android Head-Units] VBlack:
Jenkins is a Build server. In pair with gerrit source control it allows teamwork on projects.

Current build number 3, with fixed boot issue. Now images aligned with xdauto builds (offsets, sizes). Wifi see networks and could connect, but no ping so far - netlink issues.
[Android Head-Units] -=Jeff=-:
Impressive work. I have my NU3001 sitting on my bench at the moment, I switched to a MTCD unit last summer.. I might set up the Unit on my workbench to 'play' again. I liked my NU3001 but missed having a volume knob. but liked the radio overall. it did cutout a couple times and would reboot while driving. that was annoying though
[Android Head-Units] Stormbringer!:
VBlack,

Any news? at this rate everyone will sell off their units! lol
[Android Head-Units] VBlack:
Finally I managed to fix networking. So now I have functional CM13 on our units, and we could move further.

Now I starting to move all "Bonovo" things.
[Android Head-Units] Danny.69:
Yes sir!!!!

you're the best.
[Android Head-Units] VBlack:
Cause CyanogenMod is no more maintained - switched to it's successor Lineage OS 13.0, starting from build 8, both build 5 and 8 has working wifi and networking.
[Android Head-Units] Danny.69:
Does not understand very well with the translator.

Do you mean it works, or does it not work?
[Android Head-Units] VBlack:
Basic android working, WiFi working.
[Android Head-Units] Danny.69:
Ok, then you go ahead, right?

I'm looking forward to this new rom
[Android Head-Units] VBlack:
Yes, absolutely. The good news for community, that I personally now looking for use my rom in my car. Cause stock constantly failing with Google maps, which I'm using now...

So at least I have plans to make work: audio, navigation, Bluetooth, wheel keys, rear camera.
[Android Head-Units] Zaphod-Beeblebrox:
Is this based on the Kernel that exists in xdAuto/Stock, or do you have it running on a stock CM/Android kernel?

I think porting the Newsmy Apps will be somewhat trivial, but we do need the modules from our kernel (for MCU communication) to make it work.
[Android Head-Units] VBlack:
Well, currently I use kernel from xdAuto/Stock with minor modifications. This prevent's me from switching to Android 7.0, so with current kernel 6.0 is maximum, I think (SELinux not compatible, and starting from 7.0 we could not disable it).

I have in my mind to switch to available rockchip 3.10 kernel. Generally it is starting, but lack of drivers for eMMC, Audio, and probably something else...
[Android Head-Units] Stormbringer!:
Any progress?
[Android Head-Units] TeChNoGahd:
i would love to install and test this however my downloads always fail. Sometimes around 30 mb and sometimes around 100 mb but they always fail. from what i've read online this might have something to do with your timeout settings on your server. Not sure if that's the case or not but i can't test unless i can download.
[Android Head-Units] VBlack:
Sorry guys, I'm working now about 12H per day, so not enough spare left. I'm trying to fix annoying screen flickering issue, but no progress so far. I thinking about leave it for now (and other non-blocking, but annoying issues), and move to features.

So plan is:

- Make audio working

- Make BT working

- Take most UI modifications from XDAuto build

- Then begin bug fixing.

I double check server from different locations - no issue, however I update server, so maybe now you should not have it. If you want - I could share this image to you via google drive - PM me your google mail.
[Android Head-Units] VBlack:
I have made Android audio working, many modules ported, bonovo APKs added.

Untested build will be ready soon:

https://jenkins.nc.org.ua/job/nu3001_cm13/12/
[Android Head-Units] Danny.69:
Bravo, yes sir :fingers-crossed:
[Android Head-Units] VBlack:
Build number 15 has Bonovo radio fixed

https://jenkins.nc.org.ua/job/nu3001_cm13/15/#
[Android Head-Units] Stormbringer!:
Sweet!
[Android Head-Units] Surgent:
This is amazing VBlack! Has anyone been brave enough to flash it? Thoughts?
[Android Head-Units] peregrines:
This really sounds interesting! Thank You so much for your hard work [MENTION=229050]VBlack[/MENTION] !!!!
[Android Head-Units] VBlack:
Build number 17 dpi fixed, gps fixed.

https://jenkins.nc.org.ua/job/nu3001_cm13/17/

Current issues :

- mic not working

- bt not working

- display blinking

- volume keys not working

- bonovo settings not ported yet

Overall - more or less good
[Android Head-Units] Stormbringer!:
You know that blinking display might not be the software? we've been reporting that issue for a while. I think some say it might be the firewire cable. Mike seems to do that when its colder out.
[Android Head-Units] VBlack:
I believe it is SW - it is not blinking on xdauto release
[Android Head-Units] amritpal2489:
This brought new life to newsmy
[Android Head-Units] Stormbringer!:
this CAN bring new life to this head unit.

We'll see if/when it gets finished. yeah, I know these things take time but I've had my hopes dashed more than once with these damn Android devices.
[Android Head-Units] VBlack:
Well I have two of them - NU3001 (on table) and NR3001 (in car, every day usage), so I would not give up that easily.

Time is always a problem, real problem could be features that I didn't use in my current car, like CAN, 5.1 sound, etc...

The good point, that I am good at Android system, and my current job closely related to automotive android - so I have a good hope for this, at least at this point, when system already up and running, networking works, sound works, etc...
[Android Head-Units] sinnedone:
Go get em buddy. ;)
[Android Head-Units] Allan.Michaelsen:
Hi

I wanted to try this out and bring some debug info, but I'm having issues uploading it to my unit. I know my unit is a NU5001, but it's the same Android unit, and the software updates I've put on it so far is for NU3001. The unit is running XD-Auto 1.1.6F with TeamWin recovery. [MENTION=229050]VBlack[/MENTION] Can you advise how to upload the tar.gz?

I've tried converting the system.img to raw format and use rkflashtool to upload, but keep getting "cannot open device"
[Android Head-Units] amritpal2489:
Go on man... We have high hopes from you
[Android Head-Units] VBlack:
Hi, there is a several flash scripts included. most general is burn.sh. It is using rkflashtool. When do you get "cannot open device" error? During rkflashtool ? If so - this mean your device is not in bootloader mode. I use "adb reboot bootloader" command or push "reset" pin before power-up.
[Android Head-Units] Allan.Michaelsen:
Since I'm working of a windows computer I'm running the lines one at a time. I get the error while using rkflashtool, but the NU3001 has been put in boot loade rmode via fastboot from the system. If I open rkbatchtool it says it has found 1 unit in loader mode, so I think this is ok.

Do I need to make any configurations to the rkflashtool for it to work?

Maybe because I'm using windows 10 on a USB 3 port? But still the batch tools sees the unit as in loader mode
[Android Head-Units] Summer-Newsmy:
NU3001 already out of stock, what do you think of nu5003?

Hi Friend, this is summer from Newsmy, NU3001 already stop produce, the Carpad 2s series only have NU5003 (nissan SYLPHY) and NU5241 (KIA K5), same system with NU3001 and also come with android box. If you want for research, we would like to sell you as produce cost.
[Android Head-Units] sinnedone:
Hello Summer.

How much for NU5003 with Android box? I am interested in purchasing.

Thank you.
[Android Head-Units] Summer-Newsmy:
This quotation is for Vblack for his research work.
[Android Head-Units] Dream Reality Syndrome:
So it seems that the Newsmy units (specifically the NU generation) are the choice headunits for Android sound systems? I skimp through these boards from time to time and I am surprised and excited to see this project! Has anything come out that really surpasses this hardware?

I truly adored the idea of a separate Android box. I don't think I've come across anything else like that, even from this very brand!