[Q] Running CM7.2 (MiRaGe-KANG build) - How do you know V6 is working? Wi-Fi Question - Nook Color Q&A, Help & Troubleshooting

Hi All,
I'm new here but have been reading the threads since I got a Nook Color last month.
I'm booting from a 16GB microSD card: [CM7.2-RC0] MiRaGe - KANG build of CyanogenMod ("encore_CM72-MiRaGe-12122011") and also installed "gapps-gb-20110828-signed"
I ran the Battery Calibration tool just yesterday when it was plugged in and at 100%
I installed the Nook Color USB Mass Storage utility so that I could access the SD card from my computer
I also followed the thread's advice on installing V6 Supercharger (http://forum.xda-developers.com/showthread.php?t=1344873):
Nook Color with its large kernel with many features consumes the RAM rapidly and low memory becomes an issue where V6 Supercharger becomes useful.
Here is how I install, it takes only one minute.
- Download update 8 to sdcard root directory.
- Start Terminal Emulator and do the followings
- su
- cd /sdcard
- sh V6*
- choose option 0 (fastest scroll)
- choose 9
- choose option 16 to reboot ​
I have a couple questions that I can't ask in the dev threads since I just registered here.
How do you check if V6 Supercharger is working? I didn't install BusyBox or Script Manager like the original V6 Supercharger thread suggested...so is there a way to do this through the Terminal Emulator?
What do you recommend overclocking your CPU settings in CyanogenMod settings to? I have mine currently set to Conservative, Min: 300 MHz, Max: 1100 MHz, and Set on boot. Would 1200 MHz be pushing it too much?
I've read some questions and threads on here regarding the Wi-Fi turning off when it goes to sleep. When you press the side power button to turn off the screen, is that also putting the device to sleep? Is there a solution to the problem of the Wi-Fi turning off on its own when the screen is off?
Thanks in advance to any advice or answers! And of course, if you have any suggestions on other things I should be installing/uninstalling I'd greatly appreciate it!

AngelWings8 said:
I have a couple questions that I can't ask in the dev threads since I just registered here.
How do you check if V6 Supercharger is working? I didn't install BusyBox or Script Manager like the original V6 Supercharger thread suggested...so is there a way to do this through the Terminal Emulator?
What do you recommend overclocking your CPU settings in CyanogenMod settings to? I have mine currently set to Conservative, Min: 300 MHz, Max: 1100 MHz, and Set on boot. Would 1200 MHz be pushing it too much?
I've read some questions and threads on here regarding the Wi-Fi turning off when it goes to sleep. When you press the side power button to turn off the screen, is that also putting the device to sleep? Is there a solution to the problem of the Wi-Fi turning off on its own when the screen is off?
Click to expand...
Click to collapse
1. Open your app drawer, flick the screen, if it scrolls instead of stuttering then V6 is working.
2. OC as much or as little as you want. 1200 is safe but some people say that the increased battery drain isn't worth the slight increase in speed. You have to decide for yourself.
3. Yes, that is putting the device to sleep, yes, that will turn off your wifi. Most people prefer sleep to just screen off because it saves your battery. The old CM7.0.3 and earlier didn't have sleep mode and you lost 1-3% of battery per hour of standby. If you're ok with that then:
wireless & network settings > wi-fi settings > menu > advanced > wi-fi sleep policy>never

Thanks a bunch! I was wondering why there wasn't an "Advanced" option when I went to Wi-Fi settings...didn't even think to press the menu button! I chose to set the sleep policy to "Never when plugged in" and we'll see if that works for me. Is the default "When screen turns off"?

yup, it's been the default on every android device i've used. It allows you to put your device to sleep and then turn it back on when you need it without having to wait for android to boot. I can tell when an app kept my nook from sleeping because my battery is dead.

I installed the Nook Color USB Mass Storage utility so that I could access the SD card from my computer
Click to expand...
Click to collapse
I don't think you (we) need this step since I believe the feature has been integrated into the latest CM7 builds, assuming MiRaGe the same.
1. Open your app drawer, flick the screen, if it scrolls instead of stuttering then V6 is working.
Click to expand...
Click to collapse
Without even installing V6 Supercharger, I don't believe that I ever experience the stuttering. If that's the case, how do I know the V6 script is working/running/better performance?

votinh said:
Without even installing V6 Supercharger, I don't believe that I ever experience the stuttering. If that's the case, how do I know the V6 script is working/running/better performance?
Click to expand...
Click to collapse
You can tell it's installed Ok by running it again and using option 1 to show the status.
Not so easy to tell its immediate benefit as its real job is trying to ensure that the memory is kept free, so you have to compare operation over time as more apps get used / loaded.

You know, I'm not sure if I ever experienced the stuttering either. I'll have to check later today.
If I just used the Terminal Emulator, would I essentially do these steps?
- su
- cd /sdcard
- sh V6*
- choose option 0 (fastest scroll)
- choose 1 (to show status)
- choose option 16 to reboot
Also, just want to confirm that you need to keep the V6 file in the sdcard root directory right? I'm assuming if you ever delete or move the V6 file, V6 Supercharger would stop working?

By definition, "root directory" of the bootable CM7 uSD card is the one that has 117MB where ROM/GApp zip files used to be. If that, I don't believe that we (or NC) can access that partition. If it does, I want to know too.
With CM7 runs off eMMC, root directory of "normal" uSD card is ......... ehh, not in any sub-folder.
Can someone who actually do run V6 script chip in for some info?
Big thanks

Oh I'm sorry, when I wrote "sdcard root directory", I mean the root directory of what you can access when you plug it in via USB and not the partition where you're booting CM7 from. It's essentially where I save all my folders of wallpapers/music/videos/etc.

AngelWings8 said:
Oh I'm sorry, when I wrote "sdcard root directory", I mean the root directory of what you can access when you plug it in via USB and not the partition where you're booting CM7 from. It's essentially where I save all my folders of wallpapers/music/videos/etc.
Click to expand...
Click to collapse
Oh, ok.
Did you run the script yet? How was it?

No offense to the person that suggested checking V6 by flicking the app drawer, but there are a couple more reliable options.
I am no expert, by any means, but from looking over the program, it looks like all it really does is prioritize your apps by whether they are foreground or back, a launcher or hidden and so on, then allocate memory to the apps following that priority. I think any response check would wholly depend on how many apps you have running (or being killed by the V6 task killer)
Either way, even if it turns out that I wholly misunderstood the program, I can tell you how to see if it is installed and running for sure.
This will work if you have already installed the V6 or not. the following are directions for terminals, if you are running the dev's Scripter app, I would imagine it is similar, if not automatic.
Open a terminal.
su
cd sdcard/
sh V6*
the menu then scrolls. option 0 is often recommended here, but that is just a value for the scrolling speed of theV6 script itself. you can increase this number if you errant to spend a little time looking over what you're running.
f you think you have already ran the V6 look below the 17 options to current minfrees. If you want option 9 (Mirage Kang's recommendation) the current minfrees should read 6, 12, 75,100,125,150 mb. if it does, then you are supercharged. if not, go ahead and select option 9.
Now before you reboot, I would recommend that you run option 15 if you are not using Scripter. that will run V6 through the terminal emulator. That way, should you ever want to check your values or mess with the options, you can open terminal, su, then bash V6, and it will run.
Even if you don't think you will ever want to readjust the supercharger again, it had the added benefit of yelling you your "installation was INCREDIBLY SUCCESSFUL" which is bound to make you feel supercharged.
Run option 16 to reboot and now you can feel secure, without relying on a subjective flick of the app drawer.

Thanks everyone! I'm going to try uninstalling the USB Mass Storage app I downloaded then, if I don't actually need it with the CM7.2 version.
I did run Terminal Emulator to see what the minfrees were and it was the same as option 9. I didn't even think of running option 15, but I've done so now. After I rebooted, I opened up the Terminal Emulator again and typed "su" and then "bash V6" and it says "bash: V6: No such file or directory". Am I doing something incredibly stupid or wrong?
Also, do I have to leave the V6 txt file on the sdcard or can you delete it after you've run it?

I would bet it was a problem with case. bash v6 and bash V6 are two different things. Capital V should fix the issue.
Save the txt file, it is the actual script that is being ran. Without it, nothing happens.

I used bash V6 (and tried bash v6 just to see if anything would happen) and I got the same message. I thought maybe I just didn't do it right first time around, so I went back in, checked the minfrees and entered option 15 and then 16 to reboot, but when it did, it booted to the stock Nook Color OS. I just shut down and turned it back on and it went into Cyanogenmod with no problem...but is that strange that it didn't boot into CM? And once I got into CM again, I checked the overclock settings and it was back down to 800 GHz (even though I set it on boot at 1200 GHz).

votinh said:
By definition, "root directory" of the bootable CM7 uSD card is the one that has 117MB where ROM/GApp zip files used to be. If that, I don't believe that we (or NC) can access that partition. If it does, I want to know too.
With CM7 runs off eMMC, root directory of "normal" uSD card is ......... ehh, not in any sub-folder.
Can someone who actually do run V6 script chip in for some info?
Big thanks
Click to expand...
Click to collapse
That's a partition, not a directory. Every partition has a separate root directory.
With emmc, it's simpler because there's only one partition on the sd card so there's only one root directory. You can copy it over using usb or a sd card reader and it'll end up in the same place.
If you are running off the uSD, transferring files via USB places them on the "SDcard" partition on the uSD. That way, CF3D can find the files.
**I have a ton of apps, which may be the cause of my app drawer stuttering on flick (where you try to swipe to the bottom of your app list in one flick).

Thanks for all the useful replies! I uninstalled Nook Color USB Mass Storage app, and it seems to be working fine!
I saw that there is a new build for [CM7.2-RC0] MiRaGe - KANG and was wondering if you guys could kind of walk me through doing my first update. I downloaded both of these files listed in his first post:
- ROM - 01132012 build: MD5sum: 41676325569e773340378ba886dd6bf6
- transparency theme with circular battery indicator for 01132012 build. MD5sum: 9fb6a03e91f01c162a2f8f37cfe8ac77 Flash this theme after booting once with the new ROM. Do not use this theme with earlier or later builds.​
For installation, it says "Just follow the official CM7.1 installation via recovery guide (stable or nightly). The removed components will be retained on your NC from the previous ROM if you do not uninstall those (Titanium recommended) or do a clean wipe."
I do have Titanium and I backed up using the "all user apps and system data" option. Is that adequate or is there a different option I should be using? Also, since he mentions that the removed components will be retained on the NC if you don't uninstall those...how do you know which ones and how do you go about uninstalling those? I never actually used the uNooter or ROM Manager...so I'm trying to figure out how to make it work with the method I used the first time around (VeryGreen's: http://forum.xda-developers.com/showthread.php?t=1000957) What I've done is just renamed "encore_CM72-MiRaGe-01132012" with "update-" in the beginning, put it on the boot partition, and rebooted into recovery.

wrong button click, LOL
Anyway, that should be it.

Yeah, my NC seems to be working fine after just renaming it to "update-" in the beginning of the files and booting it into recovery, but the transparent battery indicator theme didn't seem to do anything
Also, this is a random question, but do your NCs' volume rocker thing seem kind of loose? I was just wondering if that's normal because mine you can move left and right (you can kind of wiggle the button itself).

AngelWings8 said:
Yeah, my NC seems to be working fine after just renaming it to "update-" in the beginning of the files and booting it into recovery, but the transparent battery indicator theme didn't seem to do anything
Also, this is a random question, but do your NCs' volume rocker thing seem kind of loose? I was just wondering if that's normal because mine you can move left and right (you can kind of wiggle the button itself).
Click to expand...
Click to collapse
My volume button does that too.

Oh good, I was hoping it wasn't some sort of issue with the button being broken or something.
Also, I asked this earlier, but could someone explain to me what to do since after updating a new [CM7.2-RC0] MiRaGe - KANG build, he says "The removed components will be retained on your NC from the previous ROM if you do not uninstall those (Titanium recommended) or do a clean wipe. If you don't need a clean wipe, i.e. current ROM is CM7.1, instead of step 5 in the guide, do wipe dalvik-cache only."
Is that what I should be doing? How do I go about it using VeryGreen's method (without using ROM Manager or ClockworkMod Recovery?)
I'm sorry if I just sound like a complete noob, but I'm trying to learn!

Related

[Q] Custom ROM bugs? Help!

Hi.
I'm running SyndicateROM Frozen 1.1.1, and I've observed several bugs. I need to know if the bugs are the fault of the ROM (and thus something I should take up with the ACS developers) or if they're my fault due to something I'm doing wrong.
1) I use folders on my LauncherPro* homescreens to organize apps. For this example, I'll use my Games folder. In it, all the games except 1 are installed onto my microSD card. After I drag the icons to the folder the first time, they are fine. However, after a reboot, the icons of the apps installed to my microSD card that are in folders change to the generic Android green/white icon. The apps still load properly, and the icons appear fine in the App drawer.
*LauncherPro is included as the only homescreen in this ROM.
2) I'm having an odd issue with Plants vs. Zombies. It loads to the main screen, and I can manage the player names, but after I click to start the adventure, it locks up with the Adventure button depressed. The main screen music also dies. No FC/wait dialog appears. I have to press the Home button to get out of it. PvZ is unplayable in this condition. Rebooting does not help, nor does formatting /cache or Dalvik-cache in custom recovery.
3) JuiceDefender Ultimate tells me in the log that it cannot toggle 2G/3G data, and that this is likely to be a kernel issue. As far as I know, this reduces the effectiveness of JD.
4) In ClockwodMod Recovery 3.0.0.6, I cannot mount my microSD card for the PC to read/write it. I get "E:Unable to open ums lunfile (no such file or directory)". I've seen posts that indicate this is a bug that was corrected in later versions, but I don't know if the custom ROM I am running is compatible with later versions,or where to find later versions. EDIT: I found CWM 3.0.2.5, and flashed it. It still reports the same error when attempting mount my microSD card for my PC to work with.
5) When I connect the phone's cable to my PC and get the the "Charging/Mass Storage/Tethered" popup and click Mass Storage, and then click "Turn On" at the next screen, it appears to work fine, except that my PC shows no new removable media drives. Sometimes, even though I touched the "Turn On" button, nothing happens. The button does not turn into a spinning wait indicator, nothing.
6) I found a post (that I've since lost track of) that purported to provide instructions to see if journaling was enabled. (I'm already formatted as EXT4). The instructions errored out, apparently because I have the wrong version of tune2fs. I'm not sure how to copy the correct version over, so I flashed the "Journaling On" zip shortly after I re-flashed this ROM. Does EXT4 and journaling stick between ROM re-flashes?
SweetBearCub said:
Hi.
I'm running SyndicateROM Frozen 1.1.1, and I've observed several bugs. I need to know if the bugs are the fault of the ROM (and thus something I should take up with the ACS developers) or if they're my fault due to something I'm doing wrong.
1) I use folders on my LauncherPro* homescreens to organize apps. For this example, I'll use my Games folder. In it, all the games except 1 are installed onto my microSD card. After I drag the icons to the folder the first time, they are fine. However, after a reboot, the icons of the apps installed to my microSD card that are in folders change to the generic Android green/white icon. The apps still load properly, and the icons appear fine in the App drawer.
*LauncherPro is included as the only homescreen in this ROM.
2) I'm having an odd issue with Plants vs. Zombies. It loads to the main screen, and I can manage the player names, but after I click to start the adventure, it locks up with the Adventure button depressed. The main screen music also dies. No FC/wait dialog appears. I have to press the Home button to get out of it. PvZ is unplayable in this condition. Rebooting does not help, nor does formatting /cache or Dalvik-cache in custom recovery.
3) JuiceDefender Ultimate tells me in the log that it cannot toggle 2G/3G data, and that this is likely to be a kernel issue. As far as I know, this reduces the effectiveness of JD.
4) In ClockwodMod Recovery 3.0.0.6, I cannot mount my microSD card for the PC to read/write it. I get "E:Unable to open ums lunfile (no such file or directory)". I've seen posts that indicate this is a bug that was corrected in later versions, but I don't know if the custom ROM I am running is compatible with later versions,or where to find later versions. EDIT: I found CWM 3.0.2.5, and flashed it. It still reports the same error when attempting mount my microSD card for my PC to work with.
5) When I connect the phone's cable to my PC and get the the "Charging/Mass Storage/Tethered" popup and click Mass Storage, and then click "Turn On" at the next screen, it appears to work fine, except that my PC shows no new removable media drives. Sometimes, even though I touched the "Turn On" button, nothing happens. The button does not turn into a spinning wait indicator, nothing.
6) I found a post (that I've since lost track of) that purported to provide instructions to see if journaling was enabled. (I'm already formatted as EXT4). The instructions errored out, apparently because I have the wrong version of tune2fs. I'm not sure how to copy the correct version over, so I flashed the "Journaling On" zip shortly after I re-flashed this ROM. Does EXT4 and journaling stick between ROM re-flashes?
Click to expand...
Click to collapse
OK can only answer some of these. I heard Launcher Pro can take a little while to read icons from the sd card. You may want to download and try Zeam launcher.
The Plants v Zombies may be a result of overclocking/undervolting. Try it again with no undervolting and your speed set to 1Ghz max and 200 Mhz min.
Not sure why you are mounting the sd card in clockwork. Sounds like either your cable is flaky or you need to reinstall the Samsung drivers to connect your USB. Also try different USB ports and turn USB debugging on. I had to reinstall the drivers for each port on my laptop as it would only recognize my phone in one of them originally.
No, journaling does not carry through other ROM flashes. If you flash a no-journaling ROM, you will have no journal unless you turn it back on. Some can be turned on simply be making a nand backup then immediately restoring it. Others work fine with the journal on flash. And some are more special and need a specific script like Bonsai.
Hope some of this helps.
SweetBearCub said:
Hi.
I'm running SyndicateROM Frozen 1.1.1, and I've observed several bugs. I need to know if the bugs are the fault of the ROM (and thus something I should take up with the ACS developers) or if they're my fault due to something I'm doing wrong.
1) I use folders on my LauncherPro* homescreens to organize apps. For this example, I'll use my Games folder. In it, all the games except 1 are installed onto my microSD card. After I drag the icons to the folder the first time, they are fine. However, after a reboot, the icons of the apps installed to my microSD card that are in folders change to the generic Android green/white icon. The apps still load properly, and the icons appear fine in the App drawer.
*LauncherPro is included as the only homescreen in this ROM.
2) I'm having an odd issue with Plants vs. Zombies. It loads to the main screen, and I can manage the player names, but after I click to start the adventure, it locks up with the Adventure button depressed. The main screen music also dies. No FC/wait dialog appears. I have to press the Home button to get out of it. PvZ is unplayable in this condition. Rebooting does not help, nor does formatting /cache or Dalvik-cache in custom recovery.
3) JuiceDefender Ultimate tells me in the log that it cannot toggle 2G/3G data, and that this is likely to be a kernel issue. As far as I know, this reduces the effectiveness of JD.
4) In ClockwodMod Recovery 3.0.0.6, I cannot mount my microSD card for the PC to read/write it. I get "E:Unable to open ums lunfile (no such file or directory)". I've seen posts that indicate this is a bug that was corrected in later versions, but I don't know if the custom ROM I am running is compatible with later versions,or where to find later versions. EDIT: I found CWM 3.0.2.5, and flashed it. It still reports the same error when attempting mount my microSD card for my PC to work with.
5) When I connect the phone's cable to my PC and get the the "Charging/Mass Storage/Tethered" popup and click Mass Storage, and then click "Turn On" at the next screen, it appears to work fine, except that my PC shows no new removable media drives. Sometimes, even though I touched the "Turn On" button, nothing happens. The button does not turn into a spinning wait indicator, nothing.
6) I found a post (that I've since lost track of) that purported to provide instructions to see if journaling was enabled. (I'm already formatted as EXT4). The instructions errored out, apparently because I have the wrong version of tune2fs. I'm not sure how to copy the correct version over, so I flashed the "Journaling On" zip shortly after I re-flashed this ROM. Does EXT4 and journaling stick between ROM re-flashes?
Click to expand...
Click to collapse
1) you can get a different launcher from the market. I've never had any luck with pushing apps to sd.
2) that's a issue with the game. Try changing your max and min cpu.clocks. If you uved you may be to low.
3)jd is a pos and you don't need it. I go on average of 12-16hrs a day with 3+ hours of screen on. And a synce interval of every hour
4) no versions of cwm on the epic has allowed you to mount your sd to pc for the epic. Cwm was ported to the epic and not created by koush him self so some things are broken.
5) try a different cable and usb ports. This is a known problem even while on a stock rom
6) yes it sticks unless the rom your flashing changes it.
Sent from my SPH-D700 using Tapatalk
Thanks Mystery for validating my advice...LOL. Would like to see you around here more.
cwm 3.1.0.1 allows mounting the sd card to pc in recovery..
chris41g said:
cwm 3.1.0.1 allows mounting the sd card to pc in recovery..
Click to expand...
Click to collapse
I forgot they fixed that. But anything before that don't allow this
Sent from my SPH-D700 using Tapatalk
kennyglass123 said:
Thanks Mystery for validating my advice...LOL. Would like to see you around here more.
Click to expand...
Click to collapse
I'm knee deep on working on sfr1.2
Sent from my SPH-D700 using Tapatalk

[Q] Guidance Appreciated

Hello Ladies and Gentlemen;
So I'm trying to run an android rom from an SD card, and I've tried a couple images-one froyo, one this: http://forum.xda-developers.com/showthread.php?t=1045018
I'm basically looking for reliability/speed, the ability to run FPSe and the ability to run word apps. It needs to run bluetooth and I'd like it to run most apps. Any suggestions? I would have gone for the CM7 nightly roms, but honestly I'm looking for something low maintenance and easy to setup. (The instructions/downloads on that thread were confusing.)
Thank you for any assistance.
Apoc
I recently went through rooting my NC from an SDcard. First with the nightlys and last with the 7.0.3 CM7 stable build.
I'd say, if you want low maintenance and quick setup, go with the CM7 7.0.3 Stable release.
Here are the steps I took to install CM7/GApps and run from the SDcard - I'll try to make this as seamless and possible: Sorry about the absence of links, I haven't reached the post limit to enable hyperlinking in my replies. Maybe some kind forum poster can post my links in a reply...
1. Download and Unzip this program to a directory (doesn't need installed)
Win32DiskImager V0.1:
2. Download your SDcard Image, CM7 Build, and GApps zip:
- "Size Agnostic" Generic SD-Image:
- Latest STABLE CM7 Release (not the nightly)
- GApps zip for latest build (CM7)
3. Buy a greater than 2gB MicroSD card (I have an 8GB PNY microSD)
4. Connect MicroSD card to computer
5. Extract Generic-sdcard-v1.3.img.zip to local folder
6. Burn generic-sdcard.img to SD card using the following steps
- Open win32diskimager
- Select generic-sdcard.img for image file
- Select microSD card drive letter for Device (should be auto selected)
- Click "Write" to write image to the microSD card
- After image is applied to microSD, close win32 disk imager
7. Remove microSD card and re-connect to computer
8. Copy CM7 and GApps .zip files to microSD drive
- This will be the main microSD drive, like I:\
- Do not extract the .zips, just copy the whole files
9. Remove microSD card and insert into TURNED OFF Nook Color
10. Hold power button on Nook Color until the screen flashes, then let go
11. Read the screen, it will bring up a terminal with installation progress... it will inflate the CM7 files to the SDcard, then shut off.
12. After shutdown, keep the SD in the nook, turn the nook back on.
13. You'll see an android pop up and finally get to some prompts
- Hit next, skip the part with linking your google account (for now)
- Enable Wireless and Connect to your Router
- Follow the rest of the prompts
- Eventually hit the home screen
14. Your CM7 install is done! If you turn off the NC, remove the SD card, and turn back on the NC... you'll be greeted with the stock V1.3 nook color
15. If you check the apps and don't see Google Apps (GApps) or the market follow these steps:
- While in CM7, hold the power button until a prompt comes up
- Click REBOOT
- Click RECOVERY
- Click OK
- Your NC will now restart and show that console setup again (like before when you installed CM7)... it will install the GApps and market... and shut down.
- Turn back on your NC, check your apps, see the Market, Click it, link your Google Account.
That should be it. Sorry for the long-winded install, thats about as basic as I can put it.
Cheers!
Swe
Thank you for the assistance. Your instructions proved a bit more enlightening. I used the latest stable version and have it working fine. (I even played FF7 for awhile.) My only current problem is bluetooth. It fails to enable when I tell it to.
Apoc52 said:
Thank you for the assistance. Your instructions proved a bit more enlightening. I used the latest stable version and have it working fine. (I even played FF7 for awhile.) My only current problem is bluetooth. It fails to enable when I tell it to.
Click to expand...
Click to collapse
I would go with the latest nightlies. They are *way* past the stable with a lot of very positive improvements. I've been running nightlies (starting with 128) for around 2 months now with zero issues. You don't have to keep updating them - they are very, very stable already.
Apoc52 said:
Thank you for the assistance. Your instructions proved a bit more enlightening. I used the latest stable version and have it working fine. (I even played FF7 for awhile.) My only current problem is bluetooth. It fails to enable when I tell it to.
Click to expand...
Click to collapse
Sometimes the first time you run bluetooth, you have to turn off WiFi, reboot, turn on bluetooth, and then turn on WiFi. I only had to do it once and both toggled properly forever after.
I'll second the recommendation of grabbing a nightly build--they're no higher maintenance or less stable than 7.0.3, and they greatly simplify things like overclocking, improving audio gain, and USB host via compatibility with the Nook Tweaks app. They also enable deep sleep which means less charging, boot considerably faster, and have built-in multiboot, to name a few things.

[Guide][24 Jan] Rooting |Sense | FAQ

I've seen a couple AOSP guides pop up recently... That's great, but there are some people like me who use Sense!
If you are looking for an AOSP guide, check out Arrow's and Crossrocker's guides, they are pretty impressive!
I am not responsible for bricks/mistakes, I am not perfect and neither are you... All of this works for me, I don't know why it wouldn't work for you, sorry, not responsible
Most of this is universal for any networks. Some stuff is not, like the Hands-Free Activation and PRL update and radio updates.
POST ONE IS FOR PEOPLE WHO HAVE 2.3.3. IF YOU HAVE 2.3.5, THEN MORE WORK IS REQUIRED AND I WILL WRITE A GUIDE FOR Y'ALL SOON
Let's start out first with rooting. Basically any phone now has Gingerbread, and the only method to root Gingerbread is with Revolutionary.io. I have never used this method, so feel free to tell me and I will add on.
Download HTC drivers here. Go to "Downloads" folder of your computer, double-click and run.
Download the Revoltionary file here and extract it to your desktop.
Open the folder and run the Revolutionary script.
Revolutionary will detect your phone's specific serial number. Use that to generate the beta key on the revolutionary website.
Enter the beta key in the Revolutionary terminal window on your computer. Copy and paste the key from the Revolutionary website to the terminal window to avoid any issues.
Let Revolutionary run.
You should now have S-Off.
Download Amon Ra here. When the download finishes, rename it to PC36IMG (the whole name should be PC36IMG.zip - most people have extension names hidden so name it PC36IMG). The thread is here
Turn on your phone, mount as disk drive and put it on the root of your SD card (not in folders).
Go into Settings - Applications - and uncheck Fast boot.
Turn phone off.
Hold volume-down and power button. This will take you to HBOOT.
HBOOT will look for files. It will detect the PC36IMG.zip. When it asks if you want to update, choose "Yes" by hitting volume-up. Let it do its thing, then it will ask if you want to reboot. "Yes" again.
You now have S-Off and a custom recovery. Let's get you the latest radios. I have had the best battery life with them so far. HAVE YOUR PHONE FULLY CHARGED.
Download time: All new radios are now in one "flashable" zip. Go to the Mik Mik here, and look under the RECOVERY Version for Baseband 2.15.00.12.19, PRI 2.33_003, WiMax 27243 & NV 2.15_003, or click here.
Plug up the phone to the computer. Mount as disk drive in dropdown menu.
Delete the PC36IMG.zip
Transfer the downloaded radio .zip to your phone.
Unmount in dropdown menu.
Turn phone off, get into HBOOT.
HBOOT will serarch for files. It won't find any. So use your volume keys to navigate to "Recovery" and select with power button.
Ah, recovery mode... the place to flash ROMs... let's go over some basic instructions. Navigate with volume keys, select with power button. You can also navigate up (with the home capacitive button) and down (with the menu capacitive button) and select (with the search capacitive button) and go back (with the back capacitive button).
USB-MS Toggle – This will connect your phone to your computer so you can edit/delete/modify files on your SD Card.
Backup/Restore – Create Nandroids (backups) here. You also restore from backups here.
Flash Zip From SD Card – Flash ROMs, kernels, themes and mods here. Obviously.
Wipe – The lifeblood of flashing ROMs, you need to properly wipe every time you flash something. I will explain later.
Partition SD Card – This allows advanced storage of cache, dalvik or data onto the SD card, giving you more space on the phone. This is extremely helpful with the newer, larger ROMs. Highly recommended, basically a requirement.
Navigate to Backup/Restore. Choose Nandroid backup.
Select boot, system, data, recovery, android.secure and wimax with volume keys and select Perform Backup. (Cache is not needed because there is no need to save temporary files).
This is your fully stock backup. Keep this safe. I keep mine on my computer.
Return to the main screen of recovery. Navigate to Wipe.
Select cache, it will wipe.
Select dalvik, it will wipe.
Return to main screen of recovery. Go to "Flash zip from sdcard".
Break time. This stuff coming up is very important. I am not responsible if you don't follow directions. DO NOT PULL BATTERY.
Select CM-EVO_Radio-2.15.00.12.19_PRI-2.33_WiMax_NV. Once it finishes, return to main screen of recovery. Select "Reboot system now".
Let the phone sit there. You should see the splash screen and then a box with a phone and green arrow. Let it sit there. This will reboot you to recovery.
Perfect. You now have the latest radios. Time to flash a custom ROM... And we are all here for custom ROMs, now aren't we?
See next post...
You should still be in recovery mode. Time to flash custom ROMs? Nope! First we shall partition your SD card. Before that, we are going to back up stuff on your SD card to the computer. Because partitioning your card will wipe it clean.
I am going to assume you have the stock 8 gigabyte card.
You should still be in recovery mode.
Plug up phone to your computer. Select "Mount as MS" in main menu of recovery.
Your computer should pop up with "Removable Disk".
Create a folder on your Desktop. Drag and drop files from Removable Disk to the folder on your desktop. You don't need those radio files anymore.
Is everything done transferring? Time to make the partition.
Select "Partition sdcard" in main menu, select Partition SD card.
Set swap size to 256 MB. Use volume keys to get to this number then select with power button.
Set EXT2 size as 1,024 MB.
Select to continue. Let it do its thing.
In "Partition sdcard" menu, choose SD: ext2 to ext3. Let it sit there.
DO NOT DO ext3 to ext4. DO NOT DO IT.
Your SD card is now partitioned. Excellent. Let's put everything back on your card... Almost time to start flashing...
Plug up phone to your computer. Select "Mount as MS" in main menu of recovery.
Your computer should pop up with "Removable Disk".
Remember where you stored all of your stuff earlier? Drag and drop files from folder to your phone again.
Unmount with power button.
FLASHING TIME!
Let's start out nice and smooth. Let's start out with a (mostly) stock rooted ROM .
I suggest Barebones, thread here. Find the download link in the OP for the odex one and download. Don't extract or anything
When the download is finished, mount as MS again. Transfer to your phone.
Transfer done? Unmount and navigate to the Wipe menu.
Wipe everything except for SD card. Twice. Believe me. Do it every time you flash a ROM.
Navigate to "Flash zip from sdcard" and find the Barebones .zip. Select with power button.
You are now flashing your first custom ROM, congratulations!
Let it sit there until it finishes. Then get back to the main menu and "Reboot system now".
Let your phone sit for a couple minutes. Skip sign-in. Let it sit on the homescreen for a couple minutes then reboot. Adjust all of your settings then reboot. Then feel free to do your set-up.
Let's get you some good data speeds. First, go to Settings - System Updates - and update PRL.Once that finishes, reboot.
Go to Market and get MSL Reader. Open the app. If it asks for "Superuser Privileges" then accept. It will tell you a 6-digit code. This code is unique to your phone. Write it down, but you can always get it again.
Go to Phone (Dial ##3282#, Choose edit mode) and enter your MSL code
select Data Profile
Hit the menu button and choose restore.
Just sit there, your phone should reboot. If it doesn't, then hold the power button and reboot.
Your phone should do "Hands-Free Provision". Once it says your phone has been provisioned, hit "Okay".
Once it starts to check for PRL update, hit cancel.
Turn on 4G, give it time to turn on (it doesn't need to connect)
Go to Phone (Dial ##3282#, Choose edit mode) and enter your MSL code. Select Advanced, scroll down to RTSP Proxy Port and HTTP PD Proxy Port. Click on them, set them to 0 (zero).
Set RTSP Proxy Address and HTTP PD Proxy Address to 0.0.0.0
Go back to the main menu of EPST and select Wimax
Find EntryRX and click on it
Change value from -89 to -110. Hit "Okay"
Hit the menu button and "Commit Changes" or "Commit Modifications". Your phone will reboot.
Go to Settings - System Updates - and Update Profile.
Once it finishes, reboot
You should now have about as good speeds as you can have on Sprint.
Feeling more adventurous? Let's try some different ROMs!
Next post...
This guide is about Sense ROMs, right? I've tried most of them all, but of course, choose whatever is best for you.
Suggested ROMs:
Sense 1.0: These are Evo 4G-based, based off of stock. We all know what stock software features are like, but there have been some additions like Quick Settings in the notification bar, small things mostly. Themed and tweaked and optimized, these are safe bets. My suggestion? The Evo Classic. Tommytomatoe is an amazing developer and puts out quality work. Plenty of themes available for it; my favorite is Supreme Classic. My second choice is Blazer Rom. Theme looks pretty sweet and runs smoothly.
Sense 2.1: This Sense version brought some major changes, like HTC Hub,Quick Settings, and a new camera. These are Evo Shift-based, nothing comes to mind that doesn't work. These are ports from different phones, so they were not designed for our phones. Basically everything is resized so it looks different. My suggestion? MikG. Aamikam has been around for quite some time, and has made some extremely popular ROMs. He constantly updates them, fixing and updating features. I don't have a second choice, because I love MikG.
Sense 3.0: This Sense version brought changes like the 3D animations, lockscreen, and Watch (movie app). These are mostly Evo 3D-based. Mostly everything works. Things that don't work is because our phone's hardware and drivers are outdated. Team Nocurnal's Shooter is an excellent bet. My experience with it has been positive, and Gruesomewolf has optimize it well. It does have 4G, and it is absolutely feature-filled.
Sense 3.5: The most recent Sense version, it brings several graphical improvements and integration with Facebook (and Beats - I can't really count this because it doesn't work correctly.) Mostly all of them are Sensation XL-based. NONE have 4G, because there is not a Sense 3.5 phone for Sprint yet. Along with the issues with Sense 3.0, these are fairly new, so not everything works. Issues are usually USB and graphics. My favorite is Radiance, it has yet to fail me and the Team Blaze devs are excellent with replying back. Second choice is Warm 2.3. Long-time Warm lover, and it runs quite smoothly.
Check out the threads, look at screenshots, find what you like and download it! Also, check to see if a new update is coming out soon, because you don't want to flash a ROM and an update is out within the hour....
Also, check out some themes. You can find them here for the most part. MAKE SURE IT IS COMPATIBLE WITH YOUR ROM.
When the download of whatever ROM you choose is finished, boot into recovery. Mount as MS again. Transfer to your phone.
Transfer done? Unmount and navigate to the Wipe menu.
Wipe everything except for SD card. Twice. Believe me. Do it every time you flash a ROM.
Navigate to "Flash zip from sdcard" and find whichever ROM you got. Select with power button.
Once it finishes, "Reboot system now" and your phone will boot up!
Let your phone sit for two to five minutes. Skip first set-up, let sit on homescreen for a two to five minutes. Reboot into recovery.
Wipe cache and dalvik twice.
Flash the theme (if you have one).
Once it finishes, "Reboot system now" and your phone will boot up!
Now adjust all of your settings and setup your phone.
Kernels! Don't know what a kernel is? The kernel is the main component of most computer operating systems; it is a bridge between applications and the actual data processing done at the hardware level. The kernel's responsibilities include managing the system's resources (the communication between hardware and software components).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Thanks to FAUX123 for the image)
Most Sense ROMs come with the stock HTC kernel. What's the advantage of running a custom kernel? Well, underclock/overclock, HAVS, Undervolting, SBC, different governors and cool stuff like that.
Let me explain a few things:
Underclocking/Overclocking - Overclocking is the process of operating the process at a higher clock rate (more clock cycles per second) than it was designed for or was specified by the manufacturer. Underclocking is running the processor at a lower clock rate than it was specified to operate at. It may be said to be the computer equivalent of driving a car below the speed limit. Usually, underclocking is used to reduce a computer's power consumption and heat emission, sometimes also to increase the system's stability and compatibility.
HAVS - Hybrid Adaptive Voltage Scaling. HAVS dynamically scales the voltage supplied to the CPU at any given speed, erring on the side of lowest power draw, in an effort to enhance power saving. This was causing issues in Gingerbread kernels so it was taken out and replaced with static undervolting.
Undervolting - Dynamic voltage scaling to increase voltage is known as overvolting; dynamic voltage scaling to decrease voltage is known as undervolting. Undervolting = good for battery.
SBC - Super Battery Charging. This is "trickle charging" and it only affects your phone while it is charging. It prevents the 10% drop that most users get when pulling the phone off the charger. It slowly continues to pump energy into your phone while it is charging so it does not lose its charge. No Gingerbread kernel has this thus far.
Governors: I borrowed basically all of this from the SetCPU website, so thanks to them!
Governors control exactly how the CPU scales between your “max” and “min” set frequencies.
ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point, ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
interactive – Available in newer kernels, and becoming the default scaling option in some official Android kernels. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
userspace – A method for controlling the CPU speed. Don't use it. It is pointless.
smartass – Included in some custom kernels. The smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
smartass v2 - a re-written smartass. Code is cleaned up, it scales more effectively and prefers lower frequencies.
InteractiveX - The interactive governor with suspend/wake logic so when the phone screen is off it runs at minimum set frequency. Also, modified code to minimize unnecessary cpu spikes
There are 5 custom Gingerbread Sense kernels that I know of:
Anthrax: my new favorite. A new kernel based on Qualcomm and Monster Audio (Beats) sources, it is amazingly smooth. Chad makes a highly-rated kernel for the Evo 3D, and I'm sure he can bring amazing things to the Evo. The thread is here, but it is shut down. Chad got a C&D and had to retract all of his work. If you seek this kernel, send me a PM. I myself am not distributing it, but I'll be sure that you get it.
ChopSuey is now my second choice. Compiled by barnacles10, the goal is "to be stable while implementing new features." It is ridiculously stable and I get very good battery life. Thread here
Freedom is my third favorite. Compiled by Lithid, it comes in various versions and degrees of undervolting. I always run Aggressive Freedom, the most undervolted. Thread here.
Golden Monkey. Compiled by netarchy, it hasn't been updated in a while, because netarchy has moved on to different phones. He always puts out quality work, so thread here.
PoonSense. Mostly stock with the usual tweaks of overclocking and governors. If someone could provide a link, that would be great.
Note: Latest ChopSuey, Freedom, and PoonSense have HDMIwIn if you are into that kind of thing (fullHDMI mirroring).
Let's assume you already have a ROM on your phone. How to flash:
Download the kernel you want, then transfer it to your phone in disk drive like we talked about earlier.
Boot into recovery.
Wipe cache and dalvik in Wipe menu. Twice.
Navigate to "Mounts" menu. Mount everything except for SDext.
Navigate to Flash zips from sdcard and find the kernel zip. Select with power button.
Reboot and enjoy!
You can also flash a kernel while you are flashing a ROM. Steps to do so:
Download whatever ROM and kernel you choose
Boot into recovery.
Plug up your phone to the computer, and mount as MS. Transfer to your phone.
Transfer done? Unmount and navigate to the Wipe menu.
Wipe everything except for SD card. Twice. Believe me. Do it every time you flash a ROM.
Navigate to "Flash zip from sdcard" and find whichever ROM you got. Select with power button.
Once the ROM has been flashed, reboot to system.
Let your phone sit for two to five minutes. Skip first set-up, let sit on homescreen for a two to five minutes. Reboot into recovery.
Wipe cache and dalvik twice.
Navigate to "Mounts" menu. Mount everything except for SDext.
Navigate to Flash zips from sdcard and find the kernel zip. Select with power button.
Reboot and enjoy!
Once you have your custom kernel, all you need to do is to choose the governor and min/max CPU frequency speeds.
My favorite governor is Smartass v2. If the kernel does not have smartass v2, then I use Interactive X.
My minimum and maximum speeds are 245/768 mHZ.
How do you set all of this stuff? Well...
Download No-Frills CPU Control (free) or SetCPU ($1.99) from the Market.
Open the application.
Drag the sliders to set your speeds!
Click the dropdown and select your governor!
Click "Set on Boot" and exit app.
Reboot phone!
Let's get something straight. Do not use "Profiles" in SetCPU or No-Frills. This makes the application run in the background and drains battery. Interactive X and smartass and smartass v2 already have built-in screen-off profiles. So do not make profiles, okay?
FAQ and helpful stuff
[Q] What order should I flash things in?
[A] Well, wipe everything except for SD card, twice. I flash the ROM first, then the theme, then the kernel (mounting everything properly), then any tweaks I may have. Works for me.
[Q] Which is the best ROM? What ROM would work best for me?
[A] What is the best flavor of ice cream? What works for me might not work for you. You may love a theme; I might not like it (I personally do not like all of the blue in themes). You have to experiment and try out different ROM types!
[Q] OMG MY PHONE KEEPS BOOTLOOPING! I CAN GET INTO BOOTLOADER BUT NOT RECOVERY!!! I THINK I BRICKED MY PHONE!!!!!!!!!!!!!
[A] No, your phone is not bricked. When a phone is "bricked" it does not turn on and is a nice expensive paperweight. If you can get into bootloader/HBOOT, you can be saved. There is something called an RUU. It is a package provided by HTC to completely wipe your phone and rewrite the software image.
Steps to run the RUU:
Download it from here. This is the most recent one.
Get into HBOOT.
Plug your phone into the computer and select "Fastboot" with power button.
Go to your downloads folder and double-click the RUU.
The directions that pop up are pretty self-explanatory.
[Q] My phone has a notification that there is an OTA update available. Maybe it's ICS! :O
[A] Do not accept OTAs. It is a general rule of thumb. You will lose root and there is a slight possibility you may brick your phone. Somebody will probably have it rooted and ready to flash within a day.
[Q]Will Vipermod or Incredicontrol work with Sense? It would be cool to adjust the level of undervolt!
[A]Nope, it won't work. None of the current GB Sense kernels have HAVS because it was simply problematic. It was implemented, and it didn't work very well so it was taken out. If you want to undervolt, then download one of Lithid's Freedom kernels that come in undervolted flavors.
[Q] Whenever I try to boot into recovery all I see is this....
[A] You do not have a custom recovery installed. See post one on how to flash a custom recovery (Amon Ra)!
[Q] My battery life has been dropping ridiculously. How can I calibrate my battery and get some more life?
[A] I follow a little guide that Hipkat wrote up here. I shall quote some for you....
HipKat said:
Charge your phone until full.
Unplug it, turn it off, then plug it in for one hour.
Turn it on for two minutes, so it fully boots.
Turn it off, unplug it, when the light goes off, plug it back in for one hour.
That part of this is actually from HTC, on how they found the best results for charging.
Now, before you plug it in, unplug, wait for the light to go off, plug it back in.
When the light turns green, unplug it again. Repeat that step 10 times.
(It may not take 10, it may take more, but 10 is good)
While plugged in, boot to recovery, wipe your battery stats.
Then reboot to system. Once it has booted to home screen, wait two minutes then unplug your phone.
Click to expand...
Click to collapse
I do this every time I flash a new ROM and kernel. Other things to help battery life are underclocking, turning auto-sync off, having GPS/WiFi/unused radios off. Do NOT use task killers. Ever since Froyo, Android has had a built-in one. Task killers just interfere with that.
Battery/Performance Tips and Thanks
Battery tips:
Sense is heavy, I know. But you can help stop the drain with a few things (I don't use any apps like Juice Defender).
Calibrate the battery.
Use Wi-Fi as much as possible. Just shut it off when you are done.
Shut off "Always-On Mobile Data" in Settings - Wireless - Mobile Networks.
Turn off "Quiet ring on pickup," "Pocket mode," "Flip for speaker," "Audible selections" and "Vibrate feedback" in Settings - Sounds.
Turn down the brightness and Screen timeout in Settings - Display. Also, turn off all animations.
Shut off GPS when not using it.
Unselect "Back up my settings" in Settings - Privacy.
Enable power saver in Settings - Power and Battery Efficiency in Quick Settings of notificaiton bar.
Turn off Auto-sync in Settings - Accounts and Sync.
Underclock.
Don't use task killers.
Theory: I use Chainfire3D and have their EGL drivers installed. Battery life has been better with them. Can't prove it, so I say theory.
How to improve performance:
Use C-O-D Tweaks. They did a plenty good job of explaining, so I won't explain. Takes away any reason for me to use a RAM script. Follow instructions to a 't' and you will be good.
Chainfire3D drivers work quite well for me, I can see the difference.
Don't underclock
.
I modify ROMs to fit my needs, usually by stripping out what I don't need. Here's what I do:
Download and install 7-Zip.
Download the ROM
Unzip the ROM using 7-Zip to a folder, usually named after the ROM. Example: unzip MikG to a folder called "MikG"
Delete whatever I don't need out of the folders, usually apps and pictures and ringtones.
After deleting to my heart's content, I right-click on everything and select "Add to xxxxx.zip". Example: "Add to MikG.zip"
7-Zip compresses and zips everything up, so transfer the custom zip you made to your SD card and flash (I don't sign my zips, I don't know why).
If something doesn't work, you deleted something you shouldn't have
Time to thank everyone.... long list....
Thanks to teh roxxorz and plainjane for answering some of the very first questions I had! They helped me start out, and they are so extremely helpful and patient.
Thanks to HipKat for the battery charging guide and answering some of my questions!
Thanks to Lithid for answering my development questions!
Thanks to AlphaRev and unrevoked for building revolutionary.io!
Thanks to Lithid and Barnacles and netarchy for your amazing kernels!
Thanks for TeamWin for HDMIwIn and PoonSense and all other work!
Thanks to Calkulin for basically making the Evo awesome!
Thanks to Amon_Ra for your incredible recovery!
Thanks to tommy tomatoe for your awesome Classic ROM and all of your themes!
Thanks to aamikam for your awesome ROMs and tweaks and optimizations!
Thanks to Team Nocturnal for Shooter!
Thanks to jaredthegreat and dropzeroc for RunnyBliss Hybrid and other cool ROMs!
Thanks to drellisdee for updating Amon Ra recovery!
Thanks to anyone who has helped me out and answered my stupid questions! I will add more to the list later!
This is a very very good guide. Keep it up.
Sent from my PC36100
Nice job, though you should throw kernels into one o our dibbed posts.
teh roxxorz said:
Nice job, though you should throw kernels into one o our dibbed posts.
Click to expand...
Click to collapse
Will do! I am going to go back and explain things, pros and cons, etc. And kernels, schedules and that sort of thing, but I'm out of town for a couple days with little internet access :/
Sent from my PC36100 using xda premium
tropicalbrit said:
Will do! I am going to go back and explain things, pros and cons, etc. And kernels, schedules and that sort of thing, but I'm out of town for a couple days with little internet access :/
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
No worries. I'm not a sense user, but still good info for those that do, and kernels are big part of the game. Do it when you get the chance.
Bumping this guide... I think I did a fairly good job
What else should I add?
tropicalbrit said:
Bumping this guide... I think I did a fairly good job
What else should I add?
Click to expand...
Click to collapse
System tuner is nice you can manage CPU speed n create a init.d script for ur CPU speed also v6 supercharger with mikg is nice..
Sent from my PC36100 using xda premium
pardon me im just trying to get 10 posts
---------- Post added at 11:23 PM ---------- Previous post was at 11:23 PM ----------
i believe i just got it with this one
Free Bump ^_^
geovanyglaude1 said:
pardon me im just trying to get 10 posts
---------- Post added at 11:23 PM ---------- Previous post was at 11:23 PM ----------
i believe i just got it with this one
Click to expand...
Click to collapse
Rude.
Sent from my calculator watch.
Do you have a British accent? I like to imitate the posters voice and read his posts aloud...
Sent from my PC36100 using XDA App
geovanyglaude1 said:
pardon me im just trying to get 10 posts
---------- Post added at 11:23 PM ---------- Previous post was at 11:23 PM ----------
i believe i just got it with this one
Click to expand...
Click to collapse
Thanks for reminding me, I will put some of the XDA rules and etiquette too!
Get to 10 posts by asking legitimate questions and learning.
Art2Fly said:
Do you have a British accent? I like to imitate the posters voice and read his posts aloud...
Click to expand...
Click to collapse
Not a legit accent, no. My bloodline is Puerto Rican and British, so that's where my name is from! Sorry to crush your dreams, I wish I were British too :/
ckoadiyn said:
System tuner is nice you can manage CPU speed n create a init.d script for ur CPU speed also v6 supercharger with mikg is nice..
Click to expand...
Click to collapse
I will look into System Tuner, I try to post information only about things I know how to do... V6 is pretty nice, haven't run it in a long time but I've seen a link to a good guide video around here so I shall look and post it!
Awesome guide! I got a question, do I need to partition my SD if I'm running Classic Sense 1.0 ROM?
Royalfox said:
Awesome guide! I got a question, do I need to partition my SD if I'm running Classic Sense 1.0 ROM?
Click to expand...
Click to collapse
You don't need to, but if you get any ROM bigger than that I would! Or you could just go ahead and partition it, save some time in the future
Sent from my PC36100 using xda premium
I wanna delete all the stuff and start like new when the new ROM's update I'm using comes out. How can I get rid of scripts? Or formating the SD card will solve all of my problems?
Sent from my Classic EVO

[GUIDE]HipKat’s Ultimate Guide To Everything Evo 4G.

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

[Q] Amatuer Noob needs help

I just got my NC and decided to give this a try instead of buying a N2A card.
Android Version 2.3.7
Kernel version 2.6.32.9
Mod Version CyanogenMod-7.1.0-encore
build Number GWK74
ClockworkMod 3.2.0.1
When I initially booted off the memory card everything was smooth until gapp. It loaded but when it came to selecting the apps when I clicked on one it flashed and just continued to set up. It didn't let me select any. No big deal because it worked fine.
I had force close issues so I ran Fix Permissions through ROM Manager and this seemed to help except for a few apps.
I used LCDDensity and changed that to 161 with Kill All which cleared up my force close issues on Words With Friends and Tweetcaster.
I get on today and notice videos are now missing from the market main screen and apps that I had yet to install are now no longer compatible with my device. They were last night but I was picking and choosing what I wanted on here. Why the sudden change? I rebooted the device just a few minutes ago and now the sudden change.
I also read about clearing davlik cache but how do you do this? I am not a programmer or developer so I have no clue. I have spent hours reading here everyday since Christmas and my mind is melting. I tried rebooting into recovery but I do not get the option to do anything. The penguin appears and a few things scroll down the screen and it reboots. I tried using the emulator and that won't work either unless I am typing something in wrong.
Are there any other tweaks or things I need to do to keep things stable and running smoothly? Are their certain things I need to clear regularly i.e. davlik cache, application cache or data?
I appreciate all the hard work and the time everyone puts into this. Please help. Like I said I need kindergarten instructions. Thank you.
First off, I've never had much success running from uSD. Even as far back as NookieFroyo. Once I made the move to running from eMMC most of my issues disappeared.
Davlik can be wiped from the Advanced selection when you boot to CWM as can Fix Permissions.
If you are going to run from SD then it is highly advisable to use a Sandisk Class 2 or 4 card. The brand does make a difference and others have found that other makes lead to slow downs and instabilities.
I would also recommend starting again following the veryGreen SD install method
http://forum.xda-developers.com/showthread.php?t=1000957
and using the MiRaGe KANG ROM.
http://forum.xda-developers.com/showthread.php?t=1344873
This is CM7 but with the latest improvements including kernel adding to stability and performance.
Also, never use Windows to format your uSD. The format utility in Windows can (and does) screw up the format. Use this freebie. Has always worked well for me. You would be surprised how many problems that involve uSDs are traced back to a bad format.
I used LCDDensity and changed that to 161
Click to expand...
Click to collapse
Setting to 161, you are asking for more issue.
Suggestion: set it back to 160.
skeeterpro said:
First off, I've never had much success running from uSD. Even as far back as NookieFroyo. Once I made the move to running from eMMC most of my issues disappeared.
Davlik can be wiped from the Advanced selection when you boot to CWM as can Fix Permissions.
Click to expand...
Click to collapse
How do I get to the Advance section and boot to CWM? When I try it through ROM Manager the device restarts with the penguin and after a few lines it says the system is ****ting down. It does not give me any menu options.
votinh said:
Setting to 161, you are asking for more issue.
Suggestion: set it back to 160.
Click to expand...
Click to collapse
I read that this was recommended and when I do it my apps that have issues work and they work well. No more force close issues.
Thanks for the advice guys. Like I said I have no experience with any of this. I am learning though and love to tinker with things and figure out how they work.
bobtidey said:
If you are going to run from SD then it is highly advisable to use a Sandisk Class 2 or 4 card. The brand does make a difference and others have found that other makes lead to slow downs and instabilities.
I would also recommend starting again following the veryGreen SD install method
http://forum.xda-developers.com/showthread.php?t=1000957
and using the MiRaGe KANG ROM.
http://forum.xda-developers.com/showthread.php?t=1344873
This is CM7 but with the latest improvements including kernel adding to stability and performance.
Click to expand...
Click to collapse
I did the veryGrenn SD install. Is there a link on how to install a new ROM. I read the link but I just do not understand it.
jsnake said:
I did the veryGrenn SD install. Is there a link on how to install a new ROM. I read the link but I just do not understand it.
Click to expand...
Click to collapse
To update the ROM on an SD card install power down, remove card then you put the card back onto the PC and copy the new ROM zip onto it but named as update-cm-*.zip. Put the card back in the Nook and power up with N button pressed until you see the screen flash. Choose reboot recovery and the new zip will be installed.
However, if you are doing a major ROM switch and haven't invested too much time installing apps etc yet then I would recommend just doing the VeryGreen install from the beginning to get a clean install.
I did a clean install and so far things are working well. Base off of the veryGreen install are there any "must have" settings or tweaks I need to do to keep things smooth? Any nook or CM7 apps you guys would recommend. I know it has been answered 50,000 times but I am losing sleep reading the forums here.
Thanks again for the help and your patience.
There are so many of apps that suitable for each individual personality, for me:
+ news: usatoday, bbc
+ sport: Y!spectacular, mobile sport
+ movie: flixter, moviefone
+ picture viewing: quickpic (must have)
+ time: clocksync (must have)
+ file navigate: file expert (must have), astro file manager
+ player: rockplayer
+ ebook: Mantano (recommended)
+ weather: fancy widget
+ web browser: Opera (like better), dophin HD
+ calculator: TI-83/86 emulators, also mortgage cal. and real science cal.
+ game: none
+ sex pos.: forget the name
+ few others that occasionally use.
Every one gets their own favorite apps to suit their interests. I personally go for ES file explorer for general file navigation and accessing my computers' shares wirelessly, Dolphin HD browser for the gesture navigation, moboplayer for playing media, and QuickPic for photo viewing.
But don't forget Nook Tweaks. This allows you to tweak the kernel and benefit from some of the good things in there that distinguish the Dalingrin CM7 kernel. Like overclocking to get a really good boost in performance (most people go for 1200MHz max for stability), undervolting to stretch the battery a bit, audio settings to make the stock feeble audio considerably louder (set DAC boost about 50%), and USB hosting if you want to connect USB peripherals.
jsnake said:
How do I get to the Advance section and boot to CWM? When I try it through ROM Manager the device restarts with the penguin and after a few lines it says the system is ****ting down. It does not give me any menu options.
Really? You are sure it's CWM 3.2.0.1? When you boot to recovery you don't get a Menu? If not, methinks your CWM is hosed. Have to say I do not ever recall not getting a CWM Menu. Nor can I call up seeing a "penguin"?
Have to say also ROM Manager is quirky at best. Used it a long time ago and found that it whacked my NC. Uninstalled and never used again. Found it was incompatible with other devices.
You might consider a new uSD install.
Click to expand...
Click to collapse
skeeterpro said:
Really? You are sure it's CWM 3.2.0.1? When you boot to recovery you don't get a Menu? If not, methinks your CWM is hosed. Have to say I do not ever recall not getting a CWM Menu. Nor can I call up seeing a "penguin"?
Have to say also ROM Manager is quirky at best. Used it a long time ago and found that it whacked my NC. Uninstalled and never used again. Found it was incompatible with other devices.
You might consider a new uSD install.
Click to expand...
Click to collapse
I'm not using SD CM7 currently myself but my recollection when I did is that the recovery is not a full clockwork but a stripped down one just designed to install update zips. As such you don't get the full menu and operation from ROM manager isn't going to work properly.
skeeterpro said:
Really? You are sure it's CWM 3.2.0.1? When you boot to recovery you don't get a Menu? If not, methinks your CWM is hosed. Have to say I do not ever recall not getting a CWM Menu. Nor can I call up seeing a "penguin"?
Have to say also ROM Manager is quirky at best. Used it a long time ago and found that it whacked my NC. Uninstalled and never used again. Found it was incompatible with other devices.
You might consider a new uSD install.
Click to expand...
Click to collapse
On this clean install I finally got it to work and there is no penguin. Just the menu that I should see so I finally cleared davlik cache.
I downloaded nook Tweaks as well.
jsnake said:
On this clean install I finally got it to work and there is no penguin. Just the menu that I should see so I finally cleared davlik cache.
I downloaded nook Tweaks as well.
Click to expand...
Click to collapse
Excellent! So all is well?
---------- Post added at 01:09 AM ---------- Previous post was at 01:09 AM ----------
bobtidey said:
I'm not using SD CM7 currently myself but my recollection when I did is that the recovery is not a full clockwork but a stripped down one just designed to install update zips. As such you don't get the full menu and operation from ROM manager isn't going to work properly.
Click to expand...
Click to collapse
Makes sense. Thanks for the clarification.
bobtidey said:
To update the ROM on an SD card install power down, remove card then you put the card back onto the PC and copy the new ROM zip onto it but named as update-cm-*.zip. Put the card back in the Nook and power up with N button pressed until you see the screen flash. Choose reboot recovery and the new zip will be installed.
However, if you are doing a major ROM switch and haven't invested too much time installing apps etc yet then I would recommend just doing the VeryGreen install from the beginning to get a clean install.
Click to expand...
Click to collapse
So I have done a clean install of veryGreen exactly as posted except that I have the latest stable instead of a nightly. So do I simply download that ROM file and do as you stated for MiRaGe Kang? Just asking because on that link there is a bunch of different things listed and I get kind of lost. All I need is the ROM file and follow what you said quoted above?
Thanks again.
I tried renaming the file but it says the name cannot contain * so what am I doing wrong. Searched the forums and can't find the answer.
jsnake said:
So I have done a clean install of veryGreen exactly as posted except that I have the latest stable instead of a nightly. So do I simply download that ROM file and do as you stated for MiRaGe Kang? Just asking because on that link there is a bunch of different things listed and I get kind of lost. All I need is the ROM file and follow what you said quoted above?
Thanks again.
I tried renaming the file but it says the name cannot contain * so what am I doing wrong. Searched the forums and can't find the answer.
Click to expand...
Click to collapse
The * is just shorthand for any name. You can't include * in the actual name as it is a wildcard character that matches any part of a name. The important part is that the new name starts with update-cm- so you can just put that on the front of the MiRaGe zip (which is all you need).
Thank you. I figured it out kind of. I downloaded that ROM and followed the instructions and rooted my nook which I did not want to do. I wanted to dual boot off the memory card. It is all a learning experience.
I did a factory restore and all was good again. Started fresh and was going for a new verygreen install and my memory card slot no longer locks the card in. I am so thankful I had completed the factory reinstall. My wife went to B&N today and exchanged it for me with no issue.
So for now I think I will stick to the verygreen install and tweak it to my liking until something stable for ICS comes about.
Thanks for your patience and help. Some really good people here helping out.

Categories

Resources