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

Root Help, phone is stuck in boot loop

L

lanceg

Well-Known Member
So silly me tried to replace the lock screen clock font, and apparently the phone didn't like the font I picked, because it is now boot looping

Is there any way to get the device to a point where I can get in via adb shell and restore the original font? (I backed it up)

Also, how do you boot into recovery? If I hold down vol - and power, I get a "polling" message that repeats itself, if I hold down vol+, vol-, and power, I get a picture of an android dude with a triangle and an exclamation point in it.
 
shimdachef said:
That is booting into recovery. You need to install a custom recovery first

http://androidforums.com/triumph-all-things-root/421674-clockworkmod-recovery-motorola-triumph.html
Click to expand...


Thanks man, trying that now. Will i be able to get into adb shell when booted into the customer recovery?

Alternatively, is there any way to get a flashable update that restores the Clockopia.ttf to the /system/fonts folder?

Edit: Got custom recovery installed and booted to it, ADB still doesn't show the phone under adb devices, but I suspect that's an issue with the particular PC I'm on now. I will try it later on a laptop that I know I has the correct drivers installed and has been able to get an ADB shell up before. I found an old post on xda where someone did the same thing I did and they were able to boot into recovery and do an adb push of the backed up font file and that fixed everything (I'm assuming I would need to mount /system prior to the adb push). Worst case scenario I just reflash the phone and spend an hour or so reloading my apps.
 
No dice so far, adb devices still shows no devices when booted into custom recovery. Any ideas?
 
Austrie said:
Well flash a stock rom to restore system..... I'll get you a link soon.
Click to expand...

Thnaks man, if you could provide a link to a stock ROM that would be awesome. I had v38 if that matters

Puzzled why adb refuses to see the device either in custom recovery or download mode
 
Thanks, I'll kep that as a last resort to try. I really would like to get an update.zip that just overwrites that one font file
 
lanceg said:
Thanks, I'll kep that as a last resort to try. I really would like to get an update.zip that just overwrites that one font file
Click to expand...

CWM allows you to only restore certain pieces (system, data, cache, boot, etc.). Judging by your situation, just restoring /system should fix your problem.

FYI, just because the device is boot-looping, doesn't mean you won't have access via ADB. When I'm working on stuff, I hit some boot loops occasionally. I use ADB to determine what's going on.
 
isaacj87 said:
CWM allows you to only restore certain pieces (system, data, cache, boot, etc.). Judging by your situation, just restoring /system should fix your problem.

FYI, just because the device is boot-looping, doesn't mean you won't have access via ADB. When I'm working on stuff, I hit some boot loops occasionally. I use ADB to determine what's going on.
Click to expand...

Issac man you are a lifesaver, how can I restore just /system from what was posted? Or even better, if there any way you could make up an update.zip that replaces the Clockopia.ttf on the device with the one from stock? Or explain to me how I can do it?

I've tried everything I know of and I still can't get adb to see the phone

Edit: WOOT!! isaac you rock!! I downloaded the stock Nandroid backup from this forum, and saw how to restor just /system, rebooted, and it works!!

I have a nandroid backup of my borked system to just in case this doesn't work and I'm forced to go back to the my hunt for an update.zip
 
Or, alternatively, I have a nandoid backupof my pooched install. I copied it over to my PC, took a peek in system.ext3.tar, and viola, there's my bad Clockopia.ttf. If there any way I can swap out that ttf with my backup, copy the backup files back to the phone, and restore it?

I tried doing it myself but got an MD5 mismatch

Edit, OK, I rerooted, reinstalled busybox, went in through adb sell, deleted the nandorid.md5 and used md5sum to make a new one. I am hoping that will let me flash my fixed copy of my system backup.

Of course by now my battery is near dead so it's charging up a bit.

Edit 2: Passed the MD5 check, but failed partway through the restore with a "Error while restoring system!" message. Any ideas?
 
You must log in or register to reply here.
Back
Top Bottom