Develop Bugs

[Q] Recovered my Nexus 7 to 4.4.4 but can't find any recovery mode

Guys I am facing this weird issue. Earlier I had TWRP installed on my nexus 7 with android 4.4.2 but since I was unable to install any OTA updates for 4.4.4 I figured maybe it was an issue with the TWRP so I wanted to get rid of it. I used One Click Factory Restore 4.4.4 KTU84P tool in the dev forums and it kinda did restore my tab to a stock version. The issue is now when I try to boot into recovery mode, it shows an error logo and seemingly there is no recovery installed. How do I go to stock recovery from here? Any help will be appreciated.
Thanks

ammy_91 said:
Guys I am facing this weird issue. Earlier I had TWRP installed on my nexus 7 with android 4.4.2 but since I was unable to install any OTA updates for 4.4.4 I figured maybe it was an issue with the TWRP so I wanted to get rid of it. I used One Click Factory Restore 4.4.4 KTU84P tool in the dev forums and it kinda did restore my tab to a stock version. The issue is now when I try to boot into recovery mode, it shows an error logo and seemingly there is no recovery installed. How do I go to stock recovery from here? Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
If you mean by error logo, you see an image of an android on its back, that is recovery, stock recovery. You can still use the OTA with TWRP, so you pretty much wasted your time removing it, the only difference is with TWRP you have to flash the OTA manually (the OTA zip is located in /cache).
So reinstall the latest TWRP, and reroot, and have fun with 4.4.4.
If you want your device to be even more useful and future upgrades to be easier, instead of leaving normal TWRP on it, after rooting, install MultiROM along with its modified TWRP, and make your device even better.

Galaxy S4 SM-N910P Stuck in Bootloop After Trying to Root With Odin

aboot fused 4 binary 1
hi, i was trying to root my note 4 sm-n910p from sprint using odin, i check in debbuging mode and everything, tried to run the cf autoroot for my phone and it seemed like it was done correctly because the red android appeared and odin said passed. but after that red android appears and all of that it tries to reboot and it gets stuck on the sprint logo just after the samsung one comes up, i can still get into recovery and download modes, i tried hard reseting a couple of times but when i try to reboot it just gets stuck again and reboots and reboots, i tried downgrading to a previous firmware and when i use odin to do it says fail and on the phone the downloading mode says sw rev check fail : (aboot) fused 4 > binary 1, (1) emmc write fail: aboot plz help my baby has been like this for a day now and im desperate :c

If you were on the latest OTA OG5, you can't fully root with CFAutoRoot and you can't downgrade.
As long as you weren't on a bootloader OB7 or below, no harm in going back to Odin or KIES recovery to stock tar OG5.
Remember, if you're trying to root OG5, you need the exploited kernel. Look for freeza's thread in general section hello root 5.1.1
Odin recovery first, then flash the kernel.
This might get you started
http://forum.xda-developers.com/showthread.php?p=62241991
Sent from my SM-N910P using Tapatalk

I'm Also facing the same problem any solutions to this? I took the OTA update of 6.0 but it was restarting again and again so I wiped the system and tried to install the 5.0 AND GOT THIS emmc error

Grv0541 said:
I'm Also facing the same problem any solutions to this? I took the OTA update of 6.0 but it was restarting again and again so I wiped the system and tried to install the 5.0 AND GOT THIS emmc error
Click to expand...
Click to collapse
You've found a very old thread. If you saw the aboot with fuse error along with eMMC like above, you may be OK as long as you don't keep trying to flash anything less than OG5 with Odin.
If it's Lollipop you're after, try OK1 and the latest Lollipop ROM.
If early Lollipop 5.0 or KitKat, you'll need the kernel linked in above thread you quoted but don't use Odin for full stock tar downgrade. But you may need Odin for Lollipop bootloader firmware.
Do you have any TWRP backups for KitKat or 5.0? You could still use those if you downgrade bootloader to OG5 and use the OG5 kernel mentioned earlier.
What may have happened with Marshmallow rebooting was remnant of ItsOn left on internal memory. If that was the issue, you can likely run Marshmallow but you need to wipe internal memory to clean install Marshmallow.
One last thing (important that you review this before you begin) : do you recall what update you had before you wiped system and tried to flash 5.0? You may need to flash that same update (full stock tar) and go through the setup wizard and use same Google user and password to get past that factory reset protection. Sometimes it gets buggy when you try to flash a lower security bootloader in Odin and phone just doesn't seem to flash a different update until you do that or bypass the factory reset protection.
Sent from my SM-N920P using Tapatalk

First of all, thank you for replying I really need your help so here it is
1- I was on KitKat 4.4 when I started ( I'm having the complete backup in twrp 4.4 GB)
2- then I flashed 'N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar" using Odin everything was working fine ( I'm also having the
backup except the system in twrp around 1.1 GB )
3- then I flashed 'Hybrid-x 5.1' that's where it first restarted faced boot loop flashed twrp everything was ok
4- then i decided to go back to 'step-2' i flashed again using Odin everything was Good then ROM download the update VIA OTA I don't know how i received but I did then I installed MM
install through OTA
5- On 'MM 6.0' it was restarting again and again but phone was working for around 20 min then I have to perform factory reset
6- I tried step-2 'N910PVPU1BOB7' And that's whee I got emmc error via Odin I tried again and again
7- Then I tried to restore backup of Lolipop and installed Emotion Rom but no networks everything was working fine else
8- And then I tried to flash 5.0 hybrid x but failed ad\nd stucked into boot loop
9- Then I downloaded 'N910PVPU4COG5 Sprint USA repair version' but failed miserably
10- then I downloaded 'N910PVPS4DQB3_N910PSPT4DQB3_N910PVPS4DQB3_HOME.tar.md5' and flashed it, I think it's MM but didn't work
11 - I read your reply stopped trying
Now before installing every Rom I performed clean installation wiped internal memory and everything except micro sd
and coming to your question I do have the backup of KitKat and 5.0 and I don't want MM I just want my phone back, and after reviewing I was on 4.4 kit kat before installing 5.0
"You may need to flash that same update (full stock tar) and go through the setup wizard and use same Google user and password to get past that factory reset protection. Sometimes it gets buggy when you try to flash a lower security bootloader in Odin and phone just doesn't seem to flash a different update until you do that or bypass the factory reset protection"
And i'm receiving that emmc error only on 5.0 & i'm also getting that 'Kernel is not seandroid enforcing set warranty bit: kernel' and keeps on boot looping but i don't think it's a problem isn't it
I don't know how to through Please guide you have everything and now i'm stucked on boot looo
and tell me how to use the Backup or kenrel
---------- Post added at 11:30 AM ---------- Previous post was at 11:04 AM ----------
samep said:
You've found a very old thread. If you saw the aboot with fuse error along with eMMC like above, you may be OK as long as you don't keep trying to flash anything less than OG5 with Odin.
If it's Lollipop you're after, try OK1 and the latest Lollipop ROM.
If early Lollipop 5.0 or KitKat, you'll need the kernel linked in above thread you quoted but don't use Odin for full stock tar downgrade. But you may need Odin for Lollipop bootloader firmware.
Do you have any TWRP backups for KitKat or 5.0? You could still use those if you downgrade bootloader to OG5 and use the OG5 kernel mentioned earlier.
What may have happened with Marshmallow rebooting was remnant of ItsOn left on internal memory. If that was the issue, you can likely run Marshmallow but you need to wipe internal memory to clean install Marshmallow.
One last thing (important that you review this before you begin) : do you recall what update you had before you wiped system and tried to flash 5.0? You may need to flash that same update (full stock tar) and go through the setup wizard and use same Google user and password to get past that factory reset protection. Sometimes it gets buggy when you try to flash a lower security bootloader in Odin and phone just doesn't seem to flash a different update until you do that or bypass the factory reset protection.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Please Have a Look

Grv0541 said:
First of all, thank you for replying I really need your help so here it is
1- I was on KitKat 4.4 when I started ( I'm having the complete backup in twrp 4.4 GB)
2- then I flashed 'N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar" using Odin everything was working fine ( I'm also having the
backup except the system in twrp around 1.1 GB )
3- then I flashed 'Hybrid-x 5.1' that's where it first restarted faced boot loop flashed twrp everything was ok
4- then i decided to go back to 'step-2' i flashed again using Odin everything was Good then ROM download the update VIA OTA I don't know how i received but I did then I installed MM
install through OTA
5- On 'MM 6.0' it was restarting again and again but phone was working for around 20 min then I have to perform factory reset
6- I tried step-2 'N910PVPU1BOB7' And that's whee I got emmc error via Odin I tried again and again
7- Then I tried to restore backup of Lolipop and installed Emotion Rom but no networks everything was working fine else
8- And then I tried to flash 5.0 hybrid x but failed ad\nd stucked into boot loop
9- Then I downloaded 'N910PVPU4COG5 Sprint USA repair version' but failed miserably
10- then I downloaded 'N910PVPS4DQB3_N910PSPT4DQB3_N910PVPS4DQB3_HOME.tar.md5' and flashed it, I think it's MM but didn't work
11 - I read your reply stopped trying
Now before installing every Rom I performed clean installation wiped internal memory and everything except micro sd
and coming to your question I do have the backup of KitKat and 5.0 and I don't want MM I just want my phone back, and after reviewing I was on 4.4 kit kat before installing 5.0
"You may need to flash that same update (full stock tar) and go through the setup wizard and use same Google user and password to get past that factory reset protection. Sometimes it gets buggy when you try to flash a lower security bootloader in Odin and phone just doesn't seem to flash a different update until you do that or bypass the factory reset protection"
And i'm receiving that emmc error only on 5.0 & i'm also getting that 'Kernel is not seandroid enforcing set warranty bit: kernel' and keeps on boot looping but i don't think it's a problem isn't it
I don't know how to through Please guide you have everything and now i'm stucked on boot looo
and tell me how to use the Backup or kenrel
---------- Post added at 11:30 AM ---------- Previous post was at 11:04 AM ----------
Please Have a Look
Click to expand...
Click to collapse
Your modified stock TWRP backups older than OG5 will need the Lollipop bootloader and the kernel. Seems OG5 bootloader and OG5 Beastmode kernel is what you need.
Your TWRP backups cannot restore bootloader and they may not have the kernel you now need to get those to boot.
Emotion probably didn't work because you need the Lollipop bootloader for connectivity. Keep in mind that internal memory isn't compatible from CM to stock. Your wipes are warranted when crossing platforms like that. But clean installs are a good idea too.
So you at least need the Lollipop bootloader for CM. There's a thread by freeza in our development forum for baseband and bootloader. The ones labeled firmware are bootloaders. You need to Odin that as a tar in AP mode.
Modified stock is just a step or two more. The order of install isn't so important as long you flash kernel zip after restoring the TWRP backup for backups older than OG5. The bootloader can be installed first or last. But the bootloop is likely due to older kernels not working with the newer bootloader. Flash kernel prior to boot. You may also need to flash SuperSU zip again but try the kernel and attempt boot before trying to install SuperSU again. It may depend on the original SuperSU installed; I haven't done this but familiar with posts but recall and steps others may omit may be lacking but I think you can figure it out with the general idea.
But remember your bootloader cannot be downgraded to Android 5.0 or KitKat. That also means you cannot Odin 5.0 or KitKat stock tars.
The older stock backups (KitKat and Lollipop 5.0) should work with lollipop 5.1 bootloader and OG5 Beastmode kernel.
Since you had some success with Emotion ROM, it's possible you don't need to Odin Marshmallow for factory reset protection. I think the kernel for Emotion is fine but you need the OG5 bootloader for that backup to connect.
Sent from my SM-N920P using Tapatalk

samep said:
Your modified stock TWRP backups older than OG5 will need the Lollipop bootloader and the kernel. Seems OG5 bootloader and OG5 Beastmode kernel is what you need.
Your TWRP backups cannot restore bootloader and they may not have the kernel you now need to get those to boot.
Emotion probably didn't work because you need the Lollipop bootloader for connectivity. Keep in mind that internal memory isn't compatible from CM to stock. Your wipes are warranted when crossing platforms like that. But clean installs are a good idea too.
So you at least need the Lollipop bootloader for CM. There's a thread by freeza in our development forum for baseband and bootloader. The ones labeled firmware are bootloaders. You need to Odin that as a tar in AP mode.
Modified stock is just a step or two more. The order of install isn't so important as long you flash kernel zip after restoring the TWRP backup for backups older than OG5. The bootloader can be installed first or last. But the boot loop is likely due to older kernels not working with the newer bootloader. Flash kernel prior to boot. You may also need to flash SuperSU zip again but try the kernel and attempt boot before trying to install SuperSU again. It may depend on the original SuperSU installed; I haven't done this but familiar with posts but recall and steps others may omit may be lacking but I think you can figure it out with the general idea.
But remember your bootloader cannot be downgraded to Android 5.0 or KitKat. That also means you cannot Odin 5.0 or KitKat stock tars.
The older stock backups (KitKat and Lollipop 5.0) should work with lollipop 5.1 bootloader and OG5 Beastmode kernel.
Since you had some success with Emotion ROM, it's possible you don't need to Odin Marshmallow for factory reset protection. I think the kernel for Emotion is fine but you need the OG5 bootloader for that backup to connect.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I Downloaded
1- OG5 Baseband by Freeza+0G5 Bootloader +Beatmode stock 1.0 and first flashed Kernel Failed! then I tried beastmode kernel r56 succeeded and then I flashed bootloader of OG5 after that Rom Emotion result= No boot at all
2- Then I wiped everything and Tried to install OG5 tar via Odin but again Boot loop
3- Tried Hybrid Rom but again Boot loop
4- And one more thing for the first time I flashed Emotion that was the last time phone booted after it's stucked on boot loop tried everything but I'm failing miserably
So tell me what should I do to Get a boot?
So tell me what to do I don't care whether I'm running MM or lollipop I just want my device back, Tell me the exact order if there Is any other like you said flash the kernel first and after bootloader, Help me

Grv0541 said:
I Downloaded
1- OG5 Baseband by Freeza+0G5 Bootloader +Beatmode stock 1.0 and first flashed Kernel Failed! then I tried beastmode kernel r56 succeeded and then I flashed bootloader of OG5 after that Rom Emotion result= No boot at all
2- Then I wiped everything and Tried to install OG5 tar via Odin but again Boot loop
3- Tried Hybrid Rom but again Boot loop
4- And one more thing for the first time I flashed Emotion that was the last time phone booted after it's stucked on boot loop tried everything but I'm failing miserably
So tell me what should I do to Get a boot?
So tell me what to do I don't care whether I'm running MM or lollipop I just want my device back, Tell me the exact order if there Is any other like you said flash the kernel first and after bootloader, Help me
Click to expand...
Click to collapse
Emotion is CM, right? I wouldn't think Beastmode would boot a CM ROM or backup.
Your TWRP backups don't boot with OG5 bootloader and flashing Beastmode kernel after restoring backup?
The bootloop issues may be data incompatibility. Are you wiping everything but ext sdcard before restoring backup? I think it should work by wiping, restore backup but flash Beastmode before attempting boot. If not, flash latest SuperSU zip from Chainfire. One of those steps should get a boot.
But maybe just a simple factory reset works?
If looking to get going with Odin, you need to flash full stock tar OG5 or higher. There's stock tars to download in the general thread for Sprint Note 4.
You may need to flash original tar that matches the last one you ran successfully before you tried to flash OB7. Or Samsung Smart Switch emergency recovery may do that too.
Weird that TWRP sometimes doesn't wipe after that fuse error. Some have found that stock recovery then factory reset or Philz touch recovery and factory reset may work better than TWRP.
I'd try Smart Switch first though. With Odin, you may need to flash full stock tar, factory reset in stock recovery and flash stock tar again, letting it auto reboot on second flash.
Sent from my SM-N920P using Tapatalk

How to downgrade from 7.0 to 6.0.1?

Hi all,
yesterday I did the update to 7.0 via TWRP. Everything is working well, but I am missing Xposed.
So, how can I downgrade to 6.0.1? Just flashing 6.0.1 via TWRP?

Ask support. They told us when u have beta they've a special roll back build to flash? I hear something like this.

Just flash twrp, Format data, wipe everything flash the stock MM rom zip and reboot if using custom rom make sure to flash correct firmware for that version

It depends the steps you took, I think there are some threads about this but from my knowledge if you are still on ext4, unlocked bootloader and custom recovery, a simple clean flash should work...
But do check
Here is something that could help https://forum.xda-developers.com/oneplus-3/how-to/guide-downgrade-to-mm-flashing-ob8-t3511161/page3

ox_eye said:
Hi all,
yesterday I did the update to 7.0 via TWRP. Everything is working well, but I am missing Xposed.
So, how can I downgrade to 6.0.1? Just flashing 6.0.1 via TWRP?
Click to expand...
Click to collapse
1. Take a nandroid backup
2. Boot to TWRP
3. Wipe-> advanced wipe-> system change partition to TWRP
4. Wipe- all
5. flash 3.0.2 TWRP
6. Reboot to TWRP and then flash 6.0.1
Hit thanks if I helped
Sent from my iPhone using Tapatalk

I have tried to flash 3.0.2-1 twrp but i cannot. Is there any solution for downgrade? Even with toolkit v2.6 is impossible.

bam bam boom said:
I have tried to flash 3.0.2-1 twrp but i cannot. Is there any solution for downgrade? Even with toolkit v2.6 is impossible.
Click to expand...
Click to collapse
Use the latest twrp beta version or modded twrp by eng.stk, backup data and clean flash 3.2.8 and make sure you change data partition to ext4.

ox_eye said:
Hi all,
yesterday I did the update to 7.0 via TWRP. Everything is working well, but I am missing Xposed.
So, how can I downgrade to 6.0.1? Just flashing 6.0.1 via TWRP?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-3/help/dont-device-questions-t3567164

Caught in Recovery Bootloop

Recently I flashed through TWRP Resurrection Remix new 7.1.1 Nougat on my Tmobile Note3. Was working great. I had the newest twrp 3.0. I was looking at a custom ROM that said I would need CWM so I downloaded CWM from Google play and I ran it. I decided to back up through CWM and it rebooted my phone. My phone rebooted into recovery, and is stuck in recovery bootloop now. It keeps rebooting into recovery. I tried to fix by taking out battery for a long time but when I turn it on againit goes back to recovery in the loop. It can power into download mode. I don't know what to do in that mode though. Please help me. If I'm to use a computer to flash a different OS please include all links to find the downloads as well as the links for finding the usb drivers. Anyone know what I'm to do?

pax216 said:
Recently I flashed through TWRP Resurrection Remix new 7.1.1 Nougat on my Tmobile Note3. Was working great. I had the newest twrp 3.0. I was looking at a custom ROM that said I would need CWM so I downloaded CWM from Google play and I ran it. I decided to back up through CWM and it rebooted my phone. My phone rebooted into recovery, and is stuck in recovery bootloop now. It keeps rebooting into recovery. I tried to fix by taking out battery for a long time but when I turn it on againit goes back to recovery in the loop. It can power into download mode. I don't know what to do in that mode though. Please help me. If I'm to use a computer to flash a different OS please include all links to find the downloads as well as the links for finding the usb drivers. Anyone know what I'm to do?
Click to expand...
Click to collapse
Hello,
I will move your thread to the correct section, whereas experts there might be able to assist you.
Regards
Vatsal,
Forum Moderator.

pax216 said:
Recently I flashed through TWRP Resurrection Remix new 7.1.1 Nougat on my Tmobile Note3. Was working great. I had the newest twrp 3.0. I was looking at a custom ROM that said I would need CWM so I downloaded CWM from Google play and I ran it. I decided to back up through CWM and it rebooted my phone. My phone rebooted into recovery, and is stuck in recovery bootloop now. It keeps rebooting into recovery. I tried to fix by taking out battery for a long time but when I turn it on againit goes back to recovery in the loop. It can power into download mode. I don't know what to do in that mode though. Please help me. If I'm to use a computer to flash a different OS please include all links to find the downloads as well as the links for finding the usb drivers. Anyone know what I'm to do?
Click to expand...
Click to collapse
I find it odd that you would find a ROM that suggests CWM instead of TWRP, but the way I see it is you go back to Resurrection Remix or try to flash the new ROM you found with TWRP (2.8.7 is recommended)
You can download the .tar file for TWRP 2.8.7 here: https://dl.twrp.me/hlte/twrp-2.8.7.0-hlte-4.4.img.tar.html
For clearer instructions, you can visit this post: https://forum.xda-developers.com/showthread.php?t=2672393
These are instructions to flash back to stock, root and install TWRP 2.8.7
I suggest right after doing this, you flash the ROM you want, that will guarantee a "cleaner" installation of the ROM
Good luck!

ShaDisNX255 said:
I find it odd that you would find a ROM that suggests CWM instead of TWRP, but the way I see it is you go back to Resurrection Remix or try to flash the new ROM you found with TWRP (2.8.7 is recommended)
You can download the .tar file for TWRP 2.8.7 here: https://dl.twrp.me/hlte/twrp-2.8.7.0-hlte-4.4.img.tar.html
For clearer instructions, you can visit this post: https://forum.xda-developers.com/showthread.php?t=2672393
These are instructions to flash back to stock, root and install TWRP 2.8.7
I suggest right after doing this, you flash the ROM you want, that will guarantee a "cleaner" installation of the ROM
Good luck!
Click to expand...
Click to collapse
Thank you for your help. I did all the clear instructions from the thread. I couldn't get the CF auto root to stick. Also couldn't find a surfboard for TWRP 2.8.7, they only have 2.8.0 on the TWRP site, or TWRP 3.0. Ultimately I've got my original factory stock lollipop back. I'm no longer rooted. I had rooted before through KingRoot. I tried again and it says that I'm out on a list for root for my phone. So my phone works again. I guess I should be happy with that.

If you want to root, you could try flashing cfautoroot with Odin.

audit13 said:
If you want to root, you could try flashing cfautoroot with Odin.
Click to expand...
Click to collapse
I did try to flash CF auto root with Odin after I flashed back to the stock ROM. But it didn't work. It stayed stuck on the T mobile screen for a very long time. So I just gave up trying to root again and stayed with the stock ROM without root. Thanks. Maybe I'll try again and see if it'll work next time.

Flashing twrp with Odin and flashing supersu from twrp had always worked for me.

audit13 said:
Flashing twrp with Odin and flashing supersu from twrp had always worked for me.
Click to expand...
Click to collapse
Will that root my device?

Yes. When I want root with stock recovery, I use cfautoroot. When I want a custom recovery and root, I flash twrp and supersu.

audit13 said:
Yes. When I want root with stock recovery, I use cfautoroot. When I want a custom recovery and root, I flash twrp and supersu.
Click to expand...
Click to collapse
OK. Thanks. Also, which version of TWRP? I can't seem to find a download for 2.8.7.0, only for 2.8.0.0 and 3.0 on the official TWRP site. Also where can I find SuperSu? Do I flash SuperSU with TWRP once TWRP is on phone? I read somewhere that the best version for TWRP is 2.8.7.0, but I can't find it anywhere.

Twrp for T-Mobile note 3: https://dl.twrp.me/hltetmo/
Flash twrp using Odin. Olen Odin, do not check anything except f reset time. Flash twrp. When you see the word reset in the status window, remove USB cable from phone, remove battery, replace battery, use button combination to boot into recovery, connect to computer, copy supersu to phone memory, flash supersu from twrp.
Supersu: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703

audit13 said:
Twrp for T-Mobile note 3: https://dl.twrp.me/hltetmo/
Flash twrp using Odin. Olen Odin, do not check anything except f reset time. Flash twrp. When you see the word reset in the status window, remove USB cable from phone, remove battery, replace battery, use button combination to boot into recovery, connect to computer, copy supersu to phone memory, flash supersu from twrp.
Supersu: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Click to expand...
Click to collapse
OK. Thank you. I will get to this next time my friend is available with the computer.

Best way to upgrade to O from current state? Stock 7.1.1 rooted.

So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!

If you don't want to wipe just update through factory image, just open the factory zip, open flash-all file and remove "-w" from last line, then execute it (update without wipe)
But I suggest to flash the stock factory image with the "-w" to make a clean install, flashing major release like 7.x -> 8.x is always better wipe to avoid potential issues.
But yes, you can first give a try without wipe and only if you find bugs try wiping. Your choice.

simply flash the OTA, then re-root

xraystyle said:
So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!
Click to expand...
Click to collapse
Use full unroot in supersu. Then take ota. Then root again after upgrading to O

Thanks for the help everyone, you pointed be in the right direction.
In the event that it might help someone else, here's what I ended up doing:
1. I downloaded the OTA, booted into the TWRP I had currently installed, and then sideloaded the OTA.
2. I used ADB to push the newest TWRP flashable zip, the latest SuperSU, and the latest SU-Hide to /sdcard on the device.
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
4. Finally, I rebooted to recovery on the phone (latest TWRP now instead of stock), and flashed SuperSU and SU-Hide.
I'm now stock, rooted, on O. No wipe necessary, kept all my apps and data. So far the OS itself has been entirely stable. I had an issue or two with a few apps after the upgrade, but those were fixed with a quick re-install. Except for Better Terminal Emulator Pro, seems it doesn't want to work on Oreo and it's no longer under active development. It's fine though, there's other terminal emulators out there.
Thanks again for the help!

xraystyle said:
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
Click to expand...
Click to collapse
Which version of TWRP do you have TWRP working with Oreo 8.0?
I can boot into the modded TWRP 3.1 (fastboot boot twrp-3-1-pixel-bootable-mod.img) but AFAIK there is no working flashable recovery for 8.0 yet.

quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.

gordonlw said:
quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.
Click to expand...
Click to collapse
That's how I did it. I don't use suhide.

Does the -w in the .bat file format or wipe the data? I want a clean clean , o-fresh in the morning feeling kind of wipe

toknitup420 said:
That's how I did it. I don't use suhide.
Click to expand...
Click to collapse
Thanks! What I ended up doing:
Decided to try and unroot and take the ota. super-su full unroot would not work. so I fastbooted to the mod twrp and flashed UPDATE-unSU. I then took the ota. then fastbooted to mod twrp and flashed super-su. worked perfect!