[Q] Android Terminal Emulator su prompt disappeared - Asus Transformer TF700

This is the second time this has happened and I'm not sure how I fixed it before. Basically the prompt is normal when you enter the terminal, but after calling "su" the prompt user info completely disappears. It used to show "[email protected]:/ #" and now it just shows a blinking cursor.
Anyone had this happen or have a fix for this behavior? I uninstalled/reinstalled both terminal and superSU and it didn't fix it. But I did not clear any app data. This happened right after I changed the superSU app logging settings and cleared out its old app logs.

Related

Charge Hot Rebooting

Hello,
Today is my 14th day with the device and this device seems to be hot rebooting itself. Its not a complete reboot but a hot reboot that take 1/3rd the time to start up. Attached is the Alogcat. Anyone have any ideas? Should I swap the device out?
There is no reason for a reboot. I am not running any applications at time of reboot. And it happens randomly.
I didn't see anything in the logcat showing what the problem was. It looked like alogcat didn't pull everything, or maybe something got lost when it hot booted. Could you try to get a logcat via adb if it happens again?
Code:
adb logcat > logcat.txt
Run the above and wait a little bit (10-15 sec) and then press ctrl+c to stop as it will just keep outputting the log to the file.
now i notice that only 3 apps are showing in my downloads in the market and i have around 20 downloaded applications. what can cause this?
do you use any app2sd+ technique (script, application, ...) ?
this happened to me in one ROM it was app2sd+, specially when i install/uninstall any app
or if i mount the sdcard as drive.
i do not all apps are installed on the phone internal memory.
after installing a new app all my apps showed back up in the market.
Its your setcpu. No profiles
Sent from my SCH-I510 using XDA Premium App
papi92 said:
Its your setcpu. No profiles
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
i dont have setcpu installed on this device. have not done that yet

[Q] Disabled app. Now phone won't work

Hey. I seem to have a problem with my phone.
Last night I was playing with my Sensation XE, and noticed that there was an app called "Wallpaper" taking up 60mb of memory, which was the biggest app at the time. I closed this app, and everything was fine, but it appeared again later. This time I cautiously disabled the app, and then checked that my wallpaper was still working OK, and I changed it a few times to make sure that was fine still, then carried on playing some games, and everything was peachy.
However, this morning I unlocked my screen to find a black screen where my phone used to be. The status bar at the top is there, and still works fine, and can be pulled down showing notifications, but even clicking on those notifications does not bring up the associated app onto the black screen below. Accessing the settings menu via the status bar also does not work, although it appears to open somewhere, as it appears in the recently used apps on the status bar menu.
Does anyone have any suggestions how I can re-enable this wallpaper app? Or any way to recover my phone? I have a previous backup from 1 month ago. Can the system state be recovered from that?
Thanks in advance for any help.
HTC Sensation XE
Flashed with Android Revolution HD 6.5.5
possible solution
hmmmm. have you used a task killer to keep the app disabled??
you could try to use adb ro remove the app entirely, and then use adb to reinstall it followed by a reboot. best make a full backup though incase it goes tits up. worst comes to worst do a backup of your rom, wipe and start fresh and reinstall apps from the backup.( i think thats possible )
heavy_metal_man said:
hmmmm. have you used a task killer to keep the app disabled??
you could try to use adb ro remove the app entirely, and then use adb to reinstall it followed by a reboot. best make a full backup though incase it goes tits up. worst comes to worst do a backup of your rom, wipe and start fresh and reinstall apps from the backup.( i think thats possible )
Click to expand...
Click to collapse
Thanks for the quick reply!
I haven't used a task killer for the disabling. I disabled it in the system page for the app. Where it usually has Force Stop, Uninstall, Clear Data etc. The uninstall option had changed to Disable.
I have used adb a couple of times in the past, but not extensively. Any chance you could run through the commands required?
al090187 said:
Thanks for the quick reply!
I haven't used a task killer for the disabling. I disabled it in the system page for the app. Where it usually has Force Stop, Uninstall, Clear Data etc. The uninstall option had changed to Disable.
I have used adb a couple of times in the past, but not extensively. Any chance you could run through the commands required?
Click to expand...
Click to collapse
I think the best thing for you to do would be plug into computer with usb debugging enabled.
Then run "adb reboot recovery"
from there reflash your ROM (a full wipe shouldnt be necessary)
then reboot and you should be good
Fixed
After many hours trawling google to try and find an answer, I finally found something.
http://forum.xda-developers.com/archive/index.php/t-1151150.html
I had no idea what the disabled app name was though, so I used the following to list the disabled packages.
Code:
pm list packages -d
The command needed to enable the apps was
Code:
pm enable APPNAME
Did a restart, and now everything seems fine again. That's possibly the last time I play with things on my phone.... Or maybe not.
Thanks for your help and time =]
Edit: Just to let anyone know, these commands are performed using a remote shell interactively through adb.
glad you got sorted buddy, and thats handy to know!

[Q] Missing write access?

Got my OPO yesterday, very happy with it, rooted and got Xposed in the first 20 minutes after updating as I have with all my Android devices. Unfortunately I noticed a few problems today.
File manager won't let me move, copy, or create files. It seems to be fine with deleting, but trying any of the former yields a "Requires elevated permission (root)" despite the fact that I have already set File Manager to rooted mode and granted it permission in SuperSU. Other file managers yield the same result.
I can't take screenshots, or let other apps take screenshots. Stock screenshot will give me a notification saying "Couldn't save, storage in use."
Similarly, Snapchat and Keepchat won't let me save my own or others' snaps.
I can restore Helium backups, but I can't create a backup. Made sure Helium has the proper permissions too.
I'm pretty sure this isn't app-related or root-related, but rather something preventing me from writing to /storage/emulated/legacy.
Things I've tried (to no avail):
Fixing permissions in TWRP
Unrooting
Uninstalling Xposed
Factory resetting
Searching for a fix on XDA and the OPO forums, all of which have led me to try the former three solutions which failed.
Also completely unrelated, but sometimes pressing the lock button won't wake my device; the hardware buttons glow as if the device is on, but nothing happens after that and the device won't wake up so I have to reboot. This is a somewhat rare problem however.
Any ideas for either problem? Thanks in advance.

Accessibility Settings Crashes

I "upgraded" to Android 11 and, among the myriad of other issues, I can't open accessibility settings at all. The ROM is stock, not rooted, and opening the accessibility app via the app info screen with the button in the bottom left pulls up a full screen notification that vibrates my phone telling me it detected a baby crying. Accessibility settings don't work at all.
Is anyone else experiencing this? Is there anything I can do that isn't a factory reset in order to fix this? I tried restarting to safe mode and the behavior doesn't change.
WiggleCat said:
I "upgraded" to Android 11 and, among the myriad of other issues, I can't open accessibility settings at all. The ROM is stock, not rooted, and opening the accessibility app via the app info screen with the button in the bottom left pulls up a full screen notification that vibrates my phone telling me it detected a baby crying. Accessibility settings don't work at all.
Is anyone else experiencing this? Is there anything I can do that isn't a factory reset in order to fix this? I tried restarting to safe mode and the behavior doesn't change.
Click to expand...
Click to collapse
Prior to your andoid 11 upgrade did you use adb to remove anything?
Limeybastard said:
Prior to your andoid 11 upgrade did you use adb to remove anything?
Click to expand...
Click to collapse
Yes, and the accessibility settings were working fine afterwards. I uninstalled things llke Chrome, Facebook services, and the default Samsung browser to name a few. I didn't full on debloat the phone, I only removed things that were actually bloatware I'd never used in the past and won't use in the future. And Facebook. If it matters, I have the unlocked variant of the N20U.
Edit: My next move was going to be pulling up a list of packages somehow that tells me which are installed for user 0 and which aren't to see where the problem lies. But again, I only uninstalled the obvious bloatware such as browsers that other apps would open over my default. Various background services, fonts, themes, etc that are just there but don't use resources, such as the car mode stuff I know I'll never use, was left alone.
WiggleCat said:
Yes, and the accessibility settings were working fine afterwards. I uninstalled things llke Chrome, Facebook services, and the default Samsung browser to name a few. I didn't full on debloat the phone, I only removed things that were actually bloatware I'd never used in the past and won't use in the future. And Facebook. If it matters, I have the unlocked variant of the N20U.
Edit: My next move was going to be pulling up a list of packages somehow that tells me which are installed for user 0 and which aren't to see where the problem lies. But again, I only uninstalled the obvious bloatware such as browsers that other apps would open over my default. Various background services, fonts, themes, etc that are just there but don't use resources, such as the car mode stuff I know I'll never use, was left alone.
Click to expand...
Click to collapse
The reason I mentioned this was because I had a similar issue whereby selecting accessibility within the settings menu would result in null,meaning nothing would happen. If memory serves me correctly it was related to samsung keyboard that I had removed, but can't be sure. But I believe you're on the right track to figure it out.
Limeybastard said:
The reason I mentioned this was because I had a similar issue whereby selecting accessibility within the settings menu would result in null,meaning nothing would happen. If memory serves me correctly it was related to samsung keyboard that I had removed, but can't be sure. But I believe you're on the right track to figure it out.
Click to expand...
Click to collapse
I did disable the Samsung keyboard. That could be it. I'll give that a go when I get a chance.
Limeybastard said:
The reason I mentioned this was because I had a similar issue whereby selecting accessibility within the settings menu would result in null,meaning nothing would happen. If memory serves me correctly it was related to samsung keyboard that I had removed, but can't be sure. But I believe you're on the right track to figure it out.
Click to expand...
Click to collapse
That was it. It was the Samsung keyboard. What a weird outcome for disabling something so trivial. I was trying to reinstall it with the old package name com.sec.android.inputmethod and it took me a while to figure out it is now called com.samsung.android.honeyboard. But once I reinstalled that for user 0 accessibility settings started working again. Thanks for the tip! I guess I'll have to leave that installed then.
WiggleCat said:
That was it. It was the Samsung keyboard. What a weird outcome for disabling something so trivial. I was trying to reinstall it with the old package name com.sec.android.inputmethod and it took me a while to figure out it is now called com.samsung.android.honeyboard. But once I reinstalled that for user 0 accessibility settings started working again. Thanks for the tip! I guess I'll have to leave that installed then.
Click to expand...
Click to collapse
Glad it helped. It puzzled me originally also., Found it in the end by backtracking on all the apps I'd uninstalled via adb one by one.
Im having the same problem, how you guys solve this cant install the apk and look like on my case adb is not picking up my ui 3.0 s20+ maybe a complete wipe (which im trying to avoid) thanks in advance
Limeybastard said:
The reason I mentioned this was because I had a similar issue whereby selecting accessibility within the settings menu would result in null,meaning nothing would happen. If memory serves me correctly it was related to samsung keyboard that I had removed, but can't be sure. But I believe you're on the right track to figure it out.
Click to expand...
Click to collapse
Made an account just to say thank you so much for this. This was the perfect fix for me and I can use half of my apps again since I can use the accessibility app now. Never expected a keyboard uninstallation to scuff half of my apps.
WiggleCat as well for the honeyboard package name.
For anyone needing an easy copy paste into command prompt, it's:
adb shell
cmd package install-existing com.samsung.android.honeyboard
User1038572 said:
Made an account just to say thank you so much for this. This was the perfect fix for me and I can use half of my apps again since I can use the accessibility app now. Never expected a keyboard uninstallation to scuff half of my apps.
WiggleCat as well for the honeyboard package name.
For anyone needing an easy copy paste into command prompt, it's:
adb shell
cmd package install-existing com.samsung.android.honeyboard
Click to expand...
Click to collapse
My pleasure. Enjoy your stay here. Some nice folks.
User1038572 said:
Made an account just to say thank you so much for this. This was the perfect fix for me and I can use half of my apps again since I can use the accessibility app now. Never expected a keyboard uninstallation to scuff half of my apps.
WiggleCat as well for the honeyboard package name.
For anyone needing an easy copy paste into command prompt, it's:
adb shell
cmd package install-existing com.samsung.android.honeyboard
Click to expand...
Click to collapse
Thanks for the command. It fixed it for me!
Wow, i fixed successful, thanks thread.
Awesome the command fixed this issue on my S20 FE. Thanks so much for sharing!
Damn! that went smoothly. Accessibility fixed after reinstalling the Samsung keyboard. Anyways if someone still doesn't want that annoying keyboard shown, you can disable it via ADB. The command is
adb shell pm disable-user --user 0 com.samsung.android.honeyboard
Thank you for pointing out that the Samsung Keyboard was the issue.
For those of you without immediate access to ADB, you can also redownload the
Samsung Keyboard via the Galaxy Store.
WiggleCat said:
That was it. It was the Samsung keyboard. What a weird outcome for disabling something so trivial. I was trying to reinstall it with the old package name com.sec.android.inputmethod and it took me a while to figure out it is now called com.samsung.android.honeyboard. But once I reinstalled that for user 0 accessibility settings started working again. Thanks for the tip! I guess I'll have to leave that installed then.
Click to expand...
Click to collapse
This saved me by inches from factory resetting my phone. However not long enough to save my whole Macrodroid macros library that i had already uninstalled because it was no longer working since it depends on accessibility services and i was desperate to get a solution. However, i have learnt a big lesson that debloating need to be done carefully if not at all. some apps are critical bindles of other critical functions

Fxtec Pro1 SystemUI keeps stopping, lockscreen loop, adb available, Signal Backup

After the battery ran out my Fxtec Pro1 stock Android (rooted) is in a lockscreen loop: I enter my PIN, the screen turns black and then it's back to the lockscreen.
Occasionally it manages to go a step further and show a dialogue "SystemUI keeps stopping". Any touch event or keyboard event returns it to the lockscreen. The same behaviour happens in Safe Mode.
I have debugging enabled and adb authorized, I have TitaniumBackup and was able to pull the TitaniumBackup files, as well as the internal storage. So mostly everything is good, except that I'd like to get a backup of my Signal Messenger chat history.
My questions:
1) What are my options to rescue my phone without needing to flash and install everything again? (Just asking in case I overlooked any options here, that would be the easiest to just fix the "SystemUI keeps stopping")
2) The Signal Messenger backup thing is strange: I have it in signal enabled, afaik it should run daily, but the folder "sdcard/Signal" is empty (at least according to adb).
3) With `am start -n com.termux/.HomeActivity` I can start things, I also see that they are started, but then I can't do `input text` to actually do something. What are my options from adb? Can I send inputs directly to an app starting?
4) Incoming phone calls work, so I am wondering: Could I create an app that runs in front of the lock screen, ideally sth like Termux, then I could do everything?
5) Maybe any chance to install and run an ssh client? Ideally in termux, because it already has su rights.
Thanks a lot for your help!

Categories

Resources