Get Root Acces for ADB - General Questions and Answers

I've rooted my Samsung Galaxy J5 to access data from an app. When I try to get the data via "adb pull" on my PC, I will be denied access. After some research I found out that i have to assign root rights to the ADB. However, when I run the command "adb root" I get the following error message: "adbd cannot run as root in production builds"
To work around that problem, I installed "adbd insecure" on my smartphone.
[2014.11.10][ROOT] adbd Insecure v2.00 | XDA Developers Forums (xda-developers.com)
But every time the connection between PC and smartphone breaks off as soon as I tick "Enable insecure adbd" and my PC no longer detects my smartphone. Does anyone have any idea why that might be? Or does someone know another way to assign root rights to the ADB? I'm just really desperate and would be happy about any help

Just use Termux and do it with your phone instead. You can grab the app from Google play or fdroid. Alternatively, use a root explorer, navigate right to the app's folder, and copy it wherever you want. Option #2 is the easiest.

Spaceminer said:
Just use Termux and do it with your phone instead. You can grab the app from Google play or fdroid. Alternatively, use a root explorer, navigate right to the app's folder, and copy it wherever you want. Option #2 is the easiest.
Click to expand...
Click to collapse
Thank you for your answer.
I tried to copy the file and paste it somewhere else, but it doesn't work. I can copy it, but when I hit paste, nothing happens.

Thoriad said:
Thank you for your answer.
I tried to copy the file and paste it somewhere else, but it doesn't work. I can copy it, but when I hit paste, nothing happens.
Click to expand...
Click to collapse
Make sure it has root permissions, and permission to access internal storage. What app are you using to do this?
Edit: Where are you trying to copy it to?

Spaceminer said:
Make sure it has root permissions, and permission to access internal storage. What app are you using to do this?
Click to expand...
Click to collapse
Ahh, it had no permission to access internal storage. Now it's working
Thank you very much for your help!!

Good stuff!

By design adb root command works in development builds only (i.e. eng and userdebug which have ro.debuggable=1 by default). Alternatively you could use modified adbd binary (which does not check for ro.debuggable)

THIS IS DETAILS MY PHONE!
=================
Model : 5056D
Brand : TCL
Manufacturer : TCL
Hardware : qcom
Codename : POP455C
Device Type : GSM
IMEI Number Slot 1 : 356999071650249
IMEI Number Slot 2 : 356999071650256
Serial Number : d8da6a98
NFC : Unsupported
Root Access : Not Rooted
=================
Shared from : SIM Device Info
NOTE: For security reason please delete after use!

Related

Iball Slide Tablet Rooted..(Perm Root)

I am not Responsible for any kind of damage..This post is for educational purpose only...
This forum contains Farhan's method of rooting..I have not personally achieved root access employing that..So I am writing down an easy method which grants root permission to your Iball tablet..
Download(See the attachments..)
1. Root explorer(preferably v2.17.1)
2. Gingerbreak v1.20
3. Root Check.
See the attachments..
These are enough for rooting.. Install RootExplorer and open it. Navigate via RootExplorer to /default.prop..
1. Press it for 2 seconds, then "open it" via text editor.
2. Edit the file default.prop to change the value ro.secure=0 (instead of the given value stock ro.secure=1)
3. Now press the back button, which gives a 'save" dialogue..Save it, and you see the original file is saved with the name "default.prop.bak".
4. Open your cmd.exe in windows and type adb shell..You should see a # instead of $..Now install and open the Root Checker, click "Verify Root Access", and then with a lot of frustration you will see "Sorry, you don't have root access"..
Don't be frustrated, I am here to help you out!!
5. Now install Gingerbreak, and open it, click "Root device"..It will take some time to run the exploit..then the device will automatically shut down..
6. Power on your device manually, it will take a little bit time more than usual. leave it for 1 minute after you see your unlock screen, then unlock it.
7.Go straight to menu>root Check..It will ask for SuperUser permission, Click ok>Veryfify Root Access..And then you will obviously see "Congratulations! You have root access!"
If you own success, please thank me, I have not copied someone's procedure, this procedure is completely discovered by me after going through lots of tutorials regarding android development, and now I am also capable of building some basic apps for android..
gourab4u said:
I am not Responsible for any kind of damage..This post is for educational purpose only...
This forum contains Farhan's method of rooting..I have not personally achieved root access employing that..So I am writing down an easy method which grants root permission to your Iball tablet..
Download(See the attachments..)
1. Root explorer(preferably v2.17.1)
2. Gingerbreak v1.20
3. Root Check.
See the attachments..
These are enough for rooting.. Install RootExplorer and open it. Navigate via RootExplorer to /default.prop..
1. Press it for 2 seconds, then "open it" via text editor.
2. Edit the file default.prop to change the value ro.secure=0 (instead of the given value stock ro.secure=1)
3. Now press the back button, which gives a 'save" dialogue..Save it, and you see the original file is saved with the name "default.prop.bak".
4. Open your cmd.exe in windows and type adb shell..You should see a # instead of $..Now install and open the Root Checker, click "Verify Root Access", and then with a lot of frustration you will see "Sorry, you don't have root access"..
Don't be frustrated, I am here to help you out!!
5. Now install Gingerbreak, and open it, click "Root device"..It will take some time to run the exploit..then the device will automatically shut down..
6. Power on your device manually, it will take a little bit time more than usual. leave it for 1 minute after you see your unlock screen, then unlock it.
7.Go straight to menu>root Check..It will ask for SuperUser permission, Click ok>Veryfify Root Access..And then you will obviously see "Congratulations! You have root access!"
If you own success, please thank me, I have not copied someone's procedure, this procedure is completely discovered by me after going through lots of tutorials regarding android development, and now I am also capable of building some basic apps for android..
Click to expand...
Click to collapse
is this all that has to done to root the iball slide i7218 ?? if not can u please explain what other prerequisites are necessary.
gourab4u said:
4. Open your cmd.exe in windows and type adb shell..You should see a # instead of $..Now install and open the Root Checker, click "Verify Root Access", and then with a lot of frustration you will see "Sorry, you don't have root access"..
Don't be frustrated, I am here to help you out!!
Click to expand...
Click to collapse
when i type adb shell in cmd the response is 'adb' is not recognised as an internal or external command, operable program or batch file.
what does it mean ?
vivdutta said:
when i type adb shell in cmd the response is 'adb' is not recognised as an internal or external command, operable program or batch file.
what does it mean ?
Click to expand...
Click to collapse
this means that you do not have adb.exe in the same directory as the commands you are typing
I can't root my iball slide q45. I tried farmroot, towelroot, kingroot, king pro root, kingo root, gingerroot, z4root. Plz give me solution.

[GUIDE][HOW-TO]Crack android pattern lock!

Dislcaimer: this is for educational purposes only,you shall not use this on other people phones without permission under any circumstances,and am not responsable to any misuse of this hack
Click to expand...
Click to collapse
ok so not long ago i had a problem with a locked android device with a pattern and i managed to unlock it using adb,so here's how in case you were stuck one day with a locked device.
the device needs to have usb debugging enabled in case usb debugging isn't enabled and you have cwm you can run the same instructions from cwm,root is not required (though it will be so better if the device was rooted)
this was tested on:gingerbread,ice cream sandwich and jelly bean.
both method are through adb.
method 1:
Code:
adb shell
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
.quit
-AND/OR-
method 2:
Code:
adb shell rm /data/system/gesture.key
and that's a video showing how method 2 is done (thanks to melvinchng) : http://www.youtube.com/watch?v=tVJ7T2oC_Zs&feature=player_embedded
you can try both of them,here is how i managed to remove the lock:
1- run the first method.
2-reboot
3-run the second method
4-reboot
NOTES:
-in the first method each line is a seperate command so click enter after typing each line.
-in the second method type all the command and then press enter.
-after running both methods and rebooting you may see the pattern lock,that doesn't necessarily mean it doesn't work,just try any random pattern and it may unlock then remove the pattern from settings.
-this may and may not work,it may work on some devices and don't on others,so all you can do is trying it but i can't assure it will work.
a small donation would be much appreciated thank (check my signature)
But What if i remember the password well enough, but didnt have data enabled the moment it got locked?
Explained elaborately here>>>http://forum.xda-developers.com/showthread.php?p=29963687
It will unlock either (Loook at the time of message above - I am time traveler )
i have better method than bot the above ones
look for smudges on the phone
Do the files need to be restored or are they just the user data for the pattern locks?
This is really great...
i wonder how do you discover this
you must be a hacker
Or you could boot into recovery backup data
wipe factory reset and reboot
Could try restoring data but most likely restore pattern lock
Or simply enter your gmail address as requested
2nd option...
if you have Custom recovery
use AROMA File Explorer and you can do the same thing through the recovery
or adb through the recovery
FWIW, on CM10 neither method works as non-root. Yay CyanogenMod.
Method #1 FAIL:
1|[email protected]:/data/data/com.android.providers.settings/databases $ ll
opendir failed, Permission denied
255|[email protected]:/data/data/com.android.providers.settings/databases $ sqlite3 settings.db
Error: unable to open database "settings.db": unable to open database file
Method #2 FAIL:
[email protected]:/data $ ll /data/system/gesture.key
-rw------- system system 20 2012-08-11 04:51 gesture.key
[email protected]:/data $ rm /data/system/gesture.key
rm failed for /data/system/gesture.key, Permission denied
(I use faceunlock + pattern (mostly to keep my kid outta my phone), but if I actually cared more about security I'd encrypt my phone and use a passphrase instead)
This is a useful guide, thanks, I will try it :good:
So I guess if Debugging wasn't previously enabled, you have no chance to unlock it...
I've noticed a locked Archos tablet in a shop (probably some stupid shopper locked it) and when I saw this thread announced on the first page I was thinking of helping the shop owner. But I guess I cannot.
Have a nice day!
I don't know whether this method can use on neither:
Rooted
Installed Busybox
Rom Version Older or Newer than CM7
This method require ADB Debugging On & A PC & A tool Provided
I found this trick a long time ago
I come for sharing
Click to expand...
Click to collapse
Download the By-pass security Hack.7z
http://www.mediafire.com/download.php?li2686c3jenmen6
Click to expand...
Click to collapse
Primary Step for all method:
Click to expand...
Click to collapse
Extract it to anywhere using 7-zip.
Open SQLite Database Browser 2.0.exe in SQLite Database Browser.
Run pull settings.db.cmd inside By-pass security Hacks folder to pull out the setting file out of your phone.
Drag settings.db and drop to SQLite Database Browser 2.0.exe program.
Navigate to Browse data tab, At table there, click to list down the selection & selete secure
Instruction To Remove Pattern Lock:
Click to expand...
Click to collapse
Now, find lock_pattern_autolock, Delete Record
Close & save database
Run push settings.db.cmd and reboot your phone
Instruction To Remove PIN Lock:
Click to expand...
Click to collapse
Now, Find Or Create lockscreen.password_type, double-click & change it's value to 65536, Apply changes!
Now, find lock_pattern_autolock, Delete Record, If doesn't exist, Ignore
Close & save database
Run push settings.db.cmd and reboot your phone
Instruction To Remove Password Lock:
Click to expand...
Click to collapse
Now, find lockscreen.password_salt, Delete Record
Now, find lockscreen.password_type, Delete Record
Close & save database
Run push settings.db.cmd and reboot your phone
hmmm i hope those thief's don't find these thread lol
zmore said:
FWIW, on CM10 neither method works as non-root. Yay CyanogenMod.
Click to expand...
Click to collapse
Nor does either method work on unrooted Galaxy Nexus with stock Jelly Bean. Yay stock Android.
mixtapes08 said:
hmmm i hope those thief's don't find these thread lol
Click to expand...
Click to collapse
don't leave usb debugging checked on then.
I advise you guys to also post your Android version. My opinion is that the security hole that permits this hack has been removed in JellyBean, maybe even in an earlier version.
I will try it too a little later, just for the fun's sake.
aussiebum said:
don't leave usb debugging checked on then.
Click to expand...
Click to collapse
If you have forgotten to leave USB debugging enabled, reboot your phone into recovery and do the same. No USB debugging required.
You may however need to mount the partition being accessed by this method, and you can do that only if you have a custom recovery installed (which you more-than-likely have, since you're here on XDA). Just go to 'Mounts and Storage' and mount /data. Then use the method just the normal way. Cheers!
Useful guide for sure. Will keep this as reference!
Does this only work for the pattern unlock or will it also work on the password or the PIN unlock screen?
I can confirm that it is working on a CM7.2 Motorola Defy.
Thanks m.sabra!

[script]replace kingroot's kinguser with supersu

Remove KingRoot’s KingUser with SuperSU using Terminal [Requires Intermediate skills]
This method works for almost all the android devices and works the best, However, it requires some decent skills to follow the instructions and copy the commands listed below into the Terminal app.
The link of the script which is shared below works without a computer system/PC, Hence the steps I’m listing below won’t require a computer PC. So are you ready?
Downloads
This download section has the download links to the files or apps you will require to complete the below listed steps. Ready to shift from KingUser to SuperSU? What are you waiting for?
lets begin.
1.Download & Install Terminal Emulator App
2.Download SuperSu script from here http://www.mediafire.com/file/mxzbt42xypvn2ts/Replace_Kinguser_with_SuperSU-v2.4.zip and unzip it!
Steps to Replace KingUser with SuperSU?
Step 1: Extract the Replace_Kinguser_with_SuperSU ZIP File & Transfer the extracted version to Internal storage of device.
Install the Terminal app for Android and extract the Replace_Kinguser_with_SuperSU file and after extracting the Replace_Kinguser_with_supersu file transfer the “Extracted Folder – MRW” to outermost directory in the internal storage.
Step 2: Open Terminal Android App & Write the Following commands in the Android Terminal.
Open the terminal android app type the command “su” in the terminal, after writing the SU in terminal, you will be prompted with the message box asking you to deny/grant the functions. Granting permission will help you remove the kinguser on your smartphone.
After granting permissions you will have to type one single line of code, The other command will be: sh /sdcard/mrw/root.sh
After writing the above command, it might show some error, but ignore that error, it will automatically launch SuperSU, in case it doesn’t manually open SuperSU.
Once done, Restart your smartphone and you will see that SuperSU works flawlessly on your Smartphone. That’s all, you’ve successfully replaced KingRoot’s KingUser with Chainfire’s SuperSU.
Huge thanks to the Dev of the script
Source and Download link credits goes to Droidmen.com
Thread link of Droidmen: https://www.droidmen.com/remove-kingroot-kinguser-with-supersu/
I shared this guide from droidmen if you found this guide useful PLEASE HIT THANKS BUTTON!​
RESERVED
Good
Sent from my Redmi Note 3 using Tapatalk

			
				
can anyone confirm it in above 4.4 ?
sohamsen said:
can anyone confirm it in above 4.4 ?
Click to expand...
Click to collapse
Well it works on 4.4.2 but you need you manually uninstall kinguser in system after.
Arkonite said:
Well it works on 4.4.2 but you need you manually uninstall kinguser in system after.
Click to expand...
Click to collapse
mine uninstalled automatically
Replace kingroot with supersu
Here you can get the most effective way to replace kingroot with supersu;
How to replace kingroot with supersu
King roots

X88 Pro 10 full access issues

Okay let me start by saying I have been modifying android boxes for several years so the question that I ask is not because I've never done it before. I recently purchased the X88 Pro 10 media box. It has Android 11 as the O/S, and the firmware for the device is from Oct. 2021. I turn on the developer options and try to access the device using ADBlink via the Ip address without success. I then connect the device to my laptop via a usb cable connection and I'm able to install an APK though my ability to go in and access or modify files and folders is limited. Has anyone else had this issue and what were you able to do to overcome the issue?
I just picked one of these up to use as an Android 11 test kit. Unfortunately, the developers who built the Android disabled wireless adb debugging! Luckily, the box is rooted at the factory so I was able to add it in. Connect via USB, su to root, mount / as rw (mount -o rw,remount / ) and add this line to the end of /system/build.prop
Code:
service.adb.tcp.port = 5555
This change to build.prop is persistent after resets so you only have to do it once.
I'm using ad link 4.8, I'm connected to the device via USB to see the device, and have the ADB Shell open. however I must be typing in the commands in wrong. See attachment. Please assist.
Thank you.
ThirdStarr said:
I'm using ad link 4.8, I'm connected to the device via USB to see the device, and have the ADB Shell open. however I must be typing in the commands in wrong. See attachment. Please assist.
Thank you.
Click to expand...
Click to collapse
Looking at your screenshot, it appears that you have successfully gained root access (the # prompt). Your next steps :
mount the / partition as rw:
Code:
mount -o rw,remount /
Add code to the end of /system/build.prop
Code:
echo "service.adb.tcp.port = 5555" >> /system/build.prop
mount the / partition as ro:
Code:
mount -o ro,remount /
This worked for me. YMMV
Thank you for the assist. That allowed me access to the device via up address.
The only issue I have now is that all the Kodi folders and files are hidden when you try to use File Manager in adbLink. This device has been the biggest bear to work with.. Once again thank you for the assistance and patiences
ThirdStarr said:
Thank you for the assist. That allowed me access to the device via up address.
The only issue I have now is that all the Kodi folders and files are hidden when you try to use File Manager in adbLink. This device has been the biggest bear to work with.. Once again thank you for the assistance and patiences
Click to expand...
Click to collapse
In the device record, check the "disable root" checkbox, save the record, then disconnect the device. When you reconnect the file manager should work.
I did as you suggested and rebooted the device.
I was only able to access this far in file manager
ThirdStarr said:
I did as you suggested and rebooted the device.
I was only able to access this far in file manager
Click to expand...
Click to collapse
For Android 11, Google has implemented scoped storage which removes the ability for external applications (or the normal shell) to read/write in /sdcard/Android/data/. You can still access this area via the shell as the root user. File manager won't work as root on this device, sorry.
Ok I understand. Thank you very much
Hello i'm on android 11, how i can use the root access? Doesn't work for me
I no longer have this device. Good luck!
hi i am kumar, regarding my x88 pro 10 android 11 i am facing a issue that i can connect to other hotspot or wifi network. i can't connect to my home wife that at the below of thw wifi name (check password and try again). i change my password in router page and try back with the new password still it shows like that. may i know why?

[Q] How to edit camera features file

I want to edit camera_features.xml file but it needs root access, I don't want to root device but I think there is a way through ADB or using some third party apps that uses super user permission to edit root files
Please I'm sure there is way to edit it without rooting device by using special third party apps but I need someone who know how to
Temporarily root Android by putting a suitable su binary into Android's filesystem - preferably /data/loca/temp - and making it executable.
https://forum.xda-developers.com/attachments/su-binaries-zip.5566949/
I don't find the directory data/local
And does it require root to put the su file there
Noticed that I made a spelling mistake:
The directory recommended to copy su binary into is
/data/local/tmp
what exists on all Android versions since beginning and by default is mounted as RW
How can I reach the folder, which app can reach and copy files to root data/local/tmp without rooting device
You use ADB - of course requires USB DEbugging got enabled on device in question.
To clarify things: the su binary is the root functionality you want to add to Android.
I tried to use adb push su data/local/tmp but it doesn't work
xXx yYy said:
You use ADB - of course requires USB DEbugging got enabled on device in question.
To clarify things: the su binary is the root functionality you want to add to Android.
Click to expand...
Click to collapse
I know but I think there is another way using apps that uses system apps permissions
Such as editing root file of the device as official device updater

Categories

Resources