I have a problem. After updating lineage to version of Jan. 11, I flashed twrp again, because the update always puts the own recovery tool.. (annoying)..
I did use the extra menu from twrp and did not install the same way as I normally flash zips..
Slot A is active..
I additionally had to fix bootloop..
But I lost the modem function (cellular).. WiFi still working..
I reboot in twrp, slot a is active. If I now activate slot B, I get a message, mount failed. The data partition is not visible on B. Only on A.
So I only can use slot A right now..
The partition is not encrypted, I removed the pin.
But it boots too fast and cellular fails..
What can I do?
Related
I unlocked the device recently, flashed TWRP and Magisk. Now after updating to Oxygen OS 5.1.11 by flashing the full OTA via zip using TWRP 3.2.1-0, the wifi does not turn on and the mac address shown seems to be invalid (screenshot attached). Also, the already enrolled fingerprints were not being recognized, so I removed and added them again, but it shows a fingerprint registration error (screenshot attached). The face-unlock feature is also not working. I can add my face data, but the phone never unlocks. I did a TWRP backup before flashing the update. All other apps, data, settings etc remain intact.
Please help to fix these issues,
Thanks in advance
I have the same problem with mine
adarshd said:
I unlocked the device recently, flashed TWRP and Magisk. Now after updating to Oxygen OS 5.1.11 by flashing the full OTA via zip using TWRP 3.2.1-0, the wifi does not turn on and the mac address shown seems to be invalid (screenshot attached). Also, the already enrolled fingerprints were not being recognized, so I removed and added them again, but it shows a fingerprint registration error (screenshot attached). The face-unlock feature is also not working. I can add my face data, but the phone never unlocks. I did a TWRP backup before flashing the update. All other apps, data, settings etc remain intact.
Please help to fix these issues,
Thanks in advance
Click to expand...
Click to collapse
I reckon this is due to tinkering with SLOT A/B manually in TWRP. I did the dalvik and cache wipe (old habits die hard), but I doubt it's the problem. I believe it's because I f****ed up with the SLOT changing (stupid me!).
Now I believe we should flash the original 5.1.5 ROM, or maybe we could reflash bootloader/modem which seems to be corrupted (no wifi, no bluetooth, seems like a modem problem) because it too has to variants A and B and they are messed
Just start over and do a clean flash of 5.1.11 according to the proper procedure. System problems like this are usually sign of getting the slots mixed up.
Make sure to follow instructions that has been posted multiple times and since every update has come out.
!!! Remove any substratum theme mods if any!!!
Others don't but I always remove my pin/pattern just in case bc it just takes just a minute to re set back up
1. Boot to twrp
2. Flash OS
3. Flash TWRP.zip (official or blusparks)
4. REBOOT TO RECOVERY (that changes your slot)
5. Install magisk 16.x
6. Flash other mods like xposed and/or kernels
Done! or others say profit!... Whatever floats ur boat.
I don't wipe caches, but u are always free to do so.
I know (now), but it's to little to late. Once the Slots get ****ed, that no longer works
I was trying to update my OP6 to OOS 9.0.8.
I downloaded the full OTA and booted into TWRP, flashed the new update img, and forgot to flash TWRP and rebooted to system. No worries, I went to fastboot and installed TWRP via adb. All was good until this point. But after I flashed Magisk zip in one slot B, slot A files all appear gibberish.
I don't know how to proceed. The device proceeds to boot on slot B all fine, latest OOS, and rooted. But booting to slot A always loops to TWRP.
I'd appreciate any help. Thanks in advance!
It's possible it's because you have a different ROM (or version) installed on slot B. The userdata partition is shared between slots so trying to boot into the "unused" slot could potentially cause a boot loop.
But otherwise I'd guess your B slot has become corrupted somehow. I had a similar problem recently. You can fix it by reflashing both slots, see this thread.
Hi there!
i tried to flash TWRP, but eventually it got me to these problems:
1: there is no TWRP at all anymore, in slot A it just shows a black screen (no matter if i start system or recovery)
2: i cannot switch to slot B. and when i do, either it starts fastboot right away or it just restarts immediately and loads slot A again.
i tried to flash different TWRP versions to both slots, but no result.
what should i do?
anyone?!
Hi, what os you wanted to flash?... cause it feels like you Android is gone now...can you boot twrp from adb?try it...if you dont know how to do it...just ask...and feels like your final way is to use MSM download tool....good louck
And yes last but not least...DONT SWITCH SLOTS FROM TWRP... DON'T DO IT...NEVER...IF YOU NEED TO SWITCH SLOT JUST RESTART TO TWRP AGAIN...AND IF AFTER FLASHING TWRP YOU DONT FLASHED MAGISK YOUR TWRP IS GONE...
So here it is...your problem...read it...you switched slots manually...that is your problem...
James Blode said:
So here it is...your problem...read it...you switched slots manually...that is your problem...
Click to expand...
Click to collapse
so basically i have no other option but to flash it and wipe all data
I just screwed up when attempting an update. I had the update downloaded but did not install it.
Then I continued to install the A/B retention script and Magisk to the inactive slot and rebooted.
Now my phone fails to boot, and gets stuck continuously loading.
Is there something I can do in TWRP to resolve this?
You can try to flash the Magisk uninstaller in TWRP and see if it fixes your issue. Maybe you lost root on one partition and some Magisk modules that are still installed are putting your phone into a bootloop.
I'm unable to mount any partitions to get the uninstaller zip on my device. I was able to sideload the zip however the Magisk Installer was also unable to mount partitions.
Edit: I changed the slot from B -> A in TWRP then rebooted and it resolved this!
Mgssidley said:
I'm unable to mount any partitions to get the uninstaller zip on my device. I was able to sideload the zip however the Magisk Installer was also unable to mount partitions.
Edit: I changed the slot from B -> A in TWRP then rebooted and it resolved this!
Click to expand...
Click to collapse
Was just about to suggest that, glad you resolved it but you still have a broken slot, you should be able to fix it by flashing the rom, flashing TWRP and magisk, change slot and repeat. You might need a usb drive attached as changing the slot will usually made the data partition not visible so you won't see your files if they're on the phone.
To be honest, I thought flashing the stock rom will flash it to both slots (it shows this during flash) so I'm not sure what you did that broke it.
djsubterrain said:
Was just about to suggest that, glad you resolved it but you still have a broken slot, you should be able to fix it by flashing the rom, flashing TWRP and magisk, change slot and repeat. You might need a usb drive attached as changing the slot will usually made the data partition not visible so you won't see your files if they're on the phone.
To be honest, I thought flashing the stock rom will flash it to both slots (it shows this during flash) so I'm not sure what you did that broke it.
Click to expand...
Click to collapse
I'm actually on stock and doing an OTA update. After it booted up I was able to install the update, A/B retention script, and Magisk (to inactive slot). It rebooted successfully after that, should I still be concerned about a broken slot?
Edit: On closer look, Magisk did not install properly and I'm unable to access internal storage from TWRP to reinstall it.
Mgssidley said:
I just screwed up when attempting an update. I had the update downloaded but did not install it.
Then I continued to install the A/B retention script and Magisk to the inactive slot and rebooted.
Now my phone fails to boot, and gets stuck continuously loading.
Is there something I can do in TWRP to resolve this?
Click to expand...
Click to collapse
You didn't install the ota but you installed magisk to inactive slot?
Hello all,
Everything was working on my rooted oneplus 7 pro, until I applied the latest OTA update. Once that was installed and the phone rebooted, my once working mobile network was no longer working. The phone says no sim card detected and every few seconds the default phone app displays the force close crash dialog. Has anyone else encountered this issue? It looks like rolling it back to the previous OxygenOS version is the only solution, but I'm not quite sure how to go about that safely. Any help would be greatly appreciated.
The device is using Magisk and TWRP
I also tried uninstalling Magisk, but that did not resolve the issue.
Have you tried just doing a reset in settings?
.This is how I install stock oos
You can use MSM tool to revert OOS, or you can try this step:
1. Reboot twrp/lineage recovery, format data. Reboot bootloader
2. Fastboot boot into TWRP FBEv2
3. Sideload official TWRP 3.5.2.9-0 installer (found on TWRP website). Reboot recovery
4. Copy OOS 11.zip to internal storage,or copy to otg drive,Flash OOS 11.zip. Reboot recovery again
5. Format data in OOS stock recovery & Reboot
6. After boot into OOS 11, just local upgrade rom .zip again, you will have OOS on both slots
7. If root is needed fastboot flash magisk patched boot.img
I'll give that a shot today. Do you have the links to MSM and OOS11.zip ? Thanks
ChimmyChanga said:
I'll give that a shot today. Do you have the links to MSM and OOS11.zip ? Thanks
Click to expand...
Click to collapse
Index of /list/Unbrick_Tools
I don't have the oos 11 off hand , I know you can download the latest and greatest directly from OnePlus website under support
I have the same problem i cant do nothing
No SIM card, or No network available -- Any help would be kind and appreciated.
At the start:
Oneplus 7 pro - GM1915 /US- active t-mob sim
LOS 18.1 (latest)
magisk 22.x upgraded along the way to current magisk 25.2, 8.0.7 app
Running LOS recovery ##// no issues since 18.1 came out
USB 2.0 port(s), good'ol red/white cable(s). ##// verified cables/ ports.. typical troubleshooting to rule them out)
Current Platform tools in $PATH
Issue. No SIM card.
Steps to masonry school:
I upgraded my LOS 18.1(magisk 25.2 persistent) to oos 12, then went to LOS 19.1. The update(s) went fine, or so it seemed... Booted fine. Still rooted. All's good until reboot. Then no SIM card found.
Mess around with turning off wi-fi, nfc, mobile data turn on airport mode... all iterations of that..
Occasionally it saw the sim card! Says, "Network unavailable." Shows T-mob on sim 1... Thinks it has 2 sim cards... ##// can't help but think this might be something
Set APN T-mob blah blah... wait.. go to local t-mob verify my sim is provisioned properly get new sim..
Their take is(of course) it's time to upgrade lol... Got a spare $800 laying around? If not, you can pay for it after there is no longer a recession lol... I digress(in distress)
##//
I started having worse problems upon performing the next 19.1 LOS_11-13-22 ota.
Immediately I got into a bootloader loop. I first tried my patched_110622-LOS_boot.img and got nothing but a seemingly successful boot, then those lovely "Power Off" words and back to bootloader.
Once back in fastboot I changed partitions(keep in mind I have not flashed anything to alter the LOS 19.1 boot restructuring at this point. Reboot. Same outcome. Bootloader loop. Booting to recovery, start, power off or bootloader all do the same thing... quickly reboot into bootloader.
I then decided to boot to twrp. I went ahead and did this
#>/ fastboot getvar all ###/// yielding partition a
#>/ fastboot flash boot_a twrp.img
#>/ fastboot boot twrp.img
The screen goes to "fastboot mode" and hangs. power+up_vol & it finally boots into twrp.
I then twrp installed the LOS update, which lead to more bootloops. Various dalvik cache/data and cache wipes after flashing, factory reset won't complete the reset... I have exhausted my limits of attempts at this point, so off to MSM I am.
All versions/drivers correct. On a win10Px64 now. Connects fine.
Now this is where it gets odd(to me anyway). I tried to go to stock oxy10, for GM1911AA and it hangs on the param preload. Something I don't remember seeing since 2020'ish. Tried multiple firmware until it took one, that was H.30. Successfully flashed. Booted. Found SIM card. Thought that was it.. Then I unplugged my usb cable from the op7p and *poof * reboot. After much digging and changing metedata preloads, various things to try to get this thing to work.
Current:
I can get it to run LOS 19.1 No SIM card found. Rooted with twrp and magisk no prob.
Just can't get it to work with the SIM, whether seen or not.
I am suspicious that I should have used H.31 for the MSM... however now it won't get past param preload with anything earlier than 11.5.1 Oxy 12. Also, I even went so far as to try flashing the CB firmware variant to see if it would take the T-mob firmware. Won't let me, says not compatible. So now I have a rooted op7pro that can only communicate via signal lol.. and not long at that...
Any thoughts/help/direction/suggestions, would be greatly appreciated.