G973F EUB Mode broken

[KrzychuG]

After switching to EUB mode, phone can boot correctly to EUB, is initially detected, but then Chimera is stuck at 89% and fail to connect to the phone eventually.

Chimera Mobile Phone Utility version: 42.32.1259 @ 2025-03-04
Printing phone history

Auto Detect
04.03.2025
20:07

Auto Detect
04.03.2025
20:05

Auto Detect
04.03.2025
20:03

Identify
Connecting to the phone...
Gathering information...
Preparing phone...
Downloading required files...
Bootloader is already downloaded
Processing files...
Communicating with the phone...
Rebooting
This may take a while.
Be patient! Do NOT disconnect the phone!
An error occurred during the procedure!
Finished at local time: [03.04.25 21:15:29]
WorkID: 348881019

I can see the Chimera "bootloader", with Chimera logo on the phone screen.


I tried few times, same problem each time. I also reinstalled the UsbDk driver, no change. Differnt cable, no change.

[Chimera Tool]

Dear User,


As we can see you have managed to run a Repair Boot procedure on the phone successfully.

Could you confirm that the phone in out of EUB mode?


Regards,
ChimeraTeam

Originally Posted by KrzychuG

After switching to EUB mode, phone can boot correctly to EUB, is initially detected, but then Chimera is stuck at 89% and fail to connect to the phone eventually.

Chimera Mobile Phone Utility version: 42.32.1259 @ 2025-03-04
Printing phone history

Auto Detect
04.03.2025
20:07

Auto Detect
04.03.2025
20:05

Auto Detect
04.03.2025
20:03

Identify
Connecting to the phone...
Gathering information...
Preparing phone...
Downloading required files...
Bootloader is already downloaded
Processing files...
Communicating with the phone...
Rebooting
This may take a while.
Be patient! Do NOT disconnect the phone!
An error occurred during the procedure!
Finished at local time: [03.04.25 21:15:29]
WorkID: 348881019

I can see the Chimera "bootloader", with Chimera logo on the phone screen.


I tried few times, same problem each time. I also reinstalled the UsbDk driver, no change. Differnt cable, no change.

[KrzychuG]

Originally Posted by Chimera Tool

Dear User,


As we can see you have managed to run a Repair Boot procedure on the phone successfully.

Could you confirm that the phone in out of EUB mode?

That is correct, i have the phone working again, but i need to service it in EUB mode, and that's the problem.


I can get into EUB, it loads the Chimera "bootloader", but doesn't offer any features, like backup/restore partitions, frp and so on, and instead is stuck at 89% for a longer while, and then fails.

[Chimera Tool]

Dear User,


Try to press the power button during the autodetect procedure.


Regards,
ChimeraTeam

Originally Posted by KrzychuG

That is correct, i have the phone working again, but i need to service it in EUB mode, and that's the problem.


I can get into EUB, it loads the Chimera "bootloader", but doesn't offer any features, like backup/restore partitions, frp and so on, and instead is stuck at 89% for a longer while, and then fails.

[KrzychuG]

I did, otherwise it would not load your loader in this model. Again, it is detected correctly, but then, it gets to the Chimera logo on screen, but then looks like it timeouts.

[Chimera Tool]

Dear User,


And what if you switch to the Device Wizard tab and want to do the Autodetect procedure from there?


Regards,
ChimeraTeam

Originally Posted by KrzychuG

I did, otherwise it would not load your loader in this model. Again, it is detected correctly, but then, it gets to the Chimera logo on screen, but then looks like it timeouts.

[KrzychuG]

That's how i repaired it, created virtual device, selected repair boot and pointed to the BL file.

Now, i'm trying using testpoint, and same problem. Currently, i choose the Device Wizard, selected G973F and created virtual device and click on auto-detect there, then connect phone via testpoint, it still behaves the same.

It hangs for a longer while on "Be patient, do not disconnect the phone", that's before the "make sure battery is connected" message, and then it fails. I've done few S10 before, and this step never took that long. No change also i choose a different model in device wizard, for example G975F instead.

If i then "close" the virtual device, i see an unknown exynos detected by Chimera, with no no features available.

This seems to behave the same as here https://forum.gsmhosting.com/vbb/f89...025-a-3369628/

[KrzychuG]

Yesterday, i also updated firmware to the latest one available, G973FXXSGHWC1, but still the same problem.

[Chimera Tool]

Dear User,

We have checked the logs and other users are working on this phone successfully.

In your device manager, it is also visible that your USBDK driver is not installed properly. Because of these reasons we suspect that this is a local problem on your end.

I would suggest reinstalling the USBDK driver and restarting your computer so you do not see the question mark in your device manager.


Regards,
ChimeraTeam

Originally Posted by KrzychuG

Yesterday, i also updated firmware to the latest one available, G973FXXSGHWC1, but still the same problem.

[KrzychuG]

Originally Posted by Chimera Tool

In your device manager, it is also visible that your USBDK driver is not installed properly. Because of these reasons we suspect that this is a local problem on your end.

What do you mean by thatt? I already tried reinstalling UsbDk driver, as i mentioned in the first message. I'll check it again later today since you pushed a new update as well.

[KrzychuG]

Originally Posted by Chimera Tool

We have checked the logs and other users are working on this phone successfully.

In your device manager, it is also visible that your USBDK driver is not installed properly. Because of these reasons we suspect that this is a local problem on your end.

I would suggest reinstalling the USBDK driver and restarting your computer so you do not see the question mark in your device manager.

No luck after the Chimera update, still same exact issue. I also fully uninstalled, rebooted, and installed UsbDk driver again - no change. Still behaves exactly the same as before.


Maybe there's something wrong with this one unit, as someone reported same exact problem here: https://forum.gsmhosting.com/vbb/f89...025-a-3369628/ , and for this user, also 2 devices out of 20 that he tried recently did not work.