Develop Bugs

[Q] Random reboots and frustrating boot loops

Hey all,
I've been having boot-loop problems for almost a month now. The phone just abruptly reboots and goes into a boot loop with just the HTC screen. The problem is fixed temporarily if I remove the battery for a while and then power it back up. If I start having too many things going on, such as several tabs in DolphinHD, downloading several updates, etc. [no gaming at all] it'll do the same thing and just reboot.
I was running Cyanogen 6 [stable] with Kingxkernel #2. I was not overclocked, but did have a few setcpu profiles active. I've tried everything imaginable since they began:
-Tried a different kernel [SNAP], didn't work
-Truned off setcpu, didn't work
Today, I got fed up with everything and then decided to flash a Sense ROM hoping that that would fix everything. I flashed the latest Fresh and after the install, even before I could skip all the set-up stuff, the phone started to reboot again.
As for the Fresh installation, I wiped fully including dalvik and cache all in RA.
I'm about to go crazy. I wan't my fully functioning phone back. Please help
EDIT: Also, I forgot to mention that around the same time the random reboots and bootloops began I got a new battery. It was the one from Best Buy made by Seido. Idk if that would affect anything seeing as I get the same problems with both batteries.

if i was you i would do all the following:
1. titanium backup all your apps...
2. flash clockwork recovery
3. nandroid backup everything
4. wipe /system
5. wipe /data
6. wipe /boot
7. wipe /cache
8. wipe /dalvik
9. install rom of your choice
10. run it for a few hours and push it as hard as you can to cause a reboot
- if it reboots -> plug into computer load up terminal/command prompt do adb logcat (copy and paste where and why it reboots)
- if it doesn't reboot -> start reinstalling your apps one at a time or in batches until you find the culprit (unlikely since most installed apps should only cause a force close rather than a reboot but still worth a shot)
11. post back with your findings... ?
fyi the nightly builds seem more stable than the stable build ever was... at least to me on my evo it was...

Thanks for the reply.
I'm going to try that to see what happens. I'll post asap.

Alright, I flashed Clockwork as you said and wiped/formatted everything you mentioned. After that, I flashed Fresh. Everything went well until it went through it's first routine reboot after flash; I didn't even get to pull down the lockscreen into activation before it randomly rebooted. I did a logcat on the first reboot. This is a little piece of the last part of that:
V/libgps ( 292): DeferredActionThread pthread_cond_wait returned
V/libgps ( 292): PA event: 0x00000040
V/libgps ( 292): PDSM_PA_EVENT_GPS_LOCK 0
D/dalvikvm( 292): GC_FOR_MALLOC freed 618 objects / 115992 bytes in 145ms
I/ActivityThread( 674): Publishing provider com.htc.dcs.provider.utility: com.htc.dcs.service.utility.UtilityProvider
D/dalvikvm( 292): GC_FOR_MALLOC freed 55 objects / 177104 bytes in 74ms
D/dalvikvm( 292): GC_FOR_MALLOC freed 296 objects / 253256 bytes in 86ms
I/ActivityThread( 674): Publishing provider com.htc.sync.provider.weather: com.htc.sync.provider.weather.Provider
D/ConnectivityService( 292): getMobileDataEnabled returning true
I/ActivityThread( 674): Publishing provider com.htc.socialnetwork.snprovider: com.htc.socialnetwork.provider.SocialNetworkProvider
horiveira:tools stgomez91$
Click to expand...
Click to collapse
It rebooted after the second to the last line. This is my first time using logcat, so I don't know too much about what any of that stuff is, except for the last line obviously.
Can anybody tell the reason why I get these problems by looking at that?
Here's a copy of the logcat file: http://www.sendspace.com/file/kt3lj1
I was hoping this would work, but alas...it did not. What do I do now??

Had the same problem.
For me the solution was to reset the GPS and after that all the random reboots stopped.
Dial : ##GPSCLRX#
Enter your MSL Code
let the phone reboot.
I hope this works for you.

How do you get your MSL code?

Gonna try that now, I hope it works...
How did you figure out it was the GPS?
EDIT: Just tried what you suggested. Didn't seem to work: after it rebooted and got past the Fresh screen, it rebooted without me touching it.

jthurs said:
How do you get your MSL code?
Click to expand...
Click to collapse
Use MSL reader, it's in the Market (and free).

Alright, after doing what aj74 mentioned and it not working, I left the battery out for a bit then powered it back on. That was at 3pm. At around 4, it had yet to reboot so I decided to restore all of my apps with Titanium Backup. I have yet to have a random reboot, though I highly doubt it's fixed.
I'm afraid to use my phone :-/

same problem. looks like this is becoming more and more frequent. i have tried unrooted, and a bunch of rooted roms. this is a problem that needs solving fast.

lo' and behold, as I was getting confident and rearranging things on the phone the loops began again.

I guess I feel better
Well, I feel better since it isn't just me. It has been working fine, then I took the phone on my first trip and as soon as I got off the plane on Wednesday, the random restarts started.
I'm guess some type of app update caused it, but god only knows which one. I did a factory reset, the gps reset, restored a nandroid backup from late september, and turned off all synching. Still get the reboot loop.
I seem to be able to make it stop for a little while by putting the phone in the freezer, but I can't believe we would all start having this problem at about the same thing if it was simply a overheating issue.
Update:
I was roaming when all of this happened, and now that I'm home, I haven't been able to get the phone to mess up. This will make it tough to take in for service. It still may be a heating issue, however, since it is not hot where I live, but it was hot where I was visiting.
Update 2:
I have now been able to get the problem to happen in my home area. The battery temp was > 100 F when it happened.

Bootup Error, init: untracked pid 123 exited

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

[Q] AT&T tilt problem - gets stuck 2 to 3 times a day

Hi all,
My phone is AT&T tilt.
Kernel : 2.6.25-dirty modified using Atools - Panel 2 type
Android 2.2.1 - Not So Super Froyo RLS 18 updated with latest androidupdate using the kernel menu to update.
all installed on NAND , using p2 for system and p3 for data and auto for swap
My problem and it seems that i am the only one or at least no one has reported it, is that the phone gets stuck 2 or 3 times a day with the backlight dimmed and the screen pixeled with grey and black random pixels.
If anyone tries to call me when this happened, my phone doesn't do anything and they have a normal ringing as if i am not answering. when i restart the phone there would be no log of what happens during the stuck phase. Sometimes it also gets stuck during the restart and i have to clear the Dalvik Cache, and all info , contacts gmail account . everything is gone and i have to resync.
Any help or pointing me to what i am doing wrong is highly appreciated.
Thanks to all in advance

Are you familiar with the Fn + Left Soft Key, wait 5 seconds, then Fn + Rt Soft Key?
Sounds like it's just stuck in VSync, which because the phone is not top of line, Android refreshes the screen faster than the phone can react, so there's a delay script in place that helps fix this, but this stuff still happens due to limited hardware.
Whenever you get the pixel snow, try that combination above too see if that helps. If not the only other thing that can be happening is data corruption, which has been around since Day 1. Try installing system on NAND and data on your SD Card and that should help with your data corruption issues as well.

Also, if you are installed completely on NAND, you could do backups of your /data partition on a daily basis (takes about 1 minute on replimenu). I do mine daily even though I have a fairly stable install. I have been having issues with the ribbon cable lately and the phone will lock in sleep mode and run the battery down a bit. Not sure if this is software or hardware related.
IMHO, if you download anything from the market, back up your /data partition as soon as you can to save all your info and newley downloaded apps or games.

Krazy-Killa said:
Are you familiar with the Fn + Left Soft Key, wait 5 seconds, then Fn + Rt Soft Key?
Sounds like it's just stuck in VSync, which because the phone is not top of line, Android refreshes the screen faster than the phone can react, so there's a delay script in place that helps fix this, but this stuff still happens due to limited hardware.
Whenever you get the pixel snow, try that combination above too see if that helps. If not the only other thing that can be happening is data corruption, which has been around since Day 1. Try installing system on NAND and data on your SD Card and that should help with your data corruption issues as well.
Click to expand...
Click to collapse
thanks a lot , no i am not familiar with this option and i will give it a try as soon as it happens , i also should try the data on SD .

PoXFreak said:
Also, if you are installed completely on NAND, you could do backups of your /data partition on a daily basis (takes about 1 minute on replimenu). I do mine daily even though I have a fairly stable install. I have been having issues with the ribbon cable lately and the phone will lock in sleep mode and run the battery down a bit. Not sure if this is software or hardware related.
IMHO, if you download anything from the market, back up your /data partition as soon as you can to save all your info and newley downloaded apps or games.
Click to expand...
Click to collapse
i tried the backup using the replimenu , but it is not working properly . it a long time , after that i restart the phone and the backup file size would be 0 KB.
that was on the old build that i used , i will try it with this build , thanks a lot

Galaxy nexus alarm/clock causes shut downs

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

Wi-Fi completely broken.

What happened/is happening:
Wi-Fi won't turn on. This includes anything that uses it. (Tethering, normal connection to routers)
The settings application will try to turn it on, but it just sits there until I enter another menu or back out and re-enter, at which point it shows it as off. Built-in wifi tethering menu in the same place says 'Error' and the checkbox is disabled.
USB tethering still works.
OpenVPN and its tun0 device still works.
Bluetooth... I don't use it, so I don't know.
What I've done:
I tried getting a logcat but I don't have any computers that I have administrative access to install the HTC drivers on, I wasn't able to.
I did some searching, and some frantic listing of directories, and comparing them to a friend's G2, and I found something.
`ls /proc/sys/net/ipv6/conf/` (same with /proc/sys/net/ipv4/conf/) gives me a list of directories corresponding to devices from `iwconfig`, but none with the names of eth0, wlan0, or wl10. List of devices from iwconfig:
lo, gannet0, dummy0, ifb0 ifb1, rmnet0, rmnet1, rmnet2, usb0, sit0, and ip6tnl0
Roughly the same list in /proc/sys/net/ipv6/conf/ (and /proc/sys/net/ipv4/conf/)
I've also flashed CM10.1 (Flinny's Andromadus build 25) and CyanogenMod 7.2.0 stable from their wiki. I started from 10.1, reflashed it, then flashed 7.2.0. No change.
I used CWM Recovery to format my /system partition and restore CM7.2.0 Stable, no change.
I have searched for about two weeks, and I've come up with nothing, short of getting a new phone, or getting some kind of backup of the files. I need a solution, because having Wi-Fi working is pretty important right now.

Had an issue like this way back when once and a clean wipe (including efs partition) and reinstalling ROM fixed it. Toward the top of this thread you'll find a link to the superwipe tool I'm talking about
http://forum.xda-developers.com/showthread.php?p=43195539
If this doesn't work then digging through the old threads for a fix should turn something up as I've seen many WiFi error threads over the years.
Oh and a logcat should help, just get an app from play store if you have no PC to use
Sent from my Nexus 4 using Tapatalk 2

Worked!
demkantor said:
Had an issue like this way back when once and a clean wipe (including efs partition) and reinstalling ROM fixed it.
Click to expand...
Click to collapse
Worked great! Thanks! It kinda wiped my data partition though, so I had to spend an hour queuing downloads on the Play Store. Better than having broken Wi-Fi.

I was wrong.
ArghArgh200 said:
Worked great! Thanks! It kinda wiped my data partition though, so I had to spend an hour queuing downloads on the Play Store. Better than having broken Wi-Fi.
Click to expand...
Click to collapse
Not fixed, actually. I thought it had worked, but last night when I decided to power on my computer and start tethering to it, it was broken again. I'm getting kinda tired of putting up with this phone.