Develop Bugs

Oppo Find 7 V1.2.8i Won't boot into TWRP recovery after booting into stock recovery

long story short, incase any of these are the reason why my phone can't get twrp recovery.
History:
Around 3-4 months ago I updated my phone to Color os 2.0.8i(if not mistaken). Not sure if I did root my phone or not. My phone screen broke, and touch screen spoiled, not using it until I repaired it few days ago. After repair decided to use CM13 and took me awhile to figure out how to flash TWRP and took me quite sometime to root my phone. After successfully rooting my phone, I started to install CM13 snapshot bcos i tot the nightly is not stable. But it failed. My phone can't turn on and can't go to recovery. Keeps boot to fastboot. Figured out i need to use some code like fastboot oem unlock(can't really rmb if this was the code I used) then flash my recovery again and my recovery works. But my phone still can't turn on. I use TWRP recovery to flash the same rom again to see if it works this time, but no it doesn't. i think i did try the CM13 nightly rom but it doesn't work too so i searched a lot about how to install CM13 on Find7. This link(http://forum.xda-developers.com/fin...0-marshmallow-unofficial-cm13-oppo-7-t3227311) said that Color OS 2 &2.1 needs to flash Color OS 1.2.8 and i did it. I did not flash the stock recovery. I use fastboot boot stockrecovery.img. Then, I install the stock rom using the stock recovery. The link says let it boot, and after that reboot back to TWRP recovery. After successfully booting into Color OS 1.2.8i, I switch off my phone and press down button + power button but the stock recovery came out. From that onwards i keep trying to flash TWRP recovery to my phone but it failed. I used fastboot flash recovery twrp.img and press volume down button + power button, fastboot boot twrp.img, fastboot erase recovery and fasboot flash recovery twrp.img and fastboot boot twrp.img all that doesn't work even the cmd said okay twice. All it does just either boot up the oppo logo and turn back off and turn on again with the logo and turn on the phone normally. OR it just boot up the stock recovery. I have read it some where that some stock rom will overwrite the custom recovery with its stock recovery so needs to delete some recovery file and edit the updater script. I did it and try to install the rom again after editing, but it failed. I tried installing another 1.2 color os(without editing the inside hoping this rom doesn't have the ability to overwrite the custom recovery) it did tried to install but up to about 40% of the loading bar, it says fail. I tried many times, I even factory reset my phone and try installing again but TWRP just can't be booted.
Problem:
- I can't get to TWRP recovery.
- Without TWRP I can't install custom rom or root my phone
Please help me. I have wasted about 4 days time just to install the CM13...

ron8899 said:
long story short, incase any of these are the reason why my phone can't get twrp recovery.
History:
Around 3-4 months ago I updated my phone to Color os 2.0.8i(if not mistaken). Not sure if I did root my phone or not. My phone screen broke, and touch screen spoiled, not using it until I repaired it few days ago. After repair decided to use CM13 and took me awhile to figure out how to flash TWRP and took me quite sometime to root my phone. After successfully rooting my phone, I started to install CM13 snapshot bcos i tot the nightly is not stable. But it failed. My phone can't turn on and can't go to recovery. Keeps boot to fastboot. Figured out i need to use some code like fastboot oem unlock(can't really rmb if this was the code I used) then flash my recovery again and my recovery works. But my phone still can't turn on. I use TWRP recovery to flash the same rom again to see if it works this time, but no it doesn't. i think i did try the CM13 nightly rom but it doesn't work too so i searched a lot about how to install CM13 on Find7. This link(http://forum.xda-developers.com/fin...0-marshmallow-unofficial-cm13-oppo-7-t3227311) said that Color OS 2 &2.1 needs to flash Color OS 1.2.8 and i did it. I did not flash the stock recovery. I use fastboot boot stockrecovery.img. Then, I install the stock rom using the stock recovery. The link says let it boot, and after that reboot back to TWRP recovery. After successfully booting into Color OS 1.2.8i, I switch off my phone and press down button + power button but the stock recovery came out. From that onwards i keep trying to flash TWRP recovery to my phone but it failed. I used fastboot flash recovery twrp.img and press volume down button + power button, fastboot boot twrp.img, fastboot erase recovery and fasboot flash recovery twrp.img and fastboot boot twrp.img all that doesn't work even the cmd said okay twice. All it does just either boot up the oppo logo and turn back off and turn on again with the logo and turn on the phone normally. OR it just boot up the stock recovery. I have read it some where that some stock rom will overwrite the custom recovery with its stock recovery so needs to delete some recovery file and edit the updater script. I did it and try to install the rom again after editing, but it failed. I tried installing another 1.2 color os(without editing the inside hoping this rom doesn't have the ability to overwrite the custom recovery) it did tried to install but up to about 40% of the loading bar, it says fail. I tried many times, I even factory reset my phone and try installing again but TWRP just can't be booted.
Problem:
- I can't get to TWRP recovery.
- Without TWRP I can't install custom rom or root my phone
Please help me. I have wasted about 4 days time just to install the CM13...
Click to expand...
Click to collapse
You forgot fastboot oem unlock. Also not all twrp versions work. Try and see. Recap: fastboot erase cache, fastboot oem unlock and fastboot flash recovery followed by twrp. img. After that press and hold power and volume down simultaneously and you should be in twrp.

My steps with fastboot oem unlock
tropical cactus said:
You forgot fastboot oem unlock. Also not all twrp versions work. Try and see. Recap: fastboot erase cache, fastboot oem unlock and fastboot flash recovery followed by twrp. img. After that press and hold power and volume down simultaneously and you should be in twrp.
Click to expand...
Click to collapse
Hi, thanks for your reply. It didn't work again. Here is what I did maybe you can see what mistake i made:
1) volume up + power button get to fastboot.
2) plug my phone in to computer
3) right click in platform-tools folder + shift and choose open command window here
4) fastboot erase cache
result
5)******* Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.029s]
finished. total time: 0.029s
i continued
6) fastboot oem unlock
result
7)...
OKAY [ 0.003s]
finished. total time: 0.003s
i continued
8) fastboot flash recovery twrp-3.0.2-0-find7.img
result
9) target reported max download size of 536870912 bytes
sending 'recovery' <10894 KB>...
OKAY [ 0.344s]
writing 'recovery'
OKAY [ 0.163s]
finished. total time: 0.507s
10) i unplug the phone from computer
11) i hold volume down + power button until i feel vibration i release
12) oppo logo showed up
13) screen goes off and vibrate again
14) oppo logo showed up again and the phone turn on normaly.

ron8899 said:
Hi, thanks for your reply. It didn't work again. Here is what I did maybe you can see what mistake i made:
1) volume up + power button get to fastboot.
2) plug my phone in to computer
3) right click in platform-tools folder + shift and choose open command window here
4) fastboot erase cache
result
5)******* Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.029s]
finished. total time: 0.029s
i continued
6) fastboot oem unlock
result
7)...
OKAY [ 0.003s]
finished. total time: 0.003s
i continued
8) fastboot flash recovery twrp-3.0.2-0-find7.img
result
9) target reported max download size of 536870912 bytes
sending 'recovery' <10894 KB>...
OKAY [ 0.344s]
writing 'recovery'
OKAY [ 0.163s]
finished. total time: 0.507s
10) i unplug the phone from computer
11) i hold volume down + power button until i feel vibration i release
12) oppo logo showed up
13) screen goes off and vibrate again
14) oppo logo showed up again and the phone turn on normaly.
Click to expand...
Click to collapse
All steps correct. Try earlier twrp versions. I remember 2.8.6.0 works.

tropical cactus said:
You forgot fastboot oem unlock. Also not all twrp versions work. Try and see. Recap: fastboot erase cache, fastboot oem unlock and fastboot flash recovery followed by twrp. img. After that press and hold power and volume down simultaneously and you should be in twrp.
Click to expand...
Click to collapse
i realise something different this time. i switch off my phone and hold volume down + power button to go to the recovery. Usually it goes to the stock recovery but this time it doesn't it just turn on the phone like just now. it repeat these steps.
11) i hold volume down + power button until i feel vibration i release
12) oppo logo showed up
13) screen goes off and vibrate again
14) oppo logo showed up again and the phone turn on normaly.

tropical cactus said:
All steps correct. Try earlier twrp versions. I remember 2.8.6.0 works.
Click to expand...
Click to collapse
alright thanks i'll go and try

tropical cactus said:
All steps correct. Try earlier twrp versions. I remember 2.8.6.0 works.
Click to expand...
Click to collapse
I tried the 2.8.6.0 twrp. i repeated all the steps. erase cache, oem unlock, flash twrp and hold the volume down + power. this time it shows oppo logo. after awhile at the oppo logo screen, it glitch a little. Then it shows a black screen with light. but there is nothing. I tried to touch the screen nothing seems to happen...
i also tried 2.8.5.0 and it repeat this
11) i hold volume down + power button until i feel vibration i release
12) oppo logo showed up
13) screen goes off and vibrate again
14) oppo logo showed up again and the phone turn on normaly.

ron8899 said:
I tried the 2.8.6.0 twrp. i repeated all the steps. erase cache, oem unlock, flash twrp and hold the volume down + power. this time it shows oppo logo. after awhile at the oppo logo screen, it glitch a little. Then it shows a black screen with light. but there is nothing. I tried to touch the screen nothing seems to happen...
i also tried 2.8.5.0 and it repeat this
11) i hold volume down + power button until i feel vibration i release
12) oppo logo showed up
13) screen goes off and vibrate again
14) oppo logo showed up again and the phone turn on normaly.
Click to expand...
Click to collapse
Well, sorry to hear that. I'm out of ideas.

tropical cactus said:
Well, sorry to hear that. I'm out of ideas.
Click to expand...
Click to collapse
Alright thanks anyway. Hopefully someone out there can help?

ron8899 said:
Alright thanks anyway. Hopefully someone out there can help
Click to expand...
Click to collapse
Have you tried CWM recovery?

tropical cactus said:
Have you tried CWM recovery?
Click to expand...
Click to collapse
I haven't tried cwm yet. Cos i have used twrp on this phone before... wondering why i can't use twrp now...

ron8899 said:
I haven't tried cwm yet. Cos i have used twrp on this phone before... wondering why i can't use twrp now...
Click to expand...
Click to collapse
Try it. It might work. Does the same thing anyway.

tropical cactus said:
Try it. It might work. Does the same thing anyway.
Click to expand...
Click to collapse
i tried. using the X9007_CWM_recovery.img.
OKAY twice.
used volume down + power button.
logo showed up and stuck at the logo for a long time
the 3 buttons(back, home & menu buttons) light up
if i used fastboot boot method, the fastboot screen lightup brightly, and stuck there. and the three buttons light up too...

ron8899 said:
i tried. using the X9007_CWM_recovery.img.
OKAY twice.
used volume down + power button.
logo showed up and stuck at the logo for a long time
the 3 buttons(back, home & menu buttons) light up
if i used fastboot boot method, the fastboot screen lightup brightly, and stuck there. and the three buttons light up too...
Click to expand...
Click to collapse
Okay. Last one. Since you have unlocked bootloader i. e. Fastboot oem unlock, try using flashify from play to install twrp and see if that works. Try a few versions of twrp.
Edit. Go back to stock recovery first and start again. Good luck.

tropical cactus said:
Okay. Last one. Since you have unlocked bootloader i. e. Fastboot oem unlock, try using flashify from play to install twrp and see if that works. Try a few versions of twrp.
Edit. Go back to stock recovery first and start again. Good luck.
Click to expand...
Click to collapse
U mean I should try flashing stock recovery using cmd, after that then I use flashify flash twrp?

ron8899 said:
U mean I should try flashing stock recovery using cmd, after that then I use flashify flash twrp?
Click to expand...
Click to collapse
Yes, so you have a working recovery. Check that it is installed first. Then fastboot erase cache and fastboot oem unlock. Reboot, download flashify and flash twrp. img and then try to enter recovery.

tropical cactus said:
Yes, so you have a working recovery. Check that it is installed first. Then fastboot erase cache and fastboot oem unlock. Reboot, download flashify and flash twrp. img and then try to enter recovery.
Click to expand...
Click to collapse
Alright, I saw two flashify in play. Which one is it? The one with the requires root?

ron8899 said:
Alright, I saw two flashify in play. Which one is it? The one with the requires root?
Click to expand...
Click to collapse
Yes, the one from rashr. Skip all warnings and proceed. Put your twrp.img on sd card first.

tropical cactus said:
Yes, the one from rashr. Skip all warnings and proceed. Put your twrp.img on sd card first.
Click to expand...
Click to collapse
oh.... i can't get my stock recovery work... it always shows half of the reocvery screen only.... and the recovery screen keeps glitch. what should i do?
this is where i download the stock recovery
http://community.oppo.com/en/forum.php?mod=viewthread&tid=17397

ron8899 said:
oh.... i can't get my stock recovery work... it always shows half of the reocvery screen only.... and the recovery screen keeps glitch. what should i do?
this is where i download the stock recovery
http://community.oppo.com/en/forum.php?mod=viewthread&tid=17397
Click to expand...
Click to collapse
Now we know where the problem is. I re-read your post. New LCD screen. Flash this stock recovery. Once you see it can work, then proceed with the erase cache, oem unlock and twrp 3.0.0.0.
The links here: https://drive.google.com/file/d/0B_5WCvt_2elTU0pKR0V1Mm1jWk0/view?usp=sharing
https://drive.google.com/open?id=0B_5WCvt_2elTbmZ5MERKTzVPQTQ
---------- Post added at 06:36 AM ---------- Previous post was at 06:26 AM ----------
Oh, and by the way, CM 13 not compatible with our LCD screen. Omni supports new screen. Read before flashing rom. If not you'll have more problems.
There's a snapshot CM 13 for new LCD in oppo forum. The links are dead but if you ask someone there, they might upload. I've erased mine. Again, there's some requirements there, so read up.
---------- Post added at 06:46 AM ---------- Previous post was at 06:36 AM ----------
community.oppo.com/en/forum.php?mod=viewthread&tid=46578&extra=
Crap, link incomplete. Nevertheless, go to find 7 third party development section. It's all there.

URGENT TWRP switch back to stock recovery after reboot

I used this https://dl.twrp.me/oneplus3/twrp-3.0.2-0-oneplus3.img.html recovery to flash but after reboot to system and then to recovery it shows the stock recovery. Any help ?

That's quite normal. If you flash a stock rom without reinstalling twrp before rebooting system, you will lose twrp because stock rom will install stock recovery too . So, you have to install TWRP from adb by Fastboot again.
Enviado desde mi ONEPLUS A3003 mediante Tapatalk

samnaction said:
I used this https://dl.twrp.me/oneplus3/twrp-3.0.2-0-oneplus3.img.html recovery to flash but after reboot to system and then to recovery it shows the stock recovery. Any help ?
Click to expand...
Click to collapse
Honestly its not that urgent to be honest before you flashed the stock rom you should of read up on what was going to happen. Being knowledgeable about what you are doing is your biggest asset. Also its not that big of a deal reflash TWRP as mentioned and going forward do some reading before making moves
Also make sure the right stuff is checked off in your settings so that the stock recovery does not come back

if u can still boot into ur OS just download flashify and flash twrp via flashify, u can download twrp via flashify too
this is normal it happens from time to time

playya said:
Honestly its not that urgent to be honest before you flashed the stock rom you should of read up on what was going to happen. Being knowledgeable about what you are doing is your biggest asset. Also its not that big of a deal reflash TWRP as mentioned and going forward do some reading before making moves
Also make sure the right stuff is checked off in your settings so that the stock recovery does not come back
Click to expand...
Click to collapse
No it's not the issue I haven't flashed stock rom. I m flashing twrp for first time. Don't know what's the issue but it got fixed after I did factory reset and flashed twrp again

samnaction said:
No it's not the issue I haven't flashed stock rom. I m flashing twrp for first time. Don't know what's the issue but it got fixed after I did factory reset and flashed twrp again
Click to expand...
Click to collapse
did you follow these steps or did you just reboot directly into the OS
2. Flashing TWRP
Turn the phone off. Then boot it into fastboot mode by holding volume up + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img* ,Make sure that this file is placed on the desktop.
Open a new command prompt on desktop and run the following commands:
Code:
fastboot flash recovery recovery.img
Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed.
In TWRP, select Reboot and then select System. Now your phone will boot into System and you have cleared Steps 2/3 . Grats.

playya said:
did you follow these steps or did you just reboot directly into the OS
2. Flashing TWRP
Turn the phone off. Then boot it into fastboot mode by holding volume up + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img* ,Make sure that this file is placed on the desktop.
Open a new command prompt on desktop and run the following commands:
Code:
fastboot flash recovery recovery.img
Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed.
In TWRP, select Reboot and then select System. Now your phone will boot into System and you have cleared Steps 2/3 . Grats.
Click to expand...
Click to collapse
Yes I did. Don't know why it didn't work first time. Everything fine after factory resetting again

[SOLVED] Could not install TWRP

Hi,
I want to enable dualsim on my singlesim device and for that the TWRP has to be installed. After checking many threads, which less or more describe the same steps, I managed to unlock the bootloader and downloaded an "unofficial" twrp image for the Moto Z Play. But on the last step while trying to flash it I got the error "Image not signed or corrupt" and the image is not installed. Here is the output by flashing:
Code:
D:\Programs\Minimal ADB and Fastboot>fastboot.exe flash recovery twrp-3.1.1-0-addison.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (11374 KB)...
OKAY [ 0.255s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.246s]
finished. total time: 0.510s
Is there a way to avoid this error ?

Use: "fastboot flash recovery twrp.img" no quotes. I change the filename to just "twrp.img" less chance of typing something wrong.
and no the .exe you did.

FSabbane said:
Hi,
I want to enable dualsim on my singlesim device and for that the TWRP has to be installed. After checking many threads, which less or more describe the same steps, I managed to unlock the bootloader and downloaded an "unofficial" twrp image for the Moto Z Play. But on the last step while trying to flash it I got the error "Image not signed or corrupt" and the image is not installed. Here is the output by flashing:
Is there a way to avoid this error ?
Click to expand...
Click to collapse
I think it is flashed. After flashing the twrp via fastboot and u see that error then just ignore it, instead directly boot your phone in recovery mode using the volume buttons and look for the word "recovery" then press on power button then it booted there.

Jimi Mack said:
Use: "fastboot flash recovery twrp.img" no quotes. I change the filename to just "twrp.img" less chance of typing something wrong.
and no the .exe you did.
Click to expand...
Click to collapse
I've changed the filename to "twrp.img" and used the command:
Code:
fastboot flash recovery twrp.img
The output is exactly the same as before.

Kap_Tutan said:
I think it is flashed. After flashing the twrp via fastboot and u see that error then just ignore it, instead directly boot your phone in recovery mode using the volume buttons and look for the word "recovery" then press on power button then it booted there.
Click to expand...
Click to collapse
unfortunatly not, after entering the recovery mode I see the message "no command" and I have to hold the power button and press volume up to enter into the Android Recovery menu.

FSabbane said:
unfortunatly not, after entering the recovery mode I see the message "no command" and I have to hold the power button and press volume up to enter into the Android Recovery menu.
Click to expand...
Click to collapse
Try to redownload the twrp again, try to use the lower version not the updated one. And after u flash that then update it with the newest one. Lets see if its work

Kap_Tutan said:
Try to redownload the twrp again, try to use the lower version not the updated one. And after u flash that then update it with the newest one. Lets see if its work
Click to expand...
Click to collapse
I've tried with the following images:
twrp-3.1.1-0-addison.img
twrp-3.1.0-0-addison.img
twrp-3.0.2-0-addison.img
which were downloaded from the url: https://www.androidfilehost.com/?w=files&flid=126925
The result is the same by all of them.
Just to be sure, the image should be copied within the "ADB/Fastboot" folder on my PC and not on the device storage/SD card, isn't it ?

FSabbane said:
I've tried with the following images:
twrp-3.1.1-0-addison.img
twrp-3.1.0-0-addison.img
twrp-3.0.2-0-addison.img
which were downloaded from the url: https://www.androidfilehost.com/?w=files&flid=126925
The result is the same by all of them.
Just to be sure, the image should be copied within the "ADB/Fastboot" folder on my PC and not on the device storage/SD card, isn't it ?
Click to expand...
Click to collapse
Did u unlock bootloader?
Yap it should be in pc adb folder

Kap_Tutan said:
Did u unlock bootloader?
Yap it should be in pc adb folder
Click to expand...
Click to collapse
Yes, I did unlock it with the unlock key received from motorola:
Code:
fastboot oem unlock UNLOCK_KEY
After that a message is displayed at each start:
your device has been unlocked and can't be trusted
ID: bad key
your device will boot in 5 seconds
Click to expand...
Click to collapse

FSabbane said:
Yes, I did unlock it with the unlock key received from motorola:
After that a message is displayed at each start:
Click to expand...
Click to collapse
After flashing twrp do not boot the phone otherwise the stock recovery will over write twrp,
After twrp is flashed while still in fastboot mode, use the volume buttons and select recovery on the menu.

flashallthetime said:
After flashing twrp do not boot the phone otherwise the stock recovery will over write twrp,
After twrp is flashed while still in fastboot mode, use the volume buttons and select recovery on the menu.
Click to expand...
Click to collapse
That was it, at each boot the recovery partition was overwritten.
Thank you very much for the help !

still doesn't work for me
FSabbane said:
That was it, at each boot the recovery partition was overwritten.
Thank you very much for the help !
Click to expand...
Click to collapse
I am still getting error saying your device is unlocked can't be trusted and will be restarted in 5 seconds,
please help me out. Also need adb zip file

velpoori said:
I am still getting error saying your device is unlocked can't be trusted and will be restarted in 5 seconds,
please help me out. Also need adb zip file
Click to expand...
Click to collapse
This is not an error. If your bootloader is unlocked this message will display at every boot.

velpoori said:
I am still getting error saying your device is unlocked can't be trusted and will be restarted in 5 seconds,
please help me out. Also need adb zip file
Click to expand...
Click to collapse
As Fandroid mentioned, it's not an error. My device also diplays it at startup.
I've added to this post a zip file that contains adb, fastboot and twrp version used to configure my device.

FSabbane said:
As Fandroid mentioned, it's not an error. My device also diplays it at startup.
I've added to this post a zip file that contains adb, fastboot and twrp version used to configure my device.
Click to expand...
Click to collapse
Have you installed twrp successfully and which OS r u running on your moto z play right now, how is it?

velpoori said:
Have you installed twrp successfully and which OS r u running on your moto z play right now, how is it?
Click to expand...
Click to collapse
I wanted twrp just to create a backup and configure my device to support dualsim. Therefore and as mentioned in a previous post, TWRP is installed only momentarly and after a reboot it would be overwritten.
My OS is the Moto Android 7.0.
What is the issue that you have now ?

FSabbane said:
I wanted twrp just to create a backup and configure my device to support dualsim. Therefore and as mentioned in a previous post, TWRP is installed only momentarly and after a reboot it would be overwritten.
My OS is the Moto Android 7.0.
What is the issue that you have now ?
Click to expand...
Click to collapse
As I told earlier I am not able to install twrp due to which I am not able to install custom rom. I tried many times to install twrp, everytime it showed "image is not found" as you guys said I tried going recovery but again it shows you already unlocked boot loader, your device can't be trusted then says " your device will reboot in 5 seconds" this is what my issue is.

velpoori said:
As I told earlier I am not able to install twrp due to which I am not able to install custom rom. I tried many times to install twrp, everytime it showed "image is not found" as you guys said I tried going recovery but again it shows you already unlocked boot loader, your device can't be trusted then says " your device will reboot in 5 seconds" this is what my issue is.
Click to expand...
Click to collapse
So that we can see where you're stuck at the moment, please follow this guide and tell us which step didn't work :
https://www.obeygeek.com/install-twrp-recovery-on-moto-z-play/
P.S.: use the adb, fastboot and twrp image I've sent you in the previous post.

FSabbane said:
So that we can see where you're stuck at the moment, please follow this guide and tell us which step didn't work :
https://www.obeygeek.com/install-twrp-recovery-on-moto-z-play/
P.S.: use the adb, fastboot and twrp image I've sent you in the previous post.
Click to expand...
Click to collapse
I will try once I reach home by 6pm, you are so helpful thank you...

FSabbane said:
I wanted twrp just to create a backup and configure my device to support dualsim. Therefore and as mentioned in a previous post, TWRP is installed only momentarly and after a reboot it would be overwritten.
Click to expand...
Click to collapse
It makes no sense then to flash it. Why don't you just use
fastboot boot twrp.img
when you want to start it? Then no flash will be involved, and twrp will be just booted for this single usage. You can repeat this whenever you need it.

recover change every boots

Hello, I have unlocked my device and when I install twrp and reboot the official recover replaced with twrp. I have tried many times but after every reboot the stock recover is there. I need to flash twrp every time to use it.any reply ASAP will appreciate. Thanks in advance.

riyan65 said:
Hello, I have unlocked my device and when I install twrp and reboot the official recover replaced with twrp. I have tried many times but after every reboot the stock recover is there. I need to flash twrp every time to use it.any reply ASAP will appreciate. Thanks in advance.
Click to expand...
Click to collapse
Make sure are flashing it and not booting it
fastboot flash recovery recovery.img
Swipe to enable system modifications on first use
Full instructions on my twrp thread
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737

TheFixItMan said:
Make sure are flashing it and not booting it
fastboot flash recovery recovery.img
Swipe to enable system modifications on first use
Full instructions on my twrp thread
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
Click to expand...
Click to collapse
At first time only I have done this process, but also it changed the recover with stock recover.

riyan65 said:
At first time only I have done this process, but also it changed the recover with stock recover.
Click to expand...
Click to collapse
Root your phone & use the root method via the twrp app

TheFixItMan said:
Root your phone & use the root method via the twrp app
Click to expand...
Click to collapse
How do I root my device without twrp???

riyan65 said:
How do I root my device without twrp???
Click to expand...
Click to collapse
Oh I thought you could boot to it but it doesn't stick
If you can't get into twrp at all it's user error
Follow my guide on the twrp thread
Make sure you rename the image recovery.img
Put your phone into fastboot mode - hold Vol down & power button
Then in a cmd prompt where you have recovery.img & fastboot type
fastboot flash recovery recovery.img
Then use the volume keys to select recovery and press power button to select
Post your cmd output but it should say write OK at the end
Ignore the error is not signed or corrupt that comes before that
Obviously I presume you have already unlocked your bootloader - just follow all the instructions on the twrp thread
Also you don't reboot the phone between flashing twrp and entering twrp for the first time

TheFixItMan said:
Oh I thought you could boot to it but it doesn't stick
If you can't get into twrp at all it's user error
Follow my guide on the twrp thread
Make sure you rename the image recovery.img
Put your phone into fastboot mode - hold Vol down & power button
Then in a cmd prompt where you have recovery.img & fastboot type
fastboot flash recovery recovery.img
Then use the volume keys to select recovery and press power button to select
Post your cmd output but it should say write OK at the end
Ignore the error is not signed or corrupt that comes before that
Obviously I presume you have already unlocked your bootloader - just follow all the instructions on the twrp thread
Also you don't reboot the phone between flashing twrp and entering twrp for the first time
Click to expand...
Click to collapse
Hey, I was able to boot it and run the latest twrp and install the supersu but the root process failed as it gives me ram extraction failed and end then I thought reboot and install magisk, so I install it and download the zip file then when I try to go in recovery mode, twrp is not available as stock recover is there. I don't know why recover change automatically. Do you know the reason behind it why it changed?? Or do I need to do something to keep it. At the time of nougat I was able to use it without any problem as recover doesn' change,but in Oreo it happening.

riyan65 said:
Hey, I was able to boot it and run the latest twrp and install the supersu but the root process failed as it gives me ram extraction failed and end then I thought reboot and install magisk, so I install it and download the zip file then when I try to go in recovery mode, twrp is not available as stock recover is there. I don't know why recover change automatically. Do you know the reason behind it why it changed?? Or do I need to do something to keep it. At the time of nougat I was able to use it without any problem as recover doesn' change,but in Oreo it happening.
Click to expand...
Click to collapse
Supersu is very old and outdated (the reason for that error is supersu can't install in systemless mode because the kernel ramdisk paths are not compatible) but since supersu is ancient now it's pointless trying to get it to work
Use magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Flash in twrp
You may have to install the magisk manager app separately if its not in your app draw
Just download the apk and install it via any file manager

MIUI 12.0.4 TWRP flash problem

Hello everyone,
I'm a long time lurker, so before posting any questions, I always check if there's any kind of solution to the problem. Unfortunately, I didn't find any either on this forum or others.
After updating MIUI from 12.0.3 to 12.0.4, TWRP recovery got replaced by stock one, but previously, I just flashed TWRP again and everything was fine. Now, when I try to flash TWRP on 12.0.4, it just doesn't stay on the phone. I use this method to flash TWRP and install root.
When I open command prompt inside minimal_adb_fastboot 1.4.3 folder and follow the instructions, I get the following message:
target reported max download size of 804276224 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.606s]
writing 'recovery'...
OKAY [ 0.623s]
finished. total time: 2.230s
After that, when I try to boot into TWRP through cmd, the phone gets stuck on Redmi loading logo. After flash, when I open recovery with phone, TWRP boots, but shows gibberish inside internal storage. After the phone gets disconnected from cable, only stock recovery boots.
After I tried flashing TWRP with different approaches (disabling driver signature, safe mode, revoke usb debugging, reinstalling phone drivers in device manager...), somehow Magisk got wiped, but Magisk manager was left. My last resort was to factory reset and try to flash TWRP again, but it still gives the same results, sometimes in different forms.
Is there any possibility that Xiaomi's new "security" update block TWRP with their stock recovery?

Cravemonic said:
Hello everyone,
I'm a long time lurker, so before posting any questions, I always check if there's any kind of solution to the problem. Unfortunately, I didn't find any either on this forum or others.
After updating MIUI from 12.0.3 to 12.0.4, TWRP recovery got replaced by stock one, but previously, I just flashed TWRP again and everything was fine. Now, when I try to flash TWRP on 12.0.4, it just doesn't stay on the phone. I use this method to flash TWRP and install root.
When I open command prompt inside minimal_adb_fastboot 1.4.3 folder and follow the instructions, I get the following message:
target reported max download size of 804276224 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.606s]
writing 'recovery'...
OKAY [ 0.623s]
finished. total time: 2.230s
After that, when I try to boot into TWRP through cmd, the phone gets stuck on Redmi loading logo. After flash, when I open recovery with phone, TWRP boots, but shows gibberish inside internal storage. After the phone gets disconnected from cable, only stock recovery boots.
After I tried flashing TWRP with different approaches (disabling driver signature, safe mode, revoke usb debugging, reinstalling phone drivers in device manager...), somehow Magisk got wiped, but Magisk manager was left. My last resort was to factory reset and try to flash TWRP again, but it still gives the same results, sometimes in different forms.
Is there any possibility that Xiaomi's new "security" update block TWRP with their stock recovery?
Click to expand...
Click to collapse
copy your important data somewhere
reflash twrp again using
fastboot flash recovery twrp.img
Flash vbmeta.img using
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reboot to twrp using
fastboot boot twrp.img
(or pwr+vol up)
flash orangeFox recovery
flash dfe if you want to decrypt the storage and format data (not wipe)
in orangefox check the option :
aggressive stock recovery deactivation

loopypalm said:
copy your important data somewhere
reflash twrp again using
fastboot flash recovery twrp.img
Flash vbmeta.img using
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reboot to twrp using
fastboot boot twrp.img
(or pwr+vol up)
flash orangeFox recovery
flash dfe if you want to decrypt the storage and format data (not wipe)
in orangefox check the option :
aggressive stock recovery deactivation
Click to expand...
Click to collapse
Thanks for the reply.
Sorry for the late reply, had some other stuff on my hand.
Sorry for the stupid question, but do I need to download vbmeta.img from somewhere or just straight up use the the command without any downloaded file? I read that vbmeta files are all unique to their own devices, that's why I'm curious if it should be replaced at all.

Cravemonic said:
Thanks for the reply.
Sorry for the late reply, had some other stuff on my hand.
Sorry for the stupid question, but do I need to download vbmeta.img from somewhere or just straight up use the the command without any downloaded file? I read that vbmeta files are all unique to their own devices, that's why I'm curious if it should be replaced at all.
Click to expand...
Click to collapse
extract vbmeta from miui "A10" zip (not A11) or download the attached file

loopypalm said:
extract vbmeta from miui "A10" zip (not A11) or download the attached file
Click to expand...
Click to collapse
Ah, I see. Thanks for the help again.
I've downloaded MIUI 12.0.4 global from this website and extracted vbmeta.img.
I don't really want to replace TWRP with OrangeFox recovery, but since TWRP can be replaced by stock recovery after every update, I'll use Fox instead.

Cravemonic said:
I don't really want to replace TWRP with OrangeFox
Click to expand...
Click to collapse
TWRP is the "confort zone"
OFox is the "future"

loopypalm said:
TWRP is the "confort zone"
OFox is the "future"
Click to expand...
Click to collapse
After testing it out, I absolutely agree with you. Never thought that you can turn a simple mobile recovery into a modern PC mobo BIOS.
Additional kudos to recovery's devs for using a fox as a theme. As Firefox fan, the recovery looks really good with it.

Cravemonic said:
After testing it out, I absolutely agree with you. Never thought that you can turn a simple mobile recovery into a modern PC mobo BIOS.
Additional kudos to recovery's devs for using a fox as a theme. As Firefox fan, the recovery looks really good with it.
Click to expand...
Click to collapse
i'm more into functionalities than themes
but , yeah , it's a well done thing ...