Bricked Unisoc T610 (Micromax IN 2B - E7544) while flashing vbmeta

[Please help] Bricked Unisoc T610 (Micromax IN 2B - E7544) while flashing vbmeta

howitzer_fire
Enthusiastic Member

10

16-11-2024, 03:28 PM

#1

Good day everyone!

For the past couple of days, I've been trying to create a custom signed vbmeta for my device by following the tutorials posted here on Hovatek. The plan was to sign magisk and twrp images using the private key used to sign vbmeta-sign.img. I had already unlocked the bootloader and things were going pretty smoothly, well, that was until I flashed the newly generated vbmeta-sign.img. At first, the flashing didn't work when I tried from the bootloader (fastboot). I then booted back to 'fastbootd' from where, I was able to flash the image. I then flashed the custom signed magisk_patched_boot.img. Upon restarting, the phone enters an infinite bootloop. It vibrates and turns on for 1-2 seconds after which it shuts down. The cycle goes on endlessly. Accessing the stock recovery/bootloader seems impossible. Powering off is not possible as well. So, I then fired up SPD Research tool and loaded up my phone's firmware (which I had previously used to flash without any problems). Initially, I tried flashing just the stock vbmeta, boot and userdata (all extracted from the pac file) partitions. As it didn't work, I tried a full flash. But that didn't solve the issue either. Left frustrated, I tried flashing using SPD Flash tool and SPD upgrade tool (got error in step _BKF_NV_LTE - GSM cali in phone is not calibrated). But the result turned out to be the same. All my flashing attempts showed as 'passed' except for 2 situations:

1. When Upgrade tool was used.
2. SPD research tool flashing also failed with my custom signed vbmeta as well.

I am kind of stumped at the moment and don't know if I have any other options left. My issue seemed identical to this one (somewhat), except in my case, I didn't sideload any GSI and the phone is still visible via SPD tools.
https://www.hovatek.com/forum/thread-47228.html

Could someone help me find a fix to this issue? Any help is greatly appreciated. Thank you.

howitzer_fire
Enthusiastic Member

10

17-11-2024, 10:33 PM

#2

Oh, I forgot to mention that I ticked the 'Erase all flash' under flash operations while flashing the pac file in my previous post. Please let me know if this could be the cause of the problem.

justshez
Intern

2,363

19-11-2024, 06:47 AM

#3

(17-11-2024, 10:33 PM)howitzer_fire Oh, I forgot to mention that I ticked the 'Erase all flash' under flash operations while flashing the pac file in my previous post. Please let me know if this could be the cause of the problem.

Is there no way you can quickly reboot to fastboot>fastbootd then flash stock vbmeta and boot?

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.

howitzer_fire
Enthusiastic Member

10

19-11-2024, 09:33 AM

#4

(19-11-2024, 06:47 AM)justshez Is there no way you can quickly reboot to fastboot>fastbootd then flash stock vbmeta and boot?

None at the moment. When holding down Vol - and Power button, the phone does not enter recovery mode. Instead, it stops bootlooping for a few seconds during which, it gets detected as SPD U2S COM Port. So there's no way to use fastboot. My suspicion is that because of me previously selecting "Erase all flash", some of the information required to initialize boot went missing and the pac file(s) that I've been trying to flash with does not contain that information within them.

howitzer_fire
Enthusiastic Member

10

19-11-2024, 10:28 AM

#5

I am also getting this message everytime I press OK button in the Download Settings screen.

"There are something wrong: The number of VOLs and CLKs is not equal to the total."

Is this normal or does this indicate an issue with my setup? I have attached a screenshot showing the error. Please have a look.

SS.png
Size: 129.15 KB / Downloads: 8

This post was last modified: 19-11-2024, 10:32 AM by howitzer_fire.

howitzer_fire
Enthusiastic Member

10

20-11-2024, 08:45 AM

#6

Okay, so if I leave sploader (u-boot-spl-16k-sign.img) unticked in the SPD Reserch Download tool, the above message does not show up. But, as usual, the flashing shows 'passed'. But as soon as I switch on the phone, the device enters bootloop. Does that shine light on what the problem could be? I am attaching the research tool logs here. Kindly check.

FAIL(262)_COM4-2024_11_19-23_30_28_625.zip
Size: 82.42 KB / Downloads: 3

PASS_SN44466906535970_COM4-2024_11_20-01_25_56_208.zip
Size: 37.21 KB / Downloads: 0

PASS_SN62547866483992_COM4-2024_11_20-00_40_53_257.zip
Size: 37.38 KB / Downloads: 0

PASS_SN93775086093709_COM4-2024_11_20-02_24_47_907.zip
Size: 27.17 KB / Downloads: 0

justshez
Intern

2,363

21-11-2024, 06:35 AM

#7

(20-11-2024, 08:45 AM)howitzer_fire Okay, so if I leave sploader (u-boot-spl-16k-sign.img) unticked in the SPD Reserch Download tool, the above message does not show up. But, as usual, the flashing shows 'passed'. But as soon as I switch on the phone, the device enters bootloop. Does that shine light on what the problem could be? I am attaching the research tool logs here. Kindly check.

Try using a lower version of research download to flash all components

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.

howitzer_fire
Enthusiastic Member

10

21-11-2024, 10:51 AM

#8

(21-11-2024, 06:35 AM)justshez Try using a lower version of research download to flash all components

Already tried multiple versions (~5) of the Research, Upgrade and Flash tools. The error message did not show up in some of the versions. But neverthless, the outcome remains the same after flashing the firmware (Bootloop) regardless of the version of the tool used. In all the uboot logs (UBootDump.txt), there's this error message:

[00005944] is_wr_rpmb_key rpmb key has been written
[00005950] The Emmc rpmb partition was used
[00005969] Error!dl_cmd_get_timestamp(): read timestamp magic(0) incorrect.
[00005975] dl_cmd_handler:enter

In Trace.log file, the following messages are seen:

[2024-11-20 20:13:03:219][BMPlatform2 ][3 - Information] [ ENTER ] -> ExecNandInit( FileSize: 0xD1944, FileOffset: 0x0 )
[2024-11-20 20:13:03:219][BMPlatform2 ][3 - Information] [ LEAVE ] <- ExecNandInit( )
[2024-11-20 20:13:04:587][BMPlatform3 ][1 - Error ] ExcuteDownloadedFile( CMD: 0x4 ( BSL_CMD_EXEC_DATA ), Timeout: 60000 ): Fail. [150:[DL1150]Incompatible partition]
[2024-11-20 20:13:04:587][Authorize ][3 - Information] [ ENTER ] -> EnableAuth( )
[2024-11-20 20:13:04:587][Authorize ][3 - Information] [ LEAVE ] <- EnableAuth( )

Despite this, the flashing continues and displays 'passed'. What do these errors signify?

maxpayne
Intern

4,059

21-11-2024, 04:05 PM

#9

(21-11-2024, 10:51 AM)howitzer_fire Despite this, the flashing continues and displays 'passed'. What do these errors signify?

Let's go through some things again.
You said you'd flashed the firmware before now. Which tool and version did you use? Was it a full flash or you only flashed certain partitions.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.

howitzer_fire
Enthusiastic Member

10

26-11-2024, 12:39 PM

#10

Sorry for the late response. I have used SPD Research download tool (v27.24.2301 & v25.20.3901) to flash the firmware successfully before. The first flash was a partial flash (boot.img & vbmeta-sign.img). The following ones were full flashes without selecting 'erase all flash' option. I even managed to upgrade my firmware version from v22 to v25 (SW_V25_HW_V2.0_20230428) via full flash. I have also found success with SPD Factory tool (R27.23.1902). The SPD driver version used during the whole process was R4.20.4201.

View a Printable Version

Users browsing this thread:
1 Guest(s)

Find us

Call us

Mail us

Useful Links

Actions