unCoRrUpTeD DATA2EXT
&
A2SD BLASTER
DATA2EXT
What is data2ext?
data2ext was started as a way to move the entire contents of the data partition to an ext partition on the sdcard. It gives you a way to increase the size of your data partition and also increase benchmark scores. This should work on most phones as it detects the block location of the sdcard, regardless if it is /dev/block/mmcblk0 or /dev/block/mmcblk1.
SETUP
The following commands are optional and need to be put in before the 1st or 2nd boot
Make sure that the data partition is mounted before issueing the commands
Code:
adb shell
mount /data
*Converting to ext3 or ext4 on first boot
Code:
echo "extA" > /data/.d2ext
A is either 2, 3 or 4, depending on what ext format you want.
In the future you can convert to ext3 or ext4 even after data is on the sdcard.
*Formatting the ext partition on first boot to ensure a clean and fresh filesystem
(Note: This does not need to be done)
Code:
echo "extA format" > /data/.d2ext
A is either 2, 3 or 4, depending on what ext format you want.
*Create a custom read_ahead speed for the sdcard.
(Info on what it does can be found here courtesy of brainmaster)
Code:
echo XXXX > /data/.sdrw
XXXX is any value you want. By default it will be set at 2048.
You will need your sdcard partitioned with at least 1 ext partition. Either you can do that through your recovery or go here to download a script that will repartition without loosing your fat32 contents.
WARNING:
Due to some changes made, you will need to either backup your apps and do a fresh install or install over my data2extV1 script. Do not try and use the a2sd-copy-and-blast method at this time.
Install on a ROM you are currently running that has a2sd or data2ext enabled:
1. Reboot into recovery
2. Flash a2sd-copy-and-blast.zip
3. Flash data2ext.zip
4. Once your phone has booted, reboot again (This is to limit the time of the first boot and the setup won't be complete until you reboot.)
Install on a ROM you are currently running that has my previous data2ext installed:
1. Reboot into recovery
2. Flash data2ext.zip
3. Reboot your phone.
Install on a ROM you are currently running that does not have a2sd or data2ext enabled:
1. Reboot into recovery
2. Flash data2ext.zip
3. Once your phone has booted, reboot again (This is to limit the time of the first boot and the setup won't be complete until you reboot.)
Install on a fresh intall of a rom:
(It doesn't matter if it has a2sd or not as this will remove all a2sd scripts if they are present)
1. Reboot into recovery
2, Wipe everything
3. Flash ROM
4. Flash data2ext.zip
5. Reboot
6. Once your phone has booted, reboot again (This is to limit the time of the first boot and the setup won't be complete until you reboot.)
[/SIZE]
A2SD-BLASTER
unCoRrUpTeD-a2sd-blaster.zip: Use this one to remove a2sd from the ROM if you are doing a fresh install or want to keep all data on your ext partition for data2ext
unCoRrUpTeD-a2sd-copy-and-blast.zip: Use this one if the ROM your are currently running is using a2sd. It will remove a2sd from it and copy all apps from the ext partition back onto your phone's /data partition.
Changelog
data2ext-V2.2:Fixed issue with V2.1 freezing on boot, due to deleting /system/bin
data2ext-V2.1:Added a check for those already using data2ext
data2ext-V2:included checks if the ROM has the needed files, included the option to change the format to ext3 or ext4 on first boot, added sdcard read ahead tweak. Reboot needed after any install, added custom_backup_list.txt for new installs or updates
a2sd-copy-and-blast_V2:changed to move data back to phone along with apps
data2ext-V1: 1st release
a2sd-blaster: 1st release
a2sd-copy-and-blast: 1st release
i'm going to test on a fresh install of liquidsense and hopefully this works b/c i just switched back to gingerbread to get the speed of data2ext and i just installed all my apps again so hopefully you found the fix....i'll post back with results
sigh....bootloops.........i'm going back to gingerbread....
someday i wish someone could get app2sd removed so that i could have data2ext working on sense 2.1
kifno said:
sigh....bootloops.........i'm going back to gingerbread....
someday i wish someone could get app2sd removed so that i could have data2ext working on sense 2.1
Click to expand...
Click to collapse
I just downloaded and flashed liquidsense and then a2sd_removal.zip. Booted right up.
It does remove busybox.a2sd, but in all testing across several different phones that has not caused any problems as the regular busybox is still in the ROM. The copy_remove.zip was missing some code to mount data before copying over, but I changed that one as well.
unCoRrUpTeD said:
unCoRrUpTeD A2SD BLASTER
&
DATA2EXT
SETUP:
You will need your sdcard partitioned with at least 1 ext partition. Either you can do that through your recovery or go here to download a script that will repartition without loosing your fat32 contents.
If you are currently running a rom with a2sd of data2ext enabled you will need to reboot into recovery and flash a2sd-copy-and-blast.zip and then data2ext.zip
If you are doing a fresh install or running a rom with a2sd disabled or nonexistent then flash data2ext.zip
If setting this up after a fresh install you will need to reboot the phone after it has booted up. This is only done to speed up the first boot startup time. Once it is running you can do whatever you want, and on the next reboot it will set everything up.
A2SD-BLASTER
unCoRrUpTeD-a2sd-blaster.zip: Use this one to remove a2sd from the ROM if you are doing a fresh install or want to keep all data on your ext partition for data2ext
unCoRrUpTeD-a2sd-copy-and-blast.zip: Use this one if the ROM your are currently running is using a2sd. It will remove a2sd from it and copy all apps from the ext partition back onto your phone's /data partition.
Click to expand...
Click to collapse
OKay so is this the correct instructions:
- wipe everything
- partition sd card to have 512mb ext2 (that's what i always use for ext)
- flash fresh install of rom
- flash data2ext.zip
- then reboot into system?
or do i
- wipe everything
- partition sd card to have 512mb ext2 (that's what i always use for ext)
- flash fresh install of rom
- reboot into rom
- reboot recovery
- then flash data2ext.zip?
thanks for all they help you've given me
kifno said:
OKay so is this the correct instructions:
- wipe everything
- partition sd card to have 512mb ext2 (that's what i always use for ext)
- flash fresh install of rom
- flash data2ext.zip
- then reboot into system?
or do i
- wipe everything
- partition sd card to have 512mb ext2 (that's what i always use for ext)
- flash fresh install of rom
- reboot into rom
- reboot recovery
- then flash data2ext.zip?
thanks for all they help you've given me
Click to expand...
Click to collapse
Updated OP.
Should be pretty clear now.
before i dive into this, bro, some questions if you will:
this moves everything in /data to sd-ext right? by everything, does this include even dalvik cache?
if, for any reason, i decide or need to return everything back to internal storage i could simply flash a2sd-copy-and-blast right?
thanks in advance!
EDIT 1:
bootloop! htc legend on cm6.1 w/ darktremor a2sd; ext3 partition. restored everything to internal storage, flashed a2sd-blaster then data2ext-V1. after restart, bootloop ..will try on ext2 partition later
EDIT 2:
bootloop also on ext2..was really hoping this mod will work on my phone
maxq1 said:
before i dive into this, bro, some questions if you will:
this moves everything in /data to sd-ext right? by everything, does this include even dalvik cache?
if, for any reason, i decide or need to return everything back to internal storage i could simply flash a2sd-copy-and-blast right?
thanks in advance!
EDIT 1:
bootloop! htc legend on cm6.1 w/ darktremor a2sd; ext3 partition. restored everything to internal storage, flashed a2sd-blaster then data2ext-V1. after restart, bootloop ..will try on ext2 partition later
EDIT 2:
bootloop also on ext2..was really hoping this mod will work on my phone
Click to expand...
Click to collapse
I'll look into it as this is also part of my dual-boot script that I am working on, which means that if this doesn't work on certain phones then the dual boot scripts won't work on all phones.
^ cool, man! i'm waiting on that as well. thanks!
this didn't give me bootloops so you've completed that step
but this didn't work at all
here's what i did:
- partition sd card
- wipe everything
- fresh install NFX stock 2.31.651.7 oxed (without apps2sd)
- install data2ext.zip
- reboot into rom
- once i approached the initial lock screen, i did adb shell reboot
- then i signed into google
- let it sync and load
- then i check application storage and it said 136mb
- so then installed titanium backup from makret
- after install i checked internal storage
- it went down to 131mb!
summary: not only did internal storage not say like 4xxmb like it does when gingerbread uses data2ext w/ 512mb, internal storage didn't even say anything different than the stock amount of internal storage
also even if the interal storage didn't correctly say how much storage we had after installing 1 app i knew this zip didn't take affect b/c of the great lost in internal storage
again i testing on nfx stock 2.31.651.7 (without apps2sd and oxed) and this did not work
edit: after fresh install method i tried the method where the rom doesn't have apps2sd.....this still doesn't work
this would be awesome if i got this to work on my rom but it doesn't even work on my rom's base.... and you haven't fixed yet....but i'll be checking up on this for fixes whenever you release a fix
I might be able to get to it tomorrow. If not it will be Wednesday. Been hard at work on my dualboot script, which uses a very complicated method of determining how to set it up. I only need to make a couple changes to this and symlink everything differently. I'm going to download nfx's Rom without a2sd as I had been testing on his a2sd stock Rom.
Sent from my dual-booted liquidsense 2.1
unCoRrUpTeD said:
I might be able to get to it tomorrow. If not it will be Wednesday. Been hard at work on my dualboot script, which uses a very complicated method of determining how to set it up. I only need to make a couple changes to this and symlink everything differently. I'm going to download nfx's Rom without a2sd as I had been testing on his a2sd stock Rom.
Sent from my dual-booted liquidsense 2.1
Click to expand...
Click to collapse
After talking with TGF about getting this to work with sense roms he said we need the correct e2fsck for sense 2.1 roms and also the libext2fs.so file for sense. Then we need to make sure busybox is intergrated into the ron by default. He couldn't help me get those files so the rest was left up to me but he did correct the script for sense roms though. Thought. I'd share that with you so that you could try and get this working for sense roms on the hero CDMA after you complete your dual boot mod.
unCoRrUpTeD said:
Install on a ROM you are currently running that has a2sd or data2ext enabled:
1. Reboot into recovery
2. Flash a2sd-copy-and-blast.zip
3. Flash data2ext.zip
4. Reboot your phone
Install on a ROM you are currently running that does not have a2sd or data2ext enabled:
1. Reboot into recovery
2. Flash data2ext.zip
3. Reboot your phone
Install on a fresh intall of a rom:
(It doesn't matter if it has a2sd or not as this will remove all a2sd scripts if they are present)
1. Reboot into recovery
2, Wipe everything...
A2SD-BLASTER[/B]
unCoRrUpTeD-a2sd-blaster.zip: Use this one to remove a2sd from the ROM if you are doing a fresh install or want to keep...
unCoRrUpTeD-a2sd-copy-and-blast.zip: Use this one if the ROM your are currently running is using a2sd...
Click to expand...
Click to collapse
Sorry to sound noobish here, but I'm running AOSP 2.2.1 on my heroc. i have moved all my apps to internal using titanium backup (in preparation for this). i have formatted by sdcard using cwm 3.0.0.5, with a 512 MB partition and 0 (zero) swap. Now I want to flash your cool data2ext! Which one do I use?
Important note! I have already tried flashing GrammarFreak's data2ext (ext2 version), and for some reason it didn't take.
And just now when I go into terminal emulator,
Code:
su
and then
Code:
data2ext -- enable
I get the following: "data2ext already enabled but not active."
Does this mess things up terribly? Can I still flash your stuff?
Yours,
Jim
[email protected] said:
Sorry to sound noobish here, but I'm running AOSP 2.2.1 on my heroc. i have moved all my apps to internal using titanium backup (in preparation for this). i have formatted by sdcard using cwm 3.0.0.5, with a 512 MB partition and 0 (zero) swap. Now I want to flash your cool data2ext! Which one do I use?
Important note! I have already tried flashing GrammarFreak's data2ext (ext2 version), and for some reason it didn't take.
And just now when I go into terminal emulator,
Code:
su
and then
Code:
data2ext -- enable
I get the following: "data2ext already enabled but not active."
Does this mess things up terribly? Can I still flash your stuff?
Yours,
Jim
Click to expand...
Click to collapse
I haven't changed what is here. It might work, might not. I tested on a couple of roms and it worked, but didn't work on others. Nandroid first. Flash a2sd-blaster.zip which removes any instance of a2sd and data2ext. Flash data2ext.zip.
Like I said I haven't changed it yet. Been working on my dualboot script. So it might work and might not.
unCoRrUpTeD said:
I haven't changed what is here. It might work, might not. I tested on a couple of roms and it worked, but didn't work on others. Nandroid first. Flash a2sd-blaster.zip which removes any instance of a2sd and data2ext. Flash data2ext.zip.
Like I said I haven't changed it yet. Been working on my dualboot script. So it might work and might not.
Click to expand...
Click to collapse
That's completely cool. Thanks for taking the time to reply!
Yrs,
Jim
...perfect...
very good apps.... i ' m very happy....
now i have used data2ext on new installation of rom and work perfectly on ideos with 1gb ext4....
it's a beautiful utility for adding space to internal memory...
excellent...
later i try with an already installed rom with a2sd....
thank you very much!!!!
update: i have a problem, apparently all work perfectly but when i active wifi the cell reboot :-(
grifovunque said:
update: i have a problem, apparently all work perfectly but when i active wifi the cell reboot :-(
Click to expand...
Click to collapse
same problem with wifi..
on my ideos script runs very very well but when i enabled wifi my phone reboot..sigh
i hope that's you can fix it..
however thanks,great script!
Works semi-great on a heavily modded Sprint stock rom. Overall, it took a few reboots, but is working. I have 409mb available. The only issue I found is that AlarmDroid does not work. I tried moving it to system/app and still not loading...i may try moving it in the actual rom, reflash everything and see what happens. The offending apk is not your fault by any means, just listing what I came across. I flashed the zip after I used your sd partitioner. On first reboot after flash, phone was normal...read that you said it takes another reboot, so I performed another reboot. On 2nd reboot, the whole system FC (just about every app came up and FC), performed another reboot. On 3rd reboot, AlarmDroid complained - but everything seemed fine...did a few more reboots, but it looks like the 3rd is the magic number for my rom...I may include this in my personal rom (obviously removing duplicate files like bb
I have one request and that is to make it more like the other scripts and allow it to be enabled, or not enabled. I am not saying have an on/off switch as the scripting for that would be extremely complicated, but have an off until enabled on switch for those looking to throw this in a rom. It is possible to put this in a rom, but some may not want it enabled right off the bat (like me)...Could it be possible to have an enabler script that upon running would move files where they needed to go? Like for instance have the tmp folder, add a file called enabled2e (or something) that runs mountpoints.sh and moves /tmp/50data2ext to system/etc/init.d...I dunno, just spitballing
evilvoice said:
Works semi-great on a heavily modded Sprint stock rom. Overall, it took a few reboots, but is working. I have 409mb available. The only issue I found is that AlarmDroid does not work. I tried moving it to system/app and still not loading...i may try moving it in the actual rom, reflash everything and see what happens. The offending apk is not your fault by any means, just listing what I came across. I flashed the zip after I used your sd partitioner. On first reboot after flash, phone was normal...read that you said it takes another reboot, so I performed another reboot. On 2nd reboot, the whole system FC (just about every app came up and FC), performed another reboot. On 3rd reboot, AlarmDroid complained - but everything seemed fine...did a few more reboots, but it looks like the 3rd is the magic number for my rom...I may include this in my personal rom (obviously removing duplicate files like bb
I have one request and that is to make it more like the other scripts and allow it to be enabled, or not enabled. I am not saying have an on/off switch as the scripting for that would be extremely complicated, but have an off until enabled on switch for those looking to throw this in a rom. It is possible to put this in a rom, but some may not want it enabled right off the bat (like me)...Could it be possible to have an enabler script that upon running would move files where they needed to go? Like for instance have the tmp folder, add a file called enabled2e (or something) that runs mountpoints.sh and moves /tmp/50data2ext to system/etc/init.d...I dunno, just spitballing
Click to expand...
Click to collapse
Creating a flag to enable or disable is pretty simple. Not sure if I put one in there. I'm not looking at it right now. All it needs is ...
Code:
if [ -f /data/.data2ext ];then
xxxx -------
xxxx /
xxxx | Existing commands
xxxx \
xxxx -------
else
# move everything back to /data
cp -a /xxx/xxxx/* /data
exit 0
I'm going to update this at one point with some checks and a different way to mount everything, which will reduce the overall script size and make it more compatible with more roms and phones. It's been a while since I looked at it , but I know that I include busybox in somethings as it has more functions than what is normally provided in the roms.
Related
WWARNING:You must Have The Correct Radio and Latest SPL! You can find them here (RADIO MUST BE INSTALLED FIRST) You can find it here
PLEASE DO YOUR RESEARCH BEFORE FLASHING ANY ROM INCLUDING MINE!!!
Please give credit if you use my work
This ROM is built from the WWE HTC Hero leak.
As with any other ROM there is a risk involved in the process, I'f you have any doubts you should just leave it alone or do some more research and get comfortable with what you are actually doing before proceeding!
Me and Drizzy will be teaming up to bring you new releases from now on. Soon 2.4 with alot more modifications, new kernel etc but untill then its BT time
DrizzyJAC r2.3.6
-Drizzy/JAC collab
-Pretty much the same as 2.3.5 but with framework/.apk's optimized
-Changed a2sd config to try and decrease loops
-/system/media moved to sdcard
JACHero r2.3.5
-app_s now moved to the sdcard @ system/sd/data/app_s
-Modified Rosie from coolbho3000 (thanks)
-CPU freq modifications in init.rc thanks to Cyanogen
-No longer overclocked by default set @ 384
-SMSReceiver service set to Highest priority
-Busybox only @ /sbin now
-apns-conf.xml update
-AudioFilter changes (should slightly increase volume and lower mic sensitivity)
-Added userinit.sh run support
-3G icon instead of H for Data
-App setup reverted to WWE format, only 3rd part apps in /data/app
-Cleaned up a2sd.sh script to prevent mounting and parsing redundancy and removed unneeded code for Hero builds
-Cleaned up update-script
***KNOWN ISSUE - use 3G/Edge to accept TOS for Market no WiFi, also first browser page on Wifi doesnt want to load at first on WiFi, go to any other site and you should be good
***Also swapper at 32/60 seems to be a sweet spot
JACHero r2.3.3
-Modified Rosie.apk
-db.hates.you custom wallpaper for JACHero
JACHero r2.3.2 - Had to pull the modified Rosie before releasing 2.3.2 it will be done soon.
-Removed cache_pressure from sysctl.conf
-Reverted AudioMOD
-updated contributors.html
JACHero r2.3.1
-replaced BT firmware in system/etc/firmware
-Max CPU set to 528
-APN changes in system/etc
-sysctl.conf changes system
-cleaned up unused/unneeded files in system/etc
-AudioMOD in /system/etc
-BT changes to enable pramods BT fix
-HCItool added to /system/bin to enable pramods BT fix
-Boot.img changes to conform to pramods BT fix
-removed launcher.apk/.odex
-removed learnmore.apk/.odex
-removed footprints/footprintswidget .apk/.odex
-removed HTCsync
JACHero r2.3
-Auto APPS2SD w/EXT2/EXT3 included script @ /system/bin/a2sd.sh
-2.6.27 Kernel - will be moving back to 2.6.29 eventually
-RAMDISK modifications
~auto mount for EXT2/3 partitions with noatime, nodirtime
~Updated sbin
~updated Trigger Binary
~calls to /data/init/rc system/init/rc
~PATH changes
~BlueTooth changes from Hero init.hero.rc and init.rc imported
-DalvikVM optimized
-Superuser Binary
-SD card placeholder
-BusyBox
-Added APN's for T-mobile users (SMS fix inlcuded in apn-conf.xml Thanks Horrorwolf)
-Trout keymappings
-Camera replaced with working Hero camera (still has rotate issue)
-Updated trout gps
-Multi-Touch
-Working WiFi
-Flash 9
-Audio libs updated (working audio and HTCMusic.apk)
-build.prop modifications to reflect proper device
-Sensor updates for Auto-Rotate (TouchFlo still won't rotate of course)
-sysctl.conf added to /system/etc
-auto backlight turned off by default in build.prop
-Wifi tether
-Swapper included
-changes to /data/app removed any .odex'd apps due to upgrade issues
-/system/lib files updated
PLEASE SUBMIT BUGS HERE http://code.google.com/p/jacheroplus
**********PLEASE READ BEFORE INSTALLING*********
Please use Cyanogen's recovery image!
Make sure you have a partitioned SD card with a FAT32 partition and a EXT3 partition. (EXT2 is supported also) If you do not this ROM will install but you will have little space left due to APPS2SD not running. I personally like the clean slate location for Hero and then i use the widgets i need if any.
When I install I check the ext filesystems first, if it tells you to go to console to manually check do it! After I've repaired the EXT partition or if it didn't need repair I will now wipe and then apply the update and reboot.
A walkthrough by forum member sxfx is posted one post below for install.
ALSO run as few widgets as possible folks!
DOWNLOADS
JACHero r2.3.6 SYM/BIND APPS2SD - MD5: 2A64747A1048FD175B1C1667D17E50FA
http://www.justanotherdev.slackdev.com
http://altepeter.com/justanotherdev/JACHero2.3.6.zip
JACHero r2.3.5 SYM/BIND APPS2SD - MD5: D80155D128ECCD3010768B52D9FB8EC0
http://www.justanotherdev.slackdev.com
http://altepeter.com/justanotherdev/JACHero2.3.5.zip
JACHero r2.3.3 SYM/BIND APPS2SD - MD5: 417ADE957153FD0BE5F3C7C9816B276F
http://www.justanotherdev.slackdev.com
http://altepeter.com/justanotherdev/JACHero2.3.3.zip
JACHero r2.3.2 SYM/BIND APPS2SD - MD5: a05c4d8d5abccd19c416b6febe40d6d2
http://www.justanotherdev.slackdev.com
http://altepeter.com/justanotherdev/JACHero2.3.2.zip
JACHero r2.3.1 SYM/BIND APPS2SD - MD5: 28f0afcc47d7766c71ecdb71e74e332a
http://www.justanotherdev.slackdev.com
http://altepeter.com/justanotherdev/JACHero2.3.1.zip
JACHero r2.3 SYM/BIND APPS2SD - MD5: D40A33ED2B1DED9181E1EA7B0AA96CC4
http://www.justanotherdev.slackdev.com
http://altepeter.com/justanotherdev/JACHero2.3.zip
JACHero r2.2.1 SYM/BIND APPS2SD - MD5: 35ad30f844862fb559ffcddadd4d49d2
http://www.justanotherdev.slackdev.com
JACHeror2.2.1 Fatality Merge SYM/BIND APPS2SD - MD5:87b22fc0baf6fc4138c48114388990b5
http://www.justanotherdev.slackdev.com
Thanks to daproy, JesusFreke, Cyanogen, Haykuro , xDan, Sangeet.003, Twisted Umbrella, and everyone else in the android community helping out.
If you like my work visit me at my Twitter.
No Off-Topic Posts!!!!!! This is not a general support thread!!!!
CREDIT:sxfx
Ok Guys.
I created this thread cause in the JACHero thread on at least every page everyone asks how to install it, what am I doing wrong, and why is it broken.
So let me give you step by steps of what exactly I have done for me and others to run Hero with out a problem. I will also create a thread with step by step on how to use Ubuntu Linux Live distro to partition your card.
Things you will need to make this work.
Your Brain
G1 Phone
SD Card reader
And the files I included in this thread.
My phone right now is running.
JACHero 2.3
NEW SPL
cyanogens recovery 1.2
8gb class 6sd with Swapper(Swap file on ext2 sd)
setCPU slightly overclock.
Results.
Ever since I did my new Buttons, and the SPL I included in this write up, I have not had one problem flashing any hero rom at all on my phone, nor did I ever have problem actually running hero roms.
So here goes.
First before you partition your card or do anything make sure your card is at least portioned to fat32, don't worry about any other partitions yet.
OK once you do that go ahead and take the radio zip file I am including in this thread and flash it on your phone.
But first make sure you don't already have new radio installed which is 2.22.19.26I THIS IS VERY IMPORTANT. To check what radio you have, power off your phone, and power it on while holding the camera button.
If you do have new radio you can continue on to flashing the new SPL.
Flashing your SPL. (PLEASE MAKE SURE YOU HAVE THE NEW BUTTONS INSTALLED)
Ok this is where it might get a little tricky, and you might require a SD card reader I know I did and frankly I think this is the best way to do it and I recommend every time you do put a new update on your sd card to update your phone do it through a card reader.
Now after you flash your SPL you might or I should say more then likely will get stuck at the T-Mobile G1 screen, this also might happen after new radio flash in the previous step. If this is the case do not freak out it's normal and your phone is not bricked, but this is why having a sd card reader is important.
Ok so Here is what you do after you have flashed new Radio and SPL(Note:The steps on running Linux live distro and using it to partition your card is coming up). Boot up Live distro of Ubuntu, when its done booting, go ahead and go into the partitioning program while your sd card is hooked up in the computer.
Go ahead and set up two partitions at this time. One EXT3, and of course the other one Fat32. Your ext3 partition doesn't have to be all that big. I actually have mine set up to 512.
Once you are done creating partitions, go ahead and put the latest JACHero on the FAT32 portion and flash away (don't forget to rename to update.zip).
At this point if you follow all of these steps there is no way possible that your phone should not boot right into the system to run the initial setup.
These steps pretty much walk you through steps as if you were starting with a phone that has completly nothing on it.
Also the first boot up after flashing the new ROM, might take a few mins at the HTC screen.
Once your phone loads up and you go through the setup process go ahead and run swapper, it should be an APP that's already pre-installed.
Once you run swapper go into the setting and change the location of your swap file from /sdcard/swapfile.swp to /system/sd/swap.swp
Here is the reason why. The default location is your FAT32 partition. If you all of a sudden mount your phone to the computer with the swap file running on FAT32 you will corrupt your sd card, and then you will have to wipe and reinstall everything.
If you set the location of your swap file on /system/sd/ that's actually your ext2/3 partition and never gets mounted and you never have to turn swapper off.
Well I hope this helps some of you out. I will be writing the walk through on loading up live distro of Linux and partitioning your card sometime today.
I have used this method on a couple different phones and it has worked each time. Also I really recommend installing cyanogens recovery 1.2, as its an excellent way of making a back up of your phone and doing future flashing.
If there is anything anyone thinks that could be done better feel free to post in here.
Remember different people have different ways. I have posted this way cause it has worked for me on my phone and two other phones I setup, and each time there was no hicups.
FILES:
Radio 2_22_19_26I
NEW SPL
CM-Recovery-1.2
Ubuntu Linux Download
DISCLAIMER:
I am not responsible for anything that you might have done to your phone by following these directions. Like I mentioned before so far every time I have used this method, I have had nothing but success.
================================================== =============================
XDA Users, KEEP THIS THREAD ON TOPIC OR IT TOO WILL GOTO THE TRASH!!!
================================================== =============================[/CENTER]
ArmandHammer said:
old one is on this site and on the market,
the new one is also on this site and on the market,
just search
Click to expand...
Click to collapse
at least u can tell me what should i search for in the market....?
ArmandHammer said:
CHMOD didnt work for me,
chmod did,
ill report back on the apps to sd
After using the old apps2sd app i got an infinite loop.
Click to expand...
Click to collapse
Yeep I was running into the same problem. It wasn't working for me in upper case either. It started working once I did it as
su <enter>
chmod 777 /data/app <enter>
exit <enter>
exit <enter>
I think it should be noted on the first pase that chmod 777 should be in lowercase.
zgmf-x322a said:
at least u can tell me what should i search for in the market....?
Click to expand...
Click to collapse
AppsToSd search that in the market(old version)
I didnt buy the new one, its in the new and improved apps to sd thread
Alright back on topic
Okay so 1.4 is out now. He says Apps2Sd is included. I've never used Apps2sd and really don't know how to. So do I have to do anything with the 1.4 build to move it onto my sd card or will it automatically do it for me?
Run the APPS2D app with your EXT2/FAT32 partitioned SD card in and reboot that is all.
To make sure it is mounted go to the Terminal and type df, you should see
system/sd with your partitions size attributes etc
EXT3 support is next on the list.
justanothercrowd said:
Run the APPS2D app with your EXT2/FAT32 partitioned SD card in and reboot that is all.
To make sure it is mounted go to the Terminal and type df, you should see
system/sd with your partitions size attributes etc
Click to expand...
Click to collapse
Perfect thanks! Is this the only difference in 1.4? So I have to create the partition myself first correct? I thought Apps2sd created the partition for me. Oh well let me go create the partitions lol.
PS: the CHMOD command doesnt seem to work in upper case. Lower case only.
So will this new Rom with the app2sd app move everything but leave rosie.apk & launcher on the phone memory? Or is there something else that needs to be done?
justanothercrowd said:
Run the APPS2D app with your EXT2/FAT32 partitioned SD card in and reboot that is all.
To make sure it is mounted go to the Terminal and type df, you should see
system/sd with your partitions size attributes etc
EXT3 support is next on the list.
Click to expand...
Click to collapse
thanks a lot, you are doing it just right
question, if my apps are already in ext2 (system/sd/app) will it work? or they will now be located in : system/sd/app_s ?
thank you
Somebody respond with how much available space they have left after running the APPS2SD.apk
i've chmod 777'd the hell outta my system/app folder and I still can't download apps. I've run the command from terminal on phone from ADB Shell, from inside the folder, from the root, as root every possible way and I still can't download anything.
Would it make a difference if I had tried downloading from market before applying commands?
I did a lot of testing and left all the files needed to keep this ROM stable and FAST under /data/app_s
Somethings work better under the app_s directory un-linked.
Everything else is under /data/app like a normal ROM so normal APPS2SD methods work. Since Marcus already has the app up I just included it...its only 18kb anyways.
This isnt off topic but an inquery to the EXT3 comming soon
Here is a question. Everyone is head over heels about using ext3 which is understandable. But why when i create and use an ext3 partition, why does everything running from my sd slow down by far?
i have 2 partitions on my sd ones an ext2 ones ext3 if i switch my link to m ext partition everything is fine.. if i switch it to my ext3 it gets about .5x slower
rahduke said:
i've chmod 777'd the hell outta my system/app folder and I still can't download apps. I've run the command from terminal on phone from ADB Shell, from inside the folder, from the root, as root every possible way and I still can't download anything.
Would it make a difference if I had tried downloading from market before applying commands?
Click to expand...
Click to collapse
If it means anything i tried to download an app then forgot about the commands, typed the commands and it worked.
I've posted this before, but got no response.
Is anyone else having trouble getting wifi turned on? I can actually use the Wifi tether app, but just trying to turn it on myself, it fails.
Thoughts?
Bryan
TheGeekNextDoor said:
I've posted this before, but got no response.
Is anyone else having trouble getting wifi turned on? I can actually use the Wifi tether app, but just trying to turn it on myself, it fails.
Thoughts?
Bryan
Click to expand...
Click to collapse
i tried moving and linking the local file once and that made my wifi never be able to turn it on until i deleted the link and moved it back
ArmandHammer said:
If it means anything i tried to download an app then forgot about the commands, typed the commands and it worked.
Click to expand...
Click to collapse
did you reset after commands?
fleshdeep said:
Somebody respond with how much available space they have left after running the APPS2SD.apk
Click to expand...
Click to collapse
43 mb AWESOME!!! the apps to sd works now in v1.4 great job.
did you reset after commands?
Click to expand...
Click to collapse
i just ran the commands and then pressed exit twice.
pentace said:
i tried moving and linking the local file once and that made my wifi never be able to turn it on until i deleted the link and moved it back
Click to expand...
Click to collapse
I've learned a lot about linking, but I am not sure what local file you are refering to that would make my wifi work for me. Any help is appreciated.
Bryan
Introducing...
Darktremor Apps2SD 2.7.5.3 Beta 04
Date of Release: January 29, 2011
Download Current Version
Instructions - Change Log - Commands - ROM List - Developer's Guide
Darktremor Apps2SD Fan Page ----
Darktremor Apps2SD Development Group
Are you installing Darktremor Apps2SD on your phone? Here are the instructions to help you: Facebook
Are you a developer wanting to include Darktremor Apps2SD in your latest ROM? Here is the Developer Guide: Facebook
Click to expand...
Click to collapse
Update on Beta 4
It seems I'm getting mixed results with these betas. I'm not sure why this is occurring, some people have been able to get this working right while others have had a hard time with it.
Currently, I'm rebuilding the entire program. This takes a while because I have to figure out how to pack all these options into the program but make it small enough to where it will run correctly.
I will say that some of the beta features are coming back out...one of them is the search for a partition code. I suspect that code may be leading me into issues with certain platforms, so I'm going back to the 2.7.5.2 method of mounting (mmcblk0p2 or mmcblk1p2).
Also, parts of the code will use Busybox Ash (the only code that won't will be starta2sd, which will still use Bash for the time being). The startup code will definitely use Busybox Ash.
Until then, here are the links to the the last two betas and the last official release:
Version 2.7.5.3 Beta 04 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip
Version 2.7.5.3 Beta 03 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03-signed.zip
Version 2.7.5.2-1 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-1-signed.zip
And, if you want past versions, you can view the repository: ftp://dtuser:[email protected] (ignore the smiley face...that's XDA doing that.)
Click to expand...
Click to collapse
Beta 04 took longer than I expected to release. I have done major changes to the code:
1. New commands: convert-ext4 - This will convert your EXT3 partition into EXT4. Just a friendly reminder on this command: Not every rom supports EXT4, so it is possible to go into a boot loop if you switch roms. Use with caution.
2. Reworked convert-ext3 (convert-ext4 gets similar code)...now a flag file is set before the reboot (no conversion is done before the reboot). At load time, the conversion is performed. This takes longer in the reboot process and you may think your phone has locked up...wait about five minutes before doing anything with the phone.
3. Repair is rebuilt...now it uses existing commands to repair the setup (reinstall, remove, cachesd, cachepart, nocache, datasd, nodata). Definitely shrinks the code.
4. Added fix_permissions program to the package. This may help with Superuser issues when using the datasd feature. It is used in reinstall, remove, datasd and nodata.
5. a2sd install is back!!! Both a2sd install and a2sd reinstall do the exact same thing.
6. Dalvik heap code has been shrunk and now creates a file called dalvikheap. Actually, the code has been doing this all along (since about 2.7.5.2, I think), but I never put the code in to use the file.
7. Low Memory Killer code has also been shrunk and uses a file caled dtset_lowmem to set the low memory killer parameter.
8. Replaced Busybox PS function with Toolbox PS. The issue with Busybox PS is that it gives a false reading when I look for android.process.acore (which is the main program when the GUI starts up). If that is present, the program thinks you are trying to run Darktremor without any command line parameters. This was because Busybox would report the process was there when, in reality, it wasn't (validated this when my phone was boot looping.) Toolbox's PS reports the correct setting. This should fix the bootlooping issues some people are experiencing.
9. New commands: usedtbusybox and usedefaultbusybox - these commands may help in diagnosing issues that is may be related to the native Busybox on your rom. a2sd usedtbusybox will use the Busybox that is packaged with Darktremor. a2sd usedefaultbusybox will turn back on the scan behavior of the program introduced in Beta 03.
10. Support for Darktremor Apps2SD version 2.7 and earlier has been discontinued. To upgrade correctly from one of those versions, use version 2.7.5.3 Beta 03b or earlier.
11. Finally fixed stalled boot issues (or at least my tests with several roms says so.)
See the change log for additional details.
You will notice that if the program runs repair and finds a problem, it will correct the issue and reboot. You will see a second reboot when the dalvik-cache clears (this is to fix timing issues with CyanogenMod...I can't control that startup as well as I can other roms). This only happens if repair is ran or you flash a new rom (as repair will realign all data). If you are upgrading from a previous version of Darktremor, you should not see the reboots.
Click to expand...
Click to collapse
This is Darktremor Apps2SD, a multipurpose program that primarily allows a user to execute applications created for the Android OS on their Secure Digital card (with the proper setup...more on that later). But, Darktremor Apps2SD is all about stability. The goal is to be able for all users of the Android OS to be able to take advantage of a method to run their applications from a secure digital card.
But just because the Darktremor Apps2SD is all about stability, doesn't mean it isn't packed with features:
- Move applications (both free and paid) to the Secure Digital card.
- Move Dalvik Cache to run either from your Secure Digital card or from your cache partition and clears the cache on demand.
- Boot Loop Protection: prevents the phone from boot looping in the event the SD card could not be mounted.
- Dalvik JIT for faster performance on Roms which support it.
- User selectable sizes for the Dalvik heap sizes, allowing a user to freely optimize their system.
- Activate a swap partition on your SD card and sets how often the swap partition is utilized.
- Automatically fixes configuration issues.
- Users can check the free space on their SD card and check the installation to make sure all is setup correctly.
- Runs ZipAlign on demand...this makes your programs load faster.
- Built in help system for easy reference of commands.
- All features can also be reversed without repartitioning your Secure Digital card.
- New logging features assists in troubleshooting issues.
- Commands to set the Low Memory Killer feature at boot time. Great for those people who are the "set it and forget it" type.
- And more...
Darktremor Apps2SD is not the same as Froyo Apps2SD. Froyo Apps2SD creates a secure folder on the FAT32 section of your SD card (this is the section that you see when you mount your phone to your computer) and stores the programs there. This is nice as you don't have to do anything special with the phone, but it isn't backwards compatible with older versions of Android (Cupcake, Donut, Eclair) and, because of the way Froyo works, older programs not designed for Froyo will automatically stay on your internal storage (unless you install a program that forces the move to your SD card).
Darktremor Apps2SD takes a different approach. Based on the original CyanogenMod works, Darktremor Apps2SD uses symbolic linking to force Android into moving your applications to the SD card. Because Android will not allow anything to be ran from the FAT32 partition on your SD card (and, in Froyo, it will only allow you to run programs from a special folder), Darktremor utilizes filesystems called EXT2, EXT3 and EXT4. Each one of these filesystems is native to Linux (the operating system running Android), which allows you to run programs from them (same as, say, a computer running Ubuntu). This method is completely compatible with all versions of Android, including Froyo. In fact, you can run both the Darktremor Apps2SD and Froyo Apps2SD at the same time.
Check out the list of Roms that either have Darktremor Apps2SD installed or are compatible with Darktremor Apps2SD. Click on the link labeled ROM List at the top of this message.
Looks good! Gonna try it out after ROM update!
Perfect on latest leedroid and very very fast.good job
Sent from my Desire HD
Bump---new version released.
What kind of SD card would you recommend? I mean which class? Class 2 is too slow,isn't it?
Sent from my Desire HD using Tapatalk
tkirton said:
Bump---new version released.
Click to expand...
Click to collapse
Just yesterday i have flashed beta 02 and all is ok but how can i upgrade to beta 03?
Thanks
Simply download it and install it like you did with Beta 02. It should retain all your settings, so you won't have to type any additional commands.
mattiadj said:
Just yesterday i have flashed beta 02 and all is ok but how can i upgrade to beta 03?
Thanks
Click to expand...
Click to collapse
I personally recommend Class 6 or better, although I've seen people use lower classes before.
lenthele said:
What kind of SD card would you recommend? I mean which class? Class 2 is too slow,isn't it?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
tkirton said:
Simply download it and install it like you did with Beta 02. It should retain all your settings, so you won't have to type any additional commands.
Click to expand...
Click to collapse
Thanks!
So I have not to remake DC?
Sent from future
No...if your Dalvik-Cache settings are already set, then it will keep dalvik-cache where it is. If it's installed on the SD card, it will still be on the SD card when you upgrade.
That Dalvik-Cache reset was a result of an earlier version (before 2.7.5.2, I believe) installer program resetting it back to internal storage. That didn't work out so well and the code was removed from the installer.
mattiadj said:
Thanks!
So I have not to remake DC?
Sent from future
Click to expand...
Click to collapse
Ok so what are real benefits of upgrade?can I wait for 04?
Sent from future
Sure, you can always wait for Beta 04 if you feel it would be better to wait. Some people like release versions and others will wait until later in the beta process (version 2.7 went through 10 beta phases before it was released).
mattiadj said:
Ok so what are real benefits of upgrade?can I wait for 04?
Sent from future
Click to expand...
Click to collapse
Bump...new version 2.7.5.3 Beta 04 released.
How can I check if I have a partition on my SD card?
Assuming that your SD card is on device block mmcblk0, you do the following:
Busybox fdisk -l /dev/block/mmcblk0
(that's a lower-case L, not an upper-case I or a number 1).
You're looking for something labeled Linux native. Probably associated with device mmcblk0p2.
kamranh3 said:
How can I check if I have a partition on my SD card?
Click to expand...
Click to collapse
Hi,
Tried it with no success on MIUI 1.1.28 with custome kernel 2.6.32.28
I followed the instructions to flash but when rebooted I checked the A2SD and it was not active or installed.
I used adb shell and looked under /system/bin for a2sd, which was missing.
Checked under MIUI settings for System/SDCard/A2SD+ and it reports no A2SD: is supported
Any ideas on how I'll make it work on Desire HD MIUI 1.1.28 ?
Try reflashing again...if you don't see /system/bin/a2sd, then your flash didn't take.
gvelim said:
Hi,
Tried it with no success on MIUI 1.1.28 with custome kernel 2.6.32.28
I followed the instructions to flash but when rebooted I checked the A2SD and it was not active or installed.
I used adb shell and looked under /system/bin for a2sd, which was missing.
Checked under MIUI settings for System/SDCard/A2SD+ and it reports no A2SD: is supported
Any ideas on how I'll make it work on Desire HD MIUI 1.1.28 ?
Click to expand...
Click to collapse
tkirton said:
Try reflashing again...if you don't see /system/bin/a2sd, then your flash didn't take.
Click to expand...
Click to collapse
I use 2.5.3 CWRecovery to flash from SDCard. I have tried at least 3 times and always see on the flash screen a number of lines with tick boxes but only the last one ticketed.
Do I need to do mount System first while in recovery ?
What else should I check ?
Ok... I mamaged to make it work
I had to manually mount the System & Data partitions and then flash the zip file
Then on first reboot and after the Bootanimation screen I got a 2nd rebooted again. After the second time all worked as expected.
so now MIUI 1.1.28 can recognise A2SD+ menory of 480MB
The problem I have is that uninstall is disabled for most applications.
How do I fix this ?
gvelim said:
How do I fix this ?
Click to expand...
Click to collapse
Wiped all, re-flashed the Rom followed by the a2sd zip before first reboot.. then rebooted
The handset rebooted 3 times on its own before I saw the lock screen. Then restored apps from titanium backup.
All super now.
Sent from my HTC Desire HD using XDA App
Dual Boot Support
DualBoot Helper APP is now on the market! (See bottom of this post for more info)
DISCLAIMER: I am not responsible for anything, ever. It is not my fault if you do not read. I do not explain things because I enjoy banging on the keyboard. If you do not read this entire post before jumping in then do not expect me or anyone else to be much help. By following this guide and any links YOU assume all responsibility for your device and anything that happens with it.
What is it?
Dual booting allows you to run two separate roms on your device at one time. It is done by intercepting the mount points during the startup of the device. This is accomplished by checking the sdcard for a specifically named file when the kernel first loads and uses the appropriate files to boot with the correct partitions. Reading from the sdcard is slower than reading from the internal memory of the phone so the speed of your sdcard will drastically determine the speed any rom runs. On the same note a rom flashed to the sdcard will take longer than usual on the first boot.
What does it do for me?
Running two separate roms has many uses for just about everyone. Users can use dual booting to try different roms, themes, apps, modifications, or anything while keeping their existing installation intact. The uses are just about endless. Besides testing different roms, this allows the user try these things and make sure they are compatible and stable before pushing the changes to their internal memory. Rom developers have all of the above options plus a few. Rom developers can additionally use dual booting to test builds of their roms without fear of soft bricking their device. For advanced users, you can mount the partitions of the other rom (be it sdcard or internal) and fix bad apk files or messed up files. The options really are limitless!
What do I need?
Sdcard 2GB or larger
Dual boot compatible kernel
Other things I should know...
*The kernel MUST support BOTH roms you flash. Unfortunately this means you can NOT mix froyo and gingerbread roms. Make sure you know what the kernel supports before you flash anything!
*If you compare roms, benchmarks will hold no value due to the sdcard being so much slower than internal memory.
*Faster sdcards will perform better than slower ones. Note: the stock 16GB sdcard is a class 2 which simply classifies it's minimum speed. A higher class sdcard will more than likely perform faster but the class rating is a minimum and not a maximum. It is entirely possible that a certain class 2 card can out perform a different class 6 card. Keep this in mind when researching to buy a new faster sdcard. More info in this post.
*First boot takes longer than usual. Up to 15 minutes! Please wait until the rom boots and the initial media scanner is done before you judge usability.
*Using a rom from the sdcard will cause the sdcard to wear faster. This is due to many more reads and writes of data than normal. The Epic simply does not have the internal capacity to run dual roms on the NAND. That being said the sdcard is our next option. While it may reduce the over all life of the sdcard keep in mind there are other android devices like the Nook Color and the other Galaxy S phones that have internal sdcards running the Android operating system. My personal opinion with is with other devices running off internal sdcards and with the price of sdcards getting cheaper and cheaper it was worth it to explore this option for the Epic.
Ok ok, so how do I get started?
I am going to break the steps down into sections. Please read everything to ensure you understand what all is involved in getting everything working. I recommend making a backup in Clockwork Mod and saving it to your PC before you even get started.
Section 1 - Setting up the environment
Step 1. Flash a compatible kernel (Kernel developers, PM me if you add my dual boot support to your kernel and I will update the list below) Remember you can NOT mix a eclair, froyo, or gingerbread roms and the kernel MUST support both roms!
Currently compatible kernels:
Genocide 2.0 Supported Roms: EC05, EB13, and DK28
Section 2 - Preparing sdcard
Important information!!!! This will destroy ALL data on your sdcard so if you lose pictures of your dog, cwm backups, nudies of your spouse, etc then you can't blame me. BACKUP YOUR SDCARD!
The easy way:
Reboot into recovery mode with a program like Rom Manager, Quick Boot, or type 'reboot recovery' from a terminal. (NOT 3-finger boot to recovery...this will NOT work)
The easy way WILL erase your sdcard with NO confirmation....you have been warned!
Choose one of the following flashable zips to automatically partition your sdcard
DualBoot_Partition_RFS.zip
DualBoot_Partition_EXT4.zip
The manual way:
Reboot into recovery mode with a program like Rom Manager, Quick Boot, or type 'adb reboot recovery' from a command line. (adb commands assume you have a working install of the Android SDK)
While in recovery issue the following commands:
Code:
adb shell
cd /sbin
./dbpart.sh --help
I put many hours into the partitioning script to make it as simple to use as possible. Simply follow program usage instructions.
Section 3 - Preparing a rom
Since we have blank partitions on the sdcard we need to populate them with data. There are multiple ways to accomplish this and you can choose which solution best suits your needs. I am not going to cover ALL methods here but enough to suffice any likely scenario needed.
The dd method will clone your current setup to the sdcard (these commands may take up to 15 minutes)
The easy way:
Flash this dd script: DualBoot_Clone_to_sdcard.zip
The manual way:
Code:
adb shell
dd if=/dev/block/stl9 of=/dev/block/mmcblk0p2
dd if=/dev/block/stl10 of=/dev/block/mmcblk0p3
dd if=/dev/block/stl11 of=/dev/block/mmcblk0p4
Preparation is complete. Please skip down to booting from sdcard.
The flash method is for flashing a new rom to the sdcard.
The easy way:
There is no sure fire easy way just yet. Stay tuned though.
The manual way:
This method is not that difficult so there is no need to be intimidated by it. It requires editing a few lines of the script that Clockwork Mod executes when flashing a rom or addon. For this example I am going to use a file named epicrom.zip but you can use any name you wish.
Step 1. On your PC, open epicrom.zip (I recommend using a program like 7zip)
Step 2. Navigate to the META_INF\com\google\android\ folder.
Step 3. Drag the file updater-script out of the zip to your desktop.
Step 4. Open the updater-script file with a text editor such as notepad (I recommend notepad++ or textpad)
Step 5. Change every instance of /dev/block/stl9 to /dev/block/mmcblk0p2
Step 6. Change every instance of /dev/block/stl10 to /dev/block/mmcblk0p3
Step 7. Change every instance of /dev/block/stl11 to /dev/block/mmcblk0p4
Step 8. Delete the entire line for any lines that contain /dev/block/bml7 or /dev/block/stl7 to disable flashing another kernel and breaking dual boot support.
Step 9. Save the file and drag and drop it back into epicrom.zip and let it replace the old one.
Note: If you get a status 6 or some other error when trying to flash it is likely you made a typo or your text editor did no save the updater-script file correctly. Recommended action is to correct the typo and/or use one of the recommended text editors note in Step 4.
Section 4 - Flashing to sdcard
Flashing a rom from this point is the same as you usually do. Put the modified rom on your sdcard and flash with Clockwork Mod like usual. I recommend doing a backup in Clockwork Mod BEFORE you flash in case you messed anything up by accident and end up flashing over internal memory when you meant to flash to the sdcard.
Section 5 - Booting sdcard
To boot from the sdcard place a file in the root of your sdcard called 'bootsdcard'. If you named it correctly upon reboot, the kernel will load the rom from the sdcard and not internal memory.
To boot back into internal memory simply remove this file from your sdcard and reboot.
You can switch back and forth using this method. If the file is there it boots sdcard, if the file is not there it boots normally. Pretty simple right?
Section 6 - Other flashables (not roms)
Themes, addons, and anything else that is flashable with Clockwork Mod must be modified in the same fashion as the rom. Use the same procedure documented in Section 3, The flash method.
Kernel Developers:
If you would like to add dual boot support to your kernel please refer to this commit: https://github.com/Rodderik/Genocide-Kernel/commit/a5dfd9f369ae4f2c90c1e7fc7d8995f88f72bd01
I will update this section if I push any specific changes to dual booting.
Now with an APP!
DualBoot Helper
VenumX coded up an APK to work with Clockwork Mod to run the scripts.
http://forum.xda-developers.com/showthread.php?p=15486144#post15486144
Questions, concerns, gripes, or complaints can be left in this thread. If you need to report any problems please be as detailed as possible.
woot
Thats my boy!!!! Make me proud!!!!!!!!!!
w00t! go man go!
Holy ****! This is huge! Thanks!
Sent from my SPH-D700 using Tapatalk
OMFG this is way amazing ;P
Thr genious once again with another first
Sent from my SPH-D700 using XDA Premium App
Edit
nevermind...
good work!!!!!!!!!!!!
davidrules7778 said:
I got a question...
Would i be able to run dual versions of android
Ex 2.1 and 2.2
or 2.2 and 2.3
if the kernal is compatible?
Click to expand...
Click to collapse
if the kernEl was compatible yes...but none of them are...and likely won't be
Good damn job bro.. Let's keep the dev community developing
Rodderik said:
if the kernEl was compatible yes...but none of them are...and likely won't be
Click to expand...
Click to collapse
what if u made one of the eclair kernal compatible or gingerbread whenever we get custom kernals for it?
Or is it not possible to make eclair kernals compatible?
i think i could make a GB kernel now.. but you wouldnt be able to mix gb with froyo or eclair, because a GB kernel wont boot those builds..
Awesome work bro! Amazing...simply amazing!
chris41g said:
i think i could make a GB kernel now.. but you wouldnt be able to mix gb with froyo or eclair, because a GB kernel wont boot those builds..
Click to expand...
Click to collapse
yup i'm going to help chris41g put together a gb kernel for you guys
as far as eclair...honestly who still uses eclair? and why?
Rodderik said:
as far as eclair...honestly who still uses eclair? and why?
Click to expand...
Click to collapse
Just what I was thinking.
Tested on EC05 just now. I uhh... likey? =)
to bad no multi android versions though =(
why cant the kernel read off the sdcard? do you need drivers from samsung once again?
Shoulon said:
Tested on EC05 just now. I uhh... likey? =)
to bad no multi android versions though =(
why cant the kernel read off the sdcard? do you need drivers from samsung once again?
Click to expand...
Click to collapse
well the kernel is stored in bml7 and called by sbl/param during boot so unless we can get a bootloader to intercept the initial loading of the kernel and pass it off we are stuck with one kernel at a time
Very Nice Work !!!
Hey rodd... I think you should work on an aosp gingerbread kernel ... this is a great advancement in devlopment man... right when it was slowing again
Sent from my SPH-D700 using XDA App
this is amazing, thanks for this!!
You cannot make a cross OS kernel. We cannot integrate this into GB yet because there is no GB source, no GB source, no custom kernel. This is Froyo only, and well, someone else can make an eclair only kernel, but that is stupid.
Hola peoples!!! Ok so I just thought I'd create my own thread on this matter. Mustangtim started one in apps and themes (and here is the link to that thread) but since I'm taking over this project it was brought to our attention that this should be in the dev section as its no longer just an app.. I am actually tearing .imgs apart trying to figure out what the deuce.
FIRST OFF THIS IS A WORK IN PROGRESS, WE ARE NOT YET FULLY SUPPORTED. HOWERVER I'M DOING MY BEST TO CHANGE THAT.
Secondly if you want to help get this started please visit the market and grab the app here. Its a $3 dollar app for unlimited amount of roms, based on your SD card storage capacity anyway. And speaking of which you need AT LEAST a class 4 or better SD card to make this run smoothly.
Also feel free to visit the forums at http://forum.init2winitapps.com/
Ok so here it is, Boot Manager Pro. Its been a long time coming for the g2x to dual boot. First off let me say long story short, I currently have a bootable SD Rom, known as ROM1. I have yet to be able to recreate my findings tho. But it works and it doesnt brick at all. However it is a bit laggy on my class 4 SD card. Luckily I've already done my research on this project as there are many threads of such awesome info so I'm just going to be lazy about it and quote the good people of xda versus re-writing it based off of their info.
ChrisDDD said:
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of its own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, & boot. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flash able backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.
Click to expand...
Click to collapse
So basically upon installing the app you need to setup your phone so that way you can properly install a ROM, follow these steps:
1. Go into the supersu(or superuser app) and then go to settings then disable logging or click none.
2. Then go into the BMP app and press the menu button on your phone, not the app, and go to settings. Once in settings put a check mark in force large boot.img, screen on during install, and then go into variables, leave tegra alone but change the sdcard block to show mmcblk1p1. Then press finish and let the app restart. By the way I didnt change any of the sizes of the .imgs but feel free to do so. But be warned do not decrease the size of the system.img only increase it, if desired.
3.Then after you've done the above you need to setup the phone rom. Click on 'Setup Phone' under phone rom and follow that process to setup your phone rom.
4. Once your phone rom is setup you may begin to install a zip to rom1 or rom2 or whatever slot you want. This is the tricky part. I have done tons of reading and most people say that if your using CWM, which us g2x'ers do, then you will probably have a better chance of getting a bootable rom by restoring from a nandroid backup you did versus installing new.
5. So after you decide which path you will take, nandroid backup or fresh rom install, choose install. If you choose a fresh rom, wipe system, data, and cache right away. If nandroid, then wipe after the install.
6. Now once you have clicked install put your phone down, DONT MESS WITH YOUR PHONE AT ALL! PUT IT DOWN AND WALK AWAY OR SOMETHING! Don’t mess with it, text from it, xda from it, dont even use the screen as a mirror!!!! lol seriously the app is picky and while under the .img creation process you want nothing to mess that up or you will not get it booted. You may however drag down the notifications bar to follow the progress of the install.
7. Once its complete, tap the install complete notification in the notification bar and let the app do its thing to finalize the install and get you back to your rom selection screen. Now if you did a nandroid back up here is where you click 'manage slot' and then factory reset the backup you did. Just do it, dont ask why.
7.1 Also so if you desire to install gapps and/or possibly a different kernel, now would be the time to do so while your here. I have read mixed reviews of doing this process right after the rom installs. However when I set up my rom1, I booted into it first all happily then realized I had no gapps. So I had to reinstall BMP on rom1 then boot back to phone rom and then I installed GB gapps and had no issues booting back into rom1.
8. Once the above steps are done if your feelin lucky go ahead and tap on boot the rom you installed, and if all goes well it will boot up.
9. If it boots up you need to post confirmation here!!! Provided info such as phone rom and the info on the sd rom you used and slot number and such.
Hopefully it will just work for you. I have done all the above steps using HFP 2.1 as my phone rom and only been able to get 1 bootable rom. Being it was for testing I used HFP as my phone rom and as well as my rom1.
So if the above steps dont wortk out for you and your boot lopped or what ever, then turn your phone off and reboot into cwm. You have 2 options to resolve the boot issue you just created. 1, you may go to restore then advanced restore then restore your boot. Or 2. select install a zip and nav to the bootmanager folder then phone rom then flash the update zip there.. then reboot and you should be back at your phone rom.
Here is a basic run down of everything that I have done so far:
When I first started working on this project I wasn’t doing any dev'ing to change any of the stuff in the boot.img. I just changed settings in the app per all the research I did. So when all was said and done I restored HFP 2.1 to ROM1 and it actually booted!! And it works lovely btw.. I can still boot into this rom today. I then decided to pass the word and ways that I created the working rom1, well I nor anyone else I passed the info to was able to get it working. Only one other person was able to confirm that rom1 works but only after I copied all my rom1 info and sent it to him for testing.. and he was able to boot into my created rom1… As I see it, it was a blue moon event that I have yet to repeat. So I thought eff it lets do some dev'in so I unpacked the boot.img from rom1 then compared that to the unpacked boot.img from rom2 that I created in my trial and error experiences. So in doing so I noticed 4 differences; 1, the mount points obviously, 2, in the sbin folder had a ueventd file from the working rom1 was a text file viewable by gedit in ubuntu. In rom2 it was just a non-readable file. 3, in the init.rc file was also missing a chmod command for system, (the command is in rom1 but not rom2) and 4, there was a ueventd.tegra file that was in rom1 that wasn’t in rom2, but everything else is the same. So I decided to plug and play with the differences to see if she boots and no go. I don’t understand why its boot looping because I am using the same rom as phone rom as for rom1 and rom2. So it boot looped. So I had to restore my boot.img many times in cwm.
So then I said eff it lets do some more research, then I noticed in the .zips folder plus the individual rom folder there are .zips that will let you flash via cwm if you get boot loops and 'should' get you booting to your desired sdrom. I then tried that way and no go.. so then I opened up the zip and had a look at the internals.. first there is the moveboot.sh file that the app runs in cwm flash the given boot.img. I then checked out the meta-inf and opened up the updater-script thinking that the app wasn’t actually flashing the boot.img which is why it loops... Well I think im half way right. However the script itself is lil dodgy... first thing I noticed was at the end of the script they have a command to cp the log from /tmp to /sdcard/bootmanager well the command was wrong so it never copied the log. So I fixed that. I also saw that the assert command was pointing to ‘boot’ instead of mmcblk0p5, so I changed that too. Then I decided to do away with the assert command and the moveboot.sh file they have going on to utilize the same functions that the kernel zips use, which is a kernel folder that holds the boot.img and a run_program that dd's the boot.img to 0p5. plus I even updated the update-binary that the file uses. I used the one from the g2x nullifier as I know that one was made for our phone and should have no issues.. plus there was a noticeable difference in the sizes of the provided binary to that replaced binary. So with the updated.zip file I then rebooted into cwm to flash that being that I was using a different command to flash the boot.img as well as the other changed stuff and still it boot looped. So as of now the only thing I don’t think ive done was grab the boot.img from rom1 then change the mount points, only change that, and then use that for rom2 and see if it boots. I don’t think I’ve done that yet. But every dam process I do I get boot loops. So basically I have came to the conclusion that it’s now NOT a boot.img issue being that I have done everything to change the boot.img and to make sure it flashes, which it does indeed and now creates the log too… I think maybe it has issues with the system.img as that’s what comes next in the boot process. But that’s just my hypothesis. I won’t be able to confirm this till I liberate rom1’s boot.img then change the mount points to point to rom2 and then see if it boots.. if it don’t work then that would mean to me that there is an issue with system.img created. But that’s just my hypothesis…
What I don’t understand is why the eff when I didnt hack the app I got a working sd-rom, but when I do change some stuff with it still don’t work!!???!! I guess maybe ill just edit/hack the apk to see what’s up.. This is getting way more complicated than it needs to be, since it worked prior to all my major changes to the script its using for flashing and the boot.img and what not. Anyone have any ideas feel free to add them.
My next steps are to edit rom1 boot.img one last time to change the mount points to point to rom2 and then if that’s a no go then it’s got to be the system.img that’s getting created. By the way this whole process I have only been restoring my nandroid backup for HFP 2.1. I have not attempted to flash new as with thru my research more times than not people would get a bootable rom via restoring versus flashing new.. so if anyone wishes to experience an sd rom let me know, ill send you a link to download my rom1 to get it going. Mind you that its not perfect and you need a class 4 or better sdcard. Everything works but it just takes a bit longer to load things and get things cached as its on the sdcard and not nand. Also if you have any input or are wishing to help pm me I need more heads to get this sorted as I can’t be the only one who knows how to edit scripts and unpack imgs and such. Either way I will continue to do this until I get it right damit!!! Oh and I just ordered a class 10 sdcard to help with this process…
That was copied from the other thread that mustangtim started. Last night when I went home the first thing I did was change the mount points on rom1 to reflect rom2, I changed nada else, then I tried to boot it... it boot looped. So maybe its a permissions issue or the system.img.
So just as a proof of concept and before anyone calls bs on my work/findings Here is the link to my rom1 that boots and is HFP2.1. *Update, 'm just going to
leave it on my DB for now till I find something better I guess. xda wont let me attach the file since its 233MB. Oh well here is the link :
Code:
[URL="http://db.tt/eBZwrOrs"][U][B]Here it is, my Rom1 HFP 2.1[/B][/U][/URL].
I have also attached my updated script file to flash back to rom1, for now.
The boot.img points to rom1 instead of phone rom, ill add to phone rom
as well, just not the now. :) Feel free to flash this via cwm versus
restoring...
Also this is part of the this: the ‘.zips’ folder you need to replace the file in
that folder as well. It’s an update file for rom1 to flash the boot.img.
..
If you’re going to use this you need install a random rom to rom1 then replace those created files in rom1 with these files in the 7z file..
So I am doing this new thread to get the devs or people with know how to help me out with my findings. I have edited the boot.img so much I could pretty much re-write everything in there by now including using magic to create to my own kernel eff!! lol jk but seriously I need people with knowhow to provide confirmation of go or no go. Basically I have people whom have helped out but It seems that I'm the only one who has dug this far into this app(unless i've been misinformed) and I have no one on my level to talk with except the init2winit devs. Which are very helpful btw.
And lastly:
Conap said:
Guys if it's failing to make the boot.img first make sure your using the market version....others have released cracked versions of our app which they broke...if your using the actual market version just send me a pm or email [email protected] and send your log.txt from BootManager folder on sdcard and we'll get it straightened out. Thanks.
Click to expand...
Click to collapse
or post here or PM me, I'm always down to help out.
Also thanks go to the init2win team, Gflam and Conap as they started this app. and as well to Mustangtim as he brought me into the light of BMP.
So you got all that???!!!??? Now lets get this party started and get full support for dual booting. I will not rest until I get this working. Thanks for your time and possible assistance.
Ok so since I have a book above I thought this is a good place for links and such...
So just incase anyone is curious, here is the Official Boot Manager Manual
Here is a nice link for Tips and Tricks while Installing ROM's that so far has good info to help you watch via adb what the BMP is doing in its creation process.
Some FAQs:
When should I set up my phone ROM?
Set up your phone ROM EVERYTIME you install a new ROM to your phone so you can get back to your phone ROM and won't get stuck on your SD ROM.
My SD ROM seems to lag how can I fix this?
SD ROM lagging may be due to a few things which all have easy fixes. First fix is that most of you have class 2 cards which are what usually come with your phones. These have a much lower read/write then cards of a higher class, we recommend a class 6 card or above. Another easy solution is overclocking merely install a better kernel and use CPU Boost (or any other overclock app) to overclock your phone.
Can I nandroid my SD ROM slots?
Yes and no you can't nandroid them in the traditional sense of the word using recovery but this app works as a recovery for your SD ROM slots and you can back up your ROM slots within the app in the Manage Installed ROMs section which works as a nandroid for your slots by fully backing up your slots to your sdcard which can later be restored.
What if I want to change the sizes of my images, how may I determine the individual sizes easily?
Easiest way is to open up terminal emulator in your app drawer. Type 'su', then grant permissions if need be, then type 'df -h' and it will display such information. You may also use adb in the same fashion. Connect via usb, open up command prompt/terminal and get adb connected and then type 'df - h' again and the same info will show. I will say this again just because, do not decrease the size of your system.img ever! Unless you want mad issues!
Here is the changlog link and just for heck of it the info based on that link:
Code:
V3.2.6
Fixed DroidX/Droid2 Install issue
Fixed UI theme issues
Fixed issue with spaces in name of pic when selecting photo for screen shot
V3.2.5
Fix to allow continue of install if no boot.img is found.
V3.2.4
Added support for HTC Rezound
Added support for rom's with multiple boot.img's
Added support for rom's made for multiple phones
AutoDetect sdcard for usb mounting
Fix for installing ICS gapps
Optimized SDRom Install process
Added support for Motorola RAZR
Added install queue
V3.2.3
Fixed issues with rom's not showing when on emmc on Droid Incredible
Fixed issues with not showing correct booted rom in app
More improvements to sms sync(all rom's will need updated app for changes to apply)
Fix issues with loader
Fixed issue with switching to backup server when main server goes down
Fixed 1x1 widget to show unlimited rom slots
Added 2x2 widget that works with unlimited rom slots
V3.2.2
Fixed force close for img's over 1Gb when resizing
Fixed current booted rom displaying correctly on gnex
Fixed issue with wrong busybox downloading on gnex which should fix alot of install/boot issues
V3.2.1
Fix for errors causing installs to fail.
Fix for some of the licensing stuff.
Removed sdbooster prefs from Galaxy Nexus(Since they don't have sdcard).
V3.2
Changed 4 sd slots to infinite slots!
Galaxy Nexus Support
Sms and Call Log synced between ROMs (you choose what ones too also requries updating boot manager in all slots)
License Check extended to a week
ROMs do not need market installed for boot manager to run (requires updating boot manager in all slots)
Hide su toasts (superuser elite only)
Fix for force close when setting screen shot in MIUI rom's
Thunderbolt defaulted to force large boot.img
Fixed unsupported device using a key
Manually setting variables only accepts numbers
V3.1.1
Fix for various force closes in rom installs and Nand restores
V3.1
Added su binary check
User selectable colors for everything
Better navigation (press title for quick action)
Added compatability for new twrp backups
Better compatiblitlity with memory tweak scripts(i.e. supercharger script and liquids default scripts)
Fix for install process being killed by android
Fix for some themes erasing img's
Fix more force closes during install
Force smaller boot.img option in settings(Fix for some phone's who's boot.img won't fit on the phone after BootManager edit's it)
Improved gapps checker
Improved security
Boot Manager now accepts keys pay for by paypal (see http://init2winitapps.com/stories/BootManager.html)
Added Evo 3d GSM Support
Added notifcation sound/vibrate for finished install (turn on in settings)
Improved data check
V3.0.3
Fix some force closes
V3.0.2
Added backup server (Sorry our server dropped out)
Fixed some force closes
2nd init fixes for Liquid's ROMs
V3.0.1
Last minute UI fixes
V3.0
UI Completely redone
Includes screen shot of each slot
Custom Info
Custom Dialogs
Custom Animations
Custom everything!
Bug Fixes
Added Droid 2 Global support
Screen shot with long press of search
V2.2.1
Bug fixes in file browsers
File browsers only show relevent files
Kernel installer fix
Droid 2 bug fix
V2.2
New security (more advanced and requires data only once a day)
Installs no longer require data
Added Italian translation thanks Black-Ice
Droid X support
Droid 2 support
Fixed status bar notifications
Fixed phone rom rebooter if gapps aren't installed
Bug fixes
V2.1
Restore android_secure to sd from nandroids
Added TWRP nandroid support
Added CWM tar nandroid support
Added Spanish translation
Made widgets easier to use
SD Booster added (Change SD read cache for better preformance)
Added current settings to manually set variables.
Added option to keep screen on during install in settings
Fixed usb layout
Updated Security
Bug Fixes
V2.0
Install now runs from the foreground (status bar)
Restore Nandroids to slots also in the foreground
User can cancel installs as they run
4 new themes added including one by apophis9283
Some phones such as tb moved to new install code (Fix for some sense rom's)
V1.3
Added third theme to app (Red Theme)
Added 4x1 widget and new widget styling
Fixed in app messenger
Added support for Htc Evo 3D
Added support for Htc Sensation
Added Support for Htc Incredible 2
Added Support for Htc Incredible S
Added Support for Htc Desire S
Added support for LG Ally
V1.2
Added option to reboot to phone rom to install gapps in license check dialog
Better error checking and error logging
Automatically install's ext2 libs if not present
Moved Set Names to Manage rom's
Fix for add-on's not installing correctly
Better compatiblility for rom's that use data2ext or apps2sd(user must set larger img's in manual variables)
Trash cleaner added to extras
Better Fix for WiFi issues on Droid 1
Added display to show what rom you are booted into
Fix for updater-script not found errors
Added support for Htc NexusOne
Added support for Htc MyTouch4G
More compatiblity for ext4 support
V1.1
Fix WiFi issues on Droid 1
Fix bug in rom installer for setting permissions correctly
Fix bug for cache size not setting correctly in setting variables manually
Fix for decimals entered into partition sizes causing force close
Fix force close in widget
Fix force closes in installer
Added Wipe data/Factory reset to Manage Rom's section
Added code to show what file's are being unzipped in dialog
Added support for rom's that extract files to sdcard so the files actually end up on your sdcard
Added support for Htc Desire (apps2sd and data2sd rom's support is experimental. Please email if you test it and it works/doesn't work)
Added support for Htc Inspire4g
Added support for Htc DesireHD
Added option to use ext4 filesystem if rom's support it-Experimental Won't work with all rom's.
Added log.txt file to sdcard to log errors during install
V1.0
Initial Release
YEZZZ
glad to finally see this here!
jookdakang23 said:
glad to finally see this here!
Click to expand...
Click to collapse
indeed... hopefully it wont be before too long that I get this app fully supported for us!
This app will be extremely useful for G2X owners and makes the G2X more versatile and desirable.
da-pharoah said:
indeed... hopefully it wont be before too long that I get this app fully supported for us!
Click to expand...
Click to collapse
idk how you get it booted. lol i keep getting bootloops
jookdakang23 said:
idk how you get it booted. lol i keep getting bootloops
Click to expand...
Click to collapse
Are you using the files I supplied or the ones that BMP created for you?
Woo hoo good job bud
Sent from my LG-P999 using xda premium
x0xhellx0x said:
Woo hoo good job bud
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
LOL thanks bro.... Go Team Hellfire!!!!
da-pharoah said:
Are you using the files I supplied or the ones that BMP created for you?
Click to expand...
Click to collapse
i remember requesting the files but think you ever sent them
jookdakang23 said:
i remember requesting the files but think you ever sent them
Click to expand...
Click to collapse
no we had a miscommunication due to our avail times and GB's lacking ability to utilize two accounts on gtalk.... I have posted those files in the op however...
First, I want to thank everyone who has helped with us on this app. Second, I know I picked the right man for the job, did you see that OP! All kidding aside, a lot of you know I write for ACS under screen name artifintel. I just had too much on my plate to give this project the attention and direction it needs. The right guy is in charge, he's a stand up person and very knowledgeable with this app. Good luck everyone!
[email protected]
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Rafase282 said:
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Click to expand...
Click to collapse
what rom are using as phone rom? and you installed to rom1?
da-pharoah said:
what rom are using as phone rom? and you installed to rom1?
Click to expand...
Click to collapse
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Rafase282 said:
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Click to expand...
Click to collapse
and no bootloop you say?? well then it may be the stock rom your using... The app is very picky and if you get a bootloop, I feel that those can get booted with tweaks... but stuck on lg screen is just no bueno.. Try a different rom... maybe one that has its partitions at ext3 format just to try it.. I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
hands down, a badass app...
SiL3nTKiLL said:
hands down, a badass app...
Click to expand...
Click to collapse
lol +1 for sure!
da-pharoah said:
I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
Click to expand...
Click to collapse
positive on ext4
By popular demand, I am bringing to you CM10.1 that you can install into Nook's internal ROM.
Note, this version totally overwrites your ROM, so back up everything important before proceeding. This is not a dual-boot solution as before, you do loose B&N ROM for good after installing this.
This is work in progress, yadda yadda.
Simplified instructions if instructions below don't work for you or you cannot follow them.
Get emmc-cwm-early2.1.img.gz, gunzip and write it to an sdcard of at least 1G in size (all content on that card will be lost).
Download CWM recovery (text) or TWRP recovery (gui) zip if you want internal recovery to be replaced with CM one (if you don't know what is it about, then you need ONE of these).
Also download latest binary zip from CM nightlies: http://download.cyanogenmod.com/?device=ovation
Add all these files + whatever other packages you might need right away on to the sdcard.
Boot from that sdcard, and install recovery (if desired) and the cm10.1 binary and whatever else you put there.
Erase /data (During initial install only. this is important to avoid crashes on bootup! Naturally, make sure you have copies of whatever important info from there).
unmount /sdcard and remove the card from the Nook. You might need to use this sdcard for your recovery needs in the future should EMMC content become badly damaged, so probably a good idea to have a copy of it somewhere.
Congrats, now on reboot you'll get into cm10.1 on your Nook HD+.
When you need to get into recovery, you can either do "reboot to recovery" in reboot menu (need to enable that in settings) or reboot the nook, and when you see original nook boot logo, press and hold power + home buttons for about 4 seconds.
If you plan to use USB Host feature, you will need a gender changer, as B&N decided not to release a special cable so far. The control to enable USBHost is in quick settings panel (slide down in the top right corner of the screen to bring it up). (QS controls are not available in CM nightly builds so you'll need to install the switcher app for now if you need it).
Known problems:
- Nook app reports incompatible in market (workaround1: just sideload it ; workaround2: change ro.product.device to nookhdplus in build.prop) - This is because they specifically blacklist Nooks! Note that workaround #2 will actually kill your sound, so revert back when you are done.
- Certain sdcards still remain unstable.
- Google Earth crashes when pressing "my location" button (but works fine otherwise).
Useful apps:
Overall loudness and volume control app: NookHDVolumeAdjuster-1.apk
Touch screen sensitivity control: NookTouchscreenSensitivityAdjuster-4.apk (backup link)
USB host control (not really needed, as you can use Quick Settings panel): USBHostSwitcher.apk
Changelog:
13/08/09 - We are official part of CM now, yay! Further updates will be at http://download.cyanogenmod.com/?device=ovation
13/08/01 - cm-10.1-20130801-UNOFFICIAL-ovation-emmc.zip
- Data usage display should work now
13/07/19 - cm-10.1-20130719-UNOFFICIAL-ovation-emmc.zip
- Picked some kernel fixes from omapzoom tree that I think would be useful for us too, this includes some voltage changes (decreases).
- Disabled hwui scissors optimization as it seems to be doing more harm than good.
- Reverted too greedy davlik vm settings
13/07/16 - cm-10.1-20130716-UNOFFICIAL-ovation-emmc.zip *Experimental*
- Update wifi drivers to R5.SP3.06
13/07/11 - cm-10.1-20130712-UNOFFICIAL-ovation-emmc.zip (backup link)
- Added Apple keyboard support
- Updated to CM-10.1.2 for security fixes
13/07/10 - cm-10.1-20130710-UNOFFICIAL-ovation-emmc.zip
- Updated to CM-10.1.1 for security fixes
13/07/08 - cm-10.1-20130708-UNOFFICIAL-ovation-emmc.zip
- NTFS and ExFAT support from upstream
13/07/06 - cm-10.1-20130706-UNOFFICIAL-ovation-emmc.zip
- redone touchscreen sensitivity changing mechanism. (app to control touchscreen sensitivity NookTouchscreenSensitivityAdjuster-4.apk)
13/07/04 - cm-10.1-20130704-UNOFFICIAL-ovation-emmc.zip
- upgraded to fixed SGX DDK [email protected] (this fixes Google Earth, and a bunch of games)
13/07/03 - cm-10.1-20130703-UNOFFICIAL-ovation-emmc.zip Experimental
- experimental touchscreen sensitivity change
- usb ids changed to match stock
- swap support enabled
13/06/30 - cm-10.1-20130630-UNOFFICIAL-ovation-emmc.zip
- Serial number is now visible in Android
- usb audio now actually works (only for output)
13/06/29 - cm-10.1-20130629-UNOFFICIAL-ovation-emmc.zip
- in-kernel bluetooth
13/06/26 - cm-10.1-20130626-UNOFFICIAL-ovation-emmc.zip Experimental
- cpu frequency changes for screen on scenario, new sgx binary blobs.
13/06/24 - cm-10.1-20130624-UNOFFICIAL-ovation-emmc.zip
- more kernel drivers for bt hid, usb 3g modems and gps devices
13/06/15 - cm-10.1-20130615-UNOFFICIAL-ovation-emmc.zip
- WiFi Direct and BT tethering are now working
- /sdcard now points to internal storage.
13/06/13 - cm-10.1-20130613-UNOFFICIAL-ovation-emmc.zip
- Boosted speaker volume. If you do not like new loud volume, flash this reversal zip after every ROM update: quietvolume-2.zip
- zinio now should work out of the box
13/06/11 - cm-10.1-20130612-UNOFFICIAL-ovation-emmc.zip
- Fixed HDMI audio
- Added USB audio support
13/06/08 - cm-10.1-20130608-UNOFFICIAL-ovation-emmc.zip
- Fixed nav bar settings crash
13/06/05 - cm-10.1-20130605-UNOFFICIAL-ovation-emmc.zip
- USBHost access is now conveniently located in QuickSettings. (IF you use some mod that disables quick settings, you still need my old ugly USBHost switcher app, just sideload it).
- now any (one at a time) usb storage should be automounted no matter how you plug it.
13/06/02 - cm-10.1-20130603-UNOFFICIAL-ovation-emmc.zip
- Forced USB Host support.
13/05/30 - cm-10.1-20130530-UNOFFICIAL-ovation-emmc.zip
- No Nook-specific changes, based on CM10.1-RC3
13/05/27 - cm-10.1-20130527-UNOFFICIAL-ovation-emmc.zip
- Fixed microphone input volume
- Kernel change to hopefully better work with some sdcards.
13/05/12 - cm-10.1-20130512-UNOFFICIAL-ovation-emmc.zip
- Fixed A2DP audio
- Fixed booting when not connected to PC/charger.
13/05/11 - cm-10.1-20130511-UNOFFICIAL-ovation-emmc.zip
- Should fix sgx crash on startup for those affected -- not.
- Cover close now should sleep the device (please test)
- Updated screen properties to highdpi (though that did not fix Nook app compatibility in market)
- Baselined on CM10.1-RC2
13/05/10 - cm-10.1-20130510-UNOFFICIAL-ovation-emmc.zip
- Wifi battery drain should be gone now.
13/05/05 - cm-10.1-20130505-UNOFFICIAL-ovation-emmc.zip
- Fixed mmc presentation, BT, sdcard mounting.
13/05/04 - cm-10.1-20130504-UNOFFICIAL-ovation-emmc.zip initial release.
Thanks for this though.
Verygreen, I am interested how this boots without sdcard as before the expliot worked because B&N left dev code to boot a kernel from sd card.
What exploit is used to boot from internal since sdcard isn't used.
Also I don't think cm10 is needed really.
I think its best to put the work into cm10.1 as its the latest platform and try bring that up to the same stage as cm10.
Wow, thank you once again verygreen! Thank you so much for your efforts!
I'm just wondering, does this overwrite the stock ROM, this no dual boot? Also, are there any performance differences?
Regardless, appreciate your efforts once again!
HiddenG said:
Wow, thank you once again verygreen! Thank you so much for your efforts!
I'm just wondering, does this overwrite the stock ROM, this no dual boot? Also, are there any performance differences?
Regardless, appreciate your efforts once again!
Click to expand...
Click to collapse
Is the reboot to 99% problem solved ? This is the biggest issue to me.
sorrowuk said:
Verygreen, I am interested how this boots without sdcard as before the expliot worked because B&N left dev code to boot a kernel from sd card.
What exploit is used to boot from internal since sdcard isn't used.
Click to expand...
Click to collapse
Same method as Bauwks, B&N forgot to fix it, they fixed some other possible vectors only.
I was holding to this knowledge hoping that it would be useful on next B&N reader, but it does not look like they'll release another omap-based one, so no need to keep suffering anymore.
So here's hope whatever they release next, the debugging code will remain in place
HiddenG said:
I'm just wondering, does this overwrite the stock ROM, this no dual boot? Also, are there any performance differences?
Click to expand...
Click to collapse
Yes, this does overwrite stock ROM, so no dualboot.
While it's possible to perform some hair-splitting by putting multiple kernels into boot partition, that's quite a bit of hassle + all the /data splitting, so I decided to not go that way, at least yet.
There are performance differences. I did not perform any real studies, but I was shocked at how fast the install phase in cwm works compared to sdcard.
lchen5 said:
Is the reboot to 99% problem solved ? This is the biggest issue to me.
Click to expand...
Click to collapse
Yes, it is solved by removing the ROM, so nothing is left there that could complain about cards with too many partitions
Awesome
I've gotten this loaded up this morning, haven't done a whole lot with it as of yet, but it did boot right up
I have noticed one thing that is not working correctly, specifically the sd card. It's reported as not mounted.
aszid said:
I've gotten this loaded up this morning, haven't done a whole lot with it as of yet, but it did boot right up
I have noticed one thing that is not working correctly, specifically the sd card. It's reported as not mounted.
Click to expand...
Click to collapse
Yes, I was just going to post that. Verygreen forgot to change the vold.fstab file from the sdcard version to emmc version.
Go to /system/etc/ and edit the vold.fstab file to say "/storage/sdcard1 auto" instead of "/storage/sdcard1 5". Just change the 5 to an auto. Then reboot and it should be ok.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
Yes, I was just going to post that. Verygreen forgot to change the vold.fstab file from the sdcard version to emmc version.
Go to /system/etc/ and edit the vold.fstab file to say "/storage/sdcard1 auto" instead of "/storage/sdcard1 5". Just change the 5 to an auto. Then reboot and it should be ok.
Click to expand...
Click to collapse
It's always the small things that gets forgotten, sigh.
I knew I needed to update that, but did not find it at 4am. Now it's in my tree, so next version will have it fixed.
Also need a better way to write sdcard image, I guess, without uploading a whole gig or so of zeros which will get slow. I tried to put in some shortcuts to minimize the write area, but failed so far. Since everything is in the same partition, changing stuff on the fly is hard.
Perhaps a solution where we only use sdcard as means to do initial bootstrap and write correct recovery and use /data/media as the actual sdcard would be better after all.
Follow up question
Could one of you guys explain a method of going back to stock from this? What I mean, is it possible to install Leapinlar's version 2.1 back to the emmc using the recovery used to install this emmc-based CM 10.1? If you suggest that we backup before installing this ROM does that mean that we can use that backup to restore the stock we have on emmc now back to emmc if this were not to work out well?
jentous said:
Could one of you guys explain a method of going back to stock from this? What I mean, is it possible to install Leapinlar's version 2.1 back to the emmc using the recovery used to install this emmc-based CM 10.1? If you suggest that we backup before installing this ROM does that mean that we can use that backup to restore the stock we have on emmc now back to emmc if this were not to work out well?
Click to expand...
Click to collapse
For restore (note, I did not really test any of these steps, but that's how it should unfold):
boot into recovery image from sdcard you made at the beginning.
Upload the backup boot image there (adb push mmcblk0p4 /tmp)
then do adb shell and in there write the image in place:
dd if=/tmp/mmcblk0p4 of=/dev/block/mmcblk0p4 bs=1048576
then do:
mount /bootdata ; rm /bootdata/BootCnt
The removal of BootCnt will tell stock u-boot to force factory restore.
now remove sdcard and reboot, the Nook will do factory restore and you are back to some sort of early 2.0.0 B&N release.
verygreen said:
It's always the small things that gets forgotten, sigh.
I knew I needed to update that, but did not find it at 4am. Now it's in my tree, so next version will have it fixed.
Also need a better way to write sdcard image, I guess, without uploading a whole gig or so of zeros which will get slow. I tried to put in some shortcuts to minimize the write area, but failed so far. Since everything is in the same partition, changing stuff on the fly is hard.
Perhaps a solution where we only use sdcard as means to do initial bootstrap and write correct recovery and use /data/media as the actual sdcard would be better after all.
Click to expand...
Click to collapse
I've been trying to examine what you have done here, and have most of it figured.
That CM zip is pretty straight forward where it just flashes the rom to emmc /system and replaces the boot.img.
The CWM looks straight forward too, but you must use the empty file for something and I can't quite figure that. I thought maybe you were using it to mount something on emmc but I see no code to do that in the ramdisk. You might have the code in a customized init binary. Recovery looks like just a normal 6.0.3.2 recovery from CM.
A suggestion on the CWM recovery.fstab. Change the boot partition fstype from vfat to emmc and backup/restore will handle it properly. And change the emmc to datamedia and /dev/null instead of vfat and 0p10. That way the emmc media partition will mount properly.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
That CM zip is pretty straight forward where it just flashes the rom to emmc /system and replaces the boot.img.
Click to expand...
Click to collapse
Yes, it's pretty straight-forward, and that was one of the goals. Unlike Kindle where you need to jump through some crazy hoops due to Amazon design decisions, Nook is significantly more relaxed.
The CWM looks straight forward too, but you must use the empty file for something and I can't quite figure that. I thought maybe you were using it to mount something on emmc but I see no code to do that in the ramdisk. You might have the code in a customized init binary. Recovery looks like just a normal 6.0.3.2 recovery from CM.
Click to expand...
Click to collapse
The recovery IS straighforward, there's no modified init or anything like that. I am not sure what empty file do you refer to.
The only difference between this CWM and sdcard cwm for sdcard installs are: removed repartitioning code in postboot script and updated fstab to point back at emmc.
A suggestion on the CWM recovery.fstab, change the boot partition fstype from vfat to emmc and backup/restore will handle it properly. And change the emmc to datamedia and /dev/null instead of vfat and 0p10. That way the emmc media partition will mount properly.
Click to expand...
Click to collapse
Aha, thanks. I'll try this and it'll probably solve the remaining CWM problems for me.
Also need to do twrp image, I guess.
verygreen said:
The recovery IS straighforward, there's no modified init or anything like that. I am not sure what empty file do you refer to.
Click to expand...
Click to collapse
I'm talking about the "file" in the recovery image. It is about 950MB and all zeros.
And if you make those mods to the recovery.fstab, then users can use that CWM to reflash back to stock using the B&N zips.
leapinlar said:
I'm talking about the "file" in the recovery image. It is about 950MB and all zeros.
Click to expand...
Click to collapse
Whoops, forgot to remove.
This is how I zero out sdcard content so it better compresses before uploading it somewhere.
jentous said:
Could one of you guys explain a method of going back to stock from this? What I mean, is it possible to install Leapinlar's version 2.1 back to the emmc using the recovery used to install this emmc-based CM 10.1? If you suggest that we backup before installing this ROM does that mean that we can use that backup to restore the stock we have on emmc now back to emmc if this were not to work out well?
Click to expand...
Click to collapse
Based on what verygreen said in the posts above, you should be able to use my stock CWM SD to both backup and restore his new setup. And you can restore an earlier backup of stock too. You can use my 2.1 zip on my thread to put the new stock on if you want replacing his CM10.1 on emmc.
Thanks verygreen, you are awesome!
EDIT: Yes! I just flashed verygreen's new CM10.1 emmc to my internal memory using my stock CWM SD. Worked perfectly.
I just uploaded emmc-cwm-early2.img.gz with fixed recovery.fstab and a zero file removed as well.
Got it going
Thanks Verygreen and Leapinlar.
I got it installed and I saved the boot partition just in case. I hopefully will not be needing to restore, but it is nice to know that I can.
The installed ROM appears snappy and I will report back any issues I discover.
my sdcard is working great after updating the mount. Thanks!
leapinlar said:
Based on what verygreen said in the posts above, you should be able to use my stock CWM SD to both backup and restore his new setup. And you can restore an earlier backup of stock too. You can use my 2.1 zip on my thread to put the new stock on if you want replacing his CM10.1 on emmc.
Thanks verygreen, you are awesome!
EDIT: Yes! I just flashed verygreen's new CM10.1 emmc to my internal memory using my stock CWM SD. Worked perfectly.
Click to expand...
Click to collapse
verygreen said:
I just uploaded emmc-cwm-early2.img.gz with fixed recovery.fstab and a zero file removed as well.
Click to expand...
Click to collapse
Is there any effective difference between the 2 recoveries? That is.. is there any reason i should be bothering to keep 2 different recovery SD cards?
Thanks for all the great work!
aszid said:
Is there any effective difference between the 2 recoveries? That is.. is there any reason i should be bothering to keep 2 different recovery SD cards?
Click to expand...
Click to collapse
There's no great logic in my recovery, just an image I use to test-drive my installs for now.
So you can use whatever other recovery you like.