Hi
I have a dead (not responding nor charging) J510FN. There was no encryption activated on the device
FOr the purpose of data recovery from the internal memory I got hold on a eMMC reader. I could recover something like 27 partitions from it, including the userdata partition (around 11,5GB)
Looking with a hex editor through the file I can see its basically full with data. But I didn't have any success yet in recovering any files. I tried to mount the .bin file and run a recovery program (ext4) through it, but couldnt get any files at all.
Someone can give me a hand on this?
Related
My Nook Simple Touch (1.1.2) is now not working because I wiped ALL the partitions before attempting to restore a backup (which I didnt know was bad at the time)
Notes
1. I have two backups:
a) the first is 239mb which contains my ebooks and pdfs
b) the second is the boot partition (77mb) - I backed up again when when noogie was on micro SD
2. So basically (both backups) I backed up the NST without selecting the whole physical drive.
3. After a failed root, I tried to restore the backup (and seeing it fail), I decided to wipe the whole partition before attempting to restore again :crying:
4. Are there any restorable backup images that can be downloaded online? Or anything which can restore the partition table including the ROM partition with the serial address etc.
5. Please help me restore the Nook back to factory or any working state. Cos AFAIK i've bricked the device.
p.s. I have tried touchnooter and installed touchformatv2 but all I get now is a Read Forever load screen. N2Tsecurity doesnt work without the ROM partition.
Please Please Help Me Im so sad (I know this is down to carelessness on my part but I really need help)
Did you really wipe all the partitions (like write zeroes over the entire physical drive)?
Or did you just try to repartition it?
The question is whether you truly wiped out the /rom and /factory partitions.
Sometimes partitioning them correctly you can rediscover the file system.
The /rom partition is necessary, even ClockworkMod needs to be able to see it.
The /rom info is replicated in /factory/rombackup.zip
Renate's solution may work.
Also, there is a tool called testdisk available for linux that I've used to recover data and partition layouts before; I would expect that it may work a champ for situations like yours.
To use it, you would need a linux box or find a windows port and boot the NSTG or NST from the noogie disk.
Testdisk can recover deleted partitions automatically, including the all-important /rom partition.
That one's important because it contains device-specific info for your NST. It'll do it automatically, but you do need to read up on what commands to give it. You can also rebuild the table manually using fdisk (and I've done so successfully before.)
A windows file recovery utility might let you recover /rom as well (or the files from it.)
You most need the contents of /devconf, and there are lots of files there. I am not sure which ones are absolutely required.
Hi,
I am using the following tutorial to recover my snapchat data folder from my phone. http://forum.xda-developers.com/gal...emory-data-recovery-yes-t1994705/post34185439. I have gotten to the part when I mount and format the VHD. When I use Recuva or Puran File Recovery I don't get the files I need. Is there a recovery software that searches for ALL files, specifically files that end in .nomedia?
Just to make sure I am mounting the right partition, everything from
/data/data/com.snapchat.android/cache/received_image_snaps
would be in /dev/block/mmcblk0p23 which is the userdata partition, is that correct?
I'm trying to recover files from my phone. coping /dev/block/sda18 using dd has not worked for me as recovery software only finds 3 files on the filesystem (it was high level formatted). There are alot of file recovery tools on android but I need to be able to boot my phone, in order to prevent any damage to the USERDATA partition (sda18), I thought of possiblly forcing it to be read only and then installing firmware, booting, installing recovery software, and using it on the read only internal memory.
is this feasible?
Thanks all
I could use an undelete apk, like this one -> fahrbot.apps.undelete. I'll try to install with /data unmounted...
hello
my phone asus zenfone 2 500kl run out of battery i put it on the charger then i powered it up but
i got a message that data encryption filed with a button to erase data but it did nothing
pleeeeeeeeeeeeees can anyone help ???
in recovery data partition is corrupted with 0mb size can't format can't fix
i think i need a tool to re partition the disk to fix these error
any help please
UPDATE :
i managed to solve the problem with TWRP
by changing the file system of (data) to other one then change it to EXT4
i had to change it 2 times but then every thing is ok
note that every thing in data including internal sd card will be wiped
Hi, guys!
I decided to make a backup of my smartphone, for which I installed TWRP. Here is my sequence of actions after that:
1. In recovery mode on a completely unencrypted smartphone, I successfully created an archive, leaving the flags of the default sections selected: Boot, System and Data.
2. I encrypted both the device memory and the external SD card (which I bought separately). And again I tried to archive: the partition /Data refused to encrypt (I got an error: 'Could not mount /data and unable to find crypto footer'), so I deleted this incomplete archive. At the same time, the TWRP decrypted the external SD card and at the start of the system it was encrypted again.
3. I decided to check how recovery from archive works and tried to recover the archive created in step 1. By default, there were selected three flags Boot, System and Data, after starting the recovery, I received an error (the text of error may be differ, because I'm translating from Russian):
Unable to recover System - read-only mounted.
Click to expand...
Click to collapse
Then I tried to restore only Boot (removed the flags from the remaining check boxes) and received a red message in the header "failure!" (the output in the terminal was without errors).
Then I tried to restore only the Data partition, and it recovered in 2 seconds, which obviously cannot be truth. I tried again and this time the partition recovered in 1 second
I decided to reboot into normal mode, and then a surprise awaited me: the smartphone didn't boot and wrote a red error:
Could not do normal boot. Invalid id KERNEL LENGHT!
Click to expand...
Click to collapse
I tried to reflash TWRP and then reboot into TWRP mode in normal mode. I tried TWRP v3.3.1 and v3.4.1 - I got the same error as it was originally, after which the smartphone turns off. But the good news is that all other button- combinations work (i.e. I was able to successfully reflash TWRP twice).
Does it make sense to flash the official firmware
I think, that most likely reason the error occurred, because the external SD-card, on which the archive was stored, was encrypted. But I didn't attach importance, because:
1. Saving the archive to an encrypted card was successful (the external card was decrypted).
2. The name of the archive was visible (and even a set of encrypted areas!), which means TWRP could somehow decrypt the data.
The worst thing is that I didn't copy archive from step 1 to my PC, and now this card (with the archive) can only be read by my non- working smartphone. Perhaps, of course, there is some kind of bug in the encryption system on my old smartphone, which still allows me to decrypt this archive and try to restore it more correctly again
I did it!
I flashed the official firmware and my smartphone work well!
Yes, I'm hacker!