Database Develop

[Q] After flashing TWRP, XT1063 only boots to the unlocked warning screen

My apologies if this has already been posted. I've been looking all morning but haven't seen anyone with the same issue.
Unlock bootloader: no problem.
Flash TWRP: I downloaded from http://teamw.in/project/twrp2/275, and I got an error about partition size mismatch, but that's ok, right?
But when I try to enter recovery, all I get is the warning screen that my phone is unlocked. The drivers are certainly installed correctly, and fastboot is working fine. I just can't get into recovery to flash a ROM!

Restoring to 4.4.4 stock worked like a charm.
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I've re-enabled USB debugging. Do I dare try to flash a custom recovery again?

Pandae said:
Do I dare try to flash a custom recovery again?
Click to expand...
Click to collapse
You can use Flashify to make a backup of your current recovery and to flash TWRP.img. should work like a charm.

But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.

Pandae said:
But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.
Click to expand...
Click to collapse
You're right. Latest motorola driver and [TOOL]Minimal ADB and Fastboot will do the trick.

Sorry, I should have clarified that when flashing TWRP, I've already been using fastboot.exe from a command line (and administrator level), with the drivers correctly installed. That's how I was able to unlock in the first place.
I did try it with the version of Fastboot you linked to (what I have works peachy for my Nexus 7), still the same thing. I can't boot into recovery and only get stuck at the Motorola unlocked warning.

Pandae said:
I can't boot into recovery and only get stuck at the Motorola unlocked warning.
Click to expand...
Click to collapse
Oh. Sorry. Can you post the output (terminal & device) of
Code:
fastboot devices
fastboot flash recovery NAME_OF_RECOVERY.img

I'd done "fastboot devices" already to verify, and it returns the serial number, though as I said it's clearly working since I was able to unlock as well as flash recovery. I'm flashing "TWRP2801-titan-motog-2014.img" that I downloaded from the TWRP site, and fastboot gives the standard messages about size and success (and my phone gives the size mismatch error).
It's so strange to me. I've flashed a custom recovery dozens of times on both generations of my Nexus 7s, but I've never seen this.

Pandae said:
It's so strange to me.
Click to expand...
Click to collapse
Yeah......have to meditate about that problem....... is your battery low? Fastboot mode of the device gives me all sorts of problems if it detects low battery

I had been using fastboot at 100% (literally finished a full charge) and 84%, but thanks for the continued attempts at explanation.

Oh, did you check the md5 checksum of your download?

Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?

Pandae said:
Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?
Click to expand...
Click to collapse
If you are willing to risk it, try a fresh download and try again. I've flashed TWRP more than 20 times by now and never recieved an error whatsoever. It basically the easiest thing to do.
Incase you are stuck again, don't reflash the entire stock rom. Just flash the recovery.img from the stock rom files.
OR
Try this:
HOW TO ROOT MOTO G 2014 with Temporary Custom Recovery
Cheers

I've flashed a custom recovery many a time and have helped people through it, though on Nexus 7s.
Now shall I compound the mystery? I didn't think yet to use ADB to make my phone reboot to recovery. I had assumed recovery wasn't working. So here we go, after booting into Android:
adb reboot devices: my phone's there.
adb reboot recovery: TWRP's working?! And now root is complete!
It doesn't make sense to me why I can't get into recovery from the bootloader, but I can get into it with the simple ADB command. But I appreciate all the help, thanks!

Pandae said:
It doesn't make sense to me why I can't get into recovery from the bootloader
Click to expand...
Click to collapse
A little workaround:
Install Android Terminal Emulator
Add "Term shortcut" widget.
In "Arguments" enter
Code:
su -c reboot recovery

ROOT HTC U PLay

This is a short guide on rooting for thous who are new to this stuff
Steps:
1: download adb platform tools from here
2: Unlock bootloader. follow the guide on htcdev.
make sure you have htc drivers installed so that you can use oem command in fastboot mode for unlocking
3: Download TWRP
4: Download SuperSU and copy it to your phone's internal memory
5: Enable USB debugging and type "adb reboot-bootloader" from pc
6: Type: "fastboot boot twrp-3.1.1-0-alpine.img"
make sure you have twrp image in same folder as adb.
7: Wait for sometime you will boot into twrp recovery from there select install and select the SuperSU zip file
8: reboot and check for root
Links:
http://www.supersu.com/download
https://developer.android.com/studio/releases/platform-tools.html

has anybody tried this? I'm a bit scared to be the first one

javnostra said:
has anybody tried this? I'm a bit scared to be the first one
Click to expand...
Click to collapse
You should make sure you get a pristine backup at hand, or a RUU appropriate to your device. Otherwise you'll never be able toreturn to a full stock system.
On the U11 it is possible to boot TWRP from fastboot, without flashing it and thus without touching stock recovery. That way I've been able to flash Magisk what's coming with MagiskSU and the possibility to use some Modules. And all without altering the system or replacing stock recovery in the first place.
Sent from my HTC U11 using XDA Labs

javnostra said:
has anybody tried this? I'm a bit scared to be the first one
Click to expand...
Click to collapse
Yes its working without flaws, i have tested it myself. also your not installing recovery this time your booting directly

dranzer006 said:
Yes its working without flaws, i have tested it myself. also your not installing recovery this time your booting directly
Click to expand...
Click to collapse
Thanks, I will try it then.

javnostra said:
Thanks, I will try it then.
Click to expand...
Click to collapse
It works. Thanks a lot. My phone is rooted

5m4r7ph0n36uru said:
You should make sure you get a pristine backup at hand, or a RUU appropriate to your device. Otherwise you'll never be able toreturn to a full stock system.
Click to expand...
Click to collapse
for anyone asking themselves how to backup
https://forum.xda-developers.com/showpost.php?p=53767160&postcount=2
or https://forum.xda-developers.com/showpost.php?p=53770286&postcount=4
or is there a different way these days? @5m4r7ph0n36uru
BerndM14 said:
Connect phone to PC, boot into bootloader mode and type fastboot boot name_of_recovery.img that'll just boot the custom recovery as opposed to flashing it, that way you can make a nandroid backup of all partitions including stock recovery.
Click to expand...
Click to collapse
an0ther said:
The guys method of using recovery to backup recovery will only work on Philz… Not twrp as it does not always backup stock recovery properly. The proper way to backup stock recovery is..
1. Root your phone, which can be done by towel root or by just booting a recovery like he said,
fastboot boot twrporwhatever.img, then flash supersu
2. Boot phone that has stock recovery
3. adb shell
4. su "watch your phone to grant root adb access if you haven't ever done it"
5. dd if=/dev/block/mmcblk0p43 of=/sdcard/recovery.img
6. This will put flashable recovery.img on your internal sd card. Copy this and save it for later
7. "fastboot flash recovery recovery.img" will get you back to stock recovery, "fastboot flash recovery twrporwhatever.img" to flash custom recovery.
Click to expand...
Click to collapse

If possible and a TWRP recovery is available one should boot to bootloader and try if the command fastboot boot name_of_twrp.img works. Make sure to NOT grant r/w at first boot and leave it ro. Now you can perform a backup of stock recovery, boot and system image (not system partition!) to obtain a pristine backup.
All else will alter system partitions md5 and the backup won't be pristine any longer. Due to block based OTA policy introduced by Google you won't be able to OTA without a pristine system image.
Sent from my HTC U11 using XDA Labs

Bro My Boot Loader is Locked.
Htc dev Not Relised Htc u play Boot loader.

I think these are the instructions. You need to register to access the link
https://www.htcdev.com/bootloader/unlock-instructions
or use my login:
lizba
ALJSDBf234LJABSf
edit: dont use my login. you have to register. you'll get a mail with another page plus a .bin file
https://www.htcdev.com/bootloader/unlock-instructions/page-4/

I have two questions.
1. If I fastboot to TWPR will it stay (flash for good) or after disconnecting my phone it will be gone ?
2. Can I flash Magisk instead of SuperSU ?

Code:
fastboot oem get_identifier_token
FAILED (remote: unknown command)
how i can solve it?

ex71 said:
Code:
fastboot oem get_identifier_token
FAILED (remote: unknown command)
how i can solve it?
Click to expand...
Click to collapse
need enable "OEM unlock" in developers menu, reboot into bootloader and select "download mode". Next steps from original guide.

ex71 said:
need enable "OEM unlock" in developers menu, reboot into bootloader and select "download mode". Next steps from original guide.
Click to expand...
Click to collapse
But in download mode there is no fastboot active ?! Until you installed the correct drivers

no "fastboot" (like a "one s", etc) on this phone. no fastboot usb
"fastboot" command work in "bootloader menu" and "download mode"
fastboot oem only in download mode

Hello. Please explain what I am doing wrong. I will download what is in points. I download this adb something, but it does not work. Nothing starts. Does not communicate with the phone. OCB. Could anyone write this guide so that he could understand and act?

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 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

Problems with flashing TWRP

I have the bootloader unlocked and everything ready to go.
However, when I execute "fastboot flash recovry <recovery_file_name>.img" the first thing that pops up on the cmd is:
(bootloader) has_slot:recovery not found
(bootloader) is_logical:recovery not found
After this it continues the flashing process and finishes with the okay status
However, after rebooting using "fastboot reboot" when I go back into the bootloader and select the recovery option I end up with the droid on his back and an orange triangle with an exclamation mark over him and No Command written under him
Can anyone help with this issue? I really want to flash a new ROM onto my nexus and I also really really want TWRP to work
Thanks,
Danush

Have you tried spelling "recovery" with an "e"?
It may be that your file name isn't properly spelled. I either rename the image to "TWRP. img" or copy the file name in Explorer and paste it into the CMD window so that there is no possibility of mis-spelling.
And another thought - is the TWRP image in the same directory as the fastboot exe?

dahawthorne said:
Have you tried spelling "recovery" with an "e"?
Click to expand...
Click to collapse
Oh yeah that's just a typo in my post ?
Thanks for pointing it out.
I do spell the "recovery" with an "e" and yet I have these issues

I added more comments while you were replying.
Try this:
https://forum.xda-developers.com/showpost.php?p=73648849&postcount=6

Do you have stock Android installed? It will replace any custom recovery with the stock recovery when you boot, unless you've flashed a kernel, mod (e.g. Magisk) or similar that disables that feature.
Don't reboot the device after flashing, boot to recovery instead.
(Don't bother with those "errors", they're just telling you that your device isn't A/B or have logical partitions.)
Edit: oh yeah... Should have checked the link @dahawthorne posted before posting myself. It tells you the same thing. D'oh!

Didgeridoohan said:
Do you have stock Android installed? It will replace any custom recovery with the stock recovery when you boot, unless you've flashed a kernel, mod (e.g. Magisk) or similar that disables that feature.
Don't reboot the device after flashing, boot to recovery instead.
(Don't bother with those "errors", they're just telling you that your device isn't A/B or have logical partitions.)
Edit: oh yeah... Should have checked the link @dahawthorne posted before posting myself. It tells you the same thing. D'oh!
Click to expand...
Click to collapse
Thanks so much for all the help!! After you mentioned it, it kinda hit me that yeah maybe that is what is happening since I used to reboot the device so maybe it was replacing TWRP with the stock recovery.

Hi,
My problem with Redmi Note 4 Snapdragon 625 2,02 GHz and unlocked trying to flash TWRP is like this (phone is in fastboot mode):
PS C:\Users\Dell\Downloads\platform-tools-latest-windows\platform-tools> fastboot devices
55050ae09804 fastboot
PS C:\Users\Dell\Downloads\platform-tools-latest-windows\platform-tools> fastboot flash recovery
fastboot: error: ANDROID_PRODUCT_OUT not set
How can I solve it? Please, help!

Didgeridoohan said:
Do you have stock Android installed? It will replace any custom recovery with the stock recovery when you boot, unless you've flashed a kernel, mod (e.g. Magisk) or similar that disables that feature.
Don't reboot the device after flashing, boot to recovery instead.
(Don't bother with those "errors", they're just telling you that your device isn't A/B or have logical partitions.)
Edit: oh yeah... Should have checked the link @dahawthorne posted before posting myself. It tells you the same thing. D'oh!
Click to expand...
Click to collapse
Don't reboot after flashing? Like when i try it says img unsigned or corrupted, and when i try to then boot into recovery via "fastboot boot recovery" i get sent to the normal Android OS, so what im getting from this is that i somehow have to manually get into the "no command" error window and then power+volume up and that just works? Ill test that, would be really awesome if it does.
Oh yea and booting into the twrp image with "fastboot boot twrp.img" sends to normal os aswell btw.