is there a way for me to backup my ext2 app partition on my sdcard with a windows machine? im running cyans 4.0.2 and i love it! but i would like to be able to backup the partition 'just in case' but i only have a xp desktop. thank you!
need to backup your ext partition?
the following commands will backup/restore your ext partition to/from a folder named sdbackup in your current directory. these must be run while phone is booted, not recovery.
to backup your ext partition: adb pull /system/sd/ %CD%\sdbackup
to restore back to sdcard: adb push %CD%\sdbackup /system/sd
When you star a thread with "How..." in the title you must start this thread in Dream Q&A sub forum !
Thread moved
You can also use Ubuntu.
title sounds more like this thread would be instructions rather than a question.
Another way that does not require adb would be to enter the following in terminal emulator
Code:
cd system
cp -r sd /sdcard/(name of folder you wish to backup to)
Than just plug the usb into your windows box, mount the sd card, and copy the folder.
hcphs said:
need to backup your ext partition?
the following commands will backup/restore your ext partition to/from a folder named sdbackup in your current directory. these must be run while phone is booted, not recovery.
to backup your ext partition: adb pull /system/sd/ %CD%\sdbackup
to restore back to sdcard: adb push %CD%\sdbackup /system/sd
Click to expand...
Click to collapse
Will this allow me to move my partition to a different SD card without re-installing all my apps (via nandroid)?
This is how I got dual booting from windows working and am now dual booting Nottachtrix4G from sdcard with stable
cam and WEBTOP along side AOKPCB
I was only able to achieve this after following sendust7 linux guide for dual boot and adapting to windows so all
credit goes to him.
Again these are the steps I took. If you try this and break something I'm not responsible.
Pre-requisites
Notepad++
Minitool partition wizard
Android SDK (google adb for dummies to get everything you need)
Cygwin (if you dont have it start install now and it might be done when its time to use it)
The rom zip you want on your sdcard and the rom zip you want on your phone
Moto-fastboot (search this forum)
Knowledge of ADB and fastboot
Fully Charged Battery
Backup everything from internal and external sdcard
Reboot to recovery
Flash the rom that you want on your sdcard to your phone like you would do normally.
Reboot phone and set it up if you like or just reboot back to recovery. If you set your rom up at this point, this
is how it will look on your sdcard at first boot.
Reboot back to recovery
adb shell
~ #mount /cache
~ #mount /system
~ #mount /data
~ #mount
Take note of system data and cache file systems (ext3 or ext4)
Power off phone and pull sdcard
Insert sdcard into computer and open minitool partition wizard.
Partition and format sdcard with same filesystem as noted before
These are the partition sizes I went with and only because i didnt feel like adjusting the slider anymore. But
These values did ensure they were big enough to hold the phone partitions. The first partition is whats left over
after resizing other partitions and will be formatted to fat32
system=384 MB <second partition on sdcard
cache=700 MB <third
data=2.6 GB <fourth
Insert sdcard and boot to recovery
adb shell
PATIENCE IS KEY FOR NEXT STEPS
~ # dd if=/dev/block/mmcblk0p12 of=/dev/block/mmcblk1p2 bs=1M
655360+0 records in
655360+0 records out
335544320 bytes (320.0MB) copied, 115.626214 seconds, 2.8MB/s
~ # dd if=dev/block/mmcblk0p15 of=/dev/block/mmcblk1p3 bs=1M
dd if=dev/block/mmcblk0p15 of=/dev/block/mmcblk1p3 bs=1M
640+0 records in
640+0 records out
671088640 bytes (640.0MB) copied, 206.557368 seconds, 3.1MB/s
~ # dd if=/dev/block/mmcblk0p16 of=/dev/block/mmcblk1p4 bs=1M
dd if=/dev/block/mmcblk0p16 of=/dev/block/mmcblk1p4 bs=1M
2048+0 records in
2048+0 records out
2147483648 bytes (2.0GB) copied, 658.327418 seconds, 3.1MB/s
Now get boot.img
While still in adb shell
~ #mount /dev/block/mmcblk0p18 /emmc
~ #cp /dev/block/mmcblk0p11 /emmc/boot.img
~ #exit
~ #adb pull /emmc/boot.img boot.img
Go here and follow this step by step and stop after you've got your boot image unpacked
http://forum.xda-developers.com/show....php?t=1630130
If you have any problems with cpio run cygwin installer again and search for cpio and install
Once boot image is unpacked go to the out directory and find init.rc
Edit init.rc with notepad++ (NOT NOTEPAD) and change these lines
ONLY CHANGE THE /dev/bloc/mmcblk part. LEAVE EVERYTHING ELSE THE SAME
From
mount ext4 /dev/block/mmcblk0p12 /system noatime nodiratime wait ro barrier=1
mount ext4 /dev/block/mmcblk0p16 /data nosuid nodev noatime nodiratime wait barrier=1 noauto_da_alloc
mount ext4 /dev/block/mmcblk0p15 /cache nosuid nodev noatime nodiratime wait barrier=1 noauto_da_alloc
TO
mount ext4 /dev/block/mmcblk1p2 /system noatime nodiratime wait ro barrier=1
mount ext4 /dev/block/mmcblk1p4 /data nosuid nodev noatime nodiratime wait barrier=1 noauto_da_alloc
mount ext4 /dev/block/mmcblk1p3 /cache nosuid nodev noatime nodiratime wait barrier=1 noauto_da_alloc
Once you have made these changes you can finish the tutorial posted above or below for repacking and make sure to
click thanks. If the boot_new.img is a different size than original that's okay.
http://forum.xda-developers.com/show....php?t=1630130
Move your boot_new.img to your moto-fastboot and reboot phone to fastboot.
moto-fastboot boot boot_new.img
If you're booted into your sdcard rom you're almost done.
Reboot to recovery and install any rom you want and boot to it.
Now create this directory on your internal sdcard
/sdcard/Boot/sdrom/
Copy your boot_new.img you used to boot your sd rom earlier to this directory and rename it to sdrom.img
Now create this directory on your internal sdcard
/sdcard/Boot/emmcrom/
Now open the rom zip you installed to your phone and copy the boot.img to this directory and rename it to
emmcrom.img
Use attached script with scriptmanager to commense dual booting. (Rename to modified-boot-rom.sh)
Run script as root with argument 1 to reboot to sdcard rom and argument 2 to reboot to phone rom. Argument 3 will
send you to recovery.
All done from windows even though it would be twice as easy and fast to do with linux but there ya go.
I take no credit as all I did was find the right resources and none of this would even be possible without
sendust7. If this helped you Please go to his guide and thank him TOO!!!!
http://forum.xda-developers.com/show....php?t=1642185
great.....will try and post back my experience!!!
I get everything up to get boot image. when I run that command, it runs for a few seconds then adb stops responding.
Any advice? I waited the one time for 15 minutes hoping it would respond...but it didn't.
thanks!
Sent from my MB860 using xda premium
95rr900 said:
I get everything up to get boot image. when I run that command, it runs for a few seconds then adb stops responding.
Any advice? I waited the one time for 15 minutes hoping it would respond...but it didn't.
thanks!
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
What rom are you putting on sdcard
EDIT: look in your rom.zip.....boot img may be in there. If it is you can just use that
Edit: could try to make sure sdcard is mounted.......mount /sdcard
Sent from my MB860 using Tapatalk 2
Im putting nottachtrix on sdcard.
Ok, so I can just copy the boot image from the rom zip and use that in cygwin...and go from there?
Now that I think about it, the sdcard was probably not mounted.
I'll give it another go in the morning. Thanks for the help!
Sent from my MB860 using xda premium
95rr900 said:
Im putting nottachtrix on sdcard.
Ok, so I can just copy the boot image from the rom zip and use that in cygwin...and go from there?
Now that I think about it, the sdcard was probably not mounted.
I'll give it another go in the morning. Thanks for the help!
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Yes
Sent from my MB860 using Tapatalk 2
Install rom you want on your sdcard
hatefuel19 said:
Install rom you want on your sdcard
Reboot phone and set it up if you like or just reboot back to recovery. If you set your rom up at this point, this is how it will look on your sdcard at first boot.
Click to expand...
Click to collapse
What do you mean by install on sdcard and is that internal or external sd? And does Aroma make any difference
many thanks Simon
EDIT : Im an idiot it means install to the phone, the rom you want to have booting from sdcard.
This is really burnin my nut sack
No matter what I do, I can't get through "getting boot image". I tried going into the nottachtrix rom.zip, but it is set up different from other roms. I guess because of the aroma installer?
Maybe I'll try with a different rom just to see if I have the same problem.
EDIT: Tried it with aokp, and still get adb not responding in the middle of getting boot image?
95rr900 said:
This is really burnin my nut sack
No matter what I do, I can't get through "getting boot image". I tried going into the nottachtrix rom.zip, but it is set up different from other roms. I guess because of the aroma installer?
Maybe I'll try with a different rom just to see if I have the same problem.
EDIT: Tried it with aokp, and still get adb not responding in the middle of getting boot image?
Click to expand...
Click to collapse
In about thirty minutes I'm gonna run through this again. Been trying to get webtop2sd working. Once I do I'm gonna do this tut again step by step and I'll see if I have any snags.
And you're right since nottachtrix uses aroma it isn't packed like other rooms which is why I put this step in here
Edit: strange how its doin same to me now too.......found a fix and gonna double check b4 I update op
EDIT: op updated - give it a try
Sent from my A500 using Tapatalk 2
awesome, thank you!
Sent from my MB860 using xda premium
stokehall said:
What do you mean by install on sdcard and is that internal or external sd? And does Aroma make any difference
many thanks Simon
EDIT : Im an idiot it means install to the phone, the rom you want to have booting from sdcard.
Click to expand...
Click to collapse
not an idiot bud. I'll clarify in op
Alright, I'm going back in! I'm going to start from scratch...format external sd and repartion.....the works!
I got Nottachtrix set up perfect and doing a nandroid of it right now. Hopefully my next post will be about success!!
Thanks OP for updating the instructions......Here we go!!
I had no errors this time, and it still didn't work? How big is your boot.img after you extract it and repack it? Mine is 2.9mb,,is that right (nottachtrix)?
also, my other question is....when you make the partitions on the sdcard, are you making them primary or logical (I did primary)? everything was ext3 when I mounted it...and that's what I made the partitions.
Also, in mini partition tool when you create them...how are you naming them? I'm just naming them, system, cache, and data?
I used aokpbc 35.1 for the internal rom and just copied the boot.img into the boot folder.
Also, the original boot.img that gets extracted from nottachtrix is 8mb in size. But after making the edits with notepad++ and saving, then repacking in cygwin...it is only 2.9mb?
This is frustrating because it takes awhile to partition the sdcard and then copy everything over in adb shell.
Also, after doing the whole boot.img thing, and then doing moto-fastboot boot boot_new.img
it boots into nottachtrix, but I'm already in nottachtrix. How can I tell if I booted from the sdcard?
Sorry for all these questions, I really want to get this working! It's more a matter of just not giving up now...lol!
Anybody else get this to work on windows?
Thanks!
95rr900 said:
I had no errors this time, and it still didn't work? How big is your boot.img after you extract it and repack it? Mine is 2.9mb,,is that right (nottachtrix)?
also, my other question is....when you make the partitions on the sdcard, are you making them primary or logical (I did primary)? everything was ext3 when I mounted it...and that's what I made the partitions.
Also, in mini partition tool when you create them...how are you naming them? I'm just naming them, system, cache, and data?
I used aokpbc 35.1 for the internal rom and just copied the boot.img into the boot folder.
Also, the original boot.img that gets extracted from nottachtrix is 8mb in size. But after making the edits with notepad++ and saving, then repacking in cygwin...it is only 2.9mb?
This is frustrating because it takes awhile to partition the sdcard and then copy everything over in adb shell.
Also, after doing the whole boot.img thing, and then doing moto-fastboot boot boot_new.img
it boots into nottachtrix, but I'm already in nottachtrix. How can I tell if I booted from the sdcard?
Sorry for all these questions, I really want to get this working! It's more a matter of just not giving up now...lol!
Anybody else get this to work on windows?
Thanks!
Click to expand...
Click to collapse
the difference in sizes is okay. The orginal boot.img contains the kernel whereas the new boot.img only contains the ramdisk. my original is 8 mb and repacked is 2.8
if you ran fast-boot boot boot_new.img and it booted you're in your sd rom. from adb shell run mount and you'll see that system is mounted under /dev/block/mmcblk1p2. This is your sd card partition, internal is mmcblk0p12.
sd card partition naming is okay as that is exactly how i named mine. Make them primary.
Don't worry about asking questions, were both learning
I'm reaching here, but I wonder if it has something to do with how the internal and external sdcard are. I run aokpcb, but I flip flop the cards, so external is emmc and internal is sdcard.
Do you think that might be an issue?
Although, I did do a clean install of aokpbc with stock settings, still a no go.
I'll have to give it another try, I just don't wanna mess up my new 32gb sdcard!
I have to be close to getting this to work, this last time I made it all the way to using script manager to boot into the other rom...but it doesn't get past the splash screen,,,then loops.
anyway, thanks for your help...really!!
I don't anderstand....
May be wrong section, but...
Why don't use Nandroid backup files ?
Look in these directory :
/sdcard/clockworkmod/backup/<backupdatesave>
You have yours :
- boot.img
- system.etx4.tar
- data.ext3.tar
- cache.ext3.tar
...
all you need here.
May i'm wrong, but do a nandroid after install CM7, nottachtrix4G, CM9, etc...
A use Boot.img for multi boot
You can use "Boot Manager" too... http://forum.xda-developers.com/showthread.php?t=1191014
To create ".img" file, you can use this proc (use CWM program) :
su
mkyaffs2image /system system.img &
while [ `pidof mkyaffs2image` ]; do
echo -n "."
sleep 2
done
Create "system.img" file...
Same for
/data
/cache
Boot
...
95rr900 said:
I'm reaching here, but I wonder if it has something to do with how the internal and external sdcard are. I run aokpcb, but I flip flop the cards, so external is emmc and internal is sdcard.
Do you think that might be an issue?
Although, I did do a clean install of aokpbc with stock settings, still a no go.
I'll have to give it another try, I just don't wanna mess up my new 32gb sdcard!
I have to be close to getting this to work, this last time I made it all the way to using script manager to boot into the other rom...but it doesn't get past the splash screen,,,then loops.
anyway, thanks for your help...really!!
Click to expand...
Click to collapse
if its looping its so ething to do with your boot.img. tinker with it til you get it right. remember if you get that far and it doesnt boot dont start over. just flash the working boot image, meaning the one from the rom you just left and then try editing the broken boot.img
delewer said:
I don't anderstand....
May be wrong section, but...
Why don't use Nandroid backup files ?
Look in these directory :
/sdcard/clockworkmod/backup/<backupdatesave>
You have yours :
- boot.img
- system.etx4.tar
- data.ext3.tar
- cache.ext3.tar
...
all you need here.
May i'm wrong, but do a nandroid after install CM7, nottachtrix4G, CM9, etc...
A use Boot.img for multi boot
You can use "Boot Manager" too... http://forum.xda-developers.com/showthread.php?t=1191014
To create ".img" file, you can use this proc (use CWM program) :
su
mkyaffs2image /system system.img &
while [ `pidof mkyaffs2image` ]; do
echo -n "."
sleep 2
done
Create "system.img" file...
Same for
/data
/cache
Boot
...
Click to expand...
Click to collapse
give that a shot and see if it works
My partitions are all ext3, but in the boot.img it says mount ext4? Do i change it to ext3 or leave it ext4?
Also do you mind posting a video tutorial?
hatefuel19 said:
adb shell
~ #mount /cache
~ #mount /system
~ #mount /data
~ #mount
adb shell
PATIENCE IS KEY FOR NEXT STEPS
~ # dd if=/dev/block/mmcblk0p12 of=/dev/block/mmcblk1p2 bs=1M
655360+0 records in
655360+0 records out
335544320 bytes (320.0MB) copied, 115.626214 seconds, 2.8MB/s
~ # dd if=dev/block/mmcblk0p15 of=/dev/block/mmcblk1p3 bs=1M
dd if=dev/block/mmcblk0p15 of=/dev/block/mmcblk1p3 bs=1M
640+0 records in
640+0 records out
671088640 bytes (640.0MB) copied, 206.557368 seconds, 3.1MB/s
~ # dd if=/dev/block/mmcblk0p16 of=/dev/block/mmcblk1p4 bs=1M
dd if=/dev/block/mmcblk0p16 of=/dev/block/mmcblk1p4 bs=1M
2048+0 records in
2048+0 records out
2147483648 bytes (2.0GB) copied, 658.327418 seconds, 3.1MB/s
Click to expand...
Click to collapse
ADB was unable to mount cache
Then when i changed the block/mmcblk0p16 , i was told it was unable to (Not Enough space)
I am very much a noob with this, just determined not to go without dual boot!
I have a problem. I have try to resize the partition using nvflash. I have use guide from modaco and also the preconfigured files. The problem is that /system is always at ~360mb (stock size). All other partitions are resized propertly.
Any help?
doctoralex said:
I have a problem. I have try to resize the partition using nvflash. I have use guide from modaco and also the preconfigured files. The problem is that /system is always at ~360mb (stock size). All other partitions are resized propertly.
Any help?
Click to expand...
Click to collapse
I'm facing the same problem. I think I know what the problem is but I cannot solve it!
I currently have installed Stefan 28G ics rom (2nd edition) and my goal is to add about 100mb to the system partition, reducing internal /sdcard.
If I use fdisk command from adb shell I find out that the partion IS actually resized, but the file system on it isn't!!
So: partition now is 650Mb, but file system on it is 550Mb!
That's because nvflash simply makes a dd of the system.img (which has the old partition size) to the partition so in my opinion there are two solutions:
a) open system.img in a linux environment, add some stuff to reach 650Mb on it and repack it with the new size
b) backup system data, formata the partition (which is already resized) to get 650Mb file system and then restore your system data
I think that all "resizing guide" doesn't talk about this second step because in that case the system.img has always the right size.
Any ideas?
Raffaele80 said:
I'm facing the same problem. I think I know what the problem is but I cannot solve it!
I currently have installed Stefan 28G ics rom (2nd edition) and my goal is to add about 100mb to the system partition, reducing internal /sdcard.
If I use fdisk command from adb shell I find out that the partion IS actually resized, but the file system on it isn't!!
So: partition now is 650Mb, but file system on it is 550Mb!
That's because nvflash simply makes a dd of the system.img (which has the old partition size) to the partition so in my opinion there are two solutions:
a) open system.img in a linux environment, add some stuff to reach 650Mb on it and repack it with the new size
b) backup system data, formata the partition (which is already resized) to get 650Mb file system and then restore your system data
I think that all "resizing guide" doesn't talk about this second step because in that case the system.img has always the right size.
Any ideas?
Click to expand...
Click to collapse
I solved my problem!
As explained before I have just added some stuff to the system.img file and then resized the file system:
dd if=/dev/zero bs=4096 count=35328 >> system.img
e2fsck -f system.img
resize2fs system.img
PS: bs and count depend on the partition size that you have set before in the .cfg file
Then NVFlashing again solve the problem!
doctoralex said:
I have a problem. I have try to resize the partition using nvflash. I have use guide from modaco and also the preconfigured files. The problem is that /system is always at ~360mb (stock size). All other partitions are resized propertly.
Any help?
Click to expand...
Click to collapse
Backup your rom with cwm.
Format /system in cwm.
Restore your cwm backup.
Sent from my LG-P990 using xda app-developers app
Hello,
I'm quite new in android development, so sorry for dumb question.
I have new GT-S6102 (because of dualsim setup) and I'd be quite happy with the stock firmware (S6102XXMA2) if it wasn't of the 160M memory. What I'm trying to do is to modify init.rc in bootimage to mount /data on 4G second partition of my SDCard instead of 160M /dev/stl11.
I'm using a Ubuntu 12.04 machine for my experiments.
I've copied /dev/block/bml7 from my phone using ADB, extracted it using abootimg.
First (and I hope that main) trouble is that when I try to update the boot.img (abootimg -u boot.img -r initrd.img), even without modifying the ramdisk, the resulting image has few different bytes near the beginning of the file. Anyway when I flashed it back to phone, it booted normally.
Then I unpacked the ramdisk (using steps from here) and modified init.rc:
Code:
mount ext4 /dev/block/mmcblk0p2 /data nosuid nodev crypt check=no
# mount rfs /dev/stl11 /data nosuid nodev crypt check=no
I have a 32G uSD card with 28G FAT and 4G EXT4 primary partitions.
Then I've repacked it, made new boot.img, flashed with ODIN and it made a nice bootloop with Samsung bootanimation without usual sound.
What am I doing wrong?
Is this modification even possible?
Thanks for advice
P.S.
I've tried to extract the boot.img from S6102XXMA3_S6102DBTMA1_S6102XXMA2_HOME.tar.md5, but 7zip on Windows and TAR on linux complain that it isn't valid archive.
jelinek.01 said:
Hello,
I'm quite new in android development, so sorry for dumb question.
I have new GT-S6102 (because of dualsim setup) and I'd be quite happy with the stock firmware (S6102XXMA2) if it wasn't of the 160M memory. What I'm trying to do is to modify init.rc in bootimage to mount /data on 4G second partition of my SDCard instead of 160M /dev/stl11.
I'm using a Ubuntu 12.04 machine for my experiments.
I've copied /dev/block/bml7 from my phone using ADB, extracted it using abootimg.
First (and I hope that main) trouble is that when I try to update the boot.img (abootimg -u boot.img -r initrd.img), even without modifying the ramdisk, the resulting image has few different bytes near the beginning of the file. Anyway when I flashed it back to phone, it booted normally.
Then I unpacked the ramdisk (using steps from here) and modified init.rc:
Code:
mount ext4 /dev/block/mmcblk0p2 /data nosuid nodev crypt check=no
# mount rfs /dev/stl11 /data nosuid nodev crypt check=no
I have a 32G uSD card with 28G FAT and 4G EXT4 primary partitions.
Then I've repacked it, made new boot.img, flashed with ODIN and it made a nice bootloop with Samsung bootanimation without usual sound.
What am I doing wrong?
Is this modification even possible?
Thanks for advice
P.S.
I've tried to extract the boot.img from S6102XXMA3_S6102DBTMA1_S6102XXMA2_HOME.tar.md5, but 7zip on Windows and TAR on linux complain that it isn't valid archive.
Click to expand...
Click to collapse
OK, so it seems that I´ve managed to work it out at last.
The unpacking and repacking of bootimage was all right, trouble was in updating only the init.rc and probably using ext4. What I have done:
I replaced all mentions of mounting /dev/stl11 on /data by mounting /dev/block/mmcblk0p2 (that was in files fota.rc, init.rc, init.charge.rc, res/recovery.fstab). In res/recovery.fstab I also changed formatting type from rfs16 to rfs32 so it supports my 4.5G partition.
Then I flashed the bootimg in my phone and formatted the data partition in recovery (that was the only way to make it rfs I've found).
Maybe it would all work with changing the format and mount type to ext4, but I hoped for as little modification as possible.
Now it reports 4.25GB free space after all my apps are installed, hurray .
I have just to remember to never boot it up without SDcard inserted. Maybe it would work as a possibility to borrow the phone to somebody with another card.
The boot.img came from S6102XXMA3_S6102DBTMA1_S6102XXMA2_HOME.tar.md5, if someone wants to try it, it is here . It probably wouldn't touch the original /data partition, so it might be possible to try it and undo it by flashing original boot.img. It just requires to have a second primary partition on SDcard and formatting it in recovery before first boot.
i didnt know to do that boot "compiling" like u did, quite good for you, im using cronmod int2ext , i have 850mb internal. i use 'pimp my rom' to get init.d support.