[Q] Rooted and Ran GladEnable... Still No Sideloading - Atrix 4G Q&A, Help & Troubleshooting

My Atrix is on 4.1.83 AT&T
I rooted using the GingerBreak
After rooting I ran the Gladenable script as per procedure in this forum
http://forum.xda-developers.com/showthread.php?t=1017373
It installed succeessfully and i clicked allow when Super User permission displayed.
Now when i try to install 3rd party apps like Amazon / Teamviewer, I am still getting the message "This application comes from unknown source and cannot be installed"
Am I missing something?
How do we know if GladEnable is installed ?
Is there any other option i have to select to Enable Sideloading?

I did see in the Super User Apps tab, 5 New Unknown Apps
Its all almost same time and detail shows
1. mount
2. cp sqlite
3. chmod
4.gladenable.sh sideload
5. gladenable.sh tether
So all above confirms GladEnable installed.
Is these 5 are correct or should i need to see more?
What happen if i run the Glad Enable again?

did you tick the box to allow unknown sources?

When I go into Settings > Applications > Development
I didn't see the option to Allow Unknown Sources.
These are the things i see..
USB Debugging
Stay awake
Allow mock locations
Am I looking at the right place?
Also Under Settings > Applications
I did see these Menus
Manage Applications
Running Services
Development
Double tap home launch

try running root explorer or titanium backup to verify Root access

sakdroid said:
When I go into Settings > Applications > Development
I didn't see the option to Allow Unknown Sources.
These are the things i see..
USB Debugging
Stay awake
Allow mock locations
Am I looking at the right place?
Also Under Settings > Applications
I did see these Menus
Manage Applications
Running Services
Development
Double tap home launch
Click to expand...
Click to collapse
Unknown Sources will be the First option in the Application menu followed by Preferred install location, manage applications etc. Make sure usb debugging is still on and leave it on! Run glade enable again just say no to them all accept the sideloading one. Give that a shot.

I had exactly the same problem. Download the app called root checker and make sure that you are rooted and have the busybox installed. Also, if you are trying to Run GladEnable.bat on Windows 7, make sure that you run it as admin by holding down control and double-clicking, like step 8 mentions. And last, but not least, make sure you have the usb on debbuging mode, you select the "None" usb option on the on your phone, and that windows uses the debbuging drivers when plugged in. I hope this info helps you.

Thanks everyone for the support!
I just reran Glad Enable and now I see the Unknown source under application menu.

Related

USB Debugging enable on boot?

I've turned on the developer options and can enable the USB Debugging option to be able to use Titanium backup. However I notice when I reboot the device it gets disabled again. Does anyone know of something/somehow to ensure it's enabled on boot?
Thanks!
---Eric
Got it, need root shell of course:
- Remount /system in readwrite mode.
- Add this to /system/build.prop: persist.service.adb.enable=1
- Save, remount as read only.
- Reboot.
Well...didn't really work...though it did, any ideas? USB debugging for me has to be manually picked each time.
So what seems to work for me upon reboot is that I use SManager and have a script run as root at boot up:
#!/system/bin/sh
echo 1 > /data/property/persist.service.adb.enable
This seems to enable USB debugging upon each boot. The build.prop worked once, but did not seem to keep it enabled.
Any chance anyone else has come up wth a different way to retain USB debugging on reboot? I just had to rebuilt my phone from scratch by restoring from stock and executing a script at boot up could potentially be fatal. I'm a linux admin so I do know what I am doing but without a unlocked bootloader and the ability to recover from a CWM backup, I'd rather not mess with the OS too much if possible.
x86cpu said:
So what seems to work for me upon reboot is that I use SManager and have a script run as root at boot up:
#!/system/bin/sh
echo 1 > /data/property/persist.service.adb.enable
This seems to enable USB debugging upon each boot. The build.prop worked once, but did not seem to keep it enabled.
Click to expand...
Click to collapse
JCDinPGH said:
Any chance anyone else has come up wth a different way to retain USB debugging on reboot? I just had to rebuilt my phone from scratch by restoring from stock and executing a script at boot up could potentially be fatal. I'm a linux admin so I do know what I am doing but without a unlocked bootloader and the ability to recover from a CWM backup, I'd rather not mess with the OS too much if possible.
Click to expand...
Click to collapse
I use Tasker with the secure plugin.
It allows turning on USB Debugging. I use it to turn on USB Debugging as a condition after boot.
Also the worst case with a script, you re-install/flash the OS.
I've reinstalled my Verizon LG G3 from stock ROM twice now. The first time I rooted it with IOROOT and the USB debugging option stays enabled after reboot. The second time I rooted it with Stump root and the USB debugging option does not stay enabled after reboot. No idea what is different between them but maybe someone else can dig through and figure it out.
I have the same problem, when I reboot the phone and open titanium backup.
tech_head said:
I use Tasker with the secure plugin.
It allows turning on USB Debugging. I use it to turn on USB Debugging as a condition after boot.
Also the worst case with a script, you re-install/flash the OS.
Click to expand...
Click to collapse
Could you share how to set this up? Thanks
bamemanxxa3416 said:
Could you share how to set this up? Thanks
Click to expand...
Click to collapse
Set up a task with the "secure Settings" plug in.
You are going to go into the "System Actions" and select "USB Debugging" then select the radio button to "On" then save.
Now you are going to create a profile that uses an Event.
The even will be a "System" type of event and under system you will see "device boot".
Once you have created the event add the USB Enable task you created.
This all assumes you know how to use tasker.
problem fixed......
tech_head said:
Set up a task with the "secure Settings" plug in.
You are going to go into the "System Actions" and select "USB Debugging" then select the radio button to "On" then save.
Now you are going to create a profile that uses an Event.
The even will be a "System" type of event and under system you will see "device boot".
Once you have created the event add the USB Enable task you created.
This all assumes you know how to use tasker.
Click to expand...
Click to collapse
Very nice instructions and thanks for taking the time
because of stumproot, if using iosroot then problem will never appear.
ericsmart said:
because of stumproot, if using iosroot then problem will never appear.
Click to expand...
Click to collapse
Actually not true.
I used ioroot and I have the issue of USB Debug not sticking.
That's why I came up with the way to fix it in tasker.
tech_head said:
Actually not true.
I used ioroot and I have the issue of USB Debug not sticking.
That's why I came up with the way to fix it in tasker.
Click to expand...
Click to collapse
but, it's good to have other solution, it's all good that you guided them who have similar problem.
I have the same problem as you.
tech_head thanks for giving this tasker newb enough bread crumbs that I was able to figure it out and solve the problem (and learn something in the process).
Real easy check usb debug,then plug phone into computer go to your folder that you have adb shift right click mouse all at once open cmd window here check Ethernet mode on phone check rsa cert when prompted type adb devices press enter then adb reboot then enter when LG logo appears unplug phone now your usb debug will always stay checked
WHATSAMATTA U ALUMNI
the tasker approach is now disabled and deathsquad737`s approach has caused it to stay checked... Thanks!
Hi Guys
I found a easy way to fix it.
1) turn on USB debugging
2) Connect G3 to your PC
3) Reboot your G3 when keep connected to PC
4) Unplug
Now the debugging option will be kept.

Can't install apk on 2.0 to save my life

Must be the ADB issue on 7.1.1 but it's driving me crazy. I've tried adb debugging then using "adb install appname.apk" it doesn't work . Someone had a working method on 2.0 when it was a beta build but i can't find the thread. Help me out peeps!
You need universal ADB drivers working and enable ADB Debugging in Developer Settings of the watch. Check the device manager for devices without any drivers and verify that ADB Debuggin is active. Of course you need to activate these first. Go to the settings menu, and scroll down to "About" Tap it. Scroll down to the bottom again, where you see "Build" something Tap it seven times. After the third tap, you'll see a playful dialog that says you're four taps away from being a developer. (If only it were that simple, eh?) Keep on tapping, and *poof*, you've got the developer settings back.

Will pay for a way to get into my tablet

I have a jp5s tablet running android 4.2.2. It is a prison issued tablet. USB debugging is not enabled, and you can't enable devlopers options. Bluetooth works but app installation is blocked for security purposes. And the ability to allow unknown sources is disabled. Recovery mode only has reboot now. There is no fastboot so adb on windows will not connect. My only idea is maybe a picture or video file that runs a script to allow USB debugging, or installs an apk(a file manager). Also I'll pay for one that will set my devices year back to 2011 or so. Please any help or advice. Maybe a windows program that will force connect adb somehow.
Yeah you can go to settings but its very limited, pressing build number only brings up a list of installed apps.
Nothing google at all its a prison tablet that's the issue I want to install apps
inameasone said:
I have a jp5s tablet running android 4.2.2. It is a prison issued tablet. USB debugging is not enabled, and you can't enable devlopers options. Bluetooth works but app installation is blocked for security purposes. And the ability to allow unknown sources is disabled. Recovery mode only has reboot now. There is no fastboot so adb on windows will not connect. My only idea is maybe a picture or video file that runs a script to allow USB debugging, or installs an apk(a file manager). Also I'll pay for one that will set my devices year back to 2011 or so. Please any help or advice. Maybe a windows program that will force connect adb somehow.
Click to expand...
Click to collapse
Hi , can you post video on YT in order to see what is actually happening your device.
Yes I do, I need to install a 3rd party app

[GUIDE] Ultimate Debloating Tool

DONT END UP REMOVING CORE SYSTEM APPS IT WILL RESULT IN A BOOTLOOP!
You need a PC to do this.
This helps you to select the app you want to debloat and gives you options to restore/backup as well.
It also includes a ton of other features.
You can either download the standalone JAR file or the ZIP file which contains both fastboot and ADB.
All credits go to Saki.
Enable developer options in Android.
MIUI: Go to Settings > About device and tap ‘MIUI version’ seven times to enable developer options.
Enable USB debugging in Android.
MIUI: Go to Settings > Additional settings > Developer options and enable USB debugging.
In order to use the Screen density and Screen resolution modules, enable USB debugging (Security settings) as well.
Connect your device to the computer and launch the application. The device is going to ask for authorisation, which you'll have to allow.
Wait for the application to detect your device. The device info should appear in the top left section.
Downloads:
https://github.com/Saki-EU/XiaomiADBFastbootTools/releases
(Just click on assets for the latest version)
Latest JAR Standalone as of 9-9-2019;
https://github.com/Saki-EU/XiaomiADBFastbootTools/releases/download/6.6.1/XiaomiADBFastbootTools.jar

Bad package installed in Xiaomi MI A2 Lite

Hello,
I have a big problem to uninstall a package that I naively installed on the phone.
First of all, the phone works rather normally but:
a) I can't uninstall this app
b) I can't uninstall any other app
c) The app is present in the Accessibility section as a service (it's a clone of LiveNetTv).
The package is named com.a02f252e890bf12d80.eccfe059f8f8a9f521.
I would like to connect the phone to PC via Adb so that I can uninstall the app
from Adb using the indications described here:
h ttps://gadgetstouse.com/blog/2020/07/10/how-to-uninstall-stock-apps-from-android-without-rooting/
The big problem is this one: from the Developer options, when I enable "Debug USB" option,
immediately the option is turned off (every single time), so it's almost impossible for me
to see the phone from PC: if from Powershell I launch the command "adb devices", the device
is never recognized so I can't launch any command to uninstall the app.
I hope you can help me with step by step: the device is not rooted and I prefer not to root it.
Thanks so much for the attention.
vaiadubai said:
The big problem is this one: from the Developer options, when I enable "Debug USB" option,
immediately the option is turned off (every single time), so it's almost impossible for me
to see the phone from PC
Click to expand...
Click to collapse
Restore Android's default settings in Developer options. Re-boot Android. Then re-try.
jwoegerbauer said:
Restore Android's default settings in Developer options. Re-boot Android. Then re-try.
Click to expand...
Click to collapse
In Developer options I don't see the option you quote.
Under System -> Advanced -> Reset options I only have 3 voices:
a) Reset Wi-Fi, mobile data and Bluetooth: I already did it.
b) Reset App Preferences (once clicked, the menu disappears immediately).
c) Reset All Data (I hope to solve before doing this).
For better info, the software of this device is of the type Android One.
Thanks for the answers,
at the end I preferred doing a reset of the phone's data.
With apps memorized in Google Drive it seems not so long to recuperate
a configuration similar to the original.

Categories

Resources