Firmwares


  • I can repeat it again: wrong upgrade package, could tyou pease upload the correct version?

    Android 10 Update  --> It is an ANDROID 11 package!!!!!

    MAX10 VersionMake Sure your unit is PX6 Andorid 10

    HA3_rk3399_10.0_ota(20230223) 

    https://www.dropbox.com/s/r3wwq02ag4zibp9/update.zip?dl=0 --> It's ANDROID 11:  rockchip/rk3399/rk3399:11/RQ3A....


  • I have the same problem and I think Dasaita doesn't care at all.


  • @Quick Yuan  please reupload / change links ...

    Android 10 Update  --> It is an ANDROID 11 package!!!!!

    MAX10 VersionMake Sure your unit is PX6 Andorid 10

    HA3_rk3399_10.0_ota(20230223) 

    https://www.dropbox.com/s/r3wwq02ag4zibp9/update.zip?dl=0 --> It's ANDROID 11:  rockchip/rk3399/rk3399:11/RQ3A....

     


  • If HA3_rk3399_10.0_ota(20230223) was strictly an Android 11 package, I wouldn't have had a successful upgrade from the latest Vivid 10 on my PX6. Maybe it fails updating from Max 10? Has anyone that failed try updating to latest Vivid 10 and then Max 10? I also only upgrade from the recovery menu. For this many people to have issues though, something is messed up with the update for sure.

     

     

     


  • The Elite  i downloaded Vivid 10  20230112 , then I wanted to uplod the latest MAX 10 20230223 , but is also shows an error and cannot be updatet . I dont know how you managet it , but there is definitely something wrong with this software .

     


  • Marek.Mok, yeah that is the same upgrade path I took. Well scratch that idea then! Yeah, Dasaita should troubleshoot whatever the issue is with the update and provide a new one.

     


  • Latest Max 10 Android 10 update HA3_rk3399_10.0_ota(20230223) works and updates just fine. Just have a slight annoyance with wired carplay disconnecting randomly and unable to reconnect sometimes. But I'd advise everyone that isn't able to update to check that they have the latest MCU downloaded and updated (MCU Version V3.78) on your system.


  • @Quick Yuan The MAX10 ota download link you put for Android 10 is wrong!! I loaded it to my device and it says Android 11 and now my device is bricked in boot loop!! Can't get into recovery mode!!  


  • The Max10 link is wrong, it won't update and comes up with a error, the asks to be rebooted.

    I checked and have the latest MCU version, you guys should really be double checking everything before posting stuff that doesn't work correctly as you could potentially be bricking people's systems with faulty updates! 


  • Not sure what might be the problem then. I have an android 10 PX6 unit and the update below works just fine for me. It was on a black screen with all the processes going while updating for a minute but other than that, it updated just fine. I used the update posted below and it worked just fine for me. I can assure you the link I downloaded below and update was NOT android 11 and infact android 10. Hope eveything works out soon and they find a fix for you guys. 

    Android 10 Update 

    MAX10 VersionMake Sure your unit is PX6 Andorid 10

    HA3_rk3399_10.0_ota(20230223) 

    https://www.dropbox.com/s/r3wwq02ag4zibp9/update.zip?dl=0


  • @tone T 

    Hi, it could depend on some integrated chip. My DASAITA does not have the integrated carplay chip, it has 1024x600 resolution and was native with android 9. MTCE MCU 3.78 installed first from the site.
    The packet (30) that doesn't update I'm not sure what it corresponds to...

  • @The Elite @Flame Red I think it is a mistake when publishing the OTA on this firmware section. This is the link for the OTA itself:

    https://scout-ivi.s3.amazonaws.com/v3.1/3.1.5/telenav_s4c_rk3399_10.0_ota(20221219).zip

    I personally tested this OTA in my unit successfully.

    Scout sytem, from version 3.0 features live OTA updates.

     

    Is there an OTA upgrade later than 22021219? I see telenav_s4c_rk3399_10.0_(20230111) out there now but that is not an OTA upgrade. Seems most have a 2023 upgrade available.

    Thank you!


  • @Bruno S @Bruno S I just made a topic about this myself!  I'm very frustrated with this. I can't even get into recovery, so I'm completely stuck. A big error 


  • @Anthony Bartman same here. This is ridiculous. Contacted dasaita and haven't received a reply yet. 

    Not being able to get into recovery is making this a huge deal. I'm totally stuck. 

     


  • I download the good firmware for Android 10 px6. And the stuck at Android logo.  I tink is a 11 Android version, ans i dont have the possibility to start m'y radio


  • Indeed there was a mistake in the MAX10 link, pointing to an A11 ota upgrade instead of A10. This morning Dasaita has removed the link and soon will provide a corrected one.

    For those who are suffering a bootloop or stuck on boot logo after trying to update to this wrong  OTA file please follow the following thread in order to solve the issue to everybody:

    Incorrect android version in current max10 px6 firmware provided by dasaita! Stuck on Android logo/unusable | Dasaita


  • @tone T if you decompress the update.zip and go to metadata udner META folder, you can see the 11 on the build. so it is in fact a A11 ota update.


  • @The Elite using different OTA files to the current Android major version will cause a corruption of the boot partition...don't do it.

    When the system is in such state it is difficult to get into the recovery menu (needed to solve this), but possible


  • @Iker Gomez I think what happened is Dasaita originally posted a Android Max 10 update, then updated the link with the wrong Android 11 update at some point shortly after.

    Because my update.zip file that I used, the metadata and actual system info from my screenshot show Android 10.

    post-build=rockchip/rk3399/rk3399:10/QQ2A.200305.004.A1/eng.hct.20230223.142052:userdebug/test-keys

    This wrong link update.zip shows a different build date and Android 11, it was actually HA3_rk3399_11.0_ota(20230103) and not HA3_rk3399_10.0_ota(20230223) 

    https://www.dropbox.com/s/r3wwq02ag4zibp9/update.zip?dl=0

    post-build=rockchip/rk3399/rk3399:11/RQ3A.210705.001/eng.hct.20230103.172626:userdebug/release-keys
    

     


  • @The Elite yes...seems you are right. I did not notice the date of the build. 


Please login to reply this topic!