Hello. I've been snooping this forum for a while, and so i rooted my Nothing Phone 1. However it was back when 1.1.0 was a thing and didn't update to newer versions (mainly because of it's reviews). However recently i've been hearing positive feedback on 1.1.3 version and so i decided to give it a shot. But how could i do such thing if i'm rooted?
I know i would soft-brick my device if i would let OTA pass and install. This way i would probably need a full OTA rom and flash it manually somehow. Also, if someone know, downgrade guide would be awesome too (in case i will have issues with the new update).
Pheggas said:
Hello. I've been snooping this forum for a while, and so i rooted my Nothing Phone 1. However it was back when 1.1.0 was a thing and didn't update to newer versions (mainly because of it's reviews). However recently i've been hearing positive feedback on 1.1.3 version and so i decided to give it a shot. But how could i do such thing if i'm rooted?
I know i would soft-brick my device if i would let OTA pass and install. This way i would probably need a full OTA rom and flash it manually somehow. Also, if someone know, downgrade guide would be awesome too (in case i will have issues with the new update).
Click to expand...
Click to collapse
You will have this tuto if you want to update by Sideload the OTA zip
[GUIDE][HowTo]Pushing an OTA.zip Update with ADB Sideload - Updated 26-07-2022
Can't help you unfortunately, but let me know, after you manage, if your vibration intensity went down at all after the update or if it's all just my brain playing tricks on me.
FWIW, I don't have any issues with the latest version, except maybe lower vibration intensity, though that might just be because I started wearing a case more often.
Also the updates apparently have different features in different regions (for example, EEA had optimized battery ever since I first received the phone with version 1.1.2). They don't document the differences so it's possible other regions are buggy-er
This is how I managed to update a rooted Nothing Phone 1 (EU).
1. Disable all Magisk modules.
2. Restore images in Magisk
3. Install the OTA update through Updater in settings. Do NOT reboot when finished.
4. Install to inactive slot in Magisk
5. When that is finished, reboot. Done!
Pheggas said:
Hello. I've been snooping this forum for a while, and so i rooted my Nothing Phone 1. However it was back when 1.1.0 was a thing and didn't update to newer versions (mainly because of it's reviews). However recently i've been hearing positive feedback on 1.1.3 version and so i decided to give it a shot. But how could i do such thing if i'm rooted?
I know i would soft-brick my device if i would let OTA pass and install. This way i would probably need a full OTA rom and flash it manually somehow. Also, if someone know, downgrade guide would be awesome too (in case i will have issues with the new update).
Click to expand...
Click to collapse
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com
Add offlineOTAUpgrade from activities tab (like nova launcher), and download the full rom, simply update, and unfortunately it reboots before magisk can install to unused slot, so Fastboot boot rooted boot img and do a full install
Pho3nX said:
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you. Unfortunately, that guide is missing all the commands and clearness.
Pheggas said:
Thank you. Unfortunately, that guide is missing all the commands and clearness.
Click to expand...
Click to collapse
There only one command "for update from root" and you can't be more clear in the step lol
So it's normal to don't found "all the commands" because there only one command to enter.
If you search a guide for root the first time, it's exactly the same thing but first your bootloader must be unlocked (all your date will be erased)
What is your problem ? Where are you blocked ?
Pho3nX said:
There only one command "for update from root" and you can't be more clear in the step lol
So it's normal to don't found "all the commands" because there only one command to enter.
If you search a guide for root the first time, it's exactly the same thing but first your bootloader must be unlocked (all your date will be erased)
What is your problem ? Where are you blocked ?
Click to expand...
Click to collapse
Hi @Pho3nX (and @Pheggas )
It's the same "my" problem...
I'd like to update me NP1 (rooted), waiting next custom roms that unfortunately are not ready
I'm not so smart with modding and we appreciate some detailed info/guide, step by step, with full commands to write, avoiding dangerous bricks...
I've stored in a folder my first boot.img and the magisk.img but I'm afraid to do some mistake with CMD strings...
Thanks for Your cooperation and... patience...
Ciao
notexcited said:
This is how I managed to update a rooted Nothing Phone 1 (EU).
1. Disable all Magisk modules.
2. Restore images in Magisk
3. Install the OTA update through Updater in settings. Do NOT reboot when finished.
4. Install to inactive slot in Magisk
5. When that is finished, reboot. Done!
Click to expand...
Click to collapse
this worked great for me the last few times, but this method no longer works for me after I installed version 1.1.4. can someone help me?
+1 for a detailed list of possible methods to update when rooted.
Sib64 said:
You will have this tuto if you want to update by Sideload the OTA zip
[GUIDE][HowTo]Pushing an OTA.zip Update with ADB Sideload - Updated 26-07-2022
Click to expand...
Click to collapse
But i shouldn't update with OTA packages when i'm rooted. There's risk of brick and tutorials on any device guides to update via flashing full package.
Pheggas said:
But i shouldn't update with OTA packages when i'm rooted. There's risk of brick and tutorials on any device guides to update via flashing full package.
Click to expand...
Click to collapse
Wait for full package and follow the same tutorial
Related
Is it a misconception that an OTA update received on your phone will not install if you have a custom recovery? I just read an article on how an update will fail if you are running a custom recovery. However, when I updated from 4.2.1 to 4.2.2.. All I did was accept the OTA update notification I got on my phone and it installed fine through the TWRP recovery I had flashed on my Nexus.
It won't install automatically, as you found out. It has been said many times over that you are easily able to install the downloaded OTA yourself in your custom recovery.
peedub said:
It won't install automatically, as you found out. It has been said many times over that you are easily able to install the downloaded OTA yourself in your custom recovery.
Click to expand...
Click to collapse
Sorry maybe I didnt word my post correctly but what I am trying to say that it does install automatically. I got the update notification on my phone and it installed fine.
Rizy7 said:
Sorry maybe I didnt word my post correctly but what I am trying to say that it does install automatically. I got the update notification on my phone and it installed fine.
Click to expand...
Click to collapse
Yes its not new info as this has been discussed before in a number of threads back when the last OTA first came out.
Had a similar question, and in the spirit of not starting a new thread...
was this OTA just lucky in that regard?
ie. I want to root (for ads.. no other compelling reason for me.. I'm happy otherwise).. and would like to do so in a way that makes me as forward compatible for future OTA updates (ie. don't want to have to wipe data).
since I'm not looking for lots of typical custom recovery features, I'm wondering if I should even bother with a custom recovery.. and/or if any are likely to allow me to accept OTAs directly OTA.
thanks!
zim2dive said:
Had a similar question, and in the spirit of not starting a new thread...
was this OTA just lucky in that regard?
ie. I want to root (for ads.. no other compelling reason for me.. I'm happy otherwise).. and would like to do so in a way that makes me as forward compatible for future OTA updates (ie. don't want to have to wipe data).
since I'm not looking for lots of typical custom recovery features, I'm wondering if I should even bother with a custom recovery.. and/or if any are likely to allow me to accept OTAs directly OTA.
thanks!
Click to expand...
Click to collapse
Rooting your phone does not keep you from being able to update it. If all else fails you can always download the OTA and update it through your custom recovery. Which is what a lot of people did instead of waiting for Google to push it to their phone, myself included. Also you don't have to have a custom recovery installed if you don't want to after you root the phone. You could use one of the toolkit's to root it and it will install a temporary custom recovery used just for rooting then remove it when its done. Or just flash the stock recovery image after you root if you do it another way. If you go through the process of rooting I would recommend unlocking the bootloader too while you are at it but be warned this will erase all your memory so backup first.
Here's my Cheat Sheet ! This is the same procedure I used a while back with N910VVRU2CPD1 . I just updated the thread to work with the newer package.
1. Odin SamMobile N910VVRU2BPA1
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CQI2
( ! System and Cache only ! )
Your mileage may vary.
Before I install my personal apps I remove as much Verizon, Samsung and Google spyware as possible.
-------------------------------------------------------------------------------------------------
EDIT: I was able to skip the recommended rooting and unlocking of 5.1.1 and make the jump I described.
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
Hyperlinks are in the text to most of what's needed.
Credit AstonsAndroid I found it HERE
I keep seeing people saying there is a way to just flash TWRP and Magisk and you're done. I'd like to avoid SuperSU and the other root methods if possible. How would that work with your updated guide? Thanks
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
RootMyNote4Please said:
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
Click to expand...
Click to collapse
I'm not sure if it was spyware or what. but my phone performance better after cleaning out that folder.
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
lodilovesmuffins said:
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
Click to expand...
Click to collapse
Kingroot needs to connected to root. I never seen it work without a connection. N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar brakes wifi but you get it back with N910VVRU2CPD1_StockRestore.tar, I dont know why. It just works
RootMyNote4Please said:
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
Click to expand...
Click to collapse
My best guess now is it's some kind of provisioning issue that is cleaned up. Some of the files deleted you may actually need some day.
does this require the developer version? btw how do i backup
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
RootMyNote4Please said:
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
Click to expand...
Click to collapse
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
kevintm78 said:
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
Click to expand...
Click to collapse
That's weird. I flashed SuperSU but it didn't show up in the apps and when I tried to use Flashfire it said I didn't have root.
Got there. SuperSU had an error message when I tried to install it the 1st time after flashing full system. So I rebooted and installed again. Now Flashfire crashes and won't open. Switched to Flashify and it seems to work ok.
Edit - Stuck here for now. Flashify can't seem to find the CQI2 file and I still haven't been able to get Flashfire to work. Tried an older version and still crashes when it checks to see if I have the pro version or not.
In case someone else has the same problem with Flashfire, it's because the program expired April 1st, 2018. Turn the date back on your phone and it will load.
Finally completed it!!!
Ok, so the things I learned from my trials and errors.
1) DON'T flash the kernal and SU after you root with the N4 fix. I did this the 1st 15 times and could never get Flashfire to work later on. So skip all of the stuff in that post after you flash TWRP. Then flash the next firmware step.
2) Uncheck auto time and date on your phone and roll it back to before 4/1/18 to get Flashfire to work.
I'm sure there are some more things and I'll add whatever else I think can help the next guy along. Good luck! And thanks for the guide doc!
Note: Did the phone icon on your lock screen disappear as well when you were done? The camera is there on the bottom right like normal, but the phone is gone on the bottom left and it displays the charging info there now.
Thanks for this - it was helpful to make clear that in my mind that despite what other guides say, there is no need to unlock a Lollipop bootloader with a Lollipop kernel + ROM first, and that we can boot a Lollipop kernel + ROM with a Marshmallow bootchain and unlock the Marshmallow bootloader from the get-go.
I tracked down the CQI2 full Odin and I made hybrid Odins that get you "rooted on N910VVRU2CQI2" in fewer steps, following hsbadr's file naming scheme:
N910VVRU2BPA1_N910VVRU2CQI2_FullFirmware.tar.md5: MM CQI2 bootchain/firmware/modem, LL BPA1 ROM/kernel/recovery
N910VVRU2CQI2_StockRestore.tar: MM CQI2 ROM/kernel (no recovery - TWRP isn't overwritten)
These should be fine as drop-in replacements for the files mentioned in steps 2 and 5 of your guide.
Using these obviously means that you are unlocking the CQI2 aboot instead of the CPD1 aboot in step 3 while temprooted, and - importantly - step 7 is unnecessary to get to a CQI2 ROM, which is good because Flashfire is now expired :3
I doubt there's much of a real benefit to being on the newer aboot, but hey, why not.
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
lodilovesmuffins said:
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
Click to expand...
Click to collapse
No, this will work with both versions of the verizon note 4.
kevintm78 said:
No, this will work with both versions of the verizon note 4.
Click to expand...
Click to collapse
Ok, thank you very much. I'll try and root my phone with this tutorial now.
Please help!!!!
I followed this link because its supposed to be a way to downgrade from 6.1.0 to 5.1.1 so I can unlock boot loader. However, these instructions make no sense to me. Can someone PLEASE help me. I've been searching and searching for a way to root my note 4 (N910VVRS2CQA1) and can't seem to find a way. I've never done this before so I'm pretty clueless. When I read these instructions, I just don't understand what I'm supposed to be doing. A lot of this tech lingo means nothing to me unfortunately. I'm starting to thing I should just give up the idea of rooting this Note 4 that's getting slower and slower and just get a new one. I don't really want to though bc I love the fact that you can replace the battery. It'd be much easier to just root and upgrade.....well, easier if I actually knew how.
Dear all!
Can anyone confirm if this is working when going from 9.0.17 to 10?
It always worked for me when I updated Android 9 versions but I'm not sure if it's working when going from 9.0.17 to 10.
Funk Wizard said:
Flashing Instructions
Update Process for Rooted Users
1. Magisk Manager > Tap "Uninstall" > Tap "Restore Images" (DO NOT REBOOT)
2. Now Run the System update to download and install the full OTA zip (DO NOT REBOOT)
3. Close all background apps
4. Open Magisk > Tap "Install" > Tap "install" again > Tap "Install to Inactive/Second Slot (After OTA)"
5. Finally tap Reboot after Magisk installation is complete.
Ref: Magisk Tutorials | OTA Installation
Click to expand...
Click to collapse
Thanks in advance!
I did this way and I had issues with freezing apps and non-working wifi.
meciu99 said:
I did this way and I had issues with freezing apps and non-working wifi.
Click to expand...
Click to collapse
How did you solve the problem?
Full Reset and Clean Install?
There is a topic that describe exacly what you must do. You can find it here.
Deurklink73 said:
There is a topic that describe exacly what you must do. You can find it here.
Click to expand...
Click to collapse
Thank you, I already know the thread.
If you would have read my thread title it says that I'm rooted with Magisk and that I have NO TWRP in place, so I'm under different conditions as the procedure described in your linked thread. But thanks anyway for your reply.
Anyone else who is on my setup and updated via my quoted procedure?
xfxx said:
Thank you, I already know the thread.
If you would have read my thread title it says that I'm rooted with Magisk and that I have NO TWRP in place, so I'm under different conditions as the procedure described in your linked thread. But thanks anyway for your reply.
Anyone else who is on my setup and updated via my quoted procedure?
Click to expand...
Click to collapse
Just do it it's the officiel procedure to update while keeping Magisk. The worst that can happen is losing Magisk, and that can be solved easily via fastboot. No need to hesitate for days.
OK guys.
I did the update like stated in my first post.
Everything went fine, no problems whatsoever. ??
xfxx said:
OK guys.
I did the update like stated in my first post.
Everything went fine, no problems whatsoever. ??
Click to expand...
Click to collapse
Out of curiosity, did you get get OOS10 update via the official OTA or download it? I haven't gotten the OTA update yet.
m4570d0n said:
Out of curiosity, did you get get OOS10 update via the official OTA or download it? I haven't gotten the OTA update yet.
Click to expand...
Click to collapse
I downloaded it.
Just google the filename and take one of the AFH mirrors!
Be cautious and control that MD5 hash is correct.
I have a OnePlus 6t (T-Mobile/fajita variant). My problem is that Android 10 isn't compatible with twrp and I've gone through the trouble of rooting my phone just for an automatic update restart my device out of nowhere and update it from Pie to Android 10. Which means I have to use MSM to reinstall Pie, unlock bootloader, flash twrp and magisk, redownload all my apps. I feel as though there is a way I can use AdGuard or another similar firewall to block the updater from even being able to download the update but I'm not sure what to look for. Any help would be greatly appreciate, I would normally ever make a post but haven't been able to find an answer anywhere so I'm sorry if this has been answered before. I have already blocked automatic updates through developer tools as well.
Gonna bump one time, if nobody has any advice I'll delete thread.
ennischris93 said:
I have a OnePlus 6t (T-Mobile/fajita variant). My problem is that Android 10 isn't compatible with twrp
Click to expand...
Click to collapse
Find Mauronofrio's TWRP and instructions here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
During TWRP install, it offers to leave system partition unmodified, stating something like "Easier to receive official updates." which I think I did, but ALSO I switched my Tmo branded to International from I believe here:
https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307
I don't recall every getting any kind of update without permission.
More recently, I flashed Omega Kernel to have guitardedhero's Dolby Atmos sound mod (but don't think this affected the update method) from here:
https://forum.xda-developers.com/oneplus-6t/development/kernel-aoxp-kernel-1-0-t3905381
Good luck.
pbergonzi said:
Find Mauronofrio's TWRP and instructions here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
During TWRP install, it offers to leave system partition unmodified, stating something like "Easier to receive official updates." which I think I did, but ALSO I switched my Tmo branded to International from I believe here:
https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307
I don't recall every getting any kind of update without permission.
More recently, I flashed Omega Kernel to have guitardedhero's Dolby Atmos sound mod (but don't think this affected the update method) from here:
https://forum.xda-developers.com/oneplus-6t/development/kernel-aoxp-kernel-1-0-t3905381
Good luck.
Click to expand...
Click to collapse
I appreciate your input, I'll see what I can do.
I'm on the international version I used an old familiar method thats worked on previous android builds. I take no responsibility if you have a issue of any kind. I was on PIE and didn't want the update notification driving me nuts because 10 was in it's early stages. I used an old version of rom toolbox, opened App manager and scrolled down to find system update APK (s). There were 2 of them I only needed to freeze the 1st one.
Good luck
(Edit fixed typos)
The way i used to block update notification and automatic update. It uses adb commands. It works without root.
1. Usb debugging on
2. Computer with adb drivers
Open command window in pc and connect your oneplus and run these commands one by one.
Commands are
Adb devices (for checking device is connected)
Adb shell
pm uninstall -k --user 0 com.oneplus.opbackup
exit
This prevent download and notification. But make sure you uncheck or disable automatic download in system update setting.
spider451 said:
I'm on the international version I used an old familiar method thats worked on previous android builds. I take no responsibility if you have a issue of any kind. I was on PIE and didn't want the update notification driving me nuts because 10 was in it's early stages. I used an old version of rom toolbox, opened App manager and scrolled down to find system update APK (s). There were 2 of them I only needed to freeze the 1st one.
Good luck
(Edit fixed typos)
Click to expand...
Click to collapse
Do you remember what those two apks are called? I tried looking up what they would be before I even started this thread but couldn't find the names. I'm also considering flashing the international version as well if all else fails.
ennischris93 said:
Do you remember what those two apks are called? I tried looking up what they would be before I even started this thread but couldn't find the names. I'm also considering flashing the international version as well if all else fails.
Click to expand...
Click to collapse
Yes it's system update.
Hi XDA community,
I will receive my new OnePlus Pro 8 tomorrow.
This will be my first OnePlus phone and it will likely be the North American version.
Primarily, I would like to unlock the bootloader and root the phone, additionally also have the Dual-sim functionality enabled.
I don't have a lot of experience with rooting, but can follow steps and instructions
1) Should I start the new phone let it update all the way to oxygen OS 11 and than follow steps to unlock the bootloader and root the phone and than transfer my data? - Will this process be more complicated than doing it with Oxygen OS 10.?
2) Once the phone is rooted, can I transfer data from my old phone through the USB/Phone/data transfer apps so it gets setup automagically ?
3) Does TWRP work with OS 11 ? if not is there an update schedule for it?
4) Does Dual Sim for NA phones work with Oxygen OS 10 or is it enabled only at Oxygen OS 11 ?
Any things else that I should be aware of? (this process or the phone in general as well?)
Thank you all
DV
Peace.
dvartak said:
Hi XDA community,
I will receive my new OnePlus Pro 8 tomorrow.
This will be my first OnePlus phone and it will likely be the North American version.
Primarily, I would like to unlock the bootloader and root the phone, additionally also have the Dual-sim functionality enabled.
I don't have a lot of experience with rooting, but can follow steps and instructions
1) Should I start the new phone let it update all the way to oxygen OS 11 and than follow steps to unlock the bootloader and root the phone and than transfer my data? - Will this process be more complicated than doing it with Oxygen OS 10.?
2) Once the phone is rooted, can I transfer data from my old phone through the USB/Phone/data transfer apps so it gets setup automagically ?
3) Does TWRP work with OS 11 ? if not is there an update schedule for it?
4) Does Dual Sim for NA phones work with Oxygen OS 10 or is it enabled only at Oxygen OS 11 ?
Any things else that I should be aware of? (this process or the phone in general as well?)
Thank you all
DV
Peace.
Click to expand...
Click to collapse
1. I would prefer to unlock the phone first and than boot twrp and flash magisk. After you got root update the system and install magisk to inactiv slot.
2. I don't know.
3. Nope.
4. Should also work with OOS 10.
Thank you for your reply..
Kollachi said:
1. I would prefer to unlock the phone first and than boot twrp and flash magisk. After you got root update the system and install magisk to inactiv slot.
2. I don't know.
3. Nope.
4. Should also work with OOS 10.
Click to expand...
Click to collapse
Thanks for your reply
Is there a forum thread for how I can unlock the bootloader and to perform root, the XDA forum threads while very resourceful are a bit overwhelming as there seem to be multiple methods of achieving root.
I am not planning on installing customROMS as yet, just want the phone to be unlocked and so I can enable the colour filter, installing gcam etc for now.
Cheers,
DV
dvartak said:
Thanks for your reply
Is there a forum thread for how I can unlock the bootloader and to perform root, the XDA forum threads while very resourceful are a bit overwhelming as there seem to be multiple methods of achieving root.
I am not planning on installing customROMS as yet, just want the phone to be unlocked and so I can enable the colour filter, installing gcam etc for now.
Cheers,
DV
Click to expand...
Click to collapse
I have a couple in the guides section..have a look. So long as you follow it correctly you should be fine.
One for the bootloader.
One for updating, rooting and payload dumper.
A few more questions...
dladz said:
I have a couple in the guides section...have a look. So long as you follow it correctly you should be fine.
One for the bootloader.
One for updating, rooting and payload dumper.
Click to expand...
Click to collapse
Do you mind pasting the links here, I have managed to get the bootloader unlocked using fastboot.
(NVM, I think I found your threads oneplus-8-pro/how-to/root-uk-eu-patched-magisk-boot-img-t4175033 & )
My model is IN2025
OS: 10.5.10.IN11AA
I wanted to know,
1) OxyOS updater is prompting that there is an update to Oxygen OS 11.IN11AA
Can I update to OxyOS 11 and still keep the bootloader unlocked ?
"It displays that OEM unlock is detected, system will download the full upgrade package, please backup data...etc."
2) Should I root my phone now and later will I be able to upgrade / flash to Oxygen OS 11 ? -North-American market requires OS 11 for dual sim
Where can I find the appropriate files to get make a 'patch' using payload for this version (10.5.10.IN11AA) ?
Thank you
dvartak said:
Do you mind pasting the links here, I have managed to get the bootloader unlocked using fastboot.
(NVM, I think I found your threads oneplus-8-pro/how-to/root-uk-eu-patched-magisk-boot-img-t4175033 & )
My model is IN2025
OS: 10.5.10.IN11AA
I wanted to know,
1) OxyOS updater is prompting that there is an update to Oxygen OS 11.IN11AA
Can I update to OxyOS 11 and still keep the bootloader unlocked ?
"It displays that OEM unlock is detected, system will download the full upgrade package, please backup data...etc."
2) Should I root my phone now and later will I be able to upgrade / flash to Oxygen OS 11 ? -North-American market requires OS 11 for dual sim
Where can I find the appropriate files to get make a 'patch' using payload for this version (10.5.10.IN11AA) ?
Thank you
Click to expand...
Click to collapse
Yes you can
Yes that's fine
Easiest way is whatever you like .
You can either root now then take the update and then OTA install magisk patched or just boot the magisk patched after and then directly install
Sorry, I still have some more questions..
dladz said:
Yes you can
Yes that's fine
Easiest way is whatever you like .
You can either root now then take the update and then OTA install magisk patched or just boot the magisk patched after and then directly install
Click to expand...
Click to collapse
I updated to OS11.IN11AA to enable Dual Sim first.
I guess I can try rooting now. Sorry I still have a few queries:
1)
In your instructions you suggest extracting 'your own' boot.img using the payload_dumper.
My phone (thanks to the OEM unlock) has downloaded a large 2GB+ zip file on the phone, should I use that payload.bin to extract the boot.img
or
the one on the oneplus website will work as well? - They appear to be the same but would like to know if there is a difference.
From the oneplus Website: OnePlus8ProOxygen_15.O.30_OTA_0300_all_2010031617_2198430880804411.zip
From the phone: OnePlus8ProOxygen_15.O.30_OTA_0300_all_2010031617_f9ca0bfd1b.zip
2)
I installed MagiskManager from the link in your thread (Preferred magisk manager- https://mega.nz/file/LU9U3aSC#EFJTOK...ejzi-VyUa3nQq8)
There weren't any updates till I selected the stable channel and than canary again. I have installed the whatever updates, it showed:
It now reads:
Magisk (latest): 1469b82a
Installed: N/A <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Why does it show N/A ?, will this change after the rooting process ?
Ramdisk: Yes
A/B: yes
SAR: yes
Crypto: File
Manager (latest) 1469b82a(315)(14)
installed: 1469b82a(315)
Does this seem correct?
You have been really awesome !
Cheers,
DV
dvartak said:
I updated to OS11.IN11AA to enable Dual Sim first.
I guess I can try rooting now. Sorry I still have a few queries:
1)
In your instructions you suggest extracting 'your own' boot.img using the payload_dumper.
My phone (thanks to the OEM unlock) has downloaded a large 2GB+ zip file on the phone, should I use that payload.bin to extract the boot.img
or
the one on the oneplus website will work as well? - They appear to be the same but would like to know if there is a difference.
From the oneplus Website: OnePlus8ProOxygen_15.O.30_OTA_0300_all_2010031617_2198430880804411.zip
From the phone: OnePlus8ProOxygen_15.O.30_OTA_0300_all_2010031617_f9ca0bfd1b.zip
2)
I installed MagiskManager from the link in your thread (Preferred magisk manager- https://mega.nz/file/LU9U3aSC#EFJTOK...ejzi-VyUa3nQq8)
There weren't any updates till I selected the stable channel and than canary again. I have installed the whatever updates, it showed:
It now reads:
Magisk (latest): 1469b82a
Installed: N/A <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Why does it show N/A ?, will this change after the rooting process ?
Ramdisk: Yes
A/B: yes
SAR: yes
Crypto: File
Manager (latest) 1469b82a(315)(14)
installed: 1469b82a(315)
Does this seem correct?
You have been really awesome !
Cheers,
DV
Click to expand...
Click to collapse
Hey,
1.) Yep that's absolutely fine, I tend to use oxygen updater as it's been absolutely flawless up until now and it won't allow you to download a firmware not compatible with your device.
Wherever you choose the numbers you've shown seem good to me, but id I had to choose I'd go with oxygen updater.
2.) Some people have had a lot more luck with the beta channel, so long as you have the install/update buttons then you're ready to patch the boot.img and go ahead and boot it using Fastboot.
Don't worry about N/A that just states that magisk_patched isn't there yet, which is normal.
So at this point, you're welcome to stick with stable but I couldn't recommend it as I've not done this myself, I've only had luck with canary but others have had luck with beta.. I'd recommend one of them channels, changing back to canary may now show the buttons that were missing..
If not then beta.
There are some troubleshooting steps at the end of the guides at the bottom. As well as all the files which I used.
Let me know how you get on
dladz said:
Hey,
2.) Some people have had a lot more luck with the beta channel, so long as you have the install/update buttons then you're ready to patch the boot.img and go ahead and boot it using Fastboot.
Don't worry about N/A that just states that magisk_patched isn't there yet, which is normal.
So at this point, you're welcome to stick with stable but I couldn't recommend it as I've not done this myself, I've only had luck with canary but others have had luck with beta.. I'd recommend one of them channels, changing back to canary may now show the buttons that were missing..
If not then beta.
There are some troubleshooting steps at the end of the guides at the bottom. As well as all the files which I used.
Let me know how you get on
Click to expand...
Click to collapse
Thanks again for all your help!
So I believe, the channel display when first opened did not show any install / update buttons but the settings showed channel: Canary.
I believe I switched to stable and the buttons showed up (i did not install than), after which I switched channels to canary and than installed.
When I search for the "1469b82a" and magisk it shows this as a Update to Canary channel (3days ago) https://github.com/topjohnwu/magisk_files/blob/canary/notes.md
I hope I am on the right track..
-------------------------------
UPDATE: So I think it has worked,
It seems I am rooted now, I have installed Titanium and bunch of other stuff that needs root.
(but I think I may have goofed up and ended up mixing your two solutions)
It was installed in 'b - drive/section'.
fastboot flash boot magisk_patched.img <(This is different from your step 4, where you do fastboot boot magisk_patched)
(I am hoping this did not goof things up, I misread )
It flashed just on 'b' - drive.
I did not flash in both 'a' and 'b'.
I also did'
"
5. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings.
6. Select Direct install (recommended)
"
When I open Magisk Manager now, I see installed 1469b82a (21101) < same as the latest
I also have the "Uninstall Magisk button" showing which wasn't before. and settings shows me many more options (super user, magisk hide etc.)
2) Also what does Magisk hide do?,
> I have read many bank apps wont install due to rooting, will that help?
Thanks for being so patient and answering all questions !
dvartak said:
Thanks again for all your help!
So I believe, the channel display when first opened did not show any install / update buttons but the settings showed channel: Canary.
I believe I switched to stable and the buttons showed up (i did not install than), after which I switched channels to canary and than installed.
When I search for the "1469b82a" and magisk it shows this as a Update to Canary channel (3days ago) https://github.com/topjohnwu/magisk_files/blob/canary/notes.md
I hope I am on the right track..
-------------------------------
UPDATE: So I think it has worked,
It seems I am rooted now, I have installed Titanium and bunch of other stuff that needs root.
(but I think I may have goofed up and ended up mixing your two solutions)
It was installed in 'b - drive/section'.
fastboot flash boot magisk_patched.img <(This is different from your step 4, where you do fastboot boot magisk_patched)
(I am hoping this did not goof things up, I misread )
It flashed just on 'b' - drive.
I did not flash in both 'a' and 'b'.
I also did'
"
5. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings.
6. Select Direct install (recommended)
"
When I open Magisk Manager now, I see installed 1469b82a (21101) < same as the latest
I also have the "Uninstall Magisk button" showing which wasn't before. and settings shows me many more options (super user, magisk hide etc.)
2) Also what does Magisk hide do?,
> I have read many bank apps wont install due to rooting, will that help?
Thanks for being so patient and answering all questions !
Click to expand...
Click to collapse
That's ok you just flashed it twice.
Reason for the boot and not flash is due to the fact that boot images can always go wrong,, bad copy or just corruption. But if you're rooted then you're all good
Magisk hide attempts to hide itself from apps that works otherwise detect it, meaning you can go ahead and use Google pay our your banking apps.
In theory anyway, but some apps have other ways of detecting root and thus it won't work.
Up until now I've been ok.
I see..
Ah I see, Thanks again. Google pay complains about root, but my other Bank apps seem fine so far. I'll try my luck with hide magisk.
I suppose next time the phone updates, I will lose root as the active partition will switch ?
The only odd thing that has happened is the I have an extra/duplicate icon for the Android Files App. I don't know how to get rid of it...but it's not a big issue.
Thanks again for your help!
Cheers,
DV
dvartak said:
Ah I see, Thanks again. Google pay complains about root, but my other Bank apps seem fine so far. I'll try my luck with hide magisk.
I suppose next time the phone updates, I will lose root as the active partition will switch ?
The only odd thing that has happened is the I have an extra/duplicate icon for the Android Files App. I don't know how to get rid of it...but it's not a big issue.
Thanks again for your help!
Cheers,
DV
Click to expand...
Click to collapse
Change to systemless and turn on magisk hide
dladz said:
Change to systemless and turn on magisk hide
Click to expand...
Click to collapse
remember to backup persist partition. i just got my oneplus 8 pro as well. it has a great deal for Black Friday in US.
dlhxr said:
remember to backup persist partition. i just got my oneplus 8 pro as well. it has a great deal for Black Friday in US.
Click to expand...
Click to collapse
How do I backup persist partition?, Will Titanium backup help or something else ?
I am new to the whole rooting thing.
dlhxr said:
remember to backup persist partition. i just got my oneplus 8 pro as well. it has a great deal for Black Friday in US.
Click to expand...
Click to collapse
Me? I have pal