Samsung Intercept
Find Your Forum
  
Welcome, Guest. Please login or register.
Did you miss your activation email?

News: Do you like Samsung Intercept?
Advanced search
Scratch-Proof your Samsung Intercept              Best Screen Protector for Samsung Intercept Latest Ringtone for your mobile
Pages: [1]
Print
Topic: Guide to root, custom ROM and recovery, wifi tether for Virgin Mobile Intercept  (Read 19690 times)
Scrotius
Newbie
*

Cookies: 0
Posts: 4


View Profile Email
« on: April 02, 2011, 12:19:37 am »

Guide to rooting, installing a custom ROM and recovery to virgin mobile intercept 2.1 on windows 7 and getting wifi tether to work.

First, make sure your computer can connect to the phone via USB.
To do so, follow this guide: http://www.youtube.com/watch?v=CS6Hkdow2Hk#

If this goes down for some reason, basically you:
Enable USB debugging, connect the phone, go to device manager, install driver from disk by browsing to ssadadb2.inf and using that on "other devices , SAMSUNG_Android" then the same for "Other devices, S3C6410 Android ADB", then the same for "USB controllers, SAMSUNG Android Composite USB Device" then the same for "Other devices, CDC Abstract Control Model". Now go to see if it worked, go to notifications USB connected, mount. If it mounts, it worked.
If you can mount it via USB, it is working. If for some reason it stopped working and you see "unknown device" in device manager, restart your phone into recovery mode (power, call, volume down). The phone should then show up on device manager, so that you can then use the above method to get the USB working.
http://dl.dropbox.com/u/12095484/Samsung.Moment.USB.Drivers.Windows.zip
(http://randomtechinfo.com/Moment/Samsung.Moment.USB.Drivers.Windows.zip)


Next, temp root your phone. (Rooting is effectively removing the restrictions placed on what you can do in your phone's operating system. An unrooted phone has the user basically logged in to a non administrator account- such an account is unable to take all actions which are possible within the OS, which an administrator account could. This is not to be confused with "unlocking" which typically means to provide a code to the networking chip on your phone that will allow it to be used with other service providers. This is easy to do with GSM phones, it typically involves spending 10$ on a website who will give you a code to enter to unlock your phone. It is harder to do on CDMA phones, such as Virgin Mobile ones, and is known as flashing the phone.)
To do so, use this, "SuperOneClick":
http://dl.dropbox.com/u/12095484/SuperOneClickv1.7-ShortFuse.zip
(http://forum.xda-developers.com/showthread.php?t=803682)
Choose option 2, rageinthecage, and click root. Click through the process and see if it is successfully rooted.

Now download flash_image , which is a program used to flash kernel images and recovery images to the boot and recovery partitions on your phones internal memory, respectively (this is the flash image from samsung moment, which works for intercept):
http://dl.dropbox.com/u/12095484/flash_image
(http://samsungmoment.googlecode.com/files/eclair_moment.zip)

Now download inxanes custom recovery. This will let you install the rom automatically from a zip file stored on your SDCard, in addition to making backups and doing other miscellaneous tasks.
http://dl.dropbox.com/u/12095484/recovery.rfs
(http://forum.sdx-developers.com/intercept-development/intercept-recovery-(important-features-working!)-(updated-11311)/msg91881/#msg91881)

Now download a kernel. (A kernel is the fundemental core software of operating systems which effects everything that a device is inherently capable of doing with hardware and software. Operating systems are built up around the kernel with higher level software and a user interface. A ROM, which is an operating system, is an example of this. ROM stands for read only memory, which is a loose term as applied to OS's for phones, because it is loaded into the Read Only Memory of such phones. Regular Android is of the same basic nature as any ROM you will find in the forums. ROMs from the forums, and from certain phone makers are simply modded versions of Android.)
Here is the kernel I used, vampirefo's kernel:
http://dl.dropbox.com/u/12095484/zImage.img
(http://forum.sdx-developers.com/intercept-development/vampirefo-kernel/)

Now download a custom ROM. I used CuteROM. It will be applied to your phone from the custom recovery. With regular recovery you cannot apply a custom ROM to your phone.
http://dl.dropbox.com/u/12095484/CuteRomX.zip
(http://forum.sdx-developers.com/intercept-development/(virgin-mobile)-cute-rom/)

Now mount your phone via usb and make a folder called sdx if it is not already there. Put CuteRomX.zip inside of this folder.

Now in the folder which contains SuperOneClick, there is a program called ADB. You will use this to log in to your phone from the computer and issue commands as root.
If your phone is mounted unmount it. In your phone, go to settings, applications, development and check enable USB debugging.
Open up command prompt on your PC, (run, cmd) cd to the SuperOneClick folder, and type adb devices. If you see one line of numbers, then adb successfully recognized your phone.
Now what you are going to do is transfer the files that you downloaded to your PC to your phone's internal memory.
To do this, do the following (if you have issues, try the files with and without the .extensions):

Code:
adb push C:\your\path\flash_image /data/local/tmp/
 adb push C:\your\path\zImage.img /data/local/tmp/
 adb push C:\your\path\recovery.rfs /data/local/tmp/

We need to give more universal permission to use the program flash_image (permissions is a big thing in linux, which is what android is based on).
We are going to log in to your phone's command line, or shell, to do this:

Code:
adb shell

You should see a #. (If you see a $ your phone isn't rooted.)
Now type:

Code:
chmod 755 /data/local/tmp/flash_image
 
Now we are going to overwrite the kernel in the boot partition of your phone with the one we downloaded, using flash_image, then we are going to do the same with the recovery file we downloaded and the recovery partition. Input these commands from within the shell (# prompt):

Code:

/data/local/tmp/flash_image boot /data/local/tmp/zImage.img
/data/local/tmp/flash_image recovery /data/local/tmp/recovery.rfs

You'll see a bunch of text and a block of numbers, if it says something to the effect of write and there are no egregious errors (even if there are it will probably work), you can assume it worked. You will probably not notice a difference with the new kernel other than perhaps speeds or compatibility. The recovery however, will look different.

Type exit exit to get out of the shell. Turn off your phone, boot into recovery. (hold power, phone, volumedown) (http://forum.sdx-developers.com/intercept-development/(virgin-mobile)-cute-rom/)
Scroll to Wipe and wipe data/cache.
Press the return arrow and go to Advanced.
Select Filesystem Conversion.  Apply the following settings:

Code:
CACHE: (ext4)
DATA: (ext4)
SYSTEM: (ext2)

Return to main menu.
Select Install zip from sd card.
Select Choose zip from sd card. Select SDX.  Select roms.  Select CuteRomX.zip.  Press Home.  Cute Rom X will install at this time.
Return to main menu and select Leave Recovery.  Select Reboot to system.
Cute Rom X will boot up for the first time, this process can take a while.
Go to the app list and select Superuser.  If it does not ask, to up go to Settings and select "Su binary v original" and allow it to update.

You now have a rooted Virgin Mobile Intercept based on Android 2.1, a custom recovery, custom OS, custom kernel.

Now we are going to get wifi tethering to work.

Download and install http://code.google.com/p/android-wifi-tether/downloads/detail?name=wifi_tether_v3_0-pre12.apk&can=2&q= onto your phone. (The regular market app probably won't work.)
Now download the latest wifi drivers for your computer.
Now open up Wifi Tether on your phone and go to settings. Now, for optimal compatibility, change SSID to be named wifi, change channel to 06, and change LAN to 10.10.1.0/24.
Now go back, and tap - press to start wifi tethering -
It should go off without an error (if you do get one, just shut it down and and start it back up again.)
Now wait a bit on your computer, and you should see a wifi network with the SSID you put (wifi) on the network list. Connect to it. Wait a little bit.
Your PC is now tethered to your phone via wifi! It might be a tad slow, but hey.

*additional notes for bricked phone sufferers.*
I will give some advice on getting out of the bricked phone state.
The main objective when you have a bricked phone is to shell into that phone via adb.
Once you have a shell into your phone via adb, you should be able to resolve the issue with standard rom/recovery/kernel installation instructions.
If you are having trouble getting your computer to recognize your phone via USB try these things:

Pray.
Restart phone in recovery mode, and check to see if it connects.
Restart phone in download mode.
Restore factory defaults.
If the above do not work, and you are unable to boot into the main OS try these things:
Keep restarting phone and waiting.
Keep restarting and pressing buttons.
Once you are finally in, and if it boot loops, try turning on and off USB debugging and  try mounting it.
If it is still boot looping and it still doesn't recognize the phone, just wait. Let it boot loop several times, and it should eventually be recognized.



« Last Edit: April 16, 2011, 09:43:09 am by Scrotius » Logged
xMrTimx
Newbie
*

Cookies: 0
Posts: 3



View Profile Email
« Reply #1 on: April 05, 2011, 06:31:46 pm »

NEED...HELP...NOW. Everything worked until this part:

Quote
Now we are going to overwrite the kernel in the boot partition of your phone with the one we downloaded, using flash_image, then we are going to do the same with the recovery file we downloaded and the recovery partition:

Code:
Code:
adb /data/local/tmp/flash_image boot /data/local/tmp/zImage.img
 adb /data/local/tmp/flash_image recovery /data/local/tmp/recovery.rfs

You'll see a bunch of text and a block of numbers, if it says something to the effect of write and there are no egregious errors (even if there are it will probably work), you can assume it worked. You will probably not notice a difference with the new kernel other than perhaps speeds or compatibility. The recovery however, will look different.


No block of numbers, but a lot of text, and recovery screen is no different, with no "Advanced" option. This is what CMD displayed:





My guess is adb didn't recognize the command or something, because it lists all available commands. Please help ASAP. Thanks!
Logged
Scrotius
Newbie
*

Cookies: 0
Posts: 4


View Profile Email
« Reply #2 on: April 05, 2011, 06:56:50 pm »

Ah s***. Thanks for letting me know. You were supposed to shell in and run those commands, sans adb in the front.

So input these commands from command prompt while in the directory with adb:

Code:
adb shell
/data/local/tmp/flash_image boot /data/local/tmp/zImage.img
/data/local/tmp/flash_image recovery /data/local/tmp/recovery.rfs

I will edit my post with this change.
Logged
jaypizzle
Newbie
*

Cookies: 0
Posts: 3


View Profile
« Reply #3 on: April 05, 2011, 07:45:40 pm »

So this is all very exciting. I've yet to do any rooting or fun stuff at all, but upon reading that VI is delaying the intercept's Froyo update AGAIN, I got impatient for a better phone and found this guide.
I ran into the above described problem but I thought I did something wrong, so I figured out how to get the latest version of ixnane updater on my phone. That's what appeared to me to be broken.
So I put the ixnane recovery program on the phone with the patched samsung update software.
Then I used that to apply the ROM, and everything went OK.
Now I can use the phone with what looks like a totally different setup - I've yet to explore it.
Am I still missing the kernel change, though? I think I fixed the recovery software issue, but I didn't do anything about missing the Zimage.img file.
So if that is the case, what are the effects of that, and how can I fix it up further? I imagine a different kernel is half the point.
Thanks, anyway!
Logged
Scrotius
Newbie
*

Cookies: 0
Posts: 4


View Profile Email
« Reply #4 on: April 06, 2011, 12:03:23 am »

So this is all very exciting. I've yet to do any rooting or fun stuff at all, but upon reading that VI is delaying the intercept's Froyo update AGAIN, I got impatient for a better phone and found this guide.
I ran into the above described problem but I thought I did something wrong, so I figured out how to get the latest version of ixnane updater on my phone. That's what appeared to me to be broken.
So I put the ixnane recovery program on the phone with the patched samsung update software.
Then I used that to apply the ROM, and everything went OK.
Now I can use the phone with what looks like a totally different setup - I've yet to explore it.
Am I still missing the kernel change, though? I think I fixed the recovery software issue, but I didn't do anything about missing the Zimage.img file.
So if that is the case, what are the effects of that, and how can I fix it up further? I imagine a different kernel is half the point.
Thanks, anyway!

You will have the kernel that is loaded with CuteROM. It is vamirefo's. This is verified by looking in your settings, about phone, and kernel version. It should say: 2.6.29


The kernel replacement instructions are there for thoroughness and to show how the kernel is replaced.
Logged
xMrTimx
Newbie
*

Cookies: 0
Posts: 3



View Profile Email
« Reply #5 on: April 06, 2011, 02:26:34 pm »

THANKS! Those fixed commands did the trick! WiFi tethering now works (just tried it on my laptop), and I have a rooted phone! I've been looking around for rooting guides for the Intercept, but I this is the first step-by-step one I've found. I can't thank you enough! That aside, do you know if this ROM/kernel supports overclocking? Thanks!
Logged
jaypizzle
Newbie
*

Cookies: 0
Posts: 3


View Profile
« Reply #6 on: April 06, 2011, 04:49:59 pm »

So this is all very exciting. I've yet to do any rooting or fun stuff at all, but upon reading that VI is delaying the intercept's Froyo update AGAIN, I got impatient for a better phone and found this guide.
I ran into the above described problem but I thought I did something wrong, so I figured out how to get the latest version of ixnane updater on my phone. That's what appeared to me to be broken.
So I put the ixnane recovery program on the phone with the patched samsung update software.
Then I used that to apply the ROM, and everything went OK.
Now I can use the phone with what looks like a totally different setup - I've yet to explore it.
Am I still missing the kernel change, though? I think I fixed the recovery software issue, but I didn't do anything about missing the Zimage.img file.
So if that is the case, what are the effects of that, and how can I fix it up further? I imagine a different kernel is half the point.
Thanks, anyway!

You will have the kernel that is loaded with CuteROM. It is vamirefo's. This is verified by looking in your settings, about phone, and kernel version. It should say: 2.6.29


The kernel replacement instructions are there for thoroughness and to show how the kernel is replaced.

Well, sweet. I've been playing with this for hours and I have to say thanks to all the modders and programmers and to Scrotius for the clearest instructions on rooting this phone I've ever seen.
I've reset to factory settings before, and I'm always careful about installing just the programs I really use, but even on day 1, the old setup was never better than poor. It warranted a barely-passing "D" grade, at best. Running Virgin Mobile's stock Android 2.1 image on the Intercept is like running Windows 95 on an original 486. It's possible, but really, really unsatisfying. It's worse than not having the best OS at all, because even though you know you should just go back to something that runs properly, you can't make yourself give up those awesome new features. So you end up just swearing a lot.
Now, I can browse simple web pages smoothly and and relatively quickly (with Dolphin HD, at least). I checked my calendar while on a phone call which came in while I was listening to a podcast and the phone didn't even freak out. Previously, I wouldn't have even tried. Those wretched soft touch buttons even work most of the time! I honestly didn't even realize the Samsung touchscreen could even deal with input as fast as it is apparently capable of.
My roommate's iPhone 3gs is still better, but I can quite literally buy a case of beer and a week's worth of groceries with just the $45 difference in our phone bills. I can't complain.
Logged
expo1001
Newbie
*

Cookies: 0
Posts: 2


View Profile
« Reply #7 on: April 09, 2011, 11:28:01 am »

Ok, I think I f***** up. I just got a shiny new intercept, and rooted it... worked beautifully, I might add... But I forgot to activate it with Virgin first, and now it will not activate using Virgin's instructions. I'm running into trouble when the the instructions call for me to dial "Dial #-#-8-4-7-4-4-6-#". I am getting an error message which says, "invalid lock code". Any help would be GREATLY appreciated!
Logged
expo1001
Newbie
*

Cookies: 0
Posts: 2


View Profile
« Reply #8 on: April 09, 2011, 11:19:23 pm »

Never mind, I figured out that the activation was some sort of app built into the stock OS, so I found the stock rom, re-flashed it, and was able to activate my phone. Afterward I was able to re-flash with CuteromX. Working like a champ now. :)
Logged
wirenut
Newbie
*

Cookies: 0
Posts: 18


View Profile Email
« Reply #9 on: April 21, 2011, 06:58:11 pm »

can u not just use z4root for the rooting aspect of it? serious question...not being smart
Logged
wirenut
Newbie
*

Cookies: 0
Posts: 18


View Profile Email
« Reply #10 on: April 21, 2011, 07:28:49 pm »

No instructions on how to install superoneclick. does it need to be installed on pc then move the apk file to the sd and install that on the phone as well?
Logged
NoNameFace
Psychotic Female
Global Moderator
Full Member
*****

Cookies: 3
Posts: 245



View Profile
« Reply #11 on: April 21, 2011, 10:02:57 pm »

No instructions on how to install superoneclick. does it need to be installed on pc then move the apk file to the sd and install that on the phone as well?

Please use the forum search feature. There's a bazillion new posts about one click rooting.  Wink
Logged

LG Optimus V: CyanogenMod 7 BACKside IHO, CWM Recovery, MIUI 1.8.12 Theme
Samsung Intercept: Stock
jaypizzle
Newbie
*

Cookies: 0
Posts: 3


View Profile
« Reply #12 on: April 22, 2011, 10:11:39 am »

So now that the official 2.2 update is out, what steps should I take to get ready to try that out, now that I've made the Scrotius guide changes and have the CuteRom loaded and whatnot?
I assume I should go back to stock, but do I need to use vampirefo or something to undo the file system conversion first? Do I have to worry about basebands? Once I get the phone ready, then, can I just flash a stock VM tar with SWUpgrade or should I use a non-SWUpgrade method?

** edit ** hey since the Scrotius method leaves us with DI06, can we just run the official update? THAT would too easy!  Tongue

** second edit ** I figured it out, mostly. And it mostly easy! My goal was just to try out Froyo, tethered or not. For anyone wondering, if you've followed the above steps and want to get the Froyo 2.2 update, you can't just run it from the automatic text. Maybe you can, but I couldn't figure it out, anyway. You can get Froyo pretty easily anyway provided you still have the regular Virgin Mobile "DI06" baseband. You can check on the phone by looking at Settings>Phone Info. It might say DI05 or DF27 and I can't help in that case - I think you have to do some more hoop-jumping. But if all you did to your stock phone was from this thread (like me) then you should still have DI06.
I did *not* have to reformat to rfs from ext2/ext4. I left that just as it is.
I hooked my phone back up to my PC, turned on USB, and copied dewdude's ROM http://dewdu.de/vm-froyo/VirginMobile-Froyo-StockROM.zip  or http://dewdu.de/vm-froyo/VirginMobile-Froyo-StockROM-Rooted.zip in the sdx folder of the SD card. The thread with discussion of that is here: http://forum.sdx-developers.com/intercept-development-2-2/virgin-mobile-froyo-2-2-stock-system-and-kernel-dump/
Then I turned off usb access on the phone, turned off the phone, and unplugged the usb. I booted the phone to recovery mode and selected install from zip file using the vampirefo recovery program already installed if you followed the Scrotius guide.
Choose the newly downloaded ROM from the appropriate folder and fire it up. It takes a while, but it ought to work. Before rebooting, I cleared the dalvik cache using the recovery program - I forget where the option is but its not hard to find. I have no idea what that does or if I needed to do it but a lot of forum posts suggest it so I did it.
Once it booted, then, I had Froyo 2.2.2 and so far I like it even better than the CuteROM'd 2.1. Now I gotta figure out tethering and whatnot... I used the rooted version of the ROM but I don't seem to have root access. I haven't played around much yet, though.
« Last Edit: April 22, 2011, 03:27:30 pm by jaypizzle » Logged
blb1980
Newbie
*

Cookies: 0
Posts: 19


View Profile
« Reply #13 on: May 24, 2011, 05:31:36 pm »

Does this work on 2.2 updated phones and do you have to have windows 7 in order to do it?
Logged
NozeDive
Newbie
*

Cookies: 0
Posts: 2


View Profile
« Reply #14 on: September 13, 2011, 09:33:28 pm »

Well I'm stuck at step one!

Whenever I try to install the new drivers, as per your instructions, I get a message stating that the device failed to start (code 10)

I am, of course, using a Samsung Intercept. I have Windows 7 Home Premium SP1 64-bit.

I have tried with different USB cables, different MicroSD cards, no card, remove and reinsert card, etc.

+100,000,000 internets to anyone who can help me. Not only would wireless tether make my life a lot easier (for work and school), but just getting a computer to recognize my phone would be awesome. Sad
Logged
Pages: [1]
Print

Jump to:  

Got a new phone? Find the forum here


Related Topics
Subject Started by Replies Views Last post
Intercept WIFI tether status???
General Android discussions
mLAR 1 8460 Last post February 02, 2010, 02:35:22 pm
by yourm0m1
Wifi Tether not working « 1 2 »
Android 2.1 Discussions
Belloc 16 9356 Last post May 25, 2010, 08:25:31 am
by yourm0m1
Kcmartz (Virgin Mobile Intercept)
Introduce Yourself
kcmartz 2 5078 Last post March 24, 2011, 10:55:31 am
by rican199
Guide for Flashing Custom Recovery using ADB
How To....
EducateAndInnovate 0 1823 Last post April 22, 2011, 01:29:18 pm
by EducateAndInnovate
Intercept Root Apk and Recovery flasher
Rooting
EducateAndInnovate 3 8505 Last post July 17, 2011, 03:59:41 pm
by adj




Thanks for visiting Samsung Intercept Forum Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Sitemap