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).
Related
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.
Hello everyone, first of all I apologize for my English, I'm French, I can ask you for help because I have a big problem with my xperia Z, let me explain.
I broke my USB port, I now use a dock charger, when I break the USB port I was in the rom V7.0.0 Existenz, I could update this rom thanks to the application XZRecovery which allows me to boot into recovery, it's the only way I found to update the rom and install mods but I'm stuck because-because that since the update to the Roma existenz kitkat, I have to flash the mod EXTRA_VOLUME_BOOST because of a bug phone calls, I have to put the speaker to wait for my partner or I not hear so I wanted to reinstall XZRecovery but this time I have a error message:
(I can not put the screen of the apk, I wrote that it displays)
- Starting recovery installation -
Checking for "su"
Extracting recovery files
Remounting system (RW)
Remount system failed !
even when I want to delete the recovery I have the same message.
I had another worry after this update, the phone will reboot to the sony logo I insert my SD card, as soon as I removed the phone starts normally, but once the main menu, I deliver my SD card is detected and I can access to my music.
I do not know if this problem is related to the failure of the installation apk XZRecovery.
If you have a solution to these problems I'm interested.
MakeBelive said:
Hello everyone, first of all I apologize for my English, I'm French, I can ask you for help because I have a big problem with my xperia Z, let me explain.
I broke my USB port, I now use a dock charger, when I break the USB port I was in the rom V7.0.0 Existenz, I could update this rom thanks to the application XZRecovery which allows me to boot into recovery, it's the only way I found to update the rom and install mods but I'm stuck because-because that since the update to the Roma existenz kitkat, I have to flash the mod EXTRA_VOLUME_BOOST because of a bug phone calls, I have to put the speaker to wait for my partner or I not hear so I wanted to reinstall XZRecovery but this time I have a error message:
(I can not put the screen of the apk, I wrote that it displays)
- Starting recovery installation -
Checking for "su"
Extracting recovery files
Remounting system (RW)
Remount system failed !
even when I want to delete the recovery I have the same message.
I had another worry after this update, the phone will reboot to the sony logo I insert my SD card, as soon as I removed the phone starts normally, but once the main menu, I deliver my SD card is detected and I can access to my music.
I do not know if this problem is related to the failure of the installation apk XZRecovery.
If you have a solution to these problems I'm interested.
Click to expand...
Click to collapse
Have you wiped the recovery from the phone?
Edit: Might be able to help you.
Download XZdual recovery zip file from here
Use this application to flash the recovery on phone itself
As you don't have working USB download required files on PC and mail yourself
androidtweaker1 said:
Have you wiped the recovery from the phone?
Edit: Might be able to help you.
Download XZdual recovery zip file from here
Use this application to flash the recovery on phone itself
As you don't have working USB download required files on PC and mail yourself
Click to expand...
Click to collapse
I just did a wipe Data, Wipe Dalvik Cache and Cache was necessary to install the update but wipe cache failed, but I still continued with the installation of the ROM.
"Remounting system (RW)
Remount system failed! "
I feel that there is a problem in mounting the read / write system.
MakeBelive said:
I just did a wipe Data, Wipe Dalvik Cache and Cache was necessary to install the update but wipe cache failed, but I still continued with the installation of the ROM.
"Remounting system (RW)
Remount system failed! "
I feel that there is a problem in mounting the read / write system.
Click to expand...
Click to collapse
were u able to install the recovery again from the instructions I gave?
androidtweaker1 said:
were u able to install the recovery again from the instructions I gave?
Click to expand...
Click to collapse
I'm really sorry I have not seen your said I'll try it right away. Thank you.
It's good, I download archive XZDualRecovery 2.7 BETA and I installed the app Rashr - The Android mobile Flash-Tool, the application my request to make a backup I agreed.
I know not too use too be app, can you help me?
MakeBelive said:
I know not too use too be app, can you help me?
Click to expand...
Click to collapse
Télécharger le XZ double récupération à partir du lien que j'ai donné dans le post précédent
Transférer à votre appareil, comme votre clé USB n'est pas électronique travaille la récupération pour vous.
Téléchargez l'application récupération de clignotant de playstore
Ouvrez l'application, sélectionnez récupération flash.
Après cela, sélectionnez le fichier zip XZ double de récupération
Récupération clignotant devrait commencer
---------- Post added at 04:00 PM ---------- Previous post was at 03:57 PM ----------
MakeBelive said:
I know not too use too be app, can you help me?
Click to expand...
Click to collapse
Après avoir téléchargé le XZ double récupération extraire le fichier img. Du fichier zip et de le transférer sur votre téléphone utiliser le fichier img. Pour clignotant
androidtweaker1 said:
Télécharger le XZ double récupération à partir du lien que j'ai donné dans le post précédent
Transférer à votre appareil, comme votre clé USB n'est pas électronique travaille la récupération pour vous.
Téléchargez l'application récupération de clignotant de playstore
Ouvrez l'application, sélectionnez récupération flash.
Après cela, sélectionnez le fichier zip XZ double de récupération
Récupération clignotant devrait commencer
---------- Post added at 04:00 PM ---------- Previous post was at 03:57 PM ----------
Après avoir téléchargé le XZ double récupération extraire le fichier img. Du fichier zip et de le transférer sur votre téléphone utiliser le fichier img. Pour clignotant
Click to expand...
Click to collapse
You know the forum rules, post on english please because this thread can be helpful for somebody else too.
androidtweaker1 said:
Télécharger le XZ double récupération à partir du lien que j'ai donné dans le post précédent
Transférer à votre appareil, comme votre clé USB n'est pas électronique travaille la récupération pour vous.
Téléchargez l'application récupération de clignotant de playstore
Ouvrez l'application, sélectionnez récupération flash.
Après cela, sélectionnez le fichier zip XZ double de récupération
Récupération clignotant devrait commencer
---------- Post added at 04:00 PM ---------- Previous post was at 03:57 PM ----------
Après avoir téléchargé le XZ double récupération extraire le fichier img. Du fichier zip et de le transférer sur votre téléphone utiliser le fichier img. Pour clignotant
Click to expand...
Click to collapse
I put it on my SD card, I selected the recovery option and Other from storage and I select the img file that I put on my SD card. it is his?
MakeBelive said:
I put it on my SD card, I selected the recovery option and Other from storage and I select the img file that I put on my SD card. it is his?
Click to expand...
Click to collapse
Yes do the thing you mentioned now
---------- Post added at 04:33 PM ---------- Previous post was at 04:33 PM ----------
neoxx3m said:
You know the forum rules, post on english please because this thread can be helpful for somebody else too.
Click to expand...
Click to collapse
Noted :good:
androidtweaker1 said:
Yes do the thing you mentioned now
---------- Post added at 04:33 PM ---------- Previous post was at 04:33 PM ----------
Noted :good:
Click to expand...
Click to collapse
I unzip the archive in the folder => rashr / recoveries but then he asked me to select a subdirectory among those present in the unzip folder.
Which folder is located img file?
I grieve you take me for an idiot but I especially do not want to miss the operation,
MakeBelive said:
I unzip the archive in the folder => rashr / recoveries but then he asked me to select a subdirectory among those present in the unzip folder.
Which folder is located img file?
I grieve you take me for an idiot but I especially do not want to miss the operation,
Click to expand...
Click to collapse
I don't assume anything about you :highfive:
you extract the file in PC after that transfer the img file to SD let me know if you need any help
androidtweaker1 said:
I don't assume anything about you :highfive:
you extract the file in PC after that transfer the img file to SD let me know if you need any help
Click to expand...
Click to collapse
I unzip the archive on my pc, I find in the subdirectory kernels these img files => philz_touch_6.12.8-honami.img
************* philz_touch_6.12.8-huashan.img
************* philz_touch_6.12.8-mint.img
************* philz_touch_6.12.8-togari.img
************* xzdrkkleak.img
MakeBelive said:
I unzip the archive on my pc, I find in the subdirectory kernels these img files => philz_touch_6.12.8-honami.img
************* philz_touch_6.12.8-huashan.img
************* philz_touch_6.12.8-mint.img
************* philz_touch_6.12.8-togari.img
************* xzdrkkleak.img
Click to expand...
Click to collapse
Okay, gimme 5 mins to sort this out :good::highfive:
---------- Post added at 07:02 PM ---------- Previous post was at 06:54 PM ----------
androidtweaker1 said:
I don't assume anything about you :highfive:
you extract the file in PC after that transfer the img file to SD let me know if you need any help
Click to expand...
Click to collapse
Extract xzdrkkleak.img
transfer it to SD and flash
androidtweaker1 said:
Okay, gimme 5 mins to sort this out :good::highfive:
---------- Post added at 07:02 PM ---------- Previous post was at 06:54 PM ----------
Extract xzdrkkleak.img
transfer it to SD and flash
Click to expand...
Click to collapse
Ok, I have a warning message => Flashing Recovery System on this devices Will Change the FOTAKernel (replacement score) Will this only work if your kernel supporting it (Review: The most Custom Kernel and ROM does it).
I not understand this message.
MakeBelive said:
Ok, I have a warning message => Flashing Recovery System on this devices Will Change the FOTAKernel (replacement score) Will this only work if your kernel supporting it (Review: The most Custom Kernel and ROM does it).
I not understand this message.
Click to expand...
Click to collapse
click ok
androidtweaker1 said:
click ok
Click to expand...
Click to collapse
I wanted to reboot into recovery but the phone to reboot normally.
MakeBelive said:
I wanted to reboot into recovery but the phone to reboot normally.
Click to expand...
Click to collapse
turn off the phone
press power button
after vibration press volume up and down keys alternately
it will boot to recovery
---------- Post added at 08:02 PM ---------- Previous post was at 07:41 PM ----------
MakeBelive said:
I wanted to reboot into recovery but the phone to reboot normally.
Click to expand...
Click to collapse
any update
androidtweaker1 said:
turn off the phone
press power button
after vibration press volume up and down keys alternately
it will boot to recovery
---------- Post added at 08:02 PM ---------- Previous post was at 07:41 PM ----------
any update
Click to expand...
Click to collapse
I could not boot into recovery mode, I tried several times, the app is compatible with rashr xperia Z.
Do not flash anything that alters or replaces your fotakernel unless your bootloader is unlocked. You will soft brick your phone and will need to use Flashtool or SUS to recover it, which you cannot with a broken USB port.
My advice - Get your USB port repaired. You will need it at some point if you're flashing roms/mods as something WILL go wrong that requires you to connect to a PC. ?
Sent from my C6603 using Tapatalk
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).
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)
Greetings.
I would like to know what would be the best option to root this terminal. I'm thinking of switching to the Miuimix rom but maybe someone can advise me on a less intrusive way. I want to do it mainly so that I can make complete backups, with the applications and their data; and that you do not have to be with a little notebook writing down passwords.
Thank you all very much in advance.
root is root, rom is rom...
for rooting you must enable magisk after fashing your rom (miui, arrow, lineage... is not important, is the same )
i raccomend flashing last version of magisk
after system boot, from magisk manager enable zygist and flash module safety 2.2.1 for passing safety net
I was commenting about the Miuimix ROM because it is the one that practically comes pre-rooted and in two steps you already have it; but I don't like its appearance very much; I am also very comfortable with xiaomi.eu even if it is a highly criticized rom.
How do I flash magisk? There is no recovery that works well on Android 12.
Is there any tutorial to do it?
I've been searching the forum and what little there is on the subject doesn't work for everyone.
Thanks for everything again.
gintony said:
How do I flash magisk? There is no recovery that works well on Android 12.
Is there any tutorial to do it?
I've been searching the forum and what little there is on the subject doesn't work for everyone.
Thanks for everything again.
Click to expand...
Click to collapse
recovery for a12 work, you must flash last twrp... only problem with this is that your internal memory is not visible... you must have all on external sd for flashing.. rom, magisk etc.. but is simple... usually when you enter in recovery select external sd, flash rom, flash magisk (magisk is .apk, rename.zip before flashing), format and reboot..
aleMarvel said:
la recuperación para el trabajo a12, debe flashear el último twrp ... el único problema con esto es que su memoria interna no está visible ... debe tener todo en sd externo para flashear ... rom, magisk, etc. pero es simple... Por lo general, cuando ingrese a la recuperación, seleccione sd externa, flash rom, flash magisk (magisk es .apk, rename.zip antes de flashear), formatee y reinthanks
Click to expand...
Click to collapse
Gracias por tu respuesta.