Database Users

[RECOVERY]14/07/14[UNLOCK BL][ROOT][TWRPv2.7.1.0 V4 RELEASED!!][NVIDIA OTA SUPPORTED]

****DISCLAIMER****
I am not responsible if you device decides to soft brick/ hardbrick or flys out the window
Recovery Installation Instructions:
1. unlock bootloader. (Hold volume up and power button, using terminal type in 'fastboot oem unlock', follow on screen instructions, (***WARNING THIS WILL WIPE DATA PARTITION***)
2. While in bootloader type 'fastboot flash recovery recovery.img'
3. select boot into recovery!!
Recovery Access:
Access recovery in pc via terminal/cmd
Adb reboot recovery
Or within the device...
Terminal emulator
Su
Reboot recovery
Or download an app from playstore that will do the work and reboot into recovery...
TWRP Version 2.7.1.0 Released:
Fully Working
Current issues list:
0 Issues
How to report an issue:
Message me with the a detailed description of the issue.
Provide a log.
Issues reported without a log will be ignored.
Download Link: http://d-h.st/cqQ
Source: https://github.com/omnirom/android_bootable_recovery
Release Changelog:
V1:
- TWRP booting
- graphics fixed but touchscreen not working
V2:
- Touchscreen fixed
- USB Mounts fixed
- software keys fixed.
V3:
- Improve read and write speeds on both internal and external storage. (TWRP method of calculating backup, MB/s seems inaccurate, jumps around way too much) but backup is very very fast!
- Improve graphical user interface speed, very very smooth!
- When not using TWRP, lp-core (super battery saving core) will be active and used as its suppose to.
- Drastically reduce TWRP loading times.
V4:
- TWRP Updated to latest source, includes better method of calculating backup and restore (now shows files and percentage complete, also supports colour text etc etc)
- Updated recovery kernel so backup and restore shall be faster
- Fixed 180 degree upside down recovery, now shows correctly
- TWRP now supports Nvidia OTA (NOTE: Installing nvidias OTA on a modified system may provide FC, DO NOT INSTALL IF YOU HAVE XPOSED INSTALLED)
CWM has been discontinued as it is not fully functioning while TWRP is and has much more, advanced features.

Unlocking Bootloader & Rooting
the new rom 4.3 should not be difficult... Now that we have recovery...
Unlocking bootloader
1. Unlock the bootloader
Access bootloader by either from poweroff holding volume down and power keys... Or enable USB debugging via pc enter adb shell reboot bootloader
Once at bootloader type in terminal/cmd fastboot oem unlock and follow intructions till the end...
WARNING DEVICE WILL WIPE USERDATA(EVERYTHING)
Device is now unlocked
2. install recovery - steps above
3. Download supersu.zip from chainfires website
Install via recovery... (Android terminal, su, reboot recovery)
Navigate to Supersu.zip via volume up, down keys and powerbutton - http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
Root achieved yay
More indepth tutorial incoming

Shaky156 said:
would really help if everyone could but high level moderators for tegra note device thread
Click to expand...
Click to collapse
Thanks Shaky for the efforts.
I agree with Tegra having its own thread, especially since so many OEM outlets will be selling this tablet and other iterations, like the coming Phone version of the Tegra 114i SoC.

e8hffff said:
Thanks Shaky for the efforts.
I agree with Tegra having its own thread, especially since so many OEM outlets will be selling this tablet and other iterations, like the coming Phone version of the Tegra 114i SoC.
Click to expand...
Click to collapse
Pm'd a high mod, has put the device on internal request list so dudes pls do pm mods and request, if you dont ask you dont get
V2 is compiling right now will test and upload after breakfast inshallah and CWM shall be functioning normal as in Image wont be flipped upside down anymore

Link to OTA 4.3 Tegra Note 4
http://forum.xda-developers.com/showthread.php?p=48866058#post48866058

Dpuble post delete pls

OP Updated with link to v2, although image is flipped so its sitting correctly, the device resolution is somewhat not set correctly so the CWM recovery looks out of shape a little but this doesnt affect the functionality of CWM
Also OP updated with link to OTA in zip file format fully factory... ENjoy

Double post delete pls

Bricked my device so cannot continue any further yet...

do you have the source for your CWM recovery. would love to have it so that development can continue. Thanks

Tomsgt said:
do you have the source for your CWM recovery. would love to have it so that development can continue. Thanks
Click to expand...
Click to collapse
Switching from CWM to TWRP for alot of reasons so will release source for TWRP, CWM source can be found in Cyanogenmod github. Also replied to your PM

http://d-h.st/eU9 TWRP v1 Recovery test

Shaky156 said:
http://d-h.st/eU9 TWRP v1 Recovery test
Click to expand...
Click to collapse
this is still CWM recovery you must have linked the wrong file. LOL

Tomsgt said:
this is still CWM recovery you must have linked the wrong file. LOL
Click to expand...
Click to collapse
That is weird...
fresh compile test here is another TWRP test: http://d-h.st/Y9u
fastboot flash recovery recovery.img
allot it to boot into your Android OS
adb reboot recovery, (TWRP should boot)

Shaky156 said:
That is weird...
fresh compile test here is another TWRP test: http://d-h.st/Y9u
fastboot flash recovery recovery.img
allot it to boot into your Android OS
adb reboot recovery, (TWRP should boot)
Click to expand...
Click to collapse
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot fl
ash recovery TWRP-2-recovery.img
target reported max download size of 641728512 bytes
sending 'recovery' (8384 KB)...
OKAY [ 0.311s]
writing 'recovery'...
FAILED (remote: (InvalidSize))
finished. total time: 0.335s
FAILED (remote: (InvalidSize)) looks like the recovery partition is pretty small. didnt notice it the first time I flashed it. witch is probably why I am still on CWM. Note Stock recovery is 8192KB but this one fails every time.

Tomsgt said:
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot fl
ash recovery TWRP-2-recovery.img
target reported max download size of 641728512 bytes
sending 'recovery' (8384 KB)...
OKAY [ 0.311s]
writing 'recovery'...
FAILED (remote: (InvalidSize))
finished. total time: 0.335s
FAILED (remote: (InvalidSize)) looks like the recovery partition is pretty small. didnt notice it the first time I flashed it. witch is probably why I am still on CWM. Note Stock recovery is 8192KB but this one fails every time.
Click to expand...
Click to collapse
I knew something wasnt right on your end since i did compile TWRP and was 100% sure I did. Will upload something soon

Shaky156 said:
I knew something wasnt right on your end since i did compile TWRP and was 100% sure I did. Will upload something soon
Click to expand...
Click to collapse
Yeah ut took me a couple tries to finally notice that LOL

Tomsgt said:
Yeah ut took me a couple tries to finally notice that LOL
Click to expand...
Click to collapse
Something isnt right, I need more than 1 tester to test TWRP on their device as it could be a user error,

Shaky156 said:
Something isnt right, I need more than 1 tester to test TWRP on their device as it could be a user error,
Click to expand...
Click to collapse
Guess i can be your second tester. Ill try this when i get home today. My bootloader is already unlocked and im rooted.
Edit: I dont even have CWM loaded so this will be fresh attempt strait to TWRP

BKO Overdrive said:
Guess i can be your second tester. Ill try this when i get home today. My bootloader is already unlocked and im rooted.
Edit: I dont even have CWM loaded so this will be fresh attempt strait to TWRP
Click to expand...
Click to collapse
Dont attempt yet... wait for another release of TWRP

[GUIDE] Unlock Bootloader, Install Custom Recovery, and Root the Pixel C (2/4/2016)

The instructions in this guide are outdated and way more complicated than necessary. Once the official release of Android 7.0 Nougat becomes available/rooted, I will update the procedures in this thread. In the meantime, I recommend referencing this post along with the original instructions.
A massive shout out to @cheep5k8 for all the hard work he did in getting root and recovery working on the Pixel C. Please donate to him if you can. He deserves it.
Disclaimer: This will wipe your device. Backup anything important before you start. I mostly made this guide for selfish reasons. cheep5k8 has done a great job but some of the instructions are a little vague. I like being spoon fed and I wanted a resource to refer to in the future. You know the drill. If it breaks, not my problem. Post in the forums or hop onto the XDA IRC channel.
There may be more efficient ways to do this, but this will get you where you need to be. If you find any problems or have any suggestions, feel free to reply (BE VERY SPECIFIC WITH STEPS) and I will do my best to update the instructions.
Prerequisites:
ADB/Fastboot - Minimal ADB and Fastboot
ADB/Fastboot Drivers - I recommend using Wugfresh's Nexus Root Toolkit and using the full driver installation guide. Alternatively, you can install them yourself using the official Google Drivers (no installer)
An easy way to access the ADB prompt is to navigate to the directory that ADB is installed in, hold shift and right click inside the directory. This will give you an expanded right click menu that includes an option to "Open command window here." Select this option and a command prompt will open that is already in the ADB directory, saving you from having to do a bunch of cd nonsense. You can check to see if your device is recognized in ADB by typing "adb devices." If ADB and the driver are all working correctly, it should come back with something like "5A20001071 device." You can also check to make sure your device is recognized in fastboot by booting to the bootloader and typing "fastboot devices." It will show something similar.
Necessary Files:
Pixel C Recovery - Cheap5k8's Recovery -- NYCHitman's Recovery (newer)
Pixel C Root files - Download the XCeeD kernel, su.img, and SuperUser.apk
Copy these files to your directory that contains the ADB and Fastboot executables.
Device Prep:
Enable developer mode
Go to Settings > About tablet
Tap on Build Number 7 times until it says "You are now a developer"
Enable OEM Unlocking
Go to Settings > Developer options
Enable OEM Unlocking
Tap on Enable when a disclaimer pops up
Enable USB Debugging (ADB)
Go to Settings > Developer options
Enable USB debugging
Tap on OK when prompted with a disclaimer
If the ADB USB driver has been installed, you will see a popup that says "The computer's RSA key fingerprint is: xx:xx:xx:xx(blah blah)"
Check the box next to "Always allow from this computer"
Tap on OK
Unlock Bootloader:
Open ADB prompt (see prerequisites)
Input the following:
Code:
adb reboot-bootloader
The device will now boot into the bootloader and say
Code:
Waiting for fastboot command...
Input the following to unlock the bootloader:
Code:
fastboot flashing unlock
You will be prompted on the tablet screen with a warning about unlocking the bootloader.
Press the power button to unlock the bootloader.
The device will reboot and say "Bootloader is unlocked and OS verification is OFF. Device will continue booting in 30 seconds." You will also hear an audible beep. You will then see the green android with some spinny stuff. This is the userdata being formatted.
When complete, the device will boot back into the bootloader and say
Code:
Waiting for fastboot command...
Boot back into Android by inputting:
Code:
fastboot reboot
Your Pixel C will be reset, so you will need to re-enable USB debugging. Connect to your wireless network and then skip past everything else in the initial setup, as all of this setup info will be wiped again later on. Refer to the "Enable USB Debugging (ADB)" steps above to re-enable USB debugging.
Install Custom Recovery:
Open ADB prompt (see prerequisites)
Input the following:
Code:
adb reboot-bootloader
The device will now boot into the bootloader and say
Code:
Waiting for fastboot command...
With the Pixel C in the Fastboot bootloader and the recovery file in your ADB directory, input the following:
Code:
fastboot flash recovery (replace with custom recovery filename).img
Example:
Code:
C:\>fastboot flash recovery twrp-2.8.7.0-dragon-ryu-01082016-2.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
(bootloader) erasing flash
OKAY [ 0.054s]
sending 'recovery' (13760 KB)...
OKAY [ 0.349s]
writing 'recovery'...
(bootloader) writing flash
OKAY [ 0.375s]
finished. total time: 0.783s
Reboot into Recovery using the physical buttons. If you reboot the device back into Android, it will write over the custom recovery with the stock one. This will be fixed in the future.
Code:
Power + Volume down until screen turns off, keep pressing volume down to boot into Coreboot Bootloader. Navigate to Reboot into Android Recovery with volume down and then press power to select.
Install Root:
In TWRP, navigate to Wipe > Format Data
Type "yes" in the warning prompt and wait for the userdata partition to format. Again, this will wipe your tablet.
Press the Home button at the bottom when the format is complete
Navigate to Reboot > Bootloader to boot back into Fastboot
In the ADB prompt, flash the new kernel:
Code:
fastboot flash boot (replace with xCeeD kernel filename).img
Example:
Code:
C:\>fastboot flash boot xceed-kernel-google-dragon-02-01-2016-RC1.img
target reported max download size of 268435456 bytes
erasing 'boot'...
(bootloader) erasing flash
OKAY [ 0.064s]
sending 'boot' (6220 KB)...
OKAY [ 0.161s]
writing 'boot'...
(bootloader) writing flash
OKAY [ 0.197s]
finished. total time: 0.426s
Reboot into Android. The device may boot twice.
Code:
fastboot reboot
Reboot back into Recovery. Power + Volume down until screen turns off, keep pressing volume down to boot into Coreboot Bootloader. Navigate to Reboot into Android Recovery with volume down and then press power to select.
In TWRP, navigate to Mount and check only Data
In the ADB prompt move su.img to /data:
Code:
adb push su.img /data
Example:
Code:
C:\>adb push su.img /data
5677 KB/s (33554432 bytes in 5.772s)
In TWRP, navigate to Mount and uncheck Data
In TWRP, navigate to Reboot > System
Perform initial device setup
Once you are at the home launcher, re-enable USB debugging (Refer to Device Prep)
In the ADB prompt, install superuser.apk:
Code:
adb install Superuser.apk
Example:
Code:
C:\>adb install Superuser.apk
8612 KB/s (6227998 bytes in 0.706s)
pkg: /data/local/tmp/Superuser.apk
Success
Install Busybox from the Play Store: link
Congrats. You are now rooted (not in the Australian sense).

Big big thanks
Amazing, great job.

P.S. One thing to add, for those who bought SuperSU Pro, you can install that too from the Play Store instead of installing the APK, but at the moment, it will say that the su binary is outdated (because the xCeeD kernel comes with 2.66, but SuperSU is already at 2.67). There needs to be a somewhat better solution but it's a bit hard to come up with it.
xCeeD v1-RC4 will have SuperSU updated to 2.67, and I'm thinking of how to make it possible to flash the normal SuperSU ZIP in TWRP. I will probably modify TWRP in some way to make that possible.

Very good step by step, guide, I went through the same process myself yesterday, although without the benefit of your guide!
Just one additional suggestion I would make, especially for people who have already got things set up nicely on their device.
Before doing anything you can make a backup of your device data using adb.
I used the guide at - http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
Although you cannot guarantee everything will restore perfectly (I recommend that for important apps that have the capability - backup the settings manually and remember to copy them off the device), it certainly saved me a heck of a lot of time in putting things back exactly as they were before - and it is a lot quicker than letting google backup restore things.

Does this void the warranty?
Great job,anyway
Enviado desde mi Pixel C mediante Tapatalk

Cool, but you don't mind make put the video or pictured for guides.
Keep it up!!

there no show up wipe/ fromat data when I into in reboot into android recovery look like said no command

Scarfacez2007 said:
there no show up wipe/ fromat data when I into in reboot into android recovery look like said no command
Click to expand...
Click to collapse
Are you booting into TWRP recovery or the stock Android recovery?

I have unlocked and I was install install custom recovery that all
---------- Post added at 01:11 AM ---------- Previous post was at 12:21 AM ----------
I just installed trwp then I into on reboot into android recovery but still no command

Thank you for this in depth tutorial.. GREATLY appreciated..my C will be in tomorrow just in time for RC4! Hopefully all goes smooth with this. So no need to swipe fastboot fix in twrp??

Scarfacez2007 said:
I have unlocked and I was install install custom recovery that all
---------- Post added at 01:11 AM ---------- Previous post was at 12:21 AM ----------
I just installed trwp then I into on reboot into android recovery but still no command
Click to expand...
Click to collapse
I had that too after my first attempt, I reinstalled TWRP and it worked after the second flash.
There were no errors shown either time.

The same thing - no command, though the TWRP is installed. Re-installing doesn't help at all.
UPD Just managed to do this step by manually booting into recovery without booting the ui.

I updated the instructions saying to use the physical buttons to boot into recovery immediately after writing TWRP to flash. I believe this should mitigate the issue with the device overwriting the custom recovery before the kernel is flashed.

You don't mind guide put with the video or picture?

Scarfacez2007 said:
You don't mind guide put with the video or picture?
Click to expand...
Click to collapse
I have no plans to make a video or pictures.

Finally I got rooted about time!!!! thanks oRAirwolf!!!!

I just wondering I can download Xposed 6.0.1 on my pixel c?

Scarfacez2007 said:
I just wondering I can download Xposed 6.0.1 on my pixel c?
Click to expand...
Click to collapse
I have no idea. I would probably start a new thread in the Q&A section.

Scarfacez2007 said:
I just wondering I can download Xposed 6.0.1 on my pixel c?
Click to expand...
Click to collapse
Yep xposed works fine

How did you get download xposed with arm64 for Google Pixel C? where get it? you don't mind can find for me on link?

LG LGMS550 Stylo 2 Plus?

Just delete this if it's considered in the wrong place. If and when is the the Stylo 2 Plus getting its own forum and has anyone come up with an exploit for rooting this phone yet?

Hiya
Yes this is the wrong place. This is for the g stylo not the stylo 2 plus as can be seen in the name of the forum.
No there is not an exploit yet. Kingroot, kangoroot, one clove root, etc all do not work yet. Soon i would imagine
I even have trouble looking on the web for things because it seems we share a model number ms550 with the lg optimus m. Weird

You think my signature would say I probably know this. Granted, I haven't worked for them in a while, for XDA, even longer. I was talking to the mods of the forum, sorry, if I confused you.

Reserved

Root recovery and boot loader unlock have been achieved on the Gsm Variants . you can find the link if you look for it .
---------- Post added at 04:31 PM ---------- Previous post was at 04:14 PM ----------
mustangtim49 said:
You think my signature would say I probably know this. Granted, I haven't worked for them in a while, for XDA, even longer. I was talking to the mods of the forum, sorry, if I confused you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-stylo-2-plus-t3482169/page6

Remote: unknown command
Rmontoya83 said:
Root recovery and boot loader unlock have been achieved on the Gsm Variants . you can find the link if you look for it .
---------- Post added at 04:31 PM ---------- Previous post was at 04:14 PM ----------
http://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-stylo-2-plus-t3482169/page6
Click to expand...
Click to collapse
I am new here and I have also googled and searched extensively about this problem with no success.
C:\Users\Darin\Downloads\twrp>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.566s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.575s
I can't boot TWRP by command line or by recovery key sequence. I have flashed recovery with this TWRP image that I got directly from @messi2050 today, 1/18/2017. If I "adb reboot recovery", I get the Android crash screen - the android laying down, red triangle. My phone is a t-mobile stylo 2 plus K-550. I'm sure I followed every step in the process correctly. If there is another thread that addresses this problem, can you direct me to it please? I can't start my own thread because I'm too new, but the most relevant recent thread regarding this is locked. Yes I have rooted another phone before without a problem(Samsung). Thanks in advance for your help.

[email protected] said:
I am new here and I have also googled and searched extensively about this problem with no success.
C:\Users\Darin\Downloads\twrp>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.566s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.575s
I can't boot TWRP by command line or by recovery key sequence. I have flashed recovery with this TWRP image that I got directly from @messi2050 today, 1/18/2017. If I "adb reboot recovery", I get the Android crash screen - the android laying down, red triangle. My phone is a t-mobile stylo 2 plus K-550. I'm sure I followed every step in the process correctly. If there is another thread that addresses this problem, can you direct me to it please? I can't start my own thread because I'm too new, but the most relevant recent thread regarding this is locked. Yes I have rooted another phone before without a problem(Samsung). Thanks in advance for your help.
Click to expand...
Click to collapse
Install the android sdk tools with adb fastboot and drivers.
Click build number 5 times to unlock developer options
Enable usb debugging
Enable allow oem unlock
Navigate to the platform tools directory paste the recovery.img in that folder.
Hold shift key right click mouse in the said folder to open command window
Plug in the phone type adb devices
Should say lgsomthing
If it does adb reboot bootloader
Fastboot devices
Should say lg something
If it does fastboot oem unlock
Reboot the phone
Enable developer options again in the settings menu by clicking build number
Go back to command window put it back in boot loader screen type fastboot flash recovery recovery.img
Unplug phone Pull battery out once done hold vol down and power until you we the lg screen release power while holding vol down then re hold power again release both buttons
Select yes and yes to wipe phone.
Flash dm verify and super user zips
Click reboot recovery
Don't forget to format data type yes and prevail
Now click thanks!!! If I helped.

I followed all of these steps. Fastboot flash recovery recovery.img from the directory where the tools are. When I get to the part of pressing volume down, power, then releasing power, and pressing again, and releasing both this is what happens:
Factory data reset screen
Erase all user data & restore default settings?
No
Yes
I've already been through that and TWRP doesn't load if I pick Yes, it just wipes my phone data, fresh Android, start over.
Please help
Rmontoya83 said:
Install the android sdk tools with adb fastboot and drivers.
Click build number 5 times to unlock developer options
Enable usb debugging
Enable allow oem unlock
Navigate to the platform tools directory paste the recovery.img in that folder.
Hold shift key right click mouse in the said folder to open command window
Plug in the phone type adb devices
Should say lgsomthing
If it does adb reboot bootloader
Fastboot devices
Should say lg something
If it does fastboot oem unlock
Reboot the phone
Enable developer options again in the settings menu by clicking build number
Go back to command window put it back in boot loader screen type fastboot flash recovery recovery.img
Unplug phone Pull battery out once done hold vol down and power until you we the lg screen release power while holding vol down then re hold power again release both buttons
Select yes and yes to wipe phone.
Flash dm verify and super user zips
Click reboot recovery
Don't forget to format data type yes and prevail
Now click thanks!!! If I helped.
Click to expand...
Click to collapse

[email protected] said:
I followed all of these steps. Fastboot flash recovery recovery.img from the directory where the tools are. When I get to the part of pressing volume down, power, then releasing power, and pressing again, and releasing both this is what happens:
Factory data reset screen
Erase all user data & restore default settings?
No
Yes
I've already been through that and TWRP doesn't load if I pick Yes, it just wipes my phone data, fresh Android, start over.
Please help
Click to expand...
Click to collapse
Then Twrp didn't flash

Flashing
Rmontoya83 said:
Then Twrp didn't flash
Click to expand...
Click to collapse
Fastboot said it flashed successfully. It copies the file, says it's ok. I would think if it didn't flash, it would fail the fastboot flash command. So is my phone jacked? I've read about how Android can rewrite the recovery partition as a security measure, or disable flashing by other means. Some kind of added security possibly?
Why would it say OK when I flash recovery, but NOT actually flash it?

[email protected] said:
Fastboot said it flashed successfully. It copies the file, says it's ok. I would think if it didn't flash, it would fail the fastboot flash command. So is my phone jacked? I've read about how Android can rewrite the recovery partition as a security measure, or disable flashing by other means. Some kind of added security possibly?
Why would it say OK when I flash recovery, but NOT actually flash it?
Click to expand...
Click to collapse
What software version are you running?

[email protected] said:
I am new here and I have also googled and searched extensively about this problem with no success.
C:\Users\Darin\Downloads\twrp>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.566s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.575s
Wrong command your trying to boot twrp
The correct command is "fastboot flash recovery recovery.img"
Click to expand...
Click to collapse

It was something I found in another tutorial when I started trying other things, since the "fastboot flash recovery recovery.img" was not getting me past the standard Android recovery. I'm about to try the file you sent me last night. I'll let you know the result.
---------- Post added at 10:25 PM ---------- Previous post was at 10:13 PM ----------
Rmontoya83 said:
What software version are you running?
Click to expand...
Click to collapse
Android version 6.0.1
Android security patch level 2016-08-01
Kernel version 3.18.20
Windows 7 Pro x64
The recovery.img you sent also said it flashed, but I got to the same Android factory reset screen after the key press procedure (volume down, power, release power, repress power, release all)
Here's the latest:
C:\Users\Darin\Downloads\platform-tools-latest-windows\platform-tools>fastboot f
lash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (15518 KB)...
OKAY [ 0.495s]
writing 'recovery'...
OKAY [ 0.362s]
finished. total time: 0.865s

Once you boot into recovery, let the screen fully dim, do not touch it... once the screen is completely blacked out, turn it back on and all touch features will be up and running... and don't mess with the adoptable storage feature..migrating data.. because TWRP will not recognise any data if you have this enabled.

[email protected] said:
I am new here and I have also googled and searched extensively about this problem with no success.
C:\Users\Darin\Downloads\twrp>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.566s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.575s
I can't boot TWRP by command line or by recovery key sequence. I have flashed recovery with this TWRP image that I got directly from @messi2050 today, 1/18/2017. If I "adb reboot recovery", I get the Android crash screen - the android laying down, red triangle. My phone is a t-mobile stylo 2 plus K-550. I'm sure I followed every step in the process correctly. If there is another thread that addresses this problem, can you direct me to it please? I can't start my own thread because I'm too new, but the most relevant recent thread regarding this is locked. Yes I have rooted another phone before without a problem(Samsung). Thanks in advance for your help.
Click to expand...
Click to collapse
You have to push the ing to and directory. Fastboot push img
Sent from my LG-K550 using Tapatalk

[email protected] said:
Fastboot said it flashed successfully. It copies the file, says it's ok. I would think if it didn't flash, it would fail the fastboot flash command. So is my phone jacked? I've read about how Android can rewrite the recovery partition as a security measure, or disable flashing by other means. Some kind of added security possibly?
Why would it say OK when I flash recovery, but NOT actually flash it?
Click to expand...
Click to collapse
Are you on the newest firmware for that phone?
If you are downgrade that could be a fix to lock down the recovery

I have successfully enabled usbotg on the LG Stylo 2 plus who wants to know how I did it? Usbhost mode..mount
Usb pendrive-
Mouse
Usb hub
Keyboard...etc
They say LG STYLO 2 PLUS DOES NOT SUPPORT OTG...LIES....LIES....THEY JUST DISABLED IT...WHY?...WELL..
FOLLOW THESE STEPS TO ENABLE FULL OTG SUPPORT
1-in root explorer go to:
-/sys/devices/soc/78db000.usb/power_supply/usb/usb_otg and edit from =0 to 1save
then-/sys/devices/soc/78db000.usb/dpdm_pulldown_enable edit disabled to enable.. plug in otg cable..
Done

WoodEe23 said:
I have successfully enabled usbotg on the LG Stylo 2 plus who wants to know how I did it?
Click to expand...
Click to collapse
You enabled it by adding it to the build prop lol

Dig waaayyyy deeper ..like
/sys/devices/soc/78db000.usb/power_supply/usb/ scroll to usb_otg and edit it from disabled to enable.
Then /sys/devices/soc/78db000.usb/dpdm_pulldown_enable edit it to enabled..
VOILA!!!"PLUGIN OTG CABLE AND UR IN THERE LIKE SWIMWEAR

[TUTORIAL] Unbricking VNS-L21/VNS-L31

Hello everyone! I know there are a lot of threads and comments about unbricking your device but in order to get you on track quicker then anything else and point you to the right direction i`m writing this tutorial which i find is quite successfull. This tutorial was made basically on my personal experience and with the help of some advices and suggestions.
First of all there are some questions that you must ask and answer yourself in order to do everything correct:
1. Do i have unlocked bootloader and frp? If yes, continue reading. If no, read Important note 2!
1.1. Do i have access to stock/custom recovery? If yes then continue to read.
1.2 Do i have problems mounting partitions with Revolution Recovery? If yes, read Important note 1!
3. Do i have installed SDK Platform Tools (ABD and FASTBOOT)? If no then download from here (Always use the latest version!!!)
4. Do i have installed HiSuite? If no then download it from here.
Okey mate if all your answers are Yes then follow Guide 1!
5. If you think your device don`t have access to these then read and follow Guide 2!
For those of you with locked FRP you can check this website and see if it helps!
How to get into fastboot?
Variant 1
Hold down (VOL-) + POWER when connected to PC!
Variant 2
1.Start HiSuite.
Step 2 (Click for image preview)
Step 3 (Click for image preview)
Turn off your phone and then by holding down (VOL-) + POWER connect usb to the pc!
! Important note 1 !
If you can`t mount partitions then the thing you must do is go to Revolution Recovery then do as i say:
Wipe -> Advanced Wipe -> Select partitions one at a time! -> Repair or change file system -> Change file system -> F2FS -> Then go back -> Select EXT4 -> And voila u`re done!
! Important note 2 !
Okay easy way to find out is if you see warning screen about unlocked bootloader then it is unlocked so it is frp. If you go to fastboot and you see Bootloader: unlocked/frp: unlocked but you don`t see the warning screen then my friend u`re not unlocked! Quickly open up the console window connect to fastboot and type:
Code:
fastboot oem unlock <your unlock code here>
Easy, a?
GUIDE 1
First of all download these files in order to continue. (Place them somewhere easy to find! )
Recovery - Revolution Recovery NOUGAT
(I can guarantee you that this version works that`s why i used her in this tutorial! METICULUS was not working for me it doesn`t even started at first place.)
Stock OEM info - Download
Stock ROM - L21C432B130
1. Open up fastboot then flash Revolution Recovery from the zip.
Code:
fastboot flash recovery recovery_twrp.img
2. Start up Revolution Recovery by connecting your device to the PC and holding down (VOL +) + (VOL -) + POWER
3. Flash Stock OEM info from the zip via Revolution Recovery. Make sure when installing it the result was Successfull!!!
4. Remove usb cable from PC and Shutdown the device via Recovery and don`t plug the cable or start the phone!
4. Get your SD Card ready and plugged to the PC then Create a New Folder named "dload" in the root directory of the SD Card and paste update.app file in there!
How it should look in the Micro SD Card: dload -> update.app
5.Place the SD Card in the phone
6. Start the phone!
7. Okay logo is there showing up wait about 1 - 2 minutes and phone will be automatically starting to update from SD Card. When it is done it will restart the phone. Make sure at the moment when it does and screen goes black, hold down VOL UP!
8. Format data and cache!!! If you skip this part there will be a bootloop!
9. Voila. You got your device unbricked and aliveeeeeeee :highfive::highfive::highfive:
That was the easy part! If u`re unlucky enough for Guide 2 well my friend get some coffee and play some calming music list!
GUIDE 2 (When no one can help you but you :silly
First of all you should know that every case is different from one another but everything comes to one mission. Access to fastboot or access to custom recovery in order to unbrick. I will give you steps which I did when I bricked my device and I had no fastboot access, no access to stock or custom recovery, no erecovery access and no wi-fi upgrade.
So what I experienced?
You see logo but only that. Warning screen saying bootloader is unlocked. When you see warning screen u`ve got a choice what to do – Press to enter recovery, press to continue booting etc. None of that. When I was connecting the usb cable to the PC no detection at all. No working key combinations.
1. DRAIN BATTERY! REALLY. IT`S THAT SIMPLE. Leave the device on and put it in a shelf or something like that so you can`t see it and can`t touch it. 2-3-4-5 days. (I left mine for 2 weeks! :laugh The battery must be that empty that when you try to power it up only power icon shows up or nothing shows up at all.
2. When u`ve done with Step 1 get a laptop or a PC with freshly installed Windows or Linux.
3. Install SDK Platform Tools (ABD and FASTBOOT) the newest version from their website!
4. Install HiSuite from their respective website!
5. So now when you`re all done with installing the requisites get your phone in your hands plug the usb cable in the phone and then hold down (VOL -) + POWER when plugging it to the PC or laptop.
6. Believe me. It should get into fastboot. I`m 99% sure. If all the steps I wrote are done correct!
Why should battery be drained at ZERO?
I will tell you the truth – I don`t know. Really. But all I know is that it`s kind of a switch. When something goes wrong draining the battery will clear something that it shouldn’t be there.
If this tutorial helped you then click Thank you so i can count how many good things i`ve done in my life he he! If i didn`t helped you then don`t stop reading until you find the solution! Good luck!
How did you unbricked your device? Tell us here and help others do the same!

Is there a special reason why we should use a Nougat Recovery? I'm on C432B160 and have tried the change filesystem thing with METICULUS Recovery and well... it didn't work

Thank you!
Created an account just to say thanks for this! I've have spent hours and hours trying to unbrick my phone..

goretsov said:
Hello everyone! I know there are lot`s of threads and comments about unbricking your device but in order to get you on track quicker then anything else and point you to the right direction i`m writing this tutorial which i find is quite successfull.
First of all these are the questions that you must ask and answer yourself in order to do everything correct:
1. Do i have unlocked bootloader and frp? If yes, continue reading. If no, read Important note 2!
1.1. Do i have access to stock/custom recovery? If yes then continue!
1.2 Do i have problems mounting partitions with Revolution Recovery? If yes, read Important note 1!
Okey mate if all your answers are Yes then follow Guide 1!
2. If you think your device don`t have access to these then read and follow Guide 2!
! Important note 1 !
If you can`t mount partitions then the thing you must do is go to Revolution Recovery then do as i say:
Wipe -> Advanced Wipe -> Select partitions one at a time! -> Repair or change file system -> Change file system -> F2FS -> Then go back -> Select EXT4 -> And voila u`re done!
! Important note 2 !
Okay easy way to find out is if you see warning screen about unlocked bootloader then it is unlocked so it is frp. If you go to fastboot and you see Bootloader: unlocked/frp: unlocked but you don`t see the warning screen then my friend u`re not unlocked! Quickly open up the console window connect to fastboot and type:
Code:
fastboot oem unlock <your unlock code here>
Easy, a?
GUIDE 1
First of all download these files in order to continue. (Place them somewhere easy to find! )
Recovery - Revolution Recovery NOUGAT
Stock OEM info - Download
Stock ROM - L21C432B130
1. Open up fastboot then flash Revolution Recovery from the zip.
2. Start up Revolution Recovery by connecting your device to the PC and holding down (VOL +) + (VOL -) + POWER
3. Flash Stock OEM info from the zip via Revolution Recovery. Make sure when installing it the result was Successfull!!!
4. Remove usb cable from PC and Shutdown the device via Recovery and don`t plug the cable or start the phone!
4. Get your SD Card ready and plugged to the PC then Create a New Folder named "dload" in the root directory of the SD Card and paste Update.app file in there!
How it should look in the SD: SD CARD -> dload -> update.app
5.Place the SD Card in the phone
6. Start the phone!
7. Okay logo is there showing up wait about 1 - 2 minutes and phone will be automatically starting to update from SD Card. When it is done it will restart the phone. Make sure at the moment when it does and screen goes black, hold down VOL UP!
8. Wipe cache!!!
9. Format data!!!
10. Voila. You got your device unbricked and aliveeeeeeee :highfive::highfive::highfive:
That was the easy part! If u`re unlucky enough for Guide 2 well my friend get some coffee!
Guide 2 will come soon because my time is limited!
Click to expand...
Click to collapse
waiting for guide 2... :fingers-crossed:

I have installed LineageOS 14.1 on my device (VNS-L21C432) and I want stock android back, I don't have a dump backup, just a normal one.. Can I use your method to get stock? I have installed TWRP by Meticulous and bootloader unlocked. I really want to came back to stock!!
I appreciate any advice, please help!

Yes i believe so
wimsjohn said:
Is there a special reason why we should use a Nougat Recovery? I'm on C432B160 and have tried the change filesystem thing with METICULUS Recovery and well... it didn't work
Click to expand...
Click to collapse
Good question! The reason i told everyone to use there version and this custom recovery is because METICULUS is not working at least didn`t for me! It didn`t even started at first place! Nougat is preferable because a lot of people get in trouble when they upgrade to Nougat and then try to downgrade that`s one of the reasons too. So my advice is try Nougat custom recovery for your case! Good Luck and best wishes

dezzie81 said:
Created an account just to say thanks for this! I've have spent hours and hours trying to unbrick my phone..
Click to expand...
Click to collapse
You are welcome my friend! I know how tough it is to find a solution out there in this wild world!

MrSagace said:
I have installed LineageOS 14.1 on my device (VNS-L21C432) and I want stock android back, I don't have a dump backup, just a normal one.. Can I use your method to get stock? I have installed TWRP by Meticulous and bootloader unlocked. I really want to came back to stock!!
I appreciate any advice, please help!
Click to expand...
Click to collapse
Yes of course there will be no trouble at all but instead of METICULUS recovery use the one i posted here! You have access to fastboot and unlocked bootloader so just follow the steps from number 4! If this doesn`t work you can try to flash http://consumer.huawei.com/bg/support/products/downloads/detail/huawei-p9lite-bk.htm?id=93797 this rollback package and via the method with SD Card and then flash stock rom from the link above! :highfive:
Good luck and i`m waiting for the result! :highfive:

arleybarros said:
waiting for guide 2... :fingers-crossed:
Click to expand...
Click to collapse
Tomorrow i`m going to post it here so wait for update! I just have to put my ideas in some kind of order to be easy to understand! :highfive:

goretsov said:
Tomorrow i`m going to post it here so wait for update! I just have to put my ideas in some kind of order to be easy to understand! :highfive:
Click to expand...
Click to collapse
i think my micro sd was bad when i tried to update my phone and now i'm stuck in a boot loop with a data partition problem (it fails when i try to wipe data) and locked bootloader.

arleybarros said:
i think my micro sd was bad when i tried to update my phone and now i'm stuck in a boot loop with a data partition problem (it fails when i try to wipe data) and locked bootloader.
Click to expand...
Click to collapse
Okay. First of all buy a decent Micro SD Card at least 6gb of storage! This is one of the most important things i forgot to tell here. Decent means famous brand like Kingston or Philips or something like that because other then this will fail! After that do you have access to fastboot? If you have fastboot then type "fastboot oem unlock <your unlock code>" If you don`t know it i can help you with that! After that flash the recovery i posted and try to fix the partition by the way i explained above. Then follow the last steps for preparing the SD and flashing the ROM. Good Luck my friend:highfive:

goretsov said:
Okay. First of all buy a decent Micro SD Card at least 6gb of storage! This is one of the most important things i forgot to tell here. Decent means famous brand like Kingston or Philips or something like that because other then this will fail! After that do you have access to fastboot? If you have fastboot then type "fastboot oem unlock <your unlock code>" If you don`t know it i can help you with that! After that flash the recovery i posted and try to fix the partition by the way i explained above. Then follow the last steps for preparing the SD and flashing the ROM. Good Luck my friend:highfive:
Click to expand...
Click to collapse
I appreciate the help, but the phone is locked. Phone Locked and FRP lock. I already imagine that at this point I only have a nice paper weight.

arleybarros said:
I appreciate the help, but the phone is locked. Phone Locked and FRP lock. I already imagine that at this point I only have a nice paper weight.
Click to expand...
Click to collapse
No there is a way to unlock FRP. I will look and tell you more. Don`t worry :highfive:

goretsov said:
No there is a way to unlock FRP. I will look and tell you more. Don`t worry :highfive:
Click to expand...
Click to collapse
If you are talking about DC Unlocker, i tried and after the phone reboot i get that "reset failed" error...

arleybarros said:
If you are talking about DC Unlocker, i tried and after the phone reboot i get that "reset failed" error...
Click to expand...
Click to collapse
No this one is free. TODO Give it a try and tell what happened. It might detect you an virus or something like that which is normal i tried it myself a time ago. Tell later what happened

goretsov said:
No this one is free. TODO Give it a try and tell what happened. It might detect you an virus or something like that which is normal i tried it myself a time ago. Tell later what happened
Click to expand...
Click to collapse
HTML:
>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (35528 KB)...
OKAY [ 0.753s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.760s
fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (27434 KB)...
OKAY [ 0.581s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.587s

arleybarros said:
HTML:
>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (35528 KB)...
OKAY [ 0.753s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.760s
fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (27434 KB)...
OKAY [ 0.581s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.587s
Click to expand...
Click to collapse
Did you try TODO for the FRP?

goretsov said:
Did you try TODO for the FRP?
Click to expand...
Click to collapse
i think you sent the wrong link...

Check again i correct it

I´m facing the same poblem. Bootloop with Bootloader locked, FRP locked, battery empty. I can get into fastboot mode but no chance of flashing anything. USB debugging seems to be deactivated. I cant charge the battery because as soon as I connect the phone to a powersource its starts the bootloop. Force flashing via sd card (volume up and down plus power) doesn´t seem to work either (guess due to the low battery).
Any suggestions are much appreciated.
regards

problem with TWRP trying install dolby plus mod XT1926 unknown partition

first of all SORRY FOR MY BAD ENGLISH...( i gonna try keep text simple )(my mother tongue is portuguese)
i am experiencing problem trying to install a MOD (an lenovo apk with much better volume level and sound quality)
from this topic here
XDA thread : https://forum.xda-developers.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192
in order to install the dolby audio apk i must first unlock the bootloader(sucessfuly done) and then install TWRP
and here the problem begins...
i am using ubuntu 14.04 / windows 7 my model is the brazilian one the G6 PLUS XT1926-8 with the lastest android 9 pie ROM PPW29.116-16.
i ve tried install TWRP but no luck...
this is the log ...
[email protected]:/home/henrIque/Downloads/G6 PLUS XT1926# fastboot flash recovery twrp-3.2.3-0-evert.img
target reported max download size of 536870912 bytes sending 'recovery' (29252 KB)...
OKAY [ 0.923s] writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure) finished. total time: 0.924s
[email protected]:/home/henrique/Downloads/G6 PLUS XT1926# fastboot flash twrp-3.2.3-0-evert.img unknown partition 'twrp-3.2.3-0-evert.img'
error: cannot determine image filename for 'twrp-3.2.3-0-evert.img'
[email protected]:/home/henrique/Downloads/G6 PLUS XT1926# adb reboot bootloader error: device not found
Click to expand...
Click to collapse
ive tried flash the twrp 3.23 ...
if i type
[email protected]:/home/henrique/Downloads/G6 PLUS XT1926# fastboot flash twrp-3.2.3-0-evert.img
< waiting for device >
unknown partition 'twrp-3.2.3-0-evert.img'
Click to expand...
Click to collapse
it wont flash it gives an error of "unknown partition"
i think it s because my android system image is new... is the android pie 9... but i dont know.....
when i connect USB DEBUGING in ubuntu with android 9 ON (system running) and type in PC-DESKTOP command line "adb devices"
it returns me the number of my smartphone and "offline" like this
[email protected]:/home/henrique/Downloads/G6 PLUS XT1926# adb devices
List of devices attached
0050250836 offline
Click to expand...
Click to collapse
if i start the phone with power Button and volume key down pressed
it dont return ... nothing appears if i type "adb devices"
if change the PC operating system to windows 7 even if motorola drivers installed
nothing appears
[email protected]:/home/henrique/Downloads/G6 PLUS XT1926# adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Click to expand...
Click to collapse
devices attached appears with blank line
in windows 7 or the command line waits forever for the device or gives me a blank line in devices attached.
i looked in control painel and my device appears as "ADB ANDROID"
can somebody help me install the apk mod(dolby atmos plus) i mean the TWRP and magisk?
sorry if i posted in wrong section i am new here
THANKS IN ADVANCE!

UPDATE... IT SEEMS THAT I BRICKED MY PHONE(I THINK MAGISK CHANGED THE PARTITION OF BOOT)
WHEN I TURN ON THE PHONE, IT TRY TO BOOT FOREVER...LIKE BOOT LOOP.
WHEN I TRY BOOT IN RECOVERY MODE TWRP MENU APPEARS BUT I DONT WHAT TO DO TO HAVE MY PHONE WORKING PROPERLY....
LET ME EXPLAIN...
i solved the problem of not installing the TWRP by reading this topic here
https://forum.xda-developers.com/g6-plus/how-to/twrp-installer-zip-evert-t3875657
it seems that newer versions of TWRP cant be installed, instead i must type
"fastboot boot twrp-3.2.3-0-evert.img" and run it by the PC-DESKTOP.
but i saw another post saying this
segra246x said:
You can install TWRP on this device and it's very simple!
First boot TWRP via fastboot boot twrp.img and then flash the TWRP-Installer.zip in TWRP. This overwrites the stock recovery which is within the boot.img now for A/B devices. After that you have to flash the magisk.zip and it's done!
Just use Google to find twrp-installer.zip/evert
Click to expand...
Click to collapse
unfortunately the MOD APK dolby plus was flashed using TWRP but no app appeared when i started the android 9...
i installed twrp 3.2.1.zio(flashed with TWRP) after that i installed magisk v18.zip with TWRP.
i noticed that the internal partition of g6 plus was encrypted. and the partition of microSD CARD the TWRP reads perfect.
i entered in the android 9 pie system
i decided install and open the apk magisk manager 6
unselect the option "forceencrypt" and unselect the option "vdb verity mode"
the apk installed something and now my smartphone wont BOOT.
it is stuck on motorola logo in bootloop forever
when i try boot in recovery mode the TWRP menu appears but i dont know what to do to have my phone working properly again...
it seems that magisk changed the partition of boot...

UPDATE: PHONE WORKING WELL AGAIN...
Reading this topic
https://forum.xda-developers.com/g6-plus/how-to/3-how-to-install-root-aka-magisk-t3854244
i must type"fastboot flash boot boot.img"(the file boot.img from a stock ROM, I have the PPW29 116-16 ROM so i used it)
[email protected]:/home/henrique/Downloads/G6 PLUS XT1926# fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (22281 KB)...
OKAY [ 0.796s]
writing 'boot'...
OKAY [ 0.653s]
finished. total time: 1.450s
Click to expand...
Click to collapse
and then the phone worked well...
DOES ANYBODY HAVE SOME IDEIA FOR THE MOD SOUND? THE DOLBY PLUS APK DONT WORKED...
i want increase the volume sound without distorting the audio

I don't think Dolby is gonna help your volume problem more than the built in one, try flashing magisk and installing the viper4android module.