yashsingh1/xdaforums huggingface dataset:
[myTouch 3G Slide Android Development] TrueBlue_Drew:
Sd card change is helping to get root

HebrewToYou,

I am not sure why you wont admit that this sd card change is helping people get root. It seems that no matter how many people post that it has helped them you just post how it is a placebo effect and there is no way it could be the SD card cause you have rooted 2 slides with 2 different cards and so that means you are right and they are wrong. Obviously it is helping some people but not everyone. I understand that it probably doesnt matter what name brand or size or class of card you use, but maybe some cards are glitchy or something like that. I do remember the EVO having some SD card issues re: the camera or something like that but I have a friend wit a EVO and he hasnt had any probs at all. I am sure he got the same card that was put in all evo's but only some of them seemed to be flawed and they are all the same brand, class and size.

Now dont get me wrong....I am not saying that for sure it is the sd card that is causing the problem because the process of gaining root isnt the easiest one, but I wouldnt rule the SD card out if I was having a problem gaining root. Luckily I didnt have a problem with the 3 slides I have rooted so far but that doesnt mean that I couldnt run into problems with other ones in the future.

Ok enough ranting out of me for now. HebrewToYou : you seem like a very smart guy and I know you have contributed to many things and helped many people on this forum. Please just try and keep a open mind to what seems to be working for some people and their phones instead of just shooting down what is obviously helping some gain root.
[myTouch 3G Slide Android Development] TrueBlue_Drew:
Follow the guide and watch the video and you can browse the forums for any problems you run into. If you do the process correctly then you should gain root access. If you have any questions feel free to PM me and I will help you out anyway I can.
[myTouch 3G Slide Android Development] HebrewToYou:
TrueBlue_Drew, I've explained the rationale for my skepticism of this "solution" before, but just to make it crystal clear...

I think it would *amazing* if achieving root was as simple as swapping out your sdcard. That would make it a lot faster and a ton easier for most people, especially if it could be done by popping in a simple 1 GB class 2 card which cost as much as a Big Mac meal at McDonalds.

The problem, however, is that for this to actually be a proven solution there would need to be some way to separate out the 'probability' factor from the hardware. And there is absolutely no conceivable way to do this.

See, a significant number of people have achieved root without swapping their sdcard and they have done so with a wide variety of different sdcard hardware inside their device, from the high-end (my class 10 16 GB) to the low end (class 2 1 GB) and all points in between. And all these people achieved root after a wide variety of attempts -- as I said above, it took me 7 tries on one Slide and 3 on another. Some people had to try it as many as 20 times and others even more than that!

So, accepting these facts, to suggest that swapping out your sdcard was the reason you achieved root -- and not simply just happenstance by getting lucky as everyone else who has achieved root has done -- isn't a verifiable claim. It is equally as likely that the swap-out of your sdcard coincided with the probability of the *very next time* you attempt to achieve root being successful.

Hence why I compare this "solution" to betting on roulette. To be perfectly blunt, the people at casinos who stare at the table history to try and predict a pick are morons. Just because black hit 25 times in a row does *not* mean that there is a high likelihood of red hitting next. The probability does not change -- it is still, and always will be, ~50/50 (a bit less, in reality, factoring in 0 and 00).

I hope that clarifies the matter.
[myTouch 3G Slide Android Development] heybobitsme:
2 cents

I just rooted with Ubuntu Lucid using original sd following directions in op with the exception of the loop. I did that manully (adb devices then arrow up and enter a bunch of times) and device offline popped up right away after rebooting to stock recovery (although I passed it a couple times because I was hitting it too fast LOL). All I'm saying is, it worked for me.

Just a thought, even though it shouldn't matter, I wonder if color of the phone has anything to do with it. Mine's black. I remember in the G1 threads somewhere there was a difference with the color and how easy things were. And not the 32A/32B thing
[myTouch 3G Slide Android Development] marty22877:
what if t-mobile got different shipments of sd cards, some were good, some were bad, ever think of that?
[myTouch 3G Slide Android Development] HebrewToYou:
The same argument could be made about ANY sdcard, Marty, not just the ones that shipped with the device. You can't base a "solution" on random manufacturing defects... There are people who have swapped out their sdcards and are yet still unable to achieve root. The entire process is based on lucky circumstances.
[myTouch 3G Slide Android Development] DoriftoShoes:
I have to say I agree with Hebrew. I don't think the sd card has anything to do with it. I think the more important piece is the timing of aborting the loop...and luck :)
[myTouch 3G Slide Android Development] i0nicx:
define bad, because if the card was bad, then there would be way more issues with them. like data loss and corruption or just plain not working.

and to add the sdcard thing is bullshat, i've tried 6 different sdcards of varying sizes and class. i'm going to try another card for ****s and giggles just because it's available to me. it's just whether or not adb can grab the hole in the boot/loop thingamajig.

and luck.
[myTouch 3G Slide Android Development] johnd8982:
step 17 after rebooting adb device list is blank
[myTouch 3G Slide Android Development] TrueBlue_Drew:
Aborting the loop? I didn't abort the loop until after my device was showing up on it. I definitly agree that there are some things that need the right timing to work. Like pushing the update/clockwork file. And for sure some luck involved also.
[myTouch 3G Slide Android Development] marty22877:
the loop has nothing to do with it, i let mine run for a solid 30 seconds and it didnt disconnect.
[myTouch 3G Slide Android Development] DoriftoShoes:
I know in my situation that I got the exact same results (shows offline once then disappears) over 30 times...The first time I tried killing the loop at the moment it shows offline it worked...

Either way, I'm happy I got root now :)
[myTouch 3G Slide Android Development] TrueBlue_Drew:
ya me too. Not sure why aborting the loop was even brought up as a timing issue. I dont think the timing of aborting has anything to do with it. My suggestion would be to not let the loop run for 2 long before you hit the recovery command in order to try and detect your phone. I took off my battery cover and if it didnt detect when I hit recovery I just popped out the battery and held down the volume button to get back to the boot screen and try it again.
[myTouch 3G Slide Android Development] DoriftoShoes:
Why would it matter how long you let the loop run before going into recovery?

If there is no issue with timing when you kill the loop I don't see why it would matter how long it runs before you go into recovery...In reality you could just let the loop keep running and reboot your phone over and over...
[myTouch 3G Slide Android Development] TrueBlue_Drew:
Glad you got it to work like that. In your situation it sounds like you did the perfect thing and I stand corrected. I guess in some instances the abort timing can be important. If it got your phone rooted then it is worth a try for people that are having similar problems.
[myTouch 3G Slide Android Development] DoriftoShoes:
I'll be the first to admit that at this point I have no idea what determines when it does or doesn't work, just relaying my experiences :D
[myTouch 3G Slide Android Development] TrueBlue_Drew:
I am not sure if it matters or not....that is why I only suggested it. On the slides I have rooted I just started the loop and then within about 10 sec I hit recovery.
[myTouch 3G Slide Android Development] i0nicx:
so i currently have my phone stuck in offline mode(i think). i'm sitting staring at the recovery screen(on the phone).

i disconnected the usb cable and reconnected it. and dont see a change. this is the text below from the terminal(using ubuntu).

for the love of god and all that is holy, if someone can give me an idea where i am it would be great.

i0nicx@i0nicx-laptop:~/androidsdk/tools$ ./adb devices

List of devices attached

????????????	no permissions

i0nicx@i0nicx-laptop:~/androidsdk/tools$ ./adb devices

List of devices attached

????????????	no permissions

i0nicx@i0nicx-laptop:~/androidsdk/tools$ ./adb push ota.zip /sdcard/update.zip

error: insufficient permissions for device

i0nicx@i0nicx-laptop:~/androidsdk/tools$ ./adb push ota.zip /sdcard/update.zip

error: insufficient permissions for device

i0nicx@i0nicx-laptop:~/androidsdk/tools$ ./adb devices

List of devices attached

????????????	no permissions

edit: the push was done after disconnecting and reconnecting the cable following the steps on the guide on the first page.
[myTouch 3G Slide Android Development] TrueBlue_Drew:
Haha....you edited before I could ask if you unplugged and plugged back in. Your device must read that it is in recovery not offline.
[myTouch 3G Slide Android Development] i0nicx:
regardless of where i am(offline, online with phone booted, and now recovery) when i run 'adb devices' i get '???????????? no permissions'

is adb being a bastard?
[myTouch 3G Slide Android Development] DoriftoShoes:
Are you on linux?

I had that before but it worked once I moved to a Windows machine...

I think it has something to do with the latest version of the Android SDK judging by some articles I've read about that error in other situations...
[myTouch 3G Slide Android Development] DoriftoShoes:
I just looked up and saw your post and see you are on Linux...Is there a Windows machien you can try it from?
[myTouch 3G Slide Android Development] i0nicx:
running ubuntu right now, i can switch back to xp or win7, but i feel like lightning will not strike twice
[myTouch 3G Slide Android Development] DoriftoShoes:
I'll play around with my ubuntu machine and see if I can figure out the issue...
[myTouch 3G Slide Android Development] TrueBlue_Drew:
so when you are in the loop process and your phone shows offline hit control+C to stop your loop from running. Then unplug and plug your phone back in. It should now show up in recovery. Is that what is happening?
[myTouch 3G Slide Android Development] DoriftoShoes:
Try this:

Run adb kill-server to stop the adb daemon then run 'sudo adb devices'

I was able to get my ubuntu machien to show my phone properly under adb devices this way
[myTouch 3G Slide Android Development] DoriftoShoes:
It's an ubuntu issue with ADB...you need to start the ADB daemon as root.

http://groups.google.com/group/android-discuss/browse_thread/thread/f85a795644e65b59?pli=1
[myTouch 3G Slide Android Development] i0nicx:
yea, i'm a jackass i just realized that as your post went up. it's always the little details.

sorry about that guys
[myTouch 3G Slide Android Development] TrueBlue_Drew:
Great find DoriftoShoes....I dont know much about Ubuntu.
[myTouch 3G Slide Android Development] DoriftoShoes:
Too bad I was too stupid/tired to find that last night when I was rooting my phone...hahahaha

I ended up throwing the SDK on my work laptop (WinXP) and doing it from there...
[myTouch 3G Slide Android Development] i0nicx:
so um, i have root after switching to my buddy's 16gb class 2 sdcard. throw me on that list of sdcard people if you want.

**** makes no sense.
[myTouch 3G Slide Android Development] fermunky:
This is how I started feeling once I thought for sure that it was my sdcard. But after formatting, I cannot reproduce it, it's found in recovery with both cards...

So again
[myTouch 3G Slide Android Development] nomadrider123:
yep no sense at all... been working at it several hours for several days. Tried everything in these 600+ posts all the programs, drivers etc 3 sd cards 3 computers my phone is a ***** and hates me. :mad:
[myTouch 3G Slide Android Development] Phantisy:
Can anyone confirm their phone is in disk drive mode under device manager when it cant be found anymore with adb devices? I believe windows is seeing the phone in recovery mode as a disk drive and this is causing the issue.

Anyone who roots their phone do they see it as a disk drive in windows when they can see it in recovery mode?

I believe this has something to do with the problems. Mine can be seen in offline mode for a few seconds and it is listed under android devices but as soon as its put into disk drive mode its gone.

Can anyone with a rooted phone test this out?
[myTouch 3G Slide Android Development] sultan.of.swing:
Phone should not be listed in disk drive mode. The phone should have its own category called "Android device"

Here is what it should be listed as in windows XP
[myTouch 3G Slide Android Development] Phantisy:
I have never it listed at that under device manager. Can you tell me what driver it is using? I have seen it listed under android phone but only as the mytouch 35 slide.
[myTouch 3G Slide Android Development] sultan.of.swing:
Using the driver supplied with PDAnet.

During driver installation it said "HTC" or something like that. I updated the driver by pointing it to the PDAnet folder.

Reboot your pc. Then reconnect the phone and get it into fastboot and see what the driver says. If it says android device and the mytouch slide or whatever then update the driver manually and point it to the PDAnet folder where you installed PDAnet.
[myTouch 3G Slide Android Development] Phantisy:
mine shows as android adb device under android phone right now. Cant change drivers says no better ones were found.
[myTouch 3G Slide Android Development] sultan.of.swing:
You should be fine then. That's just what mine says and its what it said when I rooted it.

Just keep trying to catch it in the loop. Try starting the loop and let the loop run for 5 seconds on the screen and then start recovery and the instant you see the device ctrl-c. When I did mine it saw thr device in recovery already instead of offline so I didn't have to disconnect and reconnect to get into recovery
[myTouch 3G Slide Android Development] Phantisy:
I been trying this for 2 days. Mine always loads as a disk drive when I put the phone into boot mode or recovery. Its something with win****....
[myTouch 3G Slide Android Development] sultan.of.swing:
Double check and make sure its connected via "sync" only and make sure usb debugging mode is selected. Sometimes it will change without you knowing
[myTouch 3G Slide Android Development] Phantisy:
That is what is selected.
[myTouch 3G Slide Android Development] boosted22:
cannot run loop

Ok need some help with this one. Not an expert but rooted my g1 and my my touch 3g (goldcard method) with no problems. I have sdk installed and device does show up when i rund adb devices but the problem I have is I cannot get the loop to run.

error is

loop is not recognized as an internal or external command, operable program or batch file.

EDIT: Got it to loop. Recognized offline the first time with sd card that shipped with phone. Was able to gain root thanks to everyone that worked on this.
[myTouch 3G Slide Android Development] gofizzle:
I just wanted to thank Eugene and the crew for their efforts so the Slide could be rooted. After much stress and nashing off teeth I finally saw the # sign and about crapped myself.

I have seen many post and processes that have worked for fellow members. I just wanted to share what got me past the device detection process.

A big thanks to Phylum, post # 558, who shares a few options to try. I followed his post to get to Recovery and then picked up the root instructions from there.

What worked for me was turning on my phone and then plugging into my laptop.

Then launched the command prompt and typed "adb reboot recovery". Next thing I know for the first time I have an offline device.

From there I picked up at step 7 from the "Root Your Device" instructions, followed along and finally obtained root.

I had the Samsung 8GB card in that comes with the phone and had tried a couple others, 8GB class 4, and class 6, and no card at all.

If you are stuck and about to give up, go to post #558 and give it a try, at least to get you to recovery.
[myTouch 3G Slide Android Development] akapunchy:
phantisy, mine also says adb device.

2 days ago it my cpu was recognising it as a mytouch slide, but today it keeps coming up as a adb device. don't know why... tried uninstalling and reinstalling drivers
[myTouch 3G Slide Android Development] coltfoet5:
I think I bricked....

I went through root successfully got it all done and when I went to flash a rom I cleared all the data and cache like I always did on my G1.

Now I can't adb to recognize the device and I can't get into clockwork recovery because everytime it says E:failed to verify while-file signature... E:signature verification failed Installation aborted.

Where can I go from here? Is there anyway to get ADB to recongize it again. I'm assuming when I cleared the data it turned off usb debugging which is making unable to recognize the device so I think i just made a brick.

Anyone have ideas?
[myTouch 3G Slide Android Development] Henchmin:
ive tried 5 different SD cards...

i want to cut myself
[myTouch 3G Slide Android Development] Henchmin:
I dunno if the keyboard works in recovery, but if it does try typing this in recovery mode.

"echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file"

it should mount your SD Card to your computer
[myTouch 3G Slide Android Development] coltfoet5:
There is no command prompt to type that in. I can't get into clockwork recovery.
[myTouch 3G Slide Android Development] Henchmin:
if your device is rooted then you can flash it, right?

load an image to your microSD using a card reader or something. that should work

edit: ****, if you can't get into clockwork recover...then I dunno
[myTouch 3G Slide Android Development] coltfoet5:
yeah pretty big problem not being able to get into clockwork recovery. I need a way to get into it.
[myTouch 3G Slide Android Development] h.nocturna:
Since I've been trying for ever and following every idea I could see, I thought I might throw another idea out there for anyone that's been trying to get this to work.

First, follow his advice.

Now boot up USBDeview once again and make it sort by description. Then select everything that has "T-Mobile myTouch 3G Slide" in it and click "uninstall." Then select everything that has "ADB" in it and again, uninstall it.

Once you're the bootloader, use your computer to access the device manager and see if "Android 1.0" has popped up. If it has, go ahead and install the revision 3 drivers from the Google SDK. I don't know if it matters, but I selected the "Android Composite ADB Interface" drivers.

Once you're in recovery, use the device manager and see if "ADB" has popped up. If it has, go ahead and install the revision 3 drivers from the Google SDK. I don't know if it matters, but I selected the "Android Composite ADB Interface" drivers. At this point it was detected in recovery and I just continued with the guide posted in the OP and everything worked, but if it's detected as offline, then disconnect/reconnect your USB cable and it should detect in recovery. I did this *exact* method with 2 phones and both worked on the first attempt. There was no timing the "end the loop command," it just stuck and it could've looped for eternity and the devices would still show.

I tried several methods over the last few days and this is what I did to get mine to work. I'm not guaranteeing anything, just throwing out another suggestion to all the desperate people out there. =] Good luck and happy rooting.
[myTouch 3G Slide Android Development] eddiein2021:
Thx a ton bro

Hey eugene thx for putting this up it wasn't the easiest job ever but I got my slide finally rooted. At the step with the clock work not loading up and everything and trying to time it just right. i was so pissed off after a numerous amount of failed attempts, oh and also this is the first time I've rooted something so thx for teaching me about this. It was a trip that I hopefully don't want to do again but thx to you and king for the vid. as a side note i think he should try to make the video clearer possibly an on-screen recorder? Oh and also can i delete that .bin file in the super user? Its called /system/bin/sh as root?

thx again

Eddie
[myTouch 3G Slide Android Development] dragon4000:
Ok, after tirelessly trying for more than 1,000 times:mad::mad::mad::mad:, i finally have root:D:D. After reading through all the 69 pages, I finally did it. This is what I did and it worked for me:

Boot into boot loader

Open command prompt

cd c:\android\tools

from phone, select recovery and press power

in command prompt, typed adb devices

I got this message:

c:\Android\tools>adb devices

List of devices attached

HT05NPS04355 offline

Then, unplugged usb and plugged back in

in command prompt, typed adb devices

I got this message:

c:\Android\tools>adb devices

List of devices attached

HT05NPS04355 recovery

then followed the tutorial from step 8 to 20.

Now I'm on my way to flash a rom!! Hopefully this help you guys as it did for me. Good Luck!!:D:D
[myTouch 3G Slide Android Development] eugene373:
This is how it's suppose to be Done!! lmao :D

At least you got Root :eek:
[myTouch 3G Slide Android Development] coltfoet5:
Does anybody know if I can flash an image from the regular recovery as an update.zip so I can boot the phone back up?
[myTouch 3G Slide Android Development] fermunky:
Some are still getting things mixed up as far as what settings this that and the other. First, to get the drivers to load "normally" (assuming all other drivers have been removed) is to make sure the phone Connect to PC setting is either on Charge Only or Sync. If the phone is on Drive Mode, when you connect it to the first time, Windows will install it only as a removable drive. On the other settings, it should install the device as either a Android something or other, MyTouch Slide, HTC device etc (this all just depends on what driver was installed). EITHER driver should work.

Once the drivers are installed, reboot your machine for good measure. Once in Windows, and the phone booted normally, "adb devices" should find your device no problem. Now try going into recovery mode following the root steps. From here, the hit or miss begins.
[myTouch 3G Slide Android Development] mdajunkie:
After 3 days of unsucessful attempts i finally got it rooted.

I tried every method out there and i can confirm all are hit or miss.

Good luck to everyone else.
[myTouch 3G Slide Android Development] Goonmode:
Not exactly true........i had mine on disk drive at all times and mine is rooted
[myTouch 3G Slide Android Development] fermunky:
Correct, once your drivers are installed, then it doesn't matter. But I can guarantee you that, if all the drivers are removed, and it connects in drive mode, it will not install the drivers.
[myTouch 3G Slide Android Development] Goonmode:
Naw I had my device on disk drive the WHOLE time....including the debacle i went through with the drivers...

I install HTC sync..of course that didnt work so I did PDA drivers and BAM.....all good.....while in DD mode.
[myTouch 3G Slide Android Development] ballinsane:
ok! im a complete n00b and have never rooted a phone before! can someone please break it down for me step by step. from things that need to be downloaded for the root process? i really wanna root the slide but cant seem to get pass the Loop part!
[myTouch 3G Slide Android Development] marty22877:
read post 1
[myTouch 3G Slide Android Development] ballinsane:
post one didnt help..seems like there is other things i need to do..like i need to have prior knowledge of rooting.