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.
Related
Just got the above device for Christmas. While trying to figure out if I could update the version of Android, I chatted with the Samsung Smart Switch help desk and was told that since my device status is listed as "Custom," it has apparently been rooted. Except that when I downloaded Titanium BackUp, it said it couldn't find the root or the SU (the actual error message disappeared and I can't get it back). Anyway, under Root Access it says Failed.
There is no SuperUser software on the device, nor Busy Box. When I booted into recovery, I got basic Android recovery, although it included an option to update from ADB.
So, any guesses as to whether it's been rooted or not? If it has, any issues with installing TWRP, etc., as per the link here: http://forum.xda-developers.com/gal...overy-samsung-galaxy-tab-a6-sm-t280-t3475381? Or just trying to root it, per instructions here: http://forum.xda-developers.com/gal...m-samsung-galaxy-tab-7-0-lte-2016-sm-t3455788.
I would like to update my version of Android to run a couple apps that are currently incompatible, not to mention get rid of the massive bloatware. Don't have Ubuntu and found the instructions in the above two links a little confusing (how do I ' Flash with ODIN 3.10.7 in the AP slot."?) although I can research my way through it.
Or I can just return the tablet for one that hasn't been modified and hope I can update the OS via Smart Switch.
RobinG34 said:
Just got the above device for Christmas. While trying to figure out if I could update the version of Android, I chatted with the Samsung Smart Switch help desk and was told that since my device status is listed as "Custom," it has apparently been rooted. Except that when I downloaded Titanium BackUp, it said it couldn't find the root or the SU (the actual error message disappeared and I can't get it back). Anyway, under Root Access it says Failed.
There is no SuperUser software on the device, nor Busy Box. When I booted into recovery, I got basic Android recovery, although it included an option to update from ADB.
So, any guesses as to whether it's been rooted or not? If it has, any issues with installing TWRP, etc., as per the link here: http://forum.xda-developers.com/gal...overy-samsung-galaxy-tab-a6-sm-t280-t3475381? Or just trying to root it, per instructions here: http://forum.xda-developers.com/gal...m-samsung-galaxy-tab-7-0-lte-2016-sm-t3455788.
I would like to update my version of Android to run a couple apps that are currently incompatible, not to mention get rid of the massive bloatware. Don't have Ubuntu and found the instructions in the above two links a little confusing (how do I ' Flash with ODIN 3.10.7 in the AP slot."?) although I can research my way through it.
Or I can just return the tablet for one that hasn't been modified and hope I can update the OS via Smart Switch.
Click to expand...
Click to collapse
Seems weird that the device is listed as custom out of the box. Best bet is to reflash the custom firmware using ODIN (you have to download a copy of the stock firmware of course) after that you can follow said guide to flash TWRP and then root after.
jedld said:
Seems weird that the device is listed as custom out of the box. Best bet is to reflash the custom firmware using ODIN (you have to download a copy of the stock firmware of course) after that you can follow said guide to flash TWRP and then root after.
Click to expand...
Click to collapse
It was an Open Box purchase - why we got it so cheap. I'm using it as my reading tablet and the Nook app is one of the two that won't work on it. I can (and will) look up ODIN on my own, but for the sake of expediency, if someone has a good link to the why's and what for's and how's, that would be appreciated.
jedld said:
Seems weird that the device is listed as custom out of the box. Best bet is to reflash the custom firmware using ODIN (you have to download a copy of the stock firmware of course) after that you can follow said guide to flash TWRP and then root after.
Click to expand...
Click to collapse
where can you find stock firmware i cant seem to find it anywhere?
mjohnson4580 said:
where can you find stock firmware i cant seem to find it anywhere?
Click to expand...
Click to collapse
You can check out sammobile.com for that
jedld said:
You can check out sammobile.com for that
Click to expand...
Click to collapse
Ive tried there they have no us version for this tablet
http://updato.com/firmware-archive-select-model that is where I grabbed one for the US model
I'm running Viper 4.3.1 on an unlocked HTC 10 on Verizon. I've been extremely happy with this build and saw no reason to update to the systemless version of Viper. I've been careful not to install updates that would cause problems, but I got sloppy two days ago and let it update the HTC Lock Screen app. Now the phone is stuck on a flashing stock lock screen and won't do anything else.
I can boot into bootloader and recovery, but the phone is not recognized when I plug it into my PC.
So my question(s) is this: Is there a simple way to return to a working version of Viper 4.3.1? Perhaps sideloading an earlier version of lock screen?
I guess at this point I also should ask if I'm fighting a losing battle by trying to stay on an older version of Viper?
Any help is much appreciated.
PS -- If this should have been posted in the ROMs section, I apologize.
hunteditor said:
I'm running Viper 4.3.1 on an unlocked HTC 10 on Verizon. I've been extremely happy with this build and saw no reason to update to the systemless version of Viper. I've been careful not to install updates that would cause problems, but I got sloppy two days ago and let it update the HTC Lock Screen app. Now the phone is stuck on a flashing stock lock screen and won't do anything else.
I can boot into bootloader and recovery, but the phone is not recognized when I plug it into my PC.
So my question(s) is this: Is there a simple way to return to a working version of Viper 4.3.1? Perhaps sideloading an earlier version of lock screen?
I guess at this point I also should ask if I'm fighting a losing battle by trying to stay on an older version of Viper?
Any help is much appreciated.
PS -- If this should have been posted in the ROMs section, I apologize.
Click to expand...
Click to collapse
You can try manually removing the updated app.
Use Twrp > advanced > file manager
Locate the /data/app/com.htc.lockscreeen-1 folder or whatever it's called in there and delete that entire folder.
Try to reboot, may or may not help...
Sent from my HTC6545LVW using Tapatalk
Almost There
santod040 said:
You can try manually removing the updated app.
Use Twrp > advanced > file manager
Locate the /data/app/com.htc.lockscreeen-1 folder or whatever it's called in there and delete that entire folder.
Try to reboot, may or may not help...
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
That didn't work, but by trying it, I think it will be as simple as installing a previous version of the lockscreen. Now just have to find one.
hunteditor said:
That didn't work, but by trying it, I think it will be as simple as installing a previous version of the lockscreen. Now just have to find one.
Click to expand...
Click to collapse
http://www.apkmirror.com/apk/htc-corporation/
Sent from my HTC6545LVW using Tapatalk
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
Can someone please paste a link to the 11.0.4.4 global installation file. My Oneplus8 pro is rooted and as such I cannot download it from system updates. I tried to fastboot an unpatched boot but I couldn't get WiFi to turn on. Accordingly, I'd like an alternate download option for 11.0.4.4 global.
Being rooted should not prevent the update. Otherwise download "oxygen updater" from the play store.
shorty1993 said:
Being rooted should not prevent the update. Otherwise download "oxygen updater" from the play store.
Click to expand...
Click to collapse
In my experience being rooted does prevent updates especially if you've flashed the patched boot image to both slots. In the past I've had his name issue. I got the update to stick when I fastboot flash Boot the original stock boot Image.
Have not seen the full 11.0.4.4 global zip anywhere yet....
I uninstalled Magisk, took the update and then reinstalled Magisk before rebooting. Seems to have worked OK.
PieceKeepr said:
I uninstalled Magisk, took the update and then reinstalled Magisk before rebooting. Seems to have worked OK.
Click to expand...
Click to collapse
Tried that. No joy.
State.of.mind said:
In my experience being rooted does prevent updates especially if you've flashed the patched boot image to both slots. In the past I've had his name issue. I got the update to stick when I fastboot flash Boot the original stock boot Image.
Click to expand...
Click to collapse
I tried that, but when I did I couldn't get wifi enabled. I tried to download on cellular but it repeatedly failed. I rarely use cellular and I only have 2gb/mo. (If it were stable I'd be fine.)
shorty1993 said:
Being rooted should not prevent the update. Otherwise download "oxygen updater" from the play store.
Click to expand...
Click to collapse
Oxy updated still has 2 2 not 4.4
PieceKeepr said:
I uninstalled Magisk, took the update and then reinstalled Magisk before rebooting. Seems to have worked OK.
Click to expand...
Click to collapse
No joy.
I think I'll just live with 2.2 until oxy updated has 4.4. From what I've read 4.4 doesn't really do much. OnePlus sucks anymore.
PS I was finally able to download 2.2 again and I install it (via system update) which got rid of root so I downloaded and installed 4.4. Haven't rooted it yet.
almahix said:
PS I was finally able to download 2.2 again and I install it (via system update) which got rid of root so I downloaded and installed 4.4. Haven't rooted it yet.
Click to expand...
Click to collapse
Please post here if magisk worked on 4.4? And where did you get the stock boot.img?
following.
devsk said:
Please post here if magisk worked on 4.4? And where did you get the stock boot.img?
Click to expand...
Click to collapse
Yes Magisk works on 4.4. There's a 4.4 Boot image thread in the Guides. You should be able to find it
almahix said:
I think I'll just live with 2.2 until oxy updated has 4.4. From what I've read 4.4 doesn't really do much. OnePlus sucks anymore.
PS I was finally able to download 2.2 again and I install it (via system update) which got rid of root so I downloaded and installed 4.4. Haven't rooted it yet.
Click to expand...
Click to collapse
4.4 has improved my battery life somehow.. Seemingly a lot better than it was.
In regards to there updates, I'd say (if you're rooted or not) to use oxygen updater, it's an absolutely rock solid app.
Plus they tend to release way before OnePlus do for each device.
Installation isn't affected by root, simply disable your modules then when prompted to reboot just don't, click install to inactive slot and you're done.
If you've taken an incremental update then I couldn't help you, personally I'd only stick to full updates.
4.4 has definitely improved things for me.
I'm on BA /2023
dladz said:
4.4 has improved my battery life somehow.. Seemingly a lot better than it was.
In regards to there updates, I'd say (if you're rooted or not) to use oxygen updater, it's an absolutely rock solid app.
Plus they tend to release way before OnePlus do for each device.
Installation isn't affected by root, simply disable your modules then when prompted to reboot just don't, click install to inactive slot and you're done.
If you've taken an incremental update then I couldn't help you, personally I'd only stick to full updates.
4.4 has definitely improved things for me.
I'm on BA /2023
Click to expand...
Click to collapse
I like Oxygen Updater but it is still showing 2.2. I downloaded that 2.2 to get rid of root then was able to download 4.4 from system update, now I'm trying to root 4.4. Fastboot boot isn't working for me now for some reason. I'm not sure those downloads labeled 4.4, IN11AA (2020 global) are for real. If anyone has a file known to work on this variety please share a link.
almahix said:
I like Oxygen Updater but it is still showing 2.2. I downloaded that 2.2 to get rid of root then was able to download 4.4 from system update, now I'm trying to root 4.4. Fastboot boot isn't working for me now for some reason. I'm not sure those downloads labeled 4.4, IN11AA (2020 global) are for real. If anyone has a file known to work on this variety please share a link.
Click to expand...
Click to collapse
I have the BA model. So I can't help you there mate.
There were people flashing BA according to people in my thread, perhaps contact them via PM and see what they say.
Wasn't a big deal by all accounts.
11.0.4.4 available now via OnePlus site.
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
Oxygen updater finally has the 4.4 11 AA. I have payload dumped it and tried to patch the boot.img but magisk is failing. I cannot seem to get the canary channel so I'm using the latest beta but it isn't working. I cannot believe that nothing is working for me. Has anyone else succeeded?
almahix said:
Oxygen updater finally has the 4.4 11 AA. I have payload dumped it and tried to patch the boot.img but magisk is failing. I cannot seem to get the canary channel so I'm using the latest beta but it isn't working. I cannot believe that nothing is working for me. Has anyone else succeeded?
Click to expand...
Click to collapse
I've been on 11.0.4.4 for about a week now, but I did it using the OTA, not with the full upload. I've been doing it this way for a while, just like I did with my Pixel 2XL.
Anyway, I downloaded the full upload from OnePlus's page a few minutes ago to test it out, and I was able to patch the boot image after extracting it from the payload.bin using the latest beta magisk. I did it on my Pixel 2XL, that's really the only reason I keep that phone around now, besides it being a backup phone just in case my OP8P craps out.
bouchigo said:
I've been on 11.0.4.4 for about a week now, but I did it using the OTA, not with the full upload. I've been doing it this way for a while, just like I did with my Pixel 2XL.
Anyway, I downloaded the full upload from OnePlus's page a few minutes ago to test it out, and I was able to patch the boot image after extracting it from the payload.bin using the latest beta magisk. I did it on my Pixel 2XL, that's really the only reason I keep that phone around now, besides it being a backup phone just in case my OP8P craps out.
Click to expand...
Click to collapse
Great idea! I never thought of patching the stock boot.img on another device. It worked and now I'm finally rooted. Thank you for sharing your idea! BTW my former phone was a Pixel2XL. Was that the best phone ever? Still is but I sold it when I bought my 8pro. Big mistake!
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