Database Users

Devs Need volunteers that are using 1.5

This is a call to arms for anyone still running 1.5 on their eris. We (developers) need people to capture the update process using wireshark (or an equivalent). This is needed for a new root attempt, but sadly all of the devs have already updated to 2.1 so we can't do this.
First go here and download the RUU:
http://www.pcdphones.com/downloads/Eris%20MR1.zip
Next you need to go to verizon's website and login to your account. Click "Suspend/Resume Service" and suspend your phone. You can resume service on the phone after you are done here with no penalties or charges.
Please follow these directions, taken from the first root thread
bftb0 said:
Steps:
[Binny knows this, but if anyone else is reading, it is the same as a factory reset - you will lose all your settings and apps (but not the contents of the SD card)]
1) Unpack the 1.16.605 RUU - by running it as if you were going to actually do the RUU using the USB cable and your host PC, but stop right before you would apply the update to the phone. Pull the "rom.zip" file out of the temporary area that the RUU installer unpacks.
(Poke around under C:\Documents and Settings\<Username>\??? (I can't remember - you'll see folders with names that look like registry entries). You have to do this while the RUU installer is sitting there waiting for you - if you cancel the install, it will nuke everything it unpacked. I just made copies of the entire subtrees.
2) Cancel the RUU install.
3) Move the ROM.ZIP file to the root folder of your SD card, and rename it PB00IMG.ZIP
4) You can cancel the RUU install session on the PC, and unplug the USB cable if you want (so long as you have a well-charged battery!)
3) Power down the phone, and boot it back up holding the Call and End buttons simultaneously
4) Scroll down (or whatever it asks) to go from Fastboot mode to HBOOT mode
5) The phone will automatically discover the PB00IMG.ZIP file, and unpack it and verify it.
6) It will ask you if you want to install; when you (select and) enter Yes, the phone will reboot, and come up again - appearing as if it is repeating the same thing. This time, however, it won't stop and ask you - it will just begin the install.
7) Wait... Wait... Wait... Wait... and then wait some more. If I recall correctly, it seems to hang a little bit at the HTC splash screen after the reboot. That is normal - just WAIT and let the phone do it's thing.
That's it, except for:
8) You probably will want to dial *228 and choose option 1 to complete the programming of your phone - it will reboot after it completes.
Click to expand...
Click to collapse
After you are done, DO NOT start the OTA update that it prompts you to do.
Now we are going to install wireshark and setup the capture environment:
Download wireshark from http://www.wireshark.org/download.html for your versions of windows
Install it - make sure you also install WinPcap
At this point you should turn off any wireless encryption on your router. I know it's not necessary but it makes it easier to go through the captures.
Setup the wireless on your phone to connect to your wireless router and turn off your mobile data connection.
After you have turned off the wireless security on your router, we are going to start the wireshark capture.
Run wireshark - if you are on vista or windows 7 make sure to run it as an administrator
Click "Capture" then "Interfaces"
Click "options" next to the interface that your computer has an IP for
Make sure to check "Capture packets in promiscuous mode"
In the Capture Filter box, type "host <ip_address>" where <ip_address> is the ip address your router gave your phone
Make sure that "Automatic scrolling in live capture" is checked so you can ensure the capture is working
Click "Start"
At this point, you should browse the web with your phone. You should see lots of stuff scrolling by in the wireshark window.
If there isn't, you messed up something above and should try again.
If there is a lot of stuff scrolling by, continue:
Close the browser
In wireshark, click "Capture" then "Restart"
Reboot your phone
On your phone, go to "Settings" -> "About Phone" -> "Check for Updates" and go through with the OTA update
After the update is done and your phone is rebooted, go to wireshark and click "Capture" -> "Stop"
Then click "File" -> "Save As" and give it a name.
Upload that file to Megaupload, or Mediafire, or some other file sharing site, or any private server that I can get access to.
After you have uploaded the file please message me through the forums with a link to the file.
Thanks a ton.

e-mail me at [email protected] i got my wifes phones todo this to shes still on 1.5

NO need to have a average user do this, guinea pig yourself and roll back down to 1.5 it can and has been done by other devs.

Isn't there a "logcat" line you can run through adb to get the same thing? Like, when the update is available, you can plug your phone into your computer, connect it to terminal using adb and run a logcat to find the address of the update.zip

FireSokar said:
NO need to have a average user do this, guinea pig yourself and roll back down to 1.5 it can and has been done by other devs.
Click to expand...
Click to collapse
You CANNOT downgrade from 2.1 to 1.5.

Videofolife13 said:
Isn't there a "logcat" line you can run through adb to get the same thing? Like, when the update is available, you can plug your phone into your computer, connect it to terminal using adb and run a logcat to find the address of the update.zip
Click to expand...
Click to collapse
We don't need the location of the update file, we need all the extra network traffic that surrounds the OTA process.

Ah. My bad.

We need to know, exactly, how the update process works.
I'm currently working on downgrading 2.1. Will post back a tut if i get it working

Can't we create an AVD to run with a custom rom and use the Eris MR1 ROM to do it?

Scratch that. I don't think AVDs will get OTAs.

zifnab06 said:
Scratch that. I don't think AVDs will get OTAs.
Click to expand...
Click to collapse
Sadly I tried this a while ago when messing around with AVD Skins but wasn't able to figure it out. If anyone can figure it out please let me know how you do it! -_-"

zifnab06 said:
Scratch that. I don't think AVDs will get OTAs.
Click to expand...
Click to collapse
Wait can't you set it to wireless only mode and get the OTA through wireless? (Simulated by your network connection)

nindoja said:
This is a call to arms for anyone still running 1.5 on their eris. We (developers) need people to capture the update process using wireshark (or an equivalent). This is needed for a new root attempt, but sadly all of the devs have already updated to 2.1 so we can't do this.
...
Thanks a ton.
Click to expand...
Click to collapse
No need to go to all that trouble. I've already posted a link to the OTA update (1.16.605.1 -> 1.17.605.1) in this XDA thread a couple of days ago. Just copy n' paste into your browser's URL bar. I'll repeat it here for grins.
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
(You might get a browser security warning as that server uses the wrong (google.com) cert.)
Let me know if the above link no longer works - I suppose I could repeat the OTA thing - I am not on 2.1
The OTA process drops the downloaded zip file into /cache, and somehow during reboot, it's presence is detected. If it "only" needs to be dropped in there, or there are some other hooks that need to be present at the reboot, I am not sure. I say "only" because that implies that root privilege is needed to do that - or perhaps it is possible to use "fastboot update" after rebooting the phone with $ adb '(sync; reboot -n oem-78)' The OTA zip file is not signed the way the RUU "rom.zip" files are; it uses the same signing methods as app (.apk) files - the SDK "jarsigner" method.
You can unpack the zip file and look at what it does - there is a script at
META-INF/com/google/android/update-script
which controls the update... and there is a binary patch executable included in zip which is called upon to do file-by-file binary patching.
cheers
bftb0

Thanks for the info bftb0, but we aren't looking to snag the OTA file. We are actually trying to see what communication goes on between our phones and the verizon update servers.

FYI,
When you roll back to MR1, the phone seems to have already grabbed and downloaded the OTA update... in less time than it takes to hand-configure the phone. If you want to observe the OTA process via wireless, you need to prevent the phone from having Mobile network access, since that comes up by default after a FR or MRx rom burn.
Here's a long shot. Perform the MR1 rollback inside a cell dead zone, and conduct a MIM attack by setting up a server on the wireless net so the phone downloads a different OTA zip. You control DHCP for WiFi, so you also in principle control the DNS and routing the phone sees via WiFi. In principle, it's not possible because https should prevent Man-In-the-Middle... but if that (Google) server isn't correctly configured, maybe the phone is not really being too careful about certificate problems. (Either that or the Google server is tuning its' responses based on UA strings).
bftb0

bftb0 said:
No need to go to all that trouble. I've already posted a link to the OTA update (1.16.605.1 -> 1.17.605.1) in this XDA thread a couple of days ago. Just copy n' paste into your browser's URL bar. I'll repeat it here for grins.
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
(You might get a browser security warning as that server uses the wrong (google.com) cert.)
Let me know if the above link no longer works - I suppose I could repeat the OTA thing - I am not on 2.1
The OTA process drops the downloaded zip file into /cache, and somehow during reboot, it's presence is detected. If it "only" needs to be dropped in there, or there are some other hooks that need to be present at the reboot, I am not sure. I say "only" because that implies that root privilege is needed to do that - or perhaps it is possible to use "fastboot update" after rebooting the phone with $ adb '(sync; reboot -n oem-78)' The OTA zip file is not signed the way the RUU "rom.zip" files are; it uses the same signing methods as app (.apk) files - the SDK "jarsigner" method.
You can unpack the zip file and look at what it does - there is a script at
META-INF/com/google/android/update-script
which controls the update... and there is a binary patch executable included in zip which is called upon to do file-by-file binary patching.
cheers
bftb0
Click to expand...
Click to collapse
bftb06: could you please PM me? I am going to trade my phone this week if you understand what I am getting at.

nindoja said:
Thanks for the info bftb0, but we aren't looking to snag the OTA file. We are actually trying to see what communication goes on between our phones and the verizon update servers.
Click to expand...
Click to collapse
Sorry, my bad. I didn't read carefully enough.
I could probably attempt what you are asking for - I am quite familiar with wireshark (and even hardware sniffing of WiFi, so long as you have the right nic), but the fact that the phone seems to go and look for updates immediately after a FR or MRx update means that the "check for updates" thing may not do anything useful for you if there is already an update on the phone waiting to be installed by the time you start pressing menu buttons. (Thus the idea about "do MR1 in a cell dead zone")
Beyond that, there is a possibility that the update app does not do a wildcard host bind() when it sets up the socket when it inquires about updates with the Verizon servers - for instance, MMS service works exactly that way (it will only use the mobile network interface), and precisely so because of security considerations. Do you know whether or not any of the update conversation actually traverses WiFi if the mobile network is turned off?
bftb0

bftb0 said:
Do you know whether or not any of the update conversation actually traverses WiFi if the mobile network is turned off?
bftb0
Click to expand...
Click to collapse
You can force updates to occur over WiFi if the mobile network is turned off. Do you think this would work:
1. on 1.17 do a factory reset but do not activate the phone.
2. Initiate the downgrade process
2a. while downgrading, turn on packet capture
3. When the phone boots back up and wants you to call a number to activate, hang up
I think if you can skip the activation the phone will not have a mobile data connection, which would allow you to turn on wifi and initiate the update process.

Im still on 1.5 PM me and ill help if needed

Do you guys still need this?

[How To] Root

TGA_Gunnman created a one click root that new users will want to use, said thread is a sticky in Captivate Development. If you still want to use the old method (and install ADB) please use this one.
I followed my own guide! This works perfectly if you read everything and follow the instructions.
Also: once you are rooted, be EXTREMELY careful! Half of the new threads are people who have screwed up their phones by deleting this or corrupting that. Please, for the sanity of all of the devs and Android veterans, make backups and just be all around careful. Almost all problems that anyone has had are repareable AND PREVENTABLE with a little reading and care. Just to clarify, rooting does not automatically enable sideloading. Please follow http://forum.xda-developers.com/showthread.php?t=738376 to enable sideloading.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way. Your warranty is also void, but you could have figured that out for yourself.
Now that that's over with, lets get to the fun bit. If you are on Windows, you can follow this procedure, or for TGA_Gunnman's one click root program (only on Windows), you can go ahead and skip to the bottom.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/s...iver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. (If you are on a Mac, DO NOT USE SAFARI to download the file, it automatically unzips any zip file. Use Google Chrome or firefox instead.) Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) EDIT--There is an easier way to get to recovery, but do this step anyway. Turn the phone off, then hold power, volume up and volume down. If you still want the android SDK (which will be very useful throughout your rooted experiences) follow the old procedure:
This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
Click to expand...
Click to collapse
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43

Can we please have more detailed instructions? I don't understand the part where it says "type in the terminal"
I am very new to android as this will be my first Android phone.
Also, after rooting will we be able to install 3rd party applications? Or do we have to do anything else to bypass ATT's restrictions?

adb terminal is software you need to install on your PC , will probably need samsung drivers also , guide is indeed not noob friendly. This will help you get needed bits including ADB
Probably None of us have captivate , so writing a guide is a bit troublesome

Ditto, a guide to the adb terminal please! I will acquire this phone, this Sunday.

Actually, you'd have to install a custom ROM for that. MoDaCo should be coming out with them pretty soon, and so will XDA. It won't be too long. BTW, once you have ADB installed on your computer, you can sideload apps all you want. The command is
Code:
adb install /directory/of/app/on/computer

point me to some functioning samsung drivers and I can do this!

If you cant get it to work on windows, try a ubuntu live cd. All you need to do is go to ubuntu and burn a disc and reboot.

Are there no Windows 64 bit drivers?
Edit- I found some that work. I think. Haven't tried it (yet).
http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Edit 2- Just did the root. Seems to have worked (no errors) but how do I know if it did? How do I delete say, ATT Maps?

Thanks for this. I am new to smartphones and plan on purchasing the Samsung Galaxy-S, but don't want to mess it up. I am new to editing the OS of any smartphone, but I think if I have a tutorial I will be fine

For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)

NOSintake said:
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
Click to expand...
Click to collapse
if you are in the directory above yes. the ./ just saves you from writing out the full path
lets say adb is in "/home/user/Downloads/sdk/tools"
you could type out "/home/user/Downloads/sdk/tools/adb command" regardless of where your terminal window was focused
or if you were currently in the directory "/home/user/Downloads/sdk/tools"
you could use the shortcut "./adb command"

OP I'd change your post based on my experiences... Here's a little more detail and I've rearranged it (you need the drivers before running these commands, for example).
blackjackboy said:
Please let me know if this rooting method works as I have no Captivate to test on. I'm not taking any credit for any of these files, LeshaK made the original file to root the European Galaxy S, Justadude modified it for the T-Mobile Vibrant and chaoscentral edited the file for use on the Captivate.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way.
Now that that's over with, lets get to the fun bit.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
Thank you to LeshaK, Justadude, and chaoscentral. Once again, I didn't discover how to root, that credit goes to LeshaK, bringing it over to the USA was Justadude's doing, and chaoscentral edited the file for use on our Captivates.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Click to expand...
Click to collapse

Ubuntu 10.04 - adb
Any step by step instructions just to get adb running enough on 10.04 to root and side load software? I'm getting command not found when I try to run adb, even after downloading packages.

Hi,
Did this thread worked well to Root the Captivate or anyother suggested link? I'll appreciate any help.
Thanks

rerooting captivate
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!

Thanks for the answer & More Queston
cellgeek said:
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Click to expand...
Click to collapse
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again

Muhamadabdelaall said:
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Click to expand...
Click to collapse
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.

Thanks Drachen
Drachen said:
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Click to expand...
Click to collapse
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks

Muhamadabdelaall said:
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Click to expand...
Click to collapse
The ATT stuff doesn't actually run so they aren't a big deal at this point. I also don't see Amazon MP3 background stuff like some Android devices have, so... There's really not a huge case for rooting yet.
That said, when Custom ROMs for this come out I'll still be getting one.

For those of you having a hard time installing ADB Shell, try this video. It worked for me.
http://www.youtube.com/watch?v=YeWH6Bj1DYw&feature=related

Dummy's Guide to update your I9000 from the stock software to the Official Froyo

After successfully;
researching, upgrading to the official build of my choosing, getting it to work and typing this tutorial out (for those that like me weren't knowledged in this),
I stumbled across this thread. I thought I should also share it here aswell.
Here's a N00b's (Dummy's) Guide to how to update your device from the stock software to the Official Samsung Froyo ROM (software/operating system) OF YOUR CHOICE!!
Why do this?
You get Froyo. So you get the latest version of Android to support more Apps.
It comes with some UI-tweeks, JIT-compiler, and FLASH 10.1 PLAYER!!!
Also you get a newer (better) kernel on your phone with some of Samsung's fixes for the lag and for the GPS.
You can get features/Apps not available in your native rom build and/or remove the bloatware.
This method (not incl E) can also be used to install custom ROMs (I personally can't wait for the Official English MIUI ROM).
** Denotes steps which I skipped, or was unable/unwilling to follow, or didn't quite understand
Here's the comprehensive, step-by-step, easy-to-follow breakdown/walkthrough (Section E only works on Windows Computers):
A) Remove your microSD card (this will prevent some weid issues later on)
A2) Make sure you have Kies downloaded and installed on your computer
A3) Make sure you have an extractor installed (for Windows 7, winRAR is a great free solution)
B) We need to root your device, for this goto "One Click Root/Unroot" by TGA_Gunnman at http://forum.xda-developers.com/showthread.php?t=742403
B1) Download (2.5MB) the software (depending on your computer, mine is Win7 Home Premium 64-bit) into your computer not phone
B2) Make a folder somewhere in your computer labelled "OneClickRoot" (or anything) and drag the .rar file (the one you just downloaded) into it
B3) Extract the contents of the files by Right-Click then "Extract Here" (If you don't have this option install WinRAR)
B4) Set your phone to USB Debug mode (on your phone goto MENU > Settings > Applications > Developement > USB debugging = Checked) and then connect the phone to the computer via USB cable.
B5) Open the "Galaxy S I9000 One-Click Root" application. (This step didn't work for me, so I instead opened "rootme" batchfile which started the command prompt).
B6) Your phone will shut itself off, and then turn on in a "recovery mode". DO NOT REMOVE THE CABLE. Use the Volume Up and Volume Down buttons to get to "install from " and then hit the Home button.
B7) Now your device should be restarting again but this time it will actually go to your lockscreen.
B8) Now, you have ROOT, Congratulations.
B9) Not sure? We can test to see if you have root. Goto Market on your phone and download two Apps (Superuser and Titanium Backup, use the search to find them fast).
B10) Install both and launch Titanium Backup. As soon as you turn it on it will come up with a pop up and say something like "Your device is not rooted" or "Root is not accessible" ... if you didn't get Root.
B11) If you have root it will say something like "Titanium Backup needs to gain permission from Superuser" here click Apply. If you get to the App, well done you have indeed Rooted your phone
C) Now if you want to Backup your device before the update (recommended) you can follow steps C, otherwise skip straight to Step D.
C1) On Titanium Backup if a pop up notification comes with something like "Download an updated BusyBox" allow it to do so.
C2) Now first thing you will want to backup your Apps (all paid and free and the levels/hiscores) make sure you don't have any emulator ROMs on there (they consume too much space) and delete all those unwanted Apps
C3) On Titanium Backup, hit the Menu button > More > Create "update.zip" ...
C4) On this screen select "User application" and "TitaniumBackup-3.6.2.zip" and UN-TICK the "Sign the ZIP file (with ZipSigner)"
C5) Hit the Create "update.zip"... on the bottom and Please wait
C6) Once it finishes it, exit Titanium Backup, go back to settings and disable USB debugging (as posted on B4).
C7) Connect your phone to your computer (through Kies or PC link) and then browse your My Computer until you find Galaxy S I9000.
C8) Open that folder and then open phone. Find "TitaniumBackup-3.6.2.zip" and copy that to somewhere on your computer.
C9) Now that we have backed up your applications, lets backup your ROM.
C10) According to TGA_Gunnman you can use Clockwork MOD Recovery to do this, but this is for a different (Galaxy S) device ie "Samsung Vibrant"
**C11) Follow the steps on http://forum.xda-developers.com/showthread.php?t=734164 to do so, personally I skipped doing so out of fear of bricking the device (there may be subtle differences between the devices that can make your phone a paperweight/brick)
C12) Now if you did follow the Clockwork MOD, be sure to copy the "update.zip" file somewhere into your computer (better be safe than sorry)
D1) Now we need to apply the 3-Button-Combo Fix (this is the only reason for steps A-C because it is highly recommended to have this before flashing ANY rom)
D2) I recommend the Fix by RazvanG http://forum.xda-developers.com/showthread.php?t=821698 because it seems to be the *safest*
**D3) Firstly check if your device is compatible. I wasn't successful to dump my BML1 block, so I couldn't test if the block reads "[email protected]"
**D3) RazvanG has provided some instructions on this method see his post for more information http://forum.xda-developers.com/showthread.php?p=9595936#post9595936
D4) So I took a leap of faith and continued anyways with the risk of bricking my device. I have it on contract/plan so if it fails I would just return it and say Kies was updating and it failed
D5) I followed the steps on the thread but I'll reitterate it here for your convnieance
D6) Download both files (RAZ-FiX-SGS and adbRecovery) from the thread.
D7) Make a new folder (adbRecovery) on your computer and extract the adb .zip file into there
D8) Connect your phone to the computer and copy the RAZ-FiX-SGS.zip into your phone's memory
D9) Delete the old Update.zip file AND rename the RAZ-FiX-SGS.zip to Update.zip
D10) Again, turn on USB debugging (you know how) and open "Recovery" batch file from your computer
D11) This will initiate a command prompt (on Win7) and restart your phone
D12) Your phone will go into recovery mode (like we've seen before)
D13) You need to navigate (Volume buttons) to "apply sdcard; update.zip" and hit the Home button
D14) Your phone will turn off and restart and should get to your lockscreen
D15) So you're at the lockscreen? SUCCESS! (mine didn't brick *pheww*)
D16) Now let's test to see if the 3-Button-Fix worked
D17) *IMPORTANT* Firstly browse into your phone's internal memory and delete update.zip (the one we put there from RazvanG)
D18) Now that you have done so, you can safely just turn off the device
D19) Hold the Volume Down + Home button ... then hold the power button, as soon as the device begins to turn on release the power button (keep holding Volume Down + Home)
D20) If you get a Yellow triangle with the Android robot and "Do not turn off Target", well done, you have the 3BF so you have a means to ensure that you can always recover your phone if you do brick, well done!
D21) You can *safely* remove the battery and restart your phone ONLY if you don't have a Update.zip in the root of your phone
D22) If you don't want to take a leap of faith try this method (safest method but doesn't work for some people): http://forum.xda-developers.com/showthread.php?t=860773
E1) Now is the fun part (we've just past the difficult parts)
E2) You need to hunt down the version of (official Samsung)software you wish to install ... just go through member's reviews and recommendations
E3) You need to find the product code of that build, you can do this navigating through this thread http://forum.xda-developers.com/showthread.php?t=846913
OR by asking members (they can find out with http://forum.xda-developers.com/showthread.php?t=787163)
E4) For me this was the Virgin mobile Australia build (XSA - an unbadged, no-bloatware, unlocked Froyo build with a free copy of Navigon Navigation)
E5) Make sure you update your Kies to "ver 1.5.3.10103_102" (latest as of the time I'm writing)
E6) Go visit this thread http://forum.xda-developers.com/showthread.php?t=835628 for information (the software may have been upgraded)
E7) Download (300KBs) the Kies Registry patcher 1.6.0.0 (latest as of writing) <<This only works on Windows computers, sorry Mac'ners>>
E8) Launch the Kies Registry Patcher WHEN KIES IS OPENED
E9) Click on File > Backup (and save this somewhere in your computer - this is your original product code - better safe than sorry)
E10) Make Enable Spoof to True
E11) Now where it says "Spoof Product Code as" type in the product code of your desire (mine is XSA)
E12) Hit Write Registry and it should say "Registry pathed successfully"
E13) Connect your phone via USB cable to the computer
E14) On your phone select "Samsung Kies" when the pop up comes ... it should be at the "Connected" screen (DO NOT HIT HOME BUTTON)
E15) On Kies it should find your phone, and a pop up on the corner will say "There is a firmware update available for your phone" hit that pop up
E16) Now you will see another pop up and it's asking if you want to "Back up contacts before upgrading firmware" ... seems like a good idea, tick the box and hit Upgrade
E17) If the screen on the phone shuts (ie standby) don't be alerted. Hit the power button to wake it up. DO NOT HIT THE HOME BUTTON!
E18) Another pop up will come to name the contacts file - I just hit save so its the original filename in original (Samsung)folder
E19) Another Pop up will come to say "Save to PC completed" - hit OK, its just letting you know the contacts saved properly
E20) Now you get another Pop up to start the Firmware Upgrade - This is an important area, note down the: Model Name, Current Version and Latest Version (if something goes wrong this info maybe valuable for developers)
E21) Mine is (model)GT-I9000, (current)PDA:JG4 / Phone:JG3 / CSC:JG2 and (latest) PDA:JP5 / Phone:JP3 / CSC:JP4 ......... notice they are diffirent, this is what I was looking for
E22) Hit Upgrade! (Allow Kies to function when Windows 7 or Windows Vista prompts you)
E23) Tick the "All information has been verified" and Click Next
**E24) Let Samsung record your phone number in their database? I don't care (I'm on insurance/contract/plan) and I hit "Allow saving" ad Clicked Next
E25) Wait patiently, its downloading the rom from the server, DO NOT UNPLUG THE DEVICE
E26) A progress bar will appear, your USB will get disconnected, reconnected several times, the phone will be stuck on the yellow triangle screen - these are normal
E27) The progress bar will slowly be filled from grey to blue and a progress bar will appear on your phone - almost there!
E28) The progress bar on the computer will finish and the pop up will read "GT-I9000 Upgrade completed" - Click Close
E29) Your phone will restart and will enter "recovery mode" some yellow texts will appear and scroll forward
E30) The phone will reboot again and you will see the boot image with the Galaxy S logo
E31) The phone will be stuck on that logo for awhile - be patient
E32) The phone will now get to your lockscreen, unlock it
E33) You will have to go through your initial setup firstly its the Swype tutorial, then data settings, and finally the account settings emerges
E34) If the Kies connection screen comes up: hit the home button
E35) Now you should have come to your Homescreen go and test everything (all your passwords, all your bookmarks, all your contacts, all your images/music/videos and all your apps (except bloatware) should be there but the order of all the widgets/apps in TouchWizz will be reset to abc-order)
E36) Goto Settings > About Phone Does it say Android 2.2?
E37) Well done you have passed Android Hacking 101, you are officially smarter than 50% of iPhone and Blackberry users
E38) Donate me a beer, nah just kidding, enjoy everything for free but feel free to donate to the developers that help make this possible

this is a guide for I9000 international
I9000M owners please be advised that the I9000 might cause you to lose the 850 band, and might also trigger the internal SD problem

AllGamer said:
this is a guide for I9000 international
I9000M owners please be advized that the I9000 might cause you to lose the 850 band, and might also trigger the internal SD problem
Click to expand...
Click to collapse
You made it into a thread, thanks!
Hopefully this might help fellow xdanians

Aww Mate this is awesome, I have the same Carrier and I had OPTUS crap on my Phone from custom roms, Now I'm back to Stock Froyo!!!!
A great tool to Start from afresh.....
But
At Instruction E11 - Select your product code from the drop down Box and it will populate the next field for you.

Gonna put into my favorites

Wow.
I don't think anybody that don't now much would read that.
I know allot and i would never use it either.
You should stick a warning sign on this tread.
I did read about half of it and then i just stop and shake my head.
I hope this tread is a joke.....
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram

DamianGto said:
Wow.
I don't think anybody that don't now much would read that.
I know allot and i would never use it either.
You should stick a warning sign on this tread.
I did read about half of it and then i just stop and shake my head.
I hope this tread is a joke.....
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
Click to expand...
Click to collapse
Can you elaborate?
Joke? No it's no joke but I should disclose (as always) this is a tried-and-true way of getting you to update your software but in no way can I be held responsible for damages.
Things may vary slightly in between different phones which is why the links for each source/thread is up there.
I found myself knowing what to do, but always guessing how to do it.
This is a step-by-step process of how and what I did to upgrade my phone to any ROM I want.
If this was posted up before I attempted my upgrade, I would've been so happy that someone really simplified it for me

This is a noobs guide??!!! Simplified??!! I think that everyone will appreciate the time you have spent typing this up and trying to help, but I'm with DamianGto, dude this guide is scary and just explains how YOU got YOUR particular phone running froyo and lets face it, you certainly didn't go about it the easy way!
Once again I think the time you have spent and the willingness to help is admirable, but there are much simpler and noob friendly guides out there

nagrom78 said:
This is a noobs guide??!!! Simplified??!! I think that everyone will appreciate the time you have spent typing this up and trying to help, but I'm with DamianGto, dude this guide is scary and just explains how YOU got YOUR particular phone running froyo and lets face it, you certainly didn't go about it the easy way!
Once again I think the time you have spent and the willingness to help is admirable, but there are much simpler and noob friendly guides out there
Click to expand...
Click to collapse
Well you need root + busybox to get the 3 button fix.
If anything a n00b did, they can recover with 3 button trick otherwise they will have a brick.
This is why this guide is long, to ensure things are a-ok.
If you found a friendlier guide can you post the link, much apprecated ;D

How do I exit downloading mode if I forgot to erase update.zip ?

What is it ? Kies
A2) Make sure you have Kies downloaded and installed on your computer
Thanks

Well I think this is an excellent guide that has great potential!
However, a couple of crucial mistakes, which if fixed could help make the guides less confusing...
At beginning of (D) you talk about (A-C) being solely so you could fix your 3 button download (which I don't think is actually true!)
.... But, you should mention 3 button download at the very start of the guide anyway!!
Also, you should include a quick test at the very start to check for 3 button download, because mine is already fine, so a newbie might run all those extra steps when they already had working 3 button download anyway! (The more sections that can be skipped the better!). You can then steer people to the sections they uniquely will need.
However, titanium backup isn't needed for 3 button download fix, but is a wise step before running a rom update. And this works best with root anyway. Hence I don't think your opener for (D) is very accurate. You didn't just complete those steps JUST to get download mode. The backup was important anyway!
Do others think there should be a stage added for backing up contacts etc?
A stage for backing up efi?
Anything else wise that should be in here?

Rooting the SCH i400 - Step by Step Instructions for Newbies

I just managed to root my SCH i400 (first ever rooting of any Android device for me).
I am very surprised by how smoothly it went, despite reports & warnings everywhere about complications (like this one - which should be totally ignored if you're using SuperOneClick v2.1.1 or higher).
For the benefit of n00bs like me who may be confused by multiple sources, resources, versions and problem reports, I am posting a step by step procedure that is confirmed (by me, on Windows XP SP3) to be working smoothly, without a single hitch of complications:
Phone: Make sure setting > applications > unknown sources is checked.
Phone: Make sure phone is in debugging mode.
Phone: Make sure SD card is unmounted!
PC: Make sure Windows USB driver for this phone installed and works
PC: Make sure .NET 3.51 SP1 is installed.
PC: Unzip SuperOneClickv2.1.1-ShortFuse.zip ==> C:\Program Files\SuperOneClickv2.1.1-ShortFuse
PC: Double-click SuperOneClick.exe
PC (in SuperOneClick): Make sure you're on the Universal tab (the only other tab is Samsung Captivate, which isn't the i400).
PC (in SuperOneClick): Now click the root button and wait for the process to complete.
PC (in SuperOneClick): "BusyBox not found. Would you like to install it?" Yes!
PC (in SuperOneClick): "Root install has completed! Would you like to run a test?" Yes!
PC (in SuperOneClick): "Your device has been rooted! Would you like to donate now?"
Exit SuperOneClick, unplug phone from USB, power down phone, power on phone. -- this step might not be mandatory, I just did it to be on the safe side.
Enjoy!

Great job on this tut.
Sent from my SCH-I400 using xda premium

Nice...
I may have to sneak my wife away from her for a bit....
Sent from my DROID using XDA App

Froyo is so nice... Here's how...
Hey guys... new poster here.
Just got a (Gently used) Samsung Continuum for free from Verizon after the power button on my G Droid 1 broke.
Anyways, after rcving it and realizing that it would only support Android 2.1 - I was slightly upset.
My D1 was rooted and modded to the max many times over with just about every ROM you can get.
So after reading up about IMNUTS leaking the Froyo download for the Continuum, my hopes were raised.
It is now debinged, debloated, lightening quick and amazing!
There may not be ROMS out there yet - but I truly hope some of you geniuses decide to make a few.
Just wanted to say thanks and encourage you to do some research before rooting it.
Here's what worked for me.
Odin 1.3
Continuum PIT.pit file
froyo_modem.tar.md5
cwm_recovery_test4_adryn.tar
cyan Clockwork Mod Recovery (BLUE, not yellow) (update.zip file, which is placed on the root of your SD card - renamed to update.zip)
stock_deodexed_ec03.zip (ROM)
(Place all of these files on your Desktop for easy access)
How to do it...
1. Connect your phone to your computer and Mount it.
2. Place the cyan CWM Recovery zip file to your SD card. (rename it to update.zip & do not put it in any folders. Just drag the file to your SD card - whatever drive it is listed as. Mine is my Removeable F
3. Make a new folder on your SD card. Name it whatever you want. (Mine is named "Froyo") Place the stock_deodexed_ec03.zip file in the folder on your SD card.
4. Open Odin 1.3 on your PC.
5. While your phone is off... hold the down volume button and connect it to your computer via USB. The yellow triangle will appear and it will say "Downloading". (Some people say to take the battery out, but my Odin program would not recognize my phone without the battery. Whichever works for you is fine.)
6. In Odin - Click the PIT file button. Load the Continuum.Pit.pit file into the file field. (Just double click it once you find the file from your Desktop.)
7. In Odin - Click the PDA button. Load the froyo_modem.tar.md5 file into the file field. (same as #6. Just double click it once you find the file from your Desktop.)
8. Click Start in Odin.
It should think for a minute, then say resetting, then say PASS
Then your phone will probably turn back on - turn it off again and reconnect it to your PC in download mode as stated in #5 above.
9. In Odin - Click the PDA button again. Load the cwm_recovery_test4_adryn.tar file as you did in #'s 6 and 7 above.
10. Click Start again in Odin... same as before. (thinking, resetting and PASS)
Your phone will turn on again.
11. Disconnect your phone from the computer & turn it off.
12. Hold both Volume buttons and turn it on. It will boot into the Samsung Recovery mode.
13. Use your Volume buttons to go down to highlight "apply update.zip" Then find the place where your normal Menu softkey would be and push it. The phone should then reboot into Clockwork Mod Recovery. It will be orangish.
14. In CWM, use the Volume buttons to highlight Backup/ Restore. Use the Power Button to choose it. Then at the next field, highlight Backup and make a backup.
15. After is makes the backup, press where the softkey Back button should be to go back to the original screen. From there, do a Wipe Data/ Factory reset. Do not forget to do this part.
16. Once it does the Data Wipe - go back to the main menu and and highlight & select the "zip from SD card" choice. Find your "Froyo" folder (of whatever you named it) and apply the stock_deodexed_ec03.zip file.
17. After that, go back to the main menu again and reboot your phone.
It may take a while, but your phone should restart in Froyo.
Of course, you have to re-sign in to your Google network...
Thanks so much guys for all the posts. Without them, is nowhere near as cool.

Hanging at Step #5, Now what?
Thank you for sharing. Wish I could say it went as smoothly for me with my SCH-I400 Continuum... I'm still working on it! I followed recommendations of several different developers/rooters. I've installed .Net Framework 4.0 and the SDK developers kit (who knows, maybe I'll start a new hobby...), and now when I run Superoneclick it hangs at step #5 with this message:
link_image[1728]: 3252 could not load needed library 'libdiskconfig.so' for './zergRush' (load_library[1058]: Library 'libdiskconfig.so' not found)CANNOT LINK EXECUTABLE
I have rebooted the computer and the phone, unmounted the SD card, settings to allow unknown sources, and turned on USB debugging. I'm not sure why the config file can't be found, and I don't know where to get it...
Do I need to reinstall the SDK? Or install the additional Java developers software? Or am I over-complicating this whole thing?
Any ideas will be greatly appreciated...
-James

Perhaps the easiest way is to flash a rooted ROM through Odin (or Heimdall)... Especially if you don't use Windows. This is how I did it:
http://forum.xda-developers.com/showthread.php?t=1203597

Two topics in one thread?
Hmmm... seems we have 2 things happening hear. 1: Rooting a Samsung Continuum, and 2: Flashing a ROM...
My concern is the "hang" at step five for Rooting my Continuum SCH-I400... Cant use a ROM until the dang thing is rooted, and can't seem to figure out the hang.
Tried Z4 root from the phone rather than through the PC and it hung indefinitely... Maybe there's a related issue, and I don't care if it's Superoneclick or Z4 that gets the job done.
Has anyone gotten past the same issue?
-James

bighigmt said:
Hmmm... seems we have 2 things happening hear. 1: Rooting a Samsung Continuum, and 2: Flashing a ROM...
My concern is the "hang" at step five for Rooting my Continuum SCH-I400... Cant use a ROM until the dang thing is rooted, and can't seem to figure out the hang.
Tried Z4 root from the phone rather than through the PC and it hung indefinitely... Maybe there's a related issue, and I don't care if it's Superoneclick or Z4 that gets the job done.
Has anyone gotten past the same issue?
-James
Click to expand...
Click to collapse
That's where you are over complicating. You don't actually have to root BEFORE you flash a new rom, if the rom is 'prerooted'. I've never rooted this thing via s1c or z4. I simply flashed the kernels via odin and flashed the rom in cwm.
Either let me fly or give me death. Let my soul rest, or take my breath. - DMX

Txwolf1980 said:
That's where you are over complicating. You don't actually have to root BEFORE you flash a new rom, if the rom is 'prerooted'. I've never rooted this thing via s1c or z4. I simply flashed the kernels via odin and flashed the rom in cwm.
Either let me fly or give me death. Let my soul rest, or take my breath. - DMX
Click to expand...
Click to collapse
That's fine Txwolf, but still doesn't address the issue... Or the original reason for this thread - Rooting - which is is essential for the programs I am going to run, and that is what I have been asking about...

bighigmt said:
That's fine Txwolf, but still doesn't address the issue... Or the original reason for this thread - Rooting - which is is essential for the programs I am going to run, and that is what I have been asking about...
Click to expand...
Click to collapse
The issue seems to be that you just have to use that little search box a little better via xda or your web browser and find more information the root program your trying to use.
When you give up on that you can take txwolf1980 's advice
PS hang on step 5 in OP? Or in 3rd post? That would be getting into dl mode lol
Sent from my SCH-I400 using xda premium

Come on now...
ciscogee said:
The issue seems to be that you just have to use that little search box a little better via xda or your web browser and find more information the root program your trying to use.
When you give up on that you can take txwolf1980 's advice
PS hang on step 5 in OP? Or in 3rd post? That would be getting into dl mode lol
Sent from my SCH-I400 using xda premium
Click to expand...
Click to collapse
I spent 6 hours last night troubleshooting, researching, digging deep, and "using that little search box." Seems to me You guys need to "just read the thread." It's about rooting your phone, period. If a forum is out there, I've probably read it. I'm using superoneclick to do it. SDK is installed. Net framework is installed. My error message frome SOC is above. When I am finally rooted, THEN I will install several programs - starting with a wifi tether.
I see you have the same phone as I do. Is it rooted with a one-click method? I also tried Z4root and didn't like it.

bighigmt said:
...Seems to me You guys need to "just read the thread."...
I see you have the same phone as I do. Is it rooted with a one-click method? I also tried Z4root and didn't like it.
Click to expand...
Click to collapse
well i did read the thread...
ive been out of town for a week and finally back on my pc... i would love to help you yet more info is needed.
you are running dl17 stock 2.1 correct?
what OS is your pc running?
and yes i have same phone as you. i have used superone click on ec03 build once.
just for root. but then flashed a deodexed rom to use custom mods and apps.
and since have been flashing rooted kernels, imnuts and adrynalynne have released most all of them.
there are a few ways to root the device, best bet is, as always is go to IRC.
clarity and patience are key, we all got to practice both

I rooted EC09 with soc no problem. If I send someone the EC09 could they extract the apks and send them to me? I deleted some sys apps for the ticker and rss feeds and need them back now to use it.
Sent from my SCH-I400 using xda premium

Unzip factory.rfs of ec09 to grab missing apks and put them on sdcard and install from there.
Sent from my SPH-M580BST using Tapatalk 2

verizonless said:
[*]PC (in SuperOneClick): Make sure you're on the Universal tab (the only other tab is Samsung Captivate, which isn't the i400).
Click to expand...
Click to collapse
FYI, my Windows Defender threat scanner just reported this SuperOneClickv2.1.1-ShortFuse.zip file as Exploit:AndroidOS/CVE-2011-1823, more specifically pointing at a file named Exploits/GingerBreak in that ZIP file.
I am going to delete this ZIP file as I no longer need it, but I got curious: Any idea what this means?

verizonless said:
FYI, my Windows Defender threat scanner just reported this SuperOneClickv2.1.1-ShortFuse.zip file as Exploit:AndroidOS/CVE-2011-1823, more specifically pointing at a file named Exploits/GingerBreak in that ZIP file.
I am going to delete this ZIP file as I no longer need it, but I got curious: Any idea what this means?
Click to expand...
Click to collapse
It means it'll root your phone. Some applications could try to do this without permission and do shady things with your phone. Nothing to worry about if your doing it on purpose.

trailblazer101 said:
It means it'll root your phone. Some applications could try to do this without permission and do shady things with your phone. Nothing to worry about if your doing it on purpose.
Click to expand...
Click to collapse
Im assuming by now everyone is on EG04 Gingerbread?

[HOW TO] Fix the "Low on space" problem (in plain English)

The Problem
The HTC Droid Incredible shows a "Low on space: Phone storage space is getting low" warning despite having gobs of space free because the "Application data storage" folder (also known as /data/data) that is shared by all apps on the phone is only 150mb in size. As soon as only 10% of this folder is available, the warning appears. If it gets too much lower, apps stop responding and the phone crashes.
The Story
After many months of clearing app data, uninstalling apps, resetting my phone, and generally walking on eggshells trying to keep my data storage under the limit, I was getting ready to upgrade my device. I would search every few weeks to see if anyone had solved the problem, but all I found were more people stuck in my boat, and I was ready to give up. But then I stumbled across a series of threads on xda-developers.com that gave me new hope. In the course of one night, I learned from scratch how to root my phone, and I applied a fix that increased the "Application data storage" folder to a whopping 750mb. I am now able to download as many apps as I'd like and not have to worry about clearing out app data ever again.
However, it took a bit of scouring the forums and reading various guides to figure out how to do all this. Some of the items are quite technical in nature, and some of the guides skip steps that more experienced users would know how to do already. So I joined the forum to write this guide for the "regular" users out there like myself. My goal is to explain in plain English how to fix this nagging issue once and for all and to consolidate all the relevant info and files into one place. If you find this useful, please share this with others so we can all fully enjoy our phones!
The Credits
I did not invent any of the steps, tools, or methods I am about to describe. Hats off to the following people for supplying all the info and files I needed to fix the problem and write this how-to thread. Please let me know if I've missed anyone that should be mentioned and I will add them.
vbhines for the "New to Modding/Rooting" guide
The unrevoked team for their excellent one-click rooting software and drivers
dreamersipaq for the guide to rooting an Incredible
scotty1223 for the guide to rooting a 2.3.4 Incredible
jermaine151 for the "no data limit" mod that actually fixes the problem
cmlusco and tiny4579 for all their help answering questions and troubleshooting in this thread
The Ingredients
Here's what you'll need to perform this fix:
An HTC Incredible (obviously) with an SD card
A micro USB cable (you can use the one you charge your phone with)
A computer with a USB port and internet access (PC, Mac, or Linux)
An hour of free time
The Fix
Step 1: Read the "New to Modding/Rooting" guide so you know what you're getting into and can understand the terminology: http://forum.xda-developers.com/showthread.php?t=744807
Step 2: Back up your contacts, pictures, etc. This guide is safe for your phone and will not erase any of your data if you follow it correctly, but it never hurts to back things up just in case.
Step 3a: Make sure your phone is decently charged. (at least 50%)
Step 3b: Make sure your phone isn't currently showing the "low on space" error. Delete some apps or data until the error goes away. You don't want to go through all this effort only to have your phone crash halfway through!
Step 4: Uninstall HTC sync software from your computer. Also make sure you are not running any software that communicates to your phone using USB, such as PDANet or DoubleTwist. If you haven't had to plug your phone into your computer to do anything prior to now, you're probably OK.
Step 5: On your phone, go to Menu -> Settings -> Applications -> Development and put a check in the "USB debugging" box.
Step 6: Plug your phone into your computer, select "Charge Only", select "remember my selection", click "Done", and then unplug your phone.
Step 7: If you are on a Windows PC, follow this user-friendly guide to install the USB drivers you'll need: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
When I did this step, I actually found my Android entry from the first screenshot in the guide under "Android Phone" and it did not say "Android 1.0". Don't worry, you can still use this entry to continue with the next step in the guide to "Update Driver Software".
Mac and Linux users can skip this step.
Step 8: Root your phone. This step is a bit more involved, so be sure to read the directions carefully. On your phone, go to Menu -> Settings -> About phone -> Software information and look at what it says under "Android version" at the top.
If it says 2.3.4, do this:
Download Clockwork 5.0.2.0: http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip (link updated 6/22/12)
Extract the recovery-clockwork-5.0.2.0-inc.img from the zip file and put it somewhere you'll remember.
Download Unrevoked 3.22 (this is intentionally NOT the latest version): http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe (link updated 6/22/12)
Run Unrevoked_3.22.exe
Inside the program, go to File -> Custom Recovery and select the .img file from above. At the bottom of the program window, it should now say "Recovery: Custom" and "Waiting for device"
Plug in your phone and wait while Unrevoked runs automatically. It will reboot your phone several times and will take some time, so be patient!
Once it's done, unplug your phone and ensure that a "Superuser Permissions" application is inside your app drawer. Don't run it. Instead, go to Menu -> Settings -> Applications -> Manage applications -> All, scroll down to "Superuser Permissions", click it, then click "Clear data". Return back Home.
If it says anything other than 2.3.4, do this:
Download Unrevoked 3.32: http://www.unrevoked.com/recovery/
Run reflash_package.exe. It may start up right away, or it may ask you to extract the files. Put them somewhere you can find, and once the extraction is done, find and run reflash.exe.
Plug in your phone and wait while Unrevoked runs automatically. It will reboot your phone several times and will take some time, so be patient!
After the above steps, everyone should do this:
Launch the Android Market and search for "ROM Manager". The first result should be "ROM Manager" by ClockworkMod and it should have a picture of a top hat above a gear as its icon. Click it, then click "Download", then "Accept & download". If it is already installed, you can just return Home.
Once ROM Manager has finished installing, launch it and select "Flash ClockworkMod Recovery" (the first option). Confirm your phone model (HTC Incredible). A window will pop up asking for root permissions - click to allow it.
Optional: After the download completes, scroll down and click "Backup Current ROM". You may need a lot of space free on your SD card to perform this backup depending on what you have on your phone. Once you create this backup, you can use ROM Manager to fully restore your phone (including all apps, data, and settings) in case anything goes wrong. This can take a significant amount of time, so again, be patient!
If all went well, your phone should be exactly the same as it was before, except you now have a couple new apps, and more importantly, root access!
Step 9: On your phone, go to Menu -> Settings -> Applications -> Development and uncheck the "USB debugging" box.
Step 10: Apply the Fix. This is the step you've been waiting for!
Go to this thread: http://forum.xda-developers.com/showthread.php?t=1623038, click the link for the EXT4All files in the first post, download "Convert2Ext4_no_data_limit_normal_dalvik.zip", and put it somewhere you'll remember. You can also go directly to this URL to download the file: http://dinc.does-it.net/EXT4_Mods/ (links updated 6/22/12)
Plug your phone into your computer, bring down the notification bar, select the "USB connection type" item, select "Disk drive", and click Done.
On your computer, find your phone's SD card. If you're unsure which drive is your SD card, look at how big each drive is. The drive that has a size of 6.59GB is the phone's internal memory, so the other drive is the SD card. The SD card that comes with the Incredible is 1.83GB in size, but yours may be different if you bought your own SD card.
Move "Convert2Ext4_no_data_limit_normal_dalvik.zip" from your computer to the SD card. Do not put it inside any folders.
After the file has finished moving, bring down the notifications bar, select the "USB connection type" item, select "Charge only", then click done.
Unplug your phone from your computer.
Launch ROM Manager from your app drawer and click "Reboot into Recovery" (the second option). Click "OK" to proceed.
After the phone reboots, you will now see a black screen with some blue options on it. Use the volume buttons on the left to scroll down to "install zip from sdcard" and click the optical trackpad button at the bottom of the phone to select it.
Click "choose zip from sdcard" (the first option)
Scroll down to the very bottom and select "Convert2Ext4_no_data_limit_normal_dalvik.zip"
Scroll down to "Yes - Install Convert2Ext4_no_data_limit_normal_dalvik.zip" and click it. This step will take some time to complete, and the progress bar may not move at all. Be patient!
Once it is done, click the power button at the top of your phone until you're back at the main menu, then select "Reboot system" (the first option). If you hit power too many times and end up with a blank screen, just hit power one more time and you'll see the menu.
When the phone is done rebooting after this last step, verify that the fix worked by going to Menu -> Settings -> SD & phone storage and look at the "Application data storage" section. It should now say that the "Total space" is 748mb!
At this point you can run happily through an open field, shout from the highest mountaintop, or just shed a tear of joy, because you can now install tons of apps and let them accumulate all the data they want. Enjoy!
P.S. Please let me know if any of these steps are incorrect or unclear so I can fix them. Thanks!
Troubleshooting
Here are a couple of issues people have come across while doing the steps in this guide, along with the solutions. Thanks to cmlusco for these helpful answers!
The guide says my phone should have rebooted back to the main screen, but I'm on a black screen with a bunch of blue options!
If you're on this step and the guide doesn't say you need to be here yet, just use the volume buttons to scroll to the "Reboot System Now" option and click the optical trackpad. Then you can continue on with the guide!
I'm stuck on a black screen with white bars on the side!
If your phone is "s-off", reflash the recovery-clockwork-5.0.2.0-inc.img file from Step #8 using hboot. To get to hboot, turn your phone off, hold the "volume down" button, and turn it back on. Keep holding the "volume down" button until you get to the menu where you can flash the .img file.
If your phone is not "s-off" or you have no idea what "s-off" means, run Unrevoked again with the same .img file from Step #8.
In either case, you should be able to continue using the guide from where you left off!
My phone keeps rebooting over and over and I can't do anything!
Pull out the battery, wait for 15 seconds, and put it back in and turn the phone back on. If it still keeps rebooting, pull out/re-insert the battery again, go into hboot (see above answer) and try the following steps. You can stop as soon as one of them works!
1. Restore a backup that you made in a previous step (if you have one).
2. Reflash the .img file from Step #8.
3. Flash the .img file here: http://dinc.does-it.net/wildstang83_inc_4.08.605.2_11232011.zip (note: this one will take you back to stock, so you'll have to start the guide over).
I'm still stuck!
If all else fails, please post your issue in this thread so someone can help you out. You can also try restoring your backup (you made a backup, right??) and starting over from the top. Good luck!

Potential Alternate Solution
Soniclude that was a great very detailed write up. Here is another option that I found that seems to also solve the dreaded low disk space...
Since you clearly outlined the steps for rooting your device, I wont go into that. But, why stop at fixing one of the most annoying stock problems. Rooting is half the battle to flashing a new rom - which is precisely what I did to stop the LDS issue.
I used to use CM7 and then flashed over to MIUI but recently I flashed the best rom I have used to date - ICS-Dinc AOKP (]http://forum.xda-developers.com/showthread.php?t=1475936) which is a full fledged ICS port for your OG Dinc.
Since then I have not received any LDS errors (although I have not been using this ROM that long) but I would assume that it would be similar to my lengthy experience with CM7, in which I never got the LDS warning.
Here is what my device displays as available space for applications
View attachment 895332
As you can see I have used 144MB with 604MB free for a total of 748MB, identified as internal storage.
Also, just so you can see that this ROM is not an ICS overlay and is truly a port, here is the device info
View attachment 895331
72ls1's (the dev for ICS-Dinc AOKP) has some really good directions and make the process very easy.
For those that are interested and need a few more additional details, here are a few things that helped me:
1. Make sure you have backup your device data, this includes your apps, contacts (you should be just setting all contacts to sync with your gmail account to begin with), messages and email settings. Use an app like Titanium Backup for apps; Backup and Restore app for messages; Call Log Restore for calling
2. Download the zip files outline in the ROM posting of your chocie to your sdcard; They should be placed at the top level of your sdcard, meaning not in another folder. The zip files for ICS-Dinc AOK include the ICS-Dinc zip, Gapps (use this one gapps-ics-20120207-signed.zip - http://goo-inside.me/gapps/gapps-ics-20120207-signed.zip), and Tiamat Kernel
3. In Recovery make a backup of your device (in case you need to flash back due to an error)
4. Within Recovery prior to flashing the rom make sure to unmount data, sdcard and cache
5. Then clear cache and dalivik-cache (this one is under the advanced options)
6. Do a factory reset
7. Install from zip in the following order: ICS-Dinc AOK V.02, Gapps, Tiamat
8. Reset your device
Now go enjoy the goodness of a fresh ice cream sandwich!
Hope this helps anyone else out there in either the low disk space issue or that is having questions about flashing a rom.

Where is Unrevoked 3.22?
I'm going to use the downgrade-and-reflash method to root my 2.3.4 Incredible and after reading the forums have spent the supper hour looking around for Unrevoked 3.22. There was a megaupload site that always says bandwidth is exceeded, and one more that I found where everything is in a language I can't decipher.
Does anybody have a working link to 3.22? All I want is to turn on my stupid wireless hotspot so my wife can use her Ipad in teh car without having to pay Verizon another $30 a month for access to data I already have. Argh!
Thanks,
Ryan

Captainjerky said:
I'm going to use the downgrade-and-reflash method to root my 2.3.4 Incredible and after reading the forums have spent the supper hour looking around for Unrevoked 3.22. There was a megaupload site that always says bandwidth is exceeded, and one more that I found where everything is in a language I can't decipher.
Does anybody have a working link to 3.22? All I want is to turn on my stupid wireless hotspot so my wife can use her Ipad in teh car without having to pay Verizon another $30 a month for access to data I already have. Argh!
Thanks,
Ryan
Click to expand...
Click to collapse
You can actually acomplish that without rooting.
Open dial pad and type ##778# and hit call.
Select edit mode and enter six zeros (000000) as the password.
Select security and look for S.IP DUN username, it should look something like this [email protected]. Change it to be [email protected], just remove the "dun.".
Back out to the main menu and select M.IP Default Profile. Look for DUN NAI and change it to be [email protected], remove the "dun."
Hit the menu button and select commit modifications. Your phone will reboot.
Now just use the stock 3g mobile hotspot app. When you first open it it will say you have to have a subscription and pay, just procede you will not be charged, and verizion is none the wiser. I have been doing this my self for over a year now.

Compass sensor broken
Somebody has the same issue? after flashing the zip i cannot use correctly the compass sensor, for example in SkyMaps app.

This is by far the best tutorial out there to gain root and achieve s-OFF I've come across. Thank you SIR for your time and tutorial. Just EXCELLENT!!

for me the issue was my data/data folder (hint dont sync 1500 facebook friends and never do it with high res pics and with two differant apps haha) =] jsut removed all the contacts i didnt need and turned off the sync from normal facebook app and working perfect now

stuck in loop
I followed the instructions for the 2.3.4 and after I applied the Convert2Ext4_no_data_limit_normal_dalvik fix I got stuck in a loop with at the HTC Incredible boot screen, not sure what to do now.. can only get back to the recovery mode. Not sure what to do from here

scals37 said:
I followed the instructions for the 2.3.4 and after I applied the Convert2Ext4_no_data_limit_normal_dalvik fix I got stuck in a loop with at the HTC Incredible boot screen, not sure what to do now.. can only get back to the recovery mode. Not sure what to do from here
Click to expand...
Click to collapse
If you made or have a previous roms backup. Just wipe everything in mounts and storage menu except sdcard and emmc, then restore your backup. If you dont have a backup flash a fresh rom.

You kind sir are a gentleman and a scholar. That "low space" bug has been annoying me since July 2009. I greatly appreciate you breaking down the l337 sp33k to plain English.
THANK YOU THANK YOU THANK YOU THANK YOU

Captainjerky said:
Does anybody have a working link to 3.22?
Click to expand...
Click to collapse
downloads.unrevoked.com/recovery/3.22/reflash_package.exe
---------- Post added at 01:19 PM ---------- Previous post was at 01:11 PM ----------
Thank you for the spectacular write-up, soniclude!!!
Is there a particular reason that you did not suggest using the no_data_limit_dalvik_moved mod?
Does it not work?

[/COLOR]Thank you for the spectacular write-up, soniclude!!!
Is there a particular reason that you did not suggest using the no_data_limit_dalvik_moved mod?
Does it not work?[/QUOTE]
I agree that this was an excellent how to. Thanks for the effort.
I used the no_data_limit_dalvik_moved mod and for some reason, my phone became really laggy. I'm on Pons CM7. 2. Now I'm a little hesitant to use any of the ext4 mods b/c I don't understand them too well. I'm not clear on why there is a partition in the first place. Why htc devs made it so small... Homework to do.
Sent from my ADR6300 using Tapatalk

Thanks cmlusco I used your method to unlock the 3G Hotspot on my phone and it worked like a charm.

Issue in Step 10
Thank you very much for the easy to follow directions soniclude. I went through all the steps and when I got to step 10, I ran into an issue. After clicking on "Reboot into Recovery" the phone restarts and goes to the white htc screen. After that the screen just goes black with thin white lines down the sides and stays like that. So I never see the blue options. Has anyone come across this? If so, what do I do from there?

I get the message: failed to root. is your firmware too new? What now?
Is there anything I can do now to revert my firmware so I can gain root.

joeyz400 said:
I get the message: failed to root. is your firmware too new? What now?
Is there anything I can do now to revert my firmware so I can gain root.
Click to expand...
Click to collapse
If your on 2.3.4 you need to follow this guide http://forum.xda-developers.com/showthread.php?t=1306400 to root and get s-off.

I understand I could downgrade to 2.2 to get s off but only after I gain root. It seems I can't get rooted because I am running 2.3?
---------- Post added at 06:58 PM ---------- Previous post was at 06:53 PM ----------
It looks like the only step diffrent from the link you posted and this one is to run unrevoked as admin

I think I know what is wrong. The link to Unrevoked 3.22 is not working so I googled it and 3.22 came up but it was actually 3.32 that was downloaded and I can't find 3.22 anywhere. Does anyone have a copy of 3.22?

I found the correct 3.22 and now my Incredible is Incredible!!!! Rooted and it feels so good
Thanks for such a great thread!!!!

SWEEEEEET This worked awesome.