My rooted moto G7 is still on stock android 9, security level 1 October 2019, build PPOS29.114-134-4. My wife has the identical Moto G7 phone, but unrooted, and I know she has received several OTA system updates since then.
My rooted phone is so far behind in updates because every non-OTA update method I've read about results in losing root. I know that regaining root is a simple thing to the experts but every time *I* attempt to root this (or any other phone) I end up getting into trouble. I don't even remember how rooting was originally done on this phone and obviously I am not doing things correctly.
Could a kind expert please give me step by step instructions suitable for a newbie on how to update the system on this rooted phone and then simply regain root?
My phone has twrp installed and I do have recent nandroid backups. If my memory is correct, I originally used twrp to root this phone but my memory may or may not be correct.
Thank you.
(To explain, the only reason I root this phone is
1) to use Titanium Backup which I've used many times to restore apps
2) for easy nandroid backups in case I mess something up
3) to hopefully install a Google free rom one day. I used lineageos on another phone but understand it still has problems on this phone)
maybeme2 said:
My rooted phone is so far behind in updates because every non-OTA update method I've read about results in losing root.
Click to expand...
Click to collapse
EVERY update of your firmware requires a new installation of Magisk.
New firmware = new boot.img => Magisk will be deinstalled
Thank you
Actually I cannot get any updates unless I unrooted first. When I tell the phone to look for updates it does and tells me I'm up-to-date. Which I'm obviously not.
So it seems something is preventing update. I assumed it's because I'm rooted. What do I need to do to receive ota updates and after updates how do I regain root?
maybeme2 said:
Thank you
Actually I cannot get any updates unless I unrooted first. When I tell the phone to look for updates it does and tells me I'm up-to-date. Which I'm obviously not.
So it seems something is preventing update. I assumed it's because I'm rooted. What do I need to do to receive ota updates and after updates how do I regain root?
Click to expand...
Click to collapse
You have to manually flash the firmware via fastboot. There're a lot of tutorials here in this forum for that.
Do It manually
https://forum.xda-developers.com/moto-g7/how-to/manually-update-g7-using-fastboot-t3917381
Just pay attention to not erase user data and it won't wipe anything
maybeme2 said:
Thank you
Actually I cannot get any updates unless I unrooted first. When I tell the phone to look for updates it does and tells me I'm up-to-date. Which I'm obviously not.
So it seems something is preventing update. I assumed it's because I'm rooted. What do I need to do to receive ota updates and after updates how do I regain root?
Click to expand...
Click to collapse
Theres a magisk module called Safety Net something-another and if you install hat module, reboot, go back to magislk-settings and towards the mid to bottom check the box that says Hide Magisk to protect from various forms of detection
Then you can reboot again or just wait awhile and you should be able to update BUT, as stated above, you'll have to reinstall magisk every update.
Thanks. It is hard to know what to believe anymore. In my searches I also read that accepting ota updates on a rooted Moto G7 will brick the phone.
maybeme2 said:
Thanks. It is hard to know what to believe anymore. In my searches I also read that accepting ota updates on a rooted Moto G7 will brick the phone.
Click to expand...
Click to collapse
Because some people also tell a lot of nonsense!
An ota.zip is a block based update process. You MUST verify the partitions before doing any changes! Otherwise it could lead to a fully damaged device.
"Hide the manager..." Thanks a lot!!
@maybeme2 flash the correct firmware to update your device.
WoKoschekk said:
Because some people also tell a lot of nonsense!
Click to expand...
Click to collapse
Very true. But .....it takes knowledge (which I am slowly acquiring) to tell the difference. And, if the person asking already had enough 'knowledge' to know it is nonsense, they would not need to search for information. A classic Catch-22 dilemma for a newbie. That's why searching for help is so dangerous.
QUOTE=WoKoschekk;82901585]An ota.zip is a block based update process. You MUST verify the partitions before doing any changes! Otherwise it could lead to a fully damaged device.[/QUOTE]
What do you mean by "a block based update process". I think I know, but it is dangerous to guess. If you have the time, could you explain?
Also, what do you mean by "verify the partitions before doing any changes!"? Verify for what? And after verifying the partitions, do what with that knowledge?
These are summary statements. Similar to "you must do the correct thing". It does not tell me what the correct thing is.
What people asking for help need is
1. Click on. ....
2. Copy. .. to. ... because. ..
etc.
3. Be sure to. ....
HTA123's answer was helpful that way.
"There are plenty of tutorials" is not helpful because some of these tutorials are incorrect and will brick your phone.
QUOTE=WoKoschekk;82901585]"Hide the manager..." Thanks a lot!!.[/QUOTE]
What do you mean by ""Hide the manager..."?
maybeme2 said:
What do you mean by "a block based update process". I think I know, but it is dangerous to guess. If you have the time, could you explain?
Also, what do you mean by "verify the partitions before doing any changes!"? Verify for what?
Click to expand...
Click to collapse
Android uses a ext4 filesystem that allocates storage space in units of "blocks". Your system partition is read only and Android will not change anything on it. So Motorola's developers know the block address of each file. Instead of replacing a updated file they replace an updated block.
But on a modified partition the block addresses may have changed for each file. While an update replaces a block with the correct address, this block could stored incorrect files/data.
block based OTA
To avoid such problems an OTA verifies your whole system. The easiest way to verify a partition is to build hashes/checksums.
Hide Magisk Manager
This option is helpful to hide root for some apps that check your device for root. But it's not for a device update/OTA.
WoKoschekk, that is very informative. Thank you so much! I've learned a lot and it explains a lot of things about ota's, and other things.
Excellent. I will copy and keep in my notes.
Thank you again.
maybeme2 said:
WoKoschekk, that is very informative. Thank you so much! I've learned a lot and it explains a lot of things about ota's, and other things.
Excellent. I will copy and keep in my notes.
Thank you again.
Click to expand...
Click to collapse
Attached you find a system log of a failed OTA update process grabbed from my Moto G6 plus. I know there are more interesting things in life than that. But it shows you what I have explained in my post before.
After trying to verify the partitions it fails due to a mismatched hash and the update process exits with a error (time: 04:34:25, somewhere in the middle of the log).
Related
I bought a used XT925 today. While the previous owner did go to some trouble to clean it, it still has a bunch of apps and some settings that I really don't want. Also, as a privacy paranoiac, I'm worried that there may be something malicious (however slight the possibility).
The device is rooted and running JB 4.1.2. I would love to factory reset it but having read a few reports of people losing root or worse (here, here, here and here, to list just a few) that plan seems ill-advised.
I've been toying with trying to script some kind of fs compare against a fs from a rom, but I'm not sure if this is even feasible. So far the only other thing I can think of to do is uninstall all the apps and manually sift through and delete all the other junk in the filesystem.
Does anyone have any suggestions on returning my device to the most "virgin" state possible while retaining root?
triplexdoubledadevelopers said:
I bought a used XT925 today. While the previous owner did go to some trouble to clean it, it still has a bunch of apps and some settings that I really don't want. Also, as a privacy paranoiac, I'm worried that there may be something malicious (however slight the possibility).
The device is rooted and running JB 4.1.2. I would love to factory reset it but having read a few reports of people losing root or worse (here, here, here and here, to list just a few) that plan seems ill-advised.
I've been toying with trying to script some kind of fs compare against a fs from a rom, but I'm not sure if this is even feasible. So far the only other thing I can think of to do is uninstall all the apps and manually sift through and delete all the other junk in the filesystem.
Does anyone have any suggestions on returning my device to the most "virgin" state possible while retaining root?
Click to expand...
Click to collapse
Simplest way is to use RSD Lite to send your device back to stock 4.1.2 -- then you can use the recently posted root method to gain root back. It should take < 15 minutes to do, most of that spent flashing with RSDLite. It'll actually take longer to download all the ADB drivers, Moto drivers, etc -- if you don't have them already.
triplexdoubledadevelopers said:
I bought a used XT925 today. While the previous owner did go to some trouble to clean it, it still has a bunch of apps and some settings that I really don't want. Also, as a privacy paranoiac, I'm worried that there may be something malicious (however slight the possibility).
The device is rooted and running JB 4.1.2. I would love to factory reset it but having read a few reports of people losing root or worse (here, here, here and here, to list just a few) that plan seems ill-advised.
I've been toying with trying to script some kind of fs compare against a fs from a rom, but I'm not sure if this is even feasible. So far the only other thing I can think of to do is uninstall all the apps and manually sift through and delete all the other junk in the filesystem.
Does anyone have any suggestions on returning my device to the most "virgin" state possible while retaining root?
Click to expand...
Click to collapse
Whats up,
Cpudan80 is right, your best bet is to flash stock 4.1.2, and to reroot. And it does take about 15 minutes if you don't already have drivers and stuff, but I can help you out, by linking you to my utility, which essentially does the heavy lifting of finding all of the programs and stuff, and puts it together into one convenient package.
Find it here: http://forum.xda-developers.com/showthread.php?t=2241788
Cpudan80 said:
Simplest way is to use RSD Lite to send your device back to stock 4.1.2 -- then you can use the recently posted root method to gain root back.
Click to expand...
Click to collapse
Mr.Parkinson said:
Cpudan80 is right, your best bet is to flash stock 4.1.2, and to reroot.
Click to expand...
Click to collapse
Thanks for the replies! Would you link me to that root method, Cpudan80? All of the root methods I've been able to find say that you must flash 4.0 or CWM first in order to root, then protect root and upgrade to JB again. Is there a new better way which doesn't require downgrading?
triplexdoubledadevelopers said:
Thanks for the replies! Would you link me to that root method, Cpudan80? All of the root methods I've been able to find say that you must flash 4.0 or CWM first in order to root, then protect root and upgrade to JB again. Is there a new better way which doesn't require downgrading?
Click to expand...
Click to collapse
There's a thread on here somewhere -- but here's the thread I followed (after using RSDLite to go back to clean 4.1.2). No hard steps at all, just run a bat file - press enter and viola - you're rooted.
http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit/
Cpudan80 said:
There's a thread on here somewhere -- but here's the thread I followed (after using RSDLite to go back to clean 4.1.2). No hard steps at all, just run a bat file - press enter and viola - you're rooted.
Click to expand...
Click to collapse
Amazing, thanks! I had seen that exploit at one point when I was considering getting an earlier RAZR version and was looking into how easy it was to root it. I thought that exploit didn't work with the XT925 since there was no link to it in the forum (and searches only revealed many tales of failed root attempts and downgrades). Thanks again!
Q: I have don't have the AT&T specific LG G2 (D800)...
A: Don't finish your question... this FAQ doesn't apply to you.
Q: Why won't my phone update?
A: Because your question doesn't include enough information.
Q: My phone currently is currently rooted (and may have been modified); can I update to kitkat (and retain root)?
A: Maybe, but maybe not. You are probably better off doing the procedure (found in another thread) to restore your phone to stock, using ioroot22 (or a more recent version)(found in yet another thread) to root it, but NOT make any other modifications. Then allow the 10o and 10q updates to apply. Then kitkat should apply and leave root intact.
Q: I read the previous answer - where are those other threads?
A: They can be found by searching, looking for stickies, etc. Hint: "ioroot22" is a good search term if looking for "ioroot22." To find a thread about restoring a phone to stock, "restore to stock" might be a great search term.
Q: Why are you calling it "firmware" and not "ROM"?
A: "ROM" stands for "read only memory." The fact that it can be updated (and easily modified) means that it's not ROM.
Q: How to I know which version of the firmware I have?
A: Settings->"About Phone"->"Software Information"->"Software version"
Q: My phone currently has a stock D80010d image. How can I update?
A: You need D80010q to update. First update to 10o, then see the next question.
Q: My phone currently has a stock D80010o image. How can I update?
A: You need to allow it to update to 10q first. kitkat doesn't seem to apply to anything other than 10q. Then see the next question.
Q: I currently have a stock D80010{d|o|q} image, but "update software" tells me there are no other updates. What do I do?
A: Annoy AT&T. If the first tech tells you that they can't push an update, thank them, hang up, and call back.
Q: "update software" tells me to try again in xx hours. I'm impatient. What do I do?
A: Change your time/date settings to manual, and step into the future (adjust the date.)
Q: What about "xposed framework"?
A: It doesn't work (yet.) rovo89 has fixes pending for the next release.
Q: I'm not currently using an AT&T tower (roaming) or I'm using a non-AT&T SIM. How do I update?
A: You don't. People have tried, but no one has been successful when roaming or using a non-AT&T SIM.
Q: How can I install the update without having AT&T's network push it to me?
A: No one yet knows. We have the file that is being pushed, but no one has figured out how to get the phone to install it. (You can flash the entire firmware, however...)
Q: Is there any way to jump directly to kitkat without messing with updates?
A: Yes, but it comes with two warnings... First, it will basically "factory reset" your phone (meaning you'll lose all data, settings, etc.) Second, there's no known way to root the phone after following this procedure. So, if you're okay with what is basically a "factory reset" on your phone and with losing root, jump to the following thread complements of @bigfau: http://forum.xda-developers.com/showthread.php?t=2662445
UPDATE (2014-Feb-28): Thanks to @AndroidUser00110001, if you have an older firmware with a working custom recovery, you can download and install something that allows you to jump directly to "stock" kitkat _and_ optionally root the device at the same time. HOWEVER, this will still erase any custom recovery on your phone, erase any modifications you've made to your /system partition, etc. For more information, instructions, downloads, and questions, please follow this link: http://forum.xda-developers.com/showthread.php?t=2665391
Q: So, I have the new kitkat firmware, but I decided that I want to root my phone after all. What do I do?
A: You'll have to use one of the "restore to stock" procedures to get your phone back to 4.2.2 (D80010d or D80010o), root that, and then have the '10q' and '20c' updates pushed to your phone from AT&T.
Q: Does this firmware have carrier IQ?
A: Yes.
Q: Can carrier IQ be removed?
A: No, but...
Q: Can carrier IQ be disabled?
A: Yes: using "disable service" from the play store (https://play.google.com/store/apps/details?id=cn.wq.disableservice), swipe over the "system apps", select "android system" and deselect the checkbox for "IQService"
Q: How do I install a custom recovery (CWM/TWRP) or kernel with this firmware?
A: At the present time, you can't. LG updated the bootloader with this firmware to fix the "loki" exploit which was being used to install custom recoveries and kernels. Be assured, however, that there are multiple people trying to find a way around the security mechanisms anyway. Note that it's still possible to flash an older bootloader along with and older firmware. See the threads on "how to restore to stock."
Q: Why isn't there any custom firmware available based on this official release?
A: I'm sure people are working on it already. However, how would you like to install it? (See above question...) Without a custom recovery, it'd be very difficult to package anything so a typical user could install it. Not many people would be willing to walk a typical user through the process of remounting the system partition and overwriting files. (Anyone who would be fluent with doing that has probably already started customizing their own device.)
Q: I want an RD, RC, or Moderator to walk me through everything. What do I do?
A: Keep wanting.
Q: Why is the sky blue?
A: It's not. It only appears blue to you. It's actually red. However, because you've been told your entire life that it's blue, it's altered your perception of which color is which.
Q: Is this really a FAQ?
A: No. It's just some lines I put together while doing my real (paying) job. Every time my boss looks over my shoulder, I have to make up some lame excuse on why I'm "working" on my hobby instead of what I'm being paid for.
Take care
Gary
Q: Why is the sky blue?
A: It's not. It only appears blue to you. It's actually red. However, because you've been told your entire life that it's blue, it's altered your perception of which color is which.
You... You... MONSTER! you ruined my life.
Do you think the D80010q .tot file would be of any use?
bigfau said:
Do you think the D80010q .tot file would be of any use?
Click to expand...
Click to collapse
I doubt it can hurt, though people would be better off at this point flashing 10o, rooting, and then getting the updates pushed (so they retain root.)
wher I can find the file of kk ver?
garyd9 said:
I doubt it can hurt, though people would be better off at this point flashing 10o, rooting, and then getting the updates pushed (so they retain root.)
Click to expand...
Click to collapse
@SuperSport explained it to me. If I get the D80010q .tot and flash it with Lg Tools, root, and then check for the update to D80020c. Hopefully root will still stick after Kit-Kat
updated with answers referring .TOT thread from @bigfau along with warnings. Thank you, bigfau, for getting that .tot file and posting it.
Is anyone currently working on recovery/bootloader bypass method, or are we waiting on more variants to be updated to KK. And thanks for the .TOT big
Sent from my LG-D800 using XDA Premium 4 mobile app
muppetmaster916 said:
Is anyone currently working on recovery/bootloader bypass method
Click to expand...
Click to collapse
Added question/answer for custom recovery/kernel.
garyd9 said:
Added question/answer for custom recovery/kernel.
Click to expand...
Click to collapse
Thanks, appreciated.
Sent from my LG-D800 using XDA Premium 4 mobile app
best FAQ ever!
Thanks for the FAQ Gary! I am running stock d80010d, every time I check for software updates I get this message "Your Phone is not registered yet." I have called both AT&T and LG twice about this, and no one seems to know whats going on. Any ideas?
suruat said:
Thanks for the FAQ Gary! I am running stock d80010d, every time I check for software updates I get this message "Your Phone is not registered yet." I have called both AT&T and LG twice about this, and no one seems to know whats going on. Any ideas?
Click to expand...
Click to collapse
This thread might help you: http://forum.xda-developers.com/showthread.php?t=2661999
garyd9 said:
This thread might help you: http://forum.xda-developers.com/showthread.php?t=2661999
Click to expand...
Click to collapse
This is the answer to my question! Much Thanks brother!
Root didn't seem to survive update
I was on D80010o and rooted.
I chatted with AT&T rep and updated to D80010q and then D80020c (Kit Kat).
I tried updating my su binary and it fails.
Disable Service says I'm not root.
Has this happened to anyone? Is there a way to update SU?
Thanks
vween said:
I was on D80010o and rooted.
I chatted with AT&T rep and updated to D80010q and then D80020c (Kit Kat).
I tried updating my su binary and it fails.
Disable Service says I'm not root.
Click to expand...
Click to collapse
Your phone is no longer rooted. There's no way currently to root it. You can restore to D80010o, root the device, don't do anything else, and get AT&T to push the updates again.
garyd9 said:
Your phone is no longer rooted. There's no way currently to root it. You can restore to D80010o, root the device, don't do anything else, and get AT&T to push the updates again.
Click to expand...
Click to collapse
Hmm... that's not good news.
Oh, well. I think I may just wait until a root method is found for 4.4.2.
Thanks!
So there's currently no actual way to disable carrier IQ without root right?
Knight613 said:
So there's currently no actual way to disable carrier IQ without root right?
Click to expand...
Click to collapse
Apparently not. AT&T got wise to the previous little trick and buried that sucker good.
As longs as it isn't a buggy battery leech like the last version, I can live with it.
Has anyone outside the US without an AT&T SIM card been able to upgrade to AT&T's stock 4.4.2?
Thanks
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.
Greetings,
I've been lurking around XDA trying to find good EMUI 5.0 root support.
I've been proposed by the HiCare app to prematurely update to EMUI 5.0 w/ Nougat, and I do say prematurely, since where I'm living (France), no one ever heard of such witchery
However, i seem to understand that TWRP and SuperSU fall a bit on the short side, notably with the decryption algorithms not being implemented yet, courtesy of Huawei making things as difficult as they can. Here it seems that very limited support for the H8's special Kernel is available given Huawei's pain-in-the-ass attitude.
The million dollar question i'm asking the forums today/tonight is "Can the device encryption be disabled, permanently ?". I do understand and acknowledge the potential risks of such procedure, as if my phone gets stolen, indeed my data is at risk, so is my phone with rooting and such nonsense (talking from experience, since i've bricked the poor thing on day one...).
I would like to thank everyone on this forum beforehand, as without this great community, my phone would still be gathering dust waiting some unbrick miracle to happen, shoutout to Team-MT for their Multi-Tool that saved my day
Thank you all.
I'd sure like to know this too. Seems decryption is the biggest hurdle to get around when it comes to anything twrp and su.
If you only need root access I can say that you can have root access and TWRP with Nougat. Not everything is working (access to data partition is tricky) but you can have root.
ViCioPT said:
If you only need root access I can say that you can have root access and TWRP with Nougat. Not everything is working (access to data partition is tricky) but you can have root.
Click to expand...
Click to collapse
Then my question should be "How can i mount /system and /data for flashing ?", since these are the real nightmares.
Do you have a quick explanation or tutorial to provide me please ?
Thank you
ViCioPT said:
If you only need root access I can say that you can have root access and TWRP with Nougat. Not everything is working (access to data partition is tricky) but you can have root.
Click to expand...
Click to collapse
I'm not sure if I need access to the data partition. All I'd like is AdAway which I believe modifies the hosts file in the system partition and Viper4Android which again I believe is in the system partition. What method did you use to do this? Just unlock the bootloader, install which version of TWRP? I see there's a 3.0.2 but there'e the present encryption issue and which version of supersu did you use?
Also, I can find versions of B360 full firmware laying around, but have not seen successful reflashing of it to go back to stock if there's any issues.
DJ Daemonix said:
Greetings,
The million dollar question i'm asking..
Click to expand...
Click to collapse
You simply format the data partition in TWRP and encryption is gone. I think you (don't remember) have to flash the EU region specific Nougat update .ZIP afterwards. Yes, I have first hand experience.
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.