yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Q&A, Help & Troubleshooting] blackpanther2209:
Flash it using odin.there's a firmware thread here in General S5 section or you can check your latest region or country's firmware in sammobile.
[Android Q&A, Help & Troubleshooting] noob adb:
okay guys i pushed + and power the the red triangle pops i went to adb devices it showed the devices on recovery mode

is there a command that i can put to wipe data? such as adb shell command
[Android Q&A, Help & Troubleshooting] MasterAwesome:
I think its

adb shell

su

mount - o remount,rw /data

rm - rf /data/*

Regards

MasterAwesome
[Galaxy Grand Duos i9082 Q&A, Help & Troubleshootin] sotsp:
Hi,

tomorrow morning Suddenly my phone can not may calls. The incoming call working fine.

For any attempt to call, the phone disconnects and prompts me again sim pin. I have stock rom 4.2.2 rooted.

Please help
[Galaxy Grand Duos i9082 Q&A, Help & Troubleshootin] jackeagle:
Hello...:)

If its asking for SIM pin then possibly you have activated SIM lock feature which prompts the PIN when SIM is put in other phone...Just put the pin and See....:) Also Check If IMEI no is displayed correctly by pressing *#06#...:)
[Galaxy Grand Duos i9082 Q&A, Help & Troubleshootin] sotsp:
I have not activate sim lock. Put the pin after i try call but disconnected. The IMEI displayed correctly
[AT&T Samsung Galaxy S II SGH-I777] mmystere68:
I wanted to know whether the i777 battery is compatible with the the i9100 and vice versa.
[AT&T Samsung Galaxy S II SGH-I777] SteveMurphy:
You'll lose NFC, as the 9100 doesn't support it, and you may have random reboots from time to time... but it will sort-of work. In the "old" days (I'm sure it still persists), charging the 9100 battery inside an i777 sometimes wouldn't work, so just be aware of these potential issues.

These were my experiences with it 2 years ago (on the i777 side, can't speak to the 9100), and while there are some around here who will say they ARE compatible, they're not really.

One other thing, please search next time before posting - these threads are all over this forum and have been answered/debated for 2 1/2 years.
[AT&T Samsung Galaxy S II SGH-I777] mmystere68:
I just got two spare extended batteries for my i777 and i dont know what to do with them....most people here uses the international i9100 s2.....can i sell the i777 batteries to them?? Will it work on their i9100?
[AT&T Samsung Galaxy S II SGH-I777] SteveMurphy:
Sorry, no idea. Perhaps someone who knows will chime in.
[AT&T Samsung Galaxy S II SGH-I777] mmystere68:
it is compatible!!

Sold one to my friend about 2-3 months ago and it is running fine. No problem whatsoever.
[Android Software Development] E:V:A:
Some SELinux / SEAndroid related issues

< WIP: may contain inaccuracies! >

So you're rooted and you hope to use SSH to get a root shell,

like in the good old days (yesterday), and now you've got trouble!

Thanks to Godzilla and Samsung, we now have to deal with something called

SEAndroid which stands for "Security Enchanced Linux (SEL) for Android".

This would not have been so bad, if it wasn't because these companies now

want to enable the very strict Enforcing mode, by default.

That means that nothing you're once used to, when you have root access,

works and behaves as expected. In fact SEL restricts root user, just like

any other, so you have to spend some weeks trying to understand how that

is dealt with and managed from a Super-User's perspective.

So trying to get a root shell from an SSH session, is now likely to fail

because:

You have a Samsung KNOX enabled device. Samsung KNOX is deeply intertwined with SEL.

==> Remove all KNOX garbage.

Your SEL policy is not allowing SSHelper to allocate a pseudo-terminal (/dev/ptmx ) beacuse the /dev/pts directory is mounted as RO as type /devpts.

==> remount /dev/pts to enable RW: mount -o remount,rw -t devpts /dev/pts

Your SEL policy is still not allowing you to su from outside SE context "init_shell".

==> Temporarily set SEL to Permissive mode with: su 0 setenforce 0

Your SEL policy is not allowing you to ... period.

==> Unless you have a locked bootloader, disable SEL by flashing an insecure kernel/ROM that either doesn't have SEL, or at least not in Enforcing mode.

su is not working because:

a) your AOS version is not handling SEL policies right.

b) your su version is not handling SEL contexts right.

You got fooled into buying a locked Verizon or ATT phone with locked boot loader, and no way of rooting, and no one can help you. You cannot do any development with such a phone.

==> Return phone and cancel your contract.

< TBA >

The mksh Shell

< WIP >

The MirBSD™ Korn Shell, is better known as mksh and is now the default

shell on Androids since JB 4.1, instead of ash. I don't know why this

change was made, but I suspect it has something to do with having much

better documentation, better linux community support and therefore more

features and better compatibility.

The current available mksh version is:

R49 (11 Jan 2014)

NOTE: This is the sources version and is not necessarily available as

an Android binary, unless you compile your own. (Please share it here!)

You can check your own Android mksh version with:

[SIZE=2]u0_a202@MSM8960:home $ echo $KSH_VERSION[/SIZE]
[SIZE=2] @(#)MIRBSD KSH [B][COLOR=Red]R40[/COLOR] 2011/10/07[/B][/SIZE]
[SIZE=2] [/SIZE]

The complete online man pages for mksh is found HERE.

The mksh ChangeLog is HERE.

The latest mksh sources are available HERE.

The latest statically linked ARM Android binary can be downloaded HERE.​
[Android Software Development] E:V:A:
< Here be more Dragons 3 >
[Android Software Development] E:V:A:
So after having updated SuperSU from 1.94 to 2.00, I've suddenly got some different SELinux errors in the AVC log, but did not resolve the issue. This partially confirm that this is a combined App + SELinux issue, due to several factors:

1) App is not performing the SU operation according to current (latest AOSP) standards. For example, from THIS issue on Stackoverflow, apparently AOS >4.3 (or more likely those using SELinux 4.2.2) are no longer using setuid(), and if you still wanna use it, it is suggested to do a fork() before. In addition su has to be made in the right context.

2) According to THIS article, SU is no longer allowed to execute files on the /data partition, although there are some workarounds. Please read Chainfire's blog about how to SU, for latest developments, and workarounds.

3) The current SELinux policy is restricting the use of /dev/pts|ptm|pty and the mounted devpts FS. Most likely some of the policy/behavior is wrong.

Useful links:

http://su.chainfire.eu/

http://www.xda-developers.com/andro...ak-compatibility-with-many-current-root-apps/

http://www.xda-developers.com/andro...he-android-l-developer-preview-the-right-way/
[Android Software Development] E:V:A:
Another possible reason for this issue, could be that since AOS 4.3 (and possibly some 4.2.2 in Enforcing) versions, the WRITE_EXTERNAL_STORAGE permissions in /system/etc/permissions/platform.xml have been changed to a much more restrictive setting, where Apps can ONLY write to their own directory. For a good description of the problem and solution:

[APP][4.4][ROOT] SDFix: Modify device permissions to allow apps to write to MicroSD

http://xdaforums.com/showthread.php?t=2684188

https://plus.google.com/+TodLiebeck/posts/gjnmuaDM8sn

This need to be checked.

=========================== EDIT =====================

On 4.2.2 Enforcing, we have:

[SIZE=2]...
<permission name="android.permission.READ_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
</permission>

<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
...[/SIZE]

This seem OK, but perhaps SSHelper also need to set its GID to "sdcard_rw"?

Because on KK 4.4.2b4 we have:

[SIZE=2] <permission name="android.permission.READ_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
[COLOR=Red][B]<group gid="media_rw" />[/B][/COLOR]
</permission>

<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
[COLOR=Red][B]<group gid="sdcard_r" />[/B][/COLOR]
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>

<permission name="android.permission.ACCESS_ALL_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="sdcard_all" />
</permission>

<permission name="android.permission.WRITE_MEDIA_STORAGE" >
<group gid="media_rw" />
</permission>
[/SIZE]

Looking at the permissions in our AndroidManifest.xml file, and compare that to issue#315 in Android-Terminal-Emulator, it could that we also need to add the READ_EXTERNAL_STORAGE permission, which is not present in our manifest, and contrary to what Google said about WRITE_EXTERNAL_STORAGE as automatically including READ_ access.

To help troubleshoot permission problems when running on an AOS with enabled SELinux (>4.2.2), please provide the output of the following commands:

getprop |grep "ro.build.*"
getenforce
cat /data/misc/audit/audit.log
[Android Software Development] E:V:A:
I have now found a work-around for the lost terminal job-control.

It's originally described in detail HERE.

---

EDIT: (Added 2014-11-23)

I've finally found a work-around for the crippled /dev/pts job-control and su combination. There are two small problems that combines to this issue.

1. The SELinux policy is screwed up by Samsung. And others?

2. The /dev/pts is mounted wrong by default.

The work-around:

Make sure you're device is already in Enforcing mode, so that you get the proper su prompt (#).

1. Open terminal session 1.

[SIZE=2]
## On Terminal 1
ssh -2 dummy@192.168... -p 2222
$ su -c /system/bin/sh -i
# su 0 setenforce 0
# umount /dev/pts
# su -cn u:r:init:s0 -c "busybox mount -t devpts -o rw,seclabel,relatime,mode=620,gid=5 devpts /dev/pts"[/SIZE]

2. Now go to Terminal 2 and login:

[SIZE=2]## On terminal 2
ssh -2 dummy@192.168... -p 2222
$
[/SIZE]

(You now have job-control but no su possibility.)

3. Now go back to Terminal 1 and enable Enforcing mode:

[SIZE=2]## On Terminal 1
# su 0 setenforce 1
[/SIZE]

4. Now go back to Terminal 2 and escalate to su:

[SIZE=2]## On terminal 2
$ su -c /system/bin/sh -i
# [/SIZE]

Unfortunately if you exit the su (#) shell, you'll have to repeat steps 2-4 of the procedure.
[Android Software Development] zelch:
Any progress on a pty for lollipop users?

So now that Lollipop has landed, is there any progress on getting a pty for Lollipop users?

Ideally something that can work with something not too far from stock.
[Android Software Development] E:V:A:
Are you actually having any issues? Please post what. I've used this on a KK 4.4.4 MTK device, using SuperSU 2.16, and there are no problems with this on that device.
[Android Software Development] zelch:
In short, yes.

Currently on stack (unrooted) Lollipop on a Nexus 7 (2013), and while the ssh server works it can not allocate a pty, resulting in the shell not being all that usable.

While I expect that rooting will be a requirement to adjust things, I would rather avoid the option of completely disabiling selinux enforcement.

(Yes, it's a quick and easy way to solve the problem. But the selinux enforcement buys quite a lot in the way of security, so I'd rather limit things to say, a tweaked selinux policy.)
[Android Software Development] Deleted member 230392:
Okay noob question .... My rooted Nexus 5, with sshelper installed, changed listening port to 3333, set a new password

Logon from Windows server with putty gives ...

login as: admin

SSHelper Version 6.8 Copyright 2014, P. Lutus

admin@192.168.2.205's password:

Server refused to allocate pty

sh: /data/data/com.arachnoid.sshelper/home/.profile[2]: uname: not found

What cretinous thing have I omitted to notice?

Regards Marcus
[Android Software Development] dd043:
I've been running your app for a few days with good results, thank you for that!

Would it be possible to implement a wifi lock only when there is a client connected? Wifi lock all the time is killing my battery and my standby wifi seems to be responsive enough to receive incoming connections (often after 2 or 3 attempts, but it still eventually works)
[Android Software Development] E:V:A:
First of all let me clarify that I am not the developer and maintainer of this App. It is Paul Lutus, and you can message him on his website. I only started this thread to help him out and to help myself of having a place to post problems. I really like his app, but THESE are really annoying issues, and has proably nothing to do with his app but with the screwed up way that Google is changing device permissions.

The only solution I know about for problem devices is something like I re-posted in edited post #8:

http://xdaforums.com/showpost.php?p=55779472&postcount=8

Good Luck.
[Android Software Development] jumika:
Hi!

Is it possible to start sftp session as root user? If i try to reach /data for example i get permission denied error :( In terminal i must type su to gain root rights.

Thank you!
[Android Software Development] bdexyxjd:
I would like to know this as well.
[Android Software Development] samandiriel:
Having a problem with SFTP ssh process almost immediately disconnecting. I get messages from my file manager (caja) such as "The connection is closed (the underlying SSH process exited)". This wasn't a problem until I did a factory reset on my OnePlus 5 and upgrade it to Oreo (8.1)

How can I keep the connection alive? I tried a keep alive ping on the PC side by editing SSH config files, but that was a bust.
[Android Software Development] stormy1777:
How to run SSHelper from CLI/ADB - failed Phone's LCD/Screen

Hi everyone :)

Trying to start SSH helper on a phone with a defective screen :)

It is already installed, but not running... tried this:

root@BLU:/data/app # am start com.arachnoid.sshelper

Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER]pkg=com.arachnoid.sshelper }

Error: Activity not started, unable to resolve Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 pkg=com.arachnoid.sshelper }

and many other creative combinations I somehow got from online searches:

# am start com.arachnoid.sshelper/android.intent.action.MAIN

it fails:

start com.arachnoid.sshelper/android.intent.action.MAIN <
Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.L
AUNCHER] cmp=com.arachnoid.sshelper/android.intent.action.MAIN }
Error type 3
Error: Activity class {com.arachnoid.sshelper/android.intent.action.MAIN} does not exist.

This directory exists:

root@BLU:/data/app # ls -ld *arach*
drwxr-xr-x system system 2018-08-07 21:00 com.arachnoid.sshelper-2

maybe the "-2" needs to be accounted for somehow in the command to start?

pages like: http://learnandroid.blogspot.com/2008/01/run-android-application-from-command.html

says how to construct an "am start" command, but it requires info from the Manifest, except the file AndroidManifest.xml found in the ssh helper.apk seems binary

Until I get this working ADB is the only way to connect to the phone, it's rather limited in its abilities... like, no scp :)

C:\Android>adb shell
shell@BLU:/ $ su
root@BLU:/ # scp
tmp-mksh: scp: not found

Any tips on how to start SSH Helper, maybe someone has the text Manifest xml file?

Stormy.
[Android Software Development] measel:
Terrible rsync transfer rates

I'm having trouble with transfer rates using rsync.

I use rsync to backup my phone to my computer but the transfer rates are always below 700kB/s which is unbearable.

My specs:

Phone: Samsung S9, rooted with custom rom.

Computer: MacOS 10.14.6

I had the same problem with SSHDroid but maybe some of you have an idea how to tackle this, or confirm the slow transfer speed.

By the way: When uploading music to my phone it is faster with 1.4MB/s (still not super great).
[Nook Touch General] wraq:
I'm owner a Nook'a Simple Touch. It is rooted, registered, and has firmawe version 1.2.1. I would like to connect it with eduroam. I downloaded the certificates (different types: .crt, .pem, .der) but I have no idea how install them (re-launcher). In Settings => Wireless => Add other network, I was able to set the network name SSID, security system, a username and password. But it's not enough. Maybe someone would have any advice for me?

This solution for the Kindle (Maybe something similar can be done with Nook?)

google: amazon-kindle-and-eduroam
[Nook Touch General] cowbutt:
I think I was able to just use 802.1x without installing the certificate.
[iPAQ rw6828, XDA Atom General] hsanghavi:
Does Anyone have tweaks from any forum which will stop all running programs once they are closed. As if we forget the stop them through Memory> Running Programs> Stop. If there is a tweak and we put it in the registry for good then we can get good speed of the PPC and also use minimum battery. If we forget the battery gets worn in 6 to 8 hours only. If not minimum 12 hours max 18 hrs.

Please reply if someone knows anything in any forum to support this.
[iPAQ rw6828, XDA Atom General] momopopode:
sbp pocketplus is the key :wink:
[iPAQ rw6828, XDA Atom General] kropotov:
O2+
[iPAQ rw6828, XDA Atom General] olsemwanem:
spb pocketplus is by far the best program you can get for a windows mobile device. it allows you to close programs with the close button as well as navigate through the open programs by "shift clicking" the close button.

no windows mobile user should be without any/all of the spb programs. spb makes windows mobile run how it should and microsoft should pull their fingers out and upgrade windows mobile to incorporate spb features. as usual though microsoft is happy to sell us second rate under finished products.
[iPAQ rw6828, XDA Atom General] kropotov:
spb isn't the best. it's "eat" too much memory and too slow. maby you don't know other programs, for example ilouncher, magic button etc.?
[iPAQ rw6828, XDA Atom General] taiseer999:
Agree, iLauncher is the best, have had on my Atom for the last 2 weeks, device is faster, and power consumption is reduced a great deal
[iPAQ rw6828, XDA Atom General] twins69:
can you tell me where i found ilauncher or you taiseer999 get me to link
[iPAQ rw6828, XDA Atom General] taiseer999:
Google for it

http://www.sbsh.net/products/ilauncher/

screen shot
[iPAQ rw6828, XDA Atom General] twins69:
we met again tseer999

that is trial can you give me the full thanks alot
[iPAQ rw6828, XDA Atom General] victoradjei:
Are you asking for crack******?!!!!
[iPAQ rw6828, XDA Atom General] R. Knops:
It is possible to uninstall some pocket plus components you don't use. I strip it down to the componentes I often use !

A good combination is dinarsoft handyswitcher, batti and mcube safemode.
[iPAQ rw6828, XDA Atom General] kropotov:
no it's impossible. only "all in one bottle"
[iPAQ rw6828, XDA Atom General] twins69:
he...he...

he..he...if you have radja........
[T-Mobile Samsung Galaxy Note 3] nofroyo:
Hi,

I was wondering which international roms of N3 will work on the tmobile variant N900T?
[T-Mobile Samsung Galaxy Note 3] mdiaz33685:
N9005 roms work, but some of them, NFC will not work, others have a Wifi problem also, unless you download from a develop that has fixed those issues... I have stock roms, look on my signature, all my Stock roms, have NFC issues... and MMS is set to 300mb

goto the Development thread and look to see who has them fixed,
[T-Mobile Samsung Galaxy Note 3] nobrakes:
I'm on the stock ne3 intl rom and everything is working. Go to the thread by zedomax for flashing intl roms. I'm using the stock t-mobile ne6 kernel. I did the edit that jovy wrote in the thread to fix WiFi after I flashed the nfc fix

http://xdaforums.com/showthread.php?p=52987809
[T-Mobile Samsung Galaxy Note 3] nofroyo:
Thanks for the info, i appreciate it
[Verizon Samsung Galaxy S 4] B. J.:
I dropped my phone in the ocean but the flash light was on so I swam down and got it back. I took the battery out and put it in rice but it still wouldn't turn on. So I took it apart and cleaned all the salt out of it and put it back together. Now it works but it still has some issues with the touch screen functioning and for some reason the LED light stays on. Even when the phone is turned off and off the charger and it doesn't change colors for notifications any more. Could I have hooked it back up wrong some how ? Does it matter ie affect anything else/ indicate other problems? Thanks so much for any help you can offer. :)?
[Verizon Samsung Galaxy S 4] Mistertac:
I'm going to go out on a limb and say it's because it took a swim in the ocean [emoji16]

I dropped my RAZR into a pool and was never the same again. It worked but just acted.. Well like it got wet. Not sure if anyone will be able to give you definate answers. Could look again at the connections I suppose.
[LG Optimus G (International)] shirish893:
PROBLEM:

Subsystem Crash!

-----------------------------------------------------------------------------------------------------------------

DemiGod Crash Handler : Subsystem Crash! : External_modem (Undefined error)

Press key to choose Dload Mode/Reboot/Fastboot

1)Volume Up: Dload Mode.

2) Volume Down: Reboot.

3) Power: Fastboot.

If you choose Dload Mode,

Please do following action.

1)Dload Mode. Please connect USB

2) Get the ram dump image using QCT's Memory Debug App

3) Send em-mail to contact point or M-TDR-Leader@lge.com.

-------------------------------------------------------------------------------------------------------

When i flash my rom(s) the above problem arises after boot. Tried with pacman ,carbon and pa. All same problem.

Any solution guys?

Thanx

EDIT: When i remove my sim card, it boots normally
[LG Optimus G (International)] hackenggr:
Hey,

They are two ways to fix this, first flash the modem in TWRP (Never tried this my self so not so sure it works or not) described the same problem in this thread study it if it help you [Guide]Restore to Stock "Bricked" "Unlocked" LG Optimus G f180,E97x

Second as I told you earlier go back to total stock try the KDZ updater for that if it gives error then flashing the tot file through LGNPST, you will be able to flash any desire stock KDZ after that via R&D Tool or use the first method to unlock the bootloader in above thread and then flash any custom rom you desire.

If you do go to original stock of your rom remember to backup the modem and EFS partition (if not already did, they contain your IMEI incase anything else go wrong) and copy them to safe place in computer or cloud.
[LG Optimus G (International)] shirish893:
r and d tool saying that my battery level is low... but my batter is 100% charged... dunno what is happening... i am going to try tot file
[LG Optimus G (International)] metrixx02:
My friend it is kernel isiue And some nexus 4 phones have it. İ go unlock my phone and i use it normaly 3 mounth And go another phone operator and i have ur isuee :( i cant use any custom ROM .but i go cwm recovery go back (restore my stock ROM un cwm) but i m not have any problem.i back to stock ROM for kdz methot And i m w8 İng KitKat .i go for big search and spend 20 h ....i have one methot .i m not test it but u cant test it and say me test results .d İF u want it say me i give link for u .d it is small kernel problem .d
[LG Optimus G (International)] shirish893:
I got the solution.. I flashed modem.img by fastboot... And it worked :D
[LG Optimus G (International)] metrixx02:
How modem.img where u found it?
[Zooper Widget General] RebelwithoutaClue:
I created several Zooper widgets and saved them using autosave. But I want to merge 2 widgets into 1 without having to manually enter every module. I can't use the file open options, since it will overwrite previous entries. Is there a way to merge 2 widgets in an easy way?
[Zooper Widget General] masze:
no, there is no easy way.
[Zooper Widget General] RebelwithoutaClue:
Crap! Guess I have to do it the hard way than. Thanks
[Zooper Widget General] jirka81:
I don't know if I understand the question, but did you try download widgets (templates) to PC (file extension is zw, but it is regular zip file) and merge it's content, upload it back to the phone (to the same directory) and then open it?

sorry for my english ;)