Database Develop

Apps2SD greyed out....

Yeah, first thing the 'uber coders' will think is 'google it' or 'rtfm'. Well been all over and still can't get it to work. But I'll jump though the hoops and hopefully someone will point out where the missing information is. As much documentation that is out there for Android, there is much left to be desired and checked for clarity. So here it goes:
After having many issues with Clockwork Mod recovery, I finally got AmonRA installed and was able to install CM5.0.7 (8 would not install properly at all...too many broken thing like FCs on settings and such).
Things I have done to try to get Apps2SD working:
1/ Manually partitioned SD card
2/ Use Recovery option to partition the card (converted to EXT4 as per Cyanogen's suggestion)
3/ Tried following advice here: http://code.google.com/p/android-roms/wiki/A2SD
4/ Tried following advice here: http://forum.xda-developers.com/showthread.php?t=520582
- which leads to here: http://forum.xda-developers.com/showpost.php?p=3879988&postcount=41 (which seriously need to be re-written.you can't type adb push while already in adb shell....not recognized)
5/ Ubuntu's Disk Utility tells me the EXT4 partition is clean.
So where to go from here? Nothing seems to make any sort of impact on this phone.

...to the QnA section.....
have you enabled apps2sd?
Settings>Applications and tick the Apps2SD box

Moved as not development.

garok89 said:
...to the QnA section.....
Click to expand...
Click to collapse
Nope, looking now....so far I've got 3 tabs opened because of that....this process is seriously sad. Why are there so many ways (some more poorly written than others) to do the same damn thing that the ROM is supposed to do itself? Don't worry, I'll try yet again another set of instructions to get this to work. Geeze....wasn't this hard the last time I enabled it. Seriously, I do't know why I torture myself with this....
garok89 said:
have you enabled apps2sd?
Settings>Applications and tick the Apps2SD box
Click to expand...
Click to collapse
See, now that's just insulting. Although I will forgive you if you have some sort of mental deficiency and missed reading the subject of this thread.....but just in case, I'll return the favour. If "Apps2SD" is greyed out, that means I am at Settings/Applications and quite have the capability to select option on the phone by pressing/touching the screen. Guess what.....it stayed greyed out. This is why I have a new thread here with the 5 other things that I've read, quite exhaustively, to whit there have been no positive results.

So, following the directions outline here: http://forum.xda-developers.com/showthread.php?t=534714
NO freaking change. This is on a fresh ROM install of 5.0.7. Seriously, My card size in 8GB, like his, so I used almost his numbers, just a few bytes different, and nada.
Talk about a sad state.
Yes I repartitioned the card, yes I wiped the partitions (after reinstalling the first time and getting nothing but FCs, wiped each section available in the Amon RA recovery menu....three times each.)
So, let's try yet another method.....
I downloaded Apps2SD.apk. Installed it and ran it....guess what...it aid my card wasn't paritioned?!?! Umm....wft? Why the hell was CM NOT seeing the paritions? This card has been partitioned at least 20 times in the last month, in various methods. Yeah, this i good for it's lifespan....
So I went through it's partitioning process...guess what...still greyed out.
Opened the app again... "It looks like your SD cars isn't partitioned..."...are you kidding me?? (yes the app was granted Super User permissions when it ran....)
So....where do I find the part in CM that is broken and not allowing Apps2SD to work?

How is it that after wiping each item THREE TIMES in th recovery list, and a FRESH INSTALL that my background is still the same????
What is not being wiped?

with 2.1 theres an option for all your settings to be backed up to google. if your background is stored in the same folder on the fat32 partition of your sd card, when you load the new rom, your phone will set your background to what it was.
i know because i went from 5.07 with one background to jubeh's 2.2 with another background, needed gps, wiped EVERYTHING(data, system, ext partition etc.) in RAmon's recovery, flashed 5.08 and had my old background from 5.07 set, along with all my old apps downloading automatically...half hour later and my phone was done syncing and set up exactly how i like it, w/o me doing anythin.
that's how your background is still the same. =P
edit: looking at your signature..is your ext fs first on your sd card? i might be wrong but i think the fat32 needs to be first???

JadedTech said:
Nope, looking now....so far I've got 3 tabs opened because of that....this process is seriously sad. Why are there so many ways (some more poorly written than others) to do the same damn thing that the ROM is supposed to do itself? Don't worry, I'll try yet again another set of instructions to get this to work. Geeze....wasn't this hard the last time I enabled it. Seriously, I do't know why I torture myself with this....
See, now that's just insulting. Although I will forgive you if you have some sort of mental deficiency and missed reading the subject of this thread.....but just in case, I'll return the favour. If "Apps2SD" is greyed out, that means I am at Settings/Applications and quite have the capability to select option on the phone by pressing/touching the screen. Guess what.....it stayed greyed out. This is why I have a new thread here with the 5 other things that I've read, quite exhaustively, to whit there have been no positive results.
Click to expand...
Click to collapse
i was not attempting to be insulting, i run the cmupdater support and have received numerous "app2sd is greyed out" emails when in fact it was the "move to sd" that was greyed out, not the apps2sd toggle. so get down from your high horse and dont assume that you are better than anyone else. in my experience dealing with hundreds of support requests, i have found it is the person who asks the question, not the people who attempt to help, who are the problem.
"computers don't make mistakes, people using computers make mistakes" comes to mind...
although ubuntu is showing it as clean, choose the "repair SD.ext" option in the recovery...
and although it is unlikely to correct it, fix apk uid mismatches. apps2sd can be a funny thing which can work one day and not the other at times.....
i dont know why i am still trying to help you after pretty much calling me mentally retarded, but hey....
oh, and by "the qna section" i meant that you asked a question in the development area, ie. the wrong section

See, now that's just insulting. Although I will forgive you if you have some sort of mental deficiency and missed reading the subject of this thread.....but just in case, I'll return the favour. If "Apps2SD" is greyed out, that means I am at Settings/Applications and quite have the capability to select option on the phone by pressing/touching the screen. Guess what.....it stayed greyed out. This is why I have a new thread here with the 5 other things that I've read, quite exhaustively, to whit there have been no positive results.[/QUOTE]
you have to have a partition and it will not be greyed out

Either the poor behavior in this thread is going to stop or I'll close it. There is no need to be insulting in any way.

garok89 said:
i was not attempting to be insulting, i run the cmupdater support and have received numerous "app2sd is greyed out" emails when in fact it was the "move to sd" that was greyed out, not the apps2sd toggle. so get down from your high horse and dont assume that you are better than anyone else. in my experience dealing with hundreds of support requests, i have found it is the person who asks the question, not the people who attempt to help, who are the problem.
Click to expand...
Click to collapse
Ok, a few things to clear:
1/ This has truly been one of my frustrating experiences in all the tech I have ever played with (and that's pushing 30 years). Granted you would not know my experiences and my tenaciousness in following directions, despite them having me going off-the-beaten-path because something does not fit any proposed remedy.
What was insulting was the fact that you assumed that I wouldn't check the most basic thing when the ONLY indication that Apps2SD was not working was that tick being greyed out. But that would be because I didn't go into great detail about that. I was kinda hoping that was a given because without it being ticked, it obviously doesn't work.
So, since there was some bas assumptions made, allow me to be the first to apologize deeply and hopefully we can move forward.
garok89 said:
"computers don't make mistakes, people using computers make mistakes" comes to mind...
although ubuntu is showing it as clean, choose the "repair SD.ext" option in the recovery...
Click to expand...
Click to collapse
Did that, no change. Although I will add in that your quote applies just as well to programmers as it does the users
garok89 said:
and although it is unlikely to correct it, fix apk uid mismatches. apps2sd can be a funny thing which can work one day and not the other at times.....
Click to expand...
Click to collapse
Well, doesn't seem to work at all here.<shrug>
garok89 said:
i dont know why i am still trying to help you after pretty much calling me mentally retarded, but hey....
Click to expand...
Click to collapse
That would be because I think you recognized how frustrated I have been and in reality, I'm not really venting at you but at the lack of a solution, despite there being soo many ways to supposedly fix this issue. That would also be because you are most likely the kind of techie that hates to see things not work and will spend more time trying to fix it rather than give in and simply 'reinstall' because you want to know the reason why it happened in the first place. Maybe I'm wrong there, maybe I'm not. I'm am seriously glad that you are taking your time because not a single other person has.
garok89 said:
oh, and by "the qna section" i meant that you asked a question in the development area, ie. the wrong section
Click to expand...
Click to collapse
Yeah, I forgot to apologize to the mod for that. Sorry Mod....
So, have any other ideas how to fix this? I am rather loathe to just try to 'update in hopes that it automagically fixes the issue' approach.

tdt1345 said:
you have to have a partition and it will not be greyed out
Click to expand...
Click to collapse
You might want to read my first post again.....
"Things I have done to try to get Apps2SD working:
1/ Manually partitioned SD card"

jamesd86 said:
with 2.1 theres an option for all your settings to be backed up to google. if your background is stored in the same folder on the fat32 partition of your sd card, when you load the new rom, your phone will set your background to what it was.
i know because i went from 5.07 with one background to jubeh's 2.2 with another background, needed gps, wiped EVERYTHING(data, system, ext partition etc.) in RAmon's recovery, flashed 5.08 and had my old background from 5.07 set, along with all my old apps downloading automatically...half hour later and my phone was done syncing and set up exactly how i like it, w/o me doing anythin.
that's how your background is still the same. =P
edit: looking at your signature..is your ext fs first on your sd card? i might be wrong but i think the fat32 needs to be first???
Click to expand...
Click to collapse
Yeah...I realized this after I left the house and was getting into the car. Just too frustrated when I posted. It was one of those 'don't drink and drive' but more of a 'don't vent and post' type of deals....well, at least not here. Thanks any ways.

have you tried ext2 before upgrading to ext4?
ext4 didnt like my spare g1 too much....but my main one got along fine with it

JadedTech said:
1/ Manually partitioned SD card"
Click to expand...
Click to collapse
Is the partition system ids correct:
Code:
# fdisk /dev/block/mmcblk0
Command (m for help): p
Disk /dev/block/mmcblk0: 8166 MB, 8166309888 bytes
252 heads, 62 sectors/track, 1020 cylinders
Units = cylinders of 15624 * 512 = 7999488 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 952 7436993 b Win95 FAT32
/dev/block/mmcblk0p2 953 1020 531216 83 Linux
Command (m for help):
The 'b' for the vfat partition and '83' for ext
The startup scripts use there values for some autodetection in cm5.
If all you change is the Id data wont be lost but you are at fault if you don't backup.

garok89 said:
have you tried ext2 before upgrading to ext4?
ext4 didnt like my spare g1 too much....but my main one got along fine with it
Click to expand...
Click to collapse
That is a very interesting observation as I have been automatically upgradeding to EXT4 (as I did read that is what Cyanogen uses...figured if it was good enough for him....) so I just reformatted my SD card from the Recovery partition into EXT2 with a 32MBswap and the rest in FAT32. No change. Damn....seemed like one of those 'simple and yet not obvious' type of answers that may have worked too...

ezterry said:
Is the partition system ids correct:
Code:
# fdisk /dev/block/mmcblk0
Command (m for help): p
Disk /dev/block/mmcblk0: 8166 MB, 8166309888 bytes
252 heads, 62 sectors/track, 1020 cylinders
Units = cylinders of 15624 * 512 = 7999488 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 952 7436993 b Win95 FAT32
/dev/block/mmcblk0p2 953 1020 531216 83 Linux
Command (m for help):
The 'b' for the vfat partition and '83' for ext
The startup scripts use there values for some autodetection in cm5.
If all you change is the Id data wont be lost but you are at fault if you don't backup.
Click to expand...
Click to collapse
Now this produced something interesting.
Code:
# fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 243328.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help):
#
So, how does one go about fixing this if this is the reason that "in certain setups cause problems"? This seems to be a likely candidate for the root of the issue.
Redo partitions in Fdisk?

instead of doing it from recovery
do it from ubuntu via gparted

Sorry for jumping in here but... A while back Dusty wrote a great tut for doing this correctly. Did you follow his thread instructions? If not, take a look. It may have the key to your happiness.
http://forum.xda-developers.com/showthread.php?t=534714&highlight=51dusty

JadedTech said:
So, how does one go about fixing this if this is the reason that "in certain setups cause problems"? This seems to be a likely candidate for the root of the issue.
Redo partitions in Fdisk?
Click to expand...
Click to collapse
The size warning only applies to the short falls of BIOS booting x86 PCs. We don't boot the dream from the sdcard or is the phone booted with a x86 BIOS...
If it was you need to ensure the boot partition is near to the beginning of the disk.. you can safely ignore it

Webtop2sd

http://forum.xda-developers.com/showthread.php?t=1119555
Logically speaking, this application should also work with the Bionic correct?
Just wondering, if its deemed safe in this thread to attempt using, I will try it and post back with results.
---------- Post added at 12:30 AM ---------- Previous post was at 12:08 AM ----------
Okay, so I just backed up everything and tried the app, which won't work due to the fact that it checks the phone model number, Theres a manual guide to get ubuntu running on the atrix, and I'm going to start from scratch there. Probably going to be a couple of days before I do anything since I need a new microhdmi...

I tried the app that comes with it to partition the sdcard but it does a device check then it stops with an error message that the device is not an Olympus (Atrix). Maybe we can get the dev to check on the differences, albeit small, for the Atrix and the Bionic.
Worth a shot. I've been playing around with /osh for a few days but had to reflash to stock due to the lapdock staying on the screensaver.

Hey guys, I am working on the same thing at the moment trying to port over Sogarth's method of unlocking the 10.10 maverick build of Ubuntu on our phones.
http://forum.xda-developers.com/showthread.php?t=1000316
The link here is for his old automated .bat script he made for the Atrix that I believe will work for our phones with a little modification to it to reflect Maverick packages instead of the Jaunty packages for their phones.
Please jump into the irc in my sig because I would like to get this going as well.

I would hop in IRC but I'm about to head out the door.
I'm currently approaching this situation from two directions:
1.) I'm dumping /osh/ (webtop partition) and uploading it to dropbox as soon as I can get a complete dump. (hopefully tonight) and providing it to the original Atrix dev to see if he can hook us up with an app to help do whats needed
2.) I'm also attempting the manual method as soon as I get a new microHDMI cable (I was using a cheap adapter).
You are 100% correct though, you should be able to get that install script working just by changing the packages to reflect the updated Ubuntu. MAKE SURE you backup ANY files before you change them (and preferably a complete backup of /osh/. Since we have SU on our phones we have free reign over the /osh partition, so be careful in there.
OT: I can't wait until we can get on-demand CPU overclocking for this thing... if it clocks as well as past mobile chips... Toggle 1.2-1.4ghz and plug it in the LapDock. You'd have a damned fine netbook...
(Not necessarily talking to any experienced users or noobs, the disclaimer about Linux & SU is for everyone reading this thread - I'm relatively experienced in the Linux world... and I need to be reminded of SU's power sometimes.)
I just realized that their phone's Ubuntu distribution is under the 9.x series versus the 10.x series. A lot of Major changes happened to Ubuntu between 9.x and 10.x that affected the way the operating system talked to devices and booted, they stopped using HAL and moved to a new boot method, I am uncertain whether or not the install script will work or not, though I'm somewhat confident it will, given the nature of webtop (Android does the hardware abstraction, and the booting, we just run a second set of executable's on a different X window session attached to a different display) This should mean that the portions that would normally prevent us from just duplicated the script are omitted from the Ubuntu distribution entirely. As long as we keep a backup we should still be fine.

No worries, just remember to keep FXZ and RSD handy. I've screwed up the /osh partition a couple times but that has saved me from complete disaster so far

Good call on bringing this up. Let me know if you need to test anything for this.

@xaero252
So I modified Sogarth's script to use Maverick build of all the tools it downloads and installs but the problem with the script is that it needs the phone to have the ro.secure=0 so that ADB always launches with root access without manually initiating su each line of code. I am not sure if there is a way around it or if we have to modify the script differently. Anywho, I've upload a copy of the work I've done to the script.

Is it just an sh script? If so and ut doesn't reboot the phone at all you could launch a SU terminal and do "su sh script.sh"
oh i see the issue now... we would have to be able to edit the boot loader for that method... if i'm correct though his android app doesnt use the pc for much... if you change that variable on boot do you think it woukd work?
Hmm, I have an idea, its not as polished as the pc based script, however it should still work presuming you can get a SU terminal to run on the phone ( I happen to have one running right now ) I'm going to see if I can't adapt that to a bash script. probably going to take a while.
Curiously we happen to have a 1.5gb partition for Ubuntu on built in memory, where as the atrix only had a 600 or so mb partition... This is great because we should likely be able to continue to install /, /boot and such to internal memory, and use the sd card (even left as ntfs) for /home...
Couple of things: reading through the script it looks like 100% of the commands he runs could be run on the phone via a bash script run as su. The idea is this: convert the entire script over to bash, copy the script, and the required files to the phone, and execute the script from the phone. The only other concern I can see is the wget package included with the script not being compatible with maverick, which doesn't seem likely.
I'm gonna start working on rewriting the script linux native. My idea is to use a terminal emulator (they are free on the market) and run su script.sh and pray. I need to get a new microHDMI before I do this though, so I can test my results reliably.

xaero252 said:
Is it just an sh script? If so and ut doesn't reboot the phone at all you could launch a SU terminal and do "su sh script.sh"
oh i see the issue now... we would have to be able to edit the boot loader for that method... if i'm correct though his android app doesnt use the pc for much... if you change that variable on boot do you think it woukd work?
Click to expand...
Click to collapse
As far as correcting that, no one has attempted doing custom kernels yet so to do the edit to get root access out of the gate is moot at this point.
Hmm, I have an idea, its not as polished as the pc based script, however it should still work presuming you can get a SU terminal to run on the phone ( I happen to have one running right now ) I'm going to see if I can't adapt that to a bash script. probably going to take a while.
Click to expand...
Click to collapse
Your linux skills are probably 10 folds better than mine but I believe if you convert my modified script, which has all the necessary links to the correct packages for our phone, then it might just work.
Curiously we happen to have a 1.5gb partition for Ubuntu on built in memory, where as the atrix only had a 600 or so mb partition... This is great because we should likely be able to continue to install /, /boot and such to internal memory, and use the sd card (even left as ntfs) for /home...
Couple of things: reading through the script it looks like 100% of the commands he runs could be run on the phone via a bash script run as su. The idea is this: convert the entire script over to bash, copy the script, and the required files to the phone, and execute the script from the phone. The only other concern I can see is the wget package included with the script not being compatible with maverick, which doesn't seem likely.
Click to expand...
Click to collapse
The WGET I packaged in the .zip is the correct for Maverick along with all the files in the \bin directory are corrected to match our phone. If you can convert all this to a bash script, that would be awesome instead having to do each command via ADB Shell. The only problem I had with this is every time I tried to run the DPKG command on the .deb I downloaded manually, it threw up an error saying it could not find the file or destination.
On a side note, you are correct that we have 1.5gb partition opposed to their 700mb so we could honestly forget the part about creating a ubuntu.disk on the /data partition and modify the /osh directly for now until the time we need more space. After that, we can see if Sogarth will incorporate your script into his Webtop2sd app or we could make a 3gb ubuntu.disk on the /data partition since we have plenty of space there.
I'm gonna start working on rewriting the script linux native. My idea is to use a terminal emulator (they are free on the market) and run su script.sh and pray. I need to get a new microHDMI before I do this though, so I can test my results reliably.
Click to expand...
Click to collapse
Make sure you get the adapter as well to trigger Webtop cause at the moment our phone wont do webtop directly over HDMI without the HD Dock, Webtop adapter or Laptop dock. If you want to test the script out for now, hit me with the script and I will test it for ya

Install CM9/10 on an old Ubunut partition?

I currently have my touchpad split (16 GB to each) between the stock WebOS and an Ubuntu chroot partition. I don't really use the Ubunut partition all that often and was wondering if there is a way to use that existing partition for a CM install. All of the CM install instructions I have seen involve working with the single stock partition. Is there a way for me to install and dual boot to a CM on my old ubuntu partition, or do I have to Doctor the device back to it's original partition? I would prefer to give CM a full 16 GB to work within (I think from what I read the basic install gives it 1.5 GB). Thanks for the help.

the answer is no. the ubuntu chroot that you setup used a ext3fs. you will need to remove that store-ext3fs partition, extend your logical volume /dev/store/media to use all of the free space, and resize your fat32 partition back to its original size, which should be approx 26G. all your commands such as lvresize, resizefat, lvscan, df, mount, umount etc. can all be done through novaterm.
after you get your volume back to size then you can go ahead and throw the android of your choice on it. if you need detailed help let me know and ill post a more detailed walk through.

Thanks a lot for the response. If you have a method that I could wipe out the ubuntu partition without doctoring i would appreciate it. If I do not have to loose all of my WebOS stuff it would be much more convenient. I am reasonably familiar with linux command line, but less so with novaterm and WebOS structure.

QUOTE=funkbuqet;35322160]Thanks a lot for the response. If you have a method that I could wipe out the ubuntu partition without doctoring i would appreciate it. If I do not have to loose all of my WebOS stuff it would be much more convenient. I am reasonably familiar with linux command line, but less so with novaterm and WebOS structure.[/QUOTE]
Have you considered Taylor on preware http://forums.webosnation.com/webos...partition-filesystem-editor-beta-testing.html .
Features include:
Unmount Partition
Check Filesystem
Repair Filesystem
Corrupt Filesystem
Resize Filesystem
Resize Partition
Mount Partition
Create Partition
Delete Partition
Install instructions can be found here http://en.m.webos-internals.org/wiki/Testing_Feeds?wasRedirected=true . It may be just what you are looking for.

funkbuqet said:
Thanks a lot for the response. If you have a method that I could wipe out the ubuntu partition without doctoring i would appreciate it. If I do not have to loose all of my WebOS stuff it would be much more convenient. I am reasonably familiar with linux command line, but less so with novaterm and WebOS structure.
Click to expand...
Click to collapse
http://www.webos-internals.org/wiki/Application:MetaDoctor#How_to_remove_the_ext3fs_partition
heres a link to help you step by step.
when you get to the resize part of this guide it might get a little confusing. there is an easier way to extend the logical volume size and then resizefat.
instead of writing down the size of the ext3fs before you remove it and then adding that number to the size of the store-media you can just remove the ext3fs then run
# lvresize -l +100%FREE /dev/mapper/store-media
you can check to see if it added all the free space to the logical volume with
# lvscan and/or #lvdisplay
then you can run
# resizefat /dev/mapper/store-media 26G
this will resize the fatpartition to 26Gig which is right about what it should be. you can fine tune it down to the M (megabyte) or even the K (kilobyte) to make sure you get every last bit of space if you want. just make sure that you dont try to resize fat to a size that is larger than the logical volume. if what i just said is confusing then just follow the guide in the link exactly.
one more thing. before you start making any changes run
# cat /etc/fstab
if yo usee a line like.. /dev/mapper/store-ext3fs /media/ext3fs auto noatime 0 0
then you need to remove it before going too far other wise it will attempt to automatically mount the ext3fs partition on reboot because it doesnt know that you removed it.
i hope this helps some, i've had a few beers and got a little buzz going on so if im not making sense i apologize.

haxin said:
http://www.webos-internals.org/wiki/Application:MetaDoctor#How_to_remove_the_ext3fs_partition
heres a link to help you step by step.
when you get to the resize part of this guide it might get a little confusing. there is an easier way to extend the logical volume size and then resizefat.
instead of writing down the size of the ext3fs before you remove it and then adding that number to the size of the store-media you can just remove the ext3fs then run
# lvresize -l +100%FREE /dev/mapper/store-media
you can check to see if it added all the free space to the logical volume with
# lvscan and/or #lvdisplay
then you can run
# resizefat /dev/mapper/store-media 26G
this will resize the fatpartition to 26Gig which is right about what it should be. you can fine tune it down to the M (megabyte) or even the K (kilobyte) to make sure you get every last bit of space if you want. just make sure that you dont try to resize fat to a size that is larger than the logical volume. if what i just said is confusing then just follow the guide in the link exactly.
one more thing. before you start making any changes run
# cat /etc/fstab
if yo usee a line like.. /dev/mapper/store-ext3fs /media/ext3fs auto noatime 0 0
then you need to remove it before going too far other wise it will attempt to automatically mount the ext3fs partition on reboot because it doesnt know that you removed it.
i hope this helps some, i've had a few beers and got a little buzz going on so if im not making sense i apologize.
Click to expand...
Click to collapse
That look pretty easy. Thanks for all of the help I will try this when I get home this evening.

Everything seems to have worked fine. Thanks for all your help.
basic question - If i use Acme3 to install CM9 or 10, where does it install and can I change how much disk space is allocated to android?

funkbuqet said:
Everything seems to have worked fine. Thanks for all your help.
basic question - If i use Acme3 to install CM9 or 10, where does it install and can I change how much disk space is allocated to android?
Click to expand...
Click to collapse
you dont need to worry about that really. what happens is when you install Cyanogenmod 9 for example on the touchpad it creates 3 seperate logical volumes /dev/store/cm-system [304 MB] approx
/dev/store/cm-cache [200 MB] approx /dev/store/cm-data [1.50 GB] approx for a total of just about 2GIGs of space. cyanogenmod now thinks that the 1.5gigs is the internal storage and that the rest of the media partition is "sdcard" even though technically all of it is internal storage. this way you dont have to take any storage away from webos and webos wont take any storage away from android. its shared.
once you have android installed 1.5gigs of space is usually plenty to install all the apps you want, but you can always choose to install apps to sdcard as well. youll see when you get everything up and running and you start exploring the file system with a decent browser like es file explorer or root file browser by jrummy. so basically both operating systems will have access to all of the storage. hope this helps.

Excellent. Thanks again for all your help.
Sent from my SPH-L710 using xda app-developers app

[Q]Is there a possibility to install rom on sd

Welcome. Already he was just asking about the same with the addition of some suggestions.The init.d directory has the opportunity to start up the concrete near the beginning of a comment, start the machine.One could initiate concrete partitions on the SD card to have played a role partition "mtd" for example / system / data / cachefrom what I noticed the kernel to jb has otherwise changed little these partitions (size).I do not know exactly how it looks with them, but if one could perform 2 partitions by mtd / system (small to perform the basic start-up and later redirects to / systemsd and the rest used as a framework or a particle cache?)
examples of partition
mtd / system (start-up)
mtd / ram (unless you know)
mmc / fat32
mmc / systemsd (the rest of the system)
mmc / data
mmc / .......
and so onthat was a minimum of 4 block
for it is our memory that was on the phone at the same time much bigger and faster (unless there think) than a swap sdanother thing that applications were loaded into the framework so that if they were around 500 + mb ram for the system to switch on only long landing and later had to speed up.I came up with this idea a bit strange when I have made applications to change fat32, after connecting the USB cable.for me my memory card is slightly odd partitions of personal reasons
Class10+ 32gb
fat32 / sdcard 26gb block1
ext4 / 4gb sd-ext Block2
swap ... 2gb block3
fat32 / sdcard2 2gb block4
sorry to my poor english. I hope you understand my gibberish (a lot of words I could not remember so I used google translator)

-AsA- said:
Welcome. Already he was just asking about the same with the addition of some suggestions.The init.d directory has the opportunity to start up the concrete near the beginning of a comment, start the machine.One could initiate concrete partitions on the SD card to have played a role partition "mtd" for example / system / data / cachefrom what I noticed the kernel to jb has otherwise changed little these partitions (size).I do not know exactly how it looks with them, but if one could perform 2 partitions by mtd / system (small to perform the basic start-up and later redirects to / systemsd and the rest used as a framework or a particle cache?)
examples of partition
mtd / system (start-up)
mtd / ram (unless you know)
mmc / fat32
mmc / systemsd (the rest of the system)
mmc / data
mmc / .......
and so onthat was a minimum of 4 block
for it is our memory that was on the phone at the same time much bigger and faster (unless there think) than a swap sdanother thing that applications were loaded into the framework so that if they were around 500 + mb ram for the system to switch on only long landing and later had to speed up.I came up with this idea a bit strange when I have made applications to change fat32, after connecting the USB cable.for me my memory card is slightly odd partitions of personal reasons
Class10+ 32gb
fat32 / sdcard 26gb block1
ext4 / 4gb sd-ext Block2
swap ... 2gb block3
fat32 / sdcard2 2gb block4
sorry to my poor english. I hope you understand my gibberish (a lot of words I could not remember so I used google translator)
Click to expand...
Click to collapse
I didn't get you.
But it is possible to install rom on sdcard with High read/write speed.(class 6 or higher)
all U need is a dual-boot recovery
(I don't know that u must have a Rom installed in internal memory or not(
Sent From My "ULTIMATE ROM- gb - WP8 edition" via Tapatalk

yes, but not on my mind
dual-boot umount dir and make new to port img file. mtd block is not changed
my idea if edit mtd block
Memory phone
mtdblock0 /system size 206 mb
mtdblock1 /cache size 50 mb
mtdblock3 /data size 211mb
mayby mtdblock2 is block ram1, ram2 ..... size ~200mb
all ~667mb
my idea is
mtdblock0 /system (basic start-up i don't know mayby 20mb-67mb)
and mtdblock1 is block ram 600mb
of sd card make block to /system /data etc
this is my idea but I do not know if possible

@-AsA-
Hi. I am working on a dual-boot project. I sent you an invite to our group. It would be awesome if we could work together. I have a test kernel ready, if you want to test. It's still a WIP. Everything modified is mentioned there. Please take a look. Thank you.
Looking forward to working with you.
sgt. meow

sgt. meow said:
@-AsA-
Hi. I am working on a dual-boot project. I sent you an invite to our group. It would be awesome if we could work together. I have a test kernel ready, if you want to test. It's still a WIP. Everything modified is mentioned there. Please take a look. Thank you.
Looking forward to working with you.
sgt. meow
Click to expand...
Click to collapse
im helping you on dboot project

The bootloader won't boot directly from the sdcard.
Nevertheless, you can definitely have ROM images in the sdcard and use those while booting android (basically you only have to update init.rc for that).
Check 'multiboot' in my signature for more details.

nobodyAtall said:
The bootloader won't boot directly from the sdcard.
Nevertheless, you can definitely have ROM images in the sdcard and use those while booting android (basically you only have to update init.rc for that).
Check 'multiboot' in my signature for more details.
Click to expand...
Click to collapse
Can we edit bootloader?
Sent from my XPERIA X8 using xda premium

fotak-x said:
Can we edit bootloader?
Sent from my XPERIA X8 using xda premium
Click to expand...
Click to collapse
First make it unlockable for newer devices
Then edit
sent from my W8 using client-server technology

fotak-x said:
Can we edit bootloader?
Sent from my XPERIA X8 using xda premium
Click to expand...
Click to collapse
S1loader is not open source to work with. You could hex-edit it if you had some easy way to flash it and recover from the countless hard bricks the bootloader development process has. Unfortunately this is doable via jtag only. My knowledge is limitted on that area.
Sent from my Galaxy Nexus using xda app-developers app

As for the bootloader, what could be the first real-time editor hex can perform a large change in the machine switched on.
When it comes to dual boot I can help not only the development of a test.
slightly going back bootloader to my x8 from the beginning she had unlocked (date of manufacture 10W40 surprisingly). I had not unlocked. To change the kernel or other heavy operations.Never failed to I managed to brick trying to do specifically
not worried about the phone I'm always ready to purchase a new...

The idea of a modified bootloader is nice, but it have two problem.
1. Modify the bootloader to add capability to boot directly from sdcard is basically useless because this is possible with a simple script in a modified ramdisk. Check the post from nAa, or search the thread about nBoot from feherneoh. This is easy and not need to do dangerous things.
2. The modification of the bootloader is near impossible because:
- the working of S1Boot is not documented
- this is a non-standard raw binary, hard to disassembly/decompile
- if someone can disassembly it correctly, need VERY HIGH skills in native arm assembly programming
- need special hardwares to revive the dead phone after all failed modifications (special cables, setool, etc...)
Don't forget: we had to wait more than a year to get unlocked bootloader (and this modification only skip the security verification), and this is working only with devices what older than 1-1,5 years.
I think if someone have these prerequisites, better if he/she working on valuable things instead of boot from sdcard (add fastboot support to bootloader, etc...)

I was thinking of making nBoot work with JB (it didn't). If that fails we will come up with a new method.
It's almost impossible for us to re-write the bootloader.
It would be super cool if someone added fastboot support to our bootloaders.

nobodyAtall said:
The bootloader won't boot directly from the sdcard.
Click to expand...
Click to collapse
maybe not in our device but its not impossible
http://forum.xda-developers.com/showthread.php?t=2061437

stamatis said:
maybe not in our device but its not impossible
http://forum.xda-developers.com/showthread.php?t=2061437
Click to expand...
Click to collapse
Obviously I was talking about these devices not some Samsung one...
@sgt. meow fastboot support is not something that can be added to an existing bootloader. The bootloader itself has to support this protocol. Hence the only solution would be to switch to another bootloader which would have to be ported from scratch for these devices.
The job would require a tremendous amount of effort since not even miniloader works for them!

Can we use dd to write an entire directory to a .img file? I'm thinking of something.
@nAa
I know. I was just unaware that bootloaders could be ported for our device (even if it meant no sleep for 6 months for the brave dev).

sgt. meow said:
Can we use dd to write an entire directory to a .img file? I'm thinking of something.
@nAa
I know. I was just unaware that bootloaders could be ported for our device (even if it meant no sleep for 6 months for the brave dev).
Click to expand...
Click to collapse
Mtd devices are not block devices. What are you trying to achieve?
Sent from my Galaxy Nexus using xda app-developers app

I was thinking of using feherneoh's nBoot, but in a different way. My idea was to somehow write the current ROM's /system to system.img on sdcard and the same thing with data and cache. Then install another ROM that uses the same kernel (JellySony for example). Then if XXX is present in /sdcard, it would mount system.img as /system (and the same with data and cache), thus enabling dual-boot. In a kinda stupid way.

sgt. meow said:
I was thinking of using feherneoh's nBoot, but in a different way. My idea was to somehow write the current ROM's /system to system.img on sdcard and the same thing with data and cache. Then install another ROM that uses the same kernel (JellySony for example). Then if XXX is present in /sdcard, it would mount system.img as /system (and the same with data and cache), thus enabling dual-boot. In a kinda stupid way.
Click to expand...
Click to collapse
This is how my multiboot mod worked actually - except from the fact that back in those days we couldn't flash custom kernels and the whole job was done via the chroot/hw_config.sh hack.
The bummer is you can't switch kernels so multiboot between say gb and jb is not possible.

nobodyAtall said:
S1loader is not open source to work with. You could hex-edit it if you had some easy way to flash it and recover from the countless hard bricks the bootloader development process has. Unfortunately this is doable via jtag only. My knowledge is limitted on that area.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
...where can i find s1loader in phone? can i pull it out?just curious.....

fotak-x said:
...where can i find s1loader in phone? can i pull it out?just curious.....
Click to expand...
Click to collapse
There are two options:
- Export all the partitions (I think the file is nand_partitions.c) from kernel. The mtdump/dd it.
- Use the mtdmapper module that is in the unlocking bootloader tool to get all the partitions to map and then dump it.
Both ways basically do the same thing and they both have a pretty BIG chance of getting your device hard bricked (even when you are in read-only mode).

HD PLus Partition Table restoration

I've tried diving through google and the site looking for a solution to this. Between noise,missed hits, and age, I am not having any luck finding out if this is solvable.
I made the mistake last year of trying the fstrim fix on a model that was clearly a bad idea on - funny how I found all the "DON'T!" articles a year later despite being from before my search. . *ah well* I toyed with the fixes at the time but never had much luck and set it aside for a while.
Started looking again last night and was able to at least determine the Nook isn't dead. CWM comes up, I can hit it with ADB. fdisk doesn't seem to see anything ( which I'm guessing is expected but I'm unsure why ) so I'm uncertain how to restore. the partition tables.
I have an identical model I can clone if there are any sane processes for doing such, but i've been unable to ask search engines the right questions.
Can someone clarify if this is possible or if I'm "stuck" running off of an sd card from now on?
Thanks.

dbolack said:
I've tried diving through google and the site looking for a solution to this. Between noise,missed hits, and age, I am not having any luck finding out if this is solvable.
I made the mistake last year of trying the fstrim fix on a model that was clearly a bad idea on - funny how I found all the "DON'T!" articles a year later despite being from before my search. . *ah well* I toyed with the fixes at the time but never had much luck and set it aside for a while.
Started looking again last night and was able to at least determine the Nook isn't dead. CWM comes up, I can hit it with ADB. fdisk doesn't seem to see anything ( which I'm guessing is expected but I'm unsure why ) so I'm uncertain how to restore. the partition tables.
I have an identical model I can clone if there are any sane processes for doing such, but i've been unable to ask search engines the right questions.
Can someone clarify if this is possible or if I'm "stuck" running off of an sd card from now on?
Thanks.
Click to expand...
Click to collapse
First, the HD/HD+ does not use a DOS based partition table so fdisk will not work. It has a different system, I think GPT, but not sure it is the right name.
But if you look at my HD+ stock tip thread linked in my signature, you will see I have an article about partition structure there. If you use TWRP on SD it has a terminal emulator that will let you run the routines for backing up and restoring the partitions.
But if you truly messed up with the fstrim fix your device has become read only and it is not fixable.
Sent from my SM-T707V using XDA Premium HD app

leapinlar said:
First, the HD/HD+ does not use a DOS based partition table so fdisk will not work. It has a different system, I think GPT, but not sure it is the right name.
Click to expand...
Click to collapse
This is the provided, linuxy fdisk on the CWM image when I did a adb shell, not the host OS, which also isn't dos. Unless it's behaving in a way different than expected, it should detect the block devices even if it does not understand the partitioning table. Newer implementations of fdisk do speak gpt, but I rather doubt that's on the CWM image. I believe you are correct that it is a gpt table. I'll have to verify against my other device.
leapinlar said:
But if you look at my HD+ stock tip thread linked in my signature, you will see I have an article about partition structure there. If you use TWRP on SD it has a terminal emulator that will let you run the routines for backing up and restoring the partitions.
Click to expand...
Click to collapse
I'll have to give that a whirl. I hadn't spotted that particular bit.
leapinlar said:
But if you truly messed up with the fstrim fix your device has become read only and it is not fixable.
Click to expand...
Click to collapse
I'm not sure. If I run blkid I do see that the two partitions that CWM has a wipe/format seem to have file systems on them, but they are the only ones detected. This makes me think the partitions are borked in some very creative way and I either can't see the table to fix it with the tools I'm using or the tools I need aren't present on my image.

dbolack said:
I've tried diving through google and the site looking for a solution to this. Between noise,missed hits, and age, I am not having any luck finding out if this is solvable.
I made the mistake last year of trying the fstrim fix on a model that was clearly a bad idea on ...
...
Can someone clarify if this is possible or if I'm "stuck" running off of an sd card from now on?
Click to expand...
Click to collapse
If your EMMC is bricked due to "having run fstrim on a faulty EMMC chip", your only option is to run on SD a special "no-emmc" CM ROM such as the one posted at https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/.

digixmax said:
If your EMMC is bricked due to "having run fstrim on a faulty EMMC chip", your only option is to run on SD a special "no-emmc" CM ROM such as the one posted at....
Click to expand...
Click to collapse
Interestingly, using the link to the buggy EMMC Page at Cynogen ( sorry, newb can't link ) mine is not on the list of known offenders.