Related
Hi all,
Here are my findings about how to boot android from an SD card, useful for example to test development Android builds without messing your phone. This procedure was inspired by legacy GNU/Linux boot process and then should work on most hardware with a flashable recovery.
########################################
I can't stress enough the fact that this procedure is targeted to experienced user. A good knowledge of linux/android booting process is more than required. This procedure is not meant to be useful to most people given its limitations (no recovery mode, rebuild of boot.img required)
########################################
I won't propose a step by step tutorial as it's better to understand how to do it and adapt the procedure to each need.
Two modifications are required:
1. Declare to mount sd card partitions instead of internal flash volumes. This has to be done in the init.rc script.
For example:
mount yaffs2 [email protected] /system
mount yaffs2 [email protected] /system ro remount
with
mount ext2 /dev/block/mmcblk0p6 /system
2. For some reasons, in the boot process, sd card partitions generally show up later than the mount actions, so it is generally necessary to add a timer in init binary to give to to the kernel to detect sd card partitions before mounting them (adding a sleep(5) after the "A N D R O I D" text in init.c is enough).
Build your special boot.img embedding those two modifications and flash it on the recovery volume of your phone. Now, booting into recovery will launch the system on your sd.
Regards,
I would like to report success on booting the G1 from a system located on sd card (cyanogenmod 4.2.7.1). I will describe the procedure step by steps when every thing is okay.
There is just an issue that you might have encountered during cyanogenmod ROM cooking, all wireless connexions (wifi, BT, GSM) do not work. The same system on flash if okay. I made a diff on boot log messages and the only notable difference is this error :
E/MemoryHeapBase( 83): error opening /dev/pmem_gpu0: Permission denied
E/MemoryHeapBase( 83): error opening /dev/pmem_gpu1: Permission denied
E/MemoryHeapBase( 83): error opening /dev/hw3d: Permission denied
I tried to chmod 0555 /dev/pmem* with no success.... Any idea ?
Although I finally managed to have a usable system, this work is still experimental. Please fell free to test and report success, failures here so I can improve the thing.
Let's see how we can boot a copy of cyanogen ROM 4.2.7.1 located on sd card. The main purpose is to test future ROMs (eclair ?) without messing up your phone...
DISCLAIMER : This procedure is targeted to experienced user. I am not responsible if you loose your data, your phone or your Mom !
Prerequisites are :
- adb and fastboot operationnal on your host computer
- Boot image file boot.img :
http://www28.zippyshare.com/v/19654421/file.html
- files data.cpio.gz, system.cpio.gz (data.cpio.gz and system.cpio.gz are unmodified images of a fresh install of cyanogen ROM that fit the modified boot.img) from :
http://www15.zippyshare.com/v/57489279/file.html
http://www15.zippyshare.com/v/13077582/file.html
1.
Create 3 partitions on sd card. The first one (vfat) is to store your music, videos etc. The second and the third will hold /data and /system. Result shoul look like this :
# fdisk /dev/block/mmcblk0
Command (m for help): p
Disk /dev/block/mmcblk0: 1977 MB, 1977614336 bytes
64 heads, 63 sectors/track, 957 cylinders
Units = cylinders of 4032 * 512 = 2064384 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 864 1741792+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 865 903 78624 83 Linux
/dev/block/mmcblk0p3 904 957 108864 83 Linux
Command (m for help):
2.
Copy data.cpio and system.cpio on the first partition of your sd card.
3.
Connect to your device with adb :
adb shell
4.
Mount mmcblk0p2 on temporary folder and extract user.cpio.gz archive :
mkdir /dev/tmp
mount /dev/block/mmcblk0p2 /dev/tmp
cd /dev/tmp
gunzip -c /sdcard/data.cpio.gz | cpio -i
cd /
umount /dev/tmp
5.
Mount mmcblk0p3 on temporary folder and extract system.cpio.gz archive :
mount /dev/block/mmcblk0p3 /dev/tmp
cd /dev/tmp
gunzip -c /sdcard/system.cpio.gz | cpio -i
cd /
umount /dev/tmp
6.
Reboot the phone in bootloader :
adb reboot bootloader
7.
Boot the phone with custom boot image :
unzip boot.img.zip
fastboot boot boot.img
Reports are welcome !
I haven't tried this, but great idea. Well done.
Maybe a nice additional idea would be a boot-menu style idea. Eg, detect OS on mem card and display a menu of "Internal" or "SD Card"?
I'm on it but as it will imply flashing people's phone, I need more testing and suggestions from experienced hackers. I only own my G1 for 5 days...
I acytually just started a thread about this in the Dream development subforum!
Some suggestions:
-Use a recovery image to boot the ROM on the sd card (look at modifying the CM recovery image) if this is possible. This way, you can boot from sd card when you want to, by booting into recovery image, without interfering with the flashed rom at all. No worries that flashin a new rom will require a reflash of your bootloader. Also, you can use the ROM installed in flash after a reboot without any hassle, which would be very useful when testing a ROM from the SD if it doesn't work very well and you need a working phone.
-Have the /data and /system-partition as folders on the 4th partition on the SD card, or as logical volumes on a primary one. Why?
Well, many people have their sd-cards set up with fat, extX, swap in that order. The partition layout you have described here simply isn't compatible with that, and will require a separate SD card just for this testing (which everyone might not have).
I must say, I think this is a GREAT idea! I so often want to test a few ROMS, but often they don't get the test-time they deserve because I need to swicth back to my working environment for job/uni the day after. This would be a great way to test a ROM thoroughly. And also it would be the best way to give a ROM a quick testdrive. switchroming back and forth is, for all its simplicity, hassle.
Using the recovery is the only way I found at the moment to boot from the sd card and was about to extend cm recovery with a dedicated menu Nevertheless, there will be a limitation with that: it will not be possible to use a different kernel for the system on sd as it will have to use the kernel of the recovery... Anyway, many custom roms around here use cm kernel (even those I saw with eclair) so it is not so problematic I think (tested Eugene373 AOSP20 yesterday). Anyway, it is possible to adapt the recovery with a test kernel...
I think I found a workaround for sd partitionning scheme pb, using bind mounts but I have not tested already. I will work on it this WE.
If I remember correctly you can use the command "reboot recovery" from the recovery shell to reboot again into recovery. It could mean that it is possible to choose what (kernel) to boot after the reboot. Even cyanogenmod has made quite a few changes to the kernel since the recovery image came out, and I think it would not be a very good solution to use the same kernel as the recovery image for all ROMs loaded via SD. (Especially the Hero ones won't work at all, I'm afraid.
It could also be possible maybe, to tweak the built-in bootloader into booting form either SD-card or from the internal flash? It already has the possibility to boot different things on different keypresses (home for recovery mode, and camera for fastboot). I have (again) no idea of its capabilities for reading anything off of the sd card, though.
I get your point naguz . I am not satisfied either with the solution of using the recovery kernel to boot the system on sd. I found that it adds quite much complexity to the init process: I tweaked the recovery executable to add an entry to boot from sd but I faced troubles in services startup and pre-init definitions. I think that the solution of using the recovery menu to choose to boot from sd have to be abandoned as it will require heavy additional changes to the init.rc scripts of the second system and will break its advanced features.
The ideal solution (as you suggested) would be to tweak the bootloader to boot natively from the sd card but unfortunately, we do not have the sources of the SPL (tell me if I am wrong) so it is definitely not possible.
The remaining solution is to use the recovery partition to flash the boot image of the second system. I works well, just press the home key and the second system boots ! The drawback is that you do not have recovery any more... Personnaly, I don't find that so problematic as I is still possible to boot a recovery image with fastboot when needed, so I think I will stick to this solution. I somebody have another solution, I am ok to investigate...
Aha, it makes sense that booting the sd directly from recovery mode would mess something up. I would think some of the same problems would be faced when booting the kernel from the recovery partiotion, doesn't it look like a different device to the kernel? Well, if it works, it works.
Regarding the source of the SPL, I have no idea, but I know hyakuro (a (former?) user here) has released a modified one. Trying to get in touch with him
As for the latest method: Is the recovery partiotion big enough to hold both the recovery image AND the kernel? If so, one could maybe have both. Maybe make a new "recovery image" that can either boot from sd or boot recovery image? Just throwing out ideas here.
Personally I don't see the big problem with not having a recovery image, as I would (in a dual-boot scenario) already have another, working install on the flash that I could use if the one booted from sd wasn't good enough. Re-flashing the recovery image could also be done from the working ROM in flash, for those without the SDK tools.
I think, however, that quite a few people will object to not having a recovery image.
Btw, was your latest working test done with one (4th) partition on the sd card for loading the ROM from SD? If so, new instructions please. I'd like to give it a try.
I think that it is technically impossible to boot directly from the sd, even with the sources of the SPL as drivers are required to drive the sd that can not be included in a SPL. It is the same issue on PC with PCMCIA network cards for instance. IPL+SPL has to be seen more or less like a simple BIOS...
The recovery partition size is not a matter her. The problem is the lack of control over what has to be booted as the only action we can make in the SPL is the HOME key to choose a regular boot or a recovery boot (the system on SD here). I think I have a good knowledge now of the boot process and I think we can not got further than that, despitely...
I am now trying to have /data and /system on the same partition, mount them on /mnt and bind mount each directory on /system and /data but with no succes . investigating....
Okay, bind mounting was a dumb idea of mine. The solution is to create an extended partition with 2 logical drives in it, so partitions are:
[1-3] FAT and/or EXTX and/or swap as needed (I have personnaly just one partition here)
4 extended
5 ext2 for /data
6 ext2 for /system
Now its time to bake a boot.img with the kernel of the system on the sd card + the ramdisk. I do not explain how to do that, google knows :
1.
In the ramdisk image, put my modified init program attached hereater
2.
In the init.rc script, change the lines that mount /data and /system :
mount yaffs2 [email protected] /system
mount yaffs2 [email protected] /system ro remount
with
mount ext2 /dev/block/mmcblk0p6 /system
and
mount yaffs2 [email protected] /data nosuid nodev
with
mount ext2 /dev/block/mmcblk0p5 /data
Flash boot.img on the recovery and reboot in recovery... That's all.
Jahrome,
Trying the idea on the HTC has a subtle difference. So I'm curious what change you put in the /init process.
Lets say the image one wants to use is the 'eclair' branch. This branch uses vold, so the block device, such as '/dev/block/mmcblk0p#', does not appear to be created until the vold service is started, which is after the init.rc mount operations. So the mount proposed does not work.
Curious what changes you made to the init process that might give me some ideas of what might be the simplest change. It seems that there is a relatively easy solution, that I don't yet see.
Ideas (or additional questions to clarrify) appreciated...
Hi Dale !
On which HTC are you trying the trick ?
First your trouble is not related to eclair as I successfully booted eclair on my G1 with this trick. You need to add a timeout in init so as it waits for the kernel to detect sd card partitions (need to recompile init, or use my recompiled init).
Vold has nothing to do at this point
Hope this helps
Init Delay for SDisk
Thanks for the reply. That's what I needed, it seems so ungraceful.
I thought vold was enabling something to make the kernel's discovery of the SD partitions. It is "by coincidence" that the log of the vold occured shortly before the adding of the block-device event. My apologies for not recognizing the coincidence of the log entries.
I had hoped the solution was a bit more "graceful", though I can't say what that would be or why a sleep is "ungraceful". I would like a "mount retry for n-seconds" option in the init.rc, that would be slick. Nonetheless I will add in a sleep-spin-check for a few seconds.
For the record, we are discussing the change to:
android-source: .../system/core/init/init.c
code-routine: main()
code-location: Somewhere after the "A N D R O I D" text
code-change: add in a sleep spin-check of some sort
I appreciate the comment that all we need is just a sleep. I think this completes the thread?!
Most interesting...
This is something akin to how I am using my company's Android solution for the Beagle Board...
In that environment, the entire kernel and rootfs are located on a SD/MMC card. The environment variables and boot script are stored in the NAND chip
through a "setenv" command. The U-boot monitor on the hardware defaults to run the boot script unless there is any user interaction. This image can then be converted into a typical distribution that can be flashed and ran without the SD card...
I have wondered about the implementation of this approach on my G1, but I have not had time to test it out. It is good to see that there are others that are interested in this as well...
I will be following this thread and will try to help in any way if I can... meaning if I can get some free time...
If you are interested in our Beagle Board solution, it is open source and can be found by a simple Google search using "Android rowboat"...
L8R...
very easy fix.
rename the /init to /init.android (or whatever you like)
create an init script. have it prompt on boot too boot from sd or internal. symlink the init.rc from /system. That way you only need one boot.img for multiple builds. We've been doing this a really long time on the android on vogue project. My development phone is simple, I hold down the menu button if I want to boot from the sdcard otherwise it boots from the internal.
Oh and don't worry about this.
jahrome said:
log messages and the only notable difference is this error :
E/MemoryHeapBase( 83): error opening /dev/pmem_gpu0: Permission denied
E/MemoryHeapBase( 83): error opening /dev/pmem_gpu1: Permission denied
E/MemoryHeapBase( 83): error opening /dev/hw3d: Permission denied
Click to expand...
Click to collapse
That's just that you don't have HW3D enabled in your kernel. It's important to note that if you're trying to use multiple builds that eclair with 3d and donut use different kernels.
Exactly the vogue and kaiser have been doing this for ages. If you want you can also boot ext2 and squashfs images. It's pretty simple stuff.
Anyone have a backup of the files in post #3? I've been trying this solution with files of my own creation (as in: my own cooked boot.img, and data/system files) but it doesn't seem to get past the G1 boot screen (as in: blank screen.) I've also tried the recovery boot solution however it gives me the same reaction. It leads me to believe the problem lies in my boot file.
ok anyone interested in creating a simple step by step manual? and can someone post the files again please?
Hello mate,
I am trying to boot Debian on WF.
My phone has been rooted by now, and i need help regarding mounting the partitioned fs.
Here's what i have on my SD:
1) 950MB ->Fat32.
2) 750MB -> Ext3
3) 150 -> Swap.
Now linux requires a partition to be ext formatted, which i have done by now. But i have no idea on how to mount the ext3 fs on htc wf.
I tried the procedure via recovery mode->partitioning-> mount /sd-ext/ but dint worked.
Would you please tell me how can i mount it by using Ubuntu. I am not a avid windows user and many tutorial relating to apps2sd are based upon windows, which isnt possible for me.
Also, how can i know the directory address of the filesystems i have generated. like, /dev/sd2 etc.
Hey,
I need help with Imilka Gingerbread 0.8, as I don't have 10 posts yet I can't reply in that thread so I have to start a new thread (which is actually .. pretty odd).
I have an EU HTC HD2 and I'm trying to install NAND + CWR, it is my fourth ROM Im using, first NAND, all SDbased androids did work immediatly
Flashed original HTC HD2 ROM
Reformatted SD card FAT32
Used Task 29
Installed radio 2.15.50.14
Installed HSPL 2.08
Installed MAGLDR1.13
Flashed it according to advice 5/170/44 layout
Did every wipe at AD Recovery
Partitioned my 32gb SDcard 1024mb with 0 swap
Installed zip from SDcard
Rebooted
Waiting for about 2 hours at the black screen with green HTC, post says: First boot can take up to 10-20 minutes.
EU users need 5/180/5 CWR system partition and ext2/3/4 partition on sdcard.
TMOUS users need 5/360/5 or more CWR system partition.
ext2/3/4 partition will be made @ AD Recovery partition SD card ?
If not, how can I make this partition, without linux and stuff. Just windows 7.
Or am I doing it in the wrong order?
Just did it all over again
This time with 5/180/5 layout and made ext3 partition using easeus on windows using instead of clockwork thingy.
nope, still doesn't go past the black screen + green HTC
booting for an hour now, nothing
Think I found the problem.
Updated AD recovery to 5.0.2.3 orsomething there was an option show log
and it said creation of EXT2 partition was aborted, so now I put the SD in my card reader and manually formated it ext2. retrying now
Nope, nothing
I can manually mount everything but SD-EXT
show log::
mount: mounting /dev/block/mmcblk0p2 on /sd-ext
failed: invalid argument
Hi the question is in the title.
I got it working on quarx's cm7 RC 1.0(only with directory method), but on WIUI 2.2.3 i get errors.
On startup i get this error:
Internal tests failed!
-Kernel config is not known becouse /proc/config.gz file is not found. /this was present on cm7 too/
Here i click override.
Directory method:
And when i click "Install in chroot directory" it says "Error: Partition is mounted with nodev: Can't remount with nodev!"
Loop method:
Creating and formating the loop finishes fine.
When i click mount loop it says: "Can't mount BLOCK Part: Did you forget to format? I think this ext version is not supported!"
however i'm using the ext2 file format, which is included in the application. In the log i found this line: "MountLoop > Error:mount mounting /dev/block/loop1 on /data/local/mnt/Linux failed: No such device"
I think this is the source of the error. Beside that i didn't found any strange entries in the log.
I managed to get it working.
All i had to do is remount /data with dev option. After that the directory method is working on internal memory. I've also tried to install linux on sdcard, but that fails, because when i try to change the "Chroot point" in the setup i get "Directory is nodev!, not saved", even after remounting /mnt/sdcard with dev option.
Anybody have an idea to fix this?
for me it worked!
..unfortunetly only for debian squeeze :/ would like to get at least ubuntu 10.4.
i had to manually umount my sdcard.
i'm not shure if this was necessary, but i also remounted all devices that where mounted as nodev.
my mountpoint was /data/local/linux
EDIT: *sigh sorry i forgot to say, i'm on atrix,not on defy.. but the point is, that i also get those errors whenever i try to install any ubuntu while debian squeeze works fine.
I have the same problem
Hi!
I have the same problem,I tried all the 3 roms (Wiui,CM,Miui)+the stock with root,but on these roms,the linux installer sends the same message: "Kernel features is not know because the /proc/config.gz file is not found"
I tried to install Ubuntu too with the ubuntu installer app from market ,it didn't work too.
Is there anybody,who use any linux on his/her Defy?
I' sorry for my English.
On CM10 the application named "Complete Linux Installer" is working fine. Unfortunately i'm still not able to use loop method on CM7. If you really need this on your phone you should try CM10.
By the way i would happy to hear about anybody who have a working loop device setup on CM7.
jumika said:
Directory method:
And when i click "Install in chroot directory" it says "Error: Partition is mounted with nodev: Can't remount with nodev!"
Click to expand...
Click to collapse
I may have partially solved this if you haven't already. Here's what I did to install using BLOCK method:
First, used an old HTC Dream that had an Amon RA recovery on it to format the SD card. The recovery has an automated option to make an ext2, 3, or 4 partition + swap on the sdcard. I first made an ext2, then coverted it into ext3, then into ext4. I then put the sdcard back into my main phone. My main phone did not support the Amon RA recovery and that's why I needed to use another phone.
Then I used another app called "Linux Deploy" to see what the ext4's /dev/block was. The app has a menu option called "sysinfo". I think you can also just use that command in Terminal Emulator. Look at the partition sizes carefully. Remember the filesize you used to create your EXT (the swap partition is right under your EXT as well). Use that block device in the Linux Installer setup menu. You shouldn't see the "nodev" anymore.
What happens is that the sdcard itself is usually formatted as FAT32 (vfat) and will always be "nodev". Partition some or all of the space as EXT + SWAP and it will be fine. I've successfully installed to sdcard using this way. Let me know how this works for you or if I need to clarify some things.
hi, i have been trying to get a dual boot with wp7 (hd20 8779) with android jellybean (paranoidandroid) using ext4 on the sd.
i have right now:
magldr v1.13
ext4 recovery nand
partitions:
1st FAT 14gb
2nd EXT4 1gb (made via ext4 recovery)
there is no 'nativesd' folder that i can see on the sd card (to put the jellyb.zip rom in?) and it (ext4 recovery) will not let me install zip from sd (either jellyb.zip rom or dual installer zip. it just says:
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I am also confused about which rom I should go about installing first at this point. wp7 or droid?
---- edit:
ok, i was using the wrong android rom. aokp nativesd worked. booted, tested it, all ok. but then i went to install wp7 and it erased it. wp7 booted, worked. took out sd, hooked sd up to computer, repartitioned to have wp7 ||| fat32 ||| ext4, but then when i put it back into phone and booted to wp7 (to make sure it was still there), it said available storage was entire sd card. so i powered down and tried to boot into android. now android was gone. tried to boot into ext4 recovery and that was gone too.
i am very close now. i just need help partitioning this correctly. i know now that the latest version of minitool will let me partition to ext 4 so that's no problem now. can someone please help me set up my partitions so that i don't lose one installation with another? also, i don't know how to check if something is mmcblk0p2 or how to set it to that. i haven't been able to find any instructions in doing so, just mentions of it across the forums.
please help
Okay.
You probably have WP7 now, right? You've already partitioned the card with xboxmod's CABs, haven't you? If not, please do those two steps before continuing.
Windows Phone 7 wipes entire SD card and creates its own partition every time it's installed or hard reset, and because of that you can't install Android ROM first and then WP7.
After that, just take MiniTool, delete the FAT partition and create two new:
First FAT partition, then on the rest create EXT partition. It should be mmcblk0p2 then, but you want to check it anyway. How to was in that thread:
6. (WP7 users) make sure the EXT4 partition is located @ /dev/block/mmcblk0p2
To check this mount your sd-ext partition in 4EXT recovery and use adb shell or QtADB shell and type df
Click to expand...
Click to collapse
If you don't have ADB yet, please download Android SDK where that tool is included. Or try QtADB, but I haven't used that one.
That instruction translates to:
1. Run 4EXT Recovery
2. Choose Mount... option
3. Mount /sd-ext
4. Run adb shell (type that in CMD when in folder with adb.exe, I hope you can navigate with CMD)
5. Type df and press enter.
Then install the ROM using 4EXT SD Recovery. Nothing complicated, I hope. That's how I've done that at least.
thank you
Spaqin said:
Okay.
You probably have WP7 now, right? You've already partitioned the card with xboxmod's CABs, haven't you? If not, please do those two steps before continuing.
Windows Phone 7 wipes entire SD card and creates its own partition every time it's installed or hard reset, and because of that you can't install Android ROM first and then WP7.
After that, just take MiniTool, delete the FAT partition and create two new:
First FAT partition, then on the rest create EXT partition. It should be mmcblk0p2 then, but you want to check it anyway. How to was in that thread:
If you don't have ADB yet, please download Android SDK where that tool is included. Or try QtADB, but I haven't used that one.
That instruction translates to:
1. Run 4EXT Recovery
2. Choose Mount... option
3. Mount /sd-ext
4. Run adb shell (type that in CMD when in folder with adb.exe, I hope you can navigate with CMD)
5. Type df and press enter.
Then install the ROM using 4EXT SD Recovery. Nothing complicated, I hope. That's how I've done that at least.
Click to expand...
Click to collapse
wp7 is installed. after several searches, i'm not seeing the cab files you're talking about. the current partition structure is 200mb fat ||| 14.67gb 'other' ||| I saw that part in the thread with mmcblk0p2, but I had no idea how to specify that when I made the partition or how to check it. Thank you. Yes, I have the Android SDK (had no idea that's where to find ADB) Thanks for elaborating that for me. I am going to do all this right now!
--- edit
how do i check to make sure its mmcblk0p2?
if i just repartition in minitool everything, do i still need the xboxmod cab files i can't find?
--- edit
i repartitioned with minitool and this is what i have now:
1st) 7.88mb (free) 0 (used) unallocated logical
2nd) 5.81gb (free) 11.65mb (used?) fat32 logical
3rd) 1.46gb (free) 101.80mb (used?) ext4 primary
4th) 7.67gb (free) 7.67gb (used) unformatted primary
now, i'm going to install ext4recovery nand and try to install android, is this correct?
--- edit
i'm not seeing adb anywhere. In android sdk tools i have two shortcuts: AVD Manager and SDK Manager. I don't see adb in either. I'm loaded into EXT4 Recovery Nand now.
--- edit
After looking in the android sdk program directory in windows i found adb-has-moved.txt It says:
Code:
The adb tool has moved to platform-tools/
If you don't see this directory in your SDK,
launch the SDK and AVD Manager (execute the android tool)
and install "Android SDK Platform-tools"
Please also update your PATH environment variable to
include the platform-tools/ directory, so you can
execute adb from any location.
--- edit
when i get this completely finished, I'm going to do it again to another phone, and I'm going to make a COMPLETE step by step guide from start to finish for noobies like me and post it.
---- edit
after going to a cmd prompt and navigating to the 'platform-tools' directory and typing adb, press enter, then typing 'df', press enter, i get this error:
Code:
'df' is not recognized as an internal or external command, operable program or batch file.
--- edit
i'm attaching a screenshot, i used the command 'adb shell' then enter then the command 'df'. although i have no idea if this is doing this to my sd card on my phone which has the sd-ext mounted.
Oh, you resized WP7 like that (with partitioning tool), okay, it's fine too. You will have to hardreset though. No need to use CABs then.
ADB is in C:\android-sdk-windows\platform-tools if you've downloaded it (platform tools) from that installer/updater of course.
Browse there with CMD and use adb shell.
Please remember to set both FAT and EXT4 partitions primary, else it won't work.
After you check if the partition is in that mmc02 thing, you can install the ROM with the recovery.
thank you
Spaqin said:
Oh, you resized WP7 like that (with partitioning tool), okay, it's fine too. You will have to hardreset though. No need to use CABs then.
ADB is in C:\android-sdk-windows\platform-tools if you've downloaded it (platform tools) from that installer/updater of course.
Browse there with CMD and use adb shell.
Please remember to set both FAT and EXT4 partitions primary, else it won't work.
After you check if the partition is in that mmc02 thing, you can install the ROM with the recovery.
Click to expand...
Click to collapse
ok i'm attaching a screenshot of my partitions in minitool. i made the fat primary as well. now i'm going to copy over the aokp jellybean rom and try to install it. fingers crossed! also, i hard reset wp7 when i first installed it. i'm afraid if i do it now, it will undo all the partitioning steps i've taken after that. is this correct?
---- edit
ok, something went wrong, because after i installed android from ext4 recovery nand, i powered down, booted into magldr 1.13 and selected '1. Boot WPH' and it said: 'WPH not installed.' aaaaaaahhhhhh!!!! lol
any ideas where i might have gone wrong?
---- edit
btw, when i booted into android (1st boot) i checked the space, and it said the 5.81gb or whatever it was, so i think the partitions are intact. could this be a 'uselast24NAND' issue? i don't think i did that when i installed wp7, i couldn't remember when i was supposed to do that. ah geeeeeeeez
noobinius said:
ok i'm attaching a screenshot of my partitions in minitool. i made the fat primary as well. now i'm going to copy over the aokp jellybean rom and try to install it. fingers crossed! also, i hard reset wp7 when i first installed it. i'm afraid if i do it now, it will undo all the partitioning steps i've taken after that. is this correct?
Click to expand...
Click to collapse
First check that WP7 still boots (if you've followed most of the tutorial for the old dual boot 1 sd card method you should be fine, otherwise you'll have to start over), and don't use 4ext nand recovery (doubt it'll run anyway), you need the 4ext SD version.
Just follow this , with the difference being having 3 partitions at the end ( FAT32|||EXT4|||WP7) then install via a SD ported recovery
thank you
HypoTurtle said:
First check that WP7 still boots (if you've followed most of the tutorial for the old dual boot 1 sd card method you should be fine, otherwise you'll have to start over), and don't use 4ext nand recovery (doubt it'll run anyway), you need the 4ext SD version.
Click to expand...
Click to collapse
ok, thanks hypoturtle. ok, i am going to take a little break, then find the sd version of 4ext, then i'm going to task29 this monster with hd2 toolkit and completely start over. i will update this thread with what happens and what i did. when i'm done i plan to make a complete step by step guide with links and all so there will be something with ALL the information and links in one place, placing all credit where it is due to the original developers. i am not a developer.
Yeah, that was the problem. You can't use NAND recoveries when on WP7 because they will format NAND and prepare partitions for Android, deleting WP7. For that you need SD Recovery ported by Xylo (available in NativeSD thread). After WP7 is installed, you don't even touch anything that's NAND related because it will break everything.
Check this video tut http://forum.xda-developers.com/showthread.php?t=944288
1. install wp7
2 make android partition as in vid.
You should have after the above.
<50% of sd card volume as FAT32 on first partition (primary)
>50% of volume unformatted (WP7) on second (primary)
Then you can create ext4 partition as second partition (also set as primary), I would use minitool again to shrink your FAT partition (but use 4ext recovery sd to format it see http://forum.xda-developers.com/showpost.php?p=31247925&postcount=3464 and the post before it)
So you have 3 partitions 1. fat android 2. ext4 3. wp7
I have not tried a smaller wp7 partition than 50%, don't know if it would work but 96edwy has suggested not to do this in vid.
thank you
thank you guys for your help. i have got it working and have made a step by step guide as i did it. just one problem, and i reaaaaallly hope its not a big problem. but in android it says no sd card. i need to know how to show whatever explorer program i use in android to look at the fat32 partition. anyone know?
i also need to know how to make wp7 see the fat32 partition that will have all the media files on it. anyone?
as soon as i get this information, i will post the guide. but i don't want to post it if there is something wrong (android and windows not reading the fat32 parition).
other than that both operating systems are still there and android is running from ext4 from folder nativesd!!!
noobinius said:
thank you guys for your help. i have got it working and have made a step by step guide as i did it. just one problem, and i reaaaaallly hope its not a big problem. but in android it says no sd card. i need to know how to show whatever explorer program i use in android to look at the fat32 partition. anyone know?
i also need to know how to make wp7 see the fat32 partition that will have all the media files on it. anyone?
as soon as i get this information, i will post the guide. but i don't want to post it if there is something wrong (android and windows not reading the fat32 parition).
other than that both operating systems are still there and android is running from ext4 from folder nativesd!!!
Click to expand...
Click to collapse
Check that all the partitions are set as primary, that's the only thing I can think of.
HypoTurtle said:
Check that all the partitions are set as primary, that's the only thing I can think of.
Click to expand...
Click to collapse
well, i just checked it. i'm attaching the screenshot that shows the partitions. i'm a little scared to change the last one (the wp7 one) to primary for fear of messing it all up again. also, that shouldn't effect androids view of the fat32 which is set to primary right?
noobinius said:
well, i just checked it. i'm attaching the screenshot that shows the partitions. i'm a little scared to change the last one (the wp7 one) to primary for fear of messing it all up again. also, that shouldn't effect androids view of the fat32 which is set to primary right?
Click to expand...
Click to collapse
Can't imagine that would cause the issue, you have them layed out as Fat32 | EXT4 | Unallocated right? Have a look at df again see if vold/179:1 appears, have attached mine from PA
thank you!
HypoTurtle said:
Can't imagine that would cause the issue, you have them layed out as Fat32 | EXT4 | Unallocated right? Have a look at df again see if vold/179:1 appears, have attached mine from PA
Click to expand...
Click to collapse
so thats how you see if it's called mmcblk0p2 or not.... finally. i never used it to set these up. is it too late? i don't even know how to get adb on my phone like you did, and i tried running adb shell from my computer but it keeps saying error: device not found.
how do i get it running on my phone as you did to check?
noobinius said:
so thats how you see if it's called mmcblk0p2 or not.... finally. i never used it to set these up. is it too late? i don't even know how to get adb on my phone like you did, and i tried running adb shell from my computer but it keeps saying error: device not found.
how do i get it running on my phone as you did to check?
Click to expand...
Click to collapse
Use terminal emulator, type su to get to shell then df (or anyother busybox/adb shell command)
thank you!
HypoTurtle said:
Use terminal emulator, type su to get to shell then df (or anyother busybox/adb shell command)
Click to expand...
Click to collapse
ahh, great. well, i got there did it, no 179 error or any other error. i tried taking a screenshot with volume down + power key, but it doesn't seem to want to do it, maybe cuz it doesn't no where to save it idk.
anywayas, it shows:
/dev/block/mmcblk0p2 /nativesd
/dev/block/mmcblk0p2 /system
/dev/block/mmcblk0p2 /data
tmpfs /dev
tmpfs /mnt/asec
tmpfs /mnt/obb
other than sizes, that is all it shows...
noobinius said:
ahh, great. well, i got there did it, no 179 error or any other error. i tried taking a screenshot with volume down + power key, but it doesn't seem to want to do it, maybe cuz it doesn't no where to save it idk.
anywayas, it shows:
/dev/block/mmcblk0p2 /nativesd
/dev/block/mmcblk0p2 /system
/dev/block/mmcblk0p2 /data
tmpfs /dev
tmpfs /mnt/asec
tmpfs /mnt/obb
other than sizes, that is all it shows...
Click to expand...
Click to collapse
Screenshot is turned on in settings, system, power menu but yea it wouldn't work anyway, other than reformating the fat partition, i can think of much else you can try, i think you may have to tempt fate here and change the wp7 part to primary, can't recall if it messes anything up at this stage, i don't think so, as long as it doesn't require a format.
THANK YOU!!!
HypoTurtle said:
Screenshot is turned on in settings, system, power menu but yea it wouldn't work anyway, other than reformating the fat partition, i can think of much else you can try, i think you may have to tempt fate here and change the wp7 part to primary, can't recall if it messes anything up at this stage, i don't think so, as long as it doesn't require a format.
Click to expand...
Click to collapse
WOW, rock on man.. you did it. reset wp7 partition to primary, both operating systems still working. and android is reading the fat32 partition now. Thank you sooo much for your help. I am thrilled we did it!!
Okay, I posted a guide on EXACTLY what I did with screenshots in an ACTUAL step by step process so it will be easier for the next person that doesn't know what they're doing just like I didn't. It is here: http://forum.xda-developers.com/showthread.php?p=31406820#post31406820
Guide
noobinius said:
thank you guys for your help. i have got it working and have made a step by step guide as i did it. just one problem, and i reaaaaallly hope its not a big problem. but in android it says no sd card. i need to know how to show whatever explorer program i use in android to look at the fat32 partition. anyone know?
i also need to know how to make wp7 see the fat32 partition that will have all the media files on it. anyone?
as soon as i get this information, i will post the guide. but i don't want to post it if there is something wrong (android and windows not reading the fat32 parition).
other than that both operating systems are still there and android is running from ext4 from folder nativesd!!!
Click to expand...
Click to collapse
PLEASE.. let us know where and how to get a hold of your NOOB Guide.. I would be very interested in it even if it all doesn't work!
TERRAREX0784 said:
PLEASE.. let us know where and how to get a hold of your NOOB Guide.. I would be very interested in it even if it all doesn't work!
Click to expand...
Click to collapse
Okay, I posted a guide on EXACTLY what I did with screenshots in an ACTUAL step by step process so it will be easier for the next person that doesn't know what they're doing just like I didn't. It is here: http://forum.xda-developers.com/show...0#post31406820