I was experiencing the wifi+bluetooth ship failure that I fixed once, twice, ..., but the fix didn't last
My last attemp to fix that resulted in a flex cable ribbon damage (bad move)
Power button and touch screen are now broken
Sounds like it's time to change phone :crying: I'm not willing to repair this time
I'm trying to access internal storage but I am stuck:
I can:
- access bootloader options (buy plug-in power or usb cable)
- go into recovery, but I can't validate my selection (no power button)
- go into fastboot, but it seems that mounting is not a fastboot possibility
- go into rom (fastboot reboot), but I need to touch screen to activate usb mount
Any idea ?
cailloup said:
I was experiencing the wifi+bluetooth ship failure that I fixed once, twice, ..., but the fix didn't last
My last attemp to fix that resulted in a flex cable ribbon damage (bad move)
Power button and touch screen are now broken
Sounds like it's time to change phone :crying: I'm not willing to repair this time
I'm trying to access internal storage but I am stuck:
I can:
- access bootloader options (buy plug-in power or usb cable)
- go into recovery, but I can't validate my selection (no power button)
- go into fastboot, but it seems that mounting is not a fastboot possibility
- go into rom (fastboot reboot), but I need to touch screen to activate usb mount
Any idea ?
Click to expand...
Click to collapse
Try this http://droid-at-screen.ribomation.com/installation/
Use a desktop window to access your phone. A long time back when my screen went off, i used this to access my phone.
guruzen said:
Try this http://droid-at-screen.ribomation.com/installation/
Use a desktop window to access your phone. A long time back when my screen went off, i used this to access my phone.
Click to expand...
Click to collapse
Thanks, one problem: USB debugging is not activated (what a noob I am not to have USB debugging check lol)
Do you have a custom recovery? If so, you should be able to access the shell through adb and USB while in recovery.
cailloup said:
Thanks, one problem: USB debugging is not activated (what a noob I am not to have USB debugging check lol)
Click to expand...
Click to collapse
If ravilov method works, write an android program that registers for onBootReceiver. In onReceive() have this code
Settings.Secure.putInt(context.getContentResolver(), Settings.Secure.ADB_ENABLED, 1)
Put the apk under /system/app and change the permission to rw-r-r
Restart your phone, the above app must run onBoot and u will have usb debugging enabled.
Lets see how things go.
ravilov said:
Do you have a custom recovery? If so, you should be able to access the shell through adb and USB while in recovery.
Click to expand...
Click to collapse
I have big part recovery V3 from Zn7mkUKzN1r8aCIV
So accessing shell would let me mount storage ?
How do I use adb from recovery ?
guruzen said:
If ravilov method works, write an android program that registers for onBootReceiver. In onReceive() have this code
Settings.Secure.putInt(context.getContentResolver(), Settings.Secure.ADB_ENABLED, 1)
Put the apk under /system/app and change the permission to rw-r-r
Restart your phone, the above app must run onBoot and u will have usb debugging enabled.
Lets see how things go.
Click to expand...
Click to collapse
So I won't be able to mount storage from shell, but I can write lines that will enable usb debugging so that I can use your first post ?
I
cailloup said:
I have big part recovery V3 from Zn7mkUKzN1r8aCIV
So accessing shell would let me mount storage ?
How do I use adb from recovery ?
So I won't be able to mount storage from shell, but I can write lines that will enable usb debugging so that I can use your first post ?
I
Click to expand...
Click to collapse
Looks like u cannot mount sdcard. I found something about adb enabling in init.rc that u can retrieve. Put your phone in recovery and connect to the system and do adb shell
You must be in # prompt. Pull out init.rc using the command "adb pull /init.rc ."
I am attaching my init.rc. diff it and you should find differences wrt to adb. Try replacing the adb differences and ensure the chmod is done for init.rc (initial permissions)
guruzen said:
Looks like u cannot mount sdcard. I found something about adb enabling in init.rc that u can retrieve. Put your phone in recovery and connect to the system and do adb shell
You must be in # prompt. Pull out init.rc using the command "adb pull /init.rc ."
I am attaching my init.rc. diff it and you should find differences wrt to adb. Try replacing the adb differences and ensure the chmod is done for init.rc (initial permissions)
Click to expand...
Click to collapse
adb device is ok
I got the init.rc with adb pull, it is exactly the same as yours
I tried adb pull emmc
pull sdcard
pull scard0
pull scard1
pull storage
etc
Some don't work, some work but I got only files from "sys" folder
I tried this
http://forum.xda-developers.com/showthread.php?t=2339530
Same folder issue
I tried adb shell su mount but I don't know what to do with it ^^
Since our init.rc are similar, I also tried [email protected] but I have nothing in the device list (while phone is on)
If you enabled root for adb inside the rom, you can use the following command in adb to mount the internal storage:
echo /dev/block/vold/179:97 > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun0/file
That will mount internal storage as usb storage and you will be able to access the files from a computer.
Edit: I just read that you don't have it enabled >.< Another way would be to use "input tap x y" which does not require root but as you don't have it enable, something has to be done through recovery.
Second edit: Try this inside recovery:
adb shell
mkdir sdcard0
mount /dev/block/mmcblk0p18 sdcard0
Now that the internal storage is mounted on sdcard0, exit adb shell and use the following command:
adb pull /sdcard0 sdcard
This should copy all the files from the internal storage to a new folder called sdcard in your computer.
Reiki21 said:
Second edit: Try this inside recovery:
adb shell
mkdir sdcard0
mount /dev/block/mmcblk0p18 sdcard0
Now that the internal storage is mounted on sdcard0, exit adb shell and use the following command:
adb pull /sdcard0 sdcard
This should copy all the files from the internal storage to a new folder called sdcard in your computer.
Click to expand...
Click to collapse
Yeah that worked!
currently pulling everything, it's going to be long
Thanks all for help
Problem solved
Related
i searched and cant seem to find anything on my problem....i connect via mass storage mode , it detects the phone, but for some reason it doesnt let me access the files on the card....in other words ,i cant open them...any help ????
try opening the sd card with root access.
Open the terminal and type:
Code:
sudo nautilus /media/
Then just select one of your sd cards.
If this works to access them then you need to change the permissions to allow ubuntu to access them with read and write without root.
I am using it just fine on Ubuntu 10.4
I connect my phone and it is mounted automagically, and I can move the files from/to the phone.
Do you have se_linux installed?
It also works just fine for me. It may have to do with permissions on the folders when mounted. From a cli you may try running this command with the phone not connected:
sudo chown -R user:user /media
Just replace "user" with your username.
Then connect the phone and see what happens.
thanks, I'll give this a try, let you guys know tomorrow...
Gotta say it works on Ubuntu better then does on Windows XP. You may have some permissions fudged somewhere. Do as the guys above said and let us know.
the3dman said:
try opening the sd card with root access.
Open the terminal and type:
Code:
sudo nautilus /media/
Then just select one of your sd cards.
If this works to access them then you need to change the permissions to allow ubuntu to access them with read and write without root.
Click to expand...
Click to collapse
this is not working for me
aksoutherland said:
It also works just fine for me. It may have to do with permissions on the folders when mounted. From a cli you may try running this command with the phone not connected:
sudo chown -R user:user /media
Just replace "user" with your username.
Then connect the phone and see what happens.
Click to expand...
Click to collapse
nothign when i enter command
In the phone's USB settings what do you have it set to?
Run
tail -f /var/log/messages
while connecting your phone, and when connected
ls -ltra /media
Post here and we will take a closer look
lqaddict said:
In the phone's USB settings what do you have it set to?
Run
tail -f /var/log/messages
while connecting your phone, and when connected
ls -ltra /media
Post here and we will take a closer look
Click to expand...
Click to collapse
nothing again.....i have it set to ask on connection, then i swithced to mass storage mode....... what else should i do?
error message : "could not display" "the file location is not a folder "
Install android-sdk for linux, enable USB debugging under Development settings, try connecting with adb
Code:
/path/to/android-sdk/tools/adb shell
It will drop you to $ prompt
Post here the output of
mount -a
Use
Code:
tags.
lqaddict said:
Install android-sdk for linux, enable USB debugging under Development settings, try connecting with adb
Code:
/path/to/android-sdk/tools/adb shell
It will drop you to $ prompt
Post here the output of
mount -a
Use
Code:
tags.[/QUOTE]
thanks, I appreciate the help, I will give this a try in the morning
Click to expand...
Click to collapse
Ok first things first : If you installed some launcher and your touch screen is not responding and you dont have USB debugging enabled then the only way to fix that is to install the original firmware, dload from here : http://www.androidtablets.net/forum...huawei-ideos-s7-slim-official-firmware-4.html check post 35 for the one i used
If you do have debugging enabled the download Superoneclick from below.
The super one click can aslo root the S7 slim and it has adb installed. Unxip it somewhere and go into the \adb folder. Open command prompt from there and run
Adb devices
If it doesnt show your device the either the debugging is not enabled or the right driver is not loaded. (Menu, Settings, Applications, Development, USB Debugging (Yes))
type adb shell
cd\data\app
rm *launcher*.apk
exit
adb reboot
This will remove the launchers thats faulty and touch screen will work again.
If you guys find a clockworkmod that works then leme know here cause i loaded the wrong one and its messed up.
Use psneuter to root and use the adb in the zip for the above
Cia
How to flash Recovery
Reserved for now
Use other Launchers
ADB remount
adb push c:\bluetooth_power.sh /system/etc/
unzip attached file to c:\
Swapping sdcard and sdcard2 around
adb remount
adb push vold.fstab /system/etc/vold.fstab
if you get permission denied error when doing adb remount then try the following instead :
adb push vold.fstab /sdcard/vold.fstab
adb shell
su
mount -o remount rw /system
cp /sdcard/vold.fstab /system/etc/vold.fstab
mount -o remount ro /system
exit
exit
reboot
Copy attached file into ur adb directory (and unzip it has the modified and original file in the zip) and do the above
Grumps said:
adb remount
adb push vold.fstab /system/etc/vold.fstab
if you get permission denied error when doing adb remount then try the following instead :
adb push vold.fstab /sdcard/vold.fstab
adb shell
su
mount -o remount rw /system
cp /sdcard/vold.fstab /system/etc/vold.fstab
mount -o remount ro /system
exit
exit
reboot
Copy attached file into ur adb directory (and unzip it has the modified and original file in the zip) and do the above
Click to expand...
Click to collapse
this works great - - i had a problem where i have not been able to recover my internal SD card - tried everything - even back to original eclair and all - now i just use the external sd (16gb) for everything. No problems with camera recognizing sd card or programs not downloading, etc, etc....
I'll still try to maybe swap out the internal card, or try to get it functional again somehow, but in the meantime, the S7 if again functional.
Rom
Im currently using this rom an dit works perfectly : http://www.androidtablets.net/forum...ical/15812-rom-tri_zet-ideos_s7-slim-mod.html
Only problem i had was updating google maps so i just loaded the new version via .apk manually
O yes If you load that rom and it comes on the first time the screen might not respond (stuck on lockscreen) but its busy loading software in the background. Mine came up on the lock screen saying connect charger although the battery wasnt low so i plugged the charge cable in. It then rebooted after a while and the touch screen is working perfectly.
http://forum.xda-developers.com/showthread.php?t=942166
Grumps said:
Im currently using this rom an dit works perfectly : http://www.androidtablets.net/forum...ical/15812-rom-tri_zet-ideos_s7-slim-mod.html
Only problem i had was updating google maps so i just loaded the new version via .apk manually
O yes If you load that rom and it comes on the first time the screen might not respond (stuck on lockscreen) but its busy loading software in the background. Mine came up on the lock screen saying connect charger although the battery wasnt low so i plugged the charge cable in. It then rebooted after a while and the touch screen is working perfectly.
http://forum.xda-developers.com/showthread.php?t=942166
Click to expand...
Click to collapse
I just got my Slim S7 yesterday, hated the launcher so I replaced it not thinking it would cause such a problem... long story short I tried installing the rom you linked hoping it would fix it(tried everything else) and the touch screen still is unresponsive and USB debugging is now disabled. Any ideas?
phxtravis said:
I just got my Slim S7 yesterday, hated the launcher so I replaced it not thinking it would cause such a problem... long story short I tried installing the rom you linked hoping it would fix it(tried everything else) and the touch screen still is unresponsive and USB debugging is now disabled. Any ideas?
Click to expand...
Click to collapse
well I finally got it working. I ended up doing multiple battery pulls and installed the geeksu recovery, and that's all I did. I'm up and running on that rom. Only thing is thatbi somehow lost root, but that was no biggy.
So I've been tinkering around with CM12.1 on this watch for a while (since I switched my phone from the Samsung Galaxy Note 4 to the Xiaomi Mi Max) and yesterday decided to give Android Wear another try (note: I had the LG G Watch back in the really early Android Wear days) and there have been quite a few tweaks that I decided to apply so will share them all here as I remember them.
Android Wear:
Gaining root:
Since we can not use systemless SuperSU (because we can't edit the kernel on the go) like the other watches we need to use a system only root method so I will share how to do that:
You can do this either manually by creating a .supersu containing "SYSTEMLESS=false" file in /system/ before flashing Wear SuperSU or just flash the zip from here before the SuperSU Wear zip: https://forum.xda-developers.com/android/software-hacking/root-disabler-t3370794
Also here is the latest SuperSU Wear zip file: https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
Note: you will have a Busybox app installed when you boot AW, you need to connect to Wi-Fi to be able to use it, otherwise it will crash.
Note 2: If you are connected to the phone via Bluetooth the Wi-Fi will automatically disconnect but you can disable this behavior in Developer Options on the watch.
Disabling touch to wake:
This was really annoying for me, I only want the device to wake by pressing the button not when I tilt the watch or touch the screen since that means the watch will be waking up uselessly a lot, tilt to wake can be disabled from the Android Wear app on the phone but for disabling touch to wake you need to edit some system files.
Note: this requires either having root or booting into TWRP and being connected to a PC using either Bluetooth ADB or the watch with the cradle and an USB cable.
AW+root method:
With the watch connected to the computer using either ADB over Bluetooth or the USB cable do the following in a shell:
Code:
adb pull /system/usr/idc/sec_touchscreen.idc
Now you will get the sec_touchscreen.idc file on your PC, open it using Notepad++/gedit/some other Linux EOF format compatible text editor (NOT NORMAL NOTEPAD OR ANY MICROSOFT OFFICE APP!!!!)
The last line should look like:
Code:
touch.wake=1
Just delete that line or set it to 0 and save the file.
Now back to the shell:
Code:
adb shell "mount -o remount,rw /system"
Code:
adb push sec_touchscreen.idc /system/usr/idc/
Code:
adb reboot
Done, now touching the screen will no longer wake up the device.
TWRP method:
Boot the watch in TWRP and connect it to the PC using the cradle and an USB cable then do these commands in a shell:
Code:
adb shell "twrp mount system"
Code:
adb pull /system/usr/idc/sec_touchscreen.idc
Now you will get the sec_touchscreen.idc file on your PC, open it using Notepad++/gedit/some other Linux EOF format compatible text editor (NOT NORMAL NOTEPAD OR ANY MICROSOFT OFFICE APP!!!!)
The last line should look like:
Code:
touch.wake=1
Just delete that line or set it to 0 and save the file.
Now back to the shell:
Code:
adb push sec_touchscreen.idc /system/usr/idc/
Code:
adb reboot
Done, now touching the screen will no longer wake up the device.
I am not sure if this is a problem with AW or the AW kernel with TWRP or it was just me but TWRP didn't display properly for me after I switched from CM12.1 to AW (it would only display till I clicked something then screen turns off) so I will post how to flash the zip files without being able to see TWRP:
You will need to be connected to a computer that has ADB setup for this.
The one thing you need to actually do on TWRP on the watch is select the "never ask again" and swipe to allow system modifications on the first run of TWRP. Note that after you click to tick the "never ask again" check box the screen will already go black so remember the layout so that you'll be able to swipe the slider.
Now you will open a shell on the PC and "adb shell" to the watch that is connected with an USB cable and the charging cradle.
Now you are in the TWRP shell so do these commands:
Code:
twrp mount system
Code:
twrp install /sdcard/disable_systemless_root.zip
Code:
twrp install /sdcard/SuperSU-2.78-wear.zip
Code:
twrp wipe cache
Code:
twrp wipe dalvik
Code:
reboot
NOTE: This assumes that you have put the zips from the first post in the internal storage of the device for which /sdcard/ is a mount point.
Will post more stuff soon, just wanted to post the tutorial on how to root AW for now, I'll be leaving home soon so I'll be back to post the rest of the stuff later today.
As a secondary note right now I am trying to port some AW 2.0 apps to work on 1.5 but we'll see how that goes, don't get your hopes up.
When i try push file adb say: read only file system
I write this and now it's ok:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p25 /system
exit
adb push sec_touchscreen.idc /system/usr/idc/
Thesebax4 said:
When i try push file adb say: read only file system
I write this and now it's ok:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p25 /system
exit
adb push sec_touchscreen.idc /system/usr/idc/
Click to expand...
Click to collapse
Why did you add that /dev/block/mmcblk0p25?
The right command is:
Code:
mount - o remount,rw /system
Also did you first root your device?
I never needed to add anything, that's why I'm asking?
I don't have root. TWRP ask me to make system writable, i try to swipe (yes) but screen goes black... Maybe this is fault. I search this in google https://forum.xda-developers.com/showthread.php?t=1749657 (second post) I change the partition from mmcblk0p1 to mmcblk0p25 because gear s have /system under mmcblk0p25. And this working for me.
Thesebax4 said:
I don't have root. TWRP ask me to make system writable, i try to swipe (yes) but screen goes black... Maybe this is fault. I search this in google https://forum.xda-developers.com/showthread.php?t=1749657 (second post) I change the partition from mmcblk0p1 to mmcblk0p25 because gear s have /system under mmcblk0p25. And this working for me.
Click to expand...
Click to collapse
Ah, I was thinking you were in AW not TWRP, as I said in the 2nd post you have to swipe on the black screen, you will feel a vibration, for me both methods work properly without the extra mounting.
I've installed recovery and Android wear os, but due to Heavy battery drainage and no phone audio I'm trying to Go back to stock.
I've tried flashing Stock firmware Using Odin but after flashing when the watch boot up, after Samsung gear s logo screen Goes blank and after few seconds Samsung animation comes Up but doesn't complete the animation anf Goes blank again.
I need help to fix this.
Thanks in advance
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
Recover files from phone with a broken screen, no USB debugging and set as "Charge"
Hey,
So, I'm trying to recover files from my previous phone, a Xiaomi Redmi Note 5 Pro. It can boot Android and also get into recovery mode, but I can't see anything on the screen (it's completely black) and I think it doesn't register touches either.
The big problem is, USB debugging is off and USB mode is set to charging only (no MTP).
If I enter TWRP, adb recognizes it (it's listed when you type "adb devices"), but what can I do from there? Is there a way to enable MTP through TWRP adb? I tried some commands like "adb shell" or "adb shell <command>" but it says these commands don't exist or just gives me a list of some other commands.
Is there just no way to recover my files?
Thanks for your help regardless.
@Ulfys
From your description it seems like you already have ADB access from the recovery ROM and it looks like you have access to your data partition. Therefore you can backup your data and migrate it to a new phone
Note: Being in Recovery mode you can only use adb pull, adb push and adb reboot
That doesn't help if I want to recover my files in the internal storage, though. And I don't have any other rooted device with TWRP - even if I had one, flashing another phone's data partition isn't a great idea.
Enabling MTP somehow would be a lot more convenient.
Ulfys said:
Enabling MTP somehow would be a lot more convenient.
Click to expand...
Click to collapse
Enabling MTP requires to have access to Android terminal: adb shell
EDIT:
IMO the only option you have is to pull data from device: adb pull