update errors... 'This package is for "rk3368" devices; this is a "PX5" ' - MTCD Android Head Units Q&A

update errors... 'This package is for "rk3368" devices; this is a "PX5" '
Trying to update my unit from Android 8 to Android 9. Tried the simple and direct update but it failed. But, I didn't get the black screen. So, I made the bootable sdcard and tried that way. SD card runs, does it's thing, says it was successful and tells me to remove it to reboot. When I do, it goes to a black screen and nothing else. Even after leaving it sit for 30min. That SD flash process was waaaay fast for it to have actually flashed the image.
Now, I can't get the unit to do anything without that SD card.
I have found that if I pop the SDcard out between the logo screen and when the flash process starts it errors and takes me to recovery. From there, I've tried many different roms. Hal9k versions, Malaysk versions, stock 8.0, ota 9.0 for my device, and even a 6.1.1 version.
After going to "Installing update..." most give me an error "Warning: No file_contextsE3004: This package is for "rk3368" devices; this is a "px5"" then a couple of other errors before a (Status 7) Installation aborted.
All the roms that didn't do that have some kind of signature error. Likely need to redownload but haven't tried yet.
Not really sure what to try from here...
The device had the MCU of MTCE_GS_V3.01_3 when I started. I was able to update it to MTCE_GS_V3.40
The original build number was px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.201812222.104950 test-keys though I suspect that doesn't really matter.

Couple photo screenshots.
First one is the error.
Second is what it says after the bootable sdcard runs. I see nothing there about installing the update.zip
Last is what I get sometimes if I eject the ad card too soon trying to get to the recovery menu.
{
"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 Redmi Note 7 using Tapatalk

And... I fixed it.
Didn't find anything for this error using the search here. Did a search on google and it linked me to a post on this thread https://forum.xda-developers.com/an...5-mtcd-e-head-unit-discussion-thread-t3929597
A reply told the user having the same problem to follow the SD card instructions at the beginning of the thread.
Instructions were the same as what I already followed but the file linked in the first post is different.
So, went through the process again. Installed that recovery and then was able to actually flash Android 9 onto mine.
Now for the fun part of getting everything configured and decide if this custom rom is the rom for me, if I go with the other one, or if I go to a more stock one. Least I can listen to the radio again...

Related

[Q] Two or mor packages contain the same file?

My Focus 1.3 still wont detect the retail updates via zune so I am trying to use the manual update featured here: http://forum.xda-developers.com/showthread.php?t=1306415
However, after it does a bunch of installing and reboots my phone I get an error indicating 'two or more packages contain the same file' and cant figure out why it is doing this.
Any ideas?
{
"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 had the same failure to the update 8107, i solved it that way, sending one by one cabs to the device... first one language, the 2ns 3rd 4th an so on... then the last update 8107 arm something... that solved my problem. but it can also be a ROM problem, if it is a custom rom... in the end if nothing works try a phone reset, then try to send this cab files.
Dinchy87 said:
i had the same failure to the update 8107, i solved it that way, sending one by one cabs to the device... first one language, the 2ns 3rd 4th an so on... then the last update 8107 arm something... that solved my problem. but it can also be a ROM problem, if it is a custom rom... in the end if nothing works try a phone reset, then try to send this cab files.
Click to expand...
Click to collapse
So are you saying I should remove all but one of the .cab files and run the utility? I havent done that but I'll give it a shot if that is ok to do.
Hmm, so I did this to the first .cab file and it updated me to 7.0.7403.0. However, so far the next one(s) in line will not go. They say "No applicable packages" and, of course, Zune still doesnt think I need any updates.
Edit: Actually, I think I see why. The first update which is supposed to take me to (7.0.7004.0) actually went all the way to 7403. Trying the 7403+ cab file now.
I started going one at a time and it got me partially updated but then one error out and basically bricked the phone (boot loop). I flashed back to 7004 and this time, for whatever reason, Zune detected the updates all the way up to Mango. The previous time I had flashed to 7004 it did not do that. I am now on 7.10.7720.68. I dont know if that is the 'latest' official release, but it appears to have the mango features at least.

Need help for Nexus 7 2013 wifi

Hi everyone,
I bought a NEXUS 7 2013 (ASUS-2B16) a few days ago and I didn't like 5.0 so I started to downgrade by myself.
I followed the instruction of this page (I chose 4.4.2 (KOT49H) rom)
https://www.androidpit.com/how-to-downgrade-a-nexus
When I finished everything (I assumed everything went well because I didn't see any error message) and start to run the system, it stays on this screen
{
"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 thought 4.4.2 is not compatible so I flashed with 4.4.4(KTU84P) manually but with no luck.
So I tried Nexus Root Tool Kit see if I could fix it but again with no luck.
I started to do the research and I found this post from XDA
http://forum.xda-developers.com/showthread.php?t=2380913
The post description shows the same problem that I have so I followed the instruction until the step "FORMAT DATA in TWRP" then I am stuck again. IT shows an error message that the formation is failed.
After everything I gave up and I tried to follow this post to restore my Nexus 7
http://forum.xda-developers.com/showthread.php?t=2381438
Everything went well but AGAIN I am always stuck at loading page.
I started to look at details and I found some error messages as following.
First I found my Nexus 7 has no OS installed (I am not sure)
Secondly I found the tablet is trying to mount files from E drive but always fail.
I am totally a noob with Tablet but from my experience on Windows system I guess I deleted backup partition by accident. I am hoping this information could help you guys to help me repair my tablet. If you guys need more details please let me know. Thanks in advance.
Sorry, one more thing. When I enter the command "adb devices" at DOS mode I am not able to find the devices. However, when I enter bootloader mode my computer is able to connect to my tablet. Hope this could help. Thanks.
nobody can help ?

Soft brick one sv

Hi everyone. Please bear with me I am a complete noob at this stuff.
I have a HTC one sv c525e K2_ul 4.2.2 S-on in Aus with optus (maybe LTE??)
The storage space for apps is tiny so I wanted to root the phone to re-compartment space.
I eventually found and followed the tutorial by qbking77 to unlock the phone and root it. I did well up until entering recovery to root the phone. The twrp image I used didn't work on my phone. I tried several of them with same result. Somewhere along the line I got the bootloop. I don't recall if it was before or after I tried to flash this I think I tried some other kernel that I can't find now.
Anyway I went back to twrp and tried more images. One finally worked to get into recovery. It was- twrp-2.8.6.0-k2_cl.img 10.4M the second listing under HTC One SV Boost USA (k2_cl).
So now I could enter recovery mode I went back to qbking77's tutorial. I found the options and process on my phone was different to his and I had a few errors come up like unable to mount sdcard, storage and some other stuff. As a result I was unable to do a back up and unable to install super user. From there I still got the bootloop.
Although internal sdcard and storage was unable to mount the phone did see the external sd card. So I loaded the super user zip direct from pc to sd card and opened the zip in recovery. Still bootloop.
I was wondering if I managed to unwittingly delete some important ****. So in my brilliance to persevere with screwing with it, I loaded the venom ROM (and some kernel) onto the ext sd card and opened it in recovery. Still several errors came up and I wasn't given any options to pick before flashing. It did say installation was a success at the end. Still got bootloop.
So I am hoping someone might see an obvious f-up that would turn into an easy fix ......... :laugh:
So I've been doing some reading :angel: but I'm no better off. I watched closely what I was doing and I was getting an MD5 error. I tried downloading the zips in firefox so as not to corrupt them but the phone is still coming up with 'missing MD5'.
I'm thinking my only option at this point is to run the RUU as I've seen that suggested a few times to others. Looks like a PITA but I guess it's that or new phone
I don't know when I'll get around to doing it.
Looking into RUU I need the S-off. Since I can't boot the system does anyone know how I can switch the S to off through fastboot or recovery?
So I was too lazy to run the RUU. I again attempted to flash the viper ROM. In recovery it says it was a success but I still get the bootloop. I noticed when I went into recovery something would flash up on the screen but it was too quick for me to read so I took a picture of it. Does anyone know what any of it means?
{
"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"
}

All Google Apps were crashing on CM13 - Android 6.0.1 (P3100)

Today i flashed the latest CyanogenMod13 on my Galaxy Tab 2 3G, the zip name was cm-13.0-20160517-1925-UNOFFICIAL-espresso3g.zip. I have followed the instruction of official developer Android-Andi to flash the ROM precisely. I was also flashed Mini Google Apps from Open GApps the ARM version and for Android 6.0. And i flashed too an Android Keyboard for M.
The flashing was success, but not 100% success. At the 'welcome' menu, suddenly all Google Apps were crashing at the same time and lagging my Tab.
{
"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"
}
Also i found that all Google Apps icon turned to unknown or android icons. And some application like File Manager ceases to open and said that 'Package Installer has stopped working.' And some time ago i bluetoothed an Android games called 'Beat the Boss 4' but when i want to install it says 'There's no app to handle this type of files'.
Can someone help me?
Yopu can try different gapps.
On OpenGapps also make sure to not to setup your google account before giving all permissions!
Hello, I've got the same problem on P 5110 and I've tried lots of sources of GAaps. Help please
I'm having exact same issue on my P3110, tried flashing for many times with different Gapps still persist, subscribing to this threat.
Same problem on p5100, cm13 with openapps 6.0 pico. also tried with gapps-600-base version, and a-gapps 6.0.1 one .
tried going to cm 12.1, and same problem there (with 5.1 apps ). what is going on?
E: tried some more- does not matter if i clean the internal memory. does not matter if i flash rom+gapps, or rom-reboot-gapps. Is this ****ery something to do with TWRP? i flashed the newest one, 2.8.5.0. I have not seen something this bad on no other device (have flashed nexus 7, SE arc s, xperia sp, lg g2 several times...)
E2: Got my gapps to work, atleast with CM12.1, wont try to install CM13 as dont need it for this tab. But might work in 13 aswell. Be sure to update your recovery, newest recoveries from http://forum.xda-developers.com/showthread.php?t=2676180 . I had 2.8.5.0, which according to this twrp site was the one available. But the thread I linked has 3.0 something. I used this queue zip flashing with rom+gapps, and now its working. Worth a try if you havent.
hello
if first install
hard wipe
to go back to twrp 2.8.50
put old recovery.img in twrp 3 (andi gave this solution)
regards

Question ROG 5s Update after Converting from CN to WW

I have been trying to update my phone for a while now but for some reason I am unable to, when I got the phone I followed this guide to convert it from CN to WW, and it worked well
But right now I am stuck at at version 18.1220.2109.126,
Every time I try to update to android 12 I am greeted with this
{
"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 anyone could help me with this I would be really grateful, no matter what version I use I am always getting the same message
Update incrementally up to the version you want to get to.
Andrologic said:
Update incrementally up to the version you want to get to.
Click to expand...
Click to collapse
its not working man, i almost tried every firmware
Flash RAW firmware (use the script / binary WITHOUT a wipe), then update normally.
If all else fails, you can perform the update with fastboot. It won't fix the issue and will have to be done for every future update, though.
Bypass "System update failed" - Update w/ Fastboot
Update notifications appeared, the update was recognized, but it failed instantly. I have since resolved the error by flashing a raw firmware without a wipe. This post is for archival purposes or simply an alternative installation method...
forum.xda-developers.com
twistedumbrella said:
Flash RAW firmware (use the script / binary WITHOUT a wipe), then update normally.
If all else fails, you can perform the update with fastboot. It won't fix the issue and will have to be done for every future update, though.
Bypass "System update failed" - Update w/ Fastboot
Update notifications appeared, the update was recognized, but it failed instantly. I have since resolved the error by flashing a raw firmware without a wipe. This post is for archival purposes or simply an alternative installation method...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried both, but every time I try to run a script, be it flash raw or the flash_all, I keep getting waiting for devices, even though my phone is connected to my pc(through the side port) and is in fastboot/bootloader.

Categories

Resources