Solve this puzzle... - myTouch 4G Q&A, Help & Troubleshooting

Alright... I am having a bit of an issue... looking for interesting solutions.
Have a replacement MT4G with stock 2.3.4. I am trying to downgrade to Froyo so I can root it.
Unfortunately, my usb cable must not be working. It starts charging when I plug it into the PC, but Windows won't recognize it (I have tried different ports, and double checked drivers...). When I had my first Mt4G, if I needed to use ADB, I used a market app that allowed me to connect to ADB using Wifi. It has some limitations, but it is a good substitute if needed.
But those Wireless ADB apps only work with Root (at least the ones I found), and well, obviously that was the goal all along... so I am thinking temporary root... but didn't think there was a temp root...
Question: does anyone know of a way to access ADB wirelessly without root, or know of a way to gain temp root via terminal emulator so I could then connect via the wifi ADB app and be able to complete downgrade/permroot?.... or are there any suggestions for what I could do to get the USB working?.....anything would be appreciated.
I can use the SD card with my laptop.. so downloading/getting files on the phone's SD card is not a problem... just access to ADB is a problem.
PS: Since the USB cable still functions as a charger (if that is actually the problem), I am trying to avoid spend $40 for the replacement.... since I would really only need it once.

Did you try TrueBlue_Drew thread about adb/fastboot set up ?
Sent from my HTC Glacier using XDA App

If you need to gain root access, there are other methods than the regular ADB .
Refer this post to find way that suits you.
http://forum.xda-developers.com/showthread.php?t=834225
If you need Wireless ADB, refer to this post.

Thank you both.... question however...
2kwic25: I checked the trueblue thread, and this seems to be a method for rooting which does not require the full sdk. However, it still uses the usb cable to connect to the phone. I am trying to gain temp root either through the emulator alone, or using adb (which is already installed on my pc) via wifi, but without having any su or root permissions as I don't have them and that is what I am trying to achieve ultimately.
febycb I read/scanned the link on rooting.... I went through to the end of it, and it doesn't seem to apply to the gingerbread 2.3.4 stock. This is what is on my phone now. I have a brand new phone, everything is factory locked, no root, s=on, etc.. The one post I found originally which seems to be the route most are using is to gain temproot, then downgrade to Froyo.... THEN attempt rooting to get a real permroot with s=off. So, in order to downgrade, I need to connect via USB, and use adb initially. But my USB does not work, so I am left with trying to connect via wifi. However, the thread on using adb over wifi seems to say that while you may not need to use su when running the necessary commands in the emulator, your device must still be rooted. So I cannot seem to figure out how to do this trying to use adb over wifi to get root, yet you need root to use adb over wifi.
Lastly, while I did note that your first link says only updated devices, I believe they are talking about the update to Froyo.
I guess this is the one main question I have:
Does anyone know -- or has anyone heard or read about -- a method to get temporary root on a MT4G with stock Gingerbread 2.3.4 using only the emulator???
Thanks... I am going crazy without root, and as said, I really want to avoid (as I am on a tight budget) purchasing another usb cable for $40, just to get a temp root.

I will try to sort out the issue as simple as i can
1. There is no method right now to root the 2.3.4 upgrade (even temproot).
2. To enjoy root access, you need to downgrade to Froyo (stock 2.2.1)
3. Do Permroot and then upgrade to GingerBread 2.3.4 or 2.3.5
4. Every post related to rooting is based on the stock Froyo Rom.
To downgrade, follow this post. Select the option best suited to you.
Also don't spent $40 for an OEM data cable. A replacement cable is available at price tag as low as $0.99
Just go to ebay & search for "micro usb cable". Just go through this link.

Have you installed the "HTC_drivers" file that comes on the root of the sdcard?
Possibly the reason why windows doesn't see it.
Or Make sure "USB Debugging" is enabled..
Not saying you haven't done either. Just putting it out there.
Sent from my HTC Glacier using xda premium

Thanks mahato... But yes. I have loaded the htc drivers, htc sync, pdanet.... All of them. Plus, I know all about usb debugging and it is on.
I have had it with this problem. The other thing that drives me crazy about my issue (which is why my phone was replaced in the first place, is that wifi calling keeps dropping), is that in my comprehensive research, I read one person's post that said that they confirmed that their 911 address needed to be filled out. Will I have done this and have done it through tmo. But I don't know if this was the problem, because I STILL KEEP GETTING THE DIALOG BOX which instructs me to complete my 911 address.
One more thing, since I need a cable to root this (which I know I can order cheaply), I might try to get a free usb cable from tmo...
But, before, I acquiesce to these problems and accept a new phone and just deal with it...
Can someone tell me how to confirm whether I have the ”bad chip” or ” bad screen”? I put a new screen protector on the new phone, and I thought that might be it, but I don't think so. My usual wall paper is the beautiful widgets living wallpaper which shows the blowing grass, etc.
However, when I look at my phone at an angle, the screen turns lighter, with practically zero contrast. I had read somewhere that this is a symptom, although I may be paranoid considering everything....
So does anyone know how to confirm a ” bad screen” or a ”bad chip” (I didn't even know there was a bad chip). Is there something I can check in the bootloader screen or something like that to confirm a component part number?
Sent from my HTC Glacier using xda premium

Reposted to new thread.

Ok, there are a lot of wrong statements in this thread and I don't have any time to cover them all.
Temp-rooting 2.3.4 requires running fre3vo. That's the only currently existing method.
fre3vo runs by exploiting msm_rotator.
I believe it's not documented whether the exploit absolutely requires link through ADB.
So, you could just try and see for yourself. In the worst case you'll discover that the temp root shell is given only to ADB and not to emulator.

Related

**HELP**Downgrading MyTouch/Magic to 1.5 to root

I got my mytouch(the older one, the one without the headphone jack). I have been trying to root it ever since then. but I can not do it at all.
1. I can not access my phone through adb NO MATTER WHAT, I have tried this in xp,7 and ubuntu. I always get no device found, but in fastboot mode, it is able to pick it up!!! Is there something that I need to enable on the phone? Or should the phone be in any special mode?
2. I have tried to downgrade to 1.5 using the sapimg, but it did not work at all. I would not mind using the goldcard method even though I have been advised not to do so. Even If I chose to use the gold card method, I could not do so since my adb method is not working properly!!!
Also my mytouch is unlocked, if that makes any difference.
vz2487 said:
I got my mytouch(the older one, the one without the headphone jack). I have been trying to root it ever since then. but I can not do it at all.
1. I can not access my phone through adb NO MATTER WHAT, I have tried this in xp,7 and ubuntu. I always get no device found, but in fastboot mode, it is able to pick it up!!! Is there something that I need to enable on the phone? Or should the phone be in any special mode?
2. I have tried to downgrade to 1.5 using the sapimg, but it did not work at all. I would not mind using the goldcard method even though I have been advised not to do so. Even If I chose to use the gold card method, I could not do so since my adb method is not working properly!!!
Also my mytouch is unlocked, if that makes any difference.
Click to expand...
Click to collapse
do you have debugging mode on.. on the phone go to setting>application>development..turn on debugging mode... and do u have androidsdk set up??
p.s. go check out unlockr.com for a how to root they have videos
ADB works
Thanks, ADB works. Now I just need to get the phone rooted. I had no idea that it had to be enabled!!!
As for unlocker.com it does not work, its a spam site. I am going to try to root it again.
vz2487 said:
Thanks, ADB works. Now I just need to get the phone rooted. I had no idea that it had to be enabled!!!
As for unlocker.com it does not work, its a spam site. I am going to try to root it again.
Click to expand...
Click to collapse
What is the error you are getting while trying to root using sampping.nbh?
I rooted my phone using unlockr.com, so unless you can prove things, dont start making statements about them.
vz2487 said:
I got my mytouch(the older one, the one without the headphone jack). I have been trying to root it ever since then. but I can not do it at all.
1. I can not access my phone through adb NO MATTER WHAT, I have tried this in xp,7 and ubuntu. I always get no device found, but in fastboot mode, it is able to pick it up!!! Is there something that I need to enable on the phone? Or should the phone be in any special mode?
2. I have tried to downgrade to 1.5 using the sapimg, but it did not work at all. I would not mind using the goldcard method even though I have been advised not to do so. Even If I chose to use the gold card method, I could not do so since my adb method is not working properly!!!
Also my mytouch is unlocked, if that makes any difference.
Click to expand...
Click to collapse
What is this to do with development?>??
FFS everyone of you guys that has never posted before just starts a new thread because you cannot figure out what your doing
there are forums for you but they are not here!
ayush20m said:
What is the error you are getting while trying to root using sampping.nbh?
I rooted my phone using unlockr.com, so unless you can prove things, dont start making statements about them.
Click to expand...
Click to collapse
These are the errors I am getting:
"model ID incorrect
update Fail!"
Also are you talking about theunlockr.com/? If you are then its a good site, has nice videos. Thats where I did most of my research.
vz2487 said:
Thanks, ADB works. Now I just need to get the phone rooted. I had no idea that it had to be enabled!!!
As for unlocker.com it does not work, its a spam site. I am going to try to root it again.
Click to expand...
Click to collapse
its not theunlocker.com its theunlockr.com <<< no "e" before the "r"
o yea sorry i didnt add the "the" before
vz2487 said:
These are the errors I am getting:
"model ID incorrect
update Fail!"
Also are you talking about theunlockr.com/? If you are then its a good site, has nice videos. Thats where I did most of my research.
Click to expand...
Click to collapse
This means your phone came pre installed with 1.6, you will have to use goldcard. There is no other way to root your phone.
Provide your phone information through fastboot. Turn off your phone, do back+power, then write your SPL (e.g 1.33.0004), radio (e.g. 2.22.19.26I), stuff like that is all on there. Then you can turn off your phone by holding down power again

[Q] Unable to complete root process

Hello there fellow Glacier owners.
Let me start off by saying I have rooted 2 Glaciers very recently, and I am very familiar with the process. One of them was swapped at the store because I had one of the Taiwanese screens, and it was driving me nuts. I have been trying to root the new one.
I've gone through the gfree, adb, and Visionary+ methods already, and now an issue has cropped up.
Now, when I run Visionary, pop open the terminal, and type 'su' I get an 'unknown user root' error.
When I try to use the adb/gfree method and run 'rage', I now get a 'rage: applet not found' error.
During my previous attempt, I did not get this error. I have tried a reset to factory through stock hboot, I have tried loading the 2.2.1 PD15IMG.zip, through stock hboot (didn't help, wasn't expecting it to). I've even tried switching out and formatting mSD cards on the off chance it might help.
If anyone has any advice or help they can offer me, I would greatly appreciate it.
Thanks
Any way you can post a video of your step by step? I've always used grankin's guide and I've never had an issue, not once, on 6 HTC Glaciers.
Thus far, I've only seen a few reasons why people can't root their phone:
- They aren't on 2.2.1
- They didn't put files in the correct location/follow directions to the T
I don't think I've ever seen a legit, "your device is defective" post, but it's been suggested.
I use visionaryplus.r14.apk each time and my employee has rooted a handful of HTC Glaciers using the same.
I think a video would really help expose any possible oversights. It's either your steps or the device is just "bad" and I'm thinking video footage would help reveal which it is.
Here is a link to my video using the Visionary+ method. I can upload a video for the adb if you want as well.
www.youtube.com/watch?v=qb3HIvXiF74
Replace DOT with .
I should also note that I was able to run the 'su' command at one point successfully, but this is no longer the case.
Awesome, great vid and thanks for that. Can you get a screen shot (or pic) of your About Phone > Software Information?
Thanks! Here is the requested pic...
I should note that this phone came with 2.2.1, where the other two I have rooted did not.
Awesome, thanks for the quick pic. I've had six Glaciers, two of which came with 2.2.1 pre-installed, the rest came with 2.2 and then 2.2.1 came down once I checked-in. So that alone (2.2.1 pre-installed) shouldn't be an issue.
The difficult part is, there have been multiple "processes" attempted on this device, so I can't attest to the state of the device/ROM. Is this attempt with Visionary coming from a clean install/factory reset? I'd sort of like to "take it back to basics" and have a factory reset device THEN try ONLY the Visionary method.
I saw someone mention that a dev though there could be a hardware issue causing this (I can't remember which thread or which dev mentioned it), but it was only speculative.
It seems pretty clear you know what you're doing and you're quick AND we're not even to the .sh portion (where a lot of people end up with /root/root directories).
Keep me posted...
If you could, please supply me with some detailed factory reset instructions.
I want to make sure we are troubleshooting this appropriately, and I may not be wiping it correctly.
Please let me know.
Thanks.
It should just be Menu > Settings > SD & phone storage > Factory data reset...
Ok, it's running through now.
What would my next step be?
EDIT: Wipe finished. I installed Visionary, ran Temproot, still get the 'su: unknown user root' error.
May be heading to my local T-Mobile to replace the device.
K, so once it's finished you'll get to the TMO setup wizard where you enter your Google account info, etc. Once you get through that and get to the home screen, stop and don't do anything else. That's our home base.
Let me know once you get to the home screen for the first time after factory reset and we'll go from there...
I appreciate your patience and willingness to go through everything in baby steps.
Youch, k, there we go. That's exactly what the next step would've been and it sounds like you're truly not missing anything.
Does anyone else out there have anything to offer? I think you're probably best at cutting your losses and just getting another device. It really should be a very simple process, as you've seen before.
Keep us posted on the new device!
Woops, went a little too far then. I'll re-wipe.
What's the next step?
EDIT: Didn't do this, nevermind.
Ok, I got the new phone. Attempted to root through Visionary, everything looked good, but then I did not have root. Here is what I did...
From factory, out of the box (confirmed 2.2.1), ran Visionary - Temproot.
In terminal, 'su' works properly.
Ran root.sh
Appeared to work, rebooted the phone manually, S was still on.
Ran Visionary Temproot.
Ran Visionary Permroot.
S is still on.
Are there other steps I should take? Or did I perhaps do something wrong.
Please let me know.
Ok, unless there's some silly oversight, I think we might have a different issue here. Anything 'special' about these newer HTC Glaciers? All the specs you posted look identical the devices I've had from November, December, etc.
I hope there's no issue with me posting a link to Visionary.
Visionary R14:
http://deancasey.net/android/apps/visionaryplus.r14.apk
Just for giggles, can you try that APK? I know you said you have the same version, but there's obviously some difference between what you have (hardware, software, etc.) Other than that, it's either process or device. You seem pretty knowledgeable and it's not some silly mistake like not finding the .sh script.
Has anyone else tried to root using Visionary R14 on a newly-acquired MT4G? I'm just wondering if ANYTHING is different about the newer devices.
Still not working.
Should I try the gfree method? I will also note, that the last 2 I did gave me a real hard time rooting them. I bounced around a bunch of threads/methods before I got it to work, and I really don't recall what I had to do.
Yeah, it's just something that's really weird to me. I've been a "tech," professionally, for nearly 15 years. I worked as a Project Manager for a software company for 7 years, so I was solely responsible for testing our new releases. I also did all the 'lite' work like the database patches, installer scripts, etc.
Working closely with a smart developer, you start to get really good at testing and removing your own opinions from the loop. So there's pretty much always a finite reason why something isn't working as expected.
So that side of me wants to know what the variable is. Six of these devices and I've rooted them all without issue, using that .apk and Grankin's .sh script. So it's like, ok, I know this works. I've seen it not work for people who weren't on 2.2.1, who didn't follow the directions, etc. It looks like we can rule out the user with you so now it's a matter of what is unique about your device(s)?
Try the gfree method and report back, but I'd definitely like to see if anyone smarter than you and I has any input on what could be different about the newer devices you have.
Ok, I got the new phone. Attempted to root through Visionary, everything looked good, but then I did not have root. Here is what I did...
From factory, out of the box (confirmed 2.2.1), ran Visionary - Temproot.
In terminal, 'su' works properly.
Ran root.sh
Appeared to work, rebooted the phone manually, S was still on.
Ran Visionary Temproot.
Ran Visionary Permroot.
S is still on.
Are there other steps I should take? Or did I perhaps do something wrong.
Please let me know.
Click to expand...
Click to collapse
I was under the impression that you had to turn S off before you can perm-root this device. The way I did it is here: http://forum.xda-developers.com/showthread.php?t=858996
I used only Gfree and Visionary (both can be obtained in the link). No separate rage exploit. If I follow you correctly, I don't see where you used gfree after temp-rooting, which is what actually turns S on or off from my understanding. Visionary is what puts the binaries in place and executes the exploit to do so. I only used these two tools and I have S off with perm-root verified. Try it this way:
1. Fresh MT4G, stock bootloader, recovery, etc.
2. Ensure USB debugging is on
3. Install a terminal emulator
4. Install Visionary
5. Temp-root with Visionary
6. Push gfree to your phone as described in the link above using adb
7. Open your terminal and run gfree as described in the link above
8. Reboot
9. Run Visionary again, but this time ensure you check the box to have it mount system R/W after temp-root
10. Temp-root through Visionary
11. With Visionary still open, attempt to perm-root the device; it should reboot
These are the steps that I remember following and it worked perfectly. The key was using gfree to turn S off in order to get it to stick, then going back to Visionary and rooting. I think it is possible to get perm-root with the engineering bootloader and not really turning S off, but I am not %100 sure about the new stock bootloaders and having to turn S off or not. But, this method worked on more than one MT4G on which I tried it. Hope it helps.
The method outlined in Grankin's post gets you S-Off.
totalentropy is getting stuck before we can even get to the next steps. He's just trying to get Temp Root and then get su. You won't have S-Off at this point in the process and you don't need to have it off at this point. You won't get S-Off until you run the root.sh script...
*Crappy iPod Touch camera
total, have you tried the 'Alternative Root Process' outlined in Grankin's post? He wants you to remove the Visionary and Super User apps before proceeding with that method.
kmdub, that didn't work for me.
schlongwoodian, I did try that, and it seemed to be working. After the last rage, it soft reboots to the MyTouch logo, 5 seconds later flashes back to the MyTouch logo, then boots normally. I checked S after that, and it is still on. This is the same behavior that my other two exhibited when I was trying to root them.
Here is some additional info that may be helpful.
For all 3 Glaciers, I could not push su or Superuser.apk to the phone normally. I could only push them right when the phone booted with the USB plugged in, right after the USB debugging mode message appears. Any other time and I get access denied.
When I run gfree, with the -f switch, I get an error with input file, sometime a different error that I cannot remember off the top of my head. On one Glacier, I could run gfree with the -s off switch, which did work. I tried that on this current one, and it did not help.
For all 3 Glaciers, I could not push su or Superuser.apk to the phone normally.
Click to expand...
Click to collapse
Push via? ADB? Why is Superuser.apk being pushed to the phone? That's part of another root process I'm guessing? That's not part of Grankin's root process. Now, the Superuser.apk does get installed (Visionary), but never does Superuser.apk have to be manually copied over.
Those are good points that you mentioned. Can you clarify if you pushed Superuser.apk to your phone earlier? The process should be:
- Factory reset or start with clean device
- Copy visionaryplus.r14.apk to your microSD card (I put mine in a folder named _appz)
- Copy Grankin's 'root' folder to the root of your microSD card
- Run Visionary to gain temp root
- Run Terminal and type su
It's interesting that you're getting the 'unknown user' error right when you type 'su' and you also have manually copied over a Superuser.apk. Can you start the process over again - factory reset - and do nothing once you boot the phone for the first time? Wait and don't copy a thing over, nada. Just wait and post back here. And make sure there truly is nothing on your microSD card - nothing that you've put there that is, not until we can start this over again.
I hope we're onto something...

[Q] root samsung continuum SCH i400

I still can not find anything to work when rooting my phone i used z4 nothin superoneclick and nothin there
Anyone anything? i will donate if there is somthing that works
You can flash the super clean rom, that has root built right in..
if you don't like that idea, try the super one click found around this joint..
I just rooted this morning using superoneclick. I had some troubles getting it to stay connected to my phone. I ended up having to change the USB port to one of my rear ones directly mounted on the MoBo of my desktop. The front ones seemed to have trouble keeping connected.
DL17 on mine.
SpeedSexndLivinLoud said:
I still can not find anything to work when rooting my phone i used z4 nothin superoneclick and nothin there
Anyone anything? i will donate if there is somthing that works
Click to expand...
Click to collapse
I had no problems rooting mine using SuperOneClick also.
I've got DL17.
So the superoneclick located at:
http://forum.xda-developers.com/showthread.php?t=803682
works for the Continuum?
What is DL17?
Is there a tutorial for using superoneclick anywhere? (I am an old fart)
The only reason I am interested in rooting is so I can then tether without the extra $20 a month charge and 2gb data cap. I can use my regular unlimited data plan that I already pay $30 a month for.
Thanks for any help in advance, and yes, I will donate.
Use SuperOneClick, but do it twice. The first may fail, the second will not. For some reason mine worked on the first try
Guide here: http://www.addictivetips.com/mobile/how-to-root-samsung-continuum-with-superoneclick/
I just successfully rooted my daughter's Continuum, and installed wireless tethering which worked FAMOUSLY thanks to this forum. Two issues:
I had to upload the apk to my website then download and run it to install it. The direction kept saying "mount the SD card". How exactly do I do that? When using USB on Windows 7 all I get is autorun options and the CDFS directory with the drivers on it.
Is there an application for USB tethering? I can charge while tethering if need be.

Help a noob install a rom on Epic 4g so I can tether with my over priced phone?

So I got the Froyo update and it killed my ability to tether and root.
Seriously, Im even having trouble with WIRED tethering. Its not working and wont root.
Please point me in the direction of some noob friendly step by step instructions for installing a custom rom that is tethering friendly, along with any info for simply getting wired or wireless tethering to work after the Froyo update?
You shouldn't have installed the update.
Sent from my HTC Glacier using XDA Premium App
Yeah I know. Is there nothing I can do now?
They say they can bring you back to 2.1 if you take it to the shop. Does the update do anything that prevents installing ROMs? When they bring you back to 2.1, will that fix whatever they did or is it in that version now too?
Why can't you root?
Because I accepted the update and the update killed root and tethering for me? I guess there was a way to upgrade without accepting that update.
z4root wont work, and also it says that the OS no longer has the drivers to support the free wireless tethering apps.
......Did you read the OP?
So how am I supposed to root if I cant even use clockwork to install new roms without root access? Am I totally ****ed? Should I just return this phone and get one from Verizon?
Yes I read the OP but the 2.2.1 update doesn't prevent rooting again. If it did, I wouldn't be rooted right now.
I'm not sure what you did or didn't do, but the one click method works.
hes never been one clicked. he only used z4root.
Nick_Djinn said:
z4root wont work, and also it says that the OS no longer has the drivers to support the free wireless tethering apps.
......Did you read the OP?
So how am I supposed to root if I cant even use clockwork to install new roms without root access??
Click to expand...
Click to collapse
z4root is hokey. you need to use the oneclick root. its really simple.
http://forum.xda-developers.com/showthread.php?t=770388
use this thred. it is for real root, not z4. also, the drivers are installed on your computer, not your phone.
austin420 said:
z4root is hokey. you need to use the oneclick root. its really simple.
http://forum.xda-developers.com/showthread.php?t=770388
use this thred. it is for real root, not z4. also, the drivers are installed on your computer, not your phone.
Click to expand...
Click to collapse
Thank you for something helpful finally.
That makes sense. I tried installing it on my phone. Thank you for noticing that.
You know, if you wrote these instructions for noobs it would really help....For example, when we are dealing with not 1 but 2 devices, it might be helpful to describe which device is doing what. One minute I am doing something with the phone and the next its just "install this"....Dumb it down a bit, like you are talking to people who dont know anything about anything.
Anyway, thanks. Im going to try this now.
Nick_Djinn said:
Thank you for something helpful finally.
That makes sense. I tried installing it on my phone. Thank you for noticing that.
You know, if you wrote these instructions for noobs it would really help....For example, when we are dealing with not 1 but 2 devices, it might be helpful to describe which device is doing what. One minute I am doing something with the phone and the next its just "install this"....Dumb it down a bit, like you are talking to people who dont know anything about anything.
Anyway, thanks. Im going to try this now.
Click to expand...
Click to collapse
Don't feel too bad. I had to read that stuff several times before even deciding whether I should try it.
It keeps saying phone is not connected, even though it says USB-storage is enabled and I can access the files on my phone.
Don't click on mass storage.....and turn on usb debugging
Sent from my SPH-D700 using XDA App
The NON-One click solution seems doable but complicated, and I dont really know what I am doing.
Im thinking about paying somebody to root the phone properly. One person advertised in the SF Bay Area that I know of.
wytecaztle said:
Don't click on mass storage.....and turn on usb debugging
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Cool.
Thanks for the support. Im going to try this at least for another day or so before giving up.
OK. Now it says rage against the cage is missing.
The file is clearly there, but VLC media player wants to open it instead of anything useful.
do you use any sort of anti virus? it will remove things from the ragagainstthecage exploit. disable you antivirus for a few minutes and redownload the the rootpackage. im not saying thats what the problem is, im just saying antivirus clashes with the root method.
A little effort goes a long way. Getting root is easy for the epic. Install the samsung drivers, turn on usb debuging on phone, extract the oneclick folder and run the "run.bat" file and let it do its thing.
Sent from my SPH-D700 using XDA App
Nick_Djinn said:
OK. Now it says rage against the cage is missing.
The file is clearly there, but VLC media player wants to open it instead of anything useful.
Click to expand...
Click to collapse
I had that problem also and it turned out that I was trying to run it from a networked drive. I had to unzip the file to my computer desktop then run the program from there before it worked properly.
If you check out this thread there is a how to video i made to root and flash a rom. Check it out, I think it will help you out.
http://forum.xda-developers.com/showthread.php?t=1009997
make sure correct samsung drivers are installed on your computer (32 or 64)
download and extract once click root to your computer
Enable usb debugging on your phone (settings - applications - development - usb debugging)
Plug phone into computer
Run run.bat, wait, and enjoy.

[Q] Rooting Nexus for Android Commander

I'm want to use Android Commander to transfer some files back and forth to the PC for development. AC needs root access... I've used WugFresh's excellent toolkit to unlock and root the device. All worked fine; SuperSU is present, BusyBox installed. But AC still reports no root access, and the FAQ briefly mentions the difference that not all rooting gives root access to adb.
Can anyone explain in simple terms (I'm pretty new to android) how to get full root access to the device so that I can use Android Commander? Googling for instructions to root the device seems to pretty much always lead back to WugFresh's toolkit, which I've already done.
Stuart
Try the link below .I remember having a similar problem on a Galaxy Note. I ain't certain but I think its to do with ADB insecure/secure. I could be completely wrong of course!!
http://www.xda-developers.com/android/run-adbd-in-root-mode-with-adbd-insecure/
ScottArten said:
Try the link below .I remember having a similar problem on a Galaxy Note. I ain't certain but I think its to do with ADB insecure/secure. I could be completely wrong of course!!
http://www.xda-developers.com/android/run-adbd-in-root-mode-with-adbd-insecure/
Click to expand...
Click to collapse
Many thanks, yes, that seems to have worked. Strange that there isn't more info about this out there.
This says that it only persists until a reboot - I would still be interested in anyone knows a way of doing this permanently without installing a custom ROM
Stuart

Categories

Resources