Related
Found this thread on the HTC Hero section for it's open GL will this work for our wildfire?
http://forum.xda-developers.com/showthread.php?t=899801
Yea I flashed it, noticed an improvement in playing angry birds...i think.
Sent from my HTC Wildfire using XDA App
Will it work on cm7 nightlies kevin?
Sent from my HTC Wildfire using XDA App
Yeah
Sent from my HTC Wildfire using XDA App
Yes it works with just about every ROM, but, in my view, I can't see any benefit. (I dont play Angry Birds, and, the rest of the games and LWP's don't show any benefit).
How do you do this?
Just flash it like a rom?
Well, that's what I initially did. Flash the ZIP in Post #49 in that thread. But, on reading that complete thread, I guess you have to edit the build.prop file in /system (Using Root Explorer / ADB Push Pull).
However, this is where I cant get it to work. WHenever I add the 2 lines in Root Explorer and Save Changes, the phone reboots. If I use ADB, even after pushing, when I check the same file using build.prop, no changes are visible, (The opengles.version automatically reverts back to 65536 and the line which enabled hardware acceleration of the UI is gone) and, ASI only shows OpenGL 1.0 due to this
Well, I have no idea what I am doing wrong, will try it out again and see..
I'm a newb with this.
Could someone possibly make a bit more explained guide?
Very basic guide:
* Get Root Explorer or any other file manager that can show the root folders
* Open Root Explorer, change permissions on top to R/W (Be very careful after that. Dont delete anything!)
* Locate the file build.prop under /system
* Long Press the file, Select Edit with Text Editor
* Updated: (ADB Commands Copy - Pasted from another post by kevin2516. Thanks mate )
*Make sure ADB is installed on your system and it is working. There are many guides available to install ADB, so I wont be going into that.
*Start Command Prompt (cmd), Browse to your "Tools" folder into your SDK
*Use the ADB Pull Command adb pull /system/build.prop
*This will now be saved to your tools folder. Edit is using Wordpad / Notepad++ (Not Notepad) as follows:
*Locate a line which starts with dalvik. (The first one, there are 3 of them)
Add the following 2 lines before that:
debug.sf.hw=1
ro.opengles.version=65537
* Save it.
* Push it back to System using the ADB Push Command: adb push build.prop /system/build.prop
* Reboot ADB using the adb reboot command
* Then, grab the Flashable Zip in that thread from Post #48
* Flash it as normal
Done.
Check whether it is implemented or not by going to Android System Info > System Tab > OpenGL. Here, there are 2 OpenGL versions. The first line should say 1.1, and the second should say OpenGL 1.0 ES.
With S-On you cannot change the systemfile directly I think. Thats the reason why your system not keep the change. I have write by myself a little install zip and flash it with nandroid and it works. the zip only works with wildpuzzlerom v0.8 and you can find in the thread for wpr0.8.
bgx said:
With S-On you cannot change the systemfile directly I think. Thats the reason why your system not keep the change. I have write by myself a little install zip and flash it with nandroid and it works. the zip only works with wildpuzzlerom v0.8 and you can find in the thread for wpr0.8.
Click to expand...
Click to collapse
Well, I took your flashable ZIP, removed the build.prop it contained, and replaced it with the build.prop of CM7 Nightly 2. Then, I tried flashing it, still no change.
Now, I have no idea whether I am 'allowed' to change flashable ZIP's like that or not, but, from what it is looking like, I am still unable to get this working on CM7NB2. I'll probably try making a flashable ZIP from scratch later as I get time.
bgx said:
I have write by myself a little install zip and flash it with nandroid and it works. the zip only works with wildpuzzlerom v0.8 and you can find in the thread for wpr0.8.
Click to expand...
Click to collapse
If it's simple enough, it would be nice if you could tell how to do a flashable zip (or yourself make a one suitable for CM6/7 ). I just want to test these libraries on CM7, any help is appreciated
Don't expect nothing special, I'm not a dev!
3xeno said:
Very basic guide:
* Get Root Explorer or any other file manager that can show the root folders
* Open Root Explorer, change permissions on top to R/W (Be very careful after that. Dont delete anything!)
* Locate the file build.prop under /system
* Long Press the file, Select Edit with Text Editor
* Then, locate a line which starts with dalvik. (The first one, there are 3 of them)
* Add the following 2 lines before that:
debug.sf.hw=1
ro.opengles.version=65537
* Save and Exit
* Then, grab the Flashable Zip in that thread from Post #48
* Flash it as normal
Done.
Check whether it is implemented or not by going to Android System Info > System Tab > OpenGL. Here, there are 2 OpenGL versions. The first line should say 1.1, and the second should say OpenGL 1.0 ES.
Click to expand...
Click to collapse
But it's not working for CM7?
Where can i find FLashable zip? I don't understand where is post #48
Even if i find, i have read, that it's not working? Or working?
You can find the OpenGLES 1.1 Flashable ZIP in Post #48 of this thread:
http://forum.xda-developers.com/showthread.php?t=899801
I have updated my post since Root Explorer method doesnt work (No S-OFF).
3xeno said:
You can find the OpenGLES 1.1 Flashable ZIP in Post #48 of this thread:
http://forum.xda-developers.com/showthread.php?t=899801
I have updated my post since Root Explorer method doesnt work (No S-OFF).
Click to expand...
Click to collapse
You wrote : last edit: I didn't notice any difference, much like the test ran above. I'm going to revert until more knowledgeable people look at this.
if it is like you saying, then i dont have point to that **** too.
i think devs who makes this rom should instal in rom everything what can increase perfomance. so im waiting for the rom with all those things instaled.
will it happen someday?:/
vilks said:
You wrote : last edit: I didn't notice any difference, much like the test ran above. I'm going to revert until more knowledgeable people look at this.
if it is like you saying, then i dont have point to that **** too.
i think devs who makes this rom should instal in rom everything what can increase perfomance. so im waiting for the rom with all those things instaled.
will it happen someday?:/
Click to expand...
Click to collapse
Which is exactly what I said in the CM7 thread. No one here has till date, found verifiable gains, with using OpenGL on the Wildfire. Everyone reports the same thing, that there is no or absolutely negligible (Which I think is just a mind thing) change in gaming / intensive applications performance.
If you are looking for ROM's wit inbuilt OpenGLES Support, WildPuzzle has a flashable ZIP, and DS and DK Roms provides it inbuilt in its latest version. For the others, the manual method has to be followed.
Welcome to the Droid X guide! I hope to expand up on this as much as possible, so be sure to check back for updates!
The Benefits of rooting
So why root your android phone? Well, there are several benefits... First, you can backup up your phones current state whenever you would like (makes is easy to jump back and forth if you mess things up!). In addition, you can also install different themes (different color interfaces for the basic framework and applications). You can also install custom ROMs (this is an Android OS that has been built from either Motorola's source, or the Google SDK and released through their generosity for the rest of us to enjoy!
Rooting: Many people are unsure of rooting their phones but have heard of other people doing it. Here is my stance on rooting your phone:
If you are technically savvy, or can follow instructions well and have confidence in your ability to do so, I would definitely recommend it! If you are unsure of your abilities to do so, and simply use your Droid X because it is a great phone right out of the box, then I would recommend reading through this guide and some other threads on the Droid X forums so you can familiarize yourself with the potential possibilities and process' involved with rooting and customizing your phone. I do not say any of this to deter anyone from wanting to root their phone, it just can be a dangerous situation for those who are not familiar with how it could potentially damage their phone.
I have seen many ask about the dangers of rooting. First off, yes it will void your warranty, but you CAN unroot your phone. I will include this information later =)
#1 rule of modding your phone: ALWAYS TAKE A BACKUP BEFORE MAKING ANY MODIFICATIONS!
with that said... let's continue =)
Rooting: Just because you have a rooted phone, does not explicitly open up new features on your phone.... What it does do, is open up the possibility for features on your phone =) Keep reading...
Themes: In order to theme your phone, you first have to deodex it. If you attempt to theme the phone without deodexing it, you can run into issues... Themes allow you to change the look of the phone framework and applications (e.g. different colors or images). Make sure to follow rule #1, and then follow any specific instructions that the creator of the theme may have included with their post.
Droid X Bootstrap: This is the saving grace for the Droid X created by Koush. Installing this application once rooted allows you to create backups, restore backups and install custom themes, ROM's, and other modifications that have been made into flashable zip format. I will explain how to use this later as well.
Custom ROMs: Custom ROM's are a developers build of the android operating system either using the Motorola ROM as their base, or building directly from Google's SDK. Many of the ROM's for the Droid X are "blur-free" which means that they look like a generic android OS install the way Google intended it. The default "ROM" that comes on your phone has what is known as "blur" by Motorola. It is just graphical enhancements to the way the phone operates that mostly tie into social networking applications and widgets. Many Android enthusiasts believe that Motorola Blur or HTC Sense ruins the Android feel. Whether or not to use a blurred or blur-free ROM is really up to you and how you like your phone to look and feel.
I will cover more about ROM's later in my posts and try to give an overall description of each. As usual, before trying to flash any ROM, be sure to backup your phone.
Overclocking your phone: Overclocking for those who do not already know what this means, is basically the ability to tell your phone's processor to run at a higher speed. This basically just improves performance on your phone, but can be harder on the phone as well. By telling the phone run at a faster processor speed, you can decrease the battery life of your phone. The droid X overclocks in a different manner than with most Android phones, due to the inability to run custom kernels on the Droid X.
For those who are not familiar with the potential of overclocking your phone, I highly recommend not doing it. While rooting can be dangerous, if you mess up overclock settings on your phone, you can do more harm than good.
So I have seen a bunch of people asking questions that seem to pop up repeatedly on the forums... I plan on adding to this as i put this guide together for a few people who really needed more step by step instructions to get going. Feel free to suggest stuff for me to add, and I will throw it in.
Thanks, and enjoy the following:
Ok, here are the steps for setting up the sdk, getting rooted, and all that good stuff... have a feeling I will be making this into a new thread...perhaps....
SDK:
First off... you will want to go to the following site to download the sdk:
http://developer.android.com/sdk/index.html
Grab the following download: android-sdk_r08-windows.zip
I saved it to C:\sdk (i created a folder called SDK right at the root of C: drive). When it finishes, unzip this using 7zip (or any other unzip program you like) to the sdk folder. When it is finished unzipping, you should have a folder called "android-sdk_r10-windows". If you open up that folder, you will find a folder called "android-sdk-windows". Open this folder up and double click on the "SDK Manager.exe". This will open up a window, and bring up additional windows, one of which will ask you to "choose packages to install". You can download any or all of them. I recommend downloading the following: (NOTE: this may have changed as I don't recall the API versions for sdk r10)
• Android SDK Platform-tools, revision 1 (the top-most download)
• SDK Platform Android 2.3, API 9, revision 1
• SDK Platform Android 2.2, API 8, revision 2
• USB drivers (I don't think this shows up in the latest version of the sdk's first download window. I believe it is found if you go to the available packages section the "Android SDK and AVD Manager and expand the 3rd party section....but if you happen to see it in there...grab it)
This should be sufficient for now. All packages are accepted by default. If you do not wish to download all of them, simply highlight each one (one at a time) and then click the reject button towards the bottom middle of the window. When you have selected the packages you wish to download, click the install button.
After this has installed, you now have the Android SDK installed on your machine. You can close all windows related to the SDK, as we don't actually need to do anything with it, it simply has tools within it that we will need later. (This is where the adb command originates from. There is an adb.exe tool in the "platform-tools" folder of the sdk install, but we will get to this later).
Now you will want to go to your desktop (or anywhere you have a shortcut or icon for My Computer), right click on My Computer, and select properties. Under the "advanced" tab of the window that opens, you should see a button at the bottom that says "environment variables". Click on this, and then find the "Path" variable under System Variables NOT user variables. Click Edit and go to the end of the "Variable Value" field. You will want to make sure there is a semicolon ";" at the end of this before typing any additional info. You will want to add the full path of your android SDK install. For example, if you followed my example for download/saving/extracting/installing above, you would type the following information into the end of the "Variable Value" section:
C:\sdk\android-sdk_r10-windows\android-sdk-windows\platform-tools
If you installed to another location, be sure to type the correct path to the "tools" folder within your installation of the Android SDK. Then click the OK button, and close any windows that were opened from adding to the "path variable".
Droid X Drivers
This section is a little more difficult to explain, as there are so many variables depending on what operating system you are running (windows XP, Windows Vista, Windows 7, etc). and whether or not you are running a 32-bit or 64-bit instance of your chosen Operating system.
Here is one link for Droid X drivers:
http://www.verizon-phones.org/verizon-motorola-droid-x-usb-drivers-pc-charging-drivers-download.html
I simply googled Droid X drivers, I'm sure this isn't the best link, but just for example I'm throwing it out there. If you google Droid X USB drivers you should be able to find the drivers you need, as well as help and instructions on how to get everything working.
Once you get the usb drivers installed, you will want to connect your Droid X to your computer. If it is recognized, you will get a notification in your drop down bar on your phone. On your phone, press on the USB connection in the drop down menu, and select "charge only". Next, open up a command prompt on your computer. Type the following in and hit enter:
adb devices
You should see something simiilar to the following come up if everything is configured correctly:
C:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015A882315005010 device
If you see something similar to what I have above... then ADB is working correctly, and we can continue! Now we will move on to getting your device rooted! You will want to grab the z4root.apk that I have attached earlier in this thread and download it onto your computer. We will now test out if adb is indeed working! Save the z4root.1.3.0.apk and put it in the "tools" folder of the sdk we downloaded earlier. Now open up a new command prompt (or use the one we opened earlier if you haven't already closed it!) Change directories to the "tools" folder of the sdk:
If you installed the SDK where I used in my example.... type the following:
cd C:\sdk\android-sdk_r10-windows\android-sdk-windows\platform-tools (press enter)
type the following: adb install z4root.1.3.0.apk (press enter)
You should now see the following:
C:\android-sdk-windows\tools>adb install z4root.1.3.0.apk
1833 KB/s (978414 bytes in 0.521s)
pkg: /data/local/tmp/z4root.1.3.0.apk
Success
z4root and ROOTING
If you get all of this, you have now installed a package using adb and we know the interface works. If you don't want to have to mess with this method of installing, you could also download "Astro File Manager" from the android market. You would then need to save z4root.apk to your sdcard of your Droid X. Then open the Astro program and browse to your SDcard and file the z4root.1.3.0.apk. Press on the .apk file and it should come up with a box that says something similar to "open with app installer" or "app manager"... don't recall exactly what it says, but should be something similar to package management or install of some sort. After pressing on that, you should see an install button. Press on that to install z4root.
Now that z4root is installed, you will want to go to your application list on your phone and press on the z4root to open the application. Press on the permanent root button and wait! This process may take a while, and your phone will reboot, but when it does, you are now rooted.
Make sure when trying to root your phone that you go into Settings-->Applications-->Development make sure "usb bebugging" is enabled.
Removing BOOTSTRAP COMPLETELY (You only need to follow these steps if you WANT to remove Droid X bootstrap by Koush, this is not installed on your phone by default).
If you would like to completely remove Droid X bootstrap from your phone, here is what you need to do:
1) connect your phone to ur pc in charge only mode. Make sure it is recognized by adb
A) open command prompt and type "adb devices" (hit enter, your phone should show up)
2) in the command prompt, type "adb shell" (press enter)
3) type "su" (press enter)
4) type "mount -o rw, remount /dev/block/mtdblock4 /system" (press enter)
5) type "cp /system/bin/logwrapper.bin /system/bin/logwrapper"(press enter)
6) type "adb reboot" (press enter)
Your phone will reboot after typing adb reboot, and may take a little bit longer to boot the first time after bootstrap is removed (it may not, I just haven't gone through this process in a while).
Bootstrap should now be completely removed.
Note: all text in quotes is just what you should type...do not include the quotation marks when entering commands.
Disclaimer: I take no responsibility if you mess up your phone. Typing these commands incorrectly CAN mess up your phone. By following these directions, you do so at your own risk.
Installing Droid X Bootstrap
You can grab this .apk file from this thread as well, as I have it posted in one of my previous posts. You will then install this .apk file the same way that you installed z4root. Obviously if you are using the adb command prompt method, you will want to replace z4root.apk with the full name of the droid X bootstrap apk; if you are using a file manager or installer, just follow the same instructions as before as well.
With the bootstrap installed, you are now able to take backups and restore them as well in the event your phone has problems.
Will be adding SBF instructions and links soon =)
If this guide has helped you, please say thanks!
THEMES AND HOW TO USE:
NOTE: In order to install a theme, you must deodex your phone. If you attempt to try and install a theme without deodexing your phone, you can run into problems down the road.
How to Deodex Your phone the EASY way:
Below is a link that Septhin (from Sephtin.com, all credits go to him for this) posted. This is a SYSTEM ONLY flashable .zip that will give you root, as well as deodex your phone ONLY if you are on the 2.3.340 OTA for verizon. Copy this to your sdcard, and flash in bootstrap recovery! Note: If coming from anything other than an existing 2.3.340 system, then you should wipe data/factory reset for safety's sake!
http://www.mediafire.com/?gvvgnum0uma2huk
If you are on the 2.3.15 OTA looking for Deodexed system:
http://www.mediafire.com/?drixq6ry6ja83oq
How to Manually Deodex your Droid X:
Note: all credit for this portion of the writeup goes to Webst3r on droidxforums and those he has mentioned at the bottom of this section. I did not write up the deodex portion of this guide. I am simply including it as a one stop guide to help as many people as possible.
I AM NOT RESPONSIBLE FOR WHATEVER HAPPENS TO YOUR PHONE!
You must be rooted!
What you'll need:
A Windows based machine
xUltimate v2.2
Patience
Process:
1. Unzip xUltimate v2.2, and launch "Main.exe"
2. If everything goes well xUlt should recognize the phone and make a connection. You now should see a list of options.
3. Run option 1. After option 1 is done, run option 2.
4. Now these well take a while. Run option 3.
5. IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex". It's a bad file, and interferes with deodexing process.
6. Now run option 4, and wait.
7. Exit xUltimate, and put the phone in USB mass storage.
8. Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
9. Open a command prompt, and do the following: (note: at the end of each of the following lines, press the enter/return key on your keyboard)
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Your phone should now be deodexed!
You may notice an increase in speed, and you now have the ability to edit certain files with greater effects. (i.e. services.jar)
Credits: (note these credits are from the original post made by Webst3r, not me, but I would also like to thank them for their work and contributions!)
Rainabba and Mike919: For initially working with me to get a white clock, and later deodex.
toxman: For testing, and being a huge risk taker.
teenfaces: For letting me use his services.jar
And especially Xeudoxus: For letting me a guinea pig, for xUltimate, and answering my questions. And also for the making the xUltimate tool. It defiantly makes thing easier.
SBF: What is it, and what does it do?!?
An sbf file contains the data files necessary to return an Motorola phone back to its "out of the box state". This means it is as if you just pulled the phone out of the box and turned it on. A successful sbf will return you to stock status without any custom ROM, or theme. Usually when one uses and sbf file, you will also want to wipe data/factory reset before hand, and after using and sbf for best results.
SO WHAT DO I NEED?
• RSDlite 4.8 http://www.multiupload.com/HL0ZAL9GK8
• Motorola Drivers: http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
• Correct SBF files for your phone:
o If you are on 2.3.15 OTA (bootloader 30.03): http://www.multiupload.com/HS3Q4U95CG
o 2.3.32 Full SBF: Then go to this site for all the mirror lists. I will post a few direct links below: http://www.mydroidworld.com/forums/droid-x-discussion/5633-droid-x-2-3-32-full-sbf.html
• http://www.multiupload.com/QX7Q3B53UQNOTE: http://depositfiles.com/en/files/60kvlswk2
o If you have already flashed 2.3.32, and/or have 30.04 bootloader: 2.3.34 SYSTEM ONLY SBF:
• DIRECT LINK TO SBF: http://www.megaupload.com/?d=OXK9Q1ZG
• some have preferred to flash individual files through Bootstrap recovery from MyDroidWorld. If you would like to use this method and are more comfortable flashing files than SBF, use this site:
o http://mydroidworld.com/forums/droi...ystem-baseband-2-3-340-kernel-bootloader.html
• 2.3.340 FULL SBF: http://www.mydroidworld.com/forums/droid-x-discussion/6367-new-full-sbf-droid-x-2-3-340-a.html
• Thanks to Maderschramm, there is any easier way to get back to stock on 2.3.340 OTA WITH ROOT
MADERSTCOK "SBF" (note I did not do this write-up, all credit goes to Bouchigo on android forums. Original credit goes to Maderschramm over at DroidXforums and XDA)
NOTICE: Coming from ANY non-blur based ROM and doing Maderstcok is guaranteed to bootloop due to mismatch in framework without a data/cache wipe.
http://www.droidxforums.com/forum/droid-x-hacks/15666-maderstcok-ota-2-3-340-update-zip.html
maderstcok - OTA 2.3.340 update.zip
None are responsible for your phone but you.
After a bit of work I've created an update.zip for you guys that want a fresh install of 2.3.340 without sbfing.
This is the FULL, OTA 2.3.340 - contains radio, kernel, and all other updates, even those EXCLUDED by the 2.3.340 system only sbf.
What that means is that if you have 2.3.15, 2.3.151, or 2.3.320 you're one update.zip away from the OTA 2.3.340
This is useful in many ways:
• You want stock .340 but didn't create a nandroid backup
• Can't OTA (modded phone)
• Get ready for an OTA
• Remove Root
• Add bloat back
• Re-Odex
• Your phone is acting weird on the update
• Something broke
• Fresh ROM install
• You don't want to flash 5 update.zips or sbf to update your phone
• etc.
This will format your system data (helps prevents bootloops - not 100%) and system (in case a rom put some apps in the /system/app) partitions and also changes the boot image to the stock moto M (to fix the Tranquility boot logo - something even an SBF won't fix).
As always, make a backup and I'm not responsible for what happens to your phone.
Download the file here and place it on your sdcard: http://www.droidxforums.com/forum/
• Mirror 1 http://ubuntuone.com/p/XAk/
• Mirror 2 http://www.megaupload.com/?d=4AO672L1
Instructions:
1. Using the Droid X Bootstrapper make a backup. (more information here)
2. Browse (using volume buttons) to "install zip from sdcard" and select it with the camera button.
3. Select "choose zip from sdcard".
4. Select "maderstcok340.zip"
5. Confirm the install.
6. Be patient, wait for the install to finish.
7. Reboot the Droid X. DO NOTHING ELSE IN CLOCKWORKMOD!!!!!!!
8. Activate the phone with VZW (more instructions below).
If you attempt to create a backup or flash a rom post maderstcok installation you're going to have a paperweight. This seems to be because maderstcok removes root and the clockworkmod recovery area, so it doesn't like you playing around in there. Re-root and reinstall the bootstrapper, then create a backup or flash a new rom, DON'T DO IT BEFORE REBOOTING THE DX AFTER ISNTALL.
Formatting Data and Cache is optional; however, if you want a really clean install do so. If you factory reset you'll be forced to activate the phone automatically while if you don't you'll have to follow the quick and dirty activation instructions below - the choice is ultimately yours.
Quick and dirty instructions for activation:
1. Dial *228
2. Press 1
3. Enter last 4 of primary acct holder's SSN
4. Wait - more in depth instructions in a link further down.
This can take some time, especially on the two system installs and the radio install. Don't battery pull unless you want a brick.
The file won't flash properly if you have a botched download - this seems to be caused by the size of the file. Please check your file size before flashing:
Size: 284.7 MB (298481300 bytes)
MD5: ce7122280eafad4a39ba7fefeb764bf5
My free filehosters sometimes .zip the .zip - it looks like maderstcok340.zip.zip
Just unzip once and check the md5 to make sure it checks out - if not, redownload. Don't try to flash the .zip.zip without unzipping it once!
You'll have to activate your phone again after the install. See this for additional help.
If you encounter any problems during the flashing process follow standard ROM installation troubleshooting (i.e. battery pull, factory reset, etc.)
A lot of this stuff is from Team Black Hat - I did pull some of my own phone files too - but if you're looking to donate, please hit them up. Without them we'd be up a creek. Tell 'em I sent ya
One final note - z4root seems to work flawlessly after flashing this file. Just thought I'd throw that in there...
Enjoy!
How to use RSDlite and an SBF file:
NOTES ABOUT USING SBF and RSDlite: Make sure your battery is fully charged. If your phone dies while applying an SBF file, you could be stuck...Be sure to create a backup before using SBF, this could be a nandroid backup, and I would also recommend backing up your SMS messages and applications and any application data (use Titanium backup).
I have found this to have the best results.... before applying an SBF, boot into bootstrap recovery and do a wipe data/factory reset.
1. Turn off your phone. Hold down the "Volume down" + camera button while holding the power button. Your screen should flash and say
Bootloader
30.03 (or 30.04 if you are on the latest update)
Battery OK
OK to program
Connect USB
Data Cable
2. Open up RSDlite and click the " ... " button to browse to the appropriate SBF that you need to use.
a. If on bootloader version 30.03 then you will want to use the VRZ_MB810_2.3.15_1FF_01.sbf file
b. If on bootloader 30.04, then you will more than likely want to flash the 2.3.34 system only sbf (SHADO_X6_2.3.34_SYSTEM-ONLY.sbf)
3. Once it recognizes the file, connect your droid X to the computer via the usb cable. You should see your phone listed in the bottom section of RSDlite.
4. Click the start button, and watch the magic at work =)
5. When your phone reboots, I generally try to do another wipe data/factory reset.
a. When turning phone on, hold down home button + power button. When the droid with the ! comes up, press the search button. You can use the volume up/down buttons to navigate, and the camera button to select.
If your phone dies during sbf, A) make sure to charge your battery before sbf next time B) here are some instructions
IF YOUR PHONE DIES DURING SBF
How to Fix
One thing that you may notice is that when you have this error, your phone will not charge the battery and you'll only be able to see the screen turn on if its plugged into the wall. Somewhere on the screen it will say "Your Battery is Low" and "Cannot Reprogram" or something like that. The easiest way to get through this is to find a friend with a charged battery or go to your local Verizon store and see if they have a demo phone they can use to charge your battery. If you're like me though you will not be lucky in any sense like this so you will have to find the MacGyver inside of you and get a little creative. What you need for this is an old USB cord. One end must be a standard USB cable head and the other can pretty much be anything. Once you have that, follow these steps:
NOTE: I TAKE NO RESPONSIBILITY FOR DAMAGE DONE TO ANY PHONE, BATTERY, ETC. FOLLOW THESE STEPS WITH CAUTION TO AVOID RISK OF DAMAGE.
1. Take your cable and cut off one of the ends, leaving a standard USB plug at the opposite end to plug into your computer.
2. Now you need to strip about and inch of the wire off until you get to the core where you should see 4 colored wires (red, black, white, and green). The colors don't really matter and they may vary, just as long as you can see a red wire and a black wire.
3. Strip off about a quarter inch of the rubber sleeving on the red and black cables, exposing the actual metal wire.
4. Twist the metal strands of each of the wires a couple of times so that all of the wires from the black cable are together and all of the wires from the red cable are together. This is just to make sure that you don't create a short circuit.
5. Here's where it gets a little tricky. You are going to use this cable to make the phone think the battery is fully charged, when in fact you will just be powering the phone using the power from the USB port. Pull out the battery on your phone and find the 4 exposed metal slots (the battery terminals).
6. Each of the far terminals should be labeled with a plus (+) or a minus (-). What you need to do is put exposed leads on the red wire up to the positive terminal and the leads of the black wire up to the negative terminal.
7. While still holding the leads on their respective terminals, slide the battery back into place in the phone. MAKE SURE THE WIRES ARE NOT TOUCHING WHEN YOU PUT THE BATTERY INTO THE PHONE! BAD THINGS COULD HAPPEN ONCE YOU PLUG THE CORD INTO THE COMPUTER!
Note: As tested by parm289, you can skip step 7 and just use the cable to charge the battery if you'd like. He recommends allowing it to charge for 6-7 minutes before placing it back into the phone. Thanks parm!
8. Once the battery is in place and the wires are on the correct terminals but not touching each other, plug the USB cord into the computer. If all has gone as it should, the screen on your phone should come on (may have to press the power button) and the phone should be telling you that the battery charge is okay and that it is okay to program. YAY! Your phone is almost back to normal!
9. Go back up to the previous section in this post that tells you how to reflash the .sbf and follow all of the instructions there. Once that has finished flashing the .sbf to your phone, your phone should be back to working order! You will most likely have to redo the entire setup on your phone but at least your phone is no longer a fancy paperweight
ROM overviews:
Note due to the constant change in version numbers, I have may not have updated this list. I will try to keep it updated as I can.
BLUR ROMs: Apex 1.3, ZapX Bazinga, Rubix Blurry 1.8, Simply Stunning X, DarkSlide 4.2, Fusion 2.0, Tranquility 3.7.0 (has option to add blur)
Blur-less ROMs: Tranquility3.7.0, Rubix Focused 1.9.7, Liberty 1.5, Cobalt 1.0 , Ultimate Droid, FlyX, Darkslide 4.2, GummyJar 2.5, Incredibly Re-Engineered 1.0, Obsidian 2.0.2, Fission 2.5.7
LIBERTY 1.5
http://forum.xda-developers.com/showthread.php?t=939592
ROM Features:
Base....Originally based on GummyJAR, I would call Liberty's bas a evolution of GummyJAR at this point
95% of all the apps were built from source.... rather than decompiled and hacked apps via APKmanager!! And it shows in pure speed!!!!
Blurless
Wycontacts
Cytown Phone
AOSP Pattern lock
AOSP tab Lockscreen with the option for Rotary as well
Custom terminal emulator with added color options
Reboot option in power down menu
Launcher2 with increased snap velocity
Custom Liberty wallpapers app
Custom Liberty live wallpapers (nexus Mod like, modded from CM source)
Music control's in lockscreen (will control any music source including Pandora)
MusicMod by Eliot Stocker (built from CM source and compiled by Team Liberty)
Inverted Gtalk and Gvoice
Gingerbread keyboard - built by hotaru modified by Team Liberty for better button size
AppWidgetPicker - credit boombuler
Latest Market included
build.prop tweaks - thanks to LexusBrian400
Ads blocked via hosts file - thanks to delta_foxtrot2
10% battery increments support
Clockwork recovery (bootstrap) installs on initial install
Working init.d with config file (start-up scripts)
Liberty scripts:
(Run them in terminal emulator. Type script_name -help for more info)
** ads, allinone, apploc, backup, bootani, cache, camsound, compcache, chglog, donate, exe, fixperms, freemem, install_zip, load, pulldown_text, install_zip, load, market_history pulldown_text, rb, restore,rmapk, setcpu, setprops, slim, sound, switch, symlink, sysro, sysrw, usb, zipalign_apks **
All apps optimized and zip aligned
More to come...
Toolbox Features:
• App Management:
* Apps2SD
* Remove/Backup system/data apps
* Install Add-Ons on the fly (blur, non-blur, extras, etc.)
* Backup/restore feature
• Liberty Mods
* Switch between transition animations
* Change boot logos
* Set Build Properties * File editor included by Fr4gg0r *
* Install Fonts
* Install Themes from the toolbox
* Pulldown-bar text editor
* Icon Chooser (change application and battery icons)
• Liberty Tweaks
* Ad Blocker (Block/Unblock)
* Cache Manager (clear/move to SD)
* Free Memory
* Manage Boot Animation
* Mount system rw, fix permissions, zipalign apps, etc.
• Reboot Options
* Reboot, reboot bootstrap, reboot recovery, powerdown
• Settings
* App Theme (change theme of toolbox)
* Notify for ROM updates/patches
* Lockscreen Settings
* Recovery safe mode
* Overclocking
* Sysctl Support
* Camera Shutter Sound
* Tools (Spare Parts, Dev Tools, Testing Menu)
* Restore apps feature
* Set install location on boot
* Zipalign apps on reboot
* Clear cache on reboot
* Fix permissions on reboot
Rubix 1.9.7
http://forum.xda-developers.com/showthread.php?t=927644
Rubix Focused 1.9.7 overview: If you are looking for a ROM with great stability and battery life, then look no further than Rubix Focused 1.9.7. Drod2169 has thrown some amazing scripts in this ROM that allow for app backup, ad-block, and many others. His direct support for the ROM and great speed and responsiveness from his dev work makes it a solid choice. In addition, he has fully customized sysctl.conf to help improve battery life, Java VM management, speed and performance.
* SMART One-Click Overclock App (QuickClock for rubiX) (Credit to Paul Anderson’s amazing work!)
* This is a very brilliant OC app. It configures specifically for your device, and OC’s to the BEST value, and voltage settings for your phone.
**If your max speed turns out to be <1100, it will only overclock to 1100. This is for the sake of Overclocking, and the safety of your device to not push it higher.
* Base is GummyJar (Credit Kejar)
* Full firstboot functionality.
* Rotary Lockscreen Option
* AOSP Settings Menu (No Compass Calibrate/Battery Manager. For Battery Info, check out About Phone/Battery Use)
* GB Keyboard with working size (cause size does matter )
* Theme by Mycahya
* Working 3G HotSpot
* Phone as Modem/USB Tether Option (Instructions stored in rubiX Folder on your SDCard)
* AOSP Lock screen instead of themed Moto tabs!
* Lockscreen pattern no longer on a timer.
* Market Apps installed to Data Partition
* This Includes:
* Maps
* Gmail
* Voice Search
* YouTube
* ADW Launcher
* Street View
* Spare Parts
* Adobe Flash Player
* DL Crutch Lite (For Browser Downloads)
* Tweaks adjusted
* File Manager (Credit to Cyanogen)
Gingerbread Parts: (Credit to Pete)
* Launcher 2
* Gallery 3D
* Alarm Clock
* Desk Clock
SCRIPTS: Credit to Fabulous, JRummy, Sephtin and myself.
adblock: block or view ads
apps: run the script for directions. If you choose restore, you must reboot after for it to take effect
backup: backs up all of your user apps. backup -bk is the correct way to run the script
calc: remove/restore the calculator
carhome: remove/restore the car home launcher
dxeye: remove/restore the DX LWP Please note that this is removed by default, and placed in /data/rubix run the script to restore.
email: remove/restore the email app
fixperm: fixes permissions (credit Koush)
gallery: switches between the 2D (credit to Cyanogen) and 3D AOSP Gallery
genie: remove/restore the news/weather app
office: remove/restore QuickOffice: Please note that this is removed by default, and placed in /data/rubix run the script to restore.
sys: write the system read/only (-ro) or read/write (-rw)
zipalign_apks: zipaligns all the apps in system. Unnecessary since this is ran on every boot!
Fission 2.5.7
http://forum.xda-developers.com/showthread.php?t=839246
About Fission: The first generic Android platform for current and future Droid devices. We are a bunch of mad hackers, modders and developers that were not happy with the current model of Droids being "Blurred" so we began a mission to rid our devices from the blurriness of VZW Android systems. It started with a crazy idea of messing with the Droid2 SDK that has turned into a full fledge AOSP generic type of ROM. We have incorporated many features that were only seen in AOSP ROMs before this. Some of the features include Reboot in Power Menu, custom built Framework, vanilla Android GUI, totally blur free app folder and many more AOSP like features to come in the short term future.
Features:
True Vanilla ROM with generic Android feel, not themed to look like one. No blur apps...
Reboot in Power Menu.
Custom Framework - 10% battery increments with display percent number & without.
Overclock ready out of box.
Lots of free memory.
ROM has root and has been deodexed, and zip aligned.
Busybox installed and symlinks have been applied.
Clean base for you to customize how you like.
And many more...
WILL COVER MORE THIS WEEK! Will also clean up this list to cover most important features to reduce lengthy posts.
Short Little MetaMorph Guide for Changing Icons
Had someone in a post ask about changing some battery icons... So this is a little blip about using it...
I recommend checking out DroidPirate.com if you are looking for images. If anyone else has a place they use for icons, please let me know, and I will add it to this post! Thanks
How-To
MetaMorph ONLY installs the current theme files to the app that exist in the /system/app/ if there is no file you must find the .apk on your phone and place it into the /system/app/ directory.
1) pick the icons you want and download the .zip
2) The file should be a “.ZIP” extension, make sure you do not unzip the file.
3) Connect your device via USB and mount
4) On the root of your SD-Card you need to create a folder called “AndroidThemes” IT MUST LOOK EXACTLY LIKE THAT OR IT WILL NOT WORK
5) Copy the .ZIP file you downloaded and place it in the “AndroidThemes” folder.
6) Assuming you already have the MetaMorph application installed on your phone. Open the MetaMorph app.
7) Click on “Unzip/Extract New Theme”
8) You should the .zip file you have added to the AndroidThemes folder like in the image shown below.
9) Click on the file inside of MetaMorph a MetaMorph install screen should come up telling you about the theme you are installing like shown below (just click Close)
10) Now you should see a button located on the bottom click on “Apply All” this will begin the process of the application skinning.
11) You should see a message box that pops up that says “All Themes Applied” like shown below
12) Reboot your phone and make sure whatever app you where skinning is now skinned.
Recovering Contacts If You Lose Backup Assistant When Using a Custom ROM:
For those of you who relied on Backup Assistant in the default Moto ROM for your contacts, you are in luck =)
Go to backupassistant.com and log in. From here, you can see all of the contacts as of your last sync, and then you can back them up as an Outlook CSV. Next, login to your gmail account, click on "Contacts" and then click "Import". Import the .csv file that you generated from backupassistant.com and....VOILA, all of your contacts are now synced to your gmail account, and you can kiss backup assistant goodbye!
SysCtl.conf Tweaks
Credit for this section goes to macpro88 at DroidXforums and Marius from whom macpro mentions below
Liberty 1.0 and Syssctl Config
Listen up everyone! Since the release of Liberty 1.0, JRummy16 also released a new app in the market called Sysctl Config, which gave users an interface to manually edit and tweak the sysctl.conf file. Alongside this, Liberty made it easier to configure the sysctl.conf file using the integrated menu option under Liberty Settings without the use of the app.
Please take special note! That any ROM can utilize these sysctl.conf tweaks, not just Liberty, and rooted stock as well.
(You must be rooted and have busybox installed for this to work on stock)
So what is the purpose of this thread? And what is Sysctl.conf all about?
First of all, we are going to explore what sysctl.conf is.
Second of all, we are going to explore what sysctl.conf does, and what it can do for your phone.
Lastly, we are going to explore how sysctl.conf works and what kind of benefit is has on the Android OS.
Now, before we get started, we need to clear something up! The tweaks and modifications we will discuss in this thread, WILL NOT IN ANYWAY INFLUENCE BENCHMARK SCORES SUCH AS QUADRANT! Benchmark apps are meant to measure hardware performance only and are in no way affected by these tweaks and modifications, but make no mistake! You will notice at least a slight increase in Android's performance and a possible increase in battery life as well.
Another thing that everyone needs to know is that the Android OS is a Linux based operating system, so there will be a lot of references to Linux, just so you are not confused.
So lets get started shall we?!?!
Ok, so first of all, let’s explore what sysctl.conf is.
The sysctl.conf is a configuration file for "sysctl" which is an interface for dynamically changing kernel parameters in the Linux OS. The configuration file contains the following elements, vm.min_free_kbytes, vm.dirty_ratio, vm.dirty_backgroud_ratio, vm.vfs_cache_pressure, vm.oom_kill_allocating_task. There are many other elements within the file, but we will be primarily focusing on these specifically (the vm prefix stands for virtual memory). The sysctl.conf file should be located in /etc (/system/etc) by default. To enable it you need your ROM to execute "sysctl -p" somewhere during the boot process (or shortly afterward). We will also be discussing how to enable it if it is not already done so. You can also run sysctl -p manually to enable it any time after the OS is started.
Now, let’s get down to what sysctl.conf does and how it works.
Min Free KBytes (vm.min_free_kbytes) - This is used to force the Linux VM to keep a minimum number of kilobytes free. The VM uses this number to compute a pages_min value for each lowmem zone in the system. Each lowmem zone gets a number of reserved free pages based proportionally on its size. Default is 2048kb.
Dirty Ratio (vm.dirty_ratio) and Dirty Background Ratio (vm.dirty_background_ratio) control how often the kernel writes data to "disk" (in our case the internal microSD system card, not the removable microSD card). When your apps write data to disk, Linux actually doesn't write the data out to the disk right away, it actually writes the stuff to system memory and the kernel handles when and how the data is actually going to be flushed to the disk. These values represent a percentage, the higher the percentage, the longer it waits to flush, the lower the percentage, the more often flushes will occur. Now remember, we are dealing with solid state storage, not the traditional disk platter and spindle. So we are actually able to delay flushes a little longer with solid state versus a traditional hard drive disk.
VFS Cache Pressure (vm.vfs_cache_pressure) -Now here is where it gets interesting! File system cache (dentry/inode) is really more important than the block cache above in dirty ratio and dirty background ratio, so we really want the kernel to use up much more of the RAM for file system cache, this will increas the performance of the system without sacrificing performance at the application level. The default value is 100, as a percentage, and what you want to do is lower the value to tell the kernel to favor the file system cache and not drop them aggressively.
Oom Allocating Task (vm.oom_kill_allocating_task) (enable or disable, generally in Linux this value is either a "1" or a "0," representing as on or off.) -This enables or disables killing the OOM-triggering task in out-of-memory (oom) situations. If this is set to zero, or disabled, the OOM killer will scan through the entire task list and select a task based on heuristics to kill. This normally selects a rogue memory-hogging task that frees up a large amount of memory when killed. If this is set to non-zero, or enabled, the OOM killer simply kills the task that triggered the out-of-memory condition. This avoids the expensive task list scan, which can take mass amounts of time and "hang" or freeze the system.
This information has been pulled from the following sites:
imoseyon: Sysctl tweaking for faster, longer lasting Android
imoseyon: sysctl (and minfree) tweaks revisited
http://www.linuxinsight.com/proc_sys_vm_hierarchy.html
How to edit the values manually, follow these steps:
1) First enable sysctl from Liberty settings, if you are on Liberty
2) Run Root Explorer
3) Modify /data/liberty/init.d.conf to make sure that sysctl is enabled ("sysctl = 1")
4) Go to /system/etc/, and mount it r/w
5) Modify sysctl.conf by long pressing the sysctl.conf file and selecting "Open in Text Editor." When finished, save the file and exit
6) Run Terminal Emulator
7) Type "sysctl -p" (output should confirm whether you've done step 4&5 correctly)
(Soon to come, how to enable if your ROM does not support sysctl, which will require much more tweaking.)
If you want to check to see if your changes take hold after reboots, run this in Terminal Emulator:
sysctl -a| grep vm
or
sysctl -p
This command will give you all the sysctl values, scroll down to find the ones you edited and verify that they are the same values you changed them too.
Now, if you want the easy way out, our good friend Marius has been great, and created a flash-able .zip that does all of the work for you!
The .zip can be found here, at Marius' blog titled "imoseyon."
When you flash the .zip file, in Bootstrap Recovery, the following will take effect, and please note, any settings you may have altered, will be overwritten!
Applying the .zip will do the following:
1. Install BusyBox 1.18.0 (in an alternate location)
2. Enables cron, which is a Linux time-base job scheduler
3. Tweaks certain kernel elements (vm, minfree, etc.)
4. Tweaks build.prop (on some ROMs)
5. Flushes system caches once a day (1AM PT)
This .zip should be all you need to get your phone running in tip-top shape. The zip is fairly ROM agnostic, meaning that almost any rooted ROM is going to work (rubiX, Liberty, ApeX, Darkslide, etc. and maybe even stock ROM, as long as you are rooted). It should also work for both Droid X and Droid 2.
Please make sure you create a backup before flashing anything!
After you flash the .zip, you can run the following command in Terminal to make sure it was applied successfully:
pgrep -f crond
If you get a value on the following line, the .zip has been applied successfully, don't worry about what number you, everyone may end up with a different number.
If you are really feeling adventurous and are down for a good read, and really want to get to know the Android OS even better, please follow Marius' blog, as it is a great read!
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
There really is NO right answer when you research sysctl. The best thing to do would be to search VM Linux tweaks. Most of the time, you'll see sysctl values that people optimizing their Linux systems use. Take a look at those, and then look into the actual name of what you're tweaking, to find out what it does.
VFS Cache Pressure, go ahead and disable that. I think the stock value is 100, so enter that. At the value of "12" which is the default in Liberty (from one of my old sysctl's) causes a slowdown after a while, even though makes everything much more responsive at the get go. The slowdown is why I removed it from rubiX roms. OOM Kill Allocating Task kills off the app that caused you to run out of memory, which runs better than the stock android configuration.
The default values in Liberty sysctl tweaks are what I suggested to JRummy after extensive research and testing with Drod on RubiX. The settings Marius used up above are actually the stock settings, so you would have those values by disabling sysctl all-together, which is definitely an option. By raising the dirty ratio and dirty background ratio to 95 and 60 respectively, you are allowing for fewer memory flushes which results in much improved battery life. I found, as Drod mentioned, that with vfs_cache_pressure too low, you will see some slowdowns in performance at around 50 hours without a reboot. Through additional testing, I determined that a setting of 50 here, half that of stock will provide a good blend of benefits without risk. You would need to be running for something like 150 hours without a reboot in order to ever see a slowdown with this setting. It may be even more than that.
From what I have gathered it seems the general consensus in this thread is that there are two main approaches to this:
vm.min_free_kbytes = a
vm.dirty_ratio = b
vm.dirty_background_ratio = c
vm.vfs_cache_pressure = d
One is the self-maintained, improved overall performance approach:
3072 => a => 2048
95 => b => 70
60 => c => 40
50 => d => 25*
*at 25 you’re probably going to have to reboot after about two days
Recommend values in bold
The other is the automated purge cache controlled, extreme performance approach:
3072 => a => 2048
95 => b => 70
60 => c => 40
10** => d => 1***
**Need to run a script to purge cache every 22-30
*** Need to run a script to purge cache every 10-16
Personal recommendation for most people (no manual flushing required):
dirty_ratio = 90
dirty_background_ratio = 55
vfs_cache_pressure = 20
If you are willing to play around with manual or timed flushing I think you can squeeze a little more performance and battery life with:
dirty_ratio = 90
dirty_background_ratio = 70
vfs_cache_pressure = 1
A lot of this stuff is subjective and very dependent on your usage pattern. I've gone about 3 days with the latter without having to flush and probably could have gone a lot longer except i was running some other experiments that caused my phone to reboot.
-------------------------------------------------------------------------------------------------------------------------------------
thanks I really needed this thread
Glad to hear it helped. I will be adding to it this weekend hopefully if I can escape from work...
Sent from my DROIDX using XDA App
Your example of a semicolon turned into a winky face instead of a ( ; ). Might wanna put a couple spaces in there for the noobs
Sent from my DROIDX using Tapatalk
zwade01 said:
Your example of a semicolon turned into a winky face instead of a ( ; ). Might wanna put a couple spaces in there for the noobs
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Haha, oops. Thanks for catching that. Think I fixed it... But dont think it shows up with the same formatting on my phone, so I cant tell.
Sent from my DROIDX using XDA App
<-- n00b
So I rooted my phone and tried to install a rom with rom manager and nothing happened. I tried manually and no roms appeared in the boot menu. Soooooooo my question is, do I need the bootstrapper app in order to install roms?
Sent from my DROIDX using XDA App
angryjello said:
<-- n00b
So I rooted my phone and tried to install a rom with rom manager and nothing happened. I tried manually and no roms appeared in the boot menu. Soooooooo my question is, do I need the bootstrapper app in order to install roms?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Yes, you do.
Sent from my DROIDX using Tapatalk
angryjello said:
<-- n00b
So I rooted my phone and tried to install a rom with rom manager and nothing happened. I tried manually and no roms appeared in the boot menu. Soooooooo my question is, do I need the bootstrapper app in order to install roms?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I think if you press on "flash clockwork" that you dont necessarily need bootstrap recovery, as it is built in.
I personally only use bootstrap recovery as you can still do backups/restores, and install themes and Roms. Just one less step in my opinion. I just manually download the ROMs or themes and move them to my sdcard.
Sent from my DROIDX using XDA App
SysAdmin-X said:
I think if you press on "flash clockwork" that you dont necessarily need bootstrap recovery, as it is built in.
I personally only use bootstrap recovery as you can still do backups/restores, and install themes and Roms. Just one less step in my opinion. I just manually download the ROMs or themes and move them to my sdcard.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
alright so i downloaded a rom from romManager but it won't load it from the app. I located the file on my sd card:
clockworkmod/www sephtin.com/rubix/rubiX.js
Now can i just zip the rubiX folder and do a manual boot to it?
angryjello said:
alright so i downloaded a rom from romManager but it won't load it from the app. I located the file on my sd card:
clockworkmod/www sephtin.com/rubix/rubiX.js
Now can i just zip the rubiX folder and do a manual boot to it?
Click to expand...
Click to collapse
Um... I'm not super familiar with ROM manager, as I don't personally use it to download ROMs, but from what I know, that looks like a javascript file, and not a .zip for a ROM or theme installation. This looks more like a script that sephtin may have written... I'm not sure if maybe ROM manager calls a javascript file to install the ROM or not, but to my knowledge, if you download the ROM from within ROM manager, it should be able to install it.
Here is my suggestion (I'm assuming you are trying to install Rubix 1.9.7...
Download the ROM from here:
http://bit.ly/hw6rE8
Then connect your phone to your computer via the usb cable. Put the phone in USB mass storage mode and copy the file you downloaded to your SDcard.
Before installing the ROM, use one of the free apps from the market to backup your SMS messages if you don't want to lose them. Also download Titanium backup to backup your applications and data if you don't want to lose that as well. As for your contacts, if you don't have those backed up to your google (gmail) account, then those will be wiped out as well with the Rubix installation.
Then if you haven't already... download Droid X bootstrap recovery and install it. Open the app, and press the top button to hijack the boot process. Then press the "reboot recovery" button to reboot into bootstrap recovery. When the phone reboots in bootstrap, use the volume up/down buttons to move the green highlighted selection, and the camera button the phone to make your selections. Go to the option that says "Wipe data/factory reset, and do this use the camera button to select this (this will wipe out all the downloaded apps and user data on your phone). Next, use the back arrow button on your phone to get back to the main menu if necessary. Browse to install .zip from sdcard, then locate the Rubix file that you copied to your sdcard and use the camera button to select it. This will then install the Rubix ROM. when it finishes, it should bring you back to the main menu, but if not, use the back arrow button on the phone to get back to the main menu. Choose the "reboot system now" button and it will reboot normally.
From the first reboot after installing, it may take SEVERAL minutes before the phone actually boots up, this is normal; give it some time and let it do its thing. If it does not boot up after 15 minutes, something is wrong, and you should post back here for more help (or browse on the forums and google, they are both your friend).
Good luck!
@SysAdmin-X thanks alot bro i was trying so hard to find that file on the web. Must have not been looking hard enough!
angryjello said:
@SysAdmin-X thanks alot bro i was trying so hard to find that file on the web. Must have not been looking hard enough!
Click to expand...
Click to collapse
No problem at all, im glad I could help. Post back if you have more questions
Sent from my DROIDX using XDA App
So I backed everything up, hit the top and bottom buttons on the bootstrapper app.
took me to the bootstrap recovery. I wiped all the data, then i selected install from zip. Selected the rubiXFocused1.9.7.zip, and the this happened:
Can't Open rubiXFocused1.9.7.zip
(bad)
installation aborted...
Not Good, any idea why?
Great guide for noobs and for-getters like me.
Is their any reason why you don't also include Maderstcok's SBF method ??
Personally I use it every few weeks especially when jumping Rom's so much.
Thanks for all you do.
Ps when I see someone "new" this is one guide that I refer them too.
kdkinc said:
Great guide for noobs and for-getters like me.
Is their any reason why you don't also include Maderstcok's SBF method ??
Personally I use it every few weeks especially when jumping Rom's so much.
Thanks for all you do.
Ps when I see someone "new" this is one guide that I refer them too.
Click to expand...
Click to collapse
Thanks, I havent included Maderstcok's yet just cuz I havent gotten to type it up =( plan is to get that and hopefully a lot more info.thrown up there this week!
Appreciate you referring people here! My plan is to make this a one stop guide for all the basics at a minimum.
Sent from my DROIDX using XDA App
angryjello said:
So I backed everything up, hit the top and bottom buttons on the bootstrapper app.
took me to the bootstrap recovery. I wiped all the data, then i selected install from zip. Selected the rubiXFocused1.9.7.zip, and the this happened:
Can't Open rubiXFocused1.9.7.zip
(bad)
installation aborted...
Not Good, any idea why?
Click to expand...
Click to collapse
Sounds like it might have been a bad download. Try downloading from that link again, if th at doesnt work, here is another link:
http://bit.ly/ga0ejk
Sent from my DROIDX using XDA App
SysAdmin-X said:
Sounds like it might have been a bad download. Try downloading from that link again, if th at doesnt work, here is another link:
http://bit.ly/ga0ejk
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Alright bro it worked for sure now! I got it up and running, thanks so much for this op and all the extra help!
I have figured out a way to permanently install ClockworkMod Recovey on your hybrid WebOS/CyanogenMod Touchpad. Like many of you, my ClockworkMod installation failed when I tried to install using ACMEInstaller while I also installed CyanogenMod.
I realize there is now a workaround to "inject" ClockworkMod into your TP using novacom however this requires you to utilize a computer everytime you want to boot ClockworkMod. Follow the instructions below to install ClockworkMod onto your TP permanently and free yourself from your PC!
1. Boot into WebOS
2. Mount TP to your computer and create a "cminstall" folder if it no longer exists after your CyanogenMod installation
3. Copy the "update-cwm_tenderloin-1012.zip" file into the "cminstall" directory, then unmount TP from computer
4. Download the "Internalz Pro" program using the "Preware" application in WebOS if you haven't already (Google is your friend if you get stuck here)
5. Open "Internalz Pro" and navigate to the "boot" menu (will most likely require you to tap the top-most icon of a folder with two dots next to it to get to the root of the TP - should be second folder down)
6. Tap on the file "uImage.ClockworkMod" and select "move"
7. Navigate to the "media/internal/" directory and click "select" to move file
8. Now tap on the file "update-uimage" and move the file to the same "internal" directory you did in step #7
9. Exit from "Internalz Pro" and reboot device while holding down the up volume key, which will take you in to WebOS Recovery (or select WebOS Recovery when you get to the moboot screen you may have previously installed) - you should now see a large USB icon and should be connected to your computer using a usb cable
10. Go to your command prompt in Windows and navigate to the menu where you have novacom installed - you should also have the ACMEInstaller binary file copied into this directory by now (If you don't know what I'm talking about, remember Google is your friend)
11. Type in "novacom boot mem:// < ACMEInstaller" in the command line and press enter
12. You should now see ClockworkMod recovery installing on your TP - Once it reboots into moboot select "boot ClockworkMod" and watch it boot into ClockworkMod!
13. After celebrating, boot back into WebOS, go into "Internalz Pro" and move the file "update-uimage" back into the "boot" directory - the "uImage.ClockworkMod" file that you put in the "Internal" directory is no longer needed since you reinstalled ClockworkMod properly
Essentially the boot directory was overloaded which caused for insufficient space when installing ClockworkMod. Now you should be able to boot into WebOS, CyanogenMod, WebOS, AND ClockworkMod Recovery without a computer. As always, I do not take responsibility for you bricking your TP or variability you may have... use this information if it is helpful but don't blame me if something goes wrong. I'm just trying to help out the community that has helped me for so long.
Let me know if this is helpful to you. Thanks!
dseelye
What!?
Hi!
firstly, thank you for making this guide, i know that alot of people like myself will appreciate it.
but i've run into a problem, see, now i don't have the option to boot into cyanogenmod anymore !
can i flash it in clockworkmod, or do i have to do it all over again?
a reply would be appreciated
you most likely copied the wrong file from the boot folder, as there was one for clockworkmod and one for cyanogen mod... look and see if you incorrectly copied the cyanogenmod "uImage.CyanogenMod" to your internal sd card to free up space. You will have to move this back to the boot folder and grab the other one.
Thank you VERY much!
and thanks for the INCREDIBLY quick reply!
EDIT: IT WORKED!!! YOU'RE THE MAN!!!!!
No problem... let me know if that solved your concern...thx
EDIT: Oh, just saw the edit of your post...great, glad that was it!
Just wondering... how permanent is permanent?
For instance, if I use "web doctor" to restore my touchpad, will the recovery be overwritten?
Yes, I just mean that you don't have to "inject" clockworkmod into your TP using your computer which was the workaround for the people who couldn't get it installed originally during the CyanogenMod installation. This just installs it properly but can be wiped with WebOS Doctor like anything else...
bigblueshock said:
Just wondering... how permanent is permanent?
For instance, if I use "web doctor" to restore my touchpad, will the recovery be overwritten?
Click to expand...
Click to collapse
Yeap... it will not delete a single bit of CM7, just gonna restore the original bootloaders, delete moboot and skip CWM /Android on boot...
Running again ACME with only moboot and CWM in the cminstall folder will restore them.
....After WebOS doctor... it will show CM7 as the last time you shut it down.
Sent from my GT-I9000 using XDA App
I followed directions exactly but I am not seeing the uImage.clockwork in the boot folder. Any suggestions? I see that file in the cminstall folder, do I just leave in there or should I copy directly to media\internal?
Sent from my SPH-D710 using xda premium
The "uImage.ClockworkMod" may not be in the boot directory I suppose if the previous install attempts didn't put it there so not sure why it isn't in yours. Essentially you are just trying to move some of the larger files out of that directory so you can install ClockworkMod properly as the space constraint of the partition size seems to be the issue. The other file I mentioned, "update-uimage", is actually the largest one I found and you may be able to do the ClockworkMod install properly by only removing that one temporarily. Let us know if you are able to resolve.
I've installed clockworkmod recovery with no errors on the first try, is it advisable that I need to use this method?
I was installing cwm for the first time. I didn't include it originally with the install of cyanogen mod, I guess that's why it wasn't in the boot folder. I placed both files in the media\internal directory and also inside the cminstall folder and ran the command and it worked fine. When I checked internalz pro to remove the files, the cminstall folder and uimage files were gone already. So it looks like I am good to go. cwm is working, I flashed gapps from it. Thanks for reply.
Now I just need to figure out how to make phone calls.
Sent from my SPH-D710 using xda premium
If you installed ClockworkMod completely the first time and it works, then you definitely don't need to do this as this thread was intended for those that tried to install it at the same time as when they installed CyanogenMod and ClockworkMod Recovery didn't install properly. These instructions are to outline how to get it installed correctly as just trying again using ACMEInstaller wasn't working for anyone due to the small size left in the boot directory.
hey thanks for the fix but after the fix i cant get into the market
Not sure why you can't access the market...no issues here. I would suggest reinstalling the gapps zip file and possible the market fix file that are out there now that you have clockworkmod working properly.
thanks for the help thats what i had to do
Hi, the "move" option isn't available, only "copy" "info" and "open"
The entire directory is "view-only"
Not sure why "move" isn't available for you... its been a while since I installed Preware and Internalz Pro so I must have gotten root access somehow and that's why it shows up for me and others. I'd suggest searching for how to obtain root access to WebOS to find your answer... possibly development mode if you haven't already done that but I thought that was required to get Preware installed in the first place.
Move command
dseelye said:
Not sure why "move" isn't available for you... its been a while since I installed Preware and Internalz Pro so I must have gotten root access somehow and that's why it shows up for me and others. I'd suggest searching for how to obtain root access to WebOS to find your answer... possibly development mode if you haven't already done that but I thought that was required to get Preware installed in the first place.
Click to expand...
Click to collapse
I have the same problem. Move/delete commands are available on the media/internals but on boot folder move is not available.
Thanks
Awesome man! Been struggling with this since two days. Thanks a lot for the fix and step by step instructions
---------- Post added at 09:07 AM ---------- Previous post was at 09:00 AM ----------
tmkhan said:
I have the same problem. Move/delete commands are available on the media/internals but on boot folder move is not available.
Click to expand...
Click to collapse
After Opening "Internalz Pro", Open "Preferences", scroll down to the bottom. You will see an option called "Master mode". Turn it on. You will get read/write access to the boot folder.
[SCRIPT] No-lag solution to CM7/9 "low memory" notifications (STEP BY STEP,FIXED TB)
23/01/12 - Now with Titanium Backup support!
The Titanium Backup team is awesome. I contacted them and within 3 days they had a working fix. To make sure that titanium backup works properly all you need to do is download the latest version from the market, go into 'preferences' and select 'follow all symbolic links' in the 'Troubleshooting' section at the bottom. That's it. Now you'll be able to backup normally and then restore your apps in any other rom. Neat!
Click to expand...
Click to collapse
Okay, I've found a rather excellent solution to the low storage problem that plagues the CM7 and CM9 roms - without causing the lagginess of the ".nodatadata" approach. It's not my work but was posted by drefnel on the Cyanogenmod forum. It's very smart: instead of moving the whole of /datadata (fast yaffs2) to /data (slower ext4) and so introducing lag it keeps most apps' non-performance critical data on /data and moves performance critical sqlite databases and xml preference files to the fast /datadata.
Installing this fix is a two step process:
Phase 1 - some prep, takes around 10 minutes to complete. Only has to be done once.
Phase 2 - running the script whenever you've installed new apps and used them once or twice. this just involves hitting a shortcut on your home screen. boom!
The original guide can be found here we need to make a few alterations and I've done a step-by-step below:
Step by step guide
I take no responsibility if using these instructions messes up your phone. They worked for me and you should always be able to restore using the clockworkmod backup. But you can't say you haven't been warned.
Make sure you're running CM7 or TeamHacksung's CM9 or Onecosmic ICS.
This will NOT work on encrypted phones.
DO A NANDROID BACKUP BEFORE YOU BEGIN.
Phase 1 - (if you've already used the ".nodatadata" method then start at step 4)
1. Download Terminal Emulator
2. Open terminal emulator and then enter each of the following followed by return:
su
touch /datadata/.nodatadata
3. Reboot (this might take a while as the OS will be making changes to your filesystem).
4. Open terminal emulator and then enter each of the following followed by return:
su
rm /data/data/.nodatadata
5. Reboot into recovery, go to "mounts & storage" and then select "format datadata". Reboot normally.
6. Go to the market and download GScript Lite. Open it and close it again - this should create a folder called "gscript" in your sdcard. Unzip the file attached in this post and place the script in it in that folder.
7. Open up GScript Lite, press menu and add script. Click load file, select the script file, make sure that "needs SU" is selected and click save.
8. Run the script by tapping it. You should see GScript report its progress and finally the script should finish. Press close and gscript will crash out (can't have it all ).
Phase 2
Add a shortcut to this script on your desktop.
CM7 - long-press and hold a blank area of your home screen, select 'add shortcut', and then select 'gscript lite'. select the script you've just added.
CM9 - go into your app drawer, select the 'widgets' tab, find 'gscript lite', press and hold it and move it onto your home screen. select the script you've just added.
You should use the shortcut after you've installed new apps and used them a few times. There's no harm in not using the script for a while, all that will happen is that app may become a bit laggy until you use the script to move its data to /datadata.
That's it. Congratualtions!
You can flash new CM roms and the script will carry on working fine, but if you wipe data in recovery then you'll have to start from the beginning
You won't be able to easily go back to the original configuration or use the ".nodatadata" method (you'll need to Titanium Backup, wipe everything and then restore), but you'll never miss them.
Good luck
I hope this helps people out. We should find a way of better automating the steps to make it more noob friendly and maybe Team Hacksung and One Cosmic could incorporate it into their ROMs. (Essentially the script needs to be run periodically to make sure that the performance critical /data/data elements of new apps are copied across to /datadata - apart from that it's not too different from the ".nodatadata" approach).
Personally using the much simpler .nodatadata approach, i found that after a rom (cm9) install, most lag goes away after using it for a few hours, although I have heard the speed of the flash memory is not equal on all devices... so could be laggy for some regardles of usage.
Yup I've tried both and the script approach is definitely much quicker in my case. I'm going to see if I can simplify this procedure somewhat.
Sorry for being a noob.. I am not sure how to apply the script to my Android device... Should I use Terminal Emulator on my Galaxy S and type the script in there? Would you mind to guide me through the process? Thanks a lot
Now with a step-by-step guide.
Man you are awesome! Thanks for your guide!
Wouldn't it be an idea tu use scriptmanager (free or pro) instead of gscript? it can run scripts on boot.
Maybe later, when the standard kernel for cm9 will support init.d, it can be an init.d script?
And oh, I will put a link to this thread in the wiki, you can edit the wiki yourself also if you ask for acces.
seem like there is no one try on OneCosmic, and im going it a shot!
will report later~
Zatta said:
Wouldn't it be an idea tu use scriptmanager (free or pro) instead of gscript? it can run scripts on boot.
Maybe later, when the standard kernel for cm9 will support init.d, it can be an init.d script?
And oh, I will put a link to this thread in the wiki, you can edit the wiki yourself also if you ask for acces.
Click to expand...
Click to collapse
Good points. The reason I chose GScript was its user friendliness and simplicity. There are define advantages in running this script at boot. (I'd much prefer to have things run automatically before the GUI appears (as in init.d) rather than clog up GUI boottime as Script Manager would require.)
The phenomenal uptime I get with Android means that I don't reboot very often. Ideally we'd want something that monitored the data/data folder and ran the script on the appearance of new folders. I'm not sure how you'd automate that without resorting to Tasker. Maybe init.d is the best we can do when it's supported. In the meantime a GScript shortcut on the desktop that I hit once every couple of days feels like the best option so far!
Sent from my GT-I9000 using XDA App
Code124Y said:
seem like there is no one try on OneCosmic, and im going it a shot!
will report later~
Click to expand...
Click to collapse
Tested on OneCosmic and it working good for all but picture/gallery gone...
what i mean is it scan no photo nor any image on my phone~
using gallery+ giving me the same view(nothing in gallery)
but other then this 2 gallery, im try with quickpic also and yup it show pic~
but i want the original picture gallery from the 4.0.3... any help?
There are more advantages in scriptmanager. You are not bound to a specific location on the scared for example, with gscript it has to be in /sdcsrd/gscript folder. And you can make a widget with this script in it, making it a one-click operation but I believe that is a paid feature (and gscript can do something similar, no?)
On the other hand, it is as you say, a bit more complicated.
Also making it a init.d isn't a full solution. Every update from the ROM will wipe the /system/etc/init.d so the script needs to be reinstalled.
Maybe a cwm-flashable would be needed than, everybody here can flash. In that case also the initial commands could be run during flashing.
Taptalked u see
Zatta said:
...Maybe a cwm-flashable would be needed than, everybody here can flash. In that case also the initial commands could be run during flash
Click to expand...
Click to collapse
Yup, a flashable zip which runs initial commands and then appends on an init.d script seems like the way to go. Once the CM9 kernel supports I'll learn how to make these (essentially lazy, me)
BTW, making a one click operation from GScript is easy. Just add the GScript shortcut to your home screen and it will prompt you which script you want to run on click (remember that shortcuts are now grouped with widgets in ICS)
Sent by airmail.
Code124Y said:
Tested on OneCosmic and it working good for all but picture/gallery gone...
what i mean is it scan no photo nor any image on my phone~
using gallery+ giving me the same view(nothing in gallery)
but other then this 2 gallery, im try with quickpic also and yup it show pic~
but i want the original picture gallery from the 4.0.3... any help?
Click to expand...
Click to collapse
Have you tried clearing the data for the gallery app? Worth a shot.
Sent by airmail.
revthanki said:
Have you tried clearing the data for the gallery app? Worth a shot.
Sent by airmail.
Click to expand...
Click to collapse
not needed already, becoz reboot seem to be fixed...
Samsung galaxy S GT-I9000 miui.us latest rom
I just have a question popped up in my mind, after applying this script,when I update my teamhacksung ROM in the future(i.e the future build15), will it causes any problem / break my phone?
leolee0209 said:
I just have a question popped up in my mind, after applying this script,when I update my teamhacksung ROM in the future(i.e the future build15), will it causes any problem / break my phone?
Click to expand...
Click to collapse
Absolutely shouldn't, as long as pawitp doesn't ask you to wipe data. If he does then you'll have to start again
Flash away!
Sent by airmail.
People, beware that this will break your TitaniumBackup, I was tested myself
Funnnny said:
People, beware that this will break your TitaniumBackup, I was tested myself
Click to expand...
Click to collapse
How do you mean? A bit more detail please. It really shouldn't, as Titanium Backup does respect symbolic links...
Sent by carrier pigeon.
mispost
10 char
Originally Posted by Funnnny<br />
People, beware that this will break your TitaniumBackup, I was tested myself
Click to expand...
Click to collapse
<br />
<br />
How do you mean? A bit more detail please. It really shouldn't, as Titanium Backup does respect symbolic links...<br />
<br />
<br />
Sent by carrier pigeon.
Click to expand...
Click to collapse
When I backup, wipe and restore, titaniumbackup just restore the symlink, not the actual data
Sent from my GT-I9000 using Tapatalk
Hi and welcome Telus Fascinate T959D Users.
The purpose of this thread was to join a few T959D users together. When I flash a ROM I usually have at least 6 posts open on XDA - on different methods, kernels, etc. So I started collecting information and organizing it here. I have been updating based on feedback and adding more and different content especially when more users found us here.
Special thanks to everyone who has helped with this thread over the past few years - and special call outs to @Matt5606, @iwebsource, @finneginsfast, @moosehead11, @Dayfid, @karmatose, @bucknetbucky.
However, please note that we the contributors take no responsibilities for your phone or anything you do to it - this is simply a collection of helpful posts to get you started and continue having conversations - they are by no means offered as full proof guides, nor do they imply a warranty of any sort.
Now on the fun stuff, but first a simple FAQ.
Q. What is the T959D and what ROMs can I use on it?
The T959D is Telus' Galaxy S phone - known as a fascinate. What is confusing is this phone has almost nothing in common with the Verizon Fascinate - in fact flashing a fascinate ROM will brick your phone. Fortunately for us, our phone is VERY close to the International Version - the i9000 or galaxysmtd. Those are the ROMs we use on this phone.
Q. Is there a place where I can get files for my phone?
Yes - all through XDA you can use i9000 compatible ROMs, Kernels, modems. As well, we have a stock pile of files available to you - as you read the OPs you will find those and how to get them.
Q. Can I brick my phone?
Yes - but from my personal experience it is very hard to do this, and you can always get a USB jig that gets you to download mode (if you are soft bricked) - load one of the stock images and you are right as rain again.
A USB jig is a small piece of modded hardware that plugs into your USB port on your phone and forces it into download mode on start up - EVEN if it is SOFT BRICKED. A necessity for flashing. Lots of 'how tos' on how to create them out there if you have a spare cord, or just order one on EBay
http://www.ebay.com/sch/i.html?_nkw=usb+jig
For me, the place to use the most caution is using Odin - when placing files into the fields ensure they in the right place (measure twice, flash once ) as that is the biggest risk to flashing your phone. I think this is the greatest risk to hard bricking your phone which I am not sure you can recover from (I have only ever soft bricked my phone in which the USB jig saved my hide).
Q. I put on an ICS/JB ROM and now my IMEI is gone? What is that and how do I get it back?
Your IMEI is the unique identifier on your phone. The number is written down behind your battery - and that is what your phone should be displaying when you go to About Phone in Settings. Something happened with ICS/JB that it sometimes gets lost. To prevent that you need to back up your EFS folder.
1. You must be rooted.
2. You must have a file explorer that has root access (root explorer or ES File Explorer - although, if using ES ensure you have enabled root access and mounted /system in the preferences.
3. Find your /EFS/ folder at root (/).
4. Copy the EFS folder. Ensure you have ALL the files and ALL the subfolders (one will your IMEI). However, there can be hidden files in here, I would not worry so much about those, simply ensure you copy over the EFS folder itself - that should do it.
5. Move this to your removable SD card. Zip it, keep it on your PC, put in dropbox, ensure you have a copy for safe keeping.
And that is it - after flashing a new ROM, if you are missing your EFS or your IMEI number if wrong, just copy back the folder, reboot, and voila!
Q. GPS sucks.
Yes, yes it does. Do a search if you are adventurous there are hardware fixes. There's also faster fix in the play store and there are files here you can load as well - but its a known issue with the Galaxy S family of phones.
Q. What should I run on my phone?
Well, that is entirely up to you. The last official firmware you can get is 2.3.3. If you like very stable and do not need to have the latest, just a stable working phone with great battery - maybe try a good gingerbread ROM like Darky's or CM7.0 - Darky's will give you that Samsung feel (and still have the right firmware for the camera).
There are literally tons of options - go to the i9000 thread and see what the latest is. Most users here in this thread are on SlimICS, SlimBeam, CM10 or CM10.1. I have been running latest (nightlies) CM10.1 for some time combined with my favourite kernel Semaphore.
If you are going to flash a new JB ROM though, I suggest as your first flash stable CM 10.0 - this will be the base of your next ROM and many ROMs such as slim recommend you flash CM first just to set things up for yourself.
Q. So what now?
Read, read, and read. Go through this thread - go through threads of the ROMs you want to install - see what users are saying about it lately. And please - come to this thread and ask questions - we have a small but friendly and very helpful community - and remember if we help you, stay active on the thread so you can help someone else.
Cheers - and happy flashing
ICS/JB ROMS from Scratch (updated May 31 2013)
THANKS to @karmatose and @Dayfid for creating an ODIN flashable 2.3.3 - this means no more KIES (yes!) and creating a fresh stock ROM - here's the steps for this procedure... (Updated September 26, 2012)
Please note that the links below provided by Karma http://t959d.karmatose.org will work BUT you will need a username and password to download the files. Karma or myself can make the login and password available to you.
1. Download the KG2 package from here - http://t959d.karmatose.org/index.php/apps/files/download/Shared/stock_roms/T959TLKG2_Gingerbread.zip
2. Extract the archive to a folder on your PC using your archive app of choice. Mine is WinRAR.
3. Open Odin3 v1.7.exe (the one that is in the ZIP file)
4. Place the PDA, CSC and PHONE and PIT files in the proper boxes. Take absolute care to make sure you don't mix them up. Ensure that repartition is ticked 'on' in this case.
5. Put phone in download mode (vol down + power from off or download jig) and connect it to the PC
6. Click start and wait just under 3 minutes. The phone will restart and you should be back to stock 2.3.3
7. If your intention was to get to stock, you're done. If you want to go to ICS/JB and you *don't* have a backup of your EFS folder, go to step 8. If you do have a backup of your EFS folder, go to step 10.
8A. If you need to backup your EFS folder (HIGHLY RECOMMENDED), you need to root the phone. Flash the Speedmod kernel with ODIN (in the PDA field). The phone will reboot and get stuck in a boot loop at this point. Pull and replace the battery and place the phone in Recovery Mode by holding VOL+ and VOL- and pressing the power button. When the screen lights up, release the power button and continue to hold the volume rocker until you see CWM Recovery. Using the Vol+ and Vol- to navigate the menu, go to the Speedmod Advanced Options menu and press the power button to select it. Choose to root your phone.
8B. (Optional) Now that you have custom recovery, would not be a bad idea to make a nandroid backup of your phone. So go to backups, and create backup from the CWM Menu.
8C. Once that is complete, go back to the root menu and reboot the phone. Pull the battery out and put the phone back into download mode. Flash the stock 2.3.3 kernel back (also in the PDA field) in Odin. The phone should now be rooted. Let it boot. Hopefully you're greeted with a lock screen
9. Install ES Explorer from play (or APK), enable Root Settings in the settings menu then navigate up to root and copy your EFS folder to your EXTERNAL_SD card. Power down the phone, remove the SD card and copy this to your PC, Google Drive and some other backup source. Don't lose this folder.
10. Installing ICS / JB - Depending on what OS you want to go to, you're going to need to grab an appropriate kernel to do so. The best option seems to be Semaphore's i9000 kernels. If you're going to flash an ICS rom, grab the 1.3.0s .tar file. If you're going to JB, grab the 2.1.0s .tar file.
11. Download your ROM of choice. i9000 versions of SlimICS/SlimBean/CM9/CM10 work on the T959D. You will also need grab the .zip version of the Semaphore kernel (ICS / JB) you're using and a Modem of your choosing. KG3 works best for me, your mileage may vary. Place the ROM, .zip version of the Semaphore kernel you're using and the ES File Explorer APK on your internal SD card.
12. Open Odin again. Put the .tar'd Semaphore kernel file you just downloaded in the PDA field, ensure Re-Partition is UNCHECKED. Put your phone in download mode, connect it to the PC and click start. In a bit more than 10 seconds, your phone should reboot itself. Pull the battery out and replace it.
13. Put the phone in Recovery Mode by holding VOL+ and VOL- and pressing the power button. Release the power button as soon as the screen turns on but keep holding VOL+ and VOL- until CWM appears. Use the VOL+/- keys to navigate, PWR button to select. Go to "Install zip from sdcard", then "choose zip from internal sdcard".
14. Follow the directions to install your ROM. CM9/10 comes in one flashable .zip file whereas SlimICS/SlimBean comes in multiple files. Consult the documentation for your ROM to get specifics on how to install it. Note that if you are installing CM10, CM10.1, Slim 3.x + that the partition layout has changed. This means you will need to flash the ROM at least 3 times - once you will get an error 7, then flash again, and then again - after that you will have latest.
15. Once the ROM is done flashing, flash the Kernel .zip you placed on your External SD card the same way you flashed the ROMs. Then flash your modem .zip. Note that if you are using an 's' version of semaphore, and a non-patched ROM like CM (Slim is already patched) you will want to flash the big mem library patch which is attached below after flashing the kernel.
16. Go back to the CWM main menu and reboot the phone. You should boot into ICS / JB at this point with no issue. It might take a bit so be patient.
17. Verify your IMEI number. Hit the Menu button on your phone and select System Settings > About Phone > Status. Look at your IMEI. If there's a lot of 0's in it, you need to replace your EFS folder. Use Oi Explorer to access your External SD card and install the ES File Explorer APK. Enable *all* the Root options in the application settings and return to the file browser. Locate your EFS folder backup on your external SD (emmc), longpress on the folder and select "Copy To". Hit the navigate up button in the dialog box and select /. Press OK twice then reboot your phone. Your IMEI should be back to normal now.
18. Enjoy the fruits of your labour and customize the heck out of your new ICS / JB rom.
----
This is an alternate method from @bucknetbucky created this quick 'how to'. This will put you on stock GB and allow you to flash ICS from there.
Why start from GB? The bootloaders. When flashing from froyo you'll see lots of tips on pulling batteries and the first flash always not working - this won't happen from Gingerbread AND you'll get to keep the logo for the kernel for some added bling.
For those looking to flash from GB here is how to do it...
Get back to 2.3.3 stock
1 flash stock froyo via ODIN (tick repartition! - See the 'Essential Files' section above).
2 install samsung kies (should have this if you have this device- AND update it!)
3 update to GB using kies
Root your phone and back up EFS
Backing up EFS is vital. Essentially do this.
4. Download Super1click to root your phone and following the instructions (http://depositfiles.com/files/n0dcxce3t)
5 Install a file manager with root access and backup your efs folder by copying it to the internal sdcard then your computer (instructions in OP)
Note: this is one way to root your stock GB phone - you can also use the speedmod kernel (the version I use is older --- but works --- and is attached below) which has a root option under 'advanced' but has more steps. If you already have backed up your EFS though, you really do NOT need to do this step and skip to the steps below to flash your ICS ROM.
Finally INSTALL your ICS ROM
Now to flash the latest super duper ROMs from the super duper devs you will need to do the following...
1 copy glitch v14 kernel and the rom of your choice to your internal sdcard (The version linked below is the BEST version to accomplish this with)
http://www.box.com/s/tov06pvzkkqbmui6tcmi
2 flash via ODIN the speedmod kernel (gives you a custom recovery)
3 when it tries to boot pull the battery and then boot to recovery
4 flash the glitch kernel from recovery (again you are boot looping)
5 pull the battery and boot to glitch recovery and wipe data, clear cache and such then flash your ROM
6 copy your backed up EFS folder back to the phone to restore yout imei
Just some notes
Most ROMs will come with a compatible modem, however, if having modem issues - please see a few posts down on getting modems.
A complete list of ROMs for the I9000 by Android version can be found here (as well as kernels). Please note the update dates as that will indicate how much active support there is for the ROM.
http://forum.xda-developers.com/showthread.php?t=1837223
Gingerbread ROMs (Updated 03/11/2012)
In terms of loading GB ROMs I have had success with a few - namely Darky ROM (up to 10.4.2).
Credit to the original poster, but I always start with this how to on loading a ROM.
http://forum.xda-developers.com/showthread.php?t=923712
I do not execute every step, but essentially use it to get to stock along with the custom voodoo kernel which will give you root and custom recovery to load your custom ROM.
ROM and Kernel TWEAKS (Updated 08/28/2012)
GPS Tweak
This how to can you help you tweak GPS
http://forum.xda-developers.com/showthread.php?p=17081413
Note the multiple GPS.conf entries you can have for country (Canada) as well as region (North America).
Darky ROM tweak
When installing Darky ROM you will find the buttons for home and back no longer work. There is a simple fix for this as long as you have a root explorer (like ES File Explorer) and a text editor.
Open up /system/usr/keylayout/melfas_touchkey.kl in a text editor.
Make sure that your 'keys' look like this:
key 139 MENU
key 158 BACK
key 217 SEARCH
key 105 HOME
key 106 SEARCH
Keep VIRTUAL as part of the keys and you will still have vibration as well.
Alternatively (Thanks @finneginsfast !) you can flash 'keylayout.zip' attached below from recovery.
Flashables (Updated June 29 2013))
This is reserved for flashables such as modems and kernels.
Ultimate Kernel Cleaner
Before flashing a kernel, you should run a kernel cleaning script. Matt (THANKS @Matt5606) gave me this one - it handles cache cleaning, etc. See the attached file for ultimate kernel cleaning script.
Modems
Lots of modems out there, and get Perka's file store for a ready list (see recommended apps). My favourite for a long while has been the i9000UGKC1 modem - it has GB versions as well as ICS - just make sure you get the right one!
You can also download modems diredctly from Perkas Site (/Samsung/ICS_CM_Modems/850_Modems_CM) or the android app (available in Play). Ensure you get the right modems for your ROM or Android version.
For Gingerbread: /Samsung/I9000/Modem_850_Enabled
For ICS and JellyBean: /Samsung/ICS_CM_Modems/850_Modems_CM
@finneginsfast provided me with this graphical link to help give you an idea of what modems work where: http://soggycashew.weebly.com/modem-location-map.html
Gingerbread Kernels
Semaphore. Great kernel to run with DarkyROM.
http://forum.xda-developers.com/showthread.php?t=1112908
Glitch Kernel. Great kernel to run with CM7 or MIUI GB as its made for our model!!!
http://forum.xda-developers.com/showthread.php?t=1315400
ICS Kernels
I run Semaphore almost exclusively - definitely a favourite.
http://forum.xda-developers.com/showthread.php?t=1468795
Glitch has a specialized kernel for ICS as well, but I typically do not use it.
http://forum.xda-developers.com/showthread.php?t=1459475
JellyBean Kernels
Semaphore has a JellyBean kernel for 4.1.2 as well as 4.2.2 - its my go to kernel.
http://forum.xda-developers.com/showthread.php?t=1786220
Be sure to get the LMK app from XDA (search it) to ensure your launcher and keyboard do not die, and get Semaphore manager from the Play Store as well.
Recommend APPs (Updated 09/28/2012)
Launchers - ICS/JB
- APEX Launcher (free and paid, on Google Play)
- Nova Launcher (free and paid, on Google Play)
- Holo Launcher HD (free and paid, on Google Play)
Launchers - 2.x
- Launcher Pro (free and paid - better widgets with paid - Google Play)
- GO Launcher (totally free - lots of great supporting apps - Google Play)
- ADW (free and paid, Google Play)
- Holo Launcher (free and paid, Google Play)
Keyboards
- Swift Key X (trial and paid, Google Play)
- Swype (trial and paid, Google Play)
File Management & Files
- ES File Explorer (Free, has root explorer - Google Play)
- Perka's File Stash Free and Donate - excellent file resource for modems - Google Play)
Other Stuff
Essential Files
Before we get started wanted to make available some essential files. These are from my public dropbox folder, so I may switch it in time, but felt they should be here.
Need to get back to stock, then here is the Stock Telus Froyo 2.2. http://dl.dropbox.com/u/2069701/T959TLJL3.zip
Want stock with a CWM kernel on 2.2, then here is the VooDoo Kernel http://dl.dropbox.com/u/2069701/voodoo.advanced.v666.2-20110111-21.53.tar
Remember when flashing back to stock to tick the re-partition box, and place the files as follows:
- s1_odin_20100512.pit in "PIT"
- T959TLJL3-REV03-ALL-low-CL763100.tar.md5 in "PDA"
- T959TLJL3_FROYO_Phone-CL763100.tar in "PHONE"
- SGH-T959D-CSC-TLSJL3.tar.md5 in "CSC"
Additionally, Karma has some core files he is posting as well (Thanks @karmatose !!!) and you can find those files at:
http://t959d.karmatose.org
To access the files, you will need a login. @karmatose or myself can make the login and password available to you.
Starting Fresh
Buck provided this a while back. This is recommended after many flashes and you want to start out fresh without lingering script files and other crap we're all guilty of installing/flashing
WARNING: This clears up EVERYTHING - even TB backuped programs - so if you want your TB backups, change your backup location to the REMOVABLE SD Card.
If you want to start fresh and i mean bare bones this is how i do it.
1. Remove the external sd card (the one you put in the phone)
2. Go into storage under settings and unmount then format the sd card (the partition the phone makes that you see if you do not have root)
3. Flash stock rom via odin and repartition ofcourse.
4. When you are done the phone will be like you just took it out of the box.
5. Backup the card you took out and format that. Leave it out.
6. Grab some beers and start flashing whatever you want (except the neighbors they dont like that)
Awesome thread, subscribed!
Sent from my GT-I9000 using XDA
Do I have to root my phone after installing GB . Or I can wait
And witch app is the better to backup the EFS folder
You need to root to back up your EFS... so for that. Then use root explorer or ES to copy that folder over to your SD and computer.
If you ES make sure turn on root explorer and mount /system.
Sent from my GT-I9000 using xda premium
In Odin witch slot (PDA,PHONE,CSC,BOOTLOADER) that i put the file speedmod-kernel-k16-11 . and the other one
Pda
Sent from my GT-I9000 using xda premium
there is no root option in the recovery mode after i put the speedmodkernel
nevermind lolll
I've been lookin at that procedure and you root through recovery with the speed mod kernel? I'm pretty sure you can root while on stock GB without all that hassle by just using SuperOneClick.
Sent from my GT-I9000 using XDA
Thx a lot JP for this thread!!!! . I m now part of the ICS community . Only one thing my IMEI number inst the same was its written under my battery . I copy back the EFS folder tho . Does it change something ???
---------- Post added at 08:38 PM ---------- Previous post was at 08:37 PM ----------
Matt5606 said:
I've been lookin at that procedure and you root through recovery with the speed mod kernel? I'm pretty sure you can root while on stock GB without all that hassle by just using SuperOneClick.
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
I finally found it but thx for the feedback
If you remembered to copy your efs folder before the flash, just copy the original folder back into your phone replacing the old files and reboot. You should have your number back.
Sent from my GT-I9000 using XDA
Yeppers
Sent from my GT-I9000 using xda premium
So get yourself the semaphore kernel and nova launcher and you are all set
Sent from my GT-I9000 using xda premium
it did not change my IMEI numbers?? .what is that kernel do (Semaphore) and how to install it odin??
jpmccarthy said:
Darky ROM tweak
When installing Darky ROM you will find the buttons for home and back no longer work. There is a simple fix for this as long as you have a root explorer (like ES File Explorer) and a text editor.
Open up /system/usr/keylayout/melfas_touchkey.kl in a text editor.
Make sure that your 'keys' look like this:
key 139 MENU
key 158 BACK
key 217 SEARCH
key 105 HOME
key 106 SEARCH
Keep VIRTUAL as part of the keys and you will still have vibration as well.
Click to expand...
Click to collapse
Or you can install this zip from recovery, I think it's the same fix or at least it's what I've been using for a while.