Database Info

How to root my Moto G 3 with Android version 6.0.1

I have seen threads but nothing related to the 6.0.1 version. Please do help

jerry94 said:
I have seen threads but nothing related to the 6.0.1 version. Please do help
Click to expand...
Click to collapse
6.0 or 6.0.1... no difference, must do manual systemless install

acejavelin said:
6.0 or 6.0.1... no difference, must do manual systemless install
Click to expand...
Click to collapse
how to do that?

Already answered google it
Sent from my MotoG3 using Tapatalk

flash supersu zip in twrp.. to simple

HelpMeruth said:
flash supersu zip in twrp.. to simple
Click to expand...
Click to collapse
This doesn't work... if you just flash the latest SuperSU in TWRP, a 3rd/4th Gen Moto device will fail to boot because SuperSU's install script does not recognize that this device must have a systemless install. You must start TWRP and before flashing go to Advanced - Terminal and enter "echo SYSTEMLESS=true>>/data/.supersu" so the SuperSU install script will parse the file and know it has to do a systemless install.

jerry94 said:
I have seen threads but nothing related to the 6.0.1 version. Please do help
Click to expand...
Click to collapse
Check this tutorial
forum.xda-developers.com/2015-moto-g/general/guide-install-twrp-root-xposed-t3294588
Or this one(better)
forum.xda-developers.com/2015-moto-g/general/root-how-to-root-moto-g-2015-android-t3320113e

Nikos dima said:
Check this tutorial
forum.xda-developers.com/2015-moto-g/general/guide-install-twrp-root-xposed-t3294588
Or this one(better)
forum.xda-developers.com/2015-moto-g/general/root-how-to-root-moto-g-2015-android-t3320113e
Click to expand...
Click to collapse
C:\Program Files\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.313s]
booting...
FAILED (remote failure)
finished. total time: 0.391s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (8122 KB)...
OKAY [ 0.313s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.344s
C:\Program Files\Minimal ADB and Fastboot>
I tried to flash Twrp but iam getting this

Root 6.0.1
jerry94 said:
I have seen threads but nothing related to the 6.0.1 version. Please do help
Click to expand...
Click to collapse
I was also facing the same problem First of all u need to unlock bootloader then at bootloader "fastboot boot recovery.img" change your name twrp to recovery after that you will gets boot into twrp from there flash https://www.androidfilehost.com/?fid=24269982087018189 this file
Hit like if I'm helped you

I followed all the steps of unlocking the bootloader using AdB and Fastboot. After I enter my unique key it sends some commands rather than showing that the device is unlocked.

jerry94 said:
I followed all the steps of unlocking the bootloader using AdB and Fastboot. After I enter my unique key it sends some commands rather than showing that the device is unlocked.
Click to expand...
Click to collapse
Check this video to unlock bootloader. https://youtu.be/BCRpCEtcZ_c and if you are getting errors just search in google for solution

jerry94 said:
I followed all the steps of unlocking the bootloader using AdB and Fastboot. After I enter my unique key it sends some commands rather than showing that the device is unlocked.
Click to expand...
Click to collapse
Can you screenshot it and post it here?
Sent from my Motorola XT1575 using XDA Labs

acejavelin said:
Can you screenshot it and post it here?
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
I have unlocked the bootloader and flashed twrp now. It opened the twrpmode.i booted the fone.But after that while opening the recovery mode in fastboot it is showing 'no command'

jerry94 said:
I have unlocked the bootloader and flashed twrp now. It opened the twrpmode.i booted the fone.But after that while opening the recovery mode in fastboot it is showing 'no command'
Click to expand...
Click to collapse
If you are getting "No command" that is not TWRP, it is the factory recovery...
When you install TWRP with `fastboot flash recovery twrp.img` you must start TWRP, allow it to make changes to the system, then go to TWRP's reboot menu and select Reboot to Recovery. This action will permanently set TWRP as the recovery, otherwise the OS has a script which will restore the stock recovery on boot.
Proper way to flash TWRP, in my opinion, on a new (to TWRP) Moto device once the bootloader is unlocked:
1) fastboot boot twrp.img
2) do NOT tick "Never show this screen again on boot" and select Keep Read Only button
3) do a complete backup in TWRP, preferably to the microSD card. Make a copy of this backup and store it away safely for possible future use and keep a copy on the device if possible
4) reboot into bootloader
5) fastboot flash recovery twrp.img
6) start Recovery (TWRP)
7) tick "Never show this screen again on boot" and swipe to allow modification
8) go to Reboot and select Recovery **IMPORTANT** this step allows TWRP to "lock" itself in and prevent the OS from replacing it with the stock recovery again
9) TWRP should start again, and it should not prompt you at all and just go to the TWRP menu
10) Do what you wish in TWRP (flash SuperSU, install ROM, or whatever) if anything
11) Reboot - System
Replace twrp.img with the appropriate filename from http://twrp.me for the device. If you have already made changes to the system, just start at step #4

acejavelin said:
<< Proper way to flash TWRP, in my opinion, on a new (to TWRP) Moto device once the bootloader is unlocked:
1) fastboot boot twrp.img
2) do NOT tick "Never show this screen again on boot" and select Keep Read Only button
3) do a complete backup in TWRP, preferably to the microSD card. Make a copy of this backup and store it away safely for possible future use and keep a copy on the device if possible
4) reboot into bootloader
5) fastboot flash recovery twrp.img
6) start Recovery (TWRP)
7) tick "Never show this screen again on boot" and swipe to allow modification
..
..
.. >>
Click to expand...
Click to collapse
I've seen these steps a few times (OK, many times, with all the threads started on this exact question).
I'm just curious.. Why does it work? i.e. How is rebooting into TWRP without installing it, then immediately turning around, installing it, and running it... how is that different from just installing it first thing and running it? Like, what's going on internally that makes those two things different?
Thanks x
Sent from my Nexus 7 using XDA Labs

beachfl said:
I've seen these steps a few times (OK, many times, with all the threads started on this exact question).
I'm just curious.. Why does it work? i.e. How is rebooting into TWRP without installing it, then immediately turning around, installing it, and running it... how is that different from just installing it first thing and running it? Like, what's going on internally that makes those two things different?
Thanks x
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
OK... Booting TWRP without installing has nothing to do with functionality of TWRP, it is only to get a clean backup or if you want to root without installing TWRP. TBH, this entire piece is optional and could be skipped, but if you can get a clean backup it sure can makes things easier down the road.
When you flash TWRP, it is flashed... it is written into the recovery partition of your device, but if you start the operating system at this point there is a script (or something, going from my memory of the Nexus 4 which has a script that sat in /system that ran on each boot, so this has been an issue for a while in some devices) that re-writes the recovery it isn't "official". But, but flashing TWRP, allowing it to make changes, then rebooting into TWRP again, it gives TWRP a chance to do something that stops the restoring to official process to stop. I am not sure of the specific details, and I am not sure it really matters, but it works.

acejavelin said:
... Booting TWRP without installing has nothing to do with functionality of TWRP.. .
Click to expand...
Click to collapse
I get that thank you!
Sent from my Nexus 7 using XDA Labs

[SOLVED] No boot in TWRP possible. Under no circumstances...

I have a strange problem with my brand new Mi Mix 2s.
My procedure from the beginning:
Unlook using tool from Xiaomi. For this I had to wait 72h.
Subsequently, the unlooking was considered successful.
For this I used my notebook with Windows7 (no VM).
Now I got the needed files and want to start with the installation of TWRP.
I also use my notebook but with Linux, my everyday operating system.
I have set the phone to fastboot mode (vol-down + power).
With fastboot devices you can find the phone. But commands like flash or boot end in a frozen console.
Unusual. Now I try it again in Windows7 (dualboot). The same problem.
Then I try the Windows10 game computer of my son.
The commands are confirmed as successful.
But in fact nothing happens. Nothing is flashed and I am not in the TWRP to boot.
Here the console output:
Code:
#[twrp.ing = twrp-3.2.3-0-polaris.img]
F:\platform-tools>fastboot boot twrp.img
creating boot image...
creating boot image - 43386880 bytes
Downloading 'boot.img' OKAY [ 0.914s]
booting OKAY [ 0.071s]
Finished. Total time: 1.051s
#[black screen]
F:\platform-tools>fastboot devices
19cf4510 fastboot
F:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (42368 KB) OKAY [ 0.951s]
Writing 'recovery' OKAY [ 0.201s]
Finished. Total time: 1.165s
F:\platform-tools>fastboot devices
19cf4510 fastboot
F:\platform-tools>fastboot boot twrp.img
creating boot image...
creating boot image - 43386880 bytes
Downloading 'boot.img' OKAY [ 0.910s]
booting FAILED (remote: 'Failed to load/authenticate boot image: 00000050')
Finished. Total time: 1.009s
F:\platform-tools>fastboot devices
19cf4510 fastboot
F:\platform-tools>fastboot reboot
Rebooting
Finished. Total time: 0.004s
#[reboot]
Unfortunately, I am not aware of any possibilities to solve the problem further.
Does anyone have suggestions or ideas?

Which TWRP are you flashing? Are you sure that it is the proper file for mix 2s?
What happens when you reboot the phone after flashing recovery with vol+ and power?
Flash twrp then restart manually holding vol+ and power buttons.

malimukk said:
Which TWRP are you flashing? Are you sure that it is the proper file for mix 2s?
What happens when you reboot the phone after flashing recovery with vol+ and power?
Flash twrp then restart manually holding vol+ and power buttons.
Click to expand...
Click to collapse
Yes. It is this version: https://eu.dl.twrp.me/polaris/
I have tried your tip. Does not work either.

Can it be helpful to close the bootloader and perform unloocking again?
How is the usual way to lock the device again? Using fastboot, or are there other solutions?
Can I really reopen the bootloader afterwards?
Can someone confirm that multiple opening is possible with the MIunlock tool?

yabow said:
Can it be helpful to close the bootloader and perform unloocking again?
How is the usual way to lock the device again? Using fastboot, or are there other solutions?
Can I really reopen the bootloader afterwards?
Can someone confirm that multiple opening is possible with the MIunlock tool?
Click to expand...
Click to collapse
Yes you can unlock again. I've done it myself.
I am not sure what is happening in your situation. Which MIUI version are you running?
I'd suggest you to flash a more recent version of MIUI with the Mi Flash tool.
Perhaps MIUI developer 8.12.27 version.
Let it boot to system after flashing
Then turn off, flash twrp, disconnect cable,
reboot from fastboot with Power and Vol+
No other ideas honestly

malimukk said:
Yes you can unlock again. I've done it myself.
I am not sure what is happening in your situation. Which MIUI version are you running?
I'd suggest you to flash a more recent version of MIUI with the Mi Flash tool.
Perhaps MIUI developer 8.12.27 version.
Let it boot to system after flashing
Then turn off, flash twrp, disconnect cable,
reboot from fastboot with Power and Vol+
No other ideas honestly
Click to expand...
Click to collapse
I have
MIUI-Version 10.2.1.0 GLOBAL
Model M1803D5XA
and using
fastboot version 28.0.1-4986621
on Windows10
I have tried with Linux, but here the comandline hangs and nothing happends...
Do you think i have to use a developer ROM? This can be a problem?

yabow said:
I have
MIUI-Version 10.2.1.0 GLOBAL
Model M1803D5XA
and using
fastboot version 28.0.1-4986621
on Windows10
I have tried with Linux, but here the comandline hangs and nothing happends...
Do you think i have to use a developer ROM? This can be a problem?
Click to expand...
Click to collapse
For me sometimes fastboot just does not want to work on my laptop, then I switch usb ports and it magically works again. It is usually an issue on the PC. try abother cable as well. You cab also try to uninstall your adb/fastboot drivers and install these: https://forum.xda-developers.com/showthread.php?t=2588979
Preferably on the Windows10 machine you have, as it seems closest to working.
Miui version should not be relevant, but it might be that yours is somehow messed up. I would suggest you to avoid using the mi flash tool for now as it uses fastboot to flash the different images and it might cause other issues as clearly fastboot is somehow broken. You can try to update to a dev rom thorough the phone update app?
Btw when you do fastboot boot twrp.img you have to keep the cable plugged in

Didn't change anything. Damn it.

check this
read this page (need a translater)
in MiMix2s_Xiaomi.eu_Firmware yoo find a install_TWRP.bat in folder 02_TWRP
exchange and rename your new twrp to the name in the folder
https://tradingshenzhen.com/de/cont...sh-tutorial-global-firmware-xiaomieu-firmware

So, I tried some TWRP versions (v15, v14, and others) to get the black-screen error again and again. Version v8 finally allowed me to boot into TWRP. Yeah!
Before I closed the bootloader,
got a message about a destroyed device,
reloaded the stock-ROM with MI-flash,
booted TWRP v8 from this thread,
only saw cryptic files and just used an OTG adapter to install more *imgs and *zips.
Not everything works as it should yet, but it will...
Thanks for your help.

yabow said:
So, I tried some TWRP versions (v15, v14, and others) to get the black-screen error again and again. Version v8 finally allowed me to boot into TWRP. Yeah!
Before I closed the bootloader,
got a message about a destroyed device,
reloaded the stock-ROM with MI-flash,
booted TWRP v8 from this thread,
only saw cryptic files and just used an OTG adapter to install more *imgs and *zips.
Not everything works as it should yet, but it will...
Thanks for your help.
Click to expand...
Click to collapse
Your storage is encrypted, that's why you have the "cryptic files".
TWRP v8 can not decrypt your storage, the latest version can though

[SOLVED]Oneplus 7 stuck in fastbootmode after trying to restore a backup from TWRP

My bootloader is unlocked, I was rooted with Magisk and i had twrp recovery installed as well. A few modules were installed and i had made a backup about 3 weeks ago. Yesterday i tried restoring the backup in twrp and it seemed to restore properly without errors . When i pressed reboot in the end the phone went to the fastboot mode screen and has since been there. All i can do is turn it off and regardless of what i pick, (START, Restart Bootloader, Recovery mode) it just starts into fastboot mode. Confused as to what i should do now and why this happened in the first place. All the threads i found were only for the 7 pro so i didnt want to risk anything by following those. Please advice on what i should do.
Edit : The problem was solved by flashing the STOCK ROM for android 9 which is what i was on when the device was softbricked.

hi
Hi, download adb fastboot and twrp recovery image for guacamoleb. then open a new command prompt (CMD) in the same location and run the following commands:
Code:
fastboot flash recovery (file name of twrp that you download).img
after that by holding volume up + power reboot to twrp recovery that you just installed via adb fastboot command.
when you enter on twrp recovery, install twrp recovery zip, and magisk 19.3 zip (download and copy on phone storage first, after you enter on twrp when reboot, you can connect your phone with computer or USB that contain twrp recovery zip and magisk or copy to phone storage) after this step install twrp zip first than magisk and then reboot.
i hope i helped.
sorry for my english , is not my native language.

klediY said:
Hi, download adb fastboot and twrp recovery image for guacamoleb. then open a new command prompt (CMD) in the same location and run the following commands:
Code:
fastboot flash recovery (file name of twrp that you download).img
after that by holding volume up + power reboot to twrp recovery that you just installed via adb fastboot command.
when you enter on twrp recovery, install twrp recovery zip, and magisk 19.3 zip (download and copy on phone storage first, after you enter on twrp when reboot, you can connect your phone with computer or USB that contain twrp recovery zip and magisk or copy to phone storage) after this step install twrp zip first than magisk and then reboot.
i hope i helped.
sorry for my english , is not my native language.
Click to expand...
Click to collapse
Thank you for the reply. Unfortunately i am stuck in the very first step. After typing C:\adb\Oneplus 7>fastboot flash recovery twrp-3.3.1-1-guacamoleb.img in cmd the following happens
target reported max download size of 805306368 bytes
sending 'recovery' (56612 KB)...
OKAY [ 1.220s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.228s
I have tried using fastboot boot recovery instead in cmd. The following error comes up
cannot load 'recovery': No such file or directory.
I have checked whether the device is connected by typing in fastboot devices and it shows as connected. Any other suggestions will be helpful.

wolfsbane169 said:
Thank you for the reply. Unfortunately i am stuck in the very first step. After typing C:\adb\Oneplus 7>fastboot flash recovery twrp-3.3.1-1-guacamoleb.img in cmd the following happens
target reported max download size of 805306368 bytes
sending 'recovery' (56612 KB)...
OKAY [ 1.220s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.228s
I have tried using fastboot boot recovery instead in cmd. The following error comes up
cannot load 'recovery': No such file or directory.
I have checked whether the device is connected by typing in fastboot devices and it shows as connected. Any other suggestions will be helpful.
Click to expand...
Click to collapse
Something similar happened to me, I was on OOS 10 stable and wiping the system and data from TWRP got in fastboot mode without being possible to do anything else. The way that I solved was flashing from fastboot the OOS 10 stable posted rom here: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478 This will erase all your data but you will unbrick your phone.
One important thing, if you are on android 10 you can't flash TWRP via fasboot, maybe that's the problem you are having right now.
Hope this helps

ryupunk said:
Something similar happened to me, I was on OOS 10 stable and wiping the system and data from TWRP got in fastboot mode without being possible to do anything else. The way that I solved was flashing from fastboot the OOS 10 stable posted rom here: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478 This will erase all your data but you will unbrick your phone.
One important thing, if you are on android 10 you can't flash TWRP via fasboot, maybe that's the problem you are having right now.
Hope this helps
Click to expand...
Click to collapse
Ok so thank you for the help and you were right. Now i have an all new different problem. In a nutshell i flashed the stock ROM for android 9 while i was in android 10. I completely forgot you aren't supposed to do that. As a result i cant even access fastboot mode now. Can you please tell me how i can fix this problem?

wolfsbane169 said:
Ok so thank you for the help and you were right. Now i have an all new different problem. In a nutshell i flashed the stock ROM for android 9 while i was in android 10. I completely forgot you aren't supposed to do that. As a result i cant even access fastboot mode now. Can you please tell me how i can fix this problem?
Click to expand...
Click to collapse
I think that you will need to use the MSM tool, it looks like you have a hard brick, the good news is that oneplus devices can be revived in almost all cases. I have never used the tool but I found some posts that might help you. Best of luck!
XDA Oneplus 7 thread
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
XDA Oneplus 7 pro thread
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Oneplus forum guide
https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/

ryupunk said:
I think that you will need to use the MSM tool, it looks like you have a hard brick, the good news is that oneplus devices can be revived in almost all cases. I have never used the tool but I found some posts that might help you. Best of luck!
XDA Oneplus 7 thread
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
XDA Oneplus 7 pro thread
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Oneplus forum guide
https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/
Click to expand...
Click to collapse
I have tried using it but the problem is that MSM download tool does not detect my phone. i have uninstalled and let windows automatically update qualcomm drivers. I have also made windows manually install them after uninstalling.

realme 5i twrp command not working ( fastboot boot twrp.img )

i am trying to root realme 5i. i successfully unlock bootloader. fastboot flash recovery twrp.img working fine.
but when i try command fastboot boot twrp.img it shows
PS C:\Users\hpp\Desktop\adbfastboot> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.415s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.421s
please guide me how to install twpr on m phone . please help

ad_nannnn said:
i am trying to root realme 5i. i successfully unlock bootloader. fastboot flash recovery twrp.img working fine.
but when i try command fastboot boot twrp.img it shows
PS C:\Users\hpp\Desktop\adbfastboot> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.415s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.421s
please guide me how to install twpr on m phone . please help
Click to expand...
Click to collapse
Also same problem ... But after use another twrp it's shown success .. but still no working ... In commed section it's saw successful ... But when boot on recovery mood my phone it's no working ..no recovery option

Yeah right me too

Somehow Wrong Command
ad_nannnn said:
...
But, when I try command fastboot boot twrp.img
...
FAILED (remote: unknown command)
finished. total time: 1.421s
please guide me how to install twpr on m phone . please help
Click to expand...
Click to collapse
After flashing a Custom Recovery, If you want to boot to recovery, the actual command through fastboot is
Code:
fastboot boot recovery
or also in the bootloader screen you can press vol+ button untill you see Recovery mode then hit Power button.
The most important point is After flashing a Custom Recovery you must flash the vbmeta with Verity command To make it permanent. Otherwise it'll just revert back to Stock Recovery. (This method only works in Color Os (ie., Android 9), for RealmeUI you need additional thing to do)

iamvijaypushparaj said:
After flashing a Custom Recovery, If you want to boot to recovery, the actual command through fastboot is
Code:
fastboot boot recovery
or also in the bootloader screen you can press vol+ button untill you see Recovery mode then hit Power button.
The most important point is After flashing a Custom Recovery you must flash the vbmeta with Verity command To make it permanent. Otherwise it'll just revert back to Stock Recovery. (This method only works in Color Os (ie., Android 9), for RealmeUI you need additional thing to do)
Click to expand...
Click to collapse
Where do we get this vbmeta from? I'm having the same problem, that after flashing twrp.img it just reboots back into fastboot mode. Is this because Secure Boot is enabled and does vbmeta disable that?

realme 5 tg
doveman said:
Where do we get this vbmeta from? I'm having the same problem, that after flashing twrp.img it just reboots back into fastboot mode. Is this because Secure Boot is enabled and does vbmeta disable that?
Click to expand...
Click to collapse
realme 5 telegram group

CjConvento said:
realme 5 telegram group
Click to expand...
Click to collapse
iamvijaypushparaj posted it here https://forum.xda-developers.com/showpost.php?p=83251175&postcount=16 but unfortunately it still just boots into fastboot whatever I try.

doveman said:
iamvijaypushparaj posted it here https://forum.xda-developers.com/showpost.php?p=83251175&postcount=16 but unfortunately it still just boots into fastboot whatever I try.
Click to expand...
Click to collapse
After flashing recovery via cmd, you will go back to fastboot on your screen. Navigate the volume buttons til it show Recovery mode on top of the screen. Then press power button and it will boot to recovery.

jokezerious said:
After flashing recovery via cmd, you will go back to fastboot on your screen. Navigate the volume buttons til it show Recovery mode on top of the screen. Then press power button and it will boot to recovery.
Click to expand...
Click to collapse
It turned out the problem was Orangefox. With TWRP it booted into Recovery fine when I selected that option but with Orangefox it would just reboot into fastboot. I'll try some different versions of Orangefox sometime but for now my biggest problem is that it's impossible to set a Lock Screen PIN/Password, let alone use FingerPrint. It seems unlocking the bootloader breaks the security settings.

whats orangefox ? did u found a fix !

I rooted 5i and no use your code. I follow this video
Some code:
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot devices
fastboot flash recovery REALME5i.img
fastboot flash vbmeta vbmeta.img
adb reboot recovery

[RECOVERY][anne][OFFICIAL][3.4.0-0] TWRP for Huawei P20 Lite

Official TWRP for Huawei P20 Lite
Working
Code:
[CENTER]* Touchscreen
* Adb
* Backup
* Wipe
* File manager
* MTP
[/CENTER]
Not Working
Code:
[CENTER]You tell me
[/CENTER]
Installation
Code:
[CENTER]* put your phone in fastboot mode and type
"fastboot flash recovery_ramdisk <grab_here_the_img>"
* reboot
[/CENTER]
Download
Code:
[CENTER]
[URL="https://twrp.me/huawei/huaweip20lite.html"]TWRP Official page[/URL]
[URL="https://sourceforge.net/projects/darkjoker360-developements/files/Huawei/P20%20Lite/TWRP/"]DarkJoker360 sourceforge[/URL]
[/CENTER]
Please support my work, it's very important! Thanks
DONATIONS
Regards !​

Reserved

Hi! Is this for emui 9?

there are few image installation options, only kernel, oeminfo, ramdisk, recovery_ramdisk, system image, vendor image. Ergo it's impossible install TWRP over eRecovery, which is quite important ...
But that's just my opinion

TureX said:
Hi! Is this for emui 9?
Click to expand...
Click to collapse
yes

Hello guys, I would like to inform you that this recovery is now official !

I'm a noob. What's the solution for command failed during installation?
U:\platform-tools_r30.0.4-windows\platform-tools>fastboot flash recovery_ramdisk twrp.img
Sending 'recovery_ramdisk' (13524 KB) OKAY [ 0.345s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
U:\platform-tools_r30.0.4-windows\platform-tools>

JairoAV25 said:
I'm a noob. What's the solution for command failed during installation?
U:\platform-tools_r30.0.4-windows\platform-tools>fastboot flash recovery_ramdisk twrp.img
Sending 'recovery_ramdisk' (13524 KB) OKAY [ 0.345s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
U:\platform-tools_r30.0.4-windows\platform-tools>
Click to expand...
Click to collapse
Bootloader and FRP unlocked (both red on Fastboot screen)?

Hello , i flashed con ram-disk but always boots on erecovery, theres way to boot on twrp recovery??

Hello!!
I install twrp 3.4 correctly. I tried to make a backup but it failed. "Can not create 'external_sd/TWRP' folder (Permission denied). Tested on internal memory and SD, same failure.

Hello.
I flashed the recovery without any error...
"target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (13524 KB)...
OKAY [ 0.393s]
writing 'recovery_ramdisk'...
OKAY [ 0.143s]
finished. total time: 0.537s"
but when I reboot and try to boot in recovery is booting in eRecovery.
I'm running EMUI9.1
Does anybody have a similar problem?
---------- Post added at 07:08 PM ---------- Previous post was at 06:25 PM ----------
harryfokker said:
Hello , i flashed con ram-disk but always boots on erecovery, theres way to boot on twrp recovery??
Click to expand...
Click to collapse
Hello.
to enter in TWRP Recovery after installing it you need to:
- Turn your smartphone off
- Disconnect the usb cable
- Press volume up and power button and keep holding them till you see the Huawei logo.
- Release the buttons immediately you see Huawei logo.
- Wait some seconds to see the TWRP recovery logo.

Hi! When i install twrp i can't boot to the ROM cause he boot again on twrp , so i must reinstall stock erecovery to correctly boot. Why ? Is there any way to keep twrp installed?
Thanks

TureX said:
Hi! When i install twrp i can't boot to the ROM cause he boot again on twrp , so i must reinstall stock erecovery to correctly boot. Why ? Is there any way to keep twrp installed?
Thanks
Click to expand...
Click to collapse
Wipe data from erecovery is needed.

DarkJoker360 said:
Wipe data from erecovery is needed.
Click to expand...
Click to collapse
Hi! Thank you to reply, so i need to wipe with erecovery even when i currently run los 16?

TureX said:
Hi! Thank you to reply, so i need to wipe with erecovery even when i currently run los 16?
Click to expand...
Click to collapse
No, the wipe of erecovery is meant to replace twrp format data

DarkJoker360 said:
No, the wipe of erecovery is meant to replace twrp format data
Click to expand...
Click to collapse
OK but if i keep installed twrp i can't boot cause i get a loop( only reboot to twrp)

TureX said:
OK but if i keep installed twrp i can't boot cause i get a loop( only reboot to twrp)
Click to expand...
Click to collapse
It won't boot loop you wipe data from twrp after the installation of los

n.sim said:
It won't boot loop you wipe data from twrp after the installation of los
Click to expand...
Click to collapse
Ye i know , i'm using los but after wipe with erecovery and boot to the ROM , if i would keep twrp instead erecovery that bootloop in to the twrp for each action i do( reboot , shut down and shutdown througt the power button boot only on twrp)

So no way to keep installed twrp instead recovery? Cause if i keep twrp , i got bootloop on twrp ( i cannot boot on the rom until reflash stock recovery_ramdisk)

..