Root SetCPU question

[AMTrombley0924]

Is it safe to do Menu>Device Selection>Show Other Frequency Sets on my Droid and run it like a Nexus One 1gHz processor? I have a stock kernel and am currently at 800mhz after the autodetect.

 

[Lock-N-Load]

I would say no. use autodetect.

if you want to OC, get a kernel as that is the correct way to do it and the whole point of kernels.

 

[patch]

You can try but I don't think it will let you?


I'm also running stock everything (FRGB01 with Google kernel) and have been experimenting with SetCPU. Found at 800mhz had some stability issues, but last day or so running at 700mhz maximum has been working great so far.

 

[klwheat]

patch...have you tried a different kernel. I don't know anyone who isn't running at atleast 1ghz with good stability. I realize that all droids are different, but mine consistently runs 1.2 to 1.25ghz completely stable. Just thought you might want to try a different one.

 

[weapon.seven]

i apologize upfront but i am a novice person when it comes to ROOT but i recently rooted my droid, havent downloaded a rom or kernel yet but did get SETCPU and was wondering why i cannot overclock above 800mhz? is it because i need a ROM or KERNEL?

thanks in advance.

nevermind, sorry, thanks lock and load - i just needed to read more, sorry! chevy no1 here i come!

 

[Lock-N-Load]

Chevy's are a good place to start and 1.0 is a good pretty proven stable kernel to try first. if stable, then you try 1.1.. 1.25 etc and ideally, ulv kernals are nice as less power draw but I have read that in real world power draw that fluctuates, the low is pretty good.

 

[weapon.seven]

One more question, why when I attempt to install I only get picture of exclamation point within a triangle which just sit there and then when I reboot in the ROM manager it says 3 different options, one being sp recovery is " broken ", one is " other " and I can't seem to remember third one.. what am I doing wrong once I hit install it say to just simply follow installation instructions yet all it takes me to is an exclamation point? Can u help me out please? Thank u

 

[Lock-N-Load]

you lost your clockwordmod recovery. so, go into Rom Manager and "flash alternate recovery" (bottom of the list). Then, once you do that, reflash clockworkmod recovery and then you should be able to boot into recovery via "reboot into recovery"

by doing this, your essentially deleting off the faulty clockwordmod recovery with Sprecovery (the alternate recovery method) and then putting back a correct version of clockwordmod when you reflash it back on.

 

[patch]

patch...have you tried a different kernel. I don't know anyone who isn't running at atleast 1ghz with good stability. I realize that all droids are different, but mine consistently runs 1.2 to 1.25ghz completely stable. Just thought you might want to try a different one.

Yeah, I'm probably unique on these forums as I love messing with my rooted Droid, but want to stay on the "official" versions of Android I've so far avoided flashing any custom firmware/kernel/recovery yet and am planning on doing so as long as long Motorola and Google will be continuing to support this phone.

Thanks for the heads up though, good to know in case I do start to experience issues...

I did find it interesting that the stock FRG01B kernel allowed overclocking at all! Is this the first time ever? Still trying to find the best clock settings for my stock Droid, and so far 700 max and 125 min seems to be very stable and more responsive -- although there might be a placebo effect. Someone really needs to try to create some real-world benchmarks.

 

[gnath9]

Quadrant, Linepak and SetCpu are all ways of benchmarking. I tend to just go by feel tho as numbers can be mis-leading. I get better benchmarks with Chevys but I like the feel of jdlfg's better on my current set-up. If it runs smooth and stable thats good enough for me.

 

[patch]

Quadrant, Linepak and SetCpu are all ways of benchmarking. I tend to just go by feel tho as numbers can be mis-leading. I get better benchmarks with Chevys but I like the feel of jdlfg's better on my current set-up. If it runs smooth and stable thats good enough for me.

Yeah, I guess I meant more of a realistic benchmarks that we can run to get a sense for actual performance instead of an artifical benchmark number that has no real world meaning. Some sort of scripting would be necessary, for example something like how long it takes for browser to open and load your favorite site -- or open gmail and send a message -- or load up your favorite game, etc.

But I'm with you, at this point it's best to go with your "feel" especially if you're very familiar with how long things normally take, you should be able to notice a difference.

 

[Somniferum]

Yeah, I'm probably unique on these forums as I love messing with my rooted Droid, but want to stay on the "official" versions of Android I've so far avoided flashing any custom firmware/kernel/recovery yet and am planning on doing so as long as long Motorola and Google will be continuing to support this phone.

Thanks for the heads up though, good to know in case I do start to experience issues...

I did find it interesting that the stock FRG01B kernel allowed overclocking at all! Is this the first time ever? Still trying to find the best clock settings for my stock Droid, and so far 700 max and 125 min seems to be very stable and more responsive -- although there might be a placebo effect. Someone really needs to try to create some real-world benchmarks.

Wow, I thought I was the only one taking this approach. I don't feel comfortable with the idea of flashing custom ROMs/kernels/recovery (but more power to those that do). I love overclocking though (always homebuild and OC my PCs) so when I heard the Froyo kernel allows up to 800Mhz, I went for it. I'm on FRB01B (manual update) and used Universal Androot to root, then SetCPU to OC.

My main concern now is that I hear there's an OTA update coming for FRB22D, and I don't know what I should do. Unroot first, accept the OTA, then try to regain root? I can't get a firm answer as to whether Androot even works with FRB22D. And since I don't have a custom recovery, I'm not sure if just blocking the update is even possible. When I post in other forums about this, everyone just assumes I'm running custom recovery/ROMs/kernels and many people don't even seem to realize it's possible to gain root on 2.2 without them.

Any ideas? What are you planning to do? As I understand it, in all likelihood the OTA update will cause us to lose root even if we don't unroot first. These are the kind of annoying ambiguities that make me want to stay as close to stock as possible. But I definitely want to keep OC'ing because the speed boost is worth it.

 

[gnath9]

custom Roms run way faster at the same mhz. Its not the overclock in mhz's alone that gives us great speeds.

I just dont get why VZW/Moto can't do half of what the Devs here can in terms of reduced lag and overall rom performance.

 

[patch]

Wow, I thought I was the only one taking this approach. I don't feel comfortable with the idea of flashing custom ROMs/kernels/recovery (but more power to those that do). I love overclocking though (always homebuild and OC my PCs) so when I heard the Froyo kernel allows up to 800Mhz, I went for it. I'm on FRB01B (manual update) and used Universal Androot to root, then SetCPU to OC.

My main concern now is that I hear there's an OTA update coming for FRB22D, and I don't know what I should do. Unroot first, accept the OTA, then try to regain root? I can't get a firm answer as to whether Androot even works with FRB22D. And since I don't have a custom recovery, I'm not sure if just blocking the update is even possible. When I post in other forums about this, everyone just assumes I'm running custom recovery/ROMs/kernels and many people don't even seem to realize it's possible to gain root on 2.2 without them.

Any ideas? What are you planning to do? As I understand it, in all likelihood the OTA update will cause us to lose root even if we don't unroot first. These are the kind of annoying ambiguities that make me want to stay as close to stock as possible. But I definitely want to keep OC'ing because the speed boost is worth it.

Great to hear that I'm not alone

I looked some of the official updates from previous release, as well some homegrown ones Peter Alfonso created and the actual script is human readable and not very hard if you're familiar with reading code. If we can get this zip which hopefully someone in the community will get us the actual link (as the FRGB01 update from Google) -- I'm planning on checking exactly what it does and I feel comfortable with it I'll be a guinea pig to see if I can safely execute the update on top of my rooted "official" FRG01B Froyo.

I believe there is a lot of misinformation being spread. As you have discovered a lot of people who maybe aren't very technical don't realize that root access does not mean custom rom/recovery. From what I have seen so far, there is no reason to believe it wouldn't be possible to install an official update on a rooted system with original firmware. Problems would arise with custom firmware since the OTA update always makes assumptions that all versions/checksums/files would be what is the official firmware, and fails otherwise.

 

[Somniferum]

Thanks, I feel much better knowing we're not completely at the mercy of the OTA.

I have seen it claimed several times at the droid-life.com blog that OTA updates always remove root access, but it's entirely possible that assumptions were involved regarding custom ROMs/kernels/recovery. At any rate, I hope you're right! Guess we'll find out soon enough.

 

[patch]

Thanks, I feel much better knowing we're not completely at the mercy of the OTA.

I have seen it claimed several times at the droid-life.com blog that OTA updates always remove root access, but it's entirely possible that assumptions were involved regarding custom ROMs/kernels/recovery. At any rate, I hope you're right! Guess we'll find out soon enough.

Please share those links if you come across any again, I'd like to look at any OTA "update.zip" that someone thinks will remove your root access.

I think at some point I did look at the 2.1 to 2.2 OTA 43mb update and I specifically checked to see if any of the required files for root were removed and could not find it in the script. It's certainly possible that they could remove your root access in an OTA update -- such as the "75mb full Froyo OTA update" that John Galt found since the script essentially deletes everything in your /system filesystem (where the super user stuff lives) and recopies all required files.

 

[Somniferum]

Please share those links if you come across any again, I'd like to look at any OTA "update.zip" that someone thinks will remove your root access.

Here's an example from today:

Verizon Pushing a New Froyo Update to Rooted Users

If you scroll down to the comments, Kellex (owner of the Droid Life blog) posts this reply to a question:

"If you have a custom recovery installed like Clockwork Recovery, then you should accept the update and it will be blocked by that recovery. If you don't, then I wouldn't accept it or it will kill your root."

(emphasis added)

Now granted he's speculating at this point since the exact contents of the FRG22D OTA are unknown, but he says it with enough authority that one would think it was based on legitimate experience. Kellex is always posting how-to guides on rooting and ROMs so he's seen as an Android guru around those parts.

To be fair, I guess he could be referring to that weird John Galt OTA since it's also alluded to in that thread. It's hard to say for sure with so many rumors flying around all at once.

 

[patch]

To be fair, I guess he could be referring to that weird John Galt OTA since it's also alluded to in that thread. It's hard to say for sure with so many rumors flying around all at once.

Yeah at this point that makes sense, especially since the screenshot shows a 75mb version of Froyo Again until we see the FRG22D OTA (maybe this guy has access to it?) I don't think you can say for certain.

We should all know soon, apparently they'll be pushing this OTA sometime this week.

 

[patch]

Preliminary review is that this update will install fine on a rooted FRG01B (as long as you didnt delete and system files.. There are TONS of system apps and libraries that are patched), but you will lose root access! One of the steps in the update will reset permissions on all files in system/bin where su lives and it requires special permissions to work.

I also see some updates to permissions to bluetooth files so it's possible the security fix that they say is part of FRG22D patches the exploit that EasyRoot uses.

 

[Somniferum]

Preliminary review is that this update will install fine on a rooted FRG01B (as long as you didnt delete and system files.. There are TONS of system apps and libraries that are patched), but you will lose root access! One of the steps in the update will reset permissions on all files in system/bin where su lives and it requires special permissions to work.

I also see some updates to permissions to bluetooth files so it's possible the security fix that they say is part of FRG22D patches the exploit that EasyRoot uses.

Well that's not the news I was hoping for.

Sounds like you may already have it, but just in case you don't, you can download the FRG22D update.zip file here and take a look at the scripts to confirm.

Assuming it's true that this update removes root and also removes the Androot/EasyRoot exploits, what now? What are you planning to do? I guess there's always the option of loading a custom recovery, which will supposedly block the update, but I really don't want to get into all that mess if I can avoid it. Really, really don't want to lose root though.

 

[Lock-N-Load]

first, that link you link to Somniferum is for NOT rooted users. It even says "*NOTE 2* - There is a chance you will lose root should you update to this from FRG01B. While the update file is only 1.6MB, it sounds like it is still capable of breaking root. Avoid for now if you wish to stay rooted." (and read the comments). So I think the answer is pretty clear that if you use THAT link you gave, your going to loose your root.

Second, there is a deodexed and ROOTED version of FRG22D available from P3 right here. so IF you want FRG22D and you want to KEEP root.. why not just go there and get it and viola.. be done with it and KEEP your root

ps - why is this under the SetSPU area

 

[Somniferum]

first, that link you link to Somniferum is for NOT rooted users. It even says "*NOTE 2* - There is a chance you will lose root should you update to this from FRG01B. While the update file is only 1.6MB, it sounds like it is still capable of breaking root. Avoid for now if you wish to stay rooted." (and read the comments). So I think the answer is pretty clear that if you use THAT link you gave, your going to loose your root.

Second, there is a deodexed and ROOTED version of FRG22D available from P3 right here. so IF you want FRG22D and you want to KEEP root.. why not just go there and get it and viola.. be done with it and KEEP your root

ps - why is this under the SetSPU area

Well as discussed in some of the posts upthread, Patch and I are both in the tiny minority of rooted users who don't want to load custom ROMs/kernels/recoveries. We are trying to maintain stock firmware while also keeping the ability to overclock, along with the other permissions that root allows. That deodexed P3 ROM looks cool but it doesn't meet our (admittedly unusual) criteria.

There was some question as to whether the official FRG22D update would unroot us or not, so I posted that link which is to the official, Google-signed FRG22D update file for analysis. It's pretty clear now though that not only does it unroot rooted phones, it also patches the exploit that EasyRoot/Androot were using to gain root. So it's bad news all around. I guess my best bet is to try and fend off the OTA update until someone finds a way to root FRG22D. Or give up and install a custom ROM.

P.S. -- This conversation started with the unusual fact that the stock FRG01B kernel allows overclocking, and went on from there. That's why we're in a SetCPU thread. Which makes me wonder ... even if we could root FRG22D, there's no guarantee that it would allow overclocking without a custom kernel. I wonder if it does?

 

[patch]

Well, at this point I'm going to wait and see what happens first No rush yet since I have FRG01B running great right now.

I was sure about OTA FRG22D removing root (because of permissions on su) but not sure exactly about EasyRoot, it just seemed possible since they changed permissions on bluetooth related files.

This morning author of EasyRoot confirmed my suspicions (www.unstableapps.org) and said he is working on a new version to see if he can get it working on the latest OTA.

 

[OMJ]

patch and somniferum not sure if you guys are interested in this but there is a pretty simple option for updating to FRG22D without losing root. The only hitch is you have to change your recovery although not to a custom one. You just have to change back to the 2.0.1 recovery. I pulled I copy of the recovery from FRG22D (pretty sure its the same as FRG01B) last night and could host it up so you could flash back to it if you want.

Details on the method are here
Android - whiterabbit.org

and here
http://androidforums.com/droid-all-things-root/141610-stock-rooted-2-2-froyo.html

whiterabbit has a similar philosophy on rooting to you guys he has just stuck with the 2.0.1 recovery cause its easier to update and keep root

 

[Lock-N-Load]

until someone finds a way to root FRG22D.

even if we could root FRG22D,

sorry, I guess I am totally missing something here. someone has and someone did root FRG22D... P3 did.. so not sure how that does not get you what you want?