I am currently rooted running stock A11. I noticed that the update to A12 is now available. Just for fun, I checked updates on my phone & it says there is an update for A12 available. I thought being rooted, with the boot-loader unlocked, I wouldn't get updates. But there it is, asking me to download it.
Would it work if I downloaded and installed it via OTA on my phone? Would it wipe all my data (internal storage) and un-root me? Would it brick me? Just asking because I thought the proper way to update while rooted was this way (step #4), but doing it via OTA doesn't get much easier.
I am currently happy with how my phone is set up and running. I don't have an urgent need to update and really dislike setting up a phone as new. Of course, if an update to new a new OS is available...I'm going to want to install it eventually.
Thanks for the advice!
I'm not going past Q on my stock N10+'s, one still running very well on Pie. It's load is over 1.5 years old.
The first thing I do on my stock phones is disable OTA Updates. I may eventually update the Pie one to Q but it's more restrictive than Pie. I gain some nice features and it runs a bit faster, but loose some functionality as well.
Security simply isn't an issue with Pie in everyday use. Q may prove more troublesome.
Going to R would break them. It's a mess. CPU cycle burning scoped storage and tard repetitive security permissions. All my apps are vetted and trusted, many wouldn't load on R. Some aren't replaceable like my free office app which I use a lot. Plus forced encryption on first boot up... trashware.
Trust 12 to be better? When pigs fly.
Rule #1, if your OS is running fast, stable and fulfilling its mission let it be.
At the best you'll waste a lot of time that wasn't worth the trouble and at the worst end worse off than before. I'm not buying the hype.
mn1968 said:
I am currently rooted running stock A11. I noticed that the update to A12 is now available. Just for fun, I checked updates on my phone & it says there is an update for A12 available. I thought being rooted, with the boot-loader unlocked, I wouldn't get updates. But there it is, asking me to download it.
Would it work if I downloaded and installed it via OTA on my phone?
Click to expand...
Click to collapse
Yes, you can update via OTA.
mn1968 said:
Would it wipe all my data (internal storage) and un-root me?
Click to expand...
Click to collapse
The OTA preserves /data, but because it updates the boot image, you will lose root.
mn1968 said:
Would it brick me? Just asking because I thought the proper way to update while rooted was this way (step #4), but doing it via OTA doesn't get much easier.
Click to expand...
Click to collapse
Why would an OTA update brick your device? The answer is no. However, due to Android Verified Boot features, you will need to disable both dm-verity and vbmeta verification in order to flash and boot a patched boot image. Unfortunately, this has required a data wipe to work. Those of us on the Pixel 5 are experiencing the same issue and are still working on the "why". If you leave /vbmeta and /boot stock, you can still temporarily boot a patched image....which just means that you'll lose root when you reboot.
mn1968 said:
I am currently happy with how my phone is set up and running. I don't have an urgent need to update and really dislike setting up a phone as new. Of course, if an update to new a new OS is available...I'm going to want to install it eventually.
Thanks for the advice!
Click to expand...
Click to collapse
Understandable. As I mentioned above, if you want to upgrade to Android 12 and have permanent root, it's likely that you will have to wipe. However, you can try following this guide and see if it works for you. Be warned, the user that posted that was on the 12 Beta, and had wiped previously when upgrading from Android 11. It won't cause a brick, but you may still have to wipe your device. If you're prepared to bite that bullet, you can give it a try.
Ultimately, you have 3 options:
Stay on Android 11 with root
Upgrade to Android 12, keep data, but lose root
Upgrade to Android 12, most likely wipe data, and reroot.
blackhawk said:
Rule #1, if your OS is running fast, stable and fulfilling its mission let it be.
At the best you'll waste a lot of time that wasn't worth the trouble and at the worst end worse off than before. I'm not buying the hype.
Click to expand...
Click to collapse
There is a certain degree of logic to this. I used Windows 7 and refused to update to 8.1 or 10 for a long time. Now that I'm on 10 Enterprise LTSC, I'm refusing to upgrade to 11. If it ain't broke, don't fix it.
Related
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
According to this page
https://support.t-mobile.com/docs/DOC-18109#update_download
T-Mobile began rolling out 6.0 on October 5th. It states in the instructions to perform the update manually is essentially performing the android check for updates however I get no prompt to download the OTA.
Has anyone found a way to force the update? Possibly resetting the device?
Thanks!
Wait for the OTA, sideload when someone gets the link or flash the entire image (lose everything)...
Keep pressing that update button, but it does nothing ..
I'm literally going to beat a dead horse but why, are even Google's devices subjected to this ridiculous update process? If someone wants the OTA then they should be able to get it..
I am rooted on TMO and did a manual update to LYZ28K a while back. I clicked on Check for System Update just for kicks and it downloaded a 23.2 MB file. Any idea what that is?
JimSmith94 said:
I am rooted on TMO and did a manual update to LYZ28K a while back. I clicked on Check for System Update just for kicks and it downloaded a 23.2 MB file. Any idea what that is?
Click to expand...
Click to collapse
LYZ28M An update to Android 5.1.1
steve841 said:
Wait for the OTA, sideload when someone gets the link or flash the entire image (lose everything)...
Keep pressing that update button, but it does nothing ..
Click to expand...
Click to collapse
There are methods you can use when manually flashing to not lose data. (Don't flash userdata.img) be it through fastboot cmd directly, or through the use of a toolkit like Wugs.
OP, save yourself the headache and just download the update and fastboot it. It's a unified image so there is no need to wait for a "specific" version.
Peylix said:
There are methods you can use when manually flashing to not lose data. (Don't flash userdata.img) be it through fastboot cmd directly, or through the use of a toolkit like Wugs.
OP, save yourself the headache and just download the update and fastboot it. It's a unified image so there is no need to wait for a "specific" version.
Click to expand...
Click to collapse
Am I going to lose the ability to get future OTAs if I go this route? I've got an unlocked bootloader.... But not rooted and completely stock ROM.
slopokdave said:
Am I going to lose the ability to get future OTAs if I go this route? I've got an unlocked bootloader.... But not rooted and completely stock ROM.
Click to expand...
Click to collapse
You can still get OTA's as long as you're not rooted. Unlocked bootloader doesn't matter. Anyways, even if you did root, you can just manually flash the next update the same way. Takes less than 20 minutes to do.
Peylix said:
You can still get OTA's as long as you're not rooted. Unlocked bootloader doesn't matter. Anyways, even if you did root, you can just manually flash the next update the same way. Takes less than 20 minutes to do.
Click to expand...
Click to collapse
Thanks this worked perfect!
JoshRH said:
I'm literally going to beat a dead horse but why, are even Google's devices subjected to this ridiculous update process? If someone wants the OTA then they should be able to get it..
Click to expand...
Click to collapse
We do, it's called the factory images that google provides, we get the updates immediately (had 6.0 on release day), if you want to "wait" then it's only on you, the means are out there to get the updates right away, otherwise, gotta wait for the carriers. Android isn't and doesn't seem like it'll be like the iphone, independent from carriers as far as updates. Unless Google grows some nads and lays their foot down, this is how it will always be sadly.....once again, unless you just get the update and do it yourself like maybe 80% of the community here.
While II respect the fact that the majority of the XDA community is willing and capable to erase all data and side load 6.0 this isn't something that should be accepted in 2015. I'm not asking for Google to be like Apple, but for a Nexus device, a device designed to offer the latest and most up to date version of android, to be forced to wait for weeks for a proper OTA update is just ridiculous. I simply laugh at the android 6.0 articles that the tech blogs are releasing when 99% of the user base doesn't have access to the software.
Like I said I know that this has been discussed time and again, it's just hard to believe that a company as mature and advanced as Google, can't get an OTA rolling out to all 5 million Nexus 6 owners when Apple does in fact provide the latest software, on day one to multiple hundreds of million users. It's honestly quite gross.
JoshRH said:
While II respect the fact that the majority of the XDA community is willing and capable to erase all data and side load 6.0 this isn't something that should be accepted in 2015. I'm not asking for Google to be like Apple, but for a Nexus device, a device designed to offer the latest and most up to date version of android, to be forced to wait for weeks for a proper OTA update is just ridiculous. I simply laugh at the android 6.0 articles that the tech blogs are releasing when 99% of the user base doesn't have access to the software.
Click to expand...
Click to collapse
Nope, you don't have to erase your data to sideload an update (keep in mind that sideloading an OTA isn't possible if you have root, custom recovery or custom kernel). You don't even have to erase any data (provided that you don't need to unlock your bootloader prior to flashing) if you flash a factory image (even though it's nice to clean out the old system once in a while).
This was just a tangent, my real reason for replying follows:
Like I said I know that this has been discussed time and again, it's just hard to believe that a company as mature and advanced as Google, can't get an OTA rolling out to all 5 million Nexus 6 owners when Apple does in fact provide the latest software, on day one to multiple hundreds of million users. It's honestly quite gross.
Click to expand...
Click to collapse
Of course they can roll out the OTA to everybody at once, but they don't want to (and I agree). Check out this article (2 years old, yes, but the base principle still stands):
http://www.androidpolice.com/2013/1...to-never-clear-google-service-framework-data/
JoshRH said:
While II respect the fact that the majority of the XDA community is willing and capable to erase all data and side load 6.0 this isn't something that should be accepted in 2015.
Click to expand...
Click to collapse
You don't have to wait weeks. You have to potentially wait days, sometimes it is hours. Soon someone will snag the OTA url, if they haven't already, and then you can use ADB to sideload it without needing to wipe anything.
I haven't been following too closely, but I actually haven't seen anyone that has stated they have actually received 6.0 OTA yet. Some people posting they were, but they were getting one of the security fixes. Maybe they actually haven't pushed the OTA to the Nexus 6 yet for some reason?
Like I said I know that this has been discussed time and again, it's just hard to believe that a company as mature and advanced as Google, can't get an OTA rolling out to all 5 million Nexus 6 owners when Apple does in fact provide the latest software, on day one to multiple hundreds of million users. It's honestly quite gross.
Click to expand...
Click to collapse
It also has nothing with Google's ability to roll updates out to all of the Nexus owners. It is how they decide to stagger their updates out to people. They do this to make sure everything goes smoothly. If they put an update out that causes some sort of major problem, it would suck if it was in the hands of every single user, rather than just 1%.
The only update I received today was LYZ28M sadly. Not sure why they don't just have an app where people can download Nexus updates any time instead of OTA.
I got all the important stuff backed on Drive and most of the time I get all back even without backing it up
JoshRH said:
While II respect the fact that the majority of the XDA community is willing and capable to erase all data and side load 6.0 this isn't something that should be accepted in 2015. I'm not asking for Google to be like Apple, but for a Nexus device, a device designed to offer the latest and most up to date version of android, to be forced to wait for weeks for a proper OTA update is just ridiculous. I simply laugh at the android 6.0 articles that the tech blogs are releasing when 99% of the user base doesn't have access to the software.
Like I said I know that this has been discussed time and again, it's just hard to believe that a company as mature and advanced as Google, can't get an OTA rolling out to all 5 million Nexus 6 owners when Apple does in fact provide the latest software, on day one to multiple hundreds of million users. It's honestly quite gross.
Click to expand...
Click to collapse
Hello all!
I've been looking around the forum for answers to my questions, but I'm still pretty unsure, and I'm worried about messing up my phone, so if someone could hold my hand a little bit, I would appreciate it so much!
When the marshmallow update came out, I unlocked my bootloader with Sunshine and installed TWRP and rooted. I'm currently on stock 6.0.1 and September 1, 2016 security patch.
Issue #1: Ever since I unlocked/rooted/updated to marshmallow I've had problems with some of my apps deciding they can't connect to the internet, even though WiFi and 4G are clearly connected. Like I'll be able to browse the internet on Chrome just fine, but the Amazon app won't connect.
From what I've read, it seems like a problem a lot of people have had after upgrading to marshmallow, but I'm still worried it's because I'm unlocked or rooted or have Xposed installed or something.
Restarting the phone seems to be the only thing that really makes the apps work again (temporarily). I read somewhere about clearing the cache from recovery and that seemed to have fixed the problem for a couple of months, but lately I've been having the problem again, and clearing the cache isn't helping beyond having to restart my phone to do it.
Issue #2: I've been scared to take the OTA security updates.. I've generally gathered that they won't relock my bootloader, but I'm unclear on if it's ok to take the updates OTA or if I have to download and install them through TWRP.
Also, do I even need those updates? Call me stupid, but I'm not that worried about security (the only thing I own is a massive amount of student debt, go ahead and take it =P). I'm really just hoping the updates fix the internet thing.. is that a possibility?
So overall I guess I'm asking, will taking the updates OTA wreck my stuff, and is there a chance updating will fix my internet connectivity problem?
Or will using a different ROM possibly fix my internet problem? If so, which ROM would you recommend? I used to have a Razr M with the latest (at the time) CM ROM, but I couldn't use Bluetooth and WiFi at the same time, so it kind of left a bad taste in my mouth about custom ROMs...
Any answers or advice would be greatly appreciated!! Thank you!!
If you have TWRP installed, NEVER take an OTA. You will bootloop or brick your phone. Instead just install the TWRP flashable version from this forum.
This is what you would flash, via TWRP if you want the latest firmware while keeping custom TWRP recovery.
[ROM] MCG24.251-5-5 100% Stock
https://forum.xda-developers.com/droid-turbo/general/rom-mcg24-251-5-5-100-stock-t3565795
Perhaps re-flashing your modem might help? It's also at that thread. TWRP flashable version.
By popular demand, here are just the modems: https://www.androidfilehost.com/?fid=745425885120733904
Click to expand...
Click to collapse
Ok, thank you ChazzMatt!
birdgofly said:
Ok, thank you ChazzMatt!
Click to expand...
Click to collapse
As for custom ROMs, for you who is not that experienced I would suggest this one:
Computerfreek274_1.0.8 Update Marshmallow 6.0.1 Global,De-bloated,Root,Volte, 5/29/17
https://forum.xda-developers.com/dr.../computerfreek274mm1-0-android-6-0-1-t3503634
It's actually a tweaked, debloated version of Verizon stock Marshmallow firmware. Everything will still work, including Verizon VoLTE (on Verizon, of course, not other networks). Has slight volume boost, battery optimization, etc.
And of course, lots of experienced users are also running that ROM. I do not mean to criticize it in any way, but you just mentioned that you ran some ROM where some stuff didn't work. This is a ROM built on stock, not CM/LOS based. Nothing much has been changed, just bloatware removed and some tweaks.
No worries, that ROM sounds perfect!
Thank you very much for all of your help!!
birdgofly said:
Hello all!
I've been looking around the forum for answers to my questions, but I'm still pretty unsure, and I'm worried about messing up my phone, so if someone could hold my hand a little bit, I would appreciate it so much!
When the marshmallow update came out, I unlocked my bootloader with Sunshine and installed TWRP and rooted. I'm currently on stock 6.0.1 and September 1, 2016 security patch.
Issue #1: Ever since I unlocked/rooted/updated to marshmallow I've had problems with some of my apps deciding they can't connect to the internet, even though WiFi and 4G are clearly connected. Like I'll be able to browse the internet on Chrome just fine, but the Amazon app won't connect.
From what I've read, it seems like a problem a lot of people have had after upgrading to marshmallow, but I'm still worried it's because I'm unlocked or rooted or have Xposed installed or something.
Restarting the phone seems to be the only thing that really makes the apps work again (temporarily). I read somewhere about clearing the cache from recovery and that seemed to have fixed the problem for a couple of months, but lately I've been having the problem again, and clearing the cache isn't helping beyond having to restart my phone to do it.
Issue #2: I've been scared to take the OTA security updates.. I've generally gathered that they won't relock my bootloader, but I'm unclear on if it's ok to take the updates OTA or if I have to download and install them through TWRP.
Also, do I even need those updates? Call me stupid, but I'm not that worried about security (the only thing I own is a massive amount of student debt, go ahead and take it =P). I'm really just hoping the updates fix the internet thing.. is that a possibility?
So overall I guess I'm asking, will taking the updates OTA wreck my stuff, and is there a chance updating will fix my internet connectivity problem?
Or will using a different ROM possibly fix my internet problem? If so, which ROM would you recommend? I used to have a Razr M with the latest (at the time) CM ROM, but I couldn't use Bluetooth and WiFi at the same time, so it kind of left a bad taste in my mouth about custom ROMs...
Any answers or advice would be greatly appreciated!! Thank you!!
Click to expand...
Click to collapse
There's a complete TWRP flashable update to the latest '5-5' firmware. Saves you the time of putting stock recovery back on and taking it OTA. The TWRP flash won't install the stock recovery, TWRP will stay. There's also a zip to clear/reset the radio/modem. You may not need that due to updating the rom.
Sent from my XT1254 using Tapatalk
So just an update for anyone who might come across this thread later.. I ended up flashing the ComputerFreek ROM suggested by ChazzMatt (didn't clean install, just wiped cache). It worked great, and so far I haven't had any more problems with apps not being able to connect!
Thank you to ChazzMatt, ComputerFreek, Einsteindks, and the wonderful XDA community for all your help
I usually root every phone, but since this is something I do once a year, I tend to forget some basics (so bear with me). Other things, I actually never really knew.
Until now, rooting a phone and flashing a custom rom (or the factory image) were "one and done" things and I simply never updated my phone ever again, since OTA no longer works once the bootloader is unlocked, and installing a newer image forced me to wipe everything in TWRP or else I could no longer read the encrypted memory. Of course, that also forced me to re-root my phone and reinstall everything. A bit too much of a hassle for monthly security updates...
Nowadays, however, updates and security patches are more important than ever. And since I just received my rootable SD N9600, I want to do it correctly this time and stay up do date.
This begs the question: How *do* I stay up to date without basically factory-resetting, re-formatting and re-rooting my phone every month for every security update?
Google showed me a few solutions.
Pixel phones apparently have A/B partitions and a TWRP script. Not an option for the Note 9, though.
Flashfire apparently was the perfect solution that did exactly what I was looking for, but it has been abandoned by Chainfire and unfortunately it no longer works with newer Magisk versions. Even when I downgraded to a super old Magisk version, it would ultimately crash when starting the app (after receiving root permissions). So it doesn't seem to work, although staying on an old version of Magisk forever would not be an ideal solution anyway.
Is there anything like Flashfire or a simpler approach that I am missing?
Surely, I can't be the only rooted user who wants to install monthly security patches without wiping the entire phone.
Spaced Invader said:
I usually root every phone, but since this is something I do once a year, I tend to forget some basics (so bear with me). Other things, I actually never really knew.
Until now, rooting a phone and flashing a custom rom (or the factory image) were "one and done" things and I simply never updated my phone ever again, since OTA no longer works once the bootloader is unlocked, and installing a newer image forced me to wipe everything in TWRP or else I could no longer read the encrypted memory. Of course, that also forced me to re-root my phone and reinstall everything. A bit too much of a hassle for monthly security updates...
Nowadays, however, updates and security patches are more important than ever. And since I just received my rootable SD N9600, I want to do it correctly this time and stay up do date.
This begs the question: How *do* I stay up to date without basically factory-resetting, re-formatting and re-rooting my phone every month for every security update?
Google showed me a few solutions.
Pixel phones apparently have A/B partitions and a TWRP script. Not an option for the Note 9, though.
Flashfire apparently was the perfect solution that did exactly what I was looking for, but it has been abandoned by Chainfire and unfortunately it no longer works with newer Magisk versions. Even when I downgraded to a super old Magisk version, it would ultimately crash when starting the app (after receiving root permissions). So it doesn't seem to work, although staying on an old version of Magisk forever would not be an ideal solution anyway.
Is there anything like Flashfire or a simpler approach that I am missing?
Surely, I can't be the only rooted user who wants to install monthly security patches without wiping the entire phone.
Click to expand...
Click to collapse
n9600 has limited development from the community. so if you are not going to flash a custom rom( usually thats how people stay up to date) then you will have to go through the rooting procedure each time.
bober10113 said:
n9600 has limited development from the community. so if you are not going to flash a custom rom( usually thats how people stay up to date) then you will have to go through the rooting procedure each time.
Click to expand...
Click to collapse
So every solution that makes this easier is strictly device-specific and nothing like Flashfire (which would have worked regardless of community activity for the N9600) exists anymore?
Dark times indeed, almost makes me question if I should keep rooting my devices...
I have rooted note8 with decrypted data partition (no-verity... something script). I updated recently to newest firmware simply through odin. I flashed firmware preserving data (home csc file?). There was bootloop but after i flashed twrp and rooted with magisk phone started without problem and all settings and data was there. So this is solution for me, maybe it will work on note 9 too.
Spaced Invader said:
So every solution that makes this easier is strictly device-specific and nothing like Flashfire (which would have worked regardless of community activity for the N9600) exists anymore?
Dark times indeed, almost makes me question if I should keep rooting my devices...
Click to expand...
Click to collapse
Personally I'm sticking with phones officially supported by lineageOs (formerly cynogenmod) from now on.
Kriomag said:
I have rooted note8 with decrypted data partition (no-verity... something script). I updated recently to newest firmware simply through odin. I flashed firmware preserving data (home csc file?). There was bootloop but after i flashed twrp and rooted with magisk phone started without problem and all settings and data was there. So this is solution for me, maybe it will work on note 9 too.
Click to expand...
Click to collapse
Hi, I have a Note 9 that was rooted with Magisk and running on Oreo 8. I updated it via Odin to Android 10. I have a bootloop. What should I do? Please help me
Hey there guys,
I just received my s21 ultra (G998B) and planning to root it. I had a few questions since I’m new to this and wanted some clarifications:
1) If I root the phone can I update it OTA through the settings or do I have to update it by another method? Will I lose root/data/apps if I do that?
2) If I lose root when updating it, can I just root again and be all set? Or do I have to follow another procedure for that?
3) I am planning to debloat a few apps and services that I won’t be using, if I update the system/software will the stuff that I debloated come back and will I have to do the debloat again?
Thank you for all the help.
paul_cherma said:
Hey there guys,
I just received my s21 ultra (G998B) and planning to root it. I had a few questions since I’m new to this and wanted some clarifications:
1) If I root the phone can I update it OTA through the settings or do I have to update it by another method? Will I lose root/data/apps if I do that?
2) If I lose root when updating it, can I just root again and be all set? Or do I have to follow another procedure for that?
3) I am planning to debloat a few apps and services that I won’t be using, if I update the system/software will the stuff that I debloated come back and will I have to do the debloat again?
Thank you for all the help.
Click to expand...
Click to collapse
1- Probably not usually the root or recovery will block OTA updates from installing, even if they download.
2- If you lose root, you can USUALLY re-root assuming the same root method wasnt patched. If it was patched, a new root method (though probably still through magisk) will be needed. If this is the case, its up to the dev to find that method, you might be without root for a while.
3-if you debloat, and receive an OTA, your will probably need to de-bloat again, thought I havent personally had experience with this.
Why are you rooting? Just to de-bloat? If so, root isn't really necessary...
As someone who's been in the rooting stage for many years, i can answer your questions.
1. You can not update your phone through OTA updates after rooting the device, as the device was modified in an unauthorized way. And since you own a galaxy phone, the e-fuse within the motherboard will blow and knox will be permanently blown. You can no longer use samsung pay, google pay, and any other app that uses the safetynet api, even after you unroot the device.
2. You will lose root every time you update. You will need ODIN on your PC in order to properly update your firmware and to re-root your device by following the procedure again that you used to root your device, unless samsung patched the method you used to root your device. You can always check what bootloader version you're on within the firmware. For example, on the galaxy S8, the firmware version is N950U1UES5CRG9. The 5th to last number of the firmware will tell you. In this case, N950U1UES5CRG9 is the 5th bootloader version. Keep this in mind once samsung starts to update your phone often.
3. You will have to debloat again from scratch. In order to fully update your device through ODIN, you need to download the full firmware file containing an AP (Firmware), BL (Bootloader) , CP (Modem), and CSC (Carrier File) and manually flash them.
Do keep in mind, it is possible to soft brick or even hard brick your device, so back up your data frequently if you decide to tinker with your device.
Thank you for the detailed answer. I just updated my software to the latest official one by Samsung (April 1st security patch) but I am not rooted yet. I guess I could live with the fact that I can root the phone now and stay on this software version/security patch until I upgrade, since I would have to go through a lot of hassle to set-up the phone the way I wanted. But the main reason why I want to get the official updates is because of the camera improvements that Samsung does, since the main reason of me getting this phone is the camera. And there are some root-required tweaks that I absolutely need such as Viper, and some xposed tweaks also. I like the Stock ROM of Samsung, it really has come a long way at least imo throughout the years, as I have been a Samsung user since day 1 but:
Would it be a good idea to install a custom ROM then? I am reading the description of a few custom ROMs and it seems like I can “retain everything” by simply dirty flashing the ROM and following the dev’s instructions on how to retain root whenever the developer updates it. Is that a better route to take you think? I can keep my device rooted, and still get the updates through a custom ROM.
paul_cherma said:
Thank you for the detailed answer. I just updated my software to the latest official one by Samsung (April 1st security patch) but I am not rooted yet. I guess I could live with the fact that I can root the phone now and stay on this software version/security patch until I upgrade, since I would have to go through a lot of hassle to set-up the phone the way I wanted. But the main reason why I want to get the official updates is because of the camera improvements that Samsung does, since the main reason of me getting this phone is the camera. And there are some root-required tweaks that I absolutely need such as Viper, and some xposed tweaks also. I like the Stock ROM of Samsung, it really has come a long way at least imo throughout the years, as I have been a Samsung user since day 1 but:
Would it be a good idea to install a custom ROM then? I am reading the description of a few custom ROMs and it seems like I can “retain everything” by simply dirty flashing the ROM and following the dev’s instructions on how to retain root whenever the developer updates it. Is that a better route to take you think? I can keep my device rooted, and still get the updates through a custom ROM.
Click to expand...
Click to collapse
That really varies depending on the custom rom you go for. Usually when you dirty flash a rom, you would need to re root your device, but some (not all) roms are persistent with root after system updates. Do keep in mind if you switch to a custom rom, your system might be more buggy and crash more often. One thing i will say though is that xposed is outdated. The last android version xposed officially supported was either 8 or 9. When it has to come down to certain mods you'd wish to have with root, take that into consideration too, as it might make your device really unstable if it's too outdated or if there's a buggy port available. I've dealt with that issue too many times on my phones.
HighOnLinux said:
That really varies depending on the custom rom you go for. Usually when you dirty flash a rom, you would need to re root your device, but some (not all) roms are persistent with root after system updates. Do keep in mind if you switch to a custom rom, your system might be more buggy and crash more often. One thing i will say though is that xposed is outdated. The last android version xposed officially supported was either 8 or 9. When it has to come down to certain mods you'd wish to have with root, take that into consideration too, as it might make your device really unstable if it's too outdated or if there's a buggy port available. I've dealt with that issue too many times on my phones.
Click to expand...
Click to collapse
if xposed is outdated, what is the new thing the comunity is migrating to? All the privacy, security, and customizability tools available through xposed must go somewhere, right?
Twodordan said:
if xposed is outdated, what is the new thing the comunity is migrating to? All the privacy, security, and customizability tools available through xposed must go somewhere, right?
Click to expand...
Click to collapse
There's buggy ports thats flashable on magisk. While you still can get xposed, it'll be an unofficial version, and more likely to run into issues within your rom and daily use into your device.
HighOnLinux said:
There's buggy ports thats flashable on magisk. While you still can get xposed, it'll be an unofficial version, and more likely to run into issues within your rom and daily use into your device.
Click to expand...
Click to collapse
I mean xprivacy on xposed was the must have killer feature for any android device to turn your device into anything other than a privacy nightmare. If we can't do that any more we are f'd.
[EDIT] Looks like the new version of xprivacy, xprivacyLua is still supported for android 11, with magisk and EdXposed or LSPosed:
[CLOSED][APP][XPOSED][6.0+] XPrivacyLua - Android privacy manager [UNSUPPORTED]
XPrivacyLua Really simple to use privacy manager for Android 6.0 Marshmallow and later (successor of XPrivacy). Revoking Android permissions from apps often let apps crash or malfunction. XPrivacyLua solves this by feeding apps fake data...
forum.xda-developers.com
XPrivacyLua/README.md at master · M66B/XPrivacyLua
Really simple to use privacy manager for Android 6.0 Marshmallow and later - XPrivacyLua/README.md at master · M66B/XPrivacyLua
github.com