Hey there!
I have been absent from android for some time now mostly because of my old job. Now, as Karma git me I started a new job where we erase used Devices and resell them.
We want to automate the process a bit, mostly activating usb debugging and sideloading apps. The Standard way of doing this via settings > tap 7x > activate takes too long to be viable. Imagine repeating this with like 500 Phones. The few seconds add up very fast.
So my question is:
Is there a reliable way to activate usb debugging on a wiped device? I cant use root.
The workflow should be something like this:
Connect phone > start enabler script > erase phone
We already tried using miradore (mdm) but it only activates dev options, usb debugging is manual still. Upon erasing the software we use shows that mdm is enable and that the device couldnt be erase fully.
Any help here is super appreciated.
Thanks in advance.
Related
Hey guys,
Haven't been here for a while. Okay, so I have a bit of a dilemma and every solution I've found requires something I just can't do. Here's the situation: my screen is broken, it has a lock screen, not in developer's mode, not unlocked.
This means:
I won't be able to transfer my files over, as I have to get past the lock screen
I can only install applications from Play store on my computer, but can't launch them
No use for any method that requires phone to be rooted
Can't even activate any USB options to transfer files some other way
Still need to be able to control it to create backups and such of important SMS messages, get files off
Does anyone have any suggestions at all? I don't want to have to resort to replacing the screen, as that'll end up costing me enough time and money where it's more cost-effective to purchase a new phone; however, I really need what's on my phone as soon as possible. Thanks in advance.
I think I have a solution for you: http://forum.xda-developers.com/showthread.php?t=2177440 Specifically, you'll want to read this post:
Carpetboy said:
So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process
Click to expand...
Click to collapse
In the future, always enable USB debugging in case of incidents like this. You can then use ADB commands to do a heck of a lot of things. Of course, it does make your phone data vulnerable if it gets stolen, but I'm willing to take the risk, plus 10 wrong PIN tries = reset anyway.
machoman1337 said:
I think I have a solution for you: http://forum.xda-developers.com/showthread.php?t=2177440 Specifically, you'll want to read this post:
In the future, always enable USB debugging in case of incidents like this. You can then use ADB commands to do a heck of a lot of things. Of course, it does make your phone data vulnerable if it gets stolen, but I'm willing to take the risk, plus 10 wrong PIN tries = reset anyway.
Click to expand...
Click to collapse
Now with 4.2.2 the adb device appears as offline and the only way to bring it online is to use the touch screen.... I have an important email on my phone just looking at me and its driving me completely INSANE that I cannot get to it.
I have to wait 4 days to get a screen in just to get to this important email..... THANKS GOOGLE!
oh and tmobiles insurance is a joke $100 deductable... the clear your phone. my way $79 new screen and same phone.
ikarma said:
Now with 4.2.2 the adb device appears as offline and the only way to bring it online is to use the touch screen.... I have an important email on my phone just looking at me and its driving me completely INSANE that I cannot get to it.
I have to wait 4 days to get a screen in just to get to this important email..... THANKS GOOGLE!
oh and tmobiles insurance is a joke $100 deductable... the clear your phone. my way $79 new screen and same phone.
Click to expand...
Click to collapse
where did you get the screen for $79???
hi, what does this mean?
2. Install the USB driver from the SDK so that it appears as an ADB device
michaeliang said:
hi, what does this mean?
2. Install the USB driver from the SDK so that it appears as an ADB device
Click to expand...
Click to collapse
1. It means that if you have the SDK Manager installed on your computer, somewhere between the last packages at the bottom of the list, you'll see "android drivers" (or something similar). With those drivers, your device will show up in "Device manager"(the Windows' one) as an adb device.
2. But if you don't want to get the SDK Manager and be quicker, you can download only those drivers, directly from the "Google developers" page and install them manually by going to "Device manager", right clicking on the Nexus 4 (it will appear with a yellow triangle on it, maybe), then "Update driver", "...BROWSE computer...", then click again on "Browse", then go to where the drivers have been downloaded and select the entire folder by highlighting it and clicking ok (or something). The folder with the driver would look like this "latest_usb_driver_windows" and inside you'll see another folder called "usb_drivers". That's what you need to select and install.
So that's what you need to do to make your phone appear as an adb device in "Device manager". And, of course, adb let's you do a lot of stuff to your phone through your computer, but probably you already knew that.
Hey everyone,
Ive recently had a problem trying to use a few root apps with my phone that require USB debugging and to my surprise found out it turns itself off after I leave the options screen.
Is this a normal security feature? Is there a way to keep it on?
Obviously it stays on when activated and connected to USB on a PC, but that does not help me when an app needs it. I have never seen this behavior before yet everything in USB debugging sticks (except some options after re-boot like DPI)
And thats another question,
How do we keep DPI changes in developer mode to stick after reboot.
Maybe there is a config XML somewhere in the system as normal DPI changes to the sparse Build.prop do not work since dpi is controlled via rom level.
Any help or input would be appreciated if this usb debugging thing is not normal for everyone.
If anyone knows about the DPI thing that would ne also helpful
I have an old S3 from a relative that I need to open and pull data from, but the code is not known nor is debugging enabled. I downloaded 3rd party software (dr. fone) but this model was not supported. I am looking for any possible way to extract the data from this phone. I have been googling for days, downloaded adb and odin but have no real idea how or if I can leverage those to either delete the passkey file or enable debugging to pull the data. I am generally tech savvy and not stupid, but I have zero experience with coding or mobile devices. This is very important to me and my family. Please help
OK, this is driving me nuts! The phone has been restored to stock (Android Version 8.0.0) and has nothing on it from the Play Store, just the stock Samsung apps - trying to get ADB to work without any joy, as want Fluid NG on it........
It did once offer the options (weird?), but I got the Allow USB Debugging popup with the RSA Key, but also the error 'Because an app is obscuring a permission request, Settings can't verify your response' error - Went to the 'Apps that can appear on top' section (assume this is the same as 'Draw over other apps?), and disabled everything in the list - still the same error!
Now the only options I get when connecting are:
Transfer Files
Transfer Images
MIDI Device
Charge this Phone
So far I've.......
Enabled Dev mode
Enabled USB debugging
Disabled Verify Apps via USB
Installed Samsung Drivers
Installed ADB Fastboot
Disabled all 'Draw over other apps' apps in the Apps list.
Tried another laptop
Tried another USB cable
It shouldn't be this difficult, I know!!
I updated via local upgrade coming from rooted 9.0.17 with magisk and twrp
But not I have lost twrp and magisk and don't want to deal with the stress of having to lose data and figure out how to get everything back..
So is there anyway to get the pill gestures back without root?
adb
If you're a Oneplus user running Android 10 and you've sifted through the different navigation options available for your device, you probably noticed that two-button navigation is no longer there. For proponents of this UI, such news might be pretty disheartening.
Well, grieve no more, two-button devotees! There's a way to resurrect the sweet harmony of modern gesture navigation and the coveted "back" button of yore, and it just takes a bit of ADB intervention to make it happen.
To begin, you'll need to download the latest version of Android Debug Bridge to your computer; for the most straightforward method, check out this Nexus Tools installer for Mac and Linux, compiled by Android Police's Corbin Davenport; Windows users can download the required SDK Platform Tools from here separately. You'll also need to enable USB debugging on your device, which you can do by following this path: Settings -> System -> About Phone -> tap build number 7 times to enable Developer options, then enable USB debugging via Settings -> System -> Advanced -> Developer options).
Next, make sure your phone is connected to your computer. Set the current navigation setting on your phone to the standard 3-button layout. Then open ADB and execute the following command:
adb shell cmd overlay enable com.android.internal.systemui.navbar.twobutton
And that's it! You should now see two-button navigation in your settings app.
Sandipmatsagar said:
If you're a Oneplus user running Android 10 and you've sifted through the different navigation options available for your device, you probably noticed that two-button navigation is no longer there. For proponents of this UI, such news might be pretty disheartening.
Well, grieve no more, two-button devotees! There's a way to resurrect the sweet harmony of modern gesture navigation and the coveted "back" button of yore, and it just takes a bit of ADB intervention to make it happen.
To begin, you'll need to download the latest version of Android Debug Bridge to your computer; for the most straightforward method, check out this Nexus Tools installer for Mac and Linux, compiled by Android Police's Corbin Davenport; Windows users can download the required SDK Platform Tools from here separately. You'll also need to enable USB debugging on your device, which you can do by following this path: Settings -> System -> About Phone -> tap build number 7 times to enable Developer options, then enable USB debugging via Settings -> System -> Advanced -> Developer options).
Next, make sure your phone is connected to your computer. Set the current navigation setting on your phone to the standard 3-button layout. Then open ADB and execute the following command:
adb shell cmd overlay enable com.android.internal.systemui.navbar.twobutton
And that's it! You should now see two-button navigation in your settings app.
Click to expand...
Click to collapse
Thanks for posting this. One problem, none of your links for the tools listed are showing up.
Sent from my ONEPLUS A6013 using Tapatalk
xRogerxC said:
Thanks for posting this. One problem, none of your links for the tools listed are showing up.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
That's probably because there are no links posted in the previous post.