Unlocking bootloader/ rebooting in edl without testpoint Vivo Y31 2021

Search This thread

domineus

Senior Member
Jun 16, 2007
2,172
162
extremely off topic since I have unlocked my bootloader. But has anyone noticed that usb debugging doesn't work reliably with vivo devices? adb works well in recovery as does fastboot but adb isn't working the best on neither my mac partition or windows. It takes a long time to revoke, enable usb debugging for it to finally work.

Anyone else notice this?
 

Pervokur

Senior Member
Feb 15, 2022
98
22
extremely off topic since I have unlocked my bootloader. But has anyone noticed that usb debugging doesn't work reliably with vivo devices? adb works well in recovery as does fastboot but adb isn't working the best on neither my mac partition or windows. It takes a long time to revoke, enable usb debugging for it to finally work.

Anyone else notice this?
no problems with vivo y31, adb, LADB work perfectly
 

laggy_boy

New member
Apr 27, 2022
2
0
hey pervokur,
do u mind giving ur discord id maybe i'd really like to get this done but im not understanding anything and personal help would be helpful pls
 

NeonzGamingYT

Member
Dec 5, 2020
20
1
Redmi 9A
1653895595809.png

I also wasnt be able to unlock even doing that flashing trick

Device:
vivo Y11(2019) PD1930, vivo 1906
 

6addri

Member
Mar 28, 2015
16
2
Namyangju-Si
Google Pixel 6

J0nDoe297

Member
Oct 5, 2020
10
1
no problems with vivo y31, adb, LADB work perfectly
Pervokur do u have magisk working on your vivo y31? I managed to patch and flash the latest ota boot img on my vivo y31 but it gets stuck in fastboot mode and doesn't reboot. The recovery screen says that the phone is rooted but it won't boot up
 

Pervokur

Senior Member
Feb 15, 2022
98
22
Pervokur do u have magisk working on your vivo y31? I managed to patch and flash the latest ota boot img on my vivo y31 but it gets stuck in fastboot mode and doesn't reboot. The recovery screen says that the phone is rooted but it
on y31 magisk can't mount /system, so things aren't simple

-flash los19.1 gsi and use phh-su

-you can try to boot with my vbmeta, but I didn't try to fix magisk on stock rom. In theory 24.3 magisk will be able to grant root(no modules) if you manualy start daemon

/sbin/magisk64 --daemon

but for it you should edit some .rc or .sh file

vgc/vgc.rc could be a good target

Can't help with anything else.
 

Attachments

  • vbmeta.img
    64 KB · Views: 3
Last edited:
  • Like
Reactions: J0nDoe297

J0nDoe297

Member
Oct 5, 2020
10
1
on y31 magisk can't mount /system, so things aren't simple

-flash los19.1 gsi and use phh-su

-you can try to boot with my vbmeta, but I didn't try to fix magisk on stock rom. In theory 24.3 magisk will be able to grant root(no modules) if you manualy start daemon

/sbin/magisk64 --daemon

but for it you should edit some .rc or .sh file

vgc/vgc.rc could be a good target

Can't help with anything else.
Nah I've given up now. Was able to flash magisk on root but it refused to boot and acknowledged the root
 

Pervokur

Senior Member
Feb 15, 2022
98
22
alternative:
in new fastboot v30+
fastboot boot vendor.img

in custom fastboot
fastboot oem vivo_bsp unlock_vivo
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Pervokur do u have magisk working on your vivo y31? I managed to patch and flash the latest ota boot img on my vivo y31 but it gets stuck in fastboot mode and doesn't reboot. The recovery screen says that the phone is rooted but it
    on y31 magisk can't mount /system, so things aren't simple

    -flash los19.1 gsi and use phh-su

    -you can try to boot with my vbmeta, but I didn't try to fix magisk on stock rom. In theory 24.3 magisk will be able to grant root(no modules) if you manualy start daemon

    /sbin/magisk64 --daemon

    but for it you should edit some .rc or .sh file

    vgc/vgc.rc could be a good target

    Can't help with anything else.
  • 2
    This is a tool from our QQ group.

    I think it is necessary to remind those of you who use the sm8250 device that the sm8250 is not applicable to this method.

    fingerprint unlocking can also be used normally on x70pro+. You only need to use version 1.5 factory test to calibrate the fingerprint
    1
    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 =(



    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

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

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

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

    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
    1
    OMG! You did it you mad man! I did this on windows, unlocked the bootloader on the Vivo x70 pro plus.
    1
    I must ask
    is this tested on the x fold???
    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):
    xfoldblu.jpg
    1
    How would I do that? Edit: Nvm, its in your files. Thanks!
    It's not in my file. It's here.

    Next, my expression may be incomprehensible to you because my English is not good. In order to facilitate understanding, I will provide Chinese for your reference

    1. You need a black and flesh rubber
    2. Installation factory test 1.5
    3. Enter phone input * #558# enter factory test
    4. Find the quality test
    5. Find the fingerprint test
    6. Photoelectric fingerprint calibration
    7. Use flesh colored rubber for calibration
    8. Use black rubber for calibration

    Now, you can enjoy root and fingerprints.

    Chinese
    1.你需要一块黑色和肉色橡皮
    2.安装工厂测试1.5
    3.进入Phone输入*#558#进入工厂测试
    4.找到品质测试
    5.找到指纹测试
    6.选择第一个光电指纹校准
    7.使用肉色橡皮进行校准
    8.使用黑色橡皮进行校准