Related
THIS WILL NO LONGER BE MAINTAINED and is officially killed
go here if you want rw access and get the version without a kernel.(assuming you have a kernel installed that has aufs support)
IF YOU FLASHED THE UPDATE.ZIP THAT WAS ON THIS PAGE...PLEASE DO THE FOLLOWING:
You need to remove the init script and static busybox that were installed on your device. You have to do this in recovery mode since your rw access is not real.
Download the version linked to above and place it at the root of your sdcard.
open rom manager
select boot to recovery
boot to recovery while plugged in to computer
then from computer:
Code:
adb shell
mount /system
mount /data
rm /system/etc/init.d/99sysrw
rm /data/bin/busybox
umount /system
umount /data
exit
and from the phone:
flash BlaY0's update.zip you put on the sdcard
Really cool for your contributions.
I have no clue what you said, though. Will I be able to uninstall system apps with this? I'm guessin not as you were mostly speaking of partitions.
Lemme guess, brings ext2/3 etc together for something?
wow, best news that I have heard all day.
Ah! Thank you so much. I was just asking about this a couple weeks ago.
Sent from my T-Mobile myTouch 3G Slide using XDA App
does this mean that we can use metamorph now?
sorry if its a stupid question
Hayzie said:
Really cool for your contributions.
I have no clue what you said, though. Will I be able to uninstall system apps with this? I'm guessin not as you were mostly speaking of partitions.
Lemme guess, brings ext2/3 etc together for something?
Click to expand...
Click to collapse
No, You will not be able to uninstall apps with this (at least I don't think). It doesn't actually let you write to the /system partition, it just creates an overlay.
And No it does not even look for an ext partition, it just uses the data partition.
rodriguez27 said:
does this mean that we can use metamorph now?
sorry if its a stupid question
Click to expand...
Click to collapse
Don't really know, I haven't tried. Bear in mind however since it is on your data partition, space could be an issue. Any files changed would then be stored in /data/sysrw.
thanks for the quick info
I'm gonna try this out with Android Commander. With this I should be able to remove apps and delete files without restarting into recovery and mounting everything. Right?
dumfuq said:
No, You will not be able to uninstall apps with this (at least I don't think). It doesn't actually let you write to the /system partition, it just creates an overlay.
Click to expand...
Click to collapse
apparently I was wrong.
as a test I did...
Code:
rm system/app/com.amazon.mp3.apk
while the phone was booted and it worked!
Even after a reboot I do not have com.amazon.mp3.apk installed
It worked for me too, I used android commander booted and running and removed out of /system/apps android.tether.apk, mytouchmusic-signed.apk, and twitter.apk. I had a force close when I removed one thing (I am sure it was running in the background)
They all were gone after a reboot too, I was also able to update adfree just fine.
Any way this can be built into roms?
Thanks for the hard work!
dumfuq said:
No, You will not be able to uninstall apps with this (at least I don't think). It doesn't actually let you write to the /system partition, it just creates an overlay.
And No it does not even look for an ext partition, it just uses the data partition.
Don't really know, I haven't tried. Bear in mind however since it is on your data partition, space could be an issue. Any files changed would then be stored in /data/sysrw.
Click to expand...
Click to collapse
Hey dumfuq, thanks for this! Great idea on porting this badboy! One question though... from what I understood from the source thread is that will use the EXT. Partition for data if you have it right? So it won't break a2sd? I think I understood that correctly. Plus you need your kernel and that should make it work on any rom. I assume it won't overwite the OC kernel either. I'm excited to try this one out but I'm in the middle of rebuilding my rom so I can make a new backup (my old corrupted finally). I will test out as much as I can and let you know if different roms work. I should be done reinstalling by tomorrow (i have like 200 apps, lol!). This might turn out to be a good way to skip nandroiding and wiping all together if it turns out to work properly with a2sd/a2fat32... don't ya think?
sino8r said:
Hey dumfuq, thanks for this! Great idea on porting this badboy! One question though... from what I understood from the source thread is that will use the EXT. Partition for data if you have it right? So it won't break a2sd? I think I understood that correctly. Plus you need your kernel and that should make it work on any rom. I assume it won't overwite the OC kernel either. I'm excited to try this one out but I'm in the middle of rebuilding my rom so I can make a new backup (my old corrupted finally). I will test out as much as I can and let you know if different roms work. I should be done reinstalling by tomorrow (i have like 200 apps, lol!). This might turn out to be a good way to skip nandroiding and wiping all together if it turns out to work properly with a2sd/a2fat32... don't ya think?
Click to expand...
Click to collapse
This version is not the same as blayo's for the legend. It is closer to the desire one (although I used info from both).
Mine will not even try to detect an ext partition at this point, it just uses the data partition regardless of what is available.
Also nothing at all will get overwritten with this unless you happen to have an /system/etc/init.d/99sysrw file. It doesn't copy the kernel or modules, instead it just assumes you have a supported version . The only thing this update.zip does is add the script into init.d.
dumfuq said:
This version is not the same as blayo's for the legend. It is closer to the desire one (although I used info from both).
Mine will not even try to detect an ext partition at this point, it just uses the data partition regardless of what is available.
Also nothing at all will get overwritten with this unless you happen to have an /system/etc/init.d/99sysrw file. It doesn't copy the kernel or modules, instead it just assumes you have a supported version . The only thing this update.zip does is add the script into init.d.
Click to expand...
Click to collapse
I see... so basically, only cm based roms will work. Well, eventually, most us will move to cm based roms once bluetooth and a few minor bugs are worked out. Well, thanks for the info!
sino8r said:
I see... so basically, only cm based roms will work. Well, eventually, most us will move to cm based roms once bluetooth and a few minor bugs are worked out. Well, thanks for the info!
Click to expand...
Click to collapse
I haven't used them, but I think the newer sense roms support init.d scripts so you should be all good.
Working great on Fenix 2.0 with one of dumfuqs OC kernals...thank you much for this.
V2 is posted. It is essentially BlaY0's script for legend. I've only tested with no ext partition, but hopefully if you have one it will use it to store sysrw.
dumfuq said:
V2 is posted. It is essentially BlaY0's script for legend. I've only tested with no ext partition, but hopefully if you have one it will use it to store sysrw.
Click to expand...
Click to collapse
just so you guys now, v2 probably doesn't work for people with who want it on the ext. Blay0 fixed his though (to support non ext users), so I'll give it a look here soon.
Both versions do not work on stock kernel. Am I missing something? Should I use dumfuq kernel or cyanogenmod kernel in order to use this?
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
WHAT!!?? My slide has finally lost it's parasite, com.amazon.mp3 you are toast now. You and your friends kickback, talkback, soundback, twitter... not sure what else I erased, oh genie widget. Thanks dumfuq!! You are the man
Everyone that does this, make sure to check cyanogen's wiki on making a barebones rom so you don't delete something you actually need (of course you did make a nandroid before doing this so no need to worry if you do).
You won't actually delete anything... overlay just makes you (and system) think it is deleted.
THIS UTILITY IS FOR FASCINATE TOUCHWIZ FROYO/GINGERBREAD ONLY
UPDATED FOR EC09 GINGERBREAD
I have created a format utility that can be used from within CWM3 recovery. Just select the ZIP in CWM3 recovery, and the package will do ALL of the work for you.
These utilities come in two independent packages which will completely format your device with EXT4. As a bonus, it will create all directories and setup all ownership and permissions in accordance to the Fascinate.
Voodoo recovery does not currently allow you an option to select a format style, and furthermore does not truly format any partition unless it runs through the Voodoo "lagfix" transition upon booting the device.
There is one caveat in order to use EXT4: you need a kernel that supports it, and this would be using a "Voodoo" style kernel that has built in support. Luckily, most of the "good" kernels available have this ready to go.
Understand that this package will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device. If you already have a ROM installed on your device and want to keep your device the way it is, and also want EXT4, then use the Voodoo method to switch to EXT4. The reason for this is because it backs up your data before it formats.
After you use this package, you can install any ROM of your choosing, as the package will already self-manage Voodoo's methods for "enabling" or "disabling" the "lagfix".
--------
Please report if the package is not working.
A good indicator of this is if you try to install the package and it only takes 1 second to work, then says it is finished. This means it is probably not working, however, if you are formatting the same type of file system over itself with no pre-existing data on the device, it will take the aforementioned 1 second to work.
To see if it worked: mount each partition in CWM3 recovery, then adb shell into your device and type the mount command, in the listing you should see what file system your partitions are using. If the big four all say EXT4, then the package install has been successful.
In order to assure that it will work correctly, use the latest version of a CWM3 recovery that you can find. I can personally vouch for nemesis2all's OTB CWM3 Recovery v3.0.2.8x.OTBv2. Unfortunately not all CWM3 recoveries are the same, and yours may not work with these utilities. If you find a recovery that works fine, post it here and I will update this.
--------
Packages updated: 6/28/2011 - 12:57PM EST
EXT4 Format ALL (formats everything): http://www.mediafire.com/?6hx7f8g7c8vv6xz
EXT4 Format CACHE: http://www.mediafire.com/?2621a888ydv41mg
EXT4 Format DATA: http://www.mediafire.com/?ck2bb340yybpe4z
EXT4 Format DBDATA: http://www.mediafire.com/?ahxzs8xsyyvemed
EXT4 Format FOTA: http://www.mediafire.com/?42ijpi67grdb6mm
EXT4 Format PREINSTALL: http://www.mediafire.com/?d42as1l3pdbhr2t
EXT4 Format SYSTEM: http://www.mediafire.com/?rgs46hhq8qd951t
--------------------
If you like my work, consider donating, or thanking me by clicking the thanks button
thanks for this
navenedrob said:
I have created two format utilities that can be used from within CWM3 recovery. Just select the type of file system you want to use, select it in CWM3 recovery, and the package will do ALL of the work for you.
These utilities come in two independent packages which will completely format your device with either RFS or EXT4. As a bonus, it will create all directories and setup all ownership and permissions in accordance to the Fascinate.
Voodoo recovery does not currently allow you an option to select a format style, and furthermore does not truly format any partition unless it runs through the Voodoo "lagfix" transition upon booting the device.
There is one caveat in order to use EXT4: you need a kernel that supports it, and this would be using a "Voodoo" style kernel that has built in support. Luckily, most of the "good" kernels available have this ready to go.
Understand that this package will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device. If you already have a ROM installed on your device and want to keep your device the way it is, and also want EXT4, then use the Voodoo method to switch to EXT4. The reason for this is because it backs up your data before it formats.
After you use this package, you can install any ROM of your choosing, as the package will already self-manage Voodoo's methods for "enabling" or "disabling" the "lagfix".
Please report if the package is not working.
A good indicator of this is if you try to install the package and it only takes 1 second to work, then says it is finished. This means it is probably not working, however, if you are formatting the same type of file system over itself with no pre-existing data on the device, it will take the aforementioned 1 second to work.
To see if it worked: mount each partition in CWM3 recovery, then adb shell into your device and type the mount command, in the listing you should see what file system your partitions are using. If the big four all say EXT4 or RFS (depending on script used), then the package install has been successful.
In order to assure that it will work correctly, use the latest version of a CWM3 recovery that you can find. I can personally vouch for nemesis2all's OTB CWM3 Recovery v3.0.2.8x.OTBv2. Unfortunately not all CWM3 recoveries are the same, and yours may not work with these utilities. If you find a recovery that works fine, post it here and I will update this.
Click to expand...
Click to collapse
Ok, I think I'm having a complete idiot moment here so please be patient with me. What would be the benefits of me running this on my device that is currently running jt's CM7 with OTB 1.5 kernel and EXT4 (voodoo for those who don't know) already converted? Thanks in advance.
It would be of no use. Unless you need to format your entire device.
So this would be a good thing to flash in place of wiping between rom flashes? Does it have any benefits compared to a regular data and cache wipe when you are already converted to ext4?
It would be a good idea to flash it in that scenario, yes. Currently no ROM will do the job that this package will for you, which is why a lot of ROM's say not to wipe your device, because you'll run into major issues if you do. When you do your "wipes" through recovery it doesn't really do anything besides a recursive delete of files, so it doesn't really format anything (even though it says "format" in the menu system). The only time it actually does any formatting is during the Voodoo transition. When you do wipe those areas, it does not leave the file structure intact and also does not leave the ownership and permissions intact. These packages completely solve that problem. Also, these packages are focused on performance so everything is done that is possible to make sure that your file system is as fast as possible.
navenedrob said:
It would be a good idea to flash it in that scenario, yes. Currently no ROM will do the job that this package will for you, which is why a lot of ROM's say not to wipe your device, because you'll run into major issues if you do. When you do your "wipes" through recovery it doesn't really do anything besides a recursive delete of files, so it doesn't really format anything (even though it says "format" in the menu system). The only time it actually does any formatting is during the Voodoo transition. When you do wipe those areas, it does not leave the file structure intact and also does not leave the ownership and permissions intact. These packages completely solve that problem. Also, these packages are focused on performance so everything is done that is possible to make sure that your file system is as fast as possible.
Click to expand...
Click to collapse
Ok, so basically what you are saying is this would be ideal to use instead of data/cache/dalvik wipe for rfs to rfs and ext4 to ext4, correct? Thanks in advance.
That's correct.
I've teamed up with nemesis2all and we are thinking about adding all of these abilities to the OTB kernel, so you'll be able to choose different kinds of file systems and format options through CWM3 recovery instead of having to use these packages here. That will come when it comes, but for now this is the ideal solution.
EXT2/EXT3/EXT4/XFS/RFS etc...
Also, I've updated the attachments in the post.
navenedrob said:
That's correct.
I've teamed up with nemesis2all and we are thinking about adding all of these abilities to the OTB kernel, so you'll be able to choose different kinds of file systems and format options through CWM3 recovery instead of having to use these packages here. That will come when it comes, but for now this is the ideal solution.
EXT2/EXT3/EXT4/XFS/RFS etc...
Also, I've updated the attachments in the post.
Click to expand...
Click to collapse
Just to let you know, I ran the ext4 package and I got some serious lag issues after I installed my rom and it actually starting going into a soft boot loop. It began to act very weird and unstable. I booted back into recovery and I wiped everything the way I usually do and formatted the system/data/dbdata/cache manually in mounts and storage and reinstalled. It's better than it was but it still seems like it is kinda slower and more laggier than it was before I ran the package. Any ideas? Thanks man.
You'll need to give me more information than that to determine your problem.
What kernel are you using? What recovery are you using? What ROM are you running? What are the results of running the mount command with all partitions mounted?
navenedrob said:
You'll need to give me more information than that to determine your problem.
What kernel are you using? What recovery are you using? What ROM are you running? What are the results of running the mount command with all partitions mounted?
Click to expand...
Click to collapse
OTB 1.5, CM7. It's kinda weird. When I ran your package and then flashed cm7 and booted it, it was laggier than I have ever seen my phone and when I would try to do certain operations it would soft boot. At one point I couldn't even turn wifi on. So, I booted back into recovery and wiped and manually formatted everything and reinstalled everything. After that it was still kind of laggy but much better. I restored all of my apps and got my phone back to all my custom settings. Then I began to notice that it wasn't really lagging anymore, in fact it seemed pretty snappy. I ran quadrant to see if the numbers were the same as before to determine if I was in fact ext4 converted. Surprisingly the numbers were higher than normal. And I even noticed in titanium backup that some of my internal memory had been freed up. I can't explain it but everything seems to be running really good right now. It's almost like after running your package the phone had to be conditioned, and once it was conditioned it ran real good. But, that doesn't explain why it was soft booting and wifi wouldn't work. Who knows.
Not really sure exactly, it actually could have been a few different things causing the "issues". I'm going to try your exact scenario and see what happens.
kidserious said:
OTB 1.5, CM7. It's kinda weird. When I ran your package and then flashed cm7 and booted it, it was laggier than I have ever seen my phone and when I would try to do certain operations it would soft boot. At one point I couldn't even turn wifi on. So, I booted back into recovery and wiped and manually formatted everything and reinstalled everything. After that it was still kind of laggy but much better. I restored all of my apps and got my phone back to all my custom settings. Then I began to notice that it wasn't really lagging anymore, in fact it seemed pretty snappy. I ran quadrant to see if the numbers were the same as before to determine if I was in fact ext4 converted. Surprisingly the numbers were higher than normal. And I even noticed in titanium backup that some of my internal memory had been freed up. I can't explain it but everything seems to be running really good right now. It's almost like after running your package the phone had to be conditioned, and once it was conditioned it ran real good. But, that doesn't explain why it was soft booting and wifi wouldn't work. Who knows.
Click to expand...
Click to collapse
It's possible that since you wiped your market was trying to restore all your apps in the back ground which was taking all your memory up and making your phone lag. But after you restored all your apps it was all set
Coreyc1123 said:
It's possible that since you wiped your market was trying to restore all your apps in the back ground which was taking all your memory up and making your phone lag. But after you restored all your apps it was all set
Click to expand...
Click to collapse
What I meant was as soon as it booted (during setup wizard) it was super laggy. I download TB from the market by itself and it took forever to register. I was doing the GPS fix and it soft booted. I couldn't turn wifi on and it soft booted. All before I did a batch restore in TB. And I know that the market begins to sync automatically as it always does but this was much much different.
Sent from my SCH-I500 using Tapatalk
kidserious said:
What I meant was as soon as it booted (during setup wizard) it was super laggy. I download TB from the market by itself and it took forever to register. I was doing the GPS fix and it soft booted. I couldn't turn wifi on and it soft booted. All before I did a batch restore in TB. And I know that the market begins to sync automatically as it always does but this was much much different.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I had these same symptoms one time that I installed kasonate v7, but after reflashing, the next time it didnt.
I know you're not talking about the same cm version, but they might be related and not related to the format utility.
Ok, I ran this package again to make sure that I didn't do something wrong and to see if I would get the same results. I ran the package, flashed cm7 then gapps then OTB GB 1.5. all from the recommended recovery in your post. Again I ended up in a soft boot loop and wifi was acting up again and was causing a boot loop. So once again I booted into recovery and wiped data/cache/dalvik normally and formatted manually via mounts and storage and reinstalled again and she's running like a dream. Very weird but I must say I am very happy with the results I ended up with, regardless of how I got them. So obviously, this was not your intention for it to be done this way but I do see an improvement in responsiveness, speed and memory being freed up. Before, my free internal memory was 1.49 and now it is 1.52. Thank you sir, I appreciate this.
Thanks for this utility! Works great. Went from Jt's cm7 to the miui/touchwiz rom and ran the utility in between. My phone is running faster than ever and no issues. Thanks again!
Sent from my SCH-I500 using XDA App
Yeah running this on mesmerize with heinz 57 best my phone has ever run quadrant of 2250s @ 1.5 ghz
Sent from my SCH-I500 using XDA App
stephenj37826 said:
Yeah running this on mesmerize with heinz 57 best my phone has ever run quadrant of 2250s @ 1.5 ghz
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You're welcome, the utility enables a few nice options as far as file system performance is concerned, that Voodoo doesn't at this time.
Do tell oh and thanks a million
Sent from my SCH-I500 using XDA App
This mod will move dalvik-cache from /data to /preload freeing up some space and utilizing the otherwise unused /preload partition when running a pure ICS ROM.
Based on the SGS2-CF-ROOT-XXLPH kernel.
The kernel is untouched but the init.rc script on initramdisk is modded to mount /preload with same prefs as /data normaly has.
It does not wipe or format anything, exept the dalvik-cache.
After installation, wiping dalvik-cache from CWM actually works just fine.
Flash it with CWM.
/Cheers
Can you explain better the benefits of using this? It's unclear for noobs like me.
bodhisattva99 said:
This mod will move dalvik-cache from /data to /preload freeing up some space and utilizing the otherwise unused /preload partition when running a pure ICS ROM.
Based on the SGS2-CF-ROOT-XXLPH kernel.
The kernel is untouched but the init.rc script on initramdisk is modded to mount /preload with same prefs as /data normaly has.
It does not wipe or format anything, exept the dalvik-cache.
After installation, wiping dalvik-cache from CWM actually works just fine.
Flash it with CWM.
/Cheers
Click to expand...
Click to collapse
but if u do that, all files under the dalvik-cache dir have to be rebuilt every time the phone is booted
ykk_five said:
but if u do that, all files under the dalvik-cache dir have to be rebuilt every time the phone is booted
Click to expand...
Click to collapse
I haven't looked at the mod yet, but if the dalvik cache is sym linked to the other partition, then it wouldn't have to rebuilt.
Trumpex said:
I haven't looked at the mod yet, but if the dalvik cache is sym linked to the other partition, then it wouldn't have to rebuilt.
Click to expand...
Click to collapse
i've not looked at it neither, but i have used sym links before, and the files in dalvik were duplicated, one for the old dalvik-cache, plus one for the symlink
eg
[email protected]@[email protected] and [email protected]@[email protected]
PS pls correct me if i am wrong coz i tried it couple of mths b4
Thanks all for the interest.
OBSERVE! Only for XXLPH kernel.
Answers to your questions:
* Benefit: you move away 100-300Mb of data to /preload and can use more on /data to use your favorite apps.
* No, there is no duplication of files. And YES the dalvik is rebuilt, but only on the fist boot, not each time, unless you tamper with the new paths, but the script takes care of that, so dont worry.
* kernel mounts /preload with same prefs as /data, and also in RW mode.
* the script takes care of all your worries (/system/etc/init.d/S99dalvik2preload). It is written so you can remove any directory/link (/data/dalvik-cache or /preload/dalvik-cache) and your phone still boots up and rebuilds the dalvik on /preload/dalvik-cache. A symlink is created to /preload/dalvik-cache from /data/dalvik-cache and all works just as before.
Works aslo with CWM Recovery "Wipe dalvki cache" since CMW seems to mount all filesystems and respects lymlinks.
Tested and works.
No worries.
Flash it and let me know what you think.
Installed, seems to work just fine, many thanks!
Atomix86 said:
Installed, seems to work just fine, many thanks!
Click to expand...
Click to collapse
Nice. Thanks for the feedback! Keep it coming.
Can you post your /data and /preload usage?
Hi guys, hope you like it.
though....
I would really like to have some input/feedback on this mod.
Feel free to comment, anytime, anywhere and anyhow.
ykk_five said:
but if u do that, all files under the dalvik-cache dir have to be rebuilt every time the phone is booted
Click to expand...
Click to collapse
No, not every time, just on the first execution.
I fixed the rest in my script.
Or did I missunderstand you mate?
thank you bodhisattva99 you are the best ...
is this the same with "Integrate sys Dalvik into ROM" option from Titanium Back-Up Pro?
So how long does first boot take? I'm stuck on boot logo no matter what. Once I got to the boot animation and it kept going for a good 5 minutes. Reflashing it didn't help.
bodhisattva99 said:
No, not every time, just on the first execution.
I fixed the rest in my script.
Or did I missunderstand you mate?
Click to expand...
Click to collapse
hi, if i remember correctly, since the path in init.rc points to /system/framework, so the files there will be processed to dex files. i then symlinked it to /data/framework and i found files like [email protected]@[email protected] and [email protected]@[email protected]
i cant remember what else i have changed at that time but, perhaps i was not satisfied with the final result and hence stopped testing it.
anyway, i am happy to see ppl tries to find out these kind of tweaks/tricks again
good luck and carry on
KukurikU said:
is this the same with "Integrate sys Dalvik into ROM" option from Titanium Back-Up Pro?
Click to expand...
Click to collapse
No, it is not.
That option moves the dalvik cache files for /system applications into /system
Hi, great work! I have taken the liberty of rewriting your script from scratch to a new and what I believe to be a more efficient one. There is a requirement of having Busybox installed in /system/xbin. I haven't tested it myself since I do not own an SGS2, but AColwill has tested it for me and says it appears to boot faster.
Link in my signature.
Does this work on all ICS stock rooted and custom roms like XXLPQ ans LP7? Thanks
sniperwolf64 said:
Does this work on all ICS stock rooted and custom roms like XXLPQ ans LP7? Thanks
Click to expand...
Click to collapse
May work, version 1.5 uses the SGS2-CF-ROOT-XXLPH kernel. I'm not sure which kernel LPQ/LP7 use. Have not had time to check it out.
I will make a new one for LP7 this weekend if i can find the time.
Elisha said:
So how long does first boot take? I'm stuck on boot logo no matter what. Once I got to the boot animation and it kept going for a good 5 minutes. Reflashing it didn't help.
Click to expand...
Click to collapse
That suckzzz...
Should just take a few seconds longer, not counting the dalvik rebuild.
What ROM are you on?
Proz0r said:
Hi, great work! I have taken the liberty of rewriting your script from scratch to a new and what I believe to be a more efficient one. There is a requirement of having Busybox installed in /system/xbin. I haven't tested it myself since I do not own an SGS2, but AColwill has tested it for me and says it appears to boot faster.
Link in my signature.
Click to expand...
Click to collapse
Checked out your script. Nice work.
Will try it out. This is a better solution than incorporating kernel changes, obviously...
EDIT: Flashed it and phone does not boot... stuck in bootanimation...
can som one tell me how i can dual boot my photon4g
lucky.79 said:
can som one tell me how i can dual boot my photon4g
Click to expand...
Click to collapse
You can't, yet.
This uses a method called 2ndinit myself and peetr_ have been looking into using this option.
mof9336 said:
This uses a method called 2ndinit myself and peetr_ have been looking into using this option.
Click to expand...
Click to collapse
so we can have one androidOS in the internal storage and another android OS in the external storage?? that's really really cool! Would photon 4g be the first phone to have more than 1 OS installed?
rituel said:
so we can have one androidOS in the internal storage and another android OS in the external storage?? that's really really cool! Would photon 4g be the first phone to have more than 1 OS installed?
Click to expand...
Click to collapse
Check my post: http://forum.xda-developers.com/showthread.php?t=1652411
I have used suggestions from Atrix thread and they worked fine. I have tried two or three times and each time I got some issues. I was copying stock 2.3.4 ROM onto SD card. One time USB ports were not working - no charging, no connection to computer with the cable. Next time there was problem with Play Market. I have tried different steps to reset its settings to no avail. It was giving error related to storage unavailability while downloading anything. I have removed Play Market completely, then somehow install it back, but the issue was not resolved. Now I think maybe it's a permissions issue.
Also device was really slow while running OS on sd-card (I have 32GB Transcend Class 10). It's fun to try but I don't see any practical use for it.
bloodhound_ said:
Check my post: http://forum.xda-developers.com/showthread.php?t=1652411
I have used suggestions from Atrix thread and they worked fine. I have tried two or three times and each time I got some issues. I was copying stock 2.3.4 ROM onto SD card. One time USB ports were not working - no charging, no connection to computer with the cable. Next time there was problem with Play Market. I have tried different steps to reset its settings to no avail. It was giving error related to storage unavailability while downloading anything. I have removed Play Market completely, then somehow install it back, but the issue was not resolved. Now I think maybe it's a permissions issue.
Also device was really slow while running OS on sd-card (I have 32GB Transcend Class 10). It's fun to try but I don't see any practical use for it.
Click to expand...
Click to collapse
hey can you write a detailed guide with instructions on how you got dual boot working on photon 4g please !? I cant afford to make mistakes and bork my phone >.>
And like you said as long as i can charge my phone and connect to my computer with one of the operating system its not a problem. But having dual boot will be really helpfull means I can check out more than one Rom simultaneously.
rituel said:
hey can you write a detailed guide with instructions on how you got dual boot working on photon 4g please !? I cant afford to make mistakes and bork my phone >.>
And like you said as long as i can charge my phone and connect to my computer with one of the operating system its not a problem. But having dual boot will be really helpfull means I can check out more than one Rom simultaneously.
Click to expand...
Click to collapse
The instructions I followed from Atrix page are very detailed. Link is here
It takes time to have a thread where most of the common questions answered. I think it is useless effort to start similar topic here, in addition - I don't have necessary time, knowledge and wish for this.
Anyway, if you do something wrong - you should always have full backup - then you risk nothing. Remember that if you got soft-bricked and recovery doesn't work, you can always use RSD lite to load stock 198_7 ROM, unlock, write new recovery and restore from initial backup.
The only difference between Atrix and Photon, (relative to this task) that you should keep in mind is the partition sizes. Partition table by LAKSHMAN in Play Market (or any other partition tool) can show you your partition sizes. I didn't guess to use these tools when I followed the instructions. Add up some 10 GB to each partition, just in case. When you partition your SD card, you should create partitions of the following size:
system - 420 MiB (stock ROM system partition size 408 MiB)
cache - 645 MiB (my current cache size on stock ROM is 610 MiB)
data - 2.6 MiB
I would also recommend to use script manager to launch scripts that will replace boot image from one to another. In other words, it will control where you will boot next time.
Note that Windows 7 is going mad about SD card with several partitions - sometimes you can see a single ntfs partition, sometimes it shows the ext3 partition, offering to reformat it.
bloodhound_ said:
The instructions I followed from Atrix page are very detailed. Link is here
It takes time to have a thread where most of the common questions answered. I think it is useless effort to start similar topic here, in addition - I don't have necessary time, knowledge and wish for this.
Anyway, if you do something wrong - you should always have full backup - then you risk nothing. Remember that if you got soft-bricked and recovery doesn't work, you can always use RSD lite to load stock 198_7 ROM, unlock, write new recovery and restore from initial backup.
The only difference between Atrix and Photon, (relative to this task) that you should keep in mind is the partition sizes. Partition table by LAKSHMAN in Play Market (or any other partition tool) can show you your partition sizes. I didn't guess to use these tools when I followed the instructions. Add up some 10 GB to each partition, just in case. When you partition your SD card, you should create partitions of the following size:
system - 420 GB (stock ROM system partition size 408 GB)
cache - 645 GB (my current cache size on stock ROM is 610 GB)
data - 2.6 GB
I would also recommend to use script manager to launch scripts that will replace boot image from one to another. In other words, it will control where you will boot next time.
Note that Windows 7 is going mad about SD card with several partitions - sometimes you can see a single ntfs partition, sometimes it shows the ext3 partition, offering to reformat it.
Click to expand...
Click to collapse
@PosterBoy : is this GB really?????? Man give some space to breathe..... lol
amitranjan said:
@PosterBoy : is this GB really?????? Man give some space to breathe..... lol
Click to expand...
Click to collapse
no im sure he miss typed he meant MB like he says in his post in the other thread. ok thanks man ill play around with it a bit so you're sure the phone wont be hard bricked right? I'm a very careful person I'm pretty confident I wont make mistakes all i want to know is everything every instruction given there is detailed enough and that nothing is omitted from it(meaning i dont have to do anything different except the partition sizes you mentioned here)
rituel said:
no im sure he miss typed he meant MB like he says in his post in the other thread. ok thanks man ill play around with it a bit so you're sure the phone wont be hard bricked right? I'm a very careful person I'm pretty confident I wont make mistakes all i want to know is everything every instruction given there is detailed enough and that nothing is omitted from it(meaning i dont have to do anything different except the partition sizes you mentioned here)
Click to expand...
Click to collapse
Yes, everything else from that topic applies. Be careful when you use dd. If you specify wrong drive names you might be in trouble (this will require loading sbf with RSD lite to fix partitions, I guess).
The longest part is to extract boot.img, edit the configuration file there and pack the whole thing back to andorid .img format. It requires you to install Android SDK with some tools that might not work straight away.
I am very familiar with the inner workings of CWM on regular phones, but these devices seem a bit different. Will formatting System brick the device by removing CWM from the partiton, or is it the same as a phone where CWM is in the kernel partition in boot? I ask because I have not seen any developers ask to format the system (along with factory reset/data/cache/dalvik) when going from GB to ICS, which on a phone IS the correct way to change operating systems.
Quick answer would be great as I am in flashing mode tonight!
Thanks
annoyingduck said:
I am very familiar with the inner workings of CWM on regular phones, but these devices seem a bit different. Will formatting System brick the device by removing CWM from the partiton, or is it the same as a phone where CWM is in the kernel partition in boot? I ask because I have not seen any developers ask to format the system (along with factory reset/data/cache/dalvik) when going from GB to ICS, which on a phone IS the correct way to change operating systems.
Quick answer would be great as I am in flashing mode tonight!
Thanks
Click to expand...
Click to collapse
It will not remove CWM. Don't forget, CWM is normally either on a separate partition (recovery) or for samsung devices, in the kernel directly, so It will not brick your device, it will just get to either to a infinite bootloop, stuck at samsung logo or reboot to recovery. In the case you should backup using nandroid before use.
That's what I figured, just wanted to be sure. Things are just different on these g-players. I like to use the system format option to get a true "clean" install.
Thanks for the quick response
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
annoyingduck said:
That's what I figured, just wanted to be sure. Things are just different on these g-players. I like to use the system format option to get a true "clean" install.
Thanks for the quick response
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
Click to expand...
Click to collapse
Most ROMs format the system while they are installing so you don't always need to do it manually
Sent from my Nexus 7 using XDA Premium HD app