Unlocking bootloader/ rebooting in edl without testpoint Vivo Y31 2021 - Upgrading, Modifying and Unlocking

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 =(
Your browser is not able to display this video.
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 said:
My guide in Russian {Mod edit: Link removed}
Click to expand...
Click to collapse
@Pervokur
Welcome to XDA! We're greatful that you share your knowledge.
However; I've removed the references to 4pda! Same applies to your post here.
4pda is not only another phone related website (and not at all affiliated with xda-developers) but also well known for the distribution of malware and warez. Links to 4pda are not accepted on XDA.
XDA Forum Rules (excerpt):
...
6. Do not post or request warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
(...)
11. Don’t post with the intention of selling something.
Don’t use XDA to advertise your product or service. Proprietors of for-pay products or services, may use XDA to get feedback, provide beta access, or a free version of their product for XDA users and to offer support, but not to post with the intention of selling. This includes promoting sites similar / substantially similar to XDA-Developers.com.
Do not post press releases, announcements, links to trial software or commercial services, unless you’re posting an exclusive release for XDA-Developers.com.
Encouraging members to participate in forum activities on other phone related sites is prohibited.
Off-site downloads are permitted if the site is non-commercial and does not require registration.
Off-site downloads from sites requiring registration are NOT encouraged but may be permitted if both of the following conditions are met:
A) The site belongs to a member of XDA-Developers with at least 1500 posts and 2 years membership, who actively maintains an XDA-Developers support thread(s) / posts, related to the download.
B) The site is a relatively small, personal website without commercial advertising / links (i.e. not a competitor forum-based site with purposes and aims similar to those of XDA-Developers.com.)
...
Click to expand...
Click to collapse
Regards
Oswald Boelcke
Senior Moderator

OMG! You did it you mad man! I did this on windows, unlocked the bootloader on the Vivo x70 pro plus.

Killuminati91 said:
OMG! You did it you mad man! I did this on windows, unlocked the bootloader on the Vivo x70 pro plus.
Click to expand...
Click to collapse
del

I must ask
is this tested on the x fold???

domineus said:
I must ask
is this tested on the x fold???
Click to expand...
Click to collapse
Maybe, but do you really want to become 1st with unlocked x fold?

Pervokur said:
Maybe, but do you really want to become 1st with unlocked x fold?
Click to expand...
Click to collapse
tempting as it is there's not too much reason to do it besides sideloading android 13 beta...which could be problematic as i don't have the original firmware. Plus you lose the really sweet fingerprint sensor

domineus said:
I must ask
is this tested on the x fold???
Click to expand...
Click to collapse
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
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

AndroPlus said:
I did it!
Fingerprint sensor can be used even after BLU.
View attachment 5618781
Click to expand...
Click to collapse
Impressive. Does face ID work too? I assume this resulted in wiping your memory which means I would have to set things up again...
But one big bonus is that we could run Android 13 beta 2 on the device.
Does anyone have a backup to the vivo stock rom? I received an update this morning and I wanted to make sure if anything went side ways I can still flash stock.

domineus said:
Impressive. Does face ID work too? I assume this resulted in wiping your memory which means I would have to set things up again...
But one big bonus is that we could run Android 13 beta 2 on the device.
Does anyone have a backup to the vivo stock rom? I received an update this morning and I wanted to make sure if anything went side ways I can still flash stock.
Click to expand...
Click to collapse
Yes, Face ID works too.

Dsu loader? Where's that?

@Pervokur I think the 4pda links are the links to a custom vendor.img, how would I get my own vendor.img?

Okay it worked I am OEM unlocked on the x fold. Massive update coming on the device (6.82 gb). I haven't decided if I want to root the device (I may but don't we need TWRP)?
I could in theory throw android 13 beta 2 on the device but I also need a pathway to flash stock if I do...eh we will see

domineus said:
Okay it worked I am OEM unlocked on the x fold. Massive update coming on the device (6.82 gb). I haven't decided if I want to root the device (I may but don't we need TWRP)?
I could in theory throw android 13 beta 2 on the device but I also need a pathway to flash stock if I do...eh we will see
Click to expand...
Click to collapse
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
THIS GLITCH HAS BEEN FIXED AS OF MAY 2022. IF YOUR FIRMWARE IS PAST THAT SECURITY LEVEL YOU CAN NOT OPEN THE BOOTLOADER ANYMORE. WARNING! THIS IS EXPERIMENTAL, I HAVE NO IDEA WHERE WE CAN GO FROM HERE. THIS MIGHT BREAK YOUR DEVICE!!! UNLOCKING...
forum.xda-developers.com

yxsef.7i said:
@Pervokur I think the 4pda links are the links to a custom vendor.img, how would I get my own vendor.img?
Click to expand...
Click to collapse
You can use any file, as all flashing commands will fail on locked bootloader.
It's important to execute the unlock command in a separate command window before the flashing command starts and fails.
So you can also use random movie file like this:
fastboot boot movie.mp4
then immediately run
.\fastboot.exe vivo_bsp unlock_vivo
on other command prompt

HAHAHA LOL. what a big exploit this is. thank you btw. will reply again once i can get it to unlock. will also ask about magisk later on, if there's some sort of specific steps for these devices.

AndroPlus said:
You can use any file, as all flashing commands will fail on locked bootloader.
It's important to execute the unlock command in a separate command window before the flashing command starts and fails.
So you can also use random movie file like this:
fastboot boot movie.mp4
then immediately run
.\fastboot.exe vivo_bsp unlock_vivo
on other command prompt
Click to expand...
Click to collapse
hey, fastboot isn't detecting my device, but adb does detect my device. any idea why? bit confused sorry

yxsef.7i said:
hey, fastboot isn't detecting my device, but adb does detect my device. any idea why? bit confused sorry
Click to expand...
Click to collapse
Did you install Google USB driver?
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows 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

AndroPlus said:
You can use any file, as all flashing commands will fail on locked bootloader.
It's important to execute the unlock command in a separate command window before the flashing command starts and fails.
So you can also use random movie file like this:
fastboot boot movie.mp4
then immediately run
.\fastboot.exe vivo_bsp unlock_vivo
on other command prompt
Click to expand...
Click to collapse
this se
yxsef.7i said:
hey, fastboot isn't detecting my device, but adb does detect my device. any idea why? bit confused sorry
Click to expand...
Click to collapse
even with the official Google adb+fastboot, its the same thing. no fastboot, but there's adb

AndroPlus said:
Did you install Google USB driver?
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows 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
Click to expand...
Click to collapse
this is what im looking for. hold on

Related

[TOOL] Lx Multi Tool v1.3.2 [WIN/LIN/MAC][Unlock/Recovery/Stock/Kernel/More]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​It has LINUX/UNIX and MAC support!
​
Because there is another tool for Android called Android Multi Tools, I renamed this one to Lx Multi Tool, future releases will go under this name.
​ Features: ​
Fastboot​​- Unlock/Lock Bootloader​- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.2 Included​- Flash any partition (Flashing submenu)​- Flash full Stock images (you can choose and add images)​- Erase partitions (you can choose which of the partitions)​- Reboot (you can choose again...)​​Adb​​- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.56 (Systemless!) included​- Backup (you can choose the name and place for your backup)​- Restore (you can choose your backup)​- Version (it just shows the version of your adb binaries) - platform-tools 23.0.1 included​- Logs (DMESG and Logcat)​- Screenshots (you can directly take screenshots to your PC with no Root)​- Reboot (lots of choices)​​Others​​- Refresh and delete files/folders from menus (Right-click or key F5 and Del)​- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)​- Tab key support for easier keyboard navigation​- Tool-tips for all buttons​- Check for updates​- Link to xda-thread (here)​​​ Download links: ​
Windows x86|x64 - Linux x64 - MAC x64​​All released versions can be found here.​​
​
(The latest versions are always on the bottom.)​​[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.​​
​ Known bugs/limitations: ​
- For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)​- For the return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)​​
​ Changelog: ​
​Check the changelog for each release here.​​​ Tutorials/FAQ: ​
​Q: How do I get in bootloader/fastboot mode?​Turn off the phone and turn it on by using Volume down + Power key.​​Q: How do I check for updates on your tool?​Follow the instructions on the screen below.​
​Q: Where can I find the device driver to install it for windows?​Click here, download the driver, and run the setup.​​Q: How do I root my stock phone?​- Unlock bootloader.​- Flash recovery.​- Use SuperSU 2.62 systemless or higher from here.​(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)​​Q: I get an error "Cannot open file" on MAC, what should I do?​Open the terminal, go to your application path and paste this command:​
Code:
chmod +x LxMultiTool.app/contents/macos/*
​Q: What do I need to do in order to be in Fastboot or in ADB mode.​Fastboot mode will be detected only while being in bootloader.​ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.​Refresh button needs to be used in order to check for what mode you are in.​​Q: Are there any other software that I need to install in order to run this tool?​On Windows and MAC everything is bundled, so nothing needs to be installed, just run.​On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.​If it's not enough, use ldd LxMultiTool in the terminal to find out what you're missing from your environment.​​Q: I have a yellow/orange/red text screen during boot, what's that?​When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.​​Q: Hey, my device is not detected, why?​On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.​Also, make sure you click the connection Refresh button after connecting the device to your PC.​​Q: What do I need to do in order to install a custom ROM?​1. Unlock Bootloader.​2. Flash a custom recovery of your choice.​3. Flash an insecure kernel (boot).​4. Flash custom ROM with no problems via recovery.​All those things are found and can be done via this tool.​​Q: Hi, I just downloaded this tool, how do i use it?​First, extract the folder somewhere.​After that, run LxMultiTool.exe on windows by double-clicking it, LxMultiTool on Linux, and the same on mac.​​Q: Do I need android-sdk installed or something else?​No! This tool uses its own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyway.​This tool is fully portable and stand-alone.​​Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?​Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:​- Enable Developer options​- Enable USB Debugging​- Look for the ‘OEM Unlock’ Option and toggle it.​​Q: How do I use the return to stock feature?​First, download the latest package from here, then extract the contents (there is an archive in the archive) until you get to a folder like angler-mda89d​that contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.​​Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.​
​Q: How do I enable Developer options?​- Launch the Settings​- Scroll Down and Tap on About Phone(or About Device)​- Locate the Build Number Section​- Tap on the Build Number Option 7 Times​- Go Back to the Main Settings Page​- Scroll Down and Tap on Developer Options​​Q: Hi, I just bought a phone what should I do now?​Well, you firstly need to unlock your bootloader...​​Q: What is logcat?​Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.​It is usually used for debugging and entertainment(?).​When you report an error/bug to somebody, it will be a blessing to provide a logcat (log file)!​​Q: What is a Custom Recovery and why do I need one?​A custom recovery is that thingy that lets you flash .zip files, use your logic, and you will get it why you need one.​​Q: There are other guides/tutorials out there. Should I check them instead of this?​If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...​​Q: What is sideload and how do I use it?​Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.​Please note that you need to be in sideload mode on your recovery before doing this.​To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload​
​ Sources: ​
The official and original repository can be found here.​​
​ Bug reports/feature requests: ​
If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on GitHub for more traceability here.​​
​ Licensing: ​
Please note that this tool is open source and released under the GPL v3 license, which can be read here.​Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.​​
​ Tech and stuff: ​
Some additional marketing for stuff used in this tool​​Qt - An awesome cross-platform IDE​Vmware - For letting me test this tool on all platforms (Linux and MAC).​Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)​UnixUtils - For the sed utility for Windows.​AndroidFileHost - For the awesome file-management platform for developers.​​
​ Donations: ​
Even though this tool is provided free of charge, fully open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.​​This section will also include the hall of fame for donors and on the github repository.​​Special thanks for donations:​- @john7760​​
​ Disclaimer: ​
I will not be responsible for smashed screens, bricked phones, or any other things that you can accuse me of, I've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.​Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A, or useless posts, please read the FAQ section upside, it's like a Mini-Guide!
XDA:DevDB Information
Lx Multi Tool, Tool/Utility for the Huawei Nexus 6P
Contributors
Lexmazter
Source Code: https://github.com/lexmazter/LxMultiTool
Version Information
Status: Stable
Created 2016-01-01
Last Updated 2016-01-16
Already tool kit?
*Damn, nexus dev support is amazing
I feel so bad for buying galaxy s6, 0 aosp roms, Mod edit: Profanity removed dev support and all because of stupid exynos ;C
You da man! Can't wait for my phone to show up.
That was quick!! Waiting for this phone to be launched in India.
It works great thanks.I mean Tool
Wow. Can't wait to get my 6P and use this
Sent from my A0001 using Tapatalk
Add to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P
Haven't even received my device yet, just wanted to say Thanks in advance!
Showing so much promise
I can't say more for this kind of support.
Great to see this already in the forum. Waiting on my 6P 128 Gig MONSTER.
wilbarger said:
Great to see this already in the forum. Waiting on my 6P 128 Gig MONSTER.
Click to expand...
Click to collapse
Got the 128gb monster on the way myself.
Thanks for this. Making it easy for everyone is a great thing I'm so excited to get back on a nexus
Thanks for this tool, I need to start from scratch because I don't have a Nexus since Nexus One
Thanks for this. Will be a first time user for the nexus generation. Just ordered the 6P so will definitely be doing this .
Great seeing this already. Coming from an S4 to the 64GB 6P. Will it be possible to relock the bootloader after installing a custom recovery or is the stock recovery required for the lock?
Sent from my SPH-L720 using Tapatalk
C4PO said:
Great seeing this already. Coming from an S4 to the 64GB 6P. Will it be possible to relock the bootloader after installing a custom recovery or is the stock recovery required for the lock?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
AFAIK, locking bootloader has nothing to do with the recovery, but then again, I never locked a bootloader...
Pretty sure you'd need to flash stock recovery. It won't hurt anything to try it without stock recovery, but if it doesn't work then you'll know for sure why.
I'm not planning to mess around with it too much until a stock system file is available. I need a Plan B. Lol
Doesn't run for me. (Mac User)
Heres the terminal error
sh [Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh
[Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh: line 3: [Path to location]/6PMultiTool.v0.2/simple_curses.sh: No such file or directory
There doesn't seem to be a "simple_curses.sh" file in the tool directory that I can find. Hope you can get it figured out! Thanks for the awesome tool as well!
ryman222 said:
Doesn't run for me. (Mac User)
Heres the terminal error
sh [Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh
[Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh: line 3: [Path to location]/6PMultiTool.v0.2/simple_curses.sh: No such file or directory
There doesn't seem to be a "simple_curses.sh" file in the tool directory that I can find. Hope you can get it figured out! Thanks for the awesome tool as well!
Click to expand...
Click to collapse
Unfortunately I never got the chance to test the MAC version, finally I have a tester
From what I can see at a first look is that this simple_curses.sh is some leftover from when I experimented with some UI tricks for bash to try to simulate the looks of the batch version..
Can you please check this temporary version from here -> 6PMultiTool.v0.2.1.zip

Rooting the "Huawei Y6 II Compact Dual-SIM" aka "Honor 5A" (LYO-L21)

Rooting the "Huawei Y6 II Compact Dual-SIM" aka "Honor 5A" (LYO-L21)
Good day,
I recently purchased a "Huawei Y6 II Compact Dual-SIM". The Model is: LYO-L21.
Apparently, this device is identical with the "Huawei Honor 5A", only that it doesnt say "Honor" on the back cover.
Anyway, I would like to root this device and install a custom recovery.
I already searched the forum and found this, this and this thread. However, the methods mentioned there do not seem to be working for the LYO-L21.
The bootloader has been unlocked.
I tried flashing a custom recovery.img in fastboot mode. However, it failed and now I have no working recovery on this device at all. I have tried rooting the phone with different versions of KingRoot. I tried the app as well as the PC version.
Currently the phone is working normally. Just lacking a recovery and being unable to root this device is kinda frustrating me. lul.
It would be cool if anybody could share the stock recovery.img for the "Huawei Y6 II Compact" so that I can flash that and wait until this one becomes rootable (if it isn't at this point of time).
Hope you guys can help me.
Thanks,
Mike
Здравствуйте занляните на сайт 4pda.ру и или наберите в поисковике Яндекс Хонор 5a 4pda и ещё honor 4c pro 4pda
или на 4pda там мой ник или имя Tigr1199g найдите и напишите мне
Если у вас на процессоре mtk то вы на форуме должны найти решение вашей проблемы)
---------- Post added at 10:40 PM ---------- Previous post was at 10:37 PM ----------
Welcome to the website zanlyanite 4pda.ru and either type in a search engine Yandex Honor 5a 4pda and still honor 4c about 4pda
or 4pda there is my nickname, or the name and email Tigr1199g find me
If you have a MTK processor you have on the forum to find a solution to your problem)
---------- Post added at 10:46 PM ---------- Previous post was at 10:40 PM ----------
Возможно вам поможет тема huawei honor 5A - там есть бэкап и обновление) - потому что у вас характеристики одинаковые с honor 5a)
Но я не знаю у вас версия android 64 бита или 32 у honor 5a 32 бита в процессор 64 бита - у обеих одинаковые)
4pda.ru
Юсуф said:
Welcome to the website zanlyanite 4pda.ru and either type in a search engine Yandex Honor 5a 4pda and still honor 4c about 4pda
Click to expand...
Click to collapse
Юсуф said:
or 4pda there is my nickname, or the name and email Tigr1199g find me
If you have a MTK processor you have on the forum to find a solution to your problem)
Click to expand...
Click to collapse
Hello Юсуф and thank you for your reply.
Sadly, I do not speak Russian so I will keep my English simple for you.
As I understand it, you want me to check out the forum 4pda.ru for more information about my phone. You seem to be confirming that the "Y6 II Compact" is identical with the "Honor 5A" - and, apparently the "Honor 4C", is that correct?
And yes, my device has a MTK processor.
I will try to translate the page 4pda.ru and search the forums when I have some time.
Thank you again and have a nice day!
Cheers,
Mike
Good afternoon sorry for the very long answer) huawei honor 4c - there - 64-bit - but also you can find there useful information)
You probably similar to honor 5a ) just in search of Yandex drive huawei honor 5a and napichite next to the phone name (4pda)
There all in Russian but you can use google chrome to translate pages or any other convenient translator)
(I do not understand in English but I translated with online translator Yandex)
---------- Post added at 07:22 PM ---------- Previous post was at 07:18 PM ----------
On 4pda in the subject huawei honor 5a has a custom vostanovlenie for your advise to zaginuti there)
Any custom recovery that Im tryed saying - too lage size ( honor 5x/honor 4x) Maybe somebody have working custom recovery image?
Hello guys,
Are there any news about this?
I saw a recovery on 4PDA, but currently, there are no custom ROM-s for this device, and i dont need a custom recovery until we dont have a custom rom. @Юсуф, are there any ROMs for this device on 4PDA?
Where I can find this recovery?
I saw a recovery on 4PDA,
http://4pda.ru/forum/index.php?showtopic=751678&st=840#entry54034698
but cannot download it, error 404, if anyone can post this on xda, i appreciate this, i have same problem, with my huawei y6 ii compact LYO-L21 firmware LYO-L21C577B122, i destroyed my recovery img, but phone works normally, i tried many root programm but not work root, the problem is there are a ota update to LYO-L21C577B124, but i have no functionally original recovery, please help.
if anyone find a original firmware please link this.. thanks
bootloader is unlocked
There you go, i installed this TWRP 3.0.2.0, and it works like a charm.
1: Unlock your bootloader. IT IS INDISPENSABLE! If you brick your device locked, you lost.
2: Go into fastboot (Easiest: Turn off your device, and Hold down POWER DOWN + POWER WHILE you attach the USB from the computer. The phone will go instantly into fastboot mode, it works for me)
3: Type: fastboot flash recovery twrp.img
4: The phone now should download the recovery. Pull the battery out, and restart in recovery.
Download
The file is from 4PDA.ru, i have to reupload it, because 4PDA's sign up is a PAIN. A friend of mine helped me, and it took like 2 hours.
If you like to install the stock recovery (in order to receive OTA updates), go download this img, instead of the twrp one, and install it just like TWRP.
Download
(Notice: I havent tested this recovery, to see if actually works. I'm waiting for responses)
Altough, i do not know why you need the recovery other than backing up, since there are no custom rom avaiable for this phone. (Can anyone maybe port to it?)
Rooting the Huawei Y6 II Comact (aka. the russian Honor 5A. The Chinese one is a completely different phone)
1: Unlock your bootloader. Again, it is indispensable.
2: Enable OEM unlocking in the developer settings. If you do not enable, well, you screwed up.
3: Install TWRP (see above)
4: Download UPDATE-SuperSU.zip (below)
5: Flash it via recovery
6: Reboot, and install SuperSU from Play Store, if it has not been installed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thank you very much
its works!
---------- Post added at 12:20 PM ---------- Previous post was at 12:17 PM ----------
can you please download the original recovery and boot image from the 4pda site?
same site who you downloaded the recovery
http://4pda.ru/forum/index.php?act=findpost&pid=54034698&anchor=Spoil-54034698-3
You are very welcome, i'm glad that i could help you. Feel free to ask me if you dont know how to install Xposed.
---------- Post added at 12:23 PM ---------- Previous post was at 12:21 PM ----------
abar1969 said:
thank you very much
its works!
---------- Post added at 12:20 PM ---------- Previous post was at 12:17 PM ----------
can you please download the original recovery and boot image from the 4pda site?
same site who you downloaded the recovery
http://4pda.ru/forum/index.php?act=findpost&pid=54034698&anchor=Spoil-54034698-3
Click to expand...
Click to collapse
Yes, i edited the post, it contains the stock recovery image.
thank you very much
I will test the original recovery later and post result,
hello snikerfreak
i have tested the original recovery, i can confirm that its works, and its from original LYO-L21C479B102 rom, i have installed and i not lost my root, but cannot update to LYO-L21C577B124. no problem i have root and now again the twrp recovery installed.
thanks again to you snikerfreak, and to Jemmini that create this recovery image.:good::good::good:
abar1969 said:
hello snikerfreak
i have tested the original recovery, i can confirm that its works, and its from original LYO-L21C479B102 rom, i have installed and i not lost my root, but cannot update to LYO-L21C577B124. no problem i have root and now again the twrp recovery installed.
thanks again to you snikerfreak, and to Jemmini that create this recovery image.:good::good::good:
Click to expand...
Click to collapse
Your welcome.
Do you know anything about this OTA Update? What does it contains?
Hi snikerfreak
there is a pc version, show the link, good programm :good:
http://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
Guys some one please upload the Huawei lyo-l01 (single sim ) firmware or recovery
Sorry my friend, i dont have any firmware for you.
:crying: Is there any way to get recovery img ... my phone works but only thing I cannot go to recovery mode or reset my phone

Repair DEAD(HARD BRICKED) Realme 3 | 3i Tutorial

In this tutorial we are going to Repair Realme 3 (RMX1821) MT6771 Chipset.
from being hard bricked (no charge, no recovery, no fastboot) using SP Flashtool.
with the help of Bypass Utility "MTK-bypass" to disable bootrom protection(sla and daa).
MTK-bypass credits to @k4y0z
, @chaosmaster and @xyzz on github.
REQUIREMENTS:
• Python
Download Python
The official home of the Python Programming Language
www.python.org
• libusb-win32
https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download
• Sp Flashtool
SP Flash Tool Download All versions for MediaTek Devices
SP Flash tool download is the best application to flash Stock firmware, Custom recovery and fix some extreme issues on MediaTek Android smartphones. Download SP Flash tool all versions from our official download page.
spflashtool.com
• Bypass Utility Compiled
18.9 KB file on MEGA
mega.nz
---------------------------------------------------------------
• Bypass Utility Latest Releases
Release 1.4.1 · MTK-bypass/bypass_utility
Improve handshake reliability
github.com
• Exploits Latest Releases
Release 1.5 · MTK-bypass/exploits_collection
mt6261 mt6572 mt6580 mt6582 mt6735 mt6737 mt6739 mt6755 mt6757 mt6761 mt6763 mt6765 mt6768 mt6771 mt6785 mt6799 mt6873 mt8127 mt8163 mt8173 mt8695
github.com
• Realme 3 (rmx1821) Flashtool Firmware link soon
> I will upload the realme 3 firmware with Scatter File and Auth File for Third Party Flashtool like SP Flashtool soon, but if you have an official firmware of realme 3 with Scatter and Auth File you can use it no matter what version it is.
> If you know how to extract an OFP file, you can download this realme 3|3i firmware and extract the OFP file.
https://fileload.coloros.com/30842RMX1821EX_11_C.17_201117_cb5665f2.zip
> Video Tutorial on how to Extract OPPO | REALME firmware (OFP file)
VIDEO TUTORIAL
TEXT TUTORIAL
INSTALLATION:
• Install Python (tick checkbox "Add Python X.X to PATH") and proceed.
( if you are using windows 10, Download and Install Python 3.9 through Microsoft Store )
• Install lib-usb_win32
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click Next>Next> until you see the next image
Click Finish and Launch Lunch Filter Wizard
Choose the "Install a device filter" and click next
You will see this device selection.
Now you will need to connect you phone with power off to computer.
> Hold all the buttons and connect to the computer (wait until you see Mediatek USB Port in libusb Device selection and Install)
(note: you have to select and install it very quick, because the phone disconnect in just a few seconds)
> Wait until it shows this (Click OK and close libusb and Disconnect your phone)
INITIALIZATION:
• Extract Bypass Utility, and go to extracted folder
> type "cmd" in the address bar and hit enter
> in cmd console install (Install pyusb, pyserial, json5)
by typing: pip install pyusb pyserial json5
> after that bypass mtk
by typing: python main.py
> when you see "Waiting for bootrom" , you need to connect your phone again (Holding all button and plug it into your computer and wait until it recognized.)
you should have this following output. do not close this window and remember the Found port of you phone
as you can see my port is = COM7
DO NOT DISCONNECT YOUR PHONE FROM COMPUTER THIS TIME
FLASHING FIRMWARE:
• Extract SP Flashtool and Realme 3 Firmware
• Open flashtool.exe and click Options>Connection
and tick AURT instead of USB.
Select the COM port of the phone which is COM7 in my case
then close Option Window
• Now In Flashtool choose Scatter-File from the Extracted Firmware of Realme 3
(wait until it finished the Processing)
• After that choose Authentication File
• After loading Scatter and Auth File Click Download
It should start downloading the firmware to you phone now without any error.
(wait until it finished the download.)
When finished downloading you get a check windows indicating that the flash was successful!
Thats it Congratulations! You may now disconnect your phone from your computer and POWER ON.
your DEAD [HardBricked] Realme 3 is now Alive!
(Note: This method is applicable to any MTK devices with SoC mt6735, mt6750, mt6765, mt6771, mt6785, mt8127, mt8163, mt8173, mt8695)
For more updates about MTK-Bypass visit the official github page @
MTK-bypass
MTK-bypass has 8 repositories available. Follow their code on GitHub.
github.com
all the tools and utility is not mine. credits to the developer.
Original Bypass Tool xdaThread
[MOD][DEV] MediaTek / MTK - Auth Bypass (SLA/DAA) - Utility
As some of you have already noticed, a couple of weeks ago @Dinolek and I published a utility, that allows bypassing authentication on MTK devices. The tool is based on an exploit dubbed kamakiri, which was originally found by @xyz` and released...
forum.xda-developers.com
special thanks to @popoff-r for mentioning about a thread of repairing MTK devices.
Thanks
fawazahmed0 said:
Thanks
Click to expand...
Click to collapse
so its you , i thought the two in the credits in your github bypass_utility is one who develop it. im sorry sir. im not really familliar where to see the owner of the work it github. im really sorry for not mentioning your name in this. gotta edit now. You are Great sir!
ATDteam said:
so its you , i thought the two in the credits in your github bypass_utility is one who develop it. im sorry sir. im not really familliar where to see the owner of the work it github. im really sorry for not mentioning your name in this. gotta edit now. You are Great sir!
Click to expand...
Click to collapse
Thank you for putting this altogether, this should speed up the development work for this phone(kernel etc), as people don't have to go to service center for hard brick.
Also I want to tell you, I shouldn't get the credits for bypass_utility, the two people you mentioned should be getting the credits, I just forked(copy/cloned) the repository.
I assume you are new to github, anyone can fork(copy/clone) a repository by clicking on fork button
You can differentiate whether a repository is forked(copied) or original by seeing on the top left side.
Thanks
fawazahmed0 said:
Thank you for putting this altogether, this should speed up the development work for this phone(kernel etc), as people don't have to go to service center for hard brick.
Also I want to tell you, I shouldn't get the credits for bypass_utility, the two people you mentioned should be getting the credits, I just forked(copy/cloned) the repository.
I assume you are new to github, anyone can fork(copy/clone) a repository by clicking on fork button
View attachment 5205247
You can differentiate whether a repository is forked(copied) or original by seeing on the top left side.
View attachment 5205251
Thanks
Click to expand...
Click to collapse
Thank you so much that was a very helpful information.

			
				
How to fix this error sir..
What Error?, please provide screenshot of the error, if you can't explain it.
ATDteam said:
What Error?, please provide screenshot of the error, if you can't explain it.
Click to expand...
Click to collapse
Tihis sir
What Error?, please provide screenshot of the error, if you can't explain it.
Al Djufri said:
Tihis sir
View attachment 5207505
Click to expand...
Click to collapse
try to uninstall python and reinstall again, also download the bypass_utility, the one that i attached in this thread.
and try again. make sure your usb cable is working properly, it seems that your device does not read properly by the utility. change your cable if posible. Download python 3.9, if still doest work. try using windows 10 OS.
18.9 KB file on MEGA
mega.nz
ATDteam said:
What Error?, please provide screenshot of the error, if you can't explain it.
try to uninstall python and reinstall again, also download the bypass_utility, the one that i attached in this thread.
and try again. make sure your usb cable is working properly, it seems that your device does not read properly by the utility. change your cable if posible. Download python 3.9, if still doest work. try using windows 10 OS.
18.9 KB file on MEGA
mega.nz
Click to expand...
Click to collapse
Reinstalling python
Reinstalling lib libusb
Changing usb cable
Changing port usb
Change pc, i mean borrow a pc from my friend
Changing spflashtool, same problem sir?
Do you have telegram account
thanks it works thanks for saving my phone
Its not the same in your first screenshot you reach "Disabling protection" but in the 2nd one only the utility found your phone..., did you release all the buttons emmidiately after your computer detects your phone phone? It is important that you release emmidiately. Did you try to use windows 10.? Sorry I dont have telegram.
Al Djufri said:
Reinstalling python
Reinstalling lib libusb
Changing usb cable
Changing port usb
Change pc, i mean borrow a pc from my friend
Changing spflashtool, same problem sir?
Do you have telegram accountView attachment 5208303
Click to expand...
Click to collapse
XxRRSxX said:
thanks it works thanks for saving my phone
Click to expand...
Click to collapse
Thanks for using this thread as your guide, but credits is to the developers of the Utility.
ATDteam said:
Its not the same in your first screenshot you reach "Disabling protection" but in the 2nd one only the utility found your phone..., did you release all the buttons emmidiately after your computer detects your phone phone? It is important that you release emmidiately. Did you try to use windows 10.? Sorry I dont have telegram.
Click to expand...
Click to collapse
I'm trying to with my friend pc(windows 10) using latest python and same error sir..
Always Immediately release my button when pc detection my device.. but same error
( SOLVED )
you must be use windows 10
Use latest python version
Use latest SpFlash tool version
And don't forget to chek libusb instalation
Check via cmd "pip install libusb" and "pip install libusb1"
And try to use command "python main.py"
Sorry for my English..
Thanks sir..
Al Djufri said:
( SOLVED )
you must be use windows 10
Use latest python version
Use latest SpFlash tool version
And don't forget to chek libusb instalation
Check via cmd "pip install libusb" and "pip install libusb1"
And try to use command "python main.py"
Sorry for my English..
Thanks sir..
View attachment 5208681
Click to expand...
Click to collapse
Nice thats great! sometimes you really need to be on Trial and Error before you achieve what you want. happy for you. Thank you for using my thread as guide, Credits to the developers of the utility. and you have a good english. mine is bad. :-D
Anyone who facing problem when bootrom check, you have to flash first time or it will show error. Otherwise you have to uninstall and reinstall libusb.exe and others.
Ok, thanks to ATDTEAM, very much, I bricked by patching boot image with magisk and flashing it, successfully flashed stock rom .ofp with SP Flash tool, not only this , I itentionally flashed another version , and it worked to, thnx to the bypass utility, it generates questions, the realme provides ozip files, so where are .ofp files coming from, or where we can get it, and... Fawazahmed0 , I am unable to flash twrp, I tried everything I could, I am on updated Android 10 c.19 now, so I can't flash custom recovery or root it... I can't even rollback bcoz I unable to find the older version ofp files, the ozip files just don't install, so please help for rooting Android 10, You have solved a major hurdle by introducing the method of bypass sp tool flashing but, the next step of flashing custom recovery and then rooting awaits... Pls help/ guide, Thnx...
Thanks brother, I've recently unbricked my device

Hardbricked Mi 10T Pro / how to unlock or flash stock rom

hi there
a friends mi10t pro is bricked after a wrong installed update (don't ask my how he did that - ha's a beginner)...
unlocking is not working as i can boot into miui-recovery and fastboot but cannot unlock with my own account: "sorry, couldn't unlock more devices by this account this year" - awh xiaomi, great...!
then
edl mode is working somehow via reboot-edl command, but the screen stays black - anyway, it recognizes the device via "adb devices" and in sideload-state...
then
flashing stock rom (apollo_global_images_V13.0.6.0.SJDMIXM_20220822.0000.00_12.0_global) is running until i get
$fastboot -s db380550 getvar product 2>&1 |findstr /r /c: "^product: *apollo" || missmatching image and device
Click to expand...
Click to collapse
delete these commands out of any flash.bat won't help anything...
any chance to bring that thing back to life again?
am i wrong with edl-mode, that this method can temp-unlock the device?
thanks guys!
axanon said:
hi there
a friends mi10t pro is bricked after a wrong installed update (don't ask my how he did that - ha's a beginner)...
unlocking is not working as i can boot into miui-recovery and fastboot but cannot unlock with my own account: "sorry, couldn't unlock more devices by this account this year" - awh xiaomi, great...!
then
edl mode is working somehow via reboot-edl command, but the screen stays black - anyway, it recognizes the device via "adb devices"
then
flashing an stock rom (apollo_global_images_V13.0.6.0.SJDMIXM_20220822.0000.00_12.0_global) is running until i get
delete these commands out of any flash.bat won't help anything... so...
any chance to bring that thing back to life again?
thanks guys!
Click to expand...
Click to collapse
If the bootloader is unlocked used Miflash.
Read the tutorial carefully.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
can cause problems:
"apollo_global_images_V13.0.6.0.SJDMIXM_20220822.0000.00_12.0_global" too long try rename it like V1306MIXM.
path must be C:/miflash/V1306MIXM
NOSS8 said:
If the bootloader is déverrouillé utilisé Miflash.
Lisez attentivement le tuto.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
can cause problems:
"apollo_global_images_V13.0.6.0.SJDMIXM_20220822.0000.00_12.0_global" too long try rename it like V1306MIXM.
path must be C:/miflash/V1306MIXM
Click to expand...
Click to collapse
this is not working... exact same errors, even if i use the shortened path, like you describe.
axanon said:
this is not working... exact same errors, even if i use the shortened path, like you describe.
Click to expand...
Click to collapse
Can you post the Miflash log.txt?
(In the Miflash/log folder, the last one with the biggest size.)
NOSS8 said:
Can you post the Miflash log.txt?
(In the Miflash/log folder, the last one with the biggest size.)
Click to expand...
Click to collapse
of course:
[09:11:40]:GetUserInfo
[09:12:01]:lsusb path:"C:\miflash\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[09:12:01]:ls ubs :Intel(R) Active Management Technology - SOL (COM3)
[09:12:01]ie angegebene Umwandlung ist ungültig. bei XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems)
[09:12:05]:add device db380550 index 0
[09:12:06]pen RegistryKey Software\XiaoMi\MiFlash\
[09:12:07]:driver oem16.inf exists,uninstall,reuslt True,GetLastWin32Error
[09:12:08]:install driver C:\miflash\Source\ThirdParty\Google\Driver\android_winusb.inf to C:\WINDOWS\INF\oem16.inf,result True,GetLastWin32Error
[09:12:08]:set RegistryKey value:android_winusb.inf--oem16.inf
[09:12:08]:mkdir "C:\Users\luzius\.android"
[09:12:08]utput:Ein Unterverzeichnis oder eine Datei mit dem Namen "C:\Users\luzius\.android" existiert bereits.
[09:12:08]: echo 0x2717 >>"C:\Users\luzius\.android\adb_usb.ini"
[09:12:08]utput:
[09:12:08]pen RegistryKey Software\XiaoMi\MiFlash\
[09:12:08]:install driver C:\miflash\Source\ThirdParty\Nvidia\Driver\NvidiaUsb.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[09:12:08]pen RegistryKey Software\XiaoMi\MiFlash\
[09:12:09]:install driver C:\miflash\Source\ThirdParty\Microsoft\Driver\tetherxp.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[09:12:09]pen RegistryKey Software\XiaoMi\MiFlash\
[09:12:10]:install driver C:\miflash\Source\ThirdParty\Microsoft\Driver\wpdmtphw.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[09:12:10]pen RegistryKey Software\XiaoMi\MiFlash\
[09:12:10]:driver oem98.inf exists,uninstall,reuslt False,GetLastWin32ErrorDas System kann die angegebene Datei nicht finden
[09:12:11]:install driver C:\miflash\Source\ThirdParty\Qualcomm\Driver\qcser.inf to C:\WINDOWS\INF\oem54.inf,result True,GetLastWin32Error
[09:12:11]:set RegistryKey value:qcser.inf--oem54.inf
[09:12:16]:lsusb path:"C:\miflash\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[09:12:16]:ls ubs :Intel(R) Active Management Technology - SOL (COM3)
[09:12:16]ie angegebene Umwandlung ist ungültig. bei XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems)
[09:12:20]:FlashingDevice.flashDeviceList.Remove db380550
[09:12:20]:add device db380550 index 0
[09:12:20]:dl not exit ffufilelist
[09:12:20]:Thread start,thread id 19,thread name db380550
[09:12:20]:start process id 22180 name cmd
Click to expand...
Click to collapse
axanon said:
of course:
Click to expand...
Click to collapse
It's not that one, it starts like that.
Spoiler: Log
[14:42:01 eeab043a]:MiFlash 2020.3.14.0
[14:42:01 eeab043a]:vboytest index:1
[14:42:01 eeab043a]:idproduct: 53261 idvendor: 6353
[14:42:01 eeab043a]:Thread id:9 Thread name:eeab043a
[14:42:01 eeab043a]:image path:\F2\prog\MiFlash2020-3-14-0\V13.0.9.0.SKDEUXM
NOSS8 said:
It's not that one
Click to expand...
Click to collapse
so this:
[09:12:20 db380550]:MiFlash 2021.2.26.0
[09:12:20 db380550]:vboytest index:0
[09:12:20 db380550]:Thread id:18 Thread name:
[09:12:20 db380550]:image path:C:\miflash\V1306MIXM
[09:12:20 db380550]:env android path:"C:\miflash\Source\ThirdParty\Google\Android"
[09:12:20 db380550]:script :C:\miflash\V1306MIXM\flash_all.bat
[09:12:20 db380550]hysical Memory Usage:4050944 Byte
[09:12:20 db380550]:start process id 22180 name cmd
[09:12:20 db380550]:info1:$fastboot -s devicename getvar product 2>&1 | findstr /r /c:"^product: *apollo" || echo Missmatching image and device
[09:32:20 db380550]:error: flash timeout
[09:32:25 db380550]:flashSuccess False
[09:32:25 db380550]:isFactory False CheckCPUID False
[09:32:25 db380550]:before:flashSuccess is False set IsUpdate:True set IsDone True
[09:32:25 db380550]:after:flashSuccess is False set IsUpdate:false set IsDone true
Click to expand...
Click to collapse
axanon said:
so this:
Click to expand...
Click to collapse
"[09:32:20 db380550]:error: flash timeout"
is the only error.
Change USB2 port.
Don't use Miflash, open the rom folder and run the bat file "flash_all".
NOSS8 said:
"[09:32:20 db380550]:error: flash timeout"
is the only error.
Change USB2 port.
Don't use Miflash, open the rom folder and run the bat file "flash_all".
Click to expand...
Click to collapse
changed to another USB2 port, reconnect and execute "flash_all" - turns out with the same error...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
axanon said:
changed to another USB2 port, reconnect and execute "flash_all" - turns out with the same error...
Click to expand...
Click to collapse
have you run it as administrator?
That's all the command shows?
NOSS8 said:
have you run it as administrator?
That's all the command shows?
Click to expand...
Click to collapse
yes, i run it as admin (and tested it without) - turns out like this. looks like it would be stuck at a certain point... funny, because with *adb devices" the device shows up as "db380550 sideload"...
axanon said:
yes, i run it as admin (and tested it without) - turns out like this. looks like it would be stuck at a certain point... funny, because with *adb devices" the device shows up as "db380550 sideload"...
Click to expand...
Click to collapse
The bootloader is unlocked,right?
NOSS8 said:
The bootloader is unlocked,right?
Click to expand...
Click to collapse
no, not possible to unlock - as in post #1 described
axanon said:
no, not possible to unlock - as in post #1 described
Click to expand...
Click to collapse
Sorry, I didn't understand that, everything we've done is useless in this case.
BTW: post #2
try
Not for your device but the instructions are the same.
Important :do not download the update but the rom you had before.
https://forum.xda-developers.com/t/...ocked-bootloader-mi-assistant-whyred.3798165/
Rom: https://xiaomifirmwareupdater.com/miui/surya/
Mi assistant 4 https://mega.nz/file/zpURDRbD#T2qfGO7j6F90brJ033xfkSZl6fyR2Yih9zrdjxwIOM8
I know you have tried but may these links help to resolve the error.
NOSS8 said:
Sorry, I didn't understand that, everything we've done is useless in this case.
BTW: post #2
try
Not for your device but the instructions are the same.
Important :do not download the update but the rom you had before.
https://forum.xda-developers.com/t/...ocked-bootloader-mi-assistant-whyred.3798165/
Rom: https://xiaomifirmwareupdater.com/miui/surya/
Mi assistant 4 https://mega.nz/file/zpURDRbD#T2qfGO7j6F90brJ033xfkSZl6fyR2Yih9zrdjxwIOM8
I know you have tried but may these links help to resolve the error.
Click to expand...
Click to collapse
this method worked quite well... it counts to 99% and installing around 15 minutes. then the mi assistant force closed and the phone is rebooting - ends in black screen but windows is recgnizing the phone somehow...
Your browser is not able to display this video.
axanon said:
this method worked quite well... it counts to 99% and installing around 15 minutes. then the mi assistant force closed and the phone is rebooting - ends in black screen but windows is recgnizing the phone somehow...
Click to expand...
Click to collapse
Before trying this tool, go to the recovery and erase the data then try to boot into the system.
Another tool (choose bricked device).
it seems to me that this tool displays the rom you are on and automatically downloads the version.
https://www.xiaomitool.com/V2/
NOSS8 said:
Another tool (choose bricked device).
it seems to me that this tool displays the rom you are on and automatically downloads the version.
https://www.xiaomitool.com/V2/
Click to expand...
Click to collapse
i did try tescaris tool over 10 times... but today - i don't know why i did this different:
IT WORKED!
the only thing, what i try different was, i did not choose "apollo" on the device list. this time i went with "apollo_factory". the flash procedure did all well, at the end, i've got an error but the device booted correctly!
axanon said:
i did try tescaris tool over 10 times... but today - i don't know why i did this different:
IT WORKED!
the only thing, what i try different was, i did not choose "apollo" on the device list. this time i went with "apollo_factory". the flash procedure did all well, at the end, i've got an error but the device booted correctly!
Click to expand...
Click to collapse
It was the firmware to choose.
To return to the original problem, how could he have installed a different rom with the bootloader locked!!!!
NOSS8 said:
It was the firmware to choose.
To return to the original problem, how could he have installed a different rom with the bootloader locked!!!!
Click to expand...
Click to collapse
i don't really know... i think he tried to dirtyflash a custom rom
however:
as i could use the device now for some installing after a restart it stucks on mi-boot-logo... damnit!
Try remove data.

How to unlock bootloader of vivo MTK devices?

Unlocking bootloader on vivo MTK devices
This thread is intended for vivo MTK devices only. However you might have seen some of the threads for unlocking vivo bootloader but it might not work for you. So let's begin our tutorial
!! WARNING !!
THIS STEP WILL ERASE YOUR USERDATA, SO MAKE SURE YOU HAVE BACKED UP ALL YOUR DATA BEFORE EXECUTING THIS​Requirements:
This is needed to make it work!
1. MTK Driver
2. Python (latest)
3. UsbDK
4. MTKClient
5. Zip extractor like 7zip
Set up all the requirements:
1. Install Python
1.1. Open Python that you have download​1.2. Tick a box called "add to PATH"​1.3. Install​2. Install UsbDK
2.1. Make sure you have downloaded UsbDk according to your architecture​2.2. Double click the installation file and install​3. Install MediaTek Drivers
3.1. Download zip that I attach on this thread​3.2. Use your zip extractor app and extract the zip​3.3. After extract, you will see 3 files inside, choose "cdc-acm.inf" and right click​3.4. Select "Install drivers" and follow all instructions​4. Setup MTKClient
4.1. They're many version releases on the github, download the source code zip from the latest version​4.2. Use your extractor app and extract it into a folder​4.3. Go into that folder and open command prompt from there​4.4. Simply type "pip3 install -r requirements.txt" on the cmd and enter. Wait for it to finish​4.5. Close the cmd​
Steps to unlock:
1. Go to mtkclient folder and open cmd from the folder
2. Type "python3 mtk da seccfg unlock"
3. Prepare your phone, make sure it's turn off
4. Connect your phone to PC with volume combination, hold both volume button and connect
5. Hold it until you heard usb connection sound and release it
6. Wait until it succeed
7. If successful, disconnect your device and turn it on
8. You will see a message saying "Orange state bla bla", ignore it
9. If it keeps rebooting, just wait for it to enter recovery and it will ask you to factory reset your device
10. Factory reset it and you're done!
You've finally unlocked your vivo bootloader
Tested devices:
1. vivo Y20 2021/Y12s (PD2036F)
2. vivo Y17/Y15/Y12 (PD1901)
3. vivo Y1s (PD2014F)
4. vivo Y91C (MTK)(PD1818HF)
However vivo have patched the BROM mode(something like download mode on mtk) on the latest update. But I have solution for that issue!
NeonzGamingYT said:
However vivo have patched the BROM mode(something like download mode on mtk) on the latest update. But I have solution for that issue!
Click to expand...
Click to collapse
way
NeonzGamingYT said:
However vivo have patched the BROM mode(something like download mode on mtk) on the latest update. But I have solution for that issue!
Click to expand...
Click to collapse
Seems like you don't?
so i was trying to use mtk client with your command. i'm not sure why my windows don't recognize python3 as installed and redirected me to microsoft store, so i used just python command which should ran python 3.11.2 on my pc. But when i did that it didn't really let me do that saying that "da" flag not found
Code:
mtk client\mtkclient-1.52>python mtk da seccfg unlock
usage: mtk [-h]
{printgpt,gpt,r,rl,rf,rs,ro,w,wf,wl,wo,e,es,footer,reset,dumpbrom,dumppreloader,payload,crash,brute,gettargetconfig,peek,stage,plstage,xflash}
...
mtk: error: argument cmd: invalid choice: 'da' (choose from 'printgpt', 'gpt', 'r', 'rl', 'rf', 'rs', 'ro', 'w', 'wf', 'wl', 'wo', 'e', 'es', 'footer', 'reset', 'dumpbrom', 'dumppreloader', 'payload', 'crash', 'brute', 'gettargetconfig', 'peek', 'stage', 'plstage', 'xflash')
MTK Flash/Exploit Client V1.52 (c) B.Kerler 2018-2021
Also i'm trying to make it work with vivo v25e which uses Mediatek MT8781 Helio G99 (6nm) (if you can believe description)
if i run adb toolkit it shows me this info for my phone
Code:
Device: V2201
Model: V2201
Brand: vivo
Android: 13
Firmware: TP1A.220624.014
Security Patch: 2023-02-01
also this is behaviour for my phone on the 4ths step
4. Connect your phone to PC with volume combination, hold both volume button and connect
Click to expand...
Click to collapse
at first it shows first line in device manager then second and then disappears at all, is this normal behaviour?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there any chances for me to unlock bootloader or i should just give up for now? Also i'm very sorry if i miss something obvious.
twq_bought_a_shit_phone said:
so i was trying to use mtk client with your command. i'm not sure why my windows don't recognize python3 as installed and redirected me to microsoft store, so i used just python command which should ran python 3.11.2 on my pc. But when i did that it didn't really let me do that saying that "da" flag not found
Code:
mtk client\mtkclient-1.52>python mtk da seccfg unlock
usage: mtk [-h]
{printgpt,gpt,r,rl,rf,rs,ro,w,wf,wl,wo,e,es,footer,reset,dumpbrom,dumppreloader,payload,crash,brute,gettargetconfig,peek,stage,plstage,xflash}
...
mtk: error: argument cmd: invalid choice: 'da' (choose from 'printgpt', 'gpt', 'r', 'rl', 'rf', 'rs', 'ro', 'w', 'wf', 'wl', 'wo', 'e', 'es', 'footer', 'reset', 'dumpbrom', 'dumppreloader', 'payload', 'crash', 'brute', 'gettargetconfig', 'peek', 'stage', 'plstage', 'xflash')
MTK Flash/Exploit Client V1.52 (c) B.Kerler 2018-2021
Click to expand...
Click to collapse
i got the same error
First i think if you got vivo device is most likely patched. If not what version of mtk exploit is it using
I see you're using security patch dated 2023-02-01 which most likely won't work
ko_hi said:
First i think if you got vivo device is most likely patched. If not what version of mtk exploit is it using
I see you're using security patch dated 2023-02-01 which most likely won't work
Click to expand...
Click to collapse
honestly i was trying to lock the bootloader just so i won't touch these stuff and my phone is not even vivo it's oppo a5s

Categories

Resources