[Please help] Bricked Qualcomm Android Car head unit
[Please help] Bricked Qualcomm Android Car head unit
(20-05-2024, 11:36 PM)JavierP Hi, community, a few days ago when I flashed a splash.img to change the startup animation of my screen, it stayed in bootloop and did not finish booting the loading part of Android 9 (Pie). This device mounts a 64bit MSM8953 (I think SDM450) with A/B partitions and EMMC memory. I have asked the seller to send me the complete ROM to flash it with fastboot or EDL, but he can only send me updates (Update.zip) and he cannot provide me with the complete ROM (I don't know the reason, I suppose company policy)
On the other hand, the motherboard mounts a Quectel SC600Y-EM of which I have obtained all the complete software, but of course if I flash it it will be worse, I suppose, since the one with the screen will be modified to work with the car (audi, mmi , MCU). I have been able to read information via [ Login to download] , to see if anyone can shed some light on where the problem may be coming from, I would be willing to pay if we look for a solution to the blockage.
Thanks and sorry for the long text.
(31-05-2024, 09:08 AM)maxpayne(20-05-2024, 11:36 PM)JavierP Hi, community, a few days ago when I flashed a splash.img to change the startup animation of my screen, it stayed in bootloop and did not finish booting the loading part of Android 9 (Pie). This device mounts a 64bit MSM8953 (I think SDM450) with A/B partitions and EMMC memory. I have asked the seller to send me the complete ROM to flash it with fastboot or EDL, but he can only send me updates (Update.zip) and he cannot provide me with the complete ROM (I don't know the reason, I suppose company policy)
On the other hand, the motherboard mounts a Quectel SC600Y-EM of which I have obtained all the complete software, but of course if I flash it it will be worse, I suppose, since the one with the screen will be modified to work with the car (audi, mmi , MCU). I have been able to read information via [ Login to download] , to see if anyone can shed some light on where the problem may be coming from, I would be willing to pay if we look for a solution to the blockage.
Thanks and sorry for the long text.
I'm guessing you had used fastboot to flash the splash.img. Can you enter EDL (9008) on the tablet?
(14-06-2024, 08:22 AM)maxpayne [ Login to download]
(14-06-2024, 08:41 PM)JavierP I have already tried many times but at no time does it detect the device through "adb" only EDL and Fastboot. Normally on Android screens this "USB debugging" option is deactivated because within the configuration, you have the option to activate "USB slave" or "USB device", changing this option if it would be possible but not like this.
(17-06-2024, 09:28 AM)maxpayne(14-06-2024, 08:41 PM)JavierP I have already tried many times but at no time does it detect the device through "adb" only EDL and Fastboot. Normally on Android screens this "USB debugging" option is deactivated because within the configuration, you have the option to activate "USB slave" or "USB device", changing this option if it would be possible but not like this.
Since you have a vbmeta partition, I want to assume that the splash.img was compatible and you forgot to disable verified boot.
Try flashing blank vbmeta from https://www.hovatek.com/forum/thread-32719.html to the vbmeta partition of the active slot.
Just to be clear, splash.img was all you flashed right?
(17-06-2024, 02:27 PM)JavierPI have tried but I still cannot boot, I have tried with the white vbmeta, but it does not work either.(17-06-2024, 09:28 AM)maxpayne(14-06-2024, 08:41 PM)JavierP I have already tried many times but at no time does it detect the device through "adb" only EDL and Fastboot. Normally on Android screens this "USB debugging" option is deactivated because within the configuration, you have the option to activate "USB slave" or "USB device", changing this option if it would be possible but not like this.
Since you have a vbmeta partition, I want to assume that the splash.img was compatible and you forgot to disable verified boot.
Try flashing blank vbmeta from https://www.hovatek.com/forum/thread-32719.html to the vbmeta partition of the active slot.
Just to be clear, splash.img was all you flashed right?
Yes indeed, as I told you before, modify the splash.img and the "factoryconfig.xml" file. Those are the only 2 files that I modified and I already entered bootloop.
I'll try the blank vbmeta and let you know. Thank you
(20-06-2024, 10:02 PM)JavierP I have tried but I still cannot boot, I have tried with the white vbmeta, but it does not work either.
(28-06-2024, 01:13 PM)maxpayne(20-06-2024, 10:02 PM)JavierP I have tried but I still cannot boot, I have tried with the white vbmeta, but it does not work either.
Only two options I see is to get a firmware that contains the splash image (the update.zip might...or not) or another device of the same mode to backup