just wondering if im doing something wrong? got NV installed with all 3 partitions and I had 77mb of internal mem. when I install new apps it takes away mem, am I doing something wrong, did I not config something right? I have read that apps2sd are automatic and to do nothing or it will break the system. dont mind the 77mb but would like to have my apps on my sd. any help would be great.
Do you have ext3? Drizzy expressly says you need it. So I assume if you only have ext2 there might be probs with your a2sd.
If that's not it. Did you follow all of these steps before flashing?...
This is how I installed without any problems:
: rename to update.zip
: place in the root of sd card
: shut off device
: boot into recovery
: wipe
: go to console and hit enter
(enter)
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# cd /system/sd
# rm -rf /system/sd/*
# reboot recovery
: now wipe again
: repair ext system
: flash
Enjoy!!
"DO NOT RUN ANY OTHER APPS TO SD IT WILL BREAK YOUR SYSTEM"
JUST EXT3 & LINUX-SWAP 32MB
kree said:
just wondering if im doing something wrong? got NV installed with all 3 partitions and I had 77mb of internal mem. when I install new apps it takes away mem, am I doing something wrong, did I not config something right? I have read that apps2sd are automatic and to do nothing or it will break the system. dont mind the 77mb but would like to have my apps on my sd. any help would be great.
Click to expand...
Click to collapse
your apps are going to the sd..your dalvik-cache is not
yup. checked thru the the console that in fact I do have an ext3 partition. I went thru an infinate loop with out it, also followed all the steps as best as an old newb could, I mean Im not new to flashing roms coming from the herald and wing, but concidering ow these android roms are becoming like full linux distro installs its getting a little hard to keep up, but still willing to try. gonna look up the dav thing to see where that leads me. definately an adventure! thanks!
Hi, i try to flash Cyan's new rom v4.0.1, but i keep getting this error message in my recover console:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
After trying unsuccesfully to flash the rom, my sdcard can no longer be seen in my phone and it became write-protected, unable to move files into the sdcard. Appreciate your help....
Edit: Yeah solved this menacing but simple problem which i found out is my sd card fault. Since i couldn't access sdparted in the recovery console, i had to use Ubuntu to partition my sd card again. Sighs... now i have to replace everything back into phone. Thanks anyways for those who gave advice.
is your sdcard formatted to fat32? because /dev/block/mmcblk0p1 or /dev/block/mmcblk0 is referencing your first partition or your sdcard respectively.
you dont flash a rom in consol
you flash it from the recovery screen. you probably CAN flash it from consol, but its much easier to flash from the recovery screen. what recovery image do you have?
david1171 said:
is your sdcard formatted to fat32? because /dev/block/mmcblk0p1 or /dev/block/mmcblk0 is referencing your first partition or your sdcard respectively.
Click to expand...
Click to collapse
yes my sdcard is fat32(1st partition) and my 2nd partition is ext3 whilst the last is a linux-swap partition...
oshizzle1991 said:
you flash it from the recovery screen. you probably CAN flash it from consol, but its much easier to flash from the recovery screen. what recovery image do you have?
Click to expand...
Click to collapse
Using Cyan's Recover 1.4. How do you flash from the console? commands?
Scholesville said:
Using Cyan's Recover 1.4. How do you flash from the console? commands?
Click to expand...
Click to collapse
Have you tried using the CM Updater?
Scholesville said:
yes my sdcard is fat32 and my 1st partition is ext3.
Click to expand...
Click to collapse
Well I've Always had the best luck with my partitions in order as follows Fat32-Ext3-Linux-Swap(if you use it)
And if you still have problems this is what I do
Well I re-downloaded the update. and did this.
This is how I installed without any problems:
: rename to update.zip
: place in the root of sd card
: shut off device
: boot into recovery
: wipe (alt w)
: go to console (alt x) and hit enter
(enter)
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# cd /system/sd
# rm -rf /system/sd/*
# reboot recovery
: now wipe again (alt w)
: run a filesystem check from the menu. If it tells you to run it manually,
drop to a console (alt+x) and run "e2fsck /dev/block/mmcblk0p2".
: flash
Enjoy!!
Hope this helps!!!
yourtravelboy said:
Well I've Always had the best luck with my partitions in order as follows Fat32-Ext3-Linux-Swap(if you use it)
And if you still have problems this is what I do
Well I re-downloaded the update. and did this.
This is how I installed without any problems:
: rename to update.zip
: place in the root of sd card
: shut off device
: boot into recovery
: wipe (alt w)
: go to console (alt x) and hit enter
(enter)
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# cd /system/sd
Hope this helps!!!
Click to expand...
Click to collapse
The problem is i can't even mount mount my 2nd partition, and everytime i write the command > # mount -o rw /dev/block/mmcblk0p2 /system/sd < , it justs says no such file or directory found.
I also can't go into parted in the recovery console so the now the problem is i can't even reformat my card. I'm going to try Ubuntu and reformat my card and partition it again. Sighs...
please, can you tell me how did you solved it, did you use ubuntu to reformat the sdcard? thanks in advance..
q2box said:
please, can you tell me how did you solved it, did you use ubuntu to reformat the sdcard? thanks in advance..
Click to expand...
Click to collapse
Yes, since i was not able to access parted in the recovery console, my only choice was to use Ubuntu: Partition Editor. When i diagnose my sdcard, i manage to format only my ext3 partition so my fat32 remain unchanged. You need to go download Ubuntu OS, then try to install or LiveCD the Ubuntu. There is a thread under android development which will guide you on how to do this...
I am using the Switchrom script with CY recovery. I have successfully made backups and switched between roms using the script. Now I want to try the new Drizzy Hero rom. To install the rom I will have to wipe the ext3 partition. My question is, If I wipe the ext3 partition, will I loose the script? If yes, can I copy the script in system/sd later on for it to work again?
PS: Before someone posts "search the thread" answer, I tried doing it and couldn't find anything.
Thanks
bole_to said:
I am using the Switchrom script with CY recovery. I have successfully made backups and switched between roms using the script. Now I want to try the new Drizzy Hero rom. To install the rom I will have to wipe the ext3 partition. My question is, If I wipe the ext3 partition, will I loose the script? If yes, can I copy the script in system/sd later on for it to work again?
PS: Before someone posts "search the thread" answer, I tried doing it and couldn't find anything.
Thanks
Click to expand...
Click to collapse
The only thing that is stored on your ext3 partition is your apps. So when you clear that only your apps will get cleared.
supremeteam256 said:
The only thing that is stored on your ext3 partition is your apps. So when you clear that only your apps will get cleared.
Click to expand...
Click to collapse
Thanks man. Wiping now.
To clear this up for other reader who might stumble on this thread, the above comment is not true. If you wipe you ext 2/3 you might end up wiping more stuff than just apps. I realized it the hard way lol. However you can push back switchrom.sh in /system/sd and you will be good to go. The alternate method to do this is to delete just the following folders:
mount /dev/block/mmcblk0p2 /system/sd
rm -rf /system/sd/app*
rm -rf /system/sd/dalv*
bole_to said:
To clear this up for other reader who might stumble on this thread, the above comment is not true. If you wipe you ext 2/3 you might end up wiping more stuff than just apps. I realized it the hard way lol. However you can push back switchrom.sh in /system/sd and you will be good to go. The alternate method to do this is to delete just the following folders:
Code:
mount /dev/block/mmcblk0p2 /system/sd
rm -rf /system/sd/app*
rm -rf /system/sd/dalv*[/QUOTE]
You can do that or you can wipe buy doing this
Code:
mount /system/sd
mount /sdcard
rm -rf /system/sd/*
cp /sdcard/switchrom.sh /system/sd/switchrom.sh
That's how i've been doing it. And I like to do it this way to make sure the my EXT2/3 is completely clean. I've had problems where doing a partial wipe gives me issues. But yes if you wipe your EXT2/3 drive it will get rid of everything (including the switchrom.sh)
Click to expand...
Click to collapse
when you wipe your internal phone memory and ext3 you will lose the script. once you get the rom you flashed up and running again, just repush switchrom.sh and you are good to go again. wiping the ext 3 or the internal memory WILL NOT wipe out your backups. when i use switchrom i dont even wipe all of ext3...
this is what i do... flash a new rom. get it setup the way i want. install all apps and extra settings i want. reboot into recovery, run switchrom.sh and let it do its thing. now when you have created your back up and want to flash a NEW ROM, not one of your backups, wipe internal memory of course but instead of wiping all of ext 3 drop down to recovery console and do the following
Code:
# mount /system/sd
# rm -rf /system/sd/app*
# rm -rf /system/sd/dalv*
this will prepare your ext3 for a new install of a new rom. when you are going back and forth between your backups you do not need to wipe ext3 at all. the script takes care of all of that. if you have any more questions PM me or hit me up on gtalk - palosjr
NOTE- this script is case sensitive as i found out the hard way... when bookmarking and tagging ROMs be sure to use all lowercase. if you use uppercase the script will fail. hope this helps bro.
thanks guys, i got it to work.
Okay i'm sure ive become an annoyance in this section of the forum. I think i may have bricked my phone. This is what i did.
1. Unrooted myself and downgraded to RC29.
2. I formatted my sd card even though it already said fat32
3. Downloaded cyanogen recovery 1.4 image. And Hardspl and renamed it update.zip.
4. I connected to server 23 host in telnet and successfully typed in :
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery cm-recovery-1.4.img
cat cm-recovery-1.4.img > /system/recovery.img
5. The Hardspl part pretty much failed... i renamed it update.zip and downloaded it in recovery but once i hit reboot..it took me to recovery again and said : formatting cache:... and just stayed there. So i hit reboot again and it booted back to homescreen.
6. After this i figured i was rooted so i download cyanogen rom (http://forum.xda-developers.com/showthread.php?t=567610) and put it on my sd card.
7. I went to recovery and downloaded this zip file successfully.
My problem is: i can't get past the g1logo screen. I've tried reinstalling the rom and wiping data a couple times and it wont go past. Am i screwed?
okay nevermind this post i had to go to console and type in
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file to mount my sdcard so im goin back to RC29! may as well go to 1.6 til i can figure something out about rooting this is just ridiculous
kyram04 said:
okay nevermind this post i had to go to console and type in
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file to mount my sdcard so im goin back to RC29! may as well go to 1.6 til i can figure something out about rooting this is just ridiculous
Click to expand...
Click to collapse
anyway heres a website about how to root.....http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
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!