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.
Related
Hi - I have rooted my N7000 with no problems and have CWM installed as per the instructions at http://forum.xda-developers.com/showthread.php?t=1446987.
I am new to Android (previously an IOS user) so the rooting/unrooting thing is new to me. I have searched the forums here and on android forums but most of the information I have found winds up being more advanced than the basic questions I have. Please forgive me for this basic question ahead of time.
Once rooted, do I need to manually unroot before upgrading to an official ROM? I am not interested (at this point) in flashing any custom roms - just the official ICS rom when it is released. I understand that if I accept an OTA rom upgrade, it will unroot the device. Is the only consequence of that having to re-root the device?
Thanks!
I dont know wat you make sense to follow Nook Table rooting guide instead of Rooting guide for Galaxy Note. which is sticky thread on development section.( and as much other device section i have seen, here it is most easy n state of the art guide available for note.)
Shrink said:
Once rooted, do I need to manually unroot before upgrading to an official ROM? I am not interested (at this point) in flashing any custom roms - just the official ICS rom when it is released. I understand that if I accept an OTA rom upgrade, it will unroot the device. Is the only consequence of that having to re-root the device?
Thanks!
Click to expand...
Click to collapse
- You need not to unroot to update your device
- Yes you understand right, it will unroot your device
- Re Rooting is not only consequences, Rerooting is not easy after it. b'coz newer ROM is non rootable directly.
So in case of update, you have to use CWM / Mobile Odin instead of Kies/OTA
I have not read detail on link you have mention to root your device.
I just request to check your flash counter (Boot to download mode n check it on Rt upper corner)
Your CWM is working ?
Forgive me - I copied and pasted the wrong link. It was your rooting guide that I followed. CWM is working - I have already created an image of the device as backup.
When I enter download mode, I see no mention of flash counter. Upper right corner is empty. Upper left says:
Odin Mode
Product Name: GT-N7000
Custom Binary Download: No
Current Binary: Samsung Official
Is there some concern?
Thanks again for replying! So when an official rom update is released, if I want to maintain root for the purpose of doing backups, I should not upgrade using Kies or OTA. Otherwise, if I don't care about losing root (and hope that the new ICS rom is rootable) just use the OTA method, correct?
Shrink said:
Product Name: GT-N7000
Custom Binary Download: No
Current Binary: Samsung Official
Is there some concern?
Click to expand...
Click to collapse
Everything's fine with your Note - your binary counter is No (or zero), which means that your warranty is still OK should anything happen to your Note. Binary counter 1 or higher is bad news - warranty is void.
Shrink said:
Thanks again for replying! So when an official rom update is released, if I want to maintain root for the purpose of doing backups, I should not upgrade using Kies or OTA. Otherwise, if I don't care about losing root (and hope that the new ICS rom is rootable) just use the OTA method, correct?
Click to expand...
Click to collapse
I'd forget about OTA or Kies for two reasons:
1. you lose root and all the fun it brings
2. you wait until someone (either Samsung or your provider) sees fit to deliver the update - the same update is available here a day or two after its first release. In other words, you are in better hands here at XDA.
I will stick with here then.
I am disabling Auto update under Software Updates. That will only prevent OTA rom updates won't it?
Thanks again!
Shrink said:
I will stick with here then.
I am disabling Auto update under Software Updates. That will only prevent OTA rom updates won't it?
Thanks again!
Click to expand...
Click to collapse
Yes, it will. Welcome to the fold.
If you followed guide for note thn itz ok, b'coz that link u shown was totally wrong. I read your data regarding counter n it is perfaxt, as of now nothing to worry,just atay tuned on xda, when you want to keep root use cwm to update, otherwise kies/ota.
Sent from my GT-N7000 using xda premium
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
After reading dozens of threads I'm at a loss.
1. Can I root?
2. If I root, is my phone still going to work? Or will it become the latest victim of my Beowolf.
Odin twrp then install unikernel inside twrp. Will trip Knox so Samsung pay won't work anymore.
tyrone1 said:
Odin twrp then install unikernel inside twrp. Will trip Knox so Samsung pay won't work anymore.
Click to expand...
Click to collapse
Ok thanks. Not concerned with Sam pay. Citibank and Wells aren't supported.
It works with Citibank cards
stncldtex said:
After reading dozens of threads I'm at a loss.
1. Can I root?
2. If I root, is my phone still going to work? Or will it become the latest victim of my Beowolf.
Click to expand...
Click to collapse
I finally found a routine and the right files needed to successfully acquire root, twrp, and custom ROM. Although, the only custom ROM Iv'e been able to boot and setup with all T-Mobile services intact and even the finger print security feature working, is the "OZOP_EDGE_v11_DOJ7.zip, thanks to stangdriver44".
Just remember you should back up the EFS and backup the phone using Samsung smart switch. If you need help, pm me. Id lay out the exact steps I took to get root originally and what it took to get out of a bricked phone, and finally to root and install a custom ROM.
I will type up what I did later today or tomorrow and post it in case anyone does the same thing to gets bootloops and bricks.
I have to attend to other chores now before I go back to work tomorrow, since I spent every evening for the last week and all day and night yesterday, trying to bring this phone out of brick.
chevy383surfing
tyrone1 said:
It works with Citibank cards
Click to expand...
Click to collapse
Sorry Capital One not Citi.
stncldtex said:
After reading dozens of threads I'm at a loss.
1. Can I root?
2. If I root, is my phone still going to work? Or will it become the latest victim of my Beowolf.
Click to expand...
Click to collapse
chainfire's systemless root BETA v2.61 works flawlessly: http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
pm me.
Id like to know the steps you took to root your s6. pm me whenever possible. Thanks.
chevy383surfing said:
I finally found a routine and the right files needed to successfully acquire root, twrp, and custom ROM. Although, the only custom ROM Iv'e been able to boot and setup with all T-Mobile services intact and even the finger print security feature working, is the "OZOP_EDGE_v11_DOJ7.zip, thanks to stangdriver44".
Just remember you should back up the EFS and backup the phone using Samsung smart switch. If you need help, pm me. Id lay out the exact steps I took to get root originally and what it took to get out of a bricked phone, and finally to root and install a custom ROM.
I will type up what I did later today or tomorrow and post it in case anyone does the same thing to gets bootloops and bricks.
I have to attend to other chores now before I go back to work tomorrow, since I spent every evening for the last week and all day and night yesterday, trying to bring this phone out of brick.
chevy383surfing
Click to expand...
Click to collapse
andrey1186 said:
Id like to know the steps you took to root your s6. pm me whenever possible. Thanks.
Click to expand...
Click to collapse
I will get a write up of the steps. I'll pm you tomorrow afternoon. I planned to do it tonight, but I have a case of the Mondays!
muniz_ri said:
chainfire's systemless root BETA v2.61 works flawlessly: http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
How do you flash it?
stncldtex said:
How do you flash it?
Click to expand...
Click to collapse
Install twrp on stock oj7 then flash supersu v2.61 in twrp. that's it.
muniz_ri said:
chainfire's systemless root BETA v2.61 works flawlessly: http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
Does this trip KNOX?
chip.hughes said:
Does this trip KNOX?
Click to expand...
Click to collapse
of course
stncldtex said:
How do you flash it?
Click to expand...
Click to collapse
You'd have to setup Cygwin software to make the zip an 'Odin flashable .tar.md5 type file', which I have not had time to play with, in order to flash supersu zip files onto the samsung phones.
I am working on a worksheet right now explaining what I had to do to install 5.1.1 firmware and root the phone. I am still looking back to remember exactly how I unlocked the bootloader. I did have to use an android terminal to map out the twrp recovery manual on the phone itself. I do know it would wise for anyone interested in this to backup the EFS before anything. I had to download a specific windows DOS software that does it in a couple seconds and stores it on your computer. It works for a number of other phones as well. Also need to download the newest Odin 3.10.7 software in order to work with 5.1.1 firmware without any problems. Also need to do a backup of whole phone with samsung smart switch "takes place of Kies software now". When I get home tonight I will get names and locations of everything and inform everyone. If you download the wrong DOJ7 software or firmware you'll mess up your device. It took me a week to find the right software downloads related to 5.1.1 in order to make everything work right. And I did everything within 15 minutes. Once I figured out the routine.
Once you update to 5.1.1 I know of no way to downgrade.
I do recommend going over to serio22's post -[Firmware][Bootloader & Modems][Odin] - G920T - DOJ7-
And download DOJ7 BL and DOJ7 modem and G920TUVU3DOJ7 (firmware). Download Chainfire's latest beta super su.
You can just flash unikernel to get root.
Possibly any of the other kernels too
stncldtex said:
After reading dozens of threads I'm at a loss.
1. Can I root?
2. If I root, is my phone still going to work? Or will it become the latest victim of my Beowolf.
Click to expand...
Click to collapse
Yes you can root .. by flashing unikernel .. and phone will still be working ...
Tried flashing Uni through Odin with no luck. I get this in Odin.
Get PIT for mapping.
Write operation failed.
Any idea's?
stncldtex said:
Tried flashing Uni through Odin with no luck. I get this in Odin.
Get PIT for mapping.
Write operation failed.
Any idea's?
Click to expand...
Click to collapse
I recommend you root with the latest Supersu beta v2.62-3 zip. It will patch the stock kernel which was designed for your specific build unlike the unikernel. Just flash via twrp.
muniz_ri said:
I recommend you root with the latest Supersu beta v2.62-3 zip. It will patch the stock kernel which was designed for your specific build unlike the unikernel. Just flash via twrp.
Click to expand...
Click to collapse
TWRP gives off the same error.
stncldtex said:
TWRP gives off the same error.
Click to expand...
Click to collapse
More accurately trying to Odin TWRP.
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...