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
Related
This is a step by step guide to install ClockworkMod v08, a ROM of your choosing, Flash, and the Android Market fix. This guide assumes that there is no data on your device that is important to you. Back it up or prepare to lose it.
I do NOT accept responsibility for anything good, bad, or indifferent that may come from following this guide. This includes and is not limited to completely destroying your tablet. I highly recommend leaving your tablet plugged in while doing anything like this with your device. I have no idea what will happen if the battery dies in the middle of flashing a ROM (if anything…but better safe than sorry).
ALL THE FILES NEEDED FOR THIS GUIDE EXCEPT FOR THE ROM ITSELF CAN BE FOUND AT THE BOTTOM OF THIS GUIDE.
ROM XDA Pages (Look at these to pick what ROM you want to use.)
TnT Lite
VEGAn-Tab
CyanogenMod 7 (Gingerbread)
Notion Ink Adam ROM Port
You do NOT need to root your tablet to install a ROM on this device using this guide. All the after-market ROMs come pre-rooted so you don't need to root after installing either.
Part One – Install ClockworkMod v08
ClockworkMod is what will ultimately be used for all your flashing of ROMs, backing up, clearing cache, etc.
Step 1.
Download ClockworkMod v08 (This version has been found to work best...the newer version causes some issues with some ROMs.) There are two versions available; one for installing ClockworkMod from the internal memory, one for installing it from external memory (microSD/microSDHC card).
Step 2.
Unzip the file you chose (cwmod_internal.zip OR cwmod_microsd.zip) to the root folder on the storage option of your choice.
So, for example, if the storage option you chose has the drive letter “F:” assigned to it when hooked up to your computer, you would want it to look something like this…
A folder located at “F:\recovery”
A file located at “F:\update.zip”
Step 3.
Turn off your device.
Step 4.
Press the power button and the Volume+ button at the same time and release them when the Viewsonic splash screen pops up. You should see "Detect a recovery key pressed" pop up in the upper left corner of the screen.
Step 5.
Watch ClockworkMod install. This will not take long. Your tablet will reboot when installation is complete.
Step 6.
Enter ClockworkMod:
To get into ClockworkMod you need to shut down your device, then press the Power and Volume+ button (the same way you did to install ClockworkMod).
Navigating ClockworkMod: Vol+ and Vol- are to scroll up and down, the home button selects an option, and the back button backs up.
Step 7.
Re-Partition your Tablet:
In order to make sure the Android Market works correctly after installing any ROM, we must re-partition the device.
Select the advanced option at the bottom of the ClockworkMod menu, then go to “partition SD card”, for the first option select 2048, and for the second option select 0. This erases data on your tablet. Be prepared.
Part Two – Install a ROM.
A ROM (explained in very basic terms) is like Windows on your computer (assuming you’re not running Linux or Mac OS). Each ROM contains a customized version of Android that comes packaged with software, themes, and everything else you actually see when the device powers up. You install any additional apps you would like to use after installing the ROM. Beware, ROMs are device specific. You cannot reliably install ROMs designed for another device.
Step 1.
Now that your device is essentially empty, we need to be able to put files on it. ClockworkMod can do this for us. Connect your tablet’s USB cable from your tablet to your computer. Go to the ClockworkMod main menu, then navigate down to “mounts and storage”, and then select “mount USB storage”. The tablet’s internal storage will then be accessible from your computer. You will want to open it, and create a folder called “ROMs”.
Step 2.
Download whatever ROM you want to use. The links to the ROMs are located above. Click on the link to see what that ROM looks like. The most popular ROMs for this device are TnT Lite and VEGAn Tab.
Step 3.
Copy whatever ROM you wish to install (it should be a .zip file) to the ROMs folder on your tablet. (Leave it zipped, Clockwork will install it from the .zip file as is).
Note: If the ROM you downloaded has multiple files, look for the one named “update.zip” and rename it to whatever you want (something to help you differentiate it from other ROMs), then copy that to the tablet. If an “update.zip” doesn’t exist, and you’re lost…read through that ROM’s thread and see if anybody else asked about it…if not then you probably should (on that ROM’s thread…each one is different).
Step 4.
Turn off your device.
Step 5.
Boot into ClockworkMod. (Press the power button and the volume+ button at the same time until the Viewsonic splash screen pops up, release, then you should see “Detect a recovery key pressed”. After that it will think for a few seconds and then it should boot into ClockworkMod)
Step 6.
Stand up and do a dance. Sitting too long isn't good for you.
Step 7.
Back up to the main menu, then navigate down to “mounts and storage”. When that is highlighted press the home button to select it.
Step 8.
We want to mount “/system” and “/data”.
The goal is to see the following:
“unmount/system”
and,
“unmount/data”
If either one says “mount” instead of “unmount” you need to navigate to that line and press the home button to mount it.
Step 9.
This is the step that we actually flash the ROM in.
From the ClockworkMod main menu, navigate down to “install zip from sdcard” and press the home button to select that option at the menu.
Then, navigate to “choose zip from sdcard” and press the home button to select that option.
Navigate to the line that reads “ROMs” and press the home button to select that option.
Navigate to the line that reads whatever .zip file you wish to install and press the home button to select that option.
Navigate to the line that reads “Yes – Install yourzipfile.zip” and press the home button to select that option.
You will now see it do its thing. When complete you will see something along the lines of “install zip from sdcard complete” at the bottom of the screen.
Press the back arrow over and over again until you get to the Clockwork’s main menu.
Step 10.
Here is where we prepare the system to run the new ROM.
Navigate down to “mounts and storage”, select it, and mount “/system” and “/data” again as in steps 7 and 8.
Back up to Clockwork’s main menu.
Navigate to “wipe data/factory reset”, select it. Navigate down to “Yes – delete all user data”, and select it to wipe out user data and all the cache. (You need to do this for the new ROM to function correctly)
Now, navigate to the top option “reboot system now” and select it. Your tablet will now reboot. It may take up to 15 minutes to start up the first time as it rebuilds the user data and cache for this ROM.
If your tablet boots to UID errors, or has force closes (known to fix a few of them)…
Press and hold the power button to shut the device down. Boot back into Clockwork. Select the advanced option at the bottom, and then go to “Fix Permissions”. Afterwards, back out to the main menu, then select “reboot system now”. If that is unsuccessful then boot back into Clockwork and redo steps 7-10.
Part Three – Install Flash and fix Android Market
This is needed to view websites with Flash based content, and to download apps from the market. (Fairly obvious, I know, but just in case somebody doesn't know.) Log in/set up your Google Account before trying the market fix (steps vary on the ROM you are using…in most cases you can access the web accounts by opening the Contacts app, pressing the menu button (the one above the back button), and selecting accounts).
Step 1.
Download “Adobe Flash Player 10.1.120.1.apk” which you will find attached at the bottom of this post and save it on your tablet (I recommend creating a separate folder to save .apk files in).
Step 2.
On your tablet open up whatever file explorer comes pre-installed with the ROM you’ve selected. In there, open up where you saved your .apk, then select Adobe Flash Player, and follow the on screen instructions to finish installing that.
Step 3.
Open the Market app. Once it loads close it (press the home button).
Step 4.
Go into Settings - Applications - Manage Applications - Market - Clear CACHE - Force Stop
(For TnT/TnT Lite... Settings - Applications - System Applications)
Step 5.
Press back once - Google Services Framework - Clear DATA - Force Stop
Step 6.
Go back to your home screen and open up the market. You should get an error. If not, redo steps 4 and 5 until you do.
Step 7.
Reboot your device. After it starts back up let it sit for a minute or two to let things in the operating system normalize. Open the Market. Reboot your device.
Step 8.
Open the market again and enjoy. You should now have Flash and the Android Market.
This is the Titanium Backup method. Thanks to roebeet, xguntherc, and KorbenD.
http://forum.xda-developers.com/showthread.php?t=845175
Part Four – Show your appreciation! (First, be sure to play some Angry Birds)
I encourage everybody to take the time to send a kind message, or a small donation, to everybody that helped make this device what it is. This is not me saying "HEY HEY DONATE TO ME!!!!"...like some developers for other devices do. I just feel like the great ROM developers for this device don't get the credit they deserve, so please at least send them a quick thank you note. Keep in mind that ROMs, utilities, and yes (even guides), take a considerable amount of time to plan, compile, test, fix, and distribute.
With the following link you can donate as much or as little as you would like to me (even a dollar helps). Thanks and enjoy your tablet!
Donate Here
Thank You. This is exactly what we need. One thread with all the info consolidated into one will help many new users understand what to do. People otherwise may have come here and just been blown away by the different threads, I sure was when I first decided to Root my Eris.
scsione889 said:
This is a step by step guide to install ClockworkMod v08, TnT Lite 2.2, Flash, and get the Android Market working. This guide assumes that there is no data on your device that is important to you. Back it up or prepare to lose it.
...
Part Three – Install Flash and fix Android Market
Step 1.
Create a folder on your SD card called APKs. Download “Adobe Flash Player 10.1.120.1.apk” and "TitaniumBackup_latest.apk" which you will find attached at the bottom of this post and save them in that “APKs” folder on your SD card.
Step 2.
On your tablet open up “ES File Explorer”. In there, open up the “APKs” folder, then select Adobe Flash Player, and follow the on screen instructions to finish installing that. After that, select Titanium Backup in that same folder, and install the same way.
Step 3.
Go into Settings – Applications – Manage Applications - and Force Stop both the Market and Google Services Framework apps.
Step 4.
Open up Titanium Backup, go to Backup/Restore and look for Google Services Framework, select it, then select “Wipe Data”
Step 5.
Go back to your home screen and open up the market. You should get an error. If not, redo steps 3 and 4 until you do.
Step 6.
Reboot your device. After it starts back up let it sit for a minute or two to let things in the operating system normalize. Open the Market. Reboot your device.
Step 7.
Open the market again and enjoy. You now have Flash and the Android Market. (Keep in mind, this is not the FULL market, it just makes around 99% of it available. It is unknown which apps are not available. There is a full market fix, but it is MUCH more complicated).
Click to expand...
Click to collapse
Extremely Well Done!
Would be Nice to get this Stickied to keep easy for newbies to find...
Comment on Section 3... I simplified this by removing Steps 4 and 5 and modifying Step 3 to;
Step 3.
Go into Settings – Applications – Manage Applications - and Force Stop both the Market and Google Services Framework apps, [ADD] also 'Clear Data' on 'Google Services Framework' (after stopping it in same screen).
So removes the Need for TB in this proceedure, though TB is always something worth having...
Also I only needed the first reboot in Step 6, wait a few minutes then tried Market and all was fine! No multiple reboots needed for me at least...
Nicely done.
Can you explain in a little more detail why step 8 is needed?
I have already done everything in this post and my tab seems to be working great but never did anything like step 8. I did do the wipes in step 10 so just curious.
LTL11 said:
Nicely done.
Can you explain in a little more detail why step 8 is needed?
I have already done everything in this post and my tab seems to be working great but never did anything like step 8. I did do the wipes in step 10 so just curious.
Click to expand...
Click to collapse
This technically isn't needed for TnT Lite...but if people were to use this guide as guidelines for installing other ROMs (as I hope people would do...you know...following directions is good, but learning what your doing is GREAT), step 8 is something that is always good to get in the habit of doing before a flash.
With many other ROMs, on this device and others, not mounting /data and /system before flashing causes headaches.
jtbnet said:
Comment on Section 3... I simplified this by removing Steps 4 and 5 and modifying Step 3 to;
Step 3.
Go into Settings – Applications – Manage Applications - and Force Stop both the Market and Google Services Framework apps, [ADD] also 'Clear Data' on 'Google Services Framework' (after stopping it in same screen).
So removes the Need for TB in this proceedure, though TB is always something worth having...
Click to expand...
Click to collapse
I did it using 'Clear Data' as well...but this was my way of getting newbies to use TB (and to get more familiarized with side-loading apps). It's a great utility that I feel Android users should be familiar with.
Great guide, added clarifications
The only complication in following these instructions came when I could not locate my /sdcard2 folder using Clockworkmod. Once clockwork was installed using the removable SD card (as suggested), I moved all of my other files to the internal /sdcard folder, as it was the only one (easily?) discoverable. This guide was the only one useable for this android noob.
Tommunicator said:
The only complication in following these instructions came when I could not locate my /sdcard2 folder using Clockworkmod. Once clockwork was installed using the removable SD card (as suggested), I moved all of my other files to the internal /sdcard folder, as it was the only one (easily?) discoverable. This guide was the only one useable for this android noob.
Click to expand...
Click to collapse
Yes, it seems the clockwork version on this guide, does not redirect to SD2 for installs.
You must put them on the internal storage.
omnifox said:
Yes, it seems the clockwork version on this guide, does not redirect to SD2 for installs.
You must put them on the internal storage.
Click to expand...
Click to collapse
Sorry about this guys. Editing it now.
FIXED.
After I got tnt and market working I see the apps but I can't get any of them to download they all fail
thanks in advance
Kevin
kevin stone said:
After I got tnt and market working I see the apps but I can't get any of them to download they all fail
thanks in advance
Kevin
Click to expand...
Click to collapse
Does it display an error? Please be a little bit more specific. Did you try restarting the tablet (not just putting it into standby and bringing it back up)? Also, were you sure to force close the apps before clearing the data?
I did all these steps last night and everything seemed to work as expected. When I woke up this am and actually started to play with the Market, I realized that even though the Market looked good last night, all the important apps are gone this morning. I followed the instructions on the forms and on youtube videos and got the exact same results that were to be expected. I got all the errors and rebooted when asked and thought I was ok. When I opened Market after the Fix Process, all the same apps I would see on my HTC Evo are there. HOWEVER !! once I try to search or change the category to Apps or Games, or go to the sub catagorys 90% of the apps disappear. My app / game selection is now only 1 page long
When Market first opens up, I see Angry Birds and other apps I want, in the category description, but when I try to navigate to them, the screen simply says "loading" and never come up. It will stay that way for over an hour. The only thing I can do is change another catagory. When I do that, the loading text goes away and apps will show up, but alot are missing. Even the category description like for "Action Games" no longer lists Angry Birds in it. And if I try to search for an app I know is in the market like Advanced Task Killer... it says it can't be found.
I repeat the Market Fix process over and over and over again with the exact same results. Any Idea? Everything else seems to be working fine. Flash and Titanium Back up work perfect. Just can't get Market to show all the content.
I just picked up one of these and I'm trying to get this going, but when I mount it to the computer, it doesn't see my 2gb sd card.. The tab see's it fine, but not windows...
Any suggestions?
edit - Got it working... Although it may be getting returned later on. =\
You guys rock!
Picked up my GTab today @ Staples. 45 minutes later it's ready to go with TnT 2.2, full Market access and Flash using this guide! So far...so good!
Thanks for taking the time to write up this guide. Saved me from the slower-than-molasses-out-of-the-box-os-setup they shipped the tablet with.
Can't access Gtablet VIA USB cable from PC
I installed CWM 8, TNT lite 2.2 and performed market fix. Now my Gtab is working great. Prior to this thread I was stuck in a loop. My gtab is running great thanks a lot for posting this tutorial.
My only issue now is I can't access the internal SD from PC. Nothing shows up on my PC when I connect the USB cable to my Gtab. I have tried unmounting and mounting SD several times in CWM.
Prior to this update I was able to access and sideload APK's on my gtab running stock software with Viewsonic update.
any help would be greatly appreciated.
Wyngnut
Well after booting up a couple of times it just started to work (my Gtab showed showed the SD card option). I have downloaded several programs and they all install automatically and every one of then worked. No sideloading no additional steps for install this is amazing. I was coveting the windows 7 tabs on the horizon but the free programs available through the market are amazing and when they are Combined with the Gtab hardware its amazing.
Thanks again for posting this there is no way I would have tried to put this software on my system if I had not seen this guide.
Wyngnut
sano614 said:
I just picked up one of these and I'm trying to get this going, but when I mount it to the computer, it doesn't see my 2gb sd card.. The tab see's it fine, but not windows...
Any suggestions?
edit - Got it working... Although it may be getting returned later on. =\
Click to expand...
Click to collapse
The tablet doesn't seem to like giving the PC access to the microSD card. As far as I know this is a feature that is not available in any ROM. Also, it is my understanding that for this sort of thing to be possible we need to have the device's source code so we can make the hardware/software mesh better.
That is...unless I'm missing something very obvious...which is totally possible.
Thank you so much for taking the time to write this, worked perfectly for me
It's AMAZING!
Thanks to everyone on the site - from Roebeet and pals who pulled it together to scsione889 and others who did the walkthrough. For an absolute newbie (didn't know what "root" meant) to be able in one day to turn an absolute clunker into what I have now is unbelievable.
If you're new like me, and wondering whether you can pull it off, you can. Just make this the one time in your life when you read and follow the instructions exactly, without your usual improvisation!
Setting Up Data2Ext with RA 1.7 RecoveryI made this guide for my own personal future use and decided to share it with the community. I take no credit whatsoever for this information or the files used to install this mod on your phone. Credit for the guide goes to Laie1472 who spent several hours walking me through the process in the absence of good instructions for our device. If you don’t know what this mod does or could potentially do to/for your phone, don’t install it. Please read this entire guide before flashing or asking questions which may already have been answered. As the title states this is for users who have RA 1.7 Recovery installed. If you don’t have RA 1.7 recovery, you can find it here: http://forum.xda-developers.com/showpost.php?p=10531580&postcount=5
Now on with the guide:
Step 1. Back up your sd card to your computer as this process will format and partition your sd card.
Step 2. Reboot into recovery and select partition sd (this will wipe everything on your card). You will be given 3 prompts….swap, ext. 2, & Fat 32. Partition as follows:
Swap=0
Ext2=1024
Fat32=remainder
Step 3. Since the above step erased everything on your sd card, now would be a good time to do a nandroid backup.
Step 4. Download & place on the root of your sd, the data2ext2-v7.zip attached to this thread, but DO NOT FLASH IT YET.
Step 5. Decide whether or not you’re going to use your current rom or install a new rom (easier). If you’re going to use your current, you’re going to want to uninstall all of your apps & theme in order to utilize the additional memory you’ll be freeing up on your phone. If you’re going to use a new rom download it & the appropriate gapps and move them to the root of your sd.
Step 6. Boot into recovery, wipe, and flash your new rom & gapps. Boot into your rom and sign in, but don’t install any of your apps.
Step 7. Reboot back into recovery and flash the data2ext2-v7.zip
Step 8. Boot into your rom & open Terminal Emulator.
Type the following commands minus the ( )
su
mount|egrep mmcblk0p2
(this should return nothing but a #)
Now type:
mke2fs -m0 -b4096 /dev/block/mmcblk0p2
(let the scripts run….when they finish you’ll type the next line)
data2ext --enable
(You should now be prompted to reboot, so type)
Reboot
Step 9. Once you’re rebooted go to settings/storage. You should now see .94 GB or so of available space… Congratulations you’re almost done.
Step 10. The performance boost. Open Terminal Emulator again and type:
su
busybox mount -o remount,noatime,nodiratime, /mnt/asec/ext/ext2 /data
reboot
Step 11. You’re finished, but before you re-install your apps read the You Should Know section of this guide.
You Should Know:Now say you want to make a backup of your rom and you have data2ext enabled
do this
Boot into recovery and choose backup and restore. Then choose
create nandroid+ext back up
after it's done always flash the data2ext zip and reboot.
Say aosp/cm/whoever releases an updated rom and you want to update your rom and keep all your apps and theme and settings
Do this
Boot into recovery and make a nand+ext back up by following the steps above. "you don't have to if you already have good backup''
Now wipe cache and davlik-cache and flash then flash the rom update then flash the data2ext zip and reboot
Say you want to flash a new kernel with data2ext enabled
Do this
Boot into recovery wipe cache and davlik-cache. Then flash the kernel then flash the data2ext zip and reboot.
If you ever need to wipe cache or davlik-cache always flash the data2ext zip right after then reboot
PLEASE NEVER WIPE THE SD EXT unless your redoing the whole mod or just want to start fresh
AGAIN NEVER WIPE THE SD EXT
this will more that likely result in a boot loop and make all your once good nands useless
and you might have to reflash your recovery
Say you want to flash a sense rom to update prl/profile.
Do this
Boot into recovery wipe data,cache and davlik cache
then flash sense rom and update.
Then reboot back into recovery wipe data,cache and davlik-cache then choose which nand you want to restore after it's done restoring flash the data2ext zip and reboot
Always flash the data2ext zip after doing a nand restore.
Also with this mod it's not recommended to let your battery die or do a battery pull. If you do you might have to reflash your recovery and redo the whole mod over.
Also only shut down you phone with the rom options
apps like quick shutdown and hot reboot etc will not play nice with this mod. So only use the roms power options to shut down.
If you ever want to disable this mod, open Terminal Emulator and type:
su
data2ext --disable
Nice, I should add this to my links thread, you think?
il Duce said:
Nice, I should add this to my links thread, you think?
Click to expand...
Click to collapse
Go for it. Maybe it'll help someone besides me.
Sent from my HERO200 using XDA App
Need some help, I tried flashing data2ext2-v7.zip and this is what I get...
Code:
Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:No signature (10 files)
E:Verification failed
Installation aborted.
This was using the file in the OP with RA 1.7
Everything went fine, partitioned, wiped, fresh install of rom and gapps, rebooted, signed in, rebooted to recovery and then no go trying to flash data2ext
Any help would be great.
Try flashing this one. Let me know when you get it. Thanks.
Link sent via pm.
#Root/Hack-Mod_Always*
laie1472 said:
Try flashing this one. Let me know when you get it. Thanks.
Link sent via pm.
#Root/Hack-Mod_Always*
Click to expand...
Click to collapse
Thanks a bunch. Got it and worked perfect. Just have to do the performance boost (What does that do really?) then going to look at the S-Off thing. I have put that off for a long time but might as well go for it.
Thanks to both of you for the nice tutorial here and the help.
Pm sent. And no prob glad you got it worked out. Also recommend s-off via darch's method.
#Root/Hack-Mod_Always*
Installed and so far so good. Hopefully this works much better then apps2sd did. That made me just about want to smash my phone it was lagging so bad. lol
Hippie459MN said:
Thanks a bunch. Got it and worked perfect. Just have to do the performance boost (What does that do really?) then going to look at the S-Off thing. I have put that off for a long time but might as well go for it.
Thanks to both of you for the nice tutorial here and the help.
Click to expand...
Click to collapse
OP has been updated with the SIGNED version of Data2ext.zip. Sorry Hippie, I uploaded the unsigned version to the guide. Thanks Laie1472 for hooking him up, while I was asleep.
I'm really considering this mod right now but have a concern with the battery pull portion of it since I have a 14-month old daughter that sometimes thinks the phone is a toy. lol
Question: If I disable the mod will it automatically move all /data back onto the phone? Assuming of course I have enough internal memory for it to be moved over, will it transfer automatically?
Really good write-up, thanks for taking the time to do so.
hockeyfamily737 said:
OP has been updated with the SIGNED version of Data2ext.zip. Sorry Hippie, I uploaded the unsigned version to the guide. Thanks Laie1472 for hooking him up, while I was asleep.
Click to expand...
Click to collapse
No problem at all. Your guide worked perfect and turns out it was super easy.
I also am happy to be back RA Recovery. Was using Clockwork for a short while and while its nice, RA is much better I think. Thats just me though.
Got me a **** ton of space now and phone is moving right along again. Thanks again guys.
srkmagnus said:
I'm really considering this mod right now but have a concern with the battery pull portion of it since I have a 14-month old daughter that sometimes thinks the phone is a toy. lol
Question: If I disable the mod will it automatically move all /data back onto the phone? Assuming of course I have enough internal memory for it to be moved over, will it transfer automatically?
Really good write-up, thanks for taking the time to do so.
Click to expand...
Click to collapse
I've been using this mod for a couple of weeks now and have had to do a couple of battery pulls with no negative effects on my phone. There are obviously things that can go wrong, but no guarantees they will. I've enabled it, disabled it, gone back to a sense rom, updated my Orlando & gone back without trouble....but you wont know for sure how your phone responds until you try it.
Sent from my HERO200 using XDA App
Damn auto-correct......updated my PRL....not Orlando.
Sent from my HERO200 using XDA App
Thanks, Hockey. I'm going to give it a go and see how it goes for me. I know there are always risk and not all phones/experiences will be the same. Let's hope for the best
srkmagnus said:
Thanks, Hockey. I'm going to give it a go and see how it goes for me. I know there are always risk and not all phones/experiences will be the same. Let's hope for the best
Click to expand...
Click to collapse
No problem, just back everything up to your pc and do a nand backup before you start and you have nothing to lose and about 3/4 gb of storage to gain
At step 8 I get "/dev/block/mmcblk0p2 is apparently in use by the system; will not make a filesystem here!" when I input mke2fs -m0 -b4096 /dev/block/mmcblk0p2. The only deviation I made is I had to get a TE from the market since the one that comes with jaybob's rom won't accept numerical input.
Tibson said:
At step 8 I get "/dev/block/mmcblk0p2 is apparently in use by the system; will not make a filesystem here!" when I input mke2fs -m0 -b4096 /dev/block/mmcblk0p2. The only deviation I made is I had to get a TE from the market since the one that comes with jaybob's rom won't accept numerical input.
Click to expand...
Click to collapse
I've never run Jaybob's rom, so I'm not sure if this is a rom specific thing, because I have used it on Deck's Gingerbread, Aosp, & CM7. What did you get when you typed:
su
mount|egrep mmcblk0p2
That should have returned only: #
Also which terminal emulator did you get from the market (I use Android Terminal Emulator by Jack Palevich) and were you using the default gingerbread keyboard (as opposed to swype, slide it, etc.)?
Jo
hockeyfamily737 said:
I've never run Jaybob's rom, so I'm not sure if this is a rom specific thing, because I have used it on Deck's Gingerbread, Aosp, & CM7. What did you get when you typed:
su
mount|egrep mmcblk0p2
That should have returned only: #
Also which terminal emulator did you get from the market (I use Android Terminal Emulator by Jack Palevich) and were you using the default gingerbread keyboard (as opposed to swype, slide it, etc.)?
Click to expand...
Click to collapse
I was using the default GB keyboard, and I got the same TE from the market. When I typed mount|egrep mmcblk0p2 I get "/dev/block/mmcblk0p2 on /sd-ext type ext3 (rw,noatime,nodiratime,barrier=1,nodelalloc,data=writeback)" then it goes back to just #. I was burned out last night, now I can think again. Seems like maybe the ext partition is ext3 when it should be ext2? I'm using RA 1.7 and I followed the directions for partitioning the sdcard.
About a year ago I used apps to SD for a short while then stopped, is it possible that the ext part from then is still there and conflicting with the new partition from RA 1.7? I would have thought it would be wiped during the new partitioning. The only ext visible from TE is the new one, but that's all I can come up with.
I installed the setup last night without a hitch. Using Kushdeck's latest ROM and so far so good. Re-installed all my apps from Titanium Backup without a problem and everything going smooth. Once again, thanks for the detailed how-to and informative comments to update the ROM
I'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
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!
[REF] ★★★Understanding the Android world before rooting your LG Nexus 4★★★
Understanding the Android world before rooting your LG Nexus 4
Here is a *noob friendly* collection of information every user that wants to root their phone should know. Many people blindly follow guides without even knowing what "Rooting" means. Hopefully, this will help new users (and old ones, why not?) understand what is happening with their phone, and what they will put up with.
This may seem as a lot to read, but there are no shortcuts. You either read and learn what you're dealing with, or find out the hard way.
Let's get started, shall we?
What does rooting mean?
To 'root' your phone means to gain administrative rights on the file system of your phone (in linux, root is the username of the master admin, kind of being an Administrator on Windows). With root access, you can install and uninstall anything you want on the phone.
Most phones come with limited access regarding what you can and can't do on it. This isn't necessarily a bad thing, because it can keep users from accidentally breaking something they shouldn't mess with on the phone, especially in regards to the operating system. However, many manufacturers limit your rights to things that aren't really so mission critical, too, and rooting the phone gets around this.
If you have a few unnecessary applications (bloatware) pre-installed on your phone that you cannot uninstall, rooting will give you this ability. It will also allow you to upgrade to newer versions of Android before your phone's manufacturer and/or cell provider make the updates available to you.
Click to expand...
Click to collapse
So now you know what rooting means. And I bet you are now thinking "Should I do it, or not?" Well, hope this helps you decide:
The advantages of rooting
-De-bloat your phone. Uninstall any unwanted system apps.
-More control over how the CPU acts. This can increase performance or battery life, depends on how you configure it.
-More control over power consumption. This implies undervolting your CPU, giving it less power, so it consumes less.
-More control over how apps start up. Prevent apps from starting up when they don't need to.
-Change your Baseband (Radio). Try different radio versions, with the purpose of reducing battery drain or improving your signal strength. This may also allow you to enable LTE, due to the fact that it's disabled on the latest radios.
-Flash custom ROMs. Bored of the stock ROM and look? Browse through the hundreds of custom ROMs provided by this community, each having different features and looks.
-Backups. The ability to completely backup your phone, and fully restoring it to the time of the backup. This is done with a Nandroid Backup (we'll talk about this later)
-Mods and Inovations. Use many mods, fixes, tweaks or features created by the community!
-Custom Kernels. As a Nexus device, the Nexus 4 has tons of kernels with different features, supporting better performance, or battery life! To see what a kernel is, keep reading.
-Run apps that need Root Permission. These apps can be very useful, like Titanium Backup, Root Explorer, Terminal Emulator and many others!
Click to expand...
Click to collapse
The disadvantages of rooting
-Rooting will void your warranty (Although reverting root is very easy)
-The process a bit dangerous. Something could (99.9% probably not, but still) go wrong, and end up bricking your phone. So, yes, the process is 0.1% risky. You can end up deleting everything on your phone. You'll have to handle this process gently and with care.
-You will be able to do a lot more mistakes. These may cause damage to your phone (But hey, that's why we have these kind of threads, eh?)
-No more over the air official updates. You'll have to update your phone manually, through your recovery. (Which isn't that hard)
Click to expand...
Click to collapse
Now that you fully know what rooting implies, let's continue exploring the Android world.
What about the internal memory? How does that work?
Now, as you might already know, each phone has an internal memory. In the Nexus 4's case, it's either 8GB or 16GB. This internal memory needs to hold a lot of things, not only your personal data. This is why you only have available to use 5.8 GB or 12.9 GB.
An Android's internal memory is partitioned into many chunks that have their separate purposes.
These are all the Nexus 4's partitions, and their names.
modem -> /dev/block/mmcblk0p1
sbl1 -> /dev/block/mmcblk0p2
sbl2 -> /dev/block/mmcblk0p3
sbl3 -> /dev/block/mmcblk0p4
tz -> /dev/block/mmcblk0p5
boot -> /dev/block/mmcblk0p6
recovery -> /dev/block/mmcblk0p7
m9kefs1 -> /dev/block/mmcblk0p8
m9kefs2 -> /dev/block/mmcblk0p9
m9kefs3 -> /dev/block/mmcblk0p10
rpm -> /dev/block/mmcblk0p11
aboot -> /dev/block/mmcblk0p12
sbl2b -> /dev/block/mmcblk0p13
sbl3b -> /dev/block/mmcblk0p14
abootb -> /dev/block/mmcblk0p15
rpmb -> /dev/block/mmcblk0p16
tzb -> /dev/block/mmcblk0p17
metadata -> /dev/block/mmcblk0p18
misc -> /dev/block/mmcblk0p19
persist -> /dev/block/mmcblk0p20
system -> /dev/block/mmcblk0p21
cache -> /dev/block/mmcblk0p22
userdata -> /dev/block/mmcblk0p23
DDR -> /dev/block/mmcblk0p24
grow -> /dev/block/mmcblk0p25
Yes, there are quite a lot. You, as a user, don't need to care about all of them. Here are the ones you will need to know about:
/system- size: about 0.5GB
This partition holds the Android OS itself. Kind of like the C:// disk on your every day Windows PC. This partition has many folders and files you cannot normally get to, due to safety reasons. For example, system/app is where all the system apps are installed.
If something gets deleted from this partition, Android will most probably won't work properly.
/data- size: either 5.8GB, or 12.9GB
This is where all your personal data is kept. This includes apps, sms, contacts, e-mails etc. It also stores your system settings, like wallpaper, and all those stuff you set up when you got your phone. The most important folders on this partition are data/app (where your apps are stored), data/data (where you app data is stored, like highscores and stuff), and data/media.
Data/media might be considered your sd-card. Yes, I know the Nexus 4 doesn't have an sd-card, but this folder works like one. When you connect your phone to your PC, this is the folder that pops up, with all your music, images, videos, and whatever else you keep on your phone.
Click to expand...
Click to collapse
Things are getting a bit more complicated, eh? Just bare with me. Next, I will be explaining the different terms you will be encountering throughout your Android experience.
Things you hear people talk about
Kernel
The kernel is an essential part of any Linux based operating system. It's the program that manages input and output requests of the operating system. Imagine you're at a restaurant. You give your order to a waiter. He takes it to the chef, the chef makes your food, then the waiter brings it back to you, and you enjoy it. In this case, you are the Android system, the waiter is the Kernel, and the chef is the hardware. The system gives the Kernel a request, like firing up another processor core when you play a heavy game, and the Kernel fulfills the request.
Here is an image for better understanding
{
"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"
}
Recovery
This is a secondary, mini operating system that has access to your internal memory. It contains a few commands that would normally help you recover your Android system in case of a failure, like factory resetting. You will see that, for rooting, you will need to install a custom recovery.
The stock recovery does not have the ability to write custom ROMs (I'll explain these later) on your internal memory. A custom recovery has this option, and many more.
Here are some images for you to fully understand:
Stock recovery:
Custom Recovery
You can see that the Custom Recovery has more options, including "Backup and Restore", Advanced, and Install zip from Sd-card.
You can get in Recovery by powering off your phone, then hold Power+Volume Down button until a black screen with colored text appears. Then, use the volume buttons to select 'Recovery", and then press the Power Button to select it.
Bootloader
The bootloader is the first thing that fires up when you open your phone. As the name says (Boot+Loader), this program loads the kernel, which when boots up the Android system.
The same bootloader can also boot in recovery, as explained above.
When you first get the phone, the bootloader is in a locked state. That means that you cannot use fastboot commands like "fastboot flash" or "fastboot boot". With other words, you cannot simply flash a custom recovery. Thankfully, Google gave us the option to unlock the bootloader very easily, and flash a custom recovery of our choice.
Custom ROMs
A custom ROM is a ZIP file that contains an altered version of the Android OS. There are many custom ROMs for the Nexus 4, made by wonderful and skilled devs for the community. You can install a Custom ROM with your Custom Recovery. Custom ROMs contain the following folders and files:
META-INF- This folder holds the installation info and data. A custom recovery does not know on it's own how to install a ROM. In this folder, there's a txt file that contains a script, with the purpose of telling the recovery what to do.
System- This folder contains the stuff that will be installed on the /system partition that we talked earlier about.
boot.img- Among others, this file contains the kernel that comes with the ROM.
Click to expand...
Click to collapse
Ok, so now, after you read all this stuff, you're probably thinking "Ok, I will never get the hang of this". Don't worry. With time, you will know all of these from reflex. And, after you got over that, and manned up again, you probably thought "Ok, let's root this damn thing!". Not quite yet. We aren't done. There are still some crucial things that you need to know. So let's continue.
How to backup your stuff
Before you do anything EVER, you'll always have to backup your stuff, even if you don't feel like it, or your dog died (in which case I'm truly sorry), but, no matter what you're about to do, always have a recent backup sitting around.
There are many ways and things you can and will probably have to backup.
1. Backup your entire phone, by creating a Nandroid Backup.
As you saw in the 'Custom Recovery" picture above, you have a "Backup and Restore" option. Here it is again:
With every occasion, it's best to use it as often as possible. It only takes about 2 minutes, but it could be a life saver.
A Nandroid will backup:
/system
/data (Except /data/media, where your "sd-card" is, because it's too large and not that important)
/cache (Yes, there is a cache partition, and it will be backed up, although not really necesarry)
kernel (The kernel will be backed up too)
***Optional tip: I always keep a recent nandroid backup on my PC, in case I somehow wipe all my phone's contents, and my backup among with them. The Nandroid backup is saved at this location, which can be accest with a root file explorer, like ES File Explorer : mnt/shell/emulated/clockworkmod/backup. If you want to copy it to your storage, just copy the latest backup, and then move it to your PC.
2. Your apps and data only
This can be very useful when changing ROMs. You just got bored of your ROM, and want to move to another one. The only way of taking your apps and data with you is by backing them up with an application like Titanium Backup. The backups will be saved in data/media, and will be restored using the same app with which you backup up on the new ROM.
3. Your SMS, Contacts, MMS etc.
These things can be backed up by special apps on the Play Store. Ok, contacts will be restored by Google Sync ( although not always done properly, that's why I still back them up), but SMS will not be restored. There are many free apps that back them up for you, nice an easily, for them to be restored in case of a ROM change or data loss.
4. Your storage (data/media, sd-card)
You just connect your phone to your PC, select all folders, and copy all over on your PC. This will be useful when you unlock the bootloader. A bootloader unlock will wipe all the stuff on your phone (This can be avoided, read guides). So keeping a copy of your sd-card contents on your PC isn't such a bad idea.
Click to expand...
Click to collapse
Now you know how to keep it safe by creating backups. I will say it again, you are never too safe! Backup when you do a modification, even if it's tiny. Now, after you've finished reading the above, you will probably attempt to root. You will use one of the guides out there ( I will link one at the end of this thread ) to install a custom recovery, and gain root access. But what to do with it? Well, you will most likely end up flashing a custom ROM.
Flashing a custom ROM
You will get bored of the stock ROM, and will decide to flash a custom ROM. But you haven't done it before, and you don't really understand the process.Before you do anything, you must:
-Make sure that the files are for your phone ! If you flash files that were made for another phone, you might end up with a brick!
-Never panic! There is always a way out! That's what backups are for!
-Read all the instructions! Every ROM thread has instructions. Read them!
{By the way, flashing = installing}
Now, let me take you through the whole flashing process. ( Use the steps in the ROM threads if instructed differently than here )
1. You will search far and wide in these forums for a custom ROM that fits your needs. Every ROM comes as a ZIP file. So when you decide on a ROM, download the zip. For copyright reasons, Google Apps (Play Store, Google Now etc) don't come included with the ROM. So you will have to download them too. They are usually linked on the ROM main thread.
Some ROMs might have addons too, so check them out, and download the ones you want.
2. You now downloaded the ROM, Google Apps, and some addons. The next step will be to put them on your sd-card. Connect your phone to your PC, and make an easy access folder, like "Root Stuffs" where you'll put all these zips.
3. Now, let the backup process begin. You first backup your apps, app data , SMS, Contacts etc., like I explained above. I recommend Titanium Backup for apps and SMS, MC Backup for contacts.
4. Now you are ready to go in recovery. Power down your phone. Then, press and hold the Power Button and the Volume Down button at the same time. You will be brought to the Bootloader Screen. Now, with the Volume Buttons, switch through the options until you find "Recovery". Then press the Power Button again.
5. Now you will be booted in your Custom Recovery. Depending on your recovery, you will have the options on your screen.
CWM Recovery:
6. You will go to the Backup and Restore menu, and select "Backup". If you made a backup before, you can select "Delete" first, and delete it, for space consumption purposes.
7. After the backup finished, you will return to the main screen. There, select 'Wipe data/ Factory Reset". This will wipe everything in /data except /media, so your sd-card will remain untouched. Don't worry, you have a Nandroid Backup!
8. After the wipe finished, you will go to "Install zip from sd-card". You'll have to navigate to the folder where you put the ROM, and select it. You'll see it will nicely install.
9. After the ROM finished installing, you will have to flash the Google Apps zip, and the mods. Install them the same way you installed the ROM itself.
10. After you have flashed everything, you can select "Reboot system now" . First boot will take longer to complete. Again, don't panic. You have a Nandoid bakcup . You will end up with the ROM booted, and you'll continue setting it up.
TWRP Recovery:
6. Go to the "Backup" menu, select "Boot", "System", and "Data", then swipe the thing on the bottom on the screen to start backing up.
7. Once you're done, use the home button to get to the main screen. Select "Wipe", and swipe the thing again to Factory Data Reset. This will wipe data, cache and dalvik cache. This will not wipe your internal storage (Music, photos, etc).
8. After the wipe finished, use the home button again to get to the main screen. From there, select the 'Install" option. You'll have to navigate to the folder where you put the ROM, and select it. Then, by using the "Add more zips" option, add the Gapps package, and and then any addons or mods, in this order. Then swipe the bottom thing to flash.
9. After you have flashed everything, you can select "Reboot" . First boot will take longer to complete. Again, don't panic. You have a Nandoid bakcup . You will end up with the ROM booted, and you'll continue setting it up.
***In case something went bad, like your phone doesn't boot for more than 10 minutes, or the animation endlessly repeats itself (Boot Loop), do the following:
11*. Hold down the Power +Volume Buttons until the phone shuts down. Then release them for a second, and immediately press them again. You will be brought to the bootloader screen. Enter recovery.
12*. In recovery, go to the "Backup and Restore" menu, and select "Restore". Then pick the backup you did earlier, and wait for it to complete. Then, select "Reboot system now", and you should be booted back in your original ROM.
Now, let's say that after you flashed a ROM, it either did not boot, or you had some bugs with it. You will go to the thread ROM to report your problem. Here's how to not post:
"This ROM doesn't work"
You will have to be a lot more specific than that. In reporting a problem, you will have to do the following:
-Say what you did (Flashing process)
-What you flashed afterwards
-What you did to reproduce the bug
-What recovery you use
-ROM Version
-even provide a logcat <This is quite advanced> (http://forum.xda-developers.com/showthread.php?t=1726238)
You have to give as many details as possible, so the developer can sort things out.
Click to expand...
Click to collapse
ADB and Fastboot
ADB (Android Debug Bridge)
The Android Debugging Bridge is kind of a toolkit, that has many commands to control your Android from your PC. This is an essential part of your Android experience. With ADB, you can do many stuff that you couldn't normally do, like backup your apps, or push and pull packages from your phone.
ADB is also used by many of the useful tools out there, like toolkits, and all sort of programs that enhance your Android experience.
With ADB, you can also Logcat. Logcatting is creating a log of everything that happens on your Android phone while it's on. This is used to find the sources of bugs.
Example of ADB Commands:
Code:
adb pull /system/app/RANDOM APP = creates a copy of a system app on your PC
adb push app /system/app = Copies an app from your PC to your system partition
adb reboot bootloader/recovery = Reboots the phone in bootloader or recovery
adb logcat = Starts a logcat
Fastboot
Fastboot is also a toolkit of commands, but a bit different from ADB. While with ADB, you can do simple actions, with fastboot, you can do major ones, like flashing a whole partition, or formatting one. Fastboot is usually the preferred method to flash a recovery. Also, Fastboot usually works with .img files.
Example of Fastboot commands:
Code:
fastboot erase boot = Erases the kernel
fastboot erase recovery = Erases the recovery
fastboot flash system system.img = Flashes the System partition with an image
fastboot flash boot boot.img = Flashes kernel
fastboot flash userdata data.img = Flashes Data partition
fastboot flash recovery recovery.img = Flashes a new recovery
fastboot reboot = Reboots the phone
To use ADB and Fastboot, you must first have ADB drivers and Fastboot drivers installed. Here is a very good guide to set up these two useful things:
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Click to expand...
Click to collapse
Tips and Tricks
1. Try to not use toolkits. (I'm not disregarding any toolkit dev. They did a wonderful job)
Due to the fact that people are lazy in nature , toolkits have been made so that users don't struggle with rooting their phone. But there are many reasons for you to not use one:
-->you won't learn anything from using a toolkit, and, if something goes wrong, a toolkit can rarely fix your problem. It's better if you rely on your own forces.
-->you put the fate of your phone in someone else's hands. If a bit of code is wrong, then your phone could get bricked.
-->you miss out all the fun. Why buy a Nexus device if you don't want to explore the depths of the Android OS?
2. Never panic
Whenever you don't know what to do, and you're stuck, don't panic. There are many people here that can help you. Don't try doing anything blindly. Search the forums, or start a thread in the Q&As section, and we will help you.
3. Read everything carefully!! (If you read this, post a cat picture in this thread)
I might have said it a couple of times throuout this post, but always read everything. Someone wrote something for a reason. Usually, if you read everything, and do what you are told, you are bound to be failproof.
Click to expand...
Click to collapse
Ok, so now you know pretty much all a normal user should know. But there are still questions that are very frequently asked that need answering. Here are some questions and answers about popular problems and misconceptions:
Questions and Misconceptions
1. My Nexus 4 is getting very hot. Hardware problem?
Nope. There are many reasons that contribute to your phone getting hot, like
-the fact that glass is a good heat conductor, and the Nexus is covered in it
-the fact that a quad core produces more heat
-etc.
Don't worry. Everything is working as it should. For example, the Ipad gets 3 times hotter than the Nexus.
2. If I am rooted, will I receive OTA updates?
Yes, and no.
You will be able to download the update by having installed the Stock ROM with stock kernel, though it will not be installed automatically, due to the fact that you have a custom recovery. You will need to install it manually.
3. My notifications are delayed. Why?
Well, it due to the fact that Android is doing too much filtering.
To fix, navigate to /system/etc/wifi, and open WCNSS_qcom_cfg.ini. Now find the line McastBcastFilter=3. Change the value to 1, like this: McastBcastFilter=1, save, and exit. Then reboot. Your notifications should not be delayed anymore.
4. The Nexus 4 audio quality is horrible. Why?
It isn't horrible. It's normal, but the max volume isn't as loud as on other devices. I have been a piano player for 12 years. I have quite a sensitive ear, and I can tell you that the audio quality on the Nexus is comparable with that of an Ipod. The only major difference is that, with the Ipod, you can go deaf with the max volume.
5. Which kernel/ ROM should I use?
Don't ever ask this question. What's good for others isn't necessarily good for you. You'll have to try the many kernels and ROMs yourself.
6. My Nexus 4 rattles when I shake it. Why? Something broken?
Nope. There's nothing broken. That rattling is caused my the camera lenses moving. Don't worry about that either.
Click to expand...
Click to collapse
This is all for now. I hope you understand what's up with this Rooting process. If you have any questions, don't be shy to ask in this thread
If there is anything to be added to this thread, please post below
Thank you for the time you allocated to reading this! You are now smarter :good:
Good day, and Happy flashing!!!
For credits, useful links and other stuff, see the posts below.
Useful links
INDEX of Guides, Tools, Recoveries and more... (By GaboWinter)
Unlocking Bootloader without wiping data
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
Ultimate Nexus 4 Root Guide
Credits and Thanks!!
@rootSU
For providing me a template and much of the info. His original thread in the S3 forums: (http://forum.xda-developers.com/showthread.php?t=2362743)
@mskip
For providing information on memory partitions
@paxChristos
For the logcat part
@efrant
For pointing out some mistakes
My annoying cat
For continually stepping on my keyboard.
Thanks for this awesome guide!
ngr.hd said:
Thanks go this awesome guide!
Click to expand...
Click to collapse
Thanks!! No problem. My girlfriend left me, so I have plenty of free time now
abaaaabbbb63 said:
Thanks!! No problem. My girlfriend left me, so I have plenty of free time now
Click to expand...
Click to collapse
O god Nice guide, will be helpful. One thing though:
4. Now you are ready to go in recovery. Power down your phone. Then, press and hold the Power Button and both the Up and Down Volume button at the same time. You will be brought to the Bootloader Screen. Now, with the Volume Buttons, switch through the options until you find "Recovery". Then press the Power Button again.
Click to expand...
Click to collapse
The bootloader can be accessed using just volume down and power. I never have to use both volume buttons.
chromium96 said:
The bootloader can be accessed using just volume down and power. I never have to use both volume buttons.
Click to expand...
Click to collapse
One learns new things every day...
This thread should be stickied IMO.
ohersi intriguing
this thread helped me A LOT!!!
got my Nexus yesterday, and i'm happy that such a thread exists.
@ApriliaM3
U should really consider making this a sticky
Hello!
I bought my Nexus last week, and I kept looking on the internet they can do with it. I've heard of the root, and I was curious. I also found it very interesting forum where I found this thread. Thanks for the information. Very useful.
Sorry for bad English. I used Google Translate.
i JUST realized this was here.. DOH!
THANK YOU
Nexus 4 doubts
Hii i just got a 16gb nexus 4 which is my first android phone last month and now i was thinking of rooting it and getting paranoid android on it...but just wanted to get some doubts clarified...
1. I wont be able to install ota updates when 4.3 or 5.0 android versions are released , so how will i get them ?? By Updating paranoid android ROM ??
2. In case i just root my phone and not install any custom ROMs then will i get otas ??
3. After installing a custom rom , can i revert back to the stock google thing ? I mean make my phone as it was when i first booted it.. ??
Thats all i guess..
Nice guide Andu! :thumbup:
Sent from my Nexus 4 using Tapatalk 2
simms22 said:
i JUST realized this was here.. DOH!
THANK YOU
Click to expand...
Click to collapse
No problem
gamekid94 said:
Hii i just got a 16gb nexus 4 which is my first android phone last month and now i was thinking of rooting it and getting paranoid android on it...but just wanted to get some doubts clarified...
1. I wont be able to install ota updates when 4.3 or 5.0 android versions are released , so how will i get them ?? By Updating paranoid android ROM ??
2. In case i just root my phone and not install any custom ROMs then will i get otas ??
3. After installing a custom rom , can i revert back to the stock google thing ? I mean make my phone as it was when i first booted it.. ??
Thats all i guess..
Click to expand...
Click to collapse
1. Yeah. Paranoid will most probably be updated to the latest android as soon as the source is released.
2. Yes, you will get OTAs, but you will have to install them manually.
3. Yes you can. You can either do a nandroid backup of your stock rom, and keep it, or you can flash a stock rom.
xanthrax said:
Nice guide Andu! :thumbup:
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Thanks!
Added Fastboot and ADB
If I made any mistakes, please correct me
abaaaabbbb63 said:
Added Fastboot and ADB
If I made any mistakes, please correct me
Click to expand...
Click to collapse
Ha. I was considering adb
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
Ha. I was considering adb
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Nice!
I really like how you styled your thread! Looks awesome!
is there a link you'd recommend to get all google apps and any other important apps
and Thnx for the great guide, really helped me ALOT
M.Zaki said:
is there a link you'd recommend to get all google apps and any other important apps
and Thnx for the great guide, really helped me ALOT
Click to expand...
Click to collapse
Google apps are usually linked in the ROM thread.
Here are the JB 4.2.2 gapps:
http://goo.im/gapps/gapps-jb-20130301-signed.zip
Its worth noting that some roms have specific gapps packages too. Its always good to use these dedicated packages in case they have cool optimisations (eg slim with the dark mode toggles)
Sent from my GT-I9300 using Tapatalk 4 Beta