Related
ADB Shell connects just fine, but I cannot SU into it. I am rooted and have the latest SuperUser installed... In addition, I have USB debugging enabled, the LG drivers, and Root Explorer works perfectly.
RESOLVED:
You must have SuperUser OPEN while trying to SU from ADB. I don't remember this being needed on my Nexus One, but it's working now. I will keep this up for others that might need it....
Sceencast in droid explorer isnt working for me.rooted g2x. Maybe ill reinstall it after i get home from work. Is yours working?
Do you have SuperUser OPEN while trying to use it? Seems that it's not running persistently like it did on my N1
momentarylapseofreason said:
Do you have SuperUser OPEN while trying to use it? Seems that it's not running persistently like it did on my N1
Click to expand...
Click to collapse
just got home from work. gonna try it now.
nope, no screencast even with super user running. just rebooted. gonna try again. logcat seems to be going nuts though.
I was going crazy about this and asked Chris Soyars because I have never had to do this either. This is what he said:
"You can just type 'su' while in an adb shell, and it should drop you down to root. You won't get adb providing root until you have a boot image flashed that isn't running in secure mode.... -Chris Soyars"
wewoapsiak said:
I was going crazy about this and asked Chris Soyars because I have never had to do this either. This is what he said:
"You can just type 'su' while in an adb shell, and it should drop you down to root. You won't get adb providing root until you have a boot image flashed that isn't running in secure mode.... -Chris Soyars"
Click to expand...
Click to collapse
First you need to go to settings developer options and root access and check apps and ADB
Then you might have to do the CHMOD -R 777 /directorynameyouaretryingtoaccess
Guys. I am assuming the su in adb shell is preceded by an adb remount? By default system is ro not rw.
Sent from my LG-P999 using xda app-developers app
I wasn't able to find a tidy all in one guide for linux user rooting here on XDA, so I decided to post this one. I was using Ubuntu 10.04 on a 32 bit processor.
This guide assumes you already have ADB up and running on your box. If you can't get ADB going yourself, then this method is most likely beyond your skill level anyhow
First, on your Sidekick ensure Settings>Applications>Development->USB Debugging is checked (just a reminder, I'm so used to this being on I forgot to do it on my new Sidekick)
After you have ADB up and running, make sure that your system has USB rules (a "driver") for communicating with the Sidekick.
As root:
Create or edit /etc/udev/rules.d/51-android.rules and add this line:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8″, MODE="0666"
Then secure the file and restart udev:
Code:
# chmod a+rx /etc/udev/rules.d/51-android.rules
# restart udev
udev start/running, process 3793
As a regular user:
Connect the Sidekick via the USB cable and check that your device appears, killing any previous instances of ADB that might already be running first:
Code:
$ adb kill-server
$ adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ adb devices
List of devices attached
T8394f1f27b0 device
My device's id is T8394f1f27b0. Yours will be different.
Download and unzip the rageagainstthecage-arm5 & Superuser packages from Cyanogen wiki or use the (possibly outdated) files attached below. You'll only need rageagainstthecage-arm5.bin, su and Superuser.apk.
From a terminal, run the binary to hack the system as root:
Code:
$ adb push <path>/rageagainstthecage-arm5.bin /data/local/tmp
$ adb shell
$ chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
$ ./data/local/tmp/rageagainstthecage-arm5.bin
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={2650, 2650}
[*] Searching for adb ...
[+] Found adb as PID 4150
[*] 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.
$
Restart the ADB server, push su & the Superuser app to the system, and set up the root user & group with a blank password. You should have a root (#) prompt; if you don't, repeat the above steps to push & run the bin file.
Code:
# mount -o remount,rw /dev/block/stl9 /system
# exit
$ adb push <path>/su /system/xbin
$ adb shell chmod 4755 /system/xbin/su
$ adb push <path>/Superuser.apk /system/app
$ adb shell
# echo "root::0:0:root:/data/local:/system/bin/sh" > /etc/passwd
# echo "root::0:" > /etc/group
# mount -o remount,ro /dev/block/stl9 /system
# exit
$ adb reboot
Your phone should now reboot and be rooted. Yay!
U should make this in an excutable file so it will do everything automatic instead of imputing everythin but good work man
Sent From My Rooted Sidekick 4g XDA Premium App
Datlilboricua said:
U should make this in an excutable file so it will do everything automatic instead of imputing everythin but good work man
Sent From My Rooted Sidekick 4g XDA Premium App
Click to expand...
Click to collapse
Thanks amigo. Writing a decent fail-safe script that would execute on any user's system would be way too time consuming though!
samandiriel said:
Thanks amigo. Writing a decent fail-safe script that would execute on any user's system would be way too time consuming though!
Click to expand...
Click to collapse
i knoe but it will be much easiet for others lol
Sent From My Rooted Sidekick 4g XDA Premium App
Any linux user who would be using this method would have no issues following these directions.
sduvick said:
Any linux user who would be using this method would have no issues following these directions.
Click to expand...
Click to collapse
Thanks! Good to hear that positive feedback
As a linux user, these steps are helpful but as a lazy ass, it's hard to beat the one click root. There are still a few reasons why I still have a windows partition.
Sent from my SGH-T839 using XDA App
This is the way I rooted my phone. I also installed cwm adb as well
Sent from my MB525 using XDA App
so ive always wanted a sidekick 4g, just love qwerty phones, got a chance to get a mint one for next to nothing today and of course i grabed it. so i went straight to xda and had to dig to nearly the last page for this guide! (dont trust any one click root me deals but thats besides the point) anyway thanks for this, made figuring out root simple and quick, a whole 4min maybe?
*side note, very dissapointed to see that samsung has left this community with their **** in their hands, kinda depressing and shocking no one has been able to move this phone passed froyo, i almost got this phone like 18months ago but the vision barley edged it out for me, and im glad i did, been running jelly bean on that for a while.
anyway im not a talented dev and i dont use samsung so i dont know how much help ill be here. i can port and i can somewhat build from source but mostly just mod. either way this is a backup backup phone for me so im willing to cause all sorts of harm to it trying to find some missing loopholes. chances are slim if all this other talent hasnt yet but i cant wait to play a bit!
wow... i like to remable...
demkantor said:
so ive always wanted a sidekick 4g, just love qwerty phones, got a chance to get a mint one for next to nothing today and of course i grabed it. so i went straight to xda and had to dig to nearly the last page for this guide! (dont trust any one click root me deals but thats besides the point) anyway thanks for this, made figuring out root simple and quick, a whole 4min maybe?
*side note, very dissapointed to see that samsung has left this community with their **** in their hands, kinda depressing and shocking no one has been able to move this phone passed froyo, i almost got this phone like 18months ago but the vision barley edged it out for me, and im glad i did, been running jelly bean on that for a while.
anyway im not a talented dev and i dont use samsung so i dont know how much help ill be here. i can port and i can somewhat build from source but mostly just mod. either way this is a backup backup phone for me so im willing to cause all sorts of harm to it trying to find some missing loopholes. chances are slim if all this other talent hasnt yet but i cant wait to play a bit!
wow... i like to remable...
Click to expand...
Click to collapse
Keep you eyes on bhundven, dude. He is on the verge of taking it to the next level!
Sent from my SGH-T839 using xda premium
hey good to here! just the dinking around ive done on this the past few hours im so not on the verge of anything... except for another softbrick maybe
ive seen bhundvens name pop up here and there in threads and he dose look super promising.
and as a side note for other, the rooting method laid out in op is not just for linux, ive soft bricked my new phone like 6 times already today, each time ive had to use hiedmall to restore to stock and then reroot, the last two time i just did it the same way but with windows.... in case anyone cares that is
Hey. We care, we just don't have much hope of seeing a JB or even GB port. Good luck to you though. Let us know if you get anywhere. This is still my main phone. I just got an old Epic built in to my car (runs CM10.1 great!) but it only works on Sprint (I use it on WiFi with a FreedomPop), and even though it is a better phone with a great QWERTY, the QWERTY on the SK4G is still better (plus the Epic's battery is HORRIBLE) so I'm not sure I'd switch even if I could.
I've been looking to upgrade for a long time, but until someone comes out with a quad-core 1080p 5" with a 5-row QWERTY (please someone, please!), I will probably stick with my SK4G (for at least another 6-12 mos, at which point I might brakedown and give up on the QWERTY-slider dream that no company fulfills).
PS: Someone did make this in to a script (attached), which is what I use to root, but Super1click basically does the exact same thing too (when it works, which is not 100%). After doing this root, I always use Super1Click to Shell-Root though (because I don't know the ADB commands for that)
nevermind wrong thread..
Found this over at SDX Developers
It's so easy a caveman can do it.
http://forum.sdx-developers.com/index.php?topic=17172.0
Be aware that if you do this you have no control over what has root and what doesn't. The "gingerbreak" way, along with the Android SU, does.
couldn't a person just install superuser?
Intercepter said:
couldn't a person just install superuser?
Click to expand...
Click to collapse
yes you can.... ive tested all of the ways of rooting this phone and this one is the easiest! after you do it just install superuser from the market and your all good.
Hey that's my post lol! Yeah well the thing about malware and root access that no one hardly knows is that all these apps that use root exploits to cause harm, they never request su permissions because they use there own exploit to gain root. So superuser wouldn't prompt you on an exploit root being ran. Superuser just prompts when some app requests /system/bin/su or /system/xbin/su. If you want to keep your phone safe its a mater of knowing what you install on your phone. Even with superuser your not safe from root exploit attacks!
Me personally I like nit having to allow everytime I install a new root app. And I know what I install so I never worry about malware.
Sent from my MOTWX435KT using Tapatalk
I noticed that his fix is to basically link su to sudo, which allows "root" programs to run the included superuser applet.
So does this mean someone could just install the SuperUser app without going through the usual rooting process? Is Gingerbreaking unnecessary then?
what concerns me is that if these phones ship with sudo enabled and no root password, then any app can get root without any special effort. That means the Triump is VERY insecure. I'm wondering if we can safely remove sudo and solve that particular problem.
Maybe they did that to make fixing them easier, for when a phone got sent in they could gain root and do whatever they need in it, then turn it back off real quick. This is kinda like the tether menu being hidden but not removed on the OV. How stupid do they think people are?
I don't think it's a question of stupidity - it's more one of knowledge. They don't anticipate the run-of-the-mill user to be digging through the file structure of the phone for something they have no idea of what it does or how it works.
And I'd have to agree - the non-technical people have no desire to start digging through the phone, but rather, to use it as is.
Therefore......
So if this could be made a script. Then we could un-root just as easily for protection. I only need it for barnacle.
root
--------
sudo
ln -s /system/xbin/sudo /system/xbin/su
ln -s /system/xbin/sudo /system/bin/su
unroot
-------
sudo
rm /system/xbin/su
rm /system/bin/su
RIGHT?
Edit: the "shebang" line needs to be changed. Not sure to what. You may be better off just typing in the commands yourself.
Not tested, but this should work.
The root script:
Code:
#!/bin/sh
#filename: rootme
echo "Rooting Device"
sudo
ln -s /system/xbin/sudo /system/xbin/su
ln -s /system/xbin/sudo /system/bin/su
echo 'Root has been achieved'
The unroot script:
Code:
#!/bin/sh
#filename: unrootme
echo "Un-rooting Device"
sudo
rm /system/xbin/sudo /system/xbin/su
rm /system/xbin/sudo /system/bin/su
echo 'Un-root has been achieved'
Make these files somewhere and *cd* to that directory. Type either
Code:
./rootme
or
Code:
./unrootme
Hope this helps someone.
TomXP411 said:
I noticed that his fix is to basically link su to sudo, which allows "root" programs to run the included superuser applet.
So does this mean someone could just install the SuperUser app without going through the usual rooting process? Is Gingerbreaking unnecessary then?
what concerns me is that if these phones ship with sudo enabled and no root password, then any app can get root without any special effort. That means the Triump is VERY insecure. I'm wondering if we can safely remove sudo and solve that particular problem.
Click to expand...
Click to collapse
Yes, that is true that an app could very easily gain root access on the triumph. HOWEVER, as pointed out by b_randon14 above, practically all malware apps use a root exploit to gain root priveliges. This means that even an unrooted device is susceptible. As an example, take a stock samsung captivate. It has no root, and no way to gain root, without flashing a custom rom/kernel. However, if an app used the psneuter exploit, it could still gain root access. (Btw, that is how I originally rooted my captivate, using super one click with the psneauter exploit)
So really, the triumph is no less secure than any other android device. Plus, the triumph is the only android device, aside from dev phones such as the nexus one/nexus s that come pre-rooted. So a triumph specific malware app would have to be written.
Personaly, I like the su+superuser.apk method of rooting, but that is because it is the only method I have ever used. And remember, if you prefer to have su+superuser.apk, you either use gingerbreak, or just use this trick and then install superuser.apk.
Sent from my SAMSUNG-SGH-I897
Yeah and plus an app has to be designed to gain root its not like any old app can just up and decide to request root and start destroying! And stock without any root(I.e. my method or gingerbreak) an app doesn't call /system/xbin/sudo it would call /system/bin/su or /system/xbin/su. Plus I mean if you used gingerbreak you should realize that an app can get root without going through superusrr or calling on su. I mean how else do you think gingrrbreak app gets root in the first place to copy su and superuser? Through the gingerbreak root exploit!!
Sent from my OC'ed Triumph!
The concept of an app being able to gain root makes it just as dangerous as a malignant virus for Android. The only difference is, it's not a virus. It's a nice, helpful, and otherwise very good program. Lucky for us.
I'm working on a batch script that does the same thing as these instructions, anybody vaguely interested in using it (should it be put out)?
primetechv2 said:
The concept of an app being able to gain root makes it just as dangerous as a malignant virus for Android. The only difference is, it's not a virus. It's a nice, helpful, and otherwise very good program. Lucky for us.
I'm working on a batch script that does the same thing as these instructions, anybody vaguely interested in using it (should it be put out)?
Click to expand...
Click to collapse
I wrote one and posted on xda, I think, but the shebang line needs some adjustment to find sh. Hope that helps.
Sent from my rooted Moto Triumph
Why is this not working for me? I downloaded terminal emulator from the market, typed: "sudo" and get:
sudo: permission denied
$
tsac said:
Why is this not working for me? I downloaded terminal emulator from the market, typed: "sudo" and get:
sudo: permission denied
$
Click to expand...
Click to collapse
Did they patch it? These two lines of code run from ADB should "root" the device... and sudo is just there.
adb -d shell sudo ln ln -s /system/xbin/sudo /system/xbin/su
adb -d shell sudo ln ln -s /system/xbin/sudo /system/bin/su
Now you may not be able to run "sudo" alone, you may need to specify a command with it too? Unfortunately I can't try it again, because all of my phones are rooted now
In the event this didn't work, GingerBreak should work regardless.
I'll give it a try when my phone finishes charging.....Thank you
tsac said:
I'll give it a try when my phone finishes charging.....Thank you
Click to expand...
Click to collapse
Sure. although I would still recommend Gingerbreak instead...it's more complete and contains Superuser as an extra security measure.
Sent from my MOTWX435KT using Tapatalk
Never got to try anything....Phones screen is dead. You know how people describe the flashing screen when turned on and off? Well mine flashed once and it has not worked since... Hopefully virgin mobile will honor the 1 year factory warranty. I did absolutely nothing to this phone. It just took a crap. Removal of battery does nothing. Phone will receive calls but there is nothing but a backlight. Tried several different methods. Horrible phone....Should be recalled
Thanks for your trying to help me.
Sent from my reliable homebuilt gaming rig using FireFox
rooted my dad's triumph...question though...couldn't I flash clockworkmod via rom manager or do I have to go the long way?
edit: nvm, i see rom manager doesn't support the triumph
I need to send back my One S to tmobile.
To unlock bootloader i used:
[TOOL] HTC One S All-In-One Toolkit V1.0 [4-17-12] [PERM ROOT][Noob-Proof]
And to get root i used:
How to root your HTC One S (for Windows, Mac and Linux) (superboot)
In order to revert to stock i used the official usa tmobile thread (http://forum.xda-developers.com/showthread.php?t=1630440) in order to get the nandroid. Everything worked well, i also did a recovery using the all-in-one toolkit and it does in fact revert me back to stock.
problem is in the apps i still have the "SuperSU" app and i cant uninstall it or anything. aside from the fact that my phone already says relocked and tampered, it's going to look pretty obvious i had root with that app in there. how do i get rid of it?
If you are already back to bone stock without root -- then obviously you need to reverse course and re-root it and obviously you need to have a working adb setup... (although AndroidCommander works just fine with my One-S
after you have root (you could even try this without rooting but it will fail)
adb shell
$ su
#cd data
#ls
you get a list of the packages in /data (to confirm that it is there, look for "eu.chainfire.supersu-1.apk" and if you were nice to chainfire - "eu.chainfire.supersu.pro-2.apk" (could be .1 or .2 doesnt matter)
after confirming --
#rm eu.chainfire.supersu-1.apk
and do same for any other root apps that may incriminate you (sarcasm intended)
if no error message follows each #rm, then you are good.
Confirm by
#ls
if you dont see it there... then its gone from /data
Now you should also uninstall it from /system
#rm -r /system/app/eu.chainfire.supersu.apk
and if you really care.. rip out the odex
#rm -r /system/app/eu.chainfire.supersu.odex
reboot and your crime is not so evident.
if the above doesnt work -- next best thing
$ adb remount
(succeed)
$adb shell
$su
# pm list packages
(will return long list of the package names)
then
#pm disable eu.chainfire.supersu
which should return
#package eu.chainfire.supersu new state:disabled
This does not uninstall the app it just disables it... removes the icon so that nobody will see it unless they really look for it.. which no company is going to waste time looking for (they want to sell more phones)
now... i found this by searching. It was fun. Good luck.
There's actually an option in SuperSU, "Full unroot" under the Settings menu in the heading "Cleanup". The app gets rid of itself automatically. Very easy and painless.
Sprint HTC One SuperSu 1.65 Full unroot
kuroneko007 said:
There's actually an option in SuperSU, "Full unroot" under the Settings menu in the heading "Cleanup". The app gets rid of itself automatically. Very easy and painless.
Click to expand...
Click to collapse
I am looking for threads on the removal of SuperSU and returning to an unrooted device in order to update. I did the full unroot. Still can't update as Twerp wont let me. Thanks Hope someone is still paying attention to this very old thread.
So, I'm attempting to root a Charge that the volume keys do not work. Apparently, 1 and 2 year olds who have great throwing ability is something the Charge, well, anything really, doesn't exactly appreciate. Normally, I root by going into the download mode, and flashing CWM, then installing the ROM. Obviously, not happening here.
My question is, has someone with more knowledge than I figured out how to accomplish this? Its running stock FP5. I really don't want to send it in because of the contract timing and wasteful of money. I'm also willing to experiment replacing parts, if someone knows anything about it...
Thanks.
Sent from my SCH-I510 (Tweaked 3.0) using xda premium
Yep. There's a jig that will force the phone into dl mode. IIRC it's branded for the gnex but it's confirmed to work on the Charge as well. http://forum.xda-developers.com/showthread.php?p=27533069
Sent from my SCH-I535 using Tapatalk 2
Hey, I had a thought of using ADB to root, and somehow forcing CWM on it, then using an app to boot it into dl mode. I've never used and before and don't know if it's possible, although, from what I read, it seems plausible. Can you offer any insight on this idea?
Sent from my SCH-I510 using xda
edji-x said:
Hey, I had a thought of using ADB to root, and somehow forcing CWM on it, then using an app to boot it into dl mode. I've never used and before and don't know if it's possible, although, from what I read, it seems plausible. Can you offer any insight on this idea?
Sent from my SCH-I510 using xda
Click to expand...
Click to collapse
If you have adb all set up and it properly recognizes your phone (something comes up when putting in the adb devices command) you can boot into download mode with
adb reboot download
Actually it's something I looked into recently for another member. I'm not saying it's not possible but I don't think we have the right tools for it. Originally ginger root was used via adb to root the charge but that's not going to work with our version of gb (assuming you could still find it). I'm not sure the format of cwm will work either. I'm not really proficient with adb so someone with more expertise might be able to get you going.
Sent from my Nexus 7 using Tapatalk 2
Awesome. I don't have it installed yet, but it doesn't look like it takes much to make it work. Plus, I have nine that isn't screwed up, so I think I'll see what I can come up with later.
On a side note, I can't post a reply to your tweaked 3.1 thread, but I ran into somewhat of a problem... run tweaktools, did the tweaks thing, phone BARELY would run. I also couldn't get a shell to run to get back in to uninstall. What I ended up doing to fix was a reinstall of SuperSU and installing a bash shell off a different emulator to get back into tweaktools. This was after I played in /system/etc/init.d awhile trying my hand at fixing it. Thought you may want/need to knoknow.
Sent from my SCH-I510 using xda
By the way, thanks for the tip. I'll report one way or another in a day or 2.
Sent from my SCH-I510 using xda premium
edji-x said:
On a side note, I can't post a reply to your tweaked 3.1 thread
Click to expand...
Click to collapse
You need 10 posts minimum to post in the Dev forums, XDA's rules.
Sent from my Droid Charge running [email protected] 3.2a enhanced by dSlice's Scripts & Tweaks
edji-x said:
Awesome. I don't have it installed yet, but it doesn't look like it takes much to make it work. Plus, I have nine that isn't screwed up, so I think I'll see what I can come up with later.
On a side note, I can't post a reply to your tweaked 3.1 thread, but I ran into somewhat of a problem... run tweaktools, did the tweaks thing, phone BARELY would run. I also couldn't get a shell to run to get back in to uninstall. What I ended up doing to fix was a reinstall of SuperSU and installing a bash shell off a different emulator to get back into tweaktools. This was after I played in /system/etc/init.d awhile trying my hand at fixing it. Thought you may want/need to knoknow.
Sent from my SCH-I510 using xda
Click to expand...
Click to collapse
Sorry to hear of the troubles - not sure what would have caused the issue with tweaktools. You weren't able to su, or you weren't able to open terminal emulator? What were you messing with specifically in the tweaks?
dwitherell said:
If you have adb all set up and it properly recognizes your phone (something comes up when putting in the adb devices command) you can boot into download mode with
adb reboot download
Click to expand...
Click to collapse
:banghead:
Sigh, I don't know why I didn't think of that lol. And I was Ninja'd. Double whammy lol
Sent from my SCH-I535 using Tapatalk 2
Okay, Found it in ADB, and am able to reboot into download, so all is well, I think.
On the tweaktools issue, I kinda did something like this...One tweak does okay, so lets install ALL of them....after that, performed the reboot, and everything went very sloooow. So, I tried to get into a term emulator, and nothing happened, the shell wouldn't even start. Blank screen. So, I tried a different outside of ROM toolbox. Nothing. So, I played around with the settings here and there, and still nothing. I then went into root browser, and started trying to manually move the tweaks out, nothing different. So, I downloaded another term emulator, "Better Terminal Emulator" and got a bash shell to at least open, was able to get into tweaktools, erase all tweaks, clear downloads. But the shells still weren't operating right. They'd open and run, but nothing would show on screen. So, a erase/reinstall of SuperSU, everything good....LOL
Well, maybe it'll help, maybe not, but here's the path I used to do this:
Visit samsung's site for the ADB download and install to c:\android-sdk\ (default)
Put USB Debugging on in phone
Start up command line and Odin 1.82
issue following in command line (notably in the c:\android-sdk\platform-tools)
Code:
adb reboot download
Odin up some Tweaked 2.2 with recovery and kernel for root
once rebooted, issue the following in ADB shell:
Code:
adb shell
su (Checked phone to be sure root was granted)
cd /data
rm -R *
cd /cache
rm -R *
cd /dbdata rm -R *
reboot, then adb reboot download.
Flashed EP4 Stock, updated,
Updated to FP5E
Once again, USB debug, adb reboot download, and Odin Tweaked 3.1 with 0302,
follow above code again, reboot, and I think I have it right....
Since the volume keys don't work on here, is there a way to screw around in the recovery mode via ADB rather than only the keys? I see ADB sees the phone in recovery, and seems to want to connect with it....Second is, is there a way to play with this in the *nix enviroment? I also have been searching for the Gingerbreak, etc to root this thing on stock, but haven't been able to do it....and last, is there a way to do a data wipe other than what I did, and think i accomplished with ADB?
Thanks
With the CWM that I am using, you can use the hard buttons at the bottom of the phone to navigate.
Sent from my SCH-I510 using Xparent Red Tapatalk 2