Last week something burnt out in my Streak, it wouldn't turn on, so I needed to send it to get repaired/replaced, as a little data insurance I took a dump of the internal SD card (just using dd in Ubuntu).
Now O2 are replacing my Streak, so I'll have a new one with a different IMEI, etc, and I don't want to open this one (I only opened the other one as it was an emergency). So I'm looking for help on restoring the backup I've taken without opening the phone, and once done, leaving it in a warranty-friendly state.
Obviously the first step is going to be rooting it, but what then? Is it simply a matter of copying all the files? Just thinking that might cause conflicts due to the new IMEI.
so i've got a similar (but reciprocal) problem... i had a malformed update.zip that pooched my internal microsd's system partition and the streak won't boot at all... I have a nandroid backup and i've pulled the internal microsd to find an empty ext filesystem that mounts just fine when I plug it into a linux laptop, but there's not a clear mapping from the system.img that I have and the contents of the accidentally wiped system partition...
SO, two things would fix this....
1. someone could send me a link to their raw 'dd' image of the system partition (~200mb)
2. or, I can keep figuring out how to use 'dd' with the system.img that I have to get the same results as the 'flash_image' tool...
would someone be so kind as to speed me along on this by giving me their system partition dump (1) or quickening my learning curve on (2) so that I can restore with the flash_image formatted nandroid dump of a working system partition???
Please, please....
Related
I know i need to extract them with unyaffs.exe
But i can't find where my camera photos stored ..
Please navigate me to the path ...
Motorola Atrix 2.3.4 device.
Thanks.
Nowhere, they're on the SD card (/DCIM/)
So they are gone ?
I stored them at the internal sd, not in the external sd.
Internal SD... ah, sorry: the Atrix has built-in memory... I wasn't aware of that. That depends on how it is accessed... I still wouldn't expect it to show up in Nandroid backups, but if your lucky it doesn't get formatted and you can still retrieve it. The question is, what device is this internal storage and what filesystem does it use.
Can you still mount the storage on the PC? You should be able to retrieve most of your images even if the drive was formatted using a standard photo recovery tool
I just full wiped everything .. all the storage places too and intsalled new ROM.
OK, i can do that , which revocery tool should i use ?
It's been a while ... I think I used this one:
http://www.z-a-recovery.com/digital-image-recovery.htm
The free version is enough for image recovery.
Thanks
Just recover some of my images ...
But i can't get the full library from the nandroid backup? what information do you need?
I know i can just restore the nandroid backup ... but it will do trouble ... diffrent kernel from my preset rom..
Any ideas?
?
Sorry for the late response, But I just stumbled upon the thread. I had the G2x. The internal memory is just like another SD card. Just that it's not removable. What's backed up in a Nandroid is things like the /data, /cache /boot /system and android.secure partitions. The internal memory is /emmc. It doesnt get formatted in a wipe (unless you say so) and it doesnt get backed up in the Nandroid. Otherwise, your Nandroid backups would be EXTREMELY large.
Now that I have my rooted NT the way I want it, I would like to somehow copy the whole image off onto my computer. Nandroid and Titanium Backup all seem to need a recovery ROM, and I don't think there are any for the NT.
Any ideas?
Dangerous method
jarome1 said:
Now that I have my rooted NT the way I want it, I would like to somehow copy the whole image off onto my computer. Nandroid and Titanium Backup all seem to need a recovery ROM, and I don't think there are any for the NT.
Any ideas?
Click to expand...
Click to collapse
Once you are rooted, AND if you have a 16GB SDcard installed:
Make sure the SDcard is NOT MOUNTED.
At the rooted command prompt, type "dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1"
Immediately remove the SDcard and save it.
That's the easy part. You can restore the internal memory by issuing the same command again, but with the "0" and "1" swapped. However, doing so will replace EVERYTHING on the Nook, even the recovery partition. Consequently, it is EXTREMELY DANGEROUS to do. In particular, I have not tested it (I've done the backup but not the restore). Further, if you system is so damaged as to need this, I don't see how in most cases you'd be able to get to a rooted command prompt, and the SDcard is not bootable. If we ever get to a point where we can create bootable SDcards, then a modification of this procedure would be useful.
Of course, with an SDcard created like this, you could insert it after booting and copy over portions of a partition (after mounting the relevant partition on the SDcard), and/or possibly even who partitions.
Clearly, this is an advanced technique not intended for those unfamiliar with Linux commands, and even then, it should be tested in a safe or recoverable environment.
to make a long story short, something went terribly wrong with my android phone, wiping my contacts and SMS. How do I go about recovering deleted files from internal storage (NAND)? And which files do I need if I only want to recover my contacts and sms?
I've spent the past 6 hours searching and attempting to recover them by following different tutorials, but no dice. Ive read an article where people were saying that if I take too long, I will not be able to recover my data. Please please help me as I really need to get my important data back. I'll return the favor by buying you a beer or something! THanks in advance for your help!
" Ive read an article where people were saying that if I take too long, I will not be able to recover my data. "
Although I can't help you with the actual issue of getting the data back, I believe it is not so much taking time to recover your data which will delete it, but how much data is rewritten to your phone (which could overwrite the previous data) atleast thats how it works on desktops...
My only idea would possibly to have a look for a .trash folder in the root directory of the phone's memory, or maybe look for a LOST+FOUND folder, hopefully this will be of some help to you!
Whippopotamus said:
" Ive read an article where people were saying that if I take too long, I will not be able to recover my data. "
Although I can't help you with the actual issue of getting the data back, I believe it is not so much taking time to recover your data which will delete it, but how much data is rewritten to your phone (which could overwrite the previous data) atleast thats how it works on desktops...
My only idea would possibly to have a look for a .trash folder in the root directory of the phone's memory, or maybe look for a LOST+FOUND folder, hopefully this will be of some help to you!
Click to expand...
Click to collapse
If you wait too long, but there is no current running to the device, the data on the flash storage will not change. Flash has more data remnance than a magnetic storage. What is important is not the time taken, but rather how much data has been written to the disk.
I hope you have a nandroid backup of your device, if not, see if it's possible to boot to clockworkmod now and make a backup.
Using this disk image, you can then use flash memory data recovery tools to recover the data you need.
Hope this helps.
exge said:
I hope you have a nandroid backup of your device, if not, see if it's possible to boot to clockworkmod now and make a backup.
Using this disk image, you can then use flash memory data recovery tools to recover the data you need.
Hope this helps.
Click to expand...
Click to collapse
good idea, so I was able to boot into Clockworkmod recovery, and right now i'm making a backup through that recovery. So once the backup is created, how do i go about getting my contacts and sms back? like which files do i need to recover?
EDIT: Here's what I'm getting when trying to create a backup:
SD Card space free: 6075MB
Backing up boot...
Backing up recovery...
Backing up system...
Backing up data...
Can't mount /data!
Click to expand...
Click to collapse
^operation stopped while trying to back up data, for some reason it could not mount /data.
despite the operation halt, clockworkmod was still able to create a backup that contains 3 files: boot.img (about 4.4MB), recovery.img (about 5KB), and system.img (about 370MB).
ok now how can I open system.img to look the for my contacts and sms? and what would be the file names?
The data issue means that the data partition is corrupted. The only option is to format it.
Sent from my phone to your eyes
yea i gave up. went ahead and reformat/reflashed my rom. fortunately i was able to find a really old backup of my contacts, but that's better than losing everything. thanks
you can install a recovery apk your phone or recavery app your camputer and then recovery informations from your phone
You can find many Android phone data recovery applications that advertised to be able to recover files from SD card if you search on Google, but which one can recover data from Android internal storage? Luckily FonePaw Android Data Recovery just supports Android phone internal storage recovery. The program is a professional data recovery tool for Android phones and tablets. It can retrieve lost files from SD card inside Android devices as well as internal memory of the Android devices. You may interested in what files the program can recover, let me tell you. Lost pictures, videos, contacts, text messages, documents, audio files can all be retrieved effectively no matter how you lose it.
I had a bootloop issue on my GT-N9300 speadtrum and finally solved it by flashing the ROM using the UpgradeDownload tool
Phone Specifications and Phone information
After the process, I lost all data on the phone (call logs, etc) and on the SD card and I had to root again the phone.
When using testdisk to restore the SD card, I get this:
The first two FAT32 partitions give "no file found, filesystem may be damaged" while the third one contains files.
The first swap partition option gives: Can't open filesystem; files system seems damaged, while the second one gives this result:
First [rom] partition also gives that "it seems damaged"while the next two [rom] partitions contain entries.
The last Linux swap gives: Support for this filesystem hasn't been enabled during compilation
What shall I do to make the SD card work again and restore all my data?
I hope I clearly described it and that someone can help me restore the data.
Hey Guys,
I have a Android/WinCE Car Radio.
So I got Android on a SD Card and it booted well, but one day it stopped booting.
If I mount the SD from the internal Android on the device, there is a LOST.FOUND directory on the boot partition where boot.scr and so on is.
If I delete the directory and restart, the system boots from the SD again. But if I do a restart, the system won't boot again. I need to delete the LOST.FOUND directory every time...
I'll Attach the boot partition, maybe you can give me a solution to this.
Thanks
bump
If you run fsck, the filesystem check and repair command, it might find data fragments that are not referenced anywhere in the filesystem. In particular, fsck might find data that looks like a complete file but doesn't have a name on the system — an inode with no corresponding file name. This data is still using up space, but it isn't accessible by any normal means.
If you tell fsck to repair the filesystem, it will turn these almost-deleted files back into files. The thing is, the file had a name and location once, but that information is no longer available. So fsck deposits the file in a specific directory, called lost+found (after lost and found property).
Files that appear in lost+found are typically files that were already unlinked (i.e. their name had been erased) but still opened by some process (so the data wasn't erased yet) when the system halted suddenly (kernel panic or power failure). If that's all that happened, these files were slated for deletion anyway, you don't need to care about them.
Files can also appear in lost+found because the filesystem was in an inconsistent state due to a software or hardware bug. If that's the case, it's a way for you to find files that were lost but that the system repair managed to salvage. The files may or may not contain useful data, and even if they do they may be incomplete or out of date; it all depends how bad the filesystem damage was.
Click to expand...
Click to collapse
Make sure your boot files in the root of the partition are ok.
Make a backup of the files, copy the files in the lost.found directory over the existing files or use the original one (firmware download from device supplier?)
And make sure you unmount the SDcard safe.
Good luck..
THere are no files at the LOST.FOUND directory.
If I take a other SD and put the stock image on it, it's the same problem.