• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Booting troubles

StLouis

StLouis

Member
So, I've had this problem for a long time... I just never made the effort to find out what's causing it, because it's not that much of a problem, really. Just a minor annoyance.

My milestone takes 3~10 tries to boot. Whenever I reboot it (or it reboots itself, running the still-not-so-bugfree CM6) it doesn't start like it's supposed to. I would expect it to go "White M" → "CM logo p1" → "Short vibration" → "CM logo p2" → "Lockscreen"
The thing is, my phone doesn't start that way. It often gets into some sort of bootloop back and forth between the white M and the CM logo. Sometimes it gets past the short vibration, but goes back to the M anyway. Then, after a few times, it progresses to the lockscreen.

I've had this problem for as long as I can remember (I think the only time it didn't happen was the first boot) but I didn't think much of it until I learned a friend of mine never had this problem on his phone. Am I alone on this one? Does anyone know how to fix it?
 
Can only be a CM problem. Because of the way CM boots (boots into Android and then boots itself AFAIR) this can be happening.

Try re-flashing CM and see what happens.
 
Well, the thing is, I had the exact same problem when I was on 2.1, so I find it highly unlikely it is the fault of Cyanogen. But maybe something else was causing that, and cyanogen just has a new problem with the same symptoms. I'll reinstall CM, just might yield some results.
 
So stock ROM was doing that too? Maybe you have an app that does that or something like that.
 
Well, I'm not completely sure full stock did it. I rooted my device a couple of weeks after I got the phone, so it might have started when I started using rooted stock. Would make more sense if an app is interfering with the boot, because I don't think anything without root permissions could even be considered a threat to the booting process. And the only "root" app I've used from the very beginning is Milestone Overclock (which was the reason I rooted in the first place)
Milestone Overclock does start at boot. So if it's really an app-problem, Overclock is causing it. But if that's the problem, I guess I'll just live with the weird boot, because I'm not giving up my 900MHz processor for a faster boot ;)
I'll search around if the overclock app causes problems for anyone else~
 
You must log in or register to reply here.
Back
Top Bottom