hello,
today i downloaded the Android 5.0 Image from Google and wanted to flash it.
i extraced the tgz file and flashed the boot.img and system.img via fastboot.
so far so good. i reboot the tabelt and it has a bootloop.
so i used the flash-all.bat included in the tgz file but it wont flash it (didnt copied the error message)
so i tried flashing 4.4.4. but when i flash anything it wont work (fastboot flash recovery recovery.img for example)
i tried differend usb ports and with fastboot devices it shows my device.i tried rebooting the laptop and the tablet. no changes
example
Code:
C:\Users\xxx\Desktop\nakasi-lrx21p>fastboot flash recovery recovery.img
sending 'recovery' (5682 KB)...
after 20 min of waiting nothing changes.
my setup:
a laptop with windows 8.1
all drivers installt
original nexus 7 usb cable
drivers are working fine. i often flashed something on the n7 and my m7 bevor on this laptop
Code:
C:\Users\xxx\Desktop\nakasi-lrx21p>fastboot flash boot boot.img
sending 'boot' (5146 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
thats a error message i get when something more happens then "sending 'xxx' (xxx kb)
Code:
FAILED (data transfer failure (Too many links))
finished. total time: 85.114s
now i managed to flash recovery (TWRP)
but i cant do anything there. in the pc its not listet (adb devices) and in the log of TWRP it says
Code:
E:Unable to mount '/data'
E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/data'
now i got in TWRP (changing to Clockworkmod Recovery doesnt change anything) and got to Wipe-> Advanced
there i tried to repair the partions . doesnt works. but if i format it that works and could be mounted again. (in system i have to format it in an different file format and back to ext4)
so now i flashed the rom (stock 5.0 from google) and it boots... waiting whats coming next....
etsch said:
now i got in TWRP (changing to Clockworkmod Recovery doesnt change anything) and got to Wipe-> Advanced
there i tried to repair the partions . doesnt works. but if i format it that works and could be mounted again. (in system i have to format it in an different file format and back to ext4)
so now i flashed the rom (stock 5.0 from google) and it boots... waiting whats coming next....
Click to expand...
Click to collapse
i have the same problem how did you format it and did it fix the problem
do you have TWRP ?
you go to wipe-> advanced
there you can choose which repair and format.
ive formated one by one and then it shows the size after formating.
now my tablet booted into android (i think its ugly) but iam afraid going in the recovery
My tablet is Lenovo yoga tab 3 plus, I have rooted my tablet, and after downloading the update, an error occured, and here is the log:
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Source: Lenovo/YT-X703F/YT-X703F:6.0.1/S100/YT-X703F_S000691_161121_PRC:user/release-keys
Target: Lenovo/YT-X703F/YT-X703F:6.0.1/S100/YT-X703F_S000728_170211_PRC:user/release-keys
Verifying current system...
"EMMC:/dev/block/bootdevice/by-name/boot:31655208:db7b430aac30b324daddf17bcdb14201a6468700:31655208:4de06d70f69d35ffa0a0aa0c6975385a3c937030" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation abroated.
E:failed to mount /data (Invaild argument)
I think if we can bypass verification, we can install update while the device is rooted.
Any can help us?
zkn1021 said:
My tablet is Lenovo yoga tab 3 plus, I have rooted my tablet, and after downloading the update, an error occured, and here is the log:
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Source: Lenovo/YT-X703F/YT-X703F:6.0.1/S100/YT-X703F_S000691_161121_PRC:user/release-keys
Target: Lenovo/YT-X703F/YT-X703F:6.0.1/S100/YT-X703F_S000728_170211_PRC:user/release-keys
Verifying current system...
"EMMC:/dev/block/bootdevice/by-name/boot:31655208:db7b430aac30b324daddf17bcdb14201a6468700:31655208:4de06d70f69d35ffa0a0aa0c6975385a3c937030" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation abroated.
E:failed to mount /data (Invaild argument)
I think if we can bypass verification, we can install update while the device is rooted.
Any can help us?
Click to expand...
Click to collapse
So the easiest way is to restore the boot and system partition to the original S000725 version using fastboot and then install the update, but only if you are on S000725 now. If you are sure that you didn't modify the system partition (any root app installed system less) then the boot partition is sufficient. Flashing these two partitions will not delete your apps and settings.
Here is what to do:
Download the factory image S000725 for your tablet (see first post of TWRP thread) and make sure your current software version is S000725
Extract it and get the boot.img and system.img files
restart into fastboot mode (e.g. via adb reboot bootloader, or restart the tablet with volume up key pressed)
Execute fastboot on your PC connected to the tablet with the following command:
Code:
fastboot flash boot boot.img
If the system partition was modified you will have to do the same for system
Code:
fastboot flash system system.img
If TWRP is flashed you also have to restore the recovery partition
Code:
fastboot flash recovery recovery.img
You can also install the factory image via the supplied flash tool. But we're not 100% sure it is safe wrt. DRM keys
Sometimes the flashing of such large partitions as the system partitions can fail in which case you have to do it again until it works. If you run into a bootloop after flashing the boot.img your system partition is not original and you have to flash the system.img again
EDIT: Ok I see you are on S000691 in which case you need a factory image of that version
matshias said:
So the easiest way is to restore the boot and system partition to the original S000725 version using fastboot and then install the update, but only if you are on S000725 now. If you are sure that you didn't modify the system partition (any root app installed system less) then the boot partition is sufficient. Flashing these two partitions will not delete your apps and settings.
Here is what to do:
Download the factory image S000725 for your tablet (see first post of TWRP thread) and make sure your current software version is S000725
Extract it and get the boot.img and system.img files
restart into fastboot mode (e.g. via adb reboot bootloader, or restart the tablet with volume up key pressed)
Execute fastboot on your PC connected to the tablet with the following command:
Code:
fastboot flash boot boot.img
If the system partition was modified you will have to do the same for system
Code:
fastboot flash system system.img
You can also install the factory image via the supplied flash tool. But we're not 100% sure it is safe wrt. DRM keys
Sometimes the flashing of such large partitions as the system partitions can fail in which case you have to do it again until it works. If you run into a bootloop after flashing the boot.img your system partition is not original and you have to flash the system.img again
EDIT: Ok I see you are on S000691 in which case you need a factory image of that version
Click to expand...
Click to collapse
Thank you！
I'm wondering whether I have to root again after restoring the boot and system partitions.
I got the OTA update package, can I flash it directly via recovery? I have rooted my tablet.
zkn1021 said:
Thank you！
I'm wondering whether I have to root again after restoring the boot and system partitions.
Click to expand...
Click to collapse
zkn1021 said:
I got the OTA update package, can I flash it directly via recovery? I have rooted my tablet.
Click to expand...
Click to collapse
Well first unroot by flashing boot and system, then install update in Lenovo recovery. Yes it's possible to do that. Then when the update installed successfully you can root again with TWRP and SuperSU.
brothers, I skipped system verifying by editing updater-script, but the OTA still failed because signature verifying failed.
Anyone knows how to skip signature verifying?
If we can skip that, we may install ota update package manually while the device is rooted.
matshias said:
the easiest way is to restore the boot and system partition .
...
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
hi! how can i make a backup of my currently partitions (before rooting and so on) to make possible flash them back with "fastboot flash ..."?
is the command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
makes the image compatible with "fastboot flash ..." command? or i have to convert it somehow?
P.s. yes i know about restoring with command "dd if=/sdcard1/system.img of=/dev/block/bootdevice/by-name/system", but i want to have other ways to retreat
DGolovin said:
hi! how can i make a backup of my currently partitions (before rooting and so on) to make possible flash them back with "fastboot flash ..."?
is the command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
makes the image compatible with "fastboot flash ..." command? or i have to convert it somehow?
P.s. yes i know about restoring with command "dd if=/sdcard1/system.img of=/dev/block/bootdevice/by-name/system", but i want to have other ways to retreat
Click to expand...
Click to collapse
In TWRP (via adb or TWRP terminal) you can use the command that you listed to make backups of existing partitions. The system partition is a bit special though. The dd command will give you the raw partition image. Fastboot, however, expects the system partition in sparse format. To convert you need the tool "img2simg".
The other partitions are expected in raw format by fastboot.
Unless you have a special firmware version you don't have to create these backups since we have factory images which contain exactly these partition images. Boot, recovery and system partitions are the same for all devices with the same device variant and software version.
matshias said:
In TWRP (via adb or TWRP terminal) you can use the command that you listed to make backups of existing partitions. The system partition is a bit special though. The dd command will give you the raw partition image. Fastboot, however, expects the system partition in sparse format. To convert you need the tool "img2simg".
The other partitions are expected in raw format by fastboot.
Unless you have a special firmware version you don't have to create these backups since we have factory images which contain exactly these partition images. Boot, recovery and system partitions are the same for all devices with the same device variant and software version.
Click to expand...
Click to collapse
Thanks for eхplain. I have downloaded your backups of 734th firmware for Lenovo Yoga 3 Plus F already but new knowlege will not be redundant
Hello,
Tried "adb reboot bootloader" but it only stuck with Lenovo logo. So I tried to flash boot.img using app.
Now stuck with boot loop. Manage to go into Recovery Mode - Is there any way I could restore anything from Recovery? .zip
Thank you
Hi guys,
I got n OTA update. I only did the root process from https://forum.xda-developers.com/th...ta-twrp-root-disable-encryption-yoga-t3538017 before.
After doing the "fastboot flash boot boot.img" to allow the OTA update from this thread, I got a reboot loop (soft brick right?) when I try to go to recovery, i got this
https://photos.google.com/share/AF1QipMLfvQnTcKCr4lJ6ImnPHsb9_s5aR_ERj_k_oIuhhg_k6aGD2yNen8H9y7tdhPLOA?key=T2FYdmZSZ204OFczejB0dXpGOGlRdG1aNXBvckln
any help? sadly, I'm a noob u.u
thxs
NtahX said:
Hello,
Tried "adb reboot bootloader" but it only stuck with Lenovo logo. So I tried to flash boot.img using app.
Now stuck with boot loop. Manage to go into Recovery Mode - Is there any way I could restore anything from Recovery? .zip
Thank you
Click to expand...
Click to collapse
The fastboot mode (bootloader) only shows the Lenovo logo. So this is expected. If you get a bootloop you also have to flash system.img via fastboot. So do the adb reboot bootloader again and use fastboot tool on the PC to do the flashing
---------- Post added at 10:51 PM ---------- Previous post was at 10:47 PM ----------
dasinflames said:
Hi guys,
I got n OTA update. I only did the root process from https://forum.xda-developers.com/th...ta-twrp-root-disable-encryption-yoga-t3538017 before.
After doing the "fastboot flash boot boot.img" to allow the OTA update from this thread, I got a reboot loop (soft brick right?) when I try to go to recovery, i got this
https://photos.google.com/share/AF1QipMLfvQnTcKCr4lJ6ImnPHsb9_s5aR_ERj_k_oIuhhg_k6aGD2yNen8H9y7tdhPLOA?key=T2FYdmZSZ204OFczejB0dXpGOGlRdG1aNXBvckln
any help? sadly, I'm a noob u.u
thxs
Click to expand...
Click to collapse
Same thing. Your system partition is not original that's why you have the boot loop. You have to flash the original version via fastboot.
matshias said:
The fastboot mode (bootloader) only shows the Lenovo logo. So this is expected. If you get a bootloop you also have to flash system.img via fastboot. So do the adb reboot bootloader again and use fastboot tool on the PC to do the flashing
---------- Post added at 10:51 PM ---------- Previous post was at 10:47 PM ----------
Same thing. Your system partition is not original that's why you have the boot loop. You have to flash the original version via fastboot.
Click to expand...
Click to collapse
Code:
c:\adb>fastboot flash system system_yt_x703f_s000734.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.626s]
sending sparse 'system' (516880 KB)...
OKAY [ 18.443s]
writing 'system'...
OKAY [ 7.726s]
sending sparse 'system' (507198 KB)...
OKAY [ 18.163s]
writing 'system'...
OKAY [ 7.812s]
sending sparse 'system' (511833 KB)...
OKAY [ 18.332s]
writing 'system'...
OKAY [ 7.876s]
sending sparse 'system' (514911 KB)...
OKAY [ 18.410s]
writing 'system'...
OKAY [ 7.345s]
sending sparse 'system' (514937 KB)...
OKAY [ 18.282s]
writing 'system'...
OKAY [ 7.369s]
sending sparse 'system' (511997 KB)...
OKAY [ 18.328s]
writing 'system'...
OKAY [ 22.033s]
sending sparse 'system' (156572 KB)...
OKAY [ 5.703s]
writing 'system'...
OKAY [ 17.717s]
finished. total time: 194.195s
c:\adb>fastboot flash recovery recovery_yt_x703f_s000734.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.078s]
writing 'recovery'...
OKAY [ 0.829s]
finished. total time: 2.907s
Since I already flashed boot.img yesterday, continue with system & recovery. I didn't know that Download mode will only shows Lenovo logo. Normally it will shows what running on the background. Did as told and manage to recover. Sadly I've wiped cache & data in Recovery yesterday, now back to square 1. But at least better than bricked device. Thank you.
matshias said:
The fastboot mode (bootloader) only shows the Lenovo logo. So this is expected. If you get a bootloop you also have to flash system.img via fastboot. So do the adb reboot bootloader again and use fastboot tool on the PC to do the flashing
---------- Post added at 10:51 PM ---------- Previous post was at 10:47 PM ----------
Same thing. Your system partition is not original that's why you have the boot loop. You have to flash the original version via fastboot.
Click to expand...
Click to collapse
the only way that my tablet can to be recognized in my computer is with sideload. I'll try with that method.
thxs!!
PS: I used at the end the Multiflashtool and now my tablet works perfectly
if someone has the parallel problem, here is the solution: http://www.mediafire.com/download/58upc51o93ux2f4/Archivo+StargetDawn.rar
just install and execute the multiflash program.
greetings
matshias said:
So the easiest way is to restore the boot and system partition to the original S000725 version using fastboot and then install the update, but only if you are on S000725 now. If you are sure that you didn't modify the system partition (any root app installed system less) then the boot partition is sufficient. Flashing these two partitions will not delete your apps and settings.
Here is what to do:
Download the factory image S000725 for your tablet (see first post of TWRP thread) and make sure your current software version is S000725
Extract it and get the boot.img and system.img files
restart into fastboot mode (e.g. via adb reboot bootloader, or restart the tablet with volume up key pressed)
Execute fastboot on your PC connected to the tablet with the following command:
Code:
fastboot flash boot boot.img
If the system partition was modified you will have to do the same for system
Code:
fastboot flash system system.img
If TWRP is flashed you also have to restore the recovery partition
Code:
fastboot flash recovery recovery.img
You can also install the factory image via the supplied flash tool. But we're not 100% sure it is safe wrt. DRM keys
Sometimes the flashing of such large partitions as the system partitions can fail in which case you have to do it again until it works. If you run into a bootloop after flashing the boot.img your system partition is not original and you have to flash the system.img again
EDIT: Ok I see you are on S000691 in which case you need a factory image of that version
Click to expand...
Click to collapse
I'm sorry to bother you again.
Someone made a backup via twrp, and got these files:
boot.emmc.win
boot.emmc.win.md5
recovery.log
system.ext4.win000
system.ext4.win000.md5
system.ex4.win001
system.ext4.win001.md5
system.info
How to continue with these files?
Thank you!
zkn1021 said:
I'm sorry to bother you again.
Someone made a backup via twrp, and got these files:
boot.emmc.win
boot.emmc.win.md5
recovery.log
system.ext4.win000
system.ext4.win000.md5
system.ex4.win001
system.ext4.win001.md5
system.info
How to continue with these files?
Thank you!
Click to expand...
Click to collapse
Well it seems you have to request the backup again. system.ext4 is a file based backup. This will not restore to a 100% original system image. The person who provided this for you has to run it again and select "system image" instead of "system" when creating the backup. This will then be a binary copy of the system partition.
Once you have that you should create a backup using TWRP on your own device with boot and system image selected onto an external SD card. Don't forget to boot TWRP with system left read only. Then you replace the *.win* files (also the .md5 files) on you SD card with ones you get from this person files. Then reinsert the SD card into the tablet and select restore in TWRP. Then the two partitions should be original if the person you got them from didn't modify it somehow.
I am not sure which format TWRP uses to store these partition images but if the above doesn't work we'll figure out how to extract it.
matshias said:
Download the factory image S000725 for your tablet (see first post of TWRP thread) and make sure your current software version is S000725
EDIT: Ok I see you are on S000691 in which case you need a factory image of that version
Click to expand...
Click to collapse
hello iam on s000689 and i have a hard time trying to find that recovery image... can i just you S000725 and then not have OTA updates?
I seem to have an issue that appears frequently, yet I cant find an answer.
This is a fix to Remote: FileWriteFailed
So, I was trying to reflash stock again for multirom and it fails. It can erase everything yet cannot flash anything. Basically:
Writing 'bootloader' (remote: (FileWriteFailed))
It shows up Signature Match, so I decided to continue
It sends boot, boot flashes
Anything else, I get the same Remote FileWriteFailed.
I thought that my partitions killed themselves again, so I tried flashing TWRP
Fails with same error.
I looked and found I can just boot it. So I tried and get this:
Command: fastboot boot twrp.img
downloading boot.img...
FAILED (command write failed (No error)
Restarted bootloader to try again
Recovery flashed. Im feeling confident
I go and try to update via update image
Flash bootloader OKAY
Command: fastboot update -w image-nakasi-ktu84p.zip
Archive doesnt contain *.sig
Checks everything, makes partitions
Everythings okay
Fix is (if you have sdk already)
So, basically, you have to erase System, cache, userdata, boot and recovery with fastboot erase.
Then find your factory image from google and download it
Extract everything and move the image-nakasi-*****.zip and bootloader.img to your sdk folder
Flash bootloader
Use command: fastboot update -w image-nakasi-*****.zip
Wait
Today after a successful OTA manual upgrade(downloaded latest zip and flashed) I decided to reinstall TWRP in order to reroot. However, after running first "fastboot flash recovery twrp.zip" then "fastboot boot twrp.zip", I am no longer prompted to enter my passcode(which I know) to decrypt the device, and the /system partition is empty in the TWRP file manager. The sdcard partition is filled with my encrypted files(assuming by their base64 names).
I dont think any of my actions in TWRP were significant, except possibly when I flashed the twrp.zip to have the recovery be persistent. (When I launched TWRP for the first time, I wasn't prompted for my password to decrypt then either, so I assume the damage was already done)
I have tried "twrp decrypt [password]" in the twrp terminal but I get "Failed to decrypt data"
A. Is there a way to reflash my system(e.g Can I just flash the same update.zip) and be back to normal
Or B. Can I retrieve and decrypt my data, given that I know my lockscreen passcode which is normally used to decrypt it.
Here is everything I wrote in my command prompt(Can't post links):
E:\Coding\OnePlus>fastboot
-snip fastboot help-
E:\Coding\OnePlus>fastboot flash recovery twrp-installer-fajita-3.2.3-2.zip
target reported max download size of 536870912 bytes
sending 'recovery' (16693 KB)...
OKAY [ 0.359s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.364s
E:\Coding\OnePlus>fastboot boot twrp-installer-fajita-3.2.3-2.zip
creating boot image...
creating boot image - 17096704 bytes
downloading 'boot.img'...
OKAY [ 0.361s]
booting...
OKAY [ 0.092s]
finished. total time: 0.455s
E:\Coding\OnePlus>fastboot devices
d535eae7 fastboot
E:\Coding\OnePlus>fastboot boot twrp-installer-fajita-3.2.3-2.zip
creating boot image...
creating boot image - 17096704 bytes
downloading 'boot.img'...
OKAY [ 0.361s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.456s
E:\Coding\OnePlus>fastboot flash recovery twrp-installer-fajita-3.2.3-2.zip
< waiting for device >
^C
E:\Coding\OnePlus>fastboot devices
E:\Coding\OnePlus>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
d535eae7 recovery
E:\Coding\OnePlus>adb flash
-snip adb help-
E:\Coding\OnePlus>adb push twrp-installer-fajita-3.2.3-2.zip /data
7500 KB/s (17094317 bytes in 2.225s)
E:\Coding\OnePlus>
Click to expand...
Click to collapse
As you learned from the first command there is no recovery partition, you can't flash like that. Your data is on a different partition, so it should be ok (pictures and such, I'm assuming that's what you are worried about)
Next I don't know what ROM or OS you are using, but if it's a current one, you will need a newer version of TWRP. Download 3.3.1-6 or 3.3.1-7 from this thread (link) You need the IMG file first. Run:
fastboot boot twrp-3.3.1-6-fajita.img (Or -7 if you download -7)
Hopefully that will ask you for your password and decrypt all your data. At this point backup your data. Then I would dirty flash your ROM as it's hard to say what you did with all that flashing up above. Then run the TWRP installer. Then Reboot to recovery, flash magisk (If this was a custom ROM, remeber to also re-flash Gapps). Just like you were doing a regular update. Hopefully that fixes everything.
jonesbeverly44 said:
Today after a successful OTA manual upgrade(downloaded latest zip and flashed) I decided to reinstall TWRP in order to reroot. However, after running first "fastboot flash recovery twrp.zip" then "fastboot boot twrp.zip", I am no longer prompted to enter my passcode(which I know) to decrypt the device, and the /system partition is empty in the TWRP file manager. The sdcard partition is filled with my encrypted files(assuming by their base64 names).
I dont think any of my actions in TWRP were significant, except possibly when I flashed the twrp.zip to have the recovery be persistent. (When I launched TWRP for the first time, I wasn't prompted for my password to decrypt then either, so I assume the damage was already done)
I have tried "twrp decrypt [password]" in the twrp terminal but I get "Failed to decrypt data"
A. Is there a way to reflash my system(e.g Can I just flash the same update.zip) and be back to normal
Or B. Can I retrieve and decrypt my data, given that I know my lockscreen passcode which is normally used to decrypt it.
Here is everything I wrote in my command prompt(Can't post links):
Click to expand...
Click to collapse
Hello my friend. Did you ever find a solution to get your directory back? Mine looks like you explained now in TWRP and in a file manager. Like it was encrypted or something.
boobteg2 said:
Hello my friend. Did you ever find a solution to get your directory back? Mine looks like you explained now in TWRP and in a file manager. Like it was encrypted or something.
Click to expand...
Click to collapse
Fastboot the .IMG file not the .zip file, if it is encrypted then adb sideload or boot to system then fastboot again.
I am no longer prompted to enter my passcode(which I know) to decrypt the device, and the /system partition is empty in the TWRP file manager. The sdcard partition is filled with my encrypted files(assuming by their base64 names).
Click to expand...
Click to collapse
OnePlus uses FBE (File Based Encryption) which is why it looks like this. Just booting TWRP doesn't affect your data. As long as you're able to restore a working system partition and let phone boot your data should be accessible, but _only_ once phone fully boots.
Hello, I tried to upgrade to official LOS, so I upgraded firmware using twrp and then I installed new LOS 18.1, however I didn't make any partition clean, so I stuck with bootloop can't boot into lineage os.
I can't boot into TWRP too, it seems to freeze on TWRP splash screen.
I tried to flash another recovery using fastboot. I boot successfully into fastboot, however when I enter flash command from my PC it freezes, when I ran fastboot flash with verbose, I got:
Code:
fastboot: verbose: target didn't report max-download-size
Have you idea what should I do?
I'd mention that before my TWRP sideload worked only after `adb reboot sideload` and I couldn't sideload package using TWRP gui "adb sideload".
Update: I tried connect to different usb port and I got:
Code:
$ sudo ./platform-tools_r29.0.1-linux/platform-tools/fastboot flash recovery --verbose asus/lineage-18.1-20210518-recovery-X00TD.img
fastboot: verbose: target reported max download size of 536870912 bytes
Sending 'recovery' (21157 KB)
and then phone freezed (I still have twrp splash screen)
Update 2: I discovered, I can run `adb shell` command in the twrp splash screen (however I can't i.e. run wipe command)
Finally erase cache and userdata worked but I still have bootloop. TWRP GUI works however I have problem with Mount
Now I can flash TWRP or lineage os recovery, I tried TWRP Kud however still error on wipe same AS in attarched screen.