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 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?
from xda-developers http://ift.tt/2bDAA9h
via IFTTT
No comments:
Post a Comment