How to identify my unit and update ? - MTCB Android Head Units General

Hi,
I have a VW EOS from year 2009.
I had installed a MTCB unit last year and had upgraded to Android 4.4.2 which I found here on XDA.
But now, I don't know how to identify my unit and find the correct rom to upgrade (well 5.x if available, 4.4.4 if not)
Can anyone help me ?
Thanks.

mrmrmrmr said:
Hi,
I have a VW EOS from year 2009.
I had installed a MTCB unit last year and had upgraded to Android 4.4.2 which I found here on XDA.
But now, I don't know how to identify my unit and find the correct rom to upgrade (well 5.x if available, 4.4.4 if not)
Can anyone help me ?
Thanks.
Click to expand...
Click to collapse
Read the wiki page ! (link in my signature).
Its the same as any Android device - settings/about device or machine.
You can upgrade to 4.4.4 on ANY unit and to 5.1.1 if you have a quadcore (RK3188) unit, all you need to know is your screen resolution - if you have a 2 column settings screen its 1024x600, if you have a list across the whole screen, its 800x480.
The manufacture of your device is only relevant for upgrading your MCU.

mrmrmrmr said:
Can anyone help me ?
Click to expand...
Click to collapse
All MTCB ROMs should be compatible with your MTCB unit selecting a ROM version according to the same processor and display resolution of your head unit.
Only don't update also your MCU with one intended for a different model unless you are sure that there are no compatibility issues.
In case post here the screenshots of your unit system information details.

@typos1 , @themissionimpossible
thanks to your answers.
How can I understand if my device is quadcore or not (RK3188 or not) ?
I see that to understand my resolution I will check settings screen column count.
Is that the Android settings view ?
After finding out my processor (RK3188 or not) and screen resolution, from where I should find the suitable rom ? Is there any recommended rom ?
I have read the wiki but I couldn't find how to update ROM and MCU.
Where can I find that information ?
I may want to update my MCU if that's effective on features related to Car's own display (behind steering wheel)
I understood how to define my MCU manufacturer but I couldn't find how to update MCU.

mrmrmrmr said:
@typos1 , @themissionimpossible
thanks to your answers.
How can I understand if my device is quadcore or not (RK3188 or not) ?
I see that to understand my resolution I will check settings screen column count.
Is that the Android settings view ?
After finding out my processor (RK3188 or not) and screen resolution, from where I should find the suitable rom ? Is there any recommended rom ?
I have read the wiki but I couldn't find how to update ROM and MCU.
Where can I find that information ?
I may want to update my MCU if that's effective on features related to Car's own display (behind steering wheel)
I understood how to define my MCU manufacturer but I couldn't find how to update MCU.
Click to expand...
Click to collapse
The processor type (RK3066 or RK3188) is also on the settings/about screen. To update put either the mcu.image or the update.image or both, on the GPS sd card and it should auto detect (L has a secific "updates" setting that looks for an update when pressed). If for some reason it does not auto detect you can go into recovery (using the reset button, it should beep twice before it goes into recovery) and install manually.
Updates are on the MTCB filerserver in my signature and theres also @booroondook's and @Malaysk's custom ROMs, threads for them are in the MTCB Software section, where you can also find where to download them from.
MCU updates can be found in @Malaysk's MCU thread also in the MTCB Software section.

Ok.
According to the settings information; my unit:
- is using RK3066 (seems so in build info)
- resolution 800x480 (only one column settings)
- is already using Android 4.4.4
So, I don't have any reason to update ROM. As there is no 5.x ROM for RK3066 (I read so in replies, please correct me if that's wrong)
I can only update MCU. But I have two issues there:
1. My unit uses an interesting MCU (it says MTCB-YZ-V2.21R) . Is there any YZ MCU ?
2. My unit does not have stock recovery. It has TWRP recovery because I had installed TWRP last year.
Can I update MCU from TWRP recovery ?
Thanks.

mrmrmrmr said:
Ok.
According to the settings information; my unit:
- is using RK3066 (seems so in build info)
- resolution 800x480 (only one column settings)
- is already using Android 4.4.4
So, I don't have any reason to update ROM. As there is no 5.x ROM for RK3066 (I read so in replies, please correct me if that's wrong)
I can only update MCU. But I have two issues there:
1. My unit uses an interesting MCU (it says MTCB-YZ-V2.21R) . Is there any YZ MCU ?
2. My unit does not have stock recovery. It has TWRP recovery because I had installed TWRP last year.
Can I update MCU from TWRP recovery ?
Thanks.
Click to expand...
Click to collapse
Yes, no L update for RK3066 yet.
YZ is the same as RM ie Roadmaster, there are MCUs in the MCU thread I mentioned earlier.
I cant remember how things stand with TWRP, I have read its fully working but not many people use it for some reason, but I cant remember why, yourll have to do a thread search on the original Hufei MTCB thread and see what comes up.

Thanks @typos1
But I can't find the MCUs for RM (or YZ)
You said " MCU thread I mentioned earlier"
and in your earlier post you said "MCU updates can be found in @Malaysk's MCU thread also in the MTCB Software section."
But I can't find that thread. Where is the MTCB Software section ?
And is it safe to flash MCU for RM to my YZ system ?
For TWRP, I can go through the thread but if that's not good for MCU update, what should I do ? Where can I find the recovery which is good for MCU update ?
more important, what can be the benefits of updating MCU ?
Would it help with my question here:
http://forum.xda-developers.com/and.../music-navigation-information-to-vws-t3392495

mrmrmrmr said:
Thanks @typos1
But I can't find the MCUs for RM (or YZ)
You said " MCU thread I mentioned earlier"
and in your earlier post you said "MCU updates can be found in @Malaysk's MCU thread also in the MTCB Software section."
But I can't find that thread. Where is the MTCB Software section ?
And is it safe to flash MCU for RM to my YZ system ?
For TWRP, I can go through the thread but if that's not good for MCU update, what should I do ? Where can I find the recovery which is good for MCU update ?
more important, what can be the benefits of updating MCU ?
Would it help with my question here:
http://forum.xda-developers.com/and.../music-navigation-information-to-vws-t3392495
Click to expand...
Click to collapse
The thread is in MTCB Head units/Software and development, just google it if you cant find it, but its quite easy to find - once you go into that forum its only the second thread from the top ! Cant understand how you cant find it !
I cant tell you about TWRP, I can only point you to the orignal thread and tell you to search it fro more info on TWRP.

ok. don't get angry with me
but really I found the forum. I just can't find the thread. The thread you mentioned does not have any MCU for RM or YZ
Please tell me if I am looking at the wrong thread:
http://forum.xda-developers.com/showthread.php?t=3246386

mrmrmrmr said:
ok. don't get angry with me
but really I found the forum. I just can't find the thread. The thread you mentioned does not have any MCU for RM or YZ
Please tell me if I am looking at the wrong thread:
http://forum.xda-developers.com/showthread.php?t=3246386
Click to expand...
Click to collapse
I wasnt getting angry, I jsut couldnt believe that you couldnt find it.
I have checked, there are no RM or YX MCUs, I was getting mixed up with teh wiki where it states that YZ is the same as RM. There are some MCUs (BN and HA for instance) that are interchangeable, until its confirmed that RM and YZ are, I would not try RM MCUs on your unit. As there are no YZ MCUs in that thread, take it that as yet no one has found a more up to date YZ MCUs, YZ units have only recently started to tappear so they probably have the very latest MCU anyway, over time a later version may come out.
As it stands then you have the latest available MCU and ROM for your RK3066 unit.

well, my device was installed approx. 1 year ago.
YZ was also new those days. It's 1 year now and if it is still counted as new, I am desperate about an MCU update.

mrmrmrmr said:
well, my device was installed approx. 1 year ago.
YZ was also new those days. It's 1 year now and if it is still counted as new, I am desperate about an MCU update.
Click to expand...
Click to collapse
Right, well still not many YZ versions around, there are not many Roadmaster either, which may point to it being true that they are the same. 2.22 is quite old so you may be missing a few of the latest features, but theres not much you can do other than search the web or ask the manufacturer or the seller you got it from.

Related

First custom 5.1.1 ROM released by Booroondook!

Mod edit: link removed (4pda links not allowed)
Booroondook has first done FUSE ROM and now there is he again... Bravo! Many, many improvements and fixes. Sorry he is not paying attention to XDA (doing all really for free, not for donations here) but he deserves all credits.
Full Post translation and download link
Here is the full post with download link, please donate to the dev if you like his work.
The firmware is designed as a "designer" under both options screen resolutions (800x480 and 1024x600). Everyone can afford to assemble his own version. How to assemble the firmware is described in detail here:
The order of assembly of the firmware
The firmware is available as a set designer or "do it yourself" - as anyone this thing called - and is a set of modules for self-assembly of the finished image of the firmware. The assembly is made on a computer running Windows (versions from XP and higher).
How to assemble:
1) Download the archive unpack into any empty folder on your computer (the full path to the folder does not contain spaces, non-Latin characters, punctuation marks and special characters, so not recommended for unpacking on the desktop, in the "My Documents", etc. )
2) turn in this same folder
3) Run start_rus.bat file (or start_eng.bat, if you are dearer to the English interface)
4) you will be asked to choose a processor. Only two options - RK3066 and RK3188. The selection is made by entering the numbers specified opposite processor type, and then pressing the Enter key
5) The following sentence - to select the screen resolution. Options are also two - 800x480 and 1024x600. The selection is made in the same manner as in the previous paragraph
6) After this, the firmware build process, which takes less than 10 seconds.
7) The result of the process - file update_ <vash_protsessor> _ <vashe_razreshenie> .img, which, after renaming update.img you can sew in a familiar way radio When you first start after flashing is (as usual in my firmware) conducted preset application and then fit /system/build.prop configuration file under the processor type and resolution (800x480 for the recorder will be installed screen density of 160 to 1024x600 - 240). Then reboot, after which the tape recorder will be completely ready for operation.
Features flashing process. Due to the fact that changing breakdown flash memory sections (including as compared with previously released on FUSE-firmware Android 4.4.4), the process can be performed in two stages, both stages are the same.
That is, you normally install firmware mode rekaveri (thus necessarily choosing the option with full data cleaning). The device is rebooted and ... hang on animated screensaver. If you want to wait, wait - but the result is not guaranteed. If you do not want to wait, press the RESET, then (without releasing RESET'a) - POWER. Without releasing the POWER, release the RESET, waiting 3 seconds and release POWER. All - a few seconds later we are back in rekaveri mode where once again just repeat the flashing process - again, choose the menu item, involves the installation of firmware and data cleaning, and ... forward. After the second cassette recorder firmware to be released to the operating mode (although longer than usual, as is the formation of the primary file system).
Option: instead of the second flashing, you can try to select a lower menu item - "clean and reset to factory condition."
As you understand, all your data will be lost after flashing, so advance reservations and they do not say I did not warn.
Attention!!! Those who do not have the RESET button and mechanical buttons. Before flashing be sure to ask if you can overload the radio in rekaveri mode from the "hung" or off state. If this method is not, then you better not reflash.
OTA-upgrade
The firmware is the possibility of prompt automatic updates. OTA (Over the Air - "air") or FOTA (Firmware Over the Air) - a technology that allows to (semi-) automatically obtain and install the update packages. User Intervention here minimum - it is only necessary to press the button, confirming compliance with the installation. Well, there is still a button manually check for updates. And all the rest State makes self - sends a request to the server, downloads the update package, checks it for validity (verifies the certificate used to sign the update package with a key available in the firmware), reloads the State in rekaveri mode where automatically launches the update process, and finally PG reboots to the operating mode.
Naturally, for the possibility of State OTA-update should have a working Internet connection. Automatic prompting to check for updates are sent automatically after every download SI operating mode and communication with the Internet. If desired, you can request a renewal of the "out of order" by pressing the appropriate button in the dialog "Settings" - "About your device" - "OTA update system." Another essential requirement to enable OTA updates - is the availability of free space on the "GPS-card" (/ mnt / external_sd), and (of course) the availability and serviceability of the card itself. In case of problems with the card update can be downloaded to start, but then will be a network error. Available space on the card must be two times larger than the size of the update package. As practice shows, the usual pack "weighing" of up to 20 MB. Although there are cases of 55-MB blocks. In general, if you keep on the card 120 MB of free space, the problems you should not be.
Cancellation OTA update? Unfortunately, a simple interactive option is not provided. But you can do the following: Open the file for editing /system/build.prop. Find it (towards the end of the file) option ro.product.ota.host = www.booroondook.ru: 2300. Replace the URL-address of the update server (www.booroondook.ru:2300) to something "obscene". For example, suppose that this line will look like this: ro.product.ota.host = localhost. Save the file, restart the SU. Everything - Updates you will not torture any more.
Disclaimer: The self-fulfilling complicated technical procedure for flashing the device, you will definitely take full responsibility for possible negative consequences up to the irrevocable failure of your head unit.
Version - from 06/03/2016
Link to the firmware (made on the basis of KLD-20160511): https://mega.nz/#!XFZUQKAI!H2L7gsRIuVn1D7x7slQjE_XclmVP6RWXRp-VRmc5-uU
Innovations regarding the factory options:
- Cloning a resolution of 800x480 by kernel patch (kernel.img)
- Completely redesigned Russian translation
- Root access running SuperSU
- 5 launcher to choose from ( "Settings" - "Desktop")
- 4 options "Bluetooth" application ( "Telephone"), 5 application options, "Music" and "Radio". Alternative applications are installed through the "OEM" application, return to the original (nominal) version - after the usual removal of the application settings ( "Uninstall updates")
- In settings Added "For Developers", "Screen" - "Font size" and "Display" - "Display Density"
- In settings added to the monitoring data
- OTA-update functionality
- Added missing "OEM" applications, "Weather", "DVR" (Annex "Weather" - in the version revised respected vitarkananda)
- Added widgets "Weather", "Music", "Telephone", "Video" and "Navigation", ported from the firmware for MTCD
- Partition "OEM" is increased to 384 MB. This section can be used, for example, as a "warehouse" APK-relevant distributions
- Built-in support for working with trip computer Multitronics MPC-800 (Bluetooth-name DUAL-SPP)
Attention:
1) please do not ask questions why this firmware does not work Xposed. The answer is - it does not work and on the drive firmware, and generally have Xposed big problem with Android 5 (or higher). When someone finds a way to get to work on our Xposed firmware, in principle, I immediately implement it in its firmware.
2) Management of screensaver (MTCScreenClock.apk) is only possible through /system/build.prop File Edit (parameters ro.product.screenclock = true | false and ro.product.screentimeout = 5 | 10 | 15 | 20 | 30 | 60 ). Interactive control timeout in the factory firmware is not provided, and I realize it too failed.
Note: Because an application "Weather" uses a revised version of vitarkananda, the new version of the application (as they become available) can be installed instead of the usual simple by replacing labor-intensive system file.
For developers, the public certificate signed APK following: MTCBlueTooth.apk, MTCMusic.apk, MTCRadio.apk, MTCScreenClock.apk. This means that signing their "swing" application to the same certificate (and increasing code version), you can give users the ability to easily install your development instead of forcing them to carry out the replacement of system files with setting permissions.
https://mega.nz/#!XFZUQKAI!H2L7gsRIuVn1D7x7slQjE_XclmVP6RWXRp-VRmc5-uU
[size=+1]Thread cleaned.
Keep the drama out of the public forum. If you're not a moderator you have no place telling other members how to post, no matter which side of the argument you're on, use the report feature and let us deal with it. If you have a problem with a certain member/developer do not create drama in the public forum, again, use the report feature. If it isn't a reportable offence then just leave it alone or take it elsewhere. If you believe there is a developer that is stealing someone's work and/or not giving credit, you guessed it... use the report feature. See the theme here? XDA isn't the place for your petty squabbling, if you have a valid case to argue then take the right approach and call on the moderation team. And I'll repeat, keep this drama out of the public forum. This goes for both of you.[/size]
Heisenberg said:
[size=+1]Thread cleaned.
Keep the drama out of the public forum. If you're not a moderator you have no place telling other members how to post, no matter which side of the argument you're on, use the report feature and let us deal with it. If you have a problem with a certain member/developer do not create drama in the public forum, again, use the report feature. If it isn't a reportable offence then just leave it alone or take it elsewhere. If you believe there is a developer that is stealing someone's work and/or not giving credit, you guessed it... use the report feature. See the theme here? XDA isn't the place for your petty squabbling, if you have a valid case to argue then take the right approach and call on the moderation team. And I'll repeat, keep this drama out of the public forum. This goes for both of you.[/size]
Click to expand...
Click to collapse
Your "cleaning" means no one has a clue what on earth has gone on and what all the "drama" was, as there appears to be just 2 posts left, one a quote from booroondook on xda.
It would probably be best if you removed the text from your post, or simply put "Moderator cleaned thread" or something, - currently your post confuses everyone as youve removed text and/or posts, so no one knows what you are talking about.
Since when are 4pda.ru links not allowed ? I have used them and seen them used many times over the past 2 years, or is that just referring to their use in thread titles ?
typos1 said:
Your "cleaning" means no one has a clue what on earth has gone on and what all the "drama" was, as there appears to be just 2 posts left, one a quote from booroondook on xda. If you'd like to become a moderator please feel free to make an application but until then please leave it to us. If you'd like to become a moderator feel free to make an application but until then please leave it to us. If you'd like to become a moderator feel free to make an application but until then please leave it to us.
It would probably be best if you removed the text from your post, or simply put "Moderator cleaned thread" or something, - currently your post confuses everyone as youve removed text and/or posts, so no one knows what you are talking about.
Since when are 4pda.ru links not allowed ? I have used them and seen them used many times over the past 2 years, or is that just referring to their use in thread titles ?
Click to expand...
Click to collapse
You're not meant to have a clue what's going on, that's the entire point of cleaning a thread, to remove inappropriate posts so they cannot be seen. I'm not sure why this even matters to you, you weren't involved, it isn't your business, and this thread is now back to its original purpose. Thanks for your input, but no, I won't be editing my message, it was left for a reason.
4pda links aren't allowed on XDA and haven't been for quite some time. If you are using them I suggest you stop because it could affect you negatively. We can't get to every link on this site, we act on reports made by our members, when we receive a report about disallowed links (or stumble across them) they are removed.
If you'd like to become a moderator feel free to make an application but until then please leave it to us, thanks.
Heisenberg said:
You're not meant to have a clue what's going on, that's the entire point of cleaning a thread, to remove inappropriate posts so they cannot be seen. I'm not sure why this even matters to you, you weren't involved, it isn't your business, and this thread is now back to its original purpose. Thanks for your input, but no, I won't be editing my message, it was left for a reason.
4pda links aren't allowed on XDA and haven't been for quite some time. If you are using them I suggest you stop because it could affect you negatively. We can't get to every link on this site, we act on reports made by our members, when we receive a report about disallowed links (or stumble across them) they are removed.
If you'd like to become a moderator feel free to make an application but until then please leave it to us, thanks.
Click to expand...
Click to collapse
Why 4pda links are not allowed? Where we can find list of prohibited sites?
pa.ko said:
Why 4pda links are not allowed? Where we can find list of prohibited sites?
Click to expand...
Click to collapse
The main reason is because 4pda is rife with piracy, warez, and there are major issues with GPL compliance on that site. You're also not meant to direct members to competing forums.
Thanks for explanation. True. But they also have original work like this...
pa.ko said:
Thanks for explanation. True. But they also have original work like this...
Click to expand...
Click to collapse
There is no way for you or I to know if that work is actually original. 4pda is notorious for kanging. On the surface it looks like original work but no way to prove that. This is beside the point though; 4pda is blacklisted for all of the rotten crap that takes place there, it's that crap that pulls down any original work that might be posted.
tried...not working
went to build for rk3066 pressed 1 then enter got error message..."sorry RK3066 CPU does not support in this firmware" just thought i would let others know
WECoyote633 said:
went to build for rk3066 pressed 1 then enter got error message..."sorry RK3066 CPU does not support in this firmware" just thought i would let others know
Click to expand...
Click to collapse
Your a dev and youre trying to make a RK3066 ROM ? Or youve just tried to install it on an RK3066 unit ?
typos1 said:
Your a dev and youre trying to make a RK3066 ROM ? Or youve just tried to install it on an RK3066 unit ?
Click to expand...
Click to collapse
not a developer...followed instructions in first post got error with the first step
WECoyote633 said:
not a developer...followed instructions in first post got error with the first step
Click to expand...
Click to collapse
This ROM is not compatible with 3066.
The build.bat is from a previous version.
miffymiffy said:
This ROM is not compatible with 3066.
The build.bat is from a previous version.
Click to expand...
Click to collapse
thx for info..that being the case this info might be mentioned in the first post....and the diy package perhaps shouldn't give the option to choose between the 3066 and the 3188..will continue to wait for a possible rk3066 version of 5.1.1....thx again
WECoyote633 said:
thx for info..that being the case this info might be mentioned in the first post....and the diy package perhaps shouldn't give the option to choose between the 3066 and the 3188..will continue to wait for a possible rk3066 version of 5.1.1....thx again
Click to expand...
Click to collapse
It is mentioned in the Lollipop thread and I think the original thread for booroondook's ROM, which is still open, this thread is kinda superfluous really.
I have a screen for avelo toyota
Puild number rk3188-eng4.4.4 310 ....
Android 4.4.4
MCU version
Mtcb-ksp-v2.86
I would like to update it to 5.1
Is the a suitable version for me ? Because most of the versions i found are mtcb-kdl
Is this version ok with me.? Does it effect my screen ?
---------- Post added at 04:22 AM ---------- Previous post was at 04:21 AM ----------
My problem is my device is 4.4.4 I would like to update to 5.1.1 and my device type is mtcb ksp
I didn't find an update please tell me how to update it
mr-mo7ammad said:
I have a screen for avelo toyota
Puild number rk3188-eng4.4.4 310 ....
Android 4.4.4
MCU version
Mtcb-ksp-v2.86
I would like to update it to 5.1
Is the a suitable version for me ? Because most of the versions i found are mtcb-kdl
Is this version ok with me.? Does it effect my screen ?
---------- Post added at 04:22 AM ---------- Previous post was at 04:21 AM ----------
My problem is my device is 4.4.4 I would like to update to 5.1.1 and my device type is mtcb ksp
I didn't find an update please tell me how to update it
Click to expand...
Click to collapse
Answered 10 times already!
MCU is not important, you already have MTCB unit so you can flash MTCB roms (4.4.4. or 5.1.1.)
you are probably afraid because of ksp-v2.86, that does not matter so you can flash any MTCB based rom.
mr-mo7ammad said:
I have a screen for avelo toyota
Puild number rk3188-eng4.4.4 310 ....
Android 4.4.4
MCU version
Mtcb-ksp-v2.86
I would like to update it to 5.1
Is the a suitable version for me ? Because most of the versions i found are mtcb-kdl
Is this version ok with me.? Does it effect my screen ?
---------- Post added at 04:22 AM ---------- Previous post was at 04:21 AM ----------
My problem is my device is 4.4.4 I would like to update to 5.1.1 and my device type is mtcb ksp
I didn't find an update please tell me how to update it
Click to expand...
Click to collapse
Would probably be a good idea if you read the wiki before posting.
Does anyone know how modifing exception apks for MTCScreenClock? After I modified Build.prop to activate the Screenclock, it only works when radio apk, music apk,... are working and I'd like it works always except when I'm using GPS navigator.
By the other hand, I'd like to change transparent background for MTCScreenclock and I know that the installed MTCScreeclock.apk is not the issue because I used the same and it wasn't transparent in KitKat versions. Thank you
I have got installed in my headunit last LP version of DSA (5.1.1.).

Guide and general questions

Hi there,
Just bought this Unit: https://www.amazon.de/NAVISKAUTO-To...8&qid=1467705714&sr=8-1&keywords=naviskauto+7
I open the frontcover and there ist no RK3188 writen. There is an PX3, can i flash the Malaysk rom anyway?
Is there a noob guide for updating these kind of Android devices? I flashed many phones and tablet but the MCU stuff is really confusing me and i didnt find a guide over here yet.
Furthermore, can i setup a Low pass filter (LPF) for certain chinch outs on the device itself or in MalaySK Rom?
Thanx in Advance

Rollback to EMUI 4.1.1 (VNS-L21)

Hi guys, I wanted to get EMUI 5 on my P9 Lite and I did, I used Firmware Finder but that thing automatically updated my phone to NRD90M test-keys.... Is it possible to go back to VNS-L21C432B160 and then maybe properly upgrade to 5.0 and having the same build number?
Edit: I managed to Rollback the OS, now all I need is a way to finally upgrade to EMUI 5.0. I'm sorry if this question has been posted before, please delete this thread if it's a problem. But I would actually need some help with the update, if possible.
This is the P9 forum. Why dont you look in the P9 lite forum? You probably will find anything you need there without opening a new thread.
xtcislove said:
This is the P9 forum. Why dont you look in the P9 lite forum? You probably will find anything you need there without opening a new thread.
Click to expand...
Click to collapse
That was my mistake... I found other questions about P9Lite on this section, that's why I posted here... Anyway, I managed to fix all my problems, so I'm asking for a nice moderator to remove this thread if possible. Sorry for any inconveniences.
VladCarlsson said:
That was my mistake... I found other questions about P9Lite on this section, that's why I posted here... Anyway, I managed to fix all my problems, so I'm asking for a nice moderator to remove this thread if possible. Sorry for any inconveniences.
Click to expand...
Click to collapse
Probably a mod will move this thread.
Why dont you post your solution?
xtcislove said:
This is the P9 forum. Why dont you look in the P9 lite forum? You probably will find anything you need there without opening a new thread.
Click to expand...
Click to collapse
xtcislove said:
Probably a mod will move this thread.
Why dont you post your solution?
Click to expand...
Click to collapse
Oh yes, sure! So the solution is as it follows:
To get back on MM:
1. I downloaded and updated my device using L21C432 (EU) from this thread - https://forum.xda-developers.com/hu...torial-rollback-n-to-mm-c432-devices-t3563955 - I got a small incompatibility error but I just skipped it.
2. I downloaded and update my device using L21C432B160 from the same thread and this way I got back to the proper build of EMUI 4.1.1
To upgrade to N:
1. I installed Firmware Finder
2. I upgraded the OS from 4.1.1 to 5.0 using the L21C432B370-OTA-MF-PF file (1.9 GB if I remember correctly).
3. After the upgrade was finished I just did a factory reset to get it to run as smooth as possible.
Everything worked just fine on my device. Camera works, bluetooth works, I haven't had any problems except the fact that I have 2 IMEI's now... probably because of that NRD90M test-keys build that was flashed by mistake. I don't think it should be a problem anyway

Have Pumpkin ND0286B-A08 now, advice for a rootable HU needed

Hi, I have spent many hours on this forum and others trying to learn how to root this android 8.0.0 head unit, I have read a lot and tried several ways including pushing SU apk to it with wifi (would never connect on port 5555), if someone could just tell me what (if any) method will have best chance of rooting? Link would be awesome. HU Details below.
OR please advise me what is the most easily rootable similar Android head unit? So frustrated am willing to just buy another head unit for root ability. Anyone have a similar pre-rooted one they want to sell? I'd pay more than list price for it. Thanks.
Pumpkin ND0286B-A08
px5-userdebug 8.0.0
MTCE_KLD_V2.94e_1
8-core 64bit [email protected]
Kernel Version 4.4.93+
Patch Level October 5,2017
Use Hal9k! It has a modinstaller.apk which roots, installs recovery and installs the rom. Just sideload the apk.
philicibine said:
Use Hal9k! It has a modinstaller.apk which roots, installs recovery and installs the rom. Just sideload the apk.
Click to expand...
Click to collapse
Hi sorry for late reply, I almost gave up. But am going to try this. If this works I will gladly donate to both you and the author of the rooter. Thank you!!!!!!!!!!!!!!!!!!!!
Glad you got it sorted!! Thanks for the beer tokens!! ?

Csn2 px6

hello, I bought a tablet car android px6 csn2 from Aliexpress .. I noticed that the software is locked, I read around that the mcu is proprietary ... is there a way to unlock it and install the root? The mcu number is cns2-d-12282019..
help me please
belin333 said:
help me please
Click to expand...
Click to collapse
Posted in wrong section and missed the multiple threads related, what would help?
Sorry.I would like to know if it is possible to modify the mcu which is now blocked and if it is possible to root

Categories

Resources