Related
Looks like they finally released 7.0.0 software for the 5x, NRD90M
https://developers.google.com/android/nexus/images
yep time to factory flash. 6p is missing, sounds like there is more issues over there.
Just noticed, downloading now!
Already flashed. So far things are great and fluid. All my apps restored including data, did not even have to log in. Impressed.
Sent from my Nexus 5X using Tapatalk
Did you guys need to do a factory reset to flash to Android 7 from 6.0.1?
All restored by the android internal backup? Or did you use titanium or something else?
Sent from my Nexus 5X using XDA Free mobile app
Can anyone confirm if this supports the Vulcan api?
Sent from my Nexus 5X using XDA-Developers mobile app
What is difference between OTA and factory image?
All partion became same finally?
helioXverse said:
Looks like they finally released 7.0.0 software for the 5x, NRD90M
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I've been holding it until the final release ... pushing the OTA now ...
"C:\Users\blabla\Downloads>adb sideload bullhead-ota-nrd90m-fdb8250a.zip
serving: 'bullhead-ota-nrd90m-fdb8250a.zip' (~56%)"
***Update: It finished, and working great so far! Since I pushed the OTA there was no need to reinstall any apps or restore app data. However, when I have some free time (2-3 hours), I'd like to do a fresh factory install to compare performance. I didn't run into any issues with the OTA yet.
Commodore 64 said:
I've been holding it until the final release ... pushing the OTA now ...
"C:\Users\blabla\Downloads>adb sideload bullhead-ota-nrd90m-fdb8250a.zip
serving: 'bullhead-ota-nrd90m-fdb8250a.zip' (~56%)"
***Update: It finished, and working great so far! Since I pushed the OTA there was no need to reinstall any apps or restore app data. However, when I have some free time (2-3 hours), I'd like to do a fresh factory install to compare performance. I didn't run into any issues with the OTA yet.
Click to expand...
Click to collapse
If you full ota and wiped data after it's all really the same, really. [emoji18]
Inviato dal mio Nexus 5X utilizzando Tapatalk
m4ssnet said:
If you full ota and wiped data after it's all really the same, really. [emoji18]
Inviato dal mio Nexus 5X utilizzando Tapatalk
Click to expand...
Click to collapse
Thank you for saying this.
Sent from my Nexus 5X using Tapatalk
iamterence said:
Thank you for saying this.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Actually that's not true. It mostly depends from which DP you started receiving updates. eg. I clean installed DP5, which had some features removed (eg. night mode, and it's also missing from the final), whereas someone who started clean from DP1 will have it on the final. For the final I guess they were waiting to update the Google Apps, such as Connectivity Services which got updated after the final OTA.
Noobish q, can this be flashed trough TWRP? Im on Pure Nexus 6.0.1
5ageman said:
Noobish q, can this be flashed trough TWRP? Im on Pure Nexus 6.0.1
Click to expand...
Click to collapse
No, fastboot
I'll do it late tonight when I have time to spend doing a full wipe. I'm not looking forward to the fight to root it though. From what I understand, Google is cracking down on rooting.
I had no real issues with OTA. Things seem to be even better after a fresh factory flash.
Sent from my Nexus 5X using Tapatalk
voyagerfan99 said:
I'll do it late tonight when I have time to spend doing a full wipe. I'm not looking forward to the fight to root it though. From what I understand, Google is cracking down on rooting.
Click to expand...
Click to collapse
It's really really really hard to root this phone. Fastboot flashing TWRP then flashing SuperSU in TWRP is tough. I don't know how I ever did it.
When someone that knows what they are talking about says Android is getting harder to root, they mean for those that initially find it (chainfire), not the user. For you and I, it's only a matter of flashing a cute little zip in our custom recovery.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
It's really really really hard to root this phone. Fastboot flashing TWRP then flashing SuperSU in TWRP is tough. I don't know how I ever did it.
When someone that knows what they are talking about says Android is getting harder to root, they mean for those that initially find it (chainfire), not the user. For you and I, it's only a matter of flashing a cute little zip in our custom recovery.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
So latest twrp and super su works on 7.0.0?
Sent from my Nexus 5X using XDA-Developers mobile app
Bonez1802 said:
So latest twrp and super su works on 7.0.0?
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
It's really really really hard to root this phone. Fastboot flashing TWRP then flashing SuperSU in TWRP is tough. I don't know how I ever did it.
When someone that knows what they are talking about says Android is getting harder to root, they mean for those that initially find it (chainfire), not the user. For you and I, it's only a matter of flashing a cute little zip in our custom recovery.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I understand that, but I read this article (a month old) talking about the secure boot and only being able to boot and use partial operating system features if it detects corruption, such as rooting.
http://betanews.com/2016/07/20/android-7-0-nougat-root/
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
I generated Chainfire`s CF-Auto-Root, so you can try use it.
1. Download and unpack CFAR-taimen-default.zip.
2. Reboot your device into bootloader mode.
3. Install standart fastboot drivers.
4. Run "root.bat" file.
This batch file unlock your bootloader (if it`s not) and boot modified kernel.
Wait, when device automaticaly reboot. Then just install SuperSU apk.
Download: https://drive.google.com/open?id=0B4acSOboIe6RQXpYNVp5NXJ1Ync
I do not give any guarantees of it. If it causes bootloop - flash factory image.
Tell me if it works.
Tell me if it works.
Click to expand...
Click to collapse
LOL
Much wiser to simply wait for official post from Chainfire.
Born<ICs said:
Much wiser to simply wait for official post from Chainfire.
Click to expand...
Click to collapse
Yup. This method doesn't work. I already gave it a shot. SuperSU just states "Root undetected". At least I didn't get a bootloop...
Born<ICs said:
Much wiser to simply wait for official post from Chainfire.
Click to expand...
Click to collapse
Didn't @Chainfire retired?
Born<ICs said:
Much wiser to simply wait for official post from Chainfire.
Click to expand...
Click to collapse
lucky_strike33 said:
Didn't @Chainfire retired?
Click to expand...
Click to collapse
Yes he did just a week or so ago.
I'm pretty sure chainfire retired and we will have to wait for magisk now
Sent from my Pixel 2 XL using XDA-Developers Legacy app
bajasur said:
I'm pretty sure chainfire retired and we will have to wait for magisk now
Sent from my Pixel 2 XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
And the magisk Dev just finally got the pixel one, so we maybe waiting awhile. I was thinking we might want to start a fund for either him or goodwin_c he's the one who built the unofficial versions of magisk most of this year for our og pixels. I have talked to him and he doesn't plan on getting one.
Firmware.mobi (Chainfire's site) has an option to automatically generate and download a CFAR package. Was the OP generated using this site? If not, someone should try that route.
Never mind. It was. Ignore me.
Still on a pixel xl 1. So sorry if thos is off base, but has anyone tried to use our method on this phone? Boot to the twrp image then flash Chainfires latest SU?
I am guessing it is TWRP that fails?
TonikJDK said:
Still on a pixel xl 1. So sorry if thos is off base, but has anyone tried to use our method on this phone? Boot to the twrp image then flash Chainfires latest SU?
I am guessing it is TWRP that fails?
Click to expand...
Click to collapse
There is currently no TWRP for this device.
TonikJDK said:
Still on a pixel xl 1. So sorry if thos is off base, but has anyone tried to use our method on this phone? Boot to the twrp image then flash Chainfires latest SU?
I am guessing it is TWRP that fails?
Click to expand...
Click to collapse
Twrp fails. SuperSU 2.82 SR1 boot to root fails.
lucky_strike33 said:
Didn't @Chainfire retired?
Click to expand...
Click to collapse
Apparently CCMT has been running SuperSU for the last couple years anyways: http://www.androidpolice.com/2017/10/03/chainfire-announces-end-involvement-supersu/
So it's possible that the CCMT team will update SuperSU for Pixel 2 devices.
arh2o said:
Apparently CCMT has been running SuperSU for the last couple years anyways: http://www.androidpolice.com/2017/10/03/chainfire-announces-end-involvement-supersu/
So it's possible that the CCMT team will update SuperSU for Pixel 2 devices.
Click to expand...
Click to collapse
Assuming they have the device?
arh2o said:
Apparently CCMT has been running SuperSU for the last couple years anyways: http://www.androidpolice.com/2017/10/03/chainfire-announces-end-involvement-supersu/
So it's possible that the CCMT team will update SuperSU for Pixel 2 devices.
Click to expand...
Click to collapse
They bought it a couple years ago, but Chainfire's still been actively developing with them, until the beginning of October when he finally "quit". He's still going to consult until the end of February though, so there might still be hope that he will be able to assist and speed things up for us! XDA Article About It Here
Boot to TWRP just fails in Fastboot. It just reboots the phone to bootloader. ?
Can confirm that this does NOT work. Will wipe your phone without giving you root. I have my bootloader unlocked as well. Seems we'll have to wait for a better solution.
Maybe it's just me but I feel like the title of this should be changed because it could be a bit misleading for many people. There is also already a topic for WIP Magisk so we shouldn't split topics on trying to get root into several areas.
Not So Pro said:
Maybe it's just me but I feel like the title of this should be changed because it could be a bit misleading for many people. There is also already a topic for WIP Magisk so we shouldn't split topics on trying to get root into several areas.
Click to expand...
Click to collapse
lol. there are lots of posts from people who have no clue what they're doing, posting guides like they know what they're doing. and just as many who don't have the device, saying 'try this!'
i dunno if any REAL devs even got this device or have any interest, seems like no.
but seriously, like we didn't try cf-auto-root yet? lol. lol...
Magisk and CF Auto Root are 2 different things but I do agree this one should be removed or even say WIP.
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?