EDIT: Disregard the rest of the post. Restoring the stock ROM and then installing the OTA apparently fixed the issue for me.
G7 Power user here, with Magisk.
Recently I tried to install the new OTA update, so I followed the Magisk tutorial with the Uninstall -> Restore Images, then Install -> Install to Inactive Slot and all that. Magisk had some issues unpacking the zip at first, but it eventually worked, so I rebooted as per instructions.
Then I got bootlooped. I was warned that might happen once or twice after updating, but no, this was a genuine bootloop, lasted forever. Disheartened, I figured my only option was to reflash the stock ROM completely (as flashing just the unpatched boot.img didn't help) and work my way up from there again.
But when I did that, suddenly my phone stopped detecting my SIM card. No matter which slot I put it in, no matter how many times I turned the phone on and off, the airplane mode on and off, it remained unresponsive. My IMEI is blank, even when I use the *#06#. Dialing the *#*#64663#*#* code, which I've seen as a suggestion to solve the issue, doesn't work either, it just returns me to the dial-up screen.
I've tried every solution I could find online. Some of them led me to more bootlopping, some of them simply added a "system integrity compromised" message that prevented updates and most had no effect. I'm not sure where the problem lies in the first place... Any ideas on what I could do? Any help would be much appreciated.
Related
Hello fellow xda-ers,
I have a OnePlus One, but i cannot seem to update the phone.
What is the exact problem?
- there is a system update ready, so i download the update and it asks me to install and then it tries to reboot
- the phone shuts down and doesn't reboot, i have to manually turn the phone off which makes the update sequence stop.
- the phone tells me again theres a update, but it doesnt reboot after it shuts down.
- even just giving the phone the command to reboot, just shuts the phone off and the phone doesn't reboot.
What did i try?
- via oneplus toolkit (mac) i flashed it to stock default, but still the problem persists.
- i flashed a 5.1.1. firmware straight from cyanogen mod, but still the problem persists.
- i flashed a custom recovery (while unchecking the update cm recovery), but the problem still persists.
I don't know what to do... Anybody have advice? It would be much appreciated.
I am pretty aware of what to do and not to do, i have been flashing phones since the iPhone 3gs. But this is just odd.
I was having similar problem. Except mine was booting into the bootloader. From there I tried to manually install the update. It kept failing so I gave up. Then about a week later (today) I let it try to install and it seemed to be working, except when it finally booted back up, it had completely wiped my phone!!! Now I'm midway though reinstalling all my apps and it gives me the "There's an update available for you phone". So apparently it didn't even update in that process.
I've got the exact same problem here.
Hi! Long story short: My oneplus one has started to behave weird since last month.
I was on cm13 latest nightly and boeffla kernel.
Device worked great UNTIL you perform a reboot. (I had liveboot app installed and the log started to show an abnormal error code causing a bootloop. "unable to open mixer card 0, then 1, then 2 and so on. )
Every time i reboot and this error starts, it bootloops, or starts. But when boeffla kernel default settings apply, device freezes and shutted off. (I checked this by changing the time that boeffla app waits until it applies default config).
At first i thought a clean flash was needed, i usually dirty flash nightlies and some times i start over with a clean flash.
I identified that this error " mutes" the device and causes audiofx app to FC until the phone dies.
I related this to the thread "brickloop EFS corrupt" but i didnt have any time to try anything.
Last week device shutted of because of low battery and hard bricked itself. (Well, qdloader 9008. Not a hard brick, properly speaking but there is a fix with the chinese colorOS zip)
Now this is the first weird thing... Devices dont just hardbrick itselves.
But battery was dead, really dead, and caused the mbn image flashing in the chinese tool to loop and device connect and reconnect on every attempt to flash this first file. (For those experiencing this issue i can confirm is the battery dead, and sahara error code is a corrupted file on the folder).
I have another oneplus one, so switched batteries and was able to flash the damn thing.
Now, back from dead i had none imei, baseband, bluetooth or wifi and audioFx FC.
I tried reflashing the persist, reserve4, modem1 and 2.
I tried formatting mmckbl0p15 with terminal command.
I installed colorOS, then switched to cm12 and got back my baseband, but still none of the other things.
I downloaded the "nightmare fix" full folder from the brickloop thread and followed the steps. No result on any flashing attempt.
On a random cm12.1 flashing attempt i got back wifi and bluetooth and imei showed now "0"
Using the "el hechizero" method i had rewritten the imei number with QPST and got the signal back and sim card detection. But it looped from "no sim" to "no service" all the time.
From there, i fastboot flashed cm11 44s and got everything running. Wifi, sim card, bluetooth, imei. All except audio. Device is mute, audiofx FC. And i have to reboot it several times until i get it working.
Now i am where i started. Stuck on cm11 44s. Any other rom flashing causes a hardbrick if i go with fastboot. And if it boots, something will not work, wifi, or sim detection. And audioFx FC on ANY rom (after 10 or 15 reboots it works until i reboot again) and random shut downs. (Not reboots, device just freezes and shuts off)
Of course i dont have a EFS backup, just another oneplus one that works like a charm running cm13 and boeffla.
I tried MANY things. It only leads to qdloader or faulty roms. Cm11 44s works stable enough as long as i get it to boot with audio and keep the phone charged.
Anu suggestions? Maybe i should start to think about a faulty motherboard?
I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
shagexpert said:
I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
Click to expand...
Click to collapse
I had the same issue when I first got my 6 when I was playing around with the slots. Also my original TWRP install for some reason would crash and reboot whenever I plugged in the data cable while in TWRP. I ended up flashing back to stock OOS 5.1.5 through fastboot (used the flash-all command) and then reinstalled TWRP and everything has been working great since then.
MickyFoley said:
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
Click to expand...
Click to collapse
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
To be honest I didn't know they did the same thing (magisk and Super SU). I am curious now, what if I factory reset my phone and attempted to install Super SU instead of Magisk this time?
If I do a factory reset (let's say I want it just like it was out of the box and I format the data partition as well), will I need to root the phone again? I am asking because I don't know which part of the instructions I should ignore. I am sure TWRP will already be installed after the reset so I would only need to install the extra apps...
You don't have to format data. Just factory reset it. Then use "fastboot boot twrp.img", don't allow modifications, flash a kernel you want (if you want one - I really recommend ElementalX) and then the latest version of Magisk (16.4 BETA currently). Did so - all fine. And yes: Even Titanium Backup works without any issue with Magisk.
We had similar problems with TWRP on the Razer Phone when it was new. We solved the problem by using the TWRP boot image to flash the stock boot image and then flashing a TWRP zip. I just got the OnePlus 6 yesterday and haven't really messed with it yet but everything sounds the same to me so far.
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
shagexpert said:
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
Click to expand...
Click to collapse
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
shagexpert said:
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
Click to expand...
Click to collapse
When your phone booted straight into that mode with black screen and the led, then you bricked it. Same happened to me 2 days ago. The solution was to use the Msmtool from another thread and it worked great. Just follow the guide. But it will wipe your device. And you have to install oxygenos manually via "local upgrade". If you have a question, just ask
What I ended up doing was restoring from the backup I had. This was the "bad backup" without WiFi and broken finger print and facial recognition. After the restore, I did a normal wipe (not advanced). This reset the phone to factory settings. Once I configured WiFi and signed into my Google account, Google offered to recover from a cloud backup of my One Plus - I didn't know Google made these backups. It downloaded all the apps automatically. I don't know yet if I have sign into all of them all over again.
The bad back up saved my ass, I wasn't even planning on making it. I was just testing the backup feature. That's why you should always do a backup, even if the device isn't in ideal configuration.
shagexpert said:
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
Click to expand...
Click to collapse
I rooted my phone with Magisk and installed the 5.1.6 via OTA (and reroot via installed Magisk Manager). So no need to install TWRP so far.
Titanium Backup runs flawlessly with Magisk (already on my OP 3T and my OP 5).
So give Magisk a try, I never had such an easy and reliable update as the one from 5.1.5 to 5.1.6
Helium is a great alternative to titanium.
I was trying to root my main driver, a Google Pixel 3 running the most recent version of Android. Initially I was going to flash TWRP and then install Magisk, but TWRP for some reason wouldn't flash, so instead I went about trying to go about the Magisk Canary route. I patched the boot image of the most recent Pixel 3 update and proceeded to flash that in the bootloader. That is when everything went wrong. When the phone rebooted, I found that my touchscreen was no longer working. I tried flashing the boot image using platform tools in the bootloader, but I deleted the -w line in flash_all.bat to prevent a full reset; however this did not solve the issue as I had hoped. I then went into device recovery mode and tried the factory reset option there, but that did not work either. The phone booted and I was in the setup screen with no way to press the buttons using the screen, so I connected an OTG USB device to set the device up only to find that the WiFi is not turning on. I believe there are issues with the mobile network as well as I put in a SIM card but it wan't able to connect to the network; however it did read the SIM card successfully as I was able to "turn on" mobile data. I cannot enable USB debugging to flash anything because I cannot allow the computer's USB debugging request; I either have the computer or my OTG device plugged in. Any ideas on what to do? Thank you in advance!
i have almost the exact problem.
could someone please help
Sounds like the option is, factory image flash-all with the wipe. I believe the OP did not disable/remove modules from magisk before updating. That is something that we all should be aware of at this point. Cost me two bootloops and complete resets, but I learned my lesson. Also backup your stuff. I lost a few pictures, but most of my data and such were restored through Tibu.
Okay. I was messing around with my firmware which I've done in the past. I've had a few problems then due to my phone model being obscure (Samsung Galaxy S6: SM-S906L). I've always had a copy of the firmware saved to my computer in the event of a bootloop or a similar issue, I figured I could just flash it with Odin to fix it. I have also done this in the past. After accidently wiping my phone, I went to re-install Magisk, but noticed my phone trying to push an update. I let it go through without much though and after it finished saw it didn't change much. I carried on with re-installing Magisk when I figured I might as well fix some problems I had with booting the phone (I would have to boot it into download mode then recovery to get it out of a bootloop each time I turned it off). I carried on with flashing my saved firmware to fix the problem. Everything flashed fine except the bootloader. It's come to my understanding now that because I let the update carry through with my phone, my saved firmware is no longer compatiable dispite the fact that it didn't change my android version. So now I have a bootloader installed that is meant for a higher update without my known ability to downgrade. Due to the obscurity of my phone model, I can't find anything to bring my firmware up to what my bootloader is at. So now my phone is stuck in a bootloop with the ability to access download mode, but recovery mode simply gives me a "recovery is not seandroid enforcing" error. I would greatly appreciate it if someone has any advise they could give me.