[REQUEST] Unlock Bootloader,Install TWRP ,Root Vivo Y19s - ums9230_6h10 , unisoc-t612
[REQUEST] Unlock Bootloader,Install TWRP ,Root Vivo Y19s - ums9230_6h10 , unisoc-t612
15-07-2026, 03:25 PM
Hi everyone,
I've noticed that the stock ROM for Vivo Y19s is now available, and I'm looking for help to unlock the bootloader, install TWRP, and root this device. I'm reaching out here for assistance.
Available Resources I've Found:
Kernel Source Tree: Vivo has released the open-source kernel tree. If you go to the Vivo Open Source Portal ( https://opensource.vivo.com/Project ) and search for android_14.0_kernel_umS9230 , the kernel tree file is available there.
Firmware: The extracted PAC firmware file is also available for download on FirmwareFile (Version: PD2420UF). ( https://firmwarefile.com/vivo-y19s-pd2420uf ) .
My Experience & Where I'm Stuck (No Hardware Dongles):
Since I don't have a hardware box or dongle (like CM2 or Hydra), I am looking for a reliable, free, software-based method to unlock the bootloader and root the phone.
Here is what happens when I try to interface with the PC:
- I installed the standard Vivo Unisoc/Spreadtrum drivers on a Windows PC.
- I powered off the phone, held down both Volume Up + Volume Down keys simultaneously, and connected the USB cable.
- Windows makes the connection sound, and the device briefly registers in Device Manager with name = SPRD U2S Diag | (likely in Flash/EDL mode). However, after exactly 1 second, it immediately disconnects, the disconnect sound plays again, and the phone just boots normally into the OS. It refuses to stay in the flashing state. SO thats why i can not tell , the firmware is actually working or not in my device , although version matches partially
- I also tried holding only Volume Up and connecting to the PC. The phone boots into Fastboot mode, and the COM port is not recognized like =SPRD U2S Diag. (Device Manager only shows "Android Bootloader & ADB Interface").
- I then tried holding only Volume Down and connecting to the PC. The phone boots into the default Recovery mode, and nothing is recognized in Device Manager at all.
My Question:
Does anyone know a bypass method or a specific tool/script that can catch the connection before it drops, or is there a specific trick to keeping this Unisoc chipset in boot ROM mode without a hardware dongle?
Any help or guidance on how we can use the kernel source/PAC file to achieve root would be highly appreciated!
Reference Links & Attachments:
To help anyone looking into the details, I have provided the following resources:
AIDA64 Full Hardware Report (.txt): full AIDA64 apk report (Shows the exact detected hardware architecture, SoC revisions, kernel details, and system specs of my specific unit).
https://drive.google.com/file/d/1ZefSTgh...sp=sharing
GSMArena Link: Vivo Y19s Full Specifications for official reference. = https://www.gsmarena.com/vivo_y19s-13436...55fbjkwfuy
Quick Specs (from AIDA64 apk):
Device: Vivo Y19s 4G (Model: V2419)
Chipset: Unisoc Tiger T612 (UMS9230)
CPU: 8-core (6x Cortex-A55 + 2x Cortex-A75 @ 1.82GHz)
GPU: ARM Mali-G57
RAM: 4 GB LPDDR4X (Total Memory: ~3.7 GB)
Storage: 128 GB Internal
Display: 720 × 1608, 6.68", 90Hz IPS LCD
Android: 14 (API 34)
Kernel: 5.15.123-android13-8-00046-g5c06b486c75d-ab11707803
Build ID: PD2420F_EX_A_14.0.13.15.W20.V000L1
Thank you in advance for any help or pointers!
01-08-2026, 10:58 AM
(15-07-2026, 03:25 PM)spryshanto ..
Device: Vivo Y19s 4G (Model: V2419)
Chipset: Unisoc Tiger T612 (UMS9230)
CPU: 8-core (6x Cortex-A55 + 2x Cortex-A75 @ 1.82GHz)
GPU: ARM Mali-G57
RAM: 4 GB LPDDR4X (Total Memory: ~3.7 GB)
Storage: 128 GB Internal
Display: 720 × 1608, 6.68", 90Hz IPS LCD
Android: 14 (API 34)
Kernel: 5.15.123-android13-8-00046-g5c06b486c75d-ab11707803
Build ID: PD2420F_EX_A_14.0.13.15.W20.V000L1
Thank you in advance for any help or pointers!
Extract the PAC file using https://www.hovatek.com/forum/thread-6236.html, then zip all except super and provide a link to the zip
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
01-08-2026, 11:42 AM
super_gsi64.img (3.12 GB),
super.img (4.82 GB)
.. so i exclude those 2 files in zip file..
Here is the link to the zip = https://drive.google.com/file/d/1p_bApqj...sp=sharing
contains this files =
blackbox.img (2.15 MB)
boot-5.15.img (64.00 MB)
boot-gki.img (96.00 MB)
boot-local.img (64.00 MB)
boot.img (96.00 MB)
boot_ramdisk.img (0 B)
cache.img (2.15 MB)
ddr_scan-sign.bin (53.66 KB)
ddr_scan.bin (51.98 KB)
dtb.img (131.57 KB)
dtbo.img (8.00 MB)
dyn.img (53.28 MB)
efuse.bin (2.29 KB)
factory.img (128.00 MB)
fdl1-sign.bin (57.96 KB)
fdl1.bin (56.27 KB)
FileList.ini (2.29 KB)
gsi_arm64-user-system.img (1.85 GB)
init_boot.img (8.00 MB)
kernel.img (47.41 MB)
lk-fdl2-sign.bin (2.63 MB)
lk-fdl2.bin (2.63 MB)
lk-sign.bin (2.63 MB)
lk.bin (2.63 MB)
lk_autopoweron-sign.bin (2.63 MB)
lk_autopoweron.bin (2.63 MB)
logdata.img (56.12 KB)
logo.bin (317.10 KB)
mapping.zip (22 B)
md5.txt (6.46 KB)
odm.img (10.82 MB)
oem.img (60.10 KB)
oem_PD2420DF_EX_TR_NULL_NULL.img (48.10 KB)
oem_PD2420F_EX_N_NULL_NULL.img (60.10 KB)
oem_PD2420HF_EX_TR_NULL_NULL.img (48.10 KB)
oem_PD2420JF_EX_TR_NULL_NULL.img (48.10 KB)
oem_PD2420NF_EX_MX_NULL_NULL.img (44.10 KB)
oem_PD2420NF_EX_SCA_NULL_NULL.img (44.10 KB)
oem_PD2420OF_EX_MX_NULL_NULL.img (44.10 KB)
oem_PD2420OF_EX_SCA_NULL_NULL.img (44.10 KB)
oem_PD2420RF_EX_ZA_NULL_NULL.img (44.10 KB)
oem_PD2420SF_EX_TR_NULL_NULL.img (48.10 KB)
oem_PD2420TF_EX_MX_NULL_NULL.img (44.10 KB)
oem_PD2420TF_EX_SCA_NULL_NULL.img (44.10 KB)
partition.xml (44.31 KB)
persist.img (2.00 MB)
persist_vivo.img (44.07 KB)
PM_QogirL6_gnss_cm4.bin (190.35 KB)
PM_umw2631_qogirL6.bin (1.21 MB)
prodnv.img (44.07 KB)
product.img (1.26 GB)
QogirL6_AUDCP_DSP_lit_dm.bin (6.00 MB)
qogirl6_cm4.bin (1.00 MB)
qogirl6_pubcp_exLNA_customer_deltanv_PD2420F_EX.bin (16.57 KB)
qogirl6_pubcp_exLNA_customer_nvitem_PD2420F_EX.bin (838.77 KB)
qogirl6_pubcp_VHY_DM_DSP.bin (10.00 MB)
qogirl6_pubcp_VHY_LTEA_DSP.bin (20.00 MB)
release_name_cfg.ini (4.09 KB)
rollconfig.txt (12 B)
SC9600_qogirl6_pubcp_VHY_modem.bin (25.00 MB)
sml-sign.bin (120.46 KB)
sml.bin (118.81 KB)
super_empty.img (5.37 KB)
system_dlkm.img (76.10 KB)
system_ext.img (98.90 MB)
system_file_contexts.bin (1.45 MB)
teecfg-sign.bin (121.65 KB)
teecfg.bin (120.00 KB)
tool.ini (1.22 KB)
tos-sign.bin (3.30 MB)
tos.bin (3.30 MB)
u-boot-spl-16k-emmc-sign.bin (62.96 KB)
u-boot-spl-16k-emmc.bin (61.27 KB)
u-boot-spl-16k-sign.bin (62.96 KB)
u-boot-spl-16k-ufs-sign.bin (62.91 KB)
u-boot-spl-16k-ufs.bin (61.23 KB)
u-boot-spl-16k.bin (61.27 KB)
ums9230_6h10.xml (44.31 KB)
unisoc_FHD_1080_2400.bmp (7.42 MB)
userdata.img (610.92 MB)
vbmeta-sign.img (1.00 MB)
vbmeta.img (20.00 KB)
vbmeta_odm.img (4.00 KB)
vbmeta_oem.img (4.88 KB)
vbmeta_oem_PD2420DF_EX_TR_NULL_NULL.img (4.69 KB)
vbmeta_oem_PD2420F_EX_N_NULL_NULL.img (4.88 KB)
vbmeta_oem_PD2420HF_EX_TR_NULL_NULL.img (4.69 KB)
vbmeta_oem_PD2420JF_EX_TR_NULL_NULL.img (4.69 KB)
vbmeta_oem_PD2420NF_EX_MX_NULL_NULL.img (5.19 KB)
vbmeta_oem_PD2420NF_EX_SCA_NULL_NULL.img (5.06 KB)
vbmeta_oem_PD2420OF_EX_MX_NULL_NULL.img (5.19 KB)
vbmeta_oem_PD2420OF_EX_SCA_NULL_NULL.img (5.06 KB)
vbmeta_oem_PD2420RF_EX_ZA_NULL_NULL.img (5.06 KB)
vbmeta_oem_PD2420SF_EX_TR_NULL_NULL.img (4.69 KB)
vbmeta_oem_PD2420TF_EX_MX_NULL_NULL.img (5.19 KB)
vbmeta_oem_PD2420TF_EX_SCA_NULL_NULL.img (5.06 KB)
vbmeta_product.img (4.00 KB)
vbmeta_system.img (4.00 KB)
vbmeta_system_ext.img (4.00 KB)
vbmeta_vendor.img (4.00 KB)
vbmeta_vgc.img (1.56 KB)
vbmeta_vgc_SYS_VIVOTEST3_PD2420F_EXMA.img (2.44 KB)
vbmeta_vgc_SYS_VIVOTEST_PD2420F_EXMA.img (2.25 KB)
vbmeta_vgc_V000_PD2420F_EXMA.img (1.56 KB)
vendor_boot-debug.img (128.00 MB)
vendor_boot.img (128.00 MB)
vendor_dlkm.img (14.29 MB)
vendor_file_contexts.bin (2.36 MB)
vgc.img (28.10 KB)
vgc_SYS_VIVOTEST3_PD2420F_EXMA.img (90.61 MB)
vgc_SYS_VIVOTEST_PD2420F_EXMA.img (142.50 MB)
vgc_V000_PD2420F_EXMA.img (28.10 KB)
vivo_tools.zip (143.95 KB)
This post was last modified: 01-08-2026, 11:45 AM by spryshanto.
06-08-2026, 03:19 PM
(01-08-2026, 11:42 AM)spryshanto there is 2 super file name =
super_gsi64.img (3.12 GB),
super.img (4.82 GB)
.. so i exclude those 2 files in zip file..
Here is the link to the zip = https://drive.google.com/file/d/1p_bApqj...sp=sharing
contains this files =
...
OK.
Do you have a means to backup / flash your phone's firmware?
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
06-08-2026, 04:28 PM
(06-08-2026, 03:19 PM)hovatek OK.
Do you have a means to backup / flash your phone's firmware?
I can not seem to stay in download mode to flash my phone. After installing the standard Spreadtrum drivers on Windows, I powered off the device, held down both Volume Up and Volume Down, and connected the USB cable. Windows plays the connection sound and Device Manager briefly shows "SPRD U2S Diag," but it disconnects after just one second and switches to offline charging. Since the phone refuses to remain in the flashing state, SPD Flash Tool cannot proceed. Is there any trick to stay in flashing mode without using a test point, as I really don't want to open my phone , period
06-08-2026, 09:15 PM
(06-08-2026, 04:28 PM)spryshanto ..
Download the zip @ https://mega.nz/file/d85FFAAB#9ztLbP16uX...6KUGbMc51A and run hello_tue_tue.bat and let me know the outcome
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
07-08-2026, 08:41 AM
and this is the log that generated in that folder = https://pastebin.com/CM4XJqKC
This post was last modified: 07-08-2026, 08:52 AM by spryshanto.
07-08-2026, 04:17 PM
i managed to boot into DIAG mode from fastboot mode ... but that hello_tue_tue.bat file gives this error ...
https://ibb.co/spKczBzx
and this is the log file generated = https://drive.google.com/file/d/1C0Xy3rh...sp=sharing
This post was last modified: 07-08-2026, 04:20 PM by spryshanto.
07-08-2026, 05:21 PM
See here: https://pastebin.com/25G0xZ7P
11-08-2026, 10:20 AM
(07-08-2026, 05:21 PM)spryshanto UPDATE 3: I managed to get the first part of the CMD log before hitting a continuous loop of unexpected errors.
..
We still need to patch the FDLs.
We'll update you
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
Users browsing this thread:
1 Guest(s)
1 Guest(s)
Users browsing this thread:
1 Guest(s)
1 Guest(s)