Got an issue, phone keeps rebooting at the droid logo boot video.

[evildesign]

Yesterday I rooted the phone, and it rebooted fine after that, I then moved a bunch of applications in /system/apps/ to file.apk to file.apk.old, but I did some files like VoiceCommand and HelpSomething and one other that I cant remember, plus your regular blockbuster and amazon files. I also installed SetCPU and had it set on boot with the powersave and another to change on boot. I decided to restart the phone and now it stuck in this. I am not sure, but I forgot to remount /system as ro when I rebooted, and wondering if that might be the issue.

I am wondering how can I get into the phone over adb while it in this mode, so I can rename those files and see if it complaining about that partition not being ro.

[evildesign]

So I can get it to load into the flash mode, but where do I get a rom to reflash it?

[evildesign]

The more I keep thinking about this, I think it actually a hang in the system loading, and it not a restart, since it doesnt ever show the motorola screen again and the video keeps looping. I am waiting for the phone to charge to see if I can get into recovery mode.

[ChugIt]

Why did you go and rename the files if you didn't know what you were doing? I would unroot back to 2.0.1 and start over. Loading a custom ROM generally has options to remove apps, and they run the scripts correctly. Never mess with system files if you are not exactly sure what you are doing with 100% certainty.

[droidman101]

Why did you go and rename the files if you didn't know what you were doing? I would unroot back to 2.0.1 and start over. Loading a custom ROM generally has options to remove apps, and they run the scripts correctly. Never mess with system files if you are not exactly sure what you are doing with 100% certainty.

Only this guy has a droid X.
Ok, the problem is with setcpu, NEVER set it on boot unless you are setting it at stock 1ghz ondemand. If you can boot into recovery wipe data and cache, that should fix it.

[ChugIt]

God I hate when I think I'm in a Droid thread and I'm not! 2nd time this week, sorry....

[droidman101]

God I hate when I think I'm in a Droid thread and I'm not! 2nd time this week, sorry....

I've done that some times, don't be angry at yourself, you're not alone

[evildesign]

That what I actually did, and it worked, So I will not set setcpu to load on boot.

[droidman101]

That what I actually did, and it worked, So I will not set setcpu to load on boot.

What happened was your phone booted up past the M because setcpu hadn't loaded yet, then when setcpu turned on it didn't give enough juice for the phone to totally boot up, hence the bootloop. When the phone turned off it closed setcpu, which starts the process again.

[evildesign]

Yeah, well you learn best by trial and error, now I know don't do that.

I just activated it and just sitting on communicating with server, if I reboot it just stays at the droid video, so I am going to leave it here to see how long this communicating with server takes, because I had to do another reset on it.