yashsingh1/xdaforums huggingface dataset:
[ONE General] Mr.Ak:
Maybe the devs have fixed those bugs in Nougat by now,but don't even get me started on the messed up sources..
[ONE General] BigTurboSkipper:
REEEEEEE petition closed lmao, I've literally been browsing all day reading bout lineage 14.1 having support for voLTE natively and that some users got it working too. Is that real though? I'm running lineage 14.1 on my 1+1 but yeah can't see voLTE either in settings or in the advanced testing center accessible through *#*#4636#*#* from phone app, well I can, but it's blocked in the sense I cannot toggle it on. :confused:
[ONE General] impulsar:
That was an April fool prank, we all fell for that
[ONE General] impulsar:
It's sure that any dev who manages to do this, would make headlines on xda, bacon is still a quite popular device (not in sales, but in talks).

Proud ex bacon owner :)
[ONE General] BigTurboSkipper:
DAGNAB :P
[ONE General] Mr.Ak:
"Hope" do needs some logic though. Lol.
[ONE General] pankspoo:
After long time u read this post and commented my hope rised again....... ........ Thank you
[ONE General] :
Everyone. That's what is great about an open source project, everyone contributes in any way they can. Dolphin emulator wasn't created by just one dev or even a group of devs, everyone including users contributed bug fixes and improvements until it got to where it is today. I plan on getting around to this issue myself though, or at least starting the project on github if it hasn't been done by the time I finish my other projects. If you're looking for someone, you would want a dev with experience in reverse-engineering proprietary code. Consulting the devs who develop the nvidia open source nouveau driver for Linux could be a start.
[ONE General] pankspoo:
i got something interesting

Ok i got this from OP5 forum

https://xdaforums.com/oneplus-5/themes/magisk-volte-enabler-t3649647?_e_pi_=7,PAGE_ID10,3866586897

Its magisk module enables voWIFI calling option in settings but no voLTE. But u can now able to toggle voLTE option in *#*#4636#*#* option via dialer.

Tried to call using voWIFI option enabled but not worked.

May its help any dev to make something desired.....
[ONE General] impulsar:
A dev is working for volte on LG G3 (SD801).

If he's successful then you guys would surely get volte too :)
[ONE General] :
G3 has VoLTE by default. Check Fulmics ROM. Just give up
[ONE General] giaur:
This is pointless but if you want some fun... you are welcome
[Google Pixel Guides, News, & Discussion] spiller37:
Follow at your own risk, I take no responsibility. This guide is for any stock(seems to work with mods) rom. I used TWRP RC1, but could possibly work with alpha 2(for adb sideload only). Not sure if this method is "better" than using flash-all.bat without -w, but the file download was smaller.

Required Files and Locations they should be placed:

TWRP RC1 Image placed in the same folder as your FASTBOOT executable

TWRP RC1 zip installer placed on phones internal storage

SuperSU 2.79 SR3 zip installer placed on phones internal storage

NOF27B or NOF27C - Rogers OTA placed in the same folder as your ADB executable

Ensure the TWRP and SuperSU zip installers are loaded onto the phones internal storage and the OTA zip and TWRP image are in the ADB/FASTBOOT executables folder.

Boot into current TWRP recovery

Make a full backup in TWRP

Connect the phone to the computer

In TWRP select the Advanced menu, click ADB sideload option

On the computer open a command window and navigate to the location of your ADB executable/OTA zip

Only execute one adb sideload command for your specific device

Execute the following command(Non-Rogers): adb sideload sailfish-ota-nof27b-8130b5a8.zip

Execute the following command(Rogers): adb sideload sailfish-ota-nof27c-fb487658.zip

Only execute one adb sideload command for your specific device

The command window should be displaying a percentage and the TWRP should be displaying the standard OTA step 1 and 2 - Let this complete

Click Reboot System and let the OTA finish installing

At this point TWRP and Root are gone, but can be restored

With the device powered off, hold volume down and turn on the device. Your device should now be in the bootloader.

With the device connected to the computer run the following command from the previous step's command window: fastboot boot twrp-3.0.2-0-RC1-fastboot-sailfish.img

Install twrp-pixel-installer-sailfish-3.0.2-0-RC1.zip in TWRP

Install SR3-SuperSU-v2.79-SR3-20170114223742.zip in TWRP

Click Reboot System

Install Kernel/Mods

Remember to restore any /system specific edits such as the tether build.prop edit, host file edits, or custom boot animations.
[Google Pixel Guides, News, & Discussion] bush911:
This is amazing!. I have downloaded the full factory image already. followed by your guide, Can I just use an OTA package to upgrade NMF26O to latest build? I have rooted and twrp installed
[Google Pixel Guides, News, & Discussion] Juli112:
Just remove the -w argument from the flash-all.bat and flash the factory image...
[Google Pixel Guides, News, & Discussion] bush911:
Thank you dude, so what's the difference between full factory image and full ota zip, and ota automatically downloaded to phone.

the factory image is around 1.8 G and full ota zip is around 800 M, but the ota automatically downloaded to phone is only 47 M
[Google Pixel Guides, News, & Discussion] sliding_billy:
I had good luck with this method getting to NMF26O. Just a couple of things to note. Make sure you have the latest ADB files, and while it probably is assumed that you are using TWRP RC1 I'm pretty sure this did not work in Alpha2. Also, when the OP mentions losing TWRP it actually completely removes recovery so don't freak out if you try to boot into it expecting stock recovery and get a no data (or something like that if I remember correctly) error. There is no reason to check, but last time I was curious to see if it would leave TWRP in place. All is fine as long as you can get to bootloader. One other thing is the fact that this is an OTA. I would not do this unless coming from NMF26O but that is just me.

I am in no hurry to do this update since by all accounts it adds no functionality, but I was going to try it this way again. I wonder if anyone has any reason other than habit to continue to use the flash all method.
[Google Pixel Guides, News, & Discussion] Paz9:
so should we sideload the OTA over Q or download the factory image and remove the -w flag and run flash all.bat?
[Google Pixel Guides, News, & Discussion] quinejh:
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
[Google Pixel Guides, News, & Discussion] TonikJDK:
This is only for updating stock. If you want of weta then use the full image and remove the -w from the flashall bat file.
[Google Pixel Guides, News, & Discussion] quinejh:
thank you! worked great!
[Google Pixel Guides, News, & Discussion] b00ster23:
Because I'm groovy like that... ;) (And had a nandroid backup) I went ahead and took the jump of sideloading the OTA update over weta 2.2.1. Personally, I wasn't too concerned about botching up the system, as the weta ROM is going away. Instead the author is now compiling his mod(s) to layer over this stock build. I'm assuming that the OTA sideload went without a hitch because weta is designed around the stock image. Of course, I had to install some of my mod's again that were lost in the "update"

**DISCLAIMER**

I'm not claiming or declaring the OTA update is safe to install over weta 2.2.1. I'm only giving my experience so others can weigh out the risks for themselves, if they decide to roll the dice. :silly:
[Google Pixel Guides, News, & Discussion] rohitece06:
I followed this method and everything went smoothly. I have the new update, supersu and elemental kernel but now I can not use android pay :(
[Google Pixel Guides, News, & Discussion] spiller37:
I don't use Pay, but did you update to the latest Elemental kernel 1.03?
[Google Pixel Guides, News, & Discussion] rohitece06:
Yes I did.
[Google Pixel Guides, News, & Discussion] TonikJDK:
Try Franco's, his is patched for pay. Just to try and narrow it down here.
[Google Pixel Guides, News, & Discussion] spiller37:
You might also try the patched stock kernel that was just updated.
[Google Pixel Guides, News, & Discussion] rohitece06:
Thanks it worked with patched stock kernel although I lost root and when I installed SuperSu 2.79 SR2 android pay stopped working.
[Google Pixel Guides, News, & Discussion] aholeinthewor1d:
Is something up with the OP or is it just my XDA app causing it to show like this..
[Google Pixel Guides, News, & Discussion] spiller37:
Not sure why it displays this way in the two XDA apps. If anyone knows how to fix the formatting I would be grateful for the solution.
[Google Pixel Guides, News, & Discussion] spiller37:
Oh I didn't realize root and pay could work simultaneously on the pixel yet. Not sure which thread, but there was discussion on using the dual slots to run one slot stock with pay and one slot stock with root. Then dual booting between them.
[Google Pixel Guides, News, & Discussion] rohitece06:
it was working before this January pixel update
[Google Pixel Guides, News, & Discussion] TonikJDK:
Known bug in the app. Tags often mess up.
[Google Pixel Guides, News, & Discussion] bik2101:
going to assume this thread is not relevant/usable to those who mistakenly took the 7.1.1 update on verizon without unlocking bootloader first right?
[Google Pixel Guides, News, & Discussion] TonikJDK:
No it is not, you are locked. No method at this time for you to get unlocked.
[Google Pixel Guides, News, & Discussion] sliding_billy:
Got around to upgrading the Pixel and the Xl last night to U. I am starting to get used to this (after 4 times) method and liking it. Only thing I did differently this time was not rebooting between final install of TWRP (RC1) and install of SU (SR2). Easier to just stay there and do the install.
[Google Pixel Guides, News, & Discussion] blk_jack:
The correct format for lists:

[list]

[*] item1

[*] item2

[*] item3

[/list]
[Google Pixel Guides, News, & Discussion] joshw0000:
On my MXP I could flash OTA's in recovery just like a rom. I wonder if that would work with the Pixel?

Also, what if you immediately flashed TWRP again before rebooting, or does this process reboot itself automatically?

I'm trying to find the easiest method to update without pulling out the computer every month.

EDIT: I tried it and it worked. Flash the OTA in TWRP, then immediately flash TWRP before rebooting. I'm on nmf260 now and never used a computer.
[Google Pixel Guides, News, & Discussion] emplox:
This didn't work for me. After I flash SU on the last step and install SuperSU from the play store it doesn't detect root. I also tried to flash magisk instead and that won't work either. I get the below error. Does anyone have any idea why this would be happening?

Failed: /system could not be mounted!

Updater process ended with ERROR: 1

Error installing zip file '/sdcard/Magisk-v10.z.zip'
[Google Pixel Guides, News, & Discussion] 32BitWhore:
After you install the TWRP zip, try going back to the main menu and reboot recovery so you're installing it from the actual recovery and not the fastboot image. That's how most other guides have you do it and it worked fine that way for me.

Edit: also make sure TWRP is asking for your password if you're using lock screen security. If not, reboot recovery until it does. It's a known bug. Not sure if that has anything to do with your issue.
[Google Pixel Guides, News, & Discussion] jmitch3ll4:
So I have been debating trying this method flashing to the latest 7.1.1 I have the Verizon Pixel rooted and TWRPd on NDE63L (7.1).. I'm scared it'll backfire and I'll lose my unlocked BL.. and be stuck. Any Verizon Pixel owners have any hiccups?
[Google Pixel Guides, News, & Discussion] TonikJDK:
You won't lose the unlock. But at this point might well wait until Monday when the February update comes out.
[Google Pixel Guides, News, & Discussion] jmitch3ll4:
Good thinking.. I'll wait for the newest security update.. So idk what I was thinking I couldn't really lose the unlocked BL unless I purposely re-locked it, possible to end up in a bootloop though I guess and have to flash stock through adb/fastboot.

So basically you flash the OTA in TWRP, reboot recovery, flash TWRP zip file, flash super SU reboot?
[Google Pixel Guides, News, & Discussion] 32BitWhore:
I personally would add a step in between flashing TWRP and root and reboot recovery in between, but yes. Worked great on my VZW variant.
[Google Pixel Guides, News, & Discussion] eeldivad:
I'm new to rooting. I just bought the google pixel last month and just want to enable call recording so I can record calls with better quality. what is the minimal steps I need to enable call recording? Do I just root my phone and then ACR app will work with call recording or do I need to flash the rom too?

After rooting, will I lose my settings and photos like factory reset? Will I still be able to get regular android updates from google? What would I need to do if I want to get android updates? Do I just unroot it, apply updates, then root it again with latest version of root toolkits?

I see there's TWRP, ROMs, kernels, mods, Unified android toolkit, SuperSu, etc. I think I just need TWRP to root it right? Thanks community!
[Google Pixel Guides, News, & Discussion] jmitch3ll4:
Okay thanks for the tip! Just to make sure this doesn't wipe any data right? My pictures, apps, music ect will remain in internal storage? Probably giving this a go tomorrow with the February update :D
[Google Pixel Guides, News, & Discussion] 32BitWhore:
Yep, no wipe. I'd recommend a backup first obviously though.
[Google Pixel Guides, News, & Discussion] 32BitWhore:
Same steps work great for Feb 5th OTA (NOF26V) on my Verizon version, in case anyone is wondering.
[Google Pixel Guides, News, & Discussion] jmitch3ll4:
Doing this as soon as I get off tonight.. One last question lol do I side load and flash or just straight install from the main twrp screen?
[Google Pixel Guides, News, & Discussion] 32BitWhore:
Follow the steps in the original guide exactly. You'll start by loading up TWRP, then going to advanced, then selecting ADB Sideload, then execute "adb sideload [filename.zip]" from your computer (after running a TWRP backup of course) - make sure you download the OTA to your computer, not your phone. The rest is pretty self explanatory.

The only change I'd make to the guide (and someone smarter than me may explain why this is unnecessary, I just feel safer this way) is selecting Reboot Recovery in between flashing the TWRP zip and the SuperSU zip.
[Google Pixel Guides, News, & Discussion] jmitch3ll4:
ah okay I was reading a guy posted above me about doing this all from his phone (no computer) I was going to try that route but nvm I'll just follow the thread steps. Thanks again sir
[Google Pixel Guides, News, & Discussion] pfidr34:
Nvm
[Google Pixel Guides, News, & Discussion] cswithxda:
I see no mention of this:

delete fstab.sailfish after flashing TWRP and before flashing root

Is it not necessary now?
[Google Pixel Guides, News, & Discussion] TheBurgh:
Guide worked perfect. Very helpful after coming over from the 5x
[Google Pixel Guides, News, & Discussion] TonikJDK:
Not necessary if using TWRP RC1 an Su 2.7.9 SR3.
[Google Pixel Guides, News, & Discussion] MpandAUS:
This guide finally worked for me and doing step by step.. cheers :) happy to stay on stock with root, few tweaks and mods. Pixel is a very long flashing process so I'm scared to go flash a ROM then if it screws up, it'll be a nightmare having to do everything again by restoring back to the factory image, ADB sideloading it etc.
[Google Pixel Guides, News, & Discussion] jurisquo:
tried to sideload latest OTA (NOF27B) to rooted pixel TWRP RC1; followed instructions to the letter; and get error message 'Cannot read Sailfish-ota-nof27-b-8130b5a8.zip'.

Any help you can give me would be greatly appreciated.
[Google Pixel Guides, News, & Discussion] spiller37:
Check the file name, there is no - after nof27 before the b. nof27b
[Google Pixel Guides, News, & Discussion] jurisquo:
Thanks for the reply. I retried per your instruction and got this error message

C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload sailfish-ota-nof27b-8130b5a8.zip

loading: 'sailfish-ota-nof27b-8130b5a8.zip'

error: no devices/emulators found
[Google Pixel Guides, News, & Discussion] TonikJDK:
Not sure if it is your problem but you do not want to use minimal on this phone. It is old, and knows nothing about our partitions or our partition size. Use Google's.

https://developer.android.com/studio/releases/platform-tools.html

After you get that in, make sure it sees your device

ADB devices
[Google Pixel Guides, News, & Discussion] jurisquo:
I'll give it a try. Thanks!

---------- Post added at 07:45 PM ---------- Previous post was at 06:56 PM ----------

no luck with platform. adb devices recognized device, but when adb sideload sailfish-ota-nof27b-8130b5a8.zip, same error message:

loading: 'sailfish-ota-nof27b-8130b5a8.zip'

error: no devices/emulators found

alternative method would be to flash latest factory image, then reinstall twrp and SU, correct?
[Google Pixel Guides, News, & Discussion] sliding_billy:
Again installed my unlocked Verizon XL and my wife's unlocked PIxel this way with no issues.
[Google Pixel Guides, News, & Discussion] TheBurgh:
Second time I used and all went perfect.
[Google Pixel Guides, News, & Discussion] TheArkive:
*** always refer to the main guide ***

The trick to do it all from your phone is:

1) get TWRP RC1 zip AND img file

2) make sure you have latest android studio for latest adb and make sure you have latest pixel drivers for pc

3) put phone in bootloader mode

4) connect phone > run command:

adb devices

- make sure your device is listed, if not dont bother going on, fix this first

5) put zip file on phone

- put img in same folder as fastboot.exe

6) run command from pc:

fastboot boot xxxxxx.img

This will do a temporary boot into TWRP, without actually installing TWRP on your phone yet. Install the TWRP zip during this temporary boot.

DO NOT DO "fastboot flash xxxx.img" !!!!!!!!

You will get unexpected results!!

7) now reboot phone to recovery

8) now you can use TWRP normally (except backups/restore - that doesn't fully work as intended yet)

- if you install updates or ota just reflash TWRP zip before reboot.

From here you only need step 7 and 8 for future updates. Just remember to always reflash TWRP RC1 before reboot.

NOTE: when you flash stock roms/OTA roms you will lose TWRP after reboot, so that is why after you flash stock/OTA update, (re)flash TWRP RC1

Hope that makes sense. As always, learn from the main guide. Don't forget about the A/B slot concept. That is very different compared to other android phones.

Keep in mind the main guide is intended to get your first install of TWRP and SuperSU working. The main guide also tries to explain the concept of what is happening. It may sound like extra useless info but it isn't. If you understand the concept then you can do much more, instead of waiting for another step-by-step guide ;)

I just ordered my pixel today. But I've been reading a ton on how the pixel is different. Makes total sense if you slow down and get the main concepts. It helps if you aren't afraid of losing data. If this is a concern then proceed with extreme caution. The path to "enlightenment" only comes through trial and error and learnimg for yourself.

Tinker

Break it

Fix it

Rinse ... Cycle ... Repeat!

Again... Hope this helped someone.
[Google Pixel Guides, News, & Discussion] kcchen:
Thanks for the guide. Just came across it...

I've been downloading the OTA to the phone and Installing from TWRP, rather than sideloading... Any problems with that?

Still have to fastboot TWRP.img to install TWRP and SU, but phone seems to have the latest build number.
[Google Pixel Guides, News, & Discussion] TheArkive:
I haven't had a chance to test it myself yet, but from what I've been reading as long as you do the initial TWRP setup with temp boot into a TWRP img file, then follow future OTA updates with a subsequent sideload of TWRP zip right after, and then reboot, should work. Might not hurt to wipe cache and dalvik too.

I'll reconfirm this once I get my pixel. joshw0000 managed to get it working nicely.
[Google Pixel Guides, News, & Discussion] joshw0000:
Just an FYI, there's an easier way to do this:

- Just flash the OTA in TWRP like you would any rom (need to be on the previous build obviously - basic mods are OK).

- Before rebooting, flash TWRP (if you don't it will be lost and you'll need a computer to get it back).

- Reboot

- Now reboot to recovery and flash SuperSu and/or any other mods.

Optional:

I always make a backup of my rom before doing this, as well as a backup of the new OTA before performing any mods. This way, if some mod that I perform somehow prevents me from updating in the future, I can restore back to that stock OTA and then TWRP flash to the next newest OTA.
[Google Pixel Guides, News, & Discussion] joshw0000:
Ah man, that sucks. I have a driver issue with my computer. I've updated everything I can think of but there is still something funky where the flashall.bat always fails on my computer. So for me to use the full system file, I have to mod the file and run it through a universal tool which is a PITA. I remembered this little trick from my MXP and luckily it worked like a champ.
[Google Pixel Guides, News, & Discussion] mikeprius:
How do I update the drivers? This keeps saying no device and emulator found
[Google Pixel Guides, News, & Discussion] sliding_billy:
Worked fine going from 7.1.1 March build directly to 7.1.2 except that ADB sideload threw a version build error (worked fine for devices command and reboot recovery command) when using the March Google ADB/Fastboot files. Worked fine with the December files. Used TWRP RC2, so at least this function isn't broken in RC2.
[Google Pixel Guides, News, & Discussion] bschatzow:
ODA from TWRP

Can I install the latest OTA (N2G47E) on my rooted pixel XL by booting into recovery (TWRP)? If so, is this a dirty install, i.e all the data stays intact or does this wipe the data?

Thanks.
[Google Pixel Guides, News, & Discussion] 0pUjpLBbgu6JXYXb7Clq:
I haven't been able to get the June security updates to work with this method. Anybody else having difficulty?

--OpU
[Google Pixel Guides, News, & Discussion] sliding_billy:
I installed June this way with no problem.
[Google Pixel Guides, News, & Discussion] 0pUjpLBbgu6JXYXb7Clq:
Which build did you upgrade from? Are you on a Pixel or Pixel XL?

I was getting persistent errors until I flashed back to the OTA I'd been on (NHG47K). Anything beyond that build was throwing bootloops.
[Google Pixel Guides, News, & Discussion] TENN3R:
I always used this method since the guide until june with no problems too, just need verified bootloader zip and everything is good
[Google Pixel Guides, News, & Discussion] sliding_billy:
From NHG47L to NHG47N on both a Pixel (wife's phone) and my Pixel XL. Did you check your download for possible size issue? Do you have TWRP set to check for install errors? Did you do anything before rebooting at the end of the sideload install? Is that when you got the bootloops or when you installed TWRP or SuperSU again? I ran TWRP from the RC1 temp file, and then installed RC2 full install, SuperSU 2.82 (modified) and not stable or pixel fix and then I signed with V8 signer. Also, I used the latest Google adb&fastboot files in case that made any difference .