Database Users

[Q] I can't go into Recovery mode. Why?

I have the following problem, I can not go into recovery mode. I know how to do that.I have access only in fastboot menu.when i try to enter from fastboot menu to recovery mode i don't have connection with the PC , because the problem is DRIVERS to start the second step "step2-windows.bat" for rooting.
I HAVE GOLD CARD !!!!!! .I had all drivers before this problem drivers was added to the PC and the phone WAS rooted.
The problem is not in my Windows i try those step on ,Windows7, windows xp ,Linux Ubuntu 10.4. And errors are the same "unknown device" and is impossible to install drivers to ROOT the phone.
Before the phone can not detect the SD card.The problem is fixed now is working .Now the phone is with original ROM and is not rooted.May be I have to flash new bootloader or new recovery.img I don't know.
My cable is not damaged.
the reason that I want to enter in recovery mode is that i want to root the phone again.
!!!!!!!!!!!WHO CAN HELLP ME !!!!!!!!!!!!!
sorry for my bad english

Strange.......... how it could be:
release your battery, push the power to release residual power , maybe 1 minute, in sert the battery and try go to recovery again

BesFen said:
Strange.......... how it could be:
release your battery, push the power to release residual power , maybe 1 minute, in sert the battery and try go to recovery again
Click to expand...
Click to collapse
The same f**** message "device not recognized". And it start to search Drivers on windows 7 x86 (fresh installation before 30 min.).
"Android 1.0, Qualcomm CDMA technologies MSM " - searching for drivers .. and the message "device not recognized" or "unknown device"

problem occurs when app2sd install and replace all programs to sd card.I enter into recovery mode and i wipe all options.After reboot my sd card was unmounted ........
may be this will be helpful

Follow this:
http://android.modaco.com/content/htc-legend-legend-modaco-com/309961/usb-brick-rickrolled-b0rked-fixed/

I've had a similar problem during the rooting-process of my legend
I have Win7 X86 and it also couldn't find any drivers for the legend.
Then I installed the HTC Sync application found on the HTC-Homepage
So i would suggest that you do the same

It is not an usb driver issue.
The phone acting as different device depending of its mode normal/fastboot/recovery/usb mount etc
Boot to bootloader select fastboot
run on your computer "fastboot oem boot"
if you have any of thoose =1 you have to alter it to 0
where the bold down is of importance
Normal output is:
INFOTAG xxxxx
INFOCID is HTC__***
INFOserial numer: *********
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length = xxx
INFOactive commandline:
board_legend.disable_uart3=0
board_legend.usb_h2w_sw=0
board_legend.disable_sdcard=0
diag.enabled=0
board_legend.debug_uart=0
smisize=0
userdata_sel=0
androidboot.emmc=false
androidboot.baseband=7.08.35.21 (or other)
andriodboot.cid=HTC_XXX (different depending on serial )
androidboot.carrier=HTX-
androidboot.mid=
androidboot.keycaps=querty
androidboot.mode=normal
androidboot.serialno=xxxxxxxx
androidboot.bootloader=0.43.00001
no_console_suspend=1
console=null
aArm_partion[0].name=misc
aArm_partion[1].name=recovery
aArm_partion[2].name=boot
aArm_partion[3].name=system
aArm_partion[4].name=cache
aArm_partion[5].name=userdata
partition number=6
Valid partition num=6
mpu_nand_acpu_rw 8F2 1000

result is :
Code:
C:\android SDK\tools>fastboot oem disable_uart3=0
... INFO[ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android SDK\tools>fastboot oem usb_h2w_sw=0
... INFO[ERR] Command error !!!
OKAY [ 0.000s]
finished. total time: 0.016s
C:\android SDK\tools>fastboot oem boot
... INFOsetup_tag addr=0x60000100 cmdline add=0x9D
078D14
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x22F00
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is HTC__032
INFOsetting->cid::HTC__032
INFOserial number: HT03YNX02877
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =446
INFOactive commandline: board_legend.disable_uart3=1 board_legen
INFOd.usb_h2w_sw=1 board_legend.disable_sdcard=0 diag.enabled=0
INFOboard_legend.debug_uart=0 smisize=0 userdata_sel=0 androidbo
INFOot.emmc=false androidboot.baseband=7.05.35.26L androidboot.
INFOcid=HTC__032 androidboot.carrier=HTC-EastEurope androidboot.
INFOmid=PB7610000 androidboot.keycaps=qwerty androidboot.mode=no
INFOrmal androidboot.serialno=HT03YNX02877 androidboot.bootloade
INFOr=0.43.0001 no_console_suspend=1 console=null
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFOmpu_nand_acpu_rw 8F2 1000
FAILED (status read failed (Too many links))
finished. total time: 0.874s
the phone must be rooted main is not this is the problem and what this mean
FAILED (status read failed (Too many links))

this is your problem:
board_legend.disable_uart3=1
board_legend.usb_h2w_sw=1
The FAIL string at bottom is normal.

this is your problem:
board_legend.disable_uart3=1
board_legend.usb_h2w_sw=1
The FAIL string at bottom is normal.
So you tell us that you have succeed with unrooting and lock usbcontroller.
Umm, sounds like and bad combination.
I had the uart3=1 probleb but still rooted and could insert new mtd0.img
have you tested to replace this two files?
http://www.shadowchild.nl/mtd0legend.img
http://www.shadowchild.nl/flash_image
download to your sdcard direct or with other usb/sdcard writer.
install terminal
open run
su
to check if it it still rooted
if so
chmod 755 /data/flash_image
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0legend.img > /data/mtd0.img
/data/flash_image misc /data/mtd0.img
and reboot

I assume you updated your legend to rom >2.03 (or any above 2.xx) you will have to downgrade
http://forum.xda-developers.com/showthread.php?t=725430
when you downgrade, root the legend again (fastboot usb > step1) then recovery mode >> step2
should work, worked for me tho. If not do step1 few times and try step2 again

snakehult said:
this is your problem:
Board_legend.disable_uart3=1
board_legend.usb_h2w_sw=1
the fail string at bottom is normal.
So you tell us that you have succeed with unrooting and lock usbcontroller.
Umm, sounds like and bad combination.
I had the uart3=1 probleb but still rooted and could insert new mtd0.img
have you tested to replace this two files?
http://www.shadowchild.nl/mtd0legend.img
http://www.shadowchild.nl/flash_image
download to your sdcard direct or with other usb/sdcard writer.
Install terminal
open run
su
to check if it it still rooted
if so
chmod 755 /data/flash_image
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0legend.img > /data/mtd0.img
/data/flash_image misc /data/mtd0.img
and reboot
Click to expand...
Click to collapse
thank you !!!

no way.....its not working showing
C:\sdk\tools>chmod 755 /data/flash_image
'chmod' is not recognized as an internal or external command,
operable program or batch file.
C:\sdk\tools>cat /sdcard/flash_image > /data/flash_image
The system cannot find the path specified.

no no
you most run that on your phone.
install terminal emulator or similar
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

i can't download......... showing insufficient storage........i even can't install application through 91pc suite for android..........i need help....

how do i type this in terminal all at once or sentence by sentence?

do exactly what he does :
http://android.modaco.com/content/h...com/309961/usb-brick-rickrolled-b0rked-fixed/
after unbricking your usb , install a stock rom not a custom coz you need a clean system.img.
If you don't do that, usb bricking will come again after flashing with a custom rom...
You can install a new stock rom ( like 2.03 etc... ) and use the thread "how to downgrade to 1.31" and root your legend again.
Another solution :
If the rom is not rooted and you can't follow unbrick instructions try this ( it's what i've done but not sure if result will be the same for you... ) :
Go to recovery mode ( power + volume down ) , select fastboot and try step 1 of rooting process, that will push 1.31 rom + some necessary tool to root the rom.
if all succeded , you will have a 1.31 rom apparently not rooted... but ! yes but ! after installing "connectbot" from market and select "local" and type 2 time "su" i got root access ! if not try step 1 of rooting process under fastboot mode.
If all is ok and you have ( like me ) root acces ( after typing 2 times "su" you will past from $ to # at the beginning of the line... ) , follow unbrink process .
Code:
if your phone can't even see the memory card, enable first with:
fastboot oem enableqxdm 0
Do the above step in Recovery mode.
Once the memory card is visible, transfer the files "flash_image" and "mtd0.img" to the memory card
howevor is possible.
Restart the phone, and install connectbot from the market.
Open connectbot, and through terminal (local) issue the following commands:
su [B][U](2 times)[/U][/B]
cat /sdcard/flash_image > /data/flash_image "then press enter"
cat /sdcard/mtd0.img > /data/mtd0.img "then press enter"
chmod 755 /data/flash_image "then press enter"
[B][U]and to finish process type the following command 2 times[/U] :[/B]
/data/flash_image misc /data/mtd0.img "then press enter"
It will give you 2 errors, on the last command, but ignore it and restart the phone
It should be fixed.
after that i had upgraded to an official stock rom to get back a clean system.img and boot.img. oh yes... phone again unrooted... ok... downgrade to 1.31 and root again

Isn't there a noob friendly way to unbrick.i couldn't possibly do all of that.
Sent from my HTC Legend using XDA App

THANK YOU!!!!
My phone lost the ability to read SD-cards and this thread helped me tremendously. I was just about to sell it or go and buy a new one or something.
Hugs to all!

heelp me
Very very much please help me fix my htc my legend. I do not see sd card, I can not root them anymore, can not find drivers. I do only step 1, you want to put up two do not communicate with the PC. Do not know much about Android, where I do not know the commands to be written, please help me. TeamViewer eventually get through to my PC. My address is [email protected] messenger. I pray a lot.

HTC One M7 does not start - after making Wipes Data, Cache and Dalvik

HTC One M7 does not start - after making Wipes Data, Cache and Dalvik Team Wim Recovery Projetct 3.0.2-0
No OS installend!
1 - ADB commands ok
2 - Drives ok
3 - recovery mode ok
NOTE:
HTC One M7 RUU Collection not recovered.
Unknown error.
LOGs: Team Wim Recovery Projetct 3.0.2-0
Updating partition details...
...done
Unable to find partition for '/system'
Unable to find partition for '/data'
Unable to find partition for '/cache'
Full SELinux support is present...
Unable to find partition for '/cache'
Unable to find partition for '/cache'
Phone Info:
Model : M7_UL
IMEI : #################
Build : 7.19.401.51
CID : HTC__001
HBoot : 1.61.0000
MID : PN0710000
Security : ON
Region : HTC_WWE
Model ID : PN0710000,
CID : HTC__001,HTC__J15,HTC__E11,HTC__203,HTC__102,HTC__405,HTC__Y13,HTC__A07,HTC__304,HTC__032,HTC__016,
MainVer : 7.19.401.51,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No storage

rodrigocm said:
HTC One M7 does not start - after making Wipes Data, Cache and Dalvik Team Wim Recovery Projetct 3.0.2-0
No OS installend!
1 - ADB commands ok
2 - Drives ok
3 - recovery mode ok
NOTE:
HTC One M7 RUU Collection not recovered.
Unknown error.
LOGs: Team Wim Recovery Projetct 3.0.2-0
Updating partition details...
...done
Unable to find partition for '/system'
Unable to find partition for '/data'
Unable to find partition for '/cache'
Full SELinux support is present...
Unable to find partition for '/cache'
Unable to find partition for '/cache'
Phone Info:
Model : M7_UL
IMEI : #################
Build : 7.19.401.51
CID : HTC__001
HBoot : 1.61.0000
MID : PN0710000
Security : ON
Region : HTC_WWE
Model ID : PN0710000,
CID : HTC__001,HTC__J15,HTC__E11,HTC__203,HTC__102,HTC__405,HTC__Y13,HTC__A07,HTC__304,HTC__032,HTC__016,
MainVer : 7.19.401.51,
No storage
Click to expand...
Click to collapse
Pretty normal that the recovery can't find any partition if you wiped everything. Was your bootloader re-locked when flashing the RUU? It must be when S-ON.

alray said:
Pretty normal that the recovery can't find any partition if you wiped everything. Was your bootloader re-locked when flashing the RUU? It must be when S-ON.
Click to expand...
Click to collapse
What do you install?
M7_UL
7.19.401.51 decrypted (s-off only)
7.19.401.51 Signed
How do I install?
Thanks for answering friend.

Xperia Z5 Lineage OS 17.1(Android 10) GAPPS issue [FIX]

Hi guys so recently i decided to change my Recovery and Firmware on my Xperia Z5 dual (E6683) i decided to flash Lineage OS 17.1 UNOFFICIAL-SUMIRE after that i decided to flash both GAPPS and Magisk But theres an issue "PERMISSION ISSUE" on GAPPS andriod setup i did manage to get it working via these steps hope this helps you
Requirements:
Windows/Mac with ADB installed
Phone (guessing you have TWRP and Lineage installed)
USB cable (obviously you will need this)
ADB SHELL COMMAND FOR SYSTEM UI HAS STOPPED WORKING/ANDRIOD SETUP HAS STOPPED WORKING (LINEAGE OS 17.1 ANDRIOD 10 Q)
FIX:
1ST INSTALL LINEAGE OS THROUGH TWRP RECOVERY (DO NOT INSTALL GAPPS FIRST!)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2ND REBOOT DEVICE
3RD SETUP THE DEVICE AS NORMAL THEN AFTER THAT GO TO SETTING>ABOUT PHONE TAP BASEBAND VERSION 4 TIMES TO UNLOCK DEVELOPER MODE
4TH GO TO SETTINGS>SYSTEM>DEVELOPER OPTIONS THEN FIND USB DEBUGGING ENABLE IT
5TH REBOOT DEVICE TO RECOVERY
6TH INSTALL GAPPS
7TH REBOOT TO SYSTEM
8TH OPEN CMD AND TYPE cd C:\Users\(username)\(file directory)\adb CLICK ENTER
9TH TYPE COMMANDS DOWN BELOW....
STAT REPORT:adb shell dumpsys package com.google.android.setupwizard
FIX CMD
adb shell pm grant com.google.android.setupwizard android.permission.CALL_PHONE
adb shell pm grant com.google.android.setupwizard android.permission.GET_ACCOUNTS
adb shell pm grant com.google.android.setupwizard android.permission.PROCESS_OUTGOING_CALLS
adb shell pm grant com.google.android.setupwizard android.permission.READ_CONTACTS
adb shell pm grant com.google.android.setupwizard android.permission.READ_PHONE_STATE
adb shell pm grant com.google.android.setupwizard android.permission.WRITE_CONTACTS
adb shell pm grant com.google.android.setupwizard android.permission.READ_OWNER_DATA
adb shell pm grant com.google.android.setupwizard android.permission.WRITE_OWNER_DATA
NOTE IGNORE ERROR: Bad argument: java.lang.IllegalArgumentException: Unknown permission: android.permission.READ_OWNER_DATA
AFTER SUCCESSFUL COMMANDS CHECK STATUS BAR FOR THE FINISH YOUR SETUP DEVICE AND THERE YOU GO THE SETUP SHOULD GO SMOOTH FROM HERE )

[GUIDE] Overlapping Partition Tables? Let's fix that

WARNING! Main partition table overlaps the first partition by 6 blocks!
You will need to delete this partition or resize it in an other utility.
This guide is to help those, facing this message, who have been in a mixup when repartitioning their Google Pixel 2 XL devices with the introduction of Android 12 and later ROMs/GSI Images.
More specifically this situation occurs when one follows Dollscythe's 3.8GiB system guide, followed by my (PixelExperience) repartition script.
No worries, let's solve this.
DISCLAIMER:
I AM NOT RESPONSIBLE IF THESE FOLLOWING INSTRUCTIONS ARE NOT EXECUTED PROPERLY.
KINDLY TRIPLE CHECK THE COPIED COMMANDS BEFORE EXECUTING THEM.
ANY ALTERATION TO THE PARTITIONS NOT MENTIONED BELOW COULD CAUSE SERIOUS ISSUES.
Firstly, let's understand why this occurs.
When it comes to repartitioning using sgdisk, with the case of the PixelExperience repartition method, blocks strictly defined from a starting to an ending logical sector.
(FYI: 1 logical sector = 4096 bytes)
When a user follows Dollscythe's 3.8GiB system guide, using parted, in contrast to sgdisk, the logical system sectors are modified to allow 3.8GiB of size.
Whilst this method is ideal for those planning to either flash GSI images which require specifically a larger system image, rather than making use of both product and system_ext partitions on PixelExperience and other ROMs, it is not ideal to mix them both up with each other.
(Both product and system_ext partitions offload large data from the system image, with such system apps like GApps)
So to break this down:
System is modified to adapt to 3.8GiB.
Logical starting and ending sectors system_a, system_b, pstore, aes_a, aes_b, align_parti and userdata partitions are modified.
PixelExperience script attempts to delete stock partition's userdata, but instead conflicts with 3.8GiB table.
Partition table becomes overlapped. (numerical partition numbers are not in order)
That is why it is important to keep track of which partition table your device is currently running, before making any further alterations to your system's table.
To check your current partition table, reboot into a custom recovery that supports the ADB interface via platform tools and:
Code:
adb shell
Code:
sgdisk --print /dev/block/sda
The output of this command should indicate what table you are currently running, depending on the sizes of both system_a and system_b partitions (2.5GiB on stock), or any added ones such as product and system_ext.
So double check that you are running the stock partition table before undergoing any of the guides mentioned above.
It is also worth noting that Pixel 2 XL (taimen) devices, do not revert to the stock partition table upon flashing the stock image.
This behaviour is not the same for Pixel 2 (walleye) devices, as when the stock image is flashed, the partition table is reverted to default.
(This is due to LG and HTC's bootloader behaving in different ways.)
Now, let's untie this knot!
Got the error now? Let's get started.
In short, we're going to undo the changes made, that includes both system_a and system_b partitions to the device, and redo it carefully.
Since sgdisk (installed on the device, by default) is unable to make any changes if it is found in an overlapping state, we will be using parted instead.
Download parted
Ensure you are in an ADB supported custom recovery.
Using platform-tools on an external device, push parted to the device:
Code:
adb push path/to/parted /sbin
Enter adb shell:
Code:
adb shell
Change permissions of parted:
Code:
chmod 777 /sbin/parted
Execute parted:
Code:
parted /dev/block/sda
Print current partition table:
Code:
p free
Remove overlapped partitions (when prompted, return ignore)
Code:
rm 17
rm 16
rm 15
rm 12
rm 11
rm 10
rm 9
rm 8
Recreate stock partitions
Code:
mkpart system_a ext4 169MB 2853MB
mkpart system_b ext4 2853MB 5538MB
mkpart pstore 5538MB 5546MB
mkpart aes_a 5546MB 5547MB
mkpart aes_b 5547MB 5548MB
mkpart align_parti 5548MB 5549MB
mkpart userdata ext4 5549MB 62400MB (for 64GB)
mkpart userdata ext4 5549MB 126300MB (for 128GB)
Wipe -> Format Data -> Yes
Wipe -> Factory Reset
Reboot -> Bootloader
That is what it takes to resort back to the stock partition table.
If done successfully (check via sgdisk --print /dev/block/sda), you can proceed to executing any repartition guide.

Reserved

Hello,
can someone please help me?
I tried to follow the guide to reset the partitions to default, but unfortunately it didn't work. Currently my partitions look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What must i do now to reset the partitions correctly?
I think only ext2 on system_a is incrorrect. It must be ext4?
@PixelBoot you have a small typing error on 9. Recreate Stock Partions:
mkpart system_a ext4 169MB 2853MBmkpart system_b ext4 28533MB 5538MB
On system_b you have 28533MB insteat of 2853MB
Edit: I think i have corrected it now:
I have make these additional steps in fastboot:
fastboot format:ext4 system_a
fastboot format:ext4 system_b
fastboot format:ext4 userdata
Device is booting now with Factrory Image

Cannot install twrp via fastboot, after oem unlock - troubleshooting

Hi,
I hope somebody will help to me figure out what I'm doing wrong. The problem maybe with the adb/fastboot, but I don't know how I can check it.
So, I have a bah-w09 with stock Hua ROM (EMUI 5.1.2, Android 7.0). I've used this guied for unlock bootloader: https://forum.xda-developers.com/t/...wei-mediapad-m3-8-4-btv-w09-btv-dl09.4085383/
It looks like everything is fine, but when I was tried to install twrp.img it's looks ok, but the download procedure is for 0,752 sec long, so finished around 1 sec. It's too quick and nothing happend with the tablet.
I've used the 3.2.0.0 from this thread ( I've also tried different source but with same results).
I tried two different windows 10 laptop, installed new adb/fastboot and usb drivers, run the fastboot with Administrator rigths, put the img in under "c:\twrp\twrp.img" and also renamed to "recovery.img"
In fastboot mode, under the green android droid: "PHONE Unlocked" "FRP Unlock"
In the Developer settings the "OEM Unlock" is greyed out and of course the USB Debuging is enabled.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is some results:
c:\Program Files (x86)\Minimal ADB and Fastboot>adb version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
...
FAILED (remote: unknown command)
finished. total time: 0.004s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: Already in UNLOCKED state)
finished. total time: 0.009s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 531628032 bytes
sending 'recovery' (23760 KB)...
OKAY [ 0.752s]
writing 'recovery'...
OKAY [ 0.402s]
finished. total time: 1.157s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.751s]
booting...
In this case, the cmd stucked in this positions and the cmd lost the connection (fastboot devices not given back result until I pressed ctrl+c).
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
c:\Program Files (x86)\Minimal ADB and Fastboot>
Could you please help me to figure out why is happening? or
what can I check to figure out what is the problem?
Thanks

OK, my mistake... Need to use the proper way to get the twrp recovery.
so, after then the twrp flashed, need to unplug the usb, and press and hold the volume up and power button, and after that will be load the TWRP recovery.