Hi there,
The device is rooted.
I ran (on Windows)
Code:
adb shell "su -c cat /dev/block/mmcblk0p57” > 57.img
adb shell "su -c cat /dev/block/mmcblk0p57” > 57.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The two commands above produced respectively two files of different size, while the image file was created from the same userdata partition:
57.img 1,194,611 kb;
57-1.img 283,114 kb.
Normally, the file pulled should be like this (pulled on adb Macintosh):
How could this result be produced?
Thanks.
PS: mmcblk0p57 is the userdata partition.
What is this mmcblk0p57 partition on your device used for?
Maybe it's supposed to be that way because it's a dynamic volume.
ze7zez said:
What is this mmcblk0p57 partition on your device used for?
Maybe it's supposed to be that way because it's a dynamic volume.
Click to expand...
Click to collapse
mmcblk0p57 is userdata partition.
wenyendev said:
mmcblk0p57 is userdata partition.
Click to expand...
Click to collapse
Small size for the main userdata partition, so it is probably an auxiliary partition. Check the copy partition, which should definitely be a fixed size.
ze7zez said:
Small size for the main userdata partition, so it is probably an auxiliary partition. Check the copy partition, which should definitely be a fixed size.
Click to expand...
Click to collapse
Thanks for your reply.
But previously, adb pull was able to pull out a full userdata partition of about 53 GB out of the device...
It was on adb Macintosh.
the different size result from interrupted connection. that's why checksum is recommended. full copy of 53gb will take hours. that's why gzip compression is recommended (decrypted only).
https://forum.xda-developers.com/t/...lock-bootdevice-by-name.4535851/post-87936341
please stop posting multiple threads.
please start reading answers in old threads.
aIecxs said:
the different size result from interrupted connection. that's why checksum is recommended. full copy of 53gb will take hours. that's why gzip compression is recommended (decrypted only).
https://forum.xda-developers.com/t/...lock-bootdevice-by-name.4535851/post-87936341
please stop posting multiple threads.
please start reading answers in old threads.
Click to expand...
Click to collapse
Thanks.
But the later part of your answer "
that's why gzip compression is recommended (decrypted only).
https://forum.xda-developers.com/t/...lock-bootdevice-by-name.4535851/post-87936341
please stop posting multiple threads.
please start reading answers in old threads." was simply irrelevant to the question.
Thanks for being relevant.
Related
Good Morning,
I like many unfortunate people restored my Samsung Galaxy S3 to factory settings thinking that it had a micro sd card, i was so wrong and to think i lost all my pictures, contacts etc. I was told by a good friend that it was possible to retrieve this data and to read the help guides in XDA Developers Forum.
Well, i was reading and learning how to do this by the help of Wartickler Post. I managed to install all the files, root my s3 and made sure my phone connected in ADB mode.
Now, On the second part of the tutorial is where i am getting problems, My mobile is connected in USB Debugging Mode, ADB Mode. My mobile has Busybox Installed via playstore, the ver is 1.20.2 and the install is /system/bin.
I open Crywin Terminal, enter the code "adb forward tcp:5555 tcp:5555", then "adb shell", i also enter "SU" for superuser then i am prompted with 1|[email protected]:/ #. I then enter the command "/system/bin/busybox nc -1 -p 5555 -e /system/bin/busybox dd if=/dev/block/mmcblk0p12" i get the following error, nc: invalid option --1
Please see picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Link to picture if not working, sorry Crywin Terminal
Can someone please tell me if i have went wrong anywhere as i feel i am close to completing it
Much Appreciated
Stuart Grahame
You post a link to instructions for a different device, which probably uses a different partition structure hence why the failure.
I'd guess you'll need to work out which partition holds the internal storage on the s3, not sure how successful any data recovery would be but I wish you good luck.
Just read general > sticky roll-up thread > s3 storage data recovery.
Everything you need to know is there. No need for duplicate thread
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
See ^^^^Post Above^^^^
Thread Closed
Hello everyone...
I find the phone with the non-working tuch ..
From the recoveri mode I managed to make a complete backup of the phone on sd and generated these 3 files:
userdata_20160101_000035.backup
userdata_20160101_000035.backup1
userdata_20160101_000035.backup2
is there a possibility to extract the content ???
I would be interested in contacts.
I state the phone is a Majestic
Thank you.
recovering contacts is not easy. you need SQLite Forensic Explorer to view the database file. the database is separated in many different tables, each table has a column "raw_contact_id" which contain always the unique id-no of contacts (one table contains phone nos, another table contains names, etc... you must query tables by id).
once you have extracted the backup, the file "contacts.db" is located "/data/data/com.android.providers.contacts/databases/"
from the backup I made, how do I extract the contacts.db file ??
remove the checksum(s) and merge the files. you need linux
don't be scared, i will explain you step by step. first step: do you have linux? if yes, press CTRL + ALT + T this is the terminal where you can do it. if no, please download unetbootin and prepare a bootable usb stick. you can run ubuntu on your pc without installing. don't hesitate to ask if you need help regarding unetbootin
scacco728 said:
finally I was able to understand something of the terminal in place ..
I move to the folder where the files are, I open the terminal I enter the commands and I generate this error .. why do you think ???
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
"dd" does not accept wildcards. press <TAB> instead of * for word completion. you must type the full file name. remove the stars in this example code.
edit: i will answer in this thread, because this are linux basics. so lets open a "beginner" thread here, and leave the other thread open for more advanced questions. finally, your goal is to extract contacts, what we should not discuss in main thread
4 this kind of guys x)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
Warning:
Your device will never boot :D
Does this enough?
Ok jk but consider its possible
So don't blame me,
not responsible for anything
Trick:
Read 2nd Post First
(if u think necessary)(i would)
Why ?? :
Cuz u want to increase/decrease size on internal storage/internal sd card/nand/emmc.
So u can play Asphalt 8:AirBorne
I.e. default internal storage will increase from 4.6 GB to 5.5 GB
Sounds cool ?
Go ahead
Tools required:
0. Nandorid Backup ,
back up everything every way you can/know
1. Rooted Phone
2. Custom Recovery with ADB Sideload
3. Minimal ADB and Fastboot Tools(for Computer)
4 parted utilities.zip (download from below)
5. Computer should recognise device for that install necessary drive
6. brain, commen sense, patients,calm etc.
---> PROCEDURE/STEPS
(will add screen shot, Rewrite again )
1.
Extract 'parted' from zip copy to "/system/bin"
(if can't Open Es FILE EXPLORER app> find & tape Root explorer option>mount r/w option> mount system to r/w (read/write allow)
2.
Put phone in TWRP Recovery
3.
Connect to computer
On command line interface
(Windows>Run>CMD>enter)
#commands:
adb shell
su
parted /dev/block/mmcblk0
you will see the following screen
4.
On5 re-partition
Parted command
Rm mmcblk20,21,22,23
Name ,21,22,23
Re Size command
Mkpart primary start Size end Size
Format using
Mke4fs.
Restore twrp backup
Reboot to recovery
Hello,
I am trying create a disk image on my windows PC of the data on my phone to see if I can recover some lost files.
On my PC, can I just use:
~# adb shell dd if=/dev/block/datapartition > data.img
or just
~# adb pull /dev/block/datapartition data.img
or do I need to use netcat and busybox to send and receive the files?
Do all these methods work exactly the same?
Thanks
just type the following on ADB
Code:
adb devices
Code:
adb shell
Code:
ls -la /dev/block/bootdevice/by-name
^ this would list all partion of your devices it should look like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
based on the screenshot above we know boot.img is mmcblk0p59
now we just do dd command
Code:
dd if=/dev/block/mmcblk0p59 of=/sdcard/boot.img
Congratulation you now have boot.img backup of your device :fingers-crossed::fingers-crossed:
Thanks, but will that output to the phones sd card? I would like to output the img to my pc
kaotik123 said:
Thanks, but will that output to the phones sd card? I would like to output the img to my pc
Click to expand...
Click to collapse
you are most likely do the dd command from your pc just copy the img file from your device to your pc
also on my device even it say " of=/sdcard/ " files are being drop on Internal Memory ...
ineedroot69 said:
you are most likely do the dd command from your pc just copy the img file from your device to your pc
also on my device even it say " of=/sdcard/ " files are being drop on Internal Memory ...
Click to expand...
Click to collapse
Yeah I wanted to avoid writing to the phone's memory becuase I was trying to recover lost files from it. Plus the image would be too big to fit on the remaining memory anyway. Thanks for your help but I used netcat and busybox and successfully copied the image directly to my PC. Followed the tutorial here for anyone else reading this and was quite easy: https://dfir.science/2017/04/Imaging-Android-with-root-netcat-and-dd.html (second video for windows pc).
Hi there.
I have a Galaxy A50 (SM-A505FN) with 128GB. I rooted it with magisk (original firmware from sammobile (link below), modified on unrooted phone with magisk manager, flashed through download mode and odin).
The issue is that the phone now says it only has 16GB of storage.
Conneced to my PC it also only finds 16GB of internal storage.
I added a picture of what the terminal says the partitions are.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I read about correcting partitions with twrp but since i dont have that i want to ask if there is another way to fix this.
Thanks!
www sammobile com/samsung/galaxy-a50/firmware/SM-A505FN/DBT/download/A505FNXXU3ASL6/309345/
i can only see 10 GB on your screenshot. check one of the following
Code:
cat /proc/mtd
cat /proc/partitions
cat /proc/dumchar_info
you can download parted binary and check
Code:
parted /dev/block/sda print
note that the 6263-3234 block in the first screenshot is the sd card. i dont have it encrypted so im wondering why it seems to be mirrored in the /mnt/secure/asec block. i did however click the 'copy files from sd card' when it popped up i believe. but even if that did something, it could only block 64 of my 128 gb.
displaying partitions worked, heres the result:
i see that sda shows the 128gb capacity and sda32 seems to be whats is usable for the phone after taking out all the neccessary partitions.
unfortunately i don't know how knox works, all i can see is /data is not mounted, maybe knox prevents
try to uninstall KNOX with su -c pm disable com.sec.knox.seandroid or something
@mirfatif same problem here, must be something new. i have never seen before. maybe permission problem with magisk or some sort of disk quota
data is mounted /sbin/.magisk/mirror/data
(or /sbin/.magisk/block/data)
aIecxs said:
@mirfatif same problem here, must be something new. i have never seen before. maybe permission problem with magisk or some sort of disk quota
data is mounted /sbin/.magisk/mirror/data
(or /sbin/.magisk/block/data)
Click to expand...
Click to collapse
No idea. Can't conclude anything unless OP performs some troubleshooting steps. Whatever the case is, "/data" must be a mount point. May be something to do with SELinux, or mount namesapce, or new Magisk changes for Android 10. I'm using old Magisk release on Android 9. So may be missing something new.