Anyone know the correct codes for terminal with full root access and nand write access? I can't get su commands to work. I want to remove Sprint and other crap apk's from within terminal.
-------------------------------------
Sent via the XDA Tapatalk App
Not to hijack but what terminal app works best for the EVO?
can someone please explain it to me very detailed? i dont understand so much from the tuts i have read.
Are you rooted and s-off`d?
Blinkydamo said:
Are you rooted and s-off`d?
Click to expand...
Click to collapse
yes, i have
Put cwmod on the root of your sd card. Download terminal emulator from the market. In terminal emulator type
su
press enter
then type
flash_image recovery /sdcard/nameofrecovery.img
press enter
Replace nameofrecovery with whatever the name of the file is.
When you reboot into recovery it should be cwm 3.0.0.5 (should be amber font)
Sent from my Desire HD using XDA App
it shows file not found, even when i write the name of the file.
From the htc stock rom, you need to do it from your pc using fastboot. It won't work with terminal emulator.
Which rom are you running?
Do you have adb installed on your pc?
If you have fastboot, put the recovery.img in the tools folder of your sdk, start up your phone to the bootloader, connect your phone with the usb cable then open a command promt, navigate to the tools folder and type
fastboot flash recovery nameofrecovery.img
Press enter then type
fastboot reboot
Should take aboot 5 seconds
Sent from my Desire HD using XDA App
pwraggcan said:
From the htc stock rom, you need to do it from your pc using fastboot. It won't work with terminal emulator.
Which rom are you running?
Do you have adb installed on your pc?
If you have fastboot, put the recovery.img in the tools folder of your sdk, start up your phone to the bootloader, connect your phone with the usb cable then open a command promt, navigate to the tools folder and type
fastboot flash recovery nameofrecovery.img
Press enter then type
fastboot reboot
Should take aboot 5 seconds
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
i am running revolution HD, i just tried that and it said failed <remote: not allowed>
why must it be so damn hard? damn crap
Are you eng s off?
Try using adb shell from your command prompt then use the same commands you used in terminal emulator.
Sent from my Desire HD using XDA App
pwraggcan said:
Are you eng s off?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
i think so, http://forum.xda-developers.com/showthread.php?t=857537 i used that tut. is it so many different S-OFF's ?
Ok, with that s off method you can't use fastboot commands. Did you try the commands in adb shell?
Sent from my Desire HD using XDA App
pwraggcan said:
Ok, with that s off method you can't use fastboot commands. Did you try the commands in adb shell?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
i dont know, maybe. but im trying this now http://forum.xda-developers.com/showthread.php?t=855403 will it be a problem that i used the other S-OFF and now this?
I don't know. First try the commands in adb shell from your pc.
Sent from my Desire HD using XDA App
pwraggcan said:
I don't know. First try the commands in adb shell from your pc.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
if you mean the commands that is written in cmd, then i have already tried it, and it failed.
In the command prompt, navigate to your sdk then type
Adb devices
Press enter
Your device's serial number should show
Then type
Adb shell
Press enter
If you get a $ type su then press enter
Then enter the same commands you used in terminal emulator
Why do you want cwm 3? It's generally only for 2.3 roms.
Sent from my Desire HD using XDA App
pwraggcan said:
In the command prompt, navigate to your sdk then type
Adb devices
Press enter
Your device's serial number should show
Then type
Adb shell
Press enter
If you get a $ type su then press enter
Then enter the same commands you used in terminal emulator
Why do you want cwm 3? It's generally only for 2.3 roms.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I just installed it now thats why i want it, but do you know how i get back to the older cwm? do i just flash it in ROM manager?
Excellent. What worked finally?
To go back to an older version use rom manager or the use same way you upgraded.
Sent from my Desire HD using XDA App
You could try this, i haven't tried it myself so don't know if it works, but read it somewhere here on xda.
Go to this path with any file manager.
/mnt/sdcard/clockworkmod/download/koush.tandtgaming.com/recoveries
And copy that file to another folder. Then copy the name of that recovery (2.x.x.x) and then rename your 3.0.0.5 recovery with the old recovery name and just copy the new (2.x.x.x) to this path. (Just say yes to overwriting the file).
/mnt/sdcard/clockworkmod/download/koush.tandtgaming.com/recoveries
Then reboot and then boot into recovery and that should have changed the cwm from old to new. The color should be orange now and not green, if still green it didn't work.
If it doesn't work just restore the old recovery .img you've copied earlier (2.x.x.x).
Regards Dousan
e: Lol you fixed it while i was typing... Nice
pwraggcan said:
Excellent. What worked finally?
To go back to an older version use rom manager or the use same way you upgraded.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
i used this and then the command worked
Cool. Glad you're sorted. Good luck with cm7.
Sent from my Desire HD using XDA App
Dousan said:
You could try this, i haven't tried it myself so don't know if it works, but read it somewhere here on xda.
Go to this path with any file manager.
/mnt/sdcard/clockworkmod/download/koush.tandtgaming.com/recoveries
And copy that file to another folder. Then copy the name of that recovery (2.x.x.x) and then rename your 3.0.0.5 recovery with the old recovery name and just copy the new (2.x.x.x) to this path. (Just say yes to overwriting the file).
/mnt/sdcard/clockworkmod/download/koush.tandtgaming.com/recoveries
Then reboot and then boot into recovery and that should have changed the cwm from old to new. The color should be orange now and not green, if still green it didn't work.
If it doesn't work just restore the old recovery .img you've copied earlier (2.x.x.x).
Regards Dousan
e: Lol you fixed it while i was typing... Nice
Click to expand...
Click to collapse
Hello
just tried that worked flawlessly
thank you
When I go into my terminal emulator and run su to get superuser permissions it goes through fine. After getting SU permissions I type reboot recovery and terminal emulator comes back with "not permited!" error. I am running NB 2.15 ROM. Any idea why this error is popping up? Thanks!
Because reboot recovery isn't a command....Its only and adb command, not, you can use adb on term emu
Sent from my T-Mobile myTouch 3G Slide using XDA Premium App
Whoareyou said:
Because reboot recovery isn't a command....Its only and adb command, not, you can use adb on term emu
Sent from my T-Mobile myTouch 3G Slide using XDA Premium App
Click to expand...
Click to collapse
What about just "reboot" ? That doesn't work either and I thought that was a terminal emulator command.
Its a rom issue these commands dont work well w/ the espresso roms last time i checked, they work in cyanogen though
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
edit: and yes reboot recovery is a command, i tried it in terminal emulator and it rebooted the phone to recovery
Is there an app I can use as an ADB terminal on galaxy nexus so i could use ADB commands in the terminal, sent to another device..??
I know i've seen it before, just can't track it down again.
UKROB86 said:
Is there an app I can use as an ADB terminal on galaxy nexus so i could use ADB commands in the terminal, sent to another device..??
I know i've seen it before, just can't track it down again.
Click to expand...
Click to collapse
uuh... terminal emulator for example? adb binary is already built in.
wow and it was that simple lol..
please edit thread title to include [SOLVED] at the beggining.
For example, via a terminal emulator or simply an app that will execute ADB and Fastboot commands?
GroovinChip said:
For example, via a terminal emulator or simply an app that will execute ADB and Fastboot commands?
Click to expand...
Click to collapse
Did you try it? You can try something simple like swapping boot slots in the twrp terminal emulator
Veid71 said:
Did you try it? You can try something simple like swapping boot slots in the twrp terminal emulator
Click to expand...
Click to collapse
Nope, haven't tried it. Not sure if I need any files on the phone for it to work?
Sent from my Google Pixel XL using XDA Labs
GroovinChip said:
Nope, haven't tried it. Not sure if I need any files on the phone for it to work?
Click to expand...
Click to collapse
I'm not sure either but i can't imagine it'll hurt to try a reboot command or to swap slots
How can this even work? ADB only works when the phone is in fastboot mode, which automatically means that Android isn't even running surely? Hence you can't run apps.
Sent from my Pixel XL using XDA-Developers Legacy app
GroovinChip said:
For example, via a terminal emulator or simply an app that will execute ADB and Fastboot commands?
Click to expand...
Click to collapse
NO
With two phones and adb over network you can send a command to another phone using Tasker (maybe other apps too, only ever used it while looking for an answer to your same question). I know I at least sent reboot from one phone to another... But I think fastboot won't work like this, only (simple) adb shell commands - I'm pretty sure I gave up on it once I realized that I think it is not possible to change boot slots using this method....
Other than that, FlashFire can be used I a rooted phone to change boot slot - wipe dalvik and reboot to other boot slot. I don't know a way on a non rooted phone - anyone know a way without using pc and fastboot?
GroovinChip said:
For example, via a terminal emulator or simply an app that will execute ADB and Fastboot commands?
Click to expand...
Click to collapse
For fastboot and adb in recovery, you'll need the phone connected to to a computer (or device) via usb that you have access (local/remote) to in order to issue commands remotely, but you won't be able to see the phone's screen.
For adb in normal boot, you can either use "adb over network" (LAN) (if WAN, you'll need to bypass firewall if any) or connect your phone to a computer (or device) via usb that you have access (local/remote) to in order to issue commands remotely. You can see the phone's screen using tools such as AirDroid or TeamViewer.