Has anyone flashed the new 8.1 developer image? Is it possible to root and get TWRP on there?
Horgar said:
Has anyone flashed the new 8.1 developer image? Is it possible to root and get TWRP on there?
Click to expand...
Click to collapse
I booted trwp 3.1.1-1 and flashed SuperSU 2.82 SR3 + Suhide 1.09. Oreo feels more sweeter in 8.1 DP1.
Edit: Decrypt failed at recovery so performed above via OTG. Just thought you should know.
mannunikhil said:
I booted trwp 3.1.1-1 and flashed SuperSU 2.82 SR3 + Suhide 1.09. Oreo feels more sweeter in 8.1 DP1.
Edit: Decrypt failed at recovery so performed above via OTG. Just thought you should know.
Click to expand...
Click to collapse
Yes I tried with TWRP 3.1.1.1 and supersu 2.82 SR5 plus suhide 1.09. and got the same thing TWRP would not decrypt at password entry. Had to go back to 8.0. Have you managed to get root and recovery?
Horgar said:
Yes I tried with TWRP 3.1.1.1 and supersu 2.82 SR5 plus suhide 1.09. and got the same thing TWRP would not decrypt at password entry. Had to go back to 8.0. Have you managed to get root and recovery?
Click to expand...
Click to collapse
I'm not bothered with twrp recovery so did not flash the zip, but like I said I booted into twrp.img, flashed supersu and suhide and that's it. All working for me including SafetyNet. I used USB OTG for this process.
I did the same as the poster above.
just curious;
but how is Android 8.1? ?
I've found 8.0 to not be as good on battery life as 7.x.x, although I think I have mostly worked that out on my custom kernel...
any other notable goodies?
(ps: I don't care for the pixel launcher or the ambient services stuff..)
mannunikhil said:
I booted trwp 3.1.1-1 and flashed SuperSU 2.82 SR3 + Suhide 1.09. Oreo feels more sweeter in 8.1 DP1.
Edit: Decrypt failed at recovery so performed above via OTG. Just thought you should know.
Click to expand...
Click to collapse
I flashed factory image and I have error.
Myo Thu Htet said:
I flashed factory image and I have error.
Click to expand...
Click to collapse
Move the entire folder to a drive other than C drive. I think that might fix it.
NoobInToto said:
Move the entire folder to a drive other than C drive. I think that might fix it.
Click to expand...
Click to collapse
I did. But the error exit
Myo Thu Htet said:
I did. But the error exit
Click to expand...
Click to collapse
Sweet. Now you can't flash using factory images
And I can't flash using ADB sideload and inbuilt ota system.
Great.
Edit: @Myo Thu Htet
I checked google+ page of android beta program. Seems those update has issues.
NoobInToto said:
Sweet. Now you can't flash using factory images
And I can't flash using ADB sideload and inbuilt ota system.
Great.
Edit: @Myo Thu Htet
I checked google+ page of android beta program. Seems those update has issues.
Click to expand...
Click to collapse
I did all u did ?
Yes I checked G+
Only few can install.
Myo Thu Htet said:
I flashed factory image and I have error.
Click to expand...
Click to collapse
There could be few things that is causing to stuck, you can try below points in order make it work
1) check if downloaded factory image is not corrupt - see if you can extract all files from that zip, and/or download it again.
2) Disable any antivirus/firewall in your PC which monitors the behavior of files and try again.
3) Run cmd as Administrator and then run flash-all.bat
If none of above works then try and flash each file manually, follow my guide from below link this has worked 99% times
https://forum.xda-developers.com/showpost.php?p=73699257&postcount=5
mannunikhil said:
There could be few things that is causing to stuck, you can try below points in order make it work
1) check if downloaded factory image is not corrupt - see if you can extract all files from that zip, and/or download it again.
2) Disable any antivirus/firewall in your PC which monitors the behavior of files and try again.
3) Run cmd as Administrator and then run flash-all.bat
If none of above works then try and flash each file manually, follow my guide from below link this has worked 99% times
https://forum.xda-developers.com/showpost.php?p=73699257&postcount=5
Click to expand...
Click to collapse
Nope. It looks like Google's fault this time.
NoobInToto said:
Nope. It looks like Google's fault this time.
Click to expand...
Click to collapse
Just to test your theory (and came out wrong), I sideload'ed 8.1 OTA over my previous 8.1. This time it was successful without an error, attached images - one of it not clear as taken it from laptop camera just right now.
It seems like a file system issue when sideload'ing over 8.0.0 - a android developer shall confirm.
In short, both OTA and factory images from google are totally fine, concern is something else.
mannunikhil said:
Just to test your theory (and came out wrong), I sideload'ed 8.1 OTA over my previous 8.1. This time it was successful without an error, attached images - one of it not clear as taken it from laptop camera just right now.
It seems like a file system issue when sideload'ing over 8.0.0 - a android developer shall confirm.
In short, both OTA and factory images from google are totally fine, concern is something else.
Click to expand...
Click to collapse
It wouldn't be a fair test.
The update fails when sideloading 8.1 over a 8.0 system.
Edit: let me try the few things you suggested to test your suggestions . However I am not too optimistic.
@mannunikhil as I was extracting the ota, I realised I shouldn't bother with it. Google itself has taken down the ota from their site...
NoobInToto said:
It wouldn't be a fair test.
The update fails when sideloading 8.1 over a 8.0 system.
Edit: let me try the few things you suggested to test your suggestions . However I am not too optimistic.
@mannunikhil as I was extracting the ota, I realised I shouldn't bother with it. Google itself has taken down the ota from their site...
Click to expand...
Click to collapse
Mine was the fair test just to check if OTA zips are corrupt or not. I provided suggestions for factory image not for OTA, no point in extracting the OTA anyway. And if you had gone through all the threads you would see I mentioned I had similar issue sideload'ing OTA over 8.0.0, so that means we are sailing in same boat. OTAs had compatibility issue with 8.0.0, glad google listened and taken them off.
I still have little lag in app drawer hoping that would be fixed too in republished OTA.
Just signed up for Android beta program and got the 8.1 update for my project fi carrier unlocked Google pixel XL. The update seems to be running smoothly and everything is working so far on my device... I didn't have any issues with installation it installed just fine... Can't wait for Nov security patch supposed to be a good network feature in there in Dev settings.
I am not sure if this may help anyone trying to look at why the issues are present when trying to install:
Android 8.1 beta OTA upgrade on OG Pixel
I, just like many of you, have been experiencing OTA "installation problem" when trying to upgrade to the 8.1 beta. After reviewing comments and what worked for who, I decided to give this a shot and it worked. I am not sure if this will work for other devices (nexus or XLs) and keep in mind that you WILL lose all your data stored on the device, so back up prior to this method.
1. Be sure you are enrolled in the beta program.
2. Wait for the OTA to notify you that it's available.
3. Select "Download and Install".
4. After it has done its duty, DO NOT select "Restart and Install"
5. Go to "Factory Reset" and pull the trigger.
6. Your phone will factory reset, stating it's wiping everything, then it will install the update successfully.
NOTE: this is what worked for me. I'm unsure if it will solve all the "Installation problem" reports which have been made.
It's weird cause when I tried to factory reset, then download and install, it didn't work. Yet, downloading but NOT installing, then factory resetting worked.
After doing this I posted it here: https://plus.google.com/+ChristopherLeeMurray/posts/KDCZXbfAxLJ
You don’t need to sign up to the beta program. Just go to the Google website and download the latest 8.1 factory image. That's what I did and had no problem with flashing it. You can also delete the - w and keep your data. It's getting past the TWRP password to decrypt that I cant do. So can't flash root or recovery. Anyone managed this?
I'd prefer to be in the beta program since I'm a Android apps beta tester. I beta test everything and when it was installing it said on the screen that it's a beta version of the original software version of 8.1 which is what I believe is on Googles page and mine may have errors and defects.. the beta program gets different software than what Google usually posts. Different features and such which isn't in the official version which makes it a beta version.
Related
anyone able to catch the npf26j update for the pixel..
if so can you kindly post it ...
Just installed the OTA. Running stock un rooted
---------- Post added at 08:05 PM ---------- Previous post was at 07:47 PM ----------
https://tapatalk.com/shareLink?url=...&share_tid=158735&share_fid=3793&share_type=b
(Updated w/OTA File) Google Pixel NPF26J Update Brings Two New Gestures and More!
found this for those interested:
OTA Link on AFH
https://www.androidfilehost.com/?fid=385035244224400663
Sent from my sailfish using XDA Labs
mymusicathome said:
Just installed the OTA. Running stock un rooted
---------- Post added at 08:05 PM ---------- Previous post was at 07:47 PM ----------
https://tapatalk.com/shareLink?url=...&share_tid=158735&share_fid=3793&share_type=b
(Updated w/OTA File) Google Pixel NPF26J Update Brings Two New Gestures and More!
Click to expand...
Click to collapse
What build were you on before installing this update?
JAYNO20 said:
What build were you on before installing this update?
Click to expand...
Click to collapse
NDE63V
just a update for you guys, adb sideloaded update to 26j from NVE63V. Installed twrp, instaled franco kernel, rooted, and now up and running smoothly.
Anyone who is already rooted able to sideload this? It gets to about 50% then says Total xfer: 1.09x and on the screen it says
Error Applying Update: 20
and a bunch of other stuff.
chris5h said:
Anyone who is already rooted able to sideload this? It gets to about 50% then says Total xfer: 1.09x and on the screen it says
Error Applying Update: 20
and a bunch of other stuff.
Click to expand...
Click to collapse
Make sure your current build is NVE63V, then make sure you check MD5 sum. I had issues with my browser changing zip to a folder in Safari so MD5's wouldn't match. After that, use a good cable and ADB sideload should work.
I was rooted with TWRP and ElementalX on NDE63V. I used the flash all bat for NDE63V but I took out the -w before running it which kept all of my data. Once that finished I booted it up to the OS to verify everything was working. I then ran the OTA via sideload. Booted that up to the OS and confirmed it was running fine. I then installed TWRP, SuperSU then booted back up to the OS to verify everything was fine. Then installed ElementalX and booted back up into the OS. Everything so far is working fine.
jawmail said:
Make sure your current build is NVE63V, then make sure you check MD5 sum. I had issues with my browser changing zip to a folder in Safari so MD5's wouldn't match. After that, use a good cable and ADB sideload should work.
Click to expand...
Click to collapse
you mean "NDE63V", (not "NVE63V") right?
mdecker79 said:
I was rooted with TWRP and ElementalX on NDE63V. I used the flash all bat for NDE63V but I took out the -w before running it which kept all of my data. Once that finished I booted it up to the OS to verify everything was working. I then ran the OTA via sideload. Booted that up to the OS and confirmed it was running fine. I then installed TWRP, SuperSU then booted back up to the OS to verify everything was fine. Then installed ElementalX and booted back up into the OS. Everything so far is working fine.
Click to expand...
Click to collapse
That was it. Worked perfectly.
Thank you so much.
Sweetbabyj45 said:
you mean "NDE63V", (not "NVE63V") right?
Click to expand...
Click to collapse
Yes he does.
fully stock NDE63V cannot sideload this ota. stock recovery tells me its an error 20 status 1 problem with update package. TWRP tells me a file is missing from the zip. Ive downloaded it 3 times now. im loosing my mind. All drivers and adb fastboot is updated, and rebooted my pc. any suggestions?
That is what I was experiencing until I did what jawmail suggested and that fixed it for me.
chris5h said:
That is what I was experiencing until I did what jawmail suggested and that fixed it for me.
Click to expand...
Click to collapse
MD5 verified and matches. Ive reflashed the V factory image on both the a and b partition, im still getting the same error..
Edit: figured it out. I was on the B partition and it didn't want to flash the OTA to A. So I switched to the A partition and flagged it to the B. And everything is good now.
mdecker79 said:
I was rooted with TWRP and ElementalX on NDE63V. I used the flash all bat for NDE63V but I took out the -w before running it which kept all of my data. Once that finished I booted it up to the OS to verify everything was working. I then ran the OTA via sideload. Booted that up to the OS and confirmed it was running fine. I then installed TWRP, SuperSU then booted back up to the OS to verify everything was fine. Then installed ElementalX and booted back up into the OS. Everything so far is working fine.
Click to expand...
Click to collapse
I'm rooted w/out TWRP running Despair's kernel on NDE63V and have had trouble sideloading the OTA zip... says something to the effect that it "found 3389651 but expected 3332229" and aborted install. Anyway, I would like flash the factory NDE63V (as you did) and take out the -w (as you did) but lack the know-how to take out the -w... any chance you can lead me in the right direction or instruct me on that?? Thank you in advance.
Sweetbabyj45 said:
I'm rooted w/out TWRP running Despair's kernel on NDE63V and have had trouble sideloading the OTA zip... says something to the effect that it "found 3389651 but expected 3332229" and aborted install. Anyway, I would like flash the factory NDE63V (as you did) and take out the -w (as you did) but lack the know-how to take out the -w... any chance you can lead me in the right direction or instruct me on that?? Thank you in advance.
Click to expand...
Click to collapse
Edit the .bat file with notepad. Find the -w and remove it then save the bat file. Double check its been removed then follow Google's Instructions on how to flash a factory image.
mdecker79 said:
I was rooted with TWRP and ElementalX on NDE63V. I used the flash all bat for NDE63V but I took out the -w before running it which kept all of my data. Once that finished I booted it up to the OS to verify everything was working. I then ran the OTA via sideload. Booted that up to the OS and confirmed it was running fine. I then installed TWRP, SuperSU then booted back up to the OS to verify everything was fine. Then installed ElementalX and booted back up into the OS. Everything so far is working fine.
Click to expand...
Click to collapse
sorry - wrong post...
I have elemental X kernel, rooted, and TWRP and I cannot get this to install!!! I have tried to side load it, I have tried to install in TWRP with no luck, god why did I leave Android for apple, now I'm a noob again!
Anyone having issues with the double tap to wake not working if the phone has been sitting idle for a while?
Which June factory image is for the "everything else" devices... NHG47N or NHG47B?
Edit: Sorry, just figured it out, but it took info from another site other than Google's to find out that "N" is for Verizon and "B" is for everyone else.
CatThief said:
[solved] Which June factory image is for the "everything else" devices... NHG47N or NHG47B?
Edit: Sorry, just figured it out, but it took info from another site other than Google's to find out that "N" is for Verizon and "B" is for everyone else.
Click to expand...
Click to collapse
There's actually 4 different builds.
See here for what's what
Yep, I did that. There is no description there for "N" but I found out "B" is the one I want.
I always get Failed to udate, try again when installing the ota via settings.
Juli112 said:
I always get Failed to udate, try again when installing the ota via settings.
Click to expand...
Click to collapse
Have you unlocked the bootloader and modified the phone in any way? Personally I've rooted my phone with SuperSU, so I've been using FlashFire to install the OTA.
alluringreality said:
Have you unlocked the bootloader and modified the phone in any way? Personally I've rooted my phone with SuperSU, so I've been using FlashFire to install the OTA.
Click to expand...
Click to collapse
Did you update already. I read somewhere since the may update that if you have bootloader unlocked, rooted, and another kernel you get bootloops?
Is that true? I'm still on April security update and been using stock rom, just unlocked bootloader, rooted, and using elementalx kernel
I still have the May update on my phone, so I was just reading what people were saying about June before installing. According to posts like the first link, the current version of SuperSU does not sign the boot image. Signing the boot image as the last step is reportedly needed to avoid bootloops for the May or later bootloader. If someone is just using SuperSU, they can use the zip from the second link after SuperSU, which is what I did for May.
https://forum.xda-developers.com/showpost.php?p=72451572&postcount=1357
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't use ElementalX, but I've read a few posts indicating that it will also sign the boot image when installed last.
https://forum.xda-developers.com/showpost.php?p=72181714&postcount=1435
I did a flash-all (with -w removed) of NHG47B, then booted TWRP where I installed SuperSU and also VerifiedBootSigner-v8.zip before rebooting and everything is working fine.
alluringreality said:
I still have the May update on my phone, so I was just reading what people were saying about June before installing. According to posts like the first link, the current version of SuperSU does not sign the boot image. Signing the boot image as the last step is reportedly needed to avoid bootloops for the May or later bootloader. If someone is just using SuperSU, they can use the zip from the second link after SuperSU, which is what I did for May.
https://forum.xda-developers.com/showpost.php?p=72451572&postcount=1357
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't use ElementalX, but I've read a few posts indicating that it will also sign the boot image when installed last.
https://forum.xda-developers.com/showpost.php?p=72181714&postcount=1435
Click to expand...
Click to collapse
hey thanks i got everything up and running with the new June OTA. but what do you use to reflash TWRP?
flashify just freezes i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!
Nope. twrp.img must be firstly boot into the phone, then via this temporary twrp,you can install twrp.zip from your phone.
kazemitsui said:
hey thanks i got everything up and running with the new June OTA. but what do you use to reflash TWRP?
flashify just freezes i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!
Click to expand...
Click to collapse
CatThief said:
I did a flash-all (with -w removed) of NHG47B, then booted TWRP where I installed SuperSU and also VerifiedBootSigner-v8.zip before rebooting and everything is working fine.
Click to expand...
Click to collapse
Twrp rc1 or rc2?
Supersu 2.82 or 2.79rc3?
TENN3R said:
Twrp rc1 or rc2?
Supersu 2.82 or 2.79rc3?
Click to expand...
Click to collapse
I used twrp-3.0.2-0-RC1-fastboot-sailfish.img because it was the only version that was stable for me from the start. When the January update came out I tried the current TWRP at that time (it was an RC3, can't remember the version) and while others had no problems I had an experience of my own that I'm not keen on repeating.
As for SuperSU, I installed SR5-SuperSU-v2.78-SR5-20161130091551.zip then updated to the latest 2.82 from Google Play.
I know, newer releases may work now, but I was only going to try something newer if my "old" method failed. Like I said, I only boot to TWRP, I don't flash it. I just want root.
kazemitsui said:
i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!
Click to expand...
Click to collapse
When you tried installing TWRP with FlashFire, did you put the boot signer after TWRP? The TWRP install has to be signed with the current bootloader. The FlashFire documents make it seem like it should be able to install TWRP, but I haven't tried installing TWRP and can't find any relevant posts, so I suppose it might not work.
https://flashfire.chainfire.eu/actions/zip/
Personally I've just been using the small OTAs that come to the phone the past few months, but the following post indicates that FlashFire can at least retain a previously-installed version of TWRP without issue.
https://forum.xda-developers.com/showpost.php?p=70929003&postcount=8
TENN3R said:
Supersu 2.82 or 2.79rc3?
Click to expand...
Click to collapse
I had installed 2.79 RC3 with the May update, and then I had taken the play store update to 2.82. When I did the June update with FlashFire I'm guessing it must have went back to 2.79 RC3, because I got the update message again. I haven't seen anything to suggest either is likely an issue with the Pixel.
alluringreality said:
When you tried installing TWRP with FlashFire, did you put the boot signer after TWRP? The TWRP install has to be signed with the current bootloader. The FlashFire documents make it seem like it should be able to install TWRP, but I haven't tried installing TWRP and can't find any relevant posts, so I suppose it might not work.
https://flashfire.chainfire.eu/actions/zip/
Personally I've just been using the small OTAs that come to the phone the past few months, but the following post indicates that FlashFire can at least retain a previously-installed version of TWRP without issue.
https://forum.xda-developers.com/showpost.php?p=70929003&postcount=8
I had installed 2.79 RC3 with the May update, and then I had taken the play store update to 2.82. When I did the June update with FlashFire I'm guessing it must have went back to 2.79 RC3, because I got the update message again. I haven't seen anything to suggest either is likely an issue with the Pixel.
Click to expand...
Click to collapse
I just flashed TWRP through my computer I couldn't bother trying to figure out if FlashFire will flash TWRP or not haha
So i just got a Pixel 2 and got it rooted last night and moved all my stuff over before realizing i can get 8.1. I tried to get the latest stock from google but when i tried to run the .bat file (after removing the -w to prevent wiping) it started then failed saying something about needing something with a 59 in the file and the one i was using had 69.
Is there another way to do it? like unrooting, taking the OTA then rerooting? right now it says "couldnt update, installation problem". Is this from usign magisk? i know in the past id have to freeze the ota with TiBu.
mainly just looking for a way to get 8.1 without loosing all my stuff and having to copy it all back again.
Are you trying to skip some of the monthly updates?
Some believe the updates to be incremental, others do not. Update to the next month's update from the one you're on, until you're to the current June update.
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
Are you trying to skip some of the monthly updates?
Some believe the updates to be incremental, others do not. Update to the next month's update from the one you're on, until you're to the current June update.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
oh ****, theres no better way? thats over 10gb of files
So I just went through this. I bought my pixel 2 and updated from the September to November builds via flash. Then I got lazy and got a little behind on my updates.
There was something about the transition to 8.1 (December) that got a little wonky with regard to successfully flashing the bootloader.
What I did was I downloaded the December OTA update 8.1.0 (OPM1.171019.011, Dec 2017) and flashed that directly through "Apply Update through ADB"
Once that OTA has been flashed factory images such as the most recent one you were trying to flash should work. I successfully went directly from December to May. Just remember to remove the "-w" flag from the .bat file to avoid the wipe.
You won't lose all your stuff but you will need to re-root by flashing and installing Magisk.
The instructions from this thread are good:
https://forum.xda-developers.com/pixel-2/how-to/guide-how-to-install-google-software-t3760033
Hope this helps.
Best,
JasonVaritekMVP said:
So I just went through this. I bought my pixel 2 and updated from the September to November builds via flash. Then I got lazy and got a little behind on my updates.
There was something about the transition to 8.1 (December) that got a little wonky with regard to successfully flashing the bootloader.
What I did was I downloaded the December OTA update 8.1.0 (OPM1.171019.011, Dec 2017) and flashed that directly through "Apply Update through ADB"
Once that OTA has been flashed factory images such as the most recent one you were trying to flash should work. I successfully went directly from December to May. Just remember to remove the "-w" flag from the .bat file to avoid the wipe.
You won't lose all your stuff but you will need to re-root by flashing and installing Magisk.
The instructions from this thread are good:
https://forum.xda-developers.com/pixel-2/how-to/guide-how-to-install-google-software-t3760033
Hope this helps.
Best,
Click to expand...
Click to collapse
awesome, thanks! ill check it out
also, off topic, how do you get into twrp? doing the volume down and power just takes you to the bootloader screen and going to recovery ends up just leading to the stock recovery. I had to fastboot into twrp to get back. It also wouldnt let me backup which is an whole different issue.
Did you do both the fastboot to get into twrp and then the "adb shell twrp install" command listed in step 6 of the thread I linked?
It sounds like you might have booted with twrp but not made it persist.
vaeevictiss said:
awesome, thanks! ill check it out
also, off topic, how do you get into twrp? doing the volume down and power just takes you to the bootloader screen and going to recovery ends up just leading to the stock recovery. I had to fastboot into twrp to get back. It also wouldnt let me backup which is an whole different issue.
Click to expand...
Click to collapse
JasonVaritekMVP said:
Did you do both the fastboot to get into twrp and then the "adb shell twrp install" command listed in step 6 of the thread I linked?
It sounds like you might have booted with twrp but not made it persist.
Click to expand...
Click to collapse
yea that looks different. i just installed the twrp zip file from inside twrp.
and i dont need to unroot first right? this does it automatically?
JasonVaritekMVP said:
Did you do both the fastboot to get into twrp and then the "adb shell twrp install" command listed in step 6 of the thread I linked?
It sounds like you might have booted with twrp but not made it persist.
Click to expand...
Click to collapse
EDIT: Scratch that. i ended up just doing that sideload of the ota like you suggested and im good to go now!
thanks again!
deleted, not needed
Just a few minutes ago,i got the latest OOS 5.1.11.The change logs are
System
1.Optimized network connection
2.Optimized stability for wi-fi connection
3.Fixed screen flickering issue in day light
4.General bug fixes and improvements
5.confirm pin without tapping
Camera
Improved HDR mode
Any thoughts about the improved HDR mode? Didn't receive the update yet (Germany) but would be nice if someone could do before/after photos.
I also get that update.
If i download it.. can i just not update right away?
because i want to manually update from twrp and re root with magisk.
Thanks in advance
Sent from my ONEPLUS A6000 using Tapatalk
ossy1337 said:
Any thoughts about the improved HDR mode? Didn't receive the update yet (Germany) but would be nice if someone could do before/after photos.
Click to expand...
Click to collapse
I have no photos with older firmware.i think now the photos taken are more brighter
Root users beware: issues with newer TWRP version!
This article only applies to users running TWRP recovery on a rooted device. Don't have TWRP or don't know what this means? You're probably fine.
If you've recently installed or updated TWRP recovery, you might have faced that you can't install anything with it, and that the start screen is immediately shown when updating your device via Oxygen Updater.
Why is this happening to me?
From what it seems, this issue is caused by TWRP versions 3.2.2-0 and 3.2.3-0 being incompatible with the storage encryption technology present on OnePlus devices.
Normally, you're asked to enter your PIN or unlock pattern before installing an update / flashing something yourself. However, these new TWRP versions don't prompt for it anymore. Therefore, accessing the storage space of your device is no longer possible.
This is really frustrating, as almost all of your updates / .zip files are stored there. But luckily, there is a solution:
How do I fix this issue?
First of all, if you don't have encryption turned on or are not facing this issue, do not proceed with the steps below since flashing a new version of TWRP can be risky.
Now for the the solution: it involves downgrading TWRP to an earlier version, in which installing updates still worked correctly.
The downgrade can be done either by using a computer with the fastboot command, or by using flashing apps such as the Official TWRP app or Flashify on your device itself.
These are the steps you'll need to do:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
- Flash the version of TWRP using your method of choice. For fastboot users, connect your device to your computer in Fastboot mode and type fastboot flash recovery twrp-3.2.1-1-<yourdevice>.img. When using any of the flashing apps, browse to the correct TWRP.img file and flash it.
- Reboot your device. You'll now be able to access the working version of TWRP
- Do not update your TWRP version until it has been confirmed that this issue has been resolved.
Thanks to Peter Aarnoutse for reporting this issue.
So since twrp latest works fine on my device with encryption included, I can just start the update?
Sent from my ONEPLUS A6003 using Tapatalk
Neurom67 said:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
Click to expand...
Click to collapse
Can you link 3.2.1-1 version? https://eu.dl.twrp.me/enchilada/ There is only 3.2.1-0 or 3.2.2-0
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
No problem with blue twrp.
nieXas said:
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
Click to expand...
Click to collapse
Fails for everyone atm. Was working fine for me until two days ago before Google updated the api
Sent from my ONEPLUS A6003 using Tapatalk
nieXas said:
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
Click to expand...
Click to collapse
Here is why; https://mobile.twitter.com/topjohnwu/status/1029239685338419200
3.2.1.0 installed 5.1.11 fine on my OP6.
nieXas said:
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
Click to expand...
Click to collapse
SpectraFun said:
No problem with blue twrp.
Click to expand...
Click to collapse
Batfink33 said:
3.2.1.0 installed 5.1.11 fine on my OP6.
Click to expand...
Click to collapse
Can you confirm that you used Oxygen Updater in Automatic mode to flash new OTA and you didn't loose data/root/twrp?
Have TWRP 3.2.3 and installed 5.1.11 just fine.
SMS786 said:
Have TWRP 3.2.3 and installed 5.1.11 just fine.
Click to expand...
Click to collapse
did you use pin or fingerprint disable before flashing?
did you download zip from updater too? can i flash that zip from twrp or it just flashing all the way after download?
sorry.. never using updater to update OS.
need info.. thank you
Sent from my ONEPLUS A6000 using Tapatalk
Vuska said:
did you use pin or fingerprint disable before flashing?
did you download zip from updater too? can i flash that zip from twrp or it just flashing all the way after download?
sorry.. never using updater to update OS.
need info.. thank you
Sent from my ONEPLUS A6000 using Tapatalk
Click to expand...
Click to collapse
Didn't disable my pattern lock..worked just fine.
I downloaded the zip online and installed through TWRP. Just make sure to reinstall your TWRP installer after installing the full rom OTA (wipe cache/dalvik first), then reboot back into TWRP and install Magisk..then boot into system.
The OOS 5.1.11's camera is ****tier than the 5.1.9 as you can read on the official thread on oneplus's forum, some people are advising not to upgrade
Chinaroad said:
The OOS 5.1.11's camera is ****tier than the 5.1.9 as you can read on the official thread on oneplus's forum, some people are advising not to upgrade
Click to expand...
Click to collapse
People seem to be saying this for every release
giebeka said:
Can you confirm that you used Oxygen Updater in Automatic mode to flash new OTA and you didn't loose data/root/twrp?
Click to expand...
Click to collapse
Used Oxygen updater to download zip. Rebooted to bootloader. Went Install and selected ZIP. then added TWRP zip as well. Installed both. Rebooted to bootloader again. Flashed elementalx kernel(you can skip it) and magisk. All works fine.
kakkooran said:
Just a few minutes ago,i got the latest OOS 5.1.11.The change logs are
...
5.confirm pin without tapping
Click to expand...
Click to collapse
I can't find where to enable this. Anyone found it?
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...