I have an unlocked Nexus 6 64gb from Ebay that I activated on Verizon. I rooted it, installed 5.1 and did the build.prop and settings.db changes and have tethering, etc (unlimited).
A few questions:
Will the OTA update show up on my phone since it is rooted and/or since it was not purchased from Verizon?
If it does show up and I let it update to 5.1.1, will I need to do the build.prop and settings.db changes again?
If it does not show up and I install from Google's image, do I need to do the build.prop and settings.db changes again?
I am sure these are basic questions... sorry... this was my first phone root and will be my first update to apply since doing that.
an update will show up whether you have root or not, BUT.. you can not take or apply an ota if any system files have been changed. and guess what rooting your device did, change system files.
simms22 said:
an update will show up whether you have root or not, BUT.. you can not take or apply an ota if any system files have been changed. and guess what rooting your device did, change system files.
Click to expand...
Click to collapse
Ok thanks. So that means I update with the Google Image if I want to. I think there is an option to do that without a wipe. Is that recommended / OK? If so, I wont have to change any files again, right?
hifiaudio2 said:
Ok thanks. So that means I update with the Google Image if I want to. I think there is an option to do that without a wipe. Is that recommended / OK? If so, I wont have to change any files again, right?
Click to expand...
Click to collapse
factory image, or any custom rom. and yes, you can update via factory image and do it a certain way to not lose data. you dont ever "have to" change any files. if you keep it stock, completely, you get an update ota, and you keep goung after that. if you root, tou have choices. i keep my choices simple. i root and use custom kernels btw. i also use custom roms. so, for me, updating is just flashing the latest custom rom(be it stock/rooted or real cutom rom).
simms22 said:
factory image, or any custom rom. and yes, you can update via factory image and do it a certain way to not lose data. you dont ever "have to" change any files. if you keep it stock, completely, you get an update ota, and you keep goung after that. if you root, tou have choices. i keep my choices simple. i root and use custom kernels btw. i also use custom roms. so, for me, updating is just flashing the latest custom rom(be it stock/rooted or real cutom rom).
Click to expand...
Click to collapse
Thanks again for the help. So my wife has the exact phone and same root with hotspot enabled as I do. I forgot to tell her to ignore the update, so when the OTA verizon update showed up this morning, she installed it. Her phone still says 5.1, so I assume it just tried to install but didnt work, but the Hotspot icon was removed (I just went into settings and selected it again, and it seemed to work still), but I dont know what error it might have given when she tried to install or what settings or files that I had changed, like build.prop, etc, might be changed back. Is it likely that the system trying to install the OTA update would have changed my modified settings?
Going forward, I plan to fire up Wug's rootkit and just flash the 5.1.1 image with no wipe. SO everything I did on both phones should already be ready to go when the flash finishes, right? No settings for me to change all over again?
Will have to redo the build.prop edits. Full image flash will replace the build.prop with new one.
prdog1 said:
Will have to redo the build.prop edits. Full image flash will replace the build.prop with new one.
Click to expand...
Click to collapse
Cool, all done, thanks.
Related
Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!
LordGrahf said:
Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!
Click to expand...
Click to collapse
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.
Thank you sir!
obsanity said:
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.
Click to expand...
Click to collapse
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
I'm kinda curious myself. I had no idea root killed OTA's. Maybe I wouldn't have done that if I knew that. I'm very new to the Nexus device. It's my 1st. I unlocked the bootloader and rooted already.
Sent from Mark's Nexus 6
crowbarman said:
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?
I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!
LordGrahf said:
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?
Click to expand...
Click to collapse
not sure what you mean by GI, but according to some others, after uninstalling root via SuperSU an OTA will still not install. This should not be the case unless the boot or recovery images are modified. Easily fixed by following the procedures above to fastboot the stock images on your phone.
kjnangre said:
I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!
Click to expand...
Click to collapse
Yes, it behaves exactly the same.
crowbarman said:
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.
obsanity said:
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.
Click to expand...
Click to collapse
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.
crowbarman said:
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.
Click to expand...
Click to collapse
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1
obsanity said:
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1
Click to expand...
Click to collapse
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.
obsanity said:
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.
Click to expand...
Click to collapse
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?
LordGrahf said:
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?
Click to expand...
Click to collapse
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.
obsanity said:
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.
Click to expand...
Click to collapse
There is an argument that publishing the method would allow Google to close it that much quicker, I suppose.
crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.
I assume that the encryption doesn't get in the way of being able to flash the images?
When I went from 5.0 to 5.0.1 on my old Nexus 5 all I did was flash the two new 5.0.1 images I extracted from the full factory image, then re-rooted. This is far cleaner than reverting back to the previous image then doing an OTA. I've not had to update my N6 yet so I don't know if my method will work still, but I hope it does.
Chainfire said:
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.
Click to expand...
Click to collapse
Thanks for the additional information.
I did spend a fair amount of time reading your documentation but failed to utilize a hex editor. I am not 'whining' about the lack of open source, rather, simply mildly surprised, but your website aptly describes the challenges with 5.0. Many are used to various root methods being available.
Your solution is fine with me.. I love your work.
Edit: I thought I'd add that the discussion has devolved from the OP, which was whether an OTA can be applied after uninstalling root. The answer was no, due to the unknowns about what still might be modified following the uninstall via SuperSU.
I've unlocked the bootloader and rooted the phone with the help of the Nexus Root Toolkit by WugFresh.
I now have it setup just how I want it and I don't want an OTA to kill root or change anything so something stops working (phone isn't for me, but I've set it up just right for someone with special needs).
I've read conflicting information on whether or not an OTA will actually install on a rooted phone or not. Some things say that it won't if you've changed anything at all while others say it might be possible.
Is there some system file I can rename or something to ensure the phone doesn't get a system update unless I do it manually?
LaTropa64 said:
I've unlocked the bootloader and rooted the phone with the help of the Nexus Root Toolkit by WugFresh.
I now have it setup just how I want it and I don't want an OTA to kill root or change anything so something stops working (phone isn't for me, but I've set it up just right for someone with special needs).
I've read conflicting information on whether or not an OTA will actually install on a rooted phone or not. Some things say that it won't if you've changed anything at all while others say it might be possible.
Is there some system file I can rename or something to ensure the phone doesn't get a system update unless I do it manually?
Click to expand...
Click to collapse
no matter how many times you will try to update via ota, you will not be able to. if any files change from stock, any at all, you wont be able to install an ota. especially with root.
LaTropa64 said:
I've unlocked the bootloader and rooted the phone with the help of the Nexus Root Toolkit by WugFresh.
I now have it setup just how I want it and I don't want an OTA to kill root or change anything so something stops working (phone isn't for me, but I've set it up just right for someone with special needs).
I've read conflicting information on whether or not an OTA will actually install on a rooted phone or not. Some things say that it won't if you've changed anything at all while others say it might be possible.
Is there some system file I can rename or something to ensure the phone doesn't get a system update unless I do it manually?
Click to expand...
Click to collapse
Root solved your problem ha ha
simms22 said:
no matter how many times you will try to update via ota, you will not be able to. if any files change from stock, any at all, you wont be able to install an ota. especially with root.
Click to expand...
Click to collapse
And sometimes, even if one is 100% stock, those pesky OTAs won't install.
cam30era said:
And sometimes, even if one is 100% stock, those pesky OTAs won't install.
Click to expand...
Click to collapse
right. any system file changes prevent install.
Awesome. Thanks.
Will it even attempt to install an update, and if so, does it only attempt once and then give up so you don't get stuck in a loop?
Install a custom recovery. Done. OTAs require the stock recovery in order to flash files.
LaTropa64 said:
Awesome. Thanks.
Will it even attempt to install an update, and if so, does it only attempt once and then give up so you don't get stuck in a loop?
Click to expand...
Click to collapse
itll only attemp if you let it(it needs your approval to update), otherwise itll only tell you that an update is available. if you let it, itll try, but fail. if you boot up, youll be where you were before.
Apparently I rooted it incorrectly because it was able to update. I just got a call and the phone had rebooted and went through optimizing X of X apps and now many of the tasker profiles I had set are no longer working.
It wouldn't have optimized a bunch of apps if it hadn't updated the OS, or no?
LaTropa64 said:
Apparently I rooted it incorrectly because it was able to update. I just got a call and the phone had rebooted and went through optimizing X of X apps and now many of the tasker profiles I had set are no longer working.
It wouldn't have optimized a bunch of apps if it hadn't updated the OS, or no?
Click to expand...
Click to collapse
you can always look at your android version in aboy phone, to see if it updated or not.
LaTropa64 said:
Apparently I rooted it incorrectly because it was able to update. I just got a call and the phone had rebooted and went through optimizing X of X apps and now many of the tasker profiles I had set are no longer working.
It wouldn't have optimized a bunch of apps if it hadn't updated the OS, or no?
Click to expand...
Click to collapse
You'll find update or not optimizing apps happens a lot especially if you clear cache etc...
Your fine otas can't install with root
Just flash twrp it will cone in handy incase you brick it one day you'll have twrp to fastboot fix or sideload a rom to recover from.
ONE NOTE: Never ever ever relock your bootloader with the toolkit you'll be screwed. Always leave bootlaoder unlocked. I just had to rma manufacturer phone replacement I relock mine with toolkit and couldn't flash stock firmware or oem unlock again.
Sent from my LGMS769 using XDA Free mobile app
simms22 said:
you can always look at your android version in aboy phone, to see if it updated or not.
Click to expand...
Click to collapse
I'll take a look the next time I get over there. It's not my phone, I just set it up for someone with accessibility issues and wanted it to stay the same as the day I set it up but apparently it's not done that.
Usually when a new Android OS version is released, I'll just start over from scratch by manually flashing the seven image files using fastboot. I then install the unencrypt kernel/boot image and also root.
Now that these security updates are coming out every month, is there an easier way in my specific situation to install the update only without having to start from scratch every time like above?
Flash the system image only (if radio is different, flash that too). That won't overwrite your user data/apps
Edit: When flashing the system.img, flash the cache.img as well (to be safe)
Thanks. That is pretty simple. I wish I asked this a long time ago so I could avoided a lot of resetting EVERYTHING up all the time. 2 more clarifications if you don't mind...
1) Would this also work for point releases, like say if a 5.1.2 comes out, or would it be better to reflash everything in that case?
2) No other steps like clear cache or anything? Just flash those 2, reboot, and then I should be good to go?
Toaplan said:
Thanks. That is pretty simple. I wish I asked this a long time ago so I could avoided a lot of resetting EVERYTHING up all the time. 2 more clarifications if you don't mind...
1) Would this also work for point releases, like say if a 5.1.2 comes out, or would it be better to reflash everything in that case?
2) No other steps like clear cache or anything? Just flash those 2, reboot, and then I should be good to go?
Click to expand...
Click to collapse
It should work just fine for point releases. For major releases (like when Android M is released), I will probably flash everything, and wipe everything (including userdata), and start from scratch ! lol!
In theory, it should work find even for major releases, but I'd rather start with a clean slate - especially with the new permissions manager that is being added in this release. I'd rather not take any old incompatible apps thru' - but that's just me
Clearing cache is usually not needed. I've heard of instances where some users get stuck on the Google boot logo for some reason when booting for the first time. If that happens, clearing cache seems to help.
To be safe, it may be a good idea to flash the cache.img too. It takes a few seconds. Better safe than sorry. I'll update my earlier post.
jj14 said:
...
Click to expand...
Click to collapse
Huge thanks. This should make things a lot easier for me.
Is this the system update that just got pushed to my phone? It looks like a small update, like 26MB?
Mine tried to install and failed. My phone is stock, latest official version, never rooted, but the bootloader is unlocked and it is running the no force encrypt kernel, which I believe is probably what is causing the issue?
Only way is to restore completely to stock, take the OTA and then install the no decrypt?
I got the OTA today to upgrade to M from L- (on verizon) where can I Find that system image to flash- I tried sideloading the OTA and it didn't take.
caecusscius said:
I got the OTA today to upgrade to M from L- (on verizon) where can I Find that system image to flash- I tried sideloading the OTA and it didn't take.
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
SquireSCA said:
Is this the system update that just got pushed to my phone? It looks like a small update, like 26MB?
Mine tried to install and failed. My phone is stock, latest official version, never rooted, but the bootloader is unlocked and it is running the no force encrypt kernel, which I believe is probably what is causing the issue?
Only way is to restore completely to stock, take the OTA and then install the no decrypt?
Click to expand...
Click to collapse
I believe it's actually both of these things causing the OTA not to take. If anything, anything is changed from stock...no OTA. Bootloader unlocked, kernel, root, even just changing the build.prop (but you need root for that) would cause it to fail. I believe it checks every file and if anything in /system has changed, no OTA.
I've never messed around with the encryption pieces, but I'm wondering if you only flash the system.img (you'd need to re-root) if that would suffice or not as far as the update. You'd be flashing the entire system file instead of only the delta the OTA provides, but it's probably worth looking into.
Hmmm... Well, it takes 15 minutes to just wipe the phone and flash the new ROM with the toolkit, install my apps, copy my files over and set the phone up, so it isn't a big deal, I just want to make sure that I have the right version before I do that...
(LMY48M) That's the one that I want for the VZW N6, right?
I just use helium to backup my apps and everything. Even if I need to wipe it is a pretty easy restore process. I highly recommend helium backup.
hayzooos said:
I believe it's actually both of these things causing the OTA not to take. If anything, anything is changed from stock...no OTA. Bootloader unlocked, kernel, root, even just changing the build.prop (but you need root for that) would cause it to fail. I believe it checks every file and if anything in /system has changed, no OTA.
I've never messed around with the encryption pieces, but I'm wondering if you only flash the system.img (you'd need to re-root) if that would suffice or not as far as the update. You'd be flashing the entire system file instead of only the delta the OTA provides, but it's probably worth looking into.
Click to expand...
Click to collapse
Unlocked bootloader doesn't affect it, the customised kernel does though . But yes, you could just flash the system.img
I have a Droid Turbo that is currently on version 5.1 (23.21.44) and I just recently unfroze the system update notifications for my phone because of the news of MM. I am currently rooted and have an unlocked bootloader but I don't have TWRP installed and would rather not install it for now if I don't have to.
The system update that it is trying to push to my phone isn't MM, instead it is version 23.21.49.en.US. Is it safe to just take this update while being rooted and with an unlocked bootloader? I'm also not sure how many updates I'll have to make my way through before reaching the MM update, but if there are other updates, should it also be safe to go ahead with those as well? I know I could install TWRP and flash the MM ROM that way but I would prefer to do the updates officially if it is not risking a bricked phone.
Thanks for any advice.
EDIT: I forgot to finish the title of the thread...
AirJordanTS said:
I have a Droid Turbo that is currently on version 5.1 (23.21.44) and I just recently unfroze the system update notifications for my phone because of the news of MM. I am currently rooted and have an unlocked bootloader but I don't have TWRP installed and would rather not install it for now if I don't have to.
The system update that it is trying to push to my phone isn't MM, instead it is version 23.21.49.en.US. Is it safe to just take this update while being rooted and with an unlocked bootloader? I'm also not sure how many updates I'll have to make my way through before reaching the MM update, but if there are other updates, should it also be safe to go ahead with those as well? I know I could install TWRP and flash the MM ROM that way but I would prefer to do the updates officially if it is not risking a bricked phone.
Thanks for any advice.
EDIT: I forgot to finish the title of the thread...
Click to expand...
Click to collapse
It's safe, but it will be unsuccessful until you unroot your phone and undo any other system modifications that you've done (xposed, for example). There's a huge part of the update script that checks every single file in your system partition to make sure nothing has been modified.
Ok great, thanks.
The only other modification I can think that I've made is enabling mobile Hotspot through editing a setting somewhere. Do you know if that would be affected or would need changed back?
AirJordanTS said:
Ok great, thanks.
The only other modification I can think that I've made is enabling mobile Hotspot through editing a setting somewhere. Do you know if that would be affected or would need changed back?
Click to expand...
Click to collapse
You did that by modifying /system/build.prop. That change might be okay, but I would change it back if I were you just to be safe. The change is going to be overwritten anyway once the OTA is done.
AirJordanTS said:
Ok great, thanks.
The only other modification I can think that I've made is enabling mobile Hotspot through editing a setting somewhere. Do you know if that would be affected or would need changed back?
Click to expand...
Click to collapse
It's possible it may miss overlooking that. The worst that could happen was the update just doesn't take. It fails and nothing is changed. There is a pure MM official version that you can Flash in TWRP. It will update everything, radios and all, but will not relock the bootloader. I recommend you download Titanium Backup and backup all of your apps and their data to be restored after the update. A factory reset is recommended after the update. Also, don't forget to back up all of your photos, documents, music, etc. 24.81.5 is MM. Your update was a prep for MM.
Thanks for the advice guys.
I didn't realize it but I had TWRP installed so I decided to flash a stock ROM and proceed with the OTA updates from there. The problem currently is that I'm being locked out of my phone because of the Google "verify your account" page. I reset my account password on that page and now I'm not able to log in.
Can a rooted phone be updated? If i root my razor, will i be able to update without re-rooting?
ChronosTrigger said:
Can a rooted phone be updated? If i root my razor, will i be able to update without re-rooting?
Click to expand...
Click to collapse
No, it fails to install. You need to reflash the stock boot image to take an OTA.
Confused still
CurtisMJ said:
No, it fails to install. You need to reflash the stock boot image to take an OTA.
Click to expand...
Click to collapse
I'm Sorry i'm so nooby in this regard.
So do you mean i have to basically get the stock ROM back again.
Then I can re-root like i did with the earlier version?
ChronosTrigger said:
I'm Sorry i'm so nooby in this regard.
So do you mean i have to basically get the stock ROM back again.
Then I can re-root like i did with the earlier version?
Click to expand...
Click to collapse
Yes. Razer's update engine doesn't seem to have the option to download full images like some other OEMs, so only fully stock ROM can be upgraded.
On that note, Razer seems to have set a week as the delay for releasing factory images, so if you want to keep root you might want to wait after an OTA, though we may be able to reproduce a slot earlier if someone captures the OTA package (but it's not as verifiable of course)
CurtisMJ said:
Yes. Razer's update engine doesn't seem to have the option to download full images like some other OEMs, so only fully stock ROM can be upgraded.
On that note, Razer seems to have set a week as the delay for releasing factory images, so if you want to keep root you might want to wait after an OTA, though we may be able to reproduce a slot earlier if someone captures the OTA package (but it's not as verifiable of course)
Click to expand...
Click to collapse
WARNING: This file is really intended for a developer to use in making a rooted slot. Flashing the file below could? remove root or cause other issues if you're rooted. Brick maybe? Although, mostly likely, it won't flash at all if you are rooted.
I used adb to capture the Razer Phone 2 MR2 OTA. It's located here.
I also downloaded it... but figure y'all would prefer a link straight to the Google source
SHA1 is the file name so you can verify it. E9F494FACBF8B7A6DF32F342C84459A7051ACE24
The SHA256 I calculated was: FF571E225BC81C8D450964E0C7BA28DF13E963798F9E5AF7E7C142DE7FBE51A5
translucentfocus said:
WARNING: Flashing the file below could? remove root or cause other issues if you're rooted. Brick maybe? I'm not rooted, just trying to help people get the files they need.
I used adb to capture the OTA. It's located here.
I also downloaded it... but figure y'all would prefer a link straight to the Google source
SHA1 is the file name so you can verify it. E9F494FACBF8B7A6DF32F342C84459A7051ACE24
The SHA256 I calculated was: FF571E225BC81C8D450964E0C7BA28DF13E963798F9E5AF7E7C142DE7FBE51A5
Click to expand...
Click to collapse
So With this. You can root, AND if they have any Update for the phone in the future, I can Update it without losing my root?
ChronosTrigger said:
So With this. You can root, AND if they have any Update for the phone in the future, I can Update it without losing my root?
Click to expand...
Click to collapse
Not quite... The update will likely fail to apply due to checksum failures. If it did go through it would probably brick the kernel so that's a good thing. Sorry, there's not really a way to automatically root after official OTAs as they update block by block between two known states, and neither is rooted. It's just sort of not possible, by design. You have to unroot, update and root again.
The OTA package translucentfocus has provided allows us to reproduce a single slot before the week's wait for the factory image so we can root sooner.
translucentfocus said:
WARNING: Flashing the file below could? remove root or cause other issues if you're rooted. Brick maybe? I'm not rooted, just trying to help people get the files they need.
I used adb to capture the OTA. It's located here.
I also downloaded it... but figure y'all would prefer a link straight to the Google source
SHA1 is the file name so you can verify it. E9F494FACBF8B7A6DF32F342C84459A7051ACE24
The SHA256 I calculated was: FF571E225BC81C8D450964E0C7BA28DF13E963798F9E5AF7E7C142DE7FBE51A5
Click to expand...
Click to collapse
which OTA is this? Also how to update
xterminater07 said:
which OTA is this? Also how to update
Click to expand...
Click to collapse
Sorry, I didn't specify. It's the MR2 update for the Razer Phone 2. Original reply has been also updated with version information in bold.
How to update? Actually, I posted the OTA because it's really for someone to make a slot with root before Razer releases the Factory MR2 Images--as @CurtisMJ mentioned previously.
CurtisMJ said:
Yes. Razer's update engine doesn't seem to have the option to download full images like some other OEMs, so only fully stock ROM can be upgraded.
On that note, Razer seems to have set a week as the delay for releasing factory images, so if you want to keep root you might want to wait after an OTA, though we may be able to reproduce a slot earlier if someone captures the OTA package (but it's not as verifiable of course)
Click to expand...
Click to collapse
Sorry to bring back an old thread but just a few questions if you don't mind.
I just bought a used Razer 2 seems like the user rooted it (I was unaware) and it has been years since I rooted anything. I downloaded root checker and it said I was rooted. I assume I'm running the stock rom, though magisk manager was installed on the phone when I turned it on so I guess it's not stock. I guess this means I can not take any OTA or it could brick? I went into system update and it still checked to make sure I was up to date so maybe OTA isn't disabled? So much has changed with apps and rooting since I messed with it that I don't know enough and I don't want to brick or bootloop the device.
Thanks
Univsoldur said:
Sorry to bring back an old thread but just a few questions if you don't mind.
I just bought a used Razer 2 seems like the user rooted it (I was unaware) and it has been years since I rooted anything. I downloaded root checker and it said I was rooted. I assume I'm running the stock rom, though magisk manager was installed on the phone when I turned it on so I guess it's not stock. I guess this means I can not take any OTA or it could brick? I went into system update and it still checked to make sure I was up to date so maybe OTA isn't disabled? So much has changed with apps and rooting since I messed with it that I don't know enough and I don't want to brick or bootloop the device.
Thanks
Click to expand...
Click to collapse
Yes, that sounds about right. When rooted the OTA function doesn't disable right away. Only after its downloaded an update and actually tries to apply it it'll refuse. The new Android update engine is pretty good at not bricking. My guess is probably stock. If it's rooted, then the bootloader is unlocked, and it's not too bad. For magisk root at least all you need to do is flash the stock boot image and the OTA will apply. With factory images around and an unlocked bootloader you'll have a hard time bricking it. Just don't untick "OEM Unlocking" in developer options. Ever. (Or at least until you've fully restored stock firmware. It's supposed to be disabled so you can't make that mistake but Magisk hide tricks the firmware into believing the bootloader is locked so it's enabled. Whaddayagonnado)
CurtisMJ said:
Yes. Razer's update engine doesn't seem to have the option to download full images like some other OEMs, so only fully stock ROM can be upgraded.
On that note, Razer seems to have set a week as the delay for releasing factory images, so if you want to keep root you might want to wait after an OTA, though we may be able to reproduce a slot earlier if someone captures the OTA package (but it's not as verifiable of course)
Click to expand...
Click to collapse
CurtisMJ said:
Yes, that sounds about right. When rooted the OTA function doesn't disable right away. Only after its downloaded an update and actually tries to apply it it'll refuse. The new Android update engine is pretty good at not bricking. My guess is probably stock. If it's rooted, then the bootloader is unlocked, and it's not too bad. For magisk root at least all you need to do is flash the stock boot image and the OTA will apply. With factory images around and an unlocked bootloader you'll have a hard time bricking it. Just don't untick "OEM Unlocking" in developer options. Ever. (Or at least until you've fully restored stock firmware. It's supposed to be disabled so you can't make that mistake but Magisk hide tricks the firmware into believing the bootloader is locked so it's enabled. Whaddayagonnado)
Click to expand...
Click to collapse
Thanks for the detailed response I managed to get up with the previous owner on swappa last night. He told me he unlocked the phone but never actually got around to rooting it. He also said it is running stock and the reason magisk is still on the phone after a wipe is because magisk persists after a wipe.
Messages from him.
Sorry about that, I did unlock the bootloader but I never actually got around to rooting. I usually relock the bootloader before I sell it but I completely forgot. You can apply an ota because I never installed a custom recovery, something else I didn't get around to doing. You can easily relock the bootloader using adb. If you need help with this let me know and I can walk you through it. But the bootloader being unlocked has zero effect on ota's. You are all good to go as far as that goes.
Oh no you're absolutely fine with an ota. I just looked it up and you're absolutely right, magisk does survive a reboot now. Since I didn't load a custom recovery though an ota will install just fine. Although when an ota does install though it will most likely remove magisk because it will write over the boot.img with the factory one. Here is the link to the factory images. It includes instructions on how to install it. But honestly a new ota should be released any time now since the last one I think was November. Once that installs you will be completely back to stock.
Does this sound accurate to y'all. Thanks again
@Univsoldur His knowledge seems a little dated. Kind of how mine was a few months ago Anyways here goes:
If a root checker says it's rooted then it probably is. I'm not sure why he says it isn't.
Magisk does indeed persist through a data wipe. I wasn't aware magiskinit could unpack the manager APK though. Neat
He's right in that an unlocked bootloader won't affect OTAs, but having magisk installed will.
The RP2 uses the new A/B update scheme. In this case it doesn't matter whether a custom recovery was ever installed. Recovery mode is not used during the process of installation. Unfortunately the new update scheme is also heavily based on deltas, even on the kernel image, so OTAs will be broken as it won't be able to retrieve a full kernel image from the OTA servers. Some OEMs' ROMs can do that, but Razer's can't. You can flash the factory images if you truly want a clean start, but to fix OTAs and remove magisk, reflashing just the kernel image with one from the factory image should be sufficient. The magisk uninstaller won't work due to the data wipe so that's probably the only option.
CurtisMJ said:
@Univsoldur His knowledge seems a little dated. Kind of how mine was a few months ago Anyways here goes:
If a root checker says it's rooted then it probably is. I'm not sure why he says it isn't.
Magisk does indeed persist through a data wipe. I wasn't aware magiskinit could unpack the manager APK though. Neat
He's right in that an unlocked bootloader won't affect OTAs, but having magisk installed will.
The RP2 uses the new A/B update scheme. In this case it doesn't matter whether a custom recovery was ever installed. Recovery mode is not used during the process of installation. Unfortunately the new update scheme is also heavily based on deltas, even on the kernel image, so OTAs will be broken as it won't be able to retrieve a full kernel image from the OTA servers. Some OEMs' ROMs can do that, but Razer's can't. You can flash the factory images if you truly want a clean start, but to fix OTAs and remove magisk, reflashing just the kernel image with one from the factory image should be sufficient. The magisk uninstaller won't work due to the data wipe so that's probably the only option.
Click to expand...
Click to collapse
So you think to get it back to stock I could just go here.
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Will that remove magisk and return it back to stock I would assume there is no threat of flashing the stock image. Besides that do I need to mess with the kernel?
I'm wondering if it would be possible to flash the unlocked Razer phone 2 firmware to the AT&T version. Would the bootloader need to be unlocked?
Univsoldur said:
So you think to get it back to stock I could just go here.
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Will that remove magisk and return it back to stock I would assume there is no threat of flashing the stock image. Besides that do I need to mess with the kernel?
Click to expand...
Click to collapse
Yes, that will return it to stock and remove Magisk. No, if you flash the factory image you don't need to do anything further with the kernel.
---------- Post added at 11:14 PM ---------- Previous post was at 11:11 PM ----------
DrGonzo6o said:
I'm wondering if it would be possible to flash the unlocked Razer phone 2 firmware to the AT&T version. Would the bootloader need to be unlocked?
Click to expand...
Click to collapse
The bootloader needs to be unlocked, yes. I had the unlocked one from the start, so I can't comment on how well that will work though.
Has anyone with an AT&T version successfully flashed unlocked firmware?
Univsoldur said:
So you think to get it back to stock I could just go here.
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Will that remove magisk and return it back to stock I would assume there is no threat of flashing the stock image. Besides that do I need to mess with the kernel?
Click to expand...
Click to collapse
I did post a full unroot guide...