clockopia put me in a boot loop

Pebcak · March 29th, 2012, 02:03 PM

I was messing about with changing the Clockopia.ttf font and did a reboot and forgot to adjust the permissions and now the phone won't boot up.

adb devices doesn't see the phone and in Windows device manager shows the phone as unable to start.

Does anyone have a way for me to do this without having to flash the phone which strikes me as a tad excessive just for a font.

Thanks

Pebcak · March 30th, 2012, 11:06 AM

104 views and no suggestions? That tells me one of two things. I'm the only one to have done this, but as much as I'd like to sometimes think so I'm just not that special.

So that leaves me with my original question wasn't clear enough but when I re-read my original post I'm not sure how to phrase it differently.

So I'll go with has anyone read my original post and wasn't sure what I was asking? If so let me know and I'll try to explain it further and clearer.

Thanks again

dannymur · March 30th, 2012, 04:29 PM

You got Custom Recovery? Like ClockworkMod?

If you have, try fix permissions!

Or, Factory Reset even with Stock Recovery...

Pebcak · April 4th, 2012, 07:36 AM

Quote:

Originally Posted by dannymur

You got Custom Recovery? Like ClockworkMod?

If you have, try fix permissions!

Or, Factory Reset even with Stock Recovery...

Nope no ClockworkMod so I had to go with a stock recovery which is fine (it's a good skill to know how to do) but it strikes me as a bit excessive for a clock font.

Mini rant time. Bear in mind I'm just starting out with Android and know very little but why on earth is a font for the lock screen clock system critical?

Wouldn't it make more sense for the phone to barf an error about unable to find font or unable to read font and keep going?