HELP ! SAMSUNG A22 5G A226B Hard-Bricked after Downgrade From U5 to U4 - Please need full Dump A226B U5 Android 12 readed from working phone

[Guberkov]

I write Scater Firmware , from read info all partitions and info are ok, phone flashes sucsessfuly , but not powered on,no Odin Download Mode - Only Serial MTK V-Com Port available.

All Operations work only im MTK Universal Tab.

Pleace Help.

 

[Guberkov]

Can somebody help with this file from here, thank you :

A226B U5 OS12 A226BXXU5BVJ3 Scatter Firmware Dead Boot Repair.zip

from here :

404 Error - Page Not Found! | Easy Firmware

easy-firmware.com

or here:

A226B U5 OS12 Scatter Firmware [Dead Boot Repair] (A226BXXU5BVH2).zip | Halab Tech Support

and atach this file to Google Drive or mediafire.

 

[Dinancel]

https://t.me/pump_upp - best crypto pumps on telegram
Make 1000% and more within 1 day, join channel @pump_upp !

 

[Guberkov]

FLASH Initializing usb... OK
Waiting for device... COM8 [BOOTROM:0E8D:0003]
Bypassing authentication... OK
Analyzing... preloader_s96801aa2.bin [MT6833:12:1120] [Cust]
Reading hardware info... OK
Hardware : MT6833 [Dimensity 700|810] 0989 8A00 CA00 0000
Security Config : SCB SLA DAA
MEID : A6DF3A9A33BF1224FDC5CCFB2F8A3930
Sending Download-Agent... OK
Syncing with target... OK
Booting device... OK
Syncing with DA... OK
Storage : EMMC - CID : 44000115.42443656.7CF60042.692924F2
Vendor : Samsung - Name : DV6DBB - Serial : 619871478 - Rev : 0
Boot1 : 4 MiB - Boot2 : 4 MiB - RPMB : 16 MiB - User Area : 116,48 GiB
Tips : GPT not initialized! Using scatter as partition map!
Writing preloader_s96801aa2.bin [350,36 KiB] -> preloader [4 MiB]... OK
Writing preloader_s96801aa2.bin [350,36 KiB] -> preloader_backup [4 MiB]... OK
Writing tzar.img [2,35 MiB] -> tzar [4 MiB]... OK
Writing dtbo.img [108,06 KiB] -> dtbo [8 MiB]... OK
Writing vbmeta.img [7,94 KiB] -> vbmeta [64 KiB]... OK
Writing md1img.img [62,98 MiB] -> md1img [200 MiB]... OK
Writing param.img [120,5 KiB] -> param [4 MiB]... OK
Writing up_param.img [2,81 MiB] -> up_param [4 MiB]... OK
Writing boot.img [32 MiB] -> boot [32 MiB]... OK
Writing recovery.img [40 MiB] -> recovery [40 MiB]... OK
Writing vbmeta_system.img [3,31 KiB] -> vbmeta_system [64 KiB]... OK
Writing efuse.img [1 KiB] -> efuse [512 KiB]... OK
Writing super.img [6,23 GiB] -> super [2,74 GiB]... FAIL
Image : File too large! Status code : 0xC0040004
Writing prism.img [461,2 MiB] -> prism [704 MiB]... OK
Writing optics.img [1,4 MiB] -> optics [24 MiB]... OK
Writing cache.img [64,14 KiB] -> cache [200 MiB]... OK
Writing omr.img [52,11 KiB] -> omr [50 MiB]... OK
Writing userdata.img [1,59 GiB] -> userdata [0 byte]... OK
UNLOCKTOOL 2023.01.13.1
Elapsed time : 1 minute 15 seconds

 

[Guberkov]

But, whithout result, phone dead.

 

[Guberkov]

Cannot write :

Writing super.img [6,23 GiB] -> super [2,74 GiB]... FAIL
Image : File too large! Status code : 0xC0040004

Phone is dead , pls help me.

 

[Guberkov]

Need FULL DUMP ( RPMB Backup 4 Files - BOOT1 , BOOT2 , USERAREA and MAP )

SAMSUNG A226b A22 5G U5 Android 12 Dump

from working phone SAMSUNG A226b A22 5G with Unlock Tool .

Please help me .

 

[Guberkov]

Sloved , boot repair Done !

 

[xjj]

Sloved , boot repair Done !

But how please help me!

 

[xjj]

Writing super.img [6,23 GiB] -> super [2,74 GiB]... FAIL
after flash i see that in log too
i have just black screen, USB Vcom com
This is phone of my mother three day i reflash dump and other... Black screen... Just black screen