Hello,
Anyone faced the problem of random reboots after getting root and know how to solve this issue (SM-G970F)?
I used the method of obtaining root on stock firmware - according to the instructions of topjohnwu through the magisk manager with a patch of the original AP of the native firmware.
Tried on:
latest firmware (Android 11) with magisk 21.4
November firmware (Android 10) with magisk 20.4
After installing SIM cards in the phone, it starts to warm up, the battery is discharged rapidly and the phone can spontaneously reboot at any time.
After digging more, phone self-reboot even on full stock rom if I insert or desactivate flight mode (in safe mode)
...that could be a chip issue...weird.
Related
Anyone know how to fix this problem? I flash using twrp 3.3.1.70 and using Magisk v20. Every time I root the oxygen os 10.1, it seems to work fine but only the wifi won't stick. From what I can tell the wifi won't connect to any network and after a brief search it shuts off automatically. I have a oneplus 7 pro 1917
It happened to me as well. Sometimes, the boot version is meant for a similar version but not the same, and the phone loses the drivers to the wifi. You might need to download the full original stock and flash it again to get the drivers back, however, you will need to deal on how to root it afterwards.
Have you tried
Rooting via flashing your phone with a pre patched boot img?? Then install magisk. Install twrp via magisk???
The only way I have been able to get this to work is use the MSM tool to stock firmware. I root the device and then manually update to 10.0.1, but when i restart, it gets stuck in a boot loop back to fastboot mode. to to get out of the boot loop, I use TWRP boot loop recovery, however, this also removes the rooted device.
Hi there,
after a few unplaned experiments this week I think it's a problem with the unlocked bootloader.
I have an unlocked BL and rooted Device via Magisk (V20.0.0).
1) After the first OTA my device did not restart with Qualcomm crash mode -> dm-varity - device corrupted.
2) I had reflashed my OP7 pro with the msm-tool back to 9.5.3AA. Then unlocked and rootet again. Everything worked fine.
3) OTA to 10.0.1AA -> No Wifi, unstable Bluetooth, No Speakers (Calling and Music/Video), Camera crashed and i regulary needed to reboot afterwards.
4) Again MSM-downgrade to Android 9, direct upgrade to 10.0.1AA with locked BL. Everything was OK (WiFi, BT, Speakers, Camera)
5) Unlocked again, then i has the same Problems as described on 3).
Can someone confirm if it's a problem with the unlocked BL.
Hopefully it is fixed with the next Update.
18os13 said:
The only way I have been able to get this to work is use the MSM tool to stock firmware. I root the device and then manually update to 10.0.1, but when i restart, it gets stuck in a boot loop back to fastboot mode. to to get out of the boot loop, I use TWRP boot loop recovery, however, this also removes the rooted device.
Click to expand...
Click to collapse
Hmm. .. if you have a TWRP..
WHY NOT just
1. Flash a 10.0.1 full rom
2. Flash TWRP INSTALLER
3. REBOOT TO TWRP
4. FLASH MAGISK??
5. REBOOT
---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------
etwas42 said:
Hi there,
after a few unplaned experiments this week I think it's a problem with the unlocked bootloader.
I have an unlocked BL and rooted Device via Magisk (V20.0.0).
1) After the first OTA my device did not restart with Qualcomm crash mode -> dm-varity - device corrupted.
2) I had reflashed my OP7 pro with the msm-tool back to 9.5.3AA. Then unlocked and rootet again. Everything worked fine.
3) OTA to 10.0.1AA -> No Wifi, unstable Bluetooth, No Speakers (Calling and Music/Video), Camera crashed and i regulary needed to reboot afterwards.
4) Again MSM-downgrade to Android 9, direct upgrade to 10.0.1AA with locked BL. Everything was OK (WiFi, BT, Speakers, Camera)
5) Unlocked again, then i has the same Problems as described on 3).
Can someone confirm if it's a problem with the unlocked BL.
Hopefully it is fixed with the next Update.
Click to expand...
Click to collapse
Nope.. unlocking the bootloader doesnt have anything to do wity your problem..
Hm.. have you tried the steps i mentioned above??
If you have magisk v20.. why not
1. Install twrp v70 via magisk..
2. Install magisk again (choose recommended)
3. Reboot to twrp
4. Flash a full android 10.0.1 rom
5. Re flash twrp installer
6. Reboot to twrp again
7. Flash magisk v20
8. Reboot.
I saw this in a kernel flash thread. It may help but can't confirm. Although I have run into similar issues after rooting then trying the no limits optimizations. I finally decided not to use it because it kept breaking my wifi and USB c audio. Try this maybe it will help?
From kirusakura kernel thread.
"Question: My WiFi is not working after flashing the kernel. I can´t toggle it on.
Answer: That means something happened to your device, that is causing some stuff to not get loaded properly when booting. I ran into the same issue once. Read through the thread to find the cause.
I wrote a guide in the linked thread, that explains step by step, how to return to a working condition without the need to wipe the phone completely.
Click the following link to find the post: post is linked here
"
santiagoruel13 said:
Hmm. .. if you have a TWRP..
WHY NOT just
1. Flash a 10.0.1 full rom
2. Flash TWRP INSTALLER
3. REBOOT TO TWRP
4. FLASH MAGISK??
5. REBOOT
---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------
Nope.. unlocking the bootloader doesnt have anything to do wity your problem..
Hm.. have you tried the steps i mentioned above??
If you have magisk v20.. why not
1. Install twrp v70 via magisk..
2. Install magisk again (choose recommended)
3. Reboot to twrp
4. Flash a full android 10.0.1 rom
5. Re flash twrp installer
6. Reboot to twrp again
7. Flash magisk v20
8. Reboot.
Click to expand...
Click to collapse
Problem is even when it initally roots after I restart it does not work anymore. The only way I have been able to do it somewhat successfully is through using an older version of magisk.
Hey guys the best and fastest way to resolve this is to install a custom kernel. Took me less than 5 minutes and it works now!
sonvotrung said:
Hey guys the best and fastest way to resolve this is to install a custom kernel. Took me less than 5 minutes and it works now!
Click to expand...
Click to collapse
Yeah for me it solved the problem. After the TWRP and Magisk install i didn't able to use wifi. But after i installed a custom kernel (arter97 r32) the wifi works again! Thanks!
Guys, I lost root after OTA from 9 to 10.0.1. To try to recover it I have done:
1. I reinstalled TWRP
fastboot flash boot twrp-3.3.1-71-guacamole-unified-Q-mauronofrio.img
Click to expand...
Click to collapse
On TWRP:
2. uninstalled Magisk using Magisk-uninstaller-20191102.zip
3. installed full OOS 10.0.1 OnePlus7ProOxygen_21.O.21_OTA_021_all_1910071446_6f7c731d5aa7dbe.zip
4. run the twrp installer twrp-3.3.1-70-guacamole-unified-installer-mauronofrio.zip
5. Reboot into Recovery twrp again without issue
6. Installed Magisk Magisk-v20.1.zip
7. Reboot into System
Root still doesn't work. What am I doing wrong?
PS: When my wifi broke after the update, I re-flashed the boot.img from OOS 10.0.1 OnePlus7ProOxygen_21.O.21_OTA_021_all_1910071446_6f7c731d5aa7dbe.zip and all worked fine.
haverlok said:
PS: When my wifi broke after the update, I re-flashed the boot.img from OOS 10.0.1 OnePlus7ProOxygen_21.O.21_OTA_021_all_1910071446_6f7c731d5aa7dbe.zip and all worked fine.
Click to expand...
Click to collapse
I flashed a Magisk-patched boot image and lost wifi, but the phone never gained root; I tried to reflash the stock boot image to fix the wifi but nothing has changed. I seem to be stuck with no wifi and no way to reflash anything in TWRP. Any ideas?
isellmidgets said:
I flashed a Magisk-patched boot image and lost wifi, but the phone never gained root; I tried to reflash the stock boot image to fix the wifi but nothing has changed. I seem to be stuck with no wifi and no way to reflash anything in TWRP. Any ideas?
Click to expand...
Click to collapse
I have moved away from OOS. Too many unknown apks. I am now using LOS17 no issues so far and GCam.
Hi all,
update: I made update at the end.
My OP7 version is GM1900, so far I was on build 10.0.6GM57BA with Magisk 20.4, but for some time I had 10.0.8 update notification.
Today I decided to update build.
I consider myself as medium experienced user the type that is using rather step by step guides.
But this time I thought I don't need guide cause I should remember how I did update last time. In the meantime I help my son to make homework what was an additional distraction.
I always download full OTA from oneplus.com support but it turned out there was no 10.0.8 (instead there was/is 10.0.7). So I tried to search for 10.0.8 and I found this xda news. As there is a mess with versions and links and I was doing it on mobile Chrome I accidentally tapped Global/India Full OTA
Steps I made:
1.1. Downloading file OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.2. Downloading official TWRP twrp-installer-3.4.0-0-guacamole.zip
1.3. Boot into TWRP.
1.4. Flash twrp-installer-3.4.0-0-guacamole.zip
1.5. Restart to TWRP
1.6. Flash magisk uninstall
1.7. Flash 10.3.5 (India & Global) - OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.8. Flash magisk 20.1 (but forgot to reboot after flashing TWRP it was first mistake I think)
1.9. Ended with 10.3.5 (India & Global) build with stock recovery and without Magisk.
Next I tried to return to GM57BA.
Then the steps I made:
2.1. Downloading official build 10.0.7.GM57BA from oneplus support site.
2.2. Downloading Mauronofrio's TWRP twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img and twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.3. Boot OP7 into fastboot then command "fastboot boot twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img"
2.4. After phone booted into TWRP I flashed twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.5. Restart to TWRP
2.6. Flashed magisk uninstall.
2.7. Flashed 10.0.7.GM57BA
2.8. Flashed magisk 20.4
2.9. Only then I rebooted to TWRP (I think it was mistake).
2.10. Then I saw first problem - there was no lockscreen security with TWRP (unlock pattern).
2.11. Restarted to TWRP again - the same no unlock pattern screen, no access to data partition
2.12. I started to panic and restarted into system.
2.13. I ended with hard bootloop - I mean I can't even do force reset (force reboot) by pressing and holding the Power and Volume down buttons at the same time :crying:
I'm sorry for this long description but I thought it will be helpful to diagnose what I messed up.
Questions and my thoughts:
1. Did I messed up by not restarting after last magisk flash?
2. What to do now? Do I need to wait for battery discharge? Then unbrick using MSM tool?
3. Is there any chance to repair and preserve personal data? I have TWRP backup about 3 months old. Maybe after battery discharge I should go to TWRP and then sideload this backup? Maybe magisk uninstall or stock boot image flash?
Please help
Update:
After battery discharge I managed to boot into TWRP recovery (Mauronofrio's 3.4.0.0)
Then couldn't access /data
But when I switched to Slot B and reboot to recovery situation is back to normal (I guess).
I'm still in recovery scared to boot into system.
What to do now?
kold11 said:
Hi all,
update: I made update at the end.
My OP7 version is GM1900, so far I was on build 10.0.6GM57BA with Magisk 20.4, but for some time I had 10.0.8 update notification.
Today I decided to update build.
I consider myself as medium experienced user the type that is using rather step by step guides.
But this time I thought I don't need guide cause I should remember how I did update last time. In the meantime I help my son to make homework what was an additional distraction.
I always download full OTA from oneplus.com support but it turned out there was no 10.0.8 (instead there was/is 10.0.7). So I tried to search for 10.0.8 and I found this xda news. As there is a mess with versions and links and I was doing it on mobile Chrome I accidentally tapped Global/India Full OTA
Steps I made:
1.1. Downloading file OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.2. Downloading official TWRP twrp-installer-3.4.0-0-guacamole.zip
1.3. Boot into TWRP.
1.4. Flash twrp-installer-3.4.0-0-guacamole.zip
1.5. Restart to TWRP
1.6. Flash magisk uninstall
1.7. Flash 10.3.5 (India & Global) - OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.8. Flash magisk 20.1 (but forgot to reboot after flashing TWRP it was first mistake I think)
1.9. Ended with 10.3.5 (India & Global) build with stock recovery and without Magisk.
Next I tried to return to GM57BA.
Then the steps I made:
2.1. Downloading official build 10.0.7.GM57BA from oneplus support site.
2.2. Downloading Mauronofrio's TWRP twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img and twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.3. Boot OP7 into fastboot then command "fastboot boot twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img"
2.4. After phone booted into TWRP I flashed twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.5. Restart to TWRP
2.6. Flashed magisk uninstall.
2.7. Flashed 10.0.7.GM57BA
2.8. Flashed magisk 20.4
2.9. Only then I rebooted to TWRP (I think it was mistake).
2.10. Then I saw first problem - there was no lockscreen security with TWRP (unlock pattern).
2.11. Restarted to TWRP again - the same no unlock pattern screen, no access to data partition
2.12. I started to panic and restarted into system.
2.13. I ended with hard bootloop - I mean I can't even do force reset (force reboot) by pressing and holding the Power and Volume down buttons at the same time :crying:
I'm sorry for this long description but I thought it will be helpful to diagnose what I messed up.
Questions and my thoughts:
1. Did I messed up by not restarting after last magisk flash?
2. What to do now? Do I need to wait for battery discharge? Then unbrick using MSM tool?
3. Is there any chance to repair and preserve personal data? I have TWRP backup about 3 months old. Maybe after battery discharge I should go to TWRP and then sideload this backup? Maybe magisk uninstall or stock boot image flash?
Please help
Update:
After battery discharge I managed to boot into TWRP recovery (Mauronofrio's 3.4.0.0)
Then couldn't access /data
But when I switched to Slot B and reboot to recovery situation is back to normal (I guess).
I'm still in recovery scared to boot into system.
What to do now?
Click to expand...
Click to collapse
To force restart I need to use power button and both volume keys..
To keep TWRP you need to flash rom, then without restart flash TWRP again, then restart TWRP, then flash Magisk.
Likely the r reason why your system doesn't boot is because it can't decrypt your data.
Why this happens I don't know, maybe in the upgrade they changed something related to the exception and then by downgrading again it isn't able to read it anymore.
I would suggest to:
Flash the latest rom.
Flash TWRP
Reboot TWRP
If TWRP then doesn't ask for PIN or password, then I'm afraid you have lost your data. I hope you have a backup.
I'm that case format (not just clear) data -> yes
Reboot TWRP
Then flash Magisk.
Thanks for reply.
Like I wrote in update after changing slot to b I managed to run TWRP with decrypted data, made even new new backup.
I also restarted into system and it occurs I'm still 10.3.5 (India & Global) GM57AA, so everything I flashed in with build 10.0.7.GM57BA was unsuccessful.
I think I messed with changing inactive slot procedure. Noob mistake I need to read about it.
kold11 said:
Thanks for reply.
Like I wrote in update after changing slot to b I managed to run TWRP with decrypted data, made even new new backup.
I also restarted into system and it occurs I'm still 10.3.5 (India & Global) GM57AA, so everything I flashed in with build 10.0.7.GM57BA was unsuccessful.
I think I messed with changing inactive slot procedure. Noob mistake I need to read about it.
Click to expand...
Click to collapse
I would suggest do restore your device with msm unbrick tool.
1. From recovery, turn off (i noticed, that when tried to turn off from somewhere else, the device would auto reboot later in downlaod mode)
2. In windows, turn off the connection & open device manager: Get this driver http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab
3. Press volume/down + volume/up, after about 5s connect to pc
4. Your device should show up in device manager, open it and install the driver manuell from step 2 (keep device options open... if fail you need to uninstall the driver before trying again)
5. Now wait for about 40s, if your device stays in download mode, you can open & start the msm tool (leave the options in msm as they are)
6. It will take about 280s, then the device will reboot.... (its normal that it stays longer at the oneplus logo at first start)
MSM Thread: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
I've also uploaded the 10.0.5OOS Unbrick tool on mega, because android file hosted downloads are so terrible: https://mega.nz/file/ArZFkYpS#Z_rOIwZeYN27IG6L8rOi-yfw8wXGiwvK-uWVDlsmvTI
Hello, I recently got an update on my OnePlus 7T Pro. I dowloaded the update and I forgot to install it before installing magisk to the inactive slot via the magisk app.
Now my phone won't boot. It just boots up reboots and then goes into like recovery or some black screen with white text and minimal options.
Does anyone know how I can fix this?
At first I tried to flash a new boot.img because I thought it might be wrong. But that didn't fix it. Instead I had to flash the stock rom again to make everything work. And now my phone has booted up again with all data still there since I leave my bootloader unlocked.
I followed this tutorial:
[ROM][STOCK][FASTBOOT][OP7TP] Stock Fastboot ROMs for OnePlus 7T Pro
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are...
forum.xda-developers.com
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.
Hello
My phone has been rooted for a while now (without TWRP as it wasn't available yet back when I rooted it), but magisk suddenly got issues once I've tried to update my phone.
I downloaded the update KB2003_11_C.33 as soon as it was available on the Oxyen updater app, then i've proceeded to follow the usual steps to preserve root during the OTA update:
restored image in the magisk app -> started the update -> installed magisk to inactive slot in the app
I don't know if it had a real impact, but this time I've done the update through the settings of the phone instead of through the "System Update" app.
Once the phone turned off and back on, it was stuck in a bootloop (it rebooted maybe 3-4 times) until I pressed the buttons to access the Recovery mode, then I just booted it again and it somehow worked just fine. There seemed to be no issue until I opened the magisk app and saw the message "The hidden Magisk app cannot continue to work because root was lost. Please restore the original APK" then I've also noticed that my OxygenOS version was KB2003_11_C.21 instead of 33, so the update basically failed.
I'm not sure if it matters, but I've recently installed modules (Advanced Charging Controller, BlockAds and Universal SafetyNet Fix), magisk manager was hidden (I had access to the app through a fake "settings" app) and I also had zygisk, as well as the deny list enabled to pass SafetyNet.
I've uninstalled/reinstalled Magisk manager, patched the boot.img with it (extracted from the ZIP of my current firmware) then flashed it with adb (several attempts), but magisk manager just doesn't detect anything as it keeps displaying "Installed N/A". I also tried to update my phone again to KB2003_11_C.33, which worked fine this time around, but patching the image and flashing it still didn't do anything.
I don't know what to do anymore to root my phone, I thought I didn't need to factory reset since the bootloader is still unlocked, but maybe I have no choice now.
I found the issue myself actually, I had no choice but to install unofficial TWRP to properly uninstall magisk then to reinstall it and root the phone.
You can close the thread ^^