I am on my second moto G 2015 from koodo now and this one random reboots like the first one. I seem to have tried nearly everything but may have a log with the answer this time. Any help appreciated.
Another reboot log
Got another reboot an hour later. Here's another log. These reboots happen no matter what rom.
"Fatal signal 11" is the key here, it's a segmentation fault, meaning that the program (libc in this case) accessed a memory location that was not assigned... Since libc is a core library, this should go back to the CM team as a bug report, there is nothing you can do about it.
Of course, this is assuming you have done a clean flash with recommended Gapps, and not restored any data from TiBu or any other tool, if you have you need to do that first to verify it is not an app conflict.
acejavelin said:
"Fatal signal 11" is the key here, it's a segmentation fault, meaning that the program (libc in this case) accessed a memory location that was not assigned... Since libc is a core library, this should go back to the CM team as a bug report, there is nothing you can do about it.
Of course, this is assuming you have done a clean flash with recommended Gapps, and not restored any data from TiBu or any other tool, if you have you need to do that first to verify it is not an app conflict.
Click to expand...
Click to collapse
Thanks acejavelin. I did a clean flash many times and didnt install any additional apps. I even restarted in safe mode to confirm that an app wasnt the cause and still got reboots. I tried with both open gapps and dynamic with same results on two different phones. Even tried a new sim card.
jackching said:
Thanks acejavelin. I did a clean flash many times and didnt install any additional apps. I even restarted in safe mode to confirm that an app wasnt the cause and still got reboots. I tried with both open gapps and dynamic with same results on two different phones. Even tried a new sim card.
Click to expand...
Click to collapse
Then I would suggest opening a bug report with the Lineage team (I'm guessing it's latest LM already from logs).
acejavelin said:
Then I would suggest opening a bug report with the Lineage team (I'm guessing it's latest LM already from logs).
Click to expand...
Click to collapse
I posted my logs in the lineage thread if thats what you mean. It is the latest but also happens with aosp roms.
jackching said:
I posted my logs in the lineage thread if thats what you mean. It is the latest but also happens with aosp roms.
Click to expand...
Click to collapse
This could be a hardware glitch too... We have started seeing a few Moto G 3rd Gens where the emmc chip is starting to fail, not sure if it's a poor quality nand chip or just a fluke, but seen probably a dozen or so in the last couple months fail. That could cause a similar error if it is inconsistent.
acejavelin said:
This could be a hardware glitch too... We have started seeing a few Moto G 3rd Gens where the emmc chip is starting to fail, not sure if it's a poor quality nand chip or just a fluke, but seen probably a dozen or so in the last couple months fail. That could cause a similar error if it is inconsistent.
Click to expand...
Click to collapse
Thats what im starting to believe it is. I've did a lot of research and tried pretty much everything it seems. That is probably why koodo is selling them as "Certified pre-owned" phones. I sent my first one back and they replaced it with another pre-owned that is doing the same thing. I see reports of it on google happening to different gen moto phones but dont seem to be any solid answer for it.
Factory firmware
acejavelin said:
This could be a hardware glitch too... We have started seeing a few Moto G 3rd Gens where the emmc chip is starting to fail, not sure if it's a poor quality nand chip or just a fluke, but seen probably a dozen or so in the last couple months fail. That could cause a similar error if it is inconsistent.
Click to expand...
Click to collapse
After wiping my phone completely and putting on factory firmware, i havent gotten a reset once in two days while running the factory firmware. I dont really understand why it wouldnt reboot now. Are there parts of the software that stays on the phone even after a total wipe? Should i be installing factory firmware between each rom install? I never had this type of problem with xt1032 (falcon). I always do a full wipe between roms.
Related
Hello guys,
my brand new nexus 5 just came back from replacement and worked flawlessly for a week or two,
The thing it that after the update, i had this strange "Stuck at turning wifi on bug".
I tried everything i saw on all the forums i managed to find and google usually tell users to replace their devices.
The thing is i just flashed the radio-hammerhead-M8974A-1.0.25.0.17 Radio, and at reboot i was able to turn wifi on.
The main problem now is, that the device freeze 15 second after succefully showing me nearby wifi networks, and then proceed to reboot.
I think many users are in the same situation, has someone managed, somehow, to patch the error ? I can't even tell if this is a software or hardware related glitch, but more and more users are experiencing troubles and i think google should talk more about it.
The majority of users don't have this problem. I don't. What else have you done to the device? What have you flashed?
Sent from my Nexus 5 using XDA Free mobile app
no such issues here.
I've seen this issue on various phones and it's always been either:
1) Dodgy /data (user data, apps etc)
2) Hardware problem.
I have not had this issue on the N5
jd1639 said:
The majority of users don't have this problem. I don't. What else have you done to the device? What have you flashed?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Of course i did not mean that all users where on the same case,
what i said, is that i already found many thread of people experiencing the same "undefined behaviour", which mean this is not a random bug, and that it can definitly happen to anybody's device.
My phone was using the last stock rom, the bootloader was locked and it never was altered in any ways when the problem started to appear.
Then, i did a hardreset, i unlocked the bootloader, i flashed custom roms (PA, MIUI, CYANNOGEN), then i flashed an older rom's radio image and the wifi started to activate again, but to reboot 15 sec after.
then i went back to a PA rom, and exactly the same bug occur.
weacd said:
Of course i did not mean that all users where on the same case,
what i said, is that i already found many thread of people experiencing the same "undefined behaviour", which mean this is not a random bug, and that it can definitly happen to anybody's device.
My phone was using the last stock rom, the bootloader was locked and it never was altered in any ways when the problem started to appear.
Then, i did a hardreset, i unlocked the bootloader, i flashed custom roms (PA, MIUI, CYANNOGEN), then i flashed an older rom's radio image and the wifi started to activate again, but to reboot 15 sec after.
then i went back to a PA rom, and exactly the same bug occur.
Click to expand...
Click to collapse
Flash a full factory image back to latest stock. If it still happens, send it for repair
rootSU said:
Flash a full factory image back to latest stock. If it still happens, send it for repair
Click to expand...
Click to collapse
Already done, guess i have no choice.
Then i would like to tell all the peoples who are experiencing the same experience to replace their phone using google's warranty service.
Some peoples managed to fix the bug for a time with a lucky trick, but it always end to come back.
weacd said:
Already done, guess i have no choice.
Then i would like to tell all the peoples who are experiencing the same experience to replace their phone using google's warranty service.
Some peoples managed to fix the bug for a time with a lucky trick, but it always end to come back.
Click to expand...
Click to collapse
If it comes back while on stock rom then it's a problem with the device and you should rma it. That's what warranty is for
Sent from my Nexus 5 using XDA Free mobile app
First of all sorry for my English....
Flyme OS and the experimental port of Sense are the only android based roms that works on my (i guess) hardware bricked Nexus 5 (moisture maybe); Sailfish, B2G and Ubuntu Touch works too (everythig that can work), but the stock rom and other android based roms screen locks as soon configuration starts (usually touching in "next" after selecting language) and the power button no longer unlocks. I'm trying to find the differences between Flyme and other Roms, especially in the framework-res.apk, to port this to a stock or cm rom (on which is based flyme) but I'm a little lost...
Flyme Os is stable and daily use, the only error message that it shown when boot is "cannot load native library cpu arch invalid for this build", but then use it normally
Thanks in advance, for any idea
Have you tried flashing stock with fastboot?
Yes, of course, in every way, even with the flashtool lg and factory original image .tot and D820 DLL (process that also closes the bootloader)...
So you've done this... With fastboot?
http://forum.xda-developers.com/showthread.php?t=2513701
And what errors did you get?
KJ said:
So you've done this... With fastboot?
http://forum.xda-developers.com/showthread.php?t=2513701
And what errors did you get?
Click to expand...
Click to collapse
Yes, same error: the screen locks when i touch "next" in language selection and no longer responds.
So fastboot installed everything without error?
Just wanna be sure you successfully installed stock. Which image did you use?
KJ said:
So fastboot installed everything without error?
Just wanna be sure you successfully installed stock. Which image did you use?
Click to expand...
Click to collapse
yes, entire process without error
I use any official found in https://developers.google.com/android/nexus/images
So after flashing stock, it freezes during setup? Very strange. I can only guess that those other OS's messed up your partitions.
I'm not sure what else you can try. Did you fastboot erase system, user data and cache first?
And have you asked others in the threads for those oddball OS's if they had issues like yours?
KJ said:
So after flashing stock, it freezes during setup? Very strange. I can only guess that those other OS's messed up your partitions.
I'm not sure what else you can try. Did you fastboot erase system, user data and cache first?
And have you asked others in the threads for those oddball OS's if they had issues like yours?
Click to expand...
Click to collapse
Very strange, yes. I also think it's an issue of partitions, damaged sectors or any where the stock image using to store settings or something...
I asked in a thread Flyme, about major structural changes that i can carry a stock rom, but no response yet
KJ said:
So after flashing stock, it freezes during setup? Very strange. I can only guess that those other OS's messed up your partitions.
I'm not sure what else you can try. Did you fastboot erase system, user data and cache first?
And have you asked others in the threads for those oddball OS's if they had issues like yours?
Click to expand...
Click to collapse
Sorry, i don´t undertand. Such other operating systems were installed once the problem was presented. First the original stock android (from the box, only updated by ota) started having problems, autolock randomly. Then reinstall the factory image (in every way) and still failing so I went back to using my Nexus 4 and began to try other Roms and OS's. Until I arrived at the only functional rom based on android that not autolock, Flyme...
ferozzzz said:
Sorry, i don´t undertand. Such other operating systems were installed once the problem was presented. First the original stock android (from the box, only updated by ota) started having problems, autolock randomly. Then reinstall the factory image (in every way) and still failing so I went back to using my Nexus 4 and began to try other Roms and OS's. Until I arrived at the only functional rom based on android that not autolock, Flyme...
Click to expand...
Click to collapse
What you have is DOA, look at the logs after you installed flyme os and check sd card for errors/repartition (mentioned before). But i would just change the device using DOA warranty. Dont forget to reset the tempered flag afterwards.
nbite said:
What you have is DOA, look at the logs after you installed flyme os and check sd card for errors/repartition (mentioned before). But i would just change the device using DOA warranty. Dont forget to reset the tempered flag afterwards.
Click to expand...
Click to collapse
Its not DOA, it works for over 7 months, I think that are bad sectors
attached logcat
Im not sure whats happening but it looks like your lollipop preview isnt booting with multirom. I can see the i/o error but im not sure whats causing it.
sd 0:0:0:0: [sda] Unhandled error code looks like drive is failing. Also some wifi problems but dont think thats the reason. 70% sure its the drive. Check reformat or replace. Good luck man!
nbite said:
Im not sure whats happening but it looks like your lollipop preview isnt booting with multirom. I can see the i/o error but im not sure whats causing it.
sd 0:0:0:0: [sda] Unhandled error code looks like drive is failing. Also some wifi problems but dont think thats the reason. 70% sure its the drive. Check reformat or replace. Good luck man!
Click to expand...
Click to collapse
Already formatted it, ran e2fsck (with verbose: no bad sectors), I'll wait for the final version of lollipop, if I keep using FlymeOS until I get a motherboard at reasonable price in Argentina
ferozzzz said:
Already formatted it, ran e2fsck (with verbose: no bad sectors), I'll wait for the final version of lollipop, if I keep using FlymeOS until I get a motherboard at reasonable price in Argentina
Click to expand...
Click to collapse
It either the nand or the nand controller or software thats causing bad block (going to stock, flashing everything correctly, reflashing kernel, radio etc). Very little chance of it being a software fault since it persists on different roms. Good luck!
G'day people I've run into something pretty weird with my OnePlus One. I installed the CM12 nightly and booted it up, ran it for a few hours then got ghost touches and the screen became unresponsive at times.
So, having my usual backup of CM11S, I wiped and restored to the latest backup I had and everything was weird. I kept getting ghost touches and reduced responsiveness, and sometimes it would just randomly malfunction and not unlock and just keep the screen off.
Rebooting clears up the problem for about 5 minutes and then it comes back at full blast.
I tried installing the last CM11S update via flashing Calkunins stock XNPH44S zip and still I have all these weird issues that wasn't there before I flashed the CM12 nightly.
Has anyone come across this problem or is it just me and my device? It's seriously a cause for concern, and I'm posting this to both XDA and the OnePlus forums in hopes of getting some sort of help and relief in this situation.
Any assistance is appreciated and I thank you in advance for taking the time to read this.
reflash cm12 nightly and try again.
perhaps use fastboot to flash the partitions .
You might need to find a copy of the first cm11s rom and try that one. I have a feeling your one of the unlucky with firmware sensitivity.
Which date is your phone from? (its on the box)
Sent from my A0001 using XDA Free mobile app
GO back to completely factory fresh, via fastboot commands.
If you still have problems, it's a hardware issue then.
kthejoker20 said:
GO back to completely factory fresh, via fastboot commands.
If you still have problems, it's a hardware issue then.
Click to expand...
Click to collapse
not entirely true, there are different screens, that could be the issue. It was reported in boeffla kernel thread. sesrch throught it and it might contain something useful to try.
also open a support question, Oneplus needs to know how annoying their poor choice of different lcds are
Sent from my A0001 using XDA Free mobile app
bachera said:
reflash cm12 nightly and try again.
perhaps use fastboot to flash the partitions .
You might need to find a copy of the first cm11s rom and try that one. I have a feeling your one of the unlucky with firmware sensitivity.
Which date is your phone from? (its on the box)
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I'll try to flash CM11S via fastboot to see if it clears up the issue. For now, the date I got mine is 2014-07-16. Shipped to me after 12 days (International shipment via courier)
UPDATE
Flashing CM11S via fastboot resolved all issues as far as I can tell.
Will remain on the lookout for the bugs in the future but for now I'm happy to say it worked for me.
Thank you all again for the advice and guidance, it was appreciated.
GLad it worked for you.
I love when other posters try to punk you when you try to help people.
kthejoker20 said:
GLad it worked for you.
I love when other posters try to punk you when you try to help people.
Click to expand...
Click to collapse
Nobody was trying to "punk" you. There are usually several different potential causes for the same symptom, all he was doing was highlighting that and adding extra information in order to help further (in the case that flashing the stock images didn't help, which has happened many times). He was also trying top help the OP. Calm down.
Transmitted via Bacon
timmaaa said:
Nobody was trying to "punk" you. There are usually several different potential causes for the same symptom, all he was doing was highlighting that and adding extra information in order to help further (in the case that flashing the stock images didn't help, which has happened many times). He was also trying top help the OP. Calm down.
Transmitted via Bacon
Click to expand...
Click to collapse
I thought it was the partition thing too because I had almost the same problem on my HTC Amaze back in 2014, and flashing the OEM RUU helped with sorting things out.
But as for the random screen touches, flashing everything from fastboot helped for only a few hours. The symptoms came back after a while, specifically when I replaced my music and pictures. I'm thinking that I may have a corrupted file on it somewhere but I doubt it'll cause a malfunction like that.
So I tried flashing Franco Kernel, and it seems to have cleared it up..... for now.
It's so frustrating thinking that my device may be defective
UPDATE #2
Flashing Franco Kernel didn't help. Symptoms came back within a couple hours. Will try a custom ROM, specifically AOPK (because I want to )
If that doesn't fix the issue then I've just got to face the fact that I have a defective device (somehow)
Bump
Nothing worked. I contacted the manufacturer but they seem to think doing a factory reset will help. It didn't.
Flashing CM11S via fastboot doesn't help
I really think this is a hardware issue that just emerged from nowhere, probably due to lack of premium or standardized quality adhesive.
There's a really long thread over at the OnePlus forums about a guy who found it was a grounding issue and took some adhesive tape to insulate the area near the proximity sensor (I think? I'll include the link in here somewhere)
Honestly, OnePlus impressed me....at first. But I cannot use a phone that's not working properly.
https://forums.oneplus.net/threads/...-hint-it-was-never-a-software-problem.186235/
Same problem here... I had the first ghost touches after having installed CM12 Nightly.
I was using CM12 built by Daleski75 so far without any issue. The problem does not appear on a regular basis and when it does, a reboot seems to fix it, at least for a few minutes/hours.
I'll try a clean install when the stable version is out (don't really want to wipe now and once more in two/three weeks).
@rdar_93: Did you find a solution? Are you going to send the device back to OnePlus? If it is actually a hardware issue, that will be enough for me, no more OPO. Sending the device back to China after 2 months of use and having to pay for the shipping is not acceptable.
Edit: It's getting worse... I am gonna wipe soon. Here is a short video: drive.google.com/file/d/0B-EYHGTB15_wS1JXdXlmZXVsT0k/view?usp=sharing
I can't post link for now so you'll have to copy and paste it in your browser.
Edit2: After a full wipe and the installation of the latest nightly, the situation seems to be better, even though I will have to use the phone a bit more to see if it happens again. By the way, I lost dt2w and the gestures don't work well, if not at all... When I draw a V, nothing happens, when I draw a circle, the phone behaves as if I did a double tap. Weird. Again, this happens after a wipe+latest nightly installation+wipe again (to be sure ).
sylvain15250 said:
Same problem here... I had the first ghost touches after having installed CM12 Nightly.
I was using CM12 built by Daleski75 so far without any issue. The problem does not appear on a regular basis and when it does, a reboot seems to fix it, at least for a few minutes/hours.
I'll try a clean install when the stable version is out (don't really want to wipe now and once more in two/three weeks).
@rdar_93: Did you find a solution? Are you going to send the device back to OnePlus? If it is actually a hardware issue, that will be enough for me, no more OPO. Sending the device back to China after 2 months of use and having to pay for the shipping is not acceptable.
Edit: It's getting worse... I am gonna wipe soon. Here is a short video: drive.google.com/file/d/0B-EYHGTB15_wS1JXdXlmZXVsT0k/view?usp=sharing
I can't post link for now so you'll have to copy and paste it in your browser.
Edit2: After a full wipe and the installation of the latest nightly, the situation seems to be better, even though I will have to use the phone a bit more to see if it happens again. By the way, I lost dt2w and the gestures don't work well, if not at all... When I draw a V, nothing happens, when I draw a circle, the phone behaves as if I did a double tap. Weird. Again, this happens after a wipe+latest nightly installation+wipe again (to be sure ).
Click to expand...
Click to collapse
I contacted them and they sent me a program to use. It uses fastboot to flash CM11S and probably fix the partitions that are messed up (I'm making an assumption)
UNFORTUNATELY I'm stuck in a bootloop.
I'm so angry, disappointed and depressed at the same time. I paid about $2500 TTD (in my country) which is probably the equivalent to somebody's rent. I had to work a month to save up the money to buy this and it turns out that the device is faulty after a certain amount of time (or at least mine was)
This is BS.
They said to send them a snapshot of what went on with the fastboot thing, so I figure I"ll upload it here too.
rdar_93 said:
I contacted them and they sent me a program to use. It uses fastboot to flash CM11S and probably fix the partitions that are messed up (I'm making an assumption)
UNFORTUNATELY I'm stuck in a bootloop.
I'm so angry, disappointed and depressed at the same time. I paid about $2500 TTD (in my country) which is probably the equivalent to somebody's rent. I had to work a month to save up the money to buy this and it turns out that the device is faulty after a certain amount of time (or at least mine was)
This is BS.
They said to send them a snapshot of what went on with the fastboot thing, so I figure I"ll upload it here too.
Click to expand...
Click to collapse
I guess you didnt unlock bootloader first
Which when you do wipes the phone so you loose all your stuff.
possible workaround is fasboot on custom recovery and then flash the zip that sets unlock status and circumvents the whole format thing
Sent from my A0001 using XDA Free mobile app
bachera said:
I guess you didnt unlock bootloader first
Which when you do wipes the phone so you loose all your stuff.
possible workaround is fasboot on custom recovery and then flash the zip that sets unlock status and circumvents the whole format thing
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I actually did unlock my bootloader.
PS I also got tired of seeing CM11S try to boot up so I flashed ColorOS (because it's the only rom I had on my laptop. Why not download another 4.4.x AOSP rom? Unstable wifi at school)
So yeah, wifi is not turning on. Gonna try the program again. I wonder if it would work this time?
The conditions aren't as different as before, could work, right?
Honestly I want to wait but they take so long to reply.
UPDATE
After flashing ColorOS I decided to go back and try doing the CM11S via fastboot commands. Still got a bootloop but hey I got the correct fastboot logo now in case if it made a difference.
So I did the compulsory flashing commands when I went from Color to CM11S and still bootlooped.
So I booted into fastboot again
fastboot oem unlock (supposed to unlock bootloader and reboot if it's locked, no reboot if unlocked [assumption])
then rebooted into fastboot again, ran the batch files OnePlus sent to me which essentially flashed CM11S just like you would over fastboot, but with added modems etc.
Successfully booted into CM11S without issues, WiFi works again and so far no symptoms as yet.
Will keep this post updated if anything happens.
My screenshots of the batch file commands OnePlus sent would be found in the attachments.
UPDATE 2
So I think it's fixed permanently this time.
I'm not sure though. It hasn't done anything weird. I will copy my music and photos to see if that would cause anything to happen
I would stay away from os since it messes up partition and people ran into data drop out and modem issues.
Cm11s Roms are the way to go on this hardware.
FYI, when you flash CM12 the radio is overwritten with an alpha/beta radio which causes (well, caused for me) THE EXACT issues OP was having in CM11/S. The CM12 radio (as far as I can tell) ONLY works with CM12 - making going back a PITA.
If you have the baseband in this thread (see screenshot in first post) then that means you are on the experimental radio and are going to have a bad time if you aren't on CM12.
I flashed the latest OTA radio found here and all was right with the world (at least where my OPO was concerned ).
hp13 said:
I would stay away from os since it messes up partition and people ran into data drop out and modem issues.
Cm11s Roms are the way to go on this hardware.
Click to expand...
Click to collapse
I would like to go back to CM11s to check if the situation is better. I tried to flash the lastest CM12 build and it seems to be better but still not as good as before
When I do a wipe and then flash the ROM in TWRP, there are some "folder already up to date", which I would like to avoid. What I would like to do is doing a complete clean install of either CM12 or CM11s plus rewriting the partitions,... So that I'm sure if the problem is still here it is due to an hardware issue.
Is there any chance someone can help me with this? Even with a link... I searched for "write partition" without any luck :-/
Thanks !
EDIT: Do you think the OnePlusRecovery Tool can help me with this?
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.
Has anyone else had any of these problems with their oneplus 6?
-files disappear after each reboot
-keyboard stops functioning on lock screen and I can't unlock the device
-apps randomly losing their data such as Snapchat/Instagram and I have to log back in
-can't use any other keyboard with a password since the device comes encrypted. My s7 used default keyboard before being decrypted.
I have factory reset at least 3-4 times since I have owned the device.
Oneplus customer support said in regards to my files being randomly deleted, "You should just backup your stuff with google drive". Is that really the solution? Just expect my files to be erased and have to recover from backup after each reboot? Most of the customer support people never understand my problems that I am trying to tell them and I can hardly understand them either. Sorry for ranting a bit. I was excited to get rid of my galaxy s7 and try something new that I was told has good rom support and little no bloat on stock ROM, but I've been very disappointed. I guess after seeing their customer support is partnered with Acer it makes sense.
Try a factory reset. I haven't heard anyone report such issues on OP6 before. If it still doesn't work after a factory reset, I would look for a warranty replacement
Pat123 said:
Try a factory reset. I haven't heard anyone report such issues on OP6 before. If it still doesn't work after a factory reset, I would look for a warranty replacement
Click to expand...
Click to collapse
I've factory reset 3-4 times and still have the same issues. Corrupted ROM perhaps? I have seen a few people on one plus forums talk about how their files are being deleted, but those threads disappear magically. I talked to two people today who have the same issue.
user9340 said:
I've factory reset 3-4 times and still have the same issues. Corrupted ROM perhaps? I have seen a few people on one plus forums talk about how their files are being deleted, but those threads disappear magically. I talked to two people today who have the same issue.
Click to expand...
Click to collapse
I've been using it for almost a week with 0 issues... It's probably a faulty unit you're having, make sure it's running the latest 5.1.8 software.
Try installing a custom rom and see if it sorts things out
ramqashou said:
I've been using it for almost a week with 0 issues... It's probably a faulty unit you're having, make sure it's running the latest 5.1.8 software.
Try installing a custom rom and see if it sorts things out
Click to expand...
Click to collapse
Yeah I always do the updates. I started having issues after I updated. Particularly the no keyboard on lock screen happened two updates ago.
Save method: send it back, claim warranty; do it yourself method: https://forums.oneplus.com/threads/oneplus-6-oxygenos-5-1-8-official-download-links.836441/
Download full zip and flash it via system update
which files is it deleting and from what directory? never had any issues, really think a fresh install is best way, start over and don't do any fancy crap at first (root, etc). Root I used to do to every phone, fight and cuss it out because I was not careful, now I never ever root and I'm much happier
jabbermacy said:
which files is it deleting and from what directory? never had any issues, really think a fresh install is best way, start over and don't do any fancy crap at first (root, etc). Root I used to do to every phone, fight and cuss it out because I was not careful, now I never ever root and I'm much happier
Click to expand...
Click to collapse
DCIM, Downloads, whatever directory downloaded Spotify music goes to, Some screenshots would disappear, but not all. I turned on logs and am going to give it another week or so.
Lightbird said:
Save method: send it back, claim warranty; do it yourself method: https://forums.oneplus.com/threads/oneplus-6-oxygenos-5-1-8-official-download-links.836441/
Download full zip and flash it via system update
Click to expand...
Click to collapse
Should I just switch to Android P?
P is still beta with lots of bugs. Some have said it's stable enough for a daily driver but ymmv.
user9340 said:
Should I just switch to Android P?
Click to expand...
Click to collapse
No, too many bugs
user9340 said:
Yeah I always do the updates. I started having issues after I updated. Particularly the no keyboard on lock screen happened two updates ago.
Click to expand...
Click to collapse
It's possible you had a bad flash or bad download. Download a fresh copy of 5.1.8, check the MD5, and install from the system updater (not twrp). If the problems persist, you may have a faulty unit. In nearly a month, I haven't had any of the problems you describe.
iElvis said:
It's possible you had a bad flash or bad download. Download a fresh copy of 5.1.8, check the MD5, and install from the system updater (not twrp). If the problems persist, you may have a faulty unit. In nearly a month, I haven't had any of the problems you describe.
Click to expand...
Click to collapse
I think I just realized I may have done reset system settings instead of factory reset.