Database Info

JF 1.42 rc33 and T.E.

I'm sure i'm not the only one that has noticed that you can't update terminal emulator with modded firmware, i did a mild look through the searches, and didn't find what i was looking for, is there a means to update this, i've tried takeing it out of white list and then updating, but no go... Not that its a big deal TE works, its just an annoying knawing thing in the back of my mind, knowing there is an update on the market, and i can't have it

Delete the terminal app in terminal by
su
cd /system/app
ls
them find the app that starts with com. something
type rm -> name of the app
update it in market

card13 said:
Delete the terminal app in terminal by
su
cd /system/app
ls
them find the app that starts with com. something
type rm -> name of the app
update it in market
Click to expand...
Click to collapse
gives me a read only error, i have to chmod it first right? have no clue how to do that right now, have to look it up. Thanks for pointing me to the proper file though

It'd probably be best to use adb.exe (available in the android SDK) to remove terminal emulator rather than using terminal emulator.
Also, in order to change anything in the /system partition, you need to remount it as read/write.
With adb this is easy:
Make sure your android has debug mode enabled (which I think is by default in all JF releases)
Hook it up to your computer with the USB cable
Open up a command prompt in windows (or whatever other OS you're using that has the Android SDK) and go to the tools directory in the SDK
Type "adb devices" to make sure adb sees your phone, if it doesn't, well uh...it's not working right, and you'll have to figure out why
Type "adb remount" to remount the /system partition as read-write
Type "adb shell" this will give you shell access to your G1, from there you can delete stuff from the /system partition. I think you might also be able to use "adb uninstall" but I don't know if that works for the /system/app folder.

thanks for the info TM will play with the sdk tools and see what i can do, they have been giving me a headache on linux, but then i haven't played with linux in about 6 years.. its come along way. Thanks again for the info wait 2 secs to reload the image

I've noticed that, too. I don't see a reason why I need to update TE, the one I have works just fine.

here your answer in the link below
this will allow you to remove the terminal and install the new one from market
http://forum.xda-developers.com/showthread.php?p=3287558

Noob guide: how to start terminal emulator as root.

The way to start the terminal as root is pretty easy.
Open term emulator and then hit the menu button and go into preferences. You need to go down to the bottom where it says something like initial command. Click that and at the end of the export command you see (I think the end is after $PATH) type ;su then hit enter. Now whenever you start TE you get su immediately.
Sent by breaking the sound barrier

Indirect said:
The way to start the terminal as root is pretty easy.
Open term emulator and then hit the menu button and go into preferences. You need to go down to the bottom where it says something like initial command. Click that and at the end of the export command you see (I think the end is after $PATH) type ;su then hit enter. Now whenever you start TE you get su immediately.
...
Click to expand...
Click to collapse
Sorry to re-open this old thread, but can anyone suggest modification to the terminal emulator that may allow it to START as root. Typing "su" afterwards switches the user, however the app DOESN'T start initially as root.

There's a better way to do it. Allow me to elaborate some logic:
In Terminal Emulator, whatever you set as the 'shell command line', basically is nothing more than the command you set as the 'initial shell command'. The key difference is that the 'shell command line' is initiated prior to the 'initial shell command'. Therefore, anything set as 'initial shell command' to automate root access comes secondary to the shell you have already started (through the 'shell command line'), which will cause you opening a shell in a shell and thus having to exit two shells. This is dirty. You could work around that with an 'initial shell command' like "su && exit", but it'll remain to be a dirty solution.
If you want the shell in Terminal Emulator to start as root, then set the following 'shell command line' (personally I prefer bash):
Code:
[SIZE="3"]/system/xbin/su -c "/system/xbin/bash -"[/SIZE]
That way only, Terminal Emulator will actually start your session as root and nothing more but root. When you exit the shell, you exit the one and only shell initiated as root ending your session at once.
Now for the 'initial shell command', which you no longer require to obtain root using the above method, I personally have the following set to keep things consistent and give the shell a nice looking start:
Code:
[SIZE="2"]mkdir -p /data/local/bin && export PATH=/data/local/bin:$PATH && clear && uname -a && echo[/SIZE]
I hope this clarified things a bit.
Albert

bitmaster2000 said:
There's a better way to do it. Allow me to elaborate some logic:
In Terminal Emulator, whatever you set as the 'shell command line', basically is nothing more than the command you set as the 'initial shell command'. The key difference is that the 'shell command line' is initiated prior to the 'initial shell command'. Therefore, anything set as 'initial shell command' to automate root access comes secondary to the shell you have already started (through the 'shell command line'), which will cause you opening a shell in a shell and thus having to exit two shells. This is dirty. You could work around that with an 'initial shell command' like "su && exit", but it'll remain to be a dirty solution.
If you want the shell in Terminal Emulator to start as root, then set the following 'shell command line' (personally I prefer bash):
Code:
[SIZE="3"]/system/xbin/su -c "/system/xbin/bash -"[/SIZE]
That way only, Terminal Emulator will actually start your session as root and nothing more but root. When you exit the shell, you exit the one and only shell initiated as root ending your session at once.
Now for the 'initial shell command', which you no longer require to obtain root using the above method, I personally have the following set to keep things consistent and give the shell a nice looking start (think twice before commenting about the mkdir if you don't like it):
Code:
[SIZE="2"]mkdir -p /data/local/bin && export PATH=/data/local/bin:$PATH && clear && uname -a && echo[/SIZE]
I hope this clarified things a bit.
Albert
Click to expand...
Click to collapse
Thanks a lot, I solved the problem somewhat differently, in a way that may cause some raised eyebrows from people concerned with security. I created a copy of "sh", did a chmod 6755 on it, and set it as the shell. The reason for this is that I don't have superuser installed on my phone.
Off topic, it's all moot now because I managed to drop it again and the LCD detached from the gorilla glass. Happens once every 9 months. I came to XDA to see from my old posts where I bought the screen before.

Initial Command not working in cm11 (s7262).
Entering su in Initial Command in Terminal Emulator Preferences get this result:
Code:
[email protected]:/ $ 8;53R
Entering manually su command get OK., but initial command is not working.
How can I fix this problem?
Thanks.

How To Root An AT&T HTC One X [No Longer Working]

This root was rendered unusable at this time due to AT&T disabling the Ready2Go app installation feature. Working on a work around now.
Original content:
http://www.androidpolice.com/2012/0...the-att-htc-one-x-on-version-1-85-or-earlier/

Hope you get your One X soon dude!
Confirmation number: 8PH11891CA483914J

In! Thanks Justin!
Billy

Damn, thanks a lot!

jcase said:
Now comes the timing critical part, you have to use ATT Ready2Go to Download "AT&T Mark the Spot", and interrupt the install process right after the download has finished. Easiest way is to reboot the device, but we have found other ways to do it.
Click to expand...
Click to collapse
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.

id10terrordfw said:
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
Click to expand...
Click to collapse
You need to reboot right after the download is done. I haven't had a chance to do this in person, I just found it in the firmware and asked others to test for confirmation. Hopefully someone can chime in and tell us what visual indicators show when to do the reboot.
Some testers got it first try, some took 3-4 tries.

id10terrordfw said:
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
Click to expand...
Click to collapse
I'm with you on this one. I've been trying this for last hour but to no avail. The minute it says in status bar that it's installing, I tried command. I tried when I press finish on phone and LTE signals go up and down and even tried as soon as I was done with att site but can't get it to work. I've restarted 20 times and this startup sounds I think is now annoying other people in the office

jcase said:
You need to reboot right after the download is done. I haven't had a chance to do this in person, I just found it in the firmware and asked others to test for confirmation. Hopefully someone can chime in and tell us what visual indicators show when to do the reboot.
Some testers got it first try, some took 3-4 tries.
Click to expand...
Click to collapse
Hah, well now I just feel dumb as I am on try 10 or so. I must not be able to hit the timing right at all. I'll keep at it, as I am constant as the northern star.

Don't feel dumb, it is very timing critical, with few real indicators of when to pull it off.
Maybe xfinrodx or designgears can chime in on this one

noobsquared said:
I'm with you on this one. I've been trying this for last hour but to no avail. The minute it says in status bar that it's installing, I tried command. I tried when I press finish on phone and LTE signals go up and down and even tried as soon as I was done with att site but can't get it to work. I've restarted 20 times and this startup sounds I think is now annoying other people in the office
Click to expand...
Click to collapse
Turn your ringer off, it will silence the startup sound. At least I can help with that!

id10terrordfw said:
Turn your ringer off, it will silence the startup sound. At least I can help with that!
Click to expand...
Click to collapse
Thanks, but everytime I do factory reset...it comes back on?
I might be doing something dumb.
After I get permission denied error, I try to start at the process of tryping:
Code:
adb shell ln -s /data/local.prop /data/install/com.att.android.markthespot.apk
but when I do that after uninstalling AT&T Mark the spot, it gives me erorr:
link failed File exists
So I do a factory reset and then try again from scratch.
Is there an easier way to repeat the process?
Edit: I figured it out, just delete the file like this:
Code:
adb shell rm -r /data/install/com.att.android.markthespot.apk
Hope that's the right way of doing it.
Thank you.

I have been deleting the file from data/install
adb shell
cd data/install
rm com.att.android.markthespot.apk
exit
then repeat the process...i'm in double digits on attempts...going to have to walk away from it for a bit.

going on 10x for me and still nothing. Any suggestions?

id10terrordfw said:
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
Click to expand...
Click to collapse
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (It is 3801413 bytes as of today). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!

noobsquared said:
Thanks, but everytime I do factory reset...it comes back on?
I might be doing something dumb.
After I get permission denied error, I try to start at the process of tryping:
Code:
adb shell ln -s /data/local.prop /data/install/com.att.android.markthespot.apk
but when I do that after uninstalling AT&T Mark the spot, it gives me erorr:
link failed File exists
So I do a factory reset and then try again from scratch.
Is there an easier way to repeat the process?
Edit: I figured it out, just delete the file like this:
Code:
adb shell rm -r /data/install/com.att.android.markthespot.apk
Hope that's the right way of doing it.
Thank you.
Click to expand...
Click to collapse
Um, why are you doing a factory reset?
---------- Post added at 12:11 PM ---------- Previous post was at 12:10 PM ----------
xfinrodx said:
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (I think it was around 5MB but it's been a while). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
Click to expand...
Click to collapse
I will give that a shot, and I should have thought of that. Thanks!

xfinrodx said:
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (It is 3801413 bytes as of today). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
Click to expand...
Click to collapse
Good advice, was the first person to test it for me. I confirmed it with 4 users before posting, and all got it eventually.

id10terrordfw said:
I will give that a shot, and I should have thought of that. Thanks!
Click to expand...
Click to collapse
I was the first one I'm aware of who used this exploit a couple weeks ago. I won't claim that the process is clean, but it should work for you if you do it the way I intended the instructions to read... Good luck!

Thanks for all the help but I think this red bull is not working today.
Here is what I did:
First CMD:
Code:
adb shell
cd /data/install
ls -l <- it only gives me the file name..it doesn't tell me the size.
Also, I delete the file and run the first command in second CMD and right after that I see this in ls -l:
[email protected]:/data/install $ ls -l
ls -l
lrwxrwxrwx shell shell 2012-05-25 12:16 com.att.android.markthesp
ot.apk -> /data/local.prop
Second CMD:
Execute:
Code:
adb shell ln -s /data/local.prop /data/install/com.att.android.markthespot.apk
Wait to execute:
Code:
adb reboot

xfinrodx said:
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (I think it was around 5MB but it's been a while). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
Click to expand...
Click to collapse
Great Idea !!!.... If you could post the exact size of the file , we can probably try to script it...( I have an idea in mind as mentioned below , but not sure if it works the way I intended in android )
for Ex:
szie=`ls -l /data/install/com.att.android.markthespot.apk | awk '{print $4}'`
while [ "$szie" -lt <size-of-apk> ];do
echo "waiting......"
done
adb reboot

dharani1234 said:
Great Idea !!!.... If you could post the exact size of the file , we can probably try to script it...( I have an idea in mind as mentioned below , but not sure if it works the way I intended in android )
for Ex:
szie=`ls -l /data/install/com.att.android.markthespot.apk | awk '{print $5}'`
while [ "$szie" -lt <size-of-apk> ];do
echo "waiting......"
done
adb reboot
Click to expand...
Click to collapse
If you can get a working script, that was reliable I would love to post it in the OP. To get an idea of the size, you could install the app, and do adb shell ls -l /data/app/<filename>

[Q] How to unroot phone Atrix 2

I used the eacy one click to root phone. I would like to unroot it now. I am having touch screen freezing problem. I need to start removing applications to see which one is causing the problem or if it is a hardware issue or software.
I downloaded the zip file 1-click_exploit. I expanded the files and ran the application. I have read that there is an option to uninstall with in that file but I don't see one. Where do I find it. If I just do a factory reset will it remove it? If I do a reset do I have to repurchase all of my apps?
Thank you in advance!

A factory data reset will not remove root.
Also, a reset does not delete your purchases. They are all stored in your google account. So, if they do get deleted, just reinstall them.
As far as unrooting, I do not know. Someone else may chime in here...probably going to tell you to post in the Q&A section as well.

Doesn't the one-click have an un-root feature?
Sent from my bootloader-locked MB865.

The one click method also has an un root option in the folder.
Sent from my MB865 using xda app-developers app

Generally the only trace rooting leaves is a setuid binary "su" in /system/bin. And Superuser.apk to manage permission which apps get to invoke the binary. So unrooting involves uninstalling Superuser application and removing the su binary. If you want to do it by hand: (1) adb remount (2) adb shell (3) su (4) rm /system/bin/su

kousik said:
Generally the only trace rooting leaves is a setuid binary "su" in /system/bin. And Superuser.apk to manage permission which apps get to invoke the binary. So unrooting involves uninstalling Superuser application and removing the su binary. If you want to do it by hand: (1) adb remount (2) adb shell (3) su (4) rm /system/bin/su
Click to expand...
Click to collapse
I have no idea what the above manual steps are for. I can uninstall the application but where and how do I remove the su binary. On the phone? Please send directions for a non technical type of user.
Thank you!

MaTrixJ said:
The one click method also has an un root option in the folder.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Not sure where in the the following files in 1-click_exploit is the unroot option.I have attached a list of the files in the download.

bushbaum said:
Not sure where in the the following files in 1-click_exploit is the unroot option.I have attached a list of the files in the download.
Click to expand...
Click to collapse
Out of these files, adb.exe and .dll files are left in your windows PC. Not sure if they are deleted afterwards, if not, you can always unzip the above into a directory. You'll need the adb and the dll files.
The su and superuser.apk are two files that are pushed to your phone that provides the root functionality.
The zerg file is the exploit payload temporarily used to root your phone, and removed later by the script.
So if you have unzipped these into a directory, connect your phone via USB (make sure usb debugging is on), and run the commands
Code:
adb.exe remount
adb.exe shell
su // superuser may pop a permission request on phone screen
rm /system/bin/su
rm /system/app/Superuser.apk
exit

kousik said:
Out of these files, adb.exe and .dll files are left in your windows PC. Not sure if they are deleted afterwards, if not, you can always unzip the above into a directory. You'll need the adb and the dll files.
The su and superuser.apk are two files that are pushed to your phone that provides the root functionality.
The zerg file is the exploit payload temporarily used to root your phone, and removed later by the script.
So if you have unzipped these into a directory, connect your phone via USB (make sure usb debugging is on), and run the commands
Code:
adb.exe remount
adb.exe shell
su // superuser may pop a permission request on phone screen
rm /system/bin/wu
rm /system/app/Superuser.apk
exit
Click to expand...
Click to collapse
What mode is my usb connection? charge only? I have the phone setting usb setting on. I run the commands (using the run command in windows accessories). When I go run "adb.exe remount" the black command screen blinks on screen so then under I go to run again and entered "adb.exe shell" the run command screen opens up with [email protected]:/$ I put in "su" After I entered the command rm system/bin/wu I get a "read only error" how do I change from read only?
Sorry for all these questions but I warned you that I was not a technical user. Thanks

bushbaum said:
What mode is my usb connection? charge only? I have the phone setting usb setting on. I run the commands (using the run command in windows accessories). When I go run "adb.exe remount" the black command screen blinks on screen so then under I go to run again and entered "adb.exe shell" the run command screen opens up with [email protected]:/$ I put in "su" After I entered the command rm system/bin/wu I get a "read only error" how do I change from read only?
Sorry for all these questions but I warned you that I was not a technical user. Thanks
Click to expand...
Click to collapse
I was wondering do I have to have the elite version superuser installed to grant permission to system? I just have the free version.

bushbaum said:
What mode is my usb connection? charge only? I have the phone setting usb setting on. I run the commands (using the run command in windows accessories). When I go run "adb.exe remount" the black command screen blinks on screen so then under I go to run again and entered "adb.exe shell" the run command screen opens up with [email protected]:/$ I put in "su" After I entered the command rm system/bin/wu I get a "read only error" how do I change from read only?
Click to expand...
Click to collapse
1. yes -- charge only
2. it is better to open a command prompt -- in run commands type in "cmd" which'll give you a shell, easy to track command outputs
3. in that shell cd to the directory you unzipped and run "adb.exe remount"
4. Unless it says "remount succeeded" further operations won't succeed
5. After you execute "su" your prompt will change from $ to # ... is this happening?
6. Only on # prompt, you can do "rm /system/bin/su" ... that too only if remount succeeded
Let us know at which step it fails.

kousik said:
1. yes -- charge only
2. it is better to open a command prompt -- in run commands type in "cmd" which'll give you a shell, easy to track command outputs
3. in that shell cd to the directory you unzipped and run "adb.exe remount"
4. Unless it says "remount succeeded" further operations won't succeed
5. After you execute "su" your prompt will change from $ to # ... is this happening?
6. Only on # prompt, you can do "rm /system/bin/su" ... that too only if remount succeeded
Let us know at which step it fails.
Click to expand...
Click to collapse
I get the following error after entering the run "adb.exe remount"
*daemon not running starting it now*
*daemon started successfully*
remount failed: operation not permitted

bushbaum said:
I get the following error after entering the run "adb.exe remount"
*daemon not running starting it now*
*daemon started successfully*
remount failed: operation not permitted
Click to expand...
Click to collapse
Then try remounting manually:
Code:
C:\> adb.exe shell
edison$/ su
edison#/ mount -o remount,rw /dev/block/system /system
Afterwards proceed with rest of the script.

How to access private mode without access to screen? Galaxy S5

So, I'm an idiot and was working too close to my phone with some heavy tools. Long story short, I ended up dropping my Dewalt drill directly on the screen. It's completely ruined and no longer has any picture on the screen. The phone itself still turns on. I'm able to unlock with fingerprint, etc. The problem is...since I can't actually see anything on the screen, I'm not sure exactly where to press and swipe to access private mode. I had some files for work stored in private mode that I need to retrieve from the phone (customer contracts)...but since I can't see anything, I don't know exactly how to get them back. Any ideas? Thanks in advance!

Is adb debugging enabled on your device?

Fusseldieb said:
Is adb debugging enabled on your device?
Click to expand...
Click to collapse
I believe so, yes. I think I enabled it awhile ago.

mosesport said:
I believe so, yes. I think I enabled it awhile ago.
Click to expand...
Click to collapse
Perfect. Now you can make a .bat script that pushes a screenshot fron your device every second.
You do it in following way:
1. Create a normal text file and write in there:
Code:
:1
adb shell screencap -p /sdcard/screen.png
adb pull /sdcard/screen.png
adb shell rm /sdcard/screen.png
goto 1
2. Rename it to Screenshot.bat
3. Run it and you will see a command prompt in loop getting screenshots from your device. Then open the newly created "screen.png". If you're using Windows 7, the image will update automatically every second and you will see a 'live feed' of your device's screen.
If your touchscreen is damged too, you will need inputting keyevents, like touch x y. If that's your case, just say me and I'll explain you.
Sent from my SM-G925F using XDA-Developers mobile app

Fusseldieb said:
Perfect. Now you can make a .bat script that pushes a screenshot fron your device every second.
You do it in following way:
1. Create a normal text file and write in there:
Code:
:1
adb shell screencap -p /sdcard/screen.png
adb pull /sdcard/screen.png
adb shell rm /sdcard/screen.png
goto 1
2. Rename it to Screenshot.bat
3. Run it and you will see a command prompt in loop getting screenshots from your device. Then open the newly created "screen.png". If you're using Windows 7, the image will update automatically every second and you will see a 'live feed' of your device's screen.
If your touchscreen is damged too, you will need inputting keyevents, like touch x y. If that's your case, just say me and I'll explain you.
Sent from my SM-G925F using XDA-Developers mobile app
Click to expand...
Click to collapse
When I try to run the script, the command prompt gives an error stating "adb is not a recognized as an internal or extermal command."

mosesport said:
When I try to run the script, the command prompt gives an error stating "adb is not a recognized as an internal or extermal command."
Click to expand...
Click to collapse
Install adb on your machine, reboot and try again.
Search here on xda for "15 seconds adb and fastboot installer".
(While installing, press Y for Yes when prompting to install it system wide)
Do not forget to reboot!
Sent from my SM-G925F using XDA-Developers mobile app