After updating from cm-10.1.3-find5 to cm-12-20150224-NIGHTLY-find5, I was stuck with the message Turing on Wi-Fi..., so I started playing around in TWRP recovery, wiping and reinstalling like a true noob. Eventually I was warned that "there is no system" and strode ahead where angels fear to tread...
Now I have CM12...NIGHTLY running, with no wi-fi, and cannot get to recovery. I've tried holding volume-down+power until my both thumbs and fingers are blue, but always return to the CM12 home screen.
Next, I used adb to install ROM Manager, but it can't update either Clockwork or TWRP since the wi-fi won't turn on.
However, I can use adb to fastboot and have tried flashing with recovery files of different types (Clockwork/TWRP).
But on reboot, the Find5 displays the logo waits and then displays the logo again and reboots to CM12.
I think something internal is broken:
adb logcat is reporting
F/libc ( 4873): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x8 in tid 4873 (gsiff_daemon)
So I'm attaching a bugreport. Any help is much appreciated!
Now I have CM12...NIGHTLY running, with no wi-fi, and cannot get to recovery. I've tried holding volume-down+power until my both thumbs and fingers are blue, but always return to the CM12 home screen.
Next, I used adb to install ROM Manager, but it can't update either Clockwork or TWRP since the wi-fi won't turn on.
However, I can use adb to fastboot and have tried flashing with recovery files of different types (Clockwork/TWRP).
But on reboot, the Find5 displays the logo waits and then displays the logo again and reboots to CM12.
Code:
fastboot reboot
adb reboot recovery
adb logcat is reporting
F/libc ( 4873): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x8 in tid 4873 (gsiff_daemon)
So I'm attaching a bugreport. Any help is much appreciated!
Aucun commentaire:
Enregistrer un commentaire