Hovatek Forum MOBILE Android [Please help] Bricked Qualcomm Android Car head unit
Try our Online TWRP Builder..its free!
Can't login? Please, reset your password.


[Please help] Bricked Qualcomm Android Car head unit

[Please help] Bricked Qualcomm Android Car head unit

JavierP
JavierP
JavierP
Enthusiastic Member
9
20-05-2024, 11:36 PM
#1



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 uart ttl, 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.






maxpayne
maxpayne
maxpayne
Intern
3,064
31-05-2024, 09:08 AM
#2
(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 uart ttl, 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?
This post was last modified: 31-05-2024, 09:09 AM by maxpayne.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
JavierP
JavierP
JavierP
Enthusiastic Member
9
11-06-2024, 09:38 PM
#3
(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 uart ttl, 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?

Hi, yes, but I don't have the original "splash.img". I can boot it both in fastboot mode and in EDL 9008 mode. I'll give you the link to the folder where you can see all the backup files of what the device currently has written, to see if you can find which "IMG" file may be corrupted.  Link
maxpayne
maxpayne
maxpayne
Intern
3,064
14-06-2024, 08:22 AM
#4
(11-06-2024, 09:38 PM)JavierP Hi, yes, but I don't have the original "splash.img". I can boot it both in fastboot mode and in EDL 9008 mode. I'll give you the link to the folder where you can see all the backup files of what the device currently has written, to see if you can find which "IMG" file may be corrupted.  Link

Open command prompt and run adb devices
see if adb detects the device at any point in the loop

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
JavierP
JavierP
JavierP
Enthusiastic Member
9
14-06-2024, 08:41 PM
#5



(14-06-2024, 08:22 AM)maxpayne
(11-06-2024, 09:38 PM)JavierP Hi, yes, but I don't have the original "splash.img". I can boot it both in fastboot mode and in EDL 9008 mode. I'll give you the link to the folder where you can see all the backup files of what the device currently has written, to see if you can find which "IMG" file may be corrupted.  Link

Open command prompt and run adb devices
see if adb detects the device at any point in the loop
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.
maxpayne
maxpayne
maxpayne
Intern
3,064
17-06-2024, 09:28 AM
#6
(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?
This post was last modified: 17-06-2024, 09:29 AM by maxpayne.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
JavierP
JavierP
JavierP
Enthusiastic Member
9
17-06-2024, 02:27 PM
#7
(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
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram