Database Info

[RECOVERY][e2nam] TWRP 2.8.5.0 touch recovery LG MS395

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.8.5.0:
-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements
CHANGELOG for 2.8.4.0:
-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
CHANGELOG for 2.8.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
Also note that you will need the latest adb binaries on your computer to sideload with this new version of TWRP.
CHANGELOG for 2.8.1.0:
-MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
-TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
-Temperature support - thanks to bigbiff
-Various other bugfixes and tweaks
CHANGELOG for 2.8.0.1:
-Fix a bug that causes weird graphics glitches and touch issues
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Added a class to search for files to make finding the correct brightness file automatic in most cases
-Various other bugfixes and tweaks
DOWNLOAD:
TWRP Builds
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

Latest Windows adb drivers required for sideload
HERE
Latest Linux adb drivers required for sideload compiled from android source
HERE
To install unzip and open terminal in root of folder
Code:
sudo cp adb fastboot /usr/bin

Installation
You must be rooted first follow the guide here
This can be flashed with several methods
1.) Flashify
Choose the name of the recovery image you want to flash
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
2.) Fastboot (Must be enabled first)
Start ADB shell
Code:
adb.exe shell
Get root permission
Code:
su
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img
Run the following code to zero out laf:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
To flash recovery copy openrecovery-twrp-2.8.5.0-e2nam.img to root of folder that contains fastboot.exe and start a command prompt
Code:
fastboot.exe flash recovery openrecovery-twrp-2.8.5.0-e2nam.img
To boot into recovery
Code:
fastboot.exe boot openrecovery-twrp-2.8.5.0-e2nam.img
3.) ADB shell
Copy recovery.img to root of folder that contains adb.exe and start a command prompt
Code:
adb.exe push openrecovery-twrp-2.8.5.0-e2nam.img /sdcard/
Start ADB shell
Code:
adb.exe shell
Get root permission
Code:
su
Install the image
Code:
dd if=/sdcard/openrecovery-twrp-2.8.5.0-e2nam.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
to boot into recovery
Code:
reboot recovery

Thanks for this. Will give it a try after work today. Hopefully unlocking won't give a noob like me any trouble.

I would recommend just putting the recovery on laf
Code:
fastboot flash laf recovery.img
We don't have button combo and it makes booting into recovery easier if you don't have access to the system or a PC by allowing you to boot into recovery the same way you boot into download mode.

Thank you!
Unjustified Dev said:
Installation
You must be rooted first with boot loader unlocked follow the guide here
This can be flashed with several methods
1.) Flashify
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
2.) fastboot (Only works if you chose to keep fastboot mode in the linked guide)
To flash recovery copy recovery.img to root of folder that contains fastboot.exe and start a command prompt
Code:
fastboot.exe flash recovery recovery.img
To boot into recovery
Code:
fastboot.exe boot recovery.img
3.) ADB shell
Copy recovery.img to root of folder that contains adb.exe and start a command prompt
Code:
adb.exe push recovery.img /sdcard/
Start ADB shell
Code:
adb.exe shell
Get root permission
Code:
su
Install the image
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
to boot into recovery
Code:
reboot recovery
Click to expand...
Click to collapse
This works. No problems. :laugh:

Unjustified Dev said:
Installation
You must be rooted first with boot loader unlocked follow the guide here
This can be flashed with several methods
1.) Flashify
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
2.) fastboot (Only works if you chose to keep fastboot mode in the linked guide)
To flash recovery copy recovery.img to root of folder that contains fastboot.exe and start a command prompt
Code:
fastboot.exe flash recovery recovery.img
To boot into recovery
Code:
fastboot.exe boot recovery.img
3.) ADB shell
Copy recovery.img to root of folder that contains adb.exe and start a command prompt
Code:
adb.exe push recovery.img /sdcard/
Start ADB shell
Code:
adb.exe shell
Get root permission
Code:
su
Install the image
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
to boot into recovery
Code:
reboot recovery
Click to expand...
Click to collapse
I can't seem to get the into fastboot. I have Minimal adb and Fastboot installed, put the recovery image that folder, but my phone just reboots normal no how I tell fastboot to do it..recovery, download, etc. Don't understand this, could it be causing this "fastboot (Only works if you chose to keep fastboot mode in the linked guide) "

Unjustified Dev said:
Installation
You must be rooted first with boot loader unlocked follow the guide here
This can be flashed with several methods
1.) Flashify
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
2.) fastboot (Only works if you chose to keep fastboot mode in the linked guide)
To flash recovery copy recovery.img to root of folder that contains fastboot.exe and start a command prompt
Code:
fastboot.exe flash recovery recovery.img
To boot into recovery
Code:
fastboot.exe boot recovery.img
3.) ADB shell
Copy recovery.img to root of folder that contains adb.exe and start a command prompt
Code:
adb.exe push recovery.img /sdcard/
Start ADB shell
Code:
adb.exe shell
Get root permission
Code:
su
Install the image
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
to boot into recovery
Code:
reboot recovery
Click to expand...
Click to collapse
Step 2 didn't have the adb in the code and I was copy and pasting and could get it to work. Finally figured it out. I know it's a rookie thing with me and this was the first time I used fastboot. Working now and have TWRP. Thanks!!

I was able to get TWRP on using fastboot but I don't understand this- "2.) fastboot (Only works if you chose to keep fastboot mode in the linked guide) "
Are you referring to having the recovery.img file the same location as fastbook.exe or does this mean something else?
Thanks

I'm a noobie with a question. Fortunately I was able to root and install twrp with flashfy app. Down the road if I brick my phone, how can I recover? Is there button combo on the f60 for twrp? what is fastboot?
Sent from my Z970 using Tapatalk

I am new myself and will let Unjustified explain Fastboot, although I did use that method to flash TWRP, I don't want to give you bad advice. With that said, I have Xposed Framework installed and also Gravity Box KK. Gravity box has many cool customizations and one is you can change the options you get when you reboot your phone. One the choices is reboot into recovery. Hit that and you will boot up into TWRP.
If that doesn't work for you, there is an app called Quick Boot in the play store that does the same thing as far as different choices for rebooting. Fastboot you would need to connect to you PC/Laptop and know the commands to boot into recovery, again any further details I l;eave to others that know more.
Hope this helps some.
---------- Post added at 07:20 AM ---------- Previous post was at 07:09 AM ----------
smilesintears77 said:
I'm a noobie with a question. Fortunately I was able to root and install twrp with flashfy app. Down the road if I brick my phone, how can I recover? Is there button combo on the f60 for twrp? what is fastboot?
Sent from my Z970 using Tapatalk
Click to expand...
Click to collapse
I used this: http://forum.xda-developers.com/showthread.php?t=2317790. You can read in that thread for more info on ADB and fastboot. This was a little easier for me then just using the commands posted above where you would execute them with CMD prompt from your PC, just make sure you are going to the root folder where the adb.exe and fastboot.exe are located. I was doing that wrong when I was trying to root at first. My choice not to use Flashify was strictly because I wanted to learn more, so please wait for others to chime in who know more then I.

Our phone has no button combo to reach recovery.
You usually would be able to use the factory reset button combo and then cancel to recovery but all I get is hardware cursor mode. If someone else has achieved these results then disregard the below message. :
If you would like to reach recovery from power off, then we will either need a modified aboot, or you can flash recovery over laf (download mode).
Code:
fastboot flash laf recovery.img
As for xposed, get g3tweaksbox from play store. It used to be a paid app but works flawlessly.

bichofelix said:
Our phone has no button combo to reach recovery.
You usually would be able to use the factory reset button combo and then cancel to recovery but all I get is hardware cursor mode. If someone else has achieved these results then disregard the below message. :
If you would like to reach recovery from power off, then we will either need a modified aboot, or you can flash recovery over laf (download mode).
Code:
fastboot flash laf recovery.img
As for xposed, get g3tweaksbox from play store. It used to be a paid app but works flawlessly.
Click to expand...
Click to collapse
I got to recovery once you reach factory reset I clicked yes and it went to twrp. Search Google for hard resetting F60.

TWRP Backup
Question regarding making my first back up in TWRP. I know how to do it, just wanted input on a couple of thing so I have a good back up for if/when I mess something up. As of now, my back up I made has several apps (including system) disabled via @gatesjunior Debloater. I also have Xposed installed and Greenify and Gravity Box Modules installed.
Would I be better to put things back to stock and make a back up of the phone as it was when I bought (except root) or would a backup like I have to good enough to restore from.
Thanks again for all the help, especially on my stupid questions. LOL

lowender62 said:
Question regarding making my first back up in TWRP. I know how to do it, just wanted input on a couple of thing so I have a good back up for if/when I mess something up. As of now, my back up I made has several apps (including system) disabled via @gatesjunior Debloater. I also have Xposed installed and Greenify and Gravity Box Modules installed.
Would I be better to put things back to stock and make a back up of the phone as it was when I bought (except root) or would a backup like I have to good enough to restore from.
Thanks again for all the help, especially on my stupid questions. LOL
Click to expand...
Click to collapse
As long as what you backup is currently usable you should be fine.
Unjustified Dev said:
I got to recovery once you reach factory reset I clicked yes and it went to twrp. Search Google for hard resetting F60.
Click to expand...
Click to collapse
Actually that did work. I was pressing vol+/-.
So to reiterate for others, to reach recovery you hold power & vol- until you see the lg logo, then release and immediately press and hold power again until factory reset comes up. Press yes then yes and bam.
Also, have you started a github for this device, yet?

bichofelix said:
As long as what you backup is currently usable you should be fine.
Actually that did work. I was pressing vol+/-.
So to reiterate for others, to reach recovery you hold power & vol- until you see the lg logo, then release and immediately press and hold power again until factory reset comes up. Press yes then yes and bam.
Also, have you started a github for this device, yet?
Click to expand...
Click to collapse
Thanks for the info on my backup. It does work fine and is they way I like it, so I will just keep it. On the reboot to recovery I tried that and got a different screen with mode off, mode on, etc but didn't see factory reset. Highlight was Mode Off and I moved up and selected mode on. Now when I try it boots up normally. Anyway I can set it back to Mode off like it was?
Thanks for your help!!

Unjustified Dev said:
I got to recovery once you reach factory reset I clicked yes and it went to twrp. Search Google for hard resetting F60.
Click to expand...
Click to collapse
Yes! this was what I was looking for! Thank you.
Sent from my Z970 using Tapatalk

lowender62 said:
Thanks for the info on my backup. It does work fine and is they way I like it, so I will just keep it. On the reboot to recovery I tried that and got a different screen with mode off, mode on, etc but didn't see factory reset. Highlight was Mode Off and I moved up and selected mode on. Now when I try it boots up normally. Anyway I can set it back to Mode off like it was?
Thanks for your help!!
Click to expand...
Click to collapse
Same way you get into factory reset except instead of vol- you hold both volume buttons.

bichofelix said:
Also, have you started a github for this device, yet?
Click to expand...
Click to collapse
Only for recovery our device is e2nam I won't push a full device tree until I'm booting cyanogenmod
https://github.com/Teamregular

bichofelix said:
Same way you get into factory reset except instead of vol- you hold both volume buttons.
Click to expand...
Click to collapse
Ok got it and I think it may have just been me doing something wrong. Got home from work and tried it way you described a few posts back and I booted into TWRP. It's working Thanks

[Q] XT1039 bootloop and can't get adb to pull files

Hi,
all of a sudden, my XT1039 Moto G has entered a never ending bootloop that goes like this:
- powers up, motorola animation runs fine
- if the sim is inserted, it lets me tap the numbers for 5 seconds, then it soft reboots by itself
- if the sim is not inserted, it loads fine, it lets me do what I can do in 5 seconds, then it soft reboots by itself
my XT1039 is totally stock, unrooted, the last app I've installed is a flashlight app from the Google App Store, to turn on and off the back led, three days ago, and has been working fine for three days since then.
What I have done so far:
- booted android to safe mode: 5 seconds, and it bootloops again
- booted to recovery and wiped the cache partition, rebooted to android and the problem is still there
- when powered off, held the vol up and down buttons for two minutes: somebody wrote it worked for him, it doesn't work for me
- tried all the other options on the recovery menu (Factory, BP Tools, QCOM), but they all seem to do nothing, and get me again to the bootlooping
- booted to flashboot with an otg cable and a usb pendrive, hoping a magic "backup to usb" option would show up, but it doesn't
- disconnected the battery for 5 minutes, and replaced it with a known good working one out my wife's XT1032 (same battery model), still no luck
now I'm almost ready to boot to recovery and wipe data/factory reset, but I still would like to copy the Pictures folder out of the device first, so I tried with adb:
- installed the Motorola (and the universal too) drivers on my Win 8.1 and downloaded a recent version of adb.exe (Android Debug Bridge version 1.0.32)
- during the 5 seconds of bootloop life, I can browse the XT1039 folders from Win 8.1 explorer, but 5 seconds is too short to do anything
- booted the XT1039 in flashboot, but the command adb devices doesn't see my device
- while in flasboot, navigated in Recovery --> Apply Update from ADB, the Win 8.1 alerts me there's something new on the USB chain, and adb devices says:
List of devices attached
TA98601*** sideload
but in the sideload mode it seems I can't run the pull command to get my files out of the damned device, every command like adb pull, push, shell, returns the same error:
error: closed
Is there anything else I can try to get my files out of the XT1039, before restoring it to factory ?
Any hint is highly appeciated, thanks

I can see that you were able to boot into recovery, and assuming that you are using a recent version of TWRP, you can attach the device to a computer via USB while in TWRP. and copy the pictures folder that way.
Hope this helps
Edit: It sound like you were using the stock recovery, so boot into fastboot mode and flash the recovery with instructions from here.

Professor Gibbins said:
I can see that you were able to boot into recovery, and assuming that you are using a recent version of TWRP, you can attach the device to a computer via USB while in TWRP. and copy the pictures folder that way.
Hope this helps
Edit: It sound like you were using the stock recovery, so boot into fastboot mode and flash the recovery with instructions from here.
Click to expand...
Click to collapse
You can't install TWRP with a locked bootloader, and unlocking the bootloader wipes data...

Of course. It never actually occurred to me that the bootloader would be locked.
Although, have you tried running
Code:
adb kill-server
adb start-server
and trying the 'adb pull' commands again?

Professor Gibbins said:
Of course. It never actually occurred to me that the bootloader would be locked.
Although, have you tried running
Code:
adb kill-server
adb start-server
and trying the 'adb pull' commands again?
Click to expand...
Click to collapse
Yes, unfortunately the bootloader is locked, the phone is stock as if just bought out of a shop.
Here's the sequence of commands ran while in fastboot
C:\adb>adb kill-server
* server not running *
C:\adb>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>adb devices
C:\adb>adb pull /system/app/Settings.apk
error: device not found
and the here's the sequence of commands ran in fastboot-->recovery --> apply update from ADB (the only option I've found that seems to enable some adb functionality)
C:\adb>adb kill-server
C:\adb>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>adb devices
List of devices attached
TA98601*** sideload
C:\adb>adb pull /system/app/Settings.apk
error: closed

adb newbie needs help

I unlocked my bootloader successfully, & TWRP for my U11 (ocnwhl), & sideloaded (following RootJunky's video) Magisk; but did not achieve root.
l also find that TWRP has a hair trigger, & on my old Galaxy S4, on boot up, I got 10 seconds to choose Recovery or Boot. This has 5 seconds for choosing mode & hitting Power button to enter & I am all too often not fast enough. I did manage to get a backup of my stock system w/TWRP, but if there is a way to suspend the 5seconds, & have a moment to choose if I want to go into Recovery, Bootloader, etc. I'd be quite grateful to find out about it.
Also, I have a mysterious msg, that I copied & will paste here & I'd be equally appreciative to get an explanation; I have a couple of days experience w./htc twrp-ing & next to none w/adb- I'd love know what the numbers associated w/the client & server are referring to & what I need to do about it. When I do adb devices I get the following:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
adb server version (31) doesn't match this client (36); killing...
* daemon started successfully *
FAxxxxxxxxx device
So it seems that adb sees my U11 just fine; but, I'm concerned about the msg about the numbers, even if it does show device & my serial number & I got a backup of my stock sysgtem..
Also, I installed Magisk 13.3 & I don't seem to have Root, Titanium Root & Root Checker don't seem to show root either. Perplexed.
I saw up here a comment Unlock Bootloader, load TWRP, & Magisk & profit.
All help much appreciated, TIA, oldwolf

oldwolf613 said:
I unlocked my bootloader successfully, & TWRP for my U11 (ocnwhl), & sideloaded (following RootJunky's video) Magisk; but did not achieve root.
l also find that TWRP has a hair trigger, & on my old Galaxy S4, on boot up, I got 10 seconds to choose Recovery or Boot. This has 5 seconds for choosing mode & hitting Power button to enter & I am all too often not fast enough. I did manage to get a backup of my stock system w/TWRP, but if there is a way to suspend the 5seconds, & have a moment to choose if I want to go into Recovery, Bootloader, etc. I'd be quite grateful to find out about it.
Also, I have a mysterious msg, that I copied & will paste here & I'd be equally appreciative to get an explanation; I have a couple of days experience w./htc twrp-ing & next to none w/adb- I'd love know what the numbers associated w/the client & server are referring to & what I need to do about it. When I do adb devices I get the following:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
adb server version (31) doesn't match this client (36); killing...
* daemon started successfully *
FAxxxxxxxxx device
So it seems that adb sees my U11 just fine; but, I'm concerned about the msg about the numbers, even if it does show device & my serial number & I got a backup of my stock sysgtem..
Also, I installed Magisk 13.3 & I don't seem to have Root, Titanium Root & Root Checker don't seem to show root either. Perplexed.
I saw up here a comment Unlock Bootloader, load TWRP, & Magisk & profit.
All help much appreciated, TIA, oldwolf
Click to expand...
Click to collapse
Sideloading is not necessary, just copy the magisk zip to device & choose install from twrp main menu
Your adb may need to be updated
Sent from my unknown using XDA Labs

Uninstall HTC Sync from computer

[GUIDE] Installing the lastest LineageOS 15.1 Official (and microg fork)

I managed to install it, it got really tricky. The thing is that the new Lineageos releases somehow fail the verification on twrp and the old lineageos recovery. I found out after hours of investigating that you need the *new* Lineageos recovery to flash the new lineageos. I know, it's pretty absurd.
I extracted the boot.img from lineage-15.1-20180724-nightly-tissot-signed.zip extracting the payload.bin from the zip and using this tool https://androidfilehost.com/?fid=818070582850510260.
You can download the boot.img I extracted myself here: https://drive.google.com/file/d/1QftMHTXrINAOfr3Pcaqyux9nHRnGTnKl/view?usp=sharing
Put the phone on fastboot mode, connect via usb and type:
Code:
fastboot boot boot.img
while pressing the volume-up button to enter the Lineageos recovery.
From there do a factory reset, wipe system, and now you can flash lineage-15.1-20180724-nightly-tissot-signed.zip.
To flash it, it gets tricky. First of all you can't flash from the sdcard because it shows up an error. So you go to update, and press install from ADB or something like that. Now you have the phone on adb sideload mode.
Download https://developer.android.com/studio/releases/platform-tools. Adb from XDA's "Minimal ADB and Fastboot" doesn't work for some reason.
Unzip the file, open a command prompt on that folder and type:
Code:
adb devices
It has to show up as something like this:
Code:
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
xxxxxxxxxxx sideload
Where xxxxxxx is the phone id.
Then you can proceed to flash. Just type:
Code:
adb sideload lineage-15.1-20180724-nightly-tissot-signed.zip
Wait until it completes, it seems to freeze at 50% or so but wait some minutes until the progress bar on the recovery finishes and reboot.
Now you should be booting lineageos and set up it as usual. I hope this guide helped, took me some hours to figure it all out.
To install su addon, download it from https://mirrorbits.lineageos.org/su/20180718/addonsu-15.1-arm64-signed.zip, place the zip in your internal storage, download this recovery https://basketbuild.com/filedl/devs...ewolf/Recovery/tissot/twrp-3.2.2-1-tissot.img (thx nicknitewolf) and boot it via fastboot:
Code:
fastboot boot twrp-3.2.2-1-tissot.img
From there flash the su addon as usual and enjoy. Probably this method works also for opengapps/mindthegapps, i didn't have time to test it.

Rather, just use Abhishek's recovery image and twrp (V3.2.3) installer zip and get the job done.

Once you've installed the official LineageOS 15.1: Can you then update your system from Settings -> System -> About phone -> LineageOS updates without needing to ever flash something from TWRP again?

Enable USB Debugging in Recovery Mode

Hi,
during the update the phone got stuck, daughter restarted couple of times but it always got to the 76%, hang there and then restarted itself in the endless loop.
I've tried the the hard reset (Power+VolUP) and it got to the screen saying "No Command". Then I pressed the same combo again to get to the bootloader and tried the wipe / reset. During that process I got the error message "E: Can't send SPI message. Try again" and then it said it was successful, but rebooting did nothing, got stuck in the restart loop.
So I've done the research and wanted to to upload the OTA update, have done that but that didn't do anything.
So I've found some articles on how to upload the stock rom/image but I'm unable to do so as sending adb commands is disabled due to the phone being LOCKED. I've learned that the USB debugging needs to be enabled, however I'm unable to get into the OS to set it up, so found this article:
How to enable USB Debugging in Android using recovery mode?
One million questions, Is it possible to Enable USB Debugging in Android Using Recovery Mode or any other technique? Well, the answer is Yes! It is now
www.isrgrajan.com
which outlines the following steps (in summary):
Download the Stock ROM for your device- Google it, I am dam sure you can find it. [DONE]
Download SuperSU from UPDATE-SuperSU-v1.65.zip [DONE][looks pretty old though]
Steps to Enable USB Debugging Using Recovery Mode
Unzip the stock ROM. [DONE]
Within the extracted folder, you will find the system.img well extract it too using Ext4 Unpacker [DONE but plenty of folder are empty, but eventually plentu of APK along]
Also, extract the Update-SuperSU.v1.65.zip file. [DONE, again, looks pretty old]
Now open the folder where you have extracted the system.img files [DONE]
Grab any .apk file from this folder and change the extension from .apk to .zip [PROBLEM: the apks are all over the shop. Which APK shall I pick up?]
And Copy the RSA Certificated to the Update-SuperSU.v1.65 folder (delete previous files if exist) [PROBLEM: unable to find any "RSA Certificated" like files once I open ANY apk]
Also, copy the build.prop to the system folder located within Update-SuperSU.v1.65 folder [BLOCKED by previous step]
Locate the update-script file within this folder and edit it using Notepad++ [BLOCKED by previous step]
You need to update the build.prop file after adding the following line at the bottom [BLOCKED by previous step]
persist.service.adb.enable=1
Next step is updating SQLite Database [WHERE would I do this step?]
Which can be done by adding the following code to the update-script file
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "UPDATE global SET value=1 WHERE name='adb_enabled'"
What would I do then? How to actually apply the changes back to the phone?
Does anyone know of better / latest step by step process of enabling / unlocking the device or is my device now completely and unrepairably bricked?
Thank you.

Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com

jwoegerbauer said:
https://gist.github.com/varhub/7b9555cdd1e5ad785ffde2300fcfd0bd
Click to expand...
Click to collapse
For a while (since when, I don't know) persistent properties are not shared as individual files in /data/property.
They are all packed inside /data/property/persistent_properties.
Try setprop instead.

jwoegerbauer said:
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Click to expand...
Click to collapse
will give it a go. thank you.

jwoegerbauer said:
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Click to expand...
Click to collapse
I've tried the steps but I'm crashing on sending any commands to the device. While I'm in the recovery, I see the following details and options:
```
Android Recovery
google/blueline/blueline
12/SP1A.210812.016.B2/8602260
user/release-keys
Use volume up/down and power
Warning: Previous installation has failed. Your device may fail to boot if you reboot or power off now
- Reboot system now
- Reboot to bootloader
- Enter Fastboot
- Apply Update from ADB
- Apply update from SD card
- Wipe data/factory reset
- Mount /system
- View recovery logs
- Run Graphics Test
- Run Locale Test
- Power Off
```
where I run the adb command:
`adb shell mount data` I get the `adb.exe: no devices/emulators found`.
when I go to the `Apply update from ADB` and run the command above I get `error: closed`.
Basically I'm unable to run any adb commands as of the first message, and the only place I can it's from within the update. I've noticed that while in the 'Update via ADB', then in the Win Device Manager I can see that the driver is changed to `Android Composite ADB Interface` and only now it's accepting very limited commands. `adb devices` command generates: `<device id number>: sideload`.
When in the fastboot, it switches to `Android Bootloader Interface` in the DEvice manager.
When in recovery, the device is disconnected from the computer. (is not listed in the device manager)
any thoughts. thanks
Note: that phone was never rooted.
Bootloader looks like this at the moment:
```
Fastboot Mode
Product revision: blueline MP1.0(ROW)
Bootloader version: b1c1-0.4-7617406
Basebandversion...
serial number:
secure booth: PRODUCTION
NOS Production: yes
DRAM: 4GB
Device State: Locked
Boot slot: a
```

vajnorcan said:
I've tried the steps but I'm crashing on sending any commands to the device. While I'm in the recovery, I see the following details and options:
```
Android Recovery
google/blueline/blueline
12/SP1A.210812.016.B2/8602260
user/release-keys
Use volume up/down and power
Warning: Previous installation has failed. Your device may fail to boot if you reboot or power off now
- Reboot system now
- Reboot to bootloader
- Enter Fastboot
- Apply Update from ADB
- Apply update from SD card
- Wipe data/factory reset
- Mount /system
- View recovery logs
- Run Graphics Test
- Run Locale Test
- Power Off
```
where I run the adb command:
`adb shell mount data` I get the `adb.exe: no devices/emulators found`.
when I go to the `Apply update from ADB` and run the command above I get `error: closed`.
Basically I'm unable to run any adb commands as of the first message, and the only place I can it's from within the update. I've noticed that while in the 'Update via ADB', then in the Win Device Manager I can see that the driver is changed to `Android Composite ADB Interface` and only now it's accepting very limited commands. `adb devices` command generates: `<device id number>: sideload`.
When in the fastboot, it switches to `Android Bootloader Interface` in the DEvice manager.
When in recovery, the device is disconnected from the computer. (is not listed in the device manager)
any thoughts. thanks
Note: that phone was never rooted.
Bootloader looks like this at the moment:
```
Fastboot Mode
Product revision: blueline MP1.0(ROW)
Bootloader version: b1c1-0.4-7617406
Basebandversion...
serial number:
secure booth: PRODUCTION
NOS Production: yes
DRAM: 4GB
Device State: Locked
Boot slot: a
```
Click to expand...
Click to collapse
On my pixel3, /dev/block/dm-4 is mounted to /data. Try "adb shell mount /dev/block/dm-4 /data".
The instructions you are following are very old, and likely obsolete. SuperSu is also obsolete. Try to find a newer method.

dcarvil said:
On my pixel3, /dev/block/dm-4 is mounted to /data. Try "adb shell mount /dev/block/dm-4 /data".
The instructions you are following are very old, and likely obsolete. SuperSu is also obsolete. Try to find a newer method.
Click to expand...
Click to collapse
the issue is I'm unable to run that command `adb shell mount...` with the `no devices/emulator found` message. I believe it's because the device is not even listed in the device manager (windows) when in recovery mode. When in the update mode, then it's listed in the DM. See my post above, I've updated it few times. Thanks
Btw on that link if you check the posts there are newer ones (1.5y back) claiming it works so might actually work

If you're unable to sideload the OTA via PC, I don't think there's any other option besides paying for a repair, or replacing the device. A locked bootloader definitely makes recovery a lot harder.

V0latyle said:
If you're unable to sideload the OTA via PC, I don't think there's any other option besides paying for a repair, or replacing the device. A locked bootloader definitely makes recovery a lot harder.
Click to expand...
Click to collapse
I'm able to sideload the OTA, but restart goes into start being stuck and back and forth but never gets any further than the first google load screen

vajnorcan said:
I'm able to sideload the OTA, but restart goes into start being stuck and back and forth but never gets any further than the first google load screen
Click to expand...
Click to collapse
Were you using adb/fastboot before this happened? Was the device recognised then? If not, are you sure you have the right drivers?

AlexKarimov said:
Were you using adb/fastboot before this happened? Was the device recognised then? If not, are you sure you have the right drivers?
Click to expand...
Click to collapse
I've used the adb to upload the ota and that went, according the message ok, but the system won't start up. Device is recognized only when I choose the "Apply update from ADB" option in recovery mode. The moment I choose it, it shows up as a device in device manager and "adb devices" lists it ok. In fastboot mode it does list it in device manager, but "adb devices" doesn't list it.
It's the latest driver

vajnorcan said:
I've used the adb to upload the ota and that went, according the message ok, but the system won't start up. Device is recognized only when I choose the "Apply update from ADB" option in recovery mode. The moment I choose it, it shows up as a device in device manager and "adb devices" lists it ok. In fastboot mode it does list it in device manager, but "adb devices" doesn't list it.
It's the latest driver
Click to expand...
Click to collapse
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website

AlexKarimov said:
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website
Click to expand...
Click to collapse
This requires OEM Unlocking to be enabled so it won't be much help here.
Rescue Mode might work though.
@vajnorcan try this:
Boot to bootloader and select Rescue Mode using the volume buttons, then press Power to enter it.
On your PC, go to pixelrepair.withgoogle.com and connect the USB cable to your device. Select your carrier or select "Other" if device is unlocked.
I don't know whether this will actually work...I haven't heard of anyone using this tool to successfully recover.

AlexKarimov said:
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website
Click to expand...
Click to collapse
'fastboot devices' is reading the device, which is good. but trying the online flash tool fails due to the device being locked. :/

V0latyle said:
This requires OEM Unlocking to be enabled so it won't be much help here.
Rescue Mode might work though.
@vajnorcan try this:
Boot to bootloader and select Rescue Mode using the volume buttons, then press Power to enter it.
On your PC, go to pixelrepair.withgoogle.com and connect the USB cable to your device. Select your carrier or select "Other" if device is unlocked.
I don't know whether this will actually work...I haven't heard of anyone using this tool to successfully recover.
Click to expand...
Click to collapse
The google tool has found and connected to the device, but it ends up in an error (on the device) and saying "disconnected", looked promising, but not for long. thanks.