Related
Hi I just got the 5.0.1 update, I downloaded it and the phone rebooted itself, I got the installation screen and after 5 seconds I just got the word "error" and I had to restart it manually; the device is rooted, have anyone else had this problem? I would appreciate your help
saman0suke1 said:
Hi I just got the 5.0.1 update, I downloaded it and the phone rebooted itself, I got the installation screen and after 5 seconds I just got the word "error" and I had to restart it manually; the device is rooted, have anyone else had this problem? I would appreciate your help
Click to expand...
Click to collapse
With lollipop you can't take an OTA if you are rooted or running just about anything else modified (custom kernels, like ones that have force decrypt disabled also will cause it to error out).
You can still flash it manually by flashing the images. If you don't want to wipe, don't flash the userdata.img . Also, if you aren't currently encrypted, booting up with the stock kernel will force encrypt your device, so don't flash that if you want to stay that way. You can then re-root. There are more in depth instructions for doing this out there if you search around for them.
My Nexus 6 took 5.0.1 just fine, but my Nexus 7 does this same thing, running stock ROM/Bootloader/Recovery/etc. The ONLY thing done to it is the Fastboot OEM unlock, but I doubt that alone would stop it. I'm curious to know what resolves this ( other than downloading the factory image and flashing it without wiping the userdata )
Just got same error. I didnt even root phone, bought it today, it installed apps from backup of my previous Nexus 4 and OTA is failing.
cupfulloflol said:
With lollipop you can't take an OTA if you are rooted or running just about anything else modified (custom kernels, like ones that have force decrypt disabled also will cause it to error out).
You can still flash it manually by flashing the images. If you don't want to wipe, don't flash the userdata.img . Also, if you aren't currently encrypted, booting up with the stock kernel will force encrypt your device, so don't flash that if you want to stay that way. You can then re-root. There are more in depth instructions for doing this out there if you search around for them.
Click to expand...
Click to collapse
So basically the only way is to flash the image manually? If I choose not to flash userdata.img my phone data (photos, contacts, apps, etc) won't be erased right? But I will lose root correct? Thanks!
saman0suke1 said:
So basically the only way is to flash the image manually? If I choose not to flash userdata.img my phone data (photos, contacts, apps, etc) won't be erased right? But I will lose root correct? Thanks!
Click to expand...
Click to collapse
Correct, with Lollipop if you modify things you basically are then forced to manually take the updates. Not that big of a deal as you would likely be needing a PC to reinstall your custom recovery or re-root anyhow after the update.
Flashing userdata.img isn't necessary to update. Neither is recovery.img if you want to keep a custom recovery.
Also as I mentioned before, if you have disabled encryption on your device, if you flash the stock kernel (boot.img) and boot up with it you will re-enable forced encryption. You will need to flash a kernel with force encryption disabled if you want to keep running without encryption. If you haven't disabled encryption, or don't care if your device re-encrypts (this doesn't erase anything, just may take a few minutes on first boot) then this doesn't matter.
cupfulloflol said:
Correct, with Lollipop if you modify things you basically are then forced to manually take the updates. Not that big of a deal as you would likely be needing a PC to reinstall your custom recovery or re-root anyhow after the update.
Flashing userdata.img isn't necessary to update. Neither is recovery.img if you want to keep a custom recovery.
Also as I mentioned before, if you have disabled encryption on your device, if you flash the stock kernel (boot.img) and boot up with it you will re-enable forced encryption. You will need to flash a kernel with force encryption disabled if you want to keep running without encryption. If you haven't disabled encryption, or don't care if your device re-encrypts (this doesn't erase anything, just may take a few minutes on first boot) then this doesn't matter.
Click to expand...
Click to collapse
Can I manually update without removing root first? Am I going to receive an error if I don't remove it? based on what you said, I will remove userdata.img and recovery.img and that will not wipe my data right? Do I have to decompress those files or the flash-all.bat will take care of that? Thanks!
saman0suke1 said:
Can I manually update without removing root first? Am I going to receive an error if I don't remove it? based on what you said, I will remove userdata.img and recovery.img and that will not wipe my data right? Do I have to decompress those files or the flash-all.bat will take care of that? Thanks!
Click to expand...
Click to collapse
I'm interested as well. Mine is rooted and I have encryption disabled, and I have TWRP on my phone. I tried to sideload the OTA update, but I can't get my phone to start sideload. I even flashed the stock recovery to get it to go, and no dice. What do I do next?
Anyone? I would appreciate the feedback, thanks!
sideload refers to adb as I understand it. thats NOT how you flash....you use fastboot to flash so you can do it all by hand or use one of the toolkits that script it for you.
cmh714 said:
sideload refers to adb as I understand it. thats NOT how you flash....you use fastboot to flash so you can do it all by hand or use one of the toolkits that script it for you.
Click to expand...
Click to collapse
Thanks, I get that, however I wanted to know if I need to remove the root before installing the update and if I need to decompress the .zip with the .img files or the batch will do that? thanks!
saman0suke1 said:
Thanks, I get that, however I wanted to know if I need to remove the root before installing the update and if I need to decompress the .zip with the .img files or the batch will do that? thanks!
Click to expand...
Click to collapse
If your doing from the PC you need to extract the zip file from within the image and then fastboot them. As for root, when you do it from fastboot I dont believe it matters as you will lose root anyway and need to re-root via flashing SuperSU.zip
Worked great! Thanks! Android 5.0.1 and root, no data deleted
Is it normal to not have received an update beyond 5.0? I have had a Nexus 6 since day one, no rooting of any kind and I have not received 5.0.1.
I have done the sideload method, but I really don't want to bother with it. I do however want some of these terrible bugs I am experiencing squashed. This phone is giving me lots of issues lately.
Thanks!
Can you receive and install OTA updates with an unlocked bootloader? Everything else is stock, no disabled encryption or anything just unlocked bootloader.
naulsballs said:
Can you receive and install OTA updates with an unlocked bootloader? Everything else is stock, no disabled encryption or anything just unlocked bootloader.
Click to expand...
Click to collapse
Yes
Sent from my Nexus 6 using XDA Free mobile app
saman0suke1 said:
Worked great! Thanks! Android 5.0.1 and root, no data deleted
Click to expand...
Click to collapse
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks
TOCS88 said:
Is it normal to not have received an update beyond 5.0? I have had a Nexus 6 since day one, no rooting of any kind and I have not received 5.0.1.
I have done the sideload method, but I really don't want to bother with it. I do however want some of these terrible bugs I am experiencing squashed. This phone is giving me lots of issues lately.
Thanks!
Click to expand...
Click to collapse
Try pulling your Sim card out and rebooting.
scotbotmosh said:
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks
Click to expand...
Click to collapse
If you're planning to stay rooted (meaning no OTA in future) system.img, boot.img and radio.img in any order.
scotbotmosh said:
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks
Click to expand...
Click to collapse
If you use fastboot, just run these commands in terminal (I used windows, so in order to flash using fastboot, put the image that you downloaded for the update in the same folder where you have fastboot and open a terminal there) you can rename the .img files to whatever you like and replace those name in the commands below:
fastboot flash bootloader <bootloader file name here>.img
fastboot flash radio <radio file name here>.img
Then reboot it:
fastboot reboot-bootloader
Then flash these:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
And that's it. These commands are run while the phone is connected to the PC, you have to turn it on by pressing volume up + volume down + power.
Good luck.
Is there a way to sideload the 5.1 update (downloaded from the google images page) without losing the CF root AND not losing any of my system settings and configurations?
Thanks in advance.
LordGrahf said:
Is there a way to sideload the 5.1 update (downloaded from the google images page) without losing the CF root AND not losing any of my system settings and configurations?
Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
Edit after rereading this http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 I would prob also do the reboot step after radio flash.
Maybe what your lookin for. If rooting is lost simply redo the cf root process and flash your custom recovery via fastboot. Most importantly this route will prevent data loss. I am going this route but will still backup because its safer and more responsible.
Without a modified img, and using the google provided stuff, you can't keep root. Just re-root, it's not hard.
Thanks guys. Few questions:
1. Do I need to unroot before sideloading the update?
2. Would I loose my currently installed and configured apps?
3. If I'm not losing my installed apps, what would happen to my root-required apps? For example I HAVE LMT pie control installed and configured. Would reinstalling root make it work as before without the need to reinstall and reconfigure LMT?
4. I'm still using stock recovery, would that affect what I'm trying to do in any way?
5. What is the minimal set of the update's images can I use to get this update? Like I think I should probably skip the user.img if I don't want my user settings to be wiped out, correct? What other images should I skip in order to not wipe out apps, apps settings, and system settings.
Thank you very much
LordGrahf said:
Thanks guys. Few questions:
1. Do I need to unroot before sideloading the update?
2. Would I loose my currently installed and configured apps?
3. If I'm not losing my installed apps, what would happen to my root-required apps? For example I HAVE LMT pie control installed and configured. Would reinstalling root make it work as before without the need to reinstall and reconfigure LMT?
4. I'm still using stock recovery, would that affect what I'm trying to do in any way?
5. What is the minimal set of the update's images can I use to get this update? Like I think I should probably skip the user.img if I don't want my user settings to be wiped out, correct? What other images should I skip in order to not wipe out apps, apps settings, and system settings.
Thank you very much
Click to expand...
Click to collapse
If doing the fastboot way like I linked (I have not read through the procedure for sideload, so I don't know)
1) no
2) no if you only flash some of the IMG files. For your purpose it seems (I'm also assuming you don't have custom kernel) these are the ones to not lose data. Make sure you follow the links in how to flash this correctly with the appropriate order and spots where to fastboot reboot.
Bootloader image
Radio image
Boot image (kernel)
Cache image
System image
Recovery image
Then reroot with the cf zip like before then reinstall the su app.
4) no we flash the new stock recovery too
5) minimal, to not overwrite the user data, above. Yup we skip the user data image
LordGrahf said:
Thanks guys. Few questions:
1. Do I need to unroot before sideloading the update?
2. Would I loose my currently installed and configured apps?
Click to expand...
Click to collapse
No.
LordGrahf said:
3. If I'm not losing my installed apps, what would happen to my root-required apps?
Click to expand...
Click to collapse
You'll have to install su since it was deleted by system.img but that's all. Note that last time I looked CF-Auto still said it was 5.0.1 but ...
LordGrahf said:
4. I'm still using stock recovery, would that affect what I'm trying to do in any way?
Click to expand...
Click to collapse
If you install a current TWRP it will install super-su for you when you request a reboot.
LordGrahf said:
5. What is the minimal set of the update's images can I use to get this update?
Click to expand...
Click to collapse
Everything except user.img. You can read or run flash-base to get the Google suggested initial ordering.
MunkinDrunky said:
http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
Edit after rereading this http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 I would prob also do the reboot step after radio flash.
Maybe what your lookin for. If rooting is lost simply redo the cf root process and flash your custom recovery via fastboot. Most importantly this route will prevent data loss. I am going this route but will still backup because its safer and more responsible.
Click to expand...
Click to collapse
I flashed the bootloader, but the command to flash the radio (fastboot flash radio radio-shamu-d4.0-9625-02.95.img) failed
Any idea?
Nikos2k said:
I flashed the bootloader, but the command to flash the radio (fastboot flash radio radio-shamu-d4.0-9625-02.95.img) failed
Any idea?
Click to expand...
Click to collapse
I don't really know. I usually just follow instructions. Did you fastboot reboot after flashing bootloader?
MunkinDrunky said:
I don't really know. I usually just follow instructions. Did you fastboot reboot after flashing bootloader?
Click to expand...
Click to collapse
Yes, I rebooted the boot loader (and it indeed showed the new boot loader version after the reboot)
After the fail message of the radio flash command, I rebooted to the system, it works, and from the baseband number in settings/about, it seems that the new radio has been flashed (besides the fail message)
Nikos2k said:
Yes, I rebooted the boot loader (and it indeed showed the new boot loader version after the reboot)
After the fail message of the radio flash command, I rebooted to the system, it works, and from the baseband number in settings/about, it seems that the new radio has been flashed (besides the fail message)
Click to expand...
Click to collapse
hmm yeah i really dont know why that happend. I guess as long as the new radio shows up as you say then it worked. I will actually be doing this shortly, since i am now at a computer
Just updated to 5.1
for those who will read later and more importantly in my same position.
I was on 5.0.1 BL unlocked, custom recovery+root, custom kernel- -wanting to go to->>5.1, root+custom recovery (cause flashing kernels is trivial) without any data loss (basically don't flash the userdata image) (also you could have left out the radio, I guess if you don't want newest radio, and the boot if you want to just keep your kernel--**not 100% about these two though)
I flashed via fastboot the: bootloader (then fastboot reboot-bootloader), the radio (then fastboot reboot-bootloader), then the boot (updated stock kernel), cache, system. Done, exit command prompt, then while in fastboot menu go into TWRP, whereby I choose system reboot and TWRP RE-ROOTS for me! Now I just kernel shop again
Thanks a lot gents. I followed the directions and upgraded/rerouted and none of my apps/settings got wiped. Yay!!
Can someone verify I'm on the latest versions for all components from my screenshot?
Thanks!
I also updated my Nexus 6 with 5.0.1, unlock and root, to 5.1 without losing data. I just had to re-root it afterwards.
I used Wugfresh Nexus root toolkit.
In short I used "Flash stock + unroot", in which I selected "Enable no-wipe" and "force-flash".
After this I rerooted the device from within NRT.
Worked like a charm!
---------- Post added at 03:23 PM ---------- Previous post was at 03:13 PM ----------
LordGrahf said:
Thanks a lot gents. I followed the directions and upgraded/rerouted and none of my apps/settings got wiped. Yay!!
Can someone verify I'm on the latest versions for all components from my screenshot?
Thanks!
Click to expand...
Click to collapse
That's all the latest versions yes...
I've been receiving the prompt to update my N6 to 5.1.1 for the past few days, but whenever I attempt to install it, it says it's rebooting and does nothing. Is this because I'm rooted? Besides being rooted, there's no modifications to the system (well, except for Franco Kernel and MCR I suppose...). Is it even possible to update this way? Any help would be much appreciated. Thanks!
greycobalt said:
I've been receiving the prompt to update my N6 to 5.1.1 for the past few days, but whenever I attempt to install it, it says it's rebooting and does nothing. Is this because I'm rooted? Besides being rooted, there's no modifications to the system (well, except for Franco Kernel and MCR I suppose...). Is it even possible to update this way? Any help would be much appreciated. Thanks!
Click to expand...
Click to collapse
Hi, no modifications to system (including recovery) or boot can be present for OTA to flash. Look here:
http://forum.xda-developers.com/showthread.php?t=2992919
Evolution_Tech said:
Hi, no modifications to system (including recovery) or boot can be present for OTA to flash. Look here:
http://forum.xda-developers.com/showthread.php?t=2992919
Click to expand...
Click to collapse
Well that's a bummer! Thanks for the link. It looks like sideloading will still work, is that correct? If so, is it possible to sideload an update without wiping my data or factory resetting?
greycobalt said:
Well that's a bummer! Thanks for the link. It looks like sideloading will still work, is that correct? If so, is it possible to sideload an update without wiping my data or factory resetting?
Click to expand...
Click to collapse
If your bootloader is unlocked, just do this:
Download the factory image for the new build you want.
Extract twice to end up with the bootloader, radio, boot, system, recovery, userdata, and cache images.
Flash each image individually with fastboot except for userdata.
You will be updated and won't lose data. Then, just flash TWRP again and then from TWRP, flash the superSU zip. You will be stock rooted, with TWRP recovery. All your data will remain.
If you try to flash official OTA via sideload, it will still fail because of root and custom recovery.
greycobalt said:
I've been receiving the prompt to update my N6 to 5.1.1 for the past few days, but whenever I attempt to install it, it says it's rebooting and does nothing. Is this because I'm rooted? Besides being rooted, there's no modifications to the system (well, except for Franco Kernel and MCR I suppose...). Is it even possible to update this way? Any help would be much appreciated. Thanks!
Click to expand...
Click to collapse
Hi hi. Made me smile. Thanks for that.
Evolution_Tech said:
If your bootloader is unlocked, just do this:
Download the factory image for the new build you want.
Extract twice to end up with the bootloader, radio, boot, system, recovery, userdata, and cache images.
Flash each image individually with fastboot except for userdata.
You will be updated and won't lose data. Then, just flash TWRP again and then from TWRP, flash the superSU zip. You will be stock rooted, with TWRP recovery. All your data will remain.
If you try to flash official OTA via sideload, it will still fail because of root and custom recovery.
Click to expand...
Click to collapse
I will definitely do this! Thanks. They haven't posted the Verizon 5.1.1 to the image site yet, so I'll have to wait a bit I guess. :-/ Thanks!
Didgeridoohan said:
Hi hi. Made me smile. Thanks for that.
Click to expand...
Click to collapse
Phone happily running 7.0.0 (NBD90Z, Oct 2016)
Running system less super su SR3 and Franco #57
Downloaded and fast boot flashed the latest November update from PC.
Only flashed updated bootloader and system image from 7.0.0 (NBD91P, Nov 2016)
Restarted Phone and it loops at boot animation, left for twenty minutes, no progress, so rebooted back to recovery and tried wiping, cache, dalvik and art cache, and restarted again still no difference, looped at boot animation again for twenty minutes.
So rebooted to recovery and restored October backup.
Was anyone else and to fast boot flash latest factory system image and boot their phone without any issues?
Is a full wipe really necessary?
Any one?
Sent from my Shamu using Tapatalk
ben_pyett said:
Phone happily running 7.0.0 (NBD90Z, Oct 2016)
Running system less super su SR3 and Franco #57
Downloaded and fast boot flashed the latest November update from PC.
Only flashed updated bootloader and system image from 7.0.0 (NBD91P, Nov 2016)
Restarted Phone and it loops at boot animation, left for twenty minutes, no progress, so rebooted back to recovery and tried wiping, cache, dalvik and art cache, and restarted again still no difference, looped at boot animation again for twenty minutes.
So rebooted to recovery and restored October backup.
Was anyone else and to fast boot flash latest factory system image and boot their phone without any issues?
Is a full wipe really necessary?
Any one?
Sent from my Shamu using Tapatalk
Click to expand...
Click to collapse
I flashed NBD91P without a full wipe and my phone booted without any issues. However I have not been able to get su SR2 or su SR3 to work with either NBD90Z or NBD91P. SR1 works without any issues.
I flashed bootloader, boot and system without a problem. Also using FK, but have magisk+phh root.
I've seen a few people mentioning having problems with SuperSU 2.78 SR2 and SR3 and the latest update (NBD91P)
"Only flashed updated bootloader and system image"
I'm genuinely puzzled as to why people aren't using the OTA sideload method, which is incredibly simple and leaves your data and settings totally intact.
The quote above makes me think "You did half a job and now wonder why your phone won't work...?"
dahawthorne said:
I'm genuinely puzzled as to why people aren't using the OTA sideload method, which is incredibly simple and leaves your data and settings totally intact.
The quote above makes me think "You did half a job and now wonder why your phone won't work...?"
Click to expand...
Click to collapse
You didn't read the post completely, as my phone is working as I always make the precaution of taking a backup and simply restored to it.
I didn't think ota method was possible if you had custom recovery?
Using the method I've described also leaves data and settings in tact.
I didn't run the flash all scripts.
Thanks
Sent from my Shamu using Tapatalk
No offence intended. I have never (touch wood) had any serious problems with my many upgrades on many devices. As you did, I always have a backup in case it goes wrong. In fact I even have multiple backups on my laptop in case the latest one doesn't work.
I've use the OTA sideload method a dozen times now on all my rooted Nexus devices. All of them as standard have TWRP & root (either doitright's or Chainfire's), and the OTA just slides right in there regardless. No problems at all. When it's installed (which takes about five minutes) I have to reroot - I can't remember if I've had to reinstall TWRP, though on a number of occasions I've just reinstalled it anyway without bothering to check if it was already still there.
So in summary the OTA sideload works for rooted/TWRPed devices, doesn't lose anything, and is far simpler and safer than running separate partition flashes. Give it a go and I guarantee you'll never do it the old way again.
dahawthorne said:
No offence intended. I have never (touch wood) had any serious problems with my many upgrades on many devices. As you did, I always have a backup in case it goes wrong. In fact I even have multiple backups on my laptop in case the latest one doesn't work.
I've use the OTA sideload method a dozen times now on all my rooted Nexus devices. All of them as standard have TWRP & root (either doitright's or Chainfire's), and the OTA just slides right in there regardless. No problems at all. When it's installed (which takes about five minutes) I have to reroot - I can't remember if I've had to reinstall TWRP, though on a number of occasions I've just reinstalled it anyway without bothering to check if it was already still there.
So in summary the OTA sideload works for rooted/TWRPed devices, doesn't lose anything, and is far simpler and safer than running separate partition flashes. Give it a go and I guarantee you'll never do it the old way again.
Click to expand...
Click to collapse
Do you change, or alter you system partition, ie remove application or add some.
I'm asking if an ota will apply over the top of an altered system?
If so I'll try it once I've finished work.
Although will also rule out the version of super su first.
Sent from my Shamu using Tapatalk
I change nothing. My N6 is rooted and TWRPed and I just connect to the computer and use ADB to sideload the OTA. It says "flashing unconditionally" so I'm guessing (I'm just an end-user, not a dev) that the OTA just wipes the old ROM and overwrites it, but doesn't touch the data partition. Since the system partition is replaced, root disappears with it, but I'm not sure if it touches TWRP - as I said, I just reinstall it anyway each time and then use it to flash SuperSU.
Give it a go - you'll like it...
P.S. I understand that the OTA has some sort of internal checksum to verify the package integrity, but I always double-check my download with Checksum Utility:
https://raylin.wordpress.com/downloads/md5-sha-1-checksum-utility/
dahawthorne said:
I change nothing. My N6 is rooted and TWRPed and I just connect to the computer and use ADB to sideload the OTA. It says "flashing unconditionally" so I'm guessing (I'm just an end-user, not a dev) that the OTA just wipes the old ROM and overwrites it, but doesn't touch the data partition. Since the system partition is replaced, root disappears with it, but I'm not sure if it touches TWRP - as I said, I just reinstall it anyway each time and then use it to flash SuperSU.
Give it a go - you'll like it...
P.S. I understand that the OTA has some sort of internal checksum to verify the package integrity, but I always double-check my download with Checksum Utility:
https://raylin.wordpress.com/downloads/md5-sha-1-checksum-utility/
Click to expand...
Click to collapse
So flashed, ota through flash fire, worked as described.
As expected phone booted, with stock kernel, recovery and no root.
So rebooted to bootloader and had to re fast boot flash twrp recovery.
But then flashed systemless super su and Franco kernel, phone no longer boots.
Restored backup as ran out of time.
Will try again tonight with our systemless, which root version and methods are you using?
I'll try just kernel and then just root to see which it is that's causing the problem
Progress.
Although to be honest, I'm still of the opinion that flashing just system partition is a far simpler, process then ota.
This is the first time in a a good few years and multiple nexus/android versions, where I've ever had an issue with this process. (And I've had N4, N5 and N6)
Anyone?
Thanks
Sent from my Shamu using Tapatalk
Maybe you're trying too much all at once? I installed the OTA, TWRP and SuperSU 2.78 R3 with no problems - I have tried a couple of custom kernels but saw no appreciable difference, so decided that I'd avoid the risk of tinkering with stuff I don't understand.
Maybe there's some incompatibility with the Franco kernel? I know that SuperSU performs some processing on the kernel - it shows in the installation dialogue.
The more Google locks down android the harder it will be so people need to make a choice and live with it. Either you want the pointless OTA or you are gonna use a custom set up. Not flashing an update properly and then posting a thread about it only makes developers laugh.
zelendel said:
The more Google locks down android the harder it will be so people need to make a choice and live with it. Either you want the pointless OTA or you are gonna use a custom set up. Not flashing an update properly and then posting a thread about it only makes developers laugh.
Click to expand...
Click to collapse
Why do you say he didn't flash the update properly? I thought the only difference between NBD90Z and NBD91P was the bootloader and system images. There was no new recovery, radio, etc... included in that release. So what's the harm in only updating the bootloader/system partitions?
If you did it the "right way" I guess that would be running the flash-all.bat file in the folder. All that does is flash all the partitions (which is dumb because you're overwriting the same partitions which is completely unnecessary if you already have them) and wipe userdata. With his method userdata would've stayed intact.
Please note I never do this method, I'm a custom ROM man thru and thru. Whether it's Dirty Unicorns, AOSiP, OctOS, etc... I never run factory system images because even though with GravityBox you can get a lot of customization, I still prefer CMTE over Substratum/OMS. No way to get CMTE in stock firmware.
dahawthorne said:
Maybe you're trying too much all at once? I installed the OTA, TWRP and SuperSU 2.78 R3 with no problems - I have tried a couple of custom kernels but saw no appreciable difference, so decided that I'd avoid the risk of tinkering with stuff I don't understand.
Maybe there's some incompatibility with the Franco kernel? I know that SuperSU performs some processing on the kernel - it shows in the installation dialogue.
Click to expand...
Click to collapse
Finally managed it.
Fastboot Flashed system
Fastboot Flashed stock boot
Went in to recovery
Flashed Franco
Booted rom
Went back to recovery
Flashed update-unSU (unsure is this stage is needed, but was taking no chances)
Flashed super su
Was finally able to boot rom
Seems combination of super su and Franco wouldn't work in single flash for me. Needed clean reboot between each.
Although I still believe that fast boot flash system is easiest method rather than ota, as doesn't affect recovery or boot partitions and you stay in control, each to their own.
This is the first time I've encountered any issues with this method.
Comments suggesting I didn't do it properly without highlighting what, if anything I did wrong or without adding any positive feedback are worthless.
Thanks for input and suggestions.
Sent from my Nexus 6 using Tapatalk
I had very similar issues. I've been updating this phone monthly since day 1 without issue but with the NBD91P update, I got the same boot loop even with the stock kernel. My device is also encrypted.
After I booted back to the bootloader I noticed that TWRP was gone. I found that very odd. It was like the system image was trying to write over it. Not sure though, but I do know that I had to re-flash TWRP (I've had the same version, which is also the latest one, for months) after every boot loop.
I kept re-flashing and trying different versions of the systemless versions of SuperSU but none of them worked. Got stuck in the same boot loop everytime.
I finally re-flashed everything except for SuperSU and stock NBD91P booted up fine without root.
I'm also having the same issue. I can't even flash SR1. Any update on this?
I can't not boot the NBD91P factory image if I have any layers installed. Removing that overlay folder via TWRP is the only way to make it boot again.
LordDeath said:
I can't not boot the NBD91P factory image if I have any layers installed. Removing that overlay folder via TWRP is the only way to make it boot again.
Click to expand...
Click to collapse
There is a bug in this update which causes a bootloop if the system is themed. Restore to NBD90Z.
msaitta said:
I had very similar issues. I've been updating this phone monthly since day 1 without issue but with the NBD91P update, I got the same boot loop even with the stock kernel. My device is also encrypted.
After I booted back to the bootloader I noticed that TWRP was gone. I found that very odd. It was like the system image was trying to write over it. Not sure though, but I do know that I had to re-flash TWRP (I've had the same version, which is also the latest one, for months) after every boot loop.
I kept re-flashing and trying different versions of the systemless versions of SuperSU but none of them worked. Got stuck in the same boot loop everytime.
I finally re-flashed everything except for SuperSU and stock NBD91P booted up fine without root.
Click to expand...
Click to collapse
collinjames said:
I'm also having the same issue. I can't even flash SR1. Any update on this?
Click to expand...
Click to collapse
LordDeath said:
I can't not boot the NBD91P factory image if I have any layers installed. Removing that overlay folder via TWRP is the only way to make it boot again.
Click to expand...
Click to collapse
I was able to get over my own original problem using the process listed a few posts above, in my previous comment.
Even though it took several attempts to determine a working sequence. Did you try the process which worked for me on your devices?
Strephon Alkhalikoi said:
There is a bug in this update which causes a bootloop if the system is themed. Restore to NBD90Z.
Click to expand...
Click to collapse
Can't comment as my system wasn't themed.
Does the boot loop occur, if you, remove your themes then upgrade to latest image, reboot it and finally reapply your layers?
Sent from my Nexus 6 using Tapatalk
Dopamin3 said:
Why do you say he didn't flash the update properly? I thought the only difference between NBD90Z and NBD91P was the bootloader and system images. There was no new recovery, radio, etc... included in that release. So what's the harm in only updating the bootloader/system partitions?
Click to expand...
Click to collapse
He said, quote:
Only flashed updated bootloader and system image from 7.0.0 (NBD91P, Nov 2016)
Click to expand...
Click to collapse
Unless you have the diffs from the Android git, you can't decide if flashing boot necessary or not. And even then you can decide wrong.
The whole package is: bootloader, radio, boot, system, (vendor in case of the 6P), recovery, and the clutter.
You should skip data, and shouldn't bother with the cache partition, but it's a good idea clearing it after flashing a new system. You can always check if the bootloader and radio have changed, you can diff them if you don't believe the version numbers.
That leaves boot and system, you should always flash both, even if it goes by the nuisance of re-rooting.
Also if you're unencypted, as I am, then after flashing boot, you should not reboot without flashing a root that deals with it.
(But making an unencrypted and verity-less boot is five minutes tops, by the way)
Strephon Alkhalikoi said:
There is a bug in this update which causes a bootloop if the system is themed. Restore to NBD90Z.
Click to expand...
Click to collapse
Having the lastest security fixes is more important than themes.
TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
Amazing work sir! I think this is what we've all been waiting for! I mean I know I've been checking here frequently, hoping for this
Wow and so it begins, great work thanks!
Thanks
Sent from my Pixel using XDA-Developers mobile app
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Dees_Troy said:
Note: I am going to be very busy the next couple of weeks. I probably won't be able to answer your questions or fix things immediately.
Click to expand...
Click to collapse
the pixel installer.zip is corrupt. :crying:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
GeekMcLeod said:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
Click to expand...
Click to collapse
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
zaksimmermon said:
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
Click to expand...
Click to collapse
No I haven't downloaded anything yet. Not going to until I can have supersu alongside twrp.
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Snowby123 said:
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Click to expand...
Click to collapse
"In other words, Chainfire's systemless root method modifies the same binary that TWRP needs to modify in order to get data decryption working. Therefore, when you flash TWRP you are overwriting the changes made to the init binary by Chainfire's systemless root method. While this is a minor setback, thanks to the dual partition nature of the Pixel (and future devices shipping with Nougat), TWRP has some nifty new capabilities."
I'm pretty sure he's just saying dont chance something going wrong like it bootlooping or wiping data if you need your phone for something important like a phone call. Tough to answer said phonecall in a boot loop.
zaksimmermon said:
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Click to expand...
Click to collapse
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
rtthane said:
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
Click to expand...
Click to collapse
I finally got passed that issue. I had to flash factory images and erase everything to the point of being at setup screen. I didn't set anything up, no network or wifi, skipped Google sign in, no password and also no Google functions activated. This led to an unencrypted setup, so after turning on dev settings and Android debugging I booted up the image. Now my issue is the zip to install twrp for sailfish is corrupt and if you try to unzip it there are no files in it....I downloaded the marline zip and there are files when unzipped....
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
ne0ns4l4m4nder said:
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
Click to expand...
Click to collapse
Are you trying to fastboot flash or fastboot boot?
Sent from my Pixel using Tapatalk
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
fracman said:
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
Click to expand...
Click to collapse
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
ej_424 said:
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
Click to expand...
Click to collapse
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
BakedTator said:
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
Click to expand...
Click to collapse
OK thanks, wondering if root will work with November update or of I need to roll back first. Prior to SU update today Nov update didn't work with the auto cf root