STRANGE BUT, when I recover photos from "userdata" partition with various recovery apps / PC software I get bunch of images but not one from camera.
If I edited/cropped or sent to email which caued photo to be saved by some other app it will be recovered. How is this so ???
-------------------------------------------------
Details : OnePlus One bought with CM11, OTA upgrade to CM12.
One day GSM radio stopped working. Its not SIM card isssue, or network coverage.
Tried varius stuff I could find, in desperation decided to make factory reset to see if it is helping, if not then flash OxygenOS and see if it is working.
So my **** up is that I remembered to backup photos after unlock bootloader which wiped the phone.
I tried various apps for recovery of photos directly on phone, then I tried Dr. Fone and EaseUS android recovery (only two that I found that can do recovery of lolipop OS with only Internal Storage), they require rooted phone and ADB interface, so I did everithing.
At the end I made DD raw copy of "userdata" partition and scanned on PC with Recuva, PhotoRec and at leaset thre others (ext4 specific)-
Every time I recovered more or less the same images and I get bunch of images but not one from camera.
What is s special about these files ????
They are just JPEGs on that same partition where recovery software found other files/images.
Duplicate.
http://forum.xda-developers.com/oneplus-one/help/oneplus-one-photo-recovery-question-t3180899
Related
STRANGE BUT, when I recover photos from "userdata" partition with various recovery apps / PC software I get bunch of images but not one from camera.
If I edited/cropped or sent to email which caued photo to be saved by some other app it will be recovered. How is this so ???
-------------------------------------------------
Details : OnePlus One bought with CM11, OTA upgrade to CM12.
One day GSM radio stopped working. Its not SIM card isssue, or network coverage.
Tried varius stuff I could find, in desperation decided to make factory reset to see if it is helping, if not then flash OxygenOS and see if it is working.
So my **** up is that I remembered to backup photos after unlock bootloader which wiped the phone.
I tried various apps for recovery of photos directly on phone, then I tried Dr. Fone and EaseUS android recovery (only two that I found that can do recovery of lolipop OS with only Internal Storage), they require rooted phone and ADB interface, so I did everithing.
At the end I made DD raw copy of "userdata" partition and scanned on PC with Recuva, PhotoRec and at leaset thre others (ext4 specific)-
Every time I recovered more or less the same images and I get bunch of images but not one from camera.
What is s special about these files ????
They are just JPEGs on that same partition where recovery software found other files/images.
Hi, i have a problem with lost data and I'm trying to make a raw copy.... How did you do that?
Thanks
Enviado desde mi A0001 mediante Tapatalk
My new xiaomi mi4 won't boot after 2/3 months of use. I don't know what happend. I tried connecting it to usb, the phone mounts all partitions and I can access them.
I remember when I accidentally formated all my partitions from my other mi3 and it happanned the same, I could see the partitions. I just used miflash and it worked again.
Before I can flash a new rom I need to backup my images, etc but I can't find them anywhere! I attached an image from the data partition folder.
Where is the folder that most roms show when connected via mtp? I can't find it anywhere, neither my images, videos, etc folders (where my personal data is).
Thanks!
The question:
Is it actually possible recovering your data on an android device after flashing it with a Stock ROM?
The reason:
The whole story is about to be told, and you know that you don't have to read it.
I went through a few days of hell (and apparently it's a waste of time) in learning how to get back my photos.
1. Lenovo Vibe P1 (16GB internal memory) with 64GB SD card, no root.
A lot of space and a lot of photos. "Job" Gallery, Personal Gallery, "Fun" Gallery.
I decided to keep my photos organized and moved my "Job" Gallery to my SD card, as well as all other files, that I wouldn't miss much if they would get lost, as it often happens with SD cards, I believe.
"Job" Gallery is what I sometimes have to show to people by actually giving them my phone.
In order to keep my Personal Gallery away from anyone I simply moved it into an internal memory Folder with a "." in it's name (Hidden or System Folder is what Android calls them).
2. Personal photos lost.
One of the popular "Cleaning\Boosting" Apps or Android itself (not sure by now) decides to give me an advice to wipe my "Photos Cache", which is what I did, sadly.
It turned out that it deleted my personal photos from the Hidden Folder.
3. Failed Recovery.
Downloading "Data Recovery" apps did not help much since most of them wanted a Rooted device.
And those that could work without Root some why just wouldn't locate anything from my Hidden Folder.
4. Failed Rooting = dead SDcard.
I already knew about how hard it is to root my device, not to mention that going Android6.0 made it even harder, so I never wanted to take that risk.
Now I sort of a had to try, since most of the data I really cared about was lost.
Downloading rooting apps and trying them out somehow killed my SDcard.
5. Failed SDcard Recovery = dead CardReader, dying HardDrive.
While using some Data Recovery software on my PC with SDcard plugged via CardReader, something apparently went wrong and my HardDrive started having one of those dying sounds.
It still worked though, so I could spend some time browsing the recovered SDcard data.
Sadly, those files where unreadable, probably because the recovery software was trial, so it made all of them "Unreadable Before You Pay", hard to tell by now.
I decided to try another Recovery Tool, ignoring the HardDrive issue for now, but my CardReader or the SDcard or both appeared to be dead.
6. Bricking the Vibe.
After spending some time doing backups of my dying HardDrive data, I returned to Rooting my smartphone, but by "manual" methods this time.
Trying all of those scary weird methods while actually learning all the stuff about "flashing" led me into bricking my device.
7. Failed Rooted Recovery.
Somehow, by following few guides, I finally managed to do everything correct (I hope).
I mean, unlocking bootloader by fastboot, gaining temporary root by ADB, flashing TWRP recovery and Stock ROM by QFIL, installing SuperSU, and actually rooting the device.
Right after, I downloaded a bunch of recovery apps to try again, but all of the photos and pictures, found by scanning, were useless.
Even those results before rooting were much better.
8. Failed RAW Recovery.
Surfing different forums, led me to a guide about using PC recovery tools on an Android RAW image.
While surfing, I have already tried about five PC-Android recovery tools and they didn't help much, but I decided to try it anyway.
By using BusyBox, Cygwin, NetCat, ADB, VhdxTool, I made a RAW image of my internal memory partition, converted it into a VHD and mounted it for scanning.
After using about 25-30 recovery tools I did not find any of those desired lost photos.
Scanning results on jpegs are pretty much the same for each tool.
Thank you for reading if you decided to do so anyway.
I also found others who did try to recover their precious data, like I did (after flashing and going through all the problems with rooting and getting a RAW file).
It seems like they all failed as well, so the question is - is it actually possible?
I know it's much easier with an HDD, since I know that those mansions usually keep ghosts for years, while Android totally exhausted and after all, killed me.
I really need help with this, since I see no more ways to try. If you have any advice, please share.
P.S. I'm sorry for my english, not native.
XDA Visitor said:
The question:
Is it actually possible recovering your data on an android device after flashing it with a Stock ROM?
The reason:
The whole story is about to be told, and you know that you don't have to read it.
I went through a few days of hell (and apparently it's a waste of time) in learning how to get back my photos.
1. Lenovo Vibe P1 (16GB internal memory) with 64GB SD card, no root.
A lot of space and a lot of photos. "Job" Gallery, Personal Gallery, "Fun" Gallery.
I decided to keep my photos organized and moved my "Job" Gallery to my SD card, as well as all other files, that I wouldn't miss much if they would get lost, as it often happens with SD cards, I believe.
"Job" Gallery is what I sometimes have to show to people by actually giving them my phone.
In order to keep my Personal Gallery away from anyone I simply moved it into an internal memory Folder with a "." in it's name (Hidden or System Folder is what Android calls them).
2. Personal photos lost.
One of the popular "Cleaning\Boosting" Apps or Android itself (not sure by now) decides to give me an advice to wipe my "Photos Cache", which is what I did, sadly.
It turned out that it deleted my personal photos from the Hidden Folder.
3. Failed Recovery.
Downloading "Data Recovery" apps did not help much since most of them wanted a Rooted device.
And those that could work without Root some why just wouldn't locate anything from my Hidden Folder.
4. Failed Rooting = dead SDcard.
I already knew about how hard it is to root my device, not to mention that going Android6.0 made it even harder, so I never wanted to take that risk.
Now I sort of a had to try, since most of the data I really cared about was lost.
Downloading rooting apps and trying them out somehow killed my SDcard.
5. Failed SDcard Recovery = dead CardReader, dying HardDrive.
While using some Data Recovery software on my PC with SDcard plugged via CardReader, something apparently went wrong and my HardDrive started having one of those dying sounds.
It still worked though, so I could spend some time browsing the recovered SDcard data.
Sadly, those files where unreadable, probably because the recovery software was trial, so it made all of them "Unreadable Before You Pay", hard to tell by now.
I decided to try another Recovery Tool, ignoring the HardDrive issue for now, but my CardReader or the SDcard or both appeared to be dead.
6. Bricking the Vibe.
After spending some time doing backups of my dying HardDrive data, I returned to Rooting my smartphone, but by "manual" methods this time.
Trying all of those scary weird methods while actually learning all the stuff about "flashing" led me into bricking my device.
7. Failed Rooted Recovery.
Somehow, by following few guides, I finally managed to do everything correct (I hope).
I mean, unlocking bootloader by fastboot, gaining temporary root by ADB, flashing TWRP recovery and Stock ROM by QFIL, installing SuperSU, and actually rooting the device.
Right after, I downloaded a bunch of recovery apps to try again, but all of the photos and pictures, found by scanning, were useless.
Even those results before rooting were much better.
8. Failed RAW Recovery.
Surfing different forums, led me to a guide about using PC recovery tools on an Android RAW image.
While surfing, I have already tried about five PC-Android recovery tools and they didn't help much, but I decided to try it anyway.
By using BusyBox, Cygwin, NetCat, ADB, VhdxTool, I made a RAW image of my internal memory partition, converted it into a VHD and mounted it for scanning.
After using about 25-30 recovery tools I did not find any of those desired lost photos.
Scanning results on jpegs are pretty much the same for each tool.
Thank you for reading if you decided to do so anyway.
I also found others who did try to recover their precious data, like I did (after flashing and going through all the problems with rooting and getting a RAW file).
It seems like they all failed as well, so the question is - is it actually possible?
I know it's much easier with an HDD, since I know that those mansions usually keep ghosts for years, while Android totally exhausted and after all, killed me.
I really need help with this, since I see no more ways to try. If you have any advice, please share.
P.S. I'm sorry for my english, not native.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist.
Please have a look at the P1 homepage:
http://forum.xda-developers.com/vibe-p1
If you create an XDA account, you can ask your question to the experts here:
http://forum.xda-developers.com/vibe-p1/help
Good luck and welcome to XDA!
Hello everyone,
I need your help. Sorry for the long post.
I have a OnePlus One. It was running on CM 13.0 (Android 6.0.1). I had TWRP and MultiROM installed.
I have had an issue where whenever I flash a zip file in TWRP, the phone will show an error after installing the zip: "Unable to mount storage". This appeared in red color on the screen right after showing the progress of the zip installation. The phone worked fine and all the flashed zips worked great as well. However, the error that appeared every single time when I flash a zip file bothered me. So I tried to fix it. (I know, if it's not broken don't fix it, but sadly I tired).
I followed this video to get rid of the error => (https://www.youtube.com/watch?v=X7yDPszoQ5s). However, instead of getting rid of the error, I ended up with a huge problem. My phone couldn't recognize the data in the internal storage. It showed that the internal storage was empty. When I tired to reboot in TWRP, It said: "No OS installed are you sure you wish to reboot". I realized that the video I followed was for a different problem and that I ended up with the same issue the video was trying to fix! I tried every single option the video suggested to fix the problem and nothing helped.
I connected my phone to my laptop and downloaded the latest CyanogenMod zip for my phone and I flashed it. when I rebooted my phone I got a screen that asked for my password. I typed a random password (I discovered later that the phone will accept any password and say it's correct). I got the following error: "Decryption Unsuccessful... The password you entered is correct, but unfortunately your data is corrupt... To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your google account...Then the only thing I can select is "reset phone." ". I pressed the reset button on the screen, the phone rebooted and showed the same error. Then I tired flashing PAC ROM and I got the same error again. Then I flashed OmniROM and the phone worked! It didn't show the error.
I have a Titanium backup for all my apps and I also have a nandroid backup for my previous ROM (in my memory stick using an OTG cable). However, I don't have any backups for my internal storage (photos, videos, documents... etc). I am guessing that these files are still in my internal storage. I didn't copy any new files to my phone because I think if I do, then the phone will keep replacing my old files (that I can't see) with the new ones.
My question is: Is there a way to get back these old photos and videos from the internal storage? Note that I didn't delete these files, but the phone can't read them. Also, I checked the nandroid backup that I have and the file system type of the previous ROM was EXT4. My current file system type is the same, EXT4.
Thank you for the help!
Hi guys,
I own a Nexus 5 16gb with purenexus 6.01 I'm buying another 32gb and to speed things up I would like to transfer the Nandroid backup of the first on thesecond.it can do? there would be stability problems?
i will use the 32gb as main phone and the 16gb for "home experiments" about rom, kernels and another...
thank you
It is possible to restotre it, but HELL DONT EVER RESTORE EFS!!!! it will mess up the imei and you will loose conectivity
aciupapa said:
It is possible to restotre it, but HELL DONT EVER RESTORE EFS!!!! it will mess up the imei and you will loose conectivity
Click to expand...
Click to collapse
of course, just boot, system and data (cache?).
I'm just afraid that in the boot.img is saved some serial number [phone, or a wifi mac address] that do not meet on the other device, can lead to malfunctions or brick
Luca TIR said:
of course, just boot, system and data (cache?).
I'm just afraid that in the boot.img is saved some serial number [phone, or a wifi mac address] that do not meet on the other device, can lead to malfunctions or brick
Click to expand...
Click to collapse
I have been restoring all of my partitions with twrp for a long time, no problems. TeamWin had informed users that restoring the EFS partition on a specific device (nexus 5x, 6, don't remember exactly) would brick the device. But restoring your 16gb backup to a 32gb device might have other problems such as not seeing your entire memory.
Judging by the fact that if you flash your 32gb nexus 5 with the google factory image then you have to manually "wipe data/factory reset" via recovery to get it to recognize 32gb (or else it says you have only 16, small heart attack there), then that means that the memory capacity is defined somewhere in the software (obviously). Also, the partitions would be of different sizes. You'd have no problem transferring backups between identical devices, though when you have a different memory storage, you need to reinstall everything.
Hardware information such as MAC adresses are not saved anywhere, they are retrieved at runtime. Consider that you can even change a MAC address on the fly and the device would have no problem with it as long as you turn it off and on again (ifconfig wlan0 down && ifconfig wlan0 up) (as far as the OS is concerned, because you can't truly change it, I think it's hardware defined). Same goes for IMEI etc. But the flash memory consists of many partitions that need to be of specific size. If you restore a partition with different size than it's original one, you might soft brick it.
In conclusion, no, don't transfer your backup. Unlock the device, flash recovery, flash zips, setup your device again...
chrisk44 said:
I have been restoring all of my partitions with twrp for a long time, no problems. TeamWin had informed users that restoring the EFS partition on a specific device (nexus 5x, 6, don't remember exactly) would brick the device. But restoring your 16gb backup to a 32gb device might have other problems such as not seeing your entire memory.
Judging by the fact that if you flash your 32gb nexus 5 with the google factory image then you have to manually "wipe data/factory reset" via recovery to get it to recognize 32gb (or else it says you have only 16, small heart attack there), then that means that the memory capacity is defined somewhere in the software (obviously). Also, the partitions would be of different sizes. You'd have no problem transferring backups between identical devices, though when you have a different memory storage, you need to reinstall everything.
Hardware information such as MAC adresses are not saved anywhere, they are retrieved at runtime. Consider that you can even change a MAC address on the fly and the device would have no problem with it as long as you turn it off and on again (ifconfig wlan0 down && ifconfig wlan0 up) (as far as the OS is concerned, because you can't truly change it, I think it's hardware defined). Same goes for IMEI etc. But the flash memory consists of many partitions that need to be of specific size. If you restore a partition with different size than it's original one, you might soft brick it.
In conclusion, no, don't transfer your backup. Unlock the device, flash recovery, flash zips, setup your device again...
Click to expand...
Click to collapse
clear, precise and convincing ... you're right .especially different partitioning and memory size did not convince me, you have confirmed to me. I try suffered some rom nougat when I get the device
p.s.:no small heart attack please, i'm an ambulance driver :laugh: (really)
many thanks
The emulated sdcard is not backed up by twrp anyway. I would just adb pull that partition and then push all the files back on the knew device. Data and system should be fine with twrp.
(apparently) it's working!!!
Today, I received the "twin"
just out of curiosity I tried to restore the backup on the 16gb and 32gb [purenexus 6.01] and all seems to work.but I have yet to test it.
Now I go to work tomorrow I put the sim card and use it normally to confirm that everything is ok.
p.s.:the data on the free / busy sd internal memory are righteous