Related
saw some articles about this but they weren't this specific...
so I have a Nexus One 2.2.1 stock, rooted with rageagainstthecage thing...
will my phone update to 2.3 as-is, or will I have to unroot the rageagainstthecage method first?
from 2.2 to 2.2.1 I had to uninstall Universal Androot (useless anyways) and reinstall some missing APKs that I had deleted (Amazon MP3 and GenieWidget)
Don't quote me on that, but I'm pretty sure that you will not get OTA automatically. However, as soon as it's out, it will be posted here and you can flash it manually. You will loose root though.
thanks, I hope you're right. Losing root is no biggie (hopefully a nice easy root method will come up shortly)
If anything it will be here before you get the OTA anyway.
Atleast that's what happened with Froyo.
Someone will logcat the address then DL it, then it will get mirrored all over XDA
Once it's here on XDA the flashing will begin long before the OTA arrives
question
I had CM6.1 Nightlies on my N1 with Clockwork, now I went back to stock recovery, stock FRG83 and I have my bootloader unlocked.
I'm wondering if the OTA will come automaticaly (probably gonna install the "XDA" version before OTA even starts going around)?
And I'm wondering if anybody knows what is supposed to be the criteria for the OTA to come automaticaly?
I was rooted with 2.2 and got the OTA for 2.2.1.
As far as I know you need a stock rom (rooted or otherwise) with a locked bootloader.
Sent from my Nexus One using XDA App
are you certain about the locked bootloader?
Its kinda pointless to go back to stock and such if you like the CM nightlies, its what I run, because the first phones to receive the OTA will be the "Holiday" Nexus one, based on imei. It will be up on xda with many mirorrs and versions shortly after! If you remener froyo it will be like that. So just look here for the update.zip
Just my two cents
Sent from my Nexus One using XDA App
Yeah I know I was just wondering about the update process, requirements, etc.
I love CM6.1, I'll probably go back to it when I'm fed up with Ginger there was another reason to go back to stock and that's that I still had ere27 stock backup and it was time to update the stock ROM to frg83 and back that up for the future
It doesn't matter if you have an unlocked bootloader or not, nor does it matter if you have rooted. You must have a stock recovery as the ota will use it to install, if it doesn't find it the installation will fail. Previous updates were available here for rooted users before the update went ota
i also was rooted but had a stock bootloader and recovery... got the 2.2.1 OTA. lost root though.
now for my question... i dont care if i lose root for gingerbread but since i rooted.. SU is in my rom and i cant delete it. i just dont want something on my phone that i cant use.
will the gingerbread update bring me to full stock gingerbread? or would SU be still stuck there. just asking since i rooted after i got froyo so im not sure.
If memory serves, with an OTA su will be removed, but Superuser.apk will remain.
Anyways, if you try this app, you should be able to regain root with ease, even if it's only to bin the files you don't want.
Rusty! said:
If memory serves, with an OTA su will be removed, but Superuser.apk will remain.
Anyways, if you try this app, you should be able to regain root with ease, even if it's only to bin the files you don't want.
Click to expand...
Click to collapse
yeah i got root back because of that app! my main grip was superuser.apk was still in the phone without SU access. now im back to rooted i just left it there.
so basically if i get gingerbread and lose root superuser.apk will still be left in the phone? any thoughts? if so ill just delete it then install it back somewhere i could delete it if i lose root again.
I believe so, yes.
Bin it before updating to be 'safe', I guess.
Rusty! said:
I believe so, yes.
Bin it before updating to be 'safe', I guess.
Click to expand...
Click to collapse
is there an easy way to do it... say just delete it via astro file manager? this is the tutorial i used to root in the first place..
http://forum.xda-developers.com/showthread.php?t=736271
.. lost root then i used the "one click root" that first appeared in the market, then lost root again after 2.2.1 then used visionary.
theres a lot more in the phone that was put in there by rooting (like busybox right?)... but i guess superuser.apk is the visible one since it shows on the app drawer so i wanna remove it from the phone and just install it via the market.
ASTRO can't do it as far as I'm aware, but it's easy from ADB shell or a terminal:
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
rm /system/bin/su
rm /system/app/Superuser.apk
rm /system/bin/busybox
and it's goodbye root (and busybox since you mentioned it).
Rusty! said:
ASTRO can't do it as far as I'm aware, but it's easy from ADB shell or a terminal:
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
rm /system/bin/su
rm /system/app/Superuser.apk
rm /system/bin/busybox
and it's goodbye root (and busybox since you mentioned it).
Click to expand...
Click to collapse
thanks will give it some thought
krabman said:
It doesn't matter if you have an unlocked bootloader or not, nor does it matter if you have rooted. You must have a stock recovery as the ota will use it to install, if it doesn't find it the installation will fail. Previous updates were available here for rooted users before the update went ota
Click to expand...
Click to collapse
I think that the latest Amon RA will flash an update, regardless of signature verification.
GldRush98 said:
I think that the latest Amon RA will flash an update, regardless of signature verification.
Click to expand...
Click to collapse
You're right, same as the latest ClockworkMod recovery...they disable signature check
I used Epic All in One Root and Recovery v2.04 a while back to root my Epic. Uninstalled a few of the apps. Got the froyo push today but it wouldn't take, figure it had to do with removing apps and rooting. I recovered the apps and removed root. Downloaded the update.zip and booted into recovery mode to install. I'm now getting an assertion error because the install cannot find /system/bin/playlogo
I've read some threads and noticed some of the root procedures created a playlogo-orig. I don't have that file. I do have playlogos1 though, though I'm guessing that isn't the same file?
Sort of stuck on what to do next. Can't seem to locate a playlogo to download to sdcard. Any help would be appreciated.
deflin39 said:
I used Epic All in One Root and Recovery v2.04 a while back to root my Epic. Uninstalled a few of the apps. Got the froyo push today but it wouldn't take, figure it had to do with removing apps and rooting. I recovered the apps and removed root. Downloaded the update.zip and booted into recovery mode to install. I'm now getting an assertion error because the install cannot find /system/bin/playlogo
I've read some threads and noticed some of the root procedures created a playlogo-orig. I don't have that file. I do have playlogos1 though, though I'm guessing that isn't the same file?
Sort of stuck on what to do next. Can't seem to locate a playlogo to download to sdcard. Any help would be appreciated.
Click to expand...
Click to collapse
Just use Odin to flash back to stock
Sent from my SPH-D700 using XDA Premium App
deflin39 said:
I used Epic All in One Root and Recovery v2.04 a while back to root my Epic. Uninstalled a few of the apps. Got the froyo push today but it wouldn't take, figure it had to do with removing apps and rooting. I recovered the apps and removed root. Downloaded the update.zip and booted into recovery mode to install. I'm now getting an assertion error because the install cannot find /system/bin/playlogo
I've read some threads and noticed some of the root procedures created a playlogo-orig. I don't have that file. I do have playlogos1 though, though I'm guessing that isn't the same file?
Sort of stuck on what to do next. Can't seem to locate a playlogo to download to sdcard. Any help would be appreciated.
Click to expand...
Click to collapse
You are correct playlogos1 is not the same file as playlogo.The one click root should backup playlogo since it still gets run by the script that replaces playlogo it just runs playlogo-orig from the script that is named playlogo that one click installs.
Thanks for the info. I'll give Odin a shot.
Stop, listen. Follow my directions, if you fail to follow directions I will no longer help you. Don't PM me and ask. If you screw up ask in the thread.
Rooted Users (Non - Root Users scroll down below):
MR1 RUU
http://www.multiupload.com/KU7GSF2EY0
PG05IMG_MR1_no_hboot.zip - c64b4367086fff4f51ec3d5d766a0456
Bootloader (FLASH THIS LAST) FLASHING THIS WITHOUT SUCESSFULLY FLASHING THE ABOVE FILE WILL CAUSE A SECURITY WARNING
http://www.multiupload.com/26WG1UZCXR
abda920f3e159fb05c00d8c54a5b8768 - PG05IMG_hboot_1.4.0000.zip
Flash the above PG05IMG_MR1_no_hboot.zip to restore everything to stock + OTA BUT still will have the s-off bootloader.
Rename PG05IMG_MR1_no_hboot.zip as PG05IMG.zip, and flash through hboot (like in the root guide).
To restore the bootloader, rename PG05IMG_hboot_1.4.0000.zip as PG05IMG.zip and flash through the bootloader. DO NOT FLASH THIS unless you are absolutely sure PG05IMG_MR1_no_hboot.zip flashed to your device, without issue.
Now you are done, enjoy. If you screwed up, and got a security warning contact me, don't stress. Then again, don't screw up.
Non root users wanting to return to 1.12.605.6 (Stock, pre OTA) can continue below:
NOT FOR ROOT USERS
Taken from AndroidPolice: [Tutorial] How To "Un-Root" The HTC ThunderBolt And Return It To Stock. Please check the site out.
One of the most popular questions about rooting the ThunderBolt is how to undo the process and return to stock, which renews your eligibility for customer support. Well, here you go:
Instructions:
Please read the whole tutorial first, and pay attention to every detail. Note that your battery needs to be charged to at least 40% at the beginning of the process, and remember to check the MD5 sums of all downloaded files before diving in. As always, neither Android Police nor Team AndIRC are responsible for any damage this may cause to your phone, and, needless to say, returning to stock means you will no longer be able to use root apps like ShootMe and Titanium Backup.
First, download the following files:
Stock firmware (MD5 sum: 7141f5620f6128af77d50587e341f4b0)
exploits.zip (MD5 sum: 3b359efd76aac456ba7fb0d6972de3af)
Next, push exploits.zip and misc.img.
Code:
adb push misc.img /data/local/
adb push busybox /data/local/
adb shell chmod 777 /data/local/busybox
To gain root and flash misc.img:
Code:
adb shell
su
/data/local/busybox md5sum /data/local/misc.img
If the output is anything other than "c88dd947eb3b36eec90503a3525ae0de," stop and start over again.
Now let’s write misc.img:
Code:
dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
Rename "PG05IMG_Mecha_VERIZON_WWE_1.12.605.6_Radio_1.16.00.0223r_NV_8k_1.41_9k_1.64_
release_174685_signed.zip" to "PG05IMG.zip" before placing it on your SD card.
Finally, reboot into bootloader mode by entering the following command. Allow the stock firmware to flash.
Code:
adb reboot bootloader
You’re done – your phone should now be stock, S-ON.
Bookmarking this, just in case. Thanks, Jcase!
Looks like I'll be going back to Froyo for now. I believe the Sense in GB leak is older than the stock on the device.. plus.. camera doesn't work, weather in clock widget doesn't work.. quadrant score is pretty low.. As for now.. I don't see any solid reason to upgrade to GB.. (though I wish I did).. sigh!
http://forum.xda-developers.com/showthread.php?t=1082114
Follow that to return to stock from gingerbread
I am getting No Image or Wrong Image Error In Final Step. I downloaded Stock Firmware Twice but same issue!
Can anyone help me out? I am not able to return to stock. I have BAMF remix 1.6.3 installed and trying to get back to stock as i have to send this device back to Verizon for replacement. I tried everything..file name is correct....md5 sum is correct however in final step when i tried to load the stock FW the boot-loader says wrong image!!
i downloaded stock FW from every possible source but no different!
Please Help!
If I wanted to unroot and use pre ota software? Would I have to perform both procedures or is there a way to go straight to the pre ota with s-on?
spjoneser said:
If I wanted to unroot and use pre ota software? Would I have to perform both procedures or is there a way to go straight to the pre ota with s-on?
Click to expand...
Click to collapse
Take the pre ota RUU, and make a custom ruu out of it without the hboot, and then proceed with the instructions in the first half.
jcase said:
Take the pre ota RUU, and make a custom ruu out of it without the hboot, and then proceed with the instructions in the first half.
Click to expand...
Click to collapse
First of all Jcase, thanks for the time, I know it's valuable to the community.
So just so I'm clear.... All I need to do is remove "hboot_7630_1.04.0000_110223.nb0" from the pre ota ruu or is there more to be altered than just that?
And if that's all I have to do is flash those seperate, could you tell me briefly why you could not just flash all at once? Would it not flash the rest of it if the stock hboot was installed first?
spjoneser said:
First of all Jcase, thanks for the time, I know it's valuable to the community.
So just so I'm clear.... All I need to do is remove "hboot_7630_1.04.0000_110223.nb0" from the pre ota ruu or is there more to be altered than just that?
And if that's all I have to do is flash those seperate, could you tell me briefly why you could not just flash all at once? Would it not flash the rest of it if the stock hboot was installed first?
Click to expand...
Click to collapse
Yes, because some radios seem to cause the files to flash in different orders, doing it like this keeps me from having to make multiple versions.
Sent from my LG Revolution
Question I have used the oneclick program to get ride of the NV recovery but I think im still rooted because I still see my superuser program on my stock 2.2. Can I just download Rom Manager and use clockwork Recovery to flash the Zips? I have to stock recover now which just formats the phone pretty much.
Androidfreakz said:
Question I have used the oneclick program to get ride of the NV recovery but I think im still rooted because I still see my superuser program on my stock 2.2. Can I just download Rom Manager and use clockwork Recovery to flash the Zips? I have to stock recover now which just formats the phone pretty much.
Click to expand...
Click to collapse
You need to consult the author of the program, because I don't know what it did, I can't support their application.
Sent from my LG Revolution
This flashes EVERYTHING back to stock? I have my boss tripping that his phone is bad after rooting it. I want to know if this reverts the baseband back to stock too?
AnalyzeFaith said:
This flashes EVERYTHING back to stock? I have my boss tripping that his phone is bad after rooting it. I want to know if this reverts the baseband back to stock too?
Click to expand...
Click to collapse
Reverts everything back to stock + OTA
Can I still use these steps to revert to stock after flashing the leaked Gingerbread Radio?
i am rooted and so i followed directions for first file and lost root.. so for the second file(its been forever since rooting) do i run adb commands( like step 6 for rooting) for install or can i use fastboot and bootloader? Does the second file bring root back?
Droid_ALM2ND said:
Can I still use these steps to revert to stock after flashing the leaked Gingerbread Radio?
Click to expand...
Click to collapse
yes
1234567890
droidrev71 said:
i am rooted and so i followed directions for first file and lost root.. so for the second file(its been forever since rooting) do i run adb commands( like step 6 for rooting) for install or can i use fastboot and bootloader? Does the second file bring root back?
Click to expand...
Click to collapse
Of course you lost root, this is for restoring to stock. It removes root.
jcase said:
Of course you lost root, this is for restoring to stock. It removes root.
Click to expand...
Click to collapse
well the good news is it works..the bad news is i didn't realize it was back to factory stock (like out of the box) which is very useful.. my bad.. so how do i install the bootloader file?
droidrev71 said:
well the good news is it works..the bad news is i didn't realize it was back to factory stock (like out of the box) which is very useful.. my bad.. so how do i install the bootloader file?
Click to expand...
Click to collapse
if you are S-off, you can just flash the MR1 upgrade from the root guide, otherwise you have to do a complete re-root.
I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.
lbloo said:
I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.
Click to expand...
Click to collapse
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.
I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?
lbloo said:
I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?
Click to expand...
Click to collapse
rooted stock ROM yea. I've also flashed a pure aosp ROM over stock without any reprocussions.
Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.
lbloo said:
Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.
Click to expand...
Click to collapse
I don't know what you picked up, but here's a stock/rooted ROM that you can flash in your cwm recovery http://forum.xda-developers.com/showthread.php?t=1776330
Aosp works too, its your choice
if you know how to use adb you can just boot to recovery and push the stock build.prop to your tab
I downloaded a stock copy of the stock build.prop, used the adb push command to push it into /system rebooted and nothing. Still hangs on black screen upon boot.
I then downloaded the stock ROM which simms22 kindly pointed me to, used the adb push command to copy the zip file into /data/media/Firmware, used CWM v6.0.1.0 to "install zip file from sdcard" and I got an error, here is the output:
Installing:/sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
Finding update package...
Opening update package...
Installing update package...
E:Error in /sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
(Status 0)
Installation aborted.
I tried both the Odexed and Deodexed files, both gave same results.
Am I missing a step in the process?
It's working now!
I was afraid I was messing up some of the adb commands so I downloaded the Nexus 7 Toolkit 2.0 (Great tool for someone like me)
- via Toolkit re-transferred the odexed and deodexed ROM files, reflashed, same errors as above
- via Toolkit re-installed CWM Recovery 6.0.1.0, reflashed, same errors as above
- via ADB Shell used CHMOD to modify file rights of the ROM files (stab in the dark), same errors as above
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Not sure why the other ROMS would not flash, but at this point I'm not going to mess around to try to figure it out.
Many thanks to simms22 and PhxkinMassacre for getting me pointed in the right direction.
prly a bad download.
after pushing the file you need to set the correct mode:
Code:
adb shell chmod 644 /system/build.prop
Me too - also hosed my own build.prop
lbloo said:
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Click to expand...
Click to collapse
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack
Looking back I don't recall resetting the file rights after modifying the file and that was likely the root cause of my problems.
You should try the chmod command a couple of posts back.
JackinNC said:
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack
Click to expand...
Click to collapse
What location did you push it to? /sdcard/?
Sent from my Nexus 7 using xda app-developers app
mvmacd said:
What location did you push it to? /sdcard/?
Click to expand...
Click to collapse
Yes. And, to further test, I created a little zip file called test.zip and pushed it to the tablet. I can see it just fine. It's just the grouper zip that I can't find.
Thanks
Jack
I just noticed a diff in filesize between the JRO03D_grouper.zip file I am using and one shown in a Youtube video entitled "how to put a rom to flash on a semi-bricked nexus 7 with recovery" by Youtube user metroid031993. (I'm too green to post outside links on XDA)
Mine is 261814702 bytes, the one shown in the video is 32650144 bytes.
Perhaps this is my problem, an invalid zip file. What do you think? And, can someone please tell me the correct size of JRO03D_grouper.zip?
Thanks
Jack
[Note to moderator(s): If I am heading off track in this thread, please don't hesitate to move it or to instruct me to create a new thread. I think the issue may have changed, but I have stayed here since this is where the conversation is for my root issue. Thx!]
JackinNC said:
can someone please tell me the correct size of JRO03D_grouper.zip?
Click to expand...
Click to collapse
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.
Visa Declined said:
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.
Click to expand...
Click to collapse
Thanks for the confirmation.
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
---------- Post added at 11:19 AM ---------- Previous post was at 10:51 AM ----------
JackinNC said:
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
Click to expand...
Click to collapse
Well, I got the grouper zip into /sdcard/ and was able to upgrade without losing anything. w00t!
Theory:
I was in the same adb "session" this time since I was using adb from the command line. Meaning, the daemon was still running from the first push I did. So, while I couldn't see the grouper zip after the first push (consistent with your experience, dark_samus), I could see it and upgrade with it after second push (also consistent). And, perhaps my previous attempts didn't work before because I was closing and opening the Nexus 7 Toolkit each time, therefore stopping and restarting the daemon, which meant that each push attempt was the first attempt for that "session."
I don't have any solid technical basis to support or refute that theory, it's just one possible theory that, if true, would result in the experience I had.
My problem is resolved. Thanks to everyone who contributed to this, I truly appreciate your help!
Jack
simms22 said:
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.
Click to expand...
Click to collapse
how to put the stock image if my n7 doesnt boot to android? pls help
i have CWM already
Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
my bad i already flash a fresh stock rom again, but thanks anyways...
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