yashsingh1/xdaforums huggingface dataset:
[EVO 4G Q&A, Help & Troubleshooting] dglowe343:
Experimenting with different kernels and overclocking will boost performance but can also lessen battery life. When overclocking, be sure to read as much as you can find on it. All of our phones respond differently. I've seen max speeds range from 1113mhz to 1267mhz. Always remember to NAND before messing with different kernels. IMO, SetCpu is the most commonly used app to manage clock speeds. Its a paid app available in the market.

Using a program like Autostarts wont necessarily boost performance but will increase battery life cuz certain apps you dont need running wont be allowed to start on their own.

Task killers are pretty much useless with Froyo since it only allows them to terminate background usage of the app. It wont completely kill the app. Android itself does a pretty good job of automatically killing apps that dont need to be running.

Since you're using Myn's, I'm sure many optimization/performance tweaks have already been made within the rom itself. I'm a Sense fan, but CM6 (AOSP based) is going to give you the absolute highest performance of any rom available to our phones. Sense roms will always be a little slower due to the fact that Sense eats up ALOT of memory.
[EVO 4G Q&A, Help & Troubleshooting] craigbailey1986:
Have you tried cachecleaner? Usually does the trick when my phone slows down
[EVO 4G Q&A, Help & Troubleshooting] st@matis:
check out my tweaking thread :P You can find the link in my signature
[EVO 4G Q&A, Help & Troubleshooting] threestripebrand:
Resurrect much? :p
[Click Themes and Apps] Vieira:
Hello,

Using stock rom (1.6) on HTC Tattoo and Google Goggles 1.3 I'm experiencing a force close every time I try to take a photograph. Everyone experiencing the same problem? Any idea? (1.2.1 works fine)
[Click Themes and Apps] nikiu:
I have the same issue. Don't know what to do though.
[Click Themes and Apps] Vieira:
Opened Bug Report

I opened a google support topic but I think it won't get fixed as our devices aren't officially supported anyway (because of the lack of camera autofocus).
[Captivate Android Development] existz:
NOTE

This is took from untermensch's thread in the Vibrant forum so I take no credit for this (http://xdaforums.com/showthread.php?t=833423)

I have noticed some of you are having issues after installing a new kernel or rom, when you boot into recovery you now have 3e, which does not allow unsigned zips to be flashed. With this version of 3e it has no-verification check, now allowing you to flash whatever you want.

This zip has

1) 3e recovery modified to disable signature checking

2) disables the forced wipe after installing any update.

Instructions

1)Download and extract the file below

2)Use a terminal emulator or ADB shell and type.. (or you can use Root Explorer or SGSTools to mount system RW)

mount -o rw,remount /dev/block/stl9 /system

3)Use a file manager like Root Explorer and copy the recovery file to /system/bin and replace the one there

4)Now, reboot and you should have a modded 3e recovery with no signature verification

You can either leave the modded 3e recovery or you can now flash CWM via Rom Manager

**Just like anything else, I am not responsible if this bricks your phone, this is fairly simple, follow the guide...Do at your own risk**
[Captivate Android Development] designgears:
Old news, we have CWM now in pretty much everything.

Also you cannot just replace the recovery file... you have to replace the images in sbin or in the zImage its self, otherwise you get errors and cannot do anything.
[Captivate Android Development] existz:
I done the exact method above and works fine for me...

Place extracted recovery file in /system/bin/ , reboot and flash cwm via rom manager, works perfectly fine...the reason I posted was, if you read Hardcores thread, and seen this in other threads, that after flashing his kernel, when they goto recovery they now have 3e (depending on which method when entering recovery)..alot of people have done it the way I posted with no issues...im not trying to argue with you, you by far know more then me, just posting what worked for me and some others
[Captivate Android Development] raymar23:
sounds like a good idea for the people that updated to Rogers froyo that has the 3e recovery. You could just flash a new kernel, but this is definately a good alternative.

Thanks
[Captivate Android Development] designgears:
If you look at Darkyy's rom he has a script that does this.
[Captivate Android Development] kppanic:
Thanks, this works flawlessly on a Rogers Froyo Stock. Now I have CWM working and good to go. The only thing left would be to apply some kind of lagfix.
[Captivate Android Development] skorchir:
Tested and works with Rogers 2.2 Rom. Thanks
[Captivate Android Development] bnevets27:
I also have.

Thanks
[Captivate Android Development] Guinea.Pig:
Works great on Rogers 2.2. Thanks :D
[Captivate Android Development] ziadsa:
I tested it on Galaxy S i9000m bell and it work A+

i do not have to flash cf-boot to make unsigned zip to be installed

thanks a lot for your hard work.

only thing is botton function become different then original 3e

but its working A+
[Captivate Android Development] bentonhall:
I'm a little confused on how the Recovery works..... I have a I897 that I flashed Cognition 2.3b8 to with ROM Manager/CWM and when I chose "reboot into recovery" from ROM Manager from inside Cognition, it worked fine after reloading packages once. A few days ago, I flashed Perception 10.1 with the firebird kernel. After noticing the battery didn't last as long as it used to with Cognition, I did some research and found the SpeedMod kernel K12L. Before I flashed it, I did a backup from ROM Manager which rebooted into CWM with no problems and did the backup with no problem. I have since flashed K12M and K12N. Now I thought I would give Cog 3.0 a shot and wanted to back up my current config with Perception 10.1/SpeedMod K12N. From ROM Manager, I chose to backup, named my backup and the phone rebooted into 3e Recovery and gave the errors you listed above but I don't understand why? Is it because of the I9000 kernel which doesn't make sense since Firebird is a I9000 kernel. Was it from flashing SpeedMod? Also noticed, that only the volume up/down buttons worked, not the power button which is also the select key. Only way out was to 3 button reboot (or pull the battery) which rebooted into CWM and then initiated the ROM Manager backup.

Any ideas why? Also, if I was to ODIN flash JH6 back to the phone, would that restore the Stock 2e Recovery? Sorry for the long post, but I'm still trying to learn this stuff and think you guys are awesome. The captivate would be a crappy phone if it wasn't for you all.
[Captivate Android Development] bentonhall:
I guess if I had read your second post a little closer I would have seen that flashing SpeedMod causes it. I used your fix in the OP and when I tell it to "Reboot into Recovery" from ROM Manager, it boots into what I assume is 3e (Goes by real quick) and shows something about MOVI and verification and then boots into CWM Recovery v2.5.1.2. If I 3 button boot into recovery, it boots into CWM v2.5.1.0 SpeedMod ULFK. Seems to work now but I'm still confused. Thanks again.
[Captivate Android Development] davidis57:
Using sgstools to change mount RW completes its task fine. When I try to copy the new file to /system/bin it does not allow it. The permissions do not change. I tried terminal emulator it doesnt work either. The files stay -r only. I have tried so many times to delete/rename/ or copy over. I just gave up. My system is 2.2 and rooted before you ask.
[Captivate Android Development] existz:
Use a terminal emulator or adb shell and type...

chmod 777 /system/bin/recovery

That should give r/w permission to the file, ...i just tested to verify it and it worked for me. also if you have Root Explorer you can just long press the file and select Permissions and check all the boxes.
[Captivate Android Development] hoekbrwr:
Exact the same thing is happening to me! Beforehand I had flashed CF Root to get Superuser also at the same time when rooting. I Still can boot into recovery with 3BR and come into the speedmod ULFK settings. Speedmod introduces 3e and you need signed packages. You must have 2e for this I assume!? Can anyone tell me what goes wrong?
[Captivate Android Development] Red5:
Im using the Speedmod kernel and it always pissed me off that everytime I wanted to flash somethng via CWM that I had to pull the battery and restart my phone for it to finish because of the 3e 'no signed packages'

I did the steps in the OP and I noticed that I didnt even have a recovery file in system/bin but I put it in there anyway. I rebooted and flashed a different modem just to check and sure enough, it worked. Now I dont have to worry about pulling my battery and having to reboot my phone everytime I want to flash something.

Thanks for this!
[Captivate Android Development] davidis57:
Well the file is moved now. I get reinstall packages in recovery and thats all does. I installed rom manager and have cwm on my sdcard. The phone does not go into cwm recovery. It doesnot give me options to apply install.zip. I have dxjpa and z4root running. This modded recovery does not work. Any ideas?
[Captivate Android Development] existz:
Once you install cwm and reboot back into 3e, select reinstall packages, it will install cwm and then load into it , if it doesn't then the file didn't copy over, make sure it replaces it ok, I've used this quite a few times and it works everytime, and everyone that has posted has not had an issue, so it does work
[Captivate Android Development] davidis57:
It did copy over in fact i deleted the old one and put the new one in its place. It never installs anything and seems to error but its so fast i cant read it.
[Captivate Android Development] existz:
Try starting over, delete the recovery file and also delete the update.zip on the root of the sdcard, then copy the modded recovery over to /system/bin/ , then open rom manager and install cwm again, something could have happened with the update.zip, cause if you are able to get into 3e and select reinstall packages and it actually starts but errors out with the update.zip, then something could possibly be wrong with the update.zip .. it might restart after you select reinstall packages, but it should then load in to cwm, if it doesnt and boots back into android, then go into rom manager and select restart recovery and see if that works
[Captivate Android Development] davidis57:
I deleted recovery and re-run on rom manager. Nothing doing i still got the same thing. I assume you meant to delete install.zip on the sdcard and not the root directory of my phone.
[Captivate Android Development] davidis57:
Btw it doesnt boot into android after reinstalling packages it just reboots ino recovery untill i click reboot. It seems to error wben trying to install but its too fast to read.
[Captivate Android Development] davidis57:
This has been one frustrating week. I even had to restore once trying to odin chainfires root sk i could have 2e recovery to install unsigned zips with cwm. I thought this would be easier but it wont work either.
[Captivate Android Development] existz:
Yea I was meaning delete the update.zip on the root of your sdcard, /sdcard/update.zip , it sounds like something is up with the update.zip, if its trying to reinstall packages, then the modded 3e is working, or it would give verification error...sounds like whatever file its installing is not cwm, cause once it installs, alot of words scroll real fast, then reboots to cwm recovery (green recovery), ...and then thats all it does...from there u can choose "install zip from sdcard" and then flash whatever u want...but the only thing i suggest is making sure the update.zip on the root of your scard is deleted, dont copy over, delete it, and try installing cwm from rom manager, reboot, reinstall packages, then it will boot into cwm recovery...if it doesnt work after triple checking, in rom manager goto the bottom and try installing an older vesion of cwm....something is getting messed up somewhere as I just deleted all my files and installed this again to verify without any issues

EDIT

When I say the root of your sdcard, im meaning the internal sd not your external micro sdcard (just to be clear)
[Captivate Android Development] davidis57:
I have tried all your suggestions it will not work.
[Captivate Android Development] aridoasis:
@davidis57: i had the same problem as you did... but i just followed existz's instructions and got it to work

delete the update.zip in the sdcard root

delete the recovery in system/bin

paste the new recovery in system/bin

open rom manager and reinstall clockwork (even if it says it's already installed)

select 'reboot into recover', and it will take you to 3e recovery

select reinstall packages - this will take you to clockwork

big thanks to existz. works on rogers captivate on stock froyo.
[Captivate Android Development] upNsmokeAllDay:
This worked perfectly. Nice find.
[Captivate Android Development] davidis57:
Thanks for all the help but i could not get it to work. All my goofing around i found another work around. I went to z4build kernal patcher page and selected Froyo.DXJPA and selected cwm to go with it. The site compiled a kernel with cwm in it. All z4builds use 2e recovery. I flashed it with the sgs kernel installer from the market. Low and behold my recovery is now cwm. I also installed the latest z4 file ext. I think it is ext4. Google the site and follow the instruction guides. Now i can install a rom of my choice. Before i forget download the tar file they make for you. Also download any lagfix you want.
[Captivate Android Development] bames:
works like a charm

but for those with RECOVERY on their power menu you can just use it instead of rom manager if you don't want to mess with it.
[Captivate Android Development] sabesh:
Root Explorer Copy/Paste worked for me!! Thx.
[Captivate Android Development] YaGMuR_PreNSi:
Thank you very much because of you figured out

çok teşekkürler senin sayende çözdüm
[Captivate Android Development] Sean09:
Thanks, been trying to get this going for a while now - this method helped!
[Captivate Android Development] javahaxxor:
thanks a lot!
[Captivate Android Development] mxracer101:
Thanks, great work. Made the process easy.
[Captivate Android Development] Bonta768:
Thanks existz. I hit this problem. You saved me.
[Captivate Android Development] perosredo:
I'm stuck on reinstalling clockwork --"An error occurred while downloading your recovery." I do already have the latest version installed.

Rogers 10.11 2.2 updated through KIES; never been modded.

Thoughts? Ideas?

EDIT: And I get "Installation aborted" if I try to skip ahead and mod to simpfinity--which I'm trying to do...

EDIT 2: Solved: used update.zip from this post:

http://xdaforums.com/showpost.php?p=10481996&postcount=410
[Captivate Android Development] rsnt:
worked like a charm, I have a rogers i896 with official froyo 2.2 kies firmware, rooted with superoneclick, NAND image backed up.
[Captivate Android Development] perosredo:
You now bring to my attention what I overlooked in all my frustration to get this working---I didn't do a nand backup. How would it be possible for me to go back to stock 2.2?
[Captivate Android Development] max_82:
I just want to make sure because I'm a noob here. If I've replaced the recovery file at \system\bin can I booting my captivate normally? I mean I still can replace again with my previous recovery file. Thanks.
[Captivate Android Development] mbc663:
after i reinstall clockwork and hit reboot into recovery, im stuck at my splash screen.....for 5 mins now....nothing happening.

k, somehow it got into recovery after several attempts to get into download mode. it asked me if i wanted to overwrite the old config with the new detected one, which i said yes to (nervous as could be because i dont see this step listed anywhere) and it is now backing up my nand it appears...

now restoring...

i'd love to know how i screwed this up. after changing the config it asked me to do it again, when i said no it took me to a clean version of the rom im using, without apps. trying to restore now and stuck again at splash screen. wtf?

i dunno if im gonna do this again. might just get used to pulling the battery. IF I EVER GET OUT OF THIS MESS. CANT EVEN BOOT UP

After 5 restores I finally found one that worked for my rom. I'm not going to try again. I'll continue to pull the batt
[Captivate Android Development] apparition:
I couldn't get this file working at all. everytime i deleted the original recovery with rootexplorer, it would reappear again (then not allowing me to flash CWM due to the verification issue).

i managed to get 3e mod on with the 3e installer script in the vibrant forums though. worked like a charm. automatically temp-roots too so you can replace 'recovery' then flash CWM straight from 2.2 stock. try that if you guys are having problems.
[Captivate Android Development] KonaZXIII:
Easier than I thought with Root Explorer. This saved KB1 for me.

Thanks!
[Captivate Android Development] qynt:
Worked for me. It was a pain having to remove the battery every time. Thanks!
[Captivate Android Development] JRd1st:
This worked PERFECTLY on my Captivate w/Official KB1! Thanks man!

I used Root Explorer and copied and pasted the modded recovery over the original one after setting system/bin to R/W. I saved a copy of the original, of course. lol

I have to say, Root Explorer is sooooo worth the small price.

Anyway, thanks for your work, dude! :D

BTW, you will probably need to do Reinstall Backups twice, the first time, to flash CW Recovery. I did. :)
[Captivate Android Development] TRusselo:
this OLD thread needs to be stickied! Too many noobs are having this problem now and not finding this thread
[Captivate Android Development] edtonn:
Worked perfectly

@existz, worked perfectly, and now I have CWM recovery installed. Rooted official KB1
[Captivate Android Development] edtonn:
+1, 2nd a sticky! Would be very helpful
[Captivate Android Development] Caliesv:
Worked like a charm!! thanx for the easy to do break down man!
[Captivate Android Development] locsplitter:
Awesome. Worked perfectly.

Cheers
[Captivate Android Development] Sanctus Peregrinus:
Worked like a charm. :D
[Captivate Android Development] illeont:
How do i get into system/bin folder? It's nowhere.
[Captivate Android Development] KayvinM:
You need to be rooted and have root explorer or similar app. You can also use the adb commands. Heres a link to a tutorial in case you need it.

http://www.youtube.com/watch?v=y6K1XLmafPc
[Captivate Android Development] TRusselo:
follow the steps in bold
[Captivate Android Development] elalexdesiempre:
THANK YOU!!

This recovery file worked for me. I have the official samsung froyo which i guess comes with 3e. I used abd to push and then abd shell to copy the file to system/bin.
[Captivate Android Development] buntoo:
Does it work with Galaxy S i9000?
[Captivate Android Development] Seanbest:
Worked great for me as well. Used Terminal Emulator to copy file and rebooted.
[Captivate Android Development] apparition:
Using the installer in untermensch 's thread (3e_recovery_installer.zip) has worked for me without any terminal entering. Probably the easiest way to get 3e mod recovery.
[Captivate Android Development] brianandreneedavis:
Ok, so before I read your note about not simply replacing the 3e recovery file...I replaced it so now I have those errors you were talking about. Is there any way to get the original 3e recovery file or how can i correct my mistake. I cannot root my phone and wifi and internet are not working. Please help!
[Captivate Android Development] KayvinM:
This is the original recovery file. Just unzip it and drop it in. Hope that helps.
[Captivate Android Development] Dvalin21:
I have a dilema, I'm trying to root my Vibrant (3G) and superoneclick, universal root, and root me app does not work. So I'm trying to do the "update.zip" root, but I get the verification error. With that said, how do I do this without having to connect to my computer or having root access?
[Captivate Android Development] javahaxxor:
You can only do what T-Mobile wants you to do without root. So root it first, SuperOneClick 1.7 works, or you can flash a CF-Root kernel with Odin. When that's done, you can replace the 3e recovery file with the fixed one.
[Captivate Android Development] AReynante:
Worked perfectly for me, my new captivate doesn't work through the cable, but I used an ftp client, and got it transfered fine, and now I can boot into cwr :) thank you
[Captivate Android Development] Dvalin21:
Ok, so I need some help here, When you say move the "key" files are you talking about the .dll files im suppose to move o the /efs folder? I know there is only one recovery. Just a lil more help please, thanks
[Captivate Android Development] existz:
Just download and extract the file in the OP, then use a file explorer with root, such as Root Explorer, and copy the "recovery" file that you extracted to /system/bin/ ..
[Captivate Android Development] michaelg117:
Will this work with the vibrant

Sent From The Brain Of The Magic Man Through His Nerves, Into His Muscles, To His Fingers And Onto The Magical Screen Of The Vibrant.
[Captivate Android Development] WandererTJ:
Thanks man, it worked. I can finally make a Nandroid Backup. While it's a little to late for me to find out what my unlock code originally was oh well, at least I have a backup / can make backups.

I need to add though, that in using terminal the code is:

su

mount -o rw,remount /dev/block/stl9 /system

and as it comes to the file replacement (using Root Explorer), I had it on my sd card, long selected the file and chose "move", went to the directory and deleted the original file, then pasted the new one.

I then Flashed Clockwork Recovery and chose Reboot into recovery when the DL was done. After that (for those who don't know) You have to choose the Reinstall Packages (or w/e it's called, sorry) option twice in order to get into the green CWR menu.

After that, you can make Nand Backups at your pleasure.

Again, thanks for this. Link has been added to my sig.
[Captivate Android Development] Pudrow:
Terminal Emulator

When I try to type the code into my terminal emulator it says

"mount: Operation not permitted"

Can I continue with the steps or does that have to be done first?

All I'm trying to do is root my phone. I've rooted a couple different android phones but this is a new Samsung Captivate with 2.2 froyo stock and it is blocking everything I've tried
[Captivate Android Development] sthacher:
Same boat with a friends new captivate 2.2 out of the box with 3e notnothing seems to be working to root this dang thing.
[Captivate Android Development] TRusselo:
are you rooted? you have to be rooted to access root areas!!

use SuperOneClick Root 1.8

the zip method for rooting doesnt work with 3e! it is OLD!!
[Captivate Android Development] Pudrow:
No I'm not rooted that is what I'm trying to attain. Somehow ATT has figured out a way to block it.

Super one click was the first thing I tried and it kept failing during busybox.

Nothing is working on this stupid captivate :p
[Captivate Android Development] goodolsen:
You had USB debugging turned on correct? Busybox won't install without that turned on.
[Captivate Android Development] Pudrow:
Yeah debugging was turned on. So I figure if I can get the 3e gone I can just root my phone with update.zip but theres an error in the code when I try to use it in terminal emulator
[Captivate Android Development] 4-2ndtwin:
View attachment SuperOneClickv1.6.5-ShortFuse2.zip This was the way I got rooted when I had my Captivate updated through Kies to the official 2.2.

Its just an older version, but for some reason it was the only one that would work for me. Give it a try...

Hope this works for you.