Database Develop

The Ultimate Motorola Droid 3 Recovery Guide, SBF update and root included

1. Iniciar en AP Fastmode / Starts on AP Fastmode
2. Iniciar y ejecutar RSD Lite / Install and execute RSD Lite
3. Instalar 906 SBF XML File (Descomprimir primero .7z file) / Install 906 SBF XML File (uncompress 7z file first)
4. Dejar que inicie el móvil, transferir update.zip a la SD / Allow device to start and transfer update.zip to SD
5. Apagar y encender móvil presionando X + Power / Shutdown and power on pressing X + Power at start
6. Cuando aparezca el triángulo de Android Presionar Vol Down + Up / When the Android Triangle appears, press Vol Down + Up at once.
7. Factory Reset y Wipe Cache / Factory Reset y Wipe Cache
8. Elegir "Update from SD Card" / Chose "Update from SD Card"
9. Seleccionar la carpeta update.zip / Select the update.zip compressed folder
10. Una vez instalada la actualización, iniciar el móvil / When update was installed, starts device normally
11. Personalizar al gusto / Personalize device
12. En "Settings -> Applications -> Developing Tools -> Debug mode" marcar / At "Settings -> Applications -> Developing Tools -> Debug mode" check
13. Ejecutar "motofail\run.bat" / Execute "motofail\run.bat"
14. Esperar... / Wait...
15. Listo, .906 y root en acción / Ready .906 and root running
Download Package Link (Includes all tools needed):http://minus.com/lbxveduAYIEiP2
By sloaxleak (twitter.com/#!/sloaxleak)

We already have a topic like this.
Also with half in spanish it's not very clear

not needed...did you get permission to repost other peeps work?

RE
DoubleYouPee said:
We already have a topic like this.
Also with half in spanish it's not very clear
Click to expand...
Click to collapse
Sorry, it was not my intention

...
ovelayer said:
not needed...did you get permission to repost other peeps work?
Click to expand...
Click to collapse
I just created a compilation of all the necessary files. The credits cited in each of them remain intact. I think in spanish is needed.
If a moderator believes that is an infraction, I wish him to tell me.
Thx.

It's in Spanish, so it may be helpful to some!

this thread has been reported for kanging other contributors' work.
closed.

SOLVED: Flashing Magisk results in Error1: Cannot mount /vendor

I've a Redmi 4a(Rolex) and flashing Magisk results in Cannot mount /vendor
I've started with AOSP Extended but flashing Failed. Searched online to see I must try different ROM, so I switched to Lineage OS15.1 and again Failed. Finally tried with Resurrection Remix but again Failed. Researching more someone suggested to flash boot.img separately but again failed. I'm using TWRP but that can't be the problem as currently I'm on latest version-3.2.3.0
Please help me with this. Or there must be an update to the current Magisk as I see there are many like me. I've also tried different versions of Magisk. I think John Wu (@topjohnwu) must bring an update fixing this problem
Code:
- Mounting /system, /vendor
! Cannot mount /vendor
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v17.zip'
Read Solution Here: https://freaksterism.blogspot.com/2018/10/solved-cannot-mount-vendor-magisk.html

smurfisrael03 said:
I'm using TWRP but that can't be the problem as currently I'm on latest version-3.2.3.0
Click to expand...
Click to collapse
If the TWRP you have installed isn't Treble compatible it doesn't matter if you use the latest version.
Search "cannot mount /vendor" in the Magisk forum and you'll find several threads about it, and that using a compatible TWRP is usually the solution.

Failed
Didgeridoohan said:
If the TWRP you have installed isn't Treble compatible it doesn't matter if you use the latest version.
Search "cannot mount /vendor" in the Magisk forum and you'll find several threads about it, and that using a compatible TWRP is usually the solution.
Click to expand...
Click to collapse
Installed Redwolf Recovery (Treble based) still stuck at the same Fail message---> Cannot mount /vendor
I've searched and tried lots of steps only to fail

Solution:
smurfisrael03 said:
Installed Redwolf Recovery (Treble based) still stuck at the same Fail message---> Cannot mount /vendor
I've searched and tried lots of steps only to fail
Click to expand...
Click to collapse
Okay, So after researching more I got to this link and installed treble based TWRP with /vendor partition:
I don't have 10 posts yet https:// androidfilehost.com/ ?w=file-thanks&fid=818222786056029479&mid=219&download_id=258ad41ee871813957ac9d0b5e669487&tid=1538008115&hc=091581d460197eb7735e89a53540a61fee748ea5e16661bfbf5e05f0cfaaaf32
NOTE: I've Remdi 4A(Rolex) and Treble based ROM(AOSP Extended, RR,Lineage 15.1 --> I've tried all these and they work)
Finally Installed Magisk and Rooted my Redmi 4A

Guys cab you please help? i have the same problem with vendor on mi max 2, what twrp do you advising me to download?

No its not thath the solution.... i tried it many times..

Noexcusses said:
No its not thath the solution.... i tried it many times..
Click to expand...
Click to collapse
Yes it is
You need a TWRP that has correct mount points for /vendor. It's not magisk

yo tengo el mismo problema, al pasar de rr6 a rr7 en xiaomi mi max 2, no me flashea magisk manager, ni version 18.0 ni version 18.1 beta, error 1 siempre, ni a traves de adb sideload ni con twrp, ya no se como rootear esta version de resurrection remix 9.0 PIE, y son dias leyendo hilos pero no lo consigo, gracias por leerme . un saludo.

bandido**** said:
yo tengo el mismo problema, al pasar de rr6 a rr7 en xiaomi mi max 2, no me flashea magisk manager, ni version 18.0 ni version 18.1 beta, error 1 siempre, ni a traves de adb sideload ni con twrp, ya no se como rootear esta version de resurrection remix 9.0 PIE, y son dias leyendo hilos pero no lo consigo, gracias por leerme . un saludo.
Click to expand...
Click to collapse
English please

Magisk

Well hi to rooted user...im in 2020....for those who r searching for the answer on how to fix the problem twrp recovery error 1 on installing magisk....
1. Youll have to find the current os zip file that ur using...
2. extract the bot.img
3. open TWRP then select flash img and choose the bot.img and flash it
4. Then select to flash zip N flash the magisk...
5. Done :fingers-crossed:
Sorry for my bad language
Feel free to ask me

What's that os zip file you are referring to?

jogoh said:
What's that os zip file you are referring to?
Click to expand...
Click to collapse
He means the custom ROM zip file that you've downloaded to flash to your phone.
In other words, to take the original unmodified boot.img from whichever ROM you're using or plan to install, flash that boot image via recovery so as to replace the currently modified boot partition which may be causing Error -1, and once that completes flash Magisk installer zip and let it run the boot image patching process on a clean slate.
It might work. But the issue can also just be the version of the recovery image simply doesn't support Treble. It's happened to me but usually the missing vendor partition doesn't throw an error -1 fail for flashing Magisk, so it may indeed be a corrupt boot image issue and not just TWRP.

In my case, flashing a readmi 5A compatible treble zip via TWRP solved the issue. I dont' know if I am allowed to post an url, but everything I needed I found here (Redmi 4A & 5A users only): "xiaomifirmware.com/roms/project-treble-rom-for-xiaomi-redmi-4a-5a-unified/" (just add the h t t p s protocol before it).

Twrp no se pega en moto g6

I have flashed the correct twrp for my Moto G6 and when entering for the first time the twrp asks me for a code and 2 options appear, one is to cancel and the other is language. Also to restart it and re-enter twrp mode no longer appears the twrp.

copetestag said:
He flasheado el twrp correcto para mi Moto G6 y al entrar por primera vez al twrp me pide un codigo y aparecen 2 opciones una es cancelar y la otra es idioma. También al reiniciarlo y volver a entrar en modo twrp ya no me aparece el twrp.
Click to expand...
Click to collapse
English please: I have flashed the correct twrp for my Moto G6 and when entering for the first time the twrp asks me for a code and 2 options appear, one is to cancel and the other is language. Also to restart it and re-enter twrp mode no longer appears the twrp.
---------- Post added at 09:51 PM ---------- Previous post was at 09:42 PM ----------
copetestag said:
He flasheado el twrp correcto para mi Moto G6 y al entrar por primera vez al twrp me pide un codigo y aparecen 2 opciones una es cancelar y la otra es idioma. También al reiniciarlo y volver a entrar en modo twrp ya no me aparece el twrp.
Click to expand...
Click to collapse
Get rid of encryption as TWRP can't decrypt data well by 1) FORMAT data (not just wipe data) which clears all files on "internal sd"; external sd card will be fine. 2) install no verity boot.img from your corresponding stock rom version (available on Android File Host--see instructions on main TWRP and root thread). 3) Install No Force Encrypt zip (also available from same thread, for Oreo only)

Development [RECOVERY] [OFFICIAL] [a33x] TeamWin Recovery Project 3 for Galaxy A33 5G (exynos)

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Working features:
* Flashing of zip and img files.
* Backup and restore.
* MTP, ADB, FastbootD.
* ADB Sideload
* CPU Temperature, Battery percentage, Clock.
* Etc...
Installation
1) Download the files: twrp tar, vbmeta_disabled tar and magisk apk
2) Open Odin in your pc.
3) Boot to download mode
4) Load the recovery tar into AP slot and the vbmeta_disabled tar into BL slot and click "Start".
5) As soon as the screen turns off, release all keys and press power + volume up keys till you boot into twrp (the phone has to be connected to PC all the time).
6) Go to Wipe > Format Data > type yes
7) Reboot to recovery.
8) Flash Magisk.
9) Reboot to system, Enjoy.
Download
TWRP and vbmeta_disabled: here
Magisk: here
Thanks
TWRP team
afaneh92
Sources:
Device tree
TWRP recovery

nice

lnwbas569 said:
Is there has 0mb internal storage issue?
Click to expand...
Click to collapse
That's probably because your storage is encrypted, read steps 4 and 5.

lnwbas569 said:
Nvm I got bootloop after follow method 2
My device : A336E
Basebrand A336EDXU4BVKB
Click to expand...
Click to collapse
what did you do exactly? and what is bootlooping, the twrp or the system?

lnwbas569 said:
After I had done in odin and did terminal instruction by type multidisabler, then format data and reboot into recovery again.
Once its done, I tried to boot into system then got bootloop
Click to expand...
Click to collapse
Okay, try to flash stock "AP" file and read the instructions again, but this time without multidisabler step. May fix your issue

lnwbas569 said:
Have tried, I'm sorry but still even got bootloop. I cannot boot into system
Click to expand...
Click to collapse
The problem is that you formatted data, don't format it, I've updated instructions

What is vbmeta for?

lnwbas569 said:
I wasn't format anything in recovery but still can't boot into system
Click to expand...
Click to collapse
Are you sure? Some guy just pmed me on telegram and he booted to system perfectly

in the A336M variant I got bootlopp when doing format data the system does not start, then I installed recovery stock by odin and it started perfectly, then I reinstalled twrp without formatting data and the system started fine but in vain because nothing can be done everything Flashing gives me a fail, hopefully it will be corrected in the A336M variant

lnwbas569 said:
For me, It doesnt boot into system since I haven't format data via twrp or even reinstall stock AP.tar over then reinstall twrp again. Seems no solved for me recently
Click to expand...
Click to collapse
you can install twrp without formatting data and the system starts but it is of no use since the storage is encrypted, You need to do yes or yes format data to decrypt, but there is the problem that the system does not start after doing format data

Hello everybody.
I got SM-336B phone recently, the system has been upgraded to android 13.
Bootloader is unlocked yet; I cleared user data several times, but after installing TWRP I have the same bootloop problem.
The messages says "can't mount /data partition"
I've tried also to flash SuperSU.zip, with no result, and the same error.
Anyone has a solution for mount error?
Thanks.

Beatnik71 said:
Hello everybody.
I got SM-336B phone recently, the system has been upgraded to android 13.
Bootloader is unlocked yet; I cleared user data several times, but after installing TWRP I have the same bootloop problem.
The messages says "can't mount /data partition"
I've tried also to flash SuperSU.zip, with no result, and the same error.
Anyone has a solution for mount error?
Thanks.
Click to expand...
Click to collapse
I think we all have the same problem friend, I think the developer will correct it soon

lnwbas569 said:
I saw the multidisabler in twrp which said some kind of " multidisabler android version: 12" while im installing this twrp on android 13 device as well. Hope this maybe to be solved soon cause I wanna flash custom stuffs in twrp so bad xd.
Click to expand...
Click to collapse
yes exactly but the twrp works on android 12 and 13, I also want to do things on my device but I don't know when they will correct the twrp

I was curious about the multidisabler script you mentioned, can the people getting boot loops with "can't mount /data partition" try to post system logs?
I see multidiabler runs a sed script on fstab to disable encryption, is the bug here? Seems likely.

peggeddroid said:
I was curious about the multidisabler script you mentioned, can the people getting boot loops with "can't mount /data partition" try to post system logs?
I see multidiabler runs a sed script on fstab to disable encryption, is the bug here? Seems likely.
Click to expand...
Click to collapse
multidisabler doesn't fix anything, bootloop still the same try millions of things but system still won't boot

Gollo99 said:
multidisabler doesn't fix anything, bootloop still the same try millions of things but system still won't boot
Click to expand...
Click to collapse
There's a HOWTO on using getting system logs with adb:
How to take system logcats
Since you're all getting messages indicating it's a mount error, I read through the multidisabler script source and I kind of suspect there's an error where multidisabler modifies the fstab file.
maybe line 109

peggeddroid said:
There's a HOWTO on using getting system logs with adb:
How to take system logcats
Since you're all getting messages indicating it's a mount error, I read through the multidisabler script source and I kind of suspect there's an error where multidisabler modifies the fstab file.
maybe line 109
Click to expand...
Click to collapse
yes perhaps, for example in mediatek and ext4 you have to modify fstab for the system to start, but in the case of A33 f2fs partition I don't know how fstab works

Gollo99 said:
yes perhaps, for example in mediatek and ext4 you have to modify fstab for the system to start, but in the case of A33 f2fs partition I don't know how fstab works
Click to expand...
Click to collapse
Oh that's interesting, samsung switched to f2fs for their in-house chips.
multidisabler is I gather a first time run script that turns off a bunch of options that aren't or can't be supported on a 3rd party ROM without vendor magic. The line that deals with fstab is a sed script that modifies the fstab to turn off full disk encryption, it might be wrecking fstab and preventing mounts.
But this is a new filesystem. Is this TWRP distro being compiled with a f2fs module anyway?
Looks like there's f2fs support in the base distribution. Looks like me-cafebabe has done the recent work on encrypted filesystem support in TWRP and has worked on some older samsung profiles. So this is probably just some simple questions and debugging.

peggeddroid said:
Oh that's interesting, samsung switched to f2fs for their in-house chips.
multidisabler is I gather a first time run script that turns off a bunch of options that aren't or can't be supported on a 3rd party ROM without vendor magic. The line that deals with fstab is a sed script that modifies the fstab to turn off full disk encryption, it might be wrecking fstab and preventing mounts.
But this is a new filesystem. Is this TWRP distro being compiled with a f2fs module anyway?
Looks like there's f2fs support in the base distribution. Looks like me-cafebabe has done the recent work on encrypted filesystem support in TWRP and has worked on some older samsung profiles. So this is probably just some simple questions and debugging.
Click to expand...
Click to collapse
yes, samsung changed the partitions but there are still many questions and few answers, let's hope this is solved quickly and we can get twrp 100% functional

Gabriel260BR said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Working features:
* Flashing of zip and img files.
* Backup and restore.
* MTP, ADB, FastbootD.
* CPU Temperature, Battery percentage, Clock.
* Etc...
Errores actuales:
* Descifrado
* carga lateral adb
Instalación
Método 1
1) Si ya tiene twrp en su teléfono, extraiga recovery.img del archivo tar usando Zarchiver o Winrar.
2) Reinicie su teléfono e inicie la recuperación.
3) Flashear el recovery.img como "recuperación"
4) Finalmente, reinicie la recuperación para disfrutar de la nueva recuperación de twrp
Método 2
1) Si está instalando una recuperación personalizada por primera vez, abra Odin en su PC. Descargue el último archivo de recuperación adjunto a continuación. Inicie su teléfono en modo de descarga.
2) Flashee el archivo tar que descargó en la ranura AP.
3) Tan pronto como la pantalla se apague, suelte todas las teclas y presione las teclas de encendido + subir volumen hasta que inicie twrp (el teléfono debe estar conectado a la PC todo el tiempo).
4) Ahora tienes twrp
Advertencia: no formatee los datos, por alguna razón el sistema se reiniciará si lo hace... Estoy buscando una solución
Descargar
El archivo se adjunta a continuación
Gracias
equipo TWRP
afaneh92
Guillermo por probar el recovery
Fuentes:
Árbol de dispositivos
Recuperación TWRP
Click to expand...
Click to collapse
Puedo instalarlo desde la app de twrp

How To Guide Back to CN (Bootloader Lock)

Hello everyone, I decided to create this Tutorial for (mainly) people like me, who got their devices from the Chinese version with their ROMs modified for Global.
But I will explain where you should focus if you only have the bootloader unlocked for root and have not modified your system.
1- I'm Brazilian and this text is FULLY by Google translator
2- For Newbies (because the old ones know that) ALWAYS read EVERYTHING, even comments if possible before starting the process.
3- Do it at YOUR own risk, although if you follow it correctly you will succeed.
4- I assume you have: Plataform Tool (ADB & Fastboot) (if you don't start with that on your PCs) your drivers (Motorola) are also installed
What is required for Bootloader Lock?
Be on the correct version of your Firmware, and have the OEM unlock switch in the ALLOW position
Usually when unlocking the bootloader, this key goes off in the off position, and that's why we need Root with Saftnet active for it to turn on and be able to set it to allow again
So for those who ONLY unlocked their bootloader and NOT changed the Firmware (from CN to Global or some Custom Rom)
JUST activate the OEM unlocking option (remembering that you will need root with saftnet passing)
I recommend Magisk Delta (Canary) and Saftnetfix module
Enabled unlock permission remove root by magisk app (TOTAL removal)
Ready you are sure your system is correct has the key deleted but in allowing?
Put your device in bootloader:
adb/reboot/bootloader
or Turn off the device and hold the Power button together with Vol -
fastboot oem lock
And you will have your device locked and everything working as it should.
Now who received with modified ROM or installed a custom one:
Make sure you have the correct update channel (retcn for Chinese, reteu for Europe, or whatever yours is) if it is modified:
fastboot oem config carrier retcn
done that
Go to lolinet Lolinet (CN) , Lolinet (EU), Lolinet (AIL), Lolinet (BR) and download the full ROM for your version (we will only use Smart Rescue at the end to update it It should not recognize your device for redemption before having an old and correct version)
Make sure you download the older version (this is a guarantee thing) as we will use Lenovo Smart Rescue Center to update and be 100% sure we are on the right version.
Extract the files and look for flashfile.xml open with notepad (or any other of your choice) copy everything and paste it on This Site it will give you the commands to pass the ROM, copy the commands and paste in the CMD of the window where I have the ROM files, or download the file (it will come in zip, extract and copy flashfile.bat to the ROM folder and just click on it, wait for the installation and restart
Now activate the developer options and see if you have the OEM unlock key in allow, it will be off but it has to be in allow if you don't do the root process under Magisk pass the saftnetfix module and it should appear lit now and you will be able to put in allow
Done, enter Magisk and remove Root (total removal)
It will restart and you will see that now the key is erased but in allow
So now Lenovo Smart Rescue should allow the Rescue of your device, follow the steps until it installs the most current version, when done, skip everything (as it will restore when blocked) to activate the developer option and USB debugging , then in fastboot use
fastboot oem lock
OK, you should now have your device as it left the factory.

RicoMartins said:
Hola a todos, decidí crear este tutorial para (principalmente) personas como yo, que obtuvieron sus dispositivos de la versión china con sus ROM modificadas para Global.
Pero te explicaré dónde debes concentrarte si solo tienes el gestor de arranque desbloqueado para root y no has modificado tu sistema.
1- Soy brasileño y este texto es COMPLETAMENTE del traductor de Google
2- Para los Novatos (porque los viejos lo saben) SIEMPRE lean TODO, incluso los comentarios si es posible antes de iniciar el proceso.
3- Hazlo bajo TU propio riesgo, aunque si lo sigues correctamente lo lograrás.
4- Supongo que tiene: Plataforma Tool (ADB y Fastboot) (si no comienza con eso en sus PC) sus controladores (Motorola) también están instalados
¿Qué se requiere para el bloqueo del cargador de arranque?
Estar en la versión correcta de su firmware y tener el interruptor de desbloqueo OEM en la posición PERMITIR
Por lo general, al desbloquear el gestor de arranque, esta tecla se apaga en la posición de apagado, y es por eso que necesitamos Rootear con Saftnet activo para que se encienda y poder configurarlo para permitir nuevamente
Entonces, para aquellos que SOLO desbloquearon su cargador de arranque y NO cambiaron el firmware (de CN a Global o alguna Rom personalizada)
SOLO active la opción de desbloqueo OEM (recordando que necesitará root con pase de saftnet)
Recomiendo Magisk Delta (Canario) y módulo Saftnetfix
Permiso de desbloqueo habilitado para eliminar root por la aplicación magisk (eliminación TOTAL)
Listo estas seguro que tu sistema esta correcto se ha borrado la clave pero en permitir?
Pon tu dispositivo en el gestor de arranque:
adb/reiniciar/cargador de arranque
o Apague el dispositivo y mantenga presionado el botón de Encendido junto con Vol -
candado fastboot oem
Y tendrás tu dispositivo bloqueado y todo funcionando como debería.
Ahora quien recibió con ROM modificada o instaló una personalizada:
Asegúrese de tener el canal de actualización correcto (retcn para chino, reteu para Europa o el suyo) si se modifica:
fastboot oem config carrier reetcn
hecho eso
Vaya a lolinet Lolinet (CN) , Lolinet (EU) , Lolinet (AIL) , Lolinet (BR) y descargue la ROM completa para su versión (solo usaremos Smart Rescue al final para actualizarlo. No debería reconocer su dispositivo para redención antes de tener una versión antigua y correcta)
Asegúrese de descargar la versión anterior (esto es una garantía) ya que usaremos Lenovo Smart Rescue Center para actualizar y estar 100% seguros de que estamos en la versión correcta.
Extraiga los archivos y busque flashfile.xml abierto con el bloc de notas (o cualquier otro de su elección) copie todo y péguelo en Este sitio le dará los comandos para pasar la ROM, copie los comandos y pegue en el CMD de la ventana donde tengo los archivos ROM, o descargar el archivo (vendrá en zip, extraiga y copie flashfile.bat a la carpeta ROM y simplemente haga clic en él, espere la instalación y reinicie
Ahora active las opciones de desarrollador y vea si tiene la clave de desbloqueo OEM habilitada, estará desactivada pero debe estar habilitada si no realiza el proceso raíz en Magisk, pase el módulo saftnetfix y debería aparecer encendido ahora y usted será capaz de poner en permitir
Listo, ingresa a Magisk y elimina Root (eliminación total)
Se reiniciara y veras que ahora la clave esta borrada pero en allow
Así que ahora Lenovo Smart Rescue debería permitir el rescate de su dispositivo, siga los pasos hasta que instale la versión más actual, cuando termine, omita todo (ya que se restaurará cuando se bloquee) para activar la opción de desarrollador y la depuración USB, luego en fastboot use
candado fastboot oem
Bien, ahora deberías tener tu dispositivo como salió de f
Click to expand...
Click to collapse
RicoMartins said:
Hello everyone, I decided to create this Tutorial for (mainly) people like me, who got their devices from the Chinese version with their ROMs modified for Global.
But I will explain where you should focus if you only have the bootloader unlocked for root and have not modified your system.
1- I'm Brazilian and this text is FULLY by Google translator
2- For Newbies (because the old ones know that) ALWAYS read EVERYTHING, even comments if possible before starting the process.
3- Do it at YOUR own risk, although if you follow it correctly you will succeed.
4- I assume you have: Plataform Tool (ADB & Fastboot) (if you don't start with that on your PCs) your drivers (Motorola) are also installed
What is required for Bootloader Lock?
Be on the correct version of your Firmware, and have the OEM unlock switch in the ALLOW position
Usually when unlocking the bootloader, this key goes off in the off position, and that's why we need Root with Saftnet active for it to turn on and be able to set it to allow again
So for those who ONLY unlocked their bootloader and NOT changed the Firmware (from CN to Global or some Custom Rom)
JUST activate the OEM unlocking option (remembering that you will need root with saftnet passing)
I recommend Magisk Delta (Canary) and Saftnetfix module
Enabled unlock permission remove root by magisk app (TOTAL removal)
Ready you are sure your system is correct has the key deleted but in allowing?
Put your device in bootloader:
adb/reboot/bootloader
or Turn off the device and hold the Power button together with Vol -
fastboot oem lock
And you will have your device locked and everything working as it should.
Now who received with modified ROM or installed a custom one:
Make sure you have the correct update channel (retcn for Chinese, reteu for Europe, or whatever yours is) if it is modified:
fastboot oem config carrier retcn
done that
Go to lolinet Lolinet (CN) , Lolinet (EU), Lolinet (AIL), Lolinet (BR) and download the full ROM for your version (we will only use Smart Rescue at the end to update it It should not recognize your device for redemption before having an old and correct version)
Make sure you download the older version (this is a guarantee thing) as we will use Lenovo Smart Rescue Center to update and be 100% sure we are on the right version.
Extract the files and look for flashfile.xml open with notepad (or any other of your choice) copy everything and paste it on This Site it will give you the commands to pass the ROM, copy the commands and paste in the CMD of the window where I have the ROM files, or download the file (it will come in zip, extract and copy flashfile.bat to the ROM folder and just click on it, wait for the installation and restart
Now activate the developer options and see if you have the OEM unlock key in allow, it will be off but it has to be in allow if you don't do the root process under Magisk pass the saftnetfix module and it should appear lit now and you will be able to put in allow
Done, enter Magisk and remove Root (total removal)
It will restart and you will see that now the key is erased but in allow
So now Lenovo Smart Rescue should allow the Rescue of your device, follow the steps until it installs the most current version, when done, skip everything (as it will restore when blocked) to activate the developer option and USB debugging , then in fastboot use
fastboot oem lock
OK, you should now have your device as it left the factory.
Click to expand...
Click to collapse
Help me to return to the CN ROM, since they installed the global ROM, to my motorola x30 pro, and I want to have updates via OTA again and see streaming apps

KairosIbiza said:
Help me to return to the CN ROM, since they installed the global ROM, to my motorola x30 pro, and I want to have updates via OTA again and see streaming apps
Click to expand...
Click to collapse
Hi I've been away for a while, do you still have problems doing this? Or has it already been resolved?

RicoMartins said:
Hello everyone, I decided to create this Tutorial for (mainly) people like me, who got their devices from the Chinese version with their ROMs modified for Global.
But I will explain where you should focus if you only have the bootloader unlocked for root and have not modified your system.
1- I'm Brazilian and this text is FULLY by Google translator
2- For Newbies (because the old ones know that) ALWAYS read EVERYTHING, even comments if possible before starting the process.
3- Do it at YOUR own risk, although if you follow it correctly you will succeed.
4- I assume you have: Plataform Tool (ADB & Fastboot) (if you don't start with that on your PCs) your drivers (Motorola) are also installed
What is required for Bootloader Lock?
Be on the correct version of your Firmware, and have the OEM unlock switch in the ALLOW position
Usually when unlocking the bootloader, this key goes off in the off position, and that's why we need Root with Saftnet active for it to turn on and be able to set it to allow again
So for those who ONLY unlocked their bootloader and NOT changed the Firmware (from CN to Global or some Custom Rom)
JUST activate the OEM unlocking option (remembering that you will need root with saftnet passing)
I recommend Magisk Delta (Canary) and Saftnetfix module
Enabled unlock permission remove root by magisk app (TOTAL removal)
Ready you are sure your system is correct has the key deleted but in allowing?
Put your device in bootloader:
adb/reboot/bootloader
or Turn off the device and hold the Power button together with Vol -
fastboot oem lock
And you will have your device locked and everything working as it should.
Now who received with modified ROM or installed a custom one:
Make sure you have the correct update channel (retcn for Chinese, reteu for Europe, or whatever yours is) if it is modified:
fastboot oem config carrier retcn
done that
Go to lolinet Lolinet (CN) , Lolinet (EU), Lolinet (AIL), Lolinet (BR) and download the full ROM for your version (we will only use Smart Rescue at the end to update it It should not recognize your device for redemption before having an old and correct version)
Make sure you download the older version (this is a guarantee thing) as we will use Lenovo Smart Rescue Center to update and be 100% sure we are on the right version.
Extract the files and look for flashfile.xml open with notepad (or any other of your choice) copy everything and paste it on This Site it will give you the commands to pass the ROM, copy the commands and paste in the CMD of the window where I have the ROM files, or download the file (it will come in zip, extract and copy flashfile.bat to the ROM folder and just click on it, wait for the installation and restart
Now activate the developer options and see if you have the OEM unlock key in allow, it will be off but it has to be in allow if you don't do the root process under Magisk pass the saftnetfix module and it should appear lit now and you will be able to put in allow
Done, enter Magisk and remove Root (total removal)
It will restart and you will see that now the key is erased but in allow
So now Lenovo Smart Rescue should allow the Rescue of your device, follow the steps until it installs the most current version, when done, skip everything (as it will restore when blocked) to activate the developer option and USB debugging , then in fastboot use
fastboot oem lock
OK, you should now have your device as it left the factory.
Click to expand...
Click to collapse
Hi Bro,
The older version of Lenovo Smart Rescue always requests upgrade to the latest. Or it will be auto closed. Can I just skip this step to flash the firmware by coverted commands without this application?
Thank you!

Hello friend!
I've never tried it this way, you can try it, once Smart Recue recognizes your device and agrees to update it shouldn't have any problems. But I believe this will not happen. For the Update steps by commands via fastboot are precisely for the tool to recognize the device and perform the update.
Pay attention only to blocking it only in the CN version (as I said, I never did it otherwise, so I don't know if the tool can be updated to a global version).