I was getting random shut downs, I was googling and most of the things posted didn't apply to me, so I decided to view a logcat, seeing what it showed when it randomly shut down. How do I fix this problem? I'll include a logcat as soon as I get another one, I forgot to save it
Edit: last_kmsg here
Edit 2: last_kmsg removed, it was taken after a batt pull
Edit 3: Newer kmsg
Edit 4: Said reboot instead of shut down... facepalm
noobiekins said:
I was getting random shut downs, I was googling and most of the things posted didn't apply to me, so I decided to view a logcat, seeing what it showed when it randomly rebooted. How do I fix this problem? I'll include a logcat as soon as I get another one, I forgot to save it
Click to expand...
Click to collapse
Is it a shutdown or is it a hard reboot? I'm suspecting hard reboot.
A logcat is about as much use as a chocolate teapot for hard reboots generally.
And what on earth did you extract it with? It's got a crazy amount of line spacings and is unreadable.
Best thing for reboots is the output of:
Code:
adb shell cat /proc/last_kmsg
noobiekins said:
I was getting random shut downs, I was googling and most of the things posted didn't apply to me, so I decided to view a logcat, seeing what it showed when it randomly rebooted. How do I fix this problem? I'll include a logcat as soon as I get another one, I forgot to save it
Click to expand...
Click to collapse
maybe you have some corrupt data in there.. did you restore the clock(system app) with titanium backup? anyways, go to the phones main settings, apps, all, clock.. then clear its data. reset your alarms and see if you reboot again.
this was more like a hard shut down than a hard reset, my gnex isn't rooted, brand new out of box and this happens. Factory resets also cause me to shut down. I'll do the thing thalamus said first, after rooting.
edit: I might send this to the repair center
all they will so is reflash the stock img, and you can do that.
What does mmcblk0boot1: unknown partition table and mmcblk0boot0: unknown partition table mean? Does it mean I have to format those two?
edit: I think I found the problem. In both of these, they have problems involving 's6e8aa' On my good galaxy nexus, it doesn't show 's6e8aa' in the last_kmsg, but it shows in the dmesg. The problem is I don't know what 's6e8aa' is, I think i'm going to send it to the repair center, thanks!
I have found out that, when the sim card is inserted, the phone will randomly shut down, if it is simcardless, it stays on fine
Related
Afternoon all,
Last night I left my Desire charging as normal, having recently installed the Remote Media App. I suspect it used up all my storage with some sort of indexing process, as I returned to the phone this morning to find it perpetually showing the glinting HTC logo.
A reboot failed to clear it, and booting into recovery mode reveals"E:Error in DATA:data/recovery/log, (No space left on device)"
I've tried connecting to it with adb, but I get the following error
- exec '/system/bin/sh' failed: No such file or directory (2) -
Is there any way out of this bind? I had/have ClockWorkMod recovery installed in order to use ROM Manager, but I'm not terribly clued up on what else is out there on offer.
Any advice would be greatly appreciated.
Kyle
Try rebooting the phone into recovery mode and wipe/factory reset and see if this fixes it?
(Although you will loose all your apps/settings/scenes, though)
This should resolve the problem though.
hehe, there is always that option. I was hoping not to lose texts, settings, etc though this time round. Sadly my backup is more than a few days old.
I was mistaken in thinking I had ClockWorkMods recovery image installed, it appears to have gone back to the default image. I've just discovered a modified recovery ROM from JesusFreke here http://forum.xda-developers.com/showthread.php?t=443041 which may be of use.
Having to wipe and start from scratch again is a disgustingly appaling out of space failure mode. >:-/
bin the phone and use a pineapple
That recovery image is for G1! Don't even think about flashing it.
Even if you have stock recovery, you should still be able to clear storage from HBOOT.
Regards,
Dave
One other thing that might be worth trying is booting the device in safe mode.
Whilst the phone is power down, hold down the menu button and then power on - keep menu held down until the phone is fully booted.
I doubt that it will help in this situation, since clearly /data is completely full, but there's always a slim chance it work.
Regards,
Dave
munkehman said:
bin the phone and use a pineapple
Click to expand...
Click to collapse
Thanks for the advice m, I'll be sure to kick you in the nads next time you cross the border
Sadly Safe Mode fails too. The HTC logo appears and glints for a while, and then briefly vanishes just to reappear again. My thumb got sore after 5 minutes of holding the button down
I realised that was a G1 ROM shortly after reading more about it! I see there may be a more suitable recovery ROM at http://forum.xda-developers.com/showthread.php?t=709146 that I can flash. Failing that, then I'll clear storage and consign myself to failure
Wahey! It's sorted! Well, it was sorted a couple of hours ago, but a meeting got in the way
Wrote up some of the details here - http://lodge.glasgownet.com/2010/08/31/recovering-a-htc-desire/ if anyone is interested!
kylegordon said:
Wrote up some of the details here - http://lodge.glasgownet.com/2010/08/31/recovering-a-htc-desire/ if anyone is interested!
Click to expand...
Click to collapse
Sorry to dig up an OLD OLD thread, but your "guide" helped me out last night.
In addition to looking for "big" items in the data partition, I also moved some of the Google updates (5meg Maps.apk anyone ?) from /data/app to /system/app ... renaming to overwrite the original version from my Rom.
Thanks Again.
Ok, days of peace are finally over
Today after doing a simple reset of my kaiser (power off then back on)
I have noticed an endless loop in boot and that is the line,
set volume of 256 to 5
init: untracked pid 123 exited
Click to expand...
Click to collapse
The pid number increaments by 3 after every loop and the loop starts with
snd_set_device(1,1,1)
rpc_write(blablablabla)
blablablablabla
Click to expand...
Click to collapse
and the end of the loop is
set volume of 256 to 5
init: untracked pid 123 exited
Whats suddenly worng?
I really dont want to lose my contacts, rest of the apps/tweaks I dont care
dark_prince said:
Ok, days of peace are finally over
Today after doing a simple reset of my kaiser (power off then back on)
I have noticed an endless loop in boot and that is the line,
The pid number increaments by 3 after every loop and the loop starts with
and the end of the loop is
set volume of 256 to 5
init: untracked pid 123 exited
Whats suddenly worng?
I really dont want to lose my contacts, rest of the apps/tweaks I dont care
Click to expand...
Click to collapse
If u synced your phone with a google account there is no problem for contacts because they will pop up again if you reinstall android and you sync that account again.
Anyway, you can restore system as much as u want because when android start it is read only, so this means that no changes are done to it , simply reinstall android and say "no" when menu ask you to clear data.
I tried like this:
1st Try with Clear Dalvik Cache
2nd Try: Only system reinstall and no DATA wipeout
3rd Try: Reinstall like a hard reset
I change my fonts pretty often and what I think is a ttf was encoded wrong and I replaced that :/
pssshttt! I just rebooted my phone a second time (Power off then back on) and again this stupid error popped error popped up :/
One thing is for sure that its related to the font I am using :s
Endless loop
I have had this endless loop twice and both times I had to reinstall via the installer. I don't know if there is a fix so that you don't need to reinstall. It would be really nice if someone with a little insight could maybe find out what is going on.
I haven't been able to understand exactly what I did to make it loop like this.
I just make sure never to reboot and if so I just hope no looping accours.
There is something with the 3rd Party fonts I used, only one of them caused this, rest all of em were fine. I had to reboot my phone dozen times in order to see stability or corruption before releasing mine build
I think its related to some system related, and happens only when I install that specific cursed font lol
I will continue this topic. I'm using newest froyo on kaiser, newest kernel, and I also have an untracked pid allways, when I'm using my kaiser for longer time, or install something and reboot it. I have no idea what to do with that, and I don't want to go back to WM. Please, help
And sorry for my not good english
I have this problem too,but i didnt use custom fonts only installed opera and tried to move it to sd and installed igo which uses the sd to store files.And then it froze and gave me this piece o .... loop Is there a fix for this?
Reinstall, usually the error is caused by fs corruption.
Tried it but the problem still comes back when i try to install something or try to move something to the sd card.
I have figured out what causes this error and so far it occurs only in froyo ports. The init.rc gets corrupted. The bootup process goes into infinite loop in overwriting the init.rc
Best remedy is to CLEAR DALVIK CACHE and REBOOT. (You often lose your contacts and text msgs and google login details so keep a backup)
Its so much nuisance having this init.rc crashing atleast twice in a day and I am pretty much frustrated with WM either way. I am thinking for replacing my phone for a native android
I had this happen to me 3 times today, recovered all 3 times.
Running Liqid's kernel .32 using ATools and a deodexed version of "system froyo".
Fairly "stock" settings in ATools and only added 4 apps to original build.
I also got "low on space" notifications with each of these crashes. Checked memory after recovery and it was back to normal.
I really need to figure out how to make a sig...lol.
dark_prince said:
Its so much nuisance having this init.rc crashing atleast twice in a day and I am pretty much frustrated with WM either way. I am thinking for replacing my phone for a native android
Click to expand...
Click to collapse
Agreed. Almost there.
same thing happened to me
Hello, I apologize if this has been answered elsewhere. I did look / read alot of threads and did not find anything yet.
ROM:------------Juggernaut 2.0
KERNEL:---------Jugs 0.3
OC, min/max:----1080/1836 MHz
**No Tweaks / scripts**
Here is what I noticed. I held down the "power" button to get the power menu options and selected "Screenshot". The phone went back to the previous screen as if it took the screenshot. Then 2 Seconds later I got an error/message saying:
"Error: Unable to save screenshot
mBitmap = null"
Immediately another message appeared saying:
"Screenshot saved at null"
===========================================================
I've looks in my Gallery and don't see a folder called NULL, I've plugged the phone in via USB and looked through the folders trying to find it and I cant seem to locate NULL.
Do you think this could be an issue with ROM I've installed or a One user bug that can be resolved?
Much better to just post in the ROM thread as this is a specific question to the ROM.
You need to make sure the screenshot app has proper superuser permissions. Open up Superuser and make sure it's set properly. Someone had this issue earlier today and that resolved their issue.
thats exactly what it was. I wonder how it got in the Deny list. Hmmm Well its fixed not. thanks alot bud.
I wonder how to solve this problem...
Sorry for reviving this old thread but may I know what could be the possible error for this? Any error in libs or something?
aniket.lamba said:
Sorry for reviving this old thread but may I know what could be the possible error for this? Any error in libs or something?
Click to expand...
Click to collapse
Have you tried the hard key solution? (Volume Down + Power)
On another unrelated note you really shouldn't 1080mhz your min clock as your phone is never truly idle and can cause unneeded battery drain and/or excessive heat.
My phone (rooted, but stock running 4.1.1) keeps restarting by itself. I have seen other folks with the same problem on the S3 and other devices. And it seems the only thing that fixed it was changing the SD Card (tried it) or resetting the phone. It takes me ages to set up my phone and I'd like to avoid doing the latter if possible. Is there some kind of a panic log file that gets written that I could look at? I believe that the logcat file gets cleared at every reboot which, if true, explains why I can't spot anything in there. Since this happens erratically, I can't connect from my PC and redirect the logcat to a file on my PC. I believe Linux stores crash logs. Is there something similar on Android?
Oh, and it's not rebooting because it's getting hot or anything. And I haven't done any overclocking or any messing around with the phone.
Found a couple of options after googling. I had tried earlier, but "logcat across reboots" was a better search phrase.
Anyway, I can hook up my phone to the PC and run
adb -d logcat > mylogfile.txt
which should save a log file to my PC and when I'm not near a PC, I can use something like alogrec which saves logcat files to an SD card
https://play.google.com/store/apps/details?id=org.jtb.alogrec
Another option is to use adb bugreport
http://developer.sonymobile.com/2012/01/25/new-bugreport-analysis-tool-released-as-open-source/
Hopefully it will provide a useful clue.
If not....you can always make a Nandroid, reset your phone, and then restore.
Sent from my PG06100
You can use terminal emulator from your phone and dump a logcat to sd as a .txt if you search around you'll find the proper command which I can't remember at the moment but its something like
Su > enter
Logcat -d /sdcard/filename.txt
Filename being whatever you choose
I like to break stuff!
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
flyingsherpa said:
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
Click to expand...
Click to collapse
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
noahvt said:
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
Click to expand...
Click to collapse
I have to confess my ignorance here... I'm brand new to flashing android like this so I don't know the answer to your question. If part of tutorial I followed blanks out the bootloader (and doesn't write something in?)... then you're probably right. I shall look into this more tonight when I'm at home with the nexus. Thanks for at least giving me something to look into, that's exactly what I was hoping for!
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Asus_USA said:
a7medmo7eb - We're very sorry to hear of this. Kindly email us at [email protected] with this copied problem description along with the serial number of your tablet and we will do our best to provide you with troubleshooting and servicing options.
If you have any further questions, comments or concerns please do not hesitate to let us know. We will be more than happy to assist you. Once again, thank you for choosing ASUS products and services.
Thank you.
-In Search of Incredible-
Technical Support Department
http://www.asus.com :: http://service.asus.com/
Click to expand...
Click to collapse
nhizzat said:
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Click to expand...
Click to collapse
Thanks, you're probably right. I did read up to understand all this stuff a bit more, so I know it's not lack of a bootloader or anything. All img files install just fine, so my pc can talk to the nexus, just the screen is all wonky no matter what i do.
Unfortunately I bought this 1.5 years ago so I don't think it's under warranty anymore. Everything was fine until I updated to Lollipop! Seems a big coincidence that I had a hardware failure at the same time as that update... I feel like Google ruined my tablet...
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Masterchief87 said:
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Click to expand...
Click to collapse
Hmm, thanks for the idea, but fastboot wouldn't do "format data", giving me the error: Formatting is not supported for filesystem with type ' '
Googling that makes it not look good. Weird, thing is, it still technically boots up, just the screen is so wonky you can't see where you are or interact with it properly. Not sure what else to try (opening it up and re-seating touchscreen cables?).