Hello.
I need an adb insecure kernel/a kernel with usb debugging enabled at boot for this device for development purposes but I'm a total noob in terms of kernel development. Is there anyone willing to make this?
If it matters my exact model is SM-A516B/DS.
Thank you a ton!
I think you can do it another way without an adb insecure kernel. It's been so long since I did this but this may help.
When booted normally, enable USB debugging, start adb (adb devices) and give the PC the permission permanently. Then, you can locate the following file and save it in your PC:
data/misc/adb/adb_keys
Then every time you want usb debugging to be enabled, you can create a folder called misc/adb in your data partition and then copy the adb_keys file inside.
It should work just as long as you're using the same PC to catch logs at boot when the adb_keys file was created.
And finally, you need to edit your vendor/default.prop. By default, you should have:
persist.sys.usb.config=mtp
Just change to
persist.sys.usb.config=mtp,adb
Maybe one of these is extra and not needed but I remember this used to work for me, so hopefully it still works
Good luck.
Related
Sorry about the post but I cannot find the post were it tells me how to install custom boot animations. I also need to be able to do the sounds. As far as I understand I have to put it in the media folder. I found the original one but it does not allow me to move it. I'm assuming I have to do it from recovery but I don't know how. Detailed instructions would be appreciated. I have a cold and the old brain is doing so well. Thanks
s-off your dinc and you can do it while booted
I was trying to avoid that because they do not have a way to undo s-off yet. Just incase my phone dies I dont want verizon to say I voided the warranty. Any way to do it without?
You can flash some of them from rom manager...that's how I did mine.
If you have rooted your phone, which you must have in order to install a custom ROM, you've already voided your warranty.
Adding S-OFF wouldn't change anything in the eyes of Verizon, and you can always drop your phone until it's physically broken if you need to take it in.
rom manager -> download rom -> Ihtfp69 -> boot animations -> download -> pick one
thats where i got mine from
MMBosstones86 said:
rom manager -> download rom -> Ihtfp69 -> boot animations -> download -> pick one
thats where i got mine from
Click to expand...
Click to collapse
When I try to install from Rom manager it doesn't load it says verification failed or something. Does anyone know how to manually install Droid 2 boot screen.
HTC incredible
SR sense 2. 5. 2
Radio 2. 15
Sent from my ADR6300 using XDA App
Did mine 'manually', since I'm rooted I have clockwork mod installed.
1. Boot into recovery (clockwork mod)
2. launched android SDK adb daemon
3. moved file from 'tools' folder of sdk to the proper destination on the phone.
4. Done.
Doctor Butts said:
Did mine 'manually', since I'm rooted I have clockwork mod installed.
1. Boot into recovery (clockwork mod)
2. launched android SDK adb daemon
3. moved file from 'tools' folder of sdk to the proper destination on the phone.
4. Done.
Click to expand...
Click to collapse
I'm not sure how to do step 2 your referring to. If you have a link to a thread that explains how to do that, it would be greatly appreciated.
Sent from my ADR6300 using XDA App
Well, you have to go to the android website and download the android SDK. Install it somewhere on your computer that's easy to access, preferably put the folder at the root of one of your hard drives.
You'll go into command prompt after that to do a lot of the work to transfer files.
So, make sure USB debugging is enabled (just in case) and boot your phone into cwm recovery. Connect the phone to your computer via USB.
in command prompt, cd to the android sdk's tools directory. From there, you can use the adb commands to transfer files.
So, for me, after connecting the phone I do the following in command prompt:
cd G:
cd androidsdk/tools
and then I use ADB to communicate with phone, first by verifying the phone is connected:
adb devices
(if adb is on your pc, it will auto run the daemon if it is not running)
If your phone shows up in recovery mode, you're set.
You may need to go into cwm and mount your system/sd card before transferring the file.
From there, you use adb shell to acess the phone's file systems.
If you put the boot animation to the phone you'll do something like (while in shell) mv bootanimation.zip system/somethingorother/bootanimation.zip
But don't take the above line as gospel. I dont remember the exact command line to use. Check the thread on "How 2 - ADB, Rooting...." for a list of commands in ADB shell and search for a webpage that gives basic linux commands.
Doctor Butts said:
Well, you have to go to the android website and download the android SDK. Install it somewhere on your computer that's easy to access, preferably put the folder at the root of one of your hard drives.
You'll go into command prompt after that to do a lot of the work to transfer files.
So, make sure USB debugging is enabled (just in case) and boot your phone into cwm recovery. Connect the phone to your computer via USB.
in command prompt, cd to the android sdk's tools directory. From there, you can use the adb commands to transfer files.
So, for me, after connecting the phone I do the following in command prompt:
cd G:
cd androidsdk/tools
and then I use ADB to communicate with phone, first by verifying the phone is connected:
adb devices
(if adb is on your pc, it will auto run the daemon if it is not running)
If your phone shows up in recovery mode, you're set.
You may need to go into cwm and mount your system/sd card before transferring the file.
From there, you use adb shell to acess the phone's file systems.
If you put the boot animation to the phone you'll do something like (while in shell) mv bootanimation.zip system/somethingorother/bootanimation.zip
But don't take the above line as gospel. I dont remember the exact command line to use. Check the thread on "How 2 - ADB, Rooting...." for a list of commands in ADB shell and search for a webpage that gives basic linux commands.
Click to expand...
Click to collapse
THANK YOU SIR. MUCH APPRECIATED.
Sent from my ADR6300 using XDA App
Hey guys, My friend brought me a Xtreamer Q mobile phone with broken screen, clockworkmode is working, but USB debugging mode is disabled, I found some posts about how to enable it from adb i tried them and none of them worked.
here :
http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
and from this tutorial i learnt how to edit build.prop file.
http://www.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
the commands i have used are: adb pull, adb remount, adb push.
While i was under clockworkmode i mounted system and i pulled build.prop then i added this line to it persist.service.adb.enable=1, used remount then pushed the file after that reboot, but i couldn't find the device in adb when it have booted normaly.
Next i tried to set adb_enabled to 1 in /data/data/com.android.providers.settings/databases/settings.db by following some steps from here
http://forum.xda-developers.com/showthread.php?t=774507.
and it also didn't worked "The device was not listed".
Also i have tried this zip file from clockworkmode it didn't work too...
http://android.stackexchange.com/questions/54487/install-adb-enabled-setting-from-zip
My files after editing are attached, wish somebody can help me to enable it.
The phone do not support USB OTG cable
ThElitEyeS said:
Hey guys, My friend brought me a Xtreamer Q mobile phone with broken screen, clockworkmode is working, but USB debugging mode is disabled, I found some posts about how to enable it from adb i tried them and none of them worked.
here :
http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
and from this tutorial i learnt how to edit build.prop file.
http://www.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
the commands i have used are: adb pull, adb remount, adb push.
While i was under clockworkmode i mounted system and i pulled build.prop then i added this line to it persist.service.adb.enable=1, used remount then pushed the file after that reboot, but i couldn't find the device in adb when it have booted normaly.
Next i tried to set adb_enabled to 1 in /data/data/com.android.providers.settings/databases/settings.db by following some steps from here
http://forum.xda-developers.com/showthread.php?t=774507.
and it also didn't worked "The device was not listed".
Also i have tried this zip file from clockworkmode it didn't work too...
http://android.stackexchange.com/questions/54487/install-adb-enabled-setting-from-zip
My files after editing are attached, wish somebody can help me to enable it.
Click to expand...
Click to collapse
What do you want to make with the phone if adb is working?
LS.xD said:
What do you want to make with the phone if adb is working?
Click to expand...
Click to collapse
I want to install a program to on it to control it from my computer
Hello,
I have Oneplus One 64 gb variant, yesterday my nephew somehow changed my phone's lock pattern and now my phone is locked. USB debugging was disabled at that time. I am not able to get into my phone through any means. I have lot of important data in my phone and don't want to hard reset my device. I found a solution online to get usb debugging on through adb , but I am a ultra noob and don't understand how that has to be done. please dumb it down so that I can save my precious data and unlock my phone when debugging gets enabled. Also I don't have any custom recovery installed on my phone.
This is what is mentioned in the solution.
"Instructions
1. You should try your pattern-cracking software (or whatsoever the genre it has) from inside the Stock Recovery to see whether it works with the former's environment (ADB shell available there or not).
2.Since I would never try step 1., I would do the following:
-For Jellybean 4.2.1:
1. Boot into Recovery and mount Data partition.
2. Open a shell on PC and type:
adb pull /data/property/persist.sys.usb.config ~/
Repace ~/ with home directory of your OS.
3. Open that file in a text editor and you would possibly see mtp written there. Change it to mtp,adb.
Note that sometimes Android doesn't understand the text file changes if the line terminator is "DOS Terminators" which Notepad would probably do on Windows (mine is Linux so no issue here).
In that case, I would suggest not using adb pull but doing:
adb shell
echo 'mtp,adb' > /data/property/persist.sys.usb.config
You may verify that the echo command overwrote the file by using:
adb pull /data/property/persist.sys.usb.config ~/
and seeing the file's content in some text editor.
4. Unmount Data and reboot into Android OS. USB Debugging would probably be enabled.
-For Lollipop 5.0:
JB 4.2.1 users can also follow this method if the previous one didn't work for them.
1. Boot into Recovery and mount Data partition.
2. Repeat step 2 and 3 used in JB 4.2.1 method.
3. We need to tweak some parameters in settings.db. Type:
adb pull /data/data/com.android.providers.settings/databases/settings.db ~/
4. Back it up at some other location too, and open the file in an SQLITE editor. I'm running Linux and DB Browser for SQLite works well. It's also available for Windows OS/OSX.
5. In the global table, change the value for:
adb_enabled to 1
development_settings_enabled to 1
6. Check that verifier_verify_adb_installs is set to 1 in the global table.
7. Check that as default, in the secure table:
adb_notify is 1
adb_port is -1
These checks in step 6 and 7 are not necessary but should be done so that troubleshooting becomes rather easy if the solution doesn't work for you.
8. Save the changes in settings.db and copy it back into Android by typing:
adb shell
rm /data/data/com.android.providers.settings/databases/settings.db
exit
adb push ~/settings.db /data/data/com.android.providers.settings/databases/
That delete (rm) command is not necessary since adb push should overwrite the file, but I executed it for my peace of mind.
8. Unmount Data and reboot into Android OS. ADB probably would be enabled.
source:- https://android.stackexchange.com/questions/112040/how-to-enable-usb-debugging-in-android-if-forgotten-pattern-for-screen-unlock"
Please help me understand this code and be a life saver.
Thanks in advance..
You are stuck, I'm afraid. You won't be able to run any script on stock recovery, but you can't flash a custom recovery without unlocking the bootloader which will wipe your data.
What's more, your phone should be encrypted (if it's running 6.0 or higher), which means you'll need to know the pattern to decrypt after a reboot.
If you can't figure out the pattern, there's nothing you can really do.
jisoo said:
You are stuck, I'm afraid. You won't be able to run any script on stock recovery, but you can't flash a custom recovery without unlocking the bootloader which will wipe your data.
What's more, your phone should be encrypted (if it's running 6.0 or higher), which means you'll need to know the pattern to decrypt after a reboot.
If you can't figure out the pattern, there's nothing you can really do.
Click to expand...
Click to collapse
Is there any way I can create backup of the data in these conditions?
Dush123 said:
Is there any way I can create backup of the data in these conditions?
Click to expand...
Click to collapse
Unfortunately for you in this case, there isn't.
From a general security perspective, if there was it would mean the pattern lock and encryption can be bypassed, which would be very bad.
jisoo said:
Unfortunately for you in this case, there isn't.
From a general security perspective, if there was it would mean the pattern lock and encryption can be bypassed, which would be very bad.
Click to expand...
Click to collapse
Ohk. Then it seems I don't have any option but to hard reset my device.
Thanks anyways
HI! Is there anything I can do for my pattern locked Moto E4 Plus? Details I've posted in this thread.
https://forum.xda-developers.com/showthread.php?t=2620456&page=13
Hi, I've got an old S5 with a broken screen. There's no image going on and there's no indication that the touchscreen is working.
I'm not looking to recover data, I'm looking to play around with it by controlling it from my PC. Last I remember, the phone is running a Cyanogenmod OS (I don't think LineageOS was around at that time) with either TWRP or CWM recovery, but I'd bet on TWRP.
Now: the device reaches the OS properly, I can tell because if I try to turn the ringing sound up it gives me an audio feedback.
If I connect it to a PC from the OS:
- the phone shows up in Windows Explorer as "SM-G900F"
- Device Manager shows me a "SAMSUNG Mobile USB Composite Device" under Universal Serial Bus controllers
However I cannot access any files (Windows Explorer shows the device as empty), and if I attempt to 'adb devices' in the console it shows me an empty devices list.
Now, I suspect that USB debugging might be off. So I also tried connecting it to a PC from recovery and the exact same thing as above can be observed, PLUS:
- Device manager also shows me a "SAMSUNG Android Phone" list which can be expanded to show me one entry called "SAMSUNG Android ADB Interface"
However it's the same as before, no files available and 'adb devices' shows an empty list.
Now I heard that I can theoretically enable USB debugging through ADB, by writing to a config file. That would allow me to enable USB debugging and try something like Vysor in order to control the phone from my PC.
However that's a moot point until I can figure out why the ADB service on my PC isn't seeing the device. Any help would be greatly appreciated, and if you need more info I can provide it.
Extra info:
- I installed Samsung USB drivers at some point while trying to make it work
- Windows Explorer shows a phone icon for this device, and if I recall correctly that's what happens when it's connected through MTP (Mass Storage should show it like a memory card)
_sepiroth said:
Hi, I've got an old S5 with a broken screen..........
Click to expand...
Click to collapse
I've never experienced this situation myself but, I've seen that the following thread has worked for many individuals.
https://forum.xda-developers.com/showthread.php?t=2786395
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Ibuprophen said:
I've never experienced this situation myself but, I've seen that the following thread has worked for many individuals.
https://forum.xda-developers.com/showthread.php?t=2786395
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Click to expand...
Click to collapse
Thanks a bunch, that pointed me in the right direction with my research! I solved my issue, I can now control my phone from my PC.
By doing this I ran into a couple of problems, I'm going to describe them and their solutions:
Problem 1: couldn't ADB into the device when in Recovery Mode. That is because after a long head scratching session I came to the conclusion that I didn't have TWRP Recovery installed (I had Philz Touch CWM Recovery and LineageOS 14.1 instead).
Solution 1: ADB mode is enabled in TWRP by default. So I flashed the latest TWRP through Odin, ADB instantly started working afterwards in Recovery Mode.
Problem 2: USB Debugging was disabled inside the OS.
Solution 2: from the thread that Ibuprophen posted, you can enable USB debugging in your OS by opening an ADB shell into your device and modify the build.prop like so
Code:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop
reboot
Problem 3: /system was empty so there was no build.prop. If I attempted to create a build.prop file it wouldn't be saved after a device reboot, so USB debugging still didn't work.
Solution 3: it seems like TWRP doesn't mount /system by default, only /data. You can mount it manually through ADB like this:
Code:
mount -o rw /dev/block/bootdevice/by-name/system /system
I found this out from this stackexchange question: https://android.stackexchange.com/q...data-partitions-in-recovery-mode-in-adb-shell
Problem 4: When an app tries to use USB Debugging you need to allow it to do so from the phone. Since the screen was broken, I couldn't do this.
Solution 4: You'll need to push a public key to your device with ADB. Boot into Recovery Mode and make sure your device is recognized by your PC and type
Code:
adb push <path to adbkey.pub on your PC> /data/misc/adb/adb_keys
This solution is from: https://stackoverflow.com/questions...b-rsa-key-with-broken-touch-screen-on-android
This will make sure that you won't need to confirm debugging permissions for apps coming from your machine.
So for anyone who has a broken phone screen (my screen is dead and touchscreen/touch buttons are kaput too) and wishes to control their phone from their PC but USB debugging is disabled:
1. Boot device in TWRP Recovery (flash it if you don't have it)
2. ADB into the device
3. Make sure /system is mounted (if it's empty it means it's not mounted), else mount it manually like in Solution 3
4. Configure build.prop to have USB Debugging enabled like in Solution 2
5. Push your public key to the device like in Solution 4
6. Restart the phone (into its OS)
7. Download the Chrome extension called Vysor and launch it
8. Connect your phone through a USB cable
9. The device should appear in Vysor, connect to it and have fun controlling it
Note that if you just want to backup your files, steps 1 + 2 are sufficient. After making sure ADB works you can just 'adb pull' all your files which should be located in /sdcard. Google it, it's easy to find.
The same goes for backups, you can do them directly through ADB.
Again, thanks Ibuprophen!
Vysor does not work on all graphic cards. a good free alternative is scrcpy
btw instead of flashing twrp, you can flash a modified system partition with proper entries in build.prop (for those with no custom recovery available)
aIecxs said:
Vysor does not work on all graphic cards. a good free alternative is scrcpy
btw instead of flashing twrp, you can flash a modified system partition with proper entries in build.prop (for those with no custom recovery available)
Click to expand...
Click to collapse
Very well pointed out, thanks for this.
hi guys I need help to recover some personal photos I had saved on my device. The phone has a broken screen and touch so I cannot use a mouse or try to blindly unlock it, but it has been rooted and usb debugging is enabled; unfortunately my pc is not authorized by the phone and I have no way to authorize it through the pop up without a screen. I have searched around many forums to find a solution but it seems every time there was something wrong, so I need some help.
The solution that got me the nearest to a conclusion that I tried are:
using adb in custom recovery (which I do have) and trying commands like "adb pull /sdcard" which resulted in "pull: building file list... 0 files pulled. 0 files skipped.", I don't understand why it's unable to pull any file.
trying to authorize usb debugging for my pc through adb by "adb push adb_keys /data/misc/adb", adb_keys is the adbkey.pub file in the .android folder renamed. I can confirm i pushed them since "adb pull /data" pulled "data/adb/misc/adb_keys" as the only file, but I still don't have authorization
I'm not too literate in this kind of commands so please be patient but I really need help
RECAP OF MY PHONE STATUS
Xiaomi Mi 10 5G is the device
both screen and digitizer broken, I'm not able to see the screen or use touch (but I'm 100% sure the phone still works)
Android 12 rom (xiaomi.eu stable)
custom recovery available
rooted device
usb debugging enabled
no device authorized by the phone for usb debug
I found somewhere on xda that the problem could be solved by mounting/unmountind sdcard, but I have no ideea hoe to do that
damndaniel0 said:
hi guys I need help to recover some personal photos I had saved on my device. The phone has a broken screen and touch so I cannot use a mouse or try to blindly unlock it, but it has been rooted and usb debugging is enabled; unfortunately my pc is not authorized by the phone and I have no way to authorize it through the pop up without a screen. I have searched around many forums to find a solution but it seems every time there was something wrong, so I need some help.
The solution that got me the nearest to a conclusion that I tried are:
using adb in custom recovery (which I do have) and trying commands like "adb pull /sdcard" which resulted in "pull: building file list... 0 files pulled. 0 files skipped.", I don't understand why it's unable to pull any file.
trying to authorize usb debugging for my pc through adb by "adb push adb_keys /data/misc/adb", adb_keys is the adbkey.pub file in the .android folder renamed. I can confirm i pushed them since "adb pull /data" pulled "data/adb/misc/adb_keys" as the only file, but I still don't have authorization
I'm not too literate in this kind of commands so please be patient but I really need help
RECAP OF MY PHONE STATUS
Xiaomi Mi 10 5G is the device
both screen and digitizer broken, I'm not able to see the screen or use touch (but I'm 100% sure the phone still works)
Android 12 rom (xiaomi.eu stable)
custom recovery available
rooted device
usb debugging enabled
no device authorized by the phone for usb debug
Click to expand...
Click to collapse
There is a way to do it, but it costs money
@damndaniel0
If USB-MTP mode is enabled on phone - what should be default - then you can access all user-data stored in /storage/emulated/0 directory where among others photos are stored.
See also here:
MTP USB Device Driver Windows 10 64bit Driver | Device Drivers
MTP or (Media Transfer Protocol) is a set of custom extensions to the Picture Transfer Protocol (PTP) devised by Microsoft, to allow the protocol to be used for devices other than digital cameras, for example digital audio players such as MP3 players, and other portable media devices, for...
oemdrivers.com
xXx yYy said:
@damndaniel0
If USB-MTP mode is enabled on phone - what should be default - then you can access all user-data stored in /storage/emulated/0 directory where among others photos are stored.
See also here:
MTP USB Device Driver Windows 10 64bit Driver | Device Drivers
MTP or (Media Transfer Protocol) is a set of custom extensions to the Picture Transfer Protocol (PTP) devised by Microsoft, to allow the protocol to be used for devices other than digital cameras, for example digital audio players such as MP3 players, and other portable media devices, for...
oemdrivers.com
Click to expand...
Click to collapse
If you mean simply to connect the phone through usb to pc, I cannot do that because MIUI asks everytime if I want to transfer photos, files or just charge with a pop up on screnn (which I obviously cannot do)
iBowToAndroid said:
There is a way to do it, but it costs money
Click to expand...
Click to collapse
what would it be
damndaniel0 said:
If you mean simply to connect the phone through usb to pc, I cannot do that because MIUI asks everytime if I want to transfer photos, files or just charge with a pop up on screnn (which I obviously cannot do)
Click to expand...
Click to collapse
Not in system but in custom recovery (which you do have).
Timmmmaaahh! said:
Not in system but in custom recovery (which you do have).
Click to expand...
Click to collapse
Honestly I did not try, but I don't remember the phone directory showing up in windows file explorer after connecting the phone in recovery mode, I'll try againg when I'm home and I'll let you know
anyway I checked and no, I cannot access phone files
In Recovery mode you should can run
Code:
adb devices
adb pull <LOCATION_OF_DATA_OF_INTEREST> <STORAGE_LOCATION_ON_PC>
xXx yYy said:
In Recovery mode you should can run
Code:
adb devices
adb pull <LOCATION_OF_DATA_OF_INTEREST> <STORAGE_LOCATION_ON_PC>
Click to expand...
Click to collapse
unfortunately the result of this operation is always "pull: building file list... 0 files pulled. 0 files skipped". I tried already to pull form /sdcard, /storage, /data. Am I getting the location wrong?