So I saw the articles and threads on 12/25 reporting do not Disturb until next alarm was gone. After noting mine was gone too I turned off my 6P and went back to using my Galaxy S6 for 2 days.
I turned my 6P back on to get a file off it last night and noticed do not disturb symbol was on the top status bar. I pulled the toggles down saw it was lit with 'alarms only' under it. I clicked the toggle and it does not turn off. I tried double clicking and tried holding down toggle. I Pressed the volume up button and I can change volume for alarms and media, but ring tone slider is faded out so I can't modify it.
Then I went into settings and confirmed in the notifications section that there is no do not disturb schedule turned on and no apps have access to do not disturb. I also could not turn it off from inside settings either. I did a quick Google search and found a thread on 12/23 and 12/14 of this being reported on Android Central. Before this until next alarm disappeared. Every thread has no resolution if there was one.
I tried clearing all user cache and rebooting but it's still turned on. I also booted into twrp and wiped cache in there. It still shows! So it seems to be something in the system. I am rooted (systemless) but completely stock 6.0.1. I's anyone else experiencing this or have any suggestions?
Try reflashing /system only? Or flash the factory image but remove the -w from near the end of the batch file to preserve your userdata. Then just flash TWRP and systemless root again, after verifying it's fixed, of course.
fury683 said:
Try reflashing /system only? Or flash the factory image but remove the -w from near the end of the batch file to preserve your userdata. Then just flash TWRP and systemless root again, after verifying it's fixed, of course.
Click to expand...
Click to collapse
Too bad I didn't do a nandroid backup till last night after this happened. So I was fearing what you said might be the only solution, to just flash back to stock image and root again. Any other suggestions to avoid that?
AndroidPurity said:
Too bad I didn't do a nandroid backup till last night after this happened. So I was fearing what you said might be the only solution, to just flash back to stock image and root again. Any other suggestions to avoid that?
Click to expand...
Click to collapse
If you don't wipe userdata (remove the -w flag as I described) you won't need a nandroid. All your apps will remain intact, if you remove the -w.
Download the factory image, unpack it, edit the flash-all.bat to REMOVE the -w from the file (it's near the end), save the batch file. Put your phone in bootloader mode, run the factory image as you would normally. When complete, you'll be on a fresh install with all your data. This of course assumes the issue is /system related not /data related.
You could still take a nandroid in hopes that you could flash fully clean (without modifying the batch file) and then restore /data only from the nandroid. You'd need to offload that backup somewhere though because it would get wiped with the factory image.
Also I forgot to mention if you are going to use a nandroid, make sure you remove any pin/password/lock before you make it. I believe if you leave it on there and restore it, it won't accept the pin/password/fingerprint.
fury683 said:
Also I forgot to mention if you are going to use a nandroid, make sure you remove any pin/password/lock before you make it. I believe if you leave it on there and restore it, it won't accept the pin/password/fingerprint.
Click to expand...
Click to collapse
The work around for a nandroid with lock screen security is to delete the file locksettings.db from data/system. Use the file manager in twrp to erase it. Then once booted go to lockscreen security and toggle between swipe and fingerprint. It will erase the saved ones and let you start over.
XxMORPHEOUSxX said:
The work around for a nandroid with lock screen security is to delete the file locksettings.db from data/system. Use the file manager in twrp to erase it. Then once booted go to lockscreen security and toggle between swipe and fingerprint. It will erase the saved ones and let you start over.
Click to expand...
Click to collapse
Thanks, I was not aware. I thought it was just FUBAR if you didn't remove it before making the backup.
fury683 said:
Also I forgot to mention if you are going to use a nandroid, make sure you remove any pin/password/lock before you make it. I believe if you leave it on there and restore it, it won't accept the pin/password/fingerprint.
Click to expand...
Click to collapse
Haha good thing I didn't attempt yet! Lol! Thanks for coming back with the warning. I'll try everything later tonight or tomorrow. I'll follow up with the results or if I come across any issues.
XxMORPHEOUSxX said:
The work around for a nandroid with lock screen security is to delete the file locksettings.db from data/system. Use the file manager in twrp to erase it. Then once booted go to lockscreen security and toggle between swipe and fingerprint. It will erase the saved ones and let you start over.
Click to expand...
Click to collapse
Thanks! So just to clarify these are the options for nandroid security lock work around..
1.) Set lock security to nothing (just swipe), then do the nandroid backup
2.) Leaving pin/finger print security setting - delete the locksettings.db file using twrp. But is deleting it done before or after making the nandroid backup? Or after flashing the nandroid backup right before rebooting? Thanks!
AndroidPurity said:
Haha good thing I didn't attempt yet! Lol! Thanks for coming back with the warning. I'll try everything later tonight or tomorrow. I'll follow up with the results or if I come across any issues.
Thanks! So just to clarify these are the options for nandroid security lock work around..
1.) Set lock security to nothing (just swipe), then do the nandroid backup
2.) Leaving pin/finger print security setting - delete the locksettings.db file using twrp. But is deleting it done before or after making the nandroid backup? Or after flashing the nandroid backup right before rebooting? Thanks!
Click to expand...
Click to collapse
I believe @XxMORPHEOUSxX was just saying that if you were to make a nandroid and did not remove your PIN/password first, you can still use it by using his steps mentioned. If you remove it BEFORE the nandroid, you should be able to just restore it without issue. I haven't personally done either of those things, so you may want to wait until someone who has done it chime in, but that was my understanding.
fury683 said:
I believe @XxMORPHEOUSxX was just saying that if you were to make a nandroid and did not remove your PIN/password first, you can still use it by using his steps mentioned. If you remove it BEFORE the nandroid, you should be able to just restore it without issue. I haven't personally done either of those things, so you may want to wait until someone who has done it chime in, but that was my understanding.
Click to expand...
Click to collapse
Yes exactly. If you already made a nandroid and forgot, restore it and then erase that file. I've done it and it works.
fury683 said:
If you don't wipe userdata (remove the -w flag as I described) you won't need a nandroid. All your apps will remain intact, if you remove the -w.
Download the factory image, unpack it, edit the flash-all.bat to REMOVE the -w from the file (it's near the end), save the batch file. Put your phone in bootloader mode, run the factory image as you would normally. When complete, you'll be on a fresh install with all your data. This of course assumes the issue is /system related not /data related.
You could still take a nandroid in hopes that you could flash fully clean (without modifying the batch file) and then restore /data only from the nandroid. You'd need to offload that backup somewhere though because it would get wiped with the factory image.
Click to expand...
Click to collapse
So I downloaded the MMB29M factory image, and ran the flash-all.bat. Unfortunately I forgot to remove the -w. No biggie though I had no important pictures or documents that needed backed up. Just will have to sign into all my apps all over again. Anyways it did resolve the DND being stuck on, I figured it would since it went completely back to stock including user data.
However I am still baffled at how that could have happened when it was fine after the systemless root and never played around with the root files afterwards. No exposed modules or anything. Anyways I am about to flash twrp and install the new 2.65 SuperSU to root again. So I guess only time will tell if it happens again. Thanks for the help gentlemen!
Same problem but im on a stock phone. Not even rooted
Related
I'll tell you...basically not good things
After updating lots of apps, I decided to run the command to remove the boot-cache through a terminal app on my phone, rather than through adb shell (sprint needs to hurry up and fix this bug.)
Unfortunately, the terminal app doesn't like landscape, so when hitting the front slash after the data directory, my finger instead (to my absolute horror) hit the enter key.
Hilarity did NOT ensue. Basically everything started FC'ing. I rebooted into recovery, did a wipe, and started over. Everything seems to be fine, but for those that are more familiar with the filesystem than I, could there be any residual effects, or would the wipe/factory reset basically take me back to step 1? Thanks!
I'm going to try and write an app that not only clears the boot cache, but also turns on net sharing, kinda like a "utilities" app in the interim until Sprint can fix our stuff. Should be simple enough.
Factory reset should take you back to step 1.
Have you installed the recovery ROM? It doesn't modify your actual OS at all, but it enables you to do "whole phone" backups via Nandroid. Very handy for just such an occasion.
jonnythan said:
Factory reset should take you back to step 1.
Have you installed the recovery ROM? It doesn't modify your actual OS at all, but it enables you to do "whole phone" backups via Nandroid. Very handy for just such an occasion.
Click to expand...
Click to collapse
I do believe so. I followed our five star "how to root the CDMA Hero" thread, and I think the RA-Recovery part was included there.
I'm assuming since I can reboot into recovery mode, this is, in and of itself, the recovery ROM you're talking about. I have the option of a nandroid backup in there.
So, then let me ask you this. If I get my phone how I like it, can I do a Nandroid backup, and always be able to restore to that point, similar to commercially available backup apps? Thanks for the quick reply!
a Nandroid backup will restore everything on your phone (not your SDCard) so it should work to restore even if you delete the whole /data directory. It's not tested but it seems like it should work since it's an image of the whole freaking thing.
Ok I had my phone rooted and had voodoo on it. The phone was having issues downloading from the market, plus I couldnt turn the phone on unless i had it pluged in. So I tried to reset it using odin and the Stock-i500-VZW-Recovery.tar.md5. Now when I turn the phone on i get the android application has an uxpected error and I cant get past that. What do I do? Or how can I get my phone back to stock so I can re-root it.
Jeff5886 said:
Ok I had my phone rooted and had voodoo on it. The phone was having issues downloading from the market, plus I couldnt turn the phone on unless i had it pluged in. So I tried to reset it using odin and the Stock-i500-VZW-Recovery.tar.md5. Now when I turn the phone on i get the android application has an uxpected error and I cant get past that. What do I do? Or how can I get my phone back to stock so I can re-root it.
Click to expand...
Click to collapse
Jeff,
See this post for returning to stock http://forum.xda-developers.com/showthread.php?t=782204. I would do this as a last resort only.
Good Luck!
that is what got me to this problem. there are multiple files there what one do i use?
You apply them in the order they are listed.
1. Apply the "/system" file first
2. Apply the "kernel" file second
3. Apply thie "recovery" file third
This restores stock /system, the stock kernel, and the stock recovery. Pretty much brings you back to stock. Is that what you're trying to do?
I was having the same issues with USB cable looking like it was plugged in so I couldn't reboot unless it was plugged. I tried the voodoo uninstall and screwed up my data partition.
I ended up restoring the CWM_Kernel and Di01 Stock update which brought me back to stock with root and OTA update from Verizon BUT my Data partition is screwed and I have no internal app memory. Also, I have an Nandroid backup that I tried to install but that causes the FC issues that you mentioned. My guess is that my nandroid backup will work once I fix the data partition.
Later tonight, I'm going to try to put the stock MBR back onto the phone which I think you need to do as well.
However, it sounds like you didn't complete the whole recovery process and only applied one file. I'm an android newby so you can't take my advice to the bank but I think you need to restore all the files if you're going to flash with Odin per those instructions.
For me, I had CWM loaded so I just wiped the kernel and put back the DI01 ROM which put me back to stock albeit with some work to do to get my data partition back in shape. I hope this helped, for what it's worth.
Since you've already got the original.mbr copied and the stock.zip flashed...
Boot into CWM recovery and wide data/cache.
If you have a CWM backup of your phone in a rooted state, restore that backup through CWM.
Reboot, and go into "settings" if possible at this point, and factory reset.
This got me back from market failure/0.00/fc hell after utterly failing to heed the voodoo warnings and trying to revert to stock without undoing the lagfix.
You'll likely need to use the unsigned d101 apk if your backup/flash is dh12. The OTA update did not work for me at that point.
phispher said:
You apply them in the order they are listed.
1. Apply the "/system" file first
2. Apply the "kernel" file second
3. Apply thie "recovery" file third
This restores stock /system, the stock kernel, and the stock recovery. Pretty much brings you back to stock. Is that what you're trying to do?
Click to expand...
Click to collapse
My question is do i use the phone. pda or csc buttons for these files?
Ok in Odin use the PDA button for the /system
but what button do i use in odden to load the kernal.tar and recovery.tar
i loaded the pit, and installed all the files using the pda button one after the other. now my phone get no service and it still isnt wiped. what is going on? how do i get the phone back to out of the box condition.
also, now i cant do a factory wipe/reset, im getting the error message Can't mount /dev/block/mmcblk0p1
Gotta do the mbr fix from the 0.00 internal memory topic and then restore nandroid recovery.
Oh, and it is PDA for all three files, not just system.
Sent from my SCH-I500 using XDA App
i have the same problem n i havent had a phone for a
week...whats the fix??? did u fix urs??
trapstarr56 said:
i have the same problem n i havent had a phone for a
week...whats the fix??? did u fix urs??
Click to expand...
Click to collapse
Use the uninstaller form Here:
http://forum.xda-developers.com/showthread.php?t=804784
If that does not solve it, follow the steps here:
http://forum.xda-developers.com/showthread.php?t=782204
Read all pages of each topic completely prior to initiating *either* of them.
I encrypted my 10.1 yesterday without thinking all the way though. I found out that I could no longer flash kernels while the tablet is encrypted, since the SD card is not accessible in CWR.
I've tried doing a factory reset on my tab and each time, it boots up like nothing happened. I've also tried removing the pin that I put on it and the option to remove it is grayed out.
Do any of you know of a way to do a full wipe on the 10.1? Or could I reflash it using ODIN?
Thanks in advance.
id like to know this as well
still nothing? im starting to think this is an easy fix that nobody has posted about yet
there has to be something that im missing
try post # 6 in the linked thread, restore with unmodified vanilla version image from second link provided in the post, after booting from fastboot into recovery with clockworkmod recovery img; pushing it into the device sd with adb commandline, check the post for modifications and the link for details.
http://forum.xda-developers.com/showthread.php?t=1161325
whenever i try to reset to factory defaults, it just reboots like nothing happened
re-flash a stock firmware via odin as tar or fastboot/nandroid as img (backup restore)
Ones the tab is encrypted, there's no way to un do it. Unless you do what mughalgxt suggested. Good luck
Thanks guys, I went through some of these steps and found some other good tutorials to get me back up and running. All i wanted was to try the new kernel/bonsai rom out and I'm now able to do that
**** encryption, put a lockscreen password and be done with it.
I'm still struggling with this, as well: off to read some of the linked threads, because even with flashing a stock image with ODIN I'm still not able to recover the device. At least I managed to proceed past the boot loop I WAS in (when attempting to flash from CWM) - but now, I can get to the point where the device prompts me for the decryption key (meaning, it's clearly not yet restored to factory defaults) - but can't get it boot to completion. I also note that I've still got CWM Recovery, not stock.
It seems, at some point, encryption-key be damned, right? Meaning, if I don't care about recovering the contents of the encrypted partition - surely these low-level tools have the ability to simply format the partitions? Perhaps not - at least, not CWM - as attempts to format /data continue to fail.
Off to review the linked threads to try to gain some additional insight.
I ran into this same issue a long while back. As I recall (and it's been a while), you won't be able to wipe from CWM, but you can wipe from Settings / Privacy / Factory Data Reset. I could be wrong, but I know that I didn't have to do any adb pushing or anything with special images.
Hi SacTilt-
Thanks for the reply - and agreed: Had I actively started the effort from a functioning device, I think I could have selected that option.
As it turns out - I ran CWM, rebooted into recovery, and... next thing I knew, I was in boot loop hell.
I've tried flashing a variety of files via ODIN: Some at least allow the device to boot to the point where I get the initial password prompt - which I can provide, and proceed past... but then the device just 'goes blank'.
What I'm looking for is a 'start-from-scratch', no concern for data loss, delete the dang encrypted /data folder already, will ya?... approach.
As I've mentioned, a variety of ODIN files from a myriad of sources haven't seemed to quite do the trick. I feel like I'm missing something obvious - but can't find the right angle to spot it.
Perhaps fastboot might be what I'm looking for?
FWIW: the device was rooted when I started, so I've got full Titanium backups, with which I can restore, once I recover the actual device / OS.
Thanks for any insight.
Hey guys...if anybody finds a solution to this, please let me know...I am stuck with this same damn experimental ROM I've had from day one...it's getting really old. All I want is to get rid of this stupid encryption. Thanks for any help. Tried ODIN flashing, wiping data from security screen, wiping from CMR, etc.
Have you tried formatting the sd? Whenever i had my ns4g i accidentially did the same thing and i wiped the SD and it removed the encryption.
Sent from my GT-P7510 using XDA Premium HD app
Hi,
So long story short, I restored a backup after wiping my device, and I forgot to take the pattern lock off before backing up. No pattern I entered worked. I tried a bunch of things, and eventually I found a flashable zip that let me in, but now if I try to switch the lockscreen type from Swipe it crashes as soon as I press the button to load the different lockscreen types. Also, it crashes when I try to look at fingerprints.
I made a dumb mistake that I'd like to correct. I've tried flashing the factory image (without wipe) and tried flashing stock gapps. I'm thinking maybe there is a flashable lockscreen zip, but I haven't found anything. Is it possible that someone extract the lockscreen from a working 6P so I can flash it?
Or if anyone can give me another solution or insight into what might have happened, that would be appreciated.
Try removing the /data/system/locksettings.db file and rebooting (either use a root Explorer app or TWRP).
There's a few other locksettings files you may have to remove as well
Devhux said:
Try removing the /data/system/locksettings.db file and rebooting (either use a root Explorer app or TWRP).
There's a few other locksettings files you may have to remove as well
Click to expand...
Click to collapse
That totally worked, thank you. I had removed that before but didn't reboot before I tried again. D'oh! Thank you!
You're welcome. I'm still learning things with this phone too, and others have helped me a lot
Probably too soon to be asking but has anyone heard if Team Win is planning to support an Essential phone TWRP version?
Yes I know it's an old post, but I'm replying to this, rather then starting a new one...
Everyone knows TWRP sucks for this phone. Funny the OP asks about this. I was chatting the other day in the TWRP IRC channel on Freenode, and it seems, if they could get a phone, maybe this would be possible.
But in the meantime, is there anyone working on TWRP? It's really sad, that as long as this phone has been out, there's not better support for TWRP.
Hmm
I've only used twrp to boot to root on the PH1, but it does that perfectly every time (both IMG and zip).
What exactly doesn't it do?
kboya said:
I've only used twrp to boot to root on the PH1, but it does that perfectly every time (both IMG and zip).
What exactly doesn't it do?
Click to expand...
Click to collapse
1. Doesn't fit screen properly
2. Touch & Typing doesn't work properly
3. Backups & Restore don't seem to work properly - I'm still playing with it, maybe because of A/B I'm going about it wrong.
If this would fit the screen properly, and the touch and typing worked better, then it wouldn't be half bad.
I haven't noticed the first 2 (but touch in twrp has been janky on various phones since it began... A quick search will show this.)
Not tried backup/restore as Ive not used alpha/beta indy ROMs for several years (pre-6p I'd guess). Good luck with your mod attempt.
kboya said:
I haven't noticed the first 2 (but touch in twrp has been janky on various phones since it began... A quick search will show this.)
Not tried backup/restore as Ive not used alpha/beta indy ROMs for several years (pre-6p I'd guess). Good luck with your mod attempt.
Click to expand...
Click to collapse
If it fits the screen properly, can you take a picture? I'd like to see this.
For me, twrp leaves a space on the entire right side, it doesn't fill the screen properly...
I went back playing, and I did get a backup to work ok, now I'll need to see about restoring it and see if that goes ok.
I don't remember anything like the missing part you describe and I think if notice that! Sure, but it'll be next week before I can.
kboya said:
I don't remember anything like the missing part you describe and I think if notice that! Sure, but it'll be next week before I can.
Click to expand...
Click to collapse
I'm on the forum this week, but can't boot into TWRP till next week... LOL
What you loose your phone?
I've attached two screen shots, notice all the red dots, showing the gap on the right, compared to the left, and how the top right doesn't wrap around too...
Hahaha, no, I'm on holiday abroad without a laptop and I only boot into twrp via fastboot.
I've not noticed the gap that you show, but I'm not sure it would bother me enough to really consider it
I'll have a look when I get back.
DoR3M3 said:
I've attached two screen shots, notice all the red dots, showing the gap on the right, compared to the left, and how the top right doesn't wrap around too...
Click to expand...
Click to collapse
kboya said:
Hahaha, no, I'm on holiday abroad without a laptop and I only boot into twrp via fastboot.
I've not noticed the gap that you show, but I'm not sure it would bother me enough to really consider it
I'll have a look when I get back.
Click to expand...
Click to collapse
DoR3M3 said:
If it fits the screen properly, can you take a picture? I'd like to see this.
For me, twrp leaves a space on the entire right side, it doesn't fill the screen properly...
I went back playing, and I did get a backup to work ok, now I'll need to see about restoring it and see if that goes ok.
Click to expand...
Click to collapse
DoR3M3, he'll notice if he takes a close look at it. This is a documented issue that plagues EVERY PH1. It happens on my PH1 as well. Touch typing is indeed bad. The keyboard seems to be shifted left of what you actually are typing on.
Please keep us updated on your restoring experiences. I just rooted my 2nd PH1 and I'm also looking for ways to make a NANROID backup. Really want to hear your experience with the restoring part.
Thanks!
Try booting twrp on the opposite boot partition and make a nand backup from there and then try restoring from there. From what i understood it flashes to the opposite boot partition when twrp first came out im not sure if it still does that so its possible it does that to for nand backups and restores.
Ok I have managed to make a Backup and then Restore it!
MAKING THE BACKUP
These are the Steps I have taken, and take note, I do reboot, which some might assume isn't needed, but I have found, that if I didn't, then Magisk wasn't getting flashed in properly. Sometimes you just need to reboot between steps...
When you flash a Custom Rom, that should be on Slot A, then if you root with Magisk, Magisk will be flashed to Slot B. So now your BACKUP & RESTORE will be on Slot B! But some times I have seen people get their Slots flipped around, so however it ended up, the Slot you are making your BACKUP on, is the Slot that Magisk was flashed to, not the ROM!
1. IMPORTANT - TWRP does not backup the Internal Storage so this is a simple way of backing it up! Advanced > File Manager > data - RENAME the media folder > media.bak.
2. Now you are ready to make a BACKUP! All you need checked are Boot > System > Data - Click on (Auto Generate) to rename your BACKUP!
3. When the backup completes, now go back to Advanced > File Manager > data and you will see media, which is the new folder TWRP created with your backup in, and your old one you backed up, media.bak. Now you need to rename them both! Rename the new one to media.new and rename media.bak back to it's original name media. Now here's that reboot part I was talking about before, now Reboot > Bootloader.
4. For this step I'm assuming you're Rooted and using a Custom ROM, if that is the case, when you reboot back into TWRP > Install > lower right Install Image and pick the boot image, and make sure you flash it to Boot.
5. Now go back and Install Magisk.
6. You have now successfully made your TWRP backup, now reboot the system.
7. Once booted up and back in your system, start up your File Manager, I personally use and like FX File Manager with Root Access. Now you'll navigate to data and you should still see your two directories media & media.new. In FX File Manager I have this path, data > media.new > 0 > TWRP > BACKUPS. You want to copy BACKUPS to your Internal Storage TWRP directory. So in your Internal Storage you end up with TWRP > BACKUPS. Once you are done copying it, it's safe to delete the media.new directory, but just make sure you have copied the BACKUPS directory.
8. To test that you have your BACKUPS in the right path, boot into TWRP and click on Restore, if it shows up, you placed it in the correct path!
DOING THE RESTORE
With the A/B partitions, if you are rooted and running Magisk, then you will have noticed, that you installed your ROM into Slot A, then you should of rebooted back to the Bootloader, rebooted back into TWRP and installed the boot.img and Magisk, on Slot B. But as I mentioned above, some times people get their Slots flipped around, so remember, whichever Slot your flashed Magisk to, is the Slot you RESTORE on!
1. Boot into TWRP, which I'm assuming by my above statement, you are on Slot B, click Restore, click your backup, then make sure all partitions are checked, and then swipe.
2. Now reboot to the Bootloader, then reboot back into TWRP and Install your boot.img and Magisk.
3. Next go to Advanced > File Manager > data and you'll now see media & media.bak, confused? LOL Just think about it for a second, and you can delete media.bak.
4. Now reboot into your system and enjoy!
I'd like to add for anyone saying we don't need Twrp - Same reasons virtually every other phone gets a working build of it. If there was no need or demand for it, they'd cease to exist and people will stop using it. But every couple of weeks, there's an announcement of new phones getting TWRP.
DoR3M3 said:
Ok I have managed to make a Backup and then Restore it!
Click to expand...
Click to collapse
lol. Thanks for the step by step. It does seem a bit overwhelming for the uninitiated. I'll give it a try once I've had more time to digest the whole process.
Maybe we can get that post pinned. Thanks again for testing.
We do need TWRP, it's a great tool, that does simplify many things all in one...
@Lakino, it's not complicated at all, just a few steps, and once you've done it, then you'll see how easy it is, and come back and tell us then...
The TWRP guys have an Essential phone now so they will work on it but it sounds like not until Pie is figured out.
galakanokis said:
The TWRP guys have an Essential phone now so they will work on it but it sounds like not until Pie is figured out.
Click to expand...
Click to collapse
Woo time to round up the Army and head over to Freenode - #twrp
Get your butts over their people!
I'll be looking for Essential peeps chatting...