Database Info

Troubles rooting after stock update to 4.2

I got my TF700 around April of this year. I rooted it, but left it on the stock 4.1 android it came with. A couple weeks ago, I let it go through with the stock 4.2 upgrade. Mostly fine, but I kept finding things that bugged me. One of which was that my root seemed to only be partly there. I had installed OTA RootKeeper, and it said that it had restored root after the update. What I'm finding though, is that only apps which had root before still do. Anything new gets told there is no root.
So after all that, I decided yesterday to flash to a custom ROM. Since I thought I had root, I installed GooManager to try to put TWRP on for the flashing. It never gave me any errors, but repeatedly just didn't do anything, and attempting to reboot in recovery mode always failed (once I got the "dead android" with the exclamation point, but usually it would just do a normal reboot). That lead me to figure out the no-root problem, so I decided to reinstall root. I tried with the Scott Tool and with Motochopper, but both failed. In the process of trying to fix those issues, I went ahead and did a factory wipe, but still couldn't get them to work.
So that's where I'm stuck. I have a "factory fresh" install of 4.2.1 that is apparently still locked and unrooted. I want to put root back on at a minimum, but would really like to put on a custom ROM. Nothing I have found here or elsewhere has suggested anything that has worked for me. One site suggested that I needed to use the Asus unlocking tool, however I can't find it for download anywhere (all sites point to the Asus site, but it's not providing the download link anymore). Can someone help me get this working?

Get the unlock tool from here (choose "Android" as OS):
http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+Infinity+TF700T&p=28&s=1
Unlock your device (and void your warranty), then use the fastboot method for installing TWRP, as described on their web page.

_that said:
Get the unlock tool from here (choose "Android" as OS):
...
Unlock your device (and void your warranty), then use the fastboot method for installing TWRP, as described on their web page.
Click to expand...
Click to collapse
Thanks for the link. All the ones I found would not display anything in the OS selector, so nothing was downloadable. I'm working on that step now. Do you have a link to the fastboot method? Other than seeing the term in a few posts, I have no idea what that is or where I would find the directions you mention.

techturtle said:
Thanks for the link. All the ones I found would not display anything in the OS selector, so nothing was downloadable. I'm working on that step now. Do you have a link to the fastboot method? Other than seeing the term in a few posts, I have no idea what that is or where I would find the directions you mention.
Click to expand...
Click to collapse
There's a nice tutorial here: http://forum.xda-developers.com/showthread.php?t=2277112
You can also use Scott's tool: http://forum.xda-developers.com/showthread.php?t=1938129
Just make sure you downlaod the latest TWRP version which is 2.6.3.1
You may find post # 9 from this thread interesting: http://forum.xda-developers.com/showthread.php?t=2429872
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

How to Update to 7.1.1 on a Rooted, Unlocked Bootloader, Google Play Pixel?

I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.

spook2022 said:
I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.

quangtran1 said:
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.
Click to expand...
Click to collapse
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.

lightmastertech said:
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.
Click to expand...
Click to collapse
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.

quangtran1 said:
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.
Click to expand...
Click to collapse
If it rooted, and has modified system, doesn't the OTA update method fail?
And I actually use the Raspberry Pi for fastboot. Easier than trying to get my Chromebook's chroot to talk to talk to my phone's bootloader.

Hi
Whats about Flashfire? Can i download the Factory Image, deselect Boot and Recovery in Flashfire and flash it?
After this, can i flash the the SuperSU.zip with TWRP?

spook2022 said:
<snip>
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
https://www.google.com/search?q=root+on+unlocked+pixel+7.1.1&ie=utf-8&oe=utf-8
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?

bobby janow said:
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?
Click to expand...
Click to collapse
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.

spook2022 said:
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.
Click to expand...
Click to collapse
As far as I know you can not update without losing root.. You can however update without losing data and reroot just like you did the first time.

@spook2022 It's just so frustrating to see the same question over and over. It wasn't that condescending, but yes, it was disgruntled. I just like to search for these things myself because I learn a lot along the way. Might take me an hour or so for the answer but then I learned an hours worth of stuff. I do agree though that there should be a sticky like the Heisenberg thread in the n5x forum that gives step by step for everything. One thing I will say that perhaps a few people don't know is that the Pixel and the XL are basically the same regarding root, unlocking and updating. So if you don't find the answers here you might want to head over to that forum. There seems to be a dearth of information here.
Someone suggested that the forums be combined with separate sections for things specific to each device like battery life and display as well as Verizon vs Google brand differences. I originally thought not but I'm changing my mind. Nonetheless, take the frustration from whence it came. I'm sorry I insulted you, that was not my intention. If you found a link to your solution perhaps you can post it for others. There is bound to be a similar question within a day. (oh oh there I go again..)
edit: This is what I was talking about regarding the Pixel vs the XL forums. Anything by Chainfire regarding root is a must read if you are rooted and even if you are not as I am. http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156

Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.

Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
<snip>
Click to expand...
Click to collapse
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.

Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Click to expand...
Click to collapse
Thank you so much.

bobby janow said:
...I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.

bobby janow said:
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.

kyle4269 said:
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.
Click to expand...
Click to collapse
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
---------- Post added at 03:50 PM ---------- Previous post was at 03:22 PM ----------
lightmastertech said:
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.
Click to expand...
Click to collapse
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.

bobby janow said:
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
.
Click to expand...
Click to collapse
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.

bobby janow said:
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.
Click to expand...
Click to collapse
Luckily I'm with USAA and they are too slow with adopting new technology, just got chip debit cards 2 months ago, and they'd till don't have Android Pay, lol. If they did start using SafetyNet, I'd use the kernel patch in a heartbeat. It'll be a long time before Google fixes that since there's still a lot of devices that can't use verified boot, and Google doesn't want to become the new Apple, abandoning old device just to suit them.
Wife got the Verizon version of the Pixel as an early Xmas present from my parents, and I wouldn't let the Verizon sales person activate it for fear of getting 7.1.1 before I could unlock bootloader. Wouldn't let wife turn it on for a couple hours till I had the bootloader unlocked and had flashed Google's version of Android to keep Verizon from screwing with it. Viper4Android and all the awesome rooted featured are too good to give up. She'll be really happy when Xposed or custom ROMs start coming out for it cuz even the little features are great, like holding power button with screen off to turn on flashlight. (She's been stuck with locked phones for a while while I've had my Nexus 6P and is glad to finally get a rootable phone).

kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
Yep, that's about it. Personally I'd reboot right after the OTA flash then go back to bl and do the root process. Probably not needed though.
Sent from my Pixel using XDA-Developers mobile app

kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
How is that better or different than flashing the full image by using fastboot to flash bootloader and radio (if updated), then using
Code:
fastboot update <image>.zip
and leave off the -w to keep it from wiping.
Also, correct me if I'm wrong, but doesn't OTA updates fail if you've modified the system partition, like installing Viper4Android or other mods? I know that flashing the whole system image works no matter what which is why I use that method.

Urgent problem with ota update 5.0

HI was downloading the new update 5.0 but it stopped and now the tablet says me "your system is updated" but with the 6.0.1.I can't restart the download now,what i have to do???

Same thing happened to me. Don't know why yet.

Same here. Where are you from?

Nvidia might have pulled it to fix something wait patiently it will come.

I had a similar problem as well. I got the notification to download the update, and when I clicked on the "Download" button in the notification, it did nothing. When I went into my settings and opened the OTA updater, it kept telling me that "Your system is up to date," even after repeatedly pressing the "Check Now" button, selecting "Clear data," rebooting, and messing with the advanced settings. I hope they fix this soon, I was really excited about this update!

Exact same issue here.

If you haven't root/twrp etc:
Download from here:
https://forum.xda-developers.com/shield-tablet/general/5-0-update-nougat-incoming-t3553612/page2 (there are two version - k1 & standard).
Paste it to internal memory, boot into recovery and apply update from zip.

Just wait a little. That's what NVIDIA calls "staggered rollout".

Just wanted to update and say that I got my OTA this morning and will apply it later this afternoon. Guess, just as suggested earlier, they staggered them. It's strange though that they actually pulled it back, but then again it might have been an issue with it.

if you have "nougat launcher apk" just delete it.

Been a while since I rooted mine and I'd prefer not to lose root. Anyone know if there's going to be a pre-rooted version available that won't require going through the whole process again? Honestly I don't recall if it was difficult or not but I know for previous phones I've had there was a rooted version of the OTA that someone would post within a day or two of the release. Made the whole update process quicker and easier.
Also, for those who have updated, how is the performance compared to Marshmallow?

My 2 cents: if the root is confirmed to work, there is no "process" per se.
D/L the root zip to the tablet, boot into recovery, flash that zip and reboot into system.
Should be within 2-3 min the whole thing.

Wayno-san said:
Been a while since I rooted mine and I'd prefer not to lose root. Anyone know if there's going to be a pre-rooted version available that won't require going through the whole process again? Honestly I don't recall if it was difficult or not but I know for previous phones I've had there was a rooted version of the OTA that someone would post within a day or two of the release. Made the whole update process quicker and easier.
Also, for those who have updated, how is the performance compared to Marshmallow?
Click to expand...
Click to collapse
Performance feels good so far. Don't know if there will be a pre-rooted version, but it's fairly simple and fast to root since your bootloader is unlocked and you'll get to keep all your data. If you want custom recovery I had to use the TWRP app after root to flash the recovery. Couldn't get it to stick using fastboot. There's a good rooting guide here:
http://nvidiashieldzone.com/shield-...ndroid-7-nougat/root-shield-tablet-k1-nougat/

pucka said:
Performance feels good so far. Don't know if there will be a pre-rooted version, but it's fairly simple and fast to root since your bootloader is unlocked and you'll get to keep all your data. If you want custom recovery I had to use the TWRP app after root to flash the recovery. Couldn't get it to stick using fastboot. There's a good rooting guide here:
http://nvidiashieldzone.com/shield-...ndroid-7-nougat/root-shield-tablet-k1-nougat/
Click to expand...
Click to collapse
Thanks for the info and the guide link. If I'm rooted can I let the update to nougat proceed and then just follow the procedure in the link? Thought I read somewhere that I need to unroot it first.

Wayno-san said:
Thanks for the info and the guide link. If I'm rooted can I let the update to nougat proceed and then just follow the procedure in the link? Thought I read somewhere that I need to unroot it first.
Click to expand...
Click to collapse
Yes you can just apply the update and there's no need to flash stock first. If you want to flash TWRP I would recommend getting root first by sideloading (like in the guide) and then using the TWRP app to flash TWRP.
I'm now rooted again with TWRP as custom recovery.

[ROOT]Samsung Note 5 Verizon SM-N920V 6.0.1

Mod Edit

So this is BS right? I've been out of the phone rooting game for a bit.
Sent from my SM-N920V using Tapatalk

Mod Edit

MrMike2182 said:
Why are you trying to get people to do this when it's not FULL ROOT?! You basically took the same exact console root eng kernel that is listed here https://forum.xda-developers.com/verizon-galaxy-note5/general/root-n920v-t3538192 and just renamed it..
Do not do this it's simply console root and nothing else!!
Click to expand...
Click to collapse
Lol at the if you see SuperSU you're rooted. I mean, if the CF auto works cool, but I'm gonna wait to see how many people don't read first and try to flash this.

tylerlawhon said:
Lol at the if you see SuperSU you're rooted. I mean, if the CF auto works cool, but I'm gonna wait to see how many people don't read first and try to flash this.
Click to expand...
Click to collapse
LOL there isn't even a CF auto root for the N920V!! He seriously just took the same one we already have for console root and renamed it! They're even the same exact size, haha. Besides, where does he think the SuperSU app is coming from? It sure ain't from the file he has posted because that's just the console root kernel and that doesn't install/ flash SuperSU it only flashes the boot.img..

tylerlawhon said:
..
Click to expand...
Click to collapse
There's to many inexperienced people claiming root and cluttering the hell out the forums!! Even on the easy-firmware website he posted this same exact thing and when a user asked him a question he didn't even know the answer and told the user to flash and report back with his findings.. This thread is totally not needed at all!!

Stuck in the boot interface

tylerlawhon said:
Lol at the if you see SuperSU you're rooted. I mean, if the CF auto works cool, but I'm gonna wait to see how many people don't read first and try to flash this.
Click to expand...
Click to collapse
Well there goes 1 who didn't read first lol.

please remove this threade Please .
it's worng from inexperienced someone

I know this website, easy firm ware listed above, to be a scam site. I've seen a lot of different angles they've tried INCLUDING a download manager quote unquote that is supposed to help you finish downloading. But this is a trojan app. While I never fired it up I can tell you it doesn't look like something a windows user should execute on their system. I use linux.
(mods I promise I know this site is a scam site I've watched them work over the past couple months as I researched my studies)
Regards to root. If you are patched for dirtycow good luck getting root on this phone. (see below for dirtycow patch details) The AT&T / Verizon variants of the Note 5 are extremely well coded you can't get root on them without a powerful exploit. With dirtycow available the days are numbered for any phones not patched, of course not patching your phone in the meantime means you are very vulnerable to a nasty exploit.
So how long right? I dunno but it could be awhile.
Patch details:
Google says the fix is called CVE-2016-5195 patched 11-05-2016, however my security patch level is Nov 1st, 2016. The Samsung SVE-2016-7504 is stated to be included in November's patches and there are 14 patches in that set. AT&T N920AUCS4CPK1 has a note about 14 patches from Samsung, the exact number. (so I seem to be patched if I follow the logic even though Google responded on 11/05/2016 but I dunno how to confirm what's in this Nov 1 2016 security patch in the PK1 firmware.)

It doesn't really matter if they've patched it, you can still downgrade your firmware and security level - even on this variant. I used to go between Marshmallow and Lollipop, as it was required by the ps3 controller app.

Turbine1991 said:
It doesn't really matter if they've patched it, you can still downgrade your firmware and security level - even on this variant. I used to go between Marshmallow and Lollipop, as it was required by the ps3 controller app.
Click to expand...
Click to collapse
Which part are you saying you can downgrade? You can't take the Lollipop firmware and flash it if you're currently on the latest firmware update. It will just fall in odin.

That's just not true. The Verizon model can be flashed in Odin, I've done it a few times myself. Here's someone elses word: https://forum.xda-developers.com/verizon-galaxy-note5/general/downgrade-to-lollipop-5-1-1-verizon-t3368250
It's not impossible, you just need to use an official firmware and may need to downgrade the bootloader.

Turbine1991 said:
That's just not true. The Verizon model can be flashed in Odin, I've done it a few times myself. Here's someone elses word: https://forum.xda-developers.com/verizon-galaxy-note5/general/downgrade-to-lollipop-5-1-1-verizon-t3368250
It's not impossible, you just need to use an official firmware and may need to downgrade the bootloader.
Click to expand...
Click to collapse
Uh, Sir, the link you just posted.. *I* am the original poster of that and I'm telling you with official firmware you still CANNOT go from the latest firmware update of Marshmallow back to Lollipop! I even stated in my OP that it's not going to once you accept the BPI3 firmware update you're done and stuck on Marshmallow with no way to go back not even if you follow my original instructions it won't work!! The bootloader is no longer downgradeable thanks to Verizon!

Dirty cow or not is irrelevant. We can upgrade or downgrade and we're able to root this phone just like any other variant.
The only issue is the bootloader's signature checking.

so this is crap, thanks for the further investigation

There's a simply check for a value that they are calling a binary number. What is that? Certain versions will work together but past a certain point something changes. (most often the security storage binaries) .. So the bootloader checks to see if binary # >= current firmware binaries ... If you are on S3 binary and you attempt to flash S2 binaries the bootloader newly rejects this.
I can and have written a tool to over come this problem but there is one catch. system.img is too large for me to hack into place in this way. If I can't rewrite system.img then we are still stuck. ;*(
So what am I doing? I need root so I can just dd write system.img from /sdcard/ to the partition. that's it..
Stop listening to people who are not spending all their free time looking at the Note 5.. I already have too much access for the Note 5 to survive now.. It's going down, it is not the super secure device that will refuse to boot 'ever again' if you modify stuff that Samsung tried to claim.. that was lies and nonsense (don't hack BOTA0 or BOTA1 though)... I haven't tested changes to this partitions, all others have suffered a beating from me. (if you disable certain packages without disabling other packages it will refuse to boot, no wiping will help, reflash time)

droidvoider said:
There's a simply check for a value that they are calling a binary number. What is that? Certain versions will work together but past a certain point something changes. (most often the security storage binaries) .. So the bootloader checks to see if binary # >= current firmware binaries ... If you are on S3 binary and you attempt to flash S2 binaries the bootloader newly rejects this.
I can and have written a tool to over come this problem but there is one catch. system.img is too large for me to hack into place in this way. If I can't rewrite system.img then we are still stuck. ;*(
So what am I doing? I need root so I can just dd write system.img from /sdcard/ to the partition. that's it..
Stop listening to people who are not spending all their free time looking at the Note 5.. I already have too much access for the Note 5 to survive now.. It's going down, it is not the super secure device that will refuse to boot 'ever again' if you modify stuff that Samsung tried to claim.. that was lies and nonsense (don't hack BOTA0 or BOTA1 though)... I haven't tested changes to this partitions, all others have suffered a beating from me. (if you disable certain packages without disabling other packages it will refuse to boot, no wiping will help, reflash time)
Click to expand...
Click to collapse
I tried to tell everyone that this was straight up BS back when I was asking for help and no one wanted to risk it nor did they believe me.. Instead they chose to believe this instead of me..
http://www.idigitaltimes.com/samsung-galaxy-note-5-galaxy-s6-edge-specs-and-features-att-and-verizon-models-wont-468357

Would flashing the tar file in the OP give me the ability with ADB to delete, rename or change the bootsamsung.qmg and bootsamsungloop.qmg files? All I want to do is swap those out for another set. Would I then need to flash something else to bring it back to normal?

MrMike2182 said:
I tried to tell everyone that this was straight up BS back when I was asking for help and no one wanted to risk it nor did they believe me.. Instead they chose to believe this instead of me..
http://www.idigitaltimes.com/samsung-galaxy-note-5-galaxy-s6-edge-specs-and-features-att-and-verizon-models-wont-468357
Click to expand...
Click to collapse
You seem to have a good grasp on the situation and seem to talk sense, so I'll just ask a question. I'm only passing through because I needed some info, but got interested in the thread.
It seems you have the eng boot for the device, but not able to get system to mount rw? Strange because I have checked it and it is a bonafide eng boot.
Anyway I don't own this device, but I thought I'd just share some info that allowed others to get root on a few recent ATT devices with locked bootloaders on MM.
Using Kingroot on the said devices would not work, no matter how many times or which version was used. However flashing the eng boot from the combination firmware (so not even full eng boot as no root shell with adb) and then using Kingroot, Kingroot was able to successfully root these devices even though with some it took several tries. Kingroot was then used to convert to Supersu.
This may have been tried already, but I couldn't see it. Someone tried it with stock, but not using the eng binary.
The combination eng binary allows the device to boot in permissive mode with no dm-verity, but doesn't have a root shell or any write access with adb. The full eng boot you have should do the same obviously with the addition of adb root shell.
It's just for info and I'm not claiming it will work on Verizon devices, but it seems to be pretty successful on ATT and Tracfone devices.

Phone was rooted and not sure how to remove

A couple of months ago I bought a used Samsung Galaxy S 7 edge from a place called Aarons. A friend and I quickly realized that the phone had been rooted at one point, and I only recently believe I figured out what was used. The phone of course was wiped when I got it, but whatever was used was never removed. Normally I wouldn't care so much however it is preventing security updates. I'm not very good with this kind of stuff so I am NOT sure what to do to either remove it from my phone or get the updates I need.

if nothing helping you should considering flashing stock firmware as last option, i think this will work

If you want to unroot, I think some unroot.zip files that can found across the net might be helpful.
Also, if it is rooted with magisk, I don't think there is a reason to remove it.

First you have to figure out what app it was rooted with. It's probably Magisk or SuperSU. If it's one of them you can either unroot the phone through the parameters of the "root control" app or flash the unrooting zip which you can download it from the official magisk thread or the supersu website.

This is what I found concerning what was on the phone. I may not every be right about it. Which is why I wanted someone with more knowledge to help. As I said my main concern is my inability to do security updates. whatever it is, it's even preventing me from connecting my phone to my PC.
If you'll can determine the best course of action from the screenshot that would be great. Like I said, I know nothing about this kind of thing, so I have no idea where to start with flashing the firmware our weekday unroot.zip I should be looking for.
Edit: so apparently I'm prevented from posting the image because I have under 10 posts. I'll figure that out later, but I was using sd maid when I found this info. Under device it says hero2lte @ 6.0.1 (23). Under root status it says none for su binary, but that there is a built-in superuser app.