I didnt see this anywhere.. it probably is somewhere... so sue me if im reposting.....but...
if you are stuck on the android screen and dont want to take out battery and put sd in a card reader and all the fun enjoyable stuff that comes with altering the phone then...
open the slider.... press and hold power and call button... it should(98%) of the time bring up the power down menu and voice call menu at the same time.. just press home and youll be at your status bar.. nothing else though.. no menu or settings.. but you can connect usb and add files without the trouble of opening everything...so on and so fourth.. hope this helps someone....
again i apologize if this is a repeat... hopefully it will help someone....
thanx for lookin......!
good share ill be the first to say i didnt know that
lol, im glad it will help someone...lol
i got tired of taking battery out and using the card reader so i started pressing buttons....lmao... vuala! it's saved me some time..... now if i could get help in my other thread i would be ecstatic!
Another method would be booting into recovery mode (Power off, press and hold Home+Red until you see text scrolling and etc)
Then connect via USB, open an adb shell, mount your sdcard, and push/pull whatever you want.
Code:
[[email protected] ~]$ adb shell
# mount /sdcard
# exit
[[email protected] ~]$ adb push /home/rawr/Desktop/blahh.file /sdcard/blahh.file
37 KB/s (6865 bytes in 0.178s)
[[email protected] ~]$ adb shell reboot
haykuro said:
Another method would be booting into recovery mode (Power off, press and hold Home+Red until you see text scrolling and etc)
Then connect via USB, open an adb shell, mount your sdcard, and push/pull whatever you want.
Code:
[[email protected] ~]$ adb shell
# mount /sdcard
# exit
[[email protected] ~]$ adb push /home/rawr/Desktop/blahh.file /sdcard/blahh.file
37 KB/s (6865 bytes in 0.178s)
[[email protected] ~]$ adb shell reboot
Click to expand...
Click to collapse
This is great to know, I borrowed a microsd card reader from a friend and wasted about four hours not knowing this trick. Awesome, thanks.
Thanks man. Bookmarking this for future use.
Ooglez said:
This is great to know, I borrowed a microsd card reader from a friend and wasted about four hours not knowing this trick. Awesome, thanks.
Click to expand...
Click to collapse
haha same happened here, it's the sole purpose i even bothered checking if the ADB service was active in recovery mode. you're very welcome
I used that too but it sometimes is just easier, but yea thanx for adding that here. I know its gonna help someone
Related
Ok long story short i was getting the Power button mishaps. So i banged my phone to fix it worked great a few times but last night while doing so i cracked my screen Stupid move ever lol. KIDS DONT TRY IT !!!!
Its all black now and i want to be able to retrieve my pics on the phone.Cause when i connect it to my PC it does nothing just charge.
How can i so since i cant see nothing?
Broken screen
Colombia81er said:
Ok long story short i was getting the Power button mishaps. So i banged my phone to fix it worked great a few times but last night while doing so i cracked my screen Stupid move ever lol. KIDS DONT TRY IT !!!!
Its all black now and i want to be able to retrieve my pics on the phone.Cause when i connect it to my PC it does nothing just charge.
How can i so since i cant see nothing?
Click to expand...
Click to collapse
Did you save your photo's on your internal storage or on an external SD? If you saved them externally you can put your Micro SD in a flash drive and pull it up that way.
Or if for some reason you do not have access to an sdcard adapter you could use adb and pull them from the phone from a terminal.
Sent from my SGH-T989 using xda premium
bseager said:
Did you save your photo's on your internal storage or on an external SD? If you saved them externally you can put your Micro SD in a flash drive and pull it up that way.
Click to expand...
Click to collapse
codecaine21 said:
Or if for some reason you do not have access to an sdcard adapter you could use adb and pull them from the phone from a terminal.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Most of the are on my internal SD ... How would i go using ADB method ?
Colombia81er said:
Most of the are on my internal SD ... How would i go using ADB method ?
Click to expand...
Click to collapse
Reboot into recovery(Not download mode). open a terminal and use adb's pull command. You could use adb's pull command in conjunction with the find command. Something like
Code:
adb shell find / -name "*.jpg" -exec adb pull {} ~/Documents +
This will pull all files ending with the jpg extensions. You can of course pull whole folders.
I just wrote that off the top of my head and it wasnt tested. I have to get to bed. I have to get up at 4:30am for work and it is now 11:30. Damn computer is so addicting! The one liner might not work but you get the point. Google adb pull and adb push.
codecaine21 said:
Reboot into recovery(Not download mode). open a terminal and use adb's pull command. You could use adb's pull command in conjunction with the find command. Something like
Code:
adb shell find / -name "*.jpg" -exec adb pull {} ~/Documents +
This will pull all files ending with the jpg extensions. You can of course pull whole folders.
I just wrote that off the top of my head and it wasnt tested. I have to get to bed. I have to get up at 4:30am for work and it is now 11:30. Damn computer is so addicting! The one liner might not work but you get the point. Google adb pull and adb push.
Click to expand...
Click to collapse
Thanks the issue will be to see if im on recovery mode since i cant see nothing
Colombia81er said:
Thanks the issue will be to see if im on recovery mode since i cant see nothing
Click to expand...
Click to collapse
A friend had the same issue a few weeks ago and I just popped her battery out and popped it back in. Then held the power + vol up + vol down till i felt vibration and held on for another 2 seconds. Then waited 20 seconds just to be safe. I connected my phone. I ran sudo adb devices in a terminal to make sure it was connected. Which is was and then ran the necessary commands.
Sent from my SGH-T989 using xda premium
codecaine21 said:
Code:
adb shell find / -name "*.jpg" -exec adb pull {} ~/Documents +
Click to expand...
Click to collapse
Yeah that didnt work its in recovery now. Im trying to figure this out i just dont want to d/l the pics. I dont mind backing up the whole entire thing. How would i go on doing that.
Colombia81er said:
Yeah that didnt work its in recovery now. Im trying to figure this out i just dont want to d/l the pics. I dont mind backing up the whole entire thing. How would i go on doing that.
Click to expand...
Click to collapse
That's a tough one... for me at least. I mean you are able to reboot into recovery but I am unaware of a method that will allow you to back your system up from a terminal. Adb has a backup command but you need to be able to see your screen to use it.
You could use the dd command over ssh ->
Code:
[B]sudo adb shell dd if=/dev/block/mmcblk0 | sudo ssh [email protected] "dd of=/~/Documents/recovery.img"[/B]
and check the progress with
Code:
[B]while true; do readarray -t array < <(pgrep -l '^dd$'); var=$(echo "${array[@]}" | sed 's/ dd//g'); kill -USR1 $var &>1 && sleep 5; done[/B]
but I "think" the FAT32 FS is limited to 4GB file transfers. So you will receive an error after 4GB's and the transfer will abort. Also, I am unsure of the t989's pit layout. Which blks you would need to backup if you did decide to dd single partitions. Like cache, system, recovery, boot, etc.
Maybe some computer whiz will be able to help you. I am sorry I couldn't help. Maybe one of the more experienced Linux/android users/devs can help you if you haven't already figured this out.
If someone did know, it would be cool if you could post the solution. I am curious as how to one would go about doing this.
Sent from my SGH-T989 using xda premium
codecaine21 said:
Reboot into recovery(Not download mode). open a terminal and use adb's pull command. You could use adb's pull command in conjunction with the find command. Something like
Code:
adb shell find / -name "*.jpg" -exec adb pull {} ~/Documents +
Click to expand...
Click to collapse
Im hoping you are still around for some more assistance. Im actually in the middle of the same issue as OP, except possibly that the phone was completely stock with android debugging disabled, and the touch interface is also non-functional. You'd think that would be great for getting stuff off the phone, but I was unable to use the on screen menu to actually turn on usb mass storage.
I decided to try and use push / pull from recovery, however I found out that the directories I want arent available in recovery mode (DCIM / Download with a very very important 0000001.vcf in it).
I was able to get into recovery and use "adb reboot download" and Odin'd "recovery-cmw-hercules.tar" to the phone to give me a working CMR environment (v5.0.2.6). I thought I could feel my way through the menus after another "adb reboot recovery" to blindly guess - Vol Down x 6, Pwr x 1, Vol Up x 2, Pwr x1 - type thing, to navigate"mounts and storage" and then find "mount sdcard".
However, I have been unsuccessful. I did manage to mount system / data / cache , just not sdcard, and I dont know why.
TLR No screen, no touch. Odin'd CMR. Am sitting in Command Prompt with ADB Shell / Pull working. Still can't access ~/DCIM folder on internal SDCard. Hoping for some help. What am I missing? Bonus: A screen shot of the CWR mounts and storage menu would be very helpful!
Ok so i got it....
So I first used this comand:
Code:
adb shell find / -name "*jpeg"
It gave me this
/sdcard/Download/155546_394801767258170_1181721421_n.jpeg
Then i used this command to pull everything from my internal sd-card
Code:
adb pull sdcard C:/Docs
Worked like a Charm
so my wife dorpped her s3 and broke the screen, the phone is rooted and i have adb debugging turned on i can use adb to pull/puch etc. but i dont know how, could some on tell me what adb commands i need to issue to the device to pull her internal sd data to my computer and push it back to her new s3, i also need to know how to wipe her phone with adb and reset to stock so i cna return it to the insurancce company, if anyone could tell me how to basically pull everything from her phone, internal sd data, and her text messages i know to pull the texts and view them i will need to use sqlite 3 to view the .db of her text messages but i cant figure out the commands to do so and i cant figure out how to format the commands so that it will pull the info to my desktop for viewing through sqlite 3 on the computer, also if i need to install sqlite 3 on the device with adb i need to know the commands for that as well, all help is welcomed, i have to get this thing back to stock in the next week or so, you are even more than welcome to call me an idot noob because i really am, i am very technically inclined and can follow complex instructions provided they are complete, please help ! lastly is there an adb command that would transfer what should be displayed on the screen if it worked within a emulator window if so please include that information as well.
This has been solved thanks to the info that was given, i was able to wrap my head around the entireity of adb, and my actual problem was not formatting of commands, my wife had a lock screen so i had to get that unlocked before adb would allow pulls if you need to do this with you phone i have posted a tutorial in the android general development and hacking [developers only] forums
MotoDefier said:
so my wife dorpped her s3 and broke the screen, the phone is rooted and i have adb debugging turned on i can use adb to pull/puch etc. but i dont know how, could some on tell me what adb commands i need to issue to the device to pull her internal sd data to my computer and push it back to her new s3, i also need to know how to wipe her phone with adb and reset to stock so i cna return it to the insurancce company, if anyone could tell me how to basically pull everything from her phone, internal sd data, and her text messages i know to pull the texts and view them i will need to use sqlite 3 to view the .db of her text messages but i cant figure out the commands to do so and i cant figure out how to format the commands so that it will pull the info to my desktop for viewing through sqlite 3 on the computer, also if i need to install sqlite 3 on the device with adb i need to know the commands for that as well, all help is welcomed, i have to get this thing back to stock in the next week or so, you are even more than welcome to call me an idot noob because i really am, i am very technically inclined and can follow complex instructions provided they are complete, please help ! lastly is there an adb command that would transfer what should be displayed on the screen if it worked within a emulator window if so please include that information as well.
Click to expand...
Click to collapse
I'm not going to call you an idiot noob. It seems to me that you know a little more than you express. A few Google searches could answer all of your questions. You are asking for someone to write you a novel, it's not going to happen.
Aerowinder said:
I'm not going to call you an idiot noob. It seems to me that you know a little more than you express. A few Google searches could answer all of your questions. You are asking for someone to write you a novel, it's not going to happen.
Click to expand...
Click to collapse
google has actually been un helpful in this dilema, however I think the explaination of adb commands on the sdk's page looks like it has enough information for me to write, my own novel (lol) so I will start there tonight, and hope that I understand the procedures described as well as I think I do, thanks for the reply anyway
Now that I have a little more information I guess what I really was trying to ask is for someone to give me a little better understanding of how issuing commands work I know how to issue ADB commands for instance with ADB HELP OR HELP ALL the command looks like this in the example. Adb pull [<local>] [<remote>] i dont understand what information adb is looking for where it says local and remote, is adb looking for me to type the [<local>] [<remote>] exactly this way or is it leading me to give a path for local and a path for remote, if so how do i go about figuring out said paths?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Local would be path on pc, remote would be path on phone.
sorry, for asking probably dumb questions
Aerowinder said:
Local would be path on pc, remote would be path on phone.
Click to expand...
Click to collapse
I know that it sounds stupid that i know how to open adb, i know how to issue commands (mostly) and i know that you said you think i know more than i am taking credit for, but heres the thing i do know ALOT about computers and can do almost anything with them however Command line utilities is not my strong suit, so local is the path on the pc remote is the path on the phone i am assuming that this would be the proper way to pull the sd data
adb pull -shared [< / sd>] [< C:\user agentlogon\Desktop>] if i wanted to store the file on my desktop would that be correct or am i just completly command line retarted? , i know that this isnt the real path but if it were is this correct formatting for the command line?
Like this: adb pull -shared "/sd" "C:\user agentlogon\Desktop"
Adb kill-server
Adb start-server
Adb pull <file> <Local>
Sent from my LT26i using xda app-developers app
Aerowinder said:
Like this: adb pull -shared "/sd" "C:\user agentlogon\Desktop"
Click to expand...
Click to collapse
Ok, so sorry, at this point i feel like a total idiot and im sure if your not right there with me your getting close, but i think this last question will help me understand command line utils better in the future, so when you see [<>] am i correct that the utility is showing me its okay to perform said command on [ ] directories <> files ? Also i am a very literal learner so do i use the quotes on the command or are you just quoting me?
[<>] = variable. Replace the entire sequence. So, [<local>] = "C:\directory\file.ext" This is not standardized across commandline apps. The [<>] is only meant to show the user that they need to replace this with his/her own value.
In commandline utilities, spaces separate commands, this is why you need quotations around directories that have spaces. If you don't, the C:\... directory will be interpreted as two seperate commands, resulting in a syntax error. I always use quotations around directories out of habit. / is often used as a switch. To be safe, always quote directories. This is standardized across all commandline apps.
TrinityHaxxor said:
Adb kill-server
Adb start-server
Adb pull <file> <Local>
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
Yeah i got the kill start sever on lock, and i am wanting to pull thecentire contents of the sd, not a single file, but thanks for your input it is all welcomed!
Aerowinder said:
[<>] = variable. Replace the entire sequence. So, [<local>] = "C:\directory\file.ext" hhis is not standardized across commandline apps. The [<>] is only meant to show the user that they need to replace this with his/her own val
In commandline utilities, spaces separate commands, this is why you need quotations around directories that have spaces. If you don't, the C:\... directory will be interpreted as two seperate commands, resulting in a syntax error. I always use quotations around directories out of habit. / is often used as a switch. To be safe, always quote directories. This is standardized across all commandline apps.
Click to expand...
Click to collapse
now i have a new problem it is saying /sd does not exist do you possibly have a screenshot of the path for the sd in a file manger you could post for me if not i will try to look at it with my wifes new phone and hope that the stock file system is the same as the modded system she has on the broken phone. also if this doesnt work how would i just do a full wipe of the phone so it looks like i just wiped it for privacy.
Try:
/storage/sdcard
/storage/sdcard0
/mnt/sdcard
/mnt/sdcard0
One of those should work.
Aerowinder said:
Try:
/storage/sdcard
/storage/sdcard0
/mnt/sdcard
/mnt/sdcard0
One of those should work.
Click to expand...
Click to collapse
IIts not giving me any errors, but its not giving me the files either, i tried to adb root to see if that would change and it says adbd cannot run as root in production builds, i tried to adb remount it says opperation not permitted, i tried adb shell then su and adb freezes and wont let me exit shell, it either freezes or just echo's what i type, so if i type exit it returns exit showing the word exit twice but leaves me no choice other than to close cmd and re open and restart adb, not sure what im doing wrong, the device show with adb devices in adb and shell but then says device not found when i try to su in shell lol, fml!
So, yesterday my brothers Pit bull, Maggie, knocked my GS3 out of my hand and onto the cement driveway...
The result? A shattered screen, cracked display, and broken digitizer.
I wanted to perform a backup of my current rom (CM11 Latest Nightly) but figured out that my computer was not authorized for ADB.
Well, I wasn't about to let that stop me. Here is what I did to fix that little problem.
The following guide assumes that you already have the drivers for your phone installed and also that you have ADB set up.
I have only tested this on TWRP 2.7.1.0. I do not know if it will work on other recoveries.
First things first, power off your device by doing a battery pull.
This is the best way to ensure you are fully powered down since you can't see the screen.
Next, boot your device into recovery by pressing and holding the power, home, and volume up buttons.
Once you feel the device vibrate, release the buttons.
Plug in your phone and pull up a command prompt window.
Check and see if the device is being recognized by running
Code:
adb devices
.
Connect to the device by running
Code:
adb shell
.
Next, to mount the data partition where the files we need to edit are located, run the following code.
Code:
mount -t ext4 /dev/block/mmcblk0p15 /data
It is very important you type this exactly as written. Double check a few times to be sure.
Exit the shell by typing
Code:
exit
Now, we need to find our computer's adb key. For me, it was located in "C:\Users\%Username%\.Android\".
The file we are looking for is adbkey.pub.
Push this file to your device using
Code:
adb push adbkey.pub /sdcard/adbkey.pub
Pull up another shell by typing
Code:
adb shell
Remove the current adb key by typing
Code:
rm /data/misc/adb/adb_key
Insert the key into your phone's authorized keys by typing
Code:
cat /sdcard/adbkey.pub >> /data/misc/adb/adb_keys
Exit the shell
Reboot your device with
Code:
adb reboot
Profit! :good:
Hey buddy! Great tutorial! However, I'm getting an error trying to mount mmcblk0p15. I get the error:
"mount: mounting /dev/block/mmcblk0p15 on /data failed: Invalid argument"
Do i need super user privilege do to this?
Thanks! Great tutorial, btw.
Afternoon all,
My G4 has hit the bootloop for the last few days. Periodically, it has powered up to the main screen, but not for long enough for me to recover data.
I just spoke to a data recovery place that told me that if I can put my phone into download mode, they can recover the data. Lo and behold, my phone is currently next to me in download mode!
I'm quite keen to avoid dropping that amount of money if possible, so does anyone know of a way to recover the internal memory of the phone via download mode?
Apologies if I'm duplicating a previous thread - I had a quick look, but couldn't see any with the same issue.
Probably when the phone is in download mode they can copy the partitions bit by bit then try to do data recovery from those partition images.
So if the phone doesn't boot, it doesn't mean the data partition is corrupted so in theory you could try to copy the data partition and mount it and see what files you can recover.
I do not know the exact commands to dump the data partition but I think that's the way it can be done.
Anyone else willing to give a hand here?
Thanks for the help so far. I believe the data is intact - when the phone starts up, the data is all there. It's just accessing it that is the issue.
Sent from my Nexus 5 using Tapatalk
something similar to
Code:
dd if=/dev/block/mmcblk0p55 bs=8192 skip=65536 count=548352 of=/mnt/media_rw/external_SD/data.img
OR
Code:
dd if=/dev/block/mmcblk0p55 bs=8192 skip=65536 count=548352 of=/dev/block/mmcblk1/data.img
don't quote me on that but in theory this should work...
make SURE you have a 32gb SDCard in the phone first
Where would that command be entered mate? Sorry, only ever used my phone stock before.
Sent from my Nexus 5 using Tapatalk
I thought the OP title said download mode?
Use the LG Root method as if you were going to root..
I'm mobile ATM but if I remember correctly...
Send_Command \\.\Com# [# meaning your com port number]
Then insert that command.
Tomorrow at work I can get a common list of partition names and the command to back it up with.
je2854 said:
I thought the OP title said download mode?
Use the LG Root method as if you were going to root..
I'm mobile ATM but if I remember correctly...
Send_Command \\.\Com# [# meaning your com port number]
Then insert that command.
Tomorrow at work I can get a common list of partition names and the command to back it up with.
Click to expand...
Click to collapse
You need to mount the partition first.
Also, you could mount data if it is not encrypted (is it?)
Do this:
Code:
mkdir /temp
mkdir /temp/sd /temp/data
mount /dev/block/mmcblk1p1 /temp/sd
mount /dev/block/bootdevice/by-name/userdata /temp/data
mkdir /temp/sd/recoverydata
cp -R /temp/data/media/ /temp/sd/recoverydata/
A little tip that should work :
Take the battery off your phone
Put both phone and battery in the fridge
Wait till the phone is cold and boot the device.
The bootloop trouble is due to an abnormal warm so this way you can have a one shot normal boot to backup your data before send for warranty.
terisse said:
A little tip that should work :
Take the battery off your phone
Put both phone and battery in the fridge
Wait till the phone is cold and boot the device.
The bootloop trouble is due to an abnormal warm so this way you can have a one shot normal boot to backup your data before send for warranty.
Click to expand...
Click to collapse
If you try this, please put the phone in a ziploc bag 1st and seal it so humidity won't get inside the phone while in the fridge.
nagalun said:
You need to mount the partition first.
Also, you could mount data if it is not encrypted (is it?)
Do this:
Code:
mkdir /temp/sd /temp/data
mount /dev/block/mmcblk1p1 /temp/sd
mount /dev/block/bootdevice/by-name/userdata /temp/data
mkdir /temp/sd/recoverydata
cp -R /temp/data/media/ /temp/sd/recoverydata/
Click to expand...
Click to collapse
just a question though... How can you use this command if it will not boot?
---------- Post added at 08:59 AM ---------- Previous post was at 08:50 AM ----------
to get into download mode do the following...
Pull Battery
Hold Volume Up
Plug in USB Cable (make sure it's plugged in the computer)
Release button after 5 seconds
follow the link to grab the files needed for "Send_Command"
Grab LG Root here
once you are in the mode and you followed directions you can copy the command I wrote
above to copy your data partition. The reason you must have a 32gb+ SDCard is you will
be making an exact copy of the /data partition where you can remove the SDCard and recover
whatever is needed.
je2854 said:
just a question though... How can you use this command if it will not boot?
Click to expand...
Click to collapse
Hmm... With the Send_Command.............? dd is a command too :silly:
nagalun said:
Hmm... With the Send_Command.............? dd is a command too :silly:
Click to expand...
Click to collapse
there is no need to mount the partition first..
the dd command will copy the partition as a RAW image.
you must then take it to a computer and mount it as an EXT4 or use it with ext2explore
je2854 said:
there is no need to mount the partition first..
the dd command will copy the partition as a RAW image.
you must then take it to a computer and mount it as an EXT4 or use it with ext2explore
Click to expand...
Click to collapse
in that case the command you have given him will copy 4492 mb only.
Here is why:
Code:
dd if=/dev/block/mmcblk0p55 bs=8192 skip=65536 count=548352 of=/dev/block/mmcblk1/data.img
input_file=(some partition) block_size=8192 skip_this_much_data=65536 how_many_data=548352 output_file=(somewhere)
actual data copied is 8192 * 548352 = 4492099584 bytes, and you are skipping some data from the beggining with 'skip'
you do still need to mount the sdcard, the "mmcblk1" is not treated as a directory, and it is very unlikely the sd card is mounted automatically in download mode.
nagalun said:
in that case the command you have given him will copy 4492 mb only.
Click to expand...
Click to collapse
remember me saying (if you read) above that I said "something similar to"
Hi all. Firstly, thanks for all your responses!
I've not got much of a clue what I'm doing unfortunately, I've never really messed with Android before - I'm typically fairly computer literate, but I've steered clear of messing with and rooting phones for the most part.
So to clarify, I've downloaded LG Root, Running either of the exes just leads to a cmd box that's open for about a second before closing, so I'm presuming I've missed a step. Is there a guide already in existence on how to use it?
But once in, ensure there's a sizeable Micro SD card in (it's a 64gb so I should be okay!) and use the send_command exe to send:
Code:
mkdir /temp/sd /temp/data
mount /dev/block/mmcblk1p1 /temp/sd
mount /dev/block/bootdevice/by-name/userdata /temp/data
mkdir /temp/sd/recoverydata
cp -R /temp/data/media/ /temp/sd/recoverydata/
And then the entire image should be on the Micro SD card.
How would I then mount the data image to be readable? I've only used .iso for mounting before.
Apologies for my ignorance - I'm probably making helping me quite difficult!
Sorry all, correction to my previous:- Do I basically follow http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
And replace step 10 with the above command?
Shift+Right Click the folder you extracted "open command prompt here" for starters...
Run ports.bat first...
It'll tell you your DIAG and communication port...
The second com port is the one you are looking for.
Send_Command \\.\Com"#" (don't insert quotes, # being the number you found)
je2854 said:
Shift+Right Click the folder you extracted "open command prompt here" for starters...
Run ports.bat first...
It'll tell you your DIAG and communication port...
The second com port is the one you are looking for.
Send_Command \\.\Com"#" (don't insert quotes, # being the number you found)
Click to expand...
Click to collapse
I'm having the same issue and actually tried this earlier today. Ports.bat didn't show a DIAG communication port even when I had the phone stably sitting in Download Mode.
Going to try the freezer trick. I already bought a Nexus 6P, just want to unlock the locked content on my SD card. lol.
EDIT: Holy crap! It worked. I chilled it in a baggie, then stood in front of the freezer as I unlocked all of my locked gallery files (1,411 files totaling 900MB). As soon as I was done, 30 seconds after stepping away from the freezer, it started to bootloop again.
Got the only information I needed off my phone...nice! I might give it another go tomorrow and see if I can't run ROM Toolbox and backup all my apps so it'll be easier to push to my N6P.
Awesome suggestion!
IlyaKol said:
I'm having the same issue and actually tried this earlier today. Ports.bat didn't show a DIAG communication port even when I had the phone stably sitting in Download Mode.
Going to try the freezer trick. I already bought a Nexus 6P, just want to unlock the locked content on my SD card. lol.
EDIT: Holy crap! It worked. I chilled it in a baggie, then stood in front of the freezer as I unlocked all of my locked gallery files (1,411 files totaling 900MB). As soon as I was done, 30 seconds after stepping away from the freezer, it started to bootloop again.
Got the only information I needed off my phone...nice! I might give it another go tomorrow and see if I can't run ROM Toolbox and backup all my apps so it'll be easier to push to my N6P.
Awesome suggestion!
Click to expand...
Click to collapse
Mine will only get to optimising Apps, even if still in the freezer.
Sent from my Nexus 5 using Tapatalk
Hi all, sorry for the double posting, but just to make certain before I do something that will accidentally brick my phone. I'm intending to do the following:
Put phone in download mode and connect device.
Open LG_Root folder
Run a command window in LG_Root
Code:
Send_Command.exe \\.\Com4
Then, line by line, command:
Code:
mkdir /temp/sd /temp/data
mount /dev/block/mmcblk1p1 /temp/sd
mount /dev/block/bootdevice/by-name/userdata /temp/data
mkdir /temp/sd/recoverydata
cp -R /temp/data/media/ /temp/sd/recoverydata/
Once I've done all this, what happens next? Will I see responses on the screen etc?
Again, I apologise for the probably stupid questions. I don't want to brick my phone and lose all of the data, but I'm going away with work so would like to square it before I go if I can.
Many thanks to you all so far.
Hi,
my OnePlus 3 got crushed. Felt down while driving motorbike and then at least 3 cars did drive over it. Display splintered in thousands of pieces and digitizer is dead. Home button with fingerprint also seems to not work.
By miracle the phone itself still works. . How I can enter the phone? I tried to boot into recover and browser with ADB but I dont know where my files are.
BTW USB Debugging was not activated, not rooted and Pattern lock is activated. The phone also asks for pattern lock on boot (I am worried that this means that my files are encrypted)
What else I can do?
fxppas said:
Hi,
my OnePlus 3 got crushed. Felt down while driving motorbike and then at least 3 cars did drive over it. Display splintered in thousands of pieces and digitizer is dead. Home button with fingerprint also seems to not work.
By miracle the phone itself still works. . How I can enter the phone? I tried to boot into recover and browser with ADB but I dont know where my files are.
BTW USB Debugging was not activated, not rooted and Pattern lock is activated. The phone also asks for pattern lock on boot (I am worried that this means that my files are encrypted)
What else I can do?
Click to expand...
Click to collapse
send it back and pay money for repair or you can buy yourself a new display + digitizer
for the glass oneplus take ~100 dollar. someone in this forum had the same problem.
you can ask the support first
Without debugging and with encryption you really can't do much ...
Sent from my OnePlus 3 using Tapatalk
@panther124
I just want to have my data back.. I dont really want to fix it. The mobile phone is slightly bended and has tons of scratches on the backside and a big bump. If you see the phone you will be surprised that it is still working As far as I understand is the data lost if I send the phone back.
Isnt it possible to connect just another cheap display on the phone to just for passing the lock. So I can enable debugging.
fxppas said:
Hi,
my OnePlus 3 got crushed. Felt down while driving motorbike and then at least 3 cars did drive over it. Display splintered in thousands of pieces and digitizer is dead. Home button with fingerprint also seems to not work.
By miracle the phone itself still works. . How I can enter the phone? I tried to boot into recover and browser with ADB but I dont know where my files are.
BTW USB Debugging was not activated, not rooted and Pattern lock is activated. The phone also asks for pattern lock on boot (I am worried that this means that my files are encrypted)
What else I can do?
Click to expand...
Click to collapse
Hi
did you unlock the bootloader?
maybe you could still root it and adp push / pull stuff from it
AlexLebowski said:
Hi
did you unlock the bootloader?
maybe you could still root it and adp push / pull stuff from it
Click to expand...
Click to collapse
I can enter shell with adb if I use power+vol up to boot into bootloader. But I dont know where my files are. "/sdcard" /media / mnt" I dont find anything.
fxppas said:
I can enter shell with adb if I use power+vol up to boot into bootloader. But I dont know where my files are. "/sdcard" /media / mnt" I dont find anything.
Click to expand...
Click to collapse
try look into "/storage" or "/data", or any other directories, use "adb pull" to copy everything you can to your computer.
Internal storage is at /storage/emulated/0
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
Internal storage is at /storage/emulated/0
Click to expand...
Click to collapse
[email protected] ~/on3bu $ sudo adb shell
[email protected]:/ $ cd /storage/
[email protected]:/storage $ ls
sdcard0
[email protected]:/storage $ ls -l sdcard0
lrwxrwxrwx root root 1970-04-23 10:16 sdcard0 -> /sdcard
[email protected]:/storage $ exit
[email protected] ~/on3bu $ sudo adb pull /storage/sdcard0
failed to copy '/storage/sdcard0' to './sdcard0': No such file or directory
[email protected] ~/on3bu $ sudo adb pull /sdcard
failed to copy '/sdcard' to './sdcard': No such file or directory
[email protected] ~/on3bu $ sudo adb shell
[email protected]:/ $ ls /storage/
sdcard0
[email protected]:/ $
Not with my phone
Hey, sorry for the late reply, i've been sick the last day.
First of all a stupid question
Have you seen that all your data is there under /storage/sdcard0? or is it an empty folder
try specifying the output directory of adb pull like
Code:
adb pull /storage/sdcard0 /home/username/
I'm thinking maybe it's a linux related problem, since linux doesnt always automatically create folder structures. So if your error message changes keep me posted.
Also:
my data is directly under /sdcard
so if i
Code:
adb pull /sdcard
I get
Code:
pull: building file list...
pull: /sdcard/ViPER4Android/DDC/Custom_jmxc23.vdc -> ./ViPER4Android/DDC/Custom_jmxc23.vdc
and Last but not least
maybe the sdcard isn't mounted correctly...
try
Code:
mount -a
in adb shell and leaye the shell open, then open a new one and try pulling the stuff from it.
I'm also new to XDA so until now i only had to solve my own problems but maybe it helps just give it a try
I'm also not shure if your pattern lock has encrypting your data (/sdcard).
but there is also a solution for removing lockscreen patterns via adb shell.
Good Luck,
Alex