Related
I just received notification for OTA update. (134MB)
BLU_p0010UU_V11_GENERIC_5.1_20151123-0956
1. Stagefright patch
2. google security patches
3. Mcafee security 2015
4.Other bug fixes
Anyone tried it ?
i want to know if it is going to try and stick me with mcafee. . . happy to see an update, though!
you can remove mcafee after the update.
Can anyone upload ota?
Yes please. I'm rooted and it won't let me download the update. If someone could even offer a system dump that would be helpful.
---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------
If only for the stage fright patch
---------- Post added at 02:32 PM ---------- Previous post was at 02:29 PM ----------
Also if someone could offer a system dump of the newest upgrade I'd be more than willing to cook up a rooted stock rom. I know I haven't been on the forums much lately at all but I remember working on stuff back in the t-mobile g1 days
Rooting after the update
I only first tried to root my Blu Pure XL after the update was installed. I find that the boot loader is locked and I can not find a way to gain access. I am not sure if the update added this major inconvenience but I suspect it did as the rooting method as described will not work for me at all. Any thoughts or suggestions?
blacksmithjk said:
I only first tried to root my Blu Pure XL after the update was installed. I find that the boot loader is locked and I can not find a way to gain access. I am not sure if the update added this major inconvenience but I suspect it did as the rooting method as described will not work for me at all. Any thoughts or suggestions?
Click to expand...
Click to collapse
ive updated with every ota and root works fine... boot loader isnt locked... try to flash twrp via fastboot, and if that doesnt work enable developer options in settings and "Enable OEM unlock"
but like i said Ive flashed back to stock FW with SP tool (compete stock boot, recovery, and system ver .11) so if any update would have locked BL it would have locked mine... but it didnt, doesnt, and hasnt...
Follow the thread about twrp... it gives you very easy to follow directions.
Yeah, I did the OTA update before rooting, and it didn't want to allow me after the OTA update.
I downloaded multiple files from all over the place, placed them in a "root" subfolder and it still seemed impossible.
Got it done AFTER 3 days
so...
using flashboot to flash twrp, after the OTA,
then using twrp to flash the SU.zip took 3 days?
what files and "root folder" are you referring to?
Sounds like sever case of lack of reading or lack or user error;
But Im glad you stuck with it long enough to get it working...
ArconHadron said:
Yeah, I did the OTA update before rooting, and it didn't want to allow me after the OTA update.
I downloaded multiple files from all over the place, placed them in a "root" subfolder and it still seemed impossible.
Got it done AFTER 3 days
Click to expand...
Click to collapse
tbirdguy said:
ive updated with every ota and root works fine... boot loader isnt locked... try to flash twrp via fastboot, and if that doesnt work enable developer options in settings and "Enable OEM unlock"
but like i said Ive flashed back to stock FW with SP tool (compete stock boot, recovery, and system ver .11) so if any update would have locked BL it would have locked mine... but it didnt, doesnt, and hasnt...
Follow the thread about twrp... it gives you very easy to follow directions.
Click to expand...
Click to collapse
tbirdguy said:
so...
using flashboot to flash twrp, after the OTA,
then using twrp to flash the SU.zip took 3 days?
what files and "root folder" are you referring to?
Sounds like sever case of lack of reading or lack or user error;
But Im glad you stuck with it long enough to get it working...
Click to expand...
Click to collapse
Thanks, hardest part was actually getting phone to boot into flash mode.
Specifically, holding Power plus Volume+ is fine, but you have to let go of the power button first, then the Volume+.
Plus, I had to adb reboot before getting the TWRP rom to flash properly....
Not my best effort, but findintg SPECIFIC instructions were difficult, and had to manually search for latest fastflash and TWRP......v2.8.6.0
ArconHadron said:
Thanks, hardest part was actually getting phone to boot into flash mode.
Specifically, holding Power plus Volume+ is fine, but you have to let go of the power button first, then the Volume+.
Plus, I had to adb reboot before getting the TWRP rom to flash properly....
Not my best effort, but findintg SPECIFIC instructions were difficult, and had to manually search for latest fastflash and TWRP......v2.8.6.0
Click to expand...
Click to collapse
Fastflash?
Manually search?
Under the Development heading there are 5 topics, 2 of which are for TWRP recoveries (3.0.2 is buggy but works, just takes long time to wipe and restore; and theres SOOOOO many posts about how to flash them and how to use SP Flash Tool... so once again; glad you stuck with it, but Im still going with user error due to fail to RTFM
I've tried every single method I can see online, from fastboot flashing, to the dload method, to flashing stock via fastboot and then attempting the dload method. Nothing works. Right now I'm on TWRP 3.1.1-0 and RR 7.1.2. I really need to go back as with custom roms the fingerprint reader refuses to work, and not having HWC is a big deal to me. I was on EMUI 5.0, and I can't seem to get back. Any attempt at the dload method always fails at 5% and the fastboot flashed method (Where you flash the recovery, system and boot.img via fastboot) refuses to boot, (Just sits on device booting screen for 15+ minutes and does nothing). I've spent about 5-6 hours on this and I just can't figure it out. Any help is appreciated (also if anyone would be so kind as to throw up a BLL-L22 EMUI 5.0 TWRP stock backup, I'd really appreciate it).
Have you tried DC phoenix?!
rommco05 said:
need to know your build number bln-l22cxxx?
Click to expand...
Click to collapse
bll-l22c636b370
PalakMi said:
Have you tried DC phoenix?!
Click to expand...
Click to collapse
Not paying for unlocking software I'm never going to use other than flashing stock. If I'm desperate I might but currently looking for a free way to restore stock as this is my hobby phone to mess with and not my daily driver.
YMNDLZ said:
Not paying for unlocking software I'm never going to use other than flashing stock.
Click to expand...
Click to collapse
Well, I suggested it in case nothing else worked
I do get your point
Rommco05 said:
Flash this two zips over twrp. After go to reboot and tap reboot recovery, probably you will be in stock recovery and here tap factory reset and after reboot. Now should be phone boot to Nougat
http://update.hicloud.com:8180/TDS/...cseas/update_data_full_BLL-L22_hw_spcseas.zip
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1279/g104/v82620/f2/full/update.zip
Click to expand...
Click to collapse
Didn't work, ended with error 7. Here's the link for the recovery log: https://drive.google.com/open?id=0ByoIewGd_qk2b2ZGNTh5WVRFT0E .
Rommco05 said:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1279/g104/v87976/f2/full/update.zip
http://update.hicloud.com:8180/TDS/...cseas/update_data_full_BLL-L22_hw_spcseas.zip
Try this zips are B370
---------- Post added at 05:44 PM ---------- Previous post was at 05:43 PM ----------
Have you OpenKirin twrp?
Click to expand...
Click to collapse
I do have TWRP OpenKirin 3.1.1-0. I wiped everything beforehand. and I'm going to try and flash the firmware.
EDIT: No go, error 7 once again. I might just stay on 7.1.2 as this is getting very frustrating.
Hi all,
Tried searching, got nowhere.
I've received the OTA 1.53.401.5.
I have S-ON, Magisk root, stock recovery, stock system, custom Kernel
What would happen if I attempt to install the OTA without returning boot.img to stock? (Apart from overwriting the kernel with stock kernel).
Has anyone attempted? - Magisk should be able to persist root on the B partition since v14.1
Last, but not least, if the OTA fails....will my device bootloop? Or will it abort the update before making any changes?
The idea here, is it safe to attempt despite not being near to a PC to recover the device? Or will I need to be prepared to RUU my device in case of failure?
Kyuubi10 said:
Hi all,
Tried searching, got nowhere.
I've received the OTA 1.53.401.5.
I have S-ON, Magisk root, stock recovery, stock system, custom Kernel
What would happen if I attempt to install the OTA without returning boot.img to stock? (Apart from overwriting the kernel with stock kernel).
Has anyone attempted? - Magisk should be able to persist root on the B partition since v14.1
Last, but not least, if the OTA fails....will my device bootloop? Or will it abort the update before making any changes?
The idea here, is it safe to attempt despite not being near to a PC to recover the device? Or will I need to be prepared to RUU my device in case of failure?
Click to expand...
Click to collapse
I think it will fail if it doesn't pass its checks before rebooting.
(mine did as I had booted to twrp, but then I am used to backing up my data and RUUing these days)
Electronic Punk said:
I think it will fail if it doesn't pass its checks before rebooting.
(mine did as I had booted to twrp, but then I am used to backing up my data and RUUing these days)
Click to expand...
Click to collapse
Yeah, due to some tests I've been doing with Dolby Atmos I've gotten used to RUUing too... But it still is such a pain in the ass.
So can you confirm if it is a bootloop when OTA fails?
Kyuubi10 said:
Yeah, due to some tests I've been doing with Dolby Atmos I've gotten used to RUUing too... But it still is such a pain in the ass.
So can you confirm if it is a bootloop when OTA fails?
Click to expand...
Click to collapse
I didn't get as far as rebooting. The OTA started then failed without making any changes.
Kyuubi10 said:
Yeah, due to some tests I've been doing with Dolby Atmos I've gotten used to RUUing too... But it still is such a pain in the ass.
So can you confirm if it is a bootloop when OTA fails?
Click to expand...
Click to collapse
hey mate!
it won't bootloop, because it won't reach that far xD it will just fail. you need stock boot, system and vendor. if you've messed with system/vendor it will fail anyway
In another thread @Freak07 responded me that it could work only if some file in boot or vendor image had a certain value. It hadn't for me but I am sorry I forgot what it was exactly.
I believe it was either on @Freak07 recovery thread or in his kernel thread.
---------- Post added at 09:36 PM ---------- Previous post was at 08:38 PM ----------
EMJI79 said:
I am proposed OTA by the system but I can't do it, right?
We always have to RUU-OTA-ROOT then install the kernel?
I thought I had read that somewhere but I can't find it, so if someone could confirm?
Click to expand...
Click to collapse
It depends. Check the lifetime_kb_writes file like it’s mentioned in the second post of the twrp thread. If it doesn’t show 0 for system or vendor OTA will fail and you have to RUU.
Hi,
It is imperative to be in stock and not root.Sans this office error and the OTA does not settle.Je got to have version 1.30.401.2 on the A and version 1.53.401.5 on the B.Version on the A custom and root, the version on the B just root.
But not easy to get there!
DeeZZ_NuuZZ said:
hey mate!
it won't bootloop, because it won't reach that far xD it will just fail. you need stock boot, system and vendor. if you've messed with system/vendor it will fail anyway
Click to expand...
Click to collapse
Hey DeeZZ! Long time! XD I keep saying I'll come back but I never do.
Good to know that it won't bootloop... What I want to try tbh is follow the steps by Magisk dev to take OTA.
In theory if I flash back a clean system.img and vendor.img I should successfully be able to uninstall magisk take OTA and root the new update through Magisk Manager.
EMJI79 said:
In another thread @Freak07 responded me that it could work only if some file in boot or vendor image had a certain value. It hadn't for me but I am sorry I forgot what it was exactly.
I believe it was either on @Freak07 recovery thread or in his kernel thread.
---------- Post added at 09:36 PM ---------- Previous post was at 08:38 PM ----------
It depends. Check the lifetime_kb_writes file like it’s mentioned in the second post of the twrp thread. If it doesn’t show 0 for system or vendor OTA will fail and you have to RUU.
Click to expand...
Click to collapse
Thanks for this link! It was very useful.
But I do have one complaint about it... Surely the file would not be 0 while Magisk mods are active.
I have no system mods, and all mods I have are Magisk systemless mods.
So for the file to have a value greater than 0 it must be because while Magisk is active the file "believes" there are system modifications, due to following the sym-links created by Magisk.
This being said I couldn't find the vendor "sda#" on my sys/fs.
Additionally could I possibly change the file to have a "0" value? Thus fooling the OTA mechanism?
So many theories! I hope one of them works... I'm tired of RUU and losing my data.
I don't think you can change it manually, it would be too easy.
EMJI79 said:
I don't think you can change it manually, it would be too easy.
Click to expand...
Click to collapse
Lol true
So, I've flashed OneUI on my phone (I only flashed AP and CSC, no new bootloader), and TWRP doesn't seem to work with it since it can't read or wipe the data partition. Also, booting is a little weird. Sometimes it works perfectly, but sometimes it goes into a freeze bootloop thing where the boot animation freezes, and a few seconds later it reboots. I'm wondering if this has anything to do with me having a treble gsi on the phone before OneUI. Maybe the partition table didn't go back to stock after flashing? (the fstab must have though, since it's in the boot img) Or maybe it has something to do with having a different csc on the phone? (phone is XEH, but the firmware is DBT) I've tried re-flashing it with no luck. (it even freezes just randomly too, then goes into the bootloop.)
VDavid003 said:
So, I've flashed OneUI on my phone (I only flashed AP and CSC, no new bootloader), and TWRP doesn't seem to work with it since it can't read or wipe the data partition. Also, booting is a little weird. Sometimes it works perfectly, but sometimes it goes into a freeze bootloop thing where the boot animation freezes, and a few seconds later it reboots. I'm wondering if this has anything to do with me having a treble gsi on the phone before OneUI. Maybe the partition table didn't go back to stock after flashing? (the fstab must have though, since it's in the boot img) Or maybe it has something to do with having a different csc on the phone? (phone is XEH, but the firmware is DBT) I've tried re-flashing it with no luck. (it even freezes just randomly too, then goes into the bootloop.)
Click to expand...
Click to collapse
Good thing you skip the bootloader and modem.
Are developer who had done kernel and twrp has disappeared.
You can try to send him a pm.
Their are universal twrp that you could try.
What twrp are you using mean build?
mchlbenner said:
What twrp are you using mean build?
Click to expand...
Click to collapse
I tried BlackMesa123's official TWRP, and the treble twrp, none of them worked how they should.
I'm gonna try that one now (actually a little later 'cause personal stuff)...
VDavid003 said:
I tried BlackMesa123's official TWRP, and the treble twrp, none of them worked how they should.
I'm gonna try that one now (actually a little later 'cause personal stuff)...
Click to expand...
Click to collapse
I have flashed the new twrp it seems to work well
From the link I sent you.
https://www.google.com/amp/s/forum....ent/recovery-blackedtwrp-t3881548/amp/?espv=1
Working twrp for ab 2018.
Oh ok, I'll try it soon.
Any idea why do the freezes/bootloops happen tho?
VDavid003 said:
Oh ok, I'll try it soon.
Any idea why do the freezes/bootloops happen tho?
Click to expand...
Click to collapse
I have no I idea I rebooted five times with no mishaps.
Could are twrp is just not fully meant for pie.
mchlbenner said:
I have no I idea I rebooted five times with no mishaps.
Could are twrp is just not fully meant for pie.
Click to expand...
Click to collapse
Idk, currently I'm on stock 9.0 recovery and I'm getting freezes, bootloops but just randomly. I'm thinking maybe somehow it's related to treble... The stock recovery is even complaining about not finding /vendor, and some other partition.
VDavid003 said:
Idk, currently I'm on stock 9.0 recovery and I'm getting freezes, bootloops but just randomly. I'm thinking maybe somehow it's related to treble... The stock recovery is even complaining about not finding /vendor, and some other partition.
Click to expand...
Click to collapse
I would do a reflash .
what did was updated to the new Oreo bootloader then flash a rooted pie backup.
I had no reboots but I rebooted it could take a threw times to reboot.
Since I flash the new twrp I can reboot without issue.
Did you flash your region pie it should not really matter I have a the Russian pie and I flashed a Canadian csc to get volte working.
If you root use magisk 18.1 zip and use the twrp I link you.
mchlbenner said:
I have flashed the new twrp it seems to work well
From the link I sent you.
https://www.google.com/amp/s/forum....ent/recovery-blackedtwrp-t3881548/amp/?espv=1
Working twrp for ab 2018.
Click to expand...
Click to collapse
So I've tried it and same thing... Also, here's what the stock recovery says (sorry for the 2 decades old webcam):
Blackmesa's TWRP:
Treble TWRP:
The one you sent me:
mchlbenner said:
I would do a reflash .
what did was updated to the new Oreo bootloader then flash a rooted pie backup.
I had no reboots but I rebooted it could take a threw times to reboot.
Since I flash the new twrp I can reboot without issue.
Did you flash your region pie it should not really matter I have a the Russian pie and I flashed a Canadian csc to get volte working.
If you root use magisk 18.1 zip and use the twrp I link you.
Click to expand...
Click to collapse
Didn't see you replied. I'll try that - flashing oreo and restoring backup.
VDavid003 said:
So I've tried it and same thing... Also, here's what the stock recovery says (sorry for the 2 decades old webcam):
Blackmesa's TWRP:
Treble TWRP:
The one you sent me:
Click to expand...
Click to collapse
Remember you have to reformat after installing twrp.
It took me only two minutes to find the new twrp.
20 reboots without issue.
mchlbenner said:
Remember you have to reformat after installing twrp.
It took me only two minutes to find the new twrp.
20 reboots without issue.
Click to expand...
Click to collapse
You mean wiping data right?
'cuz that's what's failing on the screenshots.
For me the first about 12 hours was normal, then the freezes and bootloops started happening.
So it didn't fix the bootloops, but at least TWRP works now!
VDavid003 said:
You mean wiping data right?
'cuz that's what's failing on the screenshots.
For me the first about 12 hours was normal, then the freezes and bootloops started happening.
Click to expand...
Click to collapse
No reformat it will whiipe everything mean your downloaded apps
I was able to install TWRP and root with Magisk when the pie update was uploaded on this forum.
---------- Post added at 01:25 PM ---------- Previous post was at 01:24 PM ----------
And yes you need to erase everything
Well, I was able to root and fix twrp, but I still get bootloops and freezes...
I think I'll just wait for pie to be released on my csc and until that, I'll either get used to it or go back to Phh-treble (I've never tought I'd say a custom ROM that is not even meant for this specific device is more stable (for me) than the official)
VDavid003 said:
Well, I was able to root and fix twrp, but I still get bootloops and freezes...
I think I'll just wait for pie to be released on my csc and until that, I'll either get used to it or go back to Phh-treble (I've never tought I'd say a custom ROM that is not even meant for this specific device is more stable (for me) than the official)
Click to expand...
Click to collapse
I am having the exact same issues you are. In fact, are you using my phone when I sleep?
If you want to try out a 9.0 gsi that'll run pretty darn good in the meantime, try aospext's 9. Works well enough to use daily and you'll get a "4g" constant connection.
And since you have the same issues, this should give you a flawless run. If you are just entering a clean treble, wipe it all. Everything including internal. Just not your emovable of course.
Flash the vendor in from A8 that says 8.1 and 9.0 compatible. Flash the .img. Reboot recovery flash vendor again and then gapps. I did magisk after a normal run through and the latest was a 50% pass on safety. Gonna try it again right now for a third time. No issues with booting at all. If you do it differently all hell breaks loose and you'll be booted but with a severe case of "no system webview syndrome" or "chrome ain't no system app useless-lee-itus" The force closing of apps could be mistaken for an old Atari video game..
---------- Post added at 09:28 AM ---------- Previous post was at 08:58 AM ----------
Don't do what i suggested unless you've got a frikken system webview handy from a rom. all nicely in a folder. Toss it rightly in twrp.
mindlery said:
I am having the exact same issues you are. In fact, are you using my phone when I sleep?
If you want to try out a 9.0 gsi that'll run pretty darn good in the meantime, try aospext's 9. Works well enough to use daily and you'll get a "4g" constant connection.
And since you have the same issues, this should give you a flawless run. If you are just entering a clean treble, wipe it all. Everything including internal. Just not your emovable of course.
Flash the vendor in from A8 that says 8.1 and 9.0 compatible. Flash the .img. Reboot recovery flash vendor again and then gapps. I did magisk after a normal run through and the latest was a 50% pass on safety. Gonna try it again right now for a third time. No issues with booting at all. If you do it differently all hell breaks loose and you'll be booted but with a severe case of "no system webview syndrome" or "chrome ain't no system app useless-lee-itus" The force closing of apps could be mistaken for an old Atari video game..
---------- Post added at 09:28 AM ---------- Previous post was at 08:58 AM ----------
Don't do what i suggested unless you've got a frikken system webview handy from a rom. all nicely in a folder. Toss it rightly in twrp.
Click to expand...
Click to collapse
Lol
Well, it's good to see it's not me being stupid or my phone being broken
Soo.. looks like I fixed it.. What I did is downgraded to stock 8.0 and let OTA do it's job. I know it must have updated my bootloader (thus adding new locks to my device) but so far no bootloops,freezes, or anything. It might have been the bootloader, or the modem, or idk.
VDavid003 said:
Soo.. looks like I fixed it.. What I did is downgraded to stock 8.0 and let OTA do it's job. I know it must have updated my bootloader (thus adding new locks to my device) but so far no bootloops,freezes, or anything. It might have been the bootloader, or the modem, or idk.
Click to expand...
Click to collapse
Their where no freezing or issues on Oreo.
Android pie was released and it would freeze at boot and watching videos.
When will the update madness with our phone ends???
Downloading right now...has anyone installed it yet?
liquor said:
When will the update madness with our phone ends???
Downloading right now...has anyone installed it yet?
Click to expand...
Click to collapse
When will it end? Probably August 2020 as Essential has promised 2 years of OS updates and 3 of security updates like the Pixel. Android Q would be the last OS update, followed by a year of security updates. And August because the phone launched late August. It might get support through September. All assuming nothing happens to Essential before then.
Installed the zip from Essential, haven't had much time to see if any differences that are noticeable.
OTA Zip
Fastboot zip
Anybody else getting "Couldn't Update" message after reverting back to May update from Q Beta?
goofball2k said:
Installed the zip from Essential, haven't had much time to see if any differences that are noticeable.
OTA Zip
Fastboot zip
Click to expand...
Click to collapse
Do you apply those OTA.zips like you would for any ROM? Or do you wipe dalvik, system, and data then flash the OTA.zip. I wanted to ask before I winded up in some crazy ****. I went ahead and backed up my phone.
jxcorex28 said:
Do you apply those OTA.zips like you would for any ROM? Or do you wipe dalvik, system, and data then flash the OTA.zip. I wanted to ask before I winded up in some crazy ****. I went ahead and backed up my phone.
Click to expand...
Click to collapse
I have TWRP installed. This is my way of doing the update.
Ensure the OTA zip and TWRP zip (optional, you can choose to install TWRP your own way) and Magisk zip (optional, only if you want to be rooted) are on the phone storage
Reboot to TWRP recovery
Select Install, then install the OTA zip file and then the TWRP recovery zip.
Reboot to system, or if you wish to have Magisk installed, flash the Magisk zip file.
knochnkopf said:
Anybody else getting "Couldn't Update" message after reverting back to May update from Q Beta?
Click to expand...
Click to collapse
Yeah, have the exact same problem.
After disliking Android Q Beta (had issues with calls) I flashed Android 9 May update (fastboot). Now the June update won't install
cjscholten said:
Yeah, have the exact same problem.
After disliking Android Q Beta (had issues with calls) I flashed Android 9 May update (fastboot). Now the June update won't install
Click to expand...
Click to collapse
I had no issues installing the June OTA through TWRP after going back to stock May ROM from the Q Beta.
I would recommend you to back up again and start with the stock fastboot June ROM.
Good luck.
Sent from my PH-1 using XDA Labs
cjscholten said:
Yeah, have the exact same problem.
After disliking Android Q Beta (had issues with calls) I flashed Android 9 May update (fastboot). Now the June update won't install
Click to expand...
Click to collapse
Have you contacted Essential about the issue? I sent them a message yesterday with my device info and the process I used to flash back to the May 2019 update. Haven't heard from them yet. Seems like an odd problem. Only thing I can think of is maybe it has something to do with a scripting error in the batch file used to flash back to stock. I also went into my bootloader to verify that was locked so it should for all intents and purposes behave as a stock device. I have no root or custom recovery installed.
---------- Post added at 09:46 AM ---------- Previous post was at 09:22 AM ----------
Anybody know if flashing the OTA file from the Essential website vs the FastBoot file will completely wipe my device or just install over the top like a normal OTA? Only reason I ask is the OTA download is 330MB but the OTA file from the website is over 1GB. I really don't want to wipe my device AGAIN after just doing it less than a month ago.
Update: Flashed OTA zip from stock recovery without loss of data. They should really make that clearer on their website because it says flashing OTA "may" result in loss of data.
knochnkopf said:
Have you contacted Essential about the issue? I sent them a message yesterday with my device info and the process I used to flash back to the May 2019 update. Haven't heard from them yet. Seems like an odd problem. Only thing I can think of is maybe it has something to do with a scripting error in the batch file used to flash back to stock. I also went into my bootloader to verify that was locked so it should for all intents and purposes behave as a stock device. I have no root or custom recovery installed.
---------- Post added at 09:46 AM ---------- Previous post was at 09:22 AM ----------
Anybody know if flashing the OTA file from the Essential website vs the FastBoot file will completely wipe my device or just install over the top like a normal OTA? Only reason I ask is the OTA download is 330MB but the OTA file from the website is over 1GB. I really don't want to wipe my device AGAIN after just doing it less than a month ago.
Click to expand...
Click to collapse
I flashed the OTA via TWRP and retained all app's and the data without any problems.
Sent from my PH-1 using XDA Labs
The new update broke fastboot for me. Anyone else having issues with it? The update was taken OTA and runs fine, but I can't flash boot images or twrp anymore. Just gets a can't be read error.
Jz5678910 said:
The new update broke fastboot for me. Anyone else having issues with it? The update was taken OTA and runs fine, but I can't flash boot images or twrp anymore. Just gets a can't be read error.
Click to expand...
Click to collapse
There's a fastboot zip linked in the previous page. Not sure if it'll help but maybe.
Essential PH-1, /e/ 0.6-n ROM, microG (NoGapps), XDA Legacy
marcdw said:
There's a fastboot zip linked in the previous page. Not sure if it'll help but maybe.
Essential PH-1, /e/ 0.6-n ROM, microG (NoGapps), XDA Legacy
Click to expand...
Click to collapse
Actually I did try that, but I can't flash it due to fastboot not working unfortunately. It seems like one of my slots is corrupted.
Jz5678910 said:
The new update broke fastboot for me. Anyone else having issues with it? The update was taken OTA and runs fine, but I can't flash boot images or twrp anymore. Just gets a can't be read error.
Click to expand...
Click to collapse
I don't use TWRP, but I was able to successfully flash Magisk-patched boot image after the latest update, so fastboot seems to be working just fine for me...