[help] Android N preview 3 {AOSP} building - Nexus 5X Q&A, Help & Troubleshooting

ok, so I got the android N preview 3 AOSP downloaded and built for bullhead (Nexus 5x). Flashed it (boot.img, cache.img, recovery.img, system.img, userdata.img) to the device but it won't work...
I thought that maybe I was missing the vendor partition, so I got the npd35k stock image which is preview 3 and flashed the vendor.img via fastboot.
still nothing....
I would appreciate if anyone can provide some help, pointers etc...
Daniel.

How did you build this? When was source released?
Sent from my SM-G930V using Tapatalk

Related

Nexus 7 2013 Wifi to Marshmellow without locking boot?

Dear all, like many of you know the factory images for this device has been released. My question is if I extract the file and use the found ROM zip to flash in TWRP, will it work?
8166uy said:
Dear all, like many of you know the factory images for this device has been released. My question is if I extract the file and use the found ROM zip to flash in TWRP, will it work?
Click to expand...
Click to collapse
The archive from Google contains a flashing script that uses fastboot from a PC. As far as I know, you can't install a factory image from a custom recovery.
You can fastboot flash system and boot which is like a dirty flash. It worked fine for me from the latest Lolipop release. Seems to work fine so far.

Stock flashable zip usb broken

Hello guys, i have a problem with my nexus 5X: the type-c port doesn't work anymore for pc transfers (i tried with 3 different cables and 2 PCs), i guess that only the data rail is gone because the charging still works.
My problem is that i don't have the stock rom and i need it to send it back for warranty so i'd like to ask if someone can give me a link to flash the stock rom (and recovery!!) to flash everything through twrp and if it is possible.
Thanks, Luca
harkan91 said:
Hello guys, i have a problem with my nexus 5X: the type-c port doesn't work anymore for pc transfers (i tried with 3 different cables and 2 PCs), i guess that only the data rail is gone because the charging still works.
My problem is that i don't have the stock rom and i need it to send it back for warranty so i'd like to ask if someone can give me a link to flash the stock rom (and recovery!!) to flash everything through twrp and if it is possible.
Thanks, Luca
Click to expand...
Click to collapse
What you're asking for only exists in one place.
https://developers.google.com/android/images
Your main option is to download the latest factory image. Unzip the archive so that you have the system, boot, and vendor images available. Boot into TWRP 3.0+ and do a factory reset then select Install/Install image to flash those three images individually. Bootloader and radio cannot be installed in this manner.
Your alternative is to use the Google stock Full OTA images:
https://developers.google.com/android/ota
Then use Flashfire to install this image:
https://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
What you're asking for only exists in one place.
https://developers.google.com/android/images
Your main option is to download the latest factory image. Unzip the archive so that you have the system, boot, and vendor images available. Boot into TWRP 3.0+ and do a factory reset then select Install/Install image to flash those three images individually. Bootloader and radio cannot be installed in this manner.
Your alternative is to use the Google stock Full OTA images:
https://developers.google.com/android/ota
Then use Flashfire to install this image:
https://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
thanks for you comment: i didn't know that i can flash stock rom too through twrp recovery
if i install flashfire i would be able to flash the recovery?
harkan91 said:
thanks for you comment: i didn't know that i can flash stock rom too through twrp recovery
if i install flashfire i would be able to flash the recovery?
Click to expand...
Click to collapse
Yes it can. Btw, stock recovery will replace TWRP on reboot if you flash Nougat images for boot, system, and vendor in TWRP.
Sent from my Nexus 5X using Tapatalk

[KERNEL] Stock Kernel + SafetyNet Patch

Stock Pixel 2 XL Kernel + SafetyNet Patch
Current version: android-9.0.0_r0.112
Suitable for build(s): All August 2019 builds
Suitable for devices(s): Pixel 2 XL (taimen)
I compiled the stock kernel for the Pixel 2 XL/Pixel 2 and applied the SafetyNet patch by sultanxda.
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay and Netflix.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This kernel is only for the builds listed above!!!! This will not work on any prior build.
- All stock features will work with this kernel (since it's just the stock kernel + patch).
- If you do not have an unlocked bootloader there is no need to use this kernel. It's exactly the same as the stock kernel, except with the addition of the SafetyNet patch.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- This will not remove the "device corrupted" warning when the phone is turned on or rebooted.
Installation:
- Be prepared with backups or the factory image from Google in case you do something wrong
- Extract boot image from zip file
- Test with command: fastboot boot filename.img
- Flash with command: fastboot flash boot filename.img
**WARNING**
If flashing this kernel for whatever reason ruins your device, I am not accountable. Use this at your own risk!
The current version will always be attached to this post (check the Downloads tab). Older versions can be found HERE.
XDA:DevDB Information
Stock Kernel + SafetyNet Patch, Kernel for the Google Pixel 2 XL
Contributors
iissmart
Kernel Special Features:
Version Information
Status: Beta
Created 2017-11-18
Last Updated 2017-12-11
Will this still allow OTAs?
Testing via fastboot boot worked like a charm. Could not flash the kernel, however. I get:
sending 'kernel' (18887 KB)...
OKAY [ 0.601s]
writing 'kernel'...
FAILED (remote: No such partition.)
finished. total time: 0.610s
I'm unlocked, but otherwise stock.
I get the same message as facted - booting works fine but can't flash the kernel.
Hm, I might need help getting the flashing instructions working for a Pixel 2 XL. It works fine on a Pixel 2 (which is what I have), so I assumed it was the same for both.
I'll look around and see what others are doing.
I don't have time right now to test, but I wonder if I need a new adb. In have a version installed from a few months ago. I'll test later this afternoon and get back to you.
Shouldn't the flash command be:
fastboot flash boot <boot.img>
Sent from my Pixel 2 XL using XDA Labs
Yes it is.
So "fastboot flash boot" works with my kernel image? If so I'll update OP.
iissmart said:
So "fastboot flash boot" works with my kernel image? If so I'll update OP.
Click to expand...
Click to collapse
Unfortunately, this causes a frozen screen at the G on boot. Giving it time, but it's been a few minutes and not looking good...
EDIT: Gave it a few more minutes (maybe 10 total) and still nothing, so I just reflashed the factory image without wiping and all good. But this method (or your kernel) does not work with stock Nov. Gonna try one of the other kernels.
Maybe it can't tell which is the active partition for boot? Maybe you guys need to modify the command to the a or b partition?
OP was right. The command is fastboot flash kernel kernelname. Kernel only flashes the kernel inside of the boot image, whole boot images are supposed to have a kernel and ramdisk.
For those of you who can't flash 'kernel', just update fastboot from the platform tools site Google proveds. It'll work like a charm.
I updated fastboot, but still get the same error...
Can someone on the January 2018 build test the new boot image I've attached to OP? This is a full boot image with the patched kernel included, so it needs to be flashed with "fastboot flash boot filename.img" after extracting from the zip file.
There has been talk of TWRP touch issues with stock kernel. Maybe you can talk with one of the kernel devs about adding drivers to your build. If indeed this is the actual root cause of said touch issues. Lol
iissmart said:
Can someone on the January 2018 build test the new boot image I've attached to OP? This is a full boot image with the patched kernel included, so it needs to be flashed with "fastboot flash boot filename.img" after extracting from the zip file.
Click to expand...
Click to collapse
I flashed the latest one you had up on the 5th and it worked fine for me. Flashed with the fastboot flash boot file.img with no issue. SafetyNet is good, no issues with it at all.
Just for reference, I'm running a Magisk installed 8.1 stock build with all current security patches.
KyleK29 said:
I flashed the latest one you had up on the 5th and it worked fine for me. Flashed with the fastboot flash boot file.img with no issue. SafetyNet is good, no issues with it at all.
Just for reference, I'm running a Magisk installed 8.1 stock build with all current security patches.
Click to expand...
Click to collapse
Thanks. I've updated OP to reference the boot image for January 2018. Should work fine for everyone now!
iissmart said:
Thanks. I've updated OP to reference the boot image for January 2018. Should work fine for everyone now!
Click to expand...
Click to collapse
Also worked great for me. Jan build, stock. Although I didn't see anything attached to OP, but I followed the link you provided and simply found the most recent file.
Android Pay works, woo hoo!
which file should I download for Jan?
kernel_wahoo_android-8.1.0_r0.13.zip ? or boot_wahoo_android-8.1.0_r0.13.img.zip?
Thanks!
facted said:
which file should I download for Jan?
kernel_wahoo_android-8.1.0_r0.13.zip ? or boot_wahoo_android-8.1.0_r0.13.img.zip?
Thanks!
Click to expand...
Click to collapse
The boot image.
FYI- I've updated OP with the mid-month update to r0.18.

bootloop flashing final build of 8.1

I have a pixel 2 xl it updated no problem I was on the DP2 My wifes Pixel xl samething DP2 then downloaded the 8.1 img used dueces script to flash and I get a bootloop there were no errors I flashed multiple times and it will not boot. tried to flash the OTA It won't let me says the time stamp is wrong. I need to get this thing working I am now downloading the Nov sec update for 8.0 ans attempting to flash the boot.img thinking this may have a bad boot.img andy help would be appreciated.
bigv5150 said:
I have a pixel 2 xl it updated no problem I was on the DP2 My wifes Pixel xl samething DP2 then downloaded the 8.1 img used dueces script to flash and I get a bootloop there were no errors I flashed multiple times and it will not boot. tried to flash the OTA It won't let me says the time stamp is wrong. I need to get this thing working I am now downloading the Nov sec update for 8.0 ans attempting to flash the boot.img thinking this may have a bad boot.img andy help would be appreciated.
Click to expand...
Click to collapse
If you are flashing the boot IMG then it's unlocked right? Download the whole image and edit the flash all bat file and remove the -w in it. Then flash the whole thing.
TonikJDK said:
If you are flashing the boot IMG then it's unlocked right? Download the whole image and edit the flash all bat file and remove the -w in it. Then flash the whole thing.
Click to expand...
Click to collapse
Either it is an issue with a bad download or i screwed up putting all the files in Deuces script Im not sure. I unpacked the img files again and ran the flash all like normal removing the erase all data I got a bunch of archive missing boot recovery etc. then it gave me the bootloader version and it started flashing again. Long story short it booted up and I am on the dec security update and the latest build. I thinking I will just modify the flash all script from now on and just flash img that way. Thanks for the reply.
Or you are using a custom kernel that doesnt support 8.1

your device is corrupt on any rom

hi guys,
i'm in trouble "your device is corrupt. it can't be trusted and may not work properly.", this problem happened after trying to update to android p beta 2.
that all what i did :
1- unlock the bootloader using adb and this command "fastboot flashing unlock_critical"
2- flash factory image "android p beta 2" by clicking on flash-all.bat. (the flash is downloaded from here for pixel 2 xl )
3- after flash done, and start my phone i get the error mentioned above ! and the phone can't boot !
i tried to get back to 8.1, so i downloaded the factory image from google server and flashed it using adb, but i still get the error ! i'm sure i install the official stock rom, but it also not working !!
please help because i've just buying this used pixel 2 xl today.
solution is : flash any ROM you want using the lastest version of ADB, i used this one HERE, and it's succeeded.
Try using Dueces Recovery Script, this will flash stock image to both slots.
Sent from my Pixel 2 XL using XDA Labs
Or flash it via fastboot to both slots

Categories

Resources