yashsingh1/xdaforums huggingface dataset:
[G4 Q&A, Help & Troubleshooting] Norcalz71:
am i correct in assuming that mmcblk0p1 is Storage 0, partition one (internal storage partition 1) and mmcblk1p1 is Storage 1, partition 1 (sd card, partition 1)?

Thanks again,
[G4 Q&A, Help & Troubleshooting] Norcalz71:
i got it booted up again (fingers crossed it stays) and managed to find the mount points and look with the ls command to see all my picture files. however, when i go to cp -R from data to the SD card, it only copies a few things and then returns to the prompt. I just lost it again so hopefully i can make it work again, but how do I make sure all the contents of the DCIM folder copy over? doing ls /data/media/0/DCIM/camera I can see the files on the internal, but it only copies over 1 .jpeg when i run the cp command. help!

EDIT: i popped out the microsd and put it in my computer - it appears it did not copy anything over even though I could run ls commands and see the file structure I created, is there a chance the /dev/block/mmcblk1p1 is the wrong partition to mount for the external SD card and I was actually writing to another partition that I mounted to /temp/sd??

EDIT: what format (exFat, FAT32, etc) does the external SD need to be? i noticed that if i just run ls with no parameters, there is a /storage and/storage/external_SD. Is that the microsd card already mounted to that point? After the phone looped again the first time, i let it sit then tried again. this time when I ran the ls command, i could not see the file structure in /data - is that bad? any chance I blew it and overwrote that on accident by mounting mmcblk1p1 to /temp/sd and copying there? could mmcblk1p1 be the data partition?
[G4 Q&A, Help & Troubleshooting] nagalun:
No, that should not be it, the sdcard was not mounted, right? The sdcard should be fine on fat32, and can you copy everything the "mount" command says and paste it here?

Just let the phone sit turned off for a few hours, you almost had it

---------- Post added at 07:19 AM ---------- Previous post was at 07:16 AM ----------

Yes, you can run ls /dev/block/ to see all the partitions. And check if in mmcblk1 there are more than one partition, or only the file (mmcblk1)
[G4 Q&A, Help & Troubleshooting] dontpannic:
I don't think it will work with Download Mode. Isn't the whole issue that there's a dodgy connection between the eMMC and the mainboard (bootloop as it can't find the storage to boot from?).

If the phone can't see the storage then download mode won't be able to either.
[G4 Q&A, Help & Troubleshooting] nagalun:
There are different kinds of dodgy, maybe it works for a while until it heats up, or maybe it just doesn't work, in that case the phone shouldn't even turn on because it can't read the bootloader, Download Mode just gives you a nice shell that boots up quickly and allows for more success because it doesn't stress the eMMC and CPU as much as booting android... In theory. :confused:
[G4 Q&A, Help & Troubleshooting] dontpannic:
Hmm. I was under the impression it was a physical fault with a solder joint - hence why contracting the solder by putting the phone in the freezer seems to temporarily allow it to boot.

Bootloader will be stored separately from the storage eMMC chip I would have thought - same way as your PC's BIOS will display even if you don't have a hard disk attached.
[G4 Q&A, Help & Troubleshooting] nagalun:
It very likely is a weak joint on the memory chip (Could be other things as well), I didn't say it wasn't a hardware problem.

It is different on phones as far I know, if the phone can't read/verify the bootloader a recovery firmware is loaded instead, aka: "QHSUSB_BULK"

That is also why it is dangerous to resize partitions, and most developers choose to reassign them instead.
[G4 Q&A, Help & Troubleshooting] Norcalz71:
So I ran it again and was able to do an ls /data/media/0/DCIM/camera and see all the JPEG files - so it seems they are still there. ls /dev/block did not seem to bring up a list of partitions - does it need to be mounted somewhere first or is there another command I could try? mount command showed (off hand, running to work now) system, cache, userdata, and a few others, but did not seem to show mmcblk1 or storage or external_SD. if there was only one partition on the SD would the proper command just be mmcblk1 rather than mmcblk1p1?

I definitely think I am "seeing" the files in the /data mount so its still there, just a matter of getting them to actually copy to the SD card. hopefully it can be mounted in download mode this way.
[G4 Q&A, Help & Troubleshooting] nagalun:
[MENTION=3711569]Norcalz71[/MENTION]

>ls /dev/block did not seem to bring up a list of partitions - does it need to be mounted somewhere first or is there another command I could try?

That's weird, did you try with a slash on the end?

And yes, the mount command says where are the files, for example, on my phone:

/dev/block/mmcblk0p1 on /firmware type vfat (...)

In this case you should do:

ls /dev/block/

Note that if you see something like this (or similar with "by-name" on the path):

/dev/block/platform/msm_sdcc.1/by-name/userdata on /data type ext4...
/dev/block/bootdevice/by-name/userdata on /data type ext4.. (not sure about this one)

"msm_sdcc.1" is the name of the chip on my phone, so you want to change it to what your phone says. Go one lower (maybe, I don't know for sure, try all and look for mmcblk1):

ls /dev/block/platform/ (there may be two folders here, check both)
ls /dev/block/platform/msm_sdcc.1/
ls /dev/block/bootdevice/

>if there was only one partition on the SD would the proper command just be mmcblk1 rather than mmcblk1p1?

Yep, and since there is a directory already made you can mount it there.

If there is no mmcblk1 then it means the sdcard is not detected.

mount /dev/block/mmcblk1 /storage/external_sd

After doing that ↑ do mount again and check the end of the list for what you just did:

/dev/block/mmcblk1 on /storage/external_sd type vfat (rw,...)

If you don't see anything it could be some things:

You may need busybox for this?

It doesn't like fat32? Try ext4?

The SD Card is not inserted all the way (?)
[G4 Q&A, Help & Troubleshooting] Norcalz71:
Again, awesome. Thanks man. I did not have the / doing:

ls /dev/block

instead of

ls /dev/block/

so that may be the issue, i'll try it again when I have some time with the freezer.

Has anyone else with a stock/non-rooted phone confirmed that the SD card is mountable in DL mode?
[G4 Q&A, Help & Troubleshooting] Norcalz71:
tried :

ls /dev/block/

instead of

ls /dev/block

still nothing comes up. checking mounts I dont see storage/mmcblk1p1 or mmcblk1 anywhere - are there any other commands to try and see where it might be mounted to (or is that a sign the SD card is not recognized?)

I remember for the root commands with dd, it had to be on internal storage because you could not access the SD card - is it possible this is the same deal and the sd card is not mountable/accessible in download mode?

I know the data is there (i think) since I can see it all with the ls command on the internal storage /data, I'm just wondering if there are any other commands that could perhaps transfer over the USB back to the PC if the sd card cant be found. still holding out hope.
[G4 Q&A, Help & Troubleshooting] nagalun:
This is the command they used to root the lg g4 in download mode:

dd if=/data/media/0/system.rooted.vs98611a.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0

As you can see they are using the same location that I'm telling you to look in, so I don't know what is happening that you can't see the files, "ls" works on all directories but that one? Why?

If the reason is that there is too many text from the output (many files), you could try this to look only for the files we want:

ls /dev/block/mmcblk1*

If that still doesn't bring up anything... Well, technically you can still transfer the files...

Look in here and tell me if there's a file named "adbd":

ls /sbin/

Also tell me what other files you see, not sure if we can run adbd without getting rid of the firmware flash program, but try it, do this:

setprop ro.secure 0
setprop ro.adb.secure 0
setprop ro.debuggable 1
setprop sys.usb.config adb

Now hopefully you can detect your phone in adb devices, and in a terminal/cmd from your pc, go to a directory you want your photos to be in, with "cd", example:

cd C:\Users\Norcalz71\Desktop\camera

Then do this:

adb pull /data/media/0/DCIM/camera/ .

If that doesn't work then tell me, there is another way, I think.
[G4 Q&A, Help & Troubleshooting] Norcalz71:
Will do! Looks like we are different time zones so I will have to give it a go after work later today.

is the /dev/block an actual directory? Still trying to learn the whole "mounting" thing with linux, as I understand it for example mmcblk0p55 might be the userdata partition block, which in this case is mounted to the directory /data. Is /dev/block/mmcblk0p55 a directory as well that you could identify as such and that just gets mounted to /data, or is /dev/block/mmcblk0p55 more of an address for a partition that must be mounted somewhere before it can be read?

I have the gpt.img from my previous g4 (the one I had to return, but they are both att H810 models) - would that have the address location for the external SD partition?
[G4 Q&A, Help & Troubleshooting] nagalun:
[MENTION=3711569]Norcalz71[/MENTION]

https://en.m.wikipedia.org/wiki/Everything_is_a_file

>Is /dev/block/mmcblk0p55 a directory as well that you could identify as such and that just gets mounted to /data, or is /dev/block/mmcblk0p55 more of an address for a partition that must be mounted somewhere before it can be read?

mmcblk0 is a file that represents the entire memory chip, partition table and everything, and mmcblk0p55 is specific to the partition number 55, in this case the data partition, you can read and do stuff with the file itself without mounting it (don't), mounting just makes the driver for the specific filesystem (ext4) to 'open' it in the directory you specify and handle writes and reads (many other things as well)

And yes, if what you are seeing has a / on the end, it is a directory separator:

/dev/block/mmcblk0

/dev is a directory, and it has another directory inside of it called block, that has the files that represent the memory devices, sdcard, emmc, etc

>I have the gpt.img from my previous g4 (the one I had to return, but they are both att H810 models) - would that have the address location for the external SD partition?

I'm not sure what is that file, but if it is the GPT partition table then it contains where each partition starts and ends, for the internal memory.
[G4 Q&A, Help & Troubleshooting] Norcalz71:
thats it, GPT partition table. So that only holds the data for the internal memory, got it.
[G4 Q&A, Help & Troubleshooting] Norcalz71:
Is it possible to Bork anything doing the setprop commands? Are they permanent changes or reset once the phone powers off? And should those just be run via send command? And then, in theory, adb should see the phone while still in DL mode?
[G4 Q&A, Help & Troubleshooting] nagalun:
Those props are not persistent, and yes, via send_command. If 'adbd' is not in /sbin/ then I don't think it's going to work.

Also, try to turn off selinux before the setprops:

setenforce 0
[G4 Q&A, Help & Troubleshooting] Norcalz71:
I did find adbd within /sbin/ via /ls /sbin/.

Heres everything in there:

#ls /sbin
Aat_Frblank
Aat_HVDCP
Aat_OTG
Aat_Warning
Aat_audio
Aat_auto_detect
Aat_blank_test
Aat_camcorder
Aat_cameraOIS
Aat_cameraVT
Aat_camera_main
Aat_dmb_hdmi
Aat_facver
Aat_gps_bt_wifi
Aat_info_1
Aat_info_1_e
Aat_info_2
Aat_irda_irrc
Aat_key_press
Aat_lcd_auto
Aat_led_display
Aat_loopback
Aat_m_sensor3
Aat_mainlist
Aat_mp3
Aat_nfc_felica
Aat_result
Aat_sensor_auto
Aat_touch_auto
Aat_touch_draw
Aat_tumble
Aat_vibrator
Atd_event
LcdUpdate
Mfts_auto_det
Mfts_cam_main
Mfts_cam_vt
Mfts_compass
Mfts_ear_jack
Mfts_irrc_irda
Mfts_key_sensor
Mfts_led_disp
Mfts_main
Mfts_mic_record
Mfts_nfc_felica
Mfts_rcv
Mfts_spk
Mfts_touch_auto
Mfts_touch_draw
Mfts_video
Selfd_accel
Selfd_atd
Selfd_auto_detect
Selfd_cameraVT
Selfd_camera_main
Selfd_gps_bt_wifi
Selfd_main
Selfd_mic
Selfd_nfc_felica
Selfd_result
Selfd_sensor_auto
Selfd_touch
Selfd_vibrator
aat_qr_display
aat_qr_generator
aat_service
adbd
appops
ddual_main
dmesg
e2fsck_static
etsui
headset_test
irda_test
lafd
lge_fota_launcher
lge_gota_launcher
make_ext4fs_static
mfts_service
minios3_ajnd
minios3_battery_thermal
minios3_batteryservice
minios3_bluetooth_stup
minios3_bootanimation
minios3_display
minios3_grouptest
minios3_hdmi
minios3_hdmi_audio
minios3_hdmi_test
minios3_input_stup
minios3_permissionservice
minios3_qrcode
minios3_ril
minios3_ril_test
minios3_schedulingservice
minios3_sensor_stup
minios3_starter
minios3_system_server
minios3_touchlocation_stup
minios3_vinput_stup
minios_cmd_service
minios_qrdisp
rcui_key_press
res
sdcard_test
setup_fs_static
sm_client
toolbox
ueventd
usbd
watchdogd
wifiminid
wireless_cmdmgrd
wmtest
xml_test
#adbd
#command | copy
#

So run the setenforce 0, then the setprop, and then open a separate command prompt for adb and hope It recognizes the device via adb devices?
[G4 Q&A, Help & Troubleshooting] nagalun:
Yup, I think it won't work if you execute it like this, /sbin/adbd, maybe has to be through setprop.

And, I think the send_command works with the program usbd BUT I'm not sure, after you do the setprops you can do something like this (if the send_command tool still works, maybe usb.config disables it):

ps -A | grep adb

To see if it is running.

If its running and it doesn't work for whatever reason you could try to kill the usbd program:

killall usbd
[G4 Q&A, Help & Troubleshooting] Norcalz71:
So run the selinux enforcing and set prop from send_command prompt, then should the ps -A |grep adb be run from send_command prompt or from adb? allall usbd run from send_command prompt?

Thanks again
[G4 Q&A, Help & Troubleshooting] nagalun:
Just run the setenforce 0 then all the setprops in order, check out the command "adb devices" and if it isn't there, do:

ps -A | grep adb

To see if it is running (if it shows up, it is). And only if it's not:

Instead of killall usbd you try this so it restarts adbd (maybe the shell is crap so it won't work):

( stop usbd && setprop sys.usb.config none && sleep 1 && setprop sys.usb.config adb & ) &
[G4 Q&A, Help & Troubleshooting] Norcalz71:
so the freezer trick is seeming to be less effective the more i try it unfortunately. A few tries ago I had the command prompt live for maybe 10-12 minutes, now it seems to last 1-2 and its tougher to actually get into DL mode (worried that all the freeze thaw is going to get condensation, even in a ziplock, in the phone and show "water" damage, hopefully not).

I can't tell if its the setprop commands or just the connection dropping out and re-looping again, but I'm about 90% sure that when I enter the last setprop command for sys.usb.config adb, i hear the USB connect/disconnect sound on my computer and it drops the send command connection (try ls after that and it doesnt do anything). However when I look at the phone screen, it is still at the "do not unplug your phone" screen and has not looped back to the boot screen. should that last setprop command drop the send command connection?
[G4 Q&A, Help & Troubleshooting] nagalun:
Yes! That's exactly what we want.

Did you check "adb devices" on your computer?

It should show up a device, then you can (hopefully) do "adb pull /data/media/0/DCIM/camera /Users/Norcalz71/Desktop/" (Change the last path to somewhere you can write to, surround it with quotes if it contains a space in it: "C:\Users\Example\Desktop\Camera Photos", make sure the second path has a slash on the end, I think the first path doesn't need one)

If you don't have the adb program of drivers, install this BEFORE trying again, to not lose time:

http://xdaforums.com/showthread.php?p=48915118

If it says permission denied or something similar run "adb root" then try again
[G4 Q&A, Help & Troubleshooting] Norcalz71:
So unfortunately when i run the setprop commands, it "dumps" the send command "#" shell I think (I hear the usb disconnect/connect sound on my computer and the little notification in the lower right of the taskbar says USB device unrecognized. I do have complete android SDK/fastboot/adb/etc all installed, but when I open a new prompt and run adb devices, it doesn't find anything. Also after running the setprop commands, the "#" shell for send_command is dead and no other commands respond (ls, mount, etc).

When I try

ps -A | grep adb

( stop usbd && setprop sys.usb.config none && sleep 1 && setprop sys.usb.config adb & ) &

it says it doesn't recognize those commands and/or doesn't do anything (tried them from the "#" after the setprop as well as from a fresh cmd prompt after trying adb devices).

Any holdout ideas? If I lightly understand whats going on I think those commands kill the send_command shell prompt and are supposed to start ADB connectivity, but for some reason or another its not finding my device via adb :/

Thanks again for the help.
[G4 Q&A, Help & Troubleshooting] nagalun:
Device unrecognized as in "malfunctioned"?

Did you try after running the setprop, disconnecting the usb cable and reconnecting?

And looking in the device manager to see if it's detected?
[G4 Q&A, Help & Troubleshooting] bender_007:
What android version was on it before bootloops? Tried to flash anything else since that?
[G4 Q&A, Help & Troubleshooting] Norcalz71:
Looks like the device is recognized in the device manager as there, but it doesnt "recognize" the device itself. tried unplugging and replugging, it pings that something connected but it doesnt know what it is.

still not sure where to run:

ps -A | grep adb

( stop usbd && setprop sys.usb.config none && sleep 1 && setprop sys.usb.config adb & ) &

since the setprop's kill my only active prompt. would I run those before doing the last setprop line instead? so do:

setenforce 0

setprop ro.secure 0

setprop ro.adb.secure 0

setprop ro.debuggable 1

ps -A | grep adb

( stop usbd && setprop sys.usb.config none && sleep 1 && setprop sys.usb.config adb & ) &

instead of ending with

setprop sys.usb.config adb

?

Super frustrating cause I can see that the data is there are alive, I just can't pull it off... :/

---------- Post added at 07:55 AM ---------- Previous post was at 07:52 AM ----------

lollipop, at&t h810 so I cant flash anything. Download mode is the only thing I can get into.
[G4 Q&A, Help & Troubleshooting] bender_007:
I´ll send you a pm in a minute, please try it
[G4 Q&A, Help & Troubleshooting] :
Just for an update gents, I ended up sending mine to a company called Gadget Lab, who have now recovered the data off my phone. Even if you can't get into download mode, a recovery company should be able to help as they can take the data straight from the memory chip.

Thanks for everyone that helped out, it's very appreciated.
[G4 Q&A, Help & Troubleshooting] nagalun:
Those last commands were only if it didn't kill the send_command prompt.

I'm out of ideas, sorry :(
[G4 Q&A, Help & Troubleshooting] Norcalz71:
no worries man, greatly appreciate the input. I'm trying to get at&t to extend my time to return the defective device so I can maybe get in touch with LG and see if they can get to it or maybe allow me to try reflowing the circuit board. Otherwise, c'est la vie.

thanks again mate.
[G4 Q&A, Help & Troubleshooting] testos83:
Thank you guys for all this. I am in the same situation as you. I really need to get my pictures back on my sd card. You seem to be very good in smartphones... Please let us know if you find a way to retreive these damn data... I am very interested to have a clear procedure to do it. Cheers.
[G4 Q&A, Help & Troubleshooting] rigocalin:
Pls see this: https://www.reddit.com/r/lgg4/comments/45gfg2/dae_g4_series_msm_big_core_disable_tool_guide/

aparently LG put forward a file that disables the 4 big cores allowing the device to boot as the power regulator for the big cores seems to be the problem.
[G4 Q&A, Help & Troubleshooting] Eltigre78232:
Do you take out the battery when you put it in the fridge? I had heard to put it in the freezer for 20 minutes. I tried it without a battery and after 15 to 20 minutes, I took it out, put a charged battery, an SD card in realy quick and attempted to boot it up. It didn't work. Did I do something wrong?
[G4 Q&A, Help & Troubleshooting] bender_007:
It disables 2 cores actually, not 4

Poslano sa mog LG-H815 koristeći Tapatalk
[G4 Q&A, Help & Troubleshooting] testos83130:
I am wrong somewhere...

Hello. How do you manage to run "ls" command ? When I do "ports.bat" it gives me

LGANDNETMDM0 COM6

LGANDNETDIAG1 COM5

When I Send_Command.exe COM6 and COM5, it works for both. But with COM6 when I "MKDIR" or "LS" or "MOUNT" it says nothing. Just go back to prompt #. On the other hand, COM5 gives me "FAIL" at each command, whatever it is.

Where am I wrong ?

Please help me, I would like to see my pictures on phone and copy on my SD.

Thanks
[G4 Q&A, Help & Troubleshooting] Norcalz71:
So far I have not been able to get this method to work. I can't find the mount location or maybe cannot access the SD card via send command. I can play around and see that my files are still there, but extracting them has been a no go.
[G4 Q&A, Help & Troubleshooting] blueeyeblue:
How can I write a file to the /system/ partition using the download mode?

I have tried remounting the system partition as rw and it does not work that simply.

I can write to the root - /temp/ eg.. but this folder gets deleted once rebooted.

Is there any folder to which I cant write except the data folder and which will stay after the reboot?

Is there any way to mount or remount system writable?

Thanks :)
[G4 Q&A, Help & Troubleshooting] Pyr0ball:
did anyone manage to figure out how to mount the sdcard in download mode?
[G4 Q&A, Help & Troubleshooting] wombat5:
Instructions for Verizon G4 (VS986)

I had to change 2 commands in order to mount the SD card on my Verizon LG G4.

The SD card was at /dev/block/mmcblk0p1 (not /dev/block/mmcblk1p1 like most other people encountered)

I also had to tell my phone how my SD card was formatted; Android's mount command wasn't smart enough to detect whether it was a Linux ("ext4") or Windows ("vfat" or "exfat")-formatted SD card.

Here's what worked for me:

# I reused the /sdcard mount point that already existed
# on my phone. You can probably leave out the remount
# command below:

mount -o rw,remount /

# ext4 worked for me because I reformatted my SD
# card on Linux...

mount -t ext4 /dev/block/mmcblk0p1 /sdcard

# ... but you probably want this instead:

mount -t vfat /dev/block/mmcblk0p1 /sdcard # or even ...
mount -t exfat /dev/block/mmcblk0p1 /sdcard

# Run the df command to see whether the mount worked
#
# (If it worked, "df" will tell you how much free space
# is available on each partition, including the /sdcard
# partition)

df

# Go ahead and copy. This took about 10 minutes for me

cp -R /data/media/0/DCIM /sdcard/Pictures

In order for my PC to see my Verizon G4 as a serial device, I had to run the LG_VZW_United_WHQL_v2.22.0.exe installer (MD5 sum e4fda49c791140d012f4d8857cb84249) and put the phone into Download Mode.

Other G4s will require the LG United Mobile installer available at http://xdaforums.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765

In order to get the phone to boot up into Download Mode, I first had to put it in the freezer for 5 minutes. (I also had to leave it in the freezer during the copy operation, else the phone would power off.)

Thanks everyone else for this useful thread, I wouldn't have been able to recover this phone without info from other G4 users.
[G4 Q&A, Help & Troubleshooting] ObiDanKenobi:
Do you have lolipop or marshmallow ? On marshmallow I could not mount the SD. It seems as the the filesystem is readonly.
[G4 Q&A, Help & Troubleshooting] wombat5:
If the root (/) filesystem is read-only, try the remount command again. If the SD card is read only, try a different filesystem type (see below for ext4 instructions).

I am stuck on Lollipop, but Android version shouldn't matter. Hardware version might.