I am looking at modifying the contents of the data.img and system.img files that were created by nandroid.
I've looked around, but came up empty.
How can I do this?
outsider787 said:
I am looking at modifying the contents of the data.img and system.img files that were created by nandroid.
I've looked around, but came up empty.
How can I do this?
Click to expand...
Click to collapse
I just recently learned that you have to unyaffs them. Not sure how to recomplie (is that the right word?) them after you make edits though.
I've been trying to get the system.img file mounted on the device itself (since it has yaffs2 built into the kernel), but no luck so far.
Has anyone else have had any success mounting these .img files from within the android OS?
Yaffs won't work that way since the image isn't a block device. It has to actually be on a block device to mount.
Ok.
What if I make a partition on my SDcard, somehow write the data.img file to that partition, and then mount that partition.
Would that work?
I have only one problem. I don't know how to write the .img file to a partition.
Anyone have any idea?
I have downloaded a nand androuid build that I am 99% happy with. I do however want to change a couple of things on the build.
I have downloaed and got ubutu up and running on a virtual box. I have then copied the system.img file on to a usb drive and copied it into ubuntu. Location of the file is in stephen which is my logon name.
I have also created a folder called mount which I want to mount the img file to.
I have done this before in ubuntu using ext2 files but I can not get the mount command to work for an img file. Is there an way to mount the img file, remove the files I do not want and then comple a newer smaller img file?
EDIT: logged on as root and moved the system.img and mount folder to main file system folder. Ran command mount -t img /system.img /mount but now getting error unknown filesystem type 'img'
Any help would be appreciated.
I rooted two nooks, and made tar backups of their partitions (I also got the dd image just in case). Out of curiosity, and with the goal of keeping minimal backup and increasing the partition for side-loaded contents to maximum, I tried to compare the contents of each partition. Since I followed the same process for rooting (Touch-Formatter v2, 1.2.1 update, NookManager, NTGAppsAttack - but before booting the Nook I got the backup), I guessed quite a lot of them are the same, and found some interesting results.
1. Boot partition is nearly the same except uRamdisk. I inspected the contents of the two uRamdisk files using bootutil by Renate, and they are identical.
-> Why are they different, and can one replace the other?
2. As we all know, rom partitions are different, but it looks only a few of them can meaningfully affect the operation. Anyway, it's small and I decided to leave them untouched and keep two separate copies.
-> What is the BCB file by the way? It just has zeroes inside. Is it automatically created if not there?
-> Some files in the devconf directory seem to be modified during the normal process or firmware update, notably BootCnt (four zero bytes), Bq275020Dffs (12 in the rombackup.zip, 13 after 1.2.1 update). What are these? Any idea?
3. The factory partition, I want to bust it (empty it up and resize it to the minimum), and let me know if I'm on a dangerous path. The idea is that I don't need rombackup.zip because I can revive the rom partition with my own tar backup if something bad happens, and it's out of date anyway after 1.2.1 update (some files in the rom partition are modified). Also, with Touch-Formatter and CWM, I wouldn't need the factory.zip file.
-> What are the files in the "touch" directory? One of my nook has them, but the other doesn't. Looking at the data inside they must be related to the display or touch screen. Maybe byproduct of calibration?
-> Can I use 1.2.1 update file with CWM instead of using Touch-Formatter, bringing it to a new fresh 1.2.1 Nook? According to this post, it seems possible.
4. The system partitions are identical, as expected. but with CWM recovery, we wouldn't need a backup of it, right?
5. The cache partition is way too big. I know the firmware update uses this space (when I resized it to something like 64MB, 1.2.1 update didn't work. I needed to increase it to something like 128MB to make it work). However, for normal operation, we surely don't need it that big.
-> How small can it be? I know it depends on individual's usage patterns... but in my case, I mostly use Nook for reading side-loaded contents. I've gone down to 32MB, but I guess that's still big.
-> Do we really need the cache partition? Can we just symlink it to somewhere in the data partition?
Out of curiosity, I just deleted BCB and BootCnt in the rom partition, and rebooted. First it said "Install Failed", a screen I have never seen before on Nook. So I looked into the rom partition and found that BCB file is recreated, but not BootCnt. On the subsequent boot, it said "Installing Rom", and then quickly rebooted. Now it's back to work. So, I guess these two files are essential for normal operation. Again, this time I deleted all files in the factory partition and also deleted BootCnt. Now, it tries to do the "Installing Rom" thing, but fell back to "Install Failed" screen. I opened up the rom partition again and I saw only BCB and BootCnt files, and none else. Nook surely formatted the rom partition first before trying to recreate it.
So I wonderfully bricked my Nook, and thought this is a good time to test if the rom partition backup works. I mounted the rom partition, untarred the backup, and rebooted. There we go, the Bronte Sisters are back. So the conclusion is that
1. When the BCB file's missing, it's simply recreated after a failed boot.
2. When the BootCnt file's missing, Nook thinks the rom partition is corrupted and tries to recreate it using rombackup.zip in the factory partition. I think this may have some side effects because firmware updates only change the files in the rom partition, leaving rombackup.zip untouched. So you will go back to the old rom partition after the built-in rom recovery.
3. The best rom recovery, I think, is using your manual backup of the rom partition. And maybe updating the rombackup.zip with a new one too?
BootCnt is a 32 bit little-endian count of the number of failed boots.
Once it hits eight your Nook will boot into the recovery image uRecImg, uRecRam.
You could also echo about anything to that file to make it arithmetically greater than 8.
Code:
echo 000 > /rom/devconf/BootCnt
That is 0x0a303030 > 8
Normally this is a B&N thing that asks you about factory restore.
If you replaced those two files it could be Clockwork Mod Recovery.
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...