I was following the cm wiki tutorial
I put the moboot, cwm, Cm9 3/10 build and gapp into the cminstall and i did the ACMEinstall. moboot come up, good, however, CWM is not showing up in the boot manual and when I try to load cm9, it try to load and then it reboot and put me back at moboot manual. Luckily, web os still work. However, I am not sure as to what to do to get Clockworkmod and cm9 to install correctly. Please advice.
Did you use AcmeInstaller, or AcmeInstaller2? You are supposed to use Acmeinstaller2 for CM9.
At this point, use Acmeuninstaller to wipe the android partition off, and try again from scratch.
Believe it or not I can't find a download link for Acmeuninstaller. Can someoen pm me the link? Now i figure out why cm 9 won;t work but what about clockworkmod? How come it won't install.
After i run the uninstall do I need to install moboot again?
google "acmeinstaller2". it should be the first hit. I'd post a link, but I just registered.
hphttps://www.box.com/shared/479acdb6ef9c99fc7b92
heres everything in one shot for you. if you cant get the recovery to install you can extract the files from cwm.zip folder and put the uimage.clockworkmod into the /boot folder then run try rebooting if still nothing try running the update script manually as root in terminal emulator from android. hope this helps.
I manage tio fix the cmw issue by using novacom the image of the cmw and force cmw install from sd.
Related
UPDATE: Since some of you guys are still finding this useful, I updated the CWM version to 3.0.2.8. Please note that ROM Manager is the best way to install CWM 3.0.2.8. You should only need this .zip if you need to restore the B&N boot loader.
There are a number of CWM installable .zip files being distributed that break Clockworkmod in a way that Rom Manager will not fix. This .zip file will reinstall the B&N bootloader (to enable the recovery buttons) and install ClockworkMod on your internal memory. This .zip will only help if you have installed a "flashable" .zip and can no longer get into CWM by holding N + Power on boot.
This file can be installed with IOMonster's bootable CWM to re-enable the ability to use CWM without an SD card.
How to use:
1) Create a bootable CWM SD card from the link above.
2) Mount the SD card on your computer and copy the RecoveryFix.zip file to it.
3) Boot the Nook into CWM from the SD card.
4) Choose "install zip from sdcard"
5) Choose "choose zip from sdcard"
6) Browse to the RecoveryFix.zip and select it.
7) Choose "Yes - Install RecoveryFix.zip"
CWM should now work by booting and holding the N + Power buttons.
Technical details:
The bootloader (u-boot.bin) file included with the stock image has code to look for the recovery key sequence on boot. It also contains the "Touch the Future of Reading" splash screen. Some of the update .zip releases include a custom uboot.bin (to change the splash screen) that does not look for the recovery keys...so there's no way to boot into recovery without an SD.
Currently the only automated way to put the correct files back is by using one of the stock recovery .zips. These take the entire system back to stock though. All this .zip does is replace the stock u-boot.bin file, CWM uRecRam and CWM uRecImg files on the /boot partition. This can also be easily fixed by booting any image from an SD card and copying these files manually.
is this for use with any flashable rom or only certain ones? i'm on hcv4 and want to make sure this is safe to use before flashing it.
This worked fantastic! Thank you!
byproxy said:
is this for use with any flashable rom or only certain ones? i'm on hcv4 and want to make sure this is safe to use before flashing it.
Click to expand...
Click to collapse
This is a standalone fix - its only necessary if you've flashed a rom and could no longer boot into CWM recovery afterward.
thanks again xawen!
Thanks so much for this! Great work!
Signature verification failed
Will This work with the Froyo builds?
Thanks
huemedia said:
Will This work with the Froyo builds?
Thanks
Click to expand...
Click to collapse
It should work with any build. It does not replace any of the build specific files, just the boot loader and the recovery images.
Works on phiremod (CM7). I was stressing why I couldn't reach my internal recovery, but was too lazy to do any research on the matter. Just stumbled upon this and everything is fixed again
Just what I was looking for... thanks!
omarsalmin said:
Works on phiremod (CM7). I was stressing why I couldn't reach my internal recovery, but was too lazy to do any research on the matter. Just stumbled upon this and everything is fixed again
Click to expand...
Click to collapse
what do you mean by "everything is fixed again"?
I like phiremod and all, but no internal storage is irking me and I want to go back to rooted stock and try to make a CM7 bootable SD.
Flashed this, now I'm stuck on the "Touch the Future of Reading" splash screen. Running CM7 nightly latest, dalingrin's 1100MHz Overclock.
Edit: Trying to boot, won't get past that damn splash screen. Tried reflashing cm7-encore-full-5.zip, gapps, got nothing. Going to try flashing the overclock again and see if that helps.
Edit2: No dice. I don't have a backup, either. Guess I have to flash a whole new boot.img?
This should be stickied. There are a LOT of CWR files around here right now.
oshigeru said:
Flashed this, now I'm stuck on the "Touch the Future of Reading" splash screen. Running CM7 nightly latest, dalingrin's 1100MHz Overclock.
Edit: Trying to boot, won't get past that damn splash screen. Tried reflashing cm7-encore-full-5.zip, gapps, got nothing. Going to try flashing the overclock again and see if that helps.
Edit2: No dice. I don't have a backup, either. Guess I have to flash a whole new boot.img?
Click to expand...
Click to collapse
Same thing kept happening to me. I would hold down the power button or power+n button or power+volume up + n button to get the NC to shut down. Then, I'd press the power+volume up + n button for a few seconds; this would get it to boot into CWR. From CWR I'd select reboot system. After that it would have no problem fully booting (until the problem happeend again). I did notice that after a while the startup boot took longer. After pressing the power button to power on the NC it would take several seconds before the "touch the future of reading" screen to come up, and it would take several more seconds (30 or so) for it to get past that screen.
I'm not sure what the beneft is of doing this; as long as I have a CWR bootable microSD with me (always in the NC's case) I don't need this.
xawen said:
There are a number of CWM installable .zip files being distributed that break Clockworkmod in a way that Rom Manager will not fix. This .zip file will reinstall the B&N bootloader (to enable the recovery buttons) and install ClockworkMod on your internal memory. This .zip will only help if you have installed a "flashable" .zip and can no longer get into CWM by holding N + Power on boot.
This file can be installed with IOMonster's bootable CWM to re-enable the ability to use CWM without an SD card.
How to use:
1) Create a bootable CWM SD card from the link above.
2) Mount the SD card on your computer and copy the RecoveryFix.zip file to it.
3) Boot the Nook into CWM from the SD card.
4) Choose "install zip from sdcard"
5) Choose "choose zip from sdcard"
6) Browse to the RecoveryFix.zip and select it.
7) Choose "Yes - Install RecoveryFix.zip"
CWM should now work by booting and holding the N + Power buttons.
Technical details:
The bootloader (u-boot.bin) file included with the stock image has code to look for the recovery key sequence on boot. It also contains the "Touch the Future of Reading" splash screen. Some of the update .zip releases include a custom uboot.bin (to change the splash screen) that does not look for the recovery keys...so there's no way to boot into recovery without an SD.
Currently the only automated way to put the correct files back is by using one of the stock recovery .zips. These take the entire system back to stock though. All this .zip does is replace the stock u-boot.bin file, CWM uRecRam and CWM uRecImg files on the /boot partition. This can also be easily fixed by booting any image from an SD card and copying these files manually.
Click to expand...
Click to collapse
This fixed my nook. Thanks!!!!!
Works - after a few tries!
Really appreciate the work. Thanks!
While I keep my boot disk with me, I am very happy to have the ability to power+N into CWR.
Great work, thanks m8s!
xawen said:
All this .zip does is replace the stock u-boot.bin file, CWM uRecRam and CWM uRecImg files on the /boot partition.
Click to expand...
Click to collapse
Can you be more specific about exactly which u-boot.bin, uRecRam and uRecImg files are included - including source and version ?
ADude said:
Can you be more specific about exactly which u-boot.bin, uRecRam and uRecImg files are included - including source and version ?
Click to expand...
Click to collapse
This .zip has the stock (B&N) u-boot.bin and the uRecRam and uRecImg for CWM 3.0.0.5. It was built a while ago to fix an issue with specific CMW installable Froyo .zip files that were being distributed. I haven't seen any CM7 images with this problem, but if anyone still has a need for this I can update to a current CWM version and post tonight.
xawen said:
This .zip has the stock (B&N) u-boot.bin and the uRecRam and uRecImg for CWM 3.0.0.5. It was built a while ago to fix an issue with specific CMW installable Froyo .zip files that were being distributed. I haven't seen any CM7 images with this problem, but if anyone still has a need for this I can update to a current CWM version and post tonight.
Click to expand...
Click to collapse
Aha - I looked more closely and saw that it is an old thread that was brought to the surface by a "thanks" comment.
question
So I flash this fix and can get into CWM 3.0.0.5, then I flash the official CWM 3.0.1.0 and can no longer get into recovery. I also tried the manual procedure using adb. Still no dice.
What am I doing wrong?
I seem to have installed it but when I reboot and should be offered the chance to boot into WebOS or Cyanogen I am offered:
boot webOS
boot ClockworkMod
boot webOS recovery
reboot
shutdown
What have I done wrong and could it be qa case of just having to start again? I want to make sure that's safe, that's why I'm posting. Maybe I should add that I couldn't find the folder where the Novacom drivers were installed (on a mac Lion 7.2) so just typed this into Terminal
novacom boot mem:// </Users/tonyohooligan/Desktop/ACMEInstaller
Andy ideas?
There should be a "Space" after the "<" sign.
novacom boot mem:// < /Users/tonyohooligan/Desktop/ACMEInstaller
Did you place the GAPPS moboot Clockwork and CM7 .zip on the cminstall folder?
Also make sure you add "update-" at the beginning of every .zip
Hope that helps.
OK, there wasn't a space so there's something I have got wrong. Can I just start again from the beginning (placing the zip files in the cminstall folder, running ACMEInstaller etc) without damaging anything? Not sure about what you mean about adding 'update-' at the beginning of every .zip, is that to the start of the file name of each .zip if I attempt the procedure again? Thanks for replying BTW, much appreciated.
TonyOHooligan said:
OK, there wasn't a space so there's something I have got wrong. Can I just start again from the beginning (placing the zip files in the cminstall folder, running ACMEInstaller etc) without damaging anything? Not sure about what you mean about adding 'update-' at the beginning of every .zip, is that to the start of the file name of each .zip if I attempt the procedure again? Thanks for replying BTW, much appreciated.
Click to expand...
Click to collapse
Yes the "update-" at the start of every files helps the ACMEInstaller identify everything properly. Give it a try again.
Good Luck.
Will do, I'll let you know how it goes....
Rather annoyingly I have got the same result, no Cyanogen option at the multi boot stage. All zip files have gone from the cminstall folder as well. I rather get the feeling that I need to erase everything and start again but have no idea how to do that...
I wonder if I use Clockwork Mod to install Cyanogen, reckon that will work?
Hmm, got a message saying that it can't open the zip (bad). Going to download that file (update-cm-7.1.0-tenderloin-a2.1-fullofbugs.zip) again.
TonyOHooligan said:
I wonder if I use Clockwork Mod to install Cyanogen, reckon that will work?
Hmm, got a message saying that it can't open the zip (bad). Going to download that file (update-cm-7.1.0-tenderloin-a2.1-fullofbugs.zip) again.
Click to expand...
Click to collapse
Try running the ACMEUninstaller. You do so the same way you do the Installer and start all over again. Seems weird you cannot get it done. Are you sure the folder is "cminstall" and not CMinstall Cminstall etc?
OK, all installed, it was either the missing space or a dodgy .zip file. Either way thanks for taking the time to help me out atapia984 it is really appreciated.
TonyOHooligan said:
OK, all installed, it was either the missing space or a dodgy .zip file. Either way thanks for taking the time to help me out atapia984 it is really appreciated.
Click to expand...
Click to collapse
Anytime Have fun. Keep a look around at some of the other threads for troubleshooting. It is all out there.
Sent from my PC36100.
Thought I should just outline what I did to put this right in case anyone else has the same problem. I downloaded the ACMEUninstaller from here:
http://www.google.co.uk/url?sa=t&rc...-cW9Cw&usg=AFQjCNHZTu7Aghf80vOjo4Pa7Feslo0SmA
and put it on the desktop. Then I made sure the Touchpad was connected via USB and put the Touchpad in recovery mode (reboot, hold down volume up before power comes back on again) then opened the Terminal and typed:
novacom boot mem:// < /Users/tonyohooligan/Desktop/ACMEUninstaller
This deleted everything from the Touchpad. I then followed the instructions again and this time Cyanogen installed perfectly. Seems like a pretty damn good Alpha version as well, haven't had a crash yet. Thanks once again to atapia for all the help.
One last thing atapia, is there anywhere to report bugs as I find them without getting on the devs nerves?
i have re flashed my phone a while ago. it went well. from 2.3.5 to eclair 2.1. i reflashed due to wifi error, however, eclair installed, rooted the the phone, i plan to reflash it with a custom rom, Bionix 1.3.1 or Project V. im using the AIO toolbar, i tried it first with the Bionix, reinstalll packages 4 times. and i get an error. also with the Project V rom. same thing. error as well. the error says:
cannot locate /sdcard/update.zip
does this mean that my phone is not yet rooted? i have super user though.
Mostly likely you do not have the CWR Update.zip on your SDcard.
Go here and download Option B and put it on your SDcard. Reinstall twice and then flash your ROM
i already copy and pasted the file in /sdcard however it is still not working? shall i got into CWR? to make it work?
Put the CWR zip from my earlier post on your sdcard (not in a folder-just plain on card by itself). Might have to rename it Update.zip, but not sure about that one.
Boot into recovery (Blue) hit Reinstall Packages.
Will reboot back into recovery (Blue) and hit Reinstall packages again, will boot into CWR (Green).
From there, find Install zip from SD card and hit it. Now you can find you ROM and highlight it and install.
I went from bricked kernel(I forget which version) to cm9 alpha 2 and it put two versions of android on my tablet.
At moboot it gives me webos,cyanogenmod,and bricked-kernel...
How do I get rid of the bricked-kernel rom and have it boot into cm9 alpha 2 instead?
got into WEBOS...usinf preware to download Internalz pro....then in setting go into master mode...and in /boot folder, delete uimage for Bricked kernal...
What is preware?
Does it internalz cost money?
I've booted into webOS like once so I am not familiar with any of this stuff.
Ignore that post. Not only is that possible in android, but that would just permanently break your Wi-Fi until you do it the proper way, by following the instructions in the OP of the bricked kernel thread.
This thread details how to get rid of the extra boot option: http://forum.xda-developers.com/showthread.php?t=1511747
I actually just did this. I used to use File Expert (free version) but they started requiring an upgrade for the root permissions, and every other root-explorer app would cause crashes & restarts. If they work for you, go ahead and use that, following the steps from the link above. I couldn't figure out why, so what I did to fix this was:
Download & Install Remount from the market https://market.android.com/details?id=com.stericson.remount
Then, run that, and choose to remount /boot as r,w
Once that was done, I used Terminal Emulator to go to /boot, change to su (to get root), and edited moboot.default (vi moboot.default), changing the contents of this file to "CyanogenMod" (it was set to the old bricked kernel entry). This will set the default to boot into CM. You can stop here if that's all you want.
I finally just went ahead and deleted /boot/uImage.CM_Bricked_Kernel as well since I wasn't going to use this anymore and it was messed up anyway.
Greetings everyone!
New *registered* user here! I've been frantically sifting through post after post on the forums all night hoping to get some help with an issue I am having on my Vibrant.
Goal:
Remove some bloatware ONLY, not looking to install any ROMs or modify the phone too much...just clean some annoying apps and icons off.
Phone Information:
Model SGH-T959
Firmware 2.2
Baseband T959UVKB5
Kernel 2.6.32.9
Build FROYO.UVKB5
I currently have the latest version of Java, Android SDK, and SuperOneClick installed.
Install directory of AndroidSDK:
C:\AndroidSDK
My method of failure:
Open SuperOneClick, Click "Root"
Start, Run, "CMD"
cd c:\AndroidSDK\tools
adb shell
mount -o rw,remount /dev/block/st19/system
This is where it fails and I run into an endless loop of it telling me the proper usage of the "mount" command. I thought I had it at one point but when I typed: rm /system/AmazonMp3.apk all it did was tell me that it was a read-only file and that it couldn't be deleted.
Can someone help lead me in the right direction of what I am doing wrong? I rooted and removed all bloatware about a year ago but I just did an upgrade through MiniKies to the latest version of firmware and I can't seem to remember the process I went through that long ago to get it done right.
I apologize for possibly asking a question that has been asked numerous times but I just couldn't seem to get the wording right to get any helpful results in the search of the forums. Thank you so much for the time in reading this and the future help if any can be provided. Have a great night!!!
It looks like you are in the wrong directory. Open a command prompt in
C:\AndroidSDK\platform-tools
Open the platform tools folder. Click on a blank space > hold down the shift key > hit right click > select open command window here. Then enter the commands:
adb devices "to check if your device is connected. also make sure usb debugging is enabled on your phone.
adb remount
adb shell
su
mount -o remount,rw -t rfs /dev/stl5 /system
rm -r /system/app/[AppName].apk
If you want a list of all your /system/apps enter this command
cd /system/app
ls *.apk
This is much easier if you download rom toolbox from the market. All you do is go to /system/app and delete whatever bloatware you dont want.
BUT BE EXTREMELY CAREFUL WHEN DELETING SYSTEM APPS. ONLY DELETE WHAT YOU KNOW IS BLOATWARE OTHERWISE YOU WILL GET FC'S
good luck
Would I still need to follow the steps prior to that and use SuperOneClick to root the device or do I just skip that process and go straight to the cmd prompt?
Also, I followed a tutorial I found for installing the Android SDK that informed me to copy all the files from android-tools to the tools directory and use that instead but I don't know what the use in that is except for maybe a smaller directory name?
EDIT: I tried what you said with and with using SuperOneClick prior to the procedure and the cmd prompt displayed the following text:
*opened cmd promt in C:\AndroidSDK\tools (no files in platform-tools anymore)*
adb devices (it found my device connected)
adb remount (adb remount: no such file or directory exists)
The adb shell and su commands works fine BUT I still hit the endless loop of it trying to explain to me the "usage" of the mount command.
I will look into Rom toolbox as I'm trying to figure this out as well. Thank you.
I strongly recommend you download root explorer or some similar root browser app. Of course though your phone must be rooted. Just try rom toolbox. It has its own root browser within the app along with other useful features. This is probably the easiest way to uninstall the bloatware in your case since you are having issues with adb.
Sent from my Galaxy Nexus using XDA
Thank you!
Okay, I have the suggested "rom toolbox" downloaded from the market and I will try to use that but SuperOneClick does not root the phone deep enough for rom toolbox to see the phone as rooted so...will the "updated.zip" method work for this instead?
I haven't tried it before but I am willing to give it a go if you think it's the best method. If this is the method you recommend, would you happen to have a link to the most recent or atleast most trusted updated.zip rooting method?
CScrivener said:
Thank you!
Okay, I have the suggested "rom toolbox" downloaded from the market and I will try to use that but SuperOneClick does not root the phone deep enough for rom toolbox to see the phone as rooted so...will the "updated.zip" method work for this instead?
I haven't tried it before but I am willing to give it a go if you think it's the best method. If this is the method you recommend, would you happen to have a link to the most recent or atleast most trusted updated.zip rooting method?
Click to expand...
Click to collapse
You can try rooting your phone using this toolbox.
http://forum.xda-developers.com/showthread.php?t=954509
If that does not work for you i will try and find the link to the "one click root program" i use all the time.
Here is an excellent guide to root.
http://forum.xda-developers.com/showthread.php?t=849028
Sent from my Galaxy Nexus using XDA
Here is the program i use. Just remember to have usb debugging enabled on your phone. It really cant get any easier than this.
http://forum.xda-developers.com/showthread.php?t=739300
Sent from my Galaxy Nexus using XDA
So I downloaded the one click program you suggested and the program itself seems to bee pretty straight forward.
I connected phone to computer with debugging on. Opened program and hit one click root. It started doing it's thing...phone rebooted and went into recovery. I started to follow instructions up until I got to where it said install packages. When I clicked it, the phone said installation failed no such file our directory exists.
The phone is looking for the updated.zip file but none exists in the one click folder. There is a root.zip and an unroot.zip...do I need to rename one of them to proceed???
Thank you so much for all the help so far, I feel like I'm so close but just not there yet. You have been an incredible help!
Sent from my SGH-T959 using XDA
CScrivener said:
The phone is looking for the updated.zip file but none exists in the one click folder. There is a root.zip and an unroot.zip...do I need to rename one of them to proceed???
Click to expand...
Click to collapse
The way (Stock) Recovery works is if you are not "Install from SD" then it will look for the file labeled Update.zip. So you can rename only the Root.zip to Update.zip and make sure that is the only thing on your internal SD labeled that or with .zip Put the unroot.zip in a folder for now. Then try again.
Alright, will give that a try when I get home. I thought I read that the program copied the update.zip file to the phone during it's process so I didn't want to do anything to work against that. I will rename one of the files, copy it to the phone and give the one click root another shot. Thank you!
Sent from my SGH-T959 using XDA
CScrivener said:
Alright, will give that a try when I get home. I thought I read that the program copied the update.zip file to the phone during it's process so I didn't want to do anything to work against that. I will rename one of the files, copy it to the phone and give the one click root another shot. Thank you!
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
There is no need to rename anything. The program does it all for you. Play close attention to the first screen (green one) if it says update.zip copied successfully it will then reboot your phone to stock recovery. Once you are in stock recovery all you do is click reinstall packages. Keep clicking reinstall packages even if it reboots the first time. To prove my point mount your phone to your pc and check to see if the update.zip is copied onto the root of your into storage. If not well copy the update.zip from the last guide i suggested from above.
Also check to see if the superuser app is installed on your phone. The program also installs that along with the update.zip. If you have superuser then go to the market download rom manager so you could download CWM.
Sent from my Galaxy Nexus using XDA
Alright, so I tried it again once I got home. Didn't work BUT I did see that update.zip was installed into my phone. The sig verification failed, which means I need to change recovery versions to the one that skips sig verification correct?
I'll go search the forums for that since I remember seeing that a little while ago but that is the correct path I need to take at this point in time am I right?
Thank you so much! Big big help!
You can pull the CWR from my signature. Same as before. Put it on your internal labeled update.zip, boot into recovery and and scroll down to Reinstall Packages. Hit it. It will cycle and probably come back to stock recovery. Hit Reinstall Packages again and the stock recovery will go from blue to green (CWR).
Side note, probably from there you will be able to install the Superuser update.zip. Just go to Install from SD card and find it and hit it. The reboot. Might not but the CWR instructions above shoudl work for you.
Well I changed the recovery version using the file from http://forum.xda-developers.com/showthread.php?t=833423 and then used the OneClickRoot and was able to get the update installed (I think). The phone booted up normally, I noticed that SU Permissions was installed so I figure I am rooted correct? WRONG. Rom toolbox says I am not. Is there another way to verify? Should I reinstall Rom toolbox incase it's just bugging out on me?
So I tried using Rom Manager too. Looks as tho SU is not installed correctly, will have to try again I guess.
Cannot install CWR, tried and the recovery text stays blue even after 14 times of reinstalling packages...
This phone will be sent flying across the room sometime tonight I'm guessing. About to erase the entire thing and try starting from scratch again. (Start from Eclair and work my way up maybe)
If you are willing to start from Eclair it would be soooo much easier that all this stuff.
Odin to stock, flash CWR from my signature, go from blue to green and then flash Fishman's Bionix and you are good to go. Simple and way easier than all this mess. Just download Fish's and put it on you SD card somewhere you'll remember. Once in green recovery just scroll to that ROM and flash it per OP.
We've just been trying to Root you since on your OP you said you didn't want to flash a custom ROM.
Well...I'm still trying to avoid flashing Roms (I've upgraded through MiniKies and that's it).
I've only been trying to root just to clean bloatware off but it seems that I must be lacking the technical skills to follow instrcutions properly....nothing is cooperating and even after following all steps nothing wants to work like it should.
Grrrr! One last try to get CWR working before I lose my mind and need to take a break/walk away for a bit.
Ok, so I'm currently back to stock Eclair (ew!!) and about to boot to recovery to install CWR. Wish me luck on that one....
Wooo, CWR up and running! Now I just have to work on a flash maybe or whatever steps were suggested next...I might try the ROM you suggested.
The ROM gets placed on external sdcard and installed from within CWR correct?
Do most ROMs remove bloatware and useless apps?
Yes and are pre-Rooted. Put the ROM.zip on either card. I have a folder that I use. Boot into recovery and get green recovery back. Go to install from SD, find the ROM and flash it per the OP instructions.
Bloat free, pre-Rooted and usually has Voodoo so you can get Voodoo Sound from the market and have a sonic ear-gasm.
Just wanted to say thanks for all the help! I installed the suggested ROM last night and I am very happy with the results thus far. It was alot easier than I thought it would be. Flashing a ROM was MUCH more simpler than the root only decision. Thank you again!