Database Users

Some Help With TWRP and Bootloader Please

Hey guys. I've tried everything, and I'm stuck. Never had so much trouble doing something so basic. No idea where it's going wrong.
Here's the basic timeline:
1. Bought phone
2. Unlocked/rooted/flashed TWRP
3. Tried CM13 for a bit, clean flash +supersu
4. Tried Exodus for a bit, clean flash + supersu
5. Tried community build of 3.0.1, clean flash +supersu
6. Wanted OTA update, so dirty flashed community build to remote root, OTA update ended up replacing TWRP with stock recovery
7. I want to go back to exodus, and can't for the life of me get TWRP back on
Here's what I've tried:
1. Basic steps on any website to download adb drivers etc.
2. Tool box from XDA
3. Factory reset then try all of the above again
Issues:
When I try to fastboot flash recovery [file] I get error: cannot load 'recovery.img' I've tried renaming it to twrp.img as I've seen suggested in some places, no help. I've ensured that the image file is in the same folder as the command prompt. I have used the Grarak TWRP file as well as 3.0.2 and 2.8.7 as suggested on some other sites.
Things I'm noticing:
When I try the fastboot devices command, it only recognizes my device when in fastboot mode, but not when loaded normally. In fastboot mode I can issue commands to reboot, get info, etc. but once loaded it's all gone.
I haven't seen that prompt that comes up to authorize a computer RSA code for USB debugging (yes, USB debugging is enabled in developer options, and yes, I have tried changing the USB settings from charging, to MTP, PTP, even MIDI.)
When I use the device-info prompt I get the following results:
Device Tampered: false
Device Unlocked: true
Device is_verified: false
Charge screen enabled: false
Display panel:
console_locked: 1
exec_console_unconsole: 0
Any and all suggestions would be greatly appreciated!

Hi, Here's what i believe you need to do. If you have the correct twrp recovery img file and all you need is to just flash it to get custom recovery in order to continue enjoying your custom roms, then this will fix your problem.
1. make sure you have all the necessary adb, fastboot drivers installed and that if you run the command 'fastboot devices' fastboot can see your Oneplus device.
2. if fastboot can see your oneplus device, then worry not. use the following command to flash your custom twrp recovery.
3. Rename your recovery file to just recovery nothing else attached.
4. boot your phone into fastboot, open the folder where you have your recovery file and hold down the shift key and rightclick anywhere in the folder and select the option that says 'Open command Window Here'
5. this will load fastboot. after fast boot loads, enter the following commands :
fastboot devices (this will display your device, once your device is showing, then worry not)
6. the next command is to flash your custom recovery image. so u need to enter exactly the following :
fastboot flash recovery recovery.img (this will then flash your custom recovery. make sure you name it just recovery)
7. after flashing your recovery, enter : fastboot boot recovery.img (this will boot you into twrp recovery mode)
let me know if this helps. Cheers!!

Try to flash Hybrid recovery using fastboot. --> http://forum.xda-developers.com/oneplus-2/general/recovery-twrp-3-0-2-hybrid-supports-oos-t3362904

[GUIDE] [ROOT] LG K7 MS330 - Concise tutorial on rooting with: ADB, TWRP and SuperSU

***MOD EDIT: BE WARNED THAT WHEN PERFORMING THESE INSTRUCTIONS, THAT ALL DATA WILL BE WIPED (FACTORY RESET) FROM THE DEVICE - THIS INCLUDES THE INTERNAL DEVICE STORAGE (INTERNAL SDCARD). YOUR EXTERNAL SD FILES, HOWEVER, ARE SAFE AND WILL NOT BE MODIFIED.***​
Hello.
I will attempt to keep this tutorial as concise as humanly possible, without the expenditure of costly applicably valid information. There are many other persons (whom I do not know) to thank for the majority of this information (from XDA Developers and other sites around the world wide web). Without further adieu: Let's begin!
The base operating system that this tutorial references is a Windows distro (I am operating on: Windows 10 Home OEM).
Target phone specs (http://www.lg.com/us/cell-phones/lg-MS330-White-k7):
Carrier: MetroPCS®[*]
[*]Make: LG K7 ("HW" or "White")
[*]Model: LG MS330
[*]Build number: LMY47V
[*]Software version: MS33010m
[*]Android version: 5.1.1
[*]Android security patch level: 2017-04-01
[*]Kernel version: 3.10.49​
Prerequisites:
A USB cable (able to transfer data)
A functional copy of Windows
An internet connection (to download the software tools)
If you opt to not download and install the stock firmware ROM (*.kdz) and LG UP (used for many things):
You are taking a great risk in the event something catastrophic occurs (no backup; Corrupted partition(s); Broken hard-key reset; etc).
The LG UP tool combined with the ROM file enables you to fully slate the drive on the phone (effectively restoring it to a manufacturers state; No partitions, no data, nothing!).
It also acts as a major fail-safe as previously iterated.
You can also (if you take the time of day) use it to create your own customized 'factory style' bloatware free, customized filled state *.KDZ ROM! Although TWRP backups should be capable of emulating this type of behavior.
The ROM is ~1GB in file size from the server (capped at ~10MB/s download rate at the time of the writing of this post). Translation: It takes a while (~30min) to download. Fortunately for me: I had it and had to use it earlier today (TWRP backup failed).
Software tools (ADB, TWRP, SuperSU, LG UP, ROM):
ADB (Android Debug Bridge): https://developer.android.com/studio/releases/platform-tools.html
TWRP (Team Win Recovery Project) v3.2.1.0: https://twrp.me/lg/lgk7.html
SuperSU (SuperUser) v2.82: http://www.supersu.com/download
LG UP Lab v1.10: https://www.mylgphones.com/download-lg-up-software
Stock ROM (MS33010i -- *.kdz): https://mega.nz/#F!sdwRDLbZ!yPOiRPv5QJS_9I4hzL4ptQ!ddJHSBhR
This will be a step-by-step process; If you skip a step: Make sure you have a good reason!
I will be assuming you have followed the links above and both downloaded and installed the appropriate software (ADB, LG UP). Keeping everything organized is key.
For instance: Create a folder on your main drive ("C" drive is common traditionally). Name this folder "Rooty." Create a short-cut of "adb.exe" and place it there. Place the SuperSU *.zip and *.kdz ROM data files in the same directory as well.
Overview of procedures:
Enable "OEM unlock"
Enable "USB debugging"
Unlock OEM bootloader
Install ("flash") TWRP
Using LG UP (after TWRP is either installed or live loaded)
Install SuperSU
Step 1) Enable developer options
Enabling developer options -- Navigate to "Settings," then to "About phone," then to "Software info," then tap on "Build number" until the dialog states: "No need, you are already a developer."
Step 1.1) Enable OEM unlock option
Traverse two levels up; Tick off "Enable OEM unlock"; Scroll down 2 options and tick off "USB debugging."
Step 2) Unlocking the OEM bootloader
Insert your USB cable to connect your desktop/laptop to your cellphone; When the dialog comes up asking for permission to debug: Accept it (OPTIONAL: Tick off the 'always allow this device'). Ensure "Media device (MTP)" option is selected (it will automatically install the drivers from your phone to your computer if enabled).
Step 2.1) Unlocking the OEM bootloader (for the not-so-technically-inclined)
Create a textfile and name it whatever you'd like (I prefer the filename: "OEM_Unlock.bat").
Copy and paste this script and simply place it in the same directory ('folder') as ADB.
Code:
REM This will reboot the phone into "bootloader" mode
adb reboot bootloader
REM This will unlock the OEM bootloader (a message will display on the starting logo afterwards)
fastboot oem unlock
REM This is just to verify that it was successfully unlocked ("unlocked: yes")
fastboot getvar unlocked
Alternatively: You can manually input the commands one at a time by typing them yourself or copying and pasting.
Step 3) Installing TWRP
You can just use ADB to directly flash the recovery partition of the ROM on the phone:
Code:
fastboot erase recovery
fastboot flash recovery C:/Android/recovery.img
You can also simply 'live boot' into TWRP (less risk of a faulty TWRP):
Code:
fastboot boot C:/Android/recovery.img
Now TWRP is installed (unless you simply loaded the image file into the phone's RAM).
Using LG UP to flash the ROM ("WIPE" every partition of the phone with TWRP; EVERYTHING will be lost:
To use LG UP: You only need to power down the phone fully (ensure it is not yet connected to the computer).
Hold the "VOLUME UP" key (do not release); Insert the USB cable. The phone should (within moments) place itself into "DOWNLOAD MODE." At which point LG UP will recognize the phone. There will be two options: "Refurbished" and "Upgrade"; Tick off 'upgrade' every time! Below that is "3 dots" which enables you to navigate (GUI) to the directory of your desired *.tot or *.kdz file. Simply hit "start" and it'll flash the phone (it usually takes ~300s or ~5m).
Step 4) Installing SuperSU
Through TWRP: Click on "Advanced"; Then click on "ADB Sideload"; Tick both the "Wipe Dalvik cache" and "Wipe cache" (these will force all APKs to be reinstalled via root level). Then slide the bar across. Return your attention to Windows.
You can just use ADB to directly sideload SuperSu onto the phone.
Code:
adb sideload C:/Android/SuperSU.zip
The final page asks if you would like to install the "official TWRP app" and also if you'd like to install it under "system" privileges (one less than root).
The end! You now have root accessible privileges through the "SuperSu" application (which contains root privilege at this point).
Alternatively to manually inputing everything by hand into ADB: I've whipped up this simple batch script for Windows:
Code:
ECHO OFF
CD\
CLS
ECHO Waiting for the device to communicate (ensure you are not in 'recovery,' 'sideload,' or 'bootloader' state)
adb wait-for-device
REM Reboots to the bootloader
adb reboot bootloader
REM Unlocks the OEM bootloader
fastboot oem unlock
REM Quick check to see if it successfully unlocked
fastboot getvar unlocked
REM Flashes (deleting the stock ROM recovery program)
fastboot erase recovery
REM Flashes (copies the TWRP custom recovery program)
fastboot flash recovery C:/Android/recovery.img
REM Loads the TWRP custom recovery program into memory (a "live boot")
fastboot boot C:/Android/recovery.img
REM Pauses execution until the phone boots into "recovery" state
ECHO Wait until the phone enters a "recovery" state...
adb wait-for-recovery
CLS
ECHO Traverse to "Advanced" then to "ADB Sideload"
ECHO Check off clearing both the Dalvik cache and cache
ECHO Press any key *after* you swipe the bar across
ECHO(
PAUSE
REM Copies over the APK to the ROM (security exploit to gain root permissions)
adb sideload C:/Android/SuperSU.zip
adb reboot
How to use the batch script file to root your phone with ADB, TWRP and SuperSU:
Place: SuperSU.zip and TWRP.img in the same directory as the ABD/fastboot executables
Modify the absolute paths and file names to your system (EG: "C:/Android/" and "recovery.img")
I hate to post this, but I feel it to be utterly important to express my deepest gratitude to all those who have posted this information that was scattered about the internet. This is my first Android or PHONE for that matter to root! It was quite the under-taking (nearly a 48 hour scourge of research). I've learned quite a bit how the Android OS works internally as a result; as well as the tool-kits that are commonly used in conjunction with modding the Android (out of the scope of this thread).
I hope this very recently updated and compiled information will help ease the suffering of another's entrance into the world of rooting Android phones. I also hope it really deepens the understanding of what they're doing (EG: The commands being utilized with abd and fastboot).
Here is a helpful link in regards to adb/fastboot:
- Quick reference to abd commands (syntax and meaning): https://developer.android.com/studio/command-line/adb.html
- Alternatively: You can use "adb help" to see a print-out of the commands and arguments (same applies to fastboot).
Happy rooting, y'all!

Thanks for the write-up!
The attached SuperSU.zip worked perfect to gain root on my K7 m1 using the adb sideload in Twrp and PC.
My bootloader I had already unlocked. Twrp, I flashed before I accomplished that feat!
Was rooted with Kingroot but wasn't satisfied with that.
Factory reset, and followed your adb sideload instructions to gain root with SuperSU.zip ..
Thanks again my friend.
Custom Roms for the K7 seem to be scarce, unless I am looking in all the wrong places.
Would be much appreciated if anyone could help me on that front?? ... Please let me know.

Good Day
With very insignificant changes to syntax used above I found this works perfectly on OSX as well.
Thanks

hi, i cant seem to unlock the bootloader. i have already enabled oem unlock and usb debuggin from settings but it always fails
Code:
PS C:\adb> adb devices
List of devices attached
ZSTSS8DUSWZD9LCE unauthorized
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot devices
ZSTSS8DUSWZD9LCE fastboot
PS C:\adb> fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 9.294s
I should note that kingrot also failed to root
i dont know whats wrong, imma gonna try factory reset and try again
UPDATE
It seems the allow oem unlock option got disabled by itself somehow, i re enabled, tried again and unlocked succesfully
UPDATE 2
Aaaaand Bootloop, dunno what went wrong, iv'e reached step 4, flashed twrp, then tried to reboot into twrp and now im stuck in bootloop
Code:
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 8.981s]
finished. total time: 8.983s
PS C:\adb> fastboot getvar unlocked
unlocked: yes
finished. total time: 0.003s
PS C:\adb> fastbot erase recovery
fastbot : The term 'fastbot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ fastbot erase recovery
+ ~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastbot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS C:\adb> fastboot erase recovery
erasing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.004s
PS C:\adb> fastboot flash recovery c:/adb/lg.img
target reported max download size of 134217728 bytes
sending 'recovery' (12010 KB)...
OKAY [ 0.394s]
writing 'recovery'...
OKAY [ 0.706s]
finished. total time: 1.103s
PS C:\adb> adb reboot recovery
error: device '(null)' not found

v20 H918 fastboot/twrp/bootloop brick

i have 3 lg
one of them is seen by my linux mint 20.1 desktop. this is my good stable and never touches any mods till my two better phones are running.
the other 2 i can get into fast boot, they were previously rooted & running orea/8 stock rooted
neither of those other 2 phones are recognized by my pc
i am using the adb reboot bootloader and get no joy on the 2 suborn phones.
both of the two phones refused to flash roms of any sort or type after a twrp wipe.
one of the phones is now fastboot only and nothing else ever happens and no connection to the pc is ever made
the other phone still goes into twrp most of the time,,sometimes fastboot only,,and still refuses to take any rom of any sort at all
my goal is to reflash twrp, and throw on lineage stable
BUT
not desktop connection?
someone pleas help me unbrick these two

updot
i found a way to get coms, but it is still failsauce.
.
the instructions on twrp page failed because my system could not read that far into my hard drive
.
TWRP Installation Tutorial for Linux Mint and Ubuntu users » AndroidGuru.eu
TWRP (Team Win Recovery Project) is an open-source custom recovery image for Android devices. It is a replacement for the stock recovery mode that is installed on most Android devices by the manufacturer. TWRP provides various advanced features and options that are not available in the stock...
www.androidguru.eu
.
seeing the fail sequence @ terminal feedback info i used that to go to where it WAS reading from, pasted the .img file there, then ran the commands @ that point
result was
.
[email protected]:~$ sudo fastboot flash boot /home/twrp-3.5.0_9-0-h918.img
target reported max download size of 536870912 bytes
sending 'boot' (23540 KB)...
OKAY [ 0.681s]
writing 'boot'...
FAILED (remote: unknown command)
finished. total time: 0.700s
[email protected]:~$
now i need to troubleshoot /fix why my phone is refusing to accept a flash,,even though it is correctly responding back to
sudo fastboot devices
any advice would be GREATLY appreciated.
will update as possible.if the Lord be willing.
event time stamp @ 4:30 - 2/9/21

notes :
adb sideload Full-Path-to-the-file.zip
CommandFunctionsADB Commandsadb devicesShows attached devicesadb shellTo jump from windows command prompt to android device shell:adb reboot bootloaderTo boot into bootloader modeadb reboot recoveryTo boot into recoveryadb get-serial noGet Serial Number of your connected deviceadb installTo install apps over adbadb install -rTo update the existing apps with new versionadb uninstall package_name.hereTo uninstall any apps or packages from the connected deviceadb uninstall -package_name.hereKeep the data and cache directories after uninstalling appsadb push <local> <remote>Upload a specified file from your computer to deviceadb pullDownload a specified file from your device to your computer.adb backupTake backup from your device to PCadb restoreRestore the backup to your phoneadb sideloadTo sideload apps or flashable zip file to your deviceadb logcatTake the realtime log from your phoneadb start-serverstart adb servers processesadb kill-serverstop adb server processesadb reboot fastbootreboot your device into fastboot modeadb usbshows all devices connected to your computer via a USB cable.adb devices //show devices attachedIt will display the list of all devices attached to your PC.adb connect ip_address_of_deviceconnect the IP address of your Android device to your computer.Fastboot commandsfastboot devicesShows connected devices on your PC/Laptopfastboot rebootTo reboot your devicefastboot reboot recoveryTo boot your device into recovery modefastboot oem device-infoTo check the bootloader unlock status:fastboot oem unlockIf the above command returns fall, run the following to unlock the bootloaderfastboot flashing unlockFew OEM may use this command to unlock bootloaderfastboot flashing unlock_criticalAllow flashing of bootloader related partitions too:fastboot oem device-infocheck bootloader lock/ unlock statusfastboot flash recovery [recovery.img]To flash recovery on your devicefastboot boot [boot.img]To test the recovery without permanently flashingfastboot format:ext4 userdataTo format data partitionfastboot flash boot [boot img name]flash flashable boot.img from fastboot modefastboot getvar cidTo display CID of your deviceFlashing ROM via Fastboot ROM zip packagefastboot -w
fastboot update </path/to/your/Rom.zip>
ref :
Basic ADB and Fastboot commands that you should learn to become Android Pro
Basic ADB command that you should learn to become Android Pro: Every Android developer or Android enthusiast should know some basic ADB comma
www.getdroidtips.com

thinking out loud.
everything i am seeing sais if my handset is not recognized by the desktop PC then my drivers are not correct.
problem with that statement is one of my 3 V20's does connect. correctly.
the other two are
FAILED (remote: unknown command)
as if there was no phone connected
but they are recognized under the fastboot devices, showing the connection is recognized by the PC, but not recognized by the phone.
how?
someone tell me pleas?
how do i get the 2 derpy phones to recognize the pc?

i am very much in a less then 3rd world country circumstance. (16 kbps max download speed for more then a week now) connecting to the internet is almost impossible as it is under excellent circumstances. for me to reboot into a Live os, and then set up a full NIC config before the Live freezes, glitches out or other wise kicks me in the face is almost impossible.
i am guna try to make an install. drag copy everything from the install to my os. this arch distro is built super similar to parrot os, so i might be able to make something work.
time will tell.
so far i have a failed atempt at this point
--------------------------------------------------------------------------------------------------------------------------------
[email protected]:/home/lglaf$ cd lglaf
bash: cd: lglaf: No such file or directory
[email protected]:/home/lglaf$ sudo git checkout h918-miscwrte #for the TMO V20
error: pathspec 'h918-miscwrte' did not match any file(s) known to git
--------------------------------------------------------------------------------------------------------------------------------
the lafsploit is not able to "get" from the hub. looks like files have been removed?
now how do i get what i need?
took me an hour and a half to run less than 10 cmd lines.
not to mention thes fails are forcing me to unplug a phone while in download mode.
this is not fun.
any one know where i can download the file "h918-miscwrte"
looks like it is no longer on github
[email protected]:/home/lglaf# git pull
Already up to date.
[email protected]:/home/lglaf# git checkout h918-miscwrte
error: pathspec 'h918-miscwrte' did not match any file(s) known to git
hard thing waiting.

OnePlus 8 TMO Magisk boot image IN2017_11_C.43

It took a bit of work to root OnePlus 8 T-Mobile version on the latest Android 12 update. I am a long time lurker and simply I wished someone else had posted the boot image to save me time. Can be simply flashed using fastboot commands.
Please check to make sure you are on the latest update from T-Mobile and that software version is: IN2017_11_C.43 Android 12 Security update November 5, 2022.
Installation instructions:
*You must have your phone unlocked for any carrier otherwise OEM unlocking will be unable to set.*
#1 go to settings, about device. TAP software version five times to enable developer options under system settings. Go to developer options and tick the following options:
a OEM Unlocking
b Enable USB debugging
#2 Download the OnePlus 8 Windows drivers and ADB fastboot drivers if your using a PC or Termux from F-Droid if using another rooted phone.
PC instructions:
Go to the directory you installed ADB and Fastboot. Open the command prompt by either right click on an empty space in that folder and finding command prompt or going to the directory tree and typing cmd and hit enter. Inside the Windows command prompt the root directory should be the same folder as your ADB and fastboot executables. Move the attached boot image to the same folder as your ADB and fastboot executables and rename it boot.img. Attach your phone to your PC and run the following commands:
adb devices
This command is so you can check to see if your PC is correctly configured and it should send you a notification on your phone to allow debugging from your PC, make sure you will allow it always.
adb reboot fastboot
This command will reboot your phone into fastboot mode. Do not select any you on your phone and only type in the following commands on your PC.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This command will flash the magisk modified boot image which will grant you root access to your phone.
fastboot reboot
This command will reboot your phone. Congrats, your now rooted on the latest Android 12 update for your T-Mobile Oneplus 8!

what attached boot img?

zeromonarch said:
what attached boot img?
Click to expand...
Click to collapse
I must've somehow missed it too. I cant find any boot image to download

If only there were the elusive boot image...
It could have saved my ass from the current double-slotted brick I sit upon!

Does anyone have the boot image for the latest T-Mobile update?
IN2017_11_C.45
in fact this isn't even the latest as there is a new update waiting for me with the new security release or security update but I haven't updated yet also does this wipe data?

Can't use fastboot anymore

I've just bought a OnePlus 6T and wanted to install LineageOS on it using this guide
I stopped at the step saying to boot custom recovery, it didn't worked for me.
Then I tried using TWRP to install the zip file provided but it said that it was invalid so it did not install it.
During these steps, i locked and unlocked the bootloader a lot of time to boot to recovery, I now know that it was not the way to do it.
I now want to go back to Stock ROM or LineageOS if possible but it seems that fastboot commands don't work anymore:
- `fastboot devices`: the device is listed
- `fastboot set_active b` : says "FAILED (remote: 'unknown command')"
- `fastboot flash boot boot.img`: the devices goes into a black screen saying "press any key to reboot"
- trying to boot: After the unlocked bootloader warning, it displays `QUALCOMM CrashDump Mode`
I already flashed boot_a and boot_b slots and used this script partially (before it crashed) to restore some of the default partitions
I don't know what to do as the usual commands (fastboot) don't work at all.
PS:
My computer is using `fastboot version 33.0.3p2-android-tools` on Arch Linux (USB 3.0)
I also tried with `fastboot version 33.0.3p2-android-tools` on Manjaro Linux (USB 2.0)

Hi.
When I install custom rom and fail very badly then I use tool from here. It will take you right to the beginning with oxygenos installed and bootloader locked. You can start over again with Lineage installation.