Hello!
I have an iPhone (6S Plus) clone with a MT6735P
but I can't root it. I tried many tools.
KingRoot, Kingo Root, iRoot and a chinese tool --> This chinese tool shows me root, I click on it, it stops at 15% and then gives me a message with one button (for retry the root I suppose) and sometimes an other message with two buttons.
USB Debugging is enabled, the drivers are correctly installed..
I tried the root with ADB (with this -> http://forum.xda-developers.com/showthread.php?t=2684210) but it doesn't work because when I type "adb devices", nothing appear in "List of devices attached".
EDIT : I tried UsbDriverTool and adb shows "offline device"... What should I do?
EDIT 2 : Resolved thanks to Wondershare Mobile GO. But when I try to root it with adb, it says :
adb push su /data/local/tmp
cannot stat 'su': No such file or directory
adb push busybox /data/local/tmp
cannot stat 'busybox': No such file or directory
adb push Superuser.apk /data/local/tmp
cannot stat 'Superuser.apk': No such file or directory
EDIT 3 : Resolved too. Idk how.
.
I have an issue with the rear camera. It's blurry in the center and distorted but when I put something in front of it, it focus verry well... There's no dust or scratches...
Thank you.
Related
SuperSU works fine and grants permission to Root Explorer which also works fine.
But 'getprop: permission denied' is shown in front of most of the headings in 'Phone information' tab in MTK Droid Tools.
And when I click 'Root' button in MTK Droid Tools the following message is shown 'ERROR: SU inaccessible'.
I have granted permission to ADB Shell in SuperSU.
If I manually open adb shell I get $ prompt and then I type su to get # prompt.
I think that maybe permissions of some files are not ok.
Please help!
threatalive said:
SuperSU works fine and grants permission to Root Explorer which also works fine.
But 'getprop: permission denied' is shown in front of most of the headings in 'Phone information' tab in MTK Droid Tools.
And when I click 'Root' button in MTK Droid Tools the following message is shown 'ERROR: SU inaccessible'.
I have granted permission to ADB Shell in SuperSU.
If I manually open adb shell I get $ prompt and then I type su to get # prompt.
I think that maybe permissions of some files are not ok.
Please help!
Click to expand...
Click to collapse
I know I am bumping this thread, but someone recently asked me the solution for this issue.
So, for anyone who might face the same problem: this error occurs due to broken symlinks of toolbox or busybox etc.
To fix it, you need to create the missing symlinks.
A simple solution is to re-root your mobile.
Hello,
Veteran SW guy here; but newbie at Android.
I have three tablets. All of them are Ematic Model EGS004. All three were bought for the sole purpose of being used by children to watch educational videos (in mp4 and flv formats) and read PDF documents. Absolutely nothing else. No games. No internet access whatsoever. Etc.
Two of the tablets are still in the box and have not been touched. I'm hoping that they may be useful for making/restoring an original image of the tablets.
To implement the requirements of this project, I did the following to one of the tablets:
1) Used the instructions at http://forum.xda-developers.com/showthread.php?t=2495069 to get root access with Cydia Impactor and Chainfire SuperSU.
2) Installed Titanium Backup (root). Using this, I uninstalled most of the Google applications (excluding Google Play), messager, YouTube, games, etc.
3) Installed File Manager (Explorer) by Rhythm Software.
4) Installed Shell Terminal Emulator by MobilDev. Using the shell, I went to the /system/lib directory and renamed libwifidisplay.so
and libwpa_client.so to libwifidisplay.disabled and libwpa_client.disabled.
Unfortunately, upon reboot, the tablet gets stuck in the bootup screen (with the ematic logo). Obviously, something about Android causes a hang if an expected kernel module is missing...
I tried using the shell in Cydia Impactor. But, the file system was read only. I tried:
mount -o rw,remount /system
But, I get an "Operation not permitted" since I am not root.
I downloaded the ADB bundle for windows at http://developer.android.com/sdk/index.html#download and successfully installed adb on my PC. I could get into a shell with the "adb shell" command. But, the /system/lib directory still is read only and I can't seem to remount it since I am not root.
I tried "adb remount". "Operation not permitted" was the result, again.
Cydia Impactor installs its "su" binary in /system/xbin. I tried running it from there using various invocations like "su -c mount -o rw,remount /system" Each time, the shell hung and I never got a shell prompt afterwards.
Questions:
1) Surely there's a way that I can get back in to rename these files now... I can "ls" them from the adb shell. I can pull them to my PC with adb pull. (adb put doesn't work either since the file system is read only.) Ideas?
2) Once I get this solved, what is the best way to get rid of the wireless capability so that children can never use it? I would like to move videos and PDF's between it and a PC strictly via USB.
3) Is there a way to image/restore one of the untouched tablets - or, for that matter, this one once its up and running like it needs to be?
Thanks everyone!
Jim
Let's try a simpler question since there have been no responses:
Once I get into a shell (non-root) using ADB or Cythia Impactor, I believe I can rename the files if I can only get SuperSU to work. However, when I invoke su, the shell hangs:
su -c ls
su
etc. All of these hang. I assume that SuperSU is waiting for a confirmation from the android display. But, since I'm stuck at the startup screen, there's never an opportunity. How can I get the shell to interact with me as root so that I can remount the file system as RW and rename files?
Thanks,
Jim
rivkah613 said:
Hello,
Veteran SW guy here; but newbie at Android.
I have three tablets. All of them are Ematic Model EGS004. All three were bought for the sole purpose of being used by children to watch educational videos (in mp4 and flv formats) and read PDF documents. Absolutely nothing else. No games. No internet access whatsoever. Etc.
Two of the tablets are still in the box and have not been touched. I'm hoping that they may be useful for making/restoring an original image of the tablets.
To implement the requirements of this project, I did the following to one of the tablets:
1) Used the instructions at http://forum.xda-developers.com/showthread.php?t=2495069 to get root access with Cydia Impactor and Chainfire SuperSU.
2) Installed Titanium Backup (root). Using this, I uninstalled most of the Google applications (excluding Google Play), messager, YouTube, games, etc.
3) Installed File Manager (Explorer) by Rhythm Software.
4) Installed Shell Terminal Emulator by MobilDev. Using the shell, I went to the /system/lib directory and renamed libwifidisplay.so
and libwpa_client.so to libwifidisplay.disabled and libwpa_client.disabled.
Unfortunately, upon reboot, the tablet gets stuck in the bootup screen (with the ematic logo). Obviously, something about Android causes a hang if an expected kernel module is missing...
I tried using the shell in Cydia Impactor. But, the file system was read only. I tried:
mount -o rw,remount /system
But, I get an "Operation not permitted" since I am not root.
I downloaded the ADB bundle for windows at http://developer.android.com/sdk/index.html#download and successfully installed adb on my PC. I could get into a shell with the "adb shell" command. But, the /system/lib directory still is read only and I can't seem to remount it since I am not root.
I tried "adb remount". "Operation not permitted" was the result, again.
Cydia Impactor installs its "su" binary in /system/xbin. I tried running it from there using various invocations like "su -c mount -o rw,remount /system" Each time, the shell hung and I never got a shell prompt afterwards.
Questions:
1) Surely there's a way that I can get back in to rename these files now... I can "ls" them from the adb shell. I can pull them to my PC with adb pull. (adb put doesn't work either since the file system is read only.) Ideas?
2) Once I get this solved, what is the best way to get rid of the wireless capability so that children can never use it? I would like to move videos and PDF's between it and a PC strictly via USB.
3) Is there a way to image/restore one of the untouched tablets - or, for that matter, this one once its up and running like it needs to be?
Thanks everyone!
Jim
Click to expand...
Click to collapse
Erratic Ematic
rivkah613 said:
Let's try a simpler question since there have been no responses:
Once I get into a shell (non-root) using ADB or Cythia Impactor, I believe I can rename the files if I can only get SuperSU to work. However, when I invoke su, the shell hangs:
su -c ls
su
etc. All of these hang. I assume that SuperSU is waiting for a confirmation from the android display. But, since I'm stuck at the startup screen, there's never an opportunity. How can I get the shell to interact with me as root so that I can remount the file system as RW and rename files?
Thanks,
Jim
Click to expand...
Click to collapse
I rooted my son's EGS004, installed busybox, and played around with it without any apparent problem. When I rebooted it, I was prompted to set up the device then and every subsequent time I rebooted it. I could not install any apps and could not redo the Cydia Impactor rooting procedure. The reason was that /data was reporting itself as 0.00B in size. Factory reset didn't change anything. Ematic wants me to return it.
Your issue sounds different, but it could be something as simple as the device being very unforgiving. There's a pinhole with a reset button (never worked for me but tech support suggested it) which may help.
Hi guys..
I ve rooted my quattro by Kingo root methed.
and i installed chainfire 3D, while installing driver it says " IT MAY STOP REBOOTING YOUR DEVICE" but i tried..... :silly:
But now my mobile stopped rebooting... whenever i try to start the logo "samsung galaxy grand quattro" comes and still stands...:crying:
is it died?:silly:
hii
Yabee said:
Hi guys..
I ve rooted my quattro by Kingo root methed.
and i installed chainfire 3D, while installing driver it says " IT MAY STOP REBOOTING YOUR DEVICE" but i tried..... :silly:
But now my mobile stopped rebooting... whenever i try to start the logo "samsung galaxy grand quattro" comes and still stands...:crying:
is it died?:silly:
Click to expand...
Click to collapse
Try flashing it using odin
CHAINFIRE 3D IS NOT TO BE USED ON JELLYBEAN WHY DON'T PEOPLE UNDERSTAND IT IS NOT FOR 4.0+?
Sent from my GT-I8552 using Tapatalk
GOT SOLUTION ( Chainfire 3D softbrick on samsung)
Please follow this instruction carefully
After you follow this:
... Download ADB here: url
...1. extract the file you just download
...2. put it in C: (so you can access it easily)
...3. you can rename it (you can name it anything you want but we will use "Android-adb" in this tutorial)
...4. open SDK Manager.exe
...5. make sure that Android SDK tools, Android SDK Platform-tools, Android SDK Build-tools and Google USB Driver is installed
Then you follow this:
>reboot your phone in recovery mode (remember, ONLY IN RECOVERY MODE, DONT CONTINUE TO "APPLY UPDATE ADB", JUST STAY IN RECOVERY MODE)
>plug in your devices in USB,
>go to CMD (command prompt)
>type this: "cd c:\Android-adb\sdk\platform-tools" without quotes / quotemarks
>type "adb" without quotes / quotemarks
>type "adb shell" without quotes / quotemarks
>it will automatically type "[email protected]:/ $" so continue it with typing "su" after that, so it will be seen like: "[email protected]:/ $ su"
>it will automatically type for you again, "[email protected]: #" so continue it with typing "system/lib/cf3d_uninstal.sh" after that, so it will be seen like "[email protected]:/ # /system/lib/cf3d_uninstall.sh"
>ignoring all the fail and your device will rebooted and just fine
If you followed the instruction carefully, the CMD will seen like this
htt*p://s29.*postimg.*org/*tgq844hzb/*dev.*png
(delete all the "*"):victory::laugh:
Yabee said:
Please follow this instruction carefully
After you follow this:
... Download ADB here: url
...1. extract the file you just download
...2. put it in C: (so you can access it easily)
...3. you can rename it (you can name it anything you want but we will use "Android-adb" in this tutorial)
...4. open SDK Manager.exe
...5. make sure that Android SDK tools, Android SDK Platform-tools, Android SDK Build-tools and Google USB Driver is installed
Then you follow this:
>reboot your phone in recovery mode (remember, ONLY IN RECOVERY MODE, DONT CONTINUE TO "APPLY UPDATE ADB", JUST STAY IN RECOVERY MODE)
>plug in your devices in USB,
>go to CMD (command prompt)
>type this: "cd c:\Android-adb\sdk\platform-tools" without quotes / quotemarks
>type "adb" without quotes / quotemarks
>type "adb shell" without quotes / quotemarks
>it will automatically type "[email protected]:/ $" so continue it with typing "su" after that, so it will be seen like: "[email protected]:/ $ su"
>it will automatically type for you again, "[email protected]: #" so continue it with typing "system/lib/cf3d_uninstal.sh" after that, so it will be seen like "[email protected]:/ # /system/lib/cf3d_uninstall.sh"
>ignoring all the fail and your device will rebooted and just fine
If you followed the instruction carefully, the CMD will seen like this
htt*p://s29.*postimg.*org/*tgq844hzb/*dev.*png
(delete all the "*"):victory::laugh:
Click to expand...
Click to collapse
Before you run the uninstall.sh script you may need to remount the /system partition in read/write mode with the following command. On my OneTouch 5020T the /system partition is in read-only mode.
This command will place it in read/write mode:
mount -oremount,rw /system
--Mouse2600
All mtk 65xx rooting
WELCOME TO MY FIRST EVER THREAD
ALL MTK65XX ROOTING FIXES AND LINKS
Don't be dumb...
BOOT LOADER UNLOCKING WIPES USER DATA
INSTALLING SUPERUSER WITHOUT FIXING BIN PERMISSIONS
WILL RENDER YOUR DEVICE IMPOSSIBLE TO ROOT WITH ALWAYS
GETTING SU IS INACCESSIBLE
Most people find framaroot doesn't work
So I Figured this out and made a whole account
just to share so please,
Excuse my lack of experience with this post stuff
************************************************
******* UNLOCKING BOOTLOADER ***********
************************************************
Skip this section to leave bootloader and user data
Exactly the same as normal...
STEP - Connect Phone/Tab Via USB Cable
STEP - ENABLE USB DEBUGGING ON PHONE/TAB
(IMPORTANT)
STEP - INITITATE A COMMAND WINDOW IN
A FOLDER CONTAINING ADB AND FASTBOOT
STEP TIP - Make a simple text document
and write cmd then rename it from .txt to .bat
and open it...
This will work as a batch file to initiate a
command window in whatever location you put it...
STEP - RUN COMMAND -- adb reboot bootloader
STEP - RUN COMMAND -- fastboot oem unlock
STEP - PRESS VOLUME UP ON YOUR DEVICE
TO UNLOCK THE BOOTLOADER
STEP - RUN COMMAND -- fastboot reboot
STEP - AS DEVICE BOOTS UP .. RUN COMMAND --
adb devices
STEP - Once your device is up and running with
unlocked bootloader
*****************************************
************QUICK ROOTING ***********
*****************************************
OPEN COMMAND WITH ADB AND WRITE THESE CODES
EXACTLY.
adb root
adb remount
...
If you get errors Or command window freezes,
Unplug device and close window, Replug device
Open Command window again and Run Commands..
adb root
adb remount
.
ONCE YOU SEE - REMOUNT SUCCEDED
YOU CAN NOW PUSH FILES LIKE SUPERUSER
AND BUSYBOX VIA COMMAND
(Warning)
Pushing superuser via adb is highly impractical as you will
need to fix permissions manually via adb shell ..(Time Hungry)
adb push superuser.apk /system/app/
adb push busybox /system/bin/
Etc. Etc.
Alternatively OPEN --MTK DROID TOOLS
(Recommended)
IT WILL DISPLAY ROOT SHELL GRANTED !
IMMEDIATELY RUN A NANDROID BACKUP WITH IT
AND AN NVRAM/IMEI BACKUP.. THEN PROCEED..
If it displays su binary found but is inaccessible
.. You have stuffed the /system/xbin/su permissions
So you need to reflash from stock ...
Enabling Easy backup and install of superSU + busybox +mobileUncle
EXTRA FILES AND NEEDED FILES
MTK Droid Tools -- http :/ /ge.tt/m/ 2P16x3 G1 ...Remove the spaces
If you don't see a download button
Click on the file name MTK_etc... and
Download or Share should pop up from the bottom
This is the latest version.. If you need adb it has a launch adb
Button in program.. Also just copy fastboot.exe to the folder for
Easy changing to fastboot in commands...
P.s If you hit errors ..
Usually just unplug and restart command window... Then replug
Any major errors use SP Flashtool to reflash stock backup in
Step 1 .. Shouldn't encounter too many errors..
If your updating ROMs and screen blacks out or lines show on screen
You neep SP Flashtool (Test-Version) To change LCD drivers
While updating.. I'm only providing a link for mtk droid tools cause
You can Google stuff I imagine
Here is how I succeeded to enable USB debugging (also adb and remote view) on Samsung Galaxy Note 4 with broken screen.
1. Following the DeathDrifterz's advice I was able to set the device in recovery mode with ROOT access and adb :
DeathDrifterz said:
So, I have a Galaxy Note 4, broken screen, broken digitizer. Do not have access too an MHL cable or Mouse to hook up to TV. The phone has a password and usb debugging disabled, so kies and the computer won't recognize it. Not even when in download mode. I did flash CWM rcovery to the phone, but this still wouldn't allow me to see the phone in recovery mode. What did work was I downloaded the trial version of Wundershare Dr. Fone, booted phone into download mode, let the program run and start searching for files. Stopped the program. Unplugged the phone. Exited Dr Fone. Opened cmd in the platform-tools folder of the SDK platform. At this point, I was now able to see the phone, in recovery, listed under ADB Devices.
So Dr Fone took the phone from download mode (vol down + home + power, then press vol up after vibrate) to recovery mode once it started finding files. Disconnect the phone from the PC, exit Dr Fone and reconnect the phone to the PC. It will still be in recovery mode. Open cmd prompt in the platform-tools folder. adb devices shows phone in recovery, used adb pull /sdcard/ and it worked like a charm. All files on the phone have now been downloaded.
Broken screen, no digitizer, password locked, USB debugging disabled, and it was free. Took 5 minutes once Dr Fone was downloaded (will take longer if you don't have the sdk tools.)
Hope it helps.
Click to expand...
Click to collapse
2. In other forum I found tutorial how to enable USB debugging from recovery with root access :
Connect the device to Mac or PC in recovery mode. (I had to map the process in my mind as the screen was broken).
Now open terminal/CMD in computer and go to platform-tools/. type and enter ./adb devices to check if the device is connected in recovery mode.
To mount the respective directories, type:
Code:
./adb shell mount data
./adb shell mount system
Get the persist.sys.usb.config file in your system using:
Code:
./adb pull /data/property/persist.sys.usb.config /Your directory
Now open that file in a texteditor and edit it to mtp,adb and save.
Now push the file back in the device:
Code:
./adb push /your-directory/persist.sys.usb.config /data/property
Get the build.prop file:
Code:
./adb pull /system/build.prop /your-directory
Add these lines:
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
Push build.prop back into the device:
Code:
./adb push /your-dir/build.prop /system/
This way you enabled USB debugging on your device. But you still can't connect. Why? Because it asks for RSA verification. If you could view your display then you could easily tap on YES to authorize the device.
3. Skipping RSA verification :
The ADB keys (after authorization) are saved in /data/misc/adb/adb_keys, so I have one Samsung Galaxy S3 with working display which already authorized my PC.
So I got the adb_keys file from it. I connected the Samsung Galaxy S3 to my PC and use :
Code:
./adb pull /data/misc/adb/adb_keys
Then reconnected the Note 4 and pushed the file in it:
Code:
./adb push /your-dir/adb_keys /data/misc/adb/adb_keys
4. Reboot! And Voila: the devices boots normally and adb connects without asking for verification.
After that I used Vysor chrome extension and Vysor apk to view the device screen and act with the device.
I installed the apk with :
Code:
./adb install apk_name.apk
Sources :
https://forum.xda-developers.com/showthread.php?t=2395047
https://android.stackexchange.com/questions/120394/can-i-enable-usb-debugging-using-adb
https://www.vysor.io/
It works! With the first method.
I have Samsung Galaxy s5, lineage os 14.1,
After my screen broke, I couldn't see my device through adb devices, no matter what driver I have installed - and believe me I've tried all the methods.
Then I've installed CWM recovery, adb recognized it in devices but I wasn't able to pull sdcard with adb pull command in Windows 7. I got access denied.
Then I saw this post and I got access to sdcard!
Works on OnePlus One with Lineage 14.1
Works like a charm on my OnePlus One with lineage 14.1
Just want to mention that if you have problems mounting /data and/or /system
I got help from this post: https://forum.xda-developers.com/galaxy-s2/help/mount-adb-t1107545
Basically, the dirty solution I found with help from kaukassus post was:
1.
Code:
adb mount
- to view name of available mounts and identify /system and /data
2.
Code:
adb shell mount -o rw,remount -t yaffs2 /dev/block/[U]mmcblk0p28[/U]
underlined is the part that is different
- to mount the data folder. Do the same for system. Then I just followed the steps from this tutorial.
The part with the RSA verification I resolved with a little help from https://gist.github.com/varhub/7b9555cdd1e5ad785ffde2300fcfd0bd
Enable ADB (2/2): RSA verification
For the RSA verification that you asked to bypass, I don't know whether it would work in your device, but it worked in my little experiment. In Lollipop, the ADB keys (after authorization) are saved in /data/misc/adb/adb_keys. Your private key is saved in computer. In Linux the directory location is $HOME/.android/. On Windows that usually translates to %USERPROFILE%.android, but keys might end up in C:\Windows\System32\config\systemprofile.android in some cases.
adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
Click to expand...
Click to collapse
Thanks for post
Worked top to bottom, on my Galaxy S5 6.0.1 (ALEXNDR ROM)!
Used step .2, .3 and oledolez tips aswell.
Got the screen cracked and black, went crazy because I had the SD card encrypted and couldn't get the stuff outta there...
Thanks a lot!
Hugo
GS5 CWM Stock ROM
Hello ! I broke my gs5(sm-g900f)'s screen and now it is constantly black. I tried everything on the thread and my device is always shown as unauthorized in vysor or when checking in ADB with /adb devices. This means I have succeeded to enable USB Debugging through ADB, however I must be having problems with the RSA key. Any help would be appreciated!!
Thanks in advance !
Dan
P.S The phone was completely stock when I broke it and I blindly installed cwm-6.0.4.7 and CF-auto-root with odin, so maybe there is a problem with that ?
what if the partition is encrypted? How I would enter the boot password with a broken screen?
xaviermchot said:
what if the partition is encrypted? How I would enter the boot password with a broken screen?
Click to expand...
Click to collapse
I had the same problem and fixed it in TWRP doing this command:
Note: Use this command only if your /data/ partition has the ext4 file system. There are some other similar commands for other file systems, but i don't remember they.
Code:
adb shell make_ext4fs /dev/block/[B]mmcblk0p20[/B]
(Bold part can change depending of your device)
Then just do a normal wipe and flash again the ROM.
MiroBiala said:
Here is how I succeeded to enable USB debugging (also adb and remote view) on Samsung Galaxy Note 4 with broken screen.
1. Following the DeathDrifterz's advice I was able to set the device in recovery mode with ROOT access and adb :
2. In other forum I found tutorial how to enable USB debugging from recovery with root access :
Connect the device to Mac or PC in recovery mode. (I had to map the process in my mind as the screen was broken).
Now open terminal/CMD in computer and go to platform-tools/. type and enter ./adb devices to check if the device is connected in recovery mode.
To mount the respective directories, type:
Code:
./adb shell mount data
./adb shell mount system
Get the persist.sys.usb.config file in your system using:
Code:
./adb pull /data/property/persist.sys.usb.config /Your directory
Now open that file in a texteditor and edit it to mtp,adb and save.
Now push the file back in the device:
Code:
./adb push /your-directory/persist.sys.usb.config /data/property
Get the build.prop file:
Code:
./adb pull /system/build.prop /your-directory
Add these lines:
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
Push build.prop back into the device:
Code:
./adb push /your-dir/build.prop /system/
This way you enabled USB debugging on your device. But you still can't connect. Why? Because it asks for RSA verification. If you could view your display then you could easily tap on YES to authorize the device.
3. Skipping RSA verification :
The ADB keys (after authorization) are saved in /data/misc/adb/adb_keys, so I have one Samsung Galaxy S3 with working display which already authorized my PC.
So I got the adb_keys file from it. I connected the Samsung Galaxy S3 to my PC and use :
Code:
./adb pull /data/misc/adb/adb_keys
Then reconnected the Note 4 and pushed the file in it:
Code:
./adb push /your-dir/adb_keys /data/misc/adb/adb_keys
4. Reboot! And Voila: the devices boots normally and adb connects without asking for verification.
After that I used Vysor chrome extension and Vysor apk to view the device screen and act with the device.
I installed the apk with :
Code:
./adb install apk_name.apk
Sources :
https://forum.xda-developers.com/showthread.php?t=2395047
https://android.stackexchange.com/questions/120394/can-i-enable-usb-debugging-using-adb
https://www.vysor.io/
Click to expand...
Click to collapse
Dear experts,
I've been trying to follow the above steps but cannot get data and system mounted:
PS C:\Users\Azubi\AppData\Local\Android\Sdk\platform-tools> adb devices
List of devices attached
52001077b43913d3 recovery
PS C:\Users\Azubi\AppData\Local\Android\Sdk\platform-tools> adb shell mount data
mount: mounting /dev/block/mmcblk0p21 on /data failed: Device or resource busy"
I'm trying to access a Galaxy S5 mini with broken screen and digitizer. It's rooted and runs with TWRP and Lineage OS.
The aim is to enable usb debugging in order to mirror the screen on pc.
Has anyone been encountering this already and could help?
Many thanks
Max