Database Info

Whenever I try to update to v10j via OTA, it gives me an error. I am not rooted (yet)

Why would it be doing this? I already removed root via the SuperSU app permanently. What could be causing the error?

Bebout said:
Why would it be doing this? I already removed root via the SuperSU app permanently. What could be causing the error?
Click to expand...
Click to collapse
You might have a system app removed or missing
Or maybe you have done something with the build prop as well if thats messed with that will also throw an error out.
If you read closely it should tell you what the error is

xxbabiboi228xx said:
You might have a system app removed or missing
Click to expand...
Click to collapse
I really hope not. How do I go about finding out if I'm missing a system app? I've already done a factory reset along with unrooting via SuperSU's app.

Bebout said:
I really hope not. How do I go about finding out if I'm missing a system app? I've already done a factory reset along with unrooting via SuperSU's app.
Click to expand...
Click to collapse
It should tell you the error after you try flashing the ota you may have to use the .kdz method

xxbabiboi228xx said:
It should tell you the error after you try flashing the ota you may have to use the .kdz method
Click to expand...
Click to collapse
I don't have TWRP installed, either. I've got stock recovery and stock everything. I was going to remove root so I could update and then re-root for v10j and then install the new version of TWRP.

Bebout said:
I don't have TWRP installed, either. I've got stock recovery and stock everything. I was going to remove root so I could update and then re-root for v10j and then install the new version of TWRP.[/QUOTE
Your telling me you removed root ? But you never had twrp as your recovery ?
Click to expand...
Click to collapse

xxbabiboi228xx said:
Bebout said:
I don't have TWRP installed, either. I've got stock recovery and stock everything. I was going to remove root so I could update and then re-root for v10j and then install the new version of TWRP.
Click to expand...
Click to collapse
Your telling me you removed root ? But you never had twrp as your recovery ?
Click to expand...
Click to collapse
I fixed it. I rooted the device and flashed the v10i recovery image for TWRP that I found and I'm now going to update to v10j via the kdz, as you suggested. Thank you.

Bebout said:
I fixed it. I rooted the device and flashed the v10i recovery image for TWRP that I found and I'm now going to update to v10j via the kdz, as you suggested. Thank you.
Click to expand...
Click to collapse
No problem glad i could assist u in your problem

Why not get TWRP again and flash @GameTheory's v10j pre-rooted stock rom, it's not like you're going to see anything special with that update it's the last one before MM:
http://androidcreations.weebly.com/flashable-update-zip.html

Bebout said:
Why would it be doing this? I already removed root via the SuperSU app permanently. What could be causing the error?
Click to expand...
Click to collapse
well even if you Remove root via SuperSU that doesn't mean your SYSTEM is unmodified, the only way to get back to FULL Unmod. software is by following my steps of restoring back to stock, here is the link
http://forum.xda-developers.com/android/development/rom-lg-g-stylo-h631-ms631-v10j-stock-t3211563
P.S. You need to have TWRP for this so Re-Root and Re-Flash TWRP and follow steps

6.0.1 ota with stock rooted 6.0

My v10 downloaded an OTA , which im assuming is 6.0
1. Im rooted on stock 6.0 and unlocked boot loader. Will the OTA work without messing up anything ? Ill have to root again im sure, just want some info before i pull the trigger.

I don't think the update will even proceed being that you're on a rooted ROM. I have that notification too, and i just don't know how to turn it off.

I to am rooted,unlockboot and stock rom. I don't feel like taking a chance. So I used titanium backup to freeze the software update and in the drop down notification if you press it, it's a notification from Google play services if you block it in apps it will disappear from your drop down. I also deleted the update zip in the cache folder.I used es file explorer ,device/cache/update

popwar said:
My v10 downloaded an OTA , which im assuming is 6.0
1. Im rooted on stock 6.0 and unlocked boot loader. Will the OTA work without messing up anything ? Ill have to root again im sure, just want some info before i pull the trigger.
Click to expand...
Click to collapse
Okay, I'm assuming you are on H90120e (system version). There is a root exploit for the H90120j update. You just do the following:
Make a backup of your apps and settings
Flash your phone to the new update (H90120j)?
Take a look at either one of these threads to root your device again:
http://forum.xda-developers.com/tmobile-lg-v10/general/step-step-guide-rooting-lg-v10-using-t3382631
OR
http://forum.xda-developers.com/tmobile-lg-v10/general/root-android-6-0-h901-t3382819

You can't flash the phone that is already rooted and has TWRP.
I am in this same situation. On stock rom with root and twrp. I want to update to the new update, but do not want to loose all my apps, settings, etc.
Question is, how to do the initial update before having to re-root again?
How do we flash the phone with the new update?

bhagiratha said:
You can't flash the phone that is already rooted and has TWRP.
I am in this same situation. On stock rom with root and twrp. I want to update to the new update, but do not want to loose all my apps, settings, etc.
Question is, how to do the initial update before having to re-root again?
How do we flash the phone with the new update?
Click to expand...
Click to collapse
Why can't you flash the phone that is already rooted and has TWRP?
All you are doing is opening the LGUP tool and flashing the new H90120j .kdz file using the "refurbish" option then flashing the H90120j .tot file that has TWRP using the "update" option which will flash the phone regardless of what is running on your phone. The guides on the first link explain that. I believe your concern is keeping all of your settings and apps. Look up Titanium backup, it works for me.

Thank you. I only flash the LGH901AT-01-V20j-310-260-JUL-12-2016-ARB02+0ROOTTWRP tot file and all is good.
Well except that I lost Dolby audio.
I will look for a fix.

jun19inf said:
Okay, I'm assuming you are on H90120e (system version). There is a root exploit for the H90120j update. You just do the following:
Make a backup of your apps and settings
Flash your phone to the new update (H90120j)?
Take a look at either one of these threads to root your device again:
http://forum.xda-developers.com/tmobile-lg-v10/general/step-step-guide-rooting-lg-v10-using-t3382631
OR
http://forum.xda-developers.com/tmobile-lg-v10/general/root-android-6-0-h901-t3382819
Click to expand...
Click to collapse
Hi,
Do I have to use LGUP to install the update or can I click install on the dropdown of my phone?
I'm on stock MM 6.0 (H90120e) Rooted and I will not have access to my main PC for another week as I'm traveling.
Thanks,
-NJ

Anyone?

bhagiratha said:
You can't flash the phone that is already rooted and has TWRP.
I am in this same situation. On stock rom with root and twrp. I want to update to the new update, but do not want to loose all my apps, settings, etc.
Question is, how to do the initial update before having to re-root again?
How do we flash the phone with the new update?
Click to expand...
Click to collapse
There's a guide in general that tells how to do all this. In fact jun19inf WROTE it.
In a nutshell, do a twrp backup.
Upgrade to 20j by flashing the stock 20j kbz.
Enable usb debugging and oem unlock
flash tot that has twrp in it.
Now you can go into twrp and 1) root via supersu 2) restore ONLY data from your twrp backup taken previously to get your apps etc back. Alternatively Titanium Backup will also do just fine.

njdevils28 said:
Hi,
Do I have to use LGUP to install the update or can I click install on the dropdown of my phone?
I'm on stock MM 6.0 (H90120e) Rooted and I will not have access to my main PC for another week as I'm traveling.
Thanks,
-NJ
Click to expand...
Click to collapse
If all is you have is root, you should be able to unroot in the SuperSU settings, and then let the update install. But if you have TWRP, then I can't see any way to do the update without using a PC to flash your phone back to stock ROM and recovery. Although you may check the dev. section to see if Eliminator has a flashable ROM to bring you up to date.
Sent from my LG-H901 using XDA-Developers mobile app

YrrchSebor said:
If all is you have is root, you should be able to unroot in the SuperSU settings, and then let the update install. But if you have TWRP, then I can't see any way to do the update without using a PC to flash your phone back to stock ROM and recovery. Although you may check the dev. section to see if Eliminator has a flashable ROM to bring you up to date.
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
Ah. Thank you very much!
-NJ

Hi all. I just got my factory warranty back and I attempted to root it. Everything went as it should, until just after the install finished. Instead of rebooting normally, it now will only reboot into TWRP. Once there, when I try to flash a custom ROM (in this case, Bliss, but I don't think it matters, I get an error message that says the zip file is corrupt. Then, while still in recovery, when I tried to wipe everything except the sd card, it says mkfs.fat process ended with error. I then powered down and attempted the factory reset. I scrolled down on both screens and it did not say anything about any errors, so I assumed it took. However, it reboots right back into TWRP recovery. It also boots right to TWRP recovery when I try to boot normally. Of course, adb does not recognize the phone in any mode that I can get into (fastboot/recovery/download), so, I can't use LG Bridge to reflash the original firmware. Does anybody have any ideas for a fix? I know that this replacement phone had 6.0 on it. I thought I did everything to a t? TIA...
OK, not sure how I got there, but when I attempt to reboot from TWRP it says No OS Installed! Are you sure you want to reboot? That at least says what the problem is. Does anybody know how to fix this?

Where can I download the update file?

wbexpress said:
Hi all. I just got my factory warranty back and I attempted to root it. Everything went as it should, until just after the install finished. Instead of rebooting normally, it now will only reboot into TWRP. Once there, when I try to flash a custom ROM (in this case, Bliss, but I don't think it matters, I get an error message that says the zip file is corrupt. Then, while still in recovery, when I tried to wipe everything except the sd card, it says mkfs.fat process ended with error. I then powered down and attempted the factory reset. I scrolled down on both screens and it did not say anything about any errors, so I assumed it took. However, it reboots right back into TWRP recovery. It also boots right to TWRP recovery when I try to boot normally. Of course, adb does not recognize the phone in any mode that I can get into (fastboot/recovery/download), so, I can't use LG Bridge to reflash the original firmware. Does anybody have any ideas for a fix? I know that this replacement phone had 6.0 on it. I thought I did everything to a t? TIA...
OK, not sure how I got there, but when I attempt to reboot from TWRP it says No OS Installed! Are you sure you want to reboot? That at least says what the problem is. Does anybody know how to fix this?
Click to expand...
Click to collapse
Did you select refurbish or upgrade?
I believe you need to select upgrade when flashing or you get stuck in TWRP
Sent from my LG-H901 using XDA-Developers mobile app

How to root V10 T-mobile M.M ver V20L
How to root V10 T-mobile M.M ver V20L
Can some one guide me on the following:
1. Can I flash back and downgrade to Software version V20J from V20L.
2. Is there any root method for V10 t-mobile MM ver V20L.

1. It is well explained in this forum, you CANNOT go back without facing a software brick.
2. You can root your phone through Dirty_Cow method or by flash Eliminater74 ROM (Part1 & Part2).
Again, search for that in this section and in development one...

jonsat said:
1. It is well explained in this forum, you CANNOT go back without facing a software brick.
2. You can root your phone through Dirty_Cow method or by flash Eliminater74 ROM (Part1 & Part2).
Again, search for that in this section and in development one...
Click to expand...
Click to collapse
Thanks so much for your reply, I was about to flash it to downgrade my V10 from V20L to V20J i even downloaded the files for it Phew....
Okay, I have searched most of the rootings are V20J i have not found a method for rooting and twrp for V20L software update.
Please if u can share the link, that would be helpful...
thanks regards,

I wonder how people perform searches... by the way, few lines under this very thread, there is:
https://forum.xda-developers.com/tmobile-lg-v10/general/root-20l-dirty-cow-t3498722

jonsat said:
I wonder how people perform searches... by the way, few lines under this very thread, there is:
https://forum.xda-developers.com/tmobile-lg-v10/general/root-20l-dirty-cow-t3498722
Click to expand...
Click to collapse
Awwhh GOD!!! big thanks for your help, u r truly an awesome person. Peace and blessing upon u.
regards,

Update received - flashing via TWRP?

Hey there fellow U11 Users,
I just received the update concerning 60fps HD-Video etc. I use TWRP so the update can't be installed by itself. So I have two questions:
A
Where do I find the update file. I looked around a lot but couldn't locate it.
B
Once found, can I just flash it with TWRP?
Thanks in advance!

Dito13 said:
Hey there fellow U11 Users,
I just received the update concerning 60fps HD-Video etc. I use TWRP so the update can't be installed by itself. So I have two questions:
A
Where do I find the update file. I looked around a lot but couldn't locate it.
B
Once found, can I just flash it with TWRP?
Thanks in advance!
Click to expand...
Click to collapse
See here: https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048/page63

Alright, thanks! :good: That only leaves the first question unanswered.

Dito13 said:
Alright, thanks! :good: That only leaves the first question unanswered.
Click to expand...
Click to collapse
/data/data/com.htc.updater/files
btw...twrp can install the update but you need to flash the firmware.zip inside the ota manually

Thank you kindly!

OMJ said:
/data/data/com.htc.updater/files
btw...twrp can install the update but you need to flash the firmware.zip inside the ota manually
Click to expand...
Click to collapse
Just to be clear: I only flash the firmware.zip manually via TWRP or do I need to flash the whole ota?
Sorry for the question. I mostly handled Nexus devices...

Dito13 said:
Just to be clear: I only flash the firmware.zip manually via TWRP or do I need to flash the whole ota?
Sorry for the question. I mostly handled Nexus devices...
Click to expand...
Click to collapse
twrp will install the ota zip but it wont install the firmware.zip inside, you have to extract & manually install from download mode

grrr.... I tried following your suggestions, but recieved error 7 in TWRP. Can you help me in the right direction?

Dito13 said:
grrr.... I tried following your suggestions, but recieved error 7 in TWRP. Can you help me in the right direction?
Click to expand...
Click to collapse
list your steps your using to install the ota via twrp....personally, I let the system initiate the install (booted into OS) as if I was 100% stock, once twrp loads, it automatically installs except for the firmware.zip
more details here...

OK, I am a Noob to the HTC world. I am used to easy flashing/rooting/etc. on Nexus devices.
TWRP doesn't do anything after accepting the ota. When I try to install the OTA via TWRP I receive Error 7. I worked my way through a lot of guides here on XDA concerning manual OTA installing. One thing I tried was flashing back to stock recovery which I found in the firmware.zip of the OTA in bootloader mode. That failed also ("FAILED (remote: not allowed on PRODUCTION device).
Edit: The device has obviously an unlocked bootloader, s-on, rooted via magisk and is a DGLU device, software number 1.16.400.5

Are you on an Untouched System Image? Completely stock ROM? While it is great we can flash the OTA in TWRP, the system stills needs to be stock, and of course will still have to fastboot firmware.

schmeggy929 said:
Are you on an Untouched System Image? Completely stock ROM? While it is great we can flash the OTA in TWRP, the system stills needs to be stock, and of course will still have to fastboot firmware.
Click to expand...
Click to collapse
Yes, everything is stock.
I managed to flash the stock recovery now. I didn't remember to use the download mode /sorry. Then Then I checked for the ota again, downloaded it and tried to apply but I landed in the stock recovery with the red exclamation mark and then nothing happened.

Dito13 said:
Yes, everything is stock.
I managed to flash the stock recovery now. I didn't remember to use the download mode /sorry. Then Then I checked for the ota again, downloaded it and tried to apply but I landed in the stock recovery with the red exclamation mark and then nothing happened.
Click to expand...
Click to collapse
re-flash twrp and try it again.

schmeggy929 said:
re-flash twrp and try it again.
Click to expand...
Click to collapse
Same result unfortunately. TWRP hands out Error 7 and "system partition has unexpected contents" or something like that although I didn't do any tinkering with the stock rom. I flashed Magisk and did a backup before and that was all.

Dito13 said:
Same result unfortunately. TWRP hands out Error 7 and "system partition has unexpected contents" or something like that although I didn't do any tinkering with the stock rom. I flashed Magisk and did a backup before and that was all.
Click to expand...
Click to collapse
Only thing I would say is start fresh. Backup all the data for your apps first. Flash the RUU, Take the OTA and reinstall all your apps.

schmeggy929 said:
Only thing I would say is start fresh. Backup all the data for your apps first. Flash the RUU, Take the OTA and reinstall all your apps.
Click to expand...
Click to collapse
Thanks again - seems to have worked. It will be interesting to see which problems occur with the Android Oreo update which was announced till the end of the year by HTC

Couldn't install system update (november security patch)

I have just received the OTA and it is failing to install...
Anybody else facing this issue? Any ideas on how to fix it?
I have my Pixel 2 rooted right now, not sure if this can affect OTA?

luizffgarcia said:
I have my Pixel 2 rooted right now, not sure if this can affect OTA?
Click to expand...
Click to collapse
Being rooted is your issue

krelvinaz said:
Being rooted is your issue
Click to expand...
Click to collapse
What is the easiest way around it then? Do i have to download the factory image and flash it losing everything i have configured? Or is there another way?

https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Follow them steps
Nothing seems to work for me though i cant install ota no matter what but hopefully it should work for you.
It has for everyone else!

UpGrad3 said:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Follow them steps
Nothing seems to work for me though i cant install ota no matter what but hopefully it should work for you.
It has for everyone else!
Click to expand...
Click to collapse
Thanks but this also does not work for me, it starts step 1 but then the installation fails...
Any other options?
EDIT: LOL and now i lost magisk and root

luizffgarcia said:
Thanks but this also does not work for me, it starts step 1 but then the installation fails...
Any other options?
EDIT: LOL and now i lost magisk and root
Click to expand...
Click to collapse
I'm in the same boat...dies at step 1. Look familiar?
https://forum.xda-developers.com/showpost.php?p=74518728&postcount=53
Only I didn't lose root, as I re-installed Magisk before rebooting.

JayBlack_686 said:
I'm in the same boat...dies at step 1. Look familiar?
https://forum.xda-developers.com/showpost.php?p=74518728&postcount=53
Only I didn't lose root, as I re-installed Magisk before rebooting.
Click to expand...
Click to collapse
Yeah i sideloaded the OTA and it worked, but now i am struggling to put back snoke and magisk...
Every time i try i get stuck in the google logo, not sure whats going wrong

luizffgarcia said:
Yeah i sideloaded the OTA and it worked, but now i am struggling to put back snoke and magisk...
Every time i try i get stuck in the google logo, not sure whats going wrong
Click to expand...
Click to collapse
That happened the first time I tried to root. Had to flash the factory image and start over. Guess I could do that...but seems there has to be an easier way. I'm really curious why the method in that guide doesn't work for me.

Does flashfire work to install the OTA?

luizffgarcia said:
Thanks but this also does not work for me, it starts step 1 but then the installation fails...
Any other options?
EDIT: LOL and now i lost magisk and root
Click to expand...
Click to collapse
JayBlack_686 said:
I'm in the same boat...dies at step 1. Look familiar?
https://forum.xda-developers.com/showpost.php?p=74518728&postcount=53
Only I didn't lose root, as I re-installed Magisk before rebooting.
Click to expand...
Click to collapse
Download the full factory image. Open the flash all bat file with notepad and edit out the -w and save it. Then run it. That will flash the full factory image but leave apps and data in place.
Then you reroot it.

TonikJDK said:
Download the full factory image. Open the flash all bat file with notepad and edit out the -w and save it. Then run it. That will flash the full factory image but leave apps and data in place.
Then you reroot it.
Click to expand...
Click to collapse
Thanks. When I re-root, do I need to do the whole patch boot image process again? Or should I reuse the patched_boot.img that I used when I rooted the first time?

JayBlack_686 said:
Thanks. When I re-root, do I need to do the whole patch boot image process again? Or should I reuse the patched_boot.img that I used when I rooted the first time?
Click to expand...
Click to collapse
Redo it, otherwise you are a month behind on the boot IMG.

TonikJDK said:
Redo it, otherwise you are a month behind on the boot IMG.
Click to expand...
Click to collapse
Thank you. One last question: when I rooted, I used the snoke kernel and pointed to that .img file when patching the boot image (no reason, other than that's what everyone seemed to be using when root first happened). It sounds like this time, I should get the full factory image, extract, grab the boot.img from within that and patch THAT to be up to date. Correct?

JayBlack_686 said:
Thank you. One last question: when I rooted, I used the snoke kernel and pointed to that .img file when patching the boot image (no reason, other than that's what everyone seemed to be using when root first happened). It sounds like this time, I should get the full factory image, extract, grab the boot.img from within that and patch THAT to be up to date. Correct?
Click to expand...
Click to collapse
Correct, you can use whatever boot IMG you want. Snoke may be updated to November... don't know...bit if it is and you like it use it.

Waiting for answers. I finally succeeded with rooting my xiaomi mi a2 lite, everything works perfect, I was so excited to install Xposed but then my phone started to lag AF. I uninstalled it and then the update show up in the notification bar, great but "couldn't install system update". Is it because of the root or TWRP?

Feb 2019 update now available

Hope by performance fixes they mean memory leak fix.

I have not seen os ram usage this low after boot in many months.

Did you have round corner?

yaral said:
Did you have round corner?
Click to expand...
Click to collapse
It squared it when I screenshot.

Anybody figure out how to turn off the rounded corners?

Anyone know what the modem sucurity patch is about? Kinda don't want to take it cuz of the sim lock issues awhile back.

enigma2446 said:
Anyone know what the modem sucurity patch is about? Kinda don't want to take it cuz of the sim lock issues awhile back.
Click to expand...
Click to collapse
no clue but i fastboot flashed the images because the OTA refused to work, but flashing the images worked. i'm still able to connect to ATT towers from my sprint sim unlocked PH-1.

TomTheGeek3 said:
no clue but i fastboot flashed the images because the OTA refused to work, but flashing the images worked. i'm still able to connect to ATT towers from my sprint sim unlocked PH-1.
Click to expand...
Click to collapse
Noob question here: When using fastboot to flash the update image, do you have to worry about the "slot A" vs "slot B" thing?? Can you provide a little more insight? I've been reading around the forum, and I'm a little worried about bricking my phone! (The bootloader on my phone is unlocked and I've rooted the phone, but I haven't flashed a third-party ROM. The OTA update feature gives me a "couldn't update" message.)

adiejg said:
Noob question here: When using fastboot to flash the update image, do you have to worry about the "slot A" vs "slot B" thing?? Can you provide a little more insight? I've been reading around the forum, and I'm a little worried about bricking my phone! (The bootloader on my phone is unlocked and I've rooted the phone, but I haven't flashed a third-party ROM. The OTA update feature gives me a "couldn't update" message.)
Click to expand...
Click to collapse
No you don't have to worry about it. The flash all file in the zip will do all the work for you. It wont take update via ota because you have to be on the stock boot.img. the stock boot img has the recovery built into the ramdisk there for if your rooted then there is no stock recovery to use for ota. Be cautious because flashing via fastboot will wipe the phone.

enigma2446 said:
No you don't have to worry about it. The flash all file in the zip will do all the work for you. It wont take update via ota because you have to be on the stock boot.img. the stock boot img has the recovery built into the ramdisk there for if your rooted then there is no stock recovery to use for ota. Be cautious because flashing via fastboot will wipe the phone.
Click to expand...
Click to collapse
If I edit the .bat file and remove "format userdata", that will prevent the wipe?

njsges said:
If I edit the .bat file and remove "format userdata", that will prevent the wipe?
Click to expand...
Click to collapse
It should without issues but always prepare for hickups.

Anyone else having issues when trying to update to the February release? I tried to sideload the OTA update and that kept giving me the error "adb sideload failed to read command: no error" and then I decided to follow Morphius's suggestion here to just unroot my device by flashing to stock bootloader in order to try to take the OTA update and that OTA keeps failing as well. Anyone else having this issue?

hssxda said:
Anyone else having issues when trying to update to the February release? I tried to sideload the OTA update and that kept giving me the error "adb sideload failed to read command: no error" and then I decided to follow Morphius's suggestion here to just unroot my device by flashing to stock bootloader in order to try to take the OTA update and that OTA keeps failing as well. Anyone else having this issue?
Click to expand...
Click to collapse
Are you rooted?

After three days running, memory Leak not fixed.. Bummer

enigma2446 said:
No you don't have to worry about it. The flash all file in the zip will do all the work for you. It wont take update via ota because you have to be on the stock boot.img. the stock boot img has the recovery built into the ramdisk there for if your rooted then there is no stock recovery to use for ota. Be cautious because flashing via fastboot will wipe the phone.
Click to expand...
Click to collapse
Again, a very noob question, (and I do apologize) but can I use something like Titanium Backup to make sure I can restore all my apps the way they were after I flash the update via fastboot? Reinstalling everything seems like a gigantic pain in the backside.

adiejg said:
Again, a very noob question, (and I do apologize) but can I use something like Titanium Backup to make sure I can restore all my apps the way they were after I flash the update via fastboot? Reinstalling everything seems like a gigantic pain in the backside.
Click to expand...
Click to collapse
Titanium Backup used to require root access. You probably need to be rooted before you update via fastboot and run the backup through Titanium Backup. Then you will need to copy your backup files to a computer because fastboot flashing will erase your phone data. Next apply the fastboot update, root again, copy your backup back to the phone and restore your backup.

enigma2446 said:
Are you rooted?
Click to expand...
Click to collapse
I was but I followed all the proper steps but for some reason this morning my computer wouldn't real the OTA zip file. I tried it tonight using a different USB port on my laptop and it is worked first time... so weird...

d14r1 said:
After three days running, memory Leak not fixed.. Bummer
Click to expand...
Click to collapse
I don't have memory leak anymore..
1.5gb ram not in usage.
The last time I restarted my phone was after the update.

I'm using my Essential 'phone in the UK having recently purchased it used. On the 7th I had a notice to say that an update was available. When I tried to install it it downloaded, but refused to install saying: Couldn't update... installation problem. As far as I know the 'phone is running the stock software but I noticed that no updates had been installed since October 2018. I unchecked 'allow bootloader unlocking' in case that was the issue, but still couldn't perform the update.
I went onto the Essential website and downloaded the OTA image to my iMac, then, following the guide, sideloaded the update on to the 'phone. This worked well and I now have an updated PH-1. I'll have to see if March's update now installs correctly or not.

so.... am i reading this right... and here is my thinking...
to keep root and still take the OTAs
- go to Essentials site and download the image zip
- (to keep root) copy boot.img to your device, patch it through magisk, then copy it back to your ota folder.
- open flashall.bat, comment the format userdata (to keep your data), change the boot.img line to patched_boot.img
- run flashall.bat
- profit