Related
Hi,
Long time reader, first time poster. I just unlocked the bootloader and flashed the latest franco nightly with fastboot and have two questions:
1. From what I've understood, in order to perform OTA updates, I have to be on the stock kernel. Do I just flash the stock boot.img extracted from the factory image? I think I may have read something about additional changes being done to the system partition after flashing a custom kernel, but I can't seem to find the thread.
2. If I want to flash a different kernel or update the existing one, do I just flash the fastboot image? Does it just overwrite the existing one or do I have to perform any additional steps, like a wipe?
I have not flashed a custom recovery or rooted the device and would like to keep it that way.
Yes. Some kernels do modify system files. If you wanted to get back to stock for an ota you'd flash both the boot.img and the system.img
Sent from my Nexus 4 using xda premium
El Daddy said:
Yes. Some kernels do modify system files. If you wanted to get back to stock for an ota you'd flash both the boot.img and the system.img
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks for the quick reply.
Do I keep my current settings and SMS messages when I flash system.img?
I'm guessing this is only necessary before performing an OTA update. If I'm only updating the kernel I just flash boot?
Eregoth said:
Thanks for the quick reply.
Do I keep my current settings and SMS messages when I flash system.img?
I'm guessing this is only necessary before performing an OTA update. If I'm only updating the kernel I just flash boot?
Click to expand...
Click to collapse
Yep your data will stay intact.
Yep just flash boot. Some say you should clear dalvik cache as well.
Sent from my Nexus 4 using Tapatalk 4 Beta
And what am i doing wrong, when the bootloader is not ending? i have root, unlocked bootloader, fancy kernel, cwmr and louder mod. i reverted the mod. flashed boot, system and recovery back to stock. i also want to perform an ota update.
Hey XDA,
My Nexus ha been a dream. Though I've hit a few bumps, I don't expect to waste money on other flagships again.
I don't need to be able to right this instant, but wiping cache is one of my regular troubleshooting tools. Upon troubleshooting an MMS issue I was having, I discovered my recovery wasn't working properly. Though I fixed the MMS issue by resetting APN settings, the recovery thing has been bothering me.
I am running stock and locked. I have done nothing to this phone to warrant it being my fault. The problem is simple (and a Google search indicated, common). When you get to Recovery, you get a droid on its back, a red exclamation mark and "NO COMMAND". Doesn't matter if you hold up and power, tap up, or get there from the bootloader. The recovery software is seemingly missing completely.
I have an extended warranty through the retailer I bought from, but the phone is otherwise fine, so this is a last resort.
My dilemma is that I want to use Android pay. My understanding is that even unlocking the bootloader breaks Android pay. Is this correct? If so, can one reliably reset the phones security trips to allow Android pay after flashing the recovery back on?
Thanks for the help.
No, unlocking the boot loader does not block Android Pay.
There is a systemless root method for the Nexus that allows you to use Android Pay while rooted, there are also a couple of ROMS that have it working currently as well.
celsian said:
No, unlocking the boot loader does not block Android Pay.
There is a systemless root method for the Nexus that allows you to use Android Pay while rooted, there are also a couple of ROMS that have it working currently as well.
Click to expand...
Click to collapse
Quite so? Can you provide links to the root method and mayhaps the roms? Does this mean I could slap TWRP on here with no consequence?
Android pay already patched systemless root. If you want Android pay don't root. You can unlock though. That will not affect Android pay.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
Android pay already patched systemless root. If you want Android pay don't root. You can unlock though. That will not affect Android pay.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Does this mean that I can't flash at least a stock recovery?
Download your system image, unzip it, unlock your bootloader and flash only the recovery.IMG in fastboot, then relock your bootloader again. Android Pay will work fine and your warranty won't be affected so long as you relock your bootloader
Arcaed said:
Does this mean that I can't flash at least a stock recovery?
Click to expand...
Click to collapse
Yes. Myself I would flash full image and start over fresh. But you can go with just recovery if you want. Also do not forget to check allow oem unlock in dev settings before attempting to unlock. If you want twrp you will need modified stock boot image with DM verity removed. Or else it won't boot. I can link you to one from the newest image if you'd like. But if you only want stock recovery you don't need anything other than stock Google image.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
Yes. Myself I would flash full image and start over fresh. But you can go with just recovery if you want. Also do not forget to check allow oem unlock in dev settings before attempting to unlock. If you want twrp you will need modified stock boot image with DM verity removed. Or else it won't boot. I can link you to one from the newest image if you'd like. But if you only want stock recovery you don't need anything other than stock Google image.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Sorry, but are you saying if I wanted to install twrp I would need a modified stock boot img?
The Stig 04 said:
Sorry, but are you saying if I wanted to install twrp I would need a modified stock boot img?
Click to expand...
Click to collapse
Yes.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
Yes. Myself I would flash full image and start over fresh. But you can go with just recovery if you want. Also do not forget to check allow oem unlock in dev settings before attempting to unlock. If you want twrp you will need modified stock boot image with DM verity removed. Or else it won't boot. I can link you to one from the newest image if you'd like. But if you only want stock recovery you don't need anything other than stock Google image.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
In that case, where do I get a full system flash?
Arcaed said:
In that case, where do I get a full system flash?
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
Sent from my Nexus 6P using Tapatalk
There are quite a few errors in the information given in this thread.
1. Unlocking the bootloader does not break Android Pay.
2. Android Pay has been patched so you can't have root with Android Pay, even systemless.
3. TWRP recovery does not require a modified boot.img.
4. Flashing any recovery (Stock or TWRP) will not affect Android Pay at all.
If you need directions on unlocking or flashing check my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
There are quite a few errors in the information given in this thread.
1. Unlocking the bootloader does not break Android Pay.
2. Android Pay has been patched so you can't have root with Android Pay, even systemless.
3. TWRP recovery does not require a modified boot.img.
4. Flashing any recovery (Stock or TWRP) will not affect Android Pay at all.
If you need directions on unlocking or flashing check my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
You beat me to it with #3. Unfortunately I'm at work and couldn't come back to this thread quickly enough.
toknitup420 said:
Android pay already patched systemless root. If you want Android pay don't root. You can unlock though. That will not affect Android pay.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Actually AP now works with systemless root again. I have AP working (yes actually making purchases), currently running the latest Chroma Rom with Supersu 2.61
Found the workaround in this thread.
I'm sure Google will patch it again though.
Arcaed said:
Quite so? Can you provide links to the root method and mayhaps the roms? Does this mean I could slap TWRP on here with no consequence?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=65188325
Heisenberg said:
There are quite a few errors in the information given in this thread.
1. Unlocking the bootloader does not break Android Pay.
2. Android Pay has been patched so you can't have root with Android Pay, even systemless.
3. TWRP recovery does not require a modified boot.img.
4. Flashing any recovery (Stock or TWRP) will not affect Android Pay at all.
If you need directions on unlocking or flashing check my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I've always been under the impression that the device will not boot with twrp installed unless you have DM verity checks removed. Has something changed with that.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
I've always been under the impression that the device will not boot with twrp installed unless you have DM verity checks removed. Has something changed with that.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It isn't necessary. I'm on my eighth Nexus 6P and I haven't flashed any modified boot.img prior to flashing TWRP.
83097markcynt said:
Actually AP now works with systemless root again. I have AP working (yes actually making purchases), currently running the latest Chroma Rom with Supersu 2.61
Found the workaround in this thread.
I'm sure Google will patch it again though.
Click to expand...
Click to collapse
I can second this. I have systemless root, and AP working, confirmed with purchases. Just a note, if you can successfully add a card, that means it has to contact your bank for approval, therefore it should confirm AP is working.
Is it possible? It not I will wait till I get home tonight. I'm thinking flash a stock rom zip. Then opt in. Don't loose all internal storage? Thoughts
Sent from my Nexus 6P using Tapatalk
iamdarren said:
Is it possible? It not I will wait till I get home tonight. I'm thinking flash a stock rom zip. Then opt in. Don't loose all internal storage? Thoughts
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
DJBhardwaj said:
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
Click to expand...
Click to collapse
Where can I find the modified boot image?
Edit: Found it, nevermind.
messiahfreedom said:
Where can I find the modified boot image?
Edit: Found it, nevermind.
Click to expand...
Click to collapse
Grab it from here, and make sure to download the corresponding boot.img to your build number.
Link: http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
DJBhardwaj said:
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
Click to expand...
Click to collapse
If we do it this way, will we lose data? Can we just update from 6.0.1?
jorgis1 said:
If we do it this way, will we lose data? Can we just update from 6.0.1?
Click to expand...
Click to collapse
You can if you were on a stock rom.
Sent from my Nexus 6P using Tapatalk
jorgis1 said:
If we do it this way, will we lose data? Can we just update from 6.0.1?
Click to expand...
Click to collapse
No, you won't loose any data. Your userdata/data partition will stay as is. You will just wipe the system and boot through TWRP, and then flash the listed image files.
superchilpil said:
You can if you were on a stock rom.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
But if we do it the manual way as stated before, do we lose root? What about gapps? Will those be included?
flashfire is a great app, does it all for you...
I simply downloaded OTA through the system update, then after it was downloaded instead of allowing it to "Restart and Install" which would have failed due to my custom recovery, I just opened flashfire. It found the OTA automatically and I hit Flash button. Done!
I ended up loading up from the PC. It's better this way because I only had 2gb of space on my 64gb!!! Bad thing is, I have spent about 2hrs installing!
Sent from my Nexus 6P using Tapatalk
So I can use flashfire to flash the latest N beta even though I'm currently running a custom ROM?
Sent from my Nexus 6P using XDA-Developers mobile app
GatorsUF said:
flashfire is a great app, does it all for you...
I simply downloaded OTA through the system update, then after it was downloaded instead of allowing it to "Restart and Install" which would have failed due to my custom recovery, I just opened flashfire. It found the OTA automatically and I hit Flash button. Done!
Click to expand...
Click to collapse
Foes your custom recovery still work? I tried this method and it just wouldn't boot into TWRP. Been trying all day thru different methods. Idk how to use adb fastboot on a computer so I'm a lil lost when trying any other method. I've been using Wug's toolkit but until he pushes an update for it I'm on stock MM until i can figure something out.
x.0ni.x said:
Foes your custom recovery still work? I tried this method and it just wouldn't boot into TWRP. Been trying all day thru different methods. Idk how to use adb fastboot on a computer so I'm a lil lost when trying any other method. I've been using Wug's toolkit but until he pushes an update for it I'm on stock MM until i can figure something out.
Click to expand...
Click to collapse
why does the wug toolkit not work?
I don't know a lot about Flashfire as far as it's compatibility with Custom Roms and such. I was previously on stock android Marshmellow with root and twrp. My phone downloaded the OTA for Android N when I "enrolled" in the beta program. I chose not to allow the phone to attempt to install the OTA as it would likely fail due to my custom recovery, to my surprise when I opened flashfire it offered to install the "update.zip" (AKA the OTA) and I simply hit "flash". It installed the OTA (did not use TWRP) and rooted my phone all on it's own, I did not lose anything no data was lost.
As a side not I would not recommend using Flashfire if you don't know how to use fastboot commands and the Android SDK. It is not complicated and it is a almost certain way to fix your phone when things go haywire. I strongly encourage you to learn how to use it as it is essential to owning a Nexus imo. These root kits and flashfire programs are cool, but they are always subject to failures...
Link to the developer Preview for anyone interested
https://developer.android.com/preview/download.html#top
I'm currently rooted, with TWRP. So ideally how to install and keep everything and I assume you just flash supersu.zip to root again.
TIA.
flashfire.
Thanks, just tried, but it doesn't seem to recognized this zip from the link above
angler-npf26f-factory-0cd1829d.zip
Is there a different zip to flash?
install it as firmware
Use fastboot and to save your data, don't flash userdata.img.
https://www.youtube.com/watch?v=dsKn2E68A0M
Quick q on the subject. Twrp, rooted, dp1, modded build.prop, flashed Pixel bootanimation and navbar buttons. I suppose I can't use flashfire, right?
Puck24 said:
Quick q on the subject. Twrp, rooted, dp1, modded build.prop, flashed Pixel bootanimation and navbar buttons. I suppose I can't use flashfire, right?
Click to expand...
Click to collapse
I have the same setup and also want to know how to flash without losing anything. Also would rather not adb. Will flashfire do this without losing root?
Also, I went to the OP link to get the ota, and it's just a Google page on how to test an update. Where do I get the update file?
Same here.
Sent from my Pixel XL using XDA-Developers mobile app
I actually got the OTA notification sometime in the last 8 hours while I was asleep. Saw some1 posting the link in the General section, I think
I also have (had) all the pixel goodies installed and flashed the OTA with FlashFire. Now everything is gone
I used FF. If you unchecked recovery and check modem, you'll keep recovery and root. Pixel goodies are gone, but easy to reflash
Confirm: you loose Pixel stuff but just reflash, only strange thing is that I had to flash Pixel Launcher thru twrp as with FlashFire it was not working.
Did you flashfire the OTA or the Factory Image of the DP2?
Enviado de meu Pixel XL usando Tapatalk
Factory image from here
https://developer.android.com/preview/download.html#device-preview
Carterman32 said:
I used FF. If you unchecked recovery and check modem, you'll keep recovery and root. Pixel goodies are gone, but easy to reflash
Click to expand...
Click to collapse
You did put the factory image on your nexus and then press the + button and flash firmware? Is that it? And then you can select to keep your datas and root?
And in order to keep TWRP, do I uncheck recovery or it will keep TWRP anyway?
Thanks in advance.
I unzipped and flashed just system.img in TWRP, followed by SuperSu, and then modified the vendor/build.prop to match the system/build.prop to keep from getting the "internal problem" alert. Maybe not the simplest method, but worked fine.
Sent from my Pixel XL using Tapatalk
timosuomi said:
I unzipped and flashed just system.img in TWRP, followed by SuperSu, and then modified the vendor/build.prop to match the system/build.prop to keep from getting the "internal problem" alert. Maybe not the simplest method, but worked fine.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Unless you have a specific desire not to do this, flash the matching vendor.img in TWRP. This is tied to that "internal problem" warning because of the proprietary drivers included in the file.
Also, I do not recommend flashing just the system.img for every update. You may run into a non functional camera when Google releases an OTA that requires the latest boot and vendor to be installed.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Unless you have a specific desire not to do this, flash the matching vendor.img in TWRP. This is tied to that "internal problem" warning because of the proprietary drivers included in the file.
Also, I do not recommend flashing just the system.img for every update. You may run into a non functional camera when Google releases an OTA that requires the latest boot and vendor to be installed.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Good call. I'm just coming from a Nexus 6, and I don't recall dealing with vendor.img with that or previous Nexii.
Sent from my Pixel XL using Tapatalk
timosuomi said:
Good call. I'm just coming from a Nexus 6, and I don't recall dealing with vendor.img with that or previous Nexii.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Ahh, that makes sense now. The vendor partition was originally part of the system. The Nexus 9 was the first Android device to feature a separate vendor partition and both 2015 Nexus devices launched with this separate partition.
Flash boot, system, and vendor each month OR whenever you move to a different month's OTA. With custom roms, just flash the vendor and custom rom. You can check /vendor/build.prop to see which vendor is currently installed.
Sent from my Nexus 5X using Tapatalk
I know I can go back to stock by using fastboot to reflash all the partitions, but can I use TWRP to just flash the stock rom and vendor images?
Yes. I use it every month to flash the latest security update.
Sent from my Nexus 6P using XDA Labs
lunotown said:
I know I can go back to stock by using fastboot to reflash all the partitions, but can I use TWRP to just flash the stock rom and vendor images?
Click to expand...
Click to collapse
Yes, unzip the zip inside the factory image zip, and choose install img instead of install zip. Only thing you have to flash with fastboot is the bootloader and radio. Best would be to stay at the latest ones. Before first boot flash supersu to prevent stock image to replace twrp with the stock recovery.
swallowingled said:
Yes. I use it every month to flash the latest security update.
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
Really? I thought the security patch OTAs did a check and if you don't have stock recovery it fails. Or do you flash the entire system partition
Sent from my Nexus 6P using Tapatalk
funnel71 said:
Really? I thought the security patch OTAs did a check and if you don't have stock recovery it fails. Or do you flash the entire system partition
Click to expand...
Click to collapse
Use the factory images from Google, I don't do OTA updates.
Sent from my Nexus 6P using XDA Labs