Related
I am trying to find a good head unit for my Scion TC 05, and an android tablet/headunit is perfect for its radio hatch.
I have recently purchased several android head units. The first being a Pyle 480x800 DVD + android headunit, model PLDNAND692. It ran 4.4.4 KitKat, but the screen resolution was too low, dpi made interface look terrible, and DVD drive was not needed. Netflix played fine though. It runs a RK3066, yet a quad core configuration.
I returned the Pyle due to the old software, low res screen, and overall buggyness with DVD drive.
Recently purchased both a Pumpkin and a Joying Headunit from amazon, and both have no problems with Hulu, Youtube, and other streaming video services, but when trying to view Netflix on either, I am met with a Error code 0013. I have tried all possible fixes, including clearing data, uninstall/reinstall, installing an older build, and a factory reset. Please help.
1) go to system->apps
2) force stop
3) clear data and clear cache
4) uninstall
5) reinstall
nixfu said:
1) go to system->apps
2) force stop
3) clear data and clear cache
4) uninstall
5) reinstall
Click to expand...
Click to collapse
Already did that.
Did it again for good measure, same result
Sent from my SM-G935T using Tapatalk
Emailed with joying, and they confirmed that Netflix has a problem with mtcd units with lollipop. I just bought the kit kat version of the radio instead. Much smoother UX, and doesn't have the memory leak problem lollipop is known for. Lollipop looks better, granted, but their kit Kat models are more fleshed out. And way easier to root.
Sent from my SM-G935T using Tapatalk
thachosenone said:
Emailed with joying, and they confirmed that Netflix has a problem with mtcd units with lollipop. I just bought the kit kat version of the radio instead. Much smoother UX, and doesn't have the memory leak problem lollipop is known for. Lollipop looks better, granted, but their kit Kat models are more fleshed out. And way easier to root.
Click to expand...
Click to collapse
I just bought lollipop version, can you root and downgrade to KK?
[email protected] said:
I just bought lollipop version, can you root and downgrade to KK?
Click to expand...
Click to collapse
Don't even need to root. Just flash a compatible 4.4. ROM.
I also have a Lollipop unit (KLD6 2.97, RK3188, 1024*600) downgraded to 4.4 and couldn't be happier.
m00n61 said:
Don't even need to root. Just flash a compatible 4.4. ROM.
I also have a Lollipop unit (KLD6 2.97, RK3188, 1024*600) downgraded to 4.4 and couldn't be happier.
Click to expand...
Click to collapse
Did you get firmware from Joying website?
[email protected] said:
Did you get firmware from Joying website?
Click to expand...
Click to collapse
No, I am using Booroondook's 4.4. ROM - get it from HERE
Installation procedure HERE
I like Booroondook's ROM because it's very close to stock.
If you fancy flashy graphics, get Malaysk's ROM from this thread
Both are rooted, have FUSE, Xposed framework and allow for lots of customizations.
m00n61 said:
No, I am using Booroondook's 4.4. ROM - get it from HERE
Installation procedure HERE
I like Booroondook's ROM because it's very close to stock.
If you fancy flashy graphics, get Malaysk's ROM from this thread
Both are rooted, have FUSE, Xposed framework and allow for lots of customizations.
Click to expand...
Click to collapse
Thanks a lot! Any reason why carjoying say dont update 5.1.1 units with Malaysk rom from XDA? Anyway I guess it doesn't matter if I am downgrading.
[email protected] said:
Thanks a lot! Any reason why carjoying say dont update 5.1.1 units with Malaysk rom from XDA? Anyway I guess it doesn't matter if I am downgrading.
Click to expand...
Click to collapse
Make sure you have a MTCB or MTCC unit.
Joying also produces MTCD units and those are not compatible. Actually they say: If you have Malaysk don't try to upgrade to 5.1 using our ROM image, that is for MTCD units and will not work on yours.
If you do have a MTCD unit check the dedicated section.
m00n61 said:
Make sure you have a MTCB or MTCC unit.
Joying also produces MTCD units and those are not compatible. Actually they say: If you have Malaysk don't try to upgrade to 5.1 using our ROM image, that is for MTCD units and will not work on yours.
If you do have a MTCD unit check the dedicated section.
Click to expand...
Click to collapse
Mine is MTCD
[email protected] said:
Mine is MTCD
Click to expand...
Click to collapse
You can still try @Malaysk MTCD ROM:
http://forum.xda-developers.com/and...lopment/rom-malaysk-roms-mtcd-device-t3385309
m00n61 said:
You can still try @Malaysk MTCD ROM:
http://forum.xda-developers.com/and...lopment/rom-malaysk-roms-mtcd-device-t3385309
Click to expand...
Click to collapse
Thanks, looks like I'll be busy over the weekend then!
So instead of following advise I decided to attempt to root my device with the thinking that I may be able to take a nandroid backup before tinkering with custom firmware. Anyway I followed another thread directions for rooting my particular device using the *#... code through settings factory reset and then kingroot, SuperSU etc etc.
IT WORKED!
I then for no reason opened the kingroot app again and it started its process again by me possibly clicking something and the device rebooted and got stuck on Joying screen bootloop, I couldn't even get back into recovery...for some time.
I know this is way off topic as this is more related to root than this threads topic but there seems to be limited threads on these devices and I thought by chance someone might be able to help.
I have been able to boot to recovery several times and factory reset, install stock firmware, update firmware etc but all seem to install then get stuck on lollipop screen.
Please see attached photo, this is where I'm at.
I'm sure, given that I can boot to recovery I should be able to fix this issue eventually with the right firmware files but I am more curious about the file structures when you download a firmware package.
Some downloads just have .img file and some have two files dupdate.img and dmcu.img.
Can someone explain what these files are and why some downloads only have dupdate.img.
Also if someone has a solution for my issue or a link to another thread that could help please let me know or I guess I'll keep flashing firmware packages until something happens.
Happy new year!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my A0001 using XDA-Developers mobile app
I was able to fix my HU with Malaysk method after I had rooted the device and rendered it officially bricked!
https://forum.xda-developers.com/an...lopment/rom-malaysk-roms-mtcd-device-t3385309
Here is a link to my post in another thread.
http://forum.xda-developers.com/showthread.php?p=70353375
Sent from my A0001 using XDA-Developers mobile app
Warm Notice：
If your system is working well, please do not upgrade it !!!
Because the upgrade is risky, it might lead to CRASH, BLACK SCREEN, OR SYSTEM ERROR;
Unless there is a major bug in the car system, it unable to be used normally.
At this time, you can choose to upgrade the system to solve it.
contact your dealer to make sure you are choosing the right firmware and right update steps
MTCH
3.80 : https://www.dropbox.com/s/4kl7j2gsgdjt527/MTCH_HA_V3.80.rar?dl=0
MTCE MCU
3.78：https://www.dropbox.com/s/3hd3ci3rp07ddnt/dmcu.img?dl=0
Android 11 Update
MAX11 Version：Make Sure your unit is PX6 Andorid 11
HA3_rk3399_11.0_ota(20220601)
HA3_rk3399_11.0_20200601_ota.rar
Shared with Dropbox
www.dropbox.com
Vivid 11 Version Make Sure your unit is PX6 Andorid 11
telenav_vivid_rk3399_11.0_ota(20220518)
telenav_vivid_rk3399_11.0_ota(20220518).zip
Shared with Dropbox
www.dropbox.com
HCT Firmware PX6 Android 11 Make Sure your unit is PX6 Andorid 11
HCT8_rk3399_11.0_ota2820220412
HCT8_rk3399_11.0_ota(20220412)升级包.zip
Shared with Dropbox
www.dropbox.com
Android 10 Update
MAX10 Version：Make Sure your unit is PX6 Andorid 10
HA3_rk3399_10.0_ota(20220521)
ha3_rk3399_10.0_ota(20220521+bt_mcu).zip
Shared with Dropbox
www.dropbox.com
Vivid 10 Version: Make Sure your unit is PX6 Andorid 10
telenav_vivid_rk3399_10.0_ota(20220518)
telenav_vivid_rk3399_10.0_ota(20220518).zip
Shared with Dropbox
www.dropbox.com
Scout 10 Version : Make Sure your unit is PX6 Andorid 10
telenav_scout_rk3399_10.0_20220527
telenav_scout_rk3399_10.0_ota(20220527).zip
Shared with Dropbox
www.dropbox.com
hotaudio said:
hi guys
I will share the latest link with MCU and updates here
V2.40 https://drive.google.com/open?id=0B_wOizoYdqYQcUpEVDc0ZHVDaG8
does anyone have online drive recommend ? my google drive is full
the android 6.0 update is more than 1 GB :angel:
Click to expand...
Click to collapse
Perhaps a second Google account to host just the updates?
Thanks for the updated MCU - will be applying to this unit:
http://www.ebay.com/itm/Android-6-0...ash=item3adbb3b7b6:g:QI8AAOSwTuJYt3cd&vxp=mtr
Do these MCU updates have a change log of some sort?
I have downloaded and instead the latest MCU and full firmware. It still goes to sleep instead of turning off, draining the car's battery. ?
93starletgt said:
I have downloaded and instead the latest MCU and full firmware. It still goes to sleep instead of turning off, draining the car's battery. ?
Click to expand...
Click to collapse
what unit you have
hotaudio said:
what unit you have
Click to expand...
Click to collapse
The same one you're adverstising:
https://www.aliexpress.com/item/Das...h-2-DIN-Universal-Car-NO-DVD/32789102885.html
Can i use it for Erisin ES6405v?
MTCD_KGL_V2.11_1
Px5 Soc
For Volkswagen
93starletgt said:
The same one you're adverstising:
https://www.aliexpress.com/item/Das...h-2-DIN-Universal-Car-NO-DVD/32789102885.html
Click to expand...
Click to collapse
this unit universal do not eat the consume the car battery . just be sure you ACC cable not connect to B+
93starletgt said:
The same one you're adverstising:
https://www.aliexpress.com/item/Das...h-2-DIN-Universal-Car-NO-DVD/32789102885.html
Click to expand...
Click to collapse
this unit universal do not eat the consume the car battery . just be sure you ACC cable not connect to B+
Ati_gangster said:
Can i use it for Erisin ES6405v?
MTCD_KGL_V2.11_1
Px5 Soc
For Volkswagen
Click to expand...
Click to collapse
I did not try , but I do not recommend to use on other brand
PX5_6.0 UPDATE (20170304) sendspace
link dont work, can you check it?
@hotaudio Android O starts support aptX codec and another codecs. May you add something for better BT sound quality ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am really confused as to which file I put on the SD card to update the MCU. Can someone please point me in the right direction. Super NoOb here.
Is the first file the MCU update and the second file the android update?
@hotaudio Can you update your bluetooth phone app to include a mute button? It is relatively useless for me without this feature (need to be on mute over long meeting calls with a kid in the car)
or otherwise provide information on how to replace this app with another phone app?
dfarmer0033 said:
I am really confused as to which file I put on the SD card to update the MCU. Can someone please point me in the right direction. Super NoOb here.
Is the first file the MCU update and the second file the android update?
Click to expand...
Click to collapse
the mcu update is just a few Kilobytes while the ROM (firmware) update is above 700MB
the mcu update file shall be named as dmcu.img (if you received a Zip file with both ROM & MCU, decompress it to get both)
put it on SDcard as mentioned and go to settings>System information>MCU update
@hotaudio is there a easy way to gain root for your system?
I was able to update. Everything went fine except now when I turn the car on and the HU wakes up it displays "Unfortunately Music has stopped working". Anyone know of a fix. Might try a wipe and install of the update. Any thoughts appreciated.
dfarmer0033 said:
I was able to update. Everything went fine except now when I turn the car on and the HU wakes up it displays "Unfortunately Music has stopped working". Anyone know of a fix. Might try a wipe and install of the update. Any thoughts appreciated.
Click to expand...
Click to collapse
Same issue - 030217 update. When I had originally installed the 030417 update from another PX5 thread here, this issue was not present. I downgraded to the 030217 update to stick with the current Dasaita build.
droc.noles said:
Same issue - 030217 update. When I had originally installed the 030417 update from another PX5 thread here, this issue was not present. I downgraded to the 030217 update to stick with the current Dasaita build.
Click to expand...
Click to collapse
Which version is in the zip file at the top of this thread? That is the one I used.
hotaudio said:
hi guys
PX5_6.0 UPDATE (20170324) https://www.sendspace.com/pro/dl/jpnu9k
Click to expand...
Click to collapse
@hotaudio any chance you could give us a basic change log on these upates? What is new/fixed in 2017/03/24 ? Same goes for MCU updates. Thanks!
aeonfluxcapacitor said:
@hotaudio any chance you could give us a basic change log on these upates? What is new/fixed in 2017/03/24 ? Same goes for MCU updates. Thanks!
Click to expand...
Click to collapse
hi
is the system update , fix the google maps sound bugs
When updating my PX5 from Android 8 to Android 10 of my Mitsubishi Outlander the radio got messed up, the physical buttons stop working, and it gives a version error, where can I get the correct version for this radio? thanks ...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Seems like you flashed an MCU as well as the ROM and it was the MCU from a different manufacturer, in order to restore it you need to find out which manufacturer your unit is from. Do you know ?
typos1 said:
Seems like you flashed an MCU as well as the ROM and it was the MCU from a different manufacturer, in order to restore it you need to find out which manufacturer your unit is from. Do you know ?
Click to expand...
Click to collapse
hello, unfortunately I don't know the manufacturer, I bought it on Aliexpress, and now the seller is no longer active, and there is no manufacturer reference on the radio.
Take some pics of the sides, back and underneath if the unit - may be able to identify it. Do you remember what the MCU was before ?
EDIT : Hold on, that wallpaper suggest that it might be a KGL unit - upload those photos to confirm. Flashing a KGL MCU may help, but with no mcu.cfg it may be a struggle to restore everything. Having said that the wallpaper will have just come from the ROM you flashed, so probably best open the unit up and get the manufacturer from the motherboard to be certain.
typos1 said:
Take some pics of the sides, back and underneath if the unit - may be able to identify it. Do you remember what the MCU was before ?
EDIT : Hold on, that wallpaper suggest that it might be a KGL unit - upload those photos to confirm. Flashing a KGL MCU may help, but with no mcu.cfg it may be a struggle to restore everything. Having said that the wallpaper will have just come from the ROM you flashed, so probably best open the unit up and get the manufacturer from the motherboard o be certain.
Click to expand...
Click to collapse
Hello typos1 tomorrow I put the photos of the motherboard, thank you very much for your help....
Ok, no probs
typos1 said:
Ok, no probs
Click to expand...
Click to collapse
hello Typos1, I disassembled the unit and took these pictures, will it help to identify? thanks
Ok, see where is says "XRC" ? That means you have an XRC unit, so flash the latest XRC MCU from the link in my signature and let me know if it sorts it.
typos1 said:
Ok, see where is says "XRC" ? That means you have an XRC unit, so flash the latest XRC MCU from the link in my signature and let me know if it sorts it.
Click to expand...
Click to collapse
Ok Type1, morning I will try, if one day you come to Portugal let me know, I want to buy you beer.
thanks
No probs, there may still be some things for you to do after you have flashed the MCU though, so let me know how you get on.
typos1 said:
No probs, there may still be some things for you to do after you have flashed the MCU though, so let me know how you get on.
Click to expand...
Click to collapse
hello typos1 , so far so good, with your help everything went well, over the weekend I’m going to install the unit in the car to test it, because right now it’s connected to a PC power supply, thanks again...
Cool, so everythings working ? I d install a later XRC MCU if I were you though.
typos1 said:
Cool, so everythings working ? I d install a later XRC MCU if I were you though.
Click to expand...
Click to collapse
hello typos1, I detected a problem, damn it, when I turn the physical sound button to the left, the sound decreases is correct, but when I turn to the right to increase the sound it decreases too, do you know what it could be?
why do people keep modifying car radio like that's so risky it would be terrible while your driving and radio suddenly start out of nowhere
Yes, it is because you did not go into factory settings and export your MCU settings before you flashed the MCU, you need to do this always, I understand it is because you did not know what you are doing but that is why you have the problem.
Go into factory settings and try and remap the buttons, but I dont think it works on the volume kob, you can also try changing the knob mode in factory settings. If none of this works you need to find someone with another XRC unit and try flashnig their mcu.cfg.
ineedroot69 said:
why do people keep modifying car radio like that's so risky it would be terrible while your driving and radio suddenly start out of nowhere
Click to expand...
Click to collapse
He did not "modify" it, he flashed a ROM without realising that there was an MCU file with it. As for mods, people have modified these stereos for years - check out all the threads about it - and mnay of these mods are very useful and correct bugs from the factory.
typos1 said:
He did not "modify" it, he flashed a ROM without realising that there was an MCU file with it. As for mods, people have modified these stereos for years - check out all the threads about it - and mnay of these mods are very useful and correct bugs from the factory.
Click to expand...
Click to collapse
yeah im not trying to criticize something im just amaze that people would "flash" not "modify" btw stuff as long as there running android such as car stereo system instead of sticking to stock version
What he flashed was a stock update, so still not a mod.
The factory ROMs are not good, again, for years people on here have modified and improved the facpory ROM, many, including me would never even use the factory ROM at all.
ineedroot69 said:
why do people keep modifying car radio like that's so risky it would be terrible while your driving and radio suddenly start out of nowhere
Click to expand...
Click to collapse
calm, what led me to do the upgrade was the radio brought factory problems, the clock was always incorrect, gps was never in the right place, etc., and the seller never supported me ...
typos1 said:
Yes, it is because you did not go into factory settings and export your MCU settings before you flashed the MCU, you need to do this always, I understand it is because you did not know what you are doing but that is why you have the problem.
Go into factory settings and try and remap the buttons, but I dont think it works on the volume kob, you can also try changing the knob mode in factory settings. If none of this works you need to find someone with another XRC unit and try flashnig their mcu.cfg.
Click to expand...
Click to collapse
Hello typos1, is it possible to downgrade the MCU? there are other versions in this list ...there may be one that can be compatible ?
Yandex
Finds everything
disk.yandex.com
NVIDIA Recovery Images for all Gen ShieldTV consoles.
Need to be flashed with fasboot.
How to is provided on the nvidia gameworks download site,
just check the 8.2.3 versions, right side you find Instructions.
Mirrors:
ShieldTV 2015
ShieldTV Pro 2015
ShieldTV 2017
ShieldTV 2019 Tube (8GB)
ShieldTV Pro 2019 (16GB)
Happy flashing.
Thank You!!
Don't forget to erase your Partitions if on Lineage or a dev build.. Here is how:
A guide how to use the recovery images for anyone using the shield root tools:
All Codes Are In The Description Boxes
final version or rc?
Has anyone else attempted this flash? I got it booted after a fresh partition wipe, bc yesterday, the launcher kept crashing, however, even today it continues to crash. I can play around in settings and i'm sure a custom launcher would work fine, however I had someone who wanted to see the stock version early and this is erm, not quite right haa...
and what i mean by crash is it intermittently flashes black and then back into the launcher. no discernable pattern or guess as to why. going to continue to toy with it and try to update it...
---edit i jumped the gun, i think those flashes were updates
----so after flashing the system over, wait for the shield to post into the chromecast screensaver, dont mess with it, then it will be fine
Hi guys
I tried to update my 2019 non pro shield with the how-to nvidia page I found here : https://developer.download.nvidia.c...-To-Flash-Recovery-Image-shield-atv-2019.txt?
But this method fails saying E:\ FAILED TO MOUNT /SDCARD
What ami doing wrong ?
My shield is non rooted, vanilia from scratch
Thx if someone can help
Fre$h said:
Hi guys
I tried to update my 2019 non pro shield with the how-to nvidia page I found here : https://developer.download.nvidia.c...-To-Flash-Recovery-Image-shield-atv-2019.txt?
But this method fails saying E:\ FAILED TO MOUNT /SDCARD
What ami doing wrong ?
My shield is non rooted, vanilia from scratch
Thx if someone can help
Click to expand...
Click to collapse
I think My main question would Be, and forgive me, because I'm learning as I go, While Running Stock, are you able to post into TWRP, after unlocking the bootloader?
Like, through fastboot, theoretically you shouldn't have to install the developer images as i did in my examples,,, but if you could get TWRP recovery to post, while in stock, with a momentarily unlocked bootloader, you should be able to run the OEM unlock code, then flash the staging blob, as well as the new images...
i do not mean to disrespect NVIDIA... but if you read their flash codes...
you can tell their devs are much more proficient on linux,
which is a great trait~! but it doesnt translate well for windoz userz...
Does anyone know if it is possible to update to consumer release via OTA after flashing this developer release?
I'd like to install this developer release on my girlfriend's Shield TV 2017 now and once Nvidia releases the consumer release, would she be able to update it via OTA? She is not technically proficient to update it to the consumer release by herself using fastboot and ADB.
Shield Experience 9.0.0 is working perfectly. I don't know why USB devices take forever to load files on Android 11 and crashes MX Player? Anyone else having the same issue? It's a developmental image so having these bugs occur is what happens. Anyways I reverted back to 8.2.3 and my issue is now resolved
MIRROR for anyone who hate the google spying!
nv-recovery-image-shield-atv-2019-pro-9.0.0.zip - Shared with pCloud
Keep, share and access your files whenever you need from wherever you are. Create a free pCloud account and make your life easier.
e1.pcloud.link
OR
PandaFiles
Download File
pandafiles.com
Seems like this new update does not like Magisk.
FLashing Magisk.zip causes me to be stuck going into bootloader.
@ jenneh - Did your notepad not have the replace option?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you can't get Plex Server up and running after installing this all, go here to sign up for the official hotfix from Nvidia or go here for the official hotfix from Plex.
LazorBlind said:
Seems like this new update does not like Magisk.
FLashing Magisk.zip causes me to be stuck going into bootloader.
Click to expand...
Click to collapse
NEVER MIND I LIED.
I tried to do the known working procedure from memory and missed a step, the method still works. Got latest update with root running row. Shame I had to do a factory reset while trying to figure things out but small sacrifices...
LazorBlind said:
NEVER MIND I LIED.
I tried to do the known working procedure from memory and missed a step, the method still works. Got latest update with root running row. Shame I had to do a factory reset while trying to figure things out but small sacrifices...
Click to expand...
Click to collapse
Thank you for sharing your experience, I have some issue... to prevent fragment external HDD I prefer ext4 fs and unfortunately the nvidia roms doesnt support at this time! So I install microg magisk module on LineageOS 17 but I encountered black screen! also I install official microG release: https://download.lineage.microg.org/mdarcy/lineage-17.1-20220110-microG-mdarcy.zip but I encountered black screen too!
see:
[RECOVERY] [OFFICIAL] TWRP for Shield Android TV
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven...
forum.xda-developers.com
I still only see the 8.2.3 recovery listed on the Nvidia website. I didn't sign in as a developer though. Where did you get version 9.0.0?
jolsowka said:
I still only see the 8.2.3 recovery listed on the Nvidia website. I didn't sign in as a developer though. Where did you get version 9.0.0?
Click to expand...
Click to collapse
It has been officially released. If you're not signed up as a developer or if the developer site doesn't work for you like it didn't for me, then your best bet is to lock bootloader (if it's unlocked), check for updates and then install the updates, then unlock the bootloader and add any/all of your modifications back.
Had issues bypassing Google login so jumped on the Lineage bandwagon. Is there anything worthwhile in 9.0 over 8.2.3?
Okay People,
Here's the dealio..
I purchased the HA5217-MAX10-CP-HD. It has been AMAZING! Until Last night I hopped in and It was stuck in Bootloop REcovery Mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I
I tried all the reset procedures, cleared the cache and finally got in but no sound came out of the unit and no SWC worked.. so I took a few pics to show the exact firmware I was using.
This was my original firmware when everything was working..
I Did all the reset procedures to make everything boot into Android but, none of my sound was working except the sound of the touches on the screen.
So, I navigated to the FIRMWARE FILE Download Sections here in the Forums and thought maybe I needed to reflash the firmware maybe the latest updated firmware. HA3_rk3399_10.0_ota(20221111) which is currently installed and now it boots into Android looks a little different.
I still have no sound , the steering wheel controls wont register, the customized EQ settings for the DSP are gone.
THIS IS THE WAY IT USED TO LOOK!
The canbus CB004 unit isnt showing vehicle info like (Door Ajar, Climate, ect. ) Also, No rearview camera fuction at all.
It used to have all these extra functions specific to my 2014 Toyota Corolla W/O JBL
My gut feeling is that I am missing something to do with a custom canbus firmware or extra APKs I need to load perhaps?
I'm not sure what an MTU / DMCU file does ... maybe I need one of those?
I really need help with this
I Made A Video Explaining the whole thing.
if your able to help me, I would really appriciate it!
You started out in the wrong end. Sound, SWC and reverse has nothing to do with firmware. It's a canbus problem. Due to the fact that no car is selected, canbus won't work. Select your car to start with.
Logos are not provided any more due to copyright problems. Google is your friend.
I know this is a month old. I have the MAX10 in my 2016 Toyota Tundra.
Have you tried to update the MCU? The current version is 3.78. In a worst case scenario your canbus adapter could be bad. Considering everything used to work
mranderonz81 said:
Okay People,
Here's the dealio..
I purchased the HA5217-MAX10-CP-HD. It has been AMAZING! Until Last night I hopped in and It was stuck in Bootloop REcovery Mode.
I
I tried all the reset procedures, cleared the cache and finally got in but no sound came out of the unit and no SWC worked.. so I took a few pics to show the exact firmware I was using.
This was my original firmware when everything was working..
I Did all the reset procedures to make everything boot into Android but, none of my sound was working except the sound of the touches on the screen.
So, I navigated to the FIRMWARE FILE Download Sections here in the Forums and thought maybe I needed to reflash the firmware maybe the latest updated firmware. HA3_rk3399_10.0_ota(20221111) which is currently installed and now it boots into Android looks a little different.
I still have no sound , the steering wheel controls wont register, the customized EQ settings for the DSP are gone.
THIS IS THE WAY IT USED TO LOOK!
The canbus CB004 unit isnt showing vehicle info like (Door Ajar, Climate, ect. ) Also, No rearview camera fuction at all.
It used to have all these extra functions specific to my 2014 Toyota Corolla W/O JBL
My gut feeling is that I am missing something to do with a custom canbus firmware or extra APKs I need to load perhaps?
I'm not sure what an MTU / DMCU file does ... maybe I need one of those?
I really need help with this
I Made A Video Explaining the whole thing.
if your able to help me, I would really appriciate it!
Click to expand...
Click to collapse
I have the same CB004 harness. I know for my Toyota Tundra I had to select 08 TOYOTA_CAMRY&RAV4.
I've installed the Dasaita's Scout, Vivid, Original MAX10 Firmwares, as well as hal9k and Malaysk modified firmwares and never seen it reset anything other than Android.
Then again these units do have some unique issues.
mranderonz81 said:
Okay People,
Here's the dealio..
I purchased the HA5217-MAX10-CP-HD. It has been AMAZING! Until Last night I hopped in and It was stuck in Bootloop REcovery Mode.
I
I tried all the reset procedures, cleared the cache and finally got in but no sound came out of the unit and no SWC worked.. so I took a few pics to show the exact firmware I was using.
This was my original firmware when everything was working..
I Did all the reset procedures to make everything boot into Android but, none of my sound was working except the sound of the touches on the screen.
So, I navigated to the FIRMWARE FILE Download Sections here in the Forums and thought maybe I needed to reflash the firmware maybe the latest updated firmware. HA3_rk3399_10.0_ota(20221111) which is currently installed and now it boots into Android looks a little different.
I still have no sound , the steering wheel controls wont register, the customized EQ settings for the DSP are gone.
THIS IS THE WAY IT USED TO LOOK!
The canbus CB004 unit isnt showing vehicle info like (Door Ajar, Climate, ect. ) Also, No rearview camera fuction at all.
It used to have all these extra functions specific to my 2014 Toyota Corolla W/O JBL
My gut feeling is that I am missing something to do with a custom canbus firmware or extra APKs I need to load perhaps?
I'm not sure what an MTU / DMCU file does ... maybe I need one of those?
I really need help with this
I Made A Video Explaining the whole thing.
if your able to help me, I would really appriciate it!
Click to expand...
Click to collapse
Did you ever get your issues fixed? I can help with the car logo because I noticed it was gone too. Go to car logo in factory settings and check the box that says "user" and the logos that used to be there will be back. And for the canbus selection, select 08 TOYOTA_CAMRY. I would also update your MCU to the latest version 3.78 Firmwares.