Database Develop

[Q] HELP PLEASE Deleted OS cant install rom

I was trying to install ViperOne and everything went south. I somehow deleted my OS in the process. ADB is not working it only freezes my computer. I was able to ADB Push my viperone.zip but I tried the install and it fail for some reason and now it seems to be in a boot loop please help me with this.

also
i have been read all threads on here and there not really helping. just want to put that out there so i dont get called lazy for not searching.

1. Fix ADB issues.

SaHiLzZ said:
1. Fix ADB issues.
Click to expand...
Click to collapse
not sure of the reason for the freezing om the computer.

MuskRat40 said:
not sure of the reason for the freezing om the computer.
Click to expand...
Click to collapse
without adb you can't do anything.
please tell us more about what you did? What recovery are you using? What version? What rom version (and link please)? also post the output of ''fastboot getvar all'' minus IMEI/SN when in bootloader.
and what operating system are you using on your computer?

alray said:
without adb you can't do anything.
please tell us more about what you did? What recovery are you using? What version? What rom version (and link please)? also post the output of ''fastboot getvar all'' minus IMEI/SN when in bootloader.
and what operating system are you using on your computer?
Click to expand...
Click to collapse
***TAMPERED***
***UNLOCKED***
M7_UL PUT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.206.1
eMMC-BOOT 2048MB
I rooted my phone with the Hasoon2000 AIO kit
downloaded ViperOne5.5.0 from the link Here on XDA
I tried to install said ROM but it said it failed
so i thought I might delete a few thing and trying to rush because im at a library my OS was one of the things to go.
ADB pushed Viper back onto phone tried to install again and failed
tried to reboot and its a loop only thing opening now is fastboot and hboot
recovery flashes on for a sec then its gone.

fastboot erase cache did let me back into recovery but will not install
ViperOne v5.5.0 install failed
installer status 7

MuskRat40 said:
I rooted my phone with the Hasoon2000 AIO kit
Click to expand...
Click to collapse
Never use toolkit, learn how to use adb and fasboot. Toolkit are for lazy ppl imo. When something goes wrong with a toolkit then you can't know why.
MuskRat40 said:
downloaded ViperOne5.5.0 from the link Here on XDA
Click to expand...
Click to collapse
Did you downloaded the M7 version of viperone or the sprint version?
MuskRat40 said:
I tried to install said ROM but it said it failed
so i thought I might delete a few thing and trying to rush because im at a library
Click to expand...
Click to collapse
Take your time and don't rush, you will make things worse.
please answer all my questions:
please tell us more about what you did? What recovery are you using? What version? What rom version (and link please)? also post the output of ''fastboot getvar all'' minus IMEI/SN when in bootloader.
and what operating system are you using on your computer?
Click to expand...
Click to collapse
erase cache and flash latest twrp (2.6.3.3 or 2.6.3.4)
then use adb to push rom to sdcard or adb sideload your rom.
---------- Post added at 04:15 PM ---------- Previous post was at 04:07 PM ----------
MuskRat40 said:
fastboot erase cache did let me back into recovery but will not install
ViperOne v5.5.0 install failed
installer status 7
Click to expand...
Click to collapse
make sure you are using the correct recovery for your phone variant
md5 checksum the recovery.img after download before you flash it
also md5 checksum the rom before pushing it to the phone
did you selected ''full wipe'' at the installation?

alray said:
Never use toolkit, learn how to use adb and fasboot. Toolkit are for lazy ppl imo. When something goes wrong with a toolkit then you can't know why.
Did you downloaded the M7 version of viperone or the sprint version?
Take your time and don't rush, you will make things worse.
please answer all my questions:
erase cache and flash latest twrp (2.6.3.3 or 2.6.3.4)
then use adb to push rom to sdcard or adb sideload your rom.
Click to expand...
Click to collapse
right now im usind twrp touch v2.6.0.1 i downloaded the m7 verson and the tool is not getting the other stuff

alray said:
Never use toolkit, learn how to use adb and fasboot. Toolkit are for lazy ppl imo. When something goes wrong with a toolkit then you can't know why.
Did you downloaded the M7 version of viperone or the sprint version?
Take your time and don't rush, you will make things worse.
please answer all my questions:
erase cache and flash latest twrp (2.6.3.3 or 2.6.3.4)
then use adb to push rom to sdcard or adb sideload your rom.
---------- Post added at 04:15 PM ---------- Previous post was at 04:07 PM ----------
make sure you are using the correct recovery for your phone variant
md5 checksum the recovery.img after download before you flash it
also md5 checksum the rom before pushing it to the phone
did you selected ''full wipe'' at the installation?
Click to expand...
Click to collapse
md5?? not sure how to do that

MuskRat40 said:
right now im usind twrp touch v2.6.0.1 i downloaded the m7 verson and the tool is not getting the other stuff
Click to expand...
Click to collapse
your recovery version is pretty out dated.
as i said before, don't use toolkit, you know why now...
download latest twrp recovery here
Code:
fastboot flash recovery <name_of_file>.img
fastboot erase cache
fastboot reboot-bootloader
then go back in recovery and flash the rom again and select full wipe.

alray said:
your recovery version is pretty out dated.
as i said before, don't use toolkit, you know why now...
download latest twrp recovery here
Code:
fastboot flash recovery <name_of_file>.img
fastboot erase cache
fastboot reboot-bootloader
then go back in recovery and flash the rom again and select full wipe.
Click to expand...
Click to collapse
you are the man!!! TWRP was out dated. It says it was successful. its loading now. Thank you so much.

MuskRat40 said:
you are the man!!! TWRP was out dated. It says it was successful. its loading now. Thank you so much.
Click to expand...
Click to collapse
np, glad it worked
hope you learned this:
don't use toolkit
don't rush
newer roms don't like old recoveries (especially 4.4 roms) So in the future be sure to update your recovery to latest version (or that one specified in the rom thread) before flashing.
hope you'll enjoy your new rom :highfive:

[DUMP][STOCK] Recovery and boot images

I received my phone a while ago, I have dumped the stock recovery and boot image
Download them here
You can fastboot them
For boot
Code:
fastboot flash boot boot.img
For recovery
Code:
fastboot flash recovery recovery.img

Thank u
Sent from my Micromax AQ4501 using Tapatalk

varun.chitre15 said:
I received my phone a while ago, I have dumped the stock recovery and boot image
Download them here
You can fastboot them
For boot
Code:
fastboot flash boot boot.img
For recovery
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Could you also dump the system partition?

Hi @varun.chitre15 , thanks for ur works on android one devices.. May I know how did you dump these??

suribi said:
Could you also dump the system partition?
Click to expand...
Click to collapse
please upload system.img

suribi said:
Could you also dump the system partition?
Click to expand...
Click to collapse
Recognized Noob said:
please upload system.img
Click to expand...
Click to collapse
Will be uploaded by tomorrow, the size is large

yes :3
suribi said:
Could you also dump the system partition?
Click to expand...
Click to collapse
yes bro you can. Copy the system with adb command
PHP:
adb pull<space> /system <space>/system
---------- Post added at 02:35 PM ---------- Previous post was at 02:34 PM ----------
varun.chitre15 said:
Will be uploaded by tomorrow, the size is large
Click to expand...
Click to collapse
can we dump system as system.img using this fastboot method?

noobpremium said:
yes bro you can. Copy the system with adb command
PHP:
adb pull<space> /system <space>/system
---------- Post added at 02:35 PM ---------- Previous post was at 02:34 PM ----------
can we dump system as system.img using this fastboot method?
Click to expand...
Click to collapse
please explain the commands clearly ... not able to get it !

eatpepsi said:
please explain the commands clearly ... not able to get it !
Click to expand...
Click to collapse
PM me I'll explain :3

Use of stock recovery?
Hi Varun, please explain me: If I brick my Canvas A1, then I would be able to restore it like factory using these recovery & boot image? I'm a newbie with such terms.

stock recovery
thanks man

Hii
Varun... Beta 2 Plz Plz Plz

Great work varun

Please make stock boot,recovery,and system images for sprout4 LMY47V universal. Thanks!

[Q] (Bootloader) Failed to Erase partition Moto X 2014

I tried to go back to Stock with factory images from Motorola Unlocked. When i try fastboot flash partition gpt.bin it shows Preflash Validation Failed and Failed to erase partition error. I cannot even go into recovery I am stuck anyone please help!.
I am getting Failed to erase partition error when i try to flash anything!.

vignesh245 said:
I tried to go back to Stock with factory images from Motorola Unlocked. When i try fastboot flash partition gpt.bin it shows Preflash Validation Failed and Failed to erase partition error. I cannot even go into recovery I am stuck anyone please help!.
I am getting Failed to erase partition error when i try to flash anything!.
Click to expand...
Click to collapse
If you are in bootloader mode you should be able to get into recovery. Just hit volume down to scroll to recovery and then volume up to select recovery.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
vignesh245 said:
I tried to go back to Stock with factory images from Motorola Unlocked.
Click to expand...
Click to collapse
Just remember - you cannot downgrade the bootloader or the partition table!!

JulesJam said:
If you are in bootloader mode you should be able to get into recovery. Just hit volume down to scroll to recovery and then volume up to select recovery.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
Just remember - you cannot downgrade the bootloader or the partition table!!
Click to expand...
Click to collapse
It's not going into recovery or rebooting the only thing I see is the fastboot menu!! What ever I do to flash it says failed to erase partition!! can you tell me why this error in fastboot!

vignesh245 said:
It's not going into recovery or rebooting the only thing I see is the fastboot menu!! What ever I do to flash it says failed to erase partition!! can you tell me why this error in fastboot!
Click to expand...
Click to collapse
What should I do now!! to get my phone back working!

vignesh245 said:
It's not going into recovery or rebooting the only thing I see is the fastboot menu!! What ever I do to flash it says failed to erase partition!! can you tell me why this error in fastboot!
Click to expand...
Click to collapse
well the last guy who got that error had to format his data partition but he had an unlocked bootloader with TWRP and could get into TWRP.
What happens when you connect your phone in bootloader mode to your PC, open a command shell and type:
fastboot devices
Does it return your device's serial number?
---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------
vignesh245 said:
What should I do now!! to get my phone back working!
Click to expand...
Click to collapse
You should not be trying to flash a lower version of the partition table!!!!
You may have to do a factory reset.
---------- Post added at 07:18 PM ---------- Previous post was at 07:16 PM ----------
vignesh245 said:
I tried to go back to Stock with factory images from Motorola Unlocked. When i try fastboot flash partition gpt.bin it shows Preflash Validation Failed and Failed to erase partition error.
Click to expand...
Click to collapse
gpt.bin is the partition table. If you were trying to flash a lower version partition table than your bootloader version, you cannot do that!!!
What is your bootloader version?

JulesJam said:
well the last guy who got that error had to format his data partition but he had an unlocked bootloader with TWRP and could get into TWRP.
What happens when you connect your phone in bootloader mode to your PC, open a command shell and type:
fastboot devices
Does it return your device's serial number?
---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------
You should not be trying to flash a lower version of the partition table!!!!
You may have to do a factory reset.
Click to expand...
Click to collapse
Thanks for the reply!!
Yes it returns a Serial number in fastboot! How flash the correct partition?.

vignesh245 said:
Thanks for the reply!!
Yes it returns a Serial number in fastboot! How flash the correct partition?.
Click to expand...
Click to collapse
Is Motorola Device Manager installed on your computer? If not, install it:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Then connect your phone in fastboot mode to your computer and run MDM and see if MDM can repair your phone.
Also - are you using version 2 of mfastboot to flash?

vignesh245 said:
Thanks for the reply!!
Yes it returns a Serial number in fastboot! How flash the correct partition?.
Click to expand...
Click to collapse
its 60.11

vignesh245 said:
its 60.11
Click to expand...
Click to collapse
I am using normal fastboot ! and I have MDM install will try to repair using MDM !!

vignesh245 said:
its 60.11
Click to expand...
Click to collapse
That is the lollipop 5.0 bootloader. What version of stock were you trying to flash? Kit Kat 4.4.4? If so, that is what happened here - you tried to downgrade the partition table. You cannot downgrade the partition table once you upgrade the bootloader.
---------- Post added at 07:41 PM ---------- Previous post was at 07:40 PM ----------
vignesh245 said:
I am using normal fastboot ! and I have MDM install will try to repair using MDM !!
Click to expand...
Click to collapse
OK let me know how it goes.

JulesJam said:
That is the lollipop 5.0 bootloader. What version of stock were you trying to flash? Kit Kat 4.4.4? If so, that is what happened here - you tried to downgrade the partition table. You cannot downgrade the partition table once you upgrade the bootloader.
---------- Post added at 07:41 PM ---------- Previous post was at 07:40 PM ----------
OK let me know how it goes.
Click to expand...
Click to collapse
Thanks for the clarity in reply!!
Where can i get the stock rom and Files for lolipop 5.0 ?? So I can get back to my stock recovery!

vignesh245 said:
Thanks for the clarity in reply!!
Where can i get the stock rom and Files for lolipop 5.0 ?? So I can get back to my stock recovery!
Click to expand...
Click to collapse
Did MDM not fix your phone? Are you on the XT1095?
http://www.graffixnyc.com/motox.php#
Also, I don't know what build you are, there looks to be more than 1 build for 5.0. Check out the support thread that the link above links too.

JulesJam said:
Did MDM not fix your phone? Are you on the XT1095?
http://www.graffixnyc.com/motox.php#
Also, I don't know what build you are, there looks to be more than 1 build for 5.0. Check out the support thread that the link above links too.
Click to expand...
Click to collapse
MDM did not fix my phone yes I am on Xt1095.
Thanks will try it and let you know

vignesh245 said:
MDM did not fix my phone yes I am on Xt1095.
Click to expand...
Click to collapse
OK, it is probably the custom recovery.

JulesJam said:
OK, it is probably the custom recovery.
Click to expand...
Click to collapse
I am getting Preflash validation failed and I found I have 22.21.11 version installed using MDM. and it says in pink color error in phone as failed to downgrade primary_apt.
Can you help me with this now??

vignesh245 said:
I am getting Preflash validation failed and I found I have 22.21.11 version installed using MDM. and it says in pink color error in phone as failed to downgrade primary_apt.
Can you help me with this now??
Click to expand...
Click to collapse
I would not mess around with the partition table. See if you can do
fastboot format data
fastboot format cache
To wipe your data and cache partitions.

JulesJam said:
I would not mess around with the partition table. See if you can do
fastboot format data
fastboot format cache
To wipe your data and cache partitions.
Click to expand...
Click to collapse
I cannot do that it says the error as in the attached screenshot!
When I select recovery using volume up it says ||boot up failed||
Can Motorola help my situation Mine is a pure edition?
||version downgraded for primary_gpt||

vignesh245 said:
Can Motorola help my situation Mine is a pure edition?|
Click to expand...
Click to collapse
Yes. It is still under warranty. I would get a warranty replacement. If you can't flash anything in BL mode and can't get into recovery and MDM can't repair your phone, idk what else to do.
Motorola should let everyone who unlocks their bootloader know you can't downgrade the bootloader or partition table. They should release the factory images of every version of Android for a device and let people know they have to stick to the version for their bootloader
Quite frankly, this is Motorola's fault for not doing that.

JulesJam said:
Yes. It is still under warranty. I would get a warranty replacement. If you can't flash anything in BL mode and can't get into recovery and MDM can't repair your phone, idk what else to do.
Motorola should let everyone who unlocks their bootloader know you can't downgrade the bootloader or partition table. They should release the factory images of every version of Android for a device and let people know they have to stick to the version for their bootloader
Quite frankly, this is Motorola's fault for not doing that.
Click to expand...
Click to collapse
Thanks a lot will contact motorola get my device replaced !.

vignesh245 said:
I cannot do that it says the error as in the attached screenshot!
When I select recovery using volume up it says ||boot up failed||
Can Motorola help my situation Mine is a pure edition?
||version downgraded for primary_gpt||
Click to expand...
Click to collapse
try using the "erase" command instead of format, I've found on my PC format works, but on Mac I need to use erase.

LMY48B 5.1.1 Factory Image Now Up at Google's Site!!!

https://dl.google.com/dl/android/aosp/hammerhead-lmy48b-factory-596bb9c1.tgz
md5sum: 2002e1b813921b1dfc67aca09c30a171
sha1sum: 596bb9c125525ce5baf4762a1cac6f5880c50cbc

I dint have access to take a look from here. I know there's an updated radio. Is there also an updated bootloader?

mikebeatrice said:
I dint have access to take a look from here. I know there's an updated radio. Is there also an updated bootloader?
Click to expand...
Click to collapse
Yes, from HHZ12f to HHZ12h.

I Tried to flash 5.1.1 without wipe (-w )
however I had the error "failed to allocate 1046266608 bytes".
So after flashing bootloader and radio,
I had to extract all .img and flash them one by one :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot reboot
everything is working now ... I hope the damn memory leak bug is fixed.

Any new appearance or features?

Could you upload the new radio and bootloader? You could make something like this thread.
http://forum.xda-developers.com/goo...us5-update-bootloader-radio-lmy47d-5-t3052571

SA3DX said:
Could you upload the new radio and bootloader? You could make something like this thread.
http://forum.xda-developers.com/goo...us5-update-bootloader-radio-lmy47d-5-t3052571
Click to expand...
Click to collapse
You can download radio in this thread:
http://forum.xda-developers.com/goo...t/modem-nexus-5-flashable-modems-efs-t2514095

Matrix_19 said:
I Tried to flash 5.1.1 without wipe (-w )
however I had the error "failed to allocate 1046266608 bytes".
So after flashing bootloader and radio,
I had to extract all .img and flash them one by one :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot reboot
everything is working now ... I hope the damn memory leak bug is fixed.
Click to expand...
Click to collapse
The ADB Error of failed to allocate X Bytes is easily resolved with a reboot of your computer.

mike102871 said:
Any new appearance or features?
Click to expand...
Click to collapse
Generally .1 releases fix bugs, so no, there is no new features or appearance

markdapimp said:
The ADB Error of failed to allocate X Bytes is easily resolved with a reboot of your computer.
Click to expand...
Click to collapse
Sadly in my case this didn´t work. Thanks anyway.
Regards

Android 5.1.1 factory image
I want to know the changelog in android 5.1.1 (LMY48B). is it fix memory leak? and what features added in this OTA?

markdapimp said:
The ADB Error of failed to allocate X Bytes is easily resolved with a reboot of your computer.
Click to expand...
Click to collapse
Matrix_19 said:
I Tried to flash 5.1.1 without wipe (-w )
however I had the error "failed to allocate 1046266608 bytes".
So after flashing bootloader and radio,
I had to extract all .img and flash them one by one :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot reboot
everything is working now ... I hope the damn memory leak bug is fixed.
Click to expand...
Click to collapse
For me, this doesnt happen if i close CHROME and all other running programs and run fastboot as admin
for some reason even tho i have plenty of ram, i get that fail when chrome is open...i close that and fastboot does its thing fine

chaco81 said:
For me, this doesnt happen if i close CHROME and all other running programs and run fastboot as admin
for some reason even tho i have plenty of ram, i get that fail when chrome is open...i close that and fastboot does its thing fine
Click to expand...
Click to collapse
Good to know...
I'll try it next time

BiggerSpain said:
Sadly in my case this didn´t work. Thanks anyway.
Regards
Click to expand...
Click to collapse
Do you have the latest fastboot files?

xda6969 said:
Do you have the latest fastboot files?
Click to expand...
Click to collapse
I think so, but I flashed the system.img manually.
Thank you for your interest.
Regards
BiggerSpain

Same x bytes error for me on both a Win 8 PC and a Win 7 PC, Chrome open/closed doesn't matter. I finally flashed on a Linux machine. Took awhile to figure out Terminal, because this is the first time I've used Linux, but eventually got it right (I like a learning challenge). No problems with a Linux flash.

VivaErBetis said:
You can download radio in this thread:
http://forum.xda-developers.com/goo...t/modem-nexus-5-flashable-modems-efs-t2514095
Click to expand...
Click to collapse
I guess I wasn't clear enough. I want BOTH the new RADIO AND BOOTLOADER. Which part do you not understand?

SA3DX said:
I guess I wasn't clear enough. I want BOTH the new RADIO AND BOOTLOADER. Which part do you not understand?
Click to expand...
Click to collapse
Ho ho.....calm down Fury.....
Do you really believe that someone is willing to help you
when you write in this way???

krillehb said:
Ho ho.....calm down Fury.....
Do you really believe that someone is willing to help you
when you write in this way???
Click to expand...
Click to collapse
My thoughts exactly.
SA3DX If you download the factory image from google and unzip it everything is there. http://lmgtfy.com/?q=nexus+5+factory+images

SA3DX said:
I guess I wasn't clear enough. I want BOTH the new RADIO AND BOOTLOADER. Which part do you not understand?
Click to expand...
Click to collapse
Now Now stop having a tantrum
SENT BY ENTANGLEMENT
---------- Post added at 07:43 PM ---------- Previous post was at 07:28 PM ----------
Jamalleelee said:
My thoughts exactly.
SA3DX If you download the factory image from google and unzip it everything is there. http://lmgtfy.com/?q=nexus+5+factory+images
Click to expand...
Click to collapse
That link is so funny
SENT BY ENTANGLEMENT

TWRP Error changing bootloader boot slot to [a/b]

TWRP Error changing bootloader boot slot to [A/B]
Any idea why this is happening? I am currently on 3.2.3-0, but it has happened on all the other versions I have tried as well.

use fastboot to change the slot
- fastboot --set-active=a
- fastboot --set-active=b

LuisAngel321 said:
use fastboot to change the slot
- fastboot --set-active=a
- fastboot --set-active=b
Click to expand...
Click to collapse
Thanks. I will try that. I wonder if this is a known bug...

Anyone knows why this doesn't work? The fastboot commands don't work for me either.

jhedfors said:
Anyone knows why this doesn't work? The fastboot commands don't work for me either.
Click to expand...
Click to collapse
You did the '--set-active' from fastboot mode and not TWRP right? On mine I have to have an underscore before the slot like: fastboot --set-active=_b because my fastboot is not the most recent.
I did get that error once because I accidentally wiped /system on the slot I was trying to switch to. No /system means no TWRP.
moto x4 xt1900-1 payton_fi

ptn107 said:
You did the '--set-active' from fastboot mode and not TWRP right? On mine I have to have an underscore before the slot like: fastboot --set-active=_b because my fastboot is not the most recent.
I did get that error once because I accidentally wiped /system on the slot I was trying to switch to. No /system means no TWRP.
moto x4 xt1900-1 payton_fi
Click to expand...
Click to collapse
That was it. I was using an older version of fastboot.

jhedfors said:
Thanks. I will try that. I wonder if this is a known bug...
Click to expand...
Click to collapse
I have the same, but TWRP is 3.2.3.1, also I had a problem after last LOS 15.1 update, maybe this was main issue that efects bricking the device...
---------- Post added at 01:44 PM ---------- Previous post was at 01:20 PM ----------
jhedfors said:
That was it. I was using an older version of fastboot.
Click to expand...
Click to collapse
This do not work me..."fastboot --set-active=a" a result is "fastboot: unknown option -- set-active=_b" or b or a and _a

mikib1 said:
I have the same, but TWRP is 3.2.3.1, also I had a problem after last LOS 15.1 update, maybe this was main issue that efects bricking the device...
---------- Post added at 01:44 PM ---------- Previous post was at 01:20 PM ----------
This do not work me..."fastboot --set-active=a" a result is "fastboot: unknown option -- set-active=_b" or b or a and _a
Click to expand...
Click to collapse
For me, I had been using fastboot in a bash terminal on windows. I had not realized that I had a global variable that was pointing to an older installed fastboot. When I switched to using a windows cmd shell, it then used the fastboot that was in the folder. No expert here though...

jhedfors said:
For me, I had been using fastboot in a bash terminal on windows. I had not realized that I had a global variable that was pointing to an older installed fastboot. When I switched to using a windows cmd shell, it then used the fastboot that was in the folder. No expert here though...
Click to expand...
Click to collapse
Thank you I was able to solve the problem only by using new fastboot...
Thank you again for your reply...
Edit: After few tests with installing system on slot a and b and checking changes slots in TWRP I saw that change slots was only possible in terminal using fastboot. Maybe this can be a issue in TWRP 3.2.3.1 with correct operation changing slots, for example ni 3.2.1.0 it change without problem but do not decrypt data (this only TWRP 3.2.3.1 doing). I'm not IT developer, so I can be wrong. But this is my observation for today work with moto X4 XT1900-7

Oops, wrong thread.