Related
Hi this is my first post and i hope its in the correct place and all
My nexus 7 (2013) is stuck in an android update circle where it constantly fails.
I tried to so the update to jss15q 4.3 using sideload where got so close but it said "signature verification failed" why could that be and can i stop it needing a verification?
I then tried to do it using fastboot and got so close again but got
:checking version-bootloader failed"
:device version-bootloader is "flo-03.05"
:Update requires "flo-03.14"
is there a way to correct either of them?
I am not rooted and i have downloaded the jss15q from developers google themselves (and i have debugging enabled)
Thanks for any help
Joe
Do you have the LTE version of the nexus or the WiFi version?
Guhrasoh said:
Do you have the LTE version of the nexus or the WiFi version?
Click to expand...
Click to collapse
I have the wifi only version.
joeyt90 said:
I have the wifi only version.
Click to expand...
Click to collapse
Follow this thread: http://forum.xda-developers.com/showthread.php?t=2382051 to unlock the bootloader (your data on the device will be lost). Make sure you reboot the device at least once after unlocking and before you do anything else with it!
After that you can flash or boot TWRP and try to install the update with TWRP, if that fails you can flash a full factory image (the above thread contains all the information needed).
Guhrasoh said:
Follow this thread: http://forum.xda-developers.com/showthread.php?t=2382051 to unlock the bootloader (your data on the device will be lost). Make sure you reboot the device at least once after unlocking and before you do anything else with it!
After that you can flash or boot TWRP and try to install the update with TWRP, if that fails you can flash a full factory image (the above thread contains all the information needed).
Click to expand...
Click to collapse
What exactaly do i have to do on that page to be able to continue the methods i am trying to use? If i just unlock the bootloader willi be able to update the boot loader from version-bootloader "flo-03.05" to "flo-03.14" then download jss14q using fast boot or is it not that easy?
Thanks again
P.S I dont want to root yet and Is it possible to just update the bootloader without unlock bootloader or do you have to unlock before you can update?
Thanks
If you want to use fastboot and the factory images you need to be unlocked.
Which file did you feed it when you "sideloaded" it? It needs to be the OTA file.
sfhub said:
If you want to use fastboot and the factory images you need to be unlocked.
Which file did you feed it when you "sideloaded" it? It needs to be the OTA file.
Click to expand...
Click to collapse
Hi I used the image from Google developers for nexus which was a zip file. Where could get the ota file from.
By unlocking do you mean just unlocking boot loader?
Thanks Joe
joeyt90 said:
Hi I used the image from Google developers for nexus which was a zip file. Where could get the ota file from.
By unlocking do you mean just unlocking boot loader?
Click to expand...
Click to collapse
Yes, bootloader must be unlocked to use the factory image restore.
As to the zip file, the zip file from the google developer site is a factory image. It is not meant to be sideloaded, only used in fastboot-style restores.
If you want to go the sideload route, what you want is the appropriate OTA zip (JWR66N->JSS15Q, JSS15J->JSS15Q), which you can get in the download section of this thread:
http://forum.xda-developers.com/showthread.php?t=2415497
If you'd rather do the factory image to JSS15Q, then I suggest you unlock the bootloader and use this post:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
Personally, I'd go the factory image restore route, it is less hassle.
sfhub said:
Yes, bootloader must be unlocked to use the factory image restore.
As to the zip file, the zip file from the google developer site is a factory image. It is not meant to be sideloaded, only used in fastboot-style restores.
If you want to go the sideload route, what you want is the appropriate OTA zip (JWR66N->JSS15Q, JSS15J->JSS15Q), which you can get in the download section of this thread:
http://forum.xda-developers.com/showthread.php?t=2415497
If you'd rather do the factory image to JSS15Q, then I suggest you unlock the bootloader and use this post:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
Personally, I'd go the factory image restore route, it is less hassle.
Click to expand...
Click to collapse
PERFECT!!!
Thank you so much to everyone who helped me on here my device is now running 4.3 version jss15q and what a difference from jwr66n.
I used the Unlock bootloader and then use factory images and it worked a treat!!
Again i cannot thank you enough i called google and the people who suplied my nexus and they both said they didnt know!!
WAHOO!!!:good::good::good::laugh::laugh:
The hot new security update is live, and you maybe want some root love without flashing custom kernel.
(Stock Image here : https://developers.google.com/android/nexus/images#volantis)
Handy modified root compatible boot image for the latest stock image MRA58N. Pure stock kernel modified from the stock images.
You have two choices:
The traditional root in system, which breaks OTA functionality.
(It's more stable now)
New "systemless" approach, which means the root stuffs are only in DATA and BOOT, the system will stay intact and it will accept OTAs.
(Note that this method is still in beta stage according to CF)
Instructions:
System:
Unzip system-root.zip, flash the boot.img through fastboot
Flash SuperSU 2.52
Systemless:
Be sure you haven't used any other root method(like the one above), if you've rooted with other methods, please re-flash your system back to pure stock
Unzip systemless-root.zip, flash the boot.img through fastboot
Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.
When a new OTA appears I can just apply it and it will work? Do I keep root or do I have to reroot it again?
Are the attached zip files for the wifi model only?
I have this Kernel:
3.10.40-g909db78
[email protected] #1
Fri Aug 28 21:16:30 UTC 2015
Is this a stock one?
And with method shall I use to get rooted MRA58N?
Jeltel said:
When a new OTA appears I can just apply it and it will work? Do I keep root or do I have to reroot it again?
Click to expand...
Click to collapse
You can revert to stock boot and stock recovery to apply OTA
corkiejp said:
Are the attached zip files for the wifi model only?
Click to expand...
Click to collapse
Yes, I can make a LTE compatible version though.
sejmand said:
I have this Kernel:
3.10.40-g909db78
[email protected] #1
Fri Aug 28 21:16:30 UTC 2015
Is this a stock one?
And with method shall I use to get rooted MRA58N?
Click to expand...
Click to collapse
Yes, and yes
topjohnwu said:
You can revert to stock boot and stock recovery to apply OTA
Yes, I can make a LTE compatible version though.
Yes, and yes
Click to expand...
Click to collapse
A LTE compatible version would be great!!!
topjohnwu said:
You can revert to stock boot and stock recovery to apply OTA
Click to expand...
Click to collapse
So that's a no
I flashed factory image MRA58N (system gets encrypted, because it wasn't under MRA58K)
then twrp
then systemless-root (boot.img)
then superuser 2.56.....
EVERYTHING WORKS FINE:
encrypted with root!
how to flash boot.img (command for flashing)
topjohnwu said:
The hot new security update is live, and you maybe want some root love without flashing custom kernel.
(Stock Image here : https://developers.google.com/android/nexus/images#volantis)
Handy modified root compatible boot image for the latest stock image MRA58N. Pure stock kernel modified from the stock images.
You have two choices:
The traditional root in system, which breaks OTA functionality.
(It's more stable now)
New "systemless" approach, which means the root stuffs are only in DATA and BOOT, the system will stay intact and it will accept OTAs.
(Note that this method is still in beta stage according to CF)
Instructions:
System:
Unzip system-root.zip, flash the boot.img through fastboot
Flash SuperSU 2.52
Systemless:
Be sure you haven't used any other root method(like the one above), if you've rooted with other methods, please re-flash your system back to pure stock
Unzip systemless-root.zip, flash the boot.img through fastboot
Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.
Click to expand...
Click to collapse
how to flash boot.img for system less (partition ?)
Lightnyboy said:
how to flash boot.img for system less (partition ?)
Click to expand...
Click to collapse
Unzip systemless-root.zip which will give you a "boot.img" file.
Then while in fastboot
"fastboot flash boot boot.img"
Anyone have the boot files for LTE yet?
Nice. Could you add the link to CF original post in systemless root.
thebrainkafka said:
Nice. Could you add the link to CF original post in systemless root.
Click to expand...
Click to collapse
topjohnwu said:
[*]Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
[*]Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.
Click to expand...
Click to collapse
Already linked? Click on "this thread" above!
Updated for LTE... Sorry for the late update.
Also looks like rovo89 just put up xposed for marshmallow in his xposed for lollipop thread. Yes!
xposed marshmallow
topjohnwu said:
Updated for LTE... Sorry for the late update.
Click to expand...
Click to collapse
Thanks for the modified boot images for LTE, I linked back here from my thread in Q&A forum.
have problems getting it to work...
am on MRA58N stock.
My exact steps.
adb reboot bootloader
Device reboots to bootloader.
fastboot flash boot boot.img (extracted from volantisg-mra58n-boot-systemless.zip)
fastboot boot twrp.img (extracted from https://dl.twrp.me/flounder/twrp-2.8.7.1-flounder.img)
From here, I manage to get into TWRP but they are asking for a PIN. I had to cancel and mounted an external USB storage and manage to flash SuperSU-v2.56-20151030013730.zip successfully. Rebooting after and not installing the the SuperSU that TWRP prompts.
After rebooting, I still don't have root. What did I do wrong?
madbat99 said:
Also looks like rovo89 just put up xposed for marshmallow in his xposed for lollipop thread. Yes!
xposed marshmallow
Click to expand...
Click to collapse
I haven't run N version yet as my N9 is finally working without lags/reboots. But, the lure of the close all recent apps button (and very successful experience with xposed/gravity box on N5 after a year) in GB was too great. It works beautifully!
This may seem off-topic, but since root is required, maybe readers can allow exception.
Sent from my Nexus 9 using Tapatalk
chesterchen said:
have problems getting it to work...
am on MRA58N stock.
My exact steps.
adb reboot bootloader
Device reboots to bootloader.
fastboot flash boot boot.img (extracted from volantisg-mra58n-boot-systemless.zip)
fastboot boot twrp.img (extracted from https://dl.twrp.me/flounder/twrp-2.8.7.1-flounder.img)
From here, I manage to get into TWRP but they are asking for a PIN. I had to cancel and mounted an external USB storage and manage to flash SuperSU-v2.56-20151030013730.zip successfully. Rebooting after and not installing the the SuperSU that TWRP prompts.
After rebooting, I still don't have root. What did I do wrong?
Click to expand...
Click to collapse
You don't need to extract twrp.img, you should flash the full image "twrp-2.8.7.1-flounder.img".
That version should not ask for PIN anymore.
Note: system-less is still experimental
If I want to switch from the systemless root to regular system modified root, are there specific cleanup actions to take?
Thanks!
maximumentropy said:
If I want to switch from the systemless root to regular system modified root, are there specific cleanup actions to take?
Thanks!
Click to expand...
Click to collapse
Reflash the stock image then you're good
Hi, can some one give me a guide on the nexus 6 p running mhc19i for no force encrypt, with either a system root that will allow me to remove apps, or a systemless root that I have to go through recovery, and is there a recovery for this version at this time other then the stock one
gigawatt said:
Hi, can some one give me a guide on the nexus 6 p running mhc19i for no force encrypt, with either a system root that will allow me to remove apps, or a systemless root that I have to go through recovery, and is there a recovery for this version at this time other then the stock one
Click to expand...
Click to collapse
To decrypt you need to format the userdata partition:
Code:
fastboot format userdata
This will obviously wipe your storage so back it up to your PC first. You will also need to flash a custom kernel that doesn't force encryption first otherwise the stock kernel will just encrypt again when you boot after formatting. You need to use TWRP recovery to flash SuperSU to get root. I have detailed instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
yeh, is there a custom kernel for mhc19i
gigawatt said:
yeh, is there a custom kernel for mhc19i
Click to expand...
Click to collapse
Of course, there are many. Have you actually looked?
yes, I have looked, but most of them have an aroma installer, I am totally blind so I need one I can flash through fastboot as there is no talkback in aroma or recovery mode. Even the stock no force encrypt would be helpful thanks.
gigawatt said:
yes, I have looked, but most of them have an aroma installer, I am totally blind so I need one I can flash through fastboot as there is no talkback in aroma or recovery mode. Even the stock no force encrypt would be helpful thanks.
Click to expand...
Click to collapse
You can flash any of them via fastboot. Extract the boot.img from the zip and flash it:
Code:
fastboot flash boot boot.img
You'll just end up with the default settings. Why don't you just flash TWRP? Then you can install it the intended way.
I can flash twrp through fastboot, but I am totally blind and use a screen reader, so I would have to have some one around to use the twrp interface, since there is no speech there, so I need a kernel or modified no force encrypt boot.img I can flash through fastboot
gigawatt said:
I can flash twrp through fastboot, but I am totally blind and use a screen reader, so I would have to have some one around to use the twrp interface, since there is no speech there, so I need a kernel or modified no force encrypt boot.img I can flash through fastboot
Click to expand...
Click to collapse
Ahh, I see, that is definitely a difficult situation. So basically as I said, I believe any of them can be flashed via fastboot, but it isn't without its own work. You'd need to download the kernel zip, extract it, place the boot.img into your working directory (your fastboot folder), and use the "fastboot flash boot boot.img" command to flash it to the device. This will give you a kernel that doesn't force encryption, and you could then go on to use an app like Kernel Auditor to tweak the settings once you've booted into Android. How possible is this for you?
well I downloaded fk-r12-anykernel2.zip and unzipped it and there was no boot.img inside, so, can you send me a link to a boot.img for his kernel or the stock with no force encrypt, and am I missing any features by not flashing it through recovery, don't really care, just asking, but if you can please send me a boot.img for the verison I posted earlier in the thread.
Thanks so much for your help
gigawatt said:
well I downloaded fk-r12-anykernel2.zip and unzipped it and there was no boot.img inside, so, can you send me a link to a boot.img for his kernel or the stock with no force encrypt, and am I missing any features by not flashing it through recovery, don't really care, just asking, but if you can please send me a boot.img for the verison I posted earlier in the thread.
Thanks so much for your help
Click to expand...
Click to collapse
Apologies for the late reply, been a bit busy with my family. It looks like Franco is one of the kernels that doesn't have the boot.img directly inside the zip. There's probably a way to extract it but it's beyond my expertise. I'm in the process of extracting the boot.img from some other popular kernels for you now though, I'll update here once I have some uploaded. It might take a while because my upload speed is woefully slow.
gigawatt said:
well I downloaded fk-r12-anykernel2.zip and unzipped it and there was no boot.img inside, so, can you send me a link to a boot.img for his kernel or the stock with no force encrypt, and am I missing any features by not flashing it through recovery, don't really care, just asking, but if you can please send me a boot.img for the verison I posted earlier in the thread.
Thanks so much for your help
Click to expand...
Click to collapse
Actually, it turns out none of the kernels have an easily accessible boot.img inside the zip. Things have changed since I last unpacked a kernel. I'll see what I can find out for you.
Here my friend use this thread. From @Tigerstown
https://tapatalk.com/shareLink?url=...share_tid=3306684&share_fid=3793&share_type=t
[UPDATED 3-10-16][Stock modified boot.img for regular root/Android N decrypted boot
It contains a stock modified boot image allowing system root and no force encryption. He updates thread for every build. Flash right from fastboot. If you need anything else feel free to PM me.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
Here my friend use this thread. From @Tigerstown
https://tapatalk.com/shareLink?url=...share_tid=3306684&share_fid=3793&share_type=t
[UPDATED 3-10-16][Stock modified boot.img for regular root/Android N decrypted boot
It contains a stock modified boot image allowing system root and no force encryption. He updates thread for every build. Flash right from fastboot. If you need anything else feel free to PM me.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Is this the link you meant?
http://forum.xda-developers.com/showthread.php?t=3306684
Yours is directing to download Tapatalk.
PS. Please conduct troubleshooting help in the open forum, the information is of no use to other people searching for it if it's hidden away in an inbox.
PPS. Fantastic idea by the way, I had forgotten about that thread.
Heisenberg said:
Is this the link you meant?
http://forum.xda-developers.com/showthread.php?t=3306684
Yours is directing to download Tapatalk.
PS. Please conduct troubleshooting help in the open forum, the information is of no use to other people searching for it if it's hidden away in an inbox.
PPS. Fantastic idea by the way, I had forgotten about that thread.
Click to expand...
Click to collapse
Yes that's the correct link. I shared it from Tapatalk instead of web browser. Thank you for grabbing the correct one.
Sent from my Nexus 6P using Tapatalk
Heisenberg said:
Apologies for the late reply, been a bit busy with my family. It looks like Franco is one of the kernels that doesn't have the boot.img directly inside the zip. There's probably a way to extract it but it's beyond my expertise. I'm in the process of extracting the boot.img from some other popular kernels for you now though, I'll update here once I have some uploaded. It might take a while because my upload speed is woefully slow.
Click to expand...
Click to collapse
If they are using anykernel zip there is no boot.img.
---------- Post added at 10:38 AM ---------- Previous post was at 10:35 AM ----------
Heisenberg said:
Is this the link you meant?
http://forum.xda-developers.com/showthread.php?t=3306684
Yours is directing to download Tapatalk.
PS. Please conduct troubleshooting help in the open forum, the information is of no use to other people searching for it if it's hidden away in an inbox.
PPS. Fantastic idea by the way, I had forgotten about that thread.
Click to expand...
Click to collapse
I posted that thread in General. I should have posted in dev threads but less traffic the better for me answering the same questions over and over ??
Android N Preview 5 beta npd90g (flashable & image, no encryption & dm verification)
** DISCLAIMER: APPLY AT YOUR OWN RISK **** The following are instructions for installing Android N Preview 5 image released by Google on 7/18/2016. After the installation you will have TWRP recovery 3.0.2-0 with the data partition erased and unencrypted if you use method 2 **Always backup your data before flashing something a total stranger gives you!
Method 1: Flash update through TWRP recovery (keeps your data and current recovery)
1- You need to have TWRP 3.0.2-0 or higher installed on your phone.
2- Download this flashable zip.
3- Copy to the phone internal storage and flash via recovery.
4- Reboot. Your data should still be intact and your OS is upgraded to N Preview 5 beta. If your internal storage is unencrypted before flashing it remains unencrypted.
Method 2: Flash update using a computer (wipes everything, unencrypts data, and upgrades TWRP)
1- ALL of your data including the internal storage will be lost so make a backup. (If you know what you are doing and you are coming from unencrypted Marshmallow you can modify the instructions to not lose data but I won't help you with that).
2- Download this file. Note that it is NOT a flashable zip.
3- Unzip into a folder of your choice on your PC.
4- Open a command window (cmd) and cd to this directory. then run the following:
Code:
flash-all
5- Wait until prompted, then press key to reboot the phone.
6- Your data is wiped and your OS is upgraded to N Preview 5 beta with unencrypted internal storage. Your TWRP is also upgraded to 3.0.2-0.
Technical details: this is a repacking of the Google image with a modified Kernel and removed userdata and recovery images. Everything else is stock.
Problem downloading from Mega on a mobile browser? Change the page setting to "Request desktop site".
About root and other issues
To obtain root after installing this update you should flash SuperSU 2.76 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.
Cool thanks.. Will android pay still work?
The link doesn't work for me (method 1). Brings up a blank page.
edit - sorry, I see it's still being uploaded. When I first looked on my phone it said this was posted at 5:37 am. When I logged in on my computer just now it says 11:37 pm (25 min ago).
Thanx! Just got the OTA Update available message - can I flash the OTA as well when I am coming from your unencrypted Android N4?
yeticomes said:
Thanx! Just got the OTA Update available message - can I flash the OTA as well when I am coming from your unencrypted Android N4?
Click to expand...
Click to collapse
If you take the google OTA your phone will be encrypted and your recovery will be replaced with google's. If you want to keep the recovery and unencrypted sdcard then flash the flashable file above (method 1) that I just finished uploading.
do you have to be on N already, to flash using method #1, and also, are the normal wiping methods required?
i4cbj45 said:
do you have to be on N already, to flash using method #1, and also, are the normal wiping methods required?
Click to expand...
Click to collapse
You can be on whatever rom you want. Just do a full wipe (data,system etc) and don't wipe sdcard. Then make sure you have TWRP 3.0+. And just flash the zip from method 1. I just did and it's working perfect.
Thanks @najoor !
Why is it always after I post that I realized what I did wrong? LOL edited and deleted.
Sent from my Nexus 6 using XDA-Developers mobile app
Can someone post a direct browser link, as yet again, I cannot download the file. Thanks.
can somebody upload the flashable no-encrypted zip ? i only want to flash that after the clean reinstall.
Works great thanks bud
Sent from my Nexus 6 using XDA Free mobile app
I'm currently on preview 4 with twrp and root with elemental. Do I need to restore the stock kernel before flashing method 1?
Thanks for your work on this, najoor!
Edit - Autocorrect mis-correcting my spelling
Sent from my Nexus 6 using XDA-Developers mobile app
a8ksh4 said:
I'm currently on preview 4 with twrp and root with elemental. Do I need to restore the stock kernel before flashing method 1?
Thanks for your work on this, najoor!
Edit - Autocorrect mis-correcting my spelling
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
No but your kernel will be replaced with N kernel and if any of your apps depend on the elemental kernel they will stop working.
ronaldheld said:
Can someone post a direct browser link, as yet again, I cannot download the file. Thanks.
Click to expand...
Click to collapse
SamS1989 said:
can somebody upload the flashable no-encrypted zip ? i only want to flash that after the clean reinstall.
Click to expand...
Click to collapse
https://zenety.stackstorage.com/index.php/s/8l9jCllpEIaaEMa/download
Can someone report the baseband version on this? Is it the 5.39R?
Thanks. And thank you OP!
Edit/Update :
It is indeed 5.39R. Thanks again.
Hotspot works after adding build.prop line
Thank you najoor, for making this process easier and possible for us to get a run at the preview
Hotspot works?
Sent from my Nexus 6 using Tapatalk
ArieleGiron said:
Hotspot works?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Look 2 posts up^^^
yankeesfan714 said:
Look 2 posts up^^^
Click to expand...
Click to collapse
Thanks buddy!!
Sent from my Nexus 6 using Tapatalk
Follow at your own risk, I take no responsibility. This guide is for any stock(seems to work with mods) rom. I used TWRP RC1, but could possibly work with alpha 2(for adb sideload only). Not sure if this method is "better" than using flash-all.bat without -w, but the file download was smaller.
Required Files and Locations they should be placed:
TWRP RC1 Image placed in the same folder as your FASTBOOT executable
TWRP RC1 zip installer placed on phones internal storage
SuperSU 2.79 SR3 zip installer placed on phones internal storage
NOF27B or NOF27C - Rogers OTA placed in the same folder as your ADB executable
Ensure the TWRP and SuperSU zip installers are loaded onto the phones internal storage and the OTA zip and TWRP image are in the ADB/FASTBOOT executables folder.
Boot into current TWRP recovery
Make a full backup in TWRP
Connect the phone to the computer
In TWRP select the Advanced menu, click ADB sideload option
On the computer open a command window and navigate to the location of your ADB executable/OTA zip
Only execute one adb sideload command for your specific device
Execute the following command(Non-Rogers): adb sideload sailfish-ota-nof27b-8130b5a8.zip
Execute the following command(Rogers): adb sideload sailfish-ota-nof27c-fb487658.zip
Only execute one adb sideload command for your specific device
The command window should be displaying a percentage and the TWRP should be displaying the standard OTA step 1 and 2 - Let this complete
Click Reboot System and let the OTA finish installing
At this point TWRP and Root are gone, but can be restored
With the device powered off, hold volume down and turn on the device. Your device should now be in the bootloader.
With the device connected to the computer run the following command from the previous step's command window: fastboot boot twrp-3.0.2-0-RC1-fastboot-sailfish.img
Install twrp-pixel-installer-sailfish-3.0.2-0-RC1.zip in TWRP
Install SR3-SuperSU-v2.79-SR3-20170114223742.zip in TWRP
Click Reboot System
Install Kernel/Mods
Remember to restore any /system specific edits such as the tether build.prop edit, host file edits, or custom boot animations.
This is amazing!. I have downloaded the full factory image already. followed by your guide, Can I just use an OTA package to upgrade NMF26O to latest build? I have rooted and twrp installed
bush911 said:
This is amazing!. I have downloaded the full factory image already. followed by your guide, Can I just use an OTA package to upgrade NMF26O to latest build? I have rooted and twrp installed
Click to expand...
Click to collapse
Just remove the -w argument from the flash-all.bat and flash the factory image...
Thank you dude, so what's the difference between full factory image and full ota zip, and ota automatically downloaded to phone.
the factory image is around 1.8 G and full ota zip is around 800 M, but the ota automatically downloaded to phone is only 47 M
Juli112 said:
Just remove the -w argument from the flash-all.bat and flash the factory image...
Click to expand...
Click to collapse
I had good luck with this method getting to NMF26O. Just a couple of things to note. Make sure you have the latest ADB files, and while it probably is assumed that you are using TWRP RC1 I'm pretty sure this did not work in Alpha2. Also, when the OP mentions losing TWRP it actually completely removes recovery so don't freak out if you try to boot into it expecting stock recovery and get a no data (or something like that if I remember correctly) error. There is no reason to check, but last time I was curious to see if it would leave TWRP in place. All is fine as long as you can get to bootloader. One other thing is the fact that this is an OTA. I would not do this unless coming from NMF26O but that is just me.
I am in no hurry to do this update since by all accounts it adds no functionality, but I was going to try it this way again. I wonder if anyone has any reason other than habit to continue to use the flash all method.
Juli112 said:
Just remove the -w argument from the flash-all.bat and flash the factory image...
Click to expand...
Click to collapse
so should we sideload the OTA over Q or download the factory image and remove the -w flag and run flash all.bat?
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
quinejh said:
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
Click to expand...
Click to collapse
This is only for updating stock. If you want of weta then use the full image and remove the -w from the flashall bat file.
thank you! worked great!
quinejh said:
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
Click to expand...
Click to collapse
Because I'm groovy like that... (And had a nandroid backup) I went ahead and took the jump of sideloading the OTA update over weta 2.2.1. Personally, I wasn't too concerned about botching up the system, as the weta ROM is going away. Instead the author is now compiling his mod(s) to layer over this stock build. I'm assuming that the OTA sideload went without a hitch because weta is designed around the stock image. Of course, I had to install some of my mod's again that were lost in the "update"
**DISCLAIMER**
I'm not claiming or declaring the OTA update is safe to install over weta 2.2.1. I'm only giving my experience so others can weigh out the risks for themselves, if they decide to roll the dice. :silly:
I followed this method and everything went smoothly. I have the new update, supersu and elemental kernel but now I can not use android pay
rohitece06 said:
I followed this method and everything went smoothly. I have the new update, supersu and elemental kernel but now I can not use android pay
Click to expand...
Click to collapse
I don't use Pay, but did you update to the latest Elemental kernel 1.03?
spiller37 said:
I don't use Pay, but did you update to the latest Elemental kernel 1.03?
Click to expand...
Click to collapse
Yes I did.
rohitece06 said:
Yes I did.
Click to expand...
Click to collapse
Try Franco's, his is patched for pay. Just to try and narrow it down here.
rohitece06 said:
Yes I did.
Click to expand...
Click to collapse
You might also try the patched stock kernel that was just updated.
spiller37 said:
You might also try the patched stock kernel that was just updated.
Click to expand...
Click to collapse
Thanks it worked with patched stock kernel although I lost root and when I installed SuperSu 2.79 SR2 android pay stopped working.
Is something up with the OP or is it just my XDA app causing it to show like this..
aholeinthewor1d said:
Is something up with the OP or is it just my XDA app causing it to show like this..
Click to expand...
Click to collapse
Not sure why it displays this way in the two XDA apps. If anyone knows how to fix the formatting I would be grateful for the solution.
rohitece06 said:
Thanks it worked with patched stock kernel although I lost root and when I installed SuperSu 2.79 SR2 android pay stopped working.
Click to expand...
Click to collapse
Oh I didn't realize root and pay could work simultaneously on the pixel yet. Not sure which thread, but there was discussion on using the dual slots to run one slot stock with pay and one slot stock with root. Then dual booting between them.
spiller37 said:
Oh I didn't realize root and pay could work simultaneously on the pixel yet. Not sure which thread, but there was discussion on using the dual slots to run one slot stock with pay and one slot stock with root. Then dual booting between them.
Click to expand...
Click to collapse
it was working before this January pixel update