Develop Bugs

[Q] Stock kernel for ATT i927

Hello...anyone have stock kernel for ATT i927? Thanks.

2.3.6 upgrage is only on AT&T i believe..
and only available through OTA...
So if you are an AT & T Customer swtich back to AT&T Stock kernel and ROM and do an upgrade..

I just installed this kernel http://forum.xda-developers.com/attachment.php?attachmentid=806478&d=1323125030 and tried the update and it still didn't work. Is this the stock ATT kernel?

I think the problem lies in the recovery image. The update may be relying on the original recovery being intact (not ClockworkMod or any other). Thus, it may not be possible to update without having the original recovery in place. I have CWM recovery and the rooted kernel installed and cannot install the over-the-air updates. When I restart the phone after it's downloaded, my phone reboots into CWM and that's it. Rebooting into the OS afterwards gives me the message that the update failed.
While in recovery, I delved a bit into the filesystem using ADB and saw that the update files are there (this thread has a bit of what I'm talking about), but I don't think CWM knows what to do with them, therefore the update fails.
Are people without CWM having this problem? Furthermore, is there any way to return to the stock recovery if this is, in case, the problem?

Could you not use Odin and remove the CWM? Reflash a kernal without the CWM?

dudejb said:
Could you not use Odin and remove the CWM? Reflash a kernal without the CWM?
Click to expand...
Click to collapse
I never installed or used CWM. Is CWM something that gets installed with the rooted ROM? The only app I noticed installed with the rooted ROM was superuser and I deleted it. When I run AVG I still get the warning that my device is rooted, but when I type "su" in the emulator it says denied...is there something else I'm missing? Thanks.

CWM Recovery is what's installed if you have ever followed this guide. It's separate from the kernel and the ROM. On most phones, it's installed from ClockworkMod's ROM Manager, but we have to flash it via Odin. It replaces the stock recovery, but offers more features (such as the ability to flash ROMs from the phone itself, instead of having to use Odin on a PC, as well as allowing for full, or nandroid, backups of the phone).

I am ATT and I updated after I rooted with no problems. Some people reported that the update will fail if you're battery isn't mostly charged.
CWM won't be there unless you specifically installed it.

I would be interested in this too. I have been unable to get the update to go through after having flashed another ROM.

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

G928TUVU4DPK6 Firmware Root Issues

Has anyone upgraded their firmware to PK6 and attempted to root? I don't have any issues flashing TWRP with Odin. None whatsoever. When I flash a SuperSU zip or a PHH Superuser zip, I cannot get past the T-Mobile boot animation. It freezes every time. Once this happens I cannot boot to recovery. I can only boot to Download Mode. Hell, I can't even power down my device after I flash a root zip. Just curios if anyone has dealt with this issue. I have attempted to flash SuperSu zips starting with the 2.71 Beta up to the 2.78 SR5 with zero luck. I've also tried with PHH Superuser and I get the same results. Can anyone shed and light on the subject?
After several failed attempts to root my Galaxy S6 Edge+ (SM-G928T) with the latest firmware update to 6.0.1, G928TUVU4DPK6, this is what I had to do to get a working root solution. At no time did I ever have a problem installing TWRP with Odin. Ive been using Odin 3.12.3 but I had the same issues with Odin 3.10.7.
I started with a clean slate and performed a fresh install of the stock firmware which I downloaded from here:
http://forum.xda-developers.com/tmo...al/sm-g928t-stock-odin-g928tuvu4dpk6-t3516310
After flashing the stock firmware with Odin 3.12.3 I did the basic setup on my device to make sure I could boot and everything was working. Next, I shut down my device and booted to Download Mode by using the key combination of Volume Down + Home + Power. Once booted into Download Mode I used Odin again to flash TWRP 3.0.2-0, which is available here:
https://dl.twrp.me/zenltetmo/
After the flash was complete I booted to recovery using Volume Up + Home + Power. When TWRP starts it will ask you if you want to swipe to allow system modification. If you swipe to allow system modifications you will trigger DM-Verity and you will not be able to boot normally unless you flash a custom kernel that has DM-Verity disabled in the fstab or you can flash the no-verity-opt-encrypt.zip that I dowloaded from here:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
The newest version available is 5.0
So, I swiped to allow system modifications. Next, I transferred the no-verity-opt-encrypt.zip from my PC to my device and installed the zip in TWRP. Once this was completed, I transferred my root zip from my PC to my device. I used the PHH Superuser to root my device which is available here:
https://superuser.phh.me/superuser.zip
I installed the root zip in TWRP, wiped cache/dalvik cache and then selected Reboot System. I didnt know if I would be able to boot or not. I could never get past the T-Mobile boot animation each time I attempted to root this damn thing but low and behold everything went as planned and I was fully booted up and running. I went through the setup wizard and everything was working as it should.
I am using PHH Superuser instead of Chainfires SuperSU. Its a personal choice for me as I have been using PHH Superuser since the hand off of SuperSU to a new company, CCMT, LLC.
Once I was finally able to boot normally I downloaded PHH's app in the Play Store from here:
https://play.google.com/store/apps/details?id=me.phh.superuser
This is just my experience of what I had to do to get root working on my S6 Edge+. All of my root apps are working as designed. I cant remember the last time I didnt have a rooted device and it was starting to bother me. I was having root withdrawals. If anyone decides to upgrade to the latest firmware from T-Mobile and wants a working root solution, here is what worked for me. I have not tried to use Chainfires SuperSU again. If you dont want to use PHH Superuser and wanted to use SuperSU instead, try to insert SuperSU in place of PHH Superuser and see what happens. Do this at your own risk because I have not tested it with this solution that I found. Good luck. Happy Rooting!!

fast69mopar said:
Has anyone upgraded their firmware to PK6 and attempted to root? I don't have any issues flashing TWRP with Odin. None whatsoever. When I flash a SuperSU zip or a PHH Superuser zip, I cannot get past the T-Mobile boot animation. It freezes every time. Once this happens I cannot boot to recovery. I can only boot to Download Mode. Hell, I can't even power down my device after I flash a root zip. Just curios if anyone has dealt with this issue. I have attempted to flash SuperSu zips starting with the 2.71 Beta up to the 2.78 SR5 with zero luck. I've also tried with PHH Superuser and I get the same results. Can anyone shed and light on the subject?
Sent from my SM-G928T using XDA-Developers mobile app
Click to expand...
Click to collapse
Here is the one I used. works great

Venal_System said:
Here is the one I used. works great
Click to expand...
Click to collapse
I tried that version too and I ended up with the same problem each time. I figured it out last night though. Im going to update my OP with the steps I had to take to get it working and that way if anyone upgrades to the latest PK6 firmware for their G928T and has this problem my thread is available with a solution.

Magisk half root?

It seems like I don't have complete root with magisk? App says root access and it passes safetynet. TiBu fully works. System update detects modification.. Is this because I used twrp to flash magisk12 and the recovery stuck? Will twrp allow you to install while selecting "keep read only"? At what point does Samsung block ota updates if I'm not flashing supersu into system?
I figured since I have twrp now I'd try hotspot initdv6 and it didn't work. I'm confused here! Anyone have magisk fully working and not tripping anything like ota's? Or snap chat.

lootbooper said:
It seems like I don't have complete root with magisk? App says root access and it passes safetynet. TiBu fully works. System update detects modification.. Is this because I used twrp to flash magisk12 and the recovery stuck? Will twrp allow you to install while selecting "keep read only"? At what point does Samsung block ota updates if I'm not flashing supersu into system?
I figured since I have twrp now I'd try hotspot initdv6 and it didn't work. I'm confused here! Anyone have magisk fully working and not tripping anything like ota's? Or snap chat.
Click to expand...
Click to collapse
If you put a custom recovery on, like TWRP which you use to flash Magisk, you lose the ability to update via OTA.

So am I able to flash stock recovery or too late? Guess I'm just trying to achieve the impossible lol. I understood magisk can maintain true stock ROM, but as you stated twrp botches it. What gets me now is hotspot patch won't work but it flashes fine.

From my understanding, you cant have root without a custom recovery and boot image (and with magisk, you wouldnt want to, since you often need to reflash the magiskv12.zip
(the stock recovery is what actually processes ota updates if im not mistaken)
If you want to go back to stock, just odin the latest tar file. If you do it dirty (without wiping data/system/cache/etc first) it usually turns out alright and you get to keep all your apps and stuff, but youll lose root and custom recovery.

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!