overclocking all the time will kill the battery quickly. I use CPU Cruise Control to keep the max speed at 600 mhz unless I need an extra boost, then I set it to full overclock. I've been able to overclock with netflix no issues - watched a 30 minute show in fact. When I was done, I went back down to 600.
Custom Kernel V 2.0 for the Samsung Replenish...
- Thread starter anon(335536)
- Start date
Today was my first attempt, and not for any longer than a few seconds either. I did use your controller app and it didn't cause issues. My phone would just either lock up or reboot upon passing 600mhz. Not sure what happened to be honest. I'll try it again after a full charge though.
The same thing has happened to me. I do not knoow why but I put my phone up past 600 and it just freezes the phone. I've tried a few times and every once in a while it did worked fine. A few times, CruiseControl force closed.
Sent from my SPH-M580 using Tapatalk
Sent from my SPH-M580 using Tapatalk
Left ya a nice review for the app. Tried running an overclock again to find out the Replenish won't handle anything above 748mhz. The slider lets us go just beyond that limit, rebooting the phone regardless of whether or not it actually spikes that high. So for anyone else that had my issue, that's "748800" on the max slider. I set mine to this with on demand and Sonic CD played perfectly. Loading apps and screens was also near-instant at this speed. Just don't forget to go back when you finish playing so you don't kill the battery 
Thanks for the good review. I appreciate all I can get to counteract the idiots who give me one star because they installed the app on a non-rooted phone and then complain when it does not work. I wish I could delete those comments, but I can't.
As for the force closes you guys are seeing, I've fixed some bugs i the market released versions of the app that causes force closes. I need to roll those updates into your version and will do so sometime soon and release here.
As for the phone rebooting issue at high frequencies, I personally have not seen one reboot at any frequency. However, that being said, the stock setup for the CPU only allows 600 mhz, so anything more than that could cause reboots, etc. I got the overclocking numbers from someone else in the android community. He actually developed a kernel to go even faster, but I opted to not allow those values in my kernel as I felt they were too unstable and could potentially burn out the CPU.
CPU Cruise Control does not actually decide what frequencies to provide - it asks the kernel what frequencies it allows and then just customized the sliders to go to those. Just an FYI.
As for the force closes you guys are seeing, I've fixed some bugs i the market released versions of the app that causes force closes. I need to roll those updates into your version and will do so sometime soon and release here.
As for the phone rebooting issue at high frequencies, I personally have not seen one reboot at any frequency. However, that being said, the stock setup for the CPU only allows 600 mhz, so anything more than that could cause reboots, etc. I got the overclocking numbers from someone else in the android community. He actually developed a kernel to go even faster, but I opted to not allow those values in my kernel as I felt they were too unstable and could potentially burn out the CPU.
CPU Cruise Control does not actually decide what frequencies to provide - it asks the kernel what frequencies it allows and then just customized the sliders to go to those. Just an FYI.
Learn something new every day 
I thought it was the app for some reason. Do you have the latest kernel on your github, or is it still the one before adding the governors? Since it seems to slightly vary for us, I might like to decrease the max value for myself so I can safely use any value without forgetting I can't just flick the bar up as high as it can go to play a quick game.
I thought it was the app for some reason. Do you have the latest kernel on your github, or is it still the one before adding the governors? Since it seems to slightly vary for us, I might like to decrease the max value for myself so I can safely use any value without forgetting I can't just flick the bar up as high as it can go to play a quick game.I ran at the highest speed today for about 30 minutes (just browsing the web, doing e-mail, etc) with no reboots or freezes. I'm guessing your hardware must be out of trim a bit. Unfortunately, there is nothing we can do about that - that's a hardware thing done at the factory on a device by device basis.
I;ll get the git repo updated sometime soon. I've been looking into undervolting, so I need to clean things up. By the way, it appears our little CPU can not be undervolted from what I have read so far. So I don't know if I will be able to squeeze any more batt life out of this guy.
I;ll get the git repo updated sometime soon. I've been looking into undervolting, so I need to clean things up. By the way, it appears our little CPU can not be undervolted from what I have read so far. So I don't know if I will be able to squeeze any more batt life out of this guy.
awww.... do you have to already be rooted to use this? im on stock 2.3.6 and cant find a way of rooting.............
ummm... quick question... does anyone know how to root 2.3.6? im on a samsung replenish and cant root... im thinking about PhoneiX but i dont want to without a recovery as a safety net. plus i have to wait til next month to do anything that completely changes the rom, considering its someone elses til they give it to me next month (theyre upgrading) and i cant clear the data, tho i can go ahead and root it.
There is no root method for the replenish on gb. You need to install phoenix rom to get root the easiest way. Phoenix rom 0.3 is coming out soon. I'd wait for that.
And yes. You need phoenix rom (which roots the phone) plus my custom kernel and an app like cruise control to overclock.
And yes. You need phoenix rom (which roots the phone) plus my custom kernel and an app like cruise control to overclock.
ghaaaaa...... and i have setcpu already. ill just factory reset and do you know if the SWUpgrade exploit will work for the flashing? you know, where you replace the contents of the the Program Files>Samsung Electronics>SWUpgrade>Models>Binary folder with what you want to flash? it seems alot simpler than messing with flashboot or odin. yes, ive rooted 3 phones (2 with superoneclick and one with the SWUpgrade + slapkernel v1.1) but ive only been messing with this stuff for maybe a week. and i had my first phone (inspire 4g) 5 or 6 monthes ago and switched plans in about 3 monthes, and now i have an xperia play 4g running (rooted) 2.3.3. Im a quick learn, but i still dont know all the flashing stuff
EDIT: and i know setcpu is a root only app, i meant i can just install after flashing PhoeniX
EDIT: didnt see the newest post before mine because its on the page after the one i bookmarked, but does that mean i cant flash phoenix if i do it? and how would i do it? what do i click in odin??? and where do i get the right form of su?
EDIT: and i know setcpu is a root only app, i meant i can just install after flashing PhoeniX
EDIT: didnt see the newest post before mine because its on the page after the one i bookmarked, but does that mean i cant flash phoenix if i do it? and how would i do it? what do i click in odin??? and where do i get the right form of su?
Last edited:
i followed a guide that let me flash cwm and install the app, but no root???
ughhh... i cant change the permissions.... i need chmod 644, right? every time i try it wont let me do it................ dont you have to have root to change permissions...? so im kinda running in circles....................................................... and su will install without odin.........................
UPDATE: CWM GIVES ME SU PERMISSIONS WHILE ITS RUNNING!!!!!!!!!!!!!!!!!
ughhh... i cant change the permissions.... i need chmod 644, right? every time i try it wont let me do it................ dont you have to have root to change permissions...? so im kinda running in circles....................................................... and su will install without odin.........................
UPDATE: CWM GIVES ME SU PERMISSIONS WHILE ITS RUNNING!!!!!!!!!!!!!!!!!
Last edited:
ghhaaaaaaa!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! i edited my post for a newer version of my tutorial and it turns out when i was off, my mom copied something and my clipboard is lost!!!!!!!!!!!!!!!!!!!!! ugh... ill have to re-type it.... and no, i dont know my way around linux, i just went with what i thought would work. i guess im just cool like that. lol.
Last edited:
Great tutorial - thanks! Not for the faint of heart, but you obviously knonw your way around linux. Phoenix ROM would have done all this for you, but now there is no need to wait. As a preiocus post said, you need phoenix because my custom kernel assumes the ext4 filesystem is the active filesystem. You are currently running samsungs RFS (aka really f*in slow) file system.
Hey All - just an FYI that I updated the Cruise Control apk I had attached to the second post in this thread. This one has some bug fixes from issues I found when I posted it to the market. Also, note it is not the "Pro" version as I am giving you all the paid app free. It is only free for those using my custom kernel (otherwise everyone with ny phone could download and use this app version without paying which I obviously don't want to do for the entire android user base 
.
Please uninstall the old version before downloading and installing this one.
.Please uninstall the old version before downloading and installing this one.
also at: http://forums.androidcentral.com/sa...-guide-stock-2-3-6-replenish.html#post1651482
REVISED TUTORIAL IN ROOTING 2.3.6 SAMSUNG REPLENISH
warning for experienced adb users!: this was made with noobs in mind. you may learn something (from me! a noob! XD) but anyways, enjoy!
this does not affect anything on the phone except for adding the ability to access root permissions. CWM (hover over any acronym with dots under it to see the full name) is not permanent, it disappears after you use it, and nothing on the phone is affected, as far as i know. i had just factory reset the phone, so use at your own risk...
you may need to know:
root of a drive- C:\ or D:\. the point you cannot "go broader" (aka-exit the folder youre in) without leaving the drive
OPTIONAL PRE-REQUISITE STEP: make sure you have at least 400 mb of memory (i know, thats alot, but just in case) on your sd card so you can back up your entire phone! i reccomend doing them all (dont do 2 and not one!!!!!!!!!!!)!!!
1. download here: http://forums.androidcentral.com/at...809-jump-development-boost-replenish-odin.zip and unzip to your desktop. if you dont have the android sdk, simply copy the adb.exe file to the root of your primary drive for later
this download was put together by joshua.worth and i will remove at his discretion.
2. download the su.zip attatchment and unzip into "platform-tools" where you installed the android sdk, if you have it, or put onto the root of your primary drive if you havent.
3. start phone while holding "spacebar" and "p". "downloading..." should appear on the screen in yellow text
4. plug into the computer and run "Odin_Multi_Downloader_v4.42.exe"
5. select SPHM580.ops for "OPS" and Replenish-CWM5.tar for "One Package" (they should be the only options) DO NOT CHANGE ANYTHING ELSE
6. hit "Start" and DO NOT REMOVE FROM THE USB.
7. as the phone reboots, hold "u" until CWM opens and set the phone down. you should close Odin now.
OPTIONAL FOLLOW UP STEP: use the volume keys to navigate to the backup and restore option and use enter to select backup. wait for it to finish completely and take you back to the the CWM main UI. continue with the guide
8. open the command prompt (type cmd.exe in search or run in the start menu, depending on your version of windows) or use some form of terminal emulator on your operating system of choice. command prompt is preferred due to the fact i know it can get the job done, but do what you will.
9. navigate to the drive your sdk is on and into "platform-tools" or to the folder you put the adb.exe and su files on. the default should be [name of drive]:\Users\[username]\. use the "cd.." command til youre at the root of the drive, and if you installed the sdk, type "cd android-sdk-windows/platform-tools" or just go to the root of the drive and go to the next step if you havent. just be sure adb.exe and su are there.
10. type this in line for line, with enters in between. the blue "~#" in the later lines is the prompt you should have. do not type this. it will be in blue. (clockworkmod should still be open on your phone at this point)
adb shell
~#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
~#exit
adb push su /system/bin/
~#chmod 777 /system/bin/su
~#reboot
DO NOT CLOSE THE COMMAND PROMPT YET FOR THE SAKE OF CONVENIENCE
11. when you're phone has rebooted, go back to the open command prompt, which should be where it was before you typed "adb shell"
12. type "adb shell". you will see a prompt of "$." type "su." if you have a prompt of "#" rejoice! you have permanent root! now you can go on the Play Store and find "Superuser" and "Busybox" (they should be free. if you cant find it, get ahold of me and ill try to supply the newest updates) if not, and you have a backup from optional step 2, you should go through til you hit CWM and restore the backup. if not, make one now and reattempt everything aside from downloads and the moving the files around on your computer.
OPTIONAL FINISH STEP: i dont know how you install CWM permanently, but you should do this so you can make routine backups of your rom and store them somewhere like on a box.com or mediafire.com account. (use hjsplit to break it into pieces for uploading and reassemble after download for flashing if its too big). to use a recovery, enter CWM (either the way i have here or if you have permanently installed, just reboot and hold "u") and navigate to "backup and restore," "restore," and select the recovery you wish to use on your sd card (make sure when you take out a backup for storage, you zip up the entire folder with the name that contains the date and time of your backup.) it will overwrite everything on your phone to be exactly like it was when you backed it up.
good luck! have fun!
Update: soon ill be posting links to a good recovery thats pre-rooted that has nothing except the root, superuser app, and busybot (installed) plus one thats pure. it wont even have CWM installed. if you softbrick your phone, when i get it up, just download, unzip into your sd card, and follow the separate readme steps that ill have zipped into it. OVERWRITE if you already have clockworkmod settings and stuff on your sd card, just to be safe. anyways, coming soon
contact me at isavegas@live.com
REVISED TUTORIAL IN ROOTING 2.3.6 SAMSUNG REPLENISH
warning for experienced adb users!: this was made with noobs in mind. you may learn something (from me! a noob! XD) but anyways, enjoy!
this does not affect anything on the phone except for adding the ability to access root permissions. CWM (hover over any acronym with dots under it to see the full name) is not permanent, it disappears after you use it, and nothing on the phone is affected, as far as i know. i had just factory reset the phone, so use at your own risk...
you may need to know:
root of a drive- C:\ or D:\. the point you cannot "go broader" (aka-exit the folder youre in) without leaving the drive
OPTIONAL PRE-REQUISITE STEP: make sure you have at least 400 mb of memory (i know, thats alot, but just in case) on your sd card so you can back up your entire phone! i reccomend doing them all (dont do 2 and not one!!!!!!!!!!!)!!!
1. download here: http://forums.androidcentral.com/at...809-jump-development-boost-replenish-odin.zip and unzip to your desktop. if you dont have the android sdk, simply copy the adb.exe file to the root of your primary drive for later
this download was put together by joshua.worth and i will remove at his discretion.
2. download the su.zip attatchment and unzip into "platform-tools" where you installed the android sdk, if you have it, or put onto the root of your primary drive if you havent.
3. start phone while holding "spacebar" and "p". "downloading..." should appear on the screen in yellow text
4. plug into the computer and run "Odin_Multi_Downloader_v4.42.exe"
5. select SPHM580.ops for "OPS" and Replenish-CWM5.tar for "One Package" (they should be the only options) DO NOT CHANGE ANYTHING ELSE
6. hit "Start" and DO NOT REMOVE FROM THE USB.
7. as the phone reboots, hold "u" until CWM opens and set the phone down. you should close Odin now.
OPTIONAL FOLLOW UP STEP: use the volume keys to navigate to the backup and restore option and use enter to select backup. wait for it to finish completely and take you back to the the CWM main UI. continue with the guide
8. open the command prompt (type cmd.exe in search or run in the start menu, depending on your version of windows) or use some form of terminal emulator on your operating system of choice. command prompt is preferred due to the fact i know it can get the job done, but do what you will.
9. navigate to the drive your sdk is on and into "platform-tools" or to the folder you put the adb.exe and su files on. the default should be [name of drive]:\Users\[username]\. use the "cd.." command til youre at the root of the drive, and if you installed the sdk, type "cd android-sdk-windows/platform-tools" or just go to the root of the drive and go to the next step if you havent. just be sure adb.exe and su are there.
10. type this in line for line, with enters in between. the blue "~#" in the later lines is the prompt you should have. do not type this. it will be in blue. (clockworkmod should still be open on your phone at this point)
adb shell
~#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
~#exit
adb push su /system/bin/
~#chmod 777 /system/bin/su
~#reboot
DO NOT CLOSE THE COMMAND PROMPT YET FOR THE SAKE OF CONVENIENCE
11. when you're phone has rebooted, go back to the open command prompt, which should be where it was before you typed "adb shell"
12. type "adb shell". you will see a prompt of "$." type "su." if you have a prompt of "#" rejoice! you have permanent root! now you can go on the Play Store and find "Superuser" and "Busybox" (they should be free. if you cant find it, get ahold of me and ill try to supply the newest updates) if not, and you have a backup from optional step 2, you should go through til you hit CWM and restore the backup. if not, make one now and reattempt everything aside from downloads and the moving the files around on your computer.
OPTIONAL FINISH STEP: i dont know how you install CWM permanently, but you should do this so you can make routine backups of your rom and store them somewhere like on a box.com or mediafire.com account. (use hjsplit to break it into pieces for uploading and reassemble after download for flashing if its too big). to use a recovery, enter CWM (either the way i have here or if you have permanently installed, just reboot and hold "u") and navigate to "backup and restore," "restore," and select the recovery you wish to use on your sd card (make sure when you take out a backup for storage, you zip up the entire folder with the name that contains the date and time of your backup.) it will overwrite everything on your phone to be exactly like it was when you backed it up.
good luck! have fun!
Update: soon ill be posting links to a good recovery thats pre-rooted that has nothing except the root, superuser app, and busybot (installed) plus one thats pure. it wont even have CWM installed. if you softbrick your phone, when i get it up, just download, unzip into your sd card, and follow the separate readme steps that ill have zipped into it. OVERWRITE if you already have clockworkmod settings and stuff on your sd card, just to be safe. anyways, coming soon
contact me at isavegas@live.com
Last edited:
This is done by removing or commenting out the install-recovery.sh line in init.rc (inside boot.img). Then you can safely delete it from (I believe) /system/etc/install-recovery.sh.
uhhhhhhh................................................. idk..................... on my xperia play i just downloaded an app that did it for me (i love pc companion. its like a get out of jail free card XD) but ill have to look into that later. problem is, i dont quite understand what youre talking about? the img in what? the phone itself? how do i access it? i a noob, remember? i stumbled upon this by playing around and it worked... i may be ok at rooting (ive done 4 phones in the week since i first started messing with it) but for this i need step by step... sorry........... 0.o
Just delete install_recovery.sh as firehak suggests. You don't need to pull it from init.rc. that will work also but is more involved. I just delete it and cwm sticks around.
Install_recovery.sh is a safety mechanism that always pushes sprints version of the recovery image each time the phone boots normally. The idea is to make sure there is always a good recovery image on the phone. However that being said, I've never heard of a recovery image suddenly going bad, so I would not think twicw about deleting install_recovery.sh. happy deleting.
Install_recovery.sh is a safety mechanism that always pushes sprints version of the recovery image each time the phone boots normally. The idea is to make sure there is always a good recovery image on the phone. However that being said, I've never heard of a recovery image suddenly going bad, so I would not think twicw about deleting install_recovery.sh. happy deleting.
Similar threads
Trending Posts
-
-
find last location of phone when it says "location unavailable" in "find my device" ?
- Started by gargavf
- Replies: 0
-
-
Question Samsung Galaxy Smart Watch - Dicky Heart Rate Monitor
- Started by ripface
- Replies: 0
Facebook
Twitter
Instagram