ASUS RT-AC68U Firmware version 3.0.0.4.386.49703
Version 3.0.0.4.386.49703 95.32 MB
2023. 1. 7.
2022. 11. 17.
Dasaita Max10 HA3_rk3399_10.0_ota(20221111) 버전 설치 하였음.
아이폰으로 변경하고 carplay 사용하는데
그 전 버전은 연결이 불안하다. 될 때도 있지만 안 될때가 더 많음.
20111111 버전이 나와서 설치했음.
큰 차이점은 설정에서 안드로이드 오토/carplay 자동연결 설정이 생김.
zlink 버전이 5번전으로 업데이트됨.
공장설정에서 블루투스 설정을 아래와 같이 변경하였음.
BT SDIO-AUTO --> WQ_RF210 (설정 변경하면 전에 있던 페어링 정보 전부 삭제됨)
Android 10 Update
MAX10 Version：Make Sure your unit is PX6 Andorid 10
HA3_rk3399_10.0_ota(20221111)
https://www.dropbox.com/s/uzigr30m8p4cpaq/HA3_RK3399_10.0%E5%8D%87%E7%BA%A7%E5%8C%85%2820221111%29.rar?dl=0
2022. 9. 18.
Dasaita MAX10-Carplay-HD recovery mode 진입하기 안드로이드 올인원 무한 부팅 탈출 하기 복구하기
구매 제품 :
Dasaita For Toyota Camry 2012 2013 2014 자동차 네비게이션 용 카 스테레오 블루투스 라디오 Carplay Android Auto 1280x720 IPS 4GB + 64GB MAX10-Carplay-HD
자동차 네비용 안드로이드 카스테레오를 구입하여 잘 사용하였음.
안드로이드 10 버전용인데, 계속 업데이트를 해주고 있었음.
그런데 몇 일전 안드로이드 11버전이 웹에 올라온 것을 보고
오~~~~ 지원 잘 해주네....
받아서 설치.
https://www.dasaita.com/community/forum/topic/36770/firmwares
MAX11 Version：HA3_rk3399_11.0_ota(20220316)
이놈을 받아 냉큼 설치....
를 했으나...
무한 부팅에 빠짐...
어.....T.T
뭐지?
안드로이드 11버전 지원이 아닌가?
다시 안드로이드 10버전 설치해야겠다.
하지만 무한 부팅
리셋 버튼을 눌러볼까?
이리 저리 눌러보다가 recovery mode진입....
아... 안드로이드 10버전을 안 받았다.
컴퓨터로 받아서 usb에 넣어서 다시 차로 와서 recovery mode 진입해서
안드로이드 10 버전 설치해야지...
리셋 버튼 누르기....
5초 계속해서 누르기
10초 계속해서 누르기
15초
20초
25초
30초..
진입안됨.
5초 계속해서 누르기 다음 리셋버튼 1회 누르기
10초 계속해서 누르기 다음 리셋버튼 1회 누르기
15초 계속해서 누르기 다음 리셋버튼 1회 누르기
20초 계속해서 누르기 다음 리셋버튼 1회 누르기
25초 계속해서 누르기 다음 리셋버튼 1회 누르기
30초.. 계속해서 누르기 다음 리셋버튼 1회 누르기
진입안됨.
리셋버튼 누르는 시간에 따라 리셋버튼 2회 누르기
결론
진입안됨.
T.T
이러면 안되는데...
판매자에게 문의해보기로.....
판매자 답변... 안드로이드10으로 복구해라.
무한 부팅으로 조작 불가 라니까.
모르겠고. 복구하라네.
안된다고 몇번 이야기하니.
수리해야 된데...
기판 변경해야된다고 함...
기판 가격 170 미국 달러...
일단 알았다고 하고 쳇 종료.
인터넷 검색
2일 차...
안드로이드 부팅 sd카드 만들어 복구할 수 있다고 함.
========================
https://forum.xda-developers.com/t/mtcd-e-android-10-upgrade-using-official-free-tools.4123933/
To upgrade a MTCD/E PX3, PX5, PX6 from Android 6+ on using official Rockchip free tools - a reminder, bringing together multiple threads.
First note - if coming from Android 6 - early versions of Realtek dual BT/WIFI (type 2) are not supported past Android 6.
[29/06/2020 - Android 10 - Users are report Bluetooth MD725 Type 1 is not working on Android 10...]
The only fix is to replace the wifi/bt module with the supported "type 1" GOC-MD-725. See this thread for details (placeholder)
Risk:
Also, there is risk associated in upgrading. The SDCard method is known to result in back-screen, sometimes recoverable booting to recovery from SDcard again. If this method fails, OTG becomes the only recovery option.
Two Rockchip Official methods;
A. SDcard Method
Note: To use these methods, your unit must support booting from SDCard or USB. Not all MTC variants are created the same, so test first.
The following is required for SDcard method
- (1) Full ROM in .IMG format
OR
- (1b) bootloader/recovery only image to flash recovery,
https://drive.google.com/folderview?id=11zpgoOW4eU6G1tjs7ExsZ2aC4RoZ9KDr
AND
- a 'full' OTA of your choice.
- Rockchip SDCard create tool
https://github.com/rockchip-linux/tools
1. Create SDCard using Rockchip SDcard create tool.
2. Insert and boot from SDcard, follow prompts.
3. Wait for install to complete...and can take some time
(1b) Flash boot/recovery image then an OTA zip. Thanks to @ikerg for recovery .IMG files.
2b. Create SDCard using Rockchip SDcard create tool with .img
3b. Insert and boot from SDcard, follow prompts.
4b. After flashing, remove SDCard, boot to recovery then flash an OTA from another SDCard or USB stick.
* Download bootloader/recovery flash image from here; https://drive.google.com/folderview?id=11zpgoOW4eU6G1tjs7ExsZ2aC4RoZ9KDr
B. OTG method - "Never fail, flash like a Boss, impress your friends method"
*May require Jig, or if lucky an USB A-A cable.)
The below method will recover a 'bricked' or non-booting unit.
If wanting to backup your ROM and test other ROMs, this is the method you want.
The following is required:
- ROM in .img format, or partiton extract
- Android Tool and Driver:
https://github.com/rockchip-linux/tools
1. Install Rockchip driver and Android Tool on PC/Laptop.
2. First try connecting your unit USB to USB using cable to PC. Try all headunit USB ports.
3. Try entering recovery. If successful you will hear the new device chime on your PC and the headunit will be connected.
If connecting via USB method does not work, a jig must be made. See the following thread for details: https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
4. Using Android Tool connected via USB - Flash SOM using .img file. If image file does not install, erase flash first after selecting .img file.
C. Downgrading steps here: https://forum.xda-developers.com/t/...ing-official-free-tools.4123933/post-85473141
Hope this thread clarifies the two free and official methods to upgrade your headunit. Enjoy.
29/06/2020 - Update - Users reporting MD725 - Type 1 Bluetooth is not working on Android 10.
28/07/2020 - Update - include bootloader/recovery plus OTA method from IMG files kindly created by the talented @ikerg .
29/06/2020 - Update - Users reporting MD725 - Type 1 Bluetooth is not working on Android 10.
March 2021 - Update - BT module found - HW upgrade to enable Android 10 upgrades. See my module thread.
August 2021 - SD Card Downgrade steps - from A10, A9 using A8 for success.
Note: Best, most successful risk free method - OTG
First note - if coming from Android 6 - early versions of Realtek dual BT/WIFI (type 2) are not supported past Android 6.
[29/06/2020 - Android 10 - Users are report Bluetooth MD725 Type 1 is not working on Android 10...]
Risk:
Also, there is risk associated in upgrading. The SDCard method is known to result in back-screen, sometimes recoverable booting to recovery from SDcard again. If this method fails, OTG becomes the only recovery option.
Two Rockchip Official methods;
A. SDcard Method
Note: To use these methods, your unit must support booting from SDCard or USB. Not all MTC variants are created the same, so test first.
The following is required for SDcard method
- (1) Full ROM in .IMG format
OR
- (1b) bootloader/recovery only image to flash recovery,
https://drive.google.com/folderview?id=11zpgoOW4eU6G1tjs7ExsZ2aC4RoZ9KDr
AND
- a 'full' OTA of your choice.
- Rockchip SDCard create tool
https://github.com/rockchip-linux/tools
1. Create SDCard using Rockchip SDcard create tool.
2. Insert and boot from SDcard, follow prompts.
3. Wait for install to complete...and can take some time
(1b) Flash boot/recovery image then an OTA zip. Thanks to @ikerg for recovery .IMG files.
2b. Create SDCard using Rockchip SDcard create tool with .img
3b. Insert and boot from SDcard, follow prompts.
4b. After flashing, remove SDCard, boot to recovery then flash an OTA from another SDCard or USB stick.
* Download bootloader/recovery flash image from here; https://drive.google.com/folderview?id=11zpgoOW4eU6G1tjs7ExsZ2aC4RoZ9KDr
B. OTG method - "Never fail, flash like a Boss, impress your friends method"
*May require Jig, or if lucky an USB A-A cable.)
The below method will recover a 'bricked' or non-booting unit.
If wanting to backup your ROM and test other ROMs, this is the method you want.
The following is required:
- ROM in .img format, or partiton extract
- Android Tool and Driver:
https://github.com/rockchip-linux/tools
1. Install Rockchip driver and Android Tool on PC/Laptop.
2. First try connecting your unit USB to USB using cable to PC. Try all headunit USB ports.
3. Try entering recovery. If successful you will hear the new device chime on your PC and the headunit will be connected.
If connecting via USB method does not work, a jig must be made. See the following thread for details: https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
4. Using Android Tool connected via USB - Flash SOM using .img file. If image file does not install, erase flash first after selecting .img file.
C. Downgrading steps here: https://forum.xda-developers.com/t/...ing-official-free-tools.4123933/post-85473141
Hope this thread clarifies the two free and official methods to upgrade your headunit. Enjoy.
29/06/2020 - Update - Users reporting MD725 - Type 1 Bluetooth is not working on Android 10.
28/07/2020 - Update - include bootloader/recovery plus OTA method from IMG files kindly created by the talented @ikerg .
29/06/2020 - Update - Users reporting MD725 - Type 1 Bluetooth is not working on Android 10.
March 2021 - Update - BT module found - HW upgrade to enable Android 10 upgrades. See my module thread.
August 2021 - SD Card Downgrade steps - from A10, A9 using A8 for success.
Note: Best, most successful risk free method - OTG
==================================
복구 방법.
0.
1. 아래 링크로 가서
https://drive.google.com/drive/folders/11zpgoOW4eU6G1tjs7ExsZ2aC4RoZ9KDr
1-1. SDDiskTool_v1.62.zip 받아서 설치함.
1-2. 자신에게 맞는 안드로이드 버전을 받음.
PX6_A10_IGV.img ==> PX6 기반 안드로이드 10 버전 부팅 이미지.
2. SDDiskTool 실행
2-1.SD_XX부분 체크
2-2. 파일 찾기 해서 이미지 불러오기
2-2. 파일 찾기 해서 이미지 불러오기
2-3. Demo 버튼 아래 버튼 눌러서 sd카드에 이미지 저장(부팅 sd카드)
2022. 9. 17.
Dasaita MAX10_ha3_rk3399_10.0_ota(20220824+Bluetooth and Mic pack) Zlink 연결 문제 해결
캡처
ha3_rk3399_10.0_ota(20220824+Bluetooth and Mic pack) 설치했다가
아이폰 zlink무선 연결이 계속 해제되어 이전 버전으로 복구하였음.
이전 버전(ha3_rk3399_10.0_ota(20220521+bt_mcu)은 잘 사용하고 있으나
가끔 괭음을 내면서 전체 작동 불능되는 경우를 2번 당했음. zlink와 아이폰이 가끔
한번씩 연결 안됨. 그럼 올인원 헤드유닛 재부팅하면 다시 접속됨.
20220824버전 문제 해결 방법 있어서 다시 한번 업데이트 해보려고 함.
추가
20220824버전 설치
공장 설정에서 변경하였음.
BT WQ_RF210 --> SDIO-AUTO (설정 변경하면 전에 있던 페어링 정보 전부 삭제됨)
knob mode 8 10k/4.7k adc ports --> 4 IO ports
Blutooth network sharing Yes --> No
zlink로 carplay 무선 연결됨 계속 시험해보겠음.
아하 기계 번역, 캡처
Hello, I made the last OTA update of 20220824 and I had problems with Bluetooth, Zlink connected for a few seconds and immediately disconnected, I clarify that in the update of 20220521 everything went well, more however; try several options:
1. Zlink disappeared from Settings/Vehicle/Factory Settings/Others.
2. A new function "Knob Mode" appears, of which I tried all its options and the Bluetooth disconnection problem persisted.
3. In Settings/Vehicle/Factory Settings/Others/, I set Bluetooth Network Sharing to "NO", and "Knob Mode" to 4 IO Ports, and voila.
안녕하세요, 저는 20220824의 마지막 OTA 업데이트를 만들었고 Bluetooth에 문제가 있었습니다. Zlink는 몇 초 동안 연결되었다가 즉시 연결이 끊겼습니다. 20220521 업데이트에서는 모든 것이 잘 진행되었지만 더 많은 문제가 있음을 분명히 합니다. 몇 가지 옵션을 시도하십시오.
1. 설정/차량/공장 설정/기타에서 Zlink가 사라졌습니다.
2. 새로운 기능 "노브 모드"가 나타납니다. 모든 옵션을 시도했지만 Bluetooth 연결 끊김 문제가 지속되었습니다.
3. 설정/차량/공장 설정/기타/에서 Bluetooth 네트워크 공유를 "NO"로 설정하고 "노브 모드"를 4개의 IO 포트로 설정하고 짜잔.
@Marek. Mok Dzięki, przetestuj ustawienia RF_210 do SDIAUTO i działa bardzo dobrze, rozwiązało to dla mnie problem z niestabilnym dźwiękiem. Dzięki, przetestuj ustawienia RF_210 do SDIAUTO i działa bardzo dobrze, rozwiązało to dla mnie problem z niestabilnym dźwiękiem. Dlaczego wybrano tę konfigurację? Dziękujemy za Twój wkład.
@마렉. Mok 감사합니다. RF_210 설정을 SDIAUTO로 테스트하면 매우 잘 작동합니다. 불안정한 오디오 문제가 해결되었습니다. 감사합니다. RF_210 설정을 SDIAUTO로 테스트하면 매우 잘 작동합니다. 불안정한 오디오 문제가 해결되었습니다. 이 구성을 선택한 이유는 무엇입니까? 입력해 주셔서 감사합니다.
2022. 7. 9.
쉴드 tv 2세대(2017년) 제품 8.2.3으로 다운그레이드 하기
쉴드 tv 2세대(2017년) 제품
8.2.3으로 다운그레이드 하기
준비물: usb A-A 케이블 필요함. USB 연결 키보드 필요.
난 usb A - C 케이블에 C암놈-A숫놈 아답터 연결해서 성공함.
1차 시도에서 12번 까지 하고 다음날 자동 업데이트 되서
다음날 다시 다운그레이드 하고 IMPORTANT까지 했음. 다시 업데이트가 안되길...
리부팅 시 부팅 파트가 수정되었다고 경고가 뜸.
https://www.nvidia.com/en-us/geforce/forums/shield-tv/9/481714/request-for-a-way-to-downgrade-to-nvidia-8/
You can actually perform the downgrade to v8.2.3 right now. I just did it over the weekend and was able to start enjoying my Shield again after getting rid of this god awful v9 update (Android 11). Since I could not find any comprehensive instructions anywhere, here are all the steps to help all of you get downgraded to v8 (with some tips at the end to disable auto system updates): Video TUTORIAL:
DETAILED PROCEDURE: 1) Go here and download correct the "NVIDIA SHIELD ANDROID TV Recovery OS Image" for your SHIELD Version. Note that you need to sign up as a developer to do this. You will get prompted as you click "download" if you are not registered as a developer. Just follow the instructions, it is quite easy to get the needed rights to download this recovery image. Take note of the link to the INSTRUCTIONS along with the download links. https://developer.nvidia.com/gameworksdownload 2) Download the Shield USB Drivers for windows. The recovery image description has a link to it, download the latest version. Then extract the contents to a folder. https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20Family%20Windows%20USB 3) Download your ADB and FASTBOOT utilities. Get it from the xda-developers website, it includes the instructions how to set it up. Look for the section "How to setup ADB on Microsoft Windows" https://www.xda-developers.com/install-adb-windows-macos-linux/ 4) Enable Developer mode in your NVIDIA SHIELD and activate USB Debugging. Watch this video
but don't switch on Network Debugging!! 5) Connect your SHIELD to the TV via HDMI. Then use a USB Type A to Type A to connect your SHIELD to your PC by using the USB Port on your shield that's farthest from the HDMI port. Connect a USB keyboard OR the NVIDIA game controller to the other USB port. https://www.amazon.com/Rankie-Cable-Type-1-Pack-Feet/dp/B01KRO8D20 6) Once Shield is connected to your PC, go to Windows' "Device Manager" and look for an unknown USB Device (likely your shield). Update the driver and have it point to the folder where you extracted the USB drivers from #2 above. Your PC should start recognizing the SHIELD after that. Dont skip this step or the flashing might fail! Instructions here: https://developer.nvidia.com/sites/default/files/akamai/mobile/docs/How-To-Install-Android-USB-Driver.txt 7) Extract your NVIDIA SHIELD recovery image (from #1) to the same folder that has all your ADB commands (adb, fastboot, etc.) 8) Launch Windows' CMD (search and run Command Prompt). Using CMD, go to your ADB folder (where you extracted your ADB files and recovery image). To check if your NVIDIA SHIELD is connected, use the command "adb devices". Your Shield should be displayed if all is working well. Then use the command "adb reboot bootloader", and your Shield should reboot into FASTBOOT mode. Use the controller (X, Y button) to UNLOCK the BOOTLOADER. Select your choice using A button. If you run into errors after running the adb commands in cmd, try using WINDOWS POWERSHELL instead. Thanks to drod70 for sharing this tip! 9) Once your BOOTLOADER is UNLOCKED, use "adb devices" again to check if your SHIELD is still connected. Then type "adb reboot bootloader" to go back to FASTBOOT Mode. At this point, run the commands stated in the instructions included with the recovery image. MAKE SURE that you use the correct commands based on your SHIELD version (eg. ...marshmallow or newer) 10) Execute the commands one after another, don't let the SHIELD time out by leaving huge gaps in between commands (e.g. like going out to get some groceries in between!). 11) Once all commands are successfully completed, you must launch the NVIDIA Shield to FASTBOOT mode again and LOCK the boot loader. (using the controller, press "A, B" while rebooting). If you miss this step, your SHIELD will get stuck on Boot Loop. 12) After locking the bootloader, reboot and you can enjoy a working SHIELD again!
IMPORTANT: Do this or else you will soon find yourself back in v9 again! DISABLE AUTO SYSTEM UPDATES (Device Preferences > About > System Upgrade) !! But somehow NVIDIA might still find a way to force the download of the update in the background and will install upon next reboot. In case this happens, go to APPS > Show System Apps > Look for "System Upgrade". "Clear All Data" and "Force Stop". This will delete the downloaded update file. Then turn off Notifications which will hopefully stop the Shield Experience Notifications. There's a thread in XDA that talks about disabling system updates completely via adb shell. But do it at your own risk...
피드 구독하기:
글 (Atom)