Hi, I'll explain my problem quick. a week ago my Nexus 5 rebooted for no reason, upon rebooting I noticed something weird: app data configurations (app data not belonging to the user accesible memory) were all reset, it was like all apps had been freshly installed but left my pictures music and those things untouched. Wifi was working perfectly fine at this point, some form of data corruption I guess. Upon manually rebooting hoping it would come back to normal I found out wifi was behaving strangely, it would take a couple of seconds to turn on and off. After further reboots it stayed greyed out and didn't respond anymore.
So I began reading about the many possible causes and fixes. Tried reinstalling rom, reflashing kernel, going back to stock through flashing stock images through fastboot, rebooting, different radios. Nothing helped, so I decided to go a bit further and mess with the persist folder, first I checked permissions were ok and reset them anyway, then I wiped manually through a file explorer, finally I decided to do what was suggested here https://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576 with some success. Wifi was still greyed out after a fresh rom install but after some reboots it would pick up and work perfectly, until the next reboot. Then it didn't work anymore. I should note I backed up the files in persist through a file explorer and then manually pasted and set permissions (didn't know you could make an .img file of it) dunno if that has anything to do. They aren't corrupted it seems.
Unplugging the battery briefly fixed it for a day, then the next day the same problem came back without me doing anything.
Some more info:
-I have a working original EFS backup from before it crashed.
-Phone was rooted running CM11 when it happened, been using that rom for 2 years with EX kernel.
-It was a bit low on space (about 400mb left) when it happened, about 300mb were freed after it crashed. I have a hard time believing this could have caused it but maybe?
-It's global D821 16gb version
-GPS has always been wonky (if that has anything to do with it)
-IMEI and IMEID haven't changed.
-Calls and data work fine.
-When either wifi or bt work they show their correct, original addresses, only once wifi showed 02:00:00:00:00:00.
-Rebooting changes little, but powering off then waiting a few seconds and turning it on sometimes brings bt back.
-Leaving the battery unplugged almost fixed it, brought it back for some hours, went to sleep and when I woke up it was gone again.
-When performing the "e2fsck /dev/block/..." command above I wasn't prompted to fix any errors I think, output was "clean, 31/1024 files, 1125/4096 blocks" and the "make_ext4fs /dev/block/..." command reformats it without issue.
So yeah, I've tried everything save baking the mobo cause I'd rather be able to sell a semi working device than a bricked one
Any other thing I could try? Or way to check if it is indeed a hardware issue? im attaching a Liveboot log if it's of any use. Thanks beforehand.
uh I can't find the way to upload the log
how is one supposed to attach a file? im on my desktop with latest chrome
Related
Greetings people!
Yesterday I got this message while booting up my TP (latest official ROM):
"The device is unable to boot because either you have turned off the device incorrectly or tried to install an application from untrusted source. Press END to reset your device or press any other button to cancel. This operation will delete all your personal data and restore the device to its factory default settings"
However apart from that message, phone works flawlessly without any noticable change in speed or stability! The only apparent problem is that it takes a while longer (about 10 seconds) to boot up because of that message. I tried a couple of backups, problem was solved at first, but returned later...
I do take daily backups, but since I hardly monitor my phone when I reset it, this problem could have been caused by an app or reg entry a while ago... and searching for the appropriate backup will be a pain in the ass.
Since there's no change in speed or stability, do you think it would be wise to keep using the phone as is, or is it possible this would cause further problems down the road?
Any other way to troubleshoot it (at least to find the program that's causing this) other than a hard reset?
Edit: couldn't wait so I reverted to a week-old backup, installed back most of my applications, and it seems to be fixed (for now)
Update! I just tried a new SD to try XDAndroid, and guess what, the error disappeared!
So there must be a program I had installed in the storage card, possibly trying to start a service or something on every reset... and failing.
Is there a way to troubleshoot this? Maybe through SKTools or anything similar? I have a ton of apps installed into storage card and it will be a pain in the back cover to try by trial-and-error.
Thank you in advance
edit: inserted my old storage card again, error did not appear, problem solved! At least for now
Still if anyone knows how to troubleshoot this, please let me know
Update: Seems this error occurs every time I use SPB backup.
Yesterday, after a scheduled backup, the error came back. To troubleshoot this, I removed the SD card, did a soft reset, the error was gone! I took another manual backup, and again, the error came back.
So there must be something happening with SPB Backup and my SD card. Probably messing with files on the SD, or the driver or whatever (no idea there, I'm a total noob when it comes to software).
Moved the issue to the SPB forum
I have this message to, but I have never used SPB Backup
Well, in my case, it was obviously something tampering with the SD card (even if not SPB backup, something else)
Have you tried rebooting your phone with the SD card taken off? I just wait till it boots normally, and then insert it back. Works for me every time.
If that still happens, that probably means whatever is causing the problem is in your main memory.
akpidis said:
Well, in my case, it was obviously something tampering with the SD card (even if not SPB backup, something else)
Have you tried rebooting your phone with the SD card taken off? I just wait till it boots normally, and then insert it back. Works for me every time.
If that still happens, that probably means whatever is causing the problem is in your main memory.
Click to expand...
Click to collapse
Well I tried that just to see what would happen and I did not get the error message. So it is something on the SD card, but booting without it is not an option for me as I have several boot-start apps that are housed on it.
Perhaps one of those apps is broken?
As far as my case goes, I kept on using it for three months after the error appeared, without noticing any lag or issues at all. The only downside was that it took me three minutes to boot up, something I got used to.
If that's no big deal for you, I'd suggest you just leave it as it is for now, and check for lagging or specific applications failing (maybe one of them will be the app that's causing the problem?). If nothing happens down the road I think it could be safe to leave it as it is.
Now, if you can't stand this, I guess the only practical solution would be a hard reset. You can always play around with removing/reinstalling those apps you mention (or even better, installing them in the phone's memory) to check if and which one is broken, but I can understand that this not only will be a huge burden, but you may come to the conclusion that no specific app is causing this and something went south in the OS.
Personally the only apps which include a boot-up service I have installed into my SD are Football Monitor and PocketWeather. I tried removing both of them them back when I first had that issue, it didn't work...
Sorry I couldn't help more :/
My Thunderbolt is locked somehow, and I have no way to restore it to factory defaults. What I mean by "locked" is as follows:
I remove two apps from the device, change the wallpaper and delete a contact. Then, I restart the device - when it boots back all of the changes I made are gone. It's like in read-only mode, the changes look like they take affect but after a reboot everything is restored to it's current FC'ing on everything state.
I've tried factory resetting the device but instead of booting to recovery it just boots to the picture of a phone with the red caution symbol showing, it does not do anything else.
I've tried flashing over a stock RUU image but the flash either 1) looks like it works then boots back to the state it was before, 2) hangs on part of a flash and reboots to the normal state.
The device is not rooted, I've tried revolutionary and get the following error:
"rawadb_handle_msg" and then it loses connection.
Any ideas would be appreciated, I've never seen anything like this.
Turn it on and let it boot up if it can then pull the battery while its on and leave power off for 5 minutes then try again.
Also can try, with power off, hold power button and volume down button together for a few seconds and when it gets to the white screen wait for about 10 seconds then select reboot from there
Latest OTA patched the Revolutionary exploit (so it won't work). You may want to root using ADB and flash the rooted RUU. Can't say I've ever seen R/O behavior; but then again, I've been rooted for months - currently on AOSP (ShiftAo5p 2.8) and waiting for an ICS with data
I know, not too helpful, but there are still ways to root.
Any feedback from VZW or a "real" corporate store? They're actually quite helpful here with tech junkies.
OK, one more suggestion - early on, I couldn't do anything either (Market, etc) and the fix was to pave (format) my SD card. I know it sounds weird, but I was going to exchange my phone (ordered, then sent back replacement). I figured, what the heck. Took the uSD card out, put it into my PC's USB port and formatted it FAT32, popped it back in and VOILA - happy happy joy joy.
Granted I copied all the data off of it before paving - then copied back selectively (highly recommend AirDroid, by the way, no more cables). Might give this a shot.
Hey guys, thanks for the suggestions - unfortunately no luck on my end with that
nautical34 said:
Hey guys, thanks for the suggestions - unfortunately no luck on my end with that
Click to expand...
Click to collapse
I inserted the card freshly formatted (I wasn't rooted at that point) - nothing on it, and I booted up, I was able to install Market apps (which I couldn't do before) - Note - AFTER I also did (multiple) a factory reset, I was good.
That didn't work for you? Maybe try again? Or just No-Go?
Also helps prove every 'Bolt has its own personality
Good luck on your CLNR ...
I have no idea what errant app or corrupted data may have been on the card, but totally paving and starting over "fixed it". Soon after, I rooted Then I had choices Granted I've had times I've had to do a factory reset (but not pave the SD) and set up all again - I've found the larger games (haven't determined which yet) cause my phone to get into reboot fits if I do actually reboot (which I need to do sometimes to get the radios to get data again); so, boring maybe, but very few games installed. That's OK, I prefer to learn or listening to music during idle time. Good luck.
I am having a very annoying problem with my Rogers I727R S2 phone on ICS stock.
The problem started to increase in frequency to become a real pain.
My phone would suddenly freeze and stop responding to screen touches for a bit, sometimes as long as 2 minutes, before bouncing back. When it comes back, it initializes as if it is restarting, so I would feel a vibration, lose all open applications and see icons start appearing on notification bar one by one. The media scanner would start working and software installed on SD card start appearing.
The problem happens spontaneously and out of the blue. It was occurring at less intensity on gingerbread before upgrading to ICS. After upgrading, it was not that frequent until only recently.
I noticed the problem goes away when I remove the SD card or when I am on flight mode with no Wi-Fi. I changed the SD card but this did not help. Connecting from home or work does not differ, so a problem with Wi-Fi would be ruled out. I once had a problem with home Wi-Fi when somehow the router’s DNS was not resolving, when this problem of mine was at its prime, and my phone was rendered unusable as it only takes couple of minutes before acting up.
I spent quite long time searching for an answer and so far no luck
I just placed a video illustration of the problem, and hope to get feedback on even where to head.
watch?v=akS59vFfIAI
raymonko said:
I am having a very annoying problem with my Rogers I727R S2 phone on ICS stock.
The problem started to increase in frequency to become a real pain.
My phone would suddenly freeze and stop responding to screen touches for a bit, sometimes as long as 2 minutes, before bouncing back. When it comes back, it initializes as if it is restarting, so I would feel a vibration, lose all open applications and see icons start appearing on notification bar one by one. The media scanner would start working and software installed on SD card start appearing.
The problem happens spontaneously and out of the blue. It was occurring at less intensity on gingerbread before upgrading to ICS. After upgrading, it was not that frequent until only recently.
I noticed the problem goes away when I remove the SD card or when I am on flight mode with no Wi-Fi. I changed the SD card but this did not help. Connecting from home or work does not differ, so a problem with Wi-Fi would be ruled out. I once had a problem with home Wi-Fi when somehow the router’s DNS was not resolving, when this problem of mine was at its prime, and my phone was rendered unusable as it only takes couple of minutes before acting up.
I spent quite long time searching for an answer and so far no luck
I just placed a video illustration of the problem, and hope to get feedback on even where to head.
watch?v=akS59vFfIAI
Click to expand...
Click to collapse
Try a different launcher.
the only way to troubleshoot is to start from scratch, read my 2nd link in my sig to restore to stock ics, reset within the recovery when odin finishes flashing, also keep out your sdcard out just to make sure your sdcard or its slot is not the problem. if still having probs its hardware failure, should still be under warranty
odeccacccp said:
Try a different launcher.
Click to expand...
Click to collapse
For reference, a different launcher did not do it
vincom said:
the only way to troubleshoot is to start from scratch, read my 2nd link in my sig to restore to stock ics, reset within the recovery when odin finishes flashing, also keep out your sdcard out just to make sure your sdcard or its slot is not the problem. if still having probs its hardware failure, should still be under warranty
Click to expand...
Click to collapse
I went through your instructions restoring to stock ICS (which did not wipe my data as I thought it would). This did not help though, and the problem persisted. After that I decided to a hard factory reset. This appears to have done the job and my phone was working very smoothly.
Because my phone is rooted, I restored to the buggy stock again using CWM in hope to be able to figure out how to my migrate my purchased software, data and settings after hard reset. I wonder if there is a way to preserve important files even with replacing systems. I want to hard reset again but I keep my important information
raymonko said:
I went through your instructions restoring to stock ICS (which did not wipe my data as I thought it would). This did not help though, and the problem persisted. After that I decided to a hard factory reset. This appears to have done the job and my phone was working very smoothly.
Because my phone is rooted, I restored to the buggy stock again using CWM in hope to be able to figure out how to my migrate my purchased software, data and settings after hard reset. I wonder if there is a way to preserve important files even with replacing systems. I want to hard reset again but I keep my important information
Click to expand...
Click to collapse
after restoring stock perform a reset in the recovery, if old data is still there after reset its a hw defect in the nand
edit: reread your post so nm what i just posted, use titu or other backup software
Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.
Rather than do that, I reset the phone, wiped Davlik cache and Fixed Permissions (took a long time!), then rebooted.
That sort of worked, but a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
What's the way-ahead here? Am I stuck doing a factory reset? Or even formatting the SD card?
Thanks in advance.
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
jeffsf said:
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
Click to expand...
Click to collapse
Okay, thanks!
Anything else on the SD card I should back up besides DCIM / Media-> Ringtones/MP3s / "ui" / TitaniumBackup?
(Got about an hour while this stuff goes off to my HD...)
Hoo! Thought I effed myself for a sec - from CWM I was wiping all partitions... including /sdcard.
Then I realized... $#¡+... my ROM is on there!
Fortunately CWM has the "mount USB storage" option.
*whew!*
I was going to add format the sdcard from the phone. But you did that. Typically when what happened to you would happen to me it would be from some app updating and for whatever reason got corrupted during install and fouled the phone up. If you use TiB I highly suggest setting a automated task to back up your TiB backups to drop box, google drive or box.net. Then in these situations you have a recent TiB to fall back on.
JaimeZX said:
Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.[...]...a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
Click to expand...
Click to collapse
Hi JaimeZX,
I am curious if you have recently rooted, flashed to stock, or installed the VB or Basic w/a twist kernel? I am running the exact same setup as you list (minus the modem) and this *exact* same scenario happened to me on the exact same day. March 12th, at about 10pm.
Detail as much information as you can, I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel. Perhaps there is an issue with the stock packages, or the USB driver ghosts (I've deleted all USB assigns at all ports and reinstalled for device detection in Heimdall). Hopefully we can get a good list of information to help us fix an issue that is apparently quite catastrophic (in that /data seems to corrupt) and save others from a future headache.
I have searched the dev threads to no avail, and as a general rule it seems that if problems are brought up they are usually met with "try flashing back to stock," "gremlins," "no one else is having problem 'X'," etc. even in cases of users with multiple complaints of the same issue. Both the DSP Sound force close upon EQ preset select and the issue that some had with the Messages, Phone Dialer, Search, Call Logs closing to homescreen are issues that I've seen this with. I believe this is a real issue, and I need to get it fixed without wasting time on messaging replies to anyone advising "try this," "Try that," etc.
My hope is that between the two of us we can address any of the common responses from developers before taking the issue to them and reporting it. I personally cannot today get my phone to boot without freezing (after boot cycle completes - not bootlooping or freezing during the bootleader seq) and am currently attempting to get into d'l mode without much luck.
When this happened to me on Tuesday night I was able to reboot to recovery, reflash the final-fixed.zip first without wiping data (which failed-/data is corrupted somehow here) and then *with* wipe/data and it booted, ran fine, so I then re-flashed BasicWithaTwist Kernel and was fine until late last night again.
I had been using the phone for some fairly constant web searching and the screen went black, appeared to soft reboot, and then froze. I pulled the battery, waited a few mins, reinstalled battery, once again, Freeze after boot.
No indication that an app crashes, phone just completely freezes, remains screen on, capkeys lit, power button does not respond, nor do softkeys or touchscreen. Makes it though the scan device and scan SD processes *sometimes* and other times freezes before it completes them.
I pulled the both the SD and the SIM and booted up, same issue, though it makes it through the scan device processes everytime since it's not scanning 18gb of data on an SD. This tells me it is not SD or SIM related, and is most likely software related, either ROM or Kernel. I've also ruled out the possibility of an old app/data package by reformatting the SD (long format - wipe all containers to "o,") let Android rebuild menu structure on SD, redownloaded a short list of commonly used apps and installed fresh - *NO* TiBackup apps were restored and the actual backup folder was not replaced to the SD after flashing.
I've tried both the Odin (Fb KJ6 back to stock) and the one click (lumin's tutorial) back to stock. Checked the download of Final-Fixed, MD5 checksum is correct. Cannot find MD5 on the sms-T959V-KJ6-antsvx.v1.1.3.zip file. Doesn't seem to be listed on Anton's github site, perhaps I don't know how to find it there. That is the only puzzle piece I haven't double checked.
All for now, looking forward to yours or anyone's replies or suggestions for anything I may be overlooking. Thanks.
0
---------- Post added at 11:19 AM ---------- Previous post was at 11:12 AM ----------
devlinandersen said:
Hi JaimeZX,
... I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel....
0
Click to expand...
Click to collapse
I should add that I have been on Valhalla Black Edition since it was in beta and have been quite happy with it. I only did a back to stock flash to try to (one more time) see if I could get a cooperative DSP sound manager. No such luck, and now a few headaches, and this issue on Tuesday coupled with yours in the exact same timeframe...I'm just thinking there is a problem somewhere in the chain of attack and hope to find it with the help of others.
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
devlinandersen said:
No indication that an app crashes
[...]
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
Click to expand...
Click to collapse
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
jeffsf said:
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Click to expand...
Click to collapse
I will try in a bit, collecting files for another fresh install, different ROM.
jeffsf said:
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
Click to expand...
Click to collapse
This is false logic and is just what I was trying to avoid. I will attempt to explain to hopefully help build a stronger environment that is conducive to problem solving. It still very well could be a dev issue if say, a certain ROM or Kernel begins to wrestle with an app that has recently updated. Is it the apps or the rom's fault? Maybe it is a seldom used feature of an app that just missed all the users testing until now, it's well within the realm of possibilities and would just like to see helpful comments (such as the first portion directly above) to help solve issues. Truth is, I don't know *what* is wrong and neither do you, so a focus on constructive commentary would just help everyone out.
Logs or it didn't happen.
Update...
After a factory reset/data wipe, wipe cache, wipe dalvik cache I had to let the battery charge for a bit. Came back and decided to just try to boot phone, still freezes after boot sequence. I decide that I will flash a different kernel and a different ROM in order to see if I can make a difference. Before flashing Blastoff v2.5 Kernel I decided to factory wipe/data wipe, wipe cache and dalvik again...I am not sure if this is news, but when doing the Dalvik cache wipe in CWM it returned no result, perhaps because I had previously performed and is empty, but I thought it strange that there was *no* communication that it was already empty/wiped, etc.
Installed Blastoff v2.5 and was able to boot without freezing. Something else was damaged with the Rom as well, would not load home screen, only had pulldown menu. Rebooted to Recovery and flashed Unnamed RC-2.zip and have been charging the battery, talking on the phone and reinstalling apps from market.
Same error happened twice to me and once with Jaime. Both of us on VB and Basic+Twist. After installing new kernel i'd point towards kernel. Also uninstalled DSP and installed voodoo sound on VB, but had that on previous version as well. If I had to start somewhere, I'd start right around there.
Hope this helps, will provide logs from SD backup I made before reflash of new kernel/rom. Gotta run. Adios...
-devil.
I had to get my phone going today, it appears to be working without freezing, though on this new app the phone dialer/phone caller force closes on outgoing calls (I am only mentioning here, I will visit the Q&A for the ROM if I need assistance). Unfortunately I was unable to replicate the problem without flashing back to my previous nandroid. I have it saved and given some time I will do my due diligence and get a logcat **if** Jaime doesn't do it before me...because I kinda have a feeling that something was updated in the market on Tuesday evening that is now fighting with the kernel somehow. But again...I didn't run a logcat so it's not even happening...yet...
...to be continued...
Devlin - sorry for the delayed reply.
I did notice that I'd had more and more apps FCing on me in the week leading up to the Über-crash. Unfortunately I don't have any more "background" to add than that.
I backed up everything I wanted on the SD card and then formatted that, plus /data, /system /everythingelsethatwasanoptioninCWM. Then did my installs.
FORTUNATELY (knock on wood) I have not had any recurrence of the major issue.
Hello,
I'm having a serious issue with my oneplus one (I bought it in November, no serious issue so far).
However, A lot of issues showed up suddenly overnight (without me installing or modifying ANYTHING at all).
Here's how it goes : after a few minutes of using apps, these apps either crash, or freeze, then the phone reboots.
I've tried factory reset, wiping dalvik cache etc... but the problem is not going away.
I even flashed the stock rom XNPH05Q 64GB, but it didn't help, I still had the same problem afterwards.
So I flashed back the original rom XNPH33R 64GB, but still nothing.
I've also tried the command make_ext4fs /dev/block/mmcblk0p15 to no avail.
I really don't know what to do anymore...
I have made a logfile during which the phone freezed, then crashed a few seconds after I launched an app called "Summoner War" (which works perfectly fine on my other phone).
I am putting the logfile here in case it can help... (the crash is most likely in part2)
Any apps seem to trigger this crash (even settings triggers it sometimes)....
Should I consider sending my phone back to Oneplus for repairs?
Any help/advice would be greatly appreciated
Sincerely