Database Users

[Q] Bootloop on rebooting into recovery?

I rooted through cyanogenmod method, then unrooted (went back to stock 2.2.1) with the stock P15100.zip. I had another hardware issue with my phone (microphone failing) and thought it could be software. The mic was still broken and I wanted to root again so went through cyanogen method again flashing CWM. I was able to reboot once into recovery to flash synth's ICS. When I try to fully reboot, then reboot into recovery again, I got bootloop for a minute, then eventually booted into the rom. I tried flashing 4ext and same issue. I tried flashing CWM again from app and still have the issue. I'm just guessing recovery is corrupted and it needs to be formatted and re-flashed? Anyone know how to format recovery via adb and then push cwm or 4ext?
Any help much is appreciated.

You can flash a recovery through terminal emulator. As I recall, the commands are:
su
flash_image recovery recoveryname.img
Sounds like you might be having bigger issues, though. I hope your recovery partition isn't going kaput.
Jack_R1 might have an idea.

Man, Jack_R1 is still around these parts? But as for OP, definitely sounds like your recovery is corrupt. What you want to do is if you have any fastboot/ADB knowledge is you're going to want to download the recovery.img of your choice, name it "recovery.img" then place it in your ADB folder, plug your phone in in Fastboot mode and then type in the following commands:
Code:
Fastboot devices
it should show you a number followed by "fastboot" after this type
Code:
fastboot delete recovery
it should spew out how long it took followed by "recovery deleted" or something like that.
lastly you're going to flash the recovery that you downloaded. Type
Code:
fastboot flash recovery recovery.img
That should do it! PM me if you need any other help

Yes, I still visit here
OP, what phone do you have? You're writing a wrong name for PD15IMG.
In any case, if you indeed have PD15IMG - find "root for S-OFF users" thread in Development, get the PD15IMG with CWM from there, flash it just like you flashed return-to-stock package, and boot into recovery. If it doesn't work - it means that it's not the recovery that's corrupted.
And I suspect that you're just not understanding correctly what your phone does, and/or not actually booting into recovery.

Nicgraner said:
Man, Jack_R1 is still around these parts? But as for OP, definitely sounds like your recovery is corrupt. What you want to do is if you have any fastboot/ADB knowledge is you're going to want to download the recovery.img of your choice, name it "recovery.img" then place it in your ADB folder, plug your phone in in Fastboot mode and then type in the following commands:
Code:
Fastboot devices
it should show you a number followed by "fastboot" after this type
Code:
fastboot delete recovery
it should spew out how long it took followed by "recovery deleted" or something like that.
lastly you're going to flash the recovery that you downloaded. Type
Code:
fastboot flash recovery recovery.img
That should do it! PM me if you need any other help
Click to expand...
Click to collapse
I have used adb a bit (for root with cyanogen method). I'm guessing that the delete command will reformat the recovery partition? I'll give this a go when I get home and get back to ya. Thanks for the reply! Is there a way to download the 4ext recovery img file?
Edit:
I downloaded the CWM touch img and connected to the phone in fastboot. Was able to follow your instructions, but the command is erase not delete. When I put in the delete command it came up with the instructions and was able to figure it out. Flashed recovery and I can now boot into recovery every time from fastboot, terminal, adb, and from power prompt in rom! BOOYAH! Thanks a ton!

Jack_R1 said:
Yes, I still visit here
OP, what phone do you have? You're writing a wrong name for PD15IMG.
In any case, if you indeed have PD15IMG - find "root for S-OFF users" thread in Development, get the PD15IMG with CWM from there, flash it just like you flashed return-to-stock package, and boot into recovery. If it doesn't work - it means that it's not the recovery that's corrupted.
And I suspect that you're just not understanding correctly what your phone does, and/or not actually booting into recovery.
Click to expand...
Click to collapse
Hey Jack,
I have HTC Glacier. Was a typo for the PD15IMG name. I think I have a decent understanding of the phone, and most likely have a corrupted recovery partition. Seems that instead of just flashing a recovery over a recovery, I may need to reformat the partition and then flash? I'll try flashing the file you suggest and report back. If it is not the recovery that is corrupted, what else could be the issue? Possibly an issue with the bootloader not allowing the phone to boot into recovery? Thanks for the reply.

Flashing recovery isn't copying a file. When you flash IMG through bootloader, it is flashed just like what it is - a complete image. Formatting the partition doesn't do anything, since it has no "format" - the image flashed by the bootloader contains both the structure and the data, just like a CD/DVD image does, for example.
The possible options I can think of are:
1) Your recovery partition is physically bad - unlikely.
2) Your bootloader is corrupted - could possibly lead to you being unable to enter recovery.
3) Something that prevents your phone from entering recovery - i.e. a stuck button or something - or you're doing it wrong. I'm afraid that what you're describing as "phone bootloops for a minute and then boots a ROM" isn't really a bootloop - because these phones can't get out of bootloop on their own, if booting failed once - it'll fail always. Logcat can confirm this. I believe it's just the ROM that's booting normally when you try to enter recovery, so, in this case, since you didn't specify how exactly you're trying to enter recovery - it seems like you're either doing it wrong, or when you try to enter recovery you're not getting there.
To help people help you, please write down the exact way you're using when trying to enter recovery, and if you know more than one way - try them all (from bootloader, by adb reboot recovery, directly booting without flashing by "fastboot boot", etc). And post your HBOOT version.

Jack_R1 said:
Flashing recovery isn't copying a file. When you flash IMG through bootloader, it is flashed just like what it is - a complete image. Formatting the partition doesn't do anything, since it has no "format" - the image flashed by the bootloader contains both the structure and the data, just like a CD/DVD image does, for example.
The possible options I can think of are:
1) Your recovery partition is physically bad - unlikely.
2) Your bootloader is corrupted - could possibly lead to you being unable to enter recovery.
3) Something that prevents your phone from entering recovery - i.e. a stuck button or something - or you're doing it wrong. I'm afraid that what you're describing as "phone bootloops for a minute and then boots a ROM" isn't really a bootloop - because these phones can't get out of bootloop on their own, if booting failed once - it'll fail always. Logcat can confirm this. I believe it's just the ROM that's booting normally when you try to enter recovery, so, in this case, since you didn't specify how exactly you're trying to enter recovery - it seems like you're either doing it wrong, or when you try to enter recovery you're not getting there.
To help people help you, please write down the exact way you're using when trying to enter recovery, and if you know more than one way - try them all (from bootloader, by adb reboot recovery, directly booting without flashing by "fastboot boot", etc). And post your HBOOT version.
Click to expand...
Click to collapse
Sorry if I wasn't more descriptive. I really appreciate your help and everything you have done for this community. Seems the recovery was corrupted by the 4ext app. I was able to extract the recovery.img from the 4ext download and was able to flash it via fastboot. Everything boots properly now. HBoot is 0.85.2007 FYI. Thanks again!

[Official][Recovery][TWRP]TWRP For Xiaomi Redmi 4X

Team Win Recovery Project 3.x, or TWRP3.x 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.
*
* We are 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 features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Download : TWRP For Santoni
Source Device Tree: Device Tree For Building TWRP

Was using your twrp recovery on my old Lenovo A6000 Plus
Great to have you in the development of Redmi 4X/4 (India) - my new phone ?
Hope to see more development for this device from you
?

advanced wishes to you my brother...

Twrp Asking for password on start up which is not our screen lock password? Any suggestion to improve this ?( I dont want to reset my phone although)

rohpag said:
Twrp Asking for password on start up which is not our screen lock password? Any suggestion to improve this ?( I dont want to reset my phone although)
Click to expand...
Click to collapse
I also have same problem

rohpag said:
Twrp Asking for password on start up which is not our screen lock password? Any suggestion to improve this ?( I dont want to reset my phone although)
Click to expand...
Click to collapse
+1

Please provide the password?

I think this is because of dm-verity. Use the password or pattern that you have set on your phone.

just press cancel when it asking the password, then wipe DATA, this will bring your phone to factory reset and at next recovery boot twrp will not asking password anymore

cikenkari said:
Please provide the password?
Click to expand...
Click to collapse
password is ur lock screen password

The TWRP have a bug with ROM Backup, about Password in lockscreen.
The fix and the bug has been reported in the One Plus Forum:
https://forums.oneplus.net/threads/fix-wrong-pin-pattern-when-restoring-twrp-nandroid-backup.452384/
This TWRP don't save the password of ROM in they backup
If i do a backup from Rom1 and the Rom2, and if i reinstall ROM1 with backup and after this restore the backup of ROM2, my password will be incorrect, after restart the system and try access the system as found in the One Plus Forum:
When you create and restore a TWRP backup (as example because you tried out a custom ROM and saw that it's not good) you'll be greeted with:
a) A "enter PIN before boot" screen
b) A wrong lockscreen code (either PIN or Pattern) when booted to Android
Click to expand...
Click to collapse
[...]Is needed delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find) to regain access of your system backup:
*password.key
*pattern.key
*locksettings.db-wal
*locksettings.db-shm
*locksettings.db[...]
I have one MOTO G2 Titan with own TWRP that don't have this bug.
Will be great add some commands in TWRP to ease this problem!
If i'm wrong in some part please correct me!

Hi guys, I have a problem. I flashed the TWRP and when I try to boot with Volume Up, I only start in the Mi Recovery mode with some chinese touch buttons. After booting into TWRP with "fastboot boot twrp.img" I cant boot into MiUI. Just have the Mi logo and it won't go any further.
Any suggestions? Thanks!

peffel said:
Hi guys, I have a problem. I flashed the TWRP and when I try to boot with Volume Up, I only start in the Mi Recovery mode with some chinese touch buttons. After booting into TWRP with "fastboot boot twrp.img" I cant boot into MiUI. Just have the Mi logo and it won't go any further.
Any suggestions? Thanks!
Click to expand...
Click to collapse
I've placed the twrp recovery in boot sector place of device, the command is wrong:
"fastboot boot twrp.img"
The correct command is, i guess:
"fastboot flash recovery twrp.img"
To reverse the problem you need the boot.img file of you ROM back and flash with command:
"fastboot boot boot.img" or "fastboot flash boot boot.img"

TingyiChen said:
password is ur lock screen password
Click to expand...
Click to collapse
How to enter pattern in form of word?? ?
---------- Post added at 06:53 PM ---------- Previous post was at 06:52 PM ----------
Isn't there any fix for data encrytion password?
I don't want to format.

I have Redmi 4X. I have installed TWRP on it. But I can't boot into recovery mode. After flashing TWRP when my device reboot, then my stock recovery appears. I can only boot to TWRP by "fastboot boot recovery.img". Otherwise, I can't boot into TWRP recovery mode in no way. Please help me. I flashed official TWRP...

incubus9867 said:
I have Redmi 4X. I have installed TWRP on it. But I can't boot into recovery mode. After flashing TWRP when my device reboot, then my stock recovery appears. I can only boot to TWRP by "fastboot boot recovery.img". Otherwise, I can't boot into TWRP recovery mode in no way. Please help me. I flashed official TWRP...
Click to expand...
Click to collapse
Do you use VolUp + Power to enter TWRP? This didn't work for me too.
Try VolUp + VolDown + Power at the same time. It works for me.

M4rQu1Nh0S said:
I've placed the twrp recovery in boot sector place of device, the command is wrong:
"fastboot boot twrp.img"
The correct command is, i guess:
"fastboot flash recovery twrp.img"
To reverse the problem you need the boot.img file of you ROM back and flash with command:
"fastboot boot boot.img" or "fastboot flash boot boot.img"
Click to expand...
Click to collapse
Found out there is a lot of problems with this version of TWRP. I installed it as a .zip from existing TWRP, didn't boot at all. Then I installed it as IMG, had it starting but all kind of misery when installing custom rom, so went back to TWRP 3.1.0-1
that is working flawless.

The easiest way to get TWRP 3.1.1.0 on your phone would be presented here: >LINK<

with phone encrypted...
this twrp keeps asking for pin
(although i enter correct pin)
found twrp 3.1.0-2 which forks fine for encrypted phone.

peffel said:
Hi guys, I have a problem. I flashed the TWRP and when I try to boot with Volume Up, I only start in the Mi Recovery mode with some chinese touch buttons. After booting into TWRP with "fastboot boot twrp.img" I cant boot into MiUI. Just have the Mi logo and it won't go any further.
Any suggestions? Thanks!
Click to expand...
Click to collapse
if its not fixed yet, you can switch languange to English. Must be looking like 中文 (https://translate.google.de/#en/zh-TW/chinese)
and one of the others buttons is the recovery. after first install of twrp theres its not possible to run again into miui. it stops at the logo. Enter TWRP and flash a new ROM

[Need help]Rooting moto g4 plus in stock june security patch level.

I want to root my moto g4 plus(unlocked bootloader and twrp flashed). Anyone knows how to root moto g4 plus. And i also want to know that how to increase battery backup after rooting(is it a myth).

@ADITYA_KUMAR this has been asked and explained many times and once more.
- Take Backup
- get Elemental-X kernel (see development section and download correct one )
- flash with TWRP
- get latest SuperSU : SuperSU
- now you can follow same guide of MM from step 5 : Guide
Don't Forget to Take Backup..

____Mdd said:
@ADITYA_KUMAR this has been asked and explained many times and once more.
- Take Backup
- get Elemental-X kernel (see development section and download correct one )
- flash with TWRP
- get latest SuperSU : SuperSU
- now you can follow same guide of MM from step 5 : Guide
Don't Forget to Take Backup..
Click to expand...
Click to collapse
How to take backup and restore it. I flashed twrp image. Before rebooting twrp works fine. But after rebooting i am not able to open twrp. I think it got removed.

ADITYA_KUMAR said:
How to take backup and restore it. I flashed twrp image. Before rebooting twrp works fine. But after rebooting i am not able to open twrp. I think it got removed.
Click to expand...
Click to collapse
What happens if you select Recovery from Bootloader ? Is it booting in Stock Recovery ?
In TWRP go to Backup and make backup of /system /data /boot.
If anything bad happens while flashing/Rooting then you can restore it.

The first time, you must open TWRP from the bootloader directly or the recovery gets overwritten.
For rooting, you can flash Magisk instead of flashing SuperSu. Other steps remain exactly the same.

____Mdd said:
What happens if you select Recovery from Bootloader ? Is it booting in Stock Recovery ?
In TWRP go to Backup and make backup of /system /data /boot.
If anything bad happens while flashing/Rooting then you can restore it.
Click to expand...
Click to collapse
When i booted into recovery mode. It shows no command.

ADITYA_KUMAR said:
When i booted into recovery mode. It shows no command.
Click to expand...
Click to collapse
That's stock Recovery, you need to flash TWRP again.

____Mdd said:
That's stock Recovery, you need to flash TWRP again.
Click to expand...
Click to collapse
I flashed twrp 2 times. But every time i restarted my phone it removed automatically.

ADITYA_KUMAR said:
I flashed twrp 2 times. But every time i restarted my phone it removed automatically.
Click to expand...
Click to collapse
Did you flashed TWRP and with the next command booted immediately into twrp?

strongst said:
Did you flashed TWRP and with the next command booted immediately into twrp?
Click to expand...
Click to collapse
Commands used:
Fastboot flash recovery name.img
It gives output as image not signed or corrupt.
After that i typed command fastboot reboot bootloader.
I open recovery mode. It opens twrp. But after i restart my phone. It automatically removes the twrp.

ADITYA_KUMAR said:
Commands used:
Fastboot flash recovery name.img
It gives output as image not signed or corrupt.
After that i typed command fastboot reboot bootloader.
I open recovery mode. It opens twrp. But after i restart my phone. It automatically removes the twrp.
Click to expand...
Click to collapse
This is your problem. You must open recovery from the bootloader menu the very first time. Or TWRP is overwritten with stock recovery. I don't know why that is. But that is how it is...

baunthiyal said:
This is your problem. You must open recovery from the bootloader menu the very first time. Or TWRP is overwritten with stock recovery. I don't know why that is. But that is how it is...
Click to expand...
Click to collapse
It means that i don't have to run the fasboot reboot bootloader command and after finishing the flashing i have to open the recovery mode directly?

Yes
ADITYA_KUMAR said:
It means that i don't have to run the fasboot reboot bootloader command and after finishing the flashing i have to open the recovery mode directly?
Click to expand...
Click to collapse
Reboot into bootloader.
Flash recovery - fastboot flash recovery twrp-xxx.img
Open recovery from bootloader menu (by using the volume and power buttons)
From there you can reboot and your recovery will work normally after this, most probably.

baunthiyal said:
Reboot into bootloader.
Flash recovery - fastboot flash recovery twrp-xxx.img
Open recovery from bootloader menu (by using the volume and power buttons)
From there you can reboot and your recovery will work normally after this, most probably.
Click to expand...
Click to collapse
I need to root my stock nougat( june version).What should i do after that.

I'll tell you what I did.
1. Flash Elemental Ex kernel. https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
2. Flash Magisk. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

baunthiyal said:
Reboot into bootloader.
Flash recovery - fastboot flash recovery twrp-xxx.img
Open recovery from bootloader menu (by using the volume and power buttons)
From there you can reboot and your recovery will work normally after this, most probably.
Click to expand...
Click to collapse
It didn't work. I flashed twrp. I opened recovery mode by using volume down to scroll to recovery mode and power button to select it. I booted in twrp mode and rebooted system from there. After that i power off my phone and tried to open twrp again, but it is showing no commands only. I didn't boot into twrp again.

ADITYA_KUMAR said:
It didn't work. I flashed twrp. I opened recovery mode by using volume down to scroll to recovery mode and power button to select it. I booted in twrp mode and rebooted system from there. After that i power off my phone and tried to open twrp again, but it is showing no commands only. I didn't boot into twrp again.
Click to expand...
Click to collapse
Try commands,
fastboot oem fb_mode_set
fastboot flash recovery name.img
Fastboot oem fb_mode_clear
Then directly boot into recovery,
Then again boot into recovery through twrp itself (there is option for it in reboot) or try anything.

Thank you guys i successfully rooted my moto g4 plus(xt1643)

[TUTORIAL] Install TWRP on Lenovo K8 Note (Oreo)

This procedure is intended for oreo users only !
WARNING : This is a Beta Build and is not completely stable. ANY data loss or bricked phones is not my or any of the Telegram members' responsibility. You and only YOU are responsible for the consequences.
The TWRP provided is a Beta Build by Telegram Group member Maanush. All credits go to him and the all other members of Telegram Group.
TWRP(Beta) : http://www.mediafire.com/file/7p7ida6ems0ta9l/TWRP_BETA_BUILD.img
Tutorial :
1. adb reboot bootloader
2. fastboot oem unlock
3. fastboot flash recovery twrp.img
4. fastboot oem reboot-recovery
After flashing TWRP:
1. Flash Force Encrypt Disabler.zip
2. Flash Magisk.zip
3. Wipe Dalvik/Cache
4. Format Data
6. Reboot

Not working
Sir, there is an error with magisk merge.img mount falied. Please help...

Akash.sep28 said:
Sir, there is an error with magisk merge.img mount falied. Please help...
Click to expand...
Click to collapse
If you're facing issues while flashing magisk modules then you might have done something wrong. Remember that you have to flash force encrypt disabler and format data after that

Sir
After flashing twrp my device restore stock recovery.
Sir I want only twrp recovery install on it.
So I can make backup
Help

CodeNameMadmax said:
Sir
After flashing twrp my device restore stock recovery.
Sir I want only twrp recovery install on it.
So I can make backup
Help
Click to expand...
Click to collapse
After successfully flashing image, write 'fastboot oem reboot-recovery'. Your device will boot into a black screen, now double press the power button, swipe to unlock. You will have to flash magisk zip(use adb sideload or flash from sd card) to prevent system from replacing TWRP.
Remember that you'll have to format your device once to be able to access internal storage so that you can restore backups

My phone not entering into the recovery mode

does the twrp3.1.1.0 work for 5 nov security update?
guys will the the old twrp3.1.1.0 for oreo works on latest 5 nov security patch

prashanth_a_r said:
guys will the the old twrp3.1.1.0 for oreo works on latest 5 nov security patch
Click to expand...
Click to collapse
Yes

sarathkrish02 said:
My phone not entering into the recovery mode
Click to expand...
Click to collapse
How are you trying to enter recovery mode?

Anas Rahman said:
How are you trying to enter recovery mode?
Click to expand...
Click to collapse
Now I can enter into twrp but tell me how to fix 0mb internal storage

sarathkrish02 said:
Now I can enter into twrp but tell me how to fix 0mb internal storage
Click to expand...
Click to collapse
Follow the steps that say "After flashing TWRP"

sarathkrish02 said:
Now I can enter into twrp but tell me how to fix 0mb internal storage
Click to expand...
Click to collapse
Or Google the same thing U will get the perfect answer even I had the same issue

About installation on twrp recovery
iam using lenovo k8 note. i have tried to install twrp recovery but i cant able to install it. i hve tried all the ways like using cmd all the cammands. after i complete flashing twrp and booting again it displays like "orange state " ,"device has been unlckd and cant b trusted" ,"your device will boot in 5 sec" after that my phone restarts and nothing happens . i have tried all possible ways . pls hlp me to install twrp .

salam... i m not entering into twrp recovery mode by this command "fastboot oem reboot-recovery" also tried to switch off cel phone with vol up+vol down+pwr btn and then vol+up and pwr btn but not entered... also tried with vol+down and pwr btn and select recovery mode but fail....
Finally i got my cell rooted successfully here is right twrp for lenovo k8 plus. All credit goes to @anasrehman @kqixs
https://androidfilehost.com/?fid=1322778262903998122

Hi, I have the same issue and I tried all the possible ways but nothing. Can anyone tell if got the same issue but got resolved

no usb debugging
currently my phone is switched off. I am able to go into normal recovery mode. I think the USB Debugging mode is off. How can i revive it again. I was thinking of applying from SD Card a custom ROM flashing. But how to unroot it first

Twrp Oreo Manning
I am just facing one major problem, every time I reboot my device It seems to be my recovery keeps installing again and again which means it's always so my internal storage - 0, after the formatting it reads it but after a new reboot, it doesn't.

Is this working now?

[RECOVERY][STABLE]Unoffical TWRP for Xiaomi Mi A3[laurel_sprout]

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:
#include <std_disclaimer.h>
/*
*
* We are 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 features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Whats Working?
Everything is working
Can change Slot A/Slot B on twrp
SDcard and OTG working
Decryption of Data working
Flashing of roms work pie and even Q roms work.
HOW TO UPDATE a ROM and Keep TWRP and ROOT:
Before all Disable all magisk modules for boths methods
- Put rom.zip, twrp installer.zip and magisk.zip on your internal storage or sdcard;
- Flash Rom;
- Flash TWRP Installer;
- Flash magisk(recommend to use Magisk v19.4);
- Reboot.
Download:
TWRP 3.3.1-2 Unofficial Installer by Nikesh Kataria
TWRP 3.3.1-2 Unofficial by Nikesh Kataria
Donations:
Credits:
Thanks to @mauronofrio for a great help to make a stable recovery
Thanks to @Typhus_ for hardcore testing
Thanks to @prakash78 for testing
Contributors
Nik001
Source Code: https://github.com/Nikesh001/android_device_xiaomi_laurel_sprout-twrp
Version Information
Status: Stable
Created 2019-10-21

Reserved

This man -> @Nik001 deserves a beer!!!
Thank you for delivering us a fully working TWRP for laurel_sprout!
Cheers!

Typhus_ said:
This man -> @Nik001 deserves a beer!!!
Thank you for delivering us a fully working TWRP for laurel_sprout!
Cheers!
Click to expand...
Click to collapse
Welcome and thank you for testing twrp.:fingers-crossed:

Thank u peru sir

A3 real modding let's start

Good Job @Nik001

Anyone tell how to flash twrp... proper commands
Please
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Is that tested anyone.

Stock fw 10.3.8 (global) not booting with this twrp - in 10.3.8 audio modules have strange dependence "saved_command_line" symbol from kernel. For loading this modules need patch kernel sources -
diff --git a/init/main.c b/init/main.c
index 6d1880f0b852..2106f54a7008 100644
--- a/init/main.c
+++ b/init/main.c
@@ -128,6 +128,7 @@ void (*__initdata late_time_init)(void);
char __initdata boot_command_line[COMMAND_LINE_SIZE];
/* Untouched saved command line (eg. for /proc) */
char *saved_command_line;
+EXPORT_SYMBOL_GPL(saved_command_line);
/* Command line for parameter parsing */
static char *static_command_line;
/* Command line for per-initcall parameter parsing */
Click to expand...
Click to collapse

Proper install method explained
Hello!
Please, @Nik001, update the OP with the install method that I'm going to describe next, ok?
It's just to avoid future complications (lost of Wi-Fi, sound, etc...) for "not that experienced users".
Your bootloader must be unlocked. If it's not, then follow step 1 of the instructions provided HERE.
Download TWRP zip file and copy it to your device (internal or external storage)
Download TWRP img file and and store it, on the folder where you have adb and fastboot files, on your PC
Open a cmd line and execute these commands (being on that folder, of course):
adb devices (to make sure your device is detected)
adb reboot bootloader (to reboot into fastboot mode)
fastboot getvar current-slot (to check what's your current active slot)
fastboot set_active b (if your active slot was a, if it was b then change it to a)
fastboot erase boot
fastboot flash boot twrp-3.3.1-2-unofficial-laurel_sprout.img
fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)​
When TWRP recovery boots, if you have a stock boot.img that matches the build on this "currently active" slot, flash it into boot partition. If you don't have, then just ignore this step...(it's not mandatory)
Install the TWRP zip (always install the latest build available)
Change slot to the one that was active on the beginning of these steps and reboot to Recovery (just to make sure that the slot, in fact, was changed)
Reboot to System
Why do I suggest this?
By doing this method (which seems more complicated but, trust me, it's how it should be done) we will flash TWRP img into the "inactive" slot, thus, not breaking anything on the "currently active" slot. When TWRP boots, it will patch both slots boot ramdisks. But the thing is, on the "currently active" slot (the one inactive on the beginning) it will patch the TWRP img but, on the "currently inactive" slot (the one that was active on the beginning), it will patch the stock boot.img, thus, no bug will happen that usually appears when a user accidentally flashes the wrong boot.img into boot partition.
On the other hand, if we have a stock boot.img, that matches the build on the "inactive" slot, we could flash it into boot partition before installing the zip that patches ramdisk. By doing this we will patch both stock boot.img present on both slots (instead of patching TWRP img and boot.img).
Cheers!

Sapper Morton said:
The method Typhus shared works 100% of the times; however I must say, I don't use it, just preference; as it follows, instead of flashing into the inactive slot, I flash the pre_patched boot image into the active slot, this of course will mostly like break network and other components on the ROM, if you mismatch image versions; however, if you flash the stock boot image (using install button, inside TWRP, tapping into 'images', select your stock boot.img) and then patch it using the TWRP Installer right after, you will be using the right image, so no problem will occur, and mostly important, no slot change is needed. Both methods works, choose what you prefer, just read it carefully and I repeat, always use the same boot image from your firmware, a lot of confusion comes to the fact, that when you uses TWRP.img or Magisk.img they aren't boot images, but they are; A/B partition scheme doesn't use some individual partitions anymore, as /recovery, thus is extremely important to patch your boot image, where the recovery, kernel and other components now lives.
Click to expand...
Click to collapse
So, in other words, your method is this (correct me if I'm wrong):
Download TWRP zip file and copy it to your device (internal or external storage)
Download TWRP img file and and store it, on the folder where you have adb and fastboot files, on your PC
Open a cmd line and execute these commands (beeing on that folder, of course):
adb devices (to make sure your device is detected)
adb reboot bootloader (to reboot into fastboot mode)
fastboot erase boot
fastboot flash boot twrp-3.3.1-2-unofficial-laurel_sprout.img
fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)​
Flash stock boot.img that matches your current build using TWRP install Image feature, into boot partition
Install the TWRP zip (always install the latest build available)
Reboot to System
Is that it?
If it is, the only downside I see is that, when a new version comes out (through OTA for example), you'll first need to get your hands on a stock boot.img that matches the new build.
Right?
Cheers!

Typhus_ said:
So, in other words, your method is this (correct me if I'm wrong):
Download TWRP zip file and copy it to your device (internal or external storage)
Download TWRP img file and and store it, on the folder where you have adb and fastboot files, on your PC
Open a cmd line and execute these commands (beeing on that folder, of course):
adb devices (to make sure your device is detected)
adb reboot bootloader (to reboot into fastboot mode)
fastboot erase boot
fastboot flash boot twrp-3.3.1-2-unofficial-laurel_sprout.img
fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)
Flash stock boot.img that matches your current build using TWRP install Image feature, into boot partition
Install the TWRP zip (always install the latest build available)
Reboot to System
Is that it?
If it is, the only downside I see is that, when a new version comes out (through OTA for example), you'll first need to get your hands on a stock boot.img that matches the new build.
Right?
Cheers!
Click to expand...
Click to collapse
As someone who just wants to root his phone with TWRP and few magisk modules, and not miss out on OTAs, seeing these many methods is so confusing and overwhelming ?

After flashing recovery from pc..then go for fastboot reboot from minimal adb and " volume+ key" i saw error in my phone "no command"

Sapper Morton said:
Use the method Typhus explained, it's more simple in the long run; there will be no need to manually flash stock boot image afterwards, since Magisk will have done a proper backup, thus, you will only need to use 'restore image' feature inside Magisk Manager; When taking an OTA, make sure to read the complete Magisk documentation before proceeding:
https://topjohnwu.github.io/Magisk/tutorials.html
Click to expand...
Click to collapse
Thank you! I will do that. But one more thing I'd like to ask. Do you know where I could find the boot image for 10.3.8.0.PFQMIXM? I checked git for dumps, but I couldn't find the boot image for this one.

Sapper Morton said:
Sure, read the OP; Typhus has linked a couple of boot images, including 10.3.8.0 PFQMIXM.
https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509
Click to expand...
Click to collapse
Sick! Thank you very much, sir!

What about flashing this on an already rooted phone with Magisk modules and the previously available TWRP by mauronofrio? Any complicated procedures? Is slot changing etc still necessary?

Makishima said:
What about flashing this on an already rooted phone with Magisk modules and the previously available TWRP by mauronofrio? Any complicated procedures? Is slot changing etc still necessary?
Click to expand...
Click to collapse
In that case, obviously, simply flash the new TWRP zip.
The install method I've explained is for everyone who never had TWRP, or Magisk patched boot, installed on the device.

Makishima said:
What about flashing this on an already rooted phone with Magisk modules and the previously available TWRP by mauronofrio? Any complicated procedures? Is slot changing etc still necessary?
Click to expand...
Click to collapse
Just flash the zip in twrp that you have.
That's what I did and it worked no problem on pe ROM

Typhus_ said:
In that case, obviously, simply flash the new TWRP zip.
The install method I've explained is for everyone who never had TWRP, or Magisk patched boot, installed on the device.
Click to expand...
Click to collapse
I did as you said but it says 'NOTE: You are now unrooted!'. Do I need to flash Magisk again?

Makishima said:
I did as you said but it says 'NOTE: You are now unrooted!'. Do I need to flash Magisk again?
Click to expand...
Click to collapse
Yes, that's right.