Getting frustrated with the likes of:
$ fastboot flash tombstones tombstones.img.ext4
sending 'tombstones' (114688 KB)...
OKAY [ 28.674s]
writing 'tombstones'...
FAILED (remote: size too large)
finished. total time: 28.679s
I was wondering if in all failed attempts to manually make space for such using:
$ fastboot erase system/cache/data/etc.,
I wouldn't be better off doing a:
$ fastboot oem format ?!?
Your mediapad bricked now.
You need linux-pc & try to use "dd" command for restore all partitions of your pad.
This is a general users guide to unbrick your Transformer tablet.
This guide will help you if your Asus tablet will only boot into recovery
and the command
Code:
adb reboot-bootloader
does not work to get you booted back to bootloader screen ..
If the above command works then skip to the first fastboot command ..
WHAT YOU NEED
An Asus tablet that will only boot into recovery …
Woking adb and fastboot on your PC
Windows drivers (if using Windows)
A fully charged tablet
Asus data cable
Stock firmware blob (from Asus's web site, make sure you get the right one)
_that's bootit.ko (unzipped and placed with fastboot.exe)
Downloads
Asus Stock firmware---MAKE SURE YOU GET THE CORRECT SKU FOR YOUR TRANSFORMER TABLET
click me
_that's bootit.ko----click me
INSTRUCTIONS
Extract your stock firmware in your downloads folder twice...You will see a blob file rename it boot.blob and move it to the same folder as your fastboot.exe or if in linux to your home folder
Unzip the bootit.ko and place it wth the above blob file.
Let start with this command to make sure that your PC can see your table as an ADB device in recovery
Code:
adb devices
OUTPUT
Code:
[email protected] ~ $ adb devices
List of devices attached
015c7d7a445c260c recovery
Then lets push the bootit.ko to the root of the device like this
Code:
adb push bootit.ko /
OUTPUT
Code:
[email protected] ~ $ adb push bootit.ko /
673 KB/s (27690 bytes in 0.040s)
Then lets insmod this .ko file
Code:
adb shell insmod /bootit.ko
This should reboot the tablet into the bootloader menu, lets verifiy.
Once in the bootloader screen lets make sure your PC can see the device in fastboot.
Code:
fastboot devices
OUTPUT
Code:
[email protected] ~ $ fastboot devices
015c7d7a445c260c fastboot
So now its time to erase the misc & cache partitions, as that is most likely the partitions that is making it boot to recovery...
Code:
fastboot erase misc
OUTPUT
Code:
[email protected] ~ $ fastboot erase misc
erasing 'misc'...
OKAY [ 1.021s]
finished. total time: 1.021s
Code:
fastboot erase cache
OUTPUT
Code:
[email protected] ~ $ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.096s]
finished. total time: 2.096s
Once these two command run with OKAY as the OUTPUT .
It is time to make sure we can reboot into the bootloader with the hardware buttons
So from where you are at in the bootloader screen use the VOL DOWN & POWER buttons to boot the tab back into the bootloader screen ..
Run these command in fastboot in this order
The next command is to just verify your computer can see your device
Code:
fastboot devices
OUTPUT
Code:
[email protected]:~ > fastboot devices
015d2bbce2501405 fastboot
Code:
fastboot erase system
OUTPUT
Code:
[email protected]:~ > fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.954s]
finished. total time: 2.954s
Code:
fastboot erase recovery
OUTPUT
Code:
[email protected]:~ > fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.945s]
finished. total time: 1.945s
Code:
fastboot -w
OUTPUT
Code:
[email protected]:~ > fastboot -w
erasing 'userdata'...
OKAY [ 23.188s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29618601984
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7231104
Block groups: 221
Reserved block group size: 1024
Created filesystem with 11/1810432 inodes and 157662/7231104 blocks
sending 'userdata' (139133 KB)...
writing 'userdata'...
OKAY [ 26.358s]
erasing 'cache'...
At this point it will either hangs on erasing 'cache'
Or it will give you an error, either way you will need to
reboot the tablet back into fastboot with the hardware buttons
Once that is done continue on the path
Code:
fastboot erase boot
OUTPUT
Code:
[email protected]:~ > fastboot erase boot
erasing 'boot'...
OKAY [ 1.209s]
finished. total time: 1.209s
Code:
fastboot erase misc
OUTPUT
Code:
[email protected]:~ > fastboot erase misc
erasing 'misc'...
OKAY [ 0.978s]
finished. total time: 0.978s
Code:
fastboot erase cache
OUTPUT
Code:
[email protected]:~ > fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.843s]
finished. total time: 2.843s
Code:
fastboot -i 0x0B05 flash system boot.blob
During the sending/writing process of this step you will get the blue bar on your screen.....
OUTPUT
Code:
[email protected]:~ > fastboot -i 0x0B05 flash system boot.blob
erasing 'system'...
OKAY [ 2.339s]
sending 'system' (800927 KB)...
OKAY [133.094s]
writing 'system'...
[OKAY [178.036s]
finished. total time: 313.469s
Code:
fastboot -i 0x0B05 reboot
OUTPUT
Code:
[email protected]:~ > fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.020s
Let it boot into stock ROM ....
Credits
@_that for his bootit.ko
TEAM CROMBi and TEAM ZOMBi-X @sbdags @hardslog
Troubleshooting
Here is some troubleshooting
Check out this thread for fasboot.exe, adb.exe and driver help ...CLICK ME
A message from _that
_that said:
Here is the original thread where the bootit module was tested for the first time -> http://forum.xda-developers.com/showthread.php?t=2291974
The problem was that the installed recovery was too old and incompatible with the bootloader and so could not access the eMMC at all. The bootloader command to boot to recovery is stored in the MSC partition (mmcblk0p3), and the recovery could not clear it. Since the bootloader checks the MSC partition before checking for volume-down, it is impossible to get to fastboot without some additional kick in the butt (aka "bootit.ko").
The correct bootit.ko file to use is the one in "bootit-bootloader.zip": http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132 - the older version turned out to be too weak. Note that this is a zipped kernel module, not a recovery-installable ZIP. You need to unzip it on your PC before adb push.
After making it to the bootloader menu and working fastboot, you can fastboot flash a current version of TWRP and install the custom ROM of your choice. No real need for the stock blob, unless you want to make sure you have the current bootloader and a known working ROM.
Here is another thread where bootit.ko didn't help, maybe it was really a hardware problem. But lots of good background info from me. -> http://forum.xda-developers.com/showthread.php?t=2437376
And here is another success story -> http://forum.xda-developers.com/showthread.php?p=47525770
Click to expand...
Click to collapse
Thx for all your help @_that
My model is XT1710-09 of Tim Italia with single sim, but it has also been tested in a dual sim model.
This tutorial explains how to get back from LineageOS to stock firmware without losing the IMEI. You should always make a copy of the IMEI in TWPR.
How does it work:
You have to be in a modified rom.
1- You have to download this firmware with the February 2018 patch: https://androidfilehost.com/?fid=962187416754466195
2- Install adb minimal fastboot: https://forum.xda-developers.com/sho....php?t=2317790
3- After installing adb minimal fastboot, go to the location of the ADB installation and paste all the files extracted from the downloaded firmware there.
4- Copy all the commands of this thread in the cmd window, press enter and wait.
Commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash boot boot.img
fastboot oem lock
These are the results that I have obtained
For US variant XT1710-01 https://forum.xda-developers.com/showpost.php?p=76192627&postcount=18
That way is way i used to return to stockOS on another devices
I just followed the steps above on my XT1710-01 unlocked US Retail and it appears to have worked. I got the normal blue/red splash screen and I have data/IMEI. I booted into bootloader and oem_locked + software status: official is there Thanks brother!
julesism said:
I just followed the steps above on my XT1710-01 unlocked US Retail and it appears to have worked. I got the normal blue/red splash screen and I have data/IMEI. I booted into bootloader and oem_locked + software status: official is there Thanks brother!
Click to expand...
Click to collapse
What I'm anxious to know is if the phone will get the OTA´s
julesism said:
I just followed the steps above on my XT1710-01 unlocked US Retail and it appears to have worked. I got the normal blue/red splash screen and I have data/IMEI. I booted into bootloader and oem_locked + software status: official is there Thanks brother!
Click to expand...
Click to collapse
I was going to try this on my XT1710-01 (Canada retail) on the weekend. Thanks for confirming!
While this get me back to the stock Moto ROM, it did not lock my bootloader.
Got the dreaded "Image signed with key bad key" message during various times during using the fastboot commands and my bootloader remains unlocked.
XT1710-01 (Canada Retail)
I think you should try it again I went thru the process posted in another thread by rajatgupta1998 and ended up exactly where you are now. I manually flashed a modified boot.img via adb to get the blue/red splash screen back although some text was still visible including bad key message.
When this topic was created, I decided to give it one more try. I had so may files unzipped from previous zips/flashes etc., I decided to make a clean adb folder with nothing but this zip/files extracted in it. Low and behold, it worked for me. I believe once, maybe twice the process stopped and I had to manually copy/paste the next command. Maybe something was missed.
Here's hoping this fixes my NFC issue
TravellingGuy said:
While this get me back to the stock Moto ROM, it did not lock my bootloader.
Got the dreaded "Image signed with key bad key" message during various times during using the fastboot commands and my bootloader remains unlocked.
XT1710-01 (Canada Retail)
Click to expand...
Click to collapse
This happened to me because I did not install the latest firmware. It is because the bootloader is more recent than the firmware you are trying to install. When putting the firmware of February 2018 I have been able to close the bootloader three times, after returning several times to lineageOS.
julesism said:
I think you should try it again I went thru the process posted in another thread by rajatgupta1998 and ended up exactly where you are now. I manually flashed a modified boot.img via adb to get the blue/red splash screen back although some text was still visible including bad key message.
When this topic was created, I decided to give it one more try. I had so may files unzipped from previous zips/flashes etc., I decided to make a clean adb folder with nothing but this zip/files extracted in it. Low and behold, it worked for me. I believe once, maybe twice the process stopped and I had to manually copy/paste the next command. Maybe something was missed.
Click to expand...
Click to collapse
I actually did try it twice that evening and the same thing happened both times. That was also from a fresh folder.
Kacike27 said:
This happened to me because I did not install the latest firmware. It is because the bootloader is more recent than the firmware you are trying to install. When putting the firmware of February 2018 I have been able to close the bootloader three times, after returning several times to lineageOS.
Click to expand...
Click to collapse
So, I was on LineageOS when I followed your process. Your process includes steps to flash the bootloader and the firmware, which *should* mean the bootloader is the same version as the corresponding firmware (i.e. I didn't skip in any steps in the process that may have allowed a more recent bootloader to remain on my device).
I see from this post (a different, older device, but could very still be relevant), (s)he says
"Make sure you have a fastboot flashable official stock image signed to work with your carrier and region before re-locking the bootloader. Currently running the official firmware is not enough."
Click to expand...
Click to collapse
I wonder if it's also dependent on carrier and/or region. I'm in Canada, maybe there is a slightly modified bootlader for us Canucks or a different bootloader depending on the carrier or purchase location.
Use mfastboot to flash the files instead of fastboot ...check google for difference
I found many ROM for our Albus here:
https://firmware.center/firmware/Motorola/Moto Z2 Play/Stock/
But can't classify them.
My albus is XT 1710-09 in VietNam, so which file is of mine ?
Can you block the bootloader but it did not get Official in the part software status, was Modified got how to make official again?
HeltonMax said:
Can you block the bootloader but it did not get Official in the part software status, was Modified got how to make official again?
Click to expand...
Click to collapse
In my case, software status shows Official with bootloader unlocked.
method in this thread doesn't help me relock bootloader. I think I flash not correct fw for my local. But I cant find anywhere
Working very well in XT710-06 thanks bro.
Working fine on xt-710-07 also (Brazilian unlocked).
The only bug is the NFC is gone. Anyone has a workaround for this?
ogabriel said:
Working fine on xt-710-07 also (Brazilian unlocked).
The only bug is the NFC is gone. Anyone has a workaround for this?
Click to expand...
Click to collapse
I just experienced this after returning to stock from LineageOS, and there was no way I was going to settle for it.
I followed the instructions only omitting the lock and reboot commands.
Flashed TWRP, (twice to be sure), rebooted into recovery, then restored my EFS, Data, and logo. (I think 'Data' is optional, I just didn't want to start over), NFC now works fine again.
I think you always need to restore your EFS.
However, the first time I tried just restoring EFS, after boot/setup, and that didn't work. so I think you have to do it prior to boot.
i imagine you could follow instructions completely, immediately booting into bootloader then use TWRP "Boot" instead of "flash", if your end game is to relock bootloader.
I successfully locked my US variant using following method
Hello,
I can confirm that using following sequence I was able to successfully lock my US variant without loosing IMEI (EFS Partition)
Here is the Stock file I used:
Retail US Stock (ALBUS_C) (ALBUS_NA_CUST) XT1710-01
https://androidfilehost.com/?fid=890129502657596522
Those on Retail channel can perhaps use following stock file
Retail Stock (ALBUS)
https://androidfilehost.com/?fid=890129502657596046
I used mfastbootv2 for my bootloader locking (Google it, easy to find)
Here is the sequence I followed:
Phase-1 (Factory Flashing)
======
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot flash dsp adspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash oem oem.img
mfastboot erase cache
mfastboot erase userdata
mfastboot erase carrier
mfastboot erase DDR
mfastboot reboot
<<Please note mfastboot erase modemst1 and mfastboot erase modemst2 commands are not being used in the above sequence>>
After reboot I wanted my phone to fully bootup upto "Welcome" screen to ensure I've LTE connectivity with my cellular provider and my IMEI is intact
Once verified, I rebooted the phone into the bootloader,
-While your phone is completely switched off, Hold <Power + Vol Down> button for few seconds to boot phone into the bootloader
Phase-2 (OEM Bootloader Locking)
======
mfastboot oem lock
mfastboot oem lock
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash boot boot.img
mfastboot oem lock
Following is the final message I got
mfastboot oem lock
...
(bootloader) Lock complete! Flash signed images after reboot if needed
OKAY [ 0.148s]
finished. total time: 0.152s
My phone automatically rebooted once the above sequence was completed
Give it a try at your risk - Best of Luck!!
sevenstar75 said:
Hello,
I can confirm that using following sequence I was able to successfully lock my US variant without loosing IMEI (EFS Partition)
Here is the Stock file I used:
Retail US Stock (ALBUS_C) (ALBUS_NA_CUST) XT1710-01
https://androidfilehost.com/?fid=890129502657596522
Those on Retail channel can perhaps use following stock file
Retail Stock (ALBUS)
https://androidfilehost.com/?fid=890129502657596046
I used mfastbootv2 for my bootloader locking (Google it, easy to find)
<...snip...>
Following is the final message I got
mfastboot oem lock
...
(bootloader) Lock complete! Flash signed images after reboot if needed
OKAY [ 0.148s]
finished. total time: 0.152s
My phone automatically rebooted once the above sequence was completed
Give it a try at your risk - Best of Luck!!
Click to expand...
Click to collapse
I really do appreciate all you guys out there posting your steps to get back to stock and lock the bootloader.
I've literally tried every possible combination of fastboot, mfastboot, mfastbootv2, and all the different variants of ROMs posted. Haha, but it *always* fails for me.
Two things I notice, and I'm not sure if you guys see these or not.
One is that I always "get the (bootloader) Image signed with key bad key" message when I try to flash the boot.img. I'm not sure if that's something you guys get as well?
The other thing is I always see the "(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer" message when I run the lock command. @sevenstar75, I notice in your final oem lock command, you don't see this. This makes me think that this is what is different for me. In my developer settings, the OEM Lock toggle is disabled, with a message to the effect of "Bootloader is already unlocked", and I can't change the toggle. This makes sense, as my bootloader IS unlocked, but why don't you see/get that message as well, I wonder?
Here is some sample output of what I'm doing and seeing:
Code:
fastboot oem lock
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.002s]
finished. total time: 0.002s
fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.002s]
finished. total time: 0.002s
fastboot flash oem oem.img
target max-sparse-size: 256MB
sending 'oem' (232923 KB)...
OKAY [ 6.020s]
writing 'oem'...
OKAY [ 3.161s]
finished. total time: 9.181s
fastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (262142 KB)...
OKAY [ 6.856s]
writing 'system'...
OKAY [ 4.225s]
sending sparse 'system' (259055 KB)...
OKAY [ 6.732s]
writing 'system'...
OKAY [ 3.632s]
finished. total time: 21.444s
fastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (245604 KB)...
OKAY [ 6.441s]
writing 'system'...
OKAY [ 3.479s]
sending sparse 'system' (240099 KB)...
OKAY [ 6.273s]
writing 'system'...
OKAY [ 3.105s]
sending sparse 'system' (30320 KB)...
OKAY [ 0.800s]
writing 'system'...
OKAY [ 0.414s]
finished. total time: 20.512s
fastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (255375 KB)...
OKAY [ 6.686s]
writing 'system'...
OKAY [ 3.752s]
sending sparse 'system' (258527 KB)...
OKAY [ 6.836s]
writing 'system'...
OKAY [ 4.416s]
finished. total time: 21.690s
fastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (262140 KB)...
OKAY [ 7.145s]
writing 'system'...
OKAY [ 3.449s]
sending sparse 'system' (258973 KB)...
OKAY [ 6.839s]
writing 'system'...
OKAY [ 3.405s]
finished. total time: 20.838s
fastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (261624 KB)...
OKAY [ 6.844s]
writing 'system'...
OKAY [ 3.589s]
sending sparse 'system' (258473 KB)...
OKAY [ 7.094s]
writing 'system'...
OKAY [ 3.587s]
finished. total time: 21.113s
fastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (253898 KB)...
OKAY [ 6.661s]
writing 'system'...
OKAY [ 3.451s]
sending sparse 'system' (262134 KB)...
OKAY [ 6.944s]
writing 'system'...
OKAY [ 4.081s]
sending sparse 'system' (8244 KB)...
OKAY [ 0.231s]
writing 'system'...
OKAY [ 0.160s]
finished. total time: 21.527s
fastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (252681 KB)...
OKAY [ 6.432s]
writing 'system'...
OKAY [ 3.292s]
finished. total time: 9.725s
fastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.448s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.458s]
finished. total time: 0.906s
fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.002s]
finished. total time: 0.002s
Hi,
1) What is your variant? I mean XT1710-?? Is that RetUS software channel?
2) Did you toggle Allow OEM Unlocking to "ON" before unlocking your phone?
3) While that toggle currently grayed out, is the toggle - ON or OFF?
As the title said, i'm having some errors while i try to flash something in fastboot, i'm folowing this steps:
First i open CMD (with administrator rights) or Terminal (root mode) and Type this:
Code:
adb devices
adb reboot-bootloader
My device reboot into bootloader, then i use:
Code:
Fastboot devices
Fastboot flash [partition] [path to file]
In this case: Fastboot flash recovery recovery.img
And here is where the problems begins
Code:
Fastboot flash recovery (path to the recovery.img file)
Sending 'recovery' (42834 KB) Failed (remote: 'not support "-u" option')
Fastboot: error: command failed
I do a little research about "-u" and got something about erasing a overwriting stuff so...
Code:
Fastboot erase recovery
(Everything is ok)
Fastboot flash recovery (path to the recovery file)
Sending 'recovery' (42834 KB) OKAY
Writing 'recovery' FAILED (remote: 'write partition:recovery')
Fastboot: error: Command Failed
I can't even do a Fastboot boot because of the '-U' option error...
I've tried with RKtools (because of my rk3368h chipset) and there i can flash everything succesfuly but when i try enter in recovery mode my device get stuck in the initial boot image (not the CR boot image)
So, i don't know if i'm using a wrong recovery.img or if my device is the problem. I hope someone can help me :laugh:
P.D: My device is a generic (unpopular) Android, so the only useful info that can i bring you is:
Android version is 8.1 (November 2018 security patch)
Device uses a rk3368h chipset
Bootloader is Unlocked
Obviously isn't rooted (that's why i'm trying to flash a CR)
Similar device: Teclast P10 (probably the m3f5)
And i'm trying to flash a ported TWRP (ported by ME )
That's all, thank you for reading my post and trying to help me.
I tried to install TWRP
fastboot flash a twrp.img
Sending 'a' (39892 KB) OKAY [ 0.929s]
Writing 'a' FAILED (remote: '(a_a) No such partition')
fastboot: error: Command failed
astboot -w
Erase successful, but not automatically formatting.
File system type f2fs not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 1.057s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 1.063s
The phone is stuck in fastboot.
I tried this:
c:\TWRP>fastboot flash boot_b twrp.img
target reported max download size of 804261888 bytes
sending 'boot_b' (39892 KB)...
OKAY [ 0.931s]
writing 'boot_b'...
OKAY [ 0.215s]
finished. total time: 1.148s
fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
fastboot erase userdata
fastboot getvar all
fastboot erase boot
fastboot set_active b
fastboot erase boot
fastboot flash boot twrp.img
fastboot reboot
I press power Volume Up but the phone boot in Fastboot
you have flashed a bad boot image. if you are on a11 stock i dont think twrp work 100% safe. los recovery is recommended and work without problems