Database Users

[Discussion] Dumb attempt to upgrade to Marshmallow with TWRM in osprey

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.

October 2020 Security Update now available

{
"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"
}
October Security Update just released today.

Official 2020, October, MiA2 Stock fastboot ROM image V11.0.15.0.QDIMIXM link in appropriate thread: https://forum.xda-developers.com/showpost.php?p=83773363&postcount=144
CAPTCHA:
After clean fastboot flashing of this version with flash_all_except_data -> rebooting phone forces to stock recovery and requests factory reset.
Seems like after installing OTA possible behaviours are: either the same request for reset, or bootloop.
Reflashed back V11.0.14.0.QDIMIXM in order to make data backup

Aerobatic said:
Official 2020, October, MiA2 Stock fastboot ROM image V11.0.15.0.QDIMIXM link in appropriate thread: https://forum.xda-developers.com/showpost.php?p=83773363&postcount=144
Click to expand...
Click to collapse
nice! thanks for this!

Tried to apply update from OTA and my device failed to start, tried again and same result. Anyone else facing the same problem?
Tonight I'll try to flash full image directly.

Yes, the update seems buggy.
Even my phone was not able to start after the update.
Tried multiple times. Eventually had to factory reset it ?
xdxita said:
Tried to apply update from OTA and my device failed to start, tried again and same result. Anyone else facing the same problem?
Tonight I'll try to flash full image directly.
Click to expand...
Click to collapse

update works fine for me with no issues at all.

xdxita said:
Tried to apply update from OTA and my device failed to start, tried again and same result. Anyone else facing the same problem?
Tonight I'll try to flash full image directly.
Click to expand...
Click to collapse
same here, now I'll try to flash V11.0.14.0.QDIMIXM and let's see...
*update1*
It worked, I did flash_all_except_data and at first reboot it went to recovery and it showed up the same message saying that data may be corrupt but when I tried to boot it again it worked fine... now I'll backup everything and let's see if it works well at every reboot.
*update2*
everything fine running V11.0.14.0.QDIMIXM

So this is yet another botched update to skip, got it.
Thank you, brave ones who are willing to update first.
I'm just too afraid to update this device nowadays.

I had to reset device after last update this is really worst device support I had

For those who have reverted to V11.0.14.0.QDIMIXM, you don't have any bootloop on androidone screen?
My wife did the update, so I reverted to V11.0.14.0.QDIMIXM with flash_all_except_data but for now it still bootloop

updated successfully. there are no visible improvements

gromez said:
For those who have reverted to V11.0.14.0.QDIMIXM, you don't have any bootloop on androidone screen?
My wife did the update, so I reverted to V11.0.14.0.QDIMIXM with flash_all_except_data but for now it still bootloop
Click to expand...
Click to collapse
Try to switch to inactive slot.

How is your experience with stock rom and october patch?

HTCDevil said:
How is your experience with stock rom and october patch?
Click to expand...
Click to collapse
for me, it's snappy and stable.

Same problem here, unacceptable

Failed install here too, had to do a full reset
---------- Post added at 09:47 AM ---------- Previous post was at 09:40 AM ----------
PereVidi_77 said:
same here, now I'll try to flash V11.0.14.0.QDIMIXM and let's see...
*update1*
It worked, I did flash_all_except_data and at first reboot it went to recovery and it showed up the same message saying that data may be corrupt but when I tried to boot it again it worked fine... now I'll backup everything and let's see if it works well at every reboot.
*update2*
everything fine running V11.0.14.0.QDIMIXM
Click to expand...
Click to collapse
I tried unsuccessfully to reboot, Everytime showed this message, finally I accepted to erase the phone and let download the backup, I lost some downloaded stuff I may download again later.
It's an Shane this happening to Android one devices, suddenly we got from special to second class citizens

I had the same problem, which was solved for me by going into fastboot and issuing a fastboot boot recovery which for some reason returned by phone to a working state with an update failed notification. will skip this one

oferwald said:
I had the same problem, which was solved for me by going into fastboot and issuing a fastboot boot recovery which for some reason returned by phone to a working state with an update failed notification. will skip this one
Click to expand...
Click to collapse
i have same probleme how you doing ?
Go in fastboot and after ?
Thanks. i dont want loss my picture on my phone.... mi a2

maxou88 said:
i have same probleme how you doing ?
Go in fastboot and after ?
Thanks. i dont want loss my picture on my phone.... mi a2
Click to expand...
Click to collapse
Hi,
All I did was go into fastboot using the power and volume shortcut, and than I connected the device to my laptop and issued the command:
fastboot reboot recovery
(naturally using the SDK Platform tools)
After that, the phone started working again. Although there is no reasonable reason it should have worked. I was surprised enough so that I decided to take the effort to create an account here and share this for others. But again, maybe it was pure luck, YMMV.
Will be crossing my fingers for you.

I've tried to update and got the "Can't load Android system. Your data may be corrupt" messege. Tried again a few times, until the phone reverted back to the previous version and said it couldn't install the update. No October update for me. =(

Updating from 10 to 11 with root

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:

[ROM][11][TOCO][UNOFFICIAL] crDroid v7.9

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
FlameGapps FULL
Magisk 23.0 (after first boot) - (Download from here)
First-time installation:
Be sure to be on the latest stock MIUI v12.1.5.0 base
Boot into TWRP or OrangeFox
Flash Rom
Reboot to recovery
Flash Gapps
Format Data
Reboot to system
Update installation:
Boot into TWRP or OrangeFox and flash rom
Reboot to recovery and flash Gapps, Magisk, etc.
Wipe cache
Reboot to system
Sources:
ROM: https://github.com/crdroidandroid
Kernel: VantomKernel
Download:
ROM: OSS Releases
Known issues:
You tell me
Visit the official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs

Thanks for the roms man

a query, the brightness is always turned up to the maximum when using the fingerprint?

fuathan said:
Thanks for the roms man
Click to expand...
Click to collapse
Welcome

Jcyeici said:
a query, the brightness is always turned up to the maximum when using the fingerprint?
Click to expand...
Click to collapse
That has not been fixed yet

Thank you very much for your great work, I will look forward to the fix of the brightness when using the footprint.
A suggestion
1- they can put the option to hide the notch drop,
2- double tap to lock screen please

i think my storage is encrypted? i cant copy things onto the phone

Thank you @AndroidHQ254. I installed the rom and it runs very smooth. FOD and face unlock works quite well.
I use NikGapps macro from 12/14/20 and it runs very well.
A part of my storage is still encripted, but no idea how to fix. Maybe someone can share his experience.

Bernd K said:
Thank you @AndroidHQ254. I installed the rom and it runs very smooth. FOD and face unlock works quite well.
I use NikGapps macro from 12/14/20 and it runs very well.
A part of my storage is still encripted, but no idea how to fix. Maybe someone can share his experience.
Click to expand...
Click to collapse
More details please on the part of your storage you mean?

hanste (SM-G901F) said:
i think my storage is encrypted? i cant copy things onto the phone
Click to expand...
Click to collapse
Did your format data and reboot reboot recovery?

Jcyeici said:
Thank you very much for your great work, I will look forward to the fix of the brightness when using the footprint.
A suggestion
1- they can put the option to hide the notch drop,
2- double tap to lock screen please
Click to expand...
Click to collapse
DT2W works on FTS screens

AndroidHQ254 said:
More details please on the part of your storage you mean?
Click to expand...
Click to collapse
See added screenshots.
1. error message if you wipe dalvik cache.
2. if you install from twrp recovery from internal storage
3. system is not encrypted only internal storage (sdcard)
My system run very well every think works and I followed your Flashing Instructions .
Maybe it make sense to use the no-vertiy-opt-encrypt script if you install the rom first time?

Works great! Only some issues / wishes:
Sometimes the screen wont wake (if i get a phone call, or unlock with FOD, the screen can sometimes stay all black with no other possibilty than to reboot trough the power menu.
No Home controls on power menu
SELinux is set to permissive. Im using SELinuxModeChanger to automatically set it to enforced every boot so i can use Google Pay.
FOD icon stays on top of first pin lock input on boot.
To flash and root i had to use different recoveries. PBRP for the rom, then TWRP for Magisk.
Other than what is mentioned above, everything seems to work great!

Duplicate

Very interested in this rom. Used a nexus 6p for 2 or 3 years and the last rom I used for it was crdroid rom. It was excellent for that device, but the device showed its age and I had to replace it. I quite like this device and I'm willing to depart from the stock rom. But I'm going to wait for a while until all the bugs are fixed as I use it for work too, so I need it to be stable as possible.

I used that rom the last 4 weeks without any problem. FOD and face unlock works quite well. Any update planned to CrDroid 7.2?

@AndroidHQ254 What is the status of this rom, have there been any updates? Unfortunately, there is no official support for this phone on crdriod site. I'm not sure where to track any progress if there is one.

Bernd K said:
See added screenshots.
1. error message if you wipe dalvik cache.
2. if you install from twrp recovery from internal storage
3. system is not encrypted only internal storage (sdcard)
My system run very well every think works and I followed your Flashing Instructions .
Maybe it make sense to use the no-vertiy-opt-encrypt script if you install the rom first time?
Click to expand...
Click to collapse
I have not had issues with decryption personally

vetle666 said:
Works great! Only some issues / wishes:
Sometimes the screen wont wake (if i get a phone call, or unlock with FOD, the screen can sometimes stay all black with no other possibilty than to reboot trough the power menu.
No Home controls on power menu
SELinux is set to permissive. Im using SELinuxModeChanger to automatically set it to enforced every boot so i can use Google Pay.
FOD icon stays on top of first pin lock input on boot.
To flash and root i had to use different recoveries. PBRP for the rom, then TWRP for Magisk.
Other than what is mentioned above, everything seems to work great!
Click to expand...
Click to collapse
About missing features - That is a rom side thing
Selinux - For now we are permissive
About FOD - I have not encountered that. Plus I do not think you keep rebooting your phone
Include logs for bugs

sage of six paths said:
@AndroidHQ254 What is the status of this rom, have there been any updates? Unfortunately, there is no official support for this phone on crdriod site. I'm not sure where to track any progress if there is one.
Click to expand...
Click to collapse
I work alone so the rom will be updated in due time

Android 11 anyone!?

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