#SharePointProblems | Koskila.net

Solutions are worthless unless shared! Antti K. Koskela's Personal Professional Blog

How to use TWRP to flash an Android device that refuses to boot to TWRP?

koskila
Reading Time 5 min
Word Count 800 words
Comments 23 comments
Rating 4.1 (9 votes)
View

Last Christmas holiday I was tasked by older relatives to fix an Android tablet they had bought. One of those absolutely useless, 100€ devices that can't really run any apps, and struggle to even start. My first proposition was to return the device - but it was already past the return window.

Lenovo's bloated nightmare version of an Android was likely the biggest reason for slowness. My second course of action was to change the launcher and disable everything I could, but the device still couldn't run YouTube, Spotify, or YLE Areena.

I figured that I needed to change the device to run some other Android version, and there are multiple guides online on how to overwrite the operating system with an alternative. However, when you run into issues with tools like fastboot not working or TWRP (or similar custom bootloader) not working, the guides are no help. This article aims to fix that gap.

All that said, on to flashing the device!

Prerequisites

A couple of first steps were easy:

  1. Enable Developer mode
  2. Enable Debugging over USB
  3. Install ADB and Fastboot drivers (you can get them from here: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118)
  4. Download the right TWRP image for your device (an example: https://unofficialtwrp.com/lenovo-tb-x103f-root-twrp/).
  5. Upload your custom ROM of choice to the internal storage of the device
  6. Upload custom Google Apps package to the internal storage of the device (https://opengapps.org/)

I won't go into details, as I suppose you're following a tutorial on XDA-developers or something, and only ended up on this article since you ran into the same issues I did. The tutorials do a good job detailing most of the steps but fall short when you run into issues.

Also, you won't need Magisk or similar if you're working with an otherwise useless device and don't need any backups (because nobody's been able to generate anything worth saving on the device so far). And if you're following tutorials on getdroidtips.com or something, be mindful of which links you're clicking and which files you download on MediaFire.

Anyway, back to the topic.

You should make sure your adb and fastboot installation path is included in your PATH variable - or, alternatively, just open your command line window (as an admin) to the installation directory directly.

Using TWRP to flash your android device:

Time needed: 5 minutes.

  1. Unlock your bootloader

    You will need to make sure you can boot any media instead of the built-in one. To do this, connect the device with USB, debugging enabled, and run the following:

    fastboot oem unlock-go

    If that gives you an error, try this command instead:

    fastboot flashing unlock

    All good? Awesome! Onto the next step...

  2. Install custom loader such as TWRP

    After this, it's supposed to be easy to flash TWRP to the device and boot to it using the commands below (the mentioned image needs to be in the folder you're running the commands from):

    adb reboot bootloader fastboot flash recovery TWRP-3.0.2_TB-X103F-beta.img fastboot reboot

    That was successful for me. But Lenovo had, unfortunately, made more annoying decisions. +Vol and power would take the Android tablet to recover mode - but even with TWRP successfully flashed to the recovery partition, you'd always be greeted with the useless, out-of-the-box recovery mode.

    Curiously, though, -Vol takes the user to a diagnostics mode that's in Chinese(?). I couldn't make anything out of it, so I decided to pursue another route.

    I spent a while reflashing, using different medias, and rebooting the device (which somehow takes multiple minutes), but to no avail. I couldn't find a way to force the device to start in TWRP instead of the out-of-the-box recovery mode.

    But luckily, there's another workaround available!

    Using fastboot you can actually flash the whole device if you have a suitable media at hand (I didn't), or force booting to TWRP from a media that's on your laptop. The latter ended up being my choice and worked nicely.

  3. Load TWRP without replacing the built-in bootloader

    Should you want to do this, simply run this below (supposing you have the .img file in your working directory already):

    fastboot boot TWRP-3.0.2_TB-X103F-beta.img

    This should, after a while, boot your device into TWRP once. That should be all you need :)
    After this, it was trivial to install LineageOS to the machine using TWRP. And boy, was it faster than Lenovo's Android!

That's all for now. Hope it helps someone :)

References

Comments

Interactive comments not implemented yet. Showing legacy comments migrated from WordPress.
D Brown
2020-04-04 00:10:27)
I'm having the same exact issue, only with the cubot p20. The same thing with the default recovery and the Chinese thingy. But I'm a noob, so I'm not sure what media you are referring to. Been trying to flash this phone for about a year, but this is the first post I see that is similar to my issue. Please help me.
2020-04-08 11:34:08
Thanks for your comment! A lot of these things are pretty frustrating to work with.. Which step are you stuck with? By "Media" I'm referring to the mounted medium where your device should load the operating system from. You can usually unlock this using fastboot (it's locked by default) like shown in the examples above.
B.S.V. Prasad
2020-12-25 12:12:38)
Great article. I was trying to install Lineage on a Google Nexus flo tab, following a number of blogs. I successfully unlocked the bootloader & managed to flash twrp. However, Twrp fails to go much beyond initial flash screen. It crashes after a while, and keeps trying to reboot. I tried "Fastboot boot twrp" as suggested by you, but fastboot just says "waiting for device" and stops, while twrp keeps relaunching itself & failing on the tab. An "adb devices" reports the device is in recovery mode. Can you suggest a way out? Thanks a ton!
Antti K. Koskela
2020-12-26 23:14:41
Hi there, If there's one thing I've learned about Android devices, it's that they're all different because each and every single manufacturer wants to do things differently... What I CAN say, however, is that fastboot boot TWRP-3.0.2_TB-X103F-beta.img worked for me, but I do recall that I DID have to restart and reset my device a few times before it finally finished successfully. Of course, it could always just be a really low-quality usb cable you're using :) So be sure to replace that, too! Hope this helps & good luck!
adb
2021-01-05 11:43:39)
i had that exact problem but more worse i cant boot the image idk whats wrong my mobile version is 8.1 oreo
Antti K. Koskela
2021-01-10 21:08:44
Hi adb, Don't take my word for this, but maybe flashing the whole device would still work even if you can't boot using fastboot? Something like this:
fastboot erase userdata
fastboot erase cache
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
Copied from here. Note - I never needed to do this, tread carefully.
2021-01-13 12:23:27)
I was facing the same issue with my mobile. using this link, now it is working fine. https://firmwareflashfiles.com/jio-f220b-flash-download/
Antti K. Koskela
2021-01-13 16:52:51
Thanks for your contribution, James! That site appears to be registered and set up very recently. A lot of sites out there publishing murky download files, so just wondering whether that's legit or not.
Bailey
2021-01-28 21:11:46)
Hey! Okay, I am a complete noob when it comes to all this. And to be frank I'm not even sure if any of what I'm struggling with is part of this discussion. But since this page is active I'm giving it a shot! About a year or two back we found our old tablet (Samsung galaxy 5100 tablet) and I found a good video that explains how to basically turn your old hardware on the tablet into newer hardware. I'm hoping that I'm just the correct terminology... The programs or files I used where something about SuperSu, Lineage Os and Twrp. To be frank - I'm not sure what they do. Anyway. I did all the steps and everything worked out good. The tablet was completely different looking with the layout and all that. But I remember that I ran into problems... it was quite slow, the google play was just not having it. And it was just a mess. I couldn't really download things effectively, since the browser didn't really function very well - I think it had to do with the fact that it was out of date. But like a said, complete noob! Anyhoo, long story short, the tablet stopped working. Everytime I press the volume button and power on button for a while it gets stuck in lineage os's loading screen and it just never comes out. I can't access the recovery or download mode what so ever, since when I do the whole volume button and power thing it only leads me back to the load screen. I try to understand the big words, but I'm too dumb with this kind of stuff. Literally ANY help would be sooo appreciated!!
Antti K. Koskela
2021-02-05 10:44:54
Hi Bailey, Wow, thanks for a very entertaining comment! :D Some of the custom ROMs - that's the LineageOS part - are less than perfect ports for some devices. And sometimes they might've been perfect back in the day, but deteriorate over time. Custom ROMs are usually maintained by hobbyists and come with no official support, so while they often work far better than original version, they come with no warranty... I ran into a similar issue with my device, which is when fastboot helped out, as it rebooted from custom image (hosted on my laptop) without replacing the bootloader. Can you hook the device up with USB and run something like this:
fastboot boot imagename.img
abrar
2021-01-29 19:37:52)
hey, i have got a samsung verizon note 3 and it is bricked, so that it is not booting in download mode, only in official recovery mode. can you please tell me how can i flash a custom recovery or a custom rom in recovery mode.
Antti K. Koskela
2021-02-05 10:46:15
Hey abrar, I know I sound like a parrot (at least if you read the other comments), but what happens when you run this:
fastboot boot imagename.img
Whitewater Magpie Ltd.
© 2025
Static Site Generation timestamp: 2025-08-26T05:15:56Z