Database Develop

CM Recovery for Nexus Player (fugu)

This is the CM-12.1 recovery for fugu.
Use the bottom button to navigate. One push to scroll down and long press to select. I've tested both adb side load and install from internal storage. This recovery also supports adb backup, but I haven't tested it yet.
I hope you enjoy not having to fastboot everything.
Download: fugu_cm_recovery-20150418.img
To install just boot bootloader and
Code:
fastboot flash recovery fugu_cm_recovery.img

Dude, quit being so amazing. It's getting ridiculous.

Excellent! This is the first custom recovery available for this device, correct? I suppose this would open the door to something like the Xposed Framework being installed on the Nexus Player but since my device is running on Android 5.1, I'll probably wait until rovo89 officially adds support for the latest version of Android first.

Yes!!! Glad to see you!

@WugFresh

@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Dear Developers,
It has come to our attention that due to excessive ads that simulate download buttons, fly-by malware APK attacks from Mobogenie, and reused (and potentially dangerous) reused short URLs, Dev-Host no longer meets our minimum acceptable requirements as a hosting affiliate. As such, we are ending our affiliation with this provider. We urge you to find a safer download host for your development projects such as our other affiliates: Goo.im and AndroidFileHost.
Click to expand...
Click to collapse
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]

GabbyWC said:
Excellent! This is the first custom recovery available for this device, correct? I suppose this would open the door to something like the Xposed Framework being installed on the Nexus Player but since my device is running on Android 5.1, I'll probably wait until rovo89 officially adds support for the latest version of Android first.
Click to expand...
Click to collapse
Yes this is the first recovery for the device but last I checked Xsposed had nothing to do with recovery. This will allow for custom firmware like cm-12.1 to be flashed to the device without having to use fastboot.
---------- Post added at 03:27 AM ---------- Previous post was at 03:17 AM ----------
WugFresh said:
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
Click to expand...
Click to collapse
I have to agree with Wugfresh on this bro AndroidFileHost is great. All you need to do is @ the guy on Twitter and he'll hook you up with a developer account complete with ftp access.
Wugfresh the issue with a revision on this is it's cm's android bootable recovery so technically anytime a commit is made to that repo it would be a revision change.

I'll host the updated image somewhere else tonight and I will be adding the date to the end of the image so you can tell if it is updated.

bkjolly said:
Yes this is the first recovery for the device but last I checked Xsposed had nothing to do with recovery. This will allow for custom firmware like cm-12.1 to be flashed to the device without having to use fastboot.
Click to expand...
Click to collapse
The Q&A for Xposed on Android 5.0 at http://www.xda-developers.com/xposed-framework-for-android-lollipop-is-here/ contains this quote:
I want to install it. Now! What do I have to do?
Make sure that you’ve read my words above and you’re familiar with your phone’s internals. Obviously, you need to be on a Lollipop ROM and have a good backup of your data. For now, I will only publish the ARMv7 version. 64-bit is more complex, so let’s try the “easy” variant first.
For now, the installation has to be performed manually in a custom recovery. Flashing the zip file will install:
* app_process32_xposed and some symlinks
* libexposed_art.so
* libart.so and some related binaries + libraries (based on 5.0.2, enhanced with support for hooking etc.)
* XposedBridge.jar (now stored in /system/framework)
Backups of existing files will be created automatically and could be restored later.

Can confirm a working flash. Everything looks great! Thanks for all the hard work

no option to make a recovery image...whats the point of this then?
I tried to wipe my cache to free some space and it sent my nexus player into a bootloop...whats going on with this?

How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!

Edit

Noob
I'm a bit of a noob - I have managed to ADB a new boot and system image to my nexus player - it's now running lollipop1.6. What does this recovery mean and how is it different than loading a boot and system image? Thanks - Does this require ClockworkMod?
dhacker29 said:
I just got my Nexus Player last night and made a working version of CM recovery for it. Use the bottom button to navigate. One push to scroll down and long press to select. I've tested both adb side load and install from internal storage. This recovery also supports adb backup, but I haven't tested it yet.
I hope you enjoy not having to fastboot everything.
Download: fugu_cm_recovery.img - 8.41 MB
To install just boot bootloader and
Code:
fastboot flash recovery fugu_cm_recovery.img
Click to expand...
Click to collapse

OathYvne said:
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Click to expand...
Click to collapse
if you restored your backup you would be downgrading it from the update you just took. you dont need a custom recovery to back up apps and their data, there are apps for that. a custom recovery makes it so its easier to flash new/custom roms(os), make backups of the current rom(os) so if anything goes wrong you can restore it, flash zips like the supersu zip or xposed framework. if you try take an ota with a custom recovery the ota will fail to install as its looking for the stock recovery(may be diff on a nexus device but its always been like that on the devices i have owned)

OathYvne said:
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Click to expand...
Click to collapse
This recovery does not provide a "nandroid" type backup where all of your info is zipped up and stored on the devices internal storage, where any application can get access to it, but rather supports adb backup. which backs up your information to a file on your computer. See http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351 for more information on usage.

WugFresh said:
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
Click to expand...
Click to collapse
I swtiched to andriodfilehost and uploaded the latest version.

dhacker29 said:
I swtiched to andriodfilehost and uploaded the latest version.
Click to expand...
Click to collapse
Thanks for an update. I tried to full backup by following commands.
adb backup -apk -shared -all -f C:\backup20151904.ab
But getting this "Now unlock your device and confirm the backup operation" lines and asking for unlock your deivice to confirm. Any sugestion to pass this. Thanks

Yes it seems Google decided to remove the backup confirmation dialog from TcSettings

So it means adb backup of a full ROM is not possible? Going to try your rom later.
Sent from my Nexus 6 using Tapatalk 2

[CUSTOM RECOVERY] TWRP Recovery

DISCLAIMER
We are not responsible for any damage, bootloop, bricked or broken tablets and Relationships.
Team @csolanol & @diegocr is back!!!
Notice
This recovery can't be flashed to the tablet meanwhile the bootloader is locked. We don't have any way to unlock it for now so you must launch it this way:
Code:
fastboot boot TWRP_Fire_2.8.7.0_adb.img
Edit: Project became stable. Got rid of the backlight error thanks to @diegocr.
Download
https://www.androidfilehost.com/?fid=24269982087018181
Update 2015-12-14
MTP working, if doesn't mount disable and re-enable
Don't use USB storage, not working
Update 2015-12-13
Added adb & USB storage mount USB storage not working
XDA:DevDB Information
[CUSTOM RECOVERY] TWRP Recovery, Tool/Utility for the Amazon Fire
Contributors
csolanol, diegocr
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2015-11-09
Created 2015-11-06
Last Updated 2015-12-14

Video: 2015 Fire: Booting TWRP, Rooting, Installing Gapps
Basic Directions
Download/Install Drivers
Verify Divers were installed Correctly
Download/Install ADB/Fastboot files
Test Fastboot commands
Download Twrp.img from link in post #1
Boot Custom Recovery with
Code:
fastboot boot TWRP_Fire_recovery.img
check root status with https://play.google.com/store/apps/details?id=com.jrummyapps.rootchecker
This is a temporary recovery, it must be booted with fastboot commands, every time want to use it.
What you can do with a Custom Recovery
Root Stock rom with SuperSu.zip
Install Google Apps Select Arm | 5.1 | pico version
Install Xposed Framwork
Backup Rom
Install Custom ROM
Install Stock Firmware (UnBrick)
...

I know this sounds stupid but cant you sign your images by getting the amazon api key or something?

Awesomeslayerg said:
I know this sounds stupid but cant you sign your images by getting the amazon api key or something?
Click to expand...
Click to collapse
I don't think there is anyway to do that which is why signed software is generally trust-able.

bullet25 said:
I don't think there is anyway to do that which is why signed software is generally trust-able.
Click to expand...
Click to collapse
Well i've seen people using lg sign tool or something to sign there images to flash thier images and make them bootable.

keep up the great work now we just gotta get custom rom installed

Can Flashify be used to boot into the recovery?

niphoet said:
Can Flashify be used to boot into the recovery?
Click to expand...
Click to collapse
no, can not
Sent from my KFFOWI using Tapatalk

Hopefully we'll get custom roms soon... AOSP on a $50, quality, device would be awesome!

THANK YOU!!! Making a backup now! I don't know if this is important or not but when I started my backup, it showed the command screen, and the first line I saw there was in red, and said
Code:
[COLOR="Red"]E:Find_File: Error opening '/sys/class/backlight'[/COLOR]
again, don't know if it's a big deal or not but thanks again so glad I can now make a backup and to OTG USB thumb drive even!!! THANKS!!!!!!!!!!!

petermg said:
THANK YOU!!! Making a backup now! I don't know if this is important or not but when I started my backup, it showed the command screen, and the first line I saw there was in red, and said
Code:
[COLOR="Red"]E:Find_File: Error opening '/sys/class/backlight'[/COLOR]
again, don't know if it's a big deal or not but thanks again so glad I can now make a backup and to OTG USB thumb drive even!!! THANKS!!!!!!!!!!!
Click to expand...
Click to collapse
Just ignore that line.

Any Tom development started yet?

Awesomeslayerg said:
Any Tom development started yet?
Click to expand...
Click to collapse
Yes, however right now I'm just doing a highly customized, de-bloated, de-amazon'd, pre-rooted, stock based rom. I don't know if anyone is working on AOSP or CM based roms at the moment.

added video to post #2

Harry44 said:
Yes, however right now I'm just doing a highly customized, de-bloated, de-amazon'd, pre-rooted, stock based rom. I don't know if anyone is working on AOSP or CM based roms at the moment.
Click to expand...
Click to collapse
That sounds really great. I tried to make a deblooated rom, but I broke the settings application by accident. I guess I'll just wait until someone else releases theirs... :/

SD, I am trying to install TWRP as per the video. For some reason, my files look different then your and I am running Win 10. Any advice? Thanks much.
PS: When I get to the command prompt,, mine just opens up to my system, not the ADB folder....
EDIT: Ok, got it to go, don't know how, but it worked. Anyone else notice the device runs a little sluggish after this? Thanks!

hey since this is running lollipop amazon os. cany you guys make a costom rom like the hdx developers do that can be booted without unlocking the bootloader. they use safestrap which is like twrp but for locked bootloaders and install custom roms. they arnt fully custom they have amazon aspects that let it boot with the locked bootloader but it is almost fully custom the hdx has a nexus rom and a cm11 rom they made for it.

sandman512 said:
SD, I am trying to install TWRP as per the video. For some reason, my files look different then your and I am running Win 10. Any advice? Thanks much.
PS: When I get to the command prompt,, mine just opens up to my system, not the ADB folder....
EDIT: Ok, got it to go, don't know how, but it worked. Anyone else notice the device runs a little sluggish after this? Thanks!
Click to expand...
Click to collapse
Did you install Google apps zip?
It's not unusual for google services to slow down a device

sd_shadow said:
Did you install Google apps zip?
It's not unusual for google services to slow down a device
Click to expand...
Click to collapse
Thanks for the reply. Yes, did install the Google Apps Zip? Can that be uninstalled?

sandman512 said:
Thanks for the reply. Yes, did install the Google Apps Zip? Can that be uninstalled?
Click to expand...
Click to collapse
Not as easily as it they were installed.
Use a root file manager, to delete or rename or move.
Use titanium backup pro or similar app, to freeze google apps
you freeze all google apps, and see if performance improved, them unfreeze google apps one at a time to see which ones are causing issues.

[RECOVERY][UNLOCKED BL] TWRP 3.5.0_9-1

Code:
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
Prerequisites for Installation
- Must have an unlocked bootloader
Installation
- Use Flashify OR:
- Go into fastboot mode
- Install using the following command where <recovery-image> is the relevant file for your device
Code:
fastboot flash recovery <recovery-image>
*** Please do NOT create any mirrors ***
Downloads
All TWRP Builds for Apollo and Thor
Source Code
- Kernel Source
XDA:DevDB Information
TWRP, Tool/Utility for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
ggow
Version Information
Status: Stable
Stable Release Date: 2016-02-25

Many thank to your great work.
Can Flash it via Flashtify ?
Sent from my LG-D855 using XDA Free mobile app

NeverSmile said:
Many thank to your great work.
Can Flash it via Flashtify ?
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
Yes you can, as long as your bootloader is unlocked

I assume it's ok to flash this via TWRP 2.8.7.0 (to the recovery Partition of course)?

Cl4ncy said:
I assume it's ok to flash this via TWRP 2.8.7.0 (to the recovery Partition of course)?
Click to expand...
Click to collapse
Should be fine
Sent from my Nexus 6 using Tapatalk

ggow said:
Should be fine
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thanks, it worked fine.
The screenshot function still creates a 0 bytes file in Pictures\Screenshots though, which can be deleted via TWRP only.

Question:
First run after installation there was a page regarding the option to mount System as read-only with a checkbox whether that page should not re-appear. I did NOT enable (i.e. left it disabled) that checkbox, but I've not seen that page again (regardless if I re-booted into recovery via the extended shutdown menu, or by pressing Vol+&Power at start). Is that option somewhere in the settings? And is it to be considered a bug that the page did not re-appear?

Cl4ncy said:
Question:
First run after installation there was a page regarding the option to mount System as read-only with a checkbox whether that page should not re-appear. I did NOT enable (i.e. left it disabled) that checkbox, but I've not seen that page again (regardless if I re-booted into recovery via the extended shutdown menu, or by pressing Vol+&Power at start). Is that option somewhere in the settings? And is it to be considered a bug that the page did not re-appear?
Click to expand...
Click to collapse
It's not a bug, usually appears on first run only and should not impact TWRP's ongoing use.

NeverSmile said:
Many thank to your great work.
Can Flash it via Flashtify ?
Click to expand...
Click to collapse
ggow said:
Yes you can, as long as your bootloader is unlocked
Click to expand...
Click to collapse
Worked like a charm. Nice visual upgrade over 2.8.7.0. Summary of other changes here.

New Build is Up
- Dated 29 March 2016
- Fix slow performance especially when flashing open-gapps-6.x packages
- I would urge everyone to update their recovery partition before upgrading to future builds of CM-13.0

ggow said:
- Dated 29 March 2016
- Fix slow performance especially when flashing open-gapps-6.x packages
- I would urge everyone to update their recovery partition before upgrading to future builds of CM-13.0
Click to expand...
Click to collapse
Updated via Flashify on a pair of Thors; no issues.

Please help me. my hdx7 has locked bootloader. I made a mistake, flashed your TWRP3.0 .........Now, HDX7 cant work,cant connect computer ,cant in recovery.
only display "kindle fire". how can i repair it? plz.....

chaefei said:
Please help me. my hdx7 has locked bootloader. I made a mistake, flashed your TWRP3.0 .........Now, HDX7 cant work,cant connect computer ,cant in recovery.
only display "kindle fire". how can i repair it? plz.....
Click to expand...
Click to collapse
How did you attempt to flash TWRP (Safestrap, Flashify, FireFlash)? In the end it really doesn't matter. If your HDX won't progress past the gray Kindle Fire screen it is probably toast. Do you know what version of FireOS was last on the device (3.x, 4.x)?

Davey126 said:
How did you attempt to flash TWRP (Safestrap, Flashify, FireFlash)? In the end it really doesn't matter. If your HDX won't progress past the gray Kindle Fire screen it is probably toast. Do you know what version of FireOS was last on the device (3.x, 4.x)?
Click to expand...
Click to collapse
my hdx7 had been flashed twrp2.8, and flashed cm11. Today, I flashed cm12,but i found hdx7 cant work. So i think it maybe because twrp2.8 is old version.
i used twrp2.8 to flash new twrp3.0........

chaefei said:
my hdx7 had been flashed twrp2.8, and flashed cm11. Today, I flashed cm12,but i found hdx7 cant work. So i think it maybe because twrp2.8 is old version.
i used twrp2.8 to flash new twrp3.0........
Click to expand...
Click to collapse
You failed to read the documentation. CM12 also requires an unlocked bootloader as clearly stated in the OP. That's why it didn't flash with TWRP 2.8. There is no "maybe". Played with fire and got burned.
Since you had TWRP 2.8 installed the last version of FireOS was likely 3.1.x. There is an outside chance your device can be recovered following instructions in the following thread. Good luck.
http://forum.xda-developers.com/kin...-to-unbrick-kindle-fire-hdx-firmware-t3277197

Davey126 said:
You failed to read the documentation. CM12 also requires an unlocked bootloader as clearly stated in the OP. That's why it didn't flash with TWRP 2.8. There is no "maybe". Played with fire and got burned.
Since you had TWRP 2.8 installed the last version of FireOS was likely 3.1.x. There is an outside chance your device can be recovered following instructions in the following thread. Good luck.
http://forum.xda-developers.com/kin...-to-unbrick-kindle-fire-hdx-firmware-t3277197
Click to expand...
Click to collapse
thank you very much

chaefei said:
thank you very much
Click to expand...
Click to collapse
Before you try @Davey126's suggestion - assuming you're on Fire OS 3.1.x - you should just give the bootloader unlock a try. Zero risk, it either unlocks or fails.

Cl4ncy said:
Before you try @Davey126's suggestion - assuming you're on Fire OS 3.1.x - you should just give the bootloader unlock a try. Zero risk, it either unlocks or fails.
Click to expand...
Click to collapse
because my hdx7 is second-hand device，i don't know whether it is lock or not.
Before flashed twrp3.0 , it had been flashed twrp 2.8、 cm11. is it means unlock？

chaefei said:
because my hdx7 is second-hand device，i don't know whether it is lock or not.
Before flashed twrp3.0 , it had been flashed twrp 2.8、 cm11. is it means unlock？
Click to expand...
Click to collapse
Well, to be as clear as possible about this. You had the real TWRP installed, i.e. TWRP 2.8.7.0, NOT Safestrap based on TWRP?
If you had the real TWRP installed you were on Fire OS v3.1.x - v3.2.3.2, which are unlockable versions. Even with Safestrap v3.7x it could be worth a try to unlock.
Again: You can't mess up anything by trying. It either unlocks or fails. And you can try the one-click-solution. Be sure to grab the PDA drivers if you suffer from the good ol' device not found problem.

Cl4ncy said:
Well, to be as clear as possible about this. You had the real TWRP installed, i.e. TWRP 2.8.7.0, NOT Safestrap based on TWRP?
If you had the real TWRP installed you were on Fire OS v3.1.x - v3.2.3.2, which are unlockable versions. Even with Safestrap v3.7x it could be worth a try to unlock.
Again: You can't mess up anything by trying. It either unlocks or fails. And you can try the one-click-solution. Be sure to grab the PDA drivers if you suffer from the good ol' device not found problem.
Click to expand...
Click to collapse
thanks. i will try .
i want use fastboot method. But when i connect hdx to computer, the computer have nothing response.....

[ROM][UNOFFICIAL] LineageOS 15.1 for the Essential PH-1 (mata)

LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
It should go without saying, but do not lock your bootloader with this installed. You must be 100% stock, I'd suggest on both slots, in order to re-lock your bootloader. Doing otherwise will likely lead to a brick that Essential really shouldn't warranty.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Unofficial LineageOS Builds
Essential PH-1 (mata): https://updater.invisiblek.org/mata
Google apps
Google apps (opengapps nano) are baked in to these builds. This is due to the A/B partition layout and complications backing up/restoring gapps between builds. This is not ideal, and is the major road block to getting this device in to official status with Lineage. At this time I do not plan to release non-gapps builds. Users who require this will have to build their own.
Source
Device | Kernel
Here's a local_manifest for those who want to build at home.
Prerequisites
Unlocked bootloader
OPM1.180104.092 firmware - even if you were on this build, you should flash this firmware package to ensure the firmware is on BOTH slots.
Fastboot and ADB set up (use your google-fu to figure this out)
Installation
This device is different than what most people are familiar with due to the A/B partition layout. If you're familiar with Pixel devices, then you already know what this means. This thread isn't really designed to explain how it all works, that should be handled somewhere else. Instead, I'll assume you can either follow directions or do some research on your own. Additionally I have a discord set up where there are several people who may be able to help if you run in to a snag.
The initial install should go rather smooth, and future updates can be taken through the built-in Lineage updater app (yes, the are the seamless updates you may have heard about). Due to A/B, the recovery's ramdisk is actually on the boot.img partition (the rom's ramdisk is on the system partition now). What this means is once you flash the rom, it essentially (lol) replaces the TWRP that you have installed. This shouldn't be a problem since with the seamless updates, you shouldn't have to ever go into recovery. If you find yourself needing recovery, you'll have to re-flash TWRP to get there.
Phew, now some instructions.
See the prerequisites. You really do need these or things aren't going to work for you.
Boot into bootloader mode and wipe data with:
Code:
fastboot -w
Download twrp (mirror) and flash it with this command:
Code:
fastboot flash boot twrp-mata_11.img
(no, this isn't a typo, you are flashing twrp to the boot partition)
While still in bootloader mode, use vol down to select "Recovery mode" and hit the power button. This should boot you in to TWRP. Enter your previous lock screen password or pin (if it asks) to decrypt your data partition.
Put the device in sideload mode with:
Code:
adb shell twrp sideload
Install the zip via adb sideload with:
Code:
adb sideload <zip name here>
When finished, reboot.
Profit!
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][UNOFFICIAL] LineageOS 15.1 for the Essential PH-1 (mata), ROM for the Essential Phone
Contributors
invisiblek
Source Code: [url]https://github.com/LineageOS[/URL]
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2017-11-12
Last Updated 2017-11-11

Q: What is broken?
A: Nothing I'm aware of
Q: Can I use the stock Essential camera app?
A: Yes
Q: Does the 360 cam work?
A: No.
Q: Is this rooted?
A: No. You're on your own for that.
Q: Does this pass SafetyNet?
A: Yes. Android pay, Pokemon Go, etc work fine. If you root, depending on your root method, you may lose this ability. But the ROM itself does pass SafetyNet.
2017-11-20 FAQ rollup: https://forum.xda-developers.com/showpost.php?p=74580036&postcount=189
FAQ site with some more info (be gentle with the terrible, or should i say complete lack of, css)

"Why no work" bug reports incoming in 5,4,3,2,1....
EDIT: @invisiblek if you need this post for anything, let me know.

THANK YOU!! So glad to see this. Just ordered the essential yesterday.

Any known bugs? How is performance compared to stock? Thanks for this!

Install it and find out. It's a testing build.

Awesome! Mine will be here soon.. glad to see development!!
Sent from my Nexus 6 using Tapatalk

First time with an A/B device, so everytime you update with a new build to the updater site it will prompt us and begin updating in the background? Don't have to be specific with the process itself but I was just curious as I'd like to stay up to date as possible if I start the custom ROM endeavor since it's still early on in development. Thanks!

installing now.. OP the link to twrp is broken

Thanks OP!
Got it up and running, seems pretty solid for the first build. The initial setup wizard hung at the last step for me but after a reboot it worked.
Oh, and the night mode works great!
^TWRP link worked for me about 30 mins ago
Update: I have installed most all of my apps and have been playing around setting up the phone for the last ~30mins....no stutters, no mistouches, everything is working great. LTE+ on VZW works, as well as Verizon messaging app. The phone apk has the option for vvm, haven't tested. Overall I can't believe how well this runs...ROM development has come a long way from the initial releases I'm used to on non nexus devices.

360 Camera doesn't work.....

CaptainElwood said:
Thanks OP!
Got it up and running, seems pretty solid for the first build. The initial setup wizard hung at the last step for me but after a reboot it worked.
Oh, and the night mode works great!
^TWRP link worked for me about 30 mins ago
Update: I have installed most all of my apps and have been playing around setting up the phone for the last ~30mins....no stutters, no mistouches, everything is working great. LTE+ on VZW works, as well as Verizon messaging app. The phone apk has the option for vvm, haven't tested. Overall I can't believe how well this runs...ROM development has come a long way from the initial releases I'm used to on non nexus devices.
Click to expand...
Click to collapse
Same feelings here. I really hope vvm works. Will test tomorrow... The ROM already kept me up tik now 3:09am
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
Also on vzw don't see LTE + though.

Has installing lineage fixed the low signal strength problem for those people that have been experiencing it?
Sent from my ONEPLUS A5000 using Tapatalk

Works great! Found a wifi bug
Following the instructions posted, wifi stops working after flashing twrp and rebooting back into LOS. I flashed addonsu-14.1-arm64-signed.zip to enable App access to root. It worked, but wifi is broken on reboot. It turns itself off immediately after turning on.
Replication steps:
1. Follow steps in OP.
2. Reboot to bootloader (adb reboot-bootloader)
3. Flash twrp_mata-6.img (fastboot flash boot twrp.img)
4. adb push addonsu-14.1-arm64.zip /sdcard/
5. Install .zip in TWRP
6. Reboot
Anybody else getting this issue? The only way I've been able to fix it is to re-flash LOS.
EDIT: Thanks to @bmg1001, this issue is resolved (for me at least) by using this build of TWRP... Sorry, I can't post links yet! Can someone link this please?
https:// drive.google. com/file/d/1Pp9Hep-EEGNHLl6I_ob7ugihpKfrAcWm/view?usp=sharing
Note that flashing this TWRP build will allow you to reboot to recovery at any time without having to reflash TWRP, as mentioned in the OP.

omvir said:
Has installing lineage fixed the low signal strength problem for those people that have been experiencing it?
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
My signal strength improved from 2 bars to 3 bars at home, but I'm not sure if the reception has improved or just the number of bars displayed at certain signal strengths..

back2you said:
360 Camera doesn't work.....
Click to expand...
Click to collapse
You betrayed Sony

TWRP DL link not working
tclaybor said:
Following the instructions posted, wifi stops working after flashing twrp and rebooting back into LOS. I flashed addonsu-14.1-arm64-signed.zip to enable App access to root. It worked, but wifi is broken on reboot. It turns itself off immediately after turning on.
Replication steps:
1. Follow steps in OP.
2. Reboot to bootloader (adb reboot-bootloader)
3. Flash twrp_mata-6.img (fastboot flash boot twrp.img)
4. adb push addonsu-14.1-arm64.zip /sdcard/
5. Install .zip in TWRP
6. Reboot
Anybody else getting this issue? The only way I've been able to fix it is to re-flash LOS.
EDIT: Thanks to @bmg1001, this issue is resolved (for me at least) by using this build of TWRP... Sorry, I can't post links yet! Can someone link this please?
https:// drive.google. com/file/d/1Pp9Hep-EEGNHLl6I_ob7ugihpKfrAcWm/view?usp=sharing
Note that flashing this TWRP build will allow you to reboot to recovery at any time without having to reflash TWRP, as mentioned in the OP.
Click to expand...
Click to collapse
Good Morning!
The URL for TWRP isn't working for me. I copy pasted it in chrome address bar. Could someone please kindly help? I'm drooling to get started!

makbomb said:
Good Morning!
The URL for TWRP isn't working for me. I copy pasted it in chrome address bar. Could someone please kindly help? I'm drooling to get started!
Click to expand...
Click to collapse
Go to the rooting guide and it's in there. Use the mirror
---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------
One thing I noticed is cell service is much weaker so far. In this same spot if my bedroom used to go from 99 to 103 dbm. Now it's at a118. Will monitor and report.
Shows 0 bars of service. Used to be 2-3

strictlyphat said:
Go to the rooting guide and it's in there. Use the mirror
Click to expand...
Click to collapse
Thanks, but it sounds like @tclaybor is using a different version, provided to him by @bmg1001 , since you'll see he was trying to link a google drive to that version?

makbomb said:
Thanks, but it sounds like @tclaybor is using a different version, provided to him by @bmg1001 , since you'll see he was trying to link a google drive to that version?
Click to expand...
Click to collapse
The one in bmg1001 thread worked. But have to click mirror.
---------- Post added at 02:54 PM ---------- Previous post was at 02:54 PM ----------
If u do get it installed let me know about signal. Mine taking big hit.

Unofficial Unofficial TWRP and Gsi Android 11 or 12(kinda)

Hi guys. First post here and I'm not around my files so it will be a straight forward guide with no downloads right now, you're smart, you know where to source them...
Ok first and foremost, Unlock your bootloader, Motorola makes it easy and there are good guides on this site to do that.
Once your bootloader is unlocked your going to look for an Unofficial TWRP package for the Lenovo K12 Pro... "What?", You say... Yep K12 Pro. Download it and jump over to your boot loader and flash it or just boot to it through fastboot and now you have a way to install root permanently, or not if you would rather not, but you have that option now.
Next find the lastest Magisk apk and get that joker installed using TWRP. Now reboot into system and everything should load up as normal BUT now you have root with TWRP recovery. I have did this at least 100 times since figuring it out and sometimes I do this with a fresh factory flash and sometimes I do this as is without even wiping user data before or after. I'm no expert and I don't care to lose my files so on the rare occasion that I do have a boot loop or soft brick, I get myself into recovery and flash ANY of the cebu firmwares and do it all over again...
Ok, so now we know how to get root and custom recovery... Next find an AB version of Gsi 11 or "borrow" the latest system.img from an Android 12 update or firmware image and open up fastboot again and flash only the system.image to the system partition. Wipe or don't wipe, up to how lucky you're feeling, and then reboot to system... 11 will take 2-3 minutes to boot the first time and I had nearly all functionality when it did. 12, well, that's a little different, it took 3-4 minutes to boot to the setup screen and then lagged like crazy BUT it eventually started downloading a few files it was missing and got better. I couldn't get my calls or messaging to work right but I could hear my phone ring but it never called the phone app to open and let me answer... Weird stuff BUT FYI 12 is a pretty nice to look at OS and maybe one of you guys can take this to the next level and get some true usefulness out of it. I know it's not very technical but when one of you true geniuses try it and get it worked out please feel free to post a true guide with proper instruction and proper terms.
That's all I got guys. Thanks for reading this and ALSO if anybody has a complete list of fastboot and adb commands for the g9 Power or the K12 Pro please share them with me. I've gotten better at getting around but I'm not near as good as if like to be.

Obligatory safety PSA:
The Lenovo K12 Pro is just the Moto G9 Power sold under a different name, however, there could be minor differences that could cause problems.
Also, while searching for this unofficial TWRP build, I only found it on websites like unofficialtwrp.com, and the like. I couldn't find one on XDA. I was unable to find the device tree, or the kernel sources used by this website anywhere on the internet, and as such, the TWRP images provided on such websites are literal blackboxes.
TWRP images created and shared on XDA can be trusted, the source code used to create the image is displayed on the posts of the images, and XDA itself is a trusted site.
Here is what the official TWRP team have to say on the matter:
Unofficial TWRP Downloads
Like the TWRP team say, it is up to you to flash these images or not, but be careful.

mistersmee said:
Obligatory safety PSA:
The Lenovo K12 Pro is just the Moto G9 Power sold under a different name, however, there could be minor differences that could cause problems.
Also, while searching for this unofficial TWRP build, I only found it on websites like unofficialtwrp.com, and the like. I couldn't find one on XDA. I was unable to find the device tree, or the kernel sources used by this website anywhere on the internet, and as such, the TWRP images provided on such websites are literal blackboxes.
TWRP images created and shared on XDA can be trusted, the source code used to create the image is displayed on the posts of the images, and XDA itself is a trusted site.
Here is what the official TWRP team have to say on the matter:
Unofficial TWRP Downloads
Like the TWRP team say, it is up to you to flash these images or not, but be careful.
Click to expand...
Click to collapse
Agreed, I posted as a proof of concept so people with more know how could improve upon. Use this at your own discretion and have fun in doing so.

Is there a way you could post a detailed, step by step instructions of this, please?
I've found the unofficial twrp, but haven't rooted a phone in over 2 years, so I'm a bit rusty, plus things have changed a lot these last couple years.
I'd really appreciate if you could take your time for that.
Thanks in advance.

I don't mind helping you out but I can't post publicly because the rules of the forum and the fact that it's unofficial. I'll get a guide wrote up and PM you. I've had no issues with my device at all but remember it is use at your own discretion.

Dauksza72 said:
I don't mind helping you out but I can't post publicly because the rules of the forum and the fact that it's unofficial. I'll get a guide wrote up and PM you. I've had no issues with my device at all but remember it is use at your own discretion.
Click to expand...
Click to collapse
That would be awesome mate!
I really appreciate that!
Thanks in advance.

Dauksza72 said:
I don't mind helping you out but I can't post publicly because the rules of the forum and the fact that it's unofficial. I'll get a guide wrote up and PM you. I've had no issues with my device at all but remember it is use at your own discretion.
Click to expand...
Click to collapse
I was able to boot into TWRP but when I flash Twrp.img to recovery it won't stick, I always had to do fastboot into recovery if I try to boot into recovery it just reboots back into system, also can't remove any junkware from system, it always gives me error when I tried to remove it using root browser, im still on stock

zfk110 said:
I was able to boot into TWRP but when I flash Twrp.img to recovery it won't stick, I always had to do fastboot into recovery if I try to boot into recovery it just reboots back into system, also can't remove any junkware from system, it always gives me error when I tried to remove it using root browser, im still on stock
Click to expand...
Click to collapse
Check out https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-2-cebu.4279917/
for TWRP.
As for removing junkware, as you may or may not know, dynamic partitions is a thing since Android 10. In it, the /system, /product and /vendor partitions have been subsumed under a /super partition. And Google has conveniently used a type of ext4 filesystem for that /super partition, that is read-only.
TL;DR: You cannot modify Android using any sort of "root browser" or inside TWRP, for that matter, anymore.
Off the top of my head, the only way you can remove "junkware" is through some Magisk modules, and even they might not even work.

There are three ways to debloat AFAIK:
Magisk - this is my preferred method. You either replace apks you want removed or empty the /product/etc/nondisable folder so they can be disabled. Takes minimal effort to figure out how to make modules and no scripting knowledge required.
Cross-flashing - you can flash retail software, often including modem firmware, to most Moto phones. The result is a clean system with no carrier junkware.
System R/W Scripts - this is the most nonsensical of the options(IMO), but this option exists if you look around and want to experiment. The big drawback here is that you have to redo everything after every update.

Dauksza72 said:
I don't mind helping you out but I can't post publicly because the rules of the forum and the fact that it's unofficial. I'll get a guide wrote up and PM you. I've had no issues with my device at all but remember it is use at your own discretion.
Click to expand...
Click to collapse
Hello. I know you're new and welcome. I just want you to know, being an unofficial twrp isn't necessarily bad by itself. It's that the sources can't be verified. Lots of devces don't have official TWRPs, yet still have a rockin development section with TWRP instructions, as long as it's shared on a trusted site (I only trust 1 other) and lists it's sources and, even then, it should have the warning. Lots of scam sites target root noobs, as you've probably noticed. I don't think sharing instructions would have been against the rules, but should include a warning to let people know it's a questionable twrp build and it poses a risk, but all of our phones are at risk anyway. We don't have to worry about it anymore though since we have an official and still we are at risk, just far less risk. It comes with the territory. On the other hand, I've been I've been doing this for a very long time with countless phones and I've never noticed any malicious activity on any on any of them.