Database Develop

Twrp 3.0 recovery

TWRP Recovery v.3.0 for BLU_VIVO_XL (gionee6753_65u_l1)
based on firmware version BLU_V0030UU_V07_GENERIC_5.1_20160126-1033 / Tue Jan 26 10:33:33 CST 2016 / Android 5.1

How do we go about to install this

jemmini said:
TWRP Recovery v.3.0 for BLU_VIVO_XL (gionee6753_65u_l1)
based on firmware version BLU_V0030UU_V07_GENERIC_5.1_20160126-1033 / Tue Jan 26 10:33:33 CST 2016 / Android 5.1
Click to expand...
Click to collapse
Is this confirmed to work? I tried flashing the TWRP for the Blu Pure XL and the phone boot looped. I was able to unlock the bootloader ADB but after flashing TWRP the phone bootlooped.

ItGuyJax8430 said:
Is this confirmed to work? I tried flashing the TWRP for the Blu Pure XL and the phone boot looped. I was able to unlock the bootloader ADB but after flashing TWRP the phone bootlooped.
Click to expand...
Click to collapse
flash the original recovery (from fastboot mode).
loading recovery and system loading - are two different things...
p.s. recovery was tested.

jemmini said:
flash the original recovery (from fastboot mode).
loading recovery and system loading - are two different things...
p.s. recovery was tested.
Click to expand...
Click to collapse
10-4 ill give the recovery a go. I knew there was a difference, I was just giving extra info on my situation. I just got my replacement phone in today, ill give the recovery a go.

ItGuyJax8430 said:
10-4 ill give the recovery a go. I knew there was a difference, I was just giving extra info on my situation. I just got my replacement phone in today, ill give the recovery a go.
Click to expand...
Click to collapse
give me the boot.img and recovery.img files from your firmware. and the file /proc/emmc from the system
and I'll make TWRP for you...

It works. Thank you jemmini!
Edit: It appears I spoke too soon. Recovery works, but now the phone is in a constant boot loop.
2nd update: By some miracle, I got the phone to stop looping and just stay on recovery by randomly pressing buttons.

During the loop, I get this message.

after unlocking the bootloader you need for the first time to boot the system with the original recovery. and only after that to flash the TWRP...

jemmini, do you have a backup of the stock rom? If so, can you upload it? Thank you.

jemmini said:
after unlocking the bootloader you need for the first time to boot the system with the original recovery. and only after that to flash the TWRP...
Click to expand...
Click to collapse
Can you provide step by step instructions?
I imagine it would be something like this.
1. Developer Options > Enable OEM Unlock
2. Enable USB Debugging
3. Reboot to bootloader
4. fastboot oem unlock
5. fastboot reboot? (boot back into system) << i think this is where people are getting boot loop
6. reboot to bootloader
7. fastboot flash recovery (twrp recovery.img)
8. reboot to recovery
9. profit?
---------- Post added at 07:50 AM ---------- Previous post was at 07:46 AM ----------
xdadev_user11 said:
jemmini, do you have a backup of the stock rom? If so, can you upload it? Thank you.
Click to expand...
Click to collapse
If you have no other option, you can try this.. http:// firmwarefile.com/gionee-s-plus

emowing said:
Can you provide step by step instructions?
Click to expand...
Click to collapse
1. Developer Options > Enable OEM Unlock
2. Enable USB Debugging
3. Reboot to bootloader
4. fastboot oem unlock
4.1. fastboot oem unlock confirm
5. fastboot reboot? (boot back into system) << i think this is where people are getting boot loop
6. reboot to bootloader
7. fastboot flash recovery (twrp recovery.img)
8. reboot to recovery
9. profit.

jemmini said:
give me the boot.img and recovery.img files from your firmware. and the file /proc/emmc from the system
and I'll make TWRP for you...
Click to expand...
Click to collapse
I'm planning on trying out TWRP later today. Before I do that, what files should I grab (as a backup) and from where should I grab them? I'm happy to upload them for others, too.

So I will be able to root the phone with this? After unlocking bootloader and flashing twrp I flash supersu?

jemmini said:
1. Developer Options > Enable OEM Unlock
2. Enable USB Debugging
3. Reboot to bootloader
4. fastboot oem unlock
4.1. fastboot oem unlock confirm
5. fastboot reboot? (boot back into system) << i think this is where people are getting boot loop
6. reboot to bootloader
7. fastboot flash recovery (twrp recovery.img)
8. reboot to recovery
9. profit.
Click to expand...
Click to collapse
@jemmini I've never heard of the command fastboot oem unlock confirm before. Is this a command to run or do you mean we should do a fastboot getvar all and check the bootloader unlock status for a yes? Sorry for the newbie question. I've never needed to do this with a nexus.

emowing said:
@jemmini I've never heard of the command fastboot oem unlock confirm before. Is this a command to run or do you mean we should do a fastboot getvar all and check the bootloader unlock status for a yes? Sorry for the newbie question. I've never needed to do this with a nexus.
Click to expand...
Click to collapse
The confirmation he means is after you execute the unlock command, on the phone screen asks you to confirm by press volume up. That all.

[del]

xdadev_user11 said:
It works. Thank you jemmini!
Edit: It appears I spoke too soon. Recovery works, but now the phone is in a constant boot loop.
2nd update: By some miracle, I got the phone to stop looping and just stay on recovery by randomly pressing buttons.
Click to expand...
Click to collapse
The same thing happened to me.
After I was able to get into recovery using your steps, I formated ONLY the /data partition and rebooted. The phone then booted up properly after that.
I then downloaded the SuperSU ZIP file and rooted my phone through recovery .
I hope this helps someone.

acotto said:
The same thing happened to me.
After I was able to get into recovery using your steps, I formated ONLY the /data partition and rebooted. The phone then booted up properly after that.
I then downloaded the SuperSU ZIP file and rooted my phone through recovery .
I hope this helps someone.
Click to expand...
Click to collapse
Nice find :good:. I'll try it when I get my phone.. it will be delivered today.

emowing said:
If you have no other option, you can try this.. http:// firmwarefile.com/gionee-s-plus
Click to expand...
Click to collapse
So I unlocked bootloader and also got the bootloop. I flashed this firmware to fix it, but I found out the radio included is not the same as the US version, so now the sim cards don't work.
The firmware image have a file called "MT6753_Android_scatter.txt" which determine what partition to flash. Base on this guide http://www.mtkroms.com/2015/03/how-to-restore-lost-imei-on-any.html, the "secro" partition being replaced may be what caused the issue, so looked like that's what I have unchecked before flashing.
jemmini said:
..
Click to expand...
Click to collapse
I just discovered that you can back the secro and many other partition within TWRP. I don't know if that alone will fix the sim problem. WRONG

Unable to Unbrick phone

Hey guys,
My younger brother had TWRP installed on his OP3. Yesterday he applied OTA and his phone got bricked. I unbricked it from MSMtool method (Qualcom Driver). It got unbricked and i have stock rom now however phone is stuck at android is upgrading (45 minutes). I tried restarting it and now it is in boot loop. i tried to flash latest OxygenOS from adb sideload and it got bricked again. Can anyone tell me what to do now or what is wrong with the device.

abdullah.ahsan11 said:
Hey guys,
My younger brother had TWRP installed on his OP3. Yesterday he applied OTA and his phone got bricked. I unbricked it from MSMtool method (Qualcom Driver). It got unbricked and i have stock rom now however phone is stuck at android is upgrading (45 minutes). I tried restarting it and now it is in boot loop. i tried to flash latest OxygenOS from adb sideload and it got bricked again. Can anyone tell me what to do now or what is wrong with the device.
Click to expand...
Click to collapse
You have TWRP installed? Use Method 2 of the unbrick guide. Now you want to wipe every partition then adb push your rom (not sideload) and manually flash it. Make sure you are on the latest Bluspark twrp.

Puddi_Puddin said:
You have TWRP installed? Use Method 2 of the unbrick guide. Now you want to wipe every partition then adb push your rom (not sideload) and manually flash it. Make sure you are on the latest Bluspark twrp.
Click to expand...
Click to collapse
I am using method 2, the OS gets stuck on bootloop that's why i tried to sideload later
I don't have a working recovery, all i can get is stock recovery, how can i install twrp?
I've tried flashing (fastboot flash recovery recovery.img) it but it is not working

abdullah.ahsan11 said:
I am using method 2, the OS gets stuck on bootloop that's why i tried to sideload later
I don't have a working recovery, all i can get is stock recovery, how can i install twrp?
I've tried flashing (fastboot flash recovery recovery.img) it but it is not working
Click to expand...
Click to collapse
Why is it not working? Does it give an error or something?

Puddi_Puddin said:
Why is it not working? Does it give an error or something?
Click to expand...
Click to collapse
Yes, it says flashing partition not allowed.
I suppose it is because usb debugging is off.

abdullah.ahsan11 said:
Yes, it says flashing partition not allowed.
I suppose it is because usb debugging is off.
Click to expand...
Click to collapse
Nah, In windows, go to Device Manager. How does your device show up? It has to do with wrong drivers.

Puddi_Puddin said:
Nah, In windows, go to Device Manager. How does your device show up? It has to do with wrong drivers.
Click to expand...
Click to collapse
Yes It shows up correctly.

abdullah.ahsan11 said:
Yes It shows up correctly.
Click to expand...
Click to collapse
What is correctly? What does it say? You might want to try different ADB drivers. You should be able to always flash In fastboot..

abdullah.ahsan11 said:
Yes, it says flashing partition not allowed.
I suppose it is because usb debugging is off.
Click to expand...
Click to collapse
Check again the bootloader to be unlocked. Use the tool for that, is it on OP3 forum, then retry to get a stock rom up before anything else (TWRP, custom rom, etc)
Sent from my OnePlus3 using XDA Labs

follow this instruction -
1- go into twrp and wipe everything even internal and formate it .
2- unistall all adb driver and oneplus driver also .. then clean tmp file from window
3rd- install latest adb+ oneplus 3 driver ..again restrat ..
4th-boot in fastboot mod and lock your bootloader
5th-flast latest build of oxygen stock recovery from fastboot
6th than again wipe or factory reset the device via stock recovery
7th open stock recoery than flash latest build of oxygen os via sideload
8th reboot the device and setup quikly
9th-unlock bootloader, flash bluespark recovery , flash rom, flash supersu ..
10th play with device

Stuck in Oneplus logo. Can't access recovery. Fastboot working.

Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
To clarify:
- I already tried erasing userdata and cache from fastboot
-I already tried flashing recovery images from twrp, stock and bluspark
Thanks in advance guys.

Pavononer23 said:
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
Thanks in advance guys.
Click to expand...
Click to collapse
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.

rykanator said:
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
Click to expand...
Click to collapse
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.

Pavononer23 said:
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Click to expand...
Click to collapse
can you boot into the bootloader/fastboot?

rykanator said:
can you boot into the bootloader/fastboot?
Click to expand...
Click to collapse
Yes I can

Pavononer23 said:
Yes I can
Click to expand...
Click to collapse
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS

rykanator said:
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
Click to expand...
Click to collapse
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear

Pavononer23 said:
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Click to expand...
Click to collapse
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here

rykanator said:
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
Click to expand...
Click to collapse
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway

Pavononer23 said:
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Click to expand...
Click to collapse
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!

rykanator said:
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
Click to expand...
Click to collapse
It is not working, I think I lost my Oneplus 3t...

Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
I mean idk if you wanna do this, but you could always try to "format userdata", then flash the stock recovery, and then sideload OOS. but you would lose all of your data in your internal storage, and it's still not a guarantee. there are some posts about doing a full wipe and starting from scratch. I'd look into those. Best of luck reviving your OP3T

Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..

nicknacknuke said:
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
Click to expand...
Click to collapse
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working

Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?

pitrus- said:
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
Click to expand...
Click to collapse
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer

Pavononer23 said:
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Click to expand...
Click to collapse
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.

przemcio510 said:
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
Click to expand...
Click to collapse
I can't install the drivers:
-First, stupid Windows policy saying that its driver is the best one available.
-Second, choosing from a disk to avoid one saying that the driver is not a x64 one.

Pavononer23 said:
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Click to expand...
Click to collapse
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.

redpoint73 said:
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
Click to expand...
Click to collapse
There were no errors when flashing TWRP. When I tried rebooting using fastboot(fastboot boot recovery.img) it got stuck in the message saying booting up... and the only thing that changed was that my phone left the bootloader screen to a screen with the Oneplus logo and a fastboot mode message under it.
The command I used was fastboot flash recovery recovery.img(Name of the actual recovery file)

HELP! Trwp is set on default on Boot! HELP!

Hi
At begining i must say, sorry, my english is bad! :laugh:
i brick my phone, so i unlock bootloader, flash recovery.
Then i enter TWRP, select storage>sdcard> flash recovery.img as boot .... i dont know why i made this step xD
And now, when i try to back to stockROM, i open TWRP\Install\Select Storage\ and, only what i can say is "Internal Storage(0 MB)"
So, dload cant help to back my stock ROM, because phone doesn't have internal memory.
So, for begin, i need to dellete TWRP from default boot.
Help

axe30 said:
Hi
At begining i must say, sorry, my english is bad! :laugh:
i brick my phone, so i unlock bootloader, flash recovery.
Then i enter TWRP, select storage>sdcard> flash recovery.img as boot .... i dont know why i made this step xD
And now, when i try to back to stockROM, i open TWRP\Install\Select Storage\ and, only what i can say is "Internal Storage(0 MB)"
So, dload cant help to back my stock ROM, because phone doesn't have internal memory.
So, for begin, i need to dellete TWRP from default boot.
Help
Click to expand...
Click to collapse
Switch the phone off, connect to PC - must have drivers and ADB installed.
Boot by Volume- & Power - must boot to Fastboot.
Flash boot.img - corresponding to your installed ROM, to the boot partition.
You can use Firmwsre Finder - from PC or another Android to download update.zip (FullOTA, corresponding to your ROM), unzip and extract boot.img from update.app by using Huawei Update Extractor on the PC.
And take care what you flash and where

axe30 said:
Hi
At begining i must say, sorry, my english is bad! :laugh:
i brick my phone, so i unlock bootloader, flash recovery.
Then i enter TWRP, select storage>sdcard> flash recovery.img as boot .... i dont know why i made this step xD
And now, when i try to back to stockROM, i open TWRP\Install\Select Storage\ and, only what i can say is "Internal Storage(0 MB)"
So, dload cant help to back my stock ROM, because phone doesn't have internal memory.
So, for begin, i need to dellete TWRP from default boot.
Help
Click to expand...
Click to collapse
I think this is going to help:https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279:good:

zgfg said:
Switch the phone off, connect to PC - must have drivers and ADB installed.
Boot by Volume- & Power - must boot to Fastboot.
Flash boot.img - corresponding to your installed ROM, to the boot partition.
You can use Firmwsre Finder - from PC or another Android to download update.zip (FullOTA, corresponding to your ROM), unzip and extract boot.img from update.app by using Huawei Update Extractor on the PC.
And take care what you flash and where
Click to expand...
Click to collapse
Already try, but still don't have internal memory and booting TWRP.

mrleja said:
I think this is going to help:https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279:good:
Click to expand...
Click to collapse
This method help me, so i unbrick phone but i stuck on NRD90M test-keys.
And i have problem, i run dload, and install update. After that i stuck on boot, and only can open fastboot. I try to flash many of recoveries via fastboot, but didn't help.

axe30 said:
This method help me, so i unbrick phone but i stuck on NRD90M test-keys.
And i have problem, i run dload, and install update. After that i stuck on boot, and only can open fastboot. I try to flash many of recoveries via fastboot, but didn't help.
Click to expand...
Click to collapse
Tri puta ti saljem odgovor na PM,ali izgleda da nešto nije u redu,ako imas Viber ili WhatsApp,posalji mi broj telefona na PM,pa cu te zvati.

help please root mi8

hello everyone
Buy a Chinese mi8, unlock it waiting for the days that xiaomi tells you.
I installed the global version, and everything works correctly, but I want to change the rom.
I've tried to install TWRP with adb and it's impossible, it tells me the ADB template that OKEY, but never restarts in recovery mode with TWRP, so I can not install magisk, or any rom that is not official.
Is there any way to install a ROM (.zip) without TWRP?, how do I do Root without magisk? Has it happened to anyone?
thanks!

First of all, you're in the wrong section.
Second you should install via fastboot as described a thousand times AND reboot directly to your TWRP image via fastboot command.
The you can flash another from and root it.
Third, I'd like to strongly advice you to do some research about android, flashing etc to make sure that you know what you are doing.... So many people are moaning about bricked devices....

trahzebuck said:
First of all, you're in the wrong section.
Second you should install via fastboot as described a thousand times AND reboot directly to your TWRP image via fastboot command.
The you can flash another from and root it.
Third, I'd like to strongly advice you to do some research about android, flashing etc to make sure that you know what you are doing.... So many people are moaning about bricked devices....
Click to expand...
Click to collapse
Thanks for your help
It's not the first cell phone I've flashed that you're not smart.
I have followed the steps as they are, and as you can see in the image, everything seems to be installed correctly. But whenever I restart in recovery mode, I get the xiaomi no twrp.
Do you know why?

cheteuk said:
Thanks for your help
It's not the first cell phone I've flashed that you're not smart.
I have followed the steps as they are, and as you can see in the image, everything seems to be installed correctly. But whenever I restart in recovery mode, I get the xiaomi no twrp.
Do you know why?
Click to expand...
Click to collapse
You are trying to be smart? Well...
Why didn't you post your exact steps with fastboot in the first post?
Now it's clear what you did wrong. I already expected it. And you did NOT read what I wrote:
You are rebooting your device with fastboot reboot. In this case your twrp is wiped out by the XIAOMI recovery. Use: fastboot boot yourimagename.
btw, why are you using such an old TWRP? You won't be able to flash actual roms.
So I'd like to come back to my advice in the first answer....

cheteuk said:
Thanks for your help
It's not the first cell phone I've flashed that you're not smart.
I have followed the steps as they are, and as you can see in the image, everything seems to be installed correctly. But whenever I restart in recovery mode, I get the xiaomi no twrp.
Do you know why?
Click to expand...
Click to collapse
fastboot boot recovery.img
not fastboot reboot
Sent from my MI 8 using Tapatalk

Vuska said:
fastboot boot recovery.img
not fastboot reboot
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
I've tried twrp-3.3.1-0-dipper too, and fastboot boot xxxx.img.
And it hasn't been restarted either.

cheteuk said:
I've tried twrp-3.3.1-0-dipper too, and fastboot boot xxxx.img.
And it hasn't been restarted either.
Click to expand...
Click to collapse
Use the all in one tool, to remove encryption and flash a compatible TWRP.

tsongming said:
Use the all in one tool, to remove encryption and flash a compatible TWRP.
Click to expand...
Click to collapse
What is the all in one tool?

cheteuk said:
What is the all in one tool?
Click to expand...
Click to collapse
Try this. There is all you need.
https://tradingshenzhen.com/de/cont...sh-tutorial-global-firmware-xiaomieu-firmware
Upps, in German. You can choose English.

Goalach said:
Try this. There is all you need.
https://tradingshenzhen.com/de/cont...sh-tutorial-global-firmware-xiaomieu-firmware
Upps, in German. You can choose English.
Click to expand...
Click to collapse
Thanks for the help.
But all the steps that indicate, I have passed them and I never install the TWRP correctly.
1. my mobile phone is unlocked (with the padlock open)
2. I have the official rom installed
3. I try to install twrp with all the commands you have told me, and I never restart the mobile with twrp. I've tried new, intermediate and older versions. and nothing
Is there any way to install an unofficial rom without TWRP?

cheteuk said:
Thanks for the help.
But all the steps that indicate, I have passed them and I never install the TWRP correctly.
1. my mobile phone is unlocked (with the padlock open)
2. I have the official rom installed
3. I try to install twrp with all the commands you have told me, and I never restart the mobile with twrp. I've tried new, intermediate and older versions. and nothing
Is there any way to install an unofficial rom without TWRP?
Click to expand...
Click to collapse
You can't flash a ROM without TWRP and Magisk is the only way you can root your phone that I know of. If you don't even know these simple things/haven't done simple research you might risk to softbrick or even hardbrick your new and shiny phone. There are many guides on how to flash TWRP but you can PM me if you want more help.
Also you don't install TWRP with adb, you need to use fastboot...

cheteuk said:
What is the all in one tool?
Click to expand...
Click to collapse
The number 1 result
http://bfy.tw/Nvtb

You can try this
Make sure you have activated the usb debugging in developer options.
1. Download the tools from here: bit.ly/FlashToolMi8
2. Install the minimal_adb_fastboot_v1.3.1_setup
3. Copy the twrp-3.2.3-0-dipper.img to Minimal ADB and Fastboot Folder
4. Turn off your phone completely. then press power button + volume down to boot in fastboot mode.
5. Run CMD as Administrator then cd to the installed Minimal ADB and Fastboot folder. (Ex: cd C:\Program Files (x86)\Minimal ADB and Fastboot)
6. Use this command on your cmd: fastboot flash recovery twrp-3.2.3-0-dipper.img
7. Then: fastboot boot twrp-3.2.3-0-dipper
8. And: fastboot reboot recovery
9. You're now in twrp recovery mode
10. Copy Disable_Dm-Verity_FEC_v1.1 and Magisk-v18.1 to your phone
11. Install Disable_Dm-Verity_FEC_v1.1 from twrp
12. Then install Magisk-v18.1
13. Reboot, Your phone now rooted