Related
Currently I'm trying to gain access to /system and mount it as read/write. I've tried using
adb shell
mount -o rw,remount /dev/block/mtd3 /system
Click to expand...
Click to collapse
but it's not working. It says nothing afterward. I've noticed that it now says "sh-3.2#" instead of just "#" or "$" as it used to... Could this be the problem? What does it mean?
This is what I see:
C:\Users\Sam>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb shell
sh-3.2# su
su
sh-3.2# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
Help?
Just typing adb remount (while not in shell) will mount system read/write. The other command is for terminal on the phone mostly
And you won't get any confirmation but an echo
Sent from my HERO200 using XDA App
danaff37 said:
Just typing adb remount (while not in shell) will mount system read/write. The other command is for terminal on the phone mostly
And you won't get any confirmation but an echo
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Hopefully not thread-jacking but I have a similar problem. I get:
remount failed: Operation not permitted.
Now what?
Sounds like adb isn't granted su permissions. Adb shell, do you see a # prompt? If not, type su, then watch your phone to allow. Then type exit, then adb remount
Sent from my HERO200 using XDA App
danaff37 said:
Sounds like adb isn't granted su permissions. Adb shell, do you see a # prompt? If not, type su, then watch your phone to allow. Then type exit, then adb remount
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Yup, already did all that. Still no dice. Wtf, right?
open the superuser app and 'forget' adb to redo it maybe?
I did get some kind of error that set something about root access not being allowed in the production version of adb/sdk or something? I'll have to reproduce that error so I can post it here.
Phateless said:
I did get some kind of error that set something about root access not being allowed in the production version of adb/sdk or something? I'll have to reproduce that error so I can post it here.
Click to expand...
Click to collapse
Found another thread on another board. I just flashed amon ra's recovery and booted up from there, and it appeared to let me copy!
But then it wouldn't let me cd to system/app. It let me cd to system, but not to app. Weird... I booted back up and there's no evidence of the "copied" apk, anywhere.
SOOOO confused now...
Wait...what rom are you on?
Sent from my HERO200 using XDA App
danaff37 said:
Wait...what rom are you on?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
OEM 1.6, Androoted and overclocked. That's it.
You may need to update busy box. Our try a third party rom
Sent from my HERO200 using XDA App
danaff37 said:
You may need to update busy box. Our try a third party rom
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
But I need the oem rom to receive the OTA update to Froyo, lol. I have busybox through titanium backup but maybe i should download it on my own. Available in the market, correct?
For now I'm going to flash the tmus rom (ota update cm6 remix) to see if this tmo froyo thing is even worth the trouble. Oy vey...
I bet cm6 will still beat out your official update
danaff37 said:
I bet cm6 will still beat out your official update
Click to expand...
Click to collapse
Can your rom beat up my rom?
Now I'm not trying to be like that. Lol just saying. I installed it on my buddy's mt3g and he loves it. Runs smooth as butter.
Sent from my HERO200 using XDA App
Haha, I know, I just couldn't resist.
Originally posted by Stetsonaw at androidforums...
Please be aware that I did not write these instructions. I only posted them. Stetsonaw wrote these instructions. While comfortable in ADB and have rooted my phone many times in testing as well as rolled back the versions etc... I have no more insight into how or why it is not working for you. If you followed the directions exactly on a version 4 phone, this should work no problem.
Haxcid
Links to the necessary files are listed at the bottom.
Remember, I am not at fault if you brick your phone, now, proceed.
Connect your phone in charge only mode to install the LG Bootstrapper and drivers, or grab the LG Universal Drivers.
Change your USB Mode to Internet Connection
Go into Settings/Applications/Development and ensure USB Debugging is turned on
If all goes according to plan, you should see the ADB Ladybug icon in your notification bar
I updated the Rootzwiki page with the same info found below.
Busybox actually comes installed by LG on the Revo, how awesome is that??
Download the rageagainstthecage binary
Download the SU binary
Move these files to the same directory your adb.exe is in.
Code:
The > and # characters below illustrate the prompt
you should have, if you have the $ when you go into adb shell,
exit out and type 'adb usb' then go back into adb shell and
you should see the #
Open Command prompt (either use the Windows Key+R and type cmd or start/run, then type cmd)
32-bit users: >cd c:\program files\android\android-sdk\platform-tools
64-bit users: >cd c:\program files (x86)\android\android-sdk\platform-tools
Or >cd (whatever directory adb is in)
>adb devices (verifies you are connected)
>adb push rageagainstthecage-arm5.bin /data/local/temp/rage
(if the above command fails due to read-only, type 'adb usb' then 'adb root' to validate root status, then 'adb devices' again to verify connection)
>adb push su /data/local/temp/su
>adb shell chmod 777 /data/local/temp/rage
>adb shell ./data/local/temp/rage
>adb shell (If this gives you a $ prompt instead of a # prompt, type 'su', if that fails, 'exit', 'adb usb' like above.)
#mount -o remount,rw -t ext3 /dev/mmcblk0p12 /system
#busybox cp /data/local/temp/su /system/bin/su
#chmod 6755 /system/bin/su
Verify the file is in place w/correct permissions
#cd /system/bin
#ls -l *su
After the ls command you should see the following returned by the system:
-rwsr-sr-x root root 26248 2011-05-29 01:09 su
At this point, you may way to remove the files you put in /data/local/temp (optional):
#rm /data/local/temp/su
#rm /data/local/temp/rage
continue with commands
#reboot
Download and install SuperUser from the Market
Thanks Zennmaster, _mrbirdman_ for finding the linux routes and birdman for helping me out, and droidx8971 for helping me find all the information possible!
http://wikifilez.com/Root Files/revolution/rageagainstthecage-arm5.bin
http://wikifilez.com/Root Files/revolution/su
https://market.android.com/details?id=com.noshufou.android.su&feature=search_result
http://www.lg.com/us/support/mc-support/drivers/LGAndroidDriver_Ver_1.0_All.exe
Just a note for some. The rageagainstthecage bin file may be detected as a virus/trojan. It is not. You may want to disable your antivirus before downloading the .bin file.
I run avira on my desktop and it caught the file as a virus everytime I downloaded it and then deleted it. Avast on my laptop however did not.
Root is simple if you follow the instructions. You need to make sure that adb recognizes your device. Takes 5 minutes to complete, took me longer to install adb again and update it.
Any reason to not use the one click method? Seems to be working
bwhxeon said:
Any reason to not use the one click method? Seems to be working
Click to expand...
Click to collapse
No idea. I have not used the one click. Create a thread for it. I posted what I know which is adb.
Successfully Rooted
with RootzWiki instructions for Windows, needed the remount and busybox lines to overcome the permission denied when pushing su.
Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .
MXFrodo195 said:
Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .
Click to expand...
Click to collapse
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
Oh ya I know, I just always keep a stock one, on the Inc if you factory reset from an AOSP rom, you'd bootloop, so you had to make sure you were on a Sense 1.0 or stock rom(from my experience), so I was just making sure it was no big deal to go back.
Any idea when we will have cw on this?
Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
I tried the factory reset. I am still rooted.
navycow said:
I tried the factory reset. I am still rooted.
Click to expand...
Click to collapse
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App
MXFrodo195 said:
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App
Click to expand...
Click to collapse
If you have to return your device, simply remove the superuser app, after you unfreeze anything you may have frozen then factory reset. They honestly will never know it was rooted. The only way now that you can really tell is the super user app from market.
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Thank you for confirming this. My revolution just came in the mail today!
Thanks for posting this here for me Haxcid!
Sent from 1885
navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Cool thanks for checking. Any benefits for ADB over S1C? Can't wait to finally root and freeze half these apps. I think we need a few more twitters to praise koush for a recovery on this beast.
Sent from my VS910 4G using XDA Premium App
Is there recovery for this now? Did I miss something?
stetsonaw said:
Is there recovery for this now? Did I miss something?
Click to expand...
Click to collapse
No No, I was saying we need to praise Koush's good work so he will make one faster .
And Stetsonaw, any idea if I root through ADB, can I unroot with S1C, since it uses the same idea.
S1C for whatever reason will not run(tried three computers, a XP, Vista, and Win7 lol), it keeps freezing at the same spot, everytime.
Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.
stetsonaw said:
Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.
Click to expand...
Click to collapse
Hmmm, ya now my computer for whatever reason won't open up ADB through command. This is getting irritating lol. Should be nice and simple, but it just won't go through. If I downloaded the SDK Manager like 4 months ago, it shouldn't matter, correct?
make sure you change directory to wherever your adb.exe is located... as in:
Code:
cd C:\Program Files\Android\android-sdk-windows\platform-tools
Just wondering if I have installed adb correctly I can open my command prompt using windows vista and type adb devices and I get my serial number displayed as a connected device does this confirm and is working? Thanks for your help! Completely new to this.
Beamer9408 said:
Just wondering if I have installed adb correctly I can open my command prompt using windows vista and type adb devices and I get my serial number displayed as a connected device does this confirm and is working? Thanks for your help! Completely new to this.
Click to expand...
Click to collapse
As far as I know that does mean you have it installed and running correctly.
I agree, that would tell me it's installed correctly. Shell into your phone. If you can do that, you should be all set. Directions for shelling into your phone can be found in the forums. If you can't find them, let me know and I'll help you out. We all have to start somewhere. Lol!
Sent from my VS910 4G using XDA Premium App
Are you rooted? Meant to ask that.
Sent from my VS910 4G using XDA Premium App
thermal_tim said:
Are you rooted? Meant to ask that.
Sent from my VS910 4G using XDA Premium App
Click to expand...
Click to collapse
Oh sorry I thought I mentioned that in my earlier post I am rooted running decrap..and the other mods that are on this forum
Ok so this is what is going on I go into command prompt type in CD then to the tools directory and hit enter then type adb devicesand hit enter serial number comes up so I type adb shell and I get $ ok so I read somewhere if you get that prompt type aubri hit enter ok so I do that superuser permission is asked on my phone so I said allow it. Retyped adb shell and it isn't recognizing what adb is? Not sure what is going on here thanks to anyone who helps explain if I'm doing something wrong.
Beamer9408 said:
Ok so this is what is going on I go into command prompt type in CD then to the tools directory and hit enter then type adb devicesand hit enter serial number comes up so I type adb shell and I get $ ok so I read somewhere if you get that prompt type su hit enter ok so I do that superuser permission is asked on my phone so I said allow it. Retyped adb shell and it isn't recognizing what adb is? Not sure what is going on here thanks to anyone who helps explain if I'm doing something wrong.
Click to expand...
Click to collapse
Once you
$adb shell
$su
#
You shouldn't need to type adb shell again bc ur already in it...
it would also help us to help you to know what you are trying to do with ADB shell... being that you are rooted, what else do you need to do with it?
Sent from my VS910 4G using Tapatalk
S.Meezy said:
Once you
$adb shell
$su
#
You shouldn't need to type adb shell again bc ur already in it...
it would also help us to help you to know what you are trying to do with ADB shell... being that you are rooted, what else do you need to do with it?
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
Thanks honestly I'm not trying to do anything with it just trying to seeif I have it installed correctly someone suggested to see if I could go into shell so I tried and that was my results.
Beamer9408 said:
Thanks honestly I'm not trying to do anything with it just trying to seeif I have it installed correctly someone suggested to see if I could go into shell so I tried and that was my results.
Click to expand...
Click to collapse
assuming your screen looked like this...
$adb shell
$su
#
...and changed from $ to # when you did it, you're good. also, it showing as a device was a good indicator too.
What is it ? ADB Shell . is it CMD command on Windows or what ?
muslimbaha said:
What is it ? ADB Shell . is it CMD command on Windows or what ?
Click to expand...
Click to collapse
https://developer.android.com/tools/help/adb.html
It's Android Debug Bridge. Basically, it's a command line interface from your PC to your phone. Think of a terminal emulator that you run on the phone itself. ADB is pretty much the same, but from a PC. It is part of Android SDK. You can also find it included in many installation packages posted here on XDA, e.g. CWM recovery. There is an executable and a couple of DLLs.
P.S.: TrymHansen beat me to it...
kt-Froggy said:
It's Android Debug Bridge. Basically, it's a command line interface from your PC to your phone. Think of a terminal emulator that you run on the phone itself. ADB is pretty much the same, but from a PC. It is part of Android SDK. You can also find it included in many installation packages posted here on XDA, e.g. CWM recovery. There is an executable and a couple of DLLs.
P.S.: TrymHansen beat me to it...
Click to expand...
Click to collapse
Sorry, but i know what it is now, how do i run it though? im trying to follow the htc desire hd guide to root my phone, which everything is done up until the point i have to test that i have root in debug mode. Not sure how to do this? run abd.exe? it just showed me a cmd window which runs and then dissapears.
If you got your phone rooted or want to test it run adb.exe shell the type su and hit enter. If the prompt change from $ to # you have root access
Sent from my LG-P990 using xda app-developers app
bitdomo said:
If you got your phone rooted or want to test it run adb.exe shell the type su and hit enter. If the prompt change from $ to # you have root access
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
What is likely to be the problem if it says SU permission denied?
If you are on stock, that means that you have no root access. If you have cm10 or cm10.1 you have to enable adb root access somewhere in the settings. I am sorry but I can not tell you at the moment where to enable it because I am on stock right now.
Sent from my LG-P990 using xda app-developers app
kt-Froggy said:
It's Android Debug Bridge. Basically, it's a command line interface from your PC to your phone. Think of a terminal emulator that you run on the phone itself. ADB is pretty much the same, but from a PC. It is part of Android SDK. You can also find it included in many installation packages posted here on XDA, e.g. CWM recovery. There is an executable and a couple of DLLs.
P.S.: TrymHansen beat me to it...
Click to expand...
Click to collapse
Thanks Bro for this information
I have a Sprint HTC One M8. It's rooted. I have TWRP. I basically just wanted to get rid of bloatware. But now I want to follow a tutorial that requires me to be S-OFF.
I think I am on this step:
Push, Prepare, and Execute firewater:
adb reboot <–important!!!!
adb wait-for-device push firewater /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater
When I type any commands nothing happens. adb devices, adb shell, etc. Nothing. Am I supposed to go in Recovery?
If I go into recovery they work.. so I rebooted.. I pushed firewater over. I did adb shell and up pops:
~ # <-[6n.
I hit SU and it says /sbin/sh: su: not found.
I did chmod command from above. When I do the last step /data/local/tmp/firewater it says permission denied.
When you are booted into android make sure usb debugging is enabled. Settings > About > Software Information > More > click Build Number like 10 times to enable developers options. Then go to Settings > Developer Options > check USB Debugging. Also go to Settings > Power > uncheck Fastboot, You have to run firewater from android, NOT from recovery. What exactly are you trying to do that requires S-OFF?
Thanks. I've already got Developer. USB Debugging is enabled.
EDIT: Because I misread your post. I didn't know I run Firewater through Android. But anyway, it's not working.
I'm just doing a simple mod to hide the Boomsound icon. Stupid to have that clog up my notification area.
PS - I see you're in Ocean City, NJ? My friends wife's parents live in Somers Point. I go down to Smithville sometimes.. little town with all the shops in it.. it's fantastic when they decorate it for Christmas. Really nice stores to shop in and the inn has the best french onion soup I've ever had.
yuppicide said:
I have a Sprint HTC One M8. It's rooted. I have TWRP. I basically just wanted to get rid of bloatware. But now I want to follow a tutorial that requires me to be S-OFF.
I think I am on this step:
Push, Prepare, and Execute firewater:
adb reboot <–important!!!!
adb wait-for-device push firewater /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater
When I type any commands nothing happens. adb devices, adb shell, etc. Nothing. Am I supposed to go in Recovery?
If I go into recovery they work.. so I rebooted.. I pushed firewater over. I did adb shell and up pops:
~ # <-[6n.
I hit SU and it says /sbin/sh: su: not found.
I did chmod command from above. When I do the last step /data/local/tmp/firewater it says permission denied.
Click to expand...
Click to collapse
I am not sure exactly what you have going on, but here are a few tips. Make sure you have it mounted as a storage device. Also, make sure you open the command window in the same folder you have adb in, or navigate to that directory properly.
KUmike said:
I am not sure exactly what you have going on, but here are a few tips. Make sure you have it mounted as a storage device. Also, make sure you open the command window in the same folder you have adb in, or navigate to that directory properly.
Click to expand...
Click to collapse
That reply helped me. You said "mounted as storage device". When I clicked my phone it said "HTC SYNC" on it.
I'm good now, thanks!
I just went through this yesterday. Updating adb fixed it for me. Also, following those commands necessitates that the file is where u type it. So, I followed another website's guide and achieved s-off.
Sent from my 831C using xda app-developers app
iandmacdonald said:
I just went through this yesterday. Updating adb fixed it for me. Also, following those commands necessitates that the file is where u type it. So, I followed another website's guide and achieved s-off.
Sent from my 831C using xda app-developers app
Click to expand...
Click to collapse
Every time I connect my phone, all I need to do is select "Disk Drive" rather than HTC Sync. By default the phone chooses that. Now everything works fine.
I know you have already fixed your problem but I recommend uninstalling the HTC Sync Manager from your computer. Keep the HTC Drivers though. If you still get the popups to install HTC Sync after you uninstall it; remove the installer/option on your M8. You'll need a file manager and root to do that or you could install ViperOne and de-select the option in Aroma.
I can't remember the file you have to remove off-hand though, I just went through my folders and deleted stuff I didn't need or want. I made backups just in case it needed to be re installed.
KUmike said:
I am not sure exactly what you have going on, but here are a few tips. Make sure you have it mounted as a storage device. Also, make sure you open the command window in the same folder you have adb in, or navigate to that directory properly.
Click to expand...
Click to collapse
I had ADB work fine without switching to Mass Storage.
mswlogo said:
I had ADB work fine without switching to Mass Storage.
Click to expand...
Click to collapse
It definitely won't for me
Sent from my 831C using Tapatalk
KUmike said:
It definitely won't for me
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
Maybe you have HTC Sync installed? You shouldn't.
mswlogo said:
Maybe you have HTC Sync installed? You shouldn't.
Click to expand...
Click to collapse
Nope, I dunno. Works in mass storage mode
Sent from my 831C using Tapatalk
I was having similar problems with my M7 and Windows 7 devices after upgrading to 4.4.2 and Sense 6 (Team Nocturnal NuiSense). My phone wasn't recognized by HTC Sync or CDMA Workshop.
I kept uninstalling/reinstalling drivers, to no avail.
What finally worked like a magic bullet for me was to dial ##3424# and turn on DM Command Service.
I'm not sure if that will work for you, but it may be worth a shot.
I hv same problem but how I can on my USB debbuging mode ,,, rooted but no OS
{ParanoiA} said:
When you are booted into android make sure usb debugging is enabled. Settings > About > Software Information > More > click Build Number like 10 times to enable developers options. Then go to Settings > Developer Options > check USB Debugging. Also go to Settings > Power > uncheck Fastboot, You have to run firewater from android, NOT from recovery. What exactly are you trying to do that requires S-OFF?
Click to expand...
Click to collapse
I hv same problem but how I can on my USB debbuging mode ,,, rooted but S-on and I hv TWRP but no OS firmware ,,,, Kindly guide me what I should do to make active my usb debugging mode in HTC desire 828 dual sim ? plzzzz