Nokia G20 Only fastboot mode after flashing!!

[toptech]

I just flashed a nokia G20 that was hanging on android one logo and now just boots to fastboot mode.

Here is the log

Using library Brom_DLL_v7.1813.3
Engine version 1.0.0.5470
Searching phone in normal mode;
[connect the phone powered off with volume down and up pressed to the usb cable]
Phone detected (MTK USB Port (COM129)) (Driver version: 1.1032.0.0)
Preparing to start flash mode;
Preparing to open COM129
Device hw code: 0766
Device hw sub code: 8A00
Device hw version: CA00
Device sw version: 0000
Device secure boot: True
Device serial link authorization: True
Device download agent authorization: True
Disabling watchdog timer;
Done;
Exploited;
Sec code uploaded;
Executed;
Vodka time;
Ready to party;
Connecting;
Downloading DA;
Initializing;
Rid: 311f2a77b8025e97ba06a6d92625896c
Requesting baudrate change;
Done;
USB SPEED: USB_HIGH_SPEED
DEVICE INFO:
BB CHIP: MT6765 [CA00, 00, 6765, 00]
BB ID: RjI1NENGNzg1QzcxMzk2MUNFOTY1OTA5RTVENTQ4MTM=
HW_STORAGE_EMMC: 0x53030188 0x3231444C 0x8F585538 0xDF48B01A [SIZE=0x1CCFC00000]
IMEI1 [OTP 0000]: 000000-00-000000-0
IMEI2 [OTP 0000]: 000000-00-000000-0
PROVIDER: N/A
USRDATA INFO: 0x1C0800000 SIZE: 0x1B0ACF8000


SPECIAL NOTE: If you are using windows 10 x64 be sure that the installed mtk driver version is 3.0.1504.0 . Any different drivers will create random read bugs on newer chipset phones.
As usual the correct drivers come inside OTSMart archive inside the "usb_driver" folder
Loading the file ...
Cfg done ...
Formatting file system now...
Done;
Formatting FRP partition now...
Done;
Formatting NVCFG partition now...
Done;
Formatting NVDATA partition now...
Done;
Formatting METADATA partition now...
Done;
Formatting SECCFG partition now...
Done;
Downloading bootloader...
Done;
Downloading images...
Done;
Success;

Time needed - 00:13:49

Log file saved to: LOG_21_01_2022_14_20_15.txt


What could have possibly gone wrong.Please help me as it is urgent.

Thank you

[.:hack3r2k:.]

Well since the phone was stuck on logo the problem could be other . Try android 11 firmware as well


Br