Unlocking bootloader/ rebooting in edl without testpoint Vivo Y31 2021

[yxsef.7i]

Did you install Google USB driver?

Get the Google USB Driver | Android Developers

The Google USB Driver is required for Windows if you want to perform adb debugging with Google devices.

developer.android.com

Also check device manager to see if the driver is loaded:

Fastboot Not Detecting Device on Windows 10/ 11? Fix for OnePlus, Xiaomi, Realme & More

If Fastboot is not detecting devices on Windows 10/11, follow our guide and install the fastboot drivers for OnePlus, Xiaomi, Realme & more.

beebom.com

got in. will now try the command

 

[yxsef.7i]

Did you install Google USB driver?

Get the Google USB Driver | Android Developers

The Google USB Driver is required for Windows if you want to perform adb debugging with Google devices.

developer.android.com

Also check device manager to see if the driver is loaded:

Fastboot Not Detecting Device on Windows 10/ 11? Fix for OnePlus, Xiaomi, Realme & More

If Fastboot is not detecting devices on Windows 10/11, follow our guide and install the fastboot drivers for OnePlus, Xiaomi, Realme & more.

beebom.com

my driver doesn't know the vivo commands...

here's what's on my window after typing fastboot:
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader

options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048

 

[yxsef.7i]

Did you install Google USB driver?

Get the Google USB Driver | Android Developers

The Google USB Driver is required for Windows if you want to perform adb debugging with Google devices.

developer.android.com

Also check device manager to see if the driver is loaded:

Fastboot Not Detecting Device on Windows 10/ 11? Fix for OnePlus, Xiaomi, Realme & More

If Fastboot is not detecting devices on Windows 10/11, follow our guide and install the fastboot drivers for OnePlus, Xiaomi, Realme & more.

beebom.com

I

Did you install Google USB driver?

Get the Google USB Driver | Android Developers

The Google USB Driver is required for Windows if you want to perform adb debugging with Google devices.

developer.android.com

Also check device manager to see if the driver is loaded:

Fastboot Not Detecting Device on Windows 10/ 11? Fix for OnePlus, Xiaomi, Realme & More

If Fastboot is not detecting devices on Windows 10/11, follow our guide and install the fastboot drivers for OnePlus, Xiaomi, Realme & more.

beebom.com

command has worked. THANK YOU SO SO MUCH. :>>>>>

 

[yxsef.7i]

Unlocked models with this method:
Vivo Y31 PD2050F 2021 A12 6.7.20
Vivo V21e PD2107F A12 6.6.19

I did it from rooted Samsung J120F, I didn't try from PC///bc no PC =(

View attachment 5605163

My guide in Russian {Mod edit: Link removed}

Custom fastboot for vivo in ubu.zip is from here https://forum.xda-developers.com/t/how-to-unlock-bootloader-of-vivo-phones.3686690/

Video of a double terminal attack. After I came up with such an idea, I succeeded on the first try. To reboot in edl just use

fastboot oem reboot-edl

instead of

fastboot vivo_bsp unlock_vivo

REMINDER! Rebooting into edl from fastboot returning locked state, so you should unlock again if you need it.


My setup
rooted Sumsung J120F with A10 custom rom from this forum
custom fastboot for vivo v2 (Linux x86_64) from this forum (for vivo_bsp command)
Termux from f-droid
Ubuntu CLI from here https://github.com/tuanpham-dev/termux-ubuntu

So there is nothing from mother Russia=) Well... only sources list with officials servers with tag arch=amd64, you can create your own in order to download x86_64 libs.

You can use any .img, big enough.

Vivo Y31 <
qemu + fastboot , so i could run x86_64 on my 32 bit arm phone
Ubuntu to run qemu
Termux to run Ubuntu
Magisk to grant root

All commands with root, otherwise fastboot will not see device.

If you can copy-paste commands, then you will understand this

Spoiler: guide in Russian

Подготовка
#
1. ставим termux с f-droid

https://f-droid.org/repo/com.termux_118.apk

скачиваем кастомный fastboot для виво и источники пакетов для ubuntu Прикрепленный файлubu.zip ( 362.4 КБ )Кол-во скачиваний: 10
и распакуем в обычную стандартную папку Download, она же Загрузки

скачиваем vendor.img , хотя наверное может подойти любой vendor.img или даже любой *.img

Яндекс

Найдётся всё

disk.yandex.ru

2. запускаем termux

3. вводим
termux-setup-storage
соглашаемся

4. вводим
pkg update
на вопросы отвечаем
y
ввод

5 ставим сюда ubuntu, копируем-вставляем всю строчку

pkg install tsu wget curl proot tar -y && wget https://raw.githubusercontent.com/tuanpham-dev/termux-ubuntu/master/ubuntu.sh && chmod +x ubuntu.sh && bash ubuntu.sh nde


соглашаемся на все

задаем пользователя и пароли(пользователь маленькими буквами, пароль минимум 6 знаков!!!), я задал
user
user
mmmmmm
mmmmmm

6 мы внутри ubuntu, но давайте выйдем и зайдем

exit

заходим в убунту с рут

sudo ./start-ubuntu20.sh

7 получаем рут и переходим в корень

su
вводим пароль, который вы задали, у меня mmmmmm

cd

копируем из загрузок файлы фастбут и источники, чтоб можно было скачать x86_64 либы

cp ../sdcard/download/amd64.list ../etc/apt/sources.list.d
cp ../sdcard/download/fastboot ~/

8 добавляем целевую архитектуру x86_64

dpkg --add-architecture amd64

9 все обновляем

apt-get update

10 ставим qemu

apt install qemu-user

11 устанавливаем x86_64 fastboot ради библиотек(может и не надо)

apt install fastboot:amd64


Атака
#
12 В ubuntu запускаем наш фастбут через эмулятор

qemu-x86_64 /root/../lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 --library-path /root/../lib/x86_64-linux-gnu/ ./fastboot --help

жмем стрелочку вверх , стираем --help и вводим vivo_bsp unlock_vivo

выполняем и получаем fail

13 в термуксе свайпаем с левой верхней части экрана для показа меню и жмем new session, это нужно для второго терминала
#


14 выбираем второй инстанс и также заходим в убунту

sudo ./start-ubuntu20.sh

далее

su

вводим пароль, который вы задавали

перходим в корень

cd

теперь можно сразу две команды посылать

15 В новом терминале вставляем

qemu-x86_64 /root/../lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 --library-path /root/../lib/x86_64-linux-gnu/ ./fastboot flash vendor /sdcard/download/vendor.img

файл vendor.img должен быть в загрузках

Пойдет загрузка файла в телефон, но не прошивка. Её без анлока и полного скачивания не будет

16 Переходим в первый терминал и выполняем команду повторно

стрелочка вверх - ввод

qemu-x86_64 /root/../lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 --library-path /root/../lib/x86_64-linux-gnu/ ./fastboot vivo_bsp unlock_vivo

@Pervokur S1 Pro (PD1945F_EX_A) confirmed unlocked. Was first to test.

 

[yxsef.7i]

Unlocked models with this method:
Vivo Y31 PD2050F 2021 A12 6.7.20
Vivo V21e PD2107F A12 6.6.19

I did it from rooted Samsung J120F, I didn't try from PC///bc no PC =(

View attachment 5605163

My guide in Russian {Mod edit: Link removed}

Custom fastboot for vivo in ubu.zip is from here https://forum.xda-developers.com/t/how-to-unlock-bootloader-of-vivo-phones.3686690/

Video of a double terminal attack. After I came up with such an idea, I succeeded on the first try. To reboot in edl just use

fastboot oem reboot-edl

instead of

fastboot vivo_bsp unlock_vivo

REMINDER! Rebooting into edl from fastboot returning locked state, so you should unlock again if you need it.


My setup
rooted Sumsung J120F with A10 custom rom from this forum
custom fastboot for vivo v2 (Linux x86_64) from this forum (for vivo_bsp command)
Termux from f-droid
Ubuntu CLI from here https://github.com/tuanpham-dev/termux-ubuntu

So there is nothing from mother Russia=) Well... only sources list with officials servers with tag arch=amd64, you can create your own in order to download x86_64 libs.

You can use any .img, big enough.

Vivo Y31 <
qemu + fastboot , so i could run x86_64 on my 32 bit arm phone
Ubuntu to run qemu
Termux to run Ubuntu
Magisk to grant root

All commands with root, otherwise fastboot will not see device.

If you can copy-paste commands, then you will understand this

Spoiler: guide in Russian

Подготовка
#
1. ставим termux с f-droid

https://f-droid.org/repo/com.termux_118.apk

скачиваем кастомный fastboot для виво и источники пакетов для ubuntu Прикрепленный файлubu.zip ( 362.4 КБ )Кол-во скачиваний: 10
и распакуем в обычную стандартную папку Download, она же Загрузки

скачиваем vendor.img , хотя наверное может подойти любой vendor.img или даже любой *.img

Яндекс

Найдётся всё

disk.yandex.ru

2. запускаем termux

3. вводим
termux-setup-storage
соглашаемся

4. вводим
pkg update
на вопросы отвечаем
y
ввод

5 ставим сюда ubuntu, копируем-вставляем всю строчку

pkg install tsu wget curl proot tar -y && wget https://raw.githubusercontent.com/tuanpham-dev/termux-ubuntu/master/ubuntu.sh && chmod +x ubuntu.sh && bash ubuntu.sh nde


соглашаемся на все

задаем пользователя и пароли(пользователь маленькими буквами, пароль минимум 6 знаков!!!), я задал
user
user
mmmmmm
mmmmmm

6 мы внутри ubuntu, но давайте выйдем и зайдем

exit

заходим в убунту с рут

sudo ./start-ubuntu20.sh

7 получаем рут и переходим в корень

su
вводим пароль, который вы задали, у меня mmmmmm

cd

копируем из загрузок файлы фастбут и источники, чтоб можно было скачать x86_64 либы

cp ../sdcard/download/amd64.list ../etc/apt/sources.list.d
cp ../sdcard/download/fastboot ~/

8 добавляем целевую архитектуру x86_64

dpkg --add-architecture amd64

9 все обновляем

apt-get update

10 ставим qemu

apt install qemu-user

11 устанавливаем x86_64 fastboot ради библиотек(может и не надо)

apt install fastboot:amd64


Атака
#
12 В ubuntu запускаем наш фастбут через эмулятор

qemu-x86_64 /root/../lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 --library-path /root/../lib/x86_64-linux-gnu/ ./fastboot --help

жмем стрелочку вверх , стираем --help и вводим vivo_bsp unlock_vivo

выполняем и получаем fail

13 в термуксе свайпаем с левой верхней части экрана для показа меню и жмем new session, это нужно для второго терминала
#


14 выбираем второй инстанс и также заходим в убунту

sudo ./start-ubuntu20.sh

далее

su

вводим пароль, который вы задавали

перходим в корень

cd

теперь можно сразу две команды посылать

15 В новом терминале вставляем

qemu-x86_64 /root/../lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 --library-path /root/../lib/x86_64-linux-gnu/ ./fastboot flash vendor /sdcard/download/vendor.img

файл vendor.img должен быть в загрузках

Пойдет загрузка файла в телефон, но не прошивка. Её без анлока и полного скачивания не будет

16 Переходим в первый терминал и выполняем команду повторно

стрелочка вверх - ввод

qemu-x86_64 /root/../lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 --library-path /root/../lib/x86_64-linux-gnu/ ./fastboot vivo_bsp unlock_vivo

Did you install Google USB driver?

Get the Google USB Driver | Android Developers

The Google USB Driver is required for Windows if you want to perform adb debugging with Google devices.

developer.android.com

Also check device manager to see if the driver is loaded:

Fastboot Not Detecting Device on Windows 10/ 11? Fix for OnePlus, Xiaomi, Realme & More

If Fastboot is not detecting devices on Windows 10/11, follow our guide and install the fastboot drivers for OnePlus, Xiaomi, Realme & more.

beebom.com

Hey, i've successfully unlocked the bootloader... but I cannot get the boot.img of Android 12 on my device because vivo didn't update the website yet. Is there any other way I can grab the boot.img? Thanks

 

[domineus]

Hey, i've successfully unlocked the bootloader... but I cannot get the boot.img of Android 12 on my device because vivo didn't update the website yet. Is there any other way I can grab the boot.img? Thanks

you can try dsu https://github.com/VegaBobo/DSU-Sideloader to boot into los19.1 gsi (from andy Yan , bvS, not!!! vndklite) with integrated root. Then use dd if= ... to backup all partitions (around 70, except "sda" and "userdata", don't backup them)

) in /dev/block/by-name/


or use magisk 24306 canary to get root on stock, but it's more risky,



more info here

Vivo x70 Pro+ Bootloader Unlock - HOW TO GUIDE

WARNING! THIS IS EXPERIMENTAL, I HAVE NO IDEA WHERE WE CAN GO FROM HERE. THIS MIGHT BREAK YOUR DEVICE!!! UNLOCKING THE BOOTLOADER REQUIRES A WIPE AFTERWARDS! UNLOCKING THE BOOTLOADER WILL DISABLE YOUR FINGERPRINT READER! (FIXED BY RELOCKING)...

forum.xda-developers.com

It didn't work. It wouldn't boot after 10 minutes for android 13 beta 2 to test. I may uninstall GSI at this point

 

[yxsef.7i]

I did it!

These feature works even after BLU:
Fingerprint sensor
Face ID
OTA install

and Magisk works too!
You have to use DSU Loader to get boot.img though.

Here's full firmware dump of PD2178_A_12.0.14.5.W10 (contains all partitions for research purpose):

PD2178_A_12.0.14.5.W10 - Google Drive

drive.google.com

View attachment 5618781

Hey, how did you flash Magisk's boot.img? You said that using fastboot to flash it doesn't work, so how did you do it?

 

[Pervokur]

Hey, i've successfully unlocked the bootloader... but I cannot get the boot.img of Android 12 on my device because vivo didn't update the website yet. Is there any other way I can grab the boot.img? Thanks

flash recovery from a11 ota(to avoid error "package limited upgrade")

reboot to recovery (if you boot normaly then stock recovery will be returned)

install a12 ota, which you can get

use boot.img from this ota

and if you still can receive updates, then with root you will find ota zip at /data/vivo-updater

upd1, early A12 recovery (jan-apr) could be with bug(no ota firmware check) so you can run any updater-script. I will not teach you how to write updater-scripts

upd2 another not so easy way - install LOS19.1 gsi through dsu sideloader,
modify vendor.img inside super
(it's could be done by mounting part of super, or just dump partitions, mount vendor, edit, flash through fastbootd)

particularly install-recovery.sh so it will dump boot.img somewhere on the next boot

 

[xiaoleGun]

I used these methods on iqoo neo5 lite (pd2118), but they don't seem to work. In the last step, fastboot vivo_ bsp unlock_ vivo

There will be the following errors and the device will be restarted automatically:
remote: Flashing is not allowed in Lock State
unknown status code
status read failed (Too many links)

If you can, please tell me the possible solution to this problem. Thank you very much.

 

[Pervokur]

I used these methods on iqoo neo5 lite (pd2118), but they don't seem to work. In the last step, fastboot vivo_ bsp unlock_ vivo

There will be the following errors and the device will be restarted automatically:
remote: Flashing is not allowed in Lock State
unknown status code
status read failed (Too many links)

View attachment 5620687
If you can, please tell me the possible solution to this problem. Thank you very much.

looks like iqoo bootloader isnt't uploading file with
fastboot flash xxxx bigimgfile.img

immediate error, right? Can you upload your abl.elf from ota firmware

 

[xiaoleGun]

looks like iqoo bootloader isnt't uploading file with
fastboot flash xxxx bigimgfile.img

immediate error, right? Can you upload your abl.elf from ota firmware

iqoo bootloader has uploaded files, the result is the same

The following is abl.elf, I hope this can help us solve the problem, thank you.
It comes from the latest version of ota firmware with version 6.15.5

 

[Pervokur]

iqoo bootloader has uploaded files, the result is the same
View attachment 5620733
The following is abl.elf, I hope this can help us solve the problem, thank you.
It comes from the latest version of ota firmware with version 6.15.5

can you make screenshot of two terminals
in 1st fastboot flash vendor vendor.img
wait 10 sec
in 2nd fastboot vivo_bsp unlock_vivo

 

[xiaoleGun]

can you make screenshot of two terminals
in 1st fastboot flash vendor vendor.img
wait 10 sec
in 2nd fastboot vivo_bsp unlock_vivo

ok, I'll try. just a moment, please.

 

[xiaoleGun]

can you make screenshot of two terminals
in 1st fastboot flash vendor vendor.img
wait 10 sec
in 2nd fastboot vivo_bsp unlock_vivo

 

[wenti2002]

Firstly,I am sorry for my poor English.But I met some problems and they are beyond my ability.So I want to ask for help.
My device is iqoo neo5(CN,P2055D).When I followed the steps to unlock the bootloader,the windows terminal showed that it was okey and finished unlocking.But actually when I rebooted my phone,it rebooted normally and didn't let me format my data.It was very strange.This method works well on the Snapdragon 888 devices.So we think that it didn't working on all of the vivo devices,especially the devices are older than Snapdragon 888 devices.But it is strange that this method was also working on IQOO(PD1824) which is older than iqoo neo5.Anyway,I am so appreciated that you can read these words and thank you for your efforts.

 

[Pervokur]

View attachment 5620747

try usb 2.0 port

 

[xiaoleGun]

try usb 2.0 port

I tried it 56 minutes ago and the result is still the same. I want to switch the system to win10 or win7 test. Maybe win11 has poor compatibility with old computers.

 

[Pervokur]

I tried it 56 minutes ago and the result is still the same. I want to switch the system to win10 or win7 test. Maybe win11 has poor compatibility with old computers.

mb you need large file filled with "1"

 

[xiaoleGun]

mb you need large file filled with "1"

With all due respect, what does "1" mean? I have tried the 1.8g vendor, and the following errors will appear:

remote: check signature fails

Maybe I need a bigger file?

and in china, we found that neo5 and neo3 have the same mistakes.

 

[Pervokur]

it

With all due respect, what does "1" mean? I have tried the 1.8g vendor, and the following errors will appear:

remote: check signature fails

Maybe I need a bigger file?

and in china, we found that neo5 and neo3 have the same mistakes.

it's clearly that iqoo bootloaders are different...

you can create 1G file filled with 1 with this

< /dev/zero tr '\000' '\377' | head -c 1G > filledwith1.img

if you're not linux user then you can do it in termux apk ob your phone