I have a Japanese Sharp 005SH Android phone. Currently, the phone had been locked up at the start screen due to the phone being out of network service for a long time.
I have rooted the phone before, and have SuperUser installed.
Currently, I am trying to get rid of the screen-lock service by the publisher by using the command "adb shell am start -a android.intent.action.DELETE -d jp.co.sharp.android.secure.StrongBox"
The problem now is. whenever I enter adb shell, the prompt is $ sign. When I type "su", nothing happens, and the cursor just blinks. I guess that this means the SuperUser app on the android phone has come out with a prompt which I need to touch to grant access. However, this is not possible as the screen is locked by the aforementioned publisher service.
Question
1. Is it possible to gain root access through ADB with the device screen locked?
2. Is it possible to remove the publisher's service without root access (and with the screen locked)?
Thank you for your time in reading this post.
Warmest Regards
Related
Hi all,
I'm trying hard to bypass the 'no sim card' locked screen that I am currently getting on my G1 Android Dev Phone 1 RC29 that I recently installed DREAIMG.nbh on. Ideally, I would like to run the android scripting environment on my phone with wireless access.
So far, my primary document that I've used to consult this matter has been this one from JesusFreke: forum.xda-developers.com/showthread.php?t=452316.
The first thing the document suggests is, "to connect to your phone with adb shell and get root access, and then type the following command:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO system (name, value) VALUES ('device_provisioned', 1);"
When I run this command, I get a 'sqlite3: permission denied' error (see below).
3.bp.blogspot.com/_scN4BTBqXiY/S-dOBTo8LiI/AAAAAAAAAfU/rtmnXywBPzI/s1600/sqlite3+permission+denied1.jpg
I recognize now that the assumption with this command is that your phone is running on RC30, as the article notes. Mine is running on RC29. In order to make this command functional, it appears as though I need to ADB push the busybox binary.
As you can see in the image above, I was able to successfully adb push the busybox binary to the /data/local of the G1.
Furthermore, I ran the wireless command in step two of the above tutorial just to see what would happen and I get this message:
3.bp.blogspot.com/_scN4BTBqXiY/S-dMU3sO2-I/AAAAAAAAAfM/Z9r_glscNvU/s1600/Wireless.jpg
With all of this being said, however, I still can't seem to bypass my original screen that says 'No Sim Card'
3.bp.blogspot.com/_scN4BTBqXiY/S-dLhIjpQ7I/AAAAAAAAAfE/JkbHfOgW3f0/s1600/DSCN5623.JPG
If someone out there knows that is going on that I should change, please let me know, because I am really running into a dead end here.
Thank you very much!
I don't remember if RC29 has this, but in the initial setup wizard you should be able to press the menu key and access a wireless setup utility to connect to wifi.
Also, after you wipe and flash (or turn the phone on the first time), and if you get the "touch the android to begin" screen you can touch each of the 4 corners of the black background in a clockwise pattern starting in the upper left to go to the home screen.
That sqlite3 command needs to be run in a root shell. Make sure you're root. The $ prompt is the regular phone user. The root prompt will be # instead. Try running "su" after connecting with "adb shell" to become root. Is the rom you're using rooted?
I'm running CM 7 on my phone, which obviously comes rooted. When I open up a terminal on the phone, I have to "su" to escalate to having root privileges. This means that the phone will ask if its OK first.
But, when you run an ADB shell when the phone is in debug mode, it goes straight to giving root access.
Is there any way to have ADB start underprivileged, so you have to run "su" to gain root access?
Advantages would be when you forget to turn off debugging mode and your phone gets stolen. A thief would have a much harder time stealing any of your information or re-flashing your phone.
Edit: I've researched my options more fully and now have a much more detailed problem. See Below
Okay,
So I've smashed my display into little bits, but the phone still works. Has power, receives calls and texts, but cannot be controlled due to the broken screen.
I'm trying to get access to the file system and my contacts, but its proving to be quite difficult without use of the screen.
I've had partial luck so far using Droid Explorer. When I connect with Droid Explorer and boot into recovery, I am able to view my file system but unable to copy any files to my PC.
When I access the phone in non-recovery mode, I am unable to view the file system but am able to use the Screencast feature to display my home screen. I am NOT able to control the screen through screen cast, however.
I believe (but may be wrong) that I am unable to do backup my files or command the phone due to a lack of Superuser rights to ADB, thus I only have read-only access and not read-write. Is there any way to restore these privileges through the command prompt?
I tried following a video on using Droid Explorer to command the phone, but I get held up at the chmod 777 /data/dalvik-cache command as I do not have access to makes changes that system, due to (I think) never granting SU to ADB while my phone had a working screen.
MTK ADB gets you a privileged shell at the push of a button, allowing you to run commands directly on your MediaTek device. Some might wonder if rooting hasn't already solved this. Firstly, root access is persisted by modifying system files. When the real binary gets substituted by that of the root app's, if the device is rebooted, the init daemon running as root runs the binary giving the app root. What's wrong with this? If you have “purist” tendencies, you probably would want your phone as stock as possible, or at least with your permission. Sadly, not only binaries are dumped. Extra temp files, logs and helper binaries too, that manually removing them is like dancing on floor of pins and a prick means a brick. Not only that, consider yourself blocked from updates. If you're unfortunate enough, an update could result in bricking your phone as the files supposed to be present had been changed. This is more common than you think. MTK ADB makes no changes to your files whatsoever. Also, there's the matter of security/privacy. Root apps tend to always do something in the background. Either sneaking in a new app, or phoning home with your private data, or both. MTK ADB doesn't steal your data. The Internet permission is for Telnet, etc. On some devices, MTK ADB can get root access (depending on manufacturer) while all devices can get shell access. You just have to check which yours belongs.
IMPORTANT
•Refresh before (and after) clicking Start to check ADB status.
•Supports all ADB functionality. Just run "adb <command>" eg "adb pull" (without quotes).
•The minimalist terminal is for those who haven't any. Feel free to use your regular terminal (I use Terminal IDE) and keyboard (Hacker's Keyboard is really good). Just run "adb shell" on it.
•You can connect to your device using another phone, PC, or anything with a terminal and in the same network by running "adb connect IP_address".
•If you get a " device offline" error, disable and enable USB debugging. Next time connect to the network before running the app.
http://www.youtube.com/watch?v=_bt8BVaDCf0
http://slaycode.WordPress.com
Bump
Proof:
http://forum.xda-developers.com/gen...iled-error-t3191150/post62611445#post62611445
More Proof:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546/page10
Proof:
http://forum.xda-developers.com/gen...iled-error-t3191150/post62611445#post62611445
More Proof:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546/page10
When I open the app it opens but it doesn't work when I enter the commands and moreover the app when I try to start the adb it says unsupported device
Am using infinix hot 4 pro running NOUGAT xos 2.2
LordFME said:
MTK ADB gets you a privileged shell at the push of a button, allowing you to run commands directly on your MediaTek device. Some might wonder if rooting hasn't already solved this. Firstly, root access is persisted by modifying system files. When the real binary gets substituted by that of the root app's, if the device is rebooted, the init daemon running as root runs the binary giving the app root. What's wrong with this? If you have “purist” tendencies, you probably would want your phone as stock as possible, or at least with your permission. Sadly, not only binaries are dumped. Extra temp files, logs and helper binaries too, that manually removing them is like dancing on floor of pins and a prick means a brick. Not only that, consider yourself blocked from updates. If you're unfortunate enough, an update could result in bricking your phone as the files supposed to be present had been changed. This is more common than you think. MTK ADB makes no changes to your files whatsoever. Also, there's the matter of security/privacy. Root apps tend to always do something in the background. Either sneaking in a new app, or phoning home with your private data, or both. MTK ADB doesn't steal your data. The Internet permission is for Telnet, etc. On some devices, MTK ADB can get root access (depending on manufacturer) while all devices can get shell access. You just have to check which yours belongs.
IMPORTANT
•Refresh before (and after) clicking Start to check ADB status.
•Supports all ADB functionality. Just run "adb <command>" eg "adb pull" (without quotes).
•The minimalist terminal is for those who haven't any. Feel free to use your regular terminal (I use Terminal IDE) and keyboard (Hacker's Keyboard is really good). Just run "adb shell" on it.
•You can connect to your device using another phone, PC, or anything with a terminal and in the same network by running "adb connect IP_address".
•If you get a " device offline" error, disable and enable USB debugging. Next time connect to the network before running the app.
http://slaycode.WordPress.com
Click to expand...
Click to collapse
Are you familiar with an APK that utilizes mtk_bypass to directly flash firmware to device.
I'm looking for an APK that basically does what sp flash tool does because I don't have a computer.
How to remove SuperSU on unrooted phone? - "there is no SU binary installed..."
Hi,
I lost some SMS data. I tired to use data recovery software. One of the programs was Fonepaw. Apparently fonepaw tried to root my device and failed; or did something else. Yet, somehow fonepaw installed SuperSU as a system application. This is causing problems with the device, a Galaxy S5 (SM-G900V) running Android 6.0.1.
When I run the SuperSU application it reports:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
My only option is to select 'OK'. Which closes the app.
SuperSU won't uninstall via application manager due to being a system application.
The "adb backup" command no longer works since my attempts at using Fonepaw and a few other applications.
ADB see's my device via "adb devices". I can explore directories. If I enter "adb shell su" I get "[email protected]:/ #".
But when I try to run "adb backup" the phone doesn't go into the prompt where you say 'okay' and set a password. Adb backup has worked just fine in the past. It's been useful, and I need to use it again as part of changing to a new phone.
Android also is showing in notification a "Security notice" stating "Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes."
Restarting does nothing. Even booting to safe mode doesn't stop the security notice. SuperSU being a system app runs in safe mode.
Root Checker app comfirms the phone isn't rooted.
I have never attempted to root the phone and have been the only owner/operator.
I would like to uninstall the SuperSU application and any data it stored on the phone without losing any data on the phone. Since the phone is not rooted and no SuperSU binary was installed, I'm hoping this is possible.
My search for information has provided limited insight.
I'm hoping someone on XDA might know what to do.
Edit: Additional info.
https://android.stackexchange.com/questions/103611/remove-su-after-unroot
I do the following:
"[email protected]:/ # cd system/xbin"
"[email protected]:/systems/xbin # ls"
output:
"Dexdump
dexdump
jack_connect
jack_disconnect
jack_lsp
jack_showtime
jack_simple_client
jack_transport
jackc
su"
The commenter at stack exchange would suggest the phone I have has root, but root check says otherwise.
Another edit:
I'm not sure, but it looks like a Custom Recovery was installed on the phone. Unsure if that's what came with phone or not, vol down+home+power brings me to a screen without the "Android" icon/statute/person thingy. Same for booting into vol up+home+power. However, in the recovery I get 'reboot to bootloader' and when I select that I go to stock android download mode/odin mode. And when I boot the system, boot/splash screen "Samsung Galaxy S5" on top, a lock icon that is unlocked with "Custom" in the middle, and "powered by Android" at the bottom.
command "adb root" returns "adbd is already running as root".
So, I'm not sure what's going on here. Found a post stating you can have adb root without root in androids system. So...I'm a noob at all this. *CONFUSED*. Hoping for someone to help.
Fonepaw support has not been helpful at all.