Does updating the kernel unroot the droid?

[banderbe]

I just updated from the stock DroidMod kernel to Chevy 1.2 update 3 and now it appears I no longer have full root permission.

If I open up a terminal and type 'su' I get the prompt asking me to allow so I click allow and it says permission denied.

The weird part is I then have a [root@droid] / # prompt.

[jasonb]

I just updated from the stock DroidMod kernel to Chevy 1.2 update 3 and now it appears I no longer have full root permission.

If I open up a terminal and type 'su' I get the prompt asking me to allow so I click allow and it says permission denied.

The weird part is I then have a [root@droid] / # prompt.

that's not the kernels fault. the kernel has nothing to do with that. something else is up.

[banderbe]

Okay.. I think this is at the root of why SetCPU (and MetaMorph) both don't work now.

No big deal I can always restore one of my backups.. just wish I knew why this happened.

[dadevers]

Okay.. I think this is at the root of why SetCPU (and MetaMorph) both don't work now.

No big deal I can always restore one of my backups.. just wish I knew why this happened.

One of the bugless beast ver. unrooted the phone some times. Did you install one of them?

[banderbe]

Okay.. I think this is at the root of why SetCPU (and MetaMorph) both don't work now.

No big deal I can always restore one of my backups.. just wish I knew why this happened.

One of the bugless beast ver. unrooted the phone some times. Did you install one of them?

Nope.. I bought the phone, then rooted it, then used DM Updater to get DroidMod 1.0.

Then, today I downloaded Chevy's kernel, installed it with SPRecovery and rebooted.

Now, root is clearly screwed up.

I realized I didn't check the 'remember selection' box when Terminal Emulator asks you to Allow, so I did that.

And now Terminal Emulator just hangs.

I think I'm going to revert the whole phone back to stock.