Develop Bugs

[Q] [HELP]I cant turn on my kindle fire.

Hello everyone, Kindle fire is my first android device(i'm noob).
I rooted it(not sure it sucess or not) and downloaded go launcher ex.apk from my computer then threw to my kindle. When I choosed to use the launcher, my device was hang. And I cant open my kindle fire until now.
How can I bring my kindle back ? please help me.
sorry for my bad english.
bict
=================================================================================================================
Now,my problem was solved. Thank you every one especally "b63" for the great advice.

a better description would be needed to help you
what exactly have you done ?
what is the status of your kf ? black/kindle fire logo/animated or not
a first shot would be to hold the power button for ~20sec till it turns off and power on again

bicture said:
Hello everyone, Kindle fire is my first android device(i'm noob).
I rooted it(not sure it sucess or not) and downloaded go launcher ex.apk from my computer then threw to my kindle. When I choosed to use the launcher, my device was hang. And I cant open my kindle fire until now.
How can I bring my kindle back ? please help me.
sorry for my bad english.
bict
Click to expand...
Click to collapse
In my first days of own the kindle I did that too XD
if you cheked the box that said use as default then you have to use KFU
(http://forum.xda-developers.com/showthread.php?t=1399889)
select option 1
1. bootmode menu
and then option 3
3. recovery
(español)
utiliza KFU v0.9.2
selecciona la opcion 1 la que dice bootmode menu
presiona enter
luego selecciona la opcion 3 recovery
presiona enter
con esto deberia de poner en modo recovery tu kf, y listo, ahora si solo la instalaste y no le diste el chequesito, presiona el boton de encendido de la kf por 15 seg y debería de funcionar bien, desinstala la aplicacion (go launcher ex)

b63 said:
a better description would be needed to help you
what exactly have you done ?
what is the status of your kf ? black/kindle fire logo/animated or not
a first shot would be to hold the power button for ~20sec till it turns off and power on again
Click to expand...
Click to collapse
Actually,that is
1.root with buritto.
2.try to go on TWRP recovery mode but not sucess(didnt see yellow fire logo) then I'm stop.
3.Try Go launcher ex.When I see it Lag for a long time,i press power off button.Then, I cant open my kindle again. *I see kindle fire logo in my display*
4.I checked on cmd that my device was connecting or not. and it was not.
Thanks for your advice I'll try the first one.

wcastillosalva said:
In my first days of own the kindle I did that too XD
if you cheked the box that said use as default then you have to use KFU
(http://forum.xda-developers.com/showthread.php?t=1399889)
select option 1
1. bootmode menu
and then option 3
3. recovery
(español)
utiliza KFU v0.9.2
selecciona la opcion 1 la que dice bootmode menu
presiona enter
luego selecciona la opcion 3 recovery
presiona enter
con esto deberia de poner en modo recovery tu kf, y listo, ahora si solo la instalaste y no le diste el chequesito, presiona el boton de encendido de la kf por 15 seg y debería de funcionar bien, desinstala la aplicacion (go launcher ex)
Click to expand...
Click to collapse
Thanks for your solution.It makes me belive must have a way to bring my kindle back.
I had done your solution.When I unlocked the sceen ,its in hanging time same as i saw in the first time.It 's a black screen, upper bar have a notification said it have unexpected error. I try to press home and back button but it didnt respond.
What I should do next.
thanks
bict

Factory reset
Sent from my HTC ThunderBolt using XDA App

RevosFTS said:
Factory reset
Sent from my HTC ThunderBolt using XDA App
Click to expand...
Click to collapse
My kindle was hang.I cant do anything on it such as press any button.
Do it have another way to command my kindle to factory reset ?

bicture said:
My kindle was hang.I cant do anything on it such as press any button.
Do it have another way to command my kindle to factory reset ?
Click to expand...
Click to collapse
yes - you could try to communicate with the kf per command line
what do you have available ? kfu or sdk ?
would recommend to download kfu - extract to c:\ and rename to something like "kfu" that it looks c:\kfu - now you can open an (elevated) command prompt
and cd to "c:\kfu\tools" - here you can issue "adb devices" - get a response ?
if yes then you are able to repair or flash a new rom
tell us about and we'll try help further ...

Did you use Kindle Fire Utility?
what said when you try the option 0 Recheck Device Status?

b63 said:
yes - you could try to communicate with the kf per command line
what do you have available ? kfu or sdk ?
would recommend to download kfu - extract to c:\ and rename to something like "kfu" that it looks c:\kfu - now you can open an (elevated) command prompt
and cd to "c:\kfu\tools" - here you can issue "adb devices" - get a response ?
if yes then you are able to repair or flash a new rom
tell us about and we'll try help further ...
Click to expand...
Click to collapse
yes,i used kindle fire utility and my status is online.I'm going to use TWRP to flash the stock rom in it.
Do you have anyway easier ?

please try to answer my questions from post #8 that i can try to help you further
there will be no easier way as flashing a new rom but please use one of the prerooted stock roms
http://forum.xda-developers.com/showthread.php?t=1451747

b63 said:
yes - you could try to communicate with the kf per command line
what do you have available ? kfu or sdk ?
would recommend to download kfu - extract to c:\ and rename to something like "kfu" that it looks c:\kfu - now you can open an (elevated) command prompt
and cd to "c:\kfu\tools" - here you can issue "adb devices" - get a response ?
if yes then you are able to repair or flash a new rom
tell us about and we'll try help further ...
Click to expand...
Click to collapse
Thank you for your advice.
Now,I did follow you and "adb devices" got response.What I should do next ?

given that you don't have fff and twrp availabe (hangs at "kindle fire" logo)
i would recommend to use the following post (i have done it today with him):
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
if your situation is an other one please tell us ...

b63 said:
given that you don't have fff and twrp availabe (hangs at "kindle fire" logo)
i would recommend to use the following post (i have done it today with him):
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
if your situation is an other one please tell us ...
Click to expand...
Click to collapse
Thanks for the solution.But I've done something wrong,I done step 4,5 before step 2,3(my confusing).
now when I used "adb devices" it said "List of devices attached 3Axxxxxxxxx device"
and when I used command in step3 it said "<waiting for the device>".
How can I solve it ?
Thx for take care a newbie like me.I'm very appreciate that.

nothing could be happened
point 4 - if you downloaded the file first ->ok
point 5 - the command could not work cause you'r still not in fastboot - right ?
just start from beginning and skip point 4 cause you allready downloaded the file
good luck !

b63 said:
nothing could be happened
point 4 - if you downloaded the file first ->ok
point 5 - the command could not work cause you'r still not in fastboot - right ?
just start from beginning and skip point 4 cause you allready downloaded the file
good luck !
Click to expand...
Click to collapse
now,I finish at 8 step.
I've seen the yellow triangle logo and computer cant find my device.
what I should do next.I dont understand a 9step "click the mount button from the recovery mode".
Where is mount button and where is the recovery mode?
Now,my computer cant connect to the device. Is that ok ?

i assume you are at the yellow triangle and your computer dont recognise the kf - right ?
now you have to update the drivers - the right one is "android adb interface"
then you can resume with point 7 - this will switch the kf to recovery mode (into twrp) - there you will see the mount button

b63 said:
i assume you are at the yellow triangle and your computer dont recognise the kf - right ?
now you have to update the drivers - the right one is "android adb interface"
then you can resume with point 7 - this will switch the kf to recovery mode (into twrp) - there you will see the mount button
Click to expand...
Click to collapse
I went to Device Manager and uninstall the old driver and try to install it again.
I did Update Driver Software>Browse My Computer for the software>Let me pick form the list > Browse >I type "C:\kfu\drivers\kindle" ... and it said "The folder you specified doesnt contain a compatible software,make sure it decided to work with 32 bit system."
I never seen this problem before. : (

would mean you selected the wrong driver file - it's android_winusb.inf

b63 said:
would mean you selected the wrong driver file - it's android_winusb.inf
Click to expand...
Click to collapse
I think I choose right file.And now, my computer see kf as "Unknown Device" in the "Universal serial Bus Controller".

Fastboot Failed (remote: Permission denied)

So, my phone is stuck in a bootloop. I'm not 100% sure how this happened, but I also can't access recovery. Every time I try, it goes to the ASUS screen, then boots back into bootloader. (this happened before I got soft bricked.) In other words, I can't use adb shell. So my only chance of unbricking is using fastboot, but it says permission is denied. Why would it tell me that?
EDIT: I got recovery working. I formatted my SD card, then injected CWM so I could reflash SuperSU.zip. Now I can get to recovery, but still not use adb shell. Storage doesn't show up on my PC via USB. When I try adb sideload, it says "error: device not found."

Water_Soup said:
So, my phone is stuck in a bootloop. I'm not 100% sure how this happened, but I also can't access recovery. Every time I try, it goes to the ASUS screen, then boots back into bootloader. (this happened before I got soft bricked.) In other words, I can't use adb shell. So my only chance of unbricking is using fastboot, but it says permission is denied. Why would it tell me that?
EDIT: I got recovery working. I formatted my SD card, then injected CWM so I could reflash SuperSU.zip. Now I can get to recovery, but still not use adb shell. Storage doesn't show up on my PC via USB. When I try adb sideload, it says "error: device not found."
Click to expand...
Click to collapse
Make sure you have the LATEST ADB drivers. Older drivers just don't seem to work...
What commands are you using in fastboot and from what firmware are you trying to flash from?
If you have the latest firmware it seems you need to flash ALL partitions to go back.
Just make sure your downloads are good and don't flash the wrong image on the wrong partition. Copy and paste can be your enemy here if you aren't careful...

ultramag69 said:
Make sure you have the LATEST ADB drivers. Older drivers just don't seem to work...
What commands are you using in fastboot and from what firmware are you trying to flash from?
If you have the latest firmware it seems you need to flash ALL partitions to go back.
Just make sure your downloads are good and don't flash the wrong image on the wrong partition. Copy and paste can be your enemy here if you aren't careful...
Click to expand...
Click to collapse
I figured it out. I flashed stock FW from a .zip. That got me out of the bootloop. As for commands not working, I found an alternate method to unlock the bootloader, and that seemed to be my problem.

Water_Soup said:
I figured it out. I flashed stock FW from a .zip. That got me out of the bootloop. As for commands not working, I found an alternate method to unlock the bootloader, and that seemed to be my problem.
Click to expand...
Click to collapse
Cool, as long as you got to your destination, the journey doesn't matter...
(and yes, I found that in a fortune cookie...)

Having the same problem, i have the
C:\adb>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14826 KB)...
How is that alternative method to unlock the bootloader?
Every time i try to go into recovery mode it doesnt open :/
OKAY [ 0.661s]
writing 'fastboot'...
FAILED (remote: Permission denied
)
finished. total time: 0.817s

Disable your lockscreen password first in setting, set to NONE
Sent from M919V Galaxy S4 via XDA Premium HD app.

Thanks!
madman604 said:
Disable your lockscreen password first in setting, set to NONE
Sent from M919V Galaxy S4 via XDA Premium HD app.
Click to expand...
Click to collapse
THAAAANKS! it works !! :laugh::fingers-crossed:

EchoeSD said:
THAAAANKS! it works !! :laugh::fingers-crossed:
Click to expand...
Click to collapse
you're welcome.
i found the solution in another obscure forum after a few days of Google-Fu.
on a sadder note. my screen gave up to the vertical line problem and Asus denied my warranty claim for being "Rooted". i unrooted, but they still know lol.
whatever tho. this phone has been nothing but problems in the 6 months i've owned it. back to Samsung whenever they ship that piece of junk back to me.

I get same message...Failed (remote: Permission denied) but the phone has bricked and I cannot get into the phone to disable the lockscreen.
Any ideas for a work around?
Also, I can access fastboot commands but not adb
and the phone will not enter into recovery on it's own.

Same issue
bricklayer67 said:
I get same message...Failed (remote: Permission denied) but the phone has bricked and I cannot get into the phone to disable the lockscreen.
Any ideas for a work around?
Also, I can access fastboot commands but not adb
and the phone will not enter into recovery on it's own.
Click to expand...
Click to collapse
Yeah, I have the same problem, so it's not just you!

who ever getting issue with remote permission denied or unable to flash via adb side load. down load raw firmware. extract it. place files in adb fastboot folder. open command windows here. and run mannual commands to install firmware

How do I get past this "permission denied" issue of fastboot ? Disabling the lockscreen surely was not the key to my problem.
I have also always allowed USB connections from the machine I am using for this fastbooting thing. Thank you!
LE: it was a matter of linux permissions . Just added +x and worked. Now I have advanced to the <Waiting for any device> error

kelogs said:
How do I get past this "permission denied" issue of fastboot ? Disabling the lockscreen surely was not the key to my problem.
I have also always allowed USB connections from the machine I am using for this fastbooting thing. Thank you!
Click to expand...
Click to collapse
multiple things you can try... unlocking bootloader if locked. flash dnx, ifwi , splash screen, boot , droidboot images. then go to recovery and factory data reset. then clear cache partition. and sideload firmware via adb

Water_Soup said:
So, my phone is stuck in a bootloop. I'm not 100% sure how this happened, but I also can't access recovery. Every time I try, it goes to the ASUS screen, then boots back into bootloader. (this happened before I got soft bricked.) In other words, I can't use adb shell. So my only chance of unbricking is using fastboot, but it says permission is denied. Why would it tell me that?
EDIT: I got recovery working. I formatted my SD card, then injected CWM so I could reflash SuperSU.zip. Now I can get to recovery, but still not use adb shell. Storage doesn't show up on my PC via USB. When I try adb sideload, it says "error: device not found."
Click to expand...
Click to collapse
Otra forma para solucionarlo en caso de que alguien mas tenga el mismo problema, es consiguiendo la imagen del TWRP, luego de esto entran en modo fastboot y escriben "fastboot boot TWRP.img", esto les servira para entrar al recovery, despues de ahi pasan la imagen del twrp a el celular, flashean la imagen en la particion de recovery y listo, no tendran problema con eso ya.

[Lenovo Tab 10 TB-X103F] Unlock Bootloader, Install TWRP, & Custom ROM GUIDE

{
"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"
}
Lenovo TAB 10 10.1" Tablet 210/1.3GHz
2GB RAM version
16GB SSD
ANDROID 6.0 (out-of-box)
I wanted to start this thread so it would be easy and fast for you all. I had to gather information from different threads elsewhere to save you guys time and headaches. Let's start!
----------------------------
DISCLAMER
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, or any problems you may/will have with your device if anything failed. Please read original thread and research if you have any concerns about ROM before flashing it! YOU are choosing to use/make these modifications, therefore, USE AT YOUR OWN RISK!!! I, myself, do not claim credit/ownership of the work, moreover, it is a collection of information made simplified and available for users. Credits goes to the creators.
-----------------------------
Original Post here
Lineage OS post here
Guide
*** Make sure Android ADB and Lenovo drivers are installed on the computer before starting ***
1. UNLOCKNG THE BOOTLOADER
a) Enable Developer Options (Systems --> About --> Tap "Build Number" 10 times)
b) Tap OEM unlock to enable it
c) Open command prompt (Admin) in the same folder as the Android ADB folder or Navigate to Android ADB folder.
d) In cmd prompt (Admin) type without quotes then hit enter: "adb reboot bootloader"
e) In cmd prompt (Admin) type without quotes then hit enter: "fastboot oem unlock" or "fastboot oem unlock-go"
f) The device will reset and reboot automatically.
g) Don't close cmd prompt and KEEP device connected to computer
2. INSTALLING TWRP (CUSTOM RECOVERY)
a) Copy the TWRP-3.0.2_TB-X103F-beta.img into the Android ADB folder
b) In cmd prompt (Admin) type without quotes then hit enter: "adb reboot bootloader"
c) In cmd prompt (Admin) type without quotes then hit enter: "fastboot flash recovery TWRP-3.0.2_TB-X103F-beta.img"
d) In cmd prompt (Admin) type without quotes then hit enter: "fastboot boot TWRP-3.0.2_TB-X103F-beta.img"
e) Wait for it to boot into TWRP
*** Tablet can now be disconnected from computer ***
3. INSTALLING LINEAGE OS WITH TWRP
a) Place files on external storage:
Rom = lineage-14.1-20171113_231156-UNOFFICIAL-x103f.zip
Gapps = open_gapps-arm-7.1-pico-20181110.zip
Root = addonsu-14.1-arm-signed.zip
b) Wipe device
c) Navigate external storage to folder that contained the files and Flash Rom, Gapps, and Root (in that order)
d) Reboot device
ENJOY!!!!!!!!

Reserved

Reserved....

Lenovo Tab 10 TB-X103F always get stuck in the bootloader
I had all the files together, went through this tutorial several times and finally wanted to flash my LENOVO. All the work just to realize that the bootloader is not working. No chance. I've tried everything. The tabet always got stuck in the bootloader. So I sent the broken tablet back. I would have liked to try it once!
kryschen

This 100% worked for me on my lenovo tb-x103f thank you!

Hey, I have a question.
Is this also for the
1GB RAM
16GB ROM version.
This question because, I see that stated the 2GB version but I really want it on my 1GB version.
Thanks in advance.

ADB-driver problem
Hello, I tried to follow this guide, but I am not able to install adb driver. I tried to use Windows driver (Win7), and also Lenovo drivers (Lenovo Driver: When I connect the tablet it is also shown as a Disk-drive. Inside that there is a Lenovo driver app). But anytime install adb-drivers failed. I also tried Clockworkmod universal drivers, but also this has not worked (maybe I did something wrong).
Because of that missing adb driver I cannot install TWRP (of course I enabled in developer options of tablet the USB debugging).
Has anybody working drivers or any idea to solve this problem?
Greetings Odiad.

none of the custom roms install on my tab,i read the install script is bad?,is this true,i get error 7 msg every time,can this be sorted?

Hey,
Two questions:
I got an issue with my camera working, can't connect to the camera and
had some zip error for this addonSu in TWRP, zip verification failure. Is this something you recognize?

Hello Good People,
I am trying to flash TWRP to my Lenovo Tab E10.
I can only complete step C
When trying to perform step D I get this message:
Booting
fastboot error: Command failed
Can someone please tell me how to resolve this?
T.I.A.

i get to step 1d and it just stays in the lenovo boot up screen (black screen with orange lenovo logo in the middle). any ideas?

Hello,i have the 1 gb ram version and i am realy new to all this
I do not have external storage so i am using internal storage for the files.SO far i have managed to install twrp 3.0.2,supersu and lineage os 14.1 but i can not istall the open gapps.
The error message is" Failed to map file(path,filename)" and "Error installing zip file (path,filename).
I tried to flash open gapps after flashing lineage and after rebooting having lineage flashed.
Any suggestions?

Hello! My name is Brandon and I'm 29. I have been studying, reading and learning (still am.) everything I possibly can about all the different possibilities that are available when it comes to electronics in general. I tried to unlock and flash my Nextbook ares 11 but I only accomplished unlocking the bootloader, So I do what I do best and kept it persistent because persistence always prevails! I searched some more and I found this thread and it just so happens there was a Lenovo tab 10 tb-x103f laying around so I gave it a shot and . . . . . . . . BOOM!! I accomplished every step and it now operates with Lineage 14.1 OS! I ran into some similar issues that are listed above but I held to and I was able to come out SUCCESSFUL! I just want to say THANK YOU soo very much for the knowledge and putting un-corrupted software on here. This is a huge accomplishment to me and I shall continue with being persistent lol

Can anyone please please make a pie update custom ROM for lenovo tab 10 tbx-103f. Many people use it and hate getting stuck at 7.1. I'll provide all information required. My tab has bootloader unlocked twrp installed and with root. If anyone wants to make a custom ROM(Any ROM) pie update for this device. I'll provide all info about this device. [Sorry if my English has some grammar mistakes.

[QUOTE = "jimpan1970, publicación: 84112321, miembro: 11341471"]
Hola, tengo la versión de 1 GB de RAM y soy realmente nuevo en todo esto
No tengo almacenamiento externo, así que estoy usando almacenamiento interno para los archivos. Hasta ahora he logrado instalar twrp 3.0.2, supersu y lineage os 14.1 pero no puedo instalar los gapps abiertos.
El mensaje de error es "No se pudo asignar el archivo (ruta, nombre de archivo)" y "Error al instalar el archivo zip (ruta, nombre de archivo).
Intenté abrir brechas abiertas después de flashear el linaje y después de reiniciar el linaje parpadeó.
¿Alguna sugerencia?
[/ CITA]
Me uno a tu pregunta...

tigeer said:
Lenovo TAB 10 10.1" Tablet 210/1.3GHz
2GB RAM version
16GB SSD
ANDROID 6.0 (out-of-box)
I wanted to start this thread so it would be easy and fast for you all. I had to gather information from different threads elsewhere to save you guys time and headaches. Let's start!
----------------------------
DISCLAMER
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, or any problems you may/will have with your device if anything failed. Please read original thread and research if you have any concerns about ROM before flashing it! YOU are choosing to use/make these modifications, therefore, USE AT YOUR OWN RISK!!! I, myself, do not claim credit/ownership of the work, moreover, it is a collection of information made simplified and available for users. Credits goes to the creators.
-----------------------------
Original Post here
Lineage OS post here
Guide
*** Make sure Android ADB and Lenovo drivers are installed on the computer before starting ***
1. UNLOCKNG THE BOOTLOADER
a) Enable Developer Options (Systems --> About --> Tap "Build Number" 10 times)
b) Tap OEM unlock to enable it
c) Open command prompt (Admin) in the same folder as the Android ADB folder or Navigate to Android ADB folder.
d) In cmd prompt (Admin) type without quotes then hit enter: "adb reboot bootloader"
e) In cmd prompt (Admin) type without quotes then hit enter: "fastboot oem unlock" or "fastboot oem unlock-go"
f) The device will reset and reboot automatically.
g) Don't close cmd prompt and KEEP device connected to computer
2. INSTALLING TWRP (CUSTOM RECOVERY)
a) Copy the TWRP-3.0.2_TB-X103F-beta.img into the Android ADB folder
b) In cmd prompt (Admin) type without quotes then hit enter: "adb reboot bootloader"
c) In cmd prompt (Admin) type without quotes then hit enter: "fastboot flash recovery TWRP-3.0.2_TB-X103F-beta.img"
d) En el indicador de cmd (Admin) escriba sin comillas y luego presione enter: "fastboot boot TWRP-3.0.2_TB-X103F-beta.img"
e) Espere a que se inicie en TWRP
*** La tableta ahora se puede desconectar de la computadora ***
3. INSTALACIÓN DEL SO LINEAGE CON TWRP
a) Coloque los archivos en un almacenamiento externo:
Rom = linaje-14.1-20171113_231156-UNOFFICIAL-x103f.zip
Gapps = open_gapps-arm-7.1-pico-20181110.zip
Raíz = addonsu-14.1-arm-signed.zip
b) Limpiar dispositivo
c) Navegue por el almacenamiento externo a la carpeta que contenía los archivos y Flash Rom, Gapps y Root (en ese orden)
d) Reiniciar el dispositivo
¡¡¡¡¡¡¡¡DISFRUTAR!!!!!!!!
[/CITA]
Click to expand...
Click to collapse

Funcionó perfecto.

thanks you so much, for, post here, works , all ok.

After flashing this ROM to TB-X103F 1gb Ram ( Wifi only ) the touch calibration completely wrong.
While in TWRP touch works normally.
e.g. the screen is vertical but the touch as if the screen is horizontal and the opposite the same.
How to solve this. I've tried most of the custom roms available all with same issue.

tigeer said:
Lenovo TAB 10 10.1" Tablet 210/1.3GHz
2GB RAM version
16GB SSD
ANDROID 6.0 (out-of-box)
I wanted to start this thread so it would be easy and fast for you all. I had to gather information from different threads elsewhere to save you guys time and headaches. Let's start!
----------------------------
DISCLAMER
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, or any problems you may/will have with your device if anything failed. Please read original thread and research if you have any concerns about ROM before flashing it! YOU are choosing to use/make these modifications, therefore, USE AT YOUR OWN RISK!!! I, myself, do not claim credit/ownership of the work, moreover, it is a collection of information made simplified and available for users. Credits goes to the creators.
-----------------------------
Original Post here
Lineage OS post here
Guide
*** Make sure Android ADB and Lenovo drivers are installed on the computer before starting ***
1. UNLOCKNG THE BOOTLOADER
a) Enable Developer Options (Systems --> About --> Tap "Build Number" 10 times)
b) Tap OEM unlock to enable it
c) Open command prompt (Admin) in the same folder as the Android ADB folder or Navigate to Android ADB folder.
d) In cmd prompt (Admin) type without quotes then hit enter: "adb reboot bootloader"
e) In cmd prompt (Admin) type without quotes then hit enter: "fastboot oem unlock" or "fastboot oem unlock-go"
f) The device will reset and reboot automatically.
g) Don't close cmd prompt and KEEP device connected to computer
2. INSTALLING TWRP (CUSTOM RECOVERY)
a) Copy the TWRP-3.0.2_TB-X103F-beta.img into the Android ADB folder
b) In cmd prompt (Admin) type without quotes then hit enter: "adb reboot bootloader"
c) In cmd prompt (Admin) type without quotes then hit enter: "fastboot flash recovery TWRP-3.0.2_TB-X103F-beta.img"
d) In cmd prompt (Admin) type without quotes then hit enter: "fastboot boot TWRP-3.0.2_TB-X103F-beta.img"
e) Wait for it to boot into TWRP
*** Tablet can now be disconnected from computer ***
3. INSTALLING LINEAGE OS WITH TWRP
a) Place files on external storage:
Rom = lineage-14.1-20171113_231156-UNOFFICIAL-x103f.zip
Gapps = open_gapps-arm-7.1-pico-20181110.zip
Root = addonsu-14.1-arm-signed.zip
b) Wipe device
c) Navigate external storage to folder that contained the files and Flash Rom, Gapps, and Root (in that order)
d) Reboot device
ENJOY!!!!!!!!
Click to expand...
Click to collapse
After 3 years this worked amazingly great...but...though I checked my hardware and it's fine...the sound is not working at all...a shame cause this tutorial is PERFECT...software clean and so on

Question Bricked device?

I tried to flash Evolution X 5.9. I came from the latest Xiaomi.eu stable (12.5.4). Followed the installing instructions (flash via twrp/ format data), but after reboot, i got a "no command" error message. I then tried to flash the original F3 EEA Fastboot Rom downloaded here: https://c.mi.com/oc/miuidownload/detail?guide=2 , unzipped it twice, but when i tried to flash the rom, i got the error message "can not find file flash_all.bat. I can only enter fastboot now. I have no idea what i did wrong. I would be grateful for any help!
Edit: I'm getting another error now: "error:Writing 'crclist'"

sycomantis said:
I tried to flash Evolution X 5.9. I came from the latest Xiaomi.eu stable (12.5.4). Followed the installing instructions (flash via twrp/ format data), but after reboot, i got a "no command" error message. I then tried to flash the original F3 EEA Fastboot Rom downloaded here: https://c.mi.com/oc/miuidownload/detail?guide=2 , unzipped it twice, but when i tried to flash the rom, i got the error message "can not find file flash_all.bat. I can only enter fastboot now. I have no idea what i did wrong. I would be grateful for any help!
Edit: I'm getting another error now: "error:Writing 'crclist'"
Click to expand...
Click to collapse
Don't go any further, it's really easy to fix, I had the same issue yesterday.
Just try this:
- Download the latest TWRP image
- Launch it from RAM: fastboot boot twrp.img
- Now, try to flash whatever you need to!
- Reboot, and the motherboard will be put out of fastboot.
Good luck!

facuarmo said:
Don't go any further, it's really simple to fix, I had the same issue yesterday.
Just try this:
- Download the latest TWRP image
- Launch it from RAM: fastboot boot twrp.img
- Now, try to flash whatever you need to!
- Reboot, and the motherboard will be put out of fastboot.
Good luck!
Click to expand...
Click to collapse
what do you mean by "Launch it from RAM" ? and which TWRP version should I downlaod? I have the "RUN_TWRP Toolkit" which lets me enter TWRP via fastboot and windows10, is that sufficient? Thx!
The thing is, that I cant copy files to the internal storage, thats why i cannot flash a rom via that RUN TWRP Toolkit.

I downloaded the latest [unofficial] TWRP Version 3.5.2_11-0, entered TWRP via cmd, but i do not know how to flash a ROW now, since i can not copy a rom.zip to the internal storage.

I'm in a similar situation. Tried out a few roms and wanted flash back to stock. Something went wrong and now TWRP is gone and I can only boot into fastboot and stock recovery. I can fastboot TWRP, but don't know how to get a rom accessible. I tried MiFlash but that just tells me "flash done" after 5 seconds without actually doing anything. Tried just executing flash_all.bat, but it comes down to this error message:
$fastboot -s devicename getvar product 2>&1 | findstr /r /c:"^product: *alioth" || echo Missmatching image and device
Click to expand...
Click to collapse
I'm trying to flash MiUI 12.5.1 on a POCO F3, so I don't really understand. Any help would be appreciated.

I was in similar situation. Twice.
Solution: fastboot rom.
I successed with Syberia.
FASTBOOT Roms of Syberia are here:
SyberiaOS - Browse /alioth/fastboot at SourceForge.net
SyberiaOS - Browse /alioth/fastboot at SourceForge.net
Syberia Project (aka Syberia OS) is a custom ROM for many devices that implements various features. This project was designed by our "Syberia Team"…
sourceforge.net
Unpack it.
Enter fastboot mode on phone.
Run install.bat. Wait. Device reboots to system.

That worked, thank you very much! The only other option I found was to remove part of the flash_all.bat, but I didn't really feel comfortable removing something I don't quite unterstand.

ptr21 said:
I was in similar situation. Twice.
Solution: fastboot rom.
I successed with Syberia.
FASTBOOT Roms of Syberia are here:
SyberiaOS - Browse /alioth/fastboot at SourceForge.net
SyberiaOS - Browse /alioth/fastboot at SourceForge.net
Syberia Project (aka Syberia OS) is a custom ROM for many devices that implements various features. This project was designed by our "Syberia Team"…
sourceforge.net
Unpack it.
Enter fastboot mode on phone.
Run install.bat. Wait. Device reboots to system.
Click to expand...
Click to collapse
Thank you so much!! It worked

ptr21 said:
I was in similar situation. Twice.
Solution: fastboot rom.
I successed with Syberia.
FASTBOOT Roms of Syberia are here:
SyberiaOS - Browse /alioth/fastboot at SourceForge.net
SyberiaOS - Browse /alioth/fastboot at SourceForge.net
Syberia Project (aka Syberia OS) is a custom ROM for many devices that implements various features. This project was designed by our "Syberia Team"…
sourceforge.net
Unpack it.
Enter fastboot mode on phone.
Run install.bat. Wait. Device reboots to system.
Click to expand...
Click to collapse
Hi,
excuse me but I don't know English.
My Poco F3 crashes on MIUI, can I get into Fastboot or start TWRP from Windows powershell.
I downloaded the syberia_alioth-v4.7-20210715-1557-OFFICIAL-fastboot but I didn't understand how to proceed.
Could you please explain me step by step what to do?
Thank you.

pegasoc said:
Hi,
excuse me but I don't know English.
My Poco F3 crashes on MIUI, can I get into Fastboot or start TWRP from Windows powershell.
I downloaded the syberia_alioth-v4.7-20210715-1557-OFFICIAL-fastboot but I didn't understand how to proceed.
Could you please explain me step by step what to do?
Thank you.
Click to expand...
Click to collapse
Unzip syberia fastboot rom to your computer.
Enter fastboot mode on your phone (power+ volume down buttons)
Connect your phone to computer via USB
In unzipped folder of Syberia fastboot rom you find windows command : install ...... .bat
Run it. It will install Syberia rom.
Dont worry if the errors are shown, iust wait, it will reboot to Syberia rom.

ptr21 said:
Decomprimi la rom di syberia fastboot sul tuo computer.
Accedi alla modalità di avvio rapido sul telefono (pulsanti di accensione e riduzione del volume)
Collega il telefono al computer tramite USB
Nella cartella decompressa della rom Syberia fastboot trovi il comando di Windows: install ...... .bat
Eseguirlo. Installerà la rom Syberia.
Non preoccuparti se vengono mostrati gli errori, aspetta, si riavvierà su Syberia rom.
Click to expand...
Click to collapse
WOW WOW WOW WOW!!! Sei un salvavita. Grazie molte!!!
Ciò che è ancora meglio è che dopo aver bloccato POCO F3 stavo solo cercando di installare syberia_alioth-v4.7-20210723-1108-OFFICIAL.
Presumo che Syberia fastboot non sia aggiornato come syberia_alioth-v4.7-20210723-1108-OFFICIAL, per aggiornare devo installare TWRP e poi
Riavvia in TWRP
Vai su "Installa" -> scegli ROM.zipper (assicurati di aver selezionato "Inietta TWRP dopo l'installazione")
Riavvia -> ripristino
Vai su "Installa" -> scegli Gapps.zipper (Magisk, Gapps-Addons opzionali ecc.) (assicurati che NON SELEZIONATO "Inietta TWRP dopo l'installazione")
Riavvia -> Sistema
Destra?

Question Dm-Verity corruption

Hi everyone, i have the dm verity corruption on my xiaomi 11 t, it is my main phone so i need to fix it, i wanted to unlock the bootloader, but i have family link that blocks that option, so i booted it into fastboot and typed:fastboot reboot fastboot, as said from the guide, but then the phone rebooted in fastbootd, i didnt know what that was and i typed fastboot reboot and it showed the DM verity error. Is there any way to fix it?

Nixk 2 said:
Hola a todos, tengo la corrupción de dm verity en mi xiaomi 11 t, es mi teléfono principal, así que necesito arreglarlo, quería desbloquear el gestor de arranque, pero tengo un vínculo familiar que bloquea esa opción, así que lo inicié en fastboot y escribí: fastboot reboot fastboot, como se dice en la guía, pero luego el teléfono se reinició en fastbootd, no sabía qué era eso y escribí fastboot reboot y mostró el error de verdad de DM. Hay alguna manera de arreglarlo?
Click to expand...
Click to collapse
I know how to fix it, it happened to me recently too
se como arreglarlo me paso hace poco tambien

I found the solution, at this point I assume you have abd and fastboot drivers installed so:
1.- fastboot devices
2.- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3.-fastboot reboot

felixpaz1992 said:
I found the solution, at this point I assume you have abd and fastboot drivers installed so:
1.- fastboot devices
2.- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3.-fastboot reboot
Click to expand...
Click to collapse
i tried it but the phone got into bootloop
i have to do one more step

Extract the IMG file and in the last part of the fastboot command drag the extracted file in place of the vbmeta.img

felixpaz1992 said:
Extract the IMG file and in the last part of the fastboot command drag the extracted file in place of the vbmeta.img
Click to expand...
Click to collapse
Is this the nulled vbmeta.img?

felixpaz1992 said:
Extract the IMG file and in the last part of the fastboot command drag the extracted file in place of the vbmeta.img
Click to expand...
Click to collapse
do i have to wipe data or no
i still have the same issue can anyone help me still bootloop
but i want to try nippon gsi but can't because of stupid vbmeta man :-'(
can't even acsess recovery only fastboot man please help

Look with these 2 programs I instantly recovered my bricked cell phone, it even allows you to downgrade if you wish, both are free
The one that says TFT allows me to flash the complete ROM, but the bootloader will block you again, the second one that says MTK Meta Utility is used to unlock the bootloader without having to go through xiaomi

Nixk 2 said:
so i booted it into fastboot and typed:fastboot reboot fastboot, as said from the guide
Click to expand...
Click to collapse
What guide? And yes, this command boots into fastbootd mode. That's not more than a binary in your recovery and won't brick your device when it gets executed. Also a reboot from fastbootd won't brick it.
To avoid serious damage on your OS and your device, you shuld try to flash a complete firmware.

BTW: your device is in "Red state".
Boot Flow | Android Open Source Project
source.android.com

WoKoschekk said:
What guide? And yes, this command boots into fastbootd mode. That's not more than a binary in your recovery and won't brick your device when it gets executed. Also a reboot from fastbootd won't brick it.
To avoid serious damage on your OS and your device, you shuld try to flash a complete firmware.
Click to expand...
Click to collapse
I dont know, maybe i flashed something? because the device said not allowed in locked state, but i couldnt do fastboot oem unlock, i needed to enter the os, btw thanks yall for the collaboration, the phone is booting, but it is in unlocked state, i gived the phone in a repair centre to lock the bootloader. Thanks again.

your device is locked in family link. it's a brick. service center can help flashing ROM. MTK - Auth Bypass (SLA/DAA) could maybe work too (at least chipset is supported)
It's now easy to bypass MediaTek's SP Flash Tool authentication
A group of developers has created a Python utility to bypass the authentication routine of MediaTek SP Flash Tool. Check it out now!
www.xda-developers.com