Database Info

Desperate need of help with my device

I’ll make this short.
I was successfully rooted. But I couldn’t update to 9.5.6.
I updated but it keeps failing. I switch to slot A and I was on 9.5.6 but WiFi didn’t work and apps would crash randomly, and it was laggy. I would go back to slot b and WiFi worked and everything was great but I’m on 9.5.3. And I would try to update again and it would fail and sometimes I would have to have in fastboot and reflash twrp to reboot to restore. I restored the device multiple times, removed root but it still happens. I used to always use android but I was on iOS for years and I’m used to jailbreaking and Apple IOS. Please help me. How can I restore and start from scratch? Or how can I fix this? It’s very annoying. I have my info backed up so I don’t care what I have to do. I love this phone but I had the Verizon iPhone bug when people call me and I answer it fails on there end. Or else I would deal with 9.5.3. All help is greatly appreciated.

You need to read the threads better, it's already been explained that wifi can end up being disabled because the rooted boot.img is older than your current rom version. Flashing one of the kernels available usually fixes this. You can also extract the boot image from the rom you downloaded and patch that boot.img file using Magisk, then when you apply that everything should work correctly.
From reading your post it would appear you're on T-Mobile (US) so you would need to download the 9.5.6 package and then extract the boot.img, then patch that using Magisk and push it to the phone using fastboot, once you reboot everything should be rooted and working.

Auto OTA update on a rooted one plus 7 pro with magisk and TWRP?

Hello! I have had my One plus 7 pro international running for months now, rooted, following this guide https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368. I had the OTA update notification for quite some time now, but I ignored it because I was lazy. A few weeks ago my phone must have auto updated however, as I started noticing banner ads again that adaway usually blocked, and I have had a few other minor issues like GPS taking longer to connect or find where I am, wifi disconnects, and google not understanding what it usually does. Phone still works just fine, just minor issues I didn't really experience before.
I would like to completely reset the phone to clean it up, and re root and setup TWRP again, but im not sure how to safely do that since my phone was updated improperly (automatically). I have magisk still installed, but the modules dont seem to be working properly. Rebooting to recovery will reboot me to one plus recovery instead of twrp. When I restart is still says my boot loader is unlocked, and some apps (like chase mobile app) still say my phone is rooted. Oxygen updater says im up to date on OxygenOS 10.0.3.gm21aa.
What would be the best option for me to clean everything up, get my root modules working again, and have the phone fully up to date and stable? Any information would be greatly appreciated.

follow the same steps you followed first time. Boot to TWRP flash magisk, No need to factory reset. Flash twrp again if you want and reboot to system

Bootloop on OOS 10.5.7 (Global)

i just updated to latest 10.5.7 Global version via OTA, and before rebooting installed magisk to the inactive slot, and then rebooting resulted in bootloop..
restored to previous slot in fastboot and tried the OTA process again, and resulted in bootloop again..
now i have switched back to the old slot running 10.5.6..
anyone knows why the process resulted in bootloop, and any fix for this?
tia..
[edit]
resolved now..

Probably your mods. I have done same update resulting NO bootloop

Tracker31 said:
Probably your mods. I have done same update resulting NO bootloop
Click to expand...
Click to collapse
thx for the reply.. i dont have any magisk mod installed, apart from magisk itself..
(well theres the built-in systemless host module that i enabled, but i dont think this would cause any trouble as it has been there in the last few updates..)
and the same setup worked fine in the previous 10.5.4, 10.5.5 and 10.5.6 updates..
not sure what went wrong this time..

Try to download update package again. Maybe something broken

Tracker31 said:
Try to download update package again. Maybe something broken
Click to expand...
Click to collapse
already tried twice last night.. i had that doubt as well.. seems quite a few indian users are getting the update fast this time, so i thought maybe the wrong indian version was pushed to my device (global version)?
will try again tonight to see if anything changes.. thx..

Anyway it's not update failure, cuz it works for me

Tracker31 said:
Anyway it's not update failure, cuz it works for me
Click to expand...
Click to collapse
and your regional version is?

AC01BA

Doesn't matter which version you flash. I crossed flashed 3 times from EU to Global and vice versa. No issues.
Maybe you forgot to auto flash Magisk again after installing OTA. It is also recommended to flash Magisk to inactive slot after installing right away "before" reboot.

lekiaM said:
Doesn't matter which version you flash. I crossed flashed 3 times from EU to Global and vice versa. No issues.
Maybe you forgot to auto flash Magisk again after installing OTA. It is also recommended to flash Magisk to inactive slot after installing right away "before" reboot.
Click to expand...
Click to collapse
actually i did remeber to flash magisk to inactive slot after OTA before rebooting.. but seemingly im the only one with this bootloop, so probably certain config in my device caused the issue..
im now in the process of trying the OTA once more, and if this fails again, i shall try to just OTA without patching with maigsk..
if the device then boots, i shall root with magisk from scratch again then..

Strange, and yes must be something system-side. That's why they always say remove modules before flashing OTA or at least disable them. But in my case (only have another font module, iOS smileys and Ktweak) they didn't interfere with the last 2 Ota's. So updating went fine, but i might disable or uninstall them in future OTA's. To avoid such problems you are facing.

You need to uninstall all magisk mods before the update, buy you don't have any installed.
I also believe you need to download the full rom and not incremental. After the update you need to install magisk normally AND also to inactive slot before the reboot.
I haven't installed the latest yet but there previous updates are are installed without issues.

turned out to be a system modification i did back in the 10.5.4 times.. had no problem with it when updating to 10.5.5 & 6, so i totally forgot about its existence.. disabled the mod, updated to 10.5.7, and then enabled the mod again.. now everything is working fine..

Would you mind sharing what it was? I'm about to update and I got some system mods going on that could interfere, and I'm sire I'm forgetting about some too

ASTDEv3 said:
Would you mind sharing what it was? I'm about to update and I got some system mods going on that could interfere, and I'm sire I'm forgetting about some too
Click to expand...
Click to collapse
the magisk module created by smali patcher..

Question Updating to A13 with Magisk...

Just wanted to double check in light of the anti-rollback e-fuse google implemented.
Are we still ok to use the 'restore images' option/method in Magisk in order to keep root whilst taking the latest OTA (A13} update?

Why not just download the factory images.. patch the new boot. Flash images and flash the patched boot.

tlxxxsracer said:
Why not just download the factory images.. patch the new boot. Flash images and flash the patched boot.
Click to expand...
Click to collapse
Wanting to keep data...without editing flashall? dumb reason tho...guess cuz I still don't trust myself not to screw it up...

I used PixelFlasher. Keep Data option and patched boot image. Was up and running in less than 10 minutes going from A12 to A13. No loss of root and retained all functionality of modules. Still pass safetynet and gpay works

Damn it....why do I NEVER remember that. Have to take that stupid lil bug patch they issued just before 13 dropped. 1.25mb update taking a friggin hour ota...smdh

Finished the ota then used pixel flasher...MUCH faster! Tyfrm...

Question Unable to update to A13 after MSM soft brick recovery on LE2115.

I have an LE2115. I tried to update install CRdroid, and during the process the guide required an upgrade to firmware F18.
I was already on the newest (F20 I think) firmware, so I figured a small roll back would be needed. I downloaded F18 from the CRdroid firmware link, and when it was run it ended up bricking the phone. Annoying, but I didn't think it the end of the world.
To unbrick it I downloaded the MSM global 11.2.10.10 and flashed the phone with A11 (11.2.10.10). I was able to get back into the phone, and everything seemed ok at first glance.
The problem is now I can't install any updates to get it back to android 13.
If I do a system ->system update -> check for updates -> download and install. It says it downloads update LE2115_11.F.17_2170_20021123112, installs it, and reboots.
After rebooting the phone shows a successfully installed update message, but when I look at under About the system is still on Android 11 (11.2.10.10). No change at all.
If I try sticking the OTA zip LE2115_11.F.17_2170_202211231112 in root, and using that for a local update the phone gives me a update failed message after a few seconds. No useful error messages at all.
Can someone point me in the right direction? I can't figure out how to get this off A11 and back to A13 (F18).
This is making me want to rip out my hair as everything I have tried has failed to get me onto a current firmware.

wizardknight said:
I have an LE2115. I tried to update install CRdroid, and during the process the guide required an upgrade to firmware F18.
I was already on the newest (F20 I think) firmware, so I figured a small roll back would be needed. I downloaded F18 from the CRdroid firmware link, and when it was run it ended up bricking the phone. Annoying, but I didn't think it the end of the world.
To unbrick it I downloaded the MSM global 11.2.10.10 and flashed the phone with A11 (11.2.10.10). I was able to get back into the phone, and everything seemed ok at first glance.
The problem is now I can't install any updates to get it back to android 13.
If I do a system ->system update -> check for updates -> download and install. It says it downloads update LE2115_11.F.17_2170_20021123112, installs it, and reboots.
After rebooting the phone shows a successfully installed update message, but when I look at under About the system is still on Android 11 (11.2.10.10). No change at all.
If I try sticking the OTA zip LE2115_11.F.17_2170_202211231112 in root, and using that for a local update the phone gives me a update failed message after a few seconds. No useful error messages at all.
Can someone point me in the right direction? I can't figure out how to get this off A11 and back to A13 (F18).
This is making me want to rip out my hair as everything I have tried has failed to get me onto a current firmware.
Click to expand...
Click to collapse
I have the same device. After the 11.2.10.10 comes C48 first a12 build but it's marked F17 update. Then comes C-66 it's also marked F-17. Take it. Next update you guessed is labeled F-17 and it is actually F-17. Android 13. Then you will get F-18 ota as well. Then have to go into oxygen updater from playstore and update to F20. Latest with Jan sec patch. Since they dropped Android 13 all their device updates for op9 are labeled wrong. After msm you started on 11.2.4.4. I flash lineage and mess with things but mostly stay on stock as it's great and cam is good on os. Good luck. Check out pixelify by Kingsman 44. Real nice for op9 also.

mattie_49 said:
I have the same device. After the 11.2.10.10 comes C48 first a12 build but it's marked F17 update. Then comes C-66 it's also marked F-17. Take it. Next update you guessed is labeled F-17 and it is actually F-17. Android 13. Then you will get F-18 ota as well. Then have to go into oxygen updater from playstore and update to F20. Latest with Jan sec patch. Since they dropped Android 13 all their device updates for op9 are labeled wrong. After msm you started on 11.2.4.4. I flash lineage and mess with things but mostly stay on stock as it's great and cam is good on os. Good luck. Check out pixelify by Kingsman 44. Real nice for op9 also.
Click to expand...
Click to collapse
Ok. Thanks. I will run the update multiple times, and see if I can get to F18.
I can't believe the naming is all buggered up. Ok, well maybe I can believe it. Seems like OnePlus is just not doing a good job anymore, but there are not many other flagship grade phones with unlocked boot loaders and custom roms anymore (and I have been using custom android roms since the touch pro 2 days). It's making me a sad panda.
I just upgraded from a OnePlus 7t to the 9 because I got a crazy good price for an open box phone on clearance. Now I am starting to wonder if I made the wrong decision.
If I have to download 5+ updates every time something doesn't flash right I am going to burn though my 1TB internet cap in no time.
Update:
After ~10gb of updates I got to F18.
Now to go and get a custom rom on this thing, and hope I don't have to unbrick it again.