The screen is black and doesn't operate when you touch it.
I know you can get into the files using the recovery ...but I don't know how many volume ups and downs you need to get into it?
I am running the 5.0 JB CM10 recovery.
Volume up + volume down + power button if froyo bootloader
Volume down + power button if gingerbread bootloader
Sent from my SGH-T959 using xda app-developers app
What he is asking is, since he can't see the screen, he needs to know exactly the number of up or down spaces to get to.....
And this brings my question, where are you trying to get to in recovery?
I approve this message.
samsgun357 said:
What he is asking is, since he can't see the screen, he needs to know exactly the number of up or down spaces to get to.....
And this brings my question, where are you trying to get to in recovery?
I approve this message.
Click to expand...
Click to collapse
The option to mount USB storage....I don't think it has it anymore...I don't have It on my gs3
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
If its the same as the recovery in PA, semaphore
Its down 6, power
Up 2
I approve this message.
If you want to copy all your files from the internal storage using ADB: Reboot into CWM and connect it to your PC. In the command prompt, type:
adb shell
mount /dev/block/mmcblk0p1
(that's the partition of the internal storage in my vibrant)
exit
adb pull /sdcard C:\backup
(make sure you create the C:\backup folder first, it will begin to copy everything from your phone's storage to your harddrive)
-----
Optional: Once you are in adb shell, you can type this:
cat /etc/fstab (it will tell you the location of each partition that you can mount)
cd /sdcard (go to /sdcard partition)
ls -la (display all files in current directory)
Just remember to use 'adb pull' or 'adb push' you need to exit adb shell first.
Or just:
1. Pull battery
2. Attempt to get into recovery by guessing.
3. Adb shell Into device.
3.b if adb can't find device, go back to 1
4. Adb pull /storage/sdcard0/ or adb pull /sdcard/
It will be in the folder containing the adb file.
Sent from my GT-I9000 using xda premium
that /storage directory is new thing in Jelly Bean, I guess it does make things easier for people, instead of /sdcard and /emmc. It's a symbolic link, I don't even see it in adb shell.
The CWM doesn't auto mount the internal storage, so you still have to mount it first.
VeryCoolAlan said:
The option to mount USB storage....I don't think it has it anymore...I don't have It on my gs3
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Click to expand...
Click to collapse
Maybe your GS3 uses MTP rather than mass storage.
Try: Up, Up, Down, Down, Left, Right, Left, Right, B, A, B, A
Sorry couldnt resist :laugh:
Lol, forgot select start!
I approve this message.
FaultException said:
Maybe your GS3 uses MTP rather than mass storage.
Click to expand...
Click to collapse
Probably.... I'm on CM10 .
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Related
So my rooted view sudden rebooted on its own into a loop and ended up booting into CM recovery by itself. But it recovery I get this message at the bottom
E:unknown misc partition fs_type "ext4"
I've tried recovery, reinstalling roms, even unrooting. Nothing will work. It'll always go back to the recovery screen with that message. Can my view be salvaged? Or is it gone?
jigz23 said:
So my rooted view sudden rebooted on its own into a loop and ended up booting into CM recovery by itself. But it recovery I get this message at the bottom
E:unknown misc partition fs_type "ext4"
I've tried recovery, reinstalling roms, even unrooting. Nothing will work. It'll always go back to the recovery screen with that message. Can my view be salvaged? Or is it gone?
Click to expand...
Click to collapse
I'm having the same issue. Did you ever get it figured out?
jigz23 said:
So my rooted view sudden rebooted on its own into a loop and ended up booting into CM recovery by itself. But it recovery I get this message at the bottom
E:unknown misc partition fs_type "ext4"
I've tried recovery, reinstalling roms, even unrooting. Nothing will work. It'll always go back to the recovery screen with that message. Can my view be salvaged? Or is it gone?
Click to expand...
Click to collapse
Could be a sign of a degrading internal memory, but is is extremely unlikely that a solid state memory device would fail like that.
You could try reformatting the internal sd via your pc while in CWM, and installing your RUU after that, provided you can see the internal drive.
Sent from my HTC Flyer P510e using XDA Premium HD app
Run these adb commands while in CWM when connected to pc , see if it helps :
adb remount
adb shell rm -rf /system/sd/dalvik-cache
adb shell format DATA:
adb shell format SYSTEM:
adb shell format CACHE:
adb shell format MISC:
Warning: THIS WILL ERASE ALL USER DATA. DO AT YOUR OWN RISK.
Then run your RUU and you should be back in working order.
Sent from my HTC Flyer P510e using XDA Premium HD app
mhkabir98 said:
Run these adb commands while in CWM when connected to pc , see if it helps :
adb remount
adb shell rm -rf /system/sd/dalvik-cache
adb shell format DATA:
adb shell format SYSTEM:
adb shell format CACHE:
adb shell format MISC:
Warning: THIS WILL ERASE ALL USER DATA. DO AT YOUR OWN RISK.
Then run your RUU and you should be back in working order.
Sent from my HTC Flyer P510e using XDA Premium HD app
Click to expand...
Click to collapse
This has been a looong time but I figured it was worth a try. I did all these commands and run into trouble once I get to the adb shell format data:. I get an error message saying "/sbin/sh: format: not found"
jigz23 said:
This has been a looong time but I figured it was worth a try. I did all these commands and run into trouble once I get to the adb shell format data:. I get an error message saying "/sbin/sh: format: not found"
Click to expand...
Click to collapse
I get the same thing
Today my Tablet (Hyundai A7HD) with CM9 started behaving very strange.
It doesnt recognize my sd card, nor its own internal nand storage anymore.
I dont know what to do, since i cant even flash an update through CWM anymore without a functioning storage medium.
the sd card works fine on my pc and i cant format the internal storage through my tablet.
what else can i do to fix this?
I could really use some help, if someone knows a way to do it.
IndigoHD said:
I could really use some help, if someone knows a way to do it.
Click to expand...
Click to collapse
Supply more information. How do you know it's not detecting the internal storage? What are the symptoms? In my point of view, the device would be bricked in this case. Can it boot at all? Or is it fastboot complaining , trying to flash it? The internal memory, is it a MTD for /system plus an MMC for /data, or only an MTD? Only one MMC? Does the devices still exists or not? The partitions..?
Give us some more information, and we'll see if someone here can come with an intelligent suggestion.
Thank you for your reply!
The Device is an Hyundai A7HD and it says that what it calls "sdcard" but actually is its internal storage is damaged. Formatting doesnt work.
It still boots fine but cant access the internal storage, so nothing can be downloaded onto the device and such.
It has a special partition where applications are installed, but nothing can be saved there.
im guessing that something is wrong with the OS, and maybe i could fix it using ADB (if someone could explain to me how)?
Ok, so no /sdcard and /sdcard is supposed to be the phones internal memory, no /data partition, hence not able to download new apps, but the phone boots and so, i.e. system partitions works fine.
This sounds quite like this (confusing) thread to me. In summary, we are talking about three devices, the internal MTD device with /system, boot image, cache etc, the internal MMC device with /sdcard and /data plus an external sdcard named something like /sdcard/external_sd. The internal MMC broken beyond repair (hardware failure).
Still it may be something else only reassembling this.
If you believe your problem is due to some problem with your ROM I suggest you try to reinstall stock ROM using the vendors standard flash tools.
If this doesn't work, we can see if a solution similar to the one in the thread above may be applicable to you.
When i use Astro file manager to look at my phones storage the internal memory calls itself "sdcard" and my ACTUAL micro-sdhc calls itself "extsd" in a folder called "mnt".
the original flash tool doesnt seem to function anymore since i would normally hold down the "menu"-button, then plug the cable into my pc and while STILL holding menu id press power 7 to 10 times and then flashing would start automatically. but ever since installing cwm and a cm9 custom-rom, this doesnt seem to function anymore.
EDIT: in Clockwordmod recovery its called "emmc" for internal memory and "sdcard" for my actual sdcard.
Ok, this is consistent. Can you do a couple of shell commands?
# mount
and
# ls -l /dev/block
... and paste in the result here. As root or as shell user (or any other user) doesn't really matter.
when i plug the device into usb it says debugging enabled. so i open adb and type in "adb devices" and it starts listing devices. But no device is recognized.
EDIT: it recognizes my phone tho.
IndigoHD said:
when i plug the device into usb it says debugging enabled. so i open adb and type in "adb devices" and it starts listing devices. But no device is recognized.
Click to expand...
Click to collapse
Tricky. And not possible to install apps, so no ConnectBot or similar ...
Do you have a link to the CM9 you are using?
kuisma said:
Tricky. And not possible to install apps, so no ConnectBot or similar ...
Do you have a link to the CM9 you are using?
Click to expand...
Click to collapse
wait! i CAN install apps from the market!
and yes, one second.
http://www.slatedroid.com/topic/33373-rom-cm9-nightlies/
im using version 20120711
EDIT: Its an Allwinner A10 Device.
IndigoHD said:
wait! i CAN install apps from the market!
Click to expand...
Click to collapse
That makes all the difference!
So, what does "mount" say?
when i type "adb mount" it just gives me a long list of commands and explanations.
EDIT: there are many versions of connectbot. which one do we need?
IndigoHD said:
when i type "adb mount" it just gives me a long list of commands and explanations.
Click to expand...
Click to collapse
No, run mount from the command line using ConnectBot. ADB didn't work, you told me before.
$ mount
Click to expand...
Click to collapse
but which connectbot on the market is the right one? There are so many.
IndigoHD said:
but which connectbot on the market is the right one? There are so many.
Click to expand...
Click to collapse
Please. Show a little more effort.
https://play.google.com/store/apps/details?id=org.connectbot
i installed it and started it.
now it asks me to connect to a host.
i honestly dont know what im doing here.
IndigoHD said:
i installed it and started it.
now it asks me to connect to a host.
i honestly dont know what im doing here.
Click to expand...
Click to collapse
Select "local", give the session some name of you choice and connect. Now you are running a local shell in the same way as using "adb shell". You are familiar with "adb shell"..?
kuisma said:
Select "local", give the session some name of you choice and connect. Now you are running a local shell in the same way as using "adb shell". You are familiar with "adb shell"..?
Click to expand...
Click to collapse
isnt adb shell a terminal that accepts commands either locally or by usb connection?
EDIT: What should i do now on connectbot?
Can anyone help me, perhaps?
Broken screen and i was just wondering how i can wipe it, so i can atleast make some money off my phone and now have al my things on it
Mhl - tv out only real way... unless you're rooted. You could use adb possibly
Sent from my GT-I9300 using Tapatalk 4
anthonyly said:
Broken screen and i was just wondering how i can wipe it, so i can atleast make some money off my phone and now have al my things on it
Click to expand...
Click to collapse
Why post the same question twice ???
JJEgan said:
Why post the same question twice ???
Click to expand...
Click to collapse
this is about wiping, hmm how would i adb wipe this LOLOL .. i wiped my sensation that was broken accidently wiping system now it's stuck at boot and broken ahha
i dont know what the aplpciation is called its when you can view your phones screen and control it on your computer
With no screen, you cannot set up screen viewing software.
You'd need to boot into download mode and flash cwm / philz recovery. Then boot into recovery, connect via usb. Adb commands (which you can Google) can be used to delete anything in /data
Sent from my GT-I9300 using Tapatalk 4
JJEgan said:
Why post the same question twice ???
Click to expand...
Click to collapse
rootSU said:
With no screen, you cannot set up screen viewing software.
You'd need to boot into download mode and flash cwm / philz recovery. Then boot into recovery, connect via usb. Adb commands (which you can Google) can be used to delete anything in /data
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
ahah i do have philz problem is i cant see whats going on LOL
You dont need to see. Adb shell runs from pc. Google it.
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
You dont need to see. Adb shell runs from pc. Google it.
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
So i can't tell when i'm in recovery or not, but
do i hold home + vol up + Power
wait
run adb and then find the command to wipe data?
i can't tell because i can't see anything
Im using wondershare mobileGo
would it be the same if i just wiped the data folder in the internal memory?
i want to make a factory reset but i can't since i don't know how via computer, i dont want whoever gonna buy my phone to go through my accoutns and all
Well you can run the command "adb devices". It won't work until you're in recovery.
Hold vol up, home and press power. Connect the usb. Run adb devices and see if it returns your serial number. If it does its connected and you're in recovery
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
You dont need to see. Adb shell runs from pc. Google it.
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
rootSU said:
Well you can run the command "adb devices". It won't work until you're in recovery.
Hold vol up, home and press power. Connect the usb. Run adb devices and see if it returns your serial number. If it does its connected and you're in recovery
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
alright im in recovery, so how do i wipe all my data/factoryreset
anthonyly said:
alright im in recovery, so how do i wipe all my data/factoryreset
Click to expand...
Click to collapse
Once in adb shell (which i'll assume you've learnt about) you just run standard linux terminal commands (case sensitive)
rm -vR /data/.*
rm -rf /data/*
You can ls /data to confirm (that's LS)
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Once in adb shell (which i'll assume you've learnt about) you just run standard linux terminal commands (case sensitive)
rm -vR /data/.*
rm -rf /data/*
You can ls /data to confirm (that's LS)
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
what is adb shell LOL, i know about adb and i've used commands with it too... but i think i might **** up so i want to do this as careful as possible
do i just paste when i have my phone connected and all when im in adb shell?
rm -vR /data/.*
then
rm -rf /data/*
to factory reset?
If you "know about adb" you know what adb shell is. Adb shell is where you type the commands.
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Once in adb shell (which i'll assume you've learnt about) you just run standard linux terminal commands (case sensitive)
rm -vR /data/.*
rm -rf /data/*
You can ls /data to confirm (that's LS)
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
rootSU said:
If you "know about adb" you know what adb shell is. Adb shell is where you type the commands.
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
so i just
rm -vR /data/.*
then
rm -rf /data/*
and im good everything is wipped?
Should be.
As mentioned "ls /data" should list the contents of /data. Do it before and after the commands above to see of it worked
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Should be.
As mentioned "ls /data" should list the contents of /data. Do it before and after the commands above to see of it worked
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
what does ls mean?
anthonyly said:
what does ls mean?
Click to expand...
Click to collapse
ls = list
ls /data = list contents of /data.
All basic linux commands, as all Android terminal and adb shell commands are.
rootSU said:
Should be.
As mentioned "ls /data" should list the contents of /data. Do it before and after the commands above to see of it worked
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
rootSU said:
ls = list
ls /data = list contents of /data.
All basic linux commands, as all Android terminal and adb shell commands are.
Click to expand...
Click to collapse
will try right now, so after this, it should be pretty much factory reset right? So when i sell my phone there's no personal things?
anthonyly said:
will try right now, so after this, it should be pretty much factory reset right? So when i sell my phone there's no personal things?
Click to expand...
Click to collapse
Should be. ls will confirm.
anthonyly said:
will try right now, so after this, it should be pretty much factory reset right? So when i sell my phone there's no personal things?
Click to expand...
Click to collapse
rootSU said:
Should be. ls will confirm.
Click to expand...
Click to collapse
wtf when i put adb devices, my phone shows up but then when i put ls /data and shows up " 'ls' is not regoniszed as an internal or extrernal command, operable program or batch file."
nvm forgot to put adb
alright i did the first command and got
C:\Users\antho_000\Desktop>adb rm -vR /data/.*
Android Debug Bridge version 1.0.31
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
Hi, I have a MB860 rooted and running Cyanogenmod. A few days ago the touch and LCD died. (presumably by break Flex).
I want to recover my data and pictures of internal storage, but the phone has PIN lock screen and only USB Charge for default (I can't change to Storage mode). When I connected to the PC I can access to RSD mode.
How I can recover my data with broken screen?
Thank you and have a nice 2014.
Greetings from Chile.
In the development section, there's a thread that discusses dual boot. Use that basis to copy the internal storage to an sd card or to your computer. There's not much you can do without the screen :/
Sent from my MB886 using xda app-developers app
Via ADB, you can copy contents from internal SD to external. Cp /sdcard/DCIM /sdcard-ext/bk_camera for example (the paths won't fit, I don't remeber the right ones for cm7)
Hit the damn thanks button instead!
Enviado desde mi MB860
You didn't say which CM version you're using. There are at least 4 generations available for the Atrix.
You can try this via command line. Make sure you type it out exactly as specified. You type in only the bold stuff, the rest are prompts/comments.
Code:
[color=grey]>[/color] [b]adb shell[/b]
[color=grey]$[/color] [b]su[/b]
[color=grey][i]#-- internal SD[/i][/color]
[color=grey]#[/color] [b]echo /dev/block/mmcblk0p18 > /sys/devices/platform/usb_mass_storage/lun0/file[/b]
[color=grey][i]#-- external SD[/i][/color]
[color=grey]#[/color] [b]echo /dev/block/mmcblk1p1 > /sys/devices/platform/usb_mass_storage/lun1/file[/b]
That should make your SD card(s) visible as windows drives.
When you're done, do "safe remove" in windows and then this:
Code:
[color=grey]>[/color] [b]adb shell[/b]
[color=grey]$[/color] [b]su[/b]
[color=grey]#[/color] [b]echo > /sys/devices/platform/usb_mass_storage/lun0/file[/b]
[color=grey]#[/color] [b]echo > /sys/devices/platform/usb_mass_storage/lun1/file[/b]
This should work at least on CM7 (kernel 2.6).
@andresrivas @ravilov that was what i was getting at, i just didn't remember the exact command lines to input to get it done, thats why i pointed in the right direction.
Sent from my MB886 using xda app-developers app
An alternative would be to USB mount from CWM, presuming you are using CWM. I'm not sure how it goes if its in TWRP or other recoveries. I've done it in that fashion ever since my digitizer messed up. Still looking for a way to fix it. No parts sold where I live
The adb trick should run fine.
If you have original firmware(or some of the very alpha cm9/cm19 kernels w/ HDMI enabled) you can try connecting the hdmi to a tv and see if you have the mirror feature enabled. If so, you can see your screen. As for input, you would need a usb keyboard and the multimedia dock or a hack cable.
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