Database Info

[Solved] Phone issues, need help please!

Posted this in the CM10 dev thread, but decided I may get some better help by posting here, and here's my OP from the thread:
so yesterday my phone randomly shut off and it seemed to completely reset my phone. It booted up fine with two or three apps missing and all of my settings lost. I didn't think much of it until today when I tried to fix it. I did a fully wipe because some apps had disappeared and wouldn't download from the play store and wouldn't restore from TiBu. I went ahead and did the full wipe, flashed latest gapps and my device started up. I began trying to restore my apps and what not, but at I was navigating the phone my app switch soft key and home key would not function. They vibrate when pressed but don't do anything; only the back key works. I went to settings and remapped the soft keys to see if it was just a glitch and nothing changed. Still no function, only vibration. I then rebooted to recovery and did yet another full wipe and this time tried to install aokp just to see if it was a bug with cm (yes I know aokp i built from cm but I had just downloaded the latest nightly to my phone and deleted the old one so this was a test of the new nightly). Still no cheese. I was then thinking to myself, screw it and at least try to restore some apps, but after configuring my google account and opening he play store i get a constant no connection, retry button. Most of the stock apps will not even open. I flashed a TiBu.zip to restore the app and great, that worked but restoring from in TiBu doesn't work now. I tried reflashing cm and essentially repeated the above steps without any luck. Any ideas? I can't test my data/phone connection other than the fact that after setting up my google account, my email synced and I was able to make a call because the browser won't even open. MY [email protected]$s didn't do a nandroid either
Help a desperate guy in need, please!!
PS redownloading cm and gapps right now on my computer in case of a corrupted download, but to have the issue on cm and aokp is suspicious. I'll have to wait for an hour or two because my internet speed is that slow...
Click to expand...
Click to collapse
Now I redownloaded CM10 fresh from the get.cm page and even did a md5 check and everything matched up, yet still no luck. another strange thing I've noticed is that my power menu, when I verified in the setting that all options for my power menu were selected, the only options that show up are power off, reboot and screenshot. I checked to be sure app permissions were correct and even fixed permissions from recovery. All apps that do open force close upon any activity, for example upon receiving an email in gmail, the gmail app force closes. I don't know if providing a logcat would be beneficial to anyone because I don't know how to read them.
I am currently waiting on a sense rom to finish downloading to verify that it isn't just aosp based roms, but my internet connection is terrible so the 600+mb file still has 2+hrs left. I am also downloading an ruu if nothing else works, but again with a 500+mb file it will take 2+hrs
Any help is much appreciated and I can provide more info if needed.
SOLVED

Sounds like it might be a kernel issue. Try flashing a different one.
If nothing else works, relock and RUU.

iElvis said:
Sounds like it might be a kernel issue. Try flashing a different one.
If nothing else works, relock and RUU.
Click to expand...
Click to collapse
Even if it's the stock cm kernel? i never had issues with it before, but I'll flash one now because luckily I have a couple on my phone already
Edit: flashed a different kernel and nothing changed, but thanks for the suggestion

CyanogenMod Install Problems SGH-i727

Rooted fine a SII SGH-i727 samsung AT&T Skyrocket. I edited in-place the file to remove the reference for the phone model (prev. error on installation). Next repacked the zip with changes to the file. All looked good.
Copied files to SD card, rebooted holding vol/power. Able to browse using vol. keys to wipe data/rom, then install zip from SD. Waited a couple min. after no errors presented. Next updated the Google Play installer, waited again a couple just in case.
Turned off, then on, sits on CyanogenMod spinning circle forever and a day. Originally 25 min., then said OK, WTH?
Rebooted again, holding power down, then on, same just sitting there issue.
OK.... Repeated procedure again, wipe, this time did the davik and cache wipe, then installed zip, then Google. Reboot, STILL sits there on spinning circle for boot.
I don't get it. Several posts on this, but I redo, and get same results - insanity is setting in... Please advise, someone
I have my own computer repair business, but not as versed in Android/phones, at least to the OS/ROM level.

kmook said:
Rooted fine a SII SGH-i727 samsung AT&T Skyrocket. I edited in-place the file to remove the reference for the phone model (prev. error on installation). Next repacked the zip with changes to the file. All looked good.
Copied files to SD card, rebooted holding vol/power. Able to browse using vol. keys to wipe data/rom, then install zip from SD. Waited a couple min. after no errors presented. Next updated the Google Play installer, waited again a couple just in case.
Turned off, then on, sits on CyanogenMod spinning circle forever and a day. Originally 25 min., then said OK, WTH?
Rebooted again, holding power down, then on, same just sitting there issue.
OK.... Repeated procedure again, wipe, this time did the davik and cache wipe, then installed zip, then Google. Reboot, STILL sits there on spinning circle for boot.
I don't get it. Several posts on this, but I redo, and get same results - insanity is setting in... Please advise, someone
I have my own computer repair business, but not as versed in Android/phones, at least to the OS/ROM level.
Click to expand...
Click to collapse
I'm using the clockworkmod, v5.0.2.6, Gapps 4.2.2, and CM-10.1.2-skyrocket.zip

Make sure you have twrp 2.5 or 2.6 (ditch cwm , it's buggy for JB and modern roms)
Make sure you're radio is JB friendly i.e. UCMC1 or UXUMA7
Copy cm10 zip and google apps zips to your sd,int or ext doesn't matter
Reboot to recovery
Wipe system,data,cache,dalvik,preload,android secure (do twice,doesn't hurt and maybe better)
Install(flash) cm10.1.2
Install(flash) Google apps
Reboot system
Notes:
1.Search , as this (and related issues) been discussed Gazillion times
2.Do exactly as above
3.Be specific when describing problems , your post is like an app log !
4.There's a dedicated cm10 thread in general forum..

mahanddeem said:
Make sure you have twrp 2.5 or 2.6 (ditch cwm , it's buggy for JB and modern roms)
Make sure you're radio is JB friendly i.e. UCMC1 or UXUMA7
Copy cm10 zip and google apps zips to your sd,int or ext doesn't matter
Reboot to recovery
Wipe system,data,cache,dalvik,preload,android secure (do twice,doesn't hurt and maybe better)
Install(flash) cm10.1.2
Install(flash) Google apps
Reboot system
Notes:
1.Search , as this (and related issues) been discussed Gazillion times
2.Do exactly as above
3.Be specific when describing problems , your post is like an app log !
4.There's a dedicated cm10 thread in general forum..
Click to expand...
Click to collapse
WOW, THANK YOU!
It was the ther ROM writer that was the helper, TWRP! Didn't think that pgm was compatible with my phone, but found that it was, and it did the trick! Now I can go to bed, thanks again :highfive:

kmook said:
WOW, THANK YOU!
It was the ther ROM writer that was the helper, TWRP! Didn't think that pgm was compatible with my phone, but found that it was, and it did the trick! Now I can go to bed, thanks again :highfive:
Click to expand...
Click to collapse
Push the thanks button for him.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 4 Beta

Now reboots on phone calls!
OK, great, now it's working, but it reboots on making an outgoing phone call. Isn't the phone functionality the most important part?

kmook said:
OK, great, now it's working, but it reboots on making an outgoing phone call. Isn't the phone functionality the most important part?
Click to expand...
Click to collapse
No one else is reporting this. It's user error. Start over and follow the instructions.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 4 Beta

kmook said:
OK, great, now it's working, but it reboots on making an outgoing phone call. Isn't the phone functionality the most important part?
Click to expand...
Click to collapse
Found that it reboots while Google Voice is installed --- and activated to make calls using GV.
If I turn off that feature in GV, the call will attempt to go through, no reboots. Enable making all calls through GV, phone reboots!

nistocus sorrow
xcrazydx said:
No one else is reporting this. It's user error. Start over and follow the instructions.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah, thanks for that helpful hint --- read my other reply about this topic. :cyclops:
Found that it is the Google Voice App, when enabled on all calls, it reboots. Just found out now that when it's set to ASK, and I attempt to make a call, the call went through, without rebooting.

kmook said:
Yeah, thanks for that helpful hint --- read my other reply about this topic. :cyclops:
Found that it is the Google Voice App, when enabled on all calls, it reboots. Just found out now that when it's set to ASK, and I attempt to make a call, the call went through, without rebooting.
Click to expand...
Click to collapse
No problem, glad I could help!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 4 Beta

CyanogenMod 11

Bout damn time I made a thread
Sent from my SGH-T699 using Tapatalk

It IS about time.

ok so the cm wiki page says to use cwm. any reason i can't use twrp?

Gibson99 said:
ok so the cm wiki page says to use cwm. any reason i can't use twrp?
Click to expand...
Click to collapse
Shouldn't be any reason you couldn't use TWRP. I'm pretty sure nard himself uses it. The CWM was a CM project for a long time, and still the recovery built within it. Everyone pushes their stuff.

been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.

Gibson99 said:
been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.
Click to expand...
Click to collapse
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.

orange808 said:
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.
Click to expand...
Click to collapse
doh, you're right. my point still stands about messaging not matching the rest of cm's theming. i guess they expect people to just use chomp, go, handcent or whatever other app... i like the standard one in cm tho. except for how light it is.

What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?

I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?

Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?

Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
which build are you on? i'm running cm11-20140608-Snapshot-M7 (which is 4.4.2, not 4.3.3) and have no issues to report so far. i haven't given it a full shakedown yet - still haven't tried BT or GPS but so far so good. watched netflix on the bus this morning and never had an issue. my wife and i text a lot and haven't had issues w/ that either. this evening i'm going to try out BT with my elm327 obd-ii adapter and if i have time, test audio over an avantree cara adapter. i started google maps a couple times and it found me quickly and accurately but i haven't run gps for more than a minute or so at a time so i don't know how it'll do. maybe i'll turn it on while on the bus this afternoon and see if it works well for the whole ride home.

robuser007 said:
What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?
Click to expand...
Click to collapse
I updated ****. we're benefiting vicariously from the d2 kit-kat release
Sent from my Nexus 7 using Tapatalk

After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help

Balthasar85 said:
After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help
Click to expand...
Click to collapse
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk

reaper000 said:
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i second this. my steps were:
1- boot to download mode, install twrp
2- boot to recovery, flash CM
3- while still in recovery, flash gapps if you want them (make sure you have the correct version of gapps from the CM site)
4- still in recovery, wipe cache and dalvik
5- still in recovery, do factory reset
6- reboot normally (it's called 'system' in twrp) and start using phone
note that there is no need to copy/flash SU at any time because CM is already rooted.

using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).

robuser007 said:
using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).
Click to expand...
Click to collapse
Ok. Now, find out what version of cpu you have and get some logs to help them track down your problems.
There's a search box in the corner.
I don't have any of the problems you are describing and I am betting the developers do not, either.

orange808 said:
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?
Click to expand...
Click to collapse
I am on T-Mo, I get this via the default android messaging app as well as hangouts, but I also have times where mobile data refuses to work as well.
Right now, I'm having this issue on 11-20140608-Snapshot-M7-apexqtmo. I did wipe data and cache before I flashed. I'm not sure what is causing my issue.
I am tempted to reflash it back to factory, and take it back under my total care and get it replaced for a S5, but I really like my keyboard. :crying:

did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).

Gibson99 said:
did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).
Click to expand...
Click to collapse
I even tried that too. My phone's about a year and a half old now. I've noticed recently if the keyboard is out, or i'm holding the phone sideways, and I get a call, the phone app crashes over and over till i rotate it upward so the display is vertical, then it stops crashing(all while the phone is still ringing so I can still answer it.)

I'm having random reboots.

Hi,
I'm having trouble with my OpO since I rootet it. Here is the history:
-Day One: Just stock 25R, installed all Apps via google play, no problems whatsoever.
-Update 30O still no problems.
-Then I rootet the phone and flashed TWRP recovery to install the Titanium Backups of my old Nexus 4. Thats when I had the first random reboots. Some while Browsing in Chrome, Some on Youtube, Some while listening Music on Hedphones.
Since I have no Sim-Pincode activated a reboot just means, that I'm Offline for about 20 seconds but having that about 5 times a day just isn't acceptable.
-Then I got the 33R OTA update, which made my root and TWRP recovery disappear because I forgot to make a check in the developper settings, but that did not make the reboots disappear
-Today I flashed the 25R stock Image of the Firmware via Fastboot to set my One to real Factory status. I only installed apps via google play and recovered the app data of 2-3 apps via helium backup without root. I got the two OTA updates, and another reboot.
-Then I rootet the thing again, to use a logcat app, and now I have two logcats ending with a reboot.
I really hope that you can help me since I allready sold my old phone and expect that it will take really long until I get a new OpO here in Germany.
The next thing I will do is flash the 25R Image again and install the apps without using helium at all and leave out the goolors icon pack that I used before. But after that I'm absolutely out of ideas.
UPDATE: Yeah so it's definitely a HW defekt or something I cannot solve. I just wiped everything via TWRP, then flashed the factory image 25R without root and just installed some apps via google play. But after one hour I read an email and it rebooted....
Unfortunately I cant post the links to the logcats due to my low post count.

Logcats don't help you when it comes to finding out what is causing your phone to reboot. It is last_kmsg that is responsible for debugging reboots.
A hardware defect would not be causing your phone to reboot, its something to do with the way your phone is configured / set up.
I would highly recommend you to start from scratch completely and do the following,
- Flash XNPH33R http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip from scratch. Make sure you do wipe.
(OR.. flash a custom ROM after wiping)
- List all of the apps that you currently have installed.
- Are you using Xposed?
- Whats your set up? ROM/Kernel/Gapps/etc.

I am not using any custom Rom, root, custom kernel or xposed module.
I just wiped everything in TWRP and flashed the 25R factory image. After about one hour of installing apps in Google play and loging into account i got the first reboot.
I can try flashing the image that you postet tomorrow but thats the same Rom that Im using now

Ord3r66 said:
I am not using any custom Rom, root, custom kernel or xposed module.
I just wiped everything in TWRP and flashed the 25R factory image. After about one hour of installing apps in Google play and loging into account i got the first reboot.
I can try flashing the image that you postet tomorrow but thats the same Rom that Im using now
Click to expand...
Click to collapse
I meant, you can try a custom ROM and see if you can reproduce the problem. Custom ROMs are running on code that is much newer than CM11S.
Ensure you're on XNPH33R when it comes to OTAs.

I just wanted to add my frightful experience. I've had the OPO for two weeks now without problems and no random reboots. Had my first reboot today and just now my phone powered off and wouldn't turn back on. I plugged it back into the wall charger and it turned itself back on but was stuck on the boot logo. I tried holding down the power button to turn it off but nothing. Pressing the power button only turned the display on and off but still stuck on boot logo. Eventually I held down the power button and volume down and the phone buzzed and went to recovery. I'm on stock 33R and Franco's kernel. Haven't tweaked anything. Now I'm afraid my phone is going to brick itself.
Sent from my A0001

Yeah so this is definitely getting worse. At first I had 1-2 reboots a day but today after unplugging I already had 3 reboots in one hour.
I think I am definitely going to send it back when I'm back home next Week.
I already flashed stock Firmware 3 times and did what feels like 10 full wipes in one Week.
This cant be normal. Apps that I installed that arent in the top 50 in the play store are: Dailyme, yatse for xbmc, line, Wolfram aplha and ogyoutube.
That really sucks. I already sold my nexus 4 and have no other phone left
Btw: I'm on 33R for the third time this Werk. Everytime via OTA

Try a different Rom like crDroid + AK Kernel. Running this 2 things since 2 weeks and i only got one reboot just because my camera stopped working because in undervolted my phone ^^

THX but I just want a functioning phone. And since I have errors that nobody else has I think that it is a Hardware issue. At the Moment I am waiting for a answer from one plus so i can send it back

Ord3r66 said:
THX but I just want a functioning phone. And since I have errors that nobody else has I think that it is a Hardware issue. At the Moment I am waiting for a answer from one plus so i can send it back
Click to expand...
Click to collapse
ok I understand your frustration but to fully test your phone you will need to run stock and stock only with no outside apps loaded. Try and do this for a day or half a day or so and see what your results may be. Its your phone and of course do what you like but testing your phone and doing the same thing every time as in reloading your apps is not a good way of fully testing.
also did you do a last_kmsg report as recommended.

Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?

Ord3r66 said:
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Click to expand...
Click to collapse
Yes you need root. After a reboot just pull the last_kmsg file from /proc/ using adb, file Explorer of your choice, etc.
Sent from my One A0001 using Tapatalk

Ord3r66 said:
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Click to expand...
Click to collapse
of course there is a tutorial there is a tutorial for everything.... Got to utilize google my friend.

OKay it's me again. Meanwhile the Oneplus support answered my mails and told me to flash custom Kernels to resolve the issue.
Since Yesterday I tried three Kernels (Franco, Heeroluca and AK) and nothing changed, so now I start to gather some Last_kmsg files name it after the APP where the reboot occured and upload it here. Ofcourse I'm also sending those files to the Oneplus Support
Here is the first one:
https://dl.dropboxusercontent.com/u/43103242/1_Line_Messenger_last_kmsg
https://dl.dropboxusercontent.com/u/43103242/2_standby_screenoff_last_kmsg

Have the same problem. Using wi-fi -> reboot. Don't know how to fix this defect. I hope a solution will be found

Had a random reboot while browsing chrome. I was scrolling down the page and received a text at the same time when my screen froze. After freezing for a few seconds, it rebooted itself. I tried getting the last_kmsg but it tells me that it isn't found. The code I used was: "su" followed with "cat /proc/last_kmsg > /sdcard/last_kmsg.txt" in terminal emulator. Let me know if there is anything else I can do. Thanks!

I have also problems with chome beta browser. I get freezes. Is this issus only with chrome or with all browers?
Gesendet von meinem A0001 mit Tapatalk

Recovered from boot loop but constant crashes with older ROM

I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?

I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine

Jst flash a newer modem in recovery

mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.

PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.

Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine

KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.

Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.

Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.

mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.