Database Users

Samsung Intercept

Will there be a forum for the samsung intercept?

Forum for samsung intercept
I can deal with the un-rooted version, because it's still a great phone for what you pay. However, I have the sprint version of the samsung intercept (assuming there's more than one carrier for this one), and I H-A-T-E all the crap that it comes preinstalled with. I hear people saying that these apps don't take any active RAM, but sysinfo and advanced task manager say otherwise..."sprint zone" is the most nefarious offender...if anyone would develop the root, I would L-O-V-E (guess I'm into spelling to-day) to donate to your efforts.
-Lukewarm Samsung Intercept user/loser.

I really hope we can get a forum for the intercept soon. I know the phone was cheap on contract but its not going to be worth it to me if no one works on a root! Maybe our prayers will be answered soon! *fingers crossed*
Sent from my SPH-M910 using XDA App

PLEASE!!
I just got the samsung intercept and I want to root it.

It would be nice for the Samsung Intercept to have its on forum. The Kernel for it is already out. I don't see why we can't get a little section of our own too. :\

granted i know that this is the bottom of the line android phone but why is it no one will actually root it ? they have already rooted the evo,epic,droid,galaxy s ect..
why is it no one will actually take the time to root the intercept or the moment.
i'm sure it cant be too much different than rooting the epic.
people claim they are going to root it but no one follows through
i dont want to flash the rom

If there won't be a forum for it here, would it be okay for users to post links to sites that have a forum for interecept. I have many questions but no place to ask them and I don't want to fill this thread with them since they don't belong here.

The phone has been rooted now actually. If you go to the sdx developer site you'll see it.

I went there and read the instructions. I am going to try rooting it tonight. Do you know if the amon ra recovery image will work with it? If not, is there an alternative recovery image with similar functionality/options?

I have a friend who has the samsung intercept, and I rooted it using the new one click universal rooter, but it was only a partial root.. The phone is still virtually not rooted... (no Titanium, market access, busybox, tether, etc.) Please help me get this thing fully rooted. He is willing to donate 10 bucks or so.

Why are there no XDA Devs responding?
Weird, its like the twilight zone or something. No support for a newish device. There are far worse phones on here, so not sure what the deal is. Maybe they're all too busy with their sweet new Evo's and the like. I wouldn't want to spend too much time on this one either (I have an Evo), but given people are willing to donate, and aren't asking for anything more than [complete] root, I don't see why not.
I'd like to get this phone for my wife. She won't spend any money and I can get this one for free. I want her on an Android phone to facilitate some mobile functions between the two of us. I see no better way to do it (while staying with Sprint) than with the Instinct. Seems nice enough in the video reviews. She's still using her Instinct! ;-P

All I want is a working recovery. One where I can wipe and not brick this phone. It is possibly the worst piece of junk I've ever layed my hands on. I figured stock would be great for my fiancee, she knows nothing of rooting and wouldn't care if she did. However, the stock ROM that came with this was MISERABLE! (Virgin Mobile, btw, not sure if they did anything different from sprint other than differing bloatware.) That being said, I decided to root the thing for her and see if I would help with the lag issues and other things. Nothing did. All the custom ROMs had an issue where the phone would be so slow I had to pull the battery out to even use it again. It was as if the processor was running at 60MHz and wouldn't get any faster. Superuser would not request permissions for anything except root explorer - everything else automatically were granted access and did not show up in superuser's app list which can be VERY dangerous. Superuser also keept saying it needed to be updated no matter how many times I updated it. Andora ROM wouldn't allow the holding of the power button or it would freeze up. As a final issue, ADB wouldn't recognize it at all. I use ADB for my G2 all the time so I know what I'm doing and I know it's not my PC. It would recognize it in recovery but any command would fail and the device would become unrecognizable again until i issued "adb kill-server." Again, though, any command make the phone unrecognizable.
Now I like the phone for the budget qualities and virgin mobile's plans (great when you're super short on money) and the fact that they have an Android phone so you can still enjoy the greatness of Android on a budget, and I don't even want anything extreme out of this phone other than for it to just work like Android should.
Thank you to all the devs who have devved for this phone so far, and they've came a looooong way and I agree it's better than when I opened the box, but we need a working recovery at least. Yes, the recovery gets the job done but it needs some serious work and at least a working recovery. I think a lot of ROM issues come from not being able to wipe.
I'm not blaming any one for all my issues, I know the devs work hard for nothing but donations and I thank them greatly for that. Its not even really the custom ROMs as it is just the phone. I read up on it before purchasing and saw it had a good amount of RAM and a 800MHz processor and thought this phone was actually going to be able to compare to a G2 (speed-wise) but boy was I wrong. I'm feeling extreme buyers remorse and everything said above was just me getting it off my chest. I actually didn't plan to root it at all. My fiancee doesn't do anything really other than text, play some games, get on facebook, and occasionally look up things on google. The phone does all these extremely well but has so much instability in between doing these things that every time she picks it up it is unknown if she's going to be able to do any of them without the phone crashing or lagging so bad she has to pull the battery.
If we can get this phone running and VANILLA Android, such as cyanogenmod or just a goold-ol-fashioned AOSP build, I think it would be a great phone with much more potential is has now.

wait, so the intersept now has a forum, but not the TRANSFORM? messed up...

the intercept also has 2.2 as of today!!!!!!

r3s-rt said:
If we can get this phone running and VANILLA Android, such as cyanogenmod or just a goold-ol-fashioned AOSP build, I think it would be a great phone with much more potential is has now.
Click to expand...
Click to collapse
r3s-rt - the biggest issue is samsung and their RFS filesystem and their proprietary drivers; which is a huge fail to porting over to AOSP or cyanogenmod... plus, there aren't that many devs (they're all working on the higher tiered phones...)

What file system would need to be used for it to be easiest?
Sent from my HERO200 using XDA App

Froyo Update
My Samsung Intercept updated to Froyo 2.2 this morning.

I got pushed the 2.2 update but it failed due to my custom inxane recovery, going to revert it to stock and try it again my brothers is on 2.2 and it pushes the stock android theme as well so no more crappy customized theme!

Not sure if this is the place to ask this question, but I will go ahead. 2 Months ago I got the intercept with a new sprint contract. I instantly wanted to root it, but decided to wait for the froyo update. Well, now I have the official froyo update up and running (SOOOO much better!!!!) so I decided to work on rooting it. First problem I had was the USB drivers. over the course of about a week, I discovered that the drivers work fine so long as you don't plug it into your PC through a USB hub (internal OR external). I followed the instructions in sprintdroids. (I read the entire thread several times hoping to learn from other people's experience). I tried both the official samsung drivers and the ones posted with PDAnet. I also tried both the one click root listed elsewhere on this site as well as SuperOneClick. The one click root gave me the following output:
exploit and busybox made by joeykrim and one click installer made by noobnl
Press any key to continue . . .
copy and run the exploit (may take 2 minutes)
37 KB/s (0 bytes in 5392.000s)
0 KB/s (0 bytes in 88.000s)[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C[*] checking NPROC limit ...
[+] RLIMIT_NPROC={1344, 1344}[*] Searching for adb ...
[+] Found adb as PID 1892[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] [email protected] so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.
make it RW and move files
mount: Operation not permitted
failed to copy 'joeykrim-root.sh' to '/system/bin/joeykrim-root.sh': Read-only f
ile system
failed to copy 'jk-su' to '/system/bin/jk-su': Read-only file system
failed to copy 'playlogo-orig' to '/system/bin/playlogo-orig': Read-only file sy
stem
failed to copy 'playlogo' to '/system/bin/playlogo': Read-only file system
failed to copy 'busybox' to '/system/bin/busybox': Read-only file system
failed to copy 'resolv.conf' to '/system/bin/resolv.conf': Read-only file system
failed to copy 'remount' to '/system/bin/remount': Read-only file system
set permission
Unable to chmod /system/bin/joeykrim-root.sh: No such file or directory
Unable to chmod /system/bin/playlogo: Read-only file system
Unable to chmod /system/bin/busybox: No such file or directory
Unable to chmod /system/bin/remount: No such file or directory
Unable to chmod /system/bin/playlogo-orig: No such file or directory
push any key to reboot the phone
Press any key to continue . . .
Yes, USB debugging was ON and my screen was not locked.
SuperOneClick did nothing and said my phone was rooted. I am unable to perform any root functions (one touch reboot, delete bloatware, overclock, etc.) therefore I do not believe I am rooted.
I am running Windows XP Media Center Edition. I get the same results no matter which driver I use. Any suggestions?

The easiest way to get root right now would be to either use the one click that's available for the intercept over on sdx-developers.com or to flash a rooted kernel like slapkernel v1.1.
Sent from my SPH-M910 using Tapatalk

Rooting

So is there a single WORKING root method for this phone? I have read the wiki, the first method is not even up to date...
Second one does not include all the needed drivers...
Digging I found a hacked one click root.apk... it fails
I have had 6800, 6850, Omnia, Eris, all with custom roms, yet I can not for the life of me root this PoS. Look I understand no one here gets paid, but would someone here PLEASE take pity on a soul that wants nothing more than to put his phone through a wall?

I've used this one many times http://destdroid.com/showthread.php?11-Droid-X-2.2-Root-Manual-Method
Sent from my DROIDX using XDA App

OMG i think I finally got it. I had to install Motoconnect, not just drivers, and I had to use a link on one of the other pages down the thread, I will post it later...

The one click in the Wiki worked fine for me. Then search out for bootstrap to get clockwork on there.

The doroot method for D2 works flawlessly

I cant get the instructions linked on post 1 to work. i prefer to do it myself in linux rather than use a script or a oneclick root. i tried the instructions on linux and adb never dies on the linux shell, so do these instrucitons not work on linux or need to be changed perhaps?
after 10 minutes i manually killed the adb shell pid in linux. then did a adb shell again, its slow as hell and as i figured there are thousands of rageagainst.bin's running (i renamed to shorten it, maybe that is the issue?) as i beleive this is how the exploit works, but it doesnt appear to be working on the 2.2 full sbf?

Check my site for step-by-step tutorials with links to all necessary files/programs. It's a new site but so far I have guides for installing ADB drivers, Rooting/UnRooting, and increasing the screen resolution for the DX.
www.TweakMyDevice.com
I'm adding more and more tutorials as I have time. Let me know if you have any questions/comments/concerns.

Rooted With Skyraider 3.3.3 and OTA update

Ok so I've read through the threads and haven't been able to find an definitive answer. I know I can get rid of the msg by editing a file on the phone, but I am wondering about the update.
I am rooted and s-off and running ClockworkMod 2.0.5.5 with Skyraider 3.3.3.
The OTA update msg is showing up on my phone. Can I update with my current state?
If so, must I wipe data and cache? Will it unroot me and bring the phone back to stock specs?
Thanks
Sent from my ADR6300 using XDA App

Would like an answer too. I just want to know if it would effect my root and so on.
Sent from my ADR6300 using XDA App

I actually have stock rom with root and just got the update. When it asked to install it counted down before restarting in recovery but once it hit zero the box disappeared and the phone did nothing. Under software updates it says system is up to date. Idk what happened??
Sent from my ADR6300 using XDA App

Also getting this system update. Skyraider 3.3 sense, dinc.
The details of the update say it is a 17.7mb file with "vcast apps, slacker, and many other improvements for your Droid incredible".
Just looking for a way to get rid of this notification. Thanks

Also getting this system update. Skyraider 3.3 sense, dinc.
The details of the update say it is a 17.7mb file with "vcast apps, slacker, and many other improvements for your Droid incredible".
edit:
Found this over at android forums, much love...
OTA, or “over-the-air”, updates are data packages sent by Verizon to update the Droid’s firmware. They add features, fix problems, and speed up the phone. So why would we want to block these updates? Well, with the update comes a wipe of all our hard work–Root and other hacks alike. Also, with the upcoming 2.1 update comes a patch to remove the loophole used to obtain Root. Until Root is achieved on an official Droid 2.1 firmware, it is necessary to block OTA updates if you want to keep Root.
Disclaimer
(2/5)
Prerequisites: (Please be familiar with the following)
Android Debug Bridge
Unix Commands
USB Debugging
USB Debugging Drivers
Requirements:
USB Data Cable
Step 1: PC Connection
Using the method found in the USB Debugging guide, connect your Droid to a PC via USB and enable USB Debugging.
Step 2: Enabling Airplane Mode
Because we will be modifying a file that will interact with OTA updates, there is a potential problem if the file receives an update while we are working on this hack. For this reason, we will turn on Airplane mode which disables all wireless communications to and from the Droid. Go into the phone settings.
Select Wireless & Networks.
Ensure that Airplane mode is checked.
You will notice the wireless signal icon in the notification bar now has a small airplane on top. You are now ready to modify the OTA update file.
Step 3: ADB Commands
Using the method found in the Android Debug Bridge guide, open Command Prompt and point it at your Android SDK tools folder. You will now be entering in the following commands, please read and copy all lines carefully. If you will be copying and pasting, remember to right click inside of Command Prompt and select “paste”, otherwise it will display your keystrokes. After each line, press enter to input the command.adb shell
Initiate the Unix terminal emulator so that Unix commands may be sent.
su
Connect as a “substitute user” to gain permissions for the following commands.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Readies the mtdblock4 and System filesystems.
cd /etc/security
Change to the Security directory on your Droid.
mv otacerts.zip otacerts.zip.bak
Renames otacerts.zip to otacerts.zip.bak.
exit
Exits su session.
exit
Exits shell session.
This hack is very simple; we are merely renaming a file necessary for OTA updates. When Verizon pushes an update, it will look for this file. Because we renamed it, the update will not be pushed to the Droid. You now no longer need to worry about losing Root! Also, at this time, you may disable Airplane mode.
Fortunately, this process is completely reversible.
Optional: Unblock OTA Updates
If by chance you have a change of heart and would like to accept OTA updates, we can easily reverse our hack. Simply follow everything in Step 3 except when you get to the renaming command. Instead, flip the command to rename the file back:mv otacerts.zip.bak otacerts.zip
Renames otacerts.zip.bak to otacerts.zip (the original file name recognized by Verizon OTA updates).
Remember to do everything else in Step 3 exactly.

http://forum.xda-developers.com/showthread.php?t=836120

http://androidforums.com/incredible-all-things-root/217209-got-rid-ota-update-nag.html
Got rid of mine doing this step above....didn't look promising at first but after reboot #2 I waited till everything booted and synced and now my OTA nag is gone. I have shown no negative recorse yet, but nanned just in case. Good luck...let me know if this worked for everyone else!

It worked for me...
Got rid of mine doing this step above....didn't look promising at first but after reboot #2 I waited till everything booted and synced and now my OTA nag is gone. I have shown no negative recorse yet, but nanned just in case. Good luck...let me know if this worked for everyone else![/QUOTE]
Tried the procedure described in the link and it worked great! Thanks for posting it! I have been looking for this all morning!!

I think the more important question we should be asking is what is actually in this update? Skyraider versions have always blocked ota updates to my knowledge, and included the content in the rom itself.
If there is something in this update that may be useful, I for one say instead of blocking it we should try to find a safe way to apply it.

[Solved] Cant reroot after 340!

Cant figure out for the life of me how to reroot after doing the 340 ota. I came from 2.2 ota.
I tried z4root multiple times, no dice.
Tried the DoRoot Automatic script. Didnt fully work.
Tried the manual method on the phone with term emu.
Tried the manual method...and im getting stuck here...
Factory Reset and did it all AGAIN... So annoyed
Mod note from Sleuth
Wispirer figured this out further down in the thread. It has to do with different versions of the superuser apk file confusing z4root. His post is here
nicely done btw
end mod note
[*] Searching for adb ...
[+] Found adb as PID 6025[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] [email protected] so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.
$
C:\Users\matt\Desktop\android-sdk-windows\platform-tools>adb kill-server
C:\Users\matt\Desktop\android-sdk-windows\platform-tools>adb.exe devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015A9D7E1303301A device
C:\Users\matt\Desktop\android-sdk-windows\platform-tools>adb shell
$ mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount: Operation not permitted
$

z4root sat for 5-10 minutes on "running exploit" when I ran it. Others have also reported this.

I experiened that ONCE too, but i pulled the battery after a few minutes since it went through the full process so many times before.

anyone any ideas?

same problem here...can't get root back yet

Just to make sure, when you guys are rooting you have USB debugging on, yeah?

Also, does 1click root work? Several DX flavors. Check the Wiki. Link in DX android development.
Some questions:
What precisely happens when you try to use z4root? Give me the step by step.
Can you get temporary root with z4?

Sleuth255 said:
Also, does 1click root work? Several DX flavors. Check the Wiki. Link in DX android development.
Some questions:
What precisely happens when you try to use z4root? Give me the step by step.
Can you get temporary root with z4?
Click to expand...
Click to collapse
It goes through the whole process, says its rooting, getting shell, etc, goes white for a second, says rebooting, come back up and no root. And nope, tried both options.

Same here. The main thread about the update says it can take as many as 10 tires. I'm on about #5. we'll see.

That doesnt quite make any sense to me....

Same thing is happening to me, z4root says using exploit, acquiring root shell, goes to white screen then goes back and says rebooting. After it reboots still no root.
Tried 1 click method and it hangs at performing the rage command. Manually tried rooting and after applying the ./rage it kicks me off like its supposed to then says my device isn't found when I do adb devices command.

Yup, Same. I even factory reset twice.

Interesting. I have both copies of the update.zip. I did notice that they were slightly different in size. I used the very first one that was posted. I'm gonna do a quick hex compare to see if they're the same...
edit: uh oh, the two update files are totally different. The original one is slightly larger and HexCMP finds no similarities after the first 1K or so. The one I used had a size of 26,358. The other, more recent one has a size of 26,259.

So whats that mean exactly? Two versions of OTA were pushed out? One rootable and one not?

It sure looks like there's two different sizes and a hex compare shows significant differences. Take a look at your update.zip. What is the precise size? If everybody who can't root has a size of 26,259 then the validity of your thought is supported.
Remember, the original update only went out to a special beta test group and then was quickly pulled. The one I used was that update.

Where do i find the update.zip file? I did the ota update

Review the Droid X 2.3.340 Update thread in this forum. Good history about this update there including the information you seek.

I tried to root with Sil3ntK1ll Root X 2.2 and it looked like it was taking until about 3/4 of the way it said waiting for device. I left it for 5 min and it was then locked up solid. I had to pull the battery and reboot. No ill effects after the reboot but I am not rooted.
So I assume the root authors are already hard at work on fixing this issue?

same story as everyone else, had root, did update, cant get it back

Found this method, hxxp://forum.androidcentral.com/motorola-droid-2/40283-how-root-droid-2-without-computer.html (note: change x's to t's) and lo and behold it worked! Did from top to bottom and now back to being rooted. Hopefully this method works for you guys.

Wanting to root

Regarding this page:
http://forum.xda-developers.com/showthread.php?t=991072
(Guide) Flash SBF to Motorola Atrix 4G
I was hoping to get some help.
I have an unrooted Atrix. It's my first Android phone. I already installed the latest update, 1.5.7, when it came out.
I'd like to roo the phone, but according to the above link I have to flash back to 1.2.6. I think I can handle the rooting process, but the flashing to the prior build is what I'm confused on how to do.
Am I understanding this correctly?:
1. I download the 1.2.6 file. Question: (What is the 1.5.2 file?)
2. Download the RSDLite 5 and install it.
3. I have a Windows Vista 32 bit system, so install the
32 bit file since I'm not rooted.
4. Then follow the instructions...turn off phone, ect..
5. On Step 7... Load up the SBF file, that would be the 1.2.6 file correct? I'm asking because I don't know what that 1.5.2 file mentioned earlier is. Does it matter where this file is extracted to on my computer?
After this is all done then do I I go to this page
[SCRIPT] GladRoot v4.2 (Bell 0.37.4, AT&T 1.26/1.52/1.57 Supported - Now w/ UnRoot) and do the first set of instructions?
Sorry for all the questions. I'm new to this and don't want to brick the phone. I really want that Titanium Backup program so I can backup and freeze some things.
Thank you
Don

I had the 1.5.7 update without root and a few days ago I did the same thing.
1. I download the 1.2.6 file. Question: (What is the 1.5.2 file?).
just get the 1.2.6 file
2. Download the RSDLite 5 and install it.
yes
3. I have a Windows Vista 32 bit system, so install the
32 bit file since I'm not rooted.
yes
4. Then follow the instructions...turn off phone, ect..
yes
5. On Step 7... Load up the SBF file, that would be the 1.2.6 file correct?
yes
I'm asking because I don't know what that 1.5.2 file mentioned earlier is. Does it matter where this file is extracted to on my computer?
no
After this is all done then do I I go to this page
[SCRIPT] GladRoot v4.2 (Bell 0.37.4, AT&T 1.26/1.52/1.57 Supported - Now w/ UnRoot) and do the first set of instructions?
if you have AT&T yes. Extract it so that it's C:\GladRootv4.2. When you run gladroot.bat be sure to answer yes to the question "Are you updating an AT&T Atrix on 1.26 to 1.57? [y/n]"
I got the adb "Unable to detect device" error whenever I ran the scripts. Just run the command adb services in a command prompt (You should see a device name as output) while in the C:\GladRootv4.2 directory for your computer to detect your phone properly and then run the script.
It's fairly painless, the SBF flash can take a while, 15-20 minutes or so. You will lose nearly everything that's on the phone, so save what you want to keep. I did notice the ringtones that I saved onto the phone (not on the sd card) were still there.

Root explorer is more interesting IMO.
Cheaper than TB.
Just need to rename apk bay adding a .bak to freeze them.

Thanks for the quick replies. These forums are great!!
One last question. Once rooted, if Motorola comes out with future updates, will this process need to be repeated for each update?
Thanks again.
Don

Shaydar said:
Root explorer is more interesting IMO.
Cheaper than TB.
Just need to rename apk bay adding a .bak to freeze them.
Click to expand...
Click to collapse
i'd rather pay for few bucks for TB to have a quick and easy "freeze"/"unfreeze" button than to keep going in and manually renaming apks.
plus you can do all the root exploring and file managing that you want for FREE with super manager (in market).

dwaded said:
Thanks for the quick replies. These forums are great!!
One last question. Once rooted, if Motorola comes out with future updates, will this process need to be repeated for each update?
Thanks again.
Don
Click to expand...
Click to collapse
Not sure, it depends how devs here on xda manage to root a future build. If the approach is the same as what is available now (preserve root in current build, update, restore root) you will not need to do the flash, lose everything etc. only if you run gladroot.bat prior to the official update. If you install the official update without running gladroot.bat then you'll have to go through the fun that is SBF flash.

I have a question about this as well, so I thought I'd ask here instead of a new thread...but at the drivers section of the instructions, it says just download them but if I've rooted my phone I should already have them. But if I've connected my phone to my computer by USB before just to transfer files, even if I haven't rooted, should I already have the right drivers?

thebeardedchild said:
I have a question about this as well, so I thought I'd ask here instead of a new thread...but at the drivers section of the instructions, it says just download them but if I've rooted my phone I should already have them. But if I've connected my phone to my computer by USB before just to transfer files, even if I haven't rooted, should I already have the right drivers?
Click to expand...
Click to collapse
Maybe. I would just install the specified drivers listed just to be safe. It's not a very large install file.

gnahc79 said:
Maybe. I would just install the specified drivers listed just to be safe. It's not a very large install file.
Click to expand...
Click to collapse
Alright, fair enough! Thanks for the help!
EDIT: Actually one more question. Does flashing the original SBF clear my phone? If it does, how can I backup everything on there if I'm currently unrooted? (I'm flashing this so that I CAN root later on). I'm not too worried about this I guess but I should be prepared anyway...