yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] twobit:
Root instructions

1) get RageAgainstTheCage from here stealth.openwall.net/xSports/RageAgainstTheCage.tgz (all credit goes to Sebastian Krahmer at c-skills.blogspot.com/) and unzip it

2) Get su, busybox, Superuser.apk

3) adb push rageagainstthecage-arm5.bin /data/local/tmp/

4) adb shell (now you will see the $ prompt)

5) type "/data/local/tmp/rageagainstthecage-arm5.bin" (without quotes) in adb shell

5) wait till adb shell closes

6) adb shell again, and now you should have # (i.e. adb root shell)

7) type "mount -o rw,remount /dev/block/stl9 /system" without quotes in adb rootshell to mount system as rw

8) exit adb rootshell

9) push su and busybox to /system/bin using "adb push <path to su>/su /system/bin/su" AND "adb push <path to busybox>/busybox /system/bin/busybox"

10) push Superuser.apk to /system/app using "adb push <path to Superuser apk>/Superuser.apk /system/app"

11) adb shell

12) you will be back at the # shell

13) cd /system/bin

14) chmod 4755 su

15) chmod 4755 busybox

16) reboot your device

Now you should have root that sticks
[Fascinate Android Development] mackeydesigns:
Totally beyond my scope of knowing what to do without breaking something, but so glad a fix is OTW.
[Fascinate Android Development] DeezNotes:
Thanks twobit! I used your directions with a few modifications. If it works I'll re-post right away.
[Fascinate Android Development] fallingup:
follow guide here by joeykrim: http://forum.sdx-developers.com/epic-development/adb-root-exploit-test/
[Fascinate Android Development] Zennmaster:
Out STANDING!!!!

Not bad, phone came in the door at 11:49, and by 13:25 had verified persistent root!

You guys rock!

Now to de-Bing this puppy!
[Fascinate Android Development] Zennmaster:
A wee bit of trouble I had, nothing to do with the instructions, but it appears that some recent versions of ADB don't recognize Samsung phones. The solution for me was to upgrade to the most recent Android SDK (which I shouldhave done anyway!)

Other than that, IT WORKS!!!
[Fascinate Android Development] GHII:
AH, I've gotta learn how to get ADB working on my mac, I was never able to with my OG Droid
[Fascinate Android Development] bblanski:
De-bing and add Google. .
[Fascinate Android Development] DeezNotes:
root doesn't seem to be sticking after a reboot for me. Can you guys confirm root is working after you reboot the phone? I've tried both a manual method plus the joeykrim method.
[Fascinate Android Development] jdkzombie:
ok, so is there a difinitive how to guide for the fascinate yet? i just switched from droid 2 to fascinate and i sure as hell hope rooting it easier than that cursed moto phone. id appreciate a link if anyone has it. and btw, i had tmobile vibrant for a while, why is it that the vibrant had 16gb of internal memory accessible anytime both on pc and on phone, but the fascinate seems to lack the ability to allow said owner to access aforementioned internal storage? BS anyone? i think so.
[Fascinate Android Development] twobit:
I guess it depends on how you look at it. You will have root, but adb will not be running as root. Type "adb shell" and then once you get the $ prompt, type "su". You should see a notification from Superuser app to grant permissions. Once you do, you will have a root shell.
[Fascinate Android Development] Zennmaster:
Yup. Confirmed. I got there by updating the Android SDK (for a new version of adb), and following twobit's instructions to the letter.

The spot where I see potential trouble is after running rageagainstthecage-arm5.bin, adb will return you to a "$" prompt BEFORE it's finished doing its thing. DON'T DO ANYTHING AT THE "$" PROMPT! Wait for adb to kick you all the way back out to your terminal, or it won't work right.

Hope this helps!

-Z
[Fascinate Android Development] Zennmaster:
Yes. It is post #51 in this very thread. If you ask me, it's not at all bad considering the phone has been out for a matter of hours!
[Fascinate Android Development] DeezNotes:
I'll give that a try. After executing the .bin file, I would type exit at the $ prompt. That's how I read the instructions. I'll back all the changes out and give it another try.

UPDATE: It seems to be persisting after a reboot now. I used the updated SDK (September 2010). The older version wouldn't leave the $ prompt after executing the .bin file. Thanks for your help! If I have time, I'll write up a start to finish for Mac users.

However, I noticed when I use Root Explorer it's not prompting me for permissions. I'll keep playing around though. I'm close. This is enough to remove the crappy pre-installed apps!
[Fascinate Android Development] GHII:
Well I tried both instructions and couldn't get it going..hmmm...I did step by step and everything seemed to work, but after I rebooted and ran adb shell and su to get the # it stays a $...AHH

I would love that Deez, im on a mac now trying to get this working...
[Fascinate Android Development] itznfb:
i just get:

/data/local/tmp/rageagainstthecage-arm5.bin

/data/local/tmp/rageagainstthecage-arm5.bin: permission denied

EDIT: nvm.... change permissions on the file to rwx and it might actually execute :)

However,,, the .bin file executed last lines:

[*] adb connection will be reset. restart adb server on desktop and re-login.

$

It's been sitting at the $ for 5 minutes now...

EDIT2: just realized I was in 2 different fascinate root threads... I got it working. 3rd try after 2 device lockups.
[Fascinate Android Development] bdube:
please do write up mac help :)
[Fascinate Android Development] poulosjr:
is there going to be a simple updated zip file specifically for

SCH-I500 soon, that has root in it like the captivate and vibrant do.
[Fascinate Android Development] nickhorvath:
There seems to be some trouble getting an update.zip properly signed for the fascinate. Even once we do we don't know that the root for the other Galaxy S phones will work because they are GSM and Fascinate is CDMA.

In the long run there probably will be one but if you want it sooner rather than later you're better off following the directions in this thread in post #51 (first on page 6)
[Fascinate Android Development] poulosjr:
wouldn't it then be the same or close to it as the Samsung Epic4G?
[Fascinate Android Development] poulosjr:
where is the internal root of the card located
[Fascinate Android Development] DeezNotes:
I remember reading/watching videos about this for other Galaxy S phones. I'm still not sure what they're talking about, but I do know that this means nothing to me now.

Although I'm not a developer, I do work with computers and I have a slight understanding of what's going on with the current rooting process. Copy some stuff to the SDcard, some stuff to writable folders, execute an exploit which allows you to mount the file system in read/write mode, change some files, add some others where you normally can't, set a start-up script to re-enable it after a reboot and you're good to go.
[Fascinate Android Development] twobit:
I think it might be /sdcard/sd
[Fascinate Android Development] dslisfree:
Just to update if anyone if you are stuck on the activation screen:

Press emergency call button, then at the dialer, press *#83786633, then press the Home key.
[HD2 Android Q&A, Help & Troubleshooting and Genera] |ErosizeD|:
hi guys, i'm here again, with a new question for you..

When i'm recording a video, it's posible to enable autofocus? like the Sony Ericcson Vivaz...

If it's posible, will be great!

( no idiot answers Thx )

Thanks to all, and great job with the htc hd2!!!
[HD2 Android Q&A, Help & Troubleshooting and Genera] joshkoss:
Moved you over to General
[Galaxy S I9000 Android Development] sandandsea:
Hi,

I used to use a Nokia 5310. With it, I could take a call by pressing any button, listenlng via headset and talking to phone's mic, while I was listening to music. Once I hang up the call, the music resumes. All this was done with 5310 phone and a normal 3.5mm headset (without any mic in its line).

Now with SSGS, when I was listening to music via a headset and taking a call with the headset plugged in, voice on the line wouldn't come through the headset. Instead, I had to remove the earpiece and talk to the phone as if the headset wasn't there.

It seems good prople here are able to play with alsa, and I think audio redirecting might be possible.

Could someone point me to the right direction?
[Galaxy S I9000 Android Development] reawatra:
I was just thinking about this the other day. I was in town listening to music and a call came through. It would be nice not having to faff around taking out the earphones to answer a call.
[Galaxy S I9000 Android Development] jdrake001:
+1

Same here, I would love to have this feature, makes the phone that much more useful and 'smart'
[Galaxy S I9000 Android Development] pizzachips:
+1...

It is amazingly annoying to have to pull out my headphones to answer the phone...
[Galaxy S I9000 Android Development] omaga:
In this case galaxy isnt a "smart"phone its from stoneage, have never hade a phone that behave like this..Is it a huge bug in Android?? or maybe the engineers in samsung need a brain transplant.
[Galaxy S I9000 Android Development] gibsonus:
I'd like to be able to use the cassette adapter in my car for music and hands free
[Galaxy S I9000 Android Development] PhoenixFx:
+1

I too would like to see a fix for this problem.

In the meantime I use my old Nokia hands free adapter with an inline mic and a 3.5mm headphone jack inside the car / when using my own headphones
[Galaxy S I9000 Android Development] :
I'm sharing the same dilemma. dunno if there is a software fix for this. I've read a few threads mentioning that Samsung had the mic rigged differently to enable video output thru the 3.5mm jack.
[Galaxy S I9000 Android Development] rishabh_destiny:
Same problem here. Looking for a solution.
[Galaxy S I9000 Android Development] john306:
Haven't got this phone yet but are you saying when the wired headset is plugged into the Galaxy S phone you cannot take a call through the headset?

I currently use a Nokia with a headset same as PhoenixFx pic, I listen to music > call comes in > hit inline remote and take call > finish call by hitting inline remote > goes back to music.....

Don't tell me this cant be done????
[Galaxy S I9000 Android Development] LostAlone:
This is true, and I cannot begin to tell you how pissed I was to discover my Skullcandy headset neither works as headphones or as a headset. IIRC one of the speaker pins and the mic pin are the other way round on the SGS so its not compatible with normal 3-pole 3.5 jacks.

Instead of getting new headphones, I'm going to run with a Jabra BT stereo thing that lets you plug your own headset in. I love my earbuds, and I'm damned if samsung is going to stop me using them, particularly when they don't even have a non-stock set of headphones on sale themselves.

I doubt that this is the cause of the headphones/phonecall thing tho. I guess they just didn't even think of it when they were coding. I don't see why this is impossible, and especially with stuff like Cyanogen just over the horizon, could see it soon.
[Galaxy S I9000 Android Development] PhoenixFx:
You can use one of the Nokia hands free adapters like I do (if you want a cheaper solution then get a 3rd party Nokia compatible one from eBay), however you won't be able to plugin your own mic, but at least the in line mic and your own headphones will work. Built in mic of the Nokia HS-45 is pretty sensitive and can be used even from a distance (especially handy inside a car)

I have no idea why Samsung didn't give the option of using the built in mic of the phone with a headset, or at least provide their bundled headset with a detachable earphone cable like Nokia does. :mad:
[Galaxy S I9000 Android Development] :
@Lostalone:

I Just managed to buy a samsung jack adaptor today. Samsung does sell one here in singapore. You can plug any third party headphones with the mic adapter. Works like a charm.
[Galaxy S I9000 Android Development] decepticon:
My Captivate worked fine but using the same headset on my Bell Vibrant does not work on calls. Where can I find said adaptor or is there a specific headset for the Bell Vibrant/Galaxy S international that works?
[Galaxy S I9000 Android Development] sandandsea:
It should not be hard if we can see/edit the source of the phone app and recompile it.

I will be looking for the source and how to recompile.

I am aware that using a nokia adapter solved the problem. I am using one myself. Though, There are still Times when such adapter is not suitable, such as jogging.
[Desire General] :
I have been passed a HTC Desire to try and fix after a friend of mine ran into issues trying to put Froyo on it. It was originally with Virgin (Virgin boot screen) but was not locked as other sims were usable.

I've tried various different methods to get it up and running but suspect something he has done with his attempts has caused serious issues - also he is not all that clued up and cannot remember exactly what he did - he did mention that RUU update failed, and also an image he had tried to flash from his sd card had got part way through and then locked up on the radio update.

With the original sim and memory card in, the phone will constantly reboot or just stick at the HTC logo. Take the memory and sim cards out, the phone will boot but system wont launch properly so cant get into settings to enable debugging so I can access the device via ADB. I can get to the fastboot screen, and to the Vol Down-Power screen on start, but if I select recovery it stays on HTC logo and goes nowhere.

I have managed to get HBOOT downgraded to 0.8, but when trying to put on original Virgin RUU it says the main version is older (probably because I'm trying to install an older version over a newer one). The stock Froyo RUU fails and tells me wrong HBOOT and sometimes gives a CID error. Although the phone is not locked, I suspect it will still need a goldcard, but cant create one as I cant get ADB access to the phone.

Sorry if this is a bit of a mess but at work and trying to take calls as well as write this and fix the darned phone. I;m not unfamiliar with methods used to get the phone rooted, but not well up on troubleshooting or working around these issues I have.

Any help would be appreciated.
[Desire General] teppic74:
You should be able to restore it by installing this RUU with a working goldcard:

http://shipped-roms.com/shipped/Bra...3.00.32U_5.09.00.20_release_140022_signed.exe

If you get a CID error your goldcard isn't working. There should be no version error with this.
[Desire General] :
Thanks for the reply....however how can I create a goldcard when I cant get the phone to a point where I can get my pc to recognise it? All the goldcard methods I have seen/tried involve having the usb plugged in and debugging enabled - cant get to that stage as phone wont boot - reboot loop most of the time and when I do occassionally get to the os it doesnt last, it will reboot after a few seconds. Anything else I could do? Or, could I use the card in other phone and create the goldcard in that and transfer over? I do have my own working Desire handset.
[Desire General] iain2510:
Don't know much about this but have read that a goldcard is unique to the SD card not the phone so you could create one on your phone and then use it in your mates. Also, from what I've read it would be worthwhile wiping your mates SD card (make sure he's not added a partition to it), copying a Rom to it, and try to install it using Rom manager (or whatever recovery program which was used to root the phone)
[Desire General] :
Ok, I used my own phone to sort out the goldcard and currently trying that out now...will keep you posted. Just started the RUU Stock Froyo and seems to have got further so far. Wish me luck!
[Desire General] :
Mmmmm....ok the RUU worked, but when it restarted (with original goldcard/memory card in, it kept rebooting. It did start once, got to initial setup then promptly rebooted. I swapped out the memory card (no sim in at all by the way at any point up to now) to my own card and after one final reboot it did start up. It doesnt seem stable at all with the original memory card, and still not entirely stable with my card. Could this be a phone fault? Im assuming if the RUU got through all its stages then all areas and files on the phone have been updated correctly and are all correct? Could past failures at updates etc have caused an issue elsewhere?
[Desire General] iain2510:
Have you wiped the various caches? As far as I can make out you need to make sure everything is wiped. I read a post on the OpenDesire thread which suggested that clockworkrom, if that is the recovery program you have installed, may not wipe one of the caches (possibly the dalvik cache) correctly. They recommended another recovery program called something like AmonRu. Although I can't really help you it might be worthwhile saying how the phone was rooted.
[Desire General] :
Ok, none of this was to root the phone. It was to debrand and put on the HTC Desire Froyo build. Not a custom rom, the standard RUU.

As far as I was aware, an RUU restore of the phone would wipe the appropiate caches, but correct me if I'm wrong. The phone now starts with the standard HTC startup and sound and for all intents and purposes is working, but just cant explain the random reboots. These seem to be worse with the 8GB card that my mate gave me with it. Although, after trying mine and putting the original one back in it seems to have stayed stable up to now. I'm beginning to wonder if there may be an issue with the memory card slot - another swap of the memory card again will probably trigger the reboots once more.

We will see how it goes anyway.
[Desire General] teppic74:
You've got a hardware fault. The RUU will completely reflash the phone, so if it flashed successfully but is still rebooting randomly, it can't be software.
[Desire General] :
Your probably right. Just started to try and do a downgrade, and after putting the PB99.IMG file on the gold card I made earlier, then starting the downgrade I noticed it stuck at about 98% on the radio update (second item in the list). I'm going to leave it a while to see if I get an error but I suspect it will not move or do anything.

Having gone through this process before on my own handset, I know it doesn't take anywhere near this long. Thing that confuses me though is that the RUU process I went through before went through with no issues - so why would that be able to successfully install a radio update and not this downgrade process? Anyone else had this happen to them?

Update: Ok, leaving this now as I've exhausted all avenues and its obvious the phone is not going to play ball. On another RUU flash it failed (and looking at the logs it was at the radio section and mentioned a partition update failure). A subsequent RUU flash was successful, so at least I've got it back to stock (although it doesnt stay booted long enough to even get the initial setup wizard done now). Passing it back to my friend tomorrow and hope he can get a warranty repair. Just a shame I couldn't get it back to the Virgin firmware. Thanks all those that helped anyway, much appreciated.
[Droid X General] eighty1:
This is copied from the Droid2 section and is said to work on the X for those of us that didnt move SU b4 updating to 2.2 or those that lost root for whatever reason.

Cool How to root the Droid 2

All credit goes to Sebastian Krahmer at http://c-skills.blogspot.com/. Please see fit to donate via Paypal to 7-4-3-C@web.de

***NOTE: Proceed at your own risk. I and the providers of this code are not responsible for anything you do to your phone!***

Setup:

- Install adb (here) and Motorola drivers for windows(32-bit or 64-bit)

- Download attached archive

- Extract to a directory, I used c:\Droid2Root

- Make sure you have USB degugging enabled

- Change connection to PC Mode

Process:

- Open command prompt

- cd c:/wherever-your-sdk-tools-folder-is

- adb devices (to verify the connection)

- cd c:/Droid2Root

- adb push Superuser.apk /sdcard/Superuser.apk

- adb push su /sdcard/su

- adb push busybox /sdcard/busybox

- adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin

- adb shell

- cd data/local/tmp

- chmod 0755 rageagainstthecage-arm5.bin

- ./rageagainstthecage-arm5.bin

- let the process run until it 'kicks' you out (may take a minute or two)

- cd c:/wherever-your-sdk-tools-folder-is

- adb devices (to verify the connection)

- adb shell (you should now have a # prompt, if not return to ./rage step above)

- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system

- cp /sdcard/Superuser.apk /system/app/Superuser.apk

- cp /sdcard/su /system/bin/su

- cp /sdcard/busybox /system/bin/busybox

- chmod 4755 /system/bin/su

- chmod 4755 /system/bin/busybox

- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system

- exit

- exit

I'm sure there are certain steps that could be streamlined or eliminated, so please feel free to make a suggestion and I'll edit the post.

Additional thanks to @rainabba and AllDroid.org for their excellent Droid X rooting tutorial, which assisted me greatly in this process.

Attached Files

File Type: rar	Droid2Root.rar (954.1 KB, 733 views)

Last edited by karnovaran; Yesterday at 01:58 PM.. Reason: Clarity

Reply With Quote
[Droid X General] h0mewreck3r:
Hello all...

This worked on my DX that I upgraded to 2.2 just fine. The root pw isn't given anywhere in the instructions as it is in the 2.1 manual root steps.

Any thoughts on the root pw so that I can SSH to the device after rooting?
[Droid X General] sheba611:
This method worked for me after thru much trial and error I was able to update to Froyo only to discover I lost root. Did not want to roll back to 2.1 and start over. Thanks so much to everyone who came up with root process and to those who discovered it worked on the DX.

:)
[Droid X General] mavermc:
I tried intstalling the 64bit drivers (then rebooted) then hooked it up in PC mode and can't seem to get it to show up in the list of attached devices.
[Droid X General] mavermc:
Tried uninstalling and reinstalling everything, the one click roots say it can't find my droid X and going through your instructions adb can't find my device ether. I kinda been having a problem with doubletwist where it doesn't recognize my device properly, could that be related?
[Droid X General] Tapple:
I don't know why, but after typing ./rageagainstthecage-arm5.bin it showed the text talking about donations, etc went right back to the $ prompt, and never booted me out of shell. I waited 15 minutes at the $ prompt before Ctrl-break'ing out of shell and trying to relogin. noticed adb is repsonding sluggish. Maybe it's still working? Anyone else having this problem?

Edit: I retried the ./rageagainstthecage-arm5.bin command after rebooting the phone and it worked this time. And I'm rooted! Wireless Tether for Root app works perfectly!
[Droid X General] mavermc:
Also I notice when I say PC mode the little debugger icon then doesn't show up like it does in USB mode or charge mode. could this be why the device isn't showing up?
[Droid X General] mavermc:
Ok so I manage to get everything good up until the point where I should be looking for a # instead of a $ for terminal. I've done the rage and waited till it kicked me out and went back in and got the same result.

The way that I got through my problems is I set the droid x to USB charge only mode (PC mode there was no debugging and every time I plugged it in, it wouldn't take the ADB driver it wanted a MB810 or something driver)

I know I set the permissions right, and it does run (shows up a little message about donating and in a min or so kicks me out, anything else I can try?

Thanks for the help.