https://plus.google.com/100708818877715770270/posts/2hFtzS7bshe?sfc=false
Factory images are up now.
edit: https://developer.android.com/preview/download-712.html
I am about to flash and see if we have any kernel issues on it.
Can we have this on slot a if I have TWRP on slot a too?
Rootuser3.0 said:
Can we have this on slot a if I have TWRP on slot a too?
Click to expand...
Click to collapse
Twrp is on both slots
Rootuser3.0 said:
Can we have this on slot a if I have TWRP on slot a too?
Click to expand...
Click to collapse
TWRP is flashed to both slots. Thats the way it works.
Golf c said:
TWRP is flashed to both slots. Thats the way it works.
Click to expand...
Click to collapse
So my question is this. If I fastboot flash this to slot A can we still Access TWRP? Will this write over the recovery? So do I make sure when I boot into bootloader that it shows slot B?
DespairFactor said:
I am about to flash and see if we have any kernel issues on it.
Click to expand...
Click to collapse
R24 boots fine.
Sent from my Pixel XL using XDA Labs
Rootuser3.0 said:
So my question is this. If I fastboot flash this to slot A can we still Access TWRP? Will this write over the recovery? So do I make sure when I boot into bootloader that it shows slot B?
Click to expand...
Click to collapse
1-It remains to be seen if twrp works with this beta?
2-The beta or any flash of a boot image will overwrite twrp. Elemental x would be an exception.
3-If your flashing this beta, it wouldn't matter what slot you are in. You would have to wipe data anyway. If you don't want issues
Anyone get this thing running? Any feedback?
Golf c said:
1-It remains to be seen if twrp works with this beta?
2-The beta or any flash of a boot image will overwrite twrp. Elemental x would be an exception.
3-If your flashing this beta, it wouldn't matter what slot you are in. You would have to wipe data anyway. If you don't want issues
Click to expand...
Click to collapse
Very well I'll wait not worth giving up PN which has been running like a Cadillac
Rootuser3.0 said:
Very well I'll wait not worth giving up PN which has been running like a Cadillac
Click to expand...
Click to collapse
I would totally agree with that. See how it goes for other folks and what new features come with it. I always wait and see what people are saying then take it for a spin. Then I always end up back on PN, Uber or DU. Haha!
Golf c said:
1-It remains to be seen if twrp works with this beta?
2-The beta or any flash of a boot image will overwrite twrp. Elemental x would be an exception.
3-If your flashing this beta, it wouldn't matter what slot you are in. You would have to wipe data anyway. If you don't want issues
Click to expand...
Click to collapse
Pøîñtßlåñk said:
Anyone get this thing running? Any feedback?
Click to expand...
Click to collapse
TWRP, SuperSu, Sharkey R24 all working great.
Sent from my Pixel XL using XDA Labs
ridobe said:
R24 boots fine.
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
ridobe said:
TWRP, SuperSu, Sharkey R24 all working great.
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
It should work, except the flashlight doesn't work for me atm. Will need kernel sources
ridobe said:
TWRP, SuperSu, Sharkey R24 all working great.
Click to expand...
Click to collapse
Nice, thank you. I figured the first two would. Wasn't sure about custom kernels. With this device you never know. Any new features?
It could be just me, but double tap to trigger ambient display seems to be more responsive. Again, it could just be me. Has anyone else noticed anything new?
If i flash using fastboot, will it wipe my data. Been on stock since coming to pixel.
Sent from my Pixel XL using Tapatalk
cpetersen2791 said:
If i flash using fastboot, will it wipe my data. Been on stock since coming to pixel.
Click to expand...
Click to collapse
Not if you delete the -w out the flash all file with notepad or apple equivalent editor
Golf c said:
Not if you delete the -w out the flash all file with notepad or apple equivalent editor
Click to expand...
Click to collapse
OK, so no different than Shamu. Usually I root and add custom recovery, but haven't felt the need yet with Pixel XL
Thanks
Sent from my Pixel XL using Tapatalk
cpetersen2791 said:
OK, so no different than Shamu. Usually I root and add custom recovery, but haven't felt the need yet with Pixel XL
Thanks
Click to expand...
Click to collapse
You would have to have an unlocked bootloader, like Shamu, but this device is nothing like anything before it. Lol
Related
Im kinda surprised that theres no thread about this...
Has anyone flashed the new OxygenOS 2.1.4 already?
https://forums.oneplus.net/threads/oxygenos-2-1-4-for-the-oneplus-one.425544/
If you want to flash it via TWRP you should read this thread. Credits to @Bobbi lim
http://forum.xda-developers.com/oneplus-one/general/flashable-oxygenos-2-1-4-coming-soon-t3299296/post64937732#post64937732
darwinzp said:
Im kinda surprised that theres no thread about this...
Has anyone flashed the new OxygenOS 2.1.4 already?
https://forums.oneplus.net/threads/oxygenos-2-1-4-for-the-oneplus-one.425544/
Click to expand...
Click to collapse
Looks interesting but flashing wipes everything and waiting on confirmation if you can flash TWRP after you've used the Oneplus recovery so we can have root
Sent from my A0001 using Tapatalk
Flashed it already, here are the things I didn't like:
1) OPO doesn't charge. At all. I mean, if you connect the charger (doesn't matter if it's Power Bank or wall charger) phone will not discharge.
2) Vibration motor is active for too long for haptic feedback.
Won't be my daily driver just because of (1).
Evolitist said:
Flashed it already, here are the things I didn't like:
1) OPO doesn't charge. At all. I mean, if you connect the charger (doesn't matter if it's Power Bank or wall charger) phone will not discharge.
2) Vibration motor is active for too long for haptic feedback.
Won't be my daily driver just because of (1).
Click to expand...
Click to collapse
My OPO charges well,just like any cm rom or previous builds of oxygen
Maybe you should try to reinstall the rom?
Evolitist said:
Flashed it already, here are the things I didn't like:
1) OPO doesn't charge. At all. I mean, if you connect the charger (doesn't matter if it's Power Bank or wall charger) phone will not discharge.
2) Vibration motor is active for too long for haptic feedback.
Won't be my daily driver just because of (1).
Click to expand...
Click to collapse
With TWRP?
ancarloro said:
With TWRP?
Click to expand...
Click to collapse
No, did it entirely by the official guide.
Evolitist said:
No, did it entirely by the official guide.
Click to expand...
Click to collapse
Have you attempted to flash TWRP over Oneplus recovery after flashing the ROM since I've seen they say you can mess your phone, but what about after you've already installed the OS?
Sent from my A0001 using Tapatalk
Renosh said:
Have you attempted to flash TWRP over Oneplus recovery after flashing the ROM since I've seen they say you can mess your phone, but what about after you've already installed the OS?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Don't think it'll fix slow charging but... Who knows? Will try it in about an hour.
What's the modem version?
fards said:
What's the modem version?
Click to expand...
Click to collapse
It's .4.0.1.с7-00013
Evolitist said:
It's .4.0.1.с7-00013
Click to expand...
Click to collapse
Cheers yeah, just extracted it to check before you posted
Probably a stupid question but what version is this based off of? 6.0 or 6.0.1?
ShinnAsuka said:
Probably a stupid question but what version is this based off of? 6.0 or 6.0.1?
Click to expand...
Click to collapse
No, Lollipop 5.1.1.
ShinnAsuka said:
Probably a stupid question but what version is this based off of? 6.0 or 6.0.1?
Click to expand...
Click to collapse
Neither. It's 5.1.1 with December security patches.
K well that sucks a lot...
Evolitist said:
Don't think it'll fix slow charging but... Who knows? Will try it in about an hour.
Click to expand...
Click to collapse
So...did you try to flash TWRP?
~KV said:
So...did you try to flash TWRP?
Click to expand...
Click to collapse
Yep, nothing has improved at all.
Do not try to flash across twrp. IMEI lose. Read the info on the forum oneplus.
Sent from my 1+1
anyone can give me the system ui apk and framework folder plz thanks
Evolitist said:
Yep, nothing has improved at all.
Click to expand...
Click to collapse
I didn't expect it to improve anything just wanted to know if you can flash TWRP after the ROM has successfully been booted into and if you can root
Sent from my A0001 using Tapatalk
Just got NPD35K pushed to my phone. Hopefully some new stuff from the Google I/O?
I thought I wouldn't be able to receive updates with a rooted device and a custom kernel. Is this the new way of Android N system image pushing?
Apparently this is now the actual beta. And no longer a preview version. This counts as preview 3.
http://9to5google.com/2016/05/18/android-n-beta-by-google-today/
Just received it also. Great ... exciting!
Got it here too,so far,so good!!!
Sent from my Nexus 6 using XDA-Developers mobile app
I've never once taken an ota but I'm tempted. Is it safe to accept if you're decrypted?
Sent from my angler using XDA Labs
Were you unencrypted when you updated to it? I know TWRP doesn't work when it's encrypted (on N) so I'm waiting for the factory images to be released so I can modify those and stay unencrypted, but if it works anyway I'll update ASAP.
Hello. I want to take this update too. My bootloader is locked. Though i have enabled oem unlocking and usb debugging. Can i ota update to android n beta? I mean in case i get into bootloop. I have everything stock. Nothing changed. Currently on may update mob30i.
Encryptable boot/kernel for NPD35K:
https://www.androidfilehost.com/?fid=24549084345926183
What i wanted to ask was. Should i be safe in case o run into bootloop. Or brick my device?
Factory image is up http://storage.googleapis.com/androiddevelopers/shareables/preview/shamu-npd35k-factory-a33bf20c.tgz
XorZone said:
Factory image is up http://storage.googleapis.com/androiddevelopers/shareables/preview/shamu-npd35k-factory-a33bf20c.tgz
Click to expand...
Click to collapse
Downloading.
aoaleman said:
Encryptable boot/kernel for NPD35K:
https://www.androidfilehost.com/?fid=24549084345926183
Click to expand...
Click to collapse
lol, I found it by googling NPD35K, first link says "44 secs ago"
Can it be rooted?
Sent from my Nexus 6 using Xparent Cyan Tapatalk 2
XorZone said:
lol, I found it by googling NPD35K, first link says "44 secs ago"
Click to expand...
Click to collapse
The innernets are fast, I gotta be fast. lol
How long does boot take?
Been waiting awhile
trvbone said:
How long does boot take?
Been waiting awhile
Click to expand...
Click to collapse
Is it encrypting?
Sent from my angler using XDA Labs
aoaleman said:
the innernets are fast, i gotta be fast. Lol :d
Click to expand...
Click to collapse
gotta go fsat!
aoaleman said:
The innernets are fast, I gotta be fast. lol
Click to expand...
Click to collapse
So if i understand correctly, this is not forcing encryption, right?
DAmn it Encryption unsuccessful reset phone prompt..... anyway around this?
blackbird5308 said:
So if i understand correctly, this is not forcing encryption, right?
Click to expand...
Click to collapse
Correct. Leaves it alone as is. Should.
aoaleman said:
Correct. Leaves it alone as is.
Click to expand...
Click to collapse
Perfect. What mods are necessary? only ramdisk / fstab i think, right?
Does anyone know when those in the beta programme can expect this ,I though I read so.e where we were getting it this month
Sent from my Nexus 6P using XDA-Developers mobile app
This month
You answered your own question
Most likely last Wednesday of this month which would be 26th
combat goofwing said:
Does anyone know when those in the beta programme can expect this ,I though I read so.e where we were getting it this month
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
its available now...
no google assistant though
Just Got Update
I just received Beta Version N-MR1 (NPF10C). Settings-About Phone shows Android Version 7.1.1. Support is listed as another heading under Settings.
Came thru over OTA, install went smooth, phone loaded smooth. Used the fancy new reboot button once, stuck in a boot loop. Recovery will not load either, just boot looping the google logo. Oddly cannot turn phone off in bootloader, it shuts down then starts itself up again to reboot loop, sorta funny yet annoying to have to flash back to 7.0 some bad karma here.
dajoey said:
no google assistant though
Click to expand...
Click to collapse
It's specifically only for the Pixel at this point. You can flash the Assistant mod, wipe app data, and you should get Assistant.
Howie Dub said:
It's specifically only for the Pixel at this point. You can flash the Assistant mod, wipe app data, and you should get Assistant.
Click to expand...
Click to collapse
Nope. Don't use the mod on 7.1.
You wont be able to boot.
AchillesTheGod said:
Nope. Don't use the mod on 7.1.
You wont be able to boot.
Click to expand...
Click to collapse
I booted just fine
Howie Dub said:
I booted just fine
Click to expand...
Click to collapse
Witch mod did you use. Maybe I used a different one
AchillesTheGod said:
Witch mod did you use. Maybe I used a different one
Click to expand...
Click to collapse
I used the flash method in this thread http://forum.xda-developers.com/android/software/guide-how-to-enable-google-assistant-t3477879
I only flashed the build.prop zip, not the velvet one. Couldn't get Assistant to work when I flashed both.
Just took OTA 7.1 smooth. Camera is a little different but don't see a focus lock.
Howie Dub said:
I used the flash method in this thread http://forum.xda-developers.com/android/software/guide-how-to-enable-google-assistant-t3477879
I only flashed the build.prop zip, not the velvet one. Couldn't get Assistant to work when I flashed both.
Click to expand...
Click to collapse
Thanks that was probably my mistake.
---------- Post added at 04:40 AM ---------- Previous post was at 04:24 AM ----------
Nope. Just tired it. Booted up. But no Assistant. Stock and rooted.
Downloading now -- 1263.5MB, wow!
Guessing the pixel launcher is still only for pixel phones as it's not in the beta. Shame
I flashed the pixel launcher and got this weird mic...
AchillesTheGod said:
I flashed the pixel launcher and got this weird mic...
Click to expand...
Click to collapse
That's when you don't have "OK Google everywhere" set up.
AchillesTheGod said:
I flashed the pixel launcher and got this weird mic...
Click to expand...
Click to collapse
How did you get it to show the weather? Mine shows date only.
Enviado desde mi Nexus 6P mediante Tapatalk
I think you have to give Location permission to the Pixel Launcher app.
Everyone on the beta, check for system update ?
thank you for the info. i just done,install it. [emoji3]
Sent from my [device_name] using XDA-Developers Legacy app
smooth update: just removed the -w from flash-all script, booted once, went back to TWRP to flash latest Flash Kernel + Magisk.
Fails safety net for me no more Google pay
1. Can I flash this (removing -w) over july 8.1.0 and keep all my apps and settings?
2. Is it already good enough as a daily driver?
r3act said:
1. Can I flash this (removing -w) over july 8.1.0 and keep all my apps and settings?
2. Is it already good enough as a daily driver?
Click to expand...
Click to collapse
Yes and yes
Sent from my Pixel 2 using Tapatalk
Thanks! One more noobish question. Can I revert to a full TWRP backup (including vendor etc) if for some reason I want to revert back to stock 8.1?
r3act said:
Thanks! One more noobish question. Can I revert to a full TWRP backup (including vendor etc) if for some reason I want to revert back to stock 8.1?
Click to expand...
Click to collapse
You will need to perform a full backup, transfer the twrp folder to PC, flash vendor image, then flash twrp,then transfer over backup to restore.
After two cycles from 100-0. With latest ElementalX kernel and Helix engine.
danbrown162 said:
Fails safety net for me no more Google pay
Click to expand...
Click to collapse
have you tried to install a custome kernel? if i remember right, it should be enough to install a kernel for that..
I flashed it and in my enthousiasm forgot to remove the -w so it became a clean install...
DP4 is already a major upgrade over 8.1.0 with lots of new features. The portrait mode in the new camera app is great and also no intermittent wifi drops anymore.
Indeed its good enough as a daily driver so I'm staying on it now.
Xposed and v4a working?
Sent from my Pixel 2 using my fingers on the keyboard.
shortyboy said:
After two cycles from 100-0. With latest ElementalX kernel and Helix engine.
Click to expand...
Click to collapse
is safety net working for you?
thanks!
Safety net not working for me either.
jasonbiggs said:
Xposed and v4a working?
Sent from my Pixel 2 using my fingers on the keyboard.
Click to expand...
Click to collapse
I couldn't get Xposed to install, but V4A is working great. Safety net also is not passing for me, I'm using latest Flash kernel.
Thanks guys, then I'll wait untill we find a solution for safety net, Google pay is a priority for me
daede86 said:
is safety net working for you?
thanks!
Click to expand...
Click to collapse
safety new is not working with latest magisk 16.6
r3act said:
I flashed it and in my enthousiasm forgot to remove the -w so it became a clean install...
DP4 is already a major upgrade over 8.1.0 with lots of new features. The portrait mode in the new camera app is great and also no intermittent wifi drops anymore.
Indeed its good enough as a daily driver so I'm staying on it now.
Click to expand...
Click to collapse
What's new about the portrait mode on DP4?
daede86 said:
Thanks guys, then I'll wait untill we find a solution for safety net, Google pay is a priority for me
Click to expand...
Click to collapse
I'm using the element kernel for Android P and safety net is passing for me. That said, I haven't re-rooted the device as of yet so I'm just unlocked currently.
Safety net is working for me on Magisk 16.6, and latest ElementalX kernel.
Installing the update right now. It'll be the first security update for Pixel 3a.
Here's a link with more details and download links, no 3a specific fixes in the June patch.
https://9to5google.com/2019/06/03/pixel-june-19-security-patch/
Thanks. I checked around 9 EDT but nothing new. Still locked so sideloaded.
I have a T-Mobile 3a (locked bootloader). I sideloaded the beta q but want to go back to pie. Can I sideload the ota to go back to pie?
dhoang said:
I have a T-Mobile 3a (locked bootloader). I sideloaded the beta q but want to go back to pie. Can I sideload the ota to go back to pie?
Click to expand...
Click to collapse
I don't believe so but... Try and let us know how it turns out. I think the bootloader and stuff is different so I think you need factory image
Sent from my Pixel 3a using Tapatalk
Is it save to update if you're rooted?
jmtjr278 said:
I don't believe so but... Try and let us know how it turns out. I think the bootloader and stuff is different so I think you need factory image
Click to expand...
Click to collapse
It does not work. It was running for a bit then an error message"missing config CONFIG NETFILTER_XT_MATCH_QTAGUID". Oh well I tried. I guess I will have to wait until Google officially includes 3a in it beta program.
BehelitOutlaw said:
Is it save to update if you're rooted?
Click to expand...
Click to collapse
Yup. Works just fine. Just fastboot the modded boot.img provided by @pbanj afterwards and your good to go
Sent from my Pixel 3a using Tapatalk
Your running the old boot.img? Do you know if there is a problem with altering the new boot.img with magisk?
jmtjr278 said:
Yup. Works just fine. Just fastboot the modded boot.img provided by @pbanj afterwards and your good to go
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
Archangel said:
Your running the old boot.img? Do you know if there is a problem with altering the new boot.img with magisk?
Click to expand...
Click to collapse
Nah. Check his first post. He's updated to the June modded boot.img. Save yourself since time and data because the OTA does not include the boot img that I could find. I downloaded the factory image to get it. Then I downloaded the OTA. Ugh. Almost 3gb if data by the time I was finished.
Sent from my Pixel 3a using Tapatalk
---------- Post added at 09:43 PM ---------- Previous post was at 09:32 PM ----------
jmtjr278 said:
Nah. Check his first post. He's updated to the June modded boot.img. Save yourself since time and data because the OTA does not include the boot img that I could find. I downloaded the factory image to get it. Then I downloaded the OTA. Ugh. Almost 3gb if data by the time I was finished.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
https://drive.google.com/file/d/1eQ9QXQqYeQityqCR2fk2jgBt7UKBA_5P/view?usp=drivesdk
Here is the one I made. Enjoy
Sent from my Pixel 3a using Tapatalk
dhoang said:
I have a T-Mobile 3a (locked bootloader). I sideloaded the beta q but want to go back to pie. Can I sideload the ota to go back to pie?
Click to expand...
Click to collapse
No. Cannot go back to pie. I had a discussion with Google rep today. She said soon as the Q beta for this month comes out, we will be able to go back to Android Pie as normal. There is an issue on their side. Here's what my error was when trying to sideload back to Pie on my VZW Pixel 3a
Perfect thanks brother! Saves me some time.
jmtjr278 said:
Nah. Check his first post. He's updated to the June modded boot.img. Save yourself since time and data because the OTA does not include the boot img that I could find. I downloaded the factory image to get it. Then I downloaded the OTA. Ugh. Almost 3gb if data by the time I was finished.
Sent from my Pixel 3a using Tapatalk
---------- Post added at 09:43 PM ---------- Previous post was at 09:32 PM ----------
https://drive.google.com/file/d/1eQ9QXQqYeQityqCR2fk2jgBt7UKBA_5P/view?usp=drivesdk
Here is the one I made. Enjoy
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
sd_N said:
No. Cannot go back to pie. I had a discussion with Google rep today. She said soon as the Q beta for this month comes out, we will be able to go back to Android Pie as normal. There is an issue on their side. Here's what my error was when trying to sideload back to Pie on my VZW Pixel 3a
Click to expand...
Click to collapse
Did you try to fastboot pie factory images? That should get you back to pie, kinda weird if not.
Sent from my Pixel 3a using Tapatalk
jmtjr278 said:
Did you try to fastboot pie factory images? That should get you back to pie, kinda weird if not.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
He has a VZW Pixel 3a. You can't fastboot a factory image with a locked bootloader. You can only sideload an OTA so he will need to wait in order to unenroll from the beta. Couple more days I think at the most.
Anyone else feel like the Multi tasking UI on the 3a has become faster after the update? Feels snappier to me
Rage1ofakind said:
Anyone else feel like the Multi tasking UI on the 3a has become faster after the update? Feels snappier to me
Click to expand...
Click to collapse
I think so. I have noticed you can swipe up from a bigger portion of the screen to show the appdrawer too. Now I can swipe up from the lower row of icons, and I think that before the update I had to swipe from the icon menu.
How do you even sideload the OTA ? When I do adb reboot recovery I just get a no command screen :/
EDIT: NVM Figured that out. When I sideload the OTA, I just get a signature verification failed error. I have a Tmobile 3a
Edit 2: I am dumb. I had the full image instead of OTA. Getting the OTA worked.
So i download the latest modded version on from pnabj "PQ3B.190605.006" then install it using this method "fastboot flash boot "whatever the boot.img is named" from the root guide and thats it?
oscar1823 said:
So i download the latest modded version on from pnabj "PQ3B.190605.006" then install it using this method "fastboot flash boot "whatever the boot.img is named" from the root guide and thats it?
Click to expand...
Click to collapse
If you have updated to the June security version and want to obtain root, then yes, flash the specific modified boot image. Then open the Magisk app and patch your boot image to complete the process.
12paq said:
If you have updated to the June security version and want to obtain root, then yes, flash the specific modified boot image. Then open the Magisk app and patch your boot image to complete the process.
Click to expand...
Click to collapse
Im already Rooted with magisk.
oscar1823 said:
Im already Rooted with magisk.
Click to expand...
Click to collapse
What are trying to do with the previously mentioned modified image?