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

Root Phone is reading my mind...refusing recovery...

muab

Android Enthusiast
May 22, 2010
337
42
Hey fellows, running a D1, rooted on BB0.4 and the provided kernel. I have set CPU set at 800 and drops to (I think) 150 with the screen off.
I have been frustrated with the battery life so I thought I would try a new kernel.
Here is the amusing part.
I just went to RM and downloaded several kernels...installed NONE of them.
Tried to reboot into clockwork and it stuck at the moto logo. Another attempt to boot into Clockwork just booted normally but the phone is acting a bit odd.

trying third attempt now going from RM using "boot to recovery"....

And stuck at Moto logo again...

I believe my phone may be psychic and figured out I was just thinking about changing kernels....

Any other ideas?
 
yes, when I was on stock 2.1 I had to reflash Clockwork a number of times but I thought on BB it would not do that anymore.
Still, I did try reflashing Clockwork, and I just tried going to recovery with X and power button and it froze at the moto logo.

Hmmm....

Last week I booted into recovery fine and made a nandroid backup. Now I just download some kernels and it freaks out....
 
Upvote 0
In RM, do you have the option to install SPRecovery?
If so, I would install that and then see if you can get into recovery. If SPRecovery works, then maybe re-install clockwork again and try again? AFAIK downloading a bunch of kernals, shouldn't stop recovery from working.

Okay, tried flashing SPRecovery twice and got an error both times. Now tried reflashing Clockwork again and it said successful...trying to boot into recovery now...and....fail.

Perhaps the 8th time now failing to boot into Clockwork. Hmmm, I wonder what the heck is going on...?
 
Upvote 0
Hmmm, not keen on unrooting.


I have tried flashing SPR a number of times and it always fails. When I flash Clockwork it always succeeds but then booting into any recovery fails.

Grrr.


I really appreciate you taking the time to try and troubleshoot with me...

Hopefully I don't have to unroot. If I do, I will probably just leave this as is for now.

Can SetCPU settings muck up anything? That is the only thing I have changed since the last time I was in recovery.
 
Upvote 0
Oh, I thought by reading your mind to refuse recovery was an addiction thing...:cool:

I doubt this was where your issue was, but this may help in the future: in SetCPU, I never check Set on Boot. Because if you max it out, the next time you flash a kernel, it'll be set at that level. And our Droids don't like every kernel at every speed.

I have had your particular issue before in the past, but I can't remember what I did to remedy the issue. Fixing permissions sometimes helps. Also updating Busybox can also help sometimes. And try to make sure you have as much of a charge as possible when flashing. A lot of times, that's the issue right there.
 
  • Like
Reactions: muab
Upvote 0
I run into this problem often with Clockwork. What usually works is in ROM Manager, hit menu button then tap "Clear Download Cache". Then tap "Flash Alternate Recovery" to flash SPR Recovery, and finally tap "Flash Clockworkmod Recovery" and flash that.

After that I can generally boot into recovery without issue. Clockworkmod Recovery is usually less finicky when I X-Boot into recovery.
 
Upvote 0
I run into this problem often with Clockwork. What usually works is in ROM Manager, hit menu button then tap "Clear Download Cache". Then tap "Flash Alternate Recovery" to flash SPR Recovery, and finally tap "Flash Clockworkmod Recovery" and flash that.

After that I can generally boot into recovery without issue. Clockworkmod Recovery is usually less finicky when I X-Boot into recovery.

You know I do think that there was something about that download cache. I had downloaded a bunch of kernels and one of them failed, then the whole phone was acting glitchy. Then I had this failure to boot to recovery. After many failures, charging the battery and downloading one more kernel (that was successful), ROM Manager acted different and the phone stopped being weird.
Then..successful recovery.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones