Hello
I bought the Note 4 from T-mobile and i'm running stock rom.
I just root the device with chainfire tool and I'm thinking to change the recovery from stock to TWRP.
I'm wondering if by doing that i will lose the ability to get OTA updates from Samsung / T-mobile.
I did a search on the forum for this question, most of the threads are a year old so i just want to make sure that the answer is the same for our new device.
Please answer just if you know for sure, Thanks
re: twrp
NirAndroid said:
Hello
I bought the Note 4 from T-mobile and i'm running stock rom.
I just root the device with chainfire tool and I'm thinking to change the recovery from stock to TWRP.
I'm wondering if by doing that i will lose the ability to get OTA updates from Samsung / T-mobile.
I did a search on the forum for this question, most of the threads are a year old so i just want to make sure that the answer is the same for our new device.
Please answer just if you know for sure, Thanks
Click to expand...
Click to collapse
You already lost the ability to receive OTA updates by rooting
the phone. If you want to get OTA updates the phone cannot be
rooted or have custom recovery like twrp.
The whole and main idea behind having twrp custom recovery
is to be able to flash custom zip file roms and mods.
With stock rooted firmware you will not be able to successfully
flash any custom roms or mods.
If you do flash any custom zip file roms using twrp
you will also loose the ability to have OTA updates.
Good luck!
First, thank you for the quick reply,
Second, are you sure about it? every place I looked people saying that root doesn't have anything to do with OTA updates.
It also say that I can put TWRP or CWM and still getting the OTA updates, all I have to do for this to happen is to be with stock rom (which is what i'm currently using)
Misterjunky said:
You already lost the ability to receive OTA updates by rooting
the phone. If you want to get OTA updates the phone cannot be
rooted or have custom recovery like twrp.
The whole and main idea behind having twrp custom recovery
is to be able to flash custom zip file roms and mods.
With stock rooted firmware you will not be able to successfully
flash any custom roms or mods.
If you do flash any custom zip file roms using twrp
you will also loose the ability to have OTA updates too.
Good luck!
Good luck!
Click to expand...
Click to collapse
NirAndroid said:
First, thank you for the quick reply,
Second, are you sure about it? every place I looked people saying that root doesn't have anything to do with OTA updates.
It also say that I can put TWRP or CWM and still getting the OTA updates, all I have to do for this to happen is to be with stock rom (which is what i'm currently using)
Click to expand...
Click to collapse
If you check the OTA option and find an update, the updater
will tell you that it cannot install the update due to an unofficial
operating system or something to that effect, I forgot the exact
wording of the message. (if you're rooted)
There is a way to unroot the phone but in my opinion it's just not worth the
hassle to re-root it because as I said being rooted and having twrp recovery
will not help you much at all since you will not be able to flash any custom
roms or mods with out loosing your official stock status which needs to
remain intact in order to be able to get future ota updates.
Good luck!
NirAndroid said:
First, thank you for the quick reply,
Second, are you sure about it? every place I looked people saying that root doesn't have anything to do with OTA updates.
It also say that I can put TWRP or CWM and still getting the OTA updates, all I have to do for this to happen is to be with stock rom (which is what i'm currently using)
Click to expand...
Click to collapse
Mr. Junky is correct. But why would you even want an OTA update? Even if you could it would unroot your device. If there is/was a software update it will be on here or SamMobile about the same time & you can install it manually.
NirAndroid said:
First, thank you for the quick reply,
Second, are you sure about it? every place I looked people saying that root doesn't have anything to do with OTA updates.
It also say that I can put TWRP or CWM and still getting the OTA updates, all I have to do for this to happen is to be with stock rom (which is what i'm currently using)
Click to expand...
Click to collapse
You have only 2 posts on XDA and you are second guessing our replies on your question? Either believe what we answer or stick to google and don't waste our time.
NirAndroid said:
Hello
I bought the Note 4 from T-mobile and i'm running stock rom.
I just root the device with chainfire tool and I'm thinking to change the recovery from stock to TWRP.
I'm wondering if by doing that i will lose the ability to get OTA updates from Samsung / T-mobile.
I did a search on the forum for this question, most of the threads are a year old so i just want to make sure that the answer is the same for our new device.
Please answer just if you know for sure, Thanks
Click to expand...
Click to collapse
Well OTA is out of the question. But I was successful with the last update by using Kies 3.
I just had to root again afterwards using the same method.
Brava27 said:
You have only 2 posts on XDA and you are second guessing our replies on your question? Either believe what we answer or stick to google and don't waste our time.
Click to expand...
Click to collapse
No body asked you to spend your time in my thread, you are more then welcome to move a long because its clearly that you have nothing smart to say beside rasing your post counter.
For all the others, thank you for your help.
The reason that i would like to keep the OTA updates is because i love the stock rom and i dont want to check every timr on the internet if a new build has came out.
its much more easier with OTA too keep being update. But i guess my needs to be root are biger and i will need to flash the updates manually.
Once again, thank you.
I get Ota updates on mine rooted.Only thing u can't install if u have twrp will put u in a boot loop it needs the stock android recovery.You have to wait for a rom with the update
...........As long as I can remember, you root a device you lose carrier OTA updates. ..why is this so difficult for people to comprehend o_0 every new device every year it's the same questions. .......you have the capacity to root......yet you question if you'll lose OTA -_-, & most root methods have disclaimers saying you lose this x we are not responsible for brick etc. ........
Sent from my SM-N910T using Tapatalk
Related
I figured, I would get the best response here... If you ROOT an Android phone, will downloading OTA updates through your phone brick it? I read an article about the new OTA for the EVO and it will brick rooted devices.
Misinformation. It would brick it if you applied it twice in sequence, not if you were rooted. You need the stock recovery to apply updates anyway, if you do get one it will not harm the phone because it can't be applied.
In the thread when the final OTA was coming out, lots of people that were rooted, said they installed it, it worked fine, but they lost root. So then they have to obtain root again.
So, I'd assume it would work fine if everything else was stock... you just might loose root.
So your saying, that if I were to install an OTA update through a rooted Android device running stock firmware, it would go through successfully without bricking it. But, if I ran the update a second time it would brick it. Correct?
If you're on a rooted stock rom, assuming you haven't flashed a custom recovery, the phone's recovery utility will not allow you to flash an OTA update because of a signature mismatch. I'm not sure what happened with the evo, but I don't believe it can happen with the nexus.
Okay, thanks? But I would still like some more input on this situation.
Pay attention
PurpleLlamaLover said:
Okay, thanks? But I would still like some more input on this situation.
Click to expand...
Click to collapse
If your not rooted you can still flash OTA update leaks, there are plenty out there. If you want custom roms then you have to root. The stock recovery only flashes stock updates, not rooted updates. If your not getting it by reading the forums, then I suggest you stay on stock, and wait for OTA update.
efishta said:
If you're on a rooted stock rom, assuming you haven't flashed a custom recovery, the phone's recovery utility will not allow you to flash an OTA update because of a signature mismatch. I'm not sure what happened with the evo, but I don't believe it can happen with the nexus.
Click to expand...
Click to collapse
No, this only happens with this specific update with the EVO.
Alright, great! Thanks guys. So since I believe the nexus one already got the offical OTA, did any of you lose ROOT access?
You WILL loose root when you update from an OTA update.
I had a rooted FRF50 and went to the FRF83 update and lost root/custom recovery, everything else was fine though.
I ask that you all forgiveth the newb nature of my question in advance, but if my phone has been rooted, and is currently running FRF50, is there anything I can do to the phone to have it automatically update using OTA? I ask because I received the notice for the OTA update the other day, but being rooted, got a signature mismatch error. (The only reason my phone is rooted is bc I bought it used that way-I wish I could've had it bone stock instead!) I know I can somehow do a manual update, but I'm trying to figure out for further future OTA updates if there's a way that I can have my phone simply automatically apply them.
Well, first off, thanks for hijacking.... AND, I have been doing a bunch of research. You should find the official build of froyo (FRF85B correct?) and manually update it. Just use it unrooted and it'll be easier when an OTA update comes along
So far I've been running my OP3T with stock rom with TWRP recovery and SuperSU to have root. This was mostly because I wanted the Adaway and titanium backup to work. I undid everything so I could update to the latest OxygenOS version, and now I'm on the stock recovery too, but with bootloader still unlocked I believe. I no longer have root after doing the upgrade as far as I can tell, still a bit new to all this flashing, haha. The last time I did this was when the nexus 4 came out
What is the best option for maintaining root while still being able to upgrade smoothly? I'm not against using one of the custom ROMs if that will help, but I do kinda like the stock rom so far!
thanks!
bluesrph said:
So far I've been running my OP3T with stock rom with TWRP recovery and SuperSU to have root. This was mostly because I wanted the Adaway and titanium backup to work. I undid everything so I could update to the latest OxygenOS version, and now I'm on the stock recovery too, but with bootloader still unlocked I believe. I no longer have root after doing the upgrade as far as I can tell, still a bit new to all this flashing, haha. The last time I did this was when the nexus 4 came out
What is the best option for maintaining root while still being able to upgrade smoothly? I'm not against using one of the custom ROMs if that will help, but I do kinda like the stock rom so far!
thanks!
Click to expand...
Click to collapse
This thread should answer all your questions and doubts
https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
saurabh40629 said:
This thread should answer all your questions and doubts
https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
Click to expand...
Click to collapse
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Sent from my OnePlus3T using XDA Labs
bluesrph said:
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Click to expand...
Click to collapse
Dm-verity u can bypass but bootloader one, you can not. Look at the apps, mods section.
bluesrph said:
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
You shouldn't try to flash the partial OTAs while you are rooted and have a custom recovery installed. The partial zip will try to make specific changes in the restricted partitions (/system, /boot, /recovery, etc.) related to the update and prior modifications to these files may cause the update to fail and the phone to brick. You can still use the "Update" tab in the Settings menu to download the update though as OOS will detect root and download the full zip of the update for you. Simply flash the full zip in TWRP, wipe cache/dalvik, then flash SuperSU and you're good to go the next time an update rolls out. Updating by this method (rooting immedately after flashing update) will also prevent OOS from replacing TWRP with the stock recovery again. When you download the update, you'll know if it's the full zip if the file is >1 GB (they're usually ~1.4 GB,, whereas the partial zips are a few hundred MB).
Unlocked bootloader warning screen is cannot be removed without relocked and fully resetting (wiping) the phone. DM-verity warning screen can be removed by following this guide. Make sure that you are flashing the correct firmware for you current version of OOS though, flashing the wrong version can brick you phone.
Hi.
Is it possible to flash TWRP and root with magisk, and then flash relevant stock firmware updates from Samsung using Odin as and when they come?
If so, would flashing said firmwares remove root and TWRP, and/or wipe data? Requiring re flashing TWRP and rooting again after each update?
Basically I'd like to stay relatively stock, just with root and TWRP. But I want to be able to keep the phone up to date without having to use custom ROMs.
And yes, I know once TWRP or root are used Knox is tripped and there's no way to get it back or magically make the warranty valid again. I don't care about that.
beta546 said:
Hi.
Is it possible to flash TWRP and root with magisk, and then flash relevant stock firmware updates from Samsung using Odin as and when they come?
If so, would flashing said firmwares remove root and TWRP, and/or wipe data? Requiring re flashing TWRP and rooting again after each update?
Basically I'd like to stay relatively stock, just with root and TWRP. But I want to be able to keep the phone up to date without having to use custom ROMs.
And yes, I know once TWRP or root are used Knox is tripped and there's no way to get it back or magically make the warranty valid again. I don't care about that.
Click to expand...
Click to collapse
One month no answer, this forum is quite dead
dryspuri said:
One month no answer, this forum is quite dead
Click to expand...
Click to collapse
Yep, it's not great...
Instead of waiting, you could do a search on your own. This stuff is not from yesterday.
The answer is in s8, s8+, note8, s8, s9+ section. Basically someone has discussed it since Sammy introduced 7 days oem lockout, and ways to circumvent it... Those that know, don't feel like repeating endlessly, when time and search do the job.
The rest discuss wallpapers, screen protectors, cases, and justifications why root is no longer necessary (this from North American users, as if they could).
Sent from my phone
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...
Hello all,
I last touched my A71 round feb this year, Rooting official rom.
I'm not sure if things have changed, as would like to install last update August and root it etc.
Can anyone give me some guidance please.
Best wishes
Hi, Exactly what you want to do?
our wishes are mutual.
rifkican said:
Hi, Exactly what you want to do?
our wishes are mut
Click to expand...
Click to collapse
To remove root in order for phone to install official updates, the re-root
Wingchundub said:
To remove root in order for phone to install official updates, the re-root
Click to expand...
Click to collapse
Impossible, once you root it, a fuse is blown and so the phone can never install official updates
Pupet_Master said:
Impossible, once you root it, a fuse is blown and so the phone can never install official updates
Click to expand...
Click to collapse
Your are incorrect, Been doing this many many years.
All i need to do is download official firmware and go from there.
Blown fuse is as regard WARRANTY, Not being able to flash stock rom, then install firmware updates to latest then re-root.
But am looking for an easier way and there is, as did it approx year back, just forgot.
Thank you
Wingchundub said:
Your are incorrect, Been doing this many many years.
All i need to do is download official firmware and go from there.
Blown fuse is as regard WARRANTY, Not being able to flash stock rom, then install firmware updates to latest then re-root.
But am looking for an easier way and there is, as did it approx year back, just forgot.
Thank you
Click to expand...
Click to collapse
He wont be able to use OTA..
Smart Switch or Kies with do it
I'd do manually with ODIN.
Install latest firmware afresh
But i would like to know are the rooting methods different from when A71 first came out and if any links available so i get upto speed.
Best wishes
Done, Installed OTA updates with latest BUJ1 firmware, not losing root and any other files, patching AP with magisk and installed via odin.