Related
I'm trying to build a new version of Apps2SD (version 2.6). I'm trying to get this version compatible with EXT4. I have resurrected my Darktremor Kernel (for those of you who don't know what that is...which is probably almost everyone...this is a kernel I built when the Hero source came out), which has EXT4 support.
I have set my ext partition to be EXT4.
The problem I'm having is, if I use the following command:
mount -o noatime,nodiratime -t auto /dev/block/mmcblk0p2 /system/sd
I get the following errors:
During boot: Invalid argument
In ADB shell: No such device
I've tried using -t ext4, but I just get "No such device".
What am I doing wrong here? I've search all over XDA and the Internet. I see Roms that have EXT4 in them, but nobody talks about how to manually mount one (I can find all sorts of information about EXT3, but it appears the attitude with EXT4 is "it just works.")
Thanks.
tkirton said:
What am I doing wrong here? I've search all over XDA and the Internet. I see Roms that have EXT4 in them, but nobody talks about how to manually mount one (I can find all sorts of information about EXT3, but it appears the attitude with EXT4 is "it just works.")
Thanks.
Click to expand...
Click to collapse
I wish I could help, but I haven't messed around with the kernel or even EXT4... hmm, maybe it's time for me to start! You have any specific tutorials you'd recommend tkirton?
pseudoremora said:
I wish I could help, but I haven't messed around with the kernel or even EXT4... hmm, maybe it's time for me to start! You have any specific tutorials you'd recommend tkirton?
Click to expand...
Click to collapse
I have a guide on how to compile your own kernel. The same guide is one of the threads in XDA, but I know how hard it is sometimes to search for something (hence why I'm asking about EXT4)
http://www.darktremor.com/kernels.html
See if that helps as a starting document.
Sorry that I having nothing useful to offer on this subject. However, am I assuming correctly that current recovery images would support an EXT4 when doing Nandroid backups for A2SD users?
Ceger
tkirton said:
I have a guide on how to compile your own kernel. The same guide is one of the threads in XDA, but I know how hard it is sometimes to search for something (hence why I'm asking about EXT4)
http://www.darktremor.com/kernels.html
See if that helps as a starting document.
Click to expand...
Click to collapse
****, I probably should have searched, I'm sure I would have found it. Thanks though, definitely going to take a look at this!
Ceger said:
Sorry that I having nothing useful to offer on this subject. However, am I assuming correctly that current recovery images would support an EXT4 when doing Nandroid backups for A2SD users?
Ceger
Click to expand...
Click to collapse
Honestly I never tried to backup or restore on an EXT4 drive. I'm sure it will work, but I'm suspecting there's issues with the kernel source. I never had a reason to go to EXT4 (EXT3 suited my needs just fine and there aren't a lot of Roms that support EXT4).
tkirton said:
Honestly I never tried to backup or restore on an EXT4 drive. I'm sure it will work, but I'm suspecting there's issues with the kernel source. I never had a reason to go to EXT4 (EXT3 suited my needs just fine and there aren't a lot of Roms that support EXT4).
Click to expand...
Click to collapse
I'll ask Toast and Fresh as their Dev ROM supports EXT4, so they should know if Nandroid backs that up or not... I suppose.
Ceger
Ceger said:
I'll ask Toast and Fresh as their Dev ROM supports EXT4, so they should know if Nandroid backs that up or not... I suppose.
Ceger
Click to expand...
Click to collapse
I'm not doubting it does...Amon_RA stated in several threads that it does. But that kernel and the one used to boot are completely different. The problem I'm running into is the one for boot (the 1.5 kernel, or version 2.6.27 of the kernel). It won't activate there, although there is an entry called /dev/block/mmcblk0p2 (so the kernel does see something...it just won't mount).
Maybe the issue is busybox. I'll see if I can find busybox on the recovery kernel and port it.
I was thinking it could be because .27 uses ext4-dev. I've seen a gang load of ext4 patches for .27 I used the rename patch in my kernel. But it seems not to work. When testing it I thought it did work. As a2sd in our init.d was seeming to be working and I had all my apps. But after everyone was saying they couldn't get it to work, I'm thinking I may need to try another patch. But yeah I'm not sure what the issue is. Maybe we can contact cyanogen or amon on this as I know they get it to work somehow.
toastcfh said:
I was thinking it could be because .27 uses ext4-dev. I've seen a gang load of ext4 patches for .27 I used the rename patch in my kernel. But it seems not to work. When testing it I thought it did work. As a2sd in our init.d was seeming to be working and I had all my apps. But after everyone was saying they couldn't get it to work, I'm thinking I may need to try another patch. But yeah I'm not sure what the issue is. Maybe we can contact cyanogen or amon on this as I know they get it to work somehow.
Click to expand...
Click to collapse
I'm coming up with the same conclusion...the ext4dev drivers don't appear to work. They load up (I'm getting that from a device dump), but they won't mount. Apparently, it won't mount in recovery, either.
I'm wondering if I grab a 1.6 or better source if I can recompile the part for ext4 inside the rest of the Hero 1.5 source. If I remember correctly with Linux compiling, as long as I have the correct dependencies, I should be able to compile it.
This is a quick walkthrough of how to apply my variant of "Mimicans speedfix" using my kernels on the Captivate. The speedfix essentially consists of making an ext3 or ext4 filesystem on an sdcard, and using that as our /data directory. This method is different from the original method in many of the details, but the underlying basis is that the stock /data partition is slow as molasses so we replace it.
This method should be pretty safe. As you will notice we dont copy around stuff and create a symlink mess. We just mount a partition over the current one. Yes we still mount the old one as well, even though it wont be used unless you take your card out. If that happens the phone will mount your old /data (that will probably be very out of date at the time) but itll get you up and running right away.
Right now there are two kernels, these mount the default partition, ext3 or ext4 on the second sdcard partition, the two options are:
Stock clock speed and Overclocked.
The overclocked kernel will clock from 100 to 800 Mhz as stock, then skippinig 1Ghz going to 1.2 Ghz.
Also, before we begin make sure you have this version of Odin. I used Samsung windows drivers that I found here.
You'll also want to read this thread about download mode. here you'll learn that you will have to try real hard to actually brick these phones, and even then it may still boot.
Ofcourse you also want to have root on your captivate.
You'll also need the android sdk.
If you are on Windows or Mac you will need some software to partition and format the sdcard, this live cd will work. You could also just get an ubuntu live cd or similar.
So, now we have the necessary tools and our new kernels and can get started.
Partition the disk:
There were reports from the modaco forums when mimocan first released his fix that ext3/4 partitions larger than 2gb were a problem, so keep your 2nd partition 2gb or smaller.
Use your favorite partitioning sofware to create 2 partitions on your sdcard. the first one will be formated FAT32 (vfat), and the second one ext3 or ext4. Make sure both are 'primary partitions'. You may want to make the second partition have partition type 83 (linux native).
Copy data files to sdcard:
If you are coming from stock, (eg without an existing a2sd /data partition on your sdcard) boot the phone without your formatted card and hotplug it before starting this process.
Using the sdk you need to connect the phone and use 'adb shell' to get a prompt on the phone.
Then follow these steps:
Code:
$
$ su -
# mkdir /sdcard/mnt
# mount -t ext4 /dev/block/mmcblk1p2 /sdcard/mnt
# busybox cp -a /data/* /sdcard/mnt
# umount /sdcard/mnt
# exit
$ exit
Flashing the kernel
1) Disconnect USB cable.
2) Open up odin.
3) Put your phone into download mode.
4) Connect USB cable, wait a second Odin should detect your phone, if not fiddle about with your drivers and reboot windows or something. This can be a real PITA.
5) In Odin load the kernel tarfile as "CSC"
6) Click "Start" in Odin, flashing should only take a few seconds.
You may run into issues here randomly and have a phone with the phone-!-computer image (I did!). Just go read up on the 'download mode' thread linked above it tells you how to proceed.
7) When you have booted your new kernel and /data partition you may have some issues with a few widgets/apps. Reinstalling or waiting/fiddeling with them seems to solve the issue. Maps was slow to open the first time after a new /data partition was mounted for me a few times, but subsequent launches were snappy.
If you want you may donate to my beer fund. It is not necessary but much appreciated
Didn't work for me. I partitioned my external SD card, flashed the speedup2 kernel, then ran the commands you posted, replacing 'ext3' with 'ext4'. My quadrant score is still in the low 900's.
Can you explain exactly what those commands do? The mimocan fix makes a lot more sense to me. Why did you decide to take a different approach?
Thanks for your help and effort!
I get 1716 scores in quadrant, but with real world running tests Touchdown and Dolphin HD browser still lag like holy hell.
I originally had the "method 2" hack (moving apps to the NAND) and that worked wonders, especially with these apps.
Can anyone test these two applications and see if there is lag for you?
Dolphin - try opening a new tab, closing it, and goto a large page and scroll with the volume buttons - it should all be smooth and quick
Touchdown - It should be very quick going between emails, I get a 5+ second delay before showing the email
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?
The captivate speedup kernel link is dead. Can soneone please post a mirror? Thanks
Worked great for me using ext4 partition/kernel. It brought my quadrant to 1817! Thats with a poor little 4gig, class 2 micro sd card. Im also running the i9000 JM2 firmware with Samset 1.6.
Thank you for all your hard work!!!! My phone is now complete (for now lol).
andy2na said:
I get 1716 scores in quadrant, but with real world running tests Touchdown and Dolphin HD browser still lag like holy hell.
I originally had the "method 2" hack (moving apps to the NAND) and that worked wonders, especially with these apps.
Can anyone test these two applications and see if there is lag for you?
Dolphin - try opening a new tab, closing it, and goto a large page and scroll with the volume buttons - it should all be smooth and quick
Touchdown - It should be very quick going between emails, I get a 5+ second delay before showing the email
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?
Click to expand...
Click to collapse
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.
_Opiate_ said:
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.
Click to expand...
Click to collapse
Its a brand new Kingston 8gb class 4 card, havent used it before applying this hack
Postal76 said:
Didn't work for me. I partitioned my external SD card, flashed the speedup2 kernel, then ran the commands you posted, replacing 'ext3' with 'ext4'. My quadrant score is still in the low 900's.
Can you explain exactly what those commands do? The mimocan fix makes a lot more sense to me. Why did you decide to take a different approach?
Thanks for your help and effort!
Click to expand...
Click to collapse
All you do is copy the files from your original /data partition onto the root of your ext{3|4} partition on the sdcard. Then that is mounted on reboot ontop of /data so you can use the new data partition from your card.
I feel this is a MUCH cleaner method than the original Mimocan fix, that copis a full copy of data into the root of the device (unnecessary backup since you still have your original /data partition as well), then it mounts your sdcard on /disk and symlinks that to /data.
I just don't see the need for the symlinks and stuff and honestly I thought this was a simpler method, no symlinks or anything.
If you arent seeing any speedups I'm betting something didn't go right, you are probably still running of the old /data partition. Are you sure you are running the speedup2 kernel and not the ext4 only kernel?
spyz88 said:
The captivate speedup kernel link is dead. Can soneone please post a mirror? Thanks
Click to expand...
Click to collapse
It seems to work from here...
_Opiate_ said:
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.
Click to expand...
Click to collapse
Except the Quadrant scores do you notice any real speed boost?
andy2na said:
.....
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?
Click to expand...
Click to collapse
yeah database I/O takes forever still.
Like I said in the other thread, try to reinstall the apps, Dolphin is very very fast here (thanks for getting me a new browser btw.)
I'm still a complete failure and now i get stuck at the galaxy s boot screen
Nuke, after doing the ext4 only method, I only get quadrant scores of 900.
Am I doing something wrong? I go through all the steps fine and everything seems like it went well but it seems like I'm doing something wrong down the line.
one thing I do notice is that I have A LOT MORE AVAILABLE MEMORY in advanced task killer. I use to only have 100 now I have 180MB.
Is it crucial to have to flash the Speedfix2?
after i put in
busybox cp -a /data/*
nothing happens it just sits there
igm503 said:
after i put in
busybox cp -a /data/*
nothing happens it just sits there
Click to expand...
Click to collapse
that part took like 15 min for me since I have a lot of application and app data
but there is no trailing dot it just repeats what i typed and then leaves a blank space
same thing it just repeats it
igm503 said:
but there is no trailing dot it just repeats what i typed and then leaves a blank space
Click to expand...
Click to collapse
What do you mean by "there is no trailing dot" ? Did you type it in? You need to include the trailing dot in your command; based on what you posted it appears you did not do that.
WOW! Okay... So now I'm getting 1756...
You just have to leave Quadrant on for like 15 minutes sometimes! This is very strange!
Notice the period after the asterisk. In the old forum, someone had a problem with that.
I did this fix last night after countless times of my messing up and figuring out how to partition with my phone still being able to read the card, flash problems with Odin, etc etc. I'm using an 8gb Classic 6 and just got an 1805 in Quadrant, and the phone is incredibly, noticeably faster. Did have some weird app problems when it was first applied, but some reinstalls fixed it. Thanks again Nuka!
Sent from my SAMSUNG-SGH-I897 using XDA App
I came across this post:
SpeedMod based (Doc's ROM and others) and every other Universal Lagfix corrupt badly /system
Thus is will cause the user Some FC overtime, Slow downs, The inability to Revert the lagfix.. or complete system failure.
It means that as long as they don't restore a /system with Odin, they're stuck on kernels using broken mount options.
Want proof
https://github.com/sztupy/universal_...e-init.sh#L273
Highlighted line is using wrong and corruption mount points
Second Issue:
Even with Advance NO RFS Config selected... RFS is still used in /system mounts... Dangerous And mean phone are slowly Dying of corruption..
Click to expand...
Click to collapse
Source: http://forums.hardwarezone.com.sg/showthread.php?t=2998903
Does anyone know what he is warning about?
XxDrAg0nxX said:
I came across this post:
Source: http://forums.hardwarezone.com.sg/showthread.php?t=2998903
Does anyone know what he is warning about?
Click to expand...
Click to collapse
Does someone tell you to check in the forum before starting a thread?
That post is from Supercurio in his tweeter page.He is working on his lagfix for froyo and came out with that today.It would be nice if he could come here and explain further more.
ps i see now that is already another thread with this subject and Ryan tried to explain a little whats happening
Copied my response from other thread on this issue to try and avert panic in case it turns out to be false - don't drop your sztupy kernel just yet - sztupy may be doing the correct thing here, he does usually know what he's doing!
Not 100% sure on this, since I have not used or looked at sztupy's lagfix very much, but that line you are pointing out is not a problem.
If /system is EXT4, then calling mount -t rfs on it will simply return an error message, and not mount it. It will do exactly nothing.
The following line would then mount it correctly.
Basically, this seems to be totally false. More evidence please.
Click to expand...
Click to collapse
EDIT: Okay, OP was updated with better information. Lack of check=no means that the FAT32 check *may* be running on the /system, which would cause corruption.
Probably a good idea to confirm if the filesystem check is actually happening though!
And there should probably only be 1 thread on this issue, this one should be closed!
Well. Dont overreact. I've been running sztupy's kernel fork -> raspdeep's oc for a time being, NO PROBLEMS AT ALL.
Dont confuse users.
Changing a file system doesn't corrupt anything, that's BS. Also long time JFS and EXT4 user.
So I was thinking...
df -h
/dev/block/mmcblk0p25------402.6M-----124.5M----257.3M-----33%---/system
/dev/block/mmcblk0p26------1.3G--------356.0M----886.5M----29% ---/data
/dev/block/mmcblk0p27------198.3M------35.7M----152.4M-----19%---/cache
Click to expand...
Click to collapse
We have roughly 2 gigs internal on our phones. Using CM7, my /system partition is over 60% empty. Why not install another rom beside it?
My idea is to partition the storage space into multiple directories that symlinks back to the original partitions only when booted.
For example, The partitioning could look like this:
/system------5M
/data--------5M
/cache------5M
/system1----200M
/data1------650M
/cache1-----100M
/system2----200M
/data2------650M
/cache2-----100M
Click to expand...
Click to collapse
The system would boot past splash1, where a screen similar to this could show up:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Depending on your selection, it would boot with either /system1 or /system2, symlinked to the original /system.
I know that it is possible to change your mtd partitions, it is a very commonly used hack on the G1 developed by Firerat and lbcoder (thread). If we can take this concept and take it a step further and create our own partitions, this seems feasable.
Some thoughts/concerns:
-both roms would have to use the same kernel as the kernel is one of the first things to boot.
-space for apps might be a bit tight for some, so A2SD might need to be used
-we would need a modified recovery image in which you have to specify which /system a rom would be copied to
-sharing /data and /cache might be possible, but might lead to problems with dramatically different roms.
-how would we go about setting up the screen to select which rom to boot?
-the closest thing to dual booting that we can do now would be /sd-ext based roms like old HD2 roms or Enomther's rom from before we had perm root
My programming knowledge is limited to HTML and flash, and I am a linux noob so I can't do much more than build a rom from source or changing out/modifying some png's for a theme.
If my idea seems feasible somebody else would have to code it. If you can come up with a better idea for dual boot, then by all means, share
mejorguille said:
So I was thinking...
We have roughly 2 gigs internal on our phones. Using CM7, my /system partition is over 60% empty. Why not install another rom beside it?
My idea is to partition the storage space into multiple directories that symlinks back to the original partitions only when booted.
For example, The partitioning could look like this:
The system would boot past splash1, where a screen similar to this could show up:
Depending on your selection, it would boot with either /system1 or /system2, symlinked to the original /system.
I know that it is possible to change your mtd partitions, it is a very commonly used hack on the G1 developed by Firerat and lbcoder (thread). If we can take this concept and take it a step further and create our own partitions, this seems feasable.
Some thoughts/concerns:
-both roms would have to use the same kernel as the kernel is one of the first things to boot.
-space for apps might be a bit tight for some, so A2SD might need to be used
-we would need a modified recovery image in which you have to specify which /system a rom would be copied to
-sharing /data and /cache might be possible, but might lead to problems with dramatically different roms.
-how would we go about setting up the screen to select which rom to boot?
-the closest thing to dual booting that we can do now would be /sd-ext based roms like old HD2 roms or Enomther's rom from before we had perm root
My programming knowledge is limited to HTML and flash, and I am a linux noob so I can't do much more than build a rom from source or changing out/modifying some png's for a theme.
If my idea seems feasible somebody else would have to code it. If you can come up with a better idea for dual boot, then by all means, share
Click to expand...
Click to collapse
Lol that's pretty cool idea
Sent from my Liquid Metal using XDA App
Bounty in place for this! I really share your dual boot vision. Very badass idea. If someone will work on it, im in bounty $20
Sent from my HTC Vision using XDA App
That would be difficult. bcoz,
1. Need WP7 drivers for G2/DZ devices
2. source/ROM compatible for G2/DZ (WP7 is not open, hehe m$)
3. A botloader.
Innocent Devil said:
That would be difficult. bcoz,
1. Need WP7 drivers for G2/DZ devices
2. source/ROM compatible for G2/DZ (WP7 is not open, hehe m$)
3. A botloader.
Click to expand...
Click to collapse
Lol who said I wanted windows 7? The picture up there is an example of a dual boot solution for old windows mobile phones. I was more interested in being able to run CM7/MIUI/liquid metal etc at once with minimal effort to change between them. And I'm pretty sure that WP7 doesn't use /system, /data, and /cache partitions.
Very cool idea .if you deside to do it I will be more than happy to help out in any way I can . Even if its not likely to work . It's still going to be a lot of fun trying .lol .cm and sense together . Or meego perhaps?
Sent from my HTC Vision using XDA App
mejorguille said:
Lol who said I wanted windows 7? The picture up there is an example of a dual boot solution for old windows mobile phones. I was more interested in being able to run CM7/MIUI/liquid metal etc at once with minimal effort to change between them. And I'm pretty sure that WP7 doesn't use /system, /data, and /cache partitions.
Click to expand...
Click to collapse
BAM!! +1000
Sent from my Liquid Metal using XDA App
awesome idea
I think this is a genius idea, and would have incredible implications if achieved. I also would be willing to donate to anyone who pulls off a functional and reproducible dual boot.
bahmanxda said:
Very cool idea .if you deside to do it I will be more than happy to help out in any way I can . Even if its not likely to work . It's still going to be a lot of fun trying .lol .cm and sense together . Or meego perhaps?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Me wants!!!! 2.4 as a daily,.... 3.0 for the eye candy!!!
Is there anything you genius'/genii/clever people can take from Kendon's Dualizer? http://www.villainrom.co.uk/forum/s...Dualizer-Dual-Boot-System&highlight=dual+boot
mejorguille said:
So I was thinking...
We have roughly 2 gigs internal on our phones. Using CM7, my /system partition is over 60% empty. Why not install another rom beside it?
Click to expand...
Click to collapse
Excellent idea!
My idea is to partition the storage space into multiple directories that symlinks back to the original partitions only when booted.
For example, The partitioning could look like this:
The system would boot past splash1, where a screen similar to this could show up:
Depending on your selection, it would boot with either /system1 or /system2, symlinked to the original /system.
Click to expand...
Click to collapse
There is already a multiboot bootloader installed on the phone which selects from two boot partitions... "boot" and "recovery". There is virtually no difference between them except for what is actually stored within the partitions.
I know that it is possible to change your mtd partitions, it is a very commonly used hack on the G1 developed by Firerat and lbcoder (thread). If we can take this concept and take it a step further and create our own partitions, this seems feasable.
Click to expand...
Click to collapse
You certainly could add or remove partitions from an MTD device using that approach, UNFORTUNATELY THOUGH, Vision does NOT HAVE an MTD device. It has an eMMC.
The eMMC also happens to be a bit of a WEIRD one. At the front of the eMMC there is a *fake* partition table, which is defined by the SPL. I am not aware of any way to alter this partition table except by modifying the SPL.
So repartitioning may not work.
However, symlinks WILL work.
Some thoughts/concerns:
-both roms would have to use the same kernel as the kernel is one of the first things to boot.
Click to expand...
Click to collapse
Nope. Put one kernel in the boot partition, the other one in the recovery partition. When you want to boot the second system image, simply boot into "recovery".
-space for apps might be a bit tight for some, so A2SD might need to be used
Click to expand...
Click to collapse
Easy
-we would need a modified recovery image in which you have to specify which /system a rom would be copied to
Click to expand...
Click to collapse
Trivial
-sharing /data and /cache might be possible, but might lead to problems with dramatically different roms.
Click to expand...
Click to collapse
Cache shouldn't be any problem, just wipe it on boot. Userdata would have to be manipulated in the exact same manner as system.
-how would we go about setting up the screen to select which rom to boot?
-the closest thing to dual booting that we can do now would be /sd-ext based roms like old HD2 roms or Enomther's rom from before we had perm root
Click to expand...
Click to collapse
Already answered. Boot recovery to boot the second system.
My programming knowledge is limited to HTML and flash, and I am a linux noob so I can't do much more than build a rom from source or changing out/modifying some png's for a theme.
If my idea seems feasible somebody else would have to code it. If you can come up with a better idea for dual boot, then by all means, share
Click to expand...
Click to collapse
Ok, now how I would do this is actually fairly simple to implement;
The boot image contains the basic structure of the root filesystem and sets up and mounts system and data.
It simply needs to be changed like this;
Destroy mountpoints "/system" and "/data".
Create new mountpoints "/base-system" and "/base-data".
Change the mounts for the system and data partitions to be mounted at the new mountpoints.
Create SYMLINKS "/system" --> "/base-system/system1" and "/data" --> "/base-data/data1" on the *first* boot image (to be installed to the "boot" partition), and "/system" --> "/base-system/system2" and "/data" --> "/base-data/data2" on the *second* boot image (to be installed to the "recovery" partition).
And that should basically do it.
This can also be used to boot Maemo/MeeGo.
This guy is already working on it, it is suppose to release soon.
http://forum.xda-developers.com/showthread.php?t=847423
I can't wait.
bahmanxda said:
Very cool idea .if you deside to do it I will be more than happy to help out in any way I can . Even if its not likely to work . It's still going to be a lot of fun trying .lol .cm and sense together . Or meego perhaps?
Click to expand...
Click to collapse
Not likely to work?!?! lol that's not very encouraging
DarkPyroGuy 09 said:
This guy is already working on it, it is suppose to release soon.
http://forum.xda-developers.com/showthread.php?t=847423
I can't wait.
Click to expand...
Click to collapse
Nah, booting from the sdcard isn't what I'm trying to accomplish. I want something on internal NAND, it would perform better (Look at the HD2).
riahc3 said:
This can also be used to boot Maemo/MeeGo.
Click to expand...
Click to collapse
It could, but as far as I'm aware there is no active effort of porting meego to the G2. Development stopped on the HD2 port, and now that nokia is out of the picture I imagine meego will die down.
There is already a multiboot bootloader installed on the phone which selects from two boot partitions... "boot" and "recovery". There is virtually no difference between them except for what is actually stored within the partitions.
Click to expand...
Click to collapse
Very good point, but would getting rid of a functional recovery be very practical? How would you approach rom upgrades? a PC based update system like ODIN for samsung phones? Fastboot? Or maybe you mean installing a new, separate boot partition.
You certainly could add or remove partitions from an MTD device using that approach, UNFORTUNATELY THOUGH, Vision does NOT HAVE an MTD device. It has an eMMC.
The eMMC also happens to be a bit of a WEIRD one. At the front of the eMMC there is a *fake* partition table, which is defined by the SPL. I am not aware of any way to alter this partition table except by modifying the SPL.
So repartitioning may not work.
However, symlinks WILL work.
Click to expand...
Click to collapse
Yeah we definitely don't want to mess with the SPL. I remember all the bricks from haykuro's SPL for having an incompatible radio/spl/recovery combination.
Nope. Put one kernel in the boot partition, the other one in the recovery partition. When you want to boot the second system image, simply boot into "recovery".
Click to expand...
Click to collapse
Again, I really wouldn't be happy loosing the recovery image. I mean, if you screw something up, boot to recovery, wipe, and reflash and you are good. If we replaced the recovery, to fix a problem you would have to be near a pc, boot to fastboot, wipe all, flash a recovery, boot to recovery, install a rom (or directly a PC10IMG.zip). I.E., the process would not be very noob friendly.
Cache shouldn't be any problem, just wipe it on boot. Userdata would have to be manipulated in the exact same manner as system.
Click to expand...
Click to collapse
When you wipe cache it takes considerably longer to boot, so maybe we should create separate cache partitions.
Already answered. Boot recovery to boot the second system.
Ok, now how I would do this is actually fairly simple to implement;
The boot image contains the basic structure of the root filesystem and sets up and mounts system and data.
It simply needs to be changed like this;
Destroy mountpoints "/system" and "/data".
Create new mountpoints "/base-system" and "/base-data".
Change the mounts for the system and data partitions to be mounted at the new mountpoints.
Create SYMLINKS "/system" --> "/base-system/system1" and "/data" --> "/base-data/data1" on the *first* boot image (to be installed to the "boot" partition), and "/system" --> "/base-system/system2" and "/data" --> "/base-data/data2" on the *second* boot image (to be installed to the "recovery" partition).
And that should basically do it.
Click to expand...
Click to collapse
Thanks for the detailed post dhkr234, you bring up a lot of good points and your method would be the easiest to implement, but unless I'm understanding something wrong, it would be not very friendly to the end user with no recovery image.
[QUOTE
Yeah we definitely don't want to mess with the SPL. I remember all the bricks from haykuro's SPL for having an incompatible radio/spl/recovery combination[/QUOTE]
I disagree... I think this is exactly what needs to be worked on. The devs eventualy got the G1 safe to flash the spl... and what's a few bricks if it means we can resize any and every partition on the device! Some one with some real skill with spl programing can figure it out... I have faith!
On a side note if we could "hack" the spl and re-partition the eMMC maybe we could reformat it to a faster file system... like they did at the factory and why our 4gig turned into 2... I would gladly trade that for 1gig if it is twice as fast! (Especially if I could change back)
Sent from my HTC Vision using XDA App
TheNewGuy said:
[QUOTE
Yeah we definitely don't want to mess with the SPL. I remember all the bricks from haykuro's SPL for having an incompatible radio/spl/recovery combination
Click to expand...
Click to collapse
I disagree... I think this is exactly what needs to be worked on. The devs eventualy got the G1 safe to flash the spl... and what's a few bricks if it means we can resize any and every partition on the device! Some one with some real skill with spl programing can figure it out... I have faith!
On a side note if we could "hack" the spl and re-partition the eMMC maybe we could reformat it to a faster file system... like they did at the factory and why our 4gig turned into 2... I would gladly trade that for 1gig if it is twice as fast! (Especially if I could change back)
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Yeah, but on the G1's we have JTAG to bring it back to life. And the eMMC partitioning the 4 gigs in 2 is irreversible. CM7 already increased its efficiency though EXT4 instead of EXT3
mejorguille said:
Yeah, but on the G1's we have JTAG to bring it back to life. And the eMMC partitioning the 4 gigs in 2 is irreversible. CM7 already increased its efficiency though EXT4 instead of EXT3
Click to expand...
Click to collapse
Yea that's basically were I got the idea.... but there has to be something like Jtag for the G2. I mean our phones aren't born with all this great stuff! LOL they start out completely bare and the OS,spl,bootloader,and who knows what else gets added on.. so it has to exist. And I know the 4gigs to 2 is irreversible but what about formatting the 2gigs we have down to one? With the right partition layout( I don't use any where near the 1.3 gigs I have on apps) we could cut it in half and still have enough room. And this would all just be one of the possible things to do if we had a hacked spl like the G1.
But I am no dev and I can't complain(or help)... just thinking out loud.
Sent from my HTC Vision using XDA App
Well i had an idea since we don't use the /cache partition, well i don't i was thinking we could use it as RAM.
Any ideas are welcome
LOL no ideas huh.....
Me either.... i wont give up tho i know for sure there is a way...
Hi
If you want a challenge try to get senors working on cm7.
Sent from my XT720 using XDA Premium App
how would that effect the ability to download market apps if its not available?
mchlbenner said:
Hi
If you want a challenge try to get senors working on cm7.
Sent from my XT720 using XDA Premium App
Click to expand...
Click to collapse
Its built on Korean right... lol i haven't even looked at it yet.... i would really like to get a fully 100% kick ass pure android working first.....
Call it a learning experience.
Because everything i know i learned here watching guys like Mz and KhP.
i need to get this finished first..
still imagine unlocking 100mb of ram bro.... cause thats what the /cache is man swap or RAM if i get that unlocked ouuuuuuuuuuuuuuuuuuuuu
mrmako777 said:
how would that effect the ability to download market apps if its not available?
Click to expand...
Click to collapse
Go away kid you bother me............
no effect.... no relevance for that matter LOL
but maybe you could help me.....
Has anyone really been far even as decided to use even go want to do look more like?
And if they did.... what about if they accidentally the whole thing?
mrmako777 said:
how would that effect the ability to download market apps if its not available?
Click to expand...
Click to collapse
hellmonger said:
no effect.... no relevance for that matter LOL
Click to expand...
Click to collapse
I don't know about that. In other ROMs, with the Dalvik on /cache larger apps, e.g. Angry Birds, wouldn't download (not enough space) when the /cache partition was to full.
You could maybe make a swap file on /cache (and an additional swap file on /data) and throw in some of the other useless small partitions. But that's still going to require fastboot.
I like using /cache for /data/dalvik-cache though and I used to get pretty close to filling it. CyanogenMod is sort of nice in that it will actually split the cache between /cache/dalvik-cache and /data/dalvik-cache with /cache/dalvik-cache holding the system apps and /data/dalvik-cache holding the downloaded cache.
3rdstring said:
I don't know about that. In other ROMs, with the Dalvik on /cache larger apps, e.g. Angry Birds, wouldn't download (not enough space) when the /cache partition was to full.
Click to expand...
Click to collapse
I was reading today on reddit that some people divert /cache to the sdcard so that large downloads work. I haven't tried it though.
Mioze7Ae said:
I was reading today on reddit that some people divert /cache to the sdcard so that large downloads work. I haven't tried it though.
Click to expand...
Click to collapse
Hmm.. Dunno about this one as well. but I never had that error, and I usually download the ROMs via my phone.
good luck! then we wont have to partition our sd card for swap anymore! possibly better battery life than swap on sd as less power is needed too!
Before you judge I'm running iceandfire 3.0 overclock at 900 and getting 13,566 to 14,000.
This build is stupid fast.
One issue sensors no big deal you can't do it I will find someone who can.
Sent from my XT720 using XDA Premium App
hellmonger said:
Go away kid you bother me............
no effect.... no relevance for that matter LOL
but maybe you could help me.....
Has anyone really been far even as decided to use even go want to do look more like?
And if they did.... what about if they accidentally the whole thing?
Click to expand...
Click to collapse
Like 3rd string mentions, cache size determines the size of an app you can download from the market as the market uses /cache as a repository to download/install apps...at least that's what I've noticed
Sent from my Milestone XT720 using Tapatalk
mchlbenner said:
Before you judge I'm running iceandfire 3.0 overclock at 900 and getting 13,566 to 14,000.
This build is stupid fast.
One issue sensors no big deal you can't do it I will find someone who can.
Sent from my XT720 using XDA Premium App
Click to expand...
Click to collapse
come on he wasnt saying he did not want to help... cant you read what Hellmonger said carefully? anyway, wouldnt it be good if you could use cache as swap? makes things more complete now that there are already so many good roms for our phone. since we are almost making 2.2 perfect, why not just do a little more, instead of leaving it there and starting to work on 2.3 where theres much more work left to do...
So i think Mz has the right idea..
But do we really have to set it up as swap the whole point ois to get this set up as ram so we dont have to fast boot anymore....
mrmako777 said:
Like 3rd string mentions, cache size determines the size of an app you can download from the market as the market uses /cache as a repository to download/install apps...at least that's what I've noticed
Sent from my Milestone XT720 using Tapatalk
Click to expand...
Click to collapse
The app will be downloaded to /sdcard/Download folder
kernel dont have swap support, so you can't use it from kernel layer. maybe you may find some swap functions in dalvik virtual machine layer, but I don't sure is there any
fjfalcon said:
kernel dont have swap support, so you can't use it from kernel layer. maybe you may find some swap functions in dalvik virtual machine layer, but I don't sure is there any
Click to expand...
Click to collapse
still no luck...
my goal is to stop the whole fastbot thing and use that cache partition as RAM, i already know how to set the download cache directory to SD card
on my ROM it's already implemented...
/cache as Ram.....
We really need to pull our bootloaders and decomplile them to see if there's a way to do the fastboot ourselves. The people that have looked the hardest at the bootloader are on Milestone A853, but according to them they don't have a working "fastboot boot" so that code pathway is missing from their studies.
What we need to find out is what the pathway through the bootloader is that ends up with booting a custom boot.img from RAM (i.e. does fastboot boot go through the entire boot stack or not and if it does how does it convince it to skip the check). In other words I have two mental two models for how fastboot works:
Model 1
Start boot process
Read flags that direct boot to fastboot
Load and execute fastboot bootloader
fastboot reads kernel from USB into memory
fastboot continues boot using the kernel in memory
Model 2
Start boot process
Read flags that direct boot to fastboot
Load and execute fastboot bootloader
fastboot reads kernel from USB into memory
fastboot sets up the phone for boot of the memory-loaded kernel
fastboot restarts boot process
Read flags that direct boot to load and execute the kernel from RAM
So the question is which one is correct? Does fastboot boot continue the current boot process, or does it alter the next boot? That's the big question. If it's model 2, here's an outline for a possible attack:
Attack for Model 2
Normal boot of blessed kernel through sh_hijack.sh
hijack loads a new kernel from the phone into memory
hijack sets up the phone for boot of the memory-loaded kernel
hijack set boot flags for fastboot boot
hijack restarts boot process
Boot memory loaded kernel
So how do we figure out if XT720 uses #1 or #2?
FYI: these are the A853 decompiled bootloaders: https://gitorious.org/droid/reversed (see the asm folder inside the source tree--we need this for XT720 so that we can understand what fastboot boot is doing)
I believe a 2nd had beem complied but it would not boot radio and we don't have a baseband made.
Sent from my Milestone using XDA Premium App