LeEco Le Pro 3 - How to TWRP Recovery & Root - LeEco Le Pro3 Guides, News, & Discussion

LeEco Le Pro 3 - How to TWRP Recovery & Root - LeEco Le Pro3 Guides, News, & Discussion

Hey here you go with the tutorial how to flash the TWRP Recovery & Root the Le Pro 3 device.
{
"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"
}
1. Requirement & Downloads:
-minimal ADB and Fastboot
-Download TWRP Image (Stock Recovery included) (Thx to DJ-Tumor)
-Download SuperSU (Root)
-activate USB debugging in developer options
2. Unlock Bootloader:
-First you have to enable developer options. Then in developer options under debugging section turn on USB debugging
-boot the Le Pro 3 into Fastboot Mode (hold power and volume down)
-connect the Le Pro 3 with your PC
-start minimal ADB & Fastboot
2.1 Type in CMD to unlock Bootloader:
Code:
fastboot oem unlock-go
The result is:
...
OKAY [ 0.008s]
finished. total time: 0.009s
2.2 Type in CMD to check if it worked:
Code:
fastboot oem device info
Thre result must be:
...
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.084s
3. Flash TWRP recovery
-unpack the downloaded Pro3_EUI5.8_TWRP.zip and copy the recovery_twrp.img into the minimal ADB Folder
-enable developer options. Then in developer options under debugging section turn on USB debugging
-boot the Le Pro 3 into Fastboot Mode (hold power and volume down)
-connect the Le Pro 3 with your PC
-start minimal ADB & Fastboot
3.1 Type in CMD to flash the TWRP Recovery:
Code:
fastboot flash recovery recovery_twrp.img
Thre result must be:
target reported max download size of 536870912 bytes
sending 'recovery' (47052 KB)...
OKAY [ 1.345s]
writing 'recovery'...
OKAY [ 0.331s]
finished. total time: 1.677s
4. Rooting Le Pro 3
-Download SuperSU root zip file and place it on internal storage
-Boot into TWRP Recovery with Power + Volum Up
-swipe right to the first TWRP screen
-switch to your language in TWRP
-Flash SuperSU.zip
-Reboot
-Done
5. Check Root:

+1
أرسلت من htc 10 بإستخدام تاباتلك

I've tried to sideload the supersu.zip via "fastboot sideload supersu.zip" but doesn't work. Then only the help commands comes up.

Im getting mine soon from alibaba rooted, with multilanguage rom and google apps pre-installed

as much as I know...there is no multilingual ROM yet.

Google Apps are not the problem. I want to root because then I could use the apps with morelocale2 in my language.

i need a root too because i want german language .
i got a question : how can i get the playstore on this phone?
and how get the apps in german from playstore .

just wait...mine if coming by end of month...3 weeks is a lot of time for android community to find ways.
I want German language too

Everyone in the waiting .. and we need rom for most countries of the world .. the device in the United States there will be rapid developments
أرسلت من HTC 10 بإستخدام تاباتلك

German unboxing and hands-on video from me. But only in german, sorry.
https://youtu.be/V-jofeuZR9U

Soulfly999 said:
German unboxing and hands-on video from me. But only in german, sorry.
https://youtu.be/V-jofeuZR9U
Click to expand...
Click to collapse
Is it possible. Video recording with devices for comparing the size of the machine..
Thanks
أرسلت من HTC 10 بإستخدام تاباتلك

I'm writing a full Review later in my blog an compare it with my Honor V8 and Redmi 3 Pro.

Root? Custom Rom? CM?
Hi there. I also play with the idea of buying a Leeco pro 3. But if there is no root and no custom Rome, then I tend to tend to the Oneplus 3. With a preinstalled software in Chinese and English I can start little. Need something in German .... apologize for my humble English

Soulfly999 said:
I'm writing a full Review later in my blog an compare it with my Honor V8 and Redmi 3 Pro.
Click to expand...
Click to collapse
I bought one too, I'm out of Xiaomi for Leeco the camera, audio and multi-tasking are good?
thanks

Root for leeco le pro 3 on this link.
http://www.sadroid.com/root-leeco-le-pro-3-5-minutes/
أرسلت من HTC 10 بإستخدام تاباتلك

yousef955 said:
Root for leeco le pro 3 on this link.
http://www.sadroid.com/root-leeco-le-pro-3-5-minutes/
أرسلت من HTC 10 بإستخدام تاباتلك
Click to expand...
Click to collapse
Do you have try this ? Or someone else ?

tristabeau said:
Do you have try this ? Or someone else ?
Click to expand...
Click to collapse
No .. Device I have not got so far .. researched and found this link.
أرسلت من HTC 10 بإستخدام تاباتلك

yousef955 said:
No .. Device I have not got so far .. researched and found this link.
أرسلت من HTC 10 بإستخدام تاباتلك
Click to expand...
Click to collapse
Ok thx If someone test this, I am curious ^^

I've testet it and i would say it's just an app to install bloatware. My Le Pro 3 is only connected with a testacount so no problem for me tot test it.
So then one of my partner shops tell me, there is a multilanguage version aviailable but i don't know if it's a own device or just a rom?
@yousef955 Comparison dimension you could find and discuss now here
http://forum.xda-developers.com/le-pro3/how-to/leeco-le-pro-3-dimension-comparison-t3478368

Thank you very much ?
أرسلت من HTC 10 بإستخدام تاباتلك

Related

[Utility] MotoFlashPro

{
"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"
}
- = MotoFlashPro = -
Utility to flash for Motorola devices on Qualcomm processors.
Instruction
Pre-extract the firmware archive to either an adb&fastboot driver folder or another location on your PC if you are catching firmware from any drive in the system.
Connect the device to your PC and set it to fastboot mod.
1. Select in the program window:
- flashfile.xml for full flashing with removal of all user data;
- servicefile.xml for flashing with all user data saved.
2. Press "Start Flash" button to start flashing.
3. When the firmware installation is finished, the device will be automatically rebooted.
The program has the following additional functions:
- reboot-bootloader - bootloader mode reboot;
- clear bootmode - fastboot mode cleaning;
- erase modemst 1/2 - modem cleaning;
- erase userdata+cache - user data and cache cleansing;
- getvar all - device information output;
- oem hw - output of information about the device equipment.
Download in Attached Files
Changelog v1.0.1:
- code optimization;
- improved output of getvar all and oem hw;
- fine aesthetic fixtures.
For the program, we thank
serg_gangubas

Thx!

+Rep
Thanks mate, this tool saved me..
I bricked my device tried Rescue and Smart Assistant tool but that one is ****..
with this tool I was able to unbrick the phone also successfully flash Brazil firmware with android 11.

Glad I could help you!

Hi, do you know how to change the software update channel?

No way. It's not Samsung. Installing firmware from another modification of the phone does not change the software update region.

ilia3367 said:
No way. It's not Samsung. Installing firmware from another modification of the phone does not change the software update region.
Click to expand...
Click to collapse
Thx mate. I was already assuming that . However there are lot of rumours regarding that. Some people are saying that it's possible..

Thanks for this! I'm rooted so the OTA updates are failing of course. I'm not 100% on what is meant by user data. Will the servicefile.xml method allow me to install (update) the latest security patch like an OTA update, not having to setup my phone again?

Mace68 said:
Thanks for this! I'm rooted so the OTA updates are failing of course. I'm not 100% on what is meant by user data. Will the servicefile.xml method allow me to install (update) the latest security patch like an OTA update, not having to setup my phone again?
Click to expand...
Click to collapse
Does anyone know the answer to this?

如果我想從高版本降級到低版本，需要解鎖引導加載程序嗎？？

Hello friends, could someone clarify for me well how is the rooting process? I am from Argentina and I do not speak English, I use the translator and we already know what that means. I would like to know the step by step to achieve the root of the team

ilia3367 said:
¡Me alegro de poder ayu
Click to expand...
Click to collapse
ilia3367 said:
¡Me alegro de poder ayudarte!
Click to expand...
Click to collapse
TengoTengo el Moto g8 plus como venía de fábrica no le he hecho nada podía instalarlo de antemano muchas gracias saludos de sonora

Hola. Te conviene buscar en tu modelo de celular. Si ya abriste el bootloader busca en Chrome como rootera moto g8 Plus o busca los foros para ese modelo.

Cris19752008 said:
Hola. Te conviene buscar en tu modelo de celular. Si ya abriste el bootloader busca en Chrome como rootera moto g8 Plus o busca los foros para ese modelo.
Click to expand...
Click to collapse

Thanks so much, works fine for me, the flash files option!

kyo11111 said:
如果我想從高版本降級到低版本，需要解鎖引導加載程序嗎？
Click to expand...
Click to collapse
本人亲测降级成功
[Guides]Downgrade from android 11 to 10
Part1:Unlock Bootlaoder step1: download and install Rescue and Smart Assistant Tool https://www.motorola.com/us/rescue-and-smart-assistant/p step2: download and install USB drivers...
forum.xda-developers.com

How do we get the most current firmware on our PC? Does motorola have a repository of the stock firmware? Can it somehow be gotten through Rescue and Smart Assistant?

cruban said:
Thx!
Click to expand...
Click to collapse
I installed : XT2201-1_HIPHI_RETEU_12_S1SH32.55-8-8_subsidy-DEFAULT_regulatory-DEFAULT_cid50_CFC.xml (European firmware Moto edge 30 pro) - Works with all installed Google applications. Multilanguage. No Chineze aplication. https://mirrors.lolinet.com/firmware/moto/hiphi/official/ RETEU
1. First :Android-SDk - WIN platform tools.
2. Extract XT2201-1_HIPHI_RETEU in c:\platform tools after install Android SDK.
3.Copy and paste "bootloader, radio" from chinese firmware in folder.
4. Open MotoFlashPro v1_0_1
5. Select "flashfile"
6 flash
(Phone need to have unlock bootloader)

Help me pls Blank flash error for me
C:\adb\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.86
[ -0.000] Opening device: \\.\COM4
[ 0.004] Detecting device
[ 0.006] ...cpu.id = 286 (0x11e)
[ 0.006] ...cpu.sn = 3644946228 (0xd9417734)
[ 0.006] Opening singleimage
[ 0.007] Loading package
[ 0.009] ...filename = pkg.xml
[ 0.011] Loading programmer
[ 0.012] ...filename = programmer.elf
[ 0.012] Sending programmer
[ 0.072] ReadFile() failed, GetLastError()=0
[ 0.372] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.378] ERROR: sahara_download()->general error
[ 0.380] Check qboot_log.txt for more details
[ 0.381] Total time: 0.382s
FAILED: qb_flash_singleimage()->sahara_download()->general error
C:\adb\blankflash>pause
Premere un tasto per continuare . . .
Help

ilia3367 said:
View attachment 5259539
- = MotoFlashPro = -
Utility to flash for Motorola devices on Qualcomm processors.
Instruction
Pre-extract the firmware archive to either an adb&fastboot driver folder or another location on your PC if you are catching firmware from any drive in the system.
Connect the device to your PC and set it to fastboot mod.
1. Select in the program window:
- flashfile.xml for full flashing with removal of all user data;
- servicefile.xml for flashing with all user data saved.
2. Press "Start Flash" button to start flashing.
3. When the firmware installation is finished, the device will be automatically rebooted.
The program has the following additional functions:
- reboot-bootloader - bootloader mode reboot;
- clear bootmode - fastboot mode cleaning;
- erase modemst 1/2 - modem cleaning;
- erase userdata+cache - user data and cache cleansing;
- getvar all - device information output;
- oem hw - output of information about the device equipment.
Download in Attached Files
Changelog v1.0.1:
- code optimization;
- improved output of getvar all and oem hw;
- fine aesthetic fixtures.
For the program, we thank
serg_gangubas
Click to expand...
Click to collapse
Hi i downloaded the MotoFlash Pro etc etc it looks good, i have not flashed Moto G82 yet alto bootloader Unlocked and Root Magisk, but earlier today saw the RSD Lite Tool v RSD_Lite_v6.2.4 tool, it appears this is for Windows 10 & older, i am on W11 Pro, which do you thing is safer and would wiork, i did post on the MOTO G82 device section there is very little activity there, i saw some of ther vids you did on YouTube, regards Durban

crDroid (10) GSI ported to HUAWEI P10 Lite (Tested On WAS-LX1A)

Hi guys, i ported the crDroid gsi from here.
I removed the unnecessary files from the rom, and included gapps.
And AIO fixes thanks to @DarkJoker360.
Install steps are easy.
1. Download the ROM from HERE.
2. Extract it.
3. Download Pretoriano80's TWRP from "HERE" and flash it using "fastboot flash recovery_ramdisk <path to TWRP.img>".
4. After that reboot to TWRP while holding the VOL+ and POWER button.
5. In TWRP wipe internal storage and flash "THIS" to decrypt the phone.
6. Reboot to TWRP again.
7. Reboot to bootloader while in TWRP.
8. Flash DarkJoker360's TWRP.
9. Wipe everything except Vendor.
10. Transfer the system.img from the rom to your device's internal storage.
11. Tap on Install, then tap on install image, look for the system.img and flash it as System Image and reboot.
I haven't had any bugs for now, if u find something tell me.

It doesn't work.
{
"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"
}

alexut210008 said:
It doesn't work.View attachment 5323563
Click to expand...
Click to collapse
Which TWRP recovery did you use?

At first - twrp_p10_lite_0.6_test
Then - TWRP_3.4.0-0-warsaw_DarkJoker360_20200611

alexut210008 said:
At first - twrp_p10_lite_0.6_test
Then - TWRP_3.4.0-0-warsaw_DarkJoker360_20200611
Click to expand...
Click to collapse
And none of them work? For me they both work, which version of emui are you on? I used the latest update for my phone.

is switching recoverys an important step? weird
wow this actually worked, android 11 aosp for prague booting now on my p10 lite

I did everything according to the instructions. Swears at the size of system.img

is there android 11 based crdroid gsi images you can port?

I do everything strictly according to the instructions.

LesterDMolester said:
Hi guys, i ported the crDroid gsi from here.
I removed the unnecessary files from the rom, and included gapps.
And AIO fixes thanks to @DarkJoker360.
Install steps are easy.
1. Download the ROM from HERE.
2. Extract it.
3. Download Pretoriano80's TWRP from here and flash it using "fastboot flash recovery_ramdisk <path to TWRP.img>".
4. After that reboot to TWRP while holding the VOL+ and POWER button.
5. In TWRP wipe internal storage and flash this to decrypt the phone.
6. Reboot to TWRP again.
7. Reboot to bootloader while in TWRP.
8. Flash DarkJoker360's TWRP.
9. Wipe everything except Vendor.
10. Transfer the system.img from the rom to your device's internal storage.
11. Tap on Install, then tap on install image, look for the system.img and flash it as System Image and reboot.
I haven't had any bugs for now, if u find something tell me.
Click to expand...
Click to collapse
Hi...
ok i will give you a method that i used to get it work on my p10 lite WAS-LX1A 4Gb Dual-Sim
First...if you come from latest stock rom was-lx1a 8.0.0b398c432 you need to downgrade to was-lx1a 8.0.0b394c432 with dload or how ever you prefer. cause with b398 you system partition is just 3,7Gb and can not get rezise. but with the b394 you can rezise it but its no need to. cause after encrypting with fstab.hi6250b and the known following steps...format wipe and so on...the system partition have a size from 4.5gb.
I use the Pretoriano80 TWRP 3.2.1.0 twrp_p10_lite_0.5_test.img
then after initial boot and setup the first config....you can see in apps there is superuser app...its integrate in the Rom.
For using magisk i did the following steps thanks to @Hami_Do
hang-in the system and open file manager in TWRP
delete the following
system/bin/adb_root
system/bin/abdb
system/etc/init/adb_root.rc
system/etc/init/adbd.rc
system/etc/init/su.rc
system/app/superuser
system/bin/su
system/xbin/su
flash the stock ramdisk.img
btw camera works with different modi
for magisk...thanks to @Hami_Do i use v23.0apk
then roboot to TWRP
there flash magisk v23.0-phh.zip

Works on a Was-Lx3 9.00.366 (C212)?
emui 8 stock With elemental kernel v5
Cada vez que instalo una rom personalizada desde Android 9.0, da la animación de arranque y allí se reinicia de vez en cuando hasta que termina en recuperación.

kanade266 said:
Works on a Was-Lx3 9.00.366 (C212)?
emui 8 stock With elemental kernel v5
Cada vez que instalo una rom personalizada desde Android 9.0, da la animación de arranque y allí se reinicia de vez en cuando hasta que termina en recuperación.
Click to expand...
Click to collapse
Why you dont try it? Make a Backup of your current System and return to Stock Rom cause you change Kernel and what ever more. After the initial boot configure the Stock Rom to activate Dev-Opt where you can activate OEM unlock and USB Debugging and so on...
solong
speedson

GizmoTheGreen said:
is there android 11 based crdroid gsi images you can port?
Click to expand...
Click to collapse
My charging port is broken, i won't be able to do any ports until i get it fixed, btw Android 11 GSI's are still not stable as Android 10 GSI's.

speedson said:
Why you dont try it? Make a Backup of your current System and return to Stock Rom cause you change Kernel and what ever more. After the initial boot configure the Stock Rom to activate Dev-Opt where you can activate OEM unlock and USB Debugging and so on...
solong
speedson
Click to expand...
Click to collapse
I already did that and it did not leave me the same problem that happened to the first comment I did everything that the post says

Damn, same problem:
"size of image is larger than target device"

The ROM works fine, although I notice it's quite slow when opening apps and animations. The fingerprint reader also doesn't works sometimes like if it wasn't there but is fixed after a restart.

hello all , thanks for this ROM.
I have a problem when I follow every step without any mistakes. my phone does not want to start . just leave twrp mode and open Huawei eRecovery ( download latest version and recovery * wide data/factory reset * reboot ...)
I don't know why my can't start normally .even the logo not shown
thanks in advance

It is possible to have a detailed guide how to install ?
Thanks.

Hi...
ok a repeat again....if you come from Stock Rom with latest Version called WAS-LX1A 8.0.0.398 C432 your System Partition is just 3,7Gb. You need to downgrade to 1 Version before called WAS-LX1A 8.0.0.394 C432 then the System Partition is 4,5Gb. Now you can flash this custom Rom.
For downgrade use dload method and
Huawei P10 Lite WAS-LX1 WAS-L21 hw eu Warsaw-L21A 8.0.0.394(C432) Firmware EMUI8.0 05014JNC [androidhost.ru].zip - AndroidHost.RU
Download file - Huawei P10 Lite WAS-LX1 WAS-L21 hw eu Warsaw-L21A 8.0.0.394(C432) Firmware EMUI8.0 05014JNC [androidhost.ru].zip
androidhost.ru
download the package and in there you find software/dload and there are 4 folder and 1 update_sd.zip
create a dload folder on your desktop and extrac the update_sd.zip and the 1 folder for your Device. so my is a WAS-LX1A (LX1A=L21A) cause of this i extrac the WAS-L21A folder.
put the update_sd.zip and WAS-L21A folder from downloadet package into the createt dload folder on your desktop. Now copy/paste this dload folder from desktop to external-sd card in your Device, Power off the Device and restart it with press and hold Vol-up+Vol-down+Pwr (no usb cable plugged) now the firmware update should start and wait for progress is finished.

speedson said:
Hi...
ok a repeat again....if you come from Stock Rom with latest Version called WAS-LX1A 8.0.0.398 C432 your System Partition is just 3,7Gb. You need to downgrade to 1 Version before called WAS-LX1A 8.0.0.394 C432 then the System Partition is 4,5Gb. Now you can flash this custom Rom.
For downgrade use dload method and
Huawei P10 Lite WAS-LX1 WAS-L21 hw eu Warsaw-L21A 8.0.0.394(C432) Firmware EMUI8.0 05014JNC [androidhost.ru].zip - AndroidHost.RU
Download file - Huawei P10 Lite WAS-LX1 WAS-L21 hw eu Warsaw-L21A 8.0.0.394(C432) Firmware EMUI8.0 05014JNC [androidhost.ru].zip
androidhost.ru
download the package and in there you find software/dload and there are 4 folder and 1 update_sd.zip
create a dload folder on your desktop and extrac the update_sd.zip and the 1 folder for your Device. so my is a WAS-LX1A (LX1A=L21A) cause of this i extrac the WAS-L21A folder.
put the update_sd.zip and WAS-L21A folder from downloadet package into the createt dload folder on your desktop. Now copy/paste this dload folder from desktop to external-sd card in your Device, Power off the Device and restart it with press and hold Vol-up+Vol-down+Pwr (no usb cable plugged) now the firmware update should start and wait for progress is finished.
Click to expand...
Click to collapse
Software installa failed! I have a WAS-LX1A 8.0.0.396 C432

Unlocking bootloader/ rebooting in edl without testpoint Vivo Y31 2021

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

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.

Question All things related with GT2 Master Explorer edition (RMX3551)

I'm coming to talk about Realme GT2 Master Explorer edition (RMX3551).
It's been already 6 months using this device, the best device I ever had, but still struggling with China stuff, can't use WearOS devices, can't make backups in Google Drive, etc...
Up to now the only thing I know is to unlock the bootloader, so here we go:
First of all, ensure you are in Android 12, if not, you should downgrade version using OTA:
GT Master Exploration Edition : https://pan.baidu.com/share/init?surl=qXtbSfyifGm-LiJ7nEIX8w (code: dfng)
Once you are on Android 12, you can continue with the guide:
1. Support unlocked models
Realme GT2 Master Exploration Edition (RMX3551)
2. Matters needing attention
[BL unlocking must meet the following conditions]
It must be the True Self GT2 Master Explorer Edition purchased through official channels in mainland China
【BL Unlocking Instructions】(Important!!!)
1. After unlocking, it may have an unpredictable impact on the phone;
2. The third-party firmware may cause some functions of the mobile phone to fail to operate normally, for example, the camera function is unavailable, and may cause damage to the device;
3. It may cause leakage of private personal information on the mobile phone;
4. After unlocking, it will affect the system upgrade, and the user cannot receive the subsequent update version of realme UI;
5. After unlocking, the mobile phone status is equivalent to restoring the factory settings, and all user personal data will be cleared. It is recommended to back up the data in advance;
6. After the mobile phone is rooted, if necessary, you can contact the realme service center to assist in flashing the phone. If you can flash back to the official version, it will not affect the warranty status of the phone, but you will not be able to enjoy the return and exchange service; if you cannot flash back to the official version or the resulting If the hardware of the mobile phone fails, it is not covered by the warranty and needs to be repaired according to the situation.
3. How to unlock BL?
Preparation:
1. Download the dedicated unlocking tool APK for Realme GT2 Master Explorer Edition:
Link: https://pan.baidu.com/s/1lLPGjU2pVn8To9c7bd4LGA
Extraction code: 8023
2. The battery power of the mobile phone is kept above 60%
3. Prepare a USB data cable
4. Prepare a PC / Macbook
Officially begin:
Step 1, turn on developer mode
Go to "Settings" → "About Phone" → "Version Information", click "Version Number" 7 times to open the developer mode;
Step 2, open oemlock
Go to "Settings" → "Other Settings" → "Developer Mode" and turn on OEM unlocking;
Step 3, use APK to enter fastboot mode
Connect to the network, open the APK, and apply for unlocking in the APK.
{
"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"
}
Step 4, click "Start Application", please read the "Disclaimer" carefully and manually tick to agree.
Step 5, click "Submit Application" and then click "Return" to return to the application interface, wait for about 15 minutes. You can check whether the application has passed the review through "Check Review Status" on the application interface.
Step 6, unlock fastboot
After passing the review, click "Start Depth Test", and the phone will restart to the START interface
(The following is the real picture of the unlocking process)
Step 7, connect to the computer, run: fastboot flashing unlock
a. Go to https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/ to download the platform-tools tool for Windows
b. After downloading, extract it to the root directory of the c drive
c. Keyboard Win + R, enter CMD and then Enter
d. Enter cd.. and then Enter until C:\
e. Enter cd platform-tools and enter
f. Enter fastboot flashing unlock and Enter to continue step 8 of this post
Step 8, follow the prompts on the phone interface, press the volume up button to select unlock, and after a three-second countdown, the phone will enter the interface of the picture on the right.
Step 9, run the command: fastboot reboot on the computer adb, and the phone will automatically restart.
NOTE: This restart will erase all user data.
4. Lockback Tutorial
method one:
In the off state, press the volume down button and the power button at the same time to enter the BootLoader interface, connect to the computer, and enter: fastboot flashing lock
The phone will enter the lock interface, press the volume up button to select the lock bootloader, and after a three-second countdown, the phone will enter the interface of the picture on the right
Computer adb run command: fastboot reboot, the phone will automatically restart.
Method Two:
The mobile phone is turned on and connected to the computer, enter: adb reboot bootloader
The phone will enter the BootLoader interface
Enter: fastboot flashing lock
The phone will enter the lock interface, press the volume up button to select the lock bootloader, and after a three-second countdown, the phone will enter the interface of the picture on the right
Computer adb run command: fastboot reboot, the phone will automatically restart.
After completing the Bootloader lock by any of the above two methods, please download the unlock APK to complete the installation, and apply for exiting the in-depth test on the application interface.
It is stated again that the operation of BL unlocking will have the following risks! ! ! Very important and a must see!
1. After unlocking, it may have an unpredictable impact on the phone;
2. The third-party firmware may cause some functions of the mobile phone to fail to operate normally, for example, the camera function is unavailable, and may cause damage to the device;
3. It may cause leakage of private personal information on the mobile phone;
4. After unlocking, it will affect the system upgrade, and the user cannot receive the subsequent update version of realme UI;
5. After unlocking, the mobile phone status is equivalent to restoring the factory settings, and all user personal data will be cleared. It is recommended to back up the data in advance;
6. After the mobile phone is rooted, if necessary, you can contact the realme service center to assist in flashing the phone. If you can flash back to the official version, it will not affect the warranty status of the phone, but you will not be able to enjoy the return and exchange service; if you cannot flash back to the official version or the resulting If the hardware of the mobile phone fails, it is not covered by the warranty and needs to be repaired according to the situation.
THANKS FOLKS!

I really wanted a custom ROM.

thanks for contribution, I'm using Realme GT2 Master explorer edition, the Chinese version of Realme UI 4.0 rom with built-in Google services, Android 13. It's been about 3 months since Realme UI has not received any new updates.

mrducluan said:
thanks for contribution, I'm using Realme GT2 Master explorer edition, the Chinese version of Realme UI 4.0 rom with built-in Google services, Android 13. It's been about 3 months since Realme UI has not received any new updates.View attachment 5916091
Click to expand...
Click to collapse
Could you tell me where I can find this ROM? Thanks.

JaymeBA said:
Could you tell me where I can find this ROM? Thanks.
Click to expand...
Click to collapse
I sent you the link in a private message.

I wish to have a Global Rom too, but it's like Realme decided not to go forward with this....sadly.

Full OTA C15
RMX3551_13.1.0.101(CN01)
RMX3551_11.C.15_1150_202305222028

Stano36 said:
Full OTA C15
RMX3551_13.1.0.101(CN01)
RMX3551_11.C.15_1150_202305222028
Click to expand...
Click to collapse
Trae idioma en español?
Compre el realme gt 2 máster edición y no se actualiza
Mod translation:
Does it bring language in Spanish?
I bought the realme gt 2 master edition and it does not update

Franciscozx said:
Mod translation:
Does it bring language in Spanish?
Click to expand...
Click to collapse
Greetings, and welcome to XDA. As a friendly reminder, we ask all members to please post in English as stipulated by XDA Rule #4:
Spoiler: XDA Rule #4
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
Thank you for your cooperation, and have a pleasant day.
-Regards: Badger50

Stano36 said:
OTA completo C15
RMX3551_13.1.0.101(CN01)
RMX3551_11.C.15_1150_202305222028
Click to expand...
Click to collapse
¿Esta ROM tiene idioma español?

Franciscozx said:
¿Esta ROM tiene idioma español?
Click to expand...
Click to collapse
Rom designed for Chinese device.I don't know if it contains the Spanish language.

mrducluan said:
gracias por su contribución, estoy usando Realme GT2 Master explorer edition, la versión china de Realme UI 4.0 rom con servicios de Google incorporados, Android 13. Han pasado aproximadamente 3 meses desde que Realme UI no recibió ninguna actualización nueva.View attachment 5916091
Click to expand...
Click to collapse
¿Esta ROM tiene idioma español?

Stano36 said:
Full OTA C15
RMX3551_13.1.0.101(CN01)
RMX3551_11.C.15_1150_202305222028
Click to expand...
Click to collapse
I wanted to clarify a doubt. You said you have the ROM with integrated google services. Do all RMX3551 owners have the same ROM? Does this ROM already come with playstore and google services pre-installed? Thanks again.

JaymeBA said:
I wanted to clarify a doubt. You said you have the ROM with integrated google services. Do all RMX3551 owners have the same ROM? Does this ROM already come with playstore and google services pre-installed? Thanks
Click to expand...
Click to collapse
It's an OTA update for the Chinese version, it probably won't include Google services.

I can't download the downgrade file, could you re-upload in google drive or something ?

Sakeadoor said:
First of all, ensure you are in Android 12, if not, you should downgrade version using OTA:
GT Master Exploration Edition : https://pan.baidu.com/share/init?surl=qXtbSfyifGm-LiJ7nEIX8w (code: dfng)
Click to expand...
Click to collapse
I've downloaded the downgrade file, but it's not for GT2 RMX3551, it's for GT RMX3366

BIBUBO BCJ said:
I've downloaded the downgrade file, but it's not for GT2 RMX3551, it's for GT RMX3366
Click to expand...
Click to collapse
Rollback for RMX3551 GT2 EE
https://rbp01.realme.net/RMX3551/RMX3551_11_A_OTA_0180_all_86b356_CN.zip

Develop Bugs

welcome