Ok, so I'm gonna do the update to android 11 now that it seems to be more stable. My question is, once I do that, and I keep root, is there a way to do a factory data reset and not lose root all together? I like to do a factory reset when doing a major update just to make sure things run as smooth as possible, but I'd like to not lose root in the process. Thanks in advance!
Root (aka Magisk) IMHO resides in the boot image, so a factory reset would not interfere with root itself. Of course you would need to reinstall Magisk manager (Canary) after the factory reset. Oh, and you need to be on Canary Magisk for A11 anyway - so if you do the update from A10 you need to make sure you are on Magisk Canary (Manager and Magisk itself) or it won't work afterwards...
s3axel said:
Root (aka Magisk) IMHO resides in the boot image, so a factory reset would not interfere with root itself. Of course you would need to reinstall Magisk manager (Canary) after the factory reset. Oh, and you need to be on Canary Magisk for A11 anyway - so if you do the update from A10 you need to make sure you are on Magisk Canary (Manager and Magisk itself) or it won't work afterwards...
Click to expand...
Click to collapse
Nope latest beta works great too. Canary isn't needed anymore.
imneveral0ne said:
Ok, so I'm gonna do the update to android 11 now that it seems to be more stable. My question is, once I do that, and I keep root, is there a way to do a factory data reset and not lose root all together? I like to do a factory reset when doing a major update just to make sure things run as smooth as possible, but I'd like to not lose root in the process. Thanks in advance!
Click to expand...
Click to collapse
I have guides for this and for 11-11 they're in the guides section.
Thoroughly tested.
Kollachi said:
Nope latest beta works great too. Canary isn't needed anymore.
Click to expand...
Click to collapse
So I just need beta magisk and the regular app? Cause I just installed the canary magisk manager and it's missing quite a few options like magisk hide and such. And I definitely need those.
dladz said:
I have guides for this and for 11-11 they're in the guides section.
Thoroughly tested.
Click to expand...
Click to collapse
That is a lot more involved than I was expecting this to be. I figured I could just retain root with an update the same way I always do.
imneveral0ne said:
That is a lot more involved than I was expecting this to be. I figured I could just retain root with an update the same way I always do.
Click to expand...
Click to collapse
It's 9 steps?
You need to remove modules, you will need to use the updated boot img and your won't have twrp to fall back on.
If you want to wipe after you'll need to set up then reinstall magisk then obtain your boot img, patch it and boot it then flash it directly.
dladz said:
It's 9 steps?
You need to remove modules, you will need to use the updated boot img and your won't have twrp to fall back on.
If you want to wipe after you'll need to set up then reinstall magisk then obtain your boot img, patch it and boot it then flash it directly.
Click to expand...
Click to collapse
It's not that, it's just that I usually used a pretty simple guide for updates and I didn't need to do anything on the computer for it to work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is it because we're updating from 10 to 11 that these extra steps are needed? Sorry, I'm just curious is all.
imneveral0ne said:
It's not that, it's just that I usually used a pretty simple guide for updates and I didn't need to do anything on the computer for it to work.
Is it because we're updating from 10 to 11 that these extra steps are needed? Sorry, I'm just curious is all.
Click to expand...
Click to collapse
No not at all.
Tbh it's extremely similar.
Just that the way I've written it means you won't have issues, I'd rather cover bases in a guide than answer a 100 questions later.
If you have magisk functional already then you're halfway there.
I've updated the OP in my guide.
Some steps are informational
dladz said:
No not at all.
Tbh it's extremely similar.
Just that the way I've written it means you won't have issues, I'd rather cover bases in a guide than answer a 100 questions later.
If you have magisk functional already then you're halfway there.
I've updated the OP in my guide.
Some steps are informational
Click to expand...
Click to collapse
I installed the canary built of magisk from your thread, but there isn't an install button. ?
Edit: I went back to the beta build and it worked fine with patching.
imneveral0ne said:
I installed the canary built of magisk from your thread, but there isn't an install button. ?
Edit: I went back to the beta build and it worked fine with patching.
Click to expand...
Click to collapse
Good stuff..so what channel did you change it to.? Are you able to provide a version as someone has the exact same issue.
dladz said:
Good stuff..so what channel did you change it to.? Are you able to provide a version as someone has the exact same issue.
Click to expand...
Click to collapse
Just the beta channel. And I can once I get my phone working again lol. You straight up told me I was gonna need to use this to root my phone after a factory reset. And I went ahead and installed twrp anyway. Using the msm tool now to fix it lol.
imneveral0ne said:
Just the beta channel. And I can once I get my phone working again lol. You straight up told me I was gonna need to use this to root my phone after a factory reset. And I went ahead and installed twrp anyway. Using the msm tool now to fix it lol.
Click to expand...
Click to collapse
Lol no worries man. Glad you're up and running.
:good:
Related
Hi everyone, posting this as a information about something you should NOT try: upgrade your OTA rom with custom recovery installed, in my case TWRP.
I did this with ignorance of not think that (or search about) the custom rom could interfere at the normal process of OTA upgrade from Lollipop to MarshMallow. Actually I remembered that I was unlocked and rooted the phone but I did not remember I was using custom recovery. AFAIK at this device is impossible to root without unlocking and custom recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are on TWRP don't do this!
For those don't know about TWRP and OTA updates, read this:
https://twrp.me/faq/officialota.html
In short terms: don't try OTA updates (official updates) if you installed custom rom such as TWRP. "Installing official updates from your manufacturer or carrier is not supported by TWRP." "[This] may result in unexpected behavior" "Most of the time the best way to get a new update onto your device is to simply wait a couple of days for ROM makers for your device to come up with ROMs that are based on the new update that you can safely and easily install."
But I did it. And now I'm reporting it for those who are curious. So, what's happened?
Fortunately the device is not bricked as I thought when it reboot to TWRP for flashing the OTA update instead of the stock recovery process! I thought that I messed everything when I see the frozen TWRP for something about 10 minutes or less. After the long 10 minutes of frozen TWRP image I got the recovery working and checked the log:
Of course, errors on the log.
Rebooted and got a frozen background image, after a while a permanent black. When the screen turn off the notification system shows the battery as dead (and it as not). But I could turn it off and gain access to the recovery holding power and volume down buttons.
After two failed reboots to the system with the same result I tried to make a screenshot using the hard buttons and it works (screenshoted the black screen) and suddenly the lock screen shows up. I got into, everything working slow meaning that there was a lot things working in the background. Got some error messages from google service and MMS/SMS communication and minutes later it automatically reboots and booted the TWRP again.
This turned to a loop. I stopped this by going to the system setup - about the device - check for updates. And got a message "the update has failed". Good. After a while the message offering the update shows again... No, thanks...
I rebooted to TWRP and fixed the permissions, maybe this solve some problems.
Right now the phone is working but the rebooting process has unexpected behaviors, some tries result in a normal fast process and other tries result in a long black image and the system/launcher just don't arm up for some minutes, but after a while it works. I'm not confident. Already backed up apps with Titanium backup.
I'm planning to restore everything from the stock using this guide:
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
And them, maybe, update the OTA to marshmallow. Before doing that, I will search and get to know if it is possible to re-root the phone with marshmallow in osprey (that means re-unlock and install TWRP again). Rooted device it's a need for me.
This is what happened to my device when tried to OTA update with TWRP. I had luck not bricking this.
+1 on the dumb attempt. Early morning, excited for the release, upgrade please! Yeah, no good. Is restoring our only option? Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery ?
Sent from my Nexus 6 using Tapatalk
Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
Click to expand...
Click to collapse
Yeah, DON'T proceed with the update! Deleting the downloaded files just break the process... My advise is to make a backup before deleting this.
sgloki77 said:
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery
Click to expand...
Click to collapse
Ok, sorry about the huge wall of text.
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
golgiapp said:
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
Click to expand...
Click to collapse
:good:
Good to know that a factory reset could fix the problems caused by the OTA update with TWRP. But after this it should remain with custom recovery and not possible to OTA update. for stock MM
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Not sure, but take a look at /cache
gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
/data/data/com.motorola.ccc.ota/app_download
hp420 said:
/data/data/com.motorola.ccc.ota/app_download
Click to expand...
Click to collapse
found it!!
thanks extracted ok !!
its a zip flashable,can it be converted to install like the oem recovery images using the adb method?
gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Thank you for the warning
---------- Post added at 12:58 AM ---------- Previous post was at 12:54 AM ----------
Thank you for the warning
I experience this today, I flashed a stock rom again so I can have the OTA update, but what I can't do is root my device, I flash the custom recovery and then I flash the beta version of SuperSU, and when I reboot my device it bricks in the Motorola Logo, anybody knows how to fix this, or should I wait a little bit longer to root my phone? as the OP I need root too
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
nelsonw said:
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
VicSanRED said:
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
Click to expand...
Click to collapse
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
hp420 said:
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
Click to expand...
Click to collapse
I tried with the latest version 2.66 and still the same issue. Don't know what to do now.
So its posible to root MM ?? Safe ,stable?
Supersu v 2.62??
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
nelsonw said:
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Can you post a little tutorial?, I wanna be sure I'm doing everything OK.
Hello guys, I have succeeded in making rooted boot.img / Kernel for OnePlus One COS13.0 that was just released yesterday,
HOW TO
Download the zip
Extract it
Run "ROOT" file or "ROOT.bat" file present in the folder, it will automatically root your OPO connected with USB debugging on
Install >> sdcard >> root.zip and then reboot
Download: package
Added to OnePlus One index thread:
[INDEX] OnePlus One
the other way will be using twrp flash chainfire systemless super su to get root.
janice1234 said:
the other way will be using twrp flash chainfire systemless super su to get root.
Click to expand...
Click to collapse
This boot.img is compiled the same way, used his script as guide. It is pretty useful and fast so thought this would be good, and yes thanks for sharing
hi, this enable built-in superuser?
Mandrake2010 said:
hi, this enable built-in superuser?
Click to expand...
Click to collapse
COS doesn't have built in superuser
Sent from my A0001 using Tapatalk
Doesnt work, my oneplus reboots and remains unrooted..?
denogun said:
Doesnt work, my oneplus reboots and remains unrooted..?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'll try it again.
THANK the post if I deserve
MZO said:
] I'll try it again.
THANK the post if I deserve
Click to expand...
Click to collapse
I tried replicating the steps in your batch file, the problem apparently lies with the flash command; somehow my bootloader relocked itself when I applied the update via CM recovery, seems like there's no way out for me now...
denogun said:
I tried replicating the steps in your batch file, the problem apparently lies with the flash command; somehow my bootloader relocked itself when I applied the update via CM recovery, seems like there's no way out for me now...
Click to expand...
Click to collapse
Oh darn! Try unlocking bootloader again? Didn't happen to me when I switched to COS13 tho
THANK the post if I deserve
turned on usb debugging, plugged OPO in, ran BOOT.bat, but it says it's still waiting for device?
khanhee said:
turned on usb debugging, plugged OPO in, ran BOOT.bat, but it says it's still waiting for device?
Click to expand...
Click to collapse
Connection isn't properly established with the device, try changing the cable
THANK the post if I deserve
MZO said:
Connection isn't properly established with the device, try changing the cable
THANK the post if I deserve
Click to expand...
Click to collapse
thanks for the quick reply.
cable works fine when using adb though. maybe a driver issue
khanhee said:
thanks for the quick reply.
cable works fine when using adb though. maybe a driver issue
Click to expand...
Click to collapse
Hah, yea could be. The script is fine here
THANK the post if I deserve
is OTA still possible after that?
123Kage said:
is OTA still possible after that?
Click to expand...
Click to collapse
Yes, it won't hurt system partition so yup
Transmitted via BACON
Just for info, I used SuperSu beta 2.67 / 2.71 and I had some issues. Titanium backup works, founds root, such as adb, but some other apps don't. @MZO can you please test Secure Settings or SELinux ModChanger?
Furthermore, how did you upgrade? Did you flash busybox?
Thanks!
matssa said:
Just for info, I used SuperSu beta 2.67 / 2.71 and I had some issues. Titanium backup works, founds root, such as adb, but some other apps don't. @MZO can you please test Secure Settings or SELinux ModChanger?
Furthermore, how did you upgrade? Did you flash busybox?
Thanks!
Click to expand...
Click to collapse
No I didn't flash busybox, and sorry can't test because I'm back on. my ROM COS13 isn't good enough
MZO said:
No I didn't flash busybox, and sorry can't test because I'm back on. my ROM COS13 isn't good enough
Click to expand...
Click to collapse
Ah crap... Oh well, I'll wait a bit for the signed version of COS13. Very strange though... Very strange that my root isn't fully made when flashing supersu. ARRGGGG!
MZO said:
Hello guys, I have succeeded in making rooted boot.img / Kernel for OnePlus One COS13.0 that was just released yesterday,
HOW TO
Download the zip
Extract it
Run "ROOT" file or "ROOT.bat" file present in the folder, it will automatically root your OPO connected with USB debugging on
Install >> sdcard >> root.zip and then reboot
Download: package
Click to expand...
Click to collapse
I can't download the file. Says webpage unavailable. Can you have a look?
Thanks..
-Screwed up somewhere as my goal was to install LineageOS and try to use it on an At&t mvno.
-Package was unopened for months, so it still had the older firmware.
-Everything seemed okay after I unlocked the bootloader.
-Then I installed TWRP.
-Did a backup of everything using TWRP before I was going to try and root the device.
-I knew something was wrong when no verity opt encrypt and Magisk gave some error message and failed.
-Now whenever I boot the device, I get a N/A in the top left corner and then goes into TWRP.
-Restoring the backup using TWRP did nothing.
-I thought this would be the solution (dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1M), but I get the bad key first and then N/A before going back to TWRP.
https://forum.xda-developers.com/moto-e4/help/moto-e4-metro-variant-rebooting-to-twrp-t3825841
What should I do now?
Any help would be appreciated. Even links to other posts that dealt with this issue is fine. Be aware that my skill level is only a little better than following Youtube videos.
Thank you.
N/A is normal. It will be there forever after you unlock bootloader. Did you format data in TWRP and type yes to format?
Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.
ah-le-le said:
Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.
Click to expand...
Click to collapse
once you flash TWRP you have to flash a no verity zip and probably magisk and definitely format data to remove encryption for your phone to boot.
Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ah-le-le said:
Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
Click to expand...
Click to collapse
I can't read that, LoL. Maybe... Failed toount data? That's because you're still encrypted.
Put the zips on external storage. Format data, type yes.
Now reboot recovery (not system) then flash the zips.
And you can take screenshots in TWRP.
Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.
One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.
ah-le-le said:
Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.
Click to expand...
Click to collapse
ah-le-le said:
One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.
Click to expand...
Click to collapse
Use caution going with a custom ROM on this device, especially with a mvno. You may score far more hurt than benefit. Also consider what you are trying to accomplished going with custom ROMs given the clean stability of Moto stock ROMs. Toss in Xposed framework and a few modules like Gravitybox for full control/customization.
OTA updates can not be processed with a custom recovery (one of several prerequisites that your device no longer meets). You may get notified but the update won't install; you'll be dumped into TWRP. You can easily disable the update engine and corresponding notifications on a rooted device.
Update out:
https://source.android.com/security/bulletin/pixel/2019-12-01.html
Security updates noted.
Functional patch notes moved to:
Pixel Community forum https://support.google.com/pixelphone/community
Notable fixes:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In addition to the specific items listed above, the December update includes hundreds of various fixes and improvements across many areas including performance, stability, camera, display and face unlock.
12/3/19 Edit Note:
*Updated Google Pay fix to better describe actual fix. This is an experimental feature that may roll out in a future update.
Anyone updated to December patch that can verify Magisk still working?
Jexx11 said:
Anyone updated to December patch that can verify Magisk still working?
Click to expand...
Click to collapse
20.1 worked fine.
I noticed they added the styles and themes app in display settings. Tulsadiver's accent mod still works- https://forum.xda-developers.com/pixel-2-xl/themes/android-10-accents-mod-t3996755
Jexx11 said:
Anyone updated to December patch that can verify Magisk still working?
Click to expand...
Click to collapse
Works as it should
Nothing yet here in UK. Did we also get live caption feature?
100rabh7791 said:
Nothing yet here in UK. Did we also get live caption feature?
Click to expand...
Click to collapse
live caption working if you use this mode https://www.xda-developers.com/enable-pixel-4-live-caption-android-10/ thanks to @MishaalRahman
kmry said:
live caption working if you use this mode https://www.xda-developers.com/enable-pixel-4-live-caption-android-10/ thanks to @MishaalRahman
Click to expand...
Click to collapse
Thanks but not rooted so i can't use this. Can't root as use this phone for official purposes and for payments
Swipe down on homescreen for notification drawer was also added
hawkswind1 said:
20.1 worked fine.
I noticed they added the styles and themes app in display settings. Tulsadiver's accent mod still works- https://forum.xda-developers.com/pixel-2-xl/themes/android-10-accents-mod-t3996755
Click to expand...
Click to collapse
Can we change status bar icons ? Like the cellular bar and Wifi and battery?
telegram notifications failed to group together after december update
I can't seem to get root back. I did my usual things. It boots up, but when I flash the latest magisk it gets stuck at the G for a bit, then reboots into recovery, where I try again.
I'm fastboot booting the latest twrp and flashing the latest magisk there.
When I say it boots up, I always check that it does before flashing anything.
blacklisted.rock said:
Can we change status bar icons ? Like the cellular bar and Wifi and battery?
Click to expand...
Click to collapse
I believe it only changes the wifi icon on the status bar and the quick tile icons
Larzzzz82 said:
I can't seem to get root back. I did my usual things. It boots up, but when I flash the latest magisk it gets stuck at the G for a bit, then reboots into recovery, where I try again.
I'm fastboot booting the latest twrp and flashing the latest magisk there.
When I say it boots up, I always check that it does before flashing anything.
Click to expand...
Click to collapse
I suggest you flash magisk uninstaller first and then flash magisk 20.1.
jlokos said:
I suggest you flash magisk uninstaller first and then flash magisk 20.1.
Click to expand...
Click to collapse
That worked! Thank you sir.
Anybody doing ota update and keeping root and magisk?
bsg411 said:
Anybody doing ota update and keeping root and magisk?
Click to expand...
Click to collapse
Is this possible? I'd love to know how?
Also, did anyone else have to flash magisk uninstaller for this update as is mentioned a few posts above by someone? That's not part of my standard procedure.
One more positive I noticed from the update. There's no longer a delay between returning to the homescreen and when you can open a folder. Previously I had to wait a split second for the homescreen animation to finish before I could open a folder.
Seems like 3rd party launchers are supported too? I just used Nova launcher with gesture navigation(not sure if this is new)
Schroeder09 said:
Is this possible? I'd love to know how?
Also, did anyone else have to flash magisk uninstaller for this update as is mentioned a few posts above by someone? That's not part of my standard procedure.
Click to expand...
Click to collapse
I thought I read somewhere it could be done.
Well, last month was the first time I was able to flash OTA and keep root. The procedure was to uninstall Magisk from Magisk Manager (not completely) install the OTA (DON'T REBOOT!) then re-install Magisk from the manager (the after OTA option), then reboot. Worked great.
This month, I tried this and I'm not able to boot up. Reboots a couple of times then goes to a stock recovery screen telling me it can't boot and the options are "try again" and the dreaded "factory reset".
I've tried booting in TWRP (using fastboot) to flash the latest magisk uninstall, and then flashing the full factory image (with the -w flag removed)... not luck so far, but I'll try again a few times as in the past when I've had trouble, re-flashing actually helps.
Anyone else had similar trouble?
basily said:
Well, last month was the first time I was able to flash OTA and keep root. The procedure was to uninstall Magisk from Magisk Manager (not completely) install the OTA (DON'T REBOOT!) then re-install Magisk from the manager (the after OTA option), then reboot. Worked great.
This month, I tried this and I'm not able to boot up. Reboots a couple of times then goes to a stock recovery screen telling me it can't boot and the options are "try again" and the dreaded "factory reset".
I've tried booting in TWRP (using fastboot) to flash the latest magisk uninstall, and then flashing the full factory image (with the -w flag removed)... not luck so far, but I'll try again a few times as in the past when I've had trouble, re-flashing actually helps.
Anyone else had similar trouble?
Click to expand...
Click to collapse
Extract the boot.img from the factory image, put it on your phone and patch it via magisk manager. Then put the patched.img in your platform-tools folder, and fastboot it to both slots. It's also a good idea to disable all modules and substratum themes, and set your screen lock to swipe before you do monthly updates. It's what I do every month without issues for about the last 2 years :good:
T-Mobile site shows it's complete: https://www.t-mobile.com/support/devices/software-updates/oneplus-7t-pro-update-to-android-11
No update for me yet. Has anyone gotten it?
No dice for me.. I've been smashing the check for update button too
I just updated to 11. So far everything seems ok.
Anyone updated with root yet?
I have the update available, but want to make sure I have everything in place to get root back once I do.
syndr said:
Anyone updated with root yet?
I have the update available, but want to make sure I have everything in place to get root back once I do.
Click to expand...
Click to collapse
I did yesterday. I MSMed and updated to 43. Rooted than installed oos11 and root held.
Got 11 this morning, no major issues.
I think some of the McLaren custom stuff is borked, and all my ringtone & sounds were defaulted to silent.
Never rooted, haven't seen a need for it yet.
Downloading right now
It's been 2 days that my oneplus 7t pro McLaren 5g edition when trying to update it keeps loading and not downloading the update, i updated my Google services, i rebooted my device multiple times, nothing worked, please help me fix this issue please
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
11.0.1.2 on T-Mobile OP7T Pro Mclaren with root.
ash083 said:
11.0.1.2 on T-Mobile OP7T Pro Mclaren with root.
Click to expand...
Click to collapse
Same here, been running for 3 days now. Not a single issue. Rooted with Magisk.
starcms said:
Same here, been running for 3 days now. Not a single issue. Rooted with Magis
Click to expand...
Click to collapse
starcms said:
Same here, been running for 3 days now. Not a single issue. Rooted with Magisk.
Click to expand...
Click to collapse
Yeah had to use the Canary version of Magisk to patch boot image.
ash083 said:
Yeah had to use the Canary version of Magisk to patch boot image.
Click to expand...
Click to collapse
I was using Canary already, guess I lucked out lol. But Magisk just released official version 23 so it's a moot point now.
How were you able to extract the boot image without twrp?
starcms said:
I was using Canary already, guess I lucked out lol. But Magisk just released official version 23 so it's a moot point now.
How were you able to extract the boot image without twrp?
Click to expand...
Click to collapse
I didn't. I downloaded it.
starcms said:
Same here, been running for 3 days now. Not a single issue. Rooted with Magisk.
Click to expand...
Click to collapse
My OTA update isn't being downloaded even after rebooting the phone and factory reseting my phone , do I have to root my phone to download it?
I don't want to risk rooting my device especially when it's t-mobile and I'm no root expert.
Do u know any other solution to download the update it would mean a lot.
Thank you
ash083 said:
I didn't. I downloaded it.
Click to expand...
Click to collapse
Mind sharing the link for the boot.img you downloaded? No worries if not, I'll look on here for it, but that's the main thing I need before I update. Thanks, man!
syndr said:
Mind sharing the link for the boot.img you downloaded? No worries if not, I'll look on here for it, but that's the main thing I need before I update. Thanks, man!
Click to expand...
Click to collapse
[GUIDE] ROOT OnePlus 7T Pro McLaren 5G (T-Mobile version HD1925)
Hi. So I wanted to put together a little write-up on how to root the T-Mobile McLaren 5G variant, at least how I rooted mine, as there doesn't seem to be anything about this yet. I was actually able to root my device last night successfully, so I...
forum.xda-developers.com
After the Tmobile update to Android 11, my phone became unusable. It will reboot to T-mobile boot screen after about 60 seconds now. Immediatedly after the update it was crashing after 2 minutes. Then I tried a full wipe and restore, it worked for a day, then when into crashing a minute after pin unlock. Did another full wipe and it lasted 3 days, then back to crashing again.
Tried various recovery methods, and nothing worked. Next step is to figure out how to put stock T-mobile Android 10 back. Why not root it and put on another OS you say? Well I need the work profile stuff and all the lockdown checks for work. Don't want my device to get marked as "untrusted".
Any recommendations on as to best place to start on reinstall.
I'm having a problem where when I go into fast boot mode my computer doesn't recognize my device driver so I am unable to send any fast boot commands, anyone know the fix?
shemminger said:
After the Tmobile update to Android 11, my phone became unusable. It will reboot to T-mobile boot screen after about 60 seconds now. Immediatedly after the update it was crashing after 2 minutes. Then I tried a full wipe and restore, it worked for a day, then when into crashing a minute after pin unlock. Did another full wipe and it lasted 3 days, then back to crashing again.
Tried various recovery methods, and nothing worked. Next step is to figure out how to put stock T-mobile Android 10 back. Why not root it and put on another OS you say? Well I need the work profile stuff and all the lockdown checks for work. Don't want my device to get marked as "untrusted".
Any recommendations on as to best place to start on reinstall.
Click to expand...
Click to collapse
Look here: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4043925/
If your device hasn't exposed EDL mode and you can get to fastboot, you can try the command: `fastboot oem edl` from the connected computer to get it there.
I also had to extract the CAB file in the linked post before my computer would see the drivers for the phone's EDL mode and install them.
Anyone have a working Dolby Atmos?
Was using the Android 10 version from I think the ROG phone but that is now incompatible