Data Recovery without screen - Samsung Galaxy Nexus

Last night my phone fell out of my pocket while doing chest press with dumbbells without me noticing. Of course when I dropped the weights, they could not have landed anywhere else but on top of my phone.
So Ive contacted samsung and I'm ready to ship it over to them for repair, but I would like to gather the images and some unsaved numbers off of it if at all possible. Is there anyway to do this without the screen? There is a password to unlock the device and im not sure if I have USB debugging on or off. Im pretty sure it prompts me if I want to use it as a usb drive still. Any help is much appreciated.
THanks

Yes, there is a way. That is if you can access adb!

If you have USB debugging on, you can fire up the command line and use an "adb pull /sdcard/".

If you can't get a dB you could probably use an mhl adapter to see the screen.
Sent from my Galaxy Nexus using xda premium

You if you have an unlocked bootloader, you could always run a nandroid. Then you could pull it off your device with the previously mentioned command: adb pull /sdcard/

Could I unlock the bootloader using the galaxy nexus tool kit without the screen?

thechainrule said:
Could I unlock the bootloader using the galaxy nexus tool kit without the screen?
Click to expand...
Click to collapse
You could, but that would defeat the purpose, as unlocking the bootloader wipes the device...

I think I might be screwed then. When ever I used the tool kit it just hangs at " Waiting for Fastboot"

thechainrule said:
I think I might be screwed then. When ever I used the tool kit it just hangs at " Waiting for Fastboot"
Click to expand...
Click to collapse
What are you trying to do with the toolkit? (It's better to do things through the command prompt yourself. You will see where things go wrong, if they do.)
If it says "waiting for fastboot", I would guess that the toolkit is trying to do something in fastboot mode and either a) your device is not booted in fastboot mode, or b) your fastboot driver is not installed on your PC.

i was trying to do a media card recovery.

Data Recovery - Galaxy Nexus
Do you have a suggestion for how to image the drive? We are working with a Galaxy Nexus mobile phone that has an internal drive only (no removable sd card). When plugged with a USB cable, the phone is detected as either a Camera or Other Device even in USB debugging. I was able to pull the system files doing Fastboot pull/system but have not been able to pull the remaining partition. Do you have any tips for copying this image?

buzzbox said:
Do you have a suggestion for how to image the drive? We are working with a Galaxy Nexus mobile phone that has an internal drive only (no removable sd card). When plugged with a USB cable, the phone is detected as either a Camera or Other Device even in USB debugging. I was able to pull the system files doing Fastboot pull/system but have not been able to pull the remaining partition. Do you have any tips for copying this image?
Click to expand...
Click to collapse
Are you rooted? If so in terminal u can dd / each partition to the sdcard then pull them from the sdcard to pc
if you are rooted already you can get a little advernturse if you absolutely need the info from the device
install android sdk,
us cmd or termail enter shell
dd if=/dev/block/mmcblk1p11 of=/sdcard/boot.img
dd if=/dev/block/mmcblk1p12 of=/sdcard/recovery.img
dd if=/dev/block/mmcblk1p17 of=/sdcard/system.img
replace the mmcblXXX with that of your device ( google will help u find it)
the just pull the imgs from deivce
this may work below
/sdcard vfat /dev/block/sda1
/system ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system
/cache ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/cache
/data ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata
/misc emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/misc
/boot emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/boot
/recovery emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
/sbl emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/sbl
/xloader emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/xloader
/radio emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/radio
if you MUST see the screen u can always screencast it to your pc. or mhl adapter
althought screen cast is free and works with nexus ( refresh rate is really bad but will get the job done) also be creative, connect a mouse to your device and that plus screencast all good man,
androidscreencast/
happy hunting

runandhide05 said:
Are you rooted? If so in terminal u can dd / each partition to the sdcard then pull them from the sdcard to pc
if you are rooted already you can get a little advernturse if you absolutely need the info from the device
install android sdk,
us cmd or termail enter shell
dd if=/dev/block/mmcblk1p11 of=/sdcard/boot.img
dd if=/dev/block/mmcblk1p12 of=/sdcard/recovery.img
dd if=/dev/block/mmcblk1p17 of=/sdcard/system.img
replace the mmcblXXX with that of your device ( google will help u find it)
the just pull the imgs from deivce
this may work below
/sdcard vfat /dev/block/sda1
/system ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system
/cache ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/cache
/data ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata
/misc emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/misc
/boot emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/boot
/recovery emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
/sbl emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/sbl
/xloader emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/xloader
/radio emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/radio
if you MUST see the screen u can always screencast it to your pc. or mhl adapter
althought screen cast is free and works with nexus ( refresh rate is really bad but will get the job done) also be creative, connect a mouse to your device and that plus screencast all good man,
androidscreencast/
happy hunting
Click to expand...
Click to collapse
You cannot dd the userdata partition. You need to use adb to pull /data/

efrant said:
You cannot dd the userdata partition. You need to use adb to pull /data/
Click to expand...
Click to collapse
he didn't specify , and noticed it did not include user data as a dd option.
but your right, I should have mentioned that to him
Sent from my Galaxy Nexus using Tapatalk 2

runandhide05 said:
he didn't specify , and noticed it did not include user data as a dd option.
but your right, I should have mentioned that to him
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Sorry, I thought I saw userdata in your post above. Anyway, I would have figured that all he wanted would be the userdata partition, given that everything else is pretty much readily available, no?
This should get the entire userdata partition for him:
Code:
adb pull /data

efrant said:
Sorry, I thought I saw userdata in your post above. Anyway, I would have figured that all he wanted would be the userdata partition, given that everything else is pretty much readily available, no?
This should get the entire userdata partition for him:
Code:
adb pull /data
Click to expand...
Click to collapse
Ya that will get everything, but if he just wants the sdcard content he can do
Code:
adb pull /data/media
Sent from my Nexus 7 using Tapatalk 2

Related

[Q]How to fsck /data or /system?

Does anybody know of a way to fsck the system or data partitions? I've run into a few times where I had data errors on /data, and the only way I could think of to fix them was to do a backup and restore. I was worried about losing data during the backup process, as the filesystem was already questionable.
I have e2fsck in my rom, but I can't run it from a normal shell as the filesystems are already mounted. Is there a way to make a rom automatically check and repair the filesystems on boot, and if so, how can I control the options it passes to fsck? Are there other ways to get to an unmounted system or data partition? Does clockworkmod have any kind of shell or fsck utilities built in? Are there other recovery programs that may have something like that?
You should be able to boot into CWM, unmount the partitions, connect with adb and run it from there. At least if your version of CWM has fsck in it.
Sent from my SPH-D700 using xda premium
You should be able to do it while booted into recovery through ADB.
Boot to recovery
connect usb cable to PC
run `adb shell`
Code:
unmount /data
unmount /system
fsck /dev/block/stl9
fsck /dev/block/stl10
syntax for above commands needs to be checked.
toadlife said:
You should be able to do it while booted into recovery through ADB.
Boot to recovery
connect usb cable to PC
run `adb shell`
Code:
unmount /data
unmount /system
fsck /dev/block/stl9
fsck /dev/block/stl10
syntax for above commands needs to be checked.
Click to expand...
Click to collapse
Just tried this out myself. Here's the correct syntax for the fsck command:
Code:
e2fsck -fv /dev/block/stl10
EDIT: Forgot to mention also that unmount should actually be umount. Or you could just use the CWR menus to unmount partitions.
zman0900 said:
Just tried this out myself. Here's the correct syntax for the fsck command:
Code:
e2fsck -fv /dev/block/stl10
Click to expand...
Click to collapse
How bout mtd?
sent from my always aosp epic
Please consider posting questions in Q&A next time. Thank you.
Sorry for the "newbie spam"! But that worked perfectly - I didn't realize that adb shell worked when booted from cwm. That's exactly what I was looking for.
zman0900 said:
Just tried this out myself. Here's the correct syntax for the fsck command:
Code:
e2fsck -fv /dev/block/stl10
EDIT: Forgot to mention also that unmount should actually be umount. Or you could just use the CWR menus to unmount partitions.
Click to expand...
Click to collapse
Thanks for this, this is why i love xda!
I have e2fsck in my /bin
On a samsung galaxy s2 i9100
How do i identify my /system & /data blocks
I cant remember how to find out!
So mine would be
e2fsck -fv /dev/block/????
Thanks
Colliebudz said:
Thanks for this, this is why i love xda!
I have e2fsck in my /bin
On a samsung galaxy s2 i9100
How do i identify my /system & /data blocks
I cant remember how to find out!
So mine would be
e2fsck -fv /dev/block/????
Thanks
Click to expand...
Click to collapse
If you run mount with no arguments, it will show a list of mounted partitions like "xxx on /system".
Colliebudz said:
Thanks for this, this is why i love xda!
I have e2fsck in my /bin
On a samsung galaxy s2 i9100
How do i identify my /system & /data blocks
I cant remember how to find out!
So mine would be
e2fsck -fv /dev/block/????
Thanks
Click to expand...
Click to collapse
Better to do /dev/block/platform/(your processor)/by-name/xxxx. Less chance of error
Colliebudz said:
Thanks for this, this is why i love xda!
I have e2fsck in my /bin
On a samsung galaxy s2 i9100
How do i identify my /system & /data blocks
I cant remember how to find out!
So mine would be
e2fsck -fv /dev/block/????
Thanks
Click to expand...
Click to collapse
the easiest was to find what /system and /data mount points actually are
cat /etc/fstab
to see a list of mount points.
toadlife said:
You should be able to do it while booted into recovery through ADB.
Boot to recovery
connect usb cable to PC
run `adb shell`
Code:
unmount /data
unmount /system
fsck /dev/block/stl9
fsck /dev/block/stl10
syntax for above commands needs to be checked.
Click to expand...
Click to collapse
How do I get the Moto X in Recovery mode to accept the adb command?
Because when I put in Recovery (Android Robot lying down) mode, the command adb and fastboot are not recognized.
rod.gui said:
How do I get the Moto X in Recovery mode to accept the adb command?
Because when I put in Recovery (Android Robot lying down) mode, the command adb and fastboot are not recognized.
Click to expand...
Click to collapse
Flash a custom recovery first. (CWM/TWRP)
Sent from Motorola Photon Q 4G LTE @ CM11
My phone is Huawei G525. It doesn't have CWM or any custom stuff, just rooted.
My problem is that it reports an imagic flagged inode and it recommends to fsck the partition (/system). The logs are saved in sdcard folder.
I can use adb and fastboot, but fastboot shell doesn't work and /system is mounted when i can use adb.
Is there any solution for me to run e2fsck on /system partition?
Or is there the case to worry about that error? The phone works fine...no random reboots, no crashes, no force closes.
Another thing...I've tried to make a romdump and system archive is damaged. Cannot be opened even with 7-zip.
mandgeo said:
My phone is Huawei G525. It doesn't have CWM or any custom stuff, just rooted.
My problem is that it reports an imagic flagged inode and it recommends to fsck the partition (/system). The logs are saved in sdcard folder.
I can use adb and fastboot, but fastboot shell doesn't work and /system is mounted when i can use adb.
Is there any solution for me to run e2fsck on /system partition?
Or is there the case to worry about that error? The phone works fine...no random reboots, no crashes, no force closes.
Another thing...I've tried to make a romdump and system archive is damaged. Cannot be opened even with 7-zip.
Click to expand...
Click to collapse
G525 DOES have CWM recovery available, find and install one so that you can fsck from recovery using adb.
Sent from Google Nexus 4 @ CM11
AndyYan said:
G525 DOES have CWM recovery available, find and install one so that you can fsck from recovery using adb.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
As far as I understand from here... http://bbs.dospy.com/thread-16432606-1-823-1.html , the bootloader needs to be unlocked. I've submitted for an update code and i'll wait. The chinese guy talks about U8950, but there are five different types. I've selected the first one, U8950-1. Maybe i'm lucky.
I've also tried to boot directly into the recovery found here... http://www.needrom.com/mobile/huawei-g525-u00/ , but that command is not allowed, maybe because the bootloader is locked. That was the only recovery i found that seems to be in english.
I'll try the same procedure to boot into recovery (fastboot boot recovery.img) because i don't want to mess things more that they are. I didn't found any tutorial in english and google translate is confusing.
Thanks!
LE. Does anybody know if Huawei rewrites the custom recovery if it's not the stock one.
mandgeo said:
As far as I understand from here... http://bbs.dospy.com/thread-16432606-1-823-1.html , the bootloader needs to be unlocked. I've submitted for an update code and i'll wait. The chinese guy talks about U8950, but there are five different types. I've selected the first one, U8950-1. Maybe i'm lucky.
I've also tried to boot directly into the recovery found here... http://www.needrom.com/mobile/huawei-g525-u00/ , but that command is not allowed, maybe because the bootloader is locked. That was the only recovery i found that seems to be in english.
I'll try the same procedure to boot into recovery (fastboot boot recovery.img) because i don't want to mess things more that they are. I didn't found any tutorial in english and google translate is confusing.
Thanks!
LE. Does anybody know if Huawei rewrites the custom recovery if it's not the stock one.
Click to expand...
Click to collapse
Well, you know this forum is dedicated for discussion about Samsung Epic 4G, not Huawei G525... But to help you out I might be able to dig in a bit more later this week when I have time. I'm a Chinese myself and can (hopefully) understand these procedures.
Sent from Google Nexus 4 @ CM11
AndyYan said:
Well, you know this forum is dedicated for discussion about Samsung Epic 4G, not Huawei G525... But to help you out I might be able to dig in a bit more later this week when I have time. I'm a Chinese myself and can (hopefully) understand these procedures.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
My phone is a Note 2 LTE N7105 - I realise not the same as this thread, but this is the only thread I have found that is discussing this. My /data partition needs an fsck, however, while I can adb to the phone when it is booted, I can't when it is in recovery.
I have TWRP 2.7.1.0 installed, and everything else works fine. When the phone is booted, I get the GT-N7105 driver appearing in portable devices in device manager, but when recovery is booted, I just get t0lte in "other devices".
Seems like the Samsung USB driver only works when the phone is properly booted, and doesn't match when booted to recovery.
Any ideas how to work around this?
paulkoan said:
My phone is a Note 2 LTE N7105 - I realise not the same as this thread, but this is the only thread I have found that is discussing this. My /data partition needs an fsck, however, while I can adb to the phone when it is booted, I can't when it is in recovery.
I have TWRP 2.7.1.0 installed, and everything else works fine. When the phone is booted, I get the GT-N7105 driver appearing in portable devices in device manager, but when recovery is booted, I just get t0lte in "other devices".
Seems like the Samsung USB driver only works when the phone is properly booted, and doesn't match when booted to recovery.
Any ideas how to work around this?
Click to expand...
Click to collapse
Yes, the workaround is to not use stupid Windows.
Works fine on linux.
run terminal app:
su
touch /forcefsck
Then reboot. It might depend on your ROM, but give it a go.

[Q] M8 black screen, no recovery, no bootloader

Hi all
I had problems with installing 4.16.401.10 firmware but finally its installed. I tried than installing cm12 and ard 34.1 rom on it, but twrp recovery was giving me unable to mount data all the time.
I done a research and found out that i could type following commands and get it work.
cd /d c:\mini-sdk
adb push mkfs.ext4 /tmp
adb shell
chmod 777 /tmp/mkfs.ext4
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37
but none of it could work. I started the phone in recovery than typed command in twrp, but it freezed than shut down.
Since than i could not starte it up, its connected to my charger but no charging lights turning on, no vibration. When i connect the phone to pc, 14 windows pups up with format disk for 11 disks. There are two disk partition where includes files. i tried several times to get the in fastboot but no device shows up. Windroid tool kit can not see the device is on even partition disk showed up in C :
please help me
No solution ?
Gkhnnn said:
Hi all
I had problems with installing 4.16.401.10 firmware but finally its installed. I tried than installing cm12 and ard 34.1 rom on it, but twrp recovery was giving me unable to mount data all the time.
I done a research and found out that i could type following commands and get it work.
cd /d c:\mini-sdk
adb push mkfs.ext4 /tmp
adb shell
chmod 777 /tmp/mkfs.ext4
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37
but none of it could work. I started the phone in recovery than typed command in twrp, but it freezed than shut down.
Since than i could not starte it up, its connected to my charger but no charging lights turning on, no vibration. When i connect the phone to pc, 14 windows pups up with format disk for 11 disks. There are two disk partition where includes files. i tried several times to get the in fastboot but no device shows up. Windroid tool kit can not see the device is on even partition disk showed up in C :
please help me
Click to expand...
Click to collapse
What is the command you're trying to use? I've never seen it before so definitely not something I'd try and use...
Hi Eddy
Commands like getting the devices booted in bootloader, or trying to flash image or recovery, every communication wait for the device.
I hear bip sound when phone connected to pc, and i try also to shut it down , vol down+turning on and press power button for getting it in bootloader, but no difference
EddyOS said:
What is the command you're trying to use? I've never seen it before so definitely not something I'd try and use...
Click to expand...
Click to collapse
Gkhnnn said:
Commands like getting the devices booted in bootloader, or trying to flash image or recovery, every communication wait for the device.
Click to expand...
Click to collapse
No, the commands in your first post (adb, chmod, etc.). Where did you find those?
If no bootloader and the screen won't com on, you are mostly likely bricked. To be clear, does holding power and vol up reboot the phone?
i found those commands an a thread where the twrp recovery was giving error on unable to mount data. thats what i tried to fix.
Yes it does reboot the phone, if the phone is connected to a pc, if i power up, i hear bip sound and 14 disk partitions shows up, i can hold power and vol up than a bip sound again
redpoint73 said:
No, the commands in your first post (adb, chmod, etc.). Where did you find those?
If no bootloader and the screen won't com on, you are mostly likely bricked. To be clear, does holding power and vol up reboot the phone?
Click to expand...
Click to collapse
You shouldn't see any partitions when connected to your PC other than the MTP storage (and microSD card if you have one). It sounds like you've properly bricked the bootloader
Gkhnnn said:
i found those commands an a thread where the twrp recovery was giving error on unable to mount data. thats what i tried to fix.
Click to expand...
Click to collapse
There are easier and safer methods for fixing the "unable to mount data" problem. Are you sure the instructions were specific to the M8? This was an XDA thread? Can you link it?
Mucking about with mmc blocks in adb is pretty risky. I agree, you have probably bricked the phone, and may need JTAG.
You wiped wrong partition - /dev/block/mmcblk0p37 is meant for HTC One (M7)
On M8, the partition is /dev/block/mmcblk0p47
You have corrupted the "carrier" partition on M8
I believe you have probably hard-bricked your M8
error on unable to mount data can easily be fixed by installing TWRP, select wipe - advance - format data - yes ... but now seems to late for that
redpoint73 said:
There are easier and safer methods for fixing the "unable to mount data" problem. Are you sure the instructions were specific to the M8? This was an XDA thread? Can you link it?
Mucking about with mmc blocks in adb is pretty risky. I agree, you have probably bricked the phone, and may need JTAG.
Click to expand...
Click to collapse
I have a link on my pc but i dont think it was here. I send it soon
i am technician so soldering wires on it should not be a problem.
ckpv5 said:
You wiped wrong partition - /dev/block/mmcblk0p37 is meant for HTC One (M7)
On M8, the partition is /dev/block/mmcblk0p47
You have corrupted the "carrier" partition on M8
I believe you have probably hard-bricked your M8
error on unable to mount data can easily be fixed by installing TWRP, select wipe - advance - format data - yes ... but now seems to late for that
Click to expand...
Click to collapse
I tried several times to wipe the dalvik cache and so on but data could not be mounted again. I ended later installing cm12 and after installation it asked me for password which was weird. I understand it as the data was corrupted. But know when i connected it to my pc i hear usually device-connected-beep-sound and 14 dusk partition shows up and i see 5 of them has files inside. Maybe dropping files will solve issue
Just for your information ,the commands i typed was inside twrp and they never get succesfully. I typed a command than it freezed than i restarted the phone. Since its in black.
i plugged in charger and charging light lighted for 5 sec than dissappeared. But i know its a live and charging as its connecting to pc without problemz
the fix is located here http://android-revolution-hd.blogspot.ca/2013/10/fix-data-htc-one.html
Gkhnnn said:
the fix is located here http://android-revolution-hd.blogspot.ca/2013/10/fix-data-htc-one.html
Click to expand...
Click to collapse
The article was posted in 2013, before the M8 was even released. This article is for the M7. The partitioning is different (M7 versus M8), so as ckpv5 said, you modified the wrong partition and bricked the phone.
this is how it looks like when phone is conected to a pc
View attachment 3180499
how can i use "Jtag solution" ?
Gkhnnn said:
how can i use "Jtag solution" ?
Click to expand...
Click to collapse
You find a repair service that offers JTAG and pay them.
It requires specialized equipment, and specialized knowledge. As well as opening up the phone.
redpoint73 said:
You find a repair service that offers JTAG and pay them.
It requires specialized equipment, and specialized knowledge. As well as opening up the phone.
Click to expand...
Click to collapse
Opening the phone is the easy part. i am electronic technician and i have repaire hundreds of iphones+samsung ... I have also the right tools, but i need to know which box needs for m8 and where do i find the connection pins overview.
Gkhnnn said:
Opening the phone is the easy part. i am electronic technician and i have repaire hundreds of iphones+samsung ... I have also the right tools, but i need to know which box needs for m8 and where do i find the connection pins overview.
Click to expand...
Click to collapse
You negligently bricked the phone by applying a fix intended for a different phone. I'd be skeptical that JTAG is within your ability or knowledge. Even if it was, the answers to your questions should be easy to find by searching (I know its been discussed on this forum in depth).
m8
dont be sceptical. smile to world and let it smile back to you.
i searched on a few website but couldnt find a box supporting m8 and jtag pinout . thats why i asked.
its not that difficult to jtag, disassembly the phone, soldering tx rx and so on , load the files to the box and press start

Data Recovery via Download Mode

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.

Bricked AFTV1 - Is repair possible with hardware mod?

I feel like a bonehead cuz I bricked my FireTV by getting ahead of myself. This FTV came shipped with 51.1.3.0 and I have always had updates blocked in my router. I purchased a SD-card adapter and was able to gain root by injecting su into /system/xbin, Installed busybox, and all that fun stuff. Everything was going along just fine, until i tried to install RBox's boot menu/Recovery without fully understanding everything. Following a guide, I ran the full bootloader unlock script and it seemed to complete fine and FTV would still boot normally with root access. What I did next is the following, trying to install recovery I download the bootmenu.img file, uploaded it to my sd card and issued the following commands:
mount -o remount,rw /system
mkdir /system/boot
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
mount -o remount,ro /system
dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
exit
exit
adb reboot​My FTV restarted and has been stuck at the FireTV Logo every since. Not exactly sure where I went wrong. Did I have to downgrade before trying to install the boot menu? I did to the checksum test on the file before using it and it matched. Anyways, I tried factory reseting by holding the back/right remote control keys....no joy, tried the alt+prtsc+i keyboard procedure....nothing, tried a fastboot cable recovery.......got the drivers installed, firetv listed in devices using kindle usb driver, but although fastboot would connect and communicate to the FTV, it wouldn't respond to any fastboot commands.
I have the ability to gain direct access to the FTV's file system, but although my electronic skills are superb, my linux/android skills are quite lacking. When I disable the CPU and connect the flash to my Ubuntu 15 VMWare system via usb, I am able to mount up 6 linux partitions from the FTV. I explored around them, but don't want to go plowing through anything like a bull in a china shop until I have a direction to take from someone who actually knows what they are doing to get my beloved Firetv booting again. Any suggestions would be GREATLY appreciated. Thanks in advance.
Plug in the fire TV with a USB to USB to your PC. If the boot loader is fully unlocked you should be able to fastboot boot clockwork recovery and flash the rom that doesn't require boot menu.
{ParanoiA} said:
Plug in the fire TV with a USB to USB to your PC. If the boot loader is fully unlocked you should be able to fastboot boot clockwork recovery and flash the rom that doesn't require boot menu.
Click to expand...
Click to collapse
I mentioned in my OP that I have already tried this and although the fastboot drivers install correctly, the "fastboot devices" command returns nothing, and the "fastboot reboot recovery" command waits for about 10 seconds, then returns "no reply received by device". So this is a dead end and I guess the problem lies in the fact that my bootloader failed to unlock. I was also guessing that the solution would be to put the stock bootloader back onto the FireTV, but cannot figure out where it goes on the fire's 6 mounted partitions in linux using the soldered-in USB flash device. I can access the /system directory, but cannot locate the /dev/block/platform/msm_sdcc.1/by-name/boot folder where the bootmenu.img file was written to which caused the bricking. Any other ideas?
No I'm not that familiar with the partitions. @rbox would probably be the best one to answer this
Adaptel said:
I mentioned in my OP that I have already tried this and although the fastboot drivers install correctly, the "fastboot devices" command returns nothing, and the "fastboot reboot recovery" command waits for about 10 seconds, then returns "no reply received by device". So this is a dead end and I guess the problem lies in the fact that my bootloader failed to unlock. I was also guessing that the solution would be to put the stock bootloader back onto the FireTV, but cannot figure out where it goes on the fire's 6 mounted partitions in linux using the soldered-in USB flash device. I can access the /system directory, but cannot locate the /dev/block/platform/msm_sdcc.1/by-name/boot folder where the bootmenu.img file was written to which caused the bricking. Any other ideas?
Click to expand...
Click to collapse
boot is partition 10. You should be able to use gdisk on the mmc device to see the partition table with the partition labels.
rbox said:
boot is partition 10. You should be able to use gdisk on the mmc device to see the partition table with the partition labels.
Click to expand...
Click to collapse
Thank you for chiming in Rbox. I am in awe of your amazing work with FireTV and keep up the spectacular work!!!
Anyways, I wanted to attach a screenshot of my dead fireTV1's MMC partition layout, but becasue I am new here, the forum won't let me add a screenshot jpg. I used gparted because as I said before, I am a linux novice and couldn't get gdisk to show me what I wanted to. Partition 10 is labeled "boot", is 10MB in size, and shows up as having a file system type "Unknown". Should I dd the stock recovery file to this partition, or what do I need to do to undo these commands which bricked my device. (Which I am pretty sure due to the fact that I didn't get the bootloader unlocked correctly).
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
mount -o remount,ro /system
dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/boot​Thank you so much for your help in advance!
Adaptel said:
Thank you for chiming in Rbox. I am in awe of your amazing work with FireTV and keep up the spectacular work!!!
Anyways, I wanted to attach a screenshot of my dead fireTV1's MMC partition layout, but becasue I am new here, the forum won't let me add a screenshot jpg. I used gparted because as I said before, I am a linux novice and couldn't get gdisk to show me what I wanted to. Partition 10 is labeled "boot", is 10MB in size, and shows up as having a file system type "Unknown". Should I dd the stock recovery file to this partition, or what do I need to do to undo these commands which bricked my device. (Which I am pretty sure due to the fact that I didn't get the bootloader unlocked correctly).
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
mount -o remount,ro /system
dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/boot​Thank you so much for your help in advance!
Click to expand...
Click to collapse
You can just dd that boot.img in /system/boot back to the partition to undo what you did.
rbox said:
You can just dd that boot.img in /system/boot back to the partition to undo what you did.
Click to expand...
Click to collapse
That did the trick & my FTV is now booting and still has root and all my stuff just where I left it......you are the best!
Should I not even try to install boot menu/recovery? I thought i was on 51.1.3.0, but I just now checked and I am actually on 51.1.4.0. I ran the full bootloader unlock script right before I reflashed the recovery partition which bricked my fire. Is it because 51.1.40 is the version-of-no-return for installing recovery, should I have ran the partial bootloader unlock, or something else? Any advice? I am happy to have my Fire TV working again, but half the fun of this is learning and understanding what goes on inside and how it works. THANKS AGAIN!!!!!
Adaptel said:
That did the trick & my FTV is now booting and still has root and all my stuff just where I left it......you are the best!
Should I not even try to install boot menu/recovery? I thought i was on 51.1.3.0, but I just now checked and I am actually on 51.1.4.0. I ran the full bootloader unlock script right before I reflashed the recovery partition which bricked my fire. Is it because 51.1.40 is the version-of-no-return for installing recovery, should I have ran the partial bootloader unlock, or something else? Any advice? I am happy to have my Fire TV working again, but half the fun of this is learning and understanding what goes on inside and how it works. THANKS AGAIN!!!!!
Click to expand...
Click to collapse
You can't unlock that version. You should block updates and wait until I release TWRP and prerooted fireos5 roms.
hey rbox, quick question: once you release the prerooted fireos5 is it possible to dd recovey.img through hardware mmc to get the unlocked bootloader?
my firetv got bricked using supersu me and now i wonder what the best way is to bring it back alive..
Adaptel said:
That did the trick & my FTV is now booting and still has root and all my stuff just where I left it......you are the best!
Click to expand...
Click to collapse
Can you tell me the command wich give you finally the success ?
Another question by me is how to create a system.img from the bin files.
I know that there is folder in the bin-zip but how to create from them a system.img or how to create a valid stuck-recovery.img
Greetings by Idijt
I_did_it_just_tmrrow said:
Can you tell me the command wich give you finally the success ?
Click to expand...
Click to collapse
Certainly. The process I went through (using Ubuntu Linux 15 with Fire's eMMC chip connected via USB via hardware mod) is as follows (keep in mind I'm not a Linux genius but know enough to get by:
When eMMC is successfully connected, Ubuntu auto-mounted 6 partitions with partition names/ids that consisted of a long string of hex digits.
By looking around these ext4 partitions, I noticed that one of them was obviously the entire contents of the Fire's /system folder.
I navigated to /system/boot/ and saw that the boot.img file was in there. I right clicked on it, selected Properties to gain a full path of the files location and copied it
I installed and ran gparted partition editor to view the partition layout of the eMMC. There are a total of 20 partitions on fire's disk, (/dev/sdb1 through /dev/sdb20 on my system) but most of them aren't mounted because they use a non-linux standard file format).and as Rbox said. Partition 10 was 10.00MB in size, type=unknown, name=boot, and was located at /dev/sdb10 (on my system).
Now all I had to do was issue this command: sudo dd if=/<long string of hex digits described abouve>/system/boot/boot.img of=/dev/sdb10
Remove 4 wires soldered to Firetv, Solder CPU oscillator pads together, Reboot and Cheer​The fire tv rebooted fine and everything was good....but I do have an update with even more good news. I felt emboldened having access to my MMC ao since my software was on version 51.1.40, I was able to then follow the guide (EXACTLY) at http://solderwiresandplastic.com/20...the-amazon-firetv-to-achieve-root-privileges/​starting at "Step 2", and was able to successfully install the latest clockworkmod recovery, RBox's AWESOME boot menu, and install RBox's latest prerooted rom. This worked because I was on version 51.1.4.0 and the bootloader eFuse freeze occurred on 51.1.4.1 (so don't even think of trying the steps in this link if your box has 51.1.4.1 or higher on it. Hope this makes sense and helps in some way.
mrchrister said:
hey rbox, quick question: once you release the prerooted fireos5 is it possible to dd recovey.img through hardware mmc to get the unlocked bootloader?
my firetv got bricked using supersu me and now i wonder what the best way is to bring it back alive..
Click to expand...
Click to collapse
No. To unlock your bootloader you need an old version of the aboot partition. But if you're on the latest software, you will brick if you attempt to flash that old version.
thanks, good to know!
Sent from my iPhone using Tapatalk
Hello. I have a bricked fire tv because of supersu me. I've extracted a system.img from a working one via adb. My problem is, that i don't know how to install this on my bricked one with hardware mod (card reader). Any advice?
where did you find the 5.0.5 image i need it also , mines bricked also from super sume just waiting for EEMC chip to come in..
geist_patrick said:
Hello. I have a bricked fire tv because of supersu me. I've extracted a system.img from a working one via adb. My problem is, that i don't know how to install this on my bricked one with hardware mod (card reader). Any advice?
Click to expand...
Click to collapse
---------- Post added at 01:21 PM ---------- Previous post was at 01:18 PM ----------
[/COLOR]
geist_patrick said:
Hello. I have a bricked fire tv because of supersu me. I've extracted a system.img from a working one via adb. My problem is, that i don't know how to install this on my bricked one with hardware mod (card reader). Any advice?
Click to expand...
Click to collapse
think you could send me your img file thanks. as im on 5.0.5 firmware bricked also. thanks
Rootet system.img
https://drive.google.com/open?id=0B8P7DODeSgf8cmk5UUx4UUFXYkk

forget encryption key reset - format /sdcard /data

Few days ago I decide to encrypt my phone. And as I want to install nightly so I rebooted and it want the password but then I discover I can't remember I tried adb shell but it says that I do not have permission (sudo does not works). So what should I basically do now? use terminal/ adb shell in TWRP and format /data and /sdcard with dd, or what is way to do it correctly? I come across to this https://android.stackexchange.com/questions/33398/cannot-factory-reset-after-encrypting#48264 but it's 4 years old I do not get completely "Substitute /dev/block/mmcblk0p12 and ext4 according to the recovery filesystem table (for /data). " part. I've LG G2.
Thanks Rob
roberto32 said:
Few days ago I decide to encrypt my phone. And as I want to install nightly so I rebooted and it want the password but then I discover I can't remember I tried adb shell but it says that I do not have permission (sudo does not works). So what should I basically do now? use terminal/ adb shell in TWRP and format /data and /sdcard with dd, or what is way to do it correctly? I come across to this https://android.stackexchange.com/questions/33398/cannot-factory-reset-after-encrypting#48264 but it's 4 years old I do not get completely "Substitute /dev/block/mmcblk0p12 and ext4 according to the recovery filesystem table (for /data). " part. I've LG G2.
Thanks Rob
Click to expand...
Click to collapse
I'm not an expert on this but since every device's partition map is unique, dd should be given the specific partition offsets and filesystem type for your device when performing any destructive operations or else you run the risk of bricking your device when using dd to write to your internal flash. That's what the "substitute" part is about because it varies from device-to-device.
I would suggest checking on one of LG G2 forums here, someone there can probably give you the proper parameters. (Here is the general LG G2 section, there are also some others eg for particular carriers like T-Mobile US)
I've already asked there but no answer. I'll rahter specifically ask about how to find partition table map. Thanks anyway

Categories

Resources