Basically, make sure you've got a microSD card with about 650mb (or more if you have a lot of apps installed, check via Settings -> SD Card menu) free on it for the ext4 conversion before you even start.
Download the ext4 version of the kernel from;
http://android.modaco.com/content/samsung-galaxy-tab-tab-modaco-com/330378/26-jan-r3-modaco-custom-kernel-for-the-samsung-galaxy-tab/
(You _might_ need an account on the site first, not sure)
Install the Samsung Kies software so you've got the USB drivers installed (or install just the drivers from:
http://downloadcenter.samsung.com/content/SW/201010/20101026044755031/SAMSUNG_USB_Driver_for_Mobile_Phones_v1.3.350.0.exe
Turn your tab off, turn it back on holding the DOWN volume button until you get the big yellow triangle.
Plug it into your PC and run Odin. Make sure that one of the leftmost boxes lights up yellow and says "COM" in it (along with a number). If not, then it hasn't picked up the tab, try rebooting the PC and/or trying another USB port.
Click the big "PDA" button and select the "p1000-mck-r3-ext4-cwm.tar" file that you downloaded (do NOT extract the archive!)
Then press the "Start" button and cross your fingers.
If the tab seems to hang, give it 5 minutes before you hold the power button down and then turn it back on again. It should sit there for several minutes and perform the conversion.
Once you're done and up & running, you can save the full firmware/ROM to the MicroSD card, boot into recovery by turning the tab on hold the UP volume button, then using the "Select ZIP from sdcard" option to flash the firmware. This will WIPE all custom applications and settings you have installed! I'd recommend doing a "wipe data/cache" before flashing this just in case though.
The full MCR firmware is available from:
http://android.modaco.com/content/samsung-galaxy-tab-tab-modaco-com/331479/04-feb-r1-modaco-custom-rom-for-the-samsung-galaxy-tab-with-online-kitchen/
There are also alternative firmware's (e.g. Overcome, Rotohammer) on this forum - they're all currently based on the same official JMI firmware with various tweaks. The MCR kernel seems to be the easiest way to start.
Full credit goes to Paul @ MoDaCo for releasing the kernel in the first place.
I typed most of this out for someone, figured I'd post it here as well in case it's useful to someone.
WARNING: Check the integrity of anything download from the MoDaCo server(s) before flashing as their server(s) frequently seem to have issues completing downloads.
knightnz said:
Basically, make sure you've got a microSD card with about 500mb or more free on it for the ext4 conversion before you even start.
Click to expand...
Click to collapse
Make sure you have sufficient space. In my case I needed more than 500MB. My system was corrupted because it tried to backup the existing system onto the microSD and I only had 639MB free, which was insufficient for me. Then when my system rebooted, I kept on getting force closes from Nook and Titanium Backup and some other apps.
nice work!
Hi knightnz,
Sorry for this noob question.
Does this means I can do it on my stock rom without installing anything or customizing my tab?
Is clockworkmod recovery required to execute this conversion?
Thanks.
Jasper
Sent from my GT-P1000 using XDA App
jasperlaguerta said:
Does this means I can do it on my stock rom without installing anything or customizing my tab?
Is clockworkmod recovery required to execute this conversion?
Click to expand...
Click to collapse
You have to flash a new kernel, which will also flash ClockworkMod Recovery onto your device, so the answer to your first question is no, you can't do this without customising your Tab (new kernel, new recovery!), and your second question, yes you need ClockworkMod!
Regards,
Dave
Yup, on the Galaxy Tab the recovery gets packaged in with the kernel installation, so if you flash a zImage, you're probably replacing the recovery as well. (I'm sure it could be omitted, but so far it seems this hasn't been the case).
At the moment all SGT recovery's are based on ClockWorkMod (this includes the MCR kernel version).
As for "stock rom", well I'd class a complete filesystem conversion as definite customising. If you _just_ replace the kernel and do the ext4 conversion though and don't worry about replacing the main firmware, then you'll retain your existing system exactly as it was, it'll be snappier though, and you'll then have access to the CWM recovery should you ever need it.
I had difficulties flashing this as the Modaco server kept on stopping the download when incomplete. I had an hour of scratching my head when I saw that the download was 4 1/2 Mb when it should be 6.66.
It took me about 6 tries to get the full file and was sweating when I saw the following screen:
phone --- ! --- Computer
Keep an eye out for this chaps...
is there a way of going back to RFS from EXT4?
(just in case)
asenduk said:
is there a way of going back to RFS from EXT4?
(just in case)
Click to expand...
Click to collapse
Yes, I already did that once. Go into the development section and find the Roto JME rom, get the full rom, the p1_hidden.pit, and a modem of your choice, and follow Roto's instructions to the letter, and you will have rfs, and your CWM3 will be gone.
I'm used to the speed increase now. Perf drop if i went back.
Ext4 is stable enough
Sent from my GT-P1000 using Tapatalk
rob_h said:
I had difficulties flashing this as the Modaco server kept on stopping the download when incomplete. I had an hour of scratching my head when I saw that the download was 4 1/2 Mb when it should be 6.66.
It took me about 6 tries to get the full file and was sweating when I saw the following screen:
phone --- ! --- Computer
Keep an eye out for this chaps...
Click to expand...
Click to collapse
Yeah, their "load balancing" server doesn't seem to have very good balance by the look of it, downloads fall over frequently.
I have a copy here http:/ /bit.ly/myroms
Sent from my GT-P1000 using Tapatalk
Setting Up Data2Ext with RA 1.7 RecoveryI made this guide for my own personal future use and decided to share it with the community. I take no credit whatsoever for this information or the files used to install this mod on your phone. Credit for the guide goes to Laie1472 who spent several hours walking me through the process in the absence of good instructions for our device. If you don’t know what this mod does or could potentially do to/for your phone, don’t install it. Please read this entire guide before flashing or asking questions which may already have been answered. As the title states this is for users who have RA 1.7 Recovery installed. If you don’t have RA 1.7 recovery, you can find it here: http://forum.xda-developers.com/showpost.php?p=10531580&postcount=5
Now on with the guide:
Step 1. Back up your sd card to your computer as this process will format and partition your sd card.
Step 2. Reboot into recovery and select partition sd (this will wipe everything on your card). You will be given 3 prompts….swap, ext. 2, & Fat 32. Partition as follows:
Swap=0
Ext2=1024
Fat32=remainder
Step 3. Since the above step erased everything on your sd card, now would be a good time to do a nandroid backup.
Step 4. Download & place on the root of your sd, the data2ext2-v7.zip attached to this thread, but DO NOT FLASH IT YET.
Step 5. Decide whether or not you’re going to use your current rom or install a new rom (easier). If you’re going to use your current, you’re going to want to uninstall all of your apps & theme in order to utilize the additional memory you’ll be freeing up on your phone. If you’re going to use a new rom download it & the appropriate gapps and move them to the root of your sd.
Step 6. Boot into recovery, wipe, and flash your new rom & gapps. Boot into your rom and sign in, but don’t install any of your apps.
Step 7. Reboot back into recovery and flash the data2ext2-v7.zip
Step 8. Boot into your rom & open Terminal Emulator.
Type the following commands minus the ( )
su
mount|egrep mmcblk0p2
(this should return nothing but a #)
Now type:
mke2fs -m0 -b4096 /dev/block/mmcblk0p2
(let the scripts run….when they finish you’ll type the next line)
data2ext --enable
(You should now be prompted to reboot, so type)
Reboot
Step 9. Once you’re rebooted go to settings/storage. You should now see .94 GB or so of available space… Congratulations you’re almost done.
Step 10. The performance boost. Open Terminal Emulator again and type:
su
busybox mount -o remount,noatime,nodiratime, /mnt/asec/ext/ext2 /data
reboot
Step 11. You’re finished, but before you re-install your apps read the You Should Know section of this guide.
You Should Know:Now say you want to make a backup of your rom and you have data2ext enabled
do this
Boot into recovery and choose backup and restore. Then choose
create nandroid+ext back up
after it's done always flash the data2ext zip and reboot.
Say aosp/cm/whoever releases an updated rom and you want to update your rom and keep all your apps and theme and settings
Do this
Boot into recovery and make a nand+ext back up by following the steps above. "you don't have to if you already have good backup''
Now wipe cache and davlik-cache and flash then flash the rom update then flash the data2ext zip and reboot
Say you want to flash a new kernel with data2ext enabled
Do this
Boot into recovery wipe cache and davlik-cache. Then flash the kernel then flash the data2ext zip and reboot.
If you ever need to wipe cache or davlik-cache always flash the data2ext zip right after then reboot
PLEASE NEVER WIPE THE SD EXT unless your redoing the whole mod or just want to start fresh
AGAIN NEVER WIPE THE SD EXT
this will more that likely result in a boot loop and make all your once good nands useless
and you might have to reflash your recovery
Say you want to flash a sense rom to update prl/profile.
Do this
Boot into recovery wipe data,cache and davlik cache
then flash sense rom and update.
Then reboot back into recovery wipe data,cache and davlik-cache then choose which nand you want to restore after it's done restoring flash the data2ext zip and reboot
Always flash the data2ext zip after doing a nand restore.
Also with this mod it's not recommended to let your battery die or do a battery pull. If you do you might have to reflash your recovery and redo the whole mod over.
Also only shut down you phone with the rom options
apps like quick shutdown and hot reboot etc will not play nice with this mod. So only use the roms power options to shut down.
If you ever want to disable this mod, open Terminal Emulator and type:
su
data2ext --disable
Nice, I should add this to my links thread, you think?
il Duce said:
Nice, I should add this to my links thread, you think?
Click to expand...
Click to collapse
Go for it. Maybe it'll help someone besides me.
Sent from my HERO200 using XDA App
Need some help, I tried flashing data2ext2-v7.zip and this is what I get...
Code:
Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:No signature (10 files)
E:Verification failed
Installation aborted.
This was using the file in the OP with RA 1.7
Everything went fine, partitioned, wiped, fresh install of rom and gapps, rebooted, signed in, rebooted to recovery and then no go trying to flash data2ext
Any help would be great.
Try flashing this one. Let me know when you get it. Thanks.
Link sent via pm.
#Root/Hack-Mod_Always*
laie1472 said:
Try flashing this one. Let me know when you get it. Thanks.
Link sent via pm.
#Root/Hack-Mod_Always*
Click to expand...
Click to collapse
Thanks a bunch. Got it and worked perfect. Just have to do the performance boost (What does that do really?) then going to look at the S-Off thing. I have put that off for a long time but might as well go for it.
Thanks to both of you for the nice tutorial here and the help.
Pm sent. And no prob glad you got it worked out. Also recommend s-off via darch's method.
#Root/Hack-Mod_Always*
Installed and so far so good. Hopefully this works much better then apps2sd did. That made me just about want to smash my phone it was lagging so bad. lol
Hippie459MN said:
Thanks a bunch. Got it and worked perfect. Just have to do the performance boost (What does that do really?) then going to look at the S-Off thing. I have put that off for a long time but might as well go for it.
Thanks to both of you for the nice tutorial here and the help.
Click to expand...
Click to collapse
OP has been updated with the SIGNED version of Data2ext.zip. Sorry Hippie, I uploaded the unsigned version to the guide. Thanks Laie1472 for hooking him up, while I was asleep.
I'm really considering this mod right now but have a concern with the battery pull portion of it since I have a 14-month old daughter that sometimes thinks the phone is a toy. lol
Question: If I disable the mod will it automatically move all /data back onto the phone? Assuming of course I have enough internal memory for it to be moved over, will it transfer automatically?
Really good write-up, thanks for taking the time to do so.
hockeyfamily737 said:
OP has been updated with the SIGNED version of Data2ext.zip. Sorry Hippie, I uploaded the unsigned version to the guide. Thanks Laie1472 for hooking him up, while I was asleep.
Click to expand...
Click to collapse
No problem at all. Your guide worked perfect and turns out it was super easy.
I also am happy to be back RA Recovery. Was using Clockwork for a short while and while its nice, RA is much better I think. Thats just me though.
Got me a **** ton of space now and phone is moving right along again. Thanks again guys.
srkmagnus said:
I'm really considering this mod right now but have a concern with the battery pull portion of it since I have a 14-month old daughter that sometimes thinks the phone is a toy. lol
Question: If I disable the mod will it automatically move all /data back onto the phone? Assuming of course I have enough internal memory for it to be moved over, will it transfer automatically?
Really good write-up, thanks for taking the time to do so.
Click to expand...
Click to collapse
I've been using this mod for a couple of weeks now and have had to do a couple of battery pulls with no negative effects on my phone. There are obviously things that can go wrong, but no guarantees they will. I've enabled it, disabled it, gone back to a sense rom, updated my Orlando & gone back without trouble....but you wont know for sure how your phone responds until you try it.
Sent from my HERO200 using XDA App
Damn auto-correct......updated my PRL....not Orlando.
Sent from my HERO200 using XDA App
Thanks, Hockey. I'm going to give it a go and see how it goes for me. I know there are always risk and not all phones/experiences will be the same. Let's hope for the best
srkmagnus said:
Thanks, Hockey. I'm going to give it a go and see how it goes for me. I know there are always risk and not all phones/experiences will be the same. Let's hope for the best
Click to expand...
Click to collapse
No problem, just back everything up to your pc and do a nand backup before you start and you have nothing to lose and about 3/4 gb of storage to gain
At step 8 I get "/dev/block/mmcblk0p2 is apparently in use by the system; will not make a filesystem here!" when I input mke2fs -m0 -b4096 /dev/block/mmcblk0p2. The only deviation I made is I had to get a TE from the market since the one that comes with jaybob's rom won't accept numerical input.
Tibson said:
At step 8 I get "/dev/block/mmcblk0p2 is apparently in use by the system; will not make a filesystem here!" when I input mke2fs -m0 -b4096 /dev/block/mmcblk0p2. The only deviation I made is I had to get a TE from the market since the one that comes with jaybob's rom won't accept numerical input.
Click to expand...
Click to collapse
I've never run Jaybob's rom, so I'm not sure if this is a rom specific thing, because I have used it on Deck's Gingerbread, Aosp, & CM7. What did you get when you typed:
su
mount|egrep mmcblk0p2
That should have returned only: #
Also which terminal emulator did you get from the market (I use Android Terminal Emulator by Jack Palevich) and were you using the default gingerbread keyboard (as opposed to swype, slide it, etc.)?
Jo
hockeyfamily737 said:
I've never run Jaybob's rom, so I'm not sure if this is a rom specific thing, because I have used it on Deck's Gingerbread, Aosp, & CM7. What did you get when you typed:
su
mount|egrep mmcblk0p2
That should have returned only: #
Also which terminal emulator did you get from the market (I use Android Terminal Emulator by Jack Palevich) and were you using the default gingerbread keyboard (as opposed to swype, slide it, etc.)?
Click to expand...
Click to collapse
I was using the default GB keyboard, and I got the same TE from the market. When I typed mount|egrep mmcblk0p2 I get "/dev/block/mmcblk0p2 on /sd-ext type ext3 (rw,noatime,nodiratime,barrier=1,nodelalloc,data=writeback)" then it goes back to just #. I was burned out last night, now I can think again. Seems like maybe the ext partition is ext3 when it should be ext2? I'm using RA 1.7 and I followed the directions for partitioning the sdcard.
About a year ago I used apps to SD for a short while then stopped, is it possible that the ext part from then is still there and conflicting with the new partition from RA 1.7? I would have thought it would be wiped during the new partitioning. The only ext visible from TE is the new one, but that's all I can come up with.
I installed the setup last night without a hitch. Using Kushdeck's latest ROM and so far so good. Re-installed all my apps from Titanium Backup without a problem and everything going smooth. Once again, thanks for the detailed how-to and informative comments to update the ROM
(I wasn't really sure if this might fit into "Development", so I put it here, maybe a mod will move it, if it's a dev topic )
Anyways, here we go, I DUALBOOTED two different, independant ROMs on the S2
Video of dualboot in action: http://www.youtube.com/watch?v=l9-V_6Ua_D0
** THIS IS NOT (YET) COMPATIBLE **
** WITH ICS (ANDROID 4.0.x) ROMS! **
-- this goes for custom ROMs as well as stock ROMs --
Icey Sammich compatibility will be added once Sammy released their ICS kernel sources.
!!! There now is an app for more convinient and easy setup of the dualboot !!!
(04.11.2011) DualBoot setup app v2.00: http://forum.xda-developers.com/showpost.php?p=19049047&postcount=94
(12.12.2011) App has been updated to 2.51, lot's of good new stuff! >> Free Version -- Donate Version <<
Click to expand...
Click to collapse
First off:
This is only a little experiment I did like "c'mon, has to be possible" - this is NOT (at least yet) tweaked for usability and anything the like, just a humble experiment.
That said, don't flame me if things are rather complexicated to do this ATM.
Maybe I'll come up with a more userfriendly way of setting this up, maybe someone else does, maybe no one does.
Also now that I found a base on what to do, there might be different ways (more easy ones maybe) to set this up, I'll keep toying around with it.
But let's cut to the chase, shall we
So, how was this set up? I'll give a brief rundown of what I did:
I edited a few .rc files in the initramfs of the kernel to make it actually perform a full boot when recovery mode was triggered and to fire up recovery mode when in battery-charging mode.
I also edited a few mounts in the boot .rc for the 2nd OS (in "recovery" mode) to use different partitions for /system and /data, so that we'd end up with really independant installs.
What partitions did I missuse for that:
partition 12 (mostly unused, only when installing a stock ROM AFAIK) for /system - that's a neat choice IMO as p12 is 512MB in size, just as p9 where /system usually sits on
partition 7 (which is usually /cache) for /data
gives us only 100MB of user data space, but for now that's OK, as said, it's only an experiment on how such a thing could be done.
with the original partition for /cache "gone", I mounted a tmpfs for it.
So the OS still has a usable /cache
Then I set up the two OSes:
(dualboot kernel not yet flashed)
Launchprep part 1:
I made a CWM backup of my normal installation I was running (stock XXKG6 at the time).
I installed DevNull-Test AOSP as to it's instructions
Some su'ed voodoo via a terminal while having the 2nd OS (the DevNull AOSP one, in this case) installed - best done in recovery mode via ADB:
rm -Rf /cache/*
cp -Rp /data/* /cache/
dd if=/dev/block/mmcblk0p9 of=/dev/block/mmcblk0p12 bs=4096
That did "set up" the 2nd OS to where it's supposed to go.
Launchprep part 2:
Then, "advanced restore" of the backup made a few minutes earlier:
- boot
- system
- data
Reboot
At this point OS #1 is running again and OS #2 is sitting in hiding, prepared to roll - so, let's roll:
Flashed the modified "dualboot kernel" (via an App or Odin or magic, doesn't matter).
---> DONE <---
reached the point to where everything works as shown in the video.
As said above already, yes it needs some manual work to set it up, yes there's a lot of things that might not work, yes there are other/better ways to set it up.
It's only a humble experiment - lot's of space for improvement.
Maybe you like it - for those who do, I wanted to share this
Attached to this post you find the modified kernel I used, it's based on my v1.20 custom kernel (see sig) but with the above mentioned changes.
I've seen the video m8, this is totally different approach, ur giving this device a new dimension. love u "in a straight way" hahaa
there currently an app called Bootmanager which also handle up to quadruple booting. But sadly currently only support HTC phones.
http://www.appbrain.com/app/bootmanager/com.drx2.bootmanager
well, one can hope!
Thanks OP this is an awesome concept! Very happy to see you posted it with a video! and nice boot animation!
sunwee said:
there currently an app called Bootmanager which also handle up to quadruple booting. But sadly currently only support HTC phones.
Click to expand...
Click to collapse
Yeah, that's the thing.... that app is HTC only.... but we have Samsung S-II and want dualboot as well.
I'm already brainstorming on how to enhance the actual usability of this, i.e. flashing a 2nd OS directely to it's place instead of first installing it to the main system partition. But there is problems when /data is not mounted to the original partition, at least stock doesn't like it on initial boot.... well, well....
That is great. Going to use this for sure. This should be in development for sure.
Congratulations already.
Sent from my GT-I9100 using Tapatalk
This is impressive bro sure will use it
but i want to ask one thing
SD card needed for this or not ?
That would be really cool (and definitely should goes to original development). Does it work with CM7/MIUI + custom rom?
vikas776 said:
SD card needed for this or not ?
Click to expand...
Click to collapse
No, so far this completely works with all internal storage.
But I have a few ideas I have yet to try to get mounted from other places - like images in /sdcard for example (I *so* hope that'll work.... )
Hi
Does this kernel include any of the Hellcat kernel tweaks or are they work in progress.
Sent from my GT-I9100 using Tapatalk
Tricky103 said:
Does this kernel include any of the Hellcat kernel tweaks or are they work in progress.
Click to expand...
Click to collapse
I made this build based on my v1.20 custom kernel, so it has everthing that one has - plus the touchfix already
exactly what i was hoping for.
great job - pls continue your work
Hi i tried this with instanity rom last night. When I use the three buttons to boot it just sits there not booting. My guess is the kernel is not compatible. Unless I made a mistake somewhere.
Sent from my GT-I9100 using Tapatalk
Hm, yah, might be that the kernel isn't fully compatible with that ROM, what kernel does the ROM usually use?
Did you boot it up fully at least once before copying /data to /cache ?
Yes I did fully boot up. But his kernel didn't have advanced activated in recovery so I flashed your kernel and moved the cache okay. But it said /data not found when I ran the 2nd command line.
I will flash aosp later. I like that rom.
I am not sure what kernel nitr8 uses. I think it is his own, Insane.tar would you like it to see if they can work together.
Sent from my GT-I9100 using Tapatalk
Tricky103 said:
But it said /data not found when I ran the 2nd command line.
Click to expand...
Click to collapse
Hm, yeah, that sounds like something didn't work.... make sure you run those commands as root, i.e. "su" as very first command (I'll add that to the first post).
Give me a direct link to the ROM and I'll try it.
Make take a few days though as I'm away from my computer a lot because of work the next two days, but I'll try once time permits.
Well yeah, and this still is in highly experimental stage, if I (or someone else) should ever get this to more stable and reliable state, I'll make an easy to use installer/setup tool
But I got a few other ideas on setting it up I have to try first....
http://goo.gl/2uZCh
This is the complete rom. Only 47mb. I thought you would like the whole rom
Tricky103 said:
Hi
Does this kernel include any of the Hellcat kernel tweaks or are they work in progress.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
May be someday WINDOWS Mo 7 and Android on our sweet beast
Hi
I tried again with Aosp Dev-null. I still get this error "cp: can't stat '/data/*': No such file or directory "
after running this command line " cp -Rp /data/* /cache/ "
Any Ideas ?
It still doesn't boot if I press 3 button it brings up the boot logo and then black screens until it boots to the 1st partition.
Thanks for the link, will download and try as soon as time permits.
Also, try this command sequence, I got an idea what the issue maybe might be, give it a shot:
Code:
su
rm -Rf /cache/*
busybox cp -Rp /data/* /cache/
dd if=/dev/block/mmcblk0p9 of=/dev/block/mmcblk0p12 bs=4096
(use "busybox cp" instead of plain "cp", maybe it helps)
And some update on my ongoing thoughts for those interested:
- got an idea on how to make a more easy to use App for prepping and setting up the dualboot environment
- managed to do a neat thing I didn't really think it would work: issued a "mount" command and the OS thought it was mounting a partition of the internal flash (/dev/block/mmcblk0p12 in this test, but was testing for later on actually doing it with p9 - you might see where I'm headed here ) but instead of the partition it actually mounted from an .img file! (loopback)
i.e. "mount /dev/block/mmcblk0p12 /somedir" actually mounted "/somepath/someimage.img" to "/somedir" instead of the partition from /dev/block/... (you just gotta love Linux and it's flexible way of handling things....)
NOW, imagine /dev/block/mmcblk0p9 (the partition carrying the system) and p10 (data) being (kinda) transparently mounted from an IMAGE FILE
I "only" have to find a way to sneak this in before init starts mounting stuff.
If there's a way to do THAT.... unlimited multiboot from OS images, anyone?
(so far this is kinda dreaming, but would be cool to get it working )
The first thing I should say here, is thank you to every Dev, every tester and every member that helped me along the way, from the guys in IRC #Ubuntu that helped me set up adb on my Linux drive to the guys on #htc-evo that walked me through rooting an hour after I first took this phone out of the box to all the other members of XDA and SDX that have been so instrumental in helping me learn all of this. Especially the people that have run into issues and the people that have offered up solutions. If other people didn't make mistakes, I never would have know half of what I do.
ULTIMATE GUIDE TO EVERYTING EVO 4G
In the year that I’ve been on this forum, I’ve come to learn a lot more than I could have ever imagined. I’ve tried to pass that knowledge on, in various threads, and tried to help as many people as I can. I know there are a lot of guides out there, but I decided to write what I’ll call “HipKat’s Ultimate Guide To Everything Evo 4G.” For ease, I’ve added links to as many things I can at the bottom of this.
The most important thing I can tell you is to fully read as much as you can before you attempt anything. The developers are really good at listing how to apply their mods, Flash their ROMS and listing what does and what doesn’t work.
FROM THE BEGINNING
So you have your Evo, freshly rooted, and you want to know where to go next. Well, here are some important things you need to do first. I’m assuming that you’ve already installed the HTC-EVO drivers via HTC Sync.
In the rooting process, you most likely ended up with Clockwork Mod Recovery. The first thing you’ll want to do is update that to a better recovery. Clockward Mod, or CWM is not a good recovery for the Evo. More on Recoveries below.
Download the file from the link provided below. You’ll have to rename the file so it reads PC36IMG.zip
Be sure that you are not adding a second .zip to the file name (PC36IMG.zip.zip).
Place the file on the root of your SD Card, meaning not in any folders, but on the card itself. Power down the phone and then reboot by holding Volume Down and Power at the same time, until the bootloader, or Hboot, comes up. After a few seconds, Hboot will scan your phone, find the PC36IMG.zip and ask you if you want to update. Select yes with the Volume Button, and when it’s finished, it will ask if you want to reboot. Select no, and then select Recovery. If it loads correctly, you can Reboot System.
Once your phone is fully booted, go to Market. Hit Menu>My Apps and see if anything on your phone can be updated.
As long as you’re in the Market, download some apps that you will need in certain instances, as I’ll explain later.
Astro File Manager, Titanium Backup, MSL Reader, Terminal Emulator & GPS Status & Toolbox.
*Note: You have an expensive device in your hands. Don’t afraid to buy some of the more important apps, and Titanium Backup is one I suggest paying for. I’ll be listing some of the more important Apps you’ll want, and some are not free. If you pay for Titanium Backup, make sure you keep the text file with the license number on your SD Card/Root
Once you’re done there, back out to your home screen, hit Menu>Settings, scroll down to Updates and quickly update your PRL and Your Profile. I do this before every ROM that I flash.
Open MSL Reader and get your MSL and write it down, then put it somewhere that you can always refer to it. You’ll need it for various things, like resetting your GPS Data.
Open Titanium Backup and hit Menu>Batch> Backup All user Apps and Data. Only select the apps that you may have downloaded. Never any System, Google or HTC Apps. It’s pretty simple to tell. They’ll be the ones in White Text.
The ONLY other apps I backup are my Alarms and my Voice Mail. You’ll need this if you use an AOSP ROM to restore your Voice Mail Data, which I’ll go into further below.
After those have completed, and since you have a Stock ROM without the extended Reboot Options, power down. Then repeat the steps to get to the Hboot, but this time, after the scan, since the PC36IMG.zip is still on your SD Card, select no, and then go to Recovery.
*Note: I usually keep my USB Cord connected to my Computer during any of this. You’ll see why below.
TWRP
The best one to use on the evo is 2.2.2.0. This is a true touch recovery unlike the ra style. It does wipe everything correctly and has a decent user interface. Lets start with the down side of 2.2.2.0 which is it takes forever to boot up, there is no option to wipe the boot partition (but that has never been an issue for me), and there is no autoreboot option. Now to the goodies. You have the option to flash upto 10 zips at once, there is a file manager program which will allows you to move, rename, copy, delete files from all directories including the root. You are able to name your backups and for people like me who flash and nand and restore on a daily basis who can forget what backups are what. Yes you can rename in ra but only after you boot back into the os. Also twrp creates a md5 for each partition. While in the backup screen you can see the size of the data in each partition. So that way you are not trying to backup useless partitions like .android or sdext when you have nothing on them. Also there is a terminal emulation option for the advanced users. While restoring or backing up it will show you how long each operation takes.
Now 2.3+ twrp. While there are a few new options in this one it is not worth the trouble to use it. Almost all the code has been rewrote to c++ but also it is based on aosp jellybean. What that means for the end user is headache after headache. Most of your zips will not flash without being reworked. You have to change the update binary and rewrite the update script.
Thanks to jlmancuso for that write up
Smelkus' Amon Ra Style Recovery
I have to give it up to Smelkus for this recovery. It's incredible, really. This makes wiping very easy. Before flashing a New ROM, wipe Caches, Factory Reset and Multi Wipe, and you're all set! It's just that easy. Plus it will work with existing Nandroids made with Amon Ra 2.3.3. This is the Recovery to use! Use the descriptions below for Amon Ra to see what everything does on Smelkus Recovery.
Smelkus Amon Ra-Supersonic-4.3
Welcome to Amon Ra
Now that you’re in Recovery, you’ll see there are a lot of options. While you may use most of them during your time with the Evo, I’m going to key on just a few.
USB-MS Toggle – This will connect your phone to your computer so you can edit/delete/modify files on your SD Card.
Backup/Restore – This is where you’ll create and restore your Nandriods. I’ll go into further depth about Nandroids below.
Flash Zip From SD Card – Obviously, this is where you flash your ROMs and Mods.
Wipe – The most important thing you can do in Amon Ra, and I will detail how to properly wipe your phone below.
Partition SD Card – With the size of the newer ROMS coming out, you will want to do this. It’s easy and will save you a ton of room on your internal memory.
Scroll down to Backup/Restore. You’re going to create your first and most important Nandroid Backup. Click here, and then click on the Backup function. I believe that if you’re making a backup, then you want it to be an exact image of your current setup. Select everything, except Cache. No need to save temp files. Then, click on Perform Backup. You’ll see a series of Dots scroll across the screen. Since we’re assuming that you are freshly rooted on a stock setup, this shouldn’t take too long, but know that with custom ROMs that you have completely setup, it could take a while. I’ve had some take almost 15 minutes.
Once it’s complete, click on Return, and then go to USB-MS Toggle. Click on it one time and wait for the pop up on your computer so you can see the files on your SD Card. Once it pops up, click on Open Folder To View Files so we can make some mods to your SD Card Files.
Scroll down to Nandroids and expand the folder. You’ll see a folder named something like HT121HL07014. Expand that folder and inside is your Nandroid Backup that you just made of your Stock/Rooted Setup. The reason I said this is your most important Nandroid is because it gives you a base to return to.
1). In case you ever have problems, this will give you a base to return to.
2). You’ll need a Sense ROM to Nandroid back to so you can update your Profile & PRL. Something you cannot do with AOSP ROMs or on the updated 3.5 ROMS.
3). If you ever need to take your phone into Sprint, and you don’t want them to see that you’re rooted, you can flash back to this Nandroid first, so all the techs will see is a Stock phone. There is no need to ever unroot, ever.
Make sure you make a Nandroid of your current setup before you restore a Nandroid.
The name of the folder that contains the images made in your Nandroid will be named something like BDEARS-20110319-0037. The numbers refer to the date and time that you made the Nandroid. In this example of my Stock/Rooted ROM, I can see I made this on March 19, 2011 and 12:37AM. To avoid confusion, you CAN rename this, however, you must preserve the original name and there can be no spaces in the name. I renamed mine to BDEARS-20110319-0037-stock. Now, I know which Nandroid is my Stock/Rooted setup.
I also do a separate Nandroid of just the Wimax and store it on my computer, in case I ever lose my RSA Keys.
On your SD Card, you may find it easier to store everything you use to modify your phone in custom Folders. On mine, I created a folder called XDA. Inside that folder, I created sub folders named Apps, Drivers, Icons, Kernels, ROMS, Root, Themes & Utilities, so I can organize everything I may use to flash, modify and update my phone. You should rename the PC356IMG.zip file on the root of your SD Card by adding Amon Ra to the end of the name (PC36IMG-Amon-Ra.zip), and moving it into the XDA\Root folder, so you’ll always have it on your SD card.
This would be a good time to download the custom ROM you want to use along with Dark Tremors Apps to SD Card (DT A2SD) and put them in the folders you created. I keep DT A2SD in the Utilities Folder. I would also suggest you download the V6 Supercharger Script and ViperMOD for AOSP Kernels (Also kept in Utilities). I would also search for the RUU for your particular phone, in case you ever need to do a complete reset back to “Out-Of-The-Box”. There are 2 types; PC36IMG.zip that you run in the bootloader (which I prefer) or an .exe that you run on your computer.
Partition Your SD Card
I think this is the first, most important thing you can do after backing up your original setup and before moving on to custom ROMs. And it’s very simple.
Create a folder on your Computer Desktop and Call it Evo Backup or something similar. Copy everything on your SD Card into this folder. When you partition, it will erase everything on your SD Card, so you must back it all up.
When it’s finished, click on USB-MS Toggle to disconnect from your computer. Scroll down to Partition SD Card and click on it.
Since the Evo doesn’t currently support SWAP, you can use 0 for the Swap Partition. If you have an 8 Gig or larger SD Card, you can use 2048 for the EXT Partition, although 1024 should be fine. The EXT Partition is where all of your Apps will be stored on your SD Card. If you’re going to move your Dalvik-Cache to the SD Card, you may want to use 2048.
While this is going on you may want to look for a ROM that the Dev has said contains Titanium Backup, or if you ADB and you know what you’re doing, you can pull the app prior to all of this, and add it to the XDA\Apps folder, if you created one, in your backup. The actual name of the app is com.keramidas.TitaniumBackup
Once the process is complete, select Upgrade EXT 2 to EXT 3. Do not use EXT 4 On Sense ROMS. DEFINITELY use EXT4 on newer AOSP ROMS. Your SD Card is now partitioned and you’re ready to restore your backup and flash your custom ROM so back out, go to USB-MS Toggle, select it and copy everything from the EVO Backup folder on your computer, back to your SD Card.
Flashing A Custom ROM
The first things you need to know are the little variations between Sense ROMS and AOSP ROMS.
Sense is the bundled software package that HTC provides on your phone out of the box. AOSP Stands for Android Open Source Project and there are plenty of differences. For starters. Some things you need to do in Sense, you cannot do in AOSP, like updating Profile and PRL, as I said above. Also, some AOSP ROMS have problems with GPS and while there are drivers you can flash to fix that, they may not always work, so you’ll have to go back to your Sense Nandroid and use what’s commonly called the Sense GPSCLRX Fix. I’ll explain that process in a bit.
AOSP will provide a cleaner ROM with a lot of options and mods built into it. While it may be plainer looking, there are a lot of theming capabilities that you can use to change the way it looks. Custom Kernels for AOSP can have SBC capabilities, which enhances the charging method for your battery and usually AOSP ROMS get better battery life than Sense ROMS do, because of the kernel options and the lack of “bloat” that you’ll find in a Sense ROM.
Sense ROMS are sleek with a lot of “Eye Candy” and really cool widgets. The ROMS themselves may be heavily themed and the 3rd party themes are usually gorgeous. A Good Sense ROM will not normally have anything that doesn’t work, ie. GPS, 4G, etc.
I prefer MIUI, an AOSP ROM with excellent stability, very few bugs and outstanding built in Theming options. It also comes with its own backup manager, which works well for saving everything, including desktop layout and current theme, and a Downloader that will download the weekly Releases automatically.
But, if you’re like many of us, you’ll end up trying everything on the menu until you find something that works for you.
Many ROMS come with the Stock HTC Kernel in them, so may want to research custom kernels and download a few, add them to your SD Card and try each out until you find something that works for you.
*Note: make sure that you only use AOSP Kernels with AOSP ROMS and Sense Kernels with Sense ROMS. Also, and I have seen this happen, make sure you are using a Custom ROM that’s built for the EVO 4G.
If you are flashing an AOSP Rom, like MIUI, you may want to clear your GPS Data first. If you’re using MIUI, I highly recommend it.
Sense GPS Fix For AOSP ROMs
You must be in a Sense ROM for this
Open Maps; get a lock on your position.
Open GPS Status & Tool Box, get a lock on your Sats and then hit Menu>Tools>Manage A-GPS State>Reset.
Open Dialer and dial ##GPSCLRX#
In the popup that asks for your password, enter your MSL, then reboot.
When the phone is rebooted, Open Maps, get a lock; Open GPS Status, hit Menu>Tools>Manage A-GPS State>Download. Once you are locked onto your Sats, power down, the Reboot to Recovery.
You CAN mod your ROM before you flash it. I keep all my ringtones, notification sounds and alarms on my SD Card.
Before I put the ROM on my SD Card, I make a copy of it, I open it with WinRAR, go to System>Media>Audio Folder and I delete all the sounds in the Alarms, Notifications and Ringtones folders. No sense having them load into internal memory if I already have them on the SD Card, and when you setup your sounds, they will still appear in the menus. I also add Titanium Backup to the System\App folder because I know I’m going to need it soon after I get booted up.
On the newer Sense ROMS, Voice Mail is not always included, so I have added a link to the bottom where you can download it and add it to the ROM before you flash it. See below on how to restore Data to your Voice Mail so it works.
I use the backup from Astro File Manager to pull the Apk for Titanium Backup and add it to the ROM I’m flashing.
In Recovery, back out until you get to the main menu, then go to Wipe and select it. While many people will argue this point, it’s my experience that process I’ll outline here is critical in successfully flashing a new ROM and cutting down on a lot of problems that people come across. It may seem like overkill, but it will not hurt to be thorough, so I can’t stress enough that you do it this way.
*Note: Do not use ROM Manager to flash ROMS or Recovery. It can lead to problems. The only thing I ever use ROM Manager for is to fix permissions.
Ok, in the wipe menu, the first option is Factory Reset/User Data. Select that and when it’s done, go down the list and select and wipe each option, except SD Card: and Battery Stats (Unless you are fully charged). I wipe Cache and Dalvik-Cache twice then I hit Factory Reset/User Data once again. Now the important part: Turn your phone off for about 3 minutes. This gives the phone time to discharge any voltage and clear remaining cache files.
While you may see a lot of people use superwipe scripts, they really are not necessary when you have Amon Ra. You just did manually what those scripts do, and you can know you did it right.
When you’re finished, back out, and go to Flash Zip from SD Card, select it, go to the folder where you have the ROM you want to flash and select it. Some ROMS take longer to flash than others, but once it’s done, go back to Flash Zip from SD Card and then go to the folder where you put DT A2SD and flash that. I know most ROMS have A2SD baked in, but this will ensure that everything works and that you have the full range of A2SD commands and Options. Once it’s finished, select Reboot System.
Because you also flashed A2SD, your phone will reboot 2 or 3 times. This is normal. Also, since you wiped your caches, they need to be rebuilt so it will take longer for the phone to boot up. I would guess that if you notice a boot loop or the soft key lights haven’t come on in 15 minutes, then you’re stuck and you’ll have to pull the battery and repeat the process. I can say though, in the hundred+ ROMS I’ve flashed, I have never boot looped using that wipe process.
Once the phone is booted, don’t touch it. Let it sit until the screen turns off. This gives everything a chance to settle in and start up. Turn the screen on and go through the preliminary setup process. Once your Desktop loads Reboot to recovery, if you’re going to flash GAPPS (AOSP ROMS) or a custom Kernel, or do a normal Reboot, and again, once booted, let the phone sit until the screen shuts off. Turn it on, and setup all the basics; Display, Accounts, Sound, etc.
If you are using an AOSP ROM, you’ll need to flash the GAPPS file with VVM, which you can do when you reboot for the first time. Multiple reboots in the beginning of a new ROM help the ROM and Kernel settle in.
Whenever you flash a zip file, other than a complete ROM, make sure to wipe Cache and Dalvik-Cache.
Now Reboot to Recovery and make a Nandroid. This is your Basic Setup of your Custom ROM. In case you have problems due to mods you make, you can always come back to this point and start over. Don’t forget to rename it so you can tell which Nandroid it is.
I keep 4 Nandroids on my phone; Stock/Rooted. Last known Good Setup. Current ROM Base Setup and Current ROM Complete Setup.
Custom Kernels
Make sure that any kernel you flash is built for your ROM. AOSP for AOSP Roms, Sense for Sense ROMs.
A word about SBC. While there has been a lot of talk about the safety of SBC Kernels, I have yet to see anything that substantiates it. I have used the same battery since I got my phone, a year ago, using SBC Kernels and have had no problems or shortened battery life. I highly recommend using SBC when possible
Custom CPU Governors
Once you have a custom kernel installed, you can set the Governor to another setting other than the default.
Here is a great guide on understanding CPU Governors.
CPU Governors Explained
Restoring Visual Voice Mail
Once you’re finished, reboot to system and either download Titanium Backup or if you added it to the ROM, open Titanium Backup and restore your apps with Data. Do not restore Voice Mail. If you are on a Sense ROM, it will already be good. If you are on AOSP and you flashed the GAPPS file, go back to Restore in Titanium Backup, and restore just the Data for Voice Mail. Not the App. Data only. Reboot and then go to Voice Mail, hit Menu and compose a voice mail and send it to yourself. If you receive it, your Visual Voice Mail is working. If not, search the forums at XDA for possible fixes, but this method has always worked for me.
At this point, you phone is basically setup and tweaked, but there are some other things you can use.
Below is a list of Apps and Practices I use to keep my phone working smoothly. Some of these Apps are paid Apps.
QuickPic – The very best Gallery there is. Allows you hide and password protect folders
Wimax RSA Keys – Allows you to ensure you haven’t lost your RSA Keys.
AdFree – Eliminates those annoying Ads on certain Apps.
Astro File Manager – Backs up and restores all your user apps.
Battery Monitor Widget – Shows you how your Battery is being used in detail
Busybox Installer – Installs the version of Busy Box you’ll need.
Kernel Manager – The Easiest Way to download Kernels. I still flash them in Recovery
MyBackupPro – Works like Titanium Backup and a good fall back if TB ever gives you problems.
ROM Manager – For fixing Permissions, only. The last step in my Process of flashing a new ROM.
Startup Manager – This is like msconfig in Windows. Lets you delete certain apps from loading at Start Up
System Tuner – Contains a lot of Tweaks, including setting the Governor for your Kernel
ROM Toolbox - AWESOME program that does everything from settings to Fonts to advanced settings and tweaks.
Once I have everything setup, I run Startup Manager to clean out my Start menu and then Rom Manager to fix Permissions.
Then I reboot to Recovery and make my final Nandroid of my Complete Setup
Battery Life
Battery life is a major concern with the Evo. There are some things you can do to extend Battery life.
Do not use Task Killers, as these actually work against the built in Memory Manager that comes with Android.
1) Turn of Data, unless you need it, and rely on WiFi whenever possible.
2) If you have your screen on a lot, turn the brightness down.
3) Calibrate your battery. There are several methods, but this is the best.
Want to thank oneoftherabble for this awesome guide on battery charging and calibration.
As soon as I can find his profile, I'll link it to this post.
You CANNOT calibrate a battery properly in an hour. Or in two hours. And you certainly CANNOT calibrate a battery properly in 30 seconds by wiping your battery stats file. It isn't going to happen. No how, no way. Flame on if you want... but I know the ACTUAL truth about it. It won't be correct.
Second.... No matter how well you calibrate your battery, after you flash a new Rom or kernel or ROM/kernel package, your calibration is no longer valid. Period. End of discussion. It ain't happening. Every ROM/kernel package is going to handle the information fed to it from the VR/Charging circuit differently.
Third.... This procedure requires that you have PATIENCE to do it right. If you don't have that patience, then don't waste your time. But.... STOP whining about how your supposed battery life is bad! What you are seeing on your battery meter is garbage and not worth looking at.
Now.... here are the steps to getting that meter and battery calibrated as a working unit... as close as we can get anyway when you figure out the actual accuracy of our meter system.
1.) You want to put your battery on the charger and let it charge. At this point, it won't matter if the phone is on or not. We just want to get it so the phone indicates a "full charge".
2.) When the LED turns GREEN then you need to POWER DOWN the phone. Let the phone sit for a couple of seconds.
3.) Unplug the phone from the charger and WAIT until the charging LED goes out. ( If you notice.. this takes about 2 to 3 seconds. That is how long it takes the phone to discharge energy to the point that the LED goes out. That is only at 3V! Now, think about how much longer it takes for it to get all the way to ZERO!?! NOW do you see why I say POWER DOWN when you FLASH?? )
4.) Plug the charger back in. It does NOT matter if it is the wall charger or USB or a car charger. The ONLY difference is going to be a little bit of speed when using the wall charger. ( More on this if you want the information )
5.) Wait until the LED turns GREEN. Now, unplug the charger. Wait for the LED to turn off.
6.) Plug the charger back in and wait until the LED turns GREEN. Unplug the charger. Wait for the LED to turn off.
7.) We are going to REPEAT 3 through 6 until it takes LESS THAN 10 seconds for the charge LED to change from orange to green.
8.) OK... it is going green really quick now. Unplug the charger and turn on your phone. THIS is where the patience part comes in. You want to run your phone WITHOUT CHARGING IT until it shuts itself off because of a low battery. Personally, I do this by turning up the screen FULL brightness, turning off the SLEEP mode, starting up MX Video Player and playing movies until I get down around 15% or so and then letting the phone discharge down until it shuts itself off.
( INFORMATION HERE!! You CANNOT "completely discharge" a Li-ion/polymer battery to "Zero" while it is in your phone. The circuits in the phone will not allow that to happen. It will shut down when the voltage gets to a point that it cannot support the phone. In our case we get down to about an actual 30% of rated battery capacity when out phones shut down. So don't worry and hurting your battery. Well, you COULD kill it. Run the phone until it shuts off and then LEAVE the phone like that for about 10 to 12 months. The internal resistance in the battery will drag it down to about Zero in that time. )
9.) Now then.... Plug in your charger and make sure that your phone is TURNED OFF. I would suggest that you pull your battery and put it back into the phone. That makes sure that the phone will be OFF when plugged in.
10.) WAIT until the LED turns GREEN. Now THAT took a LONG time didn't it??
11.) With the charger plugged in... Start your phone INTO RECOVERY! Clear ALL CACHES and THE BATTERY STATS NOW!
12.) POWER DOWN THE PHONE. I REPEAT... POWER DOWN THE PHONE Now... let your phone SIT doing NOTHING for ONE MINUTE! This step is REALLY important. Your phone CANNOT start to re-write the battery stats file properly when it reboots from Recovery. It is still LOOKING for the OLD battery stats and WILL NOT start to re-write it until it has tried and failed several times to find the old one.
13.) Start your phone up like normal with the charger UNPLUGGED. Let the phone boot and run it like you normally would until the phone shuts itself down for low battery. DO NOT RECHARGE WHILE YOU ARE DOING THIS STEP!! And, do NOT run it like a mad fool like you did to discharge it the first time. OPERATE IT LIKE YOU NORMALLY DO. ( oh yeah... please, please, please... ignore what your "meter" is telling you right now. It is really not feeling well. )
14.) When the phone dies from low battery, plug in the charger WITH THE PHONE OFF and let it FULLY CHARGE while POWERED DOWN!
15.) When the phone is fully charged... start it up!! Congratulations! You have been patient enough to actually calibrate your battery, ROM, kernel and battery "meter" to as close to accurate as they can be!!
( round of applause here ) YOU DID IT!!!
If you have any questions or you have any ideas on other information that you would like to see on your phone, batteries and such.... based on actual facts and research, then PLEASE drop me (oneoftherabble) a PM and I'll get to work on it!
GAPPS
If you flash an AOSP ROM, you have to also flash GAPPS, which contains all the Google apps.
You do this is in Recovery, after wiping Cache and Dalvik Cache. This file contains the most updated Visual Voice Mail and is confirmed to be working.
GB GAPPS w-VVM 20111212
Jellybean GAPPS
Removing Bloatware
Now that you got this far, you probably want to get rid of the bloat that comes with the Evo.
Pretty simple, actually. Since you got and paid for Titanium Back up, open it up, click on Menu>Batch and scroll down to the bottom.
Under "Un-Install" click on uninstall All User & System Apps, click Deselect All, then choose the apps you want to remove.
*Note: BE CAREFUL!
Only delete the Apps you know are safe. And really, these are pretty obvious.
These are definitely safe, but if you aren't sure, don't remove it.
Code:
amazonmp3.apk
com.htc.MusicWidget.apk
com.htc.MusicWidget.odex
com.htc.NewsReaderWidget.apk
com.htc.NewsReaderWidget.odex
com.htc.StockWidget.apk
com.htc.StockWidget.odex
com.htc.TwitterWidget.apk
com.htc.TwitterWidget.odex
Flickr.apk
Flickr.odex
htcbookmarkwidget.apk
htcbookmarkwidget.odex
htccontactwidgets.apk
htccontactwidgets.odex
HtcFootprints.apk
HtcFootprints.odex
HtcFootprintsWidget.apk
HtcFootprintsWidget.odex
HtcMusic.apk
HtcMusic.odex
HtcNaviPanel.apk
HtcNaviPanel.odex
HtcPhotoWidget.apk
HtcPhotoWidget.odex
HtcRingtoneTrimmer.apk
HtcRingtoneTrimmer.odex
htcsearchwidgets.apk
htcsearchwidgets.odex
HtcSoundRecorder.apk
HtcSoundRecorder.odex
HtcTwitter.apk
HtcTwitter.odex
MagicSmokeWallpapers.apk
MagicSmokeWallpapers.ode
Mode10Wallpapers.apk
Mode10Wallpapers.odex
Sprint_App_Updater.apk
Sprint_NASCAR.apk
Sprint_Navigation.apk
Sprint_NFL.apk
Sprint_Promotion.apk
Sprint_Qik.apk
Sprint_TV.apk
Sprint_VVM.apk
SprintTVWidget.apk
Stock.apk
Stock.odex
VisualizationWallpapers.
VisualizationWallpapers.
WidgetDownloadManager.apk
WidgetDownloadManager.odex
You can also use ADB. If you use ADB, here's the commands
Code:
adb shell
mount /dev/block/mtdblock4 /system
cd /system/app
rm amazonmp3.apk
rm com.htc.MusicWidget.apk
rm com.htc.MusicWidget.odex
rm com.htc.NewsReaderWidget.apk
rm com.htc.NewsReaderWidget.odex
rm com.htc.StockWidget.apk
rm com.htc.StockWidget.odex
rm com.htc.TwitterWidget.apk
rm com.htc.TwitterWidget.odex
rm Flickr.apk
rm Flickr.odex
rm htcbookmarkwidget.apk
rm htcbookmarkwidget.odex
rm htccontactwidgets.apk
rm htccontactwidgets.odex
rm HtcFootprints.apk
rm HtcFootprints.odex
rm HtcFootprintsWidget.apk
rm HtcFootprintsWidget.odex
rm HtcMusic.apk
rm HtcMusic.odex
rm HtcNaviPanel.apk
rm HtcNaviPanel.odex
rm HtcPhotoWidget.apk
rm HtcPhotoWidget.odex
rm HtcRingtoneTrimmer.apk
rm HtcRingtoneTrimmer.odex
rm HtcSoundRecorder.apk
rm HtcSoundRecorder.odex
rm HtcTwitter.apk
rm HtcTwitter.odex
rm MagicSmokeWallpapers.apk
rm MagicSmokeWallpapers.ode
rm Sprint_App_Updater.apk
rm Sprint_NASCAR.apk
rm Sprint_Navigation.apk
rm Sprint_NFL.apk
rm Sprint_Promotion.apk
rm Sprint_Qik.apk
rm Sprint_TV.apk
rm Sprint_VVM.apk
rm SprintTVWidget.apk
rm Stock.apk
rm Stock.odex
rm VisualizationWallpapers.apk
rm VisualizationWallpapers.odex
V6SUPER CHARGER & CAR-O-DOPE TWEAKS
People have said V6 is better for Sense ROMs and Car-O-Dope for AOSP ROMs.
Car-O-Dope
Note: The Menus in ROM Toolbox have changed so look carefully before you start applying these settings. They are all there, just in different orders
This is a really easy tweak in that you don't have to flash anything or run any scripts.
You'll need to download ROM Toolbox and System Tuner.
In ROM Toolbox, click on Performance and then on Memory Manager
Use these Settings:
Foreground Application: 6Mb
Visible Application: 12Mb
Secondary Server: 55Mb
Hidden Application: 70Mb
Content Provider: 85Mb
Empty Application: 100Mb
Click Apply On Boot
Go back, and hit Kernel Tweaks/Sysctl Tweaks, then use these settings:
Min Free Kbytes: 4096
Dirty Ratio: 70
Dirty Background Ratio: 50
VFS Cache Pressure: 10
Make sure Apply On Boot is checked.
Then, open System Tuner
Click Tweaks, the SD Card
Set Cache to 4096 and IO Scheduler to deadline
Click Boot Settings, select Re-apply SD tweak and select init.d script.
Reboot
V6 Super Charger/3G Turbo Charger
Download Busybox Installer from the Market, open it and install Busy Box1.18.2. This is the recommended version for V6 SuperCharger.
Download the V6 Supercharger from the link below and unzip it on your SD card. I have the files on the root of mine. I have all three files in one zip, when you go to that link. V6 Supercharger. 3G TurboCharger and the kickass Kernalizer. The link to XDA is the original thread posted by zeppelinrox, which will explain everything you need to know.
On your SD card, remove the .txt extension from all 3 files.
From the Market, download Script Manager. Open it and browse to the SD Card, then click on V6_SuperCharger_for_Android-update9_beta_6.3.sh Click on Help then check Run As Root and OK. Then click on Run
The first choice you make is how fast the text scrolls. Use 0, and then enter. Next you’ll choose which option. I think most people use Option 9, so hit 9, and then enter. When it’s done, enter 27, to Exit. Do not Reboot yet. When it’s done, back out to the SD Card, scroll up and hit the .. twice, then click on Data.
Scroll down to 99SuperCharger.sh and click on it. Click on Help and highlight Run as Root and Run at Root, OK, and then RUN. When it’s done, back out and browse back to the SD Card. Click on KickAssKernalizer_Tweaks_Installer, Click on Help, then Run as Root. OK and Run. I select No when it asks about the I/O Tweaks, although I’m not sure if that’s the best choice or not. But seeing anything that says it can cause boot loops makes me want to avoid it. Once it’s finished, back out again, go back to Data, then click on 99KickAssKernel, and use the same settings as before.
Go back to the SD Card, Click on 3G Turbocharger_Installer and chose fastest.
Back out, and Reboot.
**Note:
Read the threads for Supercharger for updated files. I have gotten away from V6 Supercharger, and use CoD Tweaks, exclusively, however, I do still use 3G, which has been updated. I have the best success with Experimental 1 setting
ViperMod For AOSP Kernels
This is a very simple to use Mod for AOSP Kernels.
Download the file, and flash it in Recovery, then reboot.
Once Booted, go to Terminal Manager and type:
SU
Vipermod
Once the script runs, I chose 2, to lower voltages and then chose 3, to lower by 75mv
You can play with the settings to see what works best for you
A2SD
From the Market, download ASDGUI. Open it and select Zipalign. Close the app and Open Terminal Emulator.
Type:
SU
A2SD check.
Once it’s done, Type:
SU
A2SD CacheSD
This will move the Dalvik-Cache to the EXT 3 Partition on your SD Card, opening up a LOT of room on your internal memory. Mine was over 200MB.
Once it’s finished, the phone will reboot and because of the new Dalvik-Cache, it will take longer to boot up.
Newest DT A2SD
Updating Radios
Radio Updates are released on occasion and having the newest radios is never a bad idea. Some people use different combinations to help improve battery life, reception, etc. you can read the thread below for possible radio combos.
When you update your radios, you should know that it is possible to brick your phone, if not done correctly. Some radios are in PC36IMG.zip form and this is what I prefer, but most in the thread listed are zip files that you flash in recovery.
Follow these steps exactly.
*Note: Make sure your battery has a good charge. I’d say over 50% is safe. Losing power during a radio flash will turn your Evo into a paper weight.
Boot to Recovery and go to the folder where you have stored your zip file for updating radios.
Flash the zip file as you would any other. The phone will extract the files, then reboot to a black screen with a green arrow. This could sit here for a few minutes. Do not worry if it seems to take a while.
Then the phone will reboot to recovery and say it’s clearing cache.
When the Recovery Menu pops up, you can reboot.
Newest Radios
Team Revolution MIUI Install Guide
Step 1. This is a MIUI ROM, which means GPS could be an issue, so the first thing I do is make a nandroid of my current Setup, then I restore my stock/rooted ROM.
Step 2. I update Profle and PRL, then I do the Sense GPS Fix.
You must be in a Sense ROM for this
Open Maps; get a lock on your position.
Open GPS Status & Tool Box, get a lock on your Sats and then hit Menu>Tools>Manage A-GPS State>Reset.
Open Dialer and dial ##GPSCLRX#
In the popup that asks for your password, enter your MSL, (You'll need MSL Reader from the market) then reboot.
When the phone is rebooted, Open Maps, get a lock; Open GPS Status, hit Menu>Tools>Manage A-GPS State>Download. Once you are locked onto your Sats, power down, then Reboot to Recovery.
Of course, I only use Amon Ra and in Recovery, I wipe everything, completely; Factory Reset., then each option underneat that, except SD Card:
Then I run Factory Reset again, then Cache and Dalvik Cache and Data again, jsut to make sure it's all clear.
Go to Flash, and Flash the Rom. Once it's done, go right back to flash and flash DT A2SD, the nI boot to System and once booted, I let it sit for a good 10 minutes, so everythign get's booted up and settled in.
At this point, I open LBE manager (Superuser) and set all my permissions to on and accept all.
I open Maps, get a lock, open GPS Status, and I already know I'll get a lock on my sats. Then I hit menu and update GPS Data.
Next is Connectbot, and I move my Dalvik Cache to my SD Card. Here's the commands
su
a2sd check
a2sd cachesd
The phone will reboot and again, I just let it sit for about 10 minutes.
Once I wake it up, I set my preferences, display, sounds, accounts, etc. MIUI ICS hasd a TON of new settings and one is the Status Bar Options. Hit Customize Statas Bar Notification and make sure Hide Notification is turned off. This will allow notifications to show up.
Once I'm done, I reboot to recovery, wipe Cache and Dalvik and Flash my Kernel.
The BEST kernel to use right now is Mason v0.14 SBC No FSO. I also Flash Vipermod.
That's it. If you use a different kernel and you have problems, this is the first place to look.
Upon reboot, I let the phone settle, then I open Titanium backup and restore my apps/Data. Now, I have had a lot of problems in the past with TB Freezing up when U try to restore all 117 apps I have in one session, so I do it in 3 now. I alphabetize the apps and then go A-H, I-P, Q-Z
Once finished, I open Rom Toolbox and go to Autostart Manager and make sure all the apps I DON'T need to be runnign at boot are toggled off. Then I set Car O Dope Tweaks. I'm one of the believers that Car O Dope is for AOSP, V6 is for Sense. I have yet to give Smurfs tweaks a run, but I plan to, soon.
I reboot and run Vipermod -50 in Connectbot, and then setup my desktop folders, etc. Then I g othrough any apps I need to set preferences for, Make sure VVM is working and that is basically it. Took some extra time, but I shake my head at the problems people are having that are almost alwasy attributed to shortcutting the process.
Almost all of the links and files anyone needs are on the guide in my signature
Visual Voice Mail for ICS
Follow this link. I'm on the MIUI ICS by Swiper and this worked perfectly!!!
http://forum.xda-developers.com/showthread.php?t=1547780
1. Download attached Sprint VVM apk, Install like any other downloaded APK
2. Using Root explorer, go to 'data/app' folder and find the newly installed sprint vvm
3. Select the VVM app and MOVE it to your 'system/app' folder. (permissions should already match because it was installed, but make sure it matches all other apps in system/app folder) 4. Boot into Recovery, Clear 'Cache'/ 'Dalvik Cache', then 'FIX PERMISSIONS', next 'Reboot system'
5. Once booted up, open the Sprint VVM app and click on compose.
The recipient will be '[email protected]'
Record about 15-20 secs just incase, then send the message.
You should receive a notification saying that your phone is provisioned.
6. Tap to compose another message and this time send one to yourself, wait about 5 mins and and you should receive a new vvmail notification.
The best part is, I never got to step 5. It provisioned on boot-up and I got notified of 3 Voice Mails I KNEW I had in there waiting for me.
I've included the app at attached to the OP
Bugs & Fixes.
• USB Connect - The two ways to fix this are with the app, USB Mass Storage in the market or the FTP Function is File Explorer.
• Camera only takes 3MP pics - D/L Camera ICS from the market and you'll get up to 8MP with Video Recording
• Theme Manager - There are very few themes for MIUI ICS. I understand that a new Theme Manager should be coming soon, according to the rumors.
• Music Player/Theme Sounds not seeing music folder - D/L Rescan Media form the market. Problem solved.
• Slow 3G/Data Speeds and Market Downloads. For me, after about a day, this fixed itself
Known Issues
No WIMAX
No HWA, yet
No Front Facing Camera
Useful Links
Amon Ra
TWRP Recovery
Smelkus Amon Ra-Supersonic-4.3
Dark Tremors A2SD
Newest DT A2SD
V6 Supercharger Original Thread
V6 Supercharger Newest releases
ViperMOD For AOSP Kernels
Download ViperMod
Partition SD Card
Download V6 SuperCharger/3G TurboCharger
Update Radios
GB GAPPS w-VVM 20110828
JB GAPPS
Car-O-Dope
Setup MIUI ICS For Optimal Performance
Newest Radios
With as much as you rant to people on doing ___, surprised I haven't seen you do this sooner. Well thought out.
What a read lol
Read all of it
Sent from my PC36100 using XDA App
teh roxxorz said:
With as much as you rant to people on doing ___, surprised I haven't seen you do this sooner. Well thought out.
Click to expand...
Click to collapse
Thanks. It took me the last 4 hours to get it all in there!
HipKat said:
Thanks. It took me the last 4 hours to get it all in there!
Click to expand...
Click to collapse
I think you missed the 3G fix, with setting the proxy host and ports to 0 / 0.0.0 on a sense rom. lol
teh roxxorz said:
I think you missed the 3G fix, with setting the proxy host and ports to 0 / 0.0.0 on a sense rom. lol
Click to expand...
Click to collapse
Ah, thanks! I'll add that and anything else people come up with
HipKat said:
Ah, thanks! I'll add that and anything else people come up with
Click to expand...
Click to collapse
No prob brah. If you talk about the recoveries, might as well give a snippet of the 4 available recoveries.
I'm gonna do that and other mods, etc in the 2nd post
HipKat said:
I'm gonna do that and other mods, etc in the 2nd post
Click to expand...
Click to collapse
I accept your proposed idea.
I see. Good job.
Sent from my PC36100 using XDA App
Very useful I think for everyone and its awesome how you took the time out of your life to put this guide together. Good for noobs and experience people just in case they forgot something lol. If I may suggest, you can add some guides to themeing, bit more on kernels, and differences on sense versions. Maybe pointing people in the direction of android kitchens and stuff. But this guide is on its way to success for others! Great job HipKat.
Nice!
Great job! Wish a guide like this was around in the beginning of my noob days. My only suggestion would be to add a highlighted "SEARCH BEFORE YOU POST" section, maybe throw in that "Google is your friend", ya know show people how to use google for finding things on xda with examples, like - "dsxida kitchen xda".
This guide needs stickied..
Thanks button slapped!
Now...
Now this is a guide. I vote for a sticky!
Well done.
Thanks guys. I'm gonna add a bunch more stuff for after you get all set up, like what was suggested in the 2nd post.I've been meaning to do this for a long time, but I'm the worst procrastinator there is
hmm
HipKat said:
Thanks guys. I'm gonna add a bunch more stuff for after you get all set up, like what was suggested in the 2nd post.I've been meaning to do this for a long time, but I'm the worst procrastinator there is
Click to expand...
Click to collapse
Sorry bro, but I got you beat on the procrastination... I'm still running XP on my 64 bit machine, I've had Windows Ultimate and Ubuntu sitting here on top of the desk for 3 months now..
Post it note..sticky... Awesome addition, bookmarked for future reference. Thanks HipKat
jamieg71 said:
Sorry bro, but I got you beat on the procrastination... I'm still running XP on my 64 bit machine, I've had Windows Ultimate and Ubuntu sitting here on top of the desk for 3 months now..
Click to expand...
Click to collapse
Well you two procrastinators unite tomorrow and end it.
jamieg71 said:
Sorry bro, but I got you beat on the procrastination... I'm still running XP on my 64 bit machine, I've had Windows Ultimate and Ubuntu sitting here on top of the desk for 3 months now..
Click to expand...
Click to collapse
Lol. .I have the newest Ubuntu sitting here for a month and still haven't installed it! lol
Still reading through this, but wish I'd had this when I first rooted my phone! Thanks for the work!
Sent from my PC36100 using XDA App
How to Trim Your Partitions in TWRP for a Truly Clean Install
Do you flash a lot of ROMs? Do you ever think to yourself, "I wish I could go through extra steps to get a performance boost?" Do you lie awake at night and wonder what happens to your old data when the "mkfs.ext4" command gets passed in TWRP?
If you answered 'Yes!' to 2 or more of those questions then this guide is for you! I'll explain how to run the Trim command in TWRP prior to a clean flash of a ROM to give you peace of mind and perhaps a performance boost! I emphasize perhaps because the level of performance we're talking about here may or may not translate to real world applicability, but I do it anyway because science!
Steps!***WARNING: I highly recommend making a backup of your previous ROM because if you follow this guide we are going to send everything that isn't a binary zero to the data abyss until the only thing left on your device is a bunch of zeroes and TWRP. YOU'VE BEEN WARNED!***
Follow this method prior to a clean install only (TRIM command can be run at any time)
1.) Reboot to TWRP and Choose 'Wipe' from the main menu
2.) Choose 'Advanced Wipe' and select Data, System, Cache, and Dalvik Cache
OPTIONAL (Most people shouldn't do this step): If you copied your TWRP backup to your PC and want to wipe out your SD card select 'Internal Storage' otherwise do NOT check this option!
3.) Swipe to wipe the selected partitions
4.) Hit the home button and choose 'Mount'
5.) Mount the System partition (data and cache should already be mounted)
6.) Hit back or home, choose, 'Advanced', and then choose 'Terminal Command'
7.) Hit 'Select' in the bottom right corner to get to the command prompt (you'll be in the root directory)
8.) type this at the prompt, "fstrim -v /system" and hit enter (do not add the quotes)--it will show wiped space
9.) type this at the prompt, "fstrim -v /data" and hit enter (do not add the quotes)--it will show wiped space
10.) type this at the prompt, "fstrim -v /cache" and hit enter (do not add the quotes)--it will show wiped space
11.) Reboot to Recovery
12.) Install ROM and Gapps of choice then reboot to system when prompted
13.) Super clean install complete
But, Why?!Here's a good article that sums up the answer to this question: http://arstechnica.com/gadgets/2015/04/ask-ars-my-ssd-does-garbage-collection-so-i-dont-need-trim-right/
F.A.Q.Q: What does the TRIM command do?
A: When data is deleted by an operating system it gets flagged for deletion. Which basically means that it gets overwritten if the OS needs more space. Otherwise, it just sits there invisible on your drive for an arbitrary amount of time. I can't stand arbitrary. I prefer weekly.
Q: Who else uses this command?
A: fstrim specifically is a Linux/GNU command, but if you try to defrag an SSD in any modern version of Windows they pass this command as well. OSX recently decided to extend this trick to third-party drives that owners installed themselves. How...kind of them.
Q: Do I need to run this?
A: Absolutely not. Running fstrim just accelerates a process that Android will do itself eventually. There is even a hardware trim built into modern SSD drives, but I don't know that all smartphone flash memory has this feature.
Q: Break down the "fstrim -v / " command for me cause I wanna learn!
A: fstrim is the linux command, -v stands for verbose output so you can see the results, and / is your partition that you are calling to run trim on. We only have 3 partitions to choose from and those are: System, Cache, and Data.
Q: I get the error: fstrim command not found. Halp?
A: Reboot to TWRP, re-mount the System partition, and re-run the commands.
Q: Does it work on F2FS?
A: It seems to. I ran it on my data and cache partition after converting them to F2FS and it trimmed like normal.
Q: Running fstrim, rebooting recovery, and running fstrim nets the same output. Why?
A: I don't know why this happens. If you run fstrim twice in a row you'll see the first one gives a byte output and the second run shows zero if passed on the same partition. However, rebooting recovery and perhaps remounting the drives causes it to think trim hasn't been passed yet and does it anyway? I'm guessing honestly.
Q: Will you add more questions to this as members find errors in your guide and remind you that you left something out because you're human and clearly don't know everything?
A: Absolutely.
Wow... nice!!
Great OP, too. Very informative!
"give you peace of mind and perhaps a performance boost"..
lol, perhaps? performance boost you will not get, its more like when you just run a rom after clearing your "dalvik". it will "feel" quicker for about an hour or so. i say "feel" because there actually isnt a boost there, its just cleaner on the first run. anyways, and regardless, this is still a good thread
Redundant file fragments take up space and slow performance as they're automatically deleted. You may not notice much of a difference, but it's definitely not a bad thing
This is great!! Thank you for this information
simms22 said:
"give you peace of mind and perhaps a performance boost"..
lol, perhaps? performance boost you will not get, its more like when you just run a rom after clearing your "dalvik". it will "feel" quicker for about an hour or so. i say "feel" because there actually isnt a boost there, its just cleaner on the first run. anyways, and regardless, this is still a good thread
Click to expand...
Click to collapse
Lol you're correct to an extent, it is a lot like clearing cache/dalvik in a sense. But the main difference is that it actually overwrites the written sections and not just wiping the MFT like mkfs.ext4 does when you wipe a partition.
I'll put it this way, if the fine people at ASUS include it in my UEFI BIOS for prepping a new install of Windows, I think it should be a recommended step in installing a new phone ROM. For advanced users of course
Sounds like a great idea. So to clarify, by doing this trim we do not delete the internal storage (SD card) files we use such as files listed under the "downloads" folder. Is that correct?
Nickchapstick said:
Sounds like a great idea. So to clarify, by doing this trim we do not delete the internal storage (SD card) files we use such as files listed under the "downloads" folder. Is that correct?
Click to expand...
Click to collapse
Correct. As long as you don't choose 'Internal Storage' when wiping with TWRP you can safely trim the entire data partition. The fstrim command only overwrites data that has been marked for deletion through user intervention or from a wipe command in TWRP.
So I just did this and wow there was a lot of data there. For me that short 5 minutes was worth knowing my phone has less trash just sitting around. Kudos AlkaliV2. I'll remember this til the end of time.
Followed the instructions perfectly and enjoyed the next few hours reapplying all of my settings.
enginuity2 said:
Followed the instructions perfectly and enjoyed the next few hours reapplying all of my settings.
Click to expand...
Click to collapse
I love a good clean flash. I even deny automatic restore and pick, "Setup as new device" each time because I love choosing what will and won't be on my phone. It's a rush exceeded by many things. But still a pretty good way to end the day.
After Years Of installing many roms on my s3 mini (download mode showed 180 counts of custom binaries download!!!) this article brings first day freshness to my phone :laugh:
this gave me performance again; but my progress bar in some apps is bad again
AlkaliV2 said:
I love a good clean flash. I even deny automatic restore and pick, "Setup as new device" each time because I love choosing what will and won't be on my phone. It's a rush exceeded by many things. But still a pretty good way to end the day.
Click to expand...
Click to collapse
Is this method feasible on a device that has a A/B partitions?